text:
[READ BEFORE OPENING ISSUES] BEGINNERS GUIDE FOR COMPILING (ERROR FIXES)

MAIN COMPILING
Download this setup file and execute it, follow the steps accordingly in order to compile the game
(for Linux / Mac)
ERROR FIXES
all of these need a terminal / command prompt open, so get ready to type stuff
Press Windows+R and type "cmd"
if you are on Linux, just refer to your Desktop Environment's keybinds to open a new terminal (usually Ctrl+Shift+T)
...or launch it from your start menu

"Library not found: hxCodec" | "Invalid Class: MP4Handler" FIX

type the following commands
haxelib remove hxCodec
haxelib install hxCodec

LUA RELATED ERRORS (mainly FunkinLua.hx returning errors)

type the following
haxelib remove linc_luajit
haxelib git linc_luajit https://github.com/superpowers04/linc_luajit

HXCPP_MSVC_CUSTOM ERROR (This is WINDOWS only error)

NOTICE: you need git installed in order for the next commands to work
type the following
curl -# -O https://download.visualstudio.microsoft.com/download/pr/3105fcfe-e771-41d6-9a1c-fc971e7d03a7/8eb13958dc429a6e6f7e0d6704d43a55f18d02a253608351b6bf6723ffdaf24e/vs_Community.exe
vs_Community.exe --add Microsoft.VisualStudio.Component.VC.Tools.x86.x64 --add Microsoft.VisualStudio.Component.Windows10SDK.19041 -p
del vs_Community.exe
NOTICE: if del vs_Community.exe returns an error, simply delete the file manually

this is for linux though

this is for linux though

it's not

curl -# -O https://download.visualstudio.microsoft.com/download/pr/3105fcfe-e771-41d6-9a1c-fc971e7d03a7/8eb13958dc429a6e6f7e0d6704d43a55f18d02a253608351b6bf6723ffdaf24e/vs_Community.exe

that's a linux command

curl -# -O https://download.visualstudio.microsoft.com/download/pr/3105fcfe-e771-41d6-9a1c-fc971e7d03a7/8eb13958dc429a6e6f7e0d6704d43a55f18d02a253608351b6bf6723ffdaf24e/vs_Community.exe

curl works on windows

does it though?

how do you know that?

it does, just try it

how do you know that?

I tried doing the command in the first place, it works

well I'll be damned, it does work

I think, the installer didn't show up

I think, the installer didn't show up though

it takes a bit depending on your system, but it works

I think, the installer didn't show up though

it takes a bit depending on your system, but it works

it's been a full 2 and a half minutes and it's still not there

did you use the next command after curl?

no I didn't do that but I just did and it showed up

does it work on mac because lime test mac

does it work on mac because lime test mac

it works on every platform

but theres no psych engine mac verison on the gamebanana

doesn't matter, this is for fixing compiling errors

💀

O Wow

i get this
source/FunkinLua.hx:346: lines 346-350 : Int should be Bool
source/FunkinLua.hx:346: lines 346-350 : For function argument 'f'

haxelib git linc_luajit https://github.com/nebulazorua/linc_luajit

haxelib git linc_luajit https://github.com/nebulazorua/linc_luajit

nvm works now

bruh

nvm works now

Guy acts like it’s twitter

I Just Downloaded It, Why Does This Keep Happening?

This Happens Everytime With 0.6.0's Updates.

oh fuck it happen to me

Did You Find A Fix For It?

That Did Not Work, And I Got Hit With More Errors

 I Just Downloaded It, Why Does This Keep Happening?

Which version of haxe and haxeflixel are you using?

Haxe 4.2.4.

Ok I'll Try That.

and make sure your using flixel 4.11.0

My Flixel Version Is The Latest Update. So WHAT'S GOING ON HERE?

Is There A Typo? I Tried It. And This Popped Up.

Is There A Typo? I Tried It. And This Popped Up.

haxelib update flixel you dumbass

F***ING FINALLY! Thanks So Much!

Apparently Flixel WASN'T 4.11.0

Is There A Typo? I Tried It. And This Popped Up.

haxelib update flixel you dumbass

ok idoit

Is There A Typo? I Tried It. And This Popped Up.

haxelib update flixel you dumbass

ok idoit

the only idiot here is you

Is There A Typo? I Tried It. And This Popped Up.

haxelib update flixel you dumbass

ok idoit

the only idiot here is you

wait you donnt even put issues on my engine..SO EVERYTHING IS FINE WITH IT????/

Is There A Typo? I Tried It. And This Popped Up.

haxelib update flixel you dumbass

ok idoit

the only idiot here is you

wait you donnt even put issues on my engine..SO EVERYTHING IS FINE WITH IT????/

I don't even care about your engine, your just a total dumbass

Is There A Typo? I Tried It. And This Popped Up.

haxelib update flixel you dumbass

ok idoit

the only idiot here is you

wait you donnt even put issues on my engine..SO EVERYTHING IS FINE WITH IT????/

I don't even care about your engine, your just a total dumbass

dude im sorry

Is There A Typo? I Tried It. And This Popped Up.

haxelib update flixel you dumbass

ok idoit

the only idiot here is you

wait you donnt even put issues on my engine..SO EVERYTHING IS FINE WITH IT????/

I don't even care about your engine, your just a total dumbass

dude im sorry

it's fine

i fucking hate mythslist hes so fucking annoying on gamebanana

done, you can lock this again

repo: ShadowMario/FNF-PsychEngine


text:
noteData not working

Describe your bug here.
I've been trying to use noteData for a custom note, but it never seems to register
eg. when i try hit a note and debugprint noteData, it prints nothing
code:

Command Prompt/Terminal logs (if existing)
No response
Are you modding a build from source or with Lua?
Source
What is your build target?
Windows
Did you edit anything in this build? If so, mention or summarize your changes.
yes, the note is a lua file on source code. This has also happened on downloaded build before.

directions[direction]

source: gharchive/issue

license_type: permissive

license_source: github-api


text:
How to make dialogue play after a video on source code

Describe your problem here.
I figured out how to make a video play but my monkey brain can't make the dialogue play after it starts the video and the dialogue at the same time then the song plays over the dialogue
Are you modding a build from source or with Lua?
Source
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
nothing important

I got issue 12345 nice


text:
Stage Change mid song

Describe your problem here.
how do I Switch Stages Mid Song? I just need a code for it for the event. and I also need the Value 1 and Value 2 info so I can understand how to use it
I perfer to do this
Value 1: What stage Lua to switch to
Value 2: What stage JSON to switch to
Also give me your icon so I can credit you in my mod along with whatever social media you have. Doesn't matter what it is
Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
Ive added sprites, removed the weeks to create my own, and added a bunch of lua files such as scripts and custom notes, that's pretty much all I did

#3137

That didn't help. what exactly am I supposed to do

i wanted value 1 to switch to a lua
and value 2 to switch to a json
it didn't do anything. what exactly do i do with that information

Not possible

nevermind im just dumb. my bad. sorry. but i figured it out so nevermind


text:
"Hit causes Miss"

