Version Compatability

Hi there!
Thanks for a very useful wrapper :)
I managed to get it working with Unity v2021.3.3f1+.
My question was regarding older version compatibility, say 2019.3.0f6?
Out of curiosity mostly, do you think it would be plausible to downgrade the project to such a version?
I attempted to downgrade the wrapper and stumbled across numerous issues.
I managed to fix some straightforward APIs such as: https://stackoverflow.com/questions/74906471/unitywebrequest-does-not-contain-a-definition-for-result
Yet I have a few more hurdles to go through as it seems. Just wondering if it is at all possible to use the wrapper for the aforementioned version (or older ones), thanks again 👍

Hi there,
I'm glad you find it useful :-). I would like to add support for older versions of Unity, so if you could screenshot all of the issues you're having and include them in this issue I will resolve them.

I managed to get things working.
The main issue was actually the link I attached above.
There were other errors such as UI and Visual Scripting related, but if anyone would like to get started with the basic wrapper that @GraesonB kindly wrote, I found the following to work with Unity 2019.3.0f6 versions and lower.
The requests.cs script, will not be compatible with Unity 2020.3 versions and lower.
More specifically, UnityWebRequest will not have a definition for result, which was added at 2020.3+
A quick workaround is to use Conditional Compilation as suggested by the above link.
In the requests.cs script, the following small modifications worked for me:
using System.Collections;
using System.Collections.Generic;
using UnityEngine;
using UnityEngine.Networking;

namespace ChatGPTWrapper
{
    public class Requests
    {
        private void SetHeaders(ref UnityWebRequest req, List<(string, string)> headers)
        {
            for (int i = 0; i < headers.Count; i++)
            {
                req.SetRequestHeader(headers[i].Item1, headers[i].Item2);
            }
        }

        public IEnumerator GetReq<T>(string uri, System.Action<T> callback, List<(string, string)> headers = null)
        {
            UnityWebRequest webRequest = new UnityWebRequest(uri, "GET");
            if (headers != null) SetHeaders(ref webRequest, headers);
            webRequest.downloadHandler = (DownloadHandler)new DownloadHandlerBuffer();
            webRequest.disposeUploadHandlerOnDispose = true;
            webRequest.disposeDownloadHandlerOnDispose = true;

            yield return webRequest.SendWebRequest();

            #if UNITY_2020_3_OR_NEWER
            switch (webRequest.result)
            {
                case UnityWebRequest.Result.ConnectionError:
                case UnityWebRequest.Result.DataProcessingError:
                    Debug.LogError("Error: " + webRequest.error);
                    break;
                case UnityWebRequest.Result.ProtocolError:
                    Debug.LogError(": HTTP Error: " + webRequest.error);
                    break;
                case UnityWebRequest.Result.Success:
                    var responseJson = JsonUtility.FromJson<T>(webRequest.downloadHandler.text);
                    callback(responseJson);
                    break;
            }
            #else
            if(!string.IsNullOrWhiteSpace(webRequest.error))
            {
                Debug.LogError($"Error {webRequest.responseCode} - {webRequest.error}");
                yield break;
            }
            else
            {
                var responseJson = JsonUtility.FromJson<T>(webRequest.downloadHandler.text);
                callback(responseJson);
            }
            #endif
            webRequest.Dispose();
        }

        public IEnumerator PostReq<T>(string uri, string json, System.Action<T> callback, List<(string, string)> headers = null)
        {
            UnityWebRequest webRequest = new UnityWebRequest(uri, "POST");
            if (headers != null) SetHeaders(ref webRequest, headers);

            byte[] jsonToSend = new System.Text.UTF8Encoding().GetBytes(json);
            webRequest.uploadHandler = (UploadHandler)new UploadHandlerRaw(jsonToSend);
            webRequest.downloadHandler = (DownloadHandler)new DownloadHandlerBuffer();
            webRequest.disposeDownloadHandlerOnDispose = true;
            webRequest.disposeUploadHandlerOnDispose = true;

            yield return webRequest.SendWebRequest();

            #if UNITY_2020_3_OR_NEWER
            switch (webRequest.result)
            {
                case UnityWebRequest.Result.ConnectionError:
                case UnityWebRequest.Result.DataProcessingError:
                    Debug.LogError("Error: " + webRequest.error);
                    break;
                case UnityWebRequest.Result.ProtocolError:
                    Debug.LogError(": HTTP Error: " + webRequest.error);
                    break;
                case UnityWebRequest.Result.Success:
                    var responseJson = JsonUtility.FromJson<T>(webRequest.downloadHandler.text);
                    callback(responseJson);
                    break;
            }
            #else
            if(!string.IsNullOrWhiteSpace(webRequest.error))
            {
                Debug.LogError($"Error {webRequest.responseCode} - {webRequest.error}");
                yield break;
            }
            else
            {
                var responseJson = JsonUtility.FromJson<T>(webRequest.downloadHandler.text);
                    callback(responseJson);
            }
            #endif
            webRequest.Dispose();
        }
    }
}

I hope this helps :)

@DeathByCh0c0 I Didn't have time to get around to it yesterday, I appreciate you posting your fix :-). I'll update the repo tonight

@DeathByCh0c0 not sure if you noticed or not but I added your changes to the repo. Also, the official API just launched today and its 10x cheaper than Davinci! I've added support for the new API, so feel free to test it out and leave feedback.
Seeing as you're studying human-computer-interaction and ML, if you're hoping to run some models on data that's generated from user interactions with ChatGPT in your use case, I can add a feature to pipe that conversation data into a NoSQL DB for you since that's not far off from my own plans. Let me know if you're interested

@GraesonB Hey! I did see the changes, glad to see these were somewhat helpful regarding compatibility with lower Unity3D versions :)
I actually just checked the changes you made today and it seems that the gpt-3.5-turbo works for me! Good job! 👍 From your message I gather you are referring to querying past history chat(-s)? As far as I can tell, if you terminate the active scene in play mode and restart it, past chat cannot be accessed, unless I guess you parse that as part of the initial prompt when restarting the scene. Sorry if I misunderstood your message.

@DeathByCh0c0  Haha no worries at all! My fault for being unclear. I plan on making a server for my own use case that will store conversations in a database that could be accessed later down the road in Unity by a fetch request. I'm not sure what your use case is, but if you're interested in saving conversation history in your own database, let me know :-)


feat: Add ftl-min-version to ftl-project.toml

Issue https://github.com/TBD54566975/ftl/issues/1183
Logic for what versions pass/fail is documented in version.go.
Manually tested the changes to cmd/ftl/main.go by:

Set ftl.Version by hardcoding it in ftl/Justfile
Set ftl-min-version in the top level ftl/ftl-project.toml
just build ftl to make an FTL binary
build/release/ftl schema get to see if it fatals or not

Successfully got: ftl: error: FTL version '0.1.1' predates the minimum version '10.0.1'
When it worked correctly, with no error: ftl: error: unavailable: dial tcp [::1]:8892: connect: connection refused

Nice!
What's the user experience going to be for updating/managing this field? I'm wondering if maybe we should have an ftl upgrade command that upgrades this field, as well as the go.mod and pom.xml dependencies.

That's a great point. Something I've been wondering about is that while the version in go.mod is explicitly the minimum required version, I wasn't sure if pom.xml was meant to provide its version numbers as minimum versions or target versions. I'll take a quick look around and see if I can figure it out. Having an upgrade helper would be awesome if they were all compatible :D
I'll start throwing some draft ideas and open questions into a design doc to talk through.


Enhance xt.input attribute

def index() -> xt.Component:
    layout = xt.form(xt.vstack(
        xt.input(
            placeholder="Paste YAML code here",
            on_change=State.on_yaml_input_change,
            width="30%",
            height="300px",
        ), ),
        xt.button("Convert to Python", on_click=State.handle_conversion),
        xt.text(State.python_data, font_size="2em"),
        spacing="1em",
        align_items="center",
        justify_content="center",
        height="100vh",
    )
    return layout

Problem statement
when I type inside the input it shows

Feature
When I press enter it should go to next line

Hey Anirud,
For handling larger text inputs like YAML code,  we can use xt.text_area a better fit. Here's a quick example to show how it can be set up:
xt.text_area(
    placeholder="Paste YAML code here",
    on_change=State.on_yaml_input_change,
    width="30%",
    height="300px",
)

By the way, I'm currently working on putting together more detailed documentation for these components, including text_area. It's a work in progress, but you can check out what I've got so far here. I'm planning to get the form-related docs polished up first.

Thank you, it's working :)


new(ci): added update-kernels gha.

What type of PR is this?
/kind feature

Any specific area of the project related to this PR?
/area CI

Does this PR require a change in the driver versions?
No

What this PR does / why we need it:
Which issue(s) this PR fixes:

Porting of update-kernels Prow job.
Waiting for Poiana token (missing at the moment).
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

NONE

Welcome @cappellinsamuele! It looks like this is your first PR to falcosecurity/kernel-crawler 🎉

LGTM label has been added.  Git tree hash: 79f8fdaed7616fc39a319075fb915f365dbe787c

/kind feature

/area CI


Add-design-authors-on-Individual-Design-pages-on-the-catalog

Description
This PR fixes #1121

Adds the name of the publisher on the individual design page:

Fixes error in the yaml syntax in the file : collections/_catalog/deployment/2df29b2b-7e5e-4d8b-a5b3-3dea569f4d25.md

Notes for Reviewers
Signed commits

[ ] Yes, I signed my commits.

Nice!

👏


added socketio driver

This driver uses socketio to send the universe data as an array over to other programms.
The debug mode prints connect and disconnect messages.

Is there anything else which has to be done before this PR can be merged?

