Is your work published?

Same as title. Since I want to know some detail about your work, it's better for me to read the technique in your paper, How can I find it?

Thanks for your interests Haoxiang.
I haven't published this project as a paper, though you may find the overview and optimization described in the README.md file of the project. Feel free to comment if you are interested in more details.

So, do you mean there is some new techniques in your project? Or are you implement the algorithm of some others?
best.

Good question. This project is more engineering oriented, so the quick answer is no particular new techniques are proposed.
In general that is, multi-threading, bfs, collision detection, indexing etc, and I only make use of them organically. If you are more interested in the state-of-the-art algorithms in the research domain, this project may fail your expectation.


[BUG] Index was outside the bounds of the array.

Error log after i enabled logs and clicked OK :
[5/10/2020 6:08:56 AM] (Error) Runner - The Master Worker has encountered an error: Index was outside the bounds of the array.
i can't enable logs for all time, it will make many useless data and make a huge log files (maybe a log level setting is needed to log only errors)

All bots status are on failed (no problem)
and proxies are reloaded from remote source (localhost)
idk problem is because of proxies or combo, maybe combo is too big for OB?

ahhhh, i'm going to split my wordlist to see the result
i think it's all because of my huge wordlists


Character literal syntax

Discussing with Andy, the existing syntax is !c for the character literal 'c' (if this were C++).
(seen in live code in https://github.com/perimosocordiae/advent-of-code/blob/9de86a79aeb5213539dd71647ab0c6abc51db13f/advent2021/day06.ic#L12)
Some possible alternatives:

!x (current)
!'x'
|x
|x|, | | (space char, i.e. ' ')
\x``
%c{x}
Of course, this works today: "a"[0]
So you could do this: "a"'as_char or as_char("a") (as_char or to_char)
For array: to_char_array("abc")

Andy notes that for something like %c{x}, you're burning a unary operator, % without a great reason. And you could just write it as char("x")

Purely going with gut feelings here, I like !'x' the best. The leading ! makes the parse unambiguous, allowing us to reuse ' without losing it's meaning for function calls.
I don't see significant value in supporting array versions, given that "abc" is already a slice of characters.

Why add single quotes at all? The !x syntax was strange at first but I've gotten used to it. The only major issue is !  IMO, but that's not too different from other languages that have \  syntax for escaped spaces.


Cannot read property 'parentNode' of null

I am exploring dragular for drag and drop windows with iframes rather than small simple divs containing texts. Intermittently source element is getting dropped at target but due following exception in code drop event does not fire hence information regarding drag drop get lost.
Uncaught TypeError: Cannot read property 'parentNode' of null
at getParent (dragular.js:1501)
at cancel (dragular.js:974)
at HTMLHtmlElement.release (dragular.js:1021)
Can you suggest way to avoid this exception or if such exception occurs then element moves back to original position.
I have created plunker to explain the problem with these options
dragularService('.containerVertical',{
direction: 'vertical',              // Y axis is considered when determining where an element would be dropped
revertOnSpill: true,               // item returns to original place
removeOnSpill: false                // item will be removed if not placed into valid target
});
https://plnkr.co/edit/VhvHsYSXFzWGGCWjFrjg
Thanks looking forward

Hi.. iframes are not supported, as you can see if you release drag over iframe the dragular lib did not catch the event. However.. I have tested your plunker and did not get the error.. I am on Mac OS Sierra with latest chrome. Could you tell me exact steps to get the error? Thanks

Most of the time error will come when drag happens from bottom to top
for example  moving 5 or 6th element directly to 1st spot that time this exception comes.I agree that iframes is kind of challenging environment for drag drop but when  tried removing iframes and just with plain html this exception comes when we drag bottom items and move towards top. I guess it could relate to container size. If I use small rectangular container then there is less chance of this exception but as the size of dragable container increases exception becomes often particularly when drag action is from bottom to top vertically.
I have updated plunker by removing iframes also attaching screen cast

Regards
San

I happy you managed to fix the problem, even I do not understand how moving controller from body to parent div can influence dragular.. it really interests me.. maybe it is just windows related, because I was moving controler definition around and error did not happened. But I have put too much energy into this, I need it for other projects.. so I leaving this how it is... I hope it will be OK for community. Thanks for your contribution and happy coding ;)


Filtering string with empty space not working

Describe the Bug
When filtering e.g. on Log step - the "show all" string should have two results, but in reality doesn't show any results.
Steps to Reproduce the Bug or Issue

use log step
type "show all" into filter
see no results are displayed

Screenshots or Videos
https://github.com/KaotoIO/kaoto/assets/4180208/134b233f-d554-4424-9a6f-3edaace25ee1
Platform

OS: [e.g. macOS, Windows, Linux]
Browser: [e.g. Chrome, Safari, Firefox]
Version: [e.g. 0.30.0]

This is happening since we're only filtering by property name and should also include title.


DBZ-5760 Only log full row data at TRACE level

https://issues.redhat.com/browse/DBZ-5760

@Naros Applied, thanks!


Code examples not showing

On a few of the pages about Mutexes such as this one: https://wiki.libsdl.org/SDL_UnlockMutex
The code example is not showing. Instead, the following text is shown:
Code Examples
<<Include(SDL_CreateMutex, , , from="## Begin Mutex Example", to="## End Mutex Example")>>

There's an sdlwiki bug for this: https://github.com/libsdl-org/sdlwiki/issues/233


Count badge color too dark

Is your feature request related to a problem? Please describe.
Firefox.
The background color of the count badge should not be black, rather it should be a light grey to integrate better with the Firefox dark theme.
Describe the solution you'd like
Comparison to uBlock origin:

Not sure if this is a default color that can be read from Firefox but the uBlock origin color seems pretty good.

** This is how the Gumbo live count badge shows up in incognito today after the latest google chrome update **

I dont know whats happening, maybe chrome changed something, but now the count badge is literally not readable.

Looks like they changed the default badge's text color.
I'll push an update to fix the color whenever I can.

Thank you very much

The fix (https://github.com/Seldszar/Gumbo/commit/019f805ffba0edbafee11fcd44ca00551c9068b9) will be delivered with the next version (1.10) whenever Chrome Web Store let me publish the update.

It's either using whatever color the browser is using by default or going back to square one.
I'll leave this until Chromium fixes their mess, or provide a way to actually change the text color on MV3.

I do prefer black personally, much more obvious what it wants to say and much more easily readable. When I noticed the red it felt like a bug

Perhaps on Firefox, but since Chrome 102, the text color suddenly became a dark grey, making it really hard to read.
And on the top of that, it's impossible to change this color because MV3 doesn't provide a way to change it.
I guess I can add a special case for specific browsers, but it'll only be yet another band-aid for fixing something I shouldn't think about.

I think this color might do the job for both browsers.
Thankfully, Firefox automatically choose the correct color based on the background color. Chromium should honestly steal this feature.

Let me know if that sounds good to you.

The next update (v1.10.1) will have the color displayed in the previous message, for the time being.
There's currently a pending publication on Chrome Web Store so I'll wait until it's done then I'll push everything.
Closing this issue.


<!--

👋 Welcome!
We’re using Discussions as a place to connect with other members of our community. We hope that you:

Ask questions you’re wondering about.
Share ideas.
Engage with other community members.
Welcome others and are open-minded. Remember that this is a community we
build together 💪.

To get started, comment below with an introduction of yourself and tell us about what you do with this community.

Originally posted by @maanu1234 in https://github.com/maanu1234/workers-sdk/discussions/33

@maanu1234

🙏🏽


cli: skip no-op program buffer writes

Problem
When retrying a program deploy, a buffer account might have already been partially written to but the cli program deployer will try to write the entire buffer again, wasting time and transactions.
Summary of Changes

Before pushing a buffer write transaction, first check if the buffer data is already written with the desired data

Fixes #

Codecov Report
Attention: Patch coverage is 22.22222% with 28 lines in your changes are missing coverage. Please review.

Project coverage is 81.8%. Comparing base (e682fec) to head (db27328).
Report is 30 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff            @@
##           master     #277     +/-   ##
=========================================
- Coverage    81.9%    81.8%   -0.1%
=========================================
  Files         837      837
  Lines      226539   226557     +18
=========================================
- Hits       185548   185534     -14
- Misses      40991    41023     +32


assign fragment_directory as mentioned in the docs

Fixes https://github.com/hawkowl/towncrier/issues/109

Codecov Report

Merging #134 into master will decrease coverage by 1.17%.
The diff coverage is 33.33%.

@@            Coverage Diff             @@
##           master     #134      +/-   ##
==========================================
- Coverage   93.04%   91.86%   -1.18%
==========================================
  Files          16       15       -1
  Lines         661      627      -34
  Branches       69       66       -3
==========================================
- Hits          615      576      -39
- Misses         28       33       +5
  Partials       18       18

Impacted Files
Coverage Δ

src/towncrier/__init__.py
87.87% <33.33%> (+3.59%)
:arrow_up:

src/towncrier/_settings.py
77.77% <0%> (-5.56%)
:arrow_down:

src/towncrier/test/test_cli.py
95.61% <0%> (-4.39%)
:arrow_down:

src/towncrier/_builder.py
97.87% <0%> (-2.13%)
:arrow_down:

src/towncrier/check.py
94% <0%> (ø)
:arrow_up:

src/towncrier/test/test_check.py
100% <0%> (ø)
:arrow_up:

src/towncrier/test/test_write.py
100% <0%> (ø)
:arrow_up:

src/towncrier/test/test_format.py
100% <0%> (ø)
:arrow_up:

src/towncrier/test/test_builder.py

... and 1 more

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 2cf6dd6...9407ce6. Read the comment docs.


Backup/Restore Issues

As documented in issues many times, If this critical feature doesn't work, the app is dead. Losing access to the app can mean catastrophic loss of login access. The restore/backup features need to be resolved before anyone should use this app.
this is a critical failure and no release with full functionality for backup restore should be pushed.

See if this works or helps you out:
https://github.com/freeotp/freeotp-android/issues/411#issuecomment-2322986024

I've written a bit about what's going on here in case you're interested: https://github.com/freeotp/freeotp-android/issues/283#issuecomment-2381379029. Various issues can occur depending on the version of Android, the version of FreeOTP and other factors.

I'll leave it here in case anybody stumbles across the backup/restore problems with FreeOTP: You can import the "externalBackup.xml" (the serialized java map containing json) in the Stratum Authenticator (https://github.com/stratumauth/app). From there on you can migrate / restore to where ever you like, since you can actually view your TOTP keys / URIs. I really don't get why problems like this don't get addressed by FreeOTP. It cost me multiple hours to find an implementation which can handle this "backup"-"xml".


Python: Azure AI Search api key should not be required.

Motivation and Context
We have a regression that makes the AI Search Setting's API key required.

Description
Make the AI Search setting a non-required attribute. Fixes #6697

Contribution Checklist

[X] The code builds clean without any errors or warnings
[X] The PR follows the SK Contribution Guidelines and the pre-submission formatting script raises no violations
[X] All unit tests pass, and I have added new tests where possible
[X] I didn't break anyone :smile:

Python 3.10 Test Coverage Report • FileStmtsMissCoverMissingTOTAL615873588% report-only-changed-files is enabled. No files were changed during this commit :)
Python 3.10 Unit Test Overview

