EnsureDeleted does not reset "identity" columns for InMemory database provider

When unit testing using the InMemory provider, we noticed that using the context.Database.EnsureDeleted() method does successfully "delete" the database (and its data), but it does not reset the values that are assigned to new records for integer id columns.
This is using 7.0.0-rc1-final.
Thanks,
Kevin
Repro:
    public class Person
    {
        public int Id { get; set; }
        public string Name { get; set; }
    }

    public class MyContext : DbContext
    {
        public MyContext()
        {

        }

        public MyContext(DbContextOptions options) : base(options)
        {

        }

        public virtual DbSet<Person> People { get; set; }
    }

    [Fact]
    public void ShowFailure()
    {
        var db1 = GetMyDb();
        var zach1 = db1.People.Where(p => p.Id == 1).FirstOrDefault();
        Assert.NotNull(zach1); // works

        var db2 = GetMyDb();
        var zach2 = db2.People.Where(p => p.Id == 1).FirstOrDefault();
        Assert.NotNull(zach2); // fails (because the DB is on 3 and 4 now)
    }

    private static MyContext GetMyDb()
    {
        var optionsBuilder = new DbContextOptionsBuilder<MyContext>();

        // This is the magic line
        optionsBuilder.UseInMemoryDatabase();

        var db = new MyContext(optionsBuilder.Options);

        db.Database.EnsureDeleted();

        db.People.Add(
            new Person
            {
                Name = "Zach"
            });
        db.People.Add(
            new Person
            {
                Name = "George"
            }
        );

        db.SaveChanges();
        return db;
    }

This is by design. Having a generated column just means that you will automatically have unique values assigned to new entities when you don't supply a key value. Those values starting at 1, incrementing by 1, and being reset when you drop and re-create the database is how SQL Server IDENTITY works... but it is not a contract for how all data stores will work.
If you want to have specific key values saved to the store, then you can just set them on the new entities and EF will save those, rather than having one generated for you.

This complicates using InMemory provider for unit testing - which I thought was one of the major points of the provider in the first place.

If you mock the database with explicit keys, sequencing/auto-increment doesn't happen at all.  This breaks all unit tests that specifically test INSERT operations that expect keys to be generated.

If you delete a database, and then create a database, the implied behavior is that the newly created database would be unmolested by the previous one... It doesn't matter what data store you are using... a new repository should always start with fresh seeds.

@kudoz83 - what I've found myself doing when knowing the key values is important is defining the entities as class variables and with each test executed (e.g., in the constructor) I'll set them to new instances, add them to the in-memory db, then call save changes.  At that point my class variables have the entity.id values populated with whatever value was used.
On other cases I'll query the in-memory database for the entity I want, then use it's current entity.id value.
It takes a little shift in mindset to not expect "the first value saved has an id of 1" but once you get over the hump it's actually not that bad.

I appreciate the effort @kwarnke , but it isn't clear to me from what  are describing, and I don't believe it really supports the argument from @rowanmiller that there is nothing to consider here - your initial submission I think was on point.
I'm currently working through the info here: http://docs.efproject.net/en/latest/miscellaneous/testing.html to try and create proper test cases, I think re-creating a service provider for each test will reset the data store - but I think that the InMemoryProvider should be re-visited to behave more intuitively rather than have this dismissed as "by design."
I think the crux of what brought me to this ticket is actually that you can't assign explicit Id's during the initial construction of the mock database and still expect auto-sequencing to work.  Basically if I could turn off identity-insert when filling with pre-test data, and then turn it back on when it comes time for testing, this would be a non issue.  Deleting the database and re-creating it was kind of a workaround for this - except that it doesn't work, because the identify/sequence seed isn't reset (which is counter intuitive).

@kudoz83 The contract of the API does not provide any guarantee what the generated values will be, only that within the constraints of the service and database being used they will be unique. Therefore, your tests should not rely on the values that are generated.
Also, value generation for in-memory databases is a function of the in-memory database server, not the individual databases themselves. This is by design because it can actually help debug issues when values are not repeated across databases.
As @rowanmiller said, if you want really independent tests, then you will need to create a new service provider for each test.

@kudoz83 in addition, if you do want specific values for the key properties then you can just set them before you save. If you explicitly set a value for the key property, then EF will just insert that rather than letting the database generate one for you. This is true for all providers and not just InMemory.

I want to be able to test an ASPNET core mvc app using EF and inmemory. I'm finding that very difficult to do because of the fact there is no way to really reset an inmemory database. There is also be easy way I have found to provide a new service provider into a TestServer via its Startup class. I shouldn't have to completely change how ASPNET core configures EF to do this, right? I had hopes that specifying a string to inmemory database would let me force it to use a new implementation, so for instance I tried using a new guid there, but that still didn't work and the id values still stepped on one another.


Package installer issue

After installing the package, I don't see the project in the xcode window, nor can I seem to find it anywhere..
os x v10.10.5
xcode v7.2.1
What is the default install location? Any suggestions?

Hey @noisyneuron I just confirmed on my setup that it works:
OSX 10.12.6
Xcode 8.8.3
The last update for the installer involved new code that works only for Swift 3 / Xcode 8+.
If you can't update to Sierra / Xc8, you can try: http://www.c4ios.com/C4Installer_1_1_0.pkg
This is an older version of the installer that should work on your system.

Still no luck... can't find the project anywhere..

If you want to join our slack channel we can chat directly about it, and hopefully I can help you get it running.
https://join-c4.herokuapp.com/

Over a year old, closing.


Keep-alive (reuse) connections running in NodeJS environment to reduce the number of new connections

Ref: https://github.com/nearprotocol/nearcore/issues/1316

@vgrichina Could you do that? (It will require releases on npmjs, anyway.)

ok


Make some endpoints for user stats

[x] Number of unique prompts played
[x] Total number of runs
[ ] Performance over last set of runs
[ ] Best ranking

Defer other stats for now, covered by the acheivemnts


Prototype of how we might configure emulators in Spanner.

Note:

This requires a generator change in order to allow partial classes to intercept Build/BuildAsync methods
I looked into putting common code into the common project, but the fact that every builder type has a different Settings property makes it very tricky

Chris: please see whether you think the generator change makes sense.
Amanda: please review in general
Shanika: please check that this corresponds to your understanding of what's needed to connect to a Spanner emulator
Once we're all happy with this prototype, the next steps would be:

Make the change in the generator
Roll out partial classes for SpannerClientBuilder, DatabaseAdminClientBuilder, InstanceAdminClientBuilder
Add an EmulatorDetection property to SpannerConnection (and SpannerConnectionString, and the session pool key etc)

Oh, and this is currently entirely untested :)

Thanks @jskeet. These are our requirements:

Set the endpoint to what's in the env var. I assume GetEmulatorEnvironment() would return a ServiceEndpoint?
Credentials are set to Insecure.

I think you covered both of these in this prototype.

(But GetEmulatorEnvironment returns a Dictionary<string, string>, basically mapping all the requested environment variables. ServiceEndpoint has been removed from GAX - we now just use a string as the endpoint.)

Closing this pull request, but I'll leave the branch available for a while for reference.
The generator change has now been made, with the partial methods now called InterceptBuild and InterceptBuildAsync.


Change the Screen when user not logged in

Currently it'll looks like this:

Change that button text to: "SignIn with Storybook Hub".
And send the user to: https://hub.getstorybook.io/sign-in

Fixed with #12


For the account-level Gmail integration, show sender name as "<company_name> Team"

Problem
Right now if a team connects an account-level Gmail integration, the email sender shows up as just the email address. This look impersonal and less professional.
Solution
Show the sender name as "<company_name> Team" for now, e.g. "Papercups Team" (we can make this configurable later)
Questions, or need help getting started?
Feel free to ask below, or ping us on Slack :)
(You can also check out our CONTRIBUTING.md)

Fixed as part of https://github.com/papercups-io/papercups/pull/842


Keep the same cursor color when changing your name

As a user, I don't want my cursor color to be changed (its confusing for other people).

Close in #89


Subsetting exception

Just following the example for subsetting from the documentation but I get the following exception:
>>> print(cpg[cpg.CpG > 50])
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "pyranges/pyranges.py", line 101, in __getitem__
    return _getitem(self, val)
  File "pyranges/methods/getitem.py", line 20, in _getitem
    raise Exception("Not valid subsetter: {}".format(str(val)))
Exception: Not valid subsetter: 0        True
1        True
2        True
3        True
4       False
        ...
1072     True
1073    False
1074    False
1075    False
1076    False
Name: CpG, Length: 1077, dtype: bool

Thanks for reporting! Are you on 0.0.46? That is where boolean indexing was introduced :)
python -c 'import pyranges; print(pyranges.__version__)'

Ah okay, no I'm on 0.0.45 (from bioconda)

Bioconda is lagging behind. It is due to PRs having to be reviewed now. pip install should do the trick.

You can still do gr.subset(lambda df: df.CpG > 50), which is slightly faster, but more inconvenient.

Now 0.0.48 is out on bioconda. Please feel free to reopen if you have further issues :)


Update readme.md

Update links to render correctly in MD
Remove trailing whitespaces

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


Implement the SystemInfo module

See https://testinfra.readthedocs.io/en/latest/modules.html#systeminfo

This has already been done.


Capture iOS Screen like in Quicktime

Any plans to allow Kap to capture the video of a connected iphone the way that quicktime does? This would be killer for recording screencast tutorials of iphone apps.

@abreckler I didn't know that's a thing 😅 I don't have an iPhone to test it, so I don't know how we'd proceed with this 😰

We do want to support this though, so I will add planned. Might be able to use my girlfriend's iPhone to test.

Cool, good to hear. I think people will definitely find this useful. @matheuss I would lend you my old iphone if you were closer ;)

First needs to be implemented in Aperture: https://github.com/wulkano/aperture/issues/25
Then it needs some custom UI in Kap for selecting the iOS screen.

This is beautiful. I can't wait, as I was just asking about this on Stack Overflow! <3

https://github.com/wulkano/Aperture/issues/25is currently in progress at https://github.com/wulkano/Aperture/pull/69


[BUG] Support for Map gone?

