text:
Build Failed while using this package. Sometimes it works fine but sometime the build fails

Your Environment

Plugin version: 0.6.3
Platform: Android
OS version: MacOS
Device manufacturer and model:

Running in Simulator: Yes
React Native version: 0.67.2
Plugin configuration options:
Link to your project:

Context

Task :@mauron85_react-native-background-geolocation:generateDebugRFile FAILED
Execution optimizations have been disabled for task ':@mauron85_react-native-background-geolocation:generateDebugRFile' to ensure correctness due to the following reasons:

Gradle detected a problem with the following location: '/Users/username/Documents/Folder/Project/node_modules/@mauron85/react-native-background-geolocation/android/lib/build/intermediates/local_only_symbol_list/debug/R-def.txt'. Reason: Task ':@mauron85_react-native-background-geolocation:generateDebugRFile' uses this output of task ':mauron85_react-native-background-geolocation:parseDebugLocalResources' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed. Please refer to https://docs.gradle.org/7.2/userguide/validation_problems.html#implicit_dependency for more details about this problem.
Gradle detected a problem with the following location: '/Users/username/Documents/Folder/Project/node_modules/@mauron85/react-native-background-geolocation/android/lib/build/intermediates/packaged_manifests/debug'. Reason: Task ':@mauron85_react-native-background-geolocation:generateDebugRFile' uses this output of task ':mauron85_react-native-background-geolocation:processDebugManifest' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed. Please refer to https://docs.gradle.org/7.2/userguide/validation_problems.html#implicit_dependency for more details about this problem.

Expected Behavior

Should run properly
Actual Behavior

The error given above and
Execution failed for task ':@mauron85_react-native-background-geolocation:generateDebugRFile'.

A failure occurred while executing com.android.build.gradle.internal.res.GenerateLibraryRFileTask$GenerateLibRFileRunnable
/Users/username/Documents/Folder/Project/node_modules/@mauron85/react-native-background-geolocation/android/lib/build/intermediates/local_only_symbol_list/debug/R-def.txt

Possible Fix

Steps to Reproduce

Context

Debug logs

I have the exact same error. Bump !

I have also same error, How to fix this?
Gradle detected a problem with the following location: '/home/omg9800/Desktop/Capri/frontend/consumer_app_client-merged (2) (1)/consumer_app_client-merged/node_modules/@mauron85/react-native-background-geolocation/android/lib/build/intermediates/shader_assets/debug/out'. Reason: Task ':mauron85_react-native-background-geolocation:packageDebugAssets' uses this output of task ':@mauron85_react-native-background-geolocation:compileDebugShaders' without declaring an explicit or implicit dependenc

Me too

By upgrading the values of:
def DEFAULT_COMPILE_SDK_VERSION = 33 def DEFAULT_BUILD_TOOLS_VERSION = "30.0.3" def DEFAULT_TARGET_SDK_VERSION = 33 def DEFAULT_MIN_SDK_VERSION = 21
in  the library react-native-background-geolocation/android/common/VERSIONS.gradle file to match that of my project in android/build.gradle, the error seems to disappear

authors: PartitionPixel adewalebanjo arunzn omg9800 venomkage


text:
ftp: split list_directory response

This way we get a clear list of files and folders instead of an odd list with F or D prefixes.
Depends on https://github.com/mavlink/MAVSDK-Proto/pull/343.
Closes #2308.

Note to self: remove the offset numbers behind the filenames.

source: gharchive/pull-request

repo: mavlink/MAVSDK

license_type: permissive

license_source: github-api


text:
Dependency issue with scikit-image 0.17.x

Hi,
I have recently started to use spimagine for volume rendering of microscopy data. It works perfectly and I absolutely love spimagine. However, while installing spimagine through conda withing my existing conda environment I noticed my scikit-image package has been downgraded from 0.17.x to 0.16.x which caused some problems in my codes which is heavily dependent on scikit-image features.
I guess there is some depenedncy isuue between spimagine and latest version of scikit-image but I was not able to figure that out. Could you please advise how can I have the latest-version of scikit-image working with spimagine?
Cheers

Hi @sandscruise,
Thanks for the kind words!
spimagine should not depend on scikit-image and thus should work with either version. As the conda package was kindly prepared by @tlambert03, maybe he know what could be the reason?
Alternatively, you could just install it with pip install spimagine (which should not downgrade scikit-image).
Hope that helps,
Martin

Hi @maweigert,
Thanks for getting back. I really appreciate that. I tried installing spimagine with pip but it broke my whole conda environment after installing PyQt5 from pip. I got the following error message while using pip to install spimagine:
'''
ERROR: spyder 4.1.3 requires pyqtwebengine<5.13; python_version >= "3", which is not installed.
ERROR: spyder 4.1.3 has requirement pyqt5<5.13; python_version >= "3", but you'll have pyqt5 5.15.0 which is incompatible.
ERROR: scikit-tensor-py3 0.4.1 has requirement numpy==1.16., but you'll have numpy 1.18.4 which is incompatible.
ERROR: scikit-tensor-py3 0.4.1 has requirement scipy==1.3., but you'll have scipy 1.4.1 which is incompatible.
Installing collected packages: configparser, PyQt5-sip, pyqt5, spimagine, scikit-tensor-py3
Successfully installed PyQt5-sip-12.8.0 configparser-5.0.0 pyqt5-5.15.0 scikit-tensor-py3-0.4.1 spimagine-0.2.6
'''
I used to run spyder fine but it is now broken, I guess due to installing PyQt5 through anaconda. Sorry I am pretty new to python and would really appreciate any help regarding this.
Cheers

Sorry to hear that :(
Can you try to install the missing dependency and downgrade pyqt5?
pip install pyqtwebengine
pip install --force-reinstall pyqt5==5.12.0

sorry you're having issues with the conda install @sandscruise.  I can repeat it, fwiw...
It's true that the spimagine conda recipe shouldn't be depending directly on scikit-image, but presumably one of spimagine dependencies is pinned to a version that is itself dependent on an older version of scikit-image (since the current conda package is years old at this point).  This will probably require an updated conda recipe (the current one has some old versions pinned which probably don't need to be pinned), but I unfortunately don't have time to work on this at the moment.  (It should probably be moved to conda forge too).
it is definitely notoriously difficult to use both pip and conda to install Qt-dependent projects into the same environment, and I feel your pain there...
In the meantime, I would keep in mind that while conda will often fails to install if all dependencies  versions aren't strictly met, pip does not.  So you may have luck if you install what you need in conda, then "undo" it with pip.  For instance, I just created a new conda environment and then conda installed spimagine (it worked)... then I ran pip install scikit-image -U to upgrade it.  While it gave some warnings, it happily updated scikit-image and spimagine still seems to work fine.  So until someone gets around to updating the conda recipe, I would try stuff like that.

Hi @maweigert and @tlambert03,
Many thanks for your suggestions. Unfortunately, installing missing dependency and downgrading pyqt5 with pip did not work.
However, I was able to get around this issue following @tlambert03's suggestion by upgrading scikit-image with pip.
Thank you guys again. I really appreciate your help.
Cheers!

source: gharchive/issue

authors: maweigert sandscruise tlambert03

repo: maweigert/spimagine

license_source: bigquery


text:
uninitialized constant OS

Trying to use bundle exe rake neo4j:install task gives me the error uninitialized constant OS
> bundle install
Fetching source index for http://rubygems.org/
sing rake (0.9.2.2)
Using crack (0.1.8)
Using httparty (0.7.8)
Using json (1.6.2)
Using os (0.9.4)
Using rubyzip (0.9.5)
Using neography (0.0.16)
Using bundler (1.0.21)

> bundle exec rake neo4j:install --trace
** Invoke neo4j:install (first_time)
** Execute neo4j:install
Installing Neo4j...
rake aborted!
uninitialized constant OS
/Users/dnagir/.rvm/gems/ruby-1.9.3-p0/gems/rake-0.9.2.2/lib/rake/ext/module.rb:36:in `const_missing'
/Users/dnagir/.rvm/gems/ruby-1.9.3-p0/gems/neography-0.0.16/lib/neography/tasks.rb:8:in `block (2 levels) in <top (required)>'
/Users/dnagir/.rvm/gems/ruby-1.9.3-p0/gems/rake-0.9.2.2/lib/rake/task.rb:205:in `call'
/Users/dnagir/.rvm/gems/ruby-1.9.3-p0/gems/rake-0.9.2.2/lib/rake/task.rb:205:in `block in execute'
/Users/dnagir/.rvm/gems/ruby-1.9.3-p0/gems/rake-0.9.2.2/lib/rake/task.rb:200:in `each'
/Users/dnagir/.rvm/gems/ruby-1.9.3-p0/gems/rake-0.9.2.2/lib/rake/task.rb:200:in `execute'
/Users/dnagir/.rvm/gems/ruby-1.9.3-p0/gems/rake-0.9.2.2/lib/rake/task.rb:158:in `block in invoke_with_call_chain'
/Users/dnagir/.rvm/rubies/ruby-1.9.3-p0/lib/ruby/1.9.1/monitor.rb:211:in `mon_synchronize'
/Users/dnagir/.rvm/gems/ruby-1.9.3-p0/gems/rake-0.9.2.2/lib/rake/task.rb:151:in `invoke_with_call_chain'
/Users/dnagir/.rvm/gems/ruby-1.9.3-p0/gems/rake-0.9.2.2/lib/rake/task.rb:144:in `invoke'
/Users/dnagir/.rvm/gems/ruby-1.9.3-p0/gems/rake-0.9.2.2/lib/rake/application.rb:116:in `invoke_task'
/Users/dnagir/.rvm/gems/ruby-1.9.3-p0/gems/rake-0.9.2.2/lib/rake/application.rb:94:in `block (2 levels) in top_level'
/Users/dnagir/.rvm/gems/ruby-1.9.3-p0/gems/rake-0.9.2.2/lib/rake/application.rb:94:in `each'
/Users/dnagir/.rvm/gems/ruby-1.9.3-p0/gems/rake-0.9.2.2/lib/rake/application.rb:94:in `block in top_level'
/Users/dnagir/.rvm/gems/ruby-1.9.3-p0/gems/rake-0.9.2.2/lib/rake/application.rb:133:in `standard_exception_handling'
/Users/dnagir/.rvm/gems/ruby-1.9.3-p0/gems/rake-0.9.2.2/lib/rake/application.rb:88:in `top_level'
/Users/dnagir/.rvm/gems/ruby-1.9.3-p0/gems/rake-0.9.2.2/lib/rake/application.rb:66:in `block in run'
/Users/dnagir/.rvm/gems/ruby-1.9.3-p0/gems/rake-0.9.2.2/lib/rake/application.rb:133:in `standard_exception_handling'
/Users/dnagir/.rvm/gems/ruby-1.9.3-p0/gems/rake-0.9.2.2/lib/rake/application.rb:63:in `run'
/Users/dnagir/.rvm/gems/ruby-1.9.3-p0/gems/rake-0.9.2.2/bin/rake:33:in `<top (required)>'
/Users/dnagir/.rvm/gems/ruby-1.9.3-p0/bin/rake:19:in `load'
/Users/dnagir/.rvm/gems/ruby-1.9.3-p0/bin/rake:19:in `<main>'
Tasks: TOP => neo4j:install

# Rakefile
require 'neography/tasks'

# Gemfile
source 'http://rubygems.org'

gem 'rake'
gem 'neography'

Sorry about that Dmytrii, use version 0.17 and it should work now.  It eve lets you pick your own version.

Wasn't a big deal (I just require-d it manually). No worries and thanks a lot.

authors: dnagir maxdemarzi

repo: maxdemarzi/neography

license: mit


text:
Node#create with nil in one property doesn't create the node

Neography::Node.create(x: nil, y: 1).neo_id # => nil

Neography::Node.create(x: 0, y: 1).neo_id # => "1"

Should reject nils from the hash if that's a problem.
data.reject { |k, v| v.nil? }

Anyway if there's an error it should be raised.

Update:
Looks like Neo4j server returns 500:
RestClient.post('http://localhost:7474/db/data/node/', {x:nil})

and HTTParty's post returns nil. I checked their docs and it should return a response object with .code. Any idea why?

In evaluate_response I log errors but return nil.

authors: elado maxdemarzi


text:
Taps

For #51

Adding support for onDoubleTap, onLongPress, onTapCancel, onTapDown to DataCell.
Add these new event for DataRow2.

An identical implementation to https://github.com/flutter/flutter/pull/75393/files, which added the same set of functionalities to the Flutter's DataTable.
This is the old PR, which started off from a wrong branch.

@maxim-saplin. I have a few questions about the current implementation of the onRowTap.
if (onTap != null ) {
      label = InkWell(
        onTap: onTap,
        overlayColor: overlayColor,
        child: label,
      );
    } else if (onSelectChanged != null) {
      label = GestureDetector(
        child: TableRowInkWell(
            child: label,
            overlayColor: overlayColor,
            onTap: onRowTap == null
                ? onSelectChanged
                : () {
                    onRowTap();
                    onSelectChanged();
                  }),
        onSecondaryTap: onRowSecondaryTap,
        onSecondaryTapDown: onRowSecondaryTapDown,
      );
    }

onRowTap only comes into play when if (onSelectChanged != null). Meaning, without having onSelectChanged, onRowTap will not be call. Is this intended?
onRowTap(); and onSelectChanged(); are called together. This is different from the logic of DataCell.onTap, which skip the onSelectChanged(). Intended too?

With number 2 behaviour, double tap and long press are going to be tricky. So I like to know what is your opinion on this first.

_buildDataCell() will always get non-null onSelectedChanged, below is the only call to this function and as you can see it has arrow function assigned:

Which suggests that signature of _buildDataCell can be changed to accept non-null VoidCallback onSelectChanged and null check can be removed.
Row taps are emulated by  setting individual cell tap events.

I've just committed to async-table the change remocing the nullable onSelectedChanged and excessive if statement

Thanks a lot for the help! Moved the changes to async-table branch already. Please let me know if I missed anything. Planning on moving to master and pub.dev soon

Thank you for the merge! I shall make good use of the row tap and double tap in my project when it moves to master.
I haven't add to the example though, I will make another PR for them.

authors: maxim-saplin yuankuan-itbh


text:
Map UserLoggedOut to action

Hi!
We are working on single sign out across browser tabs for all our clients that are using our OP. To achieve this we need to catch the UserSignedOut event which is fired if the session check fails. It would be nice if you could dispatch an action a registering a UserSignedOut event.  See oidc.client.js
Regards,
Anders

Agreed. Will add this as Sooners as I find Theo Time for it.

I've just pushed v2.2.2-beta.1 to npm. Please check it out and see if this helps you.

Hi!
Thanks for the quick response and fix. The event works as expected :)

Glad to hear it.

authors: anderskristiansen maxmantz

repo: maxmantz/redux-oidc


text:
New variant for tags-mode

Hi! 😄
This is a suggestion for a new variant of the tag mode. The multiple_select option for the new tags_mode attribute makes it possible to select multiple options quickly without needing to search or force the dropdown to appear. The current tag mode hides the dropdown-part when a option is selected. This approach could probably be described as a kind hybrid of the normal live_select tag mode and a normal multi select input.
A new attribute tags_mode is added with :default (how tags work today) and :multiple_select as possible options.
Example usage taken from demo-app:
<.live_select
   field={my_form[:city_search]}
   selected_option_class="cursor-pointer font-bold hover:bg-gray-400 rounded"
   mode={:tags}
   tags_mode={:multiple_select}
   placeholder="Search for a city"
   update_min_len={3} />

There is some code in the demo app related to selected_option_class as this feature would need some new style defaults/style changes to look passable out of the box. This should probably be solved some other way. Maybe by adding some new default styles.
The name chosen, multiple_select, is very much up for debate. I just needed something to work with.
Potential performance issue
When testing in the demo app I do notice some slowness when selecting or deselecting many options in rapid succession. I did not experience this in our app. I am not sure if this is a flaw in the implementation or just that the dataset for the demo app is very large. Any suggestions on this point is especially welcome.
Breaking changes
The feature also changes the value exposed to the option-slot to also return an indication if the option is already selected. This is one of the main points of the change as the impetus for this feature is a design/UX that displays the selected with a checkbox. See attached picture for example. I suppose this could be done with just styles but the design seems harder to replicate that way and I also think it would be nice to be able to have that info available to the slot. But still open for debate. :)
Example of option-slot usage:
Notice the :let now exposing a tuple which contains the option and a selected boolean.
<:option :let={{%{label: label, value: value}, selected}}>

    <input
      class="rounded w-4 h-4 mr-3 border border-border"
      type="checkbox"
      checked={selected}
    />
    <%= label %>

