Upgrade vineyard to v0.1.5.

What do these changes do?
Note that this pull request also modifies the CI YAML configurations.
Related issue number
N/A.

Codecov Report

Merging #73 (66be776) into main (5c9a222) will decrease coverage by 12.34%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##             main      #73       +/-   ##
===========================================
- Coverage   78.04%   65.70%   -12.35%
===========================================
  Files          49       48        -1
  Lines        4473     4298      -175
===========================================
- Hits         3491     2824      -667
- Misses        982     1474      +492

Impacted Files
Coverage Δ

python/graphscope/interactive/__init__.py
0.00% <0.00%> (-100.00%)
:arrow_down:

python/graphscope/interactive/query.py
0.00% <0.00%> (-94.65%)
:arrow_down:

python/graphscope/deploy/kubernetes/utils.py
12.50% <0.00%> (-61.46%)
:arrow_down:

python/graphscope/deploy/kubernetes/cluster.py
22.96% <0.00%> (-51.30%)
:arrow_down:

...n/graphscope/deploy/kubernetes/resource_builder.py
29.03% <0.00%> (-32.56%)
:arrow_down:

python/graphscope/analytical/app/triangles.py
80.00% <0.00%> (-20.00%)
:arrow_down:

python/graphscope/client/utils.py
79.16% <0.00%> (-16.92%)
:arrow_down:

python/graphscope/client/rpc.py
66.93% <0.00%> (-16.89%)
:arrow_down:

python/graphscope/client/session.py
63.44% <0.00%> (-9.62%)
:arrow_down:

python/graphscope/framework/vineyard_object.py
83.33% <0.00%> (-4.17%)
:arrow_down:

... and 13 more

Continue to review full report at Codecov.

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

Codecov Report

Merging #73 (66be776) into main (5c9a222) will decrease coverage by 12.34%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##             main      #73       +/-   ##
===========================================
- Coverage   78.04%   65.70%   -12.35%
===========================================
  Files          49       48        -1
  Lines        4473     4298      -175
===========================================
- Hits         3491     2824      -667
- Misses        982     1474      +492

Impacted Files
Coverage Δ

python/graphscope/interactive/__init__.py
0.00% <0.00%> (-100.00%)
:arrow_down:

python/graphscope/interactive/query.py
0.00% <0.00%> (-94.65%)
:arrow_down:

python/graphscope/deploy/kubernetes/utils.py
12.50% <0.00%> (-61.46%)
:arrow_down:

python/graphscope/deploy/kubernetes/cluster.py
22.96% <0.00%> (-51.30%)
:arrow_down:

...n/graphscope/deploy/kubernetes/resource_builder.py
29.03% <0.00%> (-32.56%)
:arrow_down:

python/graphscope/analytical/app/triangles.py
80.00% <0.00%> (-20.00%)
:arrow_down:

python/graphscope/client/utils.py
79.16% <0.00%> (-16.92%)
:arrow_down:

python/graphscope/client/rpc.py
66.93% <0.00%> (-16.89%)
:arrow_down:

python/graphscope/client/session.py
63.44% <0.00%> (-9.62%)
:arrow_down:

python/graphscope/framework/vineyard_object.py
83.33% <0.00%> (-4.17%)
:arrow_down:

... and 13 more

Continue to review full report at Codecov.

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


Prompt on newline

Added an option to set prompt on a new line.
This is just a port of https://github.com/robbyrussell/oh-my-zsh/pull/2984

Nice work! Excellent customization option.


Cannot run the simulator

Hello,
sorry to bother you, I have read your paper and I noticed that in simulator you used different boundary conditions for TEO setup compared to ones that are in the paper. I assume you used grid-centered blocks with two ghost cells as boundaries. Also I assume you used harmonic means of mobilities with no Upwinding. I tried to use the boundaries you specified in the paper in my simulator but it didn’t converge even for the first time step. I would appreciate if you can explain me which boundary conditions to use.
In addition I tried to run your code but there is some kind of mistake which doesn’t allow me run it. Please could you check your uploaded files.
Thank you.

Hello,
Thank you for reaching out. May I know what the problem is exactly (with my code I mean)?
Especially for the OEO case, I remember the boundaries are very critical and sensitive to implementation. To be honest, the code is a little messy; however, you can find the applied boundaries in the file 'FlowFncs.py'; function 'buildIt'. Can you read it properly?
BTW, I uploaded a new branch. Can you also check the new upload? 'Cent_Sim_Kumar2014 - 2.py' This file particularly.

Thanks for your reply and upload!
I will try to run your code again later this week.
In no way I am an expert in numerical simulations, so my questions may sound basic.
If you look at your paper, eq. 36 for TEO boundaries and Python code (FlowFncs line 128 and 129) do not match a little bit, here I assume that 0 index in the paper is for innermost ghost cell. For me it looks like in your code you set this condition also to grid #1.
Another question is as you mention in eq. 35, Lambda_w (1/2)=0 (i.e. at the boundary), and theoretically it is only possible if both grids #0 and #1 are at Smin? The same is for outermost end of core, as non-wetting phase is immobile here, grid #N and #N+1 should be at Smax, as non-wetting phase mobility is zero at the boundary. Would it be possible to force set saturations in these cells to the abovementioned values and get right boundaries? Or I missed something?

My Pleasure :) .
Regarding the 1st question: Cell [0] is the innermost cell (close to the center), and out of porous media. So, Pc=0 (infinite pore radius). Cell [1] can be assumed to be infinitely close to cell [0], but inside the porous media, so Pc is not zero. Line 128 addresses Eq. 36 when Pc=0. While Line 129 addresses Eq.36 when Pc is not zero. This is the difference between them.
Regarding question 2, I hope I understood it well. But at the innermost cell, where the water-saturated core is exposed to the nonwetting phase, no physical force allows water to be expelled from this side.  However, we can not (to have better numerical performance) set the saturation cell [1] to be Smin. So, we should manually set the transmissibility to zero (Line 161).   I am not sure about my answer, but I guess if you force-set the saturations, it may create some material balance problems. Setting the transmissibilities seems to be more physical than setting the saturations, from my perspective. However, you can quickly try both to see which one works better [I may not remember the details of my work correctly, since it is related to two years ago :) ).

Thank you very much for your reply)
Now your logic is clear to me.
I installed all required modules and tried to run your code. There was an error in Visualization class, so I assumed that file name was different and renamed "dataVisualization_1" to "visualizationClass".
After this I got this error:
= RESTART: C:\Users\Nurlan\Downloads\centrifuge_public-Full_Code\centrifuge_public-Full_Code\Cent_Sim_Kumar2014.py
Traceback (most recent call last):
File "C:\Users\Nurlan\Downloads\centrifuge_public-Full_Code\centrifuge_public-Full_Code\Cent_Sim_Kumar2014.py", line 9, in
import CentSimCore as simcore
File "C:\Users\Nurlan\Downloads\centrifuge_public-Full_Code\centrifuge_public-Full_Code\CentSimCore.py", line 15, in
from visualizationClass import *
File "C:\Users\Nurlan\Downloads\centrifuge_public-Full_Code\centrifuge_public-Full_Code\visualizationClass.py", line 9, in
optData = pd.read_pickle("./optData.pkl")
File "C:\Users\Nurlan\AppData\Local\Programs\Python\Python311\Lib\site-packages\pandas\io\pickle.py", line 179, in read_pickle
with get_handle(
File "C:\Users\Nurlan\AppData\Local\Programs\Python\Python311\Lib\site-packages\pandas\io\common.py", line 868, in get_handle
handle = open(handle, ioargs.mode)
FileNotFoundError: [Errno 2] No such file or directory: './optData.pkl'
I assume there is a problem with optData.pkl missing in the directory.
How can I generate this file? Or there is some mistakes in the code?
Sorry for so many questions) Hope you can help me.

Hello,
There is one more question regarding the boundaries:
For TEO case in the first grid you specified this boundary:
PX[1]=self.PnwEqDuetoRotationMAX(omega)-rf.pc(SwX[1])
As the first grid cell is always updated during newton iterations, this boundary also changes, or you force set it to the specified values?

Hello,
sorry for late reply. I added new files, please check the visualization class uploaded.
Regarding your question, since here the pressure is a function of Sw, it is updated in each iteration. However, since here the cell is in touch with the boundary, its Pressure value should be manually set at each iteration, as you see here.

Hello, thank you for uploaded new files. It was very helpful.
I used boundary conditions you mentioned earlier and now I can match theoretical saturation profile with numerical pretty close, but still there is some difference of about 1-2 saturation units on average. But when running your code it matches perfectly.
Could this be due to grid size that I use? My grid sizes are all the same for real and ghost cells.
Also for calculations of terms in jacobian matrix, I mean partial derivatives, I use central difference, and for dx I use fixed value of about 1E-10. Could this also be a problem here?
Thank you in advance.

Hi, I am happy it finally worked :).
Yes, one of the reasons can be the large grid sizes, especially at points close to the BCs (and small time steps at the beginning times). You can use large grid numbers or use non-uniform grinding, in which the size of the grid cells increases, e.g., logarithmically.
I guess it would be problematic if you used the same cell sizes for the ghost and real cell sizes.
I do not think the mentioned approach in partial derivatives can create serious challenges if everything is done truly.
BTW, I guess you can use still a larger dx value :).
I would be happy to answer if there are any other questions :).


build: upgrade to ng 14

Updates packages to Angular v14 (will be backwards compatible).
This update should work for Angular 9, 10, 11, 12, 13 and 14
Resolves: #2008, #2000, #1993, #1987, #1956, #1932, #1938, #1942

Hi,
I'm also desperate for this merge.
Many thanks
Jose Coelho

