doesn't compile unless buildOptimizer is disabled

Hi,
First of all, rete is awesome!
Secondly, my error report here is similar to report #10 , which claim's to be "solved" by disabling the rete-context-menu plugin, but I'm not using that plugin, so I'd question whether removing that was the real solution even in that case. There's a reference in that report to disabling the build optimizer, and from trying numerous things, that appeared to "solve" the compilation errors for me.
Specifically, I was getting this error when using the app in prod (AOT compilation):
TypeError: Cannot set property 'mustUseProp' of undefined.
and occasionally a second error about runtime compiler missing. None of these errors appear in dev compilation though.
I found this article of a similar situation, albeit a different vue component.
Based on that article (given my limited knowledge of vue.js) is that there could be a problem with the way the angular compiler handles the vue js code, and they only manifest when using the AOT / build-optimized code. I'm wondering if this general concern is applicable with rete.
Currently I able to get rete working in prod using build-optimizer false (and vendorChunk set to true for good measure -- not sure if that's required though). However, til now I've never had to disable the build-optimizer for any other 3rd party libraries, and the optimizer reduces some bundles sizes by 30%+, so I definitely want it there for prod compilation.
Hoping you can look into how to get this working with angular build-optimizer.
-S. Arora

Closing since it maybe related to other plugins.

Hello @sarora2073  !
I'm trying to setup ReteJs into my project but i'm facing the same issue, did you manage to make it work ?

Hello @sarora2073  !
I'm trying to setup ReteJs into my project but i'm facing the same issue, did you manage to make it work ?

Hi @Hydhen,
Yes - i copied the angular-render-plugin module into my project natively. I don't remember exactly what else, but I would try that first to see if it works.
-S. Arora

Hi @Hydhen,
Yes - i copied the angular-render-plugin module into my project natively. I don't remember exactly what else, but I would try that first to see if it works.
-S. Arora


!!! TASK: Rename AbstractEventSourcedRepository->findByIdentifier()

This change renames findByIdentifier() to get().
Closes #80

I still dislike the get name as stated in #80, but if you others all agree on it, so be it.


fix: Custom theme not copied when creating new branch

Description
When a new branch is created where source branch has a custom theme, theme is not copied.
Fixes #14645
Type of change

Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

Manually
JUnit

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes

/ok-to-test sha=52db824


Update TutorialActivity

With some UX support perhaps, create a more standard & friendly TutorialActivity with fewer words and more colors and pictures, and maybe a few screens.

It's better now... could be even greater with some UX help.


New arch devel

Thanks @emma-w-dev for your great work, it is very useful! Let's merge and please then make the PR to neuralet.

Thank you for your great PR @JsonSadler, I will send the merged code to the main repo after testing other dockerfile.


Support requirements and env for javascript plugins

requirements and env are currently used for Python Plugins, however, these two interfaces can be also used by javascript plugins.

requirements can be used for defining the required js dependencies, they can be listed as an array or urls and downloaded into the browser database, such that javascript plugins can run offline.

env can be used to define the supported browsers, by matching agent strings or just with browser name. This is essential to tell when a plugin is not tested on mobile but ran on mobile device, ImJoy can decide whether to display such plugins or give a warning to the user.

Note, the offline aspect of this issue is not yet implemented, but the API should be sufficient to implement the offline feature later.


Removed fast query and fast bit module and shell script from bv

Description
Resolves #2917
Removed fastbit and fastquery from bv.
How Has This Been Tested?
The CI tests should fail if there is any issue
Checklist:

[X] I have performed a self-review of my own code
[X] I have updated the release notes
[X] I have assigned reviewers (see VisIt's PR procedures for more information).

Will you also be removing the related CMake vars from CMakeLists.tst (src, databases, databases/H5Part), and find modules, as well as preprocessor logic in H5Part db plugin?

References to Fastbit and FastQuerey still exist in several files, which I break down here:
There are several session files that reference it:
./test/crummy.session
./test/tests/session/legendproperties.session
./test/tests/session/restorewithsources.session
./test/tests/simulation/updateplots_session.session

Should I remove it from these files?
I'm working on removing references in pre-processor logic:
./databases/H5Part/HistogramCache.C
./databases/H5Part/HistogramCache.h
./databases/H5Part/avtH5PartOptions.C
./databases/H5Part/avtH5PartFileFormat.C
./databases/H5Part/avtH5PartFileFormat.h
./databases/H5Part/avtH5PartWriter.C
./databases/H5Part/avtH5PartWriter.h

In particular, HistogramCache completely depends on FastBit. Should I remove this file?
Lastly, some files make some comments about it:
./operators/PersistentParticles/avtPersistentParticlesFilter.C
./avt/Pipeline/Data/avtHistogramSpecification.C
./avt/Pipeline/Data/avtHistogramSpecification.h
./avt/Pipeline/Pipeline/avtNamedSelection.C
./avt/Pipeline/Pipeline/avtNamedSelectionManager.C

I don't think that I need to change those, but please let me know if you think differently.

Since HistogramCache is completely dependent, I think removing it is a good idea.
I wouldn't bother about the files whose only reference is via comments.
Might want to touch the config-site files that still have fastbit and fastquery entries.

Thanks for the notes @biagas. This is ready to review. I believe I took care of everything except for the session files. Still not sure if those need to be updated. Currently running the test suite on pascal.


NoModuleFound: No module named 'as2_python_api.modules'

When loading the command:
ros2 launch as2_keyboard_teleoperation as2_keyboard_teleoperation_launch.py namespace:=drone_sim_0,drone_sim_1,drone_sim_2 use_sim_time:=true
it gives the error that:
NoModuleFound: No module named 'as2_python_api.modules'

`pc@pc-VB:~/aerostack2_ws/project_gazebo$ ros2 launch as2_keyboard_teleoperation as2_keyboard_teleoperation_launch.py          namespace:=drone_sim_0,drone_sim_1,drone_sim_2         use_sim_time:=true
[INFO] [launch]: All log files can be found below /home/pc/.ros/log/2023-12-17-13-27-58-278768-pc-VB-3068
[INFO] [launch]: Default logging verbosity is set to INFO
[INFO] [as2_keyboard_teleoperation-1]: process started with pid [3069]
[as2_keyboard_teleoperation-1] Traceback (most recent call last):
[as2_keyboard_teleoperation-1]   File "/opt/ros/humble/share/as2_keyboard_teleoperation/keyboard_teleoperation.py", line 42, in
[as2_keyboard_teleoperation-1]     from as2_python_api.drone_interface_teleop import DroneInterfaceTeleop as DroneInterface
[as2_keyboard_teleoperation-1]   File "/opt/ros/humble/lib/python3.10/site-packages/as2_python_api/drone_interface_teleop.py", line 37, in
[as2_keyboard_teleoperation-1]     from as2_python_api.drone_interface import DroneInterface
[as2_keyboard_teleoperation-1]   File "/opt/ros/humble/lib/python3.10/site-packages/as2_python_api/drone_interface.py", line 37, in
[as2_keyboard_teleoperation-1]     from as2_python_api.modules.takeoff_module import TakeoffModule
[as2_keyboard_teleoperation-1] ModuleNotFoundError: No module named 'as2_python_api.modules'
[ERROR] [as2_keyboard_teleoperation-1]: process has died [pid 3069, exit code 1, cmd 'python3 /opt/ros/humble/share/as2_keyboard_teleoperation/keyboard_teleoperation.py drone_sim_0,drone_sim_1,drone_sim_2 false true'].`

Solved in v1.0.9 and upcoming releases


Fixing the way the gallery route gathers the gallery images

BugFix

Added useGetUserGallery hook in order to well gather the gallery user images

Fixes #24


add template for including tests for programmatic tasks

I think making the canonical programmatic task have a test will lead to better tested tasks.

Thanks for taking a look! Let me know if the edits I just made address your concerns.


Excessive and uninformed.

This misinterprets what was previously thought to be a benefit of inheritance. Such things are intended when functions must act through interface references instead of concrete types.
Implicit cast-to-base has its utility, and is why that feature exists in the first place. Moreover, the compiler should not warn in the case of a function "slicing" its return value in the presence of static_cast, etc...

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

ID: be6a0e19-d61f-fefb-4a83-afa87219e168
Version Independent ID: 206fffd7-3651-5783-49e0-c586a9b8b992
Content: C26437 - Visual Studio
Content Source: docs/code-quality/C26437.md
Product: visual-studio-windows
Technology: vs-ide-code-analysis
GitHub Login: @mikeblome
Microsoft Alias: mblome

@warp-10 Interesting comments but I think you should address them to the authors of the core guidelines themselves. The source for the guideline is here: https://github.com/isocpp/CppCoreGuidelines/blob/master/CppCoreGuidelines.md#Res-slice (and I will add that link to our topic).

The guidelines apply to polymorphic objects. Your compiler is emitting this
warning for anything that results in "slicing", even for non-polymorphic
types. The example in your article even demonstrates this, which is why it
is not correctly implemented.
On Mon, Oct 7, 2019 at 5:10 PM Genevieve Warren<EMAIL_ADDRESS>wrote:

Closed #4057
https://github.com/MicrosoftDocs/visualstudio-docs/issues/4057 via
abdd8be
https://github.com/MicrosoftDocs/visualstudio-docs/commit/abdd8be636e826f457cd18f19eca05ffcb4f51cd
.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/visualstudio-docs/issues/4057?email_source=notifications&email_token=AAOSFT4GXHDHAZS2JXJJO6TQNO6XLA5CNFSM4I5W7EBKYY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOUCGNFYA#event-2693583584,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAOSFTY65E2HY42NCZ44WM3QNO6XLANCNFSM4I5W7EBA
.

@warp-10 I see. Thanks for the clarification! Are you willing to raise this issue on the C++ Developer Community forum? The product team actively monitors that site for actionable issues, and other developers can upvote your issue.

Certainly. I was initially under the impression this was a Microsoft-specific warning, which is why I commented on the documentation page. This is really a bug, but I'm having trouble creating a minimal example that reproduces it. The function I'm trying to simplify needs to deliberately "slice" an almost-POD resource "pointer" into a lightweight "handle" (from which said pointer type derives).

@warp-10 I'm going to close this as it doesn't seem to be a documentation bug. Good luck on creating a repro. That will make a big difference in how it gets handled internally.


Adapt to the new api in libsonata-report for sonata spike report

Description
Adapt to the new feature from libsonata-report for spike report writing, i.e. do create_file/write data/close_file in separate steps.
The spike data also requires gid offset for each population, use default 0 at the moment.
Fixes # (issue)
How to test this?
The Simulation Stack CI
Use certain branches for the SimulationStack CI
CI_BRANCHES:SPACK_BRANCH=spike_multipop,NEURODAMUS_CORE_BRANCH=sandbox/weji/report_multipop,PYNEURODAMUS_BRANCH=sandbox/weji/report_multipop,

please retest

please retest

please retest

please retest

please retest

please retest

please retest

please retest

please retest

Codecov Report

Merging #608 (31e1284) into master (e2737dd) will decrease coverage by 0.05%.
The diff coverage is 35.29%.

@@            Coverage Diff             @@
##           master     #608      +/-   ##
==========================================
- Coverage   54.24%   54.19%   -0.06%
==========================================
  Files         102      102
  Lines        8388     8398      +10
==========================================
+ Hits         4550     4551       +1
- Misses       3838     3847       +9

Impacted Files
Coverage Δ

coreneuron/io/reports/nrnreport.hpp
0.00% <ø> (ø)

...eneuron/io/reports/report_configuration_parser.cpp
0.00% <0.00%> (ø)

coreneuron/apps/main1.cpp
48.95% <100.00%> (+0.21%)
:arrow_up:

coreneuron/io/output_spikes.cpp
88.88% <100.00%> (ø)

Continue to review full report at Codecov.

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

please retest

please retest

please retest

please retest

please retest

This was ready quite some time ago but I hope all branches will be merged soon!
CI_BRANCHES:SPACK_BRANCH=spike_multipop,NEURODAMUS_CORE_BRANCH=sandbox/weji/report_multipop,PYNEURODAMUS_BRANCH=sandbox/weji/report_multipop,

@jorblancoa I think we need a tag for libsonatareport, otherwise the CoreNeuron CI will fail ?
I've created a  temporary spack branch CI_BRANCHES:SPACK_BRANCH=spike_multipop, to build with the libsonatareport@master

Yes, we should create tags and then spack PR

Ok. Lets do this as soon as BB5 is back.


sample audio file

there should be a gibson, strat, tele .wav file which you click on to hear the raw tone and then the tone after adding the ir / .nam to it.
so like it would be:
hear this model:
GibsonBefore.wav
GibsonAfter.wav
etc. etc.

the .wav would be on the website and would operate like tonex website with the bottom right play button


"Save image" should save as shown in the notebook, including background

Feedback from PyCon 2022
"The "save image" button saves my image with transparent background so I can barely see my axes and title."
In the notebook (and as expected to be saved):

When I open the saved file:

(If you look closely, you can see the axes.. It's just black and the background of my dark themed machine is very dark grey...)

@minsa110, we discussed this for a few minutes. Overall, we don't think it's safe to override the transparency of the plot image. We are plotting on top of a white rectangle.
This could also be addressed if/when core supports copying images to clipboard.


The questions about the ImageNet pre-trained model

Hello, I would like to ask if the ImageNet pre-training model is obtained by training with the current network model using the ImageNet dataset, and then load this pre-training model when training on the kitti dataset, right?

Hi, yes. The encoder of the DepthNet was trained as a classification model using the ImageNet dataset. Then, the weights are loaded by setting --mypretrain.

After I changed the network, there was a problem that the Image Net pre-training model could not be loaded. Can I put the modified model on the Image Net dataset for training, and then use the trained model file as a pre-training model in Kitti_data training on the dataset

Hi, if you have changed a small part of the network you can still load most of the pre-trained weights, but you will need to modify the code a little to make it only load certain weights. You can check out this function that we currently use to load a pre-trained model. It removes the last norm layer of the pre-trained model.
If you have made major changes to the model and want to create your own pre-trained model, you can train it on ImageNet and then use it as a pre-trained model and fine-tune it on KITTI.

RuntimeError: Error(s) in loading state_dict for LiteMono:
	size mismatch for stages.0.3.pwconv2.weight: copying a param with shape torch.Size([48, 288]) from checkpoint, the shape in current model is torch.Size([288, 288]).
	size mismatch for stages.0.3.pwconv2.bias: copying a param with shape torch.Size([48]) from checkpoint, the shape in current model is torch.Size([288]).
	size mismatch for stages.1.3.pwconv2.weight: copying a param with shape torch.Size([80, 480]) from checkpoint, the shape in current model is torch.Size([480, 480]).
	size mismatch for stages.1.3.pwconv2.bias: copying a param with shape torch.Size([80]) from checkpoint, the shape in current model is torch.Size([480]).
	size mismatch for stages.2.9.pwconv2.weight: copying a param with shape torch.Size([128, 768]) from checkpoint, the shape in current model is torch.Size([768, 768]).
	size mismatch for stages.2.9.pwconv2.bias: copying a param with shape torch.Size([128]) from checkpoint, the shape in current model is torch.Size([768])

It seems that this can’t be solved by loading some weights. Can you tell me which year’s data is the data set you use? Can you provide a download link? If possible, I’m really grateful

Sorry, I didn't make it clear. I know this is due to the problem of pre-training weight loading. What I want to ask is what version of the ImageNet dataset is, because I saw different data from different years on the official website

Hi, the version of ImageNet is 2012 (ILSVRC2012)


[WIP] Add wheels build for Windows

Add wheels build for Windows
Try to speedup conda packages solver via conda-forge metachannel

Skip other then windows checks for a while. Will revert it back later.

@Vyacheslav-Smirnov Please do not forget to remove label WIP because I have no true status of this PR.

Closing this PR due to I have found another solution to build wheels using build-in conda feature.


Merging PyBird repo for DESI

Hi,
I am Yan from the University of Queensland. This is not an issue with the code, I just can't find your email, so I just posted the message here. Sorry about that. I am currently working on implementing PyBird into the DESIlike pipeline. I talked to Arnaud who is in charge of DESIlike, he says DESIlike uses the version of PyBird from this directory. I have developed several new features such as ShapeFit with PyBird. I also tested my version of PyBird with some of the DESI mocks. Is it possible that I can merge my repo with one of your branches? This way DESIlike will still be able to import PyBird and use my version of code. Thank you very much.
Best,
Yan Lai

Dear Yan,
Thank you for reaching out. I see that your fork is based on the (old) 'dev' branch. Since then there was some updates (mainly cosmetic). It would be nice you can merge with the current version.
There is branch called 'desi' that I created for Aaron and Cullan back in the days, which is rather old, and probably unused. I suggest we use this branch. What I can do is to update the 'desi' branch to the current version, and then you can try to see if you can merge yours?
Cheers
Pierre
PS : you can find my email clicking on my name on the README of this repo.

Hi Pierre,
Thanks for your reply. I talked to Arnaud about this, he is happy with merging to the desi branch, and then desilike can import that branch. I will make a pull request soon.
Best,
Yan Lai

Sounds good. I have just merged the master branch into the desi branch. You can start your merging now into the desi branch.

Hi Pierre,
Thank you very much. I compared my code to your updated code in the desi branch and noticed the following few main changes:

You have added the option "eft_basis". Looking at the code, this mostly just converts the counterterms from one bias basis to another.
You also made some changes to the nnlo terms. I actually haven't used these terms in my test, so I didn't make any changes to these terms.
For the correlation function. In my code, I have added a new way to compute the correlation function by Hankel transforming the power spectrum.
You also added the UV-match feature in the code.
In my version, I called "correlator.py" in your code "pybird.py", but I think the contents are the same.
In my code, when generating the model power spectrum, I always put Nl = 3. Then I will take the monopole and quadrupole during fitting.
When generating the stochastic term, in your code, you no longer divide it by self.co.nd. I guess this scaling is done during the fitting.  In my code, I still divide nd when generating the stochastic terms.
The default NFFT in the Fourier transform code is 512 in your code and 256 in mine.
For common.py, when you calculate powers of mu to Legendre polynomials, for the last element of the last row, it should be 48/143 instead of 48/148. I think this is just a typo in your code.
Your kbird in common.py also has a finer binning at low k.

I think except for 3 and 4, other changes probably won't have a large impact on the output. Unless you want me to make some changes first, I will commit the changes to the desi branch. Thanks.
Best,
Yan Lai

HI Yan,
Sorry for the slow reply. Thank you for checking all this! After some thoughts, here is what I think we can do. Could you merge first the master branch with your fork version in a new branch of your fork repo and test e.g., that the numbers in the likelihood notebook are stable after your changes? Once we are happy, we can then push easily to the official repo.
Generally speaking, in resolving conflicts let us try to be as close as possible to the last pybird version given that there are ongoing parallel developments that will be merged and that might be useful for desi in the future. Let me know if I can help.
A few remarks:
"3." Let's chat about this, I would be curious to know what you did there, sounds great!
"7." Division by nd is performed in pybird ('nd' is still an option to be specified), see here and here.
"8." Where do you see this? It seems to me that NFFT = 256 by default in current version
"9." Thanks!
Feel free to let me know what you get for the tests mentioned above!
Cheers
Pierre

Hi Pierre,
Thanks for your reply. I have been checking my version of pybird code with your latest version the last few days. I think they give consistent results. The new version of the code is on the master brach of my fork repo. I ran the likelihood notebook with my lastest code, the changes I found for chi-squared and best-fit bias parameters are very small. This new likelihood notebook is also available on the master branch of my fork repo.  I also tried to keep the code in my version as close as possible to the latest version. Here are the things I changed:

For the purpose of Template fit/Shapefit, I add an additional keyword argument "Templatefit" in the "compute" function in correlator.py. The default is set to False (Full-Shape analysis). If either template fit or Shapefit is used, this is set to True.
Also for template fit/Shapefit, I am using "correlator.bird" to store the template power spectrum. I made add another keyword argument for the following function to return the power spectrum instead of changing "correlator.bird" if template fit/Shapefit is used. These functions are "window", "xbinning", "xdata", "AP" in projection.py, "IRPs" in resum.py, added "set_shapefit" function in bird.py. However, their default setting assumes we are using Full-Shape fit.
For the Hankel transform. I added an additional input argument "corr_convert" for "self.c_catalog". The same argument is added to common.py. This is passed to common.py during initialization. There is also a new class "PowerToCorrelation" which I copied from Barry (https://github.com/Samreay/Barry/tree/master) in the bottom of correlator.py. This is used to do the Hankel transform. This is done in the "pk2xi_fun" function in correlator.py.
For the "formatTaylorPs" function in bird.py, I also included the stochastic terms at the end of the loop terms.
For the binning in k-space, in my code, I will create the binning matrix during initialization and the binning is accounted for by multiplying the binning matrix to the power spectrum. This does not require the user to input bin size, so I also commented out "if self.c["with_binning"] and self.c["binsize"] is None: raise Exception("Binning: on. Please provide 'binsize'.")" in the "__is_config_conflict" function in correlator.py. This is probably faster than doing the integration.
The NFFT=512 setting is in fourier.py.
The jupyter notebook with my lastest code is here https://github.com/YanxiangL/pybird/blob/master/notebooks/likelihood.ipynb.

Please let me know if you have any questions. Thank you.
Best,
Yan Lai

Dear Yan, thanks for your amazing job, and listing here the changes for references. I merged. Cheers


[test] Regression Tests for TCP

Description
We should add the following regression tests for TCP:

[ ] Deterministic hashmap
[ ] Random number of clients, connecting and disconnecting from each other randomly
[ ] Futzing for sending data, receiving data, half-closing, full-closing
[ ] Delay, drop, reorder, and duplicate packets randomly
[ ] Different MSS and TCP options
[ ] Invariant checks around resources getting freed
[ ] Resource limit scenarios

@ppenna , this may all be handled by the simulator now?


Create document for given testId, if not exists.

--id is provided to reused doc.
Current behavior is to fail if file not exists when --id is specified. Thus to reuse doc, id generated needs to be noted.
Instead changing behavior to create doc when doc doesn't exists with --id so we can create file with given id and reuse.
This helps in automations where it will be difficult to extract id from generated doc, but easier to provide an id to reuse.

@markfields Added doesDocumentExists in test driver.
Implemented only for odsp & local drivers, its not implemented for tinylicious & routerlicious drivers in this PR.
Please review.


bugs fix

https://github.com/orgs/PotLock/projects/8/views/22?pane=issue&itemId=54045215
https://github.com/orgs/PotLock/projects/8/views/22?pane=issue&itemId=54163788
https://github.com/orgs/PotLock/projects/8/views/22?pane=issue&itemId=54045215
https://github.com/orgs/PotLock/projects/8/views/22?pane=issue&itemId=54509986

Resolves https://github.com/PotLock/bos-app/issues/283
Resolves https://github.com/PotLock/bos-app/issues/293
Resolves https://github.com/PotLock/bos-app/issues/347


ImportError: No module named 'keras_en_parser_and_analyzer.library.classifiers'

Hi,
my
current python version: 3.5.3
Current O.S: Win 8.1
and when i download the git and run
python setup.py install
everything is installed properly
and i placed sample pdf in data/resume_samples/ and   when i execute
python ./demo/create_training_data.py
I get below error !

any pointers on same

Hi,
ok i understand the classifiers folder was not present on that path . i placed folder and this error was gone
but my question why it was referring from Appdata folder rather than actual project folder ?
another error crop up which require to install docx after installing the docx and executing below command
python ./demo/create_training_data.py
i am getting this error

i resolved this issue by going to and downloading
python_docx‑0.8.6‑py2.py3‑none‑any.whl from http://www.lfd.uci.edu/~gohlke/pythonlibs/
and resolves the whole issue now it is working expected

I am getting this error while running                 python create_training_data.py
Traceback (most recent call last):
File "create_training_data.py", line 7, in
from keras_en_parser_and_analyzer.library.dl_based_parser import line_types, line_labels
File "/usr/local/lib/python2.7/dist-packages/keras_en_parser_and_analyzer-0.0.1-py2.7.egg/keras_en_parser_and_analyzer/library/dl_based_parser.py", line 2, in
from keras_en_parser_and_analyzer.library.classifiers.lstm import WordVecBidirectionalLstmSoftmax
ImportError: No module named classifiers.lstm


custom update frequence

Thank you for the plugin!
Is it possible to force the plugin to send the GPS location every 0.5 seconds?

no


[Bug] MarkPoint does not auto clip to hide

Version
5.3.2
Link to Minimal Reproduction
No response
Steps to Reproduce
After MarkPoint uses y to set the offset, moving the dataZoom beyond the area will not automatically hide
option = {
  xAxis: {
    type: 'category',
    data: ['Mon', 'Tue', 'Wed', 'Thu', 'Fri', 'Sat', 'Sun']
  },
  yAxis: {
    type: 'value'
  },
  dataZoom: [{
    startValue: 'Wed'
  }],
  series: [
    {
      data: [150, 230, 224, 218, 135, 147, 260],
      type: 'line',
      markPoint: {
        data: [{
          y: '10%',
          value: 230,
          coord: ['Tue']
        }]
      }
    }
  ]
};

Current Behavior
MarkPoint is displayed outside the area
Expected Behavior
Auto hide after MarkPoint goes out of area

we are experiencing the same issue.  marklines seem to work fine but markpoints render outside of the chart clipping area.

same for heatmap


lookup subdomain with localhost option

Checklist

[ x] only relevant code is changed (make a diff before you submit the PR)
[x ] run tests npm run test
[ ] tests are included
[ ] commit message and code follows the Developer's Certification of Origin

Checklist (for documentation change)

[ ] only relevant documentation part is changed (make a diff before you submit the PR)
[ ] motivation/reason is provided
[ ] commit message and code follows the Developer's Certification of Origin

Can you also add a test?

.. but I have no clue about options.lookupFromSubdomainIndex
.. what is the goal of this property?
.. i never seen such url https://www.uk.foot-print-on-the-moon.org who actually use lang subdomains in the middle of a url?

was introduced in https://github.com/i18next/i18next-browser-languageDetector/commit/3f30f5b76eb72239a450474d744863e3269fa2c0 by @terhuerne

@handbremse The idea of this property was to be more flexible with the subdomain mapping. For instance a localized subdomain. Given:
https://partners.de.domain.com
In this case, the partners page can be localized through this subdomain. While this is not the most common case, we've seen this pattern in some business applications and therefore I've added this feature. As this is optional, I don't see an issue to keep it as a feature for those who need it.

@terhuerne is this PR approved from your side?
Can we merge it like that?

Yes, looks good.

Thank you @handbremse (and @terhuerne)... this was now released with v6.1.5.


Refactor project to be deployable in OCR-D

Adresses #2 #7 #6 #5 #1 and ports the code to python 3.
Only finished for the deskew code but the other scripts would be similar.
I'd strongly suggest to reuse the OCR-D/core Processor/CLI wrapper/XML API instead of the methods in utils.

It seems like most of the changes here have been copied to master.


As a developer, when running tests on windows, I would like to see checkmarks

The ✔/✖ chars show up as boxes in CMD. Mocha got around this by using fallbacks of √ instead of ✔, × instead of ✖

Much thanks @konsumer, I will be getting to this soon.

Hey @konsumer, would you mind being my tester for me?  The branch will be feature/windows-icons.

Looks good! This is in standard CMD:

Thanks for the fast fix!
For others coming here from google, I also solved it by using ConEmu

Awesome! Now I just have to tackle the testing, unfortunately it involves some changes with mocking so working to resolve that (I'm used to Jasmine, Mocha is so strange).

Maybe not the best place to ask this question, but is there a way to turn off check marks when piping to a text file? They make the file appear to be a non-text file when loaded into Atlassian Crucible. Thanks!


BUG: demo mode just up to 12 members

Describe the bug
When using the command Calculate_all() I get the error message that in demo mode just up to 12 members can be calculated.
To Reproduce
I have a mid-size model (around 100 members). When I use the command Calculate_all() I get the discribed error message. When I calculate everything explicitly with CalculateSelectedCases() everything is fine.
Expected behavior
I expect that all load cases, load combinations, adons etc. will be calculated.

Version of WIN11 Pro
Version of RSTAB9.03.0007
Version of tool v1.08.0

Additional context
Add any other context about the problem here.

Hi @scja1991,
we need more info to assess the situation. What type of license do you have? Are you sure you din't switch to demo? Can you share the model so we can test the calculation?

I am sure, that i have not switched to demo. I have a licence for RSTAB 9, Stress-Strain Analysis, Steel Design and Timber Design.
The RSTAB Model and my Python-Code are attached.
RSTAB_test.zip

Hello @scja1991. I tested this and I can't reproduce this error. Can you please verify, that this error still persisit in your system?
Tested on: RSTAB version: 9.04.007, tool verison 1.09.1. I opened your model and ran the attached script without any errors. Please get back to us, so we can figure this out. Thank you


Smaller number of plasmids and how to build a new database

Dear Sir,
mob-suite is an excellent tool, but interestingly, when I compared the number of plasmids in mobsuite and PLSDB, I found that mobsuite only includes over 20,000 plasmids while PLSDB has over 30,000. What causes such a large difference in quantity between the two? Did Mobsuite intentionally delete some low-quality plasmids from its database?
Also when I wanted to build a new database, I had a lot of trouble, despite checking some of the contents mentioned in many issues, I think there is still a lack of an effective script to do the job, is there a plan to come up with a detailed tutorial to make a database? Especially the meta information that needs to be entered.
You seem to be very busy at the moment and I hope to receive a reply in your free time.
Yours,
Dave

MOB-suite was not meant to be a comprehensive collection of every plasmid, as you have pointed out, there are several excellent examples of efforts designed to hold the diversity of all plasmids. To reduce the size and complexity of the database we will remove near-identical plasmids from the same species by preserving 1 per secondary cluster id. The databases were also build at different times and so will have different numbers of plasmids contained within them. Further, our curation efforts will only include plasmids >= 1500bp and <= 400,000bp. We also actively remove any records where the summary description mentions partial or incomplete, or specifically mentions genes or IS elements. We want to restrict to higher quality "complete" records for inclusion into the database. Also we are cautious about including integrative plasmids as those can complicate the results.  The documentation for the cluster module is definitely something we need to improve and is on our list to do for future releases.


Pass header as an option?

What would you like to discuss?
I want to use hooman with Python. Unfortunately I have little experience with JS and at the moment, I don't think it is possible to pass header (user agent, cookie, ...) to hooman. It would be nice if that were possible in the future.
Checklist

[x] I have read the hooman and got documentation.

Please read docs of https://github.com/sindresorhus/got/blob/master/readme.md, hooman is a wrapper around got.
hooman(url, {
	headers: {
		'user-agent': 'my_user_agent'
	}
});

I've tried it, but it doesn't work:
const got = require("hooman");

const url = "http://example.com";
const cookie = "myCookie=myValue";
const agent = "My-User-Agent";

got(url, {
    header: {
        'User-Agent': agent,
        'Cookie': cookie
        }
  })
  .then(response => {
    console.log('Header--->>>', response.request.options.headers)
  })
  .catch(error => {
    console.error(error);
  });

Header--->>> {
  'user-agent': 'Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.122 Safari/537.36',
  'cache-control': 'max-age=0',
  'upgrade-insecure-requests': '1',
  'accept-encoding': 'gzip, deflate, br',
  origin: 'http://example.com',
  referer: 'http://example.com/'
}

It's not header, it's headers. Please triple check your spelling.


Lookup Consumables in RTI

Function to lookup consumables in RTI in a more efficient way. Updates consumable dictionaries for fracture, laceration, and burn treatment from the same lookup function

Thanks very much for this @thewati
I'm noticing a conflict. Please could you resolve it?


BSC Mainnet is deployed and tested

Problem
BSC is possibly in scope of our public beta launch, depending on complexity.
Connector added with Defi Wonderland here https://github.com/connext/nxtp/pull/1766
Note per @LayneHaber
Defi wonderland tested the connector logic, but I just don’t know if you need to kick off a processing tx on mainnet
Ideas to solve this
Add full stack support for BSC

[ ] Deploy contracts
[ ] Subgraphs
[ ] Change config
[ ] Any liquidity provisioning

Acceptance Criteria

[ ] Bridging to and from BSC works fast path
[ ] Bridging to and from BSC works slow path
[ ]

@alexwhte
This task is blocked now!

contracts are deployed but multichain connector needs contract updates to get working which are already pointed out in audits

https://github.com/connext/nxtp/pull/2630


Adding handle to multiple MatchStatus.

Handling multiple status code

Pull Request Test Coverage Report for Build 567

15 of 15 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.1%) to 90.792%

Totals

Change from base Build 566:
0.1%

Covered Lines:
848

Relevant Lines:
934

💛  - Coveralls

Job #308 is now in scope, role is REV

@rultor merge it

@rultor merge it

@amihaiemil OK, I'll try to merge now. You can check the progress of the merge here

@rultor merge it

@amihaiemil Done! FYI, the full log is here (took me 2min)

Job gh:amihaiemil/docker-java-api#308 is not assigned, can't get performer

The job #308 is now out of scope

Payment to ARC for a closed pull request, as in §28: +10 point(s) just awarded to @amihaiemil/z


missing RF unlock operation notification

Is your problem within Home Assistant (Core or Z-Wave JS Integration)?
NO, my problem is NOT within Home Assistant or the ZWave JS integration
Is your problem within ZWaveJS2MQTT?
NO, my problem is NOT within ZWaveJS2MQTT
Checklist

[X] I have checked the troubleshooting section and my problem is not described there.

[X] I have read the changelog and my problem was not mentioned there.

Describe the bug
What causes the bug?
RF unlock operation notification only appears if the door was previously RF Locked.
What do you observe?
listening to the zwave notification nothing appeared when remote unlocking. i locked the door manually and noticed notifications were working.
What did you expect to happen?
RF unlock operation notification to appear every time
Steps to reproduce the behavior:

Go to '...'
Click on '...'
Scroll down to '...'
See error
Zwave.log
ive attached a file that shows me trying to capture it remote unlocking. you will see manually locked appears twice, in between that i remote unlocked the door. yet when tried remote locking then unlocking i saw a notification stating so.

Device information
Manufacturer: Yalw
Model name: Conexis L1
Node ID in your network:
How are you using node-zwave-js?

[ ] zwavejs2mqtt Docker image (latest)
[ ] zwavejs2mqtt Docker image (dev)
[ ] zwavejs2mqtt Docker manually built (please specify branches)
[ ] ioBroker.zwave2 adapter (please specify version)
[X] HomeAssistant zwave_js integration  (please specify version)
[ ] pkg
[ ] node-red-contrib-zwave-js (please specify version, double click node to find out)
[ ] Manually built from GitHub (please specify branch)
[ ] Other (please describe)

Which branches or versions?
version: 0.1.54
node-zwave-js branch:
Did you change anything?
no
If yes, what did you change?
No response
Did this work before?
Don't know, this is a new device
If yes, where did it work?
No response
Attach Driver Logfile
zwave_js (1).log

uploaded log from integration

First off: The driver does not generate any notifications unless the device sends them. Inconsistent behavior like this would have to be fixed in the device firmware.
I'm not sure I follow your description though. In the log I see two consecutive RF unlock attempts, both times the lock sends a Door Lock Report and a Notification with alarmType 25.
Then at the end there is a RF lock attempt, but this time there's no automatic report from the node at all and the driver validates the change by querying the lock status.

apologies I may not of given you the correct information in the logs.
I posted the problem on HA forum and someone else mentioned they had the same issue, and another stated everything was fine.
https://community.home-assistant.io/t/yale-z-wave-module-2-and-usb-z-wave-stick/64073/366
Would I be correct in saying the issue would be the same regardless if I was running ZWAVE-JS or ZWAVE-JSMQTT?

Would I be correct in saying the issue would be the same regardless if I was running ZWAVE-JS or ZWAVE-JSMQTT?

Both share the same Z-Wave implementation (this one), so yes.

Thank you
Also thank you for your support. I'll close this issue as it doesn't seem to be caused by zwave js


Ripleys don't get targeted by AI mobs

Description
Ripleys are basically immune to mobs because they don't get targeted, even when attacking said mobs. This trivialises any unknown creature events.

I could have sworn this issue was already posted like a year ago by this point.
In any case, this wasn't an issue back when the Ripley was a rare thing science could mess with but now that the Ripley is mapped in cargo, this should probably be fixed


Narrative documentation

Start writing narrative documentation as several notebooks that walk a user through what is here. This should be distinct from the examples/ we have.
Best broken down into several steps:

get the CI/deploy part ready
collect together issues like #123 #120 #118 ... which contain topics that need discussing
define the first chapter
start writing

Maybe we can refer to this (meta) issue every time there is a discussion/topic that should end up in the narrative documentation.

bump The longer we don't get started the harder it will be. Unfortunately I don't really know where/how to get started on this right now either.

Now since we have stable Circle Ci support, we should start being more specific about what examples that you (we) find lacking and add them to the Pull Request description.

The other good point from @glouppe is that with the examples we have already in form of notebooks we don't really need extra docs. I like that idea.

+1 for having narrative documentation as notebooks. This means that current notebooks certainly need some love in being more than code dumps, but at least we would avoid duplicating efforts while providing users with self-contained executable documentation.

👍
We should have a think about in which order new people should read the notebooks and such. Below a first suggestion on a "table of contents"

What is scikit-optimize and when should you use it/problems it can solve(?)
Bayes opt example that we currently have
example we can use as running example for the rest of the documentation(?)
visualizing and debugging your optimisation run
convergence rate
sample points/order
partial dependence
How to choose between different surrogate models
Tuning hyperparameters for GP models(?)
Tuning hyperparameters of tree models(?)
Applications
scikit-learn hyper-opt tuning
other applications

What is the difference between point 1 and 6?
How do you plan to order it, by just prefixing the notebooks with the numbers?
And finally, in 5 i] and 5 ii] does it include the description of the prior on the data, the conditional variance for different models?

For the ordering, we can hardcode the links on the left menu instead of auto-generating them.

I was thinking for 1. to be a short introduction "You might want to use skopt if you have X, Y and Z. For example: blah, foo, bar, baz" with a mathematical definition of the problem and outline of the algorithm in general terms. Similar to the beginning of the bayes-opt notebook. Then 6. is more "examples", ready made implementations people can use to get started doing blah, foo, bar or baz.
Not sure I understand your comment on 5. I was thinking we should give some ideas on how to choose between GP and trees and ... . Or if there is no good way to choose we should say "there is no good way, try them all". 5.i and 5.ii I was thinking to have some guidance on which parameters of the surrogate model you might want to tune in which situation.

Just an idea to give us some ideas where we already have material and where we need more. Obviously we can rearrange/cut/add as we see fit.


Project tokens

https://github.com/LLK/scratch-www/pull/6773#event-6664142265
Now that the token PR is merged, will it have an impact on meowclient?
@webdev03

meowclient doesn't use the projects API so I don't think so. Does it impact api.scratch.mit.edu ?

meowclient doesn't use the projects API so I don't think so. Does it impact api.scratch.mit.edu ?

I'm pretty sure it only affects projects.scratch.mit.edu, since the API doesn't show data for unshared projects anyway.


Don't display venn chart when running npm build.

In the development environment, the Venn diagram can be displayed, but once it is built (npm run build), it cannot be displayed, and the console message is "请检查是否存在图表容器dom节点,并设置好宽高".
Project is built by vuetify 3.4

@sam61086  Any online demo？It means "Please check if the chart container dom exists, and make sure the width and height are set."

@sam61086 Fix it in version 1.0.7, thanks for the issue.


Add a favicon

Description:
A favicon (favorite icon) depicts the identity of a particular website.
We can put the logo of this website as favicon.

This contribution is under GSSOC'24.

Please assign it to me
Thanks

hey can I start working on this ?


Replace Agahnim item by an eleventh dungeon

The main goal is to have the Castle Tower available as a dungeon to track in keysanity mode with its two small keys while combining Agahnim's status as a boss.
This also has the side-effect of including the dungeon on the location tracker. For now, it returns item availability according to normal modes, so it has no chests, just the boss itself. In the future there will be two chests available in the dungeon for keysanity logic.
You can test on my own firebase project: https://lttp-tracker-f0591.firebaseapp.com/

As is this will give errors when people try to use existing rooms (NaNs on smallkeys[11] from Firebase for example, and I think the default layout is expecting the agahnim item that no longer exists), Would you have time to look into ways to clean this up? I'm hesitant to merge this and break existing trackers, as most people probably aren't checking the changelog regularly.


[WIP] Add tests for remote repo in fsm scaffold tool

Proposed changes
This PR adds tests for remote repo in fsm scaffold tool
Types of changes
What types of changes does your code introduce? (A breaking change is a fix or feature that would cause existing functionality and APIs to not work as expected.)
Put an x in the box that applies

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

Checklist
Put an x in the boxes that apply.

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

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

That won’t work. This would only pass each time if we pushed abstract round abci skill and all it’s dependencies for each PR, not feasible. The remote case needs to be mocked

If this is the case then is a bigger issue than just a test failing in the CI since the package hash is hardcoded for abstract_round_abci and will be only updated at the release. So if the test fails in the CI the users won't be able to use the --remote flag when scaffolding a FSM.
We can fix this by either making the hash constant configurable using env var or adding a CLI arg to pass down the latest hash for abstract round package

That won’t work. This would only pass each time if we pushed abstract round abci skill and all it’s dependencies for each PR, not feasible. The remote case needs to be mocked

If this is the case then is a bigger issue than just a test failing in the CI since the package hash is hardcoded for abstract_round_abci and will be only updated at the release. So if the test fails in the CI the users won't be able to use the --remote flag when scaffolding a FSM.
We can fix this by either making the hash constant configurable using env var or adding a CLI arg to pass down the latest hash for abstract round package

No it's no bigger issue. The package is hard coded (there is no other way) and during development no-one needs to be able to fetch it remotely. At release the package is available remotely. We do the same in open-aea for open_aea/signing protocol.
No-one wants to have to find out what hash to use - horrible ux


System test: Implement resource descriptor validation

part of: https://github.com/creek-service/creek-kafka/issues/56

Extend KafkaResourceValidator to validate resource groups
Extend KafkaTopicDescriptors and KafkaTopicConfigs to support calculating a consistent hash code from topic descriptors. This is used to detect mismatched descriptors
Fix Bug in  KafkaResourceValidator where it wasn't validating the config of creatable topic descriptors.
Moved shared code out of KafkaTopicConfig and into KafkaTopicConfigs
Fixed inconsistent getter style in KafkaTopicConfig
Removed ValidatingTestListener as this type of validation is now done within ResourceInitializer.

Reviewer checklist

[ ] Ensure relevant issues are linked (description should include text like "Fixes #")
[ ] Ensure any appropriate documentation has been added or amended

Coverage increased (+0.1%) to 98.152% when pulling f53f7565112d886d30ce0c969161b4c43e7a778e on validate_resource_groups into 6c188939d0098256e4d78831c8b2f2ebe0edea75 on main.


RBAC ClusterRole Issues using Helm Chart

I just deployed the stable helm chart and noticed a lot of RBAC errors.
Example:
ERROR: logging before flag.Parse: E0713 20:01:18.423061       1 reflector.go:205] github.com/bitnami-labs/kubewatch/pkg/controller/controller.go:377: Failed to list *v1beta1.ReplicaSet: replicasets.extensions is forbidden: User "system:serviceaccount:default:kubewatch" cannot list replicasets.extensions at the cluster scope
ERROR: logging before flag.Parse: E0713 20:01:18.423344       1 reflector.go:205] github.com/bitnami-labs/kubewatch/pkg/controller/controller.go:377: Failed to list *v1beta1.Deployment: deployments.apps is forbidden: User "system:serviceaccount:default:kubewatch" cannot list deployments.apps at the cluster scope
ERROR: logging before flag.Parse: E0713 20:01:18.519104       1 reflector.go:205] github.com/bitnami-labs/kubewatch/pkg/controller/controller.go:377: Failed to list *v1beta1.DaemonSet: daemonsets.extensions is forbidden: User "system:serviceaccount:default:kubewatch" cannot list daemonsets.extensions at the cluster scope

