Failed to initialize php language server on win10

Win10 x64
Sublime 3156
LSP commit c9d0fd4bdb5e947d2619b183802a91e30c121751
PHP 7.1.5 (cli)
felixfbecker/language-server： v5.3.4
The console does not provide enough information, even though I have set the all log_* to true in the settings.
Here are my settings and logs, hope it can help you diagnose the problem.
LSP.sublime-settings
{
	"auto_show_diagnostics_panel": false,
	"clients":
	{
		"phpls":
		{
			"command":
			[
				"php",
				"-d",
				"memory_limit=4096M",
				"C:\\Users\\me\\.vscode\\extensions\\felixfbecker.php-intellisense-2.2.5\\vendor\\felixfbecker\\language-server\\bin\\php-language-server.php"
			],
			"enabled": true,
			"languageId": "php",
			"scopes":
			[
				"source.php",
				"embedding.php"
			],
			"syntaxes":
			[
				"Packages/PHP/PHP.sublime-syntax"
			]
		}
	},
	"complete_all_chars": true,
	"completion_hint_type": "detail",
	"diagnostics_gutter_marker": "dot",
	"diagnostics_highlight_style": "underline",
	"log_debug": true,
	"log_stderr": true,
	"log_payloads": true,
	"log_server": true,
	"only_show_lsp_completions": false,
	"resolve_completion_for_snippets": true,
	"show_diagnostics_in_view_status": false,
	"show_diagnostics_phantoms": true,
	"show_status_messages": true,
	"show_view_status": true
}

Console output
...
LSP: global clients: phpls=True
LSP: starting active= C:\Users\me\Workspace\NuPoint\NuPoint - PHP\app\Http\Controllers\APIv1\OrderController.php other= 0
LSP: starting in C:\Users\me\Workspace\NuPoint\NuPoint - PHP
LSP: starting ['php', '-d', 'memory_limit=4096M', 'C:\\Users\\me\\.vscode\\extensions\\felixfbecker.php-intellisense-2.2.5\\vendor\\felixfbecker\\language-server\\bin\\php-language-server.php']
LSP:  --> initialize
lang_service_enabled: True
LSP: LSP stderr process ended.
LSP: LSP stdout process ended.
...

When I open a .php file and try to hover on code
LSP: Already starting on this window: phpls
LSP: phpls not available for view C:\Users\me\Workspace\Demo\Demo - LSP\index.php in window 2
LSP: Already starting on this window: phpls

composer.json
{
    "minimum-stability": "dev",
    "prefer-stable": true,
    "require": {
        "felixfbecker/language-server": "v5.3.4"
    },
    "scripts": {
        "parse-stubs": "LanguageServer\\ComposerScripts::parseStubs",
        "post-update-cmd": "@parse-stubs",
        "post-install-cmd": "@parse-stubs"
    }
}

TCP support is now merged into master, I tested the php language server with these settings:
"phpls":
		{
			"command": [
				"php",
				"~/vendor/felixfbecker/language-server/bin/php-language-server.php",
				"--tcp-server=<IP_ADDRESS>:5555"
			],
			"enabled": true,
			"tcp_port": 5555
		}

Can you let me know if it works for you?

Closing this as we got the language server on Windows via TCP in #151. There are some helpful troubleshooting tips there, too!


Add sparql.timeout vars to Marmotta

Add sparql.timeout.type and sparql.timeout.description to system-meta.properties.

I think we also need to add sparql.timeout = 360 to system-config.properties, based upon what's on marmotta-prod1.

@anarchivist: OK, just added that.


Malformed input results in crash

If you input with bad data, such as the following:
curl -X POST -H "Content-Type: text/plain" -d "[process:pid2 <= 5]" http://<IP_ADDRESS>:5000/car-elastic
It will crash with an unhandled exception

This also raises an exception if you run it directly:
translate-stix-pattern --output-language splunk --output-data-model cim "[process:pid2 <= 5]"

We should consider where we want to raise exceptions and where we want to return error conditions as a simple return value.


Add onException() attribute to caching annotations.

CachePut, CacheRemoveAll and CacheRemoveEntry all have an afterInvocation() boolean attribute which is doc'ed to behave as follows:
/**
 * (Optional) When {@link javax.cache.Cache#put(Object, Object)} should be
 * called. If true it is called after the annotated method invocation completes
 * successfully. If false it is called before the annotated method is invoked.
 *

 * Defaults to true.
 *

 * If true and the annotated method throws an exception the put will not be executed.
 */
@Nonbinding
boolean afterInvocation() default true;

This attribute seems to be driving two different forms of behavior:

Whether the operation happens before or after the method body is executed.
Whether the operation happens when the method returns abnormally.

It seem thats these two decisions should be independent, i.e. there may be some circumstances where I want the operation to occur in a finally block.  That would suggest we should have two attributes:
boolean afterInvocation() default true;
boolean onException() default false;

It is not clear to me what the use case would be for onException. The intention of annotations is to be a useful subset of the Cache API not an exhaustive one.
Now Ehcache has the concept of a CacheExceptionHandler the contents of which are reproduced below:
public interface CacheExceptionHandler {
/**
 * Called if an Exception occurs in a Cache method. This method is not called
 * if an Error occurs.
 *
 * @param ehcache   the cache in which the Exception occurred
 * @param key       the key used in the operation, or null if the operation does not use a key or the key was null
 * @param exception the Exception caught.
 */
void onException(Ehcache ehcache, Object key, Exception exception);

}
This was driven by one particular company that wanted it but is so rarely used we have not even thought of adding an ExceptionHandler to 107. So given that I don't think we should be defining an onException annotation. And if we did it would call an ExceptionHandler rather than a cache operation.
So I think we skip the onException. Now we do need to state that an afterInvocation annotation is not processed if an exception is thrown. But I checked and we have already done that.
So I propose closing this issue.

This isn't about exception handling. It is about if the remove or removeAll actions should still be executed if the annotated method throws an exception.

Yes, I realise that. And the Javadoc states that we don't execute after an exception.
I don't see why we would want to continue with a post method body cache operation so I don't see the need for the annotation.
On 03/12/2011, at 2:43 AM, edalquist wrote:

This isn't about exception handling. It is about if the remove or removeAll actions should still be executed if the annotated method throws an exception.

Reply to this email directly or view it on GitHub:
https://github.com/jsr107/jsr107spec/issues/46#issuecomment-2992443

Regards
Greg Luck
web: http://gregluck.com
skype: gregrluck
yahoo: gregrluck
mobile: +61 408 061 622

I don't know about Eric, but the kind of use-case I was thinking of here was a cache invalidation situation.
A method that performs a mutative operation on the entity we are caching terminates abnormally.  We may either know that the entity is definitively mutated or we're not sure, but in either case we know that the correct course of action is to invalidate the cache entry for the given key anyway.

So that would only apply to @Remove right? Because you don't know what the value would be if an exception is thrown.
Eric has this use case ever actually come up?
On 06/12/2011, at 7:18 AM, Chris Dennis wrote:

I don't know about Eric, but the kind of use-case I was thinking of here was a cache invalidation situation.
A method that performs a mutative operation on the entity we are caching terminates abnormally.  We may either know that the entity is definitively mutated or we're not sure, but in either case we know that the correct course of action is to invalidate the cache entry for the given key anyway.

Reply to this email directly or view it on GitHub:
https://github.com/jsr107/jsr107spec/issues/46#issuecomment-3023529

Regards
Greg Luck
web: http://gregluck.com
skype: gregrluck
yahoo: gregrluck
mobile: +61 408 061 622

Yes the argument for this is much stronger on @CacheRemoveEntry and @CacheRemoveAll.
There is also a slight (imho) inconsistency in that @CachePut(afterInvocation=false) and @CachePut(afterInvocation=false) behave differently with regard to exceptions.  Since invocation beforehand implies that the put will occur regardless of the method result it's impossible currently to have this always put behavior and have the cache updated after the operation.

