Transaction parameters are not implemented for hash-tables

The tests show that you should be able to supply them as either a hash-table or an alist, but the implementation only supports alists.
I don't recall why I dropped hash-tables, or what my intentions were at the time, so I need to investigate and resolve this one way or the other.
Discovered while testing #17

Now that I look back, it looks like I silently dropped this idea, but never quite got as far as updating the tests.


Disable Relic, Charm & Potion stacking and Stuff!

Fix #278 disable Relic, Charm & Potion stacking
You can configure it from the user settings.
Default is uncheck.

Add "Having Relic", "Having Charm" into Highlight

Resolve #442 Display the effects of EE potions

Revamp configuration window

Cloud backup via Git

Documentation here
https://github.com/hguy/TQVaultAE/blob/disable-stacking/documentation/GITBACKUP.md
Others
Fix #287 Error when no save found
Fix #467 by making path editing much clearer
Updated overall nuget dependencies to latest.
Fixed binary tool when searched key is not found.

@EtienneLamoureux it looks like the old TQ game has a built in mecanism that detect when an item has been added or removed from the player.chr and make the altered save unplayable (tested on steam). I tried to understand and trick the system but in vain for now.
Putting back the item at the exact same place make the save work again.
So it's not about file format integrity.
It's not a comparison with last backup file either because tweaking the backup file doesn't break the save.
It looks more like a checksum check where the hash is... somewhere.
The solutions are one of these

Making TQ Original save Read Only for TQVault (there is a variant of this idea in issue #268 for vault).
Excluding TQ Original save file from the return value of IGamePathService.GetCharacterList() until we have a solution (read only or other).

For now i'm excluding the feature (option 2), just to be non blocking on the PR.
Considering the facts, i don't think TQVaultAE ever worked with Titan Quest Original.
Maybe @ejfudd have some insight about this?

@hguy That does sound familiar.  I checked my file decoding notes and I did not see anything there about a checksum.  I do have the original TQVault 2.1 code somewhere and it should be in there. I will dig it up and take a look.

@hguy That does sound familiar. I checked my file decoding notes and I did not see anything there about a checksum. I do have the original TQVault 2.1 code somewhere and it should be in there. I will dig it up and take a look.

I confirm that if checksum it is, it's not stored inside the Player.chr after 30 min doing binary compare on this file, i didn't detect any differences except the items. TQVault fully support the TQ Original file format.

Edit: With the original Titan Quest, we used a utility called TQVaultMon which would monitor the Titan Quest process and disable the anti-cheat for modifying your character.

It looks like i just hit the wall of this anti-cheat. I can't find anything about this "TQVaultMon". Do you have any copy, any code somewhere, any link ?

@hguy I was able to find the source for TQVault <IP_ADDRESS>. I have extracted the TQVaultMon project and attached it.
To be honest, TQVaultMon is a relic from before I took over TQVault. The code just does an in-memory patch of the Titan Quest exe file to bypass the anti-cheat. The actual patches were provided by Soulsekkor of TQDefiler fame.
TQVaultMon.zip

@ejfudd Thanks! my investigation lead me to soulseeker/TQDefiler work on this to.
I just decompile the tool to have a look.
Looks like his patch work for v1.2-v1.3, but steam current version is labeled "v1.3.sd" and defiler doesn't support it. I have to look at this a little bit closer when i have time.

@ejfudd @EtienneLamoureux well i did compromise.
https://github.com/hguy/TQVaultAE/blob/disable-stacking/documentation/TQORIGINAL.md

That was probably the quickest and simplest fix.
If the process fix in TQDefiler.NET still works for TQ 1.3, TQVaultMon should also work.  I can post a binary from one of the older TQVault versions or you can create one from the project that I attached previously.  Of course, that's if you want to pursue it.

That was probably the quickest and simplest fix. If the process fix in TQDefiler.NET still works for TQ 1.3, TQVaultMon should also work. I can post a binary from one of the older TQVault versions or you can create one from the project that I attached previously. Of course, that's if you want to pursue it.

That's what i though first, and it certainly must with CD versions until v1.30, but for some reason the Steam version have a memory allocation that TQVaultMon can't handle and TQDefiler does. My prefered solution was to apply patch directly on the TitanQuest.exe, but the Steam binary is also slightly different and i didn't succeed either.
I only use steam version and i don't have any iso for older version, so my testing capability is limited.

Hi @EtienneLamoureux,
Is there any blocking code in this PR ?

Hi @EtienneLamoureux, Is there any blocking code in this PR ?

No, it should be all good :)
Are all the changes documented above?

Are all the changes documented above?

When documentation was needed, yes!


proposal: runtime/pprof: add  WriteGoroutineLabels function for logging

Problem Statement
Given that goroutines are anonymous and there is no accessible goroutine id makes it very difficult to add goroutine context to debug/tracing output without having a context parameter in all functions and a context field in all objects, which is often unfeasible. That lead to many attempts to workaround this limitation and reoccurring debates about it. So, although beyond doubt there is a reasonable demand for context logging, it has deliberately been ignored in order to not undermine the anonymity of goroutines, which is regarded as more important.
Proposal
As a kind of compromise, that allows to log goroutine context, without making it too easy to abuse it for "goroutine local storage", I want to propose the following API:
package pprof

// WriteGoroutineLabels writes the current goroutine's labels to w. If a write
// to w returns an error, that error is returned, nil otherwise. The format of
// the output is not specified, and should only be used for logging/tracing
// purposes.
func WriteGoroutineLabels(w io.Writer) error { ... }

This would easily and efficiently allow to set labels with the SetGoroutineLabels() and Do() functions, and still log them in code paths, where the context is not available, and give important information for log forensics. This is especially useful for 3rd party libraries, that don't support contexts, but do support setting a global log sink for debug output. For example:

import (
  "context"
  "log"
  "runtime/pprof"

  "github.com/ansiwen/foobar"
)

func init() {
  foobar.SetDebugOutput(func(msg string) {
    var lbls strings.Builder
    _ = pprof.WriteGoroutineLabels(&lbls)
    log.Printf(`[DBG]<foobar> msg="%s" context="%s"`, msg, lbls.String())
  })
}

func fireFoobarRequest(id string, data []byte) {
  go func() {
    lbl := pprof.Labels("requestID", id)
    pprof.SetGoroutineLabels(pprof.WithLabels(context.Background(), lbl))
    foobar.doRequest(data)
  }()
}

Edit: added usage example.

It seems like you are suggesting that there are packages out there that don't and won't take a context.Context, and that don't and won't take a logger that could annotate logs however it likes, but that will change their code to call pprof.WriteGoroutineLabels.  Do you have any examples of packages like that?

@ianlancetaylor Thanks for your answer. No, sorry, I think I didn't make that clear enough. I'm talking about libraries, that don't support context.Context but do support setting a logger for debug output. Let me demonstrate it with some example code:

import (
  "context"
  "log"
  "runtime/pprof"

  "github.com/ansiwen/foobar"
)

func init() {
  foobar.SetDebugOutput(func(msg string) {
    var lbls strings.Builder
    _ = pprof.WriteGoroutineLabels(&lbls)
    log.Printf(`[DBG]<foobar> msg="%s" context="%s"`, msg, lbls.String())
  })
}

func fireFoobarRequest(request foobar.Request) {
  go func() {
    lbl := pprof.Labels("requestID", request.ID)
    pprof.SetGoroutineLabels(pprof.WithLabels(context.Background(), lbl))
    foobar.doRequest(request)
  }()
}

(I just sketched that down, probably full of mistakes.) So it basically applies to all libraries that

allow to set a logger or similar as a (global) debug sink
doesn't take a context (or at least, doesn't make it available in the debug log callback) and
that is potentially used concurrently.

Without this "tunneling" of context, it inevitably gets lost, and you can't relate the debug output to the request anymore.
I hope that makes it more clear.

And regarding an example library: While I believe there are loads of libraries that fit into that category, we are about to add debug logging to our ceph Go bindings and realised, that without breaking our API we can't relate the concurrent calls into the library with the debug output.

It seems to me that if you can pass in a logger, then you can create a logger type that attaches any information you like to the log.  It can do the equivalent of pprof.WriteGoroutineLabels, only it doesn't need to call that function because it knows the relevant labels.

@ianlancetaylor How can it do that? Of course it could store any information, but a global logger instance, that is called from concurrent goroutines, could never know, which is the "right" information to add. The result of pprof.WriteGoroutineLabels is depending on the goroutine in which it is called, because every goroutine has its own set of labels.

Alternatively maybe this is also sufficient:
func GoroutineLabelsString() string { ... }

I was following the WriteTo scheme, but maybe in this case that's over-engineered, because the output is shorter.

Sorry, I meant that you pass in the logger appropriate to the goroutine.  I didn't mean to imply that there was a single global logger.

I see. But libraries don't support pass in a logger per request, at least I've never seen that. Either you can pass in a global logger, or they use the standard logger, which output you can redirect. If the library offers a logger per request that is an equivalent of a context.


Auto-include build.gradle from Core module

Contains
Auto includes the build.gradle from the core module if a module has no such file.
Makes working with own forks a bit less complicated :)
How to test
Clone a module via git or delete the build.gradle, then run ./gradlew eclipse or idea. The module should be included in the build process and also have the build.gradle included.

Hooray Jenkins reported success with all tests good!

Hooray Jenkins reported success with all tests good!

Good idea! Thanks for this :-)
I have a Gradle change pending locally that makes sure all modules are compiled more reliably, plus there are another Gradle PR or two waiting. Will get to them all together ASAP!

@Cervator I guess this is a PR you have to look at again.

Update - I grabbed this PR some time back, but after looking around a bit ended up finding a way to do away with build.gradle files in modules entirely - and was able to bake in compile support for Scala and Kotlin while I was at it via new language field in module.txt (although such modules would also still have to declare a dependency on ScalaLib or KotlinLib for runtime support)
Also came with an upgrade to Gradle 3.3 and some other stuff, and I still have a ways to go .. but it does technically build on this PR so it'll auto-close when my stuff is ready and gets merged ... :D
For anybody curious my first big commit is https://github.com/Nanoware/Terasology/commit/9ce582c0a7c7090959ab48ff73c7e818b1c0b4f9 with more coming.

@Cervator I guess we can close this one without merging for now?

@Cervator pinging to see if we can close this one as it is covered by the pull you reference

Will go ahead and close "early" - while I do have this merged I don't know if it'll disappear from rebasing or redoing things. Just a couple commits so I guess losing the contribution stats isn't the end of the world. Will credit in the eventual big PR :-)


Cannot install extensions in VS Code - Insiders

VSCode Version:  v1.46.0-insider
OS Version: Windows 10 Pro

Steps to Reproduce:

Installed Visual Studio Code - Insiders
Rebooted machine
Trying to install any extension produces error: "Failed to install '{extension name}'."

