Running app.py raises errors

Problem Description
I'm trying to run app.py with the following command:
python app.py --share --version ppt-v2 --checkpoint_dir checkpoints/ppt-v2

However, it throws the following error:
usage: app.py [-h] --pretrained_model_path PRETRAINED_MODEL_PATH [--base_model_path BASE_MODEL_PATH] [--weight_dtype WEIGHT_DTYPE] [--share] [--local_files_only] [--port PORT]
app.py: error: the following arguments are required: --pretrained_model_path

Attempts to Solve the Issue
I tried setting pretrained_model_path directly in app.py as ppt2, but encountered another error:
usage: app.py [-h] [--pretrained_model_path PRETRAINED_MODEL_PATH] [--base_model_path BASE_MODEL_PATH] [--weight_dtype WEIGHT_DTYPE] [--share] [--local_files_only] [--port PORT]
app.py: error: unrecognized arguments: --version ppt-v2 --checkpoint_dir checkpoints/ppt-v2

Could you please advise on:

How to correctly specify pretrained_model_path and other required arguments?
Whether --version and --checkpoint_dir are supported parameters, and if so, how they should be used?

Thank you!

Hi, how do you solve this problem ?

Sure. The reason is that the README file doesn't match the dev branch. Switching to the main branch can solve this issue.

@Rayjryang Thanks for answering


Allow moderator to define user names

Hi, I'd like to provide a suggestion to Jitsi: I'm convincing people to use Jitsi for secure video conferences, but most of these folks are quite tech illiterate. I suggest that the session initiator (moderator) should have the ability to set users names, which can be overridden by the user themselves. This would make it easier to understand who wants to speak.
Thanks and great work so far!

Please use the community forum when you have questions, problems or suggestions before opening new issues.
Wrong repo. There are already options that will force users to write displayname the first time they join, which can be enabled on self hosted deployments.


Is there a way to do iframe content caching?

I am working on the iframe popup that will pre-load the content from reference site in background.
After content is fully loaded, the popup will open up. Colorbox also remove the iframe after closing it.
Is there some tricky ways to do:

Preloading the content inside iframe then display colorbox after content fully loaded.
Caching the content inside iframe so it will not load the same content again next time colorbox is shown.

Thanks,
Paul

Could you just create the iframe element and add it to your document,
then use colorbox's inline property to show it?  That way the iframe
element is just being moved around the document instead of being
removed.
On Thu, Dec 15, 2011 at 5:56 AM, jamella2002
<EMAIL_ADDRESS>wrote:

I am working on the iframe popup that will pre-load the content from reference site in background.
After content is fully loaded, the popup will open up. Colorbox also remove the iframe after closing it.
Is there some tricky ways to do:

Preloading the content inside iframe then display colorbox after content fully loaded.
Caching the content inside iframe so it will not load the same content again next time colorbox is shown.

Thanks,
Paul

Reply to this email directly or view it on GitHub:
https://github.com/jackmoore/colorbox/issues/147

--
Jack Moore
jacklmoore.com
twitter.com/jacklmoore

I've been able to get the content in my iframes to cache at a browser level by making sure the server returns the appropriate HTTP cache headers.


paramsForServer and paramsFromClient  is not a function

const { paramsForServer } = require('feathers-graph-populate'); const { paramsFromClient } = require('feathers-graph-populate');
When I use either of the two requires, I get the following error:

Uncaught TypeError: paramsForServer is not a function

Thanks for reporting, @juancampuzano!  Somehow I failed to include them in the repo.  Please try again with<EMAIL_ADDRESS> paramsForServer is a CommonJS module.  Please let me know if you have any issues using it.

Thanks for your Help! Now I am getting the following error:
TypeError: makeShallowPopulate is not a function at deepPopulateHook

Weird.  I don’t know how this is working for me in my project.  I’ll get back to you.

@juancampuzano, please upgrade to the latest patch release, I believe it's<EMAIL_ADDRESS> Should be fixed, now

@marshallswain  Thank you very much, I will review and I will tell you.

@juancampuzano I'm going to go ahead and close this.  Please let me know if there's still an issue.


Nonce not added as attribute

This plugin does not apply the nonce attribute to the gtm script tag. when inspecting the script element in chrome I can see no nonce value added to the attributes list, however it is there as a property.
This is the following error breaking our CSP.
The source list for the Content Security Policy directive 'script-src' contains an invalid source: ''nonce-{{nonce}}''. It will be ignored.
Here is my implementation, is there a work around or fix ?

`import { createGtm, useGtm } from '@gtm-support/vue-gtm'
import analyticsFactory from '~/services/analytics/analyticsFactory'

export default defineNuxtPlugin((nuxtApp) => {
  const config = useRuntimeConfig()
  const nonce = useNonce()

  nuxtApp.vueApp.use(
    createGtm({
      id: 'XXXXXXXXXXX',
      enabled: true,
      nonce
    })
  )

  return {
    provide: {
      gtm: useGtm(),
      dataLayer: analyticsFactory()
    }
  }
})`

Maybe you need to use this: https://github.com/gtm-support/vue-gtm/issues/209#issuecomment-1732417673

Tried this already but makes no difference, nonce does not get applied correctly

Same here, nonce is not applied. Tried with both @gtm-support/vue-gtm and @zadigetvoltaire/nuxt-gtm.


8.0.0 "Cannot find module './package.json'"

Description
7.3.0 works
8.0.0 breaks
Steps to reproduce
example package.json. fails on git push (pre-push hook). lint-staged v8.0.0 looks to have a compatibility issue with husky.
{
  "name": "example",
  "version": "0.0.1",
  "private": true,
  "scripts": {
    "start": "              echo 'start code watcher';            react-native start --reset-cache",
    "ios": "                echo 'develop on ios';                react-native run-ios --simulator \"iPhone X\"",
    "android": "            echo 'develop on android';            react-native run-android",
    "web": "                echo 'develop on web';                react-scripts-ts start",
    "build": "              echo 'build production web';          react-scripts-ts build",
    "debug": "              echo 'run redux debugger';            open 'rndebugger://set-debugger-loc?host=localhost&port=8081'",
    "test": "               echo 'run unit tests';                jest --coverage",
    "watch": "              echo 'run unit tests reloader';       jest --watch",
    "lint": "               echo 'run code linter';               tsc && tslint --fix -p tsconfig.json -c tslint.json",
    "upgrade": "            echo 'run react native upgrade'       yarn global add react-native-git-upgrade; react-native-git-upgrade; rm -f .babelrc; rm -f ./.buckconfig; rm -f ./.flowconfig; rm -f ./.watchmanconfig; rm -f ./.gitattributes;",
    "reset": "              echo 'run react native cache reset';  watchman watch-del-all; rm -rf /tmp/metro-bundler-cache-*; rm -rf ./android/build; rm -rf ./android/.gradle; rm -rf ./android/app/build; rm -rf ~/Library/Developer/Xcode/DerivedData; rm -rf /tmp/haste-map-react-native-packager-*; rm -rf ./ios/build; yarn install; pod install --project-directory=ios; react-native start --reset-cache",
    "semantic-release": "   echo 'run continuous integration';    semantic-release",
    "travis-deploy-once": " echo 'prevent multiple deploys';      travis-deploy-once"
  },
  "husky": {
    "hooks": {
      "pre-push": "lint-staged && yarn lint && yarn test",
      "commit-msg": "commitlint -E HUSKY_GIT_PARAMS"
    }
  },
  "lint-staged": {
    "src/**/*.{js,jsx,ts,tsx,css,md}": [
      "prettier --write",
      "git add"
    ]
  },
  "release": {
    "verifyConditions": [
      "@semantic-release/changelog",
      "@semantic-release/git"
    ],
    "prepare": [
      {
        "path": "@semantic-release/changelog",
        "changelogFile": "CHANGELOG.md"
      },
      "@semantic-release/git"
    ],
    "publish": [
      "@semantic-release/github"
    ]
  },
  "commitlint": {
    "extends": [
      "@commitlint/config-conventional"
    ]
  },
  "dependencies": {
    "react": "16.6.0",
    "react-dom": "16.6.0",
    "react-native": "0.57.4",
    "react-native-keyboard-aware-scroll-view": "0.7.4",
    "react-native-vector-icons": "6.0.2",
    "react-native-web": "0.9.4",
    "react-redux": "5.1.0",
    "react-router": "4.3.1",
    "react-router-dom": "4.3.1",
    "react-router-native": "4.3.0",
    "react-scripts-ts": "3.1.0",
    "react-test-renderer": "16.6.0",
    "redux": "4.0.1",
    "redux-thunk": "2.3.0"
  },
  "devDependencies": {
    "@commitlint/cli": "7.2.1",
    "@commitlint/config-conventional": "7.1.2",
    "@semantic-release/changelog": "3.0.1",
    "@semantic-release/git": "7.0.5",
    "@semantic-release/github": "5.2.1",
    "@types/jest": "23.3.8",
    "@types/react": "16.4.18",
    "@types/react-native": "0.57.7",
    "@types/react-native-vector-icons": "4.6.4",
    "@types/react-redux": "6.0.9",
    "@types/react-router": "4.0.32",
    "@types/react-router-dom": "4.3.1",
    "@types/react-router-native": "4.2.3",
    "@types/react-test-renderer": "16.0.3",
    "babel-jest": "23.6.0",
    "babel-preset-react-native": "4.0.1",
    "codecov": "3.1.0",
    "husky": "1.1.2",
    "jest": "23.6.0",
    "lint-staged": "8.0.0",
    "prettier": "1.14.3",
    "react-art": "16.6.0",
    "react-native-typescript-transformer": "1.2.10",
    "semantic-release": "15.10.6",
    "travis-deploy-once": "5.0.9",
    "ts-jest": "23.10.4",
    "typescript": "3.1.3"
  },
  "babel": {
    "presets": [
      "react-native"
    ]
  },
  "jest": {
    "preset": "react-native",
    "collectCoverageFrom": [
      "src/**/*.{js,jsx,ts,tsx,json}"
    ],
    "coverageThreshold": {
      "global": {
        "statements": 30,
        "branches": 30,
        "functions": 30,
        "lines": 30
      }
    },
    "transform": {
      "^.+\\.jsx?$": "babel-jest",
      "^.+\\.tsx?$": "ts-jest"
    },
    "transformIgnorePatterns": [
      "node_modules/(?!react-native|react-router-native)/"
    ],
    "testRegex": "(/__tests__/.*|(\\.|/)(test|spec))\\.(jsx?|tsx?)$",
    "moduleFileExtensions": [
      "ts",
      "tsx",
      "js",
      "jsx",
      "json",
      "node"
    ],
    "globals": {
      "window": true,
      "ts-jest": {
        "babelConfig": true
      }
    }
  }
}

