Need mechanism to inject targets from package before common targets

Currently, a package can have logic that runs after common props or after common targets, but we also need to hook in after the users settings but before common targets.
For now, I'm setting CustomBeforeMicrosoftCommonTargets, but that's a hack that hijacks something that should belong to the user. We need to design a way for nuget packages to do this without stepping on anyone else.
cc @jeffkl

The SDK no longer uses a hack because it is no longer imported as a nuget package and can control when common targets are imported as it wishes. But the issue still exists for any other package extending the build via nuget and needing to run before common targets.

This is still not early enough for some things like https://github.com/onovotny/MSBuildSdkExtras. I tried using CustomBeforeMicrosoftCommonTargets, but it was still too late as some of the SDK's targets already calculated things like the define's and AssemblyInfo data.
We need an extensibility point that gets called before any SDK targets.

@nguerrera is @dasMulli's suggestion enough for you?

Yes, that's great. TIL.

This would still track adding the property and importing it, so I think we should triage out of discussion.


initializing newInit as an object

@enrique-ramirez I tried this in another browser, and got an error related to not initializing an object correctly. I fixed that here
Mind giving this one a shot? Still not 100% sure if this does the trick to you. First time using Object.assign.

Hi @evert!
While this is indeed a bug (Object.assign does break if you pass undefined as the first argument), it unfortunately doesn't fix my issue. I'm not really sure where the trouble lies, but I'll try and check it out over the weekend, see if I can find the root issue.
Thank you for the fix and sorry for the troubles!


Remove the IMAGE_REPO env var from all the temlates

cluster-api project wants to stop using the k8s.gcr.io repository, as it's too expensive. After checking in other cluster API project, it seems that this value is no longer in the template.
This PR removes all the usage in IMAGE_REPO variable; for that, the PR also upgrade the clusterctl in the kubevirtci script, to v1.2.4
Signed-off-by: Nahshon Unna-Tsameret<EMAIL_ADDRESS>
What this PR does / why we need it:
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
Special notes for your reviewer:
Release notes:

None

/ok-to-test

another podman issue. this time with pushing the locally built capk to the internal registry
docker push <IP_ADDRESS>:33847/capk-manager-amd64:dev
Getting image source signatures
Copying blob sha256:0b1d42bd476085ada536f7e14b02dab4d4c4172f3131bea3ba213d67c7efbd07
Copying blob sha256:9fce6bd02a21068901a96271d3160c2ce9da9c83c152eeb22312f65226da108c
Error: trying to reuse blob sha256:9fce6bd02a21068901a96271d3160c2ce9da9c83c152eeb22312f65226da108c at destination: pinging container registry <IP_ADDRESS>:33847: Get "https://<IP_ADDRESS>:33847/v2/": http: server gave HTTP response to HTTPS client


I would like to ask, how can I add a new language like Vietnamese. Thank you

I would like to ask, how can I add a new language like Vietnamese. Thank you

thank you for your help, you let me inquire further. Does the tool have a
character limit when using clone voice? Thank you ...
Vào Th 3, 22 thg 10, 2024 vào lúc 19:44 dosubot[bot] <
@.***> đã viết:

Hey @KalvinThien https://github.com/KalvinThien! I'm here to help you
out with any bugs, questions, or contributions you have. Let's tackle this
together!
To add a new language like Vietnamese to OpenVoice, you need to make
changes in the openvoice/api.py file. Specifically, you should add an
entry for Vietnamese in the language_marks dictionary within the
BaseSpeakerTTS class:
class BaseSpeakerTTS(OpenVoiceBaseClass):
language_marks = {
"english": "EN",
"chinese": "ZH",
"vietnamese": "VI",  # Add this line
}
This change assigns a language mark "VI" for Vietnamese, which can then be
used in the tts method to process Vietnamese text [1]
https://github.com/myshell-ai/OpenVoice/blob/main/openvoice/api.py.
To continue talking to Dosu https://dosu.dev, mention @dosu
https://github.com/dosu.
—
Reply to this email directly, view it on GitHub
https://github.com/myshell-ai/OpenVoice/issues/324#issuecomment-2429184393,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A4X27SORCU2DTASGE5YGIVTZ4ZCDHAVCNFSM6AAAAABQMNE4QCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRZGE4DIMZZGM
.
You are receiving this because you were mentioned.Message ID:
@.***>

bạn có thể cho tôi ví dụ dùng clone voice với text tiếng việt không ?
Tôi muốn test thử v2

I tried, and got the input audio to short message, I used the default example file example_reference.mp3

Hey @KalvinThien! I'm here to help you out with any bugs, questions, or contributions you have. Let's tackle this together!
To add a new language like Vietnamese to OpenVoice, you need to make changes in the openvoice/api.py file. Specifically, you should add an entry for Vietnamese in the language_marks dictionary within the BaseSpeakerTTS class:
class BaseSpeakerTTS(OpenVoiceBaseClass):
    language_marks = {
        "english": "EN",
        "chinese": "ZH",
        "vietnamese": "VI",  # Add this line
    }

This change assigns a language mark "VI" for Vietnamese, which can then be used in the tts method to process Vietnamese text [1].
To continue talking to Dosu, mention @dosu.


Problem on Login Page

Task :