I had to update my RBAC setting to the below settings to get all errors to go away - basically added extensions, apps, and batch to the apiGroups rule-set.
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
  labels:
    app: kubewatch
    chart: kubewatch-0.4.1
    heritage: Tiller
    release: kubewatch
  name: kubewatch
rules:
- apiGroups:
  - ""
  - extensions
  - apps
  - batch
  resources:
  - pods
  - jobs
  - namespaces
  - services
  - deployments
  - replicationcontrollers
  - replicasets
  - daemonsets
  verbs:
  - list
  - watch

We are running kubernetes v1.8.7 with RBAC.

@bfreezy That's great. If you were able to get this working, feel free to submit a PR with your working RBAC configs.

Just add this:
rules:
- apiGroups:
  - ""
  - extensions
  - apps
  - batch
  resources:
  - pods
  - namespaces
  - services
  - deployments
  - replicationcontrollers
  - replicasets
  - daemonsets
  verbs:
  - get
  - list
  - watch

It'd be good to update https://github.com/bitnami-labs/kubewatch/blob/master/kubewatch-service-account.yaml with the above too 😃

You'll also need to add .spec.serviceAccountName: kubewatch to the pod configuration so it takes the defined cluster role (https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/)


Cannot reproduce videochatgpt video benchmark

Dear author, I found that in your paper, you claimed a very impressive performance on videochatgpt video benchmark. However, I didn't find related code about reproducing this experiment. So I modified the mvbench evaluation code to inference on this task. But I can't reproduce it.

