fix: html reporter should use options.destination if passed in

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


AI binding support

implemented in a project and it seems to work well 😁

Hi @danielroe I am not sure if I should post my problem here, but I came across your comment here, so I post it here. I apologize if I make a mess 🙏
I am having trouble with the Cloudflare AI integration. Here's the code from "server/api/query/index.get.ts"
`
import { Ai } from "@cloudflare/ai";
export default eventHandler(async (event) => {
const c = event.context;
const llmEmbeddings =<EMAIL_ADDRESS>const llmChatbot = "@cf/meta/llama-2-7b-chat-int8";
const query = getQuery(event);
let question = query.userInput;
const ai = new Ai(c.cloudflare.env.AI, { sessionOptions: { c } }); // sessionOptions is to allow chat session
`
and I got this error - ERROR  [nuxt] [request error] [unhandled] [500] Cannot stringify a function
this works fine with my Nuxt app. Please help.
Thanks!
Gary

shouldn't it be in another repository? like @nuxthub/ai? (related project from Daniel: https://www.twitch.tv/videos/2127437533?t=01h00m20s)

Here's a patch to get AI bindings in a NuxtHub project locally. Also was fun being in Daniel's stream chat sharing what I knew to help :P

Create patches/<EMAIL_ADDRESS>with the following contents:

