karma-remap-istanbul with Quickstart angular 2 configuration shows application output on browser

I have taken the latest Angular 2 Quickstart clone. I have updated the karma.config.js file according to the steps mentioned. My test cases run and the coverage report is generated in Typescript which is great!
The Chrome browser shows the default page of the application when test cases are run as follows:

karma.config.js file:

module.exports = function (config) {

  var appBase = 'app/';      // transpiled app JS and map files
  var appSrcBase = 'app/';      // app source TS files
  var appAssets = '/base/app/'; // component assets fetched by Angular's compiler

  // Testing helpers (optional) are conventionally in a folder called `testing`
  var testingBase = 'testing/'; // transpiled test JS and map files
  var testingSrcBase = 'testing/'; // test source TS files

  config.set({
    basePath: '',
    frameworks: ['jasmine'],

    plugins: [
      require('karma-jasmine'),
      require('karma-chrome-launcher'),
      require('karma-jasmine-html-reporter'),
      require('karma-remap-istanbul'),
      require('karma-coverage')
    ],

    client: {
      builtPaths: [appBase, testingBase], // add more spec base paths as needed
      clearContext: false // leave Jasmine Spec Runner output visible in browser
    },

    customLaunchers: {
      // From the CLI. Not used here but interesting
      // chrome setup for travis CI using chromium
      Chrome_travis_ci: {
        base: 'Chrome',
        flags: ['--no-sandbox']
      }
    },

    files: [
      // System.js for module loading
      'node_modules/systemjs/dist/system.src.js',

      // Polyfills
      'node_modules/core-js/client/shim.js',
      'node_modules/reflect-metadata/Reflect.js',

      // zone.js
      'node_modules/zone.js/dist/zone.js',
      'node_modules/zone.js/dist/long-stack-trace-zone.js',
      'node_modules/zone.js/dist/proxy.js',
      'node_modules/zone.js/dist/sync-test.js',
      'node_modules/zone.js/dist/jasmine-patch.js',
      'node_modules/zone.js/dist/async-test.js',
      'node_modules/zone.js/dist/fake-async-test.js',

      // RxJs
      { pattern: 'node_modules/rxjs/**/*.js', included: false, watched: false },
      { pattern: 'node_modules/rxjs/**/*.js.map', included: false, watched: false },

      // Paths loaded via module imports:
      // Angular itself
      { pattern<EMAIL_ADDRESS>included: false, watched: false },
      { pattern<EMAIL_ADDRESS>included: false, watched: false },

      { pattern: 'systemjs.config.js', included: false, watched: false },
      { pattern: 'systemjs.config.extras.js', included: false, watched: false },
      'karma-test-shim.js', // optionally extend SystemJS mapping e.g., with barrels

      // transpiled application & spec code paths loaded via module imports
      { pattern: appBase + '**/*.js', included: false, watched: true },
      { pattern: testingBase + '**/*.js', included: false, watched: true },

      // Asset (HTML & CSS) paths loaded via Angular's component compiler
      // (these paths need to be rewritten, see proxies section)
      { pattern: appBase + '**/*.html', included: false, watched: true },
      { pattern: appBase + '**/*.css', included: false, watched: true },

      // Paths for debugging with source maps in dev tools
      { pattern: appSrcBase + '**/*.ts', included: false, watched: false },
      { pattern: appBase + '**/*.js.map', included: false, watched: false },
      { pattern: testingSrcBase + '**/*.ts', included: false, watched: false },
      { pattern: testingBase + '**/*.js.map', included: false, watched: false }
    ],

    // Proxied base paths for loading assets
    proxies: {
      // required for component assets fetched by Angular's compiler
      "/app/": appAssets
    },

    exclude: [],

    preprocessors: {
      'app/**/!(*spec).js': ['coverage']
    },
    //    reporters: ['progress', 'kjhtml'],

    reporters: ['progress', 'coverage', 'karma-remap-istanbul'],
    remapIstanbulReporter: {
      reports: {
        html: 'coverage'
      }
    },

    port: 9876,
    colors: true,
    logLevel: config.LOG_INFO,
    autoWatch: true,
    browsers: ['Chrome'],
    singleRun: false
  })
}

Why does the application output show?

Sorry I'm not quite sure I understand your question, are you asking why this window opens when your tests run?

The "Hello Angular" on the page is actually in my code's app.html file (page that loads with npm start). Ideally when you run karma tests this window comes up as a blank white page. I am afraid as my application matures, the application home page will be shown when test cases run with karma.

That's how karma works - it will compile and test your components in the browser so you'll see the output of the compiled component in the browser window. If you call fixture.destroy() after the test is run it should remove it from the DOM. Alternatively just use a headless browser instead which won't have a browser window.


Fixing Travis issue with libgfortran

After a couple unsuccessful attempts to fix this mysterious issue on master, this PR will allow me to try as many different things as necessary till the tests are working again.

Very odd issue. Looks like it it's passing now though, will merge.


make the annotation adapter use instanceof to check the type and do validation

I'm thinking for annotations that accept multiple unrelated types we make the annotation adapter use instanceof to check the type and do validation

Do you an example?  I'm not sure I fully understand this yet ...

I'm thinking for annotations that accept multiple unrelated types we make the annotation adapter use instanceof to check the type and do validation

Do you an example? I'm not sure I fully understand this yet ...

For example the siae annotation is supposed to work on arrays, char sequence and collections

So for the size adapter, I've made it so that it takes an Object and does the casting needed to do the validations

this should only be needed when the types the annotation supports have no common interface


fix(ui): persistent hint in confirm dialog

Pull Request Test Coverage Report for Build 588748711

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 19.388%

Totals

Change from base Build 588722954:
0.0%

Covered Lines:
2027

Relevant Lines:
10724

💛  - Coveralls


Make clear how this relates to dotnet core "PublishReadyToRun" and .NET Native

Is the NativeImageCompiler still supported? How does it relate to dotnet core "PublishReadyToRun" and .NET Native?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

Is NativeImageCompiler simply “NGEN” rebranded? How is this different from “brittle” ngen native compilation?
https://docs.microsoft.com/en-us/dotnet/framework/net-native/net-native-and-compilation
“... If no native image is available for a particular method, NGEN falls back to JITing code. This means that native images must continue to include metadata and IL in the event that NGEN needs to fall back to JIT compilation...“
“... NGEN images tend to be fragile. For example, a patch or change to a dependency typically requires that the assemblies that use it also be re-NGENed...”

NativeImageCompile and PublishReadyToRun are pretty much the same technology. The former is for .net framework/msix, and the later is applicable to .net core apps.
NativeImageCompiler is a package that contains:
• Crossgen compiler for .net framework
• Specially built framekwork reference-assemblies that crossgen can use for native-compilation of desktop apps.
Crossgen was concurrently developed for .net framework and .net core until a couple of years ago, so it’s the same technology. However, subsequent development and improvements are only done for .net core (now re-branded as .net 5).

Thanks Swaroop.
@3wavellc  @Marv51  Does that suffice?

Yes.
Thank you
Pete
Pete Shramko
3rd Wave, llc
2800 Post Oak Blvd Suite 4100
Houston, TX 77056
<EMAIL_ADDRESS>954-646-5011