NOTE: I can install extensions on latest stable VS Code, but not in Insiders.

Does this issue occur when all extensions are disabled?: Yes/No
n/a

Same here. It's fixed with #98726
It's currently releasing a new version.


Make it possible to write to 0x1003 - Pre-Defined Error Field

My fix for #14. A bit of a hack I know, but you can have it if you want it

There is a problem with this pull request, because 1003,00 gets write attribute, but associated variable should not be written.
However, I solved the problem the similar way, but inside the CO_SDO_writeOD() function. See https://github.com/CANopenNode/CANopenNode/commit/83b6a7abb4e5df72f915e21c6327d6afa3168c10


Save allissues.csv as .zip rather than .bz2

.bz2 is way more effective, but much less common. For files we want folks to regularly decompress it should be in .zip even though the file size will be bigger.

This will make them both, but ultimately, probably makes sense to just keep the .zip as it is more portable.
    tar -cjvf "$domain-$currentDate-allissues.csv.bz2" "allissues.csv" 2>/dev/null
    zip "$domain-$currentDate-allissues.csv.bz2" "allissues.csv" 2>/dev/null
    rm "allissues.csv"

Using this for now.


[#4460] feat(core): Add the method call of the authorizationPlugin

What changes were proposed in this pull request?
If we want to push the privileges down the underlying system, we need to call methods of the underlying system authorization plugin.
Why are the changes needed?
Fix: #4460
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Add some test cases.

Is this a backport PR?

@yuqi1129 please merge it when CI is passed.

The backend test with condition JDBK17, embedded and MySQL failed as a result of the timeout. I tried again. There is a chance that the test will hang.

The backend test with condition JDBK17, embedded and MySQL failed as a result of the timeout. I tried again. There is a chance that the test will hang.

Let us merge it.


Fix show trail page

@tisderek want to check it out? Just playing around now I'm mplaying munksins


feat: add elixir-provider

Description

Hello @thomaspoignant  This resolves #2493

Work to do:

Testing
Optimization to standard practices.

Pr adding elixir provider to the go-feature-flag

Closes issue(s)

Resolve #
Checklist

[ ] I have tested this code
[ ] I have added unit test to cover this code
[ ] I have updated the documentation (README.md and /website/docs)
[ ] I have followed the contributing guide

Hey @JoE11-y do you still want to add the tests or should I look at it myself?

Apologies for the delay, got sidetracked.
I've started adding them now.


[RFE] Add support for analysis of .NET applications

This is to track enhancement around .NET language provider.

Original enhancement #128 . I think with what we know now about new .NET versus old .NET, we will need to just start a new one.

Keep this issue in mind https://github.com/konveyor/rulesets/issues/4

Documented in #167
Implemented in konveyor/analyzer-lsp#539
What has been documented and implemented is simply the dotnet-external-provider that can be run to perform rules based analysis of .NET applications. This is not yet fully baked into the Konveyor UX.

Hello @pranavgaikwad,
Please add a size label (size/XS, size/S, size/M, size/L, size/XL) to assist in the Konveyor planning process.


Add stargazers to Github Connector quick start and docs

Quickstart: https://github.com/spiceai/quickstarts/pull/178
Docs: https://github.com/spiceai/docs/pull/394/files

Done


Self-signed certificate issue when connecting with Trino

We have a certificate issue when running a query against trino passing the self-signed certificate at https://github.com/opendatahub-io-contrib/data-mesh-pattern/blob/main/supply-chain/trino/trino-certs/ca.crt:
Code to reproduce:
certificate_path = '../../ca.crt'
engine = create_engine(
'trino://' + os.environ['TRINO_USER'] + ':' + os.environ['TRINO_PASSWD']
+ '@' + os.environ['TRINO_HOST'] + ':' + os.environ['TRINO_PORT'] + '/'
+ ingest_catalog,
connect_args={'verify': certificate_path},
)
with engine.connect() as connection:
    result = connection.execute(text('show catalogs'))
    for row in result:
        print(row)
Error:
SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self signed certificate (_ssl.c:1131)
During handling of the above exception, another exception occurred:
MaxRetryError: HTTPSConnectionPool(host='trino-service.daintree-dev.svc.cluster.local', port=8443): Max retries exceeded with url: /v1/statement (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self signed certificate (_ssl.c:1131)')))

This has been corrected with @eformat help. Keeping this issue open to document the resolution here before closing.

This was fixed with help from @eformat with steps as follows:

I reverted the trino KEYSTORE in vault to be the default. It uses a self-signed cert that is valid till 2296 and the CA.crt is checked in here https://github.com/opendatahub-io-contrib/data-mesh-pattern/blob/main/supply-chain/trino/trino-certs/ca.crt

then i regenerated the trino TRUSTSTORE as per the install docs - https://opendatahub-io-contrib.github.io/data-mesh-pattern/#/2-platform-work/3-secrets?id=create-application-secrets as trino has to trust LDAP, API, and CA

basically the superset and trino containers have this CA built into the python chain of trust - if you look at the code it adds the CA and runs "RUN update-ca-trust extract" here - https://github.com/opendatahub-io-contrib/data-mesh-pattern/blob/main/supply-chain/superset/Dockerfile#L69-L70

superset uses sqlalchemy-trino module to connect to trino - so when you setup the DB connection in superset, you must also load the CA in there. I had that step demoed - but those demos were removed cause of upstream - the original instructions are still here though if you want - https://eformat.github.io/rainforest-docs/#/4-aiml-demos/4-data-investigation

now, if you feel the need to regenerate, or change the trust chain / certs - you can, instructions are here - https://github.com/eformat/data-mesh-pattern/blob/main/supply-chain/trino/trino-certs/README.md - but you must be careful to update all the things properly

last thing, there was an error in superset pod

Unable to load SQLAlchemy dialect <class 'trino.sqlalchemy.dialect.TrinoDialect'>: No module named 'thrift'

that was a broken transitive dependency, i fixed this up as well - https://github.com/opendatahub-io-contrib/data-mesh-pattern/pull/90


feat: add a store_padded_segment  method to memory

Feature Request
Describe the Feature Request
Several opcodes have the following behavior:

Given an array of bytes, copy size bytes starting from the offset index into memory starting from dest_offset
If size is bigger than the slice to copy to memory, then fill the remaining memory elements with zeroes

It's not very efficient to duplicate this behavior. Instead, we can add a method to memory:
fn store_padded_segment(ref self: Memory, offset: usize, length:usize, source:Span<u8>);

This function will perform the following:

It first checks that the length is not 0 and returns early if so.

It resizes the memory if needed to fit the data being written.

It handles different cases based on the source offset:

If offset is past end of source, zero-fill the target

If offset + length goes past source end, copy what fits and zero-fill rest

Otherwise, copy the desired slice from source to target

You will then refactor the xcopy opcodes to use this newly introduced method.
Describe Preferred Solution
You will add the required unit tests, covering correct execution of the function and different edge cases.
Related Code
Additional Context
If the feature request is approved, would you be willing to submit a PR?
(Help can be provided if you need assistance submitting a PR)

[ ] Yes
[ ] No

Can I do it?

If I've understood correctly, parameter offset designates the start offset in the source Span. So I think we're missing a dest_offset parameter to define the start offset in memory.
@enitrat Is that right?

Or does offset designate the memory start offset, and we have no offset for the source start (offset = 0)?

Yep second one

@khaeljy I will get back to this tmr, indeed I think there's a confusion but

source is the slice of the data to copy to memory (not padded, not modified)
offset is the memory address we start the copy at
length is the amount of data we will copy

Thanks, that's clearer. Indeed, this sentence confused me a bit: Given an array of bytes, copy size bytes starting from the offset index into memory starting from dest_offset


[dart2wasm] Support non-JS wasm runtimes

We eventually may want dart2wasm to actually work in non-JavaScript environments (wasmtime, wasmer, etc). @askeksa had mentioned a list of a few things that would definitly need to be addressed in order to remove the dependency on a JS/browser environment:

We are currently dependent on JS for the following components:

Event loop
Printing
OS-level timer features, such as current time
Stack traces
Conversions between double and String
Regexps
Math functions (sin, pow, exp, etc.)

For each of these, we'll have to either:

(1) implement the feature in Dart (or intrinsically in the compiler),
(2) link to an implementation compiled to Wasm, or
(3) import an external implementation from the host.

Can existing JS solutions for those environments help here? That is, Javy and spidermonkey.wasm and similar projects compile a JS VM into wasm, so it can run in a non-JS wasm environment. If that JS happens to use wasm, it seems like that wasm could be bundled alongside the compiled JS VM, and "just work" with some glue (e.g. spidermonkey already has wasm support; it would just need to be "pointed" to the bundled wasm rather than to interpret it).
The wasm would run at full speed, and the JS is apparently fast enough for those environments, so this seems viable. Perhaps someone has already done it?
If that existed, then dart2wasm and other toolchains would not need to do any special work to port to non-JS environments (no more than people wanting to run JS there, which is considered a solved problem).

Yeah I contemplated something like the spidermonkey.wasm might be an interesting idea. Off-hand, it might be even more effective for WasmGC modules with a thin JS support runtime attached, rather than a large blob of JS. I don't know what kind of optimizations are done for the JS VM snapshot build, but a "whole world analysis" on the JS support runtime could probably lead to pruning a lot of code out of the JS VM.

(4) Exclude the feature, as it may only makes sense within JS environments. For example, the event loop is a very particular type of code execution model that came to most mainstream languages from JS (e.g. Dart, TypeScript, AssemblyScript), which the host will have to support to enable all the event loop type features in Dart (e.g. futures, microtasks, async/await, streams). However, outside the JS environment, there may be sufficiently large categories of programs/libraries that would not need the event loop, and so it may be useful to have a compilation mode that does not rely on it. There's certainly a subset of the Dart language and libraries that don't need it.
(5) Add the feature as a standard to either Wasm or WASI. Back to the event loop example, if we recognize that it covers a sufficient set of use-cases (such as how it happened for WasmGC), then it may make sense to standardize for event loop-based languages to be able to target all standalone Wasm runtimes that provide it. Dart may not be the only language wanting it. AssemblyScript seems to want it too, and there may be others.

Stack traces could be a good candidate for (5), since it will be difficult to do without support from the engine.

This would be amazing to support better serverless, and general flexible compute, using Dart.
Being able to easily deploy dart applications that are a collection of WASM modules would be revolutionary. Dart is a great language for glueing together libraries quickly, and leveraging existing libraries across languages (esp. rust) that can be compiled to WASM would expand the ecosystem so tremendously.
While this is already possible with https://pub.dev/packages/wasm_run, it would be great to further the interoperability and deployment process. This would be especially useful when trying to deploy cross platform applications that currently use FFI and native compiled libraries for each supported platform. In the highest performance applications, FFI and native code may still be desirable, but for a vast majority of applications, the ease of quickly composing applications and innovating has huge value.
Advantages

Easy interop with other WASM modules/cross language support

LLMs/Langchains
High performance Rust crates
Broad library/language support

Flexible deployment (Web, Cloud, Native)
Architecture interoperability (ex. compiling on arm64 and running on x64)
Ability to run on edge networks
Faster cold starts (vs docker containers)
Lower memory (vs docker containers)
Sandboxing and running sandboxed code

Implementation:

SpiderMonkey.wasm (mentioned above seems like a great start)
Use rust crates to implement missing functionality; Either compile with binary, or link via WASM modules if the wasm module boundary doesn't have too high of a performance penalty.

Event Loop -> tokio
Weak Support -> weak-table
double to string -> rust stdlib
RegEx -> regex
math -> rust stdlib or https://lib.rs/science/math

Upstream support into WASM/WASI spec for managed languages (Go, Python, Typescript, etc..)

--
Regardless of approach taken, facilitating the deployment of applications that are collections of Wasm modules seems like the natural evolution of docker containerization, with even greater platform flexibility, and a higher degree of composability into ever larger applications or pipelines (eg. langchains, llms, sandboxed user code, etc)

I saw some mention of SpiderMonkey from @yjbanov and others. I was wondering if this offshoot helps move things any closer as a possibility at all.

StarlingMonkey is a SpiderMonkey based JS runtime optimized for use in WebAssembly Components. StarlingMonkey's core builtins target WASI 0.2.0 to support a Component Model based event loop and standards-compliant implementations of key web builtins, including the fetch API, WHATWG Streams, text encoding, and others. To support tailoring for specific use cases, it's designed to be highly modular, and can be readily extended with custom builtins and host APIs.

source: https://github.com/bytecodealliance/StarlingMonkey

I saw some mention of SpiderMonkey from @yjbanov and others. I was wondering if this offshoot helps move things any closer as a possibility at all.

StarlingMonkey is a SpiderMonkey based JS runtime optimized for use in WebAssembly Components. StarlingMonkey's core builtins target WASI 0.2.0 to support a Component Model based event loop and standards-compliant implementations of key web builtins, including the fetch API, WHATWG Streams, text encoding, and others. To support tailoring for specific use cases, it's designed to be highly modular, and can be readily extended with custom builtins and host APIs.

source: https://github.com/bytecodealliance/StarlingMonkey

is there a way to use dart2JS to compile a non-web target?
it would be very useful to use dart in fermyon

Yes 💯 @iapicca I have just run into an almost identical use case myself. For my product, I need to compile Dart to JS to run in a embedded JS engine, initially I'm targeting Duktape. I was actually trying to use the DDC for this but the removal of the ability to use it directly via the dart cli command in favour of webserve is very annoying and the best I've found so far is to use --no-release with the build command.
I'm very open to even some pointers from the Dart team about where to go look for underlying Dart compiler APIs thar could used as ideally I want to be able to just compile sets of stand alone functions from one or several Dart libraries (ie. files) and not use a main() entry point at all.

Yes, Dart supports running the JS generated from Dart in JavaScript engines outside browsers. We use this for testing, some teams use it to run Dart applications in node.js too. Some details:
compiler
We don't recommend using the DDC compiler for that. Our recommended approach to use dart2js via dart compile js --server-mode. The --server-mode flag makes browser based libraries like dart:html inaccessible and allows you to use the output of dart2js more easily in those environments. Technically the flag is not required, but it's good practice.
preambles
Code generated by the compiler requires a couple APIs to be available from the engine (imagine APIs like setTimeout, critical to schedule microtasks and other low-level features in Dart). Some of these APIs are usually found in browsers, but may need to be polyfilled for standalone engines.
For that purpose we require a "preamble" file that is customized for the engine that you will be using. We already provide preambles in the Dart SDK for two common engines js-shell and d8. The community currently maintains a preamble for node.js in package:node_preamble.
examples
sass is written in Dart but runs in node.js and is distributed as a npm package. It is a great example that uses node_preamble.
Our team wrote the generator of package:web to run in node. This program needed very little from the Dart language, so we ended up creating a custom and over-simplified preamble for it. It may not be the best example of a preamble, but it illustrates how it all gets integrated together.

Thanks so much for all that information @sigmundch ! 👍🏻  to say that it is super useful is an understatement!
I didn't know about --server-mode, thats very helpful too. Nor about the preambles, again very useful!


[BEAM-11461] update tox and simplify tox.ini

update tox version to the latest to use generative section name for simpler tox.ini

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Choose reviewer(s) and mention them in a comment (R: @username).
[x] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

R: @tvalentyn

R: @tvalentyn

Filed https://issues.apache.org/jira/browse/BEAM-11666 for a flaky test.

Filed https://issues.apache.org/jira/browse/BEAM-11666 for a flaky test.

Thanks @tvalentyn !

Thanks @tvalentyn !


Redirecting inside Composers?

Hi,
According to mantra specs : If you need to redirect upon some condition (for example user is not authorized) use an action instead of route options like FlowRouter’s triggersEnter. Call the action from component or container’s composer function.
In colors module redirection is commented out as below:
meteor-mantra-kickstarter/client/modules/_colors/composers/colors/single.jsx
 if (Meteor.subscribe('_colors.single', _id).ready()) {
    const record = Collections._colors.findOne(_id);
    if (record) {
      onData(null, {record, error});
    } else {
      // FlowRouter.go('/colors');
    }
  }

Please help to figure out what is the proper way to redirect inside composers.
Thank you.

This is also happening in the users module here https://github.com/mantrajs/meteor-mantra-kickstarter/blob/v0.2.1/client/modules/_users/routes.jsx
I'd also like to know if this is the correct way of handling this @arunoda

I think that it should be display 404 page,not redirect.

This is and old branch, I am currently refactoring the entire app. A new version should be ready by the end of this weekend


OKHttp retry

When OKHTTP retries because of a 408, it does not respect the "Retry-After" header.  It looks like this is a standard header.  Could we add in this feature to respect the "Retry-After" header when retrying.
Thanks.

I would think if this value is non-zero we should be returning the response
directly and push the work of deciding to retry onto the application layer.
On Wed, Oct 25, 2017 at 12:42 AM jeffreyfan8<EMAIL_ADDRESS>wrote:

When OKHTTP retries because of a 408, it does not respect the
"Retry-After" header. It looks like this is a standard header. Could we add
in this feature to respect the "Retry-After" header when retrying.
Thanks.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/square/okhttp/issues/3665, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAEEEbS_yie8cl1P2QPk09eIwvgk8V8lks5svoPbgaJpZM4QFSF5
.

n.b. not clear that 408 with Retry-After is an official or common thing, but seems implicit.


PLAT-65613: avoid crash with spawnSync call for each request

used keep-alive connection to send request.
response is written to/read from a specific file so that both VSCE process and server process have access to, to keep the process synchronous.

@c3wenjiaowang do we need to update the version?


Request: Change default limit value from 10 to 0

At the moment the default limit is 10 which is pretty low.
If no limit is given with ListingParameter Object the new limit should be 0 -> all listing entries.
The initial start is easier with all list entries given (default page=1 and limit=0). With this defaults the default constructor of ListingParameters can be used. If the list grows the need for pagination and limits starts and the frontend can provide the mandatory parameters 'page' and 'limit'. The defaults are no longer needed then.

Zero ist not a good default, it can break the system. I vote for 20 as default.
Details why limits are needed from stackoverflow:
https://stackoverflow.com/questions/52348110/what-is-a-good-practice-for-pagination-using-page-number-limit-in-go
and this is how tthe gothub api handles it:
https://developer.github.com/v3/guides/traversing-with-pagination/

Not a bug

Not a bug


deep.linkId is not set at first render and changes only after reload

How to reproduce
Run this test

I had to use this "hotfix""crutch" in my code: https://github.com/deep-foundation/sdk/blob/22fe15eb29eb02238229756f3f9d115dd7fbe15e/imports/react/components/with-login.tsx#L28


fix(gateways): treating delegated gateways as builtin gateways

Changes the gateway detail view’s policy tab to treat delegated gateways the same as regular Data Plane Proxies (i.e. the same as the DPP detail view’s policy tab).
Resolves #1720.
Signed-off-by: Philipp Rudloff<EMAIL_ADDRESS>

We should probably test this out also, either a follow up here or in a separate is fine by me.

Yep. But I think we should talk through how we want these views to evolve. From a past conversation with Charly, it seems we might actually go back to the DPP list to handle all types of DataplaneOverview and turn the Gateway list view into something more dedicated.


Unable to document variadic arguments

Short summary of your issue
Variadic arguments are not accepted
Codes
/**
 * Says hi
 * @param {...string} people  a list of names
 * @returns array
 */
function sayHi() {
    return [...arguments].map((s) => "Hi " + s);
}

Output data
Log
warning: signature mismatch: Enum app/lib/hi.js#1

Workaround
This somehow works:
@param {...string} ...  <description>
Your environment

OS type and version: macOS
Node.js version: 6.6.0
ESDoc version: 0.5.2

Found a workaround that seems to be working pretty well. Closing now.


Caddy 启动失败 !

发现 Caddy 配置文件非空，开始追加 ServerStatus 网站配置内容到文件最后...
这该怎么解决》求教

http://xxx.com:80 {
root * /usr/local/ServerStatus/web
encode gzip
file_server
}

cat /tmp/caddy.log

{"level":"info","ts":1634789288.547153,"msg":"using provided configuration","config_file":"/usr/local/caddy/Caddyfile","config_adapter":""}
{"level":"info","ts":1634789288.548829,"logger":"admin","msg":"admin endpoint started","address":"tcp/localhost:2019","enforce_origin":false,"origins":["localhost:2019","[::1]:2019","<IP_ADDRESS>:2019"]}
{"level":"info","ts":1634789288.5490112,"logger":"http","msg":"server is listening only on the HTTP port, so no automatic HTTPS will be applied to this server","server_name":"srv0","http_port":80}
run: loading initial config: loading new config: http app module: start: tcp: listening on :80: listen tcp :80: bind: address already in use

80端口被占用了。
应该是你的VPS本来就有一个Web服务器、Nginx、Apache之类的


Scan the entire org

In a previous version it was possible to scan all the repos within a particular org, does this option still exist?
Thanks

@moshealon76 sorry it does not, I am not supporting github/gitlab integrations. Feel free to use this script https://github.com/zricethezav/gitleaks/issues/312#issuecomment-667128234 if you need to interact with a git provider

@moshealon76 I created a small bash script that does the org scanning, saves individual repo's reports and it can pass any arguments to gitleaks as well, take a look at it here


importing issue

these are errors whats the problem please any one help.
Output log:
Import: Game file 'Bus Simulator Ultimate_v1.3.9_apkpure.com.xapk' has been found
Import: System.InvalidOperationException: Sequence contains no elements
at System.Linq.Enumerable.Max[TSource](IEnumerable1 source)    at uTinyRipper.GameStructure.Export(String exportPath, Func2 filter)
at uTinyRipperGUI.MainWindow.ExportFiles(Object data)
Go to: Create issue

You uses old version of the ripper. Anyway, ripper is not intended to work with xapk files.


Create AS-StealthDefend.yaml

Required items, please complete
Change(s):

Test PR to check validation failures in PR#9333

Validations are passed


Add a method to buffer a request body into memory, and a method to ac…

…cess the request body when it is already buffered.
Part of #789
I didn't implement the corresponding method for non-blocking requests because the situation with futures is a little more complicated, so I didn't see any point investing too much time until the blocking API is sorted out.

Looks like rustfmt has changed as there were a bunch of files that needed reformatting.
@seanmonstar I would like to add full support for reqwests to my HTTP signing crate: https://docs.rs/http-sig/0.2.0/http_sig/index.html - I would be glad to hear if you have any concerns about adding these kinds of methods to Body as I may need to rethink the design of that crate.

Adding as_bytes() seems very reasonable.
I'm curious about the goal of the buffer() method. Could the reader not be inspected before passing it to reqwest? Or is that actually the issue, that you don't have access to reader for some reason?

Constructing the request is outside the control of my request signing crate. The idea is that a prebuilt request is passed to my library, and my library "signs" that request by attaching the appropriate authorization header. I could provide an interface for building requests through my library, but this interface would essentially duplicate the existing reqwest client API, whilst making it harder to add request signing to an existing application.
As part of signing an HTTP request, it may be necessary to compute and attach a Digest header. It is not possible to compute the digest without buffering the entire request body into memory because once we start streaming the request it is no longer possible to send headers. This is simply a limitation of HTTP request signing.

Thanks!


Forms: Different processing for cases with and without Pass parameters.

In BxDolForm::getCleanValue method:
if ($a && isset($a['db']['pass']))
    $oRv = $oChecker->get (**$a['name']**, ...);
else
    $oRv =  $oChecker->get (**$sName**);

It causes problems in Extended Search when search by range is used. In another words the problem appears for inputs with []

Need to track whether the fix affects something or not.


Add support for linting flowtype in javascript

It would be awesome to see support for flowtype.
https://flowtype.org/

I have this working! Going to open a PR later today.

super pumped for this to be merged!

Thanks for this! FWIW ale flow linting errors out on relative imports:
import AccountType from "../../../components/accountType";

$ [flow]  ../../../components/accountType Required module not found [E]

but flow on the CLI does not raise this error.

We probably need to change the command to include the directories the original file came from. This plugin runs linters on temporary files, not the original files, so files can be checked before they are saved back to disk.

Looks like this might be a bigger issue in flow.

Is this something that can be fixed here? Or is it dependent on a fix from Flow?

Including the files can be fixed in the plugin, if Flow supports some way of specifying directories for files to include.

flow doesn't support passing directories to the CLI. the check-contents command was supposed to be a really fast way of "linting" the current file without having to re-run flow entirely. Other vim linters are going about it a different way but users are complaining that its too slow because its running over the whole project.

If there's some change that can be made to the linter to fix those issues, open up a pull request.

Hmm, I was working on using flow-vim-quickfix but I assumed you wouldn't want to accept it as the main flow linter. I just saw https://github.com/w0rp/ale/pull/170 for typescript. Would you accept a PR for a flow-npm linter that does something similar?

I'll accept just about anything which works reasonably well. If it's just a wrapper around an existing executable, I'd prefer to go straight to the flow checker and handle the JSON data in this plugin. Either way, you can always open a pull request. Looking at code is always easier, unless it takes a lot of time to write.

I have eslint-plugin-flowtype installed and configured in my .eslintrc.json file, but colons preceding the types are getting flagged (I think by ESLint). I get the message "Expected ')' to match '(' from line 2 and instead saw ':'." When I run flow and eslint on the file from outside of Vim it doesn't flag an issues. Is there extra configuration I need to do? Here is the code I am editing:
// @flow
function foo(x: number, y) {
   return x * y;
}

foo(5, 6);

If I add the number type to y and the return type like this:
function foo(x: number, y: number): number {

then I get "Unrecoverable syntax error."

I had been using the Syntastic plugin before. It seems the solution to my problem was to remove that plugin.

I should probably do something to detect if another linter plugin is installed and emit a warning.


Make win32 compatible

Any particular reason why this package isn't win32 compatible? I am using this for a project right now that needs to be cross platform, and I just figured out that it's not going to work.

Hmm, I think it was because of mode, umask, owner, group: https://github.com/dwieeb/node-jsondir#attributes
I didn't have any windows system to test on at the time. I might be able to take a look at this in the future.
What happens when you take that thing out in package.json and try it?

@dwieeb Not sure, I'll fork this and give it a try. Thanks for the quick response


Downgrade mongoose to fix compilation issues regarding type instantiation

Issue mentioned here: https://github.com/francescov1/mongoose-tsgen#type-instantiation-is-excessively-deep-and-possibly-infinite

Woot number 100!


make core aware of workspaces

all core actions have to be aware of the current workspace ... sighs, needs some work

done


Error when training saturn

Hi,
I got an error when loading centroids, I used pre-train ESM2/mouse_embedding and human embedding.
Traceback (most recent call last):
  File "../../train-saturn.py", line 1064, in <module>
    trainer(args)
  File "../../train-saturn.py", line 575, in trainer
    centroid_weights.append(torch.tensor(species_genes_scores[sgn]))
KeyError: 'human_ABAT

It seems that some genes were missed in species_genes_scores, so how could I filter genes before using saturn.

Make sure that the input anndatas have all the genes listed in the centroids file.
If you are using different anndatas make sure to change the centroids file argument to something else otherwise it will use whatever file has already been creaeted.

Make sure that the input anndatas have all the genes listed in the centroids file.
If you are using different anndatas make sure to change the centroids file argument to something else otherwise it will use whatever file has already been creaeted.

Thanks, when I create a new Centroids file, it works.


Unmarshalable data behaves poorly

I noticed the following in a few of our event logs:

Original event couldn't be marshalled. Succeeded by stripping the data that uses interface{} type. Please verify that the data you attach to the scope is serializable.

A couple of observations/suggestions (which I'm happy to implement in a PR if desired):

It would be very helpful to include the original error message.  I.e.

	partialMarshallMessage := fmt.Sprintf("Original event couldn't be marshaled: %s. Succeeded by stripping the data " +
		"that uses interface{} type. Please verify that the data you attach to the scope is serializable.", err)

The message seems to indicate that only some data will be stripped, but it strips all Extra data. It would not be difficult (although efficiency would suffer) to loop through each element of Extra, and strip only those that don't marshal.

2 would be far less important if 1 were implemented, to make debugging simpler. But both might be ideal.
Thoughts?

Ugh, sorry for the extraneous closing of this. Applying the patch in #213 to our private repo unintentionally closed this.

Let's do "option 1" first. Thanks for sending PRs for the two variations. I took a chance to try to make the info message more concise and still mention specifically which fields got dropped in #258, replacing #214.
We can ship "option 2" later.


Removed migration script that added createdAt and status fields to applicants collection

Date: 22 Aug 2024

Developer Name: @yeshavyas27

Issue Ticket Number

Closes https://github.com/Real-Dev-Squad/website-backend/issues/2094
Description

This PR removes the migration script that added createdAt and status fields to the applicants collection.
Documentation Updated?

[ ] Yes
[x] No

Under Feature Flag

[ ] Yes
[x] No

Database Changes

[ ] Yes
[x] No

Breaking Changes

[ ] Yes
[x] No

Development Tested?

[x] Yes
[ ] No

Screenshots

Screenshot 1

Test Coverage

Screenshot 1

Additional Notes

@yeshavyas27 #2094 is still open, then what what do you mean by "Closes"

I meant that the mentioned issue will be closed if this PR is merged, indicating that PR is related to that issue. I am sorry if I used the wrong terminology, let me know how I can correct this.
I have added a screenshot under 'Test Coverage'.
By org PR you mean this: https://github.com/Real-Dev-Squad/website-backend/pull/2092  right? I will add that, also can you tell me what was the problem in that PR?

@iamitprakash I meant that the mentioned issue will be closed if this PR is merged, indicating that PR is related to that issue. I am sorry if I used the wrong terminology, let me know how I can correct this.
I have added a screenshot under 'Test Coverage'. By org PR you mean this: #2092 right? I will add that, also can you tell me what was the problem in that PR?

if this PR is in place https://github.com/Real-Dev-Squad/website-backend/pull/2092 do we really need this PR. CC- @vinit717

@yeshavyas27  I will wait for @vinit717  to approve first as he has more context on this

Make two PR's one for removing /batch route and it's code and another for removing /batch/update and it;s code and test


function calls and pipe sending are confusing in terms of order of operations

In the following example, it's not clear whether this bit is saying

Is this "roll a die and put 3 in a pipe" or "roll a die (with the argument 3), then put the answer in a pipe"
It feels like in general where arguments are being provided, there needs to be some visual indication. OR, arguments happen inside a dedicated screen (more like the LED pattern chooser)

The dice with value following as the range is defintely confusing.

This is a known issue with the Kodu paradigm:

data/control generally flows from left to right, except in the case of parameters to functions, where it flows from right to left.

I have another design where you click on the dice and select what upper bound you want, exactly as Jonny mentioned above. The team rejected that design!

replacing by https://github.com/microsoft/microcode/issues/207


Add tests to validated interface methods invoked on modules when they are off

Module interface methods should be unit tested to verify they don't crash if the module if turned off.

with setting v2 work, this may be reduced to none.  Lets revisit as Setting v2 gets more work done and we can investigate afterwards

Moving to 0.19. The main reason is that we are going to make changes to the module interface, so it would be better to wait for those changes, and even if we manage to make those changes in 0.18, there will not be enough time for this work item.

We are moving forward removing modules core functionality from the runner, and simplifying the module interface.
We should still make sure that the current implementation doesn't have bugs when handling turned off module.
Either adding unit tests or functional tests.

@jaimecbernardo would love your thoughts on this given the age.

I'm not sure what these tests would look like with the current architecture.
This feels very outdated now. I'll close it.


[FEATURE REQ] Add reminder on deprecated and non-source-code Azure Spring GitHub repos for relocation

Context
There are multiple GitHub repositories for Spring Cloud Azure libraries including those legacy but deprecated ones, sample repos, doc repos and the active source code repo. Currently we need to collect issues from all those separated repos which is not convenient or efficient.
Goal
Add reminders for developers when they create issues in legacy repos and sample repos to help developers learn that the repo is not the most proper one to file issues in and relocate to our actual source code repo.
Solution
There are 3 solutions we can do to add reminders:

Add reminders in README.md in each repo
Add GitHub actions for reminders
Modify the issue template for reminders.

https://github.com/microsoft/spring-cloud-azure
https://github.com/microsoft/spring-data-cosmosdb

Archived the following repos:

https://github.com/microsoft/azure-spring-boot
https://github.com/microsoft/spring-cloud-azure
https://github.com/microsoft/spring-data-cosmosdb


NonNullable<ConditionalType> can't be assigned to ConditionalType with --strictNullChecks

TypeScript Version<EMAIL_ADDRESS>
Search Terms: Conditional NonNullable Type
Code
type ConditionalType<T> = T extends string ? string : number ;

function ConditionalOrUndefined<T>() : ConditionalType<T> | undefined {
    return 0 as any;
}

function JustConditional<T>() : ConditionalType<T> {
    return ConditionalOrUndefined<T>()!; // Type 'NonNullable<ConditionalType<T>>' is not assignable to type 'ConditionalType<T>'
}

// For comparison...
function genericOrUndefined<T>() : T | undefined {
    return 0 as any;
}

function JustGeneric<T>(): T {
    return genericOrUndefined<T>()!; // no error
}

Expected behavior:
JustConditional compiles without errors, like JustGeneric.
Actual behavior:
JustConditional produces error  Type 'NonNullable<ConditionalType<T>>' is not assignable to type 'ConditionalType<T>'
Playground Link:
https://typescript-play.js.org/?target=2#code/C4TwDgpgBAwg9gOwCYEtgsQQwDYBVwQA8uAfFALxS5QQAewEyAzlE8AE4oIDmUA-Kw5deALigIArgFsARhHZQA3AChlAMwkIAxukSxEqXQhwB5dgFVkENVwhJiJABQBKKGPjI0GY3gIOoAD5QmkjWtkhQAN7KULFQ7BDAEuwIUAAMUJgsmAggKgC+qhraRlAAUhJsHobeOA4ubvqeRjj4kP7RcfGJyanVXljYZpahNgh29c4AhIpQAPRzVARQAOQAcohrEtjYmDLYRP0tvu2kJCtQKCwIcMCZTEwo3Mb70MBwUKCQq0e1J0SkFbKQqqBZQABicAUWjgUjAmE4TEQADpUUVNDpvFBuIx5CgtMMrGMJqQGmJqEEQmFxhFOnEEkkUul7plcgV0SUsRU2ABxXGcLSTclRGL0npMnHjAWE0bhSYzeaLG40djsKHAoA
Related Issues:
It looks like NonNullable has had similar issues with other complex types:
https://github.com/Microsoft/TypeScript/issues/23849
https://github.com/Microsoft/TypeScript/issues/27456

I took a look at this out of curiosity -- it seems like the issue is caused by how conditional types are compared for relationships in structuredTypeRelatedTo. (around line 13022-13053 in src/compiler/checker.ts)
If only the source type is conditional (as in the "for comparison" case in my example code) the compiler tries to determine if the constraint of the source type is related to the target type.
If both types are conditional (as in the other case in my example), then we only consider the types related if all four of the type parameters are related in a specific way, so a "nested" conditional type like this won't necessarily work.
If I remove the "else" on line 13038 so that the "both types are conditional" behavior falls back to the less specific behavior, my problem goes away and the tests still pass, but I haven't investigated whether this naive solution might cause other issues -- perhaps it would be better to widen the acceptable relationships in the earlier branch.
Are you interested in a pull request for this? If so I can add tests and put one together.

@trstamper sorry for the huuuuge delay, but I stumbled back onto this while looking into something else, and ended up opening https://github.com/microsoft/TypeScript/pull/37208 - you were half right, allowing conditionals to be related by constraint was just what was missing; however we did still have to omit the distributive constraint case - since it maps the check type back to its constraint (should it have one), it ends up mucking up variance calculation.


Minimize Window: thread 'main' panicked at 'not enough memory left'

Bevy version
4fecb899aaa33cf2ebc42ac94a32d4b5336c6e93
Operating system & version
Windows 10 19041.572
What you did
cargo run --example sprite

Click the Minimize button
What you expected to happen
Minimize Window
What actually happened
I'm sure there's at least 8G of memory available, but the process exit
    Finished dev [unoptimized + debuginfo] target(s) in 0.30s
    Running `target\debug\examples\sprite.exe`

Nov 20 13:53:39.946  WARN wgpu_core::device: Failed to parse shader SPIR-V code: UnsupportedBuiltIn(4)
Nov 20 13:53:39.949  WARN wgpu_core::device: Shader module will not be validated
thread 'main' panicked at 'not enough memory left', C:\Users\...\wgpu-0.6.0\src\backend\direct.rs:1323:35
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
error: process didn't exit successfully: `target\debug\examples\sprite.exe` (exit code: 101)

Additional information
linux and macOS do not have this problem

Thanks for reporting! This is the same issue as https://github.com/gfx-rs/wgpu-rs/issues/316 in wgpu. Some solutions for dealing with window height of 0 (#170) and minimizing a window were discussed in #545. Leaving this issue open to track window minimizing specifically.

Same thing too happens for me when I minimize the window.
Ran using
cargo +nightly run --example breakout
(Fast builds configured)
Windows 10, current Bevy master (0.4.0+)
Exact same error as #170 .
thread 'main' panicked at 'not enough memory left', C:\Users\xxxx\.cargo\registry\src\github.com-1ecc6299db9ec823\wgpu-0.6.2\src\backend\direct.rs:1355:35
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
error: process didn't exit successfully: `target\debug\examples\breakout.exe` (exit code: 0xc0000005, STATUS_ACCESS_VIOLATION)

Taking a look at this. Seems like this stems from UB with vulkan that wgpu exposes. There is already a fix merged into wgpu https://github.com/gfx-rs/wgpu/pull/1100. I'm trying out an experimental branch where I'll upgrade to the latest wgpu master branch and see if this issue is fixed.

Taking a look at this. Seems like this stems from UB with vulkan that wgpu exposes. There is already a fix merged into wgpu https://github.com/gfx-rs/wgpu/pull/1100. I'm trying out an experimental branch where I'll upgrade to the latest wgpu master branch and see if this issue is fixed.

@maspe36 if it works, just be aware that we can't publish git dependencies to crates.io, which means we can't merge pull requests with git dependencies into the bevy repo. We'd need to wait for a new wgpu release

@maspe36 if it works, just be aware that we can't publish git dependencies to crates.io, which means we can't merge pull requests with git dependencies into the bevy repo. We'd need to wait for a new wgpu release

Yeah good point. It's really less of a fix for this specific issue and more of a WIP branch for the wgpu 0.7 upgrade whenever its released.

Yeah good point. It's really less of a fix for this specific issue and more of a WIP branch for the wgpu 0.7 upgrade whenever its released.

See the changes here https://github.com/bevyengine/bevy/pull/1199
This is part one of fixing this issue, however this cannot be merged until wgpu 0.7 releases. With an upgrade to wgpu, the error is now
wgpu error: Validation Error

Caused by:
    In Device::create_texture
    Dimension X is zero

thread 'main' panicked at 'Handling wgpu errors as fatal by default', C:\Users\Sam\.cargo\git\checkouts\wgpu-rs-40ea39809c03c5d8\3d60546\src\backend\direct.rs:1737:5
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Jan 03 14:12:40.931 ERROR gpu_descriptor::allocator: `DescriptorAllocator` is dropped while some descriptor sets were not deallocated
thread 'main' panicked at 'assertion failed: `(left == right)`
  left: `1`,
 right: `0`: Allocator dropped before all sets were deallocated', C:\Users\Sam\.cargo\git\checkouts\gpu-descriptor-a05b99db0270c787\df74fd8\gpu-descriptor\src\allocator.rs:117:9

And I haven't tested this but I assume it will now panic on linux and macOS. The next step will be handling the error eloquently but I have no idea where to start with that.

See the changes here https://github.com/bevyengine/bevy/pull/1199
This is part one of fixing this issue, however this cannot be merged until wgpu 0.7 releases. With an upgrade to wgpu, the error is now
wgpu error: Validation Error

Caused by:
    In Device::create_texture
    Dimension X is zero

thread 'main' panicked at 'Handling wgpu errors as fatal by default', C:\Users\Sam\.cargo\git\checkouts\wgpu-rs-40ea39809c03c5d8\3d60546\src\backend\direct.rs:1737:5
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Jan 03 14:12:40.931 ERROR gpu_descriptor::allocator: `DescriptorAllocator` is dropped while some descriptor sets were not deallocated
thread 'main' panicked at 'assertion failed: `(left == right)`
  left: `1`,
 right: `0`: Allocator dropped before all sets were deallocated', C:\Users\Sam\.cargo\git\checkouts\gpu-descriptor-a05b99db0270c787\df74fd8\gpu-descriptor\src\allocator.rs:117:9

And I haven't tested this but I assume it will now panic on linux and macOS. The next step will be handling the error eloquently but I have no idea where to start with that.

See the changes here #1199
This is part one of fixing this issue, however this cannot be merged until wgpu 0.7 releases. With an upgrade to wgpu, the error is now
wgpu error: Validation Error

Caused by:
    In Device::create_texture
    Dimension X is zero

thread 'main' panicked at 'Handling wgpu errors as fatal by default', C:\Users\Sam\.cargo\git\checkouts\wgpu-rs-40ea39809c03c5d8\3d60546\src\backend\direct.rs:1737:5
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Jan 03 14:12:40.931 ERROR gpu_descriptor::allocator: `DescriptorAllocator` is dropped while some descriptor sets were not deallocated
thread 'main' panicked at 'assertion failed: `(left == right)`
  left: `1`,
 right: `0`: Allocator dropped before all sets were deallocated', C:\Users\Sam\.cargo\git\checkouts\gpu-descriptor-a05b99db0270c787\df74fd8\gpu-descriptor\src\allocator.rs:117:9

And I haven't tested this but I assume it will now panic on linux and macOS. The next step will be handling the error eloquently but we can't proceed until wgpu is released and upgraded in bevy.

Ran and minimized a Bevy 0.4.0 game on macOS 10.15.7 and after a few minutes the game has not crashed, but hasn't paused execution either.

See the changes here #1199
This is part one of fixing this issue, however this cannot be merged until wgpu 0.7 releases. With an upgrade to wgpu, the error is now
wgpu error: Validation Error

Caused by:
    In Device::create_texture
    Dimension X is zero

thread 'main' panicked at 'Handling wgpu errors as fatal by default', C:\Users\Sam\.cargo\git\checkouts\wgpu-rs-40ea39809c03c5d8\3d60546\src\backend\direct.rs:1737:5
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Jan 03 14:12:40.931 ERROR gpu_descriptor::allocator: `DescriptorAllocator` is dropped while some descriptor sets were not deallocated
thread 'main' panicked at 'assertion failed: `(left == right)`
  left: `1`,
 right: `0`: Allocator dropped before all sets were deallocated', C:\Users\Sam\.cargo\git\checkouts\gpu-descriptor-a05b99db0270c787\df74fd8\gpu-descriptor\src\allocator.rs:117:9

And I haven't tested this but I assume it will now panic on linux and macOS. The next step will be handling the error eloquently but we can't proceed until wgpu is released and upgraded in bevy.

Ran and minimized a Bevy 0.4.0 game on macOS 10.15.7 and after a few minutes the game has not crashed, but hasn't paused execution either.

See the changes here #1199
This is part one of fixing this issue, however this cannot be merged until wgpu 0.7 releases. With an upgrade to wgpu, the error is now
wgpu error: Validation Error

Caused by:
    In Device::create_texture
    Dimension X is zero

thread 'main' panicked at 'Handling wgpu errors as fatal by default', C:\Users\Sam\.cargo\git\checkouts\wgpu-rs-40ea39809c03c5d8\3d60546\src\backend\direct.rs:1737:5
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Jan 03 14:12:40.931 ERROR gpu_descriptor::allocator: `DescriptorAllocator` is dropped while some descriptor sets were not deallocated
thread 'main' panicked at 'assertion failed: `(left == right)`
  left: `1`,
 right: `0`: Allocator dropped before all sets were deallocated', C:\Users\Sam\.cargo\git\checkouts\gpu-descriptor-a05b99db0270c787\df74fd8\gpu-descriptor\src\allocator.rs:117:9

And I haven't tested this but I assume it will now panic on linux and macOS. The next step will be handling the error eloquently but we can't proceed until wgpu is released and upgraded in bevy.

I have exactly the same error :/

wgpu 0.7 is out now, but minimizing on Windows still crashes, but it looks like a different error now?
This is the message I get on Windows:
thread 'main' panicked at 'Error in Device::create_swap_chain: Both `SwapChain` width and height must be non-zero. Wait to recreate the `SwapChain` until the window has non-zero area.', C:\Users\Username\.cargo\registry\src\github.com-1ecc6299db9ec823\wgpu-0.7.1\src\backend\direct.rs:129:9 stack backtrace:
Do we have everything we need to solve this issue now since wgpu 0.7 is out?
I would be happy to test on Linux if that's needed.

Similar/duplicate of #170 #1882 (and a few others)


3 < 10 is false? Value::Addr < Value::Integer PartialOrd mismatching

It seems there is a problem with a Value::Addr() and Value::Integer, as shown in the following example.
$ tokay
Tokay 0.4.0
>>> l = (1,2,3)
>>> l.len
3
>>> a = l.len
>>> a
3
>>> a < 10
false
>>> a > 10
true

This works:
>>> b = 3
>>> b < 10
true
>>> b > 10
false

Reproducing playground https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=74a0441492b4e2ce954ca1eb6ca8412e

Will be resolved by #9


dhcpcd --dumplease without an interface fails to dump all leases

Per the docs, all interfaces should be dumped:

-U, --dumplease [interface]
         Dumps the current lease for the interface to stdout.  If no interface is given then all
        interfaces are dumped.

However, that is not the behavior that I observe:
# pgrep -a dhcpcd
73220 dhcpcd: eth0 [ip4] [ip6]
73221 dhcpcd: [privileged proxy] eth0 [ip4] [ip6]
73222 dhcpcd: [network proxy] eth0 [ip4] [ip6]
73223 dhcpcd: [control proxy] eth0 [ip4] [ip6]
73226 dhcpcd: [DHCP6 proxy] fe80::222:48ff:fe2f:d94
73229 dhcpcd: [BPF ARP] eth0 <IP_ADDRESS>
73240 dhcpcd: [BOOTP proxy] <IP_ADDRESS>
# dhcpcd --dumplease
dhcpcd is not running
# pgrep -a dhcpcd
73220 dhcpcd: eth0 [ip4] [ip6]
73221 dhcpcd: [privileged proxy] eth0 [ip4] [ip6]
73222 dhcpcd: [network proxy] eth0 [ip4] [ip6]
73223 dhcpcd: [control proxy] eth0 [ip4] [ip6]
73226 dhcpcd: [DHCP6 proxy] fe80::222:48ff:fe2f:d94
73229 dhcpcd: [BPF ARP] eth0 <IP_ADDRESS>
73240 dhcpcd: [BOOTP proxy] <IP_ADDRESS>

I haven't dug into why this happens yet, it's not directly a use case of mine but the fact that the documented behavior is broken is relevant to the two fixes I have for https://github.com/NetworkConfiguration/dhcpcd/issues/285 - one fix would break the documented user interface, the other fix would not (but the second fix leaves in place the unreliable "wait on data in the pipe" semantics).

This is because you started dhcpcd on eth0 but didn't limit that in your request to dump leases.
Related to #271


Rails 5 before/after_filter deprecation warnings

The master branch of vanity will throw the following deprecation warnings on a Rails 5.x application.
DEPRECATION WARNING: around_filter is deprecated and will be removed in Rails 5.1. Use around_action instead. (called from use_vanity at /Users/<snip>/.rvm/gems/ruby-2.3.1/bundler/gems/vanity-6d55564d417b/lib/vanity/frameworks/rails.rb:47)
DEPRECATION WARNING: before_filter is deprecated and will be removed in Rails 5.1. Use before_action instead. (called from use_vanity at /Users/<snip>/.rvm/gems/ruby-2.3.1/bundler/gems/vanity-6d55564d417b/lib/vanity/frameworks/rails.rb:48)
DEPRECATION WARNING: before_filter is deprecated and will be removed in Rails 5.1. Use before_action instead. (called from use_vanity at /Users/<snip>/.rvm/gems/ruby-2.3.1/bundler/gems/vanity-6d55564d417b/lib/vanity/frameworks/rails.rb:49)
DEPRECATION WARNING: after_filter is deprecated and will be removed in Rails 5.1. Use after_action instead. (called from use_vanity at /Users/<snip>/.rvm/gems/ruby-2.3.1/bundler/gems/vanity-6d55564d417b/lib/vanity/frameworks/rails.rb:50)

Offending lines are here:
https://github.com/assaf/vanity/blob/master/lib/vanity/frameworks/rails.rb#L47-L50

Is it possible to merge it ASAP? Rails 5.1 is almost ready, It would be awesome to upgrade it soon :-)

Fixed by #326.


Update GLUE URLs (now hosted on FB)

NYU is switching dataset hosting from Google to FB. This PR closes https://github.com/huggingface/datasets/issues/608 and is necessary for https://github.com/jiant-dev/jiant/issues/161. This PR updates the data URLs based on changes made in https://github.com/nyu-mll/jiant/pull/1112.

Thanks for opening this PR :)
We changed the name of the lib from nlp to datasets yesterday.
Could you rebase from master and re-generate the dataset_info.json file to fix the name changes ?

Rebased changes here: https://github.com/huggingface/datasets/pull/626


Need best practice example of how to highlight from separate component

First of all, thank you for this amazing library!
In react app: I'd like to know how to call highlight on pc chart from a react-table or similar 'mouseover' row action.
App has 2 components:

pc chart
a table or grid below

How can the chart register to another component mouseover event. what's the best practice here so both component are not tightly coupled? any idea?

Hi, here's how I approached it.
Suppose your structure is like this:
App
├-> Chart
└-> Table

In your App component, have your app manage state for a highlight:

const [highlightedDataIndex, setHighlightedDataIndex] = useState(null)
// The highlighted data via the table. Just the index, for performance.

In your parcoords chart component, take the getter as a prop:

const Chart = ({ data, highlightedDataIndex }) => { ... }

In your render, highlight as necessary. I'm using something like this:

// Wait for highlighted data, and then highlight it in the chart.
if (highlightedDataIndex !== null) {
  parcoords.highlight([data[highlightedDataIndex]])
} else {
  parcoords.unhighlight()
}

Pass the setter prop to your table, and highlight on hover of a row, for example.
If your IDs start from 1, substract to get the correct ID.
For example, using react-table:

 {
    // id is the id in the table.
    // We do id-1 to get the real value.
    setHighlightedDataIndex(row.values['id'] - 1)
  }}
  onMouseLeave={() => setHighlightedDataIndex(null)}
  {...row.getRowProps()}
