GapEncoder to support a sparse matrix (scipy) as input

Problem Description
Currently it seems like GapEncoder is constrained to text as input. Would be great to be able to pass scipy sparse matrix and skip the vectorization thing it does.
Feature Description
.fit(X) to support scipy sparse matrices for X
Alternative Solutions
No response
Additional Context
No response

Thanks for your comment.
The GapEncoder is specifically made to encode strings and we will not repurpose it for other things as 1) some of the underlying code would not carry over, 2) it would not enable us to give a consistent user story and thus make the documentation confusing.
I think that what you are looking for is not the GapEncoder, but matrix factorization tools. For instance, the closest one in terms of statistical model is https://scikit-learn.org/stable/modules/generated/sklearn.decomposition.MiniBatchNMF.html . I do believe that it support's sparse matrices, but I'm not certain. You need to choose wisely the loss to have a factorization similar to the one we do in the GapEncoder.
Fun fact: the code of scikit-learn's MiniBatchNMF is actually evolved from the algorithmic code of the GapEncoder.

Understood! Thanks for the swift reply.

Understood! Thanks for the swift reply.

Thanks for understanding. I hope that you are successful with scikit-learn objects. Don't hesitate to tell us here. It won't change much for skrub, but it will make me happy.


Support for Embedded media

Embedded media cannot be automatically shown in a reddit post. The special sites (like youtube, gfycat...) need custom support for that. The following list tracks implementation and is expanded if needed:

[x] Youtube (support added in #7)
[x] Gfycat
. . .

Bump @4kills


Highlighting for tagged roles

Can you add syntax highlighting when roles are tagged in playbooks...
example...
---
- name: My Play
  hosts: all
  become: yes
  roles:
    - { role: common, tags: [ "common", "my_common_tag" ] }

The adding the config below works, but for some reason when I combine them together it malfunctions on the quoted strings for tags, so I'm probably getting lost in regex somewhere...
# packages/language-ansible/grammars/ansible.cson
# works
  {
    captures:
      "2":
        name: "string.quoted.double.ansible"
    match: "\\- (\\{ role\\:) (\\w*)"
    name: "keyword.other.ansible"
  }
  {
    captures:
      "2":
        name: "string.quoted.double.ansible"
    match: "( tags\\:) \\[ ([[\\\"\\w*\\\"]+[,]? ]+) \\] \\}"
    name: "keyword.other.ansible"
  }

# packages/language-ansible/grammars/ansible.cson
# doesn't work
  {
    captures:
      "2":
        name: "string.quoted.double.ansible"
    match: "\\- (\\{ role\\:) (\\w*)|( tags\\:) \\[ ([[\\\"\\w*\\\"]+[,]? ]+) \\] \\}"
    name: "keyword.other.ansible"
  }

Should be fixed in latest release


several questions

The "Eichenholzzauntor" is the German translation but should be called "glasses for grandpa"
https://prnt.sc/s7h17v

Can I edit the entire line in String.yml? ( -100 Cubeis)
https://prnt.sc/s7h2vq

You can deactivate the delivery message if you don't need it, for example, you deliver 1 item

I do not understand your question.
There is a "money" string which you can try changing. If that doesn't work, you'll have to change it within Vault.
You must supply a delivery message. If you would prefer a blank line, you'd have to edit your quests.yml file and replace the message with " ".

Oak fence is the item to be delivered.
Now the name of the item is displayed but not the one I assigned


Thanos Query tries to add the same store twice when using DNS service discovery

Thanos, Prometheus and Golang version used
docker.io/thanosio/thanos:v0.7.0

What happened
When using DNS for service discovery, Thanos Query tries to connect to all addresses resolved for each SRV record (the A and the AAAA records) and, because it's the same store, it adds and removes them in a loop due to conflicting external labels.
What you expected to happen
Thanos Query should connect only to the IPv6 address, and then fallback to connecting to the IPv4 address if necessary.
How to reproduce it (as minimally and precisely as possible):
I have a service record that looks like this:
    _thanos-sidecar._tcp.example.com. 300 IN SRV 10 1 10901 01.thanos-sidecar.example.com.

01.thanos-sidecar.example.com looks like this:
    01.thanos-sidecar.example.com. 300 IN CNAME   server.example2.com.
    server01.example2.com.         3600    IN      A       <IP_ADDRESS>
    server01.example2.com.         3600    IN      AAAA    2001:db8::2

Thanos  Query tries to add both <IP_ADDRESS> and 2001:db8::2 as stores, so it adds and removes them in a loop.
Full logs to relevant components
Logs

level=info ts=2019-09-16T14:53:50.302203728Z caller=storeset.go:263 component=storeset msg="adding new store to query storeset" address=[2001:db8::2]:10901
level=warn ts=2019-09-16T14:54:00.333034248Z caller=storeset.go:252 component=storeset msg="dropping store, external labels are not unique" address=<IP_ADDRESS>:10901 extLset="{prometheus=\"prometheus01\"}" duplicates=2
level=warn ts=2019-09-16T14:54:00.339204099Z caller=storeset.go:303 component=storeset msg="update of store node failed" err="fetching store info from [2001:db8::2]:10901: rpc error: code = Canceled desc = grpc: the client connection is closing" address=[2001:db8::2]:10901
level=info ts=2019-09-16T14:54:10.343209648Z caller=storeset.go:238 component=storeset msg="removing store because it's unhealthy or does not exist" address=[2001:db8::2]:10901
level=info ts=2019-09-16T14:54:10.343861396Z caller=storeset.go:263 component=storeset msg="adding new store to query storeset" address=<IP_ADDRESS>:10901
level=warn ts=2019-09-16T14:54:20.455305967Z caller=storeset.go:252 component=storeset msg="dropping store, external labels are not unique" address=[2001:db8::2]:10901 extLset="{prometheus=\"prometheus01\"}" duplicates=2
level=warn ts=2019-09-16T14:54:20.456725158Z caller=storeset.go:303 component=storeset msg="update of store node failed" err="fetching store info from <IP_ADDRESS>:10901: rpc error: code = Canceled desc = grpc: the client connection is closing" address=<IP_ADDRESS>:10901
level=info ts=2019-09-16T14:54:30.469286373Z caller=storeset.go:238 component=storeset msg="removing store because it's unhealthy or does not exist" address=<IP_ADDRESS>:10901
level=info ts=2019-09-16T14:54:30.470207533Z caller=storeset.go:263 component=storeset msg="adding new store to query storeset" address=[2001:db8::2]:10901
level=warn ts=2019-09-16T14:54:40.539096978Z caller=storeset.go:252 component=storeset msg="dropping store, external labels are not unique" address=<IP_ADDRESS>:10901 extLset="{prometheus=\"prometheus01\"}" duplicates=2

Anything else we need to know
Domains and addresses have been doctored, but the logs are real otherwise.

I will try to provide a fix for this.

@tbregolin I have looked through the code and tested different scenarios and I think this is the expected behavior. The idea is that you can use a single domain to advertise many different targets. this is the same for srv and dns.
What is your use case that you have a duplicate IP address for the same target?
I understand that one is A and the other is AAAA, but still why do you have both set in the DNS records?
If you think that the expected behavior should be different please describe how would you think this should work. Keep in mind that keeping multiple targets per domain shouldn't change as this is the most common setup.

@krasi-georgiev thank you for looking into this.
I don't think adding and removing stores in a loop is a sane behavior. Thanos should just refuse to add a store when the external labels conflict, so that it doesn't impact availability.
Your point about using a single SRV record for each store makes sense, and works for me.
I'll leave it up to you to close this, but feel free to do so.

I don't think adding and removing stores in a loop is a sane behavior. Thanos should just refuse to add a store when the external labels conflict, so that it doesn't impact availability.

I think I misunderstood the original issue and yes I agree that when one store is healthy it should just remove the duplicate and do nothing more.
Now looking at the logs you provided it looks like it goes into a loop because it can't connect to either stores so it keeps trying.
It first marks the AAAA as a duplicate and tries to connect to A it fails to than it tries to connect to AAAA and so on.
When I tested this locally it behaved as expected and when it connected ok to the A record it just left the AAAA as duplicated and didn't go into a loop

In my case the same sidecar was reachable in both addresses. I'll try to reproduce it again in a local environment to be sure and post the logs/my findings here.

Hi,
first of all - thanos is awesome thank you guys! ;)
And could we reevaluate this is issue?  To give and example where this happens as well:
Using K8s nodeport service where multiple IPs point to the same store/query pod.

Sure! Let's investigate if you still repro this. Help wanted :hugs:

sure here is the information. pretty similar with the original except ipv4 only. hope this helps.
Thanos, Prometheus and Golang version used:
docker.io/thanosio/thanos:v0.12.2
Object Storage Provider:
gcs
What happened:
when the local querier accesses the 2nd querier inside the k8s via nodeport service, PromQL queries time out or result in partial responses.
What you expected to happen:
normal responsive queries.
Setup:
having mutliple different ips forward to the same thanos query service:
local query instance ----> k8s query instance (3 ips)
How to reproduce it (as minimally and precisely as possible):
for example through:
expose the (1 replica) query instance in k8s via a nodeport service
-- or --
(not tested) give a container 3 ips
creating a dns srv record + an A record with mutliple ips
grpc.thanos.gcp.example.com   1200    IN      SRV     1 20 30404 server01.example2.com.
server01.example2.com.         3600    IN      A       <IP_ADDRESS>
server01.example2.com.         3600    IN      A       <IP_ADDRESS>
server01.example2.com.         3600    IN      A       <IP_ADDRESS>

(when the additional ip records are removed this setup works fine)
setting local querier
--store=dnssrv+grpc.thanos.gcp.example.com
Full logs to relevant components:
the logs from the k8s querier side dont show any information.
The following logs are from the local query instance - the labels are changed.

