text:
Initialize lunr using a promise rather than a function?

Hi,
Is there a way to pass in a promise to initialize lunr instead of a function?
I want to do a non-blocking stream read to load data for lunr to index, a promise would allow me to keep things async. Any suggestions?
Thanks

Hi

Is there a way to pass in a promise to initialize lunr instead of a function?
BTW this is not an issue IMMO.

just wrap into a Promise the lunr() index creation:
function createLunrIndex(documents,fieldNames) {

    return new Promise( (resolve,reject) => {

      const idx = lunr(function() {
         //
        // load data
        // ...
      })

       resolve(idx)
    });
}

I want to do a non-blocking stream read to load data for lunr to index,

this is maybe another story. Do you want to add dynamically documents after the index creation?
That's seems not possible, see: https://stackoverflow.com/a/44086343/1786393

async function createIndex(): Promise<lunr.Index>{

    const builder = new lunr.Builder();
    builder.pipeline.add(
        lunr.trimmer,
        lunr.stopWordFilter,
        lunr.stemmer
    )
    builder.searchPipeline.add(
        lunr.stemmer
    )

    builder.ref('id');
    builder.field('keywords');

    await addObjectsToIndex();

    return builder.build();
}

async function addObjectsToIndex():Promise<void>{
   // do async stuff here
}

authors: elega9t regnete solyarisoftware


text:
Build enhancements

Used .net docker images suggested by @jon4hz.
Added the parallel job build flag to speed build up

A pull request with the enhancements by @jon4hz
I also added the parallel jobs build to the make command in the build-libs-linux.sh file.  I debated over whether to add this or not.  It could make tracking down a build issue slightly more difficult, but it does increase the build speed quite substantially which is a 'quality of life' improvement.  I'm ok to take the parallel job enhancement out if desired... or maybe make an environmental flag variable that turns it off and on...

The parallel stuff has to be optional. Build times are not a priority since mining pools are not updated that frequently to keep downtimes in check.

i agree with you, definitely needs to be reworked.

Is this still being worked on?

I opened a new PR with just the dockerfile modified.
https://github.com/oliverw/miningcore/pull/1502

source: gharchive/pull-request

authors: oliverw snoby

repo: oliverw/miningcore

license: MIT

license_type: permissive

license_source: github-api


text:
OLLAMA_MODEL_DIR is not reflecting on MacOS

What is the issue?
I tried both the executable or home brew ollama and in both cases OLLAMA_MODEL_DIR is not reflecting.
launchctl getenv OLLAMA_MODEL_DIR  does show the location and I presisted it on a plist file to work after restart.
I have also tried the old school export OLLAMA_MODEL_DIR=  in the ~/.zshrc  file to no luck.
Not sure what else to do.
OS
macOS
GPU
Apple
CPU
Apple
Ollama version
No response

Hey @yusufaly The env variable is OLLAMA_MODELS. You can get a full list of supported environment variables w/ ollama serve -h.

source: gharchive/issue

authors: pdevine yusufaly

repo: ollama/ollama


text:
ci: build dir changed

Remove no longer relevant build log dir
The build artifacts are no longer in ./build

trivial fix for release build


text:
RFE: Support for pedestal washer attachment monitoring

Is your feature request related to a problem? Please describe.
I have a pedestal washer attached to my washer which is available in the LG ThinQ app but not yet visible to Home Assistant.
Describe the solution you'd like
I'd like to be able to monitor my pedestal washer along with my main washer.
Describe alternatives you've considered
I am able to check the pedestal washer via the LG ThinQ app on my mobile.
Additional context
LGE Devices integration diagnostics download: Search for mini_washer .
config_entry-smartthinq_sensors-e48f79ce99e7bf33ea365d5094032b87.json.txt
I'll collect some mini_washer data when it's active next time I'm home.
Screen caps of the LG ThinQ app's washer screens:

Implement this feature was more complex that I was expecting, but now should be available with last release. Please test it and le me know.

Thank you. I noticed my pedestal washer being available in HA after updating this morning.


text:
🛑 MediaNet is down