[ ] Login Functionality (Can't use the current account to login)
[ ] Social media like Google and Facebook authentication (Can't use them yet)
[x] Error on deleting letter
[x] Size on google and facebook is overflow and overlap

Fixes overlapping button in #46


Unable to load refs when parsing with project in jar

I have multiple openapi files in my resources folder that reference each other. Attempting to parse them works just fine when running the code with my IDE, but as soon as I jar the project and run the jar, openapi4j is unable to process any refs. I am loading the swagger file like this:
URL url = Thread.currentThread().getContextClassLoader().getResource(filePath);
openAPI = new OpenApi3Parser().parse(url, false);

and my swagger file looks like this:
{
  "openapi" : "3.0.0",
  "info" : {
    "title" : "My Service",
    "version" : "1.0.0"
  },
  "paths" : {
    "/endpoint" : { "$ref" :  "swagger2.json#/paths/get_endpoint" },
  }
}

To Reproduce

Reference another swagger file from your root swagger file in your project resources
Parse the root file and confirm it works correctly
Create a jar of your project, including resources
Run the jar

Expected behavior
The refs should evaluate, even though they are in a jar

Hi and welcome,
Thanks for the report, I can confirm the issue.
This fails because of URI class with resolve() method.
Time to change those URI to URL.

Are you able to validate this in latest 0.9-SNAPSHOT?

I was able to validate this works fine in the 0.9 snapshot. Thank you! Any estimate on when that could be released?

Thank you, release will be pushed tomorrow or early next week.


Add locale test

Should prevent #59 from happening again.

Not a valid test anymore now that locale can be variable.


No background and no correct placement of the icons on M1 Macbook Air

I have a macOS app which compiles both on Apple Silicon macs and Intel macs fine. On my Intel mac, create-dmg generates the .dmg file correctly, placing the icons in the correct positions and setting the brackground. On the MacBook however, the same build script just generates a plain .dmg without any styling.

Device name:     /dev/disk8
Searching for mounted interstitial disk image using /dev/disk8s...
Mount dir:       /Volumes/dmg.byUneD
Copying background file 'Resources/nostrum_color.png'...
Making link to Applications dir...
/Volumes/dmg.byUneD
Copying volume icon file 'Resources/horus_volume.icns'...
Running AppleScript to make Finder stuff pretty: /usr/bin/osascript "/var/folders/00/0j9365pd59xbvyf92bpbyqdr0000gn/T/createdmg.tmp.XXXXXXXXXX.HTAmB6ncaD" "dmg.byUneD"
waited 1 seconds for .DS_STORE to be created.
Done running the AppleScript...
Fixing permissions...
Done fixing permissions
Skipping blessing on sandbox
Deleting .fseventsd
Unmounting disk image...
"disk8" ejected.
Compressing disk image...
Preparando creación de imagen…
Leyendo Protective Master Boot Record (MBR: 0)…
   (CRC32 $AF32CF39: Protective Master Boot Record (MBR: 0))
Leyendo GPT Header (Primary GPT Header: 1)…
   (CRC32 $20A8E177: GPT Header (Primary GPT Header: 1))
Leyendo GPT Partition Data (Primary GPT Table: 2)…
   (CRC32 $423F46D0: GPT Partition Data (Primary GPT Table: 2))
Leyendo  (Apple_Free: 3)…
   (CRC32 $00000000:  (Apple_Free: 3))
Leyendo disk image (Apple_HFS: 4)…
.............................................................................................................................................................................
   (CRC32 $ED7226DA: disk image (Apple_HFS: 4))
Leyendo  (Apple_Free: 5)…
.............................................................................................................................................................................
   (CRC32 $00000000:  (Apple_Free: 5))
Leyendo GPT Partition Data (Backup GPT Table: 6)…
.............................................................................................................................................................................
   (CRC32 $423F46D0: GPT Partition Data (Backup GPT Table: 6))
Leyendo GPT Header (Backup GPT Header: 7)…
.............................................................................................................................................................................
   (CRC32 $B7D82AD8: GPT Header (Backup GPT Header: 7))
Añadiendo recursos…
.............................................................................................................................................................................
Tiempo transcurrido:  7.540s
Tamaño del archivo: 62065743 bytes, Suma: CRC32 $B02CAD45
Sectores procesados: 401482, 342292 comprimido
Velocidad: 22.2M B/s
Ahorro: 69.8 %
created: /Users/cdominguez/Developer/horus/dist/Horus-0.1-arm64.dmg
hdiutil does not support internet-enable. Note it was removed in macOS 10.15.

Here a screenshot on M1:

And on the Intel machine:

Using latest v1.2.1 and getting the same issue with no background image on Monterey 12.7.4 - positioning of icons is OK as long as --skip-jenkins is not used and the applescript allowed to run.  Tried some earlier versions  but still the same.
When the completed DMG window is opened I can reveal the .background folder and it contains the background image OK (in my case I used background.png sized to the same size as the window dimensions) so not sure why it is not displaying in the window.
I am running create-dmg within bash using ./create-dmg ..... and everything else appears to build/function OK.

Possibly related to https://github.com/create-dmg/create-dmg/pull/72 ?

@Blatman Did you ever fix that issue, I believe im facing the same error now on macOS 14.5

No - been a while since I've been doing dev but the last effort with Tauri I tried using DMG Canvas via child process. There has been an update within Tauri which allows more customisation of DMG's natively (except for the DMG volume icon) however for me (I don't do production line builds) DMG Canvas provides all required customisation options. It is probably easier to use DMG Canvas as normal standalone app using the executable binaries from the Tauri build process. Note: DMG Canvas is actually a paid for app (not a lot).

@nilekell - pass, it has been a while since I was messing around with the DMG stuff and as I remember I was happy enough just to trigger the GUI from the CLI - also waiting for a stable V2 and V2 docs - it is too much overhead trying to keep abreast of all the alphas/betas/etc especially as I am not much chop with the Rust/Cargo stuff.


Need an Upload from Gallery button for Create with Keeper flow

Beneath the camera window, we need the Upload from Gallery button like we have in Keeper.

Resolved,

Completed


Missing spelling in the command in the Japanese page.

Code of Conduct

[X] I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?
https://docs.github.com/ja/repositories/creating-and-managing-repositories/troubleshooting-cloning-errors
What part(s) of the article would you like to see updated?
missing command update
git remot -v => git remote -v

Additional information
I made a pull request by mistake.(https://github.com/github/docs/pull/18709)
But it seems that pull requests for translated pages are not accepted.
So I created  issue

/assign

Thanks for opening this pull request! Unfortunately, we are not able to accept pull requests for translated content. Our translation process involves an integration with an external service at crowdin.com, where all translation activity happens. We hope to eventually open up the translation process to the open-source community, but we're not there yet.
See https://github.com/github/docs/blob/main/CONTRIBUTING.md#earth_asia-translations for more details.
I've opened an internal issue with our translators 💛


Persian(Farsi) Translation

I have been working with this bot for almost 1 year, and I am very satisfied with it. I saw the possibility and permission to add translations of other languages to the bot, so I added my own language if there is no problem.

Other languages are always appreciated. Im sure Biz will push this through soon.

Thanks!


Travis configuration files need to be updated after changes in OCL IcdLoader project

I see changes in ICD loader project introducted by commit https://github.com/KhronosGroup/OpenCL-ICD-Loader/commit/7d2584c4b8b1ac186f67143aaa2f846184709a9e
I think without this changes in travis configuration build will fails.

All PRs merged. Closing.


Can't start craco - cannot read 'push' from undefined error

Hello! I was giving a try to this plugin, but I can't figure out how to make it run, here is the error:
C:\my-project>yarn start
yarn run v1.21.1
$ craco start
(node:11068) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'push' of undefined
    at Object.overrideWebpackConfig (C:\my-project\node_modules\@baristalabs\craco-raw-loader\lib\craco-raw-loader.js:47:36)
    at overrideWebpack (C:\my-project\node_modules\@craco\craco\lib\features\plugins.js:42:40)
    at C:\my-project\node_modules\@craco\craco\lib\features\plugins.js:64:29
    at Array.forEach (<anonymous>)
    at applyWebpackConfigPlugins (C:\my-project\node_modules\@craco\craco\lib\features\plugins.js:63:29)
    at mergeWebpackConfig (C:\my-project\node_modules\@craco\craco\lib\features\webpack\merge-webpack-config.js:110:30)
    at overrideWebpackDev (C:\my-project\node_modules\@craco\craco\lib\features\webpack\override.js:11:36)
    at C:\my-project\node_modules\@craco\craco\scripts\start.js:27:5
(Use `node --trace-warnings ...` to show where the warning was created)
(node:11068) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block,
or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:11068) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
Done in 9.77s.

My .cracorc.ts configuration file looks like the following:
import { CracoConfig } from '@craco/craco'
const CracoRawLoaderPlugin = require('@baristalabs/craco-raw-loader')

export default {
  plugins: [
    {
      plugin: CracoRawLoaderPlugin,
      options: {
        test: /\.txt$/,
      },
    },
  ],
} as CracoConfig

(Also tried importing the plugin with import either as namespace or default, but without sucess)
Node version v14.17.0

Hello, is there a solution to this problem? I met the same problem when I tried the plug-in


Adding reporting workflow to generate test_run manifest based on test workflow

Description
Add a new report workflow to generate a consolidated test-run.yml based on existing test results from test workflow (e.g. integ test).
The test results can be either from URL or local directory created from the type of test workflow from our ./test.sh.
This report workflow would include all components that are included in the test-manifest arguments unless specified.
Sample command to run this report workflow would be: ./report.sh manifests/2.8.0/opensearch-2.8.0-test.yml -p opensearch=https://ci.opensearch.org/ci/dbc/distribution-build-opensearch/2.8.0/7935/linux/x64/tar --test-run-id 5109 --test-type integ-test --base-path https://ci.opensearch.org/ci/dbc/integ-test/2.8.0/7935/linux/x64/tar
Issues Resolved
https://github.com/opensearch-project/opensearch-build/issues/1274
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Sample test-run.yml with command ./report.sh manifests/2.8.0/opensearch-2.8.0-test.yml -p opensearch=https://ci.opensearch.org/ci/dbc/distribution-build-opensearch/2.8.0/7935/linux/x64/tar --test-run-id 5109 --test-type integ-test --base-path https://ci.opensearch.org/ci/dbc/integ-test/2.8.0/7935/linux/x64/tar:
---
schema-version: '1.0'
name: OpenSearch
test-run:
  Command: ./test.sh integ-test manifests/2.8.0/opensearch-2.8.0-test.yml --paths
    opensearch=https://ci.opensearch.org/ci/dbc/distribution-build-opensearch/2.8.0/7935/linux/x64/tar
  TestType: integ-test
  TestManifest: manifests/2.8.0/opensearch-2.8.0-test.yml
  DistributionManifest: https://ci.opensearch.org/ci/dbc/distribution-build-opensearch/2.8.0/7935/linux/x64/tar/dist/opensearch/manifest.yml
  TestID: '5109'
components:
  - name: alerting
    command: ./test.sh integ-test manifests/2.8.0/opensearch-2.8.0-test.yml --paths
      opensearch=https://ci.opensearch.org/ci/dbc/distribution-build-opensearch/2.8.0/7935/linux/x64/tar
      --component alerting
    configs:
      - name: with-security
        status: FAIL
        yml: https://ci.opensearch.org/ci/dbc/integ-test/2.8.0/7935/linux/x64/tar/test-results/5109/integ-test/alerting/with-security/alerting.yml
      - name: without-security
        status: PASS
        yml: https://ci.opensearch.org/ci/dbc/integ-test/2.8.0/7935/linux/x64/tar/test-results/5109/integ-test/alerting/without-security/alerting.yml
  - name: anomaly-detection
    command: ./test.sh integ-test manifests/2.8.0/opensearch-2.8.0-test.yml --paths
      opensearch=https://ci.opensearch.org/ci/dbc/distribution-build-opensearch/2.8.0/7935/linux/x64/tar
      --component anomaly-detection
    configs:
      - name: with-security
        status: PASS
        yml: https://ci.opensearch.org/ci/dbc/integ-test/2.8.0/7935/linux/x64/tar/test-results/5109/integ-test/anomaly-detection/with-security/anomaly-detection.yml
      - name: without-security
        status: PASS
        yml: https://ci.opensearch.org/ci/dbc/integ-test/2.8.0/7935/linux/x64/tar/test-results/5109/integ-test/anomaly-detection/without-security/anomaly-detection.yml
  - name: asynchronous-search
    command: ./test.sh integ-test manifests/2.8.0/opensearch-2.8.0-test.yml --paths
      opensearch=https://ci.opensearch.org/ci/dbc/distribution-build-opensearch/2.8.0/7935/linux/x64/tar
      --component asynchronous-search
    configs:
      - name: with-security
        status: PASS
        yml: https://ci.opensearch.org/ci/dbc/integ-test/2.8.0/7935/linux/x64/tar/test-results/5109/integ-test/asynchronous-search/with-security/asynchronous-search.yml
      - name: without-security
        status: PASS
        yml: https://ci.opensearch.org/ci/dbc/integ-test/2.8.0/7935/linux/x64/tar/test-results/5109/integ-test/asynchronous-search/without-security/asynchronous-search.yml
  - name: cross-cluster-replication
    command: ./test.sh integ-test manifests/2.8.0/opensearch-2.8.0-test.yml --paths
      opensearch=https://ci.opensearch.org/ci/dbc/distribution-build-opensearch/2.8.0/7935/linux/x64/tar
      --component cross-cluster-replication
    configs:
      - name: with-security
        status: Not Available
        yml: URL not available
      - name: without-security
        status: Not Available
        yml: URL not available
  - name: geospatial
    command: ./test.sh integ-test manifests/2.8.0/opensearch-2.8.0-test.yml --paths
      opensearch=https://ci.opensearch.org/ci/dbc/distribution-build-opensearch/2.8.0/7935/linux/x64/tar
      --component geospatial
    configs:
      - name: with-security
        status: PASS
        yml: https://ci.opensearch.org/ci/dbc/integ-test/2.8.0/7935/linux/x64/tar/test-results/5109/integ-test/geospatial/with-security/geospatial.yml
      - name: without-security
        status: PASS
        yml: https://ci.opensearch.org/ci/dbc/integ-test/2.8.0/7935/linux/x64/tar/test-results/5109/integ-test/geospatial/without-security/geospatial.yml
  - name: index-management
    command: ./test.sh integ-test manifests/2.8.0/opensearch-2.8.0-test.yml --paths
      opensearch=https://ci.opensearch.org/ci/dbc/distribution-build-opensearch/2.8.0/7935/linux/x64/tar
      --component index-management
    configs:
      - name: with-security
        status: PASS
        yml: https://ci.opensearch.org/ci/dbc/integ-test/2.8.0/7935/linux/x64/tar/test-results/5109/integ-test/index-management/with-security/index-management.yml
      - name: without-security
        status: PASS
        yml: https://ci.opensearch.org/ci/dbc/integ-test/2.8.0/7935/linux/x64/tar/test-results/5109/integ-test/index-management/without-security/index-management.yml
  - name: k-NN
    command: ./test.sh integ-test manifests/2.8.0/opensearch-2.8.0-test.yml --paths
      opensearch=https://ci.opensearch.org/ci/dbc/distribution-build-opensearch/2.8.0/7935/linux/x64/tar
      --component k-NN
    configs:
      - name: with-security
        status: PASS
        yml: https://ci.opensearch.org/ci/dbc/integ-test/2.8.0/7935/linux/x64/tar/test-results/5109/integ-test/k-NN/with-security/k-NN.yml
      - name: without-security
        status: PASS
        yml: https://ci.opensearch.org/ci/dbc/integ-test/2.8.0/7935/linux/x64/tar/test-results/5109/integ-test/k-NN/without-security/k-NN.yml
  - name: ml-commons
    command: ./test.sh integ-test manifests/2.8.0/opensearch-2.8.0-test.yml --paths
      opensearch=https://ci.opensearch.org/ci/dbc/distribution-build-opensearch/2.8.0/7935/linux/x64/tar
      --component ml-commons
    configs:
      - name: with-security
        status: FAIL
        yml: https://ci.opensearch.org/ci/dbc/integ-test/2.8.0/7935/linux/x64/tar/test-results/5109/integ-test/ml-commons/with-security/ml-commons.yml
      - name: without-security
        status: PASS
        yml: https://ci.opensearch.org/ci/dbc/integ-test/2.8.0/7935/linux/x64/tar/test-results/5109/integ-test/ml-commons/without-security/ml-commons.yml
  - name: neural-search
    command: ./test.sh integ-test manifests/2.8.0/opensearch-2.8.0-test.yml --paths
      opensearch=https://ci.opensearch.org/ci/dbc/distribution-build-opensearch/2.8.0/7935/linux/x64/tar
      --component neural-search
    configs:
      - name: with-security
        status: FAIL
        yml: https://ci.opensearch.org/ci/dbc/integ-test/2.8.0/7935/linux/x64/tar/test-results/5109/integ-test/neural-search/with-security/neural-search.yml
      - name: without-security
        status: PASS
        yml: https://ci.opensearch.org/ci/dbc/integ-test/2.8.0/7935/linux/x64/tar/test-results/5109/integ-test/neural-search/without-security/neural-search.yml
  - name: notifications
    command: ./test.sh integ-test manifests/2.8.0/opensearch-2.8.0-test.yml --paths
      opensearch=https://ci.opensearch.org/ci/dbc/distribution-build-opensearch/2.8.0/7935/linux/x64/tar
      --component notifications
    configs:
      - name: with-security
        status: PASS
        yml: https://ci.opensearch.org/ci/dbc/integ-test/2.8.0/7935/linux/x64/tar/test-results/5109/integ-test/notifications/with-security/notifications.yml
      - name: without-security
        status: PASS
        yml: https://ci.opensearch.org/ci/dbc/integ-test/2.8.0/7935/linux/x64/tar/test-results/5109/integ-test/notifications/without-security/notifications.yml
  - name: opensearch-observability
    command: ./test.sh integ-test manifests/2.8.0/opensearch-2.8.0-test.yml --paths
      opensearch=https://ci.opensearch.org/ci/dbc/distribution-build-opensearch/2.8.0/7935/linux/x64/tar
      --component opensearch-observability
    configs:
      - name: with-security
        status: PASS
        yml: https://ci.opensearch.org/ci/dbc/integ-test/2.8.0/7935/linux/x64/tar/test-results/5109/integ-test/opensearch-observability/with-security/opensearch-observability.yml
      - name: without-security
        status: PASS
        yml: https://ci.opensearch.org/ci/dbc/integ-test/2.8.0/7935/linux/x64/tar/test-results/5109/integ-test/opensearch-observability/without-security/opensearch-observability.yml
  - name: opensearch-reports
    command: ./test.sh integ-test manifests/2.8.0/opensearch-2.8.0-test.yml --paths
      opensearch=https://ci.opensearch.org/ci/dbc/distribution-build-opensearch/2.8.0/7935/linux/x64/tar
      --component opensearch-reports
    configs:
      - name: with-security
        status: PASS
        yml: https://ci.opensearch.org/ci/dbc/integ-test/2.8.0/7935/linux/x64/tar/test-results/5109/integ-test/opensearch-reports/with-security/opensearch-reports.yml
      - name: without-security
        status: PASS
        yml: https://ci.opensearch.org/ci/dbc/integ-test/2.8.0/7935/linux/x64/tar/test-results/5109/integ-test/opensearch-reports/without-security/opensearch-reports.yml
  - name: security
    command: ./test.sh integ-test manifests/2.8.0/opensearch-2.8.0-test.yml --paths
      opensearch=https://ci.opensearch.org/ci/dbc/distribution-build-opensearch/2.8.0/7935/linux/x64/tar
      --component security
    configs:
      - name: with-security
        status: PASS
        yml: https://ci.opensearch.org/ci/dbc/integ-test/2.8.0/7935/linux/x64/tar/test-results/5109/integ-test/security/with-security/security.yml
  - name: security-analytics
    command: ./test.sh integ-test manifests/2.8.0/opensearch-2.8.0-test.yml --paths
      opensearch=https://ci.opensearch.org/ci/dbc/distribution-build-opensearch/2.8.0/7935/linux/x64/tar
      --component security-analytics
    configs:
      - name: with-security
        status: PASS
        yml: https://ci.opensearch.org/ci/dbc/integ-test/2.8.0/7935/linux/x64/tar/test-results/5109/integ-test/security-analytics/with-security/security-analytics.yml
      - name: without-security
        status: PASS
        yml: https://ci.opensearch.org/ci/dbc/integ-test/2.8.0/7935/linux/x64/tar/test-results/5109/integ-test/security-analytics/without-security/security-analytics.yml
  - name: sql
    command: ./test.sh integ-test manifests/2.8.0/opensearch-2.8.0-test.yml --paths
      opensearch=https://ci.opensearch.org/ci/dbc/distribution-build-opensearch/2.8.0/7935/linux/x64/tar
      --component sql
    configs:
      - name: with-security
        status: FAIL
        yml: https://ci.opensearch.org/ci/dbc/integ-test/2.8.0/7935/linux/x64/tar/test-results/5109/integ-test/sql/with-security/sql.yml
      - name: without-security
        status: PASS
        yml: https://ci.opensearch.org/ci/dbc/integ-test/2.8.0/7935/linux/x64/tar/test-results/5109/integ-test/sql/without-security/sql.yml

Hi @dblock,
Can you also help to review this PR since you were a core contributor for build side of things?
Thanks!

@zelinh Any update on this PR?

Merging this PR for now.


Add userid managed appsubs

https://github.com/open-cluster-management/backlog/issues/9533
Signed-off-by: Philip Wu<EMAIL_ADDRESS>

/test test-unit

/test test-unit

@xiangjingli Found a couple of other things on Friday:

appsub on the managed cluster (local-cluster) doesn't have the userid and group annotations. The user and group annotations are injected to the child appsub resource from the managed cluster, using the values in the annotation of the local appsub. So the appsub on the managed cluster needs theses annotations. I don't know if it creates any problems, or side-effects from this change.
kubeResource doesn't contain "spec", so when a resource is created from it, it fails due to the spec validation. So instead, I unmarshal the resource to an unstructured object and inject the annotations that way.

/lgtm

/lgtm

/test test-unit

/retest

/test test-unit

/retest


Need to be able pass in the "UserData Folder" to prevent access denied messages

If the Tes application is installed into %ProgramFolders%, then it cannot run due to the "UsedDataFolder" of WebView being created in a subdirectory.
Even running as Administrator does not solve the problem.

NO.. not the "MyDocuments" folder, because some institutions have this linked to always backup to a shared drive (Like one drive etc)
What's wrong with ProgramData ? (Or it's equivalent on Mac and Linux!)

@Smurf-IV While the conversations I've seen favor the MyDocuments folder, I don't see any reason we can't use the AppData folder for the user instead. Perhaps we can allow developers to override this when creating new windows as well.

The user's AppData directory is the standard for application data. Why would you want to change it to MyDocuments? That's so arbitrary.
Most users don't want to see bunch of temporary or configuration files from some rando app cluttering up their Documents directory. Also, this directory usually syncs with onedrive, and not many use cases need your app's data synced with the user's cloud storage.
My two cents...

@dimi3tron Thanks for the feedback. There is now a mechanism for setting the folder in the next upcoming version. It now defaults to the same folder as the .exe unless it's specifically set, but the default could easily be changed to the user's AppData folder now that the code is in place.

That is a workable solution.
I'm just going to hammer on it one last time, because I'm a firm believer that sensible defaults and adherence to standards and conventions make our lives as developers a lot easier.
This means that I'd want to install my app in a conventional place. This would be one of the Program Files directories on windows. In common setups, users won't have the necessary rights to write to these directories. So why not just default it to the AppData dir? I understand I'm nitpicking  and this is a cross-platform solution, so there will different configurations needed for each platform.
However, when I use a framework I expect it to use sensible defaults, so I don't have to worry about those things and I can just focus on the application I'm building. I don't have the slightest clue where I'd have to write user data on a Mac. I expect this sort of thing to be taken care of b the framework devs.
Drops mic
I'm just kind of ranting here, but I hope you can find some value in my remarks. I'll let it rest now  :-)
Or fork it and create a PR.

@dimi3tron This has already been implemented in 2.0! On Windows, it will default to AppDataLocal. It can also be overridden on any platform to any path you like. We're currently testing on Linux and then macOS before releasing.


Optional Dependencies

This is more of just opening a discussion rather than an actual issue.
One of the features being removed in 3.0 is Elite Dependencies. As a developer that does a lot of Angular, the first thing I thought was, "Devs that use jQuery + Angular aren't going to get jQuery guaranteed to be injected before Angular anymore (which is a requirement to get Angular to enhance their "jQuery Lite subset of jQuery functionality" to just use regular jQuery)."
Indeed, a quick test and Angular is being injected before jQuery.
So that begs the question: what's the best way to handle optional dependencies like that? I believe mostly we've been telling people to just use an override in their bower.json (i.e. override Angular to have a dependency on jQuery).
It should be noted that we don't really want Angular to put jQuery as a dependency, as it's optional. I'd say over half of my projects don't use jQuery, and the other half have been depending on Elite Dependencies to include jQuery first and will break in 3.0 unless I do something else.
I know I tend to be long-winded, but the point was: is there anything we could do to better handle optional dependencies? I think the two extremes are, "Just handle it yourself by putting in an override when you use the optional dependency" all the way to possibly something like a public repo of common things like that that wiredep can pull in. Basically, if jQuery is present, it can reference this directory of special overrides and make sure it gets injected automatically before Angular.
In other words, similar to Elite Dependencies, but more explicit and transparent (could add note/confirmation when it does something along these lines?).
I don't know, pretty much just thinking out loud/dumping stream-of-conscious.

That's a great point! I think the best solution is using excludes because you're effectively in a situation that tooling shouldn't magically resolve for you. Being explicit guarantees no surprises. The downside of course is that it's extra configuration that the developer won't be expecting. For sure, we should make a note of this specifically in the release notes. Does that sound reasonable or not good enough?

I don't know... I have mixed feelings. Like I was saying, my ideas here are sort of evolving as we talk.
I guess my bigger vision is a way to handle these edge cases. In my earlier example, we want this rule to be applied 100% of the time:
if jquery is a dependency in our bower.json
then add jquery as a dependency override to angular

This is something that we always want to happen. And something bower doesn't have a way to handle on its own. I think it's silly that it's always the developer's responsibility to manually do that when it is a black and white rule (in this case).
So I guess what I've been thinking about is sort of "the next level," and I would understand if it's more than what you want wiredep to be. I've mentioned in the past (but can't find the comment) that perhaps we should take up the torch and define a spec for overrides that others can follow for common interoperability.
Likewise, I'm thinking about how we can handle the edge cases that are that way most of the time. There are always exceptions, but many of them are handled the same way. This has been something we've felt is out of scope so far, and by providing overrides, it gives people the power to manually handle most edge cases. But just think for a second, what if we could add some of that (good) magic into wiredep to make it even easier to integrate those edge cases?
One would be a way to integrate optional dependencies, like in the case I mentioned with Angular and jQuery. Another would be when there are multiple themes (what if wiredep had a way to ask you which theme to choose when you injected files and to persist that choice?). Things like that, that have a very predictable and common methodology.
A couple things we could do is either define a spec to extend bower's kind of like we have done with overrides, but more well-defined. I know we've tried to get overrides as part of the bower official spec, but it's failed. The problem with something like optional deps or choosing among multiple deps is that would be on the package author to put something like that in their bower.json. But if we did it with an open, well-defined spec, we could do it in a way that other tools could hook into.
So the other alternative could be some sort of dedicated repo to define these sorts of overrides and optional things, etc, and to use that for the rules.
I realize this is a decently sized paradigm shift, and maybe not one that we really want now (or ever). But I love the magic of wiredep and how I can just install a package and it "just works." This proposal (is you want to call something this vague a "proposal") may be too little of a benefit for the added complexity, but I guess I just dream of a world where all I need to do is bower install package and wiredep and I'm good to go!
Ok... done rambling! ...for now =)

