AQL: RANGE() function rounds start and stop values down to integer

Noted by Karsten Gerber in Community Slack:
Component, Query & Data
Affected feature:
AQL
AQL query (if applicable):
RETURN RANGE(1.5, 2.5)

AQL explain (if applicable):
Query String:
 RETURN RANGE(1.5, 2.5)

Execution plan:
 Id   NodeType          Est.   Comment
  1   SingletonNode        1   * ROOT
  2   CalculationNode      1     - LET #0 = [ 1, 2 ]   /* json expression */   /* const assignment */
  3   ReturnNode           1     - RETURN #0

Indexes used:
 none

Optimization rules applied:
 none

Steps to reproduce

Explain or run the query RETURN RANGE( 1.5, 2.5 )
In the execution this is already changed to [1, 2] and hence also the result of the query
As per the documentation, one would expect that the default step size of 1.0 is used, and thus [1.5, 2.5] as result.
Note that if you set the step size explicitly like RETURN RANGE( 1.5, 2.5, 1.0 ), then the execution plan / result is as expected

Problem:
It is unexpected that a default step size of 1.0 is different to a user-defined step size of 1.0 in the execution plan and query result.
Expected result:
[ 1.5, 2.5 ] (or the documentation needs to be changed to reflect what will actually happen)

Ranges are internally presented using two integer bounds.
That means the lower and upper bound parameters will also be converted into integers.
The documentation has examples where this is different - I guess it is from an older version of ArangoDB when there, for technical reasons, always were two implementations of some AQL functions. The AQL RANGE function implemented in JavaScript actually didn't convert the input parameters to integers, so it behaved as stated in the documentation. However, the C++-based implementation always used integers, and as part of a cleanup we removed all redundant implementations of AQL functions in 3.3 and 3.4. Final result: we only got the C++-based variant left, and this uses two integers internally. We should adjust the documentation so it reflects the current behavior.

@jsteemann Do I understand correctly, that even if you supply 1.0 as step size, then the bounds are still integers internally, but you get floating point numbers as result? Or does the presence of the third argument use a different code path which uses floats (or rather doubles) for everything?

@jsteemann ping

Resolved by https://github.com/arangodb/arangodb/pull/8299


Nfs volume

This implements the same as https://github.com/hyperhq/hyperstart/pull/248 but works with latest master instead.

@laijs updated.

LGTM
@gnawux  @gao-feng  could you also review it?

LGTM, and where is the mount.nfs comes from?

