chore(main): release 0.1.0

:robot: I have created a release beep boop
0.1.0 (2023-07-25)
Features

initial version. Docker image, tag creation and release with github actions. Fixes #1 and Fixes #2 (4a3435d)

Miscellaneous Chores

release 0.1.0 (9bb8b9c)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/natilou/wallabag-kindle-consumer/releases/tag/v0.1.0 :sunflower:


feat: add player extensions

Expose a few more extensions:

getMediaInfo()
getActiveAudioTracks()
getActiveVideoTracks()
getActiveSubtitleTracks()

breaks web and wasm build because media_info.dart depends on ffi which is not available on web. you can add a media_info_dummy.dart for web like https://github.com/wang-bin/fvp/blob/master/lib/src/controller.dart#L9-L11

Thanks, should be fixed now!


Incompatibility with K8S 1.22

Recently we upgrade to 1.22 K8S and extenerDNS stops working.
Logging:
pkg/mod/k8s.io/client-go@v0.19.2/tools/cache/reflector.go:156: Failed to watch *v1beta1.Ingress: failed to list *v1beta1.Ingress: the server could not find the requested resource
[ERROR] plugin/errors: 2 service.k8s.domain.local. AAAA: plugin/k8s_gateway: Could not sync required resources
K8S 1.22 announce:
A number of deprecated beta APIs have been removed in 1.22 in favor of the GA version of those same APIs. All existing objects can be interacted with via stable APIs. This removal includes beta versions of the Ingress, IngressClass, Lease, APIService, ValidatingWebhookConfiguration, MutatingWebhookConfiguration, CustomResourceDefinition, TokenReview, SubjectAccessReview, and CertificateSigningRequest APIs.

Thanks for reporting. The PR #21 is ready and only needs some minor updates.

PR is merged. Fix should be in the v0.1.8


Feature request: add Kotlin to list of supported languages

Self-explanatory.

Issue moved to Codewars/codewars-runner-cli #407 via ZenHub


add two number with dart