What I got is:

The model is the right one because I used the same model and reproduced the performance on MVbench.
So the only difference might be the different prompt used when testing the dataset, however I can't really believe that a different prompt can lead to such a big difference.
So could you please give me the prompt used when testing this benchmark or the inference result of this? Extraordinary claims require extraordinary evidence.

Can you reproduce the results of other models？ Recently, one paper revealed that the GPT version affects the final results.

I have checked the history and we use gpt-3.5-turbo by default. Considering the testing time, we may use gpt-3.5-turbo-1106 and the results are as follows:
completed_files: 1996
incomplete_files: 0
All evaluation completed!
Average score for correctness: 3.020541082164329
completed_files: 1996
incomplete_files: 0
All evaluation completed!
Average score for detailed orientation: 2.875250501002004
completed_files: 1996
incomplete_files: 0
All evaluation completed!
Average score for contextual understanding: 3.509018036072144
completed_files: 499
incomplete_files: 0
All evaluation completed!
Average score temporal understanding: 2.661322645290581
completed_files: 499
incomplete_files: 0
All evaluation completed!
Average score for consistency: 2.8076152304609217

Hi, we will close this issue.
Feel free to contact us if you have other questions.


[TASK] Longhorn 1.4, Bump K8s min version support, CSI sidecar versions, dependent lib version

