Messages by address service

Is your feature request related to a problem? Please describe.
Currently Etherscan is the only solution to lookup transactions by address.
Describe the solution you'd like
Create a service that allows looking up mailchain messages by address.
Describe alternatives you've considered

Proxy calls to etherscan
Custom solution for mailchain

Additional context
ref #118

@robdefeo Dupe of #161 ?

@tboeckmann #161 is about providing a better user experience by allowing user to main an address book and use friendly names. This #126 is to provide an address index for ethereum which does not exist, currently mailchain relies on etherscan for this.

Sorry, I meant Address index service #251

@tboeckmann yes. I will close this in favor of #251. Good catch


Serious QA issues: we've merged code that doesn't even compile

Missing comma:
https://github.com/kubernetes-sigs/kpng/blob/d8f49840f6044831626792a47aadd5e5fe2209d4/client/serviceevents/service-events_test.go#L52
Also, unit tests are not passing. Also, gofmt.
I think it is the minimum we can require before merging something. We should have those checks in github's pre-merge conditions.
/good-first-issue

@mcluseau I try to fix the environment. But there are still some unit test cannot pass

HI , @mcluseau . There is the https://github.com/kubernetes-sigs/kpng/pull/251 to fix the issue . Would you please review it .


Use ESM, and update rdf-ext

Hello @bergos,
This pull request updates the rdf-ext lib and ports the code to ESM
I moved this one to ESM because it is a dependency of https://github.com/zazuko/trifid-handler-fetch, which is being ported to ESM using "rdf-ext": "^2.0.1"

Thanks for the observation!

I've changed the documentation.
I don't have write access to merge...


Toggling mute without hitching in UE5.3

Hi! Thank you for such an awesome plugin.
I want to implement push-to-talk functionality and so want to frequently mute and unmute a recording.
I initially used Start Capture and Stop Capture, but that caused hitching as described in https://github.com/gtreshchev/RuntimeSpeechRecognizer/wiki/6.-Minimizing-freezes#capturable-sound-wave.
Following that, I tried using Toggle Mute to improve performance, but the hitching persists. Looking at the source, it looks like for UE5.3, this is aliased back to Start/Stop Capture:
https://github.com/gtreshchev/RuntimeAudioImporter/blob/main/Source/RuntimeAudioImporter/Private/Sound/CapturableSoundWave.cpp#L172-L184
Is there any recommended way to do this for UE5.3+?

Hi, thanks for the feedback :)
The ToggleMute function used to work in earlier engine versions, but starting from version 5.3, it no longer functions correctly and leads to crashes, especially on Windows (I assume this issue may occur on other platforms as well). To avoid crashes and make sure it always works correctly, I modified it to essentially be implemented as the StartCapture<->EndCapture starting from version 5.3.
For now, I'm not sure if it's possible to solve this in-place, so unfortunately it's on hold for now.

Hi @gtreshchev
I just found the ToggleMute problem which was leaded the crashes.
It seems crash in windows only. So I modified the prefix for the other platform can still used it.
#70
Problebly we need to wait the Epic fix this problem.
I tried to modify the ToggleMute function to not use StopStream and StartStream.
If I did it I will commit my work.

@gtreshchev Sorry my amatuer response before.
I rellay appriceate your project, it easy to use and reliablity. Thank you so much.
But the ToggleMute in 5.3 is rellay annoying me.
I finally found the bug, and contrubite the code to EpicTeam.
If you had be the member of EpicGame , you can see it.
https://github.com/EpicGames/UnrealEngine/pull/12092
Briefly, they forgot to set the CaptureThread to nullptr when the thread stop.
When you call StartStream again will cause the check been Error.
So this issus only effect on Windows.
#70
If you have time you can check by yourself.
Thanks your wonderful pluing again.


Uncaught TypeError: _statusBarItem2.default is not a function

[Enter steps to reproduce below:]

...
...

Atom Version: 1.5.3
System: Mac OS X 10.10.5
Thrown From: line-ending-selector package, v0.3.0
Stack Trace
Uncaught TypeError: _statusBarItem2.default is not a function
At /Users/xiaoguo/Downloads/Atom.app/Contents/Resources/app.asar/node_modules/line-ending-selector/lib/main.js:85

TypeError: _statusBarItem2.default is not a function
    at Object.consumeStatusBar (/Users/xiaoguo/Downloads/Atom.app/Contents/Resources/app.asar/node_modules/line-ending-selector/lib/main.js:85:23)
    at Provider.module.exports.Provider.provide (/Users/xiaoguo/Downloads/Atom.app/Contents/Resources/app.asar/node_modules/service-hub/lib/provider.js:30:52)
    at /Users/xiaoguo/Downloads/Atom.app/Contents/Resources/app.asar/node_modules/service-hub/lib/service-hub.js:55:26
    at doNTCallback0 (node.js:419:9)
    at process._tickCallback (node.js:348:13)

Commands

Config
{}

Installed Packages
# User
No installed packages

# Dev
No dev packages

Also have this problem right after I start atom.
This also seems do disable some of my other packages which makes atom completely useless for me. I tried to build atom from master brnach as well as last release.
Disabling the package hides the error message, but some of my other packages (including project manager and phpunit) still won't work.
Atom Version: 1.7.0-dev-2bdf4be
System: Linux Mint
Thrown From: line-ending-selector package, v0.3.1
Stack Trace
Uncaught TypeError: _statusBarItem2.default is not a function
At /usr/local/share/atom/resources/app.asar/node_modules/line-ending-selector/lib/main.js:73

TypeError: _statusBarItem2.default is not a function
    at Object.consumeStatusBar (/usr/local/share/atom/resources/app.asar/node_modules/line-ending-selector/lib/main.js:73:23)
    at Provider.module.exports.Provider.provide (/usr/local/share/atom/resources/app.asar/node_modules/service-hub/lib/provider.js:30:52)
    at /usr/local/share/atom/resources/app.asar/node_modules/service-hub/lib/service-hub.js:55:26
    at doNTCallback0 (node.js:443:9)
    at process._tickCallback (node.js:372:13)

Commands

Config
{
  "core": {
    "disabledPackages": [
      "autosave",
      "welcome",
      "package-generator",
      "open-on-github",
      "bookmarks",
      "keyboard-localization"
    ],
    "ignoredNames": [
      ".git",
      ".coverage",
      "tags",
      "composer.*",
      ".tags_swap",
      "tmp"
    ],
    "packagesWithKeymapsDisabled": [
      "atom-beautify",
      "tool-bar",
      "linter",
      "atom-dark-ui",
      "highlight-line",
      "last-cursor-position",
      "phpunit"
    ],
    "projectHome": "/home/user/dev",
    "themes": [
      "atom-dark-ui",
      "afterglow-like"
    ]
  }
}

Installed Packages
# User
afterglow-like, v0.2.1
color-picker, v2.1.1
docblockr, v0.7.3
file-icons, v1.6.17
flex-tool-bar, v0.7.3
highlight-line, v0.11.1
last-cursor-position, v0.9.0
linter, v1.11.3
linter-php, v1.2.0
php-cs-fixer, v2.5.6
phpunit, v1.2.0
pigments, v0.24.2
project-manager, v2.7.6
sync-settings, v0.6.0
tool-bar, v0.2.1
tree-view-git-status, v0.2.3

# Dev
No dev packages

Can you reproduce the problem in Safe Mode?
To launch Safe Mode:

Completely exit all instances of Atom
Launch Atom with the command atom --safe

After running script/clean and rebuild the latest version via git checkout $(git describe --tags git rev-list --tags --max-count=1) the problem no longer occurs.
I rebuild atom from master (after running script/clean again) and it still works.

After building from latest master I've got the problem again. I tried launching atom in safe mode, but the problem persists.
After checking out latest release (1.7.0 dev 579b6b7) it works again.

Dupe of https://github.com/atom/line-ending-selector/issues/19


Fix an issue when passphrase is canceled

Cancel the window asking passphrase crash the app because OpenPgpSignatureResult signatureResult is null when the decrypt fails.
Issue from commit be18d06afd0db49b4c111f5091ca3d12f3ace357

@dschuermann Can you please have a look at this?

Fixed by https://github.com/k9mail/k-9/commit/5d2de3b1938e981b60dd5180349ac6c2cf6a796c


Add calibration parameters for multiple batteries

Describe problem solved by the proposed pull request
Support for multiple batteries was improved in #12034 , but there is still the issue that different batteries all use the same calibration parameters.
Test data / coverage
On Pixhawk 4, multiple batteries with different levels of charge and numbers of cells were tested.
This PR makes changes that affect all different boards, so more testing should be done on different hardware.
Describe your preferred solution
Improved the Battery library by adding the ability to instantiate different batteries with different sets of parameters. Split power reading in sensors module into a separate class for readability.
Additional context
In the near future, support for digital power meters will be expanded, continuing the work done in #11755. This refactoring should make supporting this new source of battery data, as well as any future new sources, easier.

@feemi Follow-up from our discussion in #12034: This PR will hopefully address the issues you were having before. Would you mind testing it with your setup?

@ItsTimmy This will have a docs impact and possibly quite a complex QGC UI change. Please ping me when you think it is time to engage re docs. The main doc to change would be : http://docs.px4.io/master/en/config/battery.html
And presumably we may need to change the failsafe behaviour too: http://docs.px4.io/master/en/config/safety.html#low-battery-failsafe

This is looking good, but I think we should briefly take a step back and try to sketch out a rough overall design that factors in all the current requirements.

different battery types (analog bricks, digital bricks, smart batteries)
- battery_status message
multiple instances
overall system estimate (reporting, failsafe handling, etc)
system power architecture

if you have multiple batteries what's the overall percentage?

refactoring to cleanup the mess scattered across each platform adc and the sensors module

@ItsTimmy @davids5 let's schedule a call.

Related https://github.com/PX4/Firmware/issues/12033

Even though we don't have the multi-battery requirements worked out completely, I think this PR is still ready for review and merge. It does not affect the safety-critical decisions like low-battery failsafe behavior and reporting of overall system battery percentage. These are still open issues, but they can be addressed in a separate PR.

@ItsTimmy @julianoes @dagar -  I want to ensure the number of bricks logic is well understood from a HW perspective across platforms.  I still feel we need to have that meeting @dagar has arranged.

@dagar should we merge this or wait for 1.10?