</:option>

Rendered example:

This is a suggestion based on functionality that we where in need of and I hope it can be added to the project in some form.
This is not expected to be merged as-is (ex. tests is missing for now) but it is working code that we would use in our fork and a good point to discuss from I think.
I'm aware that this might not be something that this project wants and I'm happy to make changes or discuss the approach. Maybe there is a better way to achive the same or something very similar?
The changes necessary does not seem to invasive though from my perspective (except maybe the option-slot breaking change 😅).
Let me know what you think. 😄
EDIT: I forgot while writing this, but there is also a bug in this implementation I have not figured out. When making the first selection the blur event triggers and hides the dropdown. This does not happen on other selections but consistently happens from state of nothing selected to first option selected.

Hi @ringvold thanks a lot for this, I just took a superficial look but it sounds like solid work 💪 using checkboxes in the dropdown is something I've been thinking of adding for a long time now.
Unfortunately, I'm quite busy this coming week, but I will take a proper look as soon as I find some time. Cheers!

Hi @ringvold I finally found the time to read carefully what you wrote (I've been really busy in the past few weeks, still busy but things are getting a bit better).
I haven't looked at the code yet. Here's a couple of comments:

I like the idea of enabling a "quick selection mode". I'm not sure I would add a new attribute for it though. To me, it feels cleaner and less clunky to have this as a third mode: :single, :tags and (name also totally up for debate), :quick_tags. Let me know what you think

Couldn't the performance issue you were observing be caused by latency? Were you trying out your app locally? Regardless, the demo app has a bit more of 800 cities, and the search is slow indeed. I should probably add an index, right now the search simply traverses the list of cities and collect the matches.

I really like the idea of exposing the selection status to the option slot. However, I don't think that this needs to be a breaking change. Instead of exposing a tuple, we can add a new field to the map:

<:option :let={%{label: label, value: value, selected: selected}}>

In this way, old code that ignores the selected field would still work

it would be great to allow the user to deselect options using the checkboxes in the selection. But not sure right now how to do that, it's just an idea and probably out of the scope of your feature. In any case, exposing the selected status to the slot is probably a good first step in this direction.

Let me know what you think

Hi!
Thought I'd get back to you sooner but stuff happened here as well.

I am very open to how the public API should be. I always thought of it as a variant of the tag mode, but I see how it also could be just a configuration for the tag mode from a users perspective. I felt "quick selection" as you named it has a good description but as for how it should be exposed to the user I'm not sure.

Hi!
Thought I'd get back to you sooner but stuff happened here as well.

I am very open to how the public API should be. I always thought of it as a variant of the tag mode, but I see how it also could be just a configuration for the tag mode from a users perspective. I felt "quick selection" as you named it has a good description but as for how it should be exposed to the user I'm not sure.

Functionally it is a bit more than "don't close the dropdown" (as I made it here at least) as it also enables you to deselect from the drop down which I believe is not possible on "normal" tags mode. I think that might be why I think of it more as a variant of tag mode. You should have the final say on the API but I  see like :close_dropdown_on_select do not fully encapsulate the functionality I had in mind.
So I lean towards :quick_select/:quick_tags or something like that.

Yes, I tried it locally and still experienced slowness. I tested it out again and it is most pronounced when a lot of elements are selected and selecting very quickly. I suspect it might be a combination of processing a large list of options and handling many selections in quick succession. Maybe a debounce of the selection and handle an event with multiple selections solves it, but that sound like it might be a larger refactor.

Yeah, that should work. Is there any way this could interfere with some custom fields a user might have used with the same name?

I'm not sure what you mean by allowing to use checkboxes. I think about them as visual aide.  Selection technically happens on interaction with the parent element. Are there any advantages to changing this? As in it could be advantageous to move the click handler to the checkbox? Exposing the selected status enables custom markdown for selected/unselected options as an addition to the css options available today.

Other things of note
I have noticed that this PR breaks the current behavior for tags as you can deselect from the drop down. Which you can not to in the current released version. I have tried to not change the current functionality of tag mode so I'm not sure what happened there. I consider that a bug.
One thing I have not figured out yet (although not look at it very much yet) is how to not loose focus of the element when selecting it when operating it with keyboard only. Currently it resets focus to the search box when selecting. I would like to keep it in the dropdown at/around the selected element to be able to continue the selection. Any thoughts on this?

Functionally it is a bit more than "don't close the dropdown" (as I made it here at least) as it also enables you to deselect from the drop down which I believe is not possible on "normal" tags mode. I think that might be why I think of it more as a variant of tag mode. You should have the final say on the API but I feel like :close_dropdown_on_select do not fully encapsulate the functionality I had in mind.

Yeah I didn't realize you can deselect from the dropdown...

I'm not sure what you mean by allowing to use checkboxes

And this is exactly what I meant by "using checkboxes to deselect".
Ok so I agree with you now, close_dropdown_on_select obviously doesn't cut it. A third selection mode is more appropriate. quick_tags sounds good to me!

Yeah, that should work. Is there any way this could interfere with some custom fields a user might have used with the same name?

You mean custom fields they're passing to the slots? To preempt this, we could simply taise an exception when someone uses the selected key for the  options.
I will take a look at the last 2 points you mentioned (breaking current behavior and not losing focus) soon.
But it sounds like at least we agreed on how to expose this new mode in the API and how to pass the selected status in the slots :)

Yes, it does sound like we are onto something her 😄

You mean custom fields they're passing to the slots? To preempt this, we could simply raise an exception when someone uses the selected key for the options.

That is maybe also a breaking change but certainly much smaller than my suggestion.
I will make a suggestion on the default styles for this mode. I cant remember the details but there are some changes that need to be made to make it look decent out of the box.