diff --git a/dist/module.d.ts b/dist/module.d.ts
index 12db941b1043787ded77cf076333f00473e57d68..4d276743b3d553d2eda18622d092dd28929f37db 100644
--- a/dist/module.d.ts
+++ b/dist/module.d.ts
@@ -34,6 +34,13 @@ interface ModuleOptions {
      * @see https://hub.nuxt.com/docs/storage/kv
      */
     kv?: boolean;
+    /**
+     * Set `true` to enable AI for the project.
+     *
+     * @default false
+     * @see https://developers.cloudflare.com/workers-ai/
+     */
+    ai?: boolean;
     /**
      * Set to `true`, 'preview' or 'production' to use the remote storage.
      * Only set the value on a project you are deploying outside of NuxtHub or Cloudflare.
diff --git a/dist/module.mjs b/dist/module.mjs
index 082343c9647404dd7ff4d6be7c99b541ec00ee5f..e2bfc2f7f8fbacd240512d47ee6dd1ac860b5fc9 100644
--- a/dist/module.mjs
+++ b/dist/module.mjs
@@ -49,6 +49,11 @@ function generateWrangler(hub) {
       database_id: "default"
     }];
   }
+  if (hub.ai) {
+    wrangler["ai"] = {
+        binding: "AI"
+    };
+  }
   return stringifyTOML(wrangler);
 }
 function addDevtoolsCustomTabs(nuxt, hub) {
@@ -129,6 +134,7 @@ const module = defineNuxtModule({
       cache: false,
       database: false,
       kv: false,
+      ai: false,
       // Other options
       version,
       env: process.env.NUXT_HUB_ENV || "production",

Edit package.json and add the pnpm section.

{
  ...
  "dependencies": {
    "@nuxthub/core": "^0.6.10",
    ...
  },
  "pnpm": {
    "patchedDependencies": {
      "<EMAIL_ADDRESS>"patches/<EMAIL_ADDRESS>    }
  }
}

Apply patch with pnpm install
Enable AI in your NuxtHub config inside nuxt.config.ts

export default defineNuxtConfig({
  hub: {
    cache: true,
    database: true,
    ai: true,
  },
  ...
})

Start your dev server pnpm dev and login to Cloudflare if prompted by Wrangler. Workers AI uses account quota even in local development. If you're not prompted to login to Wrangler (since Wrangler logs not shown) then create a dummy Workers AI template and start it with C3 so you can login, then delete the local files after. - https://developers.cloudflare.com/workers-ai/get-started/workers-wrangler/


Default font on frontend to SF Mono?

Because we have too much problems with ligature, should we change the default font on the frontend app to be SF Mono instead of JetBrains Mono?
Also should we dump the use of NerdFont and use the regular font instead?
How about adding more fonts? Lol
cc @elianiva

#75

kenapa ditutup? frontend belom di implement

oh ternyata kamu udah implement, nvm


Implement and test end-to-end image builder workflow in core shared services

User Story
As a modernisation platform team engineer
I want to be able to use Image Builder in core-shared-services
So that I can demonstrate the workflow from image builder resource creation to the generation of shared AMIs
As an engineer consuming the modernisation platform for my application
I want to be able to see how Image Builder can be used
To create my AMIs according to agreed design and recommended best practices and conventions
Value
This story gives us code-driven deployment of Image Builder resources (including components, recipes, pipelines, infrastructure configs and distribution settings) that result in generated and shared AMIs. It allows us to see with good clarity how all the resources fit together and we can utilise them through Terraform to define and build AMIs
Questions / Assumptions
This story builds on design stories #1059 and #1125 to implement and test the definition and generation of AMIs.
At the time of writing this story, we assume

we can utilise image builder natively to effectively share generated AMIs
approaching the management of Image builder resources with Terraform does not throw up any unforeseen blockers from a technical or process point of view

Definition of done

[ ] readme has been updated
[ ] user docs have been updated
[ ] implemented design showing how image builder resources can be deployed through terraform with surrounding process supporting the creation, management and consumption of AMIs
[ ] Github action workflows deploying image builder resources into core-shared-services with AMIs shared across required accounts
[ ] Demo to mod platform team

Reference
How to write good user stories

Duplicate this has been done


cargo install probe-rs-tools warns about yanked zip dependency

$ cargo install --locked probe-rs-tools
    Updating crates.io index
  Installing probe-rs-tools v0.24.0
    Updating crates.io index
warning: package `zip v1.2.3` in Cargo.lock is yanked in registry `crates-io`, consider running without --locked
    Updating crates.io index
  Downloaded termtree v0.4.1
  Downloaded zero v0.1.3
  Downloaded strum v0.26.2
  ...

Looks like all of the zip 1.2.x and 1.3.x releases have been yanked; I wasn't able to find a reason posted anywhere obvious.

Thankfully yanked does not mean deleted, and this should not cause problems.

Thanks @bugadani !


Getting both ActiveRecord objects together with highlights for a query

Is your feature request related to a problem? Please describe.
I'm currently trying to use Chewy to do the following with a query:

Get the resulting ActiveRecord objects
Get the highlights as well

However, it seems i can only do one or the either. Is there any way I can do both at the same time?
PS: It'll also be nice to be able to paginate this. Maybe there's a way to use the Search function for this?
Describe the solution you'd like
I'd like to be able to do something like the following:
BooksIndex.query(
  query_string: {
    fields: [:name, :description],
    query: query,
    default_operator: "or"
  }
).highlight(
  fields: { "*": { force_source: true } }
)
.objects_with_highlights # take note of this

And get back ActiveRecord objects of the matching records along with a highlight attribute loaded into the object perhaps? Or any other way that might be more efficient.
Describe alternatives you've considered
Currently, what I'm doing is to index all the attributes of the model and using "_source" to access them. However, as more attributes get added, I would have to re-index the entire dataset every time I want it to be accessible in my search payload. This would become unfeasible once we have too much data.
Additional context
None but happy to provide more information to paint a clearer picture.
PS: I'd be happy to work on a PR too if someone could guide me 😁

Hi @gczh 👋 !
Did you try using object_hash?

In case when it is necessary to iterate through both of the wrappers and objects simultaneously, object_hash method helps a lot:

scope = CitiesIndex.load(scope: -> { active })
scope.each do |wrapper|
  scope.object_hash[wrapper]
end

Closing this for now, feel free to re-open the issue if you have any questions.


Queue status in administration

Description
If you have a large shop running with a lot of modifications, it's possible that you may run into problems with workers.
This is a necessary information for the shop administrator and should be visible in the administration interface.
Professional setups might use Grafana, but some basic stuff in the administration would be great.
Example
Something like the Ruby Sidekiq Dashboard would be great.

Since 6.2.0 you can see the indexing status in the administration notification.


Images not deleted while mapping

Example:
Deleted one image of a building. Replaced it with three images of three buildings. Moved down the tile. Suprised to see the old deleted image of one building still there, and none of the three new buildings. Deleted the old image again, mapped the three new images again. Saved. There are now three buildings on top of three buildings. Deleted all the images and remapped them. Saved.
Happened throughout the session. Saved frequently. Unlocked the task, locked it again several times but issue continued.
OS 10.6.8  Firefox MacBook Pro  Fast internet speed.
http://tasks.hotosm.org/project/689

dup of #2667 related to save issues


Module not found: Can't resolve 'next/dist/next-server/server/api-utils.js' in '.../node_modules/next-test-api-route-handler/dist/esm'

The problem
Just updated next.js to version 12 and now the project build is failing.
Curiously the tests are still passing, but "next build" fails with the following error:
$ next build --debug
 ******* next.config.js building:
            NODE_ENV: production
                 ENV: localhost
info  - Checking validity of types...
warn  - The Next.js plugin was not detected in your ESLint configuration. See https://nextjs.org/docs/basic-features/eslint#migrating-existing-config
info  - Creating an optimized production build...
warn  - Disabled SWC as replacement for Babel because of custom Babel configuration ".babelrc" https://nextjs.org/docs/messages/swc-disabled
info  - Using external babel configuration from /home/runner/my-project/.babelrc
Failed to compile.

./node_modules/next-test-api-route-handler/dist/esm/index.mjs
Module not found: Can't resolve 'next/dist/next-server/server/api-utils.js' in '/home/runner/my-project/node_modules/next-test-api-route-handler/dist/esm'

Import trace for requested module:
./src/pages/api/my-endpoint.test.ts

./node_modules/next-test-api-route-handler/dist/esm/index.mjs
Module not found: Can't resolve 'next-server/dist/server/api-utils.js' in '/home/runner/my-project/node_modules/next-test-api-route-handler/dist/esm'

Import trace for requested module:
./src/pages/api/my-endpoint.test.ts

Reproduction steps
I guess you just need to create a test and import next-test-api-route-handler, like this:
import { testApiHandler } from 'next-test-api-route-handler'
and then run next build.

Additional context

OS: OSX
Node version: 12.22.7

@hems By chance are you using npm 6.x? UNMET PEER DEPENDENCY<EMAIL_ADDRESS>is super weird.

yes, i'm using 6.14.15... i'm a supposed to be using a newer versiono? 😓

NPM doesn't install peer dependencies by default before version 7, along with other little changes to how npm@>=7 organizes installs and records them to package-lock.json. It'd be a little strange if you didn't have Next.js itself installed already (I don't see it in the output of your npm list... output above), but if you don't, you should ensure it's installed such that no "unmet peer dependency" errors occur.
Also, what output do you get when running npm list --depth=1 | grep next (or its Windows equivalent) at your project root?
I'd expect to see something like this:
npm list --depth=1 | grep next
...
├─┬<EMAIL_ADDRESS>│ ├──<EMAIL_ADDRESS>deduped
...
├─┬<EMAIL_ADDRESS>│ ├──<EMAIL_ADDRESS>│ ├──<EMAIL_ADDRESS>│ ├──<EMAIL_ADDRESS>│ ├──<EMAIL_ADDRESS>...

Hmm, regardless, it looks like there is something special about node 12.x and 14.x. Getting closer...

@hems Seems the problem was three-fold:

I noticed in your report you're using node@12. Turns out there were various little incompatibilities with node@14 and node@12. Originally I thought to run integration tests over all Next.js versions but not across all supported Node.js versions too 🤦🏿♂.

Webpack would compile out the import fallback code under certain circumstances.

node@<15 ships with npm@<7, which infamously does not support automatic peer dependency installation. For those using an old version of Node.js/NPM, you have to manually install next (whatever version) and its peer dependencies, otherwise NTARH will fail to import next even if it is available. I've updated the README.md to reflect this.

Installing<EMAIL_ADDRESS>should resolve this issue. If it doesn't, feel free to reopen. Thanks again for this bug report, it resulted in a major fix 👍🏿

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Short solution needed: "Redis auth usage" (lua-redis)

Please help us write most modern and shortest code solution for this issue:
Redis auth usage (technology: lua-redis)
Fast way
Just write the code solution in the comments.
Prefered way

Create pull request with a new code file inside inbox folder.
Don't forget to use comments to make solution explained.
Link to this issue in comments of pull request.

Redis auth (user/password) usage


Azure Firewall - Add option to toggle between rule count and actual rules

When you run ARI and it detects a firewall, it will log counts of the different type of rules instead of the actual rules. I think it would be pretty valuable from an inventory standpoint to have the actual rules logged as well.
Under AzureFirewall.ps1:
                            'NAT Rules'                         = [int]$data.natRuleCollections.Count;
                        'Application Rules'                 = [int]$data.applicationRuleCollections.Count;
                        'Network Rules'                     = [int]$data.networkRuleCollections.Count;

I understand any given firewall could have a ton of rules, so maybe there could be a switch or parameter that can toggle between RuleCount or ActualRules, depending on the needs of the user running ARI. Thank you.

Hello there @MatthewTownsend ,
Thanks for the feedback, I will begin working in the next improvements for the tool mid April and I believe we can think in a way to include this. We also need to fix the Load Balancer reports, since we have the exact same problem but in the other situation, we are actually bringing every single rule and this module is breaking the script for larger environments.
But since this is definably an issue we must address I will make sure to include Azure Firewall in the discussion.
Thanks

Hello there @MatthewTownsend
I just made considerable improvements in the Azure Firewall module. Can you download and try the latest version of the script and see how it goes?
Thanks


Add Tobiko image

This patch adds the Tobiko container image. Tobiko can be found at https://opendev.org/x/tobiko, and it is an openstack system testing framework.

The current version of the patch does not work, I uploaded it so I could ask you guys a little guidance with it. When I run the following:
sudo openstack tcib container image build --config-file containers_tobiko.yaml --repo-dir /tmp/repos/ --registry quay.io --volume /usr/share/tcib/container-images:/usr/share/tcib/container-images:z --namespace podified-antelope-centos9 --debug
and containers_tobiko.yaml has the following:
container_images:
- imagename: quay.io/podified-master-centos9/openstack-tobiko:current-podified

it seems like the user "tobiko" is not being created properly:
+ _USERS_TO_CREATE=tobiko
+ declare -A _SUPPORTED_USERS
+ _SUPPORTED_USERS['aodh']='aodh 42402 42402 /var/lib/aodh kolla'
..... (without tobiko)
+ for _USER_TO_CREATE in $_USERS_TO_CREATE
+ _EXTRA_GROUPS_ARG=
+ _EXTRA_PERMS=
+ _HOME_ARGS=
++ echo
++ awk '{ print $1 }'
+ _NAME=
++ echo
++ awk '{ print $2 }'
+ _UID=
++ echo
++ awk '{ print $3 }'
+ _GID=
++ echo
++ awk '{ print $4 }'
+ _HOME_DIR=
++ echo
++ awk '{ print $5 }'
+ _EXTRA_GROUPS=
+ [[ '' != \t\o\b\i\k\o ]]
+ echo 'User tobiko was not found in the supported list'
User tobiko was not found in the supported list
+ exit 1```

I am not sure where I am missing here

recheck for debug

recheck

recheck

Closing this one as a new PR that includes changes from this has already been merged.


ReportActionItem: Set pointer events to none if pending action is delete

Details
ReportActionItem: Set pointer events to none if pending action is delete
Fixed Issues
$ https://github.com/Expensify/App/issues/14325
PROPOSAL: https://github.com/Expensify/App/issues/14325#issuecomment-1387148577
Tests

Open any chat
Type in a message (if none are written)
Verify that you can copy the message (using context menu actions)

[ ] Verify that no errors appear in the JS console

Offline tests

Delete the previous message
Verify that the message has been greyed-out
Verify that you can not copy the message (context menu should not be accssibble)

QA Steps
Same as Tests and Offline tests

[ ] Verify that no errors appear in the JS console

PR Author Checklist

[X] I linked the correct issue in the ### Fixed Issues section above
[X] I wrote clear testing steps that cover the changes made in this PR

[X] I added steps for local testing in the Tests section
[X] I added steps for the expected offline behavior in the Offline steps section
[X] I added steps for Staging and/or Production testing in the QA steps section
[X] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[X] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[X] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[X] I included screenshots or videos for tests on all platforms
[X] I ran the tests on all platforms & verified they passed on:

[X] Android / native
[X] Android / Chrome
[X] iOS / native
[X] iOS / Safari
[X] MacOS / Chrome / Safari
[X] MacOS / Desktop

[X] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[X] I followed proper code patterns (see Reviewing the code)

[X] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[X] I verified that comments were added to code that is not self explanatory
[X] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[X] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[X] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[X] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[X] I verified any copy / text that was added to the app is correct English and approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[X] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[X] I verified the JSDocs style guidelines (in STYLE.md) were followed

[X] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[X] I followed the guidelines as stated in the Review Guidelines
[X] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[X] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[X] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[X] I verified that if a function's arguments changed that all usages have also been updated correctly
[X] If a new component is created I verified that:

[X] A similar component doesn't exist in the codebase
[X] All props are defined accurately and each prop has a /** comment above it */
[X] The file is named correctly
[X] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[X] The only data being stored in the state is data necessary for rendering and nothing else
[X] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[X] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[X] All JSX used for rendering exists in the render method
[X] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[X] If any new file was added I verified that:

[X] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[X] If a new CSS style is added I verified that:

[X] A similar style doesn't already exist
[X] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)