Cannot parse " it's impossible currently to have this always put behavior and have the cache updated after the operation" Can you please restate.
On 06/12/2011, at 8:20 AM, Chris Dennis wrote:

Yes the argument for this is much stronger on @CacheRemoveEntry and @CacheRemoveAll.
There is also a slight (imho) inconsistency in that @CachePut(afterInvocation=false) and @CachePut(afterInvocation=false) behave differently with regard to exceptions.  Since invocation beforehand implies that the put will occur regardless of the method result it's impossible currently to have this always put behavior and have the cache updated after the operation.

Reply to this email directly or view it on GitHub:
https://github.com/jsr107/jsr107spec/issues/46#issuecomment-3024454

Regards
Greg Luck
web: http://gregluck.com
skype: gregrluck
yahoo: gregrluck
mobile: +61 408 061 622

I mean current you cannot have both:

always put behavior (put for both normal and abnormal termination)
put happening after the operation

I believe @CacheResult would have similar semantics as @CacheRemoveEntry and @CacheRemoveAll with slightly different wording. The same changes to the javadoc for afterInvocation would be needed:
    /**
     * Defines zero (0) or more exception {@link Class classes}, which must be a
     * subclass of {@link Throwable}, indicating which exception types must cause
     * a the parameter to be cached.
     */
    Class<? extends Throwable>[] cacheFor() default {};

    /**
     * Defines zero (0) or more exception {@link Class Classes}, which must be a
     * subclass of {@link Throwable}, indicating which exception types must not
     * cause the parameter to be cached.
     */
    Class<? extends Throwable>[] noCacheFor() default {};

For @CacheResult the behavior is different is there is only a value to cache if an exception is thrown. What I believe is required for robust exception handling is the addition of the ability to cache exceptions.
    /**
    * (Optional) name of the cache to cache exceptions.
    *

    * If not specified defaults first to {@link CacheDefaults#exceptionCacheName()} and if that
    * is not specified no exception caching is done.
    */
    @Nonbinding
    String exceptionCacheName() default "";

    /**
     * Defines zero (0) or more exception {@link Class classes}, which must be a
     * subclass of {@link Throwable}, indicating which exception types which must
     * be cached. Only effective if {@link #exceptionCacheName()} or
     * {@link CacheDefaults#exceptionCacheName()} are specified.
     */
    Class<? extends Throwable>[] cachedExceptions() default {};

    /**
     * Defines zero (0) or more exception {@link Class Classes}, which must be a
     * subclass of {@link Throwable}, indicating which exception types must not
     * be cached. Only effective if {@link #exceptionCacheName()} or
     * {@link CacheDefaults#exceptionCacheName()} are specified.
     */
    Class<? extends Throwable>[] nonCachedExceptions() default {};

Note that this modification would also require some minor modifications to CacheResolver and CacheKeyGenerator

So we have 3 changesets here dealing with exception handling. In my view we either do all or none. I strongly advocate for doing all three changes. The ability to sanely deal with exceptions when using annotations is quite valuable and a highly requested/used feature in our existing cache annotations library.

I tried using the @CacheResult on top of an cache that was decorated under the covers with an ehcache blocking cache.
For my specific case I need to put an entry into the cache every time I do a get on a key (even if the method invocation fails) or the lock on that stripe in the blocking cache will never be released. I've thought about a few ways of handling this - and they go along pretty closely with these thoughts on exception handling.
Introducing a special null object placeholder object that could be put into the cache by the annotations would help handle caching methods that return null. Allowing the annotations to specify on @CachePut or @CacheResult to indicate that null responses should be remembered and not retried - and using the placeholder null value.
Since the annotations are effectively memoizing the method they are around - and null is a valid response from a method - using a null placeholder object in the annotation processing seems like a proper way to represent that the method has been checked and the result is null.
I'd also argue that this should be enabled by default and a user should have to request to disable caching null responses of method calls.
In the RI it could look something like this:
    if (!cacheResultAnnotation.skipGet()) {
	    //Look in cache for existing data
        result = cache.get(cacheKey);
        if (result != null) {
            //Cache hit, return result
            if (result == nullPlaceHolder) {
                 return null;
            }
            else {
                return result;
            }
        }
    }

    //Call the annotated method
    try {
          result = this.proceed(invocation);
    } catch (Exception e) {
         // if enabled, could do the exception handling stuff here
         if (cacheNullResults) {
              result = nullPlaceHolder;
         }
    }
    if (result != null) {
        cache.put(cacheKey, result);
    }

    return result;

The above example is pretty crude - but I think being able to cache nulls is something to consider - and being able to cache nulls when exceptions are thrown is also a valid thing to consider.

Ryan can you please split the null issue into its own

+1 to do all of Eric's proposed changes.

+1 to Eric's changes provided that they are implementable in a short time

They are, I have existing code to support all of these features that I can pull from ehcache-spring-annotations. I'm on vacation until the 14th but I'll spend a night or two once I'm back at work and get this implemented.
Ryan, as for your self-populating/blocking issue that might be handy to chat about directly via email about the behavior you're seeing. Ehcache-spring-annotations provides a selfPopulating flag for @Cachable which I personally use quite a bit and I don't believe we've had problems due to null return values, I'd have to double check though.

Ok, we have a plan. Let's close this.


Coveralls coverage for DDC is broken

The tag here points into the unknown:
https://github.com/dart-lang/sdk/blob/master/pkg/dev_compiler/README.md
Broke during the migration from the old github repo.
@kevmoo

[ ] Enable coveralls for sdk repo
[ ] Add coveralls private token to travis environment for sdk
[ ] Verify that it works

@vsmenon
See https://travis-ci.org/dart-lang/sdk/jobs/170102200#L519
Looks like we need to update the coverage script?

we're not using travis for DDC anymore


"The window is not responding" should disappear when the condition is not met anymore

This window should disappear as soon as vscode respondes again.

This is pretty old, please report with more info if you see it again


Adds more support for React specific JSX

Hi 👋🏻 @steve8708 thanks for this amazing project — I've been thinking about doing something like this for while.
I'm working on migrating a React codebase to Svelte and found there were a few things missing in the JSX parser. I hope this contribution makes sense.

Thanks for sending @ivanvanderbyl ! I am away from work this week but will take a look when I'm back next week

looks great @ivanvanderbyl! looks like I had to approve the workflow run and the only thing that appears to not pass is prettier lint https://github.com/BuilderIO/jsx-lite/pull/108/checks?check_run_id=3050027708
try running
npm run fmt:prettier

from the project root and pushing up the update, should be good to merge then 👍

hey @ivanvanderbyl - just wanted to follow up here. would love to get this PR in!

hey @ivanvanderbyl - just wanted to try pinging you one more time! otherwise sadly may need to close this out to keep our PRs clean, but would love to get this in. lmk if my suggestion above was unclear too or you could use help with the final update(s)

closing out due to inactivity to keep our PR list clean, please feel free to reopen @ivanvanderbyl if you'd like to continue on this


failed to build dependency on mac m1

There were erroros when i executed "mvn clean package" on my mac.

Enviroment:

Maven 3.9.2
JDK <IP_ADDRESS>
Python 3.9.12
mac infomation: arm64/Darwin Kernel Version 20.5.0

Is there any idea to solve this problem?

Hi @gsalmh
Apologies for not replying sooner. I received no notification of the issue, so it slipped my notice. Judging by the output, I think this is an issue resulting from the dynamic library being built for the incorrect architecture. I only tested this on older Macs, so I was not aware that M1 had these problems.
While I don't have my computer with me (in a plane awaiting takeoff), I can make an educated guess on what you could try. Edit the arguments section of the build-shared-object-library-macos execution in pom.xml to include:
<arguments>
  <!-- existing args -->
  <argument>-a</argument>
  <argument>arch64</argument>
