Allow menus to be dynamically positioned.

Please review @roryabraham
Details

Added a new prop onDimensionsChange to WithWindowDimensions which allows attaching change Listener.
Debounced the Dimensions change event on WithWindowDimensions by 200ms.
Using the above, set the recalculation of the Call menu and Emoji Picker.

Fixed Issues

Fixes #2517
Tests / QA Steps

Open Expensify.cash on Web or Desktop
Log into your account
Click into a chat with another user
Click the telephone_receiver phone icon in the top-right, and see the Call Option menu
Click on any edge of the window and change the size of the window. See that the Call Options menu dynamically moving with the size of the window.
Click the Emoji picker icon on the report composer.
Click on any edge of the window and change the size of the window. See that the Emoji picker menu dynamically moving with the size of the window.

Tested On

[x] Web
[ ] Mobile Web
[x] Desktop
[ ] iOS
[ ] Android

Screenshots

Web / Desktop

https://user-images.githubusercontent.com/24370807/117215199-872aa100-ae1b-11eb-8af1-54581936bc30.mp4

Hmmm @parasharrajat I thought we discussed in the linked issue that we were going to move the dimensions informations and listeners into Onyx, and deprecate the withWindowDimensions HOC?

Sure. Will do.

@roryabraham I have a suggestion. Can we use the React Context for WindowDimensions? https://reactjs.org/docs/context.html.
I still have doubts. I just want to achieve the best possible thing here. I understand Onyx is the way to go currently in the app.

What will happen when storage is full and Dimensions are only a runtime thing and having a read-write headache from Onyx ix worth investing in just because of simplicity.

So my take on this is that we definitely don't want to use React Context. It's a pattern we haven't used anywhere else the codebase and not one that I think we want to encourage. I'm sure I have some biases, but I think they're just sort of complex and not that commonly used 🤷🏼♂

What will happen when storage is full and Dimensions are only a runtime thing and Is having a read-write headache from Onyx worth investing in just because of simplicity?

To quote @tgolen, "this is just a rumor of a problem for now" 😄 Expensify.cash is built on Onyx, so I think the way that we should approach this is not to avoid using it because we think it might have some potential pitfalls. Instead we should use it, and then when there are problems, adjust it and make it work for our needs. It would be easy to adjust Onyx down the line to have some values only be stored in-memory 🙂

Thanks, @roryabraham. Let me do it that way.

@roryabraham Updated.
Do I need to refactor all the withWindowDimensions instances with withOnyx HOC, then How should I manage the direct props.
 windowHeight: window.height,
 windowWidth: window.width,
 isSmallScreenWidth,

instead of currently what I have done
dimensions: {
 	windowHeight: window.height,
 	windowWidth: window.width,
 	isSmallScreenWidth,
 }

🚀 Deployed to production in version: 1.0.44-0🚀

platform
result

🤖 android 🤖
failure ❌

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Fix doc build

Not sure it's worth mass-renaming inside the docs before we decide what in the docs should be dropped.

I think we should try not to duplicate fMRIPrep's documentation, so probably best is starting from scratch.

I think we should try not to duplicate fMRIPrep's documentation, so probably best is starting from scratch.


OSSM-8004: Use our proxy

/test integ-security

/test integ-security

/test integ-security

@dgn Yeah, I thought about it as well, my conclusion was to keep the old jiras in the comments so we remember why those tests are skipped every time we cherry-pick this change. If we create new ones, they will be closed in some triaging meeting, I guess :) What do you think?

@dgn Yeah, I thought about it as well, my conclusion was to keep the old jiras in the comments so we remember why those tests are skipped every time we cherry-pick this change. If we create new ones, they will be closed in some triaging meeting, I guess :) What do you think?

Maybe you're right. Alright, let's merge as-is then!


gpu

excuse me,
Does the author run the code on a single GPU？ and it takes how many days？

excuse me,
Does the author run the code on a single GPU？ and it takes how many days？

The model cannot be trained only on a single GPU (you can use one GPU to debug or perform inference).

Thank you for your response.


Invalid specs because of missing type + nullable: true

In some cases, when there's a request that returns an empty attribute, the following is generated:
                    myattribute:
                            nullable: true

Without any type (because it can't be inferred). This is not valid. While not perfect, would it be possible to generate something like this, if there is no type that can be used?
                  myattribute:
                    nullable: true
                    oneOf:
                      - type: string
                      - type: number
                      - type: boolean
                      - type: object
                      - type: array

This is at least a valid definition.

Could you elaborate the issue more specifically?
Like, A OpenAPI tool FOO does not work on this generated code.
Because, as far as I and my colleagues use this tool in my projects, it just works on many OpenAPI tools such as Swagger/OpenAPI editor, code generator and so on.


Set each default pull policy at begining

[merge]

AFAIR there are 2 ways of invoking S2I -- one from the binary and another one as part of OpenShift. Looks like after this change there is no defaulting logic when S2I is invoking from the OpenShift. I hope that we didn't break something that was working before.

AFAIR there are 2 ways of invoking S2I -- one from the binary and another one as part of OpenShift. Looks like after this change there is no defaulting logic when S2I is invoking from the OpenShift. I hope that we didn't break something that was working before.

@php-coder i checked for this before merging the PR.  the openshift logic always sets the policy:
https://github.com/openshift/origin/blob/master/pkg/build/builder/sti.go#L214-L223


Dataset creation: Do we expect the .tex files to be just a single file for each corresponding PDF?

Hey,
Thank you for your work, the results are pretty cool!
I am trying to reproduce your work for a personal project, but it seems for dataset generation many times in the src downloaded from Arxiv  there are many .tex files, I can always merge into a single .tex files maybe using a simple script, so my question is do you expect only a single tex file converted to HTML using LATExml for each pdf?
Best,
Saksham

We are using engrafo to convert latex project directories to a single html file

Thanks this was really helpful!


updated codekit (2.9)

[X] The commit message includes the cask’s name and version.
[X] brew cask audit --download {{cask_file}} is error-free.
[X] brew cask style --fix {{cask_file}} left no offenses.

Why close? What’s the issue with it?

Because I deleted the branch because I thought it was merged 😠

Because I deleted the branch because I thought it was merged 😠

Apologies. It happens so many times that I have to review a cask twice (because the first time) Travis hadn’t finished yet, thought of trying to approval system to let myself and other maintainers know it had already been reviewed.

Apologies. It happens so many times that I have to review a cask twice (because the first time Travis hadn’t finished yet), thought of trying the approval system to let myself and other maintainers know it had already been reviewed.

Don't apologize.  It was my own fault for not actually reading the status update that you posted.  You were very clear on it.


GSD Request

--- GSD JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from  to before v5.15.10",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=f6db3d98f876870c35e96693cfd54752f6199e59"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "f6db3d98f876870c35e96693cfd54752f6199e59",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "drm/msm: Fix null ptr access msm_ioctl_gem_submit()\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v5.15.10 by commit f6db3d98f876870c35e96693cfd54752f6199e59. For more details please see the references link."
}
--- GSD JSON ---

This issue has been assigned GSD-2021-1002726


Update sharepoint-design-manager-image-renditions.md

Category

[ ] Content fix
[ ] New article
Related issues: fixes #X, partially #Y, mentioned in #Z

For the above list, an empty checkbox is [ ] as in [SPACE]. A checked checkbox is [x] with no space between the brackets. Use the PREVIEW tab at the top right to preview the rendering before submitting your issue.
(DELETE THIS PARAGRAPH AFTER READING)

What's in this Pull Request?

Please describe the changes in this PR. Sample description or details around bugs which are being fixed.
(DELETE THIS PARAGRAPH AFTER READING)

Guidance

Please update this PR information accordingly. We'll use this as part of our release notes in monthly communications.
Please target your PR to 'master' branch. Released documents are in live branch.
(DELETE THIS PARAGRAPH AFTER READING)

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/general-development/sharepoint-design-manager-image-renditions.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

thx @aneethajayaraman, appreciated.


Calls to Google.Cloud.Storage.V1.UploadObject start failing with message "a task was canceled"

Maybe this is not the right place, but I'm roaming from days and I don't know where else I can ask for help.
I'm using Google Video Intelligence to process videos and Cloud Storage to upload files to be processed. I'm working in .Net, and using Google.Cloud.Storage.V1 (3.7.0) to handle requests to the Storage service. It was working fine until my app was runnig on local machine, now I deployed it on AWS and it started to failing on the Google.Cloud.Storage.V1.UploadObject method.
This is the code part:
public bool UploadBlob(string destFilename, string mimeType, Stream content)
{
   try
   {
      logger.LogInformation($"{DateTime.Now}: bucket name: {BucketName}");
      logger.LogInformation($"{DateTime.Now}: Uploading file in bucket {BucketName}");
      logger.LogInformation($"{DateTime.Now}: file data: {destFilename}, {mimeType}, content.Length}");
      var obj = StorageClient.UploadObject(BucketName, destFilename, mimeType, content);
   }
   catch (TaskCanceledException ex)
   {
     if (ex.CancellationToken.IsCancellationRequested)
     {
        logger.LogError($"{DateTime.Now}:IsCancellationRequested");
     }
     logger.LogError($"{DateTime.Now}:{ex.Message}");
     logger.LogError($"{DateTime.Now}:{ex.InnerException.Message}");
   }
   return true;
}

And this is the resulting logs with exception:
02/18/2022 13:55:59: bucket name: mmmanager2
02/18/2022 13:55:59: Uploading file in bucket mmmanager2
02/18/2022 13:55:59: file data: 3EDXNPHF3D2T058ICVIG.mp4, video, 79826367
02/18/2022 13:57:39:IsCancellationRequested
02/18/2022 13:57:39:A task was canceled.

Unhandled exception. System.NullReferenceException: Object reference not set to an instance of an object.

   at VideoAnnotationService.UploadBlob(String fileName, String destFilename, String mimeType, Stream content)

   at Workers.VideoWorker.<>c__DisplayClass15_0.<<UploadVideo>b__0>d.MoveNext() ...