Describe the bug
With LangChain4j 0.34.0, it was possible to return a Map from a method. The prompt would contain an incorrect statement about the format but you could quite easily override this at the prompt level even if not ideal.
I'm not sure exactly how it should behave but using Maps is quite practical as long as you define things properly in the prompt so maybe we could keep it working and avoid adding any indication of the format in the prompt and let the user do it?
Log and Stack trace
Starting with 0.35.0, we end up with the following stacktrace:
Caused by: dev.langchain4j.exception.IllegalConfigurationException: Illegal method return type: java.util.Map<java.lang.String, java.lang.Integer>
    at dev.langchain4j.exception.IllegalConfigurationException.illegalConfiguration(IllegalConfigurationException.java:12)
    at dev.langchain4j.service.output.ServiceOutputParser.validateJsonStructure(ServiceOutputParser.java:135)
    at dev.langchain4j.service.output.ServiceOutputParser.outputFormatInstructions(ServiceOutputParser.java:125)
    at io.quarkiverse.langchain4j.runtime.QuarkusServiceOutputParser.outputFormatInstructions(QuarkusServiceOutputParser.java:19)
    at io.quarkiverse.langchain4j.deployment.AiServicesProcessor.gatherMethodMetadata(AiServicesProcessor.java:1098)
    at io.quarkiverse.langchain4j.deployment.AiServicesProcessor.handleAiServices(AiServicesProcessor.java:932)
    at java.base/java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:733)
    at io.quarkus.deployment.ExtensionLoader$3.execute(ExtensionLoader.java:856)
    at io.quarkus.builder.BuildContext.run(BuildContext.java:256)
    at org.jboss.threads.ContextHandler$1.runWith(ContextHandler.java:18)
    at org.jboss.threads.EnhancedQueueExecutor$Task.doRunWith(EnhancedQueueExecutor.java:2516)
    at org.jboss.threads.EnhancedQueueExecutor$Task.run(EnhancedQueueExecutor.java:2495)
    at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1521)
    at java.base/java.lang.Thread.run(Thread.java:1583)
    at org.jboss.threads.JBossThread.run(JBossThread.java:483)

To Reproduce
Here is an example of an AI service that used to work with 0.34.0 and doesn't with 0.35.0.
@RegisterAiService(retrievalAugmentor = SimilarityRetrievalAugmentor.class)
public interface TriageAiService {

    @SystemMessage("You are in charge of triaging issues from an Open Source project written in Java.")
    @UserMessage("""
        Find the ten issues represented as JSON documents that are the most similar to the issue delimited by ---

        ---
        {title}

        {body}
        ---

        From now on, only consider these ten most similar issues and ignore the ones that were not selected.
        For these ten most similar issues, return the labels that are affected to them.
        The labels must be returned as a valid JSON map with the key being the label and the value being the number of the ten most similar issues in which this specific label was found.
        Do not return the issues, we only want the labels in the output.
        You must not wrap JSON response in backticks, markdown, or in any other way, but return it as plain text.
    """)
    Map<String, Integer> suggestLabels(String title, String body);
}

Expected behavior
Ideally, I would expect the Map case to be supported but avoid adding any info about the expected format so I can describe what I want.
Please complete the following information:

LangChain4j version: 0.35.0
LLM(s) used: OpenAI
Java version: 21
Spring Boot Quarkus version (if applicable): 3.15.1 with Quarkus Langchain4j 0.35.0

@gsmet thanks a lot for reporting!
My bad, I did not test for Map case explicitly, let me fix this ASAP

@gsmet do you mind reviewing https://github.com/langchain4j/langchain4j/pull/1873 ?


Don't redirect upload output to /dev/null.

Hi @ndarilek,
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!

How does it mess up the logs more than printing the build output does,
even if the build itself is successful?
I don't know enough bash scripting to only print the command output on
failure, but I'd rather have complete but messy logs than incomplete
ones that leave me scratching my head about a problem with no way to
know what's wrong. If this is easier than I think then great, I just
lost lots of time trying to debug this, and the script explicitly hid
the error cause for me with no way for me to opt out.
Thanks.

if ! bla="$(do my command)"; then ...


Anchira - Remove response decrypt

Checklist:

[x] Updated extVersionCode value in build.gradle for individual extensions
[ ] Updated overrideVersionCode or baseVersionCode as needed for all multisrc extensions
[ ] Referenced all related issues in the PR body (e.g. "Closes #xyz")
[x] Added the isNsfw = true flag in build.gradle when appropriate
[x] Have not changed source names
[ ] Have explicitly kept the id if a source's name or language were changed
[x] Have tested the modifications by compiling and running the extension through Android Studio

Probably last update for a few days. Hoping it doesn't break in the meantime.


[TC-IDM-10.2] pics and spec needs to be updated

Summary Title:
[TC-IDM-10.2] pics and spec needs to be updated
Description:
Got failures when I am testing TC-IDM-10.2, the log shows below errors:

MaxPathsPerInvoke is enabled in the device, but it is not declared in the spec.
In the device:

In the spec, there is no attribute MaxPathsPerInvoke(0x16):

MicorwaveOvenMode cluster has not implemented the commands, but the PICS set it as mandatory.
In the PICS:

In the spec:

Steps to reproduce:

Before commission to DUT, make sure DUT in comission mode.
Choose TC-IDM-10.2 and run test-case in TH.

Logs:
TH_log:
[FAILED][TC-IDM-10.2]_[zNw7rlE3]_TH_log.log
DUT_log:
[FAILED][TC-IDM-10.2]_[zNw7rlE3]_DUT_log.log

The same issue visible fo the ICD Management cluster:
logs from the test:
PjdW0NYp_TC_IDM_10_2.log

One of these is a problem with the scraper - the basic info cluster is marked as in-progress, so doesn't get scraped. The other is a real problem with the test, where overriden generated commands aren't properly parsed.

The same issue visible for various other clusters like Time, IcdManagement, ValveConfigurationAndControl, TimeSynchronization and probably quite some others as well.
UI_Test_Run_2024_02_08_15_42_46.log

Same applies to TC-IDM-10.3

Same applies to TC-ACE-2.1 and TC-ACE-2.2

the warnings about timesync and valve config will not cause test failures.

Yes, you are correct: these are only warnings, not errors

To be fair, they DO need to be fixed, but the fix is being tracked on the DM scraper repo, and it's closed, so i can't link the issue. We're hoping to get a new drop before SVE

This should now be fixed - please confirm.

This should now be fixed - please confirm.

This case was fixed, thanks!


Question: Refetching paginated resource after mutation

Hi!
I display a paginated result from useResource at one point in my app. The user can create additional items for this list in a dialog. The docs for immediate mutation updates specify pretty well how to append the result of a mutation in the current cache, for my use case however this does not work because I do not know the pagination params of the list in the create dialog. (This would be impossible to know anyway, since there can be essentially an unknown number of lists of that resource across the app)
Appending the created resource to the paginated list does make little sense, since I can't easily figure out if the new resource matches the pagination criteria. But one way to have a immediate UI update would be to refetch all useResource hooks that use the detail shape, no matter their params. invalidate and fetch only trigger a change for hooks that use the same params, is the a way to tell them to refetch for every set of params that are currently being rendered? Or am I overthinking something/am I looking at this from the wrong angle?
I could not find a discussion forum for the project, sorry for posting this question as an issue.
Kind regards
Simon

@ntucker i'm interested in this one too.
We have for example a Resource. In the current view are two getLists with different query params (pagination, filter, etc). Then we create a new entity within the same view. I'd like to be able to trigger re-fetch of these two lists to which the new entity may or may not apply.
I also have a second use case where this sort of functionality would be triggered from a websocket message too (i think i can use a manager to do this, assuming we can refresh a resource regardless of its query params)

We could have Controller.invalidateAll(key => matches);
Where it checks each key and if it matches will invalidate that endpoint. For RestEndpoints this could use path-to-regex to autobuild the matcher, making it Controller.invalidateAll(MyEndpoint.matchAll);

Sounds like that would work for me 👍

@stufisher https://resthooks.io/docs/api/Controller#invalidateAll latest release has this

Much appreciated, ill try and give this a go this week. Thanks!

Next step to covering more uses cases better is Collections. Please review if interested in this use case!

Collections are the true solution and will be released soon!


What happens if a funtion defined in windows_sys returns type i32 but win32 docs say it can return NULL?

I might be overthinking this but is there a guarantee that the check handle == 0 always hold in case of returned NULL values for windows_sys?
The function in question is OpenProcess and returns type HANDLE. The same in windows returns type Option<Handle> while should be easy to evaluate in case of NULL or no_value. The official documentation(win32docs) says that the function can return a NULL value.

The OpenProcess function in the windows-sys crate indeed returns a value of type HANDLE. HANDLE is a simple type alias for isize, and the expression handle == 0 will always evaluate to true in case the API returns a value of zero.
The Win32 API documentation calls the value NULL because HANDLE is actually a void* in the C header files. C requires that NULL must be "an integer constant expression with the value 0". The expression NULL == 0 is always true.

Return value
If the function succeeds, the return value is an open handle to the specified process.
If the function fails, the return value is NULL. To get extended error information, call GetLastError.

So it won't be an issue to exit the code early if HANDLE == 0 is returned right?

I'm guessing this is asking about resource management obligations. If that is true, then if OpenProcess returned a value that is equal to 0, there aren't any strings attached. There's an opportunity to call GetLastError, but you are free to exit the current scope without having to perform any kind of cleanup regarding this resource.
If the current scope is holding on to resources successfully claimed previously, then those resources still need to be released. windows-sys doesn't provide automatic resource management. It faithfully represents the C API, including manual resource management.
In case I completely missed what you were asking about, could you provide a minimal code sample to illustrate the issue?

Ah, I got it, thanks for the help, also someone pointed me to is_invalid of handle from windows. I just realised that the documentation provided in the link and one on docs.rs have a few definitions missing and no jump to source link.
I think I got it it now that basically we get provided with -1 or 0 in case of a NULL type.

I think I got it it now that basically we get provided with -1 or 0 in case of a NULL type.