Like probably most here, I’m stuck between a rock and a hard place. capacitor/google-maps is not working on iOS and @agm is not working with angular 12 ;(
While we’re waiting for the merge would it be able to install the branch of Jay Bell? I’ve tried several approaches installing the branch via NPM or via the dependencies in package.json but I’ve not been successful.
@yharaskrik could you provide some hints on how to achieve that as a temporary solution?

@psmeets I created a fork of agm https://github.com/ng-maps/ng-maps
Maybe this could also help. Although I don't have a lot of time for maintaining it I can manage to release updates along with new angular versions. Most of the API is the same as with agm.

Because I wasn't sure if this was going to get merged or not I created a simple (very small) package to do places autocomplete on a form field if that is what you were using it for.
https://www.npmjs.com/package/@trellisorg/google-places-autocomplete

@yharaskrik Thx for your quick reply and clarification, my use case is different
@DaSchTour Thx for your suggestion, it will be the next thing to try if merging is not going forward..

Is this moving forward? 😞 We can't upgrade to Angular 12+ because of dependencies issues..

@itayperry you can check https://github.com/ng-maps/ng-maps which is a fork of this project and should support everything agm supports.

so ? :D what now ? should we start using another lib or what ?

Hi! Since the angular 14 update for angular-google-maps was done and the last release (1.1.0) was quite long ago (July 20, 2020), I wonder when there will be a new release that contains the changes? Any plans? I would appreciate it. Thanks! @yharaskrik @sebholstein


Add basic search functionality to the backend

Add simple search features to the backend:

column = value (exact match)
column != value (exact non-match)
value (any column contains value)

At the moment, we can only search in the fields that are indexed for full-text search.

Restructured the code; added integration tests for the search functionality.

Looks good.


Add privacy manifest file for iOS

Apple saying that the requirement will take effect May 1st: https://developer.apple.com/news/?id=3d8a9yyh, need to add PrivacyInfo.xcprivacy file following the new apple policy.

https://developers.weixin.qq.com/doc/oplatform/Mobile_App/Access_Guide/iOS.html
是不是可以删除本地XCFramework，直接依赖远程
wechat_kit.podspec增加s.dependency 'WechatOpenSDK-XCFramework'


STORM-2072 Add map, flatMap with different outputs (T->V) in Trident

Introduce overloading methods of map and flatMap

Now users can specify new output fields which replace origin fields

Introduce OperationMapFunction and OperationFlatMapFunction

which also extends Operation
Trident will automatically determine this and handle properly

Also updated example code and docs page.
This change is needed for optimizing Storm SQL on Trident mode to have minimized steps.
I'll work on optimization on top of this and submit that as well.

@arunmahadevan I have commented or addressed all of comments. Please have a look again. Thanks!

+1. @arunmahadevan you might want to take a look again.

+1


Update SessionDefaults.cs

Change Default Cookie Name

Hi @anandgt2, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, DNFBOT;

I don't think this change will have a good benefit, furthermore there many repos already have the same pattern

We already made this change in several repoes.

@Tratcher since 6 months back I notice the cookie names has different pattern in several repos, some using underscore and some using dots, any plans to unify them?

Not yet, but we should. What repos and cookies have you seen?

I notice this in Session & Localization repo, because mainly I contribute on them, but I will try to mention other repos soon

BTW regarding the change the made by @anandgt2 , In which repos is already done, because I didn't expect at first glance it will add a value

FYI this got fixed in PR #98


Update tasks depending on republished common npm packages

Description: next common npm packages have been republished.
Old packages:

azure-pipelines-tasks-msbuildhelpers
azure-pipelines-tasks-packaging-common
azure-pipelines-tasks-webdeployment-common
azure-pipelines-tasks-azurermdeploycommon

Republished packages:

azure-pipelines-tasks-msbuildhelpers-v3
azure-pipelines-tasks-packaging-common-v3
azure-pipelines-tasks-azurermdeploycommon-v3
azure-pipelines-tasks-webdeployment-common-v4

We have to update all tasks depending on these packages. Here is the list of them.

msbuildhelpers-v3

XamariniOSV2

packaging-common-v3

DotNetCoreCLIV2
DownloadPackageV0
DownloadPackageV1
MavenV2
MavenV3
NpmV0
NpmV1
UseDotNetV2
UseNodeV1

azurermdeploycommon-v3

AzureAppServiceSettingsV1
AzureFunctionAppContainerV1
AzureFunctionAppV1
AzureWebAppContainerV1
AzureWebAppV1

webdeployment-common-v4

AzureMysqlDeploymentV1
AzureRmWebAppDeploymentV4
FileTransformV1
FileTransformV2
IISWebAppDeploymentOnMachineGroupV0
MysqlDeploymentOnMachineGroupV1

Documentation changes required: No
Added unit tests: No
Attached related issue
Checklist:

[ ] Task version was bumped - please check instruction how to do it
[ ] Checked that applied changes work as expected

For these tasks (with updated republished common npm packages) unit-tests are failed locally:

AzureMysqlDeploymentV1
AzureRmWebAppDeploymentV4
IISWebAppDeploymentOnMachineGroupV0
MysqlDeploymentOnMachineGroupV1

For some tasks (with updated republished common npm packages) the CI is failed.
Examples of such tasks: DotNetCoreCLIV2 and MavenV2, maybe some other tasks.

For these tasks (with updated republished common npm packages) the CI is failed, so they have been restored:

DotNetCoreCLIV2
MavenV2
MavenV3
NpmV1

MavenV2, MavenV3, and XamariniOSV2 tasks have been moved to the separate pull request.

Hi @rvairavelu, @rohit-batra, could you please review this PR and test the DotNetCoreCLIV2 and UseDotNetV2 tasks (since they are in your ownership) to make sure they are working properly after the applied changes?

Hi @phil-hodgson, @aasim, @satbai, could you please review this PR and test these tasks (since they are in your ownership):

DownloadPackageV0
DownloadPackageV1
NpmV0
NpmV1

to make sure they are working properly after the applied changes?

Hi @vsebesta, @rvairavelu, @microsoft/pipeline-environment-team.
Could you please review this PR and test these tasks (since they are in your ownership):

AzureAppServiceSettingsV1
AzureFunctionAppContainerV1
AzureFunctionAppV1
AzureWebAppContainerV1
AzureWebAppV1
AzureMysqlDeploymentV1
AzureRmWebAppDeploymentV4
FileTransformV1
FileTransformV2
IISWebAppDeploymentOnMachineGroupV0
MysqlDeploymentOnMachineGroupV1

to make sure they are working properly after the applied changes?

@DenisRumyantsev  We have validated the below task

AzureAppServiceSettingsV1
AzureFunctionAppContainerV1
AzureFunctionAppV1
AzureWebAppContainerV1
AzureWebAppV1
AzureMysqlDeploymentV1
AzureRmWebAppDeploymentV4
FileTransformV1
FileTransformV2
IISWebAppDeploymentOnMachineGroupV0
MysqlDeploymentOnMachineGroupV1
UseDotNetV2

They are working fine. But we can see some other tasks which are not owned by Us. May i know how could we proceed with PR Approval as it involve multiple team tasks?


Make highlight group matching case insensitive when disabling

I am using this plugin with Neovim and for some reason the matching groups when they are added are being added as HighlightURL instead of HighlightUrl so the case sensitivity breaks the disable function. Could we possibly make the checking here case insensitive for this situation?
Resolves #6

This needs more explanation. Who converts the cases?

I'm not sure, I have made no modification to the plugin and when I open Neovim and do :echo getmatches() I see a group added with the group name "HighlightURL". I can't find anywhere where the plugin would be setting it to HighlightURL with all caps on the URL but it is there anyway. I'm not sure if this is an issue with Neovim or not but this discrepancy breaks the disable function in Neovim.

Actually don't worry about making this change. I did some more testing and I can't justify why that is being renamed to all caps. I ended up just doing a reimplementation in lua for Neovim anyway so this PR is no longer necessary plus not a very good practice to drop the case sensitivity.


Enable/Disable Camera

Hi, when i load the libcocos2dcpp.so to turn off the camera movement, after that i replace it with the modified one in the apk. I tried to play an april fools song, it still have the camera movement. Do you have any idea why?

hmm can you try to use original libcocos2dcpp with arcaeamodder and disable all the tick, to see if the camera works? After that if it doesn't works, try to use arcaeamodder to enable the camera and then disable it again to see if it's still happened

anyways, which side of it (Android or iOS)

I dont have a fresh libcocos2dcpp.so :/
I don't know if the Ios side have it since i mainly on Android side.

Ok so, i just try another chart with a green arc in it. It doesn't show the green arc, instead it show the red arc. It's my mistake. Sorry the inconvenience!


Have completed the basic ui for notes taking page.

issue number #10

issue #11

#11 read button

@thejasveer Will require a new pull request as discussed.


Pool avax pangolin lost avax

feature for support Pool avax pangolin LOST-AVAX

@FuntasticMrFox strategy owner is incorrect, you've transferred it to the vault timelock instead of strategy timelock. I'll put forward a multi-sig tx to get that transferred. Vault owner is not transferred yet, please confirm addresses in the address book of the API and tranfer ownership of vault

@sircryptomaxi sorry about that, i transfered ownership of vault https://snowtrace.io/tx/0x7954e4dc1098921da9932afbad3a7038f5b509bdb673e81a5525013209e244c6. Thank you to put a forward a multisig tx.

seems wrong rewardToOutput route, it swaps to native

seems wrong rewardToOutput route, it swaps to native

Fixed


Unable to install spacy

Type: Bug
Getting the following error:
command : pip install spacy
Collecting spacy
Using cached spacy-3.8.2.tar.gz (1.3 MB)
Installing build dependencies ... error
error: subprocess-exited-with-error
× pip subprocess to install build dependencies did not run successfully.
│ exit code: 1
╰─> [106 lines of output]
Ignoring numpy: markers 'python_version < "3.9"' don't match your environment
Collecting setuptools
Using cached setuptools-75.3.0-py3-none-any.whl.metadata (6.9 kB)
Collecting cython<3.0,>=0.25
Using cached Cython-0.29.37-py2.py3-none-any.whl.metadata (3.1 kB)
Collecting cymem<2.1.0,>=2.0.2
Using cached cymem-2.0.8-cp313-cp313-win_amd64.whl
Collecting preshed<3.1.0,>=3.0.2
Using cached preshed-3.0.9.tar.gz (14 kB)
Installing build dependencies: started
Installing build dependencies: finished with status 'done'
Getting requirements to build wheel: started
Getting requirements to build wheel: finished with status 'done'
Preparing metadata (pyproject.toml): started
Preparing metadata (pyproject.toml): finished with status 'done'
Collecting murmurhash<1.1.0,>=0.28.0
Using cached murmurhash-1.0.10-cp313-cp313-win_amd64.whl
Collecting thinc<8.4.0,>=8.3.0
Using cached thinc-8.3.2.tar.gz (193 kB)
Installing build dependencies: started
Installing build dependencies: still running...
Installing build dependencies: finished with status 'error'
error: subprocess-exited-with-error
    Ã— pip subprocess to install build dependencies did not run successfully.
    â”‚ exit code: 1
    â•°â”€> [69 lines of output]
        Ignoring numpy: markers 'python_version < "3.9"' don't match your environment
        Collecting setuptools
          Using cached setuptools-75.3.0-py3-none-any.whl.metadata (6.9 kB)
        Collecting cython<3.0,>=0.25
          Using cached Cython-0.29.37-py2.py3-none-any.whl.metadata (3.1 kB)
        Collecting murmurhash<1.1.0,>=1.0.2
          Using cached murmurhash-1.0.10-cp313-cp313-win_amd64.whl
        Collecting cymem<2.1.0,>=2.0.2
          Using cached cymem-2.0.8-cp313-cp313-win_amd64.whl
        Collecting preshed<3.1.0,>=3.0.2
          Using cached preshed-3.0.9.tar.gz (14 kB)
          Installing build dependencies: started
          Installing build dependencies: finished with status 'done'
          Getting requirements to build wheel: started
          Getting requirements to build wheel: finished with status 'done'
          Preparing metadata (pyproject.toml): started
          Preparing metadata (pyproject.toml): finished with status 'done'
        Collecting blis<1.1.0,>=1.0.0
          Using cached blis-1.0.1.tar.gz (3.6 MB)
          Installing build dependencies: started
          Installing build dependencies: finished with status 'done'
          Getting requirements to build wheel: started
          Getting requirements to build wheel: finished with status 'done'
          Preparing metadata (pyproject.toml): started
          Preparing metadata (pyproject.toml): finished with status 'done'
        Collecting numpy<2.1.0,>=2.0.0
          Using cached numpy-2.0.2.tar.gz (18.9 MB)
          Installing build dependencies: started
          Installing build dependencies: finished with status 'done'
          Getting requirements to build wheel: started
          Getting requirements to build wheel: finished with status 'done'
          Installing backend dependencies: started
          Installing backend dependencies: finished with status 'done'
          Preparing metadata (pyproject.toml): started
          Preparing metadata (pyproject.toml): finished with status 'error'
          error: subprocess-exited-with-error

          Ãƒâ€” Preparing metadata (pyproject.toml) did not run successfully.
          Ã¢â€\x9dâ€š exit code: 1
          Ã¢â€¢Â°Ã¢â€\x9dâ‚¬> [19 lines of output]
              + C:\Users\Nehadiya Saman\Desktop\try\venv\Scripts\python.exe C:\Users\Nehadiya Saman\AppData\Local\Temp\pip-install-0x2m6w93\numpy_606679a85eb54bbca84989a04105a587\vendored-meson\meson\meson.py setup C:\Users\Nehadiya Saman\AppData\Local\Temp\pip-install-0x2m6w93\numpy_606679a85eb54bbca84989a04105a587 C:\Users\Nehadiya Saman\AppData\Local\Temp\pip-install-0x2m6w93\numpy_606679a85eb54bbca84989a04105a587\.mesonpy-w04uxt8p -Dbuildtype=release -Db_ndebug=if-release -Db_vscrt=md --native-file=C:\Users\Nehadiya Saman\AppData\Local\Temp\pip-install-0x2m6w93\numpy_606679a85eb54bbca84989a04105a587\.mesonpy-w04uxt8p\meson-python-native-file.ini
              The Meson build system
              Version: 1.4.99
              Source dir: C:\Users\Nehadiya Saman\AppData\Local\Temp\pip-install-0x2m6w93\numpy_606679a85eb54bbca84989a04105a587
              Build dir: C:\Users\Nehadiya Saman\AppData\Local\Temp\pip-install-0x2m6w93\numpy_606679a85eb54bbca84989a04105a587\.mesonpy-w04uxt8p
              Build type: native build
              Project name: NumPy
              Project version: 2.0.2
              C compiler for the host machine: gcc (gcc 6.3.0 "gcc (MinGW.org GCC-6.3.0-1) 6.3.0")
              C linker for the host machine: gcc ld.bfd 2.28
              C++ compiler for the host machine: c++ (gcc 6.3.0 "c++ (MinGW.org GCC-6.3.0-1) 6.3.0")
              C++ linker for the host machine: c++ ld.bfd 2.28
              Cython compiler for the host machine: cython (cython 3.0.11)
              Host machine cpu family: x86
              Host machine cpu: x86

              ..\meson.build:28:4: ERROR: Problem encountered: NumPy requires GCC >= 8.4

              A full log can be found at C:\Users\Nehadiya Saman\AppData\Local\Temp\pip-install-0x2m6w93\numpy_606679a85eb54bbca84989a04105a587\.mesonpy-w04uxt8p\meson-logs\meson-log.txt
              [end of output]

          note: This error originates from a subprocess, and is likely not a problem with pip.
        error: metadata-generation-failed

        Ãƒâ€” Encountered error while generating package metadata.
        Ã¢â€¢Â°Ã¢â€\x9dâ‚¬> See above for output.

        note: This is an issue with the package mentioned above, not pip.
        hint: See above for details.
        [end of output]

    note: This error originates from a subprocess, and is likely not a problem with pip.
  error: subprocess-exited-with-error

  Ã— pip subprocess to install build dependencies did not run successfully.
  â”‚ exit code: 1
  â•°â”€> See above for output.

  note: This error originates from a subprocess, and is likely not a problem with pip.
  [end of output]

note: This error originates from a subprocess, and is likely not a problem with pip.
error: subprocess-exited-with-error
× pip subprocess to install build dependencies did not run successfully.
│ exit code: 1
╰─> See above for output.
note: This error originates from a subprocess, and is likely not a problem with pip.

These errors are not related to VS Code and are related to something else.


Change connection preferrence so it tries with WS first and the polling

@xetorthio I can't get to run PWD locally, but after checking some other stuff I believe this should work. Can u plz check?

@xetorthio also reverted to 1.13 overlay networks and fixed some other stuff. It works locally now, so please try.


Retention policy is applied 5 hour too early for ToDay keys.

Unexpected behavior
At 01.10.2020 00:05 German time the hour file for 17.09.2020 contains
[3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23]
that indicates the fist time a user uploads keys on 17.09.2020 or keys changed was in the UTC interval 03:00-04:00.
So the next retention run is expected at 05:00 German time on 01.10.2020.
But the next run was earlier.
At 01.10.2020 03:00 German time and the file then contains
[5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23]
The run-time 03:00 German time indicates that some keys were also uploaded/changed in the UTC interval 01:00-02:00.
The now missing 3,4 indicate there was no key-upload/change during UTC interval 03:00-04:00 and 04:00-05:00
This is at odds with the first observation.
This is the one an only time I saw such a behavior

The the overnight retentions make thinks a little bit clearer.
(for 06.10.2020 we have not-empty hour files for 0,3,5-18,20,21)
At 06.10.2020 2:00 German Time the hour-date for 2020-09-22 file shows:
[1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23]
indicating users upload keys at 2020-09-22 in the UTC time 01:00-02:00
At 06.10.2020 3:00 German Time the hour-date for 2020-09-22 file shows:
[2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23]
indicating users also upload keys at 2020-09-22 in the UTC time 02:00-03:00
At 06.10.2020 4:00 German Time the hour-date for 2020-09-22 file shows:
[4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23]
indicating no users upload keys at 2020-09-22 in the UTC time 03:00-04:00
How could that be?
I assume the following:
The keys that have been published in the 2020-09-22-hour-03.zip file
belong to 2 categories:
A. they were uploaded in the time interval  01:00-03:00
B. they were uploaded on 21.09. But as ToDay-key they were shifted to the 2020-09-22-hour-03.zip file
The keys from category B had been remove at 2020-10-06 01:00 with all other keys uploaded on  2020-09-21.
But how to explain the observation in the 1. post?
The keys for 2020-09-16 do not show a missing "6", which does not imply there is no ToDay key,
it only says the uploaded keys can be explained without a missing "6",
but there could be at least one user that only upload a single ToDay key, which was shifted to 2020-09-17 hour 03
and published in the 2020-09-17-hour-06.zip file.
At 01.10.2020 00:05 German time the hour file for 17.09.2020 contains
[3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23]
and shows there are keys for 03:00
The keys from category B had been remove one hour later at 2020-10-01 01:00 with all other keys uploaded on 2020-09-16.
so the 01.10.2020 3:00 German time file does not contain them any more.
(Hopefully I haven't missed myself too often with all the dates and times.)
Conclusion:
If keys are shifted to the 03 hour file next day they should be deleted at 05:00 German time after 13d 23h or correctly at 06:00 German time.

if #856 and #700 are solved this issue in also solved.

if #856 and #700 are solved this issue in also solved.

This is not totally true.
If users have a wrong device time like the assumption for #723, those keys will still be shifted to 03h next day.
So https://github.com/corona-warn-app/cwa-app-ios/issues/1097 has to be fixed also.


Admin and Managed Servers Not Starting

The Admin server and Managed Servers are continually failing to start and showing only the following entry (with slight variations in directory and file name) in each the pod's log. I'm running Docker/K8S on MacOS using Docker-edge.
failed to open log file "/var/log/pods/bc42ce99-1bd8-11e8-9d6b-025000000001/weblogic-server_17.log": open /var/log/pods/bc42ce99-1bd8-11e8-9d6b-025000000001/weblogic-server_17.log: no such file or directory
Any advice is appreciated.

Can you please tell us about the persistent volume you configured?  Did the domain creation job run successfully?  The directory behind the persistent volume (host path) has to be chmod 777 accessible since the WebLogic pods will run as user = "weblogic", which I believe is uid=1000.

Yes, the domain creation job ran successfully - a visual inspection of what was created shows that things look correct.
The persistent volume is under /Users//k8s_dir. Under there I have persistentVolume001 and persistentVolume002. Everything is 777.
I did previously have a problem where I wasn't creating the volume under /Users and then noticed the note that this was a problem for a MacOS Docker/K8S setup. This was giving an error even creating the domain. Once I moved it under /Users then domain creation worked, but then lead to this error when the servers try to startup.

I've heard that it's fairly common on a mac that the vm memory allocation needs to be increased.

@bdueck, has the issue been resolved?


Fix flaky interactive query tests

The actual fix of the flakiness: we need to include the comparison of the expected result with the actual result into the waitForCondition as well to allow retries. Before that we only wait for the query to return the expected number of entries, but not all entries have been updated to date.

Cleanup: on the two interactivequeries tests, we have duplicated tests one for host = localhost and one for host = <IP_ADDRESS> just to test that any valid host should work. I've consolidated them to generate a random valid host each time.

@vvcephei @mjsax for reviews.

@vvcephei @mjsax updated per comments.


Issue #122 Dead links in che addon

Hi @l0rd, @garagatyi, this PR fixes dead links in Che addon readme and addon files, please take a look to confirm that new links points to correct place at documentation.


TTY Not Detected stdin

Describe the bug
It looks like TTY is not identified with stdin.
Kool version and environment
C:\Workspace\mega-bilheteria\portal-api>kool info
KOOL_ASUSER=0
KOOL_GLOBAL_NETWORK=kool_global
KOOL_NAME=portal-api
KOOL_VERBOSE=1

C:\Workspace\mega-bilheteria\portal-api>kool --version
kool version 1.4.0

To Reproduce
kool.yml
scripts:
  pg_restore : kool exec -e PGPASSWORD=$DB_PASSWORD database pg_restore -U $DB_USERNAME --dbname=$DB_DATABASE --verbose

Execute command:
kool run pg_restore < C:\Workspace\file-dump.tar
Expected behavior
Execute the pg_restore with a dump file.
Screenshots

@fbrissi thanks for the report! we will look into this.
Meanwhile, a quick work around would be: if you define the input file redirection < within your kool.yml file that should work as kool itself will handle the input:
scripts:
  pg_restore : kool exec -e PGPASSWORD=$DB_PASSWORD database pg_restore -U $DB_USERNAME --dbname=$DB_DATABASE --verbose
  pg_restore_file: kool run pg_restore < path\to\file.tar

Something like this.


[Asset] Add quickstart sample code for BatchGetAsstesHistory.

Fixes #<issue_number_goes_here> (it's a good idea to open an issue first for discussion)

[ ] Tests and linter pass
[ ] Code coverage does not decrease (if any source code was changed)
[ ] Appropriate docs were updated (if necessary)

Looks like ES6 style format doesn't work with the env...

I'm not sure what you mean?  It works great :)  What specifically isn't working for you?

Maybe it's my dev env config issue... I tried running the test on my local machine with the formatted string output to console, and see the string was not correctly formatted.

Can you run 'npm run fix'?

Edited file .eslintrc.yml to allow dependency on unpublished package nodejs-repo-tools.

Can you run 'npm run fix'?

Lint is not complaining now.

Can you share the output of npm run fix after fixing the stuff above?

$ npm run fix

<EMAIL_ADDRESS>fix ~/github/nodejs-asset
eslint --fix '**/*.js'


fix: doc

I suppose it's the cargo build --release to be executed before the strip -s target/release/xxx command.

Sure, your suggestion is reasonable. Thank you!


Switch to using PackageLicenseExpression

NuGet.org will then be able to show the correct license info and also automatic license checkers/validator will work properly. Also updates GH Actions workflow definition to do a deterministic build and cleaned up against the latest runners which don't need installations. Explicit System.Text.Json reference should also not be needed when you target net6.0.
Have you considered to make the big 1.0 release yet - this is working great! 🙂

Thanks @lahma, I've merged in your changes and created 1.0.0-alpha4.
We ended up moving away from C# code for our Lokalise integration to TypeScript, so I've not needed to progress this any more. I may see if Lokalise want to adopt / progress the repo at some point.

OK, thank you for merging, releasing a new version and giving an update. This library has been quite useful and solid!


Would be useful to restrict serialization/deserialization with gson @Expose annotation

We conditionally expose fields in our models with the @Expose annotation.  GsonBuilder can be configured to recognize.  Is there a plan to enable this feature with auto-value-gson extension?
public class MyModel {
   private long doNotExpose;
  @Expose @SerializedName("expose_me") private long exposeMe;
...
}

final Gson gson = new GsonBuilder()
   .excludeFieldsWithoutExposeAnnotation()
...
   .create();

This will be taken care of when #18 is solved.

@rharter If you have to guess....when do you think this is "solved"?

Just waiting on a PR in the gson repo to be released.  It just got merged, so shouldn't be too long.

@rharter Thanks for answer. I was a bit afraid because it is a PR of google/auto........


feat: add customtable

CustomTable is a debatable name :D

@bjornlexell I realize we need to enforce having React in scope again, to support React 16. So I added this: https://github.com/einride/ui/pull/99
Let's merge https://github.com/einride/ui/pull/99, then resolve conflicts here and ensure linting is ok, and I'll review again. :)

@bjornlexell I realize we need to enforce having React in scope again, to support React 16. So I added this: #99
Let's merge #99, then resolve conflicts here and ensure linting is ok, and I'll review again. :)

