ref(nuxt): Add instument.server.mjs to preview script

This setup for ESM-compatibility throws an error and the pages cannot load. I think this is also related to this issue: https://github.com/nodejs/import-in-the-middle/issues/139
Another comment where people have problems with vue/server-renderer: https://github.com/getsentry/sentry-javascript/issues/12114#issuecomment-2120096287
Steps to reproduce the import-in-the-middle issue:

define the SENTRY_DSN environment variable
Build the nuxt project
Preview the nuxt project
Load a page

Error Message:
Error: 'import-in-the-middle' failed to wrap 'file:///Users/sigridh/Documents/DEV/sentry-javascript-examples/apps/nuxt/.output/server/node_modules/vue/server-renderer/index.mjs'
    at getSource (/Users/sigridh/Documents/DEV/sentry-javascript-examples/node_modules/@sentry/nuxt/node_modules/import-in-the-middle/hook.js:304:21)
    at async load (/Users/sigridh/Documents/DEV/sentry-javascript-examples/node_modules/@sentry/nuxt/node_modules/import-in-the-middle/hook.js:319:26)
    at async nextLoad (node:internal/modules/esm/hooks:865:22)
    at async Hooks.load (node:internal/modules/esm/hooks:448:20)
    at async MessagePort.handleMessage (node:internal/modules/esm/worker:196:18) {
  cause: TypeError: emitImportAssertionWarning is not a function
      at defaultLoad (node:internal/modules/esm/load:119:5)
      at nextLoad (node:internal/modules/esm/hooks:865:28)
      at getExports (/Users/sigridh/Documents/DEV/sentry-javascript-examples/node_modules/@sentry/nuxt/node_modules/import-in-the-middle/lib/get-exports.js:80:27)
      at processModule (/Users/sigridh/Documents/DEV/sentry-javascript-examples/node_modules/@sentry/nuxt/node_modules/import-in-the-middle/hook.js:131:29)
      at getSource (/Users/sigridh/Documents/DEV/sentry-javascript-examples/node_modules/@sentry/nuxt/node_modules/import-in-the-middle/hook.js:269:31)
      at load (/Users/sigridh/Documents/DEV/sentry-javascript-examples/node_modules/@sentry/nuxt/node_modules/import-in-the-middle/hook.js:319:32)
      at nextLoad (node:internal/modules/esm/hooks:865:28)
      at Hooks.load (node:internal/modules/esm/hooks:448:26)
      at MessagePort.handleMessage (node:internal/modules/esm/worker:196:24)
      at [nodejs.internal.kHybridDispatch] (node:internal/event_target:826:20)
}

Could you force yarn to resolve<EMAIL_ADDRESS>Curious to see if that changes the error.

This was fixed with version 1.10.0 of import-in-the-middle 🎉
ref: https://github.com/nodejs/import-in-the-middle/pull/140 and https://github.com/nodejs/import-in-the-middle/pull/145


empty trading proceeds claimed data

added ShareTokens property on Market:
graph data

query

moved tradingProceedsClaimed from shareToken entity to market entity.


Files will not download, process gets stuck in searching for "file" under the menu.

I disabled headless execution for debugging (my files didn't want to download), and added a few logging entries to track where my files were failing to download, and discovered that Playwright wasn't finding the "File" menu item. Turns out that the page reloads often, causing the tests to break.
This is what I often found was the result of my download process: (I removed the file name)
  figma-export-main sudo npm run start

><EMAIL_ADDRESS>start
> playwright test

Running 642 tests using 1 worker

  ✓  1 [setup] › auth.setup.ts:8:6 › authenticate (6.4s)
     2 …ct: (redacted) › file: (redacted)
Navigating to file:(redacted)
Page reloaded: (redacted)
Page reloaded: (redacted)
Page reloaded: (redacted)
Page reloaded: (redacted)
Page reloaded: (redacted)
Page reloaded: (redacted)
Page reloaded: (redacted)
Page reloaded: (redacted)
Successfully loaded page for file: (redacted)
Setting up download event for file: (redacted)
Opening main menu for file: (redacted)
Page reloaded: (redacted)
Clicked main menu for file: (redacted)
Selecting File option for file: (redacted)
Page reloaded: (redacted)
Page reloaded: (redacted)
Page reloaded: (redacted)
Page reloaded: (redacted)
Page reloaded: (redacted)
Page reloaded: (redacted)
Page reloaded: (redacted)
Page reloaded: (redacted)
Page reloaded: (redacted)
Page reloaded: (redacted)
Page reloaded: (redacted)
Page reloaded: (redacted)
Page reloaded: (redacted)

Where I added logging:
import { test } from "@playwright/test";
import fs from "node:fs";
import dotenv from "dotenv";

dotenv.config();

const projects = JSON.parse(
  fs.readFileSync("files.json", { encoding: "utf-8" })
);

const MAX_RETRIES = 3;

test.describe('Figma download automation', () => {
  test.use({ storageState: ".auth/user.json" }); // Use authenticated state

  for (const project of projects) {
    const projectName = project.name || "Drafts";
    const teamId = project.team_id || null;

    test.describe(`project: ${projectName} (${project.id})`, () => {
      for (const file of project.files) {
        test(`file: ${file.name} (${file.key})`, async ({ page }) => {
          let attempts = 0;
          let success = false;

          while (attempts < MAX_RETRIES && !success) {
            try {
              console.log(`Attempt ${attempts + 1}: Navigating to file: ${file.name} (${file.key})`);

              // Log page reloads
              page.on('framenavigated', () => {
                console.log(`Page reloaded: ${file.name} (${file.key})`);
              });

              await page.goto(`https://www.figma.com/design/${file.key}/`, { timeout: 60000 });
              await page.waitForLoadState('load');
              console.log(`Successfully loaded page for file: ${file.name}`);
              await page.waitForTimeout(2000); // Wait for stability

              console.log(`Setting up download event for file: ${file.name}`);
              const downloadPromise = page.waitForEvent("download");

              console.log(`Opening main menu for file: ${file.name}`);
              await page.getByRole("button", { name: "Main menu" }).click();
              console.log(`Clicked main menu for file: ${file.name}`);
              await page.waitForTimeout(2000); // Wait for stability

              console.log(`Selecting File option for file: ${file.name}`);
              await page.getByTestId("dropdown-option-File").click();
              console.log(`Selected File option for file: ${file.name}`);
              await page.waitForTimeout(2000); // Wait for stability

              console.log(`Selecting Save local copy option for file: ${file.name}`);
              await page.getByTestId("dropdown-option-Save local copy…").click();
              console.log(`Selected Save local copy option for file: ${file.name}`);
              await page.waitForTimeout(2000); // Wait for stability

              console.log(`Waiting for download to start for file: ${file.name}`);
              const download = await downloadPromise;
              console.log(`Download event triggered for file: ${file.name}`);

              const suggestedFilename = download.suggestedFilename();
              const filename = suggestedFilename.match(/.*(?=\.[\w\d]+)/)![0];
              const extension = suggestedFilename.replace(filename + ".", "");
              const downloadPath = `${process.env.DOWNLOAD_PATH}/${teamId ? teamId + "/" : ""}${projectName}/${filename}.${extension}`;
              console.log(`Saving file as: ${downloadPath}`);

              await download.saveAs(downloadPath);
              console.log(`Successfully saved file: ${filename}.${extension}`);

              await download.path(); // Ensure the download is completed
              console.log(`Download completed for file: ${filename}.${extension}`);

              await page.waitForTimeout(Number(process.env.WAIT_TIMEOUT) || 0);
              console.log(`Test completed for file: ${file.name} (${file.key})`);
              success = true;
            } catch (error) {
              console.error(`Attempt ${attempts + 1} failed for file: ${file.name} (${file.key})`, error);
              attempts++;
              if (attempts >= MAX_RETRIES) {
                console.error(`Failed to download file: ${file.name} (${file.key}) after ${MAX_RETRIES} attempts`);
              }
            }
          }
        });
      }
    });
  }
});

Hi @drluciano,
Thanks for filing this issue. I'm currently on away from my laptop for the week so I can't debug more thoroughly, but can you confirm that you have editor access to the file you're attempting to download?

Can confirm, I have edit access and I'm a workspace administrator.

I'm unable to reproduce this issue. My original hunch was the UI3 had some impact on how the save local copy menu item was accessed, but that doesn't seem like the case in my tests.
Are you using Figma in a different language?

v2.0.1 has a fix to support localized Figma UI.

Thank you!


Allow for multiple levels of tags on workspace

Details

The PR introduces a new logic for using multiple levels of tags. It supports for creating/editing requests with independent multi-level tags for paid workspaces.
Fixed Issues

$ https://github.com/Expensify/App/issues/33983
PROPOSAL: N/A
Tests

Pre-condition:

Create/have a paid workspace (Collect/Control).
Enable a flag "Use multiple levels of tags" via OD.
You can import an attached collection of multiple levels of tags.

Apply tags for creating an expense report

Open a workspace chat.
Click on "+" (actions).
Click on "Request money".
Choose any type of an expense report: manual, scan and distance.
Click on "Show more".
Verify that a row rendered for each tag in the workspace after a category row.
Apply any tags to the expense report.
Verify that selection works for each row, and that the appropriate list of tags show for the appropriate level.
Create the report.
Open a report details page of this newly created report.
Verify that all previously selected tags have been applied properly for the expense report.
Try to create one more expense report.
Verify that the previously tags have been added properly to recently used tags.

Apply tags for editing an expense report

Open a report details page of an expense report.
Verify that a row rendered for each tag in the workspace after a category row.
Click on any tag field.
Apply any tags to the expense report.
Verify that a newly selected tag has been applied properly for the expense report.
Try to create one more expense report.
Verify that the previously tags have been added properly to recently used tags.

Apply tags for a split bill

Open a workspace chat.
Click on "+" (actions).
Click on "Split bill".
Choose any type of a split bill: manual, scan and distance.
Click on "Show more".
Verify that a row rendered for each tag in the workspace after a category row.
Apply any tags to the split bill.
Verify that selection works for each row, and that the appropriate list of tags show for the appropriate level.
Create the report.
Open a split bill details page of this newly created split bill.
Verify that all previously selected tags have been applied properly for the split bill.
Try to create one more expense report.
Verify that the previously tags have been added properly to recently used tags.

[x] Verify that no errors appear in the JS console

Offline tests

Same as "Tests".
QA Steps

Same as "Tests".

[x] 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: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb 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 the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[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 grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is 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 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(theme.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[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 the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label so the design team can review the changes.

[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] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

https://github.com/Expensify/App/assets/57314631/8dc352d4-9f21-4dd4-a038-e83dc06acd95
https://github.com/Expensify/App/assets/57314631/dcb22b92-ce78-465d-8a00-2fdf61ddb5f0
https://github.com/Expensify/App/assets/57314631/c5cd880a-a7de-4cab-aa43-6eb6b25518f7

Android: mWeb Chrome

https://github.com/Expensify/App/assets/57314631/c13c287b-e1fd-47c4-bf33-d3089ebfa973
https://github.com/Expensify/App/assets/57314631/cd25b972-7233-46ec-b846-ffaaaf484e81

iOS: Native

https://github.com/Expensify/App/assets/57314631/fac2860c-c5a9-4c11-9707-d748f51c8797
https://github.com/Expensify/App/assets/57314631/2726f3b8-83e9-4dd8-a818-4447907f33c1
https://github.com/Expensify/App/assets/57314631/6c89777a-7257-44a2-8e1a-0b154c2dd484

iOS: mWeb Safari

https://github.com/Expensify/App/assets/57314631/605c9484-f9d4-4132-a3dc-c033a056a8d6
https://github.com/Expensify/App/assets/57314631/39e40b51-7919-4c61-9f7f-52e6b257b1c1
https://github.com/Expensify/App/assets/57314631/363bd7b2-c993-4dc2-9349-982b8ff893aa

MacOS: Chrome / Safari

https://github.com/Expensify/App/assets/57314631/3673a45f-d678-4019-bb7d-2658c5e1721f
https://github.com/Expensify/App/assets/57314631/13b64681-61bc-440a-aebe-7207379d4d63

https://github.com/Expensify/App/assets/57314631/d6d6a6fd-4f83-472a-bf2c-3c69a643c6cf

MacOS: Desktop

https://github.com/Expensify/App/assets/57314631/52037932-870b-42b3-942e-170120fa9061
https://github.com/Expensify/App/assets/57314631/27777862-6573-4d72-976d-f6240b597fa7
https://github.com/Expensify/App/assets/57314631/eeb14427-4327-4816-931f-5e2ae2ea7df8

There is a bug that unable to attach a tag for a split bill on the latest main. It is a blocker for this PR for now. Needs to be fixed in a scope of another issue or right inside the PR.
https://github.com/Expensify/App/assets/57314631/e23d1691-e533-4848-9993-458edf890438
cc @mountiny

@rezkiy37 bro you so fast

@rezkiy37 the bug should be handled in a separate PR

@rezkiy37 you have conflicts!

@rezkiy37 btw contribuotr is handling the issue you have found

Reviewer Checklist

[ ] I have verified the author checklist is complete (all boxes are checked off).
[ ] I verified the correct issue is linked in the ### Fixed Issues section above
[ ] I verified testing steps are clear and they cover the changes made in this PR

[ ] I verified the steps for local testing are in the Tests section
[ ] I verified the steps for Staging and/or Production testing are in the QA steps section
[ ] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[ ] 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)

[ ] I checked that screenshots or videos are included for tests on all platforms
[ ] I included screenshots or videos for tests on all platforms
[ ] I verified tests pass on all platforms & I tested again on:

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

[ ] If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
[ ] I verified proper code patterns were followed (see Reviewing the code)

[ ] 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).
[ ] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[ ] I verified that comments were added to code that is not self explanatory
[ ] 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.
[ ] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
[ ] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[ ] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[ ] 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.
[ ] I verified the JSDocs style guidelines (in STYLE.md) were followed

[ ] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[ ] I verified that this PR follows the guidelines as stated in the Review Guidelines
[ ] I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
[ ] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[ ] 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
[ ] If a new component is created I verified that:

[ ] A similar component doesn't exist in the codebase
[ ] All props are defined accurately and each prop has a /** comment above it */
[ ] The file is named correctly
[ ] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[ ] The only data being stored in the state is data necessary for rendering and nothing else
[ ] 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)
[ ] 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)
[ ] All JSX used for rendering exists in the render method
[ ] 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

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