In 1ee67ac, MediaNet (https://medianet-pa.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: MediaNet is back up in c045606.

repo: olmloa/upptime


text:
[Sync] upstream

Fixes #<issue_number_goes_here>

It's a good idea to open an issue first for discussion.

[ ] Local tests pass (running run_desktop_tests.sh)
[ ] Tested against boards

[ ] Nordic nRF52840 DK
[ ] Nordic nRF52840 Dongle (JTAG programmed)
[ ] Nordic nRF52840 Dongle (DFU programmed)
[ ] Makerdiary nRF52840 MDK USB Dongle

[ ] Appropriate changes to README are included in PR

Pull Request Test Coverage Report for Build 3297316262

240 of 317 (75.71%)  changed or added relevant lines in 8 files are covered.
289 unchanged lines in 5 files lost coverage.
Overall coverage decreased (-1.4%) to 87.642%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/env/test/upgrade_storage.rs
13
14
92.86%

src/ctap/mod.rs
50
52
96.15%

src/api/customization.rs
0
3
0.0%

src/api/upgrade_storage/helper.rs
117
121
96.69%

src/env/tock/storage.rs
25
92
27.17%

Files with Coverage Reduction
New Missed Lines
%

libraries/persistent_store/src/buffer.rs
1
49.7%

src/env/tock/storage.rs
2
35.59%

src/ctap/status_code.rs
3
35.29%

src/ctap/client_pin.rs
9
98.13%

libraries/persistent_store/src/store.rs
274
62.57%

Totals

Change from base Build 2965510469:
-1.4%

Covered Lines:
14623

Relevant Lines:
16685

💛  - Coveralls

authors: coveralls oluceps

repo: oluceps/OpenSK


text:
Update support page with image.sc forum instead of old forums and lists

As requested by @pwalczysko (#training channel 22:33) - updated the support page with the image.sc forum instead of old forums and mailing lists.
Do we want to link to archives, or will they be ported soon enough?

Do we want to link to archives, or will they be ported soon enough?

I wouldn't for today to reduce confusion. We can re-evaluate after this week.
cc: @pwalczysko

Merging and releasing so this is in place for day 2 of ELMI. Happy to iterate if there are any issues.
Note: I'm unsure if there's a color policy on the icons other than ("roughly the same number of each"). We might want to place the rule in the HTML as a comment though. I certainly would have missed to update them. (See gh-298)

@will-moore Thank you very much for this quick action

authors: joshmoore pwalczysko will-moore


text:
Merge revision into develop

No conflicts but various pep8 issue fixed in 195a732

test me

Build Passed :ok_hand:
You can safely merge 'merge-revision-into-develop' into 'develop'.

:+1:

authors: DavidMansolino cyberbotics-jenkins

repo: omichel/webots


text:
Travis Test Suite

The goal of this PR is to investigate the use of travis for replacing completely jenkins.
Fix also #537

The result of sysinfo on travis is not very promising:
./webots --sysinfo
System: Linux 4.15.0-1028-gcp x86_64
Processor: Intel(R) Xeon(R) CPU @ 2.30GHz
Number of cores: 2
Warning: This plugin does not support setParent!
Warning: QOpenGLFunctions created with non-current context
./webots: line 44: 14063 Segmentation fault      (core dumped) "$webotsHome/bin/webots-bin" "$@"

I managed to get the sysinfo working:
./webots --sysinfo
System: Linux 4.15.0-1028-gcp x86_64
Processor: Intel(R) Xeon(R) CPU @ 2.30GHz
Number of cores: 2
Warning: This plugin does not support setParent!
OpenGL vendor: VMware, Inc.
OpenGL renderer: llvmpipe (LLVM 6.0, 256 bits)
OpenGL version: 3.0 Mesa 18.0.5

Still a few Failiures, but quite a lot of tests are starting to work (the one with sound and movie are probably going to be the hardest):
System              : Linux 4.15.0-1028-gcp x86_64
Processor           : Intel(R) Xeon(R) CPU @ 2.30GHz
Number of cores     : 2
OpenGL vendor       : VMware, Inc.
OpenGL renderer     : llvmpipe (LLVM 6.0, 256 bits)
OpenGL version      : 3.0 Mesa 18.0.5

### api test

OK: accelerometer
OK: asymmetric_friction
OK: battery
OK: brake
OK: camera_color
OK: camera_color_focus
OK: camera_color_motion_blur
OK: camera_color_spherical
OK: camera_image_update
OK: camera_noise_mask
OK: camera_recognition
OK: camera_revert
OK: center_of_mass_and_contact_points
OK: compass
OK: device
OK: display
FAILURE with display_attach_camera: Wrong display attaching the camera (green shape not detected)
OK: display_infrared
OK: distance_sensor_enable_disable
OK: distance_sensor_infra-red
OK: distance_sensor_laser
OK: distance_sensor_resolution
OK: distance_sensor_sonar
FAILURE with /home/travis/build/omichel/webots/tests/api/worlds/emitter_receiver_determinism.wbt: Timeout the results file has not been written quickly enough
OK: emitter_receiver_enable_disable_serial_emitter_radio_receiver
OK: emitter_receiver_enable_disable_infra_red_emitter
OK: emitter_receiver_enable_disable_radio_emitter
OK: emitter_receiver_enable_disable_serial_receiver
OK: emitter_receiver_enable_disable_infra_red_receiver
OK: emitter_receiver_infra-red_emitter_0_receiver_0
OK: emitter_receiver_infra-red_emitter_1
OK: emitter_receiver_infra-red_receiver_2
OK: emitter_receiver_infra-red_receiver_3
OK: emitter_receiver_infra-red_aperture_emitter_0
OK: emitter_receiver_infra-red_aperture_emitter_1
OK: emitter_receiver_infra-red_aperture_receiver_2
OK: emitter_receiver_infra-red_aperture_receiver_3
OK: emitter_receiver_invalid_function_call_emitter
OK: emitter_receiver_invalid_function_call_receiver
OK: emitter_receiver_physics_plugin
OK: emitter_receiver_radio_emitter_0
OK: emitter_receiver_radio_emitter_1
OK: emitter_receiver_radio_receiver_2
OK: emitter_receiver_radio_receiver_3
OK: emitter_receiver_radio_aperture_emitter_0
OK: emitter_receiver_radio_aperture_emitter_1
OK: emitter_receiver_radio_aperture_receiver_2
OK: emitter_receiver_radio_aperture_receiver_3
OK: emitter_receiver_serial_emitter_0
OK: emitter_receiver_serial_emitter_1
OK: emitter_receiver_serial_emitter_2
OK: emitter_receiver_serial_receiver_3
OK: emitter_receiver_serial_aperture_emitter_0
OK: emitter_receiver_serial_aperture_emitter_1
OK: emitter_receiver_serial_aperture_receiver_2
OK: emitter_receiver_serial_aperture_receiver_3
OK: emitter_set_channel_emitter
OK: emitter_set_channel_receiver_1
OK: emitter_set_channel_receiver_2
OK: gps
OK: gps_coordinates
OK: gps_coordinates_north_direction
OK: gps_speed
OK: gyro
OK: inertial_unit
OK: joint_end_point_collision_obstacle
OK: joint_end_point_collision_sensor
OK: led
OK: lidar_point_cloud
OK: lidar_rotating
OK: lidar_vs_range_finder
OK: light_sensor_point_spot_light_no_occlusion
OK: motion_loop
OK: motion_regular
OK: motion_reverse
OK: motor
OK: motor2
OK: pen
OK: pen_box
OK: pen_box_scaled
OK: pen_capsule
OK: pen_capsule_scaled
OK: pen_cone
OK: pen_cone_scaled
OK: pen_cylinder
OK: pen_cylinder_scaled
OK: pen_elevation_grid
OK: pen_elevation_grid_scaled
OK: pen_indexed_face_set
OK: pen_indexed_face_set_scaled
OK: pen_plane
OK: pen_sphere
OK: pen_sphere_scaled
OK: radar_frustum
OK: radar_occlusion
OK: radar_relative_speed
OK: radar_target_merging
OK: range_finder
OK: range_finder_horizontal_spherical_projection
OK: range_finder_spherical
OK: range_finder_spherical_horizontal_vertical
OK: remote_control
OK: robot_data_supervisor
OK: robot_multiple_step
OK: robot_nested_three_levels
OK: robot_nested_direct_child
OK: robot_nested_group_child
OK: robot_nested_joint_endpoint
OK: robot_nested_slot_endpoint
OK: robot_nested_parent
OK: supervisor_node
OK: robot_synchronous_time
OK: robot_time_consecutive_packets
OK: robot_wait_for_user_input_event
OK: robot_window
OK: robot_window_html
OK: runtime_config_file
FAILURE with speaker: wb_speaker_is_speaking should return true when TTS is running.
OK: supervisor_animation
OK: supervisor_export_image
OK: supervisor_field
FAILURE: Some tests have not been executed
- expected number of worlds: 122
- number of worlds actually tested: 90
)

### physics test

FAILURE with /home/travis/build/omichel/webots/tests/api/worlds/supervisor_field_determinism.wbt: Timeout the results file has not been written quickly enough
OK: supervisor_field_import_mf_node
OK: supervisor_get_def
OK: supervisor_get_from_def
OK: supervisor_get_position_orientation
OK: supervisor_get_velocity_with_joints
OK: supervisor_import_remove
OK: supervisor_import_remove_mf
OK: supervisor_import_robot_node
OK: supervisor_inertia
OK: check_saved_hidden_parameter
OK: supervisor_internal_field
OK: supervisor_node
OK: collision_multiple_trimesh
OK: supervisor_node_set_visibility
OK: connector_detach
OK: damping
OK: supervisor_reset_physics
OK: supervisor_reset_physics_hinge
OK: supervisor_reset_simulation_iteration_0
OK: supervisor_reset_simulation_iteration_1
OK: supervisor_restart_controller
OK: supervisor_restart_controller_display
OK: supervisor_save_world
OK: supervisor_self_restart
OK: supervisor_set_hinge_position_dynamic
OK: supervisor_set_hinge_position_kinematic
OK: supervisor_set_position_loop
OK: supervisor_set_position_orientation
OK: supervisor_simulation_mode
FAILURE with /home/travis/build/omichel/webots/tests/api/worlds/supervisor_start_stop_movie.wbt: Timeout the results file has not been written quickly enough
FAILURE with supervisor_start_stop_movie: Movie shouldn't be ready just after stopping recording a video.
OK: supervisor_velocity
OK: touch_sensor_bumper
OK: touch_sensor_force
OK: touch_sensor_force3d
OK: touch_sensor_kinematic
OK: track_caterpillar
OK: track_invisible
OK: determinism
OK: dynamic_distance_sensor_rays
OK: dynamic_light_sensor_rays
OK: dynamic_radar_rays
OK: dynamic_receiver_rays
OK: elevation_grid_rotation
OK: floating_point_precision
OK: hinge_2_joint_damping
OK: hinge_joint_damping
OK: hinge_joint_slot
OK: check_joint_hard_limits_after_move
OK: kinematic_geometry_update
OK: move_vehicle_with_hinge_2_joint
OK: move_car
OK: move_hinge_2_joint_with_suspension
OK: runtime_geom_update

### protos test

OK: spring_damping_force
OK: static_distance_sensor_rays
OK: static_light_sensor_rays
OK: derived_proto_automatic_IS_redirection
OK: static_radar_rays
OK: derived_proto_nested_internal_1
OK: static_receiver_rays
OK: derived_proto_nested_internal_2
OK: derived_proto_nested_internal_3
OK: derived_proto_nested_internal_4
OK: derived_proto_parameter
OK: derived_proto_with_default_parameter
OK: proto_with_template_default_parameter
OK: follow_solid_in_slot
OK: internal_template_proto
OK: mixed_template_derived_proto
OK: nested_mixed_template_proto
OK: proto_direct_nested
OK: proto_nested
OK: proto_nested_fixed
OK: proto_nested_internal_1
OK: proto_nested_internal_2
OK: proto_nested_parameter
OK: proto_nested_parameter_2
OK: proto_regeneration_multiple_instances
OK: save_joint_proto_parameter
OK: single_distance_sensor_detection
OK: slots
OK: slot_node
OK: slot_node_derived
OK: slots_node_proto_parameter
OK: super_parameter_instances
OK: template_direct_nested
OK: template_exhaustive_parameter_type
OK: template_internal_proto_regeneration
OK: template_nested
OK: template_nested_slot_container
OK: template_node_id
OK: template_parameter_toggle_from_supervisor
OK: dummy
OK: template_proto_with_nested_template_parameter_1
OK: template_proto_with_nested_template_parameter_2
OK: template_proto_with_nested_template_parameter_3
OK: template_proto_with_template_parameter_1
OK: template_proto_with_template_parameter_2
OK: template_robot_regenerated
OK: template_static
OK: template_texture
OK: template_viewpoint_proto

### parser test

OK: derived_proto_using_same_parameter_name
OK: double_quote_in_lua_string_field
OK: empty_value
OK: hidden_parameter_single
OK: hinge_2_joint_axes
OK: invalid_template_regenerator_field
OK: lua_invalid_vrml_comment
OK: lua_length_operator
OK: mismatch_field_type
OK: missing_closing_curly_bracket
OK: missing_closing_square_bracket
OK: missing_def_value
OK: missing_item_in_value
OK: missing_use_value
OK: nested_def_name
OK: nested_proto_missing_ending_curly_bracket
OK: node_without_brackets
OK: proto_concatenated_comment
OK: proto_mismatch_field_type
OK: proto_mismatch_file_name
OK: proto_missing_ending_curly_bracket
OK: proto_missing_item_value_in_field
OK: proto_nested_parameter
OK: proto_not_allowed_field_value
OK: proto_not_allowed_mf_field_value
OK: proto_parameter_missing_ending_curly_bracket
OK: proto_typo_in_alias
OK: proto_typo_in_is_keyword
OK: proto_unknown_field_header
OK: proto_unknown_field_type
OK: proto_unknown_parameter
OK: recursive_proto
OK: supplementary_curly_bracket
OK: supplementary_item_in_value
OK: supplementary_square_bracket
OK: template_context_print
OK: unknown_field
OK: unknown_node
OK: unused_proto_parameter
OK: unusual_white_spaces
OK: valid_proto_comments

### rendering test

FAILURE with mirror_supervisor: The white color of the mirror image in the 3D scene is wrong.
OK: point_set
OK: smooth_shading_camera

Test suite complete

Remains only two problematic tests:
FAILURE with speaker: wb_speaker_is_speaking should return true when TTS is running.
FAILURE with display_attach_camera: Wrong display attaching the camera (green shape not detected)

I have been able to reproduce both locally using Webots in a docker container.
For info here is a dockerfile to create a docker image with a very similar setup than the one we are using on travis and able to compile and run Webots (you can also use the ubuntu:16.04 docker image and execute the command from within this docker):
# Use an official Python runtime as a parent image
FROM ubuntu:16.04

# Set the working directory to /app
WORKDIR /app

# Copy the current directory contents into the container at /app
COPY . /app

# Install any needed packages specified in requirements.txt
#RUN pip install --trusted-host pypi.python.org -r requirements.txt
# Install Webots dependencies
RUN apt update && apt install -y openjdk-8-jdk git g++ cmake libusb-dev swig python2.7-dev libglu1-mesa-dev libglib2.0-dev libfreeimage-dev libfreetype6-dev libxml2-dev libzzip-0-13 libssl-dev libboost-dev libjpeg8-dev libavcodec-extra libpci-dev libgd-dev libtiff5-dev libssh-dev libzip-dev python-pip libreadline-dev libassimp-dev libpng12-dev libav-tools python3.5-dev
# Install additional package not available in the server edition of Ubuntu
RUN apt update && apt install -y xvfb lsb-release wget unzip zip libnss3 libnspr4 libxcomposite1 libxcursor1 libxi6 libxrender1 libxss1 libasound2 libdbus-1-3 xserver-xorg-video-dummy xpra xorg-dev libgl1-mesa-dev mesa-utils libgl1-mesa-glx xvfb
# Start xvfb
RUN Xvfb :99 -screen 0 1024x768x16 &

# Make port 80 available to the world outside this container
#EXPOSE 80

# Define environment variable
ENV JAVA_HOME /usr/lib/jvm/java-8-openjdk-amd64
ENV AUDIODEV null
ENV DEBIAN_FRONTEND noninteractive
ENV DISPLAY :99
ENV LIBGL_ALWAYS_SOFTWARE true
ENV WEBOTS_HOME /app

The failure of the camera is due to a totaly different rendering when a camera is attached to a display in a Docker environment.
Native:

Docker:

It seems impossible to initialize a dummy sound driver in travis, I have tried multiple possibilities but none of them work, it seems we don't have enough permission to do this:

I'm sorry but we are not able to change permissions for our virtualization system as it would pose security issues.
Closing this for the time being.
https://github.com/travis-ci/travis-ci/issues/1754#issuecomment-42171127

I propose to skip this test for know.

The three first stages of #534 are implemented and we can now get ride of jenkins!

👍

👀

👍

:eyes:

authors: DavidMansolino omichel


text:
[2.7.0] Adds release notes and update references to 2.6.0

Adds release notes
Update references to 2.6.0

Please review if the content is correct and the references are correct.

Need to think of a better way to handle the 2.7.0 branch falling behind the main

repo: ondat/documentation


text:
Launching executable in Windows 10

Hello,
I'm having trouble launching the executable in Windows 10 (x64). I double click the executable and nothing happens other than the Windows loading icon next to the cursor. This even prevents me from deleting the .exe file and only a complete shutdown/restart allows me to do so.

Right, the executable is meant to be used as a command like tool.
When you double click it, it causes it to run indefinitely because it lacks proper context.
You can end the processes through the Task Manager just look for ruby.exe.
I suggest you take a look at Bosko Ivanisevic's excellent guide at rubyonwindowsguides.github.io
It's pretty involved, but the first chapters give you a bit of a primer on the command line.

Thank you for your reply. There's no process in Task manager called ruby.exe, the installer doesn't run and just causes Windows Explorer to not respond.
I've had a look at Bosko Ivanisevic's guide and it works perfectly for older versions of the installation such as Ruby 2.0.0-p645, but it's the Ruby 2.2.2 (x64) version which is causing the issue.

OH, sorry. You mean the executable installer?
Before I open this back up can you give me some more information?
The exact name of the executable, the your systems chip architecture(32-bit or 64-bit), the anti-virus software you're using (if you're using; Windows Defender counts for this), and the definition version of your anti-virus(if you can find it).

