Update Tracer#in_span to finish the Span

Overview
Updates Tracer#in_span to call Span#finish at the end of the block and adds API tests for Tracer.
Details
While creating some examples based on the DataDog auto-instrumentation work I noticed that the Tracer#in_span implementation wasn't finishing the span as expected. I looked into the Python implementation and saw the call the end(). This adds the call to #finish and adds tests to both the API and SDK.
The tests are going through some slight acrobatics to verify things are working as expected. Please let me know if there are better ways to do this given the implementation(s).
I added tests for the existing API Tracer implementation before updating #in_span to make sure the changes wouldn't cause us trouble in other methods.
Thoughts

I like that the Python API makes the call to finish/end optional. If we're interested in that I can open a new PR for that functionality. @fbogsany mentioned we may want to do this.
It's usually bad form to add methods just to ease testing but you can see that I had to poke at the internals a bit to figure out if a span has ended. Any reason not to add Span#ended??

I like that the Python API makes the call to finish/end optional. If we're interested in that I can open a new PR for that functionality. @fbogsany mentioned we may want to do this.

I'm going to walk back my 'like' for this. This is a convenience API that now wraps 3 things that a client can already do with the API:

start a new span
make it active
finish it
Optionally removing one of the 3 doesn't really bring enough value to justify the complication to the method signature. Compare:

span = nil
result = OpenTelemetry.tracer.in_span('do-the-thing', finish: false) do |new_span|
  span = new_span
  compute_the_thing
end
...
span.finish

with:
span = OpenTelemetry.tracer.start_span('do-the-thing')
result = OpenTelemetry.tracer.with_span(span) { compute_the_thing }
...
span.finish

I'd argue the latter is cleaner, easier to understand, and easier to use.

I like that the Python API makes the call to finish/end optional. If we're interested in that I can open a new PR for that functionality. @fbogsany mentioned we may want to do this.

I'm going to walk back my 'like' for this. This is a convenience API that now wraps 3 things that a client can already do with the API:
1. start a new span

2. make it active

3. finish it
   Optionally removing one of the 3 doesn't really bring enough value to justify the complication to the method signature. Compare:

span = nil
result = OpenTelemetry.tracer.in_span('do-the-thing', finish: false) do |new_span|
  span = new_span
  compute_the_thing
end
...
span.finish

with:
span = OpenTelemetry.tracer.start_span('do-the-thing')
result = OpenTelemetry.tracer.with_span(span) { compute_the_thing }
...
span.finish

I'd argue the latter is cleaner, easier to understand, and easier to use.

@fbogsany Totally agree with this. Looking closer, the Python folks have added the optional flag to Tracer.use_span which appears to map to our Tracer#with_span. It wasn't clear to me that the method would accept a Span. (The API uses span: "Span" while the SDK uses span: trace_api.Span). Maybe this changes our opinion of the usefulness...
Keep #in_span signature the way it is.
OpenTelemetry.tracer.in_span('do-the-thing') do |new_span|
  compute_the_thing
end

#with_span using default finish of false:
span = OpenTelemetry.tracer.start_span('do-the-thing')
result = OpenTelemetry.tracer.with_span(span) { compute_the_thing }
# ...
span.finish

#with_span using finish ==  true:
span = OpenTelemetry.tracer.start_span('do-the-thing')
result = OpenTelemetry.tracer.with_span(span, finish: true) { compute_the_thing }

Since #in_span uses #with_span it can default to finish: true, and that might also fix up the problem of returning the value from the with_span block.

I think it is worth laying out the common use-cases of each method:

start_root_span is used when explicitly starting a new trace. This is not common for typical HTTP services, but can be used in a background (e.g. Resque or Sidekiq) job, and may also be used for services that form a boundary between 3rd-party and 1st-party systems (where we may not want to continue a trace started by another business entity). The common pattern is something like:

def foo
  span = tracer.start_root_span('foo')
  ... # maybe tracer.with_span(span) at some point
ensure
  span.finish
end

start_span provides the most flexibility. It is typically used when a caller wishes to precisely manage the lifetime of the span, the span parent, and also wishes to manage its "activation" via with_span (or not, as the case may be). Typical patterns include:

def foo(parent_span)
  span = tracer.start_span('foo', with_parent: parent_span)
  ... # maybe tracer.with_span(span) at some point
ensure
  span.finish
end

def foo
  span = tracer.start_span('foo') # implicit parent span from current context
  Thread.new(span) do |span|
    ... # maybe tracer.with_span(span) at some point
  ensure
    span.finish
  end
end

with_span simply activates and deactivates the span w.r.t. the current context. The primary value here is making the "current span" available through a call chain that does not propagate the span via an explicit parameter. Examples include pretty much any Ruby framework at present, which obviously do not anticipate the existence of OpenTelemetry. Example:

def leaf_method
  span = start_span('leaf') # implicit parent span from current context
  do_the_thing
ensure
  span.finish
end

def framework_method
  leaf_method
end

def service_method
  wire_context = tracer.http_text_format.extract(headers) { |headers, key| headers[key] } # what a horrible API, in retrospect
  span = tracer.start_span('service', with_parent_context: wire_context)
  result = tracer.with_span(span) { framework_method }
  format_result(result)
ensure
  span.finish
end

in_span is a convenience method for a common use-case, especially in manual instrumentation (the moral equivalent of StatsD.measure('my-metric') { ... } or manual timing code & logging). The most common use-case outside of auto-instrumentation is wrapping a block of code in a span, where the author shouldn't have to think about propagation (where her span's parent comes from, which spans her span parents). E.g.:

def my_wonderful_but_maybe_slow_method
  tracer.in_span('my_wonderful_but_maybe_slow_method') do
    sleep(30)
    do_something
  end
end

current_span is most often used when a new piece of information is discovered at a random point in the code and we want to add it as an attribute or event to the current span (effectively add a metric/dimension or a log), without really caring about what that span is. E.g.

def i_just_figured_it_out!
  tracer.current_span['answer'] = 42
end

From this perspective, I don't think with_span should do optional-double-duty of finishing the span. Its sole purpose is to propagate the span across API boundaries ("in process context propagation"). Most leaf methods (e.g. when instrumenting calls to Redis, memcached, MySQL, etc.) should use explicit span creation and finish.

@fbogsany I believe I have addressed all your feedback. This is rebased on master and ready to go. Thank you again for the thorough review and all the help. I've opened issue #123 to update the documentation with your Tracer method explanations above.
🙇

It looks like #122 has landed, and this is conflicted. What do we need to do to move this forward?

@mwear I will make the moves on Friday and see if I can get it over the line.

@fbogsany I've addressed all the suggestions/issues you raised with the exception of changing the behavior you mentioned in this comment.
@mwear this has been rebased and the Minitest deprecations have also been addressed.
I believe it's good to go.


Make TagPolicy a struct with options instead of a string

More complex taggers (and even the git one perhaps) will need to take parameters.
Also, how should we handle breaking config changes like this?

I anticipate we’ll need this but what are the use cases?  Should we proactively break the config now?

Some discussion in #231.
I was working on adding an "environment variable" tagger which will execute against a template. But yeah, even things like the git tagger might want parameters eventually.


[Bug Report] GitHub actions are using deprecated commands

Look at the details of a github actions run after a recent commit.
For example, you will see deprecation warnings similar to this in the 'continuous-integration' build:
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
We update our actions to remove these warnings before the commands become fully depreciated. It is likely that these commands are actually used by modules that are actions use. It may just be a need to upgrade these modules.
Verify that there are no actions raising warnings.

Please do. I would appreciate an outside option.

I can't see those deprecation commands anymore if I look at the newest workflow log for a commit, potentially fixed? @mjaskula

I still see deprecation warnings, for example here:
https://github.com/Allen-Synthesis/EuroPi/actions/runs/7801048079
But they are not the same text as I quoted above:

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

Never mind, I found the old one too. I's under the step 'Get pip cache dir'

I think I've made the necessary changes for this here: https://github.com/Allen-Synthesis/EuroPi/pull/385


Show example plots as part of documentation

In seaborn, the docstring example plots are shown as part of the documentation. Would be great to have this as part of scanpy as this will motivate the creation of more examples as part of the docstring while keeping them up-to-date.
See for example: https://seaborn.pydata.org/generated/seaborn.catplot.html

Does anyone has experience on how to achieve this?

@fidelram that's a really great point and something I'd like to discuss at next meeting.
Another great example of such examples 😅 is the way @michalk8 set it up for cellrank and squidpy [not yet public].
The even nicer thing is that @michalk8 implemented a CI pipeline for the tutorials/examples part of the repo so that every time there is a change in master of the original repo, the examples are refreshed in the notebooks repo, so to have them always up to date.
Would be really cool to concentrate efforts and try to get this logic also in scanpy (makes it both very user friendly and robust from a maintainer perspective)

@fidelram that's a really great point and something I'd like to discuss at next meeting.
Another great example of such examples 😅 is the way @michalk8 set it up for cellrank and squidpy [not yet public].
The even nicer thing is that @michalk8 implemented a CI pipeline for the tutorials/examples part of the repo so that every time there is a change in master of the original repo, the examples are refreshed in the notebooks repo, so to have them always up to date.
Would be really cool to concentrate efforts and try to get this logic also in scanpy (makes it both very user friendly and robust from a maintainer perspective)

I would love to have this! I've been talking about this with @falexwolf and a bit with @flying-sheep.
Seaborn uses a sphinx extension from matplotlib to generate the plots (plot directive).
I would definitely like to get tutorials running on CI as well, but think this is a little separate.

Tutorials can use a lot more computational resources than plotting.
These examples are written in the docstrings, while tutorials are currently in notebooks. It'll probably be a different set of tools to render these.

I would love to have this! I've been talking about this with @falexwolf and a bit with @flying-sheep.
Seaborn uses a sphinx extension from matplotlib to generate the plots (plot directive).
I would definitely like to get tutorials running on CI as well, but think this is a little separate.

Tutorials can use a lot more computational resources than plotting.
These examples are written in the docstrings, while tutorials are currently in notebooks. It'll probably be a different set of tools to render these.

I tried the sphinx extension but could not get any result. Can somebody take over this?

I tried the sphinx extension but could not get any result. Can somebody take over this?


Dead link in error message for windows "Microsoft Visual C++ 14.0 is required"

[x] I am on the latest Poetry version.
[x] I have searched the issues of this repo and believe that this is not a duplicate.
[x] If an exception occurs when executing a command, I executed it again in debug mode (-vvv option).

OS version and name: Windows 10
Poetry version: 0.11.2
Link of a Gist with the result of poetry add aioredis: https://gist.github.com/festinuz/ae4d5c5d03ba5512f43ccd246741ac1a#file-gistfile1-txt-L57

Issue