@dagar @julianoes I think this is still ready to merge. It is technically consistent with the changes in mavlink/mavlink#1182, but there is a lot of work still to be done concerning configuration. In this PR, the mapping of physical battery to battery "slot" (Discussed in that Mavlink PR) is based solely on which power connector the power module is connected to.
In the future, as more power modules are supported (Such as the INA226 in #12673), we will need to decide how we map physical batteries to battery slots. But as that is outside the scope of this particular PR, I propose we address it in another PR.

@ItsTimmy can you please rebase this branch?

It was overflowing flash on px4_fmu-v5_stackcheck, so I removed some modules from the build. Can you please double check that for me @julianoes ?

Right, so now it's the normal "doesn't fit on fmu-v2".

@dagar what should we do about the flash size for this one?

This has now been rebased to resolve the conflicts with the new battery_status module.

Where does the overall system power architecture fit into this? If I have 2 batteries connected don't I need to know more overall to provide a sensible overall percentage estimate for the system?

You are correct in that there are a lot of open questions about how to handle multiple batteries. If you look in mavlink/mavlink#1182, you can see the ongoing discussion.
This PR does not address this in any way. Because that discussion is not fully resolved (at the time I finished up this PR in July), I chose to keep the same end behavior, but start refactoring things to get ready for more comprehensive support of multiple batteries. To that end, this PR has two goals:

Add support for multiple different calibration values for different batteries. For example, two analog power modules might have slightly different voltage dividers and will need to be independently calibrated
Refactor the battery library in such a way that multiple instances of new types of batteries can be added more easily. In the future we will need to support smart batteries, external batteries coming in over MAVLink, and perhaps others. I have demonstrated this by adding support for I2C digital power modules, in #12673 .

To summarize: This PR does not change the behavior of the power system, other than by adding the option to independently configure different batteries. It was intended to make it easier to add more battery types in the future.

This might need a bit of thought, but it's probably worth moving the parameter migration to the parameter system itself. On import we could catch the old values (by string) and set them in the new parameter.
https://github.com/PX4/Firmware/blob/b943bd72ab20ecab155976d74986926d1c0349ea/src/lib/parameters/parameters.cpp#L1183

@dagar would be good to get this in! It's been a while :smile:.

@hamishwillee As far as I know, no, there is currently no way to do templated parameters, unfortunately.
And as for support in QGC, I am not sure if there is a specific roadmap. There is the open PR mavlink/qgroundcontrol#7575, which addresses displaying the battery readings, but not calibrating separate batteries.

@ItsTimmy FYI, templated param definitions are possible https://github.com/PX4/Firmware/blob/master/src/modules/mavlink/module.yaml#L20 but not templated code. @bkueng is the expert.

@hamishwillee I was not aware of that, thanks for the info! I spoke with Beat, so I now know how to use that feature. Incorporating it into this PR will be a bit tricky though, since some parameters are defined outside of a module (in the battery library). I will look into that though, and consider adding it here.

@ItsTimmy All good with me - I just wanted to make you aware of the option. I have kicked off https://github.com/PX4/Devguide/pull/898 to get the Yaml/multi instance stuff documented.

I have updated this with 3 important differences:

Parameters are now instanced with YAML files
Refactored to decrease code size
Parameter migration has been improved: Old and new parameters are now kept in sync in both directions. If either parameter is changed, the other is immediately updated to reflect this. If the deprecated parameter was changed, then a warning is displayed.

I still have some cleanup and testing to do on this. There are still some relics of the old way this was written.

@dagar @julianoes @bkueng This is ready for review.

I did some more testing on this latest version. The following tests all worked as intended:

Plugged in 2 batteries (with different cell counts) to Pixhawk 4 with analog power module
Calibrated battery 1 with QGC
Calibrated battery 2 manually (using param set)
Set values of all BAT_* parameters and BAT1_* parameters to check that migration worked correctly


have a build pipeline

Provide a script and/or a GitHub action step
But first have a definition of what you want and where you want it

There is already a build pipeline here:
https://github.com/studiorack/studiorack-registry/blob/main/.github/workflows/release.yml
You can view the pipeline runs here:
https://github.com/studiorack/studiorack-registry/actions
The result is deployed to GitHub pages here:
https://github.com/studiorack/studiorack-registry/tree/gh-pages

There is already a build pipeline here: https://github.com/studiorack/studiorack-registry/blob/main/.github/workflows/release.yml
You can view the pipeline runs here: https://github.com/studiorack/studiorack-registry/actions
The result is deployed to GitHub pages here: https://github.com/studiorack/studiorack-registry/tree/gh-pages

im confused, the surge team said my PR was wrong? https://github.com/jatinchowdhury18/AnalogTapeModel/pull/317 is it wrong?


[ci:component:github.com/gardener/etcd-druid:v0.14.2->v0.15.0]

Release Notes:
Added e2e tests to check single member restoration in multi node setup

Updated golang version used to build images to 1.19.2

The decision to add the scale-up annotation to the etcd sts now considers the etcd status if an existing sts is not present

An issue has been fixed that caused the `BackupReady` condition to show `Unknown` when the cluster is newly created.

Removes the redundant closing of snapshotter during initialization.

Updated golang version used to build images to 1.19.2

To avoid race-condition between closing of snapshotter and taking snapshot after defrag, removing the out-of-schedule full snapshot triggered after defragmentation of etcd.

To avoid potential race-condition between go-routines updated `probeEtcd func()` to use shorter timeout.

Always update member peer URL, changed the way scale-up of etcd cluster is identified.

Updated golang version used to build images to 1.18.6

Updated golang version to 1.18

Decreases the likelihood of potential race condition between the go-routines while closing the snapshotter.

[bug-fix] backup-restore does not return error when it fails to update PeerURL of member.

Fix PDB permissions for druid chart.

/approve

/kind enhancement


Add bulkClaim to OneToN to allow saving gas

The API would be a log more beautiful when using the new ABI encoder.
Open questions:

Is this assembly usage the right way to parse the signatures?
With which amount of IOUs should I measure gas? I just used a single one.

Closes #542.

With which amount of IOUs should I measure gas? I just used a single one.

Measure at two points so users can plot a linear function.

make format might fix the CI.


Do not break down rfc2622 prefixes in configuration, but in each module

Is your feature request related to a problem? Please describe.
Currently rfc2622 prefixes are broken down in the configuration, inducing considerable delays.
Describe the solution you'd like
This should be done at the stage of each module (prefix tree compilation).
ATTENTION: In the frontend, we should display the rfc2622-configured prefixes as they are (not broken down visually). Hijack prefix matches etc. can occur as till now.
Describe alternatives you've considered
N/A
Additional context
N/A

Current code with a config like this: 2400:2000::/32^48 breaks the frontend, due to timeout or memory issues.
Smaller aggregates work fine however, like ::/47^48 so anything that can more simply manage the prefixes besides printing the whole list should work better.


Remove dead code: fast_global_localizer.

@wohe does it make sense to keep it?

@pifon2a We do not use it. It was intended as part of public API to allow localizing without running SLAM. If it stays in internal it is not useful.

Ok, let's remove it then.


Example blocks with URLS are truncated after //

This Doc block
/**
     * @description @HttpGet exposes a method to a GET request when the custom REST endpoint is called. A GET request allows us to return
     * data from Salesforce. In this example, we're going to query a list of Accounts that were created and return them to the application that
     * called the endpoint. When creating a response we can use the RestResponse class to specify certain fields of the payload that is
     * sent. We are manually setting the statusCode as 200 for a successful get and 400 on error. In any other case, Salesforce will supply the error code.
     *
     * Note: This method has a false-positive PMD warning. Our Query
     * includes the keyword 'WITH SECURITY_ENFORCED' which prevents this
     * Query from accessing fields and objects that they don't have permission
     * to access. This is a form of inline CRUD/FLS Check.
     *
     * The return statement is atomically serialized and returned in the responseBody.
     * @return RestResponse  A list of Accounts or the exception message
     * @example
     * curl -H "Authorization: Bearer <SessionID>" "https://<Org Base URL>/services/apexrest/IntegrationService"
     */

Results in the following Markdown:
@HttpGet exposes a method to a GET request when the custom REST endpoint is called. A GET request allows us to return data from Salesforce. In this example, we're going to query a list of Accounts that were created and return them to the application that called the endpoint. When creating a response we can use the RestResponse class to specify certain fields of the payload that is sent. We are manually setting the statusCode as 200 for a successful get and 400 on error. In any other case, Salesforce will supply the error code. Note: This method has a false-positive PMD warning. Our Query includes the keyword 'WITH SECURITY_ENFORCED' which prevents this Query from accessing fields and objects that they don't have permission to access. This is a form of inline CRUD/FLS Check. The return statement is atomically serialized and returned in the responseBody.

#### Example
```java
curl -H "Authorization: Bearer <SessionID>" "https:

the // in https:// is being treated as an existing comment and stripped out.

I went ahead and released a patch with the changes I proposed on the PR. Comments are now not being skipped when they are inside a doc block (between /** and */), to account for the aforementioned URL use case but also to allow for comments within an @example block to provide annotations.


avoid parsing error of DOCKER_NOTEBOOK_IMAGES and JUPYTERHUB_IMAGE_SELECTION_NAMES using newlines

Description
When parsing DOCKER_NOTEBOOK_IMAGES and/or JUPYTERHUB_IMAGE_SELECTION_NAMES generated from a similar env.local definition as in the example file:
https://github.com/bird-house/birdhouse-deploy/blob/8218166d5c8c7163293a656930ff85762eff4b60/birdhouse/env.local.example#L266-L280
The script could fail if the \ to make it a continuous string were omitted (therefore, literal \n are then encoded in the string).
Since \n are permitted almost anywhere else (eg: EXTRA_CONF_DIRS, DELAYED_EVAL, OPTIONAL_VARS, etc.), this caused very unintuitive errors.
Now, any spaces can be used transparently.
Python code in the JupyterHub component that use the same DOCKER_NOTEBOOK_IMAGES typically used .split() which handles any spaces in the same way as now done by this script.
Example
Output BEFORE:
. env.local
INFO:     Resolved 'DOCKER_NOTEBOOK_IMAGES=
  pavics/workflow-tests:py39-230601-1-update240116

  pavics/crim-jupyter-eo:0.3.0
  pavics/crim-jupyter-eo:0.4.0
  pavics/crim-jupyter-nlp:0.4.0
  pavics/crim-jupyter-nlp:0.5.0

'

. pavics-jupyter-base/scheduler-jobs/deploy_data_pavics_jupyter.env
DOCKER_NOTEBOOK_IMAGES: [

  pavics/crim-jupyter-eo:0.3.0
  pavics/crim-jupyter-eo:0.4.0
  pavics/crim-jupyter-nlp:0.4.0
  pavics/crim-jupyter-nlp:0.5.0

]
DEPLOY_DATA_JOB_DOCKER_IMAGE [1]:
Error: DEPLOY_DATA_JOB_DOCKER_IMAGE not set

Output AFTER
. env.local
INFO:     Resolved 'DOCKER_NOTEBOOK_IMAGES=
  pavics/workflow-tests:py39-230601-1-update240116

  pavics/crim-jupyter-eo:0.3.0
  pavics/crim-jupyter-eo:0.4.0
  pavics/crim-jupyter-nlp:0.4.0
  pavics/crim-jupyter-nlp:0.5.0

'

. pavics-jupyter-base/scheduler-jobs/deploy_data_pavics_jupyter.env
DOCKER_NOTEBOOK_IMAGES: [pavics/workflow-tests:py39-230601-1-update240116 pavics/crim-jupyter-eo:0.3.0 pavics/crim-jupyter-eo:0.4.0 pavics/crim-jupyter-nlp:0.4.0 pavics/crim-jupyter-nlp:0.5.0 ]
DEPLOY_DATA_JOB_DOCKER_IMAGE [1]: pavics/workflow-tests:py39-230601-1-update240116
DEPLOY_DATA_JOB_DOCKER_IMAGE [2]: pavics/crim-jupyter-eo:0.3.0
DEPLOY_DATA_JOB_DOCKER_IMAGE [3]: pavics/crim-jupyter-eo:0.4.0
DEPLOY_DATA_JOB_DOCKER_IMAGE [4]: pavics/crim-jupyter-nlp:0.4.0
DEPLOY_DATA_JOB_DOCKER_IMAGE [5]: pavics/crim-jupyter-nlp:0.5.0

Additional Information
@mishaschwartz @tlvu
Not sure if you guys are using this script, so adding you for review just in case.

@tlvu
For some reason, I cannot add @mishaschwartz to the PR reviews. Can you check if there is an organization setting missing?

@tlvu For some reason, I cannot add @mishaschwartz to the PR reviewers. Can you check if there is an organization setting missing?

He was not a contributor in this repo.  Added.  He'll have to accept the invite (via email) then we can add him as reviewer.

@fmigneault
Sorry for the late reply, I was too busy with trying to get a new Jupyter env out on our side lately.
So we do not use this script since we have only one image flavor (the multiples images on our Jupyterhub are just future or old version of the same image).
A question: since this code relies on the Scheduler component, which means the built-in notebook autodeploy is also enabled, does this built-in notebook autodeploy and this customized notebook autodeploy co-exist fine with each other?

The variable AUTODEPLOY_EXTRA_SCHEDULER_JOBS seems to be properly set for the scheduler
At the very least, I was receiving daily errors in our Slack channel about DEPLOY_DATA_JOB_JUPYTERHUB_IMAGE_NAME not being set until this PR was applied.


runtime(hare): update hare.vim to match upstream

This is a (long overdue) update of the hare.vim included within Vim to match the current state of the upstream repository. I also modified the username in the MAINTAINERS file as I have migrated to this account from my previous one (@rsaihe).
Outside of the various other changes, this also adds a new haredoc filetype for documentation files inside Hare modules. Per Hare's documentation, these files use the name README. As this is a very common file name, automatic file detection must be opted into using g:filetype_haredoc.
When enabled, a recursive directory search is used to search for Hare source files. If any are found, the current directory is considered to be a Hare module and the README file is given the haredoc filetype. By default, this search recurses into only the first level of subdirectories, but this can be configured with g:haredoc_search_depth.
I did my best to ensure any potential performance impact for the automatic filetype detection remains minimal, especially given README's prevalence as a file name. Hopefully g:filetype_haredoc being opt-in is sufficient, but I'm willing to pursue alternatives if not.

thanks!

Thanks. While merging I noticed a few minor problems so I added the following patch on top:
diff --git a/runtime/doc/ft_hare.txt b/runtime/doc/ft_hare.txt
index 7fe28a13e..937c5e096 100644
--- a/runtime/doc/ft_hare.txt
+++ b/runtime/doc/ft_hare.txt
@@ -43,7 +43,7 @@ The following options are set by default, in accordance with the official Hare
 style guide: >
        setlocal noexpandtab
        setlocal shiftwidth=0
-       setlocal softtabstop=8
+       setlocal softtabstop=0
        setlocal tabstop=8
        setlocal textwidth=80
 <
diff --git a/runtime/ftplugin/hare.vim b/runtime/ftplugin/hare.vim
index ef51c7141..422bb7b4e 100644
--- a/runtime/ftplugin/hare.vim
+++ b/runtime/ftplugin/hare.vim
@@ -31,7 +31,7 @@ setlocal suffixesadd=.ha
 setlocal path-=/usr/include,,
 let &l:path .= ',' .. hare#GetPath() .. ',,'

-let b:undo_ftplugin = 'setl cms< com< flp< fo< inc< inex< isf< pa< sua<'
+let b:undo_ftplugin = 'setl cms< com< flp< fo< inc< inex< isf< pa< sua< mp<'

 " Follow the Hare style guide by default.
 if get(g:, 'hare_recommended_style', 1)

You might want to take that change back upstream.

Oh, oops! Those are both very good finds, thank you!

Should efm< also be added to b:undo_ftplugin? I didn't think to reset the options set with CompilerSet before but I assume that one should also be reset.

Oh yes, that should also be reset. Thanks for checking.


d.ts compile errors

More errors, thanks for working on these
Windows 7 x64
Phpstorm 9 EAP
compiled via gulp-typescript 2.7.7 using typescript 1.5 beta
typyings folder from your master branch master typings folder
typings\aurelia\aurelia-templating.d.ts(62,18): error TS2314: Generic type 'Array<T>' requires 1 type argument(s).
typings\aurelia\aurelia-templating.d.ts(62,26): error TS1039: Initializers are not allowed in ambient contexts.
typings\aurelia\aurelia-templating.d.ts(63,28): error TS1039: Initializers are not allowed in ambient contexts.
typings\aurelia\aurelia-templating.d.ts(64,29): error TS1039: Initializers are not allowed in ambient contexts.
typings\aurelia\aurelia-templating.d.ts(319,31): error TS1039: Initializers are not allowed in ambient contexts.
typings\aurelia\aurelia-templating.d.ts(320,29): error TS1039: Initializers are not allowed in ambient contexts.
typings\aurelia\aurelia-templating.d.ts(321,26): error TS1039: Initializers are not allowed in ambient contexts.
typings\aurelia\aurelia-templating.d.ts(322,29): error TS1039: Initializers are not allowed in ambient contexts.
typings\aurelia\aurelia-templating.d.ts(323,31): error TS1039: Initializers are not allowed in ambient contexts.
typings\es6.d.ts(1136,5): error TS2375: Duplicate number index signature.
typings\es6.d.ts(1419,5): error TS2375: Duplicate number index signature.
typings\es6.d.ts(1992,5): error TS2375: Duplicate number index signature.
typings\es6.d.ts(2275,5): error TS2375: Duplicate number index signature.
typings\es6.d.ts(2558,5): error TS2375: Duplicate number index signature.
typings\es6.d.ts(2841,5): error TS2375: Duplicate number index signature.
typings\es6.d.ts(3124,5): error TS2375: Duplicate number index signature.
typings\es6.d.ts(3407,5): error TS2375: Duplicate number index signature.

Side note#
I am assuming the es6.d.ts will eventually go away and we will just use the one included in official typescript bin folder called lib.es6.d.ts when it has the missing es6 functions.  One strange thing I noted is that if I delete your es6.d.ts file I get errors about not finding Promise, but looking at the official typscript lib.es6.d.ts Promise is defined

there is some tricky business in this...  i've found my self deleting multiply-defined items from the es6.d.ts on several occasions.  here are some related links:
https://github.com/Microsoft/TypeScript/issues/3005
https://github.com/Microsoft/TypeScript/issues/3215
https://github.com/Microsoft/TypeScript/issues/3332

Ok, thanks for the info.  Hopefully these issues will be resolved soon.  Thanks for looking into this.

#3332 has been implemented and merged. Sorry about the delay!


Native scroll is ugly

native scroll  is not suitable for me ,maybe we can change it such as perfect-scrollbar

@popingblink thanks for your advice, the package will not be included in the ng-zorro-antd dependency, you can implement it in your own project.

maybe SlimScroll can help you.


Inventory system needs work

The inventory system is quite outdated and somewhat incompatible with newer versions of Minecraft.

hello yes large problem

Sorry Bibl but MC implementation is worse spaghetti code than anything else.

well at least there's finally development after 6 months :)


Single point features are not scaling when selected in Cesium

According to the documentation, when a single point feature is selected it should scale 20%.    This is not happening.

Fixed in branch  emp-map#43

use test case in branch emp-map#43.

awaiting fix to branch 43. selection size is not increasing.

I was not able to replicate. Try again by completely removing the branch from you computer and pulling it again. There were multiple branches with the same name but different folder.
-----Original Message-----
From: jamesbeecroft<EMAIL_ADDRESS>To: missioncommand/emp3-web<EMAIL_ADDRESS>Cc: Alberto Acevedo<EMAIL_ADDRESS>Assign<EMAIL_ADDRESS>Sent: Fri, Feb 10, 2017 10:50 am
Subject: Re: [missioncommand/emp3-web] Single point features are not scaling when selected in Cesium (#41)
awaiting fix to branch 43. selection size is not increasing.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub, or mute the thread.

Fix already merged in the dev branch by merging issue #43. Closing this issue.


acme: wrong permssions for .well-known/acme-challenge/* / 403

Describe the bug
Since 20.09, renewing Let's Encrypt-certificates fail with lighttpd.
The problem is, that:

the files created below .well-known/acme-challenge/ are not world-readable anymore (This is the bug.)
lighttpd only serves world-readable files (for security reasons)
so, trying to read the acme-challenge via http(s) results in 403, and the certificate creation fails:
log message: acme: error: 403 :: urn:ietf:params:acme:error:unauthorized :: Invalid response from https://DOMAIN/.well-known/acme-challenge/...

This is probably caused by #91121, line UMask = 0027;, this should probably be UMask = 0022;
Workaround:

"Manually" fix the permissions during certificate-renewal, e.g. by running the following as root:
while true; do ll */.well-known/acme-challenge/; chmod a+r */.well-known/acme-challenge/*; sleep 0.05; done
restart all renewal-services: systemctl restart acme-DOMAIN.service
repeat each time new certificates are necessary, until this bug is fixed

(Note: This problem is indpendent from #101445)
To Reproduce
Steps to reproduce the behavior:

run lighttpd
add an acme-configuration for a domain, which is served by lighttpd
try to renew a certificate

Notify maintainers
@m1cr0man @flokli

You have two options to resolve this:

Add the lighttpd user to the acme group in your config
Set the group of your cert(s) to the lighttpd group. This is what Apache HTTPD does

lighttpd supports TLS-ALPN-01 ("acme-tls/1") since lighttpd 1.4.53, and that challenge type is supported by the dehydrated client, among others.  lighttpd TLS-ALPN-01

Sorry, reading over this again I understand what you're really highlighting here. I will change the UMask to 0023. This is safe enough as lego does a good job at not outputting sensitive files with the wrong permissions, and we have our own chmods in the renew script to do the same thing.

@rkoe could you give #106857 a test please?


safe scheduler

similar to pallet-scheduler and implements the scheduler traits but using OCW to trigger & unsigned tx to execute
https://github.com/paritytech/substrate/blob/master/frame/support/src/traits/schedule.rs
this ensures a bad schedule won't brick the chain
https://github.com/paritytech/substrate/issues/8740#issuecomment-833212430
should be able to schedule calls after a timestamp or after a relaychain block number

But the doing this in OCW will imply totally different security guarantees. Is that acceptable?
Why is this an issue if you already have on-idle-scheduler somewhere?
cc @gpestana.

Yeah it cannot be a drop in replace of pallet-scheduler. But for many use cases, OCW should be sufficient.
We can have both pallet installed in a runtime and configure individually for each pallet on which scheduler to use.


Disable rdar74087329-debug-scope-trampoline-blocks.swift

This is failing on the Linux bots. Let’s disable the test for now. rdar://104426107 tracks the actual failure.

@swift-ci Please smoke test

@swift-ci Please test

Sorry for adding you all as reviewers, I accidentally selected the wrong target branch and that caused the PR to touch loads of files.

@swift-ci Please test

Can we track this with a GitHub issue instead? @asl @BradLarson

Sure. But how to reproduce the issue? I passes for me on Mac on mainline.

Can we track this with a GitHub issue instead?

Sure, I filed https://github.com/apple/swift/issues/63107 and linked that in REQUIRES instead

Sure. But how to reproduce the issue? I passes for me on Mac on mainline. And I believe CI was happy yesterday. What is the failing revision?

This seems to only be failing on Linux. Are you testing it on Linux?
CI seems to be failing due to infrastructure issues, I’m going to merge this to unblock the linux bots

The CI on Linux was definitely green on Linux yesterday. So this is something strange

If I remember correctly, this has been been a flaky test since last year


[UPDATE ALGORITHM] Infix to Prefix conversion

✅ Fixes: #856
This PR adds code improvements to the Infix to Prefix/conversion/program.c file and an update to the Infix to Prefix/conversion/readme.md file. The main changes involve enhancing error handling, improving code readability, and adding input validation.
Code Enhancements:

Infix to Prefix/conversion/program.c: Added a constant for operator precedence (#define OPERATOR_PRECEDENCE 3).
Infix to Prefix/conversion/program.c: Improved error handling in push and pop functions by using fprintf and exit for stack overflow and underflow cases.
Infix to Prefix/conversion/program.c: Replaced the precedence function with a switch-case structure for better clarity.
Infix to Prefix/conversion/program.c: Added an input validation function isValidInfix to ensure parentheses are properly matched before processing the expression.

Documentation Update:

Infix to Prefix/conversion/readme.md: Updated the README to reflect the improvements made to the algorithm, including enhanced error handling, input validation, and clearer precedence handling.

@pankaj-bind can you review this PR and add proper labels to it. Also assign me on this PR.

@pankaj-bind can you review this PR and add proper labels to it.


[PERF] sustain: implement an HTMLBars keyword instead of using a component.

target 1.1

Reading: https://github.com/tildeio/htmlbars/blob/master/LIFECYCLE.md

Addressed by #22


Apollo and coroutines

Summary
I am trying to use Apollo with coroutines. Although it works perfectly with toDeferred, sometimes it throws fatal errors that crash my app even if surrounded by try and catches.
In some other parts of the app I use enqueue and overwrite the onFailure to properly manage the issue, but with the coroutines seems impossible with the current implementation.
This is causing several problems for my users. Am I missing something from the usage of the coroutine support?

Can you share a stacktrace of such a crash ?

Sure, this is one instance from the play dashboard
com.apollographql.apollo.exception.ApolloHttpException:
  at com.apollographql.apollo.internal.interceptor.ApolloParseInterceptor.parse (ApolloParseInterceptor.java:105)
  at com.apollographql.apollo.internal.interceptor.ApolloParseInterceptor$1.onResponse (ApolloParseInterceptor.java:53)
  at com.apollographql.apollo.internal.interceptor.ApolloServerInterceptor$2.onResponse (ApolloServerInterceptor.java:125)
  at okhttp3.RealCall$AsyncCall.run (RealCall.kt:138)
  at java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1167)
  at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:641)
  at java.lang.Thread.run (Thread.java:764)

And this from bugsnag
ApolloParseInterceptor.java:105com.apollographql.apollo.internal.interceptor.ApolloParseInterceptor.parse
ApolloParseInterceptor.java:53com.apollographql.apollo.internal.interceptor.ApolloParseInterceptor$1.onResponse
ApolloServerInterceptor.java:125com.apollographql.apollo.internal.interceptor.ApolloServerInterceptor$2.onResponse
RealCall.kt:138okhttp3.RealCall$AsyncCall.run
ThreadPoolExecutor.java:1167java.util.concurrent.ThreadPoolExecutor.runWorker
ThreadPoolExecutor.java:641java.util.concurrent.ThreadPoolExecutor$Worker.run
Thread.java:764java.lang.Thread.run```

If you know bugsnag, it separates exception by handled and unhandled. I have some legacy code that uses .enqueue with the callback and overrides onFailure, same 500 server error happens but it's categorised ad "handled", so the app won't crash. While in my new repositories using coroutines, these errors manage to crash it

Thanks. There are a few other issues about exception handling and coroutines so we might be into something. It does work ok in unit tests (https://github.com/apollographql/apollo-android/blob/1dab62c25b271846117c439aebb4afa266be17cd/apollo-integration/src/test/java/com/apollographql/apollo/CoroutinesApolloTest.kt#L78) so the setup has to be more complex than that.
Not sure it's related but still worth a shot, are you on latest versions of coroutines and kotlin  ? (1.3.2 + 1.3.61)

Also: are you able to reproduce this locally or is this only something you see in BugSnag/GooglePlay ?

That is the main issue, I can't reproduce it locally. So I have been chasing ghosts for the past couple of weeks as for some reason (probably related to our backend) these types of issues increased.
I am for kotlin, just saw that for coroutines we are on 1.3.1. I'll see if that helps too!

Any update on this?

From the stack trace is super unclear where is the issue, but I assume it's related how the coroutines is used on client side not in Apollo. If you take a look at the definition of Apollo  toDeferred it super trivial:
 val deferred = CompletableDeferred<Response<T>>()

  deferred.invokeOnCompletion {
    if (deferred.isCancelled) {
      cancel()
    }
  }
  enqueue(object : ApolloCall.Callback<T>() {
    override fun onResponse(response: Response<T>) {
      deferred.complete(response)
    }

    override fun onFailure(e: ApolloException) {
      deferred.completeExceptionally(e)
    }
  })

  return deferred

Change extension function "toDeferred" as below:
`fun  ApolloCall.toDeferred(): Deferred<Response> {
val deferred = CompletableDeferred<Response>()
deferred.invokeOnCompletion {
    if (deferred.isCancelled) {
        cancel()
    }
}
enqueue(object : ApolloCall.Callback<T>() {
    override fun onResponse(response: Response<T>) {
        deferred.complete(response)
    }

    override fun onFailure(e: ApolloException) {
        var builder = Response.builder<T>(operation())
                .errors(arrayListOf(Error(e.localizedMessage, null, null)))
                .build()

        deferred.complete(builder)
    }

    override fun onCanceledError(e: ApolloCanceledException) {
        var builder = Response.builder<T>(operation())
                .errors(arrayListOf(Error(e.localizedMessage, null, null)))
                .build()

        deferred.complete(builder)
    }

    override fun onNetworkError(e: ApolloNetworkException) {
        var builder = Response.builder<T>(operation())
                .errors(arrayListOf(Error(e.localizedMessage, null, null)))
                .build()

        deferred.complete(builder)
    }

    override fun onParseError(e: ApolloParseException) {
        var builder = Response.builder<T>(operation())
                .errors(arrayListOf(Error(e.localizedMessage, null, null)))
                .build()

        deferred.complete(builder)
    }

    override fun onHttpError(e: ApolloHttpException) {
        var builder = Response.builder<T>(operation())
                .errors(arrayListOf(Error(e.localizedMessage, null, null)))
                .build()

        deferred.complete(builder)
    }

    override fun onStatusEvent(event: ApolloCall.StatusEvent) {
        super.onStatusEvent(event)
    }
})

return deferred

}`

I have an extension function that uses coroutine.
Maybe someone else can find this usable.
`suspend fun  ApolloCall.execute() = suspendCoroutine<Response> { continuation ->
enqueue(object : ApolloCall.Callback<T>() {
    override fun onResponse(response: Response<T>) {
        continuation.resume(response)
    }
    override fun onFailure(error: ApolloException) {
        continuation.resumeWithException(error)
    }

    override fun onNetworkError(e: ApolloNetworkException) {
        //This should not be calling super because super calls failure
        //super.onNetworkError(e)
        val response = Response.builder<T>(operation())
            .errors(arrayListOf(com.apollographql.apollo.api.Error(e.localizedMessage, null, null)))
            .build()
        continuation.resume(response)
    }
})

}
`


HDDS-10445. OM admin CLI to enable force fetching network topology tree from SCM

What changes were proposed in this pull request?
OM has a background thread running that periodically refetches the updated network topology layout information from SCM for the refresh duration frequency of every one hour (default).
This change introduces an OM admin CLI for force fetching the network topology tree information from SCM (on demand) without having to rely on the configuration: ozone.om.network.topology.refresh.duration.
CLI usage:
ozone admin om fetch-topology-tree -id=omServiceId

What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-10445
How was this patch tested?

Added integration test.
Green Git CI: https://github.com/tanvipenumudy/ozone/actions/runs/8108558196

@kerneltime, @duongkame could you please take a look? Thanks!

Thanks for working on this, @tanvipenumudy. I don't see any tests written for it yet. Would you mind adding an integration test to verify your results, please?

@adoroszlai could you please review the changes as well? Thanks!

@tanvipenumudy can we close this?

Sure, marking the PR as closed.


feat(google): allow translatable entity synonyms

Proposed changes
Let's say you have a multilingual Google Assistant app (with language nl as a default language, and en) with an app that only has 1 intent: to capture a score that a user can give.
This is the models/nl.json file
{
  "intents": {
    "ScoreInputIntent": {
      "phrases": ["{score}", "Ik vind het {score}"],
      "entities": { "score": { "type": "ScoreType" } }
    }
  },
  "googleAssistant": {
    "custom": {
      "global": {
        "actions.intent.MAIN": { "handler": { "webhookHandler": "Jovo" } },
        "actions.intent.NO_INPUT_1": { "handler": { "webhookHandler": "Jovo" } },
        "actions.intent.NO_INPUT_2": { "handler": { "webhookHandler": "Jovo" } },
        "actions.intent.NO_INPUT_FINAL": { "handler": { "webhookHandler": "Jovo" } },
        "actions.intent.NO_MATCH_1": { "handler": { "webhookHandler": "Jovo" } },
        "actions.intent.NO_MATCH_2": { "handler": { "webhookHandler": "Jovo" } },
        "actions.intent.NO_MATCH_FINAL": { "handler": { "webhookHandler": "Jovo" } }
      },
      "types": {
        "ScoreType": {
          "synonym": {
            "entities": {
              "1": { "synonyms": ["1", "slecht"] },
              "2": { "synonyms": ["2", "middelmatig"] },
              "3": { "synonyms": ["3", "goed"] }
            },
            "matchType": "EXACT_MATCH"
          }
        }
      }
    }
  }
}

In the english model models/en.json, you would have something like this
{
  "intents": {
    "ScoreInputIntent": {
      "phrases": ["{score}", "I think it's {score}"],
      "entities": { "score": { "type": "ScoreType" } }
    }
  },
  "googleAssistant": {
    "custom": {
      "global": {
        "actions.intent.MAIN": { "handler": { "webhookHandler": "Jovo" } },
        "actions.intent.NO_INPUT_1": { "handler": { "webhookHandler": "Jovo" } },
        "actions.intent.NO_INPUT_2": { "handler": { "webhookHandler": "Jovo" } },
        "actions.intent.NO_INPUT_FINAL": { "handler": { "webhookHandler": "Jovo" } },
        "actions.intent.NO_MATCH_1": { "handler": { "webhookHandler": "Jovo" } },
        "actions.intent.NO_MATCH_2": { "handler": { "webhookHandler": "Jovo" } },
        "actions.intent.NO_MATCH_FINAL": { "handler": { "webhookHandler": "Jovo" } }
      },
      "types": {
        "ScoreType": {
          "synonym": {
            "entities": {
              "1": { "synonyms": ["1", "bad"] },
              "2": { "synonyms": ["2", "mediocre"] },
              "3": { "synonyms": ["3", "good"] }
            }
          }
        }
      }
    }
  }
}

With the current code/setup, the jovo build-platform doesn't take the secondary languages into account and only generates a build/[STAGE]/platform.googleAssistant/custom/types/ScoreType.yaml
"synonym":
  "entities":
    "1":
      "synonyms":
        - "1"
        - "slecht"
    "2":
      "synonyms":
        - "2"
        - "middelmatig"
    "3":
      "synonyms":
        - "3"
        - "goed"
  "matchType": "EXACT_MATCH"

Where we need a build/[STAGE]/platform.googleAssistant/custom/types/en/ScoreType.yaml as well with the translations for the English model
"synonym":
  "entities":
    "1":
      "synonyms":
        - "1"
        - "bad"
    "2":
      "synonyms":
        - "2"
        - "mediocre"
    "3":
      "synonyms":
        - "3"
        - "good"

With this pull request the desired behaviour is introduced. When you then deploy the code to Actions on Google, the translations are available in the Console.
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist

[x] My code follows the code style of this project
[ ] My change requires a change to the documentation
[ ] I have updated the documentation accordingly
[ ] I have added tests to cover my changes
[x] All new and existing tests passed

Awesome. Thank you! Will run a few tests and merge soon.

I fixed the line as requested. Thanks again!


update application to 0.0.97

UpdateBot pushed helm dependency: application to: 0.0.97

/test this
/approve

UpdateBot commands:
updatebot push-version --kind helm application 0.0.97


feat(dao): prefix dao obj with "dao", rather than suffix, for better autocomplete

closed infavor of soft cut alias


Add support for kubernetes builds on the from-token deployments

Proposed changes
This PR adds support for kubernetes builds on the from-token deployments using --kubernetes flag as well as adds support for specifying whether the deployment should run directly or not using --no-deploy flag
Fixes
If it fixes a bug or resolves a feature request, be sure to link to that issue.
Types of changes
What types of changes does your code introduce? (A breaking change is a fix or feature that would cause existing functionality and APIs to not work as expected.)
Put an x in the box that applies

[ ] Non-breaking fix (non-breaking change which fixes an issue)
[ ] Breaking fix (breaking change which fixes an issue)
[ ] Non-breaking feature (non-breaking change which adds functionality)
[ ] Breaking feature (breaking change which adds functionality)
[ ] Refactor (non-breaking change which changes implementation)
[ ] Messy (mixture of the above - requires explanation!)

Checklist
Put an x in the boxes that apply.

[ ] I have read the CONTRIBUTING doc
[ ] I am making a pull request against the main branch (left side). Also you should start your branch off our main.
[ ] Lint and unit tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have locally run services that could be impacted and they do not present failures derived from my changes

Further comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...

:)


UART Frame Error implementation

uart-rx: add comb logic frame error bit
uart-rx: has 0.5 stop bit
testbench: toggle hold low loopback uart line by writing to 0x10c
test: append frame error test to current overrun test
libos: define macros for uart statuses in uart.h

There's a compile error:
uart.c:30:39: error: use of undeclared identifier 'UART_HAS_WORD'
while ((REGISTERS[REG_UART_STATUS] & UART_HAS_WORD) == 0)

Also, you're assigning frame_error in two places.  Verilator is a bit lax about this, but the synthesis tools will most likely error on it.

Merged. Thanks!


leveldb: fix write operation suspension

Hi @syndtr Here is an easy fix for write suspension.
We have this mechanism to slow down write operations if there are too many LEVEL0 files accumulated.
But instead of writing a Millisecond then resume the write, we will "deadloop" until the SLOW DOWN
alert is resolved.
I'm not sure how much performance affect this issue will have(e.g. deadloop will definitely exhaust one CPU core),
but I think it's quite easy to fix. So please take a look.

Here is a tiny benchmarking(writing 500MB random data) for verifying the fix.
Without fix
$ ldb-benchstat batch-100kb.2020-07-13-10:03:53.json
-- batch-100kb.2020-07-13-10:03:53 (853 events) total time: 117.9550s
 total size: 524083200 bytes
  mean mb/s: 28.733 (+- 13.800)

Total delayed writes:     2262
Total delayed duration: 1m38.173530706s

With fix
-- 1 (853 events) total time: 23.6942s
 total size: 524083200 bytes
  mean mb/s: 23.030 (+- 6.419)

Total delayed writes:     89
Total delayed duration: 114.375774ms

We can see 83% of the time is spent waiting. If we get rid of this unnecessary waiting, it improves a lot.


Fix Github CI Test

Why we need this PR
CI test of unit-test failed due to redundant space/tab from #113.
In check target we use test-no-verify target that doesn't check for modified files, while it should use test target that won't accept modified files (using verify-unchanged target)
Changes made

Use test instead of test-no-verify in check target
Remove Redundant space/tab for a const var
Remove multiple checks in dockerized NMO (for the container-build-community target) and as a result save time.

Which issue(s) this PR fixes
Fixes unit-test from make test. Found in https://github.com/openshift/release/pull/49534

/retest

/retest


Adding resourceconnector - Appliance GA API version

ARM API Information (Control Plane)
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Azure 1st Party Service can try out the Shift Left experience to initiate API design review from ADO code repo.  If you are interested, may request engineering support by filling in with the form https://aka.ms/ShiftLeftSupportForm.
Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

[ ] new service onboarding
[x] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
By default, Azure SDKs of all languages (.NET/Python/Java/JavaScript for both management-plane SDK and data-plane SDK, Go for management-plane SDK only ) MUST be refreshed with/after swagger of new version is published. If you prefer NOT to refresh any specific SDK language upon swagger updates in the current PR, please leave details with justification here.

Contribution checklist (MS Employees Only):

[x] I commit to follow the Breaking Change Policy of "no breaking changes"
[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

Applicability: :warning:
If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

Change to data plane APIs
Adding new properties
All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

[x] Check this box if any of the following apply to the PR so that the label "ARMReview" and "WaitForARMFeedback" will be added by bot to kick off ARM API Review.  Missing to check this box in the following scenario may result in delays to the ARM manifest review and deployment.

Adding a new service
Adding new API(s)
Adding a new API version
-[ ] To review changes efficiently, ensure you copy the existing version into the new directory structure for first commit and then push new changes, including version updates, in separate commits. You can use OpenAPIHub to initialize the PR for adding a new version. For more details refer to the wiki.

[ ] Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If you have any breaking changes as defined in the Breaking Change Policy, request approval from the Breaking Change Review Board.
Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Additional details on the process and office hours are on the Breaking Change Wiki.
NOTE: To update API(s) in public preview for over 1 year (refer to Retirement of Previews)
Please follow the link to find more details on PR review process.

Can you please update the checklist for this PR ? Also since this seems like a new api version please include the previous version as the first commit as explained above in the link :

Hi @raosuhas Updated the API checklist and this is the previous API Version we had merged - https://github.com/Azure/azure-rest-api-specs/blob/main/specification/resourceconnector/resource-manager/Microsoft.ResourceConnector/preview/2022-04-15-preview/appliances.json

Hi @raosuhas Updated the API checklist and this is the previous API Version we had merged - https://github.com/Azure/azure-rest-api-specs/blob/main/specification/resourceconnector/resource-manager/Microsoft.ResourceConnector/preview/2022-04-15-preview/appliances.json

@aditimalladi This is not helpful for me since I cannot view the diff like this. you need to add the previous api version as the base version in the first commit while creating the PR.
IF you follow the links above this is explained in step 6 here (If creating manually) :
https://dev.azure.com/azure-sdk/internal/_wiki/wikis/internal.wiki/83/Manual-Process-Adding-new-API-version
or step 7 here : (If using openapui hub)
https://dev.azure.com/azure-sdk/internal/_wiki/wikis/internal.wiki/208/OpenAPI-Hub-Adding-new-API-version

Trying to understand Swagger Model Validation error : but this operation is already marked as an async operation - not sure what the ask is here to fix this error.
This is the older API version response for reference: https://github.com/Azure/azure-rest-api-specs/blob/main/specification/resourceconnector/resource-manager/Microsoft.ResourceConnector/preview/2022-04-15-preview/appliances.json#L280

Trying to understand Swagger Model Validation error : but this operation is already marked as an async operation - not sure what the ask is here to fix this error.
This is the older API version response for reference: https://github.com/Azure/azure-rest-api-specs/blob/main/specification/resourceconnector/resource-manager/Microsoft.ResourceConnector/preview/2022-04-15-preview/appliances.json#L280

@aditimalladi , please add Location header to the response in related examples.

Trying to understand Swagger Model Validation error : but this operation is already marked as an async operation - not sure what the ask is here to fix this error.
This is the older API version response for reference: https://github.com/Azure/azure-rest-api-specs/blob/main/specification/resourceconnector/resource-manager/Microsoft.ResourceConnector/preview/2022-04-15-preview/appliances.json#L280

@aditimalladi , please add Location header to the response in related examples.

@raych1 Could you please shar an example of the expected update?

Trying to understand Swagger Model Validation error : but this operation is already marked as an async operation - not sure what the ask is here to fix this error.
This is the older API version response for reference: https://github.com/Azure/azure-rest-api-specs/blob/main/specification/resourceconnector/resource-manager/Microsoft.ResourceConnector/preview/2022-04-15-preview/appliances.json#L280

@aditimalladi , please add Location header to the response in related examples.

@raych1 Could you please shar an example of the expected update? I have not added headers in responses for previous versions of the API

@aditimalladi , please refer to this example

Trying to understand Swagger Model Validation error : but this operation is already marked as an async operation - not sure what the ask is here to fix this error.
This is the older API version response for reference: https://github.com/Azure/azure-rest-api-specs/blob/main/specification/resourceconnector/resource-manager/Microsoft.ResourceConnector/preview/2022-04-15-preview/appliances.json#L280

@aditimalladi , please add Location header to the response in related examples.

@raych1 Could you please shar an example of the expected update? I have not added headers in responses for previous versions of the API

@aditimalladi , please refer to this example

@raych1 I have updated the example as discussed yesterday - is there something missing in the example? I still see the model validation failing with the same error.


Assigned Channel Warning update

Update download links in comment
Convert conditionals into switch cases
Add Assigned Channel warning

merge


Extracting log mel filterbank features

Thanks very much for the great library! It's my default library for speech processing now.
Just want to double check on the following, I want to extract 40-dimensional log mel filterbank feautres from sliding a Hamming window of width 25ms with an overlap of 10ms. Does the code below extract the right features? I am a bit uncertain whether frame_stride=0.01 creates overlap of 10ms..
fs, signal = wav.read(file_path)
lmfe = speechpy.feature.lmfe(signal, sampling_frequency=fs, frame_length=0.025, frame_stride=0.01, num_filters=40, fft_length=512, low_frequency=0, high_frequency=None)

Thanks!

I suggest that you should read some source code:

frame_stride (float): the step between successive frames in seconds.
So,frame_stride means that no overlap


Documentation update

Obviously the documentation is not usable or easily interpretabel by new users, nor is it finished. It barely names all the functions of the API, let alone how to use them.
Since I want to fully focus on the code I could use some help with the documentation.
Feel free to contribute at magister-api/docs (see https://github.com/magister-api/docs)

Are you using REST APIs? If so, I might be able to help.
What are the following?

The base path
Endpoints
All possible methods and parameters
An API Key (If required)


Bug: IRGen Phi's incoming is now predecessor, rendering register renaming incorrect

The process of renaming incoming registers in the Phi node during SSA construction involves looking up the renaming information from the incoming block. In the original design, the register in the Phi node's incoming edge was expected to be renamed within that incoming block.
In issue #84, the incoming block has been redefined as the predecessor block instead of the variable definition block. This change disrupts the expected renaming behavior. If the def block and predecessor are not the same, the register won't be found.

This is still buggy. Consider move the phi branch renaming out of DFS, and have a separate BB loop to rename all phi branches.


Restructure NS enqueuing; improve thread safety

Rather than collecting a list of namespaces to mark for enqueueing after
syncWithForest is complete, this change allows them to be enqueued
inline, which simplifies the control flow.
This also means that it's possible for the same namespace to be
reconciled twice at the same time (it was probably possible before as
well). While syncWithForest is guarded by the forest-wide mutex, there
is a chance that the results could be committed to the apiserver
out-of-order. I don't believe I ever observed this (a bug I was
chasing turned out to be a more mundane logic error) but in order to fix
this potential problem, this change introduces a per-namespace lock that
is only released after the namespace has been fully committed.
This allows multiple namespaces to be reconciled in parallel (although
access to the forest is still globally synchronized), but prevents any
one namespace from being reconciled more than once at a time.
Tested: integ tests; manually with later changes

See https://github.com/adrianludwin/multi-tenancy/commits/self-serve for the context of this change.

/assign @rjbez17

/hold
/approve
/lgtm
@Fei-Guo  feel free to remove hold when satisfied

/lgtm
/hold cancel
/approve


Cargo Cult JVM Settings

WHAT
Copy https://github.com/android/nowinandroid/pull/1492 and https://www.jasonpearson.dev/metaspace-in-jvm-builds/
WHY
Improve CI and local performance?
HOW
Checklist :clipboard:

[ ] Add explicit visibility modifier and explicit return types for public declarations
[ ] Run spotless check
[ ] Run tests
[ ] Update metalava's signature text files

Hey - so while these settings are better, I wanted to let you know I found an issue with how Kotlin Daemon picks up and doesn't pick up JVM args. I'm digging into it and will ping y'all when I have an update.

@yschimke FYI I updated my recommendations. Let me know if you have any questions or further issues with metaspace.


I have a question about fcnxs in the example file

Hello everyone.Recently I have read the code of fcnxs in the example file. In this example,It mentions that
"""FileIter object in fcn-xs example. Taking a file list file to get dataiter.
in this example, we use the whole image training for fcn-xs, that is to say
we do not need resize/crop the image to the same size, so the batch_size is
set to 1 here'''''
So the example has his own data.py to create a DateIter.Moreover,the example has his own solver file which confuses me very much.Why does this example has to write its own solver rather than using the default solver like model.fit()
I mimic this  example ,and write a DataIter like that.However,It doesn't work when I use the default solver model.fit().
So are there some special rules when using the model.fit()? Thank you .

This issue is closed due to lack of activity in the last 90 days. Feel free to reopen if this is still an active issue. Thanks!

This issue is closed due to lack of activity in the last 90 days. Feel free to reopen if this is still an active issue. Thanks!


Update projectName.scss

Summary
Removing terra mix in's as referenced here https://github.com/cerner/generator-terra-module/issues/64.

This can also be removed from devDependencies in the package.json

Terra-clinical & terra-consumer's package.json as well. At this point I think the only differences between these package's are the keywords produced.

@emilyrohrbough thanks for checking my kinda lazy work. I think I've got all the instances now.


Website updates

User Story

As an <audience/user>:  user
I want to <action/task>: delete the white paper
so that <outcome/goal/benefit>: its no longer public since its outdated.

Type

[x] Enhancement
[ ] Maintenance
[ ] Refactor

Description

Solution

Definition of Done

[ ] remove all links to the WP on website and docs page.

Attach files or screenshots if it's helpful for this issue.

Issue moved to MARKETProtocol/website #293 via ZenHub


Fix session attributes when getting all user sessions

This fixes an issue where the getSessionAttributes is not passed the correct raw DB attributes when called in getUserSessions.
Also thought this was such a small fix that an issue might not be needed (nor this PR to be honest, but it's a slow wednesday evening), if you'd prefer an issue linked to it just let me know.

Thanks!


'Search' and 'Geolocate me' not working

Browse the map, search or use geolocate me to view healthsites close to your location.

Fixed @markherringer
can you check it? (also please hard refresh)

please check this and close if works


Bland Icons

Love the theme honestly, however the monochrome icons look bland and boring to me after using Qbittorrent with their newer colorful icons. Would it be at all possible to use the default icons on qbittorrent rather the monochrome ones or to use a colored variant of the monochrome icons you currently have in your theme?

yep, you should to download source code. go to Builds and delete icons folder. Run .bat file in the same directory and you will see new qbtheme file

yep, you should to download source code. go to Builds and

I did exactly what you described but couldnt find the resulting file anywhere... any idea?

Open a terminal window and then run the bat file. In that case, you can see any errors that are happening. Errors could be most likely because of missing dependencies. Install them and it will work fine. You need to have the build tools in order to be able to make the build. Ensure that once then let us know here!
Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows
From: @.>
Sent: Friday, December 23, 2022 12:24 AM
To: @.>
Cc: @.***>
Subject: Re: [witalihirsch/qBitTorrent-fluent-theme] Bland Icons (Issue #32)
yep, you should to download source code. go to Builds and
I did exactly what you described but couldnt find the resulting file anywhere... any idea?
—
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fwitalihirsch%2FqBitTorrent-fluent-theme%2Fissues%2F32%23issuecomment-1363231701&data=05|01||ce8569687b2042d659eb08dae44df73a|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|638073320753603350|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=cFDwrxuAC2k9jxIO2fW8gQeF4MStFJldeH3f4U5HMO0%3D&reserved=0, or unsubscribehttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAHXTMZFWO22VNB3LNNXVKD3WOSPWTANCNFSM6AAAAAATFKNX5M&data=05|01||ce8569687b2042d659eb08dae44df73a|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|638073320753603350|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=giiWpIPbR8Qvz%2FN34DWDp0RAUzjzSH0XfYOnrC2iW8E%3D&reserved=0.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

yep, you should to download source code. go to Builds and

I did exactly what you described but couldnt find the resulting file anywhere... any idea?

My fault, try to delete not the folder, remove all files inside dark and light folders

yep, you should to download source code. go to Builds and

I did exactly what you described but couldnt find the resulting file anywhere... any idea?

My fault, try to delete not the folder, remove all files inside dark and light folders

still dont get it sorry, guess ill just wait for the app to (maybe) get updated or use it just as it is

I created a new release with default icons, but maybe in the future, when I can configure icons for all objects, I'll return to fluent icons

I created a new release with default icons, but maybe in the future, when I can configure icons for all objects, I'll return to fluent icons

I wouldn't mind the return to fluent icons if they are colored, personally.

I created a new release with default icons, but maybe in the future, when I can configure icons for all objects, I'll return to fluent icons

Perfect, Thanks a lot


Request credentials for an os-climate bucket

Requesting credentials for github user: ArianeDlns
Requesting credentials for the bucket: https://github.com/os-climate/physrisk
Email address to send a credential download link<EMAIL_ADDRESS>Request checklist:

[ ] User can establish connection with the bucket
[ ] User can read files from the bucket
[ ] User can write files to the bucket

#111 working with @judith-feredj - would it be possible to have a set of credentials,
Best,
Ariane

I believe the correct S3 bucket is actually:
os-climate-physrisk-hazard-indicators
Sent the following email today:
From: Matt Watkins<EMAIL_ADDRESS>Subject: Request: OS-Climate-Community-Hub/issues/148
Date: 27 August 2024 at 15:44:44 BST
To<EMAIL_ADDRESS>Hi,
We received your access request here:
https://github.com/os-climate/OS-Climate-Community-Hub/issues/148
Find attached a CSV file containing the requested credentials with read-only permissions.
Thanks,

Matt Watkins

The Linux Foundation
Release Engineering Team
https://www.linuxfoundation.org/
<EMAIL_ADDRESS>


browserpass not working ("Error: Specified native messaging host not found.")

Issue description
I reported this for browserpass, but they think it's a bug in the package: https://github.com/browserpass/browserpass/issues/299
Steps to reproduce

Install browserpass through nixpkgs: https://github.com/browserpass/browserpass#installing-the-host-application
Install the chrome plugin: https://github.com/browserpass/browserpass#installing-the-chrome-extension
Press the icon to see the error message

Technical details

system: "x86_64-linux"
host os: Linux 4.14.79, NixOS, 18.09.1228.a4c4cbb613c (Jellyfish)
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.1.3
channels(simendsjo): ""
channels(root): "nixos-18.09.1228.a4c4cbb613c, nixos1803-18.03.133311.5d19e3e78fb, nixos1809-18.09.932.09195057114"
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos

I'll add some details to help you investigate. You package installs host.json file which defines path to the browserpass binary (in place of %%replace%% placeholder). The message "Specified native messaging host not found" very much suggests that the binary is not present at that location.

See https://github.com/NixOS/nixpkgs/issues/47340 and https://github.com/NixOS/nixpkgs/issues/33748. We patch firefox to look for the host.json manifest in the correct place, but it looks like the patch no longer works.
The workaround is adding the json manifest to ~/.mozilla/native-messaging-hosts. Something like this should most likely do the trick:
mkdir -p ~/.mozilla/native-messaging-hosts
ln -s /run/current-system/sw/lib/mozilla/native-messaging-hosts/com.dannyvankooten.browserpass.json ~/.mozilla/native-messaging-hosts/

To clarify, the reported issue was for Chrome and/or Chromium, corresponding path is one of these instead of ~/.mozilla/native-messaging-hosts/:

~/.config/google-chrome/NativeMessagingHosts
~/.config/chromium/NativeMessagingHosts

Yeah, sorry misread and assumed it was the same issue that've popped up a bunch of time with firefox. Chrome should indeed look for the manifest files under /etc so that's quite strange.

False alarm! Sorry! :(
I didn't enable the program, ref https://github.com/browserpass/browserpass/issues/299#issuecomment-439188599


Language-specific VSCode extensions.json

We currently don't have an extensions.json defined specific for each language (we only recommend azd extension). We should add this to clue the user in on the language specific VSCode extension for the debugger in our shipped VSCode tasks to work.

Here's the ones I'd recommend--
All:

AZD (of course) (ms-azuretools.azure-dev)
Azure Resources (ms-azuretools.vscode-azureresourcegroups)
YAML (redhat.vscode-yaml)

C#:

C# (ms-dotnettools.csharp)

Java:

Extension Pack for Java (vscjava.vscode-java-pack)

JavaScript / TypeScript:

ESLint (dbaeumer.vscode-eslint)

Python:

Python (ms-python.python)
Pylance (ms-python.vscode-pylance)

We can use the list that is in devcontainer.JSON

@savannahostrowski  @bwateratmsft
Moving this to backlog. Don't think we are doing anything w.r.t to this in Gallium.


Reorder and its proofs

I am taking some liberty to merge, because all the pull request that make up this pull request have been approved.


fix: update etcd dependency according to https://github.com/etcd-io/e…

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

fix: https://github.com/kitex-contrib/registry-etcd/issues/15


[Branch View] put all controll buttons in the same td and make them look similar

I think the current implementation takes away too much space from the important left-aligned column because having the buttons inside individual fixed columns introduces unnecessary spacing. I'd put all three buttons in the same td and make them look like this (remove compact class on the pull button):

Then right-align the diffstat and let the leftmost column take the remaining space.
Originally posted by @silverwind in https://github.com/go-gitea/gitea/pull/7520#issuecomment-514727605

blocked by https://github.com/go-gitea/gitea/pull/7602 https://github.com/go-gitea/gitea/pull/7604

Not sure if that split-up was really necessary. Those two PRs conflict each other unfortunately. Maybe wait till #7602 is merged and then do the remaining changes in #7604 to achieve the equivalent of that screenshot?

i thought the contributor guidline tells me that if i like to get changes merged quik i should make smal  PRs wich a single wish/topic

i cann still klose the smal PRs and contribute to the big one?

Yes, small changes get merged faster but your old one wasn't really that big. Anyways, I'd suggest sticking to the plan above. #7602 should probably be landed by tomorrow.

thx

is still not done

@silverwind ask for reopen this - i curently dont work on this ...

close this since this is no huge deal and if somebody came with good idears ... he can make it's own issue or pull


Fix the tests

Looks like auto-merge didn't respect the sandbox tests--working on fixing that

This was meant to be part of https://github.com/OpenDevin/OpenDevin/pull/1474
Going to merge to unbreak CI


Bump Airflow to 2.4.0, standardize version bump process

Fixes

Fixes #732 by @AetherUnbound
This also addresses some security issues that dependabot identified.
Description

This PR updates our Airflow version to 2.4.0. I've also borrowed the pattern set up in #656 and applied it to the Airflow version, so we only have to update it in one place now!
As part of the version update, I've also updated the schedule_interval parameter to be schedule instead. What's unfortunate however is that the airflow.models.dag.Dag model does not have a schedule attribute, you still must use schedule_interval when referencing it on the DAG object. So there are a few instances where we were not able to update that value.
I added a bunch of deprecation warning filters for our tests to make the warning summary more relevant (presently there should be no warnings). Most of the warnings were either 1) irrelevant & unfixable or 2) due to upstream dependencies.
Lastly, and probably most notably:

⚠ Developer note ⚠
The extra argument for AIRFLOW_CONN_AWS_DEFAULT has been updated from host to endpoint_url:
Before: AIRFLOW_CONN_AWS_DEFAULT=aws://test_key:test_secret@?region_name=us-east-1&host=http://s3:5000
After: AIRFLOW_CONN_AWS_DEFAULT=aws://test_key:test_secret@?region_name=us-east-1&endpoint_url=http://s3:5000
You will continue to receive warnings about extra["host"] unless this value is changed in your .env file!

Testing Instructions

just build
just test --extended (and ensure there are no warnings in the warnings summary)
Run a few DAGs to make sure everything functions as expected
just airflow-version should report 2.4.0

Checklist

[x] My pull request has a descriptive title (not a vague title like Update index.md).
[x] My pull request targets the default branch of the repository (main) or a parent feature branch.
[x] My commit messages follow best practices.
[x] My code follows the established code style of the repository.
[x] I added or updated tests for the changes I made (if applicable).
[x] I added or updated documentation (if applicable).
[x] I tried running the project locally and verified that there are no visible errors.

Developer Certificate of Origin

Developer Certificate of Origin
Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

Ah, great thought on the retired DAGs. I'll revert those changes, we definitely don't need to change them. I used too aggressive a find-and-replace 😅


Questions when previewing and opening files

Hello, I am very happy to use this tool.
However, it is not possible to preview certain types of files during use (it is possible to preview directories, and it is also not possible to open files.
I am certain that I have installed the most dependencies instructed in README(
apart from poppler).
Additionally, I have coped the 'the preset configs' as my own configs, just like this:

Finally, a picture using yazi is attached:

Waiting for your help! thx

Have you added Git to the PATH according to the Windows Installation Guide?
Please make sure the file command is available in your terminal, you can do a file -v to verify it.

Based on the ideas you provided, I reconfirmed the git environment variables.
The fact is that git is installed correctly, and the default installation of git on the window where the path added to the environment variable is C:\Program File\Git\cmd.
But I discovered something even more torturous: The 'file' command cannot be used in pwsh, but it can be used normally in git bash.That's not all,  using yazi in git bash will cause the page to stutter

The fact is that git is installed correctly, and the default installation of git on the window where the path added to the environment variable is C:\Program File\Git\cmd.

Note that it should be C:\Program Files\Git\usr\bin, rather than C:\Program File\Git\cmd in the Windows Installation Guide.

That's not all, using yazi in git bash will cause the page to stutter

This is a specific issue with the combination of Mintty (Git Bash) and ConPTY, not a bug in Yazi; Windows Terminal should work properly.

After resetting the environment variables, the file preview returned to normal.
I misunderstood the meaning of the document, so I am very sorry for the inconvenience caused to you. Thank you very much for your kind help.
I should have learned the difference between the two paths in hindsight.
Now I have a new question. When setting the exec command of text in 'yazi.toml', it seems that setting the parameter to '%n' has no effect.

Trying to remove the parameters after nvim, this does open a file, but if there is a need to open multiple files at the same time, this is obviously not enough for me.
This problem also occurs when opening the compressed file, and I don't know how to set the unzip path to some fixed path (i.e. not the current path).
Where does my problem occur? thx

And my title did not clearly express my meaning, so it caused you trouble. I apologize to you

%*, %1, %2, ... Support for these placeholders was added recently and will be shipped with Yazi v1.0.5, you can use it in advance from a source build.
See https://yazi-rs.github.io/docs/usage/configuration/yazi#opener for more details.

Well, the current version is Yazi v0.1.4.
Then how to set the default path of the decompression to another path?

The JS file cannot be previewed properly, nor can it be opened

Do other files work properly? Please do a file -b --mime-type your-js-file-path.js to see what output comes out

By the way, the vue files also can't work properly.
In addition, no other files were found not to work properly.

The Java class file is also not working properly
Although this document is not much to read, but hope to provide you with an idea

So apart from the java class, it's only Vue files that can't be previewed? Regarding the java class, when the Yazi plugin system comes out, it will allow users to add their own previewer

Yes, the most files in vue project can't be previewed.

Just tested, it works fine for me. Can you place the files that cannot be previewed here so that I can test using them?

waf.zip
Of course. thx

When I configured Lunarvim(lvim) as the default text editor, the following error occurred

I noticed that you joined Yazi's Telegram group. Let's conclude this and continue on Telegram, since this is not a Yazi bug. Compared to an issue, the community group is an easier way to get help. 👍🏻


V14 fixes

Updates the docker images to build images for resign & no-resign configs  (no-resigns play fewer games, don't have a remote-flagfile)
updates the training code to freeze graphs in the right place, read things from cloud bigtable, and block on freshness.

@brilee could you look at the stuff in rl_loop?


[proposal] Provide a way to render inner shadow on Text

Like the title, it would be awesome if TextStyle, allows handling Inner Shadow and not just for the background.

Hi @shifenis
Can you please elaborate more?
Does the code bellow works for you?

code sample
import 'package:flutter/cupertino.dart';
import 'package:flutter/material.dart';

void main() => runApp(MyApp());

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      home: Scaffold(
        body: Center(
          child: Text(
            "Forgot Password?",
            style: TextStyle(
              shadows: [
                Shadow(
                    color: Colors.green,
                    offset: Offset(0, -2))
              ],
            ),
          ),
        ),
      ),
    );
  }
}

Hi @pedromassangocode, the code you provide is not really an inner shadow, indeed, it's a background shadow.

This is the result I would like to achieve.
At the moment I don't think Flutter can allow this, at least for the Text widget.

I think we should probably put a little more effort in to determining whether an effect like this is already possible given the primitives that exist today.

is this what you guys are looking for ?


HCIBox Bicep fails on CustomScriptExtension

Is your issue related to a Jumpstart scenario, ArcBox, HCIBox, or Agora?

HCIBox
Describe the issue or the bug

When running the Bicep script, the deployment fails on HCIBox-Client/Bootstrap with the following error:
{"customHtml":{"htmlTemplate":"VM has reported a failure when processing extension 'Bootstrap' (publisher 'Microsoft.Compute' and type 'CustomScriptExtension'). Error message: 'Command execution finished, but failed because it returned a non-zero exit code of: '1'. The command had an error output of: 'The system cannot find the file specified.\r\n''. More information on troubleshooting is available at <a target="_blank" class="msportalfx-ext-link" href="https://aka.ms/VMExtensionCSEWindowsTroubleshoot\">https://aka.ms/VMExtensionCSEWindowsTroubleshoot. ","viewModel":null}}
To Reproduce

A working deployment of all resources without errors
Environment summary

az 2.57.0
Have you looked at the Troubleshooting and Logs section?

Screenshots

Additional context

Looks like the Custom script extension could not find the Bootstrap.ps1 file. Did you use a different branch/repo for deploying by specifying the githubBranch and githubAccount parameters in your deployment?
Please share your parameters file used for deploy minus any user credentials.

You pointed me in the right direction.  I validated my parameters file and found an issue that I corrected.  My subsequent deployment worked fine.  Feel free to close the issue.

Looks like the Custom script extension could not find the Bootstrap.ps1 file. Did you use a different branch/repo for deploying by specifying the githubBranch and githubAccount parameters in your deployment?
Please share your parameters file used for deploy minus any user credentials.


Llama 3 Models

Bounty locked.
They changes the tokenizer?
Can you test the 70B model?

They changed the tokenizer?

Yeah, the actual model changes are pretty minimal

Can you test the 70B model?

No I don't have enough memory

They changed the tokenizer?

Yeah, the actual model changes are pretty minimal

Just to clarify, I diffed model.py in both repos and aside from comments, and one minor change (ParallelEmbeddings was changed to VocabParallelEmebeddings which i think just masks the tensor for each gpu instead of sharding it)  they are exactly the same. Only the tokenizer change is needed for full support in tinygrad.

I'll test 70B tomorrow, if it's good, bounty is yours.

Assuming benchmark tests pass on master, bounty is yours!
Can pay via PayPal or USDC, reach out to<EMAIL_ADDRESS>to claim

Sent


Update checklist.md

I added this line because this is the second time a partner has stopped the entire pull request process due to thinking they need to test every single command. Hopefully, future partners will read that line and know that is not the case. @ShahafBenYakir let me know if this is fine or if there is a better way to word it. Thank you!!! :)

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

@marcellarichmond this is waiting on you to merge; Does it look ready?

Yes, approved! Sorry I accepted the proposed changes from @ShahafBenYakir and thought that would do it. Let me know what else to do plz!


[Model] Update Molmo Eval to Match Official Implementation

Changes:

Process up to max 36 crops per image instead of 12 crops in default setting.
Integrate prompts from the official Molmo implementation to match the reported numbers in the paper. (https://molmo.allenai.org/paper.pdf).

@kennymckormick  Could you take a look at this PR?

Hi, @jamespark3922 ,
Will merge this PR after validating the implementation with 1 model.

[ ] TODO: Re-evaluate Molmo Series


Cleanup master

Various spelling and formatting improvements to pass go vet.

Codecov Report

Merging #612 into master will not change coverage.
The diff coverage is 50%.

@@           Coverage Diff           @@
##           master     #612   +/-   ##
=======================================
  Coverage   56.95%   56.95%
=======================================
  Files          35       35
  Lines        2472     2472
=======================================
  Hits         1408     1408
  Misses        775      775
  Partials      289      289

Impacted Files
Coverage Δ

core/client/kt/requests.go
0% <0%> (ø)
:arrow_up:

core/keyserver/keyserver.go
42.68% <0%> (ø)
:arrow_up:

core/authentication/fake.go
67.85% <75%> (ø)
:arrow_up:

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 b717b47...530d50f. Read the comment docs.


Revert "Bump pyrsistent from 0.19.2 to 0.19.3 in /config/python"

Reverts SAP-samples/btp-setup-automator#375
Must be to dev branch

Removed - manual adjustment of dev branch


Suggestion: @prettier flag

I think it would be helpful to provide a way to programmatically include/exclude the js files that the cli scans. Sure, we love the work prettier does, but sometimes we have some code that we simply wish not to be changed. In order to achieve that with the current setup, one would need to separate the files and place them into different folders, prettify the directory with the code meant to be prettified, then merge back the two folders. As you can see, this is not practical at all. I believe this is a common use case and it should be addressed at an initial stage.
How can we approach this?
// @prettier
Similar to Flow, the cli would only format the files that include this annotation at the top of the file. This opens the door for some other features to be implemented later on, maybe .prettierconfig at some point? it is too early to tell at this stage of the project i think. Complexity-wise, this option takes away some of the ease that comes along with prettier, now we would have to annotate each file in our project.
Note: if this is the way to go, then this case should be addressed:
// @flow
// @prettier

or maybe combine into one line? // @flow @prettier, i like this one better but not sure how easy it is to implement. I think this would be a first, having to deal with multiple annotations in this fashion.
The other way that i can think of is /* prettier-disable */, which has similar characteristics to the previous approach. Think of Flow comments vs. ESlint comments.
Interested in hearing your thoughts on this.

I believe this is a common use case and it should be addressed at an initial stage.

This is what I disagree on. This should not be a common case at all; the whole point of this project is to force consistency. There are times when you may want an escape hatch, and that's already being discussed in #120 so we should probably move this discussion there.

What is proposed in the other issue is similar to what i had in mind, something like
// do stuff ..
/* prettier-enable */

There are times when you may want an escape hatch

This is actually a more accurate description, exactly is what i think it should be addressed.
I have no further comments, and we can move the discussion there, feel free to close this issue.

@sonaye See also: #579


Re-enable unit tests

Clone of https://github.com/EasyPost/easyvcr-csharp/pull/26

Heh you could have fixed the branch name without creating a new PR by renaming it locally and pushing that to the remote.

Heh you could have fixed the branch name without creating a new PR by renaming it locally and pushing that to the remote.

That's how I got into this mess in the first place...


About parameter settings

bro, what's your pytorch version?
when i try to use your trained-models named as 'model_43.pth' and 'model_50.pth' , error occur.
RuntimeError: version_number <= kMaxSupportedFileFormatVersion INTERNAL ASSERT FAILED at /pytorch/caffe2/serialize/inline_container.cc:131, please report a bug to PyTorch. Attempted to read a PyTorch file with version 3, but the maximum supported version for reading is 1. Your PyTorch installation may be too old. (init at /pytorch/caffe2/serialize/inline_container.cc:131)

version of my pytorch is 1.2.0

I tested on PyTorch 1.6.0, it should be good for PyTorch verion>1.4.0. I uploaded a model_50.zip file as a backup for the downloading issues from different systems. Can you try to unzip it and to try again?


CI integration (--check option)

Could we have an option for CI?
Example: deptry --check  .
If it has done already, where I can find an example of CI integration?

This should be simply
deptry .

It will return exit code 1 if issues are found, and exit code 0 if no errors are found.
Does this answer your question? I realise this is not specified in the documentation, I will see how to incorporate this information there.

Yes thank you, I will test with Gitlab CI!


Remove autojoin feature

Main Client was updated for autojoin support in side servers

You might want to wait until the client is updated so the new code takes effect.