add OPEN_TILT to LidState for sunroof.

encountered a ValueError when sunroof was tilted up (vs retracted) while parked to provide some cooling. seems like an easy fix.
error:
Update for binary_sensor.bmw_x1_windows fails
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/dist-packages/homeassistant/helpers/entity.py", line 220, in async_update_ha_state
    await self.async_device_update()
  File "/usr/local/lib/python3.6/dist-packages/homeassistant/helpers/entity.py", line 377, in async_device_update
    await self.hass.async_add_executor_job(self.update)
  File "/usr/lib/python3.6/concurrent/futures/thread.py", line 56, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/local/lib/python3.6/dist-packages/homeassistant/components/bmw_connected_drive/binary_sensor.py", line 149, in update
    self._state = not vehicle_state.all_windows_closed
  File "/home/hass/.homeassistant/deps/lib/python3.6/site-packages/bimmer_connected/state.py", line 208, in all_windows_closed
    return len(list(self.open_windows)) == 0
  File "/home/hass/.homeassistant/deps/lib/python3.6/site-packages/bimmer_connected/state.py", line 203, in open_windows
    return [lid for lid in self.windows if not lid.is_closed]
  File "/home/hass/.homeassistant/deps/lib/python3.6/site-packages/bimmer_connected/state.py", line 203, in <listcomp>
    return [lid for lid in self.windows if not lid.is_closed]
  File "/home/hass/.homeassistant/deps/lib/python3.6/site-packages/bimmer_connected/state.py", line 348, in is_closed
    return self.state == LidState.CLOSED
  File "/home/hass/.homeassistant/deps/lib/python3.6/site-packages/bimmer_connected/state.py", line 343, in state
    return LidState(getattr(self._vehicle_state, self.name))
  File "/usr/lib/python3.6/enum.py", line 293, in __call__
    return cls.__new__(cls, value)
  File "/usr/lib/python3.6/enum.py", line 535, in __new__
    return cls._missing_(value)
  File "/usr/lib/python3.6/enum.py", line 548, in _missing_
    raise ValueError("%r is not a valid %s" % (value, cls.__name__))
ValueError: 'OPEN_TILT' is not a valid LidState

This addresses issue #101 also addressed by pull request #105.

Is merged via PR #105.


Add ringingliberty.com

Evidence: https://www.ringingliberty.com/2015/12/16/how-can-i-check-if-remote_addr-ip-is-not-in-cidr-range-in-nginx/
Original: https://serverfault.com/questions/743414/how-can-i-check-if-remote-addr-ip-is-not-in-cidr-range-in-nginx
Original is serverfault.com, not stackoverflow.com, hope that's still okay

Thanks! No problem, this filter supports all sites of the Stack Exchange network.


Add Label dialog should pe pre populated with already created label with multiple selection

So now if I want to apply 4 label on a script i need to do 8 actions (4 for typing script and 4 due to page reload and enabling the script by clicking holding to enable labeling) If we have a multi choice dialog with pre populated label which had already created along with add label field this can be done in a single step.
This is also a major issue and can ease every bodys life if fixed

Hi Pawan, yes not just this but you will find couple of other user experience issues. I created it for my personal use so I just took the easiest way out. Moreover after using it for 1 year I know that adding of tags in holdings area happens way too rarely. Only during initial setup times. For me buying and selling is not to often.
Most of the features I am adding is in 'positions' section for F&O


Update extensions.json

Removed the two extension suggestions in extension.json file as we are moving away from mermaid.

I took the liberty to rename the PR so I could remove a duplicate item in the list (plantuml) and add code spell checker 😄

We aren't fully moving away from mermaid, but you're indirectly right that we don't actually need these extensions since Quarto provides mermaid preview.
Changes to config happen over at the team repo, but I'll update it over there. Thanks for this!


ICMPv4 and ICMPv6

Any chance that this gets merged? Just wondering.

It's on my ToDo list...

It will be replaced by a newer version


Bugfix/weekpicker

Fixing several bugs in the weekpicker

If I pick week "2015-51" and then pick week 53 via January 1st I get this:


Mother Cell

Its like Mother Cell dose not spawn mass on outer layer of the cell but inside

And when i eat mother cell its crashes

Cant able to see the Crash Report Click Here

Food spawning issue was fixed, however I cannot reproduce the error. Try seeing if it still occurs on the latest version.

Dude it is latest version 1.6.0!

@Gigabyte918 I'm saying the LATEST latest version. As in the most recent commits. I can tell you are using an outdated version because the checkV function has been removed and replaced with intersects. I could not reproduce this bug on the latest commits, have you edited anything regarding experimental mode?

i dident edit any thing instead of gameserver.ini

@Gigabyte918 Please try the latest version, I can guarantee you will not get that error


Make file unable to compile

Hello,
We tried to run the tests and we got the following error
======================================================================================================= ERRORS ======================================================================================================== ____________________________________________________________________________________________ ERROR collecting test_all.py _____________________________________________________________________________________________ /usr/lib/python2.7/dist-packages/_pytest/python.py:507: in _importtestmodule     mod = self.fspath.pyimport(ensuresyspath=importmode) /usr/lib/python2.7/dist-packages/py/_path/local.py:701: in pyimport     __import__(modname) E     File "/media/Bacteria/readitandkeep/read-it-and-keep-0.3.0/tests/test_all.py", line 59 E       reads = " ".join([f"--reads{i+1} " + f for i, f in enumerate(reads_files)]) E                                        ^ E   SyntaxError: invalid syntax !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Interrupted: 1 errors during collection !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! =============================================================================================== 1 error in 0.07 seconds =============================================================================================== make: *** [Makefile:23: test] Error 2
We've got all the proper dependences installed so that shouldn't be an issue so was curious if anyone else has encountered this issue.
Thanks

The tests need Python 3 to run. That error is from Python 2.


no rounded_graph.pb and label.txt

no pb and label file.

All model already uploaded to Camera-Classifiers/app/src/main/res/raw/
Why you need pd and label ?

the gradle file need two files, as followiing:
// Top-level build file where you can add configuration options common to all sub-projects/modules.
project.ext.ASSET_DIR = projectDir.toString() + '/assets'
assert file(project.ext.ASSET_DIR + "/rounded_graph.pb").exists()
assert file(project.ext.ASSET_DIR + "/retrained_labels.txt").exists()

