Unable to import pyodbc on Apple Silicon - Symbol not found: _SQLAllocHandle

Environment

Python: 3.8.2
pyodbc: 4.0.30
OS: macOS Big Sur 11.2.1
DB: Azure SQL DB
driver: Microsoft ODBC 17

Issue
Expected behaviour
After installing pyodbc on my 2021 MacBook Pro with Apple Silicon (built from source) natively without using Rosetta in a fresh new virtual environment I am able to import pyodbc.
Observed behaviour
After installing pyodbc I get the following exception when trying to import pyodbc:
  File "<stdin>", line 1, in <module>
ImportError: dlopen({myvenv}/lib/python3.8/site-packages/pyodbc.cpython-38-darwin.so, 2):
Symbol not found: _SQLAllocHandle
  Referenced from: {myvenv}/lib/python3.8/site-packages/pyodbc.cpython-38-darwin.so
  Expected in: flat namespace
 in {myvenv}/lib/python3.8/site-packages/pyodbc.cpython-38-darwin.so

If however, I install pyodbc in a fresh new virtual environment using Rosetta and try to import pyodbc everything works fine.
Is this an actual issue or am I missing something?

https://github.com/microsoft/homebrew-mssql-release/issues/53
No ARM Mac support yet.

It gonna be support ?

https://github.com/microsoft/homebrew-mssql-release/issues/53#issuecomment-805116754

Closing due to inactivity. Please re-open if new information is available.

For mac M1 you can use:
pip install --pre --no-binary :all: pyodbc
This compiles the binary locally and thus is compatible

For mac M1 you can use: pip install --pre --no-binary :all: pyodbc
This compiles the binary locally and thus is compatible

How would a poetry user do the same?

Thanks @vicagarcia 👍🏻

For mac M1 you can use: pip install --pre --no-binary :all: pyodbc
This compiles the binary locally and thus is compatible

Thanks. This did it for me.
For the sake of posterity:
brew tap microsoft/mssql-release https://github.com/Microsoft/homebrew-mssql-release
brew update
brew upgrade
HOMEBREW_ACCEPT_EULA=Y brew install msodbcsql18 mssql-tools18

pip3 install --pre --no-binary :all: pyodbc


.Net: Example71_AssistantDelegation - remove hard-coded model string

Example should use model defined in secrets, not hardcoded string.

Generally true, but this example has restricted model targets.  Adding comments.


Storybook: Candidate Card Component

User story
Who: As a developer
What: I want a Candidate Card component and List of Cards that allows displaying each candidate and List.
Why: so the user can easily vote for their choice
Acceptance criteria
Create a storybook component like the one highlighted in the image:

List of Cards

done


feat: 增加lb-demo版本号更新脚本

:tada: This PR is included in version 1.14.0-alpha.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on npm package (@latest dist-tag)
Your semantic-release bot :package::rocket:


Fix for Issue #4851

I didn't catch when my original documentation was changed by @fchollet (overall for the better) but introducing this bug: https://github.com/fchollet/keras/issues/4851
My original docs only included the dimensions of the parameters (no batch dim) and were correct, but I think its better to change the functions to reflect the current docs.
My original docs were:
shared_axes: the axes along with to share parameters for
                      the activation function. For example if the
                      incoming feature maps from a 2D convolution
                      has dimensions 16x32x32 and you wish to share
                      parameters across space so that each feature
                      maps only has one set of parameters, set
                      shared_axes = [1, 2]

Thanks for the review. PEP8 changes made!


168988636 dashboard header styling

Header Styling Changes
This is the fist pass at getting the header styling to match more closely with the design spec.
Style changes include:

A new dropdown menu for classes in the header.
A new dropdown for problems in the header.
A icon of a persons profile in the header.
A new toggle group interface for switching panels
An updated unit/investigation title in the header.

The components for the dropdown menu and the toggle group buttons were developed outside of Clue in a new repo called concord-react-components.  The components can be tested in isolation at: storybook.concord.org
See also:

Deploy Branch Demo
PT Story
ProtoType

@kswenson  -- I think 1ef5ae0 & e17dd45 addresses your requests.
There was a failing cypress test related to the number of groups currently active.  We discussed it in orange standup.  I adjusted the failing test in 9ab5b2b so it would pass accordingly.  I suspect other branches might also be making a similar change ... (possible merge conflicts ahead as we each try to get CI working)


Change default value of 'parse_to' to 'attributes'

Addresses one of two changes proposed in #431

Contrib test failure is due to a test that expects parsing results to be present in Body rather than Attributes.