Tests
Skipped
Failures
Errors
Time

1434
1 :zzz:
0 :x:
0 :fire:
18.682s :stopwatch:


Cannot run

"/usr/bin/MCEdit
Running in fixed mode. Support files are in your Documents folder.
Traceback (most recent call last):
  File "/usr/lib/mcedit/mcedit.py", line 13, in <module>
    import splash
  File "/usr/lib/mcedit/splash.py", line 10, in <module>
    import pygame
ImportError: No module named pygame"

but
community/python-pygame 2.1.1-1 (4.1 MiB 14.4 MiB) (Installed)
    Python game library

OS: Manjaro

I get this on multiple distros of linux. I wish they provided binaries or at least included an already built environment. Not every package is available forever, guys! Just because you still use legacy dependencies doesn't mean everyone should need to install them.

Yeah Python 2.7 support is getting pretty poor. Unfortunately PyGame is about as core a library as it could be and it's not really realistic to re-write it without it. Your best bet is to compile PyGame yourself, which may or may not be realistic. (I handled OSX and Windows packaging when I was active and had to compile it myself for it to work on OSX .app releases) or use a OS release from a similar time to the last release that would have the package.
The bigger issue is really that this isn't under active development and the current developers have moved to Amulet as we felt a rewrite was necessary to continue to support newer versions due to core format changes in Minecraft and as Python 2.7 is obsoleted. I suspect due to that releases for Mac and Linux will eventually stop working without extra work if they haven't already. Classic case of software rot that just happens to affect Linux more severely due to it being an unfriendly environment for programs not under active development.
We had tried to make pre-packaged binaries like we did with OSX, but we had a lot of issues with cross-distro compatibility and had to abandon the idea.


Remove SecurityAutoConfiguration exclusion for generated apps

The Spring Boot 2.1.x ManagementWebSecurityConfigurerAdapter opens the health and info entry points by default.
Since those are sufficient for allowing SCDF server to manage the monitor the SCSt apps, there is no need to disable the entire security by excluding SecurityAutoConfiguration
Affects: spring-cloud-stream-app-maven-plugin

Related to https://github.com/spring-cloud-stream-app-starters/app-starters-release/issues/161

@artembilan we need to check the accessibility of the bindings actuator too

we need to check the accessibility of the bindings actuator too

Do you mean in your generic test-case?
Or do you it is not covered with that new ManagementWebSecurityAutoConfiguration in Spring Boot?
Let's handle it in the issue in core or already in your PR on the matter!


Can responder autoreload after changes files?

As mentioned here https://github.com/kennethreitz/responder/issues/51#issuecomment-430209707, it's not possible to do so programmatically.


core: move interop to a separate package

This makes it able to define interops in packages which do not depend from core
E.g. interops from #777 and #779 can be defined in separate packages.

Last commit with enumerator/iterator interops is for illustrative purposes.

I'm thinking now about dao and Blockchain responsibilities, technically interop context (which is almost an AppExecContext) can work without Blockchain for almost all cases except BlockHeight/CurrentBlockHash (passing topBlock to the context solves it easily) and GetHeaderHash, but even that can be reworked to go through dao. But what's the purpose of Blockchain then?

This is probably right, because everything which is not in top block, have already been pushed to storage and thus available from DAO. The only other thing which could be needed is GetConfig().

Let's postpone this a little, I need to go through interops again and check what's the best solution. We have some hierarchy in Store->DAO->Blockchain where each layer solves some part of the overall problem (Store is a generic KV store, DAO is an object layer around Store and Blockchain is a blockchain where you only change it by adding blocks/headers, but can get a lot of information about its state). At the same time there are some complications around that like IsDoubleSpend or IsDoubleClaim currently in DAO although they're higher level functions, there is caching at Store level and at the same time there is caching at DAO level.
So the question is whether interops should be using Blockchain in some form or DAO. I don't think they should use both as Blockchain in nothing without DAO, although at the moment we have it being used as a singleton with the one and only true DAO inside. Maybe that's not how Blockchain should be used. At the same time it shouldn't ever expose its DAO to the outside.

OK, so interops really are special and can't work with just Blockchain. They change state directly via PutStorageItem/PutContractState/PutAssetState and can also delete some state information. One thing I've also noticed is that our current GetValidators implementation uses dao, but contract probably expects the (filtered) result from Blockchain. That probably suggests that we should avoid passing Blockchain there and just use dao interface plus some additional data  (cache, actually, because it can also be derived from dao) like current top block.

OK, let's proceed with further improvements in some other tasks and merge this one as is (well, almost). It does solve the problem of interops being tied to the core and that's a huge win already.


Android Facebook Sdk

From @AntonioCuevaUrraco on July 29, 2015 10:51
Hello everyone I am trying to get the facebook login for Android working and this is my progress so far
I managed to build the sdk and access it from nativescript.
Also I can open for login and receive the data from facebook.
but it is crashing when the facebook activity reply back with the data.
Here It crash:
mCallbackManager.onActivityResult(requestCode, resultCode, data);

And this is the implementation I did of the interface FacebookCallback
  loginManager.registerCallback(mCallbackManager, new com.facebook.FacebookCallback({

      onSucces: function() {
        console.log("Print this");

      }
      onCancel: function() {
        console.log("Cancel was press");

       }
       onError: function(e) {
       console.log("errore " + e);
   }

      }));

The cancel is working but the onSucces is generating "abstract method not implemented"
And this is the full implementation code
 if (args.android) {

//fb initialization
com.facebook.FacebookSdk.sdkInitialize(application.android.context.getApplicationContext());

//fb objects
var mCallbackManager = com.facebook.CallbackManager.Factory.create();

var loginManager: com.facebook.login.LoginManager = com.facebook.login.LoginManager.getInstance();

//Implementing the callback Interface
 var callback = new com.facebook.FacebookCallback({

       onSucces: function(result) {
         console.log("Print this");

          console.log("Result3 " +result);
       }
       onCancel: function() {
         console.log("Cancel23");

       }
       onError: function(e) {
     console.log("errore " + e);
   }

       });

   var act: android.app.Activity = application.android.startActivity;

   //Overriding Activity onActivityResult method to send it to the callbackManager
    act.onActivityResult = (requestCode: number, resultCode: number, data: android.content.Intent) => {
    mCallbackManager.onActivityResult(requestCode, resultCode, data);
    }
    com.facebook.login.LoginManager.getInstance().logInWithPublishPermissions(act,        java.util.Arrays.asList(["publish_actions"]));
  }

Copied from original issue: NativeScript/NativeScript#510

From @slavchev on July 30, 2015 7:39
Before we investigate the issue can you check if it works when the method is named onSuccess (my guess is that you made a typo onSucces)

From @valentinstoychev on July 30, 2015 16:27
Hey @AntonioCuevaUrraco - this is a great initiative and as @slavchev said - please feel free to ask as any questions on the implementation. If you want to find fellow developers you can ask on the forum or in the G+ community page.
@Nathanaela - are you interested to work on this with @AntonioCuevaUrraco?

From @slavchev on July 30, 2015 11:14
Glad to help :)
The idea for facebook module is great! I have no idea as to whether someone is already working on such module. As a matter of fact our team don't have much experience with open source projects and guiding the community. So, please let us know if you have any suggestions. Maybe you can take a look at this page https://github.com/NativeScript/NativeScript/issues/236 and decide if it works for you and the others.

From @AntonioCuevaUrraco on July 30, 2015 10:52
You are right :-D  it was a typo. Now I get the access token with no problem.
We are thinking to create a nativescript module to provide the facebook login since we have it working for iOS and Android, Is someone already working on that?

@AntonioCuevaUrraco hey for some reason I totally missed the notification on this one -- let me know if you need any more help getting this turned into a plugin...

No problem @NathanaelA we have been quite busy developing and testing our App anyway.
I will create a project for this fb plugin on git and go through the manuals to see how the process can be automatize. I haven't done this kind of thing before so it is time to learn.
There is already some posts in the google community for the manual way. https://groups.google.com/forum/#!searchin/nativescript/facebook/nativescript/kbYW-grxLg8/8CJsZJ6BicAJ

@NathanaelA @enchev
I created the structure for the plugin and added some basic .ts files to log in for Android and iOS.
https://github.com/AntonioCuevaUrraco/nativescript-facebook-login
I added a podfile to set the dependency to the sdk for iOS and is working fine.
For Android in the other hand I don't know how to add the .aar in the plugin.
can I modify something in the plugin so the build.gradle of the project is modify too with the dependency?
//Facebook sdk
compile 'com.facebook.android:facebook-android-sdk:4.6.0'
or can I add the .aar somewhere so it is processed and added to the project automatically?

You can add the aar in the plugin's 'android/libs' folder.
Consider the documentation here.
You see where the MyLibrary.jar is? You can place MyLibrary.aar there too and it should work with v1.3.0 and up. The docs will be updated shortly.

updated the docs, the website will be updated soon.

from 1.5.0 plugins can have an include.gradle file, that can add a dependency to the project like:
dependencies {
    compile 'com.facebook.android:facebook-android-sdk:4.6.0'
}

you can find a proof of concept here


[Question] Energized Spark minus 40% entries within 24 hours?

Hi,
I update The Energized Spark Protection list once a day. I was surprised this very morning to notice a 40% drop in the number of entries:
# Package: Energized Spark Protection
# Description: True Lite Protection Pack.
# Format: hosts
# Version: 18.12.339
# Release: 339
# Entries: 78,352

# Title: Energized Spark Protection
# Description: True Lite Protection Pack.
# Format: hosts
# Version: 18.12.348
# Release: 348
# Entries: 47,124

From 78,352 to 47,124 entries is surprising. Thanks.

OK, thanks @AdroitAdorKhan , in this case I might move to anther Energized list. I'll check them out.
Concerning the update the point is I use several lists that I update once a day, automatically bundled.
I did have in mind that the drop of entries was related to a source, but I thought that source might have itself been the culprit rather than that source being removed.
Thanks.


Small fixes