That is maybe also a breaking change but certainly much smaller than my suggestion.

I don't think this is a breaking change because we're not breaking any API. The docs say that the options can be specified as maps with the shape %{label: label, value: value}.  It doesn't state that other keys in the map will be made available to the slots.

Is this one good to merge?

@egeersoz no, we just discussed a few points and I'm sure @ringvold has still a few things to add before it's ready for prime time :)

@egeersoz I still have to implement what we talked about, add test and then probably a new check by @maxmarcon. I hope to find some time to look at it this weekend though. :)

Life happens and I have not gotten to this when I thought. 🕙🏃➡
@maxmarcon Looking a bit at it now and I remember why I did this functionality as a new variant for tags. It is a bit easier to implement when it is just a variant of tags as we can piggyback on the existing tags functionality with some changes changes. Introducing a new mode we have to make sure not to mess up :tags and also add :quick_tags to most, if not all places where we are checking for :tags. It will probably be fine but I think that is why I defaulted to a new variant for tags.
On another note my fix for the dropdown removal on first select did not work. It basically just removed all phx-focus use defined externally (parent focus events). 😅
The fix seems to be to always render the tags container div but conditionally render the rest. (It might be the re rendering when the first tag is added that triggers the blur event that hides the dropdown.) In practice it would be to move the if on line 11 inside the div beneath it.
The down side of this approach is that the dropdown is not closed when removing the last selected tag which I am now used to, but it probably cant be helped.
Hoping to have something to look at soon.

Rebased on latest master. Fixed tests for tags and added tests for quick_tags.

@maxmarcon Let me know if there are any more things that need to be fixed og changed. :)
When I think about it we might need to add some documentation. 🤔

@maxmarcon Can this be merged?

@ringvold this looks awesome, thank you! Review coming soon.
FYI: I pushed a couple of minor commits to your branch just to test if I could do it (I updated a line in the docs).

🥳  🚀  💪

authors: egeersoz maxmarcon ringvold


text:
🛑 IDRC - International Development Research Centre is down

In b9f6e45, IDRC - International Development Research Centre (https://www.idrc.ca/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: IDRC - International Development Research Centre is back up in 85ecf74 after 25 minutes.

repo: maxneuvians/status-statut

license: MIT


text:
Find a way to make this work with RealityKit

Feature Request
What do you want to add?
The same path geometry working in RealityKit - without exporting from SceneKit as a USDz
How should it look like?
The same as in SceneKit
Notes
RealityKit doesn't seem to support custom geometries, I'll continue to investigate but want to get this repo working with RealityKit.

RealityKit doesn't support custom geometries, I'm hoping this will be added at a later date. At which point there with be a new repository to support creating geometries just like this one!

repo: maxxfrazer/ARKit-SCNPath


text:
Prettify the code.

update

I have tried to resolve issue #7.
I have not removed inline styling because
I am not sure about the folder structure.
So, if we have to do that please let me know @mayukh18


text:
How to Contribute Documentation?

Hi,
I'm trying to solve #7, but I'm confused with the source tree, as it seems to contain build files, and has 2 source directories, one called _sources containing text files, and one called source containing .rst files.

How are these files and folders related?
What is the procedure to change text or add new files?
How to build the documentation locally to verify its integrity before pushing PRs?

Thank you!

Thanks @hellekin! Looking at previous commits, it seems that it should be enough to change the .rst files. @haniavis could help on how you can build locally the documentation, but for simple changes you could already try a pull request directly changing the corresponding .rst file.

I updated here the guidelines for contributors: https://github.com/mazi-project/guides/wiki/Contributing
Next step is to write guidelines for the contributors to the software code ...

OK. I think there should be a Makefile to build the documentation, and the build/ directory should not be in the repository, only the sources. That would remove confusion... Maybe a Dockerfile could be there as well for people to preview the build without polluting their system with Sphinx dependencies.

Hi @haniavis, I made #10 that should also close this issue.

authors: hellekin panosnethood

repo: mazi-project/guides


text:
Current state config of plugin

How may I get current state config your plugin?

For now, we can't.
but we will put this into our next improvement.

hi, @mazipan
Yes please, thanks)

You can update version to 3.2.0 then getting current global configs with
this.$CurrencyFilter.getConfig()

Thank you @mazipan ,)
Have a nice day.

You can update version to 3.2.0 then getting current global configs with
this.$CurrencyFilter.getConfig()
@VIMHaos

Would be nice to have these in the docs. This seems to be needed (the setConfig()) to have the currency update instantly when a user changes his currency settings.

Ah, I already dropping this feature.
Since it's hard to achieve consistency from my latest approach.
Maybe need another perspective to solve this problem.

authors: VIMHaos iggyvanlith mazipan

repo: mazipan/vue-currency-filter


text:
Encryption issues

An SHA1 hash of the password is stored in the database header page.  This is insecure because a malicious user could generate hashes for common passwords and simply compare them with the hash stored in the header page.  Further, any file with the same password will have the same password hash.
As mention in #581 an Encrypt-then-MAC should be used which provides authentication without the need for storing a hash of the password.

Could you point out why this is a big deal? The reason I think it's not, is that this particular SHA1 hash is not used to derive the encryption key for the database.
If a hash collision were to be found by an attacker it would only get them past the header page validation phase. Once the system began to attempt decrypting data, (which uses MS's PBKDF2 implementation to derive the key) a decryption failure would occur.

In simple, it allows dictionary attacks on the database since there is a one to one mapping between plain text passwords and their associated SHA1 hash.  You could compute the SHA1 hash for a dictionary of plain text passwords very quickly.  To verify if a password is correct, one must only compare it with the hash stored in the file.  This is a problem because that process is computationally fast.  Once a malicious user has done this for a set of passwords, they have a reusable table of plain text passwords and their associated SHA1 hashes.  Unless you can guarantee that every instance of a LiteDB has a strong password, this gives a malicious user a very quick way to get into the data.
The use of a PBKDF2 function to derive the key has two purposes:
First it makes it computationally slow to derive a key from a password.  This time is short enough for a legitimate user generating one key when they have the correct password, but not short enough if you want to try lots of passwords.
Second, they use a salt to ensure that if a multiple users reuse the same plain text password, they key is not the same.  This renders the dictionary useless provided a different cryptographically random salt is used for each database.
In summary, hashing a password without a salt and storing it next to the database is never a good idea.

Herp derp. Absolutely right. Embarrassed that I didn't realize that.
On Mon, Apr 24, 2017, 2:23 AM elyoh notifications@github.com wrote:

In simple, it allows dictionary attacks on the database since there is a
one to one mapping between plain text passwords and their associated SHA1
hash. You could compute the SHA1 hash for a dictionary of plain text
passwords very quickly. To verify if a password is correct, one must
only compare it with the hash stored in the file. This is a problem
because that process is computationally fast. Once a malicious user has
done this for a set of passwords, they have a reusable table of plain text
passwords and their associated SHA1 hashes. Unless you can guarantee that
every instance of a LiteDB has a strong password, this gives a malicious
user a very quick way to get into the data.
The use of a PBKDF2 function to derive the key has two purposes:
First it makes it computationally slow to derive a key from a password.
This time is short enough for a legitimate user generating one key when
they have the correct password, but not short enough if you want to try
lots of passwords.
Second, they use a salt to ensure that if a multiple users reuse the same
plain text password, they key is not the same. This renders the dictionary
useless provided a different cryptographically random salt is used for each
database.
In summary, hashing a password without a salt and storing it next to the
database is never a good idea.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/mbdavid/LiteDB/issues/586#issuecomment-296535835, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAGKpHlx-zKi-sxy8FhAWlZ5634G-Lnyks5rzD_vgaJpZM4NFJ6y
.

For next version I´m thinking in remove this hash in Header page and validate password only by checking a new fixed page Type with know data before encrypt, like: Full a whole page with 1 and than encrypt using user password. To check if password is valid, just decrypt this fixed page and test if all bytes are 1 again.

The fixed page of 1s sounds like a bad idea. The knowledge of cleartext is
too informative for an attacker.
On Mon, Apr 24, 2017, 8:16 AM Mauricio David notifications@github.com
wrote:

For next version I´m thinking in remove this hash in Header page and
validate password only by checking a new fixed page Type with know data
before encrypt, like: Full a whole page with 1 and than encrypt using
user password. To check if password is valid, just decrypt this fixed page
and test if all bytes are 1 again.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/mbdavid/LiteDB/issues/586#issuecomment-296643309, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAGKpBBeYA2uMyE7o-zIzcOUMb2ooFFHks5rzJKNgaJpZM4NFJ6y
.

To secure the library, the immediate action must be to remove the hash from the header page and remove the password verification all together.  This removes the vulnerability and ensures the data is secret without possession of the password.  The current use of a PBKDF2 function to derive the key makes it extremely unlikely that an incorrect password will lead to any intelligible plain text data.
Longer term, implementing an Encrypt then MAC approach is needed to verify the data has not been modified since it was encrypted.  Separate verification of the password is not needed in this approach; if the password supplied is incorrect or the data has been modified, this is easily detected.
SecurityDriven.Inferno  provides straightforward methods for doing this out of the box.  It is professionally audited and MIT licensed so can be used in this project.

Totally agree. If I get a chance I may take a swing and send PR.
On Mon, Apr 24, 2017, 2:24 PM elyoh notifications@github.com wrote:

To secure the library, the immediate action must be to remove the hash
from the header page and remove the password verification all together.
This removes the vulnerability and ensures the data is secret without
possession of the password. The current use of a PBKDF2 function to derive
the key makes it extremely unlikely that an incorrect password will lead to
any intelligible plain text data.
Longer term, implementing an Encrypt then MAC approach is needed to verify
the data has not been modified since it was encrypted. Separate
verification of the password is not needed in this approach; if the
password supplied is incorrect or the data has been modified, this is
easily detected.
SecurityDriven.Inferno
https://github.com/sdrapkin/SecurityDriven.Inferno provides
straightforward methods for doing this out of the box. It is professionally
audited and MIT licensed so can be used in this project.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/mbdavid/LiteDB/issues/586#issuecomment-296780723, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAGKpBaFu78gqQY2qshzPH-9m087EVLkks5rzOjtgaJpZM4NFJ6y
.

Not sure if it has been mentionned yet, but there are also a bunch of issues related to the AES itself. Basically, using ECB mode is pretty bad in itself and a predictable IV is set but isn't used(because of the mode). In this case, from what I know, it seems like the best mode would be AES-XTS

Hi! With the objective of organizing our issues, we are closing old unsolved issues. Please check the latest version of LiteDB and open a new issue if your problem/question/suggestion still applies. Thanks!

authors: elyoh lbnascimento mbdavid ronnieoverby zer0x64

repo: mbdavid/LiteDB


text:
DateTime strange UTC(?) offsetting between inserting and selecting

I have such data model:
public class MyObject
{
        [BsonId]
        public long Id { get; set; }

        [JsonConverter(typeof(Iso8601DateTimeConverter))]
        public DateTime? DueTo { get; set; }
}

This DateTimeConverter, is:
public class Iso8601DateTimeConverter : IsoDateTimeConverter
    {
        public override void WriteJson(JsonWriter writer, object value, JsonSerializer serializer)
        {
            var dateTime = (DateTime)value;
            serializer.Serialize(writer, dateTime.ToString("yyyy-MM-ddTHH:mm:ssZ"));
        }
    }

When data comes from API, it's like in below example:
{
    "Id": 98,
    "DueTo": "2014-01-01T06:00:00Z"
}

From code perspective, DueTo field is 2014-01-01 at 06:00 AM.
But when I'm inserting/upserting data into LiteDB, it's beeing converted into 2014-01-01 at 07:00 AM - data format is not the problem here, but the strange offset.
The question is why?
When I've looked into my_db_file.db, inside it's 2014-01-01 07:00:00.000 string.
What can I do, to ommit data inconsistency between inserting and selecting DateTime in LiteDB? Is there any special BSON attribute to be set?

Hi @Szymaniuk, normal JSON format doesn't support dates. So, when LiteDB parse this "date" as simple "string".
To fix this, LiteDB implement and extended JSON format. Special types use an embedded document like { $type: "string value" }. It´s same used in MongoDB.
In this case, your document must be:
{
    "Id": 98,
    "DueTo": { "$date": "2014-01-01T06:00:00Z" }
}

All other types can be see here:
https://github.com/mbdavid/LiteDB/wiki/Data-Structure#json-extended

Strange... I see there, that All DateTime values converts to UTC before store and converts back to local on retrieve.
Is there any option to override default behaviour implementation, to achieve ...and converts back to UTC on retrieve. ?

@mbdavid what do you think, to change:
https://github.com/mbdavid/LiteDB/blob/21bebf439125401d76490dd1e4e6bbad502b9473/LiteDB/Document/Bson/BsonReader.cs#L113
+
https://github.com/mbdavid/LiteDB/blob/21bebf439125401d76490dd1e4e6bbad502b9473/LiteDB/Document/Json/JsonReader.cs#L158
from:
.ToLocalTime()
to:
.ToUniversalTime()
?
For me, it's fixes all problems with DateTime. I don't know what was the intention to:
All DateTime values converts to UTC before store and converts back to local on retrieve.
From my PoV all DB things related with DateTime, should be done in UTC/non changed date time. All time zones changes should be stricted to UI/external API communication.

Hi,
we're facing the same issue with DateTime. We tried to implement the solution based on #738 like this:
BsonMapper.Global.ResolveMember = (type, memberInfo, member) =>
{
if (member.DataType == typeof(DateTime))
{
member.Serialize = (o, m) => DateTime.Parse(o.ToString());
member.Deserialize = (v, m) => v.AsDateTime.ToString("o");
}
};
2 issues:

Setting a breakpoint within the action shows that the code is actually never executed.
I'm also not sure if the above conversion from and to DateTime to/from string resolves the issue and is the best solution in terms of performance.

Can you provide a sample on how to "fix/workaround" the UTC issue with 4.0?
Thanks,
Stefan

Hi @StefanKoell, it's on my list for 4.1: BsonSettings for works with DateTime in UTC or Local

That's great news! Any workaround we can use for now?

Are you converting POCO class into BsonDocument? Or are you working direct with BsonDocument?

I'm working with BsonDocuments directly.

I see where you are going ;) I've changed the datetime to UTC after reading it from the BsonDocument. Now all is good. Once you introduce the BsonSettings for UTC, I will revert to the original code.
Thanks for the fast response!