[ ] 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

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

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

[ ] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[ ] 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)
[ ] 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.
[ ] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[ ] If the PR modifies the form input styles:

[ ] I verified that all the inputs inside a form are aligned with each other.
[ ] I added Design label so the design team can review the changes.

[ ] 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.
[ ] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[ ] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

BUG
Tags not persisting when spliting bill
https://github.com/Expensify/App/assets/30054992/32ba3fc0-3fcf-4aac-adbe-b35236df0ad9

@rezkiy37 Also not sure if these are related, but it would be good to double check the following console errors:
https://github.com/Expensify/App/assets/30054992/07fcab0d-c3fa-4b95-9eb8-ac4ad16163fa

BUG Tags not persisting when splitting bill
Screen.Recording.2024-02-07.at.12.04.02.PM.mov

Yes, that's what was mentioned here and here.

@rezkiy37 Also not sure if these are related, but it would be good to double check the following console errors:
Screen.Recording.2024-02-07.at.12.15.18.PM.mov

Verified. Those errors are not related to this PR. I don't have any errors during the flow. Looks like it is something out of the feature and already on the main.

BUG
The violations are not getting removed even when I set a value for tag.
https://github.com/Expensify/App/assets/30054992/c1a289aa-4ce8-4e13-95c5-fea0300a62fa

Shouldn't the violation be included in the menu item?

Thank you for the review. Fixing and investigating. Will post an update tomorrow!

Shouldn't the violation be included in the menu item?

I already mentioned this here. So, it is out of the scope.

BUG
The violations are not getting removed even when I set a value for tag.
Screen.Recording.2024-02-08.at.8.34.42.PM.mov

I've checked. It happens because violation checks are not implemented when an update invoked for any field of an expense report.  I am not sure, that it is should be implemented in the scope of the current PR. What do you think, @mountiny?

@rezkiy37 The recent tags seem to be disappearing after some time. I guess that is related to the backend, can you confirm please?

Sorry, I couldn't reproduce the bug. I will try to track workspace tags and check on Monday.

Yeah, the violations not getting removed might be more of a back-end issue not sending an update. I'll look into it using this branch.

Btw, the violations started to work properly.

Thanks! Looks like you have one small conflict. @allroundexperts can you prioritize another review of this soon, please?

Ooops a couple of conflicts @rezkiy37

Resolved the conflicts.

@rezkiy37 more conflicts and now there a typescript error :(
Feel free to ping me on Slack when you resolve and hopefully, I can just review/merge right away.

🚀 Deployed to staging by https://github.com/yuwenmemon in version: 1.4.43-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

It seems this PR caused this regression here: https://github.com/Expensify/App/issues/36889. @cead22 Are you fixing it in this PR https://github.com/Expensify/App/pull/36821?

It's being fixed here https://github.com/Expensify/App/pull/36919

@cead22 That seems a totally different deploy blocker 😄

I think you are fixing it here since it mentions the tag violation is not showing.

🚀 Deployed to production by https://github.com/puneetlath in version: 1.4.43-20 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

https://github.com/Expensify/App/issues/46494


Package com.cloudant.sync.datastore.encryption should be renamed

Since the changes migrating from datastore to documentstore in the v2 API, for consistency, the package com.cloudant.sync.datastore.encryption should probably now be com.cloudant.sync.documentstore.encryption.
The tests should also be moved:

./cloudant-sync-datastore-android-encryption/src/test/java/com/cloudant/sync/datastore
./cloudant-sync-datastore-core/src/test/java/com/cloudant/sync/datastore/encryption

Shame this was missed for 2.x, but I think it would be API breaking to rename it now, so sadly it will probably have to wait until 3.x.

This library is now end-of-life and this issue won't be fixed.
This issue has been tagged EOL in case any forks want to import it.


Is it planned to release a alpine 3.10 based docker image for python 3.7?

Looking at Dockerfile all I can see is alpine 3.9 and alpine 3.10 is available :)
Thanks again

This is probably currently stuck on #401.

The issue is closed and PR is merged, but there is no PR about the change to official-images repo yet. How much should we wait? Is it an automated process or someone's responsbility?


simplify query JSON and fix typo in the nested label

URL of the docs page
https://docs.dapr.io/developing-applications/building-blocks/state-management/howto-state-query-api/
How is it currently worded?
The current version contains unnecessary top-level label "query" in the query JSON and a nested label "pagination"
How should it be worded?
the top-level label "query" in the query JSON should be removed, and the nested label should be replaced with "page"
The Query JSON expects "page". See:
https://github.com/dapr/components-contrib/issues/1343
https://github.com/dapr/dapr/issues/3960