While I did not make tests, it looks fine for me. Thanks for your work.
@wiedi or @bluemaex, any thoughts on this? I think we can merge it, since it does not affect any existing things and obviously works for @hrueger.

Maybe it should be called "socketio" instead of just "socket" because that's very generic. Other than that I think it's fine

In the commit message there's a spelling misstake, but in the code it is written correctly

Thanks! I've squashed it so the commit message is fine.

Oh, I somehow forgot to add the driver to the readme's driver list, should I create a new pull request for this? Or do you think that this is not necessary since it is not a 'real' hardware driver?

Sure, correct documentation would be good :)


refactor: better cache update notification

Hello, I'm using macos, I dont know if this is the reason why my cache notification in the status bar is not showing or not, so I changed your notification to really appear in the notification section with progress indicator, I hope you like it.

another thing, but this is not related with this pull request, I hope you noticed the url definition provider, what if, it beside to take the user to the urls.py, it also could set some highlight or simply scroll until the line, I dont know how to do that so I did not make it myself. 😂

Showing statuses using notification is unusual. I like the current way. I don't know why it wouldn't show up in mac. Could you run the extension in debug mode to see if there is something in the debug console?

another thing, but this is not related with this pull request, I hope you noticed the url definition provider, what if, it beside to take the user to the urls.py, it also could set some highlight or simply scroll until the line, I dont know how to do that so I did not make it myself. 😂

I don't want to do much work on this extension. Because I am building a framework on top of django called picomet. I will build an extension for it soon.

ok, today is another day, I ran the extension again e now it worked! 🤡
I think you can close it.


Testing bullet_train-core #358

The tests are failing locally due to an OpenAPI issue, but apparently the tests against main work on CI, so I'm testing https://github.com/bullet-train-co/bullet_train-core/issues/358 with CI here. We can close it if it passes.
All I've done here is Super Scaffold the example models stated in that issue.
rails g model Site team:references name:string url:text
bin/super-scaffold crud Site Team name:text_field url:text_area
rails g model Page site:references name:string
bin/super-scaffold crud Page Site,Team name:text_field
rails g model Section page:references title:string
bin/super-scaffold crud Section Page,Site,Team title:text_field

Tests are passing! Will go ahead and close this and https://github.com/bullet-train-co/bullet_train-core/issues/358.


Improve the documentation and logs for sourcing the export file.

Motivations
It's not clear enough and users are missing this fundamental step.

Solved via f61933c


ExportFormat support for "long text" with wrapping

Use case is a grid where some fields have longer text strings - a few sentences of notes, say.
Would like to be able to specify an ExportFormat code that would cause an exported Excel sheet to wrap the text and apply auto row-height mode so all text is immediately visible / printable within the cell.
Have not yet reviewed current default behavior - or verified that this is possible given Excel / Apache POI functionality. It seems reasonable, however, and in particular could make Excel exports a more attractive option for printing support in some particular cases.

Adding Tom, who has the experience with this.  Hoping Tom can help guide Brendan on this one.

Hi Brendan
Haven't tried it yet, but looks like a good start :)
How does this handle auto heighting the row to display the full wrapped text? Again, haven't tried it, but it looks like calling row.setHeight(-1) on each row after we've added the content could do this for us (unless we already have that behaviour by default). Docs
Feel free to reach out if you have any questions or want to go over anything.
Cheers
Tom

Hi Tom,
I've not been able to set auto height with setHeight(-1), though it does work for positive values.
setWrapText(true) does auto height, but the default column width is probably too large for our purposes (see output sample below).
I think it makes sense to implement this behavior where the styles map is defined on line 128 of GridExportingImplService. This allows us to only set wrapText on specific columns. We could define a new ExportFormat for a Column e.g. LONG_TEXT, and then set wrapText and a default column width accordingly.
Note that in the branch I created for this issue, wrapText can only be toggled for the entire spreadsheet.
Let me know what you guys think.

Okay - if setWrapText(true) auto heights, don't worry about the setHeight(-1) :)
Sounds like a good approach to use a custom ExportFormat to set wrap text and a reasonable default width. Bear in mind that on line 199 we are looping through the columns and calling autoSizeColumn() for each - we probably want to skip any column with wrap text here.

Sounds good, thanks. Good catch on the column autosize.


Client Allocation Request for: continental

Client Allocation Questions
Core Information

Name: continental
Website / Social Media: https://www.continental.com.hk/
Region: Asia (excl. Greater China)
DataCap Requested: 50TiB
Addresses to be Notarized: f1g6kef5vs57di4uu6o6hj6vz35wnbqbhrnnz5kuq
Notary Requested: fireflyHZ

@tangyang100 Please subscribe to notifications for this Issue to be aware of updates. Notaries may request additional information on the Issue.

Repeat application, close


events: Adds Custom Resource event

Adds CloudFormation Custom Resource event type.
Tests based on examples sourced from AWS documentation. Examples can be found here and here.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Does this not already exist in the cfn folder?

Does this not already exist in the cfn folder?

You're right. Sorry, I missed that. I'll close this one. Thanks!


Uplift terra-popup to support advanced positioning and dynamic sizing.

Issue Description
Currently the popup relies on fixed height and widths to handle it's positioning. There has been an ask from consumer to allow for dynamic sizes.
Reliant on work from issue #739
Issue Type

[ ] New Feature
[x] Enhancement
[ ] Bug
[ ] Other

Expected Behavior
A custom/dynamic size option is to be added to the popup to allow content to size popup based on it's own size.

Current discussion has risen in how to handle a dynamically sized popup. The issue being that a dynamically sized popup when bound will no longer be able to handle it's own scrolling. So if it was handling it's scrolling prior, a bounding outer container would force a double scroll bar situation.
My current proposal is that is a height or width is set as dynamic to decorate content with a prop stating that it is bound in order to allow the content to set it's own sizing to 100% and as such fill the container, providing correct scrolling and allowing flex enabled headers.

Really the popup should pretty much be equivalent to the popover in bootstrap https://v4-alpha.getbootstrap.com/components/popovers/.  Assume a width, and have no constraint on height. This is very simple to achieve.
Past that is the use case where the content needs a bound width/height, which is a legitimate use case. Because that use case is more advanced, it should be built on the simple, static popup with no height contraint.. rather than the simple popup being the special case.

The bootstrap popup does not meet our UX requirements. The popup does not become fullscreen at small view ports. It does not dynamically move the display position based on popover location.
We can assume a width with no constraint on height, but when presented in a small view port or with a very large height we need to introduce a height constraint to allow all layouts to be able to be implemented. For example, something with a fixed header.
The benefit of @dkasper-was-taken 's solution is that the simple pop-up is not treated as a special case, when a dynamic size is selected, the only difference is that a 'bounded' prop will be set on the popover content to allow it to layout differently if it chooses to.

Tech Design for Terra-Popup Update
Summary:
This component is design as a light weight replaced for tether. Incorporating a margin to allow for positioning of arrows more easily, mirroring of offsets to account for flipped, rotated, and overlapped positions, fallback behaviors, and correct positioning when zoomed on a mobile device.
Responsiveness:
All popup sizes, including custom, respond to the bounds of the bounding rect or window. If using custom sizes, children will be decorated with a prop to indicate that they needs to update their display. This is specifically to account for custom sizes that set their own scroll or what to retain a header.
Accessibility
The tadIndex behavior has been update to work the same as the modal, correctly highlighting the popup on all browsers. Chrome and IE we previous offenders.
New React Props:

Prop
Type
Default
Description

targetAttachment
string
null
Attachment point for the target.

Updated React Props:

Prop
Type
Default
Description

contentHeight
string
'80'
'custom', '40', '80', '120', '160', '240', '320', '400', '480', '560', '640', '720', '800', '880'.

contentWidth
string
'240'
'custom', '160', '240', '320', '640', '960', '1280', '1760'.

Example:
       <Popup
          contentAttachment="top left"
          contentHeight="custom"
          contentWidth="custom"
          isOpen={this.state.open}
          onRequestClose={this.handleRequestClose}
          targetRef={() => document.getElementById('popup-standard-button')}
          targetAttachment="bottom center"
        >
          <ExamplePopupContent />
        </Popup>

+1 on tech design. Nice work @dkasper-was-taken

+1 on tech design.  The only thing I would question is the word "custom" for the height and width.  Would "dynamic" be more appropriate?  Or something else?

With "custom" do you mean responsive?

JIRA created

I'm fine renaming custom to something else.  The concept allows the popup on each update to adjust to the content of the popup, rather than a prescribed size.
So custom, dynamic, unbounded, etc. Anyone want to way-in on their favorites?

unbounded

+1 for dynamic.


how to upload or download large files

i want to upload large files to server from client, now ,i can only upload a byte[] to server,  Can the data be called back through the stream？？ urgent ！！！

See my reply to similar question.
Summary: create a file server using already deployed Netty library.


Suggestion - standardise middleware locals context

In the documentation for writing the middleware there is an example:
const express = require('express')
const app = express()

const requestTime = function (req, res, next) {
  req.requestTime = Date.now()
  next()
}

I'd like to point out that this seems like a bad practice and would like to suggest a change.
Adding new attributes to an uncontrolled object could lead to name conflicts. This scenario isn't very likely to happen but leaves room for an error.
The solution is rather simple, if it makes sense to add values to req object there should be a standardised API or in this case attribute for doing so just like with res object.
From design perspective it makes sense that there is a scoped place (object) that can be edited and modified safely. This attribute(s) represent a contract that both provider and consumer should then respect.
Currently, there is no clear difference between writing values in req or res objects and I believe it makes sense to define cases clearly.
Propositions:

Define res.locals as a main way for passing the values
Add req.locas as a specified attribute for passing request related values