Debug Logs
$ git push
husky > pre-push (node v8.11.2)
module.js:549
    throw err;
    ^

Error: Cannot find module './package.json'
    at Function.Module._resolveFilename (module.js:547:15)
    at Function.Module._load (module.js:474:25)
    at Module.require (module.js:596:17)
    at require (internal/module.js:11:18)
    at Object.<anonymous> (/Users/ethanneff/Dropbox/active/dev/react-native/accomplish/node_modules/.bin/lint-staged:5:13)
    at Module._compile (module.js:652:30)
    at Object.Module._extensions..js (module.js:663:10)
    at Module.load (module.js:565:32)
    at tryModuleLoad (module.js:505:12)
    at Function.Module._load (module.js:497:3)
husky > pre-push hook failed (add --no-verify to bypass)
error: failed to push some refs

Why are you trying to run lint-stages in pre-push? It is a no-op since line-stages won’t find any staged files and won’t do anything.
From the debug log it looks like the problem is with husky. Or am I missing something crucial here?

8.0.2 fixes this. thanks!


fix(quick_lint_js): account for the fact that the archive has different structures across platforms

Ping @strager you might be interested in this. I expected the different .zip & .tar.gz archives to share the same directory structure, but it seems like the .tar.gz come wrapped with a quick-lint-js/ root directory, whereas the .zip does not


Optimizations

Micro optimizations;
Runtime cache (disabled by default);
Removed $this context of Config from included files.

 Results were consistent so only showing one number
Current master branch: 1731912
With these changes applied: 1732040 (cache enabled or disabled made no difference)

General feedback about your approach for implementing the caching, as I feel it was quite an odd one. You don't have to agree with my vision for how this would've worked, but I figured I could share nonetheless.

useCache adds state that makes it a lot harder to meaningfully unit test
I think an approach with an interface solution like this would've been far nicer, easier to test, and as a bonus would've made the library very extensible as extensions for different file formats could be made.

interface ConfigFileProvider
{
    public function getConfigFile(string $file): array;
}

class Config
{
    private readonly ConfigFileProvider $configFileProvider;
}