@dmitryax, @tigrannajaryan, do you want to review this? It is a breaking change and currently only @pmm-sumo has written support on the proposal (#431). I think I recall hearing verbal agreement in last week's SIG, but want to make sure this is expected.

@djaglowski I will take a look, sorry for the delay.


Rocket framework research

Take framework apart to learn how they quickly throw up a site from scratch for a new user without burdening them with config files like .eleventy.js
Identify optimizations, features we could be using more effectively
Are there things here that we can learn from in our own 11ty based starter kit project?

Rocket: https://rocket.modern-web.dev/

Interesting framework.
My initial impression is that it's great if the out-of-the-box layouts, templates, and options serve a project's needs. However, I predict it could become as complicated as 11ty (if not worse) with too much customization.  My assessment here comes from Rocket's emphasis on their Presets concept for extending a site. Rocket's Presets could be a neat way to modularize different site functions. But it does require its own learning curve and Javascript overhead/boilerplate.
While browsing the code, I kept thinking, "It would be way easier to do X here, and Y over there, with 11ty version 1.0." Unlike Rocket, we have that luxury because we get to start from scratch.
So I took that inspiration, and did some experimentation. I think we could create something like a super-11ty-build-system which offers the following.

Includes all our default site templates, data, and components.
Provides 99% of the site's default settings.
Allows overrides of any data/templates via the project.
Still requires an .eleventy.js file, but it'd be under 10 lines of simple set-up.
All of the build tooling in the current 11ty-build-system.

This can be achieved through a combination of 11ty's setLibrary, addLayoutAlias, beforeBuild, and plugin architecture, combined with custom engines for Nunjucks and Markdown. That sounds like a lot, but it's not; I have a working prototype clocking at 30 LOC. I like the idea of providing a tool that's still 100% 11ty, just with all of our boilerplate/settings/templates totally abstracted out of our projects.

Nice @xjensen that sounds great
30 LOC?
Rocket was helpful getting the component gallery section up quickly but I am already doing a lot of overriding. Rocket also has helpful stuff like image optimization, a service worker. If we put these in our starter kit we can make the defaults fit our needs better.
It would be great to swap this out for our own starter kit so we can improve that while we work on this project.

I was referring to a small prototype I put together when mentioning the 30 LOC bit. It's a practice .eleventy.js file that tests 11ty plugins with respect to template/layout overrides. That was the thing about which I was most unsure. But I got it working.
Here it is, for posterity. The final version would be much more robust.
const Nunjucks = require("nunjucks");
const path = require('path');
const fs = require('fs');

// Create custom Nunjucks environment.
let nunjucksEnvironment = new Nunjucks.Environment(
  new Nunjucks.FileSystemLoader([
    // Templates within the top-most dir in this list take precedence.
    "views/_includes",
    "plugin/_includes"
  ])
);

// Test plugin
const inputPlugin = (eleventyConfig, obj) => {
  // Set the custom Nunjucks environment into 11ty.
  eleventyConfig.setLibrary("njk", nunjucksEnvironment);

  // Using addLayoutAlias (few lines below) allows us to insert/override things in 11ty's layout system.
  let layoutPath = path.resolve(process.cwd(), "views/_includes/layouts/index.njk");
  if (!fs.existsSync(layoutPath)) {
    // Path is relative to the layouts folder, as set in the parent project.
    eleventyConfig.addLayoutAlias('index', '../../../plugin/_includes/layouts/index.njk');
  }
}

module.exports = function (eleventyConfig) {
  eleventyConfig.addPlugin(inputPlugin, {})

  return {
    dir: {
      input: "views",
      output: "dist",
      layouts: "_includes/layouts"
    },
  };
};


feat: Default model enhancements and API error handling

Is your feature request related to a problem? Please describe.
The default scaffolded model a bit limited, and there is some room for improvement in the error handling part of the API.
Describe the solution you'd like
Changes in Model

Auto-generated ID
Timestamps

Changes in Controller

JSON response for queries
Error handling

Describe alternatives you've considered
Considered adding an auth template, but seems like it'll be better to tackle that alone as an independent feature if needed.

Feel free to shoot a PR 👍


"Requested entity not found" for half of the messages sent trough FCM

[READ] Step 1: Are you in the right place?

For issues or feature requests related to the code in this repository
file a Github issue.

If this is a feature request make sure the issue title starts with "FR:".

For general technical questions, post a question on StackOverflow
with the firebase tag.
For general Firebase discussion, use the firebase-talk
google group.
For help troubleshooting your application that does not fall under one
of the above categories, reach out to the personalized
Firebase support channel.

[REQUIRED] Step 2: Describe your environment

Operating System version: Running at lambda AWS / Node
Firebase SDK version: "firebase-admin": "^7.0.0"
Library version: ?
Firebase Product: FCM (auth, database, storage, etc)

[REQUIRED] Step 3: Describe the problem
Steps to reproduce:
We are sending about 30k pushes to devices, 50% of this messages (iOS and Android) receives this error as response. We've already tried:

Generating new tokens for devices we own.
Change to debug/release projects.

Error: Requested entity was not found.
at FirebaseMessagingError.FirebaseError [as constructor] (/var/task/node_modules/firebase-admin/lib/utils/error.js:42:28)
at FirebaseMessagingError.PrefixedFirebaseError [as constructor] (/var/task/node_modules/firebase-admin/lib/utils/error.js:88:28)
at new FirebaseMessagingError (/var/task/node_modules/firebase-admin/lib/utils/error.js:253:16)
at Function.FirebaseMessagingError.fromServerError (/var/task/node_modules/firebase-admin/lib/utils/error.js:283:16)
at Object.createFirebaseError (/var/task/node_modules/firebase-admin/lib/messaging/messaging-errors.js:34:47)
at /var/task/node_modules/firebase-admin/lib/messaging/messaging-api-request.js:76:42
at
at process._tickDomainCallback (internal/process/next_tick.js:228:7)
Relevant Code:
let unifiedFirebase: app.App;

const initializeFirebases = async () => {
  const { iosParameters, unifiedFirebaseParameters } = await initializeParameters();
  await elk.info('Intializing firebase');
  if (!iosFirebase) {
    iosFirebase = await initializeGoogleServices(iosParameters,
                                                 'project_name_removed');
  }
  if (!unifiedFirebase) {
    unifiedFirebase = await initializeGoogleServices(unifiedFirebaseParameters,
                                                     'project_name_removed');
  }
  await elk.info('Intialized firebase');
};

const sendAndroidPush = async (androidToken: any, pushData: pushData, payload: any) => {
  const { title, body } = pushData;
  try {
    await sendPushMessage(title, body, androidToken, payload, unifiedFirebase, false);
    return true;
  } catch (e) {
    const errorDetails: any = Object.assign(pushData, {});
    errorDetails.stackTrace = e.stack || null;
    await elk.error('error_android_send_push', errorDetails);
    return false;
  }
};

const sendPushMessage = async (title:string, body:string, token:string, data: any,
                               firebaseApp: app.App, isTest:boolean) => {

  const message: FirebaseMessage = {
    token,
    notification : {
      title,
      body,
    },
  };

  if (data && Object.keys(data).length > 0) message.data = data;

  return firebaseApp.messaging().send(message, isTest);
};

Please contact Firebase support, and provide your project ID and some example tokens that causes the error. There's nothing that can be done in this repo to debug or resolve this issue.
https://firebase.google.com/support


Error Exporting Feature Lists to CSV: Requires '{}' Pattern in Filename

mzmine_0_0.log
Hi
I have a problem when I try to export to a CSV file. I am attempting to select those with a specific name from the feature list, but I keep encountering this error and I cannot get the data. Before I could get all the data together, but now it does not let me. Can you help me with this?
Operating System and Version:
Windows 11 Enterprise, 64-bit operating system, x64-based processor
12th Gen Intel(R) Core(TM) i7-1265U 1.80 GHz
16.0 GB RAM
Windows Feature Experience Pack
mzMine Version: mzMine 4.2.0
I have attached the screenshot, log file, and my project file. These are GC-EI Low resolution chromatograms.
Here is the link for the project file, it will expire in 1 week: (https://we.tl/t-DOv0XU6qNm)
I hope this information helps to diagnose the issue. Please let me know if any additional information is needed.
Thank you for your assistance!

Hi,
do you want to export multiple feature lists at once or just a single feature list?

I have 217 different chromatograms. For example, after adjusting them all with the local minimum feature resolver, I want to see them all in a single CSV file. However, it's giving me each chromatogram as a separate CSV file. Is there a way to combine them all into a single CSV file? Thank you.

This module exports ONE feature list to ONE csv file. If you select multiple feature lists you need to add {} as a name placeholder.
Usually you would run alignment multiple feature lists to compare them across samples and get a single aligned feature list that you can export to one file.
If you want to combine multiple csv files that can also be done easily in a small script downstream.


[MER-1694] Anonymous posts for students

Story
MER-1694
Notes

Instead of having a checkbox to mark a post as anonymous, I decided a button with options (similar to the ones we have in github) would improve the user experience and design

https://user-images.githubusercontent.com/74839302/222527146-63c9133b-9218-4fa7-aa2f-cefee776104b.mov
https://user-images.githubusercontent.com/74839302/222532603-3b68729f-cccb-4ab6-b44d-a9115c8fd3b3.mov

This PR includes the restyling of the CollabSpaceConfigView, done with @augusto1024 and @simonchoxx. Since there was no design provided in Figma, we intended to respect the look&feel of Figma's designs

Before

After

TODO

[x] Fix failing test
[x] Add tests

closed in favor or PR opened in oli-torus


Upgrade typer to 0.6.1

Codecov Report

Merging #75 (6bbdd89) into main (9e815ee) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main       #75   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            6         6
  Lines          280       280
=========================================
  Hits           280       280

Continue to review full report at Codecov.

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


clang-format

Codecov Report
Patch coverage: 100.00% and no project coverage change.

Comparison is base (ce9178a) 57.40% compared to head (e264e6b) 57.40%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@           Coverage Diff           @@
##             main      #96   +/-   ##
=======================================
  Coverage   57.40%   57.40%
=======================================
  Files          58       58
  Lines        4705     4705
  Branches      703      703
=======================================
  Hits         2701     2701
  Misses       1611     1611
  Partials      393      393

Files Changed
Coverage Δ

lib/easy/directory.c
73.07% <100.00%> (ø)

lib/utils/error.c
10.75% <100.00%> (ø)

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


Modify report template to list based on test label

Signed-off-by<EMAIL_ADDRESS><EMAIL_ADDRESS>Suggested fix for #382
Following the generation of some Caliper reports, I noticed that the report structure could be enhanced. I have changed the template and associated report code to follow the config file more closely and make the report more readable by:

Group test rounds under each test label, with each round starting at zero for each label.
Link to test labels instead of test rounds from the metadata side navigation (this is a more meaningful link)
Enable the provision of a description for each test label that is taken from the config file.

I have attached a file that is generated by the code.
report-20190320T153655.html.zip

LGTM.


shape: Query serialization

Make Shapes serializable. This will allow to pass them over wires as continuation tokens, distribute queries and even to implement virtual predicates.

More context: #824

How do you like CBOR as serialisation format?
It has support in JavaScript, Go, Python and it's fully compliant with JSON.

Another option is to use Gremlin's Bytecode format. Here is the implementation of the Gremlin Bytecode in JavaScript: https://github.com/apache/tinkerpop/blob/75b190665c0689e95847b0f9def145da172e1f9d/gremlin-javascript/src/main/javascript/gremlin-javascript/lib/process/graph-traversal.js
Basically: it accumulates the steps to a structure and then uses GraphSON to submit it. GraphSON is very similar to JSON-LD so we can use the same.

Workplan:

Extracting all the different structs implementing Shape to a different module (shapes.go?) so it will be clear which shapes do we have.
Add a Name() string method to the Shape interface to explicitly get the name of the shape.
Implement serialization to JSON-LD of the data the shapes hold that are not yet serializable
Implement parse(json_ld) Shape function that takes JSON-LD structure and returns a Shape object
Wire it to /query API as an acceptable Content-Type: application/ld+json
Implement a JavaScript client that can generate such shape

I know how to do 2, 3, 4, 5 and 6. 1 is a little more tricky without previous knowledge.

How do you like CBOR as serialisation format?

Yeah, I thinking about using either CBOR or Protobuf. Both have upsides and downsides.

Another option is to use Gremlin's Bytecode format.

I think this will limit us in the long run. We can support that separately if we want to be compatible with Gremlin clients, though.

Workplan:

Is already done, see shape package. This was my goal for the last few cycles.

That's an easy part :) However the implementation you describe is targeting CBOR specifically. Protobufs on the other hand may be more efficient for the case when you have a limited set of allowed messages, which is the case with Shapes. MarshalProto/UnmarshalProto may be added to the interface to support it.

This will work for simple cases, but not for advanced ones. Imagine a shape holding a pointer to a function. Or a reference to an external data source. I would propose to reject unknown shapes for serialization (return error if attempted). Also, if we want to target JSON-LD specifically here, we should consider dumping our own schema first to see if it works for us or not.

Again, let's not jump to JSON-LD for queries just yet :) It's a great option in the long run, since we can store them in DB that way (see #669), but the server needs to do a lot of work to interpret such query if it comes from HTTP. JSON-LD spec is pretty involved in terms of possible values, forms, etc. Again, I would propose to accept Protobufs with a strict schema first to see what works and what isn't. And then design a solution with JSON-LD in mind as the next step, or as a step toward #669.

Hm... Isn't strict unmarshalling JSON a solved problem in Go: https://gobyexample.com/json (I really don't know as I'm fairly new to the language)

JSON-LD will not require additional tooling

For the client side, yes, since it will just emit it. But for server side it's a different story. If you compare it to regular JSON, the number of steps necessary to interpret it may make it sub-optimal as a primary format for the queries.

we can wait with CBOR

Adding CBOR is easy if we already support JSON. It also gives a good performance boost in terms of decoding, so I would prefer it in the long run. But yes, we can start with JSON for now.

I don't feel very comfortable to add Proto messages as our data types story is pretty complex already

I would say Protos usually simplify the datatypes story a lot, since you get everything auto-generated. Plus they are easier to interpret and decode because the strict schema is baked in the format itself, as opposed to JSON/CBOR which are schema-less by design.
 I usually end up writing a proto decoder in JS by hand by translating the generated Go code. All of this is just to avoid dependencies :( So we will have to support JSON anyway, I guess. Hope the story with CBOR is better than with Protos at least.
I will look into server-side support for things like OpenAPI to see if it will be useful in this case.

By JSON-LD I was primarily talking about RDF terms representation (as we’ve done in Gizmo). Everything else is just regular JSON

To validate JSON we can use something like: https://github.com/alecthomas/jsonschema

By JSON-LD I was primarily talking about RDF terms representation (as we’ve done in Gizmo). Everything else is just regular JSON

This certainly works for serialization, but not for the deserialization, as mentioned above.

To generate JSON validation we can use something like https://github.com/alecthomas/jsonschema

Was thinking about using this exact library as well :)


Update DotNet release to call tools from eng common directory

This PR depends on this
Release stage will now use the following tools from eng/common directory

create-pull-request.yml
create-tags-and-git-release.yml
publish-blobs.yml
copy-docs-to-blobstorage.ps1

Tested with release of Azure.Template.1.0.2-preview.9 and verified doc publish step here

/azp run net - core - ci


Test/CI: seems to have broken somewhere along the way

Troubleshoot and repair...

Closing via https://github.com/geobtaa/geoblacklight_admin/pull/6


Clear Alert Bit

https://github.com/sparkfun/SparkFun_MAX17043_Particle_Library/blob/master/firmware/SparkFunMAX17043.cpp#L139
https://github.com/sparkfun/SparkFun_MAX17043_Particle_Library/blob/master/firmware/SparkFunMAX17043.cpp#L148
https://github.com/sparkfun/SparkFun_MAX17043_Particle_Library/blob/master/firmware/SparkFunMAX17043.cpp#L152
I think there should be "(1 << 5)"

It is defined in .h file
https://github.com/sparkfun/SparkFun_MAX17043_Particle_Library/blob/master/firmware/SparkFunMAX17043.cpp#L38

Good catch! Fixed in the latest commit, release 1.1.3.

Yaaaay, happy I could help. :angel:


How to disable autofill

Page Affected: https://developers.google.com/web/fundamentals/design-and-ux/input/forms/
What needs to be done?
Provide instructions on how to disable auto-fill for any given form field. This is something that developers need to be able to do for various reasons. As this stackoverflow question shows, this is quite a pain point for many developers, including myself.
https://stackoverflow.com/questions/15738259/disabling-chrome-autofill

I'd like to know the best way to do this without affecting accessibility of a given form, and that this is addressed for input fields other than passwords (i.e. address field, etc.)
Please address this on your site.


Adding USM support for Level 3 operators in SYCL-BLAS

This PR extends the USM support in SYCL-BLAS for Level 3 operators. All Level 3 benchmarks and tests now use USM and Buffers.
FYI: This PR is blocked by #385 and #388

@muhammad-tanvir-1211  Thanks for the USM support. I was wondering if there is any timeline on this PR, as I am mostly looking forward to integrate this repo into an application for L3 APIs to benchmark at scale on all the different vendor GPUs.

For avoid confusion it is better to remove the offset argument from make_*_view in case of USM pointers. Moreover, the presence of this argument breaks the interface of make_*_view for buffers.
https://github.com/codeplaysoftware/sycl-blas/blob/5e0656c0de259578fe845ef601dc5e7eea3d2c57/include/views/view.h#L332-L334
https://github.com/codeplaysoftware/sycl-blas/blob/5e0656c0de259578fe845ef601dc5e7eea3d2c57/include/views/view.h#L340-L342

The offset has been removed from the USM view class and the make_*_view methods for USM. I have also removed the get_access_displacement() method for both USM and Buffers.

The offset has been removed from the USM view class and the make_*_view methods for USM. I have also removed the get_access_displacement() method for both USM and Buffers.

You need to remove it from the buffer make_*_veiw as well and set it based on the buffer_iterator input. otherwise you create inconsistent make_view operator between buffer and usm

The offset has been removed from the USM view class and the make_*_view methods for USM. I have also removed the get_access_displacement() method for both USM and Buffers.

You need to remove it from the buffer make_*_veiw as well and set it based on the buffer_iterator input. otherwise you create inconsistent make_view operator between buffer and usm

We don't have it for buffers in the make_*_view methods. I added the offset argument only for USM in the early stages and then forgot to remove it afterwards.


js-sites-core ported from github.com/olemp/js-sites-core

Introduction
This is js-sites-core ported from github.com/olemp/js-sites-core and restructured to fit the current model of the Core.JavaScript library (AMD/Require.js).
I've removed quite a bit from the original js-sites-core to keep it simple in the beginning. Some of the logging etc (starting simple for now).
The Object Handler for Pages was also not ready.
Structure
The structure is
pnp => sharepoint => provisioning
SharePoint/Util
Some Util methods was needed, and they're added to SharePoint/Util.ts.
encodePropertyKey
Encodes property bag entries. Needed by Property Bag Entries to set properties as indexed.
replaceUrlTokens
Replaces tokens like {site} and {sitecollection}. Uses _spPageContextInfo.
Also want to support

{webpartgallery}
{siteassets}
{resources} (Which can be specifed by the user in e.g. Web Property Bag)

getNodeFromCollectionByTitle
Used in Navigation to get a Node with from a Node Collection with the specified title.
getRelativeUrl
Transform a absolute URL to a relative. Used in Composed Look since it's needs the ServerRelativeUrl.
Could perhaps be renamed to getServerRelativeUrl?
NB We need to mock up document.location and _spPageContextInfo to create tests for these.
Core
Under Provisioning, we have the Core module/class.
Core has one public function:

applyTemplate()

applyTemplate()
You would simply call it like this with a URL to your JSON template. A ES6 promise is returned.
The following tokens can be replaced for you:

{sitecollection}
{site}

An example URL would be {sitecollection}/SiteAssets/templates/taskroom.txt
pnp.sharepoint.provisioning.core.applyTemplate([URL]).then(function(result) {  })

This is a simple example of a template:
{
  "PropertyBagEntries": [
    {
      "Key": "Template",
      "Value": "SimpleTaskRoom",
      "Indexed": true
    }
  ],
  "Lists": [
    {
      "Title": "Tasks",
      "Url": "Lists/Tasks",
      "TemplateType": 171
    },
    {
      "Title": "Documents",
      "Url": "Documents",
      "TemplateType": 101
    }
  ],
  "Files": [
    {
      "Dest": "SitePages/Home.aspx",
      "Overwrite": true,
      "Src": "{sitecollection}/SiteAssets/Home.txt",
      "RemoveExistingWebParts": true,
      "WebParts": [
        {
          "Title": "SiteFeed",
          "Zone": "Main",
          "Order": 0,
          "Contents": {
            "FileUrl": "{sitecollection}/_catalogs/wp/SiteFeed.dwp"
          }
        }
      ]
    }
  ],
  "Navigation": {
    "QuickLaunch": [
      {
        "Url": "",
        "Title": "Home"
      },
      {
        "Url": "Lists/Tasks/AllItems.aspx",
        "Title": "Tasks"
      },
      {
        "Url": "Documents/Forms/AllItems.aspx",
        "Title": "Documents"
      }
    ]
  },
  "ComposedLook": {
    "ColorPaletteUrl": "{sitecollection}/_catalogs/theme/15/palette008.spcolor",
    "FontSchemeUrl": "{sitecollection}/_catalogs/theme/15/SharePointPersonality.spfont"
  }
}

applyTemplate() options (not in this Pull Request)
In the original JS Sites Core, applyTemplate() takes a second argument options, but I chose to not bring this
into this pull request, mostly because there should be a better place to handle provisioning config.
The options are

WaitMessageOptions
LoggingOptions

WaitMessageOptions

Header

The Header on the WaitMessage (SP.UI.ModalDialog.showWaitScreenWithNoClose)

Content

The Content on the WaitMessage (SP.UI.ModalDialog.showWaitScreenWithNoClose)

ShowProgress

Should a Progress Bar be present in the WaitMessage?

ProgressOverrides

Custom messages under the Progress Bar?
Defaults are Lists, Pages, Files etc.

LoggingOptions

On

Should there be logging in console?

LoggingFolder

Should a summary be saved as a file to e.g. Site Assets, or a custom library with a custom content type allowing for more data on the log file

NB! In Puzzlepart, we're using js-sites-core for several customers, and the LoggingFolder concept is very neat! If provisioning fails for the customer, they can just send us the .txt file, or we if we have a user in their tenant, we can have alerts on the list!

Schema
Have a look at the schema here (not yet ported):
https://github.com/Puzzlepart/js-sites-core/blob/master/dist/schema.md
Object Handlers
The Object Handlers are pretty solid now, but Pages and Lists can be improved.
Logging
The output from calling applyTemplate() with this file would be:
Sat Mar 05 2016 14:21:44 GMT+0100 (W. Europe Standard Time) 		 [Provisioning] 		 [Information] 		 Code execution scope started
Logger.js:31 Sat Mar 05 2016 14:21:44 GMT+0100 (W. Europe Standard Time) 		 [PropertyBagEntries] 		 [Information] 		 Code execution scope started
Logger.js:31 Sat Mar 05 2016 14:21:44 GMT+0100 (W. Europe Standard Time) 		 [PropertyBagEntries] 		 [Information] 		 Code execution scope ended
Logger.js:31 Sat Mar 05 2016 14:21:44 GMT+0100 (W. Europe Standard Time) 		 [Lists] 		 [Information] 		 Code execution scope started
Logger.js:31 Sat Mar 05 2016 14:21:46 GMT+0100 (W. Europe Standard Time) 		 [Lists] 		 [Information] 		 Code execution scope ended
Logger.js:31 Sat Mar 05 2016 14:21:46 GMT+0100 (W. Europe Standard Time) 		 [Files] 		 [Information] 		 Code execution scope started
Logger.js:31 Sat Mar 05 2016 14:21:47 GMT+0100 (W. Europe Standard Time) 		 [Files] 		 [Information] 		 Code execution scope ended
Logger.js:31 Sat Mar 05 2016 14:21:47 GMT+0100 (W. Europe Standard Time) 		 [Navigation] 		 [Information] 		 Code execution scope started
Logger.js:31 Sat Mar 05 2016 14:21:48 GMT+0100 (W. Europe Standard Time) 		 [Navigation] 		 [Information] 		 Code execution scope ended
Logger.js:31 Sat Mar 05 2016 14:21:48 GMT+0100 (W. Europe Standard Time) 		 [ComposedLook] 		 [Information] 		 Code execution scope started
Logger.js:31 Sat Mar 05 2016 14:21:59 GMT+0100 (W. Europe Standard Time) 		 [ComposedLook] 		 [Information] 		 Code execution scope ended
Logger.js:31 Sat Mar 05 2016 14:21:59 GMT+0100 (W. Europe Standard Time) 		 [Provisioning] 		 [Information] 		 Code execution scope ended

This should be recognizable for those who've used the PnP Sites Core framework (which I have used a lot).

Hi @olemp, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by Microsoft and real humans are currently evaluating your PR.
TTYL, MSBOT;

Thanks for doing that - really helps on my end. Great work on this!

No worries. Took about 5 minutes :+1:


Configuration endpoint

As an Anchor Platform developer, I would like to know what the current runtime state of the configuration is.  This story involves implementing a secure endpoint that can be used to query configuration.  This should be a restful interface and could serve later to support Anchor Platform UI Portal for viewing and editing configuration.   This will allow and anchor platform developer/operator to hit the endpoint via https and see the current runtime configuration values.
Please have security review the design of this endpoint to ensure it meets security standards as runtime configuration could expose secrets.

just need to add documentation.


build: bump angular

@angular-eslint/schematics  18.0.1 -> 18.1.0
@angular/cdk                18.0.4 -> 18.0.5
@angular/cli                18.0.5 -> 18.0.6
@angular/core               18.0.4 -> 18.0.5
PR Checklist

[ ] Unit Tests have been added for new changes
[ ] API tests have been updated if applicable
[ ] All commented code has been removed
[ ] If you've added a dependency, you've ensured license is compatible with Apache 2.0 and clearly outlined the added dependency.

What are you changing?

Anything the reviewer should know when reviewing this PR?
If the there are associated PRs in other repositories, please link them here (i.e. open-amt-cloud-toolkit/repo#365 )

:tada: This PR is included in version 8.0.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Added className prop to AnchoredOverlay component for custom styling

Docs changes related to #4739
Changelog
New

Added className prop docs as a follow up to https://github.com/primer/react/pull/4741 that allows custom styling of the AnchoredOverlay component

Rollout strategy

[ ] Patch release
[ ] Minor release
[ ] Major release; if selected, include a written rollout or migration plan
[x] None; if selected, include a brief description as to why

Testing & Reviewing

Verify that the className prop works as expected by adding custom styles to the AnchoredOverlay component.
Ensure that the updated documentation correctly reflects the new className prop.
Check for any potential issues with the className prop in various browsers (Chrome, Firefox, Safari, Edge).
Validate that the component remains SSR compatible with the new className prop.

Merge checklist

[ ] Added/updated tests
[x] Added/updated documentation
[ ] Added/updated previews (Storybook)
[ ] Changes are SSR compatible
[ ] Tested in Chrome
[ ] Tested in Firefox
[ ] Tested in Safari
[ ] Tested in Edge
[ ] (GitHub staff only) Integration tests pass at github/github (Learn more about how to run integration tests)

Hello, @broccolinisoup!
I have updated my PR according to the other PR, which also included the necessary code changes. As you suggested, I have left only the changes to the storybook.
I hope I was helpful. I would be happy to assist with other tasks as well, just let me know.
Have a great day!

Hi @romanpozdnov 👋🏻 Thanks so much!! All looks good 🎉
Feel free to have a look at our issues and pick if there is anything that interests you! Or reach out if you need any clarification for any of the issues 🙌🏻 Thanks for your contribution!!


Configure Renovate

Welcome to Renovate! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin.
:vertical_traffic_light: Renovate will begin keeping your dependencies up-to-date only once you merge or close this Pull Request.

Detected Package Files

package.json (npm)
uPortal-webapp/package.json (npm)

What to Expect
With your current configuration, Renovate will create 2 Pull Requests:

chore(deps): update dependency eslint-config-google to ^0.11.0

Schedule: "at any time"
Branch name: renovate/eslint-config-google-0.x
Upgrade eslint-config-google to ^0.11.0

chore(deps): update dependency remark-cli to v6

Schedule: "at any time"
Branch name: renovate/remark-cli-6.x
Upgrade remark-cli to ^6.0.0

:question: If you have any questions, try reading the Docs, particularly the Getting Started section.
Also, you can post questions about your config in Renovate's Config Help repository.

This PR has been generated by Renovate Bot.

Test PR, additional configuration incoming


Examples using tf-lite with gpu (face_detection_gpu) does not compile on jetson nano

The CPU example is working fine on jetson nano
 bazel build -c opt --define MEDIAPIPE_DISABLE_GPU=1 mediapipe/examples/desktop/face_detection:face_detection_cpu

However, when I try to compile the gpu version of above i.e
bazel build -c opt --copt -DMESA_EGL_NO_X11_HEADERS mediapipe/examples/desktop/face_detection:face_detection_gpu

I get lot of compilation errors related to EGL from tf-lite. Here is one trace of it.
In file included from external/org_tensorflow/tensorflow/lite/delegates/gpu/gl/egl_context.h:21:0,
                 from external/org_tensorflow/tensorflow/lite/delegates/gpu/gl/egl_context.cc:16:
external/org_tensorflow/tensorflow/lite/delegates/gpu/gl/egl_context.cc: In function 'int tflite::gpu::gl::{anonymous}::GetConfig(EGLDisplay, const EGLint*, void**)':
external/org_tensorflow/tensorflow/lite/delegates/gpu/common/status.h:68:18: error: request for member 'ok' in 'status2', which is of non-class type 'const int'
     if (!status2.ok()) return status2; \
                  ^
external/org_tensorflow/tensorflow/lite/delegates/gpu/gl/egl_context.cc:33:3: note: in expansion of macro 'RETURN_IF_ERROR'
   RETURN_IF_ERROR(GetOpenGlErrors());
   ^~~~~~~~~~~~~~~
external/org_tensorflow/tensorflow/lite/delegates/gpu/gl/egl_context.cc:35:69: error: cannot convert 'tflite::gpu::Status' to 'int' in return
     return InternalError("No EGL error, but eglChooseConfig failed.");
                                                                     ^
external/org_tensorflow/tensorflow/lite/delegates/gpu/gl/egl_context.cc:37:19: error: cannot convert 'tflite::gpu::Status' to 'int' in return
   return OkStatus();
                   ^
In file included from external/org_tensorflow/tensorflow/lite/delegates/gpu/gl/egl_context.h:21:0,
                 from external/org_tensorflow/tensorflow/lite/delegates/gpu/gl/egl_context.cc:16:
external/org_tensorflow/tensorflow/lite/delegates/gpu/gl/egl_context.cc: In function 'int tflite::gpu::gl::{anonymous}::CreateContext(EGLDisplay, EGLContext, EGLConfig, tflite::gpu::gl::EglContext*)':
external/org_tensorflow/tensorflow/lite/delegates/gpu/common/status.h:68:18: error: request for member 'ok' in 'status2', which is of non-class type 'const int'
     if (!status2.ok()) return status2; \
                  ^
external/org_tensorflow/tensorflow/lite/delegates/gpu/gl/egl_context.cc:50:3: note: in expansion of macro 'RETURN_IF_ERROR'
   RETURN_IF_ERROR(GetOpenGlErrors());
   ^~~~~~~~~~~~~~~
external/org_tensorflow/tensorflow/lite/delegates/gpu/gl/egl_context.cc:52:70: error: cannot convert 'tflite::gpu::Status' to 'int' in return
     return InternalError("No EGL error, but eglCreateContext failed.");
                                                                      ^
external/org_tensorflow/tensorflow/lite/delegates/gpu/gl/egl_context.cc:55:19: error: cannot convert 'tflite::gpu::Status' to 'int' in return
   return OkStatus();
                   ^
In file included from external/org_tensorflow/tensorflow/lite/delegates/gpu/gl/egl_context.h:21:0,
                 from external/org_tensorflow/tensorflow/lite/delegates/gpu/gl/egl_context.cc:16:
external/org_tensorflow/tensorflow/lite/delegates/gpu/gl/egl_context.cc: In member function 'int tflite::gpu::gl::EglContext::MakeCurrent(EGLSurface, EGLSurface)':
external/org_tensorflow/tensorflow/lite/delegates/gpu/common/status.h:68:18: error: request for member 'ok' in 'status2', which is of non-class type 'const int'
     if (!status2.ok()) return status2; \
                  ^
external/org_tensorflow/tensorflow/lite/delegates/gpu/gl/egl_context.cc:98:3: note: in expansion of macro 'RETURN_IF_ERROR'
   RETURN_IF_ERROR(GetOpenGlErrors());
   ^~~~~~~~~~~~~~~
external/org_tensorflow/tensorflow/lite/delegates/gpu/gl/egl_context.cc:100:68: error: cannot convert 'tflite::gpu::Status' to 'int' in return
     return InternalError("No EGL error, but eglMakeCurrent failed.");
                                                                    ^
external/org_tensorflow/tensorflow/lite/delegates/gpu/gl/egl_context.cc:102:19: error: cannot convert 'tflite::gpu::Status' to 'int' in return
   return OkStatus();
                   ^
external/org_tensorflow/tensorflow/lite/delegates/gpu/gl/egl_context.cc: In function 'int tflite::gpu::gl::CreateConfiglessContext(EGLDisplay, EGLContext, tflite::gpu::gl::EglContext*)':
external/org_tensorflow/tensorflow/lite/delegates/gpu/gl/egl_context.cc:112:70: error: cannot convert 'tflite::gpu::Status' to 'int' in return
     return UnavailableError("EGL_KHR_no_config_context not supported");
                                                                      ^
external/org_tensorflow/tensorflow/lite/delegates/gpu/gl/egl_context.cc: In function 'int tflite::gpu::gl::CreateSurfacelessContext(EGLDisplay, EGLContext, tflite::gpu::gl::EglContext*)':
external/org_tensorflow/tensorflow/lite/delegates/gpu/gl/egl_context.cc:120:67: error: cannot convert 'tflite::gpu::Status' to 'int' in return
     return UnavailableError("EGL_KHR_create_context not supported");
                                                                   ^
external/org_tensorflow/tensorflow/lite/delegates/gpu/gl/egl_context.cc:123:72: error: cannot convert 'tflite::gpu::Status' to 'int' in return
     return UnavailableError("EGL_KHR_surfaceless_context not supported");
                                                                        ^
In file included from external/org_tensorflow/tensorflow/lite/delegates/gpu/gl/egl_context.h:21:0,
                 from external/org_tensorflow/tensorflow/lite/delegates/gpu/gl/egl_context.cc:16:
external/org_tensorflow/tensorflow/lite/delegates/gpu/common/status.h:68:18: error: request for member 'ok' in 'status2', which is of non-class type 'const int'
     if (!status2.ok()) return status2; \
                  ^
external/org_tensorflow/tensorflow/lite/delegates/gpu/gl/egl_context.cc:128:3: note: in expansion of macro 'RETURN_IF_ERROR'
   RETURN_IF_ERROR(GetConfig(display, attributes, &config));
   ^~~~~~~~~~~~~~~
external/org_tensorflow/tensorflow/lite/delegates/gpu/gl/egl_context.cc: In function 'int tflite::gpu::gl::CreatePBufferContext(EGLDisplay, EGLContext, tflite::gpu::gl::EglContext*)':
external/org_tensorflow/tensorflow/lite/delegates/gpu/common/status.h:68:18: error: request for member 'ok' in 'status2', which is of non-class type 'const int'
     if (!status2.ok()) return status2; \
                  ^
external/org_tensorflow/tensorflow/lite/delegates/gpu/gl/egl_context.cc:146:3: note: in expansion of macro 'RETURN_IF_ERROR'
   RETURN_IF_ERROR(GetConfig(display, attributes, &config));
   ^~~~~~~~~~~~~~~
src/main/tools/linux-sandbox-pid1.cc:437: waitpid returned 2
src/main/tools/linux-sandbox-pid1.cc:457: child exited with code 1
src/main/tools/linux-sandbox.cc:204: child exited normally with exitcode 1
Target //mediapipe/examples/desktop/face_detection:face_detection_gpu failed to build
Use --verbose_failures to see the command lines of failed build steps.
INFO: Elapsed time: 4.812s, Critical Path: 1.58s
INFO: 0 processes.
FAILED: Build did NOT complete successfully

Based on:

request for member 'ok' in 'status2', which is of non-class type 'const int'

I think you are still pulling in X11's Status.  TFLite GPU's Status is a class, but that's not being recognized.  Instead X11's Status (which is an int) is being handled.  I don't know what Jetson Nano is, but Mesa is not officially supported from TFLite's point of view.  Some plumbing will be required on your end.  Can you make sure to block out X11 headers?

Based on:

request for member 'ok' in 'status2', which is of non-class type 'const int'

I think you are still pulling in X11's Status. TFLite GPU's Status is a class, but that's not being recognized. Instead X11's Status (which is an int) is being handled. I don't know what Jetson Nano is, but Mesa is not officially supported from TFLite's point of view. Some plumbing will be required on your end. Can you make sure to block out X11 headers?

I agree with impjdi, ensuring X11 headers are disabled sounds like the first thing todo.
You can try compiling with  EGL_NO_X11
bazel build -c opt  --copt -DMESA_EGL_NO_X11_HEADERS  --copt -DEGL_NO_X11  ...
and see if that helps (we have no jetson nano here to test with).

Thank @mcclanahoochie
Unfortunately adding EGL_NO_X11 did not help

@mcclanahoochie  here is a thought -
bazel build -c opt --copt -DMESA_EGL_NO_X11_HEADERS mediapipe/examples/desktop/face_detection:face_detection_gpu```

when executed on x86_64 Ubuntu 18.04 with nvidia 1080T at least compiles with out any issue

Jetson is arm64v8 machine that has Ubuntu 18.04 with nvidia embedded gpu. I have checked it has the same mesa egl etc (version wise) installed as on x86_64 machine.

##

Now I tried to trace the bazel build (I am a novice with bazel ... my first experience with bazel with this project itself) and it seems that usage of 'face_detection_gpu` refers to mobile_calculators with then refers to `gl` etc.

Now since it arm64v8, by any chance bazel is thinking that it is android and hence including or not including some headers ?

Is there is a way to find out (any bazel command) which platform is detected ?

That is very strange...
I have an arm64 linux board (with non-nvidia gpu) running ubuntu 18.04 and can compile the gpu examples (after installing mesa libs)
I'm not sure what else would also be trying to define 'Status' ..
Also I don't think the bazel is confusing ubuntu/android, but there are some extra bazel flags to make things verbose :
  --show_progress  --subcommands   --verbose_failures
maybe those verbose logs can point to something

Thanks @mcclanahoochie Here is the log after adding the suggested options to cmd line
(cd /home/ml/.cache/bazel/_bazel_ml/f1cff6d9ddc54c5055773f45a79d1262/execroot/mediapipe && \
  exec env - \
    PATH=/home/ml/.nvm/versions/node/v8.16.2/bin:/home/ml/.pyenv/plugins/pyenv-virtualenv/shims:/home/ml/.pyenv/shims:/home/ml/.pyenv/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games \
    PWD=/proc/self/cwd \
  /usr/bin/gcc -U_FORTIFY_SOURCE -fstack-protector -Wall -Wunused-but-set-parameter -Wno-free-nonheap-object -fno-omit-frame-pointer -g0 -O2 '-D_FORTIFY_SOURCE=1' -DNDEBUG -ffunction-sections -fdata-sections '-std=c++0x' -MD -MF bazel-out/aarch64-opt/bin/external/flatbuffers/_objs/flatbuffers/code_generators.d '-frandom-seed=bazel-out/aarch64-opt/bin/external/flatbuffers/_objs/flatbuffers/code_generators.o' -iquote external/flatbuffers -iquote bazel-out/aarch64-opt/bin/external/flatbuffers -isystem external/flatbuffers/include -isystem bazel-out/aarch64-opt/bin/external/flatbuffers/include -Wno-sign-compare -Wno-unused-function -Wno-uninitialized -Wno-unused-result -Wno-comment -Wno-return-type -Wno-unused-local-typedefs -Wno-ignored-attributes -DMESA_EGL_NO_X11_HEADERS -DEGL_NO_X11 '-std=c++14' -Wno-implicit-fallthrough -fexceptions -fno-canonical-system-headers -Wno-builtin-macro-redefined '-D__DATE__="redacted"' '-D__TIMESTAMP__="redacted"' '-D__TIME__="redacted"' -c external/flatbuffers/src/code_generators.cpp -o bazel-out/aarch64-opt/bin/external/flatbuffers/_objs/flatbuffers/code_generators.o)
ERROR: /home/ml/.cache/bazel/_bazel_ml/f1cff6d9ddc54c5055773f45a79d1262/external/org_tensorflow/tensorflow/lite/delegates/gpu/gl/BUILD:259:1: C++ compilation of rule '@org_tensorflow//tensorflow/lite/delegates/gpu/gl:gl_shader' failed (Exit 1) gcc failed: error executing command
  (cd /home/ml/.cache/bazel/_bazel_ml/f1cff6d9ddc54c5055773f45a79d1262/sandbox/linux-sandbox/737/execroot/mediapipe && \
  exec env - \
    PATH=/home/ml/.nvm/versions/node/v8.16.2/bin:/home/ml/.pyenv/plugins/pyenv-virtualenv/shims:/home/ml/.pyenv/shims:/home/ml/.pyenv/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games \
    PWD=/proc/self/cwd \
  /usr/bin/gcc -U_FORTIFY_SOURCE -fstack-protector -Wall -Wunused-but-set-parameter -Wno-free-nonheap-object -fno-omit-frame-pointer -g0 -O2 '-D_FORTIFY_SOURCE=1' -DNDEBUG -ffunction-sections -fdata-sections '-std=c++0x' -MD -MF bazel-out/aarch64-opt/bin/external/org_tensorflow/tensorflow/lite/delegates/gpu/gl/_objs/gl_shader/gl_shader.d '-frandom-seed=bazel-out/aarch64-opt/bin/external/org_tensorflow/tensorflow/lite/delegates/gpu/gl/_objs/gl_shader/gl_shader.o' -D__CLANG_SUPPORT_DYN_ANNOTATION__ -iquote external/org_tensorflow -iquote bazel-out/aarch64-opt/bin/external/org_tensorflow -iquote external/com_google_absl -iquote bazel-out/aarch64-opt/bin/external/com_google_absl -Wno-sign-compare -Wno-unused-function -Wno-uninitialized -Wno-unused-result -Wno-comment -Wno-return-type -Wno-unused-local-typedefs -Wno-ignored-attributes -DMESA_EGL_NO_X11_HEADERS -DEGL_NO_X11 '-std=c++14' -fno-canonical-system-headers -Wno-builtin-macro-redefined '-D__DATE__="redacted"' '-D__TIMESTAMP__="redacted"' '-D__TIME__="redacted"' -c external/org_tensorflow/tensorflow/lite/delegates/gpu/gl/gl_shader.cc -o bazel-out/aarch64-opt/bin/external/org_tensorflow/tensorflow/lite/delegates/gpu/gl/_objs/gl_shader/gl_shader.o)
Execution platform: @local_config_platform//:host

Use --sandbox_debug to see verbose messages from the sandbox
In file included from external/org_tensorflow/tensorflow/lite/delegates/gpu/gl/gl_shader.h:22:0,
                 from external/org_tensorflow/tensorflow/lite/delegates/gpu/gl/gl_shader.cc:16:
external/org_tensorflow/tensorflow/lite/delegates/gpu/gl/gl_shader.cc: In static member function 'static int tflite::gpu::gl::GlShader::CompileShader(GLenum, const string&, tflite::gpu::gl::GlShader*)':
external/org_tensorflow/tensorflow/lite/delegates/gpu/common/status.h:68:18: error: request for member 'ok' in 'status2', which is of non-class type 'const int'
     if (!status2.ok()) return status2; \
                  ^
external/org_tensorflow/tensorflow/lite/delegates/gpu/gl/gl_shader.cc:50:3: note: in expansion of macro 'RETURN_IF_ERROR'
   RETURN_IF_ERROR(TFLITE_GPU_CALL_GL(glCreateShader, &shader_id, shader_type));
   ^~~~~~~~~~~~~~~
external/org_tensorflow/tensorflow/lite/delegates/gpu/common/status.h:68:18: error: request for member 'ok' in 'status2', which is of non-class type 'const int'
     if (!status2.ok()) return status2; \
                  ^
external/org_tensorflow/tensorflow/lite/delegates/gpu/gl/gl_shader.cc:54:3: note: in expansion of macro 'RETURN_IF_ERROR'
   RETURN_IF_ERROR(
   ^~~~~~~~~~~~~~~
external/org_tensorflow/tensorflow/lite/delegates/gpu/gl/gl_shader.cc:68:66: error: cannot convert 'tflite::gpu::Status' to 'int' in return
                          "\nProblem shader is:\n" + shader_source);
                                                                  ^
external/org_tensorflow/tensorflow/lite/delegates/gpu/gl/gl_shader.cc:72:19: error: cannot convert 'tflite::gpu::Status' to 'int' in return
   return OkStatus();
                   ^
In file included from external/org_tensorflow/tensorflow/lite/delegates/gpu/gl/gl_shader.cc:19:0:
external/org_tensorflow/tensorflow/lite/delegates/gpu/gl/gl_call.h: In instantiation of 'int tflite::gpu::gl::gl_call_internal::Caller<T>::operator()(const string&, F, ErrorF, T*, Params&& ...) [with F = unsigned int (*)(unsigned int); ErrorF = int (*)(); Params = {unsigned int&}; T = unsigned int; std::__cxx11::string = std::__cxx11::basic_string<char>]':
external/org_tensorflow/tensorflow/lite/delegates/gpu/gl/gl_call.h:81:27:   required from 'int tflite::gpu::gl::gl_call_internal::CallAndCheckError(const string&, F, ErrorF, ResultT*, ParamsT&& ...) [with F = unsigned int (*)(unsigned int); ErrorF = int (*)(); ResultT = unsigned int; ParamsT = {unsigned int&}; std::__cxx11::string = std::__cxx11::basic_string<char>]'
external/org_tensorflow/tensorflow/lite/delegates/gpu/gl/gl_shader.cc:50:3:   required from here
external/org_tensorflow/tensorflow/lite/delegates/gpu/gl/gl_call.h:60:16: error: request for member 'ok' in 'status', which is of non-class type 'const int'
     if (status.ok()) return OkStatus();
         ~~~~~~~^~
external/org_tensorflow/tensorflow/lite/delegates/gpu/gl/gl_call.h:60:38: error: cannot convert 'tflite::gpu::Status' to 'int' in return
     if (status.ok()) return OkStatus();
                                      ^
external/org_tensorflow/tensorflow/lite/delegates/gpu/gl/gl_call.h:61:26: error: request for member 'code' in 'status', which is of non-class type 'const int'
     return Status(status.code(), status.error_message() + ": " + context);
                   ~~~~~~~^~~~
external/org_tensorflow/tensorflow/lite/delegates/gpu/gl/gl_call.h:61:41: error: request for member 'error_message' in 'status', which is of non-class type 'const int'
     return Status(status.code(), status.error_message() + ": " + context);
                                  ~~~~~~~^~~~~~~~~~~~~
In file included from /usr/include/EGL/eglplatform.h:136:0,
                 from /usr/include/EGL/egl.h:39,
                 from external/org_tensorflow/tensorflow/lite/delegates/gpu/gl/portable_gl31.h:21,
                 from external/org_tensorflow/tensorflow/lite/delegates/gpu/gl/gl_shader.h:23,
                 from external/org_tensorflow/tensorflow/lite/delegates/gpu/gl/gl_shader.cc:16:
external/org_tensorflow/tensorflow/lite/delegates/gpu/gl/gl_call.h:61:12: error: expression list treated as compound expression in functional cast [-fpermissive]
     return Status(status.code(), status.error_message() + ": " + context);
            ^
In file included from external/org_tensorflow/tensorflow/lite/delegates/gpu/gl/gl_shader.cc:19:0:
external/org_tensorflow/tensorflow/lite/delegates/gpu/gl/gl_call.h: In instantiation of 'int tflite::gpu::gl::gl_call_internal::Caller<void>::operator()(const string&, F, ErrorF, Params&& ...) [with F = void (*)(unsigned int, int, const char* const*, const int*); ErrorF = int (*)(); Params = {unsigned int, int, const char**, std::nullptr_t}; std::__cxx11::string = std::__cxx11::basic_string<char>]':
external/org_tensorflow/tensorflow/lite/delegates/gpu/gl/gl_call.h:88:24:   required from 'int tflite::gpu::gl::gl_call_internal::CallAndCheckError(const string&, F, ErrorF, Params&& ...) [with F = void (*)(unsigned int, int, const char* const*, const int*); ErrorF = int (*)(); Params = {unsigned int, int, const char**, std::nullptr_t}; std::__cxx11::string = std::__cxx11::basic_string<char>]'
external/org_tensorflow/tensorflow/lite/delegates/gpu/gl/gl_shader.cc:54:3:   required from here
external/org_tensorflow/tensorflow/lite/delegates/gpu/gl/gl_call.h:73:16: error: request for member 'ok' in 'status', which is of non-class type 'const int'
     if (status.ok()) return OkStatus();
         ~~~~~~~^~
external/org_tensorflow/tensorflow/lite/delegates/gpu/gl/gl_call.h:73:38: error: cannot convert 'tflite::gpu::Status' to 'int' in return
     if (status.ok()) return OkStatus();
                                      ^
external/org_tensorflow/tensorflow/lite/delegates/gpu/gl/gl_call.h:74:26: error: request for member 'code' in 'status', which is of non-class type 'const int'
     return Status(status.code(), status.error_message() + ": " + context);
                   ~~~~~~~^~~~
external/org_tensorflow/tensorflow/lite/delegates/gpu/gl/gl_call.h:74:41: error: request for member 'error_message' in 'status', which is of non-class type 'const int'
     return Status(status.code(), status.error_message() + ": " + context);
                                  ~~~~~~~^~~~~~~~~~~~~
In file included from /usr/include/EGL/eglplatform.h:136:0,
                 from /usr/include/EGL/egl.h:39,
                 from external/org_tensorflow/tensorflow/lite/delegates/gpu/gl/portable_gl31.h:21,
                 from external/org_tensorflow/tensorflow/lite/delegates/gpu/gl/gl_shader.h:23,
                 from external/org_tensorflow/tensorflow/lite/delegates/gpu/gl/gl_shader.cc:16:
external/org_tensorflow/tensorflow/lite/delegates/gpu/gl/gl_call.h:74:12: error: expression list treated as compound expression in functional cast [-fpermissive]
     return Status(status.code(), status.error_message() + ": " + context);
            ^
Target //mediapipe/examples/desktop/face_detection:face_detection_gpu failed to build
INFO: Elapsed time: 190.797s, Critical Path: 189.56s
INFO: 88 processes: 88 linux-sandbox.
FAILED: Build did NOT complete successfully

Thanks for the log.
It looks like the problem could be with eglplatform.h
See https://www.khronos.org/registry/EGL/api/EGL/eglplatform.h
and search the page for X11, and this is what you see
#elif defined(__unix__) && defined(EGL_NO_X11)

typedef void             *EGLNativeDisplayType;
typedef khronos_uintptr_t EGLNativePixmapType;
typedef khronos_uintptr_t EGLNativeWindowType;

#elif defined(__unix__) || defined(USE_X11)

/* X11 (tentative)  */
#include <X11/Xlib.h>
#include <X11/Xutil.h>

typedef Display *EGLNativeDisplayType;
typedef Pixmap   EGLNativePixmapType;
typedef Window   EGLNativeWindowType;

We want to be in the EGL_NO_X11 case (hence the bazel defines).
The 'Status' problem will definitely happen if we  include <X11/Xlib.h>, because inside Xlib.h we get
#define Status int
.. not what we want :/
As an experiment, try opening that file on your machine and making sure the EGL_NO_X11 case is chosen (either by using '#if 1' or write 'blah' inside that case to see if there are errors compiling). Either way the goal is to not use the X11 headers.
I know editing system files is not a solution, this is just to see if we're on the right track.

Thanks @mcclanahoochie
Your suggestion worked !!
Indeed there is a difference between the eglplatform.h on jetson vs the one that you provided the link to.
I inserted the above block resulting in the exclusion of X11 headers and I got the face_detection_gpu compiled.
I have yet to test it by running it.
Many thanks.
Here are some details that are bit strange -
A dell laptop running ubuntu 18.04 with Nvidia Quadro
# ml @ ml-dell in ~ [14:57:12]
$ sudo dpkg --status libegl1-mesa-dev
Package: libegl1-mesa-dev
Status: install ok installed
Priority: optional
Section: libdevel
Installed-Size: 172
Maintainer: Ubuntu X-SWAT<EMAIL_ADDRESS>Architecture: amd64
Multi-Arch: same
Source: mesa
Version: 19.0.8-0ubuntu0~18.04.3
Depends: mesa-common-dev (= 19.0.8-0ubuntu0~18.04.3), libglvnd-dev, libdrm-dev (>= 2.4.95), libx11-dev, libxext-dev, libxxf86vm-dev, libxdamage-dev, libxfixes-dev, libxcb-glx0-dev, libxcb-dri2-0-dev, libxcb-dri3-dev, libxcb-present-dev, libxcb-sync-dev, libxshmfence-dev, libx11-xcb-dev, libwayland-dev (>= 1.15.0), x11proto-dev
Description: free implementation of the EGL API -- development files
 This package contains the development environment required for compiling
 programs against EGL native platform graphics interface library.
 EGL provides a platform-agnostic mechanism for creating rendering surfaces
 for use with other graphics libraries, such as OpenGL|ES.
 .
 This package provides the development environment for compiling programs
 against the EGL library.
Homepage: https://mesa3d.org/
Original-Maintainer: Debian X Strike Force<EMAIL_ADDRESS>
Content of eglplatform.h
#elif defined(__ANDROID__) || defined(ANDROID)

struct ANativeWindow;
struct egl_native_pixmap_t;

typedef struct ANativeWindow*           EGLNativeWindowType;
typedef struct egl_native_pixmap_t*     EGLNativePixmapType;
typedef void*                           EGLNativeDisplayType;

#elif defined(USE_OZONE)

typedef intptr_t EGLNativeDisplayType;
typedef intptr_t EGLNativeWindowType;
typedef intptr_t EGLNativePixmapType;

#elif defined(__unix__) || defined(__APPLE__)

#if defined(MESA_EGL_NO_X11_HEADERS)

typedef void            *EGLNativeDisplayType;
typedef khronos_uintptr_t EGLNativePixmapType;
typedef khronos_uintptr_t EGLNativeWindowType;

Important thing to note is that MESA_EGL_NO_X11_HEADERS is there in the header file
Jetson Nano
# ml @ ml-nano1 in ~/Desktop/Dev/third-party/mediapipe on git:master x [14:59:43]
$ sudo dpkg --status libegl1-mesa-dev
Package: libegl1-mesa-dev
Status: install ok installed
Priority: optional
Section: libdevel
Installed-Size: 172
Maintainer: Ubuntu X-SWAT<EMAIL_ADDRESS>Architecture: arm64
Multi-Arch: same
Source: mesa
Version: 19.0.8-0ubuntu0~18.04.3
Depends: mesa-common-dev (= 19.0.8-0ubuntu0~18.04.3), libglvnd-dev, libdrm-dev (>= 2.4.95), libx11-dev, libxext-dev, libxxf86vm-dev, libxdamage-dev, libxfixes-dev, libxcb-glx0-dev, libxcb-dri2-0-dev, libxcb-dri3-dev, libxcb-present-dev, libxcb-sync-dev, libxshmfence-dev, libx11-xcb-dev, libwayland-dev (>= 1.15.0), x11proto-dev
Description: free implementation of the EGL API -- development files
 This package contains the development environment required for compiling
 programs against EGL native platform graphics interface library.
 EGL provides a platform-agnostic mechanism for creating rendering surfaces
 for use with other graphics libraries, such as OpenGL|ES.
 .
 This package provides the development environment for compiling programs
 against the EGL library.
Homepage: https://mesa3d.org/
Original-Maintainer: Debian X Strike Force<EMAIL_ADDRESS>
Content of eglplatform.h
#elif defined(USE_OZONE)

typedef intptr_t EGLNativeDisplayType;
typedef intptr_t EGLNativeWindowType;
typedef intptr_t EGLNativePixmapType;

#elif defined(WAYLAND)

#include <wayland-client.h>

typedef struct wl_display    *EGLNativeDisplayType;
typedef void                 *EGLNativePixmapType;
typedef struct wl_egl_window *EGLNativeWindowType;

#elif defined(__unix__) || defined(__APPLE__)

/* X11 (tentative)  */
#include <X11/Xlib.h>
#include <X11/Xutil.h>

typedef Display *EGLNativeDisplayType;
typedef Pixmap   EGLNativePixmapType;
typedef Window   EGLNativeWindowType;

#elif defined(__HAIKU__)

and the necessary define is missing !!

Now, the version of mesa on jetson and my dell laptop is identical but the eglplatform.h is different.
May be this file is autogenerated.

I am going to test if the gpu on jetson indeed gets used or not in next 1 hour or so and will inform the results.
Regards
Kapil

So I ran the stuff and got an error -
Command issued to run
# ml @ ml-nano1 in ~/Desktop/Dev/third-party/mediapipe on git:master x [16:27:44]
$ bazel-bin/mediapipe/examples/desktop/face_detection/face_detection_gpu --calculator_graph_config_file=mediapipe/graphs/face_detection/face_detection_mobile_gpu.pbtxt --input_video_path=/home/ml/Desktop/Dev/testdata/Run_combined.mp4

The response was -
I1212 16:27:44.495141 11397 demo_run_graph_main_gpu.cc:56] Initialize the calculator graph.
I1212 16:27:44.496888 11397 demo_run_graph_main_gpu.cc:60] Initialize the GPU.
I1212 16:27:44.518015 11397 gl_context_egl.cc:158] Successfully initialized EGL. Major : 1 Minor: 5
W1212 16:27:44.518121 11397 gl_context_egl.cc:163] Creating a context with OpenGL ES 3 failed: Unknown: ; eglChooseConfig() returned no matching EGL configuration for RGBA8888 D16 ES3 request.
W1212 16:27:44.518146 11397 gl_context_egl.cc:164] Fall back on OpenGL ES 2.
E1212 16:27:44.518735 11397 demo_run_graph_main_gpu.cc:186] Failed to run the graph: ; eglChooseConfig() returned no matching EGL configuration for RGBA8888 D16 ES2 request.