</arguments>

Let me know if it works after that.


Bug: Incomplete Conversation Retrieval from SDK (Limit: 102 Conversations)

Describe the bug
I am currently experiencing a limitation with the SDK where it only returns a maximum of 102 conversations from my wallet, despite having around 200 conversations in my wallet.
Expected behavior
No response
Steps to reproduce the bug
No response

We recently fixed this bug in android https://github.com/xmtp/xmtp-android/pull/74/files it should be a simple fix from the query method to a batch envelopes method.
So in this code we should no longer be calling query
https://github.com/xmtp/xmtp-flutter/blob/main/lib/src/conversation/conversation_v2.dart#L93-L101
Instead it should look something like
var listing = await api.client.envelopes(xmtp.QueryRequest(
      contentTopics: [Topic.userInvite(_me.hex)],
      startTimeNs: start?.toNs64(),
      endTimeNs: end?.toNs64(),
      pagingInfo: xmtp.PagingInfo(
        limit: limit,
        direction: sort,
      ),
    ));

It's possible an envelopes method on the client doesn't exist yet and if thats the case you'll need to write something like this https://github.com/xmtp/xmtp-android/blob/main/library/src/main/java/org/xmtp/android/library/ApiClient.kt#L125-L136 to iterate through all the pages and return all the envelopes (conversations).


Integration tests

Added some integration tests for google-cloud-logging and google-cloud-error_reporting. They actually use gcloud SDK to push the a test sinatra application to GAE or GKE, then run tests against the deployed application.
To invoke the integration tests, run:
.../google-cloud-ruby$ bundle exec rake integration:gae
.../google-cloud-ruby$ bundle exec rake integration:gke

I also refactored the Rakefiles a little bit to get rid of some of the empty rake tasks in subdirectories.

@dazuma please review

@hxiong388 Do you want to add a high-level discussion somewhere of when, where, and by whom these new tests are intended to be used, possibly differentiating them from the existing acceptance tests in google-cloud-ruby?

@quartzmo For some reason I have the impression we've already had some high level plan discussion regarding these integration tests. I will send you guys an email with details of our plan, then we can go from there.

@hxiong388 I mean purely for the benefit of the public! So that a user or potential contributor is aware of their value and is encouraged to make use of them. Feel free to save this for later, I was just wondering.

Maybe just a sentence or two in appropriate README(s).

@quartzmo I was planning to document these integration tests in CONTRIBUTING.md in the next revision when I add more thorough tests. This first revision is my attempt to create a template and proof of concept.
I can add a section in CONTRIBUTNG.md right now while I'm making the change to Rakefile.

@hxiong388 Either way, sounds good! Can you remove the stackdriver additions to jsondoc:umbrella? Otherwise rebasing my current work will be painful!

@quartzmo Sorry it took me a while to make the update. Have been busy this afternoon. Please let me know if find anything else.

I'll merge this soon, unless @blowmage has any comment.


chore: split NadaType and NadaValue / refactoring

Fixes #
Design discussion issue (if applicable) #
Changes
Please provide a brief description of the changes here.
Merge requirement checklist

[ ] CONTRIBUTING guidelines followed
[ ] Unit tests added/updated (if applicable)
[ ] Backwards compatibility analysis completed (if applicable). "Will this change require recompilation and upload of user programs?"

I was taking a look at the PR and I'm confused. What is a NadaValue at the compiling level exactly? IMO NadaValue should exist only at the runtime level, right?

In this context a NadaValue is what you would pass to Tuple.new for instance: PublicInteger or Array. A NadaType would be PublicIntegerType or ArrayType. The two are currently mixed in the code, which creates some confusion.

I was taking a look at the PR and I'm confused. What is a NadaValue at the compiling level exactly? IMO NadaValue should exist only at the runtime level, right?

In this context a NadaValue is what you would pass to Tuple.new for instance: PublicInteger or Array. A NadaType would be PublicIntegerType or ArrayType. The two are currently mixed in the code, which creates some confusion.

Maybe I am wrong, but IMO in this context you are not using a NadaValue. PublicInteger and Array are the types for the future values you will assign in the runtime and PublicIntegerType and ArrayType are the type definitions something like a metatype and they only live in Python because we need to get the type properties.

https://github.com/NillionNetwork/nillion/pull/2403 will need to be merged first.


Increases max size of ingestor routers.

Codecov Report

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

@@            Coverage Diff            @@
##             master     #223   +/-   ##
=========================================
  Coverage          ?   92.69%
=========================================
  Files             ?      136
  Lines             ?     2424
  Branches          ?      128
=========================================
  Hits              ?     2247
  Misses            ?      177
  Partials          ?        0

Continue to review full report at Codecov.

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


Update api.rst

typo
Summary

Checklist

[ ] If code changes were made then they have been tested.

[ ] I have updated the documentation to reflect the changes.

[ ] This PR fixes an issue.
[ ] This PR adds something new (e.g. new method or parameters).
[ ] This PR is a breaking change (e.g. methods or parameters removed/renamed)
[x] This PR is not a code change (e.g. documentation, README, …)

@b1ue64

i also did this smh

wait you did it first nvm

:trollface: kek


On Android, the onKeyPress callback returns the wrong key value when the TextInput has the maxLength property

Description
In Android, when a TextInput with the maxLength property is "full"(that is, the length of the input is equal to the maximum), the onKeyPress event will return the last character in the input.
React Native version:
0.63.3
Steps To Reproduce

Create a TextInput component with maxLength=1, and an onKeyPress handler
Type multiple different characters into the TextInput
Observe that event.nativeEvent.key in the onKeyPress callback is always the first character that was entered into the TextInput

Expected Results
onKeyPress should return the key that was actually pressed.
This behaviour only happens in Android, and can be seen in the following snack:
https://snack.expo.io/PuyXgucEf

@javiercsd Thank you for the issue! I noticed the issue in your snack - kinda  annoying. Labeled it as a bug for people to check out.

@javiercsd Thank you for the issue! I noticed the issue in your snack - kinda  annoying. Labeled it as a bug for people to check out.

Hi!
same issue here on 2023
not resolved yet?

The same issue 2024


Numerical ops

So I need to think about how to deal with LLVM and WASM numerical ops. The mapping needs to be mapped out with rigorous math. The core issue is that LLVM and WASM has signed division but midenVM does not. There are also other issue related to handling other popular sizes including 8 and 16 bits.
The mathematical core of this problem is that a subrange of integers 0..n-1 is a ring and can be equiped with the operations add, mul, udiv, umod, neg, sub where sub a - b = a + -b,  and -b = b + n mod n, and the other operations are their natural values modulo n.  udiv and mul are unrelated. We also have the usual comparisons.
Then we have signed integers which are some subrange of integers such as -n .. +n roughly. The operations on these are defined by the operations on integers, and fail if the bounds are exceeded. In the special case where the range has a power of 2 elements, the range -2^k .. 2^k-1 fits in 2k bits and with the equality of zero representations, we get a representation called two's complement which LLVM and Wasm mandate.
With the two's complement representation, add, sub, neg, and mul coincide with a ring mod 2^2k. However, for larger values where the integer result is unrepresentable, the modular operations give the wrong result. Miden has checked versions of these operations to use when the element type is an integer approximation, rather than a ring.
However division and modulus do not work at all and two extra operations are required for signed division and modulus. LLVM uses generic operator with typed operands for the size ONLY, and extra codes nsw and nuw meaning no signed wrap and no unsigned wrap which hint at the correct interpretation somehow. Translation rules need to be determined.
There's also the issue of integers of other types. i1 is just bool and is no problem. However 8 bit and 16 bit integers as well as 64 bit will be generated from LLVM front ends like Rust or C.
So the final outcome of  this issue must be a rigidly defined translation specification for LLVM (I think Wasm is secondary). That is: when you see THIS operand with THESE types, generate THIS miden assembly.
It is NOT immediately clear this is possible: that is, the compiler may need to do some "type inference" to figure out the upstream programmers actual intent.

