jps: Watch pesktop.org

jps requests the watch of the watch_keyword pesktop\.org. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

pesktop\.org has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Mast in Charcoal HQ


handling EXIT, :normal messages in handle_info

According to
https://stackoverflow.com/questions/39430574/unsupervised-gen-server-doesnt-call-terminate-when-it-receives-exit-signal,
there's an edge-case where the terminate callback of genservers might
get bypassed if the exit signal is sent first to the supervisor process,
in which case we have to catch the message and signal termination
ourselves.
Closes #7

LGTM 👍

I think that to test this correctly we'd probably need to simulate a supervision tree in the tests. I can look into it some other time. For now, I've added a simple hack test that sends {:EXIT, ...} directly to the running Firefighter GenServer.

For now, I've added a simple hack test that sends {:EXIT, ...}

Clever 💯


Add wrappers for external functions.

This change is

crates/starknet/src/plugin.rs line 66 at r1 (raw file):
Previously, yuvalsw wrote…
unreachable!()

Its is a moudle, other items are reachable.


Nether brick wall recipe conflicts with fiery nether brick wall recipe

This should be resolved. Perhaps port over the recipes for nether fences from 1.14 to 1.12, and then use the old recipe for nether brick walls?

This will be fixed in upcoming release.


[REVIEW] shubhimainalli

GitHub Profile Link
https://github.com/shubhimainalli

Really like your profile maybe one addition at the top you have connect with me on twitter and at the bottom also. You can consider if you want to remove it on one place due its duplicate information. Otherwise yeah home made food is the best in my opinion too

Great point @schmelto, Also try to pin some of the top projects/Repo.

@schmelto that's great point ill work on it.

@Pradumnasaraf thanks for suggesting that to pin the top projects.


deploying openebs-operator with default namespace at the end of the …

…test
Signed-off-by: swarna<EMAIL_ADDRESS>
What this PR does / why we need it:
In few playbooks deploying openebs-operator with non default namespace and deleting it at the end of the test.
In ci minium requirement is openebs-operator should be running as part this deploying operator with default name space after cleanup.
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
Special notes for your reviewer:
@ksatchit Please review this PR.

We might be better served to install the openebs operator in a dedicated namespace before beginning the CI run. so that we don't have to perform such steps as install it during cleanup etc.., Closing this PR in lieu of this.


Pull create-snowpack-app into this repo 🎉

Changes
Testing had historically been different as 2 different repos had been dependent on each other (snowpack for the templates & plugins, and the templates relied on snowpack to run). This brings everything into one monorepo, allowing:

Better testing (changes to plugins are tested against snowpack, and vice-versa)
Easier contribution (now it’s all just one repo)
Lighter footprint (Now there’s only one node_modules folder thanks to Yarn workspaces, as opposed to dozens).

@FredKSchott I think in this instance we should probably merge without squashing because it can import the Git history from create-snowpack-app, along with contributions. WDYT?
Testing
Tests should pass!

Yea lets definitely squash. Fantastic that tests are passing on mac, if we can get them running on Windows then this LGTM to merge!

/giphy SHIP IT


Upload to Blob example raises azure.core.exceptions.ServiceResponseError ('connection aborted.', timeout('...'))

Context

OS and version used: 2020-02-13-raspbian-buster-lite (Linux)
Python version: 3.7.3
pip version: 20.0.2
list of installed packages:
azure-core            1.8.2
azure-iot-device      2.3.0
azure-storage-blob    12.5.0
cloned repo: upload_to_blob.py Git SHA 07b0f6ba3bbc005758d3b7d0a3c0598196f22a4d

Description of the issue
Using the upload_to_blob.py script (async example)
Upload to blob fails over cellular connection with a file with size 791345 bytes (file is a compressed archive .tar.gz). A Service Exception is raised (see attached txt file)
Same file successfully uploads over Wifi
A smaller file (i.e. size 239641 bytes) successfully uploads over cellular connection
If there is a timeout regarding the Azure blob HTTPS API is there a way to set it using the python package?
Code sample exhibiting the issue
See attached .zip
upload_to_blob.zip
Console log of the issue
Console.txt
AB#8718086

Hi @dsilva-vd , thanks for the question, we'll look into this and get back to you shortly!

We are attempting to reproduce the issue now. Are there any additional details you can share regarding your cellular connection to assist us in the matter?

We are attempting to reproduce the issue now. Are there any additional details you can share regarding your cellular connection to assist us in the matter?

Hi Carter,
The only thing I can mention is the cellular connection was a LTE CAT1
modem with a UART connection to a host processor. The UART speed was set to
115200 kbps as this was the default speed.
As a test I increased the UART speed to 460800 and did not encounter this
issue. If the issue is related to an azure blob upload timeout can that
timeout be changed via an API?
Thanks
On Fri, Jan 15, 2021 at 11:41 AM Carter Tinney<EMAIL_ADDRESS>wrote:

We are attempting to reproduce the issue now. Are there any additional
details you can share regarding your cellular connection to assist us in
the matter?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Azure/azure-iot-sdk-python/issues/702#issuecomment-761114823,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AORKBXZXTKQNFWSR2TZA4NDS2CD4RANCNFSM4TIDQXYQ
.

Hi Carter,
The only thing I can mention is the cellular connection was a LTE CAT1
modem with a UART connection to a host processor. The UART speed was set to
115200 kbps as this was the default speed.
As a test I increased the UART speed to 460800 and did not encounter this
issue. If the issue is related to an azure blob upload timeout can that
timeout be changed via an API?
Thanks
On Fri, Jan 15, 2021 at 11:41 AM Carter Tinney<EMAIL_ADDRESS>wrote:

We are attempting to reproduce the issue now. Are there any additional
details you can share regarding your cellular connection to assist us in
the matter?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Azure/azure-iot-sdk-python/issues/702#issuecomment-761114823,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AORKBXZXTKQNFWSR2TZA4NDS2CD4RANCNFSM4TIDQXYQ
.

@cartertinney I will go ahead and investigate this and try and repo

@dsilva-vd I am not able to duplicate this issue on cell connection. As noted this is most likely caused by an upload timeout in azure storage. I am going to close this issue for now. If you are still experiencing this, and it is a priority, we can forward it over to the IoT Hub and Azure Storage teams to review.


Yojson.Json_error is raised.