>

Note that we pass the ID directly from the data. This ensures that it works even when the rows are filtered.

Thanks! perfect


Add tests for failing evaluation

Keep API of presenting Either<Error, number>
throw EvaluationError from within functions like evaluateExpr()
move those functions inside evaluate to make it clear they shouldn't be used on their own?

Added when I merged evaluation branch.


Use yatf in tests

Current coverage is 97.01% (diff: 100%)

Merging #2 into master will increase coverage by 0.03%

@@             master         #2   diff @@
==========================================
  Files            12         13     +1
  Lines           365        369     +4
  Methods         144        146     +2
  Messages          0          0
  Branches         15         15
==========================================
+ Hits            354        358     +4
  Misses            0          0
  Partials         11         11

Powered by Codecov. Last update a5aea49...e371ec8


BUG: CC0030 should not try to make a pointer const

Fix does not work for 'const' pointers.

@kindermannhubert I agree. We will fix.

@carloscds let's release this on 1.0.1, you can send a PR to the 1.0.x branch.

Closed on dfd5c39


High synk vulnerability. Regular Expression Denial of Service

Questions?
There's a high SYNK vulnerabilty which was introduced through<EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>Bug Report
Environment

Node version: v14.20.0
Kafka-node<EMAIL_ADDRESS>