Notes.
The ring u32 has 4 operations: add, neg, mul, and divmod denoted in MVM by wrapping operations. The operations cannot fail and always give the correct answer except that divmod fails with a divisor of 0. [Comparisons and other ordering operations are available too]
The problem with this data type is it is almost entirely useless. It has two key uses:

In systems programming
For implementing rings of useful sizes, for example for array indexing

Generally, the programmer desires two types they cannot have:

Natural numbers
Integers

A sufficiently large ring can provide a small number of operations on a small number of values with results conforming to the corresponding abstract mathematical calculations. For natural numbers the supported operations are add, mul and divmod. Subtraction and negation are not readily available for natural numbers. Whilst 'divmodcannot fail except for a divisor of 0,addandmul` can have an unrepresentable natural result. MVM provides three varieties of operations to handle this: checked operations detect overflows and report errors, whilst unchecked operations are more efficient, but may lead to undefined behaviour on overflow. Unchecked operations can be used safely in conjunction with a proof of correctness. There are also overflowing operations which may be useful for other purposes.
The representation of integers, on the other hand, is fraught with difficulties. The basic idea is that wrapping unsigned ring operations can model integers for a small number of small valued operations. Unfortunately, if the result of a computation is not representable, it is NOT possible to check with existing MVM instructions.
For example, if two medium sized values are added and the result goes past the half way mark, the result would be interpreted as a negative value. However the checked operations would still allow this because the checks for integers and natural numbers are distinct.
Conversely, the addition of two small negative numbers using u32 wrapping operations would give the correct value, but u32 checks would fail the addition as an overflow. Hence, to avoid gratuitous failures, the programmer would need to use wrapping u32 operations without checking to represent small integers.
The core difficulty here is defining a type system which would be able to statically check MVM programs, which is precursor to the real problem, which is to develop a type system which can statically account for LLVM IR programs, which in turn is the precursor to defining a type based mapping from LLVM operations to MVM operations.
In particular programmers of high level languages fed into LLVM regularly use signed integer types, even when they have no need for negative values, and often use them in lieu of a more correct type like an option type. Even worse, programs using high level type systems get munged by translators into encodings which safely abuse type systems to reduce the code to a lower level. In turn this means it is
VERY HARD IF NOT IMPOSSIBLE
to map arithmetic operations from LLVM to MVM correctly. In part this is because LLVM simply specifies that out of bounds values are poison and leaves it up to the back end (that's us!) to figure out what to do about it. The problem here is that one mans poison is another mans honey.
"I don't need to check my array index calculations because my arrays cannot be big enough for the calculations to overflow". So I can use wrapping or unchecked operations and the results will always be the same and always correct.


About the environment

Hi, may I know the version of Keras, TF, and python you're using?

The package is from early 2018, so it's likely TF 1.14
If you find compatibility issues, PRs are welcome!


Order of references random

We need to apply proper sorting for the reference list, depending on labels in ascending order.

How should we assign the position of the rest? Easiest would be insertion order.

Fixed


[API] Change release API paths

Corrects the following release API routes:

GET /repos/{owner}/{repo}/releases/{id}/assets/{attachment_id}
-> GET /repos/{owner}/{repo}/releases/assets/{attachment_id}
PATCH /repos/{owner}/{repo}/releases/{id}/assets/{attachment_id}
-> PATCH /repos/{owner}/{repo}/releases/assets/{attachment_id}
DELETE /repos/{owner}/{repo}/releases/{id}/assets/{attachment_id}
-> DELETE /repos/{owner}/{repo}/releases/assets/{attachment_id}

The routes were in conflict with the Github API:

GET /repos/{owner}/{repo}/releases/assets/{asset_id}
PATCH /repos/{owner}/{repo}/releases/assets/{asset_id}
DELETE /repos/{owner}/{repo}/releases/assets/{asset_id}

The previous routes are marked as deprecated, but have not been removed.

I would not say it's a fix but an enhancement. since endpoints work just fine. only github had made some changes we are adopting with this ...

make generate-swagger is missing & some tests :)

make generate-swagger was not missing ;)
On my system, the command did not append an extra line to the v1_json.tmpl file.
After I manually inserted an empty line, the build is passing.
That was the error:
Please run 'make generate-swagger' and commit the result:
diff --git a/templates/swagger/v1_json.tmpl b/templates/swagger/v1_json.tmpl
index e217c174f..5da925a10 100644
--- a/templates/swagger/v1_json.tmpl
+++ b/templates/swagger/v1_json.tmpl
@@ -17070,4 +17070,4 @@
       "TOTPHeader": []
     }
   ]
-}
\ No newline at end of file
make: *** [Makefile:255: swagger-check] Error 1
+}

Codecov Report

Merging #14596 (5e5ae14) into master (cbe7f52) will increase coverage by 0.05%.
The diff coverage is 53.84%.

@@            Coverage Diff             @@
##           master   #14596      +/-   ##
==========================================
+ Coverage   42.22%   42.28%   +0.05%
==========================================
  Files         764      773       +9
  Lines       81385    83048    +1663
==========================================
+ Hits        34365    35115     +750
- Misses      41416    42214     +798
- Partials     5604     5719     +115

Impacted Files
Coverage Δ

routers/api/v1/repo/release_attachment.go
35.05% <49.39%> (+35.05%)
:arrow_up:

routers/api/v1/api.go
78.08% <100.00%> (-0.72%)
:arrow_down:

services/pull/check.go
26.02% <0.00%> (-22.51%)
:arrow_down:

modules/git/repo_language_stats_nogogit.go
44.57% <0.00%> (-19.26%)
:arrow_down:

modules/setting/database.go
42.85% <0.00%> (-18.37%)
:arrow_down:

modules/indexer/stats/db.go
56.00% <0.00%> (-12.00%)
:arrow_down:

modules/git/tree_entry_nogogit.go
76.47% <0.00%> (-11.03%)
:arrow_down:

modules/setting/session.go
78.57% <0.00%> (-10.91%)
:arrow_down:

modules/convert/notification.go
52.27% <0.00%> (-8.26%)
:arrow_down:

routers/api/v1/repo/tag.go
55.55% <0.00%> (-8.09%)
:arrow_down:

... and 185 more

Continue to review full report at Codecov.

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

also we could dedublicate some code

I guess Gitea's API has been different from GitHub's for long time.
Is this PR still related?


How to return any type?

I'm trying to make an event handler that returns a string and 6 other random types via a tuple when calling a function. The types can be a C++ primitive, a string, or sol::nil.
However, I'm having trouble implementing this. There doesn't seem to be a "catch-all" sol type for functions. I tried sol::object, but it only works with sol::nil.

You should be able to use sol::object, but not by constructing it directly. You can use sol::make_object(lua_state, your_object);, where lua_state is your sol::state / lua_State* and your_object is an instance of your object (eg. string, primitive, etc.). If you don't have the state available in the method you are returning this from, you can add a sol::this_state parameter, which will automatically provide the state object to you.

Where do I add the sol::this_state parameter?


Adding lookup / history proof efficiency optimization

Implements an efficiency optimization that changes the contents of a key history proof (reducing the number of total past marker versions and future marker versions) without compromising on security.
From the doc comments of get_marker_versions() (which is basically the only function that is updated):
The past marker versions are determined as follows:

Include the largest power of 2 that is less than start_version.
Include the largest element of MARKER_VERSION_SKIPLIST that is less than start_version.
Include at most a log_2(start_version) number of versions between start_version and the
largest power of 2 less than start_version, determined as follows: For each bit position i
in start_version, if the bit is 1, include the value of start_version with the ith bit set
to 0 and followed by trailing zeros.

As a concrete example, if start_version = 85, the past marker versions would be [16, 64, 80, 84].
Since:
01010101 => 85
01010100 => 84
01010000 => 80
01000000 => 64
And 16 comes from MARKER_VERSION_SKIPLIST.
The future marker versions are determined as follows:

Include all powers of 2 that begin from start_version, up until the smallest element in
MARKER_VERSION_SKIPLIST that is greater than start_version.
Include all elements of MARKER_VERSION_SKIPLIST that are between start_version and epoch.
Include at most a log_2(start_version) number of versions between start_version and the
smallest power of 2 greater than start_version, determined as follows: For each bit position i
in start_version, if the bit is 0, include the value of start_version with the ith bit set
to 1 and followed by trailing zeros.

As a concrete example, if start_version = 85, the future marker versions would be
[86, 88, 96, 128, 256, 65536, 2^32] (potentially truncated depending on if any of these
numbers exceed epoch).
Since:
01010101 => 85
01010110 => 86
01011000 => 88
01100000 => 96
10000000 => 128
And the remainder of the list comes from MARKER_VERSION_SKIPLIST.
Note that the past marker versions do not contain start_version, as this would be redundant
in the history proof (since membership is already checked for start_version).

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 88.04%. Comparing base (3ce5335) to head (3937610).
Report is 10 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #444      +/-   ##
==========================================
- Coverage   88.61%   88.04%   -0.58%
==========================================
  Files          39       38       -1
  Lines        9109     8273     -836
==========================================
- Hits         8072     7284     -788
+ Misses       1037      989      -48

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

@dillonrg thanks for the feedback!


Balance precision

In DocumentDb the balance is stored with extreme precision.
A precision of 2 number should be enough.
"Balance": 11.400000000000002,
instead of
"Balance": 11.40,

still not fixed


Implement nonlinear tire model

A general nonlinear tire model takes the lateral slip angle, camber angle, and normal force as inputs and outputs the lateral force.
$$
F_y = f(\alpha, \gamma, F_z)
$$
If the tires are modeled as rigid, then the normal force between ground and wheel is a noncontributing force. This means you get equations that look like
$$
\begin{bmatrix}
M & c \
c & 1
\end{bmatrix}
\begin{bmatrix} \dot{\bar{u}} \
F_z \end{bmatrix} =
\begin{bmatrix} F(F_y) \
f \end{bmatrix}
$$
I currently solve the above system numerically at each time step. So that creates a circular dependency for F_y(F_z) but F_z depends on known F_y if you want to implement an arbitrary nonlinear function for F_y.
We could solve the system symbolically and it would give $F_z(\bar{x})$ which you can replace in the first equation and that gives F_y as a pure function of state. This will make for some nasty long equations with chances of divide by zero.
A second option is to introduce a vertical tire compliance and a new state to track this spring deformation. Then F_z = k*x and F_z is no longer a noncontributing force.
I guess a third option would be to iteratively solve the above to equations to home in on the value of F_z and F_y that satisfy both equations.

Comment from the code:
# We need to solve the dynamic equations and the auxiliary equations
# simultaneously to avoid having to solve the dynamic equations first and then
# substitute in the derivatives of the speeds. So reconstruct the equations of
# motion to this form:
# [Mp  0,  0, -Mf]*[up ] = [F     ]
# [0, Cf,  0,  Cz] [fyp]   [-Fy   ]
# [0,  0, Df,  Dz] [mzp]   [-Mz   ]
# [Ap, 0,  0,  Af] [fz ]   [-B_aux]

The dynamical equations end up depending on fz in this formulation and are not decoupled from the noncontributing force equations like in https://moorepants.github.io/learn-multibody-dynamics/noncontributing.html#augmented-dynamical-differential-equations
I forget why that is the case.

Nonlinear model functions at a minimum level in #15.


Source option 6 is no longer supported. Use 7 or later

[INFO] Compiling 220 source files to /Applications/webfont-generator-master/vendor/sfntly/java/target/classes
[INFO] -------------------------------------------------------------
[ERROR] COMPILATION ERROR :
[INFO] -------------------------------------------------------------
[ERROR] Source option 6 is no longer supported. Use 7 or later.
[ERROR] Target option 6 is no longer supported. Use 7 or later.
[INFO] 2 errors
[INFO] -------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  01:00 min
[INFO] Finished at: 2022-02-04T11:22:44+11:00

Yeah, I'm receiving the same error when running setup.
webfont-generator v1.3.2
macOS 12.4

Ah, software rot. It sounds like newer versions of javac are dropping support the version of Java that sfntly was written in. What version of Java are you using?

Thanks for getting back to me, I managed to find another solution to my problem, but FTR:
$ java -showversion
java version "1.8.0_261"
Java(TM) SE Runtime Environment (build 1.8.0_261-b12)
Java HotSpot(TM) 64-Bit Server VM (build 25.261-b12, mixed mode)

What was the solution you found? I'm running into the same thing and there are no answers here.

Nothing that helpful for others I'm afraid, I was just looking to locally test out a font on a web site, so I just used the .ttf file. The project got shelved so I didn't have to cross the webfont bridge in the end.

FWIW I was able to get it to work by simply changing the compiler version in the POM.XML for sfntly
/vendor/sfntly/java/pom.xml
Changed:
<maven.compiler.source>1.6</maven.compiler.source>
<maven.compiler.target>1.6</maven.compiler.target>
To:
<maven.compiler.source>1.7</maven.compiler.source>
<maven.compiler.target>1.7</maven.compiler.target>


Key error involving external zone in accessibility calculator

It happens while transit accessibility is being calculated. Here's the error message:
Traceback (most recent call last):
  File "P:\MPO\20_Data\IndyGeoprocessingTools\AccessibilityCalculator\AccessibilityCalculator.py", line 252, in <module>
    calc_transit_acc(transit_bool, transit_zones, taz_file)
  File "P:\MPO\20_Data\IndyGeoprocessingTools\AccessibilityCalculator\AccessibilityCalculator.py", line 206, in calc_transit_acc
    emp[:, zone_map[zone[0]]] = zone[1]*bool_skim[:, zone_map[zone[0]]]
KeyError: 154700

Failed to execute (AccessibilityCalculator).

The issue appears to be with all zones, not just zone 154700

The issue appears to have been caused by cell A1 in the transit skim file reading 'RCIndex' instead of being blank.


MtomEnabledServiceClient

Where is defined "MtomEnabledServiceClient" from the example?

I know it's late, but I think thats the generated WCF client that extends System.ServiceModel.ClientBase<TChanel>

@LokiMidgard is correct. That class name is really just a placeholder for whatever your specific service client is.


为什么eval的时候老用cpu跑啊？

真奇怪啊，eval的时候比train慢的好多，gpu一直为0，cpu却跑满了，感觉一直在用cpu跑，train的时候就没有这种情况

Hi
I run train_demo.py on my server and found no issue with evaluation process. All computation is conducted on GPU. Maybe you can check your code again or give more detailed info of how you run the code.


WIP: add a vulnerability check for the promoter