Now I do not anything about EGL etc as such. I looked at the line that is failing at gl_context_egl.cc and still nothing made sense. Then I googled and just with a shear luck at this point of time I found this thread that talks about EGL & X11.
https://devtalk.nvidia.com/default/topic/1030582/jetson-tx2/egl-without-x11/
Based on this thread I understood that EGL needs the notion of windowing. When I issued the above command, I was using ssh (from my osx).
I connected a monitor to jetson nano and issued the command there and it worked !!
However, this brings then another aspect as highlighted in the above thread at devtalk.nvidia.com. If one want to use non-X11 windowing system then the configuration would be different. At least this is what I understood.
Based on above, would it make sense for mediapipe to let the user (i.e. me in this case) pass the eglConfig or eglContext ? This is necessary because these edge devices will run headless and there will be no X11 windowing etc.
Please guide.
Regards
Kapil

Nice progress!
Passing in an eglConfig would require some framework plumbing (you can try modifying gl_context_egl locally for testing directly at least).
For external GL contexts, please see this https://github.com/google/mediapipe/issues/313#issuecomment-564726162
Maybe some combination of those options works for you


Chef Infra Client 17.3 release notes

Signed-off-by: Tim Smith<EMAIL_ADDRESS>

i merged https://github.com/chef/chef/pull/11741 so it can get in