No problem :-) yeah the executable installer, apologies for not being more clear.
Installer version: Ruby 2.2.2 (x64)
Operating System: Windows 10 Home (x64)
Chipset/Processor: Intel Core i7 4790k (x64)
Anti-virus: Windows Defender
Anti-virus Version: 1.203.2099.0
Please let me know if you need any more information from me.

Ok, so I can't reproduce it, and your definitions appear to be up-to-date.
At first glance it appeared to be similar to #273, but that's doesn't appear to be the case.
Hmmm, lemme think about it.

Hmm that does sound like a pretty similar case. I'm going to try and disable a few services and processes in Windows 10, maybe start in safe mode too and let you know if there's any luck and if a particular service/process was causing it.

Okay so I booted in to safe mode and attempted to launch the installer. I received a notification from Windows SmartScreen telling me it wasn't available, so I ignored, clicked run anyway and it worked.
I normal booted Windows and disabled Windows SmartScreen and it worked again! so there's something up with SmartScreeen :/

Gonna try and see if @jasonconradt could point us in the right direction; if he gets some time that is. No Rush.

Thank you, Azolo. I can use Ruby and SASS on Mac OS for now, so will look out for updates to this ticket.

@christiangibbs You can always download the 7z version and manually add the location to the PATH. That should work perfectly.

Oh thanks, I'll look in to doing that then :-)

I had the same issue; double clicking the installer, led to a ruby process, but nothing else happening.  Running from the command prompt fixed it up.

Hey guys sorry for the delay. We've been dealing with this one-by-one via signatures based on each escalation and now have a more systemic/holistic fix that should avoid this in most cases going forward for the Inno installer. The issue you were seeing is that we were virtualizing the entire installation sequence and tearing each file apart in a fairly inefficient manner.
We shipped the fix last night in our engine August release, Windows Update should take care of this automatically, or you can open the Windows Defender UI, click on the "Update" tab, and manually update.  To verify you have the update, open the UI, click on Help -> About and you'll see something like this:
Antimalware Client Version: 4.8.10240.16384
Engine Version: 1.1.12002.0
Antivirus definition: 1.205.102.0
Antispyware definition: 1.205.102.0
Network Inspection System Engine Version: 2.1.11804.0
Network Inspection System Definition Version: 115.10.0.0
Engine Version 1.1.12002.0 is what you're looking for in terms of the one that contains the fix. It goes out to all of our antimalware products (Windows Defender, FEP 2010, SCEP 2012, Microsoft Security Essentials) so they'll all get taken care of with this change.
Please advise if there are any further issues and again apologies for the lack of communication.
Regards,
Jason

@christiangibbs  @Martlark  Guys please try with the updated engine per the notes above and let me know if you have any issues.

sir, same problem here! o/

@leandroruel @Martlark @christiangibbs Hey Guys! Can you give @jasonconradt some feedback on if his suggested fix works?
I don't know why, but I don't seem to be having the same problem. =/

yes i do what @jasonconradt said. but not work, and after almost one hour, the Ruby installer launch, very weird

I managed to get it working after disabling Microsoft SmartScreen, it also seems to be working after Jason's fix to Windows Defender too. Thanks for the help and feedback!