Adding a check against PRs that attempt to add images with known vulnerabilities (Issue #235). The vulnerability detection is handled using the Container Analysis Service.

/cc @listx @prathak07

/test pull-cip-unit-tests

Thanks!
/lgtm
/approve


Access file.name instead of fileName

Fixes https://github.com/GoogleChromeLabs/text-editor/issues/33

cc @petele


feat: Add a homemade depends_on for MNG submodule to ensure ordering of resource creation

PR o'clock
Description
Hack to add a "homemade" depends_on as suggested https://discuss.hashicorp.com/t/tips-howto-implement-module-depends-on-emulation/2305/2 to ensure ordering of ressource creation for managed node groups.
I don't really like the approach, but the hack doesn't add complexity (because, there are only 2 resources in the submodule in which we add an explicit depends_on) and seems to work as expected.
I tested it to resolves https://github.com/terraform-aws-modules/terraform-aws-eks/issues/843
Note: I'm opening this PR to start discussion. So feedbacks are welcomed.
Questions

Is this something we want to do ?
@dpiddockcmp is your comment still apply ?

Checklist

[x] CI tests are passing
[x] README.md has been updated after any changes to variables and outputs. See https://github.com/terraform-aws-modules/terraform-aws-eks/#doc-generation

closing in favor of https://github.com/terraform-aws-modules/terraform-aws-eks/pull/868

Please could we reconsider this?
It is a more terraform native way of ensuring dependency between resources.
I really regret the null_resource hack as I didn't know that you could just depend on variables! We're seeing this horror being repeated in the PRs for moving workers to a module and fargate support.

Yes of course. I will rebase my branch.


Implement Confusion Matrix Logic

Implements Confusion Matrix logic, inspired by sklearn confusion matrix implementation.

Codecov Report

Merging #1769 (efe7fc7) into main (0b2ea58) will decrease coverage by 13.03%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##             main    #1769       +/-   ##
===========================================
- Coverage   88.32%   75.29%   -13.04%
===========================================
  Files          89        9       -80
  Lines        5259      255     -5004
===========================================
- Hits         4645      192     -4453
+ Misses        614       63      -551

Flag
Coverage Δ

unittests
75.29% <ø> (-13.04%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...ai/responsibleai/_tools/error_analysis/__init__.py

...sibleai/responsibleai/_tools/shared/base_result.py

...nsibleai/databalanceanalysis/data_balance_utils.py

erroranalysis/erroranalysis/report/__init__.py

raiutils/raiutils/dataset/dataset.py

...leai/responsibleai/modelanalysis/model_analysis.py

raiwidgets/raiwidgets/dashboard.py

...ai/responsibleai/rai_insights/rai_base_insights.py

...ranalysis/erroranalysis/_internal/cohort_filter.py

raiwidgets/raiwidgets/error_analysis_dashboard.py

... and 70 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

please change the target postga


Is one dist folder missing, are there many errors in the demo folder?

Have you not downloaded the dist folder ? your player is not working .

It works fine. Have a search. Thanks!


Doesn't dump page on Error 1001

For example, https://www.pixiv.net/member_illust.php?id=211815
Config:
[Network]
useproxy = False
proxyaddress =
useragent = Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/37.0.2062.124 Safari/537.36
userobots = True
timeout = 60
retry = 3
retrywait = 5

[Debug]
loglevel = DEBUG
enabledump = True
skipdumpfilter = 1004|1002
dumpmediumpage = False
dumptagsearchpage = False
debughttp = False

[IrfanView]
irfanviewpath = C:\Program Files (x86)\IrfanView
startirfanview = False
startirfanslide = False
createdownloadlists = True

[Settings]
filenameformat = %member_id%\%image_id% - %title%
filenamemangaformat = %member_id%\%image_id% - %title%_%page_index%
filenameinfoformat = %member_id%\%image_id% - %title%
avatarnameformat =
downloadlistdirectory = .
uselist = False
processfromdb = False
overwrite = False
tagsseparator = ,
daylastupdated = 5
rootdirectory = E:\conf\pixiv
alwayscheckfilesize = False
checkupdatedlimit = 0
downloadavatar = True
createmangadir = False
usetagsasdir = False
useblacklisttags = False
usesuppresstags = False
tagslimit = -1
writeimageinfo = False
writeimagejson = False
datediff = 0
backupoldfile = False
writeugoirainfo = False
createugoira = True
deletezipfile = True
enableinfiniteloop = False
verifyimage = False
writeurlindescription = True
urlblacklistregex =
urldumpfilename = url_list_%Y%m%d
dbpath =
creategif = False
useblacklistmembers = False
createapng = False

[Pixiv]
numberofpage = 0
r18mode = False
dateformat =

The page dump happened on previous, non-beta version.

looks like they change the error message from 'The user has either left pixiv, or the user ID does not exist.' to 'User has left pixiv or the user ID does not exist.'
This might be happening again if they change the message again, as I don't see any error status code in the page.

Just check that message
An error has occurred.
 appears and dump as generic error, if not filtered out?


Can't animate ToolbarAndroid using Animated

Hi,
I'm trying to apply animation to the ToolbarAndroid component, but my code results in an error. I reproduced the issue in a new project using the following code:
import React, {
  Animated,
  AppRegistry,
  Component,
  StyleSheet,
  Text,
  ToolbarAndroid,
  View
} from 'react-native';

const AnimatedToolbarAndroid = Animated.createAnimatedComponent(ToolbarAndroid);

class toolbarTest2 extends Component {
  constructor(props) {
    super(props);

    this.state = {
      toolbarHeight: new Animated.Value(56),
    };
  }

  componentDidMount() {
    Animated.timing(
      this.state.toolbarHeight,
      {
        toValue: 112,
        duration: 750,
      }
    ).start();
  }

  render() {
    return (
      <View style={{flex: 1}}>
        <AnimatedToolbarAndroid style={{
          height: this.state.toolbarHeight,
          backgroundColor: 'blue',
        }} />
        <View style={styles.container}>
          <Text style={styles.welcome}>
            Welcome to React Native!
          </Text>
          <Text style={styles.instructions}>
            To get started, edit index.android.js
          </Text>
          <Text style={styles.instructions}>
            Shake or press menu button for dev menu
          </Text>
        </View>
      </View>
    );
  }
}

const styles = StyleSheet.create({
  container: {
    flex: 1,
    justifyContent: 'center',
    alignItems: 'center',
    backgroundColor: '#F5FCFF',
  },
  welcome: {
    fontSize: 20,
    textAlign: 'center',
    margin: 10,
  },
  instructions: {
    textAlign: 'center',
    color: '#333333',
    marginBottom: 5,
  },
});

AppRegistry.registerComponent('toolbarTest2', () => toolbarTest2);

This code works when I use Animated.View, but when I replace it with ToolbarAndroid, I get an error message saying this.viewConfig is undefined when executing function setNativeProps: (link to screenshots).
I'm developing on Ubuntu Linux, testing on Nexus 5 (Android 6.0.1), using React Native 24 (but I also tested it with 25-rc with no differences).

I've never tried to make an animated component out of a native one but I suspect that's your problem based on that error.  Animated can only be used with non-native components -- I think. I would suggest using a different toolbar like the one in the react-native-router-flux if you want to apply your own animations. It's already using Animated and you can probably tap into that api and customize it to do and look how you want.

I eventually sidestepped the issue by creating my own header bar. However, I'm pretty sure Animated is supposed to work on native components, considering that e.g. Animated.View is one. I'm guessing there needs to be some additional native code for a component to work with Animated, so it's just missing in ToolbarAndroid. Whether that's something that really has to be fixed, I don't know.

Hi there! This issue is being closed because it has been inactive for a while.
But don't worry, it will live on with ProductPains! Check out its new home: https://productpains.com/post/react-native/cant-animate-toolbarandroid-using-animated
Product Pains has been very useful in highlighting the top bugs and feature requests:
https://productpains.com/product/react-native?tab=top
Also, if this issue is a bug, please consider sending a pull request with a fix.


Enable repo map with gpt 3.5 turbo-16k?

From what I've read, repo map is disabled outside gpt-4 because 3.5 cant handle the token load.  But with 3.5-16k released has anyone tried with 16k?
I'm going to dive into aider codebase and try to enable for 3.5 16k but thought I would ask for insight first

Thanks for trying aider and for your interest in experimenting with the repo map.
Here is the code that determines whether to use a repo map:
https://github.com/paul-gauthier/aider/blob/166ecdcbd0b86847088dc195ede37f7b77227859/aider/coders/base_coder.py#L167
So to enable it for gpt-3.5-turbo-16k, you could add a self.use_repo_map=True here, so that it is enabled on the model:
https://github.com/paul-gauthier/aider/blob/166ecdcbd0b86847088dc195ede37f7b77227859/aider/models.py#L58
You also need update the prompts used by the wholefile coder. To use a repo-map, it will need a repo_content_prefix:
https://github.com/paul-gauthier/aider/blob/166ecdcbd0b86847088dc195ede37f7b77227859/aider/coders/wholefile_prompts.py#L42
You can consult the editblock coder for an example of the repo_content_prefix. But you probably also need to introduce the concepts of "read-only" and "read-write" files in the other prompts, similar to the editblock coder.
https://github.com/paul-gauthier/aider/blob/166ecdcbd0b86847088dc195ede37f7b77227859/aider/coders/editblock_prompts.py#L53
I worry that GPT-3.5 won't be able to understand that the repo map is read-only content. It will probably try and "edit" the repo-map files.
I plan to eventually explore this, but I am not optimistic based on my prior experience with prompting 3.5 for code editing.

@IkuStudies have you tried to make any changes, please share the results if you did ? thanks

ok excellent, thank you for the insight @paul-gauthier
I'll have some time this afternoon to experiment, and @ramAdam will report the results here in this thread.
I'll be working with a python codebase for a game with about 20 class files, I'm aiming to refactor for more modular maintainable architecture,  GPT4 would be ideal but maybe I can coax 3.5-16k to perform.  I have universal ctags rigged up, and done some basic experiments with aider, so with pauls advice I should be able to at least perform some experiments with my codebase.  will post any findings tonight

@IkuStudies Any update from you ?

I made some changes to get gpt35turbo to work with repo map. it's actually working quite impressively, but still gpt3 reasoning, but much much much better experience (for a difficult logic, it won't be any different since you will be using gpt as a doc resource instead of your main code builder) .
The only problem is editing file using "diff" instead of "whole", sometimes it works, sometimes it doesnt, sometimes it loops forever (since i tried to quickly force the "gpt3 turbo" condition always true and set the use repo map to true.) Still can't make it stable.
Can you Paul give me any clue? (I will find a solution today, just help me sleep earlier haha).

Unfortunately 3.5 is not able to work well with the diff edit format. I did a fairly extensive benchmark:
https://aider.chat/docs/benchmarks.html

fair enough, i give up.

Ya, these LLMs can be frustrating. That's why I decided to build a benchmark, to have a fairly solid objective way to measure the impact of prompt and algorithm changes.

I've been doing some more experiments and they confirm my belief that 3.5 is really not capable of handling a repository map. Information about the rest of the repository seems to confuse it, and it's unable to work on the code for the files that it does have access to.
I'm gonna close this issue for now, but feel free to reopen it or file another issue if you find evidence that 3.5 could use a repository map.

@paul-gauthier what do you feed exactly for the repomap?


CVE-2018-16875: x509: CPU denial of service in chain validation

From https://github.com/golang/go/issues/29233

Package crypto/x509 parses and validates X.509-encoded keys and certificates. It's supposed to handle certificate chains provided by an attacker with reasonable resource use.
The crypto/x509 package does not limit the amount of work performed for each chain verification, which might allow attackers to craft pathological inputs leading to a CPU denial of service. Go TLS servers accepting client certificates and TLS clients verifying certificates are affected.

Go 1.11.3 and 1.10.6 have been released with this fixed.

Thank You, @adamdecaf, for pointing our attention on this critical issue.
Your vigilance is invaluable to us, and this is what makes us fierce believers in the open source community.
We've prepared a new release of Traefik that will address the problem.
We'll close the issue as soon as it is available to the public.

Thank you @adamdecaf
The fix release is available at: https://github.com/containous/traefik/releases/tag/v1.7.6

Just a heads up, there is a go 1.11.4 now.

go1.11.4 (released 2018/12/14) includes fixes to cgo, the compiler, linker, runtime, documentation, go command, and the net/http and go/types packages. It includes a fix to a bug introduced in Go 1.11.3 that broke go get for import path patterns containing "...". See the Go 1.11.4 milestone on our issue tracker for details.

https://golang.org/doc/devel/release.html
It does not seems important to this security fix, but it is better safe than sorry...
[]'s


Fix typo in config schema

subscription -> subscriptionId

Thank you for catching this! Merging your PR now :)