Basically, a link printed by poetry (http://landinghub.visualstudio.com/visual-cpp-build-tools) is dead.

This link has nothing to do with Poetry. This is a message displayed when compiling hiredis.


Failed to copy index: PUT on manifest file when copying dockerimage from ghcr to heroku

I see this error:
Error: failed to copy index: PUT https://registry.heroku.com/v2/something-app/worker/manifests/sha256:235kj43klj53kljlksgdfjsdjgij428010jfaqpoirjfanvkagj48g590q: UNSUPPORTED: The operation is unsupported.
panic: exit status 1

goroutine 1 [running]:
main.main()
	/go/src/github.com/akhilerm/repo-copy/main.go:20 +0x15a
Error: The process '/usr/bin/docker' failed with exit code 2

When performing this steps:
     - name: Set up Docker Buildx
        uses: docker/setup-buildx-action@v2
        with:
          version: latest
          install: true

     - name: Login Heroku-Registry
        uses: docker/login-action@v2
        with:
          registry: 'registry.heroku.com'
          username: ${{ something.HEROKU_UIGUR_LOGIN }}
          password: ${{ something.HEROKU_KLYUCH }}

      - name: Copy Something image from GHCR to Heroku
        uses<EMAIL_ADDRESS>        with:
          src: ghcr.io/something/${{ github.ref_name }}/something:${{ env.SOMETHING_SHA }}
          dst: |
            registry.heroku.com/${{ env.HEROKU_APP }}/worker:latest

Is the image that you are trying to copy to registry.heroku.com available in ghcr.io


Date to timestamp gratka

Coverage increased (+1.2%) to 79.688% when pulling 881df4bebe2393156c4007839817bbff62b2b548 on aklein13:master into 7c7d6f83042f3f72bede0505909cf542a01df4c9 on limebrains:master.


mxnet cpu broadcasting >5x slower than numpy

Description
When running on cpu only, broadcasting a  larger array is a lot more time consuming on mxnet than on numpy. Is there a way to speed this up?
Environment info (Required)
Running mxnet using python 2.7 on ubuntu 16.04 in cpu mode on Intel® Xeon(R) CPU E5-2687W v3 @ 3.10GHz × 20
Config entries for matrix computation libraries are:
USE_CUDA = 1
USE_CUDNN = 1
USE_NVRTC = 0
USE_OPENCV = 1
USE_OPENMP = 1
MKLML_ROOT=/usr/local
USE_MKL2017 = 1
USE_MKL2017_EXPERIMENTAL = 1
USE_NNPACK = 0
USE_BLAS = atlas
USE_LAPACK = 1
USE_INTEL_PATH = NONE
MXNet commit hash:
a5edbf94094581ee27157eae4f2113115a3994e7
A simple test script outputs the following:
import mxnet as mx
from   mxnet import nd
import time
import numpy as np

num_trials = 100
shape_a = (1000, 10000)
shape_b = (1000,     1)

strt = time.time()

for i in range(num_trials):
    nd.waitall()

    a = nd.empty(shape_a)
    b = nd.empty(shape_b)
    c = a + b

    c = c.asnumpy() # implicitely waits for results to be finished
stp = time.time()

print c.shape
print 'avg time over {} trials: {}s'.format(num_trials, (stp - strt) / float(num_trials))

strt = time.time()
for i in range(num_trials):
    a = np.empty(shape_a)
    b = np.empty(shape_b)
    c = a + b

stp = time.time()

print c.shape
print 'avg time over {} trials: {}s'.format(num_trials, (stp - strt) / float(num_trials))

(1000, 10000)
avg time over 100 trials: 0.0974750995636s
(1000, 10000)
avg time over 100 trials: 0.0150070381165s
When broadcasting larger arrays, a performance difference is clearly noticeable, is there anything I can do to speed it up?

@cjolivier01

What version was this done on?  0.11, 0.12, 1.0, this week's master?

Ok, I see this was done with version MXNet 0.11.0

Resolution:
In 0.11, when mxnet was built with CUDA enabled, OMP was not used for most operations in mxnet, even on CPU-only operations.  This changed in 0.12.
In 1.0, two additional things happened:

@piiswrong refactored broadcast operators from using the deprecated mshadow framework to his Kernel/Launch framework
Auto-tuning for selecting the most optimal OMP or non-OMP modes based upon thread count, number of data items and operator calculation "weight", thus using OMP for larger datasets and single-thread for smaller datasets (which is often faster).

Post 1.0, IntelOMP is built and used by default for cmake builds.
These things together make mxnet faster than numpy for most broadcast ops (so far as I have seen so far).  Times I get for the above script:
PASS 1...
(1000, 10000)
avg time over 100 trials: 0.0125194501877s
(1000, 10000)
avg time over 100 trials: 0.0115594983101s
PASS 2...
(1000, 10000)
avg time over 100 trials: 0.0119210195541s
(1000, 10000)
avg time over 100 trials: 0.0114824414253s
So, I think that the issue is resolved in current builds.  To get similar performance in your 0.11, you'd probably need to build without CUDA enabled.
Please reopen the issue if necessary.


IPv6 isn't working

Hello,
I've a port binding with 443:5000. When I access it with curl --insecure -v https://<IP_ADDRESS>/ everything looks good.
But curl --insecure -v https://[::1]/ isn't working.
It gets stuck at this output:

Trying ::1...
TCP_NODELAY set
Connected to ::1 (::1) port 443 (#0)
ALPN, offering h2
ALPN, offering http/1.1
successfully set certificate verify locations:
CAfile: /etc/ssl/certs/ca-certificates.crt
CApath: /etc/ssl/certs
TLSv1.2 (OUT), TLS handshake, Client hello (1):

A similar configuration with e. g. an Apache container works with IPv6.
Do I have an error in reasoning?
Thanks, webracer999

Oh I think it's really an error in reasoning?!
I found out, that my Apache container has the same problem, when I also use it in Docker Swarm.
When I use following in docker-compose.yml it works:

ports:
  - mode: host
    published: 443
    target: 5000

It would be a workaround for me, because I use a one node swarm (just so I can use "docker stack") ...


Fix handling of control flow instructions in convert_to_target()

Summary
This commit fixes an issue in the convert_to_target() function where it wasn't looking for control flow instructions in the proper location. Typically the control flow instructions are put in the supported_instructions field of the BackendConfiguration, but the convert_to_target() function was ignoring this field. This commit updates the function to check supported_instructions for the control flow instructions. It doesn't more broadly look at the supported_instructions field, because on other backends this field is used to list the supported pulse instructions which might have name conflicts with other instructions and cause issues building a target.
This is the spiritual backport of #11877, but because the state of the convert_to_target() function on stable/0.46 is very different very little code is carried over from the version on main and stable/1.0, basically only the tests. This is actually closer in implementation to the equivalent PR on qiskit-ibm-runtime: Qiskit/qiskit-ibm-runtime#1443 as the internal conversion function in that repository is very similar to the function on the stable/0.46 branch.
Details and comments

spiritual backport of https://github.com/Qiskit/qiskit/pull/11877


add documentation for support custom claim mapping feature

Purpose
Add documentation for support custom claim mapping feature

@tharmini , please address the review comments.

We will send a separate PR addressing the changes required


: Update how generate emissions pre-generates

Pull Request Key Information
Reason for change
The emissions that are generated for pre-sim start date were not ordered correctly
What was changed

Update generate emissions in sources
Update existing unit tests
Add more unit tests to ensure the dates are correct.

Intended Purpose
Update the code such that the emissions are generated based on oldest date first
Level of version change required
Patch
Testing Completed
All unit tests pass - old and new
results.txt
The E2E tests have been updated to reflect the new generate emissions changes.
V4_simple_non_repairable_emissions_300e5ec164c2571e1d50afdafe37c6ce2d1ad8a3.log
V4-simple_repairable_emissions_300e5ec164c2571e1d50afdafe37c6ce2d1ad8a3.log
Target Issue
Put GitHub keywords to link the pull request to the target issue here. For example: Closes #XX.
Additional Information
Include any other important information here.

Was this a bug or is this a change?

Was this a bug or is this a change?

It was a change. Previously the dates for the pre-sim start went from newest to oldest, and then all emissions after that went from oldest to newest. now it's constant oldest to newest.

Does either activate emissions or emissions logic around pre-simulation emissions need to be updated as part of this change?

Does either activate emissions or emissions logic around pre-simulation emissions need to be updated as part of this change?

Nope.


nginx not found - edge release

try to pack ip2location libs to deb and install them like nginx-custom and luajit.

https://github.com/EpicMorg/docker-scripts/pull/39


[docs] Minor Update to remove ° notations

[x] I have followed (at least) the PR section of the contributing guide.

(Though I might have done something wrong since it's saying can't automatically merge.)

Though I might have done something wrong since it's saying can't automatically merge

A rebase should fix that


Version 2.5.0

I upgraded my projects to v2.5.0, and now CI is failing on my .NET Framework 4.7.1 tests (they still pass under .net Core 2.1).
Could not load file or assembly 'System.Runtime.Extensions, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies.
Going to have to downgrade for now.

I updated the core library to use netcoreapp2.0 instead of netstandard because I needed to add support for a particular area. That's probably the problem

Facing same error here. Workaround it by downgrade to 2.4.0.

Maybe coverlet.msbuild and coverlet.msbuild.tasks can be merged and published using the new way, instead of manully specify which dlls should be packed. With dotnet build and <GeneratePackageOnBuild>true</GeneratePackageOnBuild>, MSBuild will help you to handle the dependencies. I'll try to do a POC.


Documentation https://github.com/nkolban/esp32-snippets/blob/master/cpp_utils/ArduinoBLE.md

Hello, Neil
in the file ArduinoBLE.md you suggest that if we want to debug an issue change the debug level modifying the line
#define CONFIG_LOG_DEFAULT 1
from one to five in sdkconfig.h
But when I search in this file I found instead
#define CONFIG_LOG_DEFAULT_LEVEL 1
Is this the line I need to change?
Thanks for your great work, best regards

Thank you sir.  I'm 99.9% you are correct.  I have updated the file to reflect the correct setting.  MANY thanks for reporting this.

Closing for just now.  Don't hesitate to re-open as needed.


Add Gradle 8 support

This is a pull request that addresses the error occurring in this pull request (https://github.com/gdelataillade/alarm/pull/130).
I also included an upgrade of the Gradle version that was missed last time.
Additionally, there are modifications made within the 'example' directory.

Hi @tattuu
That's awesome thank you so much !
I want to test your PR but I'm having a lot of trouble updating Java (11 -> 17).
I have installed Java 17 but it still says:
Android Gradle plugin requires Java 17 to run. You are currently using Java 11.
When I do ./gradlew --version I have:
------------------------------------------------------------
Gradle 8.5
------------------------------------------------------------

Build time:   2023-11-29 14:08:57 UTC
Revision:     28aca86a7180baa17117e0e5ba01d8ea9feca598

Kotlin:       1.9.20
Groovy:       3.0.17
Ant:          Apache Ant(TM) version 1.10.13 compiled on January 4 2023
JVM:          17.0.10 (Amazon.com Inc. 17.0.10+7-LTS)
OS:           Mac OS X 14.2.1 aarch64

When I do java --version I have:
openjdk 17.0.10 2024-01-16 LTS
OpenJDK Runtime Environment Corretto-<IP_ADDRESS>.1 (build 17.0.10+7-LTS)
OpenJDK 64-Bit Server VM Corretto-<IP_ADDRESS>.1 (build 17.0.10+7-LTS, mixed mode, sharing)

Do you have any idea ?

Hi @tattuu
Thank you so much for sharing your work, I'm adding it to the plugin !

I'm glad that the merge went smoothly!
I am happy to have been able to contribute to you and this project!
I wish for the development of both you and the project.

Thank you ! You're officially a contributor of the plugin now, congratulations !


@else should be placed on same line as previous curly brace

http://sass-guidelin.es/#conditional-statements

Thanks! Standards are good - can't auto-merge this but we'll get it in soon.

I just got one question. What if there is a comment above the @else condition?
See https://github.com/zurb/foundation/blob/master/scss%2Ffoundation%2Fcomponents%2F_grid.scss#L54

You could move the comment inside the block, and then you'd be able to pair all the @else blocks together.

Ok, I'll fix it soon

Hey, really sorry for letting this get super stale! Now that Foundation 6 is out, we won't be making any more codebase improvements to Foundation 5. We're always looking for contributions to the new codebase, though :)


added linux-build-process #8

Added linux build process
Closes #8

Seems like there is a problem with the travis-ci? #22

@joshghent any idea? Never worked with travis before

Don't worry it looks like it fails with the latest version of node due to a dependency. I've remove this testing in the master branch. Thank you for your contribution! 🎉 This is amazing!


chore: init

Codecov Report

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

@@           Coverage Diff            @@
##             main        #1   +/-   ##
========================================
  Coverage        ?   100.00%
========================================
  Files           ?         4
  Lines           ?        60
  Branches        ?         7
========================================
  Hits            ?        60
  Misses          ?         0
  Partials        ?         0

Continue to review full report at Codecov.

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

:tada: This PR is included in version 0.0.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Unable to connect Apache Age-Viewer to PostgreSQL Database

I have tried all the steps provided in the documentation to connect Apache Age-Viewer to my PostgreSQL database, but I am still unable to connect. I have verified that the PostgreSQL server is running, the user and password are correct and have the necessary permissions, and the specified port (5455) is open and accessible. But I still can't connect.
I am using the following versions:
Apache Age-Viewer: 14.16.0
PostgreSQL: 12.13

Was it working at first

@moiz697 can you share the logs of your postgres server.
If you are using docker then run docker logs --follow <container_name>
The container_name should be myPostgresDb if you are using default setup.
Also, what error are you getting on the frontend?

What error are you getting on the frontend?

@AhmarZaidi

yes container name is myPostgresDb

Was it working at first ?

nope trying for first time

First try psql -U postgresUser -d postgresDB -p 5455 -h localhost   in terminal  from outside and see if it's connecting.

First try psql -U postgresUser -d postgresDB -p 5455 -h localhost  in terminal from outside docker and see if it's connecting.

yes it is connecting to terminal now

yes it is connecting to terminal now

Please share the log, of terminal where you ran age-viewer, once you click on 'Connect' after filling the postgreSQL server, there will be some error showing if unable to connect.

@AhmarZaidi  yes container name is myPostgresDb

Okay, what error are you getting on the viewer.

@AhmarZaidi  yes container name is myPostgresDb

Okay, what error are you getting on the viewer.

psql: connection to server at "localhost" (<IP_ADDRESS>), port 5455 failed: Connection refused
Is the server running on that host and accepting TCP/IP connections?
connection to server at "localhost" (::1), port 5455 failed: Cannot assign requested address
Is the server running on that host and accepting TCP/IP connections?

@moiz697 Found a similar query here have a look.

Hello Moiz,
As discussed in meeting, you can close the issue as it is solved.


incremental build/watch tasks

https://github.com/gulpjs/gulp#incremental-builds

Can you provide more information on this issue? Sorry, I don't get whats the case here.

Sorry for the lack of information here. This allows gulp to only handle files that are actually changed in a watch or build cycle. This might improve performance a little bit in some cases.

Closing. Outdated.


Dockerized the app and supported docker compose for single launch point

Description

Introduced dockerfile to run app as a individual container.
Introduced docker-compose.yaml to serve as base yaml for dev(docker-compose.dev.yaml) abd prod(docker-compose.prod.yaml).
Added entrypoint.sh for running seed db data queries.
Updated README.md and .env.example for env valiables update.
Updated seed-prod.ts to use env variables.

Related Issues
#41

Check List

Check both dev and prod application buildup and running

[x] I have run npx turbo format to ensure the code follows the style guide.
[x] I have run npx turbo test to check if all tests are passing.
[x] I have run npx turbo build to check if the website builds without errors.

Hi @AugustinMauroy
Sorry to raise a another PR with same code change.
I just accidently raised PR with my another git username and mail id.
Please review it once your are back.
Thanks

Hello, there have been changes on the main, you would be updating t'as branch and all will be good.

Hi @AugustinMauroy
Updated the docker support from mysql to psql and also resolved merge conflicts.


[!] Error: 422 (Unprocessable Entity): Invalid search. Your query could not be parsed

Censys:
{'used': 0, 'allowance': 250, 'resets_at': '2022-02-04 17:10:03'}
[!] Error: 422 (Unprocessable Entity): Invalid search. Your query could not be parsed
https://github.com/f4rber/BruteMiner

Hi there, that project appears to be using an out-of-date query: 80.http.get.body: Awesome Miner we have since updated our Search Query Language and the new query that can search across all ports would look like this:
services.http.response.body: "Awesome Miner"

Search Results

As I have made a branch that fixes that issue here: thehappydinoa/BruteMiner:update-censys-queries I am going to go ahead and close this issue. Thanks for reporting.


XInputNative axes don't near-match default Win10 behavior (sans triggers)

Solution: Dedicate Axis 5 to Left Trigger and Axis 6 to Right Trigger.
With an Xbox One controller, the controls in the following screenshot would normally be...

Axis 1-
Axis 1+
Axis 2-
Axis 2+
Axis 3-
Axis 3+
Axis 4-
Axis 4+

With Axis 5 being shared by the triggers.

Here's two examples of how Xbox 360/One controllers normally map
https://github.com/SnowyMouse/chimera/blob/master/controller_config/windows/xbox_360.txt
https://github.com/SnowyMouse/chimera/blob/master/controller_config/windows/xbox_one.txt

It's also possible that the classic PC ports of Halo:CE were made with a very different understanding of DirectInput seeing as the Axes are unnamed and buttons start at 0 instead of 1.

See the documentation: https://github.com/samuelgr/Xidi#mapping-controller-buttons-and-axes
You will want to use XInputSharedTriggers, not XInputNative.

I am not sure how this particular game (shown in the screenshot) is interpreting axis numbers, but my guess it gets them as the . Internally Xidi just numbers them in the order X, Y, Z, RotX, RotY, and RotZ.
Is there a particular reason why the specific axis number matters? As far as Xidi is concerned, making this change is just a matter of swapping the order of a few constant values.

Closing because the axes have been numbered this way for several years now and I haven't heard of any applications breaking because the internal axis numbering is different.


ENH: Replace initial FLIRT with mri_coreg, use -basescale 1 for FLIRT-BBR

Rebases #2607 on master.
Fast-tracked to get this into the next 21.0.0 RC. Need to figure out numpy failures in the docker image to patch 20.2.x.

@mgxd We need to update the reports and boilerplate to indicate that we're using mri_coreg. Not sure it's worth doing before an RC. Let me know if I should work on this or start a new PR.

Once we get niworkflows passing, I'll kick off the release chain, but I don't expect we'll get to fmriprep until Monday. Depending on how long you think those updates will take, you can probably just do it here.

Ah, niworkflows is going to be at least two hours to finish the mask regression tests. I'll see what I can get to by 5.

Not really sure how to fix this in the citation boilerplate (from artifacts:
Functional data preprocessing

: For each of the 1 BOLD runs found per subject (across all
tasks and sessions), the following preprocessing was performed.

Preprocessing of B0 inhomogeneity mappings

: A total of 1 fieldmaps were found available within the input
BIDS structure for this particular subject.
A deformation field to correct for susceptibility distortions was estimated
based on *fMRIPrep*'s *fieldmap-less* approach.
The deformation field is that resulting from co-registering the EPI reference
to the same-subject T1w-reference with its intensity inverted [@fieldmapless1;
@fieldmapless2].
Registration is performed with `antsRegistration`
(ANTs 2.3.3), and
the process regularized by constraining deformation to be nonzero only
along the phase-encoding direction, and modulated with an average fieldmap
template [@fieldmapless3].
First, a reference volume and its skull-stripped version were generated
from the shortest echo of the BOLD run using a custom
methodology of *fMRIPrep*.
[...]

Pretty sure it should be
Preprocessing of B0 inhomogeneity mappings

: A total of 1 fieldmaps were found available within the input
BIDS structure for this particular subject.
A deformation field to correct for susceptibility distortions was estimated
based on *fMRIPrep*'s *fieldmap-less* approach.
The deformation field is that resulting from co-registering the EPI reference
to the same-subject T1w-reference with its intensity inverted [@fieldmapless1;
@fieldmapless2].
Registration is performed with `antsRegistration`
(ANTs 2.3.3), and
the process regularized by constraining deformation to be nonzero only
along the phase-encoding direction, and modulated with an average fieldmap
template [@fieldmapless3].

Functional data preprocessing

: For each of the 1 BOLD runs found per subject (across all
tasks and sessions), the following preprocessing was performed.
First, a reference volume and its skull-stripped version were generated
from the shortest echo of the BOLD run using a custom
methodology of *fMRIPrep*.
[...]

Codecov Report

Merging #2625 (c52206f) into master (d2ad203) will decrease coverage by 0.02%.
The diff coverage is 20.00%.

@@            Coverage Diff             @@
##           master    #2625      +/-   ##
==========================================
- Coverage   45.46%   45.43%   -0.03%
==========================================
  Files          41       41
  Lines        3161     3163       +2
==========================================
  Hits         1437     1437
- Misses       1724     1726       +2

Impacted Files
Coverage Δ

fmriprep/workflows/bold/registration.py
8.88% <20.00%> (-0.10%)
:arrow_down:

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 d2ad203...c52206f. Read the comment docs.

@oesteban As the master of the literate workflows, your advice on how to rearrange the boilerplate text would be appreciated.

I was looking into this earlier - from my understanding, order largely depends on the graph order, though __predesc__, __desc__, and __postdesc__ can somewhat help. LiterateWorkflow likely needs a change to allow more fine control within these sections.

@oesteban As the master of the literate workflows, your advice on how to rearrange the boilerplate text would be appreciated.

I'm not sure this problem has been introduced here - we probably should get this merged and keep investigating why the boilerplate is garbled.

order largely depends on the graph order, though __predesc__, __desc__, and __postdesc__ can somewhat help. LiterateWorkflow likely needs a change to allow more fine control within these sections.

Agreed.

No it wasn't introduced here. Was just interested in fixing it. I'm okay with merging this as is.


Compiler error

Hi b3nn,
using the same avr studio version i'm getting the following error while Building. I've Checked the Makefile for mismatched Path's but all seem to be ok. Can you confirm that the current Codebase is still ok on Github? Is there any ability of setting the compiler to verbose mode, so it puts out more Status messages to determinate when in the process the compiler is missing something (like in the output below "the system cannot find the specified path.")
Thanks for helping, I would be really happy getting this project build and try building the breadboard circut you described.
------ Build started: Project: 3DVisionAVR, Configuration: Debug AVR ------
Build started.
Project "3DVisionAVR.cproj" (default targets):
Target "PreBuildEvent" skipped, due to false condition; ('$(PreBuildEvent)'!='') was evaluated as (''!='').
Target "CoreBuild" in file "C:\Program Files (x86)\Atmel\Studio\7.0\Vs\Compiler.targets" from project "C:\Users\usr\Documents\test\3DVisionAVR\3DVisionAVR.cproj" (target "Build" depends on it):
Task "RunCompilerTask"
Shell Utils Path C:\Program Files (x86)\Atmel\Studio\7.0\shellUtils
C:\Program Files (x86)\Atmel\Studio\7.0\shellUtils\make.exe -C "C:\Users\usr\Documents\test\3DVisionAVR" -f "makefile" all
make: Entering directory 'C:/Users/usr/Documents/test/3DVisionAVR'
the system cannot find the specified path.
the system cannot find the specified path.
the system cannot find the specified path.
' [INFO]    :' Begin compilation of project "3DVisionAVR"...
""
avr-gcc (AVR_8_bit_GNU_Toolchain_3.6.2_1778) 5.4.0
Copyright (C) 2015 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
' [GCC]     :' Compiling C file "Emitter.c"
avr-gcc -c -pipe -gdwarf-2 -g2 -mmcu=atmega32u4 -fshort-enums -fno-inline-small-functions -Wall -fno-strict-aliasing -funsigned-char -funsigned-bitfields -ffunction-sections -I. -DARCH=ARCH_AVR8 -DDMBS_ARCH_AVR8 -mrelax -fno-jump-tables -x c -O2 -std=gnu99 -Wstrict-prototypes -DF_CPU=16000000UL -DUSE_LUFA_CONFIG_HEADER -IConfig/ -I. -I../lufa/LUFA/.. -DARCH=ARCH_AVR8 -DBOARD=BOARD_NONE -DF_USB=16000000UL   -MMD -MP -MF obj/Emitter.d Emitter.c -o obj/Emitter.o
Assembler messages:
RUNCOMPILERTASK(0,0): error: can't create obj/Emitter.o: No such file or directory
C:\Users\usr\Documents\test\3DVisionAVR\Emitter.c(314,1): error: error writing to -: Invalid argument
}
^
compilation terminated.
make: *** [obj/Emitter.o] Error 1
C:\Users\usr\Documents\test\lufa\LUFA\Build\DMBS\DMBS\gcc.mk(225,1): error: recipe for target 'obj/Emitter.o' failed
make: Leaving directory 'C:/Users/usr/Documents/test/3DVisionAVR'
The command exited with code 2.
Done executing task "RunCompilerTask" -- FAILED.
Done building target "CoreBuild" in project "3DVisionAVR.cproj" -- FAILED.
Done building project "3DVisionAVR.cproj" -- FAILED.
Build FAILED.
========== Build: 0 succeeded or up-to-date, 1 failed, 0 skipped ==========

Hi KoalaRX,
Yes, it's still building for me and it does look like we're using the same version of AVR Studio. The "the system cannot find the specified path" error message makes me think there could be a permissions issue with accessing your user's Documents directory.  Have you tried moving the source code to something outside of your Documents directory and then building from there? I'm building from "D:\Code" and haven't seen this issue, but this is the only project I'm using AVR Studio with.


Fix shared directory ownership and enable w+r on it

The first piece of this commit is executing on the workaround described
in [1] for the missing ownership on the _shared directory [2].
The second pieces essentially disable the ReadOnly attribute on the
mounted _shared directory so it is writable by everyone (admin and
users)[3].
[1] https://github.com/2i2c-org/infrastructure/issues/440
[2] https://github.com/2i2c-org/infrastructure/issues/810#issuecomment-968307309
[3] https://github.com/2i2c-org/infrastructure/issues/810#issuecomment-968308530

As you can see from the linked comment, I have successfully tested this on openscapes staging.
Wondering if they are not going to write themselves to top of each other... but I made that clear as a risk in my refereced comment. Do you foresee any other risk?

The openscapes folks re-confirmed they want the writable shared space so going to merge this one now.
Thanks all for the review on Sunday time!


[SPARK-39880][SQL] V2 SHOW FUNCTIONS command should print qualified function name like v1

What changes were proposed in this pull request?

This PR fixes a mismatch between v1 and v2 SHOW FUNCTIONS command: v1 prints qualified function names such as spark_catalog.db1.f1, but v2 only prints the function name. V2 command should follow v1 behavior which makes more sense.
This PR also updates the SHOW FUNCTIONS test suites to match the new behavior.
Why are the changes needed?

keep v1 and v2 commands consistent.
Does this PR introduce any user-facing change?

No, v2 SHOW FUNCTIONS is new in Spark 3.4 (not released)
How was this patch tested?

updated tests

cc @MaxGekk

+1, LGTM. Merging to master.
Thank you, @cloud-fan and @beliefer for review.


a basic classifier

added a basic classification model
added some custom functions

no conflicts with the base branch. Okay to merge.


some improvements

made character detection more robust (was not checking limits, so it was segfaulting on windows)
added capability to accept utf-8 strings directly

@skeeto any chance this may be accepted/merged?
We plan to embed pdjson in upcoming Pocohttp://github.com/pocoproject/poco release, so it would be nice to be aligned with upstream

Sorry for dragging my feet. I wanted to run your changes against JSONTestSuite to make sure nothing broke. @dhobsd took charge of all of that earlier this year, and so I wasn't familiar with the process myself. I kept putting that off.
Everything still passes and it looks like you've successfully made it stricter about malformed UTF-8. Some tests with "undefined" results have switched from passing to failing. Here are the original results (light blue == passing, dark blue == failing):

Here it is with your PR:

So I see no reason not to merge this. Thanks!

+1, I know this is merged; the new failures are good failures that would've been defined sensibly if JS wasn't specified around utf-16. Ideally, the rest of these would fail as well, but that's another project :)

Fwiw, should open another pr against the test suite for these changes since it imports libraries into the repo directly, not thru externals (if you've not done that already)

thanks a lot @skeeto and @dhobsd


Switch to other Window WPF

We develop a WPF application and I have an obstacle when using the driver. During a test I swith to some other window (Login-->Dashboard panel) where other elements are located but the driver ,,see" only those from previous one.
Is impossible to find any element on the window using  avaliable methods and also using:
	List<WebElement> elements = driver.findElements(By.xpath("//*"));

	for (WebElement el : elements){

		System.out.println(el.getText());

}

i am getting elements form previous window.
Have you got any idea how to handle this problem?
Thank you in advance for answer.
Best regards,

Better support for doing this is coming in v1.0
Today you would need to create a separate "root" session.

Hi @dominik1776,
Not sure how you set up your test and test application. But the following test working well showing all the unique elements belonging to each specific windows:
foreach (var windowHandle in newlyOpenedEdgeWindows)
{
    session.SwitchTo().Window(windowHandle);
    Assert.AreEqual(session.CurrentWindowHandle, windowHandle);
    Assert.AreNotEqual(windowHandle, previousWindowHandle);
    previousWindowHandle = windowHandle;

    var elements = session.FindElementsByXPath("//*");
    foreach (WindowsElement el in elements)
    {
        System.Diagnostics.Debug.Print(el.Id);
    }

    EdgeBase.CloseEdge(session);
}

Can you please try it out? In the sample code, we can switch to different window and successfully find the right elements belonging the right window. The snippet above is taken from https://github.com/Microsoft/WinAppDriver/blob/v1.0-RC/Tests/WebDriverAPI/Window.cs#L154


[Q]: which are the benefits of gams.jl over the standard solver calling?

hello,
it is not clear from the description which are the benefit of using this package over calling the solver directly. For instance, the transportation problem in the example can be solved by replacing
model = Model(GAMS.Optimizer)
   set_optimizer_attribute(model, MOI.Silent(), !verbose)

with
model=Model(Gurobi.Optimizer)
given that, i have a licensed version of Gurobi.
So, which are the benefits of the former over the latter approach

Great question. Honest answer from a technical perspective: I personally don’t see a benefit for this particular use case (solving LPs using Gurobi). Even worse, you will experience a minimal time overhead by using Gurobi through GAMS on a JuMP model in comparison to the direct Julia interface. Due to legal reasons, rather than filling internal GAMS data structures directly in the MathOptInterface optimizer, GAMS.jl exports the JuMP data as a .gms file and calls GAMS, which then exports the result as .gdx. Finally, GAMS.jl imports this .gdx file. While the GDX import/export is super-efficient, exporting the .gms file generates an overhead that grows with the problem size (mainly dependent on the number of non-zeros). However, in most practical cases we believe this overhead to be very acceptable. Note, that I added the transport problem mainly because it is referred to a lot in the GAMS documentation (e.g. this tutorial) and GAMS users will certainly recognize it.
The situation definitely changes for nonlinear programming though.  Second, there are user requests in the JuMP community for accessing nonlinear solvers that are only accessible through GAMS (see https://discourse.julialang.org/t/using-antigone-from-julia/10917). Third, in the JuMP documentation (https://jump.dev/JuMP.jl/v0.20/nlp/#Factors-affecting-solution-time-1) it says:

The function evaluation time, on the other hand, is the responsibility of the modeling language. JuMP computes derivatives by using reverse-mode automatic differentiation with graph coloring methods for exploiting sparsity of the Hessian matrix [1]. As a conservative bound, JuMP's performance here currently may be expected to be within a factor of 5 of AMPL's.

While I find it a bit hard to give reliable statistics on this matter, we see a similar tendency in the case of GAMS. When function evaluations are dominant, this circumstance may result in better solution performance when using, for example, GAMS.jl rather than a native solver interface (even with the overhead described above). Finally, using GAMS can be more convenient. While simply doing
using Pkg
Pkg.add("Ipopt")
using Ipopt, JuMP
model = Model(Ipopt.Optimizer)

for example probably doesn’t give you the best Ipopt experience (mainly due to the default BLAS and linear solver), a
using Pkg
Pkg.add("GAMS")
using GAMS, JuMP
model = Model(GAMS.Optimizer)
set_optimizer_attribute(model, GAMS.Solver, "ipopth")

can do.
In addition, there may be other considerations like technical support from a commercial company, free community licenses or discounts on solver packages (see section "Package Discounts" in price lists) that can result in a benefit when using GAMS.jl. But again, I doubt this is true for you, because you are using Gurobi (for which you have a license).

@renkekuhlmann  Thank you very much for the detailed explanation. I just mentioned Gurobi as an example (actually, I also have a license for the Xpress solver, which it is more efficient for solving lp problems than Gurobi).


service is not running   it is in doze mode

i create a new job and write log when it is running. it is correctly but it does not work after a certain time
i think it is in doze mode. how can set it is run every time? Can you help me?
FirebaseJobDispatcher dispatcher = new FirebaseJobDispatcher(new GooglePlayDriver(this));
Job job = dispatcher.newJobBuilder()
.setLifetime(Lifetime.FOREVER)
.setService(TimelyService.class)
.setTag("timely_service")
.setRecurring(true)
.setTrigger(Trigger.executionWindow(0, Constants.KEY_TIME_SERVICE_INTERVAL)) // 2 min
.setRetryStrategy(RetryStrategy.DEFAULT_EXPONENTIAL)
.build();
dispatcher.mustSchedule(job);

it is working as intended when it doesn't run in doze and doze on the go mode. it may run during doze maintenance windows though.


investigate issues with beacon node load balancing [3D]

validator node using a remote beacon node on a service provider, seem to periodically have issues with lower attestation performance

one avenue would be to have a prater or pyrmont node be validator only and using a remote beacon node provider

how do we measure performance of a validator when we dont own the beacon node?

As part of the investigation, disabled early attestation production on a validator node on prater that used a remote beacon node.
Xvalidators-early-attestations-enabled: False

The outcome was that attestation inclusion rate much more closely tracked with expectations.
It seems fairly clear that this configuration option needs to be publicised for use in this kind of configuration, so that other validator clients can gain similar improvements.
I created a limited dashboard to monitor using grafana:

local validator count
published attestations, blocks, aggregations
scheduled blocks, attestations (eg. if you're about to get to propose a block, you might not want to restart)
current epoch (will be time based epoch calculated by validator client)
invalid events received on the event stream
event stream disconnections
cpu / mem/GC stats

It'd be helpful to get some context of the beacon node to allow things such as

attestation effectiveness for validators I'm running
head slot of the beacon node (could sign up for head events and put a metric on that easily)
sync status of the beacon node

raised #4225 also. closing spike.


Map Stamen Watercolor 503

When I zoom in to the max level some tiles are missing and server responds with errors. Why is this happening? It just happened in this zoom level, not in the rest.
These are some of the errors from the console regarding that issue. Also I attach a screenshot
123161.jpg:1 GET http://c.tile.stamen.com/watercolor/18/208755/123161.jpg 503 (Service Unavailable)
c.tile.stamen.com/watercolor/18/208756/123160.jpg:1 GET http://c.tile.stamen.com/watercolor/18/208756/123160.jpg 503 (Service Unavailable)
123161.jpg:1 GET http://d.tile.stamen.com/watercolor/18/208756/123161.jpg 503 (Service Unavailable)
123159.jpg:1 GET http://a.tile.stamen.com/watercolor/18/208755/123159.jpg 503 (Service Unavailable)
123159.jpg:1 GET http://b.tile.stamen.com/watercolor/18/208756/123159.jpg 503 (Service Unavailable)
123160.jpg:1 GET http://b.tile.stamen.com/watercolor/18/208755/123160.jpg 503 (Service Unavailable)
123158.jpg:1 GET http://a.tile.stamen.com/watercolor/18/208756/123158.jpg 503 (Service Unavailable)
123158.jpg:1 GET http://d.tile.stamen.com/watercolor/18/208755/123158.jpg 503 (Service Unavailable)

I discovered the same Issue, but it happens only in Safari (on Mac) not in SeaMonkey or Chrome. I work with some videoOverlay - it seems to happen specially there -see www.dominique.turzer.eu

Any updates on this? It still happens to me (Firefox, Mac OS 10.14), e.g<EMAIL_ADDRESS>

Those requests work for me.

Hm, yeah, now they work. Could you think of any other reason why they might not work at times and I’m bombarded with 503s? Switched the tileset for now so it’s nothing urgent, but I’m curious if I am missing something or could optimize the tile calls on the client somehow.

The problem is still here. See https://stamen-tiles-d.a.ssl.fastly.net/toner-lite/17/38091/46411.png whether using toner-lite or just toner.

Key: terrain/18/134620/86487.png
RequestId: D6KW7W7BTVJR8QJR
HostId: lfzugTQU9IUUEUYFHbe0E+gHfhie/zNd+03nx5K+wkAowh+91Kr5F41RaVDmBmE0+7YOuyxJ4w4=

How do people work around this?


Add compression

Added compression as --compress or -c, closes #5.
Quite a few changes here to support this. It will compress the folder (as a tar.gz in the backup directory), calculate the raw size of the backup then delete the folder and compare the backed up size to the compressed size.

Merging.


Pin python requests to version 2.23.0 to resolve pip installation error/warning

Describe the bug
botbuilder-integration-aiohttp requires 2.23.0 version of requests.  Most requirements.txt files have either no version pinned or have >=2.18.0.  We should pin to 2.23.0 to avoid a pip warning:
To Reproduce
Steps to reproduce the behavior:

pip install in (for example) /BotBuilder-Samples/samples/python/57.teams-conversation-bot
Receive error message:

ERROR: botframework-connector 4.10.1 has requirement requests==2.23.0, but you'll have requests 2.18.4 which is incompatible.

Expected behavior
No errors

I'd be interested in fixing and should be a pretty easy issue.

If you want to, @loganballard, you're more then welcome to put in a PR for this. I've give the python samples a look over, and see where all this needs to be applied.


npm start

hi,
i've installed all as in tuto http://www.youtube.com/watch?v=0scZXATiGSY&index=3&list=PL55RiY5tL51olfU2IEqr455EYLkrhmh3n on centos 6.7 x86_64
but "npm start" exit with errors. thanx.
npm-debug.log:
0 info it worked if it ends with ok
1 verbose cli [ 'node', '/usr/bin/npm', 'start' ]
2 info using<EMAIL_ADDRESS>3 info using<EMAIL_ADDRESS>4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>6 silly lifecycle<EMAIL_ADDRESS>no script for prestart, continuing
7 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>8 verbose lifecycle<EMAIL_ADDRESS>unsafe-perm in lifecycle true
9 verbose lifecycle<EMAIL_ADDRESS>PATH: /usr/lib/node_modules/npm/bin/node-gyp-bin:/home/diamo/eclipse_ws/ng2/node_modules/.bin:/usr/bin:/usr/lib64/qt-3.3/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/diamo/bin
10 verbose lifecycle<EMAIL_ADDRESS>CWD: /home/diamo/eclipse_ws/ng2
11 silly lifecycle<EMAIL_ADDRESS>Args: [ '-c', 'concurrent "npm run lite" ' ]
12 silly lifecycle<EMAIL_ADDRESS>Returned: code: 1  signal: null
13 info lifecycle<EMAIL_ADDRESS>Failed to exec start script
14 verbose stack Error<EMAIL_ADDRESS>start: concurrent "npm run lite"
14 verbose stack Exit status 1
14 verbose stack     at EventEmitter. (/usr/lib/node_modules/npm/lib/utils/lifecycle.js:239:16)
14 verbose stack     at EventEmitter.emit (events.js:98:17)
14 verbose stack     at ChildProcess. (/usr/lib/node_modules/npm/lib/utils/spawn.js:24:14)
14 verbose stack     at ChildProcess.emit (events.js:98:17)
14 verbose stack     at maybeClose (child_process.js:766:16)
14 verbose stack     at Process.ChildProcess._handle.onexit (child_process.js:833:5)
15 verbose pkgid<EMAIL_ADDRESS>16 verbose cwd /home/diamo/eclipse_ws/ng2
17 error Linux 2.6.32-573.7.1.el6.centos.plus.x86_64
18 error argv "node" "/usr/bin/npm" "start"
19 error node v0.10.41
20 error npm  v3.7.1
21 error code ELIFECYCLE
22 error<EMAIL_ADDRESS>start: concurrent "npm run lite"
22 error Exit status 1
23 error Failed at the<EMAIL_ADDRESS>start script 'concurrent "npm run lite" '.
23 error Make sure you have the latest version of node.js and npm installed.
23 error If you do, this is most likely a problem with the angular2-boilerplate package,
23 error not with npm itself.
23 error Tell the author that this fails on your system:
23 error     concurrent "npm run lite"
23 error You can get information on how to open an issue for this project with:
23 error     npm bugs angular2-boilerplate
23 error Or if that isn't available, you can get their info via:
23 error     npm owner ls angular2-boilerplate
23 error There is likely additional logging output above.
24 verbose exit [ 1, true ]

and in console:
[diamo@ulhikma ng2]$ npm run lite

<EMAIL_ADDRESS>lite /home/diamo/eclipse_ws/ng2
lite-server

Did not detect a bs-config.json or bs-config.js override file.  Linux 2.6.32-573.7.1.el6.centos.plus.x86_64
npm ERR! argv "node" "/usr/bin/npm" "run" "lite"
npm ERR! node v0.10.41
npm ERR! npm  v3.7.1
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>lite: lite-server
npm ERR! Exit status 8
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>lite script 'lite-server'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the angular2-boilerplate package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     lite-server
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs angular2-boilerplate
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls angular2-boilerplate
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     /home/diamo/eclipse_ws/ng2/npm-debug.log

I noticed that some people seem to have problems with "npm start". Assuming that "npm install" worked correctly I hope that the answers/ suggestions provided in these links help you:

https://github.com/angular/angular/issues/6097
http://stackoverflow.com/questions/34335340/angular2-quickstart-npm-start-is-not-working-correctly

Please let me now if this fixes your problem!

i found out that this problem comes from starting lite-server. i use centos 6, and i haven't solved the issue. i decided to use apache web-server instead lite-server. i corrected package.json (deleting "npm run lite") and start local apache web server.  now,
$npm start
starts only tsc as watcher and all work simillar with tuto. but i prefer to do
$tsc -w
being in the project dir instead
$npm start
package.json:
{
"name": "angular2-boilerplate",
"version": "1.0.0",
"scripts": {
"tsc": "tsc",
"tsc:w": "tsc -w",
"lite": "lite-server",
"start": "concurrent "npm run tsc:w""
},
"license": "ISC",
"dependencies": {
"angular2": "2.0.0-beta.3",
"systemjs": "0.19.6",
"es6-promise": "^3.0.2",
"es6-shim": "^0.33.3",
"reflect-metadata": "0.1.2",
"rxjs": "5.0.0-beta.0",
"zone.js": "0.5.11"
},
"devDependencies": {
"concurrently": "^1.0.0",
"lite-server": "^2.0.1",
"typescript": "^1.7.5"
}
}

Yes, it comes from starting the lite server. However in the links I posted, other people were having problems with lite server as well. Maybe the solutions to their issues help you, too.

The alteration of inotify user watches in this answer worked for me. Mint 17.3

Tried npm install in Administrative Mode and it's good now..

i have solved it in centos 6. the reason is that gulp/watcher need more memo.
add a string fs.inotify.max_user_watches = 524288 into /etc/sysctl.conf.
and restart os or sudo sysctl -p

This is my pacakge.json scripts how do i do the same with gulp ?
"scripts": {
"lite": "lite-server",
"gulp": "gulp",
"start": "concurrent "npm run gulp" "npm run lite" "
},


Loading after scroll

After first load of likes etc., when scrolling off the screen and returning back, the snapshot has no data and it doesn't refresh.

Maybe observables from https://github.com/ReactiveX/rxdart might help us?

BehaviorSubject fixes the problem.


Cleanup and refactoring throughout the Baja codebase

Added inline Rustdoc comments everywhere, throughout the library.
Factored out important constants (e.g. the cryptographic certificate template into explicit constants declared in the source file.
Generalized the VeracruzIdentity type in veracruz-utils and used this type in Baja in place of an explicit triple of u32, Certificate, and Vec<VeracruzRole> values.
Removed uneccessary allocations/clones throughout the codebase, and other bits of Rust cleanup preferring reference passing rather than value passing where we can get away with it.
Added inline hints for small functions.
Removed unnecessary error type on the creation of Baja sessions, and propagated this change onwards.
(Trivial) removed non-breaking space characters in various RustDoc comments (across the Veracruz codebase) which cause RustDoc to not render correctly in favour of a proper space character.
Generalized some functions taking Strings as inputs to functions that take generic arguments that can be converted into Strings.

Various other small improvements throughout.

AWS CodeBuild CI Report

CodeBuild project: Veracruz
Commit ID: c09b9442c95ae4afe7bb63cac8a70d936918412c
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: Veracruz
Commit ID: 7903687ade3d6288f3c2e0986f27e464c6168081
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: Veracruz
Commit ID: 4b4035014e2dcdcf19fbe2f0200b3afc3d42124a
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: Veracruz
Commit ID: c5c5e9591d20cbff024b75e45248deb4379480df
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: Veracruz
Commit ID: b97a0f60ec2f83607a7b86b71ca9032354a06486
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: Veracruz
Commit ID: 216309a85b315fbb4ea55e01d44548ac88f07ad7
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

Let's wait for @dreemkiller's comments/approval before merging on this.

AWS CodeBuild CI Report

CodeBuild project: Veracruz
Commit ID: aa29ea8fb88a79105e04b151c1bb44c11a16c967
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

1+1=1, merging.


docs: fix simple typo, statisfy -> satisfy

There is a small typo in lifelines/tests/test_estimation.py.
Should read satisfy rather than statisfy.
Semi-automated pull request generated by
https://github.com/timgates42/meticulous/blob/master/docs/NOTE.md

Thanks! Cool repo!


[PF-456] StairwayComponent and its dependencies

Move the StairwayComponent from buffer into the common lib.
Corresponding PR in buffer: https://github.com/DataBiosphere/terra-resource-buffer/pull/128

regarding this commment on customizing the stairway construction, that makes sense, but it means Stairway can't be a bean. I guess that's not a huge loss, but it is a sore thumb.


Use debian 12 (bookworm) distroless image as base image

How to categorize this PR?

/kind enhancement
What this PR does / why we need it:
Similar to https://github.com/gardener/gardener/pull/8628
Which issue(s) this PR fixes:
N/A
Special notes for your reviewer:
N/A
Release note:

registyr-cache's base image is updated to `gcr.io/distroless/static-debian12:nonroot`.

/approve


Use C++14 instead of 17 for CesiumRuntime and CesiumEditor.

Requires CesiumGS/cesium-native#280
Currently this PR uses C++14 for all platforms. I may change back to C++17 for Windows, macOS, and Linux and only use C++14 for Android (and eventually iOS), but that's still TBD.

Thanks for the pull request @kring!

:heavy_check_mark: Signed CLA found.

Reviewers, don't forget to make sure that:

[ ] Cesium for Unreal Samples works.

We no longer need this because Epic accepted #544.


[BUG] partitioned writes require single batches and sorting, causing gpu OOM in some cases

We have seen cases where GpuInsertIntoHadoopFsRelationCommand runs OOM while trying to sort data for partitioned writes. The symptom is a task that is reading close to full GPU memory, and ends up having to spill the device store. It runs out of memory with most of the GPU in use.
Possible culprits:
This command wants a single batch and the writer framework says it needs this while out-of-core sort isn't implemented (it now is), so we should be able to stop requiring single batch (?).
It is not clear to me whether the sort is absolutely necessary either. @jlowe pointed out it is likely to not hold open all the parquet writers as we read in batches, but that the sort is the likely issue here. We would need to confirm whether it is needed, or find other ways to handle partitions that are larger than GPU memory of a single executor.

When discussing another issue I had the idea that maybe we should skip doing the sort all together. We are sorting because that is what Spark did to be able to group the input data by a specific key. Then they can walk through the data a row a at a time and if the key they care about changes, then they can close the current file, open a new file to write to for this key.
We can assume that the cardinality of these keys should be small so we can probably split each batch as it comes in on each key individuality.  We need to take care to try and keep the relative order of the rows the same within that key. Each of those splits can be tracked in a map and made to be spillable so that when we are ready to write out the data we can walk through the map and write out the data to each file. In the common case (the ideal one) there would be a single key per task so it really would just be doing a contig split on the data and then writing each batch out to after we verified it.
We might even be able to have an optimization that if the amount of data is over some threshold that after doing the split we start to write out the largest split in the first batch so we don't need to worry about spilling it, and we can write out at least a portion of the data each time.

The cause is that the input of the out-of-core  sort is a single large batch.
The single large batch caused the OOM.
out-of-core sort should not require a single batch, it can pull all the input batches and then sort.
Before the out-of-core sort feature was added in,  we do need the single batch for in-memory sorting.
Seems we should update the logic after the out-of-core feature.
Please see 2 related PRs for details

Robert Evans 3/24/20, 10:40 PM Support for partitioned writes

  // We need a single batch if we have to sort the data
  override def requireSingleBatch: Boolean = isPartitioned || isBucketed

  // Need single batch in some cases, at least until out of core sort is done
  override def childrenCoalesceGoal: Seq[CoalesceGoal] =

Robert (Bobby) Evans* 2/22/21, 10:28 PM Add in out of core sort (#1719)

@revans2, help to check

@res-life Yes we could do it the way you are suggesting. When I did the out of core work on the other two PRs I started to add this one in too, but it ended up being more complicated than a quick change, so I left it for later. It is likely to be simpler to try and tie the out of core sort into this, but I personally think that https://github.com/NVIDIA/spark-rapids/issues/5448#issuecomment-1124287404 is going to be a better solution. Especially if we are likely to only see one key, we can potentially avoid a lot of memory issues.

I got some suggestions from Spark DynamicPartitionDataConcurrentWriter
/**
 * Dynamic partition writer with concurrent writers, meaning multiple concurrent writers are opened
 * for writing.
 *
 * The process has the following steps:
 *  - Step 1: Maintain a map of output writers per each partition and/or bucket columns. Keep all
 *            writers opened and write rows one by one.
 *  - Step 2: If number of concurrent writers exceeds limit, sort rest of rows on partition and/or
 *            bucket column(s). Write rows one by one, and eagerly close the writer when finishing
 *            each partition and/or bucket.
 *
 * Caller is expected to call `writeWithIterator()` instead of `write()` to write records.
 */
class DynamicPartitionDataConcurrentWriter(

A solution, @revans2 please help review:

Disable require-single-batch, and this will solve the OOM problem.
Then we can add an optimization. Sort each batch and write the multiple splits one by one while keeping the writers open; if opened writers exceed a threshold, out-of-core sort the rest batches, and write partitions one by one.
Only need to keep a partition-value to partition-writer map.

Other details

Set the proposed DynamicPartitionDataConcurrentWriter like writer as default?
Spark does not set it as default.

        // maxConcurrentOutputFileWriters default value is 0.
        val maxWriters = sparkSession.sessionState.conf.maxConcurrentOutputFileWriters
        val concurrentWritersEnabled = maxWriters > 0 && sortColumns.isEmpty

Sort each batch and write the multiple splits one by one while keeping the writers open

One significant issue with this approach is that if the cardinality of keys within a batch is high, the number of rows written to a row group will be vanishingly small, increasing the size of the resulting output file and reducing the efficiency of subsequent reads from the file.  Unlike the CPU writers which buffer the inputs as they are written, the GPU writers can only write entire row groups/stripes for each write call, so we would need to do the buffering on our end to prevent this undesired behavior.  Caching insufficiently large batches for keys while waiting for new batches will have its own ramifications, of course.

Set the proposed DynamicPartitionDataConcurrentWriter like writer as default?

I don't think this is a good idea.  As mentioned above, each writer held open will add significant memory pressure on the executor since it needs to cache a significant amount of data to achieve efficient encodings in the output file.  We either need to honor the configuration setup in Spark and act accordingly, or provide separate configs to handle this.  The user needs the ability to control how this behaves to control both the amount of memory pressure in the executor and the client load on the distributed filesystem.

Okay I chatted with @jlowe about this and I don't think there is a single solution that is always a clear winner.
So I would propose that we complete this issue by just doing the out of core sort. Get that working, solve the OOM issue and then we can file some follow on issue to explore support for something like DynamicPartitionDataConcurrentWriter.  But the complexity of doing that solution is quite large and unless we have some baseline to compare it to, we will not know if it is faster or not, and in which cases to be able to help us figure out the ideal heuristics/algorithms to do this.


add examples for function category nodes

[ ] Bugfix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)

Proposed changes

This PR add examples for function category core nodes.
Checklist

[x] I have read the contribution guidelines
[x] For non-bugfix PRs, I have discussed this change on the forum/slack team.
[x] I have run grunt to verify the unit tests pass
[ ] I have added suitable unit tests to cover the new/changed functionality

Coverage remained the same at 77.272% when pulling b67f2d874b99387394114226e3972a80616cf3f0 on node-red-hitachi:function-category-examples into cbf1afc9fe6af9c93e0f629ddcfdb9823a94f9b7 on node-red:dev.

There are 48 separate examples in this PR. Each needs to be reviewed separately. That is going to take some time.
We now have multiple PRs adding examples.
How many more PRs for examples are you working on?

This is the last PR I'm currently working on.

Thank you for comments.

Delay node
06 regular rate - not sure a simple inject shows how/why this work ? why inject an array ? Is that relevant ?

As described in comment node, this example is simply imported from cookbook example.  As you pointed out, the example seems not to make sense.  So, removed 06 regular rate example, but it seems to me that the cookbook example need to be updated.

Exec node - uses ls command - which isn't cross platform... maybe try echo ? (without the path)
Not sure we need all 4 examples - why not just pass in a parameter anyway.

Comment node description explain that 'This example only works on UNIX flavored system.'.
But, as you suggested, echo works on both Windows and UNIX-based systems.
So, changed /bin/ls to echo  and merged two examples.

04 - spawn example - is that cross platform ? may as well remove it I think.

It may be a little hard to recognize at first, comment node description explain that 'This example only works on UNIX flavored system.'.

Function node
10 - async setup example - not sure what it's showing me. the node always outputs hello world which doesn't show I have done any async work ? - Also the function uses global.set("message", ... Do we want to pollute the users global context space like that ?

This example uses setTimeout to do asynchronous processing.
It would have been better to use more practical example such as I/O, but it needs changing settings.js to use external modules.

Range - file spelling limit
03 - Scale and limit - I don't think the scaling helps to show what is going on... better example maybe to just limit it.

Changed  the name to limit input

Switch
07 - recreate sequence - not sure what the name means or why I would select it. ?(maybe just remove ?)

The name comes from the settings panel, so it looks like it needs to be synchronized with that one and fixed.

08 - imports as a separate flow instead of into existing

Fixed.

09 - I know we are routing messages - but maybe want to include the word Gate as lots of people want to know how to Gate one message based on another . Ie turn on off a flow.

This example also comes from cookbook example.
This, too, should need to be fixed in sync with the cookbook.

Template
01 - maybe a bit trivial - the content is what is already in the node - maybe combine with example 4 instead. (and make it example 1)

Merged example 1and example 4.

I have merged all of the examples PRs. But please take not of the further commit I added that renamed a lot of them to make sure they were consistent. 07585f01e374ecedc8cdbbf4a2e31a49be37d0a7


Use UTF-8 encoding for multi-messages

The code for single messaging did encode the data with UTF-8 while the
multi-messaging did use the platform encoding. This causes problems on
non UTF-8 systems like Google AppEngine.
Now UTF-8 encoding is also used for multi messages.
Closes-Bug: 16, 17, 22, 28

I signed it!

LGTM


How to add images and custom tag content?

Please see this feed: http://www.espnscrum.com/rss/rugby/rss/headlines_fantasy.rss how do we add the images and custom tags? I just get undefined when I try to load them.

$("#rss-top").rss("http://www.espnscrum.com/rss/rugby/rss/headlines_fantasy.rss", {
	    limit: 3,
	    tokens: {
	      articlelink: function(entry, tokens) { return entry.link },
	      articleimage: function(entry, tokens) {
	      	if(typeof entry.image == 'undefined' || entry.image == '') {
	      		return 'scrum_placeholder.jpg';
	      	}
	      	return entry.image
	      },
	      mainheadline: function(entry, tokens) { return entry.headline },
	      articlesubhead: function(entry, tokens) { return entry.linkname }
	    },
	    layoutTemplate: '
{entries}
',
	    entryTemplate:  '
' +
                            '' +
                                '' +
                                '
{body}
' +
                            '' +
                            '
{articlesubhead}
' +
                        '
'
	});

Hello,
Im using this plugin in my website, and also having the same problem of displaying images in the feed... So I tried out what Hughes did but still no image is being displaed, do u have any idea why is it beahing so??

@AbdallahMyuto did you check that the feed is valid? Which feed URL is that?

yes i checked it's valid

Again: Which feed URL is that?


rework extrafuncMap functions for better naming

And make sure "safehtml" & "safecss" work as intended or are obsolete (autodetection).

Or don't have them at all & leave the whole html & css checking for writing html & css files.


Fix helpers in attrs & some refactors

Previously we tried to "unwrap" MustacheStatements in attributes values like <div foo={{bar}}> to a PathExpression. This has the unexpected consequence of not allow you to invoke bar if it was a helper that took no arguments.
Related ember issue: https://github.com/emberjs/ember.js/issues/12506

Thanks for cleaning this up @mmun!


Multiple Windows Webview2 component crash

Which version of the app?
WinUI 3 Gallery
Description
Closing a new window when a webview2 component is loaded causes the application to crash.
If you go to Windows -> Create Multiple windows, then on the second window that opens, navigate to the WebView2 component,  then attempt to close this window, this will cause a crash.
Screenshots
No response
Windows version
November 2021 Update/21H2 (19044)
Additional context
No response

This is a separate issue, the one in #964 relates to the window not closing.
This issue is the app crashes when attempting to close a WebView2 window.

Fixed in Windows App SDK 1.1.2, see release notes for more info.

I think @officesolutions-it is right, this is a different issue. Re-opening. This was not fixed in 1.1.2.

Looks like duplicate of https://github.com/microsoft/microsoft-ui-xaml/issues/6872.
@officesolutions-it  - can you try the workaround listed in that issue?

Closing - duplicate of https://github.com/microsoft/microsoft-ui-xaml/issues/6872 , fixed in Windows App SDK 1.3.1 (1.3.230502000).


Improvements

Hello!
I am using your file manager in order to browse through files and download them from my server.
I would like to suggest just a couple of improvements:

Display disk usage
Display recursive size for directories (include the size of the files in that directory recursively) instead of always displaying 4KB

Would you prefer that I write a pull request, or would a fork be better?
Thanks
Dany

FYI, I forked your repo and implemented above improvements.
See https://github.com/danolife/node-file-manager

Sorry to replay so late. I haven't check email recently.
Look forward to your PR. But it may be expensive to calculate recursive
size.
Best,
efei
Dany Badr<EMAIL_ADDRESS>于2018年7月12日周四 下午8:45写道：

Hello!
I am using your file manager in order to browse through files and download
them from my server.
I would like to suggest just a couple of improvements:

Display disk usage
Display recursive size for directories (include the size of the
files in that directory recursively) instead of always displaying 4KB

Would you prefer that I write a pull request, or would a fork be better?
Thanks
Dany
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/efeiefei/node-file-manager/issues/28, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AIQJp-GVEbSQHDuDU-6FicmtBkCYhIHSks5uF0TSgaJpZM4VMx70
.


Shift + F2 should select text

Prerequisites

[X] Put an X between the brackets on this line if you have done all of the following:

Reproduced the problem in Safe Mode: http://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
Followed all applicable steps in the debugging guide: http://flight-manual.atom.io/hacking-atom/sections/debugging/
Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description
Holding Shift while jumping to a bookmark doesn't select the text.
Steps to Reproduce

Open any file with text/code inside
Go to any line and create a bookmark
Now go a few lines below the bookmark
Press and hold Shift and hit F2

Expected behavior: All the lines between where the cursor was the momento I pressed F2 and where the bookmark is should be selected.
Actual behavior: The cursor moved to the bookmark but the text wasn't selected.
Reproduces how often: 100%
Versions
Any version.

Thanks @alexandernst 👍  Since https://github.com/atom/bookmarks/pull/91 was added, it looks like this works in the case where there's a bookmark below where your cursor is:
'atom-text-editor':
  'shift-f2': 'bookmarks:select-to-next-bookmark'

But not the case you described above where the next bookmark wraps past the end of the file.  I think we should maybe move this to https://github.com/atom/bookmarks?  I can do that later tonight if you don't get to it.

@rsese did you open a new issue in the right repo?

Sorry, doing that now @alexandernst thanks for the reminder :+1:

@rsese next time please don't close tasks before moving it.

Good idea, that will help things not fall through the cracks if neither person moves an issue :+1:


Emmet for jsx in js-file doesn't work anymore

VSCode Version: 1.71
OS Version: Windows 10

Steps to Reproduce:

Open a .js file with language mode JavaScript React
type div and hit tab

I found tsx works well, but jsx doesn't work.

Just a tip for those who will work on this issue: it is not related to Emmet.
VS Code defines the JavaScript React as JavaScript.

To investigate: this most likely has the same root cause as #14661

Same root cause as #14661

To the verifier: Please see comment in #14661

You can try this
"emmet.includeLanguages": {
    "javascript": "javascriptreact"
}


qbittorrent: extending path to include Python for default functionality

Motivation for this change
Since people regularly open reports about tracker search not working because
python is not found. The most recent of reports/discussions being https://github.com/NixOS/nixpkgs/issues/104221.
And since Tracker Search in qBittorrent can not be disabled & at the same time
the Python is needed for it to work - including Python for default
functionality to work.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[x] other Linux distributions

[x] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
(no dependent packages)
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Determined the impact on package closure size (by running nix path-info -S before and after)

462,853,024
516,526,608
(delta) 53,673,584 aka 53 MB

[x] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

@GrahamcOfBorg build qbittorrent

is it not compatible with python3?

Oh, yes, the naming.

Done.

Rebased to master.
Removed the last commit of split outputs.


[Feature request] Stop using dart:mirrors to deduce Command metadata

Is your feature request related to a problem? Please describe.
Currently, code using nyxx_commands cannot be compiled as dart:mirrors is used to determine metadata about commands, including argument types, annotations but also to assemble converters.
Describe the solution you'd like
Stop using dart:mirrors and migrate to a compile-friendly solution.
Possible options include:

package:build
Macros, see dart-lang/language#1482

Some existing code will have to be converter to type variables instead of Type variables (the language feature vs the type) to perform superclass checking without mirrors. Most notably, assembled converter creation and storage of command argument types will have to be converted to type variables.
A TypeHolder<T> class could be added to store command arguments instead of Type variables, and a type argument on the converterFor method on CommandsPlugin can be added to specify the target type instead of the existing function parameter.
Other code, such as the extraction of @Description, @Name, @Choices or @UseConverter annotations would have to be done at compile-time, using the aforementioned build package or macros. A new parameter would probably be added to the Command constructor to allow passing this data as const variables instead of by converters.
The extraction of command callback parameter types could be done either at compile time or at runtime, although runtime would allow for more flexibility. There is a potential issue with the fact that the number of parameters could theoretically be any arbitrary size, but this can be resolved by adding a maximum number of command arguments - probably 25 to comply with existing Discord limitations.
All of these changes can theoretically be made non-breaking, giving users time to migrate their code until the next major version of nyxx_commands would be released, which would remove all deprecated functions.

Fixing this issue would probably also allow Flutter and JS runtimes to be used with nyxx_commands.

Fixing this issue would probably also allow Flutter and JS runtimes to be used with nyxx_commands.

JS runtime wont happen anyway because we have strong dependency on dart:io in nyxx and nyxx_interactions and it wont change anytime soon. But flutter could work for sure

It would probably be beneficial to keep mirrors support but have it locked behind a conditional import for two reasons:

mirrors is quicker to use and offers a faster development cycle;
mirrors allows you to extract metadata from dart objects no matter where they are declared in the code, which is not possible with macros or build packages:

Future<void> run(Context context, @Name('test') String input) {
  // Some code...
}

commands.registerChild(Command(
  'test',
  'A test command',
  run,
));

In this case, mirrors would be able to extract the metadata on the input parameter whereas macros or build would struggle. In fact, in certain cases it would be impossible to extract the metadata.
To discuss: should the mirrors-based implementation perform the same as compileable options, or should it work universally at the cost of being inconsistent with compiled versions?

Due to the limitations of the current Dart runtime type system, the feature set available in compiled nyxx_commands would be significantly reduced and probably not worth the performance boost. This issue will be closed, but might be reopened in the future if Dart adds better support for runtime types.


Client does not support authentication protocol

Description
DBeaver can't connect to MariaDB
Via MariaDB driver:
Client does not support authentication protocol requested by server. plugin type was = ''
Via MySQL driver:
!AuthenticationProvider.BadAuthenticationPlugin!
When using the server terminal everything is ok
~:$ mysql testdb -p
Enter password:
Welcome to the MariaDB monitor....

When using phpMyAdmin, everything is ok as well.
MariaDB driver version
3.5.0
MySQL driver version
8.2.0
MariaDB version on server
10.3.39-MariaDB-0+deb10u1-log
SHOW GRANTS;
GRANT USAGE ON *.* TO user@localhost IDENTIFIED BY PASSWORD '*12345'
DBeaver Version
24.2.3
Operating System
Windows 10
Database and driver
No response
Steps to reproduce
No response
Additional context
No response

@holden321 Thank you for your report. Could you please provide the following additional information, such as connection parameters and logs? You can find instructions here: https://dbeaver.com/docs/wiki/Log-files/. Thank you.

It's been a while since no update here. If the issue is still actual please let me know and answer the question.


Add Request: Lake Mead Body Count

https://www.lakemeadbodycount.com/

Resource Type
Requests
Transfer Size

Total
2
2.7 KiB

Document
1
2.1 KiB

Stylesheet
1
0.6 KiB

Thanks for consideration!

I am afraid, this link does not seem to satisfy rule 5.


Search complication with since_id and max_id

I just noticed a problem occuring since the change of the API.search() endpoint to v1.1.
I use tweepy.Cursor with the since_id parameter to retrieve multiple pages of search results.
The corresponding request(s) looks like this:
GET /1.1/search/tweets.json?lang=de&q=SEARCH_TERM&since_id=344796632681967616
So far so good, but the last request fails:
GET /1.1/search/tweets.json?lang=de&q=SEARCH_TERM&max_id=344796632681967615&since_id=344796632681967616
.. resulting in:
tweepy.error.TweepError: [{'message': 'Missing or invalid url parameter', 'code': 195}]
I noticed that the failing request contains both since_id and max_id. Their values seem to be mutually exclusive:

since_id: Returns results with an ID greater than (that is, more recent than) the specified ID.
max_id: Returns results with an ID less than (that is, older than) or equal to the specified ID.
Source: https://dev.twitter.com/docs/api/1.1/get/search/tweets

So I think Twitter is right, this seems to be a tweepy bug.
I think this might be linked to drevicko's comment https://github.com/tweepy/tweepy/pull/296#commitcomment-3404913.
Thanks.

i can't get these two term 'max_id' and 'since_id' .


Optimise loading of Footnote in comparison tables

When we add references to a table, the ReferenceComponent loads its Footnotes. Internally its cached, but as we create a new instance of each ReferenceComponent in a table, we end up loading the footnotes multiple times. This leads to lots of additional model instances being created.
This is a draft change that changes the reference to allow the footnote to be passed in, rather than loaded on demand.
This speeds up the report views and reduces memory overhead.
A further optimisation would be to only add the ReferenceComponent if the if check is true, rather than evaluating within the component. The same ReferenceComponent instance could also be shared across table rows (and potentially across tables), which would further reduce memory overhead.

Made a few changes:

main one being passing a reference to the main component instance down to slots, so they can call methods on it. This means we can cache a list of footnote objects there as they are used rather than passing them in at the top level.
Changing the references slot definition to use a lambda has meant we can collect references for footnotes on the way in rather than having to do it afterwards with the old collect_references method. This is much better!
Also changed it so reference components are only created if the "if" evaluates to true.
The footnote components are now sorted when rendered rather than when created
I also spotted that multiple footnotes weren't separated with newlines, so sorted that out.
Also added some more thorough tests for the footnotes.


feat: AWS SecretsManager Config (allow ForceDeleteWithoutRecovery for PushSeccret)

Problem Statement
Allow ForceDeleteWithoutRecovery and RecoveryWindowInDays in PushSecret deletion for AWS SecretsManager via a new spec.secretsManager field in SecretStore.
Related Issue
Closes https://github.com/external-secrets/external-secrets/issues/2830
Proposed Changes
This PR adds a new spec.secretsManager field in SecretStore that allows for setting ForceDeleteWithoutRecovery and RecoveryWindowInDays (these fields are mutually exclusive).
Checklist

[x] I have read the contribution guidelines
[ ] All commits are signed with git commit --signoff
[ ] My changes have reasonable test coverage
[ ] All tests pass with make test
[ ] I ensured my PR is ready for review with make reviewable

Errr, something might have happend during rebase there?

Hi!
originally we thought of having specific PushSecret configuration under a structure of its own on the SecretStore (see https://github.com/external-secrets/external-secrets/blob/main/design/002-pushsecret.md). At the time we envisioned only encryption configuration, but I guess it would make sense to package it all under pushConfig or something similar.

Hi!
originally we thought of having specific PushSecret configuration under a structure of its own on the SecretStore (see https://github.com/external-secrets/external-secrets/blob/main/design/002-pushsecret.md). At the time we envisioned only encryption configuration, but I guess it would make sense to package it all under pushConfig or something similar (in this case, under spec.provider.AWS)

Yeah, I had to think a bit about what would be the best place to place these settings in.
pushConfig would work as well, but either way you will need a substructure that's specific to AWS SecretsManager, so it would need to be pushConfig.secretsManager. I'm open to moving these settings somewhere else, if needed.

/ok-to-test sha=e7f1c68


esri/widgets/LayerList/ListItem operationalItems is not initializing

Hi All,
Can you please help me out to know why "operationalItems" is not being initialized in below code:
I am using ArcGIS API for JavaScript 4.10.
@aliasOf("viewModel.operationalItems")
@renderable()
operationalItems: Collection= null;
The above line is part of code of CompassLayerList.tsx,please let me know if you want more info on it.
Thanks,
Abhinav Kumar

Unfortunately, more info is needed to provide some help.
Since this falls outside the scope of this repo (see contributing guidelines), I'd suggest reporting this to Esri Support along with more detail, including error info and maybe a test case.


Email NDR not being forwarded

<EMAIL_ADDRESS>email account is not forwarding non-delivery reports to lasair-help as it was intended to. A ticket is open with IS for them to suggest a solution.

Provisionally considering this fixed, but need to keep an eye on it. There is now a power automate flow the only function of which is to forward email without silently dropping the messages that we are actually interested in, which is what happens if you try to use "normal" o365 forwarding.


Problems compiling with the NVHPC suite

The NVHPC suite is a SDK from NVIDIA, that combines all the high performance compilers and libraries and provides it to the computing clusters. Most clusters have this available as a module now.
The host compiler is an adaptation of the PGI compiler and NVHPC additionally includes the nvcc compiler and the necessary CUDA libraries (Cusparse, Cublas etc,)
Currently Ginkgo fails with NVHPC due to two main reasons:

NVHPC does not seem to support user-defined reductions, which we need due to templating and given that we need to define reductions for our own types.
NVHPC seems to have some issues with Rapidjson, with some typedefs in the biginteger.h header, which the host compiler does not seems to recognize.

Fixed issues:
We previously also faced issues with the unified kernel reduction but that was fixed in PR #926.

should be solved when #861 is finished and merged :)

Should be fixed after #1331. Please reopen if that is not the case.


Feature: disable aura when defeated

how auras work differently from active effects (always being active in another entity)
It would be nice to have an option to disable when killed (same as disable when hidden)

Should be possible yes,


Update dependency: schedule/tracking -> schedule/tracing

Fixes #21150
I just updated the dependency's name and module name (from tracking to tracing). If tests don't pass, that means that they didn't pass either before.
As this comment pointed out, the dependency's name has changed.
Updating the dependency's name fixed the bug.

I wanted to make such PR, but I decided to not do it, because currently React Native is locked on React 16.5.0, which doesn't include the renamed tracing API. I honestly don't know whether this PR should include React version bump to 16.5.2 and what's Facebook's policy for such changes. 😕
Besides that, it's great to see the support for the newest React in this PR! 🎉

@yairopro Thanks for the PR! This code actually lives in the react repo and is synced when we update the react version. Right now RN is only compatible with<EMAIL_ADDRESS>so you need to lock the version to that. We'll probably update the RN version soon.
cc @yungsters who did the last sync :)

I believe @bvaughn is already working on the next sync.

Thanks guys.
So because these modules are from in the react and are synced, there's no need for this pull request, then should I close it?

Yes, this PR can be closed. 😄
The tracking -> tracing rename needs to happen (and has already been made) in the react repo anyway, because that's where the ReactNative renderer is built and synced from. So long as you're using the version of "react" that "react-native" pins to, the dependencies should line up correctly.
Using a different version of "react" than the explicitly pinned dependency may cause problems like this, but that was never supported.

I have update my react-native project from 0.57.8 to 0.59.1 it's give me the same error. After that I have update to 0.53.9 and it's give me the same result. I have try all of these works. But non worked for me. Can anyone help me on this.