[X] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[X] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[X] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[X] I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Screenshots/Videos

Web
https://user-images.githubusercontent.com/16493223/215522646-1b65c1c9-99d6-4cae-8821-96b87f96fcc2.mp4

Mobile Web - Chrome
https://user-images.githubusercontent.com/16493223/215522558-87fdd1f6-bb44-4c2b-b005-1181a19181f9.mp4

Mobile Web - Safari
https://user-images.githubusercontent.com/16493223/215522422-4aaa3b67-885f-4714-9e5b-163ec908dd9c.mp4

Desktop
https://user-images.githubusercontent.com/16493223/215522377-39bb3d47-9a76-4b00-ae09-3868ecd848a6.mp4

iOS
https://user-images.githubusercontent.com/16493223/215521962-2b6286a3-a29c-4ce4-bac7-ffb8c32a4d46.mp4

Android
https://user-images.githubusercontent.com/16493223/215521938-b92da1d6-882b-4372-a643-9cecc0d9f4bd.mp4

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by https://github.com/cristipaval in version: 1.2.63-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/thienlnam in version: 1.2.63-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


fix bug with rnn policy reconstruction, remove dependence on num_steps, fix smax conic obs space size

SMAX & MPE results are good. Hanabi only good for IPPO, something weird going on with MAPPO.
SMAX results
These are over 10 seeds, max and min win rate shown with the shaded region.

MPE
Returns for MPE simple spread

hanabi
top lines are IPPO, bottom lines MAPPO. @mttga and I will take a look at the cause of this

I've seen you reduced the number of envs for smax. How long does it take to train now? Nice to see good performances on MPE btw, it makes sense to increase the total timesteps there for IPPO. I think original MAPPO paper reports results on 2e7 on this env

ah yep will put that back up to 128, was at 16 for comparisons to mava as they use 16 envs across 8 workers. Yes it is! Ah cool will increase to that for the submission


Launched Encrypted Payload, but no connection

I installed the macro into a document, setup an EvilOSX listener, and opened the document (with macros enabled ofc). I was instantly notified by the listener that it launched a new encrypted payload, but the bot counter remained at 0. I have not been able to remedy this issue.

Thanks for reporting. I did some re-testing by generating EvilOSX paylaods a couple different ways and then trying the macros. I saw the exact same behavior you saw when using the EvilOSX GUI to generate a payload (i.e., python start.py and then generate the payload from that GUI). However, when I generate a payload using the "python start.py --builder" EvilOSX command the callback works fine and I can interact with the callback. Which method are you using for payload generation?

That's really odd because I'm using the command-line interface for payload generation. Also, wouldn't the payload file be the exact same regardless of whether it was generated by the CLI or GUI?

Yeah I think EvilOSX itself might have a glitch in how the GUI generates the payload versus the CLI generation...I even tried just running the python scripts from each manually and the one from the GUI error'd out while the CLI generated payload worked.

Still weird that the CLI build is not working for me. I'll try it again and get back to you.

Tested the macro generator on a freshly made EvilOSX payload (through CLI), using base64, hex, and Mac firewall on/off. Nothing worked. Each time, EvilOSX notified me that it created a new encrypted payload, yet not bot connected and nothing was installed on the victim machine