Sounds like a great idea to add an error for that rule (obv... since I forgot it in the first PR after adding support for reat 16)


Allow to load GraphQL erb templates outside of repo

This allows to make GraphQL erb(model_type.erb, query_type.erb, schema.erb) templates configurable in repo(For example in sources-api) where is insights-api-common-rails gem used and
templates live in location  ./api/common/graphql/templates in remote repos.
Example: So if you want override GraphQL schema for source-api, you
need to create file in source-api repo like is this PR.
Links
Together with TOPO PR and Sources PR fixes: https://issues.redhat.com/browse/RHCLOUD-11179 and disables GraphQL introspection  in source/topo  APIs.

Would we want a spec ( or maybe we have on in the API repos ) that proves introspection doesn't work when the disable_introspection_entry_points config value is set?

yes, that's right and now I added also this case to specs,
thanks @syncrou!


Release 2017.08

This is a placeholder Pull Request for the upcoming 2017.08 release. The main feature of this release is the Web UI (shown below).

Coverage decreased (-1.0%) to 71.088% when pulling 169bbadd6f941c2bb702f0530b5991ab2bcf07b8 on develop into 0a957152b253e36023ce8fe76ea2dcc88f64537f on master.

Coverage decreased (-1.0%) to 71.088% when pulling 0397ecb0c407718fd3d3f3d028bdb18829ba3e79 on develop into 0a957152b253e36023ce8fe76ea2dcc88f64537f on master.