/assign

@dmitsh - Can you get this docs updated to match the code?

@dmitsh - Can you get this docs updated to match the code?

done


Refactor n2 thorpe

This pull does two things:

Modify teos method of estimating N2 so that it does not use points beyond the overturn but instead uses the end points of the overturn. Ultimately this is almost identical to endpt.

Rename the method that was previous teos to teosp1 where the p1 means 'plus 1', i.e. it goes one point beyond the overturn to estimate N squared. It turns out this makes a huge difference to the epsilon estimate! For our first release I think we should choose defaults carefully. I left the default as teosp1 for consistency with previous code but I think it would be better to use bulk or endpt for the release.

Ha, that is quite a difference in the result! Would it be worth to write up a little note JTECH note on this? I am not quite sure I have seen a paper discussing the right way (or at least the various ways) of calculating stratification inside and across overturns.

That is not a bad idea! I also haven't seen much discussion of this.
I found yet another different method from the matlab code. It appears to apply a low pass ( I think) filter to T and S data before estimating N2. Then averaging N2 over each overturn.
Another subject of a paper might be global maps of the epsilon from Thorpe scales using all available CTD/Argo data... I am not aware if it has been done before.

Mater et al. 2015 JPO does a brief comparison of some N2 methods in an Appendix.

Yeah, I guess the Mater et al appendix touches on this. Probably good to this somewhere...
As for global maps from Thorpe scales - I don't think it has been done but maybe for a reason. Argo data are not useful since usually the vertical resolution is too coarse. Shipboard data can easily be contaminated enough for Thorpe scales to make sense in the upper oceans where we expect overturns to be small. Using WOCE sections to do Thorpe scales in the deep ocean could be interesting though...


Register JavaTimeModule for the default Jackson ObjectMapper from Config

As light-codegen is using Java 8 DateTime in generated models(POJOs), it would be convenient to have the default ObjectMapper from Config to support serialization of DateTime in JSON.
    static void setupMapper(ObjectMapper mapper) {
        mapper.registerModule(new JavaTimeModule());
        mapper.configure(SerializationFeature.WRITE_DATES_AS_TIMESTAMPS, false);
    }

pom dependency:
        <dependency>
            <groupId>com.fasterxml.jackson.datatype</groupId>
            <artifactId>jackson-datatype-jsr310</artifactId>
            <version>${version.jackson}</version>
        </dependency>

The code change and test cases looks good! I'd add one more test case for LocalDateTime as well in addition to ZonedDateTime.

@pragmaticway Could you please submit a pull request for the additional test case on develop branch? Thanks.

Pull Request is merged. Thanks @pragmaticway for your help.
https://github.com/networknt/light-4j/pull/83


gateway_liquidity_test flake

This one is local
tempt=28 err=Not synced to block
00:00:37 2024-11-16T01:47:06.409607Z DEBUG fm::devimint: > gateway-cli --rpcpassword=theresnosecondbest -a http://<IP_ADDRESS>:31047/v1 info
00:00:37 2024-11-16T01:47:06.421441Z DEBUG fm::devimint: Polling waiting for block height failed, will retry... attempt=29 err=Not synced to block
00:00:37 2024-11-16T01:47:06.712940Z DEBUG fm::devimint: > gateway-cli --rpcpassword=theresnosecondbest -a http://<IP_ADDRESS>:31047/v1 info
00:00:37 2024-11-16T01:47:06.724295Z DEBUG fm::devimint: Polling waiting for block height failed, will retry... attempt=30 err=Not synced to block
00:00:38 2024-11-16T01:47:07.025792Z DEBUG fm::devimint: > gateway-cli --rpcpassword=theresnosecondbest -a http://<IP_ADDRESS>:31047/v1 info
00:00:38 2024-11-16T01:47:07.038761Z DEBUG fm::devimint: > gateway-cli --rpcpassword=theresnosecondbest -a http://<IP_ADDRESS>:31047/v1 get-balances
00:00:38 thread 'main' panicked at gateway/integration_tests/src/main.rs:621:13:
00:00:38 assertion `left == right` failed: Close channels did not sweep all lightning funds
00:00:38   left:<PHONE_NUMBER>
00:00:38  right: 0
00:00:38 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Looks like a timing issue
        info!("Testing closing all channels...");
        for gw in gateways.clone() {
            gw.close_all_channels(dev_fed.bitcoind().await?.clone()).await?;
            let balances = gw.get_balances().await?;
            let curr_lightning_balance = balances.lightning_balance_msats;

Is there anything guaranteeing that balance will get updated already before get_balances is called?

@fedimint/lightning


Rapier2D components

Thanks for the great crate. I am currently facing an issue while trying to inspect rapier2D-specific components such as RigidBodyPosition or ColliderType. The message Inspectable has not been defined for this component is shown, even though:

I am compiling with the rapier2d feature set:

bevy-inspector-egui = { version="0.6.1", features=["rapier2d"]}

I am using the WorldInspectorPlugin

app.add_plugin(WorldInspectorPlugin::new());

Is there anything I am missing in order to get this going?

It looks like rapier support might have been removed for now? Just from looking at the Cargo.toml here.

Hi, is there any reason why rapier support is removed? Is there any workaround?

I removed it when releasing a version compatible with bevy 0.6 because at that point there was no compatible bevy_rapier version yet.
I also wanted to decouple bevy-inspector-egui releases from bevy_rapier, so I experimented with a separate integration crate: https://github.com/jakobhellermann/bevy-inspector-egui/tree/external-rapier/integrations/bevy-inspector-egui-rapier. You can try that and let me know how it works for you.
bevy-inspector-egui-rapier = { git = "https://github.com/jakobhellermann/bevy-inspector-egui", branch = "external-rapier", features = ["rapier3d"] }

I was gonna release that version on crates.io once rapier 0.12 is out of alpha but if that takes a while it might be worth publishing already and doing an update when rapier releases.

Hi @jakobhellermann,
I tested the example (rapier2d) on the repo and it works fine 😃. Nevertheless, if I copy that example out of the repo, the components are not inspectable. I'm not sure if is something related to depdendencies, but I think I have the correct ones:
bevy = { version = "0.6.0", features = ["dynamic"] }
bevy_rapier2d = "0.12"
bevy-inspector-egui = "0.8"
bevy-inspector-egui-rapier = { git = "https://github.com/jakobhellermann/bevy-inspector-egui", branch = "external-rapier", features = ["rapier2d"] }

Are you using the world inspector or something like a InspectorQuery?
The external bevy-inspector-egui-rapier crate doesn't actually implement Inspectable for the rapier types (this isn't allowed because of the orphan rules), but just 'registers' the types so that they can be displayed in the world inspector. My guess was that this is fine because most people won't have rapier types in their resources, they just want to inspect the ones already in the world.

Hi,
I'm using exactly the rapier2d example but from copied into my crate. A copy-paste without any modification, so my inspectors are:
        .add_plugin(RapierPhysicsPlugin::<NoUserData>::default())
        .add_plugin(WorldInspectorPlugin::new())
        .add_plugin(bevy_inspector_egui_rapier::InspectableRapierPlugin)

Regarding what you say, if Inspectable is not allowed, can I do something in order to inspect some properties of a rapier component? any workaround? I would expect that my app would behave like in the example.

In what way exactly is it not working?
For reference, this is what I would expect the world inspector to look like:

Sorry, maybe I did not explain well the error. I share the same capture:

The same message appears in all rapier components. I would expect the behavior to be the same as yours.

Can you post the output of
cargo tree -i rapier2d
cargo tree -i bevy
cargo tree -i bevy-inspector-egui

?
I suspect that there are multiple versions of one of these crates active or something like that.

Your suspects are right!
  bevy-inspector-egui:0.8.1                                                                                │
  bevy-inspector-egui:0.8.2

I will check what is happing 😵💫

At Cargo.toml:
bevy = { version = "0.6.0", features = ["dynamic"] }
bevy_rapier2d = "0.12"
# bevy-inspector-egui = "0.8" # Removed
bevy-inspector-egui = { git = "https://github.com/jakobhellermann/bevy-inspector-egui", branch = "external-rapier" } # Added
bevy-inspector-egui-rapier = { git = "https://github.com/jakobhellermann/bevy-inspector-egui", branch = "external-rapier", features = ["rapier2d"] }

Fixed the issue removing the commented line and adding the next one.
Thanks for the help!


check failed when filename ends with space

tested with rhash 1.4.2 commit 9903be0cb94b84188f9b3a42d6b6b8ca5073372e on Fedora35 / Debian11
$ mkdir a
$ echo "hello world" > "a/b "
$ rhash --crc32c -r a > result
$ rhash -c result
--( Verifying result )----------------------------------------------------------
a/b                                                 No such file or directory
--------------------------------------------------------------------------------
Errors Occurred: Errors:0   Miss:1   Success:0   Total:1