mount.nfs was built from nfs-utils(http://git.linux-nfs.org/?p=steved/nfs-utils.git;a=summary) tag nfs-utils-1-3-4

retest this please @hykins

LGTM


Debug Target drop-down too narrow

VSCode Version: 1.2.1
OS Version: Windows 10 14380

Steps to Reproduce:

Open .NET Core project
Hit View | Debug

Cannot see the full target name in the debug target drop-down:

Debug target field should be widened so the full debug target name can be displayed.

This is a designed as the debug target drop down changes size corresponding to the viewlet
This was initiated by this user request #3027
Closing as designed

@sisdorn - thanks for this info: However, to be fair, #3027 was referring to the fact that the play button got hidden - it was not asking to make the width of the debug target drop-down dependent on the width of the left-hand column.
I do not think that I should have to sacrifice a significant amount of my available screen real-estate to the left hand column just to be able to read the name of the currently selected debug target.

@bitcrazed fair enough, reopening

@isidorn Many thanks. Obviously not a Pri0, but it'd be a nice fix next time someone revisits that area of code 😉


get starting madmax but windows is Chia.exe stop? Why?

When I run chia exe, I get an error that windows has stopped.
Has anyone encountered the issue? thanks.

PermissionError: [WinError 5] Erişim engellendi
[3084] Failed to execute script chia


unnecessary boolean literals

What issue does this PR address?
Avoid unnecessary boolean literals true and false in comparisons (ie if there is no nullable involved).
Shorter Code, IMHO often more readable like !valid instead of valid == false
Does this PR introduce a breaking change?
No.
Please check if the PR fulfills these requirements

[X] The commit follows our guidelines
[ ] Unit Tests for the changes have been added (for bug fixes / features)

Other information:
Got complains from Sonarqube in the Quickstart part

IMHO often more readable like !valid instead of valid == false

This sort of shows that it's an opinion.

Got complains from Sonarqube in the Quickstart part

No idea what that is.
Can you explain what a real benefit from this PR is? Given that this doesn't really change any logic, this seems like a purely stylistic PR.


Use  unicode to know if Python 2 or 3

This passes linter tests like flake8

This is undesirable for a few reasons:

This project doesn't use Flake8, so its "linter tests" aren't important
This assigns unicode to str and then str to bytes which means that isinstance(bytes(), unicode) will be True.
The existing code is more readable.
If the project were to update this, it would be better to rely on six.


Arbitrary Command Injection

Affected versions of this package are vulnerable to Arbitrary Command Injection. An attacker could inject arbitrary shell commands if the user input can influence the iface argument.
https://snyk.io/vuln/npm:macaddress:20180511

https://nodesecurity.io/advisories/654
https://hackerone.com/reports/319467

not sure but var iface = os.NetworkInterfaces() index.js is the one that is used, not lib/xxx. the lib/xxx is used by the library itself which is in index.js

iface is passed as a first parameter to the '.one' method in the public API.
And is not sanitized in linux/unix/macos implementations.
Only windows one is safe, since does not pass it to the syscalls.

@zhaparoff (I have no idea what iface is or what it is for.) Are you saying I don't need to worry if I have a Windows machine?

Just got this as output when installing my dependencies. Maybe flooding the issue, but I think more cases are always welcome.
https://go.npm.me/audit-guide
https://nodesecurity.io/advisories/654

create-react-app built projects are also infected.

Hey everyone, I opened a pull request #18 to resolve this.  It is my understanding that by using execFile instead of exec you avoid command injection because the arguments are not run in a shell environment.  I'd love some input on this though.

CC: @Logikgate Awesome!! Thank you!
Here is another reference:
https://nodejs.org/api/child_process.html#child_process_child_process_execfile_file_args_options_callback
Thanks again

Looks like the maintainer(s) of this project haven't pushed a single commit since 3 years or even be active in the issues/PR lately.
It doesn't seem like a good omen for the projects who are using it.
Any alternative in mind?

@jourdanrodrigues Email sent

@Logikgate I just tried using your suggestion but i got this error:
warning Resolution field "macaddress-secure^0.2.11" has an invalid version entry and maybe ignored

NPM's support team is very responsive for issues like this; I'm guessing that if @scravy doesn't respond soon, they'll happily add anyone here as a collaborator to the original package given the large number of dependencies.

Only @scravy can add collaborators to this repo. What npm can do is to attribute the name of the package to someone else.

@KeitIG agreed; I'm just saying that instead of trying to get hundreds of dependents to move npm packages, we should try to get NPM to add @Logikgate or @theotix as collaborators to the npm package, so they can publish a fix to the original package.

@transitive-bullshit, wouldn't the admin action need to be here on github and on npm allowing @Logikgate to publish a fixed package? Or are you saying only NPM that would allow @Logikgate to take over the npm package name macaddress?

@epet the latter

I accepted pull #20 and released version 0.2.9.
Thank you all for having an eye on this package.


API change for Latency to milliseconds from secs

Update Latency in API response to be milliseconds (i.e. * 1000), rather than seconds.
Might be easier at millisecond level just to round to nearest integer as none of this is sensitive to half a ms difference anyway.

fixed by #49


Remove Configuration Best Practices Topic

This is a...

[x ] Feature Request
[ ] Bug Report

Study this topic: Configuration Best Practices. Verify that the content in this topic is covered elsewhere, and then delete this topic. If you find content that is not covered elsewhere, put that content into one or more existing topics.

@steveperry-53 Personally I view this page valuable.


Web UI MVP

Web UI Minimum Viable Product.
See #7

[x] Main VueJs setup
[x] Lucid API wrapper with auth token support
[ ] Register auth token
[ ] Application logic PoC
[ ] Implement Template

Related to https://github.com/nickel-org/nickel.rs/issues/441 to embed web-ui in the binary.

Reopening.


Automated cherry pick of #2801: fix: api gateway logout handler error and fix go fmt issues

Cherry pick of #2801 on release/2.12.
#2801: fix: api gateway logout handler error and fix go fmt issues

Codecov Report

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

@@              Coverage Diff               @@
##             release/2.12   #2803   +/-   ##
==============================================
  Coverage                ?   7.18%
==============================================
  Files                   ?     474
  Lines                   ?   74967
  Branches                ?       0
==============================================
  Hits                    ?    5388
  Misses                  ?   69127
  Partials                ?     452

Flag
Coverage Δ

#aFlag
7.18% <ø> (?)

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 257816d...fd1a7a2. Read the comment docs.

/lgtm

/approve

/lgtm


Remove AppContext.SetSwitch(...)

Currently, there is a bug in HttpClient which causes it to hang indefinitely and never finish when it could not create SSL/TLS secure channel.
A temporary workaround was used:
AppContext.SetSwitch("System.Net.Http.UseSocketsHttpHandler", false);
The above code should be removed when future versions of .NET Core are released.

.Net Core 3.0 was released and AppContext.SetSwitch(...) was removed from code


Adds documentation about new asm_sym feature

This commit adds documentation and fixes tests for the new asm_sym
feature, which gates symbol operands in inline assembly. These operands
are integral to this crate's implementation on macOS. Since we're using
a nightly toolchain, this is a breaking change, and there's no way to
build usdt or downstream crates that compile both before and after the
addition of this feature. The documentation describes this clearly, and
provides the feature flags needed on either side of this divide.
The tests have also been updated with the feature flag, as they run on
the latest nightly.

This will address #41 when merged.


[InputData] Support texts as InputData

Impement experimental pipeline with simple NLP-model (or even NaiveBayesClassifier) for text classification/sentiment analysis:

New InputData format with generator-based logic (for texts batch-loading)
New simple model (for instance, CNN) or adoptation the existing models that are suitable for text classification
Maybe bag-of-words, word-2-vec model, etc. for text embeddings
Several text preprocessing methods (stemming, lemmatization, filtering, etc.)
Example of dataset where pipeline can be applied (spam classification for instance as the simpliest case)
Example of FEDOT pipeline that can solve the given task

FYI tutorial for AutoNLP
https://www.youtube.com/watch?v=D-taRpi4OJk&ab_channel=AIEngineering


Types marked with @internal are excluded from typings, but still imported

Latest contains the following in container-instance:

import { ServiceOptions, ServiceOptionsWithDependencies, ServiceOptionsWithoutTypeOrDependencies } from './interfaces/service-options.interface.mjs';

...but ServiceOptionsWithoutTypeOrDependencies is marked as @internal in the TSDoc.
This seems more like a TypeScript bug, tbh.

So I guess the solution here is to use an alternative tag (as opposed to @internal).

Resolved by #147.


fixes #236

fixes #236 if a game gets scheduled, we set the related availability objects to is_available=True if they exist.

Should red card players be blocked from scheduling? Or are they already and this is just a sanity check?

Should red card players be blocked from scheduling? Or are they already and this is just a sanity check?

Good question, difficult to answer. First of all this should only be relevant during the round where the player recieves the red card. If the red card is received for a no-show, I think there is nothing to do. However, if the red card is recieved for a late contact, this question is relevant: Ideally in the team league (where we have alternates) the red card players should really be blocked from scheduling. When they are late contact an alternate search will start anyway. At the moment they can schedule but not stop their alternate search, which is at least confusing for their opponents who might not be aware of the red card.
On the other hand in the individual leagues (currently lonewolf and chess960, where we do not have alternates) the lesser evil seems to be to let those players still play - and thus schedule - their games if their opponents agree. Those opponents can claim the win already today, but most of them prefer to play a game so imo it makes sense to let the red carded player play their game and only withdraw them afterwards.
To get to the ideal solution the challenge would be to implement this different withdrawal behavior in a way that is not weird. Not sure if linking it to the league.competitor_type='team' is a good approach. In addition, what would need to be clarified is how chesster would have to change. Chesster should not just ignore a scheduling message that affects a red carded player but provide some sort of useful feedback and I am not sure if chesster would need to be changed for that and how complex that would be.

Should red card players be blocked from scheduling? Or are they already and this is just a sanity check?

Good question, difficult to answer. First of all this should only be relevant during the round where the player recieves the red card. If the red card is received for a no-show, I think there is nothing to do. However, if the red card is recieved for a late contact, this question is relevant: Ideally in the team league (where we have alternates) the red card players should really be blocked from scheduling. When they are late contact an alternate search will start anyway. At the moment they can schedule but not stop their alternate search, which is at least confusing for their opponents who might not be aware of the red card. On the other hand in the individual leagues (currently lonewolf and chess960, where we do not have alternates) the lesser evil seems to be to let those players still play - and thus schedule - their games if their opponents agree. Those opponents can claim the win already today, but most of them prefer to play a game so imo it makes sense to let the red carded player play their game and only withdraw them afterwards.
To get to the ideal solution the challenge would be to implement this different withdrawal behavior in a way that is not weird. Not sure if linking it to the league.competitor_type='team' is a good approach. In addition, what would need to be clarified is how chesster would have to change. Chesster should not just ignore a scheduling message that affects a red carded player but provide some sort of useful feedback and I am not sure if chesster would need to be changed for that and how complex that would be.

Maybe something to open a future issue for then


Configure platform-specific information

Overview
Provide users to configure platform-specific settings.
Motivation

Structure layouts and member offsets differ for each platform, such as struct stat, struct jpeg_compress_struct etc.

Use case

The user clones the minilib git repository.
The user runs make configure in the top directory of minilib.
Various information are retrieved.

System architecture, eg. uname -a
Distribution name and version, eg. 'Ubuntu 22.04', 'Debian 12'
Installed libraries, eg. 'libpng', 'libjpeg62-turbo', 'libjpeg8-turbo'
Structure layouts, eg. struct stat, struct jpeg_compress_struct etc.

Should be defined in lib.c in fixlang-minilib-io.


<EMAIL_ADDRESS>requires  -><EMAIL_ADDRESS>-> unknown revision v1.3.3

While installing "github.com/osmosis-labs/osmosis/x/gamm/types" it throws the below error.
<EMAIL_ADDRESS>requires
<EMAIL_ADDRESS>reading github.com/gogo/protobuf/go.mod at revision v1.3.3: unknown revision v1.3.3

While the above dependency has "1.3.2" as latest.
https://github.com/gogo/protobuf/releases

Hey, I think you're trying to use Osmosis as a library?
in our go.mod files, we have a replace statement for this.  Yeah it is a bit of a pain.

Hmm odd that go mod vendor/tidy didn't pick this up. @faddat's suggestion should fix the issue.


After creation a resource is not rendered if its id is nil

In 0.8.3, I could 'create' a PORO object, and let the id of the object be nil, and everything would render well, i.e.:
class Poro
  def id
    nil
  end

  def save
    # some logic
  end
end

class PoroResource < JSONAPI::Resource; end

# POST /poros
{ "data": { "attributes": {}, "type": "poros" } }

# Response
{ "data": { "attributes": {}, "type": "poros", "id": null, "..etc..": "..etc.." } }

However, in 0.9.0, the data is just null:
# POST /poros
{ "data": { "attributes": {}, "type": "poros" } }

# Response
{ "data": null }

This is due to https://github.com/cerebris/jsonapi-resources/blob/release-0-9/lib/jsonapi/resource_serializer.rb#L69
Maybe a short line in the docs somewhere would let people know this happens.

I don't know when this changed, but you can't do idis nil now because then content[:data] is nil here.
https://github.com/cerebris/jsonapi-resources/blob/release-0-9/lib/jsonapi/acts_as_resource_controller.rb#L237


Fix how hierarchical sd values are computed

Is this a fix to match to math outline, a fix to match previous understanding or a change in model? If its the latter does it also need an update in the math description of the model

Hmm having a look it looks like the model description doesn't really say which feels bad

Yeah this unfortunately wasn’t properly documented anywhere and that’s on me, and is likely why the bug persisted for this long. I will write up an issue tomorrow to describe what was previously being done and to change the model definition to describe the current implementation. Should also add to the change log.

properly documented anywhere and that’s on me

That isn't how teams work


[SPARK-36214][PYTHON] Add add_categories to CategoricalAccessor and CategoricalIndex

What changes were proposed in this pull request?
Add add_categories to CategoricalAccessor and CategoricalIndex.
Why are the changes needed?
We should implement add_categories in CategoricalAccessor and CategoricalIndex.
Does this PR introduce any user-facing change?
Yes, users will be able to use add_categories.
How was this patch tested?
Added some tests.

cc @HyukjinKwon @itholic @xinrong-databricks

Test build #141437 has started for PR 33470 at commit 3c0474c.

Test build #141437 has finished for PR 33470 at commit 3c0474c.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/141437/

The tests for pandas-on-Spark and the linter have passed.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/45956/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/45956/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/45956/

Thanks! merging to master/3.2.


chore(master): release 2.1.2

:robot: I have created a release beep boop
2.1.2 (2023-04-30)
Reverts

"fix(node): urlencode query (#66)" (2308d15)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/ooliver1/mafic/releases/tag/v2.1.2 :sunflower:


Remote Connections

Update service bouncer to allow connecting from your machine to a remote machine.

👍 this would be fantastic, especially if there was a way to group by service name and perform a staggered restart across a cluster.

Added in #25, will be in release 1.2.0


Reformat code block

 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.:x: garyng sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.


Missing Features Minor

Execute a direct copy to clipboard with a small toast notification after a Note is published

Also add in a button for copying manually


Set up CI with Azure Pipelines.

CI on Azure Pipelines is about three times faster than Travis.

An owner needs to approve Azure Pipelines for the org first.
cc @therealprof

bors try

Hopefully also with better support for Windows.

@reitermarkus Access is approved.

bors try

bors r+

bors retry


Ability to customise service type liveness/readiness probes

Liveness/readiness are hardcoded to services types defined in docker compose eg.

using lagoon.type: node uses TCP/3000
using lagoon.type: nginx-php uses TCP/9000

It would be helpful if we could define/extend health checks to assess domain specific services (eg. ensure that an entrypoint generates configuration that is expected).

Potentially related https://github.com/amazeeio/lagoon/issues/2525#issuecomment-783772941


capture_error_stacktraces is not used

There's no way to disable the use generation of stacktraces anymore.

The option capture_error_stacktraces used to exist to turn this off but has gone away as of 1.0, this should be added back.

@rokob Not sure about this. Just went through the log and I can't see any code related to capture_error_stacktraces at all. There was documentation in README.md for it, but no actual code.
Either way, I'm going to implement this for 1.2.0

This is ready for review in PR https://github.com/rollbar/rollbar-php/pull/192

Merged


unable to add a tag with spaces

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
  - location: body
    keywords:
      - 'Critcal'
    labels:
      - 'P1 - critical'

Expected behavior
a rule with a tag with spaces does not seem to work at all
Screenshots
bot does not do anything
Desktop (please complete the following information):
chrome

issue did not work in this repo:

https://github.com/ironmansoftware/issues/issues/3256

Here is the yaml:
https://github.com/ironmansoftware/issues/blob/main/.github/labeler.yaml

@riyadhalnur, i cloned the repo and tried figure out what you were doing, and it seems like i am really bad at ts. I am sorry i cannot help come up with a solution.

Hey @Omzig thanks for giving this a shot. I'll look into it when I find some time


Copy Java pom.xml to outdir

jsii-pacmak generates a pom.xml file alongside the generated java code src directory; however, jsii-srcmak only copies the src directory. That works out fine when putting the generated code side of application code (what cdk8s and cdktf do currently). That pom.xml would be needed (or another one) in order to place the generated code elsewhere and reference as a separate project. That would also align better with what the other supported languages are doing.
Could make it an option to prevent breaking existing uses.

In this case, why not use jsii-pacmak directly?

In this case, why not use jsii-pacmak directly?

cdktf started off that way, but when fixing Windows issues and adding languages we switched to jsii-srcmak since it already took care of those things.
Going back to direct use would just be copying code and changing a line or two, so definitely could go that route.
Is there some reason why the Java support works differently than other languages?


Empty tile grid (emulator)

Issue Type
[x ] Question
[ ] Bug
[ ] Improvement
[ ] Build system related
[ ] Performance
[ ] Documentation
Description and/or steps/code to reproduce the problem
Trying to implement osmdroid using gradle and followed the steps in : https://github.com/osmdroid/osmdroid/wiki/How-to-use-the-osmdroid-library
But when I launch the activity with the map it only displays a gray grid with no map tiles. Could this be an emulator issue? Just got started and left all the default settings.
I'm using the needed permissions:
`

<uses-sdk
    android:minSdkVersion="8"
    android:targetSdkVersion="22" />

<uses-permission android:name="android.permission.ACCESS_COARSE_LOCATION" />
<uses-permission android:name="android.permission.ACCESS_FINE_LOCATION" />
<uses-permission android:name="android.permission.ACCESS_WIFI_STATE" />
<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />
<uses-permission android:name="android.permission.INTERNET" />
<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" />
<uses-permission android:name="android.permission.READ_PHONE_STATE" />
<uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE" />`

and my gradle looks like:
compile 'org.osmdroid:osmdroid-android:6.0.1'
while using mavenCentral() repository
The code for the maps activity :
`package com.example.myapplication;
import android.content.Context;
import android.preference.PreferenceManager;
import android.support.v7.app.AppCompatActivity;
import org.osmdroid.config.Configuration;
import org.osmdroid.tileprovider.constants.OpenStreetMapTileProviderConstants;
import org.osmdroid.tileprovider.tilesource.TileSourceFactory;
import android.os.Bundle;
import org.osmdroid.views.MapView;
public class MapWithLocations extends AppCompatActivity {
MapView map = null;
@Override
protected void onCreate(Bundle savedInstanceState) {
    super.onCreate(savedInstanceState);
    Context ctx = getApplicationContext();
    Configuration.getInstance().load(ctx, PreferenceManager.getDefaultSharedPreferences(ctx));

    setContentView(R.layout.activity_map_with_locations);

    map = (MapView) findViewById(R.id.map);
    map.setTileSource(TileSourceFactory.MAPNIK);
}

public void onResume() {
    super.onResume();
    map.onResume();
}

public void onPause(){
    super.onPause();
    map.onPause();
}

}`
Environment
Android Emulator nexus 5.
If it's a bug, version(s) of android this affects:
All
Version of osmdroid the issue relates to:
6.0.1

Did you do the permissions prompt?
On Mon, Jul 16, 2018, 5:25 AM openBDM<EMAIL_ADDRESS>wrote:

Issue Type
[x ] Question
[ ] Bug
[ ] Improvement
[ ] Build system related
[ ] Performance
[ ] Documentation
Description and/or steps/code to reproduce the problem
Trying to implement osmdroid using gradle and followed the steps in :
https://github.com/osmdroid/osmdroid/wiki/How-to-use-the-osmdroid-library
But when I launch the activity with the map it only displays a gray grid
with no map tiles. Could this be an emulator issue? Just got started and
left all the default settings.
I'm using the needed permissions:
`

`
and my gradle looks like:
compile 'org.osmdroid:osmdroid-android:6.0.1'
while using mavenCentral() repository
Environment
Android Emulator nexus 5.
If it's a bug, version(s) of android this affects:
All
Version of osmdroid the issue relates to:
6.0.1
[image: image]
https://user-images.githubusercontent.com/41287133/42751368-d2f4a7ba-88ea-11e8-9368-bb1eed07f156.png
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/osmdroid/osmdroid/issues/1095, or mute the thread
https://github.com/notifications/unsubscribe-auth/AB4kGZow9-lFl3A6KAP6epUsuDzSdFvEks5uHFv4gaJpZM4VQzxx
.

@spyhunter99 How do I get this permissions prompt on the emulator? I figured because it's on the emulator you dont get it

https://github.com/osmdroid/osmdroid/blob/master/OpenStreetMapViewer/src/main/java/org/osmdroid/intro/PermissionsFragment.java
it must be done before loading the content view of the map. It should actually still show the map without this though. Did you check the logcat? Does the emulator have an sdcard attached?

@spyhunter99 I added the following to my android manifest file:
android:usesCleartextTraffic="true"
and now i'm getting the following (different) result :

is this supposed to happen?

ahh. It's the tile source, they just changed to ssl only, however it seems to be change somewhat frequently. We're going to publish a new version shortly with the fix for that baked in. You can also use a different tile source in the mean time

@spyhunter99 thanks! As per cleartext solution i applied in the manifest it now works :) How would I go about changing the tile source? like so? : https://github.com/osmdroid/osmdroid/wiki/Map-Sources ? Any specific solution you could recommend? :)