What is your question?
I know that the "Hurt Notes" might have been easier to not press, but does it also apply to Custom Notes?
Like, I have notes that kill, and normally I wouldn't hit them at all. or just very very little.
I even have video proof (but then don't mind the mechanic, focus on the bongo cat and the dark red notes. you can even go frame by frame if you want - psych 0.6.2 btw)
So, instead of just trying to "nerf" the hurt notes only, it would be cool, if only those notes which have "hitCausesMiss" turned true. soft and hard coded ones-
I would appreciate it

https://user-images.githubusercontent.com/76132257/177016995-d3b86ed9-2afe-4366-9e17-ac2bb63241ec.mp4

you can change their hitboxes

how?

lateHitMult/earlyHitMult

that must be new-
Is it in FunkinLua.hx?

no they're variables in Note.hx, earlyHitMult isn't new but the other one is

In that case, would I have to increase the late hit?

bigger multiplier = easier to hit late/early

I see-
thanks!


text:
[1.18.2 Bug] NBT Tags

For some reason, Apotheosis is trying to apply NBT tags to things that aren't weapons or armor, preventing things from stacking correctly. For example, if you attack a zombie with bread in your hand, the bread will now have <apoth.equipment: 1b> so it can't stack with normal bread that doesn't have that NBT tag.
https://i.gyazo.com/1a0eae51c56b03d22978ff73be094403.png
Forge - 40.1.85
Apotheosis - 1.18.2-5.7.7.jar

I have the same issue for 1.19.2

Well same here, I thought it was big stack mod's problem, but seems like it's not

This was fixed in 5.7.6 for 1.18, but it has yet to be resolved in 1 19

Manual workaround — put the affected items in a regular vanilla chest, stand on top of it, then run this command as OP:
/data remove block ~ ~ ~ Items[{}].tag."apoth.equipment"

Can also automate with command block and a button to create a "cleanser".

Ok, this is happening still wanted to just update this.
https://puu.sh/Jxhm0/c33368450b.mp4

I'm honestly unsure if the fix for this was published in 6.0.3 - it will be published in 6.1.0, but 6.0.3 is sort of a phantom-build, so it may be in there.

so is this fix not comming to 1.18.2 version? :(

This was fixed in 5.7.6 for 1.18

i am playing all the mods gravitas right now, its had version 5.7.7 and i stil get this bug :(

The fixed code is here and is published in the latest 1.18 release - https://github.com/Shadows-of-Fire/Apotheosis/blob/1.18/src/main/java/shadows/apotheosis/adventure/affix/effect/FestiveAffix.java#L91-L99
This removes that tag from all drops that go through the LivingDropsEvent, which should be all entity drops.  If a mod doesn't process drops through the event, they're violating the contract.

authors: HeavyDeception LunafeyLazuli Shadows-of-Fire ViRb3 enimog rgmoon sreny1

repo: Shadows-of-Fire/Apotheosis

license: MIT


text:
OboOntologyReleaseRunner and files to process.

From m...@sebastianbauer.info on December 04, 2012 00:04:33
When creating an OboOntologyReleaseRunner instance it awaits an OortConfiguration instance. An OortConfiguration contains paths of the files to process (added via addPaths()). However, the createRelease() method of the OboOntologyReleaseRunner also awaits a set of paths argument. From the API perspective, it's is not clear why both are needed if one of the way would be enough. In particular, it seems that the paths of the OortConfiguration are ignored.
It may be of course that the paths for OortConfiguration and for OboOntologyReleaseRunner.createRelease() are something different, but also this is not obvious.
I suggest to clean up the handling of the paths or to document it.
Original issue: http://code.google.com/p/owltools/issues/detail?id=42

From HDie...@lbl.gov on January 07, 2013 15:26:13
Yes, that is an artefact of the development of OORT. The path should be extracted from the configuration object.
I created a new method without the path parameter and marked the existing method as deprecated, see revision r1091
Status: Fixed
Labels: -Type-Defect Type-Review

repo: ShahimEssaid/owltools


text:
ERROR in documentation: sample for running tool using credentials is INACCURATE...

All,
Just a quick note...
In the documentation about using credentials (username/password) in lieu of using a Principal (client/secret), the sample STILL uses the -c and -s parameters:
"sandboxtool -m scanandanalyze -t  -u  -p
A real life sample:
sandboxtool -m scanandanalyze -t contoso -c admin@contoso.onmicrosoft.com -s mysecret
"
This WILL generate an error.
ALSO, most people tend to execute the tool using "dot-sourcing" to ensure all the variables (scope) is INCLUDED in the scope of the current PowerShell session, so I'll add "." to the front of the sample command as well, and a fake PowerShell prompt as well...
The CORRECT verbiage & sample should look like this:
"sandboxtool -m scanandanalyze -t  -u  -p
A real life sample:
PS>.\sandboxtool.exe -m scanandanalyze -t contoso -u admin@contoso.onmicrosoft.com -p mypassword
"
Cheers - Mark Vogt

Thx for reporting. I've fixed the sample commandline.

authors: jansenbe markvogt

repo: SharePoint/PnP-Tools


text:
Full set of Fabric icons not available

Category

[ ] Question
[x] Bug
[ ] Enhancement

Expected or Desired Behavior
Icon from Fabric set should be displayed
Observed Behavior
Icon from Fabric set is not displayed
Steps to Reproduce
Create New list, enter the fabric icon set icon names in the Title column and apply the following formatting
{
    "$schema": "http://columnformatting.sharepointpnp.com/columnFormattingSchema.json",
    "debugMode": true,
    "elmType": "div",
    "children": [
        {
            "elmType": "span",
            "style": {
                "float": "right",
                "font-size": "200%",
                "display": "inline-block",
                "padding": "0 4px"
            },
            "attributes": {
                "iconName": "@currentField"
            }
        },
        {
            "elmType": "span",
            "txtContent": "@currentField"
        }
    ]
}

Some icons are displayed, some are not - it doesn't look like SharePoint Online has the full set of Fabric icons available.
Some of the icons which are not displayed (out of the 1435 icons, about half don't display)

"iconName": "@currentField" is it a typo?  You should be giving a iconName not the @currentfield.

No... the title field itself contains the icon name in this test to show the error in action...

This looks like it has been fixed with recent updates, all the icons now appear.

authors: RawkBob sohailmerchant

repo: SharePoint/sp-dev-column-formatting


text:
Intermittent external dependency loading issues

Category

[ ] Question
[ ] Typo
[X] Bug
[ ] Additional article idea

Expected or Desired Behavior
When creating a custom JavaScript library to be referenced by an SPFx solution (client side web parts and application customizers etc) I expect that I can reference @microsoft/sp-* modules and therefore be able to create shared code to optimize performance and payload of our SPFx solutions.
Observed Behavior
Adding @microsoft/sp-* npm packages to an external lib and referencing them as externals in the webpack config and then referencing this library in an SPFx project (as external) works in the Workbench, however when deploying the solution to SharePoint the following error is shown when it's trying to load dependencies for the external library:
GET https://relative-path.invalid/@microsoft/sp-loader net::ERR_NAME_NOT_RESOLVED
The define statement in my library looks like this:
define("myawesome-lib", ["@microsoft/sp-loader","@microsoft/sp-http"], function(__WEBPACK_EXTERNAL_MODULE_6__, __WEBPACK_EXTERNAL_MODULE_10__) { return /******/ (function(modules) { // webpackBootstrap

The error is not always shown, it can sometimes be on an application customizer and sometimes on one or more client side web parts on the page. Cleaning the cache/restarting browser causes it either to work or other components fail to load on next reload.
Steps to Reproduce
Create a new npm library and use and reference any @microsoft/sp-* package as external in the library. Then use this library, as external, in your SPFx project and try to add one or more web parts on a page. As I stated, it does not always happen, but if you want to dig further into a "working" example I can do that off-Github.

Guys,
Contributing my two cents.
We did experience issues with loading externals. They were very intermittent. As per our investigation, it was the externals.js file that was experiencing issues with loading external resources. What we did not understand is that SPComponentloader.loadScript('') worked well and it also has a promise so that other scripts can be loaded in order.
We thought, externals.js and SPComponentLoaded are one and the same. However, we stopped using externals.js and were using SPComponentloaded.loadCSS and loadScript for all our external resources.
Thx

Did you see this get fixed @wictorwilen ? Comment from last year implies a fix was coming in a few weeks which has long since passed...

authors: andrewconnell ravinleague wictorwilen

repo: SharePoint/sp-dev-docs


text:
🐞 Broken package-solution for Application customiser extension - case-sensitive-os

Category

[ ] Question
[ ] Typo
[x] Bug
[ ] Additional article idea

Expected or Desired Behavior
Create a development package of an application customizer that loads sources from localhost. This worked in the past for web parts and extensions.
Observed Behavior
When creating a new application customizer in SPFx 1.9.1 and run development to create a package the following error is shown.

Could not find Element Manifest: sharepoint/assets/clientsideinstance.xml

This is strange because the 'clientsideinstance.xml' exists in the folder.

In my case, it is explainable because my file system is case sensitive and the reference in not CamelCased.

Intermediate Fix
Changing the assets to CamelCase in the Element manifest.

Package solution works then without any issue.
Steps to Reproduce
Create a new application customizer and run:

gulp build
gulp bundle
gulp package-solution

or as a production build.

Good catch... confirmed. I can dupe this locally as well.

authors: StfBauer andrewconnell


text:
New control - Maps and also adding "ExtensionContext" to PeoplePicker and List Cntrol

Q
A

Bug fix?
[ ]

New feature?
[X ]

New sample?
[X ]

Related issues?
NA

What's in this Pull Request?
1. Added a new control called "Maps" as a response to #14

The current version of the submitted PR, accepts co-ordinates (latitude and longitude) as properties and displays OpenStreetMap for the co-ordinates.
The plan is to add "city search" in the upcoming weeks and use Google's geocode service to get co-ordinates for the entered city. This will need API key (which is free only for some queries and after that would need billing enabled for premium services).

Default Maps control (with co-ordinates set to London)

Maps control with search

2. Added "ExtensionContext" reference in ListPicker and PeoplePicker controls.

There are times when we would need to use these controls in SPFx extensions as well. Hence I have added the reference to "ExtensionContext" in these controls and the context in these controls can now be of the type "WebPartContext" or "ExtensionContext".

context: WebPartContext | ExtensionContext;
Sharing is caring

Codecov Report

Merging #186 into dev will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              dev     #186   +/-   ##
=======================================
  Coverage   80.63%   80.63%
=======================================
  Files          10       10
  Lines         346      346
  Branches       71       78    +7
=======================================
  Hits          279      279
  Misses         44       44
  Partials       23       23

Impacted Files
Coverage Δ

src/loc/en-us.ts
100% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

Thanks @anoopt, your map control has been merged to the DEV branch and will be available in version 1.11.0.
I have also applied a couple of code changes for consistency, but also got rid of the Bing API.

Thank you @estruyf for the code update and consistency. TIL we can get the co-ordinates using "https://nominatim.openstreetmap.org".

source: gharchive/pull-request

authors: anoopt codecov-io estruyf

repo: SharePoint/sp-dev-fx-controls-react


text:
add react-send-document

Q
A

Bug fix?
no

New feature?
no

New sample?
yes

Related issues?
no

What's in this Pull Request?

Please describe the changes in this PR. Sample description or details around bugs which are being fixed.
I want to add a new sample. This sample shows how to create Custom Dialogs using @microsoft/sp-dialog package in the context of Command View Set and send selected document with e-mail. This sample using @pnp/sp and Microsoft Graph API.

thx @serdarketenci, appreciated.

authors: VesaJuvonen serdarketenci

repo: SharePoint/sp-dev-fx-extensions


text:
Update to 1.4.1 Framework + French translation

Q
A

Bug fix?
no

New feature?
yes

New sample?
no

What's in this Pull Request?
Update to 1.4.1 framework
French translation
Thanks,
PooLP

thx @PooLP, would suggest to include your own name in the GitHub profile so that we can give you credits in our monthly summary - see for example Feb 2018 as an example - Obviously, you can absolutely stay anonymous as well, if needed.

ok thank @VesaJuvonen. I would do the next time on a larger updates or a new sample.

authors: PooLP VesaJuvonen

repo: SharePoint/sp-dev-fx-webparts

license: mit

license_source: bigquery


text:
Gulp Serve error when run isolated tiles AND starter kit master:

I was interested in customizing the tiles so I made some changes to the tile scss file. Mainly I wanted color and smaller tiles. I would suggest making the icon naming easier but that is out of my pay grade. I had an older isolated tiles file one of @bcameron1231 helped me with but I get an error when I try run gulp serve. Here is my tile dilemma: https://sharepoint.stackexchange.com/questions/273918/running-gulp-serve-throws-error-error-json-validation-failed

Something is wrong with my environment. I am getting the same errors on other webparts.

repo: SharePoint/sp-starter-kit


text:
Update link to Castle.

The old link says that "Castle has moved to castle.xyz"

Not sure why I never accepted this pr, but Castle is no longer mentioned.

authors: MichaelHinrichs Sheepolution

repo: Sheepolution/how-to-love


text:
Exporting Date-Times is wrong

i am facing date time issue
I have try this code xlsx js
let wb = XLSX.utils.book_new();
let ws = XLSX.ws = XLSX.utils.json_to_sheet(exportXLSXData, {dateNF: 'mmm dd, yyyy hh:mm', cellDates: true });
/*var ws = XLSX.utils.json_to_sheet(exportdata, {header: ["string","string", "number","date","string","string","string","string","string","string","string","string",], cellDates: true}); */
// Headers
ws['A1'].v = "Issue Key";
ws['B1'].v = "Summary";
ws['C1'].v = "Time Spent (Hours)";
ws['D1'].v = "Date";
ws['E1'].v = "Work Description";
ws['F1'].v = "Task Type";
ws['G1'].v = "User";
ws['H1'].v = "Account";
ws['I1'].v = "Parent Issue Key";
ws['J1'].v = "Issue Type";
ws['K1'].v = "Issue Status";
ws['L1'].v = "Issue Priority";
ws['M1'].v = "Issue Reporter";
ws['N1'].v = "Project Key";
ws['O1'].v = "Project Name";
ws['P1'].v = "Component";
ws['Q1'].v = "All Components";
ws['R1'].v = "Fix Version";
ws['S1'].v = "All Fix versions";
for (var i = 0; i < exportXLSXData.length; ++i) {
ws[D${i + 2}].z = 'mmm dd, yyyy hh:mm';
ws[D${i + 2}].t= 'd';
}
ws['!cols'] = wscolls;
ws['!rows'] = allRows;console.log(ws)
XLSX.utils.book_append_sheet(wb, ws, sheetNames);
XLSX.writeFile(wb,fileName + EXCEL_EXTENSION);
any bdy can help me ?
I have add utc date
"Mar 10, 2020 08:00"
the output excels file date i have found wrong?
Mar 10, 2020 07:59

Try XLSX.writeFile(wb,fileName + EXCEL_EXTENSION, { cellDates: true })
https://github.com/SheetJS/sheetjs#data-types

Type d is the Date type, generated only when the option cellDates is passed.

cellDates param isn't documented clearly enough in my opinion.
The code should give some kind of warning atleast when date type is being exported without cellDates param.

https://bugs.chromium.org/p/v8/issues/detail?id=7863 V8 bug.  SheetJS has to work around it.
Closing in favor of https://github.com/SheetJS/sheetjs/issues/1565

authors: Metuuu reviewher vinodjoshi11

repo: SheetJS/sheetjs


text:
Getting the right data and temporal changes

So there are issues with the data we are currently using.

It is for the VC of SW Yorkshire and Shef is right at the bottom of this
It is restricted to 2005-2010

So I have updated the code to do a better job (see the get_NBN_data script for details)
I'm still running the code but will add the resulting data file in a PR tomorrow
I also made some progress with the Temporal groups script and organised it into its own folder

Okay the new data is in but the file is pretty huge which might slow down everyone's github if it gets moved around. feel free to delete it and share by other means if it becomes an issue.

Thanks Tom. Will see how the file size affects people and decide on action accordingly. Cheers for sorting out!

authors: AugustT annakrystalli


text:
单文件组件

src/guide/single-file-component.md

Closed due to #10.

authors: ShenQingchuan syue-dev

repo: ShenQingchuan/docs-next


text:
docker gid can be different to host

Hi,
While I've had this working ok, a recent reboot of my host ended with the host having a different gid for the docker group (233) than that created in the container (999), so I had to resort to chgrp 999 /var/run/docker.sock on my host so that Jenkins has permission to access the socket.
I've tried using the 'group_add: docker' option in my docker-compose file, but this doesn't seem to change the gid of the docker group in the running container. Maybe because the group is already created in the container?
How do others cope with this?
Alex.

I was under the impression that groups and everything would already be setup inside the container. However, I have yet to successfully complete a docker job with this container. Maybe if we were able to pass the gid on the host to the container as an argument?

Hi guys,
Truly sorry for late response. I've had no time to investigate it at the start and then forget about it.
The fact that the GID of the docker group changed after the restart seems pretty weird to me. Once the group/user is created in the system, they are persistent and their GID/UID shall not change after rebooting.
Different docker group IDs shall be solvable either via the --group-add docker parameter when using the run command or adding group_add: \n - docker to the docker-compose. Just make sure your docker socket is set to docker group ls -la /var/run/docker.sock.
Please, take a look at the https://github.com/jenkinsci/docker/issues/263. This could add you some info.

I was having this issue on a BusyBox based VM. A BusyBox VM's docker GID is something like 99, but your Docker image's GID is 999. I haven't figured out a way to change this at build time or run time, and docker builds won't complete without access to the docker socket. My next step is to move from a BusyBox based VM to a Debian based VM. Maybe that will help? 🤷♂

authors: Shimmi ajtucker colonelpopcorn

repo: Shimmi/docker-jenkins


text:
Update service configs to remove the check of bringing swarm up on ingress network if docker version is 1.13, since none of the services will not run on docker 1.13

https://github.com/Shippable/pm/issues/10352

this is done, closing

repo: Shippable/admiral


text:
To Do list: add & remove

Remove all hardcoded items from the tasks array.
Create a new JavaScript file for the new functionality.
Implemented a function for adding a new task.
Implemented a function for deleting a task.
Implemented a function for editing task descriptions.
Implemented a function to update the index of elements after deleting a task so they represent the current list order and are unique(i.e. if you're deleting the first task index 1 from the list, the index of the next task(2) should be set to 1)...
All changes to the To Do List are saved in local storage.

Hi @ShiroYaksha90
While you made a great effort in this project, unfortunately, I cannot proceed to review your code.

Invalid Code Review Request
⚠ Please make sure you added the section Future Features, including 1-3 potential features to be added.
Your Code Review Request will be marked as invalid in your Dashboard, so please submit a new one once you are ready 🙏
Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me in your question so I can receive the notification.
Please, do not open a new Pull Request for re-reviews. You should use the same Pull Request submitted for the first review, either valid or invalid unless it is requested otherwise.

Invalid Code Review Request does not count into the code reviews limit.


text:
Speed up with async

Potentiall can use async to make this code run 'faster'

Not using async.


text:
verify required theme files before dev server initialization

WHY are these changes introduced?
Adds validation to ensure required theme files exist before initializing the dev server session. This helps catch issues with incomplete or corrupted themes that could cause the dev server to fail when initializing the preview session.

https://github.com/Shopify/cli/issues/4735
https://github.com/Shopify/develop-advanced-edits/issues/406

WHAT is this pull request doing?

Adds a new verifyRequiredFilesExist function that checks for essential theme files (layout/theme.liquid and config/settings_schema.json)
Implements a retry mechanism with a 3-second delay if files are not found on first attempt
Automatically deletes invalid themes and prompts users to recreate them

How to test your changes?

Create a theme missing either layout/theme.liquid or config/settings_schema.json on your shop (more instructions below if needed)
Run the theme dev or app dev with the theme flag, and specify the theme created above. Verify it fails with appropriate error message
Delete the created theme
Create a valid theme with all required files
Verify dev server starts successfully

Measuring impact

[x] n/a - this doesn't need measurement, e.g. a linting rule or a bug-fix

Checklist

[x] I've considered possible cross-platform impacts (Mac, Linux, Windows)
[x] I've considered possible documentation changes

/snapit

pivot: only show this when essential is missing to better determine the cause

repo: Shopify/cli


text:
Setup Jest for unit testing and add a few tests.

fixes #12

Closing since we shipped https://github.com/Shopify/javascript-utilities/pull/34 which adds jest.

authors: andrewlo nimzco

repo: Shopify/javascript-utilities


text:
Create xml in to_xml if options present

to_xml should return formatted xml if options is present. Worked on in conjunction with @vignesh-vs-in.
Please review, @jahfer @stephenminded

Fixed the ruby hashing format. Can we get a go ahead for this, if everything else is looking fine?

One comment, after that 🚢

don't know much about the XML path of things, but LGTM 👍

Am I reading the code correctly in that it is serializing every money object under a  tag now?

Am I reading the code correctly in that it is serializing every money object under a  tag now?

If the builder and root options are provided, it will serialize the money object under the tag specified by root. Otherwise we'll serialize the money value as a strait up string with no tag. I'm unsure if rails provides these options by default when serializing to XML, however.

Rails expects a serialized xml tag when it provides the serialization options. It does provide the options when serializing a model.

authors: cplehm jahfer jeromecornet stephenminded vignesh-vs-in

repo: Shopify/money


text:
[react-testing] improved performance by making descendants calculations lazy for element children

Description
Fixes (issue #)
N/A

Type of change
I've been looking into a flaky slow test and doing some profiling and noticed that one of the significant bottlenecks is found in react-testing specifically when  attempting to flatten a react fiber linked list into an array of elements. It seems like determining the descendants of each child is an exponential time algorithm. This has a pretty big impact on tests with big fiber trees. I've changed the descendants to be lazily evaluated and derived from the children though grabbing the root descendants still goes through the entire tree which is slow. Additionally I hand optimized some code, for example the spread operator when compiled with typescript to es5 into a spread call seems to be a rather big culprit of performance issues in this computational heavy process.
Performing the above optimization made a significant improvement to the test in question (which had a really big fiber tree ~80 in depth) :
Before:

After:

For other tests with smaller fiber trees the improvement is a more modest 10-20%.
Before:

After:

This should improve unit tests times across the board.
Note: A change in descendants order is a breaking one. I sketched out the order in this PR and it seems to be the same as before, but something worth verifying for the reviewers.

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

Checklist

[ ] I have added a changelog entry, prefixed by the type of change noted above (Documentation fix and Test update does not need a changelog as we do not publish new version)

Things are looking stable. I've ran all tsx tests in web and here are the results:
Before:

After:

The failures are the same for both and unrelated to this change, the run on the main branch has an additional timeout result which is why it has one more failure.
One thing I've noticed is that there's a test Globe.test.tsx that's consistently passing on main and has intermittent failures on this branch. It has something to do with timing as the behavior should be the same between the two branches. I've added an artificial delay to the fiberToElement function and sure enough got the tests to consistently pass. Globe.tsx has a setTimeout(fn, 0) to flip a loading state for whatever reason so I think using jest fake timers and advancing that timer manually should fix the issue. Other then that, it's looking good.

@melnikov-s HUGE!

If you like you could pull the new er optimization into another PR and we can test that one with a beta too, and get the original one shipped ASAP

Thanks, https://github.com/Shopify/quilt/pull/1821

@melnikov-s could you please add a changelog entry? And then feel free to merge and I can cut a new release.

Will do, is this a breaking change that requires a major version bump? I'm noticing that Element is exported from the module and I've changed it's constructor signature.

@melnikov-s I don't think its intended that folks manually construct elements, rather they can just use Element for type annotations in stuff like custom matchers if they need to, so my bias would be towards not doing a major bump
that said it is technically correct to do a major one I suppose

authors: TheMallen atesgoral melnikov-s

repo: Shopify/quilt


text:
Add watched_files_dynamic_registration to global state

Motivation
Work towards Shopify/ruby-lsp-rails#326. ruby-lsp-rails wants to watch for file changes to **/structure.sql. This allows it to check if the client supports this functionality before trying to send the request.
It makes sense to add docs on how/why you might make use of this option in an addon, but I'll defer that until after I've actually written some functioning code.
Implementation
Move the options extraction for this into the global state.
Automated Tests
Add a few variants that a client might send.
Manual Tests
Edit a ruby file and observe that the file watcher is still being registered, i.e. that the index is being updated.

Thanks for the merge. What would be the steps to make use of this in ruby-lsp-rails? I believe I would need to wait for a 0.17 release and it to be adapted there, or is a minimal version requirement bump to a theoretical 0.16.4 acceptable?

repo: Shopify/ruby-lsp


text:
Illustrate which tests ExpectationsTestRunner is running

Motivation
As a new developer on ruby-lsp, I found a little difficult to understand which tests were running due to the metaprogramming in use.
Implementation

I've added an option to use the minitest spec runner.
I've tried to distinguish the test name from the fixture file in the output.

Example:
% SPEC_REPORTER=1 bin/test test/requests/document_highlight_expectations_test.rb
Started with run options --seed 60796

DocumentHighlightExpectationsTest
  test_document_highlight__vcall_invocation                       PASS (0.00s)
  test_document_highlight__until                                  PASS (0.00s)
  test_document_highlight__job                                    PASS (0.00s)
  test_document_highlight__if_elsif_else                          PASS (0.00s)
  test_document_highlight__model_action_text                      PASS (0.00s)
  test_document_highlight__lambdas                                PASS (0.00s)
  test_document_highlight__case_in                                PASS (0.00s)
  test_document_highlight__defs                                   PASS (0.00s)
  test_document_highlight__const                                  PASS (0.00s)
  test_document_highlight__call_invocation_with_variable_receiver_and_arguments PASS (0.00s)
  test_document_highlight__if                                     PASS (0.00s)
  test_document_highlight__module_and_reference                   PASS (0.00s)
  test_document_highlight__call_invocation                        PASS (0.00s)
  test_document_highlight__until_mod                              PASS (0.00s)
  test_document_highlight__fcall_invocation_variable_arguments    PASS (0.00s)
  test_document_highlight__command_nested_multiline_args          PASS (0.00s)
  test_document_highlight__nested_bare_rescue                     PASS (0.00s)
  test_document_highlight__if_inside_else                         PASS (0.00s)
  test_document_highlight__call_multiline_args                    PASS (0.00s)
  test_document_highlight__var_aref_variable                      PASS (0.00s)
  test_document_highlight__command_invocation                     PASS (0.00s)
  test_document_highlight__comments                               PASS (0.00s)
  test_document_highlight__do_blocks                              PASS (0.00s)
  test_document_highlight__argument_forwarding                    PASS (0.00s)
  test_document_highlight__model_active_storage                   PASS (0.00s)
  test_document_highlight__if_mod                                 PASS (0.00s)
  test_document_highlight__def_require_name_parameter             PASS (0.00s)
  test_document_highlight__shadowed_block_arg                     PASS (0.00s)
  test_document_highlight__model                                  PASS (0.00s)
  test_document_highlight__call_symbol_call                       PASS (0.00s)
  test_document_highlight__command_multiline_args                 PASS (0.00s)
  test_document_highlight__def_oneline                            PASS (0.00s)
  test_document_highlight__local_vars_and_params                  PASS (0.00s)
  test_document_highlight__command_call                           PASS (0.00s)
  test_document_highlight__aref_variable                          PASS (0.00s)
  test_document_highlight__class_declaration                      PASS (0.00s)
  test_document_highlight__aref_call_aref_assign                  PASS (0.00s)
  test_document_highlight__call_chained                           PASS (0.00s)
  test_document_highlight__for                                    PASS (0.00s)
  test_document_highlight__full_name_highlight                    PASS (0.00s)
  test_document_highlight__source_comment                         PASS (0.00s)
  test_document_highlight__sclass                                 PASS (0.00s)
  test_document_highlight__single_comment                         PASS (0.00s)
  test_document_highlight__command_requires                       PASS (0.00s)
  test_document_highlight__routes                                 PASS (0.00s)
  test_document_highlight__def_bad_formatting                     PASS (0.00s)
  test_document_highlight__field_assignment                       PASS (0.00s)
  test_document_highlight__ivar                                   PASS (0.00s)
  test_document_highlight__hash_literal_oneline                   PASS (0.00s)
  test_document_highlight__hash_safe_access                       PASS (0.00s)
  test_document_highlight__class_and_reference                    PASS (0.00s)
  test_document_highlight__numbered_parameters                    PASS (0.00s)
  test_document_highlight__ambiguous_local_variables              PASS (0.00s)
  test_document_highlight__fcall_chained_invocation               PASS (0.00s)
  test_document_highlight__array_literal_oneline                  PASS (0.00s)
  test_document_highlight__class_declaration_with_superclass      PASS (0.00s)
  test_document_highlight__defs_multiline_params                  PASS (0.00s)
  test_document_highlight__pattern_matching                       PASS (0.00s)
  test_document_highlight__def                                    PASS (0.00s)
  test_document_highlight__ensure                                 PASS (0.00s)
  test_document_highlight__model_active_record_constant           PASS (0.00s)
  test_document_highlight__method_params                          PASS (0.00s)
  test_document_highlight__module_declaration                     PASS (0.00s)
  test_document_highlight__multiline_block                        PASS (0.00s)
  test_document_highlight__one_line_nesting                       PASS (0.00s)
  test_document_highlight__if_elsif_else_empty                    PASS (0.00s)
  test_document_highlight__string_concat                          PASS (0.00s)
  test_document_highlight__single_line_lambda                     PASS (0.00s)
  test_document_highlight__var_field_variable                     PASS (0.00s)
  test_document_highlight__begin_rescue_ensure                    PASS (0.00s)
  test_document_highlight__multiline_invocation                   PASS (0.00s)
  test_document_highlight__special_ruby_methods                   PASS (0.00s)
  test_document_highlight__def_and_reference                      PASS (0.00s)
  test_document_highlight__nested_invocation                      PASS (0.00s)
  test_document_highlight__nameless_keyword_rest                  PASS (0.00s)
  test_document_highlight__heredoc                                PASS (0.00s)
  test_document_highlight__while_mod                              PASS (0.00s)
  test_document_highlight__global_variable                        PASS (0.00s)
  test_document_highlight__def_multiline_params                   PASS (0.00s)
  test_document_highlight__lambda_braces_oneline                  PASS (0.00s)
  test_document_highlight__fcall_invocation                       PASS (0.00s)
  test_document_highlight__ambiguous_constants                    PASS (0.00s)
  test_document_highlight__bare_rescue                            PASS (0.00s)
  test_document_highlight__unless                                 PASS (0.00s)
  test_document_highlight__hash_literal                           PASS (0.00s)
  test_document_highlight__case_when                              PASS (0.00s)
  test_document_highlight__local_variables                        PASS (0.00s)
  test_document_highlight__class_declaration_nested               PASS (0.00s)
  test_document_highlight__command_invocation_variable            PASS (0.00s)
  test_document_highlight__call_then_aref_assignment              PASS (0.00s)
  test_document_highlight__fcall_multiline_args                   PASS (0.00s)
  test_document_highlight__call_invocation_with_variable_receiver PASS (0.00s)
  test_document_highlight__nested_invocation_no_parenthesis       PASS (0.00s)
  test_document_highlight__def_rescue                             PASS (0.00s)
  test_document_highlight__aref_field                             PASS (0.00s)
  test_document_highlight__ambiguous_class_variables              PASS (0.00s)
  test_document_highlight__attr_accessor                          PASS (0.00s)
  test_document_highlight__multiline_arrays                       PASS (0.00s)
  test_document_highlight__while                                  PASS (0.00s)
  test_document_highlight__multi_assignment                       PASS (0.00s)
  test_document_highlight__aref_on_method_call                    PASS (0.00s)
  test_document_highlight__call_nested_multiline_args             PASS (0.00s)
  test_document_highlight__nested_block_arguments                 PASS (0.00s)
  test_document_highlight__controller                             PASS (0.00s)
  test_document_highlight__ambiguous_instance_variables           PASS (0.00s)
  test_document_highlight__def_endless                            PASS (0.00s)
  test_document_highlight__double_aref_with_assignment            PASS (0.00s)
  test_document_highlight__string_multibytes                      PASS (0.00s)

Finished in 0.02906s
108 tests, 12 assertions, 0 failures, 0 errors, 0 skips

Automated Tests

Manual Tests

WDYT @vinistock ?


text:
Dev Server, Windows resolves incorrect assets directory

Problem
When using an asset_url filter, windows resolves the ./snippets/ directory, rather than the ./assets/static, /assets/images, /assets/fonts (etc) directories.
Powershell error:

Liquid and Showing the assets in all the expected places:

Replication steps

Load a theme on a Windows PC.
Add any file to any of the expected working assets directories.
Load any appropriate .liquid file
Add your {{ 'file.extension' | asset_url }} tag to the liquid
Attempt a yarn start, watch webpack build error make ya feel bad
Pour a coffee

More Information
Compiles fine when doing a yarn deploy, only the dev server seems to have the issue.
Works fine if I put an asset into my ./snippets/ directory, works as if it were in the assets directory.
Example where I've added "testFile.svg" to my snippets directory, then used {{ 'testFile.svg' | asset_url }} in my liquid, no compilation errors are thrown.

Attempted SVG and PNG, same issues, also tried .txt but received a "loader needed" error for webpack, probably to be expected for an obscure file type to have in a theme.
OS: Windows 10
slate-tools: 1.0.0-beta.6

I can confirm this in OSX as well, and can confirm the single space issue that @floatingdino mentioned also, which will cause to resolve to the CDN.
For me, I tried using an {{ 'test.svg' | asset_url }} in a section file.  It tries to resolve to that same /sections folder, so for now the only way for this to work for me is to keep that image in the /sections folder.

authors: YourWishes kevmon

repo: Shopify/slate


text:
Remove mentions of Timber theme from docs

Describe the bug
The docs currently say "New will create theme using Shopify Timber" but this is no longer true.
(and Timber is deprecated).

I have an open PR for updating documentation and I just removed Timber from it. Feel free to take a look and let me know if I missed it anywhere else.

repo: Shopify/themekit


text:
add default type for user-land types

align with BaseSource/BaseFilter

Please describe after it merged.
The source implementation will be easy?

For users who use class MySource extends BaseSource { (no param). They are needed to write OnEventArguments<Record<string, unknown>>. Users can use OnEventArguments (without type param) instead after merged. Removing asymmetricity.
It's good alternative to remove default Param from BaseSource/BaseFilter because user should be interested in Param because param() { ... } implementation is now required.

The current users who is not so familiar with TS can easily update to this version.

Param is required.
So the default Param should be removed?
Please describe cons and pros with examples.
I need to decide the choices.

Okay, thanks.
Asymmetric of BaseSource/BaseFilter vs ...Arguments about Param necessity is wrongly shipped by my PR (https://github.com/Shougo/ddc.vim/pull/53).
1st option: no change
class MySource extends BaseSource {
  // {} is needed
  async gatherCandidates(args: GatherCandidatesArguments<{}>) {
    // ...
    return [];
  }
  params() { return {} }
}

2nd option (this PR):
class MySource extends BaseSource {
  // {} is not needed
  async gatherCandidates(args: GatherCandidatesArguments) {
    // ...
    return [];
  }
  params() { return {} }
}

3rd option (Param is required for BaseSource/BaseFilter):
// {} is necessary here too
class MySource extends BaseSource<{}> {
  gatherCandidates(args: GatherCandidatesArguments<{}>) {
    // ...
    return [];
  }
  params() { return {} }
}

3rd option (Param is required for BaseSource/BaseFilter):

I think it is better.

Please fix CI errors.

OK. Merged.

authors: LumaKernel Shougo


text:
[Question] Is there a way to create a file in the currently selected directory?

Is there a way to create a file in the currently selected directory?
For example, in the following case

When the cursor is in the vim directory and you create a new file, how do you create a file in the vim directory by just typing the filename, not the full path?

It needs some work.

Please update ddu-kind-file.

Thank you. confirmed.
However, I am worried that the tree display is reset every time I add a file.
Resume is set as follows.
Ddu -name=filer -ui=filer -resume -source-option-columns=filename file<CR>

Resume does not work for the feature.
Resume means restore the previous state.
But you have changed the directory state.

I have updated ddu-ui-filer for it.

Thank you. confirmed.

authors: Shougo nabezokodaikon

repo: Shougo/ddu-ui-filer


text:
Absolute Path of Command is Required on MacOS when Terminal Mode is Off

Describe the bug:
On MacOS systems, (as mentioned in the bottom of the README) an absolute path is required to run commands when terminal mode is off.
To Reproduce:
Steps to reproduce the behavior:

Set the command to use a non built-in command, such as "node ${path.join(__dirname, './tester.js')} $_URL_" (See how it uses node?)
Set terminal to false in the configuration.
Register the protocol.
Go to the protocol in a browser.
It will error and say that the command does not exist.

Expected behavior:
It should run the command like a user is doing so.

Please fix requested changes

This is fixed and released.


text:
nasbench201_dict.npy文件询问。

您好，请问这个nasbench201_dict.npy文件是什么作用，如果我用您的方法在新的数据集上跑，这个文件需要修改什么地方。麻烦您了。

您好，由于NAS-Bench-201官方提供的文件读取很慢，这个文件相当于把官方文件信息（主要包括搜索空间的模型结构和对应的精度，从而易于计算排序一致性）提取出来了，读取速度非常快，方便计算排序一致性。如果应用我们方法到新数据集，应该需要根据新数据集提取一个新的类似文件。

感谢您的回复，那我应该怎么得到一个相似的文件呀？

需要收集你自己定义的搜索空间中的模型结构在新数据集的精度和结构信息，存成字典格式，最后保存为npy文件即可

好的，麻烦您了

10/24 11:14:54 AM model_id: 0  gene: [4, 2, 1, 2, 1, 1]  loss: 0.771  top1: 73.853  target: 85.860
10/24 11:14:54 AM Evaluated: 00001      Waiting: 15624  Current Kendall's Tau: nan
10/24 11:15:43 AM model_id: 100  gene: [3, 3, 0, 3, 4, 1]  loss: 0.770  top1: 77.064  target: 92.130
10/24 11:15:43 AM Evaluated: 00101      Waiting: 15524  Current Kendall's Tau: 0.11989
10/24 11:16:31 AM model_id: 200  gene: [4, 2, 0, 4, 0, 4]  loss: 0.704  top1: 76.606  target: 86.970
10/24 11:16:31 AM Evaluated: 00201      Waiting: 15424  Current Kendall's Tau: 0.15659
10/24 11:17:18 AM model_id: 300  gene: [1, 2, 0, 4, 0, 2]  loss: 0.845  top1: 70.642  target: 89.470
10/24 11:17:18 AM Evaluated: 00301      Waiting: 15324  Current Kendall's Tau: 0.14902
10/24 11:18:04 AM model_id: 400  gene: [1, 4, 0, 3, 0, 3]  loss: 0.656  top1: 76.147  target: 92.230
10/24 11:18:04 AM Evaluated: 00401      Waiting: 15224  Current Kendall's Tau: 0.13731
10/24 11:18:51 AM model_id: 500  gene: [0, 0, 4, 3, 3, 2]  loss: 0.688  top1: 78.899  target: 92.030
10/24 11:18:51 AM Evaluated: 00501      Waiting: 15124  Current Kendall's Tau: 0.12187
10/24 11:19:37 AM model_id: 600  gene: [4, 4, 2, 3, 3, 3]  loss: 0.765  top1: 68.807  target: 91.860
10/24 11:19:37 AM Evaluated: 00601      Waiting: 15024  Current Kendall's Tau: 0.11459
10/24 11:20:25 AM model_id: 700  gene: [1, 0, 1, 1, 3, 0]  loss: 0.677  top1: 73.853  target: 91.940
10/24 11:20:25 AM Evaluated: 00701      Waiting: 14924  Current Kendall's Tau: 0.10816
10/24 11:21:13 AM model_id: 800  gene: [4, 0, 2, 3, 2, 1]  loss: 0.882  top1: 61.927  target: 91.630
10/24 11:21:13 AM Evaluated: 00801      Waiting: 14824  Current Kendall's Tau: 0.10469
10/24 11:21:59 AM model_id: 900  gene: [1, 0, 2, 1, 4, 2]  loss: 0.693  top1: 72.477  target: 87.860
10/24 11:21:59 AM Evaluated: 00901      Waiting: 14724  Current Kendall's Tau: 0.10771
10/24 11:22:46 AM model_id: 1000  gene: [1, 3, 2, 0, 1, 3]  loss: 0.721  top1: 74.312  target: 93.550
10/24 11:22:46 AM Evaluated: 01001      Waiting: 14624  Current Kendall's Tau: 0.11871
10/24 11:23:32 AM model_id: 1100  gene: [1, 2, 2, 0, 2, 4]  loss: 1.434  top1: 53.211  target: 89.940
10/24 11:23:32 AM Evaluated: 01101      Waiting: 14524  Current Kendall's Tau: 0.10808
10/24 11:24:19 AM model_id: 1200  gene: [1, 2, 3, 4, 1, 4]  loss: 0.733  top1: 73.394  target: 86.830
10/24 11:24:19 AM Evaluated: 01201      Waiting: 14424  Current Kendall's Tau: 0.09972
10/24 11:25:05 AM model_id: 1300  gene: [3, 0, 1, 4, 3, 3]  loss: 0.671  top1: 77.982  target: 92.570
10/24 11:25:05 AM Evaluated: 01301      Waiting: 14324  Current Kendall's Tau: 0.10020
10/24 11:25:52 AM model_id: 1400  gene: [2, 2, 3, 2, 1, 4]  loss: 1.060  top1: 66.972  target: 91.630
10/24 11:25:52 AM Evaluated: 01401      Waiting: 14224  Current Kendall's Tau: 0.09779
10/24 11:26:38 AM model_id: 1500  gene: [4, 3, 3, 0, 0, 2]  loss: 1.133  top1: 52.294  target: 91.110
10/24 11:26:38 AM Evaluated: 01501      Waiting: 14124  Current Kendall's Tau: 0.09112
10/24 11:27:25 AM model_id: 1600  gene: [4, 1, 4, 4, 2, 0]  loss: 0.771  top1: 72.018  target: 81.800
10/24 11:27:25 AM Evaluated: 01601      Waiting: 14024  Current Kendall's Tau: 0.09653
10/24 11:28:12 AM model_id: 1700  gene: [0, 4, 0, 4, 2, 3]  loss: 0.718  top1: 72.018  target: 84.780
10/24 11:28:12 AM Evaluated: 01701      Waiting: 13924  Current Kendall's Tau: 0.09106
10/24 11:28:59 AM model_id: 1800  gene: [1, 1, 1, 3, 1, 4]  loss: 0.713  top1: 72.018  target: 79.830
10/24 11:28:59 AM Evaluated: 01801      Waiting: 13824  Current Kendall's Tau: 0.09038
10/24 11:29:47 AM model_id: 1900  gene: [2, 4, 3, 0, 1, 4]  loss: 0.785  top1: 72.477  target: 89.190
10/24 11:29:47 AM Evaluated: 01901      Waiting: 13724  Current Kendall's Tau: 0.08981
10/24 11:30:34 AM model_id: 2000  gene: [3, 3, 3, 3, 4, 0]  loss: 0.666  top1: 74.771  target: 91.860
10/24 11:30:34 AM Evaluated: 02001      Waiting: 13624  Current Kendall's Tau: 0.09015
10/24 11:31:20 AM model_id: 2100  gene: [4, 3, 2, 4, 2, 2]  loss: 0.797  top1: 69.725  target: 92.020
10/24 11:31:20 AM Evaluated: 02101      Waiting: 13524  Current Kendall's Tau: 0.08867
10/24 11:32:08 AM model_id: 2200  gene: [1, 3, 3, 1, 2, 0]  loss: 0.705  top1: 72.936  target: 89.480
10/24 11:32:08 AM Evaluated: 02201      Waiting: 13424  Current Kendall's Tau: 0.08638
10/24 11:32:55 AM model_id: 2300  gene: [1, 0, 4, 3, 0, 1]  loss: 0.654  top1: 77.982  target: 91.140
10/24 11:32:55 AM Evaluated: 02301      Waiting: 13324  Current Kendall's Tau: 0.07949
10/24 11:33:42 AM model_id: 2400  gene: [2, 1, 0, 1, 2, 2]  loss: 0.725  top1: 68.807  target: 90.410
10/24 11:33:42 AM Evaluated: 02401      Waiting: 13224  Current Kendall's Tau: 0.07608
10/24 11:34:29 AM model_id: 2500  gene: [3, 2, 4, 3, 3, 4]  loss: 0.815  top1: 70.183  target: 92.790
10/24 11:34:29 AM Evaluated: 02501      Waiting: 13124  Current Kendall's Tau: 0.07597
10/24 11:35:16 AM model_id: 2600  gene: [0, 1, 4, 3, 4, 3]  loss: 0.648  top1: 77.064  target: 92.020
10/24 11:35:16 AM Evaluated: 02601      Waiting: 13024  Current Kendall's Tau: 0.07965
10/24 11:36:06 AM model_id: 2700  gene: [2, 4, 3, 3, 1, 3]  loss: 0.745  top1: 73.853  target: 93.060
10/24 11:36:06 AM Evaluated: 02701      Waiting: 12924  Current Kendall's Tau: 0.07911
10/24 11:36:54 AM model_id: 2800  gene: [3, 4, 3, 1, 4, 4]  loss: 0.724  top1: 73.853  target: 89.390
10/24 11:36:54 AM Evaluated: 02801      Waiting: 12824  Current Kendall's Tau: 0.07573
10/24 11:37:41 AM model_id: 2900  gene: [3, 1, 0, 2, 2, 1]  loss: 0.815  top1: 67.890  target: 93.260
10/24 11:37:41 AM Evaluated: 02901      Waiting: 12724  Current Kendall's Tau: 0.07308
10/24 11:38:26 AM model_id: 3000  gene: [2, 1, 1, 0, 4, 0]  loss: 0.850  top1: 69.725  target: 86.610
10/24 11:38:26 AM Evaluated: 03001      Waiting: 12624  Current Kendall's Tau: 0.07078
10/24 11:39:13 AM model_id: 3100  gene: [1, 0, 4, 0, 4, 4]  loss: 0.750  top1: 73.394  target: 70.050
10/24 11:39:13 AM Evaluated: 03101      Waiting: 12524  Current Kendall's Tau: 0.07153
10/24 11:40:00 AM model_id: 3200  gene: [4, 3, 2, 3, 0, 4]  loss: 0.753  top1: 75.229  target: 91.430
10/24 11:40:00 AM Evaluated: 03201      Waiting: 12424  Current Kendall's Tau: 0.07038
10/24 11:40:47 AM model_id: 3300  gene: [1, 3, 2, 2, 2, 3]  loss: 0.824  top1: 71.560  target: 93.290
10/24 11:40:47 AM Evaluated: 03301      Waiting: 12324  Current Kendall's Tau: 0.07286
10/24 11:41:32 AM model_id: 3400  gene: [1, 2, 4, 2, 4, 2]  loss: 0.749  top1: 69.725  target: 89.310
10/24 11:41:32 AM Evaluated: 03401      Waiting: 12224  Current Kendall's Tau: 0.07427
10/24 11:42:19 AM model_id: 3500  gene: [3, 2, 2, 0, 0, 2]  loss: 1.166  top1: 56.881  target: 91.060
10/24 11:42:19 AM Evaluated: 03501      Waiting: 12124  Current Kendall's Tau: 0.07441
10/24 11:43:06 AM model_id: 3600  gene: [2, 3, 2, 4, 3, 1]  loss: 0.776  top1: 73.853  target: 92.270
10/24 11:43:06 AM Evaluated: 03601      Waiting: 12024  Current Kendall's Tau: 0.07166
10/24 11:43:53 AM model_id: 3700  gene: [4, 4, 1, 3, 2, 0]  loss: 0.733  top1: 74.312  target: 92.150
10/24 11:43:53 AM Evaluated: 03701      Waiting: 11924  Current Kendall's Tau: 0.07046
10/24 11:44:39 AM model_id: 3800  gene: [0, 4, 1, 1, 2, 4]  loss: 0.740  top1: 72.477  target: 77.990
10/24 11:44:39 AM Evaluated: 03801      Waiting: 11824  Current Kendall's Tau: 0.06975
10/24 11:45:27 AM model_id: 3900  gene: [3, 1, 1, 2, 1, 1]  loss: 0.668  top1: 74.312  target: 92.020
10/24 11:45:27 AM Evaluated: 03901      Waiting: 11724  Current Kendall's Tau: 0.06902
10/24 11:46:14 AM model_id: 4000  gene: [2, 0, 2, 3, 0, 3]  loss: 0.762  top1: 68.807  target: 92.520
10/24 11:46:14 AM Evaluated: 04001      Waiting: 11624  Current Kendall's Tau: 0.06981
10/24 11:47:01 AM model_id: 4100  gene: [0, 1, 2, 1, 0, 0]  loss: 0.552  top1: 79.817  target: 86.680
10/24 11:47:01 AM Evaluated: 04101      Waiting: 11524  Current Kendall's Tau: 0.07167
10/24 11:47:48 AM model_id: 4200  gene: [4, 1, 4, 0, 1, 0]  loss: 0.637  top1: 74.771  target: 75.600
10/24 11:47:48 AM Evaluated: 04201      Waiting: 11424  Current Kendall's Tau: 0.07331
10/24 11:48:34 AM model_id: 4300  gene: [0, 1, 2, 2, 2, 1]  loss: 0.671  top1: 76.606  target: 89.830
10/24 11:48:34 AM Evaluated: 04301      Waiting: 11324  Current Kendall's Tau: 0.07386
10/24 11:49:20 AM model_id: 4400  gene: [1, 1, 2, 3, 1, 1]  loss: 0.841  top1: 63.761  target: 88.350
10/24 11:49:20 AM Evaluated: 04401      Waiting: 11224  Current Kendall's Tau: 0.07334
10/24 11:50:07 AM model_id: 4500  gene: [2, 3, 0, 4, 2, 0]  loss: 0.737  top1: 70.183  target: 89.450
10/24 11:50:07 AM Evaluated: 04501      Waiting: 11124  Current Kendall's Tau: 0.07074
10/24 11:50:53 AM model_id: 4600  gene: [0, 4, 1, 4, 3, 4]  loss: 0.750  top1: 73.394  target: 69.810
10/24 11:50:53 AM Evaluated: 04601      Waiting: 11024  Current Kendall's Tau: 0.06807
10/24 11:51:41 AM model_id: 4700  gene: [4, 2, 0, 4, 0, 0]  loss: 0.637  top1: 74.771  target: 75.850
10/24 11:51:41 AM Evaluated: 04701      Waiting: 10924  Current Kendall's Tau: 0.06646
10/24 11:52:27 AM model_id: 4800  gene: [4, 3, 2, 1, 0, 3]  loss: 0.728  top1: 74.312  target: 93.590
10/24 11:52:27 AM Evaluated: 04801      Waiting: 10824  Current Kendall's Tau: 0.06567
10/24 11:53:15 AM model_id: 4900  gene: [3, 0, 1, 3, 4, 1]  loss: 0.716  top1: 74.312  target: 91.830
10/24 11:53:15 AM Evaluated: 04901      Waiting: 10724  Current Kendall's Tau: 0.06670
10/24 11:54:01 AM model_id: 5000  gene: [3, 3, 0, 4, 2, 3]  loss: 0.707  top1: 74.771  target: 93.440
10/24 11:54:01 AM Evaluated: 05001      Waiting: 10624  Current Kendall's Tau: 0.06783
10/24 11:54:49 AM model_id: 5100  gene: [0, 0, 3, 0, 2, 0]  loss: 1.193  top1: 55.046  target: 10.000
10/24 11:54:49 AM Evaluated: 05101      Waiting: 10524  Current Kendall's Tau: 0.06829
10/24 11:55:38 AM model_id: 5200  gene: [4, 1, 4, 4, 3, 1]  loss: 0.866  top1: 66.972  target: 73.030
10/24 11:55:38 AM Evaluated: 05201      Waiting: 10424  Current Kendall's Tau: 0.06708
10/24 11:56:28 AM model_id: 5300  gene: [2, 0, 4, 4, 1, 0]  loss: 0.655  top1: 76.147  target: 88.530
10/24 11:56:28 AM Evaluated: 05301      Waiting: 10324  Current Kendall's Tau: 0.06786
10/24 11:57:16 AM model_id: 5400  gene: [0, 1, 3, 1, 0, 0]  loss: 0.552  top1: 79.817  target: 86.630
10/24 11:57:16 AM Evaluated: 05401      Waiting: 10224  Current Kendall's Tau: 0.06756
10/24 11:58:01 AM model_id: 5500  gene: [3, 2, 2, 1, 1, 4]  loss: 0.702  top1: 74.312  target: 92.830
10/24 11:58:01 AM Evaluated: 05501      Waiting: 10124  Current Kendall's Tau: 0.06917
10/24 11:58:50 AM model_id: 5600  gene: [0, 1, 1, 3, 4, 2]  loss: 0.663  top1: 76.606  target: 92.370
10/24 11:58:50 AM Evaluated: 05601      Waiting: 10024  Current Kendall's Tau: 0.06749
10/24 11:59:35 AM model_id: 5700  gene: [4, 4, 0, 1, 1, 2]  loss: 0.803  top1: 68.349  target: 85.750
10/24 11:59:35 AM Evaluated: 05701      Waiting: 09924  Current Kendall's Tau: 0.06851
10/24 12:00:23 PM model_id: 5800  gene: [1, 0, 0, 4, 1, 3]  loss: 0.741  top1: 69.725  target: 79.630
10/24 12:00:23 PM Evaluated: 05801      Waiting: 09824  Current Kendall's Tau: 0.06763
10/24 12:01:11 PM model_id: 5900  gene: [3, 4, 0, 3, 4, 1]  loss: 0.639  top1: 79.358  target: 90.960
10/24 12:01:11 PM Evaluated: 05901      Waiting: 09724  Current Kendall's Tau: 0.06756
10/24 12:01:57 PM model_id: 6000  gene: [0, 0, 3, 4, 1, 3]  loss: 0.637  top1: 74.771  target: 76.090
10/24 12:01:57 PM Evaluated: 06001      Waiting: 09624  Current Kendall's Tau: 0.06866
10/24 12:02:45 PM model_id: 6100  gene: [4, 2, 4, 1, 3, 2]  loss: 0.679  top1: 74.312  target: 91.560
10/24 12:02:45 PM Evaluated: 06101      Waiting: 09524  Current Kendall's Tau: 0.06820
10/24 12:03:32 PM model_id: 6200  gene: [1, 2, 3, 4, 0, 1]  loss: 0.778  top1: 70.642  target: 91.440
10/24 12:03:32 PM Evaluated: 06201      Waiting: 09424  Current Kendall's Tau: 0.06709
10/24 12:04:20 PM model_id: 6300  gene: [0, 3, 2, 0, 3, 4]  loss: 0.736  top1: 74.771  target: 88.420
10/24 12:04:20 PM Evaluated: 06301      Waiting: 09324  Current Kendall's Tau: 0.06646
10/24 12:05:07 PM model_id: 6400  gene: [3, 1, 0, 2, 0, 1]  loss: 0.671  top1: 76.606  target: 89.640
10/24 12:05:07 PM Evaluated: 06401      Waiting: 09224  Current Kendall's Tau: 0.06703
10/24 12:05:51 PM model_id: 6500  gene: [1, 2, 2, 4, 4, 0]  loss: 0.750  top1: 72.018  target: 74.220
10/24 12:05:51 PM Evaluated: 06501      Waiting: 09124  Current Kendall's Tau: 0.06805
10/24 12:06:38 PM model_id: 6600  gene: [1, 0, 3, 0, 1, 1]  loss: 0.741  top1: 66.514  target: 92.030
10/24 12:06:38 PM Evaluated: 06601      Waiting: 09024  Current Kendall's Tau: 0.06920
10/24 12:07:24 PM model_id: 6700  gene: [2, 4, 1, 0, 4, 3]  loss: 0.767  top1: 70.183  target: 90.350
10/24 12:07:24 PM Evaluated: 06701      Waiting: 08924  Current Kendall's Tau: 0.06890
10/24 12:08:12 PM model_id: 6800  gene: [0, 0, 2, 2, 4, 1]  loss: 0.665  top1: 73.853  target: 88.940
10/24 12:08:12 PM Evaluated: 06801      Waiting: 08824  Current Kendall's Tau: 0.06778
10/24 12:08:59 PM model_id: 6900  gene: [2, 1, 0, 3, 2, 3]  loss: 0.783  top1: 70.642  target: 92.320
10/24 12:08:59 PM Evaluated: 06901      Waiting: 08724  Current Kendall's Tau: 0.06747
10/24 12:09:46 PM model_id: 7000  gene: [1, 1, 1, 3, 4, 4]  loss: 0.705  top1: 72.477  target: 79.550
10/24 12:09:46 PM Evaluated: 07001      Waiting: 08624  Current Kendall's Tau: 0.06756
10/24 12:10:34 PM model_id: 7100  gene: [4, 0, 0, 4, 4, 1]  loss: 0.750  top1: 73.394  target: 70.190
10/24 12:10:34 PM Evaluated: 07101      Waiting: 08524  Current Kendall's Tau: 0.06873
10/24 12:11:20 PM model_id: 7200  gene: [1, 2, 1, 3, 3, 0]  loss: 0.652  top1: 76.147  target: 92.170
10/24 12:11:20 PM Evaluated: 07201      Waiting: 08424  Current Kendall's Tau: 0.06810
10/24 12:12:07 PM model_id: 7300  gene: [3, 1, 4, 2, 3, 1]  loss: 0.667  top1: 74.771  target: 93.440
10/24 12:12:07 PM Evaluated: 07301      Waiting: 08324  Current Kendall's Tau: 0.06647
10/24 12:12:53 PM model_id: 7400  gene: [2, 3, 4, 4, 4, 2]  loss: 0.757  top1: 75.688  target: 91.470
10/24 12:12:53 PM Evaluated: 07401      Waiting: 08224  Current Kendall's Tau: 0.06666
10/24 12:13:40 PM model_id: 7500  gene: [1, 1, 3, 3, 2, 2]  loss: 0.794  top1: 71.560  target: 93.070
10/24 12:13:40 PM Evaluated: 07501      Waiting: 08124  Current Kendall's Tau: 0.06644
10/24 12:14:26 PM model_id: 7600  gene: [1, 2, 3, 1, 2, 2]  loss: 0.791  top1: 68.349  target: 93.320
10/24 12:14:26 PM Evaluated: 07601      Waiting: 08024  Current Kendall's Tau: 0.06667
10/24 12:15:12 PM model_id: 7700  gene: [0, 1, 3, 2, 1, 0]  loss: 0.665  top1: 73.853  target: 88.690
10/24 12:15:12 PM Evaluated: 07701      Waiting: 07924  Current Kendall's Tau: 0.06557
10/24 12:16:00 PM model_id: 7800  gene: [2, 3, 1, 3, 2, 0]  loss: 0.748  top1: 72.018  target: 92.370
10/24 12:16:00 PM Evaluated: 07801      Waiting: 07824  Current Kendall's Tau: 0.06616
10/24 12:16:49 PM model_id: 7900  gene: [3, 1, 0, 1, 4, 3]  loss: 0.642  top1: 77.523  target: 92.160
10/24 12:16:49 PM Evaluated: 07901      Waiting: 07724  Current Kendall's Tau: 0.06485
10/24 12:17:35 PM model_id: 8000  gene: [3, 1, 0, 1, 0, 2]  loss: 0.708  top1: 71.560  target: 89.520
10/24 12:17:35 PM Evaluated: 08001      Waiting: 07624  Current Kendall's Tau: 0.06502
10/24 12:18:22 PM model_id: 8100  gene: [4, 0, 0, 2, 4, 0]  loss: 0.628  top1: 76.606  target: 88.510
10/24 12:18:22 PM Evaluated: 08101      Waiting: 07524  Current Kendall's Tau: 0.06385
10/24 12:19:09 PM model_id: 8200  gene: [0, 2, 0, 2, 0, 2]  loss: 0.732  top1: 69.266  target: 89.090
10/24 12:19:09 PM Evaluated: 08201      Waiting: 07424  Current Kendall's Tau: 0.06404
10/24 12:19:56 PM model_id: 8300  gene: [4, 2, 4, 2, 0, 3]  loss: 0.813  top1: 69.725  target: 92.250
10/24 12:19:56 PM Evaluated: 08301      Waiting: 07324  Current Kendall's Tau: 0.06481
10/24 12:20:42 PM model_id: 8400  gene: [1, 3, 4, 4, 3, 3]  loss: 0.741  top1: 76.147  target: 92.040
10/24 12:20:42 PM Evaluated: 08401      Waiting: 07224  Current Kendall's Tau: 0.06497
10/24 12:21:28 PM model_id: 8500  gene: [2, 4, 0, 0, 1, 3]  loss: 0.855  top1: 70.183  target: 91.820
10/24 12:21:28 PM Evaluated: 08501      Waiting: 07124  Current Kendall's Tau: 0.06453
10/24 12:22:15 PM model_id: 8600  gene: [1, 0, 2, 4, 4, 4]  loss: 0.724  top1: 73.394  target: 85.610
10/24 12:22:15 PM Evaluated: 08601      Waiting: 07024  Current Kendall's Tau: 0.06462
10/24 12:23:03 PM model_id: 8700  gene: [3, 2, 4, 0, 4, 4]  loss: 0.782  top1: 72.477  target: 87.910
10/24 12:23:03 PM Evaluated: 08701      Waiting: 06924  Current Kendall's Tau: 0.06384
10/24 12:23:51 PM model_id: 8800  gene: [1, 4, 2, 4, 0, 4]  loss: 0.720  top1: 73.853  target: 84.530
10/24 12:23:51 PM Evaluated: 08801      Waiting: 06824  Current Kendall's Tau: 0.06370
10/24 12:24:39 PM model_id: 8900  gene: [3, 0, 1, 4, 3, 2]  loss: 0.703  top1: 76.606  target: 92.890
10/24 12:24:39 PM Evaluated: 08901      Waiting: 06724  Current Kendall's Tau: 0.06400
10/24 12:25:26 PM model_id: 9000  gene: [3, 4, 4, 4, 3, 3]  loss: 0.704  top1: 74.312  target: 92.620
10/24 12:25:26 PM Evaluated: 09001      Waiting: 06624  Current Kendall's Tau: 0.06485
10/24 12:26:14 PM model_id: 9100  gene: [4, 2, 3, 2, 0, 4]  loss: 1.076  top1: 56.881  target: 91.220
10/24 12:26:14 PM Evaluated: 09101      Waiting: 06524  Current Kendall's Tau: 0.06557
10/24 12:27:02 PM model_id: 9200  gene: [0, 2, 2, 1, 4, 0]  loss: 0.552  top1: 79.817  target: 86.460
10/24 12:27:02 PM Evaluated: 09201      Waiting: 06424  Current Kendall's Tau: 0.06610
10/24 12:27:51 PM model_id: 9300  gene: [2, 4, 4, 3, 3, 4]  loss: 0.736  top1: 76.147  target: 91.230
10/24 12:27:51 PM Evaluated: 09301      Waiting: 06324  Current Kendall's Tau: 0.06545
10/24 12:28:40 PM model_id: 9400  gene: [4, 3, 1, 1, 4, 4]  loss: 0.707  top1: 73.853  target: 79.030
10/24 12:28:40 PM Evaluated: 09401      Waiting: 06224  Current Kendall's Tau: 0.06509
10/24 12:29:32 PM model_id: 9500  gene: [2, 0, 0, 2, 0, 4]  loss: 0.665  top1: 73.853  target: 89.060
10/24 12:29:32 PM Evaluated: 09501      Waiting: 06124  Current Kendall's Tau: 0.06589
10/24 12:30:20 PM model_id: 9600  gene: [1, 0, 3, 3, 3, 2]  loss: 0.778  top1: 69.725  target: 93.090
10/24 12:30:20 PM Evaluated: 09601      Waiting: 06024  Current Kendall's Tau: 0.06740
10/24 12:31:09 PM model_id: 9700  gene: [4, 3, 3, 2, 1, 2]  loss: 0.741  top1: 72.018  target: 92.210
10/24 12:31:09 PM Evaluated: 09701      Waiting: 05924  Current Kendall's Tau: 0.06747
10/24 12:31:58 PM model_id: 9800  gene: [0, 2, 0, 2, 2, 1]  loss: 0.746  top1: 70.183  target: 89.130
10/24 12:31:58 PM Evaluated: 09801      Waiting: 05824  Current Kendall's Tau: 0.06820
10/24 12:32:49 PM model_id: 9900  gene: [2, 4, 0, 3, 4, 4]  loss: 0.715  top1: 71.560  target: 89.960
10/24 12:32:49 PM Evaluated: 09901      Waiting: 05724  Current Kendall's Tau: 0.06889
10/24 12:33:38 PM model_id: 10000  gene: [2, 3, 3, 1, 2, 3]  loss: 0.759  top1: 67.890  target: 94.120
10/24 12:33:38 PM Evaluated: 10001      Waiting: 05624  Current Kendall's Tau: 0.06973
10/24 12:34:30 PM model_id: 10100  gene: [1, 1, 0, 2, 4, 1]  loss: 0.727  top1: 71.101  target: 86.920
10/24 12:34:30 PM Evaluated: 10101      Waiting: 05524  Current Kendall's Tau: 0.07001
10/24 12:35:18 PM model_id: 10200  gene: [0, 3, 1, 1, 1, 3]  loss: 0.662  top1: 77.982  target: 93.520
10/24 12:35:18 PM Evaluated: 10201      Waiting: 05424  Current Kendall's Tau: 0.06846
10/24 12:36:09 PM model_id: 10300  gene: [2, 4, 3, 1, 4, 0]  loss: 0.659  top1: 78.440  target: 89.660
10/24 12:36:09 PM Evaluated: 10301      Waiting: 05324  Current Kendall's Tau: 0.06860
10/24 12:37:01 PM model_id: 10400  gene: [3, 3, 3, 2, 2, 2]  loss: 0.876  top1: 70.642  target: 93.500
10/24 12:37:02 PM Evaluated: 10401      Waiting: 05224  Current Kendall's Tau: 0.06986
10/24 12:37:50 PM model_id: 10500  gene: [2, 4, 4, 3, 0, 3]  loss: 0.720  top1: 72.936  target: 92.580
10/24 12:37:50 PM Evaluated: 10501      Waiting: 05124  Current Kendall's Tau: 0.06998
10/24 12:38:40 PM model_id: 10600  gene: [0, 4, 1, 2, 2, 2]  loss: 0.877  top1: 63.303  target: 90.030
10/24 12:38:40 PM Evaluated: 10601      Waiting: 05024  Current Kendall's Tau: 0.06977
10/24 12:39:30 PM model_id: 10700  gene: [4, 2, 3, 4, 1, 2]  loss: 0.771  top1: 70.183  target: 88.780
10/24 12:39:30 PM Evaluated: 10701      Waiting: 04924  Current Kendall's Tau: 0.06965
10/24 12:40:20 PM model_id: 10800  gene: [0, 3, 3, 0, 3, 4]  loss: 0.736  top1: 74.771  target: 88.450
10/24 12:40:20 PM Evaluated: 10801      Waiting: 04824  Current Kendall's Tau: 0.06893
10/24 12:41:10 PM model_id: 10900  gene: [0, 3, 4, 1, 2, 0]  loss: 0.552  top1: 79.817  target: 86.680
10/24 12:41:10 PM Evaluated: 10901      Waiting: 04724  Current Kendall's Tau: 0.06936
10/24 12:41:59 PM model_id: 11000  gene: [3, 2, 0, 1, 2, 2]  loss: 0.705  top1: 75.229  target: 93.480
10/24 12:41:59 PM Evaluated: 11001      Waiting: 04624  Current Kendall's Tau: 0.07032
10/24 12:42:49 PM model_id: 11100  gene: [4, 1, 2, 4, 3, 2]  loss: 0.976  top1: 61.468  target: 89.940
10/24 12:42:49 PM Evaluated: 11101      Waiting: 04524  Current Kendall's Tau: 0.07065
10/24 12:43:40 PM model_id: 11200  gene: [4, 0, 0, 0, 3, 0]  loss: 0.753  top1: 71.101  target: 84.890
10/24 12:43:40 PM Evaluated: 11201      Waiting: 04424  Current Kendall's Tau: 0.07086
10/24 12:44:27 PM model_id: 11300  gene: [0, 3, 3, 1, 1, 2]  loss: 0.679  top1: 75.688  target: 93.360
10/24 12:44:27 PM Evaluated: 11301      Waiting: 04324  Current Kendall's Tau: 0.07175
10/24 12:45:20 PM model_id: 11400  gene: [3, 3, 2, 1, 0, 3]  loss: 0.694  top1: 75.688  target: 94.050
10/24 12:45:20 PM Evaluated: 11401      Waiting: 04224  Current Kendall's Tau: 0.07191
10/24 12:46:09 PM model_id: 11500  gene: [2, 3, 3, 3, 1, 1]  loss: 0.708  top1: 71.560  target: 92.810
10/24 12:46:09 PM Evaluated: 11501      Waiting: 04124  Current Kendall's Tau: 0.07218
10/24 12:46:59 PM model_id: 11600  gene: [0, 1, 2, 1, 4, 3]  loss: 0.647  top1: 75.688  target: 92.000
10/24 12:46:59 PM Evaluated: 11601      Waiting: 04024  Current Kendall's Tau: 0.07240
10/24 12:47:50 PM model_id: 11700  gene: [1, 0, 2, 0, 4, 3]  loss: 0.844  top1: 64.220  target: 91.220
10/24 12:47:50 PM Evaluated: 11701      Waiting: 03924  Current Kendall's Tau: 0.07233
10/24 12:48:39 PM model_id: 11800  gene: [1, 2, 4, 2, 0, 3]  loss: 0.830  top1: 70.642  target: 92.080
10/24 12:48:39 PM Evaluated: 11801      Waiting: 03824  Current Kendall's Tau: 0.07190
10/24 12:49:30 PM model_id: 11900  gene: [2, 0, 3, 3, 3, 2]  loss: 0.912  top1: 62.844  target: 92.890
10/24 12:49:30 PM Evaluated: 11901      Waiting: 03724  Current Kendall's Tau: 0.07207
10/24 12:50:20 PM model_id: 12000  gene: [0, 0, 4, 3, 4, 3]  loss: 0.688  top1: 78.899  target: 91.890
10/24 12:50:20 PM Evaluated: 12001      Waiting: 03624  Current Kendall's Tau: 0.07165
10/24 12:51:10 PM model_id: 12100  gene: [0, 2, 4, 0, 2, 4]  loss: 0.784  top1: 68.807  target: 86.590
10/24 12:51:10 PM Evaluated: 12101      Waiting: 03524  Current Kendall's Tau: 0.07180
10/24 12:52:01 PM model_id: 12200  gene: [1, 0, 2, 4, 0, 1]  loss: 0.867  top1: 63.303  target: 88.640
10/24 12:52:01 PM Evaluated: 12201      Waiting: 03424  Current Kendall's Tau: 0.07177
10/24 12:52:53 PM model_id: 12300  gene: [0, 2, 0, 1, 2, 3]  loss: 0.684  top1: 76.147  target: 92.700
10/24 12:52:53 PM Evaluated: 12301      Waiting: 03324  Current Kendall's Tau: 0.07196
10/24 12:53:41 PM model_id: 12400  gene: [4, 3, 1, 2, 4, 2]  loss: 0.752  top1: 71.560  target: 90.490
10/24 12:53:41 PM Evaluated: 12401      Waiting: 03224  Current Kendall's Tau: 0.07221
10/24 12:54:32 PM model_id: 12500  gene: [1, 0, 2, 3, 3, 3]  loss: 0.770  top1: 72.936  target: 92.670
10/24 12:54:32 PM Evaluated: 12501      Waiting: 03124  Current Kendall's Tau: 0.07160
10/24 12:55:21 PM model_id: 12600  gene: [2, 2, 2, 4, 1, 1]  loss: 0.773  top1: 74.312  target: 89.860
10/24 12:55:21 PM Evaluated: 12601      Waiting: 03024  Current Kendall's Tau: 0.07209
10/24 12:56:12 PM model_id: 12700  gene: [1, 4, 2, 1, 3, 0]  loss: 0.677  top1: 73.853  target: 91.890
10/24 12:56:12 PM Evaluated: 12701      Waiting: 02924  Current Kendall's Tau: 0.07212
10/24 12:57:05 PM model_id: 12800  gene: [4, 0, 0, 4, 3, 1]  loss: 0.796  top1: 70.642  target: 84.970
10/24 12:57:05 PM Evaluated: 12801      Waiting: 02824  Current Kendall's Tau: 0.07285
10/24 12:57:55 PM model_id: 12900  gene: [4, 2, 3, 3, 4, 4]  loss: 0.700  top1: 76.147  target: 90.380
10/24 12:57:55 PM Evaluated: 12901      Waiting: 02724  Current Kendall's Tau: 0.07308
10/24 12:58:46 PM model_id: 13000  gene: [1, 4, 2, 2, 4, 1]  loss: 0.825  top1: 68.807  target: 86.220
10/24 12:58:46 PM Evaluated: 13001      Waiting: 02624  Current Kendall's Tau: 0.07323
10/24 12:59:36 PM model_id: 13100  gene: [4, 1, 3, 0, 4, 3]  loss: 0.709  top1: 74.312  target: 91.170
10/24 12:59:36 PM Evaluated: 13101      Waiting: 02524  Current Kendall's Tau: 0.07285
10/24 01:00:25 PM model_id: 13200  gene: [0, 0, 1, 2, 1, 2]  loss: 0.665  top1: 73.853  target: 88.810
10/24 01:00:25 PM Evaluated: 13201      Waiting: 02424  Current Kendall's Tau: 0.07336
10/24 01:01:17 PM model_id: 13300  gene: [3, 4, 0, 4, 2, 3]  loss: 0.715  top1: 71.101  target: 91.990
10/24 01:01:17 PM Evaluated: 13301      Waiting: 02324  Current Kendall's Tau: 0.07359
10/24 01:02:05 PM model_id: 13400  gene: [1, 2, 1, 4, 3, 2]  loss: 0.733  top1: 75.688  target: 91.560
10/24 01:02:05 PM Evaluated: 13401      Waiting: 02224  Current Kendall's Tau: 0.07320
10/24 01:02:56 PM model_id: 13500  gene: [2, 3, 0, 0, 0, 2]  loss: 0.789  top1: 69.266  target: 91.390
10/24 01:02:56 PM Evaluated: 13501      Waiting: 02124  Current Kendall's Tau: 0.07300
10/24 01:03:47 PM model_id: 13600  gene: [1, 4, 2, 3, 3, 2]  loss: 0.774  top1: 72.018  target: 92.230
10/24 01:03:47 PM Evaluated: 13601      Waiting: 02024  Current Kendall's Tau: 0.07292
10/24 01:04:36 PM model_id: 13700  gene: [2, 3, 2, 3, 2, 2]  loss: 0.844  top1: 67.890  target: 93.250
10/24 01:04:36 PM Evaluated: 13701      Waiting: 01924  Current Kendall's Tau: 0.07308
10/24 01:05:26 PM model_id: 13800  gene: [1, 2, 3, 2, 2, 4]  loss: 1.440  top1: 53.670  target: 91.240
10/24 01:05:26 PM Evaluated: 13801      Waiting: 01824  Current Kendall's Tau: 0.07321
10/24 01:06:17 PM model_id: 13900  gene: [0, 4, 1, 4, 0, 4]  loss: 0.750  top1: 73.394  target: 69.490
10/24 01:06:17 PM Evaluated: 13901      Waiting: 01724  Current Kendall's Tau: 0.07326
10/24 01:07:06 PM model_id: 14000  gene: [0, 4, 1, 3, 0, 1]  loss: 0.654  top1: 77.982  target: 91.330
10/24 01:07:06 PM Evaluated: 14001      Waiting: 01624  Current Kendall's Tau: 0.07306
10/24 01:07:54 PM model_id: 14100  gene: [4, 3, 1, 1, 2, 3]  loss: 0.700  top1: 73.394  target: 93.180
10/24 01:07:54 PM Evaluated: 14101      Waiting: 01524  Current Kendall's Tau: 0.07288
10/24 01:08:45 PM model_id: 14200  gene: [3, 1, 1, 1, 2, 1]  loss: 0.794  top1: 63.303  target: 90.080
10/24 01:08:45 PM Evaluated: 14201      Waiting: 01424  Current Kendall's Tau: 0.07223
10/24 01:09:35 PM model_id: 14300  gene: [4, 3, 2, 3, 0, 0]  loss: 0.688  top1: 78.899  target: 91.910
10/24 01:09:35 PM Evaluated: 14301      Waiting: 01324  Current Kendall's Tau: 0.07276
10/24 01:10:27 PM model_id: 14400  gene: [2, 0, 4, 4, 3, 0]  loss: 0.693  top1: 74.312  target: 90.490
10/24 01:10:27 PM Evaluated: 14401      Waiting: 01224  Current Kendall's Tau: 0.07291
10/24 01:11:16 PM model_id: 14500  gene: [4, 4, 4, 4, 0, 2]  loss: 0.837  top1: 68.349  target: 80.240
10/24 01:11:16 PM Evaluated: 14501      Waiting: 01124  Current Kendall's Tau: 0.07300
10/24 01:12:07 PM model_id: 14600  gene: [1, 4, 4, 2, 3, 4]  loss: 0.749  top1: 73.394  target: 86.430
10/24 01:12:07 PM Evaluated: 14601      Waiting: 01024  Current Kendall's Tau: 0.07232
10/24 01:12:56 PM model_id: 14700  gene: [4, 4, 1, 2, 0, 3]  loss: 0.696  top1: 71.101  target: 91.460
10/24 01:12:56 PM Evaluated: 14701      Waiting: 00924  Current Kendall's Tau: 0.07293
10/24 01:13:46 PM model_id: 14800  gene: [2, 1, 3, 2, 0, 2]  loss: 1.094  top1: 57.339  target: 92.370
10/24 01:13:46 PM Evaluated: 14801      Waiting: 00824  Current Kendall's Tau: 0.07303
10/24 01:14:36 PM model_id: 14900  gene: [3, 4, 3, 1, 1, 2]  loss: 0.691  top1: 74.312  target: 93.010
10/24 01:14:36 PM Evaluated: 14901      Waiting: 00724  Current Kendall's Tau: 0.07289
10/24 01:15:25 PM model_id: 15000  gene: [0, 1, 0, 0, 1, 3]  loss: 0.752  top1: 69.725  target: 92.370
10/24 01:15:25 PM Evaluated: 15001      Waiting: 00624  Current Kendall's Tau: 0.07309
10/24 01:16:14 PM model_id: 15100  gene: [0, 2, 0, 4, 2, 3]  loss: 0.657  top1: 76.147  target: 91.430
10/24 01:16:14 PM Evaluated: 15101      Waiting: 00524  Current Kendall's Tau: 0.07383
10/24 01:17:07 PM model_id: 15200  gene: [2, 4, 0, 0, 0, 0]  loss: 1.193  top1: 55.046  target: 10.000
10/24 01:17:07 PM Evaluated: 15201      Waiting: 00424  Current Kendall's Tau: 0.07425
10/24 01:17:57 PM model_id: 15300  gene: [1, 0, 2, 0, 0, 4]  loss: 1.206  top1: 51.835  target: 86.940
10/24 01:17:57 PM Evaluated: 15301      Waiting: 00324  Current Kendall's Tau: 0.07460
10/24 01:18:46 PM model_id: 15400  gene: [2, 0, 2, 3, 2, 3]  loss: 0.775  top1: 71.560  target: 92.710
10/24 01:18:46 PM Evaluated: 15401      Waiting: 00224  Current Kendall's Tau: 0.07413
10/24 01:19:36 PM model_id: 15500  gene: [1, 4, 1, 0, 0, 1]  loss: 0.741  top1: 69.725  target: 79.560
10/24 01:19:36 PM Evaluated: 15501      Waiting: 00124  Current Kendall's Tau: 0.07454
10/24 01:20:26 PM model_id: 15600  gene: [2, 0, 3, 3, 4, 0]  loss: 0.767  top1: 76.147  target: 91.860
10/24 01:20:26 PM Evaluated: 15601      Waiting: 00024  Current Kendall's Tau: 0.07383
10/24 01:20:39 PM model_id: 15624  gene: [2, 0, 2, 0, 2, 2]  loss: 1.176  top1: 55.046  target: 86.820
10/24 01:20:39 PM Evaluated: 15625      Waiting: 00000  Current Kendall's Tau: 0.07398
10/24 01:20:39 PM Finish ranking and save predictions to : results/debug_baseline.npy
10/24 01:20:39 PM Final_pred: 15625     Final_target: 15625     Final_Kendall's Tau: 0.07398
10/24 01:20:39 PM Total Elapsed Time: 5h 13min 14s
你好，我直接用cifar10作为我们的标准得到了上面的结果，上面每一个model_id对应一个测试精度，我是需要挑选出最高的精度所对应的结构重新搭建一整个网络重新训练吗？

如果目标是在这个搜索空间中找出精度最高的网络，那么就是从上边找出最高精度的网络构建网络结构重新训练即可

您好，非常感谢您的回复，然后我没有在您提供的代码里找到相关的代码？您是否方便提供下？

好的，十分感谢您的回复


text:
ThinkPad P50 blackscreen

hi!
Got an issue with my P50. If i run tpfc on discrete gpu mode the screen goes black and never recovers. If i run it in hybrid mode the discrete gpu crashes and completely disappears from device manager leaving no trace. If i disable dgpu in devmanager, run tpfc and then try to enable dgpu i get error 31 (windows cannot load drivers for this device). This issue persist with every dual fan version of tpfc i found on github and regardless the OS version. tvicport is installed, BIOS is the latest version (1.67), and ive tried OS versions from W10 1507 up to the latest insider W11 22H2. Im running W11 insider 22H2 currently.
Thank you in advance

Hmm that's weird, the program doesn't actually access the GPU
Do you have a Xeon CPU or an i7? This might be an issue with how the CPU communicates with the GPU. I don't think this is an issue with the Quadro because the program works with my W540 (i7 X series and K2100M).
But the Nvidia driver (and intel driver) might be a cause so it's probably a good idea to update to the latest version (I also have nvidia's studio driver instead of game ready driver installed).
Also do the single fan versions also have the same issue? (if not then it might be an EC issue) You can find a pretty good list here
Thank you!

thank you for your reply
i have the i7-6820HQ with the M1000m. single fan versions of tpfc work fine. the drivers are the latest ones from both intel and nvidia respectively (nvidia-studio drivers).

hm okay, I'll try modding one of the single fan versions into dual fan then

Thank you

hm okay, I'll try modding one of the single fan versions into dual fan then

Hello! I have the same problem with black screen on P50. My P50 is Xeon/M2000M.
I took a lot of time to solve the problem and find a program to control two fans. I tried to diagnose the fans for problems through the official Lenovo Diagnostic Program. When im trying to check the fans I also got a black screen, I hope this information helps to solve the problem.
I really hope for you!

Thank you!

tpfc.zip
try see if this one works
code on #25

Hello, I will try it at Monday.
Thanks a lot in advance!!

yeah np!

hi!
just tried it and it still blackscreens. this time windows doesnt seem to freeze on dgpu only mode tho. here are ythe logs captured by the program:
TPFanControl.log
TPFanControl_csv.txt

hmm from the logs it seems like the program crashed while trying to access the fan EC
i think it might be a problem with the the second fan address

thanks for the reply!
is thre anything i could do about it or something oyu would suggest? (fan can be controlled under linux)

yea np!
is it linux mode for the laptop or running GNU/Linux? if it's the ladder do you have the source code for it? the two addresses might be similar
thank you!

it is running GNU/Linux (PopOS 20.10) in tripple boot (also got MacOS Monterey beta). Here is what i use to control the fans in linux

oooh yeah i almost forgot that linux doesn't use address to control the EC. I wonder if it's a kernel level thing

@thessarb Hello! Im sorry that im very noob at programing and understanding of all of this stuff.
I correctly understand that the problem is not solved at the moment?

yeah, I'm currently working on resolving issue #20 with PR #31, maybe you can try that build out and see if it works

@Remalisa np i am no different
@Shuzhengz thx ill try it out later

heres the link to a wip build
tpfc.zip

hi!
just tried the wip build and tpfc launches finally, but it lacks cpu temps and cant control the fan. also it shows the fans as if they were stuck at 5120RPM. here is the log:
TPFanControl.log

@thessarb Hi! Can you please explain to me how did you start the program? I was trying, but I failed ;(

@Remalisa i didnt do anything different, just extracted the zip and ran fancontrol.exe (W11 Insider Dev Build 22593)

Hello!
I have finally opened the program. I also observe that the temperatures and fan speeds do not change in numbers. I also noticed that when the manual mode is selected from 0 to 7, the fan speed simply does not change. Moreover when you select manual mode 7, it automatically changes to program mode .ini

@Shuzhengz trying to install rw apears the same problem as in this link: https://www.bleepingcomputer.com/forums/t/709973/rw-everything-not-working-after-windows-build-update-to-the-last-version-1903/

hmm are you on windows 10 or 11?
you can try using another program, any that reads the EC should work, I just haven't used those other than rweverything on windows

I'm using windows 10 21H2.
Ok, I will try something else, thanks!
On Fri, Apr 8, 2022, 11:26 PM Tom Zhang @.***> wrote:

hmm are you on windows 10 or 11?
you can try using another program, any that reads the EC should work, I
just haven't used those other than rweverything on windows
—
Reply to this email directly, view it on GitHub
https://github.com/Shuzhengz/TPFanCtrl2/issues/23#issuecomment-1093322970,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AYF5QGIKBALBARK3DB2VIL3VECI7NANCNFSM5QF5RKSA
.
You are receiving this because you were mentioned.Message ID:
@.***>

hi @Shuzhengz. had too many assignments at uni and didnt have time to track the issue. what program would you recommend to read the EC? i cant seem to find any, or i simply dont know how to search ig

hi sorry, I was very busy with school for the past few weeks and didn't have time to get back to this
rweverything might not work if you have old drivers, so probably a good idea to update all the drivers
I don't know any other equivalent programs, but you could try reading the msr registry using the rdmsr command
you can also use msr-tools provided by Intel, but I'm not sure if that works with Windows (you also have to compile it as there's no binary release)

np, same here, in the middle of an annoying exam season XD. will try it as soon as im done with the exams and post the results here. thanks

Hello Shuzhengz
Is there an update for the P50 with TPFanControl? I've been doing tons of research but can't for the life of me figure it out.

@Lego737 Hi!
sorry I just got back to working on this project, it seems like the version from PR #31 is working better than the intended version, so I'm going to say try that one out, here's the link to that wip build binary
It seems like it's still reading from the wrong address though, so it would be great if you could try downloading RW everything, then open EC Controller and search for your sensors, since I don't have access to a P50 physically
Thank you

Sure, I will do that then report here!

hi @Shuzhengz! i downloaded rw everything, opened embedded controller but i dont understand the gibberish it puts out. could you give me some hint on how to interpret it? here is an image of what i see:

yup, so currently the release version has the address 0x2F as the data port controller address, which is in hex, and would be 47 in decimal. The number 2F means that it is on the 20 row and the 0F column, which would be this one

when using manual mode to set fan speed, the value here at 0x2F would become whatever the inputted fan speed value is (after converting to hex)

try manually change the 0x2F address to value 46, if you can hear the speed of the fan ramp up then it's the right address

the temperature readout is currently at address 0x78, and should be changing in real time
you can find out which address yours is by using another software to monitor your cpu temp (package temp), then convert it to hex, and find which address has the value close o it

So i looked at the said values. 0x78 doesnt really chase the temp reported by the cpu itself, but it matches the cpu temp reported by the EC 1:1. Also 0x79 seems to chase the dGPU temps with 1s delay. Setting 0x2F to 46 ramps up only the left fan.

@Shuzhengz i think i may have found the issue. 0x31 seems to be the "fan selector". When the laptop starts up it hold the value 41 and with that i can control the left fan. With the value 40 i can control the right fan. Dgpu doesnt seem to disappear. However the dual fan tpfc seems to use values 00 and 01 in that address and sure enough, the moment i put either of those values the dgpu goes offline till the next reboot. Also if you leave it on 40 long enough it automarically goes to 00 which causes the dgpu to go offline. However switching between values for slow me seems to have enough time so it doesnt go to 00. Hope this helps.

thank you! I will work on this in a little bit

@thessarb can you try this build? I corrected the ec addresses, however I'm still working on getting the rempeature reading. Currently I'm trying to use open hardware monitor's dll in CLI mode to read the package temperature, but there are still a lot of bugs to iron out, so it would be great if you can verify that the fan addresses are working on your laptop, and open hardware monitor also works (you can download the exe here)

here's the built program: tpfc-p50b.zip

Unfourtnately, it sadly didn't work for me. I tried both builds on dGPU mode and the screen still went black.

hmm does it go black immediately or after a few seconds?

@Shuzhengz thank you, ill try it as soon as i get home

@Lego737 boot in hybrid mode, disable dgpu from dev manager so you dont BSOD in a few minutes, open rweverything and choose Embedded Controller, run tpfc. Look at the value at the row 30 and column 01. The value shpuld be 41 at the start, check the value that is input by tpfc.

Yes, it goes black instantly.

@Shuzhengz hi again! im happy to report that tpfc doesnt cause black screen for me anymore. also open hardware monitor seems to work and the values match both hwinfo64 and hwmon

@thessarb, how did you fix the issue in dGPU mode?

I did absolutely nothing. Just tried it in hybrid, dgpu didnt disappear. So i tried it in discrete mode and didnt get a black screen. The temp readout is kinda funky (the degree symbol is weird) but other than that it seems to be working fine for me

I tried his latest build in dGPU mode and my screen still went black.

Try the one Tom uploaded here, thats the one im using
Get Outlook for Androidhttps://aka.ms/AAb9ysg

From: Lego737 @.>
Sent: Sunday, July 10, 2022 6:54:10 PM
To: Shuzhengz/TPFanCtrl2 @.>
Cc: thessarb @.>; Mention @.>
Subject: Re: [Shuzhengz/TPFanCtrl2] ThinkPad P50 blackscreen (Issue #23)
I tried his latest build in dGPU mode and my screen still went black.
—
Reply to this email directly, view it on GitHubhttps://github.com/Shuzhengz/TPFanCtrl2/issues/23#issuecomment-1179762478, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ARRUGTKSWL5NOB72GCUF7QTVTL53FANCNFSM5QF5RKSA.
You are receiving this because you were mentioned.Message ID: @.***>

@Lego737 (this one)[https://github.com/Shuzhengz/TPFanCtrl2/files/9078094/tpfc-p50b.zip]

@thessarb okay so using C# is giving me a ton of problems, I think I'll try another method by reading the msr
can you try and see from rweverything's cpu msr page if address 0x019C (the temperature of each core) and address 0x1B1 (package temperature) reports the cpu temperature?
the values would look something like 0000000088260a82, you can ignore everything else and look at the "26" part (decimal digit 16-23 in the more detailed panel), the value should be half of the cpu temperature from what i can tell
thank you!

I will look at it tomorrow after reinstalling windows. Today macos just randomly decided to wipe my windows install clean off the ssd.

hi! sorry for the delay. i opened the msr page but i cant seem to find the said addresses. the list is pretty short and the values dont seem to change at all. a considerable amount of the values are just strings of 0-s.

no worries
the MSR register is actually in the user value section (theres a button on the top right of the window next to the save button to add the addresses), and there should be a value for each of the CPU cores. For 0x019C they should be slightly different, but for 0x1B1 they should all be the same
thank you!

this is all i get there

yeah so you have to add the values in the pop up window

just type in the addresses, click add, and it should show up

just looked at it and i cant relate the values to the core temps in a meaningful way. when the cpu was at 36 degrees, the value there was 42, when the temp was at 60 the value was 3A and when it hit the thermal throttling point it went crazy cycling thru all possible numbers and letter up to F

yeah in Intel's manual there is supposed to be a bitfield modifier for the values to convert it into hex (I believe it's 15:0), I can add that in the code, but I have no idea what it means or actually does.

page 20 of this

@Shuzhengz
I love that you were able to fix this app as I can now use my P50 without it overheating a ton! So, thank you for that!
However, I've come accross a problem that I'm currently looking into. When I launch a game, that being Fortnite, and have the app running in the background, Fortnite ends up crashing after 10 or so minutes. I did, at one point, reinstall the dGPU driver which seemed to fix it but in the end, it still crashed. Do you think that this is the fan app on my machine or could it be something else?! I hope to hear from you soon :)
Lego737

hi @Lego737
thank you! can you try using a CPU stress test tool like cinebench CPU or blender CPU render, with the fan control set to manual 80 and see if it crashes? this will narrow the issue down to CPU and fan contol or GPU.
also currently I'm still working on temperature for the p50 because it's not in the EC, so it would probably would be a good idea to avoid using smart mode for now and stick to manual mode to avoid overheating

I have a P-50 Xeon M2000. TpFanControl only show CPU and APS temp. This is normal? The others sensors can't be displayed? GPU and others?
I must use the program in manual mode? What values are recommended between 0 and 7?

I have a P-50 Xeon M2000. TpFanControl only show CPU and APS temp. This is normal? The others sensors can't be displayed? GPU and others? I must use the program in manual mode? What values are recommended between 0 and 7?

unfortunately yes, temps are broken right now as we can't find the address for that

license: Unlicense


text:
Collapse ReportItem and recategorize reports

Fix #65.
Flattening ReportItem makes little difference programmatically, but it greatly simplifies shifting the categories of the reports and helps reduce ReportItem's size from 5 to 4 words.

[x] UnknownFilter is an RPSL error.
[ ] More intuitive naming for SkipFBad, etc..
[ ] Reorder AnyReport to flow unidirectionally ok → skip → unrecorded → meh.
[ ] Report::UnrecordedImport, etc. and the "unrecorded" case in AllReport and AnyReport.
[ ] Remove skipping skipped.

This PR, if merged, will make many current stats stale. They will need to be redone.

PartialOrd seems like a good idea at first, until you consider:

This part of the code needs to be absolutely fast so slice::sort is undesired.
The inner value of each case has to be accessed using a match anyway. We could have another function that does that, but then the code is not really simplified then.

I am currently satisfied with listing all possibilities and making them clear. Let's just have it like this for now.


text:
Add support for Logbooks

Expedition is now core.

Related to #18

authors: domialex leMicin

repo: Sidekick-Poe/Sidekick


text:
Lichess added study flair

https://github.com/lichess-org/lila/commit/67843e8124e75e4c02ca8c2f33f6a7d22e029a13

But not in the JSON of the study list: https://github.com/lichess-org/lila/issues/15519

Covered in 2.3.96

repo: Siderite/lichessTools


text:
Added cargo flow examples.

Added two new notebooks-as-examples:

PersistVessels
CargoFlowPlots

Please comment on readability/visualizations.

Some general Comments:

There should be no personal comments (like further improvements)
Maybe the two notebooks should be joined, so that the tests do not fail. Also It would be better in terms of interpret-ability.
Also, I would rather persist only vessels in sqlite and not the merged with voyages result, since the latter is to specific.
There should be an intro explaining the motives of the example. Maybe the Cargo Flows Dashboard of the platform should be mentioned.
Where the need of explaining the variables occurs, it should be done via well structured comments or markdown cells.

authors: LamprosArgy miltonlog

repo: SignalOceanSdk/SignalSDK


text:
裁图比例设置传入数组吗？并且第一个裁图用的是数组的第一个比例 而不是图片默认尺寸

裁图比例设置传入数组吗？并且第一个裁图用的是数组的第一个比例 而不是图片默认尺寸
如上所述

啥意思?具体点

authors: SilenceLove YelCode

repo: SilenceLove/HXPhotoPicker