Pull Request Type
What kind of change does this PR introduce?
[ X ] Solved an issue/task
[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:
What is the current behavior?

Issue Number: #1062
What is the new behavior?

Other information

Hello Sir, i just entering the world of open source and trying to learn as much as i can. I have solved the issue. Please provide feedback whether everything went well or not during the process as well as merge my commit <3 !

Merged

This is an automated message from Fork, Commit, Merge [BOT].

Thank you for your contribution! Your pull request has been merged. The files have been reset for the next contributor.
What's next?
If you're looking for more ways to contribute, I invite you to check out my other projects. Just click here to find more. These projects contain real issues that you can help resolve. You can also check out the Influences section in the README to find more projects similar to this one.
Also please leave a star to this project if you feel it helped you, i would really appreciate it.
I look forward to seeing your contributions!


Doesn't work with @import and has promise error

(node:5044) UnhandledPromiseRejectionWarning: TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string. Received type undefined
    at assertPath (path.js:39:11)
    at Object.resolve (path.js:166:7)
    at handlerAssets.forEach (C:\Users\user\Documents\Projects\site\templates\node_modules\parcel-plugin-url-loader\lib\index.js:23:14)

This is the promise error I'm receiving. Also it is not trying to inline any of the less files I import.

(node:5044) UnhandledPromiseRejectionWarning: TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string. Received type undefined
    at assertPath (path.js:39:11)
    at Object.resolve (path.js:166:7)
    at handlerAssets.forEach (C:\Users\user\Documents\Projects\site\templates\node_modules\parcel-plugin-url-loader\lib\index.js:23:14)

This is the promise error I'm receiving. Also it is not trying to inline any of the less files I import.

give me your parce & url-loader version


[WIP] src/v2/guide/typescript.md

Translate TypeScript support part in documents.

Thank you for your contribution but unfortunately we'll gonna archive this repo in favor of the official v3 documentation which is being forked here https://github.com/vuejs-vn/docs-next.
Please help to submit your PR over there from now on.


geonameID type is now Option[String]

Changes to allow GADM ID as described in https://github.com/clulab/eidos/issues/688

The type of geonameID of GeoPhraseID has been changed to Option[String].
The geoNamesIndex has been changed to geonames+woredas.zip.

Thanks @EgoLaparra.  That was fast.  Do I need to bump up the version number on geonorm in build.sbt to get something other than numbers then?

No, no need of updating the version. The id returned by geonorm is a String and the conversion into Int was made in eidos.
@bethard, is that correct?

Am I not hoping to get some strings from previously unidentifiable locations?

Sorry.  They are probably in the new index with the new name.

@bethard, @EgoLaparra, in eidos.conf, geoNamesIndexURL is "http://clulab.cs.arizona.edu/models/geonames-index.zip".  Is this still the file that needs to be downloaded?  In GeoNormFinder, it will be stored as "geonames+woredas.zip", but the name change is worrisome.  Should it have been changed in eidos.conf as well or was the online version updated if that was necessary?

Both files are available on the web, so I'm assuming that the answer is yes.

Sorry, I forgot to change eidos.conf. Yes, it should to point to "geonames+woredas.zip",

I updated and am comparing the old output to new output, hoping to see something other than a number in the geoID.  That hasn't happened yet, but I am curious about these differences:

Text
Old geoId
New geoId

2015
7439356
6852983

Black
4050081
5765865

”
10522145
10513141

—
10522145
10513141

mid-May
2157544
6073561

progression
11833383
3596416

Addis Ababa
344979
444178

R2
10529703
10517701

They seem a little worrisome.

In the 1532 documents just processed there was no geoId that was a string.  For the examples above, after some neural network finds that node x is the best match, how is the text of the node compared to the document text?

For the table of differences, everything but Addis Ababa was a bad location anyway. For Addis Ababa, the change is from https://www.geonames.org/344979/addis-ababa.html to https://www.geonames.org/444178/adis-abeba-astedader.html. I think either of those would be acceptable; it's whether we think they mean the city itself or the metropolitan area, I believe.
These kids of changes are to be expected any time the content of the index changes. GeoNorm looks up the text found by the neural location finder in a Lucene index, and then uses a linear classifier to rerank the results of that Lucene lookup. Both Lucene and the classifier may give different results if the index changes.
Getting no geo IDs of the form ETH.X.X.X_X is a little surprising, though it's possible that the named entity tagger isn't finding any of the woreda names that weren't already in GeoNames. If you wanted to look further into it, you could see if any of the woreda names here are being found as locations: http://clulab.cs.arizona.edu/models/gadm_woredas.txt

Thanks.  Analemmo did it in the webapp.  Maybe I grepped before all the files were complete, but two are now in the output:
        "text" : "Aleta Wendo",
        "geoID" : "ETH.10.19.1_1"

        "text" : "Afdera",
        "geoID" : "ETH.2.2.2_1"

How can we avoid the bad locations?

The bad locations are a result of the neural location finder making mistakes. There's no simple way to fix that. Do you have any idea of how frequent they are?


Inability to sync without connection to original validator

in semuxBft,
 // Pick 2/3th active validator's height as sync target. The sync will not be
            // started if there are less than 2 active validators.
            OptionalLong target = activeValidators.stream()
                    .mapToLong(c -> c.getRemotePeer().getLatestBlockNumber() + 1)
                    .sorted()
                    .limit((int) Math.floor(activeValidators.size() * 2.0 / 3.0))
                    .max();

            if (target.isPresent() && target.getAsLong() > height) {
                sync(target.getAsLong());
            }

if a user is syncing from scratch and cannot connect directly to one of the main original seed nodes, they cannot sync.  We should not need to get the height from one of main validators if we are not ourselves a validator.

fixed in #130


Handle c-quoted strings

Fix https://github.com/toltec-dev/toltec/issues/650

This doesn't seem to fix https://github.com/toltec-dev/toltec/issues/650. I still have the issue with toltemk 0.2

This doesn't seem to fix toltec-dev/toltec#650. I still have the issue with toltemk 0.2

Could you open a new issue and provide more context? This fixed the issues for the examples I had at the time. I'll have to take some time to grok the unit tests that have been built to add an item for this as well.


DRILL-4225: TestDateFunctions#testToChar fails when the locale is non-English

Changed to use LocalDate, LocalTime and LocalDateTime to build expectedResults instead of string literals

+1


Extending from Error doesn't work when emitting ES5

I am using Typescript 1.8.10. I am using Node v4.4.7 as my primary means of executing Javascript.
Consider this very simple code (I will refer to this later as "code snippet 1"):
class GenConstructFail extends Error {} let x = new GenConstructFail("Test one two"); console.log(x.message)

I run this with tsc test.ts && node test.js. My expected behavior is that this will print "Test one two". My observed behavior is that it prints only a blank line.
There have been issues filed about this before, the ones I found seem to all link back to #5069 where project member @mhegazy closed the issue and explained "The issue is with how these built in types are hand[led] by the engine. They are extensible as per the es6 spec, but do not think the engines are there yet." However, I believe this is not the correct way to think about the issue.
If I look at the ES2015 spec, I find:

19.5.1 The Error Constructor
The Error constructor is the %Error% intrinsic object and the initial value of the Error property of the global object. When Error is called as a function rather than as a constructor, it creates and initializes a new Error object. Thus the function call Error(…) is equivalent to the object creation expression new Error(…) with the same arguments.
The Error constructor is designed to be subclassable. It may be used as the value of an extends clause of a class definition. Subclass constructors that intend to inherit the specified Error behaviour must include a super call to the Error constructor to create and initialize subclass instances with a [[ErrorData]] internal slot.

The last paragraph here is important. The ES2015 spec requires that Error be subclassable using extends and super(). However, it does not specify Error should be subclassable by other means. Here is what tsc emits when run with the default target of ES5 (I will refer to this later as "code snippet 2"):
var __extends = (this && this.__extends) || function (d, b) {
    for (var p in b) if (b.hasOwnProperty(p)) d[p] = b[p];
    function __() { this.constructor = d; }
    d.prototype = b === null ? Object.create(b) : (__.prototype = b.prototype, new __());
};
var GenConstructFail = (function (_super) {
    __extends(GenConstructFail, _super);
    function GenConstructFail(m) {
        _super.call(this, m);
    }
    return GenConstructFail;
}(Error));
var x = new GenConstructFail("Test one two");
console.log(x.message);

I do not fully understand what the Typescript __extends function is doing, but the generated code for GenConstructCall appears to revolve around expecting it can invoke call on the _super object, in this case Error. However, call is a method on Function.prototype and Error does not have Function.prototype in its prototype chain. Error is an intrinsic object, its prototype is also an intrinsic object (defined in section <IP_ADDRESS> of the spec), and the operations supported on Error, its constructor, and its prototype are all explicitly enumerated. call is not among them.
So in other words, if the code Typescript generates in ES5 mode does not behave correctly with regard to constructor parameters, it is not because the engines have not yet caught up to ES6, it is because Typescript has generated code which is neither correct ES5 nor correct ES6.
In fact, in my testing, I find that ES6 engines that fully support "code snippet 1" above when simply evaluated as code, do not support "code snippet 2" (the Typescript-transpiled-to-ES5 version of the same code). I tested with Chrome version "51.0.2704.106 m" (up to date) and also with "Microsoft Edge 25.10586.0.0 / Microsoft EdgeHTML 13.10586"; in both cases, code snippet 1 printed "Test one two" and code snippet 2 printed a blank line. (A person I talked to on Twitter tested with Node 5.4.1 and saw these same results.) I also found that in both Chrome and Edge, Error("test") produced an Error object with the message "test" (this is a special behavior guaranteed by section <IP_ADDRESS> of the ES2015 spec) but Error.call("test") produced an Error object with a blank message.
So, to summarize: Typescript's ES5 target generates an invalid constructor when Error is extended, it is doing this predictably and 100% of the time, and it is invalid because of the Javascript spec and not because of any particular engine limitation. This should be considered a bug.
Moreover, it seems Typescript could be easily modified to fix this. The problem is that .call invocation. Consider this alternate version of code snippet 1 (let's call this "code snippet 3"):
class GenConstructFail extends Error { constructor(m:string) { super(); this.message = m } }
let x = new GenConstructFail("TEST THREE FOUR"); console.log(x.message)

Here is the Javascript tsc emits for code snippet 3 (let's call this "code snippet 4"):
var __extends = (this && this.__extends) || function (d, b) {
    for (var p in b) if (b.hasOwnProperty(p)) d[p] = b[p];
    function __() { this.constructor = d; }
    d.prototype = b === null ? Object.create(b) : (__.prototype = b.prototype, new __());
};
var GenConstructFail = (function (_super) {
    __extends(GenConstructFail, _super);
    function GenConstructFail(m) {
        _super.call(this);
        this.message = m;
    }
    return GenConstructFail;
}(Error));
var x = new GenConstructFail("TEST THREE FOUR");
console.log(x.message);

The problem with "code snippet 2", at least with V8 and Edge, is that call() is swallowing the arguments to the constructor (which is after all not a real constructor). Assigning the fields after the call() avoids this problem and the code prints "TEST THREE FOUR" even on my old copy of Node 4.4.7.
My suggested fix is that Typescript should detect when it is subclassing Error or one of the built-in Error subclasses (all intrinsics) while in ES5 mode, and in this case generate a constructor which instead of assuming call() works simply takes the arguments to super() and assigns them to this after call(). (And maybe it would be better to find a way to avoid call() altogether if you can, since I see nothing in the spec to guarantee it even exists on Error.)

It's late and I need to go to sleep, but after having experimented with this, I believe that this issue is related to or a duplicate of #7574.

Basically the reason I say it's a duplicate is because if we simply capture the value of the call to super and return it, you get the correct behavior. Try this out:
var __extends = (this && this.__extends) || function (d, b) {
    for (var p in b) if (b.hasOwnProperty(p)) d[p] = b[p];
    function __() { this.constructor = d; }
    d.prototype = b === null ? Object.create(b) : (__.prototype = b.prototype, new __());
};
var GenConstructFail = (function (_super) {
    __extends(GenConstructFail, _super);
    function GenConstructFail() {
        var SUPER_RESULT = _super.apply(this, arguments) || this;
        // substitute any use of 'this' with 'SUPER_RESULT'
        return SUPER_RESULT;
    }
    return GenConstructFail;
}(Error));
var x = new GenConstructFail("Test one two");
console.log(x.message);

In any case, thanks for filing because it shows that this is another good use-case.

Daniel-- I don't think this is a duplicate of #7574, although it is clearly a related problem. At least, your sample code does not work, so if this is the code that a fix for #7574 would produce then it would not resolve this bug.
If I run your code ("code snippet 5"), I find that x.message does have the desired value on both current Chrome and Edge. However, let's say I add two more lines:
console.log(x instanceof Error)
console.log(x instanceof GenConstructFail)

On both Chrome and Edge, x instanceof Error prints true and x instanceof GenConstructFail prints false. So you have fixed the message bug, but created a new bug which is possibly worse because killing x.message results only in lost data and breaking instanceof is likely to result in actual changes to control flow (because program logic decisions are more likely to be based on instanceof than the contents of message).
The reason your sample code does not work is that code snippet 5, just as much as code snippet 2, depends on undefined behavior of Error. Error is to my reading of the spec not guaranteed to have either call or apply and therefore the behavior of call and apply on Error could do nearly anything. In practice (in Chrome and Edge-- other ES2015 engines maybe not) it appears Error.call(this, args) ignores all of its arguments and returns a new Error(), whereas Error.apply(this, args) ignores the this argument, honors args and returns a new Error with "args" as its arguments. So in code snippet 2, the Error.call(this, args) alone on a line has literally no effect and so args are just lost, but this has already been primed with a correct prototype chain so at least instanceof works; and in code snippet 5 the Error.apply(this, args) does (at least in Chrome and Edge) successfully get the arguments into Error, but the previous value of this and therefore the prototype chain are lost.
I believe that the actual bug in this particular issue is that Error is unique and cannot be treated like a constructor or function, and this is an additional issue on top of what #7574 is trying to solve.

Having gotten the opportunity to revisit this in investigating #7574, I now see the issue. However, I'm not sure what we can do here. I think we'd have to do a special check to correctly set the prototypes on certain classes.

I'll bring this up with @bterlson at some point soon.

At the moment, I am working around this by never inheriting from Error, and instead exclusively inheriting from this class:
class CustomError extends Error {
	constructor(message:string) { super() ; this.message = message }
}

This does seem to demonstrate that working around fake-constructor entities is easy, assuming you have the mechanism in place to identify the situations where you need to work around...

@DanielRosenwasser @mcclure  How is this?
var __extends = (this && this.__extends) || function (d, b) {
    for (var p in b) if (b.hasOwnProperty(p)) d[p] = b[p];
    function __() { this.constructor = d; }
    d.prototype = b === null ? Object.create(b) : (__.prototype = b.prototype, new __());
};
var C = (function (_super) {
    __extends(C, _super);
    function C() {
        var _that = _super.call(this, 'error');
        if (_that) {
            _that.__proto__ = this;
        }
        var _this = _that || this;
        return _this;
    }
    C.prototype.m = function () {
        return 'm';
    };
    return C;
}(Error));
console.log(new C().message); // 'error'
console.log(new C().m()); // 'm'
console.log(new C() instanceof Error); // true
console.log(new C() instanceof C); // true

Is there no progress or solution on this topic? It's blocking some of my code like #12097.

Technically this will be fixed in TypeScript 2.1; however, a different part of your code may no longer work. message will now be correctly initialized, however, the prototype chain will be broken. See the write-up documented here.

This workaround worked for me:
export interface IErrorConstructor {
  new (message:string):Error;
}

const CustomError = function(message:string) {
  Error.call(this, message);
  Error.captureStackTrace(this);
} as any as IErrorConstructor;
CustomError.prototype = Object.create(Error.prototype);

class MyError extends CustomError {}

const err = new MyError();
err instanceof MyError;   // true

I wonder why compiler cannot generate the code like this...

@eschwartz Will your workaround work when targeting ES5?

What's the status of this? This took us a while to find out what was going when switching our targets from ES2015 to ES5.


Fix Flip Resets

As it is now you can't jump nor dodge after falling off the ceiling or otherwise not jumping off of a surface, this should fix that.

Not sure when this broke cause it worked at some point when I tested it, but thanks.


Json generator: null values now placed in json

I notice that in latest apidoc (0.11.4), the json generator has been updated. The json generated now contains null values where they used to be absent.
Is this intentional?
Thanks

+1

Thanks for reporting - not intentional and we'll fix (looking into the bug now and if quick will have a patch shortly)

FYI - fixed in https://github.com/mbryzek/apidoc-generator/pull/64 and will be deployed today

fix is in production

Thanks!


Adding developer portal dev workflow and config

This PR:

Adds a github action that deploys dataplane docusaurus content into dev portal dev bucket, triggered manually
Adds a docusaurus config necessary to remove the landing page so it can work from a subdirectory

We will simplify the docusaurus configs later once production deployment is in place

merging, it only has affect on the dev portal deployment.


Random crashes in BlurTransformation using renderscript

Tried adding a new BlurTransformation(context, BLUR_SIZE); transform to a listview with many graphical elements. Randomly when I scroll up/down I get stack-less traces. The debug log shows only a native renderscript library crash at some point:
10-17 11:46:06.944 32483-32483/test.hiyouapp D/ImagePostTarget: Did load thumbnail!
10-17 11:46:06.956 276-276/? I/DEBUG: [2016-10-17 11:46:06.956]
10-17 11:46:06.956 276-276/?  W/NativeCrashListener: Couldn't find ProcessRecord for pid<PHONE_NUMBER>
10-17 11:46:06.956 276-276/? I/DEBUG: Build fingerprint: 'lge/jagnm_global_com/jagnm:5.0.2/LRX22G.A1440040099/152321208d526:user/release-keys'
10-17 11:46:06.956 276-276/? I/DEBUG: Revision: '6'
10-17 11:46:06.956 276-276/? E/DEBUG: AM write failure (32 / Broken pipe)
10-17 11:46:06.956 276-276/? I/DEBUG: ABI: 'arm'
10-17 11:46:06.956 276-276/? I/DEBUG: pid: 32483, tid: 2483, name: RSMessageThread  >>> test.hiyouapp <<<
10-17 11:46:06.957 276-276/? I/DEBUG: signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0xba8
10-17 11:46:06.967 991-1786/? I/ActivityManager: Start proc com.android.externalstorage for content provider com.android.externalstorage/.ExternalStorageProvider: pid=2488 uid=10005 gids={50005, 9997, 1028, 1015, 1023} abi=armeabi-v7a
10-17 11:46:06.978 276-276/? I/DEBUG:     r0 00000000  r1 96587b0c  r2 00000000  r3 00000000
10-17 11:46:06.979 276-276/? I/DEBUG:     r4 00000000  r5 13c91ca0  r6 765cd000  r7 00000000
10-17 11:46:06.979 276-276/? I/DEBUG:     r8 13903e10  r9 b043d800  sl 139d50c0  fp 00000000
10-17 11:46:06.979 276-276/? I/DEBUG:     ip a959cf08  sp 96587af8  lr 73dbb5fd  pc b66aeb6c  cpsr 600b0030
10-17 11:46:06.979 276-276/? I/DEBUG: backtrace:
10-17 11:46:06.979 276-276/? I/DEBUG:     #00 pc 0001eb6c  /system/lib/libRS.so (android::renderscript::Context::initToClient()+11)
10-17 11:46:06.979 276-276/? I/DEBUG:     #01 pc 001125fb  /system/framework/arm/boot.oat
10-17 11:46:07.050 991-1023/? D/sensors_hal_Time: time_service_sensor1_cb: msg_type 2
10-17 11:46:07.050 991-1023/? D/sensors_hal_Time: time_service_sensor1_cb: Sn 24, msg Id 3, txn Id 0
10-17 11:46:07.050 991-1023/? D/sensors_hal_Time: tsOffsetIs: Apps:<PHONE_NUMBER>362; DSPS: 201098642; Offset : -2627626316

While running attached to Android Studio I get console logs like:
V/RenderScript: Successfully loaded runtime: libRSDriver_adreno.so
V/RenderScript: 0xb041fe00 Launching thread(s), CPUs 4
V/RenderScript: 0x9e429a00 Launching thread(s), CPUs 4
V/RenderScript: 0x9d4ea600 Launching thread(s), CPUs 4
V/RenderScript: Successfully loaded runtime: libRSDriver_adreno.so
V/RenderScript: Successfully loaded runtime: libRSDriver_adreno.so
V/RenderScript: Successfully loaded runtime: libRSDriver_adreno.so
V/RenderScript: 0xb0417200 Launching thread(s), CPUs 4

                --------- beginning of crash
A/libc: Fatal signal 11 (SIGSEGV), code 1, fault addr 0xba8 in tid 15411 (RSMessageThread)
V/RenderScript: Successfully loaded runtime: libRSDriver_adreno.so
V/RenderScript: 0xb041fe00 Launching thread(s), CPUs 4
Disconnected from the target VM, address: 'localhost:8604', transport: 'socket'

Removing the blur transform (I have other chained like rounded corners) makes the app solid again and not crashable. This suggests there is a bug in the renderscript implementation of the blur transform. Not sure how this can be debugged, posting here for suggestions. Tested devices include Android 5.x and 6.x.

@gradha same problem. any solutions?

I remember looking at the source and there being a fallback method for devices not supporting renderscript which used software blur, so you could try forcing that at the cost of performance. For whatever reason I ended up discarding the blur effect and didn't look further at this. Good luck.

@gradha I will likely remove the blur as well. I see it happen if I try to transform many images at the same time (scroll really fast on the RecyclerView). The device I'm testing on which crashes still transforms the images so it seems like it does have Renderscript, then could it be a memory issue?

I have no idea about that.


Some sites redirect back to the proxy

Some sites I have noticed redirect back to the proxy with a query parameter like so, for example if I am running the proxy here http://local.com/app_dev.php/proxy-url
Then the redirect s to
http://local.com/app_dev.php/proxy-url?q=���թmcf����ؕ��ۨ�ƣ���ҝ`tר�����թXgxUd|Y�z��ɤ��c�ߣו������^���
URL decoding that results in this garbage
���թmcf����ؕ��ۨ�ƣ���ҝ`tר�����թXgxUd|Y�z��ɤ��c�ߣו������^���
This only happens on certain sites and I cannot see why its happening nor find a pattern.

To which sites does this happen to?

https://magora-systems.com/

All parts of that site seem to work fine for me. Try it:
https://unblockvideos.com/


Ollama spins up USB HDD

What is the issue?
When ever I run an Ollama model, Ollama now spins up my external USB hard drive despite not needing to as all the models are on the internal drive.
I can't say I've always noticed it doing this, although it has always spun up the hard drive when upgrading as it seems to scan USB?
Is there anyway to stop Ollama doing this by disabling any kind of USB scan functionality etc?
This is on a raspberry pi with internal nvme (where the models are) and an external USB that Ollama didn't need.
OS
Linux
GPU
No response
CPU
No response
Ollama version
0.2.3

ollama doesn't explicitly do a USB scan on startup, but it does check various places on the filesystem looking for libraries, config files, etc.  If your external drive is mounted and one of the places that ollama check references a location on the USB filesystem, that will cause the drive to spin up.
You can check where ollama is looking by tracing its syscall activities:
strace -f -e openat,newfstatat,readlinkat -o /tmp/ollama.strace ollama serve

For example, on my pi ollama checks /opt/cuda, so if I had a USB drive mounted on /opt, that would cause the drive to activate.


createOutputChannel languageId param should use log instead of Log

Disable Extensions:
Yes
Documentation:

When use Log:
let outputChannel: OutputChannel | undefined;
export const logger = {
    log(message: string, active: boolean): void {
        if (outputChannel === undefined) {
            outputChannel = vscode.window.createOutputChannel('Neo File Utils', 'Log');
        }
        outputChannel.append(`${message}\n`);
        if (active) {
            outputChannel.show();
        }
    },
    dispose(): void {
        outputChannel?.dispose();
    },
};

When use log:

Versions:
Version: 1.76.1 (Universal)
Commit: 5e805b79fcb6ba4c2d23712967df89a089da575b
Date: 2023-03-08T16:32:09.831Z
Electron: 19.1.11
Chromium: 102.0.5005.196
Node.js: 16.14.2
V8: <IP_ADDRESS>-electron.0
OS: Darwin x64 22.3.0
Sandboxed: No

@sandy081

This is correct that the normal output channels use Log as the default language id and hence they are not colored by default. log language id is used for the logging output channels.


out-of-place-testing

Building out of place works correctly, but testing out of place
does not, gtest links are broken and the license header check
does not work.

Seems like ronn man page generation does not work with out of place builds either.

This still doesn't work.


Repo sync for protected CLA branch

The pull request is created from master637640603579004222 to master to fix git push error for protected CLA branch

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


Path in window title bar not correct on Linux

Path shown in the window title bar is always shown only for the first opened file and doesn't change when switching tabs. It even stays on after all tabs are closed. System is Ubuntu 14.04 LTS.

Thanks for the report @miishke -- I think the core problem here is already covered in https://github.com/atom/atom/issues/5058 and https://github.com/atom/atom/issues/7614, so I'm going to close this in favor of those two issues to keep things focused. If you'd like, please leave a comment on those issues or just subscribe for updates. And please let me know if I've misunderstood your report.


The CSS Custom Property Regex Does Not Allow Underscores

Expected Behavior
"--test_ing: 33" should be converted to {"--test_ing": "33"}
Actual Behavior
"--test_ing: 33" is converted to {"-Test_ing": "33"}
Steps to Reproduce
Create a JS file with the following contents and run it:
const styleToObj = require("style-to-js");
console.log(styleToObj("--testing: 33; --test_ing: 33"));

The output will be:
{ '--testing': '33', '-Test_ing': '33' }

Reproducible Demo
JSFiddle: https://jsfiddle.net/2pbnvoa6/
Environment

Version: 1.1.15

Fix
This behavior is caused by an error in the CUSTOM_PROPERTY_REGEX constant. It is:
const CUSTOM_PROPERTY_REGEX = /^--[a-zA-Z0-9-]+$/;

It should be:
const CUSTOM_PROPERTY_REGEX = /^--[a-zA-Z0-9_-]+$/;

@joshualip-plaudit would you like to open a PR?

I don't have the project checked out, so it'd probably be faster for you to make the update?
I can get started on one, though.


[ISSUE #3755] change the level to warn when ack failed

Make sure set the target branch to develop
What is the purpose of the change
#3755
Brief changelog
XX
Verifying this change
XXXX
Follow this checklist to help us incorporate your contribution quickly and easily. Notice, it would be helpful if you could finish the following 5 checklist(the last one is not necessary)before request the community to review your PR.

[x] Make sure there is a Github issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a Github issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[x] Format the pull request title like [ISSUE #123] Fix UnknownException when host config not exist. Each commit in the pull request should have a meaningful subject line and body.
[x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[x] Write necessary unit-test(over 80% coverage) to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add integration-test in test module.
[x] Run mvn -B clean apache-rat:check findbugs:findbugs checkstyle:checkstyle to make sure basic checks pass. Run mvn clean install -DskipITs to make sure unit-test pass. Run mvn clean test-compile failsafe:integration-test  to make sure integration-test pass.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

Coverage increased (+0.01%) to 52.549% when pulling<PHONE_NUMBER>ceacc6aa89d7d2743ac3d080ffad1e on cserwen:pop_fix_9 into 03526d8c0f8cee45d11dc720353e0e533bff36c7 on apache:5.0.0-alpha.

Codecov Report

Merging #3756 (4421342) into 5.0.0-alpha (03526d8) will decrease coverage by 0.07%.
The diff coverage is 0.00%.

@@                Coverage Diff                @@
##             5.0.0-alpha    #3756      +/-   ##
=================================================
- Coverage          46.50%   46.43%   -0.08%
+ Complexity          5329     5319      -10
=================================================
  Files                641      641
  Lines              44342    44342
  Branches            6117     6117
=================================================
- Hits               20622    20589      -33
- Misses             20999    21035      +36
+ Partials            2721     2718       -3

Impacted Files
Coverage Δ

...lient/impl/consumer/DefaultMQPushConsumerImpl.java
32.21% <0.00%> (ø)

...apache/rocketmq/broker/longpolling/PopRequest.java
31.03% <0.00%> (-13.80%)
:arrow_down:

...org/apache/rocketmq/store/ha/WaitNotifyObject.java
66.07% <0.00%> (-5.36%)
:arrow_down:

...apache/rocketmq/remoting/netty/ResponseFuture.java
85.00% <0.00%> (-5.00%)
:arrow_down:

...rocketmq/remoting/netty/NettyRemotingAbstract.java
47.05% <0.00%> (-4.05%)
:arrow_down:

...ava/org/apache/rocketmq/test/util/VerifyUtils.java
46.26% <0.00%> (-2.99%)
:arrow_down:

...tmq/logappender/log4j2/RocketmqLog4j2Appender.java
35.00% <0.00%> (-1.67%)
:arrow_down:

...rocketmq/client/impl/factory/MQClientInstance.java
47.35% <0.00%> (-1.40%)
:arrow_down:

...mq/client/impl/consumer/RebalanceLitePullImpl.java
47.94% <0.00%> (-1.37%)
:arrow_down:

...che/rocketmq/acl/plain/PlainPermissionManager.java
70.53% <0.00%> (-1.34%)
:arrow_down:

... and 7 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 03526d8...4421342. Read the comment docs.


Refactor echtvar encode

To set a name for the database/frequency label that the INFO field of a VCF is labeled with.

[ ] Give a json as input to echtvar anno
[ ] Store a default json assets/ that can be overwritten with  a param.

[ ] Change the current COHORT_AF to CASE_AF, or just AF?

Can be started after we have decided on project/case_id.

On hold because ecthvar encode was removed in #502.


Re-consider content shown in SideBar

Let's discuss the sidebar"

It works OK, but I'm struggling with deciding on how the content inside it is established. Currently, the Server constructs a list of all the items who say "I'm a child or the Drive". But this introduces some weird scenarios:

If I want to guide visitors to some specific page, I have to make that item a direct child of the Drive. That would make the hierarchy very consistent, but it could also frustrate a user, for example if they had a certain Product that they want to feature, which actually is a child of the Products resource.
Since various resources set the Drive as their default Parent (including all Collections), this leads to a bloated navigation

Solutions

Nest all auto-generated collections under the Collections resource.
Add a new menuItems property to the Drive, and allow users to manually set these. If this property is present, show the menuItems instead of children.
Go all-in on the hierachy viewer inside the sidebar, similar how to Notion structures pages #96

I think #75 already summed up what I actaully want to achieve


Refactor of Subscriptions

Description
As in the issue, a user has to be informed about bad inputs.
Changes proposed in this pull request:

Renamed Event Subscription to Subscription
Rename directories and paths from Event Subscription to Subscription
Improve tooltips and placeholders
Change input Event type in the Simple view to the MessageStrip
Add Sink as a MesssageStrip

Related issue(s)
Closes #767

/retest

/retest

/retest


Add CI job to test generated JAR package

In order to check if our package is created correctly, a new job should be added to test it isolated from the source files. To achieve this, I created a new job that generates the JAR file and test it using our test/ folder. The tests runs in the target/ folder, which means that Clojure command will not look up the deps.edn or the src/ folder.

LGTM :heavy_check_mark:


feat(snippets): Update reactions with javascript

Summary of changes and context
The point of this PR is to make the reaction smoother by updating the DOM without refreshing (to avoid jumping back to the top at every interactions) and updating the DB with fetch
Javascript now handles selecting the correct path to fetch so we don't need the 3 different buttons per reaction anymore.
In order to respond to the Stimulus controller, the ReactionsController now only render json objects instead of redirecting or rendering ViewTemplates.
https://github.com/pil0u/lewagon-aoc/assets/75388869/535d25b7-3c99-4e15-a3a0-3ba3069a308d
Sanity checks

[x] Linters pass
[x] Tests pass
[ ] Related GitHub issues are linked in the description

J'avais pas de changement de prevu non, pour moi ca peut etre merge

🚀


Disabled Prop

Is ther any way to disabled the main fab button?

There is not right now but I am going to add the ability to spread props to any off the underlying components. That should add this feature. I will try and get to that by the weekend.

Here is a way to achieve this. I know it's not very elegant, but it does the job.
https://codesandbox.io/s/magical-swirles-txq1l?file=/src/App.js


Fix hystrix dashboard repo link on README.md

Codecov Report

Merging #51 into master will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #51   +/-   ##
=========================================
  Coverage     79.42%   79.42%
  Complexity      230      230
=========================================
  Files            51       51
  Lines           588      588
  Branches         12       12
=========================================
  Hits            467      467
  Misses          119      119
  Partials          2        2

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 20237e6...8f0bb19. Read the comment docs.

Sorry My pull request is already a mess I will then close it and open others in order to have clean pull requests


Write a doc about contributing (with architecture, design and a code example)

I feel that if I document how this app is designed and provide a real-case example of how to add features to it, it will get much more PRs and with community help will improve much faster than I can do it on my own.

I did explain a bit of the app key design concepts here: https://github.com/egnyte/gitlabform/blob/master/FEATURES_DESIGN.md

I updated and added info about what to read and where to start to the Contributing section of the README.


 I've tried adjusting all the settings but it keeps happening. Any ideas?
I'm using:
v12.5.0 APK and Windows client.
Win 10 version: 2004
GPU: RTX 2070 Super
CPU: i5-8600K

This appears to happen on the Quest 1 as well as on the Quest 2
The fact that this also occurs in other streaming solutions with SteamVR makes me think it's SteamVR causing it
VD on Oculus doesn't get this, however VD on steamvr does

I'm experiencing the same issue, which has led to some nausea, but it only began a few days ago for me.
It occurs consistently at all times in all applications including steamvr home, but does not affect either menu.
I have tried rebooting both headset and the host computer with no effect.
There is zero frame drop and packet loss.

I have some stuttering whenever I turn my head on the quest 2 in the steamVR menu.
Once I'm in a game it seems to run a bit smoother, but then as the OP said will get random sections of stuttering.
No warnings or errors in the logs for ALVR.
I just set this up today so no comment on prior builds.

https://www.youtube.com/watch?v=PK4FzEoneu8

link doesn't seem to work


Fix -1 value issue

Description: Fixed issue where Radio Thermostat will sometimes return a current temperature or set temperature value of -1
Checklist:
If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated in home-assistant.github.io

If the code communicates with devices, web services, or third-party tools:

[ ] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[ ] New dependencies have been added to the REQUIREMENTS variable (example).
[ ] New dependencies are only imported inside functions that use them (example).
[ ] New dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[ ] New files were added to .coveragerc.

If the code does not interact with devices:

[ ] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[ ] Tests have been added to verify that the new code works.

I think any immediate retry for these devices is a bad idea.  They can often take seconds to respond, especially if you happen to make a local request when it's syncing with the cloud service.
To me the better option is to just discard the bad value and try again on the next poll interval.

I've done a good bit of testing and have found that an immediate retry will
typically resolve the invalid value issue. I've let a loop constantly
polling the stats running in my shell with no negative effect.
On Jul 8, 2017 10:59 PM, "John Mihalic"<EMAIL_ADDRESS>wrote:
I think any immediate retry for these devices is a bad idea. They can often
take seconds to respond, especially if you happen to make a local request
when it's syncing with the cloud service.
To me the better option is to just discard the bad value and try again on
the next poll interval.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/home-assistant/home-assistant/pull/8395#issuecomment-313896718,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGquZY9lTrwemQ47gDT1U4Xw37616Apdks5sMFASgaJpZM4ORMlk
.

What type of device are you testing on?  I've had issues in the past with any quick polling on a 3M50 device.  I was even able to lock up the unit by flooding it with continuous requests over 30 seconds or so.

Mine is a CT50 (V1.94) running firmware 1.04.84. I assume the 3M50 and this unit are identical minus some branding. I've not ever been able to lock the unit up and a poll of /tstat has always been promptly returned within 5 seconds or so even when run on a loop for hours. Has your rapid polling waited for a response before querying again?

Yeah a CT50 and 3M50 should be the same.
I guess to me a 5s return time is pretty slow, so i'm cautious on putting in a mechanism that could potentially continually make requests in an error scenario.  Since the poll rate is every 30s, with this change if something failed out for some reason and the api was returning -1, taking 5s or longer to do so every time, with 5 retries per poll period we could potentially be continually hitting the unit.
If an immediate retry usually fixes it in your testing how about just allowing one retry per pole period on a bad value.  If this retry doesn't fit it, then discard.  Would that take care of the majority of cases?

While I don't necessary share the same concerns as you regarding a continual poll (in the rare case that it even got to that) I do think a one-and-done retry would be a reasonable middle ground. I'm going to go ahead and make this change on my custom component and test it over the next few hours. I'll reflect the change in this request assuming things go well. Thank you for your thoughts!

I'm agree with @mezz64. A polling device need no retry in update. If the state is fetch on a update period it will be fetch in next update period. Otherwise we lock the thread for no big reason. and if the state is 20sec behind the reality, that is also no big thing. Block the thread and hit the API is bad

@pvizeli, I agree. No need to try to attempt another lookup and lock a thread when we'll retry in 30 seconds anyways.


docs: Updates Android permissions docs

This picks up where #661 left off and includes the feedback from @helenaford

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

Thank you!

I assume the code quality check errors are expected?
fwiw I could create a separate PR to propose fixes for the typescript build validation errors?
Looks like it just needs a couple of things removed or commented out in the example/app.tsx.

Oh! Those are not expected. You've already got a conventional commit going so it would even be re-basable if you just added a style(lint): fix typescript errors in tests app commit on there.... otherwise, they're unrelated to this PR so I wouldn't hold it up on that

Ok, not sure if it's preferred to manually remove/comment them out - otherwise I just added some ts-ignore comments which also does the trick.

thank you!! merged 😎 🚀


Update web_accessible_resources matches to include https://chat.zhile.io

Accessing chat.openai.com from China can be difficult. As an alternative, users can access chat.zhile.io instead. Please add this domain to the matches so that Chinese users can also use this talent plugin 🙏🙏🙏.

I am not familiar with chat.zhile.io, I'll add it to the next version, but is this website uses the same interface, like a proxy or something? Even if there is a small change in the design, it might not work as we expected. Did you have a chance to try it locally?

Yes, I have tested locally and it works well. The web element and selector are seem to the office site and the author will sync the change if the offical website changes .


Tolerate default commit signing with SSH in tests

Tolerate default commit signing with SSH in tests
work around https://bugs.eclipse.org/bugs/show_bug.cgi?id=581483
If the current git setup has SSH based code signing enabled (gpg.format=ssh)[1] then the tests fail (even though not signing) as jgit fails to parse the config with an error like:
java.lang.IllegalArgumentException: Invalid value: gpg.format=ssh
        at org.eclipse.jgit.lib.DefaultTypedConfigGetter.getEnum(DefaultTypedConfigGetter.java:103)
        at org.eclipse.jgit.lib.Config.getEnum(Config.java:454)
        at org.eclipse.jgit.lib.GpgConfig.<init>(GpgConfig.java:86)
        at org.eclipse.jgit.api.CommitCommand.processOptions(CommitCommand.java:662)
        at org.eclipse.jgit.api.CommitCommand.call(CommitCommand.java:189)
        at org.jenkinsci.plugins.gitclient.JGitAPIImpl.commit(JGitAPIImpl.java:487)
        at org.jenkinsci.plugins.gitclient.GitClientMaintenanceTest.commitFile(GitClientMaintenanceTest.java:230)
        at org.jenkinsci.plugins.gitclient.GitClientMaintenanceTest.commitOneFile(GitClientMaintenanceTest.java:224)
        at org.jenkinsci.plugins.gitclient.GitClientMaintenanceTest.commitSeveralFiles(GitClientMaintenanceTest.java:218)
        at org.jenkinsci.plugins.gitclient.GitClientMaintenanceTest.test_gc_maintenance(GitClientMaintenanceTest.java:333)
        at java.base/java.lang.reflect.Method.invoke(Method.java:566)

[1] https://git-scm.com/docs/git-config#Documentation/git-config.txt-gpgformat
This has only been tested on my local windows development environment. before this change, tests failed as above.
After this change the only failing test is
 GitClientTest.test_git_ssh_executable_found_on_windows:3393 » Runtime ssh executable not found. The git plugin only supports official git client https://git-scm.com/download/win

which is a lie, but somewhat expected as this installation of the official git client did not install ssh or any mysys tools.
Checklist

[x] Unit tests pass locally with my changes

Types of changes
What types of changes does your code introduce?

[x] Test fix (non-breaking change which updates dependencies or improves infrastructure)

@jtnord I pushed changes that allow the pull request to pass tests in my environments (Linux, Windows, FreeBSD, etc.) and should pass tests on ci.jenkins.io.  Could you test the most recent changes on your Windows environment?

@jtnord I'm out of office for the next week but may have time for further reviews and changes.  I see a pattern of repeating code in those tests that I would like to fix, if you're OK with me using this draft pull request to improve the tests.  I would need you to tell me if the tests that I've modified still pass on your Windows computer.

@MarkEWaite all[1]  tests pass, however something is still missing the --local and messing with the actual clone of the repo.
after running tests my clone has the following new config options ->
commit.gpgsign=false
tag.gpgsign=false
gpg.format=openpgp

Which is unrelated to the tolleration of ssh commit signing, but if you are also looking to cleanup / refactor local setting may be something to look at at the same time,
[1] with the exception of GitClientTest.test_git_ssh_executable_found_on_windows:3393 which is somewhat expected for my environment given the test.

after running tests my clone has the following new config options ->
commit.gpgsign=false
tag.gpgsign=false
gpg.format=openpgp

Which is unrelated to the toleration of ssh commit signing, but if you are also looking to cleanup / refactor local setting may be something to look at at the same time,

Thanks.  I've previously accepted persistent changes in the configuration of the working repository to support tests, but this may be the ideal time to fix that poor behavior.

@MarkEWaite pklease @mention me when you would like me to run the tests locally again.

@jtnord I've fixed the duplications that I had created in the tests.  I've run the tests successfully on my Linux machine from a user configuration that has GPG signing enabled globally and I've run them successfully on my Linux and Windows machines where GPG signing is not enabled.  Could you check them as well?
@olamy I don't want to disrupt your work on the switch from trilead to Apache Mina.  Once this has been reviewed and verified by @jtnord, I'm happy to wait until your work on the switch from trilead to Apache Mina is complete  If you find that these changes won't disrupt your work on the switch from trilead to Apache Mina, they can be merged as soon as they are confirmed to pass tests in all the desired configurations.
Thanks again to both of you!

@MarkEWaite no worries at all. the changes in this PR are different from my current work from now
Better to do this now as I may change those classes (*Test*) as well later next week :)

tests all pass locally with the exception of the known GitClientTest.test_git_ssh_executable_found_on_windows
However it is still modifying my local config.
commit.gpgsign=false
tag.gpgsign=false

[ERROR] Errors:
[ERROR]   GitClientTest.test_git_ssh_executable_found_on_windows:3371 » Runtime ssh executable not found. The git plugin only supports official git client https://git-scm.com/download/win

❯ ssh -V
OpenSSH_for_Windows_8.6p1, LibreSSL 3.4.3

❯ where ssh
C:\Windows\System32\OpenSSH\ssh.exe

yup confirmed as well.
grhh need to go to almost every test changing the config :(


Devel

enable motor pin on gpio 5

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


Multiple time periods fix

Fixes error in syntax for relative time and adds comments about not supporting using multiple time periods in queries for both absolute time and relative time.

Fixes #1511


Add extension points for adapter notes and control object filters in metadata reader

Situation
The extracted code from EVSL still hat remnants of the table protection code in it that are RLS-specific. That means it should neither be in EVSL nor in EVSCL. Instead, we need extension points that allow adding adapter notes and filtering unwanted control tables or columns in the derived implementations.
Acceptance Criteria

Extension point exists that allows to define the adapter properties in the metadata reader
Extension point exists that allows to filter out control tables
Extension point exists that allows to filter out control columns

After experimentation it turned out that these extension points are not really needed. So we will scrap this ticket and the corresponding PR.


Ensure WM docker images - and databases - properly handle signals

Impact of the new feature
WMCore (can easily cover all of the DMWM though)
Is your feature request related to a problem? Please describe.
As we commission and plan to move our services to container solution, and triggered by a question of "docker stop" vs "docker kill", I came across a post explaining the importance of propagating and handling process signals, see:
https://vsupalov.com/docker-compose-stop-slow/#:~:text=Docker has limited patience when,for 10 seconds at least.
Describe the solution you'd like
As described in the link above, we need to verify 3 things:

In the Dockerfile: we need to use the "exec form" for the ENTRYPOINT
In the ENTRYPOINT script: execute the application/process with the exec command.
In the ENTRYPOINT script: we might have to trap signals

to ensure that our applications - and the database images - are able to gracefully stop the processes.
It might be that it is all already implemented, but we need to cross-check these aspects and make changes whenever necessary.
Describe alternatives you've considered
In addition, note that stopping the WMAgent container might take more than 10 seconds (given that it has to gracefully stop almost 20 components), so we need should probably consider something like docker stop wmagent --time 30, to give more it more time before sending in a SIGKILL.
Additional context
None

@belforte @novicecpp @mapellidario this might be interesting/useful to you as well.

hi @amaltaro

In the ENTRYPOINT script: we might have to trap signals

At the current stage it is fairly easy for us to trap those signals ... our entry point is well defined and ease to add such a signal handling mechanism. But the question is ... What we gone do with it after catching the signal.  Because it is going to be like a python exception handling, there will be no effect of it if we do not take the proper actions. And even worse, it will catch the signal and if we fail to properly exit the main process, we will be struggling to kill those containers in real life.
The only thing which comes to mind could be worth executing before killing the container is actually : manage stop-agent.
But after that you cannot kill the entry point process so easily. Here is solid example:

Our entry point is run.sh
If we  trap a SIGKILL signal and upon that we execute: manage agent-stop . Then it is our obligation to kill run.sh
Here is how the process order looks like inside our containers:

(WMAgent-2.3.3) [cmst1@vocms0260:current]$ ps auxf
USER         PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
cmst1      57541  0.0  0.0   6168  2488 pts/1    Ss   15:14   0:00 bash
cmst1      57661  0.0  0.0   8632  1656 pts/1    R+   15:16   0:00  \_ ps auxf
cmst1       2866  0.0  0.7<PHONE_NUMBER>6 ?        Sl   May07   0:06 python /usr/local/bin/wmcoreD --start --config=/data/srv/wmagent/2.3.3/config/config.py
cmst1       2857  0.0  0.7<PHONE_NUMBER>6 ?        Sl   May07   0:12 python /usr/local/bin/wmcoreD --start --config=/data/srv/wmagent/2.3.3/config/config.py
...
cmst1        596  0.0  0.0   6292  2576 pts/0    Ss+  May07   0:00 bash
cmst1          1  0.0  0.0   6044  2044 ?        Ss   May07   0:00 /bin/bash ./run.sh 2>&1
cmst1        595  0.0  0.0   4268   624 ?                Sl   May07   0:06 python /usr/local/bin/wmcoreD --start --config=/data/srv/wmagent/2.3.3/config/config.py
cmst1       2857  0.0  0.7<PHONE_NUMBER>6 ?        Sl   May07   0:12 python /usr/local/bin/wmcoreD --start --config=/data/srv/wmagent/2.3.3/config/config.py
...

NOTE: we may need to investigate deeper on that

The only explanation I may have is the running sleep infinity process at the end of run.sh and this one is a fork, which has a completely different PID, in this case  it is 595

So the only way to kill the entry point is by killing this exact process...  But this  means in order for us to properly kill that process we will have to know this exact PID at the time we are setting the trap (the signal handling mechansim). and since it is the last one to run inside the run.sh it would be quite challenging...  to get  that number.

There are  tricks we can use of course ... not a single one even .... many... But we need to pay attention to those details and justify... is it worth going into those complications.

I can't keep up to dare personally with everything here. Too much for my old age. But IIRC @novicecpp has already deal with this in our new post-rpm containers. I would be really delighted if you could find a common ground.

In my view the proper solution is to get rid of sleep which was introduced because we redirect logs and in fact run python command and let it produce stdout/stderr.  This is a common way all other containers run, they run whatever the command/executable is and let it run with stdout/stderr such that it can be both inspected and killed. What we have is a hack to preserve RPM based procedure within container, i.e. redirect logs, log into container and re-start service, etc.

What we have is a hack to preserve RPM based procedure within container, i.e. redirect logs, log into container and re-start service, etc.

Very unfair comment!
As you probably know, the agent actually runs +15 components and making all of them spit logs out to stdout is the same as having no logs at all (too large volume making it useless).

Alan, there is nothing unfair in a comment per-se. And, it is true that we transition from a previous based deployment procedure. It also true that all our service originally was not designed to run in container, and had different deployment model, and this model was based on host VM and RPMs. If we'll be able to do it from scratch and we need to run each individual component in its each container or side car, separate as much as possible in order to gain the control of runtime and logs in new environment.

IF we ever get to the point that each container will be running in its own container, there will be anyways a lot of refactoring. That would be the ideal moment to consider it. BTW, note that there is no kubernetes at all involved in this discussion neither we plan on moving to kubernetes.
Anyhow, @belforte if you can share any potential solutions that you/CRAB team has already found, please do share with us.

CRAB story in a nutshell:
We currently run 4 services as containers: TaskWorker, PublisherForOldASOwithFTS, PublisherForASOwithRucio, Monitor and use same container image with different startups scripts, just for convenience.
PID 1 is something like  /bin/sh -c sh /data/run.sh and and env. var. is passed at docker run time to tell it which service to run.
That's easy and nice. We have not put anything to stop things gracefully when docker stop time. Currently if we want to stop a service for some reason, we log into the container and execute stop.sh for a graceful termination.  But one could certainly issue docker exec -ti TaskWorker /data/srv/TaskManager/stop.sh. That's e.g. how we deploy a new version via Jenkins (Wa is changing that to a gitlab pipeline but I think it is same concept).
I am no sure what problem you want to solve. I do not think that you need to trap signals from outside the container.  And since you are in control, you do not need to issue docker kill or 'docker stop` if you do not want to.
Or do you want to use some container management tool  ? With one container for agent it seems a bit overkill.
Of course if VM reboots or its hypervisor goes somehow bellyup, there wlll be no graceful stop, but it is extremely rare and hopefully application is not too much stateful.
K8s and "Lassi's application manager" are a different story, we are using what Valentin set up few years ago when he moved CMSWEB to K8s. I know that Wa has changed things a bit for the rpm-free version, but if I try to summarize I will make mistakes.

@belforte, the new PyPI image still not dealing with termination properly. Sorry, I just discovered this when Alan tag us on this issue.
I use tini as PID 1 to execute /bin/sh -c sh /data/run.sh where it runs sleep forever. tini does not propagate signal to main python processes, but only helps container shutdown faster by tini getting terminated (bash as PID 1 does not) and OS reap other processes inside the container with SIGKILL. We still need trap signal in /data/run.sh to terminate python process gracefully.
The  start, stop, and running of the latest version from git are so convenient for us to test/debug inside the container on-the-fly. So, the double fork and sleep forever loop are still needed for us unless we discover a better way to test/debug and whether it is worth changing this behavior.

@novicecpp but we can still do docker exec -ti TaskWorker /data/srv/TaskManager/stop.sh right ? I have not understood yet which exact problem Alan (or us) needs to solve. Maybe we can talk inside CRAB first.

Thanks for the hint Stefano, indeed that is something we can do for WMAgent as well. I'll give it a try in parallel to an idea or two that also come to mind.

@anpicci Yes please, sounds good to me.

@anpicci I see you have many other tests in your pipeline. As this might require modifications and further debugging, I would highly recommend to leave this one up to @khurtado  (and we/you help him on demand).

@amaltaro that's fine with stepping back for now, and possibly help if necessary. How does that sound @khurtado?


Glitch for clue scroll answers

Upon attempting a challenge scroll answer, pressing space closes the dialogue without a chance to enter an answer. Upon relogging the user input box appears, but a graphical glitch appears upon trying to fill it. Only observed at Otto godblessed clue step.
Expected behavior
To be able to complete the clue
Screenshots
https://imgur.com/bdDGao5

OS: Windows 10
RuneLite version: 1.5.16
Launcher version: Unknown

Restart your client

this was fixed in 776d27cc4772d9ad3c779a2799ecef9a12aa0904


Usage in factories?

I have a factory like so
import Factory from '@ioc:Adonis/Lucid/Factory';
import ServiceProviderProfile from 'App/Models/ServiceProviderProfile';
import { ResponsiveAttachment } from '@ioc:Adonis/Addons/ResponsiveAttachment';
import { readFile } from 'node:fs/promises';
import { join } from 'node:path';

export default Factory.define(ServiceProviderProfile, async ({ faker }) => {

  const avatarImage = await ResponsiveAttachment.fromBuffer(
    await readFile(join(__dirname, '../../tests/resources/default-avatar.png'))
  );

  await avatarImage.setOptions({
    forceFormat: 'webp',
    keepOriginal: true,
    folder: 'avatars/service-provider',
    breakpoints: {
      xlarge: 1200,
      large: 800,
      medium: 300,
      small: 100
    }
  });
  await avatarImage.save();

  return {
    name: faker.name.findName(),
    avatar: avatarImage, // this ends up as null
    about: faker.random.words(100),
    specialties: faker.random.words(5).split(' ').join(', ')
  };
}).build();

The images are processed and saved to disk. avatarImage is the correct object before the return. Is there something else I need to do to make this work in a factory?

So I've done some digging and found that if in my model decorator I have preComputeUrls set to false it works as expected with this factory
import { ResponsiveAttachment } from '@ioc:Adonis/Addons/ResponsiveAttachment';
import Factory from '@ioc:Adonis/Lucid/Factory';
import ServiceProviderProfile from 'App/Models/ServiceProviderProfile';
import { readFile } from 'node:fs/promises';
import { join } from 'node:path';

export default Factory.define(ServiceProviderProfile, async ({ faker }) => {
  const avatarImage = await ResponsiveAttachment.fromBuffer(
    await readFile(join(__dirname, '../../tests/resources/default-avatar.png'))
  );

  return {
    name: faker.name.fullName(),
    avatar: avatarImage,
    type: faker.helpers.arrayElement(['mental', 'physical']) as 'mental' | 'physical',
    about: faker.random.words(30),
    specialties: faker.random.words(5).split(' ').join(', ')
  };
}).build();

Drive.getUrl/getSignedUrl does not seem to work outside of a response handler.

Please confirm if this still persist in v1.5.0. Thank you.

Seems to be working for me now when preComputeUrls is set to true! Thank you!!
If you don't mind me asking, how was it fixed?

I can't say what fixed it as I haven't used the add-on in a factory context yet 😄. But I definitely know that a lot of improvements where made over the last 3 or 4 versions.
Glad that it is working for you as expected.

I may have closed too early. Seems fine when running in a test context, but in a seeder context it fails.
Adonis Responsive Attachment error: {
	"stack": "RouterException: E_CANNOT_FIND_ROUTE: Cannot find route for \"drive.local.serve\" identifier
	    at Function.cannotLookupRoute (/Users/anon/development/server/node_modules/@adonisjs/http-server/build/src/Exceptions/RouterException.js:63:23)
	    at Routes.findOrFail (/Users/anon/development/server/node_modules/@adonisjs/http-server/build/src/Router/LookupStore.js:39:53)
	    at UrlBuilder.makeSigned (/Users/anon/development/server/node_modules/@adonisjs/http-server/build/src/Router/LookupStore.js:180:39)
	    at Router.makeSignedUrl (/Users/anon/development/server/node_modules/@adonisjs/http-server/build/src/Router/index.js:330:24)
	    at LocalDriver.getSignedUrl (/Users/anon/development/server/node_modules/@adonisjs/drive/build/src/Drivers/Local.js:142:28)
	    at ResponsiveAttachment.computeUrls (/Users/anon/development/server/node_modules/adonis-responsive-attachment/build/src/Attachment/index.js:418:42)
	    at ResponsiveAttachment.save (/Users/anon/development/server/node_modules/adonis-responsive-attachment/build/src/Attachment/index.js:320:9)
	    at persistAttachment (/Users/anon/development/server/node_modules/adonis-responsive-attachment/build/src/Attachment/decorator.js:61:32)
	    at async Promise.all (index 0)
	    at Proxy.saveWithAttachments (/Users/anon/development/server/node_modules/adonis-responsive-attachment/build/src/Attachment/decorator.js:98:5)",
	"message": "E_CANNOT_FIND_ROUTE: Cannot find route for \"drive.local.serve\" identifier",
	"name": "RouterException",
	"status": 500,
	"code": "E_CANNOT_FIND_ROUTE",
	"help": "When making URL for a route. You can use one of the following identifiers\n- The route name. Defined using `Route.as()`\n- The route controller.method name. `PostsController.show`"
}

This is a short conversation about it on discord
https://discord.com/channels/423256550564691970/1028339813142778017/1028339813142778017
So I think something in adonis itself would need to change to make it work properly in every context.


Use latest Infispan container image for test-infra module, 15.0.4.Final

Description

Target

[x] I checked that the commit is targeting the correct branch (note that Camel 3 uses camel-3.x, whereas Camel 4 uses the main branch)

Tracking

[ ] If this is a large change, bug fix, or code improvement, I checked there is a JIRA issue filed for the change (usually before you start working on it).

Apache Camel coding standards and style

[x] I checked that each commit in the pull request has a meaningful subject line and body.

[x] I have run mvn clean install -DskipTests locally and I have committed all auto-generated changes

/component-test infinispan


Create a Confetti animation when user uploads a post

react-confetti package - https://www.npmjs.com/package/react-confetti

Hey can i work on this issue?

Assigned


face_recognition.version wrong number

face_recognition version: 1.3.0
Python version: 3.8.1 / 3.8.2
Operating System: ubuntu 18.04

Description
wrong version number reported
What I Did
Finished processing dependencies for face-recognition==1.3.0
antonio@antonio-hp-650-nb20:~/workspace-scube/jetson/libraries/face_recognition$ python
Python 3.8.1 (default, Jan  8 2020, 22:29:32)
[GCC 7.3.0] :: Anaconda, Inc. on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import face_recognition
>>> face_recognition.__version__
'1.2.3'
>>>

I am also getting the same version:
Installed: face-recognition==1.3.0
Python 3.6.8 (default, Oct  7 2019, 12:59:55)
[GCC 8.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.

import face_recognition
face_recognition.version
'1.2.3'

Oops :(
I'll have to fix it in the next version. Thanks for the bug report.


Enables plugins to specify config map information

The most common configuration option that we don't easily support is
a plugin specification that also includes config map info. By supporting
this we can easily support different deployment configurations without
specifying the entire sonobuoy gen yaml manually and sharing that.
This is particularly useful for specifying the kube-image-repo-list
as part of the plugin itself rather than as a command line option that
makes it harder to share.

Rebased; merging after green.


Dark Mode Shortcut

Description of the new feature / enhancement
It would be great if you could add a shortcut to toggle dark mode.
Scenario when this would be used?
Switching between light/dark mode is hard on Windows and it's a nice feature to be able to toggle it with just a shortcut.
Supporting information
No response

/dup #1052


Single file compilation doesn't work (with PowerShell as integrated terminal?)

Brief Issue Summary
Launching a build of a single file from the CMake sidebar results in a garbled CLI invocation.
Expected:

Push hammer next to file name
Compile the given file

Apparent Behavior:

Push hammer next to file name
Get an error

PS D:\onedrive\develop\tests\cmake\minimalcpp14\.vscode\cmake\build> 'C:KellekekMICROS~1VISUAL~1PreviewVCToolsMSVC1415~1.266binHostx64x64cl.exe' /nologo /TP /DWIN32 /D_WINDOWS /W3 /GR /EHsc /MDd /Zi /Ob0 /Od /RTC1 -std:c++14 /FoCMakeFilesMinimalCpp14.dirMain.cpp.obj /FdTARGET_COMPILE_PDB /FS -c D:OneDriveDevelopTestsCMakeMinimalCpp14Main.cpp
At line:1 char:78
+ ... S~1VISUAL~1PreviewVCToolsMSVC1415~1.266binHostx64x64cl.exe' /nologo / ...
+                                                                  ~
You must provide a value expression following the '/' operator.
At line:1 char:78
+ ... UAL~1PreviewVCToolsMSVC1415~1.266binHostx64x64cl.exe' /nologo /TP /DW ...
+                                                            ~~~~~~
Unexpected token 'nologo' in expression or statement.
    + CategoryInfo          : ParserError: (:) [], ParentContainsErrorRecordException
    + FullyQualifiedErrorId : ExpectedValueExpression

Slashes are missing from the compiler invocation. Perhaps some formatting goes wrong due to PowerShell not using the legacy cmd.exe, MS-DOS style ~1 shorthands for long and space containing file and folder names.
Platform and Versions

Operating System: Windows 10 (64-bit)
CMake Version: 3.11.2
VSCode Version: 1.25.1
CMake Tools Extension Version: 1.1.0
Compiler/Toolchain: Visual C++ 2017

Interesting. May need to use the & invoke operator? Or perhaps just quote all arguments?

@vector-of-bool ,
I'm having the same issue. And looks like i've found the problem:
On Windows compile_commands.json contains:

"command": "C:\\Langs\\Mingw\\mingw64\\mingw32\\bin\\g++.exe    -g   -std=gnu++17 -o CMakeFiles\\primitives.dir\\main.cpp.obj -c E:\\Projects\\test\\main.cpp",

Note the delimiters. And shlex.split in this line does not support windows delimiters.
I've fixed this by replacing all shlex.split calls with a simple function (in utils.js):
function safeSplitCommand(p)
{
    p = replaceAll(p,'\\','/');
    var res = shlex.split(p);
    return res;
}
exports.safeSplitCommand = safeSplitCommand;

Mentioned line becomes:
arguments: 'arguments' in cur ? cur.arguments : util.safeSplitCommand(cur.command),

Not sure this is a best possible fix, but works for me.
P.S. Thanks for the great extension!

The \ character shouldn't affect the behavior of shell splitting, so I'm not sure how/why your change makes it work? I'll do more investigation.

Sure, but it does:
let s = shlex.split("C:\\Langs\\Mingw\\mingw64\\mingw32\\bin\\g++.exe -g -std=gnu++17 -o CMakeFiles\\primitives.dir\\main.cpp.obj -c E:\\Projects\\test\\main.cpp");
console.log(s);

gives:

Array[7]
0:"C:LangsMingwmingw64mingw32bing++.exe"
1:"-g"
2:"-std=gnu++17"
3:"-o"
4:"CMakeFilesprimitives.dirmain.cpp.obj"
5:"-c"
6:"E:Projectstestmain.cpp"

Apologies for not responding. I'm on vacation with no devbox, just a phone. I can help out testing on Monday once I'm in the office and the problem is not resolved.

when I launch the terminal I don't specify a shell to execute. If I specify cmd.exe when compiling the file on Windows this should work alright. I'll give a few things a try.

I've changed the shlex module and it should now work correctly on Windows, and I'm also going to use cmd.exe as the shell for Windows since it has the syntax I'm expecting. Shell quoting for PowerShell is much more complicated.


add reuseAddr for createSocket with dgram

https://github.com/kmpm/node-mdns-js/issues/31

seems like we had the same idea :)
I've added a node version check on-top to keep the lib compatible with "older" node versions:
https://github.com/xat/node-mdns-js/commit/bc5598ff86c441cb256503e3d951e8b6b8079e8a

I created a Node bug to reflect the fact that the API changed but the docs were not updated for reuseAddr: https://github.com/joyent/node/issues/9280

Good work but please, please, please make sure the existing tests work at least and preferably add relevant new tests.
This is published in v0.3.0


How to control the controller IO output？

I am using the UR3 now and now I need to control the release and clamping of the jaws. Can anyone tell me how to control the IO port of the controller? Thank you very much!

It depends a bit on which IOs you're looking to control, but the /ur_driver/set_io service allows you to control at least the standard digital and analogue IO on the controller.

I believe this is not an issue with the package in this repository so I'll close it.
Please feel free to keep commenting on it.

Thank you


fix spatial partition check

 fix spatial partition contains check

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

8 of 8 (100.0%)  changed or added relevant lines in 1 file are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage increased (+0.02%) to 84.159%

Files with Coverage Reduction
New Missed Lines
%

operators/src/processing/circle_merging_quadtree/operator.rs
1
82.57%

Totals

Change from base Build<PHONE_NUMBER>:
0.02%

Covered Lines:
23881

Relevant Lines:
28376

💛  - Coveralls


[material-ui] Two themes customized using TypeScript theme augmentation are conflicting

Steps to reproduce
I am using mui v5 and creating a customised theme. I have two different frontend F1 and F2 and seperate theme for each frontend F1_theme and F2_theme both of them are customised using typescript via module augumentation. everything works fine if repo has one theme at a time either F1_theme or F2_theme but when repo has both theme at the time then it picks types on one theme and start validating both themes using that type.
Current behavior
No response
Expected behavior
No response
Context
No response
Your environment

npx @mui/envinfo
  Don't forget to mention which browser you used.
  Output from `npx @mui/envinfo` goes here.

Search keywords: mui , mui theme , theme augmentation

It doesn't look like this bug report has enough info for one of us to reproduce it.
Please provide a CodeSandbox (https://material-ui.com/r/issue-template-latest), a link to a repository on GitHub, or provide a minimal code example that reproduces the problem.
Here are some tips for providing a minimal example: https://stackoverflow.com/help/mcve.

@ZeeshanTamboli don`t know why you need something to reproduce. This is how module augmentation works. MUI uses Typescript Declaration Merging and it works great when users merge MUI internal theme and one custom theme. But we can do it twice (or more times). The problem is that Typescript silently merges all themes in one global super theme. Which, of course, totally unwanted.
interface Theme {
  common: string;
}

// theme1.ts
interface Theme {
  theme1: string;
}

const myTheme1: Theme = {
  common: 'common',
  theme1: 'theme1',
};

// theme2.ts
interface Theme {
  theme2: string;
}

const myTheme2: Theme = {
  common: 'common',
  theme2: 'theme2',
};

Monorepo is become more popular nowdays, so this question will appear more often I suppose.
My workaround:  do not use module augmentation.

I use interfaces for custom Theme, ThemeOptions, Palette,... which extend mui types
Create custom theme and give it to ThemeProvider
I have useCustomTheme hook which returns my custom theme
I reexport styled as CreateMUIStyled
This solution can fail in runtime, so testing must prevent failing

@kyptov, we need reproductions because the issue might stem from another cause, and having them will help us find a solution. Are you suggesting that this is a TypeScript limitation? Unsure what actions can be taken on Material UI's side.


OV2-808 Generate Application Number And ORV2-807 Generate Permit Number

Description
This PR is for following tickets:
ORV2-808: Generate application number for a permit application.
ORV2-807: Generate permit number for a permit application.
Fixes # (issue)
Type of change
Please delete options that are not relevant.

[x] New feature (non-breaking change which adds functionality)

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[x] Test A: tested has been done using postman.

Checklist

[x] I have read the CONTRIBUTING doc
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have already been accepted and merged

Further comments

Thanks for the PR!
Any successful deployments (not always required) will be available below.
Backend - Vehicles available
Frontend available
Once merged, code will be promoted and handed off to following workflow run.
Main Merge Workflow

Created other PR


vim: markdown syntax highlighting broken

Issue description
The syntax-highlighting for vim is broken in the current stable version (nixos-19.09, vim-8.2.0013),
especially terminating asterisks do not work.
See also: https://bugzilla.redhat.com/show_bug.cgi?id=1785978
Steps to reproduce
Open vim, set filetype=markdown, enter This is **bold**, but this should be normal.
The syntax-highlighting now renders **, but this should be normal. as italics.
Solution/Workaround
vim from unstable (vim-8.2.343) works again.
So please fix in stable or update stable.
Technical details
broken version:
$ vim --version
VIM - Vi IMproved 8.2 (2019 Dec 12, compiled Jan  1 1970 00:00:01)
Included patches: 1-13

working version from unstable:
$ vim --version
VIM - Vi IMproved 8.2 (2019 Dec 12, compiled Jan  1 1970 00:00:01)
Included patches: 1-343

This is a Vim issue, not a NixOS issue, I noticed there's also no bug open on Vim's end. Could you try to clone https://github.com/vim/vim and run vim with:
env VIMRUNTIME=/path/to/vim-repo/runtime vim test.md

Since no reply from OP, closing.


Should deprecated components be removed?

It looks like react-async is deprecated and hasn't been updated in a while either. I think it would make sense to remove it from the list. Any reason not to?

fixed-data-table is also no longer maintained.

Thanks, please PR any derelict components and we will remove.


Uninitialized variable in lqdetect_dupcheck

Build fails because of an uninitialized variable in lqdetect.c, lqdetect_dupcheck(). Here's the error message.
gcc -std=gnu99 -DHAVE_CONFIG_H -I.   -I./include  -fvisibility=hidden -pthread -g -O2 -Wall -Werror -pedantic -Wmissing-prototypes -Wmissing-declarations -Wredundant-decls  -MT memcached-lqdetect.o -MD -MP -MF .deps/memcached-lqdetect.Tpo -c -o memcached-lqdetect.o `test -f 'lqdetect.c' || echo './'`lqdetect.c
lqdetect.c: In function ‘lqdetect_save_cmd’:
lqdetect.c:244:27: error: ‘ii’ may be used uninitialized in this function [-Werror=maybe-uninitialized]
     lqdetect.arg[cmd][ii] = *arg;
                           ^
lqdetect.c:202:9: note: ‘ii’ was declared here
     int ii;
         ^
cc1: all warnings being treated as errors
make[2]: *** [memcached-lqdetect.o] Error 1

I'm using gcc 4.8.5, on Ubuntu 14.04 LTS x86_64.

Thank you for contribution.
Would you send again your PR based on develop branch ??
After receive your new PR, I will close this PR.

I merged your new PR. Thank you...


Fix lgtm.com warnings

Codecov Report

Merging #407 into master will decrease coverage by 3.1%.
The diff coverage is 80%.

@@             Coverage Diff              @@
##             master     #407      +/-   ##
============================================
- Coverage      75.1%   71.99%   -3.11%
+ Complexity     1459     1263     -196
============================================
  Files           144      140       -4
  Lines          5920     4863    -1057
  Branches        744      494     -250
============================================
- Hits           4446     3501     -945
+ Misses         1252     1139     -113
- Partials        222      223       +1

Impacted Files
Coverage Δ
Complexity Δ

...co/elastic/apm/agent/servlet/ServletApiAdvice.java
7.57% <0%> (ø)
2 <0> (ø)
:arrow_down:

.../main/java/co/elastic/apm/agent/bci/AgentMain.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...tic/apm/agent/configuration/CoreConfiguration.java
95.27% <100%> (-1.5%)
15 <0> (-14)

...astic/apm/agent/impl/transaction/TraceContext.java
92.21% <100%> (-0.52%)
56 <0> (-11)

...ic/apm/agent/servlet/ServletTransactionHelper.java
71.75% <100%> (-0.22%)
40 <6> (-2)

...va/co/elastic/apm/agent/impl/ElasticApmTracer.java
75.9% <100%> (-3.05%)
44 <0> (-6)

...ddy/SimpleMethodSignatureOffsetMappingFactory.java
25% <0%> (-75%)
2% <0%> (-1%)

.../agent/plugin/api/AbstractSpanInstrumentation.java
53.19% <0%> (-11.17%)
3% <0%> (-2%)

...pm/agent/report/IntakeV2ReportingEventHandler.java
73.15% <0%> (-10.18%)
30% <0%> (-18%)

...co/elastic/apm/agent/report/ApmServerReporter.java
58.06% <0%> (-7.91%)
13% <0%> (-4%)

... and 20 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 1ed279f...53cf369. Read the comment docs.


compile error

/usr/bin/clang -D_AGAR_INTERNAL -D_DEFAULT_SOURCE -D_BSD_SOURCE  -I/home/chris/development/dlang/agar/libagar/include -D_AGAR_CORE_INTERNAL -U_XOPEN_SOURCE -D_XOPEN_SOURCE=600          -fPIC -o object.o -c object.c
object.c:1716:3: error: use of undeclared identifier 'debugSave'
                debugSave = 0;

don't know if configure has missed something ?

Sorry for the delay! This compilation error should be fixed in current.
Please try again with the latest sources.
Thanks,


Index out of bounds in stream.zig

I'm experiencing an index out of bounds error and I'm not sure there is something I can do to correct this in my code since it merely listens for the next message.
https://github.com/ianic/websocket.zig/blob/main/src/stream.zig#L238

Let me know if there is more info I can give to help diagnose this.

Seams that Zig's tls implementation still has some open issues. I didn't connect any of them with this particular error but let's try to remove it as dependency.
We can use some sidecar tcp->tls proxy. I tried with envoy. Downloaded bin for my platform, make config and start it.
config.yml:
static_resources:
  listeners:
  - address:
      socket_address:
        address: <IP_ADDRESS>
        port_value: 10000
    filter_chains:
    - filters:
      - name: envoy.filters.network.tcp_proxy
        typed_config:
          "@type": type.googleapis.com/envoy.extensions.filters.network.tcp_proxy.v3.TcpProxy
          cluster: service-https
          stat_prefix: wss_passthrough
  clusters:
  - name: service-https
    type: STRICT_DNS
    lb_policy: ROUND_ROBIN
    load_assignment:
      cluster_name: service-https
      endpoints:
      - lb_endpoints:
        - endpoint:
            address:
              socket_address:
                address: socket.polygon.io
                port_value: 443
    transport_socket:
      name: envoy.transport_sockets.tls
      typed_config:
        "@type": type.googleapis.com/envoy.extensions.transport_sockets.tls.v3.UpstreamTlsContext

 ./envoy-1.28.0-linux-aarch_64 --config-path ./config.yaml

This example connect to the remote wss endpoint through local proxy which handles tls.
const std = @import("std");
const ws = @import("ws");
const assert = std.debug.assert;
const Allocator = std.mem.Allocator;

pub fn main() !void {
    var gpa = std.heap.GeneralPurposeAllocator(.{}){};
    defer _ = gpa.deinit();
    const allocator = gpa.allocator();

    const uri = "wss://socket.polygon.io/stocks";
    const proxy_host = "<IP_ADDRESS>";
    const proxy_port = 10000;

    var tcp = try std.net.tcpConnectToHost(allocator, proxy_host, proxy_port);
    defer tcp.close();
    var cli = try ws.client(allocator, tcp.reader(), tcp.writer(), uri);
    defer cli.deinit();

    while (cli.nextMessage()) |msg| {
        defer msg.deinit();
        std.debug.print("{s}\n", .{msg.payload});
    }
}

Getting result:
[{"ev":"status","status":"connected","message":"Connected Successfully"}]
[{"ev":"status","status":"auth_timeout","message":"No authentication request received."}]

Ok I will try this and let you know what happens.

So from my testing today during market open, things are stable. I think you are right - this is related to open issues in Zig currently.


using Promise.all to replace forloop

What's the motivation ? Are you establishing that many connections ?

My motivation is this https://gist.github.com/midnightcodr/9d1b6d919d7e149acec95e15ceb53d00

I do understand your question. If things can be done in parallel, why not.

Awesome! Thank you!


Min fan speed  patch

patch.txt to add Min fan speed,
patch2.txt to fix example.py
patch2.txt
patch.txt

diff --git a/example.py b/example.py
index ad2e853..561ab9c 100644
--- a/example.py
+++ b/example.py
@@ -4,9 +4,9 @@ from msmart.device import air_conditioning_device as ac
import logging
logging.basicConfig(level=logging.DEBUG)
-# first take device's ip and id
+# first take device's ip, id and port
pip3 install msmart; midea-discover
-c = midea_device('YOUR_AC_IP', YOUR_AC_ID)
+c = midea_device('YOUR_AC_IP', YOUR_A_ID, YOUR_AC_PORT)
device = c.setup()
Refresh the object with the actual state by querying it
device.refresh()
@@ -29,6 +29,7 @@ print({
device.power_state = True
device.prompt_tone = False
device.target_temperature = 25
+device.fan_speed = ac.fan_speed_enum.Min
device.operational_mode = ac.operational_mode_enum.cool
commit the changes with apply()

diff --git a/example.py b/example.py
index ad2e853..561ab9c 100644
--- a/example.py
+++ b/example.py
@@ -4,9 +4,9 @@ from msmart.device import air_conditioning_device as ac
import logging
logging.basicConfig(level=logging.DEBUG)
-# first take device's ip and id
+# first take device's ip, id and port
pip3 install msmart; midea-discover
-c = midea_device('YOUR_AC_IP', YOUR_AC_ID)
+c = midea_device('YOUR_AC_IP', YOUR_A_ID, YOUR_AC_PORT)
device = c.setup()
Refresh the object with the actual state by querying it
device.refresh()
@@ -29,6 +29,7 @@ print({
device.power_state = True
device.prompt_tone = False
device.target_temperature = 25
+device.fan_speed = ac.fan_speed_enum.Min
device.operational_mode = ac.operational_mode_enum.cool
commit the changes with apply()

you can PR, thanks


Add Roman Numerals exercise

Looks okay to me once Isaac’s questions are addressed.

Closing and reopening to bump the checks.

It looks like you need to resolve some merge conflicts here, @Steffan153


Fix Estimator panic

This is happening in some of my CI runs, like here: https://github.com/arxanas/git-branchless/runs/5581044721?check_suite_focus=true

I've also been seeing panics in AtomicPosition::allow, but I also wasn't able to reproduce them.

I think #404 might fix that.

I filed https://github.com/console-rs/indicatif/issues/405 to track the AtomicPosition::allow panic. I think it's not addressed in #404; it's probably overflowing because of the as u8 somehow, which is still present there.


Don't use type-"date" for the HTML element

Otherwise it'll fail in Chrome with The specified value "24/02/2016" does not conform to the required format, "yyyy-MM-dd".. Always use type="text".

Yes, I encountered it as well.

Thanks, I was having this issue :+1:


autoFlush_ is used uninitialized

In zlibtop.cpp, the member autoFlush_ is never initialized, and has no setter, but is used in the baseCompress method.
I discovered this because baseCompress was sometimes failing for no reason; it turns out this happened whenever autoFlush_ randomly had a nonzero value. For some reason this causes the call to deflate to fail.
I fixed the bug by adding a line to the constructor that sets autoFlush = false, but it seems that this variable could be removed entirely since there's no way to ever set it to true.

Thanks for this bug report.  The intention was for the optional autoflush parameter passed into the constructors to be used.  I have since corrected this problem in the PR and branch https://github.com/rudi-cilibrasi/zlibcomplete/pull/6    Can you let me know if you are able to give this branch a try before I merge it into master?

@snej Did you manage to give it a try?

Yup, it fixes the problem for me. Thanks!

you're welcome! :+1:


Build fails in Windows OS

I'm using Windows OS and I tried to run the app I'm getting an error when I execute flutter pub get . . Please find the result for flutter doctor -v

The error I'm getting is as follows.

Hello @viradhanus
Have a read at this conversation here, you will get it running,
Meanwhile, we are looking to find a fix for this

Hi, I had to do a few steps to resolve this issue.

Clean the pub cache using flutter pub cache clean command.
Execute flutter pub get .. Then it gave me the following error.

And I resolved it using git config --system core.longpaths true command.
Source: Filename too long in Git for Windows

Execute flutter pub get .. Then it suggested enabling the developer mode in Windows.

After enabling the developer mode, execute flutter pub get ..


modified gmres to avoid an extra application of the linear operator

I made a small modification to the gmres function in order to avoid a second application of the linear operator at each iteration.

Thanks!


dApp connector

Hi i have issue with dApp connector of SAFEW(chrome extension):
The extension doesnt test if ergo_request_read_access() already exist before to replace its code, same for ergoConnector.nautilus.connect(). It's in inject.js or something like that..
Its a problem if i have Yoroi and Nautilus on my browser. I tried with ergoAuctionHouse and Safew is launched instead of Yoroi. Dont have this problem with Nautilus. Maybe its a deliberate choice of your dev...i dont know, but i prefer to tell you.
Hope this can help you to improve SAFEW^^
Bye

Hi,
Thanks for reporting the issue.
This should be improved soon with official support of SAFEW in the Ergodex, currently it "needs" to declare ergoConnector.nautilus.connect() because the ergoConnector.safew.connect() is not called by Ergodex.
On ergoAuctionHouse, the connection is done with "ergo_request_read_access()" which needs to be declared by all wallets following EIP-12 standard. I'm not sure how the concurrency on this method needs to be handled, it is now deprecated for the new ergoConnector.
I would recommend to avoid to have 2 ergo wallets with a dApp connector enabled in the same browser.
I would expect in the future dApps that the list of the available wallet to connect could be built by listing the ergoConnector attributes.
Regards

Hi i have issue with dApp connector of SAFEW(chrome extension):
The extension doesnt test if ergo_request_read_access() already exist before to replace its code, same for ergoConnector.nautilus.connect(). It's in inject.js or something like that..
Its a problem if i have Yoroi and Nautilus on my browser. I tried with ergoAuctionHouse and Safew is launched instead of Yoroi. Dont have this problem with Nautilus. Maybe its a deliberate choice of your dev...i dont know, but i prefer to tell you.
Hope this can help you to improve SAFEW^^
Bye

This overridde allows to use SAFEW even if only Nautilus or Yoroi support is implemented by the dApp.
SAFEW extension needs to be disabled, to uses the other Ergo wallet implementing the dApp connector.


xcode9.3  the button click event can not called

Hi,guy
I find a problem.When I add a button on the custom uitableviewcell, the touch up inside event can not be called. After removing the TBEmptyDataSet from the tableview, the event can be called.

@xiaomiwang I can't reproduce this issue. Do you have any demo?


Can't install with python 3.10

I can't seem to get the pip install to work with python 3.10.6 and pip 22.3.1
pip install requests pemja
Defaulting to user installation because normal site-packages is not writeable
Requirement already satisfied: requests in /usr/lib/python3/dist-packages (2.25.1)
Collecting pemja
Using cached pemja-0.2.6.tar.gz (48 kB)
Installing build dependencies ... done
Getting requirements to build wheel ... error
error: subprocess-exited-with-error
× Getting requirements to build wheel did not run successfully.
│ exit code: 1
╰─> [24 lines of output]
setup.py:34: RuntimeWarning: Pemja may not yet support Python 3.10.
warnings.warn(
Traceback (most recent call last):
File "/home/richard/.local/lib/python3.10/site-packages/pip/_vendor/pep517/in_process/_in_process.py", line 351, in
main()
File "/home/richard/.local/lib/python3.10/site-packages/pip/_vendor/pep517/in_process/_in_process.py", line 333, in main
json_out['return_val'] = hook(**hook_input['kwargs'])
File "/home/richard/.local/lib/python3.10/site-packages/pip/_vendor/pep517/in_process/_in_process.py", line 118, in get_requires_for_build_wheel
return hook(config_settings)
File "/tmp/pip-build-env-gt1_4mbr/overlay/local/lib/python3.10/dist-packages/setuptools/build_meta.py", line 162, in get_requires_for_build_wheel
return self._get_build_requires(
File "/tmp/pip-build-env-gt1_4mbr/overlay/local/lib/python3.10/dist-packages/setuptools/build_meta.py", line 143, in _get_build_requires
self.run_setup()
File "/tmp/pip-build-env-gt1_4mbr/overlay/local/lib/python3.10/dist-packages/setuptools/build_meta.py", line 267, in run_setup
super(_BuildMetaLegacyBackend,
File "/tmp/pip-build-env-gt1_4mbr/overlay/local/lib/python3.10/dist-packages/setuptools/build_meta.py", line 158, in run_setup
exec(compile(code, file, 'exec'), locals())
File "setup.py", line 184, in
include_dirs=get_java_include() + ['src/main/c/pemja/core/include'] + get_numpy_include(),
File "setup.py", line 111, in get_java_include
inc = os.path.join(get_java_home(), inc_name)
File "/usr/lib/python3.10/posixpath.py", line 76, in join
a = os.fspath(a)
TypeError: expected str, bytes or os.PathLike object, not NoneType
When building from scratch I get:
python setup.py sdist
/home/richard/src/pemja/setup.py:23: DeprecationWarning: The distutils package is deprecated and slated for removal in Python 3.12. Use setuptools or check PEP 632 for potential alternatives
from distutils.command.build_ext import build_ext as old_build_ext
/home/richard/src/pemja/setup.py:34: RuntimeWarning: Pemja may not yet support Python 3.10.
warnings.warn(
Traceback (most recent call last):
File "/home/richard/src/pemja/setup.py", line 184, in
include_dirs=get_java_include() + ['src/main/c/pemja/core/include'] + get_numpy_include(),
File "/home/richard/src/pemja/setup.py", line 111, in get_java_include
inc = os.path.join(get_java_home(), inc_name)
File "/usr/lib/python3.10/posixpath.py", line 76, in join
a = os.fspath(a)
TypeError: expected str, bytes or os.PathLike object, not NoneType

This error comes from JAVA_HOME variable not being set.

Pemja has supportted windows 3.10 wheel packages from 0.3.0 version

OK -- to be 100% clear. The issue is that on Ubuntu Linux pemja install fails with an error about 3.10 if you haven't set the JAVA_HOME environment variable. It should be quite easy to create a more helpful error message. It took me an hour or so to work out what the problem was. Other people might simply give up. There's an obvious few line fix.


lose response when terminal print large string

VSCode Version: 1.18.1
OS Version:macOS 10.14

Steps to Reproduce:

code --disable-extensions  open a window
using terminal,and just print large string, I have try lua and python script,they all can reproduce

just one line
print("asdqweasd"*10000)

Does this issue occur when all extensions are disabled?: Yes/No
Yes
few char will speed up,about 30000 chars,there need 5 seconds to response

You're on a very old version of vscode, please update before creating issues.

@Tyriar sorry,just typo,it is 1.28.1