Oh, thats why ResolveMember are now working, it's only to BsonMapper between POCO class to BsonDocument.
The only workaround for now is change source code here.

@mbdavid so from 4.1.0, there need to be used utc=true in connection string, in order to use this feature/fix, right? https://github.com/mbdavid/LiteDB/releases
Thanks.

Hi @Szymaniuk, yes. By default, BSON deserialization keeps DateTime as Kind=Local to be compatible. If you want work with UTC, you must define in connection string (or if you use LiteEngine you can specify in ctor).

Perhaps instead, store the Kind as well? I just got bitten by this myself. In my application the dates are all Kind=UTC. I was trying to compare Newtonsoft JSON deserialized event message data by value with what I was getting back from LiteDB, and they were not matching up like I expected.

@BennieCopeland, there is no option to store DateTimeKind in BSON format. Maybe in future I will made my own serialization format to implement better (like RavenDB do)

authors: BennieCopeland StefanKoell Szymaniuk mbdavid


text:
Can we improve the database handling?

After some superficial research I asked myself if we are using the smartest way possible to manage the database stuff. After all we are definitely not the first ones that use a database in a docker container:

https://stackoverflow.com/questions/43880026/import-data-sql-mysql-docker-container

I also like the possibility to externally call something like this
gzip -cd mysqldata/database.sql.gz | docker exec -i $user-omlbotlookup /usr/bin/mysql openml

because this is blocking the terminal until the execution is finished and it might helt to see why travis fails.

I tried another version to start the container so we can see what's happening...
Somehow mysql fails to start.
https://travis-ci.org/mboecker/lookup-server/builds/369139884#L4653

It's possible, that the data import is just too slow for travis.
https://travis-ci.org/mboecker/lookup-server/builds/369139884#L4731
It seems like it's just running the test script we wrote. When starting up the container takes too long, it terminates the build. We could use a much smaller database file for travis?

This is because I set the timeout in the R package to 10mins. What happens behind is that the docker container is tried to start but fails silently so that we just see the timeout.

We could start the mysql server in the container, call "mysql" from externally like you suggested and then start using the API. It's just not a good idea to start using the server before the database is imported.

With the newest commit, one can

start the server using run-fg.sh or start-fg.sh
(this will start the mysql database and the API)
use either cat data.sql | ./import_data.sh or gzip -cd data.sql.gz | ./import_data.sh to import whatever .sql file he wants into the server/docker container.
start using the API.

We can hide this process in the package easily by calling these commands for the user.
This should solve this issue.

Closed?

Yes

authors: jakob-r mboecker

repo: mboecker/lookup-server


text:
How to prevent d3 brush from firing a click event?

I'm sorry about ask by issues!
I had an problem like this Prevent d3 brush from firing a click event,but i can't find the solution in stackoverflow.
Could you give me some hints about this problem?

Sorry, but please use Stack Overflow tag d3.js or the d3-js Google group to ask for help. These issues are for feature requests and bug reports only. Thank you!

authors: mbostock tianxuzhang

license: ISC


text:
🛑 Mazatlan is down

In 4839f05, Mazatlan (https://www.mazatlanfc.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Mazatlan is back up in e6c4a33.


text:
Tweak layout of Schedule Finder on small screens

Asana Ticket: Schedule Finder | Mobile Layout

The Schedule Finder box is no longer in a collapsible section
Page header (e.g. "Info & Maps") is now displayed after the box

@digitalcora Looks great! Glad to also be rid of the flashing above the map on desktop with slow connections. Looking forward to seeing how more folks interact with this live. 👍

Glad to also be rid of the flashing above the map on desktop

I might have fixed this accidentally — it was an issue I saw after I made some changes for this branch, and I assumed I had introduced it. Happy little accidents 🌳

It looks like what this code is aiming to do, across a few files, is implement logic for "if there's no schedule note, use the mobile version of ScheduleFinder

That's not the case, so hopefully I can clear up some confusion here 😄
ScheduleNote is displayed in place of ScheduleFinder on subway line pages (and only there). We do this because subway lines don't (officially) have individually scheduled trips, so Schedule Finder would make no sense in that context. Instead there is a note that explains the headways of the line. This is the case regardless of mobile/desktop breakpoints. This PR does not touch that behavior.
The classModifier code you describe is there just to make the ScheduleFinder appear in one of two different places depending on whether the sidebar exists in the current breakpoint. You're correct that I was following the existing code; I saw we were already passing in a classModifier prop, and that we already had CSS for schedule-finder-- classes, but no such prop was defined in the component itself. I assumed it was a remnant of something that used to work, and restored it to functionality. But, you're probably right that we could do this more simply using a descendant selector in the CSS, and not need the separate schedule-finder-- classes at all.

But, you're probably right that we could do this more simply using a descendant selector in the CSS

I pushed a new commit that does this, let me know what you think @thecristen. There were no unique IDs or classes already that could be used to make the distinction, so I had to add some new ones.

authors: digitalcora ingridpierre

repo: mbta/dotcom


text:
Works fine in VD 1.29.0 !!!

Thanks a lot!!! I asked Guy for a long time, but I got it from you :) I checked it in all games with OpenXR and it works fine everywhere without steamVR! Pico4 5.8.2 + VD 1.29.0
True, it’s not OpenXR that says in the info panel, but Oculus :)))

Thanks.
No one ever said It didn't work with 1.29.0 though.

I thought we needed beta 1.29.1 :)

authors: huliqan mbucchia

repo: mbucchia/VirtualDesktop-OpenXR


text:
🛑 ChatGenie Client API is down

In 5a4e81a, ChatGenie Client API ($CHATGENIE_CLIENT_API) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ChatGenie Client API is back up in 7f59b54.


text:
🛑 ChatGenie Client API is down

In c7b1cfa, ChatGenie Client API ($CHATGENIE_CLIENT_API) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ChatGenie Client API is back up in 3e15958.


text:
🛑 ChatGenie Client API is down

In f37b885, ChatGenie Client API ($CHATGENIE_CLIENT_API) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ChatGenie Client API is back up in c35d5a7.


text:
🛑 ChatGenie Client API is down

In 06f9090, ChatGenie Client API ($CHATGENIE_CLIENT_API) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ChatGenie Client API is back up in 15503ab.


text:
🛑 ChatGenie Client API is down

In 06d7efc, ChatGenie Client API ($CHATGENIE_CLIENT_API) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ChatGenie Client API is back up in 3575240 after 28 minutes.


text:
🛑 ChatGenie Client API is down

In 6e65fa3, ChatGenie Client API ($CHATGENIE_CLIENT_API) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ChatGenie Client API is back up in b4ac134 after 1 hour, 45 minutes.


text:
🛑 ChatGenie Client API is down

In 579aa2f, ChatGenie Client API ($CHATGENIE_CLIENT_API) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ChatGenie Client API is back up in ebcfae3 after 9 minutes.


text:
🛑 ChatGenie Client API is down

In 184e615, ChatGenie Client API ($CHATGENIE_CLIENT_API) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ChatGenie Client API is back up in 910a60d after 49 minutes.


text:
🛑 ChatGenie Client API is down

In b80928a, ChatGenie Client API ($CHATGENIE_CLIENT_API) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ChatGenie Client API is back up in 9b0160d.


text:
🛑 GitHub Mirror is down