There's TODOs here, but this is at the point we can start reviewing it.


reactlibrary/mobilemessaging/ReactChatView.java:65: error: cannot find symbol

Hello Team, I have integrated on iOS and it seems that integration is properly setup, however on Android the app is breaking on run time. The error message while running the app is this  node_modules/infobip-mobile-messaging-react-native-plugin/android/src/main/java/org/infobip/reactlibrary/mobilemessaging/ReactChatView.java:65: error: cannot find symbol. Please check the screen shot for more clarification.

I have followed down below steps, still it fails:

Configurations:
Android Studio: 4.1.2
React Native : 0.61.3
mobile-messaging-react-native-plugin: 2.5.0
Help will be appreciated. @riskpp @tjuric

Hi @PavanApollo, sorry for delayed answer. Please check 2.5.2 version, should be fine there.
BR, Olga

I'm closing this task cause we've identified this issue in 2.5.0 version of our library and fixed it in 2.5.2.


[storage] Remove NVMe parameters from front-end that don't belong

Many of these will end up on the middle/back-end instead.
Signed-off-by: Ben Walker<EMAIL_ADDRESS>

I would like to see how we propose to solve the bridge to Marvell and Nvidia if we remove those ?
see https://github.com/opiproject/opi-marvell-bridge/blob/main/mrvl_nvme_json.rpc_methods.pdf
I'm ok if we move it to middle or back, but before we remove them, maybe we should add middle/back example first... ?