From: Kevin Larkin (MS<EMAIL_ADDRESS>Sent: Thursday, April 2, 2020 5:20:51 PM
To: MicrosoftDocs/msix-docs<EMAIL_ADDRESS>Cc: Pete Shramko<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/msix-docs] Make clear how this relates to dotnet core "PublishReadyToRun" and .NET Native (#86)
Thanks Swaroop.
@3wavellchttps://github.com/3wavellc @Marv51https://github.com/Marv51 Does that suffice?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/msix-docs/issues/86#issuecomment-608095848, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AOTCDGNYEM7XOIO4WOJORM3RKT6THANCNFSM4J523NOA.


Don't show Event Feed when you don't have permission

Overview
Currently, we always show the Event Feed even if a user does not have permission. Instead, this page should be fully hidden from the user when they do not have permission to see it. If a user does not have permission to see the Event Feed page they should be directed to the next available page (left-to-right).

Design Details
User has access to at least one page

If a user does not have permission to see the Event Feed page they should be directed to the next available page (left-to-right).

User has access to no pages
Abstract designs

Hide the left-nav
Hide the projects dropdown
Change background color to #fff
Display message (with both chef support and automate documentation being external links)...

It looks like you do not have permission to access any data in Automate.
Reach out to your administrator or contact Chef Support for help.

In the meantime, feel free to explore the Automate documentation.

References

Convert SettingsLandingComponent to reusable landing component
Settings landing page for permission-based routing

💭 Could we have a similar behaviour for when the backend can't be reached? Right now, we've got a pop up saying that the license cannot be verified, I think.

content needs to be updated to:
Reach out to your administrator or contact Chef Support for help.

In the meantime, feel free to explore the Automate documentation.```

as part of feedback from @mjingle

@susanev find out if auth can more simply communicate if a user has access to no pages

note: the screenshots are old, the top nav is now named Dashboards

✅ I'll accept this. Logging in as a user with no perms whatsoever, I see the blank page. When then making my user a member of the "Compliance Viewers" policy, I see the topnav containing only the Compliance tab.

I hope you mean blank page with no-permissions message. 😉

i hope so too!


Adjusted adopters.md to add consulting firms

Description

References

Review Checklist

[ ] I have clicked on "allow edits by maintainers".
[ ] I have added documentation for new/changed functionality in this PR or in a PR to openfga.dev [Provide a link to any relevant PRs in the references section above]
[ ] The correct base branch is being used, if not main
[ ] I have added tests to validate that the change in functionality is working as expected

The formatting LGTM.  I wonder if it would be a good idea to include language about criteria for inclusion in this section making it clear that the list is intended to be inclusive vs curated so it's clear to readers whether the list represents any endorsement or review process by the project vs. simply being a convenient resource those looking for these services can use as a starting point.

@ryanpq Makes sense, in general in both cases PRs are submitted by community members. Can you suggest a language indicating that it's not an endorsement?


How to create a new field

Hi,
Can you please confirm if there is a way to create a new field and set a value to it using a tagger?
Thank you

You mean explicitly setting a value, not coming from the document content?  If so, ConstantTagger is your friend.

Hi Pascal,
Thank you for your response. It is working like you've said.

Glad to hear.


rpcsrv: align default error code with C# implementation

Close #3586

I found only one place in C# where the HTTP status code is overwritten  internal bool CheckAuth(HttpContext context) (https://github.com/neo-project/neo/blob/233d0b03501a1af5e6a140721a67bb37de84ecc9/src/Plugins/RpcServer/RpcServer.cs#L67-L76  ) to 401, others application-level errors will be with http.StatusOK.  So now we have 400, 405 and 500 in getHTTPCodeForError, but none is explicitly set in C#. Please @AnnaShaleva correct me if I'm wrong.

I found only one place in C# where the HTTP status code is overwritten internal bool CheckAuth

This method is not applicable to our RPC server due to the different wallet model, hence we don't need to port the status code of this method.

but none is explicitly set in C#. Please @AnnaShaleva correct me if I'm wrong.

Yep, that's true. Here's a simple check, I sent several requests to C# node:

405 code (unknown method, neorpc.MethodNotFoundCode). The resulting HTTP code returned by C# server is 200 OK:

anna@kiwi:~/Documents/GitProjects/bane-labs/go-ethereum$ curl -v -d '{ "jsonrpc": "2.0", "id": 1, "method": "unknown-method", "params": [] }' http://seed1t5.neo.org:20332 | json_pp
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0*   Trying <IP_ADDRESS>:20332...
* Connected to seed1t5.neo.org (<IP_ADDRESS>) port 20332 (#0)
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0> POST / HTTP/1.1
> Host: seed1t5.neo.org:20332
> User-Agent: curl/7.81.0
> Accept: */*
> Content-Length: 71
> Content-Type: application/x-www-form-urlencoded
>
} [71 bytes data]
* Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
< Content-Type: application/json
< Date: Tue, 12 Nov 2024 13:45:51 GMT
< Server: Kestrel
< Transfer-Encoding: chunked
<
{ [461 bytes data]
100   520    0   449  100    71    729    115 --:--:-- --:--:-- --:--:--   844
* Connection #0 to host seed1t5.neo.org left intact
{
   "error" : {
      "code" : -32601,
      "data" : "   at Neo.Plugins.Result.True_Or(Boolean result, RpcError err)\n   at Neo.Plugins.RpcServer.ProcessRequestAsync(HttpContext context, JObject request)",
      "message" : "Method not found - The method 'unknown-method' doesn't exists. -    at Neo.Plugins.Result.True_Or(Boolean result, RpcError err)\n   at Neo.Plugins.RpcServer.ProcessRequestAsync(HttpContext context, JObject request)"
   },
   "id" : 1,
   "jsonrpc" : "2.0"
}

400 code (malformed request, neorpc.BadRequestCode). The resulting HTTP code returned by C# server is 200 OK:

anna@kiwi:~/Documents/GitProjects/bane-labs/go-ethereum$ curl -v -d '{ "jsonrpc": "2.0", "id": 1, "method": "getapplicationlog", "params": ["] }' http://seed1t5.neo.org:20332 | json_pp
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0*   Trying <IP_ADDRESS>:20332...
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0* Connected to seed1t5.neo.org (<IP_ADDRESS>) port 20332 (#0)
> POST / HTTP/1.1
> Host: seed1t5.neo.org:20332
> User-Agent: curl/7.81.0
> Accept: */*
> Content-Length: 75
> Content-Type: application/x-www-form-urlencoded
>
} [75 bytes data]
* Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
< Content-Type: application/json
< Date: Tue, 12 Nov 2024 13:50:12 GMT
< Server: Kestrel
< Transfer-Encoding: chunked
<
{ [86 bytes data]
100   150    0    75  100    75     84     84 --:--:-- --:--:-- --:--:--   169
* Connection #0 to host seed1t5.neo.org left intact
{
   "error" : {
      "code" : -32700,
      "message" : "Bad request"
   },
   "id" : null,
   "jsonrpc" : "2.0"
}

500 code (internal server error, neorpc.InternalServerErrorCode). It's difficult to reproduce this error on real network for C# server, but the resulting code is expected to be the same, 200 OK.

Hence, we don't really need these additional HTTP codes on the NeoGo server side.


fixed the links in the nav bar of news page

Description
Added icons to the navbar links and all the links successfully redirect to the required page
Related Issues
[Cite any related issue(s) this pull request addresses. If none, simply state “None”]

Closes #585

Type of PR

[x] Bug fix
[ ] Feature enhancement
[ ] Documentation update
[ ] Other (specify): _______________

Screenshots / videos (if applicable)

Checklist

[x] I have gone through the contributing guide
[x] I have updated my branch and synced it with project main branch before making this PR
[x] I have performed a self-review of my code
[x] I have tested the changes thoroughly before submitting this pull request.
[x] I have provided relevant issue numbers, screenshots, and videos after making the changes.
[x] I have commented my code, particularly in hard-to-understand areas.

Additional context:
GSSoC'24

Please review my pull request @varshith257 @Anishkagupta04


Fix bad replacements and code formatting for examples

Fixes errors noted in https://github.com/tdwg/chrono/issues/35 and which were fixed in the machine-readable metadata in https://github.com/tdwg/rs.tdwg.org/commit/87049bb3b0ba9f9351c8e2f655d61c6010eccb61

@tucotuco Please check this out and merge if OK

Looks good. Easiest to see it deployed. Merging.


[3.2.x] Upgrade to Quarkus CXF 2.2.4

The failure in the JDBC test is known as https://github.com/apache/camel-quarkus/issues/5353


xplat: Improve spinLock and criticalSection implementations

Measured on amd64, new CCSpinLock works twice faster comparing to older
implementation and uses a lighter interface. Besides, previous
interface was interfering with blocking threads.

No CI ? /cc @dilijev

@digitalinfinity @jianchun ping

@jianchun Thanks for the review! Anything else?


Icon: Update Icons [GESTALT-8286]

Pull Request Instructions
Introducing 1 new icon, and updating other previous icons
Diff
Interactive differences in the PR are available to see here.
Classic Icons
VR Icons
This PR fixes deviations in sound related icons:

mute
mute-fill
sound-fill
sound-slash-fill
sound-slash
sound

New Icons Introduced

ar-try-on.svg

Classic
VR
Links

Jira
[TDD](link to Paper doc)
[Figma](link to Figma file)

Checklist

[ ] Added unit tests
[ ] Added documentation + accessibility tests
[ ] Verified accessibility: keyboard & screen reader interaction
[ ] Checked dark mode, responsiveness, and right-to-left support
[ ] Checked stakeholder feedback (e.g. Gestalt designers, relevant feature teams)

R+ but can we add metadata for the new icon?

Oh good catch!


Fix PNG transparency in base64 backend upload

Transparent background support added in https://github.com/chrisiaut/pictshare/commit/948088ae51121bd738bed1a06666ee6fea9ec29d currently works only for uploading from form. This PR adds support of it for base64 string images from backend endpoint too.

awesome thanks


Groupby dictionary aggregation regression

System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Ubuntu 20.04
Modin version : aa818f5a246703621d4a70edaa04b92a511faa46
Python version: 3.8.6
Code we can use to reproduce:

import os

os.environ["MODIN_ENGINE"] = "ray"
os.environ["MODIN_CPUS"] = "4"

import modin.pandas as pd
from timeit import default_timer as timer

data_filename = "h2o_10k.csv"

df = pd.read_csv(data_filename)

def q1(df):
    groupby_cols = ["id1"]
    agg_cols_funcs = {"v1": "sum"}

    return df.groupby(groupby_cols).agg(agg_cols_funcs)

def q10(df):
    groupby_cols = ["id1", "id2", "id3", "id4", "id5", "id6"]
    agg_cols_funcs = {"v3": "sum", "v1": "count"}

    return df.groupby(groupby_cols).agg(agg_cols_funcs)

def meas_func(func, iters, *args, **kwargs):
    t_meas = float("inf")
    for _ in range(iters):
        t0 = timer()
        ans = func(*args, **kwargs)
        ans.shape
        t = timer() - t0
        del ans
        t_meas = t if t < t_meas else t_meas

    return t_meas

t_q1 = meas_func(q1, iters=3, **{"df": df})
t_q10 = meas_func(q10, iters=3, **{"df": df})

# results comparison between before vs after ee39d1767efb363fe6c147fc701b41315eee3afa commit
print("t_q1:", t_q1) # 0.026 s vs 0.031s
print("t_q10:", t_q10) # 0.091 s vs 2.09 s

Describe the problem

Regression occurred after ee39d1767efb363fe6c147fc701b41315eee3afa commit.
data file h2o_10k.txt
Source code / logs

The reason for the slow dict-groupby is pretty ridiculous. There is a dict, that contains map and reduce functions for every operation that supports GroupbyReduce. These functions are applied to groups in every partition.
https://github.com/modin-project/modin/blob/aa818f5a246703621d4a70edaa04b92a511faa46/modin/data_management/functions/groupby_function.py#L234-L267
The problem is that they're all lambdas, for pandas all of them are unknown python callables, so it can't execute aggregation with its fast C module, we force it to apply our callables. If we replace callables to the function names it performs much faster!
Here is a comparison of groupby aggregation in pandas with function name and with callable:
import pandas
from timeit import default_timer as timer

# 500mb H2O dataset
data_filename = "/localdisk/benchmark_datasets/h2o/G1_1e7_1e1_0_0.csv"
df = pandas.read_csv(data_filename)

t1 = timer()
df.groupby("id6").agg({"v1": "sum"})
print(f"str function: {timer() - t1}")

t1 = timer()
df.groupby("id6").agg({"v1": lambda df: df.sum()})
print(f"callable function: {timer() - t1}")

# Output:
# str function: 0.7193635171279311
# callable function: 38.2026267433539

Speaking about modin, when I replaced lambdas to function names in groupby_reduce_functions and ran the script from the issue header I got this results:
Before ee39d17:
t_q1: 0.025292523205280304
t_q10: 0.08418524172157049

After ee39d17:
t_q1: 0.030419232323765755
t_q10: 1.9959391057491302

After ee39d17 + fix(lambdas -> str-names):
t_q1: 0.023051242344081402
t_q10: 0.0943737206980586

Going to create PR that fixes this soon

results of H2O queries with 500mb dataset and 112 partitions:
Before ee39d17:
t_q1: 3.1282251700758934
t_q10:<PHONE_NUMBER>9238527

After ee39d17 + fix(lambdas -> str-names):
t_q1: 0.3956367587670684
t_q10:<PHONE_NUMBER>882149


Close an engagement

When the engagement end date is due, update engagement status  to closed.
Show status Closed when viewing the engagement.
Survey submissions are not allowed when the engagement is closed.

[ ] Cron job to check engagement dates
[ ] Update engagement view to show status (as per design)
[ ] Update submissions to check engagement status
[ ] Update survey to not be displayed when engagement is closed

Please add your planning poker estimate with ZenHub @saravanpa-aot

Hey team! Please add your planning poker estimate with ZenHub @djnunez-aot @jadmsaadaot @tiagograf-AOT


Support for Win32 variable-sized array fields

Hey @kennykerr and the whole team involved... this is Awesome!! I was really looking forward for this, great move by MS 👍
I was wondering if there's any idea in mind on how to deal with structs that last field is a unsized arrays (ANYSIZE_ARRAY), right now the way winapi-rs is handling this by declaring an array of size 1 (ex. CM_NOTIFY_EVENT_DATA.DeviceHandle.Data). Imho this is a bit of a constraint since we only have one field available which in the end leads to casting to thin pointers and memory transmuting operations -- specially when we receive a struct with this fields from a callback. I know this is a difficult case, and I'm pretty sure there's not straightforward way to solve it without some "unsafe" code but I would love to see/discuss your take on this 😃
BTW, this was already discussed in the internal forums https://internals.rust-lang.org/t/ffi-types-with-unsized-arrays/5203/2
P.S.: I'm aware there's already an issue (https://github.com/microsoft/windows-rs/issues/423) that talks about arrays but I do think this case requires a separate discussion, feel free to close the issue if I'm wrong

Thanks @n4r1b! Yes, this is a tricky one and worthy of discussion. It has arrays and unions - both problematic. When the variable-sized array is trailing, what I tend to do in C++ is to omit the field entirely and simply have an enclosing struct provide the data suitable to the application, assuming the alignment and padding are compatible. I agree an array of size 1 is not very useful but is sometimes the least awful approach. Another approach is illustrated in how I modeled windows::HString's  internal header:
https://github.com/microsoft/windows-rs/blob/256538e85f2f9c860c09c318423b3be79b36b9c3/src/strings/hstring.rs#L216-L224
There is a fine line between too much and too little intervention by the code generator. I will leave this open and spend some time on this and other similar structs like OVERLAPPED that also tend to have trailing data.

Thanks @n4r1b! Yes, this is a tricky one and worthy of discussion. It has arrays and unions - both problematic. When the variable-sized array is trailing, what I tend to do in C++ is to omit the field entirely and simply have an enclosing struct provide the data suitable to the application, assuming the alignment and padding are compatible. I agree an array of size 1 is not very useful but is sometimes the least awful approach. Another approach is illustrated in how I modeled windows::HString's  internal header:
https://github.com/microsoft/windows-rs/blob/256538e85f2f9c860c09c318423b3be79b36b9c3/src/strings/hstring.rs#L216-L224
There is a fine line between too much and too little intervention by the code generator. I will leave this open and spend some time on this and other similar structs like OVERLAPPED that also tend to have trailing data.

The way windows::HString is modeled looks very promising tbh, I've never used MaybeUninit but seems like a good idea to keep the unitialized instance and avoid problems with unknown size at compilation time.
My only concern with MaybeUninit is, and again I've never used it before so I'm not aware of the possible implications:

Note that dropping a MaybeUninit will never call T's drop code. It is your responsibility to make sure T gets dropped if it got initialized.

Would this mean that an implicit call to drop will be needed to free the memory, could this potentially lead to memory leaks?
Correct me if I'm wrong but could it be sth like this: https://play.rust-lang.org/?version=stable&mode=debug&edition=2018&gist=e4a3e375258e6b4b9f59578b9a4b5457

The way windows::HString is modeled looks very promising tbh, I've never used MaybeUninit but seems like a good idea to keep the unitialized instance and avoid problems with unknown size at compilation time.
My only concern with MaybeUninit is, and again I've never used it before so I'm not aware of the possible implications:

Note that dropping a MaybeUninit will never call T's drop code. It is your responsibility to make sure T gets dropped if it got initialized.

Would this mean that an implicit call to drop will be needed to free the memory, could this potentially lead to memory leaks?
Correct me if I'm wrong but could it be sth like this: https://play.rust-lang.org/?version=stable&mode=debug&edition=2018&gist=e4a3e375258e6b4b9f59578b9a4b5457

TOKEN_PRIVILEGES is another variant of an array field with a variable size. Just leaving that here to remind me to cover that.

will const generics fit this case?
#[repr(C)]
pub struct TOKEN_PRIVILEGES<const SIZE: usize> {
    pub PrivilegeCount: u32,
    pub Privileges: [LUID_AND_ATTRIBUTES; SIZE],
}

Closing as duplicate of #907 which is blocked on https://github.com/microsoft/win32metadata/issues/547


Bug: default namespace is hardcoded in the operator

if users installs with namespace keptn the controller should work as usual, this is not true anymore due to this
the namespace should be injected in the controllers from the main where it is initialized using the pod metadata

Keptn v0.8.2 is installed into the keptn namespace.
Some tasks are defined:
❯ kubectl get keptntaskdefinitions.lifecycle.keptn.sh -n keptn
NAME                AGE
core-post-logging   12d
core-pre-logging    12d
core-pre-sleep      12d

apiVersion: lifecycle.keptn.sh/v1alpha3
kind: KeptnTaskDefinition
metadata:
  creationTimestamp: "2023-09-08T07:18:36Z"
  generation: 1
  labels:
    app.kubernetes.io/instance: keptn
    app.kubernetes.io/managed-by: Helm
    app.kubernetes.io/name: klt
    app.kubernetes.io/version: v0.8.2
    argocd.argoproj.io/instance: keptn
    helm.sh/chart: klt-0.2.6
    keptn.sh/task: pre-deployment
  name: core-pre-logging
  namespace: keptn
  resourceVersion: "8401940"
  uid: cbe2c803-c2eb-4ba1-bdde-27e0b4f89d8e
spec:
  container:
    command:
    - sh
    - -c
    - echo "Pre Task has been executed"
    image: busybox:1.36.0
    name: sleep
  retries: 10
  timeout: 5m

The KeptnApp is installed into the demo-uat namespace:
apiVersion: lifecycle.keptn.sh/v1alpha2
kind: KeptnApp
metadata:
  labels:
    {{- include "podinfo.labels" (index $.Subcharts "podinfo") | nindent 4 }}
  name: {{ include "podinfo.fullname" (index $.Subcharts "podinfo") }}
  namespace: {{ .Release.Namespace }}
spec:
  version: "1.0.0"
  revision: 1
  workloads:
    - name: podinfo
      version: 0.1.0
  preDeploymentEvaluations:
    - {{ include "podinfo.fullname" (index $.Subcharts "podinfo") }}-available-cpus
  # postDeploymentEvaluations:
  #   - evaluate-deployment
  preDeploymentTasks:
    - core-pre-logging
  postDeploymentTasks:
    - core-post-logging

The logs:
2023-09-20T13:04:25Z    INFO    KeptnAppVersion Controller      Searching for Keptn App Version
2023-09-20T13:04:25Z    INFO    KeptnAppVersion Controller      Emitting event using *common.cloudEvent
2023-09-20T13:04:25Z    INFO    KeptnAppVersion Controller      Emitting event using *common.k8sEvent
2023-09-20T13:04:25Z    INFO    KeptnAppVersion Controller      Failed to get resource from application namespace       {"resource type": "*v1alpha3.KeptnTaskDefinition", "Definition name": "core-pre-logging", "namespace": "demo-uat"}
2023-09-20T13:04:25Z    INFO    KeptnAppVersion Controller      Failed to get resource from default KLT namespace       {"resource type": "*v1alpha3.KeptnTaskDefinition", "definition name": "core-pre-logging"}
2023-09-20T13:04:25Z    ERROR   KeptnAppVersion Controller      could not find KeptnTaskDefinition      {"error": "KeptnTaskDefinition.lifecycle.keptn.sh \"core-pre-logging\" not found"}


Codecov always on "Waiting for status to be reported "

I've noticed this happening on occasion as well... not sure what's causing it though.

@nicoddemus @rougeth we had some problems with it in Tenfold too, we noticed that sometimes codecov had delay to process the new coverages entries (mainly when you have many concurrencies builds running and reporting)

codecov and pytest-cov are showing different reports :/ (both on master)


Add customization to move ammo/health/metal away from the center of the screen

If more people request this, I think I'll pursue it. For now, I haven't heard of too many people requesting this.


Functionality to generate Academic Audiobooks?

This looks fantastic, thanks so much for building this tool! I'm wondering if any consideration has been given to build functionality that would allow the conversion of academic documents into audiobooks? Like many of my colleagues, I struggle with keeping up to date with published literature in my field. Being able to listen to new publications would be a game changer.

Thank you!
Sounds like an interesting project. But I don't think we'll be looking into that in the near future.
Best,
Lukas

Just found this repo, that uses nougat for something like this:
https://github.com/kaieberl/paper2speech

Thank you!!
Get Outlook for iOShttps://aka.ms/o0ukef

From: Lukas Blecher @.>
Sent: Monday, September 18, 2023 4:50:35 AM
To: facebookresearch/nougat @.>
Cc: Stephan Kadauke @.>; Author @.>
Subject: [External]Re: [facebookresearch/nougat] Functionality to generate Academic Audiobooks? (Issue #81)
Just found this repo, that uses nougat for something like this:
https://github.com/kaieberl/paper2speech
—
Reply to this email directly, view it on GitHubhttps://github.com/facebookresearch/nougat/issues/81#issuecomment-1723082874, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACTGHWTPLNOUGNKWOZYGD7TX3AKOXANCNFSM6AAAAAA42LI66M.
You are receiving this because you authored the thread.Message ID: @.***>
** This email originated from an EXTERNAL sender to CHOP. Proceed with caution when replying, opening attachments, or clicking links. Do not disclose your CHOP credentials, employee information, or protected health information to a potential hacker**.


Hex dependency resolution failed

I'm using
{:phoenix_ecto, "~> 2.0"}
Maybe you can bump up the deps

Hi. Which packages are conflicting?

{:phoenix_ecto, "~> 2.0"}

Which package is it conflicting with?

Hi Max
I tried making a project with these deps:
  defp deps do
    [
     {:calecto, "~> 0.5.2"},
     {:phoenix_ecto, "~> 2.0.0"},
    ]
  end

and there were no conflicts. I need more information about which packages are conflicting in order to help.


Update 01_Basic_QA_Pipeline.ipynb

fixed link

Done! Thanks for detailed instructions, sorry for ignoring the guidelines.

Done! Thanks for detailed instructions, sorry for ignoring the guidelines.

Hey no worries :) Thanks again for fixing this :1st_place_medal:


How to get model training process? such as 20%, 80%.

For some case, It will take long time to training a model, a "Processing" status is not enough for user experience.  We will provide training progress and left time estimation.
Thanks

@cloustone we dont give a progress indicator right now - but something we are discussing


PEX builds broken on Big Sur after recent update

I recently got a new work laptop with Big Sur installed, and I'm seeing a new error when building PEX files locally:
$ /Users/jlewis/nerdwallet/indy/build/venv/indy_macosx-11-x86-64_cp3.7/bin/python /Users/jlewis/nerdwallet/indy/build/venv/indy_macosx-11-x86-64_cp3.7/bin/pex --disable-cache --no-pypi --index=https://artifactory.nerdwallet.io/artifactory/api/pypi/pypi/simple/ --no-transitive --output-file=/Users/jlewis/nerdwallet/indy/build/dist/indy/1.1.119/pex/indy.pex --pre --preamble-file=/Users/jlewis/nerdwallet/indy/build/pex_preamble.py --python=/Users/jlewis/nerdwallet/indy/build/venv/indy_macosx-11-x86-64_cp3.7/bin/python --requirement=/Users/jlewis/nerdwallet/indy/requirements.txt --resolver-version=pip-2020-resolver --platform=linux-x86_64-cp-37-cp37m --platform=macosx-10.13-x86_64-cp-37-cp37m --no-emit-warnings --venv --script=indy /Users/jlewis/nerdwallet/indy/build/dist/indy/1.1.119/wheel/indy-1.1.119-py3-none-any.whl
Failed to spawn a job for DistributionTarget(platform=Platform(platform='linux_x86_64', impl='cp', version='37', abi='cp37m')): 'int' object has no attribute 'split'

I dug into the PEX code, and the underlying issue is a mistaken assumption about the possible values of sysconfig.get_config_var("MACOSX_DEPLOYMENT_TARGET"). Currently, create_isolated_cmd assumes that is a string: https://github.com/pantsbuild/pex/blob/3a5f1ecd486ba049b58954d2b9ec48dd7e6d1a5c/pex/interpreter.py#L1089
However, I've verified locally that sysconfig.get_config_var("MACOSX_DEPLOYMENT_TARGET") can return an int:
Python 3.7.10 (default, Feb 27 2021, 02:19:57)
Type 'copyright', 'credits' or 'license' for more information
IPython 7.20.0 -- An enhanced Interactive Python. Type '?' for help.

In [1]: import sysconfig

In [2]: sysconfig.get_config_var("MACOSX_DEPLOYMENT_TARGET")
Out[2]: 11

You can see a similar issue reported to numpy: Mac OS X Big Sur: sysconfig.get_config_var('MACOSX_DEPLOYMENT_TARGET') can return an int, but a str is required
The fix should be as simple as coercing to string after this line: https://github.com/pantsbuild/pex/blob/3a5f1ecd486ba049b58954d2b9ec48dd7e6d1a5c/pex/interpreter.py#L94
        configured_macosx_deployment_target = configured_macosx_deployment_target and str(configured_macosx_deployment_target)

@luislew I think you've fully sussed this all out. Thanks for digging.
Are you up for contributing the fix? I don't have access to macOS for experimentation and repro on things like this, so it's ideal to get a fix from someone who can prove the fix works directly.

Small note for future readers: this is a python bug. https://bugs.python.org/issue42504 . This has caused breakage in a lot of different packages (pandas, numpy, shap, etc) that used MACOSX_DEPLOYMENT_TARGET. The fix has been backported to 3.9 & 3.8 but I'm not sure if it's released in homebrew or base system python yet.


Error on clicking away from RawAutocomplete to another RawAutocomplete

Steps to reproduce
Click on one autocomplete, then click on another.
Expected results
No error is expected
Actual results
file:///Users/edeetee/fvm/versions/3.24.3/packages/flutter/lib/src/widgets/overlay.dart:1573:14
_zOrderIndex != null
is not true
    at Object.throw_ [as throw] (errors.dart:296:3)
    at Object.assertFailed (errors.dart:29:3)
    at overlay$.OverlayPortalController.new.hide (overlay.dart:1573:27)
    at [_updateOptionsViewVisibility] (autocomplete.dart:349:7)
    at _RawAutocompleteState.new._onChangedField (autocomplete.dart:368:7)
    at _onChangedField.next (<anonymous>)
    at async_patch.dart:45:50
    at _RootZone.runUnary (zone.dart:1661:54)
    at _FutureListener.thenAwait.handleValue (future_impl.dart:163:18)
    at handleValueCallback (future_impl.dart:861:44)
    at _Future._propagateToListeners (future_impl.dart:890:13)
    at [_completeWithValue] (future_impl.dart:666:5)
    at async._AsyncCallbackEntry.new.callback (future_impl.dart:736:7)
    at Object._microtaskLoop (schedule_microtask.dart:40:11)
    at _startMicrotaskLoop (schedule_microtask.dart:49:5)
    at async_patch.dart:181:7

Code sample
The error should give you something to go on.
But here is also the widget that this is happening in.
We use the textController and focusNode in order to update the state of the text field from our app state.
Code sample
import 'package:flutter/material.dart';
import 'package:flutter_riverpod/flutter_riverpod.dart';
import 'package:hooks_riverpod/hooks_riverpod.dart';
import 'package:mapbox_search/models/predictions.dart';
import 'package:smart_access/theme.dart';
import 'package:smart_access/util/geocoding.dart';

class LocationSearchBar extends ConsumerWidget {
  LocationSearchBar({
    Key? key,
    required this.onSuggestionTapped,
    required this.hintText,
    //should use stateful textcontroller
    TextEditingController? textController,
    //should only use stateless focusnode
    FocusNode? focusNode,
    this.suffixIcon,
  })  : _textController = textController ?? TextEditingController(),
        _focusNode = focusNode ?? FocusNode(),
        super(key: key);

  final String hintText;

  final TextEditingController _textController;
  final void Function(MapBoxPlace place) onSuggestionTapped;
  final Widget? suffixIcon;
  final FocusNode _focusNode;
  final GlobalKey _autocompleteKey = GlobalKey();

  @override
  Widget build(BuildContext context, WidgetRef ref) {
    // final borderStyle = context.theme.inputDecorationTheme.border;
    // final focusedBorderStyle = context.theme.inputDecorationTheme.focusedBorder;
    final textFieldKey = GlobalKey();

    ///Use RawAutocomplete to pass a custom textEditingController
    return RawAutocomplete<MapBoxPlace>(
      focusNode: _focusNode,
      key: _autocompleteKey,
      textEditingController: _textController,
      onSelected: onSuggestionTapped,
      optionsBuilder: (TextEditingValue textEditingValue) async {
        if (textEditingValue.text.isEmpty) {
          return const Iterable<MapBoxPlace>.empty();
        }
        return await searchLocation(textEditingValue.text, ref) ?? [];
      },
      displayStringForOption: (MapBoxPlace option) => option.placeName ?? '',
      fieldViewBuilder: (
        BuildContext context,
        TextEditingController textEditingController,
        FocusNode focusNode,
        VoidCallback onFieldSubmitted,
      ) {
        return TextField(
          key: textFieldKey,
          controller: textEditingController,
          focusNode: focusNode,
          style: TextStyle(
            color: context.theme.colorScheme.onPrimary,
            fontSize: 14,
          ),
          onSubmitted: (value) => onFieldSubmitted(),
          decoration: InputDecoration(
            filled: false,
            hintText: hintText,
            hintStyle: TextStyle(
              color: context.theme.colorScheme.onPrimary.withOpacity(0.5),
              fontSize: 14,
            ),
            suffixIcon: suffixIcon != null
                ? TextFieldTapRegion(
                    child: suffixIcon,
                  )
                : Icon(
                    Icons.search,
                    color: context.theme.colorScheme.onPrimary,
                    size: 20,
                  ),
            contentPadding:
                const EdgeInsets.symmetric(vertical: 0.0, horizontal: 12.0),
            // border: borderStyle,
            // enabledBorder: borderStyle,
            // focusedBorder: focusedBorderStyle,
          ),
        );
      },
      optionsViewBuilder: (
        BuildContext context,
        AutocompleteOnSelected<MapBoxPlace> onSelected,
        Iterable<MapBoxPlace> options,
      ) {
        final textFieldBox =
            textFieldKey.currentContext?.findRenderObject() as RenderBox?;
        final textFieldWidth = textFieldBox?.size.width ?? double.infinity;

        final highlightedOption = AutocompleteHighlightedOption.of(context);

        return Align(
          alignment: Alignment.topLeft,
          child: Material(
            color: context.theme.colorScheme.primary,
            elevation: 4.0,
            child: ConstrainedBox(
              constraints: const BoxConstraints(maxHeight: 400),
              child: SizedBox(
                width: textFieldWidth,
                child: ListView.builder(
                  itemCount: options.length,
                  itemBuilder: (BuildContext context, int index) {
                    final MapBoxPlace option = options.elementAt(index);

                    final isSelected = highlightedOption == index;

                    return ListTile(
                      shape: RoundedRectangleBorder(
                        side: BorderSide(
                          color: isSelected
                              ? context.theme.colorScheme.onPrimary
                              : Colors.transparent,
                        ),
                        borderRadius: isSelected
                            ? BorderRadius.circular(4.0)
                            : BorderRadius.zero,
                      ),
                      title: Text(option.placeName ?? ''),
                      onTap: () {
                        debugPrint("Selected place: ${option.placeName}");
                        onSelected(option);
                        // onSuggestionTapped(option);
                      },
                    );
                  },
                ),
              ),
            ),
          ),
        );
      },
    );
  }
}

Screenshots or Video

Screenshots / Video demonstration
[Upload media here]

Logs
Logs
[Paste your logs here]

Flutter Doctor output
Doctor output
➜ fvm flutter doctor
Doctor summary (to see all details,
run flutter doctor -v):
[✓] Flutter (Channel stable, 3.24.3,
    on macOS 15.0 24A335 darwin-arm64,
    locale en-NZ)
[!] Android toolchain - develop for
    Android devices (Android SDK
    version 34.0.0)
    ✗ cmdline-tools component is
      missing
      Run `path/to/sdkmanager
      --install
      "cmdline-tools;latest"`
      See
      https://developer.android.com/st
      udio/command-line for more
      details.
    ✗ Android license status unknown.
      Run `flutter doctor
      --android-licenses` to accept
      the SDK licenses.
      See
      https://flutter.dev/to/macos-and
      roid-setup for more details.
[✓] Xcode - develop for iOS and macOS
    (Xcode 15.1)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2023.2)
[✓] VS Code (version 1.94.0)
[✓] Connected device (3 available)
    ! Error: Browsing on the local area network for iPhone. Ensure the device is unlocked and attached with
      a cable or associated with the same local area network as this Mac.
      The device must be opted into Developer Mode to connect wirelessly. (code -27)
[✓] Network resources

! Doctor found issues in 1 category.

Hi @edeetee, the code sample you have provided contains third-party packages and other classes that are not available to us. Please provide a complete minimal reproducible code sample without any third party packages so that we can properly investigate this.
Thank you

There has been a few different problems with the RawAutocomplete that we have worked around. I think the most basic issue is that as far as we could see, there is no good way to update the text externally. Reading the RawAutocomplete code gives the impression that the textController and focusNode arguments are just there to support having an external text box, not using the internal text box and just having it update through external state.

Hi @edeetee, can you provide a minimal reproducible code sample that demonstrates the issue so that we can properly address this?

hi i've got a similar problem since 3.24 in my application but does not seems to be related to giving focus to an other autocomplete.
i produce it with a single autocomplete in my page when i select an element in the options popup, but not each time...
i do not have the exact repro steps for now


Generating a slug from a title afterStateUpdated $set()

Package
filament/filament
Package Version
3
Laravel Version
11
Livewire Version
3
PHP Version
8.3.0
Problem description
Followed this guide:
https://filamentphp.com/docs/3.x/forms/advanced#generating-a-slug-from-a-title
There seems to be a bug, see video.
I attempt to write Hello World but some text is automatically deleted.
Screencast from 2024-04-14 16-51-13.webm
Note: When i type slowly it works
Expected behavior
Slug field should show "Hello World"
Steps to reproduce
follow the tutorial.
Reproduction repository
https://github.com/csandreas1/event-system
Relevant log output
No response

I am having the same issue after copying the exact code in the documentation.   The title fields keep removing what I am typing in.

I'm facing the same situation. When typed slowly in title field, slug field is updated accurately, but when typed at normal speed cursor does backspace removing some characters.

Hi there — apologies for resurrecting this but I've just had the exact same issue after following the same guidance on a fresh resource. The slug field will work well but if you type quickly, the letters in the originating (title) field seem to be getting wiped — as if the process is not quite up to date with the field's current value and is lagging behind.

I've tried multiple methods — adding a debounce value works but it falls apart eventually no matter how high the number is. onBlur argument to live seems to be the most robust but not as good UX as it updating live.
In some cases I did notice intermediate XHRs to livewire/update that contain an out of sync value for the field being monitored.
I think it may be something to do with $set? When it's not being used, a log of the current $state within the afterStateUpdated callback seems to be accurate every time.

Why has this been close ? 🤔


'Unsupported datatype for constant' when trying to run on a M1 Pro

Hi there,
I installed on a M1 Pro machine with 32GB memory like so:
conda create --name omega
conda activate omega
conda install ipython
conda install biopython
git clone https://github.com/HeliXonProtein/OmegaFold
cd OmegaFold
ipython setup.py install
and ran into the following error:
(omega) csnow@blizzard tmp % omegafold test_0.fasta test_0_omega
INFO:root:Loading weights from /Users/csnow/.cache/omegafold_ckpt/model.pt
INFO:root:Constructing OmegaFold
INFO:root:Reading test_0.fasta
INFO:root:Predicting 1th chain in test_0.fasta
INFO:root:86 residues in this chain.
/AppleInternal/Library/BuildRoots/560148d7-a559-11ec-8c96-4add460b61a6/Library/Caches/com.apple.xbs/Sources/MetalPerformanceShadersGraph/mpsgraph/MetalPerformanceShadersGraph/Core/Files/MPSGraphUtilities.mm:343: failed assertion `unsupported datatype for constant'

Hi!
Thanks for your interests! The support for Apple Silicons has been on beta/prototype from PyTorch, which may have created some issues with our code. We have been looking for solutions, stay tuned!

Just to add onto ongoing issues with M1, here is my installation on a MacBook Pro (13-inch, M1, 2020) and the error during a test run with a 45-residue protein
INSTALLATION
conda create --name omegafold
conda activate omegafold
conda install -c conda-forge biopython
conda install pytorch torchvision torchaudio -c pytorch-nightly
git clone https://github.com/HeliXonProtein/OmegaFold
cd OmegaFold
python setup.py install
EXECUTION
python main.py test.fasta testprot/
OUTPUT
INFO:root:Loading weights from /Users/ceramirez/.cache/omegafold_ckpt/model.pt
INFO:root:Constructing OmegaFold
INFO:root:Reading test.fasta
INFO:root:Predicting 1th chain in test.fasta
INFO:root:45 residues in this chain.
loc("mps_multiply"("(mpsFileLoc): /AppleInternal/Library/BuildRoots/b6051351-c030-11ec-96e9-3e7866fcf3a1/Library/Caches/com.apple.xbs/Sources/MetalPerformanceShadersGraph/mpsgraph/MetalPerformanceShadersGraph/Core/Files/MPSGraphUtilities.mm":219:0)): error: input types 'tensor<12xf32>' and 'tensor<1xi64>' are not broadcast compatible
LLVM ERROR: Failed to infer result type(s).

I also checked the PyTorch version and that MPS was available:
COMMAND
python -c "import torch; import math; print('PyTorch version: '+torch.version); print('MPS available: '+str(torch.backends.mps.is_available())); print('MPS built in PyTorch: '+str(torch.backends.mps.is_built()))"
OUTPUT
PyTorch version: 1.13.0.dev20220919
MPS available: True
MPS built in PyTorch: True

I got the same issue with PyTorch 1.2.1 on an M1 Pro.
I switched to PyTorch Nightlies : torch-1.14.0.dev20221007
Launching python main.py, it stalled without any error message a few seconds after "INFO:root:100 residues in this chain."
So not really working on this platform...

I have the same issue on my MacBook Pro 14 M1 Max. Torch version is 1.14.0.dev20221017.
% python main.py ~/Downloads/rcsb_pdb_1FSD.fasta ~/Downloads/1FSD_output
INFO:root:Loading weights from /Users/pavel/.cache/omegafold_ckpt/model.pt
INFO:root:Constructing OmegaFold
INFO:root:Reading /Users/pavel/Downloads/rcsb_pdb_1FSD.fasta
INFO:root:Predicting 1th chain in /Users/pavel/Downloads/rcsb_pdb_1FSD.fasta
INFO:root:28 residues in this chain.
loc("mps_multiply"("(mpsFileLoc): /AppleInternal/Library/BuildRoots/a0876c02-1788-11ed-b9c4-96898e02b808/Library/Caches/com.apple.xbs/Sources/MetalPerformanceShadersGraph/mpsgraph/MetalPerformanceShadersGraph/Core/Files/MPSGraphUtilities.mm":219:0)): error: input types 'tensor<12xf32>' and 'tensor<1xi64>' are not broadcast compatible
LLVM ERROR: Failed to infer result type(s).
[1]    81569 abort      python main.py ~/Downloads/rcsb_pdb_1FSD.fasta ~/Downloads/1FSD_output


Variable Ordinals

Fix for functions that return strings (or memory pointers) to return unique values for each returned value within a single execution loop
Ordinals Reset to 0 on each execution loop, allowing for memory to be reused

Verified that there are only two methods missing unit tests: scanmsg and rawmsg
Upon further investigation, the current scanmsg implementation is incorrect. We only support reading from a MSG file loaded (and defined) in the current module MDF, but the documentation states it should be ANY MSG file.
So we'll need to correct that, I'll open a defect.


Alignment / variant calling pipeline gets stuck in VARIANT_CALLING hwen FREEBAYES_PARALLEL = True and aligning more than one ExperimentSample

Fixed in 8dd9801af62c588dedd8735f4acc2b2e4c2cdf7c. Although we may have to be careful with always requiring at least 2 celery workers else risk deadlock.


Check state file for CNI IP and error

Goes hand-in-hand with https://github.com/rancher/plugin-manager/pull/44
Look for CNI IP and error in a state file. If it is there, don't  try to get the IP by entering the network namespace. This let's us do a few things:

For rancher-vm, we don't have to worry about the vm startup script removing the IP from the containers interface
For normal containers whose CNI networking fails, we can fail faster instead of waiting for getting the IP to timeout
We can now report detailed error messages from the network-manager up to the user instead of the generic "Timeout waiting for IP" message we currently send.

@StrongMonkey I didn't even think to look at the windows logic until just now. Do we 1) use CNI plugins for windows containers 2) have similar "look inside the container" logic for Windows?

@cjellick i don't think we use cni plugin for windows container(probably in the future). The getIp method in windows is here https://github.com/rancher/agent/blob/master/utilities/utils/response_windows.go#L17.


Convert PosgreSQL "query_canceled" errors into context errors.

Fixes #35.

Tests that cover these changes are added in #77.


Implement Cleaner Updates to XML

Specifically with cheerio's updates to the api.xsp for xsp:rest.

Maybe just targeting a formatter would preclude the silliness. Something like prettier, which has both a cli tool and an API should work, as they've made strides in supporting HTML. I assume this would work for XML.
https://github.com/prettier/prettier/issues/1882


feature: add auto format on save

Please add auto format on save. To implement this feature, attach event listener on [vscode.workspace.onDidSaveTextDocument]
Thanks.

Good idea! If you have time, you can send a PR or wait until tomorrow (UTC +3 Moscow).
P.S.: Need option in preferences: autoFormatOnSave (enabled by default).

sorry, the next time I got free time for fun coding is next weekend.
if you want to look up some code, I know 2 implentations with this feature: beautify or my own vscode-tidyhtml (but typescript)

Done. Please, checkout the new version of CSScomb plugin.
F1 → ext → Extensions: Show Outdated Extensions -> Update CSScomb plugin

--
Thanks for issue. :+1:

I tested the feature and it is working for css files. But I am using less files and these files gets deleted. I will create a new issue, because it also happens on command call.


discovery openstack: handle instances without ip

openstack instance without ip still be target, error message:
ERRO[0000] creating targets failed                       err="instance 6 in group OS_RegionOne: no address" source="scrape.go:216"
Signed-off-by: CuiHaozhi<EMAIL_ADDRESS>

@fabxc @brian-brazil  PTAL

Thanks. Can we add a test for that?

@fabxc Thanks for review, test added
but CI said
--- FAIL: TestFileSD (15.60s) 	file_test.go:83: Expected new target group but got none FAIL FAIL	github.com/prometheus/prometheus/discovery/file	15.642s

@fabxc  CI  Passed today  : )
could you please take another look?

