bug?: react-query implementation when POST is used it always transforms into useMutation while for some cases its a useQuery for us!

Hi, i noticed when my endpoint is POST the tooling generates a useMutation implementation, while for us it's really a useQuery.
Since we can't dictate how the api's should be setup (POST has been chosen as a security measurement for this particular case), I was wondering if there is a way to tell the tooling which implementation to use for specific endpoints/methods?

Hey @maapteh it's not possible for now. I would it to add an options for it

I think you can also use override to create a useQuery for a specific operationId (in this case FindUsers).
We have a similar case and solve it like this:
import { defineConfig } from 'orval';

import openApiSpec from './apiSpecs/swagger.json';

export default defineConfig({
    [openApiSpec.info.title]: {
        output: {
            clean: true,
            client: 'react-query',
            headers: true,
            mode: 'tags-split',
            override: {
                operations: {
                    FindUsers: {
                        query: {
                            useQuery: true,
                        },
                    },
                },
            },
            target: 'src/services/generated/api.ts',
            tsconfig: 'tsconfig.json',
        },
        input: {
            target: 'apiSpecs/swagger.json',
        },
    },
});

Thanks, @reichhartd. Completely forgot that I did that 😅

sorry if I poke everyone watching this thread but I wonder if there is a way to generate both useQuery, useMutation with custom name as right now overriding with both useMutation and useQuery are true give out hook with same name

@landtee i suggest opening a Discussion in the Discussion area and provide your example config and what its generating and what you would like it to generate.


Tree widget: Failure to create filtering dialog in specific case

http://localhost:3000/?iTwinId=a6cabd79-a9e1-4e9a-9be3-b24d865a520d&iModelId=0848d581-c988-4fec-9763-344f8470a5d9

If this is specific to External Sources tree, then the issue can be moved to https://github.com/iTwin/viewer-components-react/milestone/12.


Updated WinRM requirements to connect to EXO

https://github.com/MicrosoftDocs/office-docs-powershell/issues/5765
https://github.com/MicrosoftDocs/office-docs-powershell/issues/5515
WinRM is not required, it could be disabled. WinRM basic auth must be enabled, but you cannot run "winrm get" and "winrm set" if WinRM is disabled.
Tested it on a new Win 10 machine, I can connect to EXO PS without any intervention. WinRM was disabled but WinRM basic auth was enabled. I couldn´t run "winrm get" and "winrm set".
Tested it on a new Win 8.1 machine, I can connect to EXO PS  without any intervention. WinRM was enabled and WinRM basic auth was enabled. I can run "winrm get" and "winrm set".
I´m thinking that we can also move "If Basic authentication for WinRM is disabled, you'll get this error when you try to connect:" between the first sentence about WinRM basic auth and the second sentence because it´s enabled by default.
Maybe something like:

WinRM needs to allow Basic authentication (it's enabled by default). We don't send the username and password combination, but the Basic authentication header is required to transport the session's OAuth token, since the client-side WinRM implementation has no support for OAuth.
If Basic authentication for WinRM is disabled, you'll get this error when you try to connect:

The WinRM client cannot process the request. Basic authentication is currently disabled in the client configuration. Change the client configuration and try the request again.

To enable Basic authentication for WinRM, run the following commands in a Command Prompt:
winrm quickconfig
winrm set winrm/config/client/auth @{Basic="true"}

Note: WinRM service can be disabled after you enable Basic authentication.

What do you think @chrisda?

Docs Build status updates of commit 0a53bca:
:clock10: Full build: the average full build time is 18 min(s) 9 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit 0a53bca:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/docs-conceptual/exchange-eop/connect-to-exchange-online-protection-powershell.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/docs-conceptual/exchange-online/connect-to-exchange-online-powershell/connect-to-exchange-online-powershell.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/docs-conceptual/exchange-online/connect-to-exchange-online-powershell/mfa-connect-to-exchange-online-powershell.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/docs-conceptual/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/docs-conceptual/office-365-scc/connect-to-scc-powershell/connect-to-scc-powershell.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/docs-conceptual/office-365-scc/connect-to-scc-powershell/mfa-connect-to-scc-powershell.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 48075f2:
:clock10: Full build: the average full build time is 18 min(s) 9 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit 48075f2:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/docs-conceptual/exchange-eop/connect-to-exchange-online-protection-powershell.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/docs-conceptual/exchange-online/connect-to-exchange-online-powershell/connect-to-exchange-online-powershell.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/docs-conceptual/exchange-online/connect-to-exchange-online-powershell/mfa-connect-to-exchange-online-powershell.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/docs-conceptual/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/docs-conceptual/office-365-scc/connect-to-scc-powershell/connect-to-scc-powershell.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/docs-conceptual/office-365-scc/connect-to-scc-powershell/mfa-connect-to-scc-powershell.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Fix smoke-tests to use new ingestor

Ran in concourse and build succeded in a expected time with pull request https://github.com/cloud-gov/deploy-logs-opensearch/pull/57


ci: add new workflows, continuous deployments

Description

Updates the explorer workflow name to CI/CD
The CI/CD workflow now enables continuous deployments to the staging and production environments with approval release-gates.
Adds a new workflow called deploy, which allows you to deploy any tag or branch to the staging and production environments
Updates the README to include status badges for the CI/CD workflow, and for the ArgoCD Explorer staging and production apps

Closes https://github.com/hirosystems/devops/issues/713
Type of Change

[ ] New feature
[ ] Bug fix
[ ] API reference/documentation update
[x] Other

Does this introduce a breaking change?
No.
Are documentation updates required?
No.
Testing information
Example workflow run here.
Checklist

[x] Tag 1 of @aulneau

@aulneau You can try approving the manual deploy gate to deploy to the k8s staging environment here:
https://github.com/blockstack/explorer/actions/runs/919649832
Currently anyone from UX or DevOps is able to approve these deployment gates, but this can easily be changed. We can also allow more people to approve deployments to the staging env and place more restrictions on who can approve a prod deployment.
There is an annotation at the bottom of the workflow's Summary page denoting the docker tag which will be deployed for each environment. For the link above, it's the ci-auto-deployments docker tag, which was automatically built and pushed up to the Docker hub in a previous job from this workflow.
Once a deploy gate is approved and opened, the specified Docker tag will be deployed to the environment within a few minutes.
With this CI/CD workflow, you'll have the option of approving a deploy gate and deploying to the staging environment for every push to any branch for this repo. The CI/CD workflow will only allow present the deploy gate for production when it's triggered from a new tag as part of the standard release process.
If you want to deploy a different branch or older tag to production for any reason, you can manually invoke the new deploy workflow.

:tada: This PR is included in version 1.12.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Track the requirements

Prerequisites

[X] I have written a descriptive issue title
[X] I have searched existing issues to ensure the feature has not already been requested

🚀 Feature Proposal
After #8 we should document in a more clear way the requirements for the project to adopt the reusable workflow.
For example:

npm test should not run the linter
the lint script should run all the linters

Motivation
I think in future the requirements will grow up, so we should start listing it before it will be too late to understand how to set up a repository
Example
No response

Totally agree with you.
I have a couple of "standard" npm scripts I use across my projects that improve the overall DX:
"ci:test": "npm run coverage && npm run test:types",
"coverage": "npm run unit -- --coverage-report=lcovonly",
"lint": "standard",
"lint:fix": "standard --fix",
"test": "npm run lint && npm run unit && npm run test:types",
"test:types": "tsd"
"unit": "tap -J \"test/**/*.test.js\"",
"unit:errors": "npm run unit -- -R terse",
"unit:report": "npm run unit -- --coverage-report=html",
"unit:verbose": "npm run unit -- -Rspec"

Just to add, this was partially discussed in the fastify/plugins Discussions last year.
Throwing all of the tests into the test script would be ideal (as @darkgl0w's example shows), as this the standard name for test scripts, with a separate lint script for... linting.

@Fdawgs something like this then ?
"coverage": "npm run unit -- --coverage-report=lcovonly", // useful to generate coverage report to be used with code coverage services
"lint": "standard",
"lint:fix": "standard --fix",
"test": "npm run coverage && npm run test:types", // target: ci run
"test:dev": "npm run lint && npm run unit && npm run test:types", // target: pre-commit run on user workflow (e.g.: my use case)
"test:types": "tsd"
"unit": "tap -J \"test/**/*.test.js\"", // just run the test suite
"unit:errors": "npm run unit -- -R terse", // run the test suite and display only errors (thanks to James Sumners that's now one of my best friends 😛)
"unit:report": "npm run unit -- --coverage-report=html", // useful to track the code coverage
"unit:verbose": "npm run unit -- -Rspec" // useful to track down tests failures and maintain a good DX (test descriptions, operations, plans ... etc)

Just to add, this was partially discussed in the fastify/plugins Discussions last year.
Throwing all of the tests into the test script would be ideal (as @darkgl0w's example shows), as this the standard name for test scripts, with a separate lint script for... linting.

test script is used for pre-commit hooks. For test only, it should go for unit.

test script is used for pre-commit hooks. For test only, it should go for unit.

This is how I use it on my workflow, I split each operations on dedicated scripts and in addition I have a CI dedicated script.

update
we can solve this by allowing the customization of the script names to run (fallback to test).
https://github.com/darkgl0w/fastify-swagger/blob/exp-alt/.github/workflows/ci.yml
custom test script name CI run

@fastify/plugins, if we can decide on what name the CI test script should have, as discussed in comments above, then this can get moving and can be applied to more plugin repos.

test:ci would be the correct name. And it should include -R terse.

I think there are two topics:

the scripts needed for the workflow
the scripts needed by the developer

The first one requires:

lint: to run once the lining as optimization
test: run the test (usually lint+test+types). It is optimized for automation and reporting

I think we should not use test:ci because we are not talking about a complex application, but a simple node.js module. So, adding a dedicated script may lead to running out of sync the test and test:ci commands.
The latter is for us: it helps us to remember simple commands:

lint:fix
test:unit: runs just the test
test:types

The other stuff adds too much noise into the scripts tag in my opinion.

@Eomm I'd say this is done? All package files in the repos have a lint and test besides the following:

benchmarks has a test script but no lint script
pacchetto has a lint script but no test script
website has a lint script but no test script


Cannot create object of type "System.Version". "Major" is a ReadOnly property when sorting apps.

My dependency graph looks like the following
Current App -> App A
Current App -> App B -> App A
All Apps where correctly downloaded.
App A was successfully published once.
I'm getting the following error when installing the second app.
##[error]RunPipeline action failed. Error: Cannot create object of type "System.Version". "Major" is a ReadOnly property. Stacktrace: at <ScriptBlock>, C:\Users\runneradmin\AppData\Local\Temp\d98c78a8-eec1-4a70-95df-4701035f9485\BcContainerHelper\AppHandling\Sort-AppFilesByDependencies.ps1: line 155 at Sort-AppFilesByDependencies, C:\Users\runneradmin\AppData\Local\Temp\d98c78a8-eec1-4a70-95df-4701035f9485\BcContainerHelper\AppHandling\Sort-AppFilesByDependencies.ps1: line 148 at Publish-BcContainerApp, C:\Users\runneradmin\AppData\Local\Temp\d98c78a8-eec1-4a70-95df-4701035f9485\BcContainerHelper\AppHandling\Publish-NavContainerApp.ps1: line 143 at Publish-BcNuGetPackageToContainer, C:\Users\runneradmin\AppData\Local\Temp\d98c78a8-eec1-4a70-95df-4701035f9485\BcContainerHelper\NuGet\Publish-BcNuGetPackageToContainer.ps1: line 32 at <ScriptBlock>, C:\Users\runneradmin\AppData\Local\Temp\d98c78a8-eec1-4a70-95df-4701035f9485\BcContainerHelper\NuGet\Publish-BcNuGetPackageToContainer.ps1: line 29 at Publish-BcNuGetPackageToContainer, C:\Users\runneradmin\AppData\Local\Temp\d98c78a8-eec1-4a70-95df-4701035f9485\BcContainerHelper\NuGet\Publish-BcNuGetPackageToContainer.ps1: line 28 at <ScriptBlock>, D:\a\_actions\microsoft\AL-Go-Actions\v2.2\RunPipeline\RunPipeline.ps1: line 322 at <ScriptBlock>, D:\a\_actions\microsoft\AL-Go-Actions\v2.2\RunPipeline\RunPipeline.ps1: line 308 at <ScriptBlock>, C:\Users\runneradmin\AppData\Local\Temp\d98c78a8-eec1-4a70-95df-4701035f9485\BcContainerHelper\AppHandling\Run-AlPipeline.ps1: line 1051 at <ScriptBlock>, C:\Users\runneradmin\AppData\Local\Temp\d98c78a8-eec1-4a70-95df-4701035f9485\BcContainerHelper\AppHandling\Run-AlPipeline.ps1: line 1038 at <ScriptBlock>, C:\Users\runneradmin\AppData\Local\Temp\d98c78a8-eec1-4a70-95df-4701035f9485\BcContainerHelper\AppHandling\Run-AlPipeline.ps1: line 763 at Run-AlPipeline, C:\Users\runneradmin\AppData\Local\Temp\d98c78a8-eec1-4a70-95df-4701035f9485\BcContainerHelper\AppHandling\Run-AlPipeline.ps1: line 728 at <ScriptBlock>, D:\a\_actions\microsoft\AL-Go-Actions\v2.2\RunPipeline\RunPipeline.ps1: line 344 at <ScriptBlock>, D:\a\_temp\d6d6865d-b8d6-4b3b-86df-b6d1156bafd9.ps1: line 1 at <ScriptBlock>, <No file>: line 1

This is the offending line https://github.com/microsoft/navcontainerhelper/blob/d26c9cfbf7caa30e1543121b3e50d7b6ce09e04e/AppHandling/Sort-AppFilesByDependencies.ps1#L155
But im not sure why its throwing this error. Maybe it was converted to a [System.Version] in this line?
https://github.com/microsoft/navcontainerhelper/blob/d26c9cfbf7caa30e1543121b3e50d7b6ce09e04e/NuGet/Publish-BcNuGetPackageToContainer.ps1#L29

Have a repro

fix is ready in prerelease

fix is ready in prerelease

Is prerelease the new preview?

same thing -allowprerelease = preview

The error is now fixed. Thanks


fix(plugin-feature): make setBundledFeatures merge each toggle object

can this be closed?

Yes, this can be closed, it was merged in this larger PR https://github.com/ciscospark/spark-js-sdk/pull/589


Added shuffle text animation #27

What is the change?
I added the shuffle text animation here.
Related issue?
closes: #27
Checklist:
Before you create this PR, confirm all the requirements listed below by checking the checkboxes [x]:

[x ] Have you followed the Contribution Guidelineswhile contributing.
[ x] Have you checked there aren't other open Pull Requests for the same update/change?
[ ] Have you made corresponding changes to the documentation?
[x] Have you tested the code before submission?
[x] Have you formatted your code ? (You can use any html,css beautifier)
[x] My changes generates no new warnings.
[x ] I'm Hacktoberfest'21 contributor.

GIF/video of the working of component you created:
Add here the GIF you created.

And don't give spaces in folder name. Give a hyphen

Are you done? Shall I review it?

Yes I am done. Actually I saw the second comment later so I made another commit for that.

Add ur component name to general readme : here
https://github.com/siddhi-244/Embellish/tree/main/HTML%2BCSS%2BJS

Let me know once you are done


Support GPU and autobatch

Codecov Report

Merging #1123 (be4cdfc) into main (b121a8f) will increase coverage by 0.27%.
The diff coverage is 62.10%.

:exclamation: Current head be4cdfc differs from pull request most recent head fd9dea0. Consider uploading reports for the commit fd9dea0 to get more accurate results

@@            Coverage Diff             @@
##             main    #1123      +/-   ##
==========================================
+ Coverage   56.59%   56.86%   +0.27%
==========================================
  Files         122      127       +5
  Lines        5976     6269     +293
  Branches     1037     1084      +47
==========================================
+ Hits         3382     3565     +183
- Misses       2393     2493     +100
- Partials      201      211      +10

Impacted Files
Coverage Δ

towhee/__init__.py
65.71% <ø> (ø)

towhee/dataframe/array/array.py
62.16% <0.00%> (ø)

towhee/engine/operator_loader.py
70.00% <ø> (ø)

towhee/engine/operator_runner/__init__.py
44.00% <0.00%> (-1.84%)
:arrow_down:

towhee/engine/thread_pool_task_executor.py
57.44% <0.00%> (ø)

towhee/operator/torch_model_handler.py
0.00% <0.00%> (ø)

towhee/serving/__init__.py
20.00% <20.00%> (ø)

towhee/engine/operator_context.py
34.69% <25.00%> (-0.09%)
:arrow_down:

towhee/operator/base.py
63.20% <28.00%> (-10.29%)
:arrow_down:

towhee/engine/operator_pool.py
36.84% <50.00%> (ø)

... and 10 more

Continue to review full report at Codecov.

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


allow user to specify raster cell size to use on import

Need: a lot of times we are given rasters with cell resolution that is too large or too small for accurate planning.  There's a sweet spot that gives you good accuracy when overlapping with a sketch, but not too detailed.
Once we've switched to using an equal area projection that is in meters, we ccould let the user specify what the resolution should be after import (e.g. 500 meters).  And gdal will resample to that size using the -tr option.
https://gdal.org/programs/gdalwarp.html#cmdoption-gdalwarp-tr
Consider adding this via an open-ended gdalWarpParams string property for each datasource that gets inserted into the gdalWarp command onimport, so that any number of custom options can be added.  Could even support an open ended Record of which gdalWarpParams is just one possibility.

We may run into trouble with sum calculations here. While increasing resolution will make our area calculations more accurate, I'm not sure there's an easy way to warn against doing any sum calculations on imported rasters that have the cell size adjusted.

@avmey  You're right the cell values would need to be adjusted, I think it's what's called disaggregation.  Most likely scenario is user would either want to:

split each large cell value equally amongst the smaller cells, say if the value was total abundance, so that the total sum stays the sum
keep the parent cell value, for example if the cell represented water depth.

This is ringing some bells for me and reminds me that Daniel is working on a "virtual resampling" feature for Geoblaze that could potentially avoid needing to adjust resolution up front - https://github.com/GeoTIFF/geoblaze/pull/228/files.  And comment in ticket - https://github.com/seasketch/geoprocessing/issues/156#issuecomment-1468029281
I'm not sure if GDAL can do that easily within a single command or even multiple.

I see this utility - https://github.com/GEMScienceTools/spatial-disaggregation
discussion of doing it with R - https://stackoverflow.com/questions/73295157/disaggregate-raster-value-to-finer-cells-equally

Closed in favor of #284


how to view the schema and execute graphql query/mutation

Hi, I've just installed this plugin, but can you show me how to view the schema (same as goto definition) and how to execute graphql query/mutation

Hi, sorry for the delay in replying to your issue.
This extension is a sample coc-extension to get the vscode-graphql equivalent working in coc.nvim. As such, I have not actually used it and cannot support it.


Add documentation GHA

Following the pattern used in the anax and mgmt-hub repos, implement a GHA to copy the docs in this repo's /docs folder to the appropriate path in the documentation repo (open-horizon.github.io) under /docs/???
@johnwalicki Do you have a preference for the path?  Do we match the pattern in mgmt-hub where the web path does not match the repo name?  /docs/fdo
Or do you prefer that they match?  /docs/FDO-support

/docs/fdo is simpler.
You would start with the GHA over in the devops repo
https://github.com/open-horizon/devops/blob/master/.github/workflows/copy-docs.yml

The CopyDocs GHA ran successfully and copied the docs/ files from this repo to the open-horizon.github.io repo.
Pages copied to https://github.com/open-horizon/open-horizon.github.io/tree/master/docs/fdo


Typography misses styles after update to beta 16

I got an issue with every Typography I'm using, the most evident that I'm proposing is the one used as App Bar title.
Expected Behavior

With 1.0.0-beta.13 I got this title

Current Behavior

After updating to 1.0.0-beta.16 the same App Bar behaves like this

Steps to Reproduce (for bugs)

Use the code shown https://material-ui-next.com/demos/app-bar/ with 1.0.0-beta.13
Update to 1.0.0-beta.16
See the changes

p.s. to downgrade simply run npm install<EMAIL_ADDRESS>Context

Your Environment

Tech
Version

Material-UI
1.0.0-beta.16

React
16

browser
Safari

etc

Your issue has been closed because it does not conform to our issue requirements.
Please provide a reproduction test case. This would help a lot 👷 .
A live example would be perfect. This codesandbox.io template may be a good starting point. Thank you!

@tommycarpi Something must be interfering with your config. The live docs examples are fine.

We have changed the font-size unit from px to rem. It means that the font size is impacted by the font size of the html element. It's helping with accessibility tools.

@oliviertassinari  I guess I found the problem, in my project I imported this
<link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/latest/css/bootstrap.min.css">
to load the css for some bootstrap components.
It looks like it conflicts with material-ui.

The following style from their CSS is definitely conflicting.
html{font-size:10px;


Acceptance Test Window Blank

I sync'd to the latest version of develop and ran the acceptance tests after following the steps in features/README (except for the step asking you to do it off of master)
The steps fail because the wallet simply loads a blank screen with no UI (despite no error in npm run hot-server (finished with webpack: Compiled successfully.)
npm run dev still works as expected.
Any idea how to debug this?

This build is on Ubuntu-64bit if that changes anything

Any errors in the Electron console @SebastienGllmt?

I tried rerunning the steps and now looking at it, I didn't notice that step the following step in features/README.md failed

Link your backend build with the Daedalus frontend (assumed that you have build the backend previously):

$ cd daedalus/node_modules/
$ npm link daedalus-client-api

It fails with 404 Registry returned 404 for GET on https://registry.npmjs.org/daedalus-client-api.
I think this is because there was a missing step where I had to run scripts/build-installer-unix.sh
After running the build using ./scripts/build-installer-unix.sh 1.0.3769 develop (not sure if the arguments are right but it worked)
I now get npm ERR! enoent ENOENT: no such file or directory, open '/home/sebastien/Documents/git/daedalus/node_modules/daedalus-client-api/package.json' (that is to saw the folder only contains node_modules/daedalus-client-api/node_modules
Any idea what is missing? Does this mean you can't run tests on changes that haven't been pushed to a branch on this repo?

Hey @SebastienGllmt I have the same problem, Now I have soved.
Check this path: /home/(yourUSER)/.config/Electron if your user have access. I set chown -R yourUser:yourUser /home/(yourUSER)/.config ... after  I ran npm install && npm run build
Then: npm run start
or
npm run dev
after that Daedalus appear well.


feat: base impl for GasUp + tests

Unsure why tests fail, they pass locally 🤔 will take another look tomorrow

I will re-add the missing address and deploy the contract to production in this PR, so we can merge it all together in one commit.


zabbix-server and zabbix-web

https://github.com/EpicMorg/docker-scripts/commit/e0c97f33f333eec79e9a1dd8154e33a374405d40


deleting charts folder from auditevent repo

Desc:

I've copied audittail helm chart library to dedicated new repository under [metal-toolbox/k8s-audittail/] So, deleting charts folder here for clean up

Deleting ci pipeline jobs i.e. are helm-library-ci.yml and helm-release.yml

It's not needed we are not using any values from "values.yaml" file so we are removing here.

Codecov Report

Merging #136 (0f48aaa) into main (a7dcfdf) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #136   +/-   ##
=======================================
  Coverage   97.04%   97.04%
=======================================
  Files          10       10
  Lines         338      338
=======================================
  Hits          328      328
  Misses          7        7
  Partials        3        3

Flag
Coverage Δ

unittests
97.04% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Non Descriptive Crash Traces.

Some Traces thrown from plugins are very opaque on the cause of the crash, or am I missing something here ?
app.cash.zipline.ZiplineException: CompletionHandlerException: Exception in completion handler InvokeOnCompletion@4[job@5] for DeferredCoroutine{Completed}@5
                                                                                at captureStack (runtime/coreRuntime.kt:12)
                                                                                at CompletionHandlerException (mnt/agent/work/44ec6e850d5c63f0/kotlinx-coroutines-core/common/src/Exceptions.common.kt:1813)
                                                                                at notifyCompletion (mnt/agent/work/44ec6e850d5c63f0/kotlinx-coroutines-core/common/src/JobSupport.kt:158)
                                                                                at completeStateFinalization (mnt/agent/work/44ec6e850d5c63f0/kotlinx-coroutines-core/common/src/JobSupport.kt:325)
                                                                                at finalizeFinishingState (mnt/agent/work/44ec6e850d5c63f0/kotlinx-coroutines-core/common/src/JobSupport.kt:236)
                                                                                at tryMakeCompletingSlowPath (mnt/agent/work/44ec6e850d5c63f0/kotlinx-coroutines-core/common/src/JobSupport.kt:910)
                                                                                at tryMakeCompleting (mnt/agent/work/44ec6e850d5c63f0/kotlinx-coroutines-core/common/src/JobSupport.kt:867)
                                                                                at <anonymous> (mnt/agent/work/44ec6e850d5c63f0/kotlinx-coroutines-core/common/src/JobSupport.kt:832)
                                                                                at <anonymous> (mnt/agent/work/44ec6e850d5c63f0/kotlinx-coroutines-core/common/src/AbstractCoroutine.kt:99)
                                                                                at <anonymous> (src/kotlin/coroutines_13/CoroutineImpl.kt:45)
                                                                                at <anonymous> (kotlin-kotlin-stdlib-js-ir.js)
                                                                                at <anonymous> (mnt/agent/work/44ec6e850d5c63f0/kotlinx-coroutines-core/common/src/internal/DispatchedTask.kt:112)
                                                                                at <anonymous> (mnt/agent/work/44ec6e850d5c63f0/kotlinx-coroutines-core/js/src/JSDispatcher.kt:155)
                                                                                at <anonymous> (mnt/agent/work/44ec6e850d5c63f0/kotlinx-coroutines-core/js/src/JSDispatcher.kt)
                                                                                at apply (native)
                                                                                at <anonymous> (runner/work/zipline/zipline/zipline/src/jsMain/kotlin/app/cash/zipline/GlobalBridge.kt:72)
                                                                                at <anonymous> (runner/work/zipline/zipline/zipline/src/commonMain/kotlin/app/cash/zipline/internal/GuestService.kt)
                                                                                at <anonymous> (zipline-root-zipline.js)
                                                                                at <anonymous> (runner/work/zipline/zipline/zipline/src/commonMain/kotlin/app/cash/zipline/internal/bridge/InboundService.kt:53)
                                                                                at <anonymous> (runner/work/zipline/zipline/zipline/src/commonMain/kotlin/app/cash/zipline/internal/bridge/Endpoint.kt:99)
                                                                                at <anonymous> (zipline-root-zipline.js)
                                                                                at <anonymous> (runner/work/zipline/zipline/zipline/src/jsMain/kotlin/app/cash/zipline/GlobalBridge.kt)
                                                                                at <anonymous> (zipline-root-zipline.js)
                                                                                Suppressed: DiagnosticCoroutineContextException: [DeferredCoroutine{Completed}@5, SetTimeoutDispatcher@3]
                                                                                at captureStack (runtime/coreRuntime.kt:12)
                                                                                at DiagnosticCoroutineContextException (mnt/agent/work/44ec6e850d5c63f0/kotlinx-coroutines-core/js/src/internal/CoroutineExceptionHandlerImpl.kt:8709)
                                                                                at handleUncaughtCoroutineException (mnt/agent/work/44ec6e850d5c63f0/kotlinx-coroutines-core/common/src/internal/CoroutineExceptionHandlerImpl.common.kt:46)
                                                                                at handleCoroutineException (mnt/agent/work/44ec6e850d5c63f0/kotlinx-coroutines-core/common/src/CoroutineExceptionHandler.kt:32)
                                                                                at <anonymous> (mnt/agent/work/44ec6e850d5c63f0/kotlinx-coroutines-core/common/src/AbstractCoroutine.kt:107)
                                                                                at notifyCompletion (mnt/agent/work/44ec6e850d5c63f0/kotlinx-coroutines-core/common/src/JobSupport.kt:158)
                                                                                ... and 21 more common stack frames skipped
                                                                                Caused by:     at captureStack (runtime/coreRuntime.kt:12)
                                                                                at ClassCastException_init_$Create$ (kotlin-kotlin-stdlib-js-ir.js)
                                                                                at THROW_CCE (runtime/hacks.kt)
                                                                                at <anonymous> (soundbound-extensions-lib.js)
                                                                                at <anonymous> (opt/buildAgent/work/b2fef8360e1bcf3d/formats/json/commonMain/src/kotlinx/serialization/json/internal/Polymorphic.kt:20)
                                                                                at <anonymous> (opt/buildAgent/work/b2fef8360e1bcf3d/core/commonMain/src/kotlinx/serialization/encoding/AbstractEncoder.kt:80)
                                                                                at <anonymous> (opt/buildAgent/work/b2fef8360e1bcf3d/core/commonMain/src/kotlinx/serialization/internal/CollectionSerializers.kt:68)
                                                                                at <anonymous> (kotlinx-serialization-kotlinx-serialization-core.js)
                                                                                at <anonymous> (opt/buildAgent/work/b2fef8360e1bcf3d/formats/json/commonMain/src/kotlinx/serialization/json/internal/Polymorphic.kt:20)
2023-11-07 23:30:07.725   813-891   Zipline                 in.shabinder.soundbound.preview      E  	at <anonymous> (opt/buildAgent/work/b2fef8360e1bcf3d/core/commonMain/src/kotlinx/serialization/encoding/AbstractEncoder.kt:80)
                                                                                at <anonymous> (commonMainSources/libraries/stdlib/src/kotlin/util/Preconditions.kt:1876)
                                                                                at <anonymous> (zipline-root-zipline.js)
                                                                                at <anonymous> (opt/buildAgent/work/b2fef8360e1bcf3d/formats/json/commonMain/src/kotlinx/serialization/json/internal/Polymorphic.kt:20)
                                                                                at <anonymous> (opt/buildAgent/work/b2fef8360e1bcf3d/core/commonMain/src/kotlinx/serialization/encoding/AbstractEncoder.kt:80)
                                                                                at <anonymous> (opt/buildAgent/work/b2fef8360e1bcf3d/core/commonMain/src/kotlinx/serialization/encoding/Encoding.kt:92)
                                                                                at <anonymous> (zipline-root-zipline.js)
                                                                                at <anonymous> (opt/buildAgent/work/b2fef8360e1bcf3d/formats/json/commonMain/src/kotlinx/serialization/json/internal/Polymorphic.kt:20)
                                                                                at encodeToDynamic_0 (opt/buildAgent/work/b2fef8360e1bcf3d/formats/json/jsMain/src/kotlinx/serialization/json/internal/DynamicEncoders.kt:42)
                                                                                at encodeToDynamic (opt/buildAgent/work/b2fef8360e1bcf3d/formats/json/jsMain/src/kotlinx/serialization/json/Dynamics.kt)
                                                                                at encodeToStringFast (runner/work/zipline/zipline/zipline/src/jsMain/kotlin/app/cash/zipline/internal/jsonJs.kt)
                                                                                at <anonymous> (runner/work/zipline/zipline/zipline/src/commonMain/kotlin/app/cash/zipline/internal/bridge/CallCodec.kt:56)
                                                                                at <anonymous> (runner/work/zipline/zipline/zipline/src/commonMain/kotlin/app/cash/zipline/internal/bridge/OutboundCallHandler.kt:99)
                                                                                at <anonymous> (runner/work/zipline/zipline/zipline/src/commonMain/kotlin/app/cash/zipline/internal/bridge/SuspendCallback.kt)
                                                                                at <anonymous> (zipline-root-zipline.js)
                                                                                at <anonymous> (runner/work/zipline/zipline/zipline/src/commonMain/kotlin/app/cash/zipline/internal/bridge/InboundService.kt:53)
                                                                                at <anonymous> (mnt/agent/work/44ec6e850d5c63f0/kotlinx-coroutines-core/common/src/JobSupport.kt)
                                                                                at <anonymous> (kotlinx.coroutines-kotlinx-coroutines-core-js-ir.js)
                                                                                at notifyCompletion (mnt/agent/work/44ec6e850d5c63f0/kotlinx-coroutines-core/common/src/JobSupport.kt:369)
                                                                                at completeStateFinalization (mnt/agent/work/44ec6e850d5c63f0/kotlinx-coroutines-core/common/src/JobSupport.kt:325)
                                                                                ... and 20 more common stack frames skipped
                                                                                at app.cash.zipline.internal.GuestService$Companion$Adapter$GeneratedOutboundService.runJob(GuestService.kt:23)
                                                                                at app.cash.zipline.internal.CoroutineEventLoop$DelayedJob$run$1.invokeSuspend(CoroutineEventLoop.kt:61)
                                                                                at app.cash.zipline.internal.CoroutineEventLoop$DelayedJob$run$1.invoke(Unknown Source:8)
                                                                                at app.cash.zipline.internal.CoroutineEventLoop$DelayedJob$run$1.invoke(Unknown Source:4)
                                                                                at kotlinx.coroutines.intrinsics.UndispatchedKt.startCoroutineUndispatched(Undispatched.kt:44)
                                                                                at kotlinx.coroutines.CoroutineStart.invoke(CoroutineStart.kt:112)
                                                                                at kotlinx.coroutines.AbstractCoroutine.start(AbstractCoroutine.kt:126)
                                                                                at kotlinx.coroutines.BuildersKt__Builders_commonKt.launch(Builders.common.kt:56)
                                                                                at kotlinx.coroutines.BuildersKt.launch(Unknown Source:1)
                                                                                at kotlinx.coroutines.BuildersKt__Builders_commonKt.launch$default(Builders.common.kt:47)
                                                                                at kotlinx.coroutines.BuildersKt.launch$default(Unknown Source:1)
                                                                                at app.cash.zipline.internal.CoroutineEventLoop$DelayedJob.run(CoroutineEventLoop.kt:58)
                                                                                at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
                                                                                at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:644)
                                                                                at java.lang.Thread.run(Thread.java:1012)

Thread with all details.
https://kotlinlang.slack.com/archives/C5HT9AL7Q/p1700181390990159?thread_ts=1691432897.694099&cid=C5HT9AL7Q

Any update ?
have been stuck on kotlin 1.9.10 and zipline 1.2.0, since above doesnt work. I am more than happy to provide info in any way possible or do a brief sync explaining the steps to repro same.
Case 1: ✅

Using zipline 1.2.0 host and jsSource both works fine.

Case 2: 🔴

used zipline 1.8.0 in host(android) and jsSources built with 1.2.0: StackOverflow (looped on below trace)

ZiplineServiceAdapterKt.descriptorName  refer below image for full trace
- So this breaks the promise done in readme for 1.x host and binary compatibility ⚠

Case 3: 🔴

used zipine 1.9.0 for both host and runtime jsBinaries, gave below hard crash

Fatal signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 0x7b7f130ff8 in tid 30292 (DefaultDispatch), pid 30209 (ndbound.preview) refer below image for full trace

After many iteration on finding out what works and what doesnt,
Below Commit is what makes the difference, with commit, plugins are loaded as expected, without, get stackOverflow error as shown.
https://github.com/Shabinder/zipline/commit/801b3d66cbe9ae2d51a44c7b272dff3c28409aa2
Shortlisted as much as I could, lmk if I can help or diagnose it more in any other way

So it seems like a type with a recursive descriptor. We can change the calculation to put in a placeholder character for when it recurses by keeping a set of seen types. Will have to try and reproduce, but should be pretty easy give what you've found out so far.

Got the same exception when using JsonElement as return type of a suspending ZiplineService method. JsonElement can be JsonArray, which in turn contains List, thus recursion appears. A big problem for us, as we wanted to use JsonElement as a return type to get abstract tree of analytics params this way.
This exception does not seem to appear when using JsonElement in return type of non-suspending functions or when using it in function parameters.

@JakeWharton  your hunch was r8, took time and dug in more today:
this is the class which ends in endless recursion
in.shabinder.soundbound.models.ThrowableWrapper(
message: kotlin.String,
stackTrace: kotlin.String,
cause: in.shabinder.soundbound.models.ThrowableWrapper?
)?


embed icon thingy

rtl makes it overlap. I don't mind turning off that option to click it, but it doesn't seem to be available. Sorry for all the issues, you're a lifesaver lol

The Obsidian team is working on much better native RTL support for version 1.6.0, which will make the RTL plugin much smaller in its scale (it will just add some missing functionality in the edges). Therefore I won't continue to work on plugin functionality that will become native soon, and as of the latest alpha that I'm helping the Obsidian team to test, this issue seems to not occur there :)


Error showing information on dashboard deploy widget

I have seen an error showing the
information in the widget of the deployments. When I click on a display, it shows something like this

The labels are not in the correct order with respect to the data.
Some help? Thanks in advance

Closing as this is a duplicate. See https://github.com/Hygieia/Hygieia/issues/2056


Fix package.json problems

Summary

Remove whitespace from license field
Correctly link to the github repo

This should fix these things on npm:

display of the number of issues/prs
link to the repo
license info

thanks @ThiefMaster


fix ReadTimeoutException: null

// Describe your PR here; eg. Fixes #issueNo
#1222
Make sure that:

[x] You have read the contribution guidelines.
[x] You submit test cases (unit or integration tests) that back your changes.
[x] Your local test passed mvn clean install -Dmaven.javadoc.skip=true.

Codecov Report

Merging #1225 (92bbb59) into master (000e54d) will decrease coverage by 0.51%.
The diff coverage is 0.00%.

@@             Coverage Diff              @@
##             master    #1225      +/-   ##
============================================
- Coverage     70.33%   69.82%   -0.52%
+ Complexity     2093     2084       -9
============================================
  Files           376      376
  Lines          8322     8317       -5
  Branches        903      901       -2
============================================
- Hits           5853     5807      -46
- Misses         2026     2063      +37
- Partials        443      447       +4

Impacted Files
Coverage Δ
Complexity Δ

...ugin/httpclient/HttpClientPluginConfiguration.java
21.87% <0.00%> (+1.58%)
3.00 <0.00> (ø)

...soul/client/tars/TarsServiceBeanPostProcessor.java
26.82% <0.00%> (-56.10%)
5.00% <0.00%> (-9.00%)

.../soul/plugin/httpclient/NettyHttpClientPlugin.java
57.14% <0.00%> (-2.05%)
10.00% <0.00%> (ø%)

...omara/soul/sync/data/http/HttpSyncDataService.java
73.52% <0.00%> (+0.98%)
12.00% <0.00%> (ø%)

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 000e54d...92bbb59. Read the comment docs.

please checked ci

There is still a problem

@linchuyao That is not a NullPointException.

why now timeOutException soul will response 500 errorCode

No particular reason. If you have a better suggestion, you can submit an issue to discuss this case. : )

There is still a problem

this pr exactly fix it


Develop

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

28 of 28 (100.0%)  changed or added relevant lines in 2 files are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-6.5%) to 93.478%

Files with Coverage Reduction
New Missed Lines
%

src/index.ts
2
0%

Totals

Change from base Build<PHONE_NUMBER>:
-6.5%

Covered Lines:
34

Relevant Lines:
36

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

28 of 28 (100.0%)  changed or added relevant lines in 2 files are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-6.5%) to 93.478%

Files with Coverage Reduction
New Missed Lines
%

src/index.ts
2
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
-6.5%

Covered Lines:
34

Relevant Lines:
36

💛  - Coveralls


allows to use multiple ownership transfer methods for own op

Codecov Report

Merging #279 (b64c1bc) into main (be75542) will decrease coverage by 0.52%.
The diff coverage is 39.21%.

@@            Coverage Diff             @@
##             main     #279      +/-   ##
==========================================
- Coverage   60.23%   59.71%   -0.53%
==========================================
  Files          64       64
  Lines        4059     4071      +12
==========================================
- Hits         2445     2431      -14
- Misses       1266     1295      +29
+ Partials      348      345       -3

Impacted Files
Coverage Δ

client/client.go
62.93% <ø> (ø)

client/core/getResource.go
31.81% <ø> (ø)

client/deviceOwnershipBackend.go
0.00% <0.00%> (ø)

client/deviceOwnershipNone.go
0.00% <0.00%> (ø)

client/refDevice.go
91.48% <ø> (ø)

client/core/ownDevice.go
55.08% <42.85%> (-0.88%)
:arrow_down:

client/deviceOwnershipSDK.go
45.56% <50.00%> (-8.28%)
:arrow_down:

client/options.go
45.03% <80.00%> (-1.06%)
:arrow_down:

client/ownDevice.go
40.90% <100.00%> (ø)

client/core/otm/manufacturer/client.go
48.83% <0.00%> (-27.91%)
:arrow_down:

... and 3 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Cropping box outside the image

Hi,
We are using this tool to enforce an upload of a specific ratio image.
When users initially select a larger image, and then select a smaller one the cropping box defaults outside of the image. See image. Should be reproducible easily.

Could you please check whether the adjustment made in fork https://github.com/hendrik-scholz/angular-img-cropper fixes the issue.


Root directory not expanding if empty and creating node

(sorry if you feel I'm spamming issues)
https://gyazo.com/b6132ba68fd554585baa4e959831f24f
Is this intended?

It's not intended, but I have never set an empty directory as root so that situation wasn't tested.

I finally tested this and I didn't experience this issue. Maybe it was fixed along the way. Can you give it another try and let me know if it is still an issue?

It seems to be fixed, I can't reproduce


Impala Query Editor + New Workflows = Sticky Bit Error Permissions

Hi,
We are facing some troubles when trying to run a Hive2Script over an Oozie Workflow after making a query over Impala Query Editor:
Both of them (query and .hql script) do the same:
USE user1;
DROP TABLE IF EXISTS data;
CREATE TABLE data....
The problem is:

First, Impala Query Editor creates the metadata (/user/hive/warehouse/user1.db/data) with user impala:hive
Then, Hive2Script in Workflow tries to manage the same metadata (/user/hive/warehouse/user1.db/data) with the user logged in HUE, in this case, user1:hive

We think that this is an inconsistency. Obviously, we can remove the sticky bit, give 777 permissions and everybody happy but say bye to any security.
(Hive warehouse folder and all databases created under it have the 1775 default permission).
Any help would be appreciate. Thanks.

Could you use the mailing list for this type of end user discussion?
http://groups.google.com/a/cloudera.org/group/hue-user
I would recommend to enable Impala impersonations that way everything is done as the logged-in user: http://gethue.com/use-the-impala-app-with-sentry-for-real-security/


refactor(papyrus_storage): add revert_events function that removes the references to the events of a block

This change is


fix(datepicker): format values received from external model changes

When ngModel.$render receives a value updated externally (that is, not as a response to a datepicker event, but some other model update) it does not actually apply configured formatting of any kind. It is assumed that the value is a string, but if it is an instance of Date then it is implicitly cast to a string and the element's value is set to that. This fix corrects the behavior by parsing it and applying local filters before assigning the element's value.

Would love to see this merged as well!

BTW, here's an example of the bug on jsFiddle
http://jsfiddle.net/uberspeck/4ht8y4nw/

FWIW, @DaveWM has a workaround in this thread...
https://github.com/angular-ui/bootstrap/issues/2659#issuecomment-60750976

As a side note...  if ng-minlength is added to the input field it breaks the datepicker.  Anybody have any ideas on what might be the cause of that?

Why hasn't this been merged yet?

@jessedhillon are you able to add a test for this PR?

Yeah, I'll try to get to it this weekend

Question: isn't this issue covered by the test at line 1316 in src/datepicker/test/datepicker.spec.js, custom format updates the input correctly when model changes?

Should be yes, I assume the test still passes?

Should it be merged now?

Yes - there's a Cherry Picking technique involved which I and other new maintainers are going to learn about in tonight's meeting.  I'm hoping that several PR's will start to get 'merged' over the coming weeks.

Sorry for the delay in response. Yes, it's passing the test in my branch. Looks like you already figured it out though! :+1:

Should be fixed in https://github.com/angular-ui/bootstrap/commit/5f9afe5a86af0e207eaacd6a9b1f202fd78d7009
Closing for now. Thanks to all


Display submitted message in report action

Details

We display the message submitted %amount% using the existing submittedAmount copy. In this way, we show the same message even if the expense report is submitted by the admin (where originally we were showing the message  You (on behalf of<EMAIL_ADDRESS>via admin-submit) submitted this report to you).
Fixed Issues

$ https://github.com/Expensify/App/issues/35263
Tests

Create a workspace and invite a member
Enable Delay submissions and set the frequency to Daily
Enable Add approvals.
[Member] Create a few expenses but don't submit them
[Admin] Submit the expense report
Verify the message submitted %amount% is displayed in both accounts

[ ] Verify that no errors appear in the JS console

Offline tests

N/A
QA Steps

Same steps from test section

[ ] Verify that no errors appear in the JS console

PR Author Checklist

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

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

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

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

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

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

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

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

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

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

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

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

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

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

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

why backend is sending that A (on behalf of you via admin-submit) submitted this report to A.

Ah, this is an old hardcoded message that we use for OldDot, and now we want to change it to submitted x.x. Also if we change the hardcoded message, we wouldn't be able to translate it in NewDot.

BUG: Web: Copy to clipboard does not copy submitted x.x. Instead whole string messages is copied.

Thanks for catching that, fixed and ready for another review

Friendly bump @parasharrajat

Oh cool, thanks for finding those issues. We're working on other high-priority items this week, and then I will look at them. Seems most of them are backend bugs

Backend PRs are in review, I will post again here when those are deployed

Hi @parasharrajat, the backend PRs have been merged. This PR is ready for review again

Friendly bump @parasharrajat

Thanks for catching that @parasharrajat! Fixed:
https://github.com/Expensify/App/assets/6829422/6a0413d1-bee1-49bc-9182-4c81eec6a68f

@marcochavezf I have a question about the avatar for the submitted message on the report header. Should this be the actor of the message or the user who created the report?
02.07.2024_16.09.42_REC.mp4

Yeah, in this case we should display the avatar of the user that submitted the report. I will check it out in a moment

Similarly, shouldn't LHN subtitle message be from Admin?

Ah good point, @trjExpensify what are your thoughts about this one? I see we have the same pattern for approved messages

The avatar issue is fixed now
https://github.com/Expensify/App/assets/6829422/c45adf55-c79d-40eb-b790-420d360798a6

Yeah, I agree that we can consider the LHN-related issue out of scope. Thanks!

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

🚀 Deployed to staging by https://github.com/blimpich in version: 9.0.5-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to staging by https://github.com/blimpich in version: 9.0.5-2 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
failure ❌

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/Julesssss in version: 9.0.5-13 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/thienlnam in version: 9.0.6-8 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


feat(ado/behavior): Add scanner/crawler inputs to the ADO task.json config

Details
Add the scanner/crawler inputs to the task config inputs.
Motivation

Context

Pull request checklist

[ ] Addresses an existing issue: Fixes #0000
[x] Added relevant unit test for your changes. (yarn test)
[x] Verified code coverage for the changes made. Check coverage report at: <rootDir>/test-results/unit/coverage
[x] Ran precheckin (yarn precheckin)
[x] (after PR created) The Accessibility Checks (pull_request) check should fail. All other checks should pass.

Codecov Report

Merging #820 (b70a653) into main (dbb5a43) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main     #820   +/-   ##
=======================================
  Coverage   87.90%   87.90%
=======================================
  Files          36       36
  Lines         686      686
  Branches       66       66
=======================================
  Hits          603      603
  Misses         83       83

Impacted Files
Coverage Δ

...s/ado-extension/src/task-config/ado-task-config.ts
100.00% <100.00%> (ø)

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 dbb5a43...b70a653. Read the comment docs.


Glitchy UI

When I try to run discline within tmux (within the Linux container from Crostini), the UI will flash and scroll up, before flashing and scrolling down again. This is not on a pattern, but when I type, the flashing happens with every keystroke.

Yep happends to me as well, even out of tmux session.
Is that because of the async way to do ?


Help parsing

@cathydeng thought on how to parse:
harborside financial center, plaza ii, 1st floor

it looks like harborside financial center is a business complex in NJ, and each of their buildings are named 'plaza N'. so maybe:
harborside
financial
center,
plaza
ii,
1st
floor

jk not PlaceName. instead of making a separate tag for building complexes, these should just all be tagged BuildingName
<BuildingName>harborside</BuildingName>
<BuildingName>financial</BuildingName>
<BuildingName>center,</BuildingName>
<BuildingName>plaza</BuildingName>
<BuildingName>ii,</BuildingName>
<OccupancyIdentifier>1st</OccupancyIdentifier>
<OccupancyType>floor</OccupancyType>

Thanks, what about this bad boy?!
215 n. loop 1604 e. apt 720

7490 n. cr 650 e.


Autosubmit Interval failling...

Hi, I have a service to send info to Librato in interval of each 5 minutes, yesterday I become to have the error {"errors":{"params":{"measure_time":["is too far in the past"]}},"request_time":1475920599}", everytime a long of one entire day.
My doubt is... How will the Librato gem send a value too old if my autosubmit_interval is equal to 5 minutes?
This is my service:
require 'librato/metrics'
require 'singleton'
class LibratoService
  include Singleton

  AUTOSUBMIT_COUNT=5
  AUTOSUBMIT_INTERVAL=5.minutes

  def initialize
    Librato::Metrics.authenticate(ENV['LIBRATO_EMAIL'], ENV['LIBRATO_API_KEY'])
    @queue = Librato::Metrics::Queue.new(autosubmit_interval: AUTOSUBMIT_INTERVAL)
    @aggregator = Librato::Metrics::Aggregator.new(autosubmit_interval: AUTOSUBMIT_INTERVAL)
  end

  def aggregator_watcher(metric, value)
    @aggregator.add("#{prefix_metric_name(metric)}" => value)
  end

  def latency_watcher(metric)
    @queue.time prefix_metric_name(metric) do
      yield
    end
  end

  def send_gauge(metric, value)
    Librato::Metrics.submit "#{prefix_metric_name(metric)}" => value
  end

  def send_metrics
    @queue.submit
    @aggregator.submit
  rescue Librato::Metrics::CredentialsMissing => e
    LoggingService.log(e.message)
  end

  private

  def prefix_metric_name(metric_name)
    "Notification.#{metric_name}"
  end
end

The "measure_time":["is too far in the past"] error is triggered if the time stamp submitted with the measurement is more than 2h behind wall time. Could it be that the clock on the server that is submitting the metrics has drifted?

this was my first thought, but there're no changes on the clock server and this service was working fine a couple months :confused:, you have another guess?

@pedrohenriquerls - just wanted to check back and see if you were able to get this resolved? That message actually gets parsed straight from the API response so the only way you should see it is if the specified time for the measurement is significantly in the past.
One possibility that occurs to me is that you could be adding metrics sporadically enough that your autosubmit is actually sending less frequently than every 5 mins. From the related docs:

...are driven by the addition of measurements. If you are adding measurements irregularly (less than once per second), time-based submission may lag past your specified interval until the next measurement is added.

We have had some people confused by this in the past. The autosubmit is only checked when you add a metric so if you are adding them rarely you may be submitting at longer windows than you think.
If this is the issue you can roll your own looped autosubmitter easily using something like this example or if you are wanting to report regularly via a background thread you may want to us something like librato-rack instead.

@pedrohenriquerls - going to go ahead and close this, feel free to follow up with<EMAIL_ADDRESS>or here if you have further issues.


Use Docker Registry cache backend

Summary
We were using the inline Docker cache for the Docker images produced by docker-publish-staging and docker-publish-release. The inline Docker cache bundles the cache metadata alongside the image (increasing its size) but it does not scale well with multi-stage builds (which we use).
Additionally, inline only supports mode=min – https://docs.docker.com/build/cache/backends/#cache-mode. This means that only the final layers which are exported (the last stage of the multi stage build) and therefore cached, resulting if fewer cache hits.
By using a registry cache backend (https://docs.docker.com/build/cache/backends/registry/), we can bundle the layers to be cached into a separate image, reducing the size of the staging/production images. A registry backend also supports mode=max which allows all the intermediary layers to be cached. This should improve the amount of cache hits that we get while building the staging and production images (thus reducing the time spent building each layer).
Changes

Change from inline to registry cache backend.
Use mode=max to cache all intermediary layers.
Use the external buildcache image as a cache reference for all the image layers (staging and production).
Extract the env to the workflow root (to make it easier to share the configuration between jobs).

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
3 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.03%) to 91.834%

Files with Coverage Reduction
New Missed Lines
%

src/routes/transactions/entities/tests/human-description.builder.ts
3
60.0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.03%

Covered Lines:
6892

Relevant Lines:
7239

💛  - Coveralls


Add em10mk4

The E-M10 Mark IV responds to a few commands differently than previous models (at least, as far as I've seen). I don't know how these commands will work with other camera models, but they work with mine.

I am trying to understand what these changes mean.
You broadcast the camera's liveview in order to take a picture? That seems odd. One would expect there should be other commands to take pictures that work outside the liveview. Btw, is the liveview still on after you take the picture or does taking a picture turn it off?
What exactly is the result of get_caminfo? From your code looks like not a single dict as expected in the code but a list of at least 3 dicts. Do the other dicts contain useful info?


Sleuth once request can't have the same trace_id?

hello, i am sorry 。
I have a question to consult you
when i use 1.3.3 sleuth, I have two micro services a and b,
like: the a port is 11016
@RequestMapping("/sservicea")
	public String sservicea() {
		LOG.log(Level.INFO, "calling trace service-b");
		return restTemplate.getForObject("http://localhost:11017/sserviceb", String.class);
	}

b:
@RequestMapping("/sserviceb")
	public String sserviceb() {
		LOG.log(Level.INFO, "calling trace service-c");
		return "OK";
	}

but i call http://localhost:11017/sservicea
i see the logs . there are two trace_id.
so zipkin can't draw the dependence Graph
sorry my enlisgh is bad.

You have a working example here - https://github.com/openzipkin/sleuth-webmvc-example. Just build your solution around what's explained there.

sorry you mistake me . the demo is working well use 1.3.0,but use 1.3.3 work  bad. once request but hava two trace_id

If you think that this is not working, please provide a sample that replicates the issue.

my demo is 3 parts
1 part:
main java
@EnableZipkinServer
@SpringBootApplication
public class ZipKinServerApplication {
public static void main(String[] args) {
	SpringApplication.run(ZipKinServerApplication.class, args);
}

}
pom:
<spring-boot.version>1.5.10.RELEASE</spring-boot.version>
<spring-cloud.version>Edgware.SR3</spring-cloud.version>

spring-boot-starter
spring-boot-starter-web
zipkin-autoconfigure-ui
zipkin-server
zipkin-autoconfigure-storage-mysql
spring-boot-starter-jdbc
mysql-connector-java
zipkin-autoconfigure-collector-rabbitmq

yml:
server:
port: 11011
zipkin:
collector:
rabbitmq:
addresses: localhost:5672
password: guest
username: guest
queue: zipkin
storage:
type: mysql
spring:
application:
name: zipkinserver
sleuth:
enabled: false
datasource:
name: zipkin
driver-class-name: com.mysql.jdbc.Driver
url: jdbc:mysql://localhost:3306/zipkin?autoReconnect=true&useUnicode=true&characterEncoding=UTF-8&zeroDateTimeBehavior=convertToNull&useSSL=false
username: root
password: 123456
schema: classpath:/zipkin.sql
initialize: true
continue-on-error: true
2 part  mircoserve A
main java
@RestController
@SpringBootApplication
public class SampleFeignApplication {
private static final Logger LOG = Logger.getLogger(SampleFeignApplication.class.getName());
@Autowired
private RestTemplate restTemplate;

@Bean
public RestTemplate getRestTemplate() {
	return new RestTemplate();
}

@Bean
public AlwaysSampler defaultSampler() {
	return new AlwaysSampler();
}

public static void main(String[] args) {
	SpringApplication.run(SampleFeignApplication.class, args);
}

@RequestMapping("/sservicea")
public String sservicea() {
	LOG.log(Level.INFO, "calling trace service-b");
	return restTemplate.getForObject("http://localhost:11017/sserviceb", String.class);
}

}
pom：
<spring-boot.version>1.5.10.RELEASE</spring-boot.version>
<spring-cloud.version>Edgware.SR3</spring-cloud.version>
spring-boot-starter
spring-cloud-starter-zipkin
spring-rabbit
yml：
server:
port: 11016
spring:
rabbitmq:
host: localhost
port: 5672
username: guest
password: guest
zipkin:
rabbitmq:
queue: zipkin
application:
name: sera
2 part  mircoserve B like A
just the functon has diff
@RequestMapping("/sserviceb")
public String sservicea() {
LOG.log(Level.INFO, "calling trace service-b");
return "ok";
}

No, please don't put the unformatted code in the issue. How am I supposed to even read it? Can you read what you pasted?
Upload your sample to Github. Also don't use the @enablezipkinserver. Have you read the documentation? This is deprecated. Please read the documentation, understand what you're doing. Read the sample that I've shown you and then I'm more than certain that everything will work for you.
Here you have another example https://github.com/spring-cloud-samples/sleuth-documentation-apps/tree/edgware .
I'm locking this issue. If you're unable to solve this problem please ask on Stackoverflow cause there's no issue with Sleuth here but with your setup.


Cow: Watch beardeddragongeek.com

Cow requests the watch of the watch_keyword beardeddragongeek\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

beardeddragongeek\.com has been seen in 2 true positives, 1 false positive, and 0 NAAs.

Approved by Makyen in Charcoal HQ


Ensure Travis fails fast

In reviewing #34, I noticed one of the build jobs failed the clippy step but continued on to the test and build steps anyways. This seems like needless work, and it might be more desirable to tighten up the builds feedback on PRs so the build fails immediately if one of the checks like clippy or rustfmt fails.
@SeanPrashad does Travis not fail-fast, or do we need to configure something else? We already have fast_finish enabled in our config:
https://github.com/0xazure/supernova/blob/66f5bc50aa6bfe8c359e684279e3c889039b8d0e/.travis.yml#L35

No, the allow_failures for nightly means that the nightly job in the build matrix can fail but the entire build won't fail and e.g. merging a pull request won't be blocked. See: Rows that are Allowed to Fail.
Also, the specific job I linked to there is for the stable release channel, so it isn't affected by allowing failures for nightly.


[FLINK-19186][python] Add Python building blocks to make sure the basic functionality of Pandas Batch Group Aggregation could work

What is the purpose of the change
This pull request will add Python building blocks to make sure the basic functionality of Pandas Batch Group Aggregation could work
Brief change log

Add Aggregation interface
Add udaf decorator
Add PandasAggregateFunctionOperation

Verifying this change
This change added tests and can be verified as follows:

Add IT test test_group_aggregate_function in test_pandas_udaf.py

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: (no)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (no)
If yes, how is the feature documented? (not applicable)

@dianfu Thanks a lot for the review. I have addressed the comments at the latest commit.

@dianfu Thanks a lot for the review. I have addressed the comments at the latest commit.

@dianfu Thanks a lot for the review. I agree with the comments.


File not found error

File "/root/miniconda3/lib/python3.9/site-packages/numpy/lib/npyio.py", line 390, in load
fid = stack.enter_context(open(os_fspath(file), "rb"))
FileNotFoundError: [Errno 2] No such file or directory: '/home/users/bencheng.liao/PlanWrapper/playground/visualization/kmeans_navsim_traj_20.npy'
Hi, Thank you for open-sourcing your great work.
I encounter the aforementioned error when caching the dataset.
I think you forget to upload this file:
plan_anchor_path: str = "/home/users/bencheng.liao/PlanWrapper/playground/visualization/kmeans_navsim_traj_20.npy"
Thank you in advance for your help.

Oh, I found it in https://github.com/hustvl/DiffusionDrive/releases/download/DiffusionDrive_88p1_PDMS_Eval_file/kmeans_navsim_traj_20.npy
sorry


await movies.ToListAsync() redundant?

In the first code snippet, it seems the construction of the Task and the subsequent await can be simplified to a single blocking call to movies.ToList(); am I missing something?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: cc54dbf8-e6fe-a212-b2cd-c015a6ba5439
Version Independent ID: b96b0b44-3e3a-a6c2-6b2b-c7bab4b78f0d
Content: Add search to ASP.NET Core Razor Pages
Content Source: aspnetcore/tutorials/razor-pages/search.md
Product: aspnet-core
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

Blocking calls take up threads while waiting for the database query to complete, so you shouldn't use them at all.

I agree, but the await in
Genres = new SelectList(await genreQuery.Distinct().ToListAsync())

already makes this blocking (within the Task). What I'm proposing is that we rewrite this as
Genres = new SelectList(genreQuery.Distinct().ToList());

In other languages, lifting into an async task and then directly awaiting it it is considered poor practice (e.g. https://eslint.org/docs/rules/no-return-await).

I think awaiting the async call will break up the function into two parts and still free up the thread while the program is waiting for a response, whereas a synchronous call will hold up the thread.

Thanks for the help! I think I understand what you're saying. The await yields control flow to the caller of OnGetAsync, effectively breaking the function up into coroutines than can be scheduled at different times rather than one large synchronous computation. Is that right?


Broken Serving

npm 2.11.2
node 0.12.5

The node file was relying upon a deprecated function in express. Blog is updated and you have been credited at the end of the page. Thanks!


update library to make apollo functionv4 and apollo server work together

Summary by Sourcery
Update the Azure Cognitive Search implementation to improve performance by caching search clients.
New Features:

Add an initialization step for search clients.

Enhancements:

Cache search clients to improve search performance.

Tests:

Update tests to reflect changes in the search service.

@gidich it seems that I accidentally added you as a reviewer. I requested Nick to review this PR already, so I am removing you.


Remove A device type

This device type does not exist.

Codecov Report

Merging #16 (834d1a7) into main (68a0b1b) will decrease coverage by 0.08%.
The diff coverage is 28.57%.

@@            Coverage Diff             @@
##             main      #16      +/-   ##
==========================================
- Coverage   21.31%   21.22%   -0.09%
==========================================
  Files           6        6
  Lines         671      669       -2
  Branches      328      327       -1
==========================================
- Hits          143      142       -1
+ Misses        253      252       -1
  Partials      275      275


Rename Chronos into Metronome

Rename all things Chronos into Metronome as that's the new name for the new Chronos.

Reviewer: @kennyt

LGTM let's SHIP this.


subdomain should be server not API key for the host

client := gochimp3.New(apiKey)
this places the apiKey at the start of the host, but it should really use the server id (such as us7)

doh, the api key needs to have the server id on the end of it. my bad

doh, the api key needs to have the server id on the end of it. my bad

if anyone else is having save issue make sure your api key actually has the "-xxx" on the end of it, where xxx is the server you plan is based on.  for example mine is in this format d4444a2aa33332f72594269e64912347-us5

if anyone else is having save issue make sure your api key actually has the "-xxx" on the end of it, where xxx is the server you plan is based on.  for example mine is in this format d4444a2aa33332f72594269e64912347-us5


Hide swagger end point according to role of user

: I want to hide endpoints dynamically by checking login-ed user permissions. Is it possible do with Spring-fox if so, please provide way to do it

Don't believe there is a way to do this.


Fix Router syntax on line 36

How to report a issue on GitHub

Fix the syntax error of Router class on line 36.

@peter279k  Thanks you so much for your time.


Fix for different VS/PS precision.

I already deleted the view_position uniform from the base.vs file (see here) because it doesn't seem to be used anywhere in our current set of chunks. As a result, can I simply close this?


When I click submit, the inference does not work and an error is displayed.

Here is the error message, thanks for the help
Traceback (most recent call last):
File "/home/ghan/anaconda3/envs/llama/lib/python3.10/site-packages/gradio/routes.py", line 393, in run_predict
output = await app.get_blocks().process_api(
File "/home/ghan/anaconda3/envs/llama/lib/python3.10/site-packages/gradio/blocks.py", line 1108, in process_api
result = await self.call_function(
File "/home/ghan/anaconda3/envs/llama/lib/python3.10/site-packages/gradio/blocks.py", line 915, in call_function
prediction = await anyio.to_thread.run_sync(
File "/home/ghan/anaconda3/envs/llama/lib/python3.10/site-packages/anyio/to_thread.py", line 31, in run_sync
return await get_asynclib().run_sync_in_worker_thread(
File "/home/ghan/anaconda3/envs/llama/lib/python3.10/site-packages/anyio/_backends/_asyncio.py", line 937, in run_sync_in_worker_thread
return await future
File "/home/ghan/anaconda3/envs/llama/lib/python3.10/site-packages/anyio/_backends/_asyncio.py", line 867, in run
result = context.run(func, *args)
File "/home/ghan/alpaca-lora/generate.py", line 107, in evaluate
generation_output = model.generate(
File "/home/ghan/anaconda3/envs/llama/lib/python3.10/site-packages/peft/peft_model.py", line 581, in generate
outputs = self.base_model.generate(**kwargs)
File "/home/ghan/anaconda3/envs/llama/lib/python3.10/site-packages/torch/utils/_contextlib.py", line 115, in decorate_context
return func(*args, **kwargs)
File "/home/ghan/anaconda3/envs/llama/lib/python3.10/site-packages/transformers/generation/utils.py", line 1524, in generate
return self.beam_search(
File "/home/ghan/anaconda3/envs/llama/lib/python3.10/site-packages/transformers/generation/utils.py", line 2810, in beam_search
outputs = self(
File "/home/ghan/anaconda3/envs/llama/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
return forward_call(*args, **kwargs)
File "/home/ghan/anaconda3/envs/llama/lib/python3.10/site-packages/accelerate/hooks.py", line 165, in new_forward
output = old_forward(*args, **kwargs)
File "/home/ghan/anaconda3/envs/llama/lib/python3.10/site-packages/transformers/models/llama/modeling_llama.py", line 689, in forward
outputs = self.model(
File "/home/ghan/anaconda3/envs/llama/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
return forward_call(*args, **kwargs)
File "/home/ghan/anaconda3/envs/llama/lib/python3.10/site-packages/transformers/models/llama/modeling_llama.py", line 577, in forward
layer_outputs = decoder_layer(
File "/home/ghan/anaconda3/envs/llama/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
return forward_call(*args, **kwargs)
File "/home/ghan/anaconda3/envs/llama/lib/python3.10/site-packages/accelerate/hooks.py", line 165, in new_forward
output = old_forward(*args, **kwargs)
File "/home/ghan/anaconda3/envs/llama/lib/python3.10/site-packages/transformers/models/llama/modeling_llama.py", line 292, in forward
hidden_states, self_attn_weights, present_key_value = self.self_attn(
File "/home/ghan/anaconda3/envs/llama/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
return forward_call(*args, **kwargs)
File "/home/ghan/anaconda3/envs/llama/lib/python3.10/site-packages/accelerate/hooks.py", line 165, in new_forward
output = old_forward(*args, **kwargs)
File "/home/ghan/anaconda3/envs/llama/lib/python3.10/site-packages/transformers/models/llama/modeling_llama.py", line 196, in forward
query_states = self.q_proj(hidden_states).view(bsz, q_len, self.num_heads, self.head_dim).transpose(1, 2)
File "/home/ghan/anaconda3/envs/llama/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
return forward_call(*args, **kwargs)
File "/home/ghan/anaconda3/envs/llama/lib/python3.10/site-packages/accelerate/hooks.py", line 165, in new_forward
output = old_forward(*args, **kwargs)
File "/home/ghan/anaconda3/envs/llama/lib/python3.10/site-packages/peft/tuners/lora.py", line 565, in forward
result = super().forward(x)
File "/home/ghan/anaconda3/envs/llama/lib/python3.10/site-packages/bitsandbytes/nn/modules.py", line 242, in forward
out = bnb.matmul(x, self.weight, bias=self.bias, state=self.state)
File "/home/ghan/anaconda3/envs/llama/lib/python3.10/site-packages/bitsandbytes/autograd/_functions.py", line 488, in matmul
return MatMul8bitLt.apply(A, B, out, bias, state)
File "/home/ghan/anaconda3/envs/llama/lib/python3.10/site-packages/torch/autograd/function.py", line 506, in apply
return super().apply(*args, **kwargs)  # type: ignore[misc]
File "/home/ghan/anaconda3/envs/llama/lib/python3.10/site-packages/bitsandbytes/autograd/_functions.py", line 317, in forward
state.CxB, state.SB = F.transform(state.CB, to_order=formatB)
File "/home/ghan/anaconda3/envs/llama/lib/python3.10/site-packages/bitsandbytes/functional.py", line 1698, in transform
prev_device = pre_call(A.device)
AttributeError: 'NoneType' object has no attribute 'device'

Do you have a gpu? just one?

Assuming you're using GPU (cuda), trying changing/adding the value of device_map in the following functions of generate.py:
if device == "cuda":         model = LlamaForCausalLM.from_pretrained(             ...             device_map={'':0},             ...         )         model = PeftModel.from_pretrained(             ...             device_map={'':0}            ...         )

i have the same problem. do you solve it

i have the same problem. do you solve it

Working fix just above
https://github.com/tloen/alpaca-lora/issues/230#issuecomment-1492338315


docker-compose issue

I have tried to run docker-compose -f docker-compose-CeleryExecutor.yml up -d
But recieved errors
ERROR: for webserver  No such image: sha256:3631d65918560df72f335194d391370a09ea944ab9f7a9f225611829bd883bdf
ERROR: for flower  No such image: sha256:3631d65918560df72f335194d391370a09ea944ab9f7a9f225611829bd883bdf

Yes, you've to update the git repository.
Airflow bump to rc5.


cant install betting module where to find it?

import betting
ModuleNotFoundError: No module named 'betting'

Betting is the other script in the repository. It is not a library or anything like that...


export default function should not be allowed in a namespace

declare namespace N {
    export default function foo();
}

should be an error.

This was fixed in #16704; #16300 should have been duped back to this one bug wasn't.


Chatterino closes automatically when opening the app

On my Mac with macOS Big Sur operating system version 11.0.1, the Chatterino application closes instantly as soon as the application opens, I have already uninstalled and reinstalled the application several times and the problem continues to persist, How can I solve this problem ?

Could you try the latest Nightly or beta version @vex-ol ? This is probably related to #2192

macOS (v2.2.3-beta2) crashed

I'm having the same problem. Tried the latest Nightly build too.

I've been running on the Big Sur beta's for a few months with no issues (currently on 11.0.1 20B29), then suddenly yesterday the app started crashing. Didn't update macOS and didn't change Chatterino versions.
I completely cleared everything in the settings folder (~/Library/Application Support/chatterino/Settings/) and now it's working again, so I'm assuming the culprit is somewhere in there. I tried replacing the new settings files with my old ones and it started crashing again, so it's definitely related. Didn't look into it any further than that though.

Fixed it by using the latest Nightly: https://github.com/Chatterino/chatterino2/pull/2192/checks?check_run_id=1408346574
@pajlada was right, it's related to #2192 and the FFZ API change.

@erenertugrul @jam396 Could you try deleting your cache folder before trying again?
For Windows:
Delete the %APPDATA%/Chatterino2/Cache folder
For Linux:
Delete the $HOME/.local/share/chatterino/Cache folder: rm -rf "$HOME/.local/share/chatterino/Cache"
For Mac:
Delete the $HOME/Library/Application Support/chatterino/Cache folder: rm -rf "$HOME/Library/Application Support/chatterino/Cache"

I just tried the Nightly build released later today and it works now! Thanks!

hi, @pajlada  i deleted $HOME/Library/Application Support/chatterino/
but nothing changed.
this odd
I tried versions
2.2.1 it works
2.2.2 it works
2.2.3-beta crashed
2.2.3-beta2 crashed
my mac high sierra

@erenertugrul try this Nightly build from yesterday: https://github.com/Chatterino/chatterino2/pull/2192/checks?check_run_id=1408346574

Same thing is happening with me, on windows.
I use the portable version, updated yesterday to 2.2.2-fix, and continued on using yesterday without problems. Today though, when I try to open it, chatterino opens as a white screen (image below) and closes right after (about one second later)

Tried again the version 2.2.2, 2.2.1, and even 2.2.0, and the problem happens on them as well.
I also tried the latest nightly, and #2192, and deleted the cache, none of those fixed it for me.

@GabrielDuarteM Opening once with admin privileges fixed it for me

@cheich Can confirm that opening with admin privileges fixes the problem! Thanks for sharing!

Duplicate of #2127, there's too many "chatterino crashing" / "chatterino crashing on startup" issues open, so I'll keep one open and close the other ones.


[Icon web component] Bootstrap stylesheet affects the entire page on Firefox

Describe the bug
The Bootstrap stylesheet that is loaded for the icon web component is affecting the entire page as opposed to just the web component
To Reproduce
Steps to reproduce the behavior:

Deploy jasig/uPortal-start@ceaf941
Removed waffle menu (it prevents the icon from loading on Firefox unless you bump the version to 1.13.5)
Log in and observe. You will see that the eyebrow goes from the right to left and that the font sizes shrink once the stylesheet loads

Screenshots

Platform:

uPortal Version: 5.3.0
Notification Portlet: 4.0.0
Browser: Firefox 62.0.3

Firefox less than or equal to version 62 do not support Shadow DOM, meaning the stylesheet can bleed out.
Firefox 63 (to be released 2018-10-23) and above have Shadow DOM enabled by default https://blog.nightly.mozilla.org/2018/09/06/developer-tools-support-for-web-components-in-firefox-63/
My first inclination would be to wait a week for Firefox to add support.
I'm open to other solutions.

I feel that something has to be figured out to support pre-Firefox 63 as the current Firefox ESR is Firefox 60 (ESR)
I pulled the latest beta of Firefox 63 and I'm now seeing huge icons

Firefox ESR is Firefox 60 (ESR)

Currently Firefox ESR is not part of the browser support matrix.
https://jasig.github.io/uPortal/SUPPORTED_BROWSERS.html
If it is being used by Universities, it may be something worth considering adding to the matrix.

I feel that something has to be figured out to support

What do you mean by "support"?
From what you've described, the styles are a bit off, but the page is still fully functional.

I pulled the latest beta of Firefox 63 and I'm now seeing huge icons

Aha, that looks familiar, I'll apply the patch from form builder here as well.
https://github.com/uPortal-contrib/form-builder/pull/57

Currently Firefox ESR is not part of the browser support matrix.
https://jasig.github.io/uPortal/SUPPORTED_BROWSERS.html
If it is being used by Universities, it may be something worth considering adding to the matrix.

What do you mean by "support"?
I want to make sure we're on the same page, so we can get this resolved slightly_smiling_face
From what you've described, the styles are a bit off, but the page is still fully functional.
To me, "support" means the webpage looks good in the latest version of Evergreen browsers (Chrome, Firefox, Edge), and functions (but may not be pixel perfect) on the rest of the supported browsers.

That (the styles) is what I'm referring to as well but the problem seems to be a lot trickier (to me at least) when we throw Shadow DOM into the picture

Currently Firefox ESR is not part of the browser support matrix.
https://jasig.github.io/uPortal/SUPPORTED_BROWSERS.html

Last time I jumped on a computer I have no install abilities on, it was what's running.

@drewwills @bjagg @apetro @jgribonvald @mairi thoughts? :thought_balloon:

That (the styles) is what I'm referring to as well but the problem seems to be a lot trickier (to me at least) when we throw Shadow DOM into the picture

To each their own.
I'd offer a contrary opinion.
uPortal has had plenty of issues with cascading styles unexpectedly breaking unrelated parts of the portal.
To me Shadow DOM is a solution, not a problem.
In terms of backward compatibility, looking into why https://github.com/webcomponents/shadydom does not seem to be taking affect.

It looks like to emulate the affect on CSS we'd need to use https://github.com/webcomponents/shadycss, looking into that now.

This is a tough issue.  It's easy to imagine there will be community members (or community institutions) with very strong opinions on either side of this debate.
On the one hand, it's not sustainable to carry on building front-end components with JSR-286, JSPs, and jQuery.  Recent experience has made it very clear to us that our most innovative & prolific contributors are not interested in engaging this kind of work any longer.  These older tools, moreover, are not as good for producing a contemporary-looking, contemporary-feeling UI... they simply don't produce the same quality of outcome.
On the other hand, support for the technologies that power Web Components (our only reasonable alternative to JSR-286) is currently a moving target in the major browsers.  It's hard simply to support the most recent version of all the browsers, and even harder to extend that support to multiple versions of those browsers.
What about this perspective...

Working on the Firefox ESR (or similar release of another browser) is something we value
But there is/should be no policy that says a contributed component must work on Firefox 60 to be accepted
Those that need a component to work on Firefox 60 should pitch in troubleshooting it
Once a component has been enhanced to work on Firefox 60, other developers should not contribute changes that break support for Firefox 60 (until it is no longer needed)

I'm working mainly on Firefox nigthly building and I didn't get these problems, but I had a similar problem with the eyebrow-user-info, and I solved it with CSS module described https://vue-loader.vuejs.org/guide/css-modules.html#usage, I didn't applyed it on esco-content-menu due to time and as I didn't find any issue on most used browser + Firefox nigthly, but I'm using all components on a fixed position of the body.
On an other part ShaddyDom is not adviced with the Web-component wrapper (if I remmenber well) of vue-js...
With my Firefox version the only problem encountered is with datalist + wc and I opened an issue on Firefox bugzilla.
I can provide all links tomorrow if you need.

To solve the problem on notification-icon you should set the width as component property with a default one (32px should be good).
You have the same problem with waffle menu.

The fix is simple, set on .svg-inline--fa a heigth and width with real units or set the parent element size and apply a %. As web-components I would suggest to add a prop that permit to set the size on the parent element and set into .svg-inline--fa height to 80% and width to 80%. This will also fix problems on safari. (It's what I've applied on my web-components and it's working)

The fix is simple, set on .svg-inline--fa a heigth and width with real units or set the parent element size and apply a %.

That fixes the height issue with the icon.
That doesn't resolve the issue of styles from in the component bleeding out on to the page.

That doesn't resolve the issue of styles from in the component bleeding out on to the page.

True and for that you need to apply scoped css. I can't say exactly for react but you have a similar build process that help to produce scoped css, with CSS Module, maybe a good link

Create React App (CRA) v1 doesn't play well with custom CSS loaders, it's getting better in CRA v2, but we need more flexibility than even CRA v2 offers to get the CSS inside the shadow dom.
I'm currently working to convert this component to Vue so we can leverage scoped styles in a web component friendly way.


Weird header is weird

Migrated from GitLab: https://gitlab.com/meltano/hub/-/issues/118
Originally created by @emilie on 2021-09-22 12:42:47

Small screen.

Full screen.

I noticed the header wasn't working correctly in Safari independent of the size of the screen.

View 4 previous comments from the original issue on GitLab