In f7c414b, GitHub Mirror (https://gh.chapro.xyz) was down:

HTTP code: 500
Response time: 68 ms

Resolved: GitHub Mirror is back up in 12bc019 after 10 minutes.

repo: mchaNetwork/status


text:
🛑 GitHub Mirror is down

In c30d9c7, GitHub Mirror (https://gh.chapro.xyz) was down:

HTTP code: 500
Response time: 137 ms

Resolved: GitHub Mirror is back up in 8977ee7 after 18 minutes.


text:
Mobile connect problem

When I try to connect this map program using my iphone6 by scanning the code, It always give a response "No active client for XXXXX".  What happened to me? Have I made some mistakes?
I have tried both window and linux version.

make sure you have server selection enabled

I'm sure that I have selected the option Server Enabled.

Now ip：8000 works on linux.

repo: mchristopher/PokemonGo-DesktopMap


text:
Found Pokemon log (CSV)

The app is fantastic, but please insert an option to choose a path where the software creates a CSV log (something like "Pokemon code;LAT;LONG;expiring_datetime" should be fine) of found Pokemon.
So we can use this data to implement crowd-sourced maps (probably just friends in the same city) using third-parts software.
Thanks!!

There's a solution here: https://github.com/mchristopher/PokemonGo-DesktopMap/issues/831
The database file doesn't just have Pokestops and Gyms. It also has Pokemon and Scanned Locations. Each type is in a separate table.


text:
Enable a Date Filter via dcc. DatePickerRange

Description
Hard-coded draft implementation of a DateRangePicker - only for discussion

dcc. DatePickerRange does not have value property, which complicated simple implementation
ctx.arg_grouping contains two entries for every dcc. DatePickerRange, which does not work with the current filter implementation
current hard-coded examples works however, and shows areas that would need to be adressed

Screenshot
Checklist

[x] I have not referenced individuals, products or companies in any commits, directly or indirectly
[x] I have not added data or restricted code in any commits, directly or indirectly
[ ] I have updated the docstring of any public function/class/model changed
[ ] I have added the PR number to the change description in the changelog fragment, e.g. Enable feature XXX ([#1](https://github.com/mckinsey/vizro/pull/1)) (if applicable)
[ ] I have added tests to cover my changes (if applicable)

Types of changes

[ ] Docs/refactoring (non-breaking change which improves codebase)
[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Notice

[x] I acknowledge and agree that, by checking this box and clicking "Submit Pull Request":

I submit this contribution under the Apache 2.0 license and represent that I am entitled to do so on behalf of myself, my employer, or relevant third parties, as applicable.
I certify that (a) this contribution is my original creation and / or (b) to the extent it is not my original creation, I am authorised to submit this contribution on behalf of the original creator(s) or their licensees.
I certify that the use of this contribution as authorised by the Apache 2.0 license does not violate the intellectual property rights of anyone else.

Description
Hard-coded draft implementation of a DateRangePicker - only for discussion

dcc. DatePickerRange does not have value property, which complicated simple implementation
ctx.arg_grouping contains two entries for every dcc. DatePickerRange, which does not work with the current filter implementation
current hard-coded examples works however, and shows areas that would need to be adressed

Screenshot
Checklist

[x]  I have not referenced individuals, products or companies in any commits, directly or indirectly
[x]  I have not added data or restricted code in any commits, directly or indirectly
[ ]  I have updated the docstring of any public function/class/model changed
[ ]  I have added the PR number to the change description in the changelog fragment, e.g. Enable feature XXX ([#1](https://github.com/mckinsey/vizro/pull/1)) (if applicable)
[ ]  I have added tests to cover my changes (if applicable)

Types of changes

[ ]  Docs/refactoring (non-breaking change which improves codebase)
[ ]  Bug fix (non-breaking change which fixes an issue)
[x]  New feature (non-breaking change which adds functionality)
[ ]  Breaking change (fix or feature that would cause existing functionality to change)

Notice

[x]  I acknowledge and agree that, by checking this box and clicking "Submit Pull Request":

I submit this contribution under the Apache 2.0 license and represent that I am entitled to do so on behalf of myself, my employer, or relevant third parties, as applicable.
I certify that (a) this contribution is my original creation and / or (b) to the extent it is not my original creation, I am authorised to submit this contribution on behalf of the original creator(s) or their licensees.
I certify that the use of this contribution as authorised by the Apache 2.0 license does not violate the intellectual property rights of anyone else.

Instead of using the dcc.DatePickerRange, can you try using this: https://www.dash-mantine-components.com/components/datepicker
The advantage of that component is that it has the value property annd similar to the RangeSlider it expects a list, so if we leverage that, we might not need all the hard-coded changes you have in this draft PR :)

authors: huong-li-nguyen maxschulz-COL

repo: mckinsey/vizro


text:
fix: typo in README file

Fixes a typo in README.md

thx

authors: codershiba mcollina

repo: mcollina/borp


text:
Add support for execution errors

fixes #7

CI is not happy:
  not ok Snapshot entry not found: "test/routes.js TAP POST return 500 on resolver error > undefined 1NaNRun with TAP_SNAPSHOT=1 in the environment to create snapshots

should be fixed now ;)

authors: mcollina temsa

repo: mcollina/fastify-gql


text:
Support PREFIX and DESTDIR in Makefile

The Jake Makefile install target assumes I want jake installed in /usr/local. Could you support a PREFIX variable allowing me to specify a different location? While we're there, could you also allow installing to a staging area using the DESTDIR variable? This patch implements these suggestions:
https://trac.macports.org/browser/trunk/dports/devel/jake/files/patch-Makefile.diff?rev=87891

This would be great. Could you implement it as a normal GitHub
pull-request, and doc it in the README? I'll merge it ASAP.
Thanks for using (and more importantly improving) Jake. :)
Matthew
On 12/10/11 6:30 PM, ryandesign wrote:

The Jake Makefile install target assumes I want jake installed in /usr/local. Could you support a PREFIX variable allowing me to specify a different location? While we're there, could you also allow installing to a staging area using the DESTDIR variable? This patch implements these suggestions:
https://trac.macports.org/browser/trunk/dports/devel/jake/files/patch-Makefile.diff?rev=87891

Reply to this email directly or view it on GitHub:
https://github.com/mde/jake/issues/85

Apologies for not submitting a pull request; I have not had a chance to learn git properly yet. Thank you for committing the fix anyway.

No worries. Actually, I ended up needing it for something too, so it was perfect timing.

The jake symlink is not made correctly: it points to cli.js in the destroot, but it needs to point to cli.js's ultimate install location. The original patch I provided above was correct because it used a relative path, but you committed something different in cb989017ce3a0c7597007f64453f58f2a2bd6317. Here is a new patch to fix it now:
https://trac.macports.org/browser/trunk/dports/devel/jake/files/patch-Makefile.diff?rev=89034

Fixed and in the latest release on NPM. Thanks. :)

authors: mde ryandesign

repo: mde/jake


text:
importer: handle trailing slash in GOROOT&GOPATH

We also need handle trailing slash in GOROOT&GOPATH in cacheimporter.

Looks good, thanks for doing this!

authors: MoZhonghua stamblerre

repo: mdempsky/gocode


text:
Results display only once and clear when new search is made.

Results currently displaying repeatedly when search button is pushed. Previous search results are not being cleared.

Changed '+=' to '=' to correct results not clearing when new search is performed.


text:
Embedding subs sometimes fail error Application provided duration: XXX is invalid

Hello!
Im having some troubles with embedding subs, it is happening on multiple files and alot of them. When i disable the option to embed subtitles everything works as excpected. In the log output i have this:
Application provided duration: 14399999000 is invalid
av_interleaved_write_frame(): Invalid argument
As soon as i disable the embed-subs options the files that failed works as excpected.
cur_dts is invalid (this is harmless if it occurs once at the start per stream) cur_dts is invalid (this is harmless if it occurs once at the start per stream) cur_dts is invalid (this is harmless if it occurs once at the start per stream) cur_dts is invalid (this is harmless if it occurs once at the start per stream) cur_dts is invalid (this is harmless if it occurs once at the start per stream) cur_dts is invalid (this is harmless if it occurs once at the start per stream) [mp4 @ 0x56455a5813c0] Application provided duration: 14399999000 is invalid av_interleaved_write_frame(): Invalid argument No more output streams to write to, finishing. [mp4 @ 0x56455a5813c0] Application provided duration: 14399999000 is invalid Error writing trailer of /media/dl/XXXXXXXXXXXX.mp4: Invalid argument
Any ideas? I would like to keep embedded subs on if possible, this is not happening on everyfile but on many/multiple files a day.

I haven't been able to find a reliable fix for this. Its FFMPEG limited. The fix_sub_duration option is supposed to address this but appears to be broken

authors: izeen mdhiggins


text:
text direction tutorial

we need internationalization content on text direction
We should also consider tutorials on
character sets, units of measure (currency, °C/°F, km/miles, etc.), localized, time and date formats, keyboard layouts, text directions

@chrisdavidmills where would this live on the site. It's touched on in various layout guides (grid, flexbox etc.) and also logical properties and values.

@rachelandrew for the text direction stuff, I was thinking maybe add some content to https://developer.mozilla.org/en-US/docs/Learn/CSS/Building_blocks/Handling_different_text_directions ?
Or if it is likely to be an entire tutorial, maybe just put it under the main Web/CSS page?

authors: chrisdavidmills estelle rachelandrew

repo: mdn/sprints


text:
Remove all appropriate KS macro calls from our JavaScript documentation

Depends on https://github.com/mdn/sprints/issues/2520 and https://github.com/mdn/sprints/issues/2523
In https://github.com/mdn/sprints/issues/2520 we triage all the KS macro calls made from our JavaScript documentation. In https://github.com/mdn/sprints/issues/2523 we develop a tool that can selectively remove KumaScript macro calls.
In this story we run the tool over the KumaScript documentation, asking it to remove the macro calls that we triaged as "remove". We then have to review the documentation, to ensure nothing broke.
Acceptance criteria
Our JavaScript documentation no longer contains calls to any macros triaged as "remove".

I've removed all calls for the spec2 macro :tada:

Based on the latest triage list, we have these macros to remove:
Draft
non-standard_inline
Obsolete_inline
experimental_inline
deprecated_inline
Index
Not sure we can really remove Index yet :(.

-> https://github.com/mdn/sprints/issues/2785#issuecomment-598696606 means we can mark Index as removed.


text:
/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/find

Request type

[x ] Correction or update

Details
the formatting on the example is wrong

There is no margin between the line numbers and the content in the first example called JavaScript Demo: Array.find()

@peterbe @tobinmori @schalkneethling @wbamberg  FYI that this is still happening. I know that this is a known issue so I'll close it, but I wasn't sure where this is being tracked, so can you link it to the issue it is a dupe of? Thanks.

I have some mental plans how to fix it but none of them are low-hanging. I don't want to have to keep trying to patch bob any further. We
The best thing to do would be to rewrite it into Yari 2.

authors: SatheesA chrisdavidmills peterbe


text:
ios sim instructions

android works, and also ios.
so if you want to add the ios instructions for the simulator 👍
gogio -o saltyui.app -target ios .

# startup an IOS sim ( and wait for eternity )

xcrun simctl install booted saltyui.app

Fixed in commit 79338561, thanks :)

repo: mearaj/saltyui


text:
ik_smart扩展词典可以配置优先级吗

假如有“天下第一“,默认分出来是天下第一,是否可以配置分出“天下”和"第一"

使用ik max word分词

repo: medcl/elasticsearch-analysis-ik


text:
Error while setting up RTMP stream

RTMP stream is not being played and in the console, I see the error below:

yourside.live.cdn.bitgravity.com/yourside/live/feed_1800k?start=0:1 GET http://yourside.live.cdn.bitgravity.com/yourside/live/feed_1800k?start=0 net::ERR_EMPTY_RESPONSE

Please, can you tell me if the RTMP stream isn't configured correctly or some issue with mejs?
Thanks,
Himani

can you provide a live example?

Closing old issues. Feel free to re-open if needed.

authors: Himani3010 Qoraiche berryamin

repo: mediaelement/mediaelement


text:
Issue when changing sources in an ended event

Hello all,
We've been hitting a strange issue with the latest MediaElement.js (4.2.10) at https://github.com/airsonic/airsonic/pull/1080 that we can't seem to resolve, and we'd appreciate some help.
The following sequence of events seems to work for HTML5 MediaElement, but not with MediaElement.js. For me, this fails in Firefox (67/68) only, not on Chromium (75).

Set src, then call load() and play() for a first MP3 stream.
In the ended event handler, do the same for a second MP3 stream.

Step 2 appears to buffer the second stream correctly, but playback never starts, and the console shows AbortError: The fetching process for the media resource was aborted by the user agent at the user's request.:

I've managed to put together a short reproduction case at https://github.com/fxthomas/mediaelement-test-aborterror.

I think I've managed to track down the root cause of this issue. I updated the test repo with some more info about it!

I've dug a bit into it, and managed to track the introduction of that particular pause call back to 33080d6b5b563e4d9e7b78dc443ecb26c4f49a6d (yup, that's old). That does not tell me a lot, unfortunately...
It seems that calling pause() should be unnecessary when we're in the ended event (the stream should have already finished playing), but maybe I'm missing something.
Is it possibly needed by a renderer (in which case, which one?) or does it trigger UI updates (in which case, can we decouple them from calls to pause())?
I'll continue to dig, maybe I'll find something.

Any success with this one ?

Well, holidays prevented me from working on this, but I'm back :wink:
After doing some more investigation in the internals of the MEJS player, I found out that our (in Airsonic) initialization order was a bit unusual. In particular, we were adding events to the MEJS player before it was fully initialized, and our event handlers were carried over once MEJS had finished its full initialization.
I believe that https://github.com/airsonic/airsonic/pull/1254 fixes the issue completely on our side, and I'm not certain it should even be considered a bug on MEJS's part (since technically we were using it somewhat wrong).

It might be detecting added event handling during initialization to warn that something is wrong, or at least document it somewhere :)

Ok IIUC, there is no issue in MediaElement ... closing ..

authors: berryamin fxthomas jvoisin


text:
Script is unable to choose another planet

He loops on the first one and log

Leaving the planet, no zones left

@DylanDelobel are you using the headless or the browser variant of the script? Can you provide a log?

Was using the browser script
The planet was completed and until valve put a new planet the script was stuck in a loop
The page refreshed so i can't provide logs

authors: DylanDelobel EoD

repo: meepen/salien-bot


text:
[0.8.1] Spooler - Queued / executing jobs information

There is a paucity of information in the Spooler queued / executing jobs information regarding the size of the job(s).

As you can see in the above example the currently executing job shows the size of the job as (1191/1194) where the units are unspecified but are presumably cut-objects, but the queued job doesn't show any such information.
It would be useful to separate out this information to individual columns and to have additional information shown i.e. number of operations executed, saved/loaded filename, max passes, etc.).
Such information would ideally be shown in the history too.