Should be solved adding   "overrides": {     "snappy": "^7.0.1"   } to your package.json


Please assign me the issue under hacktoberfest 2021

I want to add basic programming concepts in C++. Please assign me this issue.

I'll assign you @SahityaRoy and @sahelisaha2k , but PRs on this repo will not be accepted as a part of Hacktoberfest now. Sorry about that :(
Check the pinned issue to know more


Improvement support rename hive and jdbc engine external table

Currently, if you rename a hive / jdbc engine table, you will be refused:
mysql> use db1; alter table ctp2 rename tp2_orc;
ERROR 1105 (HY000): errCode = 2, detailMessage = Do not support alter HIVE table[ctp2]
Proposed changes
Issue Number: close #xxx
Problem summary
Describe your changes.
Checklist(Required)

Does it affect the original behavior:

[ ] Yes
[x] No
[ ] I don't know

Has unit tests been added:

[ ] Yes
[x] No
[ ] No Need

Has document been added or modified:

[ ] Yes
[x] No
[ ] No Need

Does it need to update dependencies:

[ ] Yes
[x] No

Are there any changes that cannot be rolled back:

[ ] Yes (If Yes, please explain WHY)
[x] No

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 35.11 seconds
load time: 641 seconds
storage size:<PHONE_NUMBER>3 Bytes
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20221223061736_clickbench_pr_67619.html