Tab Display

This is my fix for the issue of tabs not displaying in UmpleOnline when viewing individual files. The problem was that each class file was added to a <div> on the page only when the next class was found, meaning the last class would be dropped as there is no next class after the final one.
The fix involves just re-ordering the logic so that each line in the full file is added to the <div> as it's processed, instead of adding the whole class once the next one is found.

Can you please confirm that you have generated every possible type of generated output in cases where there is a) Just 1 class, and b) two or more classes. There were lots of little cases before; I would prefer to get your confirmation that you have done all this testing before doing a test, or having someone else do it. The student who worked on this before tended not do test all the output types (there are many). Also some output types don't generated on a 'per class' basis at all, so there have been problems with those. And some output types generate an extra class or two to support the compilation (I think cpp does that in some cases).

Alrighty. I've thoughroughly tested the results both in my local UmpleOnline (with the fix) and UmpleOnline on Cruise.
Cases where the user can tabulate files are when generating code for the following languages:

Java
PHP
C++
Ruby
SQL

For all but C++, one file is generated for each class. On Cruise, the generated code consistently returns no tabs at all when generating a model with a single class. On my local UmpleOnline, the single tab pops up as it should. For models that generate multiple files, Cruise fails to display a tab for the last file generated, but the rest display fine and work as expected.
C++ is a bit of a different case because it generates it's own files on top of the .cpp and .h files for each class in the model. In both cases for single classes and multiple classes, the tab for the last file is not displayed in Cruise's UmpleOnline. This case works normally for both cases on my local instance with the fix.
I've tested to see differences for the other generation targets even though they didn't have any tab display enabled, and found no difference in both single- and multiple-class tests.
Looks good!

I merged it. There is a separate process to test it on the UmpleOnline server at http://try.umple.org/test which I will do after a build runs there, so be patient for it to appear live. Good job!

Can we close this issue Tim?
It's good to close it if it's been fixed :-)

This is a PR. The issue is 650 and it is closed!


Create WinGet package for October 2023 GDK Update 1

Create WinGet package for October 2023 GDK Update 1
Tested locally with winget validate and winget install
Microsoft Reviewers: Open in CodeFlow

@microsoft/xbox-developer-experience-toolbox for review

LGTM.


LD_PRELOAD libamirstan_plugin.so core dump in triton server

Describe the bug
LD_PRELOAD libamirstan_plugin.so core dump in triton server
triton server,tensorrt and other software version: 20.03
the problem is similar with https://github.com/triton-inference-server/server/issues/2227
I tried loading the shared library with trtexec directly as mentioned by CoderHam, core dumped too.
Did a search in tensorRT issue,
no hit.
so it is a build issue?
thanks!

@tianq01
check the position,  make sure the LD_PRELOAD position befor the docker image, not   tritonserver
--env  LD_PRELOAD=/models/libamirstan_plugin.so  nvcr.io/nvidia/tritonserver:20.03.1-py3    tritonserver

@tianq01
check the position, make sure the LD_PRELOAD position befor the docker image, not tritonserver
--env LD_PRELOAD=/models/libamirstan_plugin.so nvcr.io/nvidia/tritonserver:20.03.1-py3 tritonserver

@Chen-cyw thanks for quick reply.
I tried below command:
nvidia-docker run --rm --shm-size=1g --ulimit memlock=-1 --ulimit stack=67108864 --env LD_PRELOAD=/models/libamirstan_plugin.so -p 8800:8000 -p 8801:8001 -p 8802:8002 -v /data/model_repository:/models nvcr.io/nvidia/tritonserver:20.03-py3 trtserver --model-repository=/models --strict-model-config=false --log-verbose=1
the docker fails to start without any explict error info,  looks like core dumps.
any problem with the command?

Hi @grimoire ,
we did run the converted model successfully via below python code as described in README:
trt_model = init_detector(save_path) num_detections, trt_bbox, trt_score, trt_cls = inference_detector(trt_model, image_path, cfg_path, "cuda:0")
Did you test running the egnine with trtexec -loadEngine?
thanks.

@tianq01  can you run the docker image without  start trtserver?  before run with docker , try with your local env like  https://github.com/grimoire/mmdetection-to-tensorrt/issues/33

Hi @Chen-cyw
the url cannot be opened.

@tianq01   copy  and paste  on the chrome ,not click
I have successed to convert the  mmdetection  bbox model  to trt model and run in  trtexec and tritonserver(20.03)

@tianq01 copy and paste on the chrome ,not click
I have successed to convert the mmdetection bbox model to trt model and run in trtexec and tritonserver(20.03)

missed this post.
@Chen-cyw thanks a lot!  will try.

the problem got resolved after upgrading to latest code.
closed.

the problem got resolved after upgrading to latest code.
closed.

@tianq01 Hi, can you provide some detail about how to deploy mmdet trt engine with triton-inference-server?
I've converted the trt engine file from mmdet model with docker container CLI:
mmdet2trt --fp16 cascade_rcnn_s101_fpn_syncbn-backbone+head_mstrain-range_1x_coco_fp16.py epoch_5.pth output.trt

So I got output.trt model file. And then I created the following directories to place my model:
models
    ├── big_model
    │   └── 1
    │       └── model.plan  # (rename from output.trt)
    └── libamirstan_plugin.so

and then want to deploy it with tritonserver:
docker run --rm --gpus device=3 --shm-size=1g --ulimit memlock=-1 --ulimit stack=67108864 \
  --env LD_PRELOAD=/models/libamirstan_plugin.so -p 8800:8000 -p 8801:8001 -p 8802:8002 \
  -v $(pwd):/models nvcr.io/nvidia/tritonserver:20.08-py3 \
  tritonserver --model-repository=/models --strict-model-config=false --log-verbose=1

However it cannot load the model:
=============================
== Triton Inference Server ==
=============================

NVIDIA Release 20.08 (build 15533555)

Copyright (c) 2018-2020, NVIDIA CORPORATION.  All rights reserved.

Various files include modifications (c) NVIDIA CORPORATION.  All rights reserved.
NVIDIA modifications are covered by the license terms that apply to the underlying
project or file.