Which Marvell call breaks if these are removed? I tried to read over their code and I don't see any of these used. Separately, as an FYI, they're missing several of their RPCs from that PDF documentation. They're in the go code but not in the PDF.
I also see several places where the subsystem_id is used as the SubNQN in that bridge - those are not the same thing. It needs to use the subsystem_id to look up the subsystem object, which has the NQN in it.

I was hoping to propose backend APIs and then remove these... but it should be okay to first take them out and then discuss the backend APIs

I would like to see how we propose to solve the bridge to Marvell and Nvidia if we remove those ?
see https://github.com/opiproject/opi-marvell-bridge/blob/main/mrvl_nvme_json.rpc_methods.pdf
I'm ok if we move it to middle or back, but before we remove them, maybe we should add middle/back example first... ?

Which Marvell call breaks if these are removed? I tried to read over their code and I don't see any of these used. Separately, as an FYI, they're missing several of their RPCs from that PDF documentation. They're in the go code but not in the PDF.
I also see several places where the subsystem_id is used as the SubNQN in that bridge - those are not the same thing. It needs to use the subsystem_id to look up the subsystem object, which has the NQN in it.

I'm not saying those changes are breaking, just asking if they are...
the missing RPCs from the PDF that needs to be added to Marvell implementation are attach/detach of namespace
And isn't not in the code currently because we are still having discussion if this is going to be OPI API or not
https://github.com/opiproject/opi-api/issues/177
Correct, subsystem_id vs SubNQN is not the same, and that part of bridge implementation should change