Conceptually, there may be a difference between req and res values but it's a bit vague. For example, requestTime value is somewhat related to the request, but the problem comes with data passed to add more information to the context for accessing the actual response data. Where should it be stored?
Another reason for having req and res values separated might be to prevent renderer from accessing all the data in the context, but I am uncertain if it's a valid concern.
If res.locals is so tightly coupled with renderer then the name is ambiguous.
All this, in my opinion, suggest that it'd be better to have one scope for storing the contextual values. By slightly loosening up res.locals definition, and making it less coupled with the renderer (conceptually) it could be a good place for storing all the data.

Hi @MrBr thank you for the suggestion! This has been brought up several times, and it seems there is confusion over res.locals and we tried to clear that up with our documentation.

As noted in https://expressjs.com/en/4x/api.html#res.locals the res.locals is just for exposing specific information to your rendered templates. That is the purpose of this object, not a general store of anything you want (unless you do infact what to send all that information to your rendered templates, of course).
It is perfectly acceptable to store anything you want on our req and res objects, particularly when you are authoring middleware. This is why we should example of doing that. This is how all our middleware work in the ecosystem, and why you can have things like req.session (session middleware are setting a setting property directly on req), res.body and req.files (body parsers directly set a property on req) and many others. There is nothing wrong with a middleware decorating req and res with additional properties, and in fact is encouraged as our documentation suggests.

Thank you for this fast clarification I understand intent better.
However, I still feel like it'd be a better design decision to have a scoped place for storing contextual values that is not req, res or res.locals object.
In my opinion this isn't a good example of decoration. When decorating an object the initial shape should be preserved (wrapped). In the examples above it's not new behaviour that is being added, just data without any boundaries.
We can look that addition as a behaviour of adding data to the context and I believe it makes sense to encapsulate that behaviour, put some boundaries around it.
A different thing would be if I'd like to change the logic of send method. Then this would indeed be a behavioural change but it still make sense to preserve the original.
I understand this is more theoretical thing than practical. It's still an interesting topic.

Hi @MrBr thank you for that. I'm not really sure what you are envisioning there, and what you mean, exactly. Perhaps it would help if you could build out perhaps some kind of prototype of what you are envisioning? For example, fork expressjs/express repo and build out the changes to Express.js for providing the encapsulation you are thinking and can link that fork here to help us better understand the conversation?
I assume from your text it is more than just Express.js adding a req.data = {} bag where middleware can just pile on properties, because that is no better/less conflicts/any better boundaries than just req or res itself -- any given middleware still won't know if their chosen property will conflict or not better than if it were just on req.

Just adding an attribute would suffice. I'll elaborate in details.
Every features has a definition, I'm arguing that adding value to a local context is a feature. In express there isn't such a definition in the API specification. This functionality is only briefly mentioned in an example about writing middleware.
I believe this is the first problem and the reason why there is still an ongoing debate in the community on this topic. Adding a page similar to existing Overriding the Express API, something like Passing value to middleware would be very helpful.
Currently, there is no local context, instead it's advised to add values to req or res objects. I've purposefully emphasised a feature, because if it's looked as a thing for itself, local context would be something tangible, something with boundaries. Just like locals for renderer.
What we have now is a convention. The req and res object represent a local context where temp values can be saved. This is where we reach to the boundaries problem. Those objects are used for providing the Express API and in the same time used for storing the values. Those should be 2 separate things, or if we get back to my first point, adding value to the context should be API functionality.
Because those objects are "abused" this can lead to situation where by saving a value to the local context API can be overridden. So, when I say boundaries I mean boundaries between local context and API object. Local context should be a part of the API. Then, boundaries would practically assure that no new Express API feature will override a value (or vice versa), and it should never be possible for such a thing to happen.
As you mentioned, middleware can still override the values if they use the same key but there is a big difference. Those middleware are composed by someone else so there will be no conflict with the library itself. This is the boundary border, you only guarantee for API not how it's used.
Reserved field
Getting back to the reserved field. That would be enough, in a theory an interface such as one of localStorage could be created but it's just an overhead.
An idea!
I've mentioned local context so many times that I figured that context is a good name for this feature. And while writing this I've come up to an idea. What if the middleware signature would be changed to:
const middleware = ({ req, res, context }, next) => {
  context.session = '';
};

The value doesn't belong to request or response, it belongs to the current middleware context. What do you think?
P.S.
Why is aforementioned decoration bad.
const obj = {
  override: 1
};
const middleware = (ref, next) => {
  obj.override = null;
  next();
}

middleware(obj, someNext);
// The middleware spills out of the scope and we should avoid such a behaviour because there is no guarantee how obj will be used later
// I understand this is currently not causing any issues but conceptually I believe it's not good pattern

// The right way to do a decoration would be to leave the object intact
// For example, with a bit different next signature
const obj = {
  override: 1
};
const middleware = (ref, next) => {
  next({ ...ref, override: null });
}

// This approach allows something extra
// Because the initial object hasn't been changed, we can still depend on it
const obj = {
  cb: () => {}
};
const middleware = (ref, next) => {
  const newCb = () => {
   log();
   ref.cb(); // This wouldn't be possible in the first example
  }
  next({ ...ref, cb: newCb });
}


IUserStore<TUser, TKey> seems to be missing

Reading the documentation regarding changing the primary key of the users using ApplicationUser : IdentityUser<int> at https://docs.microsoft.com/en-us/aspnet/identity/overview/extensibility/overview-of-custom-storage-providers-for-aspnet-identity when using a custom UserStore.
This seems applicable to Identity Core, until you get to the part with having the custom UserStore implement IUserStore<TUser, TKey>. It seems this interface with TKey does not exist: https://github.com/aspnet/Identity/blob/dev/src/Microsoft.Extensions.Identity.Core/IUserStore.cs#L14
Not being able to specify this TKey causes my UserStore to require me to implement FindByIdAsync with a string parameter that I would then have to parse to an int before doing the lookup - which is a bit annoying.
Has the way to achieve this been changed? - I was not able to find out a way to get all the way using the classes and interfaces available .. but I might have missed something.

Identity in Core always uses a string as a key, removing TKey was a specific design decision.
So yes, you must convert to an int before doing a lookup.


Update README.md

Would you mind to add this badge to your readme.  Its just a backlink and would help JS.ORG to get some attention.

Thanks

:+1:


New attack technique: Login via AWS EC2 Serial Console

Login via Serial Ports: AWS
https://unit42.paloaltonetworks.com/cloud-virtual-machine-attack-vectors/

Suggested tags: kind/new-technique, platform/aws

duplicate of https://github.com/DataDog/stratus-red-team/issues/487


Fixed framerate tick subscription on the client