Strange...I am not able to reproduce this behavior when generating the payload via CLI. I will have some colleagues independently try to follow the steps and see if they encounter the same problem you are seeing. If so, I will update here.

You might have to make the payload executable

You might have to make the payload executable

I got the same problem. Actually, I found the macro will generate a payload in ~/Library/Containers/com.microsoft.Word/Data/Library/Containers/ .

I got the same problem. Actually, I found the macro will generate a payload in ~/Library/Containers/com.microsoft.Word/Data/Library/Containers/ .


Use correct preprocessor macro for Mac Catalyst

This was introduced in #7719 to fix a warning that was generated when using Remote Config on Catalyst, however, the PR was not using the correct preprocessor macro for Mac Catalyst.
This is validated by the system-provided TargetConditionals.h header which states:
 *  TARGET_OS_*
 *  These conditionals specify in which Operating System the generated code will
 *  run.  Indention is used to show which conditionals are evolutionary subclasses.
 *
 *  The MAC/WIN32/UNIX conditionals are mutually exclusive.
 *  The IOS/TV/WATCH conditionals are mutually exclusive.
 *
 *
 *      TARGET_OS_WIN32           - Generated code will run under 32-bit Windows
 *      TARGET_OS_UNIX            - Generated code will run under some Unix (not OSX)
 *      TARGET_OS_MAC             - Generated code will run under Mac OS X variant
 *         TARGET_OS_OSX          - Generated code will run under OS X devices
 *         TARGET_OS_IPHONE          - Generated code for firmware, devices, or simulator
 *            TARGET_OS_IOS             - Generated code will run under iOS
 *            TARGET_OS_TV              - Generated code will run under Apple TV OS
 *            TARGET_OS_WATCH           - Generated code will run under Apple Watch OS
 *            TARGET_OS_BRIDGE          - Generated code will run under Bridge devices
 *            TARGET_OS_MACCATALYST     - Generated code will run under macOS
 *         TARGET_OS_SIMULATOR      - Generated code will run under a simulator
 *
 *      TARGET_OS_EMBEDDED        - DEPRECATED: Use TARGET_OS_IPHONE and/or TARGET_OS_SIMULATOR instead
 *      TARGET_IPHONE_SIMULATOR   - DEPRECATED: Same as TARGET_OS_SIMULATOR
 *      TARGET_OS_NANO            - DEPRECATED: Same as TARGET_OS_WATCH
 *
 *    +---------------------------------------------------------------------+
 *    |                            TARGET_OS_MAC                            |
 *    | +---+ +-----------------------------------------------+ +---------+ |
 *    | |   | |               TARGET_OS_IPHONE                | |         | |
 *    | |   | | +---------------+ +----+ +-------+ +--------+ | |         | |
 *    | |   | | |      IOS      | |    | |       | |        | | |         | |
 *    | |OSX| | |+-------------+| | TV | | WATCH | | BRIDGE | | |DRIVERKIT| |
 *    | |   | | || MACCATALYST || |    | |       | |        | | |         | |
 *    | |   | | |+-------------+| |    | |       | |        | | |         | |
 *    | |   | | +---------------+ +----+ +-------+ +--------+ | |         | |
 *    | +---+ +-----------------------------------------------+ +---------+ |
 *    +---------------------------------------------------------------------+

@googlebot I signed it!


Add Roon now playing app

Roon now playing app

Description
Connects to the http api extension for roon and serves info about the currently playing zone's song, album and artist.  See https://hub.docker.com/repository/docker/jboulter11/roon-http-api/general for info about http api.
Copilot

🤖 Generated by Copilot at 77d65aa
Summary
🎵🌐📝

This pull request adds a new applet for displaying the current song information from a roon music server. It includes the roon.star file with the applet logic and rendering, and the manifest.yaml file with the applet metadata and configuration.

roon applet born
manifest and star files made
autumn music flows

Walkthrough

Add a new applet for displaying the current song, album, and artist from a roon music server (link, link)
Create a manifest file manifest.yaml with the applet metadata and configuration fields (link)
Create a logic and rendering file roon.star with the main and get_schema functions (link)

I have read the CLA Document and I hereby sign the CLA

I didn't realize that apps ran on your servers.  If I'd known that I wouldn't have done this work, the intention is to communicate with an in-home server from the Tidbyt device itself.
It would generally not be safe to expose a port to this specific API to the internet, so I can't ask users to do that, since I certainly wouldn't.  This whole PR will be scrapped and I'll probably just return my Tidbyt when it arrives.


[VTK/GLEW] Fix Regression of VTK with newer CMake Versions

Newer CMake Versions have a new Version of FindGLEW which loads just the config and forgets to define the common GLEW variables. The wrapper now takes care to add those variables back in. Should probably be fixed in either the GLEW configs or in CMakes FindGLEW since it promises to define those variables.

closes #7519
related regression see #7801

It should be a good idea to submit this patch to upstream cmake FindGLEW as well.

Reported to CMake as https://gitlab.kitware.com/cmake/cmake/issues/19662

It failed with 'Download Build Artifacts' steps in linux testing, it's a temp issue, requene it.

@grdowns, could you priority this PR to review and merge this PR? it blocked many people.

Apologies for the wait! LGTM -- thanks everyone for the patience


retrieve user events

I can pull products with retail_v2_generated_product_service_get_product_sync.py. But I couldn't find a script that pulls the user events.

I was able to get the events using the recommendationengine API:
`from google.cloud import recommendationengine_v1beta1
import proto
from google.oauth2 import service_account
import json
Create a client
gbq_credentials = service_account.Credentials.from_service_account_file("credentials.json")
client = recommendationengine_v1beta1.UserEventServiceClient(credentials=gbq_credentials)
request = recommendationengine_v1beta1.ListUserEventsRequest(
parent="projects/project_id/locations/global/catalogs/default_catalog/eventStores/default_event_store",
)
Make the request
page_result = client.list_user_events(request=request)
Handle the response
events=[]
for i,response in enumerate(page_result):
print(i)
events.append(json.loads(proto.Message.to_json(response)))
`


merge from arlac77/template-github-action,arlac77/template-kronos-component

.github/workflows/ci.yml

chore(deps): add 14.10.1 remove 14.10.0 (jobs.build.strategy.matrix.node-version)

.github/workflows/update_readme_api.yml

chore: add 14.10.1 (jobs.update_readme_api.steps.with.node-version)

Codecov Report

Merging #685 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #685   +/-   ##
=======================================
  Coverage   99.08%   99.08%
=======================================
  Files           1        1
  Lines         109      109
  Branches        9        9
=======================================
  Hits          108      108
  Misses          1        1

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 981af74...12ca0fa. Read the comment docs.


Add Category filters on route change

Bug was available when choosing color filter in category, then navigating to other page (eg. product) and then navigating backwards to category.
After this action color is selected in sidebar but filters are NOT applied.
Short description and why it's useful
Removes bug