What's the task? Please describe
For each feature release, we should revisit if need to bump the minimum support version of K8s and K8s dependent libraries based on different reasons like K8s support version cycle, the minimum versions of K8s used by CSI sidecar components planned to deliver/support (like recent snapshotter), etc.
Describe the items of the task (DoD, definition of done) you'd like

Please use a task list for items on a separate line with a clickable checkbox https://docs.github.com/en/issues/tracking-your-work-with-issues/about-task-lists

[ ] Bump to the recent versions of K8s dependent libraries if needed
[ ] Update the min version support of K8s if needed
[ ] Update CSI sidecar versions if needed
[ ] Update golang version

ref: #4003

Issues to solve for kubernetes 1.25 support:
PSP https://github.com/longhorn/longhorn/issues/4003
PDB https://github.com/longhorn/longhorn/issues/4689
Cronjob https://github.com/longhorn/longhorn/issues/3160#issuecomment-947007800

About removed deprecated versions, it will be tackled at https://github.com/longhorn/longhorn/issues/4003 together with PSP.

Test plan
(in-progress)

Test generate support bundler generation
Test upgrade
Test zone and topology
Test uninstallation

Todo:

Upding docs:

github.com/container-storage-interface/spec v1.3.0
Min Kubernetes 1.21
User need to deploy new snapshot v1 CRD: VolumeSnapshot v1beta1 is deprecated and will be removed in a future release. It is recommended for users to upgrade to VolumeSnapshot CRD version v1 as soon as possible. Any previously created invalid v1beta1 objects have to be deleted before upgrading to version 4.1.0. (https://github.com/kubernetes-csi/external-snapshotter/pull/493, @xing-yang)

Verify CSI snapshot upgrade

install Longhorn <= 1.3.2
Enable CSI Snapshot Support on a Cluster https://longhorn.io/docs/1.3.1/snapshots-and-backups/csi-snapshot-support/enable-csi-snapshot-support/
Create some CSI snapshot https://longhorn.io/docs/1.3.1/snapshots-and-backups/csi-snapshot-support/csi-volume-snapshot-associated-with-longhorn-snapshot/
Upgrade to Longhorn master
Upgrade the CSI snapshot CRDs to the version v5.0.1 here: https://github.com/kubernetes-csi/external-snapshotter/tree/v5.0.1/client/config/crd
Upgrade the CSI snapshot controller to the version v5.0.1 here: https://github.com/kubernetes-csi/external-snapshotter/tree/v5.0.1/deploy/kubernetes/snapshot-controller
Create some new CSI snapshot https://longhorn.io/docs/1.3.1/snapshots-and-backups/csi-snapshot-support/csi-volume-snapshot-associated-with-longhorn-snapshot/
Verify that everything is working as expected

Case 1: within a Kubernetes version
Verified on v1.25.3+k3s1

[ ] Test basic recurring snapshot/backup jobs are working correctly

v1.25.3+k3s1  - Verified on local environment
v1.24.7+k3s1
v1.23.1+k3s2
v1.22.15+k3s1
v1.21.10+k3s1

[ ] Test generating support bundler generation. Make sure that the above jobs are in /yamls/kubernetes/cronjobs folder

Verified manually

Case 2: Test a Kubernetes version upgrade - Pass

[ ] Update from v1.24.7+k3s1 to v1.25.3+k3s1 and workload still working properly

Install Longhorn master in Kubernetes v1.24 cluster
Create some workload, Longhorn volumes, cronjobs, etc...
Upgrade Kubernetes to v.125
Verify that Longhorn is running ok. Basic functionality is working ok

Verified passed on master-head by following the test plan.
(1-1) Test basic recurring snapshot/backup jobs are working correctly:

covered in (1-5) e2e test

(1-2) Create recurring jobs and generate support bundle, make sure the corresponding recurring jobs are in /yamls/kubernetes/cronjobs folder:

manually verified passed in [ v1.21.10+k3s1, v1.22.9+k3s1, v1.23.7+k3s1, v1.24.7+k3s1, v1.25.3+k3s1 ]

(1-3) Test Longhorn upgrade from 1.2.x or 1.3.x to master + CSI snapshotter upgrade from release-4.0 to v5.0.1, make sure upgrade successfully, basic functionalities work, and CSI snapshot functionality works (following the test steps in the test plan):

manually verified passed in [ v1.21.10+k3s1, v1.22.9+k3s1, v1.23.7+k3s1, v1.24.7+k3s1, v1.25.3+k3s1 ]

(1-4) Test zone and topology (following the test steps in the test plan):

manually verified passed in [ v1.21.10+k3s1, v1.22.9+k3s1, v1.23.7+k3s1, v1.24.7+k3s1, v1.25.3+k3s1 ]

(1-5) Test uninstallation:

manually verified passed in [ v1.21.10+k3s1, v1.22.9+k3s1, v1.23.7+k3s1, v1.24.7+k3s1, v1.25.3+k3s1 ]

(1-6) e2e tests:

v1.21.10+k3s1, v1.22.9+k3s1, v1.23.7+k3s1, v1.24.7+k3s1, v1.25.3+k3s1

(2) Test k8s version upgrade (following the test steps in the test plan):

manually verified passed by upgrade k8s from v1.24 to v1.25


No community catalog when using external database

Fresh installation on RancherOS v1.0.3
When specifying an external database at creation time, the community catalog is missing. The whole 'add to catalog' function appears broken.
sudo docker run -d --restart=unless-stopped -p 8080:8080 rancher/server --db-host rancher.cszh9ee4nl51.ap-southeast-2.rds.amazonaws.com --db-pass <redacted>
Even when I manually add a catalog, it will never show up.
https://git.rancher.io/community-catalog.git
If I do not specify an external database, it appears as normal. ie:
sudo docker run -d --restart=unless-stopped -p 8080:8080 rancher/server
|Versions|Rancher v1.6.5 Cattle: v0.182.1 UI: v1.6.9 |
|Orchestration|Cattle|

Sorry guys, this is actually my fault. It is not a bug, but I will not delete this as it may help someone else in the future.
The issue was caught when I peeked into the docker container logs.
time="2017-07-20T23:24:02Z" level=error msg="Failed to perform catalog refresh: community: Error 1105: Parameter of prepared statement which is set through mysql_send_long_data() is longer than 'max_long_data_size' bytes"
By default, if you're running an RDS instance with AWS, the max_allowed_packet value is set too low. I set up a custom parameter group and set this value to
max_allowed_packet =<PHONE_NUMBER> and this fixed the issue for me. Hope this helps someone else.


Host name check now ignores case

We encountered an issue where a hostname of "Sitemap.xml" broke
our site at runtime, since the system expected "sitemap.xml".
This fix makes that check ignore case. It also adds tests to prove the
fix. In order to make the method testable, it was made public
(this seemed like the least intrusive way of fixing it, and
it is a static method without side effects, so it being public
should not be an issue.
I unfortunately do not have VS 2013 on my dev machine at the moment, so I've also updated the solution file to VS2015 format.

@JoachimL could you please update this PR with the latest changes?

Yes, will do ASAP.
On Tue, 8 Nov 2016, 23:56 Frederik Vig<EMAIL_ADDRESS>wrote:

@JoachimL https://github.com/JoachimL could you please update this PR
with the latest changes?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Geta/SEO.Sitemaps/pull/41#issuecomment-259285933, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAmVbrx48XLXZfEda6Np-Ztgkvu-EJsOks5q8P4ygaJpZM4KWvtT
.

@JoachimL: repeating myself, but as previously mentioned you did a lot of the the same things as I did in #39, so you will probably have to implement the same changes as well, including moving and renaming the unit test directory. But there already is a unit test project, so you might as well just add your test file to the test/Geta.SEO.Sitemaps.Tests/ project, rather than wait for yet another round where you'll probably be told the same 😃
The end diff will be quite a bit smaller too (one new file and two modified files).

Right. Will give it another go.
On Wed, 9 Nov 2016, 16:26 Carl-Erik Kopseng<EMAIL_ADDRESS>wrote:

@JoachimL https://github.com/JoachimL: repeating myself, but as
previously mentioned you did a lot of the the same things as I did in #39
https://github.com/Geta/SEO.Sitemaps/pull/39, so you will probably have
to implement the same changes as well, including moving and renaming the
unit test directory. But there already is a unit test project
https://github.com/Geta/SEO.Sitemaps/blob/master/test/Geta.SEO.Sitemaps.Tests/CompressionHandlerTest.cs,
so you might as well just add your test file to the
test/Geta.SEO.Sitemaps.Tests/ project
https://github.com/Geta/SEO.Sitemaps/blob/master/test/Geta.SEO.Sitemaps.Tests/,
rather than wait for yet another round where you'll probably be told the
same 😃
The end diff will be quite a bit smaller too (one new file and two
modified files).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Geta/SEO.Sitemaps/pull/41#issuecomment-259441240, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAmVbjedDyC5ON-6nl-DnE6OmfSL1jK5ks5q8eYTgaJpZM4KWvtT
.

Hi @JoachimL any updates on this?


CLDR v24 and pluralization

The upcoming release of the CLDR, v24, will make substantial changes to the pluralization rules. See https://docs.google.com/document/d/155ZJOHtOgnm8P80TDL8QGfNZ-wNoqsRNRGHRfJB4JGs/edit?pli=1 for the draft.
I wonder if there are any plans to support these or if we should prepare to embed the computation of the new variables into the rules if we want to use that data.

@bdurand Could you please submit a PR to fix up these breakages?

It looks like the Unicode Consortium rolled back the change to Russian pluralization in CLDR version 25 on March 18, 2014 to have the "few" rule again so my issue is solved.

Great! Then I am going to go ahead and close this issue.


penumbra.util.tendermint_proxy.v1.TendermintProxyService.GetBlocksByHeight seems broken

Describe the bug
GetBlocksByHeight fails to respond for any attempted height
To Reproduce
Steps to reproduce the behavior:

Go to https://grpcui.testnet.penumbra.zone/
Use Service name penumbra.util.tendermint_proxy.v1.TendermintProxyService
Use Method name GetBlockByHeight
Input a valid height
Invoke

Expected behavior
Block data is returned
Screenshots

I'm trying to write a test script for it locally but having some trouble.
I can call it with grpcurl at least, but the golang protobuf library isn't playing nicely with the way cometbft encoded timestamps:
grpcurl -d '{ "height": 326710 }' grpc.testnet.penumbra.zone:443 penumbra.util.tendermint_proxy.v1.TendermintProxyService.GetBlockByHeight
Failed to format response message 1: ns out of range [0,<PHONE_NUMBER>)

and I can't find a command line flag to tell grpcurl to print the raw response
I then tried writing a test script in Rust, and was able to call against localhost, but not the testnet endpoint:
let mut tm_client = TendermintProxyServiceClient::connect("http://localhost:8080").await?;
let r = tonic::Request::new(GetBlockByHeightRequest { height: 326_710 });
let res = tm_client.get_block_by_height(r).await?.into_inner();

^^ that works
let mut tm_client = TendermintProxyServiceClient::connect("https://grpc.testnet.penumbra.zone:443").await?;
let r = tonic::Request::new(GetBlockByHeightRequest { height: 326_710 });
let res = tm_client.get_block_by_height(r).await?.into_inner();

^^ that doesn't:
Error: Status { code: Internal, message: "protocol error: received message with invalid compression flag: 52 (valid flags are 0 and 1) while receiving response with status: 404 Not Found", metadata: MetadataMap { headers: {"content-type": "text/plain; charset=utf-8", "x-content-type-options": "nosniff", "content-length": "19", "date": "Tue, 04 Jun 2024 17:54:11 GMT"} }, source: None }

I have no idea why it would get a 404 on grpc.testnet.penumbra.zone but not localhost, especially considering that I was able to grpcurl the endpoint.

The underlying issue with using grpcui to call is the same golang parsing issue. If you use the Chrome network inspector and check the response you'll find:
  "responses": [
    {
      "message": "ns out of range [0,<PHONE_NUMBER>)",
      "isError": true
    }
  ],

Figured it out, that was Tonic feature flags.
I'm able to call the API from rust code now and get a response so I don't think the API is actually broken however there is an issue in that historical data is unavailable post-upgrade. I know @conorsch has been looking at things in that domain, maybe there's a fix?

nanos from the endpoint appear to be negative, which is against spec
https://github.com/protocolbuffers/protobuf/blob/bf7ac9f2f11e15c1a8f4b41428a75ad1c039a8fe/src/google/protobuf/timestamp.proto#L133-L144
message Timestamp {
  // Represents seconds of UTC time since Unix epoch
  // 1970-01-01T00:00:00Z. Must be from 0001-01-01T00:00:00Z to
  // 9999-12-31T23:59:59Z inclusive.
  int64 seconds = 1;

  // Non-negative fractions of a second at nanosecond resolution. Negative
  // second values with fractions must still have non-negative nanos values
  // that count forward in time. Must be from 0 to 999,999,999
  // inclusive.
  int32 nanos = 2;
}

notably, timestamp with negative nanos are unable to re-transmit to the client through our web communication channel

Using an int32 to hold a value that's supposed to be positive is chaotic

https://github.com/tendermint/tendermint/blob/35581cf54ec436b8c37fabb43fdaa3f48339a170/spec/consensus/signing.md#timestamp

Timestamp validation is subtle and there are currently no bounds placed on the timestamp included in a proposal or vote. It is expected that validators will honestly report their local clock time.

Closing as this isn't actually "broken" (well besides the nanos thing) and we need to build our own RPC endpoint


Parameters declared in components don't retain required: true

If we declare a parameter in this way:
components:
  parameters:
    SomeHeader:
      - name: SomeHeader
        in: header
        required: true
        schema:
          type: string

And then use it somewhere:
paths:
  /foo:
    get:
      parameters:
        - $ref: "#/components/parameters/SomeHeader"

Then the result will not be required.  Adding required: true parallel to the $ref line seems not to work either.  Inlining the definition does work.

This is because when we deal with parameters, $ref is Deferred immediately, but the resulting core.Resolved unpack does not include required.
The easiest solution is to apply the same dereferencing logic here, in RouteMeta. This sort of keeps digging the wrong direction, but at least there's prior art.
A more general solution requires a bit more thinking, I think. I hesitate to smuggle the original Schema[_] along with the internal guardrail DTOs, since that's redundant information instead of deriving truth, but I also hesitate to just turn the guardrail DTOs into direct copies of the OpenAPI models.

I ran into this for another reason, so I'm taking a crack at this.


Edited EDA_categorical.py tests

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@ffd20f9). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #99   +/-   ##
=========================================
  Coverage          ?   67.79%
=========================================
  Files             ?       33
  Lines             ?     1618
  Branches          ?        0
=========================================
  Hits              ?     1097
  Misses            ?      521
  Partials          ?        0

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 ffd20f9...bd7623f. Read the comment docs.

This PR contains now categorical plots and count plots with tests


can't build lagoon/keycloak because of missing yum command in container

Describe the bug
Make build stops at building the keycloak image.
docker build --quiet --build-arg LAGOON_VERSION=v1.1.4 --build-arg IMAGE_REPO=lagoon -t lagoon/keycloak -f services/keycloak/Dockerfile services/keycloak
Sending build context to Docker daemon  82.94kB
Step 1/23 : ARG IMAGE_REPO
Step 2/23 : FROM ${IMAGE_REPO:-lagoon}/commons as commons
 ---> 2b3153a22f87
Step 3/23 : FROM jboss/keycloak
 ---> b642d96ad2e5
Step 4/23 : USER root
 ---> Using cache
 ---> c9c1c9393fa0
Step 5/23 : RUN yum install -y nc     && yum clean all     && rm -rf /var/cache/yum
 ---> Running in 67d21a74a548
/bin/sh: yum: command not found
The command '/bin/sh -c yum install -y nc     && yum clean all     && rm -rf /var/cache/yum' returned a non-zero code: 127
make: *** [build/keycloak] Error 127```

**To Reproduce**
1. Checkout amazeeio/lagoon on tag 1.1.4 (on macos 10.13 but that not really relevant)
2. run make build
3. wait a long time until the process starts to build lagoon/keycloak
4. the error mentioned above appears.

**Expected behavior**
That the build process continues ;)

**Additional context**
Docker engine 19.03.4, compose 1.25.0-rc on Docker Desktop <IP_ADDRESS> (edge) running on MacOS 10.13

@renebakx are you running the latest lagoon? this (and some other keycloak dockerfile changes) was fixed on master already: https://github.com/amazeeio/lagoon/commit/6baa98f6d0ba903bddaad18351bde9f0995fe377

@renebakx are you running the latest lagoon? this (and some other keycloak dockerfile changes) was fixed on master already: 6baa98f

nope, not master. Wanted to test it with a tagged release. Policy forbids me to run not tagged code in production. But given it is a sandbox / testing env. I can get away with it for now ;)
Thanks! Closing this issue :)


Heat capacity bootstrapping

Description
Implemented bootstrapping scheme for computing heat capacity curve with uncertainty, and several other observables:

Melting point (based on max C_v value)
Height of C_v peak (based on max_Cv - min_Cv)
Full width half maximum (for curves which only have 1 side within the temp range used, estimated as 2x half width half maximum based on the one side)

We can now specify the confidence interval to return for all of the above calculations.
The bootstrapping significantly improves the smoothness of the heat capacity curve itself, since there are 2 elements of randomness involved in selecting the decorrelated energies which allow all frames to be used:

Randomly select the starting frame over the interval (frame_begin to frame_begin+decorrelation time), and then slice the uncorrelated energies.
Resample from those uncorrelated energies, with replacement.

Status

[ ] Ready to go

Codecov Report

Merging #113 (64ff963) into signac_workflows_2_1_21 (5fbcfda) will increase coverage by 0.97%.
The diff coverage is 99.05%.


Accessibility Audit - Carbon Website: Components - Overflow menu

This epic is tied to a larger "release" that is meant to track the progress of the Accessibility Audit for the Carbon Website. We will audit all of the pages of the carbon website based on AVT 1, AVT 2, & AVT3 - which can be found here.

AVT 1: will audit the site against the IBM Accessibility Checker - browser extension

AVT 2: will audit the site against accessible keyboard interactions

AVT 3: will audit the site against screen readers

Legend:

🌶 fully audited - on all three AVT levels

:one: 🔍 AVT 1 audited
:two: 🔍 AVT 2 audited
:three: 🔍 AVT 3 audited

:boom: issues and documentation - on all three AVT levels are complete

:one: 🚨 AVT 1 issues submitted
:two: 🚨 AVT 2 issues submitted
:three: 🚨 AVT 3 issues submitted

:sparkles: tickets are triaged

Current status of this page: 1⃣ 🔍 AVT 1 audited & 🚨 AVT 1 issues submitted

Components - Overflow menu

Usage: 6 issues - no new issues
Style: 6 issues - no new issues
Code: 6 issues
Accessibility: 3 issues - no new issues

Closing due to inactivity. Will reopen if/when ready to be worked on again.


Fix the example provider with the default ccxt feed

Thanks for the fix, the example provider has now been moved to different repo


[Dart FFI] How to pass Struct list from Dart to C/C++ Using FFI?

Cpp side:
struct MyStruct {
  char* address;
  int32_t port;
};

bool Connect(MyStruct address[], uint32_t address_sizes) = 0;

Dart side:
class MyStruct extends Struct {
  Pointer<Utf8> address;

  @Int32()
  int port;
}

How to pass Struct list from Dart to C/C++ Using FFI?

At least in C, an array is just the pointer to the first element, so you can do this:
typedef _connect_native = Int8 Function(Pointer<MyStruct> address, Uint32 addressSizes);
typedef _connect_dart = int Function(Pointer<MyStruct> address, int addressSizes);

final library = DynamicLibrary.open(path);

final function =
    library.lookupFunction<_connect_native, _connect_dart>('Connect');
final array = malloc<MyStruct>(10);
function(array, 10);
free(array);

At least in C, an array is just the pointer to the first element, so you can do this:
typedef _connect_native = Int8 Function(Pointer<MyStruct> address, Uint32 addressSizes);
typedef _connect_dart = int Function(Pointer<MyStruct> address, int addressSizes);

final function =
    library.lookupFunction<_connect_native, _connect_dart>('Connect');
final array = malloc<MyStruct>(10);
function(array, 10);
free(array);

Hello @simolus3 , can I transfer existing data:
void connect(List<MyStruct> data) {
  // How to convert data into pdata?
  final pdata;
  final size = data.length;
  function(pdata, size);
}

Sure, but you'll have to copy:
final cArray = malloc<MyStruct>(data.length);
for (var i = 0; i < data.length; i++) {
  final source = data[i];
  final dest = cArray[i];
  dest
    ..address = source.address
    ..port = source.port;
}

function (cArray, data.length);
free(cArray);


Add valid badge # check on Violations create page

RSO was "testing" App by creating a new violation and used "Admin (xyz)"
DELETE FROM BadgeDB.violations WHERE (id = '1164');

Why is there a fake user in the real Database???

force check on violation page actual violation


Parsing bug in HttpConnection::get and HttpConnection.Response::parse

While working on an application that downloads and parses RSS files from packetstormsecurity.com I've found a strange behaviour: Sometimes when selecting a pubDate entity from an item entity, Jsoup would continue parsing past the closing pubDate tag and into the next entity.
This seems to be caused by the above mentioned methods introducing the html character codes for < and > (< and > respectively) while parsing the string </pubDate>, resulting in a pubDate entity looking like this <pubDate>Tue, 06 Jun 2017 14:06:27 GMT</pubDate>, causing the parser to overshoot.
The bug only happens on very rare occasion for the above mentioned website, I'd guess about one to five in one thousand pages.
Since the above mentioned website is posting new items multiple times per day and thus the affected pages change, the code contains a method to find bad pages. When a bad page is found, the code will download and parse it thrice, once for each of the affected methods and once with a workaround, which uses Jsoup::parse and passes the body of the HttpConnection.Response object obtained from Connection::execute.
I've created a repo that contains a MCVE to reproduce the probable bug.  Versions less than 1.10.18 are affected.
 Versions less than 1.10.18 are affected.
 Could you modify the test to write out the bad URLs and note them here? If a URL is bad, is it always bad, or does that vary?

Since the above mentioned website is posting new items multiple times per day and thus the affected pages change, [...]

The affected pages change and it seems like they are not tied to specific items in the rss feed, meaning that if an items moves from page x to page x+1 and page x was affected, page x+1 won't necessarily be affected.
I've just added a method that prints all affected pages as they're found.
Another curious thing I've forgot to mention is that whether a page is affected or not changes based on if the url supplied to Jsoup::connect has a trailing slash or not.

Could you save the HTML from one of the failed pages?
If you get a URL that fails and immediately reload it, does it still fail? I'm trying to determine if it's deterministic based on the content, or what.

Yeah, downloaded some pages and added them to the repo. As far as I can see, a URL will stay bad for at least as long as the xml on the server does not change.

Thanks, will take a look. Guessing it's a similar issue to #967 maybe.

Thanks for reporting this and the test repro. I've committed a fix.
The problem was that the TokeniserState checked if the CharacterReader was empty before trying to read an end tag, and the isEmpty() method didn't buffer in new contents. So if an end tag just happened to be on a buffer read boundary, isEmpty() would return false, and would cause the tokenizer to read the next section as plain text given its fallback path.
Fixed by making isEmpty do a buffer up when called externally (not when internal, which would mix the bufPos counter up).


Typo at Demo Scene

Hello There!
I've spotted a small typo on the naming of one of the sprites in the Demo Scene.

It should be "Stopwatch", but instead it's "Stropwatch"

Thank you for your Plugin, I really appreciate your effort.

You're welcome. And thanks for letting me know; the misspelling should be fixed by now.


[Star Trek Armada] Doesn't start

Windows 10, Nvidia GTX 960
I've installed a fresh copy of Armada, to remove every trace of old tools, but your fix doesn't seem to work. It crashes on startup, before even the menu. On the Fleetops forum, you ask for a ddraw-armada.log, but it's not generating one of those at all. The closest thing is draw-splash.log, which generates from running Splash.exe and clicking "play", which I've attached. Running Armada.exe simply shows the orange Armada box for a moment, and then crashes.
ddraw-splash.log

@Cerxi, If you are not seeing a ddraw-armada.log file then it means that the wrapper is not getting loaded.  Try renaming the two files to dsound.dll and dsound.ini, respectively.

The game still crashes, but now it crashes about twice as fast, and it does generate a log file
dsound-armada.log

I tested yesterday also and found an old compatibility setting set in windows registry
open the regedit.exe and go to
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers
and delete any armada compatibility setting

I've done as thunderchero suggested, and gone through the registry for any other lingering Armada compatibility settings, but even after paring those out, no change.

From your log file it looks like your configuration file is wrong.  I see an error message:
204796 13:45:02.114 Cannot load custom library: E:\Games\Star Trek - Armada

Can you send me your ini file?

I haven't changed it from the download, but here
ddraw.zip

Can you send me your dsound.ini file?  This is the file that seems to have some wrong settings.  Also are you using both ddraw.dll and dsound.dll?  You can only use one or the other.  If you are using dsound.dll you need to delete ddraw.dll, and vice versa.
You need to either have this:

ddraw.dll
ddraw.ini

Or this:

dsound.dll
dsound.ini

I did find an issue with the old version of the files.  Try with this new one if you still have an issue:
dsound.zip

That was the dsound.ini file, I renamed them back to ddraw at some point, sorry. I never had both at once.
I've tried with the new version, but it still crashes:
dsound-armada.log

Hello Cerxi,
I am still unable to reproduce this, but there are a few more things you can try:

Delete "ARMADA.PRF" file from the Start Trek Armada 1 folder.

Try setting the following compatibility settings:

Here is an updated patch.  This uses both ddraw.dll and dsound.dll.  Copy all four files from this zip into your Start Trek Armada 1 folder, overwriting any existing file.  ddraw.zip

If this does not work please send me your "dxwrapper-armada.log" log file.
Note: you can also try opening the "dxwrapper.ini" file and setting DDrawCompat equal to 0 to disable it.  This will break the menu animations, but may allow you to get the game working.

Sorry, took me a few days to get back to my email. Unfortunately, still doesn't work, even with compatibility settings, or with DDrawCompat set to 0. dxwrapper-armada.log

@Cerxi, I think this might be some setting with either Windows or with your graphics card.  Here are some things you might want to try:

Disable high DPI scaling in the Display Properties of your video card, by setting Scale and layout to 100%.  It is recommended to restart after this change.
Make sure you are using the latest Nvidia driver.
Disable vertical sync and G-Sync (if you have it) in your graphics card settings.
Check if you have an Nvidia profile setup for Armada and verify the settings are correct there.
Make sure you have installed both Armada patch 1.2 and Armada patch 1.3.  Patch 1.2 needs to be installed first.
Try using this ARMADA.PRF file.

Let me know if any of these help you or not.

So, embarrassingly, it turns out I didn't have 1.3 installed. After installing that, everything works (as long as I keep it in Win7 compatibility mode).

I doubt if this will help but only way I can get Armada to load is to execute the armada.exe from install path. start menu short cuts crash every time.

@Cerxi, great!  I am glad you got it working!
@thunderchero, sounds like you need to recreate the Start Menu item.

@Cerxi, I updated the wiki.  Would you mind testing with the lasted patch from the wiki to make sure it still works.

Delete ddraw.dll, dsound.dll, dxwrapper.dll and dxwrapper.ini from your Armada folder.
Download the updated patch files from the wiki.

Please let me know if this works or not for you.  Thanks!

Confirmed, it works. Actually, this one works even without compatibility settings on

Ok, thanks for testing it!  I am closing the issue since it is now fixed.


Cut-off messages

Feature Request
Desired behaviour
Message also seemed a bit unclear to me, suggestions welcome

┆Issue is synchronized with this Jira Story
┆Issue Type: Story
┆Fix Versions: Dockstore 1.8
┆Issue Number: DOCK-1149

"non-standard" sounds judgemental. :) Not sure what to say though.

So it appears mat radio button content intentionally makes it nowrap.  Is the solution here to force it to wrap, scroll, or...?

Maybe a more concise message with one of these (link and tooltip)

The definition of "standard" workflow in our case:

one workflow per repository (so no workflow name)
primary descriptor is /dockstore.cwl or /dockstore.wdl or /nextflow.conf

Maybe the other way around would sound less judgemental.
i.e. rather than standard vs non-standard
(nothing) vs custom
quick vs custom

* primary descriptor is /dockstore.cwl or /dockstore.wdl or /nextflow.conf

As Dockstore gains traction, presumably many and even most workflows will not have the dockstore.cwl/wdl pattern. If I were writing a real workflow, which I've never done :), I would name my primary descriptor after the functionality, e.g., /aligner.wdl, and not after a platform it would be registered on.
My judgemental comment was sort of in jest, but I do think what we're now calling non-standard may actually end up being the norm more often than not.
All that said, I'm not sure what to say.  I do like "Quick". Not sure about "custom".


Proposal: Remove the code related to the Operator enumeration

I recommend removing the Operator enumeration.
If arrow users build their own computing systems, they will generally not use the operator enumeration values defined by arrow, because there are often differences in the number of operators defined, or differences in classification, such as the lack of bitwise operators, and there may be more in the future for arithmetic operator.
Or lack some traits implementation, such as serde.
It is very boilerplate code to distribute various operations based on Operator. If it can be removed, the amount of arrow code can be greatly reduced.

I agree it's a good idea to not make them part of the core so downstream won't be forced to pull them in. But I think there is value in keeping the code and convert them into a feature or self-contained crate for the following two reasons:

To be feature parity with the cpp implementation
For use-case where downstream just want an out of the box simple compute module to get stuff done without having to write these boilerplate code

@houqp , note that the kernels themselves are kept. I think the proposal is:
use add_primitive(lhs, rhs) instead of arithmetics_primitive<T: NativeType>(lhs, Operator::Add, rhs).
The issue with arithmetics_primitive<T: NativeType>(lhs, Operator::Add, rhs) is that it requires T: Add + Sub + Mul + ..., which may not be fulfiled by all native types (e.g. months_days_ns is probably Add and Sub but not necessarily Div?).
An equivalent problem exists in comparison compare_primitive<T: NativeType>(lhs, Operator, rhs) requires T: PartialEq + PartialOrd but months_days_ns has a similar issue.

Yeah, I only took a quick scan on the CPP code and noticed they have these comparison operators defined. But on a second thought, I think doing something just because the CPP code is doing it is not a good technical argument.
Personally, I think writing add_primitive(lhs, rhs) is cleaner and more readable than arithmetics_primitive<T>(lhs, Operator::Add, rhs). Similarily, I would prefer compare_lt(a, b) over compare(a, b, Operator::Lt).
That said, the current operator related code does more than just operator based function dispatching. It also handles array type matching to provide high level APIs centered around Array trait object like other compute modules. The latter is the what I was suggesting us to keep to make the interface more consistent across compute modules and make the library a little bit easier for new users to adopt for less complicated applications.
In short, I am 100% on board with removing all the operators.


Multiple Speech-Type Generation broken?

How does this function work now?
The description text at the top also doesn´t make me smarter ^^

Hi @0dram , will need to assure the text input has a reference audio matched.
e.g.
if you input text as : "{happy} happy happy, {sad} sad sad"
you should have uploaded two reference audio and mark them as happy and sad

hey there thanks for the quick reply <3
It just doesn't work in Pinocchio interface. I tried it with the browser and it worked just fine. I'm sorry.
Thanks again

If work is great~
Will close this issue, feel free to open if further questions


Update default out folder

This should be checked/generated automatically.

No this is not right
https://github.com/foundry-rs/foundry/blob/25598999a2b33ac6ccfa35c347f3c98aba8e0061/crates/config/src/lib.rs#L2155


Something wrent wrong

Microsoft PowerToys version
<IP_ADDRESS>
Installation method
Microsoft Store
Running as admin
Yes
Area(s) with issue?
System tray interaction
Steps to reproduce
Unplugged Xbox Elite Series 2 Controller
2024-03-03.txt
✔ Expected Behavior
I was expecting nothing to happen since I was just unplugging my Xbox Elite Series 2 controller
❌ Actual Behavior
No response
Other Software
No response

This looks like a crash within PowerToys Run. Can you provide a full /bugreport?


Regression: Tooltip contents not visible in Dark theme (V2.1.1)

In the dark theme tooltip contents are not visible as both background and text color is white.
Regression:
worked in v1.x
How to reproduce
Please check stackblitz example below.  Tooltip contents are not visible in div tooltip or angular component.
https://stackblitz.com/edit/clarity-angular8-dark-theme-tooltip
Steps to reproduce the behavior:
check stackblitz example above.
Expected behavior
Tooltip content should be visible in dark theme.
Versions
App

Angular: [e.g. 8]
Node: [e.g. 10.x]
Clarity: [e.g. 2.1.1]

Device:

Type: [e.g. MacBook]
OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Additional notes

I investigated this issue and I found a fix for it.
Can I start working on it?
If so, can you assign the issue to me?
Thanks!

Sure! Thanks, @florin-borceanu


Invalid savedPosition

Reproduction
https://codesandbox.io/s/scrollbehavior-doesnt-save-scroll-position-xvg6x2?file=/src/router.js
Steps to reproduce the bug

Scroll down Home page
Go to About page
Tap back button on codesandbox browser
In the console you can see that the savedPosition from vueRouter is zero and the page scrolls to the top

Expected behavior
The Home page opens with the position correctly saved
Actual behavior
The Home page opens with the position incorrectly saved
Additional information
Workaround
https://codesandbox.io/s/scrollbehavior-doesnt-save-scroll-position-workaround-9t77rl?file=/src/router.js
Proposal
Allow user to provide an options to vueRouter:
type AdditionalOptions = {
  // invoking in 2 cases:
  // 1. to save position (beforeEach)
  // 2. to scroll page instead of window.scrollTo (scrollContainer.scrollTo)
  getScrollContainer?: (currentRoute: RouteLocationNormalized) => HTMLElement
}

If not defined, the current behaviour is returned to
I've read https://github.com/vuejs/router/blob/a1611b6099403cfe9539ee8d4e9308b3a6a0175c/packages/router/src/scrollBehavior.ts#L176-L191
P.s
I hate the window.scrollTo, window.scrollIntoView methods with behavior: 'smooth', it would be great if we could make smoother behaviour with custom smoothScroll function.
Suggestion:
type AdditionalOptions = {
  // scrollContainer from the previous function getScrollContainer or document.scrollingElement
  scroll(scrollContainer: HTMLElement, position: ScrollPosition): void
}

This is a limitation (as you noticed) due to the fixed position. There are plans to improve but we will go through an RFC like mentioned in the comments. Right now you can either use https://github.com/antfu/vue-router-better-scroller or implement a custom solution that runs with router.afterEach()


feat(api): Add Routes + handlers

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 154 (0.0%)  changed or added relevant lines in 6 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-22.8%) to 50.101%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

internal/middlewares/valid_chat.go
0
12
0.0%

internal/middlewares/valid_feed.go
0
12
0.0%

internal/middlewares/valid_article.go
0
14
0.0%

internal/handlers/articles.go
0
22
0.0%

internal/handlers/feeds.go
0
27
0.0%

internal/handlers/chats.go
0
67
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
-22.8%

Covered Lines:
247

Relevant Lines:
493

💛  - Coveralls


Dao hf release

This implements the DAO hf as it was committed onto the state_revamp branch. This branches out from the 1.4.0 release and will revert the changes from the pulled 1.5.0 release.

Looks, good tests pass. Could not find the fixture hash as a commit in ethereum/tests though.

Could not find the fixture hash as a commit in ethereum/tests though.

It is on a branch currently -- it hopefully gets merged into develop there soon.


[bug]: Killed while loading 1.5

Is there an existing issue for this?

[X] I have searched the existing issues

OS
Linux
GPU
cpu
VRAM
No response
What happened?
It says 'Killed' when I try to run invoke.py --web as seen below
(invokeai) lunkwill@Will-of-Lunk:~/Programs/stable-invoke/invokeAI$ python scripts/invoke.py --web

Initializing, be patient...

Initialization file /home/lunkwill/.invokeai found. Loading...
InvokeAI runtime directory is "/home/lunkwill/invokeai"
Patchmatch initialized
GFPGAN Initialized
CodeFormer Initialized
ESRGAN Initialized
Using device_type cuda
Current VRAM usage:  0.00G
Scanning Model: stable-diffusion-1.5
Model Scanned. OK!!
Loading stable-diffusion-1.5 from /home/lunkwill/invokeai/models/ldm/stable-diffusion-v1/v1-5-pruned-emaonly.ckpt
| LatentDiffusion: Running in eps-prediction mode
| DiffusionWrapper has 859.52 M params.
| Making attention of type 'vanilla' with 512 in_channels
| Working with z of shape (1, 4, 32, 32) = 4096 dimensions.
| Making attention of type 'vanilla' with 512 in_channels
Killed

Screenshots
No response
Additional context
I have 16g normal RAM
and this is my GPU: Intel Corporation CometLake-U GT2
the laptop in an ASUS ZenBook running Ubuntu 22.04
Contact Details
No response

I now have the same issue on Ubuntu 22.04, with an rtx 3060.

Using device_type cuda
Current VRAM usage:  0.00G
Scanning Model: stable-diffusion-1.5
Model Scanned. OK!!
Loading stable-diffusion-1.5 from /media/iwoolf/BigDrive/Stable-diffusion/models/ldm/stable-diffusion-v1/v1-5-pruned-emaonly.ckpt
Terminated

I'm also getting this error while loading either 1.4 or 1.5.  I haven't yet tried any other models.  Same console output as OP.
I am running on Ubuntu 20.04 on WSL, 16GB memory.  Nvidia-smi correctly shows my rtx 3070.


Matcher Chaining

With matcher chaining, one can use JSONPath to get a JSON node, and use other matcher to compare its value. For example:
{
  body: [
    {
      matcher: "jsonpath"
      value: “$.user.id"
      doMatch: {
        matcher: “exact”,
        value: “1"
    }
  ]
}

This removes the stress of composing and testing complex  jsonpath/xpath expressions, which may not be supported by the current jsonpath/xpath library hoverfly is using. The matcher will be more readable too.

@tommysitu can I take this up?

@tommysitu  I am currently working on this request.

Some work has been done here to allow one level of nesting for the form matcher: https://github.com/SpectoLabs/hoverfly/pull/1025 you might find it useful @kapishmalik

@tommysitu I was thinking to change return type of all matchers from bool to string, bool...i.e. matchedvalue, ismatched or not so that I keep on iterating till doMatch is null. Whenever the value of matcher returns false, I should return false otherwise true. Hope it makes some sense.


Item is removed from shopping cart once purchased

As a user
I need to have the items I have purchased deleted from the shopping cart
So that I don't duplicate my purchase in the future
Details and Assumptions

Once a user purchases a product, we assume that if they would like for it to be deleted from their shopping cart
Information needs to flow from the order management system so shopping cart logic can make the deletions requested

Acceptance Criteria
Given that a user purchases items in their shopping cart
When a transaction is confirmed
Then all items purchased will be automatically deleted from the shopping cart

brainstorm more about this one (flow-wise)

closing this issue because it is a duplicate of the DELETE item issue, which is already in the sprint 1 backlog


Code Base:  Making Color Coding More Generic / Reusable

The classifier.js file is nice, but I was wondering if you could refactor it so that there is one function that executes something like $scope.{metric name}Style.colorClass = {color};?  That way, the specific functions only have to make a call to that one function instead of writing that line every time.  For example, commitsGreen would now be something like return setColorClass("commits", "green");
This could make adding new metrics to the page slightly less painful, and I'm sure there is an even better way to make this code more scalable, but this was just something I noticed.

That is a great recommendation! I will definitely have to look into that more. I was just not incredibly familiar with ajax when I first made the file, so I had to do it the inefficient way.

We finally figure it out and were able to get our functions down to two instead of fifteen. Thanks for the suggestion.