Hi,
When I try to use yojson, I had a trouble when I got  json via socket. like following programs.
When I send a json to a local server twice,  Fatal error: exception Yojson.Json_error raised.
Nothing raised when I send a json only once.
Is it a bug or did I misunderstood how to use it ?
server.ml
let parse json =
  match json with
  | `List l -> l
  | _ -> assert false

let () =
  let addr = Unix.ADDR_INET (Unix.inet_addr_of_string "<IP_ADDRESS>", 3300) in
  Unix.establish_server (fun ic oc ->
      let f () =
        let json = Yojson.Safe.from_channel ic in
        parse json
        |> List.length
        |> print_int in
      f (); f ()
    ) addr

client.ml
let () =
  let addr = Unix.ADDR_INET (Unix.inet_addr_of_string "<IP_ADDRESS>", 3300) in
  let ic, oc = Unix.open_connection addr in
  let json = Array.init 100 (fun i -> `Int i)
             |> Array.to_list |> (fun l -> `List l) in
  Yojson.Safe.to_channel oc json;
  flush oc;
  Yojson.Safe.to_channel oc json;
  flush oc

execution log
  [~/ocaml/json] ocamlfind query yojson -format %v
1.2.0

 [~/ocaml/json] ./server &
[4] 48638
[~/ocaml/json] ./clinet
[~/ocaml/json] Fatal error: exception Yojson.Json_error("Line 1, bytes 292-324:\nJunk after end of JSON value: '[0,1,2,3,4,5,6,7,8,9,10,11,12,13,'")
Raised at file "common.ml", line 5, characters 25-39
Called from file "read.mll", line 1105, characters 6-21
Called from file "read.mll", line 1122, characters 6-26
Called from file "server.ml", line 10, characters 19-46
Called from file "server.ml", line 14, characters 6-10
Called from file "unix.ml", line 1081, characters 12-37
Called from file "server.ml", line 8, characters 2-198

Sorry for the late reply.
from_channel can only be used to read from a channel that provides a single value.
In order to read multiple value from a channel, use stream_from_channel, which gives you a stream from which you can pull json values.


Unuseful container that started failure should be deleted automaticly

Operations:
mabin@mabin-PC:~/work/osc/pr/docker$ sudo docker run -idt ubuntu:14.04 /bin/bas
93d414b89fb38f1cd0779fd7a558da61479db876b4e758613119eeb8e6e09fed
FATA[0000] Error response from daemon: Cannot start container 93d414b89fb38f1cd0779fd7a558da61479db876b4e758613119eeb8e6e09fed: [8] System error: exec: "/bin/bas": stat /bin/bas: no such file or directory
mabin@mabin-PC:~/work/osc/pr/docker$ sudo docker ps -a
CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS              PORTS               NAMES
93d414b89fb3        ubuntu:14.04        "/bin/bas"          5 seconds ago                                               silly_almeida
mabin@mabin-PC:~/work/osc/pr/docker$
When i ran a container with wrong or non-existent command, daemon reported FATA error "Cannot start container", but it can be found by "docker ps" command. In my opinion,maybe the failed container should be deleted automaticly because it's unuseful.

Personally I would not like this feature. There have been several times in the past where a container has failed to start, and the ability to run docker inspect on the container has helped me figure out why.

OK,but in my opinion, there are some FATA and ERROR logs be recorded to show users why when we useed "docker run" to start a container, this fix solves the failure of "cli.call("POST", "/containers/"+createResponse.ID+"/start", nil, nil)".And then, althought the container is started failure,the resources of container are created success in /var/lib/docker/ , if they are unuseful and redundant,we should delete it automaticly.

ping @duglin @LK4D4 Could you help me to check this?Thanks :-)

I'm not sure I agree wit this PR.  W/o the -rm option on the run command I wouldn't expect my container to be automatically deleted.  It might make sense if Docker failed to create the basic infrastructure of the container - like it couldn't built-up the layers of the FS, etc...   but for the case you're mentioning (bad cmd), I think it might make sense to keep it around because to me once Docker is done setting up the container and it tries to start the command we're (sort of) in the user-controlled space and at that point it could fail for a lot of reasons, so they may need the container around to help debug.

Thanks @MabinGo, but we're going to go with @phemmer and @duglin opinion there: current behavior is the correct one.


Clean up interface for building + releasing

Expected Behavior
If automation (or a user) wants to create a TaskRun or PipelineRun to release the tekton pipelines project:

The Task should be able to use images for each step that have all the dependencies they need
It should be possible to auth for pushing images to registries to fall back in the following order:
a. If the user provided a service account to the run, use that
b. Otherwise use the default account in the namespace (creds automatically provided to the executing container)

Actual Behavior
In #528 and #529 we had to add some significant hacks to make ko work in a Task:

We had to have a step to install ko and copy the binary around so we could use it in later steps
We had to have a step to copy the go binary + supporting libs out of a golang image so we could use go in the gcloud image
We call gcloud auth configure-docker to setup docker auth which 1) only works in GCP based projects and 2) only works with default service credentials (not user supplied service accounts)

Additional Info

The solution here doesn't need to use ko - if we decide we want to use something else instead, and/or if we decided we want to split up publishing the images from generating the k8s config
https://github.com/google/go-containerregistry/issues/383 is the issue for creating an image for ko upstream, if that issue is solved it could close this one :) (one potential solution)
https://github.com/tektoncd/pipeline/blob/master/docs/auth.md#basic-authentication-docker might work for us however it looks like it requires a user to provide their username and password :(
Maybe we can add some kind of credential helper to the ko image (https://github.com/google/go-containerregistry/issues/383) which knows how to handle credentials via some well defined interface

https://github.com/google/go-containerregistry/blob/871d0d9dba6c1a9aa6aed154d5a936ebf7607a1d/pkg/authn/k8schain/k8schain.go#L108
https://github.com/docker/docker-credential-helpers

@bobcatfish what is the status of this issue ? :angel:

@afrittoli @bobcatfish are you ok closing this issue ? (and if there is anything that is still needed from it, creating issues on tektoncd/plumbing instead ?

@bobcatfish what is the status of this issue ? 👼

i think we're still in the same state but it also seems like it hasnt been important enough for anyone to get to


Fix issue where pvc range produced multiple volume keys

Resolves #135
Confirmed the following via tests:

Inclusion of storage.existingVolumeClaim does not create a volume key in the deployment
Omitting storage.existingVolumeClaim and creating either/or/both of storage.data / storage.attachments creates a single volume key with children for each

(dont judge my test keys lol as i had to spoof the volumeClaim names to avoid errors with includes in my test)

@guerzon how are you feeling about this one

Thanks @paimonsoror for the PR.


zsh / oh-my-zsh - no scroll

If i start demo with zsh instead of bash and have oh-my-zsh installed then the scroll will not work in xterm.js
I am not sure if this is an issue with xterm.js or oh-my-zsh
The command that causes scroll to stop working is this command: echoti smkx that is located in .oh-my-zsh/lib/key-bindings.zsh
One can also start xterm.js without oh-my-zsh and type that command into terminal and it will stop scrolling.

Thanks for reporting @wallverb. I do not have access to zsh right now, so I am not able to test this out.
Could you please take a look at your console in the developer tools of your browser and provide us with any errors/logs that might appear when attempting to scroll when in zsh with oh-my-zsh?

@parisk - when zsh/oh-my-zsh is executing that echoti smkx command then the following data is being sent to   Terminal.prototype.write = function(data) :
>
xterm.js:1467

xterm.js:1467 ]2;echoti smkx
xterm.js:1467 ]1;echoti=%

which seems like that = char is causing this:
 // ESC = Application Keypad (DECPAM).
              case '=':
                this.log('Serial port requested application keypad.');
                this.applicationKeypad = true;
                this.state = normal;
                break;

and then  this.applicationKeypad = true; is causing return in scroll code:
      on(el, wheelEvent, function(ev) {
        if (self.mouseEvents) return;
        if (self.applicationKeypad) return;

@parisk, any movement on fixing this? Really appreciate the work!

@richarddavenport unfortunately I didn't have time to deal with this and I do not project to be able to do so by the end of the month.
It would be extremely helpful if we could get an external contribution on this and I can definitely help anyone out with figuring out the internals of xterm.js.

@parisk I'd love to help! Is there any documentation anywhere, or could you help me get going with debugging? Is there an editor or IDE that works best? VS Code/Webstorm/Chrome Dev Tools? Thanks!

@richarddavenport any editor works well. All the code is in ./src/xterm.js and instructions to run the demo are here.

@Tyriar is right. Any editor supporting JavaScript works, so feel free to choose the one that suits you better.
Personal opinion though would be choosing an editor or IDE that uses xterm.js itself though, in order to dogfood it as well (use xterm.js when developing xterm.js). The two solutions that I am aware of right now are:

SourceLair that works completely in the browser; just visit https://lair.io/sourcelair/xterm and follow the instructions
Visual Studio Code, just download it, clone the repo, run npm install and you are all set

Debugging with Chrome/Firefox DevTools is the best way to go IMO.
Considering the documentation, there is no public website at the moment but you should expect it within the week. Till that time just run npm run build:docs in your terminal and then you will be able to browse the API reference in HTML format, inside the docs directory.
Feel free to ask for more help in case the above do not suffice.

@richarddavenport I published a preview version of the docs website, which contains the API reference. Most public methods are documented.
You can take a look at http://docs.xtermjs.org/. Hope it helps 😊 .

Wow! That's pretty awesome! @wallverb is right about the echoti smkx command in oh my zsh. That command is putting the terminal in Application Mode, which (I'm guessing here) is related to the applicationKeypad property. Does that sound right? I have no idea what application mode is, but it sounds important. Line 1144, if commented out, everything works, but I'm unsure of the consequences or what that line is there for. Do you know what that is for?

Yes I'm a bit hesitant to touch it as I don't know what it does either.
This reference doc we use mentioned it here:

The application keypad transmits the following escape sequences depend-
ing on the mode specified via the DECKPNM and DECKPAM escape sequences.
Use the NumLock key to override the application mode.

The code also mentions:
              // ESC = Application Keypad (DECPAM).
              case '=':
                this.log('Serial port requested application keypad.');
                this.applicationKeypad = true;
                this.state = normal;
                break;

              // ESC > Normal Keypad (DECPNM).
              case '>':
                this.log('Switching back to normal keypad.');
                this.applicationKeypad = false;
                this.state = normal;
                break;

Looking into what DECPAM and DECPNM will likely lead us to an answer.

Xterm.js scrolling with oh my zsh now works, with this branch

Hi. Found this thread from the related bug on Oh My Zsh.

Looking into what DECPAM and DECPNM will likely lead us to an answer. Also if there's a difference with DECKPAM and DECKPNM.

I think DECPAM and DECPNM are just typos for DECKPAM and DECKPNM. The mnemonics are "DEC KeyPad Application Mode" and "DEC KeyPad Normal Mode".
Application keypad modes change what character sequences the cursor keypad and/or numeric keypad keys send in response to key presses. There are two (or more) distinct keypad modes which can be set to either "application" or "normal": the numeric keypad and the cursor keypad. The applicationKeypad and applicationCursor properties modify the sequences sent by some keys, which seems appropriate.
It seems to me there may be a bug with the Home and End keys, though. Their behavior is modified by the applicationKeypad property. But xterm considers Home and End to be cursor keys, controlled by DECCKM instead of DECKPAM/DECKPNM. (See the "PC-Style Function Keys" section in that xterm reference document.) I think that means they should be controlled by applicationCursor instead of applicationKeypad.
Regardless, it's surprising to me that the keypad mode would affect mouse scroll wheel behavior. (That's the scrolling that OP is talking, about, right?) Maybe the fix is as simple as removing that if (self.applicationKeypad) return; check from the mouse scroll wheel handler.

I do not have access to zsh right now, so I am not able to test this out.

You can test this behavior under bash or other shells by doing tput smkx. That's equivalent to zsh's echoti. But be aware that under most terminfo definitions, smkx sends the sequences for both application cursor keypad and application numeric keypad modes, so you're not testing them independently if you do it that way. To test them independently (e.g. if you wanted to check which mode was controlling the Home/End behavior), you'd need to echo those escape sequences separately. (I don't remember how to do so off the top of my head.)

I believe this is the same root cause as why scrolling doesn't work in vim which also sets DECKPAM.

Following xterm's mouse spec the mouse actions dont't get modified by DECKPAM or DECKPNM. Does anyone know why we have the if (self.applicationKeypad) return; in the mouse scroll handler at all?

@jerch yeah I'm beginning to think that too, there's a bunch of reading I want to do in #194 to finally fix these sorts of issues.

I think I have some more input to provide here.

Maybe the fix is as simple as removing that if (self.applicationKeypad) return; check from the mouse scroll wheel handler.
@apjanke this won't work and should not work actually. This particular event handler is there to allow scrolling in simple text mode applications like bash, which have applicationKeypad set to false (btw. sounds quite helpful to document this better).

In addition, even if we removed this it would result in a term.scrollDisp(1) call, which would do nothing  when an app like vim is open, where term.ydisp and term.ybase are both 0.
This should be most probably handled in the previous event handler.
@richarddavenport did this work without any change on xterm.js?

@parisk Yes, it is working without any change to xterm.js.

Maybe the fix is as simple as removing that if (self.applicationKeypad) return; check from the mouse scroll wheel handler.
@apjanke this won't work and should not work actually. This particular event handler is there to allow scrolling in simple text mode applications like bash, which have applicationKeypad set to false (btw. sounds quite helpful to document this better).

Shouldn't this behavior be just a function of the mouse tracking mode, Alternate Screen, and Alternate Scroll modes, and not the numeric/cursor Application Keypad modes? OP is using zsh, which is more like bash than like vim: it's a simple text application that uses the main screen and which does not provide its own scrolling support, so it relies on the terminal to do scrolling. But some of those simple text programs, especially zsh, might still enable Application Keypad mode so they can do portable key binding using terminfo definitions, which typically only include the application mode character sequences.

@parisk I second that - why should a keyboard mode settings interfere at all with the mouse behavior? The official xterm spec does not mention any of this, therefore implementing an xterm compatible model should not have such a limitation. Do I miss something here?

What's the easiest "work-around" available before this is addressed a more verbose manner?

@ksnyde this is probably the easiest: https://github.com/Microsoft/vscode/issues/7817#issuecomment-229069151. I haven't tried it personally though.

this is probably the easiest: Microsoft/vscode#7817 (comment). I haven't tried it personally though.

Unfortunately, that will break other key bindings which depend on zle_line_init. You may or may not use those key bindings, so it may or may not matter to you.
There's an open OMZ PR I put in to drop the zle_line_init/[sr]mkx dependency and stick with normal keypad mode, and which seems likely to be accepted. If you run that locally, or upvote it so it gets merged in to the OMZ mainline, you can use that as a workaround that avoids this scrolling issue (by avoiding application keypad mode altogether) and keeps all OMZ key bindings working.
That is, if you are using Oh My Zsh. If you are using one of the Linux distributions which configure zle_line_init to use [sr]mkx in their system config files, you'll need to redefine zle_line_init in your own ~/.zshrc config file as a do-nothing.
function zle-line-linit() {
  # NOP
}

(This may still break other key bindings that depend on application keypad mode.)

For those apps there is no terminal scrolling. You can test this yourself by running vim or emacs in xterm - you can't scroll back to previous terminal content.

Minor difference, but this is not quite true: in xterm, at least some versions of it, if you run vim, it switches to the alternate screen, but you can still scroll back and see earlier contents of the buffer (as long as the buffer has more than a screen of content), as long as you have not enabled mouse event handling in vim. If you :set mouse=a in vim, then it will receive mouse events, and the terminal will not scroll in response to them. Most users probably don't see the former behavior because they have their .vimrc set up to automatically enable mouse event handling. I think this suggests that the terminal-level widget scrolling behavior is controlled by mouse event handling, not by the alternate screen mode.

Thanks for clarification @apjanke - to fully mimick xterm's behavior the handling of the scroll buffer and DECSET has to be reviewed first IMO.

@Tyriar , please teach me why 1b886a44 is needed.
you just want to hide a vertical scrollbar?
i observed xterm's behavior on linux for a little while, i thought that 1b886a44 should be dropped.

@ayapi that commit is being reverted in https://github.com/sourcelair/xterm.js/pull/287
I don't think it will help this problem though, the scroll bar will still be disabled in oh my zsh.

FWIW, I think this is a case of Xterm.js deviating from normal xterm behavior, and is not Oh My Zsh's problem, and this bug should be closed. If OMZ does provide a compatibility shim for it, it should be confined to a plugin.

@apjanke so you agree with the PR I just put up? #289

Yes, I agree with https://github.com/sourcelair/xterm.js/pull/289. "Application mode" as discussed here is just a keypad mode switch; mouse behavior should be unaffected by it, so wheel events should be allowed.


[QUESTION] How to remember window place?

How to remember windows place when I reopen scrcpy?
OS: Windows 10
Thank you very much!

Currently, you can't, there is no state saved.
However, you can explicitly position your window: https://github.com/Genymobile/scrcpy#position-and-size


docs: improves the README

This PR aims to create a more welcoming README to the Sigstore community.
Let me know what you think 😄

I don't know why DCO is failing, the commit is signed 🤔

looks like your git config is not correct
Summary
Commit sha: [2956cd9](https://github.com/sigstore/community/pull/327/commits/2956cd9ae44672fdf1b91386788c1c1034e6219f), Author: Andres, Committer: Andres<EMAIL_ADDRESS>is not a valid email address.

@cpanato yeah, I see that on the DCO message, but if you check, the commit message has a valid email address now as shown here:
https://github.com/sigstore/community/pull/327/commits/2956cd9ae44672fdf1b91386788c1c1034e6219f
I'll try closing this PR and reopening a new one

@cpanato I had to open a new PR from a  fresh branch, here it is #330


Metaquantome:expand error when running taxa

Hello,
I was testing metaquantome :expand taxonomy analysis and it failed giving this error:
ERROR:
Fatal error: Exit code 2 ()
usage: metaquantome [-h] {db,expand,filter,stat,viz} ...
metaquantome: error: unrecognized arguments: @

this was fixed in f0993019d720746ff075ce5aaf17e3887a4d7939 and will be updated in galaxy tool version 0.99.5


Add s3-insecure for S3 backend

#655

The linter test failed - looks like you have trailing whitespace on those lines. You can fix it by either installing and running the pre-commit hooks (pre-commit install; pre-commit run -a) or by manually trimming it off.

Thanks!


English documentation is missing

Hello
When running NVDA in English, in the add-on manager, one cannot access the add-on's documentation.
On the contrary, the add-on's translated documentation is available through add-on manager (e.g. Franch in my case).
The English documentation exists in any case since it is on the GitHub page.
Could you please add it as it is done automatically for the other add-ons based on the add-on template?
Thanks.

I think it might be a bug on the pipeline, since it generated the contributing.html file correctly. I'll take a look tonight on the pipeline and on the addon template to fix it.

Hello!
It seems the bug was on the pipeline. The addon was compiled by Github actions on a Linux system, and since the case of the file on disk and the code were different the pipeline couldn't find the file. I fixed the pipeline and reuploaded the addon to the release manually this time to fix it.
Thanks for the report!

The issue is fixed in version 1.4.1. Closing.
Thanks.


Run conformance jobs only on cloudprovider changes

What this PR does / why we need it:
This PR skips conformance jobs to run on every PR and to run only on cloudprovider changes.
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #699
Special notes for your reviewer:
Release note:

LGTM

/test cloud-provider-openstack-acceptance-test-lb-octavia
/lgtm

/lgtm

/assign @hogepodge @lingxiankong

/lgtm
Thanks for proposing this PR!

@ramineni should we add Gopkg.toml and Gopkg.lock file also?
@wangxiyuan after above PR is merged, conformance test will run rarely, could you point me to the periodic job? as in this job only we are uploading docker images of all plugin

/test cloud-provider-openstack-acceptance-test-lb-octavia

/assign @dims

/test cloud-provider-openstack-acceptance-test-lb-octavia

@ramineni should we add Gopkg.toml and Gopkg.lock file also?
I guess shouldn't affect the e2e conformance as it runs on k8s master everytime? And any changes to Gopkg.toml , make build itself should fail if any compatibility issues which can be fixed . Do you have any scenario in mind where it would be affected ?

/test cloud-provider-openstack-acceptance-test-lb-octavia

/test cloud-provider-openstack-acceptance-test-lb-octavia

/test cloud-provider-openstack-acceptance-test-lb-octavia

/test cloud-provider-openstack-acceptance-test-lb-octavia

/approve


Rename mapConcat to concatMapIterable

cc @fchaillou @allantl
I'm still wondering about mapConcat alias for consistency with Akka Streams but we should follow rx as the first priority

It looks good to me, and after sleeping on it a few days, I think it makes more sense to keep consistency with the rest of the Monix.


Error in running C++/ Linux

Dear,
I am trying to use Moordyn package using C++ on my Ubuntu machine.
When I try to run an example file I by typing the commad "g++ file.cpp"
I get this:
In file included from /usr/local/include/moordyn/IO.hpp:37,
                 from /usr/local/include/moordyn/MoorDyn2.hpp:38,
                 from try.cpp:2:
/usr/local/include/moordyn/Misc.hpp:171:16: error: ‘Vector’ in namespace ‘Eigen’ does not name a template type; did you mean ‘VectorXi’?
  171 |         Eigen::Vector<real, 7> toVec7() const
      |                ^~~~~~
      |                VectorXi
In file included from /usr/local/include/moordyn/Time.hpp:40,
                 from /usr/local/include/moordyn/MoorDyn2.hpp:41,
                 from try.cpp:2:
/usr/local/include/moordyn/Line.hpp: In member function ‘void moordyn::Line::getFASTtens(float*, float*, float*, float*) const’:
/usr/local/include/moordyn/Line.hpp:476:52: error: ‘seqN’ is not a member of ‘Eigen’
  476 |                 *FairHTen = (float)(Fnet[N](Eigen::seqN(0, 2)).norm());
      |                                                    ^~~~
/usr/local/include/moordyn/Line.hpp:478:52: error: ‘seqN’ is not a member of ‘Eigen’
  478 |                 *AnchHTen = (float)(Fnet[0](Eigen::seqN(0, 2)).norm());
      |                                                    ^~~~
In file included from /usr/local/include/moordyn/Time.hpp:43,
                 from /usr/local/include/moordyn/MoorDyn2.hpp:41,
                 from try.cpp:2:
/usr/local/include/moordyn/Body.hpp: In member function ‘moordyn::vec moordyn::Body::getVelocity() const’:
/usr/local/include/moordyn/Body.hpp:310:59: error: ‘seqN’ is not a member of ‘Eigen’
  310 |         inline vec getVelocity() const { return v6(Eigen::seqN(0, 3)); }
      |                                                           ^~~~
/usr/local/include/moordyn/Body.hpp: In member function ‘moordyn::vec moordyn::Body::getAngularVelocity() const’:
/usr/local/include/moordyn/Body.hpp:315:66: error: ‘seqN’ is not a member of ‘Eigen’
  315 |         inline vec getAngularVelocity() const { return v6(Eigen::seqN(3, 3)); }
      |                                                                  ^~~~
In file included from /usr/include/Eigen/Core:22,
                 from /usr/include/Eigen/Dense:1,
                 from /usr/include/Misc.hpp:37,
                 from /usr/include/Waves/SpectrumKin.hpp:3,
                 from /usr/local/include/moordyn/Waves.hpp:43,
                 from /usr/local/include/moordyn/MoorDyn2.hpp:42,
                 from try.cpp:2:
/usr/include/Eigen/src/Core/util/ConfigureVectorization.h: At global scope:
/usr/include/Eigen/src/Core/util/ConfigureVectorization.h:461:27: error: redefinition of ‘const char* Eigen::SimdInstructionSetsInUse()’
  461 | inline static const char *SimdInstructionSetsInUse(void) {
      |                           ^~~~~~~~~~~~~~~~~~~~~~~~
In file included from /usr/local/include/Eigen/Dense:1,
                 from /usr/local/include/moordyn/Misc.hpp:37,
                 from /usr/local/include/moordyn/IO.hpp:37,
                 from /usr/local/include/moordyn/MoorDyn2.hpp:38,
                 from try.cpp:2:

Could someone please help?

It seems like the version of Eigen installed on your system is older than what MoorDyn needs. To solve this you could either install the latest version of Eigen on your system (I believe any 3.4.xx version should work), or what will also probably work is compiling MoorDyn with the cmake flag "-DEXTERNAL_EIGEN=OFF", which will use the copy of Eigen in MoorDyn. If you download the eigen source http://eigen.tuxfamily.org/index.php?title=Main_Page, it should have instructions for the straightforward install procedure (nothing needs to be compiled as it's a header only library).

He is not replying, so I assume everything is working fine


go/pup: init at 0.3.9

(also required go/color: init at 9aae6aa)
First time I package a Go package.

What's the date field for?
Is there a better way to do what I did in renameImports?
Am I meant to invoke this as goPackages.pup.bin?

cc @jb55

Throwing in go-mtpfs for good measure.
Still don't know what the date field is for.

About date, there's the source code for buildFromGitHub. Should be quite clear.
About .bin, yes.

fixed as requested.

@lethalman, anything else before this can get merged?


discoverSomeServices uses discoverAll (slow), and getGattServicesForUuidAsync does not accept valid guids

When telling this binding to discover a specific list of service uuids, it instead discovers all, and then filters the results. This is slow if you are working with a device with many services.
I attempted to fix this, but no matter what I throw at getGattServicesForUuidAsync, it always returns "Bad arguments: No suitable overload found".

It doesnt appear that any methods in bindings JS call any of the C methods that accept a guid as an argument, so it is entirely possible that passing a guid to a C method is just broken.

Figured out what was going on with the uuids. See https://github.com/jasongin/noble-uwp/pull/86

Closing for now as there is a path forward, or users can use the code in the PR

I merged the PR. Thanks @tony-gutierrez !


fix packit leftovers

Resolves Issues #2 #3 #4 #5.

I pushed changes but I haven't changed the conf.yaml yet. As you suggest I leave it for now and edit when I will need Github app flags there.


Fix handling of multi-line function declarations

Resolves #684
The cause of this problem is the method of checking whether a particular clause should be excluded. In a file parser.py in function _raw_parse (line 161) only the line that ends with : is checked for excluded expressions, not all the lines in a statement that ends with a colon. The solution is to add checking if at least one line in the multi-line statement ended with : has to be excluded and if that is the case - to exclude that clause. Multi-line statements are added after a token \n, so after checking for excluded clauses in one-line statements. Because of that, checking if a clause after multi-line statement should be excluded was added starting from the line 193.
Tests with different use cases were added.

I'm going to merge this. I've thanked Jan Rusak in the changelog and contributors file.  I'll gladly add other names, but I'm not sure what they are! :)

Thanks - we did it together: Jan Rusak, Maciej Kowalczyk and Joanna Ejzel.

Thanks again, I added the names in 470e086f2961169e0998737157d99924c19bc8e4

This is now released as part of coverage 7.3.3.


strictNullChecks still allows to assign undefined to the variable declared as number

TypeScript Version:  2.0.0
Code
// strictNullChecks is on
var x: number[] = [];
var y: number = x[0];
y.toString(); // Cannot read property 'toString' of undefined

Expected behavior:
error TS2322: Type 'undefined' is not assignable to type 'number'
Actual behavior:
after compile with command tsc --strictNullChecks
Runtime exception: Cannot read property 'toString' of undefined
I thought strictNullChecks  a there to prevent developer from seeing such kind of exceptions in run time.

This is working as intended. We don't attempt to validate that array indexing operations produce existing elements; rather, we assume they always do. While this is technically not correct, the alternative of always adding undefined to the resulting type would simply be too painful. See discussion here. You could speculate that we could catch the issue in a few isolated cases (such as reading elements after assigning [] and before any elements are added), but it's not clear it is a common real world situation that would merit the effort to do so.

I would recommend adding this information to docs (handbook + what's new) because it's not the first time this issue is submitted to GitHub - and I guess people don't try to search in closed issues to find all the duplicates - and first thought it is that this is in fact TS issue - and it's not easy to find that comment https://github.com/Microsoft/TypeScript/pull/7140#issuecomment-192606629 in Pull Request comments that explains that it's made for the convenience reason :)
Or maybe --strictNullChecks=pain flag for the brave ones ;)

Ok, I see this is a tough problem. But for the end-user/programmer, it means that if my function, for example, accepts a number parameter I still must do guard checks whether it is undefined or not, even with --strictNullChecks, because my language does guaranty nothing. Probably I just don't understand the value proposition of strictNullChecks...

People don't search the docs either. :cry:
Consider the alternative universe where we did say you had to guard-off undefined in an array. Now every for loop looks like this:
const arr = [1, 2, 3];
for (let i = 0; i < arr.length; i++) {
  console.log('Element ' + i + ' has value ' + (arr[i]!).toFixed());
}

with the ! in there because the programmer thinks they've guarded against length. Then people are like "Why do I have to write ! after my array element accesses?" and the response is "So we can be sure you've thought about bounds checking", but the problem doesn't actually go away. I mean, no one just randomly accesses an element in an array without thinking about bounds. So instead you get a universe where every array element access is suffixed by ! as some meaningless ritual you have to do every time (which is annoying), but it's not actually linked to a proper bounds check in any world.
This doesn't actually help anyone. You can still write this
const arr = [1, 2, 3];
for (let i = 0; i <= arr.length; i++) {
  console.log('Element ' + i + ' has value ' + (arr[i]!).toFixed());
}

or
const arr = [1, 2, 3];
for (let i = 0; i < arr.length; i++) {
  console.log('Element ' + i +
    ' has value ' + (arr[i]!).toFixed() +
    ' and the next one is ' + (arr[i + 1]!).toFixed() );
}

or any other number of ways to get it wrong.
 This is useful only because it can tell if you have your seatbelt on or not. A non-useful check would be that when you started the engine, you had to press a button that said "I have my seatbelt on". You'd immediately get into the habit of pressing that button regardless of whether you were actually buckled in. That's basically safety-by-EULA. Same here.


How to set up language for map and autocomplete form?

Hi
How to set up language for map and autocomplete form?
thanks

You can force the language to be used in all maps API by specifying it in the script.
Here's where I found the solution:
http://stackoverflow.com/a/28130182/1920145
Basically, add &language=YourLanguageAbrv at the end of the URL of the script


MPPT data form "openDTU on Battery" in ioBroker

Thanks for your well working ioBroker interface for the openDTU. Now i have add a 2nd instanz for a new "openDTU on Battery" to ioBroker. Is there a chance to get also MPPT Data (Victron) into ioBroker ? Up to now ther are only Data from Hoymiles.

Currently only the original OpenDTU project is supported, and no forks of it.

Can't you get the data with this adapter?
https://github.com/derAlff/ioBroker.ve

Duplicate of https://github.com/o0shojo0o/ioBroker.opendtu/issues/51


tidied code to remove circular dependency

Pull Request
Description
I've tidied the code to remove a circular dependency on app. I've moved the db and ouath objects into a separate file and then referenced these and configure them inside the init.py file.
I've also moved the blueprint code out of the init.py files into the route files themselves. I've deleted the init.py files as they were empty and aren't required in Flask 3.x to show the directory is a package
Fixes # None
How Has This Been Tested?
I've run the tests locally and all passed.
I've also manually clicked through the website to check it's working as expected.
Checklist:

[ x] My code follows the style guidelines of this project
[ x] I have performed a self-review of my own code
[ x] I have commented my code, particularly in hard-to-understand areas
[ x] I have made corresponding changes to the documentation
[ x] My changes generate no new warnings
[ x] Any dependent changes have been merged and published in downstream modules

the sonar fail is because there are little tests around init that creates the application. Hard to test for this,


reload-daemon on systemd enable

On a clean install, need to reload-daemon for the service to be visible for enable.

Thanks for this PR. :+1: I will propagate it to other repos in @cloudalchemy


[v1.19-beta] Creating block decoration on manually created editor make editor rendering odd.

Same issue of already closed #14743
Also might be related to this #14811

Prerequisites

[x] Put an X between the brackets on this line if you have done all of the following:

Reproduced the problem in Safe Mode: http://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
Followed all applicable steps in the debugging guide: http://flight-manual.atom.io/hacking-atom/sections/debugging/
Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description
Creating block decoration at manually created editor make editor rendering odd.

In v1.18: no issue
In v1.19-beta: have issue(so editor rendering degradation?)

Additionally

If I open item by workspace.open(item): issue happen
If I open item by pane.activateItem(item): issue NOT happen
Although, both have un-scrollable issue described in #14811

Steps to Reproduce

launch atom in safe mode.
Open dev-console and paste code below.

it create editor and put 100 lines text
And add block decoration at point [0, 0]

(function reproduceIssue() {
  const {TextEditor} = require("atom")
  const editor = new TextEditor()

  // case-1: Open with workspace.open
  atom.workspace.open(editor)

  // case-2: Open with pane.activateItem
  //   If I opened by pane.activateItem, this rendering odd is not happens.
  //   But still can't scroll though
  // const pane = atom.workspace.getActivePane().splitRight()
  // pane.activateItem(editor)

  const lines = []
  for (let i = 1; i < 100; i++) {
    lines.push(i)
  }
  editor.insertText(lines.join("\n"))
  editor.setCursorBufferPosition([0, 0])

  // Add blockdecoration at point [0, 0]
  const item = document.createElement("div")
  item.innerText = "[block decoration]"
  const marker = editor.markBufferPosition([0, 0])
  editor.decorateMarker(marker, {type: "block", item: item})
})()

see text is inserted at different line where cursor is displayed.

Versions
macOS
ProductName:	Mac OS X
ProductVersion:	10.12.5

Atom
Atom    : 1.19.0-beta0
Electron: 1.6.9
Chrome  : 56.0.2924.87
Node    : 7.4.0

Additional Information
I noticed this issue while I'm investigating slowness of beta when opening manually created editor on my atom-narrow package.
Opening manually created editor is slower than atom-stable, not fully investigated yet(maybe this rendering issue might be cause of slowness).

Please don't open clones of closed issues.

What do you mean?

Thanks very much @as-cii as always!!


Refactored to make compound-forks handlers more generic

This PR refactors src/mapping.ts for compound-forks to make the handlers more generic (accepting necessary information as arguments to handler functions instead of from a particular Event object), following the discussion at https://github.com/messari/subgraphs/pull/263#issuecomment-1145430732 .
Two test runs are ongoing: https://thegraph.com/hosted-service/subgraph/tnkrxyz/aurigami and https://thegraph.com/hosted-service/subgraph/tnkrxyz/venus-subgraph (no errors so far).

I agree that is generally a better approach - but I don't like the fact that I have to create a Data class like MarketListData for each handler. What do you think of _handleAccrueInterest({totalBorrows, AccrueInterest})? With this, we will need validation inside each handler for presence and correct type of params.

@0xbe1 I agree that is generally a better approach - but I don't like the fact that I have to create a Data class like MarketListData for each handler. What do you think of _handleAccrueInterest({totalBorrows, AccrueInterest})? With this, we will need validation inside each handler for presence and correct type of params.

hmm that's also a good point 🤷 assemblyscript is very verbose.
LGTM

@tnkrxyz nice job! I think the method headers should be updated in src/mapping.ts.
Also looks like their was a syncing issue with the aurigami test.
Other than that lgtm

@0xbe1 I agree that is generally a better approach - but I don't like the fact that I have to create a Data class like MarketListData for each handler. What do you think of _handleAccrueInterest({})? With this, we will need validation inside each handler for presence and correct type of params.

hmm that's also a good point 🤷 assemblyscript is very verbose.

@0xbe1, I have tried to pass an object as an argument:
export function _handleAccrueInterest(
  updateMarketData: UpdateMarketData,
  accrueInterestParams: {
    comptrollerAddr: Address;
    interestAccumulated: BigInt;
    totalBorrows: BigInt;
  },
  event: ethereum.Event
): void {...}

But graph build complains that ERROR TS1109: Expression expected, seem to me due to assemblyScript more limited than typescript. So what I have in mind doesn't work. Do you think it is worthwhile to create a Data class (like MarketListData) for each handler function to contain the params?
@dmelotik , Yes, I will be updating the header to remove unused imports. aurigami subgraph failing is weird, because it doesn't seem to relate to my changes at all: failed to process trigger: block #61007515 (0x8a70…09de), transaction 276c3690a9721a11a01eba68381f647e987bf56313c21d9dd97f03419c3e1164: Found no transaction for event. I am pushing another deploy without my changes to see if it works.

@tnkrxyz
aurigami - it seems the error relates to Aurora issue with The Graph, do you mind reaching out The Graph team at #subgraph-development channel on graphprotocol server?
if it is worthwhile - yeah if you want it to work it has to be in the Data class way. I am still not sure if it is worthwhile, but I think it is good to go without these Data class

@0xbe1 Sure, I will reach out to the graph team (not yet on their discord server)
Let me confirm if I understand you correctly - I will keep params of the handler functions as they are now in my commit and no need to convert the params to data class. Am I right?

@tnkrxyz yeah you're right

This PR is now ready to be merged. The issue with aurigami subgraph remains (I am getting access to the thegraph discord server & report the issue there), but it has nothing to do with our code.

This PR is now ready to be merged. The issue with aurigami subgraph remains (I am getting access to the thegraph discord server & report the issue there), but it has nothing to do with our code.

Would you be able to open an issue to track the aurigami issue? Otherwise great job on this! And appreciate @dmelotik @0xbe1 for looking this over!

Tracked with issue #343


I suggest adding "CSS Device Adaptation" to caniuse.com  It's the standard that W3C ar...

I suggest adding "CSS Device Adaptation" to caniuse.com
It's the standard that W3C are moving towards, using CSS to specify viewport properties as opposed to the currently used meta tag. It's neater with CSS.

This issue was imported from Google Moderator
Moderator votes: +14
Issue added by john doe on 2014-04-02
To vote this issue up or down, simply include +1 or -1 in your comment.

This is a duplicate of #1012

Also already added at http://caniuse.com/#feat=css-deviceadaptation


Cannot set expiration time for lists

I'm creating a list of items with an expiration time, but, I'm having the following error:
irb>> Kredis.list "mylist", expires_in: 1.minute
kredis-1.5.0/lib/kredis/types.rb:62:in `list': unknown keyword: :expires_in (ArgumentError)

https://github.com/rails/kredis/blob/main/lib/kredis/types.rb#L64-L66
def list(key, default: nil, typed: :string, config: :shared, after_change: nil)
  type_from(List, config, key, after_change: after_change, default: default, typed: typed)
end

It appears that some kredis types do not support expires_in.
If this is not simply a typo, there may be a reason for this.

@nzwsch Yes, I have to do a little trick to expire work:

First add the parameter:

module Kredis::Types
  def list(key, typed: :string, config: :shared, after_change: nil, expires_in: nil)
    type_from(List, config, key, after_change: after_change, typed: typed, expires_in: expires_in)
  end

  def unique_list(key, typed: :string, limit: nil, config: :shared, after_change: nil, expires_in: nil)
    type_from(UniqueList, config, key, after_change: after_change, typed: typed, limit: limit, expires_in: expires_in)
  end
end

Override the Kredis list to set the expiration time on key when first value is set:

class Kredis::Types::List < Kredis::Types::Proxying
  proxying :lrange, :lrem, :lpush, :ltrim, :rpush, :exists?, :del, :expire

  attr_accessor :typed, :expires_in

  def prepend(*elements)
    return unless elements.flatten.any?

    l = lpush types_to_strings(elements, typed)

    set_expire

    l
  end

  def append(*elements)
    return unless elements.flatten.any?

    r = rpush types_to_strings(elements, typed)

    set_expire

    r
  end
  alias << append

  private

  attr_accessor :expire_at

  def set_expire
    return unless expires_in

    if expired?
      @expire_at = expires_in.from_now

      expire expires_in
    end
  end

  def expired?
    !expire_at || expire_at.past?
  end
end

I have to do the same with hash type too. Would be nice to have this behavior in the Kredis itself

Pull request welcome 🤗


Contract size limit issue on Besu v24.8.0 – Unknown4 is above the contract size limit (29897 > 24576)

I am running a Besu node with version 24.8.0, and I encountered an issue while trying to deploy a contract. The error message is as follows:

Unknown4 is above the contract size limit (29897 > 24576).
To resolve this, I tried increasing the contract size limit by adding the following to my genesis.json config file:
"contractSizeLimit":<PHONE_NUMBER>
After adding this change, I restarted the node and even performed a full resync from scratch. However, the issue persists, and the same error continues to appear.
Below is the genesis.json configuration I am using:
{
  "config": {
    "chainId": 1337,
    "homesteadBlock": 0,
    "eip150Block": 0,
    "eip150Hash": "0x0000000000000000000000000000000000000000000000000000000000000000",
    "eip155Block": 0,
    "eip158Block": 0,
    "byzantiumBlock": 0,
    "contractSizeLimit":<PHONE_NUMBER>,
    "constantinopleBlock": 0,
    "petersburgBlock": 0,
    "istanbulBlock": 0,
    "muirglacierblock": 0,
    "berlinBlock": 0,
    "londonBlock": 0,
    "zeroBaseFee": true,
    "qbft": {
      "blockperiodseconds": 2,
      "epochlength": 30000,
      "requesttimeoutseconds": 20
    }
  }
}

Steps taken to resolve:

Increased the contractSizeLimit value to<PHONE_NUMBER> in the genesis file.
Restarted the Besu node.
Resynced the node from scratch.

Expected Behavior: The contract should be deployed successfully, and the contract size limit should reflect the updated configuration.
Actual Behavior: The same error continues to appear despite the configuration changes.
Environment:

Besu version: 24.8.0
Chain ID: 1337

Can someone help to resolve:

How to increase the contract size limit ?
How to verify the configuration worked (Deploying a large contract is the only way?)

On discord, user also sent this for how they are deploying the contract:
forge script src/deploymentAndConfiguration/scripts/DeployAndConfigureSystem.s.sol:DeployAndConfigureSystem --fork-url http://localhost:8545/ --broadcast --with-gas-price 0 --legacy

@Manjeet-Nethermind If you can share the DeployAndConfigureSystem.s.sol also, that will help us recreate this.

They also said:

I have updated the node to the v:24.9.1 and also synced it from scratch but the error remains same and when I proceed with the deployment a lot of txs get dropped from the mempool

@shemnon could this be a regression of #7557 ?

I don't think it's Besu throwing the error, as "is above the contract size limit" is not an error string in any Besu code.  I think the toolchain is intercepting the large contract and not submitting it to Besu.
@Manjeet-Nethermind What toolchain are you using?

On discord they said

The issue is resolved on upgrading all the nodes to the latest version the contract is successfully deployed.


General fixes to get it working

These are the fixes I had to make to get this working with Capistrano 3.2.1.

Closing this per https://github.com/capistrano/github/issues/9 in favor of https://github.com/3scale/capistrano-github. Future issues should be sent there.


ESP32: Fix lock-app protos

Problem
Compilation of lock-app fails when Pigweed is enabled.
Change overview
Made the necessary changes in the lighting service proto.
Testing
Compiled the app successfully and tested using pigweed HDLC console.
However, for a successful compilation, I have added the necessary changes of this PR #8129.

@sweetymhaiske Please close this if it is not applicable now (as per the comments from @rgoliver )

RPC with lock-app fails now, waiting for the custom console.


leddy: Init at 0.1.0-unstable-2024-04-05

https://github.com/XanClic/leddy
A program for cotrolling the LEDs of Fnatic Streak and miniStreak keyboards.

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/4713

Does this need another approval or can it be merged?


data: dev-rakeshshaw

Fixes Issue

Changes proposed

Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[ ] My change requires changes to the documentation.
[ ] I have updated the documentation accordingly.
[ ] All new and existing tests passed.
[x] This PR does not contain plagiarized content.
[ ] The title of my pull request is a short description of the requested changes.

Screenshots

Note to reviewers

LGTM 🎉

Thanks

LGTM 👍

Thanks

when will my PR get merged?


ERROR in SocialLoginModule is not an NgModule

Bug Report or Feature Request (mark with an x)
- [x] bug report
- [ ] feature request

Versions.
@angular/cli: 1.2.6
node: 7.10.0
os: darwin x64
@angular/animations: 4.3.2
@angular/common: 4.3.2
@angular/compiler: 4.3.2
@angular/core: 4.3.2
@angular/forms: 4.3.2
@angular/http: 4.3.2
@angular/platform-browser: 4.3.2
@angular/platform-browser-dynamic: 4.3.2
@angular/router: 4.3.2
@angular/cli: 1.2.6
@angular/compiler-cli: 4.3.2
@angular/language-service: 4.3.2
Repro steps.
git clone https://github.com/jaibatrik/ng4social-test.git
cd ng4social-test
npm install

ng build

The log given by the failure.

ERROR in SocialLoginModule is not an NgModule

Desired functionality.
The SocialLoginModule (coming from angular4-social-login node module) publishes the .ngsummary.json as required. One can check that by navigating to ./node_modules/angular4-social-login/dist/lib directory.
I understand and have seen similar issues have been reported. But most of them talk about the metadata JSON not being published and hardly have any other useful information. The stack trace (if it can be called that) also contains surprisingly low amount of information.
Mention any other details that might be useful.
Link to the library used -
https://github.com/abacritt/angular4-social-login

I think you have some problem in the way you build your library. I checked your .ngsummary.json files and you have absolute paths like this: "filePath":"/Users/duttj2/WebProjects/angular4-social-login-old/a4sl-flat.d.ts". That's probably the cause of your build issues.

@filipesilva I surely have no clue on how the absolute path got generated. I am running the following command to build -
ngc && rollup -c
Below is the contents of my tsconfig.json -
{
  "compilerOptions": {
    "target": "es5",
    "module": "es2015",
    "moduleResolution": "node",
    "sourceMap": true,
    "emitDecoratorMetadata": true,
    "experimentalDecorators": true,
    "declaration": true,
    "stripInternal": true,
    "inlineSources": true,
    "skipLibCheck": true,
    "lib": [
      "es2015",
      "dom"
    ],
    "outDir": "dist",
    "noImplicitAny": true,
    "suppressImplicitAnyIndexErrors": true,
    "typeRoots": [
      "./node_modules/@types/"
    ],
    "baseUrl": ".",
    "paths": {
      "@angular/*": [
        "./node_modules/@angular/*"
      ]
    }
  },
  "files": [
    "index.ts"
  ],
  "angularCompilerOptions": {
    "annotateForClosureCompiler": true,
    "strictMetadataEmit": true,
    "skipTemplateCodegen": false,
    "flatModuleOutFile": "a4sl-flat.js",
    "flatModuleId": "a4sl-flat",
    "genDir": "dist"
  }
}

And below is my rollup.config.js -
import nodeResolve from 'rollup-plugin-node-resolve';
import commonjs from 'rollup-plugin-commonjs';
import sourcemaps from 'rollup-plugin-sourcemaps';
// import uglify from 'rollup-plugin-uglify';

import * as _angular_core from '@angular/core';

export default {
  entry: 'dist/a4sl-flat.js',
  dest: 'dist/angular4-social-login.js', // output a single application bundle
  sourceMap: true,
  format: 'umd',
  moduleName: 'Angular4SocialLogin',
  external: [
    '@angular/core'
  ],
  globals: {
    '@angular/core': 'ng.core'
  },
  onwarn: function (warning) {
    // Skip certain warnings

    // should intercept ... but doesn't in some rollup versions
    if (warning.code === 'THIS_IS_UNDEFINED') { return; }

    // console.warn everything else
    console.warn(warning.message);
  },
  plugins: [
    commonjs({
      include: ['node_modules/rxjs/**']
    }),
    sourcemaps(),
    nodeResolve({ jsnext: true, module: true })
    // uglify()
  ]
};

Do you have any idea what might be causing absolute paths to appear in the JSONs?

And, of course, ng serve works. Once I touch any file. I really don't understand what's the deal with this compiler :(

Also, do I need to bundle the .ngsummary.json files in the distributed package?

I removed them, so now the distributed package does not contain .ngsummary.json files and there's no reference to absolute paths now. Yet, the same issue persists.
Could you please help?

I'm sorry but it's both out of scope for the CLI itself, and rather time intensive to debug your particular library setup and try to figure out what's going wrong with it. The best I can do is to direct you to the ongoing discussion about library support in the CLI: https://github.com/angular/angular-cli/issues/6510
It discusses a few of the challenges in creating libraries and lists several alternatives that work today. You should have success using the existing starters and they often offer setup instructions. This is better than rolling your own setup because it isn't very straightforward (as you're experiencing).

Thanks @filipesilva. I'll rather take that path and see how it goes.


System.Text.Json Hub Protocol

Fixes https://github.com/aspnet/AspNetCore/issues/5387
Fixes #8969
We are blocked on a couple APIs that will be merged soon. So the reading and writing works for only a couple scenarios. Ignore the test failures and the todo comments for using an API that doesn't exist yet.
The meat of this change is in JsonHubProtocol.cs and I've also converted our json unit tests to a base test class so newtonsoft and system.text.json can share a lot of the tests. This part is still a little WIP as I figure out what tests can be shared.

Ping, could you guys pre-review this so that if we magically get new bits this week it'll be easier to get this merged.

cc @ahsonkhan

If we turn this off by default, can we try to get it in for preview 4 so people can use it?
@BrennanConroy can you update to make this off by default and verify the code necessary to turn Newtonsoft off and System.Text.Json on? That way we can blog about it.

:up: 📅 Newtonsoft is the new old default.

@aspnet-hello triage https://dev.azure.com/dnceng/public/_build/results?buildId=147444&view=logs

This comment was made automatically. If there is a problem contact ryanbrandenburg.
I've triaged the above build.

Ok, after discussions with JSON folks and @BrennanConroy, let's withdraw this from preview 4. It sounds like the big JSON push will be in preview 5

It might be worth combining the three places we call var bytes = JsonSerializer.ToBytes(...); using var token = JsonDocument.Parse(bytes); token.RootElement.WriteAs... into a helper method since we'll want to replace that logic later.

Is that the only thing blocking approval?
If so, could you approve and I'll make the changes soonish.

I'll approve it if it really needs to get in soon. I'm hoping someone else like @davidfowl or maybe @JamesNK will also take another look at this and approve it.
I didn't realize we were still rushing to get this in after it missed the preview4 train. I can understand not wanting to deal with merge conflicts piling up.
I haven't been in any discussions about when this needs to be merged or what changes we expect from corefx before we're comfortable pushing. Ideally we wouldn't merge this until we had a not-so-crazily-inefficient way to serialize nested objects of arbitrary types.

@aspnet-hello triage https://dev.azure.com/dnceng/public/_build/results?buildId=154173

This comment was made automatically. If there is a problem contact ryanbrandenburg.
I've triaged the above build.


[React] Nested FloatingPortal doesn't obey root prop

When having nested FloatingPortal elements, the inner portals don't respect their root prop and are set on the parent portal node. Cause: (code)
This leads to issues in more complex scenario's, e.g. a modal component with a child scroll wrapper that then has popover elements.
const ref = useRef();

...

<FloatingPortal>
  <ScrollWrapper ref={ref}>
    <FloatingPortal root={ref?.current} />
  </ScrollWrapper>
</FloatingPortal>

In the pseudo-code example above, when the inner portal is open, the element will scroll with the parent portal, rather than within the scroll wrapper.
Potential fix is to change the priority and use the provided root element if defined:
-let container = portalContext?.portalNode || root || document.body;
+let container = root || portalContext?.portalNode || document.body;

Seems valid to me.
Side note: you're reading the ref in render, but that's not allowed by React - I think we can accept a ref as well as an element for the root prop to reduce that type of usage.


MongoDB Driver insert

I used MongoDB Driver insert a record , but how can i get the last insert _id? My code like that:
name = 'Bob';
$record->email =<EMAIL_ADDRESS>$bulk->insert($record);
$result = $manager->executeBulkWrite($collection, $bulk);
`
There is no way to get insert _id ?

A couple of things: This repo is for the "wrapper" around things like MongoDB\Driver\Manager and MongoDB\Driver\BulkWrite. You might want to look into the MongoDB\Client that this repo provides. This question really belongs in the driver repo.
But to answer your question, you should be able to use:
$id = \MongoDB\extract_id_from_inserted_document($record);
after your executeBulkWrite. This is basically what the BulkWrite wrapper this repo provides does.

BulkWrite::insert() actually returns the ID value if it was generated. If the inserted document already had an ID, nothing is returned. In your case, you'll want to save this value:
$generatedId = $bulk->insert($record);

Alternatively, if you are using this library and its write methods, the following methods exist:

InsertOneResult::getInsertedId()
InsertManyResult::getInsertedIds()
BulkWriteResult::getInsertedIds()

The write operations, which return these result objects, attempt to obtain the ID from the return value of BulkWrite::insert(). In the case where the inserted document already had an ID, we still want to populate the result objects. For that reason, we have an internal  \MongoDB\extract_id_from_inserted_document() function that attempts to pull the ID out of the user-supplied document. That said, the function is a not part of our public API (the best we can do is annotate it with @internal), so please do not depend on it.


:test:gdx-tests-android:lint Execution Failure

#5352 resolves this issue.
Issue details
Command line
gradle lint

fails to fetch the artifacts for android linter 26.1.0.
Reproduction steps/code

Clone a fresh copy from master.

Run the command

gradle lint

Version of LibGDX and/or relevant dependencies
1.9.9-SNAPSHOT
Stacktrace
* What went wrong:
Execution failed for task ':tests:gdx-tests-android:lint'.
> Could not resolve all files for configuration ':tests:gdx-tests-android:lintClassPath'.
   > Could not find com.android.tools.lint:lint-gradle:26.1.0.
     Searched in the following locations:
       - file:/Users/tim/Library/Android/sdk/extras/m2repository/com/android/tools/lint/lint-gradle/26.1.0/lint-gradle-26.1.0.pom
       - file:/Users/tim/Library/Android/sdk/extras/m2repository/com/android/tools/lint/lint-gradle/26.1.0/lint-gradle-26.1.0.jar
       - file:/Users/tim/Library/Android/sdk/extras/google/m2repository/com/android/tools/lint/lint-gradle/26.1.0/lint-gradle-26.1.0.pom
       - file:/Users/tim/Library/Android/sdk/extras/google/m2repository/com/android/tools/lint/lint-gradle/26.1.0/lint-gradle-26.1.0.jar
       - file:/Users/tim/Library/Android/sdk/extras/android/m2repository/com/android/tools/lint/lint-gradle/26.1.0/lint-gradle-26.1.0.pom
       - file:/Users/tim/Library/Android/sdk/extras/android/m2repository/com/android/tools/lint/lint-gradle/26.1.0/lint-gradle-26.1.0.jar
       - https://repo.maven.apache.org/maven2/com/android/tools/lint/lint-gradle/26.1.0/lint-gradle-26.1.0.pom
       - https://repo.maven.apache.org/maven2/com/android/tools/lint/lint-gradle/26.1.0/lint-gradle-26.1.0.jar
       - https://jcenter.bintray.com/com/android/tools/lint/lint-gradle/26.1.0/lint-gradle-26.1.0.pom
       - https://jcenter.bintray.com/com/android/tools/lint/lint-gradle/26.1.0/lint-gradle-26.1.0.jar
       - https://oss.sonatype.org/content/repositories/snapshots/com/android/tools/lint/lint-gradle/26.1.0/lint-gradle-26.1.0.pom
       - https://oss.sonatype.org/content/repositories/snapshots/com/android/tools/lint/lint-gradle/26.1.0/lint-gradle-26.1.0.jar
     Required by:
         project :tests:gdx-tests-android

Please select the affected platforms

[X] Android
[ ] iOS (robovm)
[ ] iOS (MOE)
[ ] HTML/GWT
[ ] Windows
[ ] Linux
[ ] MacOS

You aren't supposed to open an issue with your pull requests...

Closing this issue since I submitted a PR for it.


No trade combinations listed

this means there is an error on application.yaml?

That message isn't an error. It just means we haven't defined any Spring profiles and Spring is telling us it's going to use the default profile. We don't define any Spring beans that use profiles, so there is no effect from using the default profile. Nothing to worry about. :)

ok thanks for reply ..well i just wonder why not work cause i put run this for a while and no new messages

i have this in application.yaml  i changed to txt at the end for can upload here...
my question is maybe i set wrong something?
application.yaml.txt

Ok, the line after that "Trading the following exchanges and pairs:" should have a list of the pairs being traded. The fact that it's empty means the bot is not doing anything. For reference, mine looks like this:

There are a number of reasons something like that could happen, so let me briefly explain the process the bot goes through to create that list. Those are what we call "trade combinations". It's a pair of exchanges and a currency pair. For example, Gemini/Kraken LTC/USD means we're using Gemini to make the long trade, Kraken to make the short trade, and LTC/USD as the currency.
For a trade combination to work you must have three things:

A "long" exchange where you can use a fiat currency (USD, EUR, etc.) to buy a cryptocurrency (BTC, ETH, LTC, etc.).
A "short" exchange where you can use margin to borrow cryptocurrency to sell for fiat. In your configuration you would have a line that says margin: true for this exchange.
Those two exchanges must both support at least one of the same currency pairs.

The bot goes through all the exchanges that you configured and automatically figures out these trade combinations for you. If it doesn't list any combinations it means that none of the exchanges in your configuration met the criteria I listed above.
Thanks for providing your configuration, and even more for not including your API keys. :)
It looks like both the exchanges in your configuration have margin: false which is appropriate. I don't think either one of those exchanges supports margin trading. You'll need to add at least one more exchange that does support margin before the bot will create any trade combinations. If you're in the US I suggest Kraken1 . If you're in the EU you can also try Liquid2.
Hopefully that helps get you started. Let me know if you have any other questions.
1 I'm not affiliated with Kraken in any way but I am a customer. They are currently the only exchange that supports margin and is supported by XChange (the library we use to connect to exchanges) and that allows customers from the USA.
2 I'm not affiliated with Liquid/Quoine in any way but I used to be a customer. They dropped all of their US based customers so I can't use them any more, but I liked their service and look forward to when they can operate in the US again.

thanks a lot for the reply ,,,ok so margin to true now ...but your think i need one more exchange so this work? so gemini and cexio none of this works? how i can have a list of they support margin in USA

At the moment the only margin exchange I know of for US customers is Kraken. Coinbase Pro has a new margin feature that is in beta but XChange doesn't support it yet, so we can't either.


Symetrical Sinkhorn loss

Hi @fwilliams,
After trying your sinkhorn loss on 2 point cloud it seems that it's not symetrical wrt the 2 set of points. Is that true ?
Best,

Hi Theo,
Thanks for posting the issue!
If your two point sets are labelled X and Y (both arrays of shape Nx3), and weights are a and b (arrays of shape N), then flipping the order of the input sets is equivalent to transposing the distance matrix M (M_ij = ||X_i - Y_j||) and passing a and b in the opposite order. i.e.
# Calling sinkhorn with the arguments X and Y flipped
M = np.linalg.norm(X[:, np.newaxis, :] - Y[np.newaxis, :, :], axis=-1)
pcu.sinkhorn(b, a, M.T, eps=...)

The matrix M is not symmetric unless X and Y are equal and Sinkhorn is an iterative algorithm, so passing the transpose M.T starts the iterations from a different place. Thus, if the number of iterations is too small, then the two calls may not agree to the number digits you expect. The eps parameter controls the stop threshold and, thus the number of digits that we expect the two calls to agree in, while max_iters controls the maximum number of iterations. Smaller eps means longer convergence times, but more digits. If your two calls disagree a lot, try increasing the maximum number of iterations. If you want them to agree in more digits, try decreasing eps.
Let me know if that helps and if you have any more questions, I'm happy to help :smile:

Hi Theo,
Thanks for posting the issue!
If your two point sets are labelled X and Y (both arrays of shape Nx3), and weights are a and b (arrays of shape N), then flipping the order of the input sets is equivalent to transposing the distance matrix M (M_ij = ||X_i - Y_j||) and passing a and b in the opposite order. i.e.
# Calling sinkhorn with the arguments X and Y flipped
M = np.linalg.norm(X[:, np.newaxis, :] - Y[np.newaxis, :, :], axis=-1)
pcu.sinkhorn(b, a, M.T, eps=...)

The matrix M is not symmetric unless X and Y are equal and Sinkhorn is an iterative algorithm, so passing the transpose M.T starts the iterations from a different place. Thus, if the number of iterations is too small, then the two calls may not agree to the number digits you expect. The eps parameter controls the stop threshold and, thus the number of digits that we expect the two calls to agree in, while max_iters controls the maximum number of iterations. Smaller eps means longer convergence times, but more digits. If your two calls disagree a lot, try increasing the maximum number of iterations. If you want them to agree in more digits, try decreasing eps.
Let me know if that helps and if you have any more questions, I'm happy to help :smile:

@TheoDEPRELLE does this answer your question? If so, I'll close the issue.

@TheoDEPRELLE does this answer your question? If so, I'll close the issue.

Yes !
Thanks a lot ;)
I'm closing the issue

Yes !
Thanks a lot ;)
I'm closing the issue


Add --remove-id and --lazy; bugfix in @Index

New features

--ri / --remove-id: removes an _id suffix from all fields (unless the entire field name is _id)

This is nice for fields that are relations; for example, if an entity Post references an entity User via a field author_id, the field to access the User entity is now Post.author instead of Post.author_id when the --ri flag is used.

--lazy: emits lazy relations on all join fields

This essentially just adds { lazy: true } to the relation decorator and changes the type from T to Promise<T> for all relation fields.
Bugfixes
This PR also fixes a bug wherein the column names referenced in @Index did not match those in the generated models when --cp is used.

Hi and thank you for your contribution!
I think --ri option could be added temporary. In future it would be good to utilize typeorm custom naming strategy, but it will be complex feature so it will take some time to implement.
It would be good to have some test for lazy relations and support eager relations, I will write them when I'll have some more free time(or you can write them yourself if you like).

Closing as no activity.


Basic structure of a Bot project.

A month ago, I wrote a C# Bot with v4.3. It was with a .bot file, and the AddBot extension method.
Now, I see there is a change in v4.4, and I looking for documentation for that, but I can't find.
If I open the EchoBot template with Visual Studio 19, I see a different structure than I know. I notice that in version 4.4 the bot is back under the normal controller.
Where is there an explanation for this?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 9d5bd35d-3178-42cd-2893-3b6a4b7a94ce
Version Independent ID: 1545fd44-d471-d947-f94d-4b5e8d6e853f
Content: Tutorial to create and deploy a basic bot - Bot Service
Content Source: articles/v4sdk/bot-builder-tutorial-basic-deploy.md
Service: bot-service
Sub-service: sdk
GitHub Login: @ivorb
Microsoft Alias: v-ivorb

There is an explanation in the Manage bot resources article.


Encoder states

The encoder state machine has some unreachable states (leftovers from older revisions?) involving the flag FLAG_ON_FINAL_LITERAL.  After removing those, FLAG_HAS_LITERAL is no longer used.  Additionally, the penultimate pair of state transitions search → save_backlog → flush_bits can be optimized.

Looks good. This streamlines encoding further, thanks.


bootstrap-sass not include in assetpath

When creating a new Project the integration of the bootstrap-sass gem works fine.
But now I wanted to integrate it in an existing project. But there the gem is not include into the assetpath. I checked with:
Rails.application.config.assets.paths The gem paths are not included.
Any ideas what went wrong?
On the Server I get the error:
couldn't find file 'bootstrap-dropdown' or every other file I try

Did you add 'bootstrap-sass' to the Gemfile, and re-bundle?

Yeah, Severall times. Also tried, bundle update. But nothing works. Server was restartet several times, too.

Did you solve this?


Method accepting NSError** should have a non-void return value

The following methods all return analysis warnings 'Method accepting NSError** should have a non-void return value to indicate whether an error occurred'
- (void)setString:(NSString *)string forKey:(NSString *)key error:(NSError *__autoreleasing *)error;
- (void)setData:(NSData *)data forKey:(NSString *)key error:(NSError *__autoreleasing *)error;
- (void)removeItemForKey:(NSString *)key error:(NSError *__autoreleasing *)error;
- (void)removeAllItemsWithError:(NSError *__autoreleasing *)error;
- (void)synchronizeWithError:(NSError *__autoreleasing *)error;

Can you create the cocoa pods with this fix? Thanks

Released v1.1.1
https://raw.githubusercontent.com/CocoaPods/Specs/036016b9ca0850c8c2e751191515dc562be8c8f3/Specs/UICKeyChainStore/1.1.1/UICKeyChainStore.podspec.json
Thank you for waiting.

Thank you!

On Jan 11, 2015, at 7:27 AM, kishikawa katsumi<EMAIL_ADDRESS>wrote:
Released v1.1.1
https://raw.githubusercontent.com/CocoaPods/Specs/036016b9ca0850c8c2e751191515dc562be8c8f3/Specs/UICKeyChainStore/1.1.1/UICKeyChainStore.podspec.json
Thank you for waiting.
—
Reply to this email directly or view it on GitHub.

Thanks!

This is old, but as I just had to fix this myself, I thought I would mention it.
Should you not be calling:
return *error == nil;
instead of
return error == nil;


Use standard pip instead of pipx

An attempt to solve macOS CI failures e.g. https://github.com/astral-sh/uv/actions/runs/8488022849/job/23256538175

Maybe once pipx is in the runner by default it'll be less likely to break? https://github.com/actions/runner-images/issues/9256
Weird that we can't find any issues about this.


✨ Add callout block support

Adding support for callout blocks and inserting emoji.
Closes #15

@scopsy Hi, thanks for the contribution, really appreciate it :)


Not scrolling to scrollId inside List

Frames has zero offset when you use AmzdScrollViewReader inside List
You can't scroll to the row that is not yet appeared

Yeah this is because List has lazy views so they won't actually exist until needed. If they dont exist then we can't get the frame. I don't have a solution for this issue right now, I am sorry for the inconvenience.
You can try to tackle this problem and make a PR or restructure to use a ScrollView.

Possible starting points to get this working is trying to Introspect the underlying view for List, it should be a table view or collection view, which you could then ask for the frame of a view maybe?

Thanks for feedback, yes its UITableView there but it can be tricky to map indexes onto IDs.
Also the first problem with frames seams to be caused by coordinateSpace and geometry.frame(in: .named(space)) because it gives offsets in ScrollView and in List they are nil even for visible cells.
I don't get how to figure out whats going on there.

From the README:

An important difference between this library and Apples implementation is that the ScrollViewReader goes inside the ScrollView. If you place the ScrollViewReader around the ScrollView the scrollTo function will not scroll to the correct location (due to its coordinateSpace not being part of the scrolling content). I considered fixing this to align with Apple but that would break backwards compatibility with projects already using ScrollViewProxy.


AnalysisPass API run refers to DAG input

Environment

Qiskit version:
Python version:
Operating system:

What is happening?
API content for AnalysisPass refers to DAG instead of the QC that I believe is the intended parameter to run on.
How can we reproduce the issue?
https://docs.quantum.ibm.com/api/qiskit/qiskit.transpiler.AnalysisPass
What should happen?
I believe that the content should relect that a quantum circuit is sent in during these method calls for the pass to run against.
Any suggestions?
I have never ever in my life made one of these issues on github, please give guidance if I have done this incorrectly!

Sorry for the delay in responding here.  AnalysisPass and TransformationPass both operate natively on DAGCircuit, which is Qiskit's compiler IR rather than the tree-like QuantumCircuit.  The compiler passes can all behave like regular Python callables that accept a QuantumCircuit, but natively all their methods are defined in terms of DAGCircuit.


fix unnecessary re-renders

PR Checklist
Please check if your PR fulfills the following requirements:

[x] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:

What is the current behavior?
Тow, even if handlers for node events are not passed, events are processed and unnecessary re-renders occur
What is the new behavior?
Added check if event handler is passed
Does this PR introduce a breaking change?
[ ] Yes
[x] No

@amcdnl any other changes need to be made?
Waiting for continue the development with this fix 😊

@Nerevar123 - All good - merged and releasing now

We probably want to do this for the other components too - can u look to see if that would help them too?

Thank you!
Sure, I'll take a look


Carthage support

Added framework and test schemes for each supported platform.
Made the schemes Shared for Carthage support.

Thanks!


Improve examples with ready to use examples

It would be nice to have examples for Language Models and NMT that show an end to end example for a given sentence.
nmt:
text = "I love playing football"
...
print(output)
"ich liebe es Fußball zu spielen"

language model:
text = "the winner of the 2018 world cup is"
...
print(output)
"France"

I would like to work on this, can you provide further details ?

Hi @ThomasDelteil. Thanks for bringing up this idea. Would you like to share more details?

@szha @ThomasDelteil How about using repl.it, as with the "Quick example" on the homepage right now:

Ideally we'd want a solution that can be part of our CI and is not mutable through means other than PR.

@leezu I am personnally not a big fan of repl.it and I think CI-tested scripts or notebooks are clearer.
@soulbliss @szha
My idea is to follow the example of the "using pre-trained word embeddings" notebook.
Have a "using pre-trained neural machine translation model" notebook that shows the usage, especially pre-processing post-processing steps for going from a sentence in one language, for example English, to another language for example German.
text = "I love playing football"
...
print(output)
"ich liebe es Fußball zu spielen"

Does that make sense?


Change the what's next message when swtching the contexts

When switching the context executing

cellery setup -> switch

change the what's next message according to the context.

Can you please explain in bit more detail about what you expect? Currently when I do cellery setup -> switch, I get message I see below.
What's next ?
======================
To create your first project, execute the command:
  $ cellery init

What could be the possible change you would like to have?


Kapacitor CLI should allow yml file extensions

Currently the define-topic-handler actions of the CLI do not recognize yml files as yaml files.

Fixed by https://github.com/influxdata/kapacitor/pull/1403


New package: Luxafor.Software version 1.0.0

[x] Have you signed the Contributor License Agreement?
[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] This PR only modifies one (1) manifest
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.4 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: codeflow:open?pullrequest=https://github.com/microsoft/winget-pkgs/pull/110356&drop=dogfoodAlpha

Automatic Validation ended with:

Manifest Error: Duplicate installer entry found.


Cannot Handle Extension Group In 36331-g30.asn1

When trying to parse 36331-g30.asn1 using the following command line parameters:
asn1c -pdu=auto -fcompound-names 36331-g30.asn1
I get this error:
ASN.1 grammar parse error near 36331-g30.asn1:2886 (token "[["): syntax error, unexpected TOK_VBracketLeft
Cannot parse "36331-g30.asn1"
The same parsing error is mentioned in 348 and 317. I've tried both the velichkov_s1ap_plus_option_group branch from brchiu's fork and mouse07410's fork, as have been recommended previously. On mouse07410's fork I still get the parsing error without generating any files. On brchiu's fork, the files are generated but then when I try to use them to generate a library for my own application, I get the same parsing error there as well.
Edit: A difference in the .asn1 file definition structure in the newer versions might be that the extension addition groups that fail to parse are now within a CHOICE statement. They were perhaps not within a CHOICE statement in the versions that brchiu and mouse07410 previously implemented on their forks.
Thank you!

I could compile (today)

36331-ck0.asn1
36331-dh0.asn1
36331-eg0.asn1
36331-fl0.asn1
36331-ge0.asn1
36331-h70.asn1
36331-i00.asn1

with mouse07410's version: https://github.com/mouse07410/asn1c


Thers isn't bevdet in model_zoo?

Hi, from the release note i see you add bevdet in model_zoo, but i don't find it. Where can i get it?

@Gang-Chen-China it may be one of the models that we couldn't release publicly due to licensing restrictions.  Can you contact your local AMD FAE and request it from them?


Questions about the meaning of folder naming conventions in OpenProteinSet

May I know what the difference is between these two folders——alignment_db and pdb?

Hi @lonelycrab888, sorry for the late reply. The alignment_db/ directory represents a different format for storing the alignments in the pdb/ directory which can be faster for I/O-bottlenecked systems. You can find more information about this in the docs


Adds .scss and .sass files support

This would throw large stacktraces when using css modules in https://github.com/pedronauck/docz.

Hey, thanks for contributing these two fixes!
With your other fix merged, I think this is fairly safe to merge. If I could just ask two things before I merge it though, I was wondering why this will cause the throwing of large stacktraces when using css modules I haven't dug into css modules yet.
Second q: I'm trying to ensure that codesandboxer-fs and codesandboxer stay in sync. It would be good to add .scss and .sass to https://github.com/Noviny/codesandboxer/blob/f3813c6fec06ee6fbc0e2501e816d7673a13252c/packages/codesandboxer/src/fetchRelativeFile/index.js#L143 this line as well.

No worries on slow reply, I'm just happy you are contributing.
I would assume we wouldn't get any error logs once scss is in the list of extensions that use the raw loader, unless there's something I'm missing.
If I have time tomorrow, probably going to work on shipping the update that supports these changes, just so the other bug fix (which is a fairly major problem) also gets out.

Closing this in favor of #39 , which takes this and runs with it to resolve imports.


Replaced the string "iteration" inside the for loop iteration

Checklist:

[x] I have read and followed the contribution guidelines.
[x] I have read and followed the how to open a pull request guide.
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

Closes ##56838

Why do you have two PRs open? Neither of the two solves the issue


compilation error in Xcode 7 beta 6 : print method signature

On Xcode 7, beta 6 the swift-2.0 branch is not compiling...
.../Pods/LogKit/Source/LogKit.swift:250:9: 'print(_:appendNewline:)' is unavailable: Please use 'terminator: ""' instead of 'appendNewline: false': 'print((...), terminator: "")'

Thanks for reporting! Fixed in Swift 2.0 branch by commit 5d42770056c469290dd0168b3ee7c87af1fa0961


Tsc task output limited in osx

VSCode Version: 1.8.1
OS Version: MacOS 10.11.6

We are converting a project over to TypeScript at the moment and have a strange issue which is causing some confusion. When any team member using macos builds through VSCode they get somewhere between 50-150 build errors shown in the Tasks output and problem window, on windows machines we get the full ~1300
It seems that VSCode on Mac just doesn't capture all of the output from the tsc process. Any ideas on what to try?

@JakeGinnivan Thank you for opening this issue. Can you share a workspace so we can try on our end?

Thank you for creating that repo @luke-john. Makes this much easier.
To make sure I understand you correctly ...

I ran through the steps in the README and see no errors in VS Code's error console.
I ran the tsc in the terminal and I see numerous errors.

Is this correct?
@dbaeumer can I pull you in here? Where does this land? Is this a tsserver thing? Doesn't seem like a language service issue as much as a task -> error console relationship issue. Please advise.

@waderyan
on the devices we're running here we are actually seeing some errors after running the build task
So after running the following

Run build task shift + command + b

We'll see errors are present down the bottom left of the vscode interface.
However the error number is incorrect (missing a lot of errors), it will also change between build task runs (so if you run shift + command + b  again there will be a different number of errors)
It seems unlikely to be a tsserver thing as it's the build task thats failing which is calling tsc, and when you open a file it does give the errors for that file.

This is not a tsserver bug. I will investigate.

with latest insiders on macOS 10.12.2

OK. On Mac we have a total of 136 errors whereas on Windows we do have 423. Even the number for demo.ts is different.

@luke-john I need to investigate why this is happening. You could do one thing to workaround this. We usually trigger compile via an npm script and never saw problems with that. Something like this in the package.json file:
	"scripts": {
		"compile": "tsc -p ."
	}

and in the tasks.json something like this:
{
	"version": "0.1.0",
	"command": "npm",
	"isShellCommand": true,
	"args": ["run", "compile"],
	"showOutput": "always",
	"problemMatcher": "$tsc"
}

Does that improve things?

Unfortunately that seems to have the same behaviour @dbaeumer.
I added the changes you suggested to a topic branch of the previous reproduction repo.
https://github.com/luke-john/vscode-18067-repro/tree/expoloration/npm-script

@luke-john I implemented a new task execution engine. Task will in the future be executed in a terminal instead of a output window which should fix this issue besides adding new capabilities. In the next drop tasks.json can opt in into the terminal execution by specifying "_runner": "terminal". Local testing shows that this should address the problem.
I don't plan to fix this in the old runner (output window based) since it has too many limitations and the new story will be terminal based.

@luke-john more work has happend for the terminal execution, but I still haven't switch it to be the default. Moving the issue until terminal is the default.

Current plan is to make the new terminal final in April and then switch. We added task API to vscode which we need to have a little while in proposed.

Moving due to shifted priorities.

You can opt into task v2.0.0 using a tasks.json of the form for April.
{
    "version": "2.0.0"
}

Will close the issue when task 2.0.0 will be the default.

This got addressed by the new terminal runner. To make use of the new terminal runner please see: https://code.visualstudio.com/docs/editor/tasks#_convert-from-010-to-200

Thank you very much for this @dbaeumer.
Really appreciate the great work yourself an the rest of the typescript and vscode teams do.


Modify the faq.md in the English version

Ⅰ. Describe what this PR does
This PR checks the spelling and grammar in faq.md in the English version.
Ⅱ. Does this pull request fix one issue?

Ⅲ. List the added test cases (unit test/integration test) if any, please explain if no tests are needed.
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

Codecov Report

Merging #717 (411f692) into master (2f8541d) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #717   +/-   ##
=======================================
  Coverage   16.72%   16.72%
=======================================
  Files          69       69
  Lines        3013     3013
=======================================
  Hits          504      504
  Misses       2458     2458
  Partials       51       51

Impacted Files
Coverage Δ

pkg/ddc/alluxio/transform_permission.go
62.50% <0.00%> (ø)

Continue to review full report at Codecov.

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