Adhearsion should support internationalising prompts (recorded and TTS)

This is the place to discuss how this will work. Pinging @bklang and @JustinAiken

Closing in favour of https://github.com/adhearsion/adhearsion/pull/557


Pick an available port instead of crashing with "listen EADDRINUSE"

DEBUG INFO: webtorrent 0.60.1, node v0.12.7, darwin x64, exit 1
events.js:85
throw er; // Unhandled 'error' event
^
Error: listen EADDRINUSE
at exports._errnoException (util.js:746:11)
at Server._listen2 (net.js:1156:14)
at listen (net.js:1182:10)
at Server.listen (net.js:1267:5)
at runDownload (/opt/local/lib/node_modules/webtorrent/bin/cmd.js:313:10)
at Object. (/opt/local/lib/node_modules/webtorrent/bin/cmd.js:147:3)
at Module._compile (module.js:460:26)
at Object.Module._extensions..js (module.js:478:10)
at Module.load (module.js:355:32)
at Function.Module._load (module.js:310:12)

This error means that the port WebTorrent wants to use (port 8000) is already in use. This could be from an other instance of WebTorrent, or any another program.
You can run WebTorrent on a different port by using the --port argument:
webtorrent --port 8001

I'll leave this issue open since we can do better here -- by either providing a friendlier error, or preferably, automatically picking an available port.

Thanks!

Leaving this issue open until we support automatically picking an available port instead of crashing.

@feross I'm whiling to help on this.
It's ok to use an external package for that?
(I think it would be too much work doing this without).
https://github.com/baalexander/node-portscanner

@Stiveknx It's not too much work actually, it can be done in just a few lines of code.
https://github.com/gillesdemey/grop/blob/master/index.js
There are countless modules on npm already, though it looks like node-portscanner has a few more bells and whistles.

@Stiveknx Cool, happy to accept a PR from you that implements this. You might not need to use an open port finder, but instead pass 0 in as the port so the OS will automatically pick a port.
@gillesdemey grop is a module done right – looks nice.

I made a little contribution on this, I believe this is what you were talking about...
Let me know if there is anything.


[etlas] Not getting an uberjar for libraries

I have some code without a Main module. It is meant to be called from some Java code. I don't want to have to copy files out of my ~/.etlas directory or put  them on my classpath. I would just like an Uber JAR with the dependencies instead.
I think the current Uber JAR mechanism only works for executables.

Maybe it is a duplicate of #305?

@jneira yeah, I think so

I seem to have the same problem. It's not clear for me what the solution is exactly? Additionally, I cannot find any documentation about all this uberjar business except for scouring the issues.

You can create an uberjar by creating a cabal.project file and adding the following line:
uberjar-mode: True

(or equivalently etlas build --enable-uberjar-mode but you must pass in that flag every time)
Note that this setting only applies to executable components and not library components, so the workaround for now is to make an executable component with your code and add main = return () in your Main.hs file.
Adding support for library components is not too hard, but it does require adding an additional flag inside the compiler.
Regarding the docs, I think it might've gotten lost when we migrated to a new documentation system. We'll take a look and update it.

OK, thanks for the info!


Replace current interaction with LLMs by Langchain-rust

Rewrite llm_api.rs to "langchain-rust"
Support LLM list:

OpenAi
Ollama
Anthropic Claude
Azure OpenAi

Rewrite llm_api.rs to "langchain-rust"
Support LLM list:

OpenAi
Ollama
Azure OpenAi
Anthropic Claude

Could you assign this issue to me?


It often leads memory leak on nginx reload

@zimmerle   It often leads memory leak on nginx reload using modsecurity branch 3.1-experimental and master,I hope that the official will fix this problem as soon as possible, which has a serious impact on the production environment.
And There is also why this problem #2381 was closed without being resolved!!!
I suggest that you officially do a test yourself. First, create a lot of virtual hosts, each virtual host quotes the modsecurity rules separately, and then constantly reload, the memory leak should be reproduced!
Describe the bug
We publish more frequently every day, and often reload nginx，every few days nginx has a memory leak,How to fix it?
Logs and dumps
Output of:
2021/01/21 11:04:08 [alert] 25264#25264: fork() failed while spawning "worker process" (12: Cannot allocate memory)
2021/01/21 11:04:08 [alert] 25264#25264: sendmsg() failed (9: Bad file descriptor)
2021/01/21 11:04:08 [alert] 25264#25264: sendmsg() failed (9: Bad file descriptor)
2021/01/21 11:04:08 [alert] 25264#25264: sendmsg() failed (9: Bad file descriptor)

Hi @Hello-Linux ,
What is this issue meant to convey that is different from your issue https://github.com/SpiderLabs/ModSecurity/issues/2502 ?

Duplicate of #2502.


[question] What about Huawei Inapp

Platforms you faced the error (IOS or Android or both?)
Android
Tested environment (Emulator? Real Device?)
real deice
after publishing app on huawei store inaps doesnt work. i guess that need to integrate
https://developer.huawei.com/consumer/en/hms/huawei-iap/
may refer to this :
https://stackoverflow.com/questions/58631362/will-react-native-work-without-google-services-on-huawei-phone
Some ideias ?

just use https://github.com/HMS-Core/hms-react-native-plugin/tree/master/react-native-hms-iap


Proper DeliveryAPI api error content is now forwarded instead of failing with null exception.

Motivation
Fixes #326
All DeliveryClient methods that reads data from Delivery API now forward proper API error content instead of failing with null exception.
This PR code additionally introduces few unit tests refactorings/enhancements + non breaking constructors changes.

I have just few notes:
1. Have you considered creating another constructor for responses (eg. DeliveryItemListingResponse) with just an ApiResponse param? It could save us setting those null values in the client.

2. Why there is no _succes check_ for _GetItemAsync, GetTypeAsync, GetContentElementAsync, GetTaxonomyAsync_ methods?

3. I think it would be better to move _succes check_ before assignement to the content variable.

No, I haven't thought about these constructors for null values. I will think about it and reach you to discuss it.
The reason is, that implementation was already done in a way, that they already produced correct error response  ... and added unit tests prove it. I will think about putting that IsSuccess check, but if I will put it there, it would be more for some code standardization than pure necessity.
You are right, it would be better place (to avoid doing not necessary code in these error cases). I will move this check as close to actual response retrieval where the code place is sub-optimal (case that you wrote).

I have just few notes:
1. Have you considered creating another constructor for responses (eg. DeliveryItemListingResponse) with just an ApiResponse param? It could save us setting those null values in the client.

2. Why there is no _succes check_ for _GetItemAsync, GetTypeAsync, GetContentElementAsync, GetTaxonomyAsync_ methods?

3. I think it would be better to move _succes check_ before assignement to the content variable.

1. No, I haven't thought about these constructors for null values. I will think about it and reach you to discuss it.

2. The reason is, that implementation was already done in a way, that they already produced correct error response  ... and added unit tests prove it. I will think about putting that `IsSuccess` check, but if I will put it there, it would be more for some code standardization than pure necessity.

3. You are right, it would be better place (to avoid doing not necessary code in these error cases). I will move this check as close to actual response retrieval where the code place is sub-optimal (case that you wrote).

I have just few notes:
1. Have you considered creating another constructor for responses (eg. DeliveryItemListingResponse) with just an ApiResponse param? It could save us setting those null values in the client.

2. Why there is no _succes check_ for _GetItemAsync, GetTypeAsync, GetContentElementAsync, GetTaxonomyAsync_ methods?

3. I think it would be better to move _succes check_ before assignement to the content variable.

I have just few notes:
1. Have you considered creating another constructor for responses (eg. DeliveryItemListingResponse) with just an ApiResponse param? It could save us setting those null values in the client.

2. Why there is no _succes check_ for _GetItemAsync, GetTypeAsync, GetContentElementAsync, GetTaxonomyAsync_ methods?

3. I think it would be better to move _succes check_ before assignement to the content variable.

1. No, I haven't thought about these constructors for null values. I will think about it and reach you to discuss it.

2. The reason is, that implementation was already done in a way, that they already produced correct error response  ... and added unit tests prove it. I will think about putting that `IsSuccess` check, but if I will put it there, it would be more for some code standardization than pure necessity.

3. You are right, it would be better place (to avoid doing not necessary code in these error cases). I will move this check as close to actual response retrieval where the code place is sub-optimal (case that you wrote).

Points 1. and 3. are now implemented, for point 2. is opened discussion within SDK maintainer team.


src/decorators.cpp memory leak?

It seems that src/decorators.cpp has a memory leak.
Run make FACTOR=1000, then run top. Memory consumption will be constantly growing when decorators.bin is running.

@kostochkin I believe I fixed that already. Can you check again and confirm you still have the issue?

Yes, the growing still exists in my environment.
I used this command for logging memory consuption:
top -d 1 -b | grep --line-buffered decorators | tee toplog.txt

And ran make FACTOR=1000 on the newly cloned repository.
Here is my toplog.txt file.

@kostochkin do you know a method of checking for memory leaks automatically? We would add it to the Makefile, to avoid such problems in the future.

@yegor256 I have just found a solution. Clang provides a flag -fsanitize=leak. I tried it, it seems working and give an useful output.

@kostochkin tested and fixed, thanks for your help!


Allow result override

Currently there is no way to limit linting to only parts of code. This would be really helpful for legacy projects where coding standards are implemented in chunks instead of rewriting the whole files.
A simple solution is to allow the reporter to override the results array:
https://github.com/jshint/jshint/blob/badc7a445457c0a2c5b76570250262492214b98c/src/cli.js#L673
For example, a custom reporter could use the git diff range for the currently staged changes and use that to remove all JSHint errors that don't apply to that changeset.

This functionality goes beyond typical expectations for "reporting", so I don't
think it would be appropriate to extend the functionality in that way. We could
address your use case with a "results interpreter" API which had free reign to
do whatever it wished with the results array. Or we could restrict the surface
area to what seems to be the minimal requirement: a list of lines to ignore.
Somewhere in the middle would be support for specifying a JavaScript function
that would be used in an Array.prototype.filter operation.
I can appreciate the desire, but I'd like to see a bit more interest from
consumers before moving on this.
In the mean time, you can use JSHint to do what you're looking for today.
Either filter the output of the default reporter according to your criteria, or
define a custom reporter that only reports the errors/warnings that you're
interested in. In both cases, you'll have to ignore the exit status of the
JSHint process and instead react to the output stream. That's clearly not
ideal, though, which is why I'm not suggesting that a new feature is
unnecessary.

Thanks for looking into this @jugglinmike -- agreed 100%!
Using a dedicated API is definitely the right way to implement this. Let's see if others would also find this useful.

My pleasure!
Also: I'd like to rescind my recommendation to parse the output of JSHint's
default reporter. That output is not intended for programmatic consumption and
is subject to change between releases. For folks that are interested in
simulating this functionality on their own, a custom reporter is a far more
stable solution.