When it work, there is a error in read label file too. I look at the source code and find them , as following:
public TensorFlowImageClassifier(AssetManager assetManager, String modelFilename, String labelFilename, int inputSize, int imageMean, float imageStd, String inputName, String outputName) {
    this.inputName = inputName;
    this.outputName = outputName;

    // Read the label names into memory.
    // TODO(andrewharp): make this handle non-assets.

    BufferedReader br = null;
    try {
        br = new BufferedReader(new InputStreamReader(assetManager.open(labelFilename)));
        String line;
        while ((line = br.readLine()) != null) {
            this.labels.add(line);
        }
        br.close();
    } catch (IOException e) {
        throw new RuntimeException("Problem reading label file!", e);
    }

Do this error not happened in your testing?


update the animated icon slider scenario to use a more appropriate AnimatedVisual

No code changes, just makes the slider example look a little nicer.

/azp run


bundle.yaml: Bump Prometheus Operator memory request and limit

When handling big Kubernetes objects, marshalling objects is memory
intense. This can be reproduced with the end-to-end test
TestPrometheusRulesExceedingConfigMapLimit. This patch doubles the
memory request and limit of the Prometheus Operator deployment to 100mb
and 200mb.

Memory profile of Prometheus Operator running TestPrometheusRulesExceedingConfigMapLimit: file.pdf

Thanks for the review @squat, would you mind taking another look?

Thanks for the help. Changed to %d, anything else missing?

I think something went wrong with rebasing here, the commit message doesn't seem to be in line with the changes.

lgtm once rebase is fixed :+1:

Thanks @brancz @squat for the feedback.


Avoid steering cluster-monitoring-operator onto infra nodes

Steering the cluster-monitoring-operator needs overriding CVO which
leads to upgrade failures, so we just steer the monitoring components
including prometheus, alertmanager, grafana and kube-state metrics by
modifying the cluster-monitoring-config ConfigMap.

@jtaleric we might not have a need to move the cluster-monitoring-operator to infra nodes as it's not heavy and we are moving all the heavy components including prometheus onto the infra nodes. Just commented out the stuff to indicate that this is the procedure in case we want to steer it. Having an extra var for it would be additional maintenance.

@jtaleric we might not have a need to move the cluster-monitoring-operator to infra nodes as it's not heavy and we are moving all the heavy components including prometheus onto the infra nodes. Just commented out the stuff to indicate that this is the procedure in case we want to steer it. Having an extra var for it would be additional maintenance.

ack

Thanks for the review @jtaleric @mohit-sheth.


SimpleITK error when running the nnUNet extension inference

Hi,
I'm running the nnUNet extension with a locally trained model.
My Slicer version is Slicer 5.7.0-2024-06-04
The installed nnUNet version is 2.4.2
nnUNet Run Settings are shown here

The nnUNet module starts running, but stops after the preprocessing step as shown below:

nnUNet preprocessing...
Traceback (most recent call last):
  File "C:\Users\msoufi\AppData\Local\slicer.org\Slicer 5.7.0-2024-06-04\lib\Python\Lib\runpy.py", line 197, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "C:\Users\msoufi\AppData\Local\slicer.org\Slicer 5.7.0-2024-06-04\lib\Python\Lib\runpy.py", line 87, in _run_code
exec(code, run_globals)
  File "C:\Users\msoufi\AppData\Local\slicer.org\Slicer 5.7.0-2024-06-04\lib\Python\Scripts\nnUNetv2_predict.exe\__main__.py", line 4, in <module>
  File "C:\Users\msoufi\AppData\Local\slicer.org\Slicer 5.7.0-2024-06-04\lib\Python\Lib\site-packages\nnunetv2\inference\predict_from_raw_data.py", line 22, in <module>
    from nnunetv2.inference.data_iterators import PreprocessAdapterFromNpy, preprocessing_iterator_fromfiles, \
  File "C:\Users\msoufi\AppData\Local\slicer.org\Slicer 5.7.0-2024-06-04\lib\Python\Lib\site-packages\nnunetv2\inference\data_iterators.py", line 12, in <module>
    from nnunetv2.preprocessing.preprocessors.default_preprocessor import DefaultPreprocessor
  File "C:\Users\msoufi\AppData\Local\slicer.org\Slicer 5.7.0-2024-06-04\lib\Python\Lib\site-packages\nnunetv2\preprocessing\preprocessors\default_preprocessor.py", line 29, in <module>
    from nnunetv2.utilities.plans_handling.plans_handler import PlansManager, ConfigurationManager
  File "C:\Users\msoufi\AppData\Local\slicer.org\Slicer 5.7.0-2024-06-04\lib\Python\Lib\site-packages\nnunetv2\utilities\plans_handling\plans_handler.py", line 16, in <module>
    from nnunetv2.imageio.reader_writer_registry import recursive_find_reader_writer_by_name
  File "C:\Users\msoufi\AppData\Local\slicer.org\Slicer 5.7.0-2024-06-04\lib\Python\Lib\site-packages\nnunetv2\imageio\reader_writer_registry.py", line 9, in <module>
    from nnunetv2.imageio.simpleitk_reader_writer import SimpleITKIO
  File "C:\Users\msoufi\AppData\Local\slicer.org\Slicer 5.7.0-2024-06-04\lib\Python\Lib\site-packages\nnunetv2\imageio\simpleitk_reader_writer.py", line 19, in <module>
    import SimpleITK as sitk
  File "C:\Users\msoufi\AppData\Local\slicer.org\Slicer 5.7.0-2024-06-04\lib\Python\Lib\site-packages\SimpleITK\__init__.py", line 18, in <module>
    from SimpleITK.SimpleITK import *
  File "C:\Users\msoufi\AppData\Local\slicer.org\Slicer 5.7.0-2024-06-04\lib\Python\Lib\site-packages\SimpleITK\SimpleITK.py", line 16, in <module>
    from . import _SimpleITK
ImportError: DLL load failed while importing _SimpleITK: The specified module could not be found.
Loading inference results...
Inference ended in error:
Failed to load the segmentation.

Tried to check similar issues, but all are reporting SimpleITK building solutions.
Any solution for this?
Thanks for your help in advance,,

My current workaround is to use a previous version of 5.7.0. The build from 2024-06-08 seems to have a bug with its SimpleITK install, the 2024-05-31 build works. Though, I have not tested any of the builds in between, so one of those might still work, too
https://download.slicer.org/?closest-revision=32881

@MathijsdeBoer Thanks a lot for your reply.
I reinstalled the previous version, and the SimpleITK issue was solved!
However, the inference could not proceed with the following error issued after starting the preprocessing,
nnUNet preprocessing...
C:\Users\msoufi\AppData\Local\slicer.org\Slicer 5.7.0-2024-05-30\lib\Python\Lib\site-packages\nnunetv2\utilities\plans_handling\plans_handler.py:37: UserWarning: Detected old nnU-Net plans format. Attempting to reconstruct network architecture parameters. If this fails, rerun nnUNetv2_plan_experiment for your dataset. If you use a custom architecture, please downgrade nnU-Net to the version you implemented this or update your implementation + plans.
  warnings.warn("Detected old nnU-Net plans format. Attempting to reconstruct network architecture "
Traceback (most recent call last):
  File "C:\Users\msoufi\AppData\Local\slicer.org\Slicer 5.7.0-2024-05-30\lib\Python\Lib\runpy.py", line 197, in _run_module_as_main
return _run_code(code, main_globals, None,
  File "C:\Users\msoufi\AppData\Local\slicer.org\Slicer 5.7.0-2024-05-30\lib\Python\Lib\runpy.py", line 87, in _run_code
    exec(code, run_globals)
  File "C:\Users\msoufi\AppData\Local\slicer.org\Slicer 5.7.0-2024-05-30\lib\Python\Scripts\nnUNetv2_predict.exe\__main__.py", line 7, in <module>
  File "C:\Users\msoufi\AppData\Local\slicer.org\Slicer 5.7.0-2024-05-30\lib\Python\Lib\site-packages\nnunetv2\inference\predict_from_raw_data.py", line 859, in predict_entry_point
    predictor.initialize_from_trained_model_folder(
  File "C:\Users\msoufi\AppData\Local\slicer.org\Slicer 5.7.0-2024-05-30\lib\Python\Lib\site-packages\nnunetv2\inference\predict_from_raw_data.py", line 100, in initialize_from_trained_model_folder
    network = trainer_class.build_network_architecture(
AttributeError: 'NoneType' object has no attribute 'build_network_architecture'

#######################################################################
Please cite the following paper when using nnU-Net:
Isensee, F., Jaeger, P. F., Kohl, S. A., Petersen, J., & Maier-Hein, K. H. (2021). nnU-Net: a self-configuring method for deep learning-based biomedical image segmentation. Nature methods, 18(2), 203-211.
#######################################################################
Loading inference results...
Inference ended in error:
Failed to load the segmentation.
Check the inference folder content C:\Users\msoufi\AppData\Local\Temp\Slicer-uXpiFb\output

Could you provide the required nnUNet release for training the custom models?
Thanks again for your help,,

I'm just using the latest nnUNet version, 2.4.0.

@MathijsdeBoer
Thanks a lot. I found the issue. The trainer name is used in the inference pipeline to set the inference model path.
Since I'm using a custom trainer (variant epochs), I had to add its class to the file below in order to be recognized.
Slicer 5.7.0-2024-05-30\lib\Python\Lib\site-packages\nnunetv2\training\nnUNetTrainer\variants\training_length\nnUNetTrainer_Xepochs.py
and now it works well.
Thanks again!

@mazensoufi  and @MathijsdeBoer  thank you for opening / following up on this issue.
Regarding the original SimpleITK problem, this is a problem related to Slicer directly on Windows system.
See the opened issue here : https://github.com/Slicer/Slicer/issues/7799
This should be solved in coming 3D Slicer versions.


"No frames received" for RGB Module

librealsense
2.38.1 RELEASE

OS
Windows

Name
Intel RealSense D435

Serial Number
920312070806

Firmware Version
<IP_ADDRESS>

Advanced Mode
YES

Camera Locked
YES

Usb Type Descriptor
3.2

Product Line
D400

Asic Serial Number
925623027108

Firmware Update Id
925623027108

Please provide a description of the problem

Hi @asb2111991  Are you using the RealSense Viewer program, please?  And if you are using the Viewer, are you enabling the RGB stream on its own, or do you have Depth, RGB and Motion Motion all enabled at the same time?

Hi @MartyG-RealSense, Thank you for responding. Yes, I am using the Viewer. I have enabled Depth and the RGB, and also tried to enable RGB without enabling the Depth. In both cases, 'No frames received".
I have tested on a different computer, same result. I have tried installing the 'Recommended Firmware', nothing seems to work
Need help badly

Thank you for the information.  Next, could you confirm please that access to the camera is set to On in the Windows privacy settings for both camera hardware and camera applications.  This can be done with instructions at https://github.com/IntelRealSense/librealsense/issues/3381#issuecomment-503424789

Yes, that was one of the very first things that I checked and it was already enabled.

Just installed the latest SDK and 'Recommended Firmware', it doesn't help. If it wasn't clear from earlier correspondence, the Stereo Module works fine and give me the depth map

Please use the instructions in the link below to check if RGB video can be displayed in the Windows Camera app.
https://github.com/IntelRealSense/librealsense/issues/8711#issuecomment-811945394
If you are using a laptop that has a built-in webcam, you could also try temporarily disabling the webcam in the Windows Device Manager to eliminate the possibility that there is a conflict between that built-in camera and the RealSense camera.
If you are using a laptop with such a webcam, you can go to the Cameras section of the Device Manager , right-click on the entry representing the webcam and select the menu option Disable device.
If disabling it does not make a difference then you can re-enable it by right-clicking on the webcam again and selecting Enable device.

Disabling my webcam did not make a difference and when I opened the camera app to see if that works with realsense, it throws an error saying 'Device could not be started'.

Has the RGB stream ever worked since you purchased the camera, or was it working correctly up until now and then suddenly stopped working?

It has worked perfectly for months. I have developed an object detection solution using that in Python. It has not been connected to the computer in the past three months, during when it has been sitting in the warehouse.

There have been a couple of cases this year where this problem has occurred with No Frames Received the first time that the camera is used after a period of inactive storage in a cool dry location for weeks / months, and worked correctly before storage.  I will seek advice from Intel about your particular case.  I recommend putting the camera aside for now in the meantime.  Thanks very much for your patience.

I have received a response from Intel.  Could you send me an email please so that I can pass your email address to Intel with your permission.  They can then follow up with you about your camera problem.  You can contact me at:
<EMAIL_ADDRESS>

I have sent the email, please confirm here or by responding via email. Thank you again for your help.

Thanks very much, I can confirm that I have received your email and will forward it to the appropriate Intel RealSense team member.

Just as proof

Yes just tested now (disabled by camera) and same issue as before argh!

In my case, it was due to humidity. The stock Realsense cameras are tested only up to 35 Celcius. If the ambient temperatures go beyond and the powered-off camera is left in such an environment for too long, this can happen.
Again, this was the cause for MY camera. Keep in indoors in a dark moisture-free place for 4 or 5 hours and if your situation is similar to mine, it should go away.


Make badge preview fixes

Describe the feature you'd like
make badge preview fixed and other items scroll-able only when the screen is in portrait mode.
Additional context
It will allow user to see the preview all the time.
Would you like to work on the issue?
YES

Hey, can you explain me what the issue is about?

Currently when the screen is vertical the badge preview screen also gets scrolled when we scroll for options and all so I think making it fixed for portrait mode would be a good idea.

@yatri1609 oh ok. It is fixed in the latest PR by yash


Multiple containers with same VIRTUAL_HOST without load balancing

Hi,
I want to know if there is a way to run a new container with a VIRTUAL_HOST already used by another container without load balancing.
I want to keep the older config until the old container isn't stopped.
I want be able to do this in order to have a migration of containers testing the new container before switch the nginx proxy. Now I have the load balancing when I start the new container.

It sounds like you might want to test the container separately before starting it up with the VIRTUAL_HOST environment variable. In general I think the right way to do this is to use health checks and only have the health check return 200 after the app has been tested, but that's only available in Nginx Plus, not the Open Source version of Nginx.

These discussions about being able to alter the labels on a running container seem relevant:

https://github.com/docker/docker/issues/15496
https://github.com/docker/docker/pull/15078

They don't help you right now though.


Link license to the Readme

Issue Link :link:
The link to the license is missing at the end of the readme.
Implementation Details :construction:
Alamofire was applied in the same format.

Thank you for watching PR :)


spec: type alias identity unclear

In the "Type Alias" proposal by Russ Cox & Robert Griesemer it is specified that:

After such a declaration, T1 and T2 are identical types.

Given the above, I think that this should be made more obvious within the spec in either the Type Identity section or the Type Declarations, "Alias declarations" sub-section.

@gbbr Can you be a bit more precise about what you are looking for? The Alias declaration sub-section seems pretty clear; there's even an example that emphasizes (with a comment) that the alias and the literal type on the right of the alias declaration are identical.

You are right, sorry about that. Not sure how I've managed to miss that comment.

@gbbr No worries! Thanks for closing the issue.


annotate: Introduce requirements.

Quick and dirty draft.
Being discussed in https://github.com/iterative/studio/issues/4118

Codecov Report

Merging #225 (00402c9) into main (24e4996) will decrease coverage by 0.07%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #225      +/-   ##
==========================================
- Coverage   83.76%   83.69%   -0.08%
==========================================
  Files          16       16
  Lines        1540     1533       -7
==========================================
- Hits         1290     1283       -7
  Misses        250      250

Impacted Files
Coverage Δ

gto/api.py
80.00% <ø> (ø)

gto/cli.py
69.42% <ø> (-0.11%)
:arrow_down:

gto/config.py
95.83% <100.00%> (+0.08%)
:arrow_up:

gto/index.py
91.25% <100.00%> (+0.13%)
:arrow_up:

gto/ext.py
71.05% <0.00%> (-0.75%)
:arrow_down:

gto/versions.py
86.66% <0.00%> (-0.64%)
:arrow_down:

gto/ui.py
83.01% <0.00%> (-0.62%)
:arrow_down:

gto/base.py
87.50% <0.00%> (-0.50%)
:arrow_down:

... and 1 more

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


fix(editor): misaligned command prefixes

#6630
#6629
#6628  👈
main

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

Join @DonIsaac and the rest of your teammates on  Graphite


[MySql Provider Question] 2.1.0-preview1 Upgrade 'GeneratedTime.CreatedTimestamp' could not be mapped

I am working on the Pomelo MySql provider update to 2.1.0-preview1:

Branch is here
PR is https://github.com/PomeloFoundation/Pomelo.EntityFrameworkCore.MySql/pull/510

Presently everything is failing with this error and I can't figure out what is missing.  Could you point me in the right direction @ajcvickers @smitpatel
[xUnit.net 00:00:03.3297454]       System.InvalidOperationException : The property 'GeneratedTime.CreatedTimestamp' could not be mapped, because it is of type 'DateTime' which is not a supported primitive type or a valid entity type. Either explicitly map this property, or ignore it using the '[NotMapped]' attribute or by using 'EntityTypeBuilder.Ignore' in 'OnModelCreating'.
[xUnit.net 00:00:03.3298187]       Stack Trace:
[xUnit.net 00:00:03.3298596]            at Microsoft.EntityFrameworkCore.Metadata.Conventions.Internal.PropertyMappingValidationConvention.Apply(InternalModelBuilder modelBuilder)
[xUnit.net 00:00:03.3298985]            at Microsoft.EntityFrameworkCore.Metadata.Conventions.Internal.ConventionDispatcher.ImmediateConventionScope.OnModelBuilt(InternalModelBuilder modelBuilder)
[xUnit.net 00:00:03.3299433]            at Microsoft.EntityFrameworkCore.Infrastructure.ModelSource.CreateModel(DbContext context, IConventionSetBuilder conventionSetBuilder, IModelValidator validator)
[xUnit.net 00:00:03.3299740]            at System.Collections.Concurrent.ConcurrentDictionary`2.GetOrAdd(TKey key, Func`2 valueFactory)
[xUnit.net 00:00:03.3299972]            at Microsoft.EntityFrameworkCore.Internal.DbContextServices.CreateModel()
[xUnit.net 00:00:03.3300151]            at Microsoft.EntityFrameworkCore.Internal.DbContextServices.get_Model()
[xUnit.net 00:00:03.3300331]            at lambda_method(Closure , ServiceProviderEngineScope )
[xUnit.net 00:00:03.3300568]            at Microsoft.Extensions.DependencyInjection.ServiceProviderServiceExtensions.GetRequiredService(IServiceProvider provider, Type serviceType)
[xUnit.net 00:00:03.3300821]            at Microsoft.Extensions.DependencyInjection.ServiceProviderServiceExtensions.GetRequiredService[T](IServiceProvider provider)
[xUnit.net 00:00:03.3301011]            at Microsoft.EntityFrameworkCore.DbContext.get_DbContextDependencies()
[xUnit.net 00:00:03.3301269]            at Microsoft.EntityFrameworkCore.DbContext.get_InternalServiceProvider()
[xUnit.net 00:00:03.3301454]            at Microsoft.EntityFrameworkCore.DbContext.get_DbContextDependencies()
[xUnit.net 00:00:03.3301660]            at Microsoft.EntityFrameworkCore.DbContext.EntryWithoutDetectChanges[TEntity](TEntity entity)
[xUnit.net 00:00:03.3301856]            at Microsoft.EntityFrameworkCore.DbContext.SetEntityState[TEntity](TEntity entity, EntityState entityState)
[xUnit.net 00:00:03.3302140]         /home/caleb/Projects/caleb/Pomelo.EntityFrameworkCore.Mysql/test/EFCore.MySql.FunctionalTests/Tests/Models/ExpressionTest.cs(32,0): at EFCore.MySql.FunctionalTests.Tests.Models.ExpressionTest..ctor()

@caleblloyd That exception means that the the type mapper (ITypeMappingSource in 2.1) is not returning a mapping for DateTime. ITypeMappingSource calls into your implementation of IRelationalTypeMapper if you haven't implemented the new service shapes directly.

We're still using IRelationalTypeMapper
The CLR Type Mapping for DateTime is here:
https://github.com/caleblloyd/Pomelo.EntityFrameworkCore.MySql/blob/f_2.1.0-preview/src/EFCore.MySql/Storage/Internal/MySqlTypeMapper.cs#L147
This method hasn't changed from 2.0.1 to 2.1.0-preview1
Anything else that could cause it?

@caleblloyd I would suggest debugging to see why the type mapper is not returning a mapping on this code path.


Cleanup rule printing

Refactor printing code to use Format features, making it more robust and easier to change.
Rebased on top of https://github.com/realworldocaml/mdx/pull/162

Rebased on master and ready for reviews.

It's a good idea to simplify that part of the code -- I just don't understand why the patch adding the section is part of the changesets. I guess this is fixing a different issue?

I feel that we could do with direct tests of the ocaml-mdx rule command (i.e. generated rules which are not  for propping up other tests). This would be enabled by #178.

I agree testing that way is not great. We still benefit from generating test rules but we need an other way to test every features of ocaml-mdx rule.


Problem Authenticating with Smartthings

Hi, similarly to issue listed as closed here: https://github.com/nfarina/homebridge/issues/17#issuecomment-168808027
The difference with the above issue is the underscores are in place in the app_id / access_token lines.
I'd appreciate any help here, no search online has found any other solution to try (I'm quite new to this!).
Using Raspbian on pi 2.
I have all set up and looks fine until the following:
Starting HomeBridge server...
Loading 1 platforms...
[SmartThings] Initializing SmartThings platform...
[SmartThings] Fetching SmartThings devices...
[SmartThings] There was a problem authenticating with SmartThings.
The app-id and token are correct.
Here is my config.json:
{
"bridge": {
"name": "Homebridge",
"username": "CC:22:3D:E3:CE:30",
"port": 51826,
"pin": "031-45-154"
},
"description": "JSON API",
"platforms": [{
        "platform": "SmartThings",
        "name": "SmartThings",
        "app_id": "xxxxxxx",
        "access_token": "xxxxxxx"
}]

}
Many thanks!
T

Did you have this issue when RPi reboot? I also had this issue but only at boot. It starts fine when I run it manually after RPi finishes booting.

Hi, yes the problem still happens after reboot- I tried reinstalling from scratch after reboot as well, no joy - same problem persists...
Sent from my iPhone

On 5 Jan 2016, at 23:13, Lam Nguyen<EMAIL_ADDRESS>wrote:
Did you have this issue when RPi reboot? I also had this issue but only at boot. It starts fine when I run it manually after RPi finishes booting.
—
Reply to this email directly or view it on GitHub.

I'm interested in the fix as well, but did you try to install this? homebridge-legacy-plugins
sudo npm install -g homebridge-legacy-plugins

Hi, yes I’ve installed this - as far as I can tell it installed ok.

On 6 Jan 2016, at 01:49, Lam Nguyen<EMAIL_ADDRESS>wrote:
I'm interested in the fix as well, but did you try to install this? homebridge-legacy-plugins
sudo npm install -g homebridge-legacy-plugins
—
Reply to this email directly or view it on GitHub https://github.com/nfarina/homebridge/issues/459#issuecomment-169192901.

Have you got 2 JSON APIs created in the SmartThings App?

I did have without realising but I have since deleted and still the same issue (prior to posting the issue)...
Sent from my iPhone

On 8 Jan 2016, at 10:40, mavis46<EMAIL_ADDRESS>wrote:
Have you got 2 JSON APIs created in the SmartThings App?
—
Reply to this email directly or view it on GitHub.

Having the same issues..it was working fine, but now, after a re-boot, I am getting this

@raspman If you manually start it after the machine finishes the boot, is there any error?

Well, if I delete the Smart app, re-provision it by updated the new information to place in json.config, I can it to work if I keep tinkering with it (by typing homebridge) and running it.  If I try to get it to run in the background or reboot the pi, it seems to go back to having an authentication error.  Yesterday I had it working awesome (simulating a power outage by reseting the pi) and it went right back up, including the hap showing up via the "Discovery" app I used to make sure it is running properly....

@raspman I think typing homebridge or start it in background manually (not automatically after boot) has the same effect and homebridge will run without error. But for me I only have issue when Pi reboots, if you can, try to hook up a monitor to the Pi and monitor when Pi reboots, see if any error comes up. For me I got this error https://github.com/nfarina/homebridge/issues/460 and it comes from homebridge. This is the reason why homebridge logs says authentication error

Interesting.  I have a headless set-up, so I'll wait a bit and see what happens.  Right now, I can't even get homebridge to run manually :)  I'm not sure if it has anything to do with Smartthings having some network issues right now our not..

Glad you're having a bit more success @raspman, I've still not got it to run once without the authentication error - have tried the above steps you mentioned (deleted smart app, re-installed it etc), rebooted the smart hub and pi, typed homebridge but same result - runs until auth :(

I can get it to run by typing homebridge, however, trying to run it again after reboot gives me an authentication error.  Also, I cannot figure out a way to run this in the background without keeping a terminal window open.  No idea what the problem is..

I think I might have figured out what the issue is on my end.  It seems, from trial and error, that homebridge loads without the authentication error as long as it is run via root (even on a reboot.)  Now, I just need to figure out how to get it to load via the root on boot up or a reboot...I can see there is an error message when I restart my pi saying "Failed to start.  See systemctl status homebridge.service"  I assume this is because I used a few methods to get it to auto load at boot up, but then deleted some files when it didn't work.

@raspman I know the wiki for run homebridge on startup has a new method (systemctl), but I don't think that's the issue (at least in my case). You're right that homebridge won't start if you run it from different account in RPi (happened to me before). Let me know if you can make it start on reboot

Now I have to figure out how to program it (properly) to do that :). I need guidance.......obviously the way I had it set up it wasn't booting from root.

Btw, I'm getting an error on boot about abosystemctl homebridge. I'm sure that has to do with me removing part of the script or something?

Sorry, typo. An error regarding systemctl homebridge.

It is still a couple of weeks out, but I am working on a refreshed and more complete smartthings plugin.

@pdlove thats great news, any chance it'll poll for updates from SmartThings, its pretty useless when Homebridge won't keep in sync with changes SmartThings has made to switches.

I have just done a clean install often having everything up and running (but a very messy install). I am now stuck with the authenticating message. I installed the latest version of node v5.4.1. Could this be the problem? And if so, how do I downgrade?

Has the authentication problem been solved?

My resolution is run via the sudo command.  However, I cannot program my Raspberry Pi to reload 'homebridge' via sudo on boot-up.

If I run homebridge just by typing the command 'homebridge' then I get the authenticating error. If I run 'sudo homebridge' then I get  an error saying config.json is not at /root/.homebridge/config.json.

Did you try moving config.json to /root/.homebridge/ ?

For me it's vice versa, I got auth error if i run sudo homebridge. and no error if on homebridge

Just tried and I get auth error with both root and normal user

I had to roll back my entire install from TimeMachine to January 7th. Updates in HomeBridge appear to have broken it (and other things)
Updating HomeBridge is something I avoid now, i've done it twice and its broken everything that was working perfectly - so if its working well for you, like mine is now and you don't need any new plugins or features I advise just leaving it and not updating until something stops working.

I have solved the auth error. Second time around I forgot to amend the SmartThings.js file for the UK - see below. Hence why it worked on my first install but didn't work on the second as I followed  a different set of instructions.
Now we need to make some changes to the smartthings.js file for the UK/EU servers:
cd /usr/local/lib/node_modules/homebridge-legacy-plugins/platforms
nano SmartThings.js
Find the following URL in the file:
https://graph.api.smartthings.com
and replace it with:
https://graph-eu01-euwest1.api.smartthings.com
In my version of the file, there was only one instance of this. Ctrl-O and Enter to save the file,

Hi, unfortunately I already had the UK server address amended & auth error still occurs - glad it works for you now tho!
Tim

On 23 Jan 2016, at 16:41, mavis46<EMAIL_ADDRESS>wrote:
I have solved the auth error. Second time around I forgot to amend the SmartThings.js file for the UK - see below. Hence why it worked on my first install but didn't work on the second as I followed a different set of instructions.
Now we need to make some changes to the smartthings.js file for the UK/EU servers:
cd /usr/local/lib/node_modules/homebridge-legacy-plugins/platforms
nano SmartThings.js
Find the following URL in the file:
https://graph.api.smartthings.com https://graph.api.smartthings.com/
and replace it with:
https://graph-eu01-euwest1.api.smartthings.com https://graph-eu01-euwest1.api.smartthings.com/
In my version of the file, there was only one instance of this. Ctrl-O and Enter to save the file,
—
Reply to this email directly or view it on GitHub https://github.com/nfarina/homebridge/issues/459#issuecomment-174198905.

Unfortunately, I cannot (again) get it to authenticate, even when using the sudo command.  I am not sure, again, if this has anything to do with the recent ST updates?  I had a few devices that I had to re-provision.  When I did so, I lost homebridge access and went to re-start it.  Once I did that, I could not get it to authenticate again (re-installed the Smartapp, etc..)


How to debug Identityserver4 source code

I want to debug Identityserver4 source code, so I can understand the underlying logic of the entire code, but I do not know how to do it. Does anyone know how to debug identityserver4 source code? Thank you
Please forgive me my English is not very good

@YINZHU2016 This isn't exactly an issue.
Identity Server 4 is open source, so you can look into the code any way you want. But to run it in debug mode, you can project-reference it by cloning a copy.

This seems to be a general question about IdentityServer - not a bug report or an issue.
Please use one of the our free or commercial support options
See here for more details.
Thanks!


feat: minor changes to support react navigation 6 for tab bar visibility option

As mentionned in #121, The tabBarVisible option is no longer present we need to check the existence and value of tabBarStyle.
Fix #121

thanks @bechir for submitting this pr


COMP: Set CMAKE VISIBILITY_PRESET to hidden

Suggested by Bradley Lowekamp (@blowekamp) at "WIP: Support adding Elastix component by CMake SimpleITK_USE_ELASTIX=ON" comment https://github.com/SimpleITK/SimpleITK/pull/1611#discussion_r848584729 referring to https://github.com/SimpleITK/SimpleITK/blob/2681d0689a5922a7f2d1b56b1c7b62361eed9d8d/SuperBuild/External_ITK.cmake#L81-L83
Discussed with Marius Staring (@mstaring) at superelastix.slack.com #elastix
Aims to avoid link warnings in SimpleITK (+ Elastix component), like

ld: warning: direct access in function '...' from file '....cxx.o)' to global weak symbol 'typeinfo for ...' from file '....cxx.o' means the weak symbol cannot be overridden at runtime. This was likely caused by different translation units being compiled with different visibility settings.

At at https://open.cdash.org/viewBuildError.php?type=1&buildid=7827932 ( Azure Pipelines 2-macOS)

I would recommend the following logic elastix:
https://github.com/SimpleITK/SimpleITK/blob/master/CMakeLists.txt#L226-L236
I'm not sure how Elasix build ITK, but the following logic SimpleITK uses to build ITK:
https://github.com/SimpleITK/SimpleITK/blob/master/SuperBuild/External_ITK.cmake#L76-L84
These cmake visibility options should be consistent when building ITK and libraries which use ITK. SimpleITK defaults to building static libraries in the super build where using the hidden options makes since. When building shared libraries it can be best to disable this hidden visibility. There are cases where both options makes sense, so it should be options available to the advance developer building the application.


Default content size

My largest, and perhaps the only stumbling stone with nbpresent so far is the scales of everything. Since the presentation css is the same (?) as in the notebook, most things are tiny in a slideshow.
It would be great if sizes were somehow possible to adjust. (Or am I missing something obvious, and the option is already there?)

#34 is all about that, so I'll close this one, but I do appreciate the feedback. If you have more thoughts on what you want to be able to do, please chime in there!
Today, the nickel fix to embiggen content is to use browser zoom :trollface: Actually, it works quite well, but it is pretty heavy handed.
If you are okay with hacking CSS, you can just make a cell with some raw style in it!
%html
<style>
  .nbpresent_present h1 {font-size: 200%}
 /* etc */
</style>

I don't like that much, though, and that approach isn't scalable, or reusable, long-term.
Near term (next couple weeks), the themes will just be at the deck level (one theme per slideshow) and provide a very limited number of options, configured through the GUI:

title (h1,2,3...), body

font size
font color
font effect (i.e. bold)

background

color
image

position
content (tricky: probably have to embed the whole image in metadata)

inevitably, this will create problems with the white-centric elements in the notebook, so the first challenge will be making key components (widgets, bokeh, etc.) more aware of theming.
Moving forward, we'll make it much more overrideable at the slide and region level, so you can make a giant jumbotron of a single word with an unique accent font on a slide, if you want. All of this needs to be at a data level, so there will be no hacking of CSS/javascript... though of course, in the notebook, nobody can stop you from doing that!
Beyond that, there will be much richer interplay between typography and layout: my holy grail is a visually defined constraint-based layout with its base units informed by the typography: e.g. as you may have seen on some style guides, regions must be one N of the title font apart from other regions, and the region text must line up on a grid.
Even out beyond that is really digging into the readability/cohesiveness of a presentation, invoking best practices from typography, as well as color theory: throw an image in, get a "good" color scheme out.
All of these things present lots of challenges, as key to all of this working is not breaking the regular notebook editing experience, but making it very easy to switch back and forth between the "themed" and "unthemed" approach. one should not feel
Thanks for the continued interest!


feat: move library to typescript code generation

The basic API interface
import {TextToSpeechClient} from '@google-cloud/text-to-speech';
// Import other required libraries
import  * as fs from 'fs';
import * as util from 'util';
async function main() {
  // Creates a client
  const client = new TextToSpeechClient();

  // The text to synthesize
  const text = 'Hello, world!';

  // Construct the request
  const request = {
    input: {text: text},
    // Select the language and SSML Voice Gender (optional)
    voice: {languageCode: 'en-US', ssmlGender: 'NEUTRAL'},
    // Select the type of audio encoding
    audioConfig: {audioEncoding: 'MP3'},
  };

  // Performs the Text-to-Speech request
  const [response] = await client.synthesizeSpeech(request);
  // Write the binary audio content to a local file
  const writeFile = util.promisify(fs.writeFile);
  await writeFile('output.mp3', response.audioContent, 'binary');
  console.log('Audio content written to file: output.mp3');
}

@bcoe @JustinBeckwith 👏
This is the first actual library conversion. Since this one had @types/ published it will go as major.

@xiaozhenliu-gg5 what's up with src/browser.js?  Don't we generate a .ts?  (if we do, we should also add "browser": "build/src/browser.js" to package.json and hope that it just works :) )