I was hoping to see a proposal on the backend APIs and then remove these... but it should be okay to first take them out and then discuss the backend APIs

I agree, would like to see us add things before remove things as well

I'm not saying those changes are breaking, just asking if they are...

Ok - I don't believe these changes require any updates to the Marvell bridge. I can't see the NVIDIA one.

the missing RPCs from the PDF that needs to be added to Marvell implementation are attach/detach of namespace
And isn't not in the code currently because we are still having discussion if this is going to be OPI API or not
https://github.com/opiproject/opi-api/issues/177

I don't think these are the same thing. If you look at how CreateNvmeNamespace is implemented on the Marvell bridge, it calls mrvl_nvm_subsys_alloc_ns which isn't documented in the PDF. I don't think there's any discussion on whether we need to be able to add/remove subsystems from namespaces.

I was hoping to see a proposal on the backend APIs and then remove these... but it should be okay to first take them out and then discuss the backend APIs

I agree, would like to see us add things before remove things as well

I limited myself to only removing things that cannot possibly work as part of a front-end configuration. So I'm not removing any functionality that was implementable anyway, and we may as well get rid of it now. We're not losing anything, only gaining clarity.

I don't think these are the same thing. If you look at how CreateNvmeNamespace is implemented on the Marvell bridge, it calls mrvl_nvm_subsys_alloc_ns which isn't documented in the PDF. I don't think there's any discussion on whether we need to be able to add/remove subsystems from namespaces.