output of make print-info:
cd librhash && make print-info
make[1]: Entering directory '/home/user/git/RHash/librhash'
cc -c -DOPENSSL_RUNTIME -O2 -DNDEBUG -pipe -ffunction-sections -fdata-sections -fomit-frame-pointer -Wall -W -Wstrict-prototypes -Wnested-externs -Winline -Wpointer-arith -Wbad-function-cast -Wmissing-prototypes -Wmissing-declarations -Wdeclaration-after-statement  test_hashes.c -o test_hashes.o
cc -DOPENSSL_RUNTIME -O2 -DNDEBUG -pipe -ffunction-sections -fdata-sections -fomit-frame-pointer -Wall -W -Wstrict-prototypes -Wnested-externs -Winline -Wpointer-arith -Wbad-function-cast -Wmissing-prototypes -Wmissing-declarations -Wdeclaration-after-statement  test_hashes.o librhash.so.0   -o test_shared
LD_LIBRARY_PATH=.: DYLD_LIBRARY_PATH=.: ./test_shared --info
Compile-time flags: __k8__ __amd64 __amd64__ __x86_64 __x86_64__ _LP64 __LP64__ __VERSION__=11.2.1 20211203 (Red Hat 11.2.1-7) (__GNUC__=11,__GNUC_MINOR__=2) __STDC_VERSION__=201710L _POSIX_VERSION=200809L _POSIX_C_SOURCE=200809L __linux __GLIBC__ OPENSSL_RUNTIME HAS_STDC_ALIGNED_ALLOC CPU_X64 IS_LITTLE_ENDIAN (__BYTE_ORDER==__LITTLE_ENDIAN)
OpenSSL supported, loaded: MD4 MD5 SHA1 WHIRLPOOL RIPEMD-160 SHA-224 SHA-256 SHA-384 SHA-512
make[1]: Leaving directory '/home/user/git/RHash/librhash'

RHash works as designed, all paths parsed from a hash file are trimmed (i.e. trailing and starting spaces are removed).
This is done to simplify parsing of hash files. Hash files are stored in text format where a space is considered a separator.
In the "simple" hash file format a space (or a group of spaces) is located before a file path, while in SFV format it is located after the file path:
$ ./rhash --simple empty-file.txt
00000000  empty-file.txt
./rhash --sfv empty-file.txt | tail -n1
empty-file.txt 00000000

Note that in MS Windows ending a file path with a space is considered bad (MSDN: Naming Files, Paths, and Namespaces):

Do not end a file or directory name with a space or a period. Although the underlying file system may support such names, the Windows shell and user interface does not.

Windows function GetFileAttributesExW and GetFileAttributesExW fail to handle such files (even with a UNC prefix).
So the problem is Linux/Unix specific. I believe it should be solved by implementing special characters support #97.
As a workaround, for now you can use --magnet or --ed2k-link hash file format.

Implemented feature #97 has not solved the problem with space, since space is not considered a special character.
One possible solution would be replacing all starting/ending spaces by the "\040" sequence.

Leading and trailing spaces in a filename are supported by commits 9ed0a15bbbeaa4c90c56ada1fe9cf72151247218 and 25d952028ade95f7a619389fdbb1c22827511b40.
Note that, it is not recommended to use trailing spaces (or dots) in a file name on Windows. For details see the MS article Naming Files, Paths, and Namespaces.

Works for me. Thanks a lot.
Should I wait to close it until a new release is done or close it now?


Release to Noetic?

It looks like all packages depended on by this repo have been released into ROS Noetic. Mind making a Noetic release?
I'm not sure how much work is to be done. I didn't see any Python 3 syntax errors. It will need #219.

Done: ros/rosdistro#24029.


Sample Update - Remove delete option on a document library

What's in the pull request

Updated PnP PowerShell script to remove delete option on a SharePoint document library or list with latest cmdlet updates
Updated CLI for Microsoft 365 script to remove delete option on a SharePoint document library or list with latest cmdlet updates

Awesome updates @ganesh-sanap, these will be live shortly 🎉😁


Integrate pallet-membership benchmarks once they're ready

We started using the membership pallet in https://github.com/Snowfork/polkadot-ethereum/pull/348. Right now all weights are hardcoded to 50_000_000 but https://github.com/paritytech/substrate/pull/8596 added benchmarks. Once the benchmarks' generated WeightInfo is integrated into the pallet, we should update our Substrate version and add the benchmarks to our runtime.

Note: The current weights are over-weighted and so this is not really a security or major issue, but once the weights are updated by substrate or other dependencies, it could be valuable to update those in our parachain too for cheaper/more optimized costs.

@musnit I had a look at the weight breakdown here and realized they're not actually over-weighted. Definitely not all of them. So I'm adding the security label here.

Obsolete. We've got weights in place now for this pallet.


fix(audits/server): Better "must accept UTF-8" test with emoji

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Proposed 2.0.0-b1

High Level Overview of Change
This is a beta for the next release.
Highlights:

https://github.com/XRPLF/rippled/pull/4292
Several changes to improve performance