@bcoe jsdoc is there! I will take a deeper look later today at what is actually being generated by jsdoc, and likely make fixes, but the general structure of jsdoc comments is already here.

This will also wait for https://github.com/googleapis/gapic-generator-typescript/issues/125 (webpack.js is not taken care of). This will be a quick fix for the generator.

Looks like we also need to address the missing license headers:
protos/protos.d.ts is missing a valid license header.
system-test/fixtures/sample/src/index.ts is missing a valid license header.
system-test/install.ts is missing a valid license header.

@JustinBeckwith License headers in the generated files are addressed in https://github.com/googleapis/gapic-generator-typescript/pull/124.
As for protos.d.ts, I'm not sure it needs to have a license header at all, but if it must, I can add it in gax (compileProtos.ts script generates it). Do you think it's needed, or it's better to ignore .d.ts in the bot?

That's more of a question for OSPO than me :)

OK! License for protos.d.ts is taken care of by https://github.com/googleapis/gax-nodejs/pull/649, then gax v1.9.1 will go out and I'll update this PR.

For running locally npm run docs and comparison between googlapis.dev/nodejs/text-to-speech,  generated comments are parsed by jsdoc correctly. And small inconsistency would be taken care by https://github.com/googleapis/gapic-generator-typescript/pull/127 @bcoe @alexander-fenster