try this
https://github.com/osmdroid/osmdroid/blob/master/osmdroid-android/src/main/java/org/osmdroid/tileprovider/tilesource/TileSourceFactory.java#L99
then apply it with map.setTileSource(...)


No indication where a badge comes from

I see a badge on the app, open it and... now what? There is no way to figure out why the badge is there as far as I can tell?

I think the badge appeared on your app because of an invitation. Indeed the app badge includes the invitations. Contrary to the web-client, the invitations are not highlighted in vector-ios. We should add a pink red marker on each invitation.
Could you please confirm?
Note: The joined rooms concerned by the missed notifications are highlighted in the rooms list. A green or a pink red badge displays the missed notifications.

Actually, it was a "Fuzzy76 (IRC) joined the room" in one of my favorited rooms.

The wrong app badge could not be related to a membership event like "Fuzzy76 (IRC) joined the room".
I failed to reproduce the issue.

Cannot reproduced
Note: A pink red marker has been added on each invitation (see #426).

It happens every time the IRC bridge reboots, and does not seem to clear until I visit the one channel I have favorited.


Migrate to class syntax throughout the project

Also contains some slight cleanup that was possible after the change.
See commit messages for details.
I'll do one more pull request after this, with some general cleanup before I start working on the customizability feature (which will probably result in a non backwards compatible version).
It'll also fix all the bugs I can find.
Sorry these pull requests are a bit too general, and not focused on just one change. Just let me know and I'll split these up into multiple ones.
I'm hoping this makes it faster overall, not having to go through ~10 different pull requests.

I updated the pull request. It had too many unrelated changes hidden in single commits.

Is this ready to be merged? Are you confident you didn't break anything?

It is. I don't think anythings broken, but deep tag alignment is a bit over active. I think it's bugged in master and now somehow got fixed as I haven't touched the logic.
This pull request with per section indent off:
/**
 * [parseCommand description]
 *
 * @param   {[type]} event                       [description]
 * @param   {[type]} inline                      [description]
 * @returns {[type]}               [description]
 * @throws  {[type]} [description]
 * @example
 * @todo    [code]
 */

master:
/**
 * [parse_command description]
 *
 * @param   {[type]} event         [description]
 * @param   {[type]} inline        [description]
 * @returns {[type]}               [description]
 * @throws  {[type]} [description]
 * @example
 * @todo    [code]
 */

I plan on addressing it in the next pull request, alongside with a punch of other bugs.

Ok great 👍
If you fix bugs, please make sure to check the issue tracker and see if they where already reported. Maybe we can also reduce the number of open issues with your affords. I can see how much work you are putting into this, it is highly appreciated.


Add new timeout and retries for the default values of each nri_kubernetes component

Add new timeout and retries for the default values of each nri_kubernetes component

The configuration change and therefore unittest need to be updated:
In order to run unit test:
helm plugin install https://github.com/quintush/helm-unittest
helm unittest ./charts/newrelic-infrastructure-v3 -3

Moreover the chart tests are failing since we have a dependency for tests with https://github.com/newrelic/nri-kubernetes/pull/335#pullrequestreview-858401678
I would merge this first and then the other to enable e2e tests


Initial commit of Boolean State Cluster as per issue #227

Hope I'm doing this right!

Will start pushing other Clusters today. Forgot to mention, tested this Cluster on Google Home using the "Contact Sensor" device. Seems to work fine

Thank you and welcome to the contributors :-)