This is something that we always want to happen

Not necessarily. If you load angular first then it will use jqLite, which some people want and have coded against and don't have to worry about using a specific version of jQuery that is compatible with that version of Angular. A newer breaking jQuery may be what they want.
I feel like this is on the developer to be explicit about what they want that is non-standard. If you disagree, then lets keep this open and spitball some more ideas. Otherwise going to close as it would be probably impractical to implement something like this since we would have to know about every package and its requirements.


calculate guest memory overhead base on topology and not just cores

What this PR does / why we need it:
So far we were calculating the vcpus memory overhead based only on the guest cores.
This PR calculates the overhead based on guest topology.
Release note:
NONE

/lgtm
/approve

/cherrypick release-0.26


Add Home Assistant Nightly beta test badge toe the readme

This pull request adds a Home Assistant Nightly beta tests badge to the README to spot if it fails quickly.

coverage: 100.0%. remained the same
when pulling e9f19e7f65300319eae3f8cb0b97885a563c5d29 on create_home_asistant_beta_tests_badge
into 60cbc80ba1a814a19ff7e87d94f4ef02e179b6f2 on master.


[BEAM-5649] Conditionally remove CREATE_VIEW from java generated protos.

The graph generation is tightly coupled to legacy runner execution, but this
makes it possible for these implementation details to not leak outside of the
Java SDK.

Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

It will help us expedite review of your Pull Request if you tag someone (e.g. @username) to look at it.


[MB-8332] Create folders for components without them in src/components/Office/

Description
Take all the components without their own folders in src/components/Office and give them their own folder.
Reviewer Notes
Nothing in particular that I can see to call out.
Setup
Ensure the app runs as usual, etc.
Code Review Verification Steps

[ ] If the change is risky, it has been tested in experimental before merging.
[ ] Code follows the guidelines for Logging
[ ] The requirements listed in Querying the Database Safely have been satisfied.
Any new migrations/schema changes:

[ ] Follow our guidelines for zero-downtime deploys (see Zero-Downtime Deploys)
[ ] Have been communicated to #g-database
[ ] Secure migrations have been tested following the instructions in our docs

[ ] There are no aXe warnings for UI.
[ ] This works in Supported Browsers and their phone views (Chrome, Firefox, IE, Edge).
[ ] Tested in the Experimental environment (for changes to containers, app startup, or connection to data stores)
[ ] User facing changes have been reviewed by design.
[ ] Request review from a member of a different team.
[ ] Have the Jira acceptance criteria been met for this change?

References

Jira story for this change

Warnings

:warning:
Please add the JIRA issue key to the PR title (e.g. MB-123)

  Generated by :no_entry_sign: dangerJS against 872fd86a76be42620061d7e131401573b420de8b

Messages

:book:
:link: MB-8332

  Generated by :no_entry_sign: dangerJS against 711a578c8eaf916bf095357ac7444b45ed0e92a6


