Bringing One-Click/Automatic Updates to Ghost

It has been a feature long-requested by many users, and thanks to the new Ghost-CLI project, Automatic Updates are finally within reach!
Before this feature will work fully, however, there are several changes that need to be made across Ghost, Ghost-Admin, and Ghost-CLI, to provide the smoothest, most fault-tolerant update process. This issue exists to document and track those specific changes as they occur in the separate repositories.
Brief Overview
Currently, whenever there is a new Ghost version, a notification appears in Ghost-Admin prompting the user to update, and providing a link to the relevant support page with documentation as to how to manually update Ghost. This current notification would be extended and instead of linking to a support page, it would link to the /ghost/about page, where a button would appear that a user could click to update their blog.
Upon clicking the button, a server request would be made, and the Ghost server would communicate with the managing CLI process (ghost run), which would then trigger the ghost update command. As Ghost itself would still be running, the user could then continue using Ghost normally, and Ghost-Admin would poll the Ghost server in the background until 1 of 2 things happens:

The update process erred, in which case Ghost-Admin would retrieve the error and display it (with perhaps a link to documentation).
The update process succeeded, and the user needs to refresh the page to get the latest version of Ghost-Admin.

Additional Notes

The update process will only be available if Ghost is being run with Ghost-CLI.
The first iteration will only feature one-click updates through the admin client. Future versions will work on automatic updates that require no user interaction.

Tasks
Ghost-CLI