Thanks for putting up with my fumbling :-) Before this, I'd never written a line of Typescript and am still a git novice, but I'll do what I can.


nightwind/helper not exporting default

i have a file called nwpp.ts that adds a svelte store .dark to nightwind but i get this error from the browser:
Uncaught (in promise) SyntaxError: The requested module '/node_modules/nightwind/helper.js' does not provide an export named 'default'

this is the code that imports inside nwpp.ts
import nightwind from 'nightwind/helper'

im using svelte btw


Add Scroll Back To Top

Since it is a long page, I think it is better to have a scroll button up.

Yeah you're right. I'm wondering now if there's a way to make it using only CSS.

This should work, thanks!


Rust-gpu instead of GLSL?

I saw that there was some GLSL involed and just wanted to tell you that Embark studios is working on a GLSL Rust replacement.
https://github.com/EmbarkStudios/rust-gpu

Hello! I know about this crate, but it is not suitable for rg3d because rg3d aims for low-end and relatively old hardware too as well as modern GPUs. Also rust-gpu seems to be immature and I don't want to fight with random bugs from it, I have OpenGL already :smile:

I understand :D I just thought I would share just in case.
Still an interesting project you got going. I will try to look more into it soon.
I would say this issue is resolved now so I will close it :P


Put tags in search help