APEXMALHAR-2011-2012 Avro to Pojo & Pojo to Avro converter

Please review changes for Avro to Pojo conversion & back.
Thanks,
Dev

CI build has failed because of checkstyle errors, can you remove checkstyles error added by these commits. Also avoid not required new lines in the code.

@devtagare In general, please take care of following things:

Make sure travis build passes after the PR is created.
Take care of all the checkstyle violations are taken care of.
Methods other than the lifecycle method & getter/setter should be made only public if required. Otherwise take a best call on whether the method should be private or protected based on possibility of extending.
Please add class level javadoc. This is required so that "@since" tags gets properly added during release cycle.
About unit tests, please have a look at other unit tests in malhar and how they make the operator to go through the lifecycle. If possible it would be great if the test not only checks for process method but also takes operator to whole lifecycle.
For tests, as this is going to contrib, these unit tests won't be run by travis (please correct me if I'm wrong), please make sure that the tests passes in your local machine.

Re-opening, had closed it due to travis build issues.

Re-opening

@devtagare If I remember correctly, all contrib tests are skipped by default. If your tests does not depend on any external system, can only your test be included and exclude everything else for travis?
I see there is includes/excluded/tests parameter of surefire plugin which can control what test to execute. Instead of skipTest=true, can these parameters be used to control which tests to run ?
@tweise Thoughts?