mrvl_nvm_subsys_alloc_ns is on page 7 of the PDF

mrvl_nvm_subsys_alloc_ns is on page 7 of the PDF

Whoops, I didn't realize that the GitHub pdf viewer has a "more pages" button - I see it now. Thanks.


fix(reset-state): ensure state is reset

:tada: This PR is included in version 2.0.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


⚠ Bofrost.at has degraded performance

In 128f35b, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1453 ms

Resolved: Bofrost.at performance has improved in fd7cf42.


Added image magnifier sample

Q
A

Bug fix?
no

New feature?
no

New sample?
yes

What's in this Pull Request?
This web part allow to magnify an image, displaying a resolution more detailed through a lens.

@giuleon,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by Microsoft. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot

Hi @VesaJuvonen, are there problem to merge this one ?

Just time - lack of it... to double check things... will be merged soon to get it included in Oct release.

Ok thanks 😉

We would always request a sample in one PR to ensure that we can check stuff more efficiently, since now we'll need to cancel both of the samples, if either one is not working... so would rather request the second sample as new PR. thx.

ok thanks

thx Giuliano for this. Sorry for the small delay on getting things processed, our objective is to be much faster in the future.

Thanks Vesa


about minifilter IRP_SETINFORMATION ProtectFiles

minifilter-->FileDispositionInformation
can not protect files
shift+delete can delete files, so how can i stop this?

FILE_DELETE_ON_CLOSE
Delete the file when the last handle to it is passed to NtClose. If this flag is set, the DELETE flag must be set in the DesiredAccess parameter.
.... And there are better places to be getting free support than here.  A lot of people start here

thanks ,  it`s work fine


Implement POST /v3/packages/:guid/upload

https://github.com/cloudfoundry/cf-crd-explorations/issues/13

We should also squash or just reword the WIP commits in this PR. My intention was to deal with those before making the PR, but I was out sick and didn't mention it to those who took over.

@gnovv and I just accepted this as is. I decided against undoing the WIPs because it was causing conflicts. Should we just merge this PR, or do people have unresolved concerns?

@gnovv and I just accepted this as is. I decided against undoing the WIPs because it was causing conflicts. Should we just merge this PR, or do people have unresolved concerns?

Thanks for updating the README with environment variable details. This is good to be merged.


Do not wrap the result type of paramless methods in ExprType.

Reserve ExprType for by-name params only.
This is closer to the contents of TASTy and of pickles, and is also closer to a user understanding of the language.
We then rename ExprType to ByNameType.

doesnt ExprType signal that the value is evaluated each time?

No, it's not remotely enough to know that. When you have f(x) an you compute f.tpe.appliedTo(x.tpe), you never receive an ExprType, although f(x) is clearly evaluated each time.


Karpenter nodes doesn't join aws load balancer registerd target groups to take load.

Description
Observed Behavior: Karpenter nodes are getting created, but nodes are not able to join ec2 registered target groups in order to take load to pods running on karpenter nodes.

Expected Behavior: Karpenter should join registered target groups in order take load on to pods running on it's nodes
Reproduction Steps (Please include YAML): deployed karpenter on eks manged node group using terraform module eks and submodule of karpenter with version 20.0.0 and helm chart with version v0.34.0, I have registered target groups for my external and internal application load balancer which redirects requests on to pods running on eks managed node groups and not by karpenter nodes.
Versions: Karpenter = v0.34.0, Terraform eks module 20.0.0 and karpenter submodule 20.0.0

Chart Version: v0.34.0
Kubernetes Version (kubectl version): 1.29

My node pool and node class details
resource "kubectl_manifest" "karpenter_node_pool" {
  count     = local.is_test_environment ? 0 : 1
  yaml_body = <<-YAML
    apiVersion: karpenter.sh/v1beta1
    kind: NodePool
    metadata:
      name: default
    spec:
      template:
        spec:
          nodeClassRef:
            name: default
          requirements:
            - key: "kubernetes.io/arch"
              operator: In
              values: ["amd64"]
            - key: karpenter.k8s.aws/instance-family
              operator: In
              values: [t3]
            - key: karpenter.k8s.aws/instance-size
              operator: In
              values: [large]
            - key: "karpenter.sh/capacity-type" # If not included, the webhook for the AWS cloud provider will default to on-demand
              operator: In
              values: ["on-demand"]
      disruption:
        consolidationPolicy: WhenUnderutilized
        expireAfter: 720h
  YAML

  depends_on = [
    helm_release.karpenter, kubectl_manifest.karpenter_node_class
  ]
}

resource "kubectl_manifest" "karpenter_node_class" {
  count     = local.is_test_environment ? 0 : 1
  yaml_body = <<-EOF
    apiVersion: karpenter.k8s.aws/v1beta1
    kind: EC2NodeClass
    metadata:
      name: default
    spec:
      amiFamily: AL2
      role: ${module.eks.eks_managed_node_groups["two"].iam_role_name}
      subnetSelectorTerms:
        - tags:
            karpenter.sh/discovery: ${local.cluster_name}
      securityGroupSelectorTerms:
        - tags:
            karpenter.sh/discovery: ${local.cluster_name}
      tags:
        karpenter.sh/discovery: ${local.cluster_name}
  EOF

  depends_on = [
    helm_release.karpenter
  ]
}

module and helm chart

module "karpenter" {
  source                        = "terraform-aws-modules/eks/aws//modules/karpenter"
  version                       = "20.0.0"
  cluster_name                  = module.eks.cluster_name
  irsa_oidc_provider_arn        = module.eks.oidc_provider_arn
  enable_irsa                   = true
  create_access_entry           = false
  create_instance_profile       = true
  create_node_iam_role          = false
  node_iam_role_arn             = module.eks.eks_managed_node_groups["two"].iam_role_arn
  node_iam_role_use_name_prefix = false
  node_iam_role_additional_policies = {
    AmazonSSMManagedInstanceCore = "arn:aws:iam::aws:policy/AmazonSSMManagedInstanceCore"
  }
  tags = {
    "karpenter.sh/discovery" = local.cluster_name
  }
}

resource "helm_release" "karpenter" {
  count            = local.is_test_environment ? 0 : 1
  create_namespace = true
  namespace        = "karpenter"
  name             = "karpenter"
  repository       = "oci://public.ecr.aws/karpenter"
  chart            = "karpenter"
  version          = "v0.34.0"

  set {
    name  = "serviceAccount.annotations.eks\\.amazonaws\\.com/role-arn"
    value = module.karpenter.iam_role_arn
  }

  set {
    name  = "dnsPolicy"
    value = "Default"
  }

  set {
    name  = "serviceAccount.annotations.eks\\.amazonaws\\.com/sts-regional-endpoints"
    value = "true"
    type  = "string"
  }

  set {
    name  = "settings.clusterName"
    value = module.eks.cluster_name
  }

  set {
    name  = "settings.clusterEndpoint"
    value = module.eks.cluster_endpoint
  }

  set {
    name  = "settings.interruptionQueue"
    value = module.karpenter.queue_name
  }

  values = [
    <<-EOT
    affinity:
      nodeAffinity:
        requiredDuringSchedulingIgnoredDuringExecution:
          nodeSelectorTerms:
            - matchExpressions:
              - key: "karpenter.sh/nodepool"
                operator: "DoesNotExist"
    EOT
  ]

  depends_on = [module.eks.eks_managed_node_groups, module.eks]
}

Please let me know what I'm missing or it's a bug.

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

kubectl of my targetgroup binding created by alb when i add above mentioned annotation
kubectl describe targetgroupbindings  k8s-stagingi-callisto-224c049c92 -n staging-ibwave - o yaml
Name:         k8s-stagingi-callisto-224c049c92
Namespace:    staging-ibwave
Labels:       ingress.k8s.aws/stack=staging-ingress-group
Annotations:
API Version:  elbv2.k8s.aws/v1beta1
Kind:         TargetGroupBinding
Metadata:
Creation Timestamp:  2024-04-24T18:29:01Z
Finalizers:
elbv2.k8s.aws/resources
Generation:        1
Resource Version:  88988643
UID:               7121a4df-526e-410e-b48b-971352b3f780
Spec:
Ip Address Type:  ipv4
Networking:
Ingress:
From:
Security Group:
Group ID:  sg-0ff2ccd75dfcc5429
Ports:
Port:      30717
Protocol:  TCP
Node Selector:
Match Labels:
Environment:  staging
Service Ref:
Name:            callisto-web
Port:            8080
Target Group ARN:  arn:aws:elasticloadbalancing:eu-west-1:207997242047:targetgroup/k8s-stagingi-callisto-224c049c92/8c6c8fdc65818fd6
Target Type:       instance
Status:
Observed Generation:  1
Events:
Type    Reason                  Age                From                Message

Normal  SuccessfullyReconciled  95s (x3 over 95s)  targetGroupBinding  Successfully reconciled

Do you have an existing load balancer (not AWS Load Balancer Controlled), that you are trying to use?  Do you haven an ingress resource, if so, can you include it?

@dewstyh Do you have an update here? It's tough for us to make progress on the bug without getting more information.

Hello sorry for lost of track on this issue, the issue has been solved, I've alb annotation target node labels and matched with that to register nodes under those targetgroups. then it's successfully registerd the instances( targets).
thanks


Control points are all labelled as "1" when opening an mcd for which control points have been set

Hey,
I do the following:

Set control points on an mcd and their counterpart on a czi.
I close napping
I open napping again
I select the same files for visualisation

The previously set control points are now all marked as "1"
Cheers,
Nils

Thanks for reporting
Known but for which I don't know the solution :smile:
The napari interface for point labels is currently being refactored, waiting for that before attempting to fix this bug.
Note that, when you add another point, the point IDs are "restored"

See https://github.com/napari/napari/issues/2115

I have now noticed that when reopening the images where points have already been set, the correct points are replaced by point number 1.

Maybe an "Export points" button would be a quick fix.

I have now noticed that when reopening the images where points have already been set, the correct points are replaced by point number 1.

Ok, that's definitely a bug then

Maybe an "Export points" button would be a quick fix.

The points are already saved automatically to the control points directory - could you maybe check the state of that file when testing next time? Thanks!

That's how I know that the control points are overwritten. To me it seems like the problem comes from the fact that the control points are always and automatically written out, where erroneous points replace the correct ones.


Rule questions (dates and inner decisions)

Datetime
Do you have any suggestions for how we could use dates within rules?
Something like: application_date is after 2022  or birthday is between 1990 and 2000 or for something spicier ticket_date is not less than 30 days from today?
Inner decisions
We would like to capture the inner decisions for when a consequent is false. In drools they have something like setExplanation(string) but I'm not sure the best way to do that here. Would a JSON structure like this make sense?
{ "result": "failed", "reason": "low credit" }
Any suggestions would be appreciated.

@montag Thanks for your feedback.

Date Time can be added as a type of token (similar to that of a String Token or a Numeric Token).
Yes, for inner decisions, a json structure would be good, as it gives freedom to the authors to specify something that communicates to the receiver of the decision

Please let me know if you are good with the above. I can pick up Date Time as an enhancement.

Thanks for your feedback.
Datetime would be a great enhancement for us. We're currently using epoch millis as a Numeric token which works great but it's hard to read or update. A standard format timestamp would be a great improvement.
We've also made a few tweaks ourselves. If you're interested we can push PR's for those.

Yes, sure!
Please send those PRs. Happy to review and release.
I will get to work on the date time.
On the current Python API, do you see a need for a fluent API, that
constructs a rule in a single command? I am thinking of the same, but your
feedback is appreciated.
On Mon, 29 May, 2023, 01:16 montag, @.***> wrote:

Thanks for your feedback.
Datetime would be a great enhancement for us. We're currently using epoch
millis as a Numeric token which works great but it's hard to read or
update. A standard format timestamp would be a great improvement.
We've also made a few tweaks ourselves. If you're interested we can push
PR's for those.
—
Reply to this email directly, view it on GitHub
https://github.com/jeyabalajis/simple-rule-engine/issues/32#issuecomment-1566242777,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AD2BGJVOHK34YFCFM6OPCSLXIOTPRANCNFSM6AAAAAAXGSDX5M
.
You are receiving this because you commented.Message ID:
@.***>


sanitizing headers (maybe behind flag option?)

Nginx will silently remove any headers containing _ in the header field name.
Maybe AFNetworking should sanitized any header (maybe behind a flag option, or at least warn?)
https://www.nginx.com/resources/wiki/start/topics/tutorials/config_pitfalls/#missing-disappearing-http-headers

Thanks for the PR, but we won't be merging it. Thanks anyway!

@jshier haha I guess new year PR clean up..


Print exit status on http errors

When error codes are returned from consul/http failed to connect codes print them out so we know there's an underlying problem.

In general an error code from this call is not a problem. This is the call that ensures only one node will execute the command for a particular time step.

Yes, but if I used cronsul in front of my cron task it would silently not execute and it would never execute if configured incorrectly.  With the above change cron would get a response back which would be forwarded to email or syslog.

I'm not sure I understand your concern. The point of cronsul is to silently not execute your command on all but one of the nodes.
Are you seeing failures that are not the normal mutex behavior?

Correct, but if someone mistakenly does not configure the CONSUL_HOST or CONSUL_PORT correctly then it will silently execute nothing ever on any server.

Aha, that makes sense.
And I see that you're suppressing output if you get the normal "false" output as well, so under normal operation this should still be silent.


LocateOwner dives the entire SyntaxTree when partial parsing (while typing)

We can be smarter in our LocateOwner implementation to determine the potential location of a text change based on the starts of Block children

/cc @ToddGrun talked with @Eilon and duping the whole syntax tree is a no go, but we should talk to figure out a more performant way of doing this. Have some ideas.

@ToddGrun talked with @Eilon to do this in RC2 would need to see performance numbers.

@NTaylorMullen can you work with the tooling folks to identify what perf analysis we need to do here?

Will do

@NTaylorMullen need an update on this because it's been stale. Have we seen perf issues here that we need to investigate for 1.0.0? If not, I'll move this out.

Move out. It's being worked around in Visual Studio.

Talked with @ToddGrun offline. Perf issues found with this are many years old. Will have to re-profile.

After completing #800 LocateOwner shows itself to be around 6% of execution for successful partial parses:

This was done with the MSN home page.

@ToddGrun I worked on short circuiting this logic and the best I could do as to avoid the final OwnsChange call on an EditHandler (no perf impact). I know you said you worked around this on your end. Could we sink up to see what you've done?

Took a shot at minimizing call paths here. Got through it a bit but turned out allocations muddled the perf gains (went from 6% impact to 25% after attempted fix).


Move RequestFocus function to TextBoxBase.java

This enables RequestFocus not only for TextBox but also for
EmailPicker and PasswordTextBox.
Change-Id: Ia514ccb53d93b1e11db0f89d8580319ebb411c14

@afmckinney @halatmit This fixes #296 by provided RequestFocus to both PasswordTextBox and EmailPicker

LGTM


Also uninstall Intel Graphics Command Center (Beta)

https://www.microsoft.com/store/productId/9NMR79ZTJFTC
And name should be IntelGraphicsCommandCenterBeta

Thanks, I will push the change soon.


Quid of sugared ops:: traits and GAT-ifying them

Based on the "GAT motivation" discussion over Zulip, and more precisely, around this question (archive link for those not on Zulip); people have started pondering about the idea that traits representing some of our sugary operations, such as […]-indexing, or deref-coercions, could maybe be GAT-ified in some retro-compatible fashion, so that they not be required to necessarily yield & or &mut references respectively.
Motivation
Plenty of examples in that Zulip thread; but people can also provide some to this very GH "issue".
But to summarize the main ones:

custom (re-)borrowing (e.g., Pin<&mut _>) could be featured with a GAT-ified Deref{,Mut}), and more general borrowing (e.g., &mut pinned_box being able to coerce to pinned_box.as_mut());

custom indexing/slicing.

without involving unsafe or other RefCast-like approaches;
when the reference type does not necessarily have the layout of a Rust reference (e.g., more embedded data (could be solved by ptr_metadata), or FFI requirements).
when other GAT APIs become widespread, and thus types such as <Ty as Trait>::Gat<'lt> become more common.

Questions:

What would exactly be the semantics of a GAT-ified operator such as Index{,Mut} (I suspect the same concerns apply to Deref{,Mut})?
indexable[idx]

is actually sugar for a *-dereference (to a place expression) of the &Index::Output or &mut Index::Output (depending on the kind of usage of the place), so the starting point of these traits is &indexable[idx] or &mut indexable[idx].
Wouldn't GAT-ifying this result in either:

reversing the relationship;
and/or having &indexable[idx] not yield a &T (and same for &mut).
This last idea seems like the most likely solution? Maybe?

How could the change be made in a retro-compatible fashion? I suspect we'll need new traits, to be the really sugared ones, and have the current ones be subsets which blanketly implement the new ones.

Whoops, I raced with #2, lemme move this there


scan with a specific timestamp range

Hi, may I ask can we scan with a specific timestamp range? I have found no api for this.

hrpc.TimeRangehttps://pkg.go.dev/github.com/tsuna/gohbase/hrpc#TimeRange

Got it. Many thanks


MB-6137: make all non-migrations containers use crud psql role in prd

Description
This makes all non-migrations containers use the low privileged PostgreSQL role (crud) when interacting with the RDS database. This change only applies to the staging environment.
I applied this to experimental successfully: https://github.com/transcom/mymove/pull/5701
I applied this to staging successfully: https://github.com/transcom/mymove/pull/5702
Setup
This change is only run via CircleCI after merging to master.
Code Review Verification Steps

[x] If the change is risky, it has been tested in experimental before merging.
[x] Tested in the Experimental environment (for changes to containers, app startup, or connection to data stores)
[x] Have the Jira acceptance criteria been met for this change?

References

Jira story for this change

Messages

:book:
:link: MB-6137

  Generated by :no_entry_sign: dangerJS against f4730f8f67613a6278034b56c8913ca214b3a1c6

Messages

:book:
:link: MB-6137

  Generated by :no_entry_sign: dangerJS against f4730f8f67613a6278034b56c8913ca214b3a1c6


Link "preload": how to?

Using <link rel="preload" href="bundle.js" as="script"> could be useful for preloading the bundle, but we need to handle this for module.bundle.js and bundle.js to avoid the loading of useless bundle.
https://developer.mozilla.org/en-US/docs/Web/HTML/Preloading_content

dont forget to include the fallback for "preload".
And i dont understand your question :S

It's more like a reminder. I don't want both bundle preloaded, but only the one is needed for the user's browser. I need to investigate if we can discern the type of browser using the link preload tag. Do you have some hints?

You can use the Preload-Tag without a Browser detection.
It's the same as CSS. If the Browser can use the tag, they ignore it. You only need this to tags
`