Search help should have tags. We should also have documentation for all search terms that can be used for searching.

Was https://github.com/natlas/natlas/commit/7e9cba5fb8f2dfc2768df198fcc01038959454dc supposed to close this as referenced in the git commit message?


[BUG] scout:import starting two processes with the same id, one always failing

Version
Laravel: 8.62.0
Scout: 9.2.10
Package: 5.0.1
Problem
I get entries in the table failed_jobs like Illuminate\Queue\MaxAttemptsExceededException: Matchish\ScoutElasticSearch\Jobs\QueueableJob has been attempted too many times or run too long.
I don't think it's actually a timeout, because payload contains timeout: null and failOnTimeout: false.
I spent hours searching for the cause and even logged the responses of Elasticsearch. Looking into worker.log, which is maintained by pm2, I see:
[2022-01-28 09:47:20][izYkReOaDX7UOzCmr4t21lHLOjvUIPj3] Processing: Matchish\ScoutElasticSearch\Jobs\QueueableJob
[2022-01-28 09:48:50][izYkReOaDX7UOzCmr4t21lHLOjvUIPj3] Processing: Matchish\ScoutElasticSearch\Jobs\QueueableJob
[2022-01-28 10:05:17][izYkReOaDX7UOzCmr4t21lHLOjvUIPj3] Processed:  Matchish\ScoutElasticSearch\Jobs\QueueableJob