Disabling SmartScreen shouldn't have any impact on the scenario I described above, in which double-clicking on the installer seems to have no apparent affect (no UI), but then 5-20 mins later (depending on machine hardware), you'll see the install UI.
@leandroruel  @christiangibbs I can investigate whether Defender is involved in this but need some data.
From an elevated cmd prompt:
cd c:\Program Files\Windows Defender or C:\Program Files\Microsoft Security Essentials
mpcmdrun.exe -getfiles -all
That will create a file named MPSupportFiles.cab in \ProgramData\Microsoft\Windows Defender or \ProgramData\Microsoft\Microsoft Security Essentials
If it's under 20m, just email me at j a s o n c o n @ m I c r o s o f t. c o m (remove the spaces)
Just a note - there IS potentially sensitive information in these support cabs including machine name, locale, IP address, some registry and machine config settings for example. If you'd rather not share, no worries but it really limits my ability to help understand what's happening. The data will only come to me and reside on my PC (other than being on our email server for a brief period of time), I'll use it troubleshoot, and potentially share this info with others on my team if necessary, then delete it once we're done.

edited:  cd 'c:\Program Files\Windows Defender\mpcmdrun.exe' -getfiles -all
i put some '' to the spaces between the path string.
but when i run this command i get this:
Set-Location : A parameter cannot be found that matches parameter name 'getfiles'.
On line:1 character:53

cd 'c:\Program Files\Windows Defender\mpcmdrun.exe' -getfiles -all

                                                ~~~~~~~~~

CategoryInfo          : InvalidArgument: (:) [Set-Location], ParameterBindingException
FullyQualifiedErrorId : NamedParameterNotFound,Microsoft.PowerShell.Commands.SetLocationCommand

@jasonconradt If I haven't said it before, you're awesome. Thanks for working through this for us.
I'm going to leave this open until October, just in case someone else has this problem. But since the release of Ruby 2.2.3 on Sept. 4, there have been about ~80k downloads and no more issues reported. So everything looks good.