This makes it a little bit easier to run nlcovidstats.py and process_casus_data.py from the command line. I was still not quite able to get process_casus_data.py working. I'm not sure it's downloading the data like expected. I'll make an issue.

I still wasn't quite able to get process_casus_data.py working from the command line. I am seeing the following at the moment:
Warning: do you really want to download 145huge data files? Ctrl-C to abort, ENTER to continue.
Downloading casus data for 2020-07-02 ...
Wrote /home/wouter/Sources/covid19/data-casus/COVID-19_casus_landelijk_2020-07-02.csv.gz .
Using casus data before 2020-07-03.
Loading casus data for 2 days (using 6 processes)
..
Wrote /home/wouter/Sources/covid19/data/casus_history_summary.csv .
Loaded from cache: /home/wouter/Sources/covid19/cache/casus_summary_cache.pkl
---snippet from summary dataframe df---
Traceback (most recent call last):
  File "./process_casus_data.py", line 438, in <module>
    plots_for_report('fixj2', show=True)
  File "./process_casus_data.py", line 352, in plots_for_report
    df = get_summary_df()
  File "./process_casus_data.py", line 28, in get_summary_df
    print(df)
  File "/home/wouter/Sources/covid19/venv/lib/python3.8/site-packages/pandas/core/frame.py", line 680, in __repr__
    self.to_string(
  File "/home/wouter/Sources/covid19/venv/lib/python3.8/site-packages/pandas/core/frame.py", line 801, in to_string
    formatter = fmt.DataFrameFormatter(
  File "/home/wouter/Sources/covid19/venv/lib/python3.8/site-packages/pandas/io/formats/format.py", line 595, in __init__
    self.max_rows_displayed = min(max_rows or len(self.frame), len(self.frame))
  File "/home/wouter/Sources/covid19/venv/lib/python3.8/site-packages/pandas/core/frame.py", line 1041, in __len__
    return len(self.index)
  File "/home/wouter/Sources/covid19/venv/lib/python3.8/site-packages/pandas/core/generic.py", line 5270, in __getattr__
    return object.__getattribute__(self, name)
  File "pandas/_libs/properties.pyx", line 63, in pandas._libs.properties.AxisProperty.__get__
  File "/home/wouter/Sources/covid19/venv/lib/python3.8/site-packages/pandas/core/generic.py", line 5270, in __getattr__
    return object.__getattribute__(self, name)
AttributeError: 'DataFrame' object has no attribute '_data'

This is even if I change the requirements.txt to match the library versions you are using. Not sure what is missing.

I noticed two things:

Only two csv files were loaded although it announced that it was going to load 145 of them. Something is wrong there, or maybe you hardcoded to only get the first two. If you do that, the data processing won't work. It needs at least a month of data, preferably starting from at least October.  Anyway, to get the full dataset, download the ZIP from https://github.com/mzelst/covid-19/archive/master.zip ; unzip the CSV files in data-rivm/casus-datasets/ into the folder data-casus/ and compress all of them using gzip.

The error message seems to be related to pickling/unpickling (this is done for caching purposes) in some versions of Pandas. https://stackoverflow.com/questions/63559007/unpickling-dictionary-that-holds-pandas-dataframes-throws-attributeerror-dataf If you downgraded/upgraded pandas, try deleting the cache file (in the cache/ folder). Or wait for the cache to expire (1 hour).


Android 64-bit

@Zeus64, When you plan to release the android 64 version ?

it's work already in 64 bit version :) https://play.google.com/store/apps/details?id=club.kiskis.app&hl=en who use alcinoe is already packaged in 64 bit


2PI - QuickView Details | Reviews Tab | Allows users to delete reviews

STR-
Go to QuickView Details | Reviews Tab
Delete an existing review
RESULTS - Review is deleted
EXPECTED RESULTS - 2PI user should never be able to delete/edit someone else's review. They should be able to edit and delete their own.

Tested on Latest.
All users (  Basic users/app owners, admins and org stewards) can delete their own reviews successfully.
Admins can delete other's reviews successfully.
Non admins cannot delete reviews that are from someone else.

2PI Users passed but needs testing with a 1st Party admin

Admins and orginal owners can delete reviews but 2PI and any others that are not original owners can not.


Portals - Market Data

Overview
See this comment: https://github.com/shapeshift/web/issues/6981#issuecomment-2206869446

What about market-data?

Historical market data isn't going to be available, but that's nothing different than e.g how we used to do UNI-V2 opportunities - we absolutely can and should upsert the current price of all https://api.portals.fi/v2/tokens tokens in the market-data slice
References and additional details
https://api.portals.fi/v2/tokens which contains spot price
Acceptance Criteria

Spot price is fetched and upserted for LP tokens JIT with whichever smart pattern we can come up with. There are ~50k assets totals supported by Portals, which we will generate with the generation script in https://github.com/shapeshift/web/issues/7303. We obviously can't afford to run it at runtime. Usefuls patterns could be prefetching on assets scroll with https://tanstack.com/query/v4/docs/framework/react/guides/prefetching, or simply JIT when selecting an asset
If there is already market data for a token (meaning it's either a token that already had market-data from other sources, not Portals, or is a Portals asset with its spot price already fetched), market data is not refetched JIT and business is as usual here

Need By Date
No response
Screenshots/Mockups
No response
Estimated effort
No response

discussion from grooming on monday:
provider vs JIT - JIT much less LOE but not reusable for showing in portfolio / defi positions
@0xApotheosis should have this work done in the custome import token implementation and we can use that for learnings to apply here.

estimates are based on JIT approach, we can improve as we know more

@0xApotheosis working on implementation w custom tokens  that can also be leveraged for this

fyi @gomesalexandre historical data is now available https://api.portals.fi/docs#/Supported/SupportedController_getTokenHistory


Pipenv requirements currentely requires Postgres setup

The psycopg2 package requires having Postgres installed and configured. For some it would be easier to set up and start with Sqlite. There should be a way to all using psycopg2-binary for --dev package install and only require psycopg2 for production.

It looks like this isn't quite an easy fix with pipenv as it does not support installing packages only for production: https://github.com/pypa/pipenv/issues/3167 . I'm still digging around for a way to do this so the setup will work for both Sqlite and Postgres but I may just remove psycopg2 and only have it in the heroku-production branch for releases to heroku.

@stevenabadie it's your call. The build works on my machine right now, so as long as it works, I'm good.

@stevenabadie if you still want to move forward with this, why don't we just use docker containers to match production as much as possible? It'd be pretty easy to setup.
https://www.docker.com/

We can do this with docker in #174. Closing this issue.


Screenshot quality degradation affects visual analysis accuracy

What happened?
When capturing screenshots during browser sessions, Cline is using WebP format with default compression settings, which introduces quality loss. This affects the accuracy of visual analysis in two ways:

False Positives: Compression artifacts are misinterpreted as visual defects, causing Cline to report errors in elements that are actually correct.

False Negatives: Real visual defects are masked by compression artifacts, causing Cline to miss actual issues that should be detected.

The issue is particularly noticeable with:

Fine text (< 12px)
Sharp edges and 1px lines
Gradient transitions
Color accuracy checks

Steps to reproduce

Create a test page with precise visual elements:

<!DOCTYPE html>

Small text for quality testing

Run Cline analysis:

const result = await cline.analyzeVisual('test.html');
console.log(result.issues);

Compare with direct browser screenshot:

Open test.html in Chrome
Take screenshot manually
Notice quality difference in:

1px line (appears blurry in Cline)
Gradient (shows banding in Cline)
Small text (less readable in Cline)

Relevant API REQUEST output
// Current implementation in BrowserSession.ts
let screenshotBase64 = await this.page.screenshot({
    ...options,
    type: "webp", // Uses lossy compression by default
});

// Console output shows compression artifacts:
[Error] Visual analysis failed:
- Element
 appears blurred (actual: sharp)
- Gradient shows banding artifacts
- Text element
 fails clarity check

Additional context

Issue affects all screenshot captures
Reproducible across different browsers and platforms
Impact increases with:

More complex visual elements
Finer details in UI
Color-sensitive components
Text-heavy interfaces

Environment:

Cline Version: 3.0.4
Puppeteer Version: ^23.4.0
Node.js Version: 18.x
OS: Arch Linux

Proposed Solution:
Use PNG as primary format for lossless quality, with high-quality WebP as fallback only when needed. This ensures:

No compression artifacts
Accurate visual analysis
Reliable test results

--
FYI, this is my first contribution to this project.  I asked Cline to help write this, after reviewing only CONTRIBUTING.md.  Then I asked Cline to review CODE_OF_CONDUCT.md, and zero changes were required: Cline writes positively by default.  Thank you so much for this wonderful creation.

On reviewing after posting, I see an error.  The version Cline wrote [guessed at, I suppose?] is incorrect: I am running version 3.0.4.
A fix is forthcoming.

Closing per https://github.com/cline/cline/pull/1011#issuecomment-2561600219

Thank you so much for this wonderful creation.

Thank you for taking the time to investigate and contribute @libertyteeth. I'm sorry I couldn't merge it in the end, but please don't let that stop you from taking a stab at another itch. I ended up learning way more about webp thanks to your issue/PR and it's interesting how much of a difference a slight bump in quality can have in file size.

Thank you so much for this wonderful creation.

Thank you for taking the time to investigate and contribute @libertyteeth. I'm sorry I couldn't merge it in the end, but please don't let that stop you from taking a stab at another itch. I ended up learning way more about webp thanks to your issue/PR and it's interesting how much of a difference a slight bump in quality can have in file size.

Thank you for your kind response.  I was gut punched by a non-blood family relative last night and left the celebration and haven't returned.  This affected my response, which was after I had gotten home.
What do you think of a configuration option?  I am happy to work on it if it will meet your approval.
Thank you again, and Merry Christmas.


gRPC

Hi All,
I am trying to create a gRPC client for the conductor server using .Net Core. But I have a problem with the connection to the server: Grpc.Core.RpcException: Status(StatusCode=Internal, Detail="Error starting gRPC call: The SSL connection could not be established, see inner exception.")
Could you explain how to configure the gRPC server or share a link on the documentation which could explain this process?

@BohdanPr It doesn't seem like Conductor specific issue, and quick search through gRPC dotnet revealed this: https://github.com/grpc/grpc-dotnet/issues/792, which might be of help to you.


RISC-V: Disable some known failing tests

The tests are broken and should be disabled until fixed.
Based on results from https://ci.adoptium.net/job/build-scripts/job/jobs/job/evaluation/job/jobs/job/jdk21u/job/jdk21u-evaluation-linux-riscv64-temurin/112
Relates to https://github.com/adoptium/aqa-tests/issues/4976

@smlambert I reran it with https://ci.adoptium.net/job/Grinder/8537/console. My fork is on luhenry/adoptium-aqa-tests, which is why your run didn't succeed.


Fixed link in compatibility.adoc

Seems linked blog post moved.

Thanks, @munterbusch-ms !

:+1:

👍

Thanks!

https://apisyouwonthate.com/blog/api-versioning-has-no-right-way
works fine.
Thanks!


Not Compatible with Models quantized with updated llama.cpp q4 and q5 quantization.

Not Compatible with Models quantized with updated llama.cpp q4 and q5 quantization released in llama.cpp PR 1405.

@abetlen Any ideas on how to use the new models?

@awinml are you using the latest version? The current version 0.1.50 is pinned to this commit which includes those changes

@abetlen Updating the version to 0.1.50 resolved the issue. Thanks!

when using version 0.1.51 and 0.1.52 the problem still persist :
llama.cpp: loading model from Wizard-Vicuna-13B-q4_1.bin error loading model: unknown (magic, version) combination: 67676a74, 00000003; is this really a GGML file? llama_init_from_file: failed to load model
When I use old models though everything works fine using python, as well as when I run new models normally using llama.cpp.
Am I missing something or is there a bug somewhere?

when using version 0.1.51 and 0.1.52 the problem still persist :
llama.cpp: loading model from Wizard-Vicuna-13B-q4_1.bin error loading model: unknown (magic, version) combination: 67676a74, 00000003; is this really a GGML file? llama_init_from_file: failed to load model
When I use old models though everything works fine using python, as well as when I run new models normally using llama.cpp.
Am I missing something or is there a bug somewhere?

Similarly, same problem working with os.system call to ./main but not through Llama()

There are now three versions of llama model files following rapid development of the quantization code in llama.cpp.
About a week ago it changed to v2 which required python-llama-cpp==0.1.50. 00000003 however looks like a bad version number.
Below is a quick way to verify your model versions.
$ cat ../ggml_file.sh
#!/bin/bash

xxd $1 | awk -v fname=$1 '{printf("magic: 0x%8s, version: 0x%4s, file: %s\n", $3$2, $4, fname);exit}'

$ find . -name "*.bin" -exec ../ggml_file.sh {} \; | sort -n -k 4,4 | egrep "0x0[123]00"
magic: 0x6767666d, version: 0x0100, file: ./alpaca-13B-ggml/ggml-model-q4_0.bin
magic: 0x6767666d, version: 0x0100, file: ./alpaca-30B-ggml/ggml-model-q4_0.bin
magic: 0x6767666d, version: 0x0100, file: ./alpaca-7B-ggml/ggml-model-q4_0.bin
magic: 0x6767746a, version: 0x0100, file: ./alpaca-7b-native-enhanced/ggml-model-q4_0.bin
magic: 0x6767746a, version: 0x0100, file: ./alpaca-7b-native-enhanced/ggml-model-q4_1.bin
magic: 0x6767746a, version: 0x0100, file: ./alpaca-7b-native-enhanced/ggml-model-q4_2.bin
magic: 0x6767746a, version: 0x0100, file: ./alpaca-7b-native-enhanced/ggml-model-q4_3.bin
magic: 0x6767746a, version: 0x0100, file: ./alpaca-7b-native-enhanced/ggml-model-q5_0.bin
magic: 0x6767746a, version: 0x0100, file: ./alpaca-7b-native-enhanced/ggml-model-q5_1.bin
magic: 0x6767746a, version: 0x0100, file: ./alpaca-7b-native-enhanced/ggml-model-q8_0.bin
magic: 0x6767746a, version: 0x0100, file: ./legacy-ggml-vicuna-13b-4bit/ggml-vicuna-13b-4bit-rev1.bin
magic: 0x6767746a, version: 0x0100, file: ./legacy-ggml-vicuna-13b-4bit/ggml-vicuna-13b-4bit.bin
magic: 0x6767746a, version: 0x0100, file: ./vicuna-13B-1.1-GPTQ-4bit-128g-GGML/vicuna-13B-1.1-GPTQ-4bit-128g.GGML.bin
magic: 0x6767746a, version: 0x0100, file: ./vicuna-13B-1.1-GPTQ-4bit-128g-GGML/vicuna-13B-1.1-GPTQ-4bit-32g.GGML.bin
magic: 0x6767746a, version: 0x0200, file: ./GPT4All-13B-snoozy-GGML/GPT4All-13B-snoozy.ggml.q4_0.bin
magic: 0x6767746a, version: 0x0200, file: ./GPT4All-13B-snoozy-GGML/GPT4All-13B-snoozy.ggml.q5_0.bin
magic: 0x6767746a, version: 0x0200, file: ./GPT4All-13B-snoozy-GGML/GPT4All-13B-snoozy.ggml.q5_1.bin
magic: 0x6767746a, version: 0x0200, file: ./GPT4All-13B-snoozy-GGML/GPT4All-13B-snoozy.ggml.q8_0.bin
magic: 0x6767746a, version: 0x0200, file: ./Wizard-Vicuna-13B-Uncensored-GGML/Wizard-Vicuna-13B-Uncensored.ggml.q4_0.bin
magic: 0x6767746a, version: 0x0200, file: ./Wizard-Vicuna-13B-Uncensored-GGML/Wizard-Vicuna-13B-Uncensored.ggml.q5_0.bin
magic: 0x6767746a, version: 0x0200, file: ./Wizard-Vicuna-13B-Uncensored-GGML/Wizard-Vicuna-13B-Uncensored.ggml.q5_1.bin
magic: 0x6767746a, version: 0x0200, file: ./Wizard-Vicuna-13B-Uncensored-GGML/Wizard-Vicuna-13B-Uncensored.ggml.q8_0.bin
magic: 0x6767746a, version: 0x0200, file: ./gpt4-alpaca-lora-30B-4bit-GGML/gpt4-alpaca-lora-30b.ggml.q4_0.bin
magic: 0x6767746a, version: 0x0200, file: ./gpt4-alpaca-lora-30B-4bit-GGML/gpt4-alpaca-lora-30b.ggml.q5_0.bin
magic: 0x6767746a, version: 0x0200, file: ./gpt4-alpaca-lora-30B-4bit-GGML/gpt4-alpaca-lora-30b.ggml.q5_1.bin
magic: 0x6767746a, version: 0x0200, file: ./gpt4-alpaca-lora-30B-4bit-GGML/gpt4-alpaca-lora-30b.ggml.q8_0.bin
magic: 0x6767746a, version: 0x0300, file: ./dromedary-65B-lora-GGML/dromedary-lora-65B.ggmlv3.q4_0.bin
magic: 0x6767746a, version: 0x0300, file: ./dromedary-65B-lora-GGML/dromedary-lora-65B.ggmlv3.q4_1.bin
magic: 0x6767746a, version: 0x0300, file: ./dromedary-65B-lora-GGML/dromedary-lora-65B.ggmlv3.q5_0.bin
magic: 0x6767746a, version: 0x0300, file: ./dromedary-65B-lora-GGML/dromedary-lora-65B.ggmlv3.q5_1.bin

Works with commit 08737ef:
llama_model_load_internal: format     = ggjt v2 (latest)
But not when quantizing with newer versions of ggerganov/llama.cpp. I guess llama-cpp-python is not yet ready to work with version 3?


Errors running app via "run dev" on "skeleton-es2016-webpack" at "1.0.0-beta.1.1.6/"

I have copied skeleton-es2016-webpack into a sub-directory (www-new) of a recently-created repository.
While in the directory www-new/, I followed the instructions in the README.md.
I was unable to successfully load the sample webapp.
Test 1

npm install
npm run dev
Open http://localhost:3000/.

These are the console errors.
Uncaught (in promise) TypeError: _aureliaPal.DOM.injectStyles is not a function
    at Object.configure (webpack:///./~/aurelia-templating-resources/dist/commonjs/aurelia-templating-resources.js?:53:21)
    at eval (webpack:///./~/aurelia-framework/dist/commonjs/aurelia-framework.js?:48:32)

Test 2

npm run build
mkdir www-new-build-test/
cp build/* www-new-build-test
cp index.html www-new-build-test/index.html
Open file:///[...]/www-new-build-test/index.html

These are the console errors.
Uncaught (in promise) TypeError: _aureliaPal.DOM.injectStyles is not a function
    at Object.configure (file:///[...]/www-new-build-test/1.bundle.js:28903:22)
    at file:///[...]/www-new-build-test/1.bundle.js:721:33

Test 3

npm run build
mkdir www-new-dist-test/
cp dist/* www-new-dist-test
Open file:///[...]/www-new-dist-test/index.html

These are the console errors.
Uncaught (in promise) TypeError: y.DOM.injectStyles is not a function
    at Object.configure (file:///[...]/www-new-dist-test/1.bundle.js:28903:22)
    at file:///[...]/www-new-dist-test/1.bundle.js:721:33

The solution was in the same README.md that had the instructions:
See README.md: Getting Started at the "Note: " just before README.md: Bundling:

Note: when using NPM 2.x, you might encounter a run-time error like '[...].DOM.injectStyles is not a function'. To work around this issue, execute the command npm dedupe.

FWIW, I hit this upgrading my Aurelia packages (mostly from 1.0 to 1.1. npm dedupe didn't improve the problem at all, but a more aggressive rm -r node_modules/; npm install cleared it up.


Folder Name of "Encipher | Decipher" need to change

Describe the bug

We can't do git pull
When we do we get an error
Expected behavior

Screenshots (optional)

Additional context (optional )

Assign me this task under GSSOC'23

@MohitGupta121 Kindly assign me under gssoc'23

Due to this, we can't use the "git pull" command.


GDScript Installation fails with Class "CustomTypes" hides a global script class

Describe the bug
Following the instructions on installation from the readme, I downloaded v1.6.7-gdscript.zip and extracted the addons folder to the root of my projects. ./assets/YATI However attempting to enable the plugin is met with:
res://addons/YATI/CustomTypes.gd:24 - Parse Error: Class "CustomTypes" hides a global script class.
  res://addons/YATI/Importer.gd:-1 - Compile Error:
  res://addons/YATI/TiledImport.gd:-1 - Compile Error:
  modules/gdscript/gdscript.cpp:2788 - Failed to load script "res://addons/YATI/TiledImport.gd" with error "Compilation failed". (U

To Reproduce
Steps to reproduce the behavior:

In a new godot project install the YATI Addon

Expected behavior
Plugin to enable correctly
Desktop (please complete the following information):

OS: Windows 10
Version: GDScript 1.6.7
Godot Version 4.2.1

Occasionally I also had this and after some disabling and re-enabling of the plugin the problem disappeared.
Don't know why that happens and unfortunately I have no clearer recipe against it.
Hope you get it sorted.

Looks like preload seems to cause a global namespace issue. I put in a pr that has fixed it in my project. Would love it you take a look.

What happens if you now (after it once worked in the project) change that back to 'preload'?
Does it continue to work or is it starting to fail again?
I'm a little hesitant to change something that works for 99.9% of all users.

After changing it back the error comes back and refuses to load the script again. I totally get the hesitation for it and don't mind if the pr is earmarked or rejected. Just wanted to share the fix that I found.

Ok, if the error occurs again, it really is a nuisance.
I'll test that and eventually include it in a future release with adaptions for 4.3.
Thank you very much for your valuable hints and pr!

Should be now fixed with release 1.6.8 / 2.0.0

Unfortunately it looks like the issue is still there :

I'm using Godot v4.3 stable and updated YATI to v2.0.1.
I tried deactivating/reactivating the plugin, but to no avail.

But the preload option is removed, I've double-checked that.
Really strange that what helped in the past no longer works.
And I still cannot reproduce it.
Is there anything corrupted cached?
Maybe try to remove the .godot/imported folder or even the .godot folder?

I think I found the issue: commit acf3c7fc10379b2feb4a4a80fc9d8a1e9a631123 reintroduced the preload that was fixed in 49b72b02444b3a41dd25da79bb700c1a8a64eb1c.

 You're using the runtime right?
And there I forgot to remove the preload.

Yep, I'm using it to load chunks of the world dynamically (#41) :)
Anyway, it's all solved now, thanks for your help!

Sorry about that!
I'll fix it of course but think it's overkill to put out an extra release about it.


Most likely the start of a 2.0 refactor

This PR introduces a new replace method that can be used to specify a list of keys that should be overwritten entirely, even when performing a mergeMany.
In the following, the value of some_key will be entirely replaced with the incoming data, while all existing keys will use the merge behavior:
<?php

Stillat\Proteus\Support\Facades\ConfigWriter;

ConfigWriter::replace(['some_key']->mergeMany('app', [
   'other_key' => [],
   'some_key' => []
]);

@JohnathonKoster this works perfect for both of my scenarios, SHIP IT!


Whether to support streaming output？

Short answer - No.
from langchain.chat_models import ChatOpenAI
from langchain.schema import (
    HumanMessage,
)

from langchain.callbacks.streaming_stdout import StreamingStdOutCallbackHandler
chat = ChatOpenAI(streaming=True, callbacks=[StreamingStdOutCallbackHandler()], temperature=0)
resp = chat([HumanMessage(content="Write me a song about sparkling water.")])

Supporting streaming is possible, but right now, it does not fit the most common 99% of scenarios for this library. Let me know if you believe otherwise


Auto-upgrade to <IP_ADDRESS>

Base PullRequest
default branch (https://github.com/http4k/http4k-connect/tree/master)
Command results

Details:

add path
/home/runner/work/_actions/technote-space/create-pr-action/v2/node_modules/npm-check-updates/build/src/bin

./upgrade_http4k.sh <IP_ADDRESS>

Changed files

Changed file:

gradle.properties

:octocat: Repo | :memo: Issues | :department_store: Marketplace

Codecov Report

Merging #119 (dce65e4) into master (ddffc10) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #119   +/-   ##
=========================================
  Coverage     62.83%   62.83%
  Complexity      666      666
=========================================
  Files           396      396
  Lines          4251     4251
  Branches        291      291
=========================================
  Hits           2671     2671
  Misses         1411     1411
  Partials        169      169

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more


Joining @atom-ide-community

Hi @lgeiger. Thanks for this great package!
We were wondering if would like to join @atom-ide-community with this package. The community can help to maintain and improve the package. For example, I am planning to add a debugger to ide-python.

Hi @aminya thanks for reaching out.
It's awesome to see that the @atom-ide-community has taken over support of the IDE functionality in Atom, great work!
I haven't had enough time lately to do a proper job at maintaining this package so I'd be really happy to welcome more people. I think @atom-ide-community would be a great new home for ide-python 🎉

From an organisational perspective, can I just transfer ownership of the repo to the organisation or would this break package publishing?

Hi @aminya thanks for reaching out.
It's awesome to see that the @atom-ide-community has taken over support of the IDE functionality in Atom, great work!

I haven't had enough time lately to do a proper job at maintaining this package so I'd be really happy to welcome more people. I think @atom-ide-community would be a great new home for ide-python 🎉

This would be awesome!

From an organisational perspective, can I just transfer ownership of the repo to the organisation or would this break package publishing?

You can transfer the package to the organization. It does not affect publishing. Everyone will continue to get the updates.

Thanks for joining us. 🎉 I am closing this issue.

Great to be here 🚀


programm forgets devices after disconnect

when a device is temporary not available (say a unplugged USB Headset for example) the program sometimes "forgets" that device. What I mean with this that for example the "favorit" status is forgotten and when the device is reconnected it is not longer in the favorite device list and thus is it not possible to select it with a left or right click on the tray icon.

This is an issue with Windows.
It can't tell if the USB is a new device or the same device when it's plugged back in. So it just treats it as a new device everytime.

Dear xenolightning,
First of all thank your for your application. I respect that you are the dev and it is ultimately your decistion. However since you are on github I hope I may illustrate another aspect before you finally decide:
This problem completely brakes the usability for me and potentially for many users. Because my USB bluetooth and HDMI Sound devices are frequently disconnected I always have to open the Preferences to switch to my other devices which makes the programm kind of obsolete.
I would like to propose the following solution:

As I guess you can not read a device ID or something similar from the windows API so you can't identify for sure a certain device? However I think a 95% probability would be sufficient. Maybe you could read just the device name and try to indentify favorite devices by name? If somebody would argue, that there could be two devices with the same name (really?) I would say in this rare case you could still change the name in the windows settings once and be good forever (windows seems to remember/recognise the devices correctly) If this fails you could also try to read the icon id in combination with the name?

If you really don't like the idea – please consider the following option as a workaround or additional feature:
please make an option to "show all available sound devices at right click on tray" (not only favorites)
That would already help a lot since I could choose all devices with only two clicks.
heck I would even make it other way around and name it "show only favorite devices in tray" and have it switched on by default if you prefer

To further improve on this idea  you could also make an option to "hide" certain sound devices in that list (simiar to the favorite status but other way around)
I hope I could contribute a bit to your project. In any case: thank you for your effort and your hard work!

I've looked at another way to identify devices in the past, but it's all ultimately led back to using the Id. There's no full proof way of distinguishing between different devices apart from the Id string.
It is REALLY stupid, and don't get me wrong I don't like the way Windows does it either. There may be a way to get the device serial number for some devices, but if others don't have a serial number then it's not a reliable way either.
In short there's no 100% fool-proof way of doing this.
The option of hiding some devices is a much more reasonable solution, and the behaviour is somewhat predictable. Although it suffers from the same issue reversed. If you reconnect a "hidden" device it will appear again.
You can un-favourite devices, and all devices will show in the right click menu. Not ideal but is probably more useful than opening the application for every "new device".

Hi there!
thanks for the quick reply. I have no idea how many devices have this serial number but I suppose even if it works only in some cases it would help. But to be honest I can't really judge this with my limited programming knowledge. I trust you you thought about this a lot.
I'm glad that you liked the idea with hiding and I see the same problem as you mentioned – However probably still worth the effort.
In any case I can't reproduce the feature that you are describing: Are you talking about version 2 now?
If I unfav all devices I have no devices left in the tray menu.

It's likely that the "old" devices you favourited, are still in the settings.
These are the ones that have been connected, marked as favourite, then disconnected.
They still remain favourited by the application, even through they will never exist again.
Open up the .json settings file and clear the line "FavouriteDevices".
You can delete the entire line of make the value empty:
"FavouriteDevices" : "",

Thanks alot! That worked for me!
To make the user experience more consistent you may consider to introduce the "show only favorite devices in tray" option.
That would also alow to cycle through favorites with left click but see all devices with right click.
However for me the biggest pain-point is solved now – So I want to thank you for your effort so far! =)

Glad it's working for you.
I'm hesitant to introduce more new features into an obsolete version of the application. Supporting the old version is already taking up time which could be used for developing v2.
I'll look at the feasibility of it for v2

allright, then I wish you much success with the v2!
I hope I could help a bit.
Kind regards!


Add performance workaround to readme

The current nodejs-express stack can take a long time to build in some envs (cp4apps). adding some doc for possible workarounds.

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

LGTM!

How do I merge/ Still says I need a approving review.

cc @neeraj-laad


use suse images for ceph_config_helper under nova

tested and working

How can I test this?

curious -- is this a new pod in Rocky?

I don't think so.

I don't know what this does, so I don't know how to test it, therefore I can't vote.

How can I test this?

Mainly you clean the whole deployment and redeploy with this, and check the output of the containers. They must have the same output (i.e. do the same actions) as the default ones.
Crude, but it works.

curious -- is this a new pod in Rocky?

Nope, its a container part of the nova chart which creates the ceph keyring as a secret inside k8s, and makes sure the user, keys, pools and so on are created for the storage backend (rdb in our case)


this is the page that Azure portal sent to when I want to create a new directory. But this doesn't tell me how to create a directory... it assumes I have one and tells me how to create a tenant. The link/help in Azure dashboard needs to point to a different page

this is the page that Azure portal sent to when I want to create a new directory. But this doesn't tell me how to create a directory... it assumes I have one and tells me how to create a tenant. The link/help in Azure dashboard needs to point to a different page

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 588fc4d6-0c4d-297d-cfe1-8562728fdc4d
Version Independent ID: cf117c91-90fa-036b-9763-a3c16b398a33
Content: Tutorial - Create an Azure Active Directory B2C tenant
Content Source: articles/active-directory-b2c/tutorial-create-tenant.md
Service: active-directory
Sub-service: b2c
GitHub Login: @kengaderdus
Microsoft Alias: kengaderdus

@gary-newsham-class-com-au Thanks for your feedback! We will investigate and update as appropriate.

@gary-newsham-class-com-au I understand you are trying to create new B2C directory and document showing to create AD B2C tenant. Directory and Tenant can be used interchangeably for each other. Azure AD B2C is different from Azure AD. So, when you create Azure AD B2C, it creates another tenant and can be used for AD B2C features.


Combine thread launches into single launch per tree for gpu_hist

This PR contains major changes in the design of the gpu_hist algorithm. Previously we repeatedly launched groups of omp threads with one thread per GPU to execute some unit of work on the GPU. During a single tree construction there would be hundreds of thread launches. This can cause stalls as shown here:

This PR now launches one thread per GPU and this thread is used to construct the entire tree, only exiting when tree construction is finished. Each device shard still needs to communicate with other shards, but this is achieved via NCCL.
So we now no longer need to create and destroy many threads per iteration (or rely on the omp implementation to manage the thread pool efficiently) and we now avoid any unnecessary CPU thread synchronisation.
This PR also fixes #4332
Potential issues to look out for:

Each device shard redundantly builds its own tree. If these trees were to somehow get out of sync, the algorithm would fail. Given that the histograms have been synced, I expect these to be identical. This potential issue also applies to the distributed GPU version even before this PR.
Correct use of NCCL. I believe we have had some issues with deadlocks when using NCCL from multiple threads before. I have never experienced this myself.

@canonizer @trivialfis can you please review.

Am still unsatisfied with the column sampling design, will try to come up with something better with tests in the next few days.

@trivialfis @canonizer ready for a second review.

Seems the added tests paid off.  Will review once tests passed.

@trivialfis @canonizer I had this working and then it suddenly stopped working - after two days I finally realised the cmake refactor had disabled openmp in all cuda code. The new cmake native support does not automatically propagate host compiler flags to nvcc via -Xcompiler, contrary to the old FindCuda.cmake. Just something to be aware of in future.

@RAMitchell Any update?  If you still have pending work on this PR then I can extract the CMake fix out.

Codecov Report

Merging #4343 into master will increase coverage by 0.29%.
The diff coverage is 95.83%.

@@            Coverage Diff             @@
##           master    #4343      +/-   ##
==========================================
+ Coverage   68.04%   68.33%   +0.29%
==========================================
  Files         132      132
  Lines       12370    12392      +22
==========================================
+ Hits         8417     8468      +51
+ Misses       3953     3924      -29

Impacted Files
Coverage Δ

include/xgboost/tree_model.h
93.75% <ø> (ø)
:arrow_up:

src/common/random.h
100% <100%> (ø)
:arrow_up:

tests/cpp/common/test_random.cc
97.95% <95.45%> (-2.05%)
:arrow_down:

src/tree/updater_colmaker.cc
39.64% <0%> (-0.12%)
:arrow_down:

src/objective/multiclass_obj.cu
93.68% <0%> (+1.05%)
:arrow_up:

python-package/xgboost/core.py
83.6% <0%> (+3.8%)
:arrow_up:

python-package/xgboost/compat.py
89.09% <0%> (+5.45%)
:arrow_up:

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 503cc42...4213ddd. Read the comment docs.


[WFCORE-2233] extend tests for ProcessStateListener

tests for more transitions (reload-required, ....)
test for execution timetout
test  for listener that raises exception

https://issues.jboss.org/browse/WFCORE-2233

@ehsavoie fyi

@ehsavoie please approve

@ehsavoie ok now?

:+1:


Clarify and harmonize the interfaces of the wrapper/adapter classes

Currently, the relationships between and intended uses of the class in fv3net/regression/sklearn/adapters.py and fv3net/regression/wrappers.py are not as clear as possible. See this dicussion: https://github.com/VulcanClimateModeling/fv3net/pull/388#discussion_r439070696.
This could probably be improved by

using an abstract base class for each type of "model" clarifying its expected interface. We have at least three kinds of "Model":

scikit-learn models
models which take stacked xarrays
models which take unstacked xarrays.
(planned) models which take tuples/named-tuples of stacked numpy arrays

perhaps better docstrings/typehints.
choosing one name: either "wrapper" or "adapter".

this predates fv3fit. out of date.


Stage 2 - Support Software / Tools dynamically loads a list of GitHub repos under thetensor-space.

Software/Tools.  This link should load a list of the GitHub repos that are on "TheTensor-Space" Git organization.  Maybe this can be automatically updateing, so if we add or merge repos it shows up.  It would be nice to have a blurb of each, e.g. if it stripped off the first few lines from the readme.

@algeboy I have the base functionality down for this issue. Below is a screenshot of it working:

What data do you want displayed for each repository? Right now, we're displaying the title (which links to the repository) and the description of the repository. We can pull data like forks, stars, description, README.md, etc. as described in the GitHub API.
I was thinking we'd use the "card" from the articles page to display these instead of the way I have them now.

I like the idea of the cards.  We can pull up a snippet of the readme.  These will include a simple starement of the content and maybe a graphic or a list of authors.

Alright, great. I'll add snippets of the README.md, title, a link to the repo, and authors, then I'll make a new comment with my progress.

@algeboy it is done. Below is a screenshot of the software / tools page. It lists all the repositories with authors, 200 characters of the README.md, title, and links to the repositories.

I had an issue where some of the repositories had a file called "README" instead of "README.md", so my scripts had trouble getting all the README files. When I was unable to get the README, I used the repository description instead.
If you rename all your "README" files to "README.md for each repository, the issue will be fixed.
From what you see here, are there any other changes I should make?

@Alex-Cannon great


LuckPerms in the GUI

Recently I learned that in the plugin Ultra Permission there is a setting in the GUI. I would very much like to see the same in LuckPems. I think it's cool!
Who thinks anything about this idea?

Created the GUI of LuckPerms using the API
https://www.spigotmc.org/resources/luckperms-in-gui.53460/


Before you begin: Android Basics in Compose

URL of codelab
In which task and step of the codelab can this issue be found?
Describe the problem
Steps to reproduce?

Go to...
Click on...
See error...

Versions
Android Studio version:
API version of the emulator:
Additional information
Include screenshots if they would be useful in clarifying the problem.

The issue is closed as no details provided.


Best way to handle v3 beta breaking changes?

There are some awesome changes already in v3 beta, so I'd like to use it, but as I see it gets breaking changes. I understand it is a beta, but how can I use it, so new beaking changes won't give an error or result an unexpected behaviour.

Although the branch is called "beta", v3 is stable as of now and pretty much done feature wise. With that being said, I can't guarantee that there won't be any new breaking changes until the official release.
If you decide to use a release candidate, then I'd highly recommend to read the changelog before updating to a newer version.

Will do, and you are doing an awesome job! 👍


Linux/gaster: Permission denied

./sshrd.sh: 176: Linux/gaster: Permission denied
[-] An error occurred
How can I solve this error? I have already tried several solutions and I cannot correct it

Have you tried running this as root?

Try to: chmod +x Linux/* This command will allow permissions for the all files in the directory


[Typst Universe] Add thumbnails to packages

Description
Templates on the Typst Universe have thumbnails, which greatly help with distinguishing between them and getting a notion of what they do and how they look at a glance. I think it would be helpful for packages to have thumbnails too; currently they all have the same crate (

) as their thumbnail.
Ideas for guidelines:

Thumbnails should be clear even in small sizes.
They should depict a logo or a representative cropped shot that demonstrates concisely what the package does, maximising the relevant information to clutter ratio.
Care should be taken not to use shocking colours and patterns: draw attention to your package by providing good functionality and documentation, not by having a flashy thumbnail.

(Issue copied from the Forum)

I'll just post what I have said in our internal chat. I think that your guidelines are good, but designs are particularly hard to get right.

Yeah, I see your point (this is why I formulated the above guidelines, to counter shitty designs…). All submissions to the Typst Universe are reviewed before they are accepted or rejected. Thumbnails for packages (or templates for this matter) are not different to any other aspect of a submission, be it the code itself, the title, etc.


When accessed from laptop/desktop, I get location of internet supplier

In itself this is understandable. but maybe the ability then to go directly to a location would help. Probably a huge feature in itself...
Wonderful initiative BTW. Being able to access the Whatsapp Group from the map / add it (for Whatsapp Admins of points) will be a huge help.

For now even a button to "change address" which will do nothing but refresh the page, would already be a workaround.

Resolved - there's a button to change the address :)


Implementing Vigenere Cipher in Go

💥 Proposal
Implementing Vigenere Cipher in Go.
Have you read the Contributing Guidelines on Pull Requests?
Yes

/assign


[BUG] toomanysnapshots UI message displays incorrect snapshot count

Describe the bug
When I test https://github.com/longhorn/longhorn/issues/6560 . I found a minor issue where I created only 100 snapshots, but the UI displays the message: "Snapshots count is 101, over the warning threshold of 100."
After discussing with Andy, we need to check the backend to determine why the snapshot number is reported as one extra.
To Reproduce

Create 100 snapshot
See toomanysnapshots UI message

Expected behavior
The snapshot count should match the number of snapshots created.
Support bundle for troubleshooting
supportbundle_c2c056ed-e625-4da1-bf61-336f4ecb746e_2024-05-30T04-01-30Z.zip
Environment

Longhorn version: master-head
Impacted volume (PV): pvc-9c781422-5821-4c5d-99e8-4ecd1f4cd5c1
Installation method (e.g. Rancher Catalog App/Helm/Kubectl): Kubectl
Kubernetes distro (e.g. RKE/K3s/EKS/OpenShift) and version: v1.28.9+k3s1

Number of control plane nodes in the cluster: 1
Number of worker nodes in the cluster: 3

Node config

OS type and version:
Kernel version:
CPU per node:
Memory per node:
Disk type (e.g. SSD/NVMe/HDD):
Network bandwidth between the nodes (Gbps):

Underlying Infrastructure (e.g. on AWS/GCE, EKS/GKE, VMWare/KVM, Baremetal): AWS
Number of Longhorn volumes in the cluster: 1

Additional context
https://github.com/longhorn/longhorn/issues/6560
cc @a110605 @longhorn/dev

The line that generates the condition is here:
https://github.com/longhorn/longhorn-manager/blob/7296f4603847bcdbb231b86973ad191c50b15e20/controller/volume_controller.go#L1720
Looks like we just count the number of snapshots in engine.Status.Snapshots, but that includes volume-head. So you created 100 snapshots, but there are 101 by the reckoning of this code (100 + volume-head). This is probably pretty quick to fix up, but we need to confirm the context:

For this purpose, should volume-head be considered a snapshot? Probably not.
Is there any other place we use this calculation?

The replicas do a similar calculation when checking for adherence to snapshot-max-count. They ignore volume-head. We should probably do the same here. (It's only a warning anyway, so really, we just need to display whatever number seems most natural.)
https://github.com/longhorn/longhorn-engine/blob/15c1e891387ba650b4a8b5a6398c7426e8d7ebff/pkg/replica/replica.go#L1407-L1425

Verified on master-head 20240617

longhorn master-head https://github.com/longhorn/longhorn/commit/9bdd9ccc191df987e51946acad9eac0327e4f414
longhorn-manager master-head https://github.com/longhorn/longhorn-manager/commit/1cda0e761f01f8a933f77474a30df22796d25342

The test steps
https://github.com/longhorn/longhorn/issues/8668#issuecomment-2150256851
Result Passed

Manual test passed
Regression test passed
https://ci.longhorn.io/job/public/job/master/job/sles/job/amd64/job/longhorn-tests-sles-amd64/946/testReport/tests/test_basic/test_settings/


React18 compatibility

Hello there,
I was just wondering if the Easy-email editor is compatible with React18 or is it only designed to work with React17? If it is not yet compatible with React18, are there any plans to migrate it in the future? Thank you so much!

It appears there is a conflict when trying to install it while also using React 18

React 18 can be used directly without compatibility issues.

That is not true, even copy-pasting the example from the read me file with react 18 doesn't work I got
Type '{ children: Element; compact: boolean; showSourceCode: true; }' is not assignable to type 'IntrinsicAttributes & ExtensionProps'.
  Property 'children' does not exist on type 'IntrinsicAttributes & ExtensionProps'

quick steps to reproduce

run yarn create vite choose react with typescript
follow the docs of easy-email and copy paste the example code in the docs

It just affects type hints because react-18 React.FC removes children props.
Maybe it's time to upgrade to react-18.

In version 4.13.0, we have updated to react-18,  please check @pushchris @Nilegfx @ZiedChekir @ghyghoo8

Seems like it supports React 18. I used React 17.2.0
where I got dependency tree error since the easy-email-core, easy-email-editor and easy-email-extension are dependent on React 18.
So, I added following to package.json
  "overrides": {     "easy-email-core": {       "react": "^17.0.2",       "react-dom": "^17.0.2"     },     "easy-email-editor": {       "react": "^17.0.2",       "react-dom": "^17.0.2"     },     "easy-email-extensions": {       "react": "^17.0.2",       "react-dom": "^17.0.2"     }   },

I confirm it is working smoothly with react version 18. Thank you for all your effort.


metals: 0.11.2 -> 0.11.4

Description of changes
Upgrade metals to 0.11.4. Note that metals is now using scala 2.13 so this was updated too.
Drop jdk as a metals dependency (Same idea as #171074 and #171067, cc @dtzWill)
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

Mostly LGTM.  The PATH bits makes me think there was some utility or need for jdk vs jre, but I don't know.  If we aren't sure I'm okay either way.  I have only minimally used metals so I don't know it's functionality well enough to say-- it does look fairly comprehensive so seems plausible.

TBH I don't remember why I put the PATH bit initially :sweat_smile:. It might very well have just been a copy paste from another derivation based on coursier..

LGTM, I'm rigged it up to my editor and simple things I tried seem good!

Thanks! :+1:


Add test for creating amendment without year

closes #80

@mico this test isn't correct. As previously mentioned in the other ticket, "ISO 123/Amd 1" cannot exist. The base document must have a year.
i.e. "ISO 123:1999/Amd 1" is okay, but not "ISO 123/Amd 1".

@mico can you please help rebase, and can we also add a test that Amendment/Corr requires a year otherwise an error will be raised?


Please publish official documents which explain how we can test Dynamics 365 for Financial and operations with JMeter.

[Enter feedback here]
If Performance SDK will be deprecated and Microsoft suggests JMeter, please publish official documents which explain how we can test Dynamics 365 for Financial and operations with JMeter.
https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/perf-test/perfsdk-multi-user-testing#:~:text=Visual Studio 2019 is the last version of Visual Studio that includes web performance and load testing features and will be deprecated in the future. We suggest using Apache JMeter for performance testing. For more information%2C see JMeter.
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: f0b04519-4802-eaaa-c5ed-b13e8979d36d
Version Independent ID: a4ebe802-e7fd-fd99-00a1-aa0ebf8fcb48
Content: Run multi-user testing by using the Performance SDK - Finance & Operations | Dynamics 365
Content Source: articles/fin-ops-core/dev-itpro/perf-test/perfsdk-multi-user-testing.md
Service: dynamics-365-cross-app
GitHub Login: @kennysaelen
Microsoft Alias: kesaelen

Hi @yujiim, apologies for the delay.
There is currently a good 4-part blog series on Dynamics 365 finance and operations apps performance testing with JMeter.
You can review the blogs for more information:
Part 1 - Dynamics 365 finance and operations apps performance testing with JMeter - Introduction
Part 2 - Dynamics 365 finance and operations apps performance testing with JMeter - Execution
Part 3 – Dynamics 365 finance and operations apps performance testing with JMeter - Result Analysis
Part 4 – Dynamics 365 finance and operations apps performance testing with JMeter - Tips and Troubleshooting
Within the Dynamics 365 guidance docs, you can find information on Set up and run load tests for your Dynamics 365 implementation projects. A few articles in the testing section require use of JMeter for different scenarios.
We'll look into adding more links or information to the Dynamics 365 finance and operations documentation to cover JMeter use.
Thanks very much for your suggestion.


[TC-533] ssl_keys - tenancy checks

Adding tenancy checks to the DS ssl_keys API.
Still with limited testing

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-trafficcontrol-PR-trafficops-test/52/

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-trafficcontrol-traffic_ops-test-PR/54/

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-trafficcontrol-PR/92/


Implement Discord Bot

Public Discord Bot "BocaChicaBot" registered for this.
Maybe use: https://github.com/bwmarrin/discordgo
Not a typical Discord Bot... would just post messages exactly like the Twitter version does (no websocket api use to listen for commands, just http api use).

closed with #23

closed with #23


scripts: deployer of script contract is not msg.sender

Component
Forge
Have you ensured that all of these are up to date?

[X] Foundry
[X] Foundryup

What version of Foundry are you on?
forge 0.2.0 (34d279a 2022-12-08T07:48:46.429075528Z)
What command(s) is the bug in?
forge script
Operating System
Linux
Describe the bug
The deployer of the Script contract is not msg.sender which means a user that uses msg.sender in the constructor will cause unexpected results. This bit me as I spent an hour trying to predict the Create2 address of my deployed contract (so I could store it in the script storage and check if it exists before I deploy).
I would suggest that the deployer of the script contract should be influenced by the --sender flag unless doing so is infeasible/would break other workflows?

I would suggest that the deployer of the script contract should be influenced by the --sender flag unless doing so is infeasible/would break other workflows?

That would be rad, been struggling with this for months, I can't test scripts that deploy contracts who implement stuff like Ownable which uses msg.sender in the constructor. And so I thought, well, what if I try to prank before calling the run() function on the deployed script contract? But then I get FAIL. Reason: You have an active prank. Broadcasting and pranks are not compatible. Disable one or the other, which makes me think that the same problem would come up if --sender were to be used?

EOAs can't directly use CREATE2, although they can call a contract that does a CREATE2. When a CREATE2 is in a forge script, the transaction is actually a call to this create2 deployer contract.
If one want to precompute the address of a new contract, this is the sender that must be used. Btw, there is a cheatcode for this vm.computeCreate2Address(salt, initCodeHash).
On a side note, I think that this behaviour is a bit dangerous because it's unclear what happens under the hook. I find that using a cheatcode would be safer (like vm.create2WithStandardDeployer).


[T4A6][W09-B2] Chan Jing Hui Benedict

Added UtilsTest class

Some comments added. Please close the PR after reading comments.


biometrics dialog should be using material 3

Since the ListPreference which displays the dialog relies on androidx's alert dialog, there are three options.

wait for support to be made (unlikely it seems)
theme the dialog to look like material 3
recreate list preference using materialdialogbuilder (what I did for my custom time picker dialog)

Something to think about; even some google apps don't use material 3 for their dialogs in settings.


Handle Partial Imports

This plugin doesn't seem to handle partial import paths. Meaning paths that point to a folder not a specific file. Native browser import-maps do handle this.
Example that is not working:
Build script:
importMap.load({
  imports: {
    'lib/': '../../../lib/',
  },
});

JS source:
import { RenderPass } from 'lib/fx/RenderPass.js';

Sorry for a bit late reply but could you try the 3.0.0-next.1 version? That one should be fully spec compliant but would love some live testing of it  before I release it.


feat(RELEASE-1283): process-file-updates resources

new pipeline and task for internal process-file-updates
cloned from https://github.com/hacbs-release/app-interface-deployments/blob/main/internal-services/catalog/file-updates-pipeline.yaml and https://github.com/hacbs-release/app-interface-deployments/blob/main/internal-services/catalog/file-updates-process-file-updates-task.yaml with additional seeding feature and added tests

I doubt this affects e2e tests since it is a new pipeline. force merging

Why was this merged without removing the duplicate resources in app-interface-deployments repo?

Why was this merged without removing the duplicate resources in app-interface-deployments repo?

I asked a similar question in the Jira which is still open, maybe let's follow up there? https://issues.redhat.com/browse/RELEASE-1283?focusedId=26092699&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-26092699


Adding few new python algorithms

Description

Added few new algorithms in python folder

Just as a remainder, bot will close this pull request if you don't respond to the review within 2 days from now.

Closed due no response to the review.


Assembly loader on computation expressions

Codecov Report

Merging #493 (3610abb) into master (41e18d7) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head 3610abb differs from pull request most recent head eeb53d8. Consider uploading reports for the commit eeb53d8 to get more accurate results

@@      Coverage Diff      @@
##   master   #493   +/-   ##
=============================
=============================

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 41e18d7...eeb53d8. Read the comment docs.


Does android have Signal R Android client library with sample

I like to have android version for SignalR

I've trying to implement a chat client based on the project from: https://github.com/aspnet/Docs/tree/master/aspnetcore/signalr/dotnet-client/sample
I managed to create a Windows forms client that connects to the chat with success; the sample also works perfectly on the browser clients, etc. All clients seem to work flawlessly.
My problem is the android client; I cannot make it to work. Whenever I try to connect to the hub I get the error "There were no compatible transports on the server.".
I have websockets installed on the server.
I've tried the url: http://mydomain.com/signalr
I if try with http://mydomain.com I get a 404 (not found).
My great doubt is: is this new java client compatible with signalr applications built using libraries like
Microsoft.AspNet.SignalR.Core
Microsoft.AspNet.SignalR.SqlServer
Microsoft.AspNet.SignalR.SystemWeb
What am I missing?
Thanks.

Can you verify that websockets are being used by the other clients? Because the 1.0.0 version of the Java client only supports Websockets you'll get that There were no compatible transports on the server.  if the server doesn't support Websockets. One common issue is that it's common for cloud providers like app service to not have websockets on by default. The other clients handle this silently by falling back to Server Sent events or LongPolling.

try with http://mydomain.com I get a 404 (not found).

You have to pass in the Hub route that you specify in your MapHub function in your Startup.cs.


Multiple builderrors after updating version 3.11.0 to 3.12.0

Thanks for stopping by to ask us a question! Please make sure to include:

What you're trying to do
I was trying to install the latest package version : 3.12.0.  And run  npm tsc
What I have tried
I tried to delete the node_modules folder and reinstall my dependencies, but that didn't work

This is the build error :
node_modules/@google-cloud/common/build/src/service.d.ts:29:18 - error TS2430: Interface 'ServiceOptions' incorrectly extends interface 'GoogleAuthOptions<JSONClient>'.
  Types of property 'authClient' are incompatible.
    Type 'GoogleAuth<JSONClient>' is not assignable to type 'JSONClient'.

29 export interface ServiceOptions extends GoogleAuthOptions {
                    ~~~~~~~~~~~~~~

node_modules/@google-cloud/common/build/src/util.d.ts:42:18 - error TS2430: Interface 'MakeAuthenticatedRequestFactoryConfig' incorrectly extends interface 'GoogleAuthOptions<JSONClient>'.
  Types of property 'authClient' are incompatible.
    Type 'GoogleAuth<JSONClient>' is not assignable to type 'JSONClient'.
      Type 'GoogleAuth<JSONClient>' is missing the following properties from type 'JWT': createScoped, getRequestMetadataAsync, fetchIdToken, hasUserScopes, and 53 more.

42 export interface MakeAuthenticatedRequestFactoryConfig extends GoogleAuthOptions {

@Wizzel1 if you delete your package-lock.json and node_modules, I believe a fresh install of the library should work for you. Sorry for the inconvenience.
Please let us know if you continue running into any issues.


[FEATURE REQUEST]: Do not allow special characters in usernames

Describe the feature you'd like to get added
People are registring with usernames that have, for example, spaces in them, which might not be very ideal. I haven't dug into very detail what and how username validation should be handled, so you might have to do some research.
Additional context
However, those users which have already registered, should be able to keep their usernames.

for example, spaces in them

I can check for special characters such as @#[[^$µ%..., not sure if spaces are worth?

In my opinion, atleast spaces shouldn't be allowed in usernames

It's more complex than that. You should take into account the possibilities of cyrillic characters, emojis etc. Ideally username wouldn't start / end with . _ or - whereas it should be allowed as a separator character e.g. first.last, first_last (not _first.last-).

True, the "fix" I implemented was just a simple fix for now. There might be a package that I can use for it, but I'll look into that

I might've found a package that I can use. Tho, it would remove the special characters rather than check for special characters. I have a few ideas to still show them an error message if they have special characters

I'll keep this open for now, but this has been partially fixed in 1.4.8


Dockerfile for creating the EFI image

This is my first attempt to add a Dockerfile and docker-compose.yml
The Dockerfile is not perfect yet and I am not sure if this is the right way with regards to when to build and which directorys to include at docker build time vs docker runtime.
However if you run:
git clone -b feature-docker git@github.com:t-oster/zfsbootmenu.git
cd zfsbootmenu
docker-compose up

you end up with a fresh vmlinuz.EFI in your ./out directory.
You can then change the sourcecode at your will and rerun
sudo rm -rf out #we need to delete the directory because it was created as root
docker-compose up

in order to regenerate the image.

Thinking about this a bit more, there is a more generic way to approach the build. I think it would be good to make the built image as reusable as possible, so let's not copy the local clone or create a new clone of the upstream repo at build time. Instead, we'll just make a basic Void image with all of the pieces necessary to do the build.
The build can be handled by a zbm-build.sh script which will check /zbm to make sure it looks like it has the components we need for a build. If so, it will happily run the build as normal. If /zbm is empty, it will instead install git and then clone the upstream repo. This means the image is totally usable without requiring a local repo, but you can bind-mount the local repo to /zbm and that will be used instead.
What do you think about the script in the latest commit?

Hi, this looks good to me, because I can still build the current directory with just docker-compose up and we don't add/clone the source twice. Very elegant.
If you want you can squash and merge it or do you need anything from me?

Hi, I squashed the commits, but so your messages/name vanished, so I added a Co-Authored line. However if you prefer three commits I can also revert that, whatever you like better.

I made a few more fixes and pushed 416696773a91429e51e6d0db4fcdb23f37b89a8c as the final version. Specifically:

A README provides usage information
The build script now looks for hostid and zpool.cache in the contrib/docker directory and will populate these files in the container so they are installed in the ZBM images

Thanks for your contributions. This will be very helpful to our release process!

You're welcome. thanks for reviewing and merging so quickly and again for this great tool, which makes me feel safe again when running zpool upgrade on my server.


Remove logError parameter

Q
A

Fixed Issues?
fix https://github.com/redux-saga/redux-saga/issues/1621

Patch: Bug Fix?

Major: Breaking Change?
Yes

Minor: New Feature?

Tests Added + Pass?
Yes

Any Dependency Changes?

1 don't ignore error during cancellation, allow it to bubble
2 remove logError parameter

Let me think aloud the current behavior of exception during cancellation as far as I understood. In the following code, the parent is going to cancel the child, and child would throw an exception during the cancellation. The behavior is that we will re-throw the exception in already-cancelled tasks, so exception will bubble to parent. When parent catches the exception, it will run ...
https://github.com/redux-saga/redux-saga/blob/309d6be7507a22e2443e7843e61ef8555ea25eba/packages/core/src/internal/proc.js#L269-L270
... so the parent will be aborted with the bubbled exception.
function* parent() {
  // ... other code ...
  yield cancel(child) // child would throw during cancellation
}

My concern is that whether it is the desired behavior of cancellation. Because cancelling a task means that we don't care that child anymore, exception from a cancelled task should NOT abort our parent task. However, if we want to have env.onError called with the exception, we must accept this behavior first. 😕

logic that could throw in during cancellation controls the resource management, so we can leave a system in unpredictable state. basically there are 2 options:

swallow an error and probably log it. using onError seems to be a bit awkward, as end user needs to distinguish between  error bubbling to the root and other 'not critical' errors.
re-throw an error. breaking changes, but forces users to have safe finally block.

but forces users to have safe finally block.

I like this idea. By the way, if we adopt the re-throw approach, maybe we should warn users that an exception during cancellation occurs

I'm on vacation for next 3 weeks, so feel free to make any changes required for v1 release

Overall, I like this PR, it makes thing easier.  @Andarist what do you think?  If we like it, I will do a more thorough review.


Simplify FuncMemory read and write interfaces

Now we have the memcpy interfaces to FuncMemory, and we may use them
to simplify Uint/Int accessors to the memory.

Does this really simplify the code? We get rid of template specialization, instead, we need separate functions for IO with masks.
Unit-tests for memcpy_host_to_guest relied on read for checks. I'll fix it.

We get rid of template specialization, instead, we need separate functions for IO with masks.

Yes, and what is bad about separate functions?
My motivation is to make memcpy virtual in a next step, so we can support mappings other than existing FuncMemory (w/ complicated IO connections etc.)


Fix flaky tests: be less specific about the exact message of PVC missing

We seem to get the "didn't find PVC" message now sometimes, instead
of "didn't find PVC associated with DataVolume". Ignore both.
What this PR does / why we need it:
Seen as a flaky test here. We briefly get a warning for the VMI, which is resolved once the import is complete.
The change in message is most likely introduced in #6171 although I haven't dug much into it.
Release note:

NONE

/retest

/retest


incorrect warning for import

Issue Type: Bug
# xFolder/file1

def a():
    pass

# xFolder/file2

from file1 import *  # suggests xFolder.file1
a()

file next in folder not recognised as source for import. Addressing with full name including foldername suggested, but does not work just filename works (shown as warning: unresolved import, undefined variable)
Extension version: 2019.4.11987
VS Code version: Code 1.33.1 (51b0b28134d51361cf996d2f0a1c698247aeabd8, 2019-04-11T08:27:14.102Z)
OS version: Windows_NT x64 10.0.16299

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-7820HQ CPU @ 2.90GHz (8 x 2904)

GPU Status
2d_canvas: enabledchecker_imaging: disabled_offflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwarerasterization: enabledsurface_synchronization: enabled_onvideo_decode: enabledwebgl: enabledwebgl2: enabled

Memory (System)
15.88GB (7.91GB free)

Process Argv

Screen Reader
no

VM
0%

Please could you go into the Python output panel and scroll to the top and let us know which of the following messages you see:

Starting Microsoft Python language server.
Starting Jedi Python language engine.

Hello,
the first message is starting Microsoft python language server.
Best regards
Lukáš Matějka
po 20. 5. 2019 v 22:28 odesílatel Don Jayamanne<EMAIL_ADDRESS>napsal:

Please could you go into the Python output panel and scroll to the top
and let us know which of the following messages you see:

Starting Microsoft Python language server.
Starting Jedi Python language engine.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vscode-python/issues/5509?email_source=notifications&email_token=ACCCJYGHD4ZMZSXIJTCGOF3PWMCVPA5CNFSM4HJEMLZ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVZ7JCY#issuecomment-494138507,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACCCJYCFLTV6STG43FARUNDPWMCVPANCNFSM4HJEMLZQ
.

Thanks for clarifying, @flukas.  How are you invoking the file?  (I suspect that everything is working correctly.)
Keep in mind that in Python even if you put a script inside a package, the script will not behave as part of the package.  So if you run python3 xFolder/file2 then from xFolder.file1 import * won't work.  Instead you have to run python3 -m xFolder.file2.

Because we have not heard back with the information we requested, we are closing this issue for now. If you are able to provide the info later on then we will be happy to re-open this issue to pick up where we left off.


Url checking upgrades

Checklist:

[x] Did you sign the Contributor License Agreement?
[ ] Does the CI pipeline pass?

Codecov Report

Merging #158 (9446b6b) into main (7ac2343) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head 9446b6b differs from pull request most recent head 45f6d63. Consider uploading reports for the commit 45f6d63 to get more accurate results

@@           Coverage Diff           @@
##             main     #158   +/-   ##
=======================================
  Coverage   91.27%   91.27%
=======================================
  Files          92       92
  Lines        2373     2373
=======================================
  Hits         2166     2166
  Misses        207      207

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 2c21eb8...45f6d63. Read the comment docs.


Explore Resource Bot into Tiny Killer Micro Bots

I love the Resource Bot as a single point of automation for Postman knowledge, but I'd like to have it exploded into four separate microbots that do one thing and does it well!
Let's break up the Resource Bot into four separate collections:

Documentation
Blog
Videos

Document each one separately, allowing anyone to fork and use it for just one purpose, applying to their own documentation, blog, or videos.
Once separated we can evolve over time based on others feedback.

I splitted this into two separate collections last week. One for the blog, and another for Youtube.
I figured I'll need a lot more data points for collections and that of Documentation wasn't exactly scraping. It was just a simple script that randomly selects a URL, so I left it out.