fixes #12

Listen to backspace key event when a focussed textfield is empty.
Previously - Not able to move to previous field when backspace is tapped

thanks so much @Ayush783 for your work.
I have published it


Document CSI update

Document CSI volume expansion.
xref https://github.com/kubernetes/enhancements/issues/556

@gnufied @msau42 can I get a technical LGTM then this is ready to merge. Thanks!
/lgtm

/lgtm
Thanks!

Thanks, everyone!
/approve


More usability changes

I started trying it and here few low hanging fruits usability-wise:

start presenting paths from the output_dir if present
present only the directories within it

Thank you for taking a look at this! I left one comment about path filtering, but the other changes look good. Should be good to merge this later tonight.

Actually these changes look fine to me. I'll just merge now and do some quick functional testing later today :)


Update Core schema diagrams for release 97

Part of the e! 97 release cycle. See ENSCORESW-3096.

Is this for release 96 ? If can you resubmit the PR against postreleasefix/96 ?

Ah, just read the commit message, apologies. Will merge it later


Jordan CD and NCD Download

To please update the Jordan CD and NCD download function to include additional variables (as attached, the new variables are highlighted in yellow).
Public Health Surveillance | Data Dictionary Codes.docx

To please also include BMI in the NCD download function (revised codes file attached).
Public Health Surveillance | Data Dictionary Codes.docx

I note that BMI is not yet included in the download if we can please include

How is BMI calculated in our context?  Is it just a case of including the lab_3 variable from the jordan codes file? Or do you want something different?

This is finished.


Localhost setup

I was following a tutorial to setup a testing server on my imac running High
10.13.  At step 23 (of 25 steps) when I entered the following command:
sudo openssl req -extensions san -config /etc/ssl/openssl.cnf -x509 -nodes -newkey rsa:4096 -keyout /private/etc/apache2/server.key -out /private/etc/apache2/server.crt -days 365 -subj "/C=US/ST=Florida/L=Boca Raton/O=WebsiteBeaver/CN=localhost"
I got the following message:
Error Loading extension section san
Can you help me please?  I'm a 76-year-old retiree trying to dabble in website development as a hobby. I've had some Unix experience in the past.  I manage OK with websites that deals with the client side only, but I need to get into some server side processing.

What tutorial were you following? The command you’ve listed doesn’t have anything to do with dehydrated itself, so I’m a bit confused on how you got here.

I created a new GitHub account and attempted to create a “New Issue”.  I have no idea how it ended us a part of your thread.  Perhaps in my frustration in seeking an answer to my problem I did not pay enough attention to what I was doing.  I sincerely apologies for the error.  I will revisit the process and try to identify what I did wrong.

On Mar 22, 2018, at 1:03 AM, txr13<EMAIL_ADDRESS><EMAIL_ADDRESS>wrote:
What tutorial were you following? The command you’ve listed doesn’t have anything to do with dehydrated itself, so I’m a bit confused on how you got here.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/lukas2511/dehydrated/issues/519#issuecomment-375180749, or mute the thread https://github.com/notifications/unsubscribe-auth/Aj5f6ixsl6ko0BXNf8mRkHP-SSyHu720ks5tgzCcgaJpZM4S2Rsy.

This is a test.Please Ignore!!

On Mar 22, 2018, at 1:03 AM, txr13<EMAIL_ADDRESS>wrote:
What tutorial were you following? The command you’ve listed doesn’t have anything to do with dehydrated itself, so I’m a bit confused on how you got here.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/lukas2511/dehydrated/issues/519#issuecomment-375180749, or mute the thread https://github.com/notifications/unsubscribe-auth/Aj5f6ixsl6ko0BXNf8mRkHP-SSyHu720ks5tgzCcgaJpZM4S2Rsy.

@lukas2511 I think this can be closed.


Support for certificate chains

Currently, a single IdP  SSL certificate can be set in the settings file. For example, the loop reading the cert for fingerprinting will terminate at the first "END CERTIFICATE".
This means that cert chains, where several certs are chained together, cannot be used.
Perhaps making the IdP x509cert field an array of strings instead of a single string could solve this?

Sorry, for now the toolkit only supports 1 IdP cert.

Just curious, is only a single iDP cert (no internal root\CA chains) still the case with the latest release?


feat: rework socket

#182
Checklist

[ ] I didn't over-scope my PR
[ ] My PR title matches the commit convention
[ ] I did not include breaking changes
[ ] I included unit tests that cover my changes
[ ] I added/updated the documentation about my changes
[ ] I made my own code-review before requesting one

Description of the changes
Fast change to make it work.
We will need a big refactoring on the client/lenra_ui_runner to create the view system for lenra too.
But for now it work like before with the json view.
https://github.com/lenra-io/application-runner/pull/242

@jonas-martinez i have an issue with the lenra_image_test.dart file during analyze/test locally.
No idea why, i did not touch this...
It's working with the CI tho.
Any idea ?

This is indicated in the README but it might be better to execute it automatically when running the tests. What do you think ?

Could be yes. We can create a new issue to do this !

:tada: This PR is included in version 1.0.0-beta.93 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

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


Update

Updating packages, fixing lint, releasing 3.0.8
Updating package lock
Removing dead bithound badge
update package.json and package-lock.json
new build
new build

Opened by @bsimons on 2020-11-30 17:11:03

@bsimons added reviewers on 2020-11-30 17:11:03
@153957


Support for Standalone Google Apps Script Projects

Being able to create sidebars is all well and good when your script is tied to a Document, but what about those of us who want to use Apps Script to interact with OAuth Services in standalone Apps Script projects? We can't call things like DocumentApp.getUi().showSidebar(page);.

Unfortunately there is no way for scripts to manipulate the UI of the script editor. You can either log a message with the URL to open (like the samples do) or publish the script as a web app.


Build Pipeline Bug - .net core build failing

Description
Pool: [Azure Pipelines]
Image: windows-latest
.NET Core Build task is stuck and our build pipeline is failing:
##[error]The job running on agent Azure Pipelines 2 ran longer than the maximum time of 60 minutes. For more information, see https://go.microsoft.com/fwlink/?linkid=2077134
As a workaround, we tried configuring self-hosted agents, on the devs machine, and all the failed builds were executed successfully.
I've already created a ticket with the developer community, and more information and logs can be found here :
https://developercommunity.visualstudio.com/t/Build-Pipeline-Bug---net-core-build-fai/10391627
From the last response from the agent, it seems like the earlier succeeded run is upon the image version of ‘20230508.3’, and the failed runs are after this very version.
Platforms affected

[X] Azure DevOps
[ ] GitHub Actions - Standard Runners
[ ] GitHub Actions - Larger Runners

Runner images affected

[ ] Ubuntu 20.04
[ ] Ubuntu 22.04
[ ] macOS 11
[ ] macOS 12
[ ] macOS 13
[ ] Windows Server 2019
[X] Windows Server 2022

Image version and build link
Agent name: 'Azure Pipelines 2'
Agent machine name: 'fv-az406-355'
Current agent version: '3.220.5'
Operating System
Runner Image
Runner Image Provisioner
Current image version: '20230612.1'
Agent running as: 'VssAdministrator
Is it regression?
no
Expected behavior
Idempotent result when executing the build pipeline using azure pipeline agents and self-hosted ones.
Actual behavior
The build pipeline is failing when using Azure Pipelines' agents
Repro steps
Variable Group '' was defined in the Variables tab
Agent Queue 'Azure Pipelines' was used with unrecognized Agent Specification, vmImage property must be specified to determine image - https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/hosted?view=azure-devops&tabs=yaml#software
trigger:
branches:
include:
- refs/heads/master
- refs/heads/release/1.8.0
paths:
include:
- /web
- /api
batch: True
name: $(version. Major).$(version. Minor).$(version. Patch)$(Rev:.r)
resources:
repositories:

repository: self
type: git
ref: refs/heads/master
jobs:
job: Job_1
displayName: Agent job 1
pool:
name: Azure Pipelines
steps:

checkout: self
task: UseDotNet@2
displayName: Use .NET Core sdk 7.x
inputs:
version: 7.x
task: DotNetCoreCLI@2
displayName: dotnet restore
inputs:
command: restore
projects: ./api/,.sln
task: DotNetCoreCLI@2
displayName: dotnet build
inputs:
projects: ./api/<projectname.sln
task: DotNetCoreCLI@2
displayName: dotnet test
inputs:
command: test
projects: ./api/<projectname.sln
arguments: --no-build
task: DotNetCoreCLI@2
displayName: dotnet publish api
inputs:
command: publish
publishWebProjects: false
projects: '**/. Facade.csproj'
arguments: --output $(Build.ArtifactStagingDirectory)/api
zipAfterPublish: false
task: DotNetCoreCLI@2
displayName: dotnet publish usersync
inputs:
command: publish
publishWebProjects: false
projects: '**/. UserSync.csproj'
arguments: --output $(Build.ArtifactStagingDirectory)/usersync
zipAfterPublish: false
task: DotNetCoreCLI@2
displayName: dotnet publish emailreminders
inputs:
command: publish
publishWebProjects: false
projects: '**/. EmailReminders.csproj'
arguments: --output $(Build.ArtifactStagingDirectory)/emailreminders
zipAfterPublish: false
task: NodeTool@0
displayName: Use Node 12.x
inputs:
versionSpec: 12.x
checkLatest: true
task: Npm@1
displayName: npm install
inputs:
workingDir: web
verbose: false
task: Npm@1
displayName: npm build
inputs:
command: custom
workingDir: web
verbose: false
customCommand: run build
task: CopyFiles@2
displayName: Copy web.config to build folder
inputs:
SourceFolder: web
Contents: web.config
TargetFolder: web\build
task: CopyFiles@2
displayName: Copy frontend files to staging directory
inputs:
SourceFolder: web\build
TargetFolder: $(Build.ArtifactStagingDirectory)/ui
task: PublishBuildArtifacts@1
displayName: Publish Artifact
inputs:
ArtifactName:
...

Hi @ilia-shipitsin,
Do you have an approx time of resolution, we are dealing with this issue for more than 3 weeks already.
Maybe you can share with me a link to the main Problem so I can follow up on what's happening?
thanks!

Unfortunately, no details yet.

Hi @ilia-shipitsin
Maybe you got any updates? it's been a while now already.
thanks

it is internal incident tracker, no public access. from what I see that particular incident was resolved.
probably, your issue has different nature. can you provide build links (even if they are private, we can try to follow up) ?

Hello, @Iddorot , we have similar issue https://github.com/actions/runner-images/issues/7683
it was reported for the same build image update. It describes some specific details in .net behaviour regarding "sync vs async"  in .net itself.
as you say, it works on your self hosted runners, can you please check different .net versions to narrow change ?