It strikes me as odd that a process is started twice with the same id.
The process started at 09:48:50 fails immediately (written to failed_jobs).
I can see in pm2 monit that one queue worker is doing work until the log entry at 10:05:17 confirms that the job was processed. This also shows that there is no timeout problem and the job actually works.
I guess it's tough, even for you, to diagnose this behaviour. Could you at least point out, how I could debug this problem better and narrow down the cause?

I don't want to bother you, but at least I would appreciate a hint how to debug this. As a workaround, I have to use single thread indexing and it's slowing things down a lot. A real shame, since the application is running on a 64-core Threadripper.
I also notice you seem to be from Kyiv? I hope you are not there right now and your loved ones are safe! Day after day, it's heartwrenching to see what happens in Ukraine. :( Our governments are NOT doing enough to stop this war and every citizen I know is willing to suffer inconveniences. It would be delusional to think we could have a war in Europe today without consequences for every single one of us.

Hey! First of all, thank you for your support💙💛 I really appreciate all the people who try to help in any way they can and do not stand aside🤗
İ would try to exclude some moving parts to narrow down the cause.
Do you have the same issues for other commands? İ mean the same process ids
Could you use something else instead of pm2?
İf the issue appears only for package specific command then you can try to disable some code into the command(you need to fork the package then)

Maybe the issue appears because of chaining jobs
https://github.com/matchish/laravel-scout-elasticsearch/blob/8f0fffc318b527838de9a3712067cfcc21866ed3/src/Console/Commands/ImportCommand.php#L53

Also changes in pm2 configuration could help

https://github.com/matchish/laravel-scout-elasticsearch/issues/190#issuecomment-1100136780
You can try to send import job to queue directly without chaining (fork needed)

Maybe the issue appears because of chaining jobs
https://github.com/matchish/laravel-scout-elasticsearch/blob/8f0fffc318b527838de9a3712067cfcc21866ed3/src/Console/Commands/ImportCommand.php#L53

While I was investigating the problem that was the exact line that I found suspicious in regards to parallelization. If I am understanding it correctly, it is an asynchronous process which runs multiple processes one after the other, synchronously. But this would not profit from a multithreading CPU. Why is it done that way?

Do you have the same issues for other commands? İ mean the same process ids

No.

Could you use something else instead of pm2?

No, too much dependencies. It is a very mature and stable process manager, I don't see a way how it could cause the problem.

Also changes in pm2 configuration could help