--- End of stack trace from previous location where exception was thrown ---

   at VideoWorker.ProcessMultimedia() in ...

   at System.Threading.Tasks.Task.<>c.<ThrowAsync>b__139_1(Object state)

   at System.Threading.QueueUserWorkItemCallbackDefaultContext.Execute()

   at System.Threading.ThreadPoolWorkQueue.Dispatch()

I'm using default outbound rules so all the traffic is permitted so I don't think AWS platform could be an issue.
At the moment I don't know what approach to use to debug this.
Any help is welcome.
Thank you.

Hi,
that's all exception message is, hope can help:
02/23/2022 14:22:37:ex: System.Threading.Tasks.TaskCanceledException: A task was canceled.

         at Google.Cloud.Storage.V1.StorageClientImpl.UploadHelper.CheckFinalProgress()

         at Google.Cloud.Storage.V1.StorageClientImpl.UploadHelper.Execute()

         at Google.Cloud.Storage.V1.StorageClientImpl.UploadObject(Object destination, Stream source, UploadObjectOptions options, IProgress`1 progress)

         at Google.Cloud.Storage.V1.StorageClientImpl.UploadObject(String bucket, String objectName, String contentType, Stream source, UploadObjectOptions options, IProgress`1 progress)

         at VideoAnnotationService.UploadBlob(String fileName, String destFilename, String mimeType, Stream content)

Unhandled exception. System.NullReferenceException: Object reference not set to an instance of an object.

   at VideoAnnotationService.UploadBlob(String fileName, String destFilename, String mimeType, Stream content)

   at MultimediaManagerService.Workers.VideoWorker.<>c__DisplayClass15_0.<<UploadVideo>b__0>d.MoveNext() in F:\Progetti\MultimediaManagerService\Workers\VideoWorker.cs:line 376

--- End of stack trace from previous location where exception was thrown ---

   at MultimediaManagerService.Workers.VideoWorker.ProcessMultimedia() in F:\Progetti\MultimediaManagerService\Workers\VideoWorker.cs:line 101

   at System.Threading.Tasks.Task.<>c.<ThrowAsync>b__139_1(Object state)

   at System.Threading.QueueUserWorkItemCallbackDefaultContext.Execute()

   at System.Threading.ThreadPoolWorkQueue.Dispatch()

Thank you for the fast reply.
Fabio

Right. So it sounds like it's timed out during the upload - it looks like a 100 second timeout. I'd certainly expect it to take a lot less time than that to upload 79MB.
Are you able to test whether it works for very small uploads? Also, please could you show how you're constructing the client, including anything you're doing for authentication?
(As an aside, the NullReferenceException is just because you're trying to log ex.InnerException.Message. That's nothing to do with the storage library. If you're logging the whole exception now, you can get rid of all the extra bits of logging.)

I tried with a video of just 869 KB, same results, then right now I noticed that a request to Google.Cloud.Translation.V2 has also the same problem.
It could be a network problem from AWS, but other requests to external services are working.

Again, please show how you're constructing the client and what you're doing for authentication. It's possible that it's actually the authentication request that's timing out.

Both codes added,
I succesfully received the access token substring and the same problem occurs while listing bucket objects.
Here's the exception log:
02/23/2022 18:52:45:ex: System.Threading.Tasks.TaskCanceledException: A task was canceled.

         at Google.Apis.Requests.ClientServiceRequest`1.Execute()

         at Google.Api.Gax.Rest.RestPagedEnumerable`3.AsRawResponses()+MoveNext()

         at System.Linq.Enumerable.SelectManySingleSelectorIterator`2.MoveNext()

         at System.Linq.Enumerable.Count[TSource](IEnumerable`1 source)

         at VideoAnnotationService.UploadBlob(String fileName, String destFilename, String mimeType, Stream content)

Okay, that's interesting. Assuming there aren't thousands of objects in your bucket (we can always try a different operation, of course), that suggests there's a problem accessing https://storage.googleapis.com
I've finished work for the day now, but I'll have a look tomorrow at putting together some sample code to make a similar request directly with HttpClient.

Ok,
actually the bucket is empty,
Thank you for your support!

Right - if the bucket is empty, then it should still be entirely valid, and return quickly.
Before I get to it tomorrow, please could you let me know any interesting details of how you're deploying it on AWS? I don't know much about AWS but in GCP at least there are lots of different ways of deploying (VM, Cloud Run, GKE, Cloud Functions etc). I would imagine it's the same for AWS.

It is a .Net core service in a Docker Container running on an Ubuntu VM.

Okay, here's some more code to test. Note that in the previous auth token test, we didn't have any scopes, so I believe it would actually have been creating a self-signed JWT - which means you may well find that fetching the auth token does fail here.
This code assumes you have somewhere you can execute an async method.
using Google.Apis.Auth.OAuth2;
using Google.Apis.Storage.v1;
using System.Net.Http.Headers;

...

string bucketName = "...";

ITokenAccess cred = GoogleCredential.GetApplicationDefault()
    .CreateScoped(StorageService.Scope.CloudPlatform);

var token = await cred.GetAccessTokenForRequestAsync("https://storage.googleapis.com");
var httpClient = new HttpClient();
string uri = $"https://storage.googleapis.com/storage/v1/b/{bucketName}/o";
var request = new HttpRequestMessage
{
    RequestUri = new Uri(uri),
    Method = HttpMethod.Get,
    Headers =
    {
        Authorization = new AuthenticationHeaderValue("Bearer", token)
    }
};

var response = await httpClient.SendAsync(request);
logger.LogInformation("Status: {status}", response.StatusCode);
string text = await response.Content.ReadAsStringAsync();
logger.LogInformation("Response content: {content}", text);

Here's the resulting exception:
Unhandled exception. System.InvalidOperationException: The access token has expired and could not be refreshed. Errors: timeout, timeout, timeout

   at Google.Apis.Auth.OAuth2.TokenRefreshManager.RefreshTokenAsync()

   at Google.Apis.Auth.OAuth2.TokenRefreshManager.GetAccessTokenForRequestAsync(CancellationToken cancellationToken)

   at Google.Apis.Auth.OAuth2.ServiceAccountCredential.GetAccessTokenForRequestAsync(String authUri, CancellationToken cancellationToken)

   at VideoAnnotationService.UploadBlobAsync(String fileName, String destFilename, String mimeType, Stream content)

   at MultimediaManagerService.Workers.VideoWorker.<>c__DisplayClass15_0.<<UploadVideo>b__0>d.MoveNext() in F:\MultimediaManagerService\Exprivia.ILab.Findustry.MultimediaManagerService\Workers\VideoWorker.cs:line 376

Okay, so it looks like the problem is with auth after all.
Here's another bit of code to just check HttpClient interaction with the Google OAuth servers:
var httpClient = new HttpClient();
var request = new HttpRequestMessage
{
    RequestUri = new Uri("https://accounts.google.com/o/oauth2/token"),
    Method = HttpMethod.Post,
    Content = new FormUrlEncodedContent(new[] { KeyValuePair.Create("key", "value")})
};
var response = await httpClient.SendAsync(request);
logger.LogInformation("Status: {status}", response.StatusCode);
string text = await response.Content.ReadAsStringAsync();
logger.LogInformation("Response content: {content}", text);

Obviously that's not actually going to get an access token - but hopefully it will at least show the response. (I'd expect a response of "BadRequest" with JSON showing an error of "unsupported_grant_type".)

Another URL to try with the above code is https://oauth2.googleapis.com/token - apologies, I had misread our own code.
Additionally, please could you tell us what kind of credential you've got in your JSON file? I expect it's probably a service account credential, but it's worth checking.