Hi @ilia-shipitsin
The Azure Devops project is private so I'm not sure if sharing the build links can help.
I'm sharing the logs from "use .net core" tasks in the exact same build using the different agents.
MS Hosted Agents .net logs:
2023-07-03T07:10:17.4937466Z ##[debug]Evaluating condition for step: 'Use .NET Core sdk 7.x' 2023-07-03T07:10:17.4938884Z ##[debug]Evaluating: succeeded() 2023-07-03T07:10:17.4939104Z ##[debug]Evaluating succeeded: 2023-07-03T07:10:17.4939548Z ##[debug]=> True 2023-07-03T07:10:17.4939774Z ##[debug]Result: True 2023-07-03T07:10:17.4939996Z ##[section]Starting: Use .NET Core sdk 7.x 2023-07-03T07:10:17.5046431Z ============================================================================== 2023-07-03T07:10:17.5046572Z Task         : Use .NET Core 2023-07-03T07:10:17.5046663Z Description  : Acquires a specific version of the .NET Core SDK from the internet or the local cache and adds it to the PATH. Use this task to change the version of .NET Core used in subsequent tasks. Additionally provides proxy support. 2023-07-03T07:10:17.5046875Z Version      : 2.222.0 2023-07-03T07:10:17.5046928Z Author       : Microsoft Corporation 2023-07-03T07:10:17.5046993Z Help         : https://aka.ms/AA4xgy0 2023-07-03T07:10:17.5047074Z ============================================================================== 2023-07-03T07:10:17.5820132Z ##[debug]Using node path: C:\agents\3.220.5\externals\node10\bin\node.exe 2023-07-03T07:10:17.9784746Z ##[debug]agent.TempDirectory=D:\a\_temp 2023-07-03T07:10:17.9807643Z ##[debug]loading inputs and endpoints 2023-07-03T07:10:17.9817047Z ##[debug]loading ENDPOINT_AUTH_PARAMETER_SYSTEMVSSCONNECTION_ACCESSTOKEN 2023-07-03T07:10:17.9907194Z ##[debug]loading ENDPOINT_AUTH_SCHEME_SYSTEMVSSCONNECTION 2023-07-03T07:10:17.9910170Z ##[debug]loading ENDPOINT_AUTH_SYSTEMVSSCONNECTION 2023-07-03T07:10:17.9913151Z ##[debug]loading INPUT_INCLUDEPREVIEWVERSIONS 2023-07-03T07:10:17.9915118Z ##[debug]loading INPUT_INSTALLATIONPATH 2023-07-03T07:10:17.9917004Z ##[debug]loading INPUT_PACKAGETYPE 2023-07-03T07:10:17.9918848Z ##[debug]loading INPUT_PERFORMMULTILEVELLOOKUP 2023-07-03T07:10:17.9920659Z ##[debug]loading INPUT_USEGLOBALJSON 2023-07-03T07:10:17.9922465Z ##[debug]loading INPUT_VERSION 2023-07-03T07:10:17.9924505Z ##[debug]loading INPUT_WORKINGDIRECTORY 2023-07-03T07:10:17.9937658Z ##[debug]loaded 10 2023-07-03T07:10:17.9943659Z ##[debug]Agent.ProxyUrl=undefined 2023-07-03T07:10:17.9944585Z ##[debug]Agent.CAInfo=undefined 2023-07-03T07:10:17.9944962Z ##[debug]Agent.ClientCert=undefined 2023-07-03T07:10:17.9945430Z ##[debug]Agent.SkipCertValidation=undefined 2023-07-03T07:10:18.0374713Z ##[debug]Agent.ProxyUrl=undefined 2023-07-03T07:10:18.0375490Z ##[debug]Agent.CAInfo=undefined 2023-07-03T07:10:18.0375980Z ##[debug]Agent.ClientCert=undefined 2023-07-03T07:10:18.0376485Z ##[debug]check path : D:\a\_tasks\UseDotNet_b0ce7256-7898-45d3-9cb5-176b752bfea6\2.222.0\node_modules\azure-pipelines-tool-lib\lib.json 2023-07-03T07:10:18.0383611Z ##[debug]adding resource file: D:\a\_tasks\UseDotNet_b0ce7256-7898-45d3-9cb5-176b752bfea6\2.222.0\node_modules\azure-pipelines-tool-lib\lib.json 2023-07-03T07:10:18.0384124Z ##[debug]system.culture=en-US 2023-07-03T07:10:18.0630008Z ##[debug]Agent.ProxyUrl=undefined 2023-07-03T07:10:18.0630765Z ##[debug]Agent.CAInfo=undefined 2023-07-03T07:10:18.0631265Z ##[debug]Agent.ClientCert=undefined 2023-07-03T07:10:18.0631864Z ##[debug]check path : D:\a\_tasks\UseDotNet_b0ce7256-7898-45d3-9cb5-176b752bfea6\2.222.0\node_modules\azure-pipelines-tasks-packaging-common\node_modules\azure-pipelines-tool-lib\lib.json 2023-07-03T07:10:18.0632571Z ##[debug]adding resource file: D:\a\_tasks\UseDotNet_b0ce7256-7898-45d3-9cb5-176b752bfea6\2.222.0\node_modules\azure-pipelines-tasks-packaging-common\node_modules\azure-pipelines-tool-lib\lib.json 2023-07-03T07:10:18.0633375Z ##[debug]system.culture=en-US 2023-07-03T07:10:18.0719635Z ##[debug]Setting resource path to D:\a\_tasks\UseDotNet_b0ce7256-7898-45d3-9cb5-176b752bfea6\2.222.0\task.json 2023-07-03T07:10:18.0720217Z ##[debug]check path : D:\a\_tasks\UseDotNet_b0ce7256-7898-45d3-9cb5-176b752bfea6\2.222.0\task.json 2023-07-03T07:10:18.0720760Z ##[debug]adding resource file: D:\a\_tasks\UseDotNet_b0ce7256-7898-45d3-9cb5-176b752bfea6\2.222.0\task.json 2023-07-03T07:10:18.0723000Z ##[debug]system.culture=en-US 2023-07-03T07:10:18.0733163Z ##[debug]check path : D:\a\_tasks\UseDotNet_b0ce7256-7898-45d3-9cb5-176b752bfea6\2.222.0\node_modules\azure-pipelines-tasks-packaging-common\module.json 2023-07-03T07:10:18.0733898Z ##[debug]adding resource file: D:\a\_tasks\UseDotNet_b0ce7256-7898-45d3-9cb5-176b752bfea6\2.222.0\node_modules\azure-pipelines-tasks-packaging-common\module.json 2023-07-03T07:10:18.0734381Z ##[debug]system.culture=en-US 2023-07-03T07:10:18.0835892Z ##[debug]useGlobalJson=false 2023-07-03T07:10:18.0837311Z ##[debug]packageType=sdk 2023-07-03T07:10:18.0838573Z ##[debug]version=7.x 2023-07-03T07:10:18.0838963Z ##[debug]vsVersion=undefined 2023-07-03T07:10:18.0839411Z ##[debug]nugetVersion=undefined 2023-07-03T07:10:18.0839978Z ##[debug]installationPath=C:\hostedtoolcache\windows/dotnet 2023-07-03T07:10:18.0841134Z ##[debug]performMultiLevelLookup=false 2023-07-03T07:10:18.0842450Z ##[debug]includePreviewVersions=false 2023-07-03T07:10:18.0844211Z ##[debug]workingDirectory=D:\a\1\s 2023-07-03T07:10:18.0847271Z ##[debug]agent.proxyurl=undefined 2023-07-03T07:10:18.0847704Z ##[debug]AZURE_HTTP_USER_AGENT=VSTS_065385ef-a071-4857-a61d-eb38d07e591c_build_40_0 2023-07-03T07:10:18.0854655Z ##[debug]testing directory 'C:\hostedtoolcache\windows/dotnet' 2023-07-03T07:10:18.0856191Z ##[debug]testing directory 'C:\hostedtoolcache\windows' 2023-07-03T07:10:18.0859090Z ##[debug]mkdir 'C:\hostedtoolcache\windows/dotnet' 2023-07-03T07:10:18.0884248Z Tool to install: .NET Core sdk version 7.x. 2023-07-03T07:10:18.7935099Z ##[debug]Finding channel 7.0 for version 7.x 2023-07-03T07:10:20.3337475Z Found version 7.0.305 in channel 7.0 for user specified version spec: 7.x 2023-07-03T07:10:20.3761456Z ##[debug]Processed: ##vso[telemetry.publish area=TaskDeploymentMethod;feature=UseDotNetV2]{"userVersion":"7.x", "resolvedVersion":"7.0.305"} 2023-07-03T07:10:20.3762291Z ##[debug]isExplicit: 7.0.305 2023-07-03T07:10:20.3781822Z ##[debug]explicit? true 2023-07-03T07:10:20.3787176Z Version 7.0.305 was not found in cache. 2023-07-03T07:10:20.3805769Z Getting URL to download .NET Core sdk version: 7.0.305. 2023-07-03T07:10:20.3806199Z Detecting OS platform to find correct download package for the OS. 2023-07-03T07:10:20.3806683Z ##[debug]which 'powershell' 2023-07-03T07:10:20.3807285Z ##[debug]found: 'C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe' 2023-07-03T07:10:20.3807729Z ##[debug]which 'C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe' 2023-07-03T07:10:20.3808184Z ##[debug]found: 'C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe' 2023-07-03T07:10:20.3809713Z ##[debug]C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe arg: -NoLogo -Sta -NoProfile -NonInteractive -ExecutionPolicy Unrestricted -Command 2023-07-03T07:10:20.3812392Z ##[debug]C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe arg: & 'D:\a\_tasks\UseDotNet_b0ce7256-7898-45d3-9cb5-176b752bfea6\2.222.0\externals\get-os-platform.ps1' 2023-07-03T07:10:20.3813004Z ##[debug]exec tool: C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe 2023-07-03T07:10:20.3813416Z ##[debug]arguments: 2023-07-03T07:10:20.3813775Z ##[debug]   -NoLogo 2023-07-03T07:10:20.3814124Z ##[debug]   -Sta 2023-07-03T07:10:20.3814475Z ##[debug]   -NoProfile 2023-07-03T07:10:20.3814837Z ##[debug]   -NonInteractive 2023-07-03T07:10:20.3815191Z ##[debug]   -ExecutionPolicy 2023-07-03T07:10:20.3815913Z ##[debug]   Unrestricted 2023-07-03T07:10:20.3816319Z ##[debug]   -Command 2023-07-03T07:10:20.3816972Z ##[debug]   & 'D:\a\_tasks\UseDotNet_b0ce7256-7898-45d3-9cb5-176b752bfea6\2.222.0\externals\get-os-platform.ps1' 2023-07-03T07:10:20.3817888Z [command]C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -NoLogo -Sta -NoProfile -NonInteractive -ExecutionPolicy Unrestricted -Command "& 'D:\a\_tasks\UseDotNet_b0ce7256-7898-45d3-9cb5-176b752bfea6\2.222.0\externals\get-os-platform.ps1'" 2023-07-03T07:10:20.7062079Z Primary:win-x64 2023-07-03T07:10:20.7063561Z Detected platform (Primary): win-x64 2023-07-03T07:10:20.7065403Z ##[debug]Got download URL for platform with rid: win-x64 2023-07-03T07:10:20.7074079Z ##[debug] 2023-07-03T07:10:20.7076324Z ##[debug]Agent.Version=3.220.5 2023-07-03T07:10:20.7076626Z ##[debug]Agent.TempDirectory=D:\a\_temp 2023-07-03T07:10:20.7077012Z ##[debug]testing directory 'D:\a\_temp' 2023-07-03T07:10:20.7091538Z Downloading: https://download.visualstudio.microsoft.com/download/pr/ca2298f8-7c39-4187-98e5-f1be30e5eee5/b76077aaf76b1751b77fd4574837a0ab/dotnet-sdk-7.0.305-win-x64.zip 2023-07-03T07:10:20.7092342Z ##[debug]destination D:\a\_temp\1d2d8208-341b-405a-9cdb-0270966510ab 2023-07-03T07:10:20.7092799Z ##[debug]downloading 2023-07-03T07:10:20.8615110Z ##[debug]creating stream 2023-07-03T07:10:22.4757556Z ##[debug]download complete 2023-07-03T07:10:22.4758719Z Extracting downloaded package D:\a\_temp\1d2d8208-341b-405a-9cdb-0270966510ab. 2023-07-03T07:10:22.4759304Z ##[debug]Agent.TempDirectory=D:\a\_temp 2023-07-03T07:10:22.4759622Z Extracting archive 2023-07-03T07:10:22.4759982Z ##[debug]testing directory 'D:\a\_temp\93a7' 2023-07-03T07:10:22.4760371Z ##[debug]testing directory 'D:\a\_temp' 2023-07-03T07:10:22.4760771Z ##[debug]mkdir 'D:\a\_temp\93a7' 2023-07-03T07:10:22.4761530Z ##[debug]which 'C:\Windows\system32\chcp.com' 2023-07-03T07:10:22.4762758Z ##[debug]found: 'C:\Windows\system32\chcp.com' 2023-07-03T07:10:22.4763131Z ##[debug]C:\Windows\system32\chcp.com arg: 65001 2023-07-03T07:10:22.4763547Z ##[debug]C:\Windows\system32\chcp.com arg: 65001 2023-07-03T07:10:22.4766579Z ##[debug]exec tool: C:\Windows\system32\chcp.com 2023-07-03T07:10:22.4767097Z ##[debug]exec tool: C:\Windows\system32\chcp.com 2023-07-03T07:10:22.4767482Z ##[debug]arguments: 2023-07-03T07:10:22.4767859Z ##[debug]arguments: 2023-07-03T07:10:22.4768206Z ##[debug]   65001 2023-07-03T07:10:22.4768547Z ##[debug]   65001 2023-07-03T07:10:22.4768834Z [command]C:\Windows\system32\chcp.com 65001 2023-07-03T07:10:22.4863651Z Active code page: 65001 2023-07-03T07:10:22.4942877Z ##[debug]Exit code 0 received from tool 'C:\Windows\system32\chcp.com' 2023-07-03T07:10:22.4948153Z ##[debug]Exit code 0 received from tool 'C:\Windows\system32\chcp.com' 2023-07-03T07:10:22.4948706Z ##[debug]STDIO streams have closed for tool 'C:\Windows\system32\chcp.com' 2023-07-03T07:10:22.4949145Z ##[debug]STDIO streams have closed for tool 'C:\Windows\system32\chcp.com' 2023-07-03T07:10:22.4949539Z ##[debug]which 'powershell' 2023-07-03T07:10:22.5064236Z ##[debug]found: 'C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe' 2023-07-03T07:10:22.5082807Z ##[debug]C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe arg: -NoLogo -Sta -NoProfile -NonInteractive -ExecutionPolicy Unrestricted -Command 2023-07-03T07:10:22.5105038Z ##[debug]C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe arg: $ErrorActionPreference = 'Stop' ; try { Add-Type -AssemblyName System.IO.Compression.FileSystem } catch { } ; [System.IO.Compression.ZipFile]::ExtractToDirectory('D:\a\_temp\1d2d8208-341b-405a-9cdb-0270966510ab', 'D:\a\_temp\93a7') 2023-07-03T07:10:22.5113593Z ##[debug]exec tool: C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe 2023-07-03T07:10:22.5114923Z ##[debug]arguments: 2023-07-03T07:10:22.5119973Z ##[debug]   -NoLogo 2023-07-03T07:10:22.5120370Z ##[debug]   -Sta 2023-07-03T07:10:22.5120725Z ##[debug]   -NoProfile 2023-07-03T07:10:22.5121088Z ##[debug]   -NonInteractive 2023-07-03T07:10:22.5121441Z ##[debug]   -ExecutionPolicy 2023-07-03T07:10:22.5122006Z ##[debug]   Unrestricted 2023-07-03T07:10:22.5122366Z ##[debug]   -Command 2023-07-03T07:10:22.5122930Z ##[debug]   $ErrorActionPreference = 'Stop' ; try { Add-Type -AssemblyName System.IO.Compression.FileSystem } catch { } ; [System.IO.Compression.ZipFile]::ExtractToDirectory('D:\a\_temp\1d2d8208-341b-405a-9cdb-0270966510ab', 'D:\a\_temp\93a7') 2023-07-03T07:10:22.5124268Z [command]C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -NoLogo -Sta -NoProfile -NonInteractive -ExecutionPolicy Unrestricted -Command "$ErrorActionPreference = 'Stop' ; try { Add-Type -AssemblyName System.IO.Compression.FileSystem } catch { } ; [System.IO.Compression.ZipFile]::ExtractToDirectory('D:\a\_temp\1d2d8208-341b-405a-9cdb-0270966510ab', 'D:\a\_temp\93a7')" 2023-07-03T07:10:32.5319496Z ##[debug]Exit code 0 received from tool 'C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe' 2023-07-03T07:10:32.5320427Z ##[debug]STDIO streams have closed for tool 'C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe' 2023-07-03T07:10:32.5321092Z ##[debug]Copying all root folders into installation path: C:\hostedtoolcache\windows/dotnet 2023-07-03T07:10:47.5739094Z ##[debug]Comparing if version being installed 7.0.305 is greater than already installed version with folder name 7.0.305 2023-07-03T07:10:47.5739983Z ##[debug]isExplicit: 7.0.305 2023-07-03T07:10:47.5740359Z ##[debug]explicit? true 2023-07-03T07:10:47.5740741Z ##[debug]isExplicit: 7.0.305 2023-07-03T07:10:47.5741103Z ##[debug]explicit? true 2023-07-03T07:10:47.5742816Z ##[debug]Version: 7.0.305 is the latest among the versions present at path: C:\hostedtoolcache\windows/dotnet 2023-07-03T07:10:47.5743392Z ##[debug]Copying root files (such as dotnet.exe) into installation path: C:\hostedtoolcache\windows/dotnet 2023-07-03T07:10:47.5887037Z ##[debug]Creating installation complete marker file for .Net core 7.0.305 version sdk 2023-07-03T07:10:47.6048118Z Successfully installed .NET Core sdk version 7.0.305. 2023-07-03T07:10:47.6049697Z ##[debug]Agent.Version=3.220.5 2023-07-03T07:10:47.6050442Z ##[debug]Processed: ##vso[task.prependpath]C:\hostedtoolcache\windows/dotnet 2023-07-03T07:10:47.6051439Z ##[debug]set DOTNET_ROOT=C:\hostedtoolcache\windows/dotnet 2023-07-03T07:10:47.6062359Z ##[debug]Processed: ##vso[task.setvariable variable=DOTNET_ROOT;isOutput=false;issecret=false;]C:\hostedtoolcache\windows/dotnet 2023-07-03T07:10:47.6063000Z ##[debug]set DOTNET_MULTILEVEL_LOOKUP=0 2023-07-03T07:10:47.6063673Z ##[debug]Processed: ##vso[task.setvariable variable=DOTNET_MULTILEVEL_LOOKUP;isOutput=false;issecret=false;]0 2023-07-03T07:10:47.6064363Z Creating global tool path and pre-pending to PATH. 2023-07-03T07:10:47.6064764Z ##[debug]testing directory 'C:\Users\VssAdministrator\.dotnet\tools' 2023-07-03T07:10:47.6065175Z ##[debug]Agent.Version=3.220.5 2023-07-03T07:10:47.6065653Z ##[debug]Processed: ##vso[task.prependpath]C:\Users\VssAdministrator\.dotnet\tools 2023-07-03T07:10:47.6066117Z ##[debug]Agent.ProxyUrl=undefined 2023-07-03T07:10:47.6066503Z ##[debug]task result: Succeeded 2023-07-03T07:10:47.6073363Z ##[debug]Processed: ##vso[task.complete result=Succeeded;] 2023-07-03T07:10:47.6160252Z ##[section]Finishing: Use .NET Core sdk 7.x
Self Hosted Agents logs:
2023-06-28T07:47:26.5374097Z ##[section]Starting: Use .NET Core sdk 7.x 2023-06-28T07:47:26.5574030Z ============================================================================== 2023-06-28T07:47:26.5574154Z Task         : Use .NET Core 2023-06-28T07:47:26.5574244Z Description  : Acquires a specific version of the .NET Core SDK from the internet or the local cache and adds it to the PATH. Use this task to change the version of .NET Core used in subsequent tasks. Additionally provides proxy support. 2023-06-28T07:47:26.5574434Z Version      : 2.222.0 2023-06-28T07:47:26.5574478Z Author       : Microsoft Corporation 2023-06-28T07:47:26.5574532Z Help         : https://aka.ms/AA4xgy0 2023-06-28T07:47:26.5574623Z ============================================================================== 2023-06-28T07:47:29.5744879Z Tool to install: .NET Core sdk version 7.x. 2023-06-28T07:47:32.2784820Z Found version 7.0.305 in channel 7.0 for user specified version spec: 7.x 2023-06-28T07:47:32.3136709Z Version: 7.0.305 was found in cache. 2023-06-28T07:47:32.3145389Z Creating global tool path and pre-pending to PATH. 2023-06-28T07:47:32.3161844Z ##[section]Finishing: Use .NET Core sdk 7.x

