[vm/ffi] Add DynamicLibrary.functionExists()

Currently, the only way to check whether a function exists in a given DL (or an already loaded library in DynamicLibrary.Process()) is to call .lookup() and catch exceptions. This doesn't work all that well when someone has "catch all exceptions" enabled, e.g. in VS Code.
Consider adding a boolean returning function to check whether a function with a given name exists. I've had a quick look at the SDK code and adding a new function based on the existing ResolveSymbol looks reasonably simple (ffi_dynamic_library.cc):
static bool SymbolExists(void* handle, const char* symbol) {
#if defined(HOST_OS_LINUX) || defined(HOST_OS_MACOS) ||                        \
    defined(HOST_OS_ANDROID) || defined(HOST_OS_FUCHSIA)
  return dlsym(handle, symbol) != nullptr;
#elif defined(HOST_OS_WINDOWS)
  return GetProcAddress(reinterpret_cast<HMODULE>(handle), symbol) != nullptr;
#else
  const Array& args = Array::Handle(Array::New(1));
  args.SetAt(0,
             String::Handle(String::New(
                 "The dart:ffi library is not available on this platform.")));
  Exceptions::ThrowByType(Exceptions::kUnsupported, args);
#endif
}

Originally posted by @vaind in https://github.com/dart-lang/ffi/issues/104#issue-899609369
This is a dart:ffi feature, not package:ffi feature, so I'm moving this issue.

Is anyone working on this? Otherwise, I'm happy to help contribute this feature.

Is anyone working on this?

No.

Otherwise, I'm happy to help contribute this feature.

Yes, please go ahead and make a PR. 😄
I'll review it.


Fix nicProperties: Nat and FirewallActive could not be false

BREAKING CHANGE:
NicProperties.Nat and NicProperties.FirewallActive were bool and
tagged with omitEmpty, which made it impossible to set these to false
via sdk. To actually make use of optional attributes in a struct, the types must
be references.
Also add support for Go 1.11 modules

@scriptnik Could you please have a look and/or merge ;)


Update experimental-module.md

Wrap title to inline code syntax

@pjessesco : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Hi @corob-msft, thanks for the reply.
Is there any plan to apply the change to the other pages programmatically? If not, I'd like to involve it.


fix member photo

Coverage increased (+0.01%) to 82.68% when pulling 5a38c6ace3077f69855b3c80ebdbdf9545525988 on itowtips:member into 38f5d03fcb0311c3af17af9a76a38d73001ab916 on shirasagi:master.


chore(context): safer retrieve

Since retrieve/store doesn't imply index semantics, we should opt for returning Optional types so that the caller isn't required to wrap every invocation with a try/except.

Codecov Report

Merging #83 (936f296) into master (a679130) will not change coverage.
The diff coverage is 50.00%.

@@           Coverage Diff           @@
##           master      #83   +/-   ##
=======================================
  Coverage   68.41%   68.41%
=======================================
  Files          33       33
  Lines        1453     1453
=======================================
  Hits          994      994
  Misses        459      459

Impacted Files
Coverage Δ

ergo/context.py
57.14% <50.00%> (ø)

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 a679130...936f296. Read the comment docs.


How do I add more features to my osiris build?

I'm not sure how to add the draw aimbot fov and the viewmodel xyz to my build can someone explain

Go and check pull request and find one that is at max 2 months old. Then go add the code. Some code will be altered so do try to be careful or you might break it.

ato explain find the pu and pull requests, click on them. Then press code changed. now find the file and the code line number. Repleace the red witht the green and add the green


Make it possible to change LLVM version directly from Nix

Need to use the "replace text" function in Nix to update the LLVM version in Setup.hs.
Maybe also provide a helper function in Nix to build for a specific LLVM version.

Nix now doesn't rely on Setup.hs. Version can be directly modified in the flake.nix thanks to #5.


sos_triangle core dumps for solid surface generation of big system

I am getting an error while generating solid surface which says- ERROR:Maximum number of co-ordinates exceeded!
Program TERMINATED
I am sharing a screenshot for reference.

Please help me regarding this.
Thank you

You can try increasing MAX_COORD in https://github.com/osmart/hole2/blob/7259d8f488e360d90377d3397a56e57c262793d7/src/sos_triangle.c#L28-L33 and recompile yourself.

Thank you for your response Sir. I'll try to increase the coordinates count

Please let us know if the proposed change addresses your problem!

Sir, now I think program is able to read the coordinates as I have increased the MAX_COORD  but I still facing issue while generating "solid_surface.vmd_plot" file.
I am sharing the screenshot for your reference

Sir, I am still in need of your assistance as I am lacking in programming skills to figure out this error related to "segmentation-fault (core-dumped)" on my own

Thank you Sir. I'll try what I can do on my part and update if I am able to resolve the issue

Sir, I am extremely sorry to bother you again but I want to bring in light another issue I face while using "qpt_conv" command. Despite hitting enter three times. Nothing seems to happen