Exeption with both Urls
 02/24/2022 11:04:10:ex: System.Threading.Tasks.TaskCanceledException: The operation was canceled.

         at System.Net.Http.ConnectHelper.ConnectAsync(String host, Int32 port, CancellationToken cancellationToken)

         at System.Net.Http.HttpConnectionPool.ConnectAsync(HttpRequestMessage request, Boolean allowHttp2, CancellationToken cancellationToken)

         at System.Net.Http.HttpConnectionPool.CreateHttp11ConnectionAsync(HttpRequestMessage request, CancellationToken cancellationToken)

         at System.Net.Http.HttpConnectionPool.GetHttpConnectionAsync(HttpRequestMessage request, CancellationToken cancellationToken)

         at System.Net.Http.HttpConnectionPool.SendWithRetryAsync(HttpRequestMessage request, Boolean doRequestAuth, CancellationToken cancellationToken)

         at System.Net.Http.HttpConnectionPool.EstablishProxyTunnel(HttpRequestHeaders headers, CancellationToken cancellationToken)

         at System.Net.Http.HttpConnectionPool.ConnectAsync(HttpRequestMessage request, Boolean allowHttp2, CancellationToken cancellationToken)

         at System.Net.Http.HttpConnectionPool.CreateHttp11ConnectionAsync(HttpRequestMessage request, CancellationToken cancellationToken)

         at System.Net.Http.HttpConnectionPool.GetHttpConnectionAsync(HttpRequestMessage request, CancellationToken cancellationToken)

         at System.Net.Http.HttpConnectionPool.SendWithRetryAsync(HttpRequestMessage request, Boolean doRequestAuth, CancellationToken cancellationToken)

         at System.Net.Http.RedirectHandler.SendAsync(HttpRequestMessage request, CancellationToken cancellationToken)

         at System.Net.Http.HttpClient.FinishSendAsyncBuffered(Task`1 sendTask, HttpRequestMessage request, CancellationTokenSource cts, Boolean disposeCts)

         at VideoAnnotationService.UploadBlobAsync(String fileName, String destFilename, String mimeType, Stream content)

Yes it is a service account.

Okay, so at this point the problem clearly isn't in the client libraries - you need to review your network configuration, firewalls etc. You originally wrote:

I'm using default outbound rules so all the traffic is permitted so I don't think AWS platform could be an issue.

... but it really sounds like that is the problem. You might want to try connecting to some other URLs (e.g https://www.google.com, https://microsoft.com, https://wikipedia.org) to see if there's any pattern in what you can and can't reach.

Yes the problem occurs also for https://www.google.com/ and https://microsoft.com/, but it works with an external service making NLP.....quite strange!
I tried also with http instead of https, same results.
Fabio

Okay - I'm afraid at this point I don't think I have any other information to offer, as the problem definitely isn't in the client libraries. Hopefully you'll be able to find AWS experts who can help with the networking side. I'll close the issue now, but best of luck resolving it. (And if you can resolve the networking and you still have problems with the libraries, do either add another comment here or create a new issue, of course.)

ok,
Thank you for your support!
Fabio


Find when a configuration is resolved

Expected Behavior
I see deprecation messages like the following in my build scan:
Mutating the dependencies of configuration '<project>' after it has been resolved or consumed. This behavior has been deprecated.
    This will fail with an error in Gradle 9.0.
    After a Configuration has been resolved, consumed as a variant, or used for generating published metadata, it should not be modified.

This comes with a corresponding stack trace. However, I would also like to see where in my build the configuration has been resolved so that I can decide which location needs to be changed. Is this possible?
Current Behavior (optional)
No response
Context
I am attempting to prepare some builds for Gradle 9.

This issue needs a decision from the team responsible for that area. They have been informed. Response time may vary.

Currently, there's no easy way to discover where the failure comes from because it's technically hard to interpret the information. However, we might consider adding some pointers to the upgrade guide and linking to them from the message.
For now, you can add some throws/debug logic in configuration.incoming.beforeResolve

There are still a couple of things I'm struggling with. Please let me know if this isn't the right place to discuss this anymore, and I can move to forums, Slack, or somewhere else.
Specifically, the error message is:
Mutating the dependencies of configuration '<project>:api' after it has been resolved or consumed. This behavior has been deprecated.

I believe it is because in our plugins we add dependencies to the api and implementation configurations in an afterEvaluate block.
I have tried to throw in configurations.api.incoming.beforeResolve, but it does not fire. I have tried to put it in various places (near the beginning of the project's build.gradle file, at the top of the root project's build.gradle file in a subprojects block). I suppose that this makes sense, since api is neither consumable or resolvable.
When I throw an exception in beforeResolve targeting compileClasspath, it only throws during compileJava. So my best guess is that maybe apiElements or some other related configuration is consumed early, but I don't know how to validate that assumption.
Any additional suggestions would be greatly appreciated.

It would be nice to get some better insight into this.
There are multiple ways a configuration can be observed.  beforeResolve isn't going to help in cases where the configuration is used from another configuration (e.g., someConf.extendsFrom(api))
We'll see if there are any quick wins for 8.13

I wrote https://github.com/gradle/gradle/pull/31658 to try to capture a bit more context whenever we observe a configuration. This will report whether the configuration being mutated was previously:

Resolved
Consumed as a variant
Published
Observed due to a child configuration doing one of the above

It is difficult to capture the original place of observation, as that would require capturing a stack trace for each time a configuration is observed.
To debug things like this I would recommend debugging Gradle. See the "Debugging build logic" section.
You can put a breakpoint here and filter your breakpoint to only trigger when the configuration-being-mutated is the one being observed.


WIP: upload to S3

I just fixed the return code when uploading (https://github.com/mamba-org/powerloader/commit/63e2f68fefcbd85c3971d5affdbdb9af03d32844) :)


[AutoPR resources/resource-manager] Microsoft.Authorization/policy* entities 2019-09-01

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/7380

(message created by the CI based on PR content)


Make ipywidgets show up

I.e. press the 'save with widgets' button.

From https://github.com/pyviz/nbsite/pull/52#issuecomment-391880204:

nbsite doesn't currently support ipywidgets (i.e. they won't appear, as you are finding with nbconvert). We do have a library that uses ipywidgets, but have so far only ever cheated to get widgets to appear in docs (e.g. follow the doc/index.ipynb link from https://github.com/ioam/paramnb).

Should be possible to support ipywidgets; see https://ipywidgets.readthedocs.io/en/latest/embedding.html

Here's an example of where they should be showing up but aren't: https://examples.pyviz.org/voila_gpx_viewer/voila_gpx_viewer.html

Here's an example of where they should be showing up but aren't: https://examples.pyviz.org/voila_gpx_viewer/voila_gpx_viewer.html

Are you sure that notebook is even being run?

Nevermind it definitely is, I see the widget model in the output.


Build fails with '_Decimal128' does not name a type

Testing on Ubuntu 14.04.3 LTS, HHVM 3.13.1 and the master of libbson
root@e347410b8ada:/tmp/mongofill-hhvm# ./build.sh

git submodule update --init
hhvm tools/merge.php
hphpize
** hphpize complete, now run `cmake . && make` to build, `make test` to test
cmake .
-- The C compiler identification is GNU 4.8.4
-- The CXX compiler identification is GNU 4.8.4
-- The ASM compiler identification is GNU
-- Found assembler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Configuring for HHVM API version 20150212
-- bson Include dir: /usr/local/include/libbson-1.0
-- libbson library: /usr/local/lib/libbson-1.0.so
-- Configuring done
-- Generating done
-- Build files have been written to: /tmp/mongofill-hhvm
make
Scanning dependencies of target mongo
[ 33%] Building CXX object CMakeFiles/mongo.dir/src/bson.cpp.o
In file included from /usr/local/include/libbson-1.0/bson.h:33:0,
                 from /tmp/mongofill-hhvm/src/bson.cpp:3:
/usr/local/include/libbson-1.0/bson-decimal128.h:61:8: error: '_Decimal128' does not name a type
 static _Decimal128 BSON_INLINE
        ^
/usr/local/include/libbson-1.0/bson-decimal128.h:71:32: error: variable or field 'bson_Decimal128_to_decimal128' declared void
 bson_Decimal128_to_decimal128 (_Decimal128        decimal128,
                                ^
/usr/local/include/libbson-1.0/bson-decimal128.h:71:32: error: '_Decimal128' was not declared in this scope
/usr/local/include/libbson-1.0/bson-decimal128.h:72:50: error: expected primary-expression before '*' token
                                bson_decimal128_t *dec)
                                                  ^
/usr/local/include/libbson-1.0/bson-decimal128.h:72:51: error: 'dec' was not declared in this scope
                                bson_decimal128_t *dec)
                                                   ^
/usr/local/include/libbson-1.0/bson-decimal128.h:72:51: note: suggested alternative:
In file included from /usr/include/c++/4.8/ios:42:0,
                 from /usr/include/c++/4.8/istream:38,
                 from /usr/include/c++/4.8/sstream:38,
                 from /usr/include/c++/4.8/complex:45,
                 from /usr/include/boost/type_traits/is_complex.hpp:12,
                 from /usr/include/boost/type_traits.hpp:49,
                 from /usr/include/hphp/third-party/folly/Portability.h:300,
                 from /usr/include/hphp/third-party/folly/FBString.h:53,
                 from /usr/include/hphp/third-party/folly/Conv.h:27,
                 from /usr/include/hphp/third-party/folly/Format.h:24,
                 from /usr/include/hphp/util/assertions.h:28,
                 from /usr/include/hphp/runtime/base/countable.h:23,
                 from /usr/include/hphp/runtime/base/req-ptr.h:20,
                 from /usr/include/hphp/runtime/base/type-string.h:20,
                 from /usr/include/hphp/runtime/base/debuggable.h:19,
                 from /usr/include/hphp/runtime/ext/extension.h:21,
                 from /tmp/mongofill-hhvm/src/bson.cpp:1:
/usr/include/c++/4.8/bits/ios_base.h:939:3: note:   'std::dec'
   dec(ios_base& __base)
   ^
make[2]: *** [CMakeFiles/mongo.dir/src/bson.cpp.o] Error 1
make[1]: *** [CMakeFiles/mongo.dir/all] Error 2
make: *** [all] Error 2

I've it building including the typedefs for _Decimal128. You can check it here:https://github.com/mongofill/mongofill-hhvm/commit/ca7d944aa2bd03dcc13090745c650c86e6125840
Should this be a temporary fix or something required as it's from libbson and not the extension code itself?


visual issues with connect automatically

The "connect automatically" has a different font than the rest of the labels in the dialog.
there is a large vertical space under the "connect automatically" button and the rest of the dialog (disks)

also it would be nice to have a question mark next to the "connect automatically" explaining what does it actually do since it is a very unintuitive feature.

Fixed by https://github.com/oVirt/ovirt-web-ui/issues/31


UnboundLocalError when system cmake is installed using pip

I got the following error
 Traceback (most recent call last):
    File "/tmp/pip-build-env-nizg97b2/overlay/lib/python3.12/site-packages/scikit_build_core/program_search.py", line 81, in get_cmake_program
      result = Run().capture(cmake_path, "-E", "capabilities")
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    File "/tmp/pip-build-env-nizg97b2/overlay/lib/python3.12/site-packages/scikit_build_core/_shutil.py", line 43, in capture
      return self._run(args, capture=True)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    File "/tmp/pip-build-env-nizg97b2/overlay/lib/python3.12/site-packages/scikit_build_core/_shutil.py", line 71, in _run
      return subprocess.run(
             ^^^^^^^^^^^^^^^
    File "/home/njzjz/anaconda3/lib/python3.12/subprocess.py", line 571, in run
      raise CalledProcessError(retcode, process.args,
  subprocess.CalledProcessError: Command '['/home/njzjz/anaconda3/bin/cmake', '-E', 'capabilities']' returned non-zero exit status 1.

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
    File "/tmp/pip-build-env-nizg97b2/overlay/lib/python3.12/site-packages/scikit_build_core/program_search.py", line 90, in get_cmake_program
      result = Run().capture(cmake_path, "--version")
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    File "/tmp/pip-build-env-nizg97b2/overlay/lib/python3.12/site-packages/scikit_build_core/_shutil.py", line 43, in capture
      return self._run(args, capture=True)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    File "/tmp/pip-build-env-nizg97b2/overlay/lib/python3.12/site-packages/scikit_build_core/_shutil.py", line 71, in _run
      return subprocess.run(
             ^^^^^^^^^^^^^^^
    File "/home/njzjz/anaconda3/lib/python3.12/subprocess.py", line 571, in run
      raise CalledProcessError(retcode, process.args,
  subprocess.CalledProcessError: Command '['/home/njzjz/anaconda3/bin/cmake', '--version']' returned non-zero exit status 1.

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
    File "/home/njzjz/anaconda3/lib/python3.12/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 353, in <module>
      main()
    File "/home/njzjz/anaconda3/lib/python3.12/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 335, in main
      json_out['return_val'] = hook(**hook_input['kwargs'])
                               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    File "/home/njzjz/anaconda3/lib/python3.12/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 118, in get_requires_for_build_wheel
      return hook(config_settings)
             ^^^^^^^^^^^^^^^^^^^^^
    File "/tmp/pip-build-env-nizg97b2/overlay/lib/python3.12/site-packages/scikit_build_core/build/__init__.py", line 126, in get_requires_for_build_wheel
      [*requires.cmake(), *requires.ninja()] if requires.settings.wheel.cmake else []
      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    File "/tmp/pip-build-env-nizg97b2/overlay/lib/python3.12/site-packages/scikit_build_core/builder/get_requires.py", line 78, in cmake
      cmake = best_program(get_cmake_programs(module=False), version=cmake_verset)
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    File "/tmp/pip-build-env-nizg97b2/overlay/lib/python3.12/site-packages/scikit_build_core/program_search.py", line 169, in best_program
      for program in programs:
    File "/tmp/pip-build-env-nizg97b2/overlay/lib/python3.12/site-packages/scikit_build_core/program_search.py", line 125, in get_cmake_programs
      yield get_cmake_program(cmake_path)
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    File "/tmp/pip-build-env-nizg97b2/overlay/lib/python3.12/site-packages/scikit_build_core/program_search.py", line 105, in get_cmake_program
      result.stdout,
      ^^^^^^
  UnboundLocalError: cannot access local variable 'result' where it is not associated with a value

The error handling here has a problem. So I hack subprocess.py to print the stdout/stderr:
   Traceback (most recent call last):
    File "/home/njzjz/anaconda3/bin/cmake", line 5, in <module>
      from cmake import cmake
  ModuleNotFoundError: No module named 'cmake'

   Traceback (most recent call last):
    File "/home/njzjz/anaconda3/bin/cmake", line 5, in <module>
      from cmake import cmake
  ModuleNotFoundError: No module named 'cmake'

This seems to be expected, as scikit-build-core runs in an isolated environment.
The error handing problem should be related to #717.

After checking #717, I think this will work:
-        except subprocess.CalledProcessError:
+        except subprocess.CalledProcessError as result:
             logger.warning(
                 "Could not determine CMake version via --version, got {!r} {!r}",
                 result.stdout,
                 result.stderr,
             )

A script called CMake that imports CMake from CMake sounds suspect (what is anaconda doing?), but you are correct, static checks didn’t catch the unbound variable bug.

A script called CMake that imports CMake from CMake sounds suspect (what is anaconda doing?)

To be clear, I installed cmake using pip install cmake. cmake.cmake is defined here as a script.
The content of bin/cmake:
#!/home/njzjz/anaconda3/bin/python3.12
# -*- coding: utf-8 -*-
import re
import sys
from cmake import cmake
if __name__ == '__main__':
    sys.argv[0] = re.sub(r'(-script\.pyw|\.exe)?$', '', sys.argv[0])
    sys.exit(cmake())

Yes, that makes sense - if cmake is installed in an "outer" environment (such as no environment), then it might get picked up on the path but not have a valid Python install. If cmake became a real "script", that would fix this, though I'm not sure where I'd need to put the helper module files if we do that (something I do want to explore).
Hopefully this is fixed in #719. It's a tricky[^1] thing to test for.
[^1]: as in it would take more time than I have currently for quick fixes to set one up.

Was able to test locally. Fixed in 0.9.2.


[BUG] Potential Breaking Change / Bug between cds-typer 0.15 and 0.16

Is there an existing issue for this?

[X] I have searched the existing issues

Nature of Your Project
TypeScript
Current Behavior
It seems as if there's a breaking bug between 0.15 and 0.16. Types that are not arrays are typed as arrays after updating-
Given a definitions such as:
 function someFunction(someId : String) returns SomeType;

    type SomeType {
        someOtherTypes   : SomeOtherTypes;
    }

       type SomeOtherTypes {
        someArrayOfStrings : array of String;
    }

In 0.16 it results in:
export function _SomeTypeAspect<TBase extends new (...args: any[]) => object>(Base: TBase) {
    return class SomeType extends Base {
          someOtherTypes?: SomeOtherTypes | null;
        static actions: {
      }
    };
  }
  export class SomeType extends _SomeTypeAspect(__.Entity) {}
  export class SomeType_ extends Array<SomeType> {}
  Object.defineProperty(SomeType, 'name', { value: 'SomeService.SomeType' })
  Object.defineProperty(SomeType_, 'name', { value: 'SomeService.SomeType' })

export function _SomeOtherTypeAspect<TBase extends new (...args: any[]) => object>(Base: TBase) {
  return class SomeOtherType extends Base {
    someArrayOfStrings?: Array<string>;
      static actions: {
    }
  };
}
export class SomeOtherType extends _SomeOtherTypeAspect(__.Entity) {}
export class SomeOtherTypes extends Array<SomeOtherType> {}
Object.defineProperty(SomeOtherType, 'name', { value: 'SomeService.SomeOtherTypes' })
Object.defineProperty(SomeOtherTypes, 'name', { value: 'SomeService.SomeOtherTypes' })

And the someOtherTypes property in SomeType seems to be typed as an array.
In 0.15 it results in:
export type SomeType = {
    someOtherTypes?: SomeOtherTypes | null;
};

export type SomeOtherTypes = {
    someArrayOfStrings?: Array<string>;
};

And seems to be correctly typed.
Expected Behavior
I'd expect types not defined as arrays not being identified as arrays.
Steps To Reproduce
No response
Environment
- **OS**: MacOs
- **Node**: v20.11.0
- **npm**: 10.4.0
- **cds-typer**: 0.16.0
- **cds**: 7.6.2

Repository Containing a Minimal Reproducible Example
No response
Anything else?
No response

Hi Tobias,
thanks for bringing up this issue.
This is a bit of an odd one, as it should have been present even in earlier versions. The problem here is that the whole singular/plural spiel is only applied to entities. So when you are dealing with types, you should only ever encounter the flexion as it was defined by the user.
I'll take this to our internal discussion see if we want to put flexion on type definitions or if we have to find another way to address this.
Best,
Daniel


Creation of material.md - team The Leftovers 2.0

Hi @open-sci/the-leftovers-2-0,
As anticipated in the lecture on the 28th of April (practical part), in the space dedicated to your group in the repository of the course, you have to create a material.md file where you list all the members of the group with all the roles they have had in the project (using the CRediT taxonomy as specified in the title page of your slides).
In addition, in the material.md file, you also need to add a bibliographic reference in APA style for each of the items to submit. You can follow the template below to create the document (the words between angular brackets must be substituted with the correct value):
# Material - team <<name of the team>>

## Members
[<<Member 1 full name>>](<<GitHub account URL>>), roles:
* <<role 1>>, <<description 1>>
* <<role 2>>, <<description 2>>
* ...

[<<Member 2 full name>>](<<GitHub account URL>>), roles:
* <<role 1>>, <<description 1>>
* <<role 2>>, <<description 2>>
* ...

[<<Member 3 full name>>](<<GitHub account URL>>), roles:
* <<role 1>>, <<description 1>>
* <<role 2>>, <<description 2>>
* ...

[<<Member 4 full name>>](<<GitHub account URL>>), roles:
* <<role 1>>, <<description 1>>
* <<role 2>>, <<description 2>>
* ...

## Material

### Data Management Plan
<<Bibliographic reference in APA style of the last version>>

Reviews of the [<<initial version of the DMP>>](<<DOI URL of the initial version of the DMP>>):
* <<Bibliographic reference in APA style of the first review>>
* <<Bibliographic reference in APA style of the second review>>

Authors' response to the reviews:
* <<Bibliographic reference in APA style of the authors' response to the reviews>>

### Protocol introducing the methodology
<<Bibliographic reference in APA style of the last version>>

Reviews of the [<<initial version of the protocol>>](<<DOI URL of the initial version of the protocol>>):
* <<Bibliographic reference in APA style of the first review>>
* <<Bibliographic reference in APA style of the second review>>

Authors' response to the reviews:
* <<Bibliographic reference in APA style of the authors' response to the reviews>>

### Software developed
<<Bibliographic reference in APA style of the last version>>

### The data gathered while running the methodology
<<Bibliographic reference in APA style of the last version>>

### Article presenting the research
<<Bibliographic reference in APA style of the last version>>

### Slides supporting the presentation
<<Bibliographic reference in APA style of the last version>>

Please remember that the last point (i.e. "Slides supporting the presentation") can be added after the workshop on the 5th of May.
For further doubts, do not hesitate to contact me in the Signal group.

The material.md file for the Leftovers team has been created in 2020-2021-the-leftovers-20-code repository: https://github.com/open-sci/2020-2021-the-leftovers-20-code/blob/main/material.md

The material.md file for the Leftovers team has been created in 2020-2021-the-leftovers-20-code repository: https://github.com/open-sci/2020-2021-the-leftovers-20-code/blob/main/material.md

It should be put in the main course repo. Can you move it there, please?

Yes, now we have added the file to the course repo.


Pretrained model?

Hi, would it be possible to provide a link to a pre-trained model?  Thanks!

If I revisit this project, I might.


Time.now -> Time.now.utc (Travis and Server already use utc)

test "successfully shows token with expired refresh token"
didn't handle timezones properly on local machines (fine on travis and server, which both use UTC).
Replacing Time.now with Time.now.utc fixes this.  The string formatting is different between Time.now and Time.now.utc, so I didn't replace instances where Time.now is still used with string formatting.
Pull requests into Bonnie require the following. Submitter and reviewer should :white_check_mark: when done. For items that are not-applicable, note it's not-applicable ("N/A") and :white_check_mark:.
Submitter:

[x] This pull request describes why these changes were made.
[x] This PR is into the correct branch.
[x] JIRA ticket for this PR: https://jira.mitre.org/browse/BONNIE-1937
[x] JIRA ticket links to this PR
[x] Code diff has been done and been reviewed (it does not contain: additional white space, not applicable code changes, debug statements, etc.)
[x] If UI changes have been made, google WAVE plug-in has been executed to ensure no 508 issues were introduced. N/A
[x] Tests are included and test edge cases (tests updated)
[x] Tests have been run locally and pass (remember to update Gemfile when applicable)
[x] Test fixtures updated and documented as necessary ( see internal wiki ) N/A
[x] Code coverage has not gone down and all code touched or added is covered.

In rare situations, this may not be possible or applicable to a PR. In those situations:

Note why this could not be done or is not applicable here:
Add TODOs in the code noting that it requires a test
Add a JIRA task to add the test and link it here:

[x] [BLOCKED/N/A] Automated regression test(s) pass Unable to run because measure view is currently in a broken state.  I believe these changes are N/A to the regression anyway.

Reviewer 1:
Name: @hossenlopp

[x] Code is maintainable and reusable, reuses existing code and infrastructure where appropriate, and accomplishes the task’s purpose
[x] The tests appropriately test the new code, including edge cases
[x] You have tried to break the code

Reviewer 2:
Name:

[ ] Code is maintainable and reusable, reuses existing code and infrastructure where appropriate, and accomplishes the task’s purpose
[ ] The tests appropriately test the new code, including edge cases
[ ] You have tried to break the code

It appears bundle-audit is making travis fail. I believe we are addressing those in codecov PRs.


textInput value is not showing from the starting.

Hi,
I am facing a problem with textInput  value. If I select auto-populate value or click the GPS button then the address is showing in the textInput  field but it's not showing from the stating by default. If I scroll then I can see the address from the first position. Is there any solution for it? Please check this screen https://d.pr/v/MsHxxW
Thank you!

I'm facing the same issue in Android side.
Is there any solution or workaround? Thanks, in advance.

I was facing the same issue. I solved it using the selection prop provided by TextInput. But you will need to control it using a state otherwise the user won't be able to move along the TextInput and will be stuck at the start.
const [selection, setSelection] = useState<any>({start: 0, end: 0});
then pass this using textInputProps of GooglePlacesAutocomplete component like this -
 <GooglePlacesAutocomplete       textInputProps={{         selection: Platform.OS === 'android' ? selection : undefined,         onFocus() {           setSelection(undefined);         },         onBlur() {           setSelection({start: 0, end: 0});         },
Hope this helps :)


Support for inserting links

Support to easily insert links to external or internal resources. This would imply a toolbar action which would probably show a dialog to the user allowing him to select a target for the link.
I do not know the type of links JATS has. Aare there also links to external resources or only internal IDREF-based links?

JATS has ext-link for external links and xref for internal (IDREF) links.
Also we want file-picker functionality for graphic and inline-graphic if it is not already there. (This is easy enough and I can do it.)
There are a couple of other elements/attributes that have linking semantics, such as external-resource and external-object, but these are underspecified (IMO) so we may have to leave them alone. But they are worth looking at.
(Docs at http://jats.nlm.nih.gov/extensions/bits/tag-library/1.0/ under @xlink:href show the possible parents of this attribute; it is not a short list.)
BITS now has support for XInclude, which may be a complication for xref in BITS-conformant documents.

 Also we want file-picker functionality for graphic and inline-graphic if it is not already there. (This is easy enough and I can do it.)

This should already be implemented.
So we would probably need two link actions, one for external links and one for internal ones, right?

I now have this in one of my CSS files (which could be migrated upstream if wanted):
ext-link:after {
    content:
        oxy_urlChooser(
        edit, "@xlink:href",
        columns 40);
}

Do we need anything more than this?
Internal linking (via xref/@rid) already appears to work.
Formally, xref/@rid is IDREFS and can target multiple ID values -- but this feature is rarely if ever used TMK. Should we worry about that?

Yes, this is one way of allowing insertion of external links, via a form control.
Another way would be via a toolbar action. The action could avoid using any custom Java operation, it could invoke an existing operation to insert an XML fragment like:
  <ext-link xlink:href="${ask('Paste Link Here:', url, '')}" xmlns:xlink="http://www.w3.org/1999/xlink"/>

That ask editor variable will automatically popup a dialog asking for an URL.
Actually if you edit the XHTML document type association in the Preferences->"Document Type Associations" page, in the Author->Actions tab there is an action called "a.href" which again uses the same editor variable to ask for a link target.

Putting editor variables into those fragments is really nice. I will remember that, even if ext-ref stays as it currently is (with the form control) it may be useful elsewhere.

Closing, since what we have appears to be Good Enough.

On the other hand I did use this method on one or two other Actions ...


support golang 1.18 workspaces

in workspace enabled repo
 $ go generate ./ent                                                                                ☸ rancher-desktop on ☁
go: -mod may only be set to readonly when in workspace mode, but it is set to "mod"
        Remove the -mod flag to use the default readonly value,
        or set GOWORK=off to disable workspace mode.

oh，i have this error too!!!
when i run "go work init"

You can change the line in ent/generate.go and remove or edit the -mod flag. It should work then.
Let me know if you need more help.

We support 1.17 and 1.18. Therefore no generics in Ent and no workspaces (imo).

Thanks this fixed the problem for me.

Closing then. If anyone has trouble with something similar, please open a new issue.


[bug] tauri does not deliver WindowEvent::Focused when unstable feature is enabled

Describe the bug
tauri does not deliver WindowEvent::Focused when unstable feature is enabled.
Reproduction
https://github.com/topecongiro/tauri-bug-focused-event
Expected behavior
The mwe app emits the following output on switching the focus of the window:
event = Ready
event = WindowEvent { label: "main", event: Focused(true) }
event = WindowEvent { label: "main", event: Focused(false) }

Full tauri info output
[✔] Environment
    - OS: Windows 10.0.19045 X64
    ✔ WebView2: 124.0.2478.97
    ✔ MSVC: Visual Studio Build Tools 2022
    ✔ rustc: 1.77.2 (25ef9e3d8 2024-04-09)
    ✔ cargo: 1.77.2 (e52e36006 2024-03-26)
    ✔ rustup: 1.27.0 (bbb9276d2 2024-03-08)
    ✔ Rust toolchain: stable-x86_64-pc-windows-msvc (default)
    - node: 21.7.3
    - yarn: 1.22.19
    - npm: 10.5.0

[-] Packages
    - tauri [RUST]: 2.0.0-beta.19
    - tauri-build [RUST]: 2.0.0-beta.15
    - wry [RUST]: 0.39.5
    - tao [RUST]: 0.28.0
    - tauri-cli [RUST]: 1.5.6
    - @tauri-apps/api [NPM]: 2.0.0-beta.11
    - @tauri-apps/cli [NPM]: 2.0.0-beta.17

[-] App
    - build-type: bundle
    - CSP: unset
    - frontendDist: ../dist
    - devUrl: http://localhost:1420/
    - bundler: Vite

Stack trace
No response
Additional context
No response

What is the status of this issue?


[MOD REPORT] The Outcast Menu (BF4)

Mod Name: The Outcast Menu (ID#116)
Category: Battlefield 4
Mod Type: EBOOT/SPRX
Author: Synful
Version: 1.0

Does not contain SPRX

Does not contain SPRX

@Alesita66
Thanks for reporting this! I will look into it and get it updated soon as.

Fixed.


Use enum VideoQuality/TrackType without exporting PBType.

nice work!
one question: is it necessary to change it to lower case enums? I think we still use some upper case enums in the code base? Question is if it's worth making users change all of these enums.

Makes sense, but changing to uppercase will cause a dart-style prompt requiring lowerCamelCase, unless we change analysis_options.yaml to disable lowerCamelCase mandatory requirements.

Makes sense, but changing to uppercase will cause a dart-style prompt requiring lowerCamelCase, unless we change analysis_options.yaml to disable lowerCamelCase mandatory requirements.

Got it. I think that would be preferable instead of forcing users to update all the enum references. wdyt?


[WIP] Use universal rubygems method for installing gems

What was the end-user problem that led to this PR?
When following the setup documentation for bundler, it suggests to run bin/rake spec:deps to install the development dependencies for bundler.
Doing this with ruby 1.9.3 (and not upgrading rubygems) will cause this to fail.
What was your diagnosis of the problem?
Ruby 1.9.3 ships with a version of rubygems that is less than 2.0, and doesn't include the mechanisms for installing multiple gems (with specific versions) using colon delimited strings (which is the mechanism used to do so in spec:deps).
What is your fix for the problem, implemented in this PR?
By using ruby -S gem install [GEM_NAME] -v [GEM_VERSION] for each gem, it is a universal way of installing targeted versions of gems on various versions of ruby/rubygems that isn't rubygems dependent.
Why did you choose this fix out of the possible options?
This was the easiest implementation to do that maintains the same documentaion and instructions necessary to setup bundler for development.
The cons with this approach is that is causes additional subshell invocations to be launched for each gem, instead of one, which will be slower.  Since this is a finite number of calls we are doing this for (5 currently), I expect that to be negligible compared to the total time necessary load up the rubygems gem command and fetch each gem from rubygems (we can compare the travis builds from master to see this to compare).
An alternative to this approach would be to call out to the Gem::Installer directly from within the rake task, and avoid calling out to the gem command all together.  This has the downside of requiring more code to do it, but should alleviate the any extra time caused by using sh call to install the gems (might try this in a separate commit so it will have another build on travis and we can compare that result to the initial implementation).

This should only be done if the version of RubyGems does not support installing a list of gems.

@colby-swandale While I agree, part of what I said in the PR description was:

we can compare the travis builds from master to see this to compare

If we filter on rubygems versions from the get go, we can't see any affects on travis because part of what the travis version of this does is install rubygems greater than 2.0, and then invokes spec:deps once that is loaded.  It also means that this code would never be exercised on travis, and we would be going on "faith" that it works.
I have edited the PR title to [WIP] (work in progress) to reflect that this is not ready for merging yet until we can get more data, but I think making this a fallback from the get go would de-legitimize it from having any data in the first place that this is a significant performance degradation to the build (which I assume is what your argument for having this as a fall back is in the first place).

Using this build's travis run, and one from master, I have yet to find a case where the rake spec:travis:deps differs by any more than a second to complete, and with it taking around 20s on average to complete across multiple ruby versions, I think that is within an acceptable margin of variance.
Here are some excerpts:

master
#5938

ruby-2.4.1 RGV=master
22.78s
21.99s

ruby-1.9.3 RGV=v2.2.5
23.79s
22.89s

ruby-1.8.7 RGV=v2.2.5
20.54s
20.98s

I mostly just picked a couple of different versions of ruby for this, and I think it just so happens that most of the "faster" ones are the ones from my PRs build.  I think this would vary between each one, so I don't think there is any noticeable performance difference (from the perspective of time for the build to run) to be gained or lost with this change.

Once the deps are installed though, it goes from 1.5s to 9.9s on my machine

Once the deps are installed though, it goes from 1.5s to 9.9s on my machine

@segiddins I assume you are referring to rerunning the spec:deps after the gems have installed correctly, right?  I know that this isn't a case we won't run into on Travis (unless we consider using the Travis cache for the gem dependencies to slightly speed up the build), but is rerunning spec:deps something that is common for you or anyone else?  I personal don't consider myself a huge and frequent contributor to bundler and every time I do come back to add something, I just simply "hope everything works right from last time :crossed_fingers:", so I probably don't have a good perspective on this.
That said, this PR was more focused from the beginning on "new bundler developer approachability", and not on making this a super-ly optimal performant task.  If we instead think that to solve making this more approachable would rather be to do one of the following:

Updating the docs is to add more steps is a better way to approach this problem
Don't mind increasing complexity in this task to solve that problem
We will be switching to not supporting older versions rubygems versions in bundler 2 AND never expecting that someone would ever have to write and test backported change to older versions of bundler
Developers can figure it out themselves (technically a solution, though one I wouldn't recommend)

That is fine.  Again, I personally am not concerned about the performance for a developer setup task, and am more focused on making these setup steps as accessible as possible.  Any performance metrics here are simply to help put into perspective the pros and cons of the selection of solutions that we are considering.

I'm happy just to do "if Gem::VERSION < 2.5" or something

Was packed up for the weekend when I got this, but changes made.

Wonderful, thanks so much!

@bundlerbot r+


Keypress indicator lights appearing in wrong place on right keypad.

Version
alpha5.1
What is the issue?
Includes alpha5.1.A.
When pressing keys on the right keyboard, any keys from columns 5-8 cause the keypress indicator to light white on the top row column 5 instead of the actual key pressed. The same happens for columns 9-12 when the top row column 9 key lights. The erroneous light goes off if either of the top row keys are pressed but it doesn't fix the fault. The MIDI output of the key presses is not affected.

which mode is this in? scales? classic? both? others?

nvm. I have reproduced this issue on my board. guess you don't like the exploder :P
I'll have it worked out for 5.2

marking closed. erroneous code has been identified and changed for 5.2


how to disable the packet loss feedback mechanism

hi all
i want to disable the  packet loss feedback mechanism because i found worst subscriber connection causes the publisher lower his send video bandwidth. in other words, one of subscribers have worst connection causes all subscribers get worst video stream quality from publisher.
i had try three way as follows ,However, it seems not work.
1.add removeREMB function as Sergio say ,and remove other rtcp-fb in sdp.
2. commented wrtc.setFeedbackReports() in the file erizoJSController.js at server.
3.commented  sdp << "a=rtcp-fb:" << payloadType << " " << rtp.feedbackTypes[itFb] << "\n"; in the file Sdpinfo.cpp at server.
Any idea how to disable feedback mechanism?
Many thanks

Take a look at the "Managing Quality Adaptation" of the licode client API


7/8 problem

I can’t recover 7/8 either using the built-in function or using alltheblocks.net/nft-recovery. There is also a problem with adding coins to staking and also a problem with withdrawing coins from staking. OS. Windows 10

Please update your program to the latest version


Allow to export information by alias on by adding by_alias on model config, instead of export func (dict/json...)

Initial Checks

[X] I have searched Google & GitHub for similar requests and couldn't find anything
[X] I have read and followed the docs and still think this feature is missing

Description
from https://pydantic-docs.helpmanual.io/usage/model_config/#alias-generator
from pydantic import BaseModel

def to_camel(string: str) -> str:
    return ''.join(word.capitalize() for word in string.split('_'))

class Voice(BaseModel):
    name: str
    language_code: str

    class Config:
        alias_generator = to_camel

voice = Voice(Name='Filiz', LanguageCode='tr-TR')
print(voice.language_code)
#> tr-TR
print(voice.dict(by_alias=True))
#> {'Name': 'Filiz', 'LanguageCode': 'tr-TR'}

This should also work:
from pydantic import BaseModel

def to_camel(string: str) -> str:
    return ''.join(word.capitalize() for word in string.split('_'))

class Voice(BaseModel):
    name: str
    language_code: str

    class Config:
        alias_generator = to_camel
        by_alias = True # This is the new configuration added

voice = Voice(Name='Filiz', LanguageCode='tr-TR')
print(voice.language_code)
#> tr-TR
print(voice.dict()) # Note that by_alias is NOT passed here
#> {'Name': 'Filiz', 'LanguageCode': 'tr-TR'}

Affected Components

[ ] Compatibility between releases
[ ] Data validation/parsing
[ ] Data serialization - .dict() and .json()
[ ] JSON Schema
[ ] Dataclasses
[X] Model Config
[ ] Field Types - adding or changing a particular data type
[ ] Function validation decorator
[ ] Generic Models
[ ] Other Model behaviour - construct(), pickling, private attributes, ORM mode
[ ] Plugins and integration with other tools - mypy, FastAPI, python-devtools, Hypothesis, VS Code, PyCharm, etc.

@aradyaron thanks for the feature request. This looks like a legitimate feature request. A PR would be welcome.

Closing in favor of https://github.com/pydantic/pydantic/issues/8379. I think a change along these lines should be implemented in V3 👍.


bug: Tutorial Part 2 broken for Python 3.10

The loading part of the tutorial currently uses target-postgres. That defaults to the transferwise variant. And that one (as of now) is broken for Python 3.10, 3.11. The issue has been fixed October, but no new wheel has been built.
I am unsure on how to best fix the tutorial @aaronsteers @tayloramurphy @pnadolny13 @visch, your thoughts?
I'm really tempted to not go out of the meltano context (ever) again for the tutorial. That would mean using our target-postgres as well.

@sbalnojan seems like we have a few options:

indicate at the start of the tutorial that this only works with 3.9 currently.
build a codespace just for the tutorial and have them work through that - still keep it scoped to 3.9
I see in the extractor setting that we already have introduced the --variant flag, so we could just do that for the target as well and use the meltanolabs variant

We'll need to separately figure out acceptance criteria to make the meltanolabs variant the default, but I haven't made it a priority to dig into that yet.

@sbalnojan two things come to mind for this:

Short term we can update the hub definition to use the git url and pin the commit hash of the bug fix that they havent released yet.
Long term option 1 - ideally we'd get meltanolabs variant cleaned up enough to be default for target-postgres
Long term option 2 -  it might be better to switch to a more tutorial-like set of plugins with less dependency friction. I suggested sqlite in this discussion https://github.com/meltano/meltano/discussions/6950. duckdb seems the most relevant lightweight db right now, although I cant speak to the maturity/stability of those plugins (tap/target/dbt duckdb) as of today. It unclear if theyre ready for the lime light or not.

@pnadolny13 thanks for these suggestions!
I played around with @visch with a few options as well. And I'm 100% positive I don't want to leave the meltanolabs comfort ever for the tutorial :-D So I'm not at all comfortable with duckdb for the codespaces demo right now.
I think the ideal structure would be the following:

Super Quick Tutorial = Current Codespaces tutorial (having a few helper functions and stuff to speed up things)
Tutorial (the one we have right now), complemented by a possible codespace (but not necessarily), offering short cuts (not mandatory!) - this would e.g. launch a postgres with a one liner https://github.com/sbalnojan/meltano-tutorial.

So what I'm now doing is to first convert the tutorial over to Meltanolabs based taps and targets. (the accompanying GitHub repository already has a small set of tests)
Thanks to @visch for fixing the target and showing me that this is quite straight forward.

Tutorial converted.


Defi Wonderland Task List

Problem
Get optimistic roots working on staging testnet. Off-chain changes for optimistic roots, needs to reviewed, improved, and finalized.
This is a task for tracking and coordinating with Defi Wonderland, the work that needs to be done on staging.
This will span multiple Connext weekly sprints.
Impact
Quality and performance of the optimistic roots release. This is a prerequisite for running all test scenarios, and going through the contract upgrade checklist.
Proposed Solution
Complete https://www.notion.so/defi-wonderland/Off-Chain-Task-List-f2246a5ec509447a97a0f13900995115
Acceptance Criteria

[ ] Task List is completed

@preethamr this looks like its getting broken out into other issues, do we want to keep this or close it in favor of the constituent tasks?

closing in favor of epic


Plfm 4741

The root cause of the bug was that the sort column was joined using an inner join when it should have been a left outer join.  I rewrote the queries using 'join ... on' syntax and introducing the left outer join so that the original query:
SELECT annoBlob.ANNOTATIONS_BLOB
FROM SUBSTATUS_ANNOTATIONS_OWNER annoOwner
inner join  SUBSTATUS_ANNOTATIONS_BLOB annoBlob
inner join  SUBSTATUS_STRINGANNOTATION srt
WHERE annoOwner.EVALUATION_ID=42
and annoOwner.SUBMISSION_ID = annoBlob.SUBMISSION_ID
and annoOwner.SUBMISSION_ID = srt.SUBMISSION_ID
and srt.ATTRIBUTE = 'string_anno'
ORDER BY srt.VALUE asc ;

becomes:
SELECT annoBlob.ANNOTATIONS_BLOB
FROM SUBSTATUS_ANNOTATIONS_OWNER annoOwner
inner join  SUBSTATUS_ANNOTATIONS_BLOB annoBlob on annoOwner.SUBMISSION_ID = annoBlob.SUBMISSION_ID
left outer join  SUBSTATUS_STRINGANNOTATION srt on annoOwner.SUBMISSION_ID = srt.SUBMISSION_ID and srt.ATTRIBUTE = 'string anno_null'
WHERE annoOwner.EVALUATION_ID=42
and srt.ATTRIBUTE = 'string anno_null'
ORDER BY srt.VALUE asc ;


Update site to v5.2 of the kit

Site updated with files for v5.2
This now makes it work on Codespaces, though i have noticed that it seems to make it run on port 3001 rather than 3000 which may need documenting somewhere (or at least some troubleshooting in case it's something to do with my setup).

I'm not sure it makes sense to copy all these changes from the prototype kit back into the docs site. Whilst the 2 repos started off the same, we’ve been teasing them apart.
The docs site doesn't really need to 'use' the prototype kit itself - it can just be a simple Express site which uses NHS Frontend in a similar way.
It could even be switched to using a static site generator framework instead like Eleventy or Jekyll or Metalsmith or Hugo - which would be cheaper to host. But currently we do have a single example of a dynamic page (the branching example) which prevents it - and @edwardhorsford did suggest that we could add some more dynamic examples (eg validation?) in future.
It might be worth closing this pull request and re-opening smaller ones with any of the useful changes from the NHS prototype kit that we might want to copy across (eg devcontainer.json)?

That's fair - though I'd like that documented somewhere. Interestingly I think the branching examples should go as tehy're tricky to maintain and in the govuk version are so buried that I didn't know they existed (I'd also say inconsistent givne we don't have code examples of the basic tutorial).
Strictly speaking we don't need codespaces for the docs site, it was more that Paul's pull request had gone stale and so out of curiosity I wanted to try codespaces only for everything to just break.


Bump jekyll from 3.8.6 to 4.2.2 and fix rouge console lexer issue

follow-up #14791
Update to Jekyll 4 and fix issue with rouge console lexer introduced in 3.28.0 by https://github.com/rouge-ruby/rouge/pull/1779.
With rouge 3.28.0

With rouge 3.27.0

Also updates to stable Ruby 2.7.6

Also found out that since rouge 3, hcl format is highlighted correctly!
Before:

After:


Update cookie cutter structure and docs

An "OpenCDMS component" repository can contain:

A Python package containing one or more pygeoapi processes with...

Corresponding tests
Corresponding sphinx docs broken into 4 sections (note that docs from multiple repositories will be compiled together into central documentation):

User guide (overview for users)
Administrator guide (setup and configuration information for system installers / administrators)
Developer guide (detailed information how the process runs including the business logic it performs
Common (brief sections that may be contained in multiple guides, e.g. an introduction/overview paragraph that is included in all three guides. In general not much text should be repeated, instead users should be referred to the relevant section of the other guides)

Standard configuration for processes, e.g. shared config table(s) in OpenCDMS Application database
Shared approach to logging and storing logs as appropriate

A Node package containing interface web component(s) for interacting with the Python processes

Corresponding tests
Corresponding sphinx docs (following the same user, admin, developer structure as the Python package)
Standard configuration for web components to be added to the OpenCDMS web application shell
Shared approach to logging of UI warnings and errors?

Potentially the repository should have docs at the root level that draws sections from the python and node packages together if appropriate for the component

When packing for PyPI the Python package may (optionally) contain the UI code so that developers can run the UI locally to interact with a local version of processes. However, when packaging for npm these packages should be stripped of the Python code to reduce the package size.
This issue aims to update the cookiecutter to reflect the structure above - including providing the common structures for documentation and testing.
Notes:
The structure above is intended to be suitable for a wide variety of solutions, e.g.
a) A Python-only package that contains Python wrappers around R functions for generating "products" that return outputs including graphs and data. In this case it is expected that a corresponding node package will not exist in the respository because the products will get their data from a shared "product selector" that is implemented in the main web application for use by many "product" component repositories
b) A Node-only package that implements a generic user interface component (like the "product selector" that is described above)
c) A repository containing Python and Node packages that are maintained together, e.g. a backup component that contains Python processes for performing backups and a UI component that configures the specifics of how backups should run (e.g. which database(s) to backup, whether all tables should be backed up, where backup should be stored etc.)

Cookie cutter assessment
$ cookiecutter gh:opencdms/component-cookiecutter
You've downloaded /home/ubuntu/.cookiecutters/component-cookiecutter before. Is it okay to delete and re-download it? [yes]: y
author [Name of author]: OpenCDMS Project
email [Author email address]<EMAIL_ADDRESS>maintainer [Name of maintainer]: Ian Edwards
maintainer_email [Maintainer email address]<EMAIL_ADDRESS>package_url [Package homepage]: https://github.com/opencdms-components/forms-component
process_id [ID for process, imported as import process_id]: forms
process_name [Name of process class, process_id.process_name]: forms
process_description [Short description of process]: Forms Component
plugin_name [Name of the OpenCDMS Plugin]: forms-component
plugin_description [Short description of the plugin.]: Forms Component
keywords []: opencdms
license [MIT]:

appears to have a Python .gitignore - should extend for JS/node
requirements-dev.txt  - We should standardize on requirements_dev.txt
The README.md in the created component has usage text for using the cookie cutter that is not of value
components/packages.json - if we scaffold a new component in a subdirectory, the packages.json will be in the subdirectory
should we mandate that all components in an OpenCDMS Component plugin use the same packages.json?

removed:
{
  "name": "forms",
  "version": "0.0.1",
  "description": "Forms Component",
  "main": "index.js",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "author": "OpenCDMS Project",
  "license": "Apache-2.0"
}


Table: Bold table header text on sort

Description
Bold table column header text when sorting by column.
We received feedback from users that it is difficult to see what column is used for sorting. Bolding the header text would draw attention and make the sorted column stand out from the rest.
References #2097
Type of change

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

How Has This Been Tested?
Added e2e test to validate
All unit and e2e tests passed when executing npm run test
Exploratory testing also performed in browser using modus-table component
Checklist

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

Validated for sorting and manual sorting, working as expected


add first working example

I just wrote a working foundationdb example. I submit this PR to propose a shape of internal structures and API.

I used futures 0.1 intentionally. futures 0.1 has enough ecosystem to build some working apps, for example database drivers and hyper, while there's not that much libraries for futures 0.2. I believe the client should built on top of futures 0.1 at this time.
FdbFuture is a wrapper for FDBFuture, but with rust Futures crate. There's an heap allocation (Box<Task>) which is hard to avoid because foundationdb is completion-based and rust Futures is poll-based.
FdbFutureResult is a result of a future, which contains a pointer to completed FDBFuture. It can be resolved into actual result like FDBCluster, FDBDatabase, or some others.
~There should be FdbTrxFuture like things to retain reference count to the database handle while running query. In current example, dropping FdbDatabase while querying will clean-up all resources before transaction finishes.~ I added FdbClusterGet/FdbTrxGet to fix resource leak/use after free.

Misc.

It seems that there's no way to mix network thread of foundationdb with other I/O loop.
There are tons of Arcs to manage internal resources. It might hurt performance, but I can't find better solution for now.

I'm going to merge this in. I agree that the FoudationDB API has some disappointing limitations. Their crazy use of statics is definitely not great. Over time, perhaps we can reimplement that C API directly in Rust...


Attempt at webcomponent community proposal to allow state update via "context protocol"

This is a draft PR, an attempt at making a library less state manager for DOM component updates and a lit adapter to update its state based on that protocol. That "Context" protocol is part of W3C’  Web Components Community Group community-protocols (tracker)
See proposal
Intent
This PR is an exploration for what's needed to have Context protocol in lit-html.
What would be great is to have a "no framework" dependency part, and an adapter that leverages it on the framework side, say what would be on lit-html. So, making a Svelte or Vue.js (or Web Component friendly framework) adapter would be just the basica specific to the framework.
Related

See also lit/lit#1955

@googlebot I signed it!

Have you checked out this https://github.com/lit/lit/pull/1955? Seems like some room for shared effort... also, if you're interested in Community Protocols, we're having a session discussing them next week<EMAIL_ADDRESS>the more insight the better!

Have you checked out this #1955? Seems like some room for shared effort (...)

No, I didn't know. I must have missed it.
Thanks for the info, i'll try to participate

Thanks @renoirb, but closing as this went in with https://github.com/lit/lit/pull/1955

Yup. No worries. In fact when I was talking here, the use-case I was working with at the time was exactly in the context of Micro frontends and verticals within a shell, like described here, and I was trying to explain that, but I couldn't get to say that.


The use case is, given a tree structure like this:
├── siteA
│   ├── regionA
│   │   ├── service_A
│   │   ├── service_B
│   │   ├── service_C
│   │   ├── service_D
│   │   ├── service_E
│   │   ├── service_F
│   │   └── service_G
│   └── regionB
│       ├── service_A
│       ├── service_B
│       ├── service_C
│       ├── service_D
│       ├── service_E
│       ├── service_F
│       └── service_G
└── siteB
    ├── regionA
    │   ├── service_A
    │   ├── service_B
    │   ├── service_C
    │   ├── service_D
    │   ├── service_E
    │   ├── service_F
    │   └── service_G
    └── regionB
        ├── service_A
        ├── service_B
        ├── service_C
        ├── service_D
        ├── service_E
        ├── service_F
        └── service_G

I'd like to be able to run terraform on, eg. all service_C and service_D targets.
I actually have many more sites/regions/and services than shown above! :)

Seems like a handy feature to have. PR welcome 👍

PR welcome 👍

Bah!

Hi,
I am working on a PR to provide this functionality, and have some questions regarding how to cope with running it in combination with the exclude-dirs flag
My take is that when running with include-dirs it makes no sense to add an exclusion list as well, but this is only my take and maybe there are cases where this would be useful
In the meantime, I am borrowing heavily from the -exclude-dirs logic to implement this, and hope to have an initial PR soon (working on the tests as we speak)

My take is that when running with include-dirs it makes no sense to add an exclusion list as well, but this is only my take and maybe there are cases where this would be useful

Typically, whitelist/blacklist logic works as follows:

If neither is specified, include all
If blacklist is specified, include all except the items in the blacklist
If whitelist is specified, only include items in the whitelist
If both whitelist and blacklist are specified, include items in the whitelist, minus those in the blacklist

Ok, then the flow in configstack/module.go should be:
```
   // this will flag all modules not in the included-dirs glob as Excluded
    includedModules, err := flagIncludedDirs(crossLinkedModules, terragruntOptions)
if err != nil {
	return []*TerraformModule{}, err
}
finalModules, err := flagExcludedDirs(excludedModules, terragruntOptions)
if err != nil {
	return []*TerraformModule{}, err
}

.. and a test for checking that the include/exclude thing works would be to run it, say, with
`
opts.IncludeDirs = []string{canonical(t, "../test/fixture-modules/module-c"),canonical(t, "../test/fixture-modules/module-b")}
opts.ExcludeDirs = []string{canonical(t, "../test/fixture-modules/module-b")}
`

and expecting only module-c and module-a (because of dependencies) to be flagged as included

I was looking through old issues to see if anything could be closed out.
@mattiarossi It looks like your PR adding this functionality was merged. Can this issue be closed?

This was indeed resolved in #626, so closing.

This was indeed resolved in #626, so closing.


Add ExaCA input file generator

To be consistent with 3DThesis and AdditiveFOAM, updating material properties in ExaCA from a Mist file would be valuable. I think there are a couple of questions about what is a "material property" versus a "model parameter" in the ExaCA inputs, e.g., nucleation parameters, but it could be valuable to be able to track common material-specific model parameters in Mist files.
Examples of ExaCA material files can be found in the ExaCA repo: https://github.com/LLNL/ExaCA/tree/master/examples/Materials
As mentioned above, I'm not sure if Mist files are the right place to store data about the nucleation parameters. But if so, the following dictionary in the main ExaCA input file would need to be updated in addition to the material file:
{
   "Nucleation": {
      "Density": 10,
      "MeanUndercooling": 5,
      "StDev": 0.5
   }
}

Looking at the ExaCA input files, I think that the solidification range definitely makes sense to get from Mist (and we already have what you'd need to calculate it mostly). I think there's a strong argument that the interfacial response function is fundamental enough to the material to add it to Mist.
I am less confident about the nucleation parameters. Those are essentially 100% from calibration vs experiment, right?

You can calculate nucleation density as a function of undercooling from CALPHAD (at equilibrium), but I don't know if that has a one-to-one mapping with how nucleation is defined in the ExaCA model. @MattRolchigo would be better to comment on that.
At any rate, the nucleation parameters have historically been what has been adjusted when calibrating CA models to experiments.

I would vote for adding material property generation for CA where it makes sense, but not forcing it in where it doesn't make sense. Nucleation seems better left to myna (just an opinion) - and there will be plenty of cases where we need variable input support that isn't a "material parameter", e.g. details of how you calibrate the material absorption for an optimal heat transfer simulation

Right now, ExaCA doesn't actually use the freezing range for anything, though it did in the past (and may in the future based on improving flexibility with how we calculate/extract cooling rate information). I agree on leaving the nucleation parameters out - the nucleation parameters used by ExaCA are for heterogenous nucleation which may be process/feedstock dependent. I imagine the nucleation density you can calculate with CALPHAD would likely be homogenous nucleation @gknapp1 ? Though it may be useful in the future if ExaCA has the CALPHAD-extracted nucleation density vs undercooling, I wouldn't know what to do with it at the moment.

@MattRolchigo, yeah you could calculate the homogenous nucleation rate from CALPHAD, but the uncertainty bars on that would be huge. If we think feedstock variability is a main contributor, then that would be an argument to put it in Mist, but if we think the process dependence is larger, that would be an argument against putting it in Mist.
For the interfacial response function, do you expect to usually use a polynomial? Or do you have plans to use other formulations? (A table that you interpolate from, some analytic function with exponentials or logs or other special functions?)
If it's just the freezing range and a polynomial for the interfacial response function, implementing that should be very easy.

@stvdwtt I honestly don't know whether the material or process-dependence would be larger, but either way I imagine the large error bars would mean that it would end up being a calibration parameter either way. For the interfacial response function, I imagine using either a polynomial or an exponential will be sufficient for any future cases I can think of

@MattRolchigo, would it be too limiting if we just implemented polynomial interfacial response functions for now? I'm not entirely sure how we'd want to parameterize an exponential IRF yet (do we have an generic exponential functional form? Do we have special-case coefficients for IRFs?). If you had an exponential, would it be a "pure" exponential, or a polynomial plus an exponential term?

@stvdwtt I think just implementing polynomial functions would be fine - we aren't that sensitive to it (and we used exclusively polynomial forms for awhile anyways). Right now we only accept exponential functions of the form V = A * V^B, and we don't allow combining of functional forms


Add server side pre-rendering for SEO

We currently use a catch all server side routing to index for our front end website. We need to add server side rendering so search engines won't think we have a single page.

Initial investigations:
https://stackoverflow.com/questions/27928372/react-router-urls-dont-work-when-refreshing-or-writting-manually/36623117#36623117
http://janekk.github.io/tech/2014/07/25/aspnet-mvc-reactjs-browserify.html
https://reactjs.net/

Moving to site backlog.


Upgrade to ZIO 2.0.0-M4

Potentially fixes #463
Mainly want to run the CI process against this branch, as I'm seeing some cross version errors locally.

Ah, I see. Are you available to discuss the details of what needs to happen
via Slack/Zoom/etc?
On Wed, Oct 20, 2021, 10:41 AM Ferdinand Svehla @.***>
wrote:

We need to figure out how to support ZIO 1 and 2, we could start with a
topic branch and publish snapshots from there, wdyt?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/zio/zio-json/pull/464#issuecomment-947843504, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAPVWHBVWFK5J3RNIJOMRUDUH3WMLANCNFSM5GJU4FQA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.


[boost-thread] CMake Error

Boost Thread cannot be built with LLVM.
Do I understand correctly that this is already covered by this issue by @Neumann-A?
Quite some effort seems to have been invested already - thank you for that.
How to reproduce:
vcpkg.exe install boost-thread --overlay-triplets=..\my-vcpkg-triplets --triplet=x64-win-llvm
Result:
CMake Error at scripts/cmake/vcpkg_execute_build_process.cmake:134 (message):
    Command failed: C:/Code/vcpkg/downloads/tools/cmake-3.27.1-windows/cmake-3.27.1-windows-i386/bin/cmake.exe --build . --config Debug --target install -- -v -j13
    Working Directory: C:/Code/vcpkg/buildtrees/boost-thread/x64-win-llvm-dbg
    See logs for more information:
      C:\Code\vcpkg\buildtrees\boost-thread\install-x64-win-llvm-dbg-out.log

Call Stack (most recent call first):
  installed/x64-windows/share/vcpkg-cmake/vcpkg_cmake_build.cmake:74 (vcpkg_execute_build_process)
  installed/x64-windows/share/vcpkg-cmake/vcpkg_cmake_install.cmake:16 (vcpkg_cmake_build)
  installed/x64-windows/share/boost-build/boost-modular-build.cmake:139 (vcpkg_cmake_install)
  ports/boost-thread/portfile.cmake:12 (boost_modular_build)
  scripts/ports.cmake:170 (include)

Log file:
install-x64-win-llvm-dbg-out.log ends with
error:     '/boost//C:/Code/vcpkg/installed/x64-win-llvm/debug/lib/boost_chronod.lib'
error: referred to from project at
error:     '..'

That boost prefix to the absolute path is unsurprisingly a problem.
Luckily, I can work around this by building only our project with LLVM, and sticking with MSVC for the VCPKG stuff for now.

Installing 51/51<EMAIL_ADDRESS>Building<EMAIL_ADDRESS>-- [OVERLAY] Loading triplet configuration from: E:\all\my-vcpkg-triplets\x64-win-llvm.cmake
-- Downloading https://github.com/boostorg/thread/archive/boost-1.84.0.tar.gz -> boostorg-thread-boost-1.84.0.tar.gz...
-- Extracting source E:/vcpkg_cache/downloads/boostorg-thread-boost-1.84.0.tar.gz
-- Using source at E:/all/vcpkg/buildtrees/boost-thread/src/ost-1.84.0-19b5b607c9.clean
-- Getting CMake variables for x64-win-llvm
-- Including E:/all/vcpkg/ports/boost-thread/b2-options.cmake
-- Configuring x64-win-llvm
-- Building x64-win-llvm-dbg
-- Building x64-win-llvm-rel
-- Copying headers
-- Copying headers done
-- Installing: E:/all/vcpkg/packages/boost-thread_x64-win-llvm/share/boost-thread/usage
-- Installing: E:/all/vcpkg/packages/boost-thread_x64-win-llvm/share/boost-thread/copyright
-- Performing post-build validation
Stored binaries in 1 destinations in 110 ms.
Elapsed time to handle boost-thread:x64-win-llvm: 7.6 s
boost-thread:x64-win-llvm package ABI: 83b23558dfdbd34d272e7544650ed0145a3f38d0843d50829d1ce4f540bb7be6
Total install time: 1 min
The package boost is compatible with built-in CMake targets:

    find_package(Boost REQUIRED [COMPONENTS <libs>...])
    target_link_libraries(main PRIVATE Boost::boost Boost::<lib1> Boost::<lib2> ...)

That boost prefix to the absolute path is unsurprisingly a problem.

no that is normal. The problem is that the name boost_chronod.lib is wrong.
You are probably not using my overlays for boost-moddular-build-helper, boost-uninstall and vcpkg-cmake-get-vars from https://github.com/Neumann-A/my-vcpkg-ports.

Works like a charm, thanks.