@tweise Creating a tracking Jira... https://issues.apache.org/jira/browse/APEXMALHAR-2038
Will ask on dev for inputs on what all such test are there in their area of work.

The changes looks good to me.
@devtagare Please squash the commits into a single comment.
Will wait for a day after squash for any other comments and then I can merge the changes.

@chinmaykolhatkar @devtagare Did this change pass mvn verify? I see that the checkstyle violation count went up. Changes should not be pushed without running verify, especially when the travis build did not succeed.

Yes, had run mvn verfiy before committing the final changes on the pull
request.All checks had passed.
Thanks,
Dev
On Sat, Apr 2, 2016 at 2:20 PM, Thomas Weise<EMAIL_ADDRESS>wrote:

@chinmaykolhatkar https://github.com/chinmaykolhatkar @devtagare
https://github.com/devtagare Did this change pass mvn verify? I see
that the checkstyle violation count went up. Changes should not be pushed
without running verify, especially when the travis build did not succeed.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/apache/incubator-apex-malhar/pull/211#issuecomment-204806497

Yes.. I checked the same.. Before merging.. I ran travis build command and it passed successfully.


imgMap does not work with complex sprites

Hey there, not sure if we're doing something wrong.
When using a simple texture, or a Sprite.from(TEXTURE), it works great, but if we have a Sprite that contains two sprites, it doesn't render anything for the <key/>:
// For "WASD" layout, returns 'W' on QWERTY/QWERTZ, 'Z' on AZERTY, 'В' on JCUKEN, etc.
//  but could also be bound to another key layout like "ESDF".
const localizedKey = getLocalizedDisplayKey(KeyBind.Jump);