I would open a new issue because you're having issues with qpt_conv.
I have no idea what could be the problem but at least if you create an issue specific for the problem then there's a chance that someone may see it.
(I wrote a short post about posting issues and questions at https://github.com/MDAnalysis/mdanalysis/discussions/4558 which may be helpful.)

I am going to leave this issue open for now.


build: replace unnecessary use of CMake 3.6 feature

Description
https://github.com/intel/mkl-dnn/pull/658 introduced a regex list filter to src/cpu/CMakeLists.txt
This feature is only available for Cmake 3.6 onwards which will cause the build to fail if DNNL_ENABLE_JIT_PROFILING is not set (e.g. for an AArch64 build) an the host machine has CMake 3.5 or older.
This patch replaces with filter(REMOVE_ITEM ... for compatibility with older versions of Cmake.
Note: this should not be encountered by the standard commit tests. Builds on AArch64 will encounter this line, but with no AArch64 CI this will not get tested. I hope to address this with a PR or RFC in the very near future.
Fixes # no issue raised.
Checklist
All Submissions

[x] Do all unit and benchdnn tests (make test and make test_benchdnn_*)
pass locally?
_yes, but given it's a CMake change outside the scope of the current CI, it's not entirely relevant.)
[ ] Have you formatted the code using clang-format?
no changes made to sources.

New features

[ ] Have you added relevant tests?
not applicable
[ ] Have you provided motivation for adding a new feature?
not applicable

Bug fixes

[ ] Have you added relevant regression tests?
not applicable
[ x ] Have you included information on how to reproduce the issue (either in a
github issue or in this PR)?

Hi @nSircombe,
Thanks for the patch! LGTM!
I would also like to disable VTune integration if DNNL_ENABLE_JIT_PROFILING is OFF. Do you have objections of the minor addition (https://github.com/intel/mkl-dnn/pull/675/commits/5991317cdc5c5112ae6b7668a1d7e44bfdbc985d) to your patch?

Hi @emfomenk - I don't have any objections to that.

I have a related problem, which I was about to raise as an issue, but maybe could be addressed here...
/src/CMakeLists.txt adds -ldl to EXTRA_SHARED_LIBS, since "Not every compiler adds -ldl automatically".
This is usually the case if if(UNIX AND NOT APPLE) however, the use of elseif() with if(NOT DNNL_ENABLE_JIT_PROFILING) means, as far as I can tell, -ldl does not get added if DNNL_ENABLE_JIT_PROFILING is disabled (e.g. during an AArch64 build).
Is this intentional? It looks like a simple change is needed:
diff --git a/src/CMakeLists.txt b/src/CMakeLists.txt
index 4d80a2974..301c44c14 100644
--- a/src/CMakeLists.txt
+++ b/src/CMakeLists.txt
@@ -58,7 +58,8 @@ if(NOT DNNL_ENABLE_JIT_PROFILING)
     # library
     message(STATUS "Intel(R) VTune(TM) Amplifier JIT profiling disabled")
     add_definitions(-DDNNL_ENABLE_JIT_PROFILING=0)
-elseif(UNIX AND NOT APPLE)
+endif()
+if(UNIX AND NOT APPLE)
     # Not every compiler adds -ldl automatically
     list(APPEND EXTRA_SHARED_LIBS "${CMAKE_DL_LIBS}")
 endif()

This is usually the case if if(UNIX AND NOT APPLE) however, the use of elseif() with if(NOT DNNL_ENABLE_JIT_PROFILING) means, as far as I can tell, -ldl does not get added if DNNL_ENABLE_JIT_PROFILING is disabled (e.g. during an AArch64 build).
Is this intentional?

The thing is that library uses dlopen() only if it incorporates VTune jitprofiling.a. That's why we don't require dl if DNNL_ENABLE_JIT_PROFILING is OFF. What kind of problem do you observe? I would expect that dnnl doesn't need dl explicitly...

@nSircombe, let me merge the PR as is.
Let's move the discussion about libdl in new issue or a separate PR if you think dnnl should be linked against it regardless of using the jitprofiling.a.

Merged. Thanks for the contribution!

Great, cheers.
I’ll get a bit more detail on the libdl issue and start a new PR.

@emfomenk - I was getting:
../../../src/libdnnl.so.1.3: undefined reference to `dlopen'
../../../src/libdnnl.so.1.3: undefined reference to `dlclose'
../../../src/libdnnl.so.1.3: undefined reference to `dlsym'

at link time.

that library uses dlopen() only if it incorporates VTune jitprofiling.a.

This makes sense now, it was a side effect of building jitprofiling, so your addition to this PR has fixed the issue for me!

Oh, indeed, I didn't match this coincidence.
Well glad to hear it now works fine :)

I had the same issue using a regex to filter out jit* files. Since the number of files was large (and changes regularly) I decided to add to utils.cmake:
# list_filter_exclude(<list> <regexp>)
# behave like list(FILTER <list> EXCLUDE REGEX <regexp>)
macro(list_filter_exclude _list _regexp)
    set(_kept)
    foreach(_item ${${_list}})
        string(REGEX MATCH "${_regexp}" _ok "${_item}")
        if(NOT _ok)
            list(APPEND _kept "${_item}")
        endif()
    endforeach()
    set(${_list} "${_kept}")
endmacro()

Yes, I saw that. Neat.
...it's possibly worth bumping the min CMake version to >3.6 to be honest. I'm not sure what the repercussions would be though.


added landing screens

I have added landing pages to your app. The landing pages include pictures, nice background images, descriptions and login/sign up button. The pages contain animations too. I have a recorded a video too. https://drive.google.com/file/d/11KddcX2e-MwbUZ6L-WK2b_DvCDdpmxRc/view?usp=sharing
The animations are more smooth than as seem in video.

This looks great! Thanks for contributing :)


Make android less sensitive

I don't think it's too sensitive on iOS, so what you can do is add a prop sensitive or maxSensity or whatever, use it when you put your magic number 4, and in defaultProp, set value to 4 only for Android device for the moment, and later I'm gonna try on both, to see if we apply this default parameter on Android and iOS :)
Thanks for your PR!

Ok, so I just add a props sensitivity by default the value is 0, but you can pass everything you want.


Smart Editor: The Save button in the attribute inspector is enabled when selecting an existing feature.

Widget
Smart Editor
Version of widget
1.0 Alpha
Bug or Enhancement
Bug
Repo Steps or Enhancement details
Open Smart Editor.
Select an existing feature.
The save button is enabled.
Not sure if this is a new change in the workflow. There was an issue requesting that the Save button should be disabled until user make a change.

good catch, resolution checked in

Verified.


Cannot hear others when I minimize the webview on iOS

I forked this repo and hosted my local server.
Then I noticed that I couldn't hear others voice and other can hear my voice when I minimize the webview on iOS.
It's okay on the desktop but only on mobile.
When I was using the former version(v1.x) for livekit, it was okay.

Safari browser is recommended. Please check readme file.


feat: add favicons

Resolves #99
Impact: minor
Type: feature
Feature
Adds favorites icons
Testing

Verify favorite icon links are rendered in the HTML markup

@mikemurray updated


update example page to correct URLs

A few comments. LGTM otherwise.

Need to use the CDN URL - otherwise this will break when copied to the docs site.

This is obsolete now with our videojs 6.x work for the new docs website.


As a User I want to be able to use the app with my own realtime location data

[x] Persistence: actually store locations
[x] long/midterm background runtime testing on android

initial tests on nexus 5 indiciate that location updates stop after a while.

Further testing on the Nexus 5 shows that once battery-optimizations are disabled for the app, the background task is working most of the time.
So it's not entirely stable, but in a usable state. This statement is backed with N=1 ;)

When you open the app on iOS and then select the Nepal example before any other trajectory, zooming to the trajectory seems to be broken.

implemented in #14


[Docker installation / SQL issue] Base table or view not found: 1146 Table 'cocorico.user' doesn't exist

| Bug report?      | [ ]
I'm using  Docker installation msg error on main page :
An exception occurred while executing 'SELECT DISTINCT id_1 FROM (SELECT '' AS sclr_0, l0_.id AS id_1, l0_.price AS price_2, l0_.certified AS certified_3, l0_.average_rating AS average_rating_4, l0_.createdAt AS createdAt_5, l1_.title AS title_6, l1_.description AS description_7, l1_.slug AS slug_8, l1_.locale AS locale_9, l1_.id AS id_10, l2_.id AS id_11, l3_.id AS id_12, l3_.lft AS lft_13, l3_.lvl AS lvl_14, l3_.rgt AS rgt_15, l3_...

Hello Matino,
It sounds like the installation was not finished when you accessed localhost. Could you wait to see

[OK] Server running on http://<IP_ADDRESS>:8000

in the progress of the installation http://localhost:9001/logtail/cocorico before accessing localhost.
PS: For your eventual next issue on cocorico-docker please add it to the https://github.com/Cocolabs-SAS/cocorico-docker repository.
Thanks,

Hello Matino,
A new issue has been created https://github.com/Cocolabs-SAS/cocorico-docker/issues/4 relating to yours.


Initial commit of Temperature Measurement Cluster (Issue #211)

Tested on Google Home with live temperature data.

@JimBuzbee If you are ready for recheck just click on the "circle arrows" beside my name above in the reviewer list

I think I did it, and accepted, but it's red for me?

Yes it still has the old result shown there. if you klick the "circle button" then it disapears and I get an email ... but I check now


Streamline generation by removing multiple candidates.

As suggested, this eliminates multi-candidate generation from consumer-facing APIs. The plugin APIs have been made backward compatible to avoid disrupting model providers. I also made telemetry backwards-compatible because I don't really know the implications of changing the data there.
Checklist (if applicable):

[x] Tested (manually, unit tested, etc.)
[x] Docs updated

FYI - we'll adjust the dev UI code to follow this change once it merges (tracking in https://github.com/firebase/genkit/issues/960).


update name and query logic for memory temperature metric

This PR updates a metric name:
rocm_temperature_hbm_celsius -> rocm_temperature_memory_celsius
and enables support for a vram sensor location.
Examples samples with the update:
rocm_temperature_hbm_celsius{card="1",location="hbm_0"} 47.0
rocm_temperature_celsius{card="7",location="junction"} 39.0

@jordap Can you update dashboards to use updated metric name?

@jordap Can you update dashboards to use updated metric name and add to this branch?

Dashboards have been updated.


Create man pages for the Debian package

With our Debian package, we can provide man pages for commands.
Creating this issue to discuss this.

My plan was to go for az.1 and az-$(subcommand).1 man pages.
I intend to split the official Debian package to build independent binary packages for each of the command modules, as I'm replacing the component subsystem to work using dpkg instead of apt for the official Debian package (as per Debian policy). This means it would be convenient for me if the man pages are split across command modules.

No movement on this in two years. Closing.


Implemented Heap Sort Algorithm

Description:
This pull request introduces an implementation of the Heap Sort algorithm.
Definition:

Heap Sort is an efficient comparison-based sorting algorithm that utilises a binary heap data structure to sort arrays.
This algorithm builds a heap from the input array, repeatedly extracts the maximum element from the heap, and rebuilds the heap until the array is sorted.
This algorithm is known for its O(n log n) time complexity.

Implementation Details:
heap_sort.f90: Contains the heap_sort_module with:

heap_sort: A subroutine that sorts the input array using the heap sort algorithm.
heapify: A subroutine that maintains the heap property for a given subtree.
swap: A helper subroutine that swaps two elements in the array.

The implementation follows the module structure as outlined in the contribution guidelines.
Example Usage:
example_usage_heap_sort.f90: A test program that demonstrates the heap_sort subroutine from the heap_sort_module. It sorts a sample array and prints the results.
Additional Test Cases:
tests_heap_sort.f90: A test program that includes a variety of test cases to validate the heap_sort implementation.

The code is fine, but it would be better if you could add more test cases! 👍

Thanks, @SatinWukerORIG
Sure, I will work on adding more test cases 🙂

I like the cases that you made 👍
Do you think writing the algorithm and test cases inside one file is better? Or is it easier to write in separate files? In other repositories of TheAlgorithms (like Python and Java), we put everything under one file. Fortran is an old and redundant language, do you think which way is more readable?

Thanks 🙂
In a language with verbose syntax like Fortran, combining both algorithm logic and test logic in one file can result in longer files that are harder to navigate. Separating them encourages modularity and clarity, especially when dealing with many test cases or complex algorithms.
We can probably use subdirectores to group the relevant files: algorithm, example usage, and test cases, by algorithm name.
For instance, we could use a structure like this:
|-- sorts
    -->heap_sort
        --> heap_sort_module.f90
        --> example_usage_heap_sort.f90
        --> tests_heap_sort.f90
    --> quick_sort
        --> quick_sort_module.f90
        --> example_usage_quick_sort.f90
        --> tests_quick_sort.f90
    --> radix_sort
        --> radix_sort_module.f90
        --> example_usage_radix_sort.f90
        --> tests_radix_sort.f90
    ⋮

In the Java repository they seprate the two logics: Java Repository.
In contrast, in the Python repository, combining the two works well because of Python’s concise syntax. Test cases are often embedded directly in the docstrings alongside the algorithm code, as seen in this example from the Python repository.
Let’s not forget that Fortran still holds value in fields like scientific computing, high-performance computing, and numerical analysis. Its performance and optimisation capabilities enable it to endure in computationally intensive domains. 👍


Add null check at every dispatcher's bind method

Fix #62

Implement preconditions to make sure lightcycle binding target is not null
Add test

Thanks. I am going to give you a heads up when releasing.


Is sink() preferred over assign()?

In all the examples in the documentation, the sink() subscriber is used. For example:
let cancellable = publisher.sink(
    receiveCompletion: { completion in ... },
    receiveValue: { (players: [Player]) in
        print("Fresh players: \(players)")
    })

Are there any reasons we should not use assign() with GRDBCombine?

Hello again @simensol,
GRDBCombine publishers are regular Combine publishers, and they can feed any Combine Subscriber. You can dump them into sink, assign, and process them in any possible way.
So one can argue that all the sink examples in the documentation are unnecessary. And even, as your question reveals, confusing.
I'll try to find a better balance in the way documentation is written. Until then, please dump those publishers wherever you want to :-)

Alright, thanks for answering (again)! And thanks for making this fabulous package!

 We're all learning about Combine :-)


Grafana agent is not happy in proxy environment

Description
Grafana agent is not happy behind a proxy and it's not able to send it's events on leopard
ts=2024-11-12T13:30:31.246223133Z level=info msg="failed to send usage report" retries=0 err="Post "https://stats.grafana.org/agent-usage-report\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)"
ts=2024-11-12T13:30:38.212122343Z level=info msg="failed to send usage report" retries=1 err="Post "https://stats.grafana.org/agent-usage-report\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)"
ts=2024-11-12T13:30:46.0336601Z level=info msg="failed to send usage report" retries=2 err="Post "https://stats.grafana.org/agent-usage-report\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)"
ts=2024-11-12T13:30:48.802753301Z level=warn msg="error sending batch, will retry" component=loki.write.default component=client host= status=-1 tenant=leopard error="Post "/loki/api/v1/push": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
TODO

Well fix it
Check if it's an issue in alloy

Same thing happening on goat (obviously) but currently the error logs on both installations are the following :
ts=2024-11-17T19:26:08.476715803Z level=warn msg="error sending batch, will retry" component=loki.write.default component=client host=write.loki.goat.gaws.gigantic.io status=500 tenant=goat error="server returned HTTP status 500 Internal Server Error (500): at least 2 live replicas required, could only find 1"
ts=2024-11-17T19:26:16.795472471Z level=warn msg="error sending batch, will retry" component=loki.write.default component=client host=write.loki.goat.gaws.gigantic.io status=500 tenant=goat error="server returned HTTP status 500 Internal Server Error (500): at least 2 live replicas required, could only find 1"
ts=2024-11-22T04:07:39.428437592Z level=warn msg="error sending batch, will retry" component=loki.write.default component=client host=write.loki.goat.gaws.gigantic.io status=-1 tenant=goat error="Post \"https://write.loki.goat.gaws.gigantic.io/loki/api/v1/push\": net/http: request canceled (Client.Timeout exceeded while awaiting headers)"
ts=2024-11-22T07:07:46.528358431Z level=warn msg="error sending batch, will retry" component=loki.write.default component=client host=write.loki.goat.gaws.gigantic.io status=-1 tenant=goat error="Post \"https://write.loki.goat.gaws.gigantic.io/loki/api/v1/push\": net/http: request canceled (Client.Timeout exceeded while awaiting headers)"

After restarting both grafana-agents on goat and leopard there are no error logs mentioning any timeouts. Moreover, after checking the timestamps of the previous error logs, I noticed that those errors didn't happen that often and were quite spread in time.
Finally, k8s events can been seen in grafana explore on both installations :

Since this PM is 2 weeks old, maybe some changes that could have happened in the meantime made the agents work again. So I would say on my end that we could close this.
@QuentinBisson any comments ?

Can you delete the chart and see if it is not a manual change ?

So I rolled the charts on both installations and I don't see any noticeable change 🤷

Noice


delugePostProcess.py

It appears that the changes to indexing between 2.7 and 3.x is impacting the delugePostProcess.py.
File "./delugePostProcess.py", line 56, in
torrent_files = torrent_data['files']
KeyError: 'files'
It does not appear that the python 3 conversion was completed on the deluge file.

I have resolved this issue in my fork of your repo, Not ready for the pull yet, it appears that under python3 the values coming from deluge are byte encoded, so I had to add the decodes into the values for the processing to work. My tests using both python2.7 and python3 now appear to function for the delugePostProcessing.py.
…
--Justin
On Mon, Jan 28, 2019 at 8:22 AM Michael Higgins @.***> wrote: This is more likely a communication error with deluge returning a dict without the 'files' parameter Did you check your deluge settings? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#979 (comment)>, or mute the thread https://github.com/notifications/unsubscribe-auth/AKau1C2R9sCXonvux1JlyzEBVkbdhTrXks5vHvmigaJpZM4aVDv5 .

Oh that explains when when I moved to P3 last week things stopped, I look forward to what your fork has to offer :)

Added a try/except block for the deluge data that should catch this and decode
good catch


User modified colours - background colour for focused item defaults to white

Tested using Firefox colour settings. When arrowing through the results, for the first five the focused result is indicated in the box but has a white background. Don't know what the user would expect in terms of a background, but as they have changed settings this may not be readable for them. See https://accessibility.blog.gov.uk/2017/03/27/how-users-change-colours-on-websites/ for further information on the sorts of things that need to be considered.

We recently discussed this as a team and we're unsure if this is default behaviour in Firefox. We should investigate first.


Can't camera button

I can't see camera button sometimes.
https://www.dropbox.com/s/3bmdgrzp3s56rxd/Camera button.mp4?dl=0#
and what is the correct BSImagePicker?
Another path: https://github.com/asefnoor/BSImagePicker

Thanks for reporting it! I'll have a look at it when I get the time.
This is the 'correct' BSImagePicker. The others (there are 83 of them) are whats called forks, and sometimes they contribute back to this repo. https://guides.github.com/activities/forking/

@mikaoj
I'm using your library in my project, and my client wants to fix this issue asap.
Can you help me now?
Thank you.

Could you show me your code for creating, setting up and presenting the image picker?
I’m Joakim Gyllström and I approve this message
På 21 mars 2016 till 11:03:46, Ying1986 (notifications<EMAIL_ADDRESS>skrev:
@mikaojhttps://github.com/mikaoj
I'm using your library in my project, and my client wants to fix this issue asap.
Can you help me now?
Thank you.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHubhttps://github.com/mikaoj/BSImagePicker/issues/68#issuecomment-199207991

I have used your code in objective-c:
`    BSImagePickerViewController* vc = [[BSImagePickerViewController alloc] initWithDefaultSelections: nil];
vc.maxNumberOfSelections = 5;

UIImage *cameraImage = [UIImage imageWithIcon:@"fa-camera" backgroundColor:[UIColor clearColor] iconColor:[UIColor darkGrayColor] fontSize: 30];

vc.takePhotoIcon = cameraImage;
vc.takePhotos = true;

vc.selectionFillColor = [UIColor grayColor];
vc.selectionStrokeColor = [UIColor yellowColor];
vc.selectionShadowColor = [UIColor redColor];

[self bs_presentImagePickerController: vc animated:YES select:^(PHAsset * _Nonnull asset) {

} deselect:^(PHAsset * _Nonnull asset) {

} cancel:^(NSArray<PHAsset *> * _Nonnull asset) {

} finish:^(NSArray<PHAsset *> * _Nonnull assets) {
} completion:^{

}];`

Thanks! Could you try it without setting you own custom camera icon?

yes, but I need own icon, because this library use heart icon as camera,
I think camera icon is not the reason of this issue.

I understand that, but I'm trying to pinpoint the problem so that I can fix it later. There more you can help me with that the quicker I can apply my limited time to the right area in the code :)
Could you try removing those lines and see if it helps?
Or at least not use the category function for creating an image with icon, background color, icon color and font size. And use the plain UIImage(named: "chat") instead.
This is not intended as a permanent fix, but only to find out where the problem actually is.

And no, the default is not an heart. If you don't set the camera at all the default will actually be a camera :)
The heart is only in the example to show how you actually set it if you don't like the default.

Any update on this?


Session 5: Add Passport services to docker-compose

@emre-f you're the expert at this. Can you please add all docker services that are necessary for Passports (broker, ui node, ory kratos, ory hydra) to the session 5 docker-compose.yml?

@jb-adams There is an issue with the allocated ports. Both the passport-broker and the data-connect service uses the port 4500. I tried modifying the ports of the passport-broker in the docker compose file but it didn't work.

Would it be easier to change the ports of the data-connect image?
Do you know what else I need to change to make the passport broker work at a different port?

Okay thank you, after discussing with @yash-puligundla, we just modified the port of data-connect. This issue can be labelled complete, now the passport service works.


Decapitalize error string;

https://github.com/golang/go/wiki/Errors

Please sign your commits following these rules:
https://github.com/moby/moby/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "f23608bc" git@github.com:243083df/machine.git somewhere
$ cd somewhere
$ git commit --amend -s --no-edit
$ git push -f

Amending updates the existing PR. You DO NOT need to open a new one.

Thanks, but that's likely to create more problems than it solves.


ci: Upgrading the library for github-script to the latest version

Description

[!TIP]
Add a TL;DR when the description is longer than 500 words or extremely technical (helps the content, marketing, and DevRel team).
Please also include relevant motivation and context. List any dependencies that are required for this change. Add links to Notion, Figma or any other documents that might be relevant to the PR.

Fixes #Issue Number
or
Fixes Issue URL

[!WARNING]
If no issue exists, please create an issue first, and check with the maintainers if the issue is valid.

Automation
/ok-to-test tags=""
:mag: Cypress test results

[!CAUTION]
If you modify the content in this section, you are likely to disrupt the CI result for your PR.

Communication
Should the DevRel and Marketing teams inform users about this change?

[ ] Yes
[ ] No

#33554  👈
release

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

Join @mohanarpit and the rest of your teammates on  Graphite


Update transforms.py

Updated FindReplaceIdSpec to get the first column of the select statement instead of ID

@GeekStewie My apologies, I thought that I had submitted a review for you and it was sitting in Pending state.


[Android] Module AppRegistry is not a registered callable module

Steps:

Clone repo
npm i
run Android Studio under Nexus 5X and 6.0 Marshmallow

Result:
Crash

Additional stacktrace from studio:
02-29 16:58:30.445 3330-4222/com.app E/ReactNativeJS: Module AppRegistry is not a registered callable module.
02-29 16:58:30.459 3330-4223/com.app E/unknown:React: Exception in native call from JS
                                                      com.facebook.react.bridge.NativeArgumentsParseException: RKSourceCode.getScriptText got 0 arguments, expected 2
                                                          at com.facebook.react.bridge.BaseJavaModule$JavaMethod.invoke(BaseJavaModule.java:227)
                                                          at com.facebook.react.bridge.NativeModuleRegistry$ModuleDefinition.call(NativeModuleRegistry.java:158)
                                                          at com.facebook.react.bridge.NativeModuleRegistry.call(NativeModuleRegistry.java:58)
                                                          at com.facebook.react.bridge.CatalystInstanceImpl$NativeModulesReactCallback.call(CatalystInstanceImpl.java:431)
                                                          at com.facebook.react.bridge.queue.NativeRunnableDeprecated.run(Native Method)
                                                          at android.os.Handler.handleCallback(Handler.java:739)
                                                          at android.os.Handler.dispatchMessage(Handler.java:95)
                                                          at com.facebook.react.bridge.queue.MessageQueueThreadHandler.dispatchMessage(MessageQueueThreadHandler.java:31)
                                                          at android.os.Looper.loop(Looper.java:148)
                                                          at com.facebook.react.bridge.queue.MessageQueueThreadImpl$3.run(MessageQueueThreadImpl.java:185)
                                                          at java.lang.Thread.run(Thread.java:818)
02-29 16:58:30.461 3330-4222/com.app I/ReactNativeJS: 'Failed to print error: ', 'undefined is not an object (evaluating \'RCTSourceCode.getScriptText().\nthen\')'

Thanks for the report. I'll look into this when I have a chance. Meanwhile you may also want to try requesting help in the Gitter channel (link from README badge). /cc @niftylettuce for familiarity with Android RN dev

http://stackoverflow.com/questions/34969858/react-native-module-appregistry-is-not-a-registered-callable-module/35630058
Please let us know if you find a solution!
thanks

will do!
i try clean install from React Native official docs, and it works well...

I'll regenerate the RN app from init this weekend. It requires some hacks to chop off some of the tooling they're building for iOS so I'll look for a happy middle ground.

+1

Sorry for the flub all. I'll be sure this gets fixed as soon as I can. Meanwhile, try a "react-native" upgrade after installing and see if you can push through any issues. I will get on this Saturday.

It was my first try (updating react-native after cloning the repo), and it gives the same error. Not tried this: [http://stackoverflow.com/a/35630058]. If I discover anything new I'll report here.

While this is being addressed, please try testing on an actual device and being sure you look through the closed Android issues in this repo. Also, and feedback on the Android instructions in the README is welcome and relevant here.

BTW @vjeux has never heard of this error before :(
https://twitter.com/julienrenaux/status/704556052902191104

@ochervak @shprink to better understand how to debug this I need to try and replicate your environments as closely as possible. If possible, please provide your kit version used and your current node -v && npm -v. Thanks!

Released a new version of the starter kit on the latest RN stable (v0.21.0), which includes a host of Android goodies. Not sure if it's going to resolve this issue, but it's what I'll be using try try and replicate this issue with what information I have.

Same thing after updating the starter kit (already cleaned the node_modules dir). Tried reinstall node (v5.7.1) and all packages again too :disappointed:
On a fresh react-native it works pretty well =/

Hey guys, from my experience, I went straight with the bundler that RN provides.  Webpack is a nightmare to work with when you want to do anything complex.  The package system is not the best in my opinion, and the amount of time you will save using the built-in packager/bundling system is wayyyy less compared to the time you'll spend trying to configure your webpack.config.js files.

@gustavovnicius could you provide your Node, NPM and emulator version. Did you try the port forwarding run script,

Thanks for the knowledge drop @niftylettuce. What kind of environment are you using? My goal is to keep things simple while helping others move forward with a simple extensible toolset.

Sure!
node v5.7.1, npm 3.6.0 running on latest genymotion 2.6.0 / vbox 5.0.16.
After the update, running in an actual device (Android 5.0) it gives a slightly different error

But after reloading JS, it works

@jhabdas I'm using RN v0.20 and just running npm start when I want to run my project.  I really don't need webpack.  With the latest version of RN, you can have custom .babelrc files, which the packager respects.  In older versions, you can just edit the .babelrc file directly in the ./node_modules/react-native folder that the packager.sh script uses.  Here's what my .babelrc file looks like:
{
  "presets": [ "react-native", "stage-0" ],
  "plugins": [
    "transform-decorators-legacy"
  ]
}

My npm start command looks like this in package.json:
"start": "node_modules/react-native/packager/packager.sh",

After reloading JS, it works? Could you expand. While the default packager may seem easier I have my doubts as to its long-term efficacy while building and maintaining apps. As suggested, the goal here is to keep tooling light, and Id rather not see RN turned into a framework.

@jhabdas Yeah, Reload JS works fine for me.  The moment I switched out of all this webpack nonsense my workflow became SO much easier. I was spending 90% of the time before configuring webpack, now I don't have to configure anything, I can focus on the code and RN packages themselves, writing decorators, etc.  My key tip for ANYONE using RN is to use RN packager directly, and .babelrc for any cool Babel plugins you need.

Thanks, @niftylsttuce. As a result, what changes do you feel this kit could make to best serve Android builders while continuing to provide extensible support for building apps?

I have my doubts about using Babel given its immaturity. But thanks for the info.

My setup is like this:
index.android.js
index.ios.js
src/
package.json

Inside my index.android.js and index.ios.js files is the following code:
require('./src');

And finally inside ./src dir, is a file index.js, which is completely written in ES6/7 (I have stage-0 flag enabled in .babelrc (see above)).  The RN packager picks this up all relatively easily, and my app runs just fine.  Source maps work too.
I feel like this kit should be deprecated and nobody should use webpack anymore for RN development.  I literally spent hours trying to configure it, get it working, used it for months, just to run into the same problems over and over again with webpack.  Webpack is unstable and I dislike it (I'm speaking from hours of REALLY intense bugs, debugging, and configurations, not just saying this to put hate on anyone's projects or packages).  If I were maintaining this, I'd put a DEPRECATED notice on the Readme.md and disable Issues here on the settings of the repo.  It's just way too messy to try to use RN with Webpack.  Maybe React and Webpack are fine, but with RN you have to worry about all the RN packages that the packager picks up, all the ignore files and package names, image assets, etc.
If you had doubts about Babel, it's what RN itself is using and it's stable for development IMO (at least 100x more than Webpack).  True, it breaks sometimes, but only because they are moving so fast and are at least somewhat more organized :laughing:.

@jhabdas It works aftter reloading, but after some changes, eventually it gives the same error again, couldn't realize why.
After some readings:
RN JS Env, @niftylettuce feedback, and by looking at RNWS which is "not actively maintained", wouldn't be better / simpler if the starter kit relies on RN packager, with changes needed made on .babelrc ? After all, the RN itself relies on babel.

Android works fine out of the box with the packager.  No problems there.  I add this to my package.json and run it whenever I'm running on a device plugged in over adb...
"adb-reverse": "adb reverse tcp:8080 tcp:8080 && adb reverse tcp:8081 tcp:8081",

Then run it with npm run adb-reverse.

Stage 0 seems like a bad idea to me as its too edge to build maintainable apps with. But, again, thanks for the info. There are a lot of ways to build, and it'd be great to learn from what others are doing.

Oh!  Another thing that makes life easier for Android/iOS reloading etc - is my package "Frappe".
Check it out at https://github.com/niftylettuce/frappe.

I spent time working through RN Android setup this weekend. I'm still working on it. I feel it's important to build maintainable and extensible apps. If you're interested in a quick win all have a choice on how to build. But I do not feel using the methods provided using the default RN JS language extensions is the best way to build apps either for iOS or Android.

+1

I'll put an hour on this today for the +1. If the example app in the RNWS repo isn't experiencing the same issue the problem shouldn't be too hard to isolate. Thanks for the nudge.

Got sidetracked publishing a new blog post and I'm still stuck getting emulators functioning in the IDE.
Could someone try one of the Example RN apps in react-native-webpack-server repo and let me know if your emulator fires up without issue there?

Just ran the BabelES6 example in that repo and got the following screen:

Thanks for checking. Next step would to to look back at older Releases of
this kit to see if there's a possible conflict with newer RN tooling. iOS
requires some modifications. And it seems Android will as well following
the latest fresh init in 2.21.
On Sun, Mar 20, 2016 at 7:57 PM Joe Meissler<EMAIL_ADDRESS>wrote:

Just ran the BabelES6 example in that repo and got the following screen:
[image: error]
https://camo.githubusercontent.com/fb5a961a95bc291370d3d8b04a66ded216b4d8e3/687474703a2f2f692e696d6775722e636f6d2f436565456b396f2e706e67
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/jhabdas/react-native-webpack-starter-kit/issues/58#issuecomment-199072727

Greenkeeper just submitted https://github.com/jhabdas/react-native-webpack-starter-kit/pull/72 for RN the latest 0.22 patch, which gives a different backtrace:
03-21 21:59:35.420 2570-2570/com.app E/unknown:React: Exception in native call from JS
                                                      java.lang.RuntimeException: java.util.concurrent.ExecutionException: java.lang.RuntimeException: ReferenceError: Can't find variable: __fbBatchedBridge (<unknown file>:1)
                                                          at com.facebook.react.bridge.CatalystInstanceImpl.runJSBundle(CatalystInstanceImpl.java:171)
                                                          at com.facebook.react.ReactInstanceManagerImpl.createReactContext(ReactInstanceManagerImpl.java:879)
                                                          at com.facebook.react.ReactInstanceManagerImpl.access$700(ReactInstanceManagerImpl.java:104)
                                                          at com.facebook.react.ReactInstanceManagerImpl$ReactContextInitAsyncTask.doInBackground(ReactInstanceManagerImpl.java:200)
                                                          at com.facebook.react.ReactInstanceManagerImpl$ReactContextInitAsyncTask.doInBackground(ReactInstanceManagerImpl.java:183)
                                                          at android.os.AsyncTask$2.call(AsyncTask.java:295)
                                                          at java.util.concurrent.FutureTask.run(FutureTask.java:237)
                                                          at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:234)
                                                          at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1113)
                                                          at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:588)
                                                          at java.lang.Thread.run(Thread.java:818)
                                                       Caused by: java.util.concurrent.ExecutionException: java.lang.RuntimeException: ReferenceError: Can't find variable: __fbBatchedBridge (<unknown file>:1)
                                                          at com.facebook.react.common.futures.SimpleSettableFuture.get(SimpleSettableFuture.java:68)
                                                          at com.facebook.react.bridge.CatalystInstanceImpl.runJSBundle(CatalystInstanceImpl.java:147)
                                                          at com.facebook.react.ReactInstanceManagerImpl.createReactContext(ReactInstanceManagerImpl.java:879)
                                                          at com.facebook.react.ReactInstanceManagerImpl.access$700(ReactInstanceManagerImpl.java:104)
                                                          at com.facebook.react.ReactInstanceManagerImpl$ReactContextInitAsyncTask.doInBackground(ReactInstanceManagerImpl.java:200)
                                                          at com.facebook.react.ReactInstanceManagerImpl$ReactContextInitAsyncTask.doInBackground(ReactInstanceManagerImpl.java:183)
                                                          at android.os.AsyncTask$2.call(AsyncTask.java:295)
                                                          at java.util.concurrent.FutureTask.run(FutureTask.java:237)
                                                          at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:234)
                                                          at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1113)
                                                          at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:588)
                                                          at java.lang.Thread.run(Thread.java:818)
                                                       Caused by: java.lang.RuntimeException: ReferenceError: Can't find variable: __fbBatchedBridge (<unknown file>:1)
                                                          at com.facebook.react.bridge.ReactBridge.loadScriptFromAssets(Native Method)
                                                          at com.facebook.react.bridge.JSBundleLoader$1.loadScript(JSBundleLoader.java:32)
                                                          at com.facebook.react.bridge.CatalystInstanceImpl$2.call(CatalystInstanceImpl.java:157)
                                                          at com.facebook.react.bridge.CatalystInstanceImpl$2.call(CatalystInstanceImpl.java:148)
                                                          at com.facebook.react.bridge.queue.MessageQueueThreadImpl$1.run(MessageQueueThreadImpl.java:73)
                                                          at android.os.Handler.handleCallback(Handler.java:739)
                                                          at android.os.Handler.dispatchMessage(Handler.java:95)
                                                          at com.facebook.react.bridge.queue.MessageQueueThreadHandler.dispatchMessage(MessageQueueThreadHandler.java:31)
                                                          at android.os.Looper.loop(Looper.java:148)
                                                          at com.facebook.react.bridge.queue.MessageQueueThreadImpl$3.run(MessageQueueThreadImpl.java:187)
                                                          at java.lang.Thread.run(Thread.java:818)
03-21 21:59:35.470 2570-2587/com.app W/EGL_emulation: eglSurfaceAttrib not implemented

After visiting the release history for this kit the error encountered upon Android simulation varies by version. I believe users have been working around the problems by using adb and running directly devices. What have your experiences been?

I just tried to run an example of the react-native repo and it did work. After I got that running I again tried it with the starter kit but still the same error. I'm not sure if that helps. I'm further no it, if I have something else I will let you know.

I am experiencing the same "Module AppRegistry is not a registered callable module" error when running inside an emulator.
I did also make the android bundle by running webpack with the given config and it works perfectly on react-native-playground. The build seems to be working fine so it's not in the javascript code. The issue seems to be in the setup of reactnative?
Maybe in the react-native-webpack-server or something?

Wanted to chime in that I have been getting the "AppRegistry" error mentioned in this thread on a separate Android RN project after upgrading from RN 19.0 to 23.1. Suggest this is perhaps a RN issue and we might want to post on the main RN issues thread. We'll need some +1's.

Same thing for me... Completely agree with @niftylettuce, I'd deprecate this project. (sent you an email @niftylettuce)

@ferologics I've never heard of a starter kit being deprecated due to a bug. Am I missing something?

@ferologics I don't have any intention of deprecating project due to a bug running Android in a simulator. This project was extracted from the [Lumpen Radio](git@github.com:jhabdas/lumpen-radio.git
https://github.com/jhabdas/lumpen-radio) benefit project after delivering the iOS app to the App Store. At that time RN Android was just emerging into the RN ecosystem and, as suggested in the project README, Android users will likely experience some bumpiness until proper support is added. Hence this issue.

I'm getting this error running on an actual device

Thanks noting that @tjgillies. Just to verify, you were trying to use adb via the NPM script in the package manifest to connect and are using the required version of Android specified in the README? I'd love to debug the Android error, but it feels like it's in a downstream dep and I'm not sure where to start.

I was trying to run over adb connected to wifi. When I used an actual usb cable it worked.

Isn't this issue caused because of reversing 8081 to 8080 port?

Hi @jhabdas Do you have any update about this? Thanks.

@smileo need to find someone with the time and inclination to debug why the android bundles generated won't load in the simulator but will on an actual device (and RNPlay, from feedback in the thread above).

Getting the same "Module AppRegistry is not a registered callable module." when using a real Nexus 5X and running this projects example code.

One thing that might be related AppRegistry.registerComponent needs to be called when the bundle loads; if you defer it (async in any way), you get this error

@nevir Interesting. These bundles are generated async so perhaps that's the issue.
I spent a few hours debugging this today without any luck. But I was able to develop Android with HMR using the RN CLI with react-native run-android after tweaking build.gradle to point to the src/main.android.js entry file. The whole Android Studio / Gradle experience I found to be a bit wonky. Hopefully developing RN apps for Android gets easier once buck is better integrated into the RN ecosystem. Until then I'm going to lock conversation on this issue as there's not much more to be said here. If someone finds a fix please submit a PR this way. Happy coding!


hotfix: absolute url for matomo icon in microsite

Closes #20902

Hey, I just made a Pull Request!
The icon for matomo was not defined as an absolute path, which caused the icon to not be displayed correctly on https://backstage.io/plugins/
Screenshot:

:heavy_check_mark: Checklist

[ ] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[x] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

Thanks for this fix!


Add test to symfony configuration

Codecov Report

Merging #41 into master will increase coverage by 1.37%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master      #41      +/-   ##
============================================
+ Coverage     93.14%   94.51%   +1.37%
- Complexity      100      101       +1
============================================
  Files            17       18       +1
  Lines           248      310      +62
============================================
+ Hits            231      293      +62
  Misses           17       17

Impacted Files
Coverage Δ
Complexity Δ

src/DependencyInjection/Configuration.php
100.00% <0.00%> (ø)
1.00% <0.00%> (?%)

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 533dc89...bde960a. Read the comment docs.


Aliases map for ibc denoms (hardcoded) in client.toml

add field
modify config structure
add aliases field to context
rm
add aliases to ctx

Closes: #https://github.com/osmosis-labs/osmosis/issues/3655
Changes
Added map to client.toml, which maps human readable denom names (ex: uatom) to their ibc denom versions
In order to get aliases map you should simply call client's Context.Aliases
Documentation and Release Note

Does this pull request introduce a new feature or user-facing behavior changes? yes
Is a relevant changelog entry added to the Unreleased section in CHANGELOG.md? yes
How is the feature or change documented? changelog

I suppose there should also be added some functionality to dynamically generate this map?

@ValarDragon

We can generate / populate the map osmosis-side!

This is actually an illegal syntax in toml  ¯_(ツ)_/¯
However it can be done like this:

I will try the second approach from osmosis-side

@ValarDragon I do not think it is possible to do this from osmosis side. client.toml is being generated on sdk side in ReadFromClientConfig.
We could:

in the same function add functionality to dynamically add map structure to client.toml
somehow manage to do it from osmosis-side. I mean, it is possible I lied a little, but I do not know if that is the right way to do that

can we in run-time read all keys for a toml object? (Instead of having a struct with all of them?)


Fix typo

@graves501 if you force push this CI should run again. Then we can review/merge thanks!

@graves501 if you force push this CI should run again. Then we can review/merge thanks!

Hi, couldn't really force push without any changes, so I basically rebased off of the master branch and force pushed afterwards.


Improve way to incorporate third party objects (Iframes)

Description
The goal would be to simplify how to incorporate third party objects like fig from Plotly. The relationship between get_user_content_url, on_user_content and the url can be complex for new comers or for complex applications using this to create multiple visualizations.
from taipy.gui import Gui, get_user_content_url, notify

def expose_plotly(fig):
    buffer = io.StringIO()
    fig.write_html(buffer)
    return buffer.getvalue()

html = expose_plotly(sankey_graph(data))
uc_url = None

def on_user_content(state, path: str, query: dict):
    return state.html

def on_init(state):
    state.uc_url = get_user_content_url(state, "val", {"name": "param"})

Acceptance Criteria

[ ] Ensure new code is unit tested, and check code coverage is at least 90%
[ ] Propagate any change on the demos and run all of them to ensure there is no breaking change
[ ] Ensure any change is well documented

is this covered by the new part property content ?

Could you reference the issue/PR where we have an example of code of how it works?

from taipy.gui import Gui, State

import plotly.express as px
from plotly.graph_objs import Figure
import typing as t
import pandas as pd

df = pd.read_csv("https://raw.githubusercontent.com/mwaskom/seaborn-data/master/iris.csv")

figure = px.scatter(df, x="sepal_length", y="sepal_width", color="species")

color = "species"

def change_color(state: State):
    state.color = "petal_width" if state.color == "species" else "species"

def get_scatter(color):
    return px.scatter(df, x="sepal_length", y="sepal_width", color=color)

# <|{figure}|plotly|height=40vh|>

md = """
# Taipy Plotly test

<|part|content={get_scatter(color)}|height=40vh|>

<|Change color|button|on_action=change_color|>

"""

Gui(md).run()


Document Kubernetes performance gotchas

I did a performance comparison last night between our default StatefulSet Kubernetes config file and an alternative DaemonSet config on a 3-node v1.7.8 GKE cluster of n1-standard-1 VMs. The performance difference was massive:
When running against daemonset with `hostNetwork` and `hostDir` (using the VMs' 100GB pd-standard boot disks):
_elapsed___errors____________ops___ops/sec(cum)__p95(ms)__p99(ms)_pMax(ms)_____seq(begin/end)
   78.8s        0         146093         1853.3    130.0    176.2    486.5          0 / 73356

When running against statefulset (using a 1GB pd-standard, which our config defaults to):
_elapsed___errors____________ops___ops/sec(cum)__p95(ms)__p99(ms)_pMax(ms)_____seq(begin/end)
   52.0s        0          18023          346.5    520.1    704.6   1208.0           0 / 9071

When running against statefulset (using a 100GB pd-standard to be more fair, since GCE disk size affects IOPS):
_elapsed___errors____________ops___ops/sec(cum)__p95(ms)__p99(ms)_pMax(ms)_____seq(begin/end)
   84.4s        0          30822          365.1    570.4    738.2   2147.5          0 / 15426

I suspect most of the difference is network-related -- we already know that our RPC layer can be a bottleneck, and going through the Docker bridge is not cheap. I would have expected it to be more like a 2x difference, though, not a 5x difference. It's also possible that the way the StatefulSet's disk gets mounted is a little different from the machine's boot disk, but they were all using the same kind of disk (persistent HDDs).
If any Kubernetes customers are particularly worried about performance, I can try to confirm the hypothesis. Just let me know and I'll do so, otherwise I'll probably let this sit for a while. cc @robert-s-lee

Confirmation would be useful for current reference architecture preparation and provide the right expectations for customers who are in the self-evaluation.

This is part of https://github.com/cockroachdb/docs/issues/2937.


test

Describe the bug
A clear and concise description of what the bug is. Include version by typing gh --version.
Steps to reproduce the behavior

Type this '...'
View the output '....'
See error

Expected vs actual behavior
A clear and concise description of what you expected to happen and what actually happened.
Logs
Paste the activity from your command line. Redact if needed.

blah

blah2

blah4

what

reopen

close issue


fix how we ge pkg names

right now we're topping out at 12K

What exactly is topping out?

i have the code to get pkg names kind of hard coded https://github.com/ropensci/cchecksapi/blob/master/scrape.rb#L91-L108 - working on a while loop now

limit max is 6000, correct?

Why not just get them in one query? This code is not live, right?

Btw. I can add an API point that just lists all packages.

i thought there was a max for limit, but maybe not?
yeah, an endpt to just list pkgs would be helpful

fix in for  now

http://crandb.r-pkg.org/-/pkgnames?limit=10
FYI, just a second or so to get all names...


all the "l" is in bold letter when brought to view in pdf format

try opening this file in any other pdf viewer.

it once happened with me for a specific adobe pdf viewer a long ago.

Thank you
On Tue, Dec 15, 2020, 8:55 PM Dinesh Solanki<EMAIL_ADDRESS>wrote:

it once happened with me for a specific adobe pdf viewer a long ago.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/AmruthPillai/Reactive-Resume/issues/351#issuecomment-745363980,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALWP6IGQQZKC3PB4LS7ZE3LSU55XHANCNFSM4SHMFKJQ
.

Thank you
…
On Tue, Dec 15, 2020, 8:55 PM Dinesh Solanki @.***> wrote: it once happened with me for a specific adobe pdf viewer a long ago. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#351 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALWP6IGQQZKC3PB4LS7ZE3LSU55XHANCNFSM4SHMFKJQ .

is the issue solved, if yes, please close this.


eslint and prettier

Eslint and prettier set to run on "grunt dev" with auto fixes. After eslint and prettier run, the sever will start.
.eslintrc: changed to match p5 styling guide
.gruntfile changes to run eslint and prettier  on "grunt dev"
Installed the following to handle conflicts between eslint and prettier
"eslint-config-prettier": "^6.11.0",
"eslint-plugin-prettier": "^3.1.3",
Autofixes added the an additional 60 files.

Before merging, please take care of styling issues!

closing in favor of #490 which has this commit, and the fixes, and is on the processing repo which you now have access to as well so we can all contribute to it :)


Redis not firing "failed" method

Laravel Version: 5.8.16
PHP Version: 7.1.29
Queue Driver: Redis
Description:
I've got a chain of jobs that are all queued, when any of the jobs fail I broadcast an event for pusher. This works perfectly with the sync driver, but with redis it seems like the failed method never gets triggered.
Steps to reproduce

Create a queued job
Change the driver to redis
Add some sort of logging into the failed method
Throw an exception in the handle method

I figured it out, I didn't have the $tries property set.


currency symbols

change order with currency symbols ( input: "$30" => "USD 30")

There should be a control to disable this.

Thank you


This happens when the areas where the DR should be applied aren't the same.
In this case the first item gives DR to torso groin and vitals, the second item to all areas. This doesn't match.

I mitigated it be using
DR+1 eye skull face *arm *leg torso groin hand foot neck vitals
on the second item.

Good workaround!
I found the issue and it will be fixed in 0.10.5.


Bug when mixing DialogContent and DataTemplates in a DialogHost instance in XAML ?

Pretty sure this was working on previous versions of the nuget package. I moved to 0.7.7 and now i'm seeing a wrong popup when attempting to select the dialog content vs a data template.
When using a data template using the 'Show' method then later attempting to select IsOpen shows the previous DataTemplate instead of the DialogContent.
Here is the snippet of my XAML:
<dialogHostAvalonia:DialogHost
x:Name="DialogHost"
IsOpen="{Binding CommandError, Converter={x:Static ObjectConverters.IsNotNull}}"
Identifier="MainDialogHost"
DialogClosingCallback="{Binding DialogClosingHandler}"
DialogMargin="16"
dialogHostAvalonia:DialogHostStyle.CornerRadius="8">
dialogHostAvalonia:DialogHost.DataTemplates

</dialogHostAvalonia:DialogHost.DataTemplates>
    <dialogHostAvalonia:DialogHost.DialogContent>
        <StackPanel Orientation="Vertical">

....
When the binding trigger the IsOpen it will show a previous DataTenmplate used befaore. If no DataTemplate was used before then the behavior is to show the proper dialog content.
Can anybody confirm if this is a valid bug?
Thanks in advance,

Hello, @rodrigovaras.
I was pretty sure what this is an Avalonia behavior. Can you provide an minimal reproduceable example, cuz i can't really understand order of actions tbh?

Hello, @rodrigovaras.
I was pretty sure what this is an Avalonia behavior. Can you provide an minimal reproduceable example, cuz i can't really understand order of actions tbh?

XAML has defined a DataTemplate and a DialogContent section.
I simulate an error during my 'Connect' command which will trigger the 'IsOpen' property.
Result is correct the Host show the XAML content of my error description , etc..
So far good, now i use  a menu item which trigger by code use the Show method that trigger the proper DataTemplate, i have 3 different ones. So far so good.
Finally i trigger another Connect error which should display my dialogcontent XAML, but it shows the latest XAML form the last DataTemplate.

Closing as stale. If the issue still relevant - feel free to reopen this or create a new one.


request for ALSA docs

I'm having trouble getting audio working on my kiss install since most apps are built to use alsa instead of kiss, which I'm not familiar with. If anyone has the time, I'd massively appreciate a wiki article on this.

There's no interest for this.


Useless logs after each step with cypress-if

Current behavior
I added cypress-if plugin into my project and I can see some new logs after each step

And this type of logs so long after huge failed scenario.

Desired behavior
I looking for solution to turn off this logs or something like that.
Test code to reproduce
https://github.com/triori/badeball_cypress-if
This is a small repo with three of useless test.
The modules and structure used are the same as in my work project.
You can run it like npx cypress run and at the end of failed test log you can see this type of logs.
Versions

Cypress version:  13.6.6
Preprocessor version: 20.0.2
Node version: 20.10.0

Checklist

[x] I've read the FAQ.
[X] I've read instructions for logging issues.
[X] I'm not using<EMAIL_ADDRESS>(package name has changed and it is no longer the most recent version, see #689).

These logs are hidden by default. I can't say why cypress-if makes hidden commands appear, nor do I feel like debugging it on their behalf.


date

I'm so sorry, I mistaken the issue title for the search box.

No worries :-) if you have questions the slack channel #franklin is fairly active (discourse also if someone @ me on the issue 😄 )


ElmahCore.Sql is not compliant with DBs with case-sensitive collation

The SQL statements in ElmahCore.Sql can only work on databases with case-insensitive collation. This effectively breaks the execution of Elmah SQL statements on such DBs. This has never been a problem in pre-.NET Core versions of Elamh and can be considered as a significant breaking change that forces to change the collation for the entire DB just just to be able to use Elmah! That is to me absolutely inappropriate and the fix is quite easy - just follow the casing of the DB objects as they are defined.
Examples wrong statements:

The DB objects/columns referenced in the following statements are defined with capital casing (information_schema.tables => INFORMATION_SCHEMA.TABLES)

SELECT 1
WHERE EXISTS (
   SELECT 1
   FROM   **information_schema.tables**
   WHERE  **table_schema** = 'dbo'
   AND    **table_name** = '**elmah_error**'
   )

The statememt for insertion of records is not consistent with the definition of the Elmah table itself!

CREATE TABLE [dbo].[**ELMAH_Error**]
INSERT INTO **Elmah_Error** (ErrorId, Application, Host, Type, Source, Message, ""User"", StatusCode, TimeUtc, AllXml)
VALUES (@ErrorId, @Application, @Host, @Type, @Source, @Message, @User, @StatusCode, @TimeUtc, @AllXml)

Example error when running Elmah on a DB with case-sensitive collation (SQL_Latin1_General_CP1_CS_AS / SQL Server 2019 / version 15.0.2000.5):
System.Data.SqlClient.SqlException (0x80131904): Invalid object name 'information_schema.tables'.
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action1 wrapCloseInAction)    at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action1 wrapCloseInAction)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
at System.Data.SqlClient.SqlDataReader.TryConsumeMetaData()
at System.Data.SqlClient.SqlDataReader.get_MetaData()
at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, SqlDataReader ds)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, TaskCompletionSource1 completion, Int32 timeout, Task& task, Boolean asyncWrite, String method)    at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)    at System.Data.SqlClient.SqlCommand.ExecuteScalar()    at ElmahCore.Sql.SqlErrorLog.CreateTableIfNotExists()    at ElmahCore.Sql.SqlErrorLog..ctor(String connectionString)    at ElmahCore.Sql.SqlErrorLog..ctor(IOptions1 option)

I just created a pull request for the fix. I will appreciate a lot if the fix is released soon since I'm currently finalizing the migration of a big product from .NET Framework to .NET 5 (ASP.NET Core) and this problem is quite blocking for me.
https://github.com/ElmahCore/ElmahCore/pull/81

I just created a pull request for the fix. I will appreciate a lot if the fix is released soon since I'm currently finalizing the migration of a big product from .NET Framework to .NET 5 (ASP.NET Core) and this problem is quite blocking for me.
https://github.com/ElmahCore/ElmahCore/pull/81

Many thanks for the extremely quick release!!!

Many thanks for the extremely quick release!!!


提示语句应当是 Remote file '{}' exists but is NOT different, skip uploading. 吧

https://github.com/houtianze/bypy/blob/6f4b69a7e4cc0b15c87130d5538f4f986708d7c7/bypy.py#L1920
1920 行 提示语句是不是写反了.
应当是 Remote file '{}' exists but is NOT different, skip uploading. 吧?

确实写错了，感谢指正。春节快乐：）

已修正。


Adds 'Export Flow to Logic App' script, solving #2067

Adds 'Export Flow to Logic App' script, solving #2067

Coverage remained the same at 100.0% when pulling 27d95108aa4d36a28b58bb80951fdab49e0cd1c7 on appieschot:main into 9e15dcb14a9c6a3e6c0d50be7226deb76b3d3206 on pnp:main.

Coverage remained the same at 100.0% when pulling 27d95108aa4d36a28b58bb80951fdab49e0cd1c7 on appieschot:main into 9e15dcb14a9c6a3e6c0d50be7226deb76b3d3206 on pnp:main.

Whoops, made a rooky mistake by merging to my own master, sorry about that. Will update asap!

Whoops, made a rooky mistake by merging to my own master, sorry about that. Will update asap!

Marked the PR as draft. Could you please mark it as ready for review when done?

Marked the PR as draft. Could you please mark it as ready for review when done?

@waldekmastykarz  updated; should only contain the last commit. If you want I can also push that last commit to a seperate branch and do a new PR, but looking at it this looks good :).

If the rebase succeeds all is good 👍

Oke second time I screw up because its in the wrong stuff. Ill remove this PR and create a new one with a propper branch, sorry


Spike on HTTPS reverse proxy for pd

We want to expose pd's gRPC service over HTTPS on 443/TCP. For now, it'd be enough to use a reverse proxy that speaks h2/grpc. The goal is to use Buf Studio to query the protos. Here's an example URL: https://studio.buf.build/penumbra-zone/penumbra/penumbra.view.v1alpha1.ViewProtocolService/ChainParameters?target=https%3A%2F%2Fgrpc.testnet-preview.penumbra.zone&selectedProtocol=grpc-web (n.b. change the target URL param as necessary)
Attempt to use caddy to expose a fullnode's pd service over HTTPS. We think the h2c:// scheme would enough; see this HN comment and the official Caddy docs. Additionally, see the Buf Studio docs on CORS for necessary headers.
This work is towards longer-term efforts like #1406 & #1556. For now, we simply want to unblock external partners who are consuming the protobufs in browsers.

❯ curl -I https://shadow.petrichor.guru
HTTP/2 200
access-control-allow-origin: https://studio.buf.build
alt-svc: h3=":443"; ma=2592000
content-type: application/grpc
date: Thu, 15 Dec 2022 01:08:59 GMT
grpc-status: 12
server: Caddy
content-length: 0

That shows working TLS termination with an HTTP 200 response. That's progress! But it isn't enough to make Buf Studio happy. Why not?

Caddyfile for serving the above

shadow.petrichor.guru

# proxy pd, as grpc service
reverse_proxy h2c://<IP_ADDRESS>:8080

# CORS support for Buf Studio
header / {
  # Access-Control-Allow-Origin *
  Access-Control-Allow-Origin  https://studio.buf.build
}

Progress, but still short of the mark. Here's what's running:

:heavy_check_mark: full node running at buf-studio.penumbra.zone
:heavy_check_mark: pd exposed directly on 8080/TCP
:heavy_check_mark:  pd exposed via h2c reverse proxy at 443/TCP, with TLS termination handled by caddy

If I use this URL in Buf Studio, I see an error:
penumbra.view.v1alpha1.ViewProtocolService
ConnectError -

However, in the web console for my browser, I see a 200 OK on the OPTIONS request. (Previously, a CORS error was displayed. Massaging the associated HTTP headers via the Caddyfile resolved that problem.)  What does work on Buf Studio is this URL, which requires that you:

Run buf beta studio-agent locally on CLI
Choose Set Agent URL and enter http://localhost:8080
For Target, enter http://buf-studio.penumbra.zone:8080.

For what it's worth, you can also set the Target to http://fullnode.testnet.penumbra.zone:8080 and it'll work just as well. So it looks like we can use Buf Studio, even to talk to a non-TLS'd endpoint, as long as we leverage the studio-agent. While the HTTPS setup doesn't work with Buf Studio, it does appear to serve well.

The studio-agent is running a local proxy, but the point of having solid TLS/grpc-web support for pd is so that it's possible to use without any additional infrastructure. So using studio-agent doesn't really solve the problem, because the goal isn't to make Buf Studio specifically work, it's to enable web content to make RPC requests to Penumbra nodes.
I'm a little confused about what's going on with the CORS headers there. Previously, I got Buf Studio to work against pd without any proxying, using the experimental work in #1666, and didn't have to do anything special with headers.
So it seems to me like the problem is likely somehow related to the way Caddy is being used as a proxy -- which reinforces the goal of having this functionality built into pd natively, rather than forcing people to debug Caddy issues to be able to make requests.

I rebased the experimental support I did in #1666 onto the 038-kalyke tag here: https://github.com/penumbra-zone/penumbra/tree/acme-rustls-kalyke
Maybe we could try running that on a publicly accessible machine with a DNS name, and see if it still works?

Aye, giving that a shot now...

New server up at pd-tls.penumbra.zone, running the code from the acme-rustls-kalyke branch. Try this URL for Buf Studio. Does that work for you, @hdevalence? Works for me:

Yep, works for me. It's a bit weird and uncomfortable that the experimental auto-https code works without extra setup, but Caddy doesn't.  It might be useful to compare headers or something between them to see if we get any clues about why?

Let me take a look. Downgrading caddy to HTTP1.1 may help.

Downgrading caddy to HTTP1.1 may help.

That was it. Caddy defaults to HTTP2, and we explicitly set HTTP1.1 for tonic-web here: https://github.com/penumbra-zone/penumbra/blob/349f66f3b2e7facfac1ba71a25395c9ea0a251f9/pd/src/main.rs#L212-L213
Try buf-studio.penumbra.zone in Buf Studio. Working well for me over here. Full caddyfile:
# Downgrade to HTTP1.1 from the default of HTTP2.
{
    servers :443 {
        protocols h1
    }
}

buf-studio.penumbra.zone

# proxy pd, as grpc service
reverse_proxy h2c://<IP_ADDRESS>:8080

# Make runtime logs more verbose
log {
        level DEBUG
}

So we can easily bolt on a temporary HTTPS solution on any testnet with this method. Will leave these two machines running for 038-kalyke, and update "pd-tls.penumbra.zone" for 039, when the time comes.
Haven't done this yet, but omitting the http1 downgrade should be possible if we're using https on the frontend. Will try that soon and note results.

Sick, nice find!
Does that config force HTTP/1 only, or allow either HTTP/1 or HTTP/2?  We'll need HTTP/2 to support native grpc; in pd we serve both simultaneously.

As written it's h1 only, but I just updated it to h1 h2 and that appears to be working fine still. Once we land #1666, we can do full h2 across the board, we won't need HTTP1.1 support anywhere, AFAICT.

I think we might need/want h1 support in pd to make grpc-web work, although I'm not clear on the details -- it's recommended by the tower-web docs, though.

Made a small change to the cluster config, which provides automatic HTTPS for pd: https://grpc.testnet-preview.penumbra.zone. That URL works just fine in Buf Studio, and will remain working. The same setup isn't yet live for the weekly testnet, given delays in #1659, but plan of record is to cut over on the deploy for #1757. I'll handle that over there.
Leaving the pd-tls machine up the interim, since it's nice to have an HTTPS target that's running the stable testnet. As soon as 039-praxidike goes out, that machine can be cleaned up.

As of 040-themisto (#1814), we now have a stable HTTPS for talking to pd: https://grpc.testnet.penumbra.zone. That URL can be used in Buf Studio with the gRPC-web connection option:

That URL will remain active as we release subsequent testnets. Similarly, https://grpc.testnet-preview.penumbra.zone exists, for the very latest work merged into main.
Cleaned up the temporary "pd-tls" and "buf-studio" hosts, since they're no longer necessary.


Support for jump to template code from WebView

This feature currently is experimental and rely to install @volar/experimental.
Hope to achieve without configuration, but it may not be possible.
https://user-images.githubusercontent.com/16279759/119563799-9bd6d500-bdda-11eb-85ee-eebbd5b5a59e.mov

It's absolutely a killer feature，😄


Replace ILayer.Style with a ILayer.Styles like IFeature.Styles

The problem

The ILayer.Style is a single item while the IFeature.Styles is a collection. That is odd.
The default layer style is a common confusion for users that work with styles on features.
Sometimes users want one style to be on top of another (like a callout that needs to be above all the symbols). This is now possible by adding the symbol style and callout style to a StyleCollection and assign it to the ILayer.Style. You have to know about this possibility something. If we have a ILayer.Styles users will be able to discover that functionality.

Complications

If there is no default symbol users will not see anything in their map unless they explicitly add it. One solution would be to just leave this up to the user, but perhaps this will result in a lot of frustration. Solutions:

Perhaps we should write a warning to the log, but then again sometimes the users just does not want a symbol (yes there will be cases where users want this), should we write a warning?
Render something in a gray semi-transparent default style as long as there is no style. The user will at least see something. Perhaps only in debug mode. Problem: but our design is that the style determines the renderer, but here we would need some workaround.
Add a default symbol to the ILayer.Styles anyway. So, the layer will just have a single style when created. Downside: There will still be confusion for people working with IFeature.Styles. We have to pick some default style for each layer.

The current RasterFeature needs a RasterStyle. This is necessary in our logic because the style determines the renderer. It makes no sense for the user to add this, it adds no information, it is just necessary to make it work. Currently we solve this by setting a default style. This solution will disappear, so we have to come up with an alternative.
Many samples would need extra lines to add the style. It would be nice of the minimal code would be necessary to add a layer.

The proposed solution

Replace the ILayer.Style with an ILayer.Styles collection like in the IFeature.Styles.
The ILayer.Styles will be empty by default.
Create the OpenStreetMap layer with an extension method which add the RasterStyle
IMPORTANT: Add a warning to the log whenever a feature has not style in ILayer.Styles and IFeature.Styles. Make this depend on a ILayer.LogNoStyleWarning property so that it is possible to remove this warning if you choose to have no styles in some scenarios.

One thing first: the layer style is drawn first, then the feature style.
The problem comes up only for new users.  They want a fast success by seeing the map and a feature on the screen. We will have such thing when bringing the MapView things to MapControl. one thing is the Marker. There is no need to think about features and styles. If they want to have more advanced styles, then they have to go deeper into  features and style. The concept is very flexible, but you need some time to get it.
As first step I would things more consistent by using same names and same types.

The problem comes up only for new users.  They want a fast success by seeing the map and a feature on the screen. We will have such thing when bringing the MapView things to MapControl. one thing is the Marker. There is no need to think about features and styles. If they want to have more advanced styles, then they have to go deeper into features and style. The concept is very flexible, but you need some time to get it.

This is the 'ease of use' argument, which is a valid argument, but you have to carefully weigh the pros and cons every time. There are three things I want to say about it.
Ease of use is often a short term thing
Very often a solution that improves 'ease of use' at first only complicates things later on. I see this very often in api designs where the implementation is abstracted away from the user.  But where there is something failing underneath or they need to support more complicated scenarios it becomes harder to fix. There are tweaks to get things done in their current solution, but it is hard to get right because users still don't understand what is going on. To get back on track again they have to switch to another kind of solution, but users often stay stuck in their current solution because the switch seems such a big investment.
Also the component developers go along with the users on this 'ease of use' track, by adding more add-hoc functionality to their 'ease of use' solutions, which keeps users longer on this dead end road.
An example is our editing support. This was originally part of the samples. So, low ease of use. Users would have to copy a lot of code to get it working. Then we moved this to the widgets (in itself a good decision because it makes things more maintainable), which made it very easy to get started, but then it did not support all user scenarios and we received feature requests. We could go along with this by making the editing widget more flexibly, but it ends somewhere. So, I think that by pointing users to the editing widget implementation we can prevent a lot of misery.
Add ease of use by offering composition
Above we described a problem of many 'ease of use' solutions, but I think it does not have to be that way. With the Map extension method approach I hope to achieve the same ease, while also putting the user on the compositional track. The extension methods make it easy to get started, but we should immediately point them to the implementation of the extension method and should stimulate them to copy that code to their own solution as soon as they require more advanced functionality. In general I think it is good to point users to our implementation. I have seen you (@charlenni) answer a question by posting the url to the VisibleFeatureIterator.cs. I like it that way. And we should try to keep our code comprehensible to our users.
About ease of use with composition. Instead of this:
Map.Widgets.Add(new SomeComplicatedWidget());

I would prefer this:
Map.AddSomeComplicatedWidget();

That is just as easy. Not sure it is possible to make it this easy, but this is what I aim for. We may also find other ways to support composition.
Ease of use versus maintenance
Adding support to make specific scenarios easy often complicates the code. And, like described above, when you start on that track you later have to add more options to support other scenarios. Also, making general changes becomes harder because you need to take into account the effect on those components. More stuff means more problems, which means less time to make progress on more fundamental changes. I am maintaining this project now for ten years and I intend to continue doing that. So, I feel free to choose not to add functionality if I suspect it will make the maintenance higher.


Metrics within the linkerd mesh explorer

Would be really neat to see if we can surface metrics into the explorer directly

Yes!


Voice Over doesn't read the value typed via vscode.window.showInputBox

Issue Type: Bug
An extension calls vscode.window.showInputBox() to read a value. User uses Voice Over. It does not read the value typed by the user inside the input box.
Expected:
Voice Over should read the value typed by the user in the input box.
VS Code version: Code 1.25.0 (0f080e5267e829de46638128001aeb7ca2d6d50e, 2018-07-05T13:11:58.697Z)
OS version: Windows_NT x64 10.0.16299

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz (8 x 3408)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwarerasterization: disabled_softwarevideo_decode: enabledvideo_encode: enabledvpx_decode: enabledwebgl: enabledwebgl2: enabled

Memory (System)
31.92GB (23.21GB free)

Process Argv
C:\Program Files\Microsoft VS Code\Code.exe

Screen Reader
no

VM
0%

Extensions (2)

Extension
Author (truncated)
Version

cpptools
ms-
0.17.7

vsliveshare
ms-
0.3.472

@chrmarti this is probably fixed now?

Indeed, this fixed. Most likely by the reimplementation.


Handle Git Tag Deletions

Description
If a remote tag is deleted, do not trigger a build.
Value
This prevents un-necessary builds attempting to queue in Vela and also would mark the Hook as passed in GitHub (currently a tag deletion marks the hook push as failed due to Vela failing to find a commit to build off of)
Definition of Done
Deleting a remote git tag does not attempt to trigger a build.
Effort  (Optional)
Unsure, however it looks like the GitHub published message has a root level deleted boolean which is set to true on deletes.
This paired with the root level ref key being set to refs/tags/* should allow Vela to gracefully handle this.

This might be done already. The newest release doesn't seem to be triggering builds for me on tag deletions.

@tmapes are you okay with is closing this one for now then?

Closing!

Thanks!


change pdf font to palatino

Although more styling could be done, this PR changes the PDF font to Palatino.
Closes #98

Looks like you will need to install the latex package:
Error: Failed to compile jupyter-edu-book.tex. See jupyter-edu-book.log for more info.
In addition: Warning message:
In parse_packages(logfile, quiet = c(TRUE, FALSE, FALSE)) :
  Failed to find a package that contains Palatino[.](tfm|afm|mf|otf)
Execution halted
The command "./_build.sh" exited with 1.

The TTF/OTF (as in the error message, not Type-1) because we are using XeTeX.

No idea what any of that means :)

XeTeX is unicode-aware TeX, and uses a newer font format like most other modern software.

Closing this. Thanks @jedbrown for the PR and @moorepants for confirming that these settings can often be a mystery :wink:


Cowswap Trades not working on TallyHo!

Overview
When trying to complete a TallyHo! trade, the transaction fails when using Cowswap. When turning flag off, initial trade looks like its trying to use Cowswap but after selecting Preview Trade it shows correct figures and trade completes on 0x as expected.
References and additional details

Log into app.shapeshift.com and connect to TallyHo!
Populate trade, select preview trade and then confirm and trade
Notice the trade fails with a Something went wrong error
Turn Cowswap flag off and replicate trade
Notice when initially populating trade, the fees look off
Preview trade and notice the fees look accurate
Confirm and Trade and note the trade executes as expected

Acceptance Criteria
Trades should work without having to turn flags off
Need By Date
No response
Screenshots/Mockups
No response
Ownership

[X] If my bounty needs engineering or needs product I have added the respective labels on the right
[X] As the sponsor of this bounty I will review the changes in a preview environment (ops/product) or review the PR (engineering)

Estimated effort
No response
Sponsor / Stakeholder
No response
Bounty Hunters

Join our discord
Include an expected timeline for you to complete work in the work plan when you apply for this bounty!
Please refer to this link for some basic info
Please do not start work on this issue until you are approved in Gitcoin.

closed as tallyho has some green dream


Essentia alternative for Windows

Hello, thank you for this project, it works nice on Linux. However I would now like to run it on Windows, but Essentia with python bindings is not available for Windows, do you know a way around this, or an alternative that can be used instead of Essentia?
Thanks :-)

Hey, I couldn't get Essentia to work on Windows too. I would suggest that you setup WSL if you have Windows 10. WSL is a linux kernel that works within Windows 10, and is fairly simple to use.


Create a workflow to ensure an issue will have labels and the proper project linked

Summary

This issue is creating  a workflow to ensure an issue will have labels, assignees, and the proper project linked

Deadline

09/25/2023

After investigation, it is not possible to add action in the CI workflow to give the issue creator a remind message on UI after validation failure, decided to remove this issue.


[C++][Parquet] Pass all CXXFLAGS to Thrift ExternalProject

Reporter: Uwe Korn / @xhochy
Assignee: Uwe Korn](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=uwe) / @xhochy
Related issues:

parquet-cpp 1.0.0 release (blocks)

Note: This issue was originally created as PARQUET-865. Please see the migration documentation for further details.

Uwe Korn / @xhochy:
PR: https://github.com/apache/parquet-cpp/pull/235

Wes McKinney / @wesm:
Issue resolved by pull request 235
https://github.com/apache/parquet-cpp/pull/235


Add support for elasticSearch typeless API

Support for elastic search typeless API
Problem
As described in elastic docs. Starting from elastic version 8.0 APIs that accept types are removed and a new endpoint needs to be called.
Proposed Solution
Introduce a new configuration variable to enable usage of new endpoint to send data when using ES>8.0

Hello fjogeleit another minor change for elasticSearch compatibility. Not bumping helm chart just in case you wanna include something else. Thankyou!

Hey @guipal, thanks for the contribution. I will check and the missing bump is fine.


Release notes pages not operational for April releases

Describe the bug
I was trying to add the table to the blog post for the April releases but the links to the release notes do not work so I have removed that section for now. Here is the section I was planning to add (Removed from the draft for now until this can be resolved so as not to cause confusion)
Fixes and Updates
This release contains the following fixes and updates.

Temurin 8u412 release notes, including fixes in OpenJDK 8u412

Temurin 11.0.23 release notes, including fixes in OpenJDK 11.0.22

Temurin 17.0.11 release notes, including fixes in OpenJDK 17.0.10

Temurin 21.0.3 release notes, including fixes in OpenJDK 21.0.3

Temurin 22.0.1 release notes, including fixes in OpenJDK 22.0.1

Expected behavior
Links work in the same way as for previous releases such as https://adoptium.net/en-GB/temurin/release-notes/?version=jdk-21.0.2+13
Screenshots

Desktop (please complete the following information):
Doesn't seem to matter since others can replicate it but my initial attempt was on FireFox 124.0.2 on Fedora 39/Linux/x64
Additional context
Initially raised in slack at https://adoptium.slack.com/archives/CLCFNV2JG/p1714033031045209

Working now

This has happened for the last 3 release periods if you look back in the Slack release channel, so we may want to understand why a full update of the API is needed each time (as @johnoliver said in this recent one, there was already a full update that occured the day after the notes were pushed to the binaries repositories, so it is odd he had to trigger another one today).

The infinite spinner  is fixed to finish with a "Oups" message when data cannot be found (for a good or a bad reason).  I reopen the issue, because we need to understand why data are not available in the API.


Pump and Fan RPM is Zero After Waking From Sleep

It seems it is always zero after waking from sleep.  I have to restart FanControl to get it to register.  Does the DLL somehow need re-initializing or something?  Thanks!

If you have nzxt cam installed get rid of it in my experience with my 240 aio cooler works perfecly without the cam software!! So unless customizing the aio display is that important nzxt cam doesnt serve a purpose it just gets in the way


Training/Validation metrics for BasicVSR++

Thank you for releasing the code of BasicVSR++!
I am trying to replicate the training on my machine. However, there seems to be a mismatch with the reported metrics. Could you please help me figure out how to replicate the exact results which have been reported in the paper / repository?
I trained the Vimeo90k BD model on a single GPU with initialization from the pretrained REDS model. These are the training logs. As can be seen, the final PSNR/SSIM are 27.9380/0.8522 which is much lesser than the paper reported values 29.04/0.8753.
Similarly, I trained the Vimeo90k BI model on a single GPU with initialization from the pretrained REDS model. These are the training logs. As can be seen, the final PSNR/SSIM are 27.3268/0.8253 which is much lesser than the paper reported values 27.79/0.8400.
I have also compared these values with the logs available in the documentation and I notice the same mismatch.
I have started training the REDS model. Since I was getting an OOM (24GB does not seem to be enough), I have changed the value of samples_per_gpu to 2 instead of 4 and the starting learning rate of the optimizer to 5e-5 instead of lr=1e-4. Compared to the documentation, I do notice that the PSNR is lower during my training, but I will provide an update on this after this training is completed.
Is there any mistake in the steps I have followed?
P.S.: For confirmation regarding the data used, evaluation of all the 3 pretrained models on the data (REDS model on REDS4, Vimeo90k BI and BD on their respective test sets) yielded accurate results. All LR data was prepared using the same script and was also used with BasicVSR / IconVSR. So the data is correct.

Hi, I think the largest difference is the batch size.
During finetuning on Vimeo-90K, I used 4 GPUs to train, and the batch size per GPU is 2. Therefore the total batch size is 8. In your training, you use 1 GPU and the batch size is 4.
Actually I just found that the configurations are problematic. The batch size there is incorrect. I will modify it. For all the models, the total batch size is 8.

Hi. Thank you for your response!
I understand. For Vimeo90k BI and BD, I am using 1 GPU and I have set the samples_per_gpu to the default value of 4. If I set the batch size to 8, I will not be able to train the model since it will go out of memory. Hence, I plan to scale the learning rate down by 2 as well and start from lr=5e-5. Could you please suggest if I need to consider any other aspects in order to get this training run to work?
Similarly, for the REDS model, and a single GPU, the maximum samples_per_gpu supported is 2. Any bigger batch size will lead to OOM. Similar to the above approach, I plan to scale down the learning rate by a factor of 4 and start from lr=2.5e-5.
Please do let me know if this seems like a viable approach.

I think what you are doing is reasonable. But it could lead to performance drop.


Can I ask a question? why not lock in here.  See the link below

https://github.com/nakabonne/tstorage/blob/832a3826434cb92acec0b7d3893cd7bf75c22c7e/partition_list.go#L77-L79

Hi @keroro6, thank you for your interest.
I would say we don't have to lock there at all. You can check it by writing a tiny test code like:
func TestInsertRows(t *testing.T) {
	node := &partitionNode{
		val: &fakePartition{
			minT: 1,
		},
	}
	list := &partitionListImpl{
		numPartitions: 1,
		head:          node,
		tail:          node,
	}
	for i := 0; i < 10000; i++ {
		go list.insert(newMemoryPartition(nil, 0, ""))
	}
}

You can see any data race doesn't occur.
$ go test -race -v -run=TestInsertRows
=== RUN   TestInsertRows
--- PASS: TestInsertRows (0.26s)
PASS
ok      github.com/nakabonne/tstorage   0.550s

I'm opening to any questions.

Thanks for your reply. I will try. I'm interest to the project really

Glad to hear that. Ask me anything.

Let me close this. Feel free to re-open if you come up with an additional question.


Bug in ccSGD optimizer

The ccSGD optimizer does not support types other than Float32, and crashes MXNet if another type is tried. For concreteness,
dataType = np.float64
arr = mx.nd.array([1,2,3], dtype=dataType)
opt = mx.optimizer.create("ccSGD")
opt.update(1, arr, arr, ())

crashes with error message:
Check failed: DataType<DType>::kFlag == type_flag_ TBlob.get_with_shape: data type do not match specified type.Expected: 1 v.s. given 0
[16:42:32] /Users/sebastianb/Software/mxnet/dmlc-core/include/dmlc/logging.h:245: [16:42:32] src/engine/./threaded_engine.h:295: [16:42:32] /Users/sebastianb/Software/mxnet/mshadow/mshadow/./tensor_blob.h:556: Check failed: DataType<DType>::kFlag == type_flag_ TBlob.get_with_shape: data type do not match specified type.Expected: 1 v.s. given 0

This does not seem to be documented behaviour, and all the other optimizers support multiple types.

ccSGD is implemented before MXNet had type support.
I'll add type support to it when I have time.
You are welcome to do it if you like. src/operator/convolution-inl.h is a good reference.