Weird scrolling behavior when scrolloff is set to a non-zero value

To reproduce:

In a buffer with more lines than fit in the window, :set scrolloff=1
Move using j or k

Expected behavior:
The cursor moves down or up, but the content of the window doesn't change until the cursor reaches the penultimate line when moving down or the second line when moving up
Observed behavior:
When starting from the top, as soon as the cursor is on the second line, the content starts to scroll with every move. When the cursor is in a lower line at the time the setting is changed, moving up also causes weird scrolling
This is using a current checkout (d9e6571) and neovim 0.1.7

Yep, I can reproduce this.  That's some weird behavior.

I can reproduce this too. I have scrolloff 3 in my vimrc and oni just moves the content at every 5 j scrolldown.

Actually, if scrolloff is not zero, another weird scrolling occurs when you scroll from the bottom of the file up using mousewheel. The content just keeps glitching while going up. @ohle Can you reproduce this one? or it's just my configuration problem?
I've temporarily disabled scrolloff if Oni is detected.

I'm also having this problem. Took me a while to find this issue here to see what the problem was. Looking forward to have this fixed.

Put a bounty on this in case someone is interested in checking it out, as it sounds like it is impacting several people:
https://www.bountysource.com/issues/44356173-weird-scrolling-behavior-when-scrolloff-is-set-to-a-non-zero-value
There are a few places to look in terms of investigation:

browser\src\neovim\NeovimInstance.ts - check out the msgpack-rpc messages we receive from Neovim in this scenario
browser\src\Screen.ts - manages the state of the screen, and it can actually be queried at runtime
browser\src\Renderer\CanvasRenderer.ts - if the state of the screen is updating correctly, then it's likely a problem with the render strategy.

I'm going to have a bit of a look into this, and see what is causing it.
From a quick 10 min look, I can see that Oni is receiving the messages for scrolling when moving from line 2 to line 3, that it should be getting at the bottom of the window instead. I'm seeing this in the Session.ts file, so I need to trace that backwards and see if I can find what is causing it to be sent.
From that, it doesn't seem to be a render strategy issue, the renderer is doing exactly what it has been told, its just the instructions are wrong.
I'll keep looking and see if I can work it out, if not then it will have helped me understand the code base a little better.

To bring in some discussion from PR #802:
It looks like the winline() call that is used to update the screen mapping doesn't work well with scrolloff values.
However, as other parts of the code base depend on this call, the fix is more complicated than just removing it.
From @bryphe :

This whole pipeline is pretty hacky and convoluted - really what this is building for us is one function - a function that maps buffer space (like a line and column in a buffer) into screen space - and I suspect there is a way to simplify this without all the back-and-forth events and crazy iteration in init.vim.
I'm trying to explore right now if there is an alternative fix - instead of needing to have this OniUpdateWindowDisplayMap in init.vim, perhaps we can do a pull instead from the Oni side, and based on the info we already have in the event context, and the state of the buffer, maybe we can simplify and build up that bufferSpaceToScreenSpace function. If we go this route, we could get rid of the hacky iteration + winline code that is causing issues with scrolloff (and I suspect it is causing some other problems as well), and have a more robust solution in general.

A solution like this should both make cases like scrolloff work, as well as making the process as a whole more robust and easily debugged, as currently this interaction can only be debugged using the message-pack calls.


platformio run cannot build "desktop" version

end of out is:

Processing desktop (platform: native)
Verbose mode can be enabled via -v, --verbose option
LDF: Library Dependency Finder -> http://bit.ly/configure-pio-ldf
LDF Modes: Finder ~ chain, Compatibility ~ off
Found 2 compatible libraries
Scanning dependencies...
Dependency Graph
|--  2.23.0
Error: Nothing to build. Please put your source code files to '/home/a/bracelets/CovidBracelet/src' folder
============================================================== [FAILED] Took 0.80 seconds ==============================================================
Environment    Status    Duration

nrf52840_dk    SUCCESS   00:00:05.220
desktop        FAILED    00:00:00.797
======================================================== 1 failed, 1 succeeded in 00:00:06.017 ========================================================

@prathje, could you have a look? We need the Desktop mode for testing the Mbed Stuff, correct?

Should be fixed with b99f373 👍


sws-2019-09

cumulative merge of (almost, see below) all currently open PRs
what's not merged yet:
- #1111, #1163 - conflicting commits in BR_EnvelopeUtil.cpp (chunking vs. API), wouldn't want to decide on my own which to merge..
merged #1163 (https://github.com/reaper-oss/sws/pull/1195/commits/8be88b617787e0615ebc31bb638abf7a9483d956)
- #1186 - got merge conflict in SnM_RegionPlaylist.cpp
merged #1186 (https://github.com/reaper-oss/sws/pull/1195/commits/739ab3cb628f2de67aae400f73c41877ac125073)

#1112 - not crucial
#1197

TODO:

bump minimum REAPER version to v5.979 (https://github.com/reaper-oss/sws/pull/1195#issuecomment-531038414)
curate whatsnew.txt

Sure, but how so? You mean opening a PR for it on my repo or should I add you as collaborator?

All collaborators gain write access to submitted pull request's branches when the "Allow edits from maintainers" checkbox is ticked. I can send a PR if you prefer too.

Maybe ~ a month is a bit short for keeping SWS backwards compatibility with older Reaper versions?

Yeah, one month is bit too tight for no real good reason.

I had some conflicts when reverting the chunking in b35a744 which I think came from 24e79b1 which I tried to keep intact, so it would be good if you could look over it.

Looks good to me!

All collaborators gain write access to submitted pull request's branches when the "Allow edits from maintainers" checkbox is ticked. I can send a PR if you prefer too.

Ah, news to me.
I see it's ticked already, so go ahead. :)

Looks good to me!
Thanks for checking. So I'll merge https://github.com/reaper-oss/sws/pull/1163 shortly.

Then I'd also merge #1197 (if it's fine), curating (new word I learned in this context :D) the whatsnew.txt, I could do, and then it should be ready for proposing Time to merge?

@cfillion
Sorry for the confusion.
I merged your PR #1200 before I noticed you have already pushed to this branch.
Then I didn't know how to cleanly reverse it, so I made a hard reset and added your commits as patch again.

Mhh I'm not sure what happened either (I only pushed here once before your merge of 'envelope-tweaks'), but it looks like the merge was successful before the last force-push? You should be able to reset the history to how it was then using git reset --hard  e443823.

You should be able to reset the history to how it was then using git reset --hard e443823.
Done, thanks.
For future, it's fine if you push to it, I just have to remember to check for updates before I do something with it.

I'd like to land a fix for #1189
I'm also currently looking into #1158 and the likely too small envelope buffers used in TrackSends.cpp. I think I can improve thanks to your code snippet from Slack, so no hurry. :)