I0224 07:22:55.402466 1 metrics.cc:184] found 1 GPUs supporting NVML metrics
I0224 07:22:55.408652 1 metrics.cc:193]   GPU 0: GeForce RTX 2080 Ti
I0224 07:22:55.409009 1 server.cc:119] Initializing Triton Inference Server
I0224 07:22:55.850319 1 pinned_memory_manager.cc:195] Pinned memory pool is created at '0x7f13f6000000' with size 268435456
I0224 07:22:55.852497 1 netdef_backend_factory.cc:46] Create NetDefBackendFactory
I0224 07:22:55.852517 1 plan_backend_factory.cc:48] Create PlanBackendFactory
I0224 07:22:55.852523 1 plan_backend_factory.cc:55] Registering TensorRT Plugins
I0224 07:22:55.852566 1 logging.cc:52] Registered plugin creator - ::BatchTilePlugin_TRT version 1
I0224 07:22:55.852579 1 logging.cc:52] Registered plugin creator - ::BatchedNMS_TRT version 1
I0224 07:22:55.852600 1 logging.cc:52] Registered plugin creator - ::CoordConvAC version 1
I0224 07:22:55.852638 1 logging.cc:52] Registered plugin creator - ::CropAndResize version 1
I0224 07:22:55.852645 1 logging.cc:52] Registered plugin creator - ::DetectionLayer_TRT version 1
I0224 07:22:55.852653 1 logging.cc:52] Registered plugin creator - ::FlattenConcat_TRT version 1
I0224 07:22:55.852660 1 logging.cc:52] Registered plugin creator - ::GenerateDetection_TRT version 1
I0224 07:22:55.852671 1 logging.cc:52] Registered plugin creator - ::GridAnchor_TRT version 1
I0224 07:22:55.852683 1 logging.cc:52] Registered plugin creator - ::GridAnchorRect_TRT version 1
I0224 07:22:55.852709 1 logging.cc:52] Registered plugin creator - ::InstanceNormalization_TRT version 1
I0224 07:22:55.852716 1 logging.cc:52] Registered plugin creator - ::LReLU_TRT version 1
I0224 07:22:55.852723 1 logging.cc:52] Registered plugin creator - ::MultilevelCropAndResize_TRT version 1
I0224 07:22:55.852734 1 logging.cc:52] Registered plugin creator - ::MultilevelProposeROI_TRT version 1
I0224 07:22:55.852742 1 logging.cc:52] Registered plugin creator - ::NMS_TRT version 1
I0224 07:22:55.852749 1 logging.cc:52] Registered plugin creator - ::Normalize_TRT version 1
I0224 07:22:55.852757 1 logging.cc:52] Registered plugin creator - ::PriorBox_TRT version 1
I0224 07:22:55.852765 1 logging.cc:52] Registered plugin creator - ::ProposalLayer_TRT version 1
I0224 07:22:55.852772 1 logging.cc:52] Registered plugin creator - ::Proposal version 1
I0224 07:22:55.852779 1 logging.cc:52] Registered plugin creator - ::PyramidROIAlign_TRT version 1
I0224 07:22:55.852785 1 logging.cc:52] Registered plugin creator - ::Region_TRT version 1
I0224 07:22:55.852793 1 logging.cc:52] Registered plugin creator - ::Reorg_TRT version 1
I0224 07:22:55.852802 1 logging.cc:52] Registered plugin creator - ::ResizeNearest_TRT version 1
I0224 07:22:55.852810 1 logging.cc:52] Registered plugin creator - ::RPROI_TRT version 1
I0224 07:22:55.852816 1 logging.cc:52] Registered plugin creator - ::SpecialSlice_TRT version 1
I0224 07:22:55.852828 1 onnx_backend_factory.cc:53] Create OnnxBackendFactory
I0224 07:22:55.860046 1 libtorch_backend_factory.cc:53] Create LibTorchBackendFactory
I0224 07:22:55.860167 1 custom_backend_factory.cc:46] Create CustomBackendFactory
I0224 07:22:55.860172 1 backend_factory.h:44] Create TritonBackendFactory
I0224 07:22:55.860203 1 ensemble_backend_factory.cc:47] Create EnsembleBackendFactory
I0224 07:22:55.860364 1 autofill.cc:142] TensorFlow SavedModel autofill: Internal: unable to autofill for 'big_model', unable to find savedmodel directory named 'model.savedmodel'
I0224 07:22:55.860396 1 autofill.cc:155] TensorFlow GraphDef autofill: Internal: unable to autofill for 'big_model', unable to find graphdef file named 'model.graphdef'
I0224 07:22:55.860420 1 autofill.cc:168] PyTorch autofill: Internal: unable to autofill for 'big_model', unable to find PyTorch file named 'model.pt'
I0224 07:22:55.860450 1 autofill.cc:180] Caffe2 NetDef autofill: Internal: unable to autofill for 'big_model', unable to find netdef files: 'model.netdef' and 'init_model.netdef'
I0224 07:22:56.123378 1 autofill.cc:376] failed to load /models/big_model/1/model.plan: Internal: onnx runtime error 1: /workspace/onnxruntime/onnxruntime/core/session/inference_session.cc:279 onnxruntime::InferenceSession::InferenceSession(const onnxruntime::SessionOptions&, const onnxruntime::Environment&, const void*, int) result was false. Could not parse model successfully while constructing the inference session

I0224 07:22:56.123459 1 autofill.cc:212] ONNX autofill: Internal: unable to autofill for 'big_model', unable to find onnx file
WARNING: Since openmp is enabled in this build, this API cannot be used to configure intra op num threads. Please use the openmp environment variables to control the number of threads.
E0224 07:23:19.480148 1 logging.cc:43] coreReadArchive.cpp (38) - Serialization Error in verifyHeader: 0 (Version tag does not match)
E0224 07:23:19.516318 1 logging.cc:43] INVALID_STATE: std::exception
E0224 07:23:19.516344 1 logging.cc:43] INVALID_CONFIG: Deserialize the cuda engine failed.
I0224 07:23:19.548534 1 autofill.cc:225] TensorRT autofill: Internal: unable to autofill for 'big_model', unable to find a compatible plan file.
W0224 07:23:19.548552 1 autofill.cc:265] Proceeding with simple config for now
I0224 07:23:19.548576 1 model_config_utils.cc:629] autofilled config: name: "big_model"

E0224 07:23:19.558529 1 model_repository_manager.cc:1633] unexpected platform type  for big_model
error: creating server: Internal - failed to load all models

Can you share your procedure please? Thank you.


couple of enhancements for man.vim

g:ft_man_open_mode to be able open man pages in vert split or separate
tab
set nomodifiable for buffer with man content

g:ft_man_open_mode to be able open man pages in vert split or separate
tab

set nomodifiable for buffer with man content
You can view, comment on, or merge this pull request online at:
https://github.com/vim/vim/pull/873

-- Commit Summary --

couple of enhancements for man.vim

-- File Changes --
M runtime/ftplugin/man.vim (15)

-- Patch Links --
https://github.com/vim/vim/pull/873.patch
https://github.com/vim/vim/pull/873.diff

CC'ing the maintainer.
--
hundred-and-one symptoms of being an internet addict:
104. When people ask about the Presidential Election you ask "Which country?"
/// Bram Moolenaar --<EMAIL_ADDRESS>-- http://www.Moolenaar.net   \
///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \
\\  an exciting new programming language -- http://www.Zimbu.org        ///
\\            help me help AIDS victims -- http://ICCF-Holland.org    ///


Keep code after page reload

Should avoid that (inexerienced or experienced whatsoever) programmers loose their code after a page reload.

This will only be available in the standalone-version, as it does not sound like expected behaviour in projects using Papyros (such as Dodona)

Yes, with likely a listener attached to the editor to update the value in localStorage every so often to not cost too much processing.


Update Composer dependencies (2024-12-28-00-11)

Visual regression test passed!
View the visual regression test report


Displaying line numbers in writeroom-mode kills left margin.

When inside writeroom-mode, enabling the line numbers (linum-mode) kills the left margin completely, so that the text is not centered anymore. Re-enabling writeroom-mode fixes the margin, but hides the line numbers again.
Disclaimer: New to emacs. Using spacemacs. Havn't tried with vanilla emacs.

Hi, sorry for the late reply (I was on vacation).
linum-mode has its own ideas about the width of the window margins. There's not much that writeroom-mode can do about that, except to note that the two aren't really compatible.
The only solution I can see is if linum-mode would respect the existing margin widths. But I have no idea if that is possible or not.
Sorry I can't be of more help.

I just noticed that nlinum-mode (available from ELPA; I have no idea how it can be installed / used in Spacemacs, though) behaves better in this respect. It's still not perfect, but it's usable. Two remaining problems that I've noticed:

when nlinum-mode needs more space for line numbers (e.g., when line 100 is reached), the left margin disappears again, but this can be fixed by switching to another buffer and back again, or by splitting and unsplitting the window. Not perfect, but a livable work-around. This shouldn't be necessary very often, BTW.

2), when writeroom-mode is disabled, the line numbers disappear completely, even though nlinum-mode is still active. It needs to be disabled and reenabled to make the line numbers appear again. This is probably a bug in writeroom-mode which I'll try to fix ASAP.

Would it be possible to adapt whiteroom-mode to not have the columns added by display-line-numbers-mode (included with Emacs 26) contribute towards the line length?
In other words, would it be possible to specify that whiteroom-mode should have, say, 80 characters long lines, excluding any characters added by display-line-numbers-mode?
Thanks!

In other words, would it be possible to specify that whiteroom-mode should have, say, 80 characters long lines, excluding any characters added by display-line-numbers-mode?

I just pushed an update to visual-fill-column-mode that should do that.


MB-10909: Service Counselor and TXO users can add/edit delivery address to NTS-release shipments

Jira tickets for this change: MB-10909, MB-11607
Summary
This pull request fixes an issue where office users (Service counselors, TIO, and TOO) were unable to add or edit a shipment's delivery address for an NTS-release shipment. This bug stemmed from changes made to remove the two-button "Does the customer know their delivery address" prompt for NTS-release shipments, as users should be unable to create an NTS-release shipment without knowing the destination. Previously, the bug prevented the delivery address from being sent to the backend whenever a shipment was added or edited; this resolves that bug and correctly sends the delivery address to be updated in the database.
This pull request also cleans up some unrelated test error messages and warnings which had been introduced in other branches.
@transcom/truss-design There are no UI changes made in this pull request, but the changes in functionality and test error messages did touch component code, which is why the CODEOWNERS policy may require someone to approve this PR.
Setup to Run Your Code

💻 You will need to use two separate terminals to test this locally.
Terminal 1
Start the UI locally.
make office_client_run

Terminal 2
Start the Go server locally.
make server_run

Additional steps

Log in locally to the office application as a Service Counselor and open any move in the queue.
Add an NTS-release shipment to this move, filling out all fields (including the delivery address), and click "Save."
Verify that the correct values display for this shipment on the Move details page, including the delivery address.
Click "Edit shipment," verify that the correct values display for the delivery address on the edit page, and then change the delivery address for this shipment, afterwards clicking "Save."
Verify that the delivery address value has updated.

Verification Steps for Author
These are to be checked by the author.

[ ] Request review from a member of a different team.
[ ] Have the Jira acceptance criteria been met for this change?

Verification Steps for Reviewers
These are to be checked by a reviewer.

Frontend

[ ] User facing changes have been reviewed by design.
[ ] There are no aXe warnings for UI.
[ ] This works in Supported Browsers and their phone views (Chrome, Firefox, IE, Edge).
[ ] There are no new console errors in the browser devtools
[ ] There are no new console errors in the test output
[ ] If this PR adds a new component to Storybook, it ensures the component is fully responsive, OR if it is intentionally not, a wrapping div using the officeApp class or custom min-width styling is used to hide any states the would not be visible to the user.

Messages

:book:
:link: MB-10909

  Generated by :no_entry_sign: dangerJS against e0b67b2aee7bd9196e5ebca52f0aec17bcd92348


Running scale tests in emulator mode

The existing repo has this script https://github.com/openshift/instaslice-operator/blob/main/test/perf/load_with_stats.sh which we can use to submit 100 emulator pods and get the latency via CI, this could be a nightly job as it would take few minutes to run.

FYI @harche

/close


Add dot files to static as config option

Great work on this! It's running super slick so far.
One comment/suggestion I have. I'm working on a firebase project which includes a .firebaserc file. I've added this file to static, but static doesn't pickup on dot files. I configured it to do so on my local as a test, might be nice to have an option to pass dot: true (or something of that nature) in the task-config.js file. I want this file to transfer into the main dest directory do I can run a firebase deploy from the dest root.
Thoughts?
Thanks.

huh. Didn't realize it's not copying dotfiles. Thanks for catching that! I think it should be default. Let's look into why it's not.
Are you using blendid or master?

Pushed up and cut a new blendid release (4.0.0-blendid-beta-20). yarn upgrade blendid and you should be good to go. Thanks!

Amazing! Thanks for looking into it so quickly!


Protected APIs marked with @internal for SharedMap and Counter

Adding @internal prevents APIs from being on the public docs.

Build blocker is probably being caused by the package-lock and lerna-pacakge-lock changes. Leaving those out of the PR should allow it to pass

"lockfileVersion": 2,

are we forcing npm 7?

Refers to: package-lock.json:4 in ce6320e. [](commit_id = ce6320e043dbecafc7b0451bbb0569163087a903, deletion_comment = False)


Create new resource page for "conferences"

Request
Let's add a page under resources located at https://techqueria.org/resources/conferences with the title "Conferences"
Why did you make this request?
Let's showcase conferences that center around Latinx in Tech
Any additional context?
Yes, here are a few conferences we would like to initially add:

LULAC's Latinx Tech Summit: https://www.latinxtechsummit.org/home; https://www.latinxtechsummit.org/
Latinx Tech Summit: http://www.latinotech.org/
Latinx in Tech Summit: http://ltx-latinx-in-tech-summit.eventcreate.com/
Latin Tech Summit: https://latintech.io/
Latinx in AI Summit: https://www.latinxinai.org/events

See #294 for a similar request and how it was resolved in #323

Hi fvcproductions - Could I handle this issue? let me know if it is ok. Thanks!

@justjunior123 yeah feel free!

@fvcproductions I've finished up the task locally and all looks great. Do I merge my changes? Sorry I'm new to open source and a little lost at the moment.

@fvcproductions The conference category in resources is already part of the current site. All the links listed in this post have also been added on the site. This request seems to have already been completed. Is there anything else that needs to be done?

@hyerania nope, not really - I will close
but I will create an issue to add in the images for resources without an image


Updated to the latest version 2.4.7, Android studio cannot find the code implementation of RtmpClient

Describe the bug
After upgrading to the latest version 2.4.7 or 2.4.6, Android studio cannot find the code implementation of RtmpClient. Downgrading the version to 2.4.5 works fine.

Hello,
I just tested the compilation in a clear project and it is working fine for me. This is like the library is not found
Can you show me your build error?

Android studio has been upgraded to the latest version and the problem has been solved


fix: nullability semantics of predicates in JoinRel and FilterRel

An attempt to fix #51.

[x] Filter relations
According to https://github.com/substrait-io/substrait/issues/325#issuecomment-1244578057:

For those boolean expressions, true is treated as "succeeds" and false and unknown (aka null) are treated as "fails".

I modified the summary of filter relations to reflect this behavior.

[x] Join relations

[x] ~According to https://github.com/substrait-io/substrait/blob/e68fdc049c1219a1269225456072d7548c83f297/site/docs/relations/logical_relations.md?plain=1#L199, literal join expression values are allowed, but they must be true. Added a check and test.~
[x] Added some notes to the summary of join relations about nullability behavior of the join and post join filter predicates.

I've added comment tests to the test runner to test these changes.

@jvanstraten do you prefer a single PR to fix #51, or should I split over multiple PRs? If we're doing multiple PRs, this one is ready for review.


Add support for PC Engines APU2

Add the signature.
Fix allocator issues. coreboot reports page 0 as reserved and this breaks
the address space map allocator. Coreboot also reports memory starting at
0xc0000 as usable, and the asm code would toss that -- in the process, tossing
all of memory.
asm has turned out to be a bit fragile. It can't function without having memory
start at 0. But the code is a bit subtle, so be careful if you decide to adjust it.
Add a comment to mmuinit to explain an error message that is seen all too often.

dammit. master. dammit.

why is it showing as wants to merge 2 commits into Harvey-OS:master not main?

I'm going to close and reopen this issue to trigger the build, which is tied to the PR open even. Sorry for the noise

I got it in finally on another path.


Hitsound pack 8-14

Check  #1463 if you want previous hitsound pack
Extract to csgo/sound
sound.zip

Funny thing is i expected that to happen at some point so i left the volume at 0 and turned it up quickly, nice one dude


FIX: Remove deprecated functionality

Let's see if I got them all without breaking things. Not likely.

travis no esta happy

All better


Improve answer storage

The current slide answer save code uses text serialization to compound multiple answer fields into a single database field, and the display code splits this field up again for display.
This doesn't currently handle slides which have a mixture of control types (textarea, multi-textarea, checkbox, radio button).
The form save code should be extended to create a struct/document which is serialized into the single database field, and the display code should be able to match fields from the serialized struct to populate the fields correctly when viewed.
The serialized struct should support a mixture of control types:

Multi-text area
Checkboxes
Multiple groups of radio buttons.

This feature is now mostly complete and deployed to the staging server.  There are some placeholder syntax changes for checkboxes, detailed on the project wiki.

Can we recall specific answers from previous slides where that slide has multiple questions on it now?

Yep, that's fixed now.  I've added the updated syntax to the formatting wiki page.

How does this work if there are multiple answers on the specified step/slide?


Factor out the routine for calculating efforts and improve speed by reducing printouts

Before, typingEffort calculation was in carpalx, but optimization requires calculating sum of typing efforts for different corpuses. Now the calculation is moved into carpalx.ts.
Also, logging in console take a considerable amount of time. Now the console logs only when there's an improvement or annealing so you can keep track of current score.
Benchmarks
N = 100, 5 runs
Old average: 9.128s
New average: 8.534s (6.5% faster)
N = 1000, 2 runs
Old average: 82.535s
New average: 75.080s (9.0% faster)

Note: I had to change display method because the refactoring moves logging into the sumTypingEfforts function. Once this function returns a value to the main loop, console.clear() got called, so it seems like nothing was printed. This end up saving some time ;)

Need to figure out how to pass these tests first :)


raidboss: add wol nm/ex initial translations

But what is "GTFO" in wol?
EDIT: Well, I got it from Akurosia, so never mind...

Sorry! Maybe that GTFO one should just say "don't stack"?

Sorry! Maybe that GTFO one should just say "don't stack"?

 But maybe in the future, a commit message or comment would help when using these abbrivated concept？


Please add SVG

This should be opened in https://github.com/AliOsm/phlex-icons-web-app
I opened it here 👉🏻  https://github.com/AliOsm/phlex-icons-web-app/issues/4


prepare patch release 0.12.1

Pull Request Checklist:

[ ] This PR addresses an already opened issue (for bug fixes / features)

This PR fixes issue #xyz

[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Documentation has been added / updated (for bug fixes / features)
[x] HISTORY.rst has been updated (with summary of main changes)
[x] I have added my relevant user information to AUTHORS.md

What kind of change does this PR introduce?:
prepare release 0.12.1 ... updated changes
Does this PR introduce a breaking change?:
no
Other information:

@Zeitsperre we need a patch release. But we will have the same issue that the main branch is restricted when pushing the tag.

Right. Perhaps what we can do is to not have bumpversion tag on commit, then tag the commit made to master. I can try finding a way to do this semi-automatically in the meantime.

So, for now, run $ bump-my-version bump --no-tag patch, then tag the commit made to master.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 72.201%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1709

Relevant Lines:
2367

💛  - Coveralls


Hierarchical ais-hierarchical-menu--link__active class

For design like magento it could be useful to have ais-hierarchical-menu--link__active
Right now I am only able to do this

With ais-hierarchical-menu--link__active we would be able to put the blue border only for one link in the level 1

That's doable already: http://algolia.github.io/instantsearch.js/#q=&hPP=6&idx=instant_search&p=0&hFR[hierarchicalCategories.lvl0][0]=Cameras %26 Camcorders > Digital Cameras&is_v=0

@redox yes cool


Remove of un-needed line

removal of following line, as it contradicts the line that comes after, which offers a random server-id for the slave.
RUN sed -i '/\[mysqld\]/a server-id=1\nlog-bin' /etc/mysql/mysql.conf.d/mysqld.cnf

thanks


aws s3 write stream

I used google cloud storage write stream method is
remoteWriteStream = await storage.bucket(bucketName).file(fileName).createWriteStream();
sharp(srcBucketData).resize(300, 300, {fit: sharp.fit.inside, withoutEnlargement: true}).pipe(remoteWriteStream);
but aws s3 is not working.
Please let me know if there are any samples available in aws s3 storage

The unit tests include Stream-based input and output:
https://github.com/lovell/sharp/blob/844deaf48060d60eb05f3f61c567282e3611f12a/test/unit/io.js#L135-L151
This might be a question better suited to a site such as StackOverflow, for which you'll need to provide more information than "not working".

I hope this information helped. Please feel free to re-open with more details if further assistance is required.


Add CTA board spider

Adding a spider for the Chicago Transit Authority board. It's mostly straightforward, but there's one part I have a question on.
On the events page, one type of meeting's start time is consistently marked "Immediately following Cmt Strategic Planning & Svs". I'm just setting the date on those and leaving the time at midnight, but would it be better to add a time an hour or so after the previous meeting?

I'd say put the same time for the finance+audit meeting as the strategic planning one. It looks like the same room is used for other meetings right after, so these two probably go together.

@r-wei works for me! Just updated that, and also changed the start URL so that it shows all events by default

@pjsier This looks good to me! I'll get this merged in shortly.


error - PlayerJoinEvent

logs
http://hastebin.com/vekegacewu.avrasm

This is because you're using wrong multiplier permisson (the ".*"). Remove it from the player and it will be fine.

ok, thx, it work : )


Monaco Webpack Update to fix hot reload for development

This switches back to using MonacoWebpackPlugin which fixes development hot reloading.
It does setup the loading of the webworkers differently based on the documentation for monaco-yaml.
https://github.com/remcohaszing/monaco-yaml#usage
I've tested in development and a production build.
The hot reloading is working and the workers are loading properly.
Working with QE to make sure that is resolves the issues they were seeing during testing.

Ran the credentials-types tests locally and pointed at the Dev server, everything passed. these tests have the Monaco editor for input and injector configs.


Extend qemu_cortex_r5 test coverage

At the time of writing, the qemu_cortex_r5 board based on xilinx_zynqmp SoC is only able to run very basic non-multitasking samples and tests (e.g. hello_world sample).
In order to improve test coverage on the qemu_cortex_r5 platform and facilitate CI testing of the ARM Cortex-R port, QEMU needs to be patched to provide a better emulation of the RPU of the Xilinx ZynqMP SoC; at the same time, incorrect xilinx_zynqmp SoC implementation on Zephyr needs to be fixed.
QEMU Tasks