Note that the replacement for getting and setting thread name (#4312) was reverted, so it is not in this release.
Comparison: https://github.com/XRPLF/rippled/compare/1.12.0...develop-next
Type of Change

[x] Release

Please ignore the accidental close. I just rebased this commit in order to include a couple more PRs:

#4634

This has been waiting for a while.

#4702

This reverts a change which never went into a release. Reverting now prevents churn in the API (i.e. we don't want the API to change in one release, and then revert back in the next release - it's better to keep it stable and only change once, when it's actually ready to go). Furthermore, there are problems on Windows if we don't include this revert.

notes:

Proposed 2.0.0-b1 (4854508d39) :+1: on linux, macOS
Fails on Windows; requires #4708
#4707 may be needed in order to create targets during packaging

Rebased to add #4708. This is expected to build on Windows now.

Force pushed to include:

#4709
#4707

This is now ready for re-review at 046d0c2f0af89067aea0d245da706a35c5f99046.

@legleux to confirm inclusion of #4707

@legleux to confirm inclusion of #4707

Looks good


Add variable address implementation

Closes #40
Implementation

Check if the offset is ADDR_OFFSET (= 6), if it is then execute the address loading of the variable.
Since the assembler index is actually used in the memory, it can directly be used while pushing to stack, it is just multiplied by 8 to show that it is an integer, which will help in language implementations.

All integration tests and yamtests are passing. Merging this.


ParquetMetadataConverter.java is too long

ParquetMetadataConverter is huge and could benefit from splitting into a few smaller classes with well defined responsibilities.
Reporter: Alex Levenson / @isnotinvain
Assignee: Ashish Singh / @SinghAsDev
Note: This issue was originally created as PARQUET-310. Please see the migration documentation for further details.

Ryan Blue / @rdblue:
We should define its public API at the same time and make sure the packages line up.


Ability to auto-create Mayastor pools

Is your feature request related to a problem? Please describe.
I need a better way to automate the bringing up of Kubernetes Clusters with Mayastor configured. I use Cluster API to setup the Kubernetes cluster that takes care of setting up the nodes with the prerequisites to run Mayastor. As part of the Mayastor installation, labelling the nodes, I should be able to specify what devices should be used to create Mayastor pools automatically, instead of me having to add a node, label a node, fetch devices and create a MSP. I am looking to avoid the steps => fetch devices and create MSP.
Describe the solution you'd like
It should be as simple as labeling the node with devices to be used to create MSP.
Describe alternatives you've considered
Still exploring
Additional context
Creating this issue based on the discussion started in the Kubernetes Slack thread

@rawkode, can you please provide details about your use-case? We do currently use a custom resource for pool definition. For example (taken from terrafor experiment we are currently working on):
apiVersion: "openebs.io/v1alpha1"
kind: MayastorPool
metadata:
  name: mayastor-pool-local-${node}
  namespace: mayastor
spec:
  node: ${node}
  disks:
    - /dev/sdb

Thus creating a pool is quite straightforward. I can imagine, that we can introduce a nodeSelector as is usual at deployments and such. Just be aware, that currently pool to nodes is a 1:1 relationship, so matching multiple nodes will result in having multiple pools.
Do you use any k8s/configuration automation for your deployment?


Getting 503 and 403 errors

Hi there,
I've created the required file directories (and made them word-writable just in case), but when I try the upload, the following happens:
I either get a 503 (Service unavailable error) - This happens when using the frontend helper
Or if I try to access the url (some-app.com/upload) directly, I get a 403 Access Denied
All I get in the console on the server is:
I20150730-00:24:47.744(2)? ERROR
I20150730-00:24:47.745(2)? [Error: Request aborted]
Not sure what I'm missing in the config here?
UploadServer.init({
	    tmpDir: process.env.PWD + '/.uploads/tmp',
		uploadDir: process.env.PWD + '/.uploads/',
		getFileName: function(fileInfo, formData) {
			return 'myapp_'+ fileInfo.name;
		},
		mimeTypes: {
			"jpeg": "image/jpeg",
		"jpg": "image/jpeg",
		"png": "image/png"
		},
		maxPostSize: 10000,
		maxFileSize: 10000,
		checkCreateDirectories: true //create the directories for you
	  })

Oh, and I've tested that process.env.PWD returns the correct path as well.
Any help would be greatly appreciated. Thanks!
EDIT:
Got it working brilliantly on localmachine, but it's bombing on the server.
First run: Cross-domain error. I think this was because the site is running on IP:8000 and trying to access IP/upload
Second run: So I removed the absoluteURL config option and tried again. This time the URL is correct (includes the port), but I get a net::ERR_CONNECTION_REFUSED error.

Have you tried god rights temporarily, just to see if that makes a difference?

Damnit, yeah, was the permissions on the server itself. I'm using mup to deploy, but for some reason it creates the build in /opt/ and the permissions are totally insane. Sorry to bother you all, it's working now on chmod 777, I'll change it when I can figure out which user is running meteor on the server.

Cool :+1:

Solved, thanks!


Solidify cache hierarchy level names

[ ] Dataset API creates a directory with given name, containing part-### files. When downloading or generating, the files are created directly. This should be unified (probably: no partitioning -> plain files, otherwise directory with part-### files).
[x] Come up with better names for the cache hierarchy level names (e.g. partitioning-by-rows-### and scale-factor-###)

I added scalefactor_ and partitioning_ prefixes. Or do we like partitioning-by-rows-### and scale-factor-### better?

scalefactor_ and partitioning_ sounds good to me!


Collapsed blocks uncollapse when going from text -> blocks

Describe the bug
Create a project in blocks, collapse, convert to text, make some changes, convert back. Previously collapsed blocks are now expanded.
Expected behavior
We preserve the position of blocks somewhat, we should also preserve collapsed/expanded blocks if possible.

No plans to fix this in near future


Feat: add lookforward to incremental models for lambda live views

Spike as a POC

The idea here is likely to be implemented in another iteration. It needs more discussion to ensure a correct and clean implementation.


Extend ListMicrogridDispatches to support receiving dispatches by last modification time

What's needed?
Currently there is no way to just receive dispatches by their last update time. @Marenz requested the following: "It would also be useful to receive dispatches once they have been updated"
Proposed solution
Extending the DispatchFilter so it would also support querying by update_time:
// Message for listing dispatches for a given microgrid, and an optional filter
message DispatchListRequest {
  // The microgrid ID
  uint64 microgrid_id = 1;

  // Additional filter parameters
  DispatchFilter filter = 2;
}

// Parameters for filtering the dispatch list
message DispatchFilter {
-  // Filter by component ID or category
+ // Optional filter by component ID or category
  repeated ComponentSelector selectors = 1;

-  // Filter by dispatch start time interval
-  // If no interval is provided, all dispatches starting from the
-  // current timestamp will be included.
+  // Optional filter by time interval
+  // Dispatches will be filtered based on the start_time of the dispatch request.
+  // If no interval is provided, all dispatches starting from the current timestamp will be included.
-  TimeIntervalFilter time_interval = 2;
+  TimeIntervalFilter start_time_interval = 2;

-  // Filter by active status
+  // Optional filter by active status
  // If this field is not set, dispatches of any active status will be included.
  optional bool is_active = 3;

-  // Filter by dry run status
+  // Optional filter by dry run status
  // If this field is not set, dispatches of any dry run status will be included.
  optional bool is_dry_run = 4;

+  // Optional filter by update time.
+  // Include only dispatches updated after this UTC timestamp.
+  google.protobuf.Timestamp modified_since = 5;
}

Use cases
To ensure users don't miss updates, such as changes to a dispatch's start time, it's essential to allow filtering by the last update time. The update_time_interval filter addresses this need by enabling users to identify dispatches recently modified.
Alternatives and workarounds
No response
Additional context
No response

This will require improving as update_time_interval references TimeIntervalFilter which in fact exposes a start and end time. However to receive the last updates since a certain time only requires the "start time" but no "end time" as the end time would always be empty anyhow.

I think it might be enough to have a
// Optional filter by dispatches newer than this timestamp
// If not given, no update_time filter will be applied
optional Timestamp updated_since

@Marenz I've updated the proposal above. Should hopefully be in line with what you had in mind.

Is this a duplicate of https://github.com/frequenz-floss/frequenz-api-dispatch/issues/161
In particular the following:
+  // Optional filter by update time
+  TimeIntervalFilter update_time_interval = 7;

FWIW I like the update_time_interval API better, it is consistent with other time based filters, and the naming convention matches the data field better.

True, this is superseded by https://github.com/frequenz-floss/frequenz-api-dispatch/issues/161


Etch error when using address (N < 10)

When running the test from creating an NFT with Solmate, I ran into this problem
function test_RevertUnSafeContractReceiver() public {
        vm.etch(address(1), bytes("mock code"));
        vm.expectRevert(bytes(""));
        nft.mintTo{value: 0.08 ether}(address(1));
    }

FAIL. Reason: Etch cannot be used on precompile addresses (N < 10). Please use an address bigger than 10 instead] test_RevertUnSafeContractReceiver() (gas: 3548)

Change this into below codes will solve the problem.Please make the change to the documentation.
    function test_RevertUnSafeContractReceiver() public {
        vm.etch(address(11), bytes("mock code"));
        vm.expectRevert(bytes(""));
        nft.mintTo{value: 0.08 ether}(address(11));
    }

[PASS] test_SafeContractReceiver() (gas: 272635)

Solved on main


The converted model is not the same as the original model

Platform (like ubuntu 16.04/win10):win10
Python version: 36
Source framework with version (like Tensorflow 1.4.1 with GPU):pytorch 0.4.0
Destination framework with version (like CNTK 2.3 with GPU):pytorch
Pre-trained model path (webpath or webdisk path): Self-trained model
Running scripts: IR2pytorch
I did an experiment. Turn pytorch model into IR, and then IR into pytorch model.
But the final pytorch model and the original pytorch model structure is not the same, compared to the two models, the final pytorch model which lacks relu, BN, pooling and other layers.
In addition, the visual IR model is right.

Hi @konioyxgq, very thanks for your report. Could you upload your model for us to debug?

@rainLiuplus  https://drive.google.com/file/d/1vNDId7mevnnuW2pad_Oy7B2KEA0l1rM5/view?usp=sharing

@rainLiuplus Thank you for your reply.


speed up the user's learning process

You learn faster when the answers are provided when needed.  Please work that into this app.

Hi,
can you please elaborate a bit? The kata is meant to be for figuring out the solution yourself, I think the answer would not serve that purpose, in my opinion.
Wolfram

A kata is like a drill that you can do over and over for practice.  I'm not saying the user should not think, but what happens when the user doesn't know the answer? - They have to go elsewhere to go hunt it down.  If they can get the answer by clicking on a button that saves them a lot of time.  Then they can redo the kata and not have to use the answer-button the second time around.  The result is that they can get up to speed much quicker.

Hi Frank,
thanks for the input. The name kata might be misleading here I agree. I
thought it had charme and makes the learning even deeper when you have to
go figure out things, or better try them out, from the mistake you learn.
I am intending the katas to be built that way that you can go from top to
bottom and learn the according feature. If that doesnt work the kata might
needs better explaination.
On the es6katas.org site I agree there could be some additional links +
hints.
--
Kind regards / Saludos / Mit freundlichen Grüßen
Wolfram Kriesing, uxebu Co-Founder
<EMAIL_ADDRESS>mobile: +49<PHONE_NUMBER>
ECMAScript6+React.js workshop http://meetu.ps/2Jds4D
Learn ES6, one kata a day http://es6katas.org
uxebu GmbH
Fraunhofer Straße 31e
86167 Augsburg
Amtsgericht Augsburg, Handelsregister HRB 28613
Directors: W. Kriesing, T. v. Klipstein
On Fri, Jun 26, 2015 at 12:17 AM, Frank Gutierrez<EMAIL_ADDRESS>wrote:

A kata is like a drill that you can do over and over for practice. I'm not
saying the user should not think, but what happens when the user doesn't
know the answer? - They have to go elsewhere to go hunt it down. If they
can get the answer by clicking on a button that saves them a lot of time.
Then they can redo the kata and not have to use the answer-button the
second time around. The result is that they can get up to speed much
quicker.
—
Reply to this email directly or view it on GitHub
https://github.com/tddbin/tddbin-frontend/issues/7#issuecomment-115417114
.

Thanks for the conversation.  Good luck.


Dockerfile*.ubi: bump python to 3.12

following upstream's https://github.com/vllm-project/vllm/pull/8133

Requires to be merged along with https://github.com/openshift/release/pull/56778


helm installation error

# helm install hwameistor -n hwameistor ./helm/hwameistor --create-namespace --set global.k8sImageRegistry=m.daocloud.io/registry.k8s.io
walk.go:74: found symbolic link in path: /github/actions-runner/_work/hwameistor/hwameistor/helm/hwameistor/crds resolves to /github/actions-runner/_work/hwameistor/hwameistor/deploy/crds
Error: INSTALLATION FAILED: parse error at (hwameistor/templates/failover-assistant.yaml:9): bad character U+002D '-'

Will fix urgently

fixed by PR https://github.com/hwameistor/hwameistor/pull/1018


[Design] - Applicants, Managers, HR / Notifications

Design Goal & User Groups
Please explain the primary goals of this design work.
Eventually, Talent Cloud will require a common form of notification system to allow for efficient and timely job action completion. This notification system will need to do different things for each user group, but will functionally use the same UI, preferably located in the navigation.
Please select the users this UI will apply to.

[ ] Administrators
[x] Applicants
[x] Hiring Managers
[x] HR Advisers

Initial Research & Notes
Please list/link all research performed before this design work began. Include research relevant to insights from team members as well. Don't be afraid to ask for references or documents!
Related to the navigation redesign: #1551
The notification system could do the following for each group...
Applicants:

notify them of updates on their applications
notify them of why they weren't selected for a position in a timely fashion
notify them of jobs that match their existing skills
notify them that they've received a new verified credential
notify them of new features

Managers:

notify them of new applications
notify them of new activity and/or comments on a job action from HR
notify them of a job action's status changing (e.g. from approved to published)
notify them of new manager features

HR:

notify them of new activity on their claimed job actions
notify them of new HR features

Assumptions
Please list all assumptions made during your design work. This should include behavioural assumptions made by the team that have no direct research references.

we'll want to ensure that each type of notification can be toggled on/off

no immediate gut reaction on where this should live, but likely the new account page?

we might need to also build out an email service for these notifications that can be toggled on and off per notification type, per user

Design Versions
Each version should contain the following:

the version number
a link to the prototype
a list of all changes made since the last version and why those changes were made
a screenshot of the new UI
any research performed on this version, as well as outcomes for the next version

Version 1
Prototype Link:
Changes
Please list all changes made to this version from the last, and indicate why that change was made when appropriate.

we added a bulleted list

this was done as a result of...

etc.

Screenshot
Research/Feedback & Outcomes
Please include notes, links, images, etc. that are associated with any research performed on this version only. Outline any outcomes required in the next version.
Version 2
Repeat versions as necessary.

Turns out Laravel has native notification support: https://laravel.com/docs/6.x/notifications.
This will help out quite a bit with the implementation of this feature, although there's still some complexity around pushing notifications between the server and the frontend. I think the most important thing at this stage is figuring out a "data architecture" for what constitutes a notification, and how notifications are different between user roles.

I don't have much to say that @Khristophor didn't already cover. We need to figure out all the types of notifications we need, and what information each of them needs to capture.

I just realized that I've been conflating Comments (#1532) and Notifications in my head. We could also present each comment as a separate notification, but we wouldn't have to. New comments could create a single "You have new comments" notification. How are comments and notifications intended to interact?

After doing a bit of reading I sort of assumed a comment would be a separate model (in terms of Laravel architecture), but passed in to a Laravel notification. The example given is:
<?php

namespace App;

use Illuminate\Foundation\Auth\User as Authenticatable;
use Illuminate\Notifications\Notifiable;

class User extends Authenticatable
{
    use Notifiable;
}

and then sending it
use App\Notifications\InvoicePaid;

$user->notify(new InvoicePaid($invoice));

where we could call new NewActivity($comment, $location); (terrible naming, I know) or something.

This is all great! To clarify how I was seeing it in my head:
Comments (generically), and activity on a job poster (e.g. the job was published on Mar 21st 2019) are both TYPES of notifications, but there are other types (as outlined above). On their own, they are their own models.
With this approach, we can make the activity feed outlined in #1763 a filtered list of notifications that contains only comments and activity. Compare that to the eventual notification feed every user will have, which will have an aggregate of ALL notification types, comments and activities included. :)


Manage package with cruft

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

Project coverage is 92.57%. Comparing base (6237310) to head (b10c80f).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #977   +/-   ##
=======================================
  Coverage   92.57%   92.57%
=======================================
  Files          19       19
  Lines        1818     1818
=======================================
  Hits         1683     1683
  Misses        135      135

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


[$250] Login - Changing link to staging doesn't log in user/display welcome modal

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 9.0.73-0
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?:  N/A
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/5315890
Issue reported by: Applause - Internal Team
Action Performed:

Open new expensify web
create a new expensifail user
once recieved the link, copy it
change to staging and paste in browser in different window

Expected Result:
The link should log in the user with a new account and should display a welcome modal
Actual Result:
The user is not logged in in any window and welcome modal is not displayed
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android: Standalone
[ ] Android: HybridApp
[ ] Android: mWeb Chrome
[ ] iOS: Standalone
[ ] iOS: HybridApp
[ ] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

https://github.com/user-attachments/assets/881b150a-abe1-473e-b3bd-2c2e6945c569
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~021867607890498748252
Upwork Job ID:<PHONE_NUMBER>498748252
Last Price Increase: 2024-12-20

Issue OwnerCurrent Issue Owner: @hungvu193

Though this isn't a customer flow since it's on staging, the flow itself - logging in - is pretty important, so I think we should look into getting this fixed.

Look like an BE issue 🤔

Not overdue

Updating to Internal and adjusting the priority

Actually - since this is only happening on Staging, I am going to close for now.


Broken link in sdk comparision about lifecycle

Is there an existing issue for this?

[X] I have searched the existing issues

Expected behavior
The link is broken for the reference to platform sdk lifecycle implementation
Yes. See Manual Lifecycle Implementation
should guide to: https://developer.adobe.com/client-sdks/documentation/mobile-core/lifecycle/ ?
Actual behavior
"Yes. See Manual Lifecycle Implementation"
leads to a 404
Steps to reproduce
Go to https://developer.adobe.com/client-sdks/previous-versions/documentation/upgrade-platform-sdks/comparison/#core-functionality and click "Yes. See [Manual Lifecycle Implementation]"
Environment

Browser: Chrome
OS: Mac

Sample code
No response
Logs
No response

@morritza The broken Lifecycle link has been fixed. Thanks for the feedback.


Parsl jobs lost on larger workflows: parsl.executors.high_throughput.interchange.ManagerLost

I've been trying to run a large example through the current Fractal architecture and ran into this issue:
Jobs start (up to 4 jobs for the 10 well case). After some time, some jobs finish. Some other jobs start. They run for a few minutes. After about 10 minutes, all jobs have stopped.
It created the zarr structure, created ROI tables within them. But no image data ever gets written to the zarr file. And the server contains this error message:
ERROR:    Exception in ASGI application
Traceback (most recent call last):
  File "/data/homes/jluethi/.conda/envs/fractal-dev/lib/python3.8/site-packages/parsl/dataflow/dflow.py", line 797, in _unwrap_futures
    new_inputs.extend([dep.result()])
  File "/data/homes/jluethi/.conda/envs/fractal-dev/lib/python3.8/concurrent/futures/_base.py", line 437, in result
    return self.__get_result()
  File "/data/homes/jluethi/.conda/envs/fractal-dev/lib/python3.8/concurrent/futures/_base.py", line 389, in __get_result
    raise self._exception
  File "/data/homes/jluethi/.conda/envs/fractal-dev/lib/python3.8/site-packages/parsl/dataflow/dflow.py", line 288, in handle_exec_update
    res = self._unwrap_remote_exception_wrapper(future)
  File "/data/homes/jluethi/.conda/envs/fractal-dev/lib/python3.8/site-packages/parsl/dataflow/dflow.py", line 481, in _unwrap_remote_exception_wrapper
    result = future.result()
  File "/data/homes/jluethi/.conda/envs/fractal-dev/lib/python3.8/concurrent/futures/_base.py", line 437, in result
    return self.__get_result()
  File "/data/homes/jluethi/.conda/envs/fractal-dev/lib/python3.8/concurrent/futures/_base.py", line 389, in __get_result
    raise self._exception
  File "/data/homes/jluethi/.conda/envs/fractal-dev/lib/python3.8/site-packages/parsl/executors/high_throughput/executor.py", line 438, in _queue_management_worker
    s.reraise()
  File "/data/homes/jluethi/.conda/envs/fractal-dev/lib/python3.8/site-packages/parsl/app/errors.py", line 138, in reraise
    reraise(t, v, v.__traceback__)
  File "/data/homes/jluethi/.conda/envs/fractal-dev/lib/python3.8/site-packages/six.py", line 719, in reraise
    raise value
  File "/data/homes/jluethi/.conda/envs/fractal-dev/lib/python3.8/site-packages/parsl/executors/high_throughput/interchange.py", line 559, in start
    raise ManagerLost(manager_id, m['hostname'])
parsl.executors.high_throughput.interchange.ManagerLost: Task failure due to loss of manager 4b73cc5f7614 on host pelkmanslab-slurm-worker-011

Currently can't use parsl visualize, because my current installation approach doesn't seem to make that easy somehow. I'm a bit worried if we're loosing the manager, if a job gets suddenly shut down. Where would we find more relevant logs?
This is my run script for the example:
# Register user (this step will change in the future)
http POST localhost:8000/auth/register<EMAIL_ADDRESS>password=test

# Define/initialize empty folder for project-related info
# (and also for the output dataset -- see below)
TMPDIR=`pwd`/tmp-proj-1
rm -r $TMPDIR
mkdir $TMPDIR

# Set useful variables
PROJECT_NAME="project_10x10"
DATASET_IN_NAME="input-ds-1"
DATASET_OUT_NAME="output-ds-1"
WORKFLOW_NAME="My worfklow 1"

# Create project
fractal project new $PROJECT_NAME $TMPDIR

INPUT_PATH=/data/active/fractal/3D/PelkmansLab/CardiacMultiplexing/Cycle1_5x5_10wells_constantZ
OUTPUT_PATH=/data/active/jluethi/Fractal/20220914_10well_5x5

# Update dataset info
fractal dataset modify-dataset $PROJECT_NAME "default" --new_dataset_name $DATASET_IN_NAME --type image --read_only true

# Add resource to dataset
fractal dataset add-resource $PROJECT_NAME $DATASET_IN_NAME ${INPUT_PATH} --glob_pattern *.png

# Add output dataset
fractal project add-dataset $PROJECT_NAME $DATASET_OUT_NAME --type zarr
fractal dataset add-resource $PROJECT_NAME $DATASET_OUT_NAME ${OUTPUT_PATH} --glob_pattern *.zarr

# Create workflow
fractal task new "$WORKFLOW_NAME" workflow image zarr

# Add subtasks (with args, if needed)
echo "{\"num_levels\": 5, \"coarsening_xy\": 2, \"channel_parameters\": {\"A01_C01\": {\"label\": \"DAPI\",\"colormap\": \"00FFFF\",\"start\": 110,\"end\": 800 }, \"A01_C02\": {\"label\": \"nanog\",\"colormap\": \"FF00FF\",\"start\": 110,\"end\": 290 }, \"A02_C03\": {\"label\": \"Lamin B1\",\"colormap\": \"FFFF00\",\"start\": 110,\"end\": 1600 }}}" > ${TMPDIR}/args_create.json
fractal task add-subtask "$WORKFLOW_NAME" "Create OME-ZARR structure" --args_json ${TMPDIR}/args_create.json

echo "{\"parallelization_level\" : \"well\", \"executor\": \"cpu\"}" > ${TMPDIR}/args_yoko.json
fractal task add-subtask "$WORKFLOW_NAME" "Yokogawa to Zarr" --args_json ${TMPDIR}/args_yoko.json

echo "{\"parallelization_level\" : \"well\", \"labeling_level\": 1, \"labeling_channel\": \"A01_C01\", \"executor\": \"gpu\"}" > ${TMPDIR}/args_labeling.json
fractal task add-subtask "$WORKFLOW_NAME" "Per-FOV image labeling" --args_json ${TMPDIR}/args_labeling.json

fractal task add-subtask "$WORKFLOW_NAME" "Replicate Zarr structure"
echo "{\"parallelization_level\" : \"well\", \"executor\": \"cpu\"}" > ${TMPDIR}/args_mip.json
fractal task add-subtask "$WORKFLOW_NAME" "Maximum Intensity Projection" --args_json ${TMPDIR}/args_mip.json

echo "{\"parallelization_level\" : \"well\", \"labeling_level\": 2, \"labeling_channel\": \"A01_C01\", \"executor\": \"gpu\"}" > ${TMPDIR}/args_whole_well_labeling.json
fractal task add-subtask "$WORKFLOW_NAME" "Whole-well image labeling" --args_json ${TMPDIR}/args_whole_well_labeling.json

echo "{\"parallelization_level\" : \"well\", \"level\": 0, \"table_name\": \"nuclei\", \"executor\": \"cpu\", \"workflow_file\": \"/data/homes/jluethi/fractal_3repo/fractal/examples/05_10x10_test_constant_z/regionprops_from_existing_labels_feature.yaml\"}" > ${TMPDIR}/args_measurement.json
fractal task add-subtask "$WORKFLOW_NAME" "Measurement" --args_json ${TMPDIR}/args_measurement.json

# Apply workflow
fractal workflow apply $PROJECT_NAME $DATASET_IN_NAME "$WORKFLOW_NAME" --output_dataset_name $DATASET_OUT_NAME

Ah ok. So then, server-side, would be important that these types of messages go to some log where the user knows to look. This was in parsl.log?
And the actual issue then is on the task side, thanks for opening it there! :)

It's not parsl.log, but it's within the SLURM logs (as in fractal->parsl->slurm). Then parsl fails "badly", because of a slurm error, and the ManagerLost is not very informative.
Those logs are located in paths like
server/runinfo/000/submit_scripts/parsl.slurm.1663225286.5581121.submit.stderr

The issue of harmonizing logs is broader than this single case, so I'm closing this issue and we should come back to this topic later on with some more organized plans.
But I think that we first need to consolidate our choices on parsl executors, before entering monitoring/logs organization. The current choice seems to work (up to task errors, of course), but we still need to make sure that we are happy with it.


Add support for salt-api

As suggested by @jothibasu-kamaraj, salt-api support is going to be added.

Image 3000.3_1 is ready at Dockerhub and Quay.io 🎉
docker pull cdalvaro/saltstack-master:3000.3_1


summary IOL2 for igor

also for CC blog https://docs.google.com/document/d/1g0GY7uOWNQACtBqBsJ7vNUOafmiF4ZLpeweEt53UtA0/edit

scheduled for publishing monday 6am pacific. also need to send this blog post to the IOL1 and 2 lists, publish on open policy network blog, send to cc affiliates and staff lists too, OPN google group

https://blog.creativecommons.org/2016/03/28/reporting-back-institute-open-leadership-2/


removing CTOs who aren't part of advocacy anymore. cleaning up images

Docs Build status updates of commit eeb0bd7:
:warning: Validation status: warnings

File
Status
Preview URL
Details

advocates/toc.yml
:warning:Warning
View
Details

advocates/index.html.yml
:warning:Warning
View
Details

advocates/map.yml
:warning:Warning
View
Details

advocates/andrew-harvey.yml
:white_check_mark:Succeeded

advocates/duncan-davidson.yml
:white_check_mark:Succeeded

advocates/lims-wang.yml
:white_check_mark:Succeeded

advocates/media/profiles/andrew-harvey.png
:white_check_mark:Succeeded

advocates/media/profiles/davis-joseph.png
:white_check_mark:Succeeded

advocates/media/profiles/duncan-davidson.png
:white_check_mark:Succeeded

advocates/media/profiles/gustavo-cordido.jpeg
:white_check_mark:Succeeded

advocates/media/profiles/lims-wang.jpg
:white_check_mark:Succeeded

advocates/media/profiles/munipuli.png
:white_check_mark:Succeeded

advocates/media/profiles/nina-zakharenko.jpg
:white_check_mark:Succeeded

advocates/media/profiles/penina-weiss.png
:white_check_mark:Succeeded

advocates/media/profiles/rong-yu.png
:white_check_mark:Succeeded

advocates/muniraju-pulipalyam.yml
:white_check_mark:Succeeded

advocates/penina-weiss.yml
:white_check_mark:Succeeded

advocates/rong-yu.yml
:white_check_mark:Succeeded

advocates/toc.yml

Line 27, Column 10: [Warning-xref-not-found] Cross reference not found: 'advocates.andrew-harvey'.
Line 91, Column 10: [Warning-xref-not-found] Cross reference not found: 'advocates.duncan-davidson'.
Line 135, Column 10: [Warning-xref-not-found] Cross reference not found: 'advocates.lims-wang'.
Line 147, Column 10: [Warning-xref-not-found] Cross reference not found: 'advocates.muniraju-pulipalyam'.
Line 155, Column 10: [Warning-xref-not-found] Cross reference not found: 'advocates.penina-weiss'.
Line 163, Column 10: [Warning-xref-not-found] Cross reference not found: 'advocates.rong-yu'.

advocates/index.html.yml

Line 10, Column 8: [Warning-file-not-found] Invalid file link: './map'.
Line 12, Column 8: [Warning-file-not-found] Invalid file link: './tweets'.
Line 110, Column 8: [Warning-xref-not-found] Cross reference not found: 'advocates.andrew-harvey'.
Line 114, Column 10: [Warning-file-not-found] Invalid file link: 'media/profiles/andrew-harvey.png'.
Line 430, Column 8: [Warning-xref-not-found] Cross reference not found: 'advocates.duncan-davidson'.
Line 434, Column 10: [Warning-file-not-found] Invalid file link: 'media/profiles/duncan-davidson.png'.
Line 650, Column 8: [Warning-xref-not-found] Cross reference not found: 'advocates.lims-wang'.
Line 654, Column 10: [Warning-file-not-found] Invalid file link: 'media/profiles/lims-wang.jpg'.
Line 710, Column 8: [Warning-xref-not-found] Cross reference not found: 'advocates.muniraju-pulipalyam'.
Line 714, Column 10: [Warning-file-not-found] Invalid file link: 'media/profiles/munipuli.png'.
Line 750, Column 8: [Warning-xref-not-found] Cross reference not found: 'advocates.penina-weiss'.
Line 754, Column 10: [Warning-file-not-found] Invalid file link: 'media/profiles/penina-weiss.png'.
Line 790, Column 8: [Warning-xref-not-found] Cross reference not found: 'advocates.rong-yu'.
Line 794, Column 10: [Warning-file-not-found] Invalid file link: 'media/profiles/rong-yu.png'.

advocates/map.yml

Line 106, Column 8: [Warning-xref-not-found] Cross reference not found: 'advocates.andrew-harvey'.
Line 110, Column 10: [Warning-file-not-found] Invalid file link: 'media/profiles/andrew-harvey.png'.
Line 426, Column 8: [Warning-xref-not-found] Cross reference not found: 'advocates.duncan-davidson'.
Line 430, Column 10: [Warning-file-not-found] Invalid file link: 'media/profiles/duncan-davidson.png'.
Line 646, Column 8: [Warning-xref-not-found] Cross reference not found: 'advocates.lims-wang'.
Line 650, Column 10: [Warning-file-not-found] Invalid file link: 'media/profiles/lims-wang.jpg'.
Line 706, Column 8: [Warning-xref-not-found] Cross reference not found: 'advocates.muniraju-pulipalyam'.
Line 710, Column 10: [Warning-file-not-found] Invalid file link: 'media/profiles/munipuli.png'.
Line 746, Column 8: [Warning-xref-not-found] Cross reference not found: 'advocates.penina-weiss'.
Line 750, Column 10: [Warning-file-not-found] Invalid file link: 'media/profiles/penina-weiss.png'.
Line 786, Column 8: [Warning-xref-not-found] Cross reference not found: 'advocates.rong-yu'.
Line 790, Column 10: [Warning-file-not-found] Invalid file link: 'media/profiles/rong-yu.png'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 5396799:
:warning: Validation status: warnings

File
Status
Preview URL
Details

advocates/index.html.yml
:warning:Warning
View
Details

advocates/andrew-harvey.yml
:white_check_mark:Succeeded

advocates/duncan-davidson.yml
:white_check_mark:Succeeded

advocates/lims-wang.yml
:white_check_mark:Succeeded

advocates/map.yml
:white_check_mark:Succeeded
View

advocates/media/profiles/andrew-harvey.png
:white_check_mark:Succeeded

advocates/media/profiles/davis-joseph.png
:white_check_mark:Succeeded

advocates/media/profiles/duncan-davidson.png
:white_check_mark:Succeeded

advocates/media/profiles/gustavo-cordido.jpeg
:white_check_mark:Succeeded

advocates/media/profiles/lims-wang.jpg
:white_check_mark:Succeeded

advocates/media/profiles/munipuli.png
:white_check_mark:Succeeded

advocates/media/profiles/nina-zakharenko.jpg
:white_check_mark:Succeeded

advocates/media/profiles/penina-weiss.png
:white_check_mark:Succeeded

advocates/media/profiles/rong-yu.png
:white_check_mark:Succeeded

advocates/muniraju-pulipalyam.yml
:white_check_mark:Succeeded

advocates/penina-weiss.yml
:white_check_mark:Succeeded

advocates/rong-yu.yml
:white_check_mark:Succeeded

advocates/toc.yml
:white_check_mark:Succeeded
View

advocates/index.html.yml

Line 10, Column 8: [Warning-file-not-found] Invalid file link: './map'.
Line 12, Column 8: [Warning-file-not-found] Invalid file link: './tweets'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


[Bug]: All models filtered out when browsing while logged in

What happened?
Yesterday, I noticed that all models are filtered out when I am browsing while logged in. This is true on the main page, as well as my liked models page and any user pages. The exception is the hidden models page, where I can still see the (faded) list of hidden models.
This issue affects me when logged in on multiple browsers, but not when logged out. If I have the model page link, I can still go to the page and interact with it, only search is impaired.
Steps to reproduce the problem

I logged in, and went to the main page, removing all filters. I get the no results found icon.
I log out, and the search works fine.
I made a burner account to see if it was a system/browser issue, but I the new account works fine.
I attempted other troubleshooting steps as well (clearing cookies, disabling browser extensions, etc..)

What should have happened?
I just want to restore normal account behavior. It's strange that it seems to be account specific. My guess is that I triggered a bug when switching a few user settings in rapid combination that corrupted some user setting. I'm okay if you need to reset my account: I can rebuild my likes/hidden settings, but just want to keep the supporter badge.
What platforms do you use to access the site?
Windows
What browsers do you use to access the site?
Mozilla Firefox, Google Chrome
Additional information, context and logs
No response

Hey @Machinekng, is this still an issue you are experiencing? Sharing screenshots or screen recording might help us identify your the problem. I'd appreciate if you share with us your user account as well to have a deeper look into it. Thanks!

Of course. The account on civitai is also machinekng.
This is what it looks like when I am logged in:

This is what it looks like when I am logged out:

Yah, i cannot search for a specific model anymore, this greatly affect some abilities using sd-civitai-brower on webui from here. https://github.com/camenduru/sd-civitai-browser

Yah, i cannot search for a specific model anymore, this greatly affect some abilities using sd-civitai-brower on webui from here. https://github.com/camenduru/sd-civitai-browser

Yeah, looks like the site is effectively down right now. I can't search or even log in.

I have the same problem

This always happens to me after I've hidden an X amount of models. Not sure if it's the cause.

This always happens to me after I've hidden an X amount of models. Not sure if it's the cause.

I do have a lot of models hidden, and now that you mention it, the issue could have cropped up when I was hiding models.
Were you able to fix the issue by unhiding models?

I unhide all the users I was currently hiding (170+ users) and some additional models and search is now working again.
I think that means this is a bug with the hidden model filter?

Another update, I tried hiding by tag instead of user/model, and the issue came up again once I added enough tags. I removed a few, and search is working.

This always happens to me after I've hidden an X amount of models. Not sure if it's the cause.

I do have a lot of models hidden, and now that you mention it, the issue could have cropped up when I was hiding models.
Were you able to fix the issue by unhiding models?

Short of deleting the account and starting over I never found a solution for it.
In the end I stopped hiding models. Unfortunatly the Everything filter isn't showing up Adult results now so that's another issue.

@Machinekng thanks for sharing that information. That's pretty crucial to get to the root cause of this problem. I'll be making some tests to see if I'm able to reproduce the issue and come up with a solution for it

Ill add that for me it only seems to affect some models?

Ill add that for me it only seems to affect some models?

That's probably unrelated to the hidden model bug, especially as there was recently a purge of TOS-violating models.

Ill add that for me it only seems to affect some models?

That's probably unrelated to the hidden model bug, especially as there was recently a purge of TOS-violating models.

Nah i figured out later that it was any NSFW model for me, even with the option enabled

With our latest release, this should be resolved now. Please let us now if you are still experiencing issues when filtering models or excluding tags/users/models.

No, I'm having this issue here too. But, only on desktop. As a test I tried on my phone, everything shows. But I'm not about to be downloading this sort of thing on my phone.
 It happens for all models, adult or not.

same issue here, any fix, please? I see this was reported in February...

fixed as soon as i commented, to anyone wondering it seems Civit will do this when its down, so if its happening to you maybe you just need to wait it out

It does seem to be happening again. Can only see models with the Everything browsing mode turned on atm.

its 2024 now and I just created an account, I am having the exact same issue and its just after creating an account. Was there ever a definite fix for this issue? or are we just not able to use the account? Absolutely no search results are popping up for me on my MacBook or my phone after logging into my account.

I am getting this today. I don't see any models if you click on the Models tab.


Add rake script to export/import policies and policy profiles

This PR continues the work to add export/import support similar to the CFME RH Consulting Scripts to ManageIQ by adding support for exporting and importing MiqPolicy and MiqPolicySet objects.

@gmcculloug,
This is similar to PR #14126 that @carbonin merged a couple weeks ago.
Brant

@gmcculloug any feedback on this?

@branic Hey Brant, just wanted to make sure that you were good with the changes I suggested, please let me know if you need any help or have any questions. Thanks.

@eclarizio I think I'm good with the changes suggested. I haven't had time to look at them in detail yet. I'm hoping to be able to do that and make the updates in the next week or so.

@eclarizio I finally was able to make the changes to the spec files.

@eclarizio Are there any other changes you would like me to make on this PR?

@gmcculloug No reason to keep them. I just forgot to delete them before committing. They have now been removed.


Add Express.js Middleware

Hi, is this issue still open?
If yes then what is the requirement, would like to contribute.


weighting add support for min capping

We want the ability to set min and max capping in a weight scheme, e.g.:
scheme = qp.Rim("My weight scheme", cap=(0.05, 5))

Which would make sure no factors were less than 0.05 or more than 5.
Existing use will be interpreted as max-only capping, e.g.:
scheme = qp.Rim("My weight scheme", cap=5)

Opt out of anesrake cap correction using:
scheme.anesrake_cap_correction = False

This PR resolved by #618.


Simple filter || Autofilter

Hi,
I was hoping you might be able to help. Love the project and I have everything working great.
Is there any way to add a simple filter to a row of columns?
i.e. add a simply filter button to the each column A-K in row 3.
Even if it involves me making specific changes to my SRC file - happy to do that.
I just can't find any documentation in general about how I could add this with PHP in the generation of a xlsx file.
Any help would be much appreciated!
Donal

SimpleXLSXGen 1.2.16
https://github.com/shuchkin/simplexlsxgen
https://c-rex.net/projects/samples/ooxml/e1/Part4/OOXML_P4_DOCX_autoFilter_topic_ID0EIDM4.html#topic_ID0EIDM4
$data = [
    ['autofilter'],
    [1000],
    [2000],
    [3000],
    [4000],
    [5000],
    [1500]
];
$xlsx = SimpleXLSXGen::fromArray($data);

// hack
$xlsx->modTemplate('xl/worksheets/sheet1.xml', '<autoFilter ref="A1:A5"/>');

$xlsx->saveAs('autofilter.xlsx');

Amazing - thanks so much!
I have this working but I have one issue that arises.
My code looks like this:
`$xlsx2 = SimpleXLSXGen::fromArray( $reportCells )
->setDefaultFont( 'Helvetica Neue' )
->setDefaultFontSize( 12 )
->setColWidth(1, 6)
->setColWidth(2, 6)
->setColWidth(3, 50)
->setColWidth(4, 20)
->setColWidth(5, 35)
->setColWidth(6, 25)
->setColWidth(7, 25)
->setColWidth(8, 25)
->setColWidth(9, 35)
->setColWidth(10, 30)
->setColWidth(11, 35);
// ->mergeCells('A1:I1');
// ->mergeCells('A2:I2');
$xlsx2->modTemplate('xl/worksheets/sheet1.xml', '');
$xlsx2->saveAs($saveReportPath.'/'.$projectNameForReport.'.xlsx'); `
If I add the mergeCell commands (which were working before - amending semi colon etc) it causes an error when I now add the autofilter. Without the mergeCells the autofilter works.
Also how would I add two autofilters? i.e. the A column works fine but I can't figure out how to do a B column as well etc
Thanks so much for your help!
Donal

fixed in 1.2.16
use $xlsx->autoFilter('A2:B10');

Thanks so much - sorry I missed that I could just change the column letter and it would run across.
I still seem to have the mergecell issue. Individually the "mergeCells" and "modTemplate" work - but as soon as I have both of them it creates an error in the xlsx file.
I'm looking at the SRC file - could it be something with how the strings are swapped in?