looks like 2.222.0 is used in both Hosted and Self Hosted agents.
taking into account that there's no visiable difference between self-hosted and hosted agents, I would ask you to provide repro steps, otherwise we are out of ideas, I do not have a clue what steps would we take.

@Iddorot , can you please provide repro steps ?

I'm closing issue. Feel free to reopen if the problem still exists. Thank you.


deploy gnosis safes properly and change hardhat config

deploy gnosis safes with modules
fixed nonce too low error because .wait() wasn't being awaited
changed optimizer runs in hardhat config

aight looks like we're going w/ this


Interval

Hi Guys,
there is one request I want and one bug I want to report.
First, the bug:
Interval is being created without removing it when page change.
I would probably solve it in $destroy event and remove the interval or something.
It would be great if you can fix it.
Second, is there a way to communicate with the carousel. I want to start the carousel with automatic loop and stop and resume it on user behaviour. if he clicks on something or hover the carousel.
Waiting for your reply.

Hi @Roycohen
Thanks for catching that. Bug reported at: #24
I also created one more task to implement pausing carousel on hover #25
Now, to enable controlling carousel out of carousel is not what I imagine in the first place. If you have idea how this can be done, feel free to fork the repository
#24 and #25 it's on me and I will try to do it once I get some free time.
Cheers

Hi @Wlada Thanks!
Looking forward for this to be resolved.


Create ricktshawtd.md

@heyword - OK with this?

What state or country is El Segundo in?

Approved


Addition meta

Often ESRI sources need some additional meta data to be able to run.
This defines an object to pass options into pyesridump
Ref: https://github.com/openaddresses/pyesridump/pull/38
cc/ @migurski @iandees

Would it make sense to generalize this to "extra args" that just get passed in to the cacher? 🤔

What do each of the parts do? The documentation is slightly thin, and I’m wondering about the boolean flag. Also, would it be possible to rename the type property? The word is used a few other ways in our sources and in https://github.com/openaddresses/openaddresses-ops/issues/16 I’ve proposed that we try to avoid it since it’s so overloaded in meaning.

Closing as stale


Drop support for python 3.6

Due to conflicts in dependencies, I think it is best to drop support for python 3.6. We continue to officially support python 3.7 and 3.8.

Codecov Report

Merging #82 (83a9971) into main (02d27d6) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #82   +/-   ##
=======================================
  Coverage   86.43%   86.43%
=======================================
  Files          54       54
  Lines        1489     1489
=======================================
  Hits         1287     1287
  Misses        202      202

Flag
Coverage Δ

cpu
86.43% <ø> (ø)

pytest
86.43% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Continue to review full report at Codecov.

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


Can I just skip steps 18 & 19?

steps 18 and 19 of what part?

Part 2.

When you have booted, change your theme to anything else, then change it back to remove the old menuhax version
Reinstall menuhax using browserhax and the HomeBrew Launcher (you do not need to reconfigure, just press install in menuhax_manager)

you can probably skip menuhax install, if it's already working for you on 9.2 now.

I've never had menuhax still can skip?

you probably shouldn't skip these (or any) steps.

Ok but why won't browserhax work for me on firmware 9.2?

if the issue is it keeps crashing,
try picking your version at http://smealum.github.io/3ds/#otherapp and download ropbin. place it at the root of the SD and rename it to browserhax_hblauncher_ropbin_payload.bin.

It doesn't crash it won't do nothing when I go to the link also I got nothing of browserhax on my sd card.

What do I do I need browerhax to complete Part 2.

Old3DS? there's a slider you probably need to tap...

What slider? What do you mean?

if you're using Old3DS there is a slider on the page you need to tap. zoom in, and tap the very right edge of it.

It won't let me install menuhax

.......and what kind of error do you get?

It says to verify multiple things.

It failed to get the body size of the body-filepath

The error code is 0x00000002

try getting a new menuhax_manager, since it can't seem to find the right file...
https://github.com/yellows8/3ds_homemenuhax/releases

Do I put it in the root or the 3ds folder?

place menuhax_manager in "3ds", replacing the older one.

ok

Done and thanks


ghactions: Misc cleanups

The main goal is to have win-sshproxy and gvproxy build with -Hwindowsgui as part of our build artifacts.
This makes them easier to include in our releases, and to provide them for use by podman.