At present, the Frame event on the client will run every frame (as the name suggests); however, this will lead to a) unnecessary work (more simulation than is strictly necessary) and b) unnecessary network traffic (code that sends updates every frame will lead to queue backpressure on the server)
We should offer a fixed rate tick that only runs every 1/60th of a second (or whatever rate we pick, perhaps server-specified, but we probably don't want it to be a parameter server owners tweak without understanding?)
Open questions:

What should the tickrate be?
What happens when the client drops below that tickrate?
What happens when it drops just below, so that you have the worst-case scenario of having to wait another full tick again?
Should developers expect that frametime to be constant, or should they still need to use delta_time()?

Experienced it on macOS when:

running on different displays (120fps on builtin, 60fps on external)
minimising the app - immediately jumps to 600-700fps
running with --headless - also jumps to hundreds of fps

I added fixed_rate_tick to the API some time ago. The answers to the questions posed above are:

Up to the user.
It's a simple if (time() - last) > duration implementation, so it'll run on the next frame.
 Not much we can do about it.
fixed_rate_tick returns the elapsed time for developers to use.

We can revisit this if those nuances become an issue.


Enhancement for image support in reports

Add the ability for images to be dynamically resized when rendering in reports.
For example, pass max_width and max_height parameters through to the part_image template tag...
Idea which came about when implementing https://github.com/inventree/InvenTree/pull/5907

Actually was implemented in #5907


Update Thema code list to reflect v1.4.2 (#309)

Fixes #309.
Source: https://www.editeur.org/files/Thema/1.4/Thema_1.4_en/Thema_v1.4.2_en.json.

Oh - could you also update the changelog, @rhigman ?


How to get downloaded image from my react component

Hello, is there any methods/options available for downloaded image that i can get from react component so i can save my database or server from my component.
If yes please share methodology of that.
Thanks
MD Helal Uddin

@helal-apex
ImageEditor does not support saving images to a server or database directly.
I think you should develop some (get image & API call for saving the image to your DB) modules that you want to do.


Fix rosetta pax result tables and cleaned up some dead code paths

This PR fixes some issues in reporting that were introduced in #440 . In particular, with the introduction of a non-empty ARTIFACT_NAME in the rosetta tests, the tables no longer were presented correctly:

I couldn't find anywhere that used the non-default value of ARTIFACT_NAME, so I removed it in the _test_*_rosetta.yaml files.
This change also cleans up some dead code (EXTRA_TEST_ARGS, EXTRA_GIN_ARGS) since they didn't appear to be used anywhere.
Also the table for rosetta-pax metrics were quite long so I rewrote that to output as a markdown table.

Placed PR into draft until CI passes

presubmit timedout (6hr exceeded). Rerunning manually: https://github.com/NVIDIA/JAX-Toolbox/actions/runs/7687728046

The tables appear in different sections, but they are correctly rendered now. I believe we should merge this now since we can at least view failures correctly now. I'll follow up with a fix to the tables appearing in different sections.


VirtAddr::try_new() succeeds on non-canonical addresses

From the VirtAddr::try_new docs:

This function tries to performs sign extension of bit 47 to make the address canonical. It succeeds if bits 48 to 64 are either a correct sign extension (i.e. copies of bit 47) or all null. Else, an error is returned.

This means that (surprisingly) you can provide a non-canonical address 0x00008123DEADBEEF and, instead of try_new failing, you get the VirtAddr 0xFFFF8123DEADBEEF. As the try_new implementation is used throughout VirtAddr's methods, this means you get weird behavior like VirtAddr::new(addr).as_u64() == addr and VirtAddr::from_ptr(ptr).as_ptr() == ptr not necessarily being true, which is quite confusing.
It's especially confusing if you're working on a 5-level paging system where the virtual address space now has 57 bits. In that case, 0x0008123DEADBEEF is a canonical virtual address. I would either expect VirtAddr::try_new to work in this case (returning the passed in address) or fail (returning Err, as this library doesn't have to support 5-level paging). What I wouldn't want is for the virtual address to be silently modified.
Issues related to this have come up in #298. One of the consequences of the current implementation is that adding an u64 to a VirtAddr can "jump" the gap between the lower and upper half of the virtual address space. For example:
let x = VirtAddr::new(0x0000_7FFF_FFFF_FFFF);
let y = x + 5u64;
assert_eq!(y, VirtAddr::new(0xFFFF_8000_0000_0004));
assert_eq!(y - x, 0xFFFF_0000_0000_0005);
assert_ne!((x + 5u64) - x, 5u64);
// But subtraction doesn't "jump" the gap
let _ = y - 5u64; // This panics

which seems very unintuitive.
I would propose the following breaking change: VirtAddr::try_new and VirtAddr::new only succeed if the provided address is canonical and fail otherwise. This removes an unexpected foot-gun and simplifies the implementation.

@phil-opp would you be OK with this breaking change for 0.15 ?

A fully agree that this behavior wasn't a good idea. Many people treat the lower and upper half as separate address spaces (e.g. user and kernel space) so that the boundary should not be crossing silently. I agree with your point about 5-level paging too.
So yes, I think we should make that breaking change. I normally try to avoid any breaking change that silently changes the runtime behavior, but in this case I don't see a better migration path. At least it only changes some behavior into errors, so all users that relied on the old behavior should notice the change at some point.
(There might be users that want to treat the virtual address space as one contiguous address space and want to keep the current gap jump behavior. In that case, we could add some separate jumping_add methods that expose the previous behavior. But let's wait if there is any interest in this at all.)

(There might be users that want to treat the virtual address space as one contiguous address space and want to keep the current gap jump behavior. In that case, we could add some separate jumping_add methods that expose the previous behavior. But let's wait if there is any interest in this at all.)

Sounds reasonable to me.

I just left a comment in #293 that is related to this: https://github.com/rust-osdev/x86_64/issues/293#issuecomment-903260820


Elastichsearch stateful sets and Readme related changes

Highlight of changes

Remove es-master PV during teardown to avoid orphaned disks left behind
Provision more CPU's for ES cluster. The original n1-standard-2 leads to failure to provision the 3rd data pod due to resource constraints and anti-affinity.
README.md, where software requirements have been expanded and deprecated instructions are removed
Rename some scripts to align with the README.md instructions.

Note

I have moved the regions to us-central1 to work around issues in us-west1. Happy to revert if us-west1 is considered optimal for demo
Bazel 0.20.0 is the last compatible version to existing code due to breaking changes in 0.21.0 onwards. - If Bazel upgrade is desired, I would submit another PR dedicated to Bazel upgrade.

/test this please

/lgtm
/approve

/test this please

/retest this please

/ok to test

/retest this please

Please test this

/test this please

/retest this please

/test this please

/test this please

/retest this please

/retest this please

Need to make a number of changes to satisfy requirement of CI pipeline, resulting in Bazel partial upgrade


⚠ Jenkins Plugins Artifactory has degraded performance

In 4cbeb08, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 1317 ms

Resolved: Jenkins Plugins Artifactory performance has improved in 4ddb033 after 20 minutes.


Update http4s-blaze-server, http4s-circe, ... to 0.21.21

Updates

org.http4s:http4s-blaze-server
org.http4s:http4s-circe
org.http4s:http4s-dsl

from 0.21.16 to 0.21.21.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.http4s" } ]

labels: library-update, semver-patch

Superseded by #240.


feat: Better large output display in datafusion-cli with --maxrows option

Which issue does this PR close?

NA
Rationale for this change
If a query outputs a large number of lines, currently datafusion-cli will display them all and flood the terminal.
This PR added a --maxrows option to limit max number of rows for output display.
--maxrows <MAXROWS>
            The max number of rows to display for 'Table' format
            [default: 40] [possible values: numbers(0/10/...), inf(no limit)]

arrow-datafusion/datafusion-cli|cli-large-output🌝| >>> cargo run --release -- --maxrows 5
    Finished release [optimized] target(s) in 0.30s
     Running `target/release/datafusion-cli --maxrows 5`
DataFusion CLI v31.0.0
❯ CREATE EXTERNAL TABLE lineitem STORED AS PARQUET LOCATION '/Users/yongting/Desktop/code/my_datafusion/arrow-datafusion/benchmarks/data/tpch_sf10/lineitem/part-0.parquet';
0 rows in set. Query took 0.041 seconds.

❯ select l_orderkey, l_partkey from lineitem;
+------------+-----------+
| l_orderkey | l_partkey |
+------------+-----------+
| 1          | 1551894   |
| 1          | 673091    |
| 1          | 636998    |
| 1          | 21315     |
| 1          | 240267    |
| .                      |
| .                      |
| .                      |
+------------+-----------+
59986052 rows in set (5 shown). Query took 2.451 seconds.

What changes are included in this PR?

Change elapsed time measurement in CLI to (query start -> all result ready in memory in [RecordBatch]), before it also counts the time for formatting and printing the results.
Add --maxrows option, now only Table CLI display format is supported.

Are these changes tested?
Unit tests

Are there any user-facing changes?
No

I think we could encapsulate the code a bit and make a MaxRows type structure like this that would make parsing a little less awkward:

Thank you for the suggestions
Besides enum MaxRows for cleaner implementation, I also let explain/analyze/describe ignore --maxrows option


[Bug]:

What happened?
I am getting 404 errors on the small screen on the document page.[GSSoS 2023]
Add screenshots

What browsers are you seeing the problem on?
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

duplicate of https://github.com/priyankarpal/ProjectsHut/issues/484
also don't do spam


DevExpress 14.2.3

Devexpress 14.2 was released. Any chance you could provide the nuspec files for that as well?
(or maybe just put up the tool you use somewhere..)

Hi @mterwoord, I've added the nuspec files for DevExpress v14.2.3 and v14.2.4.
Let me know if you run into any issues.

Cool. I didn't even remember this project, until you fixed this issue. At work, I already generated them myself.. Sorry for the hassle..


Security Patch

Updated several dependencies

Hey man I'd really appreciate it if you'd update the program. Currently it's using unsupported packages.


8-bit quantized models for the hand tracking

Please make sure that this is a feature request.
System information (Please provide as much relevant information as possible)

MediaPipe Solution (you are using): Hand Tracking (Palm detection, Hand Landmark)
Programming language : C++/Python/Android Java

I think MediaPipe hand tracking is a highly efficient ML solution that runs in real-time.
Becasue the hand tracking is the 32-bit floating type ML model,
I have to use the GPU delegate supporting the 32-bit floating computation to accelerate the hand tracking on edge device.
(I know that there are only 32-bit floating point models for MediaPipe ML solutions except for object detection and face detection)
However, GPU is very expensive and the edge devices have limited resource and computational power.
So we need to use the NPU delegate for the edge devices, and almost of NPU (ex. Edge TPU and Hexagon NPU) require a fully 8-bit quantized model as the input.
Do you have a plan to release the fully 8-bit quantized models for hand tracking (palm and hand landmark)?
Thank you.

@freesokim hello sir
I have same demand with you, i remember you mentioned the
PINTO_model_zoo provided the quantized model, is it a fully int8 model ? thanks !

Hi @Stephenfang51 .
We have similar issue ,could you please check this issue.

@Stephenfang51
Hi, Sorry for late reply.
I think PINTO_model_zoo provide the 8-bit quantized models, but I have not tried them yet.
My question is google have any plan to release the official 8-bit quantized models for the hand tracking.
Thanks.

@Stephenfang51
Do you mean that google don't have any release plan for quantized model?

I also have this question. Is google have any plan to release the official 8-bit quantized models for the hand tracking?


Is there a plan to implement provider for Yahoo

Hi,
I have been using your API to integrate with google, facebook, twitter and windows live. I also need to integrate with yahoo but I found no provider for yahoo neither in core project nor in extra providers project. Is there a plan to roll out a provider for yahoo?
Regards
Adeel

No plan from me and i'm assuming no plan from Phillip.
We will accept a PR for it, though.
GL :+1:

I didn't know Yahoo was still used by people, thought people used gmail to login to yahoo.

NP, I will try to implement it and If I succeeded, I will create a pull
request on your repo. I think, I should put it in ExtraProviders project,
right?
On 22 June 2016 at 17:51, Phillip Haydon<EMAIL_ADDRESS>wrote:

I didn't know Yahoo was still used by people, thought people used gmail to
login to yahoo.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/SimpleAuthentication/SimpleAuthentication/issues/212#issuecomment-227732961,
or mute the thread
https://github.com/notifications/unsubscribe/ABBKjLtaLTKSe5_K-ur4CD9fSnKDPT6xks5qOS_DgaJpZM4I7mVT
.

--
Regards
Muhammad Adeel Zahid

Yep - that's correct. GL :+1:

Hi SimpleAuthentication/SimpleAuthentication
You have been invited to join the Cook at Home https://u3431732.ct.sendgrid.net/wf/click?upn=QgBgXNb9qe6bSBTooCR18ecl8fVTnBcGrCB-2BcpvqGpx9BZijN5ezGCHSiX1BlHqX_s5UH8bhnBaopYjthcNSRccgGEPCgo2wwm-2FsOE4oLDazYxlfmDhl1YobY9pwG6aclcFKUobUJJCG7pz-2Ft-2BNbYNqZI56NgE660HxAarqFgpK4ug8r97tNfmtCT0w19XVKgHMmgH13G5qna9aoxuE-2BlbnGHfkJbWPBzqNSIGhp16JQBi4fYcE1xBySPZrTqj-2F-2F6PfaOZBtWbVDPQpC96VBWRkaq4nH4k-2F8OrHtsalX0fENLeCtu6d9TYC-2Bcw8xbbjyYWRfcP9T-2B4za9olQQp-2BBCH17tg4T3NNxUlMSFRCmW0wf-2BBHAWKDfL-2BnYevhdZxRON1CnI4T4AtNU4q4V-2Ba43N3iWDenfylxRnoWR4Lvz8zC4XYDhhxS3-2Bfxe9GfEF-2BD9H0CsuOH1KnMNcsALcl8SnMg-3D-3D
Regards
Cook at Home Team

Hi SimpleAuthentication/SimpleAuthentication

You have been invited to join the Cook at Home.

Regards
Cook at Home Team


Added JUnit tests for finding activities command.

Collaborators: Zi Foong

Codecov Report

Merging #86 (346dc81) into master (915908f) will increase coverage by 1.75%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master      #86      +/-   ##
============================================
+ Coverage     72.59%   74.35%   +1.75%
- Complexity      467      483      +16
============================================
  Files            81       81
  Lines          1427     1427
  Branches        162      162
============================================
+ Hits           1036     1061      +25
+ Misses          345      320      -25
  Partials         46       46

Impacted Files
Coverage Δ

...du/address/logic/commands/FindActivityCommand.java
100.00% <0.00%> (+100.00%)
:arrow_up:

...ddress/logic/parser/FindActivityCommandParser.java
100.00% <0.00%> (+100.00%)
:arrow_up:

...el/activity/ActivityContainsKeywordsPredicate.java
100.00% <0.00%> (+100.00%)
:arrow_up:

Continue to review full report at Codecov.

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


Add a workaround for hseeberger/scala-sbt#3 to build inside a docker container.

Add a workaround for hseeberger/scala-sbt#3 to build inside a docker container.
Otherwise results in the following error if building inside docker on aufs:
[info] Compiling 123 Scala sources and 2 Java sources to /root/kafka-manager/target/scala-2.11/classes...
[error] File name too long
[error] one error found

CLA is valid!


set env vars explicitly to fix circle ci check

I don't have any experience with Circle CI, but the point is that it should have the same env vars set as in the check above.

thanks @sdebruyn!


Ability to Choose how Torrents will Display

Feature request
Kindly add the ability to display Parsed Data only. The most helpful data to display would be:
(Quality, Resolution, Codec, Audio info, HDR info, Subtle info, File Size. )
Looking forward to a favorable response.

No Plans for such a feature.


Garbled line

In the first paragraph of the doc there appears to be a garbled line with "[run" and  "(**":
You can instead simply [run metamath-lamp directly using your web browser](**main Metamath-lamp web site!

All fixed! Please let us know what else needs fixing or improving. Pull requests are welcome too :-).


Fix REST API schema errors

Description:
Checking the publisher REST API definition, observed a couple of schema validation errors.

Check other REST APIs too and fix all.
There are couple of warnings with unused models as well. Need to remove all unused ones.
eg:
ThreatProtectionPolicyList
EndpointList

Fixed in the latest version, hence closing


[WIP] feat(storage): add support for eip 7702 bytecode

PR addressing https://github.com/risechain/pevm/issues/317, working towards https://github.com/risechain/pevm/issues/302

Dam, the new bytecodes file has balooned in size due to the new enum field bringing the size to ~ 53mb and GH is throwing warnings 😭 .

Hey @hai-rise, thanks for the feedback 🙏 . I've added tests and addressed the above comments. LMK if you'd like me to add tests converting back to the revm types.

@hai-rise, thank you for the feedback. Have refactored with the suggestion above 🙏


Update Types doc for search

Update this doc to make sure all types included in this doc return results when searched:
https://docs.influxdata.com/influxdb/cloud/reference/flux/language/types/#time-types

This will likely be resolved when the flux-restructure branch merges.


Have any negative prompt template ?

It will be nice

This would be very nice too.
If anyone is home?

@Dalabad any update ?

+1

Hey guys, negative prompts are - in my experience - very specific for an image. You start with a prompt and once you found a seed that you like, you fix that seed and you can improve on that specific case by adding positive / negative prompts.
There are the obvious ones like ugly, malformed, text, copyright, signature, ..., but I would not suggest using them on all images unless you think they are necessary. If you guys have experiences where some negative prompts always make sense, let me know :)

Got it !


Missing Value 0 in raw

Zero values do not show up in raw array. In show, they are correctly appended. See example:
  "raw": [
    1425,
    338,
    9,
    6,
    45,
    44,
    38,
    402,
    31
  ],
  "show": [
    "TCP Segment Len: 0",
    "TCP Segment Len: 0",
    "TCP Segment Len: 1425",
    "TCP Segment Len: 338",
    "TCP Segment Len: 9",
    "TCP Segment Len: 0",
    "TCP Segment Len: 6",
    "TCP Segment Len: 45",
    "TCP Segment Len: 44",
    "TCP Segment Len: 38",
    "TCP Segment Len: 402",
    "TCP Segment Len: 0",
    "TCP Segment Len: 31",
    "TCP Segment Len: 0",
    "TCP Segment Len: 0"

the Autovifification.clean_empty() method is not doing what it is supposed to do
In [1]: import pdml2flow

In [2]: a = pdml2flow.autovivification.AutoVivification()

In [3]: a[0] = 0

In [4]: a[1] = 0

In [5]: a[3] = [0,1,2,3]

In [6]: a
Out[6]: {0: 0, 1: 0, 3: [0, 1, 2, 3]}

In [7]: a.clean_empty()
Out[7]: {3: [1, 2, 3]}

added some unit tests , this should no longer happen


Example cucumber test

We'll need to update this once #1177 is merged, unfortunately.

Updated to gradle

Thanks @stsefanenko! Sorry for a lack of attention on this one. I looks good, I will have a final look and merge after CI reports green status 👍

@stsefanenko merged! 🎉
Thanks a lot, good job! 👍

Released in https://github.com/testcontainers/testcontainers-java/releases/tag/1.10.7!


[Designer/templating] Fixes + add toString

Related Issue
Fixes https://github.com/MicrosoftDocs/AdaptiveCards/issues/251
Description

Actually create a copy of the expression nodes which were previously overwritten causing the same data object to be reused for all items in an array
Introduce toString to support basic explicit conversion of numbers into string

How Verified
Verified in:

adaptivecards-designer-app
Web site running locally

How to test
Card payload:
{
    "$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
    "type": "AdaptiveCard",
    "version": "1.0",
    "body": [
        {
            "type": "Container",
            "items": [
                {
                    "type": "ColumnSet",
                    "columns": [
                        {
                            "type": "Column",
                            "width": "auto",
                            "items": [
                                {
                                    "type": "TextBlock",
                                    "text": "{if(changePriceRatio >= 0, '▲', '▼')}",
                                    "color": "{if(changePriceRatio >= 0, 'good', 'attention')}"
                                }
                            ]
                        },
                        {
                            "type": "Column",
                            "width": "stretch",
                            "items": [
                                {
                                    "type": "TextBlock",
                                    "text": "{name}"
                                }
                            ]
                        },
                        {
                            "type": "Column",
                            "width": "stretch",
                            "items": [
                                {
                                    "type": "TextBlock",
                                    "text": "{toString(lastPrice)}",
                                    "horizontalAlignment": "Center"
                                }
                            ],
                            "horizontalAlignment": "Center"
                        },
                        {
                            "type": "Column",
                            "width": "auto",
                            "items": [
                                {
                                    "type": "TextBlock",
                                    "text": "{changePriceRatio}%",
                                    "color": "{if(changePriceRatio >= 0, 'good', 'attention')}"
                                }
                            ],
                            "horizontalAlignment": "Right"
                        }
                    ]
                }
            ],
            "$data": "{$root}"
        }
    ]
}

Data payload:
[
    {
        "name": "Object-1",
        "lastPrice": 1.10762,
        "changePriceRatio": -0.17
    },
    {
        "name": "Object-2",
        "lastPrice": 1578.205,
        "changePriceRatio": -0.68
    },
    {
        "name": "Object-3",
        "lastPrice": 51.475,
        "changePriceRatio": -0.23
    },
    {
        "name": "Object-4",
        "lastPrice": 28324,
        "changePriceRatio": 0.35
    },
    {
        "name": "Object-5",
        "lastPrice": 9338.87,
        "changePriceRatio": -1.04
    }
]

Card should render as follows in the designer in "Preview mode":

Microsoft Reviewers: Open in CodeFlow

@dclaux, @matthidinger, guys, question: how/when are we expecting to spin up a package update for this and also should we update the version up on vnext.adaptivecards.io for bug bash purposes ?  Also David, can you actually include the sample update that we can use both for the bash as well as to update our documentation site if needed?

@shalinijoshi19 I'd love to try and get an update out tomorrow if the fix is confirmed working in the site. If not we might need a few more days into next week, but we should definitely sync on the overall status of the latest site deployments and close those ends. The Project board has the 4 items I'm hoping to close for the next publish


App crashes when uploading avatar

Every time I try to upload avatar for a user, node crashes with the following output:
0 info it worked if it ends with ok
1 verbose cli [ '/usr/local/bin/node',
1 verbose cli   '/Users/username/.npm-global/bin/npm',
1 verbose cli   'start' ]
2 info using<EMAIL_ADDRESS>3 info using<EMAIL_ADDRESS>4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>6 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>7 verbose lifecycle<EMAIL_ADDRESS>unsafe-perm in lifecycle true
8 verbose lifecycle<EMAIL_ADDRESS>PATH: /Users/username/.npm-global/lib/node_modules/npm/bin/node-gyp-bin:/Users/username/Documents/Programming/Webs.nosync/Lolz/rekvisits/spruce/node_modules/.bin:/Users/username/.npm-global/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/go/bin:/usr/local/MacGPG2/bin:/usr/local/share/dotnet:/opt/X11/bin:~/.dotnet/tools:/Library/Frameworks/Mono.framework/Versions/Current/Commands:/Users/username/.npm-global/bin:/Library/Frameworks/Mono.framework/Versions/Current/Commands/usr/local/mongodb/bin:/usr/local/mongodb/bin
9 verbose lifecycle<EMAIL_ADDRESS>CWD: /Users/username/Documents/Programming/Webs.nosync/Lolz/rekvisits/spruce
10 silly lifecycle<EMAIL_ADDRESS>Args: [ '-c', 'node ./bin/www' ]
11 silly lifecycle<EMAIL_ADDRESS>Returned: code: 1  signal: null
12 info lifecycle<EMAIL_ADDRESS>Failed to exec start script
13 verbose stack Error<EMAIL_ADDRESS>start: `node ./bin/www`
13 verbose stack Exit status 1
13 verbose stack     at EventEmitter.<anonymous> (/Users/username/.npm-global/lib/node_modules/npm/lib/utils/lifecycle.js:289:16)
13 verbose stack     at EventEmitter.emit (events.js:182:13)
13 verbose stack     at ChildProcess.<anonymous> (/Users/username/.npm-global/lib/node_modules/npm/lib/utils/spawn.js:40:14)
13 verbose stack     at ChildProcess.emit (events.js:182:13)
13 verbose stack     at maybeClose (internal/child_process.js:962:16)
13 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:251:5)
14 verbose pkgid<EMAIL_ADDRESS>15 verbose cwd /Users/username/Documents/Programming/Webs.nosync/Lolz/rekvisits/spruce
16 verbose Darwin 18.6.0
17 verbose argv "/usr/local/bin/node" "/Users/username/.npm-global/bin/npm" "start"
18 verbose node v10.10.0
19 verbose npm  v5.3.0
20 error code ELIFECYCLE
21 error errno 1
22 error<EMAIL_ADDRESS>start: `node ./bin/www`
22 error Exit status 1
23 error Failed at the<EMAIL_ADDRESS>start script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]

@matronator
Thanks for creating this issue.
You need to create a new folder named profile_pictures under the public/images directory.
It was not pushed at it was in my .gitignore.
Thanks

Oh, I see, sorry my bad! Thank you! :)
BTW, really cool project, very easy to install and get it up and running in no time (compared to other node/npm modules/packages) and easily customizable/extendible. Loving it so far, keep up the good work! 😉

@matronator
Thanks! Feel free to create a PR!
Happy Coding!


Postconditions involving Heap

There is essentially a bug related to post-conditions and the heap.  The problem is that we have two names for the heap: #HEAP and ##HEAP, with the former referring to the original heap and the latter referring to the new heap.  The key issue is that, when generating preconditions we need to use #HEAP and when generating postconditions we need to use ##HEAP.
This could actually be fixed on the Whiley side by introducing a concept of old versus new in postconditions.  For example, 'p could be similar to *p but refer to the value in the original heap.  What about p->f ... how to we replace that?  'p->f has the same number of characters as ('p).f

Ok, this should be an RFC.


School Employee Community Type

Create a new community type in Doorway for "School Employee"
AC:

DPP user can create select a "School Employee" community type on a listing
If it's selected, on the public site, a "School Employee" community type shows as a tag on the listing picture
If it's selected, on the public site, a "School Employee" community type tag translates correctly
If it's selected, on the public site, a "School Employee" community type shows as detail page and translates correctly

check what this looks like w other languages
YL made a script, minor updates for translations

@sarahlazarich I ran this through google translations. Are any of these too long?

Spanish: "Empleado de la escuela"
Vietnamese: "Nhân viên trường học"
Chinese: "学校员工"
Filipino: "empleyado ng paaralan"

@sarahlazarich this has been merged to core and the script run in the dev environment. Translations still need to be confirmed so can you verify those in your QAing?
QA notes:

https://bloom.exygy.dev/listings has the new reserved type on Valley Heights Senior Community property
You should also be able to add it to new listings on https://partners.bloom.exygy.dev/

This has been run in production and School Employee community type is now there


Fix DatetimeRange timestamp iteration

Problem: DatetimeRange.iter_timestamps() does not return the correct time series when the starting timestamp is tz-aware and in a timezone with DST.
Currently the function produces the following at spring-forward:
                     timestamp
1656 2018-03-11 00:00:00-07:00
1657 2018-03-11 01:00:00-07:00
1658 2018-03-11 03:00:00-06:00
1659 2018-03-11 03:00:00-06:00

It needs to be:
                     timestamp
1656 2018-03-11 00:00:00-07:00
1657 2018-03-11 01:00:00-07:00
1658 2018-03-11 03:00:00-06:00
1659 2018-03-11 04:00:00-06:00

Solution: Advance timestamp in standard timezone (e.g., UTC) and convert back to input timezone before yielding.
Also fixed DatetimeRange.list_timestamps_from_dataframe() to return unique timestamps only. Do we need sort it?
Did not fix relevant pytests

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 94.24%. Comparing base (ac69a9e) to head (d55ab1e).

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #17      +/-   ##
==========================================
+ Coverage   94.20%   94.24%   +0.03%
==========================================
  Files          18       18
  Lines         777      782       +5
==========================================
+ Hits          732      737       +5
  Misses         45       45

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


nixos/tests/nginx: fix etag test flakiness

Description of changes
Out of 25 test runs:

Before: 18 successes, 7 failures
After: 25 successes, 0 failures

The main fix is waiting for multi-user.target before any switch-to-configuration happens (not exactly sure why or whether that's a wanted behavior from switch-to-configuration, I have not dug that far). The wait_for_nginx_on_port change is something I did along my debugging journey and I don't see a reason to revert it back, it should be objectively better.
ZHF: #230712
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

@ofborg test nginx


YAML front matter - preview / view

Hi,
In view mode the icon in fields cannot see

Fülike

I presume this is related to Obsidian's core management of yaml block. There's pretty much nothing I can do about it sorry

This has been fixed with the recent addidtion of Properties in obsidian


Support for multiple cameras at once

I am trying to initialize multiple cameras at once just like a bothie feature in nokia phones,

As of now only one camera can be initialized at a time and other camera gets disposed off automatically, And also when I print the available cameras length it always prints 2 even though my device has three cameras in the back and a camera in the front, Is there any specific reason to that?.
This is how one of the camera gets disabled (Green Area) on initializing multiple cameras at once.The Sample image shows a screen with two halves the upper part for the primary camera (camera[0]) and lower for the secondary camera (camera[1] which is disposed)

I searched about using the multiple camera on android and found that the MultiCamera Api is available for API level 29 and above

I searched about using the multiple camera on android and found that the MultiCamera Api is available for API level 29 and above

@maheshmnj hey any update on this? thx

@jtkeyva nothing yet its just a feature request so this is considered as low priority by but you can always add a 👍🏻  to increase its priority.

@maheshmnj in addition to the Android document you shared, here is the iOS counter part. It seems like iOS has this functionality since 2019. I really hope this feature request can have a higher priority since the need for this type of functionality has increased a lot lately.
https://www.wwdcnotes.com/notes/wwdc19/249/

Bumping this as this would be a great feature! Even if it only works on a few devices at the beginning

Hello all, we are currently working on this feature on CamerAwesome plugin.
Feel free to help us or testing it 👍

I am also looking forward to this feature of being able to take pictures with both Front and Back cameras at the same time. It's extremely needed feature.
Thank you.

Any update?

Following


Change for .erb files

I added the ability to recognize .erb files for rails projects. Used the HTML5 icon and changed the color to  the same color as Ruby. Added corresponding variables in icon-variables.less. Also, modified the icons.less & icon-variable.less files to recognize C# files
Thanks,
Cornell

Closed via https://github.com/wyze/atom-seti-icons/commit/d1f70abce06b5c9e78e5a35d155865936642c2d4 and published in v1.0.0.


feat(v2): add trailingSlash config option

Motivation
Fixes https://github.com/facebook/docusaurus/issues/3372
After analyzing the behavior of multiple static hosting providers (see https://github.com/slorber/trailing-slash-guide), I think we should have a trailingSlash option (like Next.js has)
This is a risky change that can have deep SEO impacts for some sites, so we are keeping a retrocompatible behavior by default.
It would allow 3 values:

true: force a trailing slash to SPA routes + links, output /myPath/index.html
false: remove trailing slashes on SPA routes + links, output /myPath.html
undefined: retrocompatible behavior: leave routes unchanged (often no trailing slash), output /myPath/index.html

If the new behaviors are successful, we should add them to the init template, and deprecate the undefined legacy behavior with a Joi warning, telling the users to be extra careful about the potential SEO impacts.
Have you read the Contributing Guidelines on pull requests?
yes
Test Plan
Tests + deploy previews

I'm implementing a new {trailingSlash: boolean | undefined} config.

undefined: it keeps the existing retro-compatible behavior (paths not modified), and output /path/index.html
false: remove a potential trailing slash on routes, links, canonical URLs, and output /path.html
true: force a trailing slash on routes, links, canonical URLs, and output /path/index.html

Refer to https://github.com/slorber/trailing-slash-guide for how the files will be served by your host.
I've created 3 deployments to test this feature:

trailingSlash undefined: https://docusaurus-trailing-slash-undefined.netlify.app/ (Netlify pretty URLs off)
trailingSlash false: https://docusaurus-trailing-slash-false.netlify.app/ (Netlify pretty URLs on)
trailingSlash true: https://docusaurus-trailing-slash-true.netlify.app/ (Netlify pretty URLs on)

Note: using true/false instead of undefined allows to use Netlify with pretty URLs on without having any annoying redirection, but it's not the case for the undefined behavior that will keep redirecting with pretty URLs on (default behavior). Had to disable this.
PLEASE: help me review those deployments and let me know if you see any unwanted side-effects: now is a better time to complain than after merging the PR :)
Note: this feature is generic and in core, to avoid the need to have each plugin implement custom trailingSlash logic. In some cases it might require some plugin tweaks but it should work fine in a generic way for plugin authors in most cases.

trailingSlash false: docusaurus-trailing-slash-false.netlify.app (Netlify pretty URLs on)

@slorber The docs page is missing the navigation on the left. I can't tell if this is intentional or a bug introduced in this PR.
See page https://docusaurus-trailing-slash-false.netlify.app/docs.

trailingSlash true: docusaurus-trailing-slash-true.netlify.app (Netlify pretty URLs on)

This has the right behavior for me based on my requirements in https://github.com/facebook/docusaurus/issues/3372#issuecomment-856104497.
I see that the URLs in the pages, in the canonical meta tag, the sitemap, and the browser bar are all matching and contain trailing slashes. And Netlify's Pretty URL redirects users correctly.
I will now wait for the canary build to test this on my site.

@slorber The docs page is missing the navigation on the left. I can't tell if this is intentional or a bug introduced in this PR.

Thanks, definitively not intentional but understand why it happens, due to using slug: "/". Other docs work fine see https://docusaurus-trailing-slash-false.netlify.app/docs/installation
Will fix this asap.

I wasn't able to get my site working with the current canary release. I get build errors and I'm not sure what the cause is.

Yarn install output
PS D:\Repositories\Documentation\apimatic-docs> yarn upgrade @docusaurus/core@canary  @docusaurus/preset-classic@canary
yarn upgrade v1.22.10
[1/4] Resolving packages...
[2/4] Fetching packages...
info<EMAIL_ADDRESS>The platform "win32" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
info<EMAIL_ADDRESS>The platform "win32" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
[3/4] Linking dependencies...
warning "@docusaurus/preset-classic > @docusaurus/theme-search-algolia ><EMAIL_ADDRESS>has unmet peer dependency "@types/react@>= 16.8.0 < 18.0.0".
y "<EMAIL_ADDRESS>[4/4] Rebuilding all packages...
success Saved lockfile.
success Saved 8 new dependencies.
info Direct dependencies
└─<EMAIL_ADDRESS>info All dependencies
├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>└─<EMAIL_ADDRESS>Done in 61.44s.

Build output (has error)
Unable to build website for locale en.
RangeError: Invalid time value
    at D:\Repositories\Documentation\apimatic-docs\node_modules\@docusaurus\plugin-content-blog\lib\blogUtils.js:118:12
    at async Promise.all (index 16)
    at async Object.generateBlogPosts (D:\Repositories\Documentation\apimatic-docs\node_modules\@docusaurus\plugin-content-blog\lib\blogUtils.js:84:5)
    at async Object.loadContent (D:\Repositories\Documentation\apimatic-docs\node_modules\@docusaurus\plugin-content-blog\lib\index.js:59:25)
    at async D:\Repositories\Documentation\apimatic-docs\node_modules\@docusaurus\core\lib\server\plugins\index.js:54:46
    at async Promise.all (index 6)
    at async Object.loadPlugins (D:\Repositories\Documentation\apimatic-docs\node_modules\@docusaurus\core\lib\server\plugins\index.js:53:34)
    at async Object.load (D:\Repositories\Documentation\apimatic-docs\node_modules\@docusaurus\core\lib\server\index.js:102:82)
    at async buildLocale (D:\Repositories\Documentation\apimatic-docs\node_modules\@docusaurus\core\lib\commands\build.js:80:19)
    at async tryToBuildLocale (D:\Repositories\Documentation\apimatic-docs\node_modules\@docusaurus\core\lib\commands\build.js:32:20)
    at async Object.mapAsyncSequencial (D:\Repositories\Documentation\apimatic-docs\node_modules\@docusaurus\utils\lib\index.js:328:24)
    at async build (D:\Repositories\Documentation\apimatic-docs\node_modules\@docusaurus\core\lib\commands\build.js:68:25)
error Command failed with exit code 1.

Let me know if this is something that will go away with the next beta release. If this feels like a bug, let me know how I can debug it to help avoid this going to release.

@thehappybug this does not look related to trailing slashes. From which version are you upgrading? May be related to refactor in #4759
It looks like we can't compute a proper date for some of your blog posts using this code:
      date = date ?? (await fs.stat(source)).birthtime;
      const formattedDate = new Intl.DateTimeFormat(i18n.currentLocale, {
        day: 'numeric',
        month: 'long',
        year: 'numeric',
      }).format(date);

Can you give me an idea of your blog post filenames + their frontmatter please? Do you see any post with a potentially wrong date filename pattern or frontmatter?

Hello, is this update included in the latest public builds?

@Labirintami It is only available on canary right now.
See: https://github.com/facebook/docusaurus/issues/3372#issuecomment-857931379

will be in beta.1, probably tomorrow
I've written how to use a Canary release here: https://docusaurus.io/community/canary


Node 8 image

Can we make a branch for node 8, this LTS is still heavily supported and is quite widespread in terms of use due to AWS Lambda

@nk2580 ready:

https://github.com/tarampampam/node-docker/tree/image-9-alpine tarampampam/node:8-alpine
https://github.com/tarampampam/node-docker/tree/image-8-alpine tarampampam/node:9-alpine

This images will be time-to-time rebuilded, so, any insalled software shoul have actial versions.


clean up

@squillace

Hi @Rick-Anderson, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

It looks like you're a Microsoft contributor (Rick Anderson). If you're full-time, we DON'T require a Contribution License Agreement. If you are a vendor, please DO sign the electronic Contribution License Agreement. It will take 2 minutes and there's no faxing! https://cla.microsoft.com.

TTYL, MSBOT;

@Rick-Anderson : Thanks for your contribution to the Azure documentation! The author, @azdocprs, has been notified to review your proposed change.

@squillace Hi Ralph Please review this contribution. Thanks.

#sign-off. @Rick-Anderson sorry my man! lost in the weeds. Great help.


Placeholder property don't consider on load

Placeholder is not considered at first entry. Thereafter, it works perfectly fine.
<tag-input [ngModel]="[]" [onlyFromAutocomplete]="true" theme='dark' [ngModelOptions]="{standalone: true}" [onlyFromAutocomplete]="true" [placeholder]="'Add Items'">                       <tag-input-dropdown [showDropdownIfEmpty]="true" [autocompleteItems]="capabilities">                       </tag-input-dropdown>                     </tag-input>
Initially, taking default placeholder "Enter a new tag"

Later, considering the custom placeholder.

Thanks,
Aniket

Change placeholder to secondaryPlaceholder. I got confused the first time too.

Thanks. But this module have many issues in devices.


[Task]: Add layout to MainContainer.

Update server implementation to add layout prop for MainContainer upon creating a new app on Anvil appPositioningType.

Also take a look if we can rename appPositioningType to LayoutSystemType

@aswathkk There is a separate task for that.

The dsl key is a JSON Object in the backend codebase, which means that we can add any more keys to this object.
The client can pass the new layout key in the api request and the backend already supports that today.
This is a client-side-only task, which requires no BE bandwidth.
cc: @somangshu @prsidhu @marks0351

DSL Migrations should not run for Anvil applications
Properties like leftColumn, rightColumn, parentRowSpace, etc, should not be added to the DSL in any flow
DSL migrations in Anvil is technically possible (avoidable but still possible), so we need a way to migrate only Anvil DSLs.
Migrations assume a hierarchy that is widget -> children[], this may change in Anvil, so Migrations are even more not feasible.


Support of polygons with interior holes

Request for support of polygons with interior holes. I think the core of the code will work as is if there is some way to represent them.
For now my hack is this: when creating the list of polygons for the graph creation, specify the exterior polygon ring first, then put a blank polygon (empty list) in front of every matching interior ring. Then in the init method for the graph I catch those empty lists and rewind the pid by one. The resulting behavior for the visibility graph seems fine so far.

I'm very curious about what you are using the package for, if you would be open to share, send me a mail on<EMAIL_ADDRESS>


Move Purchasing Error to Purchase Template

When the moderators were refactored to be a generic component used in both the purchase and settings/store views, a purchase-specific error was left in js/templates/components/moderators.html
That should be removed, and the error handled in the purchase view/template, triggered by the moderator component.

This was refactored.


ci: Update VERSION file to master for Hanoi development

Revert VERSION to 'master' so that Hanoi development can be resumed.
Hold until docker compose files and snaps are validated.
Related PRs:
https://github.com/edgexfoundry/cd-management/pull/44
https://github.com/edgexfoundry/developer-scripts/pull/292
Signed-off-by: Lisa Rashidi-Ranjbar<EMAIL_ADDRESS>PR Checklist
Please check if your PR fulfills the following requirements:

[X] The commit subject follows the Conventional Commits spec
[X] The commit message follows the EdgeX Contributor Guide
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)
[ ] make test has completed successfully

PR Type
What kind of change does this PR introduce?

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

Codecov Report

Merging #2588 into master will decrease coverage by 0.23%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #2588      +/-   ##
==========================================
- Coverage   39.05%   38.81%   -0.24%
==========================================
  Files         150      145       -5
  Lines       13123    12722     -401
==========================================
- Hits         5125     4938     -187
+ Misses       7691     7510     -181
+ Partials      307      274      -33

Impacted Files
Coverage Δ

internal/security/secretstore/init.go
3.92% <0.00%> (-3.27%)
:arrow_down:

internal/security/pipedhexreader/mocks/mock.go

internal/security/kdf/mocks/mock.go

internal/security/pipedhexreader/pipedhexreader.go

internal/security/secretstore/vmkencryption.go

internal/security/kdf/methods.go

...adata/operators/device_profile/value_descriptor.go
97.67% <0.00%> (+0.65%)
:arrow_up:

Continue to review full report at Codecov.

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


Implement BCV Control Design using Shoelace

User Story
As a developer, I want to choose a UI toolkit to use forever so we can standardize designs with a system so that we can implement UI designs as efficiently as possible.
As a translator or advisor, I want to navigate to different texts and to different books, chapters, and verses within a text. I want to be able to sync navigation across multiple views and tools.
Description
UI Toolkits Bakeoff Contestant # 2, Shoelace. Implement the BCV control design in the toolkit, doing all you reasonably can to match the design, particularly in appearance so we can get a good feel of how easy the components are to customize.

UI Toolkit Research background doc
Figma Design
UX created sandbox

Code Style Thoughts from Sebastian

Create little components (e.g. for the book name list entry)

Results
Note your thoughts about the usability of the toolkit in Toolkit Evaluation
Be ready to demo BCV at the sprint demo planning meeting.

reference to the first task

https://github.com/paranext/paranext-core/issues/777


chore: update go-database-reconciler to 1.14.7

This version has two fixes.

auto fields are sent as nil to CP
More than one consumer group can
be associated with one consumer.

This is just a bump PR.
I will add more details about the changes in the changelog when I prep the release PR post merging this.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 22.42%. Comparing base (18831e9) to head (8aa2b04).

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1394      +/-   ##
==========================================
+ Coverage   22.36%   22.42%   +0.06%
==========================================
  Files          54       54
  Lines        4530     4530
==========================================
+ Hits         1013     1016       +3
+ Misses       3417     3415       -2
+ Partials      100       99       -1

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Make type initialization happen lazily

Motivation
For performance reasons, in production, we remove as much as sorbet-runtime overhead as possible. One of the changes we apply is no-op'ing T annotations such as T.let(x, Type) by monkey patching the T module:
module InlineTypeAssertions
  def let(value, type, checked: true)
    value
  end
end

T.singleton_class.prepend(InlineTypeAssertions)

This effectively negates the overhead of the inline assertion let but the cost of type Type construction is still present.
Here's a very simple example using the patch above:
100_000.times do
  x = T.let([], T::Array[T::Hash[Integer, String]])
end

Profiling this snippet with our InlineTypeAssertions patch shows that while T.let is not doing anything, we still spend a considerable amount of time into initializing Type mostly due to T::Utils.coerce:

This PR proposes to move the type coercion outside of the initializer to let it happen lazily. In a normal execution context, this doesn't modify the behavior at all. The type construction is just moved to the first call involving the type rather than when the type is instantiated. But in a context where inline type assertions are no-op'ed, this drastically simplifies the type initialization and since nothing ever calls inside the type in that case, the lazy construction is never executed, resulting in a considerable speed-up and less pressure on the garbage collector.

There is no extra performance cost for this change but we require an additional instance variable for each type to store the original type passed to the constructor before we lazily coerce it.
Test plan
See included automated tests.

If I understand correctly, for codebases that force all sig blocks eagerly in production during load time, this will mean that many sig-related allocations move from load time to the first request. Does that sound right to you?
Is it possible to build in a mode where the force all sig blocks utility function also forces the evaluation of this lazy computation?

Indeed we are deferring type evaluation from signature evaluation time to the first time the signature is checked. In our case, we eagerly force the signatures evaluation at boot time but also disable any check against the signatures so we never get to the lazy part.
But you're right, we wouldn't want that to be the default behavior for everybody using T::Utils.run_all_sig_blocks.
I added the ability to turn on and off the type construction when calling run_all_sig_blocks with a default to force the type construction eagerly. This brings back the type construction in signatures to boot time and still allow lazy construction for inline annotations.

We have a policy of testing changes to Sorbet against Stripe's codebase before
merging them. I've kicked off a test run for the current PR.  When the build
finishes, I'll share with you whether or how it failed. Thanks!
Stripe employees can see the build results here:
→ https://go/builds/bui_PDXRtz43cYTpMv
→ https://go/builds/bui_PDXRvgN1oYzucf
→ https://go/builds/bui_PDXRvMfCIREXHq

I'm getting a NotImplementedError coming from lib/types/types/base.rb:39.
Can you double check that you've implemented everything and try again?

Passes CI at Stripe, going to merge when Sorbet's CI passes.


Why let the rxjava intrude into the domain module?

The rxjava seemed to make the domain not that clean.

I agree with them. Can CompletableFuture replace rx in this case?

Using RxJava in the domain logic is exactly the opposite of delaying technical decisions and reducing coupling to external frameworks, as C. Martin suggests in his lecture here.


Excluding delegates storages from STRONG_DELEGATE_CHECK

Hi!
It's quite common to have collections of delegates. The collection itself is usually named like  "_delegates_Hash", "_delegates_Storage" or simply "delegates". Obviously, there is common part in all these cases, but currently you're excluding property only if it contains "queue".
I've added a simple exclusion by common part. It solved our warnings and I think for others it'll be quite helpful too.
P.S. I made that pull request to 0.9.5 since it is currently released version and master branch has separate rules file. I can make separate pull request for master with the same simple fix.

Hi, thanks for your pull request. Unfortunately, this check has changed in master. We are working on a DSL for writing linters, and in the latest version this check has already been written in the DSL. If you are interested, you could try to download and build master, and make the pull request on top of it. Thanks.

@dulmarod

By the way, in master the check leaves in infer/lib/linter_rules/linters.al.


Alphabet generalisation

Generalised the theorems in the Theory of Words so that they don't only work for the original binary "a" and "b" alphabet.
They now work for arbitrary alphabets described by the pattern top_letter.
Also wrote python script generating theory files for simple alphabets made up of named letters.

der_l1_l2_phi, der_l1_l2_phi_and and regex_eq_der_diff_l look like
pretty much the same theorem?

der_l1_l2_phi came first and was the main lemma used for regex_eq_der_diff_l (which needs to exist beacuse it's one of the theorems referenced in the proof generation). When generalising the theorem I noticed that der_l1_l2_phi was not general enough so I instead had to prove and use der_l1_l2_phi_and, which is a bit more convoluted.
While we could now prove der_l1_l2_phi from der_l1_l2_phi_and fairly easily, I chose to keep the original proof of der_l1_l2_phi just in case someone ever wants to actually read it to understand how it works (since the proof of der_l1_l2_phi_and is strictly more complex) and because there's virtually no downside to keeping both proofs.
Also I expect der_l1_l2_phi to be quite useful and straightforward in most cases.  der_l1_l2_phi_and exists for degenerate cases like the one I had to deal with.
Also I like the proposal to generalise our theorems to arbitrary contextual implications. I'm not atm convinced that they all can be generalised but it would be nice. However idk if it should necessarely be part of this PR specifically. That's another pretty large piece of work and ti would be useful to ahve this merged in.


Laravel 7 Support

@christofferok could you please make the quick update?

I've added Laravel 7 support in the new version 4.0.3.
https://github.com/christofferok/laravel-emojione/releases/tag/4.0.3
Let me know if there are any issues 👍🏼

thank you!


fix hibernate.default_schema and hibernate.default_catalog

see #1120

Going to merge this. Even if it's not quite the perfectly most elegant implementation, it's good enough for now.


Code command broken

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.80.2
OS Version: Mac OS 13.1

Steps to Reproduce:

cd /path/to/the/directory
code .
See that instead of opening the desired directory and accessing the files within, that the text editor opens instead with blank results / no file tree.

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.81.1. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

Can you try to reproduce with our nightly insider builds? You can give our preview releases a try from: https://code.visualstudio.com/insiders/

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!

Yes, the problem persists. Sometimes it works, sometimes it doesn't.


fix typos on language distribution

https://github.com/chaoss/wg-common/issues/131

The original text was actually correct, so we're not going to merge this one. Let us know if you have any questions about it. Can you also double check that the translation matches the original text?

The contents of a repository can be counted by iterating through each file, though several libraries exist, including the one used by Augur: https://github.com/boyter/scc
if "though" is corrected here, I don't understand what this sentence want to say....


The editor display dimly.

VSCode Version: 1.1.1
OS Version: win10 10586.318

On 4K resolution ratio monitor the text in editor displays dimly.

@osjn What do you mean by dimly? Can you maybe add a screenshot?

Closing after a number of days without a response.


⚠ Bofrost.de has degraded performance

In 1ccd4ff, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1813 ms

Resolved: Bofrost.de performance has improved in cf52fd2 after 6 minutes.


feat: add FontLoader, Font, & TextGeometry

Why
Resolves #91
What
Add FontLoader, Font, & TextGeometry
Checklist

[x] Storybook entry added
[x] Ready to be merged

Is there any interest in this?


Remove version: SmartSoft.SmartFTP version 10.0.3243.0

[Automated] It returns code over 400 in all urls
Microsoft Reviewers: Open in CodeFlow

@wingetbot run

@wingetbot run

URL: https://static.smartftp.com/static/Products/Client/10.0.3243.0/x64/SmartFTP.msi
Response Error: The remote server returned an error: (404) Not Found.
(Automated message - build 923)