AGRC Geocoding Toolbox

Issue description
I used to be able to use the geocoding toolbox without any issues. Several months ago I started having problems where it would code part of a table and then give up. I could work around it by breaking the table into smaller ones after the point where it would hit an error (I wasn't doing a ton of locations, ~400 in the original table). Now it fails without accomplishing anything. I don't know if I'm doing something wrong on my end, and I don't know enough Python to be able to effectively troubleshoot this myself.
Here is the table I'm currently working with (125 locations):
Naloxone finished with zip code sheet.xlsx
Expected result
I expected: "Yay! Here are the locations! Now you can display them in a map!"
Actual result
Instead:
Executing: GeocodeTable AGRC-61FFB138304379 Sheet1$ OBJ_ID StreetAddress Zip "Address points and road centerlines (default)" "NAD 1983 UTM Zone 12N" C:\Users\ebrutsch\Desktop\Geocoding
Start Time: Thu Jun 16 09:39:35 2016
Running script GeocodeTable...
Geocode Table Version 2.1.7
Api key is valid.
Begin Geocode.
Failed script GeocodeTable...
Traceback (most recent call last):
File "c:\program files (x86)\arcgis\desktop10.3\ArcToolbox\Toolboxes\AGRC Geocode Tools.tbx#GeocodeTable.py", line 330, in
File "c:\program files (x86)\arcgis\desktop10.3\ArcToolbox\Toolboxes\AGRC Geocode Tools.tbx#GeocodeTable.py", line 304, in start
File "c:\program files (x86)\arcgis\desktop10.3\ArcToolbox\Toolboxes\AGRC Geocode Tools.tbx#GeocodeTable.py", line 67, in locateAddresses
UnboundLocalError: local variable 'r' referenced before assignment
Failed to execute (GeocodeTable).
Failed at Thu Jun 16 09:39:58 2016 (Elapsed Time: 23.16 seconds)

I am moving this to here. @keatonwalker should be able to help you through this. I did notice there is a 2.1.9 version and you are on 2.1.7. I would try upgrading and see if the problem continues. Let's continue this issue in the correct repo. Thank you for submitting it.


Components in the template are not recognized with JSX code

git: https://github.com/joker77877/vue-vite-volar

I don't think this is specific to TSX/JSX, I observe the same in my project (plain TS).
I assumed this was because local components in non-script setup style were unsupported?

I don't think this is specific to TSX/JSX, I observe the same in my project (plain TS).
I assumed this was because local components in non-script setup style were unsupported?

You may need to config "editor.semanticHighlighting.enabled": true in vscode.

Please release the latest version as soon as possible, thank you.

@joker77877 I'm still fixing #94 for next version, will check a patch release if possible.
You can also run volar master branch as debug mode for now.
https://github.com/johnsoncodehk/volar/blob/master/.github/STEP_TO_PROFILING.md#run-volar-on-debug-mode


[WIP] Add support for public enums with newtype variants

My strategy was to straight copy the @enum= matches and translate to @enum_newtype=, removing the variadics for the fields.

working on a better way to enable newtypes.

working on a better way to enable newtype variants


List gtest as an external dependency for the Kokoro Windows build

Ref: #1861

This change is

@coryan I e-mailed your users.noreply.github.com address from the commit log. Did you want me to use a different e-mail address? Either way, my e-mail is just my username [at] gmail.com.

I think you should have to the Kokoro logs now, in any case:
[137/588] Linking CXX executable google\cloud\future_void_test.exe
FAILED: google/cloud/future_void_test.exe
cmd.exe /C "cd . && C:\ProgramData\chocolatey\lib\cmake.portable\tools\cmake-3.13.3-win64-x64\bin\cmake.exe -E vs_link_exe --intdir=google\cloud\CMakeFiles\future_void_test.dir --manifests  -- C:\PROGRA~2\MIB055~1\2017\COMMUN~1\VC\Tools\MSVC\1414~1.264\bin\Hostx64\x64\link.exe /nologo google\cloud\CMakeFiles\future_void_test.dir\future_void_test.cc.obj  /out:google\cloud\future_void_test.exe /implib:google\cloud\future_void_test.lib /pdb:google\cloud\future_void_test.pdb /version:0.0  /machine:x64 /debug /INCREMENTAL /subsystem:console  google\cloud\google_cloud_cpp_testing.lib google\cloud\google_cloud_cpp_common.lib external\lib\gmockd.lib external\lib\gtestd.lib external\lib\gmock_maind.lib kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib && cmd.exe /C "cd /D T:\src\github\google-cloud-cpp\build-output\google\cloud && powershell -noprofile -executionpolicy Bypass -file T:/src/github/vcpkg/scripts/buildsystems/msbuild/applocal.ps1 -targetBinary T:/src/github/google-cloud-cpp/build-output/google/cloud/future_void_test.exe -installedDir T:/src/github/vcpkg/installed/x64-windows-static/debug/bin -OutVariable out""
LINK Pass 1: command "C:\PROGRA~2\MIB055~1\2017\COMMUN~1\VC\Tools\MSVC\1414~1.264\bin\Hostx64\x64\link.exe /nologo google\cloud\CMakeFiles\future_void_test.dir\future_void_test.cc.obj /out:google\cloud\future_void_test.exe /implib:google\cloud\future_void_test.lib /pdb:google\cloud\future_void_test.pdb /version:0.0 /machine:x64 /debug /INCREMENTAL /subsystem:console google\cloud\google_cloud_cpp_testing.lib google\cloud\google_cloud_cpp_common.lib external\lib\gmockd.lib external\lib\gtestd.lib external\lib\gmock_maind.lib kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib /MANIFEST /MANIFESTFILE:google\cloud\CMakeFiles\future_void_test.dir/intermediate.manifest google\cloud\CMakeFiles\future_void_test.dir/manifest.res" failed (exit code 1104) with the following output:
LINK : fatal error LNK1104: cannot open file 'external\lib\gmockd.lib'
[138/588] Linking CXX executable google\cloud\iam_bindings_test.exe
FAILED: google/cloud/iam_bindings_test.exe
cmd.exe /C "cd . && C:\ProgramData\chocolatey\lib\cmake.portable\tools\cmake-3.13.3-win64-x64\bin\cmake.exe -E vs_link_exe --intdir=google\cloud\CMakeFiles\iam_bindings_test.dir --manifests  -- C:\PROGRA~2\MIB055~1\2017\COMMUN~1\VC\Tools\MSVC\1414~1.264\bin\Hostx64\x64\link.exe /nologo google\cloud\CMakeFiles\iam_bindings_test.dir\iam_bindings_test.cc.obj  /out:google\cloud\iam_bindings_test.exe /implib:google\cloud\iam_bindings_test.lib /pdb:google\cloud\iam_bindings_test.pdb /version:0.0  /machine:x64 /debug /INCREMENTAL /subsystem:console  google\cloud\google_cloud_cpp_testing.lib google\cloud\google_cloud_cpp_common.lib external\lib\gmockd.lib external\lib\gtestd.lib external\lib\gmock_maind.lib kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib && cmd.exe /C "cd /D T:\src\github\google-cloud-cpp\build-output\google\cloud && powershell -noprofile -executionpolicy Bypass -file T:/src/github/vcpkg/scripts/buildsystems/msbuild/applocal.ps1 -targetBinary T:/src/github/google-cloud-cpp/build-output/google/cloud/iam_bindings_test.exe -installedDir T:/src/github/vcpkg/installed/x64-windows-static/debug/bin -OutVariable out""
LINK Pass 1: command "C:\PROGRA~2\MIB055~1\2017\COMMUN~1\VC\Tools\MSVC\1414~1.264\bin\Hostx64\x64\link.exe /nologo google\cloud\CMakeFiles\iam_bindings_test.dir\iam_bindings_test.cc.obj /out:google\cloud\iam_bindings_test.exe /implib:google\cloud\iam_bindings_test.lib /pdb:google\cloud\iam_bindings_test.pdb /version:0.0 /machine:x64 /debug /INCREMENTAL /subsystem:console google\cloud\google_cloud_cpp_testing.lib google\cloud\google_cloud_cpp_common.lib external\lib\gmockd.lib external\lib\gtestd.lib external\lib\gmock_maind.lib kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib /MANIFEST /MANIFESTFILE:google\cloud\CMakeFiles\iam_bindings_test.dir/intermediate.manifest google\cloud\CMakeFiles\iam_bindings_test.dir/manifest.res" failed (exit code 1104) with the following output:
LINK : fatal error LNK1104: cannot open file 'external\lib\gmockd.lib'

Alright so I think there's a deeper issue here. I saw:
-- Configuring GTest::gtest with T:/src/github/google-cloud-cpp/build-output/external/lib/gtest$<$<CONFIG:DEBUG>:d>.lib
-- Configuring GTest::gtest_main with T:/src/github/google-cloud-cpp/build-output/external/lib/gtest_main$<$<CONFIG:DEBUG>:d>.lib
-- Configuring GTest::gmock with T:/src/github/google-cloud-cpp/build-output/external/lib/gmock$<$<CONFIG:DEBUG>:d>.lib
-- Configuring GTest::gmock_main with T:/src/github/google-cloud-cpp/build-output/external/lib/gmock_main$<$<CONFIG:DEBUG>:d>.lib

and the log and assumed that the issue was it not being able to find gmockd because generator expressions are not evaluated at configure time. The fix results in:
-- Configuring GTest::gtest with T:/src/github/google-cloud-cpp/build-output/external/lib/gtestd.lib
-- Configuring GTest::gtest_main with T:/src/github/google-cloud-cpp/build-output/external/lib/gtest_maind.lib
-- Configuring GTest::gmock with T:/src/github/google-cloud-cpp/build-output/external/lib/gmockd.lib
-- Configuring GTest::gmock_main with T:/src/github/google-cloud-cpp/build-output/external/lib/gmock_maind.lib

But it still complains about not being able to find gmockd.

FWIW, I reached out to the gtest folks inside google to see if we can cut a release and upgrade vcpkg to that new release.  That would be the easiest fix.  Let's see what they say.
Alternatively, it seems cmake/external/googletest.cmake is forcing a Release build for the googletest dependency:
https://github.com/googleapis/google-cloud-cpp/blob/bd20db4f2369b8927de862af9245e47109c69b0a/cmake/external/googletest.cmake#L51
But then we try to load the libraries with *d.lib.

For now, the gtest release will allow this PR to be merged. However, I still think the other issues are worth fixing for a separate PR:

Debug mode is failing because the linux build looks for external/lib/libgmock.a even though libgmockd.a is created
For Windows, you allegedly need to add --config to the CMake invocation because CMAKE_BUILD_TYPE is ignored
CMAKE_CONFIGURATION_TYPES may come into play, but I'm not sure how it helps

I'll revert the other changes for now.


SS 3.2.1 - image elements do not render

Hi @wilr
Environment

SilverStripe + CMS: 3.2.1
This repository: dev-master (483d1ed107cff3f3cb12ce936534179bfa610823)

Problem
Image Elements do not render to the page.
Example
I have three elements:

ElementLink
ElementContent
ElementImage

I upload an image and do not set any of the fields other than the title. I've given it a custom CSS class to show that the Element association is working.
Upon previewing, the image tag is rendered empty:

I suppose that the div element comes from ElementHolder.ss which is working correctly, but the data is not available for some reason in the ElementImage.ss template, hence there being blank values rendered (the figure class is another example, it should have the extra class in it).
When I check the image under "Files" it has a URL and Title set as I expect it should, which means that the template rendering should work, no?

The ElementLink and ElementContent both render correctly.
Thanks,
Robbie

Beautiful. Thanks @wilr


Conflict between cuda version and gcc version

In "conda_cu113.yml", you installed cuda11.3 and gcc11.2, but in fact, they are conflicting.
When I install "pyg_lib torch_scatter torch_sparse torch_cluster torch_spline_conv", the error occur:
RuntimeError: The current installed version of /home/username/anaconda3/envs/icg_cuda113/bin/x86_64-conda-linux-gnu-c++ (11.2.0) is greater than the maximum required version by CUDA 11.3 (10.0.0). Please make sure to use an adequate version of /home/username/anaconda3/envs/icg_cuda113/bin/x86_64-conda-linux-gnu-c++ (>=5.0.0, <=10.0.0).
Here is the version correspondence table of cuda and gcc

In fact, conda_cu121.yml also cannot successfully create the desired conda environment. This is because cudatoolkit=12.1 is not yet supported in conda.

In fact, conda_cu121.yml also cannot successfully create the desired conda environment. This is because cudatoolkit=12.1 is not yet supported in conda.

I just updated the conda_cu121.yml with my working local version. Could you check if the installation for this environment works for you?


LauncherIconSwitcherPlugin error

I applied this package to my project.
However, there was an error and the error was in the file "GenerationPluginRegistrant.java", "flutterEngine.getPlugins().add(new com.example.launcher_icon_switcher.LauncherIconSwitcherPlugin())")". I don't know which one is the problem.