/lgtm


Allow enabling PersistentKeepalive for wireguard enabled setup

I'm observing an issue with connectivity (on internal wireguard IPs 192.168.x.x) from nodes on public network to node, which is inside private cloud / behind cloud provider firewall. The issue disappears immediately after I ping those nodes from the affected node inside private cloud (pings in the other direction get unstuck). The connectivity works as long as there is some traffic sent in that direction from time to time.
From what I managed to find about wireguard, this seems to be the issue of some firewall / networking gear blocking up inactive routes and could be solved by using PersistentKeepalive feature.
Expected Behavior
Connectivity between nodes and pods persists even after periods of no traffic between given pair of nodes and direction.
Current Behavior
After a few hours of no traffic from node1 to node2 the packets from node2 to node1 stop being routable. The problem is fixed immediately after any packet is sent from node1 to node2.
Note that the first ping from node1 to node2 has higher latency:
ING <IP_ADDRESS> (<IP_ADDRESS>) 56(84) bytes of data.
64 bytes from <IP_ADDRESS>: icmp_seq=1 ttl=64 time=41.1 ms
64 bytes from <IP_ADDRESS>: icmp_seq=2 ttl=64 time=19.8 ms
64 bytes from <IP_ADDRESS>: icmp_seq=3 ttl=64 time=20.0 ms

as I suppose it is triggering the firewall to evaluate and re-open the route.
Possible Solution
I suspect wireguard's persistent keepalives might solve the issue. According to documentation this feature may be specified by adding the PersistentKeepalive = field to a peer in the configuration file, or setting persistent-keepalive at the command line.
I would like my calico setup to have this setting, I suppose it needs a new config flag to be added.
Steps to Reproduce (for bugs)

create node1 on public vps
create node2 on private cloud vps (in my case oracle cloud)
connect them into calico node-to-node mesh, but without any workload that would send traffic from node2 to node1
after few hours observe that you can't send traffic from pods on node1 to pods in node2 (or even ping the node wireguard internal ip)

Context
Right now pinging internal ips of other nodes fixes the issue and keeping e.g. webpage open that uses node2->node1 route keeps it going, after I close the page the problem will appear soon.
Your Environment

Calico version calico/node:v3.21.1
Orchestrator version (e.g. kubernetes, mesos, rkt): k3s
Operating System and version: 5.13.0-22-generic Ubuntu 21.10 kubelet version v1.22.2+k3s2

The problem I had seems to be caused by my firewall rules that rejected NEW connections on UDP port 51820 (while accepting packets for connections in state RELATED,ESTABLISHED). While keep alive might paper over this problem, updating firewall works for me.
As for the feature itself I suppose it might still be useful in some settings, so I'm not closing this issue so it could be used to track it.

pinging @petercork re. this wireguard feature request

@petercork are there any updates available on this?


Better indication locations for used edits/make inputs

Make it clearer to the user where edits should and should not be made

"Would it be possible to consolidate the sections where users need to modify (credentials, define node names, projects, and time frames, and save data ) towards maybe the bottom of the code? I imagined the process of grabbing data, and if I wanted to adjust what data to grab and how to save it, I would need to scroll up and down repeatedly. Consolidating these sections could enhance usability and efficiency."


Handle max winrm requests

The WinRM gem currently assumes that a Windows server allows 1500
operations per connection, and resets the connection just before hitting
the limit.
Unfortunately, this limit is configurable and a WMI error may be returned
by any operation.  Issue /WinRb/WinRM#197
tracks this problem.  The gem owner will eventually fix this issue by watching
for the error and simply resetting the connection when it occurs, but he
won't be doing so until version 2 of the gem - which is a while off.
We are propagating the fix up a level to the MiqWinRM wrapper class here.
When the error is returned either while running a command_executor or an elevated_runner
we do the right thing and retry the last command issued.
@djberg96 @roliveri @Fryguy @jrafanie @chessbyte please review, comment, and merge when
appropriate.  Thanks much.

Wow some git barfiness.  I have fixed the above rubocop issue and re-pushed.

@djberg96 updated based on your comments.  Please review when able.
@roliveri @Fryguy @chessbyte same if possible.  Thanks all.


Finish quidel geo util refactor

Description
For some reason quidel_covidtest was refactored but quidel wasn't finished. Basically just copied the changes from https://github.com/cmu-delphi/covidcast-indicators/commit/b39d55f58d14389d6aadc3e2571f125bd13d82a8
Changelog
Itemize code/test/documentation changes and files added/removed.

Update geo_map to use geo utils by taking existing code from quidel_covidtest
Change function calls to match new signature
Fix tests

Fixes

Fixes #(issue)

@chinandrew I got these for linting. No big problems.
************* Module delphi_quidel.run
delphi_quidel/run.py:7:0: W0611: Unused join imported from os.path (unused-import)
delphi_quidel/run.py:9:0: W0611: Unused pandas imported as pd (unused-import)
************* Module delphi_quidel.pull
delphi_quidel/pull.py:65:0: C0301: Line too long (102/100) (line-too-long)
delphi_quidel/pull.py:314:0: C0301: Line too long (115/100) (line-too-long)
delphi_quidel/pull.py:405:0: C0301: Line too long (117/100) (line-too-long)
************* Module delphi_quidel.data_tools
delphi_quidel/data_tools.py:9:0: C0303: Trailing whitespace (trailing-whitespace)
delphi_quidel/data_tools.py:67:0: C0301: Line too long (109/100) (line-too-long)
delphi_quidel/data_tools.py:122:0: C0301: Line too long (112/100) (line-too-long)
delphi_quidel/data_tools.py:175:0: C0301: Line too long (105/100) (line-too-long)
delphi_quidel/data_tools.py:310:0: C0301: Line too long (102/100) (line-too-long)

@chinandrew I got these for linting. No big problems.
************* Module delphi_quidel.run
delphi_quidel/run.py:7:0: W0611: Unused join imported from os.path (unused-import)
delphi_quidel/run.py:9:0: W0611: Unused pandas imported as pd (unused-import)
************* Module delphi_quidel.pull
delphi_quidel/pull.py:65:0: C0301: Line too long (102/100) (line-too-long)
delphi_quidel/pull.py:314:0: C0301: Line too long (115/100) (line-too-long)
delphi_quidel/pull.py:405:0: C0301: Line too long (117/100) (line-too-long)
************* Module delphi_quidel.data_tools
delphi_quidel/data_tools.py:9:0: C0303: Trailing whitespace (trailing-whitespace)
delphi_quidel/data_tools.py:67:0: C0301: Line too long (109/100) (line-too-long)
delphi_quidel/data_tools.py:122:0: C0301: Line too long (112/100) (line-too-long)
delphi_quidel/data_tools.py:175:0: C0301: Line too long (105/100) (line-too-long)
delphi_quidel/data_tools.py:310:0: C0301: Line too long (102/100) (line-too-long)

@krivard informed me that the run-quidel branch already has these changes and just isn't in main yet, so I guess this may not be needed?

@krivard informed me that the run-quidel branch already has these changes and just isn't in main yet, so I guess this may not be needed?

@chinandrew Oh, yes. I have finished the geo util refactor in run-quidel branch. Didn't realize that it is not in the main.

@chinandrew Oh, yes. I have finished the geo util refactor in run-quidel branch. Didn't realize that it is not in the main.

run-quidel has the merged flu+covid quidel pipeline, which has not been deployed, and iirc is blocked on deletion support since it will also remove a bunch of regions from the historical data record

run-quidel has the merged flu+covid quidel pipeline, which has not been deployed, and iirc is blocked on deletion support since it will also remove a bunch of regions from the historical data record

is run-quidel what's currently deployed?

is run-quidel what's currently deployed?

@chinandrew quidel_covidtest is the one that is deployed which is for covidtest only. run-quidel is for both covid test and flu test

@chinandrew quidel_covidtest is the one that is deployed which is for covidtest only. run-quidel is for both covid test and flu test

ah, right. in that case I think this PR can be closed and we'll just figure out the run-quidel issue

ah, right. in that case I think this PR can be closed and we'll just figure out the run-quidel issue


Remove wireguard-tools from wireguard and mark it as depending on wir…

Make wireguard depend on wireguard-tools
Remove wireguard-tools from wireguard
Make wireguard-tools no longer conflict with wireguard

Poked around at this a bit. Keep in mind I have no direct wireguard experience.
First thing: before installing the packages on this branch I installed wireguard and wireguard-tools from the testing branch.
reMarkable: ~/ opkg install wireguard
Installing wireguard (1.0.20210219-3) to root...
Downloading https://toltec-dev.org/testing/rmall/wireguard_1.0.20210219-3_rmall.ipk
Configuring wireguard.
reMarkable: ~/ opkg install wireguard-tools
Installing wireguard-tools (1.0.20210914-2) to root...
Downloading https://bin.entware.net/armv7sf-k3.2/wireguard-tools_1.0.20210914-2_armv7-3.2.ipk
Installing libnl-tiny (2023-07-27-bc92a280-1) to root...
Downloading https://bin.entware.net/armv7sf-k3.2/libnl-tiny_2023-07-27-bc92a280-1_armv7-3.2.ipk
Installing ip-full (4.4.0-10a) to root...
Downloading https://bin.entware.net/armv7sf-k3.2/ip-full_4.4.0-10a_armv7-3.2.ipk
Configuring libnl-tiny.
Configuring ip-full.
Configuring wireguard-tools.

Note that wireguard comes via toltec, but wireguard-tools comes via the entware repo. And then
opkg install wireguard-tools_1.0.20210914-2_rmall.ipk
Package wireguard-tools (1.0.20210914-2) installed in root is up to date.

Because the upstream wireguard has the exact same version number presumably. Removing it and installing the toltec version worked fine. But it did make me wonder whether we're giving ourselves trouble shadowing a package like this... maybe we should arrange things so the toltec versions are always preferred?
Second thing:
reMarkable: ~/toltec-test/wireguard/ opkg files wireguard
Package wireguard (1.0.20210219-4) is installed on root and has the following files:
/lib/modules/4.9.84-zero-gravitas/kernel/net/ipv6/ip6_udp_tunnel.ko
/lib/modules/4.9.84-zero-gravitas/kernel/net/ipv4/udp_tunnel.ko
/lib/modules/4.9.84-zero-gravitas/extra/wireguard.ko
/lib/modules/4.14.78/kernel/net/ipv4/udp_tunnel.ko
/lib/modules/4.14.78/extra/wireguard.ko
/lib/modules/4.14.78/kernel/net/ipv6/ip6_udp_tunnel.ko
reMarkable: ~/toltec-test/wireguard/ modprobe wireguard
modprobe: FATAL: Module wireguard not found in directory /lib/modules/5.4.70-v1.1.5-rm11x
reMarkable: ~/toltec-test/wireguard/ ls /lib/modules/
4.14.78               4.9.84-zero-gravitas  5.4.70-v1.1.5-rm11x

Do we need to build for a third kernel?