This feels very open ended. The history stores a lot of history, and there's a lot of information to it. It's marked completed so I assume it is, but due to the open nature of the question it's not clear whether it actually was.

authors: Sophist-UK tatarize


text:
feat: Add HTTP Probe trace time metrics

the following tracing metrics have been added:

dns: get the ip address, from dnsStartAt() to  dnsDone()
conn: tcp connection,  from connectStart() to connectDone()
tls: tls connection, from tlsStart() to tlsDone()
send: send the http header, from wroteHeaderField() to wroteHeaders()
wait: send the http request, from wroteRequest() to gotFirstResponseByte()
transfer : wait all of data received, from gotFirstResponseByte() to putIdleConn()
total: from the beginning to the end. getConn() to putIdleConn()

total >= DNS + conn + tls + send + wait +transfer

it can be seen in Prometheus and Grafana, the following snapshot is an example.

open the debug log, you will see the following debug information
DEBU[2022-06-28T20:26:33+08:00] [http TRACE MegaEase] - total - start get connection: 1656419193697500000
DEBU[2022-06-28T20:26:33+08:00] [http TRACE MegaEase] - dns - start resolve megaease.com: 1656419193697806
DEBU[2022-06-28T20:26:33+08:00] [http TRACE MegaEase] - dns - resolve ip [{172.67.222.231 } {104.21.46.25 } {2606:4700:3033::6815:2e19 } {2606:4700:3033::ac43:dee7 }], time 67.725ms
DEBU[2022-06-28T20:26:33+08:00] [http TRACE MegaEase] - conn - start tcp connect to 172.67.222.231:443: 1656419193765629
DEBU[2022-06-28T20:26:33+08:00] [http TRACE MegaEase] - conn - tcp connection created to 172.67.222.231:443. time: 85.463ms
DEBU[2022-06-28T20:26:33+08:00] [http TRACE MegaEase] - tls - start negotiation: 1656419193851180
DEBU[2022-06-28T20:26:33+08:00] [http TRACE MegaEase] - tls - negotiated to "megaease.com", time: 96.888ms
DEBU[2022-06-28T20:26:33+08:00] [http TRACE MegaEase] - connection established. reused: false idle: false idle time: 0ms
DEBU[2022-06-28T20:26:33+08:00] [http TRACE MegaEase] - send - start write header field :authority [megaease.com] : 1656419193948308
DEBU[2022-06-28T20:26:33+08:00] [http TRACE MegaEase] - send - start write header field :method [GET] : 1656419193948308
DEBU[2022-06-28T20:26:33+08:00] [http TRACE MegaEase] - send - start write header field :path [/] : 1656419193948308
DEBU[2022-06-28T20:26:33+08:00] [http TRACE MegaEase] - send - start write header field :scheme [https] : 1656419193948308
DEBU[2022-06-28T20:26:33+08:00] [http TRACE MegaEase] - send - start write header field user-agent [MegaEase EaseProbe/v1.7.0] : 1656419193948308
DEBU[2022-06-28T20:26:33+08:00] [http TRACE MegaEase] - send - start write header field accept-encoding [gzip] : 1656419193948308
DEBU[2022-06-28T20:26:33+08:00] [http TRACE MegaEase] - send - headers written, time: 0.089ms
DEBU[2022-06-28T20:26:33+08:00] [http TRACE MegaEase] - wait - start write request: 1656419193948405
DEBU[2022-06-28T20:26:34+08:00] [http TRACE MegaEase] - transfer - start transfer the response: 1656419194738504
DEBU[2022-06-28T20:26:34+08:00] [http TRACE MegaEase] - wait - got first response byte, time: 790.082ms
DEBU[2022-06-28T20:26:34+08:00] [http TRACE MegaEase] - transfer - done, time: 0.085ms
DEBU[2022-06-28T20:26:34+08:00] [http TRACE MegaEase] - total - done , time: 1041.068ms
DEBU[2022-06-28T20:26:34+08:00] [http TRACE MegaEase] ======================== Trace Stats ======================
DEBU[2022-06-28T20:26:34+08:00] [http TRACE MegaEase] DNS       Connect TLS     Send    Wait    Trans   Total
DEBU[2022-06-28T20:26:34+08:00] [http TRACE MegaEase] 67.73     85.46   96.89   0.09    790.08  0.09    1041.07
DEBU[2022-06-28T20:26:34+08:00] [http TRACE MegaEase] ===========================================================

Codecov Report

Merging #150 (af815e8) into main (2f049ee) will increase coverage by 0.65%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #150      +/-   ##
==========================================
+ Coverage   90.92%   91.57%   +0.65%
==========================================
  Files          44       43       -1
  Lines        3020     3182     +162
==========================================
+ Hits         2746     2914     +168
+ Misses        203      199       -4
+ Partials       71       69       -2

Impacted Files
Coverage Δ

global/global.go
100.00% <ø> (ø)

probe/http/http.go
100.00% <100.00%> (ø)

probe/http/metrics.go
100.00% <100.00%> (ø)

probe/http/trace.go
100.00% <100.00%> (ø)

daemon/daemon_unix.go

daemon/daemon_windows.go

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 2f049ee...af815e8. Read the comment docs.

authors: codecov-commenter haoel

repo: megaease/easeprobe


text:
Unify project name as MeiliSearch in comments

Hello.
I've found that usage of 'Meilisearch' and 'MeiliSearch' are mixed in this project. Seems official naming are 'MeiliSearch', so I updated the comments.
Please look on 🙏

bors merge

bors merge

bors merge

bors merge

bors merge

bors merge

authors: bidoubiwa djKooks eskombro

repo: meilisearch/meilisearch-java


text:
Update version for the next release (v0.5.2)

🚀 Enhancements