@xiaozhenliu-gg5 @bcoe @JustinBeckwith I hereby declare this library ready! :)
Three things we'll keep working on are:

package.json improvements - it's mostly done, new packages will have system-test script, linkinator stuff already there, but we are adding more stuff there.
generating main src/index.ts for multiple versions - we are thinking what's the best way of doing it.
one s.replace in synth.py will be taken care of by https://github.com/googleapis/gapic-generator-typescript/issues/134

With these three things in mind, I think we can go ahead and release this as a semver major (as discussed, because of DefinitelyTyped types). What do you folks think?

It's ready for another look @JustinBeckwith  :)

Congrats folks!


backup: pass aws, s3 params and set up volumes

This PR shows how we can pass aws, s3 params to backup pod for early feedback.
Once we have converged enough and I have tested it with confidence, I would separate it into two or  more PRs.

let's clean this up based on the new s3 doc?

@xiang90
Sure. I'm doing testing, and fixing problems now.

Closing this.
Will try to submit a couple of smaller PRs instead.


chore(main): release 1.30.0

:robot: I have created a release beep boop
1.30.0 (2024-08-04)
Features

add hyprls (#428) (0e65781)
add nginx-language-server support (#421) (37a336b)
add pbls support (#434) (490d0a9)
Add regal lsp support (OPA rego linter) (#426) (5716924)
add shopify_theme_ls mapping (#412) (ce1b625)
add starpls LSP server (#444) (7c075f0)
add steep configuration (#422) (fd69d5c)
add textlsp (#433) (9ac210a)

Bug Fixes

prefer vim.islist over vim.tbl_islist (#413) (a4caa0d)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/williamboman/mason-lspconfig.nvim/releases/tag/v1.30.0 :sunflower:


Adding the PDU types.

Please note, I'm a few weeks into Rust. I've already picked up a few tricks from going through your source (such as quick_error!), so please bear with me if you find something else that could be improved.
I've opened this PR so that you can see my changes as they happen. That way, you can make comments early on.
I may make small commits, but when it is time to merge, I will tidy up my commit history.

This pull request is now ready. I've added an scpproxy tool for debug/diagnosing issues between SCU/SCP.
USAGE:
    scpproxy [OPTIONS] <destination-host> <destination-port>

FLAGS:
    -h, --help       Prints help information
    -V, --version    Prints version information

OPTIONS:
    -l, --listen-port <listen-port>    The port that we will listen for SCU connections on [default: 3333]

ARGS:
    <destination-host>    The destination host name (SCP)
    <destination-port>    The destination host port (SCP)

Here is an example output of an echo request.
listening on: <IP_ADDRESS>:3333
forwarding to: <IP_ADDRESS>:2222
scu ----> scp: AssociationRQ { protocol_version: 1, calling_ae_title: "ECHOSCU", called_ae_title: "ANY-SCP", application_context_name: "1.2.840.10<IP_ADDRESS>.1", presentation_contexts: [PresentationContextProposed { id: 1, abstract_syntax: "1.2.840.10008.1.1", transfer_syntaxes: ["1.2.840.10008.1.2"] }], user_variables: [MaxLength(16384), ImplementationClassUID("1.2.276.0.7230<IP_ADDRESS>.6.4"), ImplementationVersionName("OFFIS_DCMTK_364")] }
scu <---- scp: AssociationAC { protocol_version: 1, application_context_name: "1.2.840.10<IP_ADDRESS>.1", presentation_contexts: [PresentationContextResult { id: 1, reason: Acceptance, transfer_syntax: "1.2.840.10008.1.2" }], user_variables: [MaxLength(16384), ImplementationClassUID("1.2.276.0.7230<IP_ADDRESS>.6.4"), ImplementationVersionName("OFFIS_DCMTK_364")] }
scu ----> scp: PData { data: [PDataValue { presentation_context_id: 1, value_type: Command, is_last: true, data: [0, 0, 0, 0, 4, 0, 0, 0, 56, 0, 0, 0, 0, 0, 2, 0, 18, 0, 0, 0, 49, 46, 50, 46, 56, 52, 48, 46, 49, 48, 48, 48, 56, 46, 49, 46, 49, 0, 0, 0, 0, 1, 2, 0, 0, 0, 48, 0, 0, 0, 16, 1, 2, 0, 0, 0, 1, 0, 0, 0, 0, 8, 2, 0, 0, 0, 1, 1] }] }
scu <---- scp: PData { data: [PDataValue { presentation_context_id: 1, value_type: Command, is_last: true, data: [0, 0, 0, 0, 4, 0, 0, 0, 66, 0, 0, 0, 0, 0, 2, 0, 18, 0, 0, 0, 49, 46, 50, 46, 56, 52, 48, 46, 49, 48, 48, 48, 56, 46, 49, 46, 49, 0, 0, 0, 0, 1, 2, 0, 0, 0, 48, 128, 0, 0, 32, 1, 2, 0, 0, 0, 1, 0, 0, 0, 0, 8, 2, 0, 0, 0, 1, 1, 0, 0, 0, 9, 2, 0, 0, 0, 0, 0] }] }
scu ----> scp: ReleaseRQ
scu <---- scp: ReleaseRP
shutdown initiated from: SCU

I will be submitting another pull request that will implement an echoscp and echoscu command. They won't be super useful, but they will ensure the correctness of the state machine that will be built with them.

I made the changes you requested. I'm ready for another review.

Also, give me a heads up before you merge, and I'll squash these commits.

Ready for you again.

Ready for you again.


Consistent metric export in "taskrun"

Should adopte knative/pkg wrapper just like others.

Changes

Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:

[ ] Includes tests (if functionality changed/added)
[ ] Includes docs (if user facing)
[ ] Commit messages follow commit message best practices
[ ] Release notes block has been filled in or deleted (only if no user facing changes)

See the contribution guide for more details.
Double check this list of stuff that's easy to miss:

If you are adding a new binary/image to the cmd dir, please update
the release Task to build and release this image.

Reviewer Notes
If API changes are included, additive changes must be approved by at least two OWNERS and backwards incompatible changes must be approved by more than 50% of the OWNERS, and they must first be added in a backwards compatible way.

kind/bug


Why use float_64 for gradient

Hi wang,
I'm just wondering why to convert the gradient Tensor into float64, I thought they might be just float32. And it should be more accurate than SGD required.
https://github.com/hwang595/ps_pytorch/blob/89a1cfa136b957073576fae827d39ef0fb09d2fc/src/distributed_worker.py#L258

Hey Kaiyu, @Stonesjtu. Thanks for pointing this out. There was an issue I faced when developing this prototype that np.float32 can't be fully converted to MPI.FLOAT and vice versa. It could be an potential issue in mpi4py, but I could be wrong. I haven't tested it for the current version combination of pytorch and mpi4py under the gradient compression setting, but I will do that ASAP and report the result under this thread.
If you want, you can raise a PR. Any contribution is highly appreciated.
Thanks!

I have tested np.float32 without a problem. And I don't quite understand what fully converted  means.

Sorry for being confusing @Stonesjtu. The issue I mentioned was related to this line, which I wrote for a old version where there wasn't any gradient compression strategy and each worker just send the raw gradient matrices as numpy array. To send numpy array directly, mpi4py provides a series of APIs with capital character e.g. Isend, Irecv, and etc, where users need to specify datatype in MPI e.g. MPI.FLOAT or MPI.DOUBLE (as I did in this line). The issue is, if I specify .astype(np.float32) and use MPI.FLOAT, wrong data will be received on parameter server side. In this case, based on my test, only np.float64 with MPI.DOUBLE works.
However, all of the forgoing stuff is with respect to an old version. And you're right, the new version with gradient compression works with np.float32 without any problem. I already made changes on the master branch.
Thanks a lot for your contribution!

So, will you try float16 to see the speedup gain? I think half precision is enough in most cases.

Actually, I think what's interesting is to add a --half-precision argument. To be more specific, when enable half-precision, all computation in PyTorch side will convert to HalfTensor (https://pytorch.org/docs/stable/tensors.html#torch.Tensor.half) and all gradient matrix in numpy will be then converted to np.float16. In that case, both computation and communication will scale better. If that's what you're suggesting, then yes, I'm planning on it.

I do think simply transferring float16 helps a lot to reduce the communication overhead.


WIP View Instances for Witherable

should really get rid of all occurances of FunctorMaybe, make a few other odds.ends also be witherable

This overlaps with #62, no?

@danbornside This PR seems to mix a couple of things. Can you open separate PRs for these changes and update the changelog?

Looks like the main content of this is fixed in !62 as @alexfmpe points out.  the rest of the noise is now in a separate PR: !102


HHH-10313 Make SessionImplementor extend WrapperOptions

As per the TODO in AbstractStandardBasicType. This removes the need to allocate a new WrapperOptions for every call and saves a lot of allocations.

@sebersole I was trying to help by merging most of @stuartwdouglas 's performance improvements, but will need your help to evaluate some details.
This patch looks good and passes the tesuite, but there are several casting operations which will assume that the passed SessionImplementor is the one which was patched here to implement WrapperOptions too.
My doubt is: are we able to state with some confidence that integrating frameworks like Spring and Seam, EJB integrationts, etc won't be passing in a custom implementation for the SessionImplementor interface here?
I checked Hibernate Search, and that one should be fine as we extend your beautiful org.hibernate.engine.spi.SessionDelegatorBaseImpl, which inherits this enhancement.

Or should we rework this to make the SessionImplementor explicitly extend WrapperOptions ?
That would make it more explicit, and avoid the need for casting.
Yet as long as the integrating frameworks don't recompile against this latest version, they'll be broken at runtime. (assuming a custom SessionImplementor can in practice reach these internals)

@stuartwdouglas Thanks for this!  I remember making a "mental note" back when I first wrote this code to come back and investigate the instantiations of WrapperOptions.
@Sanne We have always expected that a custom Session implementation also implement SessionImplementor.  Is that what you are asking?  If so, this should be fine.

@Sanne The PR already makes SessionImplementor extend WrapperOptions.  What do you mean in your second comment?

@sebersole thanks for joining :)
No my doubt is slightly different: I fear that several existing third party implementations of SessionImplementor might not be safe to be cast to WrapperOptions. They might not have the implementation for the new methods.

@sebersole to clarify: I'm aware that the issue I mention might be far fetched, but needing on opinion as I was hoping to backport this on 5.0 too.
I guess we could just push it to master if there are doubts.

Ah, I was missing the 5.0 angle.  For 5.0 I guess the first question is whether we expect third party implementors to also extend SessionDelegatorBaseImpl.  If so, that gives us some additional options; if not, I just don't see how this change could be applied to 5.0.  One option for 5.0 would be to type check the incoming Session; if it implements WrapperOptions we can apply this optimization; if it doesn't we continue with what we do today.  I think that might be the best we can get for 5.0

Overall though, I do wonder if it is better to have Session implementors instead return a WrapperOptions object (I tend to prefer delegation and composition over inheritance).  The idea here would be to build/hold the WrapperOptions instance on the SessionImpl and expose that via a new SessionImplementor method (either directly or via interface inheritance with a WrapperOptionsContext interface)

As Sanne and I discussed in chat there are really 2 points here:

Composition/delegation versus inheritance
Compatibility concerns for porting to 5.0

These are independent.
I will implement (1) just because its my preference for coding in general.
The solution for (2) is to not have SessionImplementor extend WrapperOptionsContext in 5.0 (it will in master/5.1).  For 5.0 we will instead have SessionImpl and SessionDelegatorBaseImpl implement WrapperOptionsContext and AbstractStandardBasicType will check to see if the Session implements WrapperOptionsContext and DoTheRightThing depending.  Similarly, SessionDelegatorBaseImpl will need to do some checking of its delegate.

@Sanne Hey, for 5.0, if I have SessionDelegatorBaseImpl implement WrapperOptionsContext how does that effects existing Search, etc builds?  Those delegators would need to be recompiled for that to work?

@sebersole I think that should not be needed, but to be sure I'll try to verify that when you're done.

@Sanne To be clear.. I am worried about users using existing Search, etc builds with a new ORM build

@sebersole Yes I understood. I think that should work, as the code of the two projects will be "paired up" at runtime.

Applied this upstream (in slightly different format).  Thanks again Stuart!

sorry forgot to reply, but FWIW that worked totally fine.
In the meantime, it's not even longer a concern as we upgraded.


Creating Editor simple example

Hi guys! You library looks very promising and i try to use it in my current react project. But i'm facing a problem.
Try to reproduce your basic example to creating a simple react component like this one:

To achieve that download latest npm package: 0.4.3
And after i implement that component and normally just create bundle via webpack (a lot additional react-based libraries already connected to project and they work fine) when i'm trying to serve it i getting an error:

If we gonna try to inspect it it is located to a Editor component.

Did i miss something?
Environment:

OS: Windows 10, x64
Browser: Chrome
npm v6.14.14
node v14.17.5
react-flow-editor v0.4.3
package.json
"devDependencies": {  "@babel/core": "^7.12.3",  "@babel/preset-env": "^7.12.1",  "@babel/preset-react": "^7.12.1",  "babel-loader": "^8.1.0",  "file-loader": "^6.1.1",  "html-loader": "^1.3.2",  "html-webpack-plugin": "^4.5.0",  "react": "^17.0.0",  "react-dom": "^17.0.0",  "react-flow-editor": "^0.4.3",  "react-svg-loader": "^3.0.3",  "webpack": "^5.10.0",  "webpack-cli": "^4.1.0",  "webpack-dev-server": "^3.11.0" },

Hi @Askiater thanks for that report. It seems that setImmediate is not supported by modern browsers anymore.
However, we could replace is by setTimeout.

@Askiater does it work with the latest version 0.6.1 ?

They render in kinda weird position, but know it working! Thanks


Permission dialogs are not popping up

🐛 Bug Report
Inserted the permission boiler-plate code  but permission dialogs are not popping up
  Map<PermissionGroup, PermissionStatus> permissions = await PermissionHandler().requestPermissions([PermissionGroup.location]);
I also inserted the permission in the Android Manifest
 <uses-permission android:name="android.permission.LOCATION"/>
Version: 2.1.2
Platform:

[ ] :iphone: iOS
[Y] :robot: Android

Closing this issue since OP has resolved his problem.


How to restrict access only from localhost?

I want to enable swagger ui but restrict it's access only from localhost. How do i do this with latest swashbuckle?

I think this is a dup of #334


Update version: Bilibili.Livehime version <IP_ADDRESS>53

Pull request has been created with WinGet Automation :rocket:
Microsoft Reviewers: Open in CodeFlow

Url validation error

manifests\b\Bilibili\Livehime\<IP_ADDRESS>53

https://link.bilibili.com/p/help

Http status code: NotFound


Error :This endpoint does not support the user facade

By creating a Invoice i become this Error.
Token ,Key and Sin are correct.
Can anyone help me please?
`11-20 22:09:56: Bitpay\Client\Response Object
(
[raw:protected] => HTTP/1.1 200 OK
Date: Mon, 20 Nov 2017 21:09:55 GMT
Content-Type: application/json; charset=utf-8
Content-Length: 279
Connection: keep-alive
Set-Cookie: __cfduid=d2116c6677c67a2b5881b49d537ccfeb31511212195; expires=Tue, 20-Nov-18 21:09:55 GMT; path=/; domain=.bitpay.com; HttpOnly
Strict-Transport-Security: max-age=31536000
X-Download-Options: noopen
X-Content-Type-Options: nosniff
Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: HEAD,GET,POST,PUT,DELETE,OPTIONS
Access-Control-Allow-Headers: Content-Type,Authorization,Content-Length,X-Requested-With,Cache-Control,X-Accept-Version,x-signature,x-pubkey,x-identity,cf-connecting-ip
ETag: W/"117-DwMzKwkGMJWjPVsJFOJy6dG+Eck"
set-cookie: connect.sid=s%3ApdC1pnpraR9oB5wIzLOVqClDb9dTQAXW.jSywZsiPnKlhb1f7ZO%2BMzs0BhX%2F23rGNVVDsFknLFUM; Path=/; HttpOnly; Secure
Server: cloudflare-nginx
CF-RAY: 3c0e649cca45134d-LHR
{"data":[{"policies":[{"policy":"id","method":"require","params":["Tf2Gzfst1o7p6cZXaCGUNFzSpqGQHgkXRWJ"]}],"resource":"AtsQGS1TZzbQskp7L8GWGkmGwfte8qT6yWseCtmLiciB","token":"ArmcoLsi3qZoj86sFd4mz9","facade":"pos","label":"Modulexpert Bitpay Plugin","dateCreated":1511211874485}]}
[headers:protected] => Array
(
[Date] =>  Mon, 20 Nov 2017 21
[Content-Type] =>  application/json; charset=utf-8
[Content-Length] =>  279
[Connection] =>  keep-alive
[Set-Cookie] =>  __cfduid=d2116c6677c67a2b5881b49d537ccfeb31511212195; expires=Tue, 20-Nov-18 21
[Strict-Transport-Security] =>  max-age=31536000
[X-Download-Options] =>  noopen
[X-Content-Type-Options] =>  nosniff
[Access-Control-Allow-Origin] =>  *
[Access-Control-Allow-Methods] =>  HEAD,GET,POST,PUT,DELETE,OPTIONS
[Access-Control-Allow-Headers] =>  Content-Type,Authorization,Content-Length,X-Requested-With,Cache-Control,X-Accept-Version,x-signature,x-pubkey,x-identity,cf-connecting-ip
[ETag] =>  W/"117-DwMzKwkGMJWjPVsJFOJy6dG+Eck"
[set-cookie] =>  connect.sid=s%3ApdC1pnpraR9oB5wIzLOVqClDb9dTQAXW.jSywZsiPnKlhb1f7ZO%2BMzs0BhX%2F23rGNVVDsFknLFUM; Path=/; HttpOnly; Secure
[Server] =>  cloudflare-nginx
[CF-RAY] =>  3c0e649cca45134d-LHR
)
[body:protected] => {"data":[{"policies":[{"policy":"id","method":"require","params":["Tf2Gzfst1o7p6cZXaCGUNFzSpqGQHgkXRWJ"]}],"resource":"AtsQGS1TZzbQskp7L8GWGkmGwfte8qT6yWseCtmLiciB","token":"ArmcoLsi3qZoj86sFd4mz9","facade":"pos","label":"Modulexpert Bitpay Plugin","dateCreated":1511211874485}]}
[statusCode:protected] => 200

)
11-20 22:09:56: Invoice gesetzt
11-20 22:09:56: Bitpay Kunde gesetzt
11-20 22:09:57: Error im Abschnitt ErstelleBitpay(CreateInvoice)
11-20 22:09:57: Request :POST https://test.bitpay.com:443/invoices HTTP/1.1
Content-Type: application/json
X-BitPay-Plugin-Info: BitPay PHP-Client/0.0.0
User-Agent: BitPay PHP-Client/0.0.0 (PHP 5.6.30)
X-Accept-Version: 2.0.0
x-identity: 02889e4b476a49024998143973107e50372b762dfc5fe39aabb8a4640c51c663f6
x-signature:<PHONE_NUMBER>086589d7f068b4079b81f87e0dd5b3bda6102014975d5ddb60570cd6606fda0220082143156d202fd4a8ce1334335f52376e7181754c7d711b33b0e57b20768884
11-20 22:09:57: Response :HTTP/1.1 401 Unauthorized
Date: Mon, 20 Nov 2017 21:09:57 GMT
Content-Type: application/json; charset=utf-8
Content-Length: 60
Connection: keep-alive
Set-Cookie: __cfduid=d70da7857d3231370ab1c70ddf1c7bcb61511212196; expires=Tue, 20-Nov-18 21:09:56 GMT; path=/; domain=.bitpay.com; HttpOnly
Strict-Transport-Security: max-age=31536000
X-Download-Options: noopen
X-Content-Type-Options: nosniff
Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: HEAD,GET,POST,PUT,DELETE,OPTIONS
Access-Control-Allow-Headers: Content-Type,Authorization,Content-Length,X-Requested-With,Cache-Control,X-Accept-Version,x-signature,x-pubkey,x-identity,cf-connecting-ip
ETag: W/"3c-yVv/7rJRfF6QLK8eJWWlLJx/NBI"
set-cookie: connect.sid=s%3A_WZCEizI1pG5z4hrx36lquVsz-WgkrvH.iR0H%2BubdhtWpHaQL1qcOizEsG0PWb%2BS1M%2BMlk9H%2Ftck; Path=/; HttpOnly; Secure
Server: cloudflare-nginx
CF-RAY: 3c0e64a5a8e83506-LHR
{"error":"This endpoint does not support the user facade"}`

From the error it looks like you're passing a token that is not linked to the POS or Merchant facade.
Did you try to use the 4 examples from the tutorial:
https://github.com/bitpay/php-bitpay-client/tree/master/examples/tutorial

Hello!
The Plugin runs in over 50 Shops but in only 6 Shops i have this Problem
i use a pairingcode

can you email me at pieter at bitpay com ? I expect to need more info & interaction to resolve this.


@envelop/sentry fails subscriptions

Hi! 👋
Firstly, thanks for your work on this project! 🙂
Today I used patch-package to patch<EMAIL_ADDRESS>for the project I'm working on.
Symbol('sentryTracing') is undefined when using subscriptions with graphql-ws (together with fastify and yoga) and as such causes the subscription call itself to fail. Not sure if the package is meant to be used with subscriptions - but at least it shouldn't crash :)
Here is the diff that solved my problem:
diff --git<EMAIL_ADDRESS><EMAIL_ADDRESS>index 1cd1c34..24ffd45 100644
---<EMAIL_ADDRESS>+++<EMAIL_ADDRESS>@@ -36,6 +36,10 @@ const useSentry = (options = {}) => {
     }
     const onResolverCalled = trackResolvers
         ? ({ args: resolversArgs, info, context }) => {
+            if(!context[sentryTracingSymbol]){
+                console.warn('no sentryTracingSymbol present, skipping tracing')
+                return null
+            }
             const { rootSpan, opName, operationType } = context[sentryTracingSymbol];
             if (rootSpan) {
                 const { fieldName, returnType, parentType } = info;

This issue body was partially generated by patch-package.

We have found the same, but without using subscriptions. We do use GraphQL Yoga.

We have found the same, but without using subscriptions. We do use GraphQL Yoga.

I'm also using GraphQL Yoga (made that clearer in the original post) although "plugged into" fastify. Are you using vanilla GraphQL Yoga and get the same consistently?

We use GraphQL Yoga with the envelop plugin registered like so:
async function main() {
	const server = createServer({
		graphiql: process.env.NODE_ENV === 'development',
		endpoint: "/",
		schema,
		context: createContext,
		plugins: [
			useSentry({
				startTransaction: true,
				renameTransaction: false,
				trackResolvers: true,
				includeRawResult: true,
				includeResolverArgs: true,
				includeExecuteVariables: true,
				skip({operationName}) {
					if (operationName == "health") return true
					return false
				},
			})
		]
	})
	await server.start()
}

We need the same patch, even for a very simple query.


Optimize translation process with task batching and flexible CLI modes

Improved Resilience in Translation Process

The translation process can now resume from where it left off in the event of an unexpected interruption.
Since files are only saved once they are fully translated, the system ensures that partially translated files are not left behind, maintaining the integrity of the translation output even when the process is halted.
This allows users to continue the translation process smoothly without having to restart from the beginning, making the translation process more efficient and robust.

(Solved #21)
Example:

If the translation process is stopped midway through, simply rerun the command, and it will pick up from the last completed file instead of restarting from scratch.

# Resuming from where the process left off after an interruption:
translate -add -l "ko"

Batch image and markdown translation tasks in groups of 5 for efficient async processing.

Group translation tasks for both images and markdown files into batches of 5 for more efficient asynchronous processing.
This ensures smoother handling of large sets of files and improves performance in translation tasks.

Update progress bar in real-time using tqdm_asyncio.gather for both images and markdown files.

The progress bar for image and markdown translation now updates in real-time, showing the progress of translation tasks using tqdm_asyncio.gather.
This enhances visibility during the translation process, providing an accurate status of how many files are being processed and completed.

Here is an example:
(.venv) C:\Users\sms79\dev\co_op_translator\src\co_op_translator\test_repo>poetry run translate -l "es" -u
Warning: The update command will delete all existing translations for 'es' and re-translate everything.
Do you want to continue? Type 'yes' to proceed: yes
Proceeding with update...
Translating remaining images: 100%|████████████████████████████████████████████| 3/3 [00:46<00:00, 15.55s/it]
Translating remaining markdown files: 100%|███████████████████████████████████| 1/1 [02:05<00:00, 125.62s/it]

Ensure proper handling of translated files and skipping existing translations when using --add mode.

When using the --add mode, the system properly skips files that have already been translated, avoiding redundant translations.
This improves the efficiency of the translation process, particularly when working with incremental translations.

Added CLI support for modes: --add, --update, --images, --markdown.

New CLI options are added to control the translation process:

--add: Adds new translations without deleting existing ones.
--update: Updates translations by deleting and recreating them.
--images: Only translate image files.
--markdown: Only translate markdown files.

Example Commands
Here are some example commands to demonstrate how the CLI modes can be used:
# Adds a new translation in Spanish without deleting existing translations
translate -l 'es' --add

# Updates only French markdown files by deleting and re-translating
translate -l 'fr' --update --markdown

# Adds a new translation for Korean images only
translate -l 'ko' --images

I have reviewed the changes and everything looks good.


FM: descriptors should have the same length as input keypoints

Currently when we use the getBriefDescriptors function, the returned array of descriptors doesn't always have the same length as the input keypoints.

The issue lies in the fact that the keypoints passed by the user can be too close to the border to be processed by the BRIEF algorithm.
Indeed, the algorithm uses a patch around the keypoints with a size of patchSize. Therefore, all keypoints too close to border must be removed.
Additionally, since we use rBrief, we also have to handle orientation,  and our algorithm cuts the smallest horizontal rectangle around the rotated patch, so this can have a maximal size of Math.sqrt(2)*patchSize.
The patch size is typically 30, so we will actually ignore a big part of the image. Also, this algorithm simply will not work with smaller images.
Some references about this issue:

https://stackoverflow.com/questions/12911276/calculating-descriptors-for-dense-keypoints
https://answers.opencv.org/question/18378/how-do-descriptors-treat-image-bounds/

Visibly, the keypoints should indeed be ignored.
Also, the keypoints are ignored inside of the BRIEF algorithm, which then returns an array of new keypoints and the corresponding descriptors.


floating_maximum_size initial implementation

Thanks!

I think these patches floating_maximum_size and  floating_minimum_size partially solves #604 and #682.
Or at least it "hides" the bad effect of the 1x1 issue from wlc.
And thank you; keep it going :)


Enable support for Github Enterprise when using github auth

The Github auth part is nice,  but you will find many orgs that prefer not to host their code on Github.com.  That said, they may still use github,  just the enterprise version instead.  This should be a simple change to pull out the hard coded URI for github.com and allow a user to insert the proper equivalent in to the config.php file.

According their documentation, the support of OAuth for Github Enterprise will be removed in November 2015: https://help.github.com/enterprise/2.2/admin/guides/user-management/using-github-oauth/

I thought I remembered a conversation about this with github, the gist of which was "misleading article".  Let me verify with them that this functionality is being fully remove and get back to you.
Sent from my iPhone

On Jul 28, 2015, at 4:53 AM, Frédéric Guillot<EMAIL_ADDRESS>wrote:
According their documentation, the support of OAuth for Github Enterprise will be removed in November 2015: https://help.github.com/enterprise/2.2/admin/guides/user-management/using-github-oauth/
—
Reply to this email directly or view it on GitHub.

Okay, got a response back from Github and I am correct.  What's actually being turned off is the ability for github enterprise instances to oauth link to github.com (as they've provided other auth solutions there).   Application oauth linkages shall continue to work.   Relevant excerpt from my conversation with them below:
Colin Seymour (GitHub Enterprise)
Jul 28, 9:40 AM
So if I understand correctly, applications will still be able to authenticate against my internal enterprise instance (which is what I want to maintain).
Is my understanding correct?
Yes. That is correct and this won't be changing any time soon.
— Colin
Cheers,
Steve
Sent from my iPhone

On Jul 28, 2015, at 4:53 AM, Frédéric Guillot<EMAIL_ADDRESS>wrote:
According their documentation, the support of OAuth for Github Enterprise will be removed in November 2015: https://help.github.com/enterprise/2.2/admin/guides/user-management/using-github-oauth/
—
Reply to this email directly or view it on GitHub.

It's now possible to define custom urls for Github OAuth (in dev version only).
See https://github.com/fguillot/kanboard/blob/master/docs/github-authentication.markdown#github-entreprise

Thanks!
Sent from my iPhone

On Aug 1, 2015, at 1:52 PM, Frédéric Guillot<EMAIL_ADDRESS>wrote:
It's now possible to define custom urls for Github OAuth (in dev version only).
See https://github.com/fguillot/kanboard/blob/master/docs/github-authentication.markdown#github-entreprise
—
Reply to this email directly or view it on GitHub.


feat: new nvidia bmc version

see https://docs.nvidia.com/networking/display/bluefieldbmcv2404
Signed-off-by: Boris Glimcher<EMAIL_ADDRESS>

CI test failed https://github.com/opiproject/ansible-opi-dpu/actions/runs/8990987516/job/24697554440?pr=80
Should this test be required for the Ansible project?


Some glyphs not rendering properly

I like the font that Superuser currently has, but it has some missing glyphs that render with a default character. It would be nice to either have the rest of those glyphs filled in, or to have a different font that fits the aesthetic of the theme and is clearly legible. Even a basic sans font would work if it doesn't look to jarring compared to the rest of the theme.

A few notes about the font:

It has to be free for non-commercial use.
All glyph sets would be preferred, but English at the minimum, with hope for Japanese as well.


Conflicting protobuf-java versions

The situation at the moment:

reader-osm: protobuf-java 3.11.4 as a dependency of osmosis-osm-binary
reader-gtfs: protobuf-java 2.6.1as dependency of gtfs-realtime-bindings

This causes problems in my draft PR (#2205) as protobuf v3 classes are not available.
We should probably move to a newer version of the gtfs-realtime-bindings to avoid this.

Thanks for pointing this out. Unfortunately gtfs realtime 0.0.7 seems to use only protobuf 3.6.1. And protobuf 3.14.0 seems to be the most recent version.
But maybe 3.x is compatible from a Java standpoint? Can you try if 0.0.7 passes tests and still makes the problems you mentioned?

Switching to gtfs-realtime-bindings 0.0.7 provided by io.mobilitydata.transit while excluding the transient dependency on protobuf 3.6.1 seems to fix the issue. At least the unittests in my draft PR pass now.
Should i create a separate PR for the fix or can i add this to my existing POM cleanup PR? https://github.com/graphhopper/graphhopper/pull/2200

Let's wait what @michaz says :)

Oh, please go ahead, as long as it works. There's nothing special happening there.

Fixed by #2200


Dev --> Master 02-21-2020: SGQL reference, DNS note update, MC coming soon update

Hello @astuteape,Thanks again for the PR! We appreciate your contribution and look forward to                                              continued collaboration. Thanks!                                             Team SendGrid DX


Resetting navigation state on v1.0.0-beta.22

Current Behavior
Given the following code that worked on v1.0.0-beta.21:
Navigator structure
const AuthNavigator = StackNavigator({
  OnboardingScreen: {},
  LoginScreen: {},
  SignUpScreen: {},
});

const UserNavigator = DrawerNavigator({
    ProfileStack: {
      screen: StackNavigator({
        ProfileScreen: {
          screen: ProfileScreen,
          navigationOptions: {
            accessibilityLabel: 'Profile Screen',
          },
        },
        LeaderboardScreen: {},
      }),
    },
}, {
    headerMode: 'none',
    drawerWidth: 300,
    drawerPosition: 'left',
    contentComponent: props => <DrawerContent {...props} />,
});

export default StackNavigator(
  {
    Authentication: { screen: AuthNavigator },
    User: { screen: UserNavigator }, // Logged in
  },
  {
    initialRouteName: 'Authentication',
    headerMode: 'none',
  },
);

Reducer (this previously did work on v1.0.0-beta.21)
function navReducer(state = initialState, action) {
  switch (action.type) {
    // Settings are retrieved from secondary storage
    case REHYDRATE: {
      // Check if user has been logged in
      if (action.payload.auth.status === "loggedin") {
          // Go to Profile
          return AppNavigator.router.getStateForAction(
            NavigationActions.reset({
              index: 0,
              key: null,
              actions: [
                NavigationActions.navigate({
                  routeName: "User",
                  params: { title: `${action.payload.user.name}'s profile` }
                })
              ]
            })
          );
        }
    }
  }
};

Result from using reset:

Adding NavigationActions.init() does the following:
            return AppNavigator.router.getStateForAction(NavigationActions.reset({
              index: 0,
              key: null,
              actions: [
                NavigationActions.init({ routeName: 'User' }),
                NavigationActions.navigate({
                  routeName: 'ProfileScreen',
                  params: { title: `${action.payload.user.name}'s profile` }
                }),
              ],
            }));

Result from using reset with NavigationActions.init:

Expected Behavior
The reset action should allow users to configure the navigation state from the root. Instead this doesn't seem to appear functional.
Your Environment

software
version

react-navigation
v1.0.0-beta.22

react-native
v0.51.0

node
v6.10.3

npm or yarn
<EMAIL_ADDRESS>

Uhm thanks for reporting.
This is probably related to one of these two PRs we merged in latest:

https://github.com/react-community/react-navigation/pull/895
https://github.com/react-community/react-navigation/pull/3094

But I'm not really sure why.

For more clarification I updated the navigation structure. One of the root navigators is a drawer navigator and that's the one I'm trying to reset to which doesn't allow me.

What seems to fix it is setting the drawer routes in your navigation options. It now seems to be required as long as you've set navigation options for the drawer (as per pull request #1803). This should really be defaulted though.
{
    drawerOpenRoute: 'DrawerOpen',
    drawerCloseRoute: 'DrawerClose',
    drawerToggleRoute: 'DrawerToggle'
    headerMode: 'none',
    drawerWidth: 300,
    drawerPosition: 'left',
    contentComponent: props => <DrawerContent {...props} />,
}

Boy better testing needs to be done before things go to a release. Spent about 3 hours figuring out what was wrong. Finally to land here.

Same here, spent more than 3 hours digging into the code and rolling back commits (blaming self) since this issue didn't allow further app execution and development...

add routeName: payload.routeName  at line 42  NavigationActions.js  @jamsch

Same here, lost 2 hours... beta 22 has undocummented breaking changes.
Too bad for a 8k stars library

We are doing our best to have the library is a good spot - sadly in this situation, something slipped through.
I've modified the Release Notes accordingly to @jamsch last comment (thanks for that btw).

Just updated from beta-11 to 1.5.7 and found the same message, also because of the drawer, but none of the proposed solutions are working.

hi there! if this is still a bug can you create a new issue that reproduces the bug on https://snack.expo.io? thanks!


Run tap via API

Can tap be executed via JS API (instead of shell CLI)? I mean:
Instead of running this in a shell:
$ tap --bail --color --reporter=spec test1.js test2.js

do the same in Node:
var tap = require('tap');

tap.xxxxx

Well, even the tap provided executable spawns a process, so the answer is not :)

You can spawn it as a child process if you want?
var tapprocess = child_process.spawn(process.execPath, [
  require.resolve('tap/bin/run.js'), '--bail', '--color', ... ])

Or you can use t.spawn() to run the various tests (which is basically what the included bin/run.js file does)

Sure. What I meant is running tap via pure JS API without spawning a child process. But that's ok.
Thanks.


Discover local block devices using maya-agent

FEATURE REQUEST
What happened:
The feature is about maya-agent runs on minions and provide the local block device information
What you expected to happen:
It is expected to provide the local block device information

As the block device discovery is only local, it is not required to implement protocols involving tcp/ip like scsi. fdisk -l displays the block device/partition info. This command returns the result in string format and manual processing of string. Using lsblk -J would be a good idea, as the result will be on json format and the necessary columns can be processed later

@gkGaneshR:
Check if there are any libraries that can be used, which can abstract the os-dependencies - similar to osquery ?

@kmova:
osquery exposes certain os related info, but block device info is not present there, since it is developed for the purpose of security related monitoring. The other alternatives provides even less features like process and ports exposure. I have gone through the internals of osquery and found out they do the same terminal commands but they are exposed as sql query. I have completed the code using os-exec lsblk. Can I raise a PR?

Yes @gkGaneshR -- go ahead.

This issue is the initial task towards implementing the usecase in https://github.com/openebs/openebs/issues/194

Im a little puzzled about certain terms used in #194 but that's OK. The maya-agent needs to do a whole lot more (eventually) for us then the disks. The disks, however -- are the low hanging fruit.
in #194 several things are mentioned that are needed for the disk, the list is a little short but a good start. Things that must be added to the list are -- in no particular order:

physical location (ie enclosure slot number)
fault led manipulation
ok2rm led manipulation (if applicable)
extend log pages (read write errors etc, number of corrections etc)
in case off SSD wear levers
rotational speed
temperature
FW revision level
what partition is being used by what OpenEBS volume
serial number
manufacture
model
state (online, removed, etc)
.... likely more things as we go

This information needs to be extracted by means of an API such that other consumers, be it tools, CLI k8s or what have you can make use of it.
Some (most) of the info can be abstracted via libudev and libmnt (which gets it from sys/proc interface) other require us to periodically -- send SCSI commands to devices.

@gkGaneshR osquery was originally developed for this yes but has gained a more generic role. Your suggested approach of using lsblk and fdisk will not provide the level of detail we typically need, if we were to leverage osquery -- we can extend it easily. Also -- the other features it brings are useful for other things we need to maya agent to "know"

@gila @kmova lsblk will not only present the columns which we are currently showing but also the following fields:
NAME  device name
KNAME  internal kernel device name
MAJ:MIN  major:minor device number
FSTYPE  filesystem type
MOUNTPOINT  where the device is mounted
LABEL  filesystem LABEL
UUID  filesystem UUID
PARTTYPE  partition type UUID
PARTLABEL  partition LABEL
PARTUUID  partition UUID
PARTFLAGS  partition flags
RA  read-ahead of the device
RO  read-only device
RM  removable device
HOTPLUG  removable or hotplug device (usb, pcmcia, ...)
MODEL  device identifier
SERIAL  disk serial number
SIZE  size of the device
STATE  state of the device
OWNER  user name
GROUP  group name
MODE  device node permissions
ALIGNMENT  alignment offset
MIN-IO  minimum I/O size
OPT-IO  optimal I/O size
PHY-SEC  physical sector size
LOG-SEC  logical sector size
ROTA  rotational device
SCHED  I/O scheduler name
RQ-SIZE  request queue size
TYPE  device type
DISC-ALN  discard alignment offset
DISC-GRAN  discard granularity
DISC-MAX  discard max bytes
DISC-ZERO  discard zeroes data
WSAME  write same max bytes
WWN  unique storage identifier
RAND  adds randomness
PKNAME  internal parent kernel device name
HCTL  Host:Channel:Target:Lun for SCSI
TRAN  device transport type
SUBSYSTEMS  de-duplicated chain of subsystems
REV  device revision
VENDOR  device vendor
i couldn't find disk temperature on lsblk and the temperature_sensors column is not working on osquery as well. hddtemp is another package with gives temperature of disk specified. ok2rm is already present on lsblk, which we have removed later on our release(RM column).  Model, serial, vendor are also displayed. A column called 'STATE' in lsblk has status to be running /null. I think, to check if the device is connected in cluster or not, we will be using crd to watch crd/iscsi discover. Please confirm.


Unable to Login

Registered admin user
Clicked login
And it is still showing login icon at the top right corner( like fresh login page)

Do you have any errors in the API logs? Did you register the admin as a user?


Oak optimize

Optimize oak:

improve readability
decrease computation time

Thanks. Also, would it make sense to refactor the run() function since it's over 200 LOC? It can be a separate PR.

Sure, I will refactor it in a separate PR


Error line 4

Hello,
After running the script command, I got that:
line 4, in
from trakt import *
ModuleNotFoundError: No module named 'trakt'

Same in here

Please ?

Did you install the required packages first? pip install tinydb trakt
cf: https://github.com/lukearran/TvTimeToTrakt#install-required-libraries

Did you install the required packages first? pip install tinydb trakt cf: https://github.com/lukearran/TvTimeToTrakt#install-required-libraries

yes

Did you install the required packages first? pip install tinydb trakt cf: https://github.com/lukearran/TvTimeToTrakt#install-required-libraries

yes

Let me try and reproduce this. Which OS are you running the script from (e.g Windows 11, macOS)?

Did you install the required packages first? pip install tinydb trakt cf: https://github.com/lukearran/TvTimeToTrakt#install-required-libraries

yes

Let me try and reproduce this. Which OS are you running the script from (e.g Windows 11, macOS)?

WIndows 11 yh

I can't reproduce this issue on a clean installation of Windows 11 with Python 3.10
Please verify that you've configured Python and Pip correctly on your local environment.
But I'll keep the issue open for anyone to report a solution in the future.

Hey, you can try installing the packages using python -m pip install tinydb trakt, it can solve your issue if you have multiple pip versions installed.

Well, still not working, I give up


Automatic PR from RestAPI-PR1871

Generated from RestAPI PR: https://github.com/Azure/azure-rest-api-specs/pull/1871

Codecov Report

Merging #1538 into master will increase coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1538      +/-   ##
==========================================
+ Coverage   54.23%   54.23%   +<.01%
==========================================
  Files        3585     3585
  Lines       88235    88233       -2
==========================================
- Hits        47853    47852       -1
+ Misses      40382    40381       -1

Impacted Files
Coverage Δ

...work/v2017_09_01/models/patch_route_filter_rule.py
46.15% <0%> (ø)
:arrow_up:

...17_09_01/models/verification_ip_flow_parameters.py
38.46% <0%> (ø)
:arrow_up:

...17_09_01/operations/network_watchers_operations.py
6.69% <0%> (ø)
:arrow_up:

...2017_09_01/operations/load_balancers_operations.py
95.93% <0%> (ø)
:arrow_up:

...mt/network/v2017_09_01/models/network_interface.py
100% <0%> (ø)
:arrow_up:

...017_09_01/models/express_route_service_provider.py
100% <0%> (ø)
:arrow_up:

...2017_09_01/models/express_route_circuit_peering.py
100% <0%> (ø)
:arrow_up:

...gmt/network/v2017_09_01/models/ip_configuration.py
33.33% <0%> (ø)
:arrow_up:

...ons/load_balancer_network_interfaces_operations.py
37.5% <0%> (ø)
:arrow_up:

...ork/v2017_09_01/models/vpn_client_configuration.py
100% <0%> (ø)
:arrow_up:

... and 85 more

Continue to review full report at Codecov.

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


Refactor: EventProvider

Abstract
Make EventProvider implementations stand-alone applications (#49).
Steps

[ ] Convert calingen.contrib.providers.german_holidays to an actual Django app

[ ] There are 17 dedicated EventProvider in this package. Possibly enable activation of them by a setting.

[ ] Get rid of calingen.settings.CALINGEN_EXTERNAL_EVENT_PROVIDER
[ ] Adjust documentation accordingly
[ ] Have a look at calingen.settings.CALINGEN_MISSING_EVENT_PROVIDER_NOTIFICATION

[ ] Does it work with the new way of providing EventProvider?
[ ] Can this be enhanced?

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 5 (0.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.3%) to 97.505%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

calingen/contrib/providers/german_holidays/apps.py
0
5
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.3%

Covered Lines:
1722

Relevant Lines:
1761

💛  - Coveralls


Fixed bug in options.activation

If we didn't reset the options.activation to undefined, the convOptions value in buildLinearBottleneck_ will be rewrote with last activation value.

@BruceDai, @huningxin, PTAL, thanks!
Cc/ @miaobin, thanks for reporting the issue.

LGTM, thanks @Honry


Radzon Components not working in Latest Preview Blazor

Created a project and added Radzen Components as per tutorial.  All worked when the project was net core 7 Server Side Blazor.  After upgrading to the new Preview of Blazor in .NET 8 the component stopped working.
Randomly added a Datepicker to the top right of the page under search.  This was working fine until upgrade.  No other libs/css has been updated apart from the nuget packages required for the latest preview.
To see result and reproduce you can find my test repo at here.
You can see that selecting date from Datepicker does nothing.
Putting this as a bug as not found any resolution.

You can check this forum thread which explains why this happens: https://forum.radzen.com/t/sidebar-not-working-in-net-8-rc1-experiment/15198
In short this is by design in .NET 8 Blazor - layouts are not interactive by default which means components don't fire events.

Appreciate the details this was not easy to track down in the forum.  For those who have same issue. read the linke provided above it explains what is happening.


Use "X as Y" for dipdup imports in callbacks

Hi. @droserasprout, please can you add more explanation and context to this so I can attempt it?

Hi @princeibs! This ticket is for our team to track progress on task. I have created a "help wanted" tag to track tickets suitable for external contributors and marked some.
https://github.com/dipdup-io/dipdup/issues?q=is%3Aopen+label%3A"help+wanted"+sort%3Aupdated-desc


I can not connect to internet

I install wire guard successful buy client after connect can not use internet!?!

I am having the same problem.

same problem

what is the system/dist, and where is it hosted?

Ubuntu 22.04, German Hetzner

I've never used German Hetzner, but does it have a non-system firewall in which it blocks remote access ports?

I can not handshate, is mtu must be special number?

My power can be any value, but is there a firewall that is managed via the web by your provider?
In Oracle Cloud I need to release the virtual interface ports to be able to use any server, Take a look at this issue:  https://github.com/angristan/wireguard-install/issues/321#issuecomment-1038285584

I got same issue in both Vultr and HostHatch providers, I did try Ubuntu 20 and Debian 10, 11, 12. all of theses options have no internet issues.


Fix typo

Codecov Report

Merging #2 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master       #2   +/-   ##
=======================================
  Coverage   96.33%   96.33%
=======================================
  Files           1        1
  Lines         273      273
  Branches       49       49
=======================================
  Hits          263      263
  Misses          5        5
  Partials        5        5

Impacted Files
Coverage Δ

triehash.pl
96.33% <100%> (ø)
:arrow_up:

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 971282a...d561e74. Read the comment docs.


Needed Solution: Integer to Roman

Link - https://leetcode.com/problems/integer-to-roman/submissions/
Preferred Languages: - C++, Java, Python, Javascript
Code along with an easy-to-understand, and proper explanation of the solution will make a valid contribution.
Instructions: -
Make a folder, and rename it to the problem's title.
Add your code file along with a markdown containing the code's explanation and problem link inside the folder.
Do add your name and GitHub ID at the top of the markdown and code if you wish to seek credits.

I would like to do this @Jimmy290901 but is your org still included for hacktober cause many orgs asking for DSA solutions have been excluded for not followinng guidelines


[e2e]: go workflow_dispatch main workflow_inputs-noldflags slsa3

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/11510261149
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.go.workflow_dispatch.main.workflow_inputs-noldflags.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.go.workflow_dispatch.main.workflow_inputs-noldflags.slsa3.yml
Trigger: workflow_dispatch
Branch: main
Date: Fri Oct 25 01:36:58 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/11527768716
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.go.workflow_dispatch.main.workflow_inputs-noldflags.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.go.workflow_dispatch.main.workflow_inputs-noldflags.slsa3.yml
Trigger: workflow_dispatch
Branch: main
Date: Sat Oct 26 01:36:36 UTC 2024
Tests are passing now. Closing this issue.