I will look into that, maybe there are rules for running/starting/stopping processes that affect this case.

Hey! First of all, thank you for your support💙💛 I really appreciate all the people who try to help in any way they can and do not stand aside🤗

You're welcome! It's a matter of course.

Ok, I guess it's solved. It was a simple reason after all.
It always worked with 1 worker. With 2 workers, I got the following:
Worker 0
	[2022-04-20 08:52:37][dU53PW37lcxbwCXMXxIbkPhPzoGOev7c] Processing: Matchish\ScoutElasticSearch\Jobs\QueueableJob
	[2022-04-20 08:55:05][dU53PW37lcxbwCXMXxIbkPhPzoGOev7c] Processed:  Matchish\ScoutElasticSearch\Jobs\QueueableJob
Worker 1
	[2022-04-20 08:54:07][dU53PW37lcxbwCXMXxIbkPhPzoGOev7c] Processing: Matchish\ScoutElasticSearch\Jobs\QueueableJob
	[2022-04-20 08:54:07][dU53PW37lcxbwCXMXxIbkPhPzoGOev7c] Failed:     Matchish\ScoutElasticSearch\Jobs\QueueableJob

The process started by worker 1 is failing immediately. Notably, it always starts 90 seconds after worker 0 started the first process.
I didn't know about the setting retry_after in the queue config. And even after I found it, I interpreted it as: "retry a failed job after that number of seconds."
Actually, as per the documentation, retry_afterwill even retry a job, while it is running.

In your config/queue.php configuration file, each queue connection defines a retry_after option. This option specifies how many seconds the queue connection should wait before retrying a job that is being processed. For example, if the value of retry_after is set to 90, the job will be released back onto the queue if it has been processing for 90 seconds without being released or deleted. Typically, you should set the retry_after value to the maximum number of seconds your jobs should reasonably take to complete processing.

(https://laravel.com/docs/9.x/queues)
Why does it always work with exactly one worker? I guess, a worker has to be available to retry a job. The Laravel doc does not mention that retry_after is irrelevant (afaik), if only one worker is running.
Two questions:
While investigating the code, I noticed that the import does not use parallelization. The job \Matchish\ScoutElasticSearch\Jobs\Import uses import stages from \Matchish\ScoutElasticSearch\Jobs\ImportStages::fromSource. There, the data is chunked and all chunks are processed in those stages. I. e. the chunks are not distributed over several jobs. Why?
And am I assuming correctly that $job = (new QueueableJob())->chain([$job]); is used to prevent an exception that would occur, when the job tried to output something to a non-existent output stream?

I don't remember details, but you're right Import was designed to run in parallel but at some point there were some issues with consistency because of overlapping pages, performance chunking, stages execution order, etc.
I've have some proof of concept here and it worked last time I checked (no progress report yet). So if you have time and willing, be my guest to try it) PR highly welcome as well.
Chaining jobs just a way to not have if and to work with any job in the same way. If it's not queueable job it will be executed immediately, otherwise will go to a queue

Will compare my solution with this one when come back to parallel import. Thanks)

IMHO, this issue could be closed.


Angular 18

Fix #9881 #9956
Waiting releases:

[x] angular-eslint
[ ] angular-builders/jest Beta: 18.0.0-beta.2

adding a bounty for the work done here
Let's merge this, then, I'll let you follow the beta version to use a real version once it's released :)

@pascalgrimaud yes I will update the real version and thanks for the bounty https://opencollective.com/generator-jhipster/expenses/205307

@qmonmert : approved


Consider removing notebook types from language mode picker

Does this issue occur when all extensions are disabled?: No (some type of Notebook extension required)

VS Code Version: 1.61.0
OS Version: Mac Big Sur

Comments here in this Jupyter issue: https://github.com/microsoft/vscode-jupyter/issues/7363#issuecomment-923323526
From my perspective, the notebook types (Jupyter, Github-Notebooks) should not show up in the ChangeModeAction list. It creates some confusing scenarios having blank text editors of "Jupyter" language mode. Or having individual cells in a notebook set to "Jupyter" or "Github-Issues" language modes.

We closed this issue because we don't plan to address it in the foreseeable future. If you disagree and feel that this issue is crucial: we are happy to listen and to reconsider.
If you wonder what we are up to, please see our roadmap and issue reporting guidelines.
Thanks for your understanding, and happy coding!


Refactor ipld to use pull streams for get

This a PR to refactor ipld resolver to use pull streams #101 , as well as change the default behavior from returning a single value in a callback to returning an array. In addition to this the changes will expose getPullStream which should allow people to read the stream and process each node along the path.
In this PR, I didn't add explicit tests for proper path resolution (i.e. the collected along the path are correct), wanted to get a little more feedback first. Also note this will be a breaking change.
@vmx PTAL when you get a chance, and let me know if the interface should change or any thing you'd like to see implemented differently, also if you have any pointers to other projects that will need to be updated to support this change, that would be great!

As returning the result as an array is a breaking change, I'd like to get a @diasdavid view on it. For me it sounds good.

Fine by me. It makes it consistent with the IPFS APIs for when there is more than a way to return (array vs pull vs readable)

@zcstarr The other projects that would need to be updated are:

https://github.com/ipfs/js-ipfs-unixfs-engine
https://github.com/ipfs/js-ipfs

@vmx quick question is the expectation that js-ipfs ipfs.dag.get returns array as well, or should I make the integration of this pull stream PR a non breaking change with js-ipfs ?

@zcstarr A non-breaking change sounds good. I would then start a discussion about the breaking change later on.
@diasdavid Do you agree?