[X] ~PATCH: arm/xlnx-zynqmp: put APUs and RPUs in separate CPU clusters~
(https://patchwork.kernel.org/patch/10717697)
[X] ~PATCH: xlnx-zynqmp: add the timers~
(https://patchwork.kernel.org/patch/10048347)
[X] ~PATCH: xlnx-zynqmp: add PL390 GIC for RPU~
(WIP)

~A pull request incorporating the above patches is to be made on zephyr_rtos/qemu. As for the new patch(es), a pull request will be made on Xilinx/qemu and, hopefully, Xilinx will submit an upstream patch.~
It seems the hard-coded qemu machine type -machine xlnx-zcu102 (currently being used as the default "run" environment by qemu_cortex_r5 board) is simply obsolete. Both RPU GIC and TTCs are properly mapped when emulating with -machine arm-generic-fdt using the latest zcu102-arm.dts from Xilinx/qemu-devicetrees.

[x] https://github.com/zephyrproject-rtos/sdk-ng/issues/138 Add arm-generic-fdt machine type support to Zephyr SDK qemu (this machine type is currently only available in Xilinx/qemu)

Zephyr Tasks

[x] https://github.com/zephyrproject-rtos/ci-dockerfiles/pull/55 Add Zephyr SDK 0.11.0-alpha-5 to the CI docker image
[x] #20298 Modify qemu_cortex_r5 board qemu emulation to use arm-generic-fdt machine type
[ ] #20267 Fix incorrect xilinx_zynqmp dts (the current dts used by RPU is really that of APU, especially the GIC-400 mapping that only applies to APU)
[ ] #21508 Implement PL390 GICv1 support
[ ] #19869 Implement tickless API for Cadence TTC system timer driver

Note

Since the current Zephyr architecture cannot support AMP of Zynq APUs and RPUs in one project, we should consider the APU and RPU to be different hardware platforms (i.e. consider renaming xilinx_zynqmp to xilinx_zynqmp_rpu; when Cortex-A support is added in the future, add xilinx_zynqmp_apu; qemu_cortex_a53 should then utilise xilinx_zynqmp_apu). -> This has been addressed in the PR #20267.

cc @bbolen @wjliang @carlocaione @ioannisg

Sample qemu RPU boot command line using the latest dts:
qemu-system-aarch64 -machine arm-generic-fdt -nographic -dtb ~/Dev/xilinx-qemu-devicetrees/build/zcu102-arm.dtb -serial mon:stdio -device loader,file=/home/stephanos/Dev/zephyr-public/zephyr/tests/kernel/timer/timer_monotonic/build_cr5/zephyr/zephyr.elf,cpu-num=4 -device loader,addr=0xff5e023c,data=0x80008fde,data-len=4 -device loader,addr=0xff9a0000,data=0x80000218,data-len=4

I'm trying out Zephyr and an emulator is my obvious first choice.. I've been able to build and execute Zephyr on QEMU-R5 but I am unable to debug the app / kernel (while starting Qemu machine, I tell the GDB to listen to a port for TCP connections and then connect it via an IDE).. I think the problem is that the R5 image is ARM while the Qemu model is Aarch64, and so this incompatibility generates problems (See https://forums.xilinx.com/t5/Embedded-Linux/Running-application-on-R5-of-zcu102-xilinx-QEMU-model/td-p/905515).. Have any of you guys been able to debug this ? If so, can you kindly list down the steps..
--Bilal

@bwasim I have never tried debugging Zynq RPU under QEMU, but the Xilinx docs mention that a special gdb build is required for this (i.e. multi-arch build configured with --enable-targets=all), which is not included in the Zephyr SDK at the moment.
https://xilinx-wiki.atlassian.net/wiki/spaces/A/pages/18841606/QEMU+-+Zynq+UltraScalePlus#QEMU-ZynqUltraScalePlus-DebuggingtheA53sandtheR5sfromGDB
I will look into this tomorrow and see if I can get this special gdb build included in the Zephyr SDK.

Thanks for the update..
On a side note, I'm currently trying to get a functional board support for ZCU102-R5 (physical board) with support for Ethernet enabled (I don't see the GEM IP ported to Zephyr yet).. Will open a PR for it soon (Thanks to your previous work, I already have the UART / Kernel up and running)..
--Bilal

@bwasim Just tested Xilinx QEMU RPU debugging, and it works with a gdb that is configured with --target=aarch64-zephyr-elf --enable-targets=arm-zephyr-eabi (you can just use gdb-multiarch that is commonly available too).
I will try to get this included for the Zephyr SDK 0.11.0 release.

Very cool.. Thanks..

What debugger is that?

What debugger is that?

@andrewboie It is gdb with the gdb-dashboard.
https://github.com/cyrus-and/gdb-dashboard

All PRs merged.

@stephanosio not familiar with this platform, but what's the CPU clock frequency for this QEMU, thanks

@stephanosio not familiar with this platform, but what's the CPU clock frequency for this QEMU, thanks

@wentongwu In terms of QEMU, it is meaningless to talk about the CPU clock frequency for obvious reasons.
When running on real hardware (ZCU102), the clock frequency would depend on various configurations (e.g. on-board oscillator frequency, PLL configuration, ... handled by the PMU).

yes, for normal mode we don't need that, but I'm trying to enable QEMU icount mode for qemu_cortex_r5, and it need CPU clock frequency to some math, if any interest, please take a look https://github.com/zephyrproject-rtos/zephyr/pull/22904 and https://github.com/zephyrproject-rtos/zephyr/issues/14173 . Thanks


SOLR-15407 untokenized field type with sow=false fix + tests

Description
sow=false should not split on whitespace and build field queries with the entire query text.
It's the responsibility of each field query text analysis to manage tokenization if any.
Currently this doesn't happen for not textual fields such as string, numerical.
It's up to discussion if we want to apply tokenization to numerical, even with sow=false
Solution
no tokenization happens if the field is not textual
Tests
There are old tests that have been corrected as their behaviour was incorrect, with sow=false in my opinion.
There is a org.apache.solr.search.TestExtendedDismaxParser#testFocusQueryParser that is up for discussion in relation to numerical fields.
Checklist
Please review the following and check all that apply:

[ X] I have reviewed the guidelines for How to Contribute and my code conforms to the standards described there to the best of my ability.
[ X] I have created a Jira issue and added the issue ID to my pull request title.
[ X] I have given Solr maintainers access to contribute to my PR branch. (optional but recommended)
[ X] I have developed this patch against the main branch.
[X ] I have run ./gradlew check.
[X ] I have added tests for my changes.
[X ] I have added documentation for the Reference Guide

the pull request has been updated with what I believe it is the current correct behavior:
/*
* sow=true implies the minimum should match is "per document"
* i.e a document to be a match must contain all the mm query terms anywhere at least once
* sow=false implies the minimum should match is "per field"
* i.e a document to be a match must contain all the mm query terms in a single field at least once

*/

I'll look closer at this PR (e.g. in a debugger etc.) possibly tomorrow or if not then this weekend.

that's much appreciated, I want a second pair of eyes minimum before merging this, so thanks David for your time.
I would be delighted to have an opinion also from the other committers that were recently involved in the edismax query parser : @madrob @romseygeek @munendrasn @sarowe

Given there's disagreement in changing this behaviour (is it bug or not?)
I suggest the following steps:

isolate the changes for the MM issue if possible in a separate Pull Request
find someone else opinion on both topics of this Pull Request ( the string field sow bug and the MM bug)
Should I tag any other people @dsmiley ?
I took the latest people involved in the class, but we didn't get any other opinion in the last 10 days

In the meantime I was still thinking about this and I still think it is a
bug:
If we set a field type to be keyword analysed (so producing the same token
as a String field), the sow works correctly and we have the same behaviour
I am introducing with the fix.
On Mon, 24 May 2021, 16:59 David Smiley, @.***> wrote:

@.**** commented on this pull request.
It seems we don't agree on this yet.
In solr/core/src/test/org/apache/solr/search/TestExtendedDismaxParser.java
https://github.com/apache/solr/pull/129#discussion_r637963606:

@@ -1771,6 +1787,35 @@ public void testSplitOnWhitespace_Basic() throws Exception {
assertThat(parsedquery, anyOf(containsString("((name:stigma | title:stigma))"), containsString("((title:stigma | name:stigma))")));
}

@Test
public void testSplitOnWhitespace_stringField_shouldBuildSingleClause() throws Exception

Based on the test name, I'd expect sow=true each time. Maybe just drop
this part of the method name.
In solr/core/src/test/org/apache/solr/search/TestExtendedDismaxParser.java
https://github.com/apache/solr/pull/129#discussion_r637963928:

@@ -1771,6 +1787,35 @@ public void testSplitOnWhitespace_Basic() throws Exception {
assertThat(parsedquery, anyOf(containsString("((name:stigma | title:stigma))"), containsString("((title:stigma | name:stigma))")));
}

@Test
public void testSplitOnWhitespace_stringField_shouldBuildSingleClause() throws Exception
{

   assertJQ(req("qf", "trait_ss", "defType", "edismax", "q", "multi term", "sow", "false"),

       "/response/numFound==1", "/response/docs/[0]/id=='75'");

   String parsedquery = getParsedQuery(

       req("qf", "trait_ss", "q", "multi term", "defType", "edismax", "sow", "false", "debugQuery", "true"));

   assertThat(parsedquery, anyOf(containsString("((trait_ss:multi term))")));

}

@Test
public void testSplitOnWhitespace_numericField_shouldBuildAlwaysMultiClause() throws Exception

Again, just drop "testSplitOnWhitespace_" from the method name, I think.
In solr/core/src/test/org/apache/solr/search/TestExtendedDismaxParser.java
https://github.com/apache/solr/pull/129#discussion_r638071458:

@@ -1771,6 +1787,35 @@ public void testSplitOnWhitespace_Basic() throws Exception {
assertThat(parsedquery, anyOf(containsString("((name:stigma | title:stigma))"), containsString("((title:stigma | name:stigma))")));
}

@Test
public void testSplitOnWhitespace_stringField_shouldBuildSingleClause() throws Exception
{

   assertJQ(req("qf", "trait_ss", "defType", "edismax", "q", "multi term", "sow", "false"),

This is a change in behavior, and I think it's not a good change. For a
non-tokenized field (StrField in this case), I think we should ignore
whatever "sow" is and split on whitespace any way, thus here have two terms
to match. It would be straight-forward to document this (no differences
between numbers and StrField).
I think it could be reasonable to try both ways (both split and don't
split) and then put a DisjunctionMaxQuery over the two, though I'd prefer
not.
In solr/core/src/java/org/apache/solr/parser/SolrQueryParserBase.java
https://github.com/apache/solr/pull/129#discussion_r638074368:

       } else {

         List<Query> subqs = new ArrayList<>();
         for (String queryTerm : queryTerms) {
           try {
             subqs.add(ft.getFieldQuery(parser, sf, queryTerm));

         } catch (Exception e) { // assumption: raw = false only when called from ExtendedDismaxQueryParser.getQuery()

           // for edismax: ignore parsing failures

         } catch (Exception e) {

           /*

           This happens when a field tries to parse a query term of incompatible type

           e.g.

           a numerical field trying to parse a textual query term

            */

           subqs.add(new MatchNoDocsQuery(queryTerm + " is not compatible with " + field));

It appears this change (the addition of MatchNoDocsQuery here) has no
effect but maybe I'm mistaken?
In solr/core/src/java/org/apache/solr/parser/SolrQueryParserBase.java
https://github.com/apache/solr/pull/129#discussion_r638072636:

       return new RawQuery(sf, queryTerms);

     } else {
       if (queryTerms.size() == 1) {
         return ft.getFieldQuery(parser, sf, queryTerms.get(0));

     } else if(ft instanceof StrField){

In essence, I think the behavior I see here was correct before -- no
special case for either StrField or numerics. In the context of the logic
that reaches this point, the field is already ft.isTokenized==false.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/apache/solr/pull/129#pullrequestreview-666761251, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAD5JK7YA7MGLQJO5BK2HM3TPJZUZANCNFSM444WCCXQ
.

Thinking a little more about this I'll make even a bigger provocation:
I don't think it should exist a StrField type at all, it is textual information and we can get the same through a text field which is just "Keyword tokenized", and should be the only way, there's no benefit/differentiation in having two ways for the same.
But removing the StrField type is definitely not in scope in this issue, so in my opinion, we should at least have consistent behavior, and today if you define a field as StrField type or text Keyword tokenized, the sow works correctly just for the latter.

From JIRA:

it seems we get a document just containing "100" in the numerical field to be a match, even if it doesn't contain "terminator" anywhere else with mm=100%. And I think that's incorrect.

And I agreed.  What test illustrates this problem?  I'm suspecting the code already works this way but I must be mistaken for you to pose this question in JIRA.

isolate the changes for the MM issue if possible in a separate Pull Request

+1 indeed; if it fixes its own issue then it deserves a separate PR, especially for sensitive code like query parsers that will be noticed by users.

Sister issue and PR has been added:
https://issues.apache.org/jira/browse/SOLR-15449
https://github.com/apache/solr/pull/158
I am going now to clean this PR just leaving the string field part

Pull Request has been cleaned, only the fix related with the Jira issue is now present.
i'll summarize it again.
Index Time
Configuring a field to be "StrField" or "text" with a keyword tokenizer builds an inverted index with a single token per field value.
Expected Query Time behaviour
As a user using the edismax and typing a full text query I expect:
sow=false -> to not split on whitespace and delegate to the field text analysis (that for a StrField will not tokenize)
sow=true -> to split on whitespace independently of the field type
** Current Incorrect Behaviour **
If I query a "StrField" type or a text field type Keyword Tokenized, I get two different behaviours :
sow=false -> it splits on whitespace anyway for StrField, causing incorrect results, for Keyword Tokenized texts, it works correctly
sow=true -> to split on whitespace independently of the field type, it works correctly
The changes are clear in the tests

** Current Incorrect Behaviour **
If I query a "StrField" type or a text field type Keyword Tokenized, I get two different behaviours :
sow=false -> it splits on whitespace anyway for StrField, causing incorrect results, for Keyword Tokenized texts, it works correctly
sow=true -> to split on whitespace independently of the field type, it works correctly

This summary is helpful. If starting with a clean slate, perhaps the "correct" behavior should be as you've outlined -- but then I would think you'd want the same strict "non-splitting" behavior for integer fields. My gut reaction is that this is a very unusual use case (configuring a StrField or integer field as qf). In fact, a strong argument in principal for "strict" non-splitting behavior would be to effectively discourage this kind of configuration in the first place!
Ultimately though I think I'm converging on agreement with https://github.com/apache/solr/pull/129/files#r638071458 ... tbh I'm having a hard time imagining a use case where the configuration in question (or its current behavior) would be desirable; but assuming there may be such use cases already in place, this change could surely disrupt them.
Perhaps the fact that keyword-tokenized text fields currently work "correctly" (as defined above) could be employed to address this issue going forward for certain use-cases, rather than changing existing behavior? Keyword-tokenized text would also seem more appropriate to the edismax use-case, by providing analysis for text normalization (the lack of which strikes me as the most unusual aspect of configuring StrField qf).

I agree it's not the most elegant solution to check on the type instance (but there's plenty in Solr that does that), but I still think that it is an inconsistency.
As specified in other comments, the root problem is the StrField type per se:
Should we then start a much more complex task i.e. "removal of StrField" to avoid such inconsistencies?
We could try doing it in a back-compatible way, but ultimately I think the real issue is that we express text to be untokenized in the index in two ways with no apparent benefit but just inconsistencies?
i.e.
StrField could be an alias rather than a separate Field Type

The core of my point is that that Solr already has an API to interrogate the field type to see if it produces one token or more -- {{FieldType.isTokenized}}.  SolrQueryParserBase uses this in a number of places already.  It appears you want to make StrField a further specialized case when isTokenized==false is not distinguishing enough and that appears to me going too far / hacky.  It might be justifiable if we felt the result was clearly the correct behavior but we don't even think that (I don't, nor does Michael).
Nonetheless some user control could be added so that someone with a normalizing text field that uses TextField (likely with KeywordTokenizer but not necessarily) could get query parser behavior that is the same as how StrField behaves. It'd be nice if a user could set tokenized="false" on the fieldType definition that uses TextField if they can attest the processing doesn't tokenize.  I experimented this morning with that and was able to do it by modifying the first line of TextField.init to be this snippet:
    if ((falseProperties & TOKENIZED) == 0) {
      properties |= TOKENIZED;
    }

(instead of insisting TOKENIZED as it did before).
And maybe the existing logic in SolrQueryParserBase could be improved somehow; I'm definitely not claiming it's perfection.  It just strikes me as a cast on StrField is a strong code smell to me that we're doing something wrong when there is already isTokenized which seems suitable for your purpose.

Making an update here to understand the potential next steps.
So I think we agree that:

if you configure a StrField in the QF and you configure sow=false, currently the parameter is ignored, you split by whitespace and you don't match your multi terms (it is like we use a query time tokenization, not in line with the expected invisible query time keyword tokenization of the StrField.) This is incorrect and gets you zero results when you shouldn't

the StrField condition is not a solution you like, so we won't approve the pull request in the current status

So next steps:

it seems we want to "discourage" the usage of StrField in QF with an inconsistent behaviour (in comparison with a text field with the same keyword tokenization analysis). Should we then explicitly raise an error if the user passes a StrField (maybe all non-textual fields) in QF?

OR

should we remove the StrField type completely? we can leave the schema.xml back-compatible, but always use text fields for textual information server-side (I think it's the same approach that Elasticsearch uses and it makes sense to me)

OR

just ignore this issue? I am not a fan of this

OR

any other idea? super happy to explore other options

This is incorrect and gets you zero results when you shouldn't

I'll acknowledge that the current behavior seems "incorrect" in principle to me (though just as incorrect for numeric fields). In terms of practical use cases, the current behavior strikes me as highly unusual -- but frankly no more unusual than if the behavior were to be changed to respect sow=false. Perhaps I'm being closed-minded in thinking that what's "incorrect" is the config itself -- but before declaring the config to be canonically "incorrect" (and disallowing it), I think an open-minded attempt to brainstorm possible use cases would be in order.
That's particularly the case because:

The change in behavior would be dramatic (for anyone actually relying on this config); it's also worth noting that the current behavior is not newly introduced, and I'm not aware of any instances of users expressing confusion about it in the past (again to be clear, my initial inclination is to consider qf against non-analyzed fields to be "incorrect" in principle)
iiuc there'd be no way to migrate current behavior for anyone who wanted to preserve it
There's currently a viable workaround (and a more "search-idiomatic" one at that, via KeywordTokenizer) for anyone who desires the proposed "correct" behavior.

Hmm... on second thought maybe wrt point 2:
<analyzer type="index">
  [KeywordTokenizer]
</analyzer>
<analyzer type="query">
  [WhitespaceTokenizer]
  ...
</analyzer>

iiuc there'd be no way to migrate current behavior for anyone who wanted to preserve it
Mmmm if you want to split on whitespace for a field in QF that is a StrField, you can just use sow=true .
The reason I am saying that currently in my opinion we have a problem is that if you do:
Given q=
sow=true  -> StrField:term1 StrField:term2
sow=false  -> StrField:term1 StrField:term2

As a user (my personal idea) if I set a StrFIeld in QF and set sow=false, I am relying on the query time tokenization approach of my QF fields (and query time tokenization approach for a StrField is "not to tokenize at all")
So if I have multi terms in the index for my StrField e.g. StrField: "term1 term2", currently I am unable to search for them both using sow=true or sow=false.
On the other hand if I have in my index [Doc1 StrField:"term1"]  [Doc2 StrField:"term2"], for the query "term1 term2" I'll make sure to configure my sow=true.


Unknown error when trying to post to community

Unknown error when trying to post to community.
Investigate.

This also seems to happen for posting to timeline.


docs(common): contributing guide

What?
This PR updates the CONTRIBUTING.md
View the rendered file →
Why?
JIRA: EXT-1256

Hi @BibiSebi and @demetriusfeijoo
This is a new CONTRIBUTING.md guide for those who want to contribute to this SDK. Feel free to leave lots of questions, comments, and suggestions here 🙌🏻

@BibiSebi thanks for the review! I've addressed your feedback :)
https://github.com/storyblok/field-plugin/pull/225/commits/9f42d8d0a6017dc6bda207733c8b68da1b1abd05


Implementing Ditto for CHIL paper experimentation

PR Type
Feature
Short Description
Implementing Ditto as an additional baseline method for FL4Health, but also to add to the CHIL paper results.
Tests Added
Basic tests verifying functionality for Ditto have been implemented.

@emersodb @fatemetkl Just got through the Ditto paper, will have feedback by 6:30 EST. Just going through now.


Home path is missing the drive letter on Windows

What steps will reproduce the problem?
1. cindex any/path (without CSEARCHINDEX set)
2.
3.

What is the expected output?
Using .csearchindex in home dir.

What do you see instead?
Failing due to the home path missing the drive letter. In index/read.go, the
line in File() getting the home dir should probably read 'home =
os.Getenv("HOMEDRIVE") + os.Getenv("HOMEPATH")'

What version of the product are you using? On what operating system?
Windows 7, 64 bit

Please provide any additional information below.

Original issue reported on code.google.com by<EMAIL_ADDRESS>on 23 Jan 2012 at 10:39

I am getting the following error on windows 7 64bit.

cindex.exe -list

2013/04/02 21:27:11 open \Users\dips/.csearchindex: The system cannot find the
path specified.

Original comment by<EMAIL_ADDRESS>on 2 Apr 2013 at 4:00

I have got the same error as dips.

Original comment by<EMAIL_ADDRESS>on 16 Sep 2013 at 3:50


doesn't seem to recalc the atom on cache updates

Repro:

Make an atomWithQuery
useAtom on your query atom
Have some other UI update the graphcache entry that the query returns

Expected:
that atom updates with the new value
Actual:
No update
cc: @juliette-pouchol

We would need an actual code snippet, or, better a reproduction.
Info given isn't enough to triage it.

Well I guess the first question would be: is this expected to work? I can work on a repro but I thought I would see if this was obvious to you first. Cache updates are pretty basic urql

It should work, it subscribes to the changes of the items that are in the query.

i'll work on nailing down a repro soon then

so i finally painstakingly put together our use case in codesandbox: https://codesandbox.io/p/sandbox/urql-client-side-suspense-demo-81obe?file=%2Fsrc%2Findex.js%3A22%2C44
And it didn't repro 🤦
I dug harder in our code and it turns out we weren't using the same client, because we were using useHydrateAtoms([clientAtom, client]) but our client gets recreated and memoized on a couple props. Changing to both hydrate and set the atom in a useEffect fixed this. Sorry to take up attention, but leaving our root cause and fix here in case anyone else runs into this.
Thanks again for this great library, which does not have this bug :D

@scamden Yay! Pretty happy my work (and a lot of tests) did pay off :D
Happy hacking! Also, be aware that Next + Suspense may cause some weird freezes and hangouts of the entire page on route change that irrecoverable. But only in production build and with old router.
At least, once, I had this problem and I didn't manage to solve it for weeks. Only solution was to revert the changes and keep using 'loading' and stuff like that.
But I hope you'll never run into that problem :)

(and a lot of tests)
love this.

Also, be aware that Next + Suspense may cause some weird freezes and hangouts of the entire page on route change that irrecoverable.

oh dang! good to know! I have seen some "stuck in suspense" things, but so far the fix was to put a suspense boundary between the nearest jotai-scope provider and the suspending atom. This frightens me that this happened to you only in production though and I love the ergonomics of suspense so I don't want to stop lol.
Any more detail on when this happened to you? What version of next? was it a route change during an urql query?

@scamden to be completely honest I don't remember details, but it was super weird and it didn't work either it was suspended by URQL, or was suspended by just an async atom. And even a different sequence of visiting the routes was affecting it. If you do it in the 1 - 2 - 3 sequence it freezes at 3. But if you do 1 - 3 - 2 it does not :) So it was pretty weird. It was on Next 12 AFAIR.
So yeah, weird stuff :) Maybe with the app router it's no longer a thing, but for a page router it was there and it was a major PAIN as I had to revert 3 weeks of work :P