The windows-sys crate doesn't provide this translation. It is ultimately a transliteration of the raw C API calls into Rust. There aren't any automatic conversions applied, and error handling is essentially the same as you would have implement it in C. If an API call is documented to return NULL in case of error, you would compare the HANDLE against 0. If an API call is documented to return INVALID_HANDLE_VALUE on error you would instead compare the return value against -1 or INVALID_HANDLE_VALUE.
The windows crate is different: It provides a custom HANDLE type with convenience functions (such as is_invalid). It is this HANDLE type that considers both -1 and 0 invalid, because HANDLE return values [are] so inconsistent.
For a short description of the differences between windows and windows-sys see the FAQ entry How do I choose between the windows and windows-sys crates?.


./build-infer.sh clang ends with error on Ubuntu 20.04

Hello,
I've tried to install infer from source for the passed two days in order to run the analyzer on C code, and have found myself repeatedly getting an error after running ./build-infer clang as follows:
...
[ 98%] Built target arcmt-test
make[3]: Entering directory '/tmp/clang-setup.4nnVxP/build'
Scanning dependencies of target c-arcmt-test
make[3]: Leaving directory '/tmp/clang-setup.4nnVxP/build'
make[3]: Entering directory '/tmp/clang-setup.4nnVxP/build'
[ 98%] Building C object tools/clang/tools/c-arcmt-test/CMakeFiles/c-arcmt-test.dir/c-arcmt-test.c.o
[ 98%] Linking CXX executable ../../../../bin/c-arcmt-test
make[3]: Leaving directory '/tmp/clang-setup.4nnVxP/build'
[ 98%] Built target c-arcmt-test
make[3]: Entering directory '/tmp/clang-setup.4nnVxP/build'
Scanning dependencies of target clang-check
make[3]: Leaving directory '/tmp/clang-setup.4nnVxP/build'
make[3]: Entering directory '/tmp/clang-setup.4nnVxP/build'
[ 98%] Building CXX object tools/clang/tools/clang-check/CMakeFiles/clang-check.dir/ClangCheck.cpp.o
[100%] Linking CXX executable ../../../../bin/clang-check
collect2: fatal error: ld terminated with signal 9 [Killed]
compilation terminated.
make[3]: *** [tools/clang/tools/clang-shlib/CMakeFiles/clang-cpp.dir/build.make:1751: lib/libclang-cpp.so.9] Error 1
make[3]: *** Deleting file 'lib/libclang-cpp.so.9'
make[3]: Leaving directory '/tmp/clang-setup.4nnVxP/build'
make[2]: *** [CMakeFiles/Makefile2:28654: tools/clang/tools/clang-shlib/CMakeFiles/clang-cpp.dir/all] Error 2
make[2]: *** Waiting for unfinished jobs....
make[3]: Leaving directory '/tmp/clang-setup.4nnVxP/build'
[100%] Built target clang-check
make[2]: Leaving directory '/tmp/clang-setup.4nnVxP/build'
make[1]: *** [Makefile:152: all] Error 2
make[1]: Leaving directory '/tmp/clang-setup.4nnVxP/build'
make: *** [Makefile:355: clang_setup] Error 2

  compilation failure; you can try running

    make clean
    './build-infer.sh' clang

Also I've prospected the ongoing issues and running NO_CMAKE_STRIP=1 hasn't been of any help to me.
infer version is 0.17.0
Please tell me if I have forgotten anything of relevance and/or I've duplicated an issue.
Cordially

Can you please try install the ninja package on whatever version of Linux you're running and re-try this?
Ninja should be automatically detected by Infer's build system, so you shouldn't need to do anything different than what you did before.

Will do, and keep you informed on it, thank you for the quick answer !