Hello, @jnlian !
Unfortunately, I can't reproduce your error. Could you try to run flutter clean and see if the problem remains ?
If it does, could you also provide a flutter doctor -v output ?


add support for build csi volume source

https://issues.redhat.com/browse/BUILD-275

flaking openshift-e2e-aws-builds-techpreview
/test openshift-e2e-aws-builds-techpreview

flaking e2e-gcp-builds
/test e2e-gcp-builds

/assign @adambkaplan
/assign @coreydaley

You should put BUILD-275:  in the beginning of your PR title. I know you reference it in the PR description, but having it in the title will help us when we have to search PRs in the future.
I do have a question for @adambkaplan in looking at the BUILD-275 acceptance criteria.
It mentions making sure that TechPreviewNoUpgrade feature gate is enabled.
However, the csiVolumesEnabled parameter to setupBuildVolumes is currently on based on only the BuildCSIVolumes feature gate.
See
https://github.com/openshift/openshift-controller-manager/blob/ebe986727319c6c7741cc841bff7fd4f7801c7ca/pkg/cmd/controller/build.go#L54-L63
@adambkaplan - should that code be changed to check both feature gates? I don't think that BuildCSIVolumes is automatically set to true if tech preview is on, but maybe I am "misremembering" .... and I don't recall exactly where you wired all that feature gate stuff up.

@adambkaplan assisted this old man's memory yesterday (including reminding me of the fact that I actually did some of this stuff, albeit more or less following his instructions ;-) ), and confirmed that only checking for BuildCSIVolumes is sufficient for our means.  It s a feature set vs. feature gate distinction, where we can't have BuildCSIVolumes on unless tech preview is on.
So all good on this point.

/hold
Need https://github.com/openshift/api/pull/1056 to merge, as well as an update to openshift/apiserver.

/retest

/test verify


Fix Hive table comment should be after table column definitions

For the documentation, please refer to:
https://cwiki.apache.org/confluence/display/Hive/LanguageManual+DDL#LanguageManualDDL-CreateTable
This closes #1395

cc @iffyio

Pull Request Test Coverage Report for Build<PHONE_NUMBER>1
Details

31 of 35 (88.57%)  changed or added relevant lines in 4 files are covered.
14 unchanged lines in 3 files lost coverage.
Overall coverage decreased (-0.01%) to 89.241%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/ast/dml.rs
2
3
66.67%

src/parser/mod.rs
15
18
83.33%

Files with Coverage Reduction
New Missed Lines
%

tests/sqlparser_common.rs
1
89.63%

src/ast/value.rs
1
86.96%

src/lib.rs
12
12.47%

Totals

Change from base Build<PHONE_NUMBER>8:
-0.01%

Covered Lines:
28831

Relevant Lines:
32307

💛  - Coveralls


fix(metrics): 2 "Global labels" examples should be enough

Right now the full diff is super distracting and does not add much.

I would recommend keeping the top-level properties, i.e., counters, gauges & histograms in the example snippet.


CLI for Directions API

This attempts to address part of #120.  Thank you!

@critical-path Thanks for the contribution once again! 🙇 This looks great - there are a few unrelated test failures that we'll handle on our end. I'll merge your PR into directions-v5 branch and make the necessary changes.


[PE-D][Tester A] Timetable is not reflected in the record

add n/jake s/A1111112D<EMAIL_ADDRESS>h/@jakeTele c/mon: 8-10
When the above command is entered, the timetable is not inserted inside the record. Based on the below picture, the timetable for Monday is shown as "no periods".

Labels: severity.High type.FunctionalityBug
original: AndrewOng2066/ped#1

Duplicate of #137


dict[str, list[OmeroChannel]] data not displayed correctly

Collect fractal-tasks-core 0.10.0a6
Create a workflow, and add task Create OME-ZARR structure (multiplexing)
Fill the allowed_channels required arguments until "save" works. This will require adding a key-value pair, and in the value there should be an item, and in the item one should set wavelength_id="aaa" and one should set window["start"]=0 and window["end"]=1
Save -> fractal-web shows no error
EXPECTED BEHAVIOR: I should see the new element in allowed channels. ACTUAL BEHAVIOR: there is nothing displayed.