Then this interface provides the functionality of Config::load as you made it, rather than defining this behaviour directly inside of Config.
(Just ignore my bad name here, naming is hard, I'd come up with something else for an actual implementation)
Convenient todo:

[ ] Remove cache, it doesn't actually increase performance https://github.com/tnapf/Config/pull/1#issuecomment-1567335440
[ ] Fuck double quotes https://github.com/tnapf/Config/pull/1#discussion_r1209475288
[ ] Remove realpath https://github.com/tnapf/Config/pull/1#discussion_r1209467179

Conversations not linked can be resolved after reading as it's just me pointing something out

I couldn't reproduce the performance test scenario, unless I instantiate Config for each of 100 000 iterations.
I guess we expect different usage of Config class; I expected Config to be shared among all dependent classes, then this "runtime caching" (probably "caching" is wrong name here) works well; I had around 80 ms average for 100 000 iterations.

I couldn't reproduce the performance test scenario, unless I instantiate Config for each of 100 000 iterations or make it read 100 000 different files.

 Sorry   (the gh emoji looks quite bad so enjoy a screenshot from the discord one)
In that case however, caching does work, and assuming we can come to an agreement regarding my feedback in https://github.com/tnapf/Config/pull/1#issuecomment-1567368706 and https://github.com/tnapf/Config/pull/1#discussion_r1209469386 it'd be a nice addition

In that case however, caching does work, and assuming we can come to an agreement regarding my feedback in #1 (comment) and #1 (comment) it'd be a nice addition

I suggest merging this PR and opening an issue regarding ConfigFileProvider (or rather ConfigProvider). Then I'll make a new branch with ConfigProvider implementation.


Jenkins Plugin for ABAP (SAP Netweaver, S/4 HANA)

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Update logger.Info in Terraform driver

Description
Update logger.Info in Terraform driver
Type of change

This pull request fixes a bug in Radius and has an approved issue (issue link required).
Fixes: #6868

Auto-generated summary

🤖[deprecated] Generated by Copilot at 6faa112
Summary
:recycle::mag::key:

Refactor logging in terraform.go to use structured key-value pairs instead of formatted strings. This improves observability and consistency of the radius project.

logger.Info changed
Structured logging for clarity
Refactoring in spring

Walkthrough

Refactor the logger.Info calls to use structured key-value pairs instead of formatted strings (link,

/ok-to-test

Thanks for jumping on this 👍


[Documentation] Setup-google-maps.md

Status
Ready/In Progress/In Hold (Reason for hold)
Related Issues
fixes: link to the issue
Description
A few sentences describing the overall goals of the pull request's commits.
Screenshots
Paste here any images that will help the reviewer

@altmannyarden Not sure if you need to approve here, but you can review if required.

I dont understand - If i have the Google Maps integration enabled, do I still need to do those steps?

I dont understand - If i have the Google Maps integration enabled, do I still need to do those steps?

As far as I understand, for both automations and the integration you need to add the  API by following the steps in GCS.
To run the automations,  you need to enter the server config and for the ShowLocationOnMap automation you also need to add the automation to a layout.  For the integration you don't need the server config for it to work. See https://github.com/demisto/etc/issues/45220#issue-1090284655

I saw the issue and the KB, I still think it's a not a best practice to do add the API key in the server configuration.
Will update here after checking this issue. @richardbluestone

From my testing, adding the ui.google.api.key server config was the only way I could get these automations to work. The Google Maps integration is separate and unrelated (it uses a different Google API, the Geocoding API). This could be confusing for users, but that is a bigger issue.

@altmannyarden @ali-sawyer What do we want to do about the server configs? Once approved I can then update https://github.com/demisto/content/pull/16923

From my testing, adding the ui.google.api.key server config was the only way I could get these automations to work. The Google Maps integration is separate and unrelated (it uses a different Google API, the Geocoding API). This could be confusing for users, but that is a bigger issue.

How it is different? The showonmap script using the command from the Google Maps integration.
Anyway, I tested the "showonmap" automation:

If I configured the Google Maps integration -  the automation works.
If I added only the API key using the server configuration - the automation failed.

I wanted to test the showlocation script, but I couldn't find any integration that map the "geolocation" field.
@ali-sawyer @richardbluestone

@altmannyarden To see the `Geo Location field, go to Settings>Objects Setup>Fields and search for Geo Location. Edit the field and select Add to all Indicator types. When you edit the indicator, you should see this field. Of course you need to add the general purpose dynamic section and select the showlocation script to the layout and then add the layout to an indicator type. I will add this as note about the Geo Location field, as its not clear enough.
For the showonmap script it didn't make any difference with the integration enabled or the server config. The map appeared but with an error message.
For the showlocation script it only worked without the server config but with the same error (see attached).
I think its because billing is not enabled in GCS. We have to enter the API key either in the integration or server config to remove the error message. @ali-sawyer Do you have an API I can test?

I fired up a new instance without any integrations or server configs. You can run both scripts without the server config or instance, but the map will appear with an error. When entering the API key, the error is removed.


Nickname delay

Allow delay for nicknaming
Fixes/Resolves/Closes (please use correct syntax):

#4893

👍


Using Widgetset CDN behind HTTP Proxy

I'd like to try using the CDN - but it doesn't seem to be working behind a Proxy; it seems that Groovy's RestClient doesn't automatically use the java System Properties http.proxyHost | http.proxyPort | https.proxyHost | http.proxyPort
Could CompileWidgetsetTask be changed to (optionally) specify an http proxy on RestClient? Ideally by using the standard JVN system properties, but allowing us to override by config values on vaadinCompile.httpProxy* =
As it happens, I don't need proxy authentication, but others might => https://gist.github.com/bryanchug/4172603
FWIW, in my current project external dependencies download fine, which implies that gradle is using the HTTP Proxy (configured via ~/.gradle/gradle.properties
systemProp.http.proxyHost=theProxyHostname
systemProp.http.proxyPort=3128
systemProp.http.nonProxyHosts=localhost|artifact-repo|*.hpd.int

systemProp.https.proxyHost=theProxyHostname
systemProp.https.proxyPort=3128
systemProp.https.nonProxyHosts=localhost|artifact-repo|*.hpd.int

Here's a stacktrace showing the failure.
Execution failed for task ':orion-admin-ui:vaadinCompile'.
> java.net.SocketException: Socket is not connected: connect

* Try:
Run with --info or --debug option to get more log output.

* Exception is:
org.gradle.api.tasks.TaskExecutionException: Execution failed for task ':orion-admin-ui:vaadinCompile'.
        at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter
java:69)
        at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:4
)
[...]
Caused by: java.net.SocketException: Socket is not connected: connect
        at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:549)
        at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.jav
:180)
        at org.apache.http.impl.conn.ManagedClientConnectionImpl.open(ManagedClientConnectionImpl.java:294)
        at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:640)
        at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:479)
        at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:906)
        at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:1066)
        at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:1044)
        at groovyx.net.http.HTTPBuilder.doRequest(HTTPBuilder.java:515)
        at groovyx.net.http.RESTClient.post(RESTClient.java:141)
        at groovyx.net.http.RESTClient$post.call(Unknown Source)
        at fi.jasoft.plugin.tasks.CompileWidgetsetTask.queryRemoteWidgetset(CompileWidgetsetTask.groovy:368)
        at fi.jasoft.plugin.tasks.CompileWidgetsetTask.compileRemotely(CompileWidgetsetTask.groovy:229)
        at fi.jasoft.plugin.tasks.CompileWidgetsetTask.run(CompileWidgetsetTask.groovy:206)
        at org.gradle.internal.reflect.JavaMethod.invoke(JavaMethod.java:75)
        ... 75 more

Added proxy configurations for widgetset CDN.
Feature is documented here https://github.com/johndevs/gradle-vaadin-plugin/wiki/Using-Vaadin-CDN


cardano-testnet: don't specify delegated supply anymore. Use create-testnet-data default behavior

Description
This pops an earlier TODO and doesn't cause any runtime changes, because the behavior remains the same under the hood.
Checklist

[X] Commit sequence broadly makes sense and commits have useful messages
[X] Self-reviewed the diff

Thanks @carbolymer :pray:


Android one-click deploy tooltip not updated with one device

Godot version:
3.2 beta2
Issue description:
It always says "Select device from the list" even if only one device is connected (and with recent update it will instantly deploy, so even no list appears).

Looks like a new (half-baked) feature for the case of a single Android device with a wrong tooltip.
If you connect multiple devices, it works as expected.

It worked when I implemented #28236, so this may come from an unrelated regression or be OS/device-specific :slightly_smiling_face:

It worked when I implemented #28236, so this may come from an unrelated regression or be OS/device-specific :slightly_smiling_face:

At least I guessed correctly that it is feature :smiley_cat:

There does not seem to be a knob to stop the debug / logcat process. I would prefer to undo the change and add an entry for that instead.

Shouldn't the "stop" button do that already?

Shouldn't the "stop" button in the top bar do that already?

That isn't related to. Enable debug and hit the Android button. The only way I found to stop the debugging connection is to kill the Android app ?!?!
Honestly, someone should rework how those buttons work. Currently 'playing' / debug Android collides horribly with playing / debug a desktop app.

Is this still reproducible in 3.2.3-stable? If so, I believe this might qualify as a junior job.

If not

You probably meant if yes 🤔
Still valid in 42f209850

Hi, i am currently working on a side project in godot 3.2.x and the answer is yes, i could reproduce that bug when i connect only 1 device is still not updating the UI, but with 2 device the icon showing up and working well as expected. I tested on 3.2.2 and 3.2.3.


#165 Issue fixed

Related Issue
Social handles in the footer section and the "Contribute to Regala" should open on a new page to enhance user experience.
Closes: #165
Description of Changes
I have made the required changes to redirect all the social handles in the footer and the "Contribute to Regala" to a new page
Checklist:

[x] My code adheres to the established style guidelines of this project.
[x] I have conducted a self-review of my code.
[x] I have included comments in areas that may be difficult to understand.
[x] I have made corresponding updates to the project documentation.
[x] My changes have not introduced any new warnings.

@Astrodevil  could you please  review this PR


Incorrect code generated when multi-dimensional variable accessed by aliased dimensions

We have a case in the C-ROADS model where we have a 2D variable that uses aliased dimensions on both the left and right sides.  SDE generates incorrect array indices on the RHS in this case.
Relevant portions of the test case (I will push this on a branch as funcsubs.mdl shortly):
DimA: A1, A2, A3
  ~~|
DimA' <-> DimA
  ~~|

...

Intensity Diff[DimA,DimA']  =
  IF THEN ELSE (
    Rank[DimA] >= Rank[DimA'] ,
    ABS ( Intensity[DimA] - Other[DimA'] ),
    666
  )
  ~~|

In this case, we should see the RHS index values mirror those on the LHS, but instead, they are set to the i value only (no variation in j):
  // Intensity Diff[DimA,DimA'] = IF THEN ELSE(Rank[DimA]>=Rank[DimA'],ABS(Intensity[DimA]-Other[DimA']),666)
  _intensity_diff[0][0] = _IF_THEN_ELSE(_rank[0] >= _rank[0], _ABS(_intensity[0] - _other[0]), 666.0);
  // Intensity Diff[DimA,DimA'] = IF THEN ELSE(Rank[DimA]>=Rank[DimA'],ABS(Intensity[DimA]-Other[DimA']),666)
  _intensity_diff[0][1] = _IF_THEN_ELSE(_rank[0] >= _rank[0], _ABS(_intensity[0] - _other[0]), 666.0);
  // Intensity Diff[DimA,DimA'] = IF THEN ELSE(Rank[DimA]>=Rank[DimA'],ABS(Intensity[DimA]-Other[DimA']),666)
  _intensity_diff[0][2] = _IF_THEN_ELSE(_rank[0] >= _rank[0], _ABS(_intensity[0] - _other[0]), 666.0);
  // Intensity Diff[DimA,DimA'] = IF THEN ELSE(Rank[DimA]>=Rank[DimA'],ABS(Intensity[DimA]-Other[DimA']),666)
  _intensity_diff[1][0] = _IF_THEN_ELSE(_rank[1] >= _rank[1], _ABS(_intensity[1] - _other[1]), 666.0);
  // Intensity Diff[DimA,DimA'] = IF THEN ELSE(Rank[DimA]>=Rank[DimA'],ABS(Intensity[DimA]-Other[DimA']),666)
  _intensity_diff[1][1] = _IF_THEN_ELSE(_rank[1] >= _rank[1], _ABS(_intensity[1] - _other[1]), 666.0);
  // Intensity Diff[DimA,DimA'] = IF THEN ELSE(Rank[DimA]>=Rank[DimA'],ABS(Intensity[DimA]-Other[DimA']),666)
  _intensity_diff[1][2] = _IF_THEN_ELSE(_rank[1] >= _rank[1], _ABS(_intensity[1] - _other[1]), 666.0);
  // Intensity Diff[DimA,DimA'] = IF THEN ELSE(Rank[DimA]>=Rank[DimA'],ABS(Intensity[DimA]-Other[DimA']),666)
  _intensity_diff[2][0] = _IF_THEN_ELSE(_rank[2] >= _rank[2], _ABS(_intensity[2] - _other[2]), 666.0);
  // Intensity Diff[DimA,DimA'] = IF THEN ELSE(Rank[DimA]>=Rank[DimA'],ABS(Intensity[DimA]-Other[DimA']),666)
  _intensity_diff[2][1] = _IF_THEN_ELSE(_rank[2] >= _rank[2], _ABS(_intensity[2] - _other[2]), 666.0);
  // Intensity Diff[DimA,DimA'] = IF THEN ELSE(Rank[DimA]>=Rank[DimA'],ABS(Intensity[DimA]-Other[DimA']),666)
  _intensity_diff[2][2] = _IF_THEN_ELSE(_rank[2] >= _rank[2], _ABS(_intensity[2] - _other[2]), 666.0);

This leads to differences when comparing against the expected Vensim output:
_intensity_diff[_a1,_a2] time=0.00 vensim=666 sde=990 diff=48.648649%
_intensity_diff[_a1,_a2] time=1.00 vensim=666 sde=990 diff=48.648649%
_intensity_diff[_a1,_a3] time=0.00 vensim=666 sde=990 diff=48.648649%
_intensity_diff[_a1,_a3] time=1.00 vensim=666 sde=990 diff=48.648649%
_intensity_diff[_a2,_a1] time=0.00 vensim=990 sde=600 diff=39.393939%
_intensity_diff[_a2,_a1] time=1.00 vensim=990 sde=600 diff=39.393939%
_intensity_diff[_a2,_a3] time=0.00 vensim=666 sde=600 diff=9.909910%
_intensity_diff[_a2,_a3] time=1.00 vensim=666 sde=600 diff=9.909910%
_intensity_diff[_a3,_a1] time=0.00 vensim=990 sde=100 diff=89.898990%
_intensity_diff[_a3,_a1] time=1.00 vensim=990 sde=100 diff=89.898990%
_intensity_diff[_a3,_a2] time=0.00 vensim=600 sde=100 diff=83.333333%
_intensity_diff[_a3,_a2] time=1.00 vensim=600 sde=100 diff=83.333333%

I dug into this more last week since it was related to some of the issues that Hazhir was running into with the model he posted in discussion #557.  It is also related to a similar issue reported in #278.
Summary
There are a number of overlapping problems that would be hard to fix in isolation or in serial fashion, so I decided to tackle them together.  I have fixes in place in the chris/179-multi-dim branch that resolve the issues affecting the test case above and the one in #278.
The problems stem from how subscripts are handled in the read equations phase and in the code gen phase.  I tried as best as I could to only touch the code in those two areas for now.  There are likely some similar bugs in a couple other areas, but those can be addressed separately.
Test updates
As part of this work, I expanded the test coverage in read-equations.spec.ts and gen-equation-{c,js}.spec.ts so that we are more methodical in how different variants of subscripted equations are tested.  I added a number of describe groups in these files, and the test cases have the same names and ordering in all 3 files.  That way we can more easily diagnose the behavior of the "read equation" phase and the "code gen" phase for each test model and pinpoint any issues affecting either phase.  Going forward, any time we add a test case to read-equations.spec.ts, we should add the same test to the gen-equation-{c,js}.spec.ts files, and vice versa.
Since both the LHS and RHS subscripts (and whether a LHS/RHS variable is apply-to-all or non-apply-to-all) affect the logic in the read equation and gen equation phases, I grouped the tests as follows:

when LHS has no subscripts
when LHS is apply-to-all (1D)
when LHS is NON-apply-to-all (1D)
when LHS is apply-to-all (2D)
when LHS is NON-apply-to-all (2D)
when LHS is apply-to-all (3D)
when LHS is NON-apply-to-all (3D)

Then for each group, there are cases to cover the various combinations of RHS variable references, e.g., "when RHS variable is apply-to-all (1D) and is accessed with specific subscript".
Some of these cases were tested in sample models like the arrays model, but there were a number that were not already covered (including the ones reported in this issue, and in #278, and in Hazhir's test model).  So now we have better coverage and a standard structure to make it easier to add new test variants in the future.
Implementation fixes
The changes were in 5 specific areas:

As a first step, I removed all uses of normalizeSubscripts, which was previously used in a number of places to sort subscripts/dimensions alphabetically by family.  My observation is that this step is not necessary (correct me if I'm wrong), and makes understanding and debugging more difficult, especially in cases (like reported in this issue) where more than one subscript/dimension resolves to the same family.  To prove that it's not necessary, as a first step on this branch, I removed all calls to this function and ran the existing tests.  All of the existing model tests passed without changes, and only a few unit tests that checked for specific order needed to be updated.

I reimplemented the expandedRefIdsForVar function that is called during the read equation phase.  This function was one contributor to the bug reported in this issue.  It didn't handle the case where more than one subscript/dimension resolves to the same family, so each time through the loop it would match the first instance but would not match the others, which led to incorrect refIds.  The fixed implementation is a bit more methodical in how it resolves RHS variable/subscript/dimension references given the context of the LHS variable instance.  (The same steps are used on the code gen side in the next item.)

On the code gen side, I reimplemented the cVarIndex function.  This function was the other contributor to the bug reported in this issue, and suffered from similar issues to those noted in item (2).  I fixed the cVarIndex function so that it follows the same steps to resolve RHS variable/subscript/dimension references that was used in item (2).
(Both functions previously used a shared separatedVariableIndex function, but that one was not fully generalized to handle different combinations of subscripts; for example, it had a case for 2 LHS subscripts and 2 RHS subscripts, but wasn't generalized further.  With the changes in (2) and (3), we no longer depend on that function in most common cases.  There are only 3 remaining uses of separatedVariableIndex, and those could probably be rewritten as a later improvement.)

As part of fixing (3), I was able to simplify how marked dimensions (like in SUM(x[DimA!])) are handled in the code gen phase.

(Minor change.)  Also as part of fixing (3), I changed the order in which loop variables are emitted.  This doesn't really affect the way the generated code works, but makes it easier to inspect and understand the generated code.  Previously the loop variables would be emitted in the order that they are visited on the RHS of the equation, which means you would sometimes end up with:
for (let j = 0; ...) {
for (let k = 0; ...) {
for (let i = 0; ...) {
  _x[i][j][k] = ...

The loop variables are now emitted in the order that they appear on the LHS of the equation, which makes the generated code use a consistent order.  The above becomes:
for (let i = 0; ...) {
for (let j = 0; ...) {
for (let k = 0; ...) {
  _x[i][j][k] = ...


nncp - wait_for_status_success - fix log if no node selector

Short description:
More details:
What this PR does / why we need it:
Which issue(s) this PR fixes:
Special notes for reviewer:
Bug:

!verified

!verified


Allow usePolling option in chokidar to handle nfs mounts

Basically, I code to a local directory on Mac OS X that is exported/mounted into a Debian VM via NFS.  Right now, if I change a file in OS X, nothing is triggered to chokidar (and subsequently to onchange).  If I touch the file within the VM or edit it within the VM, it is triggered and passed through to onchange.
From what I can tell, onchange uses chokidar(https://github.com/paulmillr/chokidar) which uses watchify(https://github.com/substack/watchify) to actually watch the files.
There was an issue on watchify about watching files on an nfs mount:
Changes to files on NFS should be detected
Watchify and Chokidar have already fixed this problem (https://github.com/substack/watchify/issues/120) by enabling polling instead of using FSEvents.  Now I just need a way to pass this option into chokidar from onchange.
Is there a way to enable polling on chokidar through an option in onchange?

Watchify isn't related to chokidar, in fact, it uses chokidar. However, there's no option currently in onchange. You can use the environment variable specified in https://github.com/paulmillr/chokidar#performance until it does exist. I'd be happy to accept a PR that mirrors the CLI options added in watchify to here.

Thanks for the quick response.  I hadn't seen that env variable earlier.
I was able to get on change to work from what I originally had in package.json:
{   "watch": "onchange src/ -i -v -- npm test -s" }
changed to:
{   "watch": "CHOKIDAR_USEPOLLING=true onchange src/ -i -v -- npm test -s" }
It takes an extra few seconds to find the files (probably from the polling), but it's better than having to touch each file that changes.


[MacOS] Wrong executable architecture in package .._macosx_11_0_arm64

I discovered that the distribution package clang_tidy-<IP_ADDRESS>-py2.py3-none-macosx_11_0_arm64.whl falsely contains the x86_64 binary.
I extracted the downloaded wheel using unzip and used the file utility to examine the architecture.
file clang_tidy-<IP_ADDRESS>-py2.py3-none-macosx_11_0_arm64/clang_tidy/data/bin/clang-tidy shows Mach-O 64-bit executable x86_64 instead of Mach-O 64-bit executable arm64.
As I am explicitly not wanting to use the rosetta emulator on my MacOS M1 machine, I am not able to use clang-tidy for now.
I downgraded to using 15.0.2 which seems to properly install the arm64 binary.

The issue still appears in the latest clang_tidy-18.1.1-py2.py3-none-macosx_11_0_arm64.whl package where the packaged binary is still x86_64 instead of arm64 .
Unfortunately, on Apple Silicon machines, the rosetta2 frameworks kicks in silently and therefore you won't detect such an issue easily as it will just run the x86 binary on your arm64 without letting you know.

Trying to address this in https://github.com/ssciwr/clang-tidy-wheel/pull/74
Would be great if you could check the produced wheel from the manual build I triggered @marcelhuberfoo. Should be ready in a few hours.

Trying to address this in #74 Would be great if you could check the produced wheel from the manual build I triggered @marcelhuberfoo. Should be ready in a few hours.

You're potentially forcing me to upgrade to Sonoma (macos-14) now 🥲, up to now, I could still use Ventura (macos-13) without too much of a hassle 😄
Nevertheless, I learned how to make use of restricted dependencies.

Unfortunately, the build was still targeting x86_64 when looking to the logs as well as according to the wheel check which actually failed the build.
I played around a bit to find the proper options required to cross build, and managed to use the following cmake configuration command to successfully build an arm64/AArch64 binary:
cmake -S llvm -B XBLD -DLLVM_ENABLE_PROJECTS="clang;clang-tools-extra" \
-DCMAKE_OSX_DEPLOYMENT_TARGET:STRING=11.0 -DCMAKE_OSX_ARCHITECTURES:STRING=arm64 \
-DCMAKE_BUILD_TYPE:STRING=Release -DCMAKE_SYSTEM_NAME=Darwin \
-DCMAKE_INSTALL_PREFIX=$HOME/xbld -DLLVM_HOST_TRIPLE=arm64-apple-darwin22.6.0 \
-DLLVM_TARGETS_TO_BUILD=AArch64 -G Ninja -DHAVE_POSIX_REGEX=0 \
-DHAVE_STEADY_CLOCK=0 -DLLVM_ENABLE_ZSTD:STRING=OFF

A set of options was copied from the manual build job you referenced with additional options to direct cmake to actually cross compile.

-DCMAKE_SYSTEM_NAME=Darwin
-DLLVM_HOST_TRIPLE=arm64-apple-darwin22.6.0 # $(gcc -dumpmachine)
-DLLVM_TARGETS_TO_BUILD=AArch64 # probably the most important one
-DHAVE_POSIX_REGEX=0 # in order to suppress build warnings
-DHAVE_STEADY_CLOCK=0 # in order to suppress build waringns
-DLLVM_ENABLE_ZSTD:STRING=OFF # to not fail linking due to incorrect libzstd.dylib architecture

I hope this helps you figuring out the correct options to set for the build.
Thank you for your support.

Thanks for that @marcelhuberfoo !
I'll ping you when I got an actual artifact to try.

I played around a bit more and even found a configuration where you could reduce to one build job, producing a so called universal binary containing code for both architectures in the same file. This file is actually more or less double the size but at least executable out of the box on both architectures.
For this, you would need to change the following flags:

-DCMAKE_OSX_ARCHITECTURES:STRING="arm64;x86_64"
-DLLVM_TARGETS_TO_BUILD="AArch64;X86"

and you could leave out LLVM_HOST_TRIPLE as it is even not clear what it should be set to.

Might actually be much simpler in that we've hit this
The pre-installed 3.8 interpreter isn't actually native itself!
New build with the workaround in place is now running https://github.com/ssciwr/clang-tidy-wheel/actions/runs/9841436874/job/27168025877

Might actually be much simpler in that we've hit this The pre-installed 3.8 interpreter isn't actually native itself! New build with the workaround in place is now running https://github.com/ssciwr/clang-tidy-wheel/actions/runs/9841436874/job/27168025877

Thanks @renefritze, a proper arm64 binary was provided by the generated wheel 🎉
Seems we are not far away from having a proper build soon 😃

New wheels for tidy 18.1.8 should hit PyPi in a few hours


Fixing header generation

Hey @hughandersen I've taken the liberty to jump in and help solve the headers issue.
It seems that my original idea to do it by overloading the RestClient.get_headers wouldn't fit this case - thanks for trying to implement it this way anyway, you did a good job giving it a shot.
I've reverted back to decoupling the oauth functionality outside of the IbkrClient class. Now all these functions live in support/oauth.py and the header generation happens there internally too when we call req_live_session_token. OAuthMixin is now deprecated and can be removed.
This way we also don't pass any additional **kwargs to get, post or delete, and so these can be used as before in the request method. I think this should make the other IBKR endpoints function as before.
I've also implemented the base_url argument that allows us to specify the base_url=REQUEST_BASE_URL when calling the client.post in req_live_session_token. Your implementation was close, but it relied on reading self._use_oauth in RestClient which doesn't really have access to that variable, as it is only defined in its concrete implementation. Using base_url parameter mitigates this problem.
If you think this could work, merge it in and let me know how it goes 👍

Ohh it does? Let me revisit this then

Addressed here: https://github.com/hughandersen/ibind/pull/2


arm: nxp: mpu: Fix Coverity issue

Fixes a Coverity issue in the NXP MPU driver, as well as a second similar issue in the NXP and ARM MPU drivers found by inspection.
Neither of these issues are causing any actual runtime failures, and given we are so close to releasing 1.8, I suggest we do not include this in the release. I don't want any surprises like #261.

After 07e0a78, attempting to execute from RAM no longer triggers a MPU-caused bus fault on frdm_k64f, as can be seen from mpu_test run - you'll get a usage fault / invalid use of the EPSR instead of a bus fault.  Also my own tests of stack/heap/data execution all successfully execute code from those regions without causing any fault at all after this change; those test actual execution of code written to RAM. Looking at the MPU configuration before and after this change, the only  difference seems to be that previously region 0 was disabled via a direct write to RGD0_WORD2, causing the valid mask to also be cleared, whereas now you are configuring it through RGDAAC0 and therefore leaving it marked valid.  Otherwise, before and after the change, the region attributes seem to be identical (0x7c0). I would have thought that would be ok since you are clearing the non-debugger permissions, but for some reason it doesn't seem to be working AFAICS as long as the valid mask remains set.

FWIW, my tests are here:
https://github.com/stephensmalley/zephyr/commit/3d5b9dfaee61f5236d02e01962471711cf9edde0
Don't know if they would be useful to submit.  exec_stack for example before and after this change shows the difference in behavior caused by this change, although you can see it even with mpu_test; it just isn't as obvious (bus fault -> usage fault there versus a bus fault -> FAIL).

Thanks for catching this. It turns out that clearing certain bits in WORD2/RGDAAC0 actually enables access. Specifically, the MxSM register fields:
Bus Master 3 Supervisor Mode Access Control
Defines the access controls for bus master 3 in Supervisor mode.
00 r/w/x; read, write and execute allowed
01 r/x; read and execute allowed, but no write
10 r/w; read and write allowed, but no execute
11 Same as User mode defined in M3UM
I've got a fix I'm testing now.

@stephensmalley, please have a look at #484. I like your test and think it's worth submitting, perhaps merge the new functionality into the existing mpu_test.

Submitted as https://github.com/zephyrproject-rtos/zephyr/pull/493


Silencing expiration with support of external call/handler

Expected Behavior
This is support for #1814, or kind of idea for possible solution
I see potential in having possibility to define command to be executed when silencing is expired (when expire = ). Either directly in silencing definition or in handler-like approach.
One use case is to resolve all checks for given client when silencing expires. This will ensure that if something went wrong during silencing (maintenance) and has not been resolved till silencing expiration, it will be alarmed during next check cycle.
This generic feature request might be handy in many other situations.
Please see "Steps to Reproduce" for better understanding.
Current Behavior
Referring to use case above. When this happens now, handlers are not processing events created during silencing (as expected). Once silencing expires, ongoing issue stays unnoticed by ticketing system.
Please see "Steps to Reproduce" for better understanding.
Possible Solution
N/A
Steps to Reproduce (for bugs)

Have a check with result exit =0
Silence the check with expiration of 5 minutes
Make check to fail within 5 minutes, exit = 1|2
Handler will not handle result (as expected)
Silencing expires
Handler won't be triggered anytime further because failure keeps going for ever - means there is no change state

Expected steps/behaviour:

Have a check with result exit =0
Silence the check with expiration of 5 minutes
Make check to fail within 5 minutes, exit = 1|2
Handler will not handle result (as expected)
Silencing expires and it will execute custom script in back-end which resolve check result - it will make it green
Check goes through the next cycle (etc. every 60s) and makes the result orange/red again
Handler will be triggered because there is change state from green to red/orange

Context
This is manageable when silencing  is fully managed by custom automation - means no auto expire is used. When custom automation uses API to un-silence the client, it can easily run another API call to resolve check results and get expected solution.
The problem comes when silencing is used with auto expiration.
Your Environment

Sensu version used: 1.4
Operating System and version (e.g. Ubuntu 14.04): RHEL 7.4

If anything is not clear from description, just raise the hand and I can formulate it in other way.
I really think this might be interesting feature, also for other purposes.

@mcbsdEU it seems this is due to the handler(s) also using filtering (e.g. occurrences).
I can see an issue if an event is silenced by multiple silenced entries, when only one of them expires (it's still silenced).

@mcbsdEU could you please clarify the specific problem you would like to solve (formulate it in another way). Thank you!

Hi @portertech
If I simplify it as much as possible. I would like to run some back-end action once silencing expires automatically. If silencing is triggered and cleared by back-end itself it is not a problem to insert additional task at the time of clearing. In some cases, it is more efficient to just trigger silencing with automatic expiration - and for these use cases it would be handy to instruct silencing mechanism to run external command in time of expiration. Yes, event may be silenced by multiple entries, but this command would be consciously linked with exact silencing entry. So for instance, one time expiration would be set with standard parameters + expiration value + path to command (optional).  I think it would extend the almighty power of Sensu:) But of course, that is just my point of view...

Just to add, that tracking for silencing could be also alternate way for same approach. It would work in same way as tracking of results (exit codes) and it would be transparent to silencing overlap - means that result gives 0 when no silencing is applied and 1 when one or more silencing entries are active. If not this, it could at least bring additional interesting insight for analysis and tshooting purposes.


403 Forbidden response for "/" path with empty reason value(Reason: "")

I see in the logs, with verbose level 4, entries about 403 Forbidden response HTTP status code.
Most of the time they appear every 30 seconds at the same moment when HPAs are calling metrics API, but sometimes I see them twice in one second for the same IP.
I see these calls only for three particular nodes every time.

Could somebody please help me to understand the root cause of these 403 status codes?
Any thoughts about who can call metrics-server by root path?
And can it somehow prevent any modules HPA, Scheduler, etc from fetching metrics from metrcis-server?

Thank you in advance!
 GoVersion:"go1.10.3", Platform:"linux/amd64"}

metrics-server command and version:
image: registry/metrics-server-amd64:v0.3.1
command:
  - /metrics-server
  - --kubelet-insecure-tls
  - --client-ca-file=/path/to/ca.crt
  - --kubelet-preferred-address-types=InternalIP

it shouldn't prevent the HPA from doing anything.  It's unclear what's calling metrics-server from the root path.  What IP address is that?

@DirectXMan12 Thank you for the answer!
IP address is the IP address of  the master node. Process who is calling metrics-server from master node is the kube-apiserver.
user@master-node1 # netstat -ap | grep 43252
tcp        0      0 master-node1:43252   metrics-server-service-ip:https     ESTABLISHED 23377/kube-apiserve

I wonder if it's a health-check or something from the aggregator?

Yeah, it might be. But I believe that it does not relate to the metrics-server so I will close the ticket.
Thank you for your help!


Enchants appear to be searched as implicits

I was so hyped when i saw that nobody had this raised zombies enchant on the market until i went and opened in the browser that it looked up by [implicit], not by [enchant]

Will be continued here #68 Thanks for reporting!

Possible fixed with 0.5.0-alpha.0. Please report back. Thank you!


Allow setting kevent_flags on struct sigevent

Depends on https://github.com/rust-lang/libc/pull/2813
Blocks https://github.com/tokio-rs/tokio/issues/4728

Back when I originally defined struct sigevent, Rust could not represent C unions.  So I cheated and defined it as a struct, replacing the union field with what I thought would be its most important member.  But now I need to use a different union member.  So in the linked libc PR I defined sigevent the correct way, using unions.  This PR both fixes the field names and adds a backwards-compatible way to set the new field.
A search through every crate on crates.io shows that Nix was the only currently-maintained crate using the union-as-struct field.  So I think we can handle the backwards-compatibility issues in libc by merging the libc PR, then quickly releasing patch releases of Nix.

So I think we can handle the backwards-compatibility issues in libc by merging the libc PR, then quickly releasing patch releases of Nix.

This seems reasonable. A few procedural questions:

How far back to we want to patch?
I pulled the download numbers for each recent minor version over the last 14 days:

Version
Count

0.18
18143

0.19
40880

0.20
71998

0.21
21651

0.22
146464

0.23
274245

0.24
160180

IMO this supports patching back to 0.22, and only back to 0.20 by request.

Should we combine this with the existing plans for a 0.24.2 patch, or address this subsequently as a 0.24.3?

I've rebased.  But so far, the libc maintainers still haven't merged the PR there.  Trying to be both backwards-compatible AND Rust 1.13.0 compatible AND satisfy that project's style checker is very difficult.  If they refuse to merge it, I'm thinking about just copying the FFI definitions into Nix, so we won't be blocked anymore.  What do you think of that, @rtzoeller ?

Ok, I pushed a version that inlines the C structures into Nix.  But only for FreeBSD, because that's the only platform that really needs this change.

Still no word from upstream.  I'll merge this now.  Once the upstream PR merges, we can revert the 2nd commit.

Re-link the updated libc PR: https://github.com/rust-lang/libc/pull/3630


Add "raw note" functionality to Author's Notes script

This allows you to opt out of your note being put in brackets.

Looked inside scenario.zip file too and everything appears to be in order!
There's a minor typographical error in the comment of the shared.js change and I want to test the script behavior on input "/an -r ". Other than that, it looks good! You can update the comment @ioncorimenia or I can later. I don't think the PR needs to be held up over this.

I was thinking, perhaps typing only /an without any arguments should clear the author's note and show "Author's note disabled" in the status line (if you have display turned on)? It would provide a convenient way of temporarily disabling the script. If that's not a bad idea, I can send it as a separate pull request.

Everything looks good on my end! @ioncorimenia @CoomerDeveloper I'll be merging the PR soon

Alright, merged in @ioncorimenia thanks a bunch!
(Also thanks for fixing the typo I had left in the scripts :laughing:)


Kitematic - internet connectivity issue

Kitematic would open showing images available for download
connect ETIMEDOUT 52.54.x.x:443
Information about the Issue: Possible internet connectivity issue. How do I configure Kitematic, Docker to use proxy?

Are you behind a firewall or VPN?
See our wiki for possible solutions:
https://github.com/docker/kitematic/wiki/Common-Proxy-Issues-&-Fixes


Linting to include a warning that the process id is autogenerated

Problem you would like to solve
It's very easy to build and deploy your process without ever changing the process id. The problem with that is when a user then goes to use the API to access the process or looks into logs trying to find mentions of the process it's not in a very easy to read or differentiate the ID and requires to users to have to keep looking up the ID again.
Proposed solution
The modeling linting should warn users that the ID has been auto generated and they should make it easier to read.
Alternatives considered
We could also automatically change to the ID based on the first time that the model is renamed.
Additional context
No response

I believe web modeler changes this for the first process based on the file name. I think it would be easy to pick up a process with an auto-generated ID (in Camunda scope) and nudge a user to change it.


Backport "HBASE-28502 Cleanup old backup manifest logic (#5871)" to branch-3

In older versions of HBase's backup mechanism, a manifest was written per table being backed up. This was since refactored to one manifest per backup, but the manifest code was not updated. A concrete issue with the old code was that the manifest for full backups did not correctly list the tables included in the backup.
Reviewed-by: Ray Mattingly<EMAIL_ADDRESS>

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 14s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ branch-3 Compile Tests _

+1 :green_heart:
mvninstall
2m 59s
branch-3 passed

+1 :green_heart:
compile
0m 27s
branch-3 passed

+1 :green_heart:
checkstyle
0m 11s
branch-3 passed

+1 :green_heart:
spotless
0m 44s
branch has no errors when running spotless:check.

+1 :green_heart:
spotbugs
0m 31s
branch-3 passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
2m 45s
the patch passed

+1 :green_heart:
compile
0m 25s
the patch passed

+1 :green_heart:
javac
0m 25s
hbase-backup generated 0 new + 106 unchanged - 3 fixed = 106 total (was 109)

+1 :green_heart:
checkstyle
0m 11s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
hadoopcheck
4m 53s
Patch does not cause any errors with Hadoop 3.3.6.

+1 :green_heart:
spotless
0m 42s
patch has no errors when running spotless:check.

+1 :green_heart:
spotbugs
0m 38s
the patch passed

_ Other Tests _

+1 :green_heart:
asflicense
0m 11s
The patch does not generate ASF License warnings.

20m 57s

Subsystem
Report/Notes

Docker
ClientAPI=1.45 ServerAPI=1.45 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5900/1/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/5900

Optional Tests
dupname asflicense javac spotbugs hadoopcheck hbaseanti spotless checkstyle compile

uname
Linux 69fee50897e7 5.4.0-172-generic #190-Ubuntu SMP Fri Feb 2 23:24:22 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-3 / aa39ccfc61

Default Java
Eclipse Adoptium-11.0.17+8

Max. process+thread count
82 (vs. ulimit of 30000)

modules
C: hbase-backup U: hbase-backup

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5900/1/console

versions
git=2.34.1 maven=3.8.6 spotbugs=4.7.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 28s
Docker mode activated.

-0 :warning:
yetus
0m  3s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-3 Compile Tests _

+1 :green_heart:
mvninstall
3m  5s
branch-3 passed

+1 :green_heart:
compile
0m 16s
branch-3 passed

+1 :green_heart:
shadedjars
5m 30s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 14s
branch-3 passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
2m 49s
the patch passed

+1 :green_heart:
compile
0m 17s
the patch passed

+1 :green_heart:
javac
0m 18s
the patch passed

+1 :green_heart:
shadedjars
5m 31s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 11s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
9m 56s
hbase-backup in the patch passed.

29m 21s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5900/1/artifact/yetus-jdk17-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/5900

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux d77ad320e9b8 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-3 / aa39ccfc61

Default Java
Eclipse Adoptium-17.0.10+7

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5900/1/testReport/

Max. process+thread count
3703 (vs. ulimit of 30000)

modules
C: hbase-backup U: hbase-backup

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5900/1/console

versions
git=2.34.1 maven=3.8.6

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 26s
Docker mode activated.

-0 :warning:
yetus
0m  3s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-3 Compile Tests _

+1 :green_heart:
mvninstall
2m 45s
branch-3 passed

+1 :green_heart:
compile
0m 15s
branch-3 passed

+1 :green_heart:
shadedjars
5m 37s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 12s
branch-3 passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
2m 23s
the patch passed

+1 :green_heart:
compile
0m 15s
the patch passed

+1 :green_heart:
javac
0m 15s
the patch passed

+1 :green_heart:
shadedjars
5m 39s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 11s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
11m 10s
hbase-backup in the patch passed.

29m 54s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5900/1/artifact/yetus-jdk8-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/5900

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 4206aef92d60 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-3 / aa39ccfc61

Default Java
Temurin-1.8.0_352-b08

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5900/1/testReport/

Max. process+thread count
3575 (vs. ulimit of 30000)

modules
C: hbase-backup U: hbase-backup

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5900/1/console

versions
git=2.34.1 maven=3.8.6

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 29s
Docker mode activated.

-0 :warning:
yetus
0m  3s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-3 Compile Tests _

+1 :green_heart:
mvninstall
3m 18s
branch-3 passed

+1 :green_heart:
compile
0m 16s
branch-3 passed

+1 :green_heart:
shadedjars
5m 54s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 14s
branch-3 passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
2m 55s
the patch passed

+1 :green_heart:
compile
0m 16s
the patch passed

+1 :green_heart:
javac
0m 16s
the patch passed

+1 :green_heart:
shadedjars
5m 54s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 12s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
9m 51s
hbase-backup in the patch passed.

30m 23s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5900/1/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/5900

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 3bcf632e1db6 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-3 / aa39ccfc61

Default Java
Eclipse Adoptium-11.0.17+8

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5900/1/testReport/

Max. process+thread count
3416 (vs. ulimit of 30000)

modules
C: hbase-backup U: hbase-backup

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5900/1/console

versions
git=2.34.1 maven=3.8.6

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.


Breakpoints work with built-in lldb but are not getting hit when using custom lldb

OS: Darwin arm64 22.5.0 (macOS Ventura, M2)
VSCode version:  1.81.1
CodeLLDB version:  v1.9.2
Compiler:  Apple clang version 14.0.3 (clang-14<IP_ADDRESS>.1)
Debuggee:  Mach-O 64-bit executable arm64 (a trivial hello_world application in C)

CodeLLDB is working flawlessly when using provided LLDB against the following trivial hello_world C program:

lldb version 16.0.0-custom
  rust-enabled

but trying to debug exactly the same hello_world program with a custom lldb , breakpoints are not getting hit.

I'm using a custom LLDB:
version
lldb version 18.0.0git (https://github.com/llvm/llvm-project.git revision ba818c4019c550e1a413e1563a05b241b508defd)
  clang revision ba818c4019c550e1a413e1563a05b241b508defd
  llvm revision ba818c4019c550e1a413e1563a05b241b508defd

(I replaced the contents of bin and lib in $HOME/.vscode/extensions/vadimcn.vscode-lldb-1.9.2/lldb with my llvm-project/build/bin/ and build/lib/  folders)
I also tried to debug the same program via CLI with my custom lldb and it works as expected (breakpoints included):

With the hello world C application I turned ON the verbose logging in the extension settings, to no avail (there is no output, neither using built-in lldb nor using my custom lldb):

But when trying to debug another binary (an Ada program, that's why I built my own lldb, to support Ada debugging), the logs are shown. This is the log that I get when trying to debug a simple Ada program with my custom lldb (breakpoints are not getting hit... or looking at the logging file, it seems that I don't receive a breakpoint callback from lldb):
https://gist.github.com/juananpe/6fb8ef7f1a8931d972df8ae24aaf2ae0

Again, the same Ada program can be correctly debugged from CLI using my custom lldb:

I know that Ada is not supported, thus I wanted to replicate the same weird behavior using a trivial C program.
I built my own version of lldb using this recipe:
https://gist.github.com/juananpe/3dbf52bc5dcd1e28e7d14c461530bb6d
The bin and lib folders of my custom lldb are here: https://www.dropbox.com/scl/fi/qairf2wbnvfx9mcz8aqec/custom-lldb.tgz?rlkey=8pc6rfszxkx8g5tifwyf0jhc8&dl=0
Any help or hint about how to proceed or what else to test will be much appreciated.
I was wondering if you could share the recipe used for building the built-in rust-enabled lldb version 16.0.0
Thanks.

@vadimcn Thanks for your response.
I tried to display the list of breakpoints following your advice. Not sure where to stop the program, though. I selected Run / Start Debugging and then tried the break list command from the command input, obtaining the following:

In text format:
break list
Current breakpoints:
1: file = '/opt/adatutorial/small.adb', line = 12, exact_match = 0, locations = 1, resolved = 1, hit count = 1
  1.1: where = small`_ada_small + 66 at small.adb:12:24, address = 0x0000000100001172, resolved, hit count = 1

So, the breakpoint seems to get resolved (and hit)
I also included the "breakpointMode": "file" setting in launch.json.  But removing the "breakPointMode" line from the file AFAICT I got the same result ?:-|

I also get the message
error: Command requires a process, which is currently stopped.

whenever I try to use the v command:

It's weird because the debugger is running but the process has stopped...
What I don't really understand is why I should change any configuration when the debugger works perfectly with a program that already has the breakpoints set correctly. If all I do is swap the lldb binary (and lib/ folder) and restart VSCode, everything should still work the same, right? That's why I thought that my next step should be to rebuild LLDB using the exact recipe that you used for building the built-in rust-enabled lldb version 16.0.0-custom. If it works, I will apply my Ada patch to your lldb fork directly. If not, well, I'll have run out of ideas.
Thanks again for your time,

Not sure where to stop the program, though.

Try setting "stopOnEntry": true.   This should stop the program before the first instruction gets executed.
Alternatively, you could cause your program to send SIGSTOP to itself, or just intentionally cause a segfault; these will stop the process and allow you it inspect its state.

If all I do is swap the lldb binary (and lib/ folder) and restart VSCode, everything should still work the same, right?

Not necessarily.   You are adding your changes to top-of-the-tree LLDB.  There could have been changes between 16.0.0 and TOT, that broke CodeLLDB.  I guess you could try applying your changes on top of 16.x branch.

That's why I thought that my next step should be to rebuild LLDB using the exact recipe that you used for building the built-in rust-enabled lldb version 16.0.0-custom.

It is very unlikely that my build recipe impacts breakpoints functionality in any way.

These are static libs produced by the LLDB build.   CodeLLDB uses dynamic linking, so I bundle only the dylib.  Generally, a build directory of any project will contain lots of intermediate build artifacts, which aren't needed at runtime.   What you put in the installation package depends on use case.
If you do a default build of LLDB, it will depend on whatever version of Python you have installed on your machine.  Which is fine for local use, but since I want a "portable" package, I bundle a minimal Python runtime as well.


Rounding does not work as expected in report

I'm using
{{ future.total_net_energy_import | round: 1 | autoscale: 'MJ'}}

And expect to have only one figure behind the decimal but instead I get two:

This is because the query returns a value in MJ (e.g.<PHONE_NUMBER>570.8057). round: 1 rounds this to "1343332946570.8" then autoscale converts it to EJ ("1.34 EJ"). I'll see what I can do to give you more control over number formatting.
In the interim you can do this:
{{ future.total_net_energy_import | divided_by:<PHONE_NUMBER>000 | round: 1 | autoscale: 'EJ' }}


Fix embedded subwindow drag in single window mode

Fixes #47244
The problem was that it was using the position of the last dragged sub window. So, I added a new drag state SUB_WINDOW_DRAG_START. When the drag starts, the drag_from and drag_pos variables are set to the initial position of the sub window and the mouse.
https://user-images.githubusercontent.com/6378569/111965647-32250c80-8ab3-11eb-98f5-72acc3a04b77.mp4

Why it needs new enum SUB_WINDOW_DRAG_START ?
I just change only (on original)
gui.subwindow_drag_pos = sw.window->get_position();

to
gui.subwindow_drag_pos = gui.subwindow_focused->get_position();

It seems to work for me too.

Why it needs new enum SUB_WINDOW_DRAG_START ?
I just change only (on original)
gui.subwindow_drag_pos = sw.window->get_position();

to
gui.subwindow_drag_pos = gui.subwindow_focused->get_position();

It seems to work for me too.

Much cleaner! Didn't know I could get the the currently focused from window from gui. Updating PR with the change.

Could you squash the changes to a single commit? It appears your newer commit reverts some changes you did on a previous one.

This appears to have been superseded by #53419. Please comment if that's not the case.


Huge difference to regular darknet output

Hey there!
After compiling my custom tiny yolo v3 network for the edgetpu I´m able to run my network but the output is insanely different.
On my custom network there is only one class, anchors and input size remain the same so i don´t know where these issues might be coming from.
Edge Tpu output:

Desired output

Do you have any why this is happening and how to fix this?

I've been having the same issue too. I've seen a notable loss in accuracy with the conversion from darknet to keras and this may have been propagated onto the edge tpu model.

I am experiencing the same kind of issue (worse output after conversion). I don't know if it's the inference.py script or the converted model. I've also noticed that the boxes sometimes have negative coordinates.

I have the same problem, any solution?

Hi @ItsMeTheBee @Rariusz
I corrected mistakes of utils.py.(Issue #19)
I hope it helps you solve your problem.
Plus, please confirm that anchor.txt is loaded properly. (I think your bounding boxes are too small)

Maybe it has something to do with the missing representative dataset for int8 calibration? This repo for some reason just generates random data.
Compare:
https://github.com/guichristmann/edge-tpu-tiny-yolo/blob/master/keras_to_tflite_quant.py#L21
to
https://github.com/hunglc007/tensorflow-yolov4-tflite/blob/master/convert_tflite.py#L17
Unfortunately, I couldn't get this repository to work yet, so I can't confirm if this is a fix.

Because my inference also yields very bad results, I ran this through the quantization debugger.
Results include two very high RMSE / scale values, for functional_1/activation_5/Relu and functional_1/activation_7/Relu, which probably lead to this bad accuracy.
Full results can be found in the attached csv
@guichristmann can you please shine light on if the example gif of joker provided was performed with the edgetpu compiled version of the model? Additionally, could you please tell us what dataset you used as a representative dataset when converting to tflite?
debugger_results.csv


Adding beginner section

Intent of this page is to be able to link common resources to new users learning about AWS for the first time and generating a starting point for them.

LGTM 🛳

Flawless :shipit:


Drop bintutils

Fixes https://github.com/conda-forge/openblas-feedstock/issues/1
Tries to switch over to using the devtoolset-2 binutils ( 2.23.52 ). This should hopefully be new enough.
If not, we will need to stick with the binutils package until we can come up with something better in the docker container that obviates this need.
Also, goes ahead and bumps the build number as we are using a different version of binutils.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

Awesome! Well that went smoother than expected. Bye-bye binutils.


Max time limit

is there a way to set a site's max time limit.
like blocking facebook after 10 minutes of use.

No, there is no way to set this but I


Unable to pass options: spotify clientID and clientSecret

I have my secret and ID saved in a string, but upon passing it I get an error:

I have added the plugin like so:

It asks for "clientID" but you use "spotifyClientID", it also asks for a non-empty string but you pass the string constructor, please view the readme for example usage of initiating the plugin.

Oh that's weird. The variable apparently has to be explicitly called clientID and not spotifyClientID. That solved my issue at last


Getting error "Cannot find module 'webpack/lib/InitFragment'"

I'm trying to use craco to get my app to ignore my fixture data if there is a live API server running.  I've created the following craco.config.js file
const { when } = require('@craco/craco')
const IgnorePlugin = require('ignore-webpack-plugin')

module.exports = {
  webpack: {
    plugins: [
      ...when(
        process.env.REACT_APP_API_BASE,
        () => new IgnorePlugin({ requestRegex: /fixtures/ }),
        []
      )
    ]
  }
}

but when I run npm start I get the following error
UnhandledPromiseRejectionWarning: Error: Cannot find module 'webpack/lib/InitFragment'
Require stack:
- /Users/davesag/src/industrie/anzi/credible-ui/node_modules/ignore-webpack-plugin/ImportDependency.js
- /Users/davesag/src/industrie/anzi/credible-ui/node_modules/ignore-webpack-plugin/IgnoreAsyncImportsPlugin.js
- /Users/davesag/src/industrie/anzi/credible-ui/node_modules/ignore-webpack-plugin/index.js
- /Users/davesag/src/industrie/anzi/credible-ui/craco.config.js
-<EMAIL_ADDRESS>-<EMAIL_ADDRESS>
What am I doing wrong?

Noting that CRA internally uses<EMAIL_ADDRESS>I also tried simply installing that as a dev dependency but I get the same result.  Looking into node_modules/webpack/lib/ there is no InitFragment. But what I did notice is that there is an IgnorePlugin in node_modules/webpack/lib/ so I've updated my config to
/* eslint-disable import/no-extraneous-dependencies */
require('dotenv').config()
const { when } = require('@craco/craco')
const { IgnorePlugin } = require('webpack')

module.exports = {
  webpack: {
    plugins: [...when(process.env.REACT_APP_API_BASE, () => [new IgnorePlugin(/fixtures/)], [])]
  }
}

it appears to work.


Require contact information for MatterFi site:

Email, Address, Social Medias, Phone Numbers.

email<EMAIL_ADDRESS>points to a Tim, Mehow, Robert group
Address: 30 N Gould St, Ste R
Sheridan , WY 82801
Social Media:
Telegram:
t.me/matterfi
Discord:
discord.gg/RVGfCbZNmG
(FYI a Discord.ME/MatterFi can be made later)
Instagram:
instagram.com/matterfinance
(MatterFi is taken by a black film group “matter Films”
Facebook:
www.facebook.com/MatterFi-108207714429114/s
(URL shortening is not setup yet)
Twitter:
twitter.com/FiMatter (this URL will change after further verification)
LinkedIn:
linkedin.com/company/matterfi
Signal:
Not sure if I can help you here… but I want to!
Phone Numbers:
I need to setup GrassHopper (https://grasshopper.com/) number later, for now if you'll leave it blank I'll add a reminder to follow up

I'm adding Mehow to this GitHub Org, I'll tag him in this project. @wigggles should you choose the next step is to populate the above information

Can add the company social media links into the Home page bottom "Contact us" section next to the Form.

To do so we'll need to "hydrate" them with relevant information and bring them up to the same standards as the website. I can backlog this if you see it as valuable? I just don't see it as valuable right now.

I've moved it to ice box and added a personal reminder to follow up in two months, I'll assign it to my self so you feel no more pressure

I think the color hover icons that jekyll has should take care of most of that. Its got icons for most media already. I don't think it has:
Discord or
Telegram or
Linkedin (which also could be used with the Teams bios later)
But there are icons for Twitter, Instagram, Facebook already there.

ok updated font awesome, was required for social media icons discord and telegram. Site has links to all provided media.

We should make sure that these media accounts share a link to the web site to help with SEO

Media accounts are linked on home page.


Feature/base paths

Purpose
Based on the base path and uri listed in the endpoint's SwaggerGen annotation, there will be a folder(s) created for the endpoint and the yaml file, that is valid swagger, will be there.
In addition, there is now a new ruby script called generate_docs that creates the html files from the yaml files and places them in swaggen_html if the yaml comes from swaggen, or sample-project_html if the yaml comes from sample-project
Created a new class called SwaggerEndpoint that contains the map of request methods to endpoints, but created to potentially contain more.
Example folder structure:

Sample yaml file from changes:

Sample redoc file from changes:

I've had a chance to briefly look this over. There is a lot going on here, so I would like a chance to do a more thorough review tonight. Can e hold off on merging this until then?


Demo app isn't working

Upon opening the Demo app, many errors show up within XCode after attempting to build. Is anyone else facing these issues?

Actually this has been resolved -- both the demo app works and some of the boilerplate code that we tried adopting was not working, but we got it working.


Release/2.3.0

Changes

closes #792 (Use new web3modal api)
fix: Respect image overrides for explorer wallet id's
add: --w3m-wallet-icon-large-border-radius theme variable
add: --w3m-wallet-icon-small-border-radius theme variable
fix: flickering network icon within network button component in safari
add: error state / shake animation feedback to connector "loading" screens
add: connector loading screen in iOS to display app store links and useful info
add: new network switching loading screen
add: WalletConnect connector now pre-heats pairing and caches it up to 3 minutes. This reduces loading views and un-necesary websocket requests. Cache is invalidated if: connection is requested for expired pairing (3min), user has connected, there was connection error
add: closes #958 closes #865 (add tokenContracts option to define custom erc-20 token for account view balance, per chain)
fix: closes #946 (Add small vertical padding in low vertical space screen mode)
remove: closes #892 closes #879 closes #820 Hardcoded injected wallet presets in favour of cloud data and add info notices about common pitfalls
add: dynamic wallet "connection" view that adopts to platform, installed wallets and listing data
add: closes #909 if injected wallet is detected on a mobile device, use it once user clicks on connect button
fix: closes #978 by phanthai12 (inset css property not working in safari 13)

Breaking Changes

ios: closes #930 closes #937 (To improve stability around mobile linking, deeplinks are now prioritised over universal links, this requires users to interact with native prompt when performing connection or transaction, but results in much more reliable linking between dapps and mobile)
closes #956 - Modal no longer sets defaultChain to mainnet or first chain defined in wagmi config. So when connecting user's active wallet chain will be used. You can set defaultChain to get back previous behaviour or ask user to select your dapp supported chain before connection using enableNetworkView option.

@Trynight unlikely, but if you are feeling adventurous you can try canary version on npm for 2.3.0 (might need to do some work still to migrate to full 2.3.0 once it is out)

@Trynight ty for testing, I'm planning to address android specifics next week, likely missing something there as I mostly tested with web and ios so far.

@Trynight Let's continue discussion here. First of all there is new canary you can try 2.3.0-6a0bdcf
However there are no android specific changes here. I tested agains our lab deployment here https://07a3dee0.web3modal-dev.pages.dev and your own dapp https://dee-lance-2-3-0.vercel.app/en
And it seems that there is indeed an issue on dee-lance, wallet doesn't prompt user to connect, which means that dap doesn't send pairing request. As this is working in deployment above, I think it is something related to specific implementation on dee-lance.
My best suggestion is to look at implementation of custom button on this pr and try to replicate it https://github.com/WalletConnect/web3modal/pull/954/files#diff-bde49ed11d10c5e6c1d960944fc796117a3fa690d98a1d5a38563af6f178f4daR62-R66

@Trynight have you tried over https? Most wallets will block requests from non secure http sources

@Trynight noup, that should be fine, as you are not the owner of wallets that you are connecting with. Atm it is a bit unclear as to why things are failing. Are you proposing valid chains that trust wallet supports?

@Trynight I'm afraid there is no way to hook into trust wallet logs. When you mention "bnative browser" what exactly do you mean? I assume it's something like chrome on android?


New Docs : Write about Gemini

Description : Under the Docs section create a markdown file which is about the blog about Gemini.
It should contain but not limited to:

[ ] What is Gemini
[ ] Background
[ ] Performance
[ ] Capabilities
[ ] Safety measures
[ ] Conclusion

Note: Write it in markdown format and try to add some pictures.
Best of Luck and Happy Coding.
Sandip

Assign me under Aperture'24

Please assign me this issue , I'm intrested in fixing this issue

@Sneha123-zudo you are assigned to this issue. Best of Luck and Happy Coding.


Update mermaid to use mindmap

NOTE: Before you start, the following should be completed.

Read Wiki to understand the usage and the correct effect of functional design.
Make sure no similar issue(including closed ones) exists.
Try to find the answer on Jekyll Forum and StackOverflow.

Description
Hello, i wanted to use the mermaid mindmap feature so i changed:
my _data/assets/cross_origin.yml from:
mermaid:   js<EMAIL_ADDRESS>to this in my local file:
mermaid:   js<EMAIL_ADDRESS>and my _includes/mermaid.html from:
<script src="{{ site.data.assets[origin].mermaid.js | relative_url }}"></script>
to this in my local file:
<script type="module">
    import mermaid from '{{ site.data.assets[origin].mermaid.js | relative_url }}';
</script>

Is it the right way to do? Should i expect some bugs or other?
btw : Awesome template 🥇

Hi @bastien-w, Starting from version 10.x, Mermaid no longer supports usage through CJS, which is not very friendly for web page app. Therefore, I only upgraded it to the latest version 9.4 in 25ec7649cd80b788ecfcc51e7c8a4bc9e8150069.
See also: https://github.com/mermaid-js/mermaid/releases/tag/v10.0.0


Enhance Mod Configuration

PR content:

[ ] Spell Configs
[ ] Ritual Configs
[ ] Miscellanous Configs

Fix #98

For the record, I am 100% for the ability to configure spell damage:
a) It was requested specifically by the author of a modpack who wanted to be able to have it fit in with other mods which inflated health and damage values of mobs. Otherwise including the mod was pointless as the spells did no damage.
b) If we're going to hand-hold and worry about players editing the configuration files and messing up their progression, we may also have to worry about how to prevent people from enabling cheats and going into creative mode.
90% of people never look at configuration files. This change will affect nobody but the people it was intended to affect, and any concerns about hand-holding people should be discarded as they are irrelevant.


Link is unclickable

Description
One can't click on the link in the footnote
(Optional:) Please add any files, screenshots, or other information here.
No response
(Required) What is this issue most closely related to? Select one.
Other
Internal issue ID
a4a12294-cbf5-4b76-9d8e-a6c0e803c492
Paper URL
https://arxiv.org/html/2407.04503v1
Browser
Chrome/<IP_ADDRESS>
Device Type
Desktop

Thank you for the report!
This threw me for a loop, until I realized they are not links in the source. If you download the PDF and open it with a classic PDF viewer, they aren't clickable there either.
In a browser PDF preview we are benefiting from an added-value service that automatically enhances such cases into links. That could be an extension for the arXiv HTML article viewer,  will mark as a feature idea.


AsyncStorage implementation issue.

will it be possible to provide an example for AsyncStorage when I tried it says "Possible Unhandled Promise Rejection (id: 0):
TypeError: Cannot read property 'hasOwnProperty' of null"

Same here, any solution?

You don't need to use this library to get simple persistence with Recoil and React Native. Just adapt the localForage example from the Recoil documentation, and you get (with TypeScript):
import {atom, AtomEffect, DefaultValue} from "recoil";

function persistAtom<T>(key: string): AtomEffect<T> {
  return ({setSelf, onSet}) => {
    setSelf(AsyncStorage.getItem(key).then(savedValue =>
      savedValue != null
        ? JSON.parse(savedValue)
        : new DefaultValue() // Abort initialization if no value was stored
    ));

    // Subscribe to state changes and persist them to localForage
    onSet((newValue, _, isReset) => {
      isReset
        ? AsyncStorage.removeItem(key)
        : AsyncStorage.setItem(key, JSON.stringify(newValue));
    });
  };
}

Then wrap your RecoilRoot with a Suspense component:
      <React.Suspense fallback={<View><Text>Loading</Text></View>}>
        <RecoilRoot>
          {/* your app components */}
        </RecoilRoot>
      </React.Suspense>

Despite the typings, it doesn't seem to support async getItem or setItem.


[dattri.func.ihvp] Implement ihvp_at_x_ekfac

Description

1. Motivation and Context

This PR is the same as the closed one #79.
To complete the proposal in the issue #76.
2. Summary of the change

The implementation is basically the same as originally designed.
Specifically,

Added ihvp_at_x_ekfac and its helper functions to dattri.func.ihvp.
Added wrapper function manual and class MLPCache to dattri.func.ihvp.
Slightly modified dattri.func.ihvp._check_input_size to support the EK-FAC method.

3. What tests have been added/updated for the change?

[x] Unit test: Typically, this should be included if you implemented a new function/fixed a bug.

Seems like test_ihvp_datainf_nn  is a bit shaky.

Seems like test_ihvp_datainf_nn  is a bit shaky.

Could lower the threshold to 0.8.

Seems like test_ihvp_datainf_nn  is a bit shaky.

Could lower the threshold to 0.8.

Should I do it here or in a separate PR?

Seems like test_ihvp_datainf_nn  is a bit shaky.

Could lower the threshold to 0.8.

Should I do it here or in a separate PR?

You could just do it here. This shaky test is going to block other PRs if we merge this PR without lowering the threshold.


#8939 Add proper function for bulk-fetching user profile objects by ID within a realm

Fixes #8939

Merged, thanks @novokrest!  I also added c06565d90994107bfe2abb911fd95d027dc82d9f on top.


is_incremental always returns false for BigQuery

UPDATE: added step 4 to reproduction recipe
Describe the bug
The is_incremental() macro always returns false when the target is BigQuery, effectively disabling the incremental build feature.
Steps To Reproduce

Create a fresh DBT project with dbt init
Configure the profile to use BigQuery
Change the "my_first_dbt_model.sql" file to this:

{{ config(materialized='incremental') }}
select 1 as id
{% if is_incremental() %}
THIS SHOULD CAUSE AN ERROR
{% endif %}

execute "dbt run" to initially create the table
execute "dbt run" again
=> no error is displayed (bug)
execute "dbt run --bypass-cache"
=> error is displayed (expected behaviour)

Expected behavior
An error message should be displayed when calling "dbt run" because the SQL inside the is_incremental condition is invalid.
When running "dbt run --bypass-cache" the result is as expected.
Additional information
I did a little debugging and verified that is_incremental is indeed returning false. The cause is that adapter.get_relation apparently returns None. Since the problem vanishes when --bypass-cache is specified, I suspect that the problem is caused by a bug in the relation cache.
System information
Which database are you using dbt with?

[ ] postgres
[ ] redshift
[X ] bigquery
[ ] snowflake
[ ] other (specify: ____________)

The output of dbt --version:
installed version: 0.14.2
   latest version: 0.14.2

Up to date!

The operating system you're using:
macOS Mojave
The output of python --version:
Python 3.7.4

hey @haukeduden - I think this is the normal and expected behavior of the is_incremental() macro -- this macro should return True when:

a model is materialized as incremental AND
the --full-refresh flag was not provided AND
the target table exists in the database

I think the issue you're seeing is that for the first run of a model, the destination table does not yet exist in the database.
The is_incremental() block is frequently useful for self-queries, eg.
-- models/my_model.sql
select *
from source_table
{% if is_incremental() %}
  where event_time > (select max(event_time) from {{ this }})
{% endif %}

Here, {{ this }} refers to the model itself, eg analytics.my_model. The is_incremental() logic prevents this self-query from running if analytics.my_model does not yet exist in the database, that is: when adapter.get_relation returns None.
It's certainly possible that there is some other cache-related bug at play here, but I'm not sure that the example code you sent through exercises that bug if it does exist. I'm going to close this issue out, but please feel free to follow up if I have the wrong idea - happy to discuss this further.

Hi Drewbanin,
thank you for the quick response. I realize now that my reproduction recipe was oversimplified. I have modified the original problem description and added an additional run step.
The problem occurs even if the target table already exists, so it would seem that this is an actual bug.

@haukeduden thanks for the additional info. When I try to reproduce this, I do see dbt failing on the second invocation of dbt run.

If this is a cache-related issue, then it probably has something to do with the state of your particular BQ project. Does your project name or dataset name contain any interesting/special characters? When we've seen caching issues like this in the past, they usually had to do with case-sensitive comparisons in the cache lookup. Any chance your dataset is named something like MydbtProject or something like that?

Yes, the dataset has some camel-casing. It is called "AshData".

I just tried again with a lower-case dataset name. Then I also get the expected error message on the second call. So it seems that this might indeed be called by upper characters in the original dataset name.

Thanks @haukeduden - that's super helpful. I appreciate you taking the time to report this one -- we'll take a look at fixing it!


Getter function to work with defaultAttrs of computed property type

Changes

getAttr() of default-attrs mixin to use Ember's get to fetch attribute off of defaultAttrs object.

Why
I've made a screenshot of the error stacktrace to show why this PR got submitted :1st_place_medal:.

While using paper-chips from ember-paper which depends on virtual-each every time I typed in something to the input, I've had such error logged to console.
After changing the getter to use  Ember's get I've got rid of this error.
But the real Why is that, the folks @ember-paper declare defaultAttrs as computed property, and so the errors were raised.
Using computed without dependent keys is pretty common after all, so It'd be nice if it was computedProperty compatible.

0.6.2, thanks @BobrImperator !


Cannot seem to find WFC2DGenerator node

Hi, as the title mentions, I am trying to follow the how-to: https://github.com/AlexeyBond/godot-constraint-solving#how-to-use but I can't seem to get the WFC2DGenerator node to appear in my node search window. I'm not sure if I need to do something more after installing the plugin or not.
Any advice?

Hi. In order for a plugin to work, it should be enabled in project settings: https://docs.godotengine.org/en/stable/tutorials/plugins/editor/installing_plugins.html#enabling-a-plugin. Maybe that's the problem.

I see, you are definitely right. I thought that plugins may get enabled by default. I was wrong, that was it, thank you for the quick help!


Modal content

Branch improves display of card titles and attempts conditional rendering of log in/out options, but this isn't working (yet).

** NB: This is an ironically-named branch, as it does not contain any modal content. (It was intended to, but we ended up focusing on other things).
Modal content will thus be added in a different branch.


Update PHPCS in AuthController

@joshcanhelp There are a fair few changes in this to bring it up to code standards. The next part of this would be to make sure it meets Drupal best practices so removing the static methods of Drupal::logger and Drupal::service and utilise dependency injection which i'll do in a subsequent PR.

Hey @joshcanhelp ,
Sorry for the slow progress on this one, just reverted the changes and will start the process of fixing these changes on a seperate PR.


Native script  select type  is not there

hi
i am getting below error in android
JS: ERROR Error: [Formly Error] There is no type by the name of "select"
JS: ERROR CONTEXT {

could you please ensure that you're using the 5.0.0-beta.21 version of @ngx-formly/nativescript ?


[ Unit Test ] remove mse loss layer  in makeCompiledGraph @open sesame 05/04 10:00

This patch remove the mse loss layer in makeCompiledGraph
Self evaluation:

Build test:	 [X]Passed [ ]Failed [ ]Skipped
Run test:	 [X]Passed [ ]Failed [ ]Skipped

Signed-off-by: jijoong.moon<EMAIL_ADDRESS>

:memo: TAOS-CI Version: 1.5.20200925. Thank you for submitting PR #1895. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://ci.nnstreamer.ai/.

:octocat: cibot: @jijoongmoon, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://ci.nnstreamer.ai/nntrainer/ci/repo-workers/pr-checker/1895-202205022052520.89602398872375-291dd3890dd72c5d4d69a2ce4ea583e0897b088c/.

:octocat: cibot: @jijoongmoon, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://ci.nnstreamer.ai/nntrainer/ci/repo-workers/pr-checker/1895-202205022219160.66770696640015-9aa624cbd525799ea124267f2ac44ca55ea9a98e/.

:octocat: cibot: @jijoongmoon, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://ci.nnstreamer.ai/nntrainer/ci/repo-workers/pr-checker/1895-202205041000270.67786288261414-9aa624cbd525799ea124267f2ac44ca55ea9a98e/.


no difference between convit_base and convit_base_patch models

The code for the models convit_base and convit_base_patch appears to be exactly the same. I'm guessing either one of them is redundant or there's an error somewhere?

convit_base takes the model from VisionTransformerbase class and convit_base_patch from VisionTransformer class. The only difference between these two classes is the presence of a convolutional block in the patch named model.