1.4.12

Hi @rockb1017, looks like the chart archive and metadata is missing in this PR, compared to the 1.4.11 PR.


Support MP4 Video Previews

If an mp4 or other web-supported video format exists, it would be nice to be able to preview the video inside of the VS Code editor. This feature would look similar to how a GIF might be previewed except with a play head.
You may commonly have video files as part of your directory if they are part of your blog or static site.

See also #72280, #87706

Ok, it makes sense. I will close this issue.


Python 3.11 support

Blockers:

[x] orjson build fails on arm64
[x] PyTezos doesn't support py311
[x] pydantic v1.10.4

6.5 branch unlikely to get Python 3.11, and for 7.0 everything works out of the box. Closing until it's time to bump Python in next.


⚠ Thumbnails API Endpoint has degraded performance

In 3007e38, Thumbnails API Endpoint (https://thumbnails.roblox.com/v1/assets?assetIds=82738847&format=Png&isCircular=false&size=30x30) experienced degraded performance:

HTTP code: 200
Response time: 1053 ms

Resolved: Thumbnails API Endpoint performance has improved in 621d799.


The instructions to integrate with electron-packager aren't working

Here's my build file:
import packager from 'electron-packager'
import rebuild from 'electron-rebuild'

const extraModules = ['realm']
const onlyModules = []
const force = true

packager({
    dir: 'build',
    out: 'out',
    overwrite: true,

    afterCopy: [(buildPath, electronVersion, platform, arch, callback) => {
        rebuild({ buildPath, electronVersion, arch, extraModules, onlyModules, force })
        .then(() => callback())
        .catch((error) => callback(error));
    }]
}, function done_callback (err, appPaths) {
    console.log(err);
    console.log(appPaths);
 })

It works correctly except realm extra module isn't getting rebuilt.
Am I missing something?

@itwy What package manager are you using?

electron-rebuild has had many bug fixes and a module resolution rewrite since this issue was raised, if it's still an issue please ping me below and I will re-open


reflow doesnt work if plugin ran on table with tbody which is later added

tbody jumps when you start scrolling if it's not created before the first floatThead and scrolls smoothly if declared before?
( scrolling behavior http://jsfiddle.net/9eo8gjag/7/ vs http://jsfiddle.net/9eo8gjag/6/ )

an idea for a fix is to add a lazy flag to the floatThead data i attach to the element and not init if there is no thead or tbody, on reflow check the lazy flag and init if lazy is true

also, this is related:
http://jsfiddle.net/9eo8gjag/9/
see fiddle for bug

Sorry me, I am new on GitHub and dont know how to create new theme. I found a new bud of your script: Excel export don't work properly with it. In exported table.xls i can see only  content without . There is a part of export script (creates template for Excel):
template = '{table}'

Sorry for my English, hope you will understand me


List of all possible options

I think it's a good idea to extend Readme file and add small table with short description of supported options. What do you think? I can create pull request with it later :-)

I've just done it in #9 :)


Callback never called from query.find()

I'm using Parse JavaScript SDK v1.6.12. On one of my queries promise seems never resolved. I can see the result with corect data in Network/Response tab via Developer Tools in Chrome, but callback is never called.
Exactly same query to different table/class works fine...
The only difference I can see is in response headers where in working query Content-Encoding is gzip, in the not working one this is missing. Not sure if this is relevant ...

my fault, misspelled success ... (sucess)


Timeline events should use dates to order rather than rely on their position in an array.

Considering this component acts as a timeline and date ranges are provided, this could be used for sorting the timeline elements in chronological order.
I was able to get this working in my own project, and will look at opening a PR for this.

I think this would be good as an optional configuration, but it should also be able to sort by the original position in array.

What would happen if the dates overlapped?


Check signatures after using repo-{add,remove}

It seems they don't care about GPG succeeding, so we have to check
ourselves.

lgtm, thank you!


Add Synapse Ingestion Page

🚀 Deployed on https://6359b11a1ac24842c02d9ea8--cozy-fox-0defec.netlify.app


Support Bitcoin Core 0.16.3

Just installed this and it downloaded 0.16.2 when I installed it.  0.16.2 contains a vulnerability.
See: https://bitcoincore.org/en/2018/09/18/release-0.16.3/

fixed in https://github.com/greenaddress/abcore/releases/tag/v0.67alphaPoC