Note that the DB has the right data, as is clear e.g. by exporting the worfklow:
      "args": {
        "image_extension": "tif",
        "num_levels": 5,
        "coarsening_xy": 2,
        "allowed_channels": {
          "asd": [
            {
              "wavelength_id": "asd",
              "window": {
                "start": 0,
                "end": 1
              },
              "active": true,
              "coefficient": 1,
              "inverted": false
            }
          ],
          "new": [
            {
              "wavelength_id": "asd",
              "window": {
                "start": 1,
                "end": 1
              },
              "active": true,
              "coefficient": 1,
              "inverted": false
            }
          ]
        }

Fixed with 57d0664, and I confirm that the behavior is as expected.


Deserialize nullable objects invalid

Comparing to the old JSON.Parse... JsonConvert.Deserialize loses nullable values on deserialization. It only works if you specify object literal
https://deck.net/63674400362dccdce1adef54826e830a
Also JsonConvert.DeserializeObject<Test>(testJson, new JsonSerializerSettings { NullValueHandling = NullValueHandling.Include }); does not work which I would of expected that to be the fix

And a stab in the dark your fix might need to start here
https://github.com/bridgedotnet/Bridge.Newtonsoft.Json/blob/796f965d6b65dd26889dc44c801cb096821f4e97/Newtonsoft.Json/Resources/Manual/JsonConvert.js#L344

Ok I've found a fix... well workaround in my eyes.
Deserialize to an object then use As...
var test = JsonConvert.DeserializeObject<System.Object>(testJson).As();

Final update.
Add this to AssemblyInfo.cs
[assembly: Convention(Target = ConventionTarget.Member, Notation = Notation.LowerCamelCase)]
Now this will work:
var test = JsonConvert.DeserializeObject<System.Object>(json).As();
So basically this code will work if you add the line to your AssemblyInfo.cs file
https://deck.net/b49755d09b242e16102ce5bfba2bd5f4
I would however expect a fix so that a DeserializeObject works without needing to do DeserializeObject().As()...?

Thanks for the report. I haven't had a chance to investigate exactly what's going wrong here, but just a few days ago there was a fix merged that included case-insensitive matching during deserialization. See Issue #14 (pull request)
The fix was merged into the master branch and will be included in the upcoming 16.0.0-rc release. Maybe that fix will help with this scenario; at least it might mitigate the use of [assembly: Convention] attribute.

Thanks I'll pull that once its released and confirm if it worked

Just a heads up that my fix (DeserializeObject().As()... then causes List deserialization to break.. now lists deserialize to arrays and so .Count doesn't work as it wants .length.
The work around to that is a load of ((dynamic)a).length calls but thats then getting into the realms of a lot of workarounds all through code.
Has the fix confirmed if it fixes this issue and any due date on this release?


Release 4.1V WiFi error on heap_caps_malloc MALLOC_CAP_SPIRAM (IDFGH-4193)

Now the 4.1 release has a new bug, while using memory on SPIRAM, and delete a task, and recreate task it start to have problems.
If just use internal memory there is no problem, but once use SPIRAM memory the problem start to happen.
W (44750) wifi:tx null, bss is null
W (44920) wifi:tx null, bss is null
W (45150) wifi:add mismatch
so, this error just draw if the PSIRAM is used, so, a FIX for the 4.1 sdk is urgently needed.
MALLOC_CAP_8BIT:
Heap summary for capabilities 0x00000004:
At 0x3ffb2730 len 15448 free 0 allocated 15080 min_free 0
largest_free_block 0 alloc_blocks 20 free_blocks 1 total_blocks 21
At 0x3ffca5ec len 32767 free 200 allocated 32212 min_free 12
largest_free_block 200 alloc_blocks 19 free_blocks 1 total_blocks 20
At 0x3f804ad4 len 4175147 free 3630180 allocated 543564 min_free 3622888
largest_free_block 3629584 alloc_blocks 82 free_blocks 11 total_blocks 93
At 0x3ffaff10 len 240 free 0 allocated 96 min_free 0
largest_free_block 0 alloc_blocks 7 free_blocks 0 total_blocks 7
At 0x3ffb6388 len 7288 free 0 allocated 6988 min_free 0
largest_free_block 0 alloc_blocks 16 free_blocks 1 total_blocks 17
At 0x3ffb9a20 len 16648 free 4 allocated 15116 min_free 0
largest_free_block 0 alloc_blocks 92 free_blocks 3 total_blocks 95
At 0x3ffca5c8 len 88632 free 0 allocated 86952 min_free 0
largest_free_block 0 alloc_blocks 103 free_blocks 0 total_blocks 103
At 0x3ffe0440 len 15072 free 16 allocated 12904 min_free 0
largest_free_block 4 alloc_blocks 131 free_blocks 3 total_blocks 134
At 0x3ffe4350 len 113840 free 23508 allocated 89104 min_free 20192
largest_free_block 23348 alloc_blocks 73 free_blocks 4 total_blocks 77
Totals:
free 3653908 allocated 802016 min_free 3643092 largest_free_block 3629584
MALLOC_CAP_32BIT:
Heap summary for capabilities 0x00000002:
At 0x3ffb2730 len 15448 free 0 allocated 15080 min_free 0
largest_free_block 0 alloc_blocks 20 free_blocks 1 total_blocks 21
At 0x3ffca5ec len 32767 free 200 allocated 32212 min_free 12
largest_free_block 200 alloc_blocks 19 free_blocks 1 total_blocks 20
At 0x3f804ad4 len 4175147 free 3630180 allocated 543564 min_free 3622888
largest_free_block 3629584 alloc_blocks 82 free_blocks 11 total_blocks 93
At 0x3ffaff10 len 240 free 0 allocated 96 min_free 0
largest_free_block 0 alloc_blocks 7 free_blocks 0 total_blocks 7
At 0x3ffb6388 len 7288 free 0 allocated 6988 min_free 0
largest_free_block 0 alloc_blocks 16 free_blocks 1 total_blocks 17
At 0x3ffb9a20 len 16648 free 4 allocated 15116 min_free 0
largest_free_block 0 alloc_blocks 92 free_blocks 3 total_blocks 95
At 0x3ffca5c8 len 88632 free 0 allocated 86952 min_free 0
largest_free_block 0 alloc_blocks 103 free_blocks 0 total_blocks 103
At 0x3ffe0440 len 15072 free 16 allocated 12904 min_free 0
largest_free_block 4 alloc_blocks 131 free_blocks 3 total_blocks 134
At 0x3ffe4350 len 113840 free 23508 allocated 89104 min_free 20192
largest_free_block 23348 alloc_blocks 73 free_blocks 4 total_blocks 77
At 0x4009d100 len 12032 free 11984 allocated 0 min_free 11964
largest_free_block 11984 alloc_blocks 0 free_blocks 1 total_blocks 1
Totals:
free 3665892 allocated 802016 min_free 3655056 largest_free_block 3629584
MALLOC_CAP_INTERNAL:
Heap summary for capabilities 0x00000800:
At 0x3ffb2730 len 15448 free 0 allocated 15080 min_free 0
largest_free_block 0 alloc_blocks 20 free_blocks 1 total_blocks 21
At 0x3ffca5ec len 32767 free 200 allocated 32212 min_free 12
largest_free_block 200 alloc_blocks 19 free_blocks 1 total_blocks 20
At 0x3ffaff10 len 240 free 0 allocated 96 min_free 0
largest_free_block 0 alloc_blocks 7 free_blocks 0 total_blocks 7
At 0x3ffb6388 len 7288 free 0 allocated 6988 min_free 0
largest_free_block 0 alloc_blocks 16 free_blocks 1 total_blocks 17
At 0x3ffb9a20 len 16648 free 4 allocated 15116 min_free 0
largest_free_block 0 alloc_blocks 92 free_blocks 3 total_blocks 95
At 0x3ffca5c8 len 88632 free 0 allocated 86952 min_free 0
largest_free_block 0 alloc_blocks 103 free_blocks 0 total_blocks 103
At 0x3ffe0440 len 15072 free 16 allocated 12904 min_free 0
largest_free_block 4 alloc_blocks 131 free_blocks 3 total_blocks 134
At 0x3ffe4350 len 113840 free 23508 allocated 89104 min_free 20192
largest_free_block 23348 alloc_blocks 73 free_blocks 4 total_blocks 77
At 0x4009d100 len 12032 free 11984 allocated 0 min_free 11964
largest_free_block 11984 alloc_blocks 0 free_blocks 1 total_blocks 1
Totals:
free 35712 allocated 258452 min_free 32168 largest_free_block 23348
MALLOC_CAP_8BIT|MALLOC_CAP_INTERNAL:
Heap summary for capabilities 0x00000804:
At 0x3ffb2730 len 15448 free 0 allocated 15080 min_free 0
largest_free_block 0 alloc_blocks 20 free_blocks 1 total_blocks 21
At 0x3ffca5ec len 32767 free 200 allocated 32212 min_free 12
largest_free_block 200 alloc_blocks 19 free_blocks 1 total_blocks 20
At 0x3ffaff10 len 240 free 0 allocated 96 min_free 0
largest_free_block 0 alloc_blocks 7 free_blocks 0 total_blocks 7
At 0x3ffb6388 len 7288 free 0 allocated 6988 min_free 0
largest_free_block 0 alloc_blocks 16 free_blocks 1 total_blocks 17
At 0x3ffb9a20 len 16648 free 4 allocated 15116 min_free 0
largest_free_block 0 alloc_blocks 92 free_blocks 3 total_blocks 95
At 0x3ffca5c8 len 88632 free 0 allocated 86952 min_free 0
largest_free_block 0 alloc_blocks 103 free_blocks 0 total_blocks 103
At 0x3ffe0440 len 15072 free 16 allocated 12904 min_free 0
largest_free_block 4 alloc_blocks 131 free_blocks 3 total_blocks 134
At 0x3ffe4350 len 113840 free 23508 allocated 89104 min_free 20192
largest_free_block 23348 alloc_blocks 73 free_blocks 4 total_blocks 77
Totals:
free 23728 allocated 258452 min_free 20204 largest_free_block 23348

Thanks for reporting.

Hi @filzek, I didn't reproduce by creating and deleting task in psram, seems like it happened in some specific scenario,
could you show me your commit ID and provide a code to reproduce this issue? Thanks.

@YouDONG-ESP PTAL

@filzek Thanks for reporting, will close due to short of feedback, feel free to reopen with more details/updates, thanks.


Add note in last modified time recipe

Description (required)
add a note about git history in the modified time recipe. Related discussion is here #8779
Related issues & labels (optional)

Closes #8779

Lunaria Status Overview
🌕 This pull request will trigger status changes.

Learn more
By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.
You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

Locale
File
Note

en
recipes/modified-time.mdx
Source changed, localizations will be marked as outdated.

Warnings reference

Icon
Description

🔄
The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.

Amazing, thank you for picking up this issue, @apatel369 !
I read back through the issue and thought that Fryuni's comment had a bit more helpful information so I just edited it a tiny bit, but this is exactly what we needed and super helpful. Thank you! 💪

@sarah11918  Ya, I directly copied from your response. Thanks. !coauthor.
Also, I am seeing hackorfest-accepted tag but FYI I didn't submit it for hacktoberfest.


Teach Find command to search selected text

PR Checklist

[x] Closes https://github.com/microsoft/terminal/issues/8307
[x] CLA signed.
[ ] Tests added/passed
[ ] Documentation updated - not yet
[x] Schema updated
[x] I've discussed this with core contributors already.

Detailed Description of the Pull Request / Additional comments
Add selectionMode field to the find command.

If no mode is specified (backward-compatibility) or none is provided - behave as before.
If selectionMode is set to singleLine and a single line of text is selected,
use it to populate the search box.
If selectionMode is set to multiLine concatenate all lines with line-breaks omitted,
and use the resulting string to populate the search box.

The population logic will be applied whenever the search box control gets loaded /
reset by the consequent find command.
If the population logic should be applied while the search box is already populated,
an old value will be overridden.
Validation Steps Performed

Manual tests

Do we need to add this to settings? Some people may not like the idea of arbitrarily populating the selected text.

Do we need to add this to settings? Some people may not like the idea of arbitrarily populating the selected text.

@skyline75489 - this is a good question :blush:
Probably, I could add it as a parameter to the Find operation.
Something like
{ "command" : { "action": "find", "populateFromSelectionMode": "None"}

Where populateFromSelectionMode is one of:

None - do not populate
SingleLineSelected - populate when single line selected
MultilineSelectedUseFirstLine - use the first line if more than one line selected
MultilineSelectedUseAll - use the entire text for search

WDYT?

Honestly I'm good as long as the default behaviour remains the same. Remember the MRU tab switching thing? That just backfired in like no time. So considering this is also a breaking change, we should learned from the tab switching lesson.

Something like
{ "command" : { "action": "find", "populateFromSelectionMode": "None"}}

Where populateFromSelectionMode is one of:

None - do not populate
SingleLineSelected - populate when single line selected
MultilineSelectedUseFirstLine - use the first line if more than one line selected
MultilineSelectedUseAll - use the entire text for search

Great work! I like the design for this setting with just a few nits:

don't forget to make the enums camel case
Does any text application do multilineSelectedUseFirstLine? I feel like that's an odd case, but if someone else uses it, go for it.
I wonder if we could make the names smaller? Maybe fillSearchBox, singleLine, multiLine (if we remove the other case)? Summoning @cinnamon-msft for some thoughts on this.

@carlos-zamora - I added selectionMode to the find command with values none (default), singleLine, multiLine. Please review.

This is something I would actually consider making default. VS Code does this by default and we tend to follow in their footsteps for a lot of our features. I'm curious how the team feels about this.
For the setting, I'm wondering if this should just be a boolean instead: to either populate with a selection or not.

This is something I would actually consider making default. VS Code does this by default and we tend to follow in their footsteps for a lot of our features. I'm curious how the team feels about this.
For the setting, I'm wondering if this should just be a boolean instead: to either populate with a selection or not.

I'm down for just making it a bool (true --> multiLine, false --> none). Also down to make true the default because chromium edge and VSCode have it enabled by default.

What if we don’t make it a setting at all? Let the users complain if they hate it

Do it by default and only

@DHowett - in general I like your approach: let's put it in the preview and see if anyone complains.
The question is wether it usually works? I am not experienced enough, my only input is that it didn't work for MRU. But probably then it was an issue with the timing. I am not sure if this one goes to 1.5 or 1.6, but probably we should put it optional in 1.5 and default in 1.6 preview? Won't it allow us to get as much inputs as possible? Then we can cleanup the code.
I guess the main cost for this approach is translating the resources :smile:
So probably, let's use a single useSelection flag, set to false in 1.5 and to true in 1.6 preview?
Unrelated to above, should we allow only single line selection (aka VS Code) or allow multiple lines by concating them (aka notepad++)?

This is something I would actually consider making default. VS Code does this by default and we tend to follow in their footsteps for a lot of our features. I'm curious how the team feels about this.
For the setting, I'm wondering if this should just be a boolean instead: to either populate with a selection or not.

I'm down for just making it a bool (true --> multiLine, false --> none). Also down to make true the default because chromium edge and VSCode have it enabled by default.

@carlos-zamora - hmm from what I played right now:

Edge Chromium, VS, FoxitReader - does not use selection.
Firefox, Chrome, Word - do multi-line but cuts at some stage
VSCode works only with single line.
Notepad++ works with multiline
Outlook - no one knows how to search there

Created an alternative PR here: https://github.com/microsoft/terminal/pull/8521.
Simply rollbacked the configuration commit.

I'm obviously biased towards whatever Sublime does, and they will pre-populate the search box with the selection, so I think that'd be cool 😎
@skyline75489 I definitely appreciate you thinking about this changing a default behavior. We were burned super hard about this, and we've had no shortage of discussion of "DONT CHANGE THE DEFAULTS" in the past month. I guess I can imagine a user wanting this to be disabled. That being said, it's a lot less breaking than in-order/mru tab switching IMO. For tab switching, there was no good remedy without changing the settings. You couldn't get an in-order-like behavior in MRU without changing the settings. For this one, you can still get the old behavior by pressing Bkspc.
I think IF someone comes along saying "but muh cheese moved", then we have a plan for how we would make this configurable.
(We do have a team sync planned for later today, so we'll be discussing this one)

On another topic, we've maybe revealed a bit of a shortcoming with the Terminal's search functionality here. We don't support multi-line searching at all. We probably should! But I don't think we should really start worrying about this in this PR. Let's just make the behavior here the same as "select some text, copy it, open the find box, paste the text". We can loop back around on multiline in the future.

Mike's rationale matches mine for making it non-configurable. This doesn't need to be a knob that users can turn; I expect that if we did make it a knob we would only ever see users use two things: "turn it off" and "do the freakin' sane thing" (which is "it acts just like copy/paste of the selection would").
We are possibly the most configurable terminal that exists (I kid, but maybe?). That doesn't mean that we need to make literally everything an option.
Down that road lies madness. Down that road lies "I want the letter A to render differently on Tuesdays; perhaps you should have a tuesdayAAppearance config field?". Down that road lies "we have a search box, but users want to reclaim the 16 pixels taken up by the Case Sensitive button so why not let them hide it?" and the 60,000 individual UI feature toggles that come out of that. It's mad. Mad!

Mike's rationale matches mine for making it non-configurable. This doesn't need to be a knob that users can turn; I expect that if we did make it a knob we would only ever see users use two things: "turn it off" and "do the freakin' sane thing" (which is "it acts just like copy/paste of the selection would").
We are possibly the most configurable terminal that exists (I kid, but maybe?). That doesn't mean that we need to make literally everything an option.
Down that road lies madness. Down that road lies "I want the letter A to render differently on Tuesdays; perhaps you should have a tuesdayAAppearance config field?". Down that road lies "we have a search box, but users want to reclaim the 16 pixels taken up by the Case Sensitive button so why not let them hide it?" and the 60,000 individual UI feature toggles that come out of that. It's mad. Mad!

@DHowett - what's wrong with madness? Sanity is overrated after all :smile:
I see your point, and cannot argue (I worked on either drivers or cloud backend, so hardly know how it works with humans).
Then please review: https://github.com/microsoft/terminal/pull/8521

From our team meeting today: Team fully agrees that this should not be configurable. Redirect all to #8510 :smile:

Erm, #8521


Google plugin should limit authorized users by google apps domain

Hello!
It would be nice to be able to limit by email domain which users are authorized to access GoCD when they authenticate with google.
e.g. if my company has the google apps domain foo.com, it would be nice to be able to limit access to GoCD only to google users who log in from that domain.
I'm happy to try this. I was thinking: allow oauth providers have

a method to return extra fields they want to ask for on the configuration screen
a post-oauth-authentication hook that says "should this user have access to GoCD"

I suggest create field in plugin settings say userMatchRegex & add it in UI. This could be a comma separated value.
Add a regex matcher here which will throw a runtime exception if there is a regex setup & the email doesn't match the regex.

That won't work for the github plugin. Publicly viewable emails are optional in github and you can set to whatever you want (see https://developer.github.com/v3/users/). That's why I was thinking that the email matching should only be configurable/available for the google plugin.

the regex matcher is going to be generic. so for google it will be something like *<EMAIL_ADDRESS>& for github it could be something else. keeping a generic matcher will make it easier for other providers - so if someone adds a MSN login the rest remain same.

fixed with https://github.com/srinivasupadhya/gocd-oauth-login/pull/7


Entire project is sent to each builder

Bug report

Version: 0.3.1
URL: https://vercel.com/unitof/php-root-bug/li430s3wp (see build logs)
Repository: https://github.com/unitof/vercel-examples/tree/builder-rootfiles-bug/php-root-bug

Description
It appears that all files in the now Vercel project root (where .vercel and/or now.json are kept) are being sent to the builder for each Serverless Function. It's causing my builds to fail, as my repo as a whole is well over the Lambda max of 50MB, even though each Serverless function is well below that.
My understanding is that each Serverless Function should, by default, include only its own .php file, plus any matching files explicitly specified in that function's includeFiles in now.json.
The example at the repo above is nearly identical to the vercel-examples/php example, just with a 100MB nonsense zip file added to the root directory. It fails to build because Error: The Serverless Function "api/index.php" is 127.22mb which exceeds the maximum size limit of 50mb. Learn More: https://vercel.link/serverless-function-size.

(If I'm understanding properly) I think thats intended. For example check out the Lumen example: https://github.com/juicyfx/vercel-examples/tree/master/php-lumen api/index.php just pulls in the main lumen app entry file from the root of the project.
I'm not sure, but maybe adding your zip to the ~.nowignore~ .vercelignore would work? https://vercel.com/guides/prevent-uploading-sourcepaths-with-vercelignore

It's the feature. You must use . vercelignore and ignore all files/folders you don't want to upload.

Gotcha, my mistake then. I didn't realize each function gets the context of the entire repo by default.
I don't want to .vercelignore the files in my root, as I want them to be served statically, but I'll use excludeFiles instead.
Which does lead me to a new bug, which I'll report separately: Vercel now requires includeFiles and excludeFiles to be a single glob pattern, but vercel-php still expects arrays.


Add MagicConstantCasingFixer

Implements #2570.
Please let me know if I've done anything wrong.

Fixing 5.* now

what if someone imported his own __file__ constant ?

Thanks @keradus, I will take those into consideration!

I've updated my PR with your suggestions.
In terms of importing a magic constant, I don't think it's possible (correct me if I'm wrong), see:
https://3v4l.org/uuGn4
https://3v4l.org/ndn9b

you have used wrong syntax to import a const, but indeed it's not possible to import const named like keyword https://3v4l.org/nug2Z

Oops 🤦♂

What about supporting ::class as well?

valid scenario, but then it's not a magic constant

According to PHP Manual, it is.

wow, :+1:

Foo::class are 3 tokens, you fix last one, so you fix single token as well.

Yep, but T_CLASS can also refer to when you declare a class, so I'll have to do some checks for T_DOUBLE_COLON before it

Also anyone else having trouble viewing the travis logs? They aren't loading for me

Yep, same here :/

You are not interested in T_CLASS, you are in CT::T_CLASS_CONSTANT (thanks to ClassConstantTransformer).

Dealing with T_CLASS_CONSTANT looks good :)
Please rebase, btw. the last Travis job for this PR has logs again \o/

What am I running to rebase sorry? I tried git rebase -i master and squashing everything but my first commit but I got conflicts 😢

don't worry about squashing, as long as you are the only author the squashing can be done simple at the end before it is merged

LGTM :)

please add to symfony ruleset

Thank you @ntzm.

nice, thanks so much @ntzm :D


bug in terminal vs code

Type: Bug
I found a bug when opening a terminal in Visual Studio Code on the right side there is a tab when we open a new terminal, and it is not visible and leaves a small part of the UI, this really hinders me, I have tried restarting vs code but still nothing, previously it was fine course, but recently I discovered this problem.
 Unfortunately, it's hard for us to understand what issue you're seeing. Please help us out by providing a screen recording showing exactly what isn't working as expected. While we can work with most standard formats, .gif files are preferred as they are displayed inline on GitHub. You may find https://gifcap.dev helpful as a browser-based gif recording tool.
If the issue depends on keyboard input, you can help us by enabling screencast mode for the recording (Developer: Toggle Screencast Mode in the command palette). Lastly, please attach this file via the GitHub web interface as emailed responses will strip files out from the issue.
Happy coding!

It seems to be appearing randomly sometimes: (not able to create a gif for repro though, reloading generally fixes it, not sure what's causing it but it started happening from v1.83.0)

/duplicate #192668
already fixed in insider's


Make it possible to have numbers as enum members

I think it should be possible to use numbers as enum members.
The usecase is keyboard keys.
It would be really nice if I could put all the keyboard keys in one enum so one can do if pressed? Key::W, if pressed? Key::1 etc. however currently you get this error when having numbers in enums:
Syntax error in eval:2: unexpected token: 1

I don't see any reason why it shouldn't be possible to use numbers as enum members.
Currently the only way (besides strings which would be the worst solution because they are slow) are symbols, so e.g. :"2" (unfortunately :2 doesn't work).
I would have to make a huge case for all the keys. Sure, it can be generated with macros but this whole run-time case would still be much slower compared to just using an enum.
And also as far as I know in the future symbols will (hopefully, besides the enum argument symbols) be removed. Then I would have to go an even worse way, strings.

you could have Key::Num1

Yeah as a workaround something like this (or Key::One) probably works but for the long term I would prefer not having to write so much just for one number.

I don't see any reason why it shouldn't be possible to use numbers as enum members.

Here is one: enum members are type identifiers, and type identifiers must start with an uppercase letter.

I thought it's about convieniency and not about strictly following rules like this. There's no advantage in doing that.
I would understand this when I talk about the naming of structs, classes etc. because naming them after numbers is obviously very confusing. But enum members cannot be called without having EnumName:: before it (or passing :"1" to an enum argument but that wouldn't clash with anything). So they are always encapsulated in a namespace and so there's no clash with actual integers. Enum's can't be includeded either.

However I realized that there could be a clash here because this compiles:
enum E
  A
  B
  C

  def self.hello
    puts A
  end
end

E.hello


Weekly Package Upgrade

:tada: This PR is included in version 1.3.13 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[mem_bkdr_if] change write data type back from logic to bit

When the data type is logic and the backdoor writing is only in some part of the word, so when reading the word, the read can be with X's (which will fail tests).
Signed-off-by: Eitan Shapira<EMAIL_ADDRESS>

I'm not sure this is the right solution. If I understand correctly, the tests are failing because they are seeing X's that are stored in the simulation, but were masked by the 2-state logic used in the backdoor accessor. Surely, we should be fixing the underlying problem instead?

Before any read transaction is initiated, the simulation is inserting X's to all memory before randomizing and backdoor write to only relevant addresses (In order to detect easily good read). The flash_ctrl is looking at 32 bits wide words, while the flash is actually 64 bits wide. When doing read transaction the 64 bits word is being extracted and stored in a read fifo under some of the flash_phy sub-hierarchies and while in this fifo there is an assertion to make sure all the data is valid which can cause the problem if only a part of this 64 bits word was part of this read transaction.
I hope this is clear enough.
I definitely think the read methods should be with logic data type and not bit, in order to identify X reads from the memory (I made a PR long ago to make sure it will be, and it was changed back in read8 method).
However, maybe it is not important to identify those X's while in backdoor write.

I'd much prefer to just round up the widths of the backdoor writes that the test is doing. Simpler, and an easy place to hang a comment explaining what's going on.

When thinking of it, I think the more correct approach should be to change the assertion.
The flash_ctrl can ask to read half words (32 bits) from the flash, so there is no reason in those cases to make sure all 64 bits are valid, because 32 of those bits aren't part of this transaction.
@tjaychen can you take a look at it?
The assertion is in file /hw/ip/prim/rtl/prim_fifo_sync.sv line 173
(hierarchy: tb.dut.u_flash_eflash.gen_flash_cores[1].u_core.u_rd.u_rd_storage)
`ASSERT(DataKnown_A, rvalid_o |-> !$isunknown(rdata_o))
@sha-ron

@tjaychen @sha-ron
I'm now a member of the lowrisc org, so I comment here to make sure you received it.

OK, understood. I will close this PR now. Thanks!


workaround for Mutex::Lock not being signal-safe

see: https://github.com/nodejs/node/issues/18476
/cc @mafintosh

LGTM


version variabele not updated

Hi,
The variable used as version is not updated in the next task.
Two tasks:

The patch number of SoftwelNgVersion2 var should be updated to 78:

But its not if i check it in the show all build variables output:

Any idea?
Thx

That's correct, the variable is changed but you will not see the change until you run the build or release again. This is because the variables are loaded at the beginning of the Job. if you add another Job it will work.

Indeed. Than it works.
But it seems that the variabeles are loaded when a job is queued and not when it is started. so if i queue multiple jobs thy all use the same variabele:
var is 1
queue1
queue2
run1 => it uses 1 and updates to 2
run2 => it uses 1 and updates to 3
queue3
=> it uses 3 and updates to 4
Do you see any workaround?

I haven't tested it in a scenario like that I will have to check that out


capabilitiesResolution does not work properly with an Ivy repository

Given the attached showcase.zip.
We will test using the command gradle dependencies --configuration runtimeClasspath.
There are 2 knobs to toggle, the first know is whether the ivy or the maven repository is used.
The second knob is whether the components.all<JakartaActivationCapability>() line is commented in or not.
What we have an eye on, are jakarta.activation-api and jakarta.activation.

If you run with maven repo and without the rule

both jars end up in the tree

If you run with the Ivy repo and without the rule

both jars end up in the tree

If you run with the maven repo and with the rule

the jakarta.activation jar replaces the jakarta.activation-api jar
output:
candidate jakarta.activation:jakarta.activation-api:1.2.2(runtime)
candidate com.sun.activation:jakarta.activation:1.2.2(runtime)
select com.sun.activation:jakarta.activation:1.2.2(runtime)

If you run with the Ivy repo and with the rule

the resolution of both jars fails
output:
candidate jakarta.activation:jakarta.activation-api:1.2.2(runtime)
candidate jakarta.activation:jakarta.activation-api:1.2.2(master)
candidate com.sun.activation:jakarta.activation:1.2.2(default)
select com.sun.activation:jakarta.activation:1.2.2(default)
candidate jakarta.activation:jakarta.activation-api:1.2.2(runtime)
candidate jakarta.activation:jakarta.activation-api:1.2.2(master)
candidate com.sun.activation:jakarta.activation:1.2.2(default)
select com.sun.activation:jakarta.activation:1.2.2(default)
candidate jakarta.activation:jakarta.activation-api:1.2.2(runtime)
candidate jakarta.activation:jakarta.activation-api:1.2.2(master)
candidate com.sun.activation:jakarta.activation:1.2.2(default)
select com.sun.activation:jakarta.activation:1.2.2(default)

Sorry for the late reply.
The issue is in the backlog of the relevant team and is prioritized by them.

This is still reproducible with 8.9


fix(logs): update log dependenies per Spring update

Checklist

[ ] The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
[ ] Links to related issues (if applicable)
[ ] Tests for the changes have been added/updated (if applicable)
[ ] Docs related to the changes have been added/updated (if applicable). If a new feature has been added a Usage Guide has been added for the same.
[ ] For any breaking change/potential downtime/deprecation/big changes an entry has been made in Updating DataHub

Doing some further testing here, I actually think we don't need to bump the log versions.


[Event Change Request] Codeunit 8 "AccSchedManagement"

Hello, can you please the Event OnAfterCalcCellValue set scope from local to global?
[IntegrationEvent(true, false)]
    local procedure OnAfterCalcCellValue(var AccSchedLine: Record "Acc. Schedule Line"; var ColumnLayout: Record "Column Layout"; var Result: Decimal; var SourceAccScheduleLine: Record "Acc. Schedule Line"; var GLAcc: Record "G/L Account")
    begin
    end;

No, you cannot call events directly. You must subscribe to events.


How to use the MOdel?

After training how can I use the saved model for my project? Can someone explain how to use the model to predict different entities of a given text?

I meet same problems. I read the codes and have to say,   he put the training validation tests together. bad design.

Dear wen-fei,
Unfortunately, I couldn't exactly get your mention "put the training validation tests together".
If you are mentioning "design", yes. Our code in this repository is designed only for proof of our model. Therefore we did not considered any real time use or inference-only mode.
For real time use, we made BERN, which was originally based on CollaboNet (now we use BioBERT) and publicly available online. BERN will show better performance and is much efficient over CollaboNet in most case.
If you are mentioning separation of dataset for training and test run of the model, which is related to academic integrity, we clearly divided test data from train and validation data.
For the latter one, we are open to discuss on this matter. Please leave comment here or send me email for further talk.
Thank you for your interest in our work.
Best regards,
Wonjin

Dear sub10,
My apologize for late reply. Since we were about to publish our new paper, BERN, which I mentioned above comment,

Dear wen-fei,
Unfortunately, I couldn't exactly get your mention "put the training validation tests together".
If you are mentioning "design", yes. Our code in this repository is designed only for proof of our model. Therefore we did not considered any real time use or inference-only mode.
For real time use, we made BERN, which was originally based on CollaboNet (now we use BioBERT) and publicly available online. BERN will show better performance and is much efficient over CollaboNet in most case.
If you are mentioning separation of dataset for training and test run of the model, which is related to academic integrity, we clearly divided test data from train and validation data.
For the latter one, we are open to discuss on this matter. Please leave comment here or send me email for further talk.
Thank you for your interest in our work.
Best regards,
Wonjin

In order to apply the CollaboNet to another datasets, what should I do?

Hi @393301836, it looks like your comment here is a duplicated. Please see #4


Introduce changes to elevation.json to fix bug on x-ms-skip-url-encoding

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

Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

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

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
If updating an existing version, please select the specific language SDKs and CLIs that must be refreshed after the swagger is published.

[ ] SDK of .NET (need service team to ensure code readiness)
[ ] SDK of Python
[x] SDK of Java
[ ] SDK of Js
[ ] SDK of Go
[ ] PowerShell
[ ] CLI
[ ] Terraform
[ ] No refresh required for updates in this PR

Contribution checklist:

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

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

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

Change to data plane APIs
Adding new properties
All removals

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

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

Adding a new service
Adding new API(s)
Adding a new API version
-[ ] To review changes efficiently, ensure you are using OpenAPIHub to initialize the PR for adding a new version. More details, refer to the wiki.

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

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

Breaking Change Review Checklist
If any of the following scenarios apply to the PR, request approval from the Breaking Change Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in a stable version
[ ] Removing properties in a stable version
[ ] Removing API version(s) in a stable version
[ ] Updating API in a stable or public preview version with Breaking Change Validation errors
[ ] Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

Not yet. SDK is still under development.
On Thu, May 12, 2022 at 4:08 AM Tom Kerkhove @.***>
wrote:

@.**** commented on this pull request.
In specification/maps/data-plane/DEM/preview/1.0/elevation.json
https://github.com/Azure/azure-rest-api-specs/pull/19044#discussion_r871074494
:

@@ -89,7 +89,6 @@
"required": true,
"type": "array",
"collectionFormat": "pipes",

       "x-ms-skip-url-encoding": true,

Has this been released already because this can be considered breaking
—
Reply to this email directly, view it on GitHub
https://github.com/Azure/azure-rest-api-specs/pull/19044#pullrequestreview-970429444,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABMVEKGPM2K3L65RJGFIRT3VJS36VANCNFSM5VXJQHSQ
.
You are receiving this because your review was requested.Message ID:
@.***>

adding @tjprescott to give the OK

Approved breaking change as they have not released any SDKs based on this Swagger.


some false validations

Hi,
I was playing around a bit today and noticed that some simple examples don't go through, while more complex are fine. Can you please take a look. I take the code directly from langchain, but it should be 1:1 copy of your implementation:
from langchain.chains.graph_qa.cypher_utils import CypherQueryCorrector, Schema

schema = [Schema(left_node='Movie', relation='IN_GENRE', right_node='Genre'),
 Schema(left_node='User', relation='RATED', right_node='Movie'),
 Schema(left_node='Actor', relation='ACTED_IN', right_node='Movie'),
 Schema(left_node='Actor', relation='DIRECTED', right_node='Movie'),
 Schema(left_node='Director', relation='DIRECTED', right_node='Movie'),
 Schema(left_node='Director', relation='ACTED_IN', right_node='Movie'),
 Schema(left_node='Person', relation='ACTED_IN', right_node='Movie'),
 Schema(left_node='Person', relation='DIRECTED', right_node='Movie')]

cypher_val = CypherQueryCorrector(schema)

examples = [
    "MATCH (a:Actor {name: 'Tom Hanks'})-[:ACTED_IN]->(m:Movie) RETURN count(m)",
     "MATCH (a:Actor)-[:ACTED_IN]->(:Movie)-[:IN_GENRE]->(g1:Genre), (a)-[:ACTED_IN]->(:Movie)-[:IN_GENRE]->(g2:Genre) WHERE g1.name = 'Comedy' AND g2.name = 'Action' RETURN DISTINCT a.name",
     "MATCH (a:Actor)-[:ACTED_IN]->(m:Movie) RETURN a.name, COUNT(m) AS movieCount ORDER BY movieCount DESC LIMIT 1",
     "MATCH (g:Genre)<-[:IN_GENRE]-(m:Movie) RETURN g.name, COUNT(m) AS movieCount"
]

for i in examples:
  print(cypher_val(i))

Thanks

@tomasonjo
I've fixed this and merged into main branch.

Thank you!


Add profiler to sdxl mlperf pipeline

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.


reduce allocations on get values

How do this avoid allocations? Has it been verified by a profiler?

The seq is an allocation and the first call also incur an overhead. Also this pr is part of a secret plan to get rid of all those lazy collections you are making eager by calling tolist on them.. ;)

So should I change GetValueAs to internal? Or scrap altogether?
I thought your idea was that most of the api was supposed to be public?

After taking a close look you could remove the mapping part in the timer.
And in the gauge you could remove the conversion between seq and list and you would get the same result. But only remove the converstion between seq and list for GetValues, not for GetValuesAndReset as it is important that it's being evaluated at the right time in GetValuesAndReset

We just need to be careful with code that is brittle and difficult to see you are changing in the wrong way. But I sense you don't like the GetValueAs(). In that case just close the PR


Change the email address

I do no longer have much time to support this app, I think it would be nice to display github.com/lululombard/CertRemainTime/issues and get redirected to it when you tap that link.

No problem, I'll push this in the next update.


Progress update: KSLHacks/SignalR_Chatroom

Progress update so we can sync and get the newest version of dev branch to corporate EF.  Still working on Issue #41 for Basic Chatroom working. Opening Issue #49 (Implementing IRepository InMemory)

Testing Use Case:
+Jabbr should load successfully (get past the R logo splash).
+One room should be visible and the load room should be successful. (located in browser dev tools).
+Upon clicking the room, open room should FAIL. Not implemented at this time.

Can someone test this?

Will do. There are also conflicts with dev, @KSLHacks I can look into that if you want.

:shipit:


graph validation errors for dcp1 dataset

@aaclan-ebi  please add some details

From meeting with @ESapenaVentura , we decided to bypass graph validation for now and create separate ops ticket to run validation on existing submissions. I created an epic ticket in the ops-board for that: https://github.com/ebi-ait/hca-ebi-dev-team/issues/455
Meeting notes: https://docs.google.com/document/d/1Kd-hNFqwTDOT0-ZHlbBMC0g2wXcJx1jx3JGf5e0vIWM/edit


Need more information on the extensions

File: ee/ucp/interlock/deploy/configuration-reference.md
The current documentation doesn't explain anything about the extensions. The example configuration is not good enough.

WIP: https://github.com/docker/docs-private/pull/1333


Fix resize

Coverage decreased (-0.03%) to 71.329% when pulling 4e556a00959f141bc39289e27450908054b4e8f9 on eatonphil:fix-resize into 44fd5f6013db2b8f5157668929c8d06cd6657d8a on linode:release-14.2.


500 Internal Server Error - unknown error on only some packages

Describe the bug
I get the 500 Internal Server Error - GET http://<my_registry>:4873/husky - unknown error on multiple packages like husky or jest. Other packages just work fine ...
When i open the URL, verdaccio shows:
{
  "error": "unknown error"
}

When i run npm-check-updates (on the client) the following error is shown:
{
  headers: [Object: null prototype] {
    'x-powered-by': [ 'verdaccio/4.6.2' ],
    'access-control-allow-origin': [ '*' ],
    'content-type': [ 'application/json; charset=utf-8' ],
    'content-length': [ '31' ],
    vary: [ 'Accept-Encoding' ],
    date: [ 'Mon, 18 May 2020 10:33:41 GMT' ],
    connection: [ 'keep-alive' ],
    'x-fetch-attempts': [ '1' ]
  },
  statusCode: 500,
  code: 'E500',
  method: 'GET',
  uri: 'http://<my_registry>:4873/husky',
  body: { error: 'unknown error' },
  pkgid: 'husky@latest',
  message: '500 Internal Server Error - GET http://<my_registry>:4873/husky - unknown error'
}

To Reproduce
I don't really know - i have a pretty default Verdaccio installation and the error hasn't occured when i installed it. I occurs when i try to update e.g. husky or jest some other packages seem to work just fine.
Expected behavior
Don't show the unknown error and just get the current data from the npm registry.
Configuration File (cat ~/.config/verdaccio/config.yaml)
Pretty standard / default:
# path to a directory with all packages
storage: /<my_nas>/srv/npm
# path to a directory with plugins to include
plugins: ./plugins

web:
  enable: true
  title: Verdaccio
  # comment out to disable gravatar support
  # gravatar: false
  # by default packages are ordercer ascendant (asc|desc)
  # sort_packages: asc

auth:
  htpasswd:
    file: ./htpasswd
    # Maximum amount of users allowed to register, defaults to "+inf".
    # You can set this to -1 to disable registration.
    # max_users: 1000

security:
  api:
    jwt:
      sign:
        expiresIn: 60d
        notBefore: 1
  web:
    sign:
      expiresIn: 7d
      notBefore: 1

# a list of other known repositories we can talk to
uplinks:
  npmjs:
    url: https://registry.npmjs.org/

packages:
  '@*/*':
    # scoped packages
    access: $all
    publish: $authenticated
    unpublish: $authenticated
    proxy: npmjs

  '**':
    # allow all users (including non-authenticated users) to read and
    # publish all packages
    #
    # you can specify usernames/groupnames (depending on your auth plugin)
    # and three keywords: "$all", "$anonymous", "$authenticated"
    access: $all

    # allow all known users to publish/publish packages
    # (anyone can register by default, remember?)
    publish: $authenticated
    unpublish: $authenticated

    # if package is not available locally, proxy requests to 'npmjs' registry
    proxy: npmjs

# You can specify HTTP/1.1 server keep alive timeout in seconds for incomming connections.
# A value of 0 makes the http server behave similarly to Node.js versions prior to 8.0.0, which did not have a keep-alive timeout.
# WORKAROUND: Through given configuration you can workaround following issue https://github.com/verdaccio/verdaccio/issues/301. Set to 0 in case 60 is not enought.
server:
  keepAliveTimeout: 60

middlewares:
  audit:
    enabled: true

# log settings
logs:
  - { type: stdout, format: pretty, level: http }
  #- {type: file, path: verdaccio.log, level: info}

listen: <IP_ADDRESS>:4873

Environment information
System:
OS: Linux 3.4 Debian GNU/Linux 10 (buster) 10 (buster)
CPU: (4) arm ARMv7 Processor rev 5 (v7l)
Binaries:
Node: 13.14.0 - /usr/bin/node
npm: 6.14.5 - /usr/bin/npm
npmGlobalPackages:
verdaccio: 4.6.2
Debugging output

$ NODE_DEBUG=request verdaccio prints:

 error-=- error reading  package.json: Unexpected token : in JSON at position 216935
 http <-- 500, user: cmiksche(<my_client>), req: 'GET /husky', error: unknown error
 http <-- 500, user: cmiksche(<my_client>), req: 'GET /husky', error: unknown error
 error-=- error reading  package.json: Unexpected token          in JSON at position 57852
 http <-- 500, user: cmiksche(<my_client>), req: 'GET /jest', error: unknown error
 http <-- 500, user: cmiksche(<my_client>), req: 'GET /jest', error: unknown error

Seems your cache is corrupted, i would remove the packages are throwing error and try again

@juanpicado Thanks, deleting the packages helped.
But could we improve the error handling on that error? unknown error isn't really helpful and if there is no other solution, Verdaccio could remove the corrupted packages automatically?!

Our verdaccio server is working with 3 different upstreams and we also experience this problem from time to time. Deleting the affected package and retrying helps but I agree that it would help if cache corruptions like this could be detected and healed automatially

Are you using cluster with one instance ?

@juanpicado Are you referring to me or @jachstet-sea ?
I installed it simply via npm on a OrangePi PC (but it was more experimental - i think the performance of my OrangePi is too low) - no setup with Docker or Kubernetes

We're seeing the same issue, and have had it happen for a long time. Single instance basic k8s deployment with default container image.
All we do, is act as a proxy to speed up local builds, and 60% of the time when a PR introduces a new package or new version of a package, the build fails due to 500 error.
Retrying builds 2-3 times usually resolves it, as it finally downloads the package, and resumes normal operation.
We're running multiple builds in parallel on the same project, so we might have 2 npm ci running concurrently, trying to fetch the same packages. (Could that be why?)

We're seeing the same issue, and have had it happen for a long time. Single instance basic k8s deployment with default container image.
All we do, is act as a proxy to speed up local builds, and 60% of the time when a PR introduces a new package or new version of a package, the build fails due to 500 error.
Retrying builds 2-3 times usually resolves it, as it finally downloads the package, and resumes normal operation.
We're running multiple builds in parallel on the same project, so we might have 2 npm ci running concurrently, trying to fetch the same packages. (Could that be why?)

hi guys, keep on mind that access to the storage using multiple instances if you are using the default storage (file system) verdaccio lock the metadata file (see: https://github.com/verdaccio/monorepo/blob/9.x/plugins/local-storage/src/local-fs.ts#L65
) for such reason that storage is not scalable by default.
That explains why the retry might solve the issue.
@CMiksche the server logs would be more useful, but if the performance is low I'm afraid I cannot do much.

@juanpicado we only ever run a single pod in our cluster.

@CMiksche the server logs would be more useful, but if the performance is low I'm afraid I cannot do much.

$ NODE_DEBUG=request verdaccio prints:

 error-=- error reading  package.json: Unexpected token : in JSON at position 216935
 http <-- 500, user: cmiksche(<my_client>), req: 'GET /husky', error: unknown error
 http <-- 500, user: cmiksche(<my_client>), req: 'GET /husky', error: unknown error
 error-=- error reading  package.json: Unexpected token          in JSON at position 57852
 http <-- 500, user: cmiksche(<my_client>), req: 'GET /jest', error: unknown error
 http <-- 500, user: cmiksche(<my_client>), req: 'GET /jest', error: unknown error

I use forever and basically the same statements are in my forever logs - so i cannot provide more information because i don't have more information.
But i solved the initial problem (500 Internal Server Error - unknown error on only some packages) with your recommendation of deleting and reinstalling the packages with a error.
I don't have any other problems but it would be nice if we could automatically remove the packages with error reading  package.json: Unexpected token          in JSON at position and reinstall them instead of printing a error message ...

Hi pal 👋🏼!
This issue has gone quiet 😶.
We get a lot of issues, so we currently close issues after 180 days of inactivity. It’s been at least 90c days since the last update here.
If we missed this issue or if you want to keep it open, please reply here. You can also add/suggest the label "discuss" to keep this issue open!
As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request. Check out https://github.com/verdaccio/contributing for more information about opening PRs, triaging issues, and contributing!
Thanks for being a part of the Verdaccio community! 💘

The issue is probably not fixed but I can't check the current state because I stopped using Verdaccio....

Sorry the bot 🤖 got crazy this morning.

Sorry the bot 🤖 got crazy this morning.

I have a similar error. Please help me

I use nginx as a proxy

Installing using docker

config.yaml   as follows

Sorry the bot 🤖 got crazy this morning.

I have a similar error. Please help me

I use nginx as a proxy
Installing using docker

config.yaml as follows

The problem was solved,  It's a linux authorization  problem

I have a similar error.did you solve it?

@yanzhangshuai 大佬 这个问题 怎么解决的？ 我们这边也经常出现500的错误

我记得是linux目录权限问题


Agent cloning for Users...

I have Huginn deployed on ubuntu on my laptop.. i want to clone all agents of admin user for every new user.... can anyone help me with the query???

Hi @nineralpha,
you could put all your agents into a scenario and export it. Then on every new you create import the scenario.

O yes.. Thanks man that may help. i am going to try it
On Tue, Mar 8, 2016 at 8:49 PM, Dominik Sander<EMAIL_ADDRESS>wrote:

Hi @nineralpha https://github.com/nineralpha,
you could put all your agents into a scenario and export it. Then on every
new you create import the scenario.
—
Reply to this email directly or view it on GitHub
https://github.com/cantino/huginn/issues/1339#issuecomment-193832223.

I'm going to close this.  Please reopen if you have more questions!


Mappable split

Distinguish between a mappable entity and a transaction:

the mapping of an entity depends only on its properties
the mapping of a transaction depends on its properties, the operation type (required) and the parent transaction type (optional)

Transaction->mappedProperties

made the parameter operation required (remove the default value of null)
refactored the method to the template method pattern

Coverage remained the same at 100.0% when pulling 30ec36ce132cfb6ecc6de4154934416e1420138f on reka:mappable-split into da11081e74b889ae85ceb2109f826ea3efb37ec7 on wirecard:59-sepa.

Coverage remained the same at 100.0% when pulling 53e09cf1c9646a7f987560b4fb49281a7b1eab2e on reka:mappable-split into da11081e74b889ae85ceb2109f826ea3efb37ec7 on wirecard:59-sepa.


Fixing unmount delete test failure

After the longhorn refactor, this case was failing as Linux throws error
when the test case was trying to unmount the mount path when an active
volume has a replica running and storing meta files in this mount path.
The following code changes fixes it using -l flag to accomplish the
motive that the test case was trying to achieve.

If failed to umount due to Longhorn is actively using the disk, we still need to understand why it works before.

This was working before because replica was running as a docker container, not as a regular linux process. As a result, there was an internal volume binding created for replica container by the docker as shown below:
"HostConfig": {
            "Binds": [
                "/tmp/longhorn-test/testdisk/replicas/test2-edbc5e08:/volume",
                 ...
            ]
}
"Mounts": [
            {
                "Type": "bind",
                "Source": "/tmp/longhorn-test/testdisk/replicas/test2-edbc5e08",
                "Destination": "/volume",
                "Mode": "",
                "RW": true,
                "Propagation": "rprivate"
            },

However, when I tried to do unmount docker command, I still see the same error:
root@mas1# docker exec 5f6002acacdb umount /volume
umount: /volume: target is busy
        (In some cases useful info about processes that
         use the device is found by lsof(8) or fuser(1).)

But when you unmount the actual path as a linux command (and not a docker command), I believe linux is agnostic of this path being re-mounted by the docker container and ends up un-mounting it.
I also think it relies on the fact that this mount path is not mentioned the ps output of the replica process:
v0.5.0:
Mount path: /tmp/longhorn-test/testdisk
root@mas1:/tmp/longhorn-test/testdisk/replicas/test2-edbc5e08# ps ax | grep replica
18359 ?        Ssl    0:03 longhorn replica --listen <IP_ADDRESS>:9502 --size<PHONE_NUMBER>0 /volume

After Refactor:
Mount path: /tmp/longhorn-test/testdisk
 3771 ?        Sl     0:00 /usr/local/bin/longhorn replica /host/tmp/longhorn-test/testdisk/replicas/diskvol-36396a63 --size<PHONE_NUMBER> --listen <IP_ADDRESS>:10015

Make sense. Sounds like a bug for Linux before the refactoring, since umount should return the same result if the target was busy even the path is bind-mounted instead of directly mounted in the same namespace.


feat(google-maps): add google-map component

Add initial infrastructure for angular/google-maps,
a skeleton for the google-map component, and a demo
for the google map component

Also, sorry for all the merge conflicts; I just merged the youtube-player


[bug] window display abnormally when the frontend dynamically changes decorations from true to false if use 'window.open_devtools()' at 'main.rs' in MacOS

Describe the bug
https://user-images.githubusercontent.com/15380331/187812807-67c5e170-02c4-4eb3-b573-037b524ed410.mov
Reproduction
reproduction code  is here.
run the app to see the effect.
block this code and run again is fine.
#[cfg(any(debug_assertions, feature = "devtools"))]
window.open_devtools();

Expected behavior
No response
Platform and versions
MacOS v11.4 (M1)

Environment
› OS: Mac OS 11.4.0 X64
› Node.js: 17.0.1
› npm: 8.1.0
› pnpm: Not installed!
› yarn: 1.22.17
› rustup: 1.25.1
› rustc: 1.63.0
› cargo: 1.63.0
› Rust toolchain: stable-aarch64-apple-darwin
Packages
Error only one package mangager should be used, but found npm and yarn

Cargo.tmol
[build-dependencies]
tauri-build = { version = "1.0.4", features = [] }
[dependencies]
serde_json = "1.0"
serde = { version = "1.0", features = ["derive"] }
tauri = { version = "1.0.5", features = ["api-all"] }
Stack trace
No response
Additional context
No response

upstream issue https://github.com/tauri-apps/wry/issues/297


#323 hack aubg background colors

Used a dark green colour for beckground and lighter green for text

Note here that I remove commented css codes from all files and at the same time fixed another issue which was the breakage of the awards section text for mobile devices.


Resolving #2153  Added ability to set frame-lock.

Added ability to increase / decrease max FPS.
By default disabled.
By pressing shift & -  -> decrease the limit.
By pressing shift & + -> increase the limit.
Also updated stats FPS with render FPS & loopFPS:

in console you can see what exact limit was set [after changing the limit].

Added comments as requested + added check is typing inside of input [in this case don't apply].

Decreasing and increasing the limit seems to be working fine but render fps don't go be beyond 60 fps even if the limit is set at 100fps. Is it dependent on refresh rate of screen?
https://user-images.githubusercontent.com/35926530/163037376-e26e4acb-55bc-4556-b91d-17f602216418.mp4

Decreasing and increasing the limit seems to be working fine but render fps don't go be beyond 60 fps even if the limit is set at 100fps. Is it dependent on refresh rate of screen?
bandicam.2022-04-13.00-15-51-603.mp4

Usually max refresh rate is 60fps. But if your device has low performance and you get max 40fps for example you can not go beyond this physical limit of computation power of your device.

Usually max refresh rate is 60fps.

This should be determined by the browser and how fast it fires requestAnimationFrame. We should not hardcode any values here.

Usually max refresh rate is 60fps.

This should be determined by the browser and how fast it fires requestAnimationFrame. That is not necessarily 60FPS.
(note that we should not hardcode any values here)

so anything to be changed ?
you want to replace 2 * 16.6 with a constant and that's it ?
anything else ?

This isn't likely to ship.


Chart.Js - Maximum Call Stack Size Exceeded (Chrome), too much recursion (Firefox) com.google.gwt.core.client.JavaScriptException

Hi,
Chart.js classes of charts occur Error in browsers,
some one know how to solve?
the bug occur only in Vaadin debug application mode, but i'm not sure if in production mode it presents in a hidden way and complicates the UI client's performance or application server consumption
Thanks
JJL

I don't think anyone here will be able to debug this since we don't use GWT / Vaadin and it doesn't appear to be a bug in Chart.js, but rather in how those tools have been setup to use Chart.js. I think the best place to work on debugging this issue would be in the ticket for vaadin-chartjs as that would be a community with much stronger knowledge of this issue: https://github.com/moberwasserlechner/vaadin-chartjs/issues/17

benmccann thanks for your reply and for directions,
I'll explain better, I did not mean if anyone could debug, mine was an affirmation
when you set up the Vaadin Servelet configuration in debug mode, in order to use Inspector tools,
if there are any Chart.js components (based on GWT) in the GUI, this error occur and does not allow you to use Vaadin's debugging tool well,
moreover the applications go in a block with the blue progress bar that stops and flashes and from there it does not move anymore.
I was wondering if anyone has solved and in which way this bug clearly/probably is in Chart.js since it also sometimes comes out in the original link of the classes. as seen from the attached images
http://vaadin-demos.qqjtxeeuih.eu-central-1.elasticbeanstalk.com:5600/?debug#!multi-axis-bar-chart

I don't see any indication that this is a bug in Chart.js. You would need to give us a bit more info showing what the bug might. I've never seen this using Chart.js alone. It seems more like a bug in Vaadin or the GWT configuration to me. All the stack trace lines refer to com.vaadin.DefaultWidgetSet. There's no information about Chart.js here that would let us know where to look. I'm not sure what this output like at Unknown.new O4d means. If that's a minimized symbol perhaps try using the non-minimized version to get more useful debug output?
Mon Feb 11 10:06:59 GMT-800 2019 com.vaadin.client.ApplicationConfiguration
SEVERE: (RangeError) : Maximum call stack size exceeded
com.google.gwt.core.client.JavaScriptException: (RangeError) : Maximum call stack size exceeded
	at Unknown.new Map(Unknown)
	at Unknown.z5d(com.vaadin.DefaultWidgetSet-0.js)
	at Unknown.new k5d(com.vaadin.DefaultWidgetSet-0.js)
	at Unknown.B$d(com.vaadin.DefaultWidgetSet-0.js)
	at Unknown.new O4d(com.vaadin.DefaultWidgetSet-0.js)
	at Unknown.Jv(com.vaadin.DefaultWidgetSet-0.js)
	at Unknown.new Lv(com.vaadin.DefaultWidgetSet-0.js)
	at Unknown.vv(com.vaadin.DefaultWidgetSet-0.js)
	at Unknown.new uv(com.vaadin.DefaultWidgetSet-0.js)
	at Unknown.Nnb(com.vaadin.DefaultWidgetSet-0.js)
	at Unknown.QHb(com.vaadin.DefaultWidgetSet-1.js)
	at Unknown.new RHb(com.vaadin.DefaultWidgetSet-1.js)
	at Unknown.vLb(com.vaadin.DefaultWidgetSet-1.js)
	at Unknown.uLb(com.vaadin.DefaultWidgetSet-1.js)
	at Unknown.vLb(com.vaadin.DefaultWidgetSet-1.js)
	at Unknown.uLb(com.vaadin.DefaultWidgetSet-1.js)
	at Unknown.vLb(com.vaadin.DefaultWidgetSet-1.js)
	at Unknown.uLb(com.vaadin.DefaultWidgetSet-1.js)
	at Unknown.vLb(com.vaadin.DefaultWidgetSet-1.js)
	at Unknown.tLb(com.vaadin.DefaultWidgetSet-1.js)
	at Unknown.vLb(com.vaadin.DefaultWidgetSet-1.js)
	at Unknown.uLb(com.vaadin.DefaultWidgetSet-1.js)
	at Unknown.vLb(com.vaadin.DefaultWidgetSet-1.js)
	at Unknown.uLb(com.vaadin.DefaultWidgetSet-1.js)
	at Unknown.vLb(com.vaadin.DefaultWidgetSet-1.js)
	at Unknown.uLb(com.vaadin.DefaultWidgetSet-1.js)
	at Unknown.vLb(com.vaadin.DefaultWidgetSet-1.js)
	at Unknown.tLb(com.vaadin.DefaultWidgetSet-1.js)
	at Unknown.vLb(com.vaadin.DefaultWidgetSet-1.js)
	at Unknown.uLb(com.vaadin.DefaultWidgetSet-1.js)
	at Unknown.vLb(com.vaadin.DefaultWidgetSet-1.js)
	at Unknown.uLb(com.vaadin.DefaultWidgetSet-1.js)
	at Unknown.vLb(com.vaadin.DefaultWidgetSet-1.js)
	at Unknown.uLb(com.vaadin.DefaultWidgetSet-1.js)
	at Unknown.vLb(com.vaadin.DefaultWidgetSet-1.js)
	at Unknown.uLb(com.vaadin.DefaultWidgetSet-1.js)
	at Unknown.vLb(com.vaadin.DefaultWidgetSet-1.js)
	at Unknown.tLb(com.vaadin.DefaultWidgetSet-1.js)
	at Unknown.vLb(com.vaadin.DefaultWidgetSet-1.js)
	at Unknown.uLb(com.vaadin.DefaultWidgetSet-1.js)
	at Unknown.vLb(com.vaadin.DefaultWidgetSet-1.js)
	at Unknown.uLb(com.vaadin.DefaultWidgetSet-1.js)
	at Unknown.vLb(com.vaadin.DefaultWidgetSet-1.js)
	at Unknown.uLb(com.vaadin.DefaultWidgetSet-1.js)
	at Unknown.vLb(com.vaadin.DefaultWidgetSet-1.js)
	at Unknown.tLb(com.vaadin.DefaultWidgetSet-1.js)
	at Unknown.vLb(com.vaadin.DefaultWidgetSet-1.js)
	at Unknown.uLb(com.vaadin.DefaultWidgetSet-1.js)
	at Unknown.vLb(com.vaadin.DefaultWidgetSet-1.js)
	at Unknown.uLb(com.vaadin.DefaultWidgetSet-1.js)
	at Unknown.vLb(com.vaadin.DefaultWidgetSet-1.js)
	at Unknown.uLb(com.vaadin.DefaultWidgetSet-1.js)
	at Unknown.vLb(com.vaadin.DefaultWidgetSet-1.js)
	at Unknown.uLb(com.vaadin.DefaultWidgetSet-1.js)
	at Unknown.vLb(com.vaadin.DefaultWidgetSet-1.js)
	at Unknown.tLb(com.vaadin.DefaultWidgetSet-1.js)
	at Unknown.vLb(com.vaadin.DefaultWidgetSet-1.js)
	at Unknown.uLb(com.vaadin.DefaultWidgetSet-1.js)
	at Unknown.vLb(com.vaadin.DefaultWidgetSet-1.js)
	at Unknown.uLb(com.vaadin.DefaultWidgetSet-1.js)
	at Unknown.vLb(com.vaadin.DefaultWidgetSet-1.js)
	at Unknown.uLb(com.vaadin.DefaultWidgetSet-1.js)
	at Unknown.vLb(com.vaadin.DefaultWidgetSet-1.js)
	at Unknown.tLb(com.vaadin.DefaultWidgetSet-1.js)

I actually considered to chart.js is involved in the bug just because it comes out when I add a chart component of any type to the GUI,
if I do not add a chart.js component this bug does not come out .. but I can not say where the problem is because on my console does not come out any exception (despite having captured in all the methods of our classes) and also re-launching from the methods of the components chart.js
so I do not know how I can find the origin, those coded messages I do not know what they are, I think it's a trace of GWT components
I do not know what to do to find out the cause, I also checked that in the final components of the chart there are recursive calls but it is not so,
however I did not go to the bottom (parent classes) in the java classes of chart.js, I use them as final components without modifying them

in addition, the last components added to our applications, graph charts are the only JavaScript code,
and questobug only presented with the addition of these classes (chart.js) and there is evidence only when we set the vaadin applications to debug mode

I assume this was the cause in his case too:
I get this when I try to provide arrays for pointRadius, pointBackgroundColor, pointBorderColor, pointHoverRadius, pointHoverBackgroundColor, pointHoverBorderColor in an attempt to mark certain points in the chart.
The clone calls itself for each of those array elements, so when chart has many points it all quickly gets out of hand.

@mbonaci it's strange to get a call stack size error here because there is only one recursion level for arrays (except if your array contains objects or arrays). Starting 2.8, almost all dataset options are now scriptable, which I think should be used most of the time instead of providing arrays.

I also am having this issue "max stack size exceeded" with chart.js 2.9.3.    However in chart.js version 2.8.0 it works fine for me.  I will try to create an example of the issue.

So I am including an object i called "meta1" in the datasets object which has a bunch of data/info for drilldown purposes.  When a user clicks on a point on the current graph it will drilldown to the next level by using the meta1 object -- and on down as many levels the user wants to drilldown.
In chart.js 2.8.0 this method of doing drilldown works fine.   However, in chart.js 2.9.3 I get the "max stack size exceeded" error.  I am guessing that chart.js must be cloning or following this large "meta1" object I am passing along with the dataset and it is causing this error.
Is there any way to just have chart.js clone only the things it needs in the object rather than following any and all items in the dataset object?

I was storing objects in chartInstance.options temporarily and not deleting them. These objects were references/copies of other objects in the chartInstance. I think that was causing the recursion. My bad.

I have this issue too , use with angular 8:
ERROR RangeError: Maximum call stack size exceeded
at Chart.js:9286
at Array.sort ()
at Chart._getSortedDatasetMetas (Chart.js:9870)
at Chart._getSortedVisibleDatasetMetas (Chart.js:9879)
at ChartElement._getMatchingVisibleMetas (Chart.js:12512)
at ChartElement.determineDataLimits (Chart.js:12979)
at ChartElement.update (Chart.js:11502)
at fitBoxes (Chart.js:7127)
at fitBoxes (Chart.js:7145)
at fitBoxes (Chart.js:7145)

i hace the same error anyone knows how to solved it ?

Suffering from the same issue, using angular.
@benmccann this seems to be a general issue, not directly related to vaadin. You should consider to reopen this ticket.

We would need an issue filed that follows our issue guidelines. Specifically we would need a piece of code that reproduces the issue

I had the same problem implementing the graphs in angular, using canvas and ViewChild, initializing the graphs in ngAfterViewInit.
Although the ngAfterViewInit waits for the rendering of the html, it kept giving me the error mentioned in this issue and it only painted the first graph that it initialized.
What I did was add a setTimeOut to initialize the graphics inside the ngAfterViewInit, and all the graphics were rendered without any message in the console.
It has not yet been determined, but with this I was able to solve it.

Used to have this problem with react-chartjs-2 v2.10.0 and React v16.14.0
The problem was solved by removing 'responsive: true' from options, it might have called too much rerender

Used to have this problem with react-chartjs-2 v2.10.0 and React v16.14.0
The problem was solved by removing 'responsive: true' from options, it might have called too much rerender


Revert "Allow BCCSP config to be set using env var (#1900)"

This reverts commit 0a9f7663a3a548385f3e4fa55e147b6dbce055d4 which pushed the pkcs11 code outside of the pkcs11 build tag. This prevents cross-compilation of Fabric due to the fact the miekg/pkcs11 package contains CGO which requires a cross-compiler for each platform you are cross compiling for.
We need to find a better approach to solving this problem that doesn't pull the code out of the build tag.
Signed-off-by: Brett Logan<EMAIL_ADDRESS>

@btl5037 @wlahti  I assume the release-2.2 PR also needs to be reverted?

@btl5037 @wlahti I assume the release-2.2 PR also needs to be reverted?

I didn't realize this was backported, I'll revert it there as well.

We never really wanted to do this one but you guys kept pushing us. ;) Makes sense to me.


Remove batch processor from traces pipeline

What does this PR do?
The PR removes batch processor from OTLP traces pipeline.

Motivation
OTLP trace data in the agent goes through multiple hops before it is sent to our backend. Agent drops trace data during the handshake and customer receives error with no helpful information and no way to overcome the limitations.
Customers can set the OTLP GRPC receiver message limit via max_rcv_msg_size_mib. The batch processor will combine large GRPC messages and send them to the trace agent. It results in a message that is larger than the trace agent GRPC limit of 10 MB. We can't configure the message size via the batch processor; it results in large messages that get dropped because of the trace agent limit.
For example, If we send five messages of 3 MB size to the core agent within 10 seconds. Core Agent will try to send a 15 MB message to the trace agent, but that fails.

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes
Use the python script to generate traces.
from opentelemetry import trace
from opentelemetry.exporter.otlp.proto.grpc.trace_exporter import \
    OTLPSpanExporter
from opentelemetry.sdk.trace import TracerProvider
from opentelemetry.sdk.trace.export import BatchSpanProcessor
from opentelemetry.trace import SpanKind

trace.set_tracer_provider(TracerProvider())

# Configure the OTLP exporter
otlp_exporter = OTLPSpanExporter(
    endpoint="localhost:43177",
    insecure=True,
)

# Add the OTLP exporter to the tracer provider
trace.get_tracer_provider().add_span_processor(BatchSpanProcessor(otlp_exporter))

# Function to generate a single trace with multiple spans
def generate_single_trace_with_multiple_spans(
    tracer, child_spans_count, attributes_count, attribute_length
):
    with tracer.start_as_current_span("root-span", kind=SpanKind.SERVER) as root_span:
        # Creating child spans within the root span
        for i in range(child_spans_count):
            with tracer.start_as_current_span(
                f"child-span-{i}", kind=SpanKind.INTERNAL
            ) as child_span:
                # Add specified number of attributes to each child span
                for j in range(attributes_count):
                    attr_value = (
                        "x" * attribute_length
                    )  # Create an attribute value of the specified length
                    child_span.set_attribute(f"key_{j}", attr_value)

# Get a tracer
tracer = trace.get_tracer(__name__)

# Generate a trace with multiple spans and add attributes to each span
generate_single_trace_with_multiple_spans(
    tracer, child_spans_count=1000, attributes_count=50, attribute_length=100
)

Run the script in a loop
for i in {1..100}
do
  python py_apps/generate_trace.py
done

With the change, the data shouldn't get dropped in core agent. We should see the trace in the Datadog UI.

Reviewer's Checklist

[x] If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
[ ] Use the major_change label if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.
[ ] A release note has been added or the changelog/no-changelog label has been applied.
[ ] Changed code has automated tests for its functionality.
[x] Adequate QA/testing plan information is provided. Except if the qa/skip-qa label, with required either qa/done or qa/no-code-change labels, are applied.
[x] At least one team/.. label has been applied, indicating the team(s) that should QA this change.
[ ] If applicable, docs team has been notified or an issue has been opened on the documentation repo.
[ ] If applicable, the need-change/operator and need-change/helm labels have been applied.
[ ] If applicable, the k8s/<min-version> label, indicating the lowest Kubernetes version compatible with this feature.
[ ] If applicable, the config template has been updated.

/merge


Various fixes

I've found that there were several columns duplicated in Misc section, so I removed them

fixes #40

Please consider that this is one my first step in modding, so review accurately.

@Mehni just to let you know about this pull request

Thank you kindly, and my apologies that this PR slipped under the radar.
For 1.4, Ludeon has done a decent job of creating tame/hunt columns so I'll use those.
I've incorporated the other bugfixes in #48.
Thank you again for your contribution!


Release/1.2.14

I've switched to draft with this release, due to Flutter 3 being released just now. I'd like to check compatibility with it before we release a new version of flutter

Blocked until https://github.com/ably/ably-flutter/issues/394 is resolved

Tthings like test changes and internal refactors do not need to be included.

I've removed some entries in https://github.com/ably/ably-flutter/pull/393/commits/6c801db8aa1f683319361f35b14c8c9a5fc40644


Update bl to >=0.9.5

Fixes #8.

@MineRobber9000 due to lack of response I'm going to close this pull request.


H2 & H3 errors on ICDS website

Summary of the bug
When inspecting the titles on the ICDS component pages what is graphically displayed does not match with the code
🪜 How to reproduce
Tell us the steps to reproduce the problem:

Go to page: '...'
Open the inspect function
Hover over the title that says 'Introduction' or 'Component variants'
Notice how the code states that it is a H3 title, whereas visibly it is a H2 title.

📸 Screenshots or code
🖥 📱 Device

Type: Desktop
Device: MacBook
OS version: macOS Sonoma
Browser version: Safari 17.1

🧐 Expected behaviour
The titles styles used for the  'Introduction' and 'Component variants' should match what the code says. I.e. if it shows a H2 title (as it currently does) then the code should state H2 not H3.
📝 Acceptance Criteria
If relevant, describe in full detail the different interactions and edge cases that the component or patterns needs to fulfil.
Given
When
Then
Additional info
Tell us anything else useful to help us fix or understand the problem.

This work has been completed as https://github.com/mi6/ic-design-system/pull/688


[stable/rabbitmq-ha] Unable to apply the policies

Describe the bug
A clear and concise description of what the bug is.
Unable to apply the default policies through the values.yaml file
Version of Helm and Kubernetes:
Helm- v3.0.2      k8s- v1.17.0
Which chart:
stable/rabbitmq-ha
What happened:
coalesce.go:199: warning: destination for policies is a table. Ignoring non-table value
Error: template: rabbitmq-ha/templates/statefulset.yaml:43:28: executing "rabbitmq-ha/templates/statefulset.yaml" at <include (print $.Template.BasePath "/secret.yaml") .>: error calling include: template: rabbitmq-ha/templates/secret.yaml:26:38: executing "rabbitmq-ha/templates/secret.yaml" at <include "rabbitmq-ha.definitions" .>: error calling include: template: rabbitmq-ha/templates/_helpers.tpl:107:41: executing "rabbitmq-ha.definitions" at <4>: wrong type for value; expected string; got map[string]interface {}

What you expected to happen:
The policies should be created and able to deploy the chart successfully
How to reproduce it (as minimally and precisely as possible):
Try enabling the policies section in the values.yaml with the below values:
policies:
    {
       "name":"ha-custom-policy",
       "pattern":".*",
       "vhost":"/",
       "definition":{
          "ha-mode":"exactly",
          "ha-params":2,
          "ha-sync-mode":"automatic",
          "ha-sync-batch-size":1
        }
    }

Anything else we need to know:
N/A

Sorry - This is due to my mistake and I missed |-
policies:
    {
       "name":"ha-custom-policy",
       "pattern":".*",
       "vhost":"/",
       "definition":{
          "ha-mode":"exactly",
          "ha-params":2,
          "ha-sync-mode":"automatic",
          "ha-sync-batch-size":1
        }
    }


[MSKINS-177] Support Matomo (e.g. Apache Analytics) as macro

Signed-off-by: Olivier Lamy<EMAIL_ADDRESS>

depends on https://github.com/apache/maven-doxia-sitetools/pull/32

This should only be Matomo-specific, not ASF specific. Just make the full host a mandatory config option (next to site id) to make this feature usable outside ASF projects.

This should only be Matomo-specific, not ASF specific. Just make the full host a mandatory config option (next to site id) to make this feature usable outside ASF projects.

I like that. It could be in custom/matomo/....

makes sense using something generic such custom/matomo/.. I will change that

This deserves some documentation

This should only be Matomo-specific, not ASF specific. Just make the full host a mandatory config option (next to site id) to make this feature usable outside ASF projects.

isn't good enough? https://github.com/apache/maven-fluido-skin/pull/22/files#diff-85dce09d83956e168d3fdfc3bfe3119e82cb7d0e18083a0a475441337168fcee

The CDATA block is broken:
Please remove it, it has no use these days.

interesting

Please remove it, it has no use these days.

CDATA you mean? because I don't understand the link with the screenshot attached