// This is just a plain Sprite with a PIXI.Text inside of it:
const localizedLabelKeySprite = new KeyboardKeySprite( localizedKey );

// In practice the "Press <key/> to jump" would be localized:
const instructionText = new TaggedText('Press <key/> to jump', {
  key: {
    imgSrc: 'keyImg',
    imgDisplay: 'icon',
  }
}, {
  imgMap: {
    keyImg: localizedLabelKeySprite,
  }
});

As a counter-example, showing a plain sprite, a texture or raw asset url works great (but doesn't help with dynamically-configured keys):
  imgMap: {
    keyImg: '/assets/img/ui/input/blank_key.png',
  }

Note: This is not related to #393 (PIXI.BitmapText), this is using plain PIXI.Text / TaggedText.
Would a RenderTexture help? 🤔

For context, this is for showing localized labels like "Press <key> to <action>" for different, user-configured layouts:

Would like to avoid creating spritesheets/hundreds of textures for all the different layouts and languages, given that all the keys would be basically identical 😆

To be honest, I haven't tested this with dynamic sprites. Part of the reason is that I was developing this library based on requests for a specific use case. You have been using it for another use case and it's been showing a bunch of important issues with the library.
When you create a new TaggedText and provide an imgMap, you're actually providing a template for the sprite you want to display. That template is recreated by the library to make as many copies as needed (so you can do like )
The code that clones the sprite is:
// pixiUtils.ts
export const cloneSprite = (sprite: PIXI.Sprite): PIXI.Sprite =>
  new PIXI.Sprite(sprite.texture);

So you can see that I never anticipated the interactive sprites.  😓
I think it should be possible to either rewrite the cloneSprite function or use something like https://pixijs.download/dev/docs/PIXI.Renderer.html#generateTexture . The only real constraint is the sprite would need to have some fixed width and height at the time it's rendered. I presume you'd need to recreate or redraw each time the key label changes too.

Nice, all good!

You have been using it for another use case and it's been showing a bunch of important issues with the library.

It's still the best library out there for what it does do.

I think it should be possible to either rewrite the cloneSprite function

Will do - just wanted to check that it definitely wasn't supported out of the box. I think we can make all our input icons (gamepad button, keyboard keys) fit into some fixed-size container. Will report back!
sitenote, I wonder if it could be as easy as:
export const cloneSprite = (sprite: PIXI.Sprite): PIXI.Sprite =>
  sprite.clone();

(or ...come to think of it, do we need to clone? or is that just for multiple occurrences)

Ignore me, I think I imagined that sprite.clone() exists 😆

Had a quick crack on my lunchbreak and it didn't work first try (boo).
In practice these for us would just be one-liners (no wraparound), so might just glue together raw PIXI.Text.
const TOKEN = "<key>";
const value: string = t("Press <key> to jump"); // translated value

const startMiddleOrEnd = value.startsWith(TOKEN) ? 'start' : value.endsWidth(TOKEN) ? 'end' : 'middle';
const parts = text.split(TOKEN) as [string] | [string, string];

const instruction = new Container();

switch (startMiddleOrEnd) {
  case 'start':
    instruction.addChild(keySprite, makePixiText(parts[0]));
    break;

  case 'end':
    instruction.addChild(makePixiText(parts[0]), keySprite);
    break;

  case 'middle':
    const texts = parts.map(makePixiText);
    instruction.addChild(texts[0], keySprite, texts[1]);
    break;
}

// do layout for instruction.children, etc.


AAPT: error: resource android:attr/lStar not found

I get the following Eraser build issue with the latest Flutter beta release:
FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':eraser:verifyReleaseResources'.
> A failure occurred while executing com.android.build.gradle.tasks.VerifyLibraryResourcesTask$Action
   > Android resource linking failed
     ERROR: /home/luke/Work/click/click_flutter/build/eraser/intermediates/merged_res/release/mergeReleaseResources/values/values.xml:194: AAPT: error: resource android:attr/lStar not found.

OK, I discovered the issue: you have compileSdkVersion 29, but anything under 31 breaks with the latest Flutter:
https://github.com/Wes1324/eraser/blob/3b9ebd9a9bde51844810e6710cd5c884c5ed8e5a/android/build.gradle#L25
I fixed this in my own project by overwriting this value:
allprojects {
    repositories {
        google()
        mavenCentral()
    }
    subprojects {
        afterEvaluate { project ->
            if (project.hasProperty('android')) {
                project.android {
                    // Fix for Eraser issue:
                    compileSdk = 34
                }
            }
        }
    }
}

Thanks for reporting this @lukehutch.
I've merged a PR that should fix this and deployed version 3.0.0 of the package to pub.dev.
GitHub automatically closed your issue because I mentioned it on my PR but please see if the newest version fixes the issue you were seeing. If not, feel free to reopen the issue.
Thanks again!

Thanks for the quick fix, I'm sure that will fix it. I'll wait for your next release to try it.

Glad to hear it @lukehutch. Thanks for retesting


IL-292 - Autotests for module 'Favorite'. Refactor tests for 'Cart'

Task Name:
IL-292: Add Auto-Tests for "Favorites" Feature & Refactor Cart Tests
Developer:
Tetiana Perinha
Changes:
Develop automated tests to cover the "Favorites" feature.
Add an assertion method and an API method specific to testing the "Favorites" functionality.
Refactor existing tests and methods related to the "Cart".

More tests need test data to be committed to the repo:

==================================================================================== ERRORS ====================================================================================
_________________________________________________________ ERROR collecting tests/authentication/test_authentication.py _________________________________________________________
ImportError while importing test module '/Users/astriganova/Desktop/Projects/forks/Online-Store-QA/tests/authentication/test_authentication.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
/Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.9/lib/python3.9/importlib/__init__.py:127: in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
tests/authentication/test_authentication.py:6: in <module>
    from configs import firstName, lastName, password, email, email_iced_late, imap_server, email_address_to_connect, \
E   ImportError: cannot import name 'firstName' from 'configs' (/Users/astriganova/Desktop/Projects/forks/Online-Store-QA/configs.py)
______________________________________________________ ERROR collecting tests/registration/test_confirm_email_negative.py ______________________________________________________
ImportError while importing test module '/Users/astriganova/Desktop/Projects/forks/Online-Store-QA/tests/registration/test_confirm_email_negative.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
/Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.9/lib/python3.9/importlib/__init__.py:127: in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
tests/registration/test_confirm_email_negative.py:5: in <module>
    from configs import firstName, lastName, password, email, imap_server, email_address_to_connect, gmail_password, \
E   ImportError: cannot import name 'firstName' from 'configs' (/Users/astriganova/Desktop/Projects/forks/Online-Store-QA/configs.py)
_____________________________________________________ ERROR collecting tests/registration/test_registration_with_email.py ______________________________________________________
ImportError while importing test module '/Users/astriganova/Desktop/Projects/forks/Online-Store-QA/tests/registration/test_registration_with_email.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
/Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.9/lib/python3.9/importlib/__init__.py:127: in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
tests/registration/test_registration_with_email.py:5: in <module>
    from configs import gmail_password, imap_server, email_address_to_connect, DB_NAME, HOST_DB, PORT_DB, DB_USER, DB_PASS
E   ImportError: cannot import name 'gmail_password' from 'configs' (/Users/astriganova/Desktop/Projects/forks/Online-Store-QA/configs.py)
=============================================================================== warnings summary ===============================================================================
venv/lib/python3.9/site-packages/urllib3/__init__.py:34
  /Users/astriganova/Desktop/Projects/forks/Online-Store-QA/venv/lib/python3.9/site-packages/urllib3/__init__.py:34: NotOpenSSLWarning: urllib3 v2.0 only supports OpenSSL 1.1.1+, currently the 'ssl' module is compiled with 'LibreSSL 2.8.3'. See: https://github.com/urllib3/urllib3/issues/3020
    warnings.warn(

framework/tools/class_email.py:44
  /Users/astriganova/Desktop/Projects/forks/Online-Store-QA/framework/tools/class_email.py:44: DeprecationWarning: invalid escape sequence \d
    pattern = "\d{3}-\d{3}-\d{3}"

-- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
=========================================================================== short test summary info ============================================================================
ERROR tests/authentication/test_authentication.py
ERROR tests/registration/test_confirm_email_negative.py
ERROR tests/registration/test_registration_with_email.py
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Interrupted: 3 errors during collection !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
======================================================================== 2 warnings, 3 errors in 0.12s =========================================================================
(

Discussed in 1-1: no opportunity to make these tests independent from Tanya's mail at the moment, imports will be fixed separately.


Error related to 'flagfile' has been occuring for IMU-Vehicle calibration.

Hello.
I'm trying to calibrate IMU to Vehicle for autonomous driving in RTK mode.
But the IMU to Vehicle calibration program has been exiting with an error message.
Is this related to docker or something else?
The program is not revealed so that I can't know what this error means.
System information

OS Platform and Distribution (e.g., Linux Ubuntu 14.04): Linux Ubuntu 14.04
Apollo installed from (source or binary): source
Apollo version (1.0, 1.5, 2.0, 2.5, 3.0): 3.0

Steps to reproduce the issue:

dev_into
/apollo$ ./scripts/bootstrap.sh
Enable GPS, CAN bus and Localization in RTK mode.
Check odometory topic.
Downloads https://apollocache.blob.core.windows.net/apollo-cache/imu_car_calibrator.zip
Symbolic link *.so files the program needs.
/apollo$ ./scripts/sensor_calibration.sh imu_vehicle

Supporting materials (screenshots, command lines, code/script snippets):

Error Message : "ERROR: flag 'flagfile' was defined more than once (in files '/home/tmp/gflags-2.2.0/src/gflags.cc' and '/tmp/gflags-2.2.0/src/gflags.cc')."
Even there are no /home/tmp/gflags-2.2.0/ directory and /tmp/gflags-2.2.0/ directory. I was able to find /home/tmp/gflags-2.2.0.tar.gz file only.

When I input the command: bash sensor_calibration.sh lidar_camera
There is the same error as you provided, have you solve the problem?

@pkh0104 @weidezhang @natashadsouza

I am having a similar problem for lidar-camera calibrator, specifically, the error message is
ERROR: something wrong with flag 'flagfile' in file '/tmp/gflags-2.2.0/src/gflags.cc'.  One possibility: file '/tmp/gflags-2.2.0/src/gflags.cc' is being linked both statically and dynamically into this executable.
I'm not sure how to debug this, any help is appreciated

Thank you for your comment.
But I still have the problem after reinstalling entire system(IPC).
By the way, I wrote wrong Apollo version. Apollo version which I'am using is not 3.0 but 3.x that I pulled from master branch on mid October.
At that time, The version of docker image was changed to dev-x86_64-20180906_2002.
Can that change cause this problem by any chance?

@pkh0104 have you tried pulling from the latest branch? Please try that and let me know if you still see an error. Thank you for your interest in Apollo

I am having a similar problem for lidar-camera calibrator, specifically, the error message is
ERROR: something wrong with flag 'flagfile' in file '/tmp/gflags-2.2.0/src/gflags.cc'. One possibility: file '/tmp/gflags-2.2.0/src/gflags.cc' is being linked both statically and dynamically into this executable.
I'm not sure how to debug this, any help is appreciated

@tkkhuu please try the suggestion recommended above: "purge all gflags and install apollo again." Let me know if you still see an issue post that. Thanks!

Hello.
I'm trying to calibrate IMU to Vehicle for autonomous driving in RTK mode.
But the IMU to Vehicle calibration program has been exiting with an error message.
Is this related to docker or something else?
The program is not revealed so that I can't know what this error means.
System information

OS Platform and Distribution (e.g., Linux Ubuntu 14.04): Linux Ubuntu 14.04
Apollo installed from (source or binary): source
Apollo version (1.0, 1.5, 2.0, 2.5, 3.0): 3.0

Steps to reproduce the issue:

dev_into
/apollo$ ./scripts/bootstrap.sh
Enable GPS, CAN bus and Localization in RTK mode.
Check odometory topic.
Downloads https://apollocache.blob.core.windows.net/apollo-cache/imu_car_calibrator.zip
Symbolic link *.so files the program needs.
/apollo$ ./scripts/sensor_calibration.sh imu_vehicle

Supporting materials (screenshots, command lines, code/script snippets):

Error Message : "ERROR: flag 'flagfile' was defined more than once (in files '/home/tmp/gflags-2.2.0/src/gflags.cc' and '/tmp/gflags-2.2.0/src/gflags.cc')."
Even there are no /home/tmp/gflags-2.2.0/ directory and /tmp/gflags-2.2.0/ directory. I was able to find /home/tmp/gflags-2.2.0.tar.gz file only.

hello,i canot download the calibration tool with the url:https://apollocache.blob.core.windows.net/apollo-cache/imu_car_calibrator.zip.Can you send me one copy?Thanks!

Closed due to inactivity. If the problem persists, pls feel free to reopen it or create a new one and refer to it.


node.js >16.13

Describe the bug
Can't update other adapter while using node.js > 16.13
pi@raspberrypi:/opt/iobroker $ npm install<EMAIL_ADDRESS>npm ERR! code EBADENGINE
npm ERR! engine Unsupported engine
npm ERR! engine Not compatible with your version of node/npm<EMAIL_ADDRESS>npm ERR! notsup Not compatible with your version of node/npm<EMAIL_ADDRESS>npm ERR! notsup Required: {"node":"^12.19.0 || ^14.15.0 || ^16.13.0"}
npm ERR! notsup Actual:   {"npm":"9.6.7","node":"v18.17.0"}
npm ERR! A complete log of this run can be found in: /home/iobroker/.npm/_logs/2023-08-01T11_33_42_577Z-debug-0.log

Please install Github version for now, after that potentially restart and reload admin to create instance (if not already there)


Constant values in Expr mult and div

Hello,
So Expr.__mult__ check if the input is a number using _is_number, but Expr.__div__ calls buildGenExprObj which check if the object is a number using python builtin isinstance:
https://github.com/SCIP-Interfaces/PySCIPOpt/blob/910beeb4b770519c55ec25538258bc3a077bb369/src/pyscipopt/expr.pxi#L115
_is_number tries to convert the object to a float and catches the eventual error.
_is_number is actually more general than isinstance, because it will also catch all the numpy types (np.int, np.float, np.float32...) as numbers.
Is it possible to replace the call to isinstance(int) or isinstance(float) with _is_number?
Thanks

Sure! That sounds very reasonable. I am happy to accept your pull request 😃


About quantize.

Thank you for open this repo. Recommend add int8 model fps and acc in readme.

Thanks for your advise, it will be taken into our update schedule

great


can't distinguish between responses with the same (void) schema

What version of Effect is running?
"@effect/platform": "^0.69.25",

What steps can reproduce the bug?
I add endpoint:
    HttpApiEndpoint.get('home', '/')
      .addSuccess(HttpApiSchema.Created)
      .addSuccess(HttpApiSchema.NoContent)

implement it:
.handle('home', () => Effect.succeed(null)

What is the expected behavior?
I should have an option to return something different to trigger the no content response.
What do you see instead?
The handler always returns the Created status
Additional information
I can do some workaround to make it work,

Either I can make the second response to be error response and then use Effect.fail
Or I can add a distinguishable schema to each response, so the result of handler can be dispatched to the correct status code

To allow for multiple empty responses on an endpoint you first have to create a discriminated union to distinguish between the different response types, then "cast" them to empty responses:
import {
  HttpApi,
  HttpApiBuilder,
  HttpApiEndpoint,
  HttpApiGroup,
  HttpApiScalar,
  HttpApiSchema,
  HttpServer
} from "@effect/platform"
import { NodeHttpServer, NodeRuntime } from "@effect/platform-node"
import { Effect, Layer, Schema } from "effect"
import { createServer } from "http"

class NoContent extends Schema.TaggedClass<NoContent>()("NoContent", {}) {}

class ImATeapot extends Schema.TaggedClass<ImATeapot>()("ImATeapot", {}) {}

class EmptyApi extends HttpApiGroup.make("empty").add(
  HttpApiEndpoint.get("no-content", "/no-content")
    .addSuccess(NoContent.pipe(HttpApiSchema.asEmpty({
      status: 204,
      decode: () => new NoContent()
    })))
    .addSuccess(ImATeapot.pipe(HttpApiSchema.asEmpty({
      status: 418,
      decode: () => new ImATeapot()
    })))
) {}

class TopLevelApi extends HttpApi.empty.add(EmptyApi) {}

const EmptyApiLive = HttpApiBuilder.group(
  TopLevelApi,
  "empty",
  (handlers) => handlers.handle("no-content", () => Effect.succeed(new ImATeapot()))
)

const ApiLive = HttpApiBuilder.api(TopLevelApi).pipe(
  Layer.provide(EmptyApiLive)
)

HttpApiBuilder.serve().pipe(
  HttpServer.withLogAddress,
  Layer.provide(HttpApiScalar.layer()),
  Layer.provide(ApiLive),
  Layer.provide(NodeHttpServer.layer(createServer, { port: 3000 })),
  Layer.launch,
  NodeRuntime.runMain
)

You have to explicitly specify what the status code will rehydrate to.
With the recently added predefined error types in the HttpApiError module it is easier to accomplish now.


Provide short term solution for array "star" substitution

We want to eventually just use JSONPath for variable expansion but in the short-term we should just add an extra star expansion for array types for our string-prefix based expansion. e.g. params.myarray will cause the create "both" a params.myarray and params.myarray[*] map key for ApplyArrayReplacements and the various validate methods.
This will let us update our tests to use the star-expansion in advance of jsonpath support.

/assign

/kind feature


add adblocking per whitelist

this blocks the connections to following hosts, even happening with a payed account:

braze.com
segment.com
facebook.com
googletagmanager.com
cdn-apple.com
sentry.io

Hi, thanks!
This is a really good addition, I will hopefully test it out soon and get it merged before the release of a new version.

So, we can't block all of these, some of them are also required for the social logins, I trust Deezer doesn't share their data with Facebook, Google and Apple in a straight way. I do know they use sentry and now thanks to you I know they also use some other stuff. I'm totally fine with blocking user tracking and ads, however blocking socials is a no go for me, therefore included a little bit more, feel free to explore and make them more restricted.