Hi again, compilation has failed again with following message:
-- Build files have been written to: /tmp/clang-setup.ibSPYr/build/tools/clang/runtime/compiler-rt-bins
[3431/3434] Cleaning compiler-rt...
[1/1] Cleaning all built files...
Cleaning... 0 files.
[3431/3434] Performing build step for 'compiler-rt'
[38/727] Building CXX object lib/sanitizer_common/CMakeF...erCommon.x86_64.dir/sanitizer_platform_limits_posix.cc.o
FAILED: lib/sanitizer_common/CMakeFiles/RTSanitizerCommon.x86_64.dir/sanitizer_platform_limits_posix.cc.o
/tmp/clang-setup.ibSPYr/build/./bin/clang++  -DHAVE_RPC_XDR_H=1 -I/tmp/clang-setup.ibSPYr/llvm/projects/compiler-rt/lib/sanitizer_common/.. -g -O2 -Wall -std=c++11 -Wno-unused-parameter -O3 -DNDEBUG    -m64 -fPIC -fno-builtin -fno-exceptions -fomit-frame-pointer -funwind-tables -fno-stack-protector -fno-sanitize=safe-stack -fvisibility=hidden -fno-lto -O3 -gline-tables-only -Wno-gnu -Wno-variadic-macros -Wno-c99-extensions -Wno-non-virtual-dtor -fno-rtti -Wframe-larger-than=570 -Wglobal-constructors -MD -MT lib/sanitizer_common/CMakeFiles/RTSanitizerCommon.x86_64.dir/sanitizer_platform_limits_posix.cc.o -MF lib/sanitizer_common/CMakeFiles/RTSanitizerCommon.x86_64.dir/sanitizer_platform_limits_posix.cc.o.d -o lib/sanitizer_common/CMakeFiles/RTSanitizerCommon.x86_64.dir/sanitizer_platform_limits_posix.cc.o -c /tmp/clang-setup.ibSPYr/llvm/projects/compiler-rt/lib/sanitizer_common/sanitizer_platform_limits_posix.cc
/tmp/clang-setup.ibSPYr/llvm/projects/compiler-rt/lib/sanitizer_common/sanitizer_platform_limits_posix.cc:1131:1: error: 'assertion_failed__1131' declared as an array with a negative size
CHECK_SIZE_AND_OFFSET(ipc_perm, mode);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/tmp/clang-setup.ibSPYr/llvm/projects/compiler-rt/lib/sanitizer_common/sanitizer_platform_limits_posix.h:1437:3: note: expanded from macro 'CHECK_SIZE_AND_OFFSET'
  COMPILER_CHECK(sizeof(((__sanitizer_##CLASS *) NULL)->MEMBER) == \
  ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/tmp/clang-setup.ibSPYr/llvm/projects/compiler-rt/lib/sanitizer_common/sanitizer_internal_defs.h:336:30: note: expanded from macro 'COMPILER_CHECK'
#define COMPILER_CHECK(pred) IMPL_COMPILER_ASSERT(pred, __LINE__)
                             ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/tmp/clang-setup.ibSPYr/llvm/projects/compiler-rt/lib/sanitizer_common/sanitizer_internal_defs.h:342:57: note: expanded from macro 'IMPL_COMPILER_ASSERT'
    typedef char IMPL_PASTE(assertion_failed_##_, line)[2*(int)(pred)-1]
                                                        ^~~~~~~~~~~~~~~
1 error generated.
[47/727] Building CXX object lib/sanitizer_common/CMakeF...anitizerCommon.x86_64.dir/sanitizer_procmaps_common.cc.o
ninja: build stopped: subcommand failed.
FAILED: tools/clang/runtime/compiler-rt-stamps/compiler-rt-build
cd /tmp/clang-setup.ibSPYr/build/tools/clang/runtime/compiler-rt-bins && /usr/bin/cmake --build . && /usr/bin/cmake -E touch /tmp/clang-setup.ibSPYr/build/tools/clang/runtime/compiler-rt-stamps//compiler-rt-build
ninja: build stopped: subcommand failed.
make: *** [Makefile:355: clang_setup] Error 1

Hmm, not sure, but I found this: https://github.com/rust-lang/rust/issues/69556

Just an FYI, ubuntu-latest for GitHub Actions is 18.04 and not 20.04, which could mean that this is genuinely broken on 20.04, if the current version of LLVM that Infer uses is incompatible with glibc 2.31.

Thank you, I'll check if that helps me somehow a keep you informed. cordially

Soooo, twas impossible for me to get it running on my release of ubuntu so I've proceeded to make it happen in a docker environment, thanks to the dockerfile provided [here] (https://fbinfer.com/docs/getting-started/).
I've not quite put my finger down on what broke the building on Ubuntu 20.04 so I suppose that you are right for that matter. Thanks for taking this issue into account, cordially.

I just tried to build facebook-clang-plugins on 20.04 -- I confirm I get the same error as you do:
/tmp/clang-setup.8icOVA/llvm/projects/compiler-rt/lib/sanitizer_common/sanitizer_platform_limits_posix.cc:1131:1: error: 'assertion_failed__1131' declared as an array with a negative size
CHECK_SIZE_AND_OFFSET(ipc_perm, mode);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/tmp/clang-setup.8icOVA/llvm/projects/compiler-rt/lib/sanitizer_common/sanitizer_platform_limits_posix.h:1437:3: note: expanded from macro 'CHECK_SIZE_AND_OFFSET'
  COMPILER_CHECK(sizeof(((__sanitizer_##CLASS *) NULL)->MEMBER) == \
  ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/tmp/clang-setup.8icOVA/llvm/projects/compiler-rt/lib/sanitizer_common/sanitizer_internal_defs.h:336:30: note: expanded from macro 'COMPILER_CHECK'
#define COMPILER_CHECK(pred) IMPL_COMPILER_ASSERT(pred, __LINE__)
                             ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/tmp/clang-setup.8icOVA/llvm/projects/compiler-rt/lib/sanitizer_common/sanitizer_internal_defs.h:342:57: note: expanded from macro 'IMPL_COMPILER_ASSERT'
    typedef char IMPL_PASTE(assertion_failed_##_, line)[2*(int)(pred)-1]
                                                        ^~~~~~~~~~~~~~~
1 error generated.
[52/727] Building CXX object lib/sanitizer_comm...on.x86_64.dir/sanitizer_deadlock_detector1.cc.
ninja: build stopped: subcommand failed.
FAILED: tools/clang/runtime/compiler-rt-stamps/compiler-rt-build

My guess is that llvm_clang_compiler-rt_libcxx_libcxxabi_openmp-9.0.0.tar.xz will need to be updated to a version of LLVM that works with glibc 2.31.
An alternative solution is to do something like this:

http://www.linuxfromscratch.org/blfs/view/stable/general/llvm.html

(search for Fix a problem introduced by Glibc-2.31 if you are using compiler-rt).

@andrewvaughanj hello! I am having trouble trying to compile from source on 19.10 Ubuntu. When can we expect a new release (and hopefully new binary)?
For compiling from source, would it be possible to use the installed version of clang rather than building it? Compiling clang takes a very long time.

@ubnt-kannan:
Unfortunately, I am not a maintainer or anything of Infer -- simply a contributor. This problem really is with facebook-clang-plugins and not Infer itself, and facebook-clang-plugins needs to be updated to a newer LLVM to avoid this issue.
Unfortunately, given the way that clang plugins work, I believe it is very hard (impossible maybe?) to build facebook-clang-plugins against your system clang, rather than the clang that gets built at part of facebook-clang-plugins. Maybe if your system clang is precisely what's in facebook-clang-plugins you might be able to make it work, but I really have no idea about that.
In terms of a binary release, I know that's been waiting a while (and Infer recently went to 1.0), but I am not sure when that's happening.


Aborting computation

I have a problem in implementing kernel interrupt functionality. Based on the stdin kernel from the example directory, I add few functions. One to simulate long computation:
slowFib :: Integer -> Integer
slowFib 0 = 0
slowFib 1 = 1
slowFib n = slowFib (n - 2 ) + slowFib (n - 1)

and the other to catch SIGINT signal:
interruptable n act = do
  putStrLn $ "STARTING EVALUATION: " <> n
  e <- async act
  installHandler sigINT (Catch (cancel e)) Nothing
  putStrLn "WAITING FOR RESULT"
  r <- waitCatch e
  putStrLn "RESULT RECEIVED"
  return r

and modify clientRequestHandler:
clientRequestHandler :: KernelProfile -> ClientRequestHandler
clientRequestHandler profile callbacks req =
  case req of
    ExecuteRequest (CodeBlock code) _ -> do
      interruptable "precode" $ do
        -- This can be interrupted
        threadDelay 5000000

        -- -- But this cannot:
        -- let f = slowFib 41
        -- f `seq` return 0
        -- return f
      sendKernelOutput callbacks $ ExecuteInputOutput 1 (CodeBlock code)
      -- echoStdin code callbacks
      return $ ExecuteReply 1 ExecuteOk
    _ -> defaultClientRequestHandler profile (simpleKernelInfo "Stdin") callbacks req

complete source code.
The problem is that threadDelay version nicely interrupts, but the one with slowFib does not... and I have no idea why. I asked question on SO because I thought that it was general problem with monad transformer stacks... but nope, actually my simple example given there was wrong.
@gibiansky, can you explain why one work while the other not? How to abort computation properly?
Anyway, library is great. It made making jupyter kernel so painless... much more pleasant than making kernel in python. We use it in production code!

The first thing to check is the masking state at the point. I guess it is MaskedInterruptible.
Basically function serveInternal forks a thread inside bracket without restoring masking state.

Ok, I try that.
But still I don't understand, why threadDelay can be interrupted but slowFib cannot. What is the difference between the two?

@ttylec the difference is that threadDelay is interruptible

which means that they can receive asynchronous exceptions even in the scope of a mask.

Thanks! That was exactly the case. I will prepare pull request to improve documentation for other newcomers.


Fix flakey WhenCompleteScriptIsNotCalled_ThenWorkspaceShouldGetDeletedWhenScriptFinishesRunning test

Background
Fix flakey WhenCompleteScriptIsNotCalled_ThenWorkspaceShouldGetDeletedWhenScriptFinishesRunning test
Deleting a workspace is best effort (try three times and fail silently). If something is locking files or folders then the workspace may fail to be deleted but this is by design.
This makes testing the workspace cleaner reliably somewhat difficult as it is valid for a workspace to not be deleted.
This PR attempts to work around this for the test, trying to correctly identify a failure that is "valid" vs an issue and a real test failure.
How to review this PR

Quality :heavy_check_mark:

Pre-requisites

[ ] I have read How we use GitHub Issues for help deciding when and where it's appropriate to make an issue.
[ ] I have considered informing or consulting the right people, according to the ownership map.
[ ] I have considered appropriate testing for my change.

[sc-67444]


Refactor markdown specification to fix broken internal links

Hello! While referencing the v3.1.0 spec, I noticed that internal links to sections didn't seem to be working (such as in the table of contents, clicking Parameter Object didn't navigate the page to the Parameter Object section. Upon closer examination, I saw that the links were pointing to <a> tags on each header which followed a naming camelCase naming convention. To the best of my knowledge, Markdown tends to generate snake-case anchor tags when rendered as html. This seems to be supported by the rendered markdown on github and the official OpenAPI website.
Problem
The table of contents and other internal links would try and reference page sections using a camelCase naming convention when instead they should be referenced by their snake-case representations. For example, the Parameter Object section, was being referenced with the link #parameterObject when said section was actually being rendered with the link #parameter-object.
Solution
I refactored all internal links to use the snake-case naming convention that would be generated by markdown renderers. However, I didn't want to break any third party viewers which may be relying on the <a> tags within the headers, so I also updated those tags to now use a snake-case naming convention instead.

Was cluelessly working against the release branch instead of v3.1.1-dev. Need to duplicate efforts there to avoid overwriting previous work


[UI][BUG] Reload button is missing any feedback (no spinner)

Describe the bug
I am using an Orbot and sometimes (quite often in fact), Twitter blocks an IP. I have to get new exit node and then click [Refresh] in Fritter.
Problem is, there is no "loading" indication, so I have to look into Orbots up/down speeds to confirm, that it is loading in the background.
To Reproduce
Steps to reproduce the behavior:

Use Orbot, connect to Ror
Find an exit node that is blockd
Change exit node in Orbot
Hit refrest
No indication that it is loading in the backgroun is show, the feed just shows up after some time (if successful)
If not successful, the screen stays the same (no info that it failed again)

Screenshots

Device

Irrelevant

This will be fixed in the next version.


[FEATURE] Allow Users To Change Specific Configurable Options

Describe the feature
After a user purchases a product, they are able to upgrade and downgrade their service now, except configurable options don't show themselves when upgrading
I'd like for users to be able to go to their services tab, and adjust configurable options themselves with a set time period of when they can change it (IE: changing their ptero egg every day, but only allowed to adjust the RAM once a month)
This will help since I currently offer a "build it yourself" package, which users use configurable options to completely make their own service to their liking, but I can't provide a option for users to adjust the options they selected down the road unless I had 2 of the exact same service they'd upgrade to, (but that doesn't work either since users don't have access to configurable options)
V0.9 is a massive change in itself already, so I apologize if this isn't viable for the current state, I've seen the discord and how ridiculous some of the users are when it comes to problems/features (they literally just won't shut up)_

Closing to move to discussion thread


Ajax error occurs randomly

Hi @yajra i just want to ask why is it i will get ajax error randomly when i navigate back and forth to my page...is this due to network?
Thank you in advance

I think this is an environment issue. This mostly occurs when using php artisan serve.

@yajra ,
by the way I am working in localhost
Is this okay in my database.php
 'connections' => [

        'sqlite' => [
            'driver' => 'sqlite',
            'database' => env('DB_DATABASE', database_path('database.sqlite')),
            'prefix' => '',
        ],

        'mysql' => [
            'driver' => 'mysql',
            'host' => env('DB_HOST', 'localhost'),
            'port' => env('DB_PORT', '3306'),
            'database' => env('DB_DATABASE', 'forge'),
            'username' => env('DB_USERNAME', 'forge'),
            'password' => env('DB_PASSWORD', ''),
            'charset' => 'utf8',
            'collation' => 'utf8_unicode_ci',
            'prefix' => '',
            'strict' => true,
            'engine' => null,
        ],

        'pgsql' => [
            'driver' => 'pgsql',
            'host' => env('DB_HOST', 'localhost'),
            'port' => env('DB_PORT', '5432'),
            'database' => env('DB_DATABASE', 'forge'),
            'username' => env('DB_USERNAME', 'forge'),
            'password' => env('DB_PASSWORD', ''),
            'charset' => 'utf8',
            'prefix' => '',
            'schema' => 'public',
            'sslmode' => 'prefer',
        ],

    ],

and my .env
DB_CONNECTION=mysql
DB_HOST=<IP_ADDRESS>
DB_PORT=3306
DB_DATABASE=mydb
DB_USERNAME=root
DB_PASSWORD=

Oops sorry, it's not the .env I am referring to. I was referring to your dev environment. I suggest you use valet, homestead, wamp, xamp, etc. ^_^

@yajra .,
I am using wamp

@ezekel, I'm not really sure on how to fix this one but based on previous duplicate issues, the intermittent error was due to artisan serve or the dev environment you are using. Maybe try updating your settings as a production configurations?


Grammar

Does anyone have a bit more information on this issue, and could we break it down into smaller issues?
If not, can I close this for now? 😁


Global loadbalancer becomes a single container loadbalancer after upgrade

**Rancher Version:**1.2.0 to 1.2.1-rc2
**Docker Version:**1.12.3
**OS and where are the hosts located? (cloud, bare metal, etc):**Ubuntu, Cloud
**Setup Details: (single node rancher vs. HA rancher, internal DB vs. external DB)**Single node
**Environment Type: (Cattle/Kubernetes/Swarm/Mesos)**Catle
Steps to Reproduce:

Create a cattle env in 1.2.0 setup and add few services and global LB
Upgrade rancher to 1.2.0-rc2
Upgrade the LBs from 0.4.2 to 0.4.6

Results:
The global LB is not a global anymore. There is only one LB container.
Expected:
The LB should remain global

@soumyalj could you please provide the calls executed by the UI on the upgrade? I believe it will be 2 calls: update and upgrade

@vincent99 might be a UI issue. Looks like we are not sending all the labels on lbService update/upgrade. Here is the set of labels that were set originally on the service:
"io.rancher.container.agent.role": "environmentAdmin",
"io.rancher.container.create_agent": "true",
"io.rancher.container.pull_image": "always",
"io.rancher.scheduler.global": "true",
"io.rancher.service.hash": "a48ca67e1170db2ea8b7cff6b0750dd7a7785de5",
"io.rancher.service.selector.link": "io.rancher.glb=true",

And these are the labels that UI is sending out:
labels
Object {...}
io.rancher.container.agent.role
"environmentAdmin"
io.rancher.container.create_agent
"true"
io.rancher.service.selector.link
"io.rancher.glb=true"
logConfig
Object {type="logConfig", ...}

Version - v1.2.1-rc3 UI tag 1.2.38
Verified fixed


Support greater utterance ids

Description:

Support utterance ids up to 9999, whereas 100 used to not fit.
Add tooltip in case it's even bigger.

Checklist:
You should check all boxes before the PR is ready. If a box does not apply, check it to acknowledge it.

[x] ISSUE NUMBER. You linked the issue number (Ex: Resolve #XXX).
[x] PRE-COMMIT. You ran pre-commit on all commits, or else, you
ran pre-commit run --all-files at the end.
[x] FRONTEND TYPES. Regenerate the front-ent types if you played with types and routes.
Run cd webapp && yarn types while the back-end is running.
[ ] USER CHANGES. The changes are added to CHANGELOG.md and the documentation, if they impact
our users.
[x] DEV CHANGES.

Update the documentation if this PR changes how to develop/launch on the app.
Update the README files and our wiki for any big design decisions, if relevant.
Add unit tests, docstrings, typing and comments for complex sections.

@christyler3030, two new commits to

Reuse our HoverableDataCell instead of Tooltip

Add an autoWidth feature that lets cell content overflow the cell width.
Refactor cell content out of wrapper to honor column definitions such as align="center".

Fix popper font being different from cell content

Let me know what you think?
Before

After:


Filter directories instead of files

I wonder if there is a way to filter directories instead of files within the option.filter function. Does decompress provides a way to do it or I have to delete them after decompressing, in a promise?
I am trying to delete all the *.lproj (this is actually a directory, not a file) from an OS X application:
const LOCALES = /example\.app\/Contents\/Resources\/(.*?)\.lproj/;

decompress( fullPath, cache, {
    strip  : 1,
    filter : file => {
        return path.extname( file.path ) !== ".html"
            && ! LOCALES.test( file.path );
    }
} ).then( files => {
    // Delete the package once it's decompressed
    fs.unlinkSync( fullPath );

    resolve();
} );

You should be able to do it, the filter option will iterate through all files, including directories.

You can check if a file is a directory by checking file.type === 'directory'.


GEODE-6425: Fixes region stat counter rollover

After fixing GEODE-6424 operations can execute fast enough that some
int counters roll over too frequently to provide meaningful information.
Converting to long counters delays this rollover, which allows for more
meaningful analysis.
Thank you for submitting a contribution to Apache Geode.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[ ] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?

[ ] Has your PR been rebased against the latest commit within the target branch (typically develop)?

[ ] Is your initial contribution a single, squashed commit?

[ ] Does gradlew build run cleanly?

[ ] Have you written or updated unit tests to verify your changes?

[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and
submit an update to your PR as soon as possible. If you need help, please send an
email to<EMAIL_ADDRESS>

Missed several places where we also access the stats by index id.


nice to have: progress management

Remember to run
npx prisma migrate dev
npx prisma db push

[x] chart of questions by type
[x] on hover show number of questions solved
[x] improve styling of dashboard
[x] complete #79

to get questions list:
http://localhost:8000/api/user/get-answered-questions/16
to add answered questions:
http://localhost:8000/api/user/add-answered-question
{
  "userId": 16,
  "questionId": 3,
  "complexity": "MEDIUM",
  "category": ["Dynamic Programming", "String"],
  "answeredAt": "2023-06-14T17:13:54.907Z"
}

The above isn’t a bug (difference in complexity for progress bar and solved questions) it’s cos I manually added a random question that doesn’t tally with the question bank

added in #101


Add doc URLs to deprecation messages

My understanding is that in v6 and v7 there are going to be API deprecations. TSDoc decprecations have been already been added for some of these and they are causing some confusion.
For example, in this issue users of the package gained the mistaken impression that of was deprecated and in this issue, the user was unsure of what was deprecated with startWith(null). In both of these situations, the deprecation messages were due to subtleties with TypeScript's signature matching mechanism.
For contributors, it might be obvious what is and what is not deprecated, but it's understandable that users of the package might be confused by deprecation messages that are reported after a patch upgrade - particular when the deprecation message seems to related to 'normal' use.
We could make this somewhat clearer by creating a simple markdown document for each deprecation that lists what is deprecated and why and could add a link to that document in the deprecation message itself. Doing so should not require too much effort and should go some way to curtailing the opening of deprecation-related issues.
@benlesh @JWO719

See also this comment regarding endWith. That user was passing undefined and without strictNullChecks enabled, undefined will match the signature with the Scheduler in it.

I'll like the idea. If all agree to this approach I can prepare the docs site for this!

I had the same problem with startWith and didn't understand the documentation which was
deprecated startWith(     scheduler: SchedulerLike): MonoTypeOperatorFunction<T> use scheduled and concatAll (e.g. scheduled([[a, b, c], source], scheduler).pipe(concatAll()))
Ended up here to figure out that it's because of the type not getting inferred. Added type like this to solve it startWith(permission.control.value as boolean).

I think the deprecation messages themselves need to be improved. Things like this keep popping up because the messages aren't sufficiently specific: https://stackoverflow.com/questions/56571406/is-the-startwith-operator-in-rxjs-really-deprecated

Yet another: https://github.com/ReactiveX/rxjs/issues/4918

Hi @cartant !
From what I understand there are the following problems:

Creating a markdown document for deprecations and lists deprecations plus an explanation.
Add a link to that markdown document in deprecation messages.
Find ways to improve the format of depreciation linter messages.
Find ways to include a link to the deprecations document in the changelog #4577

For 1 I believe this is related to #4841 with  precondition of #4688
For 2 We can create a script for that. I guess @JWO719 can give details.
For 3 we could use formatter:
current styling

following quick options:

using built-in formatters like stylish

tslint --project tsconfig.json --config tslint.json -t stylish ./index.ts

or we can use custom formatters and extend  stylish with links to the docs

tslint --project tsconfig.json --config tslint.json -s ./formatters -t stylishRxJS ./index.ts

POC can be found here
For 4 we could just add another script to the tools folder that checks if there are deprecations. If yes ad the link.

Please let me know your opinion

Unfortunately, I don't think we should use a formatter.
I was not anticipating a solution requiring developers having to adjust there linting configuration and I don't think we can require them to do that.
IMO, it should report understandable messages - that include a URL - without configuration changes.
I would prefer to see a message like this:
ERROR: 3:11  deprecation  of is deprecated: passing a scheduler to of is deprecated - see https://rxjs.dev/<whatever>

where passing a scheduler to of is deprecated - see https://rxjs.dev/<whatever> is what would be in the TSDoc.
The of is deprecated part of the message is unavoidable - and unfortunate - so I think the message that follows after that is critical. It has to be succinct and understandable and, IMO, followed by a URL that links to a document with a detailed explanation of the reason for - and the implications of - the deprecation.

I had a look at your answer and a discussion with @JWO719 about the docs part.
I would do the following things:

Create a list of all deprecations to track the progress

In the docs under api/deprecations I will refactor the table to table of content

In api/deprecations below the TOC, I manually insert content for each deprecation.
The content has the following structure:

Deprecation name
Reason for depreciation
Implications of deprecation
Refactoring suggestion or link to migrate scripts

I use the create list and update manually every deprecation message.
The message has the following sections:

GenericDeprecationError
HumanReadebleShortMessage
LinkToDeprecationPage

And follows the pattern:
<GenericDeprecationError> <HumanReadebleShortMessage> - see <LinkToDeprecationPage>

I create the checklist here:

[ ] combineLatest - static method deprecated
[ ]
[ ]
[ ]

Here the first draft of the list:

[ ] combineLatest - operator function - deprecated
[ ] merge - operator function - deprecated
[ ] zip - operator function - deprecated
[ ] concat - operator function - deprecated
[ ] race - operator function - deprecated
[ ] of - static method - deprecated in v8
[ ] of - static method - no generic argument
[ ] combineLatest - static method - resultSelector deprecated
[ ] combineLatest - static method - scheduler deprecated
[ ] combineLatest - static method - multiple args as array
[ ] startWith - operator function - derived operator from scheduled and concatAll
[ ] merge - static method - derived operator from scheduled and mergeAll
[ ] endWith - operator function - derived operator from scheduled and concatAll
[ ] concat - static method - derived operator from scheduled and concatAll - removed in v8
[ ] forkJoin - static method -multiple args as array
[ ] forkJoin - static method - no resultSeletor anymore
[ ] create - static method - deprecated in favour of new Observable()
[ ] Observable - class - use an observer object instead of callbacks
[ ] zip - static method - no resultSelector anymore
[ ] switchMapTo -operator function - no resultSelector anymore
[ ] never - static method - deprecated in favour of constant
[ ] concatMap - operator function - no resultSelector anymore
[ ] mergeMap - operator function - no resultSelector anymore
[ ] empty - static method - depricated in favour fo constant
[ ] concatMapTo - operator function - depricated
[ ] exhaustMap - operator function - no resultSelector anymore
[ ] switchMap - operator function - no resultSelector anymore
[ ] tap - operator function -  use an observer object instead of callbacks
[ ] NotificationKind - string litterals instead of enums
[ ] VirtualTimeScheduler - class - frameTimeFactor removed in v8
[ ] VirtualTimeScheduler - class - index removed in v8
[ ] fromEvent - static method - no resultSelector anymore
[ ] fromEventPattern- static method - no resultSelector anymore
[ ] WebSocketSubject - class - use deserializer in favour or resultSelector
[ ] mergeMapTo - operator function - deprecated
[ ] Scheduler - class - implement own scheduler instead
[ ] timeInterval - static method - use only as interface
[ ] from - static method - depreacted in favour of scheduled
[ ] partition - operator function - use static method instaed
[ ] bindNodeCallback - static method - no resultSelector anymore
[ ] TestScheduler -class - hot/voldObservable not for public use
[ ] bindCallback - static method - no resultSelector anymore
[ ] generate - static method - resultSelector needs deprecation. currently missing

@cartant
I would need a bit of input about the grouping and reverencing them.
I would like to create a timeline that lists all deprecation by release.
If a deprecation gets removed I list the removal and a link to the deprecation with detailed instructions.
What is the best way to discover in which release the deprecation was introduced?

I went through all deprecations and found the version of the introduction.
@benlesh
Please introduce a rule that commits need to mention deprecations!
It took me forever to set up this list. Also, it will take users forever to find out what to do because even in the changelog there is nothing.
Introducing some rules to commit messages and the changelog will help everyone A LOT!

I created a first draft of the deprecation page. I would need some feedback about the content and the linking. Sometimes it is pretty repetitive content, especially in the remove sections.
Also the namings: Removed, Old usage, New usage etc are not really good.
I'm happy for every input. :)
In the following my first try:
...

Deprecations introduced in version 6.0.0-beta.4 on 2018-03-29

Static method never deprecated in favour of constant NEVER
Removed in version 7.x
Reason for deprecation
Deprecated because it is more efficient?
Implications of deprecation
Replacing never with NEVER
Refactoring Suggestions
Old usage:
import { never } from 'rxjs';

never();

New usage:
import { NEVER } from 'rxjs';
NEVER;

Static method empty deprecated in favour of constant EMPTY
Removed in version 7.x
Reason for deprecation
Deprecated because it is more efficient?
Implications of deprecation
Replacing empty with EMPTY
Refactoring Suggestions
Old usage:
import { empty } from 'rxjs';
empty();

New usage:
import { EMPTY } from 'rxjs';
EMPTY;

...

Deprecations removed in version 6.0.0-beta.5 on 2018-03-29
...
...

Deprecations removed in version 7.x on ???

Static method never removed
Deprecated in version 6.0.0.beta-4 see refactoring suggestions there

Static method empty removed
Deprecated in version 6.0.0.beta-4 see refactoring suggestions there
...
...

I like it. I think it will resolve a lot of confusion. If figuring out when the deprecations were added it too tedious, I'd suggest a section titled "Deprecations introduced prior to /* some date */".

I updated the draft above and used tables.
Thanks for your feedback and time! <3
I guess I have everything from the content side to start. I will discuss the rest with @JWO719 regarding the integration.
If more feedback pops up, just shoot!

@JWO719 I updated the todos with a JSON structure.
Please confirm it so I can start working on it.

The json structure looks good to me, I could imagine that this could be autogenerated at some point of time!

Exactly this is the reason I want to start with a JSON right away. :)
THX for the answer!


feature request: way to shut down gracefully

right now it's impossible to end the pg client.

sorry, I forgot that we can pass in our own client.


Load base split don't work in scenario of pure little table scan

Bug Report

What version of TiKV are you using?

./tikv-server -V
TiKV
Release Version:   6.2.0-alpha
Edition:           Community
Git Commit Hash:   b1952dcaf8af9ab218916b26eb5dd3ce72a8d638
Git Commit Branch: heads/refs/tags/v6.2.0-alpha
UTC Build Time:    2022-07-22 05:51:18
Rust Version:      rustc 1.62.0-nightly (7c4b47696 2022-04-30)
What operating system and CPU are you using?

Steps to reproduce

Disable corpr-cache
1、Use sysbench to prepare 1000 rows tables;
2、Run select count(*） from sbtest1 in parallel;
3、Check region count of table sbtest1;
What did you expect?
Region can split and CPU should be balance in all tikvs.
What did happened?

/type bug
/assign @nolouch

This is caused by the half split checker with sampling keys with scan in each region_max_size / 1000 size. this case only 1000 rows in the table, it's too small, so it cannot find a key. Details logic in:
https://github.com/tikv/tikv/blob/e278777f97cc71aa60cf21550c5e8f55bfa95b84/components/raftstore/src/coprocessor/split_check/half.rs#L39-L57

It's a not blocking issue, will try to improve it in 6.3.

/assign CabinfeverB

/assign @CabinfeverB


serial: Replace the serial-rs crate with serialport-rs

Replace the unmaintained serial-rs crate with serialport-rs.
Closes #86

Thank you! Could you add the libudev-dev package here and also add an entry to the changelog?

I chose to remove the dependency to libudev-sys (by disabling default features for the serialport-rs crate) because cross compilation would rely on a pkg-config config with a sysroot for the target (see readme) which complicates the setup for CI and usage.
Especially since as described here, the impact of disabling this dependency  sums up as : "Enumeration will still be available [...], but won't expose as much information and may return ports that don't exist physically."
This would not be necessary if this PR got merged into libudev-sys: https://github.com/dcuddeback/libudev-sys/pull/8


Update fetch_params.sqf

Hello. I think You have an incorrect entry in the file.

Q
A

Bug fix?
yes

New feature?
no

Needs wipe?
no

Fixed issues
#...

Description:

Content:

[ ] Content part

Tested on:

[ ] Local MP Vanilla
[ ] Local MP ACE
[ ] Dedicated MP Vanilla
[ ] Dedicated MP ACE

Hey there and thanks for the heads up on this.
This "typo" isn't really doing anything bad in the end. The range for the value is 0-3 and the default case isn't happening as there are cases for the whole value range of the parameter.
And this code base won't get any updates anymore, so I appreciate your hint and pull request on this but won't merge it as there won't be any new releases with the current codebase in the master branch. This way I can keep the master (which will move after release of 0.97 in a seperate branch) even with the last release. Although the release page says there are 7 commits since the release, the rar files contain these commits.


⚠ Bofrost.at has degraded performance

In 7a0fc4b, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1084 ms

Resolved: Bofrost.at performance has improved in f85cb00 after 8 minutes.


feat: meta transactions

This PR implements functionality for delegate actions and meta transactions for NEP 366: Meta Transactions.
For @near-js/transactions, this adds:

new action classes and creator for DelegateAction actions
methods for constructing, signing, and encoding DelegateActions
new schema entries for DelegateAction
new classes for NEP 461 prefixes

In @near-js/accounts I've added Account methods:

signedDelegate builds and signs a delegate action
signAndSendMetaTransaction builds and signs a meta transaction derived from the delegate action

A new cookbook example in included to demonstrate the usage of the new Account methods.

sorry misclick

we're going to need to pull almost all of the types into the types package and only keep internal/local types in the individual packages that use the @near-js/types package

The crux of the issue is that many of these are classes implementing methods with heavy dependencies not appropriate for @near-js/types. Transaction is a good example but PublicKey is even better. To do it cleanly requires another substantial refactor with breaking changes.

I think this is why a Transaction type exists in the types package, but because Action types don't, the Transaction type in the types package defines actions as an type.

The Transaction type in @near-js/types is a duplicate definition that originally came from the providers.ts file before the refactor. They should be merged when appropriate.


Well, this borked my client

I installed this on through the jellyfin windows client and just clicked on a skin and hit "set" to see how it looked. It was far too bubbly, so I went back into the plugin and clicked it again to open it back up... but was greeted with a blank page and a drop menu that was not clickable. I tried to "uninstall" the plugin... and it refuses to. It just spins for several minutes.. I logged out and in, and now I can't log into Jellyfin. I'm kinda at a loss. Is there anything I can share to help work on this? Is it possible to change back to the default theme by editing an xml file? I'm a bit of a noob and really regretting things right now.

If you get a blank page, try to refresh it

I was able to fix it by directly messing with files on the server.. finally got the old theme back


Update kubectl version used in e2e tests

Based off  https://github.com/kubeflow/kfserving/blob/master/test/scripts/create-cluster.sh#L31 , the test cluster uses Kubernetes 1.17.
This PR updates the kubectl version used to a matching version. This version also has the fix for the problem outlined in this issue: https://github.com/kubernetes/kubernetes/issues/91615 where re-applying a CRD with deeply nested properties took a long time.
This PR also changes the README instructions to tell users to use a version of kubectl which has a fix for the above issue.

/cc @yuzisun

Thanks @pvaneck! that's great finding!
/lgtm
/approve


update dependencies, fix all clippy lints

lgtm.

bors try

I think CI is blocked on #49

cargo test does not go through on my machine, but also not in master :/

Hi @elwerene, I've probably caused some conflicts in Cargo.toml – apologies. If you rebase against master and accept them your PR should pass tests and we can merge.

@urschrei I just fixed the conflicts

bors try

bors try

bors try

Existing reviewers: click here to make lnicola a reviewer

try again!

bors try

Hi @elwerene - sorry that this sat so long. Can you explain why you made the most recent change? f71c2a1

Is it https://github.com/rust-lang/cargo/issues/3494 again? :smile:

No, I accidently set the wrong feature before and it wasn't possible to use rustls without defaultls. Now it's just an update without changing the tls feature behavior.
maybe it's the mentioned cargo issue? I'm too tired to understand it atm :)
Maybe tomorrow..


pip installation error

after installing python properly, setting the environmental variable for system and running the code: python get-pip.py
Result:
Collecting pip
Using cached https://files.pythonhosted.org/packages/5c/e0/be401c003291b56efc55aeba6a80ab790d3d4cece2778288d65323009420/pip-19.1.1-py2.py3-none-any.whl
ERROR: Could not install packages due to an EnvironmentError: [WinError 32] The process cannot access the file because it is being used by another process: 'C:\Users\Yahya\AppData\Local\Temp\pip-req-tracker-rsimtfny\084f5a8368fb89a7efa9c04f435e93864cabf099a23e186572afd976'
Consider using the --user option or check the permissions.
would you please help me to solve it?
I do appreciate your help and support.

The first line of the README is: "THIS PROJECT IS UNMAINTAINED."
Your error message has nothing to do with nfldb. The error message even suggests a possible solution to your problem. Maybe you should try it?


99 problems and issues ain't one of them

Playing with PyGithub ... oh the joy

This is a comment. Really a comment

Second Comment


Update TinyMceAsset.php

Updated the tinymce js file for the most recent one. The current file was removed form the original repository.

@PendalF89 Could you please merge this pull request? We use your library in a few projects, and currently, the code is broken in all of them.
By the way, my suggestion would be that the updated line look like this:
public $js = ['tinymce.min.js', 'jquery.tinymce.min.js'];


[BUG] UI - Display the error message on the volume page for backup creation failure.

Describe the bug
There is no error message on the volume page if backup creation fails because of the backup deletion is in progress.
To Reproduce

Create a volume in longhorn and write some data around 300 MB into it.
Take a backup of the volume, say b1
Write more data into the volume 100 MB.
Delete the already created backup b1 and immediately create a new backup.
The screen shows no error.

Expected behavior
The volume screen should show the error message Unable to create the backup as a backup deletion on the same volume is in progress.
Environment:

Longhorn version: Longhon Master - 10/02/2020
Kubernetes version: v18.8
Node OS type and version: Ubuntu 18.04

Additional context:
Once https://github.com/longhorn/longhorn/issues/1845 is resolved, The API response info can be used to implement this.

Assign the backend part of change to @joshimoo

After the 500 API response, The UI automatically handled the error and displayed the error message. So closing this now. We're tracking the enhancement of error messages on the volume details page. https://github.com/longhorn/longhorn/issues/1386


Update jts-core to 1.17.0

Updates org.locationtech.jts:jts-core from 1.16.1 to 1.17.0.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.locationtech.jts", artifactId = "jts-core" } ]

labels: library-update, semver-minor

Skipping for now due to JTS conflict in GT


Enable rebase action in case of Merged STPS

This PR still do NOT resolve the problem from issue #603
Now we have a poor UX, because when we rebase the empty branch, then nothing happen on the graph (edge is still gray), so this give us (or our users) an impression that nothing was done.

Now we have a poor UX, because when we rebase the empty branch, then nothing happen on the graph (edge is still gray), so this give us (or our users) an impression that nothing was done.

@micpiotrowski I opened https://github.com/VirtusLab/git-machete-intellij-plugin/issues/623


[GraphQL / frontend] Support Bean Validation

Entity editor form will now have bean validation support. If an attribute or an entity has a bean validation constraint, and said constraint is not satisfied, then an error message will be displayed. For attribute constraints the message will be displayed under the relevant field. For entity-level constraints the error will be displayed at the bottom of the form.
Known issues:

error messages localization: https://github.com/Haulmont/jmix-graphql/issues/115
compositions are not supported yet: https://github.com/Haulmont/jmix-graphql/issues/116

Related: https://github.com/Haulmont/jmix-graphql/issues/115

couldn't get expected result, validation message has not been dispalying:

Enviroment:
Jmix version: 1.0.0-SNAPSHOT
Jmix Studio plugin version: 1.1.SNAPSHOT3090-211
IntelliJ version: IntelliJ IDEA 2021.1.1 (Ultimate Edition)
Case:

open attached project -> run
open NewEntity editor -> set negative value to age and string with length more than 10 to name -> Submit

AR:
Message keys are displayed instead of messages:

backmod.zip

@vadimbasko Could you please look into above comment?

@vyacheslav-pushkin yes, please open ticket in jmix-graphql module.

@owlet1997

please open ticket in jmix-graphql module.


[Proposal] Replace tsd.json with equivalent typings.json in templates

Duplicate of #53.
I'll update to Typescript 2.0 and @types when @SteveSandersonMS gives the go-ahead. TS2 is still in beta, but types will deprecate even typings. (much easier system as well)

@MarkPieszak Are you happy to do it for all the templates (not just the Angular one)? If so yes please go ahead whenever you're ready. If you prefer not to do the non-Angular ones, lets hold off until I can do them all at once, as it's advantageous just to have one common approach.

Sure I'll fix up all the templates, let me get going with that one :+1:

@SteveSandersonMS
Are you on Slack or anything? Tough talking on here!
I was going to say, TS2.0 is still in beta, we'll have to have some instructions on how someone can get 2.0beta setup in their environment in VSCode & VStudio, either way I can get the PR in and we can decide to hold off merging it until the official release, or get in there sooner. Whatever you want!


Add unit tests for TransferPayload and PaymentRequest Printable encodings

TransferPayload <-> Printable_TransferPayload
PaymentRequest <-> Printable_PaymentRequest

Motivation
Increase unit test code coverage
In this PR

Added TransferPayloadTests and PaymentRequestTests to UnitTests

Can we write a failing test for TransferPayload that has both "bip39" and "rootEntropy" set ?

Can we write a failing test for TransferPayload that has both "bip39" and "rootEntropy" set ?


Possibility to pass SecurityContext to HttpClient creation

Hi, thanks for making this lib!
To support connections to a parse server with a self-signed certificate from a mobile app, I need to pass a special created SecurityContext to the creation of the HttpClient. Are there any plans to do so?
Would it help if I prepare a PR?
Thanks in advance!
Best regards,
Chris

Hey Christopher
Yeah sure, I've not actually had to do that before so I'm unsure on best
approach regarding certificates. So yes, please create a PR.
Cheers
On Tue, Feb 5, 2019, 08:04 Christoph Bayer<EMAIL_ADDRESS>wrote:

Hi, thanks for making this lib!
To support connections to a parse server with a self-signed certificate
from a mobile app, I need to pass a special created SecurityContext to the
creation of the HttpClient. Are there any plans to do so?
Would it help if I prepare a PR?
Thanks in advance!
Best regards,
Chris
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/phillwiggins/flutter_parse_sdk/issues/71, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AHgn3mTBScj1GHfBfrn1Ibe6OeGrGwesks5vKTsEgaJpZM4aitCZ
.

I'm working on a solution, but I have one question: Is this lib compatible with dart:html or is it built just for dart:io? It would be much nicer to implement if no compatibility with dart:html has to guaranteed.
Inside parse.dart dart:io is imported...
Thanks for your support!

Hey
This lib isn't compatible with dart:html due to this lib being directly
created for Flutter. (Flutter can't be used with dart:html, Sorry!)
I appreciate your work!
Thank you!
On Thu, 7 Feb 2019 at 10:51, Christoph Bayer<EMAIL_ADDRESS>wrote:

I'm working on a solution, but I have one question: Is this lib compatible
with dart:html or is it built just for dart:io? It would be much nicer to
implement if no compatibility with dart:html has to guaranteed.
Inside parse.dart dart:io is imported...
Thanks for your support!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/phillwiggins/flutter_parse_sdk/issues/71#issuecomment-461372329,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHgn3pIebti9tAetxpgisnjBqKIJJKKhks5vLAUigaJpZM4aitCZ
.

--
Kind Regards
Phill Wiggins
<EMAIL_ADDRESS>

Hi,
that makes it a lot easier :-)
I have created a PR, can you please review? I just started to look in dart and flutter some weeks ago, so please don't hesitate to give me hints what can be made better.
Cheers,
Chris

Hey Chris
Looks interesting, I'll run some tests tonight and merge if it's looking
good. Just to confirm, this PR isn't forcing users to use SecurityContext
is it? I'm running through an overview of the PR and it looks to assume
that there is always a SecurityContext in ParseCoreData in some areas? Is
that correct?
Cheers
On Thu, 7 Feb 2019 at 15:21, Christoph Bayer<EMAIL_ADDRESS>wrote:

Hi,
that makes it a lot easier :-)
I have created a PR, can you please review? I just started to look in dart
and flutter some weeks ago, so please don't hesitate to give me hints what
can be made better.
Cheers,
Chris
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/phillwiggins/flutter_parse_sdk/issues/71#issuecomment-461466108,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHgn3uGpDpVtfXSKJ9xjbxHSu01zFliJks5vLESFgaJpZM4aitCZ
.

--
Kind Regards
Phill Wiggins
<EMAIL_ADDRESS>

Hi,
No, you do not have to use a SecurityContext, it is an optional parameter to Parse().initialize(). It should be 100% backwards compatible. There is now always a SecurityContext in ParseCoreData, but this is null in case of no context has been set. In this case the old behavior without a context is used:
ParseHTTPClient([SecurityContext securityContext])
      : _client = securityContext != null
            ? IOClient(HttpClient(context: securityContext))
            : IOClient();

Amazing! Thank you for your work!
On Thu, 7 Feb 2019 at 15:42, Christoph Bayer<EMAIL_ADDRESS>wrote:

Hi,
No, you do not have to use a SecurityContext, it is an optional parameter
to Parse().initialize(). It should be 100% backwards compatible. There is
now always a SecurityContext in ParseCoreData, but this is null in case of
no context has been set. In this case the old behavior without a context is
used:
ParseHTTPClient([SecurityContext securityContext])
: _client = securityContext != null
? IOClient(HttpClient(context: securityContext))
: IOClient();
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/phillwiggins/flutter_parse_sdk/issues/71#issuecomment-461476578,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHgn3opMtWdgcvaBWq51TZRO9PEmutxZks5vLEmDgaJpZM4aitCZ
.

--
Kind Regards
Phill Wiggins
<EMAIL_ADDRESS>


[VS Classic] Implement status bar

It needs to show:

"|{ Refact" when idle
rotating icon of some sort when it's thinking about the new completion
contrast background and "unplugged" icon when error, tooltip should show what the error was

@olegklimov or did you just mean that the unplugged icon should visually stand out

@digital-phoenix unplugged is just this:

And this:

Give the LSP server a wrong address or something, you'll see an error. Or turn off Wi-Fi on your laptop.

@olegklimov do you have an image I could use for "|{ Refact" or the disconnected plug icon?

Almost! We need to give you @digital-phoenix a rotating icon. And a disconnected plug.

no status popup, no icon changes when hovering;
no error message if you delete api key, close settings, open settings and add new incorrect key - still working;
no error message when change correct url to incorrect;
if no API key there is message "500 Internal Server error, no caps available" instead of "Missing authorization header";
incorrect message "The API key is not recognized" when API key is incorrect;
need to reload IDE when added correct API key;

My list of unfinished things:

Popup that says which model was last used
Error message in the same popup, error icon, maybe error background in status bar
Errors that should make it into the popup (and icon): any LSP errors (give it a misspelled model), connection problems (turn wifi off), bad API key (especially important for the message to be intelligible).
If the API key is empty, popup should give a link to README on github to the #installation header, so people know what they need to do to make it work

No, it's too intrusive. Background and icon change are good ideas. But not a popup that might be annoying.

@olegklimov i think the rotating icon is working what else need to be done


Add advice for connect: connection refused error

Overview
Error as reported by the current version of the plugin:

error connecting to server (host: server1.example.com, IP: <IP_ADDRESS>): dial tcp <IP_ADDRESS>:443: connect: connection refused

23.4 represents the monitored server.
I often see this when the remote service has been stopped for various reasons (e.g., replacing a certificate, upgrading the app or it has crashed).
We should suggest checking the specified port (less likely) and remote service state (more likely).
References

https://github.com/atc0005/check-cert/issues/585
https://www.pico.net/kb/what-is-a-tcp-connection-refused/
https://groups.google.com/g/golang-nuts/c/2CaywyD7IiU

Two systems:

<IP_ADDRESS>

run the plugin

<IP_ADDRESS>

to test against

From system 2:
sudo firewall-cmd --zone=internal --add-source="<IP_ADDRESS>"
sudo firewall-cmd --zone=internal --add-service="https"

From system 1:
$ /usr/lib64/nagios/plugins/check_cert_dev --server server1.example.com --port 443
9:28AM ERR github.com/atc0005/check-cert/cmd/check_cert/main.go:304 > Error fetching certificates chain error="error connecting to server (host: server1.example.com, IP: <IP_ADDRESS>): dial tcp <IP_ADDRESS>:443: connect: connection refused" age_critical=15 age_warning=30 app_type=plugin apply_expiration_validation_results=true apply_hostname_validation_results=true apply_sans_list_validation_results=false cert_check_timeout=10s expected_sans_entries= filename= logging_level=info port=443 server=server1.example.com version="check-cert v0.14.1-dev.1.gadc51c4 (https://github.com/atc0005/check-cert)"
CRITICAL: Error fetching certificates from port 443 on server1.example.com

**VALIDATION ERRORS**

* error connecting to server (host: server1.example.com, IP: <IP_ADDRESS>): dial tcp <IP_ADDRESS>:443: connect: connection refused: consider double-checking specified port and remote service state (i.e., make sure service is actually running on given port)
 | 'time'=3ms;;;;

From system 2:
sudo firewall-cmd --zone=internal --remove-service="https"
sudo firewall-cmd --zone=internal --remove-source="<IP_ADDRESS>"


Mysterious image appeared in my project

Describe the bug
I made a background in my project and named it. I went to check it out in the Asset Editor, and when I came back, it became an image that I didn't create.
I've done this in multiple projects, but it's a different mysterious image each time
https://makecode.com/_Fj76g7a4g6Cy
Screenshots

Desktop (please complete the following information):

OS: ChromeOS
Browser Chrome85

This seems to fixed. @livcheerful can you validate in /beta?


Add userinfo command to /commands/Tools.

I made a userinfo command for my bot using Komada and I figured I'd try to get it added here, just cos why not.. if anyone wants to use it, go ahead! :D
P.S. sorry for the bad ways I code it, with the unnecessary variables, etc.

Turns out the quality sucks, and I dont really wanna add this command anymore.


Fix to avoid throwing errors on aborted requests

I'm downloading large sets of json files using superagent from a slow server. In some cases, I need to abort the request using .abort() method.
When the json is in the middle of the transfer, I get a syntax error when superagent tries to parse the partially transfered json string.
I think that on aborted requests, the parser shouldn't throw any error.
Thanks for the good work, and let me know if I can help fixing this.

LGTM. Recommend merge. Semver patch vs minor is debatable but I guess the conservative path would be to consider this a semver minor change.

+1


tests: minor cleanup to tests/modify board coverage/types

tests: arch/timing: cleanup test configuraton
boards: frdm_k64f: remove as default platform
boards: arc/nsim: all nsim variants are simualtors
tests: timer_behavior: nsim_em is now marked as simulator

(should this go for 3.2?)

(should this go for 3.2?)

would be nice.

(should this go for 3.2?)

would be nice.

Cool, was thinking about the implications of removing the frdm_k64f board, maybe reducing potential problem visibility from the CI, but then we are keeping an eye on the bi-weekly full run so we should be alright.

@nashif Any reason frdm_k64f is deleted as the default platform?

@nashif Any reason frdm_k64f is deleted as the default platform?

look at the commit message, this is a remenant from the past, there no justification for this to be the ONLY hardware platform to be set as default in CI, it just builds, no execution. We have enough ARM platforms covered by emulation already. This just adds uneeded load to an oalready overload CI workflow.

Cool, was thinking about the implications of removing the frdm_k64f board, maybe reducing potential problem visibility from the CI, but then we are keeping an eye on the bi-weekly full run so we should be alright.

the frdm_k64f is just being treated like any other board we have in Zephyr, we are not removing anything, it not a defult CI target and It will also be covered in other CI runs (weekly for example).


🐛 Bug Report: Documentation is not available for this url https://backstage.io/link?scm-auth

📜 Description
I tried to set the additional scopes for the gitlab and accessed the documentation it seems not available
👍 Expected behavior
Render the docs
👎 Actual Behavior with Screenshots

👟 Reproduction steps
Go to https://backstage.io/link?scm-auth
📃 Provide the context for the Bug.
No response
🖥 Your Environment
N/A
👀 Have you spent some time to check if this bug has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
None

Hmm woops, think we want to fix this. We had a page that used to do this all the client before. @jhaals can you point us in the right direction here so we can find the old links?

Ah! Thanks for the ping. We'll look into it.


Enable Resolve v2 for workspace

The v2 resolver allows for more fine-grained inclusion of dependency
features. Previously dev-dependency features got merged with 'normal'
dependency features. This may not always be desirable.
For more information see
https://doc.rust-lang.org/edition-guide/rust-2021/default-cargo-resolver.html
Types of changes
What types of changes does your code introduce to thin-edge.io?
Put an x in the boxes that apply

[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Improvement (general improvements like code refactoring that doesn't explicitly fix a bug or add any new functionality)
[ ] Documentation Update (if none of the other choices apply)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Further comments
This should be a non-breaking change as, as far as I could tell no crates had 'hidden' feature dependencies. However, since it is the default since the 2021 edition it makes sense to enable it now so as to reduce potential future workload.

As per docs you provided the resolver = 2 is an implied as long as we use edtion = 2021 which we do.


dispatchEvent before morph in reflex actions

Bug Report
Describe the bug
dispatchEvent before morph mostly for same reflex in sequence (or not). This occured after I upgraded from 3.3.0 version. I adjust stimulus targets to new implementation and remove code as described here in setup#upgrading-to-v-3-4-0
Expected behavior
dispatchEvent after morph  (always?)
Screenshots or reproduction
The last response is in correct way (morph before dispacthEvent).

But when the response is in correct way, I get other errors (I guess this is about view_component_reflex, even me using #id) just to complement this unexpected behaviour above.

All this errors not exist in the previous version. Just in very rare occasions the dispatchEvent is triggered before morph only in production environment.
Versions
StimulusReflex

Gem: 3.4.0
Node package: 3.4.0

External tools

Ruby: 2.6.3
Rails: 6.0
view_component 2.23.2
view_component_reflex: 3.1.2
stimulus: 2.0.0

Hi there! I'm sorry you're having troubles. Could you please prepare an MVCE from the harness project linked in the SR readme so that we can clone, run and fix the issue on our local machine?
We need to be able to interact with code that is breaking to be able to do more than guess or make general suggestions - and have no doubt, we really want to help you fix this.

Hi there! I'm sorry you're having troubles. Could you please prepare an MVCE from the harness project linked in the SR readme so that we can clone, run and fix the issue on our local machine?
We need to be able to interact with code that is breaking to be able to do more than guess or make general suggestions - and have no doubt, we really want to help you fix this.

Just let me know when it's ready. 💙

Just let me know when it's ready. 💙

@leastbad It is a conflict with view_component_reflex and my application 😞 , I removed it in the application (I was testing it with new features) and everything worked perfectly. I will close this issue here and I will perform MVCE in view_component_reflex repository.
Grateful for the attention! You from the stimulus community (reflex, view_component_reflex) are doing an excellent job for the Rails/Web community 😄

@leastbad It is a conflict with view_component_reflex and my application 😞 , I removed it in the application (I was testing it with new features) and everything worked perfectly. I will close this issue here and I will perform MVCE in view_component_reflex repository.
Grateful for the attention! You from the stimulus community (reflex, view_component_reflex) are doing an excellent job for the Rails/Web community 😄

Thanks John! Just let us know if something else comes up.

Thanks John! Just let us know if something else comes up.


URL with heading anchor does not scroll up if website not already loaded

Describe the bug
Using a URL with a blog post heading anchor, the site jumps past the heading. Note this does not occur when using heading anchors on the home page of the demo site; only with blog posts (that I've tested).
To Reproduce
Steps to reproduce the behavior:

Go to "Technical Content" blog post on demo website
Add #examples to the end of the URL
Copy that URL into a different tab/window/browser

Expected behavior
When typing in (or clicking if available) a post heading anchor (ie. the #[Heading name]) while the website is already loaded, the screen will jump past the heading and then scroll back to the anchored heading.
For the Home page, the jump-and-scroll works both while the website is already loaded and when you're going straight from a random tab/window.
Technical details:

Academic Version: Demo Website (0.4.8 ?)
Hugo Version: Demo Website
Browser/OS: Firefox and Chrome, Manjaro Linux

Below is a gif of the behavior:

First we go to the blog post itself. When manually typing in the #examples anchor to the URL, the page correctly jump-and-scrolls.
When copy/pasting that exact same URL into a different tab/window, we get the jump, but not the scroll.

Academic supports a number of dynamically sized components such as the navbar and Portfolio widget. In order to jump to a page anchor, we need to know the offset to the anchor once the dynamic components have begun loading and fed back their render height to Academic.
There are a number of approaches to handle this in the user experience. An alternative, for example, is to show a loading screen until the page has loaded, however one of the general principles of app design is to start rendering earlier rather later.

Gotcha. So is there any solution/actionable for this or is it more just a minor quirk that isn't worth fixing?

This is inherently how web pages are loaded by the browser when powerful async integrations are involved. There is room for Mermaid, Mathjax, etc. to further optimise their code. If you turn off or reduce as much dynamically sized content as possible on your site, then the page load may perhaps be faster with a less noticeable delay on the anchor coming into view.
If anyone wishes to contribute to improving the user experience in some way, then I'll be happy to review a PR as always :)