[X] Test version (https://test.storefrontcloud.io) - this is a new feature or improvement for Vue Storefront. I've created branch from develop branch and want to merge it back to develop
[ ] RC version (https://next.storefrontcloud.io) - this is a stabilisation fix for Release Candidate of Vue Storefront. I've created branch from release branch and want to merge it back to release
[ ] Stable version (https://demo.storefrontcloud.io) - this is an important fix for current stable version. I've created branch from hotfix or master branch and want to merge it back to hotfix

Upgrade Notes and Changelog

[x] No upgrade steps required (100% backward compatibility and no breaking changes)
[ ] I've updated the Upgrade notes and Changelog on how to port existing VS sites with this new feature

IMPORTANT NOTICE - Remember to update CHANGELOG.md with description of your change
Contribution and currently important rules acceptance

[ ] I read and followed contribution rules

Closing in favour of #3682 :)


nemo_ckpt_convert.py prompt table conversion when TP is not 1

Branch/Tag/Commit
main
Docker Image Version
nvcr.io/ea-bignlp/bignlp-training:22.08.01-py3
GPU name
V100
CUDA Driver
470.141.03
Reproduced Steps
In nemo_ckpt_convert.py line 644 model_weights_ckpt = "model_weights.ckpt" and then line 651 os.path.join(args.prompt_saved_dir, model_weights_ckpt), you make an assumption that prompt tunning was carried out with TP = 1.

If TP > 1 then the folder structure is differnt. For every of the ranks a folder is created (e.g. mp_rank_00  mp_rank_01 in case of TP=2). In that case the ckpt files are not in the folder listed above but in the mp_rank_xx folders. They are the same so just mp_rank_00  could be used.

I have not tested for PP > 1 or for PP > and TP > 1 but I would imagine this will also be the case.

The folder issue should be handled in unpack_nemo_ckpt by NeMo.

The above is not related to unpack_nemo_ckpt which is working just fine. What I was trying to say is that unpack_nemo_ckpt creates differnt folder structure when the prompt_table is created by a job that has Tensor Paralelism of 1 (in this case the "model_weights.ckpt" is in the folder the code is pointing at) and it is creating a different folder structure if Tensor Paralelism is greater than 1 (in that case "model_weights.ckpt" is not where the code is looking, instead there are folders called mp_rank_00 to mp_rank_xx each with a seperate "model_weights.ckpt" but all containing the same prompt_table).
You couple lines of conditional logic to check TP and:

If TP = 1 - keep the existing code
if TP > 1 look into the mp_rank_00 instead

I think the same will apply if there is PP > 1


Kroach/oasis 2519 release20 master

This objective-c-sdk P.R. will add to master branch the 2.0.x changes
that Optimizely released in objective-c-sdk 2.0 GA .

Coverage remained the same at 97.403% when pulling c6de74d84a9fc959dae3ce4d0f6de902b909b7dd on kroach/OASIS-2519-release20-master into fc758c3acf0e371dc5c3de8127866cde20fda450 on master.


GPU not accepted?

Not sure what is going on here.  I am running the new NVIDIA 3080 TI.  It says my GPU is not supported which I have never had happen to me before even on older codebases.  :/
`
Traceback (most recent call last):
File "/home/killab/anaconda3/envs/HDNet/lib/python3.7/site-packages/tensorflow/python/client/session.py", line 1356, in do_call
return fn(*args)
File "/home/killab/anaconda3/envs/HDNet/lib/python3.7/site-packages/tensorflow/python/client/session.py", line 1339, in run_fn
self.extend_graph()
File "/home/killab/anaconda3/envs/HDNet/lib/python3.7/site-packages/tensorflow/python/client/session.py", line 1374, in extend_graph
tf_session.ExtendSession(self.session)
tensorflow.python.framework.errors_impl.InvalidArgumentError: Cannot assign a device for operation hourglass_stack_fused_depth_prediction/conv1/weights/Initializer/truncated_normal/TruncatedNormal: Could not satisfy explicit device specification '' because the node {{colocation_node hourglass_stack_fused_depth_prediction/conv1/weights/Initializer/truncated_normal/TruncatedNormal}} was colocated with a group of nodes that required incompatible device '/device:GPU:0'. All available devices [/job:localhost/replica:0/task:0/device:CPU:0, /job:localhost/replica:0/task:0/device:XLA_CPU:0].
Colocation Debug Info:
Colocation group had the following types and supported devices:
Root Member(assigned_device_name_index=-1 requested_device_name='/device:GPU:0' assigned_device_name='' resource_device_name='/device:GPU:0' supported_device_types=[CPU] possible_devices_=[]
L2Loss: CPU XLA_CPU
Assign: CPU
VariableV2: CPU
Identity: CPU XLA_CPU
Add: CPU XLA_CPU
Mul: CPU XLA_CPU
TruncatedNormal: CPU XLA_CPU
Const: CPU XLA_CPU
Colocation members, user-requested devices, and framework assigned devices, if any:
hourglass_stack_fused_depth_prediction/conv1/weights/Initializer/truncated_normal/shape (Const)
hourglass_stack_fused_depth_prediction/conv1/weights/Initializer/truncated_normal/mean (Const)
hourglass_stack_fused_depth_prediction/conv1/weights/Initializer/truncated_normal/stddev (Const)
hourglass_stack_fused_depth_prediction/conv1/weights/Initializer/truncated_normal/TruncatedNormal (TruncatedNormal)
hourglass_stack_fused_depth_prediction/conv1/weights/Initializer/truncated_normal/mul (Mul)
hourglass_stack_fused_depth_prediction/conv1/weights/Initializer/truncated_normal (Add)
hourglass_stack_fused_depth_prediction/conv1/weights (VariableV2) /device:GPU:0
hourglass_stack_fused_depth_prediction/conv1/weights/Assign (Assign) /device:GPU:0
hourglass_stack_fused_depth_prediction/conv1/weights/read (Identity) /device:GPU:0
hourglass_stack_fused_depth_prediction/conv1/weights/Regularizer/l2_regularizer/scale (Const) /device:GPU:0
hourglass_stack_fused_depth_prediction/conv1/weights/Regularizer/l2_regularizer/L2Loss (L2Loss) /device:GPU:0
hourglass_stack_fused_depth_prediction/conv1/weights/Regularizer/l2_regularizer (Mul) /device:GPU:0
 [[{{node hourglass_stack_fused_depth_prediction/conv1/weights/Initializer/truncated_normal/TruncatedNormal}}]]

During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "HDNet_Inference.py", line 64, in
tf.global_variables_initializer().run()
File "/home/killab/anaconda3/envs/HDNet/lib/python3.7/site-packages/tensorflow/python/framework/ops.py", line 2679, in run
run_using_default_session(self, feed_dict, self.graph, session)
File "/home/killab/anaconda3/envs/HDNet/lib/python3.7/site-packages/tensorflow/python/framework/ops.py", line 5614, in run_using_default_session
session.run(operation, feed_dict)
File "/home/killab/anaconda3/envs/HDNet/lib/python3.7/site-packages/tensorflow/python/client/session.py", line 950, in run
run_metadata_ptr)
File "/home/killab/anaconda3/envs/HDNet/lib/python3.7/site-packages/tensorflow/python/client/session.py", line 1173, in run
feed_dict_tensor, options, run_metadata)
File "/home/killab/anaconda3/envs/HDNet/lib/python3.7/site-packages/tensorflow/python/client/session.py", line 1350, in do_run
run_metadata)
File "/home/killab/anaconda3/envs/HDNet/lib/python3.7/site-packages/tensorflow/python/client/session.py", line 1370, in do_call
raise type(e)(node_def, op, message)
tensorflow.python.framework.errors_impl.InvalidArgumentError: Cannot assign a device for operation hourglass_stack_fused_depth_prediction/conv1/weights/Initializer/truncated_normal/TruncatedNormal: Could not satisfy explicit device specification '' because the node node hourglass_stack_fused_depth_prediction/conv1/weights/Initializer/truncated_normal/TruncatedNormal (defined at /home/killab/ml/models/ShapeGeneration/HDNet_TikTok/hourglass_net_depth.py:28) placed on device Device assignments active during op 'hourglass_stack_fused_depth_prediction/conv1/weights/Initializer/truncated_normal/TruncatedNormal' creation:
with tf.device(None): </home/killab/anaconda3/envs/HDNet/lib/python3.7/site-packages/tensorflow/python/ops/variables.py:1696>
with tf.device(/gpu:0): </home/killab/ml/models/ShapeGeneration/HDNet_TikTok/hourglass_net_depth.py:26>  was colocated with a group of nodes that required incompatible device '/device:GPU:0'. All available devices [/job:localhost/replica:0/task:0/device:CPU:0, /job:localhost/replica:0/task:0/device:XLA_CPU:0].
Colocation Debug Info:
Colocation group had the following types and supported devices:
Root Member(assigned_device_name_index=-1 requested_device_name='/device:GPU:0' assigned_device_name='' resource_device_name='/device:GPU:0' supported_device_types=[CPU] possible_devices_=[]
L2Loss: CPU XLA_CPU
Assign: CPU
VariableV2: CPU
Identity: CPU XLA_CPU
Add: CPU XLA_CPU
Mul: CPU XLA_CPU
TruncatedNormal: CPU XLA_CPU
Const: CPU XLA_CPU
Colocation members, user-requested devices, and framework assigned devices, if any:
hourglass_stack_fused_depth_prediction/conv1/weights/Initializer/truncated_normal/shape (Const)
hourglass_stack_fused_depth_prediction/conv1/weights/Initializer/truncated_normal/mean (Const)
hourglass_stack_fused_depth_prediction/conv1/weights/Initializer/truncated_normal/stddev (Const)
hourglass_stack_fused_depth_prediction/conv1/weights/Initializer/truncated_normal/TruncatedNormal (TruncatedNormal)
hourglass_stack_fused_depth_prediction/conv1/weights/Initializer/truncated_normal/mul (Mul)
hourglass_stack_fused_depth_prediction/conv1/weights/Initializer/truncated_normal (Add)
hourglass_stack_fused_depth_prediction/conv1/weights (VariableV2) /device:GPU:0
hourglass_stack_fused_depth_prediction/conv1/weights/Assign (Assign) /device:GPU:0
hourglass_stack_fused_depth_prediction/conv1/weights/read (Identity) /device:GPU:0
hourglass_stack_fused_depth_prediction/conv1/weights/Regularizer/l2_regularizer/scale (Const) /device:GPU:0
hourglass_stack_fused_depth_prediction/conv1/weights/Regularizer/l2_regularizer/L2Loss (L2Loss) /device:GPU:0
hourglass_stack_fused_depth_prediction/conv1/weights/Regularizer/l2_regularizer (Mul) /device:GPU:0
 [[node hourglass_stack_fused_depth_prediction/conv1/weights/Initializer/truncated_normal/TruncatedNormal (defined at /home/killab/ml/models/ShapeGeneration/HDNet_TikTok/hourglass_net_depth.py:28) ]]Additional information about colocations:No node-device colocations were active during op 'hourglass_stack_fused_depth_prediction/conv1/weights/Initializer/truncated_normal/TruncatedNormal' creation.

Device assignments active during op 'hourglass_stack_fused_depth_prediction/conv1/weights/Initializer/truncated_normal/TruncatedNormal' creation:
with tf.device(None): </home/killab/anaconda3/envs/HDNet/lib/python3.7/site-packages/tensorflow/python/ops/variables.py:1696>
with tf.device(/gpu:0): </home/killab/ml/models/ShapeGeneration/HDNet_TikTok/hourglass_net_depth.py:26>
Original stack trace for 'hourglass_stack_fused_depth_prediction/conv1/weights/Initializer/truncated_normal/TruncatedNormal':
File "HDNet_Inference.py", line 57, in
out2_1 = hourglass_refinement(x1,True)
File "/home/killab/ml/models/ShapeGeneration/HDNet_TikTok/hourglass_net_depth.py", line 119, in hourglass_refinement
out0_d = hourglass_stack_no_incep(netIN)
File "/home/killab/ml/models/ShapeGeneration/HDNet_TikTok/hourglass_net_depth.py", line 74, in hourglass_stack_no_incep
c0 = conv_layer(stack_in,layer_name('conv'),KER_SZ,NUM_CH[0],bn=bn,training=training)
File "/home/killab/ml/models/ShapeGeneration/HDNet_TikTok/hourglass_net_depth.py", line 34, in conv_layer
kernel = variable('weights', [kernel_size, kernel_size, input_channels, output_channels], initializer, regularizer=tf.contrib.layers.l2_regularizer(0.0005))
File "/home/killab/ml/models/ShapeGeneration/HDNet_TikTok/hourglass_net_depth.py", line 28, in variable
return tf.get_variable(name, shape, initializer=initializer, regularizer=regularizer, dtype=tf.float32, trainable=True)
File "/home/killab/anaconda3/envs/HDNet/lib/python3.7/site-packages/tensorflow/python/ops/variable_scope.py", line 1496, in get_variable
aggregation=aggregation)
File "/home/killab/anaconda3/envs/HDNet/lib/python3.7/site-packages/tensorflow/python/ops/variable_scope.py", line 1239, in get_variable
aggregation=aggregation)
File "/home/killab/anaconda3/envs/HDNet/lib/python3.7/site-packages/tensorflow/python/ops/variable_scope.py", line 562, in get_variable
aggregation=aggregation)
File "/home/killab/anaconda3/envs/HDNet/lib/python3.7/site-packages/tensorflow/python/ops/variable_scope.py", line 514, in _true_getter
aggregation=aggregation)
File "/home/killab/anaconda3/envs/HDNet/lib/python3.7/site-packages/tensorflow/python/ops/variable_scope.py", line 929, in _get_single_variable
aggregation=aggregation)
File "/home/killab/anaconda3/envs/HDNet/lib/python3.7/site-packages/tensorflow/python/ops/variables.py", line 259, in call
return cls._variable_v1_call(*args, **kwargs)
File "/home/killab/anaconda3/envs/HDNet/lib/python3.7/site-packages/tensorflow/python/ops/variables.py", line 220, in _variable_v1_call
shape=shape)
File "/home/killab/anaconda3/envs/HDNet/lib/python3.7/site-packages/tensorflow/python/ops/variables.py", line 198, in
previous_getter = lambda **kwargs: default_variable_creator(None, **kwargs)
File "/home/killab/anaconda3/envs/HDNet/lib/python3.7/site-packages/tensorflow/python/ops/variable_scope.py", line 2511, in default_variable_creator
shape=shape)
File "/home/killab/anaconda3/envs/HDNet/lib/python3.7/site-packages/tensorflow/python/ops/variables.py", line 263, in call
return super(VariableMetaclass, cls).call(*args, **kwargs)
File "/home/killab/anaconda3/envs/HDNet/lib/python3.7/site-packages/tensorflow/python/ops/variables.py", line 1568, in init
shape=shape)
File "/home/killab/anaconda3/envs/HDNet/lib/python3.7/site-packages/tensorflow/python/ops/variables.py", line 1698, in _init_from_args
initial_value(), name="initial_value", dtype=dtype)
File "/home/killab/anaconda3/envs/HDNet/lib/python3.7/site-packages/tensorflow/python/ops/variable_scope.py", line 901, in
partition_info=partition_info)
File "/home/killab/anaconda3/envs/HDNet/lib/python3.7/site-packages/tensorflow/contrib/layers/python/layers/initializers.py", line 150, in _initializer
seed=seed)
File "/home/killab/anaconda3/envs/HDNet/lib/python3.7/site-packages/tensorflow/python/ops/random_ops.py", line 178, in truncated_normal
shape_tensor, dtype, seed=seed1, seed2=seed2)
File "/home/killab/anaconda3/envs/HDNet/lib/python3.7/site-packages/tensorflow/python/ops/gen_random_ops.py", line 1013, in truncated_normal
name=name)
File "/home/killab/anaconda3/envs/HDNet/lib/python3.7/site-packages/tensorflow/python/framework/op_def_library.py", line 788, in _apply_op_helper
op_def=op_def)
File "/home/killab/anaconda3/envs/HDNet/lib/python3.7/site-packages/tensorflow/python/util/deprecation.py", line 507, in new_func
return func(*args, **kwargs)
File "/home/killab/anaconda3/envs/HDNet/lib/python3.7/site-packages/tensorflow/python/framework/ops.py", line 3616, in create_op
op_def=op_def)
File "/home/killab/anaconda3/envs/HDNet/lib/python3.7/site-packages/tensorflow/python/framework/ops.py", line 2005, in init
self._traceback = tf_stack.extract_stack()
`

Hi, Can you solve this problem?

Hi, this problem could be addressed by checking your cuda  version.
tensorflow 1.14-cuda 10


Updating a DynamicTable defintion fails with SQL compilation error: unexpected

Attempting to create dynamic tables through TF, however running into a show stopper bug.
The very first apply of the dynamic table succeeds without any problems.
But:

Every subsquent apply that attempts to update the resource fails with

│ Error: 001003 (42000): SQL compilation error:
│ syntax error line 1 at position 71 unexpected '<EOF>'.
│
│   with snowflake_dynamic_table.my_dyn_table,
│   on my_dynamic_tables.tf line 59, in resource "snowflake_dynamic_table" "my_dyn_table":
│   59: resource "snowflake_dynamic_table" "my_dyn_table" {

Every tf apply thinks it detects changes for dynamic tables even if nothing changed. It seems to be because it thinks there were external changes to the query of the DT that added some spacing to the start of it, even if there were no changes at all (the exact same tf apply reran back to back)

Note: Objects have changed outside of Terraform

Terraform detected the following changes made outside of Terraform since the
last "terraform apply":

  # snowflake_dynamic_table.my_dyn_table has changed
  ~ resource "snowflake_dynamic_table" "my_dyn_table" {
        id                   = "MY_DB|PUBLIC|MY_DYN_TABLE"
        name                 = "my_dyn_table"
      ~ query                = <<-EOT
          -     ---
          + ---
                select * from (

hi @rmargarint-nydig , I experienced same error. found that using multi-line <<-EOT caused the issue for me. I had to wrap in double quotes and query the full name space of the table or view.

hello @rmargarint-nydig , did you find a work around for this? We are still experiencing the same issue.

It looks like the syntax error happens because the query that's executed is this:
ALTER DYNAMIC TABLE "<database>"."<schema>"."<table>" SET

(database, schema, and table are placeholders -- the important feature is that there is nothing after SET)
This appears to happen when Terraform detects that there are changes but there are actually no changes.
A workaround is to introduce an innocuous change that Terraform will actually apply. For example, if the table's target lag is an hour, Snowflake harmonizes this to 1 hour. If this is specified in Terraform as 60 minutes, the terraform provider detects this as a change, and the following statement will always be applied
ALTER DYNAMIC TABLE "<database>"."<schema>"."<table>" SET TARGET_LAG = '60 minutes'

Despite being an unnecessary alter statement, this works around the <EOF> error.
We actually discovered this because we tried to get rid of the spurious change and realized we were depending on a bug.

Hey @rmargarint-nydig. Thanks for creating the issue.
Yes, it looks like a bug in the dynamic table resource. It is relatively easy to fix. I will work on it next week so that it will hopefully be ready for next Wednesday's release.


How to update Text Area from GET request?

Not sure if this is possible with Data Manipulation Plugin, but would like to update a Text Area based on information from GET requests to the REST API of an Artifactory server. Not clear how I am supposed to use custom code to modify the behaviour. How does one do this? Can it be done through the user interface of the panel, or does one use this plugin as a framework where changes are made to the plugin code? Maybe this plugin is meant to be used in conjunction with another plugin that would act as the read-only view (eg: Table Panel with a JSON data source)?
Upon initial request, I can see the console.log successfully showing response from the URL input.
When I attempt to change Custom Code in the Initial Request section, it always reverts to console.log(data, response, initial, elements)
Screenshot of the form; would like "properties" to get updated with data from a GET request.

Related details:

Artifactory and Caddy (reverse proxy to enable TLS for Artifactory) run as Docker containers.
CORS being handled by Caddy.

Many thanks!

@mikhail-vl many thanks. The PR looks like a good idea, especially as I prefer to read documentation, than watch a video, to find this information; I can more easily search a document than a video.

@mikequentel I hope it's clear now and you can move forward.
Appreciate the feedback. Everybody learns differently, and we do our best to keep videos and documentation updated to answer as many questions as possible.


Why do I have this error：verbose stack Error: @0.0.0 build: tsc && vite build

Describe the bug

The first time I initialized the project with React -ts and then NPM run build, I reported the following error
Reproduction

System Info
Output of npx envinfo --system --npmPackages vite,@vitejs/plugin-vue --binaries --browsers:
  System:
    OS: macOS 10.15.6
    CPU: (4) x64 Intel(R) Core(TM) i5-5257U CPU @ 2.70GHz
    Memory: 75.87 MB / 8.00 GB
    Shell: 5.7.1 - /bin/zsh
  npmPackages:
    vite: ^2.3.5 => 2.3.6

Used package manager:
Logs

0 info it worked if it ends with ok
1 verbose cli [ '/usr/local/bin/node', '/usr/local/bin/npm', 'run', 'build' ]
2 info using<EMAIL_ADDRESS>3 info using<EMAIL_ADDRESS>4 verbose run-script [ 'prebuild', 'build', 'postbuild' ]
5 info lifecycle @0.0.0~prebuild: @0.0.0
6 info lifecycle @0.0.0~build: @0.0.0
7 verbose lifecycle @0.0.0~build: unsafe-perm in lifecycle true
8 verbose lifecycle @0.0.0~build: PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/Users/tibic/TestCode/my-vite-app/node_modules/.bin:/Library/Frameworks/Python.framework/Versions/3.8/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin
9 verbose lifecycle @0.0.0~build: CWD: /Users/tibic/TestCode/my-vite-app
10 silly lifecycle @0.0.0~build: Args: [ '-c', 'tsc && vite build' ]
11 silly lifecycle @0.0.0~build: Returned: code: 2  signal: null
12 info lifecycle @0.0.0~build: Failed to exec build script
13 verbose stack Error: @0.0.0 build: `tsc && vite build`
13 verbose stack Exit status 2
13 verbose stack     at EventEmitter.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16)
13 verbose stack     at EventEmitter.emit (events.js:315:20)
13 verbose stack     at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack     at ChildProcess.emit (events.js:315:20)
13 verbose stack     at maybeClose (internal/child_process.js:1021:16)
13 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:286:5)
14 verbose pkgid @0.0.0
15 verbose cwd /Users/tibic/TestCode/my-vite-app
16 verbose Darwin 19.6.0
17 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "build"
18 verbose node v12.18.3
19 verbose npm  v6.14.6
20 error code ELIFECYCLE
21 error errno 2
22 error @0.0.0 build: `tsc && vite build`
22 error Exit status 2
23 error Failed at the @0.0.0 build script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 2, true ]

Before submitting the issue, please make sure you do the following

[ ] Read the Contributing Guidelines.
[x] Read the docs.
[x] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[ ] Provide a description in this issue that describes the bug.
[x] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to https://github.com/vuejs/vue-next instead.
[x] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.

Does this happen when you just use vite instead of tsc && vite? Or in other words: is this really a vite related issue?

Setting skipLibCheck to true in tsconfig.json should fix this issue. If it happens right after generating it with create-app, we should probably add this to the template.

@nihalgonsalves Yes , you are right! It has been settled, thank you!
// Ignore type checking for all declaration files (*.d.ts)
    "skipLibCheck": true,


[ionic v4 - angular] - iPhone X don't show header and tabs correctly (missing safe area)

Bug Report
Ionic Info
Ionic:

   ionic (Ionic CLI)          : 4.0.1 (/Users/u007240/.npm-packages/lib/node_modules/ionic)
   Ionic Framework            : @ionic/angular 4.0.0-beta.0
   @angular-devkit/core       : 0.7.0-rc.3
   @angular-devkit/schematics : 0.7.0-rc.3
   @angular/cli               : 6.0.8
   @ionic/ng-toolkit          : 1.0.0
   @ionic/schematics-angular  : 1.0.1

System:

   NodeJS : v10.7.0 (/usr/local/Cellar/node/10.7.0/bin/node)
   npm    : 6.2.0
   OS     : macOS High Sierra

Describe the Bug
Every starter came without padding for the safe area in iPhone X for the Notch.
Steps to Reproduce
Steps to reproduce the behavior:

ionic start myApp [tabs|menu|blank] --type=angular

Also seeing this as well....

I'm also having the exact same problem!

This may not be an ionic 4 issue, but an iPhoneX issue instead. I say this because after some looking around at who actually uses ionic, I ran accross this site: http://showcase.ionicframework.com/apps/top
I downloaded a couple of their apps, notably, Markey Watch and I can see this exact same issue there. Given Ionic 4 is in beta and was just released a couple days ago, my assumption is that Market Watch isn't using ionic 4 which would mean this issue is found in multiple Ionic versions.

@mswilson4040 this could be in fact something not related with ionic but in fact if we do any of the start templates in ionic 3 removing  "--type=angular " ionic start myApp [tabs|menu|blank] all works as expected. Some of the apps in the market are incompatible with iPhone X because are created before ionic have iOS 11 support.
In order to resolve this issue I add the following css to the global.scss
body {
    background-color: var(--ion-color-primary);
}
ion-app {
    margin-top: env(safe-area-inset-top);
    margin-bottom: env(safe-area-inset-bottom)
}

Related to #14742

@SoulOnFire Can you expand on where the env function is imported from?

This is now fixed in beta.3.

Please let me clarify this a bit:
The bottom Tab bar works just fine while the header height seems still not corrent. Please find a screenshot as follow:

Sorry it may not be able to see the notch from this screenshot but it's still clear the header area is a bit lower than it should be.
Thanks!

@babaru Please make sure you're updating the starter to use beta.12 of @ionic/angular. By default they're using beta-7 right now (we need to update the base project).
With beta 12, things look as expected


[release-4.4] Bug 1813914: Disable serving for cert regeneration controller to avoid wrong dependency

backport of https://github.com/openshift/cluster-kube-apiserver-operator/pull/797
/cc @sttts @deads2k @soltysh

/lgtm

/retest

/bugzilla refresh

/bugzilla refresh


[LiveComponent] Throw exception for typed LiveProps as interfaces

Q
A

Bug fix?
yes

New feature?
no

Issues
Fix #1590

License
MIT

Check is done just after the hydration extensions are called, to allow userland implementations.

Thanks Simon.


Optionally publish NavCam and DockCam images in raw Bayer format that can later be de-Bayered to RGB

Not tested yet!
Adds a feature to the is_camera driver for NavCam and DockCam that optionally publishes images in raw Bayer format. The feature is disabled by default in cameras.config (bayer_enable parameter). The rate of publishing Bayer images can be throttled (bayer_throttle_ratio parameter).
The implementation is much like the existing grayscale output but instead of converting Bayer to grayscale, it just copies the raw Bayer imagery into the output message (ROS supports tagging the image as Bayer encoded).
There are a number of ways we could use it downstream. Perhaps the most ROS-idiomatic approach would be to run the Bayer-encoded images through the ROS image_proc package's debayer nodelet, and then subscribe to the resulting color image topic in the image sampler.

Oops, PR should have been to develop.