This might help explain why things aren't working as I expected when I was testing the stable merge. We either need to drop the package, or add an epoch to the version number to make sure it always installs ours. The priority on the rm2 arch should be enough to also force ours to be installed, but apparently not so.
As for wireguard not working properly in 2.15.1, this is a known issue (#506) which is why #759 is dropping the package for 3.x support. You can also find a PR that has been open for over 12 months now (#651), updating the wireguard package as well as the kernel version it builds against to 5.4.70.

reMarkable: ~/toltec-test/ opkg install wireguard_1.0.20210219-4_rmall.ipk
Upgrading wireguard on root from 1.0.20210219-3 to 1.0.20210219-4...
Wireguard has been upgraded.
The old kernel module will remain loaded until you reboot, or you can
attempt to manually remove it by running "modprobe -r wireguard".
Removing obsolete file /usr/bin/wg-quick.
Removing obsolete file /lib/systemd/system/wg-quick.target.
Removing obsolete file /usr/bin/wg.
Removing obsolete file /usr/share/man/man8/wg.8.
Removing obsolete file /usr/share/man/man8/wg-quick.8.
Removing obsolete file<EMAIL_ADDRESS>Configuring wireguard.

Packaging looks good to me!


Replace use of set-output command with env file

Fixes #461

Confirmed clean Gradle builds in https://github.com/detekt/detekt/pull/5467


when I run the function breast_cancer.py, I got this error. please can anyone help me to solve it urgently?

Environment

Qiskit Machine Learning version:
Python version:
Operating system:

What is happening?

when I run the function breast_cancer.py, I got this error. please can anyone help me to solve it urgently?
 in (.0)
40     training_input = {
41         key: (sample_train[label_train == k, :])[:training_size]
---> 42         for k, key in enumerate(class_labels)
43     }
44     test_input = {
TypeError: slice indices must be integers or None or have an index method
How can we reproduce the issue?
run the function breast_cancer.py, you will get this error. please can anyone help me to solve it urgently?
 in (.0)
40     training_input = {
41         key: (sample_train[label_train == k, :])[:training_size]
---> 42         for k, key in enumerate(class_labels)
43     }
44     test_input = {
TypeError: slice indices must be integers or None or have an index method
What should happen?
brast_canser.py should be run and generate the train and test dataset
Any suggestions?
No response

What you posted is not a script to reproduce the issue, unfortunately. The script breast_cancer.py is not intended to be run directly as you proposed. Can you please post a snippet to reproduce the issue?
These lines work perfectly well:
from qiskit_machine_learning.datasets import breast_cancer

ds = breast_cancer(100, 20, 4)
print(ds)

Yes, I got it. You are right. I put the values of training size and testing
size as a ratio. Thank you very much. Please, is there a version of quantum
gan that uses breast_cancer,py as a dataset to reproduce it??
Thanks a million
Now, I will try to run qgan.. is it run
On Tue, 16 Aug 2022 at 2:17 PM Anton Dekusar @.***>
wrote:

What you posted is not a script to reproduce the issue, unfortunately. The
script breast_cancer.py is not intended to be run directly as you
proposed. Can you please post a snippet to reproduce the issue?
These lines work perfectly well:
from qiskit_machine_learning.datasets import breast_cancer
ds = breast_cancer(100, 20, 4)print(ds)
—
Reply to this email directly, view it on GitHub
https://github.com/Qiskit/qiskit-machine-learning/issues/454#issuecomment-1216557001,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOE5CA6G6UOMCMTPM44Y6HDVZOBDXANCNFSM56VKWC6A
.
You are receiving this because you authored the thread.Message ID:
@.***>

No, I'm not aware of a QGAN example on the breast cancer dataset.
I'm closing this issue as resolved. Feel free re-open if the issue persists.


Server disconnected

Describe the bug
Getting server disconnected around 70-80% of the times I try to use a prompt.
To Reproduce
Steps to reproduce the behavior:

Use prompt
See error

Expected behavior
It should not disconnect
Screenshots
If applicable, add screenshots to help explain your problem.
Environment

Operating System: [MacOS with M1 MAX 64 GB
Using Ollama
Continue Version: [0.0.352]

Console logs
Traceback (most recent call last):

  File "continuedev/src/continuedev/core/autopilot.py", line 368, in _run_singular_step
    observation = await step(self.continue_sdk)
                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

  File "continuedev/src/continuedev/core/main.py", line 359, in __call__
    return await self.run(sdk)
           ^^^^^^^^^^^^^^^^^^^

  File "continuedev/src/continuedev/plugins/steps/chat.py", line 85, in run
    async for chunk in generator:

  File "continuedev/src/continuedev/libs/llm/ollama.py", line 158, in stream_chat
    async with self._client_session.post(

  File "aiohttp/client.py", line 1141, in __aenter__

  File "aiohttp/client.py", line 560, in _request

  File "aiohttp/client_reqrep.py", line 899, in start

  File "aiohttp/streams.py", line 616, in read

  File "asyncio/futures.py", line 287, in __await__

  File "asyncio/tasks.py", line 339, in __wakeup

  File "asyncio/futures.py", line 203, in result

aiohttp.client_exceptions.ServerDisconnectedError: Server disconnected

Additional context
Nothing to add

Could you share the contents of the Ollama class in your config.py?

from continuedev.src.continuedev.core.models import Models
from continuedev.src.continuedev.core.config import CustomCommand, SlashCommand, ContinueConfig
from continuedev.src.continuedev.plugins.context_providers.github import GitHubIssuesContextProvider
from continuedev.src.continuedev.libs.llm.maybe_proxy_openai import MaybeProxyOpenAI
from continuedev.src.continuedev.plugins.steps.open_config import OpenConfigStep
from continuedev.src.continuedev.plugins.steps.clear_history import ClearHistoryStep
from continuedev.src.continuedev.plugins.steps.feedback import FeedbackStep
from continuedev.src.continuedev.plugins.steps.comment_code import CommentCodeStep
from continuedev.src.continuedev.plugins.steps.share_session import ShareSessionStep
from continuedev.src.continuedev.plugins.steps.main import EditHighlightedCodeStep
from continuedev.src.continuedev.plugins.context_providers.search import SearchContextProvider
from continuedev.src.continuedev.plugins.context_providers.diff import DiffContextProvider
from continuedev.src.continuedev.plugins.context_providers.url import URLContextProvider
from continuedev.src.continuedev.plugins.context_providers.terminal import TerminalContextProvider
from continuedev.src.continuedev.libs.llm.ollama import Ollama
config = ContinueConfig(
allow_anonymous_telemetry=False,
models=Models(
default=Ollama(model="wizardcoder:34b-python")
),
system_message="",
temperature=0.5,
custom_commands=[
CustomCommand(
name="test",
description="Write unit tests for the higlighted code",
prompt="Write a comprehensive set of unit tests for the selected code. It should setup, run tests that check for correctness including important edge cases, and teardown. Ensure that the tests are complete and sophisticated. Give the tests just as chat output, don't edit any file.",
)
],
slash_commands=[
SlashCommand(
name="edit",
description="Edit code in the current file or the highlighted code",
step=EditHighlightedCodeStep,
),
SlashCommand(
name="config",
description="Customize Continue - slash commands, LLMs, system message, etc.",
step=OpenConfigStep,
),
SlashCommand(
name="comment",
description="Write comments for the current file or highlighted code",
step=CommentCodeStep,
),
SlashCommand(
name="feedback",
description="Send feedback to improve Continue",
step=FeedbackStep,
),
SlashCommand(
name="clear",
description="Clear step history",
step=ClearHistoryStep,
),
SlashCommand(
name="share",
description="Download and share the session transcript",
step=ShareSessionStep,
)
],
context_providers=[
# GitHubIssuesContextProvider(
#     repo_name="/",
#     auth_token=""
# ),
SearchContextProvider(),
DiffContextProvider(),
URLContextProvider(
preset_urls = [
# Add any common urls you reference here so they appear in autocomplete
]
),
TerminalContextProvider(),
],
)

Thanks. I'll try this exact setup on my own machine to see if I can reproduce. The first thing I would check is that you've pulled the model you are using, but I'm quite confident you already know to do this. I'll give an update soon

ollama list
NAME                  	ID          	SIZE  	MODIFIED
codellama:latest      	36893bf9bc7f	3.8 GB	4 hours ago
wizardcoder:34b-python	1064f08e84a4	19 GB 	About an hour ago

From one of the ollama founders: "We've seen some issues with large prompts with the 34B models – looking into this - sorry!!"
I'm wondering whether the first message you send (when chat history is empty, or right after loading ollama) might work, while later messages don't because of the built up context. Unfortunately I don't have the hardware to test this on my own with a 34b

From one of the ollama founders, it sounds like they are having issues with 34b models with long context inputs.

This is probably true. I see this aswell. Yeah I'll try a smaller model. Any special you recommend?

I've been seeing really great results from codellama:13b-instruct, with the instruct part being crucial. Even 7b is decent

I'm going to close this issue since it seems mostly resolved, but you're feel free to reopen if something is still wrong. Let me know if you have any more questions about models to use!


Add ICU

Out of a bunch of libraries providing internationalization support, this is probably the most widely used and referenced. It would be nice to have ICU available via Hunter.
http://site.icu-project.org/download

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/11722611-add-icu?utm_campaign=plugin&utm_content=tracker%2F1032790&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F1032790&utm_medium=issues&utm_source=github).

Thanks for request. Also I've made some hacking earlier but haven't finished it: https://github.com/hunter-packages/icu

FYI, there is an ICU ticket for adding CMake support:
http://bugs.icu-project.org/trac/ticket/7747
I would also like to see ICU in Hunter.

As you can see, that ticket was created 7 years ago, so it seems to be extermely unlikely that ICU project will change their build system. I think it would be much more productive to support building of ICU via autotools (runConfigureICU), and support MSVC with its MSYS/MSVC platform option (like done e.g. in [1]), or by using devenv & msbuild (like done in [2])
[1] https://github.com/bincrafters/conan-icu/blob/testing/59.1/conanfile.py#L109
[2] https://github.com/Vitallium/conan-icu/blob/master/conanfile.py#L36

Version 55.1 added to Hunter, available since v0.20.40:

https://github.com/ruslo/hunter/releases/tag/v0.20.40

Thanks for adding ICU to Hunter. :)
Why such an old version?  ICU 55.1 is 3 years old.  ICU 61.1 is the latest version.

Why such an old version? ICU 55.1 is 3 years old

This version was needed by the project that use ICU.

ICU 61.1 is the latest version

If you want I can create hunter-61.1 branch and you can send pull request with CMake ported from 55.1. In this case please start discussion here:

https://github.com/hunter-packages/icu

Please see:
ICU build files for CMake build tools
In the ICU build files for CMake build tools are released most configure
options, compile and linker flags and others from the original ICU files:
 'configure.ac', '*/*.m4', '*/Makefile.in', 'icudefs.mk.in', 'config/mh-*',
 'data/pkgdataMakefile.in', 'data/makedata.mak', 'allinone/allinone.sln',
 'allinone/Build.Windows*.ProjectConfiguration.props', '*/*.vcxproj'

Unrealized options are marked with 'TODO' in CMake files.
Extras, samples and test building is not released.
Layoutex building is partially implemented, need to study the work with
the library icu-le-hb without pkg-config, only with CMake.
ICU data building from scratch ('files' mode) is not released.
Now ICU_DATA_PACKAGING can be 'archive', 'library', 'static' and 'auto'.
For iOS, Android and Microsoft Store (Windows Store) platforms is always 'auto'.
Building and sample running are tested on Ubuntu 18.04 with GCC 7.3.0 and
Clang 6.0.0. Only building is tested with Android NDK 17.1.4828580.
In these configurations static and shared buildings are tested.
For building with CMake copy the files to ICU source tree and just run:
cd ./icu
mkdir ./build
cd ./build
cmake ../ \
 -DICU_ENABLE_EXTRAS=OFF \
 -DICU_ENABLE_SAMPLES=OFF \
 -DICU_ENABLE_TESTS=OFF \
 -DBUILD_SHARED_LIBS=ON \
 -DCMAKE_BUILD_TYPE=Release \
 -DCMAKE_INSTALL_PREFIX=inst
cmake --build .

For more info see file 'README_CMakeLists.txt'
The main idea belongs to Ruslan Baratov with Hunter package manager. Thanks.
See file 'LICENSE_CMakeLists' for license information.

Thank you!  This looks like a great starting point.
I am working on a standalone data build script in Python for ICU.  Right now the data build configurations are part of the Makefile, and that means they are not as portable and not as easy to configure, so moving them to a script gives us more flexibility.  It also should mean that it is easier to invoke the data build from other build systems like CMake.

There is also some discussion here:
https://unicode-org.atlassian.net/browse/ICU-7747


Feat learning units precondition

Pull request to facilitate review

How do the changes affect the overall performance. Have you conducted any tests?

Yes, I tested the old use case that we had.
{
"goal": ["2504"],
"optimalSolution": true
}
The precondition increases the running time by approximately 1.5 seconds. But, when I do a quick test with the new merged approach (filtering the learning units "inScopeLearningUnits") it took around 35ms with the precondition


Bugfix: leak resource if pod is force deleted

Fix https://github.com/virtual-kubelet/tensile-kube/issues/49

LGTM