👍


How to calculate FID in BFR task?

Hi, thanks for your wonderful work which inspires us so much. However, we wonder how to calculate the FID metric in your paper. In other word, which reference dataset did you choose when computing the results' FID. We reproduct your results which are visually amazing but cannot achieve the FID around 20 in your paper.

Thank you for your prompt response! I have another question regarding the FID library you utilized. I've noticed that many projects focusing on image restoration tasks often employ the pytorch-fid repository for calculating FID. Could you please confirm whether you also used this library, either with default settings or any other codes?
I'm eager to replicate your methodology, and aligning with your quantitative metrics is my initial step. Your understanding is greatly appreciated! : )

We use pytorch-fid to calculate FID :)

A follow-up question, if I may – which layer of the inception network did you use?
As both LFW and WIDER have less than 2048 images, we cannot compute FID using the default layer (as mentioned here: https://github.com/mseitzer/pytorch-fid?tab=readme-ov-file#using-different-layers-for-feature-maps).


export sce from python

hello, the package is very cool to convert annadata into sce format. May i ask a question, please? How do i export the sce object to be able to load into R? Thanks a lot.

Currently there's not a straight forward way of doing this. One can read an RDS file using rds2py from R to Python.
I've been thinking of implementing language agnostic representations for datasets so that they can be read from any language. Hopefully that will come soon. but right now, may be write to H5AD then read it in R?


chore(main): release 0.1.3

:robot: I have created a release beep boop
0.1.3 (2023-10-07)
Bug Fixes

Maven Central (#24) (95bbe34)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/sverrehu/k3a-embedded/releases/tag/v0.1.3 :sunflower:


a question about data augmentation

Hello everybody,
I want to ask you about the example binary segmentation (camvid), how does data augmentation with albumentation work exactly? does it generate a new batch of images each step in the training ?
My dataset is very small, it contains 40 images for training and 10 images for validation. should i use this type of data augmentation or generate more images and save them to a directory and then do the training.
I will be grateful if you can help me or give a hint about how to proceed.

closed


Server startup error related to throttle policy deployment

Description
Getting this error during pack startup (can be seen in all the profiles as well as in the all-in-one pack).
[2022-07-22 09:17:20,931] ERROR - APIUtil Error occurred while trying to retrieve the event publisher for type: NOTIFICATION
[2022-07-22 09:17:20,933] ERROR - APIUtil Error occurred while trying to retrieve the event publisher for type: NOTIFICATION
[2022-07-22 09:17:20,934] ERROR - APIUtil Error occurred while trying to retrieve the event publisher for type: NOTIFICATION
[2022-07-22 09:17:20,938] ERROR - APIUtil Error occurred while trying to retrieve the event publisher for type: NOTIFICATION
[2022-07-22 09:17:20,940] ERROR - APIUtil Error occurred while trying to retrieve the event publisher for type: NOTIFICATION
[2022-07-22 09:17:20,941] ERROR - APIUtil Error occurred while trying to retrieve the event publisher for type: NOTIFICATION
[2022-07-22 09:17:20,944] ERROR - APIUtil Error occurred while trying to retrieve the event publisher for type: NOTIFICATION
[2022-07-22 09:17:20,951] ERROR - APIUtil Error occurred while trying to retrieve the event publisher for type: NOTIFICATION
[2022-07-22 09:17:20,952] ERROR - APIUtil Error occurred while trying to retrieve the event publisher for type: NOTIFICATION
[2022-07-22 09:17:20,953] ERROR - APIUtil Error occurred while trying to retrieve the event publisher for type: NOTIFICATION
[2022-07-22 09:17:21,261]  INFO - SessionDataStore Thread pool size for temporary authentication context data delete task: 20

There is no functionality issue, but the error log should not be there.
Steps to Reproduce
Issue occurs at server startup for update levels from 9 (<IP_ADDRESS>) onwards
Affected Component
APIM
Version
4.1.0
Environment Details (with versions)
No response
Relevant Log Output
No response
Related Issues
No response
Suggested Labels
No response

Closing this issue as per the comment in the linked internal ticket.


react-use doesn't support webpack 5 tree shaking

What is the current behavior?
I installed react-use and only imported one hook:
import { useLocalStorage } from 'react-use';

But the build result bundled all hooks:

What is the expected behavior?
react-use should support webpack 5 tree shaking and only bundle useLocalStorage.js and depended modules.
A little about versions:

OS:
Browser (vendor and version):
React:
react-use:
Did this worked in the previous package version?

Are you shure?

@guoyunhe By looking at the folder structure for the installed package it looks like we can import the individual functions directly like this:
import useLocalStorage from 'react-use/lib/useLocalStorage';

Although I am not sure if this is the right way to this


⚠ Quirk Club Argentina (API endpoint) has degraded performance

In 85bb962, Quirk Club Argentina (API endpoint) (https://us-central1-quirkclub-dev.cloudfunctions.net/api/check/api) experienced degraded performance:

HTTP code: 200
Response time: 10281 ms

Resolved: Quirk Club Argentina (API endpoint) performance has improved in c133c63.


IPropertyBag not support JSON.stringify in V8

I want to pass a C# object to JS, when I used IPropertyBag, I found that when I use JSON.stringify in JS, it will return "{}" json string, how should I assign a C# object to JS?

Hi @feiyin0719,
Please clarify. Do you need to use the C# object on the JavaScript side, or do you just need its JSON representation? Or both?
Thanks!

I need both

I need to use C# object use in JavaScript side , and can use  JSON.stringify to serialization the c# object in JavaScript side

ok, I will try it, thanks

yes, This solves the problem, but can we provide a way to make c# objects work like javascript objects? For example, the JSI(JavaScript interface) in React Native. I have tried to provide an object implement the getPropertyNames, hasOwnProperty method, but it cannot work. I think this can make the communication between c# and javascript more convenient

Hi @feiyin0719,

This solves the problem, but can we provide a way to make c# objects work like javascript objects in JS? For example, the JSI(JavaScript interface) in React Native.

One of ClearScript's main goals is to allow script code to access .NET objects and types without special coding. There's no need to implement getPropertyNames – or any such method – when you can simply do this:
// use a .NET object in script code
engine.AddHostObject("myObj", new MyClass());
engine.Execute("myObj.MyMethod()");

// use a .NET type in script code
engine.AddHostType(typeof(MyClass));
engine.Execute(@"
    const myObj = new MyClass();
    myObj.MyMethod();
");

.NET and JavaScript have radically different type systems, so .NET objects can't always behave exactly like script objects. but ClearScript tries to provide convenient access. If the result isn't sufficiently "JavaScript-like", you can always hide ClearScript's .NET objects within pure JavaScript wrappers:
dynamic setup = engine.Evaluate(@"(function (myClrObject) {
    globalThis.MyJsObject = {
        myMethod: () => myClrObject.MyMethod()
    }
})");
setup(new MyClass());
engine.Execute("MyJsObject.myMethod()");

This approach should yield much better performance than handling low-level JavaScript operations in .NET.
Cheers!

ok, I got it, but if I want to use some js lib,It will be a little more cumbersome to deal with

Hello @feiyin0719,

if I want to use some js lib,It will be a little more cumbersome to deal with

Unfortunately, it seems like most JavaScript libraries out there assume either a web browser or Node.js environment, requiring modifications to work correctly in a bare JavaScript setting.
Our hope is that, by providing easy access to .NET objects from script code, and vice versa, ClearScript enables you to construct whatever script API you require with the least amount of work.
The ability to serialize host objects via JSON.stringify is a frequent request, so we'll keep this issue open and look into improving support for that in a future release. If you encounter other specific obstacles, please create a new issue and let us know.
Thanks!


Struggling to setup a private repository

All,
I have setup a private repository using local storage:
I have then started the service running.
On another machine I then build and tag a container:
docker tag <tag_num> docker-registry.DOMAIN/jenkins_slave
I then try and push to the registry:
sudo docker push docker-registry.DOMAIN/jenkins_slave
The push refers to a repository [docker-registry.DOMAIN/jenkins_slave](len: 1)
Sending image list
But thats it - I dont see anything else (like it actually pushing).
I have looked on the server and the logs show absolutely nothing - even with debug enabled.
I have obviously missed a really silly step out - but any help appreciated in debugging this?
Cheers
Dan

@chewmanfoo How did you get around the mcafee firewall problem ? I am also observing "Error: Status 502 trying to push repository " issue. Can you please help.


Sample code for testing windows desktop app

From: https://github.com/appium/sample-code/issues/162
How is the app value for calculated here? How to get that value for 3rd party windows desktop apps?
I am trying to run a windows desktop app with appium, I tried giving it full path to exe file which also didn't work.

Hi @ChillarAnand,
When you are testing your own UWP application wit the source code available, you can simply get the app value from AppX\vs.appxrecipe file under RegisteredUserModeAppID entry.
If you don't have the source code, you may also run Get-AppxPackages in PowerShell and try to deduce the value yourself.


is it possible to use 'share to web' toggle through notion-py?

if not, can this function be added?

settingValue = {
        "role": "reader", **# Enter the permissions you want to assign** none: [share to web] off / reader: [share to web] on
        "type":"public_permission"
    }
    try:
        client.get_block("12345678-1234-1234-1234-123456789012").set("permissions",[settingValue])

Thank you! It worked well!


Created a logo for boss-validator

Added the PNG to the root directory
Added logo to README
Fixed title in the README

Closing this PR in favor of #24


1653: Add intro slides with stores and disclaimer

Short description
Added screenshots with initials stores to intro slides
Added disclaimer text
Fixes: #1653

@ztefanie
did you check if the correct font is used in the screenshots?
You can also create screenshots from my open pr
Even not sure if anyone will notice that

@ztefanie did you check if the correct font is used in the screenshots? You can also create screenshots from my open pr Even not sure if anyone will notice that

i think it is good enough for now, we can still update this, especially if more stores are published

@ztefanie
I think in the finalization ticket is the applicationUrl missing
To avoid creating a separate task for adjusting a string could you please provide
 applicationUrl: "https://koblenz.sozialpass.app/erstellen" in the buildConfig


How to prevent gradient exploding?

Thank you for your contributions!
It seems that the Correlation operation leads to huge gradients. As the paper says that your init_lr is 1e-2. Can you tell me the parameter initialization you use? Is the xavier OK for this, or can you share other tricks to avoid gradient exploding?

Thank you for your contributions!
It seems that the Correlation operation leads to huge gradients. As the paper says that your init_lr is 1e-2. Can you tell me the parameter initialization you use? Is the xavier OK for this, or can you share other tricks to avoid gradient exploding?

in my experiment, normal distribution with delta 0.005 is able to avoid NAN, for correlation operation,  siamfc also uses a conv layer init with 1e-3 to scale the output correlation map, i do not know the solution of the author, by the way, the pre-trained model may do some favor to the performance, and lr warm-up is worthy to try.


经常遇到连接失败的提示

配置了key和socks5代理,不知道为什么有大概率会遇到下面的错误.
用过另外一个叫GptCli的程序,那个设置了代理后连接问答就很稳定.
aichat 写一个计算pi的c#程序

Error: Failed to fetch stream

Caused by:
    0: error sending request for url (https://api.openai.com/v1/chat/completions): error trying to connect: operation timed out
    1: error trying to connect: operation timed out
    2: operation timed out

AICHAT has a 10-second connection timeout. If the API cannot be connected within 10 seconds, this error will be reported.
Your problem is caused by bad internet connection.
AICHAT may allow config longer timeouts in the future.


include error

problem:
"g++ -I/usr/local/include/nacos/"
I think we should put all header files in nacos directory.

+1, 这项目实现的太垃圾了，完全就是个demo


DomainEntity_EmailUrlInfo TI detection creates memory issues on large data sets

KQL Query for DomainEntity_EmailUrlInfo is not optimized for larger data sets leading to memory issues in LAW.
Source- https://github.com/Azure/Azure-Sentinel/blob/master/Solutions/Threat Intelligence/Analytic Rules/DomainEntity_EmailUrlInfo.yaml
To Reproduce
Run Existing query against data set that is TB a day in email traffic. Analysts will get excessive memory alerts and in cases for larger deployments
SEM00023 errors as materialize exceeds the limit and fails the query.

Expected behavior
Utilize improved query performance by dropping materialize and split data up more to improve performance.
Here is a fix which improves overall performance of query by over 90 percent on same data sets with same results.
https://github.com/MSJosh/documentation/blob/main/Sentinel/Misc. KQL/TI/DomainEntity_EmailUrlInfo.yaml

Hi @MSJosh ,  thanks for flagging this issue, we will investigate this issue and get back to you with some updates. Thanks!


Fix execute rpc async

Fixes https://github.com/chkr1011/MQTTnet/issues/1093.

Closed as this is already done in the master.


No release for version 9.3.0 and 9.3.1 in GitHub

From what I can see in the GitHub tags the latest tag is v9.3.1, but in the releases there is only a release for the RC of version v9.3.1. This is also the case for v9.3.0.
Because of this, we don't get the new symbols, upgrade, install and deploy ZIP-files.
Also the download link on the website (https://www.dnnsoftware.com/community/download) redirects to the lastest version, which is version v9.2.2 because both v9.3.0 and v9.3.1 are pre-releases.
Is there any reason why we don't get releases anymore for full releases and only tags?

We are currently in the process of getting v9.3.1 released as a production build, hopefully it will be released today. Recently we have changed the release process to include release candidates with a defined testing window for each release. The v9.3.0 release went through 8 weeks of RC test cycles, and unfortunately hours after it was released, a few issues related to an incomplete upgrade were reported. We made the decision to pull the v9.3.0 release, while quickly turning out a fix and getting a new RC out labeled v9.3.1.
If you have the ability to safely test the release candidates, it will help us deliver issues that might not be caught during our internal testing cycles. Each issue found, we update our processes to make the next build even better.

I see. It's a little confusing that the tag v9.3.0 and v9.3.1 exists. Because of this I thought they were released and public available. But it's clear now. I'll rely on releases instead of tags.


links in the site's flags dropdown are absolute

Steps to reproduce:

build the site locally
go to Getting Started
click on the Languages dropdown, then click on any flag

The browser is redirected to the https://angular-translate.github.io/docs/... guide page for that language, not to the local one.
This makes difficult testing improvements to the website, as one has to manually edit the URL in order to access the language's pages.

@gonzalo-roberto-diaz  Thanks for reporting, I've fixed that one. Will be available after next release.


WIP: Rebase BuildStrategy

(This is a precursor to a full EP on the topic, to get ideas out and start discussion)
In a "rebase" operation, an original image's base image layers are swapped out with another set of layers from another image.
Users might want to do this for a couple reasons:

if a vulnerability is found in a base image, you can replace those layers in an application image simply using registry API operations, and not have to rebuild the image from scratch on top of the new image. This can be especially useful if you need to quickly produce lots of images where the vulnerability is fixed, or if you no longer have access to the original source.
if you'd prefer to have another image as the base image; for example, an image is built on a large-ish image, and you'd prefer to have it based on a slimmer image like ubi or openjdk-slim, etc.

(the second case, producing slimmer built images, seems to be a motivating use case for runtime config)
In either case, rebasing is not guaranteed to be safe by default, and care must be taken when building to ensure your application code can handle being rebased onto other base images. Rebasing onto a base image with different versions of system libraries or installed runtimes might produce an image that can't execute. Rebased images should still be subjected to tests before being deployed to production. Buildpacks for example takes care to separate application layers from base image layers, so that rebasing is more likely to be successful.
To enable rebasing in Shipwright, we could define a new rebase BuildStrategy, which would expect an input image, and parameters for old- and new-base images (or could expect this to be stored in OCI image annotations on the image), and an output of where to publish the newly rebased image. (As an alternative, we could define a new Rebase CRD alongside Build, since they're fairly separate operations, I'm not sure that's necessary though, and a BuildStrategy is easier to iterate on)
When BuildRuns are triggered, rebasing builds could watch for updates to a base image and automatically produce rebased images built on that new base image.
References:

Buildpacks Rebase
crane rebase documentation
OCI spec proposal for base image annotations

cc @sbose78

Good topic, Jason!
Actually, we also care about that because we run the Build on our official environment. And we care about the first case very much.
My two cents:

I would like to think about this scenario from our end-user experience. On our UI, or even on the OpenShift operator UI, the user needs to create a build then submit a buildrun to do the build execution. The build should be a template that stores the initial settings, but the rebase should be a kind of execution level request, not the definition request. If the end user wants to rebase its image, I am thinking if the buildrun is a better place to have a new Rebase section, like:

---
apiVersion: shipwright.io/v1alpha1
kind: BuildRun
metadata:
  name: buildpack-nodejs-buildrun
spec:
  buildRef:
    name: buildpack-nodejs-build
  serviceAccount:
    generate: true
  rebase:
    registry.access.redhat.com/ubi8-minimal

The second thing is about Kaniko or other buildstrategies, I think the buildpacks can be done easily. But I think it is not easy to define the Rebase for the Dockerfile build, because the base image is defined and controlled in the Dockerfile, and without the kaniko build process, I am not sure how to ensure the image is rebased correctly.

So when we were thinking about this requirement before, we just think of buildpacks first. But I think it is a good topic, we can think about that together :)

Thanks for your response!
I had imagined this being phrased as another type of parameterized BuildStrategy, but one that didn't require any source input, only an image to rebase.
apiVersion: shipwright.io/v1alpha1
kind: Build
metadata:
  name: rebase
spec:
  inputs:
  - name: image
    type: Image
    value: gcr.io/my/image
  strategy:
    name: rebase
    params:
      old_base: ubuntu
      new_base: registry.access.redhat.com/ubi8-minimal

(This assumes parameterized strategies and Adam's inputs EP land)
Then you could run this any number of times as new gcr.io/my/images get built, or if new ubi8-minimal images get published. If neither of those images change, you could run it over and over and it would just be a no-op.
The real reason I want this as a Build instead of a configuration of a BuildRun is that I want to be able to trigger these automatically when base images change.
I think you're describing another feature where Builds (or Runs?) can immediately rewrite the base image of images they produce, sort of like how runtime images work today, but purposefully scoped down (which I support!). I think we could live with both features, but for this issue I'm more interested in the first.

The second thing is about Kaniko or other buildstrategies, I think the buildpacks can be done easily. But I think it is not easy to define the Rebase for the Dockerfile build, because the base image is defined and controlled in the Dockerfile, and without the kaniko build process, I am not sure how to ensure the image is rebased correctly.

Yeah, Dockerfile builds are less likely to be safe in every case, but if someone knows it's safe there's no reason to disallow it. Once the standard annotations are in, it shouldn't be hard to make Kaniko write those at least, so you won't need params in most cases.

Hi Jason,

I had imagined this being phrased as another type of parameterized BuildStrategy, but one that didn't require any source input, only an image to rebase.

If it is a new Build which is based on the rebase strategy, that is why I was thinking the user experience, for example, the user can create and show the build list from UI or CLI and know what is his build, but if there are some rebase build, I am thinking people may feel confusing and don't know the relationship between the original build and this rebase build. And I don't know if it is can be shown and used well from UX perspective.
And I agree auto-trigger and one-time base image rebase are two different features :)
I thought this issue is related to one-time base image rebase, but if it is related to the auto-trigger, I think it is more complex and we should have a better design with trigger together. :)
When I compare with other Build services, like OpenShift Build v1 or Google/AWS Build (I forget which one...), the trigger related config is integrated in the Build Config:
This is the OpenShift Build v1 page:

So if for trigger, I am thinking if we can introduce a new trigger-related CRD and link it to the original Build, Or have a new property inside of the Build directly? I think it should be a more consistent user experience. :)

Yeah, Dockerfile builds are less likely to be safe in every case, but if someone knows it's safe there's no reason to disallow it. Once the standard annotations are in, it shouldn't be hard to make Kaniko write those at least, so you won't need params in most cases.

Sure thing, it is better that we support this on multiple build strategies.

I'd like to be really careful not to expand the scope of this to include triggering. That's a separate EP entirely, which should be designed in isolation in such a way that rebuilds or rebases both work equally well. I'd like us to design that too, but separately from supporting rebasing.
Rebasing will be supported as a one-time operation for now (just as one-time build runs are supported now), but which can be triggered in the future. I like to think of it as just another kind of BuildStrategy which can be requested and run, or (in the future) triggered.
It's possible a user would want to request a build from source, then as a followup operation, request a rebase of that resulting image on top of another image. That use case is supported today using runtime images, but I think that's a bit overly complex for this use case (it supports adding copy, run, etc., directives), and can possibly lose information about the original base image. I'd like to understand that use case a bit more as part of producing an EP for this work.

I'd like to be really careful not to expand the scope of this to include triggering.

Agree.

Rebasing will be supported as a one-time operation for now (just as one-time build runs are supported now), but which can be triggered in the future. I like to think of it as just another kind of BuildStrategy which can be requested and run, or (in the future) triggered.

If it is supported as a one-time operation for now but can be triggered in the future, so it also related to trigger, so I think we should be careful and have a better design also for future feature integration.
I totally agree this is a valid scenario we should support. I am just thinking for this kind of requirement, if a new rebase BuildStrategy then a new rebase Build is good from the UX perspective.

I totally agree this is a valid scenario we should support. I am just thinking for this kind of requirement, if a new rebase BuildStrategy then a new rebase Build is good from the UX perspective.

The reason a rebase BuildStrategy is attractive to me is that it doesn't require any (more) changes to the API to support it. It's just another BuildStrategy with sort of odd semantics. We can modify the definition until we're happy with it, and users can provide their own or uninstall rebase support if they want to. Then if we decide it's a common enough and well-understood-enough concept, we can decide whether we want to promote it as a first-class concept alongside Build.

My two cents so far are:

We need to have a good understanding on how such rebase strategy will look. For example:

If for Buildpacks, we need to check if their binaries can provide us already the pack rebase as mentioned in their docs. If this is the case, users might only require to choose an strategy name without any further new parameters.
If for Kaniko, if Kaniko provides support for this, or if we need to develop some glue code. For Kaniko I do see the need of new parameters in our API.

API wise, I like both ideas. I think Jason´s one is related to this thread https://kubernetes.slack.com/archives/C019ZRGUEJC/p1615387780007200 . I think Jordan proposal is good in the sense that you do not need a new Build only for rebase, you could use an existing one and just trigger a new BuildRun with the purpose of rebase.
I´m confused on the overlap with the runtime feature. I see this as a replacement of the runtime feature which I think it would be for the better. Is this the case?

I would agree with @qu1queee that while both the @ImJasonH and @zhangtbj ideas introduced here share a common goal of helping to "trim images" or "make them leaner" as is cited in https://github.com/shipwright-io/build/blob/master/docs/proposals/runtime-image.md they in fact they do not overlap so much in the scenarios they are addressing.  I'm also not 100% sure @ImJasonH was suggesting that, but I think it helps to explicitly confirm that the commonality most likely stops at the shared goal.
I'm possibly oversimplifying, but from what I've read, rebase seems to == replace layers, where as the https://github.com/shipwright-io/build/blob/master/docs/proposals/runtime-image.md == minimize the size of the layers you add on top of the existing layers
I also think of https://github.com/shipwright-io/build/blob/master/docs/proposals/runtime-image.md as having some sub-goals of

providing an API that facilitates the multi-stage docker builds pattern when it is available, but not impose it when it is not
pulling in a popular semantic that OpenShift Builds provided for pulling in content from other images before multi-stage docker builds existed, namely https://docs.openshift.com/container-platform/4.7/cicd/builds/creating-build-inputs.html#builds-image-source_creating-build-inputs maps

But I'm of course curious as to what @sbose78 and @otaviof as the authors of the EP think, and if they share my recollections / inferences.
https://github.com/shipwright-io/build/blob/master/docs/proposals/runtime-image.md also bleeds into what could be included in sources or inputs or however we want to organize the "multiple content inputs" into building an image.  Some of that is captured in @adambkaplan 's https://github.com/shipwright-io/build/issues/544
With all that ^^,  I'm however not sure @ImJasonH and/or @zhangtbj ideas here are a replacement for https://github.com/shipwright-io/build/blob/master/docs/proposals/runtime-image.md
However, I think I could see some form of both proving complementary and useful to users.

I'm also not 100% sure @ImJasonH was suggesting that, but I think it helps to explicitly confirm that the commonality most likely stops at the shared goal.

I am explicitly not interested in adding image-slimming functionality to the core Shipwright API; that's something that can already be expressed better in a Dockerfile or buildpacks, and those features and communities are far more established and moving faster, so we'll never catch up.
I'd like to deprecate and phase out runtime-image, and I believe it should be relatively straightforward to do today since (we think) it has relatively little use.

[runtime image has a sub-goal of]

pulling in a popular semantic that OpenShift Builds provided for pulling in content from other images before multi-stage docker builds existed, namely https://docs.openshift.com/container-platform/4.7/cicd/builds/creating-build-inputs.html#builds-image-source_creating-build-inputs maps

Multi-stage docker builds do exist today though, and I think there's far more understanding and support for them now. I don't think this is a feature of OpenShift Builds we need to carry over to Shipwright.

If for Buildpacks, we need to check if their binaries can provide us already the pack rebase as mentioned in their docs. If this is the case, users might only require to choose an strategy name without any further new parameters.
If for Kaniko, if Kaniko provides support for this, or if we need to develop some glue code. For Kaniko I do see the need of new parameters in our API.

Rebasing doesn't require pack rebase, and doesn't require (much, if any) new glue code to be written. pack rebase uses code in go-containerregistry's mutate.Rebase (that I wrote, incidentally) to reassemble layers efficiently. We can reuse that logic, either by repackaging it in our own code, or by having a BuildStrategy that calls crane rebase (that I also wrote, and am improving now).
mutate.Rebase and crane rebase both work against any image, however it was built. If it was built with a tool that's rebase-aware, it can rely on hints baked into the image to make rebasing even easier.

I´m confused on the overlap with the runtime feature. I see this as a replacement of the runtime feature which I think it would be for the better. Is this the case?. To be more precise, rebase applies to both Dockerfile-less and Dockerfile-based strategies, while runtime is really only for Dockerfile-based.

I'd like to deprecate and phase out runtime whether or not or however rebase is included, full stop. Some of the functionality can be simulated with rebase, but I think they solve different problems.

I'm also not 100% sure @ImJasonH was suggesting that, but I think it helps to explicitly confirm that the commonality most likely stops at the shared goal.

I am explicitly not interested in adding image-slimming functionality to the core Shipwright API; that's something that can already be expressed better in a Dockerfile or buildpacks, and those features and communities are far more established and moving faster, so we'll never catch up.
I'd like to deprecate and phase out runtime-image, and I believe it should be relatively straightforward to do today since (we think) it has relatively little use.

[runtime image has a sub-goal of]

pulling in a popular semantic that OpenShift Builds provided for pulling in content from other images before multi-stage docker builds existed, namely https://docs.openshift.com/container-platform/4.7/cicd/builds/creating-build-inputs.html#builds-image-source_creating-build-inputs maps

Multi-stage docker builds do exist today though, and I think there's far more understanding and support for them now. I don't think this is a feature of OpenShift Builds we need to carry over to Shipwright.

Yep I'm OK with that.  I was mostly trying to convey background and context.  And in this particular case, explaining how to move from our old thing to the new thing should not be difficult.  And I have not heard / cannot think of why a user would be inclined to express the desire to copy a subset of content from an image via k8s types and yaml instead of Dockerfile commands, or any analogous functionality across the spectrum of image building tools (present or future).

If for Buildpacks, we need to check if their binaries can provide us already the pack rebase as mentioned in their docs. If this is the case, users might only require to choose an strategy name without any further new parameters.
If for Kaniko, if Kaniko provides support for this, or if we need to develop some glue code. For Kaniko I do see the need of new parameters in our API.

Rebasing doesn't require pack rebase, and doesn't require (much, if any) new glue code to be written. pack rebase uses code in go-containerregistry's mutate.Rebase (that I wrote, incidentally) to reassemble layers efficiently. We can reuse that logic, either by repackaging it in our own code, or by having a BuildStrategy that calls crane rebase (that I also wrote, and am improving now).
mutate.Rebase and crane rebase both work against any image, however it was built. If it was built with a tool that's rebase-aware, it can rely on hints baked into the image to make rebasing even easier.

I´m confused on the overlap with the runtime feature. I see this as a replacement of the runtime feature which I think it would be for the better. Is this the case?. To be more precise, rebase applies to both Dockerfile-less and Dockerfile-based strategies, while runtime is really only for Dockerfile-based.

I'd like to deprecate and phase out runtime whether or not or however rebase is included, full stop. Some of the functionality can be simulated with rebase, but I think they solve different problems.

Yes, I think the alternative to the runtime feature is a user Dockerfile that follows the multi-stage best practices.
@ImJasonH for the rebase strategy and merely speaking about buildpacks, one needs to do a rebase of the run image ( illustration in docs ), if you translate this to the crane rebase cmd, the old/new base needs to be the run image, which is an existing layer on your app image if you previously build with creator. So I´m wondering if for "buildpacks", instead of using crane we should stick to what the community buildpacks/lifecycle already provides, what do you think?
Or are you saying that in general for any rebase strategy, we should have a single step that uses an standard tooling/mechanism, like crane?

Or are you saying that in general for any rebase strategy, we should have a single step that uses an standard tooling/mechanism, like crane?

Using pack rebase would only work to rebase images produced by buildpacks (AFAIK), since it relies on base image information in image annotations.
crane rebase would be capable of rebasing any image, either by requiring users to explicitly specify base image information, or using a standard annotation, which buildpacks should also set.

Using pack rebase would only work to rebase images produced by buildpacks (AFAIK), since it relies on base image information in image annotations.

yes, thats my understanding. I still think we should also have a pack rebase strategy, while we already have a pack build strategy for building. Maybe something to consider as alternatives in your upcoming EP. I think having the pack rebase is convenient, while our default Dockerfile-less  strategy is paketo (cloud native buildpack implementation).


Page info: empty date should say "never"

Regression from #256
Expected output:

Actual output:

:tada: This issue has been resolved in version 6.12.1 :tada:
The release is available on:

GitHub release
v6.12.1

Your semantic-release bot :package::rocket:


[wip]fix: failing backup and restore appsmithctl

Description

[!TIP]
Add a TL;DR when the description is longer than 500 words or extremely technical (helps the content, marketing, and DevRel team).
Please also include relevant motivation and context. List any dependencies that are required for this change. Add links to Notion, Figma or any other documents that might be relevant to the PR.

Fixes #Issue Number
or
Fixes Issue URL

[!WARNING]
If no issue exists, please create an issue first, and check with the maintainers if the issue is valid.

Automation
/ok-to-test tags=""
:mag: Cypress test results

[!CAUTION]
If you modify the content in this section, you are likely to disrupt the CI result for your PR.

Communication
Should the DevRel and Marketing teams inform users about this change?

[ ] Yes
[ ] No

Summary by CodeRabbit

New Features

Introduced a new utility function to dynamically retrieve the database URL from environment variables and a specified configuration file.
Added a constant for the Docker environment configuration path to improve configuration management.

Enhancements

Updated the restore process to allow for flexible database URL handling, improving adaptability for different database connections.
Enhanced database URL retrieval methods in multiple functions for improved maintainability and consistency.

/build-deploy-preview skip-tests=true

/build-deploy-preview skip-tests=true


Update pipeline to run tests twice, with different versions of TSM

[X] This contribution adheres to CONTRIBUTING.md.

What does this Pull Request accomplish?
Update test running pipeline to run the automated tests twice: once with the latest released version of TSM and once with the next-to-latest released version of TSM. Each test run produces a different set of results files. Both sets are published in the PublishTestResults@2 task of the pipeline.
Why should this Pull Request be merged?
Increases reliability of the automated tests
What testing has been done?

Ensured that the testing VM configuration was correctly updated (those changes belong to the ni-central repo and so are not included in this PR).
Ensured that the changes made to the pipeline work as expected with a stubbed version of the Activate_TSVersion.ps1 script (the reason we use a stub is because the VM configuration changes aren't yet final, and so the VM isn't yet setup correctly. For this same reason, we will not complete this PR until those changes are final and the VM has been updated by the deployment pipeline, otherwise the automated tests pipeline would fail. These two PRs are mutually interdependent).
Tested that the changes made to pyproject.toml have the desired effect by invoking tox with a command line argument in the current VM.

[X] I have run the automated tests (required if there are code changes)

This looks pretty good, I just have a few questions.

Have you confirmed the clean environment doesn't delete any result/coverage files before the second run?

I did. The clean does not remove the result or the coverage files.

What happens if a user doesn't pass any positional arguments to tox?

If there is no argument, then {posargs} expands to blank. This would result in the results file being named py38-tests--tsm-version-results.xml, which isn't terrible but isn't great either. So I'm changing the variable to {posargs:any}, which would result in the file name being py38-tests-any-tsm-version-results.xml if an tsm version argument isn't specified.

Is there a way to use only a single positional argument instead of all of them?

I don't know that there is. I had looked for that too, but I didn't find anything in the documentation.

If there is no argument, then {posargs} expands to blank. This would result in the results file being named py38-tests--tsm-version-results.xml, which isn't terrible but isn't great either. So I'm changing the variable to {posargs:any}, which would result in the file name being py38-tests-any-tsm-version-results.xml if an tsm version argument isn't specified.

I like this idea

/azp run

FYI, we can't run the tests yet because the underlying VM hasn't yet been rebuilt to have the required versions of the software. That should happen next weekend if all goes well.


add responsive-font-size mixin to replace rfs's font-size

Task: task-437077
Removes rfs package in favor of an in house solution. Also, adds 1.6 line height within markdown to match Docs. Ideal for scaling is as follows:

A fluid scaling between the max and min.
Minimum values still allow for discernable differences between heading sizes, especially on h1-h4.
Relatively straightfoward outer api. @include responsive-font-size($max, $min).
No major "jumps" between scaled values and min and max.
OS font-size changes don't mess up anything.

Link: preview-228
https://design.docs.microsoft.com/pulls/228/components/markdown.html
Testing

Visit link above.
Resize window from wide (circa 1500px to small)
View on your mobile device.

Additional information
Testing a smaller paragraph font size on mobile worked fairly well too. Did not move forward with it, but it could be added with the following:
.markdown {
  	@include responsive-font-size($markdown-paragraph-size, 0.875rem); // experiment only
}

Did some testing with this version:
`${document.body.clientWidth}px ${window.getComputedStyle(document.querySelector('h1')).fontSize}`

@mixin responsive-font-size(
	// font-size to stop scaling at
	$end-rem,
	// font-size to start scaling from
	$start-rem: $end-rem * $font-size-scaling-factor,
	// viewport width to stop scaling at
	$end-vw: $breakpoint-tablet,
	// viewport width to start scaling from
	$start-vw: 576px
) {
	// how much do we need to scale the font-size?
	$rem-delta: strip-units($end-rem) - strip-units($start-rem);
	// over what distance are we scaling the font-size?
	$vw-delta: strip-units($end-vw) - strip-units($start-vw);
	// unit of scale
	$rate: math.div($rem-delta, $vw-delta) * 16;

	font-size: clamp(#{$start-rem}, #{$start-rem} + #{$rate} * (100vw - #{$start-vw}), #{$end-rem});
}

@mixin responsive-font-size(
	// font-size to stop scaling at
	$end-rem,
	// font-size to start scaling from
	$start-rem: max($end-rem * $font-size-scaling-factor, 1rem),
	// viewport width to stop scaling at
	$end-width: $breakpoint-desktop,
	// viewport width to start scaling from
	$start-width: 576px
) {
	$m: math.div(
			strip-units($end-rem) - strip-units($start-rem),
			strip-units($end-width) - strip-units($start-width)
		) * strip-units($document-font-size);

	$y: strip-units($start-rem) * strip-units($document-font-size);
	$x: strip-units($start-width);
	$b: $y - $m * $x;

	font-size: clamp(#{$start-rem}, #{$b}px + #{$m * 100}vw, #{$end-rem});
}