level=warn ts=2020-05-04T08:53:48.660483028Z caller=proxy.go:453 err="receive series from Addr: <IP_ADDRESS>:30118 LabelSets: {cluster="example1", location="cloud", replica="A"} Mint:<PHONE_NUMBER>000 Maxt:<PHONE_NUMBER>854775807: rpc error: code = Canceled desc = context canceled" msg="returning partial response"
level=warn ts=2020-05-04T08:53:48.871095765Z caller=proxy.go:453 err="failed to receive any data from Addr: <IP_ADDRESS>:30118 LabelSets: {cluster="example1", location="cloud", replica="A"} Mint:<PHONE_NUMBER>000 Maxt:<PHONE_NUMBER>854775807: context canceled" msg="returning partial response"
level=warn ts=2020-05-04T08:53:48.871264387Z caller=proxy.go:453 err="failed to receive any data from Addr: <IP_ADDRESS>:30118 LabelSets: {cluster="example1", location="cloud", replica="A"} Mint:<PHONE_NUMBER>000 Maxt:<PHONE_NUMBER>854775807: context canceled" msg="returning partial response"
level=warn ts=2020-05-04T08:53:48.871349964Z caller=proxy.go:453 err="receive series from Addr: <IP_ADDRESS>:30118 LabelSets: {cluster="example1", location="cloud", replica="A"} Mint:<PHONE_NUMBER>000 Maxt:<PHONE_NUMBER>854775807: rpc error: code = Canceled desc = context canceled" msg="returning partial response"
level=warn ts=2020-05-04T08:53:49.083421245Z caller=proxy.go:453 err="failed to receive any data from Addr: <IP_ADDRESS>:30118 LabelSets: {cluster="example1", location="cloud", replica="A"} Mint:<PHONE_NUMBER>000 Maxt:<PHONE_NUMBER>854775807: context canceled" msg="returning partial response"
level=warn ts=2020-05-04T08:53:49.083491547Z caller=proxy.go:453 err="failed to receive any data from Addr: <IP_ADDRESS>:30118 LabelSets: {cluster="example1", location="cloud", replica="A"} Mint:<PHONE_NUMBER>000 Maxt:<PHONE_NUMBER>854775807: context canceled" msg="returning partial response"
level=warn ts=2020-05-04T08:53:49.083461563Z caller=proxy.go:453 err="receive series from Addr: <IP_ADDRESS>:30118 LabelSets: {cluster="example1", location="cloud", replica="A"} Mint:<PHONE_NUMBER>000 Maxt:<PHONE_NUMBER>854775807: rpc error: code = Canceled desc = context canceled" msg="returning partial response"
level=warn ts=2020-05-04T08:55:03.38414351Z caller=storeset.go:440 component=storeset msg="update of store node failed" err="getting metadata: fetching store info from <IP_ADDRESS>:30118: rpc error: code = DeadlineExceeded desc = context deadline exceeded" address=<IP_ADDRESS>:30118
level=info ts=2020-05-04T08:55:03.384597984Z caller=storeset.go:360 component=storeset msg="removing store because it's unhealthy or does not exist" address=<IP_ADDRESS>:30118 extLset="{cluster="example1", location="cloud", replica="A"}"
level=warn ts=2020-05-04T08:55:03.384776011Z caller=proxy.go:453 err="receive series from Addr: <IP_ADDRESS>:30118 LabelSets: {cluster="example1", location="cloud", replica="A"} Mint:<PHONE_NUMBER>000 Maxt:<PHONE_NUMBER>854775807: rpc error: code = Canceled desc = grpc: the client connection is closing" msg="returning partial response"
level=warn ts=2020-05-04T08:55:03.384902065Z caller=proxy.go:453 err="receive series from Addr: <IP_ADDRESS>:30118 LabelSets: {cluster="example1", location="cloud", replica="A"} Mint:<PHONE_NUMBER>000 Maxt:<PHONE_NUMBER>854775807: rpc error: code = Canceled desc = grpc: the client connection is closing" msg="returning partial response"
level=info ts=2020-05-04T08:55:03.414442417Z caller=storeset.go:384 component=storeset msg="adding new storeAPI to query storeset" address=<IP_ADDRESS>:30118 extLset="{cluster="example1", location="cloud", replica="A"}"
level=warn ts=2020-05-04T08:56:16.827457802Z caller=proxy.go:453 err="receive series from Addr: <IP_ADDRESS>:30118 LabelSets: {cluster="example1", location="cloud", replica="A"} Mint:<PHONE_NUMBER>000 Maxt:<PHONE_NUMBER>854775807: rpc error: code = Internal desc = unexpected EOF" msg="returning partial response"
level=warn ts=2020-05-04T08:59:37.051939594Z caller=proxy.go:453 err="receive series from Addr: <IP_ADDRESS>:30118 LabelSets: {cluster="example1", location="cloud", replica="A"} Mint:<PHONE_NUMBER>000 Maxt:<PHONE_NUMBER>854775807: rpc error: code = Internal desc = unexpected EOF" msg="returning partial response"
level=warn ts=2020-05-04T08:59:38.427084806Z caller=proxy.go:453 err="receive series from Addr: <IP_ADDRESS>:30118 LabelSets: {cluster="example1", location="cloud", replica="A"} Mint:<PHONE_NUMBER>000 Maxt:<PHONE_NUMBER>854775807: rpc error: code = Internal desc = unexpected EOF" msg="returning partial response"

under the store page the k8s querier shows up 3 time with each ip.


Missing last second of audio

Single-file reproducer, not sure if I'm using libopusenc incorrectly or if this is a bug.
Steps to reproduce:

Put raw audio into c:\temp\input.raw, 2 bytes per sample, 48khz, mono
Run the reproducer ( https://gist.github.com/lwahonen/6b0b0e311750703a0ae7deb164b82405 )
Notice that the last word or two from the test recording are missing from c:\temp\output.opus

I'm using libopusenc, libogg, libopus etc from their respective HEADs

I do call ope_encoder_drain(opusEncoderPointer);
Is there a different drain I need to call too?

Running the same raw data via opusenc.exe --raw input.raw test.opus results in audio data not being lost.

I rebuilt all components and the issue disappeared.


Insight into error working on one machine and not another

I have my rails app working w/ rubycas-server just fine.  I created a clone of this app on a vagrant VM.  When I try to login, I get the following error in my application (and don't see any errors in the rubycas-server logs or any further info in my application logs).  Any ideas what could be causing this?
Started GET "/accounts/service?ticket=ST-1330102377r8FA7C57CA66F687E9D" for <IP_ADDRESS> at 2012-02-24
08:52:55 -0800
Processing by Devise::CasSessionsController#service as HTML
Parameters: {"ticket"=>"ST-1330102377r8FA7C57CA66F687E9D"}
Completed 500 Internal Server Error in 592ms
RuntimeError (The CAS authentication server at https://ssodev.foo.com/proxyValidate?service=http%3A%2F%2Flocalhost%3A3000%2Faccounts%2Fservice&ticket=ST-1330102377r8FA7C57CA66F687E9D responded with an error (#<Net::HTTPSeeOther 303 See Other readbody=true>)!):

The problem was my machine would resolve ssodev.foo.com as one ip and vagrant would resolve it as another.


Change Makefile variables order

Put them in the following order:

The variables that have to be changed (like TRANING_COMMAND)
The variables that are likely to be changed (like DISABLE_HTTP_AUTH)
The variables that may be changed (like paths and job names)
The variables that are unlikely to be changed (like APT_COMMAND)

Add comments to the first two groups.

closed in https://github.com/neuromation/cookiecutter-neuro-project/pull/146


Visual Studio Code Arm 64 on Ubuntu 20.04.4 LTS Crashes on Start

Does this issue occur when all extensions are disabled?: I don't know what this means

VS Code Version: code_1.67.2-1652811872_arm64.deb
OS Version: Ubuntu 20.04.4 LTS

Steps to Reproduce:

Install the version code_1.67.2-1652811872_arm64.deb on Ubuntu 20.04.4 LTS
Click on the blue Visual Studio Icon.  Nothing happens however when I look at the processes running I see the following:

Does the issue happen with latest insiders https://code.visualstudio.com/insiders , should be addressed with https://github.com/microsoft/vscode/pull/145527


Add new rule to check for useless quote escapes

When using the autofixer for Q000 it does not remove the backslashes from quotes that no longer need escaping.
This new rule checks for such backslashes (regardless whether they come from the autofixer or not) and can remove them.
I used Q100 to avoid ocnflicts with Q00x rules flake8-quotes might add (even though it's not very actively maintained)
fixes #8617

Haven't reviewed the code yet, but the ecosystem check seems to be flagging some cases like "\\'", in which the backslash escapes are necessary (I think?) to add a backslash literal.

Yeah, just noticed that I'm not checking for escaped backslashes - already on it

Awesome, thanks @ThiefMaster!

Ecosystems looks much better now. The one new violation is actually correct since those quotes there should not be escaped.

The mkdocs CI failure seems unrelated (it didn't fail until I rebased to the latest master).


Fixing typos for include in requirements.txt in examples/http/*.

Description
Ticket #211. Reorganizing the examples/http directory broke the requirements.txt references to the top-level requirements.txt file.
Testing
Tested locally to make sure these now find the top-level requirements.txt
Checklist:
Standard test suite is being run.
Documentation
No documentation changes.

Would you fix the lint @rcbjBlueMars ?

Would you fix the lint @rcbjBlueMars ?

The pylint errors are related to the upstream OTel instrumentation modules removing the modules being instrumented as dependencies. Up till now we had been depending on that to make sure all the correct modules were picked up. I'm working on adding the modules (flask, aiohttp, mysql.connector, etc) to the relevant test directories.
I'm going to keep the OTel instrumentation modules we depend on in the setup.py dependency list. The end modules aren't actually used unless someone tries to enable the corresponding module. In theory, this wouldn't be done unless they are actually using that module.

Closing this PR and adding changes to a new branch based on updated test suite that runs correctly.


missing/broken asset (picture) links

See e.g. http://haxe.org/manual/type-system-resolution-order.html or the macro flow diagram.

I got confused by directories there but it should be fixed now. Waiting for the website to confirm.

@jasononeil: The images are there in the github markdown (https://github.com/HaxeFoundation/HaxeManual/blob/master/output/HaxeManual/website/type-system-resolution-order.md) but are missing on the website (http://haxe.org/manual/type-system-resolution-order.html). Do I have to update something else?

The paths in the markdown won't work in a different context:
src="../../../HaxeManual/assets/graphics/generated/type-system-resolution-order-diagram.png"
I had a workaround in place before, but it might have changed during this
commit
https://github.com/HaxeFoundation/HaxeManual/commit/65e2227e94dd966fec031b4b326074b0dea51830.
I'll fix it tonight and try set up some kind of automated test to make sure
this doesn't happen again.
On Tue, May 12, 2015 at 4:25 AM, Simon Krajewski<EMAIL_ADDRESS>wrote:

@jasononeil https://github.com/jasononeil: The images are there in the
github markdown (
https://github.com/HaxeFoundation/HaxeManual/blob/master/output/HaxeManual/website/type-system-resolution-order.md)
but are missing on the website (
http://haxe.org/manual/type-system-resolution-order.html). Do I have to
update something else?
—
Reply to this email directly or view it on GitHub
https://github.com/HaxeFoundation/HaxeManual/issues/143#issuecomment-101037755
.


How to use TensorCore PTX in Triton

Hi， i want to know how to use Tensor Core PTX(like,mma.sync.aligned.m16n8k16.row.col.f32.f16.f16.f32) in Triton?

those are generated by the compiler when possible (based on type, shape, target) for kernels using tl.dot

Thank you for your reply， But If I want to customize some operators based on PTX, did Tirton provide these ptx in some way?

I don't think triton offers low level control of PTX codegen... What do you have in mind?


Community

Why wouldnt you tell people they must make a Folder named Community in the package you have released. Nobody can get this to work because they dont understand the error codes. Simple

now if i didnt know any better I wouldnt have a clue what that meant. All you say is README README, Ive seen you be half rude to several people now about your readme file. Have you read it? And MOSTLY!! why isnt it included in your package?!?!?!
Its as If you just expect everyone to have a folder named "MSFSaddons", to which they add your folder to as well as go into your folder and create yet another file named "community".
Your read me says to simply extract to packages, sorry bud but that doesnt even work

Please follow the instructions in the Readme, especially this part:

Simply unzip the content of the ZIP file into the MSFS “Packages” folder (parent directory of the “Community” folder which contains all mods)

I can see from the error message in your screenshot that you have not followed these instructions and unzipped it in the wrong directory, namely in your Computer's Downloads folder rather than in the MSFS “Packages” folder.


Rock Paper Scissors

a game made using java, rock paper scissors, simply uses the concept of generating random numbers and using them as outputs from computer.

@Romi904 kindly review my PR.


Do not duplicate OPENSSL_armcap_P on 32 bit ARM

The declaration in armcap.c was duplicate.
This resolves CI failures on cross-compile builds on ARM.

This pull request is ready to merge

Merged to master branch. Thank you for the reviews.

BTW, how did you find this? Did you spot this particular duplicated symbol (just noticed, or a link error somewhere?) or did you write the checker first?

Hmm... actually it seems this PR did not fix the problem fully - it fixed the https://github.com/openssl/openssl/actions/runs/4531614374/jobs/7981985115 arm-linux-gnueabi build but it did NOT fix the arm-linux-gnueabihf build https://github.com/openssl/openssl/actions/runs/4531614374/jobs/7981985290
@tom-cosgrove-arm do you have any idea what could be missing?

@t8m I'll take a look

Okay, the issue is
crypto/armv4cpuid.pl:.comm	OPENSSL_armcap_P,4,4
crypto/bn/asm/armv4-gf2m.pl:.comm	OPENSSL_armcap_P,4,4
crypto/bn/asm/armv4-mont.pl:.comm	OPENSSL_armcap_P,4,4
crypto/chacha/asm/chacha-armv4.pl:.comm	OPENSSL_armcap_P,4,4
crypto/poly1305/asm/poly1305-armv4.pl:.comm   OPENSSL_armcap_P,4,4
crypto/sha/asm/sha1-armv4-large.pl:.comm	OPENSSL_armcap_P,4,4
crypto/sha/asm/sha256-armv4.pl:.comm   OPENSSL_armcap_P,4,4
crypto/sha/asm/sha512-armv4.pl:.comm	OPENSSL_armcap_P,4,4

i.e. the "multiple" symbols are all coming from libcrypto.a.
They are only emitted in the hf build, because that is __ARM_ARCH == 7; the non-hard-float build is  __ARM_ARCH == 5
as(1) says ".comm declares a common symbol named symbol. When linking, a common symbol in one object file may be merged with a defined or common symbol of the same name in another object file." i.e. these are expected to be merged - they're intended to be the same symbol.
I don't know the history of this code - I suspect the intent was that these assembler files could be used independently.
I'll check if we can just replace the .comms with .externs, and then re-instate OPENSSL_armcap_P from armcap.c on all builds, not just aarch64. (I'm sure that would be fine on aarch64 - it's already done that way there - but there may be "nuances" (!) on armv4 builds...

Using .extern works (in local testing, anyway) so I'll raise a PR for that (after internal review, natch, sorry)


account.history doesn't return the latest transaction

When I try with the .rawhistory function, I get one more transaction.
from piston.steem import Steem
from piston.account import Account

account=Account('mebot')

h = 0
r = 0

for i in account.history():

    h += 1

for i in account.rawhistory():

    r += 1

print(h)
print(r)

returns:
2
3

Yes, its a bug. It has been fixed in python-steem library, feel free to backport it to Piston.

I didn't even know there was a steem-python library.
The rebranding and name changing is very confusing.

steem-python is a fork of Piston, and an 'official' Steem library.


Release pyqtconsole v1.2.0

A release is probably in order.

I'm going to merge this on my own, let me know if I should wait next time. Best, Thomas

No problem, thanks ! :)


Smalltalk language: Rename variable assignment operator from "<-" to ":="

For more compatibility with other Smalltalk implementations.

Implemented with commit earlier today.


Add VS 16.1 build tools to 3.5 and 4.8 SDK images

LGTM - the PR title is a little misleading since this applies to all SDK images.

Getting my PRs all jumbled together.  I'll fix it.


nodejs 0.10.40 installed into wrong directory

When installing nodejs 0.10.40 via nvm the nodejs binaries end up under
[nvm_root]/v0.10.40 and not under
[nvm_root]/versions/node/v0.10.40
nodejs 0.12.7 and 4.1.1 however are installed under [nvm_root]/versions/node/ as expected.
Tested on RHEL6.6 with nvm 0.26.1.

This is the right directory. "/versions/node" is new with 0.12.0 and later only.


Is it possible to sort keys in json_object

I am using jansson library to create nested JSON data structure.
But I am not able to sort the keys of json object. Is it possible to sort a JSON Object according to keys after creation ?
Note: I am not using json_dumps or json_loads. I have to create nested DS using json_object_set* functions.

In Jansson 2.8 and later, the insertion of object keys is preserved. If you can construct your data structure in such a way that you insert the items in the correct order, then you're done. You can also do this in a separate step, taking an object, sorting its keys, and creating a new object with the keys in the correct order.

@akheron

You can also do this in a separate step, taking an object, sorting its keys, and creating a new object with the keys in the correct order.
How to do this ? Can you provide a simple example ?

Adapted from how json_dumps() and friends implement JSON_SORT_KEYS encoding flag (around line 300 in src/dump.c):
/* A helper to sort strings lexically/alphabetically */
static int sort_lexically(const void *key1, const void *key2) {
    return strcmp(*(const char **)key1, *(const char **)key2);
}

json_t *sort_object(json_t *object) {
    const char **keys;
    size_t size, i;
    json_t *result;

    /* Collect object keys to the `keys` array */
    size = json_object_size(object);
    keys = malloc(size * sizeof(const char *));
    if(!keys)
        return NULL;

    i = 0;
    while(iter)
    {
        keys[i] = json_object_iter_key(iter);
        iter = json_object_iter_next(object, iter);
        i++;
    }
    assert(i == size);

    /* Sort the `keys` array. qsort() is a standard library
     * function. */
    qsort(keys, size, sizeof(const char *), sort_lexically);

    /* Iterate through the now sorted `keys` and insert values from
       `object` to `result` in that order */
    result = json_object();
    for(i = 0; i < size; i++) {
        const char *key;
        json_t *value;

        key = keys[i];
        value = json_object_get(object, key);
        assert(value);

        json_object_set(result, key, value);
    }

    /* Returns a new reference */
    return result;
}

I didn't even try to compile this, so it may have errors. But I hope you get the idea :)

@akheron Thanks.
I will check this.


Remove spaces from CFBundleExecutable key

Fixes #339.
and Squirrel.Windows bug "Windows shortcut doesn't work when productName contains a space" (https://github.com/electron-userland/electron-builder/issues/339)
Related issue: https://github.com/electron-userland/electron-builder/issues/288
Yes, this commit breaks electron-builder, but it will be fixed today in a separate commit (maybe some changes will be required on electron-packager side).

This is blocked on #340.

I'm not sure about the Windows change. If it's only a problem with Squirrel.Windows shortcuts, can't electron-builder deal with that?

can't electron-builder deal with that?

Yes, it can be fixed on electron-builder side. But I think it will be useful in the electron-packager.
On the other hand — yes, we should do avoid unnecessary escaping. I will revert.

The fix is not really correct — app LEGO Digital Designer works for me. Executable is LEGO Digital Designer. Hmm... I will investigate.

OS X — it is OS bug.
Windows — fixed in Squirrel.Windows.
About strict — I will prepare PR to use ES6 in my other PRs.

@develar By the way, I found out last night (via node.green) that you don't need 'use strict' to use const.

@malept In the recent V8 VM (part of nodejs 6?), yes, strict mode is not required to use let/const. But we should support nodejs 4/5.

@malept http://v8project.blogspot.de/2016/01/v8-release-49.html "Release 4.9 also makes block level constructs such as class and let available outside of strict mode"

@develar you should look at http://node.green/

@malept Not quite understand what do you mean.
I see "is block-scoped (strict mode)"
function test() {
  let foo = 22;
}

/Users/develar/Documents/electron-packager/foo.js:2
  let foo = 22;
  ^^^

SyntaxError: Block-scoped declarations (let, const, function, class) not yet supported outside strict mode
    at exports.runInThisContext (vm.js:53:16)
    at Module._compile (module.js:387:25)
    at Object.Module._extensions..js (module.js:422:10)
    at Module.load (module.js:357:32)
    at Function.Module._load (module.js:314:12)
    at Function.Module.runMain (module.js:447:10)
    at startup (node.js:148:18)
    at node.js:405:3

Oh, I read node, not v8.


Switch Raspberry Pi building to unofficial GCC 6.5 toolchain

PiperOrigin-RevId: 267155769
This cherry-pick is needed to fix the issue #35062.

@mihaimaruseac , this is another cherry-pick PR for r1.15 which is required to fix the issue #35062.

LGTM but it will have to wait ~3-4 days as I finished the 1.15 cherrypicks and moved to the 2.1 ones. Then I'll do the 2.1.1 release and only after that I'll switch the build system to the one used for 1.15 and 2.0.


chore(main): release 1.3.0

:robot: I have created a release beep boop
1.3.0 (2024-05-07)
Features

icons for mkdown (#202) (83848be)
list: add className prop forwarding to List and ListItem (#204) (bc31c7e)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/Arize-ai/ui-components/releases/tag/v1.3.0 :sunflower:


fix ts error (could not find a declaration file...)  when using in TS project

error TS7016: Could not find a declaration file for module 'vue-awesome-paginate'. '/path/node_modules/vue-awesome-paginate/dist/index.js' implicitly has an 'any' type.
There are types at '/path/node_modules/vue-awesome-paginate/dist/VueAwesomePaginatePlugin.d.ts', but this result could not be resolved when respecting package.json "exports". The 'vue-awesome-paginate' library may need to update its package.json or typings.
fix #18

Thanks for the fix, helped get through my project!


Terrible "First pull vs Consecutive Pulls" Performance Comparison

Due to the encoding performance of python-ndn, the first-pull vs consecutive pulls comparison drastically shows that the application nr-archway gains no real advantage till after 8+ pulls of the same data. As such, efforts are currently being made to reduce encoding time effectively decreasing the number of pulls needed to see an advantage when using nr-archway.
Ideally, nr-archway would only need 2 pulls of the same data to meet or be better than traditionally pulling the data from the original location.
This is the leading problem with nr-archway as it stands now. FTP is also the only interface it works with, but we are confident that we can quickly add more interfaces once we solve this performance issue.
This issue will be updated as more information is found out or solved relating to the performance of nr-archway.

Issue on python-ndn's part: https://github.com/named-data/python-ndn/issues/33#issue
Encoding Performance Comparison: https://github.com/zjkmxy/ndn-encoding-test/blob/main/performance_results.md


Add more details to the docs

Tweaked the docs a bit to detail some issues we've encountered while setting up.

thanks :+1:


insiders.liveshare.vsengsaas.visualstudio.com not chaining intermediate cert

Hello --
If you run this command in a shell
echo | openssl s_client -showcerts -servername insiders.liveshare.vsengsaas.visualstudio.com -connect insiders.liveshare.vsengsaas.visualstudio.com:443
then you can see that your site is not sending back the intermediate certificate in the chain, which is "Microsoft IT TLS CA 2". This means that some clients will not be able to negotiate a TLS channel. This is easy to reproduce with curl:
phkelley@cort:~$ curl -I https://insiders.liveshare.vsengsaas.visualstudio.com
curl: (60) server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
More details here: http://curl.haxx.se/docs/sslcerts.html

curl performs SSL certificate verification by default, using a "bundle"
 of Certificate Authority (CA) public keys (CA certs). If the default
 bundle file isn't adequate, you can specify an alternate file
 using the --cacert option.
If this HTTPS server uses a certificate signed by a CA represented in
 the bundle, the certificate verification probably failed due to a
 problem with the certificate (it might be expired, or the name might
 not match the domain name in the URL).
If you'd like to turn off curl's verification of the certificate, use
 the -k (or --insecure) option.

Thanks

@phkelley Thanks for reporting this.  It's also directly related to #86 since Linux clients suffer from this problem and many proxies are linux based.
There is a staged fix for this pending deployment to the insiders environment.

Great thank you

@phkelley This should be resolved now.  Let us know if you are still seeing issues.

Looks fixed to me, thanks Chuck


enh/101-hpc-batch-exp-runs

Right now it runs all the simulations for an experiment at once. However, on
Mesabi nodes which have 24 cores, I can only use 48 at a time. So if I want to
average the results of 100 runs I need to be able to specifythe # of jobs that
parallel can run in parallel when running on HPC.

GNU Parallel already does this by default I think


Slider images are all visible on reload until js is loaded

Issue description:
Shopware 6.2.3 is using tiny-slider 2.9.2.
During the page load the images are all visible (below each other). Once the js files are loaded, the slider is displayed correctly. Just the active image is visible. The problem is, the hole website is "jumping" on every page load.
I have added a lazy loading plugin to Shopware which is also reducing the issue but it's not completely gone.
Demo link/slider setting: intern test
Tiny-slider version:   2.9.2
Browser name && version:  Tested with Chrome 84.0.4147.105 and Firefox 79.0
OS name && version:   Happens on all system. (Tested with MacOS 10.15.6 and Win10 Pro)

You can fix this via css (flex on parent and overflow scroll as fallback)

You can fix this via css (flex on parent and overflow scroll as fallback)

Can you show an example?

My slide item 1

My slide item 2

  ...

My slide item 1

My slide item 2

  ...

My slide item 1

My slide item 2

  ...

.my-slider:not(.tns-slider) {
  display: flex;

  /* Scroll fallback example */
  overflow-x: auto;

  /* Can even add scroll snapping */
  scroll-snap-type: x mandatory;
}

.my-slider-item {
  scroll-snap-align: start;
  user-select: none;

  /**
   * Some sizing. I know, this is experimental,
   * but a shorthand instead of ::before block fallback.
   * Just for understanding the size of slide
   */
  aspect-ratio: 4 / 3;

  /* Just for visual detection of slide */
  border: 1px solid #000;
  border-radius: 4px;

  /* If we need single slide */
  flex-basis: 100%;
  flex-grow: 1;
  flex-shrink: 0;

  /* Media fallbacks */
}

.my-slider.custom:not(.tns-slider) .my-slider-item {
  /**
   * If we need more:
   * 2: flex-basis: 50%;
   * 3: flex-basis: 33.333%;
   * ...and so on
   */
  flex-basis: 33.333%;
}

/* If you don't want scroll fallback, then */
.my-slider.overflow-hidden:not(.tns-slider) {
  overflow: hidden;
}

Demo
Other margins and paddings you can handle by yourself. There's still gonna be a small layout thrashing (especially with scroll fallback), but it better to have fallbacks on simple sliders, I think.


docs(prom-example): remove deprecated startServer

and destructure DEFAULT_OPTIONS to obtain port endpoint to make log message more compact

closed in favor of https://github.com/open-telemetry/opentelemetry-js/pull/2802


Unconfigured source in geometry field causing issues

Steps to reproduce

Create a geometry page block
Add a source event without selecting a module
See error in the console

Expected behaviour
We shouldn't save unconfigured sources

I'll require more clarity to continue on this.

Tested and confirming that this is now fixed.

CL Entry
What Changed?
The Geometry Block
How did it change?

The way form fields are ordered in the 'Configured Sources' tab.
The requirements for which the Geometry block is evaluated. Now you need to have selected a module and Geometry field.
Required fields now have an asterisk for indication.


Remove Jquery, Popperjs, bootstrapjs and Added CSS only modal, & RWD

Remove the bootstrap.css file from the index.html file and import only the required modules using sass

Closing in favour of https://github.com/Aroliant/DevTools/commit/079ae1f1ceafee4d148e9e22f3decb61f25e6daf


run DDF.to_sql tests in local Client() mode

(this PR forks off of https://github.com/dask/dask/pull/6038)
The tests pass, but there are some warnings (and apparent ~3s timeouts between test cases) worth trying to understand:
pytest -s dask/dataframe/io/tests/test_sql.py::test_to_sql

============================================================================================================== test session starts ===============================================================================================================
platform darwin -- Python 3.8.1, pytest-5.3.5, py-1.8.1, pluggy-0.13.1
rootdir: /Users/ryan/c/dask, inifile: setup.cfg
collected 4 items

dask/dataframe/io/tests/test_sql.py .distributed.worker - WARNING -  Compute Failed
Function:  make_meta
args:      (Empty DataFrame
Columns: [name, age, negish]
Index: [])
kwargs:    {}
Exception: ValueError("Table 'test' already exists.")

distributed.worker - WARNING -  Compute Failed
Function:  _sequence
args:      ([])
kwargs:    {}
Exception: ValueError("Table 'test' already exists.")

distributed.nanny - WARNING - Worker process still alive after 3 seconds, killing
..distributed.worker - WARNING -  Compute Failed
Function:  make_meta
args:      (Empty DataFrame
Columns: [name, age, negish]
Index: [])
kwargs:    {}
Exception: ValueError("Table 'test' already exists.")

distributed.worker - WARNING -  Compute Failed
Function:  _sequence
args:      ([])
kwargs:    {}
Exception: ValueError("Table 'test' already exists.")

distributed.nanny - WARNING - Worker process still alive after 3 seconds, killing
.

================================================================================================================ warnings summary ================================================================================================================
dask/dataframe/io/tests/test_sql.py::test_to_sql[1-True]
dask/dataframe/io/tests/test_sql.py::test_to_sql[2-True]
  /Users/ryan/.pyenv/versions/dask-3.8.1/lib/python3.8/site-packages/distributed/dashboard/core.py:79: UserWarning:
  Port 8787 is already in use.
  Perhaps you already have a cluster running?
    Use -vv to show these durations.)
========================================================================================================= 4 passed, 2 warnings in 18.20s =========================================================================================================

Hypothesis
I think what's happening is:

the "Compute failed… Table 'test' already exists." messages are generated by tests where we're causing errors intentionally, and verifying they're raised
however, I think I'm not propagating the errors correctly in my chain helper (for linearizing the dependency graph), and the workers end up hanging until they timeout at Client shutdown time

Windows 3.6 (spurious?) failure in dask/tests/test_config.py::test_collect_env_none:
>           assert config == {"foo": "bar"}
E           AssertionError: assert {'foo': 'bar', 'parent': 2132} == {'foo': 'bar'}
E             Omitting 1 identical items, use -vv to show
E             Left contains 1 more item:
E             {'parent': 2132}

also in Windows 3.8.
Windows 3.7 spuriously failing dask/array/tests/test_routines.py::test_cov (also seen in https://github.com/dask/dask/pull/6038#issuecomment-606285301)

I commented out the pytest.raises test-case that seemed to be generating some of the warn-spam above, but the strange timeouts, and warnings about distributed.nanny - WARNING - Worker process still alive after 3 seconds, killing, remained:
pytest -s dask/dataframe/io/tests/test_sql.py::test_to_sql
============================================================================================================== test session starts ===============================================================================================================
platform darwin -- Python 3.6.10, pytest-5.4.1, py-1.8.1, pluggy-0.13.1
rootdir: /Users/ryan/c/dask, inifile: setup.cfg
collected 4 items

dask/dataframe/io/tests/test_sql.py .distributed.nanny - WARNING - Worker process still alive after 3 seconds, killing
..distributed.nanny - WARNING - Worker process still alive after 3 seconds, killing
.

=========================================================================================================== slowest 10 test durations ============================================================================================================
8.67s call     dask/dataframe/io/tests/test_sql.py::test_to_sql[1-True]
8.38s call     dask/dataframe/io/tests/test_sql.py::test_to_sql[2-True]
1.22s call     dask/dataframe/io/tests/test_sql.py::test_to_sql[1-False]
0.66s call     dask/dataframe/io/tests/test_sql.py::test_to_sql[2-False]

(0.00 durations hidden.  Use -vv to show these durations.)
=============================================================================================================== 4 passed in 20.14s ===============================================================================================================

Still interested to understand whether that's normal/ok, or an artifact of my "task-chaining" logic.


Unable to debug

As a server admin, being able to specify which plug-in I want to debug is extremely valuable.
Currently to debug, the plug-in requires the -D mode be used at the Homebridge level which means all plugins are put into debug mode.
This means the logs are likely unusable for debugging just one if there are many plugins installed.

Tried to do this on the server earlier when the switch flipped even though the mower was active and headed back home.
My guess was the restricted reason flipped to not applicable for some reason, but I could not confirm.

The colors also show up the wrong color according to the logger class. Warns are showing up as red with errors, and debug is blue along with info.

The colors also show up the wrong color according to the logger class. Warns are showing up as red with errors, and debug is blue along with info.

Turns out, the coloring issue is really within Visual Studio Code messing with the colors that the application is producing and removing them.


Improve first use experience

This was first posted on codeplex by Tomasp
When you clone the repo for the first time, there is a couple of things that make the first experience annoying:
*I downloaded the code and tried opening "fsharp.sln" to look at it - this does not work (the projects fail to load in VS 2013), because you first need to build the proto compiler (which generates some targets file that is referenced from the projects). This is pretty bad first-open experience!

Next, I tried to follow the DEVGUIDE. Now, "gacutil" in step 1 is not usually in your PATH - but I knew that so I opened VS Command Prompt (Windows search returned command prompt for VS 2012 though!) and I ran the "gacutil" command. This failed because I need Admin rights (which is not mentioned in the DEVGUIDE), so I had to reopen the prompt in admin mod.

I tried running the "msbuild" command next, which failed (with confusing error involving resource manifests - it actually looks like a real error in the code!) This was because I used wrong MSBUILD version (the one from VS Command Prompt 2012).

I guess you should be able to open "fsharp.sln" when you get the code (even if you do not want to build anything). The MSBUILD issues can be expected - but the error should be better (or the guide should be more clear about this).

comments
latkin wrote Dec 17, 2014 at 4:09 PM [x]

I have a pending update internally which will remove the need for GACing the old FSharp.Core version. This will help a lot - no more need for admin on first build.

We can update DEVGUIDE to point to  https://visualfsharp.codeplex.com/wikipage?title=Required Software which lists MSBuild 12.0 as a requirement and provides a download link. VS is linked, too, but 2013 is not explicitly stated as the version. Certainly this could be polished.

I don't have a good answer for the proto targets. Making that "just work" first time with no user action will require nontrivial refactoring of how the repo is set up.

cc @tpetricek

@tpetricek do you feel this has improved any? The following is in place:

gacutil is no longer needed on first build of proto
README links directly to Required Software page, which lists VS 2013 (and thus msbuild 12.0) as requirements

You still need to build proto before you open the sln though.


evaluation results significantly different

hello, is the provided model the best one? why are the evaluation results I obtained significantly different from the provided results?
The method I used is as follows:

This low performance was caused by a mis-config of hyper parameter nms_thres, which was set to 0.0 but should be 0.6. It is now fixed in the latest commit. Please feel free to have a try.


Improve code style and remove unneeded language keywords

SwiftLint and Xcode throw warnings when building the code.
Feel free to merge this PR if you agree with the code style and changes.

@alexsteinerde nice, thanks for your update ;)


Update boost pin

@MaxRis Is this the same failure we were seeing in Arrow before?

@xhochy yes, it should be it, since -DBOOST_ALL_NO_LIB  is not defined for static boost libs linkage. I can patch it as well.

@MaxRis as always this would be very much appreciated.

@xhochy have created PR with patch https://github.com/jschueller/parquet-cpp-feedstock/pull/1
Build passed there https://ci.appveyor.com/project/MaxRisuhin/parquet-cpp-feedstock/build/1.0.12
thanks!


Handle torch.seed

@jansel This is probably the incorrect way, looking for feedback.
The generated Fx graph for
        def fn(x):
            attention_seed = int(torch.seed() % sys.maxsize)
            torch.manual_seed(attention_seed)
            return ()

is

def forward(self):
    seed = torch.random.seed()
    mod = seed %<PHONE_NUMBER>854775807;  seed = None
    int_1 = int(mod);  mod = None
    manual_seed = torch.random.manual_seed(int_1);  int_1 = None
    return ()

Ready for review.


Add PremierProfiles call

Added an extension method for the PremierProfiles API.
Note: The PremierProfilesResponse is incomplete.  This file should be considered something like a starting point implementation.  I wasn't sure how much reuse of the internal structure you'd want so I kept the nested objects in the same file.  Also, the majority of the properties are not present as they were not relevant to what I needed.

Merging into a separate branch so the work can be completed and merged to master.

Thanks for the heads up. We'll modify that when we split out the classes and finish off the attributes.
If you didn't know, until it is merged, you can continue to update a PR by making commits to the source branch. So feel free to do so in the future.

Yeah I intended to just got caught up in other things :)
Thanks for the heads up though.

No problem. I'm not sure when we'll have the feature finished and tested but you can track the work here: https://github.com/experianplc/experian-dotnet/tree/PremierProfilesUpdate I've already made that change to API Extensions you highlighted.


defaultMergedResolver unexpected behaviour for aliased and nullable fields

This is a somewhat odd one, but caused a lot of headache before I figured out where it went wrong. Essentially, I have a GraphQL server as an api-gateway, that links to other services through the magic of makeRemoteExecutableSchema. Here's a tiny working example of the setup:
import { execute, toPromise } from 'apollo-link';
import { createHttpLink } from 'apollo-link-http';
import { ApolloServer, gql } from 'apollo-server';
import {
  buildClientSchema,
  IntrospectionQuery,
  introspectionQuery,
  parse,
} from 'graphql';
import {
  makeExecutableSchema,
  makeRemoteExecutableSchema,
} from 'graphql-tools';
import fetch from 'node-fetch';

async function startAPI() {
  // Create the link to the backend service
  const link = createHttpLink({
    uri: 'http://localhost:5001/graphql',
    fetch: fetch as any,
  });
  // Fetch the schema from the backend service
  const introspectedSchema = await toPromise(
    execute(link, { query: parse(introspectionQuery) }),
  ).then(res => res.data as IntrospectionQuery);

  const schema = makeRemoteExecutableSchema({
    link,
    schema: buildClientSchema(introspectedSchema),
  });
  // Start the API-server on port 5000
  const server = new ApolloServer({ schema });
  server
    .listen(5000)
    .then(() => console.log('API gateway started'))
    .catch(console.log);
}

async function startBackendService() {
  // TypeDefs with a non-root type
  const typeDefs = gql`
    type Product {
      name: String
      price(asOf: String): Int
    }
    type Query {
      products: [Product]
    }
  `;

  const resolvers = {
    Query: {
      products: () => {
        return [
          {
            name: 'First product',
            price: 1234,
          },
          {
            name: 'Another Product',
            price: 18,
          },
        ];
      },
    },
    Product: {
      /* Dummy resolver that return null for certain arguments */
      price: (
        source: { name: string; price: number },
        args?: { asOf?: string },
      ) => {
        if (args && args.asOf) {
          const requestedDate = new Date(args.asOf);
          const today = new Date();
          if (requestedDate > today) {
            return null;
          }
        }
        return source.price;
      },
    },
  };
  const server = new ApolloServer({
    schema: makeExecutableSchema({ typeDefs, resolvers }),
  });
  // Start the server on port 5001
  await server
    .listen(5001)
    .then(() => console.log('Backend started'))
    .catch(console.log);
}

startBackendService().then(startAPI)

Compiling and running the above code works fine and serves the playground on http://localhost:5000/ (and on 5001).
Also
# Write your query or mutation here
query{
  products{
    name
    priceTomorrow: price(asOf: "2020-07-16")
  }
}

yields the expected
{
  "data": {
    "products": [
      {
        "name": "First product",
        "priceTomorrow": null
      },
      {
        "name": "Another Product",
        "priceTomorrow": null
      }
    ]
  }
}

However, if we run
# Write your query or mutation here
query{
  products{
    name
    price
    priceTomorrow: price(asOf: "2020-07-16")
  }
}

we get
{
  "data": {
    "products": [
      {
        "name": "First product",
        "price": 1234,
        "priceTomorrow": 1234
      },
      {
        "name": "Another Product",
        "price": 18,
        "priceTomorrow": 18
      }
    ]
  }
}

where I would expect
{
  "data": {
    "products": [
      {
        "name": "First product",
        "price": 1234,
        "priceTomorrow": null
      },
      {
        "name": "Another Product",
        "price": 18,
        "priceTomorrow": null
      }
    ]
  }
}

This is due to the api-gateway assigning the defaultMergedResolver to the fields in Product, and the defaultMergedResolver not expecting fields to be null.
Note however that this only applies when the aliased field is accompanied by a field with the original field name (aliased or not). For example this query:
# Write your query or mutation here
query{
  products{
    price: name
    priceTomorrow: price(asOf: "2020-07-16")
  }
}

throws an error, even though I would expect it to return
{
  "data": {
    "products": [
      {
        "price": "First product",
        "priceTomorrow": null
      },
      {
        "price": "Another Product",
        "priceTomorrow": null
      }
    ]
  }
}

but this
# Write your query or mutation here
query{
  products{
    anyOtherAlias: price
    priceTomorrow: price(asOf: "2020-07-16")
  }
}

works perfectly fine.

This should just work correctly in graphql-tools-fork, as in the fork, the result is loaded from the correct responseKey with only a single attempt.

We recently released an alpha version of GraphQL Tools (#1308) that should fix the issue.
Please update graphql-tools to next or run:
npx match-version graphql-tools next

Let us know if it solves the problem, we're counting for your feedback! :)

Rolled into #1306, closing.


[2010-07-01] More consistent logging/inspection/output in Debug and other classes

created by: @chillu (ischommer)
assigned to: @chillu (ischommer)
created at: 2010-07-01
original ticket: http://open.silverstripe.org/ticket/5768

There's 1001 methods in SilverStripe to do logging, debugging and output. Some of them respect CLI mode, others enforce HTML, some of them render differently with Ajax requests. All in all: Its a mess. I would like to make this more consistent, ideally around Zend_Log. We also need to distinguish more clearly between output helpers like Debug::show() and logging (SS_Log::log()).
For the moment, I'm just collecting what we have - its unclear how this will be solved.
== Context ==
Context should really be handled by the requested Content-Type in the HTTP header. Any CLI scripts should ensure that "text/plain" is set. One use case is dev/build, which can be run through a URL with differently coloured HTML (and a header with linked breadcrumbs), but also on CLI with plaintext output.

CLI (plaintext, newlines, coloured output)
text/html: HTML tags, inline CSS
text/html: Ajax mode (no  tags)
Output supression: E.g. when running unit tests, no output might be desired at all (regardless of content-type)

== Methods: Output/Log ==

Debug::message() - Shows message through echo(), with optional header traceback and HTML styling
Debug::log() - Writes to a hardcoded file location in some non-standard log format
Debug::header() - Sends an HTTP header
Debug::show() - Does Debug::text() with more context around it
Debug::showError() - Uses DebugView class to write detailed error info.
Debug::emailError() - Uses SS_Log::log() and SS_LogEmailWriter
DebugView->writeInfo() - Writes HTML with optional header (and breadcrumbs!)
DebugView->writeError() - Wtites error as HTML
SS_Log::log() - Writes to one or more Zend_Log_Writer interface (can be email, HTML, etc)

== Methods: Inspection/Debugging ==

ViewableData::Debug()/ViewableData_Debugger - Lists methods/params about an object
Object::__toString() - Returns $this->class
DataObject/DataObjectSet->debug()/ - Returns HTML with Debug::text(). Not consistently implemented across objects.
Debug::text() - Outputs a value/object in HTML
Debug::dump() - Kinda like Debug::text()
SS_Backtrace::backtrace() - HTMLized version of PHP's built-in debug_backtrace()

Partially fixed with https://github.com/silverstripe/silverstripe-framework/pull/3266

Logging API has been semi-standardised with monolog as a base. See https://github.com/silverstripe/silverstripe-framework/pull/4430
This is likely the most work we'll do on addressing this, so I'm closing this ticket.


Error when running redis_setup.sh in command line

when I run ./redis_setup.sh
it showed following error
"./redis_setup.sh: line 4: [: too many arguments
Docker is already installed"
even when docker is not installed
it is due to an error in argument of if-else in line 4

@sandeepsajan0 installing Docker should not be done by this repo. A simple message "Docker is not installed" is enough. Plus, everything should be running using docker-compose, having docker and docker-compose installed is a pre-assumption and the repo should not take care of it.

the environment already runs with docker-compose. Unused scripts shall be removed and the README updated. the only way to run the repo shall be docker-compose.


Readme file and code of conduct enhancement

Could you please assign this issue to me under GSSOC'24 extd and Hacktoberfest? I would like to work on readme file and code of conduct make it more user-friendly . Thanks!
FEATURES I CAN ADD IF ASSIGNED :
1.navigation: your readme file is long and same goes for code of conduct for making it user friendly there should be navigation.
2.A little preview of code of conduct
3. Contact Information: Including a contact section for users to reach out with questions or suggestions, promoting open communication within the community.
4. A little preview of how to contribute .
5. Visual Design Improvements

Sure @itsbhh leeeesss gooo 🚀

I'd love to collaborate on this issue as part of GSSOC'24 and Hacktoberfest!
I have experience in improving documentation to make it more engaging and user-friendly.
My contributions will focus on:
-Integrating a contact section to ensure anyone with questions or suggestions can easily reach out, fostering better collaboration.
-Implementing subtle design tweaks for a more visually appealing and accessible document.
Looking forward to the opportunity to improve these elements for the benefit of the entire community.

I'd love to collaborate on this issue as part of GSSOC'24 and Hacktoberfest! I have experience in improving documentation to make it more engaging and user-friendly. My contributions will focus on: -Integrating a contact section to ensure anyone with questions or suggestions can easily reach out, fostering better collaboration. -Implementing subtle design tweaks for a more visually appealing and accessible document.
Looking forward to the opportunity to improve these elements for the benefit of the entire community.

Wait for @itsbhh if she not make a PR till tommorow i will assign you

@itsbhh any updates ??

@itsbhh any updates ??

Ya Till tomorrow morning you will receive the PR. Worked on Readme now working on code of conduct. Please wait till tomorrow.

@itsbhh any updates ??

Ya Till tomorrow morning you will receive the PR. Worked on Readme now working on code of conduct. Please wait till tomorrow.

Sure


Added poller to a resumable task store test to increase reliability

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

Project coverage is 98.69%. Comparing base (edf2021) to head (812e8dd).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #778   +/-   ##
=======================================
  Coverage   98.69%   98.69%
=======================================
  Files          73       73
  Lines       11263    11263
  Branches     1609     1609
=======================================
  Hits        11116    11116
  Misses        141      141
  Partials        6        6

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


Add WolframAlpha API material property queries

In the case of some material properties not being specified, this PR adds a function within the materials submodule to query the WolframAlpha API for a given property of a given material. The quantity is given in metric units.
This will be used by Stefano's material constructor to find properties and build OpenMC materials.
It is necessary to provide a key for access to the Wolfram Short Answers API, and free keys are limited to 2000 calls per month. Hence, CI testing can't realistically be performed at scale, but a manual testing protocol can be created.
Register for a key at developer.wolframalpha.com

Comments addressed


[-Werror=maybe-uninitialized] in main.c

When installing pgmoneta using the Git source, there are some errors in the source code after running the 'make' command.
`[ 91%] Building C object src/CMakeFiles/pgmoneta-bin.dir/main.c.o
In function ‘init_replication_slots’,
    inlined from ‘main’ at /usr/local/pgmoneta/src/main.c:626:20:
/usr/local/pgmoneta/src/main.c:1938:41: error: ‘slot_status’ may be used uninitialized [-Werror=maybe-uninitialized]
 1938 |          if (create_slot && slot_status == SLOT_NOT_FOUND && strlen(config->servers[srv].wal_slot) > 0)
/usr/local/pgmoneta/src/main.c: In function ‘main’:
/usr/local/pgmoneta/src/main.c:1848:8: note: ‘slot_status’ was declared here
 1848 |    int slot_status;
      |        ^~~~~~~~~~~
cc1: all warnings being treated as errors
make[2]: *** [src/CMakeFiles/pgmoneta-bin.dir/build.make:76: src/CMakeFiles/pgmoneta-bin.dir/main.c.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:174: src/CMakeFiles/pgmoneta-bin.dir/all] Error 2
make: *** [Makefile:156: all] Error 2`

What compiler and compiler version are you using ?

Fedora 38
gcc (GCC) 13.1.1 20230614 (Red Hat 13.1.1-4)
I just initiated it with SLOT_NOT_FOUND and ran successfully!
I researched and created a guide tailored for a new beginner to install this application on a Fedora 38 virtual machine. I compiled the guide by combining several references from the Git documentation.
hope it helpful
install.md

Can you send a pull request for this ?
Although it should be
int slot_status = INCORRECT_SLOT_TYPE;

I think your document could be a good start for a doc/DEVELOPERS.md file... So, can you send a pull request for that too ?

Remember to add yourself to the AUTHORS file as well...

sorry for twice PR


Need to improve the syntax highlighting in Rust

From @D101101 on January 20, 2016 17:1
Syntax highlighting for Rust works well, but in some places it is clearly not completed yet.

Copied from original issue: Microsoft/vscode#2130

From @crumblingstatue on February 3, 2016 15:1
I also find it confusing that keywords and type names share the same highlighting color.

+1

:+1:

You're talking about several issues at once here. In general, I agree that tokenizing (which leads to syntax highlighting) can be improved for some edge cases. Let's use separate issues for discussing/improving the details, since "highlighting needs to be improved" is a rather generic topic for an issue. As far as I can see, you're mentioning the following problems:
Highlighting of nested generics like Vec<Vec<u64>>: This has been fixed in #37.
Keywords and type names share the same highlighting color: This depends on the syntax theme you're using. Some themes use different colors, while unfortunately some themes are using same colors for keywords and types.
Box, BufReader and VecDeque are not highlighted: This is because they're not seen as types. Atom-language-rust currently only detects a few known types. These types are matched by string and were therefore intentionally limited to types in the prelude since these can be used without a namespace prefix. It would be nice to have every type highlighted, and maybe we could add a rule to match any type statement. But however, that would lead to the problem that arbitrary type names would be highlighted because atom-language-rust cannot verify if a type actually exists or not. I'm not sure if that would be desirable, but let's open a dedicated issue for this if you think so.
Variable identifier highlighted as type (let str: &str = ...): There seems to be a bug that causes variable names to be tokenized as a type if you name your variable like a core/std type (e.g. also happens with let i8: i8 = 8;).

Closing this in favor of separate issues


Fix deepmerge require

Attempting to use the yet-to-be-documented dynamicTemplateData (instead of substitutions, which doesn’t work) results in:

merge is not a function on line 289

This PR fixes the deepmerge require.

 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.

So doing this as a quick fix right on GitHub didn’t work out – I can see that test assertions for usage of merge are failing. I’ll look into it!

Closing the PR as this was an issue on our side.


Improve performance of gulp-tslint

Hi,
We're using gulp-tslint in our project which has around 200+ .ts files.
Works like it should 👍 although we've never used type-checking rules of tslint.
However, recently I wanted to give them a try and enable type-checking rules by passing program option in addition to configuration like this:
gulp.task('tslint:app', () => {
    let configuration = 'tslint.json';
    let program = tslint.Linter.createProgram('tsconfig.json');

    return gulp
        .src(['./app/**/*.ts'], { base: '.' })
        .pipe(gulpTslint({
            formatter: 'stylish',
            program,
            configuration
        }))
        .pipe(gulpTslint.report());
});

And here I noticed how a bit slower it checks each file than tslint CLI.
I saw that map(...) part in index.ts includes creating instance of tslint.Linter for each and every file.
Perhaps, it'd be better having only once instance of tslint.Linter defined outside of map loop?
I just compared it to the code in tslint itself (runner.ts processFiles which is called from CLI) and it also has only once instance of linter.
I believe downside to that will be that
The only thing that needs to be added inside the loop before cb(...) is: tslint.failures = []; tslint.fixes = []; so that failures will not be carried over to the next file.
What do you think? Is it worth creating a PR for that?

Go for it 👍


[Bugfix] Fix bug of xformer prefill for encoder-decoder

FILL IN THE PR DESCRIPTION HERE
The K and V should not be cut off for encoder-decoder model, because they are calculated from the vision encoder output. The length of K and V is the number of image tokens, which is different than the number of prompt tokens.
BEFORE SUBMITTING, PLEASE READ THE CHECKLIST BELOW AND FILL IN THE DESCRIPTION ABOVE

 PR Checklist (Click to Expand)
Thank you for your contribution to vLLM! Before submitting the pull request, please ensure the PR meets the following criteria. This helps vLLM maintain the code quality and improve the efficiency of the review process.
PR Title and Classification
Only specific types of PRs will be reviewed. The PR title is prefixed appropriately to indicate the type of change. Please use one of the following:

[Bugfix] for bug fixes.
[CI/Build] for build or continuous integration improvements.
[Doc] for documentation fixes and improvements.
[Model] for adding a new model or improving an existing model. Model name should appear in the title.
[Frontend] For changes on the vLLM frontend (e.g., OpenAI API server, LLM class, etc.)
[Kernel] for changes affecting CUDA kernels or other compute kernels.
[Core] for changes in the core vLLM logic (e.g., LLMEngine, AsyncLLMEngine, Scheduler, etc.)
[Hardware][Vendor] for hardware-specific changes. Vendor name should appear in the prefix (e.g., [Hardware][AMD]).
[Misc] for PRs that do not fit the above categories. Please use this sparingly.

Note: If the PR spans more than one category, please include all relevant prefixes.
Code Quality
The PR need to meet the following code quality standards:

We adhere to Google Python style guide and Google C++ style guide.
Pass all linter checks. Please use format.sh to format your code.
The code need to be well-documented to ensure future contributors can easily understand the code.
Include sufficient tests to ensure the project to stay correct and robust. This includes both unit tests and integration tests.
Please add documentation to docs/source/ if the PR modifies the user-facing behaviors of vLLM. It helps vLLM user understand and utilize the new features or changes.

Adding or changing kernels
Each custom kernel needs a schema and one or more implementations to be registered with PyTorch.

Make sure custom ops are registered following PyTorch guidelines: Custom C++ and CUDA Operators and The Custom Operators Manual
Custom operations that return Tensors require meta-functions. Meta-functions should be implemented and registered in python so that dynamic dims can be handled automatically. See above documents for a description of meta-functions.
Use torch.libary.opcheck() to test the function registration and meta-function for any registered ops.  See tests/kernels for examples.
When changing the C++ signature of an existing op, the schema must be updated to reflect the changes.
If a new custom type is needed, see the following document: Custom Class Support in PT2.

Notes for Large Changes
Please keep the changes as concise as possible. For major architectural changes (>500 LOC excluding kernel/data/config/test), we would expect a GitHub issue (RFC) discussing the technical design and justification. Otherwise, we will tag it with rfc-required and might not go through the PR.
What to Expect for the Reviews
The goal of the vLLM team is to be a transparent reviewing machine. We would like to make the review process transparent and efficient and make sure no contributor feel confused or frustrated. However, the vLLM team is small, so we need to prioritize some PRs over others. Here is what you can expect from the review process:

 After the PR is submitted, the PR will be assigned to a reviewer. Every reviewer will pick up the PRs based on their expertise and availability.
 After the PR is assigned, the reviewer will provide status update every 2-3 days. If the PR is not reviewed within 7 days, please feel free to ping the reviewer or the vLLM team.
 After the review, the reviewer will put an  action-required label on the PR if there are changes required. The contributor should address the comments and ping the reviewer to re-review the PR.
 Please respond to all comments within a reasonable time frame. If a comment isn't clear or you disagree with a suggestion, feel free to ask for clarification or discuss the suggestion.

Thank You
 Finally, thank you for taking the time to read these guidelines and for your interest in contributing to vLLM. Your contributions make vLLM a great tool for everyone!

LGTM. But can you take a deeper look on why the current tests can be passed and fix the unit tests at tests/kernels/test_encoder_decoder_attn.py

After some deep investigation, I found that the current unit test can pass with the bug is just because an unexpected behavior (or bug) of xformers.
Although the K and V are cut off by wrong length, here we calculate attention bias using the correct length. So this will trigger an unexpected behavior of xformers.memory_efficient_attention.
I fied a bug to xformers for this https://github.com/facebookresearch/xformers/issues/1122
In summary, xformers makes the result unexpectedly correct even without this PR's fix.


Missing "type" declarations

Something I noticed in a few places, and I'm not sure if this is valid JsonSchema or not...

In several traits with multiple forms (OneOf, AnyOf, etc.) the ROOT schema is missing any type declaration ("object" I would expect)... is that on purpose?
On some of the multi-format values that discriminate by enum value (See SensorState), seem to specify their ENUM values without specifying a type for properties... is this valid? I know the property definition carries the type in that instance, but my understanding was an enum node needed to specify a type still...

We usually nest the actual type inside the oneOf to make it easier to read the sub-schema as an individual unit.
Looking at https://tools.ietf.org/html/draft-handrews-json-schema-validation-01#section-6.1.1 it doesn't look like type nor enum  but I agree it could make thing more readable (an enum without a type couldn't be taken as an hint that value of multiple types could be accepted).

We usually nest the actual type inside the oneOf to make it easier to read the sub-schema as an individual unit.
Looking at https://tools.ietf.org/html/draft-handrews-json-schema-validation-01#section-6.1.1 it doesn't look like type nor enum  but I agree it could make thing more readable (an enum without a type couldn't be taken as an hint that value of multiple types could be accepted).

Thank you, Im unfamiliar with JSONSchema so I'm not sure what the rules are.
I was looking at the possibility of on the fly transforming your schema validations into a validation layer to get some of the business rules represented therein for free. I was hoping for a shortcut by inheriting your business rules, but I think I'm going to have to consider some other options.
Thanks again for this repo, its a huge help.

Thank you, Im unfamiliar with JSONSchema so I'm not sure what the rules are.
I was looking at the possibility of on the fly transforming your schema validations into a validation layer to get some of the business rules represented therein for free. I was hoping for a shortcut by inheriting your business rules, but I think I'm going to have to consider some other options.
Thanks again for this repo, its a huge help.

@i8beef depending on the language you're using there might be validation options already available: https://json-schema.org/implementations.html#validators

@i8beef depending on the language you're using there might be validation options already available: https://json-schema.org/implementations.html#validators

Im not validating Google Home messages, I'm validating app config structures that are needed for my bridging app. I tried to keep said config as close to the object structures you use, where each device has attributes, commands and states. The attributes are 1:1 so I load your schema into a validator directly and it works great. I was hoping to do the same for commands and states by transforming your schema into one that would validate my config structures, but I've found that doesn't work that great. oneOf, anyOf, enums, "missing" type declarations (that I can take from other places if I do this differently) kind of shot that in the foot.
Not your issue, I was just looking for a short cut. It'll be better if I parse your schema, and then recursively loop through it to generate a new JSON file, and parse THAT instead for my validations, where I can take an additive approach instead of a subtractive one.
Thanks again!

Im not validating Google Home messages, I'm validating app config structures that are needed for my bridging app. I tried to keep said config as close to the object structures you use, where each device has attributes, commands and states. The attributes are 1:1 so I load your schema into a validator directly and it works great. I was hoping to do the same for commands and states by transforming your schema into one that would validate my config structures, but I've found that doesn't work that great. oneOf, anyOf, enums, "missing" type declarations (that I can take from other places if I do this differently) kind of shot that in the foot.
Not your issue, I was just looking for a short cut. It'll be better if I parse your schema, and then recursively loop through it to generate a new JSON file, and parse THAT instead for my validations, where I can take an additive approach instead of a subtractive one.
Thanks again!

@i8beef for applying transformation on JSON schemas you might want to take a look at https://cuelang.org as it provides a nice declarative way to work with schema and data.
I'd be happy to add missing "type" declaration for enum (2) if it makes things easier to consume by downstream tool, I'm just not sure if it wouldn't make things more confusing for top-level anyOf/oneOf (1).

@i8beef for applying transformation on JSON schemas you might want to take a look at https://cuelang.org as it provides a nice declarative way to work with schema and data.
I'd be happy to add missing "type" declaration for enum (2) if it makes things easier to consume by downstream tool, I'm just not sure if it wouldn't make things more confusing for top-level anyOf/oneOf (1).

Honestly I'd prefer you just follow whatever the JSONSchema best practices are here. My questions were more just about triggering a review of these if there was something missed, or if it was intentional. What I was trying to do was questionable, and its not surprising I hit issues. You shouldn't pollute your schemas for me here unless there's a legitimate deviation from what the JSON Schema specs say you should do.

Honestly I'd prefer you just follow whatever the JSONSchema best practices are here. My questions were more just about triggering a review of these if there was something missed, or if it was intentional. What I was trying to do was questionable, and its not surprising I hit issues. You shouldn't pollute your schemas for me here unless there's a legitimate deviation from what the JSON Schema specs say you should do.

We currently only enforce that all sub-schemas with properties also have type defined, but we should probably also apply this logic to top-level schemas and individual non-enum properties.

We currently only enforce that all sub-schemas with properties also have type defined, but we should probably also apply this logic to top-level schemas and individual non-enum properties.


type of ID is changed

in this example the ID is changed from a int to a floating point value
⋊> ~ curl --data '{"jsonrpc":"2.0","id":43,"method":"account_list","params":[]}' -H 'content-type:application/json' http://<IP_ADDRESS>:5000/                                                          17:19:35
{"jsonrpc":"2.0","result":"[{\"address\":\"afb2f771f58513609765698f65d3f2f0224a956f\",\"type\":\"account\",\"url\":\"keystore://foo\"}]","id":43.0}

I think this is an issue of Gson, the JSON library used. I don't think they distinguish between integers and floats.
Is it an actual problem?

Looking into this a little bit, I don't think I can do much about it on my side. Since ID can be an Any, Gson will treat the integer as a floating point number.

hm - actually for me it is not yet a problem. Would still consider this as a bug and think someone in the future will stumble uppon this - I think this should be kept open as a bug.
Is there no way to not parse this value at all? Just return as given ;-)

The JSON returned back to the user is generated from a Map<String, Any>. Anything else will be difficult and would require major refactoring.
If it really is a problem, the user should use a string as the ID. Or a floating-point number.

If it really is a problem, the user should use a string as the ID. Or a floating-point number.

The user might not always be control over both ends

Thanks for addressing this issue!
just wondering:
val id = json.substringAfter("\"id\":").split(",".toRegex())[0].trim()

this would only work when the id is not the last element - right? Because otherwise there would be no comma following..

right..

PS: happy to review PR's for this project - so things like this do not end up on master.  So if you want this - open PRs with changes and tag me

Not sure if I'm gonna address it any further right now. At least it's better than it was.

PS: happy to review PR's for this project - so things like this do not end up on master. So if you want this - open PRs with changes and tag me

Will keep that in mind. Thanks


fix: random increase in size of Edit FAB

Fixes #1555
Cause
Popping of soft keyboard makes a layout resize
Changes:

change layout params to wrap content
apply fabsize = mini

Screenshots for the change:

@addiegupta @ShridharGoel  please review


Add : Light & Dark Mode

Currently there is no light and dark mode.

I want to add a toggle button for toggle between light and dark mode.
Please assign me under JWOC 2024, if approved.

It's already available, please take pull from master.

@Jagroop2001 why it's not visible in deployment in this https://64bcf6b874de0805368c53b9--timely-flan-114f94.netlify.app/ you provide.

I didn't updated yet because here everyday new changes are merged


Use standard path for ConEmu.xml

Placing xml file in the unusual location restricts or limits users from

pin cmder to TaskBar;
using "ConEmu here" feature;
using "DefTerm" feature.

Details are here: https://github.com/Maximus5/ConEmu/issues/277

Well, looks like you are awesome, thanks :)

This becomes a problem when building this project. Running the build scripts will delete the conemu-maximus5 folder before downloading a new version. Also, all the vendor files are ignored from .gitignore so the file will never be checked into git.
I guess this is something that would have to be worked around inside the build script.

That is not a problem. As you may see, file is copied if it is absent.
And if you want to preserve it on rebuild (?) just add copy back to config before deletion.

eec3fd5 - Backup and restore ConEmu.xml on ./build.ps1

One more drawback of "current" scheme. All settings are reset to defatuls when user unpack new cmder version. Proposed patch will preserve user changes made in ConEmu.xml on unpacking cmder.7z into existing installation.

Thanks, manually merged it into my fork.


Switch tile shaders to an ubershader

The number of shaders is being unwieldy. Per discussion with the Firefox graphics team I'm tentatively proposing that we switch to an ubershader that is then specialized on-the-fly into specific shaders via preprocessor magic when the shader graph is hot.
This should also improve performance by eliminating the need for temporary render targets in many cases. For example, the mask step can be entirely eliminated except in pathological cases (more nested clips than available samplers).

Does this work on WebGL?

It should work just fine on WebGL.

Here is the node pipeline I'm envisioning:
  Mask UV 0         Mask UV 1
      +                 +
      |                 |
+-----v-----+     +-----v-----+
|           | MIN |           |
|  Mask 0   +----->  Mask 1   +------+
|           |     |           |      |
+-----------+     +-----------+      v       +----------+     +-------------+
                                   Apply     |          |     |             |       GPU
                                   Mask +---->  Filter  +----->  Composite  +---->Blender
                                     ^       |          |     |             |
+-----------+     +-----------+      |       +----------+     +-------------+
|           |  ×  |           |      |
|  Color 0  +----->  Color 1  +------+
|           |     |           |
+-----^-----+     +-----^-----+
      |                 |
+-----+-----+           |
|           |           |
|  Radial   |           |
| Gradient  |           |
|           |           |
+-----^-----+           |
      |                 |
      +                 +
  Color UV 0       Color UV 1

So basically building the shader by putting building blocks together depending on the scene graph?

Depending on the clip/paint/filter/composite ops, yeah. But we only actually build a customized shader if a particular graph is used frequently (say, 100 or 1000 times). Otherwise we use a generic ubershader. This avoids compilation time unless it's really needed, and it also improves batching if a filter is only used a few times.

FWIW, WebRender is moving to a world where we need to know the shader source at build time. This is for Software-WebRender and offline shader optimization for startup on Mac and Android.
That's not to say doing runtime shader generation is necessarily a bad idea in this context, (Skia does it after all) it just makes some things harder.

@jrmuizel So what I was envisioning is a bit of a compromise approach in which all the shader functions are handwritten, but the "main" function that glues everything together via function calls is dynamically generated. I was thinking that this should be reasonably compatible with SWWR and Metal-like "shader library" approaches. As long as all the important logic is precompiled into bytecode or GPU machine code, dynamically generating the final main function shouldn't be a problem, right?

Yeah, that sounds reasonable. I don't know how well dynamically generating just part of it will work in practice, but none of the current motivations for ahead of time compilation directly apply to pathfinder anyways. The ubershader covers startup and there's not an immediate need for doing software pathfinder in a sw-wr style.


Prompts are being ignored

Describe the bug
Not sure if its a bug but after prompting not to use deprecated modules I'm still getting the same installs:
npm install
npm WARN deprecated<EMAIL_ADDRESS>This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm WARN deprecated<EMAIL_ADDRESS>Rimraf versions prior to v4 are no longer supported
npm WARN deprecated<EMAIL_ADDRESS>Glob versions prior to v9 are no longer supported
npm WARN deprecated<EMAIL_ADDRESS>Use @eslint/object-schema instead
Link to the Bolt URL that caused the error
https://bolt.new/~/sb1-8hhyez
Steps to reproduce
See Errors
Expected behavior
It should not use any deprecated install I would hope after prompting not too but I could be wrong  and I will still need to address each one after the install to correct them.
Screen Recording / Screenshot
No response
Platform
Browser name = Chrome
Full version = <IP_ADDRESS>
Major version = 129
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
performance.memory = {
  "totalJSHeapSize": 84748656,
  "usedJSHeapSize": 59961332,
  "jsHeapSizeLimit":<PHONE_NUMBER>
}
Username = Dwaynep
Chat ID = de2a19520344

Additional context
No response

@TakeOrdersai we upgraded to a newer AI model, so hopefully this is resolved. Unfortunately we cannot control whether the AI knows the latest status of every NPM dependency. We will be introducing the ability to lock specific files tho, so you could lock your package.json after you are satisfied with all package versions using that feature soon!


New version: vim.vim.nightly version 9.1.0260

Pull request has been created with WinGet Releaser v2 :rocket:
Microsoft Reviewers: Open in CodeFlow

Hi @chrisbra,
The package didn't pass a Defender or similar security scan. This might be a false positive and we can rescan tomorrow.
(Automated response - build 876.)

Automatic Validation ended with:

Installation failed with exit code -1978335187
2024-04-03 17:00:22.996 [FAIL] Installer failed security check. Url: https://github.com/vim/vim-win32-installer/releases/download/v9.1.0260/gvim_9.1.0260_x64.exe Result: 0x80004005
2024-04-03 19:30:25.053 [FAIL] Installer failed security check. Url: https://github.com/vim/vim-win32-installer/releases/download/v9.1.0260/gvim_9.1.0260_x86.exe Result: 0x80004005

(Automated response - build 876.)

@wingetbot run


HandshakeV10 packet Ignored

A handshakeV10 packet is ignored rarely  when creating a new connection using newConnection  method.
After connecting to MySQL Server, it seems that channelRead method in QueueHandler is called before adding handshake callback.
Environment
OS: Ubuntu 16.04
MySQL Server: mysql  Ver 14.14 Distrib 5.7.22, for Linux (x86_64) using  EditLine wrapper
Frameworks:
- MySQL 3.0.0-rc.2.2,
- Core 3.1.7
Log
[WARNING] [Async] [QueueHandler] Read triggered when input queue was empty, ignoring: handshakev10(MySQL.MySQLHandshakeV10(protocolVersion: 10, serverVersion: "5.7.22-0ubuntu<IP_ADDRESS>", connectionID: 8, authPluginData: 21 bytes, capabilities: CLIENT_NO_SCHEMA | CLIENT_PLUGIN_AUTH | CLIENT_CONNECT_ATTRS | CLIENT_CAN_HANDLE_EXPIRED_PASSWORDS | CLIENT_CONNECT_WITH_DB | CLIENT_PROTOCOL_41 | CLIENT_COMPRESS | CLIENT_FOUND_ROWS | CLIENT_LONG_FLAG | CLIENT_ODBC | CLIENT_IGNORE_SPACE | CLIENT_MULTI_STATEMENTS | CLIENT_INTERACTIVE | CLIENT_LOCAL_FILES | CLIENT_PS_MULTI_RESULTS | CLIENT_IGNORE_SIGPIPE | CLIENT_MULTI_RESULTS | CLIENT_SESSION_TRACK | CLIENT_RESERVED | CLIENT_PLUGIN_AUTH_LENENC_CLIENT_DATA | CLIENT_TRANSACTIONS | CLIENT_DEPRECATE_EOF | CLIENT_LONG_PASSWORD | CLIENT_SECURE_CONNECTION, characterSet: Optional(latin1_swedish_ci), statusFlags: Optional(2), authPluginName: Optional("mysql_native_password"))).

I have also noticed this happening. I will dig into this, thanks!

QueueHandler is no longer being used. See #176.


[aes] Wire up bus integrity alert

Signed-off-by: Michael Schaffner<EMAIL_ADDRESS>

With @vogelpi being out for a couple more days it should be OK to merge this as-is and we can then revisit the approach in a follow-up (unless this PR can wait 2 more weeks). Up to you @msfschaffner


Added Kubernetes

I'm hesitant to add promotional free chapters to this list, especially when users are asked for email addresses. I'll leave this PR open for a week or so in case others want to make a case for Kubernetes as an exception.


Add PB profile shape for discussion

This PR adds the ShEx shape used in PodBrowser for discussion.
Note: I think we want to go with SHACL but this is just to get us started with discussion.

Related to https://github.com/solid/webid-profile/issues/26

Closing in favor of https://github.com/solid/webid-profile/pull/84 (WIP)


Strange error in Copy-BcEnvironment

Describe the issue
We want to copy an environment using the Copy-BcEnvironment function. After removing the old Container or after copying to the new container we get the error message described in the script output section.
Scripts used
$bcAuthContent = New-BcAuthContext -clientID "clientID" -clientSecret "clientSecret" -tenantID "tenantID" -includeDeviceLogin
Copy-BcEnvironment -bcAuthContext $bcAuthContent -environment "destinationenvname" -sourceEnvironment "sourceEnvName"-environmentType Sandbox -force

Full output of scripts
Line |
  63 |  …      } while ($Operation.status -in "queued", "scheduled", "running")
     |                  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     | The property 'status' cannot be found on this object. Verify that the property exists.

Additional Content
We are using Version 6.0.3

When you say "After removing the old Container or after copying to the new container we get the error message described in the script output section." - what do you mean by Container?
Copy-BcEnvironment copies sandbox environments - has no connection to containers.

Works fine here:

Please include full output of your script instead of only the error.

Got it - it is a bug.
You can get around this by specifying -apiVersion "v2.19" when calling Copy-BcEnvironment.
I will make that the default.

Thanks a lot for your support. We will add -apiVersion "v2.19" temporary to our script
Kind regards


Extension Link broken in Readme

The Readme links to https://chrome.google.com/webstore/detail/atomos/hdoljekhdmbkopfbcdljnjmjkgfgoebi?hl=en to download the extension, but that link returns 404.

Hello @bearbytes, thank you for your interest in our devtool!
We are currently waiting for Atomos be approved by Chrome Web Store and we will update the README link when our extension is uploaded. In the meantime, the alternative installation method should work properly.

Hello @vlee022, please consider publishing to Edge's Extension Store as well.


Super call instead of explicit parent class init call

Looking at the thread dying issue #168, I found the following code:
https://github.com/PyMoDAQ/PyMoDAQ/blob/30f6f7877bfa8fc140841118288fe188c6077238/src/pymodaq/control_modules/daq_viewer.py#L101-L103
A skmple super().__init__() should be enough.
That will call the init of the first parent class.
If that class is well written, it will contain another super.__init__() (best with handling all excess kwargs), which will resolve to the second parents init.
That continues until all parents (direct and the parents of parents) have been called.
If any parent class is QObject, that will be initialized as well.
See also:

general regarding super https://rhettinger.wordpress.com/2011/05/26/super-considered-super/
for the method resolution order: https://www.python.org/download/releases/2.3/mro/

Thanks for pointing this out however I'm well aware of that but when using super and multiple inheritance as I do here lead to various issues. At the end I thought it would be easier/clearer to init each parent separately.

I just tested it, and it worked, but that is obviously not a comprehensive test. I understand your reluctance.
Your current code initializes "QObject" twice, by the way, as ControlModul also initializes "QObject".

For the time being I think we will stick to not use the super method here, but we will move away the second QObject initialization. I did it in https://github.com/PyMoDAQ/PyMoDAQ/commit/862d0ed12d7a591b76c2323c59af855ad480ec87
Thx


Replaced GRPC dependency with Protobuf

Seems that we don't need GRPC dependency but only protobuf in Android project

Let me confirm why we added protobuf from grpc first


autoIncrement: true stopped working

[X] Bug report

Current behavior
Old migrations and new ones do not output auto increment anymore to any column
Expected behavior
SQL output should add auto increment to column
Minimal reproduction of the problem with instructions
Sample code:
exports.up = async function(db) {
  return await db.createTable('user_readings', {
    id: {
      type: 'int',
      primary: true,
      autoIncrement: true,
    },
  });
};

Dry run output:
$ db-migrate up -e $NODE_ENV --dry-run
[INFO] dry run
show server_version_num;
SHOW search_path;
SET search_path TO "$user","public";
SELECT table_name FROM information_schema.tables WHERE table_name = 'migrations' AND table_schema = 'public';
SELECT * FROM "migrations" ORDER BY run_on DESC, name DESC;
BEGIN;;
CREATE TABLE  "user_readings" ("id" INTEGER  ) ;
INSERT INTO "migrations" ("name", "run_on") VALUES ($1, $2) [ [ '/20200428080719-createUserReadingsTable',
    2020-04-28T09:39:29.577Z ] ]
[INFO] Processed migration<PHONE_NUMBER>0719-createUserReadingsTable
COMMIT;;
[INFO] Done
   Done in 0.53s.

What is the motivation / use case for changing the behavior?
Am I missing anything here? It worked like charm before and after I update packages it's not working anymore.
Environment
Deps:
success Saved lockfile.
success Saved 8 new dependencies.
info Direct dependencies
└─<EMAIL_ADDRESS>info All dependencies
├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>└─<EMAIL_ADDRESS>
success Saved lockfile.                                                                                success Saved 3 new dependencies.
info Direct dependencies                                                                                └─<EMAIL_ADDRESS>info All dependencies
├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>└─<EMAIL_ADDRESS>
Additional information:

Node version: v10.15.3
Platform:  macOS Catalina

I also tried the v1.0.0-beta.7 but it shows same results

your migrations are wrong (there is no such option as primary, only primaryKey) not db-migrate, please read the documentation more carefully before opening an issue like this and make sure you're not doing it wrong:
https://db-migrate.readthedocs.io/en/latest/API/SQL/#createtabletablename-columnspec-callback

Sorry about it. Thanks.


Player collision disabling doesn't work.

What version of ViaVersion are you using? Type /ver viaversion
0.7.4
What version of Spigot are you using? Type /ver
Paperspigot 1.8.8
What plugins are you using? Type /plugins
n/a
Are you using any additional software like BungeeCord? If so, what software and version? (Please list your plugins as well)
LilyPad
How does this error happen? login? Using an item?
Just doesn't work, you can push players.
Is there an error in the console? Use pastebin.com. Is there a kick message?

Is autoteam enabled in the config?
autoteam: true

Yep
`# Do you want us to prevent collision?
prevent-collision: true
If the above is true, should we automatically team players until you do?
auto-team: true`

What plugins do you use?

@iLemon1 Can you maybe try if it happens without LilyPad?

Can't remove it, sorry.

Ok, I'll try to reproduce it tomorrow

I can also confirm this, player collision is still an issue with LilyPad.

@MylesIsCool found out that there is a mistake in the LilyPad packets, https://github.com/LilyPad/GoLilyPad/blob/master/packet/minecraft/v19/clientTeams.go#L116

Update your lilypad

can't get player collosion to work neither :/, would like to get it disabled