@cfillion
(almost) ready for contacting Tim for merging?
If you want to look over the whatsnew and change / add something:
https://gist.github.com/nofishonfriday/efc32c9c37953a7ba1abb2701eadddee
version bump (as it's mostly bug fixes):?
#define SWS_VERSION 2,10,1,0
#define SWS_VERSION_STR "2, 10, 1, 0\0"
#define SWS_VERSION_TYPE "Pre-release"
#define SWS_COMMIT "@GIT_COMMIT@"
#define REA_VERSION 5,9,7,9

(almost) ready for contacting Tim for merging?

Yes!
Whatsnew's formatting is looking good (makewhatsnew.exe outputs https://fiddle.jshell.net/dsw2uzyh/show/). Sublists are not parsed but this is not new (a markdown whatsnew could be nice instead of the custom format in the future?)

send envelopes should now be stored/recalled correctly with Snapshots (long standing bug), thogh it hasn't been tested much

Small typo there.

(internal): BR_Envelope::Build(), BR_Envelope::Commit(): revert to using API envelope code (rather than chunking)

I don't think this line is useful to most users (and us devs have the git log for this kind of historical info). The changelog already mentions the only user-visible change earlier (p=2094872) and 2.10.0's changelog only mentionned the fix for #1086.

split the macOS release into 32-bit and 64-bit versions, delete reaper_sws_extension.dylib

Users will see this if they install reaper_sws-x86_64.dylib or reaper_sws-i386.dylib without deleting the old reaper_sws_extension.dylib:

Same on Linux actually (new filenames without an installer to automate the migration).
I think adding a note like this would be helpful:

Update notice: The SWS extension filenames have changed in this release. Linux and macOS users should remove the previous version before installing SWS X.Y.Z.

Speaking of which, the new ARM linux builds should be mentioned (it's also the motivation for the new filenames, since it makes suffixes like "32" or "64" insufficient):

+Added Linux ARM builds (32-bit and 64-bit)

version bump (as it's mostly bug fixes)?

I think calling it 2.11.0 would be worth it. There's more than just backward-compatible bugfixes (just bumping the REAPER version makes it not backward-compatible) and it's not a tiny update after all: 62 commits, 93 files and 3k lines are changing in this PR alone. 😄

done.
If you give 'go' I'd contact Tim! :)


PR  #1796 (React relay variables) introduced a breaking change when validation query variables

I'm kind of new to Flow, and I'm here because the changes introduced in #1796 makes Flow to complain about my code.
I'm using an exact type to validate the myVars key inside my component's state, so I'm checking nothing else is passed as variables for that query, something like this:
type FragmentQueryVariables = {|
  nodeIds: Array<string>,
|};

And here's the full example, using the new Variable and Variables declarations:
type Variable = string | void | number | Variables | void | Array<Variables>;
type Variables = { [string]: Variable } & {$call?: void};

type FragmentQueryVariables = {|
  nodeIds: Array<string>,
|};

const ids: Array<string> = ['some', 'strings'];
const myVars: FragmentQueryVariables = {
  nodeIds: ids,
};
const queryVariables: Variables = myVars;

This gives lots of errors, which I guess boils down to this:
    Type argument `T` is incompatible:
        6:   nodeIds: Array<string>,
                            ^ string. This type is incompatible with
        3: type Variables = { [string]: Variable } & {$call?: void};
                            ^ object type

I tried to "fix" the declaration by adding Array<Variable> but it keeps complaining about the same.
Any pointers? I always though that a stricter type like my exact definition above will fit into something like that Variables declaration... I'm typecasting to any for the time being, but I really prefer not doing that.

@mandx Use // $FlowFixMe instead of any casting. It's better because Flow will tell you once it will be fixed.

@steida Yeah, that makes sense. It does take a bit of refactoring, because // $FlowFixMe statement will affect the next line in its entirety, but that's still better than blindsiding Flow entirely by using any. Thanks!

Check https://github.com/este/este for another inspiration.


Excellent documentation

I'm a fairly experienced Windows and Linux user, and this documentation, explaining how to install nvm, nodejs and npm was outstanding. I love how the links go right where they should. It was easy to read through the text, clicking the appropriate link, running the appropriate command and so on. There were no hiccups or snags. Absolutely wonderful!
Thank you,
--dang

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

ID: c6995595-66c4-f26a-b307-89a068b4b5ba
Version Independent ID: 69400ed1-5d98-4d6e-47a3-5c409564e77d
Content: Set up NodeJS on WSL 2
Content Source: hub/nodejs/setup-on-wsl2.md
Product: dev-environment
Technology: windows-nodejs
GitHub Login: @mattwojo
Microsoft Alias: mattwoj

Wow! Thank you so much @gotdang. We don't get very many of these sort of encouragement issues being filed and it's much appreciated. I hope that I can continue to offer this sort of value in the upcoming articles I'm working on. (Currently an expansion of the Docker tutorial as that's already growing outdated).


A pathway that aligns with RISP, Research & Impact Support Portal

So this might be too big to be a pathway, but it is good to think of how to approach it. There is a central  vu portal which connects to our resources.
It has a somewhat chronological structure which might be good to reflect somewhere - in case people come to us from the portal they might appreciate this familiarity

Given that this stems from our "pathway" days and has not seen any further activity, I will close this issue for now 👍 Please feel free to open up a new issue if this has relevance, with an update to the current context.

After having a meeting with @Jolien-S and @Alex-van-der-Jagt, I want to re-open the issue. We have a feeling that from a user perspective (a user being a researcher who is not involved in content creation, for example a PhD student who is just starting) the handbook still needs some overview that will have some kind of timeline structure. The research data life cycle was mentioned as providing an overview. We don't know if RISP (vu portal) is the best structure, but it seems better than nothing and it connects the handbook with other VU website resources. We don't know exactly how to move on from this, maybe make a guide with the timeline structure in it? We also have a feeling that the landing page is now doing a good job in addressing contributors but might lack oveview for user just looking for some general RDM information


Immediate failure on transaction use

This code:
return conn.transaction(on: .mysql) { txn in
  return MyObject.query(on: txn).all()
}

throws this error:
NIO-ELT-#1 (2): Fatal error: Attempting to call `send(...)` while handler is still: callback(NIO.EventLoopPromise<()>(futureResult: NIO.EventLoopFuture<()>), (Function)).

on MySQL database version 5.7, using Vapor 3.1.0, Fluent 3.1.2, FluentMySQL 3.0.1.
The same code executed without transactions works fine.

I aggrieved that is reproducing, but I am thinking it depended on MySQL lib (tested on 3.2.4)
My case is better:
We has 2 async query in the transaction and one should throw error.
Example:
`
return request.transaction(on: .mysql) { (connect) -> Future in
let userFuture : Future = UserEntity.find(updateUserId, on: connect).map { entity in
throw Abort(.forbidden, reason: "You have not access")
}
let userPersonalFuture : Future = UserPersonalEntity.find(currentUser.userId, on: connect).map {}
return [userFuture, userPersonalFuture].flattern(on: connect).map {
return SuccessResponse()
}
}
`
That generated:
Fatal error: Attempting to callsend(...)while handler is still: callback(NIO.EventLoopPromise<()>(futureResult: NIO.EventLoopFuture<()>), (Function)).: file /.build/checkouts/mysql/Sources/MySQL/Connection/MySQLConnection.swift, line 81
If would removed request.transaction and use request without connect then it works is fine

Also experiencing this error. Effectively we can't use transactions with MySQL in Vapor?

This limitation has been lifted in the latest version of the driver (4.0.0) as MySQLConnection now supports queueing up multiple queries.


Hugo Installer causing error

Description
I'm getting a command failed error for command C:\Windows\system32\cmd.exe /d /s /c hugo-installer --version otherDependencies.hugo --extended --destination node_modules/.bin/hugo. It says Invalid values:, Argument: arch, Given: "ia32", Choices: "arm", "arm64", "x64", "x86".
Steps to Reproduce
This happens on my Windows 10. I think it should happen on other people's Windows 10 as well. I have tried to run the npm create hyas@latest -- --template doks command on WSL, but it doesn't work either. I get this on WSL: CMD.EXE was started with the above path as the current directory. UNC paths are not supported. Defaulting to Windows directory.
Expected Result
Dependencies should have installed without error.
Actual Result
I got an error.
Environment
><EMAIL_ADDRESS>preinfo
> npm version

{
  'hyas-project': '0.0.0',
  npm: '10.4.0',
  node: '20.11.0',
  acorn: '8.11.2',
  ada: '2.7.4',
  ares: '1.20.1',
  base64: '0.5.1',
  brotli: '1.0.9',
  cjs_module_lexer: '1.2.2',
  cldr: '43.1',
  icu: '73.2',
  llhttp: '8.1.1',
  modules: '115',
  napi: '9',
  nghttp2: '1.58.0',
  nghttp3: '0.7.0',
  ngtcp2: '0.8.1',
  openssl: '3.0.12+quic',
  simdutf: '4.0.4',
  tz: '2023c',
  undici: '5.27.2',
  unicode: '15.0',
  uv: '1.46.0',
  uvwasi: '0.0.19',
  v8: '<IP_ADDRESS>-node.17',
  zlib: '<IP_ADDRESS>-motley-5daffc7'
}

><EMAIL_ADDRESS>info
> npm list

npm ERR! code ELSPROBLEMS
npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS><EMAIL_ADDRESS>C:\Users\Chandan\Documents\hyas-project
├── UNMET DEPENDENCY<EMAIL_ADDRESS>├── UNMET DEPENDENCY<EMAIL_ADDRESS>├── UNMET DEPENDENCY<EMAIL_ADDRESS>├── UNMET DEPENDENCY<EMAIL_ADDRESS>├── UNMET DEPENDENCY<EMAIL_ADDRESS>├── UNMET DEPENDENCY<EMAIL_ADDRESS>├── UNMET DEPENDENCY<EMAIL_ADDRESS>├── UNMET DEPENDENCY<EMAIL_ADDRESS>└── UNMET DEPENDENCY<EMAIL_ADDRESS>

I cannot reproduce your issue on Windows 11 Pro (Node v20.11.0 and npm 10.2.4) and with WSL (Node v20.11.1 and npm 10.2.4)
What you could try:

delete package-lock.json and the node_modules directory — then run npm i again
use npm 10.2.4

Has anyone else stumbled upon this issue?
If this doesn't help, maybe it's a good idea to raise an issue: dominique-mueller/hugo-installer
BTW) In the upcoming Hyas 2.3 release — available soon — hugo-installer will be dropped. Then you will need to use your own (global) Hugo install


HA 2024.8.1 & ge_home -> won't initialize

Fresh HA install on unraid via docker.  Created the custom_components folder and copied ge_home to it, relaunched HA and went to add the integration per the instructions.  This is the error I get and I don't see anything in the logs for why this would have happened:
Config flow could not be loaded: {"message":"Invalid handler specified"}

Was able to replicate. Running HA on Debian via Docker.
Config flow could not be loaded: {"message":"Invalid handler specified"}

I'm running on Ubuntu via Docker and saw this though I had used the UI to reboot HA. To solve this, i restarted the docker container, upon which adding the integration no longer threw that error message.

Yep, can confirm a restart fixes it.


mkosi: 20.1 -> 20.2

Description of changes
Changelog: https://github.com/systemd/mkosi/releases/tag/v20.2
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
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 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.

Result of nixpkgs-review pr 283108 run on x86_64-linux 1

6 packages built:

mkosi
mkosi-full
mkosi-full.dist
mkosi-full.man
mkosi.dist
mkosi.man

Looks good! Could you also apply this patch: https://github.com/systemd/mkosi/pull/2315 ?
It seems to fix the mkosi-chroot command during the build, since NixOS is technically an "unmerged-usr" distribution.


R5D, T3, u-*.metal, F1, z1d, etc should all have enhanced networking as per:
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/enhanced-networking.html
It seems like the data source might be inconsistent, for example A1 instances are marked as having enhanced networking, so it doesn't seem like it's related to new instance types specifically.

Yeah, the data source just doesn't return that info. It seems like it's missing some instances. Here's a list of instances that the API returns with enhanced networking enabled in N. Virginia: a1,c3,c4,c5,c5d,c5n,d2,g3,h1,i2,i3,m4,m5,m5a,m5d,p2,p3,p3dn,r3,r4,r5a,x1,x1e
Since it returns both ENA and VF instances I think they just forgot about something.

Applies to the g4dn instances as well. #469

Fixed by https://github.com/powdahound/ec2instances.info/pull/490


etcdmain: database file does not match with snapshot

Hello,
We use a kubernetes cluster with 3 or 2 etcds and we see that sometime one of the etcd member goes into the below issue:
we see the issue that the etcd can't speak with his cluster members anymore. because his data is inconsistent or differs from the other nodes in the cluster.
You see following error message
2017-12-01 10:10:01.168631 I | etcdserver: recovered store from snapshot at index 3426537
2017-12-01 10:10:01.168656 I | etcdserver: name = etcd1
2017-12-01 10:10:01.168660 I | etcdserver: data dir = /var/lib/etcd/data
2017-12-01 10:10:01.168666 I | etcdserver: member dir = /var/lib/etcd/data/member
2017-12-01 10:10:01.168670 I | etcdserver: dedicated WAL dir = /var/lib/etcd/wal
2017-12-01 10:10:01.168673 I | etcdserver: heartbeat = 100ms
2017-12-01 10:10:01.168676 I | etcdserver: election = 1000ms
2017-12-01 10:10:01.168679 I | etcdserver: snapshot count = 10000
2017-12-01 10:10:01.168690 I | etcdserver: advertise client URLs = http://<IP_ADDRESS>:2379
2017-12-01 10:10:01.168789 W | wal: ignored file<PHONE_NUMBER>000075-00000000003012ad.wal.broken in wal
2017-12-01 10:10:01.168799 W | wal: ignored file<PHONE_NUMBER>000076-0000000000311951.wal.broken in wal
2017-12-01 10:10:01.168806 W | wal: ignored file<PHONE_NUMBER>000077-0000000000320994.wal.broken in wal
2017-12-01 10:10:01.168813 W | wal: ignored file<PHONE_NUMBER>000078-0000000000330637.wal.broken in wal
2017-12-01 10:10:01.522668 I | etcdserver: restarting member b7ac64605e023502 in cluster<PHONE_NUMBER>a07674 at commit index 3445035
017-12-01 10:10:01.527818 C | raft: b7ac64605e023502 state.commit 3445035 is out of range [3426537, 3428606]
panic: b7ac64605e023502 state.commit 3445035 is out of range [3426537, 3428606]
We can see in the ectdctl logs the below message
etcdmain: database file (/var/lib/etcd/data/member/snap/db index 137632097) does not match with snapshot (index 137648093)
What we do as work around is to disable the puppet agent there, change the initial state in etcd.yaml from new to existing and then clean up the data folder.
Then the etcd pod that shows the issue is deleted and we find the node is back with no issues.
Please let me know if this is fixed in any upcoming versions or any other solution to find a better solution ?
The version we use is:
etcdctl --version
etcdctl version: 3.1.10
API version: 2
curl -L http://<IP_ADDRESS>:2379/version
{"etcdserver":"3.2.11","etcdcluster":"3.2.0"}
Kubernetes version : v1.5.7

Hello,
We use a kubernetes cluster with 3 or 2 etcds and we see that sometime one of the etcd member goes into the below issue:
we see the issue that the etcd can't speak with his cluster members anymore. because his data is inconsistent or differs from the other nodes in the cluster.
You see following error message
2017-12-01 10:10:01.168631 I | etcdserver: recovered store from snapshot at index 3426537
2017-12-01 10:10:01.168656 I | etcdserver: name = etcd1
2017-12-01 10:10:01.168660 I | etcdserver: data dir = /var/lib/etcd/data
2017-12-01 10:10:01.168666 I | etcdserver: member dir = /var/lib/etcd/data/member
2017-12-01 10:10:01.168670 I | etcdserver: dedicated WAL dir = /var/lib/etcd/wal
2017-12-01 10:10:01.168673 I | etcdserver: heartbeat = 100ms
2017-12-01 10:10:01.168676 I | etcdserver: election = 1000ms
2017-12-01 10:10:01.168679 I | etcdserver: snapshot count = 10000
2017-12-01 10:10:01.168690 I | etcdserver: advertise client URLs = http://<IP_ADDRESS>:2379
2017-12-01 10:10:01.168789 W | wal: ignored file<PHONE_NUMBER>000075-00000000003012ad.wal.broken in wal
2017-12-01 10:10:01.168799 W | wal: ignored file<PHONE_NUMBER>000076-0000000000311951.wal.broken in wal
2017-12-01 10:10:01.168806 W | wal: ignored file<PHONE_NUMBER>000077-0000000000320994.wal.broken in wal
2017-12-01 10:10:01.168813 W | wal: ignored file<PHONE_NUMBER>000078-0000000000330637.wal.broken in wal
2017-12-01 10:10:01.522668 I | etcdserver: restarting member b7ac64605e023502 in cluster<PHONE_NUMBER>a07674 at commit index 3445035
017-12-01 10:10:01.527818 C | raft: b7ac64605e023502 state.commit 3445035 is out of range [3426537, 3428606]
panic: b7ac64605e023502 state.commit 3445035 is out of range [3426537, 3428606]
We can see in the ectdctl logs the below message
etcdmain: database file (/var/lib/etcd/data/member/snap/db index 137632097) does not match with snapshot (index 137648093)
What we do as work around is to disable the puppet agent there, change the initial state in etcd.yaml from new to existing and then clean up the data folder.
Then the etcd pod that shows the issue is deleted and we find the node is back with no issues.
Please let me know if this is fixed in any upcoming versions or any other solution to find a better solution ?
The version we use is:
etcdctl --version
etcdctl version: 3.1.10
API version: 2
Kubernetes version : v1.5.7

Hi @chaithramohan would you mind updating your title to something a little more meaningful so others can reference. Maybe etcdmain: database file does not match with snapshot Also, you could consolidate these two messages here. Thank you!

@hexfusion done

it is probably caused by the broken wal files. do you know how the wal files got broken at the first place? did the machine experience any disk issues?

Also are you able to reproduce this problem? If not, are you willing to share your broken data dir for us to investigate?

Not able to reproduce the problem, did not face the issue yet again after that to share the data file as well but wanted to know if there is any fix in any upcoming release or is there a way to automatically handle such a failure ??

I am not sure what is the root cause, so I cannot provide you the answer.
On Fri, Dec 15, 2017 at 5:56 PM chaithramohan<EMAIL_ADDRESS>wrote:

Not able to reproduce the problem, did not face the issue yet again after
that to share the data file as well but wanted to know if there is any fix
in any upcoming release or is there a way to automatically handle such a
failure ??
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/coreos/etcd/issues/9021#issuecomment-352152267, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AERbyxBqttZOfZV6CKnFs9KusOrZB8WEks5tAyNmgaJpZM4RDOLV
.

okay, i will try getting more details once i get hold of them. In the meanwhile with regard to a similar issue (https://github.com/coreos/etcd/issues/8935), some investigation was going on in
"I will be surprised that etcd 3.1.11 fixes the root cause. I feel the root cause is somewhere in raft pkg, and it is a pretty subtle one.
We probably should still spend sometime to understand why it happens under 3.0.10, and if 3.1.x fixes it which commit exactly fixed it "
This problem had occured when we used v3.1.5 and now its like about 2 days we upgraded to 3.2.11. Is there a possibility with regard to the above comment that 3.1.11 fixes it or any investigation in that regard ?

That is a different issue. That cluster has no broken wal files.
On Fri, Dec 15, 2017 at 6:01 PM chaithramohan<EMAIL_ADDRESS>wrote:

okay, i will try getting more details once i get hold of them. In the
meanwhile with regard to a similar issue (#8935
https://github.com/coreos/etcd/issues/8935), some investigation was
going on in
"I will be surprised that etcd 3.1.11 fixes the root cause. I feel the
root cause is somewhere in raft pkg, and it is a pretty subtle one.
We probably should still spend sometime to understand why it happens under
3.0.10, and if 3.1.x fixes it which commit exactly fixed it "
This problem had occured when we used v3.1.5 and now its like about 2 days
we upgraded to 3.2.11. Is there a possibility with regard to the above
comment that 3.1.11 fixes it or any investigation in that regard ?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/coreos/etcd/issues/9021#issuecomment-352152644, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AERbyxIrZNLLOTJbDz0yMBXsyxhabfcbks5tAySHgaJpZM4RDOLV
.

Okay i am not yet sure if we can reproduce the issue, if yes i shall share more details.
Can you please suggest any solution to avoid broken wal files (incase this issue comes because of that) ?


improve caching in LinkedDataSource

Problem: the CachingLinkedDataSource does not respect ETAG or Expires headers. Currently this implmentation will not update LDP collections once they have been retrieved. We need to re-implement its behaviour and add Expires and headers and ETag handling on both client and server so as to make efficient and correct communication possible.

approach:

add request and response headers to the linkedDataRestClient
implement simple cache control

do not cache resources that don't want caching (Date header equals Expires header)
add expires-immediately headers to mutable resources and never-expires to immutable resources

implement ETAG-based cache control

add ETAG support to client: store ETAG header value with resource and send If-Modified-None header when fetching
. add ETAG header handling to resources that are cachable but are not immutable


[Feature]:  Dark mode is not enable after clicking on toggle button.

Hey @skmirajulislam  I want to fix the issue of toggle button and also make some changes in navigation bar.
Navigation icons are not properly visible.

Could you assign me this task, so that I can start working on it.
Please make sure to add labels gssoc-ext, hactoberfest, level1, level2, level3.

I have fixed this issue and now you can use this toggle button. I have requested to apply changes what i have done through pull request.


How to create a node

Is it possible to create a node?

Yes. Use controlled props like you would modify state for any component in react.
This issue doesn’t have enough information and we don’t typically answer stack overflow style questions. Closing.


First time you click the sync icon on a sync dataset from the datasets view js error is happening

the second time it works as expected
Uncaught Error: TrackJS Caught: Cannot read property 'from_external_source' of undefined

I won't trigger the sync event in this case. Should I change the style of the icon or show a different tooltip?


Prepare static content during regular pip install

Right now, the equivalent of setup.py css and setup.py js is not run by default.

make install does it


Rewrite in TypeScript

Being a very small codebase, this is a good candidate to try TS out.

Will probably follow the Skate core convention here. Will reopen if necessary.


Adding simple icmp-responder example

Your title is quite straightforward, but what is missing anywhere in the commit or comment is 'why would I need a simple ICMP responder'?

I've moved the nse to an examples directory to help make it obvious that this isn't a core component. Thanks for the feedback!


Updated prometheus src url

Since version 2.17.2 no longer has the latest tag on Github, the url returns a 404.
TASK [monitoring_server : Install prometheus] ********************************************************************
fatal: [pistack0]: FAILED! => {"changed": false, "msg": "Failure downloading https://github.com/prometheus/prometheus/releases/latest/download/prometheus-2.17.2.linux-armv7.tar.gz, HTTP Error 404: Not Found"}

I got the URL structure from here https://github.com/prometheus/prometheus/releases/tag/v2.17.2
Had to make this change to get the playbook to execute all the way through.
ps. thanks for this repo, great work!

Since version 2.17.2 no longer has the latest tag on Github, the url returns a 404.
TASK [monitoring_server : Install prometheus] ********************************************************************
fatal: [pistack0]: FAILED! => {"changed": false, "msg": "Failure downloading https://github.com/prometheus/prometheus/releases/latest/download/prometheus-2.17.2.linux-armv7.tar.gz, HTTP Error 404: Not Found"}

I got the URL structure from here https://github.com/prometheus/prometheus/releases/tag/v2.17.2
Had to make this change to get the playbook to execute all the way through.
ps. thanks for this repo, great work!

Thank you @justinschuldt! It really didn't make sense to reference ../latest/.../...{{ version }}..., good catch.


Pagination with Continuation Token Support

WIP at the minute just to gather some feedback.
Closes #53.

I have opened an issue to get some help on the issue we are facing at the minute: https://github.com/Azure/azure-cosmos-dotnet-v3/issues/2657

Hey, @zhangzunke I wanted to make sure that you saw this effort. Any thoughts on this implementation?

@dcuccia @bradwestness Sorry guys mind taking a look at this?

Hey @mumby0168 did you received some answer from Azure about the issue?

Hey @mumby0168 did you received some answer from Azure about the issue?

Hi no not yet, going to chase them, their is an issue open on GitHub & I have a ticket raised via my company. Will update on here when I hear back.

Hey guys @IEvangelist @dcuccia @joemersonsouza so we have had a reply back from the cosmos team see https://github.com/Azure/azure-cosmos-dotnet-v3/issues/2657#issuecomment-902897257
So it appears if you are to skip and get a continuation token then the next query must match exactly i.e. also including the original skip. We can incorporate this inside our library. It may add complications.
The 3 queries I wanted to support for paging aimed to meet the given scenarios.
CT -> (Contiuation Tokens)

A user starts at page 1 and then cycles page 1,2,3 .... in order (this can make use of CT)
A user wants to jump to a page say 4 and then cycle 5,6,7 in order again can use a CT but must know about the original skip.

Whether we support the second case is up for discussion? This would not support traditional paging but could be great for supporting a load more ... scenario.
I would really appreciate some feedback/help on what we think this should support. Obviously, CT provides a much more cost-effective way to page through data but also could potentially limit a user's experience. Definitely up for debate.

@mumby0168 thanks for the follow-up. Could we support both scenarios, but somehow unify the experience by returning an IAsyncEnumerable<IPage>? Or, if that's the API, then does it mean we can remove the second one altogether, since the caller will have control over the "load more" iteration? Armchair development, so caveat emptor...

@mumby0168 thanks for the follow-up. Could we support both scenarios, but somehow unify the experience by returning an IAsyncEnumerable<IPage>? Or, if that's the API, then does it mean we can remove the second one altogether, since the caller will have control over the "load more" iteration? Armchair development, so caveat emptor...

Yeah maybe so, it depends how we want to support it, I have been coming at this from the point of view that a user is on a screen look at a blog. They are on the first page and want to view the next. This would then come in two separate requests more than likely an API. I thought about IAsyncEnumerable<T> but would that work well for a scenario such as above? Not really worked with it too often so that is a limited view.
I suppose we may just have to rely on the caller knowing a bit about what is going on, matching a skip up would not be to hard, but then if this is on top of an OrderBy(x => ...) for example the problem grows 🤔

Part of me is thinking about closing this PR for now. Maybe opening up a new discussion section around the design of this. But at the same time this is something I would love to see soon 👀

My thought is that if we expose the async iterator, then we can encapsulate the complexity and keep the CT knowledge behind the scenes. Leaving open for more comments/thoughts is fine with me. I may have a little time to play with the iterator concept.

My thought is that if we expose the async iterator, then we can encapsulate the complexity and keep the CT knowledge behind the scenes. Leaving open for more comments/thoughts is fine with me. I may have a little time to play with the iterator concept.

Yeah that would be great to see! No reason we could not offer two options ... is there?

@mumby0168 I think we might be able to offer both via a single API. Check out what I just pushed - does this cover our needs? Using the .FirstAsync() extension for the case where you "just want one page", but that would usually be the exception. The requirement for that case is that the consumer pull in System.Linq.Async, which is currently not shipped with the SDK (but I imagine it will be soon).

@mumby0168 reading back, I finally understand what you mean about the separate-call API scenario. I don't know how to resolve that one as elegantly...maybe this is the minimum viable approach? Not worth it if it doesn't solve a major use case, though.

Maybe there's a state machine we can expose on top of the IAsyncEnumerable. Our own continuation async iterator...

Hey @dcuccia I think the push you made looks really cool and certainly would be good to add as an extra option to the API! I think this paging issue might need more discussion what does everyone think about putting something in the calendar to go and discuss this and decide our approaches? @IEvangelist @bradwestness and anyone else who would like to discuss?

@IEvangelist what about offering a continuation token paging option, an IAsyncEnumerable option like @dcuccia suggested and then just expose the Container via the IRepository<T> if a client wants to handle this them selves? Really struggling to decide here 🤦♂

Hey guys, do you have some news about this feature?

Hi @joemersonsouza we are in two minds with it, what would you like to see and what are your requirements for paging if you don't mind?

I am going to close this PR it is worth refereeing back to I think but we have some discussions set up on how to go about this further in the next few weeks. Hopefully, after that, we can have a plan of attack on how to implement this correctly.
Thanks, everyone for the discussions/contributions to this so far.


Two issues

The plugin is excellent. However, I'm having the following problem:
As a rule, it saves the file in the following location: Attachments/Diagram.svg
However, it creates the "Attachments" folder in the root and not inside the current folder (where the note is being prepared).
Also, it always saves as "Diagram.svg" causing the files to overlap. Ideally, by default, the plugin would automatically increment the name. Example: Diagram1.svg, Diagram2.svg, Diagram3.svg, Diagram4.svg, etc.
Therefore, I kindly request two updates:

The possibility of configuring the plugin so that the attachment is included within the folder where the note is inserted and not in the root folder;

That the diagram is saved with automatic name increment or that the inclusion of a specific name by the user is mandatory, avoiding conflict between two files with the same name.

Thank you very much. The Plugin is a 10!

Thanks for the comment!
Regarding your points:

I understand this request, and will look into adding this setting for a future version.
It is allready default behaviour for the plugin to increment names (it uses the obsidian API vault.getAvailablePathForAttachments function, which increments names if necessary). If you experience that this is not the case that is a bug I'm not able to reproduce. What version of obsidian on what system are you using?)


Debugging support for tests

Added a gulp task for running / debugging unit tests. In the gulp pane in Webstorm right-click test and select Debug 'test'. This should respond to any breakpoints set.

Coverage remained the same at 93.815% when pulling 1d56441918f9137706d8ed5050a0e98fab7d8f3c on test-debugging into 8a6f4bb140245235571213b077f83057ce163187 on master.

@lasalvavida Could you quickly take a look at this?

Tried it and it works, should be good.

Please update README.md with any instructions.  As build/debug/test/etc instructions grow, we'll move them from README.md to their own guide like Cesium.


Question About AD-PT

I would like to ask a question about the AD-PT paper. In the AD-PT paper, when using only 20% of the kitti dataset, it showed a significant performance improvement in the SECOND model. However, when I used the SECOND-IOU model using the ONCE 1M provided as a backbone pretrain model, it showed -1.7mAP performance when using AD-PT. I would like to ask if you can release the imageset of the data when using 20% of the kitti.

Hello, there is the 20% kitti info.https://drive.google.com/file/d/1-T2Icy_S8OvV-8Y_8ihCQFjjeHghaRs-/view?usp=sharing
Also, are you loading parameters from our pre-trained checkpoint correctly? The BACKBONE_3D of our pre-training model is "VoxelResBackBone8x", so it should also be aligned in the config of SECOND-IOU and SECOND.


Don't write to AzureDataTables

Description
I have tried to write to AzureDataTables with a base example (see attached) without luck.
I have tried several combinations, I have noticed that if the table does not exist it will create it and write once if I stop the program and re-run the message is not written.
If the table already exists it never writes to it.
I have attached a small console app following the Nlog official .Net Core app
Environment
Windows 10 Pro
netcoreapp3.1
Attachments
TestAzure.zip

Can you include the output from the NLog InternalLogger: https://github.com/NLog/NLog/wiki/Internal-Logging

Below are the files requested.
internal-nlog.table.exists.txt
internal-nlog.table.notexisits.txt

Very strange. There are no errors.
internal-nlog.table.notexisits.txt says this:
2021-09-30 21:08:00.1656 Trace AzureTableStorageTarget(Name=azure): Requested Table Name: Foo
2021-09-30 21:08:00.5803 Debug AzureTableStorageTarget: Created table: Foo
internal-nlog.table.exists.txt says this:
2021-09-30 21:08:31.3233 Trace AzureTableStorageTarget(Name=azure): Requested Table Name: Foo
Curious if there is some flush/close-logic that needs to be improved. What happens if you run the application, and wait 30-60 secs before you Press ANY key to exit

You can also try to setup a AzureEventSourceListener that writes to console, and see if something is failing:
// Setup a listener to monitor logged events.
using AzureEventSourceListener listener = AzureEventSourceListener.CreateConsoleLogger();

See also: https://docs.microsoft.com/en-us/dotnet/api/overview/azure/data.tables-readme

Have also made a pull-request to improve the diagnostic logging in the AzureDataTables-NLog-target. See also: #111
You can download the pre-release nuget-package, and check if it gives some extra output:
https://ci.appveyor.com/api/buildjobs/yn8g4iq3rm8by8ln/artifacts/src%2FNLog.Extensions.AzureDataTables%2Fbin%2FRelease%2FNLog.Extensions.AzureDataTables.3.1.0.snupkg

I've tried to:

Wait 60 seconds (no effect)
Added the AzureEventSourceListener it issue an error 409 Conflict, below the entire log

2021-10-01 09:48:53.4700||DEBUG|TestAzure.Runner|Doing hard work! Action1|
Press ANY key to exit
[Informational] Azure-Core: Request [9b3b5712-88b8-45ab-80cf-eda8901ef7e5] POST https://xxxx.table.core.windows.net/Tables?$format=REDACTED
x-ms-version:REDACTED
DataServiceVersion:3.0
Accept:application/json; odata=minimalmetadata
x-ms-client-request-id:9b3b5712-88b8-45ab-80cf-eda8901ef7e5
x-ms-return-client-request-id:true
User-Agent:azsdk-net-Data.Tables/12.1.0,(.NET Core 3.1.19; Microsoft Windows 10.0.19043)
x-ms-date:REDACTED
Authorization:REDACTED
Content-Type:application/json; odata=nometadata
client assembly: Azure.Data.Tables
[Warning] Azure-Core: Error response [9b3b5712-88b8-45ab-80cf-eda8901ef7e5] 409 Conflict (00.4s)
Cache-Control:no-cache
Transfer-Encoding:chunked
Server:Windows-Azure-Table/1.0,Microsoft-HTTPAPI/2.0
x-ms-request-id:e343fd6f-f002-0023-5e98-b6afa7000000
x-ms-client-request-id:9b3b5712-88b8-45ab-80cf-eda8901ef7e5
x-ms-version:REDACTED
X-Content-Type-Options:REDACTED
Date:Fri, 01 Oct 2021 07:48:55 GMT
Content-Type:application/json; odata=minimalmetadata; streaming=true; charset=utf-8

I can't install the 3.1.0 version because the nuget raise an error, I have tried also with net5.0

dotnet add package nlog.extensions.azuredatatables -v 3.1.0
  Determining projects to restore...
  Writing C:\Users\massimo\AppData\Local\Temp\tmp6CC6.tmp
info : Adding PackageReference for package 'nlog.extensions.azuredatatables' into project 'D:\Temp\AzureDataTables\TestAzure\TestAzure.csproj'.
info : Restoring packages for D:\Temp\AzureDataTables\TestAzure\TestAzure.csproj...
error: NU1202: Package NLog.Extensions.AzureDataTables 3.1.0 is not compatible withnetcoreapp3.1 (.NETCoreApp,Version=v3.1). Package NLog.Extensions.AzureDataTables 3.1.0 does not support any target frameworks.
error: Package 'nlog.extensions.azuredatatables' is incompatible with 'all' frameworks in project 'D:\Temp\AzureDataTables\TestAzure\TestAzure.csproj'.

I have created a nuget.config pointing to local directory, and "pushed" your package.
<?xml version="1.0" encoding="utf-8"?>
<configuration>
    <packageSources>
        <add key="MyLocalSharedSource" value="d:\packages" />
    </packageSources>
</configuration>

Pushed with command
nuget add D:\NLog.Extensions.AzureDataTables.3.1.0.snupkg -source d:\packages
Do you have somewhere the updated source code (I can't find any branches on your git repo), I can try to add to my project and debug.

@m4ss1m0g Thank you for debugging this, and making a fix. Would be nice that it actually failed with an exception, instead of just silently doing nothing.

Created https://github.com/Azure/azure-sdk-for-net/issues/24378 for Microsoftt

@m4ss1m0g Guess the issue can be closed as resolved with https://www.nuget.org/packages/NLog.Extensions.AzureDataTables/3.1.0


Modify LDMatrix to allow for reordering/sorting LD matrices

There are cases where we would like to re-order the LD matrix by shuffling its rows and columns to align with some external requirements. This task is challenging to implement, because it will likely mess up with the LD boundaries and affect the sparsity structure of the original matrix.
As a starting point, we can limit ourselves to solutions that do not necessarily re-order the matrix itself, but affect the order in which we iterate over its rows/columns. This may require that instead of storing LD boundaries (start and end point for each row), we can store the indices of all neighboring SNPs whose LD is non-zero. This is similar to the sparse matrix formats implemented by scipy and other libraries.
Will keep this issue open to explore various ideas for how we can go about implementing this.

New interface should easily support this.


add new keywords

Hey, thanks for the contribution, I didn't see it before pushing 75c056b, will close this but thanks for taking the time.


Setting of window title seems to break with tmux 2.7 on OS X

My homebrew recently updated tmux to version 2.7. Since then, the tmux window title does not get set at all, no errors, just nothing happens it stays at 'zsh'. After switching back to 2.6, it works as expected.

This has to do with the default value of allow-rename configuration setting having been changed to off in tmux version 2.7.


Button update

Simplifying button styles as requested
https://trello.com/c/zIxOb1y9/556-styleguide-button-style-clean-up
BREAKING CHANGE:
Button now will no longer do anything with the following props:
-Inverse
-Fullwidth
-Ghost
-Loading
Button colors can now only take the following values:
-callToAction
-primary
-secondary
-hyperlink

@mengtzu @manthachan Would any of you guys mind giving another look? I just changed the demo page


Resolve Apache Conscious Language Checker findings

Change references to Daffodil "main" branch
Fix test quotes/strings and typos to avoid false positives
Links to 3rd party repos are changed to 'main' where possible, or to a
commit hash or tag where not, again to minimize false positives

Findings that are not resolved:

Dependency license text that contains "his or her"--we probably
shouldn't modify text from other licenses
False positive found in "Saxon-HE" dependency

DAFFODIL-2557

Should we amend this PR's commit message to include those instructions as well?
The default branch has been renamed! The master branch is now named main.
If you have a local clone, you can update it by running:
git branch -m master main
git fetch origin
git branch -u origin/main main
git remote set-head origin -a

Seems reasonable. Will update with instructions.


VirtualizedPropertyGrid minimizes down to one line when its height is changed

Describe the bug
After changing from using PropertyGrid to VirtualizedPropertyGridWithDataProvider, I discovered that every time the element containing the VirtualizedPropertyGridWithDataProvider changes height (thus passing a new value for the height prop), the grid minimizes down to only showing the top line. ProperyGrid did not do this when its panel had a height change.
My property grid does not specify orientation, but I tested setting that to Orientation.Horizontal, and it did not fix the problem. Additionally, when I specify a new width for the property grid, the problem does not occur.
To Reproduce
Steps to reproduce the behavior:

Include a VirtualizedPropertyGridWithDataProvider in your UI.
Select an element to display in the property grid.
Tap on the only visible line ("Selected Item(s)") to expand it.
Change the height prop being passed into the property grid.

Expected behavior
The property grid should resize to reflect the new height, but it should not minimize down to only showing the "Selected Item(s)" line.
Screenshots
Before height change:

After height change:

Desktop (please complete the applicable information):

OS: iOS
Browser: Safari WKWebView inside native app
Version: 16.3.1
iTwin.js Version: 3.6.1

Additional context
This happens inside a native iOS mobile app. I assume it will also happen in a browser-based desktop or mobile app, but I have not tested that. The app in question is the sample app for the iTwin Mobile SDK. I have not yet pushed the changes to that app to use VirtualizedPropertyGridWithDataProvider, but I will be doing so shortly. One that happens, my actual code will be here.

@tcobbs-bentley, have you tried to reproduce this in a sandbox?

No.

@grigasp I've never made a sandbox before, so I don't know what is needed to share them with others if they are not automatically shared. I created a sandbox here:
https://www.itwinjs.org/sandbox/TravisCobbs/Element Properties
Instructions for sandbox:

Resize the bottom panel to be taller (not necessary, but helpful).
Select an element.
Expand the property grid so it is visible.
Hit the "Press me" button.

The sandbox recreates the data provider on each component rerender (e.g. when size changes), which in turn causes a complete rerender of the property grid, dropping any categories' state. Using React.useMemo to memoize the provider should solve the problem.

The sandbox I created created the data provider in a different location than the iTwin Mobile sample app, but adding useMemo to the mobile sample did indeed fix the problem. I apologize for the false alarm.


Detect API Gateway errors

Description
When using the "Lambda Proxy Integration" of AWS API Gateway, the lambda must return a response per this document: https://docs.aws.amazon.com/apigateway/latest/developerguide/set-up-lambda-proxy-integrations.html#api-gateway-simple-proxy-for-lambda-output-format
So instead of throwing an error or calling context.fail(err); our lambdas return a response like:
exports.handler = async (event, context) => {
try {
   <code here throws exception>
  } catch (err) {
    logger.error('------ There was an error');
    logger.error(err);

    response.statusCode = HttpStatus.INTERNAL_SERVER_ERROR;
    response.body = 'There was an error';

    return response;
  }
}

Unfortunately, iopipe reports errors in our process as successful transactions as it is expecting to trap an error or for context.fail(err); to be thrown.
Steps to reproduce the issue:

Create a lambda and an API gateway endpoint using "Lambda Proxy Integration"
Have the lambda send a properly formatted API Gateway reponse
Check iopipe dashboard for errors

Describe the results you received:
While the transactions appear in iopipe, they are not recognized as errors.
Describe the results you expected:
I would like to see them as errors.
p.s. I have filed issues in other iopipe repos but I will close them if needed
Additional information you deem important (e.g. issue happens only occasionally):

I put together an idea on how you might address this:
https://github.com/jeffggardner/iopipe-js-core/tree/fix-347

@jeffggardner Great--thanks for supplying this! Would you mind making it a PR against this repo?
The only thing that jumps out as a potential integration issue is that the change to the package name would interfere with our tooling.  But I'll pull this down and run some tests.  Thank you!

PR submitted and I fixed the package name :)

@jeffggardner
There's a couple ways to handle this, I think. In the Python agent there is a new feature  in the Event Info plugin to collect response meta data, such as status codes. This hasn't made it's way to the Node plugin yet, but would allow you to configure alters for specific status codes. Python PR is here:
https://github.com/iopipe/iopipe-python/pull/341
Another option is that the Python agent provides an context.iopipe.error() method to report handled errors. All it does is send the report to IOpipe, it doesn't return any values to Lambda. Unfortunately, context.iopipe.fail() does call the Lambda callback, so it doesn't behave the same way. There is a context.iopipe.sendReport(), though, which could be used to send an error back to IOpipe without calling the callback. We could add an context.iopipe.error() method which would just call sendReport() with an error to make the APIs consistent.

@mrickard I'm under a bit of a time crunch so my plan is to deploy my changes to our private repos and to at least keep moving forward unless you think my recommendation is something you feel could be implemented in the next week or so.  LMK

@jeffggardner We're looking at leveraging our event-info plugin for customizable responses.  Since you're under a time crunch, I'd suggest keep moving forward on your side, and we'll keep you updated with progress on our side.


Add Your Research on Art Community Platforms

To Do: Add your research on art community platforms to research page by describing the main functionalities of the platform, what can we use from this example for our project, and add the link to the platform.
Deadline: 13.03.2022 @17.00

I did research about other art community platforms and added my favorite art platform to Research on Art Community Platforms. You can get more information about my favorite here.


[FileExplorer] Add PDF Thumbnail Provider for Windows Explorer

Summary of the Pull Request
This change adds a PDF Thumbnail Provider to render thumbnails in Windows Explorer for PDF files. Just like the SVG Thumbnail provider. There are third-party tools (like Adobe Acrobat reader) that are doing this, but out-of-the box Windows does not generate thumbnails for PDF files.

Quality Checklist

[x] Linked issue: #13061
[ ] Communication: I've discussed this with core contributors in the issue.
[X] Tests: Added/updated and all pass
[X] Installer: Added/updated and all pass
[X] Localization: All end user facing strings can be localized
[ ] Docs: Added/ updated
[ ] Binaries: Any new files are added to WXS / YML

[ ] No new binaries
[X] YML for signing for new binaries
[X] WXS for installer for new binaries

Contributor License Agreement (CLA)
A CLA must be signed. If not, go over here and sign the CLA.

Please create a stand alone issue for this.

Please create a stand alone issue for this.
#13061

LGTM! Works as intended.
Nit: Could you please add the new key for the pdf thumbnail to the BugReportTool as well?
In registryKeys in tools/BugReportTool/BugReportTool/RegistryUtils.cpp, please?

And clean up tool?

What do you neen? Can you clarify?
Met vriendelijke groet,
Robert de Veen

Van: Heiko @.>
Verzonden: Sunday, September 12, 2021 5:54:58 PM
Aan: microsoft/PowerToys @.>
CC: R. de Veen @.>; Author @.>
Onderwerp: Re: [microsoft/PowerToys] [FileExplorer] Add PDF Thumbnail Provider for Windows Explorer (#13058)
LGTM! Works as intended.
Nit: Could you please add the new key for the pdf thumbnail to the BugReportTool as well?
In registryKeys in tools/BugReportTool/BugReportTool/RegistryUtils.cpp, please?
And clean up tool?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/PowerToys/pull/13058#issuecomment-917661911, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABLXLDFTJM57J2E3ICQ3DHTUBTENFANCNFSM5DOYCE6Q.

What do you neen? Can you clarify?

Van: Heiko @.>
Verzonden: Sunday, September 12, 2021 5:54:58 PM
Aan: microsoft/PowerToys @.>
CC: R. de Veen @.>; Author @.>
Onderwerp: Re: [microsoft/PowerToys] [FileExplorer] Add PDF Thumbnail Provider for Windows Explorer (#13058)
LGTM! Works as intended.
Nit: Could you please add the new key for the pdf thumbnail to the BugReportTool as well?
In registryKeys in tools/BugReportTool/BugReportTool/RegistryUtils.cpp, please?
And clean up tool?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/PowerToys/pull/13058#issuecomment-917661911, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABLXLDFTJM57J2E3ICQ3DHTUBTENFANCNFSM5DOYCE6Q.

I thought we have the registry key listed here too:

https://github.com/microsoft/PowerToys/tree/master/tools%2FCleanUp_tool
https://github.com/microsoft/PowerToys/tree/master/tools%2FCleanUp_tool_powershell_script

But we haven't.

LGTM! Works as intended.
Nit: Could you please add the new key for the pdf thumbnail to the BugReportTool as well?
In registryKeys in tools/BugReportTool/BugReportTool/RegistryUtils.cpp, please?

@jaimecbernardo did you mean this change: https://github.com/microsoft/PowerToys/pull/13058/files?file-filters[]=.cpp&file-filters[]=.pdf#diff-3e83500ba5934789916189129940f743fab350effe98712322b4270d02eaf9c7

LGTM! Works as intended.
Nit: Could you please add the new key for the pdf thumbnail to the BugReportTool as well?
In registryKeys in tools/BugReportTool/BugReportTool/RegistryUtils.cpp, please?

@jaimecbernardo did you mean this change: https://github.com/microsoft/PowerToys/pull/13058/files?file-filters[]=.cpp&file-filters[]=.pdf#diff-3e83500ba5934789916189129940f743fab350effe98712322b4270d02eaf9c7

I mean for BCC13D15-9720-4CC4-8371-EA74A274741E.
Like { HKEY_CLASSES_ROOT, L"CLSID\\{36B27788-A8BB-4698-A756-DF9F11F64F84}" }, that is set for the svg thumbnail.


Fix: Server certificate volume mount in deployment template

What type of PR is this?
/kind bug
/kind chart-release

Any specific area of the project related to this PR?
/area falcosidekick-chart

What this PR does / why we need it:
There's a bug introduced with #548 caused by incorrect values in the template conditions.
Which issue(s) this PR fixes:

N/A
Special notes for your reviewer:
Checklist

[x] Chart Version bumped
[x] CHANGELOG.md updated

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: jgmartinez
Once this PR has been reviewed and has the lgtm label, please assign leogr for approval. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Issif, jgmartinez
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Issif]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: 76044d0e31c10c08e4c389fcd9fe82ecf9718efe


After models are added to the MLJ registry: Check all examples run

The @load commands cannot be tested until the models are registered.

@ablaom checked that they all run and did the necessary fixes where needed which will show up in the next release that I'm rolling out shortly.


Multithreaded manifest-based downloader

Support for multiple connections via 'concurrent_connections' config
Replaced FailedChunkCollector and old resume system in downloadCutout.py with manifest-based resume system
Added hash and eq to downloadCutout Rects so they can be dictionary keys
Pulled downloader functions into a class so class constants could be namespaced

@mtauraso  I was testing this out and ran a few examples. In manifest.fits, all entries of the sh and sw columns are set to 0.0061111111111111 when the specification set in the configuration file is 22asec for both. Is this expected behavior? Is some unit conversion happening in the backend?

@mtauraso I was testing this out and ran a few examples. In manifest.fits, all entries of the sh and sw columns are set to 0.0061111111111111 when the specification set in the configuration file is 22asec for both. Is this expected behavior? Is some unit conversion happening in the backend?

I delved into the code, and it seems like that in the manifest file, sh and sw are being written in degrees. This behaviour is fine as long as we make this abundantly clear in our docs.

@mtauraso I was testing this out and ran a few examples. In manifest.fits, all entries of the sh and sw columns are set to 0.0061111111111111 when the specification set in the configuration file is 22asec for both. Is this expected behavior? Is some unit conversion happening in the backend?

I delved into the code, and it seems like that in the manifest file, sh and sw are being written in degrees. This behaviour is fine as long as we make this abundantly clear in our docs.

This is indeed what is happening, I'll add some documentation of the manifest file format so its super clear


Extension point to handle HID connection failure

A generic way to enable targets to tap into HID connection failures, letting them deal with the failure in a customized way

I get that the WinRT implementation is WinRT specific. But this callback takes a PacketIO which is our generic HID interface. Wouldn’t there be a WebUSB version of the callback too? We need to try avoiding to special too much for each platform.

From: Guillaume Jenkins<EMAIL_ADDRESS>Sent: Friday, February 23, 2018 8:53:19 AM
To: Microsoft/pxt
Cc: Peli de Halleux; Comment
Subject: Re: [Microsoft/pxt] Extension point to handle HID connection failure (#3908)
@guillaumejenkins commented on this pull request.

In pxteditor/editor.tshttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoft%2Fpxt%2Fpull%2F3908%23discussion_r170305669&data=04|01|jhalleux%40microsoft.com|175b6dd57c234151473808d57addf1db|72f988bf86f141af91ab2d7cd011db47|1|0|636550016022124239|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwifQ%3D%3D|-1&sdata=nth1W7EFcCmkmzI5PMQjVtk3TypHMQGv3OyN%2FWpJ2xc%3D&reserved=0:

@@ -257,6 +257,7 @@ namespace pxt.editor {
showUploadInstructionsAsync?: (fn: string, url: string, confirmAsync: (options: any) => Promise) => Promise;
fieldEditors?: IFieldCustomOptions[];
toolboxOptions?: IToolboxOptions;

   winrtHandleDeviceNotFoundAsync?: (io: pxt.HF2.PacketIO) => Promise<void>

I don't think we can make it too generic, everything inside that callback on the Adafruit needs to use WinRT-specific APIs:

Reconnect via WinRT serial
Set the baudrate using WinRT SerialDevice API
WinRT-specific device disconnect
Re-init the WindowsRuntimePacketIo (initAsync is not standard in our base PacketIo class)

I'm open to suggestions if you can think of how to design a single generic WinRT / WebUSB extension point. Otherwise I suggest we use 2 separate callbacks, and then the target can refactor some common logic between the 2 callbacks if possible / necessary
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoft%2Fpxt%2Fpull%2F3908%23discussion_r170305669&data=04|01|jhalleux%40microsoft.com|175b6dd57c234151473808d57addf1db|72f988bf86f141af91ab2d7cd011db47|1|0|636550016022124239|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwifQ%3D%3D|-1&sdata=nth1W7EFcCmkmzI5PMQjVtk3TypHMQGv3OyN%2FWpJ2xc%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAD-4KaEXZqm65Y7Dtev1QdVJWx0uZsUPks5tXuz_gaJpZM4SP-LK&data=04|01|jhalleux%40microsoft.com|175b6dd57c234151473808d57addf1db|72f988bf86f141af91ab2d7cd011db47|1|0|636550016022124239|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwifQ%3D%3D|-1&sdata=hY%2ByQbq0zJUNSYSUEDsoX7I4d4VQ3g2CxQ7wvuZMM3A%3D&reserved=0.

So if I understand correctly you're suggesting a single extension method, and then the targets will do something like this in the implementation?
if (isWinrt()) {
    // WinRT implementation
} else if (webUsb()) {
    // WebUSB implementation
}

After discussion, we were told that the 1200 baudrate trick applies to most Arduino devices and as such we moved the logic to pxt-core. Targets can activate this by adding the appropriate entry to boardDefinition in pxtarget.json


net/http/httputil: ReverseProxy should not forward unparseable query parameters [go1.17 backport] - CVE-2022-2880

From Golang security announcement:
Requests forwarded by ReverseProxy included the raw query parameters from the
inbound request, including unparseable parameters rejected by net/http. This
could permit query parameter smuggling when a Go proxy forwards a parameter
with an unparseable value.
ReverseProxy will now sanitize the query parameters in the forwarded query
when the outbound request's Form field is set after the ReverseProxy.Director
function returns, indicating that the proxy has parsed the query parameters.
Proxies which do not parse query parameters continue to forward the original
query parameters unchanged.
Thanks to Gal Goldstein (Security Researcher, Oxeye) and
Daniel Abeles (Head of Research, Oxeye) for reporting this issue.
This is CVE-2022-2880 and Go issue https://go.dev/issue/54663.

Top level tracking issue: https://github.com/aws/eks-distro-build-tooling/issues/620


Improve window dragging and add fetcher window expansion/retraction animation

This commit improves the old window dragging by making it where it no longer snaps the cursor to the center of the title bar, but rather drags in a natural manner. This pull request also add a Classic Mac OS style opening and closing animation when clicking on a drive icon on the desktop and closing a Fetcher window. However, it does come at the cost of using the other 3 arguments available since there is some data we need to pass to the other sessions of Fetcher to properly preform the animation. However, the diskID argument is preserved, and if you open Fetcher from the command line, the animation isn't preformed since you didn't click on a drive. Feel free to make any further changes :3
- TalonFox

This is awesome, thank you so much :3

No problem :3


(lol) Add more clear alias for :latest pkg ensure

"When you can't move fast and break things" (http://lanyrd.com/2015/cfgmgmtcamp/sdhgcz/)
package { 'puppet':
  ensure => yolo,
}

:+1:

Ha!

CLA signed by all contributors.

Ship it!

:100:
This will dovetail nicely with the ensure => chaos PR I'll be pushing up soon, which selects a random package version.

If you write a unit test for this value and a better commit message, I will merge this. I'll do it. Don't think I won't.

:+1:

Can this be restructured to be a breaking change? Perhaps we retire latest? Naturally, for consistency reasons, we should introduce this breaking change in a Z release.

@kylog :trollface:

Ironic

Some times, a couple of years from now, someone will run into this code in the Puppet code base and look back on this and go "those fuckers".

I love that this was triaged.

And more importantly, left open...

The green button calls to me, so tempting...

It needs at least a spec before we go green button.

Folks. People.
Can we please agree that what happens in Belgium stays in Belgium? (That goes double for @adrienthebo, geddit?)

Well, if anyone wants a spec, this seems to work ;)
describe Puppet::Type.type(:package), "when validating attribute values" do
  before do
    @provider = stub 'provider', :class => Puppet::Type.type(:package).defaultprovider, :clear => nil
    Puppet::Type.type(:package).defaultprovider.stubs(:new).returns(@provider)
    @provider.expects(:satisfies?).with([:versionable]).returns true
  end

  it "should support :yolo as a value to :latest" do
    Puppet::Type.type(:package).new(:name => "yay", :ensure => :yolo)
  end
end

Actually, I'm not sure that works, but vaguely close :+1:

I love you guys. Again, great talk @MosesMendoza it was really inspiring. ;)

:)

:sob:


CRC appears to have the wrong byte order

Thanks for the great library!
I was doing some tests and noticed that the CRC checksum on RTU packets seems to have the wrong endianness. I was beating my head against the wall trying to understand why my devices were not responding to requests, and decided to compare the packets emitted by nanomodbus on a raspberry pi pico to what mbpoll emits over a USB->RS485 adapter. The packets were identical, except for the last 2 bytes, which were swapped.
Manually swapping the bytes by modifying the return value of crc_calc seemed to fix the problem for me. ( I tried messing around by manually definining NMBS_BIG_ENDIAN but it swapped the body bytes as well....)
return (crc << 8) + (crc >> 8);

Ow, I'm sorry for the waste of time! I'll have a look at it. It's strange that tests weren't able to catch this, maybe the RTU code is validating the incoming CRCs in the wrong order, too

In doing some research, I came across this article which explains this oddity.
https://64k.space/the-modbus-crc-endianness-kerfuffle.html

Looks like I should have read the official RTU document (https://modbus.org/docs/Modbus_over_serial_line_V1_02.pdf), I never heard about this little-endian CRC thing.
Thank you very much for the discovery.
I pushed the fix on master, let me know if everything is ok now.

Solved in 3904a6c52f9a53b5366fd95cf4d6997da6976d40


[Feature] Add Option for Random Touch Trail Color

Pretty self-explanatory I think. It just sounds pretty fun to me  :)

Also make the color change every time you re-open the keyboard.


raw html being dropped

Raw html was working fine with the PyPI version (0.4.0) but on the latest (0.5.0.dev) raw html is being dropped (updated to get links working)
For example, this content is rendered:
Testing

But if I wrap it in a div it disappears, i.e.

Testing

This was occurring as there was no handler for html_block nodes (as opposed to html_inline). See my pull request that fixes this up.


map.getUiSettings() not a function?

I'm getting a "map.getUiSettings is not a function" when calling it.
Stumbled cross this function through #921. Is it outdated?

map.getUiSettings().setMyLocationButtonEnabled(false);
The above code is for Java, not Javascript.


Add information to readme about testing

This resolves https://github.com/enchant97/quart-redis/issues/4

This is great documentation, thanks!


Replace Ctrl+Alt+Delete to Ctrl+Shift+Delete to Immediate access Task…

… Manager
Replace Ctrl+Alt+Delete to Ctrl+Shift+Delete to Immediate access Task Manager

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

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


336 pre install garden in base images

closes #336 and resolves a gripe
Overview
tested manually end to end, but leaving as draft until I've got some unit tests too
Discussion
Any additional context that you think is important for reviewers or future users/contributors looking at this PR.
Testing
How did you test this? If a reviewer pulled this branch down and wanted to kick the tires, how would they do so?
Documentation
Does this PR update any docs pages? Should it?

📚 Documentation preview 📚: https://garden-ai--373.org.readthedocs.build/en/373/

Codecov Report
Attention: 27 lines in your changes are missing coverage. Please review.

Comparison is base (9f051a0) 75.89% compared to head (086f0e3) 75.80%.

Files
Patch %
Lines

garden_ai/app/notebook.py
4.16%
23 Missing :warning:

garden_ai/containers.py
88.57%
4 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #373      +/-   ##
==========================================
- Coverage   75.89%   75.80%   -0.10%
==========================================
  Files          42       42
  Lines        2344     2426      +82
==========================================
+ Hits         1779     1839      +60
- Misses        565      587      +22

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

The potential downside of this is that users need to specify the --requirement argument for both notebook start and notebook publish every time, which might be surprising because it's different to the --base-image behavior.

Admittedly the --base-image behavior is a little awkward itself. Maybe as part of #362 we should think through both the --base-image and --requirements behavior together. But for now I think your solution is a huge improvement.

the layer caching we get for free with docker is basically just as good as caching the custom image in local data.

Good realization, and I love that this keeps things pretty simple for our implementation.


[Storage] Fix authentication issue to support get token for --subscription

Description

Support get token for --subcription  in storage data plane commands.
If your storage account are in different subscription compared with account information, --auth-mode login will fail with AuthenticationFailure.
Testing Guide

az storage container create -n test --account-name xxxx --auth-mode login --subscription xxxxx
History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change.
[Component Name 2] az command b: Add some customer-facing feature.

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

add to S171


Improving the README file(documentation of this project)

As I have seen that the README file consists of only pictures, i can improve it by adding text and some more features to it. Please assign it to me under GSSoC-23. @Anupkjha2601

As I have seen that the README file consists of only pictures, i can improve it by adding text and some more features to it. Please assign it to me under GSSoC-23. @Anupkjha2601

Thank you for assigning it to me.


feat: upgrade Realtime image to v2.1.0

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 62.801%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
3552

Relevant Lines:
5656

💛  - Coveralls


Can't install

I'm trying to install and keep getting the following error message:
npm WARN deprecated<EMAIL_ADDRESS>this library is no longer supported
npm WARN deprecated<EMAIL_ADDRESS>Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm WARN deprecated<EMAIL_ADDRESS>request has been deprecated, see https://github.com/request/request/issues/3142
npm ERR! code 243
Any help would be greatly appreciated

@drosenberg-gh thanks for giving it a shot - it’s probably the next few lines of the error that’d say what’s going wrong - the WARN bits wouldn’t cause it to not install

My bad, here is the rest of the error
npm ERR! code 243
npm ERR! git dep preparation failed
npm ERR! command /usr/bin/node /usr/lib/node_modules/npm/bin/npm-cli.js install --force --cache=/home/username/.npm --prefer-offline=false --prefer-online=true --offline=false --no-progress --no-save --no-audit --include=dev --include=peer --include=optional --no-package-lock-only --no-dry-run
npm ERR! npm WARN using --force Recommended protections disabled.
npm ERR! npm ERR! code EACCES
npm ERR! npm ERR! syscall symlink
npm ERR! npm ERR! path ../../../home/username/.npm/_cacache/tmp/git-clone3quyUI
npm ERR! npm ERR! dest /usr/lib/node_modules/node-ble
npm ERR! npm ERR! errno -13
npm ERR! npm ERR! Error: EACCES: permission denied, symlink '../../../home/username/.npm/_cacache/tmp/git-clone3quyUI' -> '/usr/lib/node_modules/node-ble'
npm ERR! npm ERR!  [Error: EACCES: permission denied, symlink '../../../home/username/.npm/_cacache/tmp/git-clone3quyUI' -> '/usr/lib/node_modules/node-ble'] {
npm ERR! npm ERR!   errno: -13,
npm ERR! npm ERR!   code: 'EACCES',
npm ERR! npm ERR!   syscall: 'symlink',
npm ERR! npm ERR!   path: '../../../home/username/.npm/_cacache/tmp/git-clone3quyUI',
npm ERR! npm ERR!   dest: '/usr/lib/node_modules/node-ble'
npm ERR! npm ERR! }
npm ERR! npm ERR!
npm ERR! npm ERR! The operation was rejected by your operating system.
npm ERR! npm ERR! It is likely you do not have the permissions to access this file as the current user
npm ERR! npm ERR!
npm ERR! npm ERR! If you believe this might be a permissions issue, please double-check the
npm ERR! npm ERR! permissions of the file and its containing directories, or try running
npm ERR! npm ERR! the command again as root/Administrator.
npm ERR!
npm ERR! npm ERR! A complete log of this run can be found in:

Ah right, yeah - I’ve seen that, was hoping it was something weird on my homebridge instance. I’ll have a look into solving it
If you want a workaround you can install it manually using
npm install -g homebridge-plugin-am43-blinds-bluez as another user

I think you mean npm install -g homebridge-am43-blinds-bluez
because Not Found - GET https://registry.npmjs.org/homebridge-plugin-am43-blinds-bluez - Not found


GH 3029 copy-webpack-plugin 6.0.1 breaking changes fix

Update copy-webpack-plugin configuration by addressing these breaking changes in v6.0.0
Release notes
Closes #3029
System admin changes

[ ] anet.yml needs change
[ ] db needs migration
[ ] documentation has changed
[ ] graphql schema has changed

Checklist

[x] Described the user behavior in PR body
[x] Referenced/updated all related issues
[x] commits follow a repo#issue: Title title format and these 7 rules
[x] commits have a clean history, otherwise PR may be squash-merged
[ ] Added and/or updated unit tests
[ ] Added and/or updated e2e tests
[ ] Added and/or updated data migrations
[ ] Updated documentation
[x] Resolved all build errors and warnings
[ ] Opened debt issues for anything not resolved here

@ysf-simsoft there is already a PR for this: https://github.com/NCI-Agency/anet/pull/3025
In the future, please push your changes to it


assert_dirs_equal should work for missing files

Just realized it attempts to compare contents of "differing" files even when one is different because it doesn't exist. Don't feel like fixing this as part of current issue, so I'm just filing a bug.

I actually might have misunderstood what was going on. I think the errors I saw were cases where a script was attempting to write a file before the parent directory was created. This is not an unexpected sort of a problem when you're rearranging directories, but it's not a problem with assert_dirs_equal. I'll close this and reopen if I run into this again.


[GSoD 2021] Refactored README.md

Related: wechaty/wechaty.js.org#1012

@huan @proudofsimin @Rohitesh-Kumar-Jain Please take a look.

Thank you for the refactoring

@lijiarui please take a look.

@lijiarui please take a look.

@huan Can you take a look?

@huan done the requested changes.

@huan Done with the requested changes. Also, NPM/ Build is failing because of PR #17 but I think we can ignore this.


feat: add op counter

related with https://github.com/paradigmxyz/evm-inspectors/issues/20

@mattsse does it look good to you ?

the total gas cost per opcode * count?

I was thinking of mapping each opcode to its constant gas value. Then, when the final opcode result is mapped, I would simply multiply the constant gas by the number of repetitions of that opcode.  but  this implementation seems inefficient, doesn't it ?

or it may be some funciton that can calculate the gas?

@sslivkoff what should opcode_gas
the total gas cost per opcode * count?

i tried to use the look up table from revm but it doesn't work it return for some opcode gas 0 and for some good value and for others false value
   fn step(&mut self, interp: &mut Interpreter, _context: &mut EvmContext<DB>) {

        let opcode_val = interp.current_opcode();
        let opcode =
            OpCode::new(opcode_val).unwrap_or_else(|| unsafe { OpCode::new_unchecked(opcode_val) });

        *self.opcode_counts.entry(opcode).or_insert(0) += 1;

        let spec_id = revm::primitives::specification::SpecId::SHANGHAI;
        let gas_info =
            revm::interpreter::instructions::opcode::spec_opcode_gas(spec_id)[opcode_val as usize];

        let opcode_gas = gas_info.get_gas() as u64;

        *self.opcode_gas.entry(opcode).or_insert(0) += opcode_gas;
    }
}```

@sslivkoff what should opcode_gas
the total gas cost per opcode * count?

afaui the same op-code can cost different amounts of gas depending on context and depending on input arguments
so ideally it would be the sum of each opcode ocurrence but this would not be a simple multiplication

there's also a bit of complication on contract calls returning whatever amount of spare unused gas they do not use
ideally want a situation where the sum of opcode gas entries equals the total amount of gas used by the transaction
might need to do some interesting nested gas accounting to make this happen given the various types of gas refunds

let's also make the fields pub so they can be consumed easily

let's also make the fields pub so they can be consumed easily

hm they are already public,

@mattsse does it look goods to you ? workflow is failing but doesn't seem related with this pr ?

I few nits,
this could also use a helper function that returns an iterator over all opcodes and their count+gas (opcode, (u64,u64))

thanks, i hope this time look good to you :)


Staff should be available as authors before first login

Issue Summary
As an admin, if you're setting up a staff member, for example, a contributor with a new account. Then the current process requires them to confirm before you can add them as an author, thus giving them access to edit the page.
This is a lot less convenient than it could be:

send invite
they login and see nothing
now you know they've accepted
now you can add them to pages they need to edit
now they can login and get to work

Even more ideal would be all staff getting access to published pages, but not necessarily access to edit them. If the pages are published, then it makes no sense that they have access to see them online but not within their ghost accounts - does it?
Steps to Reproduce
Clear from summary above.
Ghost Version
4.48.0
Node.js Version
N/A
How did you install Ghost?
Docker / Linux
Database type
SQLite3
Browser & OS version
No response
Relevant log / error output
No response
Code of Conduct

[X] I agree to be friendly and polite to people in this repository

I'm closing this as a feature requests because this is currently working as expected. As the bot says, please post the idea on the forum and we'll take demand into consideration 🙂

@daniellockyer would you mind explaining your rational behind a useless button existing for all staff not being a bug? They can click new page, write on the new page, but will always get an error when trying to save it.


Invalidate a donation from the admin panel

This gives certain users with the proper credentials the right to mark a donation as invalid.
We need this in the rare cases when a manual fix is need due to some problem with stripe or the bank.

There is a formatting error in Grid.tsx which is blocking the build. @slavcho could you please check this?


use: io.ktor:ktor-client-darwin-legacy instead of io.ktor:ktor-client-darwin

https://youtrack.jetbrains.com/issue/KTOR-4159

Is this an ios issue? The macOS sample works fine

I added an iOS sample, and everything is working. Also, I don't see why I should use darwin-legacy given the issue you linked is fixed.

@luca992  use a iOS 11 devices


Add Madgwick attitude estimation filter

I just added a replacement for qfilter. It seems to work fine even though it does not estimate the gyro biases (can be added according to the original paper ).
Unlike qfilter, it estimates the angle between the horizontal plane and the magnetic field, so that it can use 3 components (qfilter only uses a projection of the magnetic field on the x-y plane).

Ok, I just found a bug: sometimes the filter converges upside down! This needs more work.

Merged with disclaimer WIP in pull request #121

Could we delete this branch then?


This repo needs a license

The title says it all.

Yes, it does.

The title says it all.

Commit


(GitHub Sort Reactions) Suggestion: collapse out of view the block of buttons when mouseaway. In such case, display the active sort icon next to the two-triangles icon

@Mottie First of all, thanks a lot for this great script!
I was wondering whether it's possible to make a script to sort the comments based on the reactions in a practical way ! You really nailed it, once again! 👏

I just have one suggestion, please:
Currently, having two rows of button blocks (one of the post itself and the second by the script)
makes it distracting and difficult for me to visually distinguish them.
My suggestion is to collapse out of view (- in a similar way to that of your script "GitHub Reveal Header"- maybe collapse  the block by temporarily converting it to a thin line/separator) the block of buttons on mouseaway from that element. And:

when a sort button is active and the block of buttons is collapsed on mouseaway,
to display the currently active sort icon and its order (i.e. create an extra icon) next to the two-triangles icon.
when no sort is active, remove that extra icon.

Please see my mockup below to better see what I mean.
I know the script in it's initial version - I just wanted to post my suggestion and I hope you like it. 🙂
Example screenshot:

And a mockup:

PS. I've tried implementing my suggestion myself but unfortunately it seems too difficult for me, that's why I didn't provide a PR instead.

Hi @darkred!
Yeah, I agree that having the bar under the comment with all the reactions is a bit confusing. Too many emojis clumped together!
I'm not sure I want to make the bar collapsible. Maybe instead we could do something like this?

Clicking the emoji would open a select showing all reactions. Clicking the arrow would change the sort direction, or remove the sort on the third click.

Great idea, @Mottie! That would be the best! Compact and subtle.

Try this out:

Great! Thank you.


'az interactive' throws unknown locale: UTF-8 on MacOS

Description
az interactive command throws error unknown locale: UTF-8 on MacOS command line.

It works after I set the LC_CTYPE environment variable to en.
Environment summary
Install Method: How did you install the CLI? (e.g. pip, interactive script, apt-get, Docker, MSI, nightly)
Answer here:
brew update && brew install azure-cli
CLI Version: What version of the CLI and modules are installed? (Use az --version)
Answer here:
OS Version: What OS and version are you using?
Answer here:
➜  ~ az --version
azure-cli (2.0.18)

acr (2.0.12)
acs (2.0.16)
appservice (0.1.17)
backup (1.0.1)
batch (3.1.4)
billing (0.1.5)
cdn (0.0.9)
cloud (2.0.8)
cognitiveservices (0.1.8)
command-modules-nspkg (2.0.1)
component (2.0.7)
configure (2.0.11)
consumption (0.1.5)
container (0.1.11)
core (2.0.17)
cosmosdb (0.1.13)
dla (0.0.12)
dls (0.0.14)
eventgrid (0.1.4)
extension (0.0.3)
feedback (2.0.6)
find (0.2.7)
interactive (0.3.10)
iot (0.1.12)
keyvault (2.0.11)
lab (0.0.11)
monitor (0.0.10)
network (2.0.15)
nspkg (3.0.1)
profile (2.0.13)
rdbms (0.0.7)
redis (0.2.9)
resource (2.0.15)
role (2.0.12)
servicefabric (0.0.4)
sql (2.0.12)
storage (2.0.16)
vm (2.0.15)

Python location '/usr/local/opt/python3/bin/python3.6'
Extensions directory '/Users/felipebueno/.azure/cliextensions'

Python (Darwin) 3.6.2 (default, Aug 27 2017, 16:33:15)
[GCC 4.2.1 Compatible Apple LLVM 8.1.0 (clang-802.0.42)]

Shell Type: What shell are you using? (e.g. bash, cmd.exe, Bash on Windows)
Answer here:
zsh on macOS Sierra 10.12.6

Screenshots

@williexu, can you take a quick look?

This seems to be a bug in the way Python makes assumptions about the format of locale names and only appears to happen on the OSX terminal. The fix is to set LANG/LC_ environmental variables to the correct string for your locale. Got this from here, here and here.

@felipebueno could you please try out this solution? I'll close this for now since it doesn't require a product fix. Please feel free to reopen if you have any further concerns.


TODO: update parths to relative in Cargo.toml files

Example :
diff --git a/compatibility-test/Cargo.toml b/compatibility-test/Cargo.toml
index 7a18f73..2b31ff5 100644
--- a/compatibility-test/Cargo.toml
+++ b/compatibility-test/Cargo.toml
@@ -11,7 +11,7 @@ description = "Tests for both the propverify and the proptest crates - to check
 [dependencies]

 [target.'cfg(verify)'.dependencies]
-propverify = { path="/home/rust-verification-tools/propverify" }
+propverify = { path="../propverify" }

 [target.'cfg(not(verify))'.dependencies]
 proptest = { version = "*" }
diff --git a/demos/simple/klee/Cargo.toml b/demos/simple/klee/Cargo.toml
index 11fe766..fa1e6f4 100644
--- a/demos/simple/klee/Cargo.toml
+++ b/demos/simple/klee/Cargo.toml
@@ -5,7 +5,8 @@ authors = [""]
 edition = "2018"

 [dependencies]
-verification-annotations = { path="/home/rust-verification-tools/verification-annotations" }
+#verification-annotations = { path="/home/rust-verification-tools/verification-annotations" }
+verification-annotations = { path="../../../verification-annotations" }

btw. also maybe consider +nightly in scripts as it seems that some nightly features are required, example:
 cargo clean
-cargo build --features=verifier-klee
+cargo  +nightly build --features=verifier-klee

Your comment crossed paths with a PR that just landed that improves the docker/build system.
In particular, we now use +nightly in the docker/init script that rebuilds all the tools.
(The docker build process is also much faster than before: 15-20 minutes instead of 3 hours)
We deliberately do not use +nightly in the verify.sh scripts, the cargo-verify script or the Cargo.toml files in regression tests (demos///Cargo.toml, compatibility-test/Cargo.toml) because those need to be built with an LLVM-10 compatible version of Rust. (Our docker build uses the last LLVM-10 version of rustc (nightly-2020-08-03) and makes that the default Rust compiler.  Support for LLVM11-based rustc is partially done - but many of our regression tests break.)

wrt this change
[target.'cfg(verify)'.dependencies]
-propverify = { path="/home/rust-verification-tools/propverify" }
+propverify = { path="../propverify" }

What we really want to do here is to use path="$RVT_DIR/propverify" but, unfortunately, Cargo does not support environment variables in toml files.
We chose to use an absolute path because then it is easy to use the same dependency information in any toml file, examples, etc. But this only works if you are using docker (where we mount $RVT_DIR) as /home/rust-verification-tools.
Until now, we have been assuming that building directly (not using docker) was too painful for people to do - so this seemed like a good choice. But

It sounds as if you are not using docker
The PR that I just merged dramatically simplified the build process (you no longer have to build a custom version of rustc/libstd/libcore) and we are wondering whether we could further simplify our use of docker.

I need to think about this a bit more...

or maybe must make package propverify and put it on crates.io ?

We have held off on doing that because the code is still all experimental,
changes in a tool often needs matching changes in a crate (and vice versa)
so building them all within docker with a single compiler, from a single
source tree avoids problems. (Of course, long-term, they should be on
crates.io - but we don't feel ready for that yet.)
But I am puzzled about why you were seeing any problems here.
If you build a docker image and you only verify within that image (and you
use 'cargo clean' or 'cargo verify --clean ...' to remove code compiled
with other rustc versions), then it should all be consistent.
If you are building as I described in #138 and seeing problems (except for
the need for sudo), can you give us some details so that we can reproduce
and fix.
On Fri, May 21, 2021 at 1:17 PM Grzegorz Wierzowiecki (parity) <
@.***> wrote:

or maybe just make package propverify and put it on crates.io ?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/project-oak/rust-verification-tools/issues/137#issuecomment-845910082,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACXRJSKTEQBN72MI36P6RYTTOZFPNANCNFSM45HARZ2Q
.


Fix overfiltering

QA has identified situations, where the UI can become usable, when filtering with no matches, then taking an action, such as opening the map. After further investigation, all checkbox filter and freetext search, map activation and date filtering have been changed back to mirror production HydroShare.
Functional review has been performed by Martin and Mark:
http://dev-hs-7.cuahsi.org/search/

Select checkbox filters until no results are returned
Search in the freetext area, note everything is reset and a new search started

METRIC
VALUE

https://sonarqube.cuahsi-workstation.com:9000/dashboard?id=hydroshare-4011


Photo Uploaded but not showed in instagram

Photo Uploaded successfully but not showed in instagram account in many many times!
hi
i am using InstagramUploadPhotoRequest to upload photo to my Instagram account and uploading process finished completely and successfully. status in result is "ok" but uploaded photo not showed in my instagram account in many times.
uploading stack trace:
`- Setup...

Device ID is: android-486d4feeeab9c28b, random id: 4443cfd4-c54f-4223-af23-c5361a3593ff
Logging with user my.username and password ***********
Sending request: org.brunocvcunha.instagram4j.requests.InstagramLoginRequest
Reading InstagramLoginResult from {"logged_in_user": {"pk":<PHONE_NUMBER>9, "username": "my.username", "full_name": "", "is_private": false, "profile_pic_url": "https
Sending request: org.brunocvcunha.instagram4j.requests.InstagramUploadPhotoRequest
Sending request: org.brunocvcunha.instagram4j.requests.internal.InstagramUploadResumablePhotoRequest
The upload id is<PHONE_NUMBER>681
Reading InstagramUploadPhotoResult from {"upload_id": "1596093606681", "xsharing_nonces": {}, "status": "ok"}
Upload photo result: StatusResult(status=ok, message=null, spam=false, lock=false, feedback_title=null, feedback_message=null, error_type=null, checkpoint_url=null)
Sending request: org.brunocvcunha.instagram4j.requests.internal.InstagramConfigurePhotoRequest
Reading InstagramConfigureMediaResult from {"media": {"taken_at":<PHONE_NUMBER>, "pk":<PHONE_NUMBER>927551152, "id": "2364527181927551152_39845003030", "device_timestamp": 15960
Configure photo result: InstagramConfigureMediaResult(super=StatusResult(status=ok, message=null, spam=false, lock=false, feedback_title=null, feedback_message=null, error_type=null, checkpoint_url=null), ................
`
========

how solve this problem uploading is ok but not shown in my instagram account!!!
please help me to solve this problem
tnx

Addressed in rewrite or no longer relevant.
Please reopen if issue persists in rewrite.


Revert "disable auto-deploy to prod during change freeze"

Reverts citizensadvice/local-office-search-api#222

do not merge before 6th Jan