[ ] ghost update command should make sure blog can start before switching to new version (TryGhost/Ghost-CLI#153)

Basically, Ghost-CLI needs to be able to verify that the new version of Ghost has been installed correctly, and that there won't be any issues switching versions. With the current update process, the blog could be left in a broken state if the old version is stopped and the new one fails to start, so we want to make sure the new version will start correctly.

[ ] ghost update should communicate with the Ghost process (issue/PR # TBD)

Currently, Ghost-CLI starts ghost using a ghost run command, which allows the CLI to provide some light management of the core Ghost server process. Communication between the two process currently happens over IPC channels - and this should be extended to allow ghost update to tell ghost run that it has finished installing the new Ghost version, before it stops the old version, giving Ghost time to notify the client that the blog is restarting.
Ghost

[ ] Update API endpoint (PR in progress - #7977)

This endpoint handles communication with the Ghost-CLI process to start the update process, as well as inform Ghost-Admin of the update status.
There will be both a GET endpoint and a POST endpoint.
The GET endpoint will return a couple of things:

New version if one is available
Status flag signifying whether or not the blog is currently undergoing an update process.
Any errors that occurred during update

The POST endpoint will:

Trigger the update process by sending an IPC message to Ghost-CLI

At the moment, only the blog owner will be able to update the blog, but it could be extended in the future to allow administrators as well, pending discussion.
As part of this endpoint, there will be a config variable added that controls whether or not the blog is able to be updated (for example, if you enable a particular privacy flag or if you're not running with Ghost-CLI).
Ghost-Admin

[ ] Make custom update notification that links to the About page.

Because the update button will be located on the About page, the update notification should link to the About page instead of a support page. This should also take into account the configuration of the server, so if the user is not running via Ghost-CLI, or has disabled CLI updates for any particular reason, then the notification will not link to the about page and instead show a different message.

[ ] Build polling service that will poll the server in the background at either fixed or increasing intervals to determine update status

The service should also check whenever Ghost-Admin is first loaded to see if Ghost is currently being updated, and trigger the polling process if it is. (Use case: user refreshes the page after starting an update process).
There should probably be a way to ask the service if Ghost is updating, and certain blog actions may need to be disabled during update (for example: theme uploads, import/export, etc.) - this may be added in future improvements

@acburdine what's the status of this so far as Ghost-CLI is concerned?

Ghost-CLI currently is missing a couple of things needed to get this working, my thought was we'd be putting this off until after 1.0, as it's a fairly sizable feature that will require stuff in all three major Ghost components.

Ok, it was added to an internal sprint list so just wanted to check in on the current status so I can prioritise properly 😄

We had a conversation about this earlier today. Not sure what the status is, but the simple version that we were talking about was:
Running ghost autoupdate causes Ghost to setup a cron job that runs daily.
The cron job should do the following:

if there is a patch or minor update available, run ghost update
if there is a major update available, send an email

Not sure the best way to send an email, maybe an endpoint in Ghost?
The other thing to consider here, is that I think we lost maintenance mode between LTS and 1.0.0? Original issue: https://github.com/TryGhost/Ghost/issues/6976
We should make sure that this is available, because ghost update could make use of it.
This might be a simple approach to getting this working?

That was actually something I had thought about as well. The email part might be a little tricky, but it's definitely a viable approach 👍

For what it's worth, I think https://github.com/TryGhost/Ghost-CLI/issues/153 is still a needed feature before even the simple approach can be considered - otherwise we would potentially run into the issue where ghost update would kill your blog because of some issue.

Any updates here?


The table requires all rows to have an unique id property?

Although I find one similar issue created by someone. I am getting same issue. But I am not understanding how can I solve this warning.
I am getting same warning like this-
The table requires all rows to have an unique id property. A row was provided without id in the rows prop. To prevent the loss of state between renders, please provide an unique id for each row.
But where should I give the id props?
Here is my component-
import { Box, Typography } from "@mui/material";
import MaterialTable from "@material-table/core";

//Images
import NewsIcon from "Asset/news.png";
import VideoIcon from "Asset/video.png";

//Data
import OverviewTwo from "Data/Demo/OverviewTwo";

const Overview = () => {
    const data = [];
    OverviewTwo && OverviewTwo.forEach(item => {
        data.push({
            category: <Box component="img" src={item.category === "news" ? NewsIcon : VideoIcon} alt="icon" />,
            publish: <Typography variant="body1" component="p">{item.publish}</Typography>,
            source: <Typography variant="body1" component="p">{item.source}</Typography>,
            likes: <Typography variant="body1" component="p">{item.likes}</Typography>,
            dislike: <Typography variant="body1" component="p">{item.dislikes}</Typography>,
            shares: <Typography variant="body1" component="p">{item.share}</Typography>,
        })
    })
    const columns = [
        { title: 'Category', field: 'category' },
        { title: 'Published', field: 'publish' },
        { title: 'Source', field: 'source' },
        { title: 'Likes', field: 'likes' },
        { title: 'Dislikes', field: 'dislike' },
        { title: 'Shares', field: 'shares' }
    ];
    return (
        <Box>
            <MaterialTable
                columns={columns}
                data={data}
                options={{
                    search: false,
                    showTitle: false,
                    toolbar: false,
                    selection: false,
                    paging: false,
                    tableLayout: 'fixed',
                    sorting: false
                }}
                localization={{
                    body: {
                        emptyDataSourceMessage: (
                            <Typography variant="body1" component="p">
                                Analytics is Empty!
                            </Typography>
                        ),
                    },
                }}
            />
        </Box>
    );
};
export default Overview;

What happened to this? Is the bug still present? Is there a fix for this?

What happened to this? Is the bug still present? Is there a fix for this?

It seems material table will not generate this id for you. It expects a "id" property in the row data and uses that as the unique id. If you have a separate property that provides uniqueness you can use the "idSynonym" option to map to it otherwise you need to generate the 'id' property yourself.
Example:
// the structure of the individual row items
export interface RowItem {
  guid: string;
  message?: string;
  successful: boolean;
  name: string;
}

Here I don't have an 'id' property but I do have the 'guid' that is unique.
<MaterialTable
          title='Items
          options={{
            sorting: true,
            pageSize: 5,
            pageSizeOptions: [5],
            detailPanelType: 'single',
            idSynonym: 'guid',
          }}
...

In here I use the 'idSynonym' option to use 'guid' as the unique id property.
See the type declarations for idSynonym: https://github.com/material-table-core/core/blob/d8fb7db073cd2b2f55c05289816dc2f8bcd168db/types/index.d.ts#L358


support some queries on farms endpoint

required for https://github.com/threefoldtech/tfgrid-sdk-ts/issues/491

[ ] node status
[ ] node rented by (twin id)
[ ] node certified
[ ] node has gpu
[ ] has nodes available for (twin id)

@MarioBassem please create a ticket to upgrade the proxy


Update git-workflow.md

clearing up reviewer / assignation confusion. feel free to edit this text if it's not as clear as it should be.

@stevecurtis bumping this. i can implement this for you if you want.

@stevecurtis please implement (update this commit) with language equal or similar to what @kevwalsh wrote, and your PR will be accepted.


Compile src to dist as commonjs modules.

Should we use dist/commonjs or maybe src/commonjs? Right now I'm using dist which is not that nice since we are all moving to an ES module world and commonjs modules will hopefully go away.

@johnjbarton I can squash all these PRs into one if you prefer?
@guybedford Does this solve your issue?

Another thing to consider is to require Node 5 and disable transformations that are natively supported there.

One more option would be to publish these as a different npm package... but I don't like that... Do you?

@johnjbarton PTAL
I changed it to compile to dist/commonjs since that leaves us more room for other output formats in the future.

yes I think the dist version is better, LGTM

@johnjbarton Your content is a bit unclear to me; "dist version" as in dist/ or "dist version" as in dist/commonjs/?

sorry, I meant your last change, with the sub-dir.
On Wed, Jan 27, 2016 at 8:58 AM, Erik Arvidsson<EMAIL_ADDRESS>wrote:

@johnjbarton https://github.com/johnjbarton Your content is a bit
unclear to me; "dist version" as in dist/ or "dist version" as in
dist/commonjs/?
—
Reply to this email directly or view it on GitHub
https://github.com/google/traceur-compiler/pull/2065#issuecomment-175742640
.

@johnjbarton I think I need to update the npm script version too... We should remove the make version once we resolved the current snafus.


Running cargo make serve on Windows fails

I've forked your template and trying to run on web 'as-is'. It finishes compilation and then unfortunately fails with this:
   ...
   Replacing C:\Users\username\.cargo\bin\wasm2es6js.exe
    Replaced package `wasm-bindgen-cli v0.2.69` with `wasm-bindgen-cli v0.2.69` (executables `wasm-bindgen-test-runner.exe`, `wasm-bindgen.exe`,
`wasm2es6js.exe`)
[cargo-make] INFO - Execute Command: "wasm-bindgen" "--out-dir" "target/wasm32-unknown-unknown/release/" "--out-name" "wasm" "--target" "web" "--no-typescript" "target/wasm32-unknown-unknown/release/bevy_game.wasm"
[cargo-make] INFO - Execute Command: "mkdir" "-p" "build/web/target"
[cargo-make] ERROR - Error while executing command, error: Os {
    code: 2,
    kind: NotFound,
    message: "The system cannot find the file specified.",
}

I think it's something trivial, but I can't figure it out.

Hey, thanks for raising the issue.
I am currently settign up my windows PC to be able to test this myself, but it looks like the mkdir command just needs to be different for Windows.

I tried to run the command separately and it didn't complain. Thanks for helping out!

 In my case the command worked out of the box. I have very little experience with commands on Windows, so I am not sure how to change it to be more compatible.

I tried to run the command separately and it didn't complain.
Do you mean you ran the mkdir command as is outside of the cargo-make task? Or did you run several mkdir commands always just creating one subdirectory?

I ran it outside of the scripts 😀   I'll do a clean download of your template and try everything again.

Nah, same thing. How would you suggest to debug this 🧐 ? Quite annoying to wait for a whole minute for everything to compile just to get this error.

This seems to be a simple issue, but to be honest I have no idea what mkdir on windows actually does/can do. Seems that there are a lot of possible different setups here (actually "works on my Win10 machine" ^^).
Maybe you could try some small changes like build/web/target -> ./build/web/target? I don't think you need to do a clean download of the template every time. Just make sure to not have the build/web directory, then the situation should be the same as for a fresh download.

Same error for me on Win10 running Windows Terminal/Powershell/Starship prompt. I've tried
[tasks.create-build-dir]
args = ["./build/web/target"]
command = "mkdir"

and
[tasks.create-build-dir]
args = ["-p", "./build/web/target"]
command = "mkdir"

Running either mkdir command directly from the command line in the project root creates the folders as expected.

Hey @NiklasEi, I emailed you recently, not sure if you mind.

This works though
[tasks.create-build-dir]
script_runner = "@duckscript"
script = [
'''
p = canonicalize "build/web/target"
mkdir ${p}
''']

I tested this and for me, it also works. I will push this and maybe @rgripper can very, that this also solves the issue on his machine?

It seems there are some weird path things on windows. I had to replace all the cp and mv commands with this before it worked.

[tasks.copy-files-for-release]
script_runner = "@duckscript"
script = [
'''
target = set "./build/web/target"
web = set "./build/web"
windows = set "./build/windows"

echo "Creating ${target}"
rm -r ${web}
mkdir ${target}

echo "Copying ${windows}/icon.ico to ${web}/icon.ico"
cp ${windows}/icon.ico ${web}/icon.ico
echo "Moving ${web}/icon.ico to ${web}/favicon.ico"
mv ${web}/icon.ico ${web}/favicon.ico

echo "Copying ${TARGET_DIR}${CARGO_MAKE_CRATE_NAME}.wasm to ${target}"
cp ${TARGET_DIR}${CARGO_MAKE_CRATE_NAME}.wasm ${target}/${CARGO_MAKE_CRATE_NAME}.wasm

echo "Copying ${TARGET_DIR}wasm.js to ${target}"
cp ${TARGET_DIR}wasm.js ${target}/wasm.js

echo "Copying ${TARGET_DIR}wasm_bg.wasm to ${target}"
cp ${TARGET_DIR}wasm_bg.wasm ${target}/wasm_bg.wasm

echo "Copying ./index.html to ${web}"
cp ./index.html ${web}/index.html

echo "Copying ./assets to ${web}"
cp ./assets ${web}

echo "Copying ./credits to ${web}"
cp ./credits ${web}
''']

don't have windows myself, but this is a strange one.
a task with a command + args is basically like running rust std::process::Command which i probably behaves differently than running the command inside a shell.
however, the question is this running inside a linux subsystem?
because i see an example of:
[tasks.create-build-dir]
args = ["-p", "${CARGO_MAKE_WORKING_DIRECTORY}/build/web/target"]
command = "mkdir"
dependencies = ["echo-path"]

and i'm not sure dos knows what -p is (could be wrong).

I can confirm that the issue appears in all cp, mv and mkdir commands on Windows when run from cargo make serve.

However, all of the commands (except for mkdir's -p) work when executed manually outside the make.
The workaround https://github.com/NiklasEi/bevy_game_template/issues/7#issuecomment-830876426 solves the issue.

i suddenly remembered something about mkdir on windows.... the reason you cant run commands like mkdir on windows, is because its an internal cmd command and not a standalone executable.
meaning, it only works when inside a windows shell environment.
duckscript is indeed the way to go forward since it provides a real cross platform api.

Resolved using the script @will-hart proposed

Link to the relevant PR: #10.


Browser Window Opens but No Content

I'm running
livedown start ./README.md --open --verbose
which opens a new tab in Chrome which appears empty.
The url is
http://localhost:1337/
Sanity Check
less ./README.md displays the content of the file, leading me to believe my file path is correct
Setup

Chrome 39.0
OS X 10.9.5

Console Errors
In the Chrome developer console, I'm seeing
Failed to load resource: net::ERR_CONNECTION_REFUSED  http://localhost/socket.io/?EIO=3&transport=polling&t=1422024891424-0

This error is repeated multiple times.

Looking at the line
http://localhost/socket.io/?EIO=3&transport=polling&t=1422024891424-0

it appears the port (1337 in this example) is missing.

I'm experiencing this as well (through the use of the vim plugin) and am a little wary of not knowing the cause. It seems like this broke for at least the three of us for no reason. I haven't updated the package or plugin and am curious about why it stopped working all of a sudden. Maybe it has to do with side effects relating an upgrade of one of the dependencies?

I think the use of ^'s in package.json is the problem. I just removed them all in my local copy of livedown and ran npm install to get the exact version numbers. Things are back to normal now. Rooting through now to figure out exactly which dependency is causing the issue.

So the culprit is socket.io version 1.3.2, which really just updates socket.io-client to it's version 1.3.2. @mgrubb, your patch probably addresses that exact issue, but I can't look at it at this moment.
In the mean time, my workaround is to specify the exact version number in the livedown package.json where it's installed. In my case:
$ cd ~/.nvm/v0.10.28/lib/node_modules/livedown
$ vim package.json

# edit the version of socket.io to be "1.3.1", save and quit

$ rm -rf node_modules
$ npm install

I wish what I did was as elegant as that :)
I just hacked a template handler into server.js to substitute the url
into index.html.

Jonathan Freeman<EMAIL_ADDRESS>January 26, 2015 at 5:28 PM
So the culprit is |socket.io| version 1.3.2, which really just updates
|socket.io-client| to it's version 1.3.2
https://github.com/Automattic/socket.io-client/commit/ea9b2b72ad989dd0a4df420973a33f33a53dbc77.
@mgrubb https://github.com/mgrubb, your patch probably addresses
that exact issue, but I can't look at it at this moment.
In the mean time, my workaround is to specify the exact version number
in the livedown |package.json| where it's installed. In my case:
|$ cd ~/.nvm/v0.10.28/lib/node_modules/livedown
$ vim package.json
edit the version of socket.io to be "1.3.1", save and quit
$ rm -rf node_modules
$ npm install
|
—
Reply to this email directly or view it on GitHub
https://github.com/shime/livedown/issues/9#issuecomment-71560797.

@shime I see you've fixed this with #11
When you have a chance would you please tag a new release and push it to npm?
Thanks.

Sure, thanks for the ping!

@shime thanks for the quick response, I see 1.0.8 tagged here on GitHub but I'm still seeing 1.0.7 on
npm

@salcode forgot to publish it on NPM again. It's up now, thanks!

@shime Awesome, thank you.


notebook template updates

Pinging @haticekaratay and @camipacifici for additional updates.
(I know this is mast_notebooks; once we agree on the final template, I will merge it into style_guides)

@camipacifici comments addressed.
For the merger into style_guides, we ought to point the source image to the style guide repo, instead of the deprecated generic "notebooks" repo. (also, the style guide has a very low-resolution version of the image, so we'll have to swap that out too)


comparison operators declare wrong result_type

Hi,
In functional/operators.hpp we have
BOOST_COMPUTE_DECLARE_BINARY_OPERATOR(equal_to, "==", T, T) BOOST_COMPUTE_DECLARE_BINARY_OPERATOR(not_equal_to, "!=", T, T) BOOST_COMPUTE_DECLARE_BINARY_OPERATOR(greater, ">", T, T) BOOST_COMPUTE_DECLARE_BINARY_OPERATOR(less, "<", T, T) BOOST_COMPUTE_DECLARE_BINARY_OPERATOR(greater_equal, ">=", T, T) BOOST_COMPUTE_DECLARE_BINARY_OPERATOR(less_equal, "<=", T, T)
declaring a return type T of those functions. Note that the opencl specs says in 6.3 d) (among other things):

The relational operators greater than (>), less than (<), greater than or equal (>=), and less than or equal (<=) operate on scalar and vector types. If the source operands are a vector float, the result is a vector signed integer.

Yes, technically you are completely right. However, I have to add that it should not result in any bug when using Boost.Compute since those operators are later included (inlined like any other function) in generated OpenCL kernel/s (for example in kernels used in boost::compute::sort() algorithm) and result_type is deduced, or rather specified, on the OpenCL side.
vector<float4_>input1, input2;
// fill the inputs
vector<int4_> output;
transform(
    input1.begin(), input1.end(), input2.begin(), output.begin(), greater<float_4>(), queue
);
// this will be essentially evaluated to
// output[index] = ((input1[index]) > (input2[index]));
// and there will be no conversion int4 -> float4 -> float2
// one could assume would happen since result_type of greater<float_4>() is float4_

I don't know if making those operators objects (like greater<float_4>()) more "type-accurate" on C++ side would make any difference.

On the other hand, it's better to have the right type, maybe someone will try to deduce something from the result_type of the function.. What do you think?

In my current application I am going to use it for type deduction (e.g. it could mess up when I want to count the number of elements in a vector that are larger than elements in another vector. This would certainly produce a warning when the result is a float).
Note that the exact rules outlined by the standard are a bit more complicated, e.g. it is not always int but sometimes a smaller or larger integer type. While i would be very happy to get "some" integer type, the exact rules might be more tedious to implement.

In that case I'll fix it soon! I don't have time for this today, but I'll look into it tomorrow morning.

don't worry i can likely only pick it up with the next boost releas eincluding it. So no stress!


Detect and track large files automatically

When pushing sentence-transformers models to the hub, I had the issue that tokenizers for some multilingual transformers models were creating a unigram.json file that is larger 10 MB. The push to the hub / git resulted in an error, due to the file limit size of 10 MB.
remote: -------------------------------------------------------------------------
remote: Your push was rejected because it contains files larger than 10M.
remote: Please use https://git-lfs.github.com/ to store larger files.
remote: -------------------------------------------------------------------------
remote: Offending files:
remote:  - unigram.json (ref: refs/heads/main)
To https://huggingface.co/sentence-transformers/paraphrase-multilingual-MiniLM-L12-v2
 ! [remote rejected] main -> main (pre-receive hook declined)
error: Fehler beim Versenden einiger Referenzen nach 'https://huggingface.co/sentence-transformers/paraphrase-multilingual-MiniLM-L12-v2'

I currently test a fix to detect large files in a repo and to add them to git-lfs before the push:
https://github.com/UKPLab/sentence-transformers/blob/695f12f9a7839e3697957271bbc9108caaf24ca8/sentence_transformers/SentenceTransformer.py#L525
I think this could be relevant for other libraries and also for transformers as well, when someone tries to push tokenizers files that are larger then 10MB.
In the best case, files larger than 10MB should be detected automatically and pushed to git-lfs.

sounds reasonable to me to have this (as an option or by default) in Repository.push_to_hub but interested in others' thoughts.
(ideally, not adding the same pattern multiple times if it's already in .gitattributes, etc)

I think this should be the default. The Repository.push_to_hub already adds everything with git_add, so I think it should also track everything large that it adds.
https://github.com/huggingface/huggingface_hub/blob/0d185de837846859668a0ee5b1aa5ef71a4f9ac4/src/huggingface_hub/repository.py#L452-L460
I think it would make it too complex if I need to pass what-to-track into PretrainedModel.save_pretrained().
Users can add, track, commit themselves if they don't like to track everything.

Fixing this in https://github.com/huggingface/huggingface_hub/pull/177


Scheme submission: Zr

{
"notes": "Developed at LLNL, USA with SHG TiSas",
"references": [
{
"author": "Raiwa and Savina",
"id": "https://doi.org/10.1039/D4JA00065J",
"year": 2024
}
],
"rims_scheme": {
"scheme": {
"element": "Zr",
"gs_level": "0",
"gs_term": "$4d^{2}5s^{2} (^{3}F_{2})$",
"ip_term": "",
"lasers": "Ti:Sa",
"last_step_to_ip": false,
"step_forbidden0": false,
"step_forbidden1": false,
"step_level0": "378.16",
"step_level1": "369.727",
"step_lowlying0": false,
"step_lowlying1": false,
"step_term0": "$4d^{2}5s(a^{2}D)^{5}p (^{3}F_{3}$)",
"step_term1": "Rydberg",
"trans_strength0": "",
"trans_strength1": "",
"unit": "nm"
}
},
"saturation_curves": [
{
"data": {
"x": [
0.0,
30000.0,
40000.0,
110000.0,
180000.0,
290000.0,
440000.0,
660000.0,
1150000.0,
4480000.0
],
"x_err": [
0.0,
2000.0,
2000.0,
5000.0,
9000.0,
14000.0,
22000.0,
33000.0,
58000.0,
224000.0
],
"y": [
0.0,
0.48,
0.663,
0.871,
0.849,
0.959,
0.847,
0.913,
0.985,
1.0
],
"y_err": [
4e-05,
0.00205,
0.00256,
0.00312,
0.00306,
0.00334,
0.00305,
0.00323,
0.00341,
0.00345
]
},
"fit": true,
"notes": "- Zr-90 normalized to 1.\n- Measured on LION at LLNL.  TiSa system.\n- FES Beam focus 1.2 x 1.4 mm, 1000 Hz, 6.9 ns Pulsewidth.\n- SES set to 369.730 nm ",
"title": "FES ",
"unit": "W * cm^-2"
},
{
"data": {
"x": [
0.0,
84000.0,
337000.0,
631000.0,
1157000.0,
1789000.0,
2210000.0,
2273000.0,
5261000.0
],
"x_err": [
0.0,
4000.0,
17000.0,
32000.0,
58000.0,
89000.0,
110000.0,
114000.0,
263000.0
],
"y": [
0.0001,
0.0247,
0.1377,
0.2577,
0.3539,
0.4396,
0.6087,
0.6673,
1.0
],
"y_err": [
0.0,
0.0004,
0.0011,
0.0016,
0.0019,
0.0022,
0.0027,
0.0029,
0.0039
]
},
"fit": true,
"notes": "- SES beam focused to 1.1 x 1.1 mm, 1000hz, 5ns pulsewidth.\n- Signal Zr-90 normalized to 1.",
"title": "SES",
"unit": "W * cm^-2"
}
],
"submitted_by": "Manuel Raiwa"
}

A few notes (mostly bugs in processing)

Submission mask makes a json error (https://github.com/RIMS-Code/rimsdb_scheme_submission/issues/13)
Put comments in as bullet points
Remove "Draw to IP feature" (https://github.com/RIMS-Code/rimsdb_scheme_submission/issues/14)
Power units were entered in MW/cm2 and not in W/cm2 (need more unit selections in submission mask) (https://github.com/RIMS-Code/rimsdb_scheme_submission/issues/15)
Entry of states should be fixed now. Needs a better description as well.


Minor fix in GrpcCollectionModelBIndingData

Issue describing the changes in this PR
Removing unnecessary  private field from GRPCollectionModelBindingData
Pull request checklist

[ ] My changes do not require documentation changes

[ ] Otherwise: Documentation issue linked to PR

[ ] My changes should not be added to the release notes for the next release

[ ] Otherwise: I've added my notes to release_notes.md

[ ] My changes do not need to be backported to a previous version

[ ] Otherwise: Backport tracked by issue/PR #issue_or_pr

[ ] I have added all required tests (Unit tests, E2E tests)

Additional information
Additional PR information

/check-enforcer evaluate


Release/2.3.0

Summary
Update version.
Issue Type
Starter Names
Additional Information

@saragluna FYI: Build passed in my localhost.

We should make this a draft pull request for now since it's not ready to be merged.


docs: improve functions reference

What's Changed in this PR

Describe the change in this PR

A script to update DataFusion functions:

ruby misc/update_functions.rb [nightly | v0.x]

Adds df_functions.md, which is generated by update_functions.rb and contains all the datafusion functions.
Preview link https://feature-functions.greptime-docs.pages.dev/nightly/reference/sql/df_functions
Tweak functions reference.

Checklist

[ ] Please confirm that all corresponding versions of the documents have been revised.
[ ] Please ensure that the content in summary.yml matches the current document structure when you changed the document structure.
[ ] This change requires follow-up update in localized docs.

Summary by CodeRabbit

Documentation

Updated English and Chinese documentation to provide comprehensive overviews of Datafusion and GreptimeDB functions.
Added detailed descriptions, examples, and related resources for various function categories including aggregate, scalar, window, string, math, date and time, system, and management functions.

I don't recommend translating docs/nightly/zh/reference/sql/functions/df-functions.md, it can't be auto-generated and may be confused. The function in English is suitable and precise. @nicecui


Returning new target based on promise resolution in onBefore not changing transition

This issue tracker is for Bug Reports and Feature Requests only.
Please direct requests for help to StackOverflow.  See http://bit.ly/UIR-SOF for details.
This is a:

[x] Bug Report
[ ] Feature Request
[ ] General Query

My version of UI-Router is: 1.0.6
Bug Report
Current Behavior:
When resolving a promise in an onBefore or onStart hook, if this results in returning a different target state, the transition continues as if there was no change to the target.
Expected Behavior:
onBefore should wait for the promise to resolve and change state if a new target is returned.
Link to Plunker that reproduces the issue:
https://jsfiddle.net/yw19qud6/1/
In this example, if AuthService rejects, you should be redirected to state2 (if that isn't the transition already).

Ugh, I just needed to do a "return auth.isAuthenticated().catch(() => ....)" and it worked.


database/sql: hang when driver panics

Debugging a hang in a program using Go 1.6.
Looks like the sqlite3 driver has buggy cgo usage, which triggers a panic during a call to a driver method with one of the database/sql locks held. The panic invokes some deferred functions higher up the stack without unlocking the lock. Those functions try to get the lock for themselves and deadlock. Looks like maybe database/sql needs to use defer to guard its various calls into the driver.
I started this for the driver.Stmt methods, but there are a lot.
/cc @bradfitz

I fixed the ones that I've seen buggy cgo-based database drivers hit. I think we'll leave the rest for Go 1.7 since these are in some cases actual logic changes to database/sql.


🐛 [firebase_storage] Using getData throws a PlatformException instead of a FirebaseException

Bug report
Describe the bug
When calling getData() on a storage reference and the call fails, a PlatformException is issued instead of it being converted into a FirebaseException like it is done for other methods.
Steps to reproduce
Steps to reproduce the behavior:

Call .getData() on a non existing reference
See the platform exception being thrown

Expected behavior
The call should convert the PlatformException into a FirebaseException like it does for other methods.
Additional context
This is probably related to #8113, if not the same issue.
Additionally, I'm not providing a sample project because I think I found the issue.
If we look at the firebase_storage_platform_interface-4.4.3/lib/src/method_channel/method_channel_reference.dart implementation, and look at the definition of getData we quickly notice the result of the methodCall is directly returned from the function, meaning the encompassing try / catch block is more or less doing nothing.
If we look at other method implementations in this class, we see the futures produced by other method calls are always awaited, thus their PlatformExceptions are correctly converted to a FirebaseException.
https://github.com/firebase/flutterfire/blob/dcf1b22aefa6b3846cff9604ab15fae36d847cd1/packages/firebase_storage/firebase_storage_platform_interface/lib/src/method_channel/method_channel_reference.dart#L142-L160

Thanks for the report. Using the plugin example and using getData() on a reference that doesn't exist throws a PlatformException as reported.

I've just tested this with:
    final ref = FirebaseStorage.instance
              .ref()
              .child('flutter-tests')
              .child('some-image.jpg');
          try {
            final result = await ref.getData();
          } catch (e) {
            print('${e.runtimeType}');
          }

It produced a FirebaseException, this might have something to do with the Storage rework a few months back but it is no longer an issue.


Does not identify child images

This code in the docker-remove-image script:
docker images --filter since=IMAGE_ID

Identifies images created more recently (newer) than the specified image (IMAGE_ID), not child images.

Hmm, that could be a problem.  Thanks for letting me know about this, I'm gonna see what my options are.


Fix incorrect plural "Objects" for all FindGameObjectWithTag references

Hey @oferei, this is a simple typo fix for all 4 of the snippets, per language. :bow:

hey, thanks for the help, but this fix is not perfect. apparently Unity now has two methods: FindObjectOfType and FindObjectsOfType. this wasn't the case in Unity v5.1.0, so it's time to update the package. however, removing FindObjectsOfType (plural) is not right, as this function will exists.
anyway, this package is generated using a process that starts with the crawler that gathers data from the web documentation and then continues with the generator which formats the data for Sublime. so modifying this package manually is useless - any fixes should be done to one of the other projects. please wait until I run the process again for Unity 5.3 and see if that fixes everything. if not, please report an issue.

correction: I mentioned FindObjectOfType when you talked about FindGameObjectWithTag. well, now I'm a bit confused, because FindGameObjectWithTag (singular) seems to work, although it is undocumented.

You‘re right it isn’t documented.
Admittedly, I was following along with a Unity tutorial that used it which was where I learned it. When later using it in my project and your completions package in Sublime, it autocompleted to the plural version and my code broke… so I assumed it was a bug.
I see now it's actually the documented method, and I could have fixed my code by accessing the first item in the list. Either way, I look forward to the Unity 5.3 update. :bow:

coming soon. I may also add the undocumented methods.

enjoy v5.3.1

:beers:


[freeglut] Build error

Package: freeglut:x86-windows -> 3.4.0
Host Environment

Host: x64-windows
Compiler: MSVC 19.0.23026.0
vcpkg-tool version: 2023-08-02-6d13efa755f9b5e101712d210199e4139b4c29f6
vcpkg-scripts version: ad46340bf 2023-08-07 (22 hours ago)

To Reproduce
vcpkg install devil
Failure logs
-- Using cached FreeGLUTProject-freeglut-v3.4.0.tar.gz.
-- Cleaning sources at E:/test/vcpkg/buildtrees/freeglut/src/v3.4.0-fe4645a74b.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source E:/test/vcpkg/downloads/FreeGLUTProject-freeglut-v3.4.0.tar.gz
-- Applying patch x11-dependencies-export.patch
-- Applying patch fix-debug-macro.patch
-- Applying patch no_x64_enforcement.patch
-- Applying patch windows-output-name.patch
-- Using source at E:/test/vcpkg/buildtrees/freeglut/src/v3.4.0-fe4645a74b.clean
-- Configuring x86-windows
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:112 (message):
    Command failed: E:/test/vcpkg/downloads/tools/ninja/1.10.2-windows/ninja.exe -v
    Working Directory: E:/test/vcpkg/buildtrees/freeglut/x86-windows-rel/vcpkg-parallel-configure
    Error code: 1
    See logs for more information:
      E:\test\vcpkg\buildtrees\freeglut\config-x86-windows-dbg-CMakeCache.txt.log
      E:\test\vcpkg\buildtrees\freeglut\config-x86-windows-rel-CMakeCache.txt.log
      E:\test\vcpkg\buildtrees\freeglut\config-x86-windows-out.log

Call Stack (most recent call first):
  installed/x64-windows/share/vcpkg-cmake/vcpkg_cmake_configure.cmake:252 (vcpkg_execute_required_process)
  ports/freeglut/portfile.cmake:23 (vcpkg_cmake_configure)
  scripts/ports.cmake:147 (include)

E:\test\vcpkg\buildtrees\freeglut\config-x86-windows-dbg-CMakeCache.txt.log
# This is the CMakeCache file.
# For build in directory: e:/test/vcpkg/buildtrees/freeglut/x86-windows-dbg
# It was generated by CMake: E:/Program Files/CMake/bin/cmake.exe
# You can edit this file to change values found and used by cmake.
# If you do not want to change any of the values, simply exit the editor.
# If you do want to change a value, simply edit, save, and exit the editor.
# The syntax for the file is as follows:
# KEY:TYPE=VALUE
# KEY is the name of a variable in the cache.
# TYPE is a hint to GUIs for the type of VALUE, DO NOT EDIT TYPE!.
# VALUE is the current value for the KEY.

########################
# EXTERNAL cache entries
########################

//No help, variable specified on the command line.
BUILD_SHARED_LIBS:UNINITIALIZED=ON

//Path to a program.
CMAKE_AR:FILEPATH=E:/Program Files (x86)/Microsoft Visual Studio 14.0/VC/bin/amd64_x86/lib.exe

//Choose the type of build, options are: None Debug Release RelWithDebInfo
// MinSizeRel ...
CMAKE_BUILD_TYPE:STRING=Debug

CMAKE_CROSSCOMPILING:STRING=OFF

CMAKE_CXX_FLAGS:STRING=' /nologo /DWIN32 /D_WINDOWS /W3 /utf-8 /GR /EHsc /MP '

CMAKE_CXX_FLAGS_DEBUG:STRING='/D_DEBUG /MDd /Z7 /Ob0 /Od /RTC1 '

CMAKE_CXX_FLAGS_RELEASE:STRING='/MD /O2 /Oi /Gy /DNDEBUG /Z7 '

//C compiler
CMAKE_C_COMPILER:FILEPATH=E:/Program Files (x86)/Microsoft Visual Studio 14.0/VC/bin/amd64_x86/cl.exe

CMAKE_C_FLAGS:STRING=' /nologo /DWIN32 /D_WINDOWS /W3 /utf-8 /MP '

CMAKE_C_FLAGS_DEBUG:STRING='/D_DEBUG /MDd /Z7 /Ob0 /Od /RTC1 '

//Flags used by the C compiler during MINSIZEREL builds.
CMAKE_C_FLAGS_MINSIZEREL:STRING=/MD /O1 /Ob1 /DNDEBUG

CMAKE_C_FLAGS_RELEASE:STRING='/MD /O2 /Oi /Gy /DNDEBUG /Z7 '

//Flags used by the C compiler during RELWITHDEBINFO builds.
CMAKE_C_FLAGS_RELWITHDEBINFO:STRING=/MD /Zi /O2 /Ob1 /DNDEBUG

//Libraries linked by default with all C applications.
CMAKE_C_STANDARD_LIBRARIES:STRING=kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib

//No help, variable specified on the command line.
CMAKE_ERROR_ON_ABSOLUTE_INSTALL_DESTINATION:UNINITIALIZED=ON

//Flags used by the linker during all build types.
CMAKE_EXE_LINKER_FLAGS:STRING=/machine:X86

//Flags used by the linker during DEBUG builds.
CMAKE_EXE_LINKER_FLAGS_DEBUG:STRING=/nologo    /debug /INCREMENTAL

//Flags used by the linker during MINSIZEREL builds.
CMAKE_EXE_LINKER_FLAGS_MINSIZEREL:STRING=/INCREMENTAL:NO

CMAKE_EXE_LINKER_FLAGS_RELEASE:STRING='/nologo /DEBUG /INCREMENTAL:NO /OPT:REF /OPT:ICF  '

//Flags used by the linker during RELWITHDEBINFO builds.
CMAKE_EXE_LINKER_FLAGS_RELWITHDEBINFO:STRING=/debug /INCREMENTAL

//Enable/Disable output of compile commands during generation.
CMAKE_EXPORT_COMPILE_COMMANDS:BOOL=

//No help, variable specified on the command line.
CMAKE_EXPORT_NO_PACKAGE_REGISTRY:UNINITIALIZED=ON

//No help, variable specified on the command line.
CMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY:UNINITIALIZED=ON

//No help, variable specified on the command line.
CMAKE_FIND_PACKAGE_NO_SYSTEM_PACKAGE_REGISTRY:UNINITIALIZED=ON

//Value Computed by CMake.
CMAKE_FIND_PACKAGE_REDIRECTS_DIR:STATIC=E:/test/vcpkg/buildtrees/freeglut/x86-windows-dbg/CMakeFiles/pkgRedirects

//No help, variable specified on the command line.
CMAKE_INSTALL_BINDIR:STRING=bin

//No help, variable specified on the command line.
CMAKE_INSTALL_LIBDIR:STRING=lib

//Install path prefix, prepended onto install directories.
CMAKE_INSTALL_PREFIX:PATH=E:/test/vcpkg/packages/freeglut_x86-windows/debug

//No help, variable specified on the command line.
CMAKE_INSTALL_SYSTEM_RUNTIME_LIBS_SKIP:UNINITIALIZED=TRUE

//Path to a program.
CMAKE_LINKER:FILEPATH=E:/Program Files (x86)/Microsoft Visual Studio 14.0/VC/bin/amd64_x86/link.exe

//No help, variable specified on the command line.
CMAKE_MAKE_PROGRAM:UNINITIALIZED=E:/test/vcpkg/downloads/tools/ninja/1.10.2-windows/ninja.exe

//Flags used by the linker during the creation of modules during
// all build types.
CMAKE_MODULE_LINKER_FLAGS:STRING=/machine:X86

//Flags used by the linker during the creation of modules during
// DEBUG builds.
CMAKE_MODULE_LINKER_FLAGS_DEBUG:STRING=/nologo    /debug /INCREMENTAL

//Flags used by the linker during the creation of modules during
// MINSIZEREL builds.
CMAKE_MODULE_LINKER_FLAGS_MINSIZEREL:STRING=/INCREMENTAL:NO

CMAKE_MODULE_LINKER_FLAGS_RELEASE:STRING='/nologo /DEBUG /INCREMENTAL:NO /OPT:REF /OPT:ICF  '

//Flags used by the linker during the creation of modules during
// RELWITHDEBINFO builds.
CMAKE_MODULE_LINKER_FLAGS_RELWITHDEBINFO:STRING=/debug /INCREMENTAL

CMAKE_MSVC_RUNTIME_LIBRARY:STRING=MultiThreaded$<$<CONFIG:Debug>:Debug>$<$<STREQUAL:dynamic,dynamic>:DLL>

//Path to a program.
CMAKE_MT:FILEPATH=CMAKE_MT-NOTFOUND

//Value Computed by CMake
CMAKE_PROJECT_DESCRIPTION:STATIC=

//Value Computed by CMake
CMAKE_PROJECT_HOMEPAGE_URL:STATIC=

//Value Computed by CMake
CMAKE_PROJECT_NAME:STATIC=freeglut

//RC compiler
CMAKE_RC_COMPILER:FILEPATH=rc

CMAKE_RC_FLAGS:STRING=-c65001 /DWIN32

//Flags for Windows Resource Compiler during DEBUG builds.
CMAKE_RC_FLAGS_DEBUG:STRING=-D_DEBUG

//Flags for Windows Resource Compiler during MINSIZEREL builds.
CMAKE_RC_FLAGS_MINSIZEREL:STRING=

//Flags for Windows Resource Compiler during RELEASE builds.
CMAKE_RC_FLAGS_RELEASE:STRING=

//Flags for Windows Resource Compiler during RELWITHDEBINFO builds.
CMAKE_RC_FLAGS_RELWITHDEBINFO:STRING=

//Flags used by the linker during the creation of shared libraries
// during all build types.
CMAKE_SHARED_LINKER_FLAGS:STRING=/machine:X86

//Flags used by the linker during the creation of shared libraries
// during DEBUG builds.
CMAKE_SHARED_LINKER_FLAGS_DEBUG:STRING=/nologo    /debug /INCREMENTAL

//Flags used by the linker during the creation of shared libraries
// during MINSIZEREL builds.
CMAKE_SHARED_LINKER_FLAGS_MINSIZEREL:STRING=/INCREMENTAL:NO

CMAKE_SHARED_LINKER_FLAGS_RELEASE:STRING='/nologo /DEBUG /INCREMENTAL:NO /OPT:REF /OPT:ICF  '

//Flags used by the linker during the creation of shared libraries
// during RELWITHDEBINFO builds.
CMAKE_SHARED_LINKER_FLAGS_RELWITHDEBINFO:STRING=/debug /INCREMENTAL

//If set, runtime paths are not added when installing shared libraries,
// but are added when building.
CMAKE_SKIP_INSTALL_RPATH:BOOL=NO

//If set, runtime paths are not added when using shared libraries.
CMAKE_SKIP_RPATH:BOOL=NO

//Flags used by the linker during the creation of static libraries
// during all build types.
CMAKE_STATIC_LINKER_FLAGS:STRING=/machine:X86

//Flags used by the linker during the creation of static libraries
// during DEBUG builds.
CMAKE_STATIC_LINKER_FLAGS_DEBUG:STRING=/nologo

//Flags used by the linker during the creation of static libraries
// during MINSIZEREL builds.
CMAKE_STATIC_LINKER_FLAGS_MINSIZEREL:STRING=

//Flags used by the linker during the creation of static libraries
// during RELEASE builds.
CMAKE_STATIC_LINKER_FLAGS_RELEASE:STRING=/nologo

//Flags used by the linker during the creation of static libraries
// during RELWITHDEBINFO builds.
CMAKE_STATIC_LINKER_FLAGS_RELWITHDEBINFO:STRING=

CMAKE_SYSTEM_NAME:STRING=Windows

CMAKE_SYSTEM_PROCESSOR:STRING=x86

CMAKE_SYSTEM_VERSION:STRING=10.0.19045

//The CMake toolchain file
CMAKE_TOOLCHAIN_FILE:FILEPATH=E:/test/vcpkg/scripts/buildsystems/vcpkg.cmake

//If this value is on, makefiles will be generated without the
// .SILENT directive, and all commands will be echoed to the console
// during the make.  This is useful for debugging only. With Visual
// Studio IDE projects all commands are done without /nologo.
CMAKE_VERBOSE_MAKEFILE:BOOL=ON

//No help, variable specified on the command line.
FETCHCONTENT_FULLY_DISCONNECTED:UNINITIALIZED=ON

//No help, variable specified on the command line.
FREEGLUT_BUILD_DEMOS:UNINITIALIZED=OFF

//No help, variable specified on the command line.
FREEGLUT_BUILD_SHARED_LIBS:UNINITIALIZED=1

//No help, variable specified on the command line.
FREEGLUT_BUILD_STATIC_LIBS:UNINITIALIZED=0

//No help, variable specified on the command line.
FREEGLUT_REPLACE_GLUT:UNINITIALIZED=ON

//No help, variable specified on the command line.
INSTALL_PDB:UNINITIALIZED=OFF

//Automatically copy dependencies into the output directory for
// executables.
VCPKG_APPLOCAL_DEPS:BOOL=OFF

//No help, variable specified on the command line.
VCPKG_CHAINLOAD_TOOLCHAIN_FILE:UNINITIALIZED=E:/test/vcpkg/scripts/toolchains/windows.cmake

//No help, variable specified on the command line.
VCPKG_CRT_LINKAGE:UNINITIALIZED=dynamic

//No help, variable specified on the command line.
VCPKG_CXX_FLAGS:UNINITIALIZED=

//No help, variable specified on the command line.
VCPKG_CXX_FLAGS_DEBUG:UNINITIALIZED=

//No help, variable specified on the command line.
VCPKG_CXX_FLAGS_RELEASE:UNINITIALIZED=

//No help, variable specified on the command line.
VCPKG_C_FLAGS:UNINITIALIZED=

//No help, variable specified on the command line.
VCPKG_C_FLAGS_DEBUG:UNINITIALIZED=

//No help, variable specified on the command line.
VCPKG_C_FLAGS_RELEASE:UNINITIALIZED=

//The directory which contains the installed libraries for each
// triplet
VCPKG_INSTALLED_DIR:PATH=E:/test/vcpkg/installed

//No help, variable specified on the command line.
VCPKG_LINKER_FLAGS:UNINITIALIZED=

//No help, variable specified on the command line.
VCPKG_LINKER_FLAGS_DEBUG:UNINITIALIZED=

//No help, variable specified on the command line.
VCPKG_LINKER_FLAGS_RELEASE:UNINITIALIZED=

//The path to the vcpkg manifest directory.
VCPKG_MANIFEST_DIR:PATH=

//Use manifest mode, as opposed to classic mode.
VCPKG_MANIFEST_MODE:BOOL=OFF

//No help, variable specified on the command line.
VCPKG_PLATFORM_TOOLSET:UNINITIALIZED=v140

//Appends the vcpkg paths to CMAKE_PREFIX_PATH, CMAKE_LIBRARY_PATH
// and CMAKE_FIND_ROOT_PATH so that vcpkg libraries/packages are
// found after toolchain/system libraries/packages.
VCPKG_PREFER_SYSTEM_LIBS:BOOL=OFF

//Enable the setup of CMAKE_PROGRAM_PATH to vcpkg paths
VCPKG_SETUP_CMAKE_PROGRAM_PATH:BOOL=ON

//No help, variable specified on the command line.
VCPKG_SET_CHARSET_FLAG:UNINITIALIZED=ON

//No help, variable specified on the command line.
VCPKG_TARGET_ARCHITECTURE:UNINITIALIZED=x86

//Vcpkg target triplet (ex. x86-windows)
VCPKG_TARGET_TRIPLET:STRING=x86-windows

//Trace calls to find_package()
VCPKG_TRACE_FIND_PACKAGE:BOOL=OFF

//Enables messages from the VCPKG toolchain for debugging purposes.
VCPKG_VERBOSE:BOOL=OFF

//(experimental) Automatically copy dependencies into the install
// target directory for executables. Requires CMake 3.14.
X_VCPKG_APPLOCAL_DEPS_INSTALL:BOOL=OFF

//(experimental) Add USES_TERMINAL to VCPKG_APPLOCAL_DEPS to force
// serialization.
X_VCPKG_APPLOCAL_DEPS_SERIALIZED:BOOL=OFF

//The directory which contains the installed libraries for each
// triplet
_VCPKG_INSTALLED_DIR:PATH=E:/test/vcpkg/installed

//No help, variable specified on the command line.
_VCPKG_ROOT_DIR:UNINITIALIZED=E:/test/vcpkg

//Value Computed by CMake
freeglut_BINARY_DIR:STATIC=E:/test/vcpkg/buildtrees/freeglut/x86-windows-dbg

//Value Computed by CMake
freeglut_IS_TOP_LEVEL:STATIC=ON

//Value Computed by CMake
freeglut_SOURCE_DIR:STATIC=E:/test/vcpkg/buildtrees/freeglut/src/v3.4.0-fe4645a74b.clean

########################
# INTERNAL cache entries
########################

//ADVANCED property for variable: CMAKE_AR
CMAKE_AR-ADVANCED:INTERNAL=1
//This is the directory where this CMakeCache.txt was created
CMAKE_CACHEFILE_DIR:INTERNAL=e:/test/vcpkg/buildtrees/freeglut/x86-windows-dbg
//Major version of cmake used to create the current loaded cache
CMAKE_CACHE_MAJOR_VERSION:INTERNAL=3
//Minor version of cmake used to create the current loaded cache
CMAKE_CACHE_MINOR_VERSION:INTERNAL=27
//Patch version of cmake used to create the current loaded cache
CMAKE_CACHE_PATCH_VERSION:INTERNAL=1
//Path to CMake executable.
CMAKE_COMMAND:INTERNAL=E:/Program Files/CMake/bin/cmake.exe
//Path to cpack program executable.
CMAKE_CPACK_COMMAND:INTERNAL=E:/Program Files/CMake/bin/cpack.exe
//Path to ctest program executable.
CMAKE_CTEST_COMMAND:INTERNAL=E:/Program Files/CMake/bin/ctest.exe
//ADVANCED property for variable: CMAKE_C_COMPILER
CMAKE_C_COMPILER-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_FLAGS
CMAKE_C_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_FLAGS_DEBUG
CMAKE_C_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_FLAGS_MINSIZEREL
CMAKE_C_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_FLAGS_RELEASE
CMAKE_C_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_FLAGS_RELWITHDEBINFO
CMAKE_C_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_STANDARD_LIBRARIES
CMAKE_C_STANDARD_LIBRARIES-ADVANCED:INTERNAL=1
//Path to cache edit program executable.
CMAKE_EDIT_COMMAND:INTERNAL=E:/Program Files/CMake/bin/cmake-gui.exe
//Executable file format
CMAKE_EXECUTABLE_FORMAT:INTERNAL=Unknown
//ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS
CMAKE_EXE_LINKER_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_DEBUG
CMAKE_EXE_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_MINSIZEREL
CMAKE_EXE_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_RELEASE
CMAKE_EXE_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_RELWITHDEBINFO
CMAKE_EXE_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_EXPORT_COMPILE_COMMANDS
CMAKE_EXPORT_COMPILE_COMMANDS-ADVANCED:INTERNAL=1
//Name of external makefile project generator.
CMAKE_EXTRA_GENERATOR:INTERNAL=
//Name of generator.
CMAKE_GENERATOR:INTERNAL=Ninja
//Generator instance identifier.
CMAKE_GENERATOR_INSTANCE:INTERNAL=
//Name of generator platform.
CMAKE_GENERATOR_PLATFORM:INTERNAL=
//Name of generator toolset.
CMAKE_GENERATOR_TOOLSET:INTERNAL=
//Source directory with the top level CMakeLists.txt file for this
// project
CMAKE_HOME_DIRECTORY:INTERNAL=E:/test/vcpkg/buildtrees/freeglut/src/v3.4.0-fe4645a74b.clean
//ADVANCED property for variable: CMAKE_LINKER
CMAKE_LINKER-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS
CMAKE_MODULE_LINKER_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_DEBUG
CMAKE_MODULE_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_MINSIZEREL
CMAKE_MODULE_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_RELEASE
CMAKE_MODULE_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_RELWITHDEBINFO
CMAKE_MODULE_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_MT
CMAKE_MT-ADVANCED:INTERNAL=1
//number of local generators
CMAKE_NUMBER_OF_MAKEFILES:INTERNAL=1
//Platform information initialized
CMAKE_PLATFORM_INFO_INITIALIZED:INTERNAL=1
//noop for ranlib
CMAKE_RANLIB:INTERNAL=:
//ADVANCED property for variable: CMAKE_RC_COMPILER
CMAKE_RC_COMPILER-ADVANCED:INTERNAL=1
CMAKE_RC_COMPILER_WORKS:INTERNAL=1
//ADVANCED property for variable: CMAKE_RC_FLAGS
CMAKE_RC_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_RC_FLAGS_DEBUG
CMAKE_RC_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_RC_FLAGS_MINSIZEREL
CMAKE_RC_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_RC_FLAGS_RELEASE
CMAKE_RC_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_RC_FLAGS_RELWITHDEBINFO
CMAKE_RC_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//Path to CMake installation.
CMAKE_ROOT:INTERNAL=E:/Program Files/CMake/share/cmake-3.27
//ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS
CMAKE_SHARED_LINKER_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_DEBUG
CMAKE_SHARED_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_MINSIZEREL
CMAKE_SHARED_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_RELEASE
CMAKE_SHARED_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_RELWITHDEBINFO
CMAKE_SHARED_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_SKIP_INSTALL_RPATH
CMAKE_SKIP_INSTALL_RPATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_SKIP_RPATH
CMAKE_SKIP_RPATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS
CMAKE_STATIC_LINKER_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_DEBUG
CMAKE_STATIC_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_MINSIZEREL
CMAKE_STATIC_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_RELEASE
CMAKE_STATIC_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_RELWITHDEBINFO
CMAKE_STATIC_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_TOOLCHAIN_FILE
CMAKE_TOOLCHAIN_FILE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_VERBOSE_MAKEFILE
CMAKE_VERBOSE_MAKEFILE-ADVANCED:INTERNAL=1
//Install the dependencies listed in your manifest:
//\n    If this is off, you will have to manually install your dependencies.
//\n    See https://github.com/microsoft/vcpkg/tree/master/docs/specifications/manifests.md
// for more info.
//\n
VCPKG_MANIFEST_INSTALL:INTERNAL=OFF
//ADVANCED property for variable: VCPKG_VERBOSE
VCPKG_VERBOSE-ADVANCED:INTERNAL=1
//Making sure VCPKG_MANIFEST_MODE doesn't change
Z_VCPKG_CHECK_MANIFEST_MODE:INTERNAL=OFF
//Vcpkg root directory
Z_VCPKG_ROOT_DIR:INTERNAL=E:/test/vcpkg

E:\test\vcpkg\buildtrees\freeglut\config-x86-windows-rel-CMakeCache.txt.log
# This is the CMakeCache file.
# For build in directory: e:/test/vcpkg/buildtrees/freeglut/x86-windows-rel
# It was generated by CMake: E:/Program Files/CMake/bin/cmake.exe
# You can edit this file to change values found and used by cmake.
# If you do not want to change any of the values, simply exit the editor.
# If you do want to change a value, simply edit, save, and exit the editor.
# The syntax for the file is as follows:
# KEY:TYPE=VALUE
# KEY is the name of a variable in the cache.
# TYPE is a hint to GUIs for the type of VALUE, DO NOT EDIT TYPE!.
# VALUE is the current value for the KEY.

########################
# EXTERNAL cache entries
########################

//No help, variable specified on the command line.
BUILD_SHARED_LIBS:UNINITIALIZED=ON

//Path to a program.
CMAKE_AR:FILEPATH=E:/Program Files (x86)/Microsoft Visual Studio 14.0/VC/bin/amd64_x86/lib.exe

//Choose the type of build, options are: None Debug Release RelWithDebInfo
// MinSizeRel ...
CMAKE_BUILD_TYPE:STRING=Release

CMAKE_CROSSCOMPILING:STRING=OFF

CMAKE_CXX_FLAGS:STRING=' /nologo /DWIN32 /D_WINDOWS /W3 /utf-8 /GR /EHsc /MP '

CMAKE_CXX_FLAGS_DEBUG:STRING='/D_DEBUG /MDd /Z7 /Ob0 /Od /RTC1 '

CMAKE_CXX_FLAGS_RELEASE:STRING='/MD /O2 /Oi /Gy /DNDEBUG /Z7 '

//C compiler
CMAKE_C_COMPILER:FILEPATH=E:/Program Files (x86)/Microsoft Visual Studio 14.0/VC/bin/amd64_x86/cl.exe

CMAKE_C_FLAGS:STRING=' /nologo /DWIN32 /D_WINDOWS /W3 /utf-8 /MP '

CMAKE_C_FLAGS_DEBUG:STRING='/D_DEBUG /MDd /Z7 /Ob0 /Od /RTC1 '

//Flags used by the C compiler during MINSIZEREL builds.
CMAKE_C_FLAGS_MINSIZEREL:STRING=/MD /O1 /Ob1 /DNDEBUG

CMAKE_C_FLAGS_RELEASE:STRING='/MD /O2 /Oi /Gy /DNDEBUG /Z7 '

//Flags used by the C compiler during RELWITHDEBINFO builds.
CMAKE_C_FLAGS_RELWITHDEBINFO:STRING=/MD /Zi /O2 /Ob1 /DNDEBUG

//Libraries linked by default with all C applications.
CMAKE_C_STANDARD_LIBRARIES:STRING=kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib

//No help, variable specified on the command line.
CMAKE_ERROR_ON_ABSOLUTE_INSTALL_DESTINATION:UNINITIALIZED=ON

//Flags used by the linker during all build types.
CMAKE_EXE_LINKER_FLAGS:STRING=/machine:X86

//Flags used by the linker during DEBUG builds.
CMAKE_EXE_LINKER_FLAGS_DEBUG:STRING=/nologo    /debug /INCREMENTAL

//Flags used by the linker during MINSIZEREL builds.
CMAKE_EXE_LINKER_FLAGS_MINSIZEREL:STRING=/INCREMENTAL:NO

CMAKE_EXE_LINKER_FLAGS_RELEASE:STRING='/nologo /DEBUG /INCREMENTAL:NO /OPT:REF /OPT:ICF  '

//Flags used by the linker during RELWITHDEBINFO builds.
CMAKE_EXE_LINKER_FLAGS_RELWITHDEBINFO:STRING=/debug /INCREMENTAL

//Enable/Disable output of compile commands during generation.
CMAKE_EXPORT_COMPILE_COMMANDS:BOOL=

//No help, variable specified on the command line.
CMAKE_EXPORT_NO_PACKAGE_REGISTRY:UNINITIALIZED=ON

//No help, variable specified on the command line.
CMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY:UNINITIALIZED=ON

//No help, variable specified on the command line.
CMAKE_FIND_PACKAGE_NO_SYSTEM_PACKAGE_REGISTRY:UNINITIALIZED=ON

//Value Computed by CMake.
CMAKE_FIND_PACKAGE_REDIRECTS_DIR:STATIC=E:/test/vcpkg/buildtrees/freeglut/x86-windows-rel/CMakeFiles/pkgRedirects

//No help, variable specified on the command line.
CMAKE_INSTALL_BINDIR:STRING=bin

//No help, variable specified on the command line.
CMAKE_INSTALL_LIBDIR:STRING=lib

//Install path prefix, prepended onto install directories.
CMAKE_INSTALL_PREFIX:PATH=E:/test/vcpkg/packages/freeglut_x86-windows

//No help, variable specified on the command line.
CMAKE_INSTALL_SYSTEM_RUNTIME_LIBS_SKIP:UNINITIALIZED=TRUE

//Path to a program.
CMAKE_LINKER:FILEPATH=E:/Program Files (x86)/Microsoft Visual Studio 14.0/VC/bin/amd64_x86/link.exe

//No help, variable specified on the command line.
CMAKE_MAKE_PROGRAM:UNINITIALIZED=E:/test/vcpkg/downloads/tools/ninja/1.10.2-windows/ninja.exe

//Flags used by the linker during the creation of modules during
// all build types.
CMAKE_MODULE_LINKER_FLAGS:STRING=/machine:X86

//Flags used by the linker during the creation of modules during
// DEBUG builds.
CMAKE_MODULE_LINKER_FLAGS_DEBUG:STRING=/nologo    /debug /INCREMENTAL

//Flags used by the linker during the creation of modules during
// MINSIZEREL builds.
CMAKE_MODULE_LINKER_FLAGS_MINSIZEREL:STRING=/INCREMENTAL:NO

CMAKE_MODULE_LINKER_FLAGS_RELEASE:STRING='/nologo /DEBUG /INCREMENTAL:NO /OPT:REF /OPT:ICF  '

//Flags used by the linker during the creation of modules during
// RELWITHDEBINFO builds.
CMAKE_MODULE_LINKER_FLAGS_RELWITHDEBINFO:STRING=/debug /INCREMENTAL

CMAKE_MSVC_RUNTIME_LIBRARY:STRING=MultiThreaded$<$<CONFIG:Debug>:Debug>$<$<STREQUAL:dynamic,dynamic>:DLL>

//Path to a program.
CMAKE_MT:FILEPATH=CMAKE_MT-NOTFOUND

//Value Computed by CMake
CMAKE_PROJECT_DESCRIPTION:STATIC=

//Value Computed by CMake
CMAKE_PROJECT_HOMEPAGE_URL:STATIC=

//Value Computed by CMake
CMAKE_PROJECT_NAME:STATIC=freeglut

//RC compiler
CMAKE_RC_COMPILER:FILEPATH=rc

CMAKE_RC_FLAGS:STRING=-c65001 /DWIN32

//Flags for Windows Resource Compiler during DEBUG builds.
CMAKE_RC_FLAGS_DEBUG:STRING=-D_DEBUG

//Flags for Windows Resource Compiler during MINSIZEREL builds.
CMAKE_RC_FLAGS_MINSIZEREL:STRING=

//Flags for Windows Resource Compiler during RELEASE builds.
CMAKE_RC_FLAGS_RELEASE:STRING=

//Flags for Windows Resource Compiler during RELWITHDEBINFO builds.
CMAKE_RC_FLAGS_RELWITHDEBINFO:STRING=

//Flags used by the linker during the creation of shared libraries
// during all build types.
CMAKE_SHARED_LINKER_FLAGS:STRING=/machine:X86

//Flags used by the linker during the creation of shared libraries
// during DEBUG builds.
CMAKE_SHARED_LINKER_FLAGS_DEBUG:STRING=/nologo    /debug /INCREMENTAL

//Flags used by the linker during the creation of shared libraries
// during MINSIZEREL builds.
CMAKE_SHARED_LINKER_FLAGS_MINSIZEREL:STRING=/INCREMENTAL:NO

CMAKE_SHARED_LINKER_FLAGS_RELEASE:STRING='/nologo /DEBUG /INCREMENTAL:NO /OPT:REF /OPT:ICF  '

//Flags used by the linker during the creation of shared libraries
// during RELWITHDEBINFO builds.
CMAKE_SHARED_LINKER_FLAGS_RELWITHDEBINFO:STRING=/debug /INCREMENTAL

//If set, runtime paths are not added when installing shared libraries,
// but are added when building.
CMAKE_SKIP_INSTALL_RPATH:BOOL=NO

//If set, runtime paths are not added when using shared libraries.
CMAKE_SKIP_RPATH:BOOL=NO

//Flags used by the linker during the creation of static libraries
// during all build types.
CMAKE_STATIC_LINKER_FLAGS:STRING=/machine:X86

//Flags used by the linker during the creation of static libraries
// during DEBUG builds.
CMAKE_STATIC_LINKER_FLAGS_DEBUG:STRING=/nologo

//Flags used by the linker during the creation of static libraries
// during MINSIZEREL builds.
CMAKE_STATIC_LINKER_FLAGS_MINSIZEREL:STRING=

//Flags used by the linker during the creation of static libraries
// during RELEASE builds.
CMAKE_STATIC_LINKER_FLAGS_RELEASE:STRING=/nologo

//Flags used by the linker during the creation of static libraries
// during RELWITHDEBINFO builds.
CMAKE_STATIC_LINKER_FLAGS_RELWITHDEBINFO:STRING=

CMAKE_SYSTEM_NAME:STRING=Windows

CMAKE_SYSTEM_PROCESSOR:STRING=x86

CMAKE_SYSTEM_VERSION:STRING=10.0.19045

//The CMake toolchain file
CMAKE_TOOLCHAIN_FILE:FILEPATH=E:/test/vcpkg/scripts/buildsystems/vcpkg.cmake

//If this value is on, makefiles will be generated without the
// .SILENT directive, and all commands will be echoed to the console
// during the make.  This is useful for debugging only. With Visual
// Studio IDE projects all commands are done without /nologo.
CMAKE_VERBOSE_MAKEFILE:BOOL=ON

//No help, variable specified on the command line.
FETCHCONTENT_FULLY_DISCONNECTED:UNINITIALIZED=ON

//No help, variable specified on the command line.
FREEGLUT_BUILD_DEMOS:UNINITIALIZED=OFF

//No help, variable specified on the command line.
FREEGLUT_BUILD_SHARED_LIBS:UNINITIALIZED=1

//No help, variable specified on the command line.
FREEGLUT_BUILD_STATIC_LIBS:UNINITIALIZED=0

//No help, variable specified on the command line.
FREEGLUT_REPLACE_GLUT:UNINITIALIZED=ON

//No help, variable specified on the command line.
INSTALL_PDB:UNINITIALIZED=OFF

//Automatically copy dependencies into the output directory for
// executables.
VCPKG_APPLOCAL_DEPS:BOOL=OFF

//No help, variable specified on the command line.
VCPKG_CHAINLOAD_TOOLCHAIN_FILE:UNINITIALIZED=E:/test/vcpkg/scripts/toolchains/windows.cmake

//No help, variable specified on the command line.
VCPKG_CRT_LINKAGE:UNINITIALIZED=dynamic

//No help, variable specified on the command line.
VCPKG_CXX_FLAGS:UNINITIALIZED=

//No help, variable specified on the command line.
VCPKG_CXX_FLAGS_DEBUG:UNINITIALIZED=

//No help, variable specified on the command line.
VCPKG_CXX_FLAGS_RELEASE:UNINITIALIZED=

//No help, variable specified on the command line.
VCPKG_C_FLAGS:UNINITIALIZED=

//No help, variable specified on the command line.
VCPKG_C_FLAGS_DEBUG:UNINITIALIZED=

//No help, variable specified on the command line.
VCPKG_C_FLAGS_RELEASE:UNINITIALIZED=

//The directory which contains the installed libraries for each
// triplet
VCPKG_INSTALLED_DIR:PATH=E:/test/vcpkg/installed

//No help, variable specified on the command line.
VCPKG_LINKER_FLAGS:UNINITIALIZED=

//No help, variable specified on the command line.
VCPKG_LINKER_FLAGS_DEBUG:UNINITIALIZED=

//No help, variable specified on the command line.
VCPKG_LINKER_FLAGS_RELEASE:UNINITIALIZED=

//The path to the vcpkg manifest directory.
VCPKG_MANIFEST_DIR:PATH=

//Use manifest mode, as opposed to classic mode.
VCPKG_MANIFEST_MODE:BOOL=OFF

//No help, variable specified on the command line.
VCPKG_PLATFORM_TOOLSET:UNINITIALIZED=v140

//Appends the vcpkg paths to CMAKE_PREFIX_PATH, CMAKE_LIBRARY_PATH
// and CMAKE_FIND_ROOT_PATH so that vcpkg libraries/packages are
// found after toolchain/system libraries/packages.
VCPKG_PREFER_SYSTEM_LIBS:BOOL=OFF

//Enable the setup of CMAKE_PROGRAM_PATH to vcpkg paths
VCPKG_SETUP_CMAKE_PROGRAM_PATH:BOOL=ON

//No help, variable specified on the command line.
VCPKG_SET_CHARSET_FLAG:UNINITIALIZED=ON

//No help, variable specified on the command line.
VCPKG_TARGET_ARCHITECTURE:UNINITIALIZED=x86

//Vcpkg target triplet (ex. x86-windows)
VCPKG_TARGET_TRIPLET:STRING=x86-windows

//Trace calls to find_package()
VCPKG_TRACE_FIND_PACKAGE:BOOL=OFF

//Enables messages from the VCPKG toolchain for debugging purposes.
VCPKG_VERBOSE:BOOL=OFF

//(experimental) Automatically copy dependencies into the install
// target directory for executables. Requires CMake 3.14.
X_VCPKG_APPLOCAL_DEPS_INSTALL:BOOL=OFF

//(experimental) Add USES_TERMINAL to VCPKG_APPLOCAL_DEPS to force
// serialization.
X_VCPKG_APPLOCAL_DEPS_SERIALIZED:BOOL=OFF

//The directory which contains the installed libraries for each
// triplet
_VCPKG_INSTALLED_DIR:PATH=E:/test/vcpkg/installed

//No help, variable specified on the command line.
_VCPKG_ROOT_DIR:UNINITIALIZED=E:/test/vcpkg

//Value Computed by CMake
freeglut_BINARY_DIR:STATIC=E:/test/vcpkg/buildtrees/freeglut/x86-windows-rel

//Value Computed by CMake
freeglut_IS_TOP_LEVEL:STATIC=ON

//Value Computed by CMake
freeglut_SOURCE_DIR:STATIC=E:/test/vcpkg/buildtrees/freeglut/src/v3.4.0-fe4645a74b.clean

########################
# INTERNAL cache entries
########################

//ADVANCED property for variable: CMAKE_AR
CMAKE_AR-ADVANCED:INTERNAL=1
//This is the directory where this CMakeCache.txt was created
CMAKE_CACHEFILE_DIR:INTERNAL=e:/test/vcpkg/buildtrees/freeglut/x86-windows-rel
//Major version of cmake used to create the current loaded cache
CMAKE_CACHE_MAJOR_VERSION:INTERNAL=3
//Minor version of cmake used to create the current loaded cache
CMAKE_CACHE_MINOR_VERSION:INTERNAL=27
//Patch version of cmake used to create the current loaded cache
CMAKE_CACHE_PATCH_VERSION:INTERNAL=1
//Path to CMake executable.
CMAKE_COMMAND:INTERNAL=E:/Program Files/CMake/bin/cmake.exe
//Path to cpack program executable.
CMAKE_CPACK_COMMAND:INTERNAL=E:/Program Files/CMake/bin/cpack.exe
//Path to ctest program executable.
CMAKE_CTEST_COMMAND:INTERNAL=E:/Program Files/CMake/bin/ctest.exe
//ADVANCED property for variable: CMAKE_C_COMPILER
CMAKE_C_COMPILER-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_FLAGS
CMAKE_C_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_FLAGS_DEBUG
CMAKE_C_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_FLAGS_MINSIZEREL
CMAKE_C_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_FLAGS_RELEASE
CMAKE_C_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_FLAGS_RELWITHDEBINFO
CMAKE_C_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_STANDARD_LIBRARIES
CMAKE_C_STANDARD_LIBRARIES-ADVANCED:INTERNAL=1
//Path to cache edit program executable.
CMAKE_EDIT_COMMAND:INTERNAL=E:/Program Files/CMake/bin/cmake-gui.exe
//Executable file format
CMAKE_EXECUTABLE_FORMAT:INTERNAL=Unknown
//ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS
CMAKE_EXE_LINKER_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_DEBUG
CMAKE_EXE_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_MINSIZEREL
CMAKE_EXE_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_RELEASE
CMAKE_EXE_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_RELWITHDEBINFO
CMAKE_EXE_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_EXPORT_COMPILE_COMMANDS
CMAKE_EXPORT_COMPILE_COMMANDS-ADVANCED:INTERNAL=1
//Name of external makefile project generator.
CMAKE_EXTRA_GENERATOR:INTERNAL=
//Name of generator.
CMAKE_GENERATOR:INTERNAL=Ninja
//Generator instance identifier.
CMAKE_GENERATOR_INSTANCE:INTERNAL=
//Name of generator platform.
CMAKE_GENERATOR_PLATFORM:INTERNAL=
//Name of generator toolset.
CMAKE_GENERATOR_TOOLSET:INTERNAL=
//Source directory with the top level CMakeLists.txt file for this
// project
CMAKE_HOME_DIRECTORY:INTERNAL=E:/test/vcpkg/buildtrees/freeglut/src/v3.4.0-fe4645a74b.clean
//ADVANCED property for variable: CMAKE_LINKER
CMAKE_LINKER-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS
CMAKE_MODULE_LINKER_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_DEBUG
CMAKE_MODULE_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_MINSIZEREL
CMAKE_MODULE_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_RELEASE
CMAKE_MODULE_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_RELWITHDEBINFO
CMAKE_MODULE_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_MT
CMAKE_MT-ADVANCED:INTERNAL=1
//number of local generators
CMAKE_NUMBER_OF_MAKEFILES:INTERNAL=1
//Platform information initialized
CMAKE_PLATFORM_INFO_INITIALIZED:INTERNAL=1
//noop for ranlib
CMAKE_RANLIB:INTERNAL=:
//ADVANCED property for variable: CMAKE_RC_COMPILER
CMAKE_RC_COMPILER-ADVANCED:INTERNAL=1
CMAKE_RC_COMPILER_WORKS:INTERNAL=1
//ADVANCED property for variable: CMAKE_RC_FLAGS
CMAKE_RC_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_RC_FLAGS_DEBUG
CMAKE_RC_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_RC_FLAGS_MINSIZEREL
CMAKE_RC_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_RC_FLAGS_RELEASE
CMAKE_RC_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_RC_FLAGS_RELWITHDEBINFO
CMAKE_RC_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//Path to CMake installation.
CMAKE_ROOT:INTERNAL=E:/Program Files/CMake/share/cmake-3.27
//ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS
CMAKE_SHARED_LINKER_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_DEBUG
CMAKE_SHARED_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_MINSIZEREL
CMAKE_SHARED_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_RELEASE
CMAKE_SHARED_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_RELWITHDEBINFO
CMAKE_SHARED_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_SKIP_INSTALL_RPATH
CMAKE_SKIP_INSTALL_RPATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_SKIP_RPATH
CMAKE_SKIP_RPATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS
CMAKE_STATIC_LINKER_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_DEBUG
CMAKE_STATIC_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_MINSIZEREL
CMAKE_STATIC_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_RELEASE
CMAKE_STATIC_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_RELWITHDEBINFO
CMAKE_STATIC_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_TOOLCHAIN_FILE
CMAKE_TOOLCHAIN_FILE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_VERBOSE_MAKEFILE
CMAKE_VERBOSE_MAKEFILE-ADVANCED:INTERNAL=1
//Install the dependencies listed in your manifest:
//\n    If this is off, you will have to manually install your dependencies.
//\n    See https://github.com/microsoft/vcpkg/tree/master/docs/specifications/manifests.md
// for more info.
//\n
VCPKG_MANIFEST_INSTALL:INTERNAL=OFF
//ADVANCED property for variable: VCPKG_VERBOSE
VCPKG_VERBOSE-ADVANCED:INTERNAL=1
//Making sure VCPKG_MANIFEST_MODE doesn't change
Z_VCPKG_CHECK_MANIFEST_MODE:INTERNAL=OFF
//Vcpkg root directory
Z_VCPKG_ROOT_DIR:INTERNAL=E:/test/vcpkg

E:\test\vcpkg\buildtrees\freeglut\config-x86-windows-out.log
[1/2] "E:/Program Files/CMake/bin/cmake.exe" -E chdir "../../x86-windows-dbg" "E:/Program Files/CMake/bin/cmake.exe" "E:/test/vcpkg/buildtrees/freeglut/src/v3.4.0-fe4645a74b.clean" "-G" "Ninja" "-DCMAKE_BUILD_TYPE=Debug" "-DCMAKE_INSTALL_PREFIX=E:/test/vcpkg/packages/freeglut_x86-windows/debug" "-DFETCHCONTENT_FULLY_DISCONNECTED=ON" "-DFREEGLUT_BUILD_STATIC_LIBS=0" "-DFREEGLUT_BUILD_SHARED_LIBS=1" "-DFREEGLUT_REPLACE_GLUT=ON" "-DFREEGLUT_BUILD_DEMOS=OFF" "-DINSTALL_PDB=OFF" "-DCMAKE_MAKE_PROGRAM=E:/test/vcpkg/downloads/tools/ninja/1.10.2-windows/ninja.exe" "-DBUILD_SHARED_LIBS=ON" "-DVCPKG_CHAINLOAD_TOOLCHAIN_FILE=E:/test/vcpkg/scripts/toolchains/windows.cmake" "-DVCPKG_TARGET_TRIPLET=x86-windows" "-DVCPKG_SET_CHARSET_FLAG=ON" "-DVCPKG_PLATFORM_TOOLSET=v140" "-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON" "-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON" "-DCMAKE_FIND_PACKAGE_NO_SYSTEM_PACKAGE_REGISTRY=ON" "-DCMAKE_INSTALL_SYSTEM_RUNTIME_LIBS_SKIP=TRUE" "-DCMAKE_VERBOSE_MAKEFILE=ON" "-DVCPKG_APPLOCAL_DEPS=OFF" "-DCMAKE_TOOLCHAIN_FILE=E:/test/vcpkg/scripts/buildsystems/vcpkg.cmake" "-DCMAKE_ERROR_ON_ABSOLUTE_INSTALL_DESTINATION=ON" "-DVCPKG_CXX_FLAGS=" "-DVCPKG_CXX_FLAGS_RELEASE=" "-DVCPKG_CXX_FLAGS_DEBUG=" "-DVCPKG_C_FLAGS=" "-DVCPKG_C_FLAGS_RELEASE=" "-DVCPKG_C_FLAGS_DEBUG=" "-DVCPKG_CRT_LINKAGE=dynamic" "-DVCPKG_LINKER_FLAGS=" "-DVCPKG_LINKER_FLAGS_RELEASE=" "-DVCPKG_LINKER_FLAGS_DEBUG=" "-DVCPKG_TARGET_ARCHITECTURE=x86" "-DCMAKE_INSTALL_LIBDIR:STRING=lib" "-DCMAKE_INSTALL_BINDIR:STRING=bin" "-D_VCPKG_ROOT_DIR=E:/test/vcpkg" "-D_VCPKG_INSTALLED_DIR=E:/test/vcpkg/installed" "-DVCPKG_MANIFEST_INSTALL=OFF"
FAILED: ../../x86-windows-dbg/CMakeCache.txt
"E:/Program Files/CMake/bin/cmake.exe" -E chdir "../../x86-windows-dbg" "E:/Program Files/CMake/bin/cmake.exe" "E:/test/vcpkg/buildtrees/freeglut/src/v3.4.0-fe4645a74b.clean" "-G" "Ninja" "-DCMAKE_BUILD_TYPE=Debug" "-DCMAKE_INSTALL_PREFIX=E:/test/vcpkg/packages/freeglut_x86-windows/debug" "-DFETCHCONTENT_FULLY_DISCONNECTED=ON" "-DFREEGLUT_BUILD_STATIC_LIBS=0" "-DFREEGLUT_BUILD_SHARED_LIBS=1" "-DFREEGLUT_REPLACE_GLUT=ON" "-DFREEGLUT_BUILD_DEMOS=OFF" "-DINSTALL_PDB=OFF" "-DCMAKE_MAKE_PROGRAM=E:/test/vcpkg/downloads/tools/ninja/1.10.2-windows/ninja.exe" "-DBUILD_SHARED_LIBS=ON" "-DVCPKG_CHAINLOAD_TOOLCHAIN_FILE=E:/test/vcpkg/scripts/toolchains/windows.cmake" "-DVCPKG_TARGET_TRIPLET=x86-windows" "-DVCPKG_SET_CHARSET_FLAG=ON" "-DVCPKG_PLATFORM_TOOLSET=v140" "-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON" "-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON" "-DCMAKE_FIND_PACKAGE_NO_SYSTEM_PACKAGE_REGISTRY=ON" "-DCMAKE_INSTALL_SYSTEM_RUNTIME_LIBS_SKIP=TRUE" "-DCMAKE_VERBOSE_MAKEFILE=ON" "-DVCPKG_APPLOCAL_DEPS=OFF" "-DCMAKE_TOOLCHAIN_FILE=E:/test/vcpkg/scripts/buildsystems/vcpkg.cmake" "-DCMAKE_ERROR_ON_ABSOLUTE_INSTALL_DESTINATION=ON" "-DVCPKG_CXX_FLAGS=" "-DVCPKG_CXX_FLAGS_RELEASE=" "-DVCPKG_CXX_FLAGS_DEBUG=" "-DVCPKG_C_FLAGS=" "-DVCPKG_C_FLAGS_RELEASE=" "-DVCPKG_C_FLAGS_DEBUG=" "-DVCPKG_CRT_LINKAGE=dynamic" "-DVCPKG_LINKER_FLAGS=" "-DVCPKG_LINKER_FLAGS_RELEASE=" "-DVCPKG_LINKER_FLAGS_DEBUG=" "-DVCPKG_TARGET_ARCHITECTURE=x86" "-DCMAKE_INSTALL_LIBDIR:STRING=lib" "-DCMAKE_INSTALL_BINDIR:STRING=bin" "-D_VCPKG_ROOT_DIR=E:/test/vcpkg" "-D_VCPKG_INSTALLED_DIR=E:/test/vcpkg/installed" "-DVCPKG_MANIFEST_INSTALL=OFF"
CMake Deprecation Warning at CMakeLists.txt:1 (CMAKE_MINIMUM_REQUIRED):
  Compatibility with CMake < 3.5 will be removed from a future version of
  CMake.

  Update the VERSION argument <min> value or use a ...<max> suffix to tell
  CMake that the project does not need compatibility with older versions.

-- The C compiler identification is MSVC 19.0.23026.0
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - failed
-- Check for working C compiler: E:/Program Files (x86)/Microsoft Visual Studio 14.0/VC/bin/amd64_x86/cl.exe
-- Check for working C compiler: E:/Program Files (x86)/Microsoft Visual Studio 14.0/VC/bin/amd64_x86/cl.exe - broken
CMake Error at E:/Program Files/CMake/share/cmake-3.27/Modules/CMakeTestCCompiler.cmake:67 (message):
  The C compiler

    "E:/Program Files (x86)/Microsoft Visual Studio 14.0/VC/bin/amd64_x86/cl.exe"

  is not able to compile a simple test program.

  It fails with the following output:

    Change Dir: 'E:/test/vcpkg/buildtrees/freeglut/x86-windows-dbg/CMakeFiles/CMakeScratch/TryCompile-yf475v'

    Run Build Command(s): E:/test/vcpkg/downloads/tools/ninja/1.10.2-windows/ninja.exe -v cmTC_ee0eb
    [1/2] E:\PROGRA~2\MICROS~1.0\VC\bin\AMD64_~2\cl.exe  /nologo   /nologo /DWIN32 /D_WINDOWS /W3 /utf-8 /MP   /MDd /Zi /Ob0 /Od /RTC1 /showIncludes /FoCMakeFiles\cmTC_ee0eb.dir\testCCompiler.c.obj /FdCMakeFiles\cmTC_ee0eb.dir\ /FS -c E:\test\vcpkg\buildtrees\freeglut\x86-windows-dbg\CMakeFiles\CMakeScratch\TryCompile-yf475v\testCCompiler.c
    cl : Command line warning D9002 : ignoring unknown option '/utf-8'
    [2/2] cmd.exe /C "cd . && "E:\Program Files\CMake\bin\cmake.exe" -E vs_link_exe --intdir=CMakeFiles\cmTC_ee0eb.dir --rc=rc --mt=CMAKE_MT-NOTFOUND --manifests  -- E:\PROGRA~2\MICROS~1.0\VC\bin\AMD64_~2\link.exe /nologo CMakeFiles\cmTC_ee0eb.dir\testCCompiler.c.obj  /out:cmTC_ee0eb.exe /implib:cmTC_ee0eb.lib /pdb:cmTC_ee0eb.pdb /version:0.0 /machine:X86  /debug /INCREMENTAL /subsystem:console  kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib && cd ."
    FAILED: cmTC_ee0eb.exe
    cmd.exe /C "cd . && "E:\Program Files\CMake\bin\cmake.exe" -E vs_link_exe --intdir=CMakeFiles\cmTC_ee0eb.dir --rc=rc --mt=CMAKE_MT-NOTFOUND --manifests  -- E:\PROGRA~2\MICROS~1.0\VC\bin\AMD64_~2\link.exe /nologo CMakeFiles\cmTC_ee0eb.dir\testCCompiler.c.obj  /out:cmTC_ee0eb.exe /implib:cmTC_ee0eb.lib /pdb:cmTC_ee0eb.pdb /version:0.0 /machine:X86  /debug /INCREMENTAL /subsystem:console  kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib && cd ."
    RC Pass 1: command "rc /fo CMakeFiles\cmTC_ee0eb.dir/manifest.res CMakeFiles\cmTC_ee0eb.dir/manifest.rc" failed (exit code 0) with the following output:
    系统找不到指定的文件。
    ninja: build stopped: subcommand failed.

  CMake will not be able to correctly generate this project.
Call Stack (most recent call first):
  CMakeLists.txt:2 (PROJECT)

-- Configuring incomplete, errors occurred!
[2/2] "E:/Program Files/CMake/bin/cmake.exe" -E chdir ".."  "E:/Program Files/CMake/bin/cmake.exe" "E:/test/vcpkg/buildtrees/freeglut/src/v3.4.0-fe4645a74b.clean" "-G" "Ninja" "-DCMAKE_BUILD_TYPE=Release" "-DCMAKE_INSTALL_PREFIX=E:/test/vcpkg/packages/freeglut_x86-windows" "-DFETCHCONTENT_FULLY_DISCONNECTED=ON" "-DFREEGLUT_BUILD_STATIC_LIBS=0" "-DFREEGLUT_BUILD_SHARED_LIBS=1" "-DFREEGLUT_REPLACE_GLUT=ON" "-DFREEGLUT_BUILD_DEMOS=OFF" "-DINSTALL_PDB=OFF" "-DCMAKE_MAKE_PROGRAM=E:/test/vcpkg/downloads/tools/ninja/1.10.2-windows/ninja.exe" "-DBUILD_SHARED_LIBS=ON" "-DVCPKG_CHAINLOAD_TOOLCHAIN_FILE=E:/test/vcpkg/scripts/toolchains/windows.cmake" "-DVCPKG_TARGET_TRIPLET=x86-windows" "-DVCPKG_SET_CHARSET_FLAG=ON" "-DVCPKG_PLATFORM_TOOLSET=v140" "-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON" "-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON" "-DCMAKE_FIND_PACKAGE_NO_SYSTEM_PACKAGE_REGISTRY=ON" "-DCMAKE_INSTALL_SYSTEM_RUNTIME_LIBS_SKIP=TRUE" "-DCMAKE_VERBOSE_MAKEFILE=ON" "-DVCPKG_APPLOCAL_DEPS=OFF" "-DCMAKE_TOOLCHAIN_FILE=E:/test/vcpkg/scripts/buildsystems/vcpkg.cmake" "-DCMAKE_ERROR_ON_ABSOLUTE_INSTALL_DESTINATION=ON" "-DVCPKG_CXX_FLAGS=" "-DVCPKG_CXX_FLAGS_RELEASE=" "-DVCPKG_CXX_FLAGS_DEBUG=" "-DVCPKG_C_FLAGS=" "-DVCPKG_C_FLAGS_RELEASE=" "-DVCPKG_C_FLAGS_DEBUG=" "-DVCPKG_CRT_LINKAGE=dynamic" "-DVCPKG_LINKER_FLAGS=" "-DVCPKG_LINKER_FLAGS_RELEASE=" "-DVCPKG_LINKER_FLAGS_DEBUG=" "-DVCPKG_TARGET_ARCHITECTURE=x86" "-DCMAKE_INSTALL_LIBDIR:STRING=lib" "-DCMAKE_INSTALL_BINDIR:STRING=bin" "-D_VCPKG_ROOT_DIR=E:/test/vcpkg" "-D_VCPKG_INSTALLED_DIR=E:/test/vcpkg/installed" "-DVCPKG_MANIFEST_INSTALL=OFF"
CMake Deprecation Warning at CMakeLists.txt:1 (CMAKE_MINIMUM_REQUIRED):
  Compatibility with CMake < 3.5 will be removed from a future version of
  CMake.

  Update the VERSION argument <min> value or use a ...<max> suffix to tell
  CMake that the project does not need compatibility with older versions.

-- The C compiler identification is MSVC 19.0.23026.0
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - failed
-- Check for working C compiler: E:/Program Files (x86)/Microsoft Visual Studio 14.0/VC/bin/amd64_x86/cl.exe
-- Check for working C compiler: E:/Program Files (x86)/Microsoft Visual Studio 14.0/VC/bin/amd64_x86/cl.exe - broken
CMake Error at E:/Program Files/CMake/share/cmake-3.27/Modules/CMakeTestCCompiler.cmake:67 (message):
  The C compiler

    "E:/Program Files (x86)/Microsoft Visual Studio 14.0/VC/bin/amd64_x86/cl.exe"

  is not able to compile a simple test program.

  It fails with the following output:

    Change Dir: 'E:/test/vcpkg/buildtrees/freeglut/x86-windows-rel/CMakeFiles/CMakeScratch/TryCompile-kfrrs9'

    Run Build Command(s): E:/test/vcpkg/downloads/tools/ninja/1.10.2-windows/ninja.exe -v cmTC_6c8b0
    [1/2] E:\PROGRA~2\MICROS~1.0\VC\bin\AMD64_~2\cl.exe  /nologo   /nologo /DWIN32 /D_WINDOWS /W3 /utf-8 /MP   /MDd /Zi /Ob0 /Od /RTC1 /showIncludes /FoCMakeFiles\cmTC_6c8b0.dir\testCCompiler.c.obj /FdCMakeFiles\cmTC_6c8b0.dir\ /FS -c E:\test\vcpkg\buildtrees\freeglut\x86-windows-rel\CMakeFiles\CMakeScratch\TryCompile-kfrrs9\testCCompiler.c
    cl : Command line warning D9002 : ignoring unknown option '/utf-8'
    [2/2] cmd.exe /C "cd . && "E:\Program Files\CMake\bin\cmake.exe" -E vs_link_exe --intdir=CMakeFiles\cmTC_6c8b0.dir --rc=rc --mt=CMAKE_MT-NOTFOUND --manifests  -- E:\PROGRA~2\MICROS~1.0\VC\bin\AMD64_~2\link.exe /nologo CMakeFiles\cmTC_6c8b0.dir\testCCompiler.c.obj  /out:cmTC_6c8b0.exe /implib:cmTC_6c8b0.lib /pdb:cmTC_6c8b0.pdb /version:0.0 /machine:X86  /debug /INCREMENTAL /subsystem:console  kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib && cd ."
    FAILED: cmTC_6c8b0.exe
    cmd.exe /C "cd . && "E:\Program Files\CMake\bin\cmake.exe" -E vs_link_exe --intdir=CMakeFiles\cmTC_6c8b0.dir --rc=rc --mt=CMAKE_MT-NOTFOUND --manifests  -- E:\PROGRA~2\MICROS~1.0\VC\bin\AMD64_~2\link.exe /nologo CMakeFiles\cmTC_6c8b0.dir\testCCompiler.c.obj  /out:cmTC_6c8b0.exe /implib:cmTC_6c8b0.lib /pdb:cmTC_6c8b0.pdb /version:0.0 /machine:X86  /debug /INCREMENTAL /subsystem:console  kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib && cd ."
    RC Pass 1: command "rc /fo CMakeFiles\cmTC_6c8b0.dir/manifest.res CMakeFiles\cmTC_6c8b0.dir/manifest.rc" failed (exit code 0) with the following output:
    系统找不到指定的文件。
    ninja: build stopped: subcommand failed.

  CMake will not be able to correctly generate this project.
Call Stack (most recent call first):
  CMakeLists.txt:2 (PROJECT)

-- Configuring incomplete, errors occurred!
ninja: build stopped: subcommand failed.

Additional context

都已经按要求安装；且Windows 10 SDK已重新安装，还是报这个问题

@xiaochong0406, Do you have the English language pack installed? Restart VS after installation and try again.

Ping @xiaochong0406 for response.

We hope your question was answered to your satisfaction; if it wasn't, you can reopen with more info.


Change target directory in soroban-examples

There has been a recent changes in soroban-examples where target directory is now part of each example's directory instead of being at the top level directory. Our docs need to be updated to refer to target/wasm32-unknown-unknown/... instead of  ../target/wasm32-unknown-unknown/.. in the examples.
Convo ref

Errors occur with current dev-dependencies in cargo.toml files
[dev_dependencies]
soroban-sdk = { version = "0.7.0", git = "https://github.com/stellar/rs-soroban-sdk", rev = "9bbac60c25cee9aa995025db5af828c243d15690", features = ["testutils"] }

https://github.com/stellar/soroban-examples/issues/237

Update: Waiting for 0.8.0 release to implement change

PR: https://github.com/stellar/soroban-docs/pull/405

Merge


Can't override AZURE_ResourceTypes

I can't override the value of the AZURE_ResourceTypes, I do it via environment settings.
I always got all resources.
Name: AZURE_ResourceTypes
Value: {"Patient", "Observation", "Encounter"}

I have run the app, but I also wasn't able to override with the system env the value of the model
 [JsonProperty("resourceTypes")]
        public List<string> ResourceTypes { get; set; } = new List<string>{
                "Account",
                "ActivityDefinition",
                "AdverseEvent",
                "AllergyIntolerance",
                "Appointment",
                "AppointmentResponse",
                "AuditEvent",
                "Basic",
                "Binary",
                "BiologicallyDerivedProduct",
                "BodyStructure",
                "Bundle",
                "CapabilityStatement",
                "CarePlan",
                "CareTeam",
                "CatalogEntry",
                "ChargeItem",
                "ChargeItemDefinition",
                "Claim",
                "ClaimResponse",
                "ClinicalImpression",
                "CodeSystem",
                "Communication",
                "CommunicationRequest",
                "CompartmentDefinition",
                "Composition",
                "ConceptMap",
                "Condition",
                "Consent",
                "Contract",
                "Coverage",
                "CoverageEligibilityRequest",
                "CoverageEligibilityResponse",
                "DetectedIssue",
                "Device",
                "DeviceDefinition",
                "DeviceMetric",
                "DeviceRequest",
                "DeviceUseStatement",
                "DiagnosticReport",
                "DocumentManifest",
                "DocumentReference",
                "EffectEvidenceSynthesis",
                "Encounter",
                "Endpoint",
                "EnrollmentRequest",
                "EnrollmentResponse",
                "EpisodeOfCare",
                "EventDefinition",
                "Evidence",
                "EvidenceVariable",
                "ExampleScenario",
                "ExplanationOfBenefit",
                "FamilyMemberHistory",
                "Flag",
                "Goal",
                "GraphDefinition",
                "Group",
                "GuidanceResponse",
                "HealthcareService",
                "ImagingStudy",
                "Immunization",
                "ImmunizationEvaluation",
                "ImmunizationRecommendation",
                "ImplementationGuide",
                "InsurancePlan",
                "Invoice",
                "Library",
                "Linkage",
                "List",
                "Location",
                "Measure",
                "MeasureReport",
                "Media",
                "Medication",
                "MedicationAdministration",
                "MedicationDispense",
                "MedicationKnowledge",
                "MedicationRequest",
                "MedicationStatement",
                "MedicinalProduct",
                "MedicinalProductAuthorization",
                "MedicinalProductContraindication",
                "MedicinalProductIndication",
                "MedicinalProductIngredient",
                "MedicinalProductInteraction",
                "MedicinalProductManufactured",
                "MedicinalProductPackaged",
                "MedicinalProductPharmaceutical",
                "MedicinalProductUndesirableEffect",
                "MessageDefinition",
                "MessageHeader",
                "MolecularSequence",
                "NamingSystem",
                "NutritionOrder",
                "Observation",
                "ObservationDefinition",
                "OperationDefinition",
                "OperationOutcome",
                "Organization",
                "OrganizationAffiliation",
                "Parameters",
                "Patient",
                "PaymentNotice",
                "PaymentReconciliation",
                "Person",
                "PlanDefinition",
                "Practitioner",
                "PractitionerRole",
                "Procedure",
                "Provenance",
                "Questionnaire",
                "QuestionnaireResponse",
                "RelatedPerson",
                "RequestGroup",
                "ResearchDefinition",
                "ResearchElementDefinition",
                "ResearchStudy",
                "ResearchSubject",
                "RiskAssessment",
                "RiskEvidenceSynthesis",
                "Schedule",
                "ServiceRequest",
                "Slot",
                "Specimen",
                "SpecimenDefinition",
                "StructureDefinition",
                "StructureMap",
                "Subscription",
                "Substance",
                "SubstancePolymer",
                "SubstanceProtein",
                "SubstanceReferenceInformation",
                "SubstanceSpecification",
                "SubstanceSourceMaterial",
                "SupplyDelivery",
                "SupplyRequest",
                "Task",
                "TerminologyCapabilities",
                "TestReport",
                "TestScript",
                "ValueSet",
                "VerificationResult",
                "VisionPrescription"
            };

I tried to set in
AZURE_ResourceTypes={"Device"}
AZURE_ResourceTypes=["Device"]
AZURE_ResourceTypes='Device'

No luck

Hi @oyemeLife , thanks for submitting this issue. We will investigate and get back to you!

Hi @oyemeLife , thanks for submitting this issue. We will investigate and get back to you!

To address this, I forked the repository to implement changes and override the migrationOptions binding model with an empty list. Since it is not possible to override a list of strings directly, the workaround involves overriding an existing index. For instance, setting AZURE_ResourceTypes__0 = Device will assign "Device" to the first index. This method supports multiple resources by adding settings via AZURE_ResourceTypes__[index].

Hi @oyemeLife , do you mind sharing more on your use case? Is there a reason that you are only migrating certain resource types? Also, are you able to share which company you are representing?

Hi @oyemeLife , do you mind sharing more on your use case? Is there a reason that you are only migrating certain resource types? Also, are you able to share which company you are representing?

We are currently using two stores. Some resources point to the new FHIR API, while others point to the old one. Our original plan was to migrate resources one by one. I can share the company name privately.

Hi @oyemeLife, thanks for the info. To clarify - by two stores, is that the older Azure API for FHIR and the new Azure Health Data Services FHIR? And for the migration, is your source FHIR server the Azure API for FHIR, and your destination FHIR server the Azure Health Data Services FHIR? Just want to make sure we understand your FHIR setup correctly.
Also, if you could send me the company name to<EMAIL_ADDRESS>that would be helpful for our customer tracking, thank you!

Yes, that's correct. Migrating from Azure API for FHIR to Azure Health Data Services FHIR.

The same issue persists when setting the Azure_SurfaceCheckResources environment variable while testing the end-to-end function. Luckily, the SurfaceCheckResources array only uses the patient index for the first element in the migration options,
   public List<string>? SurfaceCheckResources { get; set; } = new List<string> { "Patient" };
so I can set Azure_SurfaceCheckResources__{INDEX}
This is what I did.

Hi @oyemeLife , thanks for the info. Can you share your rationale on why you are planning to migrate resource types one by one?
We do not recommend migrating resource types one by one, because many of these resources are interlinked. It may be the case that you migrate data into AHDS FHIR that is supposed to be linked to another resource, but that resource type does not exist in the FHIR server yet. We recommend migrating all the of the resource types, which is why we have provided the superset of resource types.
If you are hoping to either test the migration tool or migrate smaller chunks of data, I would suggest that you explore using smaller chunks (https://github.com/Azure/apiforfhir-migration-tool/tree/main/FHIR-data-migration-tool-docs#export-in-the-migration-tool) by configuring AZURE_ExportChunkDuration, or, you can adjust the AZURE_StartDate to set the first date and continue to start-stop the migration tool as you test the migration tool. This way, resources are still migrated in chronological order, with all the resource types, and the links between the various resources can be maintained.
Looking forward to hear more about your use case. Thanks!

The original plan was to migrate resources one by one. Some of the resources point to new ADHD, some of the resources point to both ADHD and Azure API, and some point to old Azure API.  d
For example
AuditEvent:
✗ The totals are different:
OLD: 40840455
NEW: 7689342
Device:
OLD: 456
NEW: 0
Practitioner:
OLD: 844
NEW: 0
Consent:
OLD: 948851
NEW: 186580
I believe then, it should be removed from the readme and env settings to have the ability of overriding the resource types as it's currently not recommended and not supported

Hi @oyemeLife  - I see, yes, we would still recommend migrating all resource types (if you'd like smaller chunks, you can change the dates in the migration tool), and then using the new AHDS FHIR server as your single source of truth. If you migrate resource types one at a time, there is a possibility that the references between resources may get broken.
We will go ahead and update the documentation. Our original intention was to provide all the R4 resource types, and customers could update that list if they, for example, knew that their FHIR server only had a certain subset of these resource types. However, the idea was to still migrate all the resource types that are in a given FHIR server. We will update the documentation to make this more clear!
Other than that, were there any other issues with your migration?

Closing this issue as we have updated the documentation to remove the wording about customizing the resource types. Please feel free to reopen or create a new issue if there are any other issues with the migration!


Support autorepeats and getting keymap entries

Signed-off-by: Sean Young<EMAIL_ADDRESS>

I've added some other changes too. Ready for review, thanks!

ping @coolreader18 @jeff-hiner
Thanks

Sorry, was apparently not getting notifications. I'll take a look shortly.

@jeff-hiner thanks for the review - it's ready for the 2nd review


Host services stored in Consul not accessible from containers

We have Consul configured to use a advertise_addr of <IP_ADDRESS>. This means that if we had simple Consul service definitions for applications on the host (postgres, redis, etc), DNS lookups to those services will return <IP_ADDRESS>. This is ok on the host as <IP_ADDRESS> is the correct address for locally running services, but from a container, <IP_ADDRESS> is the local interface of the container, not the host. On production servers we set the advertise_addr to the address of eth0 or eth1, so containers can access services on hosts via those addresses.
("Host" above refers to the Vagrant machine, i.e. the guest VM).
We could possibly set the advertise_addr to the eth0 interface IP. I'm not entirely sure what the effects of this are, though.

One way to fix this is to set the advertise_addr to the eth0 interface (should be <IP_ADDRESS> but I'm not sure how consistent it is). The client_addr can be set to <IP_ADDRESS> so that consular can speak to consul on <IP_ADDRESS>, while the website can still be accessed at <IP_ADDRESS>.

@smn: ready for review.
With a NAT-ed VirtualBox guest, the eth0 interface should always have an address of <IP_ADDRESS>. Source: https://blogs.oracle.com/fatbloke/entry/networking_in_virtualbox1

:+1:

Do we want to document those magic IPs somewhere? We used another one earlier as well for setting up dnsmasq.

Yeah perhaps a VirtualBox cheat sheet. Or a note about stuff in the configuration of this VM that is specific to VirtualBox.


home page - lost tile

The tile Set Second password gets lost when we:

Set a username

Lock our account

Fixed by PR: #38


Add study discovery validation

The web page only shows users, studies that have not expired. Added functionality for enrollment so that users can only enroll in studies that they are eligible for.

I'll just merge this and remove those prints on a separate commit so I can get started on more changes without worrying about conflicts.