installation of basemap

i have downloaded the basemap package from github,when i m trying to run the setup.py code from the 1st folder named as basemap,i m getting the below error,but the other two folders named basemap_data and basemap_data_hires setup.py programs got successfully installed
Microsoft Windows [Version 10.0.19043.1415]
(c) Microsoft Corporation. All rights reserved.
C:\Users\sahana.DESKTOP-VB0949B.000\AppData\Local\Programs\Python\Python310\Lib\site-packages\basemap-1.3.0\packages\basemap>python setup.py install
C:\Users\sahana.DESKTOP-VB0949B.000\AppData\Local\Programs\Python\Python310\Lib\site-packages\basemap-1.3.0\packages\basemap\setup.py:52: RuntimeWarning: Cannot find GEOS library and/or headers in standard locations ('C:\Users\sahana.DESKTOP-VB0949B.000\AppData\Local\Programs\Python\Python310\Lib\site-packages\geos_init_.py'). Please install the corresponding packages using your software management system or set the environment variable GEOS_DIR to point to the location where GEOS is installed (for example, if 'geos_c.h' is in '/usr/local/include' and 'libgeos_c' is in '/usr/local/lib', then you need to set GEOS_DIR to '/usr/local'
warnings.warn(" ".join([
C:\Users\sahana.DESKTOP-VB0949B.000\AppData\Local\Programs\Python\Python310\lib\site-packages\setuptools\installer.py:27: SetuptoolsDeprecationWarning: setuptools.installer is deprecated. Requirements should be satisfied by a PEP 517 installer.
warnings.warn(
running install
C:\Users\sahana.DESKTOP-VB0949B.000\AppData\Local\Programs\Python\Python310\lib\site-packages\setuptools\command\install.py:34: SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and pip and other standards-based tools.
warnings.warn(
C:\Users\sahana.DESKTOP-VB0949B.000\AppData\Local\Programs\Python\Python310\lib\site-packages\setuptools\command\easy_install.py:156: EasyInstallDeprecationWarning: easy_install command is deprecated. Use build and pip and other standards-based tools.
warnings.warn(
running bdist_egg
running egg_info
writing manifest file 'src\basemap.egg-info\SOURCES.txt'
running install_lib
running build_py
running build_ext
"C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.30.30705\bin\HostX86\x64\cl.exe" /c /nologo /O2 /W3 /GL /DNDEBUG /MD -IC:\Users\sahana.DESKTOP-VB0949B.000\AppData\Local\Programs\Python\Python310\lib\site-packages\numpy\core\include -IC:\Users\sahana.DESKTOP-VB0949B.000\AppData\Local\Programs\Python\Python310\include -IC:\Users\sahana.DESKTOP-VB0949B.000\AppData\Local\Programs\Python\Python310\include "-IC:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.30.30705\ATLMFC\include" "-IC:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.30.30705\include" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.19041.0\ucrt" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.19041.0\shared" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.19041.0\um" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.19041.0\winrt" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.19041.0\cppwinrt" /Tcsrc_geoslib.c /Fobuild\temp.win-amd64-3.10\Release\src_geoslib.obj
_geoslib.c
C:\Users\sahana.DESKTOP-VB0949B.000\AppData\Local\Programs\Python\Python310\lib\site-packages\numpy\core\include\numpy\npy_1_7_deprecated_api.h(14) : Warning Msg: Using deprecated NumPy API, disable it with #define NPY_NO_DEPRECATED_API NPY_1_7_API_VERSION
src_geoslib.c(680): fatal error C1083: Cannot open include file: 'geos_c.h': No such file or directory
error: command 'C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.30.30705\bin\HostX86\x64\cl.exe' failed with exit code 2
C:\Users\sahana.DESKTOP-VB0949B.000\AppData\Local\Programs\Python\Python310\Lib\site-packages\basemap-1.3.0\packages\basemap>
please mention where the basemap-1.3.0 folder and geos folder should be placed.i., wether in the python folder or in the lib /sitepackages
also do mention how to set the path of the GEOS
i have already installed visual studio build compiler,oges and cmake

Hi @sahanaRavinder,
From your logs, it is clear that the problem with building basemap from source is due to GEOS not being found. Did you follow the steps from the README file? In particular, this (assuming you use the command prompt and you want to build GEOS e.g. in a temporary folder called extern):
cd packages\basemap
set GEOS_DIR=extern
python -c "import utils; utils.GeosLibrary('3.5.1').build(installdir='extern')"

After that, you need to build the basemap wheel using bdist_wheel so that the GEOS dll gets bundled:
python setup.py bdist_wheel

After that, you will have built the wheel package from source and it will be available in the dist folder, and you can install the wheel file with pip install.
One last point: it does not matter where you download the basemap source code or the GEOS source code. The source code must be downloaded somewhere so that you can build the wheel package from source. What lives later in site-packages is the content of this wheel package after installing it with pip install.

@sahanaRavinder From what I saw in https://github.com/libgeos/geos/issues/536, be sure of being located at packages\basemap when doing this:
python -c "import utils; utils.GeosLibrary('3.5.1').build(installdir='extern')"

If you run this from packages\basemap\utils, it will not obviously work. I would also recommend you to build the source code somewhere outside the Python system folders.

Thanks, I'll check it out.
On Thu, 13 Jan 2022, 18:00 Víctor Molina García, @.***>
wrote:

@sahanaRavinder https://github.com/sahanaRavinder From what I saw in
libgeos/geos#536 https://github.com/libgeos/geos/issues/536, be sure of
being located at packages\basemap when doing this:
python -c "import utils; utils.GeosLibrary('3.5.1').build(installdir='extern')"
If you run this from packages\basemap\utils, it will not obviously work.
I would also recommend you to build the source code somewhere outside the
Python system folders.
—
Reply to this email directly, view it on GitHub
https://github.com/matplotlib/basemap/issues/531#issuecomment-1012093656,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AWHA7MZVYBOZWAQW7MT64BTUV3AVTANCNFSM5LVTWYZA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>

@sahanaRavinder Did you have time to try it out and see if you can install basemap 1.3.1 with pip?

Sorry ,I didn't try as I was occupied with other things...I will try it
ASAP and let you know
On Fri, 28 Jan 2022, 21:01 Víctor Molina García, @.***>
wrote:

@sahanaRavinder https://github.com/sahanaRavinder Did you have time to
try it out and see if you can install basemap 1.3.1 with pip?
—
Reply to this email directly, view it on GitHub
https://github.com/matplotlib/basemap/issues/531#issuecomment-1024330963,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AWHA7MZFE4YXDXFDIAEVJO3UYKZEZANCNFSM5LVTWYZA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>

I am closing this issue due to lack of feedback. Since we now have wheel files for Windows and Python 3.10, the installation should be straightforward. Feel free to reopen the issue if the problem persists.


syscall/Stat: hang on 3hours with many goroutine stat nfs path

What version of Go are you using (go version)?

$ go version
go version go1.10.8 linux/amd64

Does this issue reproduce with the latest release?
Not yet try to reproduce on latest release
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GOARCH="amd64"
GOBIN=""
GOCACHE="/root/.cache/go-build"
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/go"
GORACE=""
GOROOT="/usr/local/go"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build323519428=/tmp/go-build -gno-record-gcc-switches"

What did you do?
write a go binary command which starts 100 goroutine to fstat 100 different nfs client mount path when nfs server is down.
nfs mount options(vers=4.1,rsize=1048576,wsize=1048576,namlen=255,soft,proto=tcp,timeo=600,retrans=2,sec=sys)

What did you expect to see?
total command run time should be 3min with the mount option(timeo=600,retrans=2)
What did you see instead?
total command run time is 3hour30min with the mount option(timeo=600,retrans=2)
Anything else
strace log
strace-log
fstat nfs path log
fstat-log

Have you tried the same with a threaded C program?


Error: Cannot find module 'babel-eslint' Referenced from: mypath/testing-create/package.json

node v6.3.1
create-react-app v0.2
When opening App.js or index.js in Atom I get this error :
Error: Cannot find module 'babel-eslint' Referenced from: /Users/Home/github/testing-create/package.json
at Object.ModuleResolver.resolve (/usr/local/lib/node_modules/eslint/lib/util/module-resolver.js:75:19)
at load (/usr/local/lib/node_modules/eslint/lib/config/config-file.js:519:42)
at /usr/local/lib/node_modules/eslint/lib/config/config-file.js:392:36
at Array.reduceRight (native)
at applyExtends (/usr/local/lib/node_modules/eslint/lib/config/config-file.js:363:28)
at Object.load (/usr/local/lib/node_modules/eslint/lib/config/config-file.js:531:22)
at loadConfig (/usr/local/lib/node_modules/eslint/lib/config.js:64:33)
at new Config (/usr/local/lib/node_modules/eslint/lib/config.js:197:38)
at CLIEngine.executeOnText (/usr/local/lib/node_modules/eslint/lib/cli-engine.js:750:28)
at Object.cli.execute (/usr/local/lib/node_modules/eslint/lib/cli.js:181:36)

I ran an npm run eject and the babel-eslint folder is in my node_modules folder.
If any other infos are needed feel free to ask me to add them here.
EDIT : looks like I needed to instal babel-eslint globally on my computer, I'm not sure how we could warn new users (like me) about this since this tool is made for them.

This is mentioned in the generated project README.
Unfortunately we can't warn everyone about this because we can't guess if you are using editor plugins for linting or not.
Linting in terminal works fine without global installations.
Also, this problem should be fixed within a couple of months by ESLint itself so it's probably not too bad.

@gaearon Can't that be fixed by specifying the parser in config/eslint.js like so parser: require.resolve('babel-eslint'), ? This change worked fine for me using Atom.

This will only fix parser but won’t fix the same issues with plugins.
The real fix for this will be https://github.com/eslint/eslint/issues/3458.

Got it! Thanks for the clarification.


Update kinsky to 4.4.5

After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} left no offenses.
[x] The commit message includes the cask’s name and version.

Thank you for the contribution. It was merged directly as 6db2fd30e563f3d0414c544e5d3a754c8ce93ff4. Your contribution is still credited to you.


stats: Remove --use-fake-symbol-tables option.

See also https://github.com/envoyproxy/envoy/issues/6307 which removes the code supporting fake symbol tables, but leaves the option in place.
Removing the option is a breaking change, so splitting that off on its own.

Hi @jmarantz, I would like to take it if you're not working on it.

You are welcome to take it; I expect it will be pretty easy and I can review. However, I think it would be better to wait a bit, because removing an option can break production setups, potentially. @mattklein123 when do you think would be appropriate? Maybe 1-2 weeks prior to the cut-date for 1.17?

If the code was removed in the last release IMO it can be removed any time during this cycle so fine to do it now.


[BACKLOG-8242] - making sure the injected Trans finishes its listener…

…s before considering it to be done

Build Completed
:x: This pull request has errors. They will need to be addressed before it can be accepted. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands
ant -Dpentaho.resolve.repo=http://ivy-nexus.pentaho.org/content/groups/approved -Dtestreports.dir=bin/reports/unit-test -f engine/build.xml clean-all resolve jacoco && ant -Dpentaho.resolve.repo=http://ivy-nexus.pentaho.org/content/groups/approved -Dtestreports.dir=bin/reports/integration-test -f engine/build.xml jacoco-integration checkstyle publish-local

Cleanup Commands
rm -r ~/.ivy2/local || echo no publish local to remove

Changed files
  engine/src/org/pentaho/di/trans/steps/metainject/MetaInject.java
  engine/test-src/org/pentaho/di/trans/steps/metainject/MetaInjectTest.java

Still Broken Tests:
org.pentaho.di.www.SlaveServerJobStatusTest.testSerialization:
:red_circle: java.lang.RuntimeException
java.lang.RuntimeException: Unable to invoke setter for LogDate
	at org.pentaho.di.base.LoadSaveBase.createValidatorMapAndInvokeSetters(LoadSaveBase.java:119)
	at org.pentaho.di.www.SlaveServerJobStatusLoadSaveTester.testXmlRoundTrip(SlaveServerJobStatusLoadSaveTester.java:54)
	at org.pentaho.di.www.SlaveServerJobStatusLoadSaveTester.testSerialization(SlaveServerJobStatusLoadSaveTester.java:48)
	at org.pentaho.di.www.SlaveServerJobStatusTest.testSerialization(SlaveServerJobStatusTest.java:107)
C

org.pentaho.di.www.SlaveServerTransStatusTest.testSerialization:
:red_circle: java.lang.RuntimeException
java.lang.RuntimeException: Unable to invoke setter for LogDate
	at org.pentaho.di.base.LoadSaveBase.createValidatorMapAndInvokeSetters(LoadSaveBase.java:119)
	at org.pentaho.di.www.SlaveServerTransStatusLoadSaveTester.testXmlRoundTrip(SlaveServerTransStatusLoadSaveTester.java:54)
	at org.pentaho.di.www.SlaveServerTransStatusLoadSaveTester.testSerialization(SlaveServerTransStatusLoadSaveTester.java:48)
	at org.pentaho.di.www.SlaveServerTransStatusTest.testSerialization(SlaveServerTransStatusTest

Unit test coverage change
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.
org.pentaho.di.job.entries.evalfilesmetrics.JobEntryEvalFilesMetrics

Branch Change:  + .78%
Complexity Change:  + 1.03%
Instruction Change:  + .16%

org.pentaho.di.job.entries.evaluatetablecontent.JobEntryEvalTableContent

Branch Change:  + 1.01%
Complexity Change:  + 1.06%
Instruction Change:  + .17%

org.pentaho.di.job.entries.waitforsql.JobEntryWaitForSQL

Branch Change:  + .66%
Complexity Change:  + .93%
Instruction Change:  + .13%

org.pentaho.di.repository.kdr.KettleDatabaseRepositoryCreationHelper

Branch Change: -1.64%:small_red_triangle_down:
Complexity Change: -.69%:small_red_triangle_down:
Instruction Change: -2.43%:small_red_triangle_down:
Line Change: -3.70%:small_red_triangle_down:

org.pentaho.di.trans.step.StepMeta

Instruction Change: -.19%:small_red_triangle_down:
Line Change: -.27%:small_red_triangle_down:

org.pentaho.di.trans.steps.checksum.CheckSumMeta

Branch Change:  + 1.32%
Complexity Change:  + 1.43%
Instruction Change:  + .43%
Line Change:  + .54%

org.pentaho.di.trans.steps.combinationlookup.CombinationLookupMeta

Instruction Change:  + .04%

org.pentaho.di.trans.steps.datagrid.DataGridMeta

Instruction Change:  + .09%

org.pentaho.di.trans.steps.dbproc.DBProcMeta

Instruction Change: -.11%:small_red_triangle_down:

org.pentaho.di.trans.steps.groupby.GroupByMeta

Branch Change:  + 5.21%
Complexity Change:  + 5.26%
Instruction Change:  + .14%
Line Change:  + .37%

org.pentaho.di.trans.steps.memgroupby.MemoryGroupByMeta

Branch Change:  + 2.35%
Complexity Change:  + 2.70%

org.pentaho.di.trans.steps.metainject.MetaInject

Branch Change:  + .55%
Complexity Change:  + 1.75%
Instruction Change:  + .21%
Line Change:  + .38%
Method Change:  + 1.04%

org.pentaho.di.trans.steps.rowgenerator.RowGeneratorMeta

Instruction Change: -.08%:small_red_triangle_down:

org.pentaho.di.trans.steps.setvalueconstant.SetValueConstantMeta

Instruction Change: -.14%:small_red_triangle_down:

org.pentaho.di.trans.steps.singlethreader.SingleThreaderMeta

Instruction Change: -.08%:small_red_triangle_down:

org.pentaho.di.trans.steps.sortedmerge.SortedMergeMeta

Instruction Change:  + .18%

org.pentaho.di.trans.steps.synchronizeaftermerge.SynchronizeAfterMergeMeta

Instruction Change:  + .04%

org.pentaho.di.trans.steps.textfileinput.TextFileInputMeta

Branch Change: -.53%:small_red_triangle_down:

Integration test coverage change
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.
org.pentaho.di.trans.steps.metainject.MetaInject

Complexity Change:  + .99%
Instruction Change:  + .21%
Line Change:  + .40%
Method Change:  + 1.39%

Checkstyle violations
The code submitted is not complying with one or more of our guidelines. To perform these checks locally, please use this tool.
/home/buildguy/project/engine/test-src/org/pentaho/di/trans/steps/metainject/MetaInjectTest.java

:heavy_exclamation_mark: Unused import - org.pentaho.di.trans.steps.datagrid.DataGridMeta. at Line: 53 Column: 8

:heavy_exclamation_mark: Unused import - org.pentaho.di.trans.steps.dummytrans.DummyTransMeta. at Line: 54 Column: 8

Build Completed
:fire: This pull request has some issues. It would be preferable to fix them in order for it to be just perfect. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands
ant -Dpentaho.resolve.repo=http://ivy-nexus.pentaho.org/content/groups/approved -Dtestreports.dir=bin/reports/unit-test -f engine/build.xml clean-all resolve jacoco && ant -Dpentaho.resolve.repo=http://ivy-nexus.pentaho.org/content/groups/approved -Dtestreports.dir=bin/reports/integration-test -f engine/build.xml jacoco-integration checkstyle publish-local

Cleanup Commands
rm -r ~/.ivy2/local || echo no publish local to remove

Changed files
  engine/src/org/pentaho/di/trans/steps/metainject/MetaInject.java
  engine/test-src/org/pentaho/di/trans/steps/metainject/MetaInjectTest.java

Still Broken Tests:
org.pentaho.di.www.SlaveServerJobStatusTest.testSerialization:
:red_circle: java.lang.RuntimeException
java.lang.RuntimeException: Unable to invoke setter for LogDate
	at org.pentaho.di.base.LoadSaveBase.createValidatorMapAndInvokeSetters(LoadSaveBase.java:119)
	at org.pentaho.di.www.SlaveServerJobStatusLoadSaveTester.testXmlRoundTrip(SlaveServerJobStatusLoadSaveTester.java:54)
	at org.pentaho.di.www.SlaveServerJobStatusLoadSaveTester.testSerialization(SlaveServerJobStatusLoadSaveTester.java:48)
	at org.pentaho.di.www.SlaveServerJobStatusTest.testSerialization(SlaveServerJobStatusTest.java:107)
C

org.pentaho.di.www.SlaveServerTransStatusTest.testSerialization:
:red_circle: java.lang.RuntimeException
java.lang.RuntimeException: Unable to invoke setter for LogDate
	at org.pentaho.di.base.LoadSaveBase.createValidatorMapAndInvokeSetters(LoadSaveBase.java:119)
	at org.pentaho.di.www.SlaveServerTransStatusLoadSaveTester.testXmlRoundTrip(SlaveServerTransStatusLoadSaveTester.java:54)
	at org.pentaho.di.www.SlaveServerTransStatusLoadSaveTester.testSerialization(SlaveServerTransStatusLoadSaveTester.java:48)
	at org.pentaho.di.www.SlaveServerTransStatusTest.testSerialization(SlaveServerTransStatusTest

Unit test coverage change
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.
org.pentaho.di.core.auth.core.impl.DefaultAuthenticationConsumerFactory

Branch Change:  + 7.14%
Complexity Change:  + 7.69%

org.pentaho.di.job.entries.waitforsql.JobEntryWaitForSQL

Branch Change:  + .66%
Complexity Change:  + .93%
Instruction Change:  + .13%

org.pentaho.di.trans.step.StepMeta

Instruction Change: -.19%:small_red_triangle_down:
Line Change: -.27%:small_red_triangle_down:

org.pentaho.di.trans.steps.checksum.CheckSumMeta

Branch Change: -1.32%:small_red_triangle_down:
Complexity Change: -1.43%:small_red_triangle_down:
Instruction Change: -.22%:small_red_triangle_down:
Line Change: -.54%:small_red_triangle_down:

org.pentaho.di.trans.steps.combinationlookup.CombinationLookupMeta

Instruction Change:  + .04%

org.pentaho.di.trans.steps.constant.ConstantMeta

Instruction Change:  + .10%

org.pentaho.di.trans.steps.csvinput.CsvInputMeta

Instruction Change: -.05%:small_red_triangle_down:

org.pentaho.di.trans.steps.datagrid.DataGridMeta

Instruction Change: -.09%:small_red_triangle_down:

org.pentaho.di.trans.steps.dbproc.DBProcMeta

Instruction Change:  + .11%

org.pentaho.di.trans.steps.dimensionlookup.DimensionLookupMeta

Branch Change: -.66%:small_red_triangle_down:
Complexity Change: -.41%:small_red_triangle_down:
Instruction Change: -.50%:small_red_triangle_down:
Line Change: -.24%:small_red_triangle_down:

org.pentaho.di.trans.steps.ifnull.IfNullMeta

Branch Change: -2.00%:small_red_triangle_down:
Complexity Change: -1.89%:small_red_triangle_down:
Instruction Change: -.17%:small_red_triangle_down:

org.pentaho.di.trans.steps.insertupdate.InsertUpdateMeta

Instruction Change:  + .05%

org.pentaho.di.trans.steps.memgroupby.MemoryGroupByMeta

Branch Change:  + 1.18%
Complexity Change:  + 1.35%

org.pentaho.di.trans.steps.metainject.MetaInject

Branch Change:  + .55%
Complexity Change:  + 1.75%
Instruction Change:  + .21%
Line Change:  + .38%
Method Change:  + 1.04%

org.pentaho.di.trans.steps.singlethreader.SingleThreaderMeta

Instruction Change: -.08%:small_red_triangle_down:

org.pentaho.di.trans.steps.systemdata.SystemDataMeta

Branch Change:  + 2.04%
Complexity Change:  + 2.04%
Instruction Change:  + .32%
Line Change:  + .81%

org.pentaho.di.trans.steps.webservices.WebServiceMeta

Branch Change:  + 1.79%
Complexity Change:  + 1.19%
Instruction Change:  + .07%

Integration test coverage change
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.
org.pentaho.di.trans.step.BaseStep

Branch Change: -.29%:small_red_triangle_down:
Complexity Change: -.18%:small_red_triangle_down:
Instruction Change: -.13%:small_red_triangle_down:
Line Change: -.08%:small_red_triangle_down:

org.pentaho.di.trans.steps.metainject.MetaInject

Complexity Change:  + .99%
Instruction Change:  + .21%
Line Change:  + .40%
Method Change:  + 1.39%


m3u8 live urls not playing

Try adding android:usesCleartextTraffic="true" in your manifest.xml application tag
<application
......
android:usesCleartextTraffic="true"
....>


perf(transformer): React display name transform reduce Atom allocations

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#3616  👈
#3615
#3614
#3613
#3612
#3611
#3610
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @overlookmotel and the rest of your teammates on  Graphite


Offset and clustering

Current coverage is 47.10% (diff: 22.05%)

Merging #422 into devel will decrease coverage by 0.11%

@@              devel       #422   diff @@
==========================================
  Files           182        184     +2
  Lines         17945      18013    +68
  Methods           0          0
  Messages          0          0
  Branches       2513       2338   -175
==========================================
+ Hits           8473       8485    +12
- Misses         9042       9109    +67
+ Partials        430        419    -11

Powered by Codecov. Last update 2e02736...132c8d9

Nice, you can delete the branch when you are finished :)


d20190918_MIAO

Metadata filled out and data uploaded, but one file (Guofang Miao - US-NC4_Rs_daily_2009-2011.csv) is only daily means (?). Contacting contributor to clarify.

OK, contributors has approved report.


Release 0.2.0-rc.0 only works with RN0.60 (androidx) [FIX INCLUDED]

We are not using androidX yet and we're getting this error while compiling:
> Task :react-native-appearance:compileDebugJavaWithJavac FAILED
/path/to/app/node_modules/react-native-appearance/android/src/main/java/com/reactlibrary/RNCAppearanceManager.java:3: error: cannot find symbol
import android.annotation.NonNull;
                        ^
symbol:   class NonNull
location: package android.annotation
/path/to/app/node_modules/react-native-appearance/android/src/main/java/com/reactlibrary/RNCApperancePackage.java:3: error: cannot find symbol
import android.annotation.NonNull;
                        ^
symbol:   class NonNull
location: package android.annotation
/path/to/app/node_modules/react-native-appearance/android/src/main/java/com/reactlibrary/RNCApperanceModule.java:11: error: cannot find symbol
import android.annotation.NonNull;
                        ^
symbol:   class NonNull
location: package android.annotation
/path/to/app/node_modules/react-native-appearance/android/src/main/java/com/reactlibrary/RNCApperanceModule.java:12: error: cannot find symbol
import android.annotation.Nullable;
                        ^
symbol:   class Nullable
location: package android.annotation
/path/to/app/node_modules/react-native-appearance/android/src/main/java/com/reactlibrary/RNCAppearanceManager.java:10: error: cannot find symbol
    @NonNull
    ^
symbol:   class NonNull
location: class RNCAppearanceManager
/path/to/app/node_modules/react-native-appearance/android/src/main/java/com/reactlibrary/RNCAppearanceManager.java:18: error: cannot find symbol
    protected RNCAppearanceProvider createViewInstance(@NonNull ThemedReactContext reactContext) {
                                                        ^
symbol:   class NonNull
location: class RNCAppearanceManager
/path/to/app/node_modules/react-native-appearance/android/src/main/java/com/reactlibrary/RNCAppearanceManager.java:16: error: cannot find symbol
    @NonNull
    ^
symbol:   class NonNull
location: class RNCAppearanceManager
/path/to/app/node_modules/react-native-appearance/android/src/main/java/com/reactlibrary/RNCApperancePackage.java:17: error: cannot find symbol
    public List<NativeModule> createNativeModules(@NonNull ReactApplicationContext reactContext) {
                                                ^
symbol:   class NonNull
location: class RNCApperancePackage
/path/to/app/node_modules/react-native-appearance/android/src/main/java/com/reactlibrary/RNCApperancePackage.java:15: error: cannot find symbol
    @NonNull
    ^
symbol:   class NonNull
location: class RNCApperancePackage
/path/to/app/node_modules/react-native-appearance/android/src/main/java/com/reactlibrary/RNCApperancePackage.java:25: error: cannot find symbol
    public List<ViewManager> createViewManagers(@NonNull ReactApplicationContext reactContext) {
                                                ^
symbol:   class NonNull
location: class RNCApperancePackage
/path/to/app/node_modules/react-native-appearance/android/src/main/java/com/reactlibrary/RNCApperancePackage.java:23: error: cannot find symbol
    @NonNull
    ^
symbol:   class NonNull
location: class RNCApperancePackage
/path/to/app/node_modules/react-native-appearance/android/src/main/java/com/reactlibrary/RNCApperanceModule.java:31: error: cannot find symbol
    public RNCApperanceModule(@NonNull ReactApplicationContext reactContext) {
                            ^
symbol:   class NonNull
location: class RNCApperanceModule
/path/to/app/node_modules/react-native-appearance/android/src/main/java/com/reactlibrary/RNCApperanceModule.java:47: error: cannot find symbol
    @NonNull
    ^
symbol:   class NonNull
location: class RNCApperanceModule
/path/to/app/node_modules/react-native-appearance/android/src/main/java/com/reactlibrary/RNCApperanceModule.java:82: error: cannot find symbol
    @androidx.annotation.Nullable
                        ^
symbol:   class Nullable
location: package androidx.annotation
/path/to/app/node_modules/react-native-appearance/android/src/main/java/com/reactlibrary/RNCApperanceModule.java:90: error: cannot find symbol
    private void sendEvent(ReactContext reactContext, String eventName, @Nullable WritableMap params) {
                                                                        ^
symbol:   class Nullable
location: class RNCApperanceModule
/path/to/app/node_modules/react-native-appearance/android/src/main/java/com/reactlibrary/RNCApperanceModule.java:100: error: cannot find symbol
    private void sendEvent(String eventName, @Nullable WritableMap params) {
                                            ^
symbol:   class Nullable
location: class RNCApperanceModule
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
16 errors

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':react-native-appearance:compileDebugJavaWithJavac'.
> Compilation failed; see the compiler error output for details.

For those whom want an easy fix, use the patch file:
https://gist.github.com/nschild/0c9ded2e04af98054aca27d6359a2947
Also, add the following line to your build.gradle's dependencies section:
implementation 'com.android.support:support-annotations:+'

thanks! can you open a pull request for this?

Is there a previous release we can use meanwhile?

@brentvatne I am not sure of what path the team wants to take on this. If they accept my PR, AndroidX will not work, and since AndroidX is the future, I doubt it should be included.
@rolandjitsu all you have to do is run npm install patch-package, add "scripts": { "postinstall":  "patch-package";} to your package.json and place the above file into a /patches/ folder in your root directory. Now, when node installs react-native-appearance, it will automatically apply the patch file.

This problem can be solved for react-native 0.59 by using jetifier, running npx jetify -r

Jetifier is the community answer for handling library/project android/androidx mismatch

added instructions under readme: https://github.com/expo/react-native-appearance#linking


New StrictlyPositiveInt type

Description
We would like to define a new StrictlyPositiveInt serializable type in the kotools.types.number package for representing positive integers excluding zero. This type should be available on all platforms and should be compatible with Kotlin and Java. Its serialization should behave like an Int.
Here's the minimal API for this type:
public fun StrictlyPositiveInt(value: Number): StrictlyPositiveInt {
    TODO("Not yet implemented")
}

public fun Number.toStrictlyPositiveInt(): StrictlyPositiveInt {
    TODO("Not yet implemented")
}

public fun Number.toStrictlyPositiveIntOrNull(): StrictlyPositiveInt? {
    TODO("Not yet implemented")
}

public interface StrictlyPositiveInt {
    override fun equals(other: Any?): Boolean
    override fun hashCode(): Int
    public fun toInt(): Int
    override fun toString(): String
}

Checklist

[ ] Implement the type and its minimal API.
[ ] Make the type serializable.
[ ] Refactor code.
[ ] Check the generated documentation.
[ ] Check and update the public API binaries.
[ ] Update the Unreleased section in changelog.

We will use the existing type instead of defining a new one.

We will work on the existing type instead of reimplementing it from scratch.


June dame sprint staging

Coverage decreased (-0.5%) to 26.616% when pulling 5b7ead4e60f796389e375a43a51713ced586bcce on june-dame-sprint-staging into 90b518bc4e44060fa5eae2e2fef6438c8916965c on master.


Add user function call support

Function defined by the user can now be called in the same ways as built-in functions, for example:
fn add($a: int64, $b: int64): int64 {
return $a + $b;
}
BEGIN {
print(add(5, 9));
}
If a function of the same name as an existing built-in is defined, it overrides the built-in and a warning is printed.
Implementation-wise, the functionality depends on existing relocations against subprogs implemented in commit d345d06 ("Implement relocations against .text for subprogs").
Functions are generated as separate LLVM IR functions and translated into BPF subprogs via the LLVM bpf backend. Relocations make sure the resulting program can be loaded.

Checklist

[ ] Language changes are updated in man/adoc/bpftrace.adoc
[ ] User-visible and non-trivial changes updated in CHANGELOG.md
[x] The new behaviour is covered by tests

Second PR following recently merged #2624 to implement user-defined functions (#2516).

Fixed build on systems with older glibc that do not have BPF relocations in elf.h, like those used in CI.

There are still some limitations to the implementation, the biggest of which is that bpftrace functions are directly converted into BPF subprograms. That means you are not able to pass more than four 64-bit values to a function, since arguments are passed in registers, and also you can't have a return value bigger than 8 bytes. Currently, passing values through a map can be used as a workaround for that. Given that, declaring a function returning a string should not segfault; that is an unrelated bug.
The annoying typing of integers is the result of using stricter type comparisons for functions; bpftrace generally only checks the base type (integer, string etc.), not the signedness nor the size of the type. I was not sure how to approach that; opting for less strict type control seemed possibly dangerous to me so I chose to make the type control strict for the time being.
About the verifier errors: that's something we unfortunately have to live with. The verifier is expected to get better at proving the halting of recursive calls but as the halting problem is unsolvable, there will always be recursive calls that fail at the verifier. It makes little sense to replicate the complex halting checks in bpftrace.

About the verifier errors: that's something we unfortunately have to live with. The verifier is expected to get better at proving the halting of recursive calls but as the halting problem is unsolvable, there will always be recursive calls that fail at the verifier. It makes little sense to replicate the complex halting checks in bpftrace.

We shouldn't allow verifier errors though to the user of bpftrace though. AFAIK it's not possible to trigger one except when using while loops (which I'd like to deprecate eventually). In other parts of the language we generally restrict functionality so that the verifier will always be happy. I'm not so keen to do that here because there is useful functionality that'd get blocked as collateral damage.
Maybe something similar to what we do with HelperVerifierError might be a good solution - parse the verifier log and if it matches the pattern we expect, provide a nice message to the user explaining what's wrong and how to fix it.

Maybe something similar to what we do with HelperVerifierError might be a good solution - parse the verifier log and if it matches the pattern we expect, provide a nice message to the user explaining what's wrong and how to fix it.

This sounds good but also possibly very difficult in trying to anticipate every verifier error as we make the bpftrace language more expressive. I imagine that we wouldn't do the same for raw c code that we import and interop with.

@lenticularis39 Thanks for working on this! Similar to @ajor I'm starting to play with it and just documenting some random issues.

This yields a verifier error for the unused add1 function (though maybe this will go away after we finish libbpf migration). Maybe something we can catch earlier in semantic analyser.
fn add($a: int64, $b: int64): int64 { return $a + $b; }
fn add1($a: int64): int64 { return $a + $a; }
BEGIN { print(add(1, 1)); }

Also seeing it here:
fn add1($a: int64, $b: int64): int64 { return $a + $b; }
fn add2($a: int64): int64 { return $a + $a; }
BEGIN { print(add1(1, 1)); }
hardware:cpu-cycles:1e8 { print(add2(2)); }

I get the shadow warning but it seems like this program doesn't work:
fn printf($a: int64): void { print(($a)); }
BEGIN { printf(3); }

We should support some of the aggregate map types e.g. count, sum, min, max, avg
fn go($a: uint64): void { print(($a)); }
BEGIN { @ = count(); go(@); }

Should we be catching unused returns? e.g.
fn add1($a: int64, $b: int64): int64 { return $a + $b; }
BEGIN { add1(1, 1); }

We shouldn't allow statements after return values. Fortunately, this doesn't actually add to sum.
fn add1($a: int64, $b: int64): int64 { return $a + $b; @ = sum(2); }
BEGIN { @ = sum(add1(1, 1)); }

This should be caught in semantic analysis. Right now it causes a segfault
fn add($a: int64, $b: int64): int64 { exit(); return $a + $b; }

Questions

Is it possible to pass strings as arguments and if so, how?
Should we disallow some keywords as function names e.g.  BEGIN {BEGIN(1, 1); } ?

Is it possible to pass strings as arguments and if so, how?

In the current implementation, no, since arguments are passed in BPF registers and thus are limited to four words. This can be improved by storing function arguments in a BPF map ("stack").

Should we disallow some keywords as function names e.g.  BEGIN {BEGIN(1, 1); } ?

Keywords are already disallowed by the parser implementation which requires the name of a function to be an identifier. BEGIN is not a keyword, it is a name of an attach point; it's unusual and confusing to use it as a name of a function, but I see little reason why we should disallow that.


metrics/linux/cpuusage.go is inacculate if a host runs KVM VMs

Hi.
I've found that metrics/linux/cpuusage.go calucurates user inaccurately on Linux hosts running KVM vms.
What's inaccurate?
As you can see man 5 proc, 1st column of /proc/stat means  user   (1) Time spent in user mode, and 9th column means guest (9) Time spent running a virtual CPU for guest operating systems under the control of the Linux kernel.
Acutually, user includes guest, so cputime is duplicated, if host running KVM vms. ( ... it is undocumented 😭 )
Evidence
In Linux kernel sources, user is accounted as cputime[CPUTIME_USER] and guest is as cputime[CPUTIME_GUEST],  by account_guest_time
Here is a source of 4.14-rc3
/*
 * Account guest cpu time to a process.
 * @p: the process that the cpu time gets accounted to
 * @cputime: the cpu time spent in virtual machine since the last update
 */
void account_guest_time(struct task_struct *p, u64 cputime)
{
	u64 *cpustat = kcpustat_this_cpu->cpustat;

	/* Add guest time to process. */
	p->utime += cputime;
	account_group_user_time(p, cputime);
	p->gtime += cputime;

	/* Add guest time to cpustat. */
	if (task_nice(p) > 0) {
		cpustat[CPUTIME_NICE] += cputime;
		cpustat[CPUTIME_GUEST_NICE] += cputime;
	} else {
		cpustat[CPUTIME_USER] += cputime; ⭐
		cpustat[CPUTIME_GUEST] += cputime; ⭐
	}
}

In case task_struct is virtual machine (e.g. KVM), account_guest_time accounts cputime to both cpustat[CPUTIME_USER] and cpustat[CPUTIME_GUEST].
account_guest_time has been introduced in v2.6.24-rc1. ( https://github.com/torvalds/linux/commit/94886b84b1bcdc95f34f70e7fce407efefe472e1 )
/*
 * Account guest cpu time to a process.
 * @p: the process that the cpu time gets accounted to
 * @cputime: the cpu time spent in virtual machine since the last update
 */
void account_guest_time(struct task_struct *p, cputime_t cputime)
{
	cputime64_t tmp;
	struct cpu_usage_stat *cpustat = &kstat_this_cpu.cpustat;

	tmp = cputime_to_cputime64(cputime);

	p->utime = cputime_add(p->utime, cputime);
	p->gtime = cputime_add(p->gtime, cputime);

	cpustat->user = cputime64_add(cpustat->user, tmp);
	cpustat->guest = cputime64_add(cpustat->guest, tmp);
}

How to correct ?
Subtracting guest time from user time.
user = user - guest

Example
Here is mpstat implementation.
https://github.com/sysstat/sysstat/blob/master/mpstat.c#L529-L568 (d7321c1)
/*
 ***************************************************************************
 * Display CPU statistics in JSON format.
 *
 * IN:
 * @tab		Number of tabs to print.
 * @g_itv	Interval value in jiffies multiplied by the number of CPU.
 * @prev	Position in array where statistics used	as reference are.
 *		Stats used as reference may be the previous ones read, or
 *		the very first ones when calculating the average.
 * @curr	Position in array where current statistics will be saved.
 ***************************************************************************
 */
void write_json_cpu_stats(int tab, unsigned long long g_itv, int prev, int curr)
{
	struct stats_cpu *scc, *scp;
	unsigned long long pc_itv;
	int cpu, next = FALSE;

	xprintf(tab++, "\"cpu-load\": [");

	/* Check if we want global stats among all proc */
	if (*cpu_bitmap & 1) {

		next = TRUE;
		xprintf0(tab, "{\"cpu\": \"all\", \"usr\": %.2f, \"nice\": %.2f, \"sys\": %.2f, "
			      "\"iowait\": %.2f, \"irq\": %.2f, \"soft\": %.2f, \"steal\": %.2f, "
			      "\"guest\": %.2f, \"gnice\": %.2f, \"idle\": %.2f}",
			 (st_cpu[curr]->cpu_user - st_cpu[curr]->cpu_guest) < ⭐
			 (st_cpu[prev]->cpu_user - st_cpu[prev]->cpu_guest) ? ⭐
			 0.0 :
			 ll_sp_value(st_cpu[prev]->cpu_user - st_cpu[prev]->cpu_guest, ⭐
				     st_cpu[curr]->cpu_user - st_cpu[curr]->cpu_guest, ⭐
				     g_itv),

⭐ are the points I mentioned above.
Also https://github.com/torvalds/linux/commit/94886b84b1bcdc95f34f70e7fce407efefe472e1 said

A modified "top(1)" is able to display good cpu user time and cpu guest
time by subtracting cpu guest time from cpu user time. Update "gtime" in
task_struct accordingly.

日本語
仮想マシン KVM で動かしている Linux ホストで metrics/linux/cpuusage.go の user と guest 時間が正確に表示できないので issue をたてました

Linux をホストとして KVM でゲストを実行していると、 /proc/stat が返す user 時間に guest 時間が余分に加算されます (カーネルのソースを参照してください)
解決するには user 時間から guest 時間を減算するよいです (mpstat のソースや　account_guest_time が追加された際のコミットログを参考にしてください)

Thank you for your issue report, I opened a pull request in #423. Please take a quick look.

Sorry for late reply ( I was on vacation ✈ ). Thank you for fixing 👍


feat: reexport BroadcastSender from fasyslog#6

Reexport  BroadcastSender from https://github.com/fast/fasyslog/pull/6

Thank you! I'll handle this patch today.

@BBArikL Pending for merging ...
You can ping me the next time, since PR doesn't send a direct notification, instead, it only sends to<EMAIL_ADDRESS>Besides, I'd recommend you to use a different branch name (rather than main) for contributing. Otherwise, when using git push to modify the patch, there is some frictions like "The upstream branch of your current branch does not match the name of your current branch."


change incorrect title, fix several console warnings

Codecov Report

Merging #364 (9f4b357) into develop (d01ab4e) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop     #364   +/-   ##
========================================
  Coverage    53.79%   53.79%
========================================
  Files           13       13
  Lines          329      329
  Branches        58       58
========================================
  Hits           177      177
  Misses         152      152

Flag
Coverage Δ

core-utils
53.79% <ø> (ø)

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

Continue to review full report at Codecov.

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


ext-gmp Plans?

Are there any plans, currently, to add support for php-gmp?

We didn't have a plan, but now we have because of your request.
@chingor13 Can you take a look?

Yep will do. I'm not seeing an major concerns about this extension so maybe we'll just compile it into PHP (rather than as shared). WDYT?

SG

I think this would be awesome – having to have a Dockerfile that simply installs GMP is a bit lame. Shared is 100% fine, there is nothing special about needing it as an external extension (afaict).

The gmp extension should now be available by default in the runtime for new deployments as of today's release.

Amazing.


Use erlang application name when fetching configuration.

Coverage remained the same at 100.0% when pulling ffb2c54046526c5f472b987e510868d9ecd6129e on use-erlang-app-name into d100c7256498852030389a2e835927fe994a76fb on master.


Consider changing Literal None fields

Is your feature request related to a problem? Please describe.
Currently, fields which are constant and None are described as:
abbreviation: Literal[None] = Field(None)

However, the type goes missing when rendering the schema:
"abbreviation": {
      "const": null,
      "default": null,
      "title": "Name"
    }

Describe the solution you'd like
We can get the same behavior by just making the field a NoneType:
abbreviation: type(None) = Field(None)

which renders as:
"abbreviation": {
      "default": null,
      "title": "Bar",
      "type": "null"
    }

Describe alternatives you've considered
We can leave things as they are, but we'd have to modify the schema when rendering to guis.
Additional context
Add any other context or screenshots about the feature request here.

The problem is not so much the null type as it is the Literal annotation, I think we should fix this at the level of the model create instead. Currently, if you make a Literal of type string, you have no way to know what is the type in the schema either.
I small method overload to this method should do the trick:
https://github.com/pydantic/pydantic/blob/9811727b1353e605d7183bae3d4e0d1d4ba30b95/pydantic/json_schema.py#L722
I have implemented the solution in another project where I am making my custom json model creator since the default pydantic one has some rough edges.
https://github.com/AllenNeuralDynamics/Aind.Behavior.Services/blob/aafc4da15293e3501106293173bf393bde26309f/src/DataSchemas/aind_behavior_services/utils.py#L44
Happy to make a PR if you want to go in this direction, as it would make my life easier as well.

Tracking https://github.com/pydantic/pydantic/issues/8905


Added print statements and save more items on pca_output dictionary

Please ignore and remove this pull request. It was a mistake on my end while trying to merge one branch (sfim) into main on my fork, not on your original repo. If I make some real changed, worth sharing, I will then open a pull request. This was just print statements for me.


Added basic getter for tenant and user details

Added a wrapper function for getting the tenant and user details as a dictionary, rather than pulling from database.
Closes #5

Changes Unknown when pulling 11fc21fa26d1641b86e5df6cb2068222623c0e04 on ananthanithya:admin-details-getter into ** on BenjamenMeyer:master**.

Please merge master, and update for pep8

@ananthanithya please update

will need to be revisited in light of PR #43


k8s 1.30 Support for rancher-alerting-drivers

Add k8s 1.30 Support for rancher-alerting-drivers

User is not able to find rancher-alerts chart on marketplace to install on v2.9.0-alpha5 (Local : v1.30.1+rke2r1, Downstream AKS : v1.30.0-eks-036c24b)
https://github.com/rancher/rancher/assets/149133120/a57bf0c6-ce0f-4ea3-85a6-50c12c3d5c00

Pass Verified in rancher v2.9-head Below are the test cases.
Local Cluster

Provisioned Rancher with local k8s v1.28.7+rke2r1 cluster.
Installed rancher-monitoring:104.0.0-rc1+up45.31.1
Installed rancher-alerting-drivers:104.0.0-rc1
Configured monitoring and alerting to monitor and send alerts on telegram
Upgraded Local cluster to k8s v1.30.1+rke2r1
Verified configured monitoring still sending alerts.
Monitoring passed p0 test cases.
Monitoring outbound links, grafana, prometheus targets function properly - ie, no dead links.
Chart annotations are correct.
Uninstall Monitoring and Alert app successfully on local cluster and deleted respective namespaces.
Fresh install monitoring and alert app on v1.30.1+rke2r1
Configured monitoring and alerting to monitor and send alerts on telegram on fresh installation of app.
Verified configured monitoring still sending alerts.
Monitoring outbound links, grafana, prometheus targets function properly - ie, no dead links.

Downstream Cluster

Provisioned downstream k8s 1.28.7+rke2r1 cluster.
Installed rancher-monitoring:104.0.0-rc1+up45.31.1
Installed rancher-alerting-drivers:104.0.0-rc1
Configured monitoring and alerting to monitor and send alerts on telegram
Upgraded downstream cluster to k8s v1.30.1+rke2r1
Verified configured monitoring still sending alerts.
Monitoring passed p0 test cases.
Monitoring outbound links, grafana, prometheus targets function properly - ie, no dead links
Chart annotations are correct.
Uninstall Monitoring and Alert app successfully on downstream cluster and deleted respective namespaces.
Fresh install monitoring and alert app on K8s v1.30.1+rke2r1
Configured monitoring and alerting to monitor and send alerts on telegram on fresh installation of app.
Verified configured monitoring still sending alerts.
Monitoring outbound links, grafana, prometheus targets function properly - ie, no dead links.


Add isValidOrEmpty Event

Had the use case to show if a date field was invalid as a user was typing into the text box.
Also, re-ordered a couple of attribute lists -- my bad.

Hey @peterheesterman, thanks for contributing.  Unfortunately I don't think this is an API that we can support.  It seems like what you really want to get at is the actual text typed in by the user, which can probably be gotten at by following the chains of refs down to the input element.  I think a better approach here would be to expose the onChange event in the DateInput component, which we can probably work into the refactor of that component.


Add GA4 copy event tracker

What

tracks text copy events within the browser
copied text is determined using the window.getSelection() method, assuming that some text has been highlighted to copy, if not does not send an event
strips PII, line breaks etc. from text

Have tested this in the major browsers, seems to be okay. Just in case I've wrapped the whole thing in a try/catch block to catch anything I've not thought of.
Why
Part of the GA4 migration.
Visual Changes
None.
Trello card: https://trello.com/c/s6uLhovR/751-add-tracking-browser-copy-events

I've pushed a commit on the assumption that the attribute will be copy_length but will change it later if the decision is to use something different.

@AshGDS have updated this PR...

changing the video_duration attribute to length
updating the video tracker and copy tracker code accordingly
changing the copy tracker to only record 30 chars

Feel free to re-review the whole thing, although it shouldn't be a huge change.


Support for Proximity placement group and Availability zone as input for VMWare to Azure and Hyper-V to Azure replications in Site Recovery Service

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR. How to fix?

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

[x] Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.

adding/removing APIs.
adding/removing properties.
adding/removing API-version.
adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

[ ] If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Please follow the link to find more details on API review process.

/azp run automation - sdk

Can one of the admins verify this patch?

/azp run automation - sdk

@ChenTanyi Can you please review the PR ?

@vidyadharijami API change need to be reviewed by ARM first.

          "$ref": "#/definitions/EnableProtectionInput"

can you explain why this input is adding new properties but they are not reflected in the response to this API?

Refers to: specification/recoveryservicessiterecovery/resource-manager/Microsoft.RecoveryServices/stable/2018-07-10/service.json:2688 in ebf307e. [](commit_id = ebf307e804782e07d98b9c525a61b66b4e37a448, deletion_comment = False)

          "$ref": "#/definitions/EnableProtectionInput"

can you explain why this input is adding new properties but they are not reflected in the response to this API?
Refers to: specification/recoveryservicessiterecovery/resource-manager/Microsoft.RecoveryServices/stable/2018-07-10/service.json:2688 in ebf307e. [](commit_id = ebf307e, deletion_comment = False)

We have added optional properties in provider specific properties for both input and API response. And here we have added for V2A and H2A.

I'm not seeing these new properties in the response. Can you point me to the line number that contains "targetAvailabilityZone" in the response definition for PUT "/Subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.RecoveryServices/vaults/{resourceName}/replicationFabrics/{fabricName}/replicationProtectionContainers/{protectionContainerName}/replicationProtectedItems/{replicatedProtectedItemName}"

Line number : 10487  in HyperVReplicaAzureReplicationDetails
"targetAvailabilityZone": {
"description": "The target availability zone.",
"type": "string"
},
"targetProximityPlacementGroupId": {
"description": "The target proximity placement group Id.",
"type": "string"
},
Line number 11899 :  in InMageAzureV2ReplicationDetails
"targetAvailabilityZone": {
"description": "The target availability zone.",
"type": "string"
},
"targetProximityPlacementGroupId": {
"description": "The target proximity placement group Id.",
"type": "string"
},


completed all todo's and changed a animation to be unique

NIce work!
If your commit message needs an "and" best that you had made each a separate commit.


Blockchain Tree Service

Issues

Tree State is behind the rw lock
https://github.com/paradigmxyz/reth/blob/9312424db05b066cee6fae40471dc679ed35cef8/crates/blockchain-tree/src/shareable.rs#L29-L32

Any meaningful tree operation requires a write lock
Any rpc query on the pending state might be waiting for the write lock to be lifted

Connecting buffered blocks is a recursive operation in a non-obvious case
https://github.com/paradigmxyz/reth/blob/9312424db05b066cee6fae40471dc679ed35cef8/crates/blockchain-tree/src/blockchain_tree.rs#L828

In the worst case, this would connect up to 3 epochs worth of blocks. This might be the root cause of https://github.com/paradigmxyz/reth/issues/6905

Cumbersome state tracking
Any pending or side chain in the blockchain tree has an in-memory state attached to it. Over the last months, we've had multiple cases of state corruption (https://github.com/paradigmxyz/reth/pull/5683, https://github.com/paradigmxyz/reth/pull/5921, https://github.com/paradigmxyz/reth/pull/6821) due to mishandling of in-memory state after canonical state update.

Solution
Blockchain Tree should be rewritten into a message-passing service. The engine should send control commands to the tree service. The tree service should orchestrate how to prioritize the received actions.
The tree service interface should be async.
struct BlockchainTreeHandle {
  to_tree: UnboundedSender<TreeMessage>,
}

struct BlockchainTreeService {
  messages_rx: UnboundedReceiverStream<TreeMessage>,
  task_spawner: Arc<dyn TaskSpawner>, // for concurrent payload processing
}

// impl Future for BlockchainTreeService { ... }

Downgrade the lock to wrap only the actual tree state. Double-check if the lock is necessary at all.
Tree Action Prioritization:

New Payloads can be processed in parallel
FCU can only be processed one at a time and no New Payloads should be processed in parallel at this point
FCU should be prioritized over any new payload unless the new payload is required to process the FCU

We might need to move the ancestor check to the tree. This information should be included in the response that the tree sends back to the engine.
Testing
All existing tests should be ported over to the new service.
We should have chain generation test utils for easier testing of the tree .

closing because we're rewriting this


Bug with Django 3.2: get_meta() missing 1 required positional argument: 'is_partition'

When running and import I get the following stacktrace:
inspectdb_refactor --database=arpguard --app=API
"C:\Program Files\JetBrains\PyCharm 2019.2\bin\runnerw64.exe" D:\Local_Development\DeviceAndNetworkInventory\venv-arpguard-api\Scripts\python.exe "C:\Program Files\JetBrains\PyCharm 2019.2\plugins\python\helpers\pycharm\django_manage.py" inspectdb_refactor --database=arpguard --app=API D:/Local_Development/DeviceAndNetworkInventory/ArpGuardAPI/source
Tracking file by folder pattern:  migrations
Traceback (most recent call last):
  File "C:\Program Files\JetBrains\PyCharm 2019.2\plugins\python\helpers\pycharm\django_manage.py", line 52, in <module>
    run_command()
  File "C:\Program Files\JetBrains\PyCharm 2019.2\plugins\python\helpers\pycharm\django_manage.py", line 46, in run_command
    run_module(manage_file, None, '__main__', True)
  File "C:\Python39\lib\runpy.py", line 210, in run_module
    return _run_module_code(code, init_globals, run_name, mod_spec)
  File "C:\Python39\lib\runpy.py", line 97, in _run_module_code
    _run_code(code, mod_globals, init_globals,
  File "C:\Python39\lib\runpy.py", line 87, in _run_code
    exec(code, run_globals)
  File "D:/Local_Development/DeviceAndNetworkInventory/ArpGuardAPI/source\manage.py", line 22, in <module>
    main()
  File "D:/Local_Development/DeviceAndNetworkInventory/ArpGuardAPI/source\manage.py", line 18, in main
    execute_from_command_line(sys.argv)
  File "D:\Local_Development\DeviceAndNetworkInventory\venv-arpguard-api\lib\site-packages\django\core\management\__init__.py", line 419, in execute_from_command_line
    utility.execute()
  File "D:\Local_Development\DeviceAndNetworkInventory\venv-arpguard-api\lib\site-packages\django\core\management\__init__.py", line 413, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "D:\Local_Development\DeviceAndNetworkInventory\venv-arpguard-api\lib\site-packages\django\core\management\base.py", line 354, in run_from_argv
    self.execute(*args, **cmd_options)
  File "D:\Local_Development\DeviceAndNetworkInventory\venv-arpguard-api\lib\site-packages\django\core\management\base.py", line 398, in execute
    output = self.handle(*args, **options)
  File "D:\Local_Development\DeviceAndNetworkInventory\venv-arpguard-api\lib\site-packages\inspectdb_refactor\management\commands\inspectdb_refactor.py", line 118, in handle
    self.handle_inspection(options)
  File "D:\Local_Development\DeviceAndNetworkInventory\venv-arpguard-api\lib\site-packages\inspectdb_refactor\management\commands\inspectdb_refactor.py", line 270, in handle_inspection
    for meta_line in self.get_meta(table_name, constraints, column_to_field_name, is_view):
TypeError: get_meta() missing 1 required positional argument: 'is_partition'

For me this seems to be an incompatibility with newer Django versions. I'm using Django 3.2 for my project. The last working version seems to be 2.1.

Try using the github's version, not the one from PyPi.
Issue #9


Flesh out resolve_types

Trying to improve resolve_types.

@hynek vroom vroom?

Do we know someone who knows what any of this means and could review?

Hello.  Happy to review.
So this is backwards incompatible change because before the default was for include_extras=False and we've change it to be True.  I'm not sure this is a complete deal breaker though as this variable only matters when using Annotated.
See https://peps.python.org/pep-0593/#interaction-with-get-type-hints
From the get_type_hints documentation:
The function recursively replaces all Annotated[T, ...] with T, unless include_extras is set to True (see Annotated for more information).
So I guess my question is if we're happy with the documentation of "this resolves the types more accurately."

You're right in that this is technically backwards incompatible, I made the call with the following assumptions:

the change is relatively minor (I'm not aware of any use case other than Annotated at this time, I think)
the change will affect very few users (subjective, because no one has opened an issue about not having access to Annotated via resolve_types)
the new default is, IMO, more correct so I'd prefer to suffer a little pain now rather than drag the bad default on forever

Happy to change the default if you folks think that's the right call.
As for the docs, happy to be more precise if we think that'll be useful to the readers.

I wonder if for the docs it could say that the value is passed in to get_type_hints and leave it at that.  Since it's possible the definition of include_extras could change in the future?  (As in maybe it does more than Annotated and now our docs would be out of date with python.). But that's a pretty minor difference all things considered.
As to the default value, I'm of 2 minds. It's nice when you get the latest and greatest by default.  However I'm not sure I like that our default is the opposite of python's.  That being said, our method is not called the same as theirs so it might be ok to reverse the default here.

Yeah I think I'm fine with this "breakage" since nobody except Tin is using Annotated and this seems still like a beta feature. Hiding it behind an option would give us another auto_attribs=True.

Eh sorry, was this ready for merge?

Yeah, barring any bikeshedding around the docs.


add function and widget to convert binary mask to mesh compatible with surforama

From discussion with @LorenzLamm  and @rdrighetto

Thanks @rdrighetto ! We should definitely have a look at those if we find we are having meshing performance issues.
I think we are good to get started with the new function / widget introduced in #29, so I will close this for now. We can re-open if we find that we need to improve the meshing. Thanks everyone!


Updated the ESP8266 notifier to use ESP32

a slight change to library includes and defining and LED pin where all there where needed.
I could refactor this to support both boards by preprocessor defintion.s

@DarthPJB hey, thanks for the pull, lets see if it lights up.

@DarthPJB LGTM


Release 0.2

There are two things blocking hackage release as per https://github.com/input-output-hk/stack2nix/blob/master/stack.yaml#L6:

[ ] hackage-db filters out deprecated packages, but those are sometimes part of stackage LTS, upstream declined my patch https://github.com/peti/hackage-db/pull/7
[ ] couldn't upstream default resolver to cabal2nix https://github.com/NixOS/cabal2nix/pull/322

For hackageDB we call:
loadHackageDB :: Maybe FilePath
              -- ^ The path to the Hackage database.
              -> Maybe UTCTime
              -- ^ If we have hackage-snapshot time.
              -> IO DB.HackageDB
loadHackageDB optHackageDB optHackageSnapshot = do
  dbPath <- maybe DB.hackageTarball return optHackageDB
  DB.readTarball optHackageSnapshot dbPath

which could be modified to use lower bits to avoid https://github.com/domenkozar/hackage-db/commit/0b58f1062d0a87b06bbae343d3c5a2f86ba26537

For resolver, I think we have to finally make cabal2nix a proper library.

Alright I've opened a PR upstream: https://github.com/NixOS/cabal2nix/pull/357


[Issue]: Rebuildable AETN, workers dont pick neutronium cores NOT dropped from natural AETN

Description of the bug/crash
I have several neutronium cores in my base, but the workers only use those which dropped from AETNs in the world.
Those from care package are not being used.
Steps To Reproduce
simply doesnt work
Player.log
no crash

Show me a screenshot.

Btw...I deactivated all mods to make sure its not another mod interfering.

nvm...I didnt see that the neutronium cores from the care package have to go through the analyzer first -.-
 They are only moved that close to the thing because I made my dupes manually move them there to be shown in the picture.

@MrPurple6411 attach your save file and the log.

Log:
Player.log
Zipped Save:
Lucky Galaxy.zip
Workshop mod list file:
appworkshop_457140.zip

@MrPurple6411  you using this mod: https://steamcommunity.com/sharedfiles/filedetails/?id=2963257205
That's the problem. The cores are too cold, set a value from -250C, for example.

@SanchozzDeponianin  ahh yes thank you :-) such small dumb mistake on my part. very sorry to have bothered you :-)


[feature request] streamline the GUI

Hi, I just wanted to say that it would be nice not only to add "features" but also streamline the GUI as I think this one is a bit cluttered, too much stuff on the main window. Here are some suggestions
This is a clean layout

this is a bit confusing

You can click the collapse/expand button to hide/show the download options (the ^ interface element below the "Queue actions" button). I have no plans to declutter the interface beyond that.


Loading local files, with require(), adds .js extension to path

I need to load a local environment file tha has all of my api urls.  I tried doing the following:
Loading the file:
let resource = require('resource')

Changes made to system_config_dev:
 protected SYSTEM_CONFIG_DEV = {
    defaultJSExtensions: true,
    paths: {
      [this.BOOTSTRAP_MODULE]: '${this.APP_BASE}${this.BOOTSTRAP_MODULE}',
      'angular2/*': '${this.APP_BASE}angular2/*',
      'rxjs/*': '${this.APP_BASE}rxjs/*',
      'resource': '${this.APP_BASE}resource',  // Added this line
      '*': '${this.APP_BASE}node_modules/*'
    },
    packages: {
      angular2: { defaultExtension: false },
      rxjs: { defaultExtension: false },
      resource: { defaultExtension: false }  // Added this line
    }
  };

However it is still trying to load the file with .js extension at the end.  So I also tried the same method for resource.json, but again it added a .js at end.  What do I need to do?

Use require('./resource.json');. Take a look at the config here.

Thanks for quick reply however issue is not that it doesn't load from correct path, it is that it is loading resource.json.js instead of just resource.json.  So the path is fine, its the extension that is wrong because the default extension is set to JS and for some reason it is not reading the overwrite in packages.
Here is screenshot:
If I do require('./resource.json');

If I do require('./resource');

'resource': '${this.APP_BASE}resource',  // Added this line

means /resource.js (because there's defaultJSExtensions: true). If resource is located in different directory use:
'resource': '${this.APP_BASE}/data/resource'

Now resource will be loaded from /data/resource.js.

Sorry if I am not explaining it correctly but the path is not the issue, the extension is.  So how do we make the app call a require or a require.json file with .js extension?

You need to disable the defaultJSExtension option for this "module". For further information take a look at the SystemJS API docs.


Unrecognizable enums and custom classes In remote

Godot version
4.2 Stable
System information
Windows 10
Issue description
Exported custom classes in C#, during play in remote, show the object ID instead of a recognizable name.
Also, exported enums are shown as numbers during play in remote, instead of strings.
I know I could export a Dictionary holding a string identifier and the enum or custom class, but that's redundant code I'd rather avoid.

Steps to reproduce
Create a class that inherits a node2D or Resource and export it or export an enum representing an integer.
Minimal reproduction project
N/A

Doesn't seem to be specific to topic:dotnet:

Doesn't seem to be specific to topic:dotnet:

Yeah, also happens in GDScript for enum, where it only shows the integer value.

Related to https://github.com/godotengine/godot/issues/79476.


how to stream a video file in videoplayer as avplayer from webserver(http://123.134.134.....)

i'd like to stream video file in player. video file exist in my own webserver. so what i want to do is i send a file url and get a file data and play file in video player... for example avplayer or anything is ok.. how can i do this??

As for now it's hard to accomplish, custom headers and new file serving is already ongoing, so it should be available easily in a couple of days.

so .. you mean that it is impossible?? right...?? or not?

@shindonghyeok it used to be supported by the older versions of Swifter but it was removed (00321c9). The reason of that is the implementation was loading a file into memory with every request. If you need that right now, please take what we have before.


WinPB: Add VS2019 support for Windows JDK15 builds

eclipse/openj9#9805
add top level main.yml, MSVS_2019 role and add openssl 1.1.1g built with VS2019

Signed-off-by: Joe deKoning<EMAIL_ADDRESS>

Testing at https://ci.adoptopenjdk.net/view/Tooling/job/VagrantPlaybookCheck/780/

@jdekonin I think the when condition for Download OpenSSL-1.1.1g and Unpack OpenSSL-1.1.1g for installation needs to have appended to it
or (not openssl64_vs2019_installed.stat.exists)

Re-testing at : https://ci.adoptopenjdk.net/view/Tooling/job/VagrantPlaybookCheck/828/ now that I can test for JDK15 builds

Both changes applied to commit with a rebase.

Hmm, I ran it locally (As the vpc job failed), and I got the following error message (for both the items in the task)
TASK [MSVS_2019 : Register Visual Studio Community 2019 DIA SDK shared libraries] ***
failed: [<IP_ADDRESS>] (item=C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\DIA SDK\bin\msdia140.dll) => {"ansible_loop_var": "item", "changed": true, "cmd": "regsvr32 /s \"C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Community\\DIA SDK\\bin\\msdia140.dll\"", "delta": "0:00:00.153664", "end": "2020-08-17 01:01:36.418646", "item": "C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Community\\DIA SDK\\bin\\msdia140.dll", "msg": "non-zero return code", "rc": 3, "start": "2020-08-17 01:01:36.264982", "stderr": "", "stderr_lines": [], "stdout": "", "stdout_lines": []}

Updated with a missed spot for a condition.  Should be good now.
I'm not sure what to say about the registering of msdia140.dll.  Have you tried it manually on the same system?  Files present?  rc=3 is LoadLibrary failed.  Is the o/s 64bit support only?  This works on Windows 2012.  I have not tested on other releases.

To be fair, I've seen this issue with MSVS_2017 previously, and it does seem to be intermittent. I've created a branch with the changes in this PR and the Checksum update in #1512 so I can test using VPC, again.


Auto update copyright for auto exclusion

Signed-off-by: renfeiw<EMAIL_ADDRESS>

reviewers: @smlambert @llxia

I think that the write access for @llxia who is one of the 2 reviewers is not quite trickled out yet, expect that the committers of the AQAvit project to have these permissions soon.


refactor(next-edit-button): instead of looping through edits, go through them in reverse order

Done in 6d8d47c


Breaking Backend interface into smaller pieces

The Backend interface, in aggregate, is large and getting larger. I've started establishing a pattern with the versioning support for having interface subsets that a backend implementer can optionally support. The use case for this is one I found myself running into regularly when working with Afero, and also with a FUSE-based project: when there's a huge API surface, but you only need to support a reasonable subset of it for your use-case, it can be cumbersome and inconvenient to do so without some help from the API itself.
As I feel one of the key value propositions gofakes3 offers is in testing S3 integrations in the context of your own project's infrastructure without having to resort to Mock Soup, I think this is something we should be working towards making convenient, so here's an attempt at doing some of that! The idea here is that if you needed to provide your own backend, there would be areas of the S3 integration surface that were relevant to your project, and areas that were not, so you shouldn't be forced to implement the latter.
The two things I've done here in service of that are to break DeleteMulti into a separate interface (it is now polyfilled if your backend doesn't support it directly) and to move CreateBucket and DeleteBucket into a separate interface too (this positively affects the Afero single-bucket backend, which has now had its ErrNotImplemented methods removed).
The upshot is that the core Backend interface is now only 7 methods, and ideally it would stay hovering around that, which is pretty reasonable from an implementer's point of view. Inside of that, there are some cases where you can cut corners as well (for example, we don't properly support pagination in ListBuckets yet, which turns out to be absolutely fine in practice), so I'll spend some time flushing those out and documenting them in the interface. It's not exactly trivial to implement a Backend, but it shouldn't be mystifyingly difficult to go from "zero" to the guts of a functioning one in a short amount of time either.
~NOTE - this PR is based on https://github.com/johannesboyne/gofakes3/pull/28 and depends on that merge, so it should stay WIP until that one has been given a thorough dissection!~ Also need a test on the DeleteMulti polyfill process.
TODO:

[ ] Test DeleteMulti polyfill process

Codecov Report

Merging #29 into master will decrease coverage by 11.75%.
The diff coverage is 35.52%.

@@             Coverage Diff             @@
##           master      #29       +/-   ##
===========================================
- Coverage   76.49%   64.73%   -11.76%
===========================================
  Files          14       14
  Lines        1021     1245      +224
===========================================
+ Hits          781      806       +25
- Misses        167      343      +176
- Partials       73       96       +23

Impacted Files
Coverage Δ

option.go
50% <0%> (-12.5%)
:arrow_down:

hash.go
83.87% <100%> (-5.79%)
:arrow_down:

uploader.go
87.61% <100%> (-0.24%)
:arrow_down:

error.go
63.41% <20%> (-3.26%)
:arrow_down:

gofakes3.go
52.72% <29.44%> (-15.49%)
:arrow_down:

messages.go
37.71% <32.55%> (-28.95%)
:arrow_down:

routing.go
67.27% <37.14%> (-16.48%)
:arrow_down:

prefix.go
90.62% <93.33%> (+0.96%)
:arrow_up:

util.go
68.96% <0%> (-10.35%)
:arrow_down:

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 b60435e...c71d670. Read the comment docs.

closed due to inactivity - happy to re-open again ;-)


Detect common installation mistakes and show error message

[ ] User forgets to clone community => Look for action we depend on and show error message during init if not detected
[ ] User clones monorepo instead of cursorless-talon => Have python file at root of mono-repo that shows error message

See https://github.com/cursorless-dev/cursorless/issues/1951 for an example where a user tried to use cursorless without Talon community repo

Sounds good


:robot: Triggering CI on branch 'release-next' after synching to openshift/master

/test 4.4-e2e

OCF Webhook is merging this PR


Dreame L10 Pro Cleaning mode

Hi. In cleaning mode list i see only "sweeping"
Screenshots

Model Name: dreame.vacuum.p2029
Firmware Version: 4.1.8_1138
Home Assistant Version: 2022.10.4
Configuration Type: With map support

oh. sorry.
i need insert water tank first.
Now i see sweeping and mopping.
Only mopping posible?


Graph tests

After adding many new details to a graph, I've been running the whole program to see if it succeeds at getting to the latest items, but when it doesn't, it takes quite a deal of work to find out why--I've used the visual graph a few times to find places where I've missed edges.
Ideally we would have a better solution for this. In keeping with the codegen, we could write our tests in yaml, at least the ones that are formulaic:
- with: [items...]
  context:
    foo: bar
  requires: item
  goal: Spot or item

Some ideas for tests:

any_path_to to check that the given setup can reach the target spot
no_path_to for the opposite
can_obtain to test collecting an item (at any location available)
requires to test both any_path_to and no_path_to with/without a specific item
path to check a specific path

The generated test code should be able to pinpoint where in the graph the expectation fails (which would be different based on the type of test, for example), or at least be more descriptive than simply "panicked because it couldn't reach the objective".

Structure of this is going to be macros and functions defined in analyzer and codegen a test file with all the tests.
It'd be hard to find specific exits that don't exist, except in the case of a specific path. So for the proposed any_path_to, we'd output all steps from a spot we can access to a spot we can't. (Unfortunately this includes testing warps at every spot.)
Currently we can't simulate having other movement types, but that could be done with a refactoring of local_travel_time.


Fixes to get build running again on macOS.

Basically, re-applying changes from #41 which were lost in efec217.
We need to be careful here, because I remember the original changes in #41 broke the release process. However, I think this should good as we're using ConvertableFilePath etc rather than string, which iirc is what the original problem was.
Integration tests failing for me on the mac, but I don't think that's anything to do with any of this.

@binarymash merged


SET and REPLACE deprecated?

I get these messages when I run, and it's ok! It's a warning. But I can't find the new way to do the things. It's not in the docs (I'm currently using what is in the docs), and it doesn't seem to be anywhere.
Where can I get info?

The documentation seems to not be up to date with the README file.
On the doc you can read SET work this way:
client.set('testKey', 'testValue', (err, result) => {
    assert.isNull(err);
    done();
}, { expire: 60 });

But on the README file:
client.set('testKey', 'testValue', { expire: 60 }, (err, result) => {
    assert.isNull(err);
    done();
});

The second one do not log any warning. But the mandatory object parameter is a bit annoying.

Fixed the README in #112


Jenkins Build collector

Hi,
When i am spinning hygieia instance using docker compose file, i am getting below highlighted error though i can see all the the jobs in drop down list in widget for the jenkins instance configured in docker compose file
ERROR c.c.d.collector.DefaultHudsonClient - Client exception loading build details: 403 Forbidden.
Please let me know if you require more detail.

@Ishan1987  - go to  hygieia-jenkins-build-collector.properties file and set jenkins.saveLog= false.

@nireeshT  I am still getting the same error post setting the variable  jenkins.saveLog to false inside the container and restarted the container.
the WARN  c.c.d.collector.DefaultHudsonClient - Credentials for the following url was not found. This could happen if the domain/subdomain/IP address in the build url returned by Jenkins and the Jenkins instance url in your Hygieia configuration do not match:
hygieia-jenkins-build   ERROR c.c.d.collector.DefaultHudsonClient - Client exception loading build details: 403 Forbidden. URL =

@nireeshT  Please let me know if you need more detail to resolve above mentioned error.

Your properties isn't configured correctly. You need to make sure that the uri returned by jenkins rest calls (the one that is configured in global properties as the Jenkins host) is the exact same as what you are using for your jenkins.servers[x] in your config.

Please reopen if issue is not resolved.


Don't want a  for text readOnly field

I have a column of type text and readOnly true.  When in edit mode, I don't want the  textbox to show.  I tried this:
editTemplate: function(value, item) {                  return value;               }
Visually, it works exactly as what I want, ie the existing value is just shown in the table cell.  But now when I try to save an edit, an exception (Cannot read property 'val' of undefined) somewhere in jsgrid.min.js.
I have seen various examples of the editTemplate in issues #682 and #271 but am totally floored by the pattern used.  How do I have simple plain text in edit mode for a text or textarea type, or is there documentation available on how the editTemplate is to be used?
Thanks.

Once you completely redefines editTemplate, the editValue should be also redefined. This method should return the edited value of the field. These two properties usually goes along.
When only editTemplate is redefined, once the editValue is called it throws because edit control is not created.


Image download link is obsolete in lesson 1/4

Hi there,
Thanks for providing this nice tutorial.
The windows image link on this page seems obsolete.

The Microsoft Edge team no longer offers VM image downloads for the testing of Microsoft Edge and Internet Explorer.

You may consider updating the link to https://developer.microsoft.com/en-us/windows/downloads/virtual-machines/
-Xiongwei

Thanks for that catch! I'll adjust the link soon.

Fell off the radar, but the links have been fixed.


Minor fixes

This PR will

Add a more expressive lookup exception text and change the name according to Pythonic naming conventions
format the default SWC registry JSON to be more readable
add __repr__ methods to each object for better debug output
fix minor formatting issues using black

The most notable change will be in the repr methods, so now we'll have a formatted output such as
In [4]: from swc_registry import SWC

In [5]: SWC("SWC-101")
Out[5]: <SWC swc_id=SWC-101 title=Integer Overflow and Underflow

In [6]: from swc_registry.get_entry_info import SWCRegistry

In [7]: SWCRegistry()
Out[7]: <SWCRegistry with 29 entries>

Thanks, @dmuhs, looks cool! :)


(wip) init infer at v0.15.0

Motivation for this change
New package for infer, an open-source static analysis tool maintained by facebook.
12/16/18: This PR is NOT FINISHED yet. I'm putting it here to ask for some help with a couple issues I've run into trying to compile these tools.
Organization:
This PR currently contains three new packages:

infer-deps - the ocaml 4.06.1+flambda compiler and the opam requirements from the opam.lock file for infer
facebook-clang - a custom clang for infer (see facebook-clang-plugins) that facilitates plugins for clang-analyzer and clang-frontend
infer - the project itself, for analysis of Java, C, C++, and Objective C code

I did also add a source.nix for installing the precompiled binaries, but I assume that won't be liked upstream since we prefer binaries built on the nix build farm?

Problems:
As you can see from their install and getting started pages, they recommend running Infer inside a Docker container on Linux. There is a homebrew formula available for macOS, but on Linux they recommend using their precompiled binaries if not using Docker.
The problems I'm having with writing this package generally revolve around the custom clang:

[ ] macOS: clang build fails about 25% of the way through make with this (truncated) error message:

macOS dynamic lib issue

[ 26%] Linking CXX shared library ../../../../lib/clang/7.0.0/lib/darwin/libclang_rt.tsan_osx_dynamic.dylib
ld: warning: linking against a dylib which is not safe for use in application extensions: /nix/store/f8y5mdc0sjf5lx97j8xqnnrhsad6f3xw-libc++-5.0.2/lib/libc++.dylib
ld: warning: linking against a dylib which is not safe for use in application extensions: /nix/store/h7rxgvw954lmc3xvb0jxnjbdax92v107-libc++abi-5.0.2/lib/libc++abi.dylib
ld: warning: linking against a dylib which is not safe for use in application extensions: /nix/store/x7v2211y4864na7ggfiqjx1wwbq90gsc-Libsystem-osx-10.11.6/lib/libc.dylib
ld: warning: linking against a dylib which is not safe for use in application extensions: /nix/store/f8y5mdc0sjf5lx97j8xqnnrhsad6f3xw-libc++-5.0.2/lib/libc++.dylib
ld: warning: linking against a dylib which is not safe for use in application extensions: /nix/store/h7rxgvw954lmc3xvb0jxnjbdax92v107-libc++abi-5.0.2/lib/libc++abi.dylib
ld: warning: linking against a dylib which is not safe for use in application extensions: /nix/store/x7v2211y4864na7ggfiqjx1wwbq90gsc-Libsystem-osx-10.11.6/lib/libc.dylib
/nix/store/ykzmq1yyggy8c8gfvxqzrd292j1ld797-bash-4.4-p23/bin/bash: codesign: command not found
make[2]: *** [projects/compiler-rt/lib/tsan/CMakeFiles/clang_rt.tsan_osx_dynamic.dir/build.make:731: lib/clang/7.0.0/lib/darwin/libclang_rt.tsan_osx_dynamic.dylib] Error 127
make[2]: *** Deleting file 'lib/clang/7.0.0/lib/darwin/libclang_rt.tsan_osx_dynamic.dylib'
make[1]: *** [CMakeFiles/Makefile2:25117: projects/compiler-rt/lib/tsan/CMakeFiles/clang_rt.tsan_osx_dynamic.dir/all] Error 2
make: *** [Makefile:152: all] Error 2
builder for '/nix/store/l7nja9b7af0r292zilwb9rcy19mj5mq7-facebook-clang.drv' failed with exit code 2

I assume this might be the type of issue that could be fixed by fixDarwinDylibNames but I don't know enough about how that pkg works to use it here. I'm also wary of continuing the attempt on macOS before getting the Linux side fully working since I think I might run into similar errors later on.

[ ] linux: here, clang gets much further through compilation, down to the external tools. One of the tools required is compiler-rt, and building this tool fails here:

CMakeError.log from compiler-rt

Compiling the C compiler identification source file "CMakeCCompilerId.c" failed.
Compiler: /tmp/nix-build-facebook-clang.drv-0/llvm/build/./bin/clang
Build flags:
Id flags:
The output was:
1
impure path `/usr/lib/gcc/x86_64-linux-gnu/7.3.0/../../../x86_64-linux-gnu/crt1.o' used in link
clang-7.0: error: linker command failed with exit code 1 (use -v to see invocation)
Compiling the CXX compiler identification source file "CMakeCXXCompilerId.cpp" failed.
Compiler: /tmp/nix-build-facebook-clang.drv-0/llvm/build/./bin/clang++
Build flags:
Id flags:
The output was:
1
impure path `/usr/lib/gcc/x86_64-linux-gnu/7.3.0/../../../x86_64-linux-gnu/crt1.o' used in link
clang-7.0: error: linker command failed with exit code 1 (use -v to see invocation)
Determining if the C compiler works failed with the following output:
Change Dir: /tmp/nix-build-facebook-clang.drv-0/llvm/build/tools/clang/runtime/compiler-rt-bins/CMakeFiles/CMakeTmp
Run Build Command:"/nix/store/crsfyhfdllxvdrrkv8jhyk7i7ahyn124-gnumake-4.2.1/bin/make" "cmTC_dd491/fast"
make[3]: Entering directory '/tmp/nix-build-facebook-clang.drv-0/llvm/build/tools/clang/runtime/compiler-rt-bins/CMakeFiles/CMakeTmp'
/nix/store/crsfyhfdllxvdrrkv8jhyk7i7ahyn124-gnumake-4.2.1/bin/make -f CMakeFiles/cmTC_dd491.dir/build.make CMakeFiles/cmTC_dd491.dir/build
make[4]: Entering directory '/tmp/nix-build-facebook-clang.drv-0/llvm/build/tools/clang/runtime/compiler-rt-bins/CMakeFiles/CMakeTmp'
Building C object CMakeFiles/cmTC_dd491.dir/testCCompiler.c.o
/tmp/nix-build-facebook-clang.drv-0/llvm/build/./bin/clang    -o CMakeFiles/cmTC_dd491.dir/testCCompiler.c.o   -c /tmp/nix-build-facebook-clang.drv-0/llvm/build/tools/clang/runtime/compiler-rt-bins/CMakeFiles/CMakeTmp/testCCompiler.c
Linking C executable cmTC_dd491
/nix/store/451ffnn773jrl8qmhjs71dqd6pkfx2rx-cmake-3.12.1/bin/cmake -E cmake_link_script CMakeFiles/cmTC_dd491.dir/link.txt --verbose=1
/tmp/nix-build-facebook-clang.drv-0/llvm/build/./bin/clang      CMakeFiles/cmTC_dd491.dir/testCCompiler.c.o  -o cmTC_dd491
impure path `/usr/lib/gcc/x86_64-linux-gnu/7.3.0/../../../x86_64-linux-gnu/crt1.o' used in link
clang-7.0: error: linker command failed with exit code 1 (use -v to see invocation)
make[4]: *** [CMakeFiles/cmTC_dd491.dir/build.make:87: cmTC_dd491] Error 1
make[4]: Leaving directory '/tmp/nix-build-facebook-clang.drv-0/llvm/build/tools/clang/runtime/compiler-rt-bins/CMakeFiles/CMakeTmp'
make[3]: *** [Makefile:121: cmTC_dd491/fast] Error 2
make[3]: Leaving directory '/tmp/nix-build-facebook-clang.drv-0/llvm/build/tools/clang/runtime/compiler-rt-bins/CMakeFiles/CMakeTmp'

In the custom clang build script, this option is enabled with -DLLVM_BUILD_EXTERNAL_COMPILER_RT=On. I poked around in the nix expression for llvm_7 and the llvm.Packages.compiler-rt files, but I'm still not entirely sure how to fix an impure path being linked with nix. I expect the cmake config for compiler-rt is linking against the library path it shouldn't be, but adding gcc, gcc_multi, clang_5, glibc or llvm to buildInputs didn't seem to fix the issue. I tried not passing that option to facebook-clang, but if I do that then the infer build eventually fails with a similar issue:

 Lines from infer/config.log when trying to build using custom clang WITHOUT compiler-rt

Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/7
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/7.3.0
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/8
Selected GCC installation: /usr/lib/gcc/x86_64-linux-gnu/7.3.0
Candidate multilib: .;@m64
Selected multilib: .;@m64

Those are the current issues with this project. Any advice/edits would be much appreciated. Also feel free tell me if I should reorganize the files - I don't really like that three new packages are being added instead of just one, but I don't know how to put these all in the same directory and make them "inferPackages" like how llvm does it.
TODO

[x] get java analyzers working
[ ] get c analyzers (i.e. clang) working

[ ] at this point the checkPhase call for make test should work properly

[ ] condense infer-deps and facebook-clang into infer to one package to clean up

[ ] joining these will allow getting rid of the hacky postUnpack phases in infer-deps and facebook-clang to work with opam

[ ] add utop v2.1.0 for:

[ ] infer REPL
[x] make config_tests, which runs when one of java or c analyzers are disabled

[ ] maybe add option to install precompiled bins?

Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Noting here - infer released 0.16.0 about a month ago. I'm leaving this PR up for now, but will try to get 0.16 working instead, since it looks like it may be easier to get working in package managers (upgrades to opam2, and clang 7.0.0, among other changes)

I guess you should use buildOcaml and buildDunePackage. opam-build I saw several months ago in channel, search in history. It would be hard to implement build phase by opam (by several reasons: opam trying to download dependencies, but nix must know about all the dependencies before the building start. And even if you have build cache, it would be hard to reuse, because ocamlc hardcode ablosute paths in ocaml bytecode, and opam do same in opam's switch and opam's root configuration. So if you would try this, use symlinks to mimic same paths at build phase).

@Pitometsu thanks for the advice. I'm trying an approach right now by just manually setting OPAMROOT to a subdir under $out but that doesn't seem like a good convention. I'll check out buildOcaml and buildDunePackage, especially now since infer 0.16+ has upgraded to opam 2.0.

Closing this since 0.15.0 is pretty out of date. Hopefully i can come back and get 0.17.0 working in a different PR.


jq command not found

I got the following error:
/actions-runner/_work/_actions/related-sciences/gce-github-runner/main/action.sh: line 175: jq: command not found
(23) Failed writing body

Should related-sciences/gce-github-runner be responsible for installing jq or is that up to the workflow using it?

Here is where jq is called first:
https://github.com/related-sciences/gce-github-runner/blob/6cb6998237b68764579d45dde1dabd94fa494f47/action.sh#L172-L176

@dhimmel sorry for the delay. In your error example above, that error happened during the on-the-GCE-VM shutdown hook, which we no longer use as per #34. I can see (code) that nxonto-date doesn't use explicit shutdown hook anymore 👏- so I don't think this will be an issue anymore.
The cases when jq is still used at the moment are all on the GitHub-hosted Action runner, this is the code that creates and deletes the GCE VM, and according to the GitHub documentation for ubuntu-latest, jq is preinstalled: https://github.com/actions/runner-images/blob/7704a85e7f0a0dcab94608297f5bf99266f098dd/images/linux/Ubuntu2204-Readme.md
Closing, please reopen if the error persists.


[CAMEL-8468] Usage of camel-xstream depends on TCCL

Thanks for the PR this has been merged. Do you mind closing this


Add missing display examples (MAX32672FTHR & MAX32665EvKIT)

MAX32665EvKit and MAX32672FTHR have display but there are driver and use case examples.
Added display examples for these devices, examples developed based on LVGL library.

LVGL v8.3.3 version library added inside libs folder
Added MAX32672 FTHR display (CFAL12832C)  driver & use case example
Added MAX32665 EvKIT display (LS013B7DH03)  driver & use case example
Update deice example list.

Examples:

@Jake-Carter It is ok, please feel free to merge it. Thanks.


3D Secure

Hi
Will there be any updates to the missing 3D Secure element to this in the immediate future?

Is anyone working on this?

Hi @JoSquiders - this is on the roadmap, but no capacity to make the changes at this point in time.
If you're able to make a pull request with the required changes, that would be helpful...

Hi @JustinBusschau Okay thank you, I will take a look when I get some time. I have a client requiring the 3D Secure by the end of June so I'll either have to try and do it myself or switch to a different code library or hope someone updates this one in the meantime :)


Stacks disappear when created and are uninteractable

When dragging two cards on top of one another, they instantly disappear. The DOM elements are still there in the upper left corner, but they are invisible to the user and uninteractible.

Resolved as of adf38090516be4a818ea146ce56a93f5c75b8773.


asprof hangs when attaching to service (GraalVM 17/21)

Describe the bug
Issue
When I attempt to profile our service's memory allocations in production with async profiler, it often hangs without printing any output to the console. It also causes the service to become unresponsive (to even health checks), but does not cause a crash. It's worth noting that this service has some heavy traffic in production and this issue is less likely to repro if the instance has been recently (~within an hour) restarted.
Command used:
/bin/asprof collect -e alloc -d 5s -f ./profile.txt <pid of the service>
Async profiler version:
Tried both the stable release (v3.0) and multiple nightly builds (latest being async-profiler-3.0-5ebc82d-linux-x64 from 12/11)
Expected vs. actual behavior
Expected Behavior
Async profiler should profile the service without causing it to hang
Actual Behavior
Async profiler hangs the service (as well as itself) when attempting to profile the service
Reproduction Steps
Attempt to profile memory allocations of an instance of the service that has been running in production for a while:
/bin/asprof collect -e alloc -d 5s -f ./profile.txt <pid of the service>
I also attempted with --cstack vm with the same outcome:
/bin/asprof collect -e alloc -d 5s --cstack vm -f ./profile.txt <pid of the service>
Additional Information/Context
No response
Async-profiler version
v3.0, 3.0-116504c, 3.0-3cf733d , 3.0-5ebc82d (nightly builds)
Environment details
JDK: GraalVM 21 (also repros with 17)
Application is running in a container:
Container's host OS: CentOS Stream 9

Thank you for the report. We have not seen such a behavior before, so it would be helpful if you provide additional debugging details.

Does the problem happen only with alloc profiling? Have you ever observed application hanging with -e cpu?
What does a "hang" look like? Does a JVM process consume CPU when it is unresponsive (e.g., it utilizes 100% of one CPU core)? Or is it idle?
What are GC settings? What is an allocation rate of the application? (this can be estimated from GC logs)
Have you tried to configure alloc sampling rate? Defaults may be too tough. Try --alloc 10m

Thank you for the quick reply.

Does the problem happen only with alloc profiling? Have you ever observed application hanging with -e cpu?

I confirmed it repros with -e cpu as well

What does a "hang" look like? Does a JVM process consume CPU when it is unresponsive (e.g., it utilizes 100% of one CPU core)? Or is it idle?

CPU utilization by the service process drops to ~0% when I started the profiler.

What are GC settings? What is an allocation rate of the application? (this can be estimated from GC logs)

GC Settings: -XX:+UseG1GC -XX:ParallelGCThreads=28 -XX:ConcGCThreads=9
Allocation rate is roughly 2.2 GBPS (with spikes of ~3.5 GBPS).

Have you tried to configure alloc sampling rate? Defaults may be too tough. Try --alloc 10m

Still managed to repro the problem with --alloc 10m (and even with --alloc 100m).

Thank you for the update. This must be some sort of a deadlock. When it hangs next time, can you please dump native stacks of the process? There are several ways to do that:

gstack PID (called pstack on some distributions).
jhsdb jstack --mixed --pid PID