Remove duplicated gem versions from the gemspec/Gemfile (#149) @brunoocasali
Update sidekiq worker to job in readme (#137) @jmarsh24

🐛 Bug Fixes

Fix rubocop unintentional CI error (#144) @brunoocasali

Thanks again to  @brunoocasali, @curquiza, @jmarsh24 ! 🎉

bors merge

repo: meilisearch/meilisearch-rails


text:
Only some records are indexed when importing hight volume to vectorize

Describe the bug
When importing data into Meilisearch, only 300,000 to 700,000 records are indexed, despite having 8 million products in total.
To Reproduce

Use the provided code to import products from a Prisma database into Meilisearch.
Start the import script.
Observe that the import stops after 300k to 700k records, even after a prolonged period.

Expected behavior
All 8 million products should be imported and indexed into Meilisearch without prematurely stopping.
Screenshots
If applicable, add screenshots or logs showing the number of records fetched and imported.
Meilisearch version
[v1.11.0], but happening also on previous versions
Additional context

Architecture: Fly io machine 4 CPUs, 8GB RAM
Device: Remote server
OS: Ubuntu 20.04
Browser: Not applicable

Meilisearch Settings
Tried also with MEILI_EXPERIMENTAL_REDUCE_INDEXING_MEMORY_USAGE= 'true"
export const meilisearchProductsIndexSettings: Settings = {
  stopWords: spa,
  sortableAttributes: ['id', 'offers.price', 'ratingsAverage', 'ratingsCount', 'createdAt'],
  embedders: {
    default: {
      source: 'huggingFace',
      model: 'sentence-transformers/paraphrase-multilingual-MiniLM-L12-v2',
      documentTemplate: '{{doc.name}}',
      binaryQuantized: true,
    },
  },
  searchableAttributes: [
    'name',
    'brand.name',
    'model.name',
    'line.name',
    'categories.name',
    'hierarchicalCategories',
    'keywords',
    'offers.shop.name',
  ],
  filterableAttributes: [
    'hierarchicalCategories',
    'categories',
    'brand',
    'offers.price',
    'offers.shop',
    'ratingsAverage',
    'ratingsCount',
    'offersCount',
  ],
}

Code Snippet
import { prisma } from '@/db.server'
import { fullProductSelect } from '@/modules/product/product.service.server'
import {
  meilisearchProductsIndex,
  fullProductToMeiliSearchProduct,
  createMeilisearchProductsIndex,
} from '@/utils/meilisearch'
import pMap from 'p-map'
import pRetry from 'p-retry'

const importProductsToMeilisearch = async () => {
  const lastImportedProduct = await meilisearchProductsIndex
    .search('', {
      limit: 1,
      sort: ['id:desc'],
    })
    .catch((err) => null)
    .then((res) => res?.hits?.[0])

  let currentCursor = 0
  const numPerPage = 1000

  while (true) {
    const products = await pRetry(() =>
      prisma.product.findMany({
        take: numPerPage,
        ...(currentCursor && { cursor: { id: currentCursor } }),
        skip: currentCursor ? 1 : 0,
        select: fullProductSelect,
      }),
    )

    if (!products.length) break

    currentCursor = products[products.length - 1].id

    const newMeiliSearchProducts = await pMap(products, fullProductToMeiliSearchProduct)

    await pRetry(() => meilisearchProductsIndex.updateDocumentsInBatches(newMeiliSearchProducts))
  }
}

importProductsToMeilisearch()

Hello @anaibol 👋
Thank you for the report. I will list all the reasons why it could fail that way.

Do you have any information about the tasks in the queue?

curl 'http://localhost:7700/tasks?statuses=failed'

Did you compile Meilisearch with GPU support? It doesn't seem you did. I hope you have a GPU on your machine 😬

I recommend using a third-party API like Ollama (which you can install on your machine) or OpenAI for that many documents. The huggingFace option will compute the embeddings locally, and it's not efficient at all on a non-GPU machine.
Have a nice day 🏞

Hello @anaibol 👋
Thank you for the report. I will list all the reasons why it could fail that way.

Do you have any information about the tasks in the queue?

curl 'http://localhost:7700/tasks?statuses=failed'

Did you compile Meilisearch with GPU support? It doesn't seem you did. I hope you have a GPU on your machine 😬

I recommend using a third-party API like Ollama (which you can install on another GPU machine) or OpenAI for that many documents. The huggingFace option will compute the embeddings locally, and it's not efficient at all on a non-GPU machine.
Have a nice day 🏞

Hello! Since I have a lot of records to vectorize and I have the time to do it on background, no worries if it takes hours or days, I am running it on the CPU. Moving to GPU or an external service would be much expensive. Before moving to meilisearch I was using typesense, which handled great the vectors computation on the CPU, so I think it's an issue with the queueu and jobs management.
I see there is an issue with storage
, but the fly.io vm has plenty of free storage.
![Screenshot 2024-10-30 at 7 16 17 PM](https://gith

ub.com/user-attachments/assets/ccadd3ef-ded4-45f3-b673-744b47902885)

Hey @anaibol 👋
Thank you for the report. It seems that you are indeed out of disk space, but it's nearly expected. When Meilisearch is indexing, it writes a lot of temporary files. Those files are stored in the $TMP_DIR folder, which, most of the time, is not on the main disk. That's why you see plenty of unused space.
What I can recommend is to:

Create a tmp folder at the root of your main disk and change the $TMP_DIR folder to point to this one. Meilisearch MUST be aware of this environment variable (specify it correctly and reboot it). You should see an increase in disk usage when Meilisearch is indexing. We are working on drastically reducing the disk usage when indexing.
Reduce the number of batched tasks. Meilisearch tries to batch all the enqueued tasks by default. On the cloud, we use different techniques to manage that correctly. But when managing it yourself, you need to specify this limit yourself. Too many processing tasks can result in too much content written to disk.

Have a nice day 🎃

Hey @anaibol 👋
Thank you for the report. It seems that you are indeed out of disk space, but it's nearly expected. When Meilisearch is indexing, it writes a lot of temporary files. Those files are stored in the $TMP_DIR folder, which, most of the time, is not on the main disk. That's why you see plenty of unused space.
What I can recommend is to:

Create a tmp folder at the root of your main disk and change the $TMP_DIR folder to point to this one. Meilisearch MUST be aware of this environment variable (specify it correctly and reboot it). You should see an increase in disk usage when Meilisearch is indexing. We are working on drastically reducing the disk usage when indexing.
Reduce the number of batched tasks. Meilisearch tries to batch all the enqueued tasks by default. On the cloud, we use different techniques to manage that correctly. But when managing it yourself, you need to specify this limit yourself. Too many processing tasks can result in too much content written to disk.

Have a nice day 🎃

cool! that worked. I really appreciate your help and I love the product you are building!!!

authors: Kerollmops anaibol

repo: meilisearch/meilisearch


text:
异步渲染复制的BUG

异步渲染时，attributedText为nil，不能复制。

@lujun5678275 有 DEMO 吗？如果你使用的是 textRenderer 那么应当从 textRenderer 取值。

repo: meitu/MPITextKit


text:
changed test imports

✅ Closes: #380

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

authors: CrisGrud melfore-devops

repo: melfore/mosaic


text:
JobLog log UI fix and isUITrigger() 'trigger' of null" TypeError

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/1809
Originally created by @derek-knox on 2020-02-26 21:52:02

View 5 previous comments from the original issue on GitLab

repo: meltano/meltano


text:
Release v1.95.0

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/3214
Originally created by @aaronsteers on 2022-02-04 18:38:30

Evergreen Releases - Prep Steps:
An Evergreen release process means we are always releasing. We open a new release ticket as soon as we've completed the prior release. (It's therefore the final step in this checklist.)
"Evergreen Prep" Checklist

[x] Open this Issue
[x] Indicate the version to be released here in the issue's title Release vX.Y.Z

If the release number changes (from minor to major or patch, for instance), update the version here and in the issue description.

Readiness Checklist:
Engineering team, to get ready for the upcoming release:

[x] Ensure any already-merged commits since the last release have Changelog entries (excepting non-user-impacting commits, such as docs fixes).
[x] Create a comment in the #engineering-team slack channel with pending-but-not-merged MRs, potentially shipping. (Aka, the "burndown" list.)

Otherwise a comment that all known merge candidates are already merged.

[x] Create or link to a summary of MRs merged and/or expected in the #marketing Slack channel, with an @channel mention.

Release Checklist
Rotating assignee, on the morning of the release:

[x] Changelog updates and version bump:

[x] Check the pending MRs to make sure nothing expected is still waiting to be merged.
[x] Create a new branch named release/vX.Y.Z and a corresponding MR with the Release MR template.
An automated pipeline (linked to the branch prefix release/v*) will
immediately and automatically bump the version and flush the changelog.

[x] Check this box to confirm the automated changelog flush and version bump are correct.
You do not need to wait for the CI pipeline. (An identical CI pipeline is already included in the below.)

[x] Cut a release tag from your release/vX.Y.Z branch (not from main) named vX.Y.Z with Message=Release vX.Y.Z

In response to new tag creation, these steps are performed automatically in Gitlab pipelines:

Abort if tag vX.Y.Z does not match output from poetry version --short
Test everything.
Publish to PyPi .

Validate publish once the pipeline finishes. (While the process is running, you can continue with next steps, such as changelog grooming.)

[x] Check this box when the tag's pipeline has completed (eta 40-60 minutes).
[x] Check this box when PyPi publish is confirmed.

Groom the changelog:

[x] Compare the Changelog against the main branch commit history and add any significant user-impacting updates (excluding docs and website updates, for instance).
[x] Review the Changelog for readability and typoes, committing fixes or updates if needed.
[ ] Final changelog review:

Open the Changelog in preview mode, mouse over each link and ensure tooltip descriptions match the resolved issue.
Check contributor profile links to make sure they are correct.

[x] Merge the resulting MR to main with the merge commit message Release vX.Y.Z
[x] Open the next Release issue using the Release template.

Announcements, Marketing, and Promotion
Marketing or Product team:

[ ] Post-release announcement steps:

[x] Post announcement to Meltano slack: #announcements

Copy-paste to:

[x] Singer slack: #meltano
[x] dbt slack: #tools-meltano

[ ] Blog post
[ ] Tweet the blog post

View 30 previous comments from the original issue on GitLab


text:
bug: Table of content links do not scroll page to selected entry

Meltano Version
NA
Python Version
NA
Bug scope
Other
Operating System
Tested with Firefox and Chrome
Description
Going to https://docs.meltano.com/reference/glossary#singer should result in the page being scrolled down till the "Singer" entry is at the top of the page. Once that page is open, clicking links in the table of contents on the right should result in the page being scrolled up/down, but instead nothing happens.
Code
No response

@afolson can you look at this? I can confirm that it doesn't jump to it, but it works for other pages.

I thought this was a quick fix, but there is some jekyll magic at work here I can't see through at the moment. My fix doesn't fix: https://github.com/meltano/meltano/pull/7274.

should now work and be closed!

authors: WillDaSilva sbalnojan tayloramurphy


text:
feat(taps): Support declaring arbitrary SQLAlchemy type instances in SQL tap schemas

Feature scope
Tap/target metadata.
Description
Related to the original Singer spec's sql-datatype (see https://github.com/meltano/sdk/issues/1323, https://github.com/meltano/sdk/issues/1903), this new metadata object would work in an analogous manner to Python's logging module capability for importing and instantiating arbitrary callables and classes.
The story, specifically for vector/embedding fields for LLMs, would go something like:

As a user, I know that one or more fields in a stream represent a vector. For example, {"id": 1, "my_vector": [1, 2, 3]}.

I would like to use MeltanoLabs/target-postgres alongside pgvector/pgvector-python to declare the SQLAlchemy type of my_vector: pgvector.sqlalchemy.Vector

I would like not to only declare the type but also any arbitrary parameteres for it, like length, dimension, etc.:
# catalog metadata in Meltano syntax
schema:
  my_stream:
    my_vector:
      sqlalchemy_type:
        (): "pgvector.sqlalchemy.Vector"
        dim: 3

This would trigger the SDK to import pgvector.sqlalchemy.Vector and instantiate it as Vector(dim=3).

The other requirement is that the user installs pgvector-python in the same virtual environment as target-postgres, which could be achieved with package extras, e.g. target-postgres[vector] or by documenting known postgres SQLAlchemy extensions in the target's readme.

Potential issues
The biggest problem I can think off is figuring out the priority with which this type override is considered. For example, in target-postgres:

a few JSON schema types are mapped first to postgres-specific column types, e.g. `int -> BIGINT
then the SDK defaults are used

But by introducing this feature, we'd expect targets to resolve in the following order:

sqlalchemy_type overrides
custom target implementation overrides
SDK defaults

Dear Edgar,
thank you for converging this from https://github.com/MeltanoLabs/target-pinecone/issues/20 so quickly. Is GH-1872 actually already setting the stage for your proposal, or is it something different?
With kind regards,
Andreas.

authors: amotl edgarrmondragon

repo: meltano/sdk


text:
Is this repo active?

I have to do a lot of client side image manipulations. Is this library still active and can it be used in production? Are there any recent alternatives?

The current master branch is unlikely to change for awhile, but I have been trying to find time to work on the more experimental cleanup branch, which contains a lot of backwards incompatible changes. I'm also exploring implementing WebWorkers again since the last time I implemented them, browsers didn't support cool stuff like transferring data ownership or passing UInt8Arrays without serialization (it was strings only).
The current master branch is suitable for production use.

repo: meltingice/CamanJS


text:
Fixed import for EmbeddingBase class for ollama and huggingface embedders

Description
Fixed import for EmbeddingBase class for ollama and huggingface embedders.
Fixes #1544
Type of change
Please delete options that are not relevant.

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

Checklist:

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

Maintainer Checklist

[ ] closes #xxxx (Replace xxxx with the GitHub issue number)
[ ] Made sure Checks passed

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

This looks good, thanks @kmitul.

authors: CLAassistant Dev-Khant kmitul


text:
🛑 Kérwá is down

In 43994ba, Kérwá (https://kerwa.ucr.ac.cr) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Kérwá is back up in 26bba08 after 47 minutes.

repo: memoemg/howyoudoing


text:
🛑 Kérwá is down

In 32ed64f, Kérwá (https://kerwa.ucr.ac.cr) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Kérwá is back up in 9d59b21 after 24 minutes.


text:
docs: adds troubleshoot guidance for delta issues

Includes several places where you can take a look if there is any issue with the delta updates feature
Changelog: None
Ticket: None
Signed-off-by: Luis Ramirez Vargas luis.ramirez@northern.tech
External Contributor Checklist

🚨 Please review the guidelines for contributing to this repository.

[ ] Make sure that all commits follow the conventional commit specification for the Mender project.

The majority of our contributions are fixes, which means your commit should have
the form below:
fix: <SHORT DESCRIPTION OF FIX>

<OPTIONAL LONGER DESCRIPTION>

Changelog: <USER-FRIENDLY-CHANGE-DESCRIPTION> or <None>
Ticket: <TICKET NUMBER> or <None>

[ ] Make sure that all commits are signed with git --signoff. Also note that the signoff author must match the author of the commit.

Description
Please describe your pull request.
Thank you!

@MuchoLucho  Seems like you made a branch directly in the repo instead of your fork. Not much difference practically but was sure this wasn't allowed.
@lluiscampos Don't have much opinion on this, do comment if this needs to come from a fork instead.

Merged the new information as well as old comments in. Thoughts @TheMeaningfulEngineer @MuchoLucho ?

repo: mendersoftware/mender-docs


text:
[meom code clinic] tests

This issue is open for the MEOM internal code clinic / review process

tests

[ ] The package has tests:

[ ] Tests cover essential functions of the package and a reasonable range of inputs and conditions.

[ ] Continuous Integration: Has continuous integration setup (We suggest using Github actions but any CI platform is acceptable for review)

See issues #79

Now closing code review.

authors: lesommer rcaneill

repo: meom-group/jaxparrow


text:
Broken documentation link

Tipo de componente utilizado
Broken link
Comportamiento Esperado
View advanced documentation in http://mercadopago.github.io/px-ios/v4/
Comportamiento Actual
http://mercadopago.github.io/px-ios/v4/

Are there any updates on this being fixed? Us developers need to access the documentation to make good implementations.
Hay alguna novedad sobre este problema? Los desarrolladores necesitamos acceso a la documentación para poder implementar el SDK correctamente.

authors: adrianosouzacostacr tomassasovsky

repo: mercadopago/px-ios


text:
Update uri

Cambios introducidos :

Se cambia la uri de Tracking para tomar beta o v1 segun corresponda
Se apaga Tracking

Revisión

[ ] Todos los textos se encuentran localizables
[ ] No se introducen warnings al proyecto
[ ] Se incluyen cambios de UX ? se verificó que se vean bien tanto en iPhone SE y S6 : NA
[ ] No se agregan logs / prints innecesarios
[ ] No se agregan comentarios basura
[ ] Correr Swiftlint

Testeo

[ ] Testeado en BETA con emulador
[ ] Testeado en BETA con dispositivo
[ ] Test unitarios OK
[ ] Test funcionales OK
[ ] Documentación actualizada

Codecov Report

Merging #1126 into development will decrease coverage by 0.61%.
The diff coverage is n/a.

@@               Coverage Diff               @@
##           development    #1126      +/-   ##
===============================================
- Coverage        57.89%   57.28%   -0.62%
===============================================
  Files              259      259
  Lines            20296    20296
===============================================
- Hits             11750    11626     -124
- Misses            8546     8670     +124

Impacted Files
Coverage Δ

...cadoPagoSDK/MercadoPagoSDK/ServicePreference.swift
65.26% <ø> (ø)
:arrow_up:

...adoPagoSDK/MercadoPagoSDK/Tracker/MPXTracker.swift
69.23% <ø> (-12.83%)
:arrow_down:

...K/MercadoPagoSDK/Tracker/TrackStorageManager.swift
0% <0%> (-57.84%)
:arrow_down:

...rcadoPagoSDK/MercadoPagoSDK/Tracker/MPXReach.swift
0% <0%> (-52.28%)
:arrow_down:

...agoSDK/MercadoPagoSDK/Tracker/MPTFingerPrint.swift
44.61% <0%> (-44.62%)
:arrow_down:

...oSDK/MercadoPagoSDK/Tracker/TrackingStrategy.swift
0% <0%> (-16.67%)
:arrow_down:

MercadoPagoSDK/MercadoPagoSDK/JSONHandler.swift
62.31% <0%> (-5.8%)
:arrow_down:

authors: codecov-io demtej


text:
would like to have RawVal to support adding comments as well

I see the ctyHandler be able to handle comment https://github.com/mercari/hcledit/blob/main/internal/handler/cty.go#L20
we'd like RawHandler for RawVal be able to accept comment as well https://github.com/mercari/hcledit/blob/main/internal/handler/raw.go#L21
thanks
i can contribute as well if approved

Sure! Happy to review a pull request for this. Please just request review from me or the other code owners on the PR.

@ryan-ph a quick update here https://github.com/mercari/hcledit/pull/127/files

Thanks for the contribution @piggybankwang!

authors: piggybankwang ryan-ph

repo: mercari/hcledit


text:
allow fastify v5

Looks like fastify and fastify-plugin v5 versions are already being used. Is it possible to allow fastify  v5 instead of 4.x to prevent unexpected fastify version error.

I have the same issue when trying to update to Fastify v5.
cc: @mcollina
FastifyError [FST_ERR_PLUGIN_VERSION_MISMATCH]: fastify-plugin: index-auto-1 - expected '4.x' fastify version, '5.0.0' is installed

Would you like to send a PR?

Would you like to send a PR?

Yeah I can do that.

Thanks

Shipped a release

authors: jimmy-guzman luthfi-hh mcollina

repo: mercurius-js/cache


text:
Roborock S50

Device model
roborock.vacuum.s5
Device name
Roborock S50, S51, S55 (White, Gold, Black)
Does the device require a MiCloud connection?
Yes
Anything special about the device?
Device works actually, but plugin says :
[miot] [Roborock S55] Device services:
"vacuum",
"battery",
"identify"
[miot] [Roborock S55] Initializing device properties
[miot] [Roborock S55] Device properties:
"vacuum:status",
"vacuum:mode",
"battery:battery-level",
"battery:charging-state"
[miot] [Roborock S55] Initializing device actions
[miot] [Roborock S55] Device actions:
"vacuum:start-sweep",
"vacuum:stop-sweeping",
"battery:start-charge",
"identify:identify"
And then :
[miot] [Roborock S55] =AB= Action vacuum:start-room-sweep does not exist on this device. Skipping action button!
But Roborock S55 do have room cleaning, please update it 👍

According to the spec found here: http://www.merdok.org/miotspec/
there is no start-room-sweep action in the miot protocol for this device.

There is no way to add it? In another plug-in I can select room cleaning.
https://github.com/homebridge-xiaomi-roborock-vacuum/homebridge-xiaomi-roborock-vacuum

The other plugin uses the old miio protocol. This plugin uses the new miot protocol and old devices that natively does not support it have limited functionality hence it is missing for your device.

Ok I will keep with the other plug-in

authors: Marrand merdok

repo: merdok/homebridge-miot


text:
Adding your library to apollo docs community integrations?

Hello!
I'm the Staff Product Manager for Apollo Client 👋
I'm really excited you created this library for Apollo + Solid.js. I'm really liking the approach Solid.js is taking and curious if it will gain popularity. Would you be interested in adding your library to our Community Integration section on our web client's main docs page:
https://www.apollographql.com/docs/react/
We accept PRs to our documentation site. 😄
docs filehttps://github.com/apollographql/apollo-client/edit/main/docs/source/index.mdx
As a caveat: If you do add it, it may drive a lot of interest to your project, so if you feel it's not in a stable release state, adding it may not be something you are interested in at the moment, so just let us know!
Thanks for the consideration!

@Torsten85 👋 I was just following up on this question. Just let me know what you think! I'd love to let users of Apollo Client know about this repository.

Hi @jpvajda and sorry for the late reply.
I would love to see this library added to the community integrations! Of course I cannot guaranteed that this is 100% stable (as I do this in my spare time) but I'm using it for quite a while now and didn't encountered any issues.

@Torsten85 I've added a reference to your library, feel free to close this issue now. Thanks again!

Thanks!

repo: merged-js/solid-apollo


text:
Leadtime

New configuration schema to describe type and status conversion between raw and standard.
Each type of issue may have different set of statuses representing Resolved or Rejected, so
in new schema, status-mapping are nested within type-mapping. User can choose to map one or
more JIRA types to a single standard type, same logic for status conversion.
Calculates Lead-Time for those Resolved issues only.

Some notes for future work:

We need more documentation for configuration as some mappings are not self-explanatory.
We need to verify that grafana dashboards are still working.

LGTM

repo: merico-dev/lake


text:
Windows native compatibility for make file

Current Behavior
Currently, the make files are not Windows-compatible, and make commands cannot run on Windows power shell or CMD. It can only run via the bash terminal.
Desired Behavior
The make file will be Windows native compatible so that they can be executed via Windows power shell or CMD.
Implementation

Acceptance Tests

Mockups

Contributor Guides and Handbook

🛠 Meshery Build & Release Strategy
📚 Instructions for contributing to documentation

Meshery documentation site and source

🎨 Wireframes and designs for Meshery UI in Figma
🙋🏾🙋🏼 Questions: Discussion Forum and Community Slack

/assign

repo: meshery/meshery


text:
added Designs docs

Notes for Reviewers
This PR fixes #
Signed commits

[ ] Yes, I signed my commits.

🚀 Preview for commit 45f15112413e790f3f8a0a6b943abe6acd1a374c at: https://64c9d401f095665acfe480f9--meshery-docs-preview.netlify.app


text:
DOC: update readme

Remove badges: the README is used an description for the sdist and the wheel. Having the badges pointing to the status of the main branch on the PyPI page for specific releases is not very consistent. Furthermore loading external resources from the documentation is an issue for distributions, which for privacy reasons need to patch the resources out.
Remove link to contributing documentation page: linking to a page that has only a TODO entry does not look very nice.
Reword and add some more details for the use cases target by meson-python.

GitHub is back to normal, apparently. PR is updated.

The check-boxes were not removed in this PR. They were removed a while ago during the big documentation refactoring.

repo: mesonbuild/meson-python