Thanks Justin. As an FYI, we’ve made more optimizations for handling the Inno installer beginning with engine September, which dropped on 9/16 (engine version 1.1.12101.0).
Please send me a flare if there any further issues.
Jason
From: Justin Baker [mailto:notifications@github.com]
Sent: Monday, September 21, 2015 7:52 PM
To: oneclick/rubyinstaller rubyinstaller@noreply.github.com
Cc: Jason Conradt Jason.Conradt@microsoft.com
Subject: Re: [rubyinstaller] Launching executable in Windows 10 (#282)
@jasonconradthttps://github.com/jasonconradt If I haven't said it before, you're awesome. Thanks for working through this for us.
I'm going to leave this open until October, just in case someone else has this problem. But since the release of Ruby 2.2.3 on Sept. 4, there have been about ~80k downloads and no more issues reported. So everything looks good.
—
Reply to this email directly or view it on GitHubhttps://github.com/oneclick/rubyinstaller/issues/282#issuecomment-142166546.

authors: Azolo Martlark christiangibbs jasonconradt leandroruel

repo: oneclick/rubyinstaller


text:
Sunsetting Amazon Web Services connected with RubyInstaller

Hello folks,
Been providing S3 and CloudFront setup for RubyInstaller since November 2008.
Originally this was the source of the downloads provided by the website, and also served the JS/CSS of the initial website build.
I've been paying these expenses without issues, but now that I've been away of the project for more than 3 years, I think is time to sunset those expenses.
While not prohibited expensive, these have been draining resources on my end, which I no longer want to maintain.
If not mistaken, I believe all releases are now located in both Bintray and GitHub, which are also backed by Amazon S3, so most of the resources available there are duplicated or no longer relevant.
I'm sending this message as FYI and possible to gather some feedback before I continue with the removal. The following are the steps and deadlines I've in mind:

Today (September 3, 2018) - Backup (locally) the entire S3 buckets (distfiles.openknapsack.org, packages.openknapsack.org, rubyinstaller)
Friday (September 7, 2018) - Remove cdn.rubyinstaller.org CloudFront setup.
Monday (September 10, 2018) - Remove S3 bucket contents.

Please confirm if you have any objection with this timetable or other recommendation.
Cheers.
/cc @larsch @Azolo

Looks good to me. Thanks for doing it all of these years. 💚

@luislavena - Thank you for service well done

Hello folks,
Wanted to update and close this issue:

S3 buckets were archived (in case someone needs them).
S3 buckets were removed.
CloudFront distribution was removed.

Closing this issue now.
Cheers.

@luislavena Fortunately there are services in the meantime, which are free to use for OSS. But thank you Luis for spending these expenses for years!

authors: Azolo dmajkic larskanis luislavena


text:
RadioButton TabbleViewCell

Hello, Im trying to use your radio-button api into one of my project with tableview, data is loaded from the web server which is done. The problem is when i select any option after scroll its reset to its default value, i almost stuck in it from a week please help me out here. below is my code.

if ([module isEqualToString:@"RADIO"]) {
    static NSString *CellIdentifier = @"radiocell";

    UITableViewCell *cell = [tableView dequeueReusableCellWithIdentifier:CellIdentifier forIndexPath:indexPath];
    cell.selectionStyle = UITableViewCellSelectionStyleDefault;
    cell.backgroundColor = [UIColor clearColor];
    cell.backgroundView = nil;

    NSMutableArray* buttons = [[NSMutableArray alloc] init];
    CGRect btnRect = CGRectMake(25, 5, 300, 30);
    for (NSString* optionTitle in category) {

        RadioButton* btn = [[RadioButton alloc] initWithFrame:btnRect];
        [btn addTarget:self action:@selector(onRadioButtonValueChanged:) forControlEvents:UIControlEventValueChanged];
        btnRect.origin.y += 40;
        [btn setTag:indexPath.row];
        [btn setTitle:optionTitle forState:UIControlStateNormal];
        [btn setTitleColor:[UIColor whiteColor] forState:UIControlStateNormal];
        btn.titleLabel.font = [UIFont fontWithName:@"HelveticaNeue-Regular" size:15];
        [btn setImage:[UIImage imageNamed:@"unchecked.png"] forState:UIControlStateNormal];
        [btn setImage:[UIImage imageNamed:@"checked.png"] forState:UIControlStateSelected];
        btn.contentHorizontalAlignment = UIControlContentHorizontalAlignmentLeft;
        btn.titleEdgeInsets = UIEdgeInsetsMake(0, 6, 0, 0);
        [cell.contentView addSubview:btn];
        [buttons addObject:btn];
    }
    [buttons[0] setGroupButtons:buttons];
    [buttons[0] isButtonSelected:YES];

    return cell;

Its not a right place for such questions. Use stackoverflow.

authors: haidershahzad onegray

repo: onegray/RadioButton-ios

license: mit

license_source: bigquery


text:
no more silent failure fetching idp metadata

This is an attempt to avoid silent failure when fetching idp metadata. Currently the only way I am able to detect a failure is to reach into parser.document from outside and see if it's empty. With this PR, we get exceptions in two new cases:

When the URL has no scheme and we don't even attempt to fetch metadata, and
When the HTTP response is not an instance of Net::HTTPSuccess

:+1: :shipit:

@bonyiii , @phene since you are using that feature on production, are you agree with this change?
Is it ok to raise an exception when the fetch fail?
I'm scared of those integration that are using this functionality and does not expect an Exception.
Maybe add a soft parameter and raise or not based on that. Default value will be not raise to keep compatibility issues. What do you think @stevecrozz and @tony-spataro-rs?

I think it should be fine to make changes as long as they're published in a new version and documented. But I would understand if you don't agree and I'm happy to make this new case a non-default.

My team uses another means for downloading the metadata and only provides RubySaml with the content when it's present, so this change should have no effect on us.

I'm ok with this change.

This seems like a valuable change in the long run; although I can understand the desire not to break compatibility, we should make things work correctly before the gem reaches v1.0. Two options:
-- If the user population are ok with the change, we should make it now (and add something to release notes). It's a change that only affects corner cases (metadata URL is invalid) that presumably would not result in successful SAML.
-- If someone has concerns, we could instrument the code so that the exception is raised if the gem version is >= 1.0
It sounds to me like option #1 is better; for my use case, an exception is better than silent failure.

This change alters the behavior of this method, would be wise to at least add Yard documentation to the parse_remote method

@Lordnibbler I amended my commit, adding a new @raise to the yardoc for parse_remote and made an improvement there also. Since the YARDoc is identical for both parse_remote and get_idp_metadata, I was able to use "see" to reference one method's yardoc from the other method, and I verified that this generates the correct docs when running yard.

@stevecrozz isn't see used like @see?
http://www.rubydoc.info/gems/yard/file/docs/Tags.md#see

@Lordnibbler That's what I thought at first, but @see just adds a link in the docs to the other method whereas @params (see ...) inlines the documatation as if you had written in here instead of "over there". I found it here and it does seem to work if we want the same docs in both places.
https://gist.github.com/chetan/1827484#methods
I can change it if you just want to "reference" the other docs though.

ah thats nice! :+1:

authors: Lordnibbler bonyiii phene pitbulk stevecrozz tony-spataro-rs

repo: onelogin/ruby-saml


text:
Copy to Clipboard

Despite having xclip installed, the copy to clipboard feature did not work for me.  It worked as expected using the "Better Version" at https://github.com/sumnerevans/menu-calc  Thanks, this is great!

Line 45, change xclip to xclip -selection clipboard

repo: onespaceman/menu-calc


text:
deinit crash for iOS

hi 猫神
我在 deinit 时手动 调用stopAnimating(),  偶现 crash , 概率比较高,  控制台可以明显的看到释放代码执行了,  我将 APNGImageView 用于 CollocationView 中
释放的代码:
deinit {
stopAPNG()
}
func stopAPNG() {
if let arFilterAPNGView = arFilterAPNGView {
GCDUtils.main({
print("(Thread.current) ---------------- arFilterAPNGView")
arFilterAPNGView.stopAnimating()
self.arFilterAPNGView = nil
})
}
}
crash时 控制台的 堆栈

thread #21, queue = 'gcdTimerQueue'
frame #0: 0x00000001817958e8 libsystem_kernel.dylib__ulock_wait + 8   frame #1: 0x0000000104997300 libdispatch.dylib_dispatch_ulock_wait + 48
frame #2: 0x0000000104997428 libdispatch.dylib_dispatch_thread_event_wait_slow + 36   frame #3: 0x000000010497e230 libdispatch.dylib_dispatch_barrier_sync_f_slow + 240
frame #4: 0x0000000103f797ac APNGKitAPNGImageView.(startAnimating() -> ()).(closure #1) [inlined] function signature specialization <Arg[0] = Owned To Guaranteed> of APNGKit.APNGImageView.(startAnimating () -> ()).(closure #1) at APNGImageView.swift:185 [opt]   frame #5: 0x0000000103f79704 APNGKitAPNGImageView.(startAnimating() -> ()).(closure #1) at APNGImageView.swift:184 [opt]
frame #6: 0x0000000103f7f140 APNGKit`GCDTimer.(Event.setter).(closure #1) [inlined] function signature specialization <Arg[0] = Owned To Guaranteed> of APNGKit.GCDTimer.(self=) -> ()).(closure #1) at GCDTimer.swift:66 [opt]

frame #7: 0x0000000103f7f114 APNGKitGCDTimer.(Event.setter).(closure #1) at GCDTimer.swift:65 [opt] frame #8: 0x000000010496da10 libdispatch.dylib_dispatch_client_callout + 16
frame #9: 0x0000000104979a84 libdispatch.dylib_dispatch_continuation_pop + 552 frame #10: 0x00000001049881f8 libdispatch.dylib_dispatch_source_latch_and_call + 204
frame #11: 0x000000010496fa60 libdispatch.dylib_dispatch_source_invoke + 828 frame #12: 0x000000010497b128 libdispatch.dylib_dispatch_queue_serial_drain + 692
frame #13: 0x0000000104971634 libdispatch.dylib_dispatch_queue_invoke + 852 frame #14: 0x000000010497d630 libdispatch.dylib_dispatch_root_queue_drain + 552
frame #15: 0x000000010497d39c libdispatch.dylib_dispatch_worker_thread3 + 140 frame #16: 0x000000018185b100 libsystem_pthread.dylib_pthread_wqthread + 1096
frame #17: 0x000000018185acac libsystem_pthread.dylib`start_wqthread + 4

Not sure what happened. Could you try this branch or  to see whether it could solve it?
BTW, there should be no need to call stopAnimating or set nil if you could ensure that the container could be deinited correctly. Similar as other regular views, the APNGView could dealloc itself when there is no strong reference on it.

push 后 pop有一定概率Crash,找了好几天，问题不好定位，暂时放弃使用了。

APNGKit v2 was released and this should not happen anymore.
I am closing it for now.

authors: hrstruggle1 iFallen onevcat

repo: onevcat/APNGKit


text:
Swift 5 upgrade

Using Xcode 11 GM with Swift 5 tells me to convert APNGKit to support Swift 5.
I can see only one line of code needs to be changed, will we see an update for that?
Thanks!

Hey,
Maybe soon!

do it now you lazy bum

APNGKit supports Swift 5 from v1.2 and now APNGKit v2 was also released with full support for the latest tech. I am closing this.

authors: eitanaviv michaelamici onevcat


text:
Crash in iOS8 simulator

Check List
I have read the wiki page and cheat sheet, but there is no information I need.
I have searched in existing issues, but did not find a same one.
I want to report a problem instead of asking a question. It'd better to use kingfisher tag in Stack Overflow to ask a question.
Issue Description
Using Kingfisher 4.6.0, we received a crash inside KingFisher When I run OC project in iOS8 simulator with Xcode 9.2.

Not sure what happens. Could you always reproduce it in iOS 8 Simulators?

authors: onevcat yywDavidYang

repo: onevcat/Kingfisher


text:
Move appear life cycle to placeholder

And also ensure image setting on main thread

This is a workaround for #1508. But a real fix is still being waited from Apple.

Please revert this change as it causes flickering every time swiftUI re-renders - see details at https://github.com/onevcat/Kingfisher/issues/1549

@onevcat ^

@hyouuu This fix was intended as a workaround of Apple's bug on iOS 14. However, the flickering seems to be a side effect. I will see how we can solve it.

@onevcat yes the intention is well understood and appreciated - it's just the side effect is too much :) Hope you can find a more appropriate fix soon and thanks!

authors: hyouuu onevcat


text:
Fix "Edit NeoVim config" command.

Looks like I broke the init.vim edit command when I updated the getUserHome() command for Windows.
I've updated it to use the environment variable instead now.

Thanks for catching this, @CrossR!

authors: CrossR bryphe

repo: onivim/oni


text:
Powershell inside :term freezes on start

This might not a deal-breaker for me, since I use WSL inside a separate terminal, but calling :term on windows causes onivim to open powershell by default (apparently) but the shell seems frozen, it doesn't recognize any input, so you can't even exit it without closing the term window completely.

I have tried :term wsl.exe, it opens the correct shell, but it seems frozen. Can't do anything inside.

I have tried :term wsl.exe, it opens the correct shell, but it seems frozen. Can't do anything inside.

Thanks for opening this! I was thinking this might be related to #3040 - at least, when I tested with Avast, the first time I opened the terminal, it required scanning the winpty-agent.exe. Are there still issues after re-launching Onivim after the scan, @iilonmasc ?
For other users running into this - would it be possible to provide a log file? (Control+Shift+P -> Debug: Log to trace file) and then opening the terminal. Might give some clues...
One instance I've seen this occur is building from source - if the node dependencies aren't installed (node install-node-deps.js), the terminal won't open.

Thanks for opening this! I was thinking this might be related to #3040 - at least, when I tested with Avast, the first time I opened the terminal, it required scanning the winpty-agent.exe. Are there still issues after re-launching Onivim after the scan, @iilonmasc ?
For other users running into this - would it be possible to provide a log file? (Control+Shift+P -> Debug: Log to trace file) and then opening the terminal. Might give some clues...
One instance I've seen this occur is building from source - if the node dependencies aren't installed (node install-node-deps.js), the terminal won't open.

@bryphe it did require a scan yes, but as mentioned in #3040 after the first scan and relaunch the AV seems to be fine with onivim.
I tried again to be on the safe side, but the terminal still freezes.

@bryphe it did require a scan yes, but as mentioned in #3040 after the first scan and relaunch the AV seems to be fine with onivim.
I tried again to be on the safe side, but the terminal still freezes.

I created a debug log right after opening onivim, pastebin didn't want me to upload it there because it was too large so I created a gist. https://gist.github.com/iilonmasc/fe9df44b187b161a27ee3caa570699f1
Steps I took during the debug trace:

Start the terminal via :term
Switch to the terminal
try to type asd inside the terminal
Closing onivim

I created a debug log right after opening onivim, pastebin didn't want me to upload it there because it was too large so I created a gist. https://gist.github.com/iilonmasc/fe9df44b187b161a27ee3caa570699f1
Steps I took during the debug trace:

Start the terminal via :term
Switch to the terminal
try to type asd inside the terminal
Closing onivim

Thanks for the logging the issue and all the details, @iilonmasc - this should be fixed now in latest nightlies w/ #3117

authors: bryphe iilonmasc mabasic


text:
Performance: Async Syntax Highlighting

This is a follow-up to #866 - the issue being that, even though our textmate syntax highlighting (reason-textmate is faster than the JS syntax highlighting strategy when run in isolation: https://github.com/onivim/reason-textmate#performance ) - it's actually slower in wall-clock time when run in the editor.
The problem is that we are 'time-slicing' our syntax highlighting - giving it a budget of 2ms per frame. This means we are running it at 1/8 the potential speed (assuming a frame time of 16ms) - essentially 8x slower.
#866 was an attempt to move this to an OCaml thread to run in parallel, but unfortunately this is where the lack of multicore is problematic - most the of operations are CPU bound (the processing of the regex), so it causes delays in the rendering / responsiveness. When multicore is in place - threading will be a viable option, and we can revisit!
However, without OCaml multicore, we have to go back to running the syntax highlighting in a separate process - this will allow us to still get parallelism. The implementation can be simpler and more performant than our previous node-textmate strategy, which used JSON-RPC, because we can use OCaml's efficient Marshal module as the bridge, and we can strongly-type both ends of the protocol in Reason, and leverage the native reason-textmate parsing (and reason-tree-sitter.
TODO:

[x] Send language info to client
[x] Send theme to client
[x] Create type for managing the state in Oni_Syntax_Server

[x] Track buffers / buffer updates in state
[x] Move SyntaxHighlighting.t there

[x] Update theme when it changes
[x] Run syntax highlight job continuously in Oni_Syntax_Server
[x] Create simpler client-side state for managing syntax highlighting - just the tokens
[x] Wire up 'textmate' strategy again

[x] Hook up grammar discovery
[x] Add getUpdatedLines to job / interface
[x] Add clearUpdatedLines to job / interface

[x] Wire up 'treesitter' strategy again

[x] Add TreeSitterConverter repository (like GrammarRepository but for tree-sitter)
[x] Hook up tree-sitter json discovery
[x] Add getUpdatedLines to job / interface
[x] Add clearUpdatedLines to job / interface

[x] Hook up configuration / configuration changes (to decide if we need to pick up tree-sitter)
[x] Hook up logic to determine which highlight strategy to use
[x] Add rei interfaces + review and consolidate
[x] Implement 'shift' logic when adding / removing lines
~Debug issue where new characters are not highlighted with previous token~ (this was an pre-existing issue, will test further to explore a fix in separate PR)
[x] Add integration test for syntax highlighting

[x] Windows: Fix crash when spinning up syntax server

~Turn on 'C' tree-sitter?~ (will defer to a separate change)
[x] Keep track of ranges that were updated, send those up, and clear them

[x] Store updated ranges as part of job
[x] Add 'getPendingRanges'
[x] Call 'clearPendingRanges'

[x] Add health check for syntax server
[x] Test release builds

[x] OSX
[x] Windows
[x] Linux

... later - keyword extraction would be nice to have!

/azp run


text:
Added input/button features to toolbar

Description

What is the purpose of this pull request?
I have added the button / user input features to the toolbar.

[X] New feature
[ ] Documentation update
[ ] Bug fix
[ ] Refactor
[ ] Release
[ ] Other

Closing for inactivity

repo: onlook-dev/onlook


text:
support rounding and saturation implementations of Cast

It can be useful to allow implementations

to round when casting from floating point to integer types and
to saturate when casting between different integer types.

One reason is that this is preferable for numerics (see onnx issue #5004). Another reason is that this is the most direct implementation on some hardware.
Proposal: Add flags or other configuration options in onnx-mlir to select (1) rounding and (2) saturation and make rewrites like constant propagation and Cast canonicalization (FuseCastCastPattern) respect the selections. Lowerings can warn or error out if they don’t match the selections.
The current lowering to Krnl uses MathBuilder::cast() which truncates when converting between integer types.
The current lowering to Mhlo uses mhlo::ConvertOp which may either truncate or saturate (see spec).
The onnx Cast spec doesn’t say whether cast from floating point to integer type should truncate or round but past discussions (onnx issues #2285 and #3776) pointed to truncation like numpy. The spec says that cast between integer types (except bool) should truncate. There’s ongoing discussion about both in onnx issue #5004.

@sorenlassen did #2210 resolve this Issue or is there more to do?

it's not solved yet, I hope to get to it at some point, let's keep it open

authors: cjvolzka sorenlassen

repo: onnx/onnx-mlir


text:
Update docker instructions and Dockerfile

Signed-off-by: Kevin O'Brien caomhin@us.ibm.com

PR #710 implemented the changes originally proposed here

authors: AlexandreEichenberger caoimhinuibrian


text:
Please, update to newer cargo, dependencies no longer build

The cargo version used depends on libgit2-sys v0.4.6, which no longer builds on Debian Testing. Since newer versions build just fine, the easiest fix would be to update to newer cargo.
The errors are:
libgit2-sys-0.4.6/libgit2/src/openssl_stream.c:146:3: error: dereferencing pointer to incomplete type ‘BIO {aka struct bio_st}’
libgit2-sys-0.4.6/libgit2/src/openssl_stream.c:204:1: error: variable ‘git_stream_bio_method’ has initializer but incomplete type

Thanks for reporting. I am using Debian Sid and it is building fine.
But I'll definitely update this crate.

Works ok.

authors: jan-hudec onur

repo: onur/cargo-license


text:
OverView

OverView

Checked

repo: oocakoglu/FlutterChallengeApp


text:
Play example throws KeyError: 'encoded'

Summary
trying to play a song results in a key error using the simple example
Reproduction Steps
Set up the basic example (in a cog) and use e.g. /play query: Wolke 10 HBz
Minimal Reproducible Code
# DragonBot.py
class DragonBot(commands.Bot):
    def __init__(self, *args, **kwargs):
        super().__init__(*args, **kwargs)
        self.first_start = True
        self.pool = mafic.NodePool(self)

    async def on_ready(self) -> None:
        if self.first_start:
            log.info(
                f"Bot started as {self.user.name}#{self.user.discriminator} | {self.user.id}"
            )
            await db.set_up()
            log.debug("Database setup successful")
            await self.pool.create_node(
                host = "localhost", port = 2333, password = "youshallnotpass", label = "Main"
            )
            self.first_start = False

# MusicPlayer.py
from DragonBot import DragonBot
from discord.abc import Connectable
from mafic import Player, Track

class DragonPlayer(Player[DragonBot]):
    def __init__(self, client: DragonBot, channel: Connectable) -> None:
        super().__init__(client, channel)

        # Mafic does not provide a queue system right now, low priority.
        self.queue: list[Track] = []

# m_play.py
class MaficMusicEventsCog(commands.Cog):
    def __init__(self, client):
        self.client = client

    @commands.slash_command(name = "join", description = "join's your voice")
    async def join(self, inter: discord.ApplicationContext):
        """Join your voice channel."""

        assert isinstance(inter.user, discord.Member)

        if not inter.user.voice or not inter.user.voice.channel:
            return await inter.response.send_message("You are not in a voice channel.")

        channel = inter.user.voice.channel

        # This apparently **must** only be `Client`.
        await channel.connect(cls = DragonPlayer)  # pyright: ignore[reportGeneralTypeIssues]
        await inter.send(f"Joined {channel.mention}.")

    @commands.slash_command(name = "play", description = "Play a song of your desire")
    async def play(self, inter: discord.ApplicationContext, query: str):
        """Play a song.
        query:
            The song to search or play.
        """

        assert inter.guild is not None

        if not inter.guild.voice_client:
            await self.join(inter)

        player: DragonPlayer = (
            inter.guild.voice_client
        )  # pyright: ignore[reportGeneralTypeIssues]

        tracks = await player.fetch_tracks(query)

        if not tracks:
            return await inter.send("No tracks found.")

        if isinstance(tracks, mafic.Playlist):
            tracks = tracks.tracks
            if len(tracks) > 1:
                player.queue.extend(tracks[1:])

        track = tracks[0]

        await player.play(track)

        await inter.send(f"Playing {track}")

def setup(client: DragonBot):
    client.add_cog(MaficMusicEventsCog(client))

Expected Results
The bot joins the voice channel and plays that song
Actual Results
The bot joined but didn't play any song
Ignoring exception in command play:
Traceback (most recent call last):
  File "E:\DragonBot\venv\Lib\site-packages\discord\commands\core.py", line 124, in wrapped
    ret = await coro(arg)
          ^^^^^^^^^^^^^^^
  File "E:\DragonBot\venv\Lib\site-packages\discord\commands\core.py", line 978, in _invoke
    await self.callback(self.cog, ctx, **kwargs)
  File "E:\DragonBot\extensions\mafic\m_play.py", line 45, in play
    tracks = await player.fetch_tracks(query)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "E:\DragonBot\venv\Lib\site-packages\mafic\player.py", line 457, in fetch_tracks
    return await node.fetch_tracks(query, search_type=raw_type)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "E:\DragonBot\venv\Lib\site-packages\mafic\node.py", line 902, in fetch_tracks
    return [Track.from_data_with_info(track) for track in data["tracks"]]
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "E:\DragonBot\venv\Lib\site-packages\mafic\node.py", line 902, in <listcomp>
    return [Track.from_data_with_info(track) for track in data["tracks"]]
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "E:\DragonBot\venv\Lib\site-packages\mafic\track.py", line 151, in from_data_with_info
    return cls.from_data(track=data["encoded"], info=data["info"])
                               ~~~~^^^^^^^^^^^
KeyError: 'encoded'

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "E:\DragonBot\venv\Lib\site-packages\discord\bot.py", line 1114, in invoke_application_command
    await ctx.command.invoke(ctx)
  File "E:\DragonBot\venv\Lib\site-packages\discord\commands\core.py", line 375, in invoke
    await injected(ctx)
  File "E:\DragonBot\venv\Lib\site-packages\discord\commands\core.py", line 132, in wrapped
    raise ApplicationCommandInvokeError(exc) from exc
discord.errors.ApplicationCommandInvokeError: Application Command raised an exception: KeyError: 'encoded'

Lavalink Information

Lavalink version 3.6.2

System Information

Python v3.11.1-final
mafic v1.1.0
aiohttp v3.8.3
py-cord v2.4.None-final
system info: Windows 10 10.0.22621   (actually win 11)

Checklist

[X] I have searched the open issues for duplicates.
[X] I have shown the entire traceback, if possible.

Additional Context
No response

See https://github.com/ooliver1/mafic/issues/39#issuecomment-1433353149


text:
Bootloop on iOS 15.x.y with Dopamine

Hello. I believe there is something in AltList which bootloops devices on Dopamine jailbreak. I released an update of my tweak which more or less only replaced AppList with AltList and this happened for some people. Not all though.
Example of bootloop'd devices:

iPhone 12 PLUS MAX iOS 15.3.1 (Dopamine 1.0.3)
(model unknown) iOS 15.1 (Dopamine 1.0.3)

I tried to remove AltList and replace it with eg. "LSApplicationWorkspace allApplications" and that worked.
I went a bit further and prepared a build which has only this code:
#import <AltList/LSApplicationProxy+AltList.h>
%ctor {
    NSArray<LSApplicationProxy*>* a = [[LSApplicationWorkspace defaultWorkspace] atl_allInstalledApplications];
}

This also bootloops the device. I mean it doesn't invoke safe mode like a normal crash.
I installed AltList as the README.md says (except I can't do the "include <AltList/AltList.h>" like another issue mentions).

That's not a bootloop, that more sounds like a respring loop.
Anyhow, your issue is likely that you did not make your tweak properly link against the AltList framework, therefore the method does not exist and the process crashes. Make sure you add in your Makefile under EXTRA_FRAMEWORKS.

Ah, yes a respring loop then. The library is linked properly.
A common thread among reporters was the tweak "whoozitpro" (caller ID tweak), although installing it myself did not cause the issue, and I think I got some messages that they had it and no respring loops occurred as well.
In the end, as I was not able to properly debug this, I removed AltList and included only the specific code I needed (name, check if hidden, and the tag-function). This stopped respring loops for the users who tested it.
I think the issue can be closed though, I am not sure I have more time to investigate this. But at least we can be aware that there might be something up.

I am not sure if this is relevant, but at one point I got a respring loop on my device. And I think it was when I had brought over the categories. But I had added "allApplications" instead of "atl_allApplications". So both my category, and the original LSApplicationWorkspace had the same method. Not sure if that's ok in Objective C or it caused that issue.

You need to use a different prefix in your project, do not use atl_allApplications, change the atl

Yeah I did change that, just didn't change it in the comment.


text:
main.go lines 13 to 16 masks panics by exiting without errors

Bug Description
opcap fails on audit.go line 59 with out of boundary message.
opcap just exits with no errors
Version and Command Invocation
opcap check
Steps to Reproduce:

just run opcap check

Expected Result
Run audits against operators
Actual Result
The program exits without errors and doesn't do it's job
Additional Context
No additional context

Bug on github. Duplicated issue.

repo: opdev/opcap


text:
[Feature] Configuration Document Optimization Suggestions - ChatQnA Setup and Deployment

Priority
P3-Medium
OS type
Ubuntu
Hardware type
GPU-Nvidia
Running nodes
Single Node
Description
Due to the limited performance of my local Intel processor, I tried to deploy ChatQnA using a 3090 graphics card. According to the documentation at https://github.com/opea-project/GenAIExamples/blob/main/ChatQnA/docker_compose/nvidia/gpu/README.md, everything went smoothly.
However, after completing the deployment, I found that the host's large language model was still using the CPU instead of the GPU. After some troubleshooting, I discovered that the CUDA version on Ubuntu was incompatible with the torch version inside TGI Docker, which caused the GPU not to load. I saw a great table in the documentation listing which Docker image versions should be used for different GPU series; this is very helpful. I also suggest providing recommendations for which CUDA versions should be installed on Ubuntu hosts so that users can complete their setup more smoothly and quickly transition to developing upper-level applications.

Overall, OPEA is fantastic.

thanks for reporting this issue. it's very good feedback. we should have a doc to list all deployment prerequisites before deploying such docker image.
we will add such content in the future release.

repo: opea-project/GenAIExamples


text:
Add an interactive map to the facility details page

Depends on #2075
Refer the the "Facility Profile" section of the Figma board
Icons can be exported from Figma by selecting them then using the Export panel at the right side of the page.
Disable scroll zoom on the map so that content below the map is easily accessible.

Client action needed: OAR requested to sign-off on #2075 first before commencing this issue.

Feedback on #2075 to be applied in this ticket:
Comments from the OAR team:

can we make the font for the OAR ID itself size 18 instead of 14
is it possible to pin the "Description" data point as the last data point and allow it to be the width of the 2 columns, instead of wrapping into the one column. E.g. see this facility's description (note that description only shows up for claimed facilities if the owner has entered a description)

authors: TaiWilkin jwalgran obrienad


text:
Implement the previous download format

Depends on the recommendation in #2388. If this is undoing the change is the best approach: restore the old download (1 row per facility, all contributor values concatenated into single cell)
Downloads should remain to restricted to a maximum of 10k results.
@mariel-oar This issue was split from #2388 for estimation purposes

@jwalgran , to make sure we are on the same page: we do not want the 10k facility download limit lifted - just reverting to the previous format. They are kind of related because we had instituted the 10k limit in response to download times being much slower with the new format, so wanted to be clear.

Thanks for clarifying that. I updated the issue description to not that the 10k restriction should remain in effect.

@mariel-oar I'm adding the client action needed label to this while the OS Hub team reviews the document linked in #2388 and decides whether or not to move forward with this.

Removed CAN as OS Hub approved this.

authors: jwalgran mariel-oar obrienad


text:
Should we track which archive rows came from?

We may want to keep track of what data came from which archive. For example, if a user wants to delete one of their archive uploads, or to reason about changes in time over separate uploads from the same user.
Archives are defined by the user they belong to + the date at which they were requested (proxied in the archive_at column in the account and profile tables, which is the date of the most recent tweet in the archive)
It's easy to know which archive upload accounts and profiles are from, they come from the account_id at archive_at time.
Following, Follower, and Tweet track the user_id although not the specific archive upload time. Which is fine because right now we're just deleting tweets and follower/following and reuploading them whenever a user uploads a new archive.
In the future we may want to keep snapshots of follower/following at different times, which would need us to keep track of what archive they came from.
We wouldn't necessarily want to keep snapshots of tweet collections at different times. If users delete tweets and they're not present in a subsequent archive upload, there's not much reason for us to keep the tweets that were uploaded before but are deleted now.
The only reason I can think of to track what archive tweets belong to is if we start scraping tweets in other ways (since I think archives only include all tweets from the user, none from others), and if we store them in the same table. I think if we started scraping we might want to keep them in a different table and make a view that joins scraped and archive tweets anyway.

my current answer is "don't bother, but good to document this thought process"

Changed my mind I think it's worth it for the convenience of tracking which archive uploads things came from. We already have an archive-upload table that just tracks what time it was uploaded and is referenced by account and profile, just need to add a column in tweets and followed/following relationships

repo: open-birdsite-db/open-birdsite-db


text:
15634 Expand Validating Webhook

https://github.com/open-cluster-management/backlog/issues/15634

/hold

/unhold


text:
[Update] Update max_out_len for datasets

Thanks for your contribution and we appreciate it a lot. The following instructions would make your pull request more healthy and more easily get feedback. If you do not understand some items, don't worry, just make the pull request and seek help from maintainers.
Motivation
Please describe the motivation of this PR and the goal you want to achieve through this PR.
Modification
Please briefly describe what modification is made in this PR.
BC-breaking (Optional)
Does the modification introduce changes that break the backward compatibility of the downstream repositories?
If so, please describe how it breaks the compatibility and how the downstream projects should modify their code to keep compatibility with this PR.
Use cases (Optional)
If this PR introduces a new feature, it is better to list some use cases here and update the documentation.
Checklist
Before PR:

[ ] Pre-commit or other linting tools are used to fix the potential lint issues.
[ ] Bug fixes are fully covered by unit tests, the case that causes the bug should be added in the unit tests.
[ ] The modification is covered by complete unit tests. If not, please add more unit test to ensure the correctness.
[ ] The documentation has been modified accordingly, like docstring or example tutorials.

After PR:

[ ] If the modification has potential influence on downstream or other related projects, this PR should be tested with those projects.
[ ] CLA has been signed and all committers have signed the CLA in this PR.

daily test passed

repo: open-compass/opencompass


text:
Value distribution: Metadata occupies a lot of space

Maybe we can toggle it closed? If I'm trying to explore multiple examples, I need to keep scrolling down each time I load a new example.

I tried again and it's not too bad. Can re-open as needed.

repo: open-contracting/pelican-frontend


text:
Update details_motor_preparation.md to prevent mistakes while preparing the motors

It is better to warn of this step before the step is shown to prevent mistakes.
Description
We assembled the motors of the first unit and mistakenly also shortened the wires of the Hip AA motors. We were following step by step and the guide warned us too late.
We think this should be warned before irreversible steps are taken.

Hi Pau,
thanks for your suggestion.
We remove the insulation of the motor phase wires for all the modules - so I think the information about the Hip AA exception shouldn't be in that section.
I moved it to the top of the Preparing the Motor Phase Wires Section.
Is this better?
Best. Felix

Yes, that would be better!
Thanks.

authors: fgrimminger nitrostormbcn


text:
feat: add TransactionContext

This PR

Adds backwards compatible, basic implementation of 'TransactionContext'

The functions that are important are
WithTranscationContext(ctx, EvaluationContext)
TransactionContext(ctx)

Related Issues
https://github.com/open-feature/go-sdk/issues/256
Notes
For next steps,

I see the API suggested in https://github.com/open-feature/go-sdk/issues/256 is to remove the local evalCtx which would make the API much cleaner in my opinion, but I am not sure what is the process for breaking changes
I am also not sure what the right behavior of merging should be from the API's perspective if they run WithTransactionContext multiple times. My guess is we should expect the user to handle this on their end, but would be interested in opinions on if WithTransactionContext should merge existing TransactionContexts

How to test
I updated the associated tests for merging order / evaluation. Please let me know if any other tests will be helpful!

Hey @kevinschoonover, could you please update the readme to include a section about this? Please follow the template found here. Thanks!

I am also not sure what the right behavior of merging should be from the API's perspective if they run WithTransactionContext multiple times. My guess is we should expect the user to handle this on their end, but would be interested in opinions on if WithTransactionContext should merge existing TransactionContexts

Yes, I agree. Currently, all implementations override existing transaction context, but adding another method that merges would be useful.

Hey @kevinschoonover, could you please update the readme to include a section about this? Please follow the template found here. Thanks!

Done!

I am also not sure what the right behavior of merging should be from the API's perspective if they run WithTransactionContext multiple times. My guess is we should expect the user to handle this on their end, but would be interested in opinions on if WithTransactionContext should merge existing TransactionContexts

Yes, I agree. Currently, all implementations override existing transaction context, but adding another method that merges would be useful.

Added a MergeTransactionContext function which should solve this case. Let me know if there is anything else I can update!

repo: open-feature/go-sdk


text:
ci: add adams85 from ConfigCat as component owner

This PR

Adds @adams85 (ConfigCat) to the component owner's list of the ConfigCat providers. The intention behind this is that we (ConfigCat) would like to mark the providers in this repo as the official OpenFeature JS providers for ConfigCat, and we would like to participate in their development and maintenance.

Notes
I noticed that the config-cat-web provider wasn't on the list, so I added it. Please let me know if there was a specific reason not to list it, and I'll remove it from this PR.

@adams85 great to hear that!
I opened a PR to add you to the org, this would make sense before we merge this.
Please have a look: https://github.com/open-feature/community/pull/390

repo: open-feature/js-sdk-contrib


text:
Added CloudFormation Tips

Added some tips to work with CloudFormation

Closing for now pending further review.

authors: QuinnyPig StanForever

repo: open-guides/og-aws


text:
Alerts on test cases does not work with "owner" filter

Affected module
backend
Describe the bug
setting an alert on a test case result, if a filter on "owner" is set the alert does not work
To Reproduce
Screenshots or steps to reproduce

Expected behavior
A clear and concise description of what you expected to happen.
Version:

OpenMetadata version: 1.1.5
OpenMetadata Ingestion package version:  openmetadata-ingestion[docker]==1.1.5]

Additional context
Add any other context about the problem here.

https://github.com/open-metadata/OpenMetadata/pull/14806 fixes this

repo: open-metadata/OpenMetadata


text:
Deployment: Which concrete permissions are necessary for Elasticsearch?

Is some content missing, wrong or not clear?
We have a managed Elasticsearch cluster where users only get access to specific indexes of the cluster via technical users. In order to configure the necessary permissions for OpenMetadata we would like to know, which one are necessary. This information is missing in the docs.
Describe the solution you'd like
A concrete list of permissions a user of an elasticsearch cluster should have to successfully deploy OpenMetadata.

ElasticSearch user needs to be able to create/delete/update indexes. We end up creating 30+ indexes

authors: harshach notniknot


text:
Not all tag filters are displayed

Steps to reproduce:

Added different tags to the entity (more than 10)
Verify if all the tags are available in the filter
In the below screenshot, User.Politics and User.SSN are not in the tags filter.

@darth-coder00 @Sachin-chaurasiya I can reproduce this and search is returning that tag in aggregations. It looks like we only take 10 tags? also make sure you are sorting the tags in the order of aggregation count and showing the top 10

@harshach I tried reproducing it, we have added 12 different tags to raw_product_catalog, but only 10 of them are visible in aggregations under Network tab. User.IPAddress and User.MedicalRecords are missing.
We can show all the tags if we can get it in aggregations.

Looks like if we add lot of tags we get a server side error


text:
Define schema for Policy

Definition
Policies are technical representations that convey actionable intent on data entities, for bots to consume in order to satisfy regulatory compliance requirements.
Use Case
Data entities can be tagged with predefined tags
A Policy typically defines 'action'(s) and a set of 'conditions' to match on data entities (or its fields).
Eg: Delete (Action) data from Table (Entity) which has columns with PII tags (Condition)
Once a policy is attached to a data entity, a relevant bot would be able to interpret the action and take necessary steps towards satisfying the requirement set by the policy.

Notes Document: https://docs.google.com/document/d/1svyYBpSNBq3XUhALNCOuS-WTYtHNE-NMnghwszDe2G8/edit?usp=sharing


text:
Simplify config classes using @Getter @Setter annotations

Describe your changes :

I worked on this to simplify config classes and make them compact

Type of change :

[ ] Bug fix
[x] Improvement
[ ] New feature
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation

Frontend Preview (Screenshots) :
For frontend related change, please link screenshots of your changes preview! Optional for backend related changes.

Checklist:

[x] I have read the CONTRIBUTING document.
[x] I have performed a self-review of my own.
[x] I have tagged my reviewers below.
[ ] I have commented on my code, particularly in hard-to-understand areas.
[x] My changes generate no new warnings.
[ ] I have added tests that prove my fix is effective or that my feature works.
[x] All new and existing tests passed.

Reviewers

Backend: @sureshms @harshach

Thought about using @Data - decided not to as it brings in a whole lot of other things besides getters and setters


text:
Schema Changes for DBT

Describe your changes :

Fix #4456

Type of change :

[x] Improvement

Checklist:

[x] I have read the CONTRIBUTING document.
[ ] I have commented on my code, particularly in hard-to-understand areas.
[ ] I have added tests that prove my fix is effective or that my feature works.
[x] All new and existing tests passed.

Reviewers

@open-metadata/ingestion

@pmbrull config will be used for getting dbt files from local or a file server where all the directly the path of the file will be provided.
In the case of s3 and gcs we are adding a option to enter the name of the files in dbtCatalogFileName and dbtManifestFileName and our code searches all their buckets for these two files

@OnkarVO7, thanks for clarifying. Got it. I'll open then an issue to improve it in 0.11 to not search all the buckets (this will not work with some more constrained security requirements).
We should allow a prefix to be passed there too and search from that key.
Approving this now for 0.10. Thanks!


text:
The difference between yours and the original version of SECOND

Hi, first of all, thanks for your sharing of this wonderful work.
I noticed that you have re-implemented some other detectors, like SECOND. And in this Issue, you have mentioned that there is no difference w.r.t the data augmentation. But what for other modules? I am a newbie in DL for PC detection, and would like to dive into one detector and try to reproduce it to get some deep insights.
BTW, I have found you did some comparisons in accuracy, but what about run-time, like FPS?
Best

The implementation of SECOND (v1.5) should be similar with the original repo. For the inference time, you could test it with the provided model on your own machine.

Thanks for your reply. And I will close this issue if nobody else has relevant question.

repo: open-mmlab/OpenPCDet