Yeah. Let's have .get and .getPullStream both in js-ipfs and js-ipld just like the Files API does -- https://github.com/ipfs/interface-ipfs-core/blob/master/SPEC/FILES.md. No need to implement the ReadableStream endpoints at this level.

@zcstarr Thanks for all your work on this. A lot has happened since this PR was originally opened. We don't use pull-streams anymore, but async iterators. Hence I'm closing this issue.


Dashboard stats detail

Adds additional profit detail and base currency balance to the stats box

I've been using this for the past day or so and i can tell you ti's working great and really informative! @eatsleepcoderepeat-gl do you have any comments? I'll merge this so he gets the PR credit and then add the dashboard url wrapper so we can include it in the master script.

I have a number of updates that I'm working on for this script, particularly to move away from watching for DOM modification events to trigger stats updates, as this can be very resource intensive and may cause browser crashes.
Feel free to merge this if you'd like in the meantime and I'll add a PR later for my updates. I would suggest waiting to put this script in the all.user.js script until we address the way the stats update, however.

Merged and released :D
thanks @falcontx!


Use type cache when it's available in JavaExecutionContextView.

To clarify this change:
Previously, if the type cache was not explicitly set on a context, the java context view would fall back to the default. A new instance of the JavaExecutionContextView is used each time (resulting in a different default, empty cache) during each parse. This resulted in memory exhaustion because there was no type sharing across JavaParsingVisitors.

Reverting, as I think this has no effect. On the subsequent call to getMessage it just returns the message with the key rather than the default, which is the same instance.

@tkvangorder Please revert.

There is one execution context instance per parsing operation (over a whole source set or project). Thus, there should be a unique type cache per parsing operation. This is WAD.

@jkschneider : on my side this fixed a huge regression (very long parsing with a lot of heap space)


[Bug]: Canvas not Responsive on Different Devices

Give a brief about the bug ✍
Brief about the bug: The current implementation of the canvas in the script lacks responsiveness, causing it to appear incorrectly sized or even black on certain devices.
What is the expected behavior? 🤔
The canvas should dynamically adjust its size and position based on the dimensions of the device's viewport, ensuring consistent and visually appealing rendering across various screen sizes.
Provide step by step information reproduce the bug 📄
Steps to reproduce the bug:
Access the application on different devices with varying screen sizes (e.g., desktop, laptop, tablet, mobile).
Observe the canvas element's rendering and behavior.
Note inconsistencies such as incorrect sizing, misalignment, or black canvas areas.
Compare the observed behavior with the expected behavior of a responsive canvas.
This issue impacts the usability and visual experience of the application, especially for users accessing it on devices with non-standard screen dimensions.
I am an open-source contributor and would like to contribute this feature enhancement to the project.
Select program in which you are contributing
GSSoC24
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

please assign me this issue .

@tanya-54 Please raise any other issue, i'll assign you
If you have any doubt you can directly send message on our discord (https://discord.gg/rZb46cCMmK), we have created separate channals for all projects...
Thank you :)


Create first user using mgradm

What does this PR change?
Now that mgradm install [kubernete|podman] can create the first user use this feature rather than querying the API ourselves.

@srbarrios this is probably of interest for you


Error when using resolver.alias

With
 config.resolve.alias = { 'components': '/src/components' }

Storybook is requesting a file like localhost:8000/src/components/..., but it seems only<EMAIL_ADDRESS>(@fs + absolute path) would work. Can you provide an example how to do alias?

Seems like it could, maybe, be related to https://github.com/eirslett/storybook-builder-vite/pull/28?

Try using ./src/components (dot first)?

Or 'components': path.resolve(__dirname, 'src', 'components')

Hii guys, just got into this issue. I have my src directory as a tsconfig path.

With ./src/components the request becomes localhost:8000/@id/src/suspense/Suspense (where is @id generated from?)
With path.resolve(__dirname, 'src', 'components'), request becomes localhost:8000/Users/dongchen/path/to/src/components/... (path is right but missing the @fs)

I'm looking into this issue. I'm doing it on a react-ts project.

@imdongchen Maybe you're hit by the fsServe.strict setting that is enabled by default? You could try turning it off and see if that helps - or configuring the root directory?

Turning off fsServe.strict works! Thanks!

Turning off fsServe.strict works! Thanks!

But ideally, I would suggest that you re-enable the setting, and try to configure fsServe.root properly so that it still serves your stories!


Release v1.2.0

In this release we want make big refactoring
We want

[x] Make refactoring for Activities (#7)

[x] MainActivity
[x] CheckKeyActivity

[x] Make refactoring for Fragments (#8)

[x] SettingsFragment
[x] PasswordFragment
[x] ConfirmFragment
[x] UpdateFragment

[x] Make refactoring for Utils (#9)

[x] Crypt
[x] PasswordGenerator

[x] Move files/images to another folders (#10)

[x] Make refactoring for Database files (#11)

[x] Password
[x] PasswordDao

This list will be update in the future. We're planning to release update 7 July

All our plans was made. We're merging pull request.


support for deploying headless managed project

usecase: deploying assets into an existing project without updating the manifest.

@lionelvillard has PR #775

added --projectname flag with PR #775


Eliah Kagan: Watch idscan.net

Eliah Kagan requests the watch of the watch_keyword idscan\.net. See the MS search here and the Stack Exchange search here.

idscan\.net has been seen in 4 true positives, 0 false positives, and 0 NAAs.

As noted in chat (https://chat.stackexchange.com/transcript/message/53053909#53053909) this may not be a useful keyword to watch because it appear in legitimate posts and future appearances are fairly unlikely to be spam.
If I'd thought of this, I'd likely not have requested the watch. I certainly have no objection if this PR is closed.