User inclusion proofs for v3

V3 is using a multivariate KZG to interpolate the advice polynomials. The user inclusion proof should be a KZG opening proof for the balance values corresponding to a particular user.

#290


follow-up workshop sessions for data submitters (March)

to be raised at the project management meeting 27th Jan.

Nikki has made two tentative 'drop in surgery' dates (3 March and 18th March) where the idea would be to have submitters drop in and ask specific questions, and keep the formality to a minimum.

refined idea - to have two half-day sessions (morning preferable) at the proposed dates. @NikkiTaylorJNCC to send out save the dates for the two sessions

JNCC to give short recap overview
submitters with ICES to then go into Q&A and help sessions as needed

@neil-ices-dk to automate the feedback form to ping<EMAIL_ADDRESS>and<EMAIL_ADDRESS>

@neil-ices-dk to automate the feedback form to ping<EMAIL_ADDRESS>and<EMAIL_ADDRESS>
Feedback from now udpated https://forms.office.com/r/rwEym4XPZq
entering response sends email to marinemammals (JNCC) and Accessions (ICES)
Any further additions to the feedback form?

@neil-ices-dk to automate the feedback form to ping<EMAIL_ADDRESS>and<EMAIL_ADDRESS>
Feedback form now udpated https://forms.office.com/r/rwEym4XPZq entering response sends email to marinemammals (JNCC) and Accessions (ICES)
Any further additions to the feedback form?

I think that's fine now @neil-ices-dk thanks!

potentially 5 attendees, Niki to chase up with email along with notification to new template


Error: Socket unusable after connection. Hint: You may be using a certificate for the wrong environment

I am getting this error while sending push notifications using apn for few days.
Earlier it was working fine.
What can be the root cause for this?
Any help would be highly appreciated.

do you use the certificate that goes with your build? (Eg if you test with an ad hoc build, you should use that certificate). I find it easier to use the provider authentication tokens


Add test for equality on slices of a struct array

Which issue does this PR close?
Closes #514.
Rationale for this change
This was caused by a problem in struct slices and equality. It was fixed by a separate PR, but it seems beneficial to get an explicit test of the expected behavior in as well to prevent regression.
What changes are included in this PR?
A test that was previously failing for equality on slices of a struct array.
Are there any user-facing changes?
No.

Marking PRs that are over a month old as stale -- please let us know if there is additional work planned or if we should close them.


Container issues

How to handle multi output coming from masker? Example, clustering output and mask in case of Deep clustering. Right now the masker expects only a single output
Applying the mask: I need to apply the mask on the masker input (magnitude spectra and not the real and imaginary part). Will have to rethink the design

The Container is quite limited for now and I'm not sure it makes sense to try and fit all forward into one class. Probably the solution will be to subclass it (but I'll try to find something clever to keep the saving and loading practical as it is now).
For the masking, a 'mag' mask is a magnitude mask which is applied to the complex representation. It's strictly equivalent to a magnitude mask, but the phase is kept so the resynthesis can be done.

Solved by #19


Typo in TeamsFX CLI V2 doc

https://learn.microsoft.com/en-us/microsoftteams/platform/toolkit/teamsfx-cli?pivots=version-two#teamsfx-provision - The word trigger has a typo, please correct it.

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

ID: e572f611-ae28-a06a-a66a-7d15c497496d
Version Independent ID: e572f611-ae28-a06a-a66a-7d15c497496d
Content: TeamsFx Command Line Interface - Teams
Content Source: msteams-platform/toolkit/TeamsFx-CLI.md
Service: msteams
GitHub Login: @MuyangAmigo
Microsoft Alias: zhany

@surbhigupta12 - Could you please help to update this.


cmd.exe always hang if calling SetConsoleScreenBufferSize at bottom line

Environment
Microsoft Windows [Version 10.0.18362.239]

Steps to reproduce
Sorry, I don't figure out clearly but this step always make cmd.exe hang. At present, the method that can be reliably reproduced is to start vim.exe at the bottom line of cmd.exe.
Expected behavior
Do not hang.
Actual behavior
Hang.
FYI, I tried to run this code, but not reproduce.
#include <windows.h>

int
main(int argc, char* argv[]) {
	HANDLE h = GetStdHandle(STD_OUTPUT_HANDLE);
	COORD coord;
	coord.X = 80;
	coord.Y = 300;
	SetConsoleScreenBufferSize(h, coord);
	return 0;
}

I send PR to vim/vim. https://github.com/vim/vim/pull/4679
I cound avoid hang with moving cursor to top of window before calling SetConsoleScreenBufferSize.

Now, I could reproduce this with the code above. But seems to depend on some conditions.

I attached conhost.exe with gdb.

[Thread 17920.0x3d04 exited with code 0]
warning: onecore\windows\core\console\open\src\buffer\out\textbuffercelliterator
.cpp(49)\conhost.exe!00007FF7AA12FB34: (caller: 00007FF7AA10CACE) Exception(1) t
id(3e34) 80070057 p[^[ｪﾔﾁﾄ｢ﾜｷB
warning: onecore\windows\core\console\open\src\buffer\out\cursor.cpp(198)\conhos
t.exe!00007FF7AA125B92: (caller: 00007FF7AA109DAD) LogHr(2) tid(3e34) 80070057 p
[^[ｪﾔﾁﾄ｢ﾜｷB
    Msg:[onecore\windows\core\console\open\src\buffer\out\textbuffercelliterator
.cpp(49)\conhost.exe!00007FF7AA12FB34: (caller: 00007FF7AA10CACE) Exception(1) t
id(3e34) 80070057 p[^[ｪﾔﾁﾄ｢ﾜｷB
]
warning: onecore\windows\core\console\open\src\host\_stream.cpp(233)\conhost.exe
!00007FF7AA12DB11: (caller: 00007FF7AA10E281) FailFast(1) tid(3e34) 8000FFFF vｽI
ﾈG[ﾅｷB
gdb: unknown target exception 0xc0000409 at 0x7ff7aa12db11

Thread 1 received signal ?, Unknown signal.
[Switching to Thread 17920.0x3e34]
0x00007ffd53dcf5ef in RaiseFailFastException ()
   from C:\WINDOWS\System32\KernelBase.dll
(gdb)

https://github.com/microsoft/terminal/blob/9b92986b49bed8cc41fde4d6ef080921c41e6d9e/src/buffer/out/textBufferCellIterator.cpp#L46
This is a line crashed.

Probably, https://github.com/microsoft/terminal/issues/1795 https://github.com/microsoft/terminal/issues/1206 are related issues.

I guess that the cause of this bug is related on cursor location. If the cursor position is out of bounds of RESIZED size, cmdhost.exe crash.

@DHowett-MSFT Did you get enough information to fix this issue?

@mattn, I've tried to reproduce this today and cannot get it to happen. Does it still happen for you? Can you provide a crash dump from the conhost on your machine that is crashing?

Sorry, I mistaken. When this bug occur, conhost.exe is always exited so I can not get dump. But when I used gdb, I could get stacktrace above.

I can reproduce this fairly easily in the debugger (or at least a very similar issue). The trick, in my case, is to have the Wrap test output on resize option unchecked in the Layout properties. Then the easiest way to trigger it is with a printf in a bash shell:
printf "\e[1;80H\e[8;25;40t"; sleep 5

The sleep isn't always required, but it seems to help in some situations, assumedly because it needs time to trigger before the prompt is displayed and the cursor repositions itself.
In the debugger I can see that it's crashing when trying to paint the cursor while out of bounds (the buffer width is 40, while the y pos is at 80). Here's the key part of my call stack (on commit 4b439cf290d74caf61041803846df81a75f28919):
OpenConsole.exe!TextBufferCellIterator::TextBufferCellIterator(const TextBuffer & buffer, _COORD pos, const Microsoft::Console::Types::Viewport limits) Line 46
OpenConsole.exe!TextBufferCellIterator::{ctor}(const TextBuffer & pos, _COORD) Line 23
OpenConsole.exe!SCREEN_INFORMATION::CursorIsDoubleWidth() Line 2852
OpenConsole.exe!RenderData::IsCursorDoubleWidth() Line 269
OpenConsole.exe!Microsoft::Console::Render::Renderer::_PaintCursor(Microsoft::Console::Render::IRenderEngine * const pEngine) Line 733
OpenConsole.exe!Microsoft::Console::Render::Renderer::_PaintFrameForEngine(Microsoft::Console::Render::IRenderEngine * const pEngine) Line 118
OpenConsole.exe!Microsoft::Console::Render::Renderer::PaintFrame() Line 65
OpenConsole.exe!Microsoft::Console::Render::RenderThread::_ThreadProc() Line 165
OpenConsole.exe!Microsoft::Console::Render::RenderThread::s_ThreadProc(void * lpParameter) Line 148

I'm almost certain I've had this crash with a manual resize as well, although I haven't now been able to reproduce that.

As @mattn hinted, the issue can be worked around by setting the cursor position to (0, 0) before resizing the buffer. It still crashes if the console is resized to the minimum allowed, but that is less likely to happen.
Another workaround is to FreeConsole() and then AllocConsole() every time the console dies (which can be detected by checking if GetNumberOfConsoleInputEvents fails with error ERROR_PIPE_NOT_CONNECTED). This will pop out a new console where your application can continue running.

I've been doing some digging into this, and found there were two underlying issues: 1) the cursor position being out of range, and 2) the viewport being out of range. Issue 1 has largely been addressed by PR #4901, which added bounds checking on the cursor position. That fixed my first test case.
Another partial "fix" came in commit eb480b6bbbd83a2aafbe62992d360838e0ab9da5, which added exception checking on the _PaintFrameForEngine method, and that has stopped my second test case from crashing. It's still technically failing, though, so that's not ideal, but at least it doesn't crash.
It's also worth mentioning that this exception check doesn't catch all exceptions under the _PaintFromEngine method. In particular, an exception in the IsCursorDoubleWidth method will not be caught because it's incorrectly marked as noexcept. So that's the first thing I'd recommend fixing.
The main outstanding problem, though, is the viewport being out of range. That can be triggered from a number of different places: the SetConsoleScreenBufferSize API (which may have been the source of this particular issue), the SetConsoleScreenBufferInfoEx (which I suspect was the source of issue #256), and the SetConsoleWindowInfo API (which was the source of the crash in my second test case).
The last of these is fairly easy to fix. The error is in the SCREEN_INFORMATION::SetViewport method, which tries to make sure the viewport coordinates are in range. There are off-by-one errors in those calculations, though, so it never successfully corrects out-of-range values.
The other two only seem to fail when viewport wrapping is disabled. The problem comes from resizing the buffer in such a way that that viewport extends past the bottom or right. When the wrapping is enabled, the ResizeWithReflow method adjust the viewport so that's not a problem. When disabled, though, the ResizeTraditional method leaves the viewport in a broken state, and the next repaint or cursor movement will likely crash.
Now I don't want to mess with the ResizeScreenBuffer method, since that's called from a bunch of places, most of which have their own way of adjusting the viewport. So my suggestion is we add some additional checks in the SetConsoleScreenBufferSizeImpl and SetConsoleScreenBufferInfoExImpl functions to test if the viewport is out of range, and then adjust the origin to move it back into range.
I can't be certain this will fix every possible resize exception, but it should at least be a major improvement on the current state of affairs.

After testing this some more, I found that fixing the viewport wasn't enough by itself. We also need to make sure the cursor position is clamped to the new buffer dimensions, otherwise there are still situations in which conhost can crash. I had hoped we were clamping the cursor to the viewport in enough places to make that unnecessary, but it seems not.
So in addition to the changes discussed above, I'm also recommending we clamp the cursor position in SetConsoleScreenBufferSize and SetConsoleScreenBufferSizeImpl. I don't think it's necessary in SetConsoleWindowInfo though.
I've already starting putting together a PR with these changes, but there's not a huge amount of work involved, so if you think this is the wrong approach, it's not a big deal to drop it and try something else.

I'm alright with your proposals, @j4james. I think it's just a bunch of little things that slipped through the cracks here, so I'm happy to take the fixes.
If you did want to tackle the Resize* methods though ever... they're not sacred nor original. I did rewrite them at some point in time, so if it's time to patch them up further, don't feel like you must avoid them unless they just look too crazy to touch.
My long term goal has always been to try to move everything to standard rectangle math (bottom and right are exclusive to match what everything else does instead of the crazypantsness that Console did forever with SMALL_RECTs being inclusive bottom/right) and I think this particular area is suffering from the mismatch pretty heavily. My first attempt was Viewport... which obviously failed as it left a lot of bugs. til::rectangle and friends are my newest attempt, but I haven't rolled them out broadly yet.


puppetdb 5.X?

Someone test with the latest puppetdb?

I'm running 5.0.1 with 0 issues.

great thanks

I suggest this is made clear in the README, in case someone doesn't dare to upgrade their Puppet.


Introspect thor commands?

Hi, is there someway i can introspect available commands from code? I.e read in a Thorfile and then enumerate the commands? And necessary paramters and such?
Thanks much.

It almost sounds like what you're asking for is thor list or thor help, but trying that out I see a few limitations. Not sure if this is quite what you were talking about but thought I'd add some notes.
The command thor list is the closest to what you're asking for but it doesn't include the necessary parameters.
The help command does include the parameters and works for executables built with thor, but it seems that running thor help in a directory containing a thor file will only show the help for thor's own commands and not the ones in the Thorfile. Interestingly, thor help <command> still works.
For example in Thor's own repo:
$ thor help
Commands:
  thor help [COMMAND]  # Describe available commands or one specific command
  thor install NAME    # Install an optionally named Thor file into your system commands
  thor installed       # List the installed Thor modules and commands
  thor list [SEARCH]   # List the available thor commands (--substring means .*SEARCH)
  thor uninstall NAME  # Uninstall a named Thor module
  thor update NAME     # Update a Thor file from its original location
  thor version         # Show Thor version

$ thor help release
Usage:
  thor :release

Create tag v0.19.1 and build and push thor-0.19.1.gem to Rubygems

It does show up in thor list, but without parameters.
$ thor list
default
-------
thor :build    # Build thor-0.19.1.gem into the pkg directory
thor :install  # Build and install thor-0.19.1.gem into system gems
thor :release  # Create tag v0.19.1 and build and push thor-0.19.1.gem to Rubygems
thor :spec     # Run RSpec code examples

Now a slightly off-topic side note: I think it'd be really useful to have something like git's --porcelain flag  (to "give the output in an easy-to-parse format for scripts", which will "remain stable across versions regardless of user configuration").
Parsing the list of tasks is useful for:

Command-line auto-completion
CI tools that try to automatically find certain tasks like "test", like travis-build.

I've been working on a new tool for the later problem that is similar to travis-build but that acts as a universal frontend for any tasks rather than having a few built-in tasks it supports or assumptions it makes. The idea is that it can aggregate the available tasks from all task runners. So if you have a Thorfile, a Rakefile and a Gruntfile all in the same directory and you run psychic list tasks it should be able to show you all of the tasks implemented by thor, rake or grunt. Similarly, if you run something like psychic run lint it would find which of those tools have defined a "lint" task defined and either run the first match or run each lint task. So it might use Thor to lint your ruby code and Grunt to lint your javascript code.
An output format that's designed to be simple and machine-readable would useful, especially if it's used by several tools.

Hi but i was wondering if there was something just readily available. I guess thor on the inside works like:
1 Enumerate the commands
2 Get the command of the user
3 See the params and see if the params of the user are correct
4 If so execute
Therefore i was just looking for somthing like:
require 'thor'
Thor = Thor:Load("MyThorFile");
Thor.commands.first.name

etc etc.
However a porcelain would be handy but beating the purpose a bit. But for other usecases would work as autocompelte etc.

Ah, sorry... I didn't notice you said "from code"

Now a slightly off-topic side note: I think it'd be really useful to have something like git's --porcelain flag (to "give the output in an easy-to-parse format for scripts", which will "remain stable across versions regardless of user configuration").
Parsing the list of tasks is useful for:

Command-line auto-completion
CI tools that try to automatically find certain tasks like "test", like travis-build.

I've been working on a new tool for the latter problem that is similar to travis-build but that acts as a universal frontend for any tasks rather than having a few built-in tasks it supports or assumptions it makes. The idea is that it can aggregate the available tasks from all task runners. So if you have a Thorfile, a Rakefile and a Gruntfile all in the same directory and you run psychic list tasks it should be able to show you all of the tasks implemented by thor, rake or grunt. Similarly, if you run something like psychic run lint it would find which of those tools have defined a "lint" task defined and either run the first match or run each lint task. So it might use Thor to lint your ruby code and Grunt to lint your javascript code.
An output format that's designed to be simple and machine-readable would useful, especially if it's used by several tools.

@maxlinc  Could you build the thing above? I'm looking for exactly the same thing in Thor for Command-line autocompletion?


fix: handle one off bypassing paymaster and data middleware case

Pull Request Checklist

[ ] Did you add new tests and confirm existing tests pass? (yarn test)
[ ] Did you update relevant docs? (docs are found in the site folder, and guidelines for updating/adding docs can be found in the contribution guide)
[ ] Do your commits follow the Conventional Commits standard?
[ ] Does your PR title also follow the Conventional Commits standard?
[ ] If you have a breaking change, is it correctly reflected in your commit message? (e.g. feat!: breaking change)
[ ] Did you run lint (yarn lint:check) and fix any issues? (yarn lint:write)
[ ] Did you follow the contribution guidelines?

PR-Codex overview
This PR introduces improvements to middleware handling in the core package.
Detailed summary

Added bypassPaymasterMiddleware for v0.7.0 user operations
Updated defaultGasEstimator to handle bypassing paymaster middleware
Updated defaultPaymasterAndData middleware logic

The following files were skipped due to too many changes: packages/core/src/utils/userop.ts, packages/alchemy/src/middleware/gasManager.ts

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

updated the PR with:
additional omit paymaster field from gas estimator for bypass case
Added a number of missing jsDocs

@dphilipson we don't have control over the overridden dummy paymaster middleware. When the user sets the paymaster (for example gas manager), both dummy paymaster middleware and paymaster middleware is overridden.
The dummy paymaster middleware is supposed to set the paymaster address + dummy data for the dummy paymaster middleware. (we should add this to our doc of using custom paymaster)

Asana task https://app.asana.com/0/1205598840815267/1207162808443182/f for "The dummy paymaster middleware is supposed to set the paymaster address + dummy data for the dummy paymaster middleware. (we should add this to our doc of using custom paymaster)" @dphilipson

we don't have control over the overridden dummy paymaster middleware. When the user sets the paymaster (for example gas manager), both dummy paymaster middleware and paymaster middleware is overridden

wait why don't we just do what we do with dummyPaymaster? we can skip running dummy paymaster if the override is 0x and just noop there. that means nothing downstream will get a paymaster field so doesn't matter if people override the gas estimator

breaking change: - dummyPaymasterAndData middleware override used to be () => Hex, but in this PR, changed to ClientMiddlewareFn just like all other middlewares.

updated thanks for the thorough review! @dphilipson @moldy530

@dphilipson udpated per your suggestion. Thanks!


Marketing - Added Pricing Page

Added new pricing screen

Feel free to modify any of the lines or let me know what you'd like it to say
I updated the theme for the 11ty app and it updated the styles across every html page in the dist folder lol

Merging this in before we lose it :D


[UI] Fix Workloads Widget

Current Behavior

Unlike other widgets on Meshery Dashboard, Workloads widget is not using the white paper background. Thus, having a poor UX when no workload is discovered/registered by Meshery Server.

Desired Behavior

Use exact same styling/classes for the "Workloads" widget.
Screenshots/Logs

Environment

Browser: Chrome Safari Firefox
Host OS: Mac Linux Windows
Meshery Server Version: stable-v
Meshery Client Version: stable-v
Platform: Docker Kubernetes

Contributor Guides and Handbook

🎨 Wireframes and designs for Meshery UI in Figma (open invite)
🖥 Contributing to Meshery UI
🙋🏾🙋🏼 Questions: Discussion Forum and Community Slack

Hey I really wanted to work on this issue can you please assign this to me

@theBeginner86 seems like this issue is covering tthe current issue too.

duplicate issue


2-Class detection, one class has no results

I'm trying to train a two class detection model. I am training on DIGITS Version 4.0.0, Caffe Version 0.15.14.
Right now i'm using COCO's dog database filtered out to only include images with either humans or dogs. This is how I set up my database.

I set up the data to look like this

dog 0 0 0 539.72 295.45 562.63 313.84 0 0 0 0 0 0 0
person 0 0 0 512.89 271.42 534.13 304.15 0 0 0 0 0 0 0

This is how my current model is set up.

I'm using this DetectNet 2 Class Prototxt (https://github.com/NVIDIA/caffe/blob/caffe-0.15/examples/kitti/detectnet_network-2classes.prototxt) and GoogleNet (http://dl.caffe.berkeleyvision.org/bvlc_googlenet.caffemodel) as the pretrained model.
Currently, my results look like this.

There is detection for one of the classes(dogs), however, the percision and recall for the second class(human) never rises above 0.
Can anyone point me in the right direction of how to get the 2-class detection to work?

I encounter this situation before. My solution was increasing the number of training epoch to more than 300 epoch and increase the samples of the training set.

@lesterlo Do you know at what epoch your model started showing signs of recognizing two classes?

@colphin Between 100-150 epoch. Sometimes it needs more than 200 epoch

Thanks, I've increased my training to 3855 and validation to 1969, and set the epoch to 1000, I'll report back if this worked out for me.


Move path-related fixtures into their own module

neon_fixtures.py has grown into quite a beast.

test_output_dir seems like a good candidate for moving to the new file too. And get_self_dir() from utils.py. Maybe shared_snapshot_dir and test_overlay_dir too, although they're a little more tightly coupled with storage.
I think you'll need to add imports to many tests that use these fixtures, but the CI will flag those :-)

Hmm, some of these aren't fixtures. Would you like me to make them fixtures?

Hmm, some of these aren't fixtures. Would you like me to make them fixtures?

I was just thinking of moving them as is. No opinion if they should be fixtures.

Just feels like we are overloading a directory called fixtures. For now, I'll move them as is, like you suggest. Can defer more re-organization to later.

I'm just gonna get rid of get_self_dir(). I'll evaluate the rest after https://github.com/neondatabase/neon/pull/9306 is merged.

Waiting on https://github.com/neondatabase/neon/pull/9303 to merge before pushing up my latest changes. No sense in needlessly spinning the CI.

This PR is ready to go.


[Bug Report] build error

Element UI version
1.3.7
OS/Browsers version
win10
Vue version
2.3.4
Reproduction Link
https://jsfiddle.net/pj71jkyw/
Steps to reproduce
npm run build
// 去除 webpack 的 UglifyJsPlugin 编译正常
What is Expected?
build success
What is actually happening?
ERROR in static/js/vendor.74e75a6a11ba645ad266.js from UglifyJs
Unexpected token: punc (() [static/js/vendor.74e75a6a11ba645ad266.js:126197,10]

Issues without a reproduction link will be closed directly.


layout or display issue

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version: 1.81.0
OS Version: windows 64

Steps to Reproduce:

minimize the vs code window
try to publish a repo to GitHub
encountering a layout or display issue within (VS Code) that is affecting the ability to interact with the OK
button when trying to publish a repository to GitHub.

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.81.0. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

@sbatten, @TylerLeonhardt could you chime in on this one? Thank you!

Gonna wait on advice from @sbatten

This doesn't repo on macos simply because the width of the controls is smaller but the problem exists on both. The simplest fix is to reserve more space on Windows on the sides of the quick pick. Otherwise you have to worry about the useable area


chore: always use react strict mode

PR includes

[X] DX

Branch title and PR header don't pass contribution guide

Could you plz elaborate. Do you want me to change branch name speed/strict-mode => issues/strict-mode? according to docs
And I didn't get the comment about PR header.
Thanks in advance

You should first create an issue  describing the problem you're trying to fix and then put the issue header in the PR title field.

You should first create an issue describing the problem you're trying to fix and then put the issue header in the PR title field.

I've fixed it in another PR, this PR will be closed.


new content build without dependencies and pyenv

Trying a new approach for the content build where we use virtualenv and circle ci caching. Thus, reducing the build of our build image.

Docker Image Ready - Dev
Docker automatic build at CircleCI has deployed your docker image: devdemisto/content-build:<IP_ADDRESS>68
It is available now on docker hub at: https://hub.docker.com/r/devdemisto/content-build/tags
Get started by pulling the image:
docker pull devdemisto/content-build:<IP_ADDRESS>68

Docker Metadata

Image Size: 634.83 MB

Image ID: sha256:baf667f4536240021e0451ce446bf7bc11c1e6471bfa1d55210e85697d5b9e02

Created: 2019-11-02T16:52:27.037496485Z

Arch: linux/amd64

Command: ["/bin/sh"]

Environment:

PATH=/home/circleci/.local/bin:/home/circleci/bin:/usr/local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
LANG=C.UTF-8
GPG_KEY=0D96DF4D4110E5C43FBFB17F2D347EA6AA65421D
PYTHON_VERSION=3.7.5
PYTHON_PIP_VERSION=19.3.1
PYTHON_GET_PIP_URL=https://github.com/pypa/get-pip/raw/ffe826207a010164265d9cc807978e3604d18ca0/get-pip.py
PYTHON_GET_PIP_SHA256=b86f36cc4345ae87bfd4f10ef6b2dbfa7a872fbff70608a1e43944d283fd0eee
DEBIAN_FRONTEND=noninteractive
NODE_VERSION=10.16.3
YARN_VERSION=1.17.3

Labels:

org.opencontainers.image.authors:Demisto<EMAIL_ADDRESS>org.opencontainers.image.revision:c2c99df50fa119043ec70109a5c7e1a06331537d
org.opencontainers.image.version:<IP_ADDRESS>68

what about the other docker image (content-build-2and3)? why we are keeping it?

Keeping it for history. In case we want to go back.


thread '' panicked at 'arithmetic operation overflowed'

When I try to load a JPEG file I get the following error:
thread '<main>' panicked at 'arithmetic operation overflowed', ./src/jpeg/entropy.rs:147

This seems to happen with any JPEG. The issue exists in the opening.rs example.

Are you using the most recent version of the image crate?  This should have been fixed a few days ago.

Yes, at least as far as I can tell. This happens after I clone the repo, build it and build the opening.rs example.

Happens for me as well, same error on several JPEGs. Here's an example build that failed at runtime. (2 days ago, but after the supposed fix)

Could you provide a backtrace to help diagnose the error?

I don’t think we fixed all overflows.

Here's a traceback, built with rustc 1.0.0-nightly (cfea8ec41 2015-03-10) (built 2015-03-11) and cargo 0.0.1-pre-nightly (66849de 2015-03-10) (built 2015-03-10). The git checkout by cargo is at commit 92a5cec81b08bfd4e829bf0e2873575934d2ee3a.
± % RUST_BACKTRACE=1 cargo run --bin=day12                                                                                !10040
    Running `target/debug/day12`
24 days of Rust - image (day 12)
thread '<main>' panicked at 'arithmetic operation overflowed', /home/zbyszek/.cargo/git/checkouts/image-f4d4ca6613133df7/master/./src/jpeg/entropy.rs:147
stack backtrace:
1:     0x7f1060269142 - sys::backtrace::write::haa06f2eb4ff4d5e5ADA
2:     0x7f106026d0b2 - panicking::on_panic::hdcb20beee702c0b03IJ
3:     0x7f106025ee19 - rt::unwind::begin_unwind_inner::hbe159b4d97e14ee66oJ
4:     0x7f106025f1c1 - rt::unwind::begin_unwind_fmt::haee4ef7e01d3657fHnJ
5:     0x7f106026c9d7 - rust_begin_unwind
6:     0x7f1060298514 - panicking::panic_fmt::h5ce132f2ef412bf4HZs
7:     0x7f106029843d - panicking::panic::h4135742065e40164TXs
8:     0x7f106018aa17 - jpeg::entropy::derive_codes_and_sizes::h9fc1744702218dccnhk
                        at /home/zbyszek/.cargo/git/checkouts/image-f4d4ca6613133df7/master/./src/jpeg/entropy.rs:147
9:     0x7f106018d0d6 - jpeg::entropy::derive_tables::h3e1769f62f7e171bulk
                        at /home/zbyszek/.cargo/git/checkouts/image-f4d4ca6613133df7/master/./src/jpeg/entropy.rs:173
10:     0x7f10601eef3a - jpeg::decoder::JPEGDecoder<R>::read_huffman_tables::h4735152126459403654
                        at /home/zbyszek/.cargo/git/checkouts/image-f4d4ca6613133df7/master/./src/jpeg/decoder.rs:459
11:     0x7f10601ed80e - jpeg::decoder::JPEGDecoder<R>::read_metadata::h5388995571800148850
                        at /home/zbyszek/.cargo/git/checkouts/image-f4d4ca6613133df7/master/./src/jpeg/decoder.rs:274
12:     0x7f10601ed2bd - jpeg::decoder::JPEGDecoder<R>.ImageDecoder::colortype::h17242995496453324886
                        at /home/zbyszek/.cargo/git/checkouts/image-f4d4ca6613133df7/master/./src/jpeg/decoder.rs:553
13:     0x7f10601ec278 - dynimage::decoder_to_image::h13845769526475690536
                        at /home/zbyszek/.cargo/git/checkouts/image-f4d4ca6613133df7/master/./src/dynimage.rs:423
14:     0x7f10601c36d2 - dynimage::load::h8503650011569077649
                        at /home/zbyszek/.cargo/git/checkouts/image-f4d4ca6613133df7/master/./src/dynimage.rs:559
15:     0x7f10601c1138 - dynimage::open::h4d9e0b0b0409b7d1fPq
                        at /home/zbyszek/.cargo/git/checkouts/image-f4d4ca6613133df7/master/./src/dynimage.rs:523
16:     0x7f10601167a0 - main::haa985ea1b3d1679foaa
                        at src/day12.rs:13
17:     0x7f10602711f8 - rust_try_inner
18:     0x7f10602711e5 - rust_try
19:     0x7f106026e800 - rt::lang_start::h9871739369611a7ejDJ
20:     0x7f1060117584 - main
21:     0x7f105fb35ec4 - __libc_start_main
22:     0x7f10601165c8 - <unknown>
23:                0x0 - <unknown>
An unknown error occurred

To learn more, run the command again with --verbose.

This is not solved for me. Here's an image that causes the bug: http://fuskbugg.se/file/deoBTg/P1010529.jpg. Backtrace:
~/image $ RUST_BACKTRACE=1 ./opening P1010529.jpg
thread '<main>' panicked at 'arithmetic operation overflowed', ./src/jpeg/decoder.rs:209
stack backtrace:
   1:     0x7fa9bfefd642 - sys::backtrace::write::haa06f2eb4ff4d5e5ADA
   2:     0x7fa9bff01292 - panicking::on_panic::hdcb20beee702c0b03IJ
   3:     0x7fa9bfef3319 - rt::unwind::begin_unwind_inner::hbe159b4d97e14ee66oJ
   4:     0x7fa9bfef36c1 - rt::unwind::begin_unwind_fmt::h538254dabdf1d6dbHnJ
   5:     0x7fa9bff00bb7 - rust_begin_unwind
   6:     0x7fa9bff2c714 - panicking::panic_fmt::hd9bfa4da86a3b50cHZs
   7:     0x7fa9bff2c63d - panicking::panic::haeeb941f9623f4dfTXs
   8:     0x7fa9bfe9ea4c - jpeg::decoder::JPEGDecoder<R>::decode_mcu::h16681377858681548104
                        at ./src/jpeg/decoder.rs:209
   9:     0x7fa9bfe9df8d - jpeg::decoder::JPEGDecoder<R>::decode_mcu_row::h10512436574909087948
                        at ./src/jpeg/decoder.rs:177
  10:     0x7fa9bfe9da1d - jpeg::decoder::JPEGDecoder<R>.ImageDecoder::read_scanline::h7914295650239136969
                        at ./src/jpeg/decoder.rs:582
  11:     0x7fa9bfe9d3b1 - jpeg::decoder::JPEGDecoder<R>.ImageDecoder::read_image::h3871398705554507924
                        at ./src/jpeg/decoder.rs:606
  12:     0x7fa9bfe94590 - dynimage::decoder_to_image::h7917595641188824261
                        at ./src/dynimage.rs:424
  13:     0x7fa9bfe6b812 - dynimage::load::h8796976204864138992
                        at ./src/dynimage.rs:559
  14:     0x7fa9bfe69278 - dynimage::open::hc6f3ea251803955dmPq
                        at ./src/dynimage.rs:523
  15:     0x7fa9bfdd016f - main::hc384947efbfd4b22iaa
  16:     0x7fa9bff053d8 - rust_try_inner
  17:     0x7fa9bff053c5 - rust_try
  18:     0x7fa9bff029e0 - rt::lang_start::h9871739369611a7ejDJ
  19:     0x7fa9bfdd066e - main
  20:     0x7fa9bf809ad4 - __libc_start_main
  21:     0x7fa9bfdcfee8 - <unknown>
  22:                0x0 - <unknown>
~/image $

It seems to be solved for some images though, as nothing worked yesterday and some images have worked today.

As a workaround you can just use your program in release mode. This disables the overflow checks.

Aha! Thank you, that'll work for now.

Do you anticipate fixing this in the near future? Can I help in some way? While compiling with the --release flag is a workaround, it's also a pretty substantial impediment to the programming workflow.

This is a annoying bug because it was revealed due to changed overflow semantics in rustc. We anticipate fixing it at some point, we are just missing man power to do that timely. So help is welcome. In principle all shifts and additions have to be replaced by wrapped_*.
I am not sure about the real cause I suppose it is a minor bug in the decoder.

@nwin: I'll be happy to stamp out any overflow panics I can find.

closing for now as the known test cases work now after #412 got merged

I am getting the same panic with 0.3.11.
thread 'test_cluster_color' panicked at 'arithmetic operation overflowed', /home/shiv/.cargo/registry/src/github.com-0a35038f75765ae4/image-0.3.11/./src/jpeg/entropy.rs:73
Is there a work-around? Thanks. --shiv--

@00shiv: Yes, as mentioned earlier, it seems to work if you build in release mode (cargo build --release).

Sorry. I should have added that doing so just moves the error to a slightly later stage.
thread '' panicked at 'called Result::unwrap() on an Err value: FormatError("Could not decode symbol.")', ../src/libcore/result.rs:731

@00shiv: And you have no unwraps in your own code? Make a backtrace when that error occurs, and you will be more likely to get some help :)

I do. But I thought it was coming out of the unwrap on the load call. I'll double check. Thanks.


Add Chinese(zh-tw) translations

Fixes Or Enhances # .
Make sure that you've checked the boxes below before you submit PR:

[x] Tests exist or have been written that cover this particular change.

Change Details:

related to #405

@go-playground/admins

Coverage remained the same at 100.0% when pulling 532cde1085aad0bfb8ae2a5fa41aab2493035528 on kanozec:v9 into f8af4b15dbe132b53d3a53e7c3724271040e82e7 on go-playground:v9.


question about the cal_dataset

hello, I want to prune a llama2 7b model which is pretrained with alpaca dataset and then finetuned with my own dataset. In this case, should i reset all the adapters, or can still use llama2 adapters. Besides, when i choose the cal_dataset for slicing the model, should i choose the alpaca dataset or my own dataset, which is not included in the finetuning dataset before.
looking forward to the reply.

Hi, if I understand correctly you have a llama2 7b just with new weights - in that case you can use the llama2 adapter, and load the   weights from a local checkpoint using hf_utils.get_model_and_tokenizer.
As for the cal_dataset for slicing, you can use whatever dataset you prefer but it makes sense to slice with data which was used for finetuned. A mix of finetuned and pretraining data should work too!


FAILURE: Failed to create Azure AD application. Exiting...

Actual behavior: Not verbose information log for the fail result.
Expect behavior: Success create Azure AD application

Thanks for reporting this issue. Could you please double check that you have the permission to create a AAD Application Registration through the Azure Portal in that directory?
We are in the process of rewriting that script to emit better error messages.

Yes, able to create through the Azure Portal.

I just updated the script to printout the exception. Could you please pull down the script again and rerun it? It should print out the problem

Connect-AzureAD : Object reference not set to an instance of an object.
At /home/yicheng/workbenchAADSetup.ps1:72 char:16
+ $currentUser = Connect-AzureAD -TenantId $TenantName
+                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo          : AuthenticationError: (:) [Connect-AzureAD], AadAuthenticationFailedException
+ FullyQualifiedErrorId : Connect-AzureAD,Microsoft.Open.Azure.AD.CommonLibrary.ConnectAzureAD

But I can manually create an AD application then get the GUID and key.

I'm wondering if you're using a different account when you get prompted for logging in through powershell.
When you are prompted for navigating to

WARNING: To sign in, use a web browser to open the page https://microsoft.com/devicelogin and enter the code BB3SF9NJN to authenticate.

Could you open https://microsoft.com/devicelogin in an incognito window and login with the same account you do as the portal?

It will ask to pick an account after the code enter, and seems it's same account.

And you got the same error? There seems to be some problem with the login


dark theme

Is there a way to support dark theme? basically white font and black  background.

Would love a dark material theme. Or at least one that work with dark jenkins stylish theme.
I am using the Dark Jenkins Stylish theme in addition, but when looking at Console Output the background is grey-ish with black text.

+1 this would be really nice. FWIW the existing themes render nicely with the Dark Reader Chrome and or Firefox plugin. It would be nice if this was native for Android / iOS viewing though.

+1 !!!!!
I am currently using chrome extension that darkens webpages in general, but its not perfect on the material theme. A native dark mode would be a huge improvement!!!

Add below code as an Extra CSS in Theme section. It might not be the best fit but it help a lot.
body, form, p, table, td, th {
    color: #ffff ! important;
    background-color: #333 ! important;
}
#side-panel .task-link {
    color: #fff;
}
.pane.build-details a, .pane.build-details a:visited {
    color: white;
    opacity: 0.6;
    text-decoration: none;
}
.cbwf-dialog {
    border-radius: 4px;
    border: solid 1px #d7d7d7;
    background-color: #666;
    box-shadow: rgba(0, 0, 0, 0.25) 0 0 0 999em, rgba(0, 0, 0, 0.25) 0 0 0 1px, rgba(0, 0, 0, 0.33) 0 3px 10px;
}

.cbwf-dialog .header {
    border-radius-topleft: 4px;
    border-radius-topright: 4px;
    background-color: #666;
    padding: 7px 10px;
    font-weight: bold;
    font-size: 1.2em;
}

.cbwf-stage-logs .node-name {
    padding: 5px 10px;
    background-color: #666;
    border-radius: 4px;
    cursor: pointer;
}

Jenkins (since v2.239) is now supporting an official dark plugin (but those ugly icons): could it be a starting point to port this awesome theme to a dark flavour?

A true dark mode would be awesome. The dark theme for jenkins is nice, but the icons are so heinous.

That would be awesome.
+1

+1


Alpha Version - Bulk Deletion Feature

Fixes #76
Users are now able to delete multiple contacts in one go.
Initial contacts:

Command: Delete 1 3 (persons of indices 1 & 3 are deleted)

Duplicate handling: Delete 1 1 (only person of index 1 is deleted)

LGTM!


Alignment of AND in JOIN ... ON

Hello,
it was mentioned that SQL statements or not yet really in focus for ABAP Cleaner.
So I suppose, the following thing is not yet supposed to work nicely, or is it?
Rule "Align SELECT ... FROM ... JOIN", in the example, I find the position of the AND irritating:

The END should be aligned with the ON, or the equal signs aligned.
I could not make it work nicely with reconfiguring the rule, either.
(And anyway, in my company we will try to stick to the default.)
Best regards,
Edo

Hi Edo,
you're right, the equals signs in this condition should be aligned – however, when I tried your example, it worked fine. This is probably from the example code for the "Align SELECT ... FROM ... JOIN" rule, right? Then it is simply a misunderstanding: Each of those "Align SELECT …" rules only does one part of the job, and the alignment of the ON clause is done by yet another rule, the "Align logical expressions" rule. So, if you copy the example to the main window of ABAP cleaner, things should look fine, because there, all rules are executed:

You can try it this way:

either open the standalone version of ABAP cleaner, or from ADT, use menu "Source Code / Show Read-Only Preview …" (because this menu allows to paste code to the main window of the ABAP cleaner UI)
press "Configure…" and click on the "Align SELECT ... FROM ... JOIN" rule
select entire example code and press Ctrl+C to copy the right-hand side, or Ctrl+Shift+C to copy the left-hand side
close "Profiles and Rules" window
press Ctrl+V to have all cleanup rules executed on the example code

Kind regards,
Jörg-Michael

Hi Jörg-Michael,
thanks for the explanation, that makes perfect sense!
Herzliche Grüße aus Lübeck,
Edo


Offset.fetch(payload, cb) does not return latest offset before the given time

I would like to be able to search an offset by timestamp using kafka-node, and it looks like the Offset API is supposed to offer a way to do that using the fetch method.
Currently, I am not getting the behavior described in the documentation for the Offset.fetch() method. I am passing the following OffsetRequest, {topic: 'my-topic', partition: 0, time: Date.now()}, to the method. Since I am not producing any new messages to the topic, I expect the latest offset in the topic to be returned in the response (e.g., {'my-topic': {'0': [ latestOffset ]}}).
However, I am only getting 0 as the offset in the response. It seems like the returned offset is 0 for any time argument other than -1 (latest) (0 is expected for -2, earliest, since the earliest offset in my topic is 0).
Is searching offsets by timestamp implemented in kafka-node yet?
Environment

Node version: 10.10.0
Kafka-node version: 4.1.3
Kafka version: 2.2.0

Sample Code
const kafka = require('kafka-node');

let client = new kafka.KafkaClient({kafkaHost: 'localhost:9092'});
let offset = new kafka.Offset(client);

console.log(`Getting records before ${new Date(Date.now())}.`)

let payloads = [{topic: 'my-topic', partition: 0, time: Date.now()}];
offset.fetch(payloads, (err, data) => {
        if (err) console.log('Error: ', err);
        else {
            console.log(data);
            // logs the following:  { 'my-topic': { '0': [ 0 ] } }
        }
});

Looks like we only have v0 of the offset request implemented. It should not be difficult to implement v1 to get this.

@hyperlink
There are difference in offset response between v0 and v1

// v0
ListOffsetRequest => ReplicaId [TopicName [Partition Time MaxNumberOfOffsets]]
ReplicaId => int32
TopicName => string
Partition => int32
Time => int64
MaxNumberOfOffsets => int32

// v1 (supported in <IP_ADDRESS> and later)
ListOffsetRequest => ReplicaId [TopicName [Partition Time]]
ReplicaId => int32
TopicName => string
Partition => int32
Time => int64

In v1 response there are only one offset with timestamp:
{
  size: 50,
  correlationId: 2,
  topicNum: 0,
  topic: 'test',
  partitionNum: 0,
  partition: 1,
  errorCode: 0,
  timestamp:<PHONE_NUMBER>574,
  offset: 100
 }

Could you provide model for offsetV1Response?
e.g.:
// For existing timeindex
{ 'test': {
    '1':  {  timestamp:<PHONE_NUMBER>574,  offset: 100  }
  }
}

// For not existing timeindex
{ 'test': {
    '1':  {  timestamp: 0,  offset: 0  }
  }
}

I also seem to experience similar issues.
Whenever I provide Date.now() as an input value for ‘time’ It returns some offset, which is not equal to ‘latest’ (possibly rather a last committed offset (?)). Now if I provide a timestamp other (earlier) than Date.now(), eg 2 days earlier, the method returns the ‘latest’ offset. This is procures not what I would expect. Running latest version of kafka-node on a Confluent Kafka deployment.


Add list schedule command

[x] Add list-s logic to command and parser (completed on https://github.com/AY2324S1-CS2103T-T17-3/tp/pull/106/commits/fecea099b25114c169be34cb25e4d6182f7dd188 )
[x] Update UI to show the list of schedules (completed on https://github.com/AY2324S1-CS2103T-T17-3/tp/pull/106/commits/e99664b2ae227881c88259ac794f2d584d5e6a3e )

UI is not included in coverage, hence will not pass.


[WIP] feat(Flex): replace Flex.Gap with adding margins on the elements

Fixes the issue with rendering double gap between elements if the one between them is hidden. Does not render additional element for the gap => reduced amount of rendered dom elements.
Previously:

Now:

Warnings

:warning:
There are no updates provided to CHANGELOG. Ensure there are no publicly visible changes introduced by this PR.

  Generated by :no_entry_sign: dangerJS

For some reason one of the examples for the Flex is difference, very minimal difference between the Flex.Items when the size prop is used.. (Anybody knows why is this happening?)


(SIMP-6445) Updated static assets

SIMP-6445 #close
https://gitlab.com/simp/pupmod-simp-haveged/pipelines/59665379

WIP until after SIMP 6.4.0 Alpha is released

Decided to take a different tack on the assets moving forward.


Iframe is dead

I ran into that problem today,
the Iframe link is showing an empty page (I also tried with a new note in case)
I'm currently investigating, it seems it is not related to asIframe css since loading the paragraph without asIframe options doesn't work either (empty content inside the paragraph)
I'm following 2 tracks for this bug:

Check the Context and that the query send data
Check the route and that the route parameters are used correctly

Does IFrame work now?

I can try it again, but that bug was supposed to be fix in #203

It was fixed, I close the issue


(PE-30638) Raise PluginNotSupported error for unsupported plugins

Update bolt-servers project_inventory_targets to raise informative errors when unsupported or unknown plugins are encountered in a project's inventoryfile.

Just pushed this to collaborate with Enis on 30638. Will rebase and clean up when that is merged. Added DMN for now.


Org IdPs

Separates items into components
Full stub for IdPs with need to plug in data

Right now, there is a CORs error when trying to update from localhost. I was not able to fully verify yet.


i18n-js and ember-cli-mirage

Hello
I'm building and app with ember on the top of rails with [ember-cli-rails[(https://github.com/thoughtbot/ember-cli-rails) and the project use i18n-js without any problem when running the app from rails. But when I want to run the test. Uncaught ReferenceError: I18n is not defined. Because run alone without rails when running test, I've tried to add the script to the footer of my index page who is used to run the test
<!DOCTYPE html>
<html>
  <head>
    <meta charset="utf-8">
    <meta http-equiv="X-UA-Compatible" content="IE=edge">
    <title>Front Tests</title>
    <meta name="description" content="">
    <meta name="viewport" content="width=device-width, initial-scale=1">

    {{content-for 'head'}}
    {{content-for 'test-head'}}

    <link rel="stylesheet" href="assets/vendor.css">
    <link rel="stylesheet" href="assets/front.css">
    <link rel="stylesheet" href="assets/test-support.css">

    {{content-for 'head-footer'}}
    {{content-for 'test-head-footer'}}
  </head>
  <body>

    {{content-for 'body'}}
    {{content-for 'test-body'}}
    <script src="assets/vendor.js"></script>
    <script src="assets/test-support.js"></script>
    <script src="assets/front.js"></script>
    <script src="testem.js"></script>
    <script src="assets/test-loader.js"></script>
    <script src="../../app/assets/javascripts/i18n/translation.js"></script>

    {{content-for 'body-footer'}}
    {{content-for 'test-body-footer'}}
  </body>
</html>

But it's still undefined.
Can i18n-js can be loaded here ?
Maybe the best is to stop using i18n-js and turn to something only on the ember app for the translation.
Related issues :

On ember-cli-rails
On ember mirage

Try adding
<script src="../../app/assets/javascripts/i18n.js"></script>

The README state to "include" i18n/translation since it already got require statement for sprockets
But sometimes that doesn't work

Thanks for your answer @PikachuEXE. But it doesn't work, I got a 404. I don't have any i18n file. It only works if I copy past the i18n-js code directly in my emberapp/test/index.html. It's very dirty for the moment but I will try to load directly the i18n file in my ember app, need to figure out.

I've finally move my translation code to ember. i18n is now using ember-18n.


Getting garbage output when reading COM port

SerialPort Version: v5.0.0

NodeJS Version: v6.11.2

Operating System and Hardware Platform: Windows 10 64-bit

Have you checked the right version of the api docs?: yes

Are you having trouble installing and you checked the Installation Special Cases docs? N/A

Are you using Electron and have you checked the Electron Docs?: N/A

Summary of Problem
I'm working with an OBD Solutions ECUsim 2000, and I'm getting garbage output with serialport. I have an OBD scanning software running in the background, connected to the same board but over a different COM port, and that back and forth generates data on the terminal. Here's what I'm getting as output:
$ node test.js
parser setup
data received:  rB�^"^J"^J�r�^F�B�J�^J�J�rB"^��r�^J"^J�J�rB"^��rB�>J�J�>J�r"�^�rB�^J�.J�^*�rB^��2B�J�.J�^
data received:  Br"�^�BrB�^J�^J"^J�2B�^��B�^J"^J�^J�rB^��2B�^"^J�^J�rB�^��r"B^J�>J�.
data received:  �rB"^��B�^J�J�^J�2B�.F�rB^J"^J�^J�r"^�Br""^J�^J�^J�B�^&�rB�^J�^J�>
data received:  �rB�.&�rB�^J�J�.J�2B�^��r�^*"^J�J�r"B^�"rB"^J�^J�J�rB"^��rB"^J�>J�^
data received:  B�^F�rB"^J�^J�^J�r"^��rB�>J�^J�.

Steps and Code to Reproduce the Issue
Standard successful install, but with these warnings:
npm WARN enoent ENOENT: no such file or directory, open 'C:\Users\wputnam\package.json'
npm WARN wputnam No description
npm WARN wputnam No repository field.
npm WARN wputnam No README data
npm WARN wputnam No license field.

Used the below code:
const SerialPort = require('serialport');
const Readline = SerialPort.parsers.Readline;
const port = new SerialPort('COM4', {
  baudrate: 115200,
  parity: 'none',
  stopBits: 1,
  dataBits: 8,
  flowControl: false
}, function(err) {
  if (err){
    console.log('error: ', err.message);
    port.close();
}});
const parser = new Readline({delimiter: '\n'});
port.pipe(parser);

console.log('parser setup');

parser.on('data', function(data) {
  console.log('data received: ', data);
});

Terminal requirements according to the manual were hardcoded into the constructor. I've tried casting the data variable into different types of strings as well. Output is normal and readable in Tera Term v4.95 (SVN# 6761) with the same settings:
Tx: 18DAF110 04 41 10 0C E0
Rx: 18DB33F1 01 0D
Tx: 18DAF110 03 41 0D 66
Tx: 18DAF118 03 41 0D 66
Tx: 18DAF128 03 41 0D 66
Rx: 18DB33F1 01 10
Tx: 18DAF110 04 41 10 0C E0
Rx: 18DB33F1 01 0D
Tx: 18DAF110 03 41 0D 66
Tx: 18DAF118 03 41 0D 66
Tx: 18DAF128 03 41 0D 66
Rx: 18DB33F1 01 10
Rx: 18DB33F1 01 0D

so I don't think it's the device's or driver's fault.
(Matter of fact, someone had a similar version of the issue and posted an issue on here in the past, but the .toJSON() function is no longer available, so I can't use that to check.)

The object 'data' is a buffer object, and according to this toJSON  is still an method, though you maybe speaking about something else.
data.toJSON().data works in my case.

@Eliminster0 data.toString('hex') doesn't do anything different. data.toJSON().data returns
$ node test.js
parser setup
(node:1304) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): TypeError: data.toJSON is not a function

I've also already tried the encoding options you mentioned with the former. None of them do anything different.

@reconbot If I add in parser.setEncoding('hex') under the declaration for the Readline, I'll get:
$ node test.js
parser setup
data received:  7222225e4a225e4ac25e4ac27242c21ec6c27222425e4a225e4a225e4ac27242c25ec6c23242c25e4ac25e4a425e4a227222225ec622
data received:  22025e4a025e4a225e4a227202c25e26227242c25e2ac25e2ac25e
data received:  c27242025ec6c27242c25e4ac23e4ac25e4ac27242c25ec6c27242225e4a025e4ac21e4ac27222425ec6c27242c22e4ac25e4ac25e2ac27222425ec6227242c23e4ac22e
data received:  c25e4a227242c25e26427222225e4ac25e4ac25e4ac27242c21ec6c27242c21e4ac25e2ac25e4ac27242c21ec6c23242c22e
data received:  c25e
data received:  c25e4a223242c22e06c27242c25e4ac23e4ac23e
data received:  c23242c25ec622
...

Trying all the encoding options with that function gives me various flavors of garbage. I double checked the encoding on Tera Term, and it uses UTF-8 as well, but it still produces the correct output.
Also, I tried running the same script in my Lubuntu 17.04 VM in VirtualBox with the VM granted access to the COM port. Same version of serialport, but nodejs is v4.7.2. The output behavior is exactly the same on the VM as it is on the Windows machine.

@reconbot Just tried a simple reading Python script in the Lubuntu VM using pyserial v3.4, and I'm getting the actual data from the board as intended. I'm starting to think that my issue may be bug-related.

If I change that line in my JavaScript file from port.pipe(parser) to port.pipe(process.stdout), and comment out the parser.on() function, I get:
$ node test.js
parser setup
rB�^B�."BB�^*�^"^J�2B�>�rB"^J�2B�^B�rB"^B�>B�B�^*B^J"^J�rB"^F�r"^JrB�B�rB�^B�.B�r"�^*B^J�^J�rB^F�r"�^*Br""^B�rBB^BB^B"�^J^J"^J�r"�^F"rB"^J"rB"^B�rB^B"^B�rB"^J�^J�>J�B�.F�r"^J�r"�^�rB�^B�^�rB�^JB^JB^J"rB�.�rB"^J�rB�^B�rB�>"�^*"rB�J�^*�^*r"^F�rB�.J�rB�.B�rB�^B�^B�rBB^J"^J�.*Br"^F"

where the characters are showing up one by one, with no line breaks, and it will keep doing that until I kill the script.

Here's the Python script that I wrote. It's pretty basic:
import serial

ser = serial.Serial('/dev/ttyS3', 115200)
print(ser.name)
n = ""

while True:
    n = ser.read(10)
    print n

Here's an additional observation in case it's relevant. The newline delimiters that this board has been using aren't the norm. In Tera Term, the default delimiter for a new line is CR. However, this setting caused the first line to simply rewrite over itself repeatedly. I had to change the setting to either AUTO or CR+LF, which makes each new entry start on a new line. In Python, I had a similar issue with the newline read function, because that function only uses \n as the delimiter. However, because the data is structured in a certain way, I'm reading this data by getting X bytes at a time with read anyway.
But regardless of how I interpret the newline with pyserial, when I run that above script, I'm going to get something like:
Tx: 18DAF128 03 41 0D 00

(the difference here, of course, is that each character is on a new line, and there are a lot of whitespaces being printed between Rx and Tx lines)
I can then use string I/O to get the data I want.

Finally, here is a link to the User Guide for the board. The instructions for terminal setup are on page 14. (I've installed the drivers from the website mentioned in the manual, and it went through an installation wizard with no issues, so it shouldn't have anything to do with the drivers, especially if Python is picking up the text fine in the VM.)

Hey all, i'm also facing the same issue.
(btw, I'm sending data from arduino)
The only thing i notice is :
if i use baudrate 115200 , it returns garbage.
BUT i'm able to receive non-garbage data if i change the baudrate to 9600.
this is the sample code with 9600
Arduino
void setup() {   // put your setup code here, to run once:   Serial.begin(9600); // baudrate is 9600   Serial.println(); } int counter = 0; void loop() {   // put your main code here, to run repeatedly:  Serial.println(counter);  counter += 1;  if (counter > 10){  counter = 0;  } }
nodejs
var SerialPort = require('serialport'); const Readline = SerialPort.parsers.Readline; var port = new SerialPort("COM4",{"baudrate":9600,"xon":true,"xoff":true}); const parser = port.pipe(new Readline({ delimiter: '\n' }));   parser.on('data', function(data){       console.log(data);   });

Yes, the baudrate matches for every test.
When testing 115200, i also tried to read it with serial port reader application (mobaxterm), and the data came in good.
The only baudrate i remember testing are 115200, 57600, 9600.
i'm using it on Windows 10 64 bit.
btw, the data came in good if i switch to<EMAIL_ADDRESS>

sample code
const SerialPort = require('serialport');
const port = new SerialPort("COM4",{"baudrate":115200,"xon":true,"xoff":true});
port.on('open',function(data){
	console.log("port open");
})
port.on('data', function(data){
	console.log(data.toString('utf8'))
});

sample output
X:55516.00;Y:52896.00;Z:63908.00;GX:65233.00;GY:130.00;GZ:78.00;

X:55576.00;Y:52924.00;Z:63860.00;GX:65303.00;GY:96.00;GZ:25.00;

X:55588.00;Y:52928.00;Z:63948.00;GX:65273.00;GY:127.00;GZ:31.00;

using npm install --save<EMAIL_ADDRESS>, the data came in good.
using npm install --save serialport, which is serialport@latest <EMAIL_ADDRESS>, the data came in as garbage.
using npm install --save<EMAIL_ADDRESS>the data came in as garbage.
also<EMAIL_ADDRESS>sometime unable to connect to port in. in 10 testing, only 4 time it able to produce garbage. the other 6, nodejs just quit with no notice/error.


fix broken URL for TensorBoard

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/Using-TensorBoard-for-Visualization.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

@duli2012 Could you take a review on this one?

approved.


Answer Q8

@zthomae do you want to take care of this? It's the Dieter problem :sunglasses:

I'll try my best to decipher what Kevin wrote in his final exam notes.
plz wish me luck

:four_leaf_clover:

Is this the last problem that needs a solution?

Yes, although it is the dynamic programming Dieter problem. All the other
unlisted numbers are either design or personality.
On Tuesday, February 9, 2016, Nick Heindl<EMAIL_ADDRESS>wrote:

Is this the last problem that needs a solution?
—
Reply to this email directly or view it on GitHub
https://github.com/UW-UPL/InterviewPrepJan2016/issues/6#issuecomment-182162250
.


[server] Fix double-slash in URL

From the Railway logs,
{"level":30,"time":1688525035865,"pid":20,"hostname":"railway","reqId":"req-27","msg":"Route GET://puzzle/projectEuler?id=3 not found"}

Fixed by this commit.


SAA-2216: Separate first and last name in allocation dashboard prisoners and candidates

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

Project coverage is 84.45%. Comparing base (87fffc0) to head (c6b48cc).

Additional details and impacted files
@@             Coverage Diff              @@
##               main    #1192      +/-   ##
============================================
+ Coverage     84.44%   84.45%   +0.01%
- Complexity     3750     3752       +2
============================================
  Files           385      385
  Lines         12690    12700      +10
  Branches       1098     1098
============================================
+ Hits          10716    10726      +10
  Misses         1467     1467
  Partials        507      507

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


Write build command

Guess I forgot about this one. Shouldn't be too hard. But, in doing so, may want to abstract some of the handle functions in dev.js into functions that can be used by both dev and build.

Support functional options like minify and prettier.


Permit https scheme on remote documents

This PR permit remote documents with http and https schemes and changes Net::Http to Open::Uri

Thanks!


fix: nudge: removes unnecessary border calculations in css

SUMMARY:
Using a CSS variable inside of a nested calc function isn't valid SASS, this change removes these property overrides to fix the Size nudge animation, because border is appended to the client rect, these overrides are unnecessary.
https://user-images.githubusercontent.com/99700808/220772475-8745647d-5bb4-4e11-80e0-0a5c44deb2df.mp4
JIRA TASK (Eightfold Employees Only):
ENG-44290
CHANGE TYPE:

[X] Bugfix Pull Request
[ ] Feature Pull Request

TEST COVERAGE:
N/A CSS only
TEST PLAN:
Pull the PR branch and run yarn and yarn storybook. Verify the PrimaryButton story behaves as expected when given the following nudgeProps:
{
  "animation": "size",
  "delay": 5000,
  "enabled": true,
  "iterations": 5
}

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@25b084e). Click here to learn what that means.
Patch has no changes to coverable lines.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@           Coverage Diff           @@
##             main     #547   +/-   ##
=======================================
  Coverage        ?   84.50%
=======================================
  Files           ?      790
  Lines           ?    16711
  Branches        ?     5844
=======================================
  Hits            ?    14122
  Misses          ?     2523
  Partials        ?       66

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


[BACKEND] Send channels to React as array

Right now I'm receiving channels as object of objects and it's kinda bad.

Closing this as we already send channels as array of objects to frontend.


ros2 run rviz2 rviz2

Currently in the deb package there is rviz2 available, but it is not start-able via ros2 run. To enable this would enhance the usability and user experience of rviz.

Yup, this is something we wanted to do before the release, but just didn't have time. Also since the binary is currently statically linked against rviz_common, it is pretty large, so I hesitated to duplicate it. I'm sure we could come up with another way to install the binary once and provide a redirection or script or something to run it the other way.


Manual composer installation failed with error

I tried to install composer the usual way from inside the container but it failed with error message.
Docker container: phpearth/php:7.1-cli
Installation Command
$ curl -sS https://getcomposer.org/installer|php

Error reported by the system.
Some settings on your machine make Composer unable to work properly.
Make sure that you fix the issues listed below and run this script again:

The phar extension is missing.
Install it or recompile php without --disable-phar

build docker container based on 7.1-cli tag and try to install composer manually. I tried to do a manual installation so that I can have the latest version of composer but it failed with above error message.
For now I have used the alpine packaged composer version.

To be able to run Composer on any PHP, you'll need the following extensions:

phar
json
mbstring
openssl
zip
zlib

And also some other recommended packages in general Linux systems (full complete list):

curl
git
subversion
openssh
openssl
mercurial
tini
bash
(many of these might not apply in some app cases)

The composer package from PHP.earth Alpine installs PHP extensions automatically (apk add --no-cache composer)
Otherwise also this will work:
apk  add --no-cache php7.1-phar
curl -sS https://getcomposer.org/installer|php

I'll write more docs on this and check if it can be simplified more. Thanks @samundra for reporting issues.

@petk Thanks for the mentioned packages. I had to use apk add --no-cache composer to finally use composer. I found that it tries to get the latest version which is nice. However I thought I could install it out of the box and was surprised when it didn't.
I think, we should add phar packages by default to our docker boxes.

I agree. Phar is sort of essential extension and doesn't add too much to the Docker image (0.3MB ATM). Added via 5c06d4ec1a80958f0f9ee986a0dc23f7cbf2a98d
I'll leave this opened until I fix the Composer docs chapter also...

Docker & Composer chapter has been updated: https://php.earth/docs/docker/composer with some more info and usage examples. Closing this. In case there's more that needs to be explained, let me know...


Dropping items that check to confirm via dialog box cause item to become invisible

I've noticed that any items that open a dialog box to warn/verify that you want to drop (e.g. based on the limit set in-game) hide the item immediately regardless of whether the drop is confirmed or not. This is especially problematic if you are mid-combat and the dialog box gets interrupted, as it effectively causes the item to disappear from your inventory.
To prevent similar issues, I think following each "hide" action with an inventory state check at the next game tick in order to verify synchronization may help to minimize these sorts of errors, especially if support for gear switches is intended to be added in the near future. It would be very unfortunate to have certain crucial items accidentally become inaccessible from your inventory during difficult PvM and PvP situations.

Yeah sorry about this issue. It is fixed in v1.0.1, but it takes some time for the runelite team to approve the changes :shrug:
Also it's already rapported in #1


document config

What is needed to simply run the basic tests with Gradle

Testing fails with:

PhysicalKeyTest > testS3Uris() FAILED
    org.opentest4j.AssertionFailedError at PhysicalKeyTest.java:33

org.opentest4j.AssertionFailedError: expected: s3://bucket/foo/a+b c?versionId=a%2Fb but was: s3://bucket/foo/a+b c?versionId=a%252Fb


Replacing attention implementation with FlexAttention seems to break Llama3 inference

I tried to replace the attention implementation here
https://github.com/huggingface/transformers/blob/238b13478df209ab534f2195a397dc64a3930883/src/transformers/models/llama/modeling_llama.py#L419
With
def attn_causal(b, h, q_idx, kv_idx, q_len):
    casual_mask = q_idx >= kv_idx
    if q_len > 1:
        return causal_mask
    else:
        return q_idx >= -1 # when q_len == 1, it means you are generating one token at a time
block_mask = create_block_mask(lambda b, h, q_idx, kv_idx: attn_causal(b, h, q_idx, kv_idx, q_len), B = None, H = None, Q_LEN = q_len, KV_LEN = key_states.shape[-2])
attn_output = flex_attention(query_states, key_states, value_states, block_mask = block_mask)

The generation became nonsensical given the same input and temperature, I also compared activation, they seem close enough but not identical.
The only difference in implementation I can think of is the upcasting to 32 bit in the original llama code, but that shouldn't make that much of a difference.
For reference, here is the original HF implementation:
attn_weights = torch.matmul(query_states, key_states.transpose(2, 3)) / math.sqrt(self.head_dim)

if attention_mask is not None:  # no matter the length, we just slice it
    causal_mask = attention_mask[:, :, :, : key_states.shape[-2]]
    attn_weights = attn_weights + causal_mask

# upcast attention to fp32
attn_weights = nn.functional.softmax(attn_weights, dim=-1, dtype=torch.float32).to(query_states.dtype)
attn_weights = nn.functional.dropout(attn_weights, p=self.attention_dropout, training=self.training)
attn_output = torch.matmul(attn_weights, value_states)

These might not be identical, depending on what exactly is being passed in the HF implementation. During decoding, is the HF impl passing in an attention_mask?

attention_mask is used when there are paddings to mask the paddings out.  It shouldn't make a difference in our case, but I can confirm.

@Chillee you are right, HF inserted empty tokens when using static cache.
After masking those out manually, the outputs are normal.

@kyleliang919 would you mind sharing the fix?

@kyleliang919 would you mind sharing the fix?

sure, you need two kinds of masks, one for prefilling context, the other for generative inference as follows.
Also another thing you need to pay attention to is, don't use static cache, it turns out huggingface pre-allocate padding tokens in the cache, it will be a nightmare to handle those tokens dynamically.  Using Dynamic Cache will fix the problem.
def attn_causal(b, h, q_idx, kv_idx):
    causal_mask = q_idx >= kv_idx
    return causal_mask

block_mask = create_block_mask(
                lambda b, h, q_idx, kv_idx: attn_causal(b, h, q_idx, kv_idx),
                B=None, H=None, Q_LEN=query_states.shape[1], KV_LEN=key_states.shape[1]
            )
attn_output = flex_attention(query_states, key_states, value_states, block_mask=block_mask)


add footer with links to useful pages

@betsybookwyrm when you have time could you have a look at this, please?


SSL_CTX_free - Access violation

Hi,
I just encountered a bizarre scenario in a sample client application I was trying out.
Was testing the client against a server using TLS.
A third party library handles the client side communication and this library uses the secure functions we provide to establish secure communication.
I have implemented the secure functions using openssl [Openssl version is 1.1.1l].
The TLS option of my client can be switched ON and OFF, meaning it can have both secure(TLS) and non-secure communication with servers.
For once, after making a successful client-server TLS communication, I stopped my server, switched OFF the TLS option at my client side and tried to establish a connection with the now non-existent server.
To my surprise, I got the below access violation:
First-chance exception at 0x7B8AB83E (libcrypto-1_1.dll) in Client.exe: 0xC0000005: Access violation reading location 0xABABABAB.
After some basic analysis, it was found that this happened when the function SSL_CTX_free was getting called.
I know that this is very limited information to make a query, but I am just looking for some suggestions or early leads.
Can someone tell me what could have possibly gone wrong?
Is there a scenario where the context of previous TLS connection gets reused? If yes, I have not done anything intentionally for this.
Any possible method to check SSL_CTX object before calling  SSL_CTX_free()? I have done the null check but want to know if there is any other validation that could be done before calling SSL_CTX_free().
Thanks in advance and sorry for the limited info I could furnish.
Regards,
Amal

The location 0xABABABAB is interesting. See:
https://www.asawicki.info/news_1292_magic_numbers_in_visual_c

ABABABAB - Used by Microsoft's HeapAlloc() to mark "no man's land" guard bytes after allocated heap memory

So this is heap memory which is not allocated to the application but is nonetheless being read. I guess you need to figure out why. Perhaps a double free, or an attempt to free an uninitialised value?

Hi @mattcaswell
Thanks for the reply.
In fact the location is not a constant, although once in a while it does show up.
Below is the error I got on 5 iterations of the same steps to reproduce the issue:
First-chance exception at 0x7B0C8C4E (libcrypto-1_1.dll) in Client.exe: 0xC0000005: Access violation reading location 0x0000002C.
First-chance exception at 0x773AFEE5 (ntdll.dll) in Client.exe: 0xC0000005: Access violation writing location 0x00000004.
First-chance exception at 0x7AFFB83E (libcrypto-1_1.dll) in Client.exe: 0xC0000005: Access violation reading location 0xABABABAB.
First-chance exception at 0x773AFEE5 (ntdll.dll) in Client.exe: 0xC0000005: Access violation writing location 0x00000004.
First-chance exception at 0x7B0C8C4E (libcrypto-1_1.dll) in Client.exe: 0xC0000005: Access violation reading location 0x3E7B8FD9.
The API call remains the same SSL_CTX_free.
In between, I was wondering if after calling SSL_CTX_free, do we need to set the SSL_CTX parameter to NULL?
Could see this done in some of the samples available online.

The API call remains the same SSL_CTX_free.

Nonetheless the problem is likely to be the same, i.e. attempting to use an object that has already been freed, or possibly using an object pointer that has not been initialised correctly.

In between, I was wondering if after calling SSL_CTX_free, do we need to set the SSL_CTX parameter to NULL?

There isn't a simple yes/no answer to this question - which is more about C than OpenSSL specifically.
SSL_CTX objects are reference counted. When you call SSL_CTX_new() you get an object back with 1 reference. If you call SSL_CTX_up_ref() then it will increment the reference count. When you call SSL_CTX_free it will decrement the reference count. If the reference count drops to zero then the object will be freed and the memory that it was using will be released back to the OS. Any subsequent attempt to use the SSL_CTX after that point is likely to cause a crash.
In other words there must be exactly one call to SSL_CTX_free() for each call to SSL_CTX_new() or SSL_CTX_up_ref().
You must not use an SSL_CTX once it has been freed (the ref count is zero). In order to avoid accidental use many applications will set the pointer to NULL after it has been freed. This is not strictly necessary if your application will never make use of the pointer again anyway - but is often considered good practice.

@mattcaswell
Yes, I get it.
As I mentioned in the first post, the actual handling of the communication is done by a third party library.
It uses the secure functions that we provide to establish secure TLS communication.
So we need to provide a separate function to create the contexts, separate functions to perform read/write operation and finally one separate function to do the cleanup.
It is in the clean up function that we free up the context.
Expectation is that the create context function is invoked first followed by read/write functions and finally the clean up function.
In issue scenario, as per logs, what I am seeing is that the clean up function is getting called without invoking the create context function first.
I am not sure if this is an issue with the third party library logic, but am assuming that an unnecessary SSL_CTX_free is being done even when a SSL_CTX_new has not happened.

In issue scenario, as per logs, what I am seeing is that the clean up function is getting called without invoking the create context function first.
I am not sure if this is an issue with the third party library logic, but am assuming that an unnecessary SSL_CTX_free is being done even when a SSL_CTX_new has not happened.

Right - yeah if you call SSL_CTX_free with a bad pointer (i.e. you didn't call SSL_CTX_new first) then this will definitely cause this crash. Make sure you don't do that :-)

Thanks @mattcaswell


[Feature Request] Add auto backup for internal database

Explain in detail what your suggested feature would be used for.
Add auto-backup & restore like doing to VRC Registry.
Describe how it would look if it requires a UI.
Using same/simmilar UI to VRC Registry Backup feature will enough.
Explain why people would want to use it.
I lost all my old datas, favorated worlds that is not public anymore right after update.
Settings and session data also lost. I need to put youtube API key again.
No backup or pre-update data can not be found.
This feature will prevent that happening on future.

I'm not sure how @Natsumi-sama would feel about implementing this, but the VRCX database can easily get into the multiple-gigabyte range. Adding automatic backup will cause VRCX to use way more storage in those cases. I'm not opposed to adding this just the storage usage is a concern.

Post note,
If you upgraded from a fairly old version a database resiliency feature was enabled (WAL), plus a database cleaning is run along with that. So if you closed it during that yeah that'll explain your database corruption.

It's a long time requested feature that would be nice to have but yea getting around those storage concerns is an issue, maybe having a toggle to disable it for those with very small C:\ drives would be good enough.

How about backup only few datas like internal favorated world/avatar and settings? They included on DB and they are main reason for requesting it

I'm for this being implemented. For ideas if you decide to do it, maybe have it off-by-default & prompt the option to enable it before updating after implementing it? It could even show/warn about the estimated space required if they decide enable the feature.


EDS Boolean getters return NaN

I think their may be a bug in the latest changes for the EDS getters where the data is defined as boolean, as the parseInt function is returning NaN instead of an integer value and hence the "this.device.eds.lssSupported" in the LSS.init function is always false. May be the same issue in other locations.

Good catch, should be fixed now


Updated documentation for forward all emails

Added the case for how to forward all emails from one domain to an email address.

Ahh I meant to merge this into the arm branch...Github is not very intuitive...sorry @zixia


Debug RPC fixes/improvements

Minor fixes in Call Tracer (e.g. gas used type and binary fields in JSON)
Added call tracing of function calls between C++ contracts
The 4 overloads of ContractHost::callContractFunction() were reduced to a single 1
ContractHost::callContractFunction() is now ContractHost::callContractFunctionImpl() as a new layer of logic was required to do the tracing when enabled
Added tracing for transfer calls

SonarQube is complaining about code duplication in ContractHost. We will fix that, but not in this branch. We should do it in the refactoring task.


RTL support to auth app

RTL suuport to auth app
Issue: https://github.com/cortezaproject/corteza-locale/issues/14#

@chenraz, thank you for the PR and the support, the RTL functionality has been added to the webapp via:

https://github.com/cortezaproject/corteza-webapp-compose/pull/349
https://github.com/cortezaproject/corteza-webapp-admin/pull/91

The RTL functionality respects the browser language that is assumed via the Vue i18n package.
Closing this one.


Bug: passes validation even though incorrect url

Using v2.0.0
Any url that contains // + domain appears to pass validation. However, if you prefix a colon :, you can now add any string before :// + domain, and the test will still pass as a valid url.
Passes as valid url:
//google.com
sdlkjasdfoiklnsadf://google.com

Both of those are valid URLs:

Protocol-relative URL.
URL with a custom protocol.

Gotcha, thanks for the clarification, @sindresorhus.


iPad mini 4 on iOS 12.1.1 b3 (16C5050a), 'STATUS: Unsupported' on Unc0ver 3.0.0~b29 and b34

Hello!
Just upgraded a iPad Mini 4 (iPad4,4) from 10.2 to 12.1.1 b3 and installed unc0ver b34 (then also b29) which both yield:
[*] STATUS: Unsupported
Happy to help if I can provide information.
Thanks for the great work! 👍

Maybe an duplicate of issue 549 (same issue but different hardware, iPad mini 2).

Mistakenly interpreted iPad4,4 as iPad Mini 4. So this is dup of #549

Same problem #549 but other model, but that is because my chipset ain't supported yet; A7. Maybe A8 isn't supported yet either.

I've corrected the title to reduce the confusion.

Hello! I was able to jailbreak my device with the latest build (3.0.0~b37) but in my case Cydia din't show up. Do you have the same problem?
Kind regard


Link to documentation not working

The readme links this page as documentation: https://docs.muetsch.io/pyquadkey2/. Unfortunately the link seems to be wrong, this page does not exist (returns currently HTTP 404).
Maybe this is the correct documentation link: https://github.com/muety/pyquadkey2/tree/master/docs? Or is there another more extensive documentation?

Fixed.


JWS Verification Error in dehydrated

Hey!
2 days ago I had to bump the version of this module to latest due to the ACME v1 deprecation. After bumping this module, some certificates could successfully renew in isolation, but certificates that are receiving sustained amounts of traffic appeared to be making the server crash during generation, which was causing us to hit Lets Encrypt's rate limits as the process was incomplete.
Looking in the logs, I was getting very similar log output that I mentioned here:
https://github.com/GUI/lua-resty-auto-ssl/issues/136
notice signal 15 (SIGTERM) received, exiting
notice signal 15 (SIGTERM) received, exiting
notice signal 14 (SIGALRM) received
notice signal 14 (SIGALRM) received
notice signal 14 (SIGALRM) received
notice signal 14 (SIGALRM) received
notice signal 14 (SIGALRM) received
notice signal 14 (SIGALRM) received
notice signal 14 (SIGALRM) received
notice signal 14 (SIGALRM) received
notice signal 14 (SIGALRM) received
notice signal 14 (SIGALRM) received
notice signal 14 (SIGALRM) received
notice signal 14 (SIGALRM) received
notice signal 17 (SIGCHLD) received
notice signal 17 (SIGCHLD) received
alert worker process 19879 exited on signal 9
alert worker process 19879 exited on signal 9
alert worker process 19879 exited on signal 9
alert shared memory zone "auto_ssl" was locked by 19879
alert shared memory zone "auto_ssl" was locked by 19879
alert shared memory zone "auto_ssl" was locked by 19879
notice exit
notice exit
INFO openresty (exit status 0)
INFO 'openresty' with pid 10560
notice using the "epoll" event method
notice using the "epoll" event method
notice openresty/<IP_ADDRESS>
notice openresty/<IP_ADDRESS>
notice built by gcc 4.9.2 (Debian 4.9.2-10)
notice built by gcc 4.9.2 (Debian 4.9.2-10)
notice OS: Linux 4.4.0-1092-aws
notice OS: Linux 4.4.0-1092-aws
notice getrlimit(RLIMIT_NOFILE): 1048576:1048576
notice getrlimit(RLIMIT_NOFILE): 1048576:1048576
notice start worker processes
notice start worker processes
notice start worker process 10588
notice start worker process 10588
notice signal 17 (SIGCHLD) received
notice signal 17 (SIGCHLD) received
info waitpid() failed (10: No child processes)
notice signal 17 (SIGCHLD) received
notice signal 17 (SIGCHLD) received
info waitpid() failed (10: No child processes)
notice [lua] start_sockproc.lua:11: auto-ssl: starting sockproc, context: init_worker_by_lua*
notice [lua] start_sockproc.lua:11: auto-ssl: starting sockproc, context: init_worker_by_lua*
CRIT reaped unknown pid 19899)
notice signal 17 (SIGCHLD) received
notice signal 17 (SIGCHLD) received
notice signal 17 (SIGCHLD) received
notice signal 17 (SIGCHLD) received
info waitpid() failed (10: No child processes)

I came across this investigation here (https://github.com/GUI/lua-resty-auto-ssl/issues/43#issuecomment-539993756) and decided to bump openresty to openresty/openresty:<IP_ADDRESS>-5-xenial to try and fix the lock issues in lua-resty-core.
The instances that we have running are more stable now, but we keep seeing this error when generating new certs:
error [lua] lets_encrypt.lua:40: issue_cert(): auto-ssl: dehydrated failed: env HOOK_SECRET=xxx HOOK_SERVER_PORT=8999 /usr/local/openresty/luajit/bin/resty-auto-ssl/dehydrated --cron --accept-terms --no-lock --domain xxxx.example.com --challenge http-01 --config /etc/resty-auto-ssl/letsencrypt/config --hook /usr/local/openresty/luajit/bin/resty-auto-ssl/letsencrypt_hooks status: 256 out: # INFO: Using main config file /etc/resty-auto-ssl/letsencrypt/config
ERROR # INFO: Using additional config file /etc/resty-auto-ssl/letsencrypt/conf.d/dehydrated-conf.sh
ERROR startup_hook
ERROR Processing xxxx.example.com
ERROR  + Signing domains...
ERROR  + Generating private key...
ERROR  + Generating signing request...
ERROR  + Requesting new certificate order from CA...
ERROR  err:   + ERROR: An error occurred while sending post-request to https://acme-v02.api.letsencrypt.org/acme/new-order (Status 400)
ERROR
ERROR Details:
ERROR HTTP/1.1 100 Continue
ERROR
ERROR HTTP/1.1 400 Bad Request
ERROR Server: nginx
ERROR Date: Wed, 27 Nov 2019 23:00:58 GMT
ERROR Content-Type: application/problem+json
ERROR Content-Length: 107
ERROR Connection: keep-alive
ERROR Boulder-Requester: 72675174
ERROR Cache-Control: public, max-age=0, no-cache
ERROR Link: <https://acme-v02.api.letsencrypt.org/directory>;rel="index"
ERROR Replay-Nonce: xxxx
ERROR
ERROR {
ERROR   "type": "urn:ietf:params:acme:error:malformed",
ERROR   "detail": "JWS verification error",
ERROR   "status": 400
ERROR }

Have you seen this before? Is there a misconfiguration somewhere in our nginx config, or in dehydrated? I'm not sure if this is related to the locking issue or not, my guess would be no.
Thanks!

I don't think I've seen this before. Based on where that's failing, that seems mostly to be happening on dehydrated's side with the request it's making to issue the cert. Based on some similar issues (https://github.com/go-acme/lego/issues/1006#issuecomment-557026527), I'm wondering if somehow the local account registration needs to be regenerated? You could trigger a new account to be registered by deleting/moving the /etc/resty-auto-ssl/letsencrypt/accounts directory. Then the next issue attempt should create a new account first.
If that doesn't do the trick, then we can debug further by trying to figure out what the JWS payload dehydrated is sending to Let's Encrypt.

I think I'm seeing the same error when renewing certs (haven't had to issue new ones recently). I had thought this error was related to upgrading (#192), but I already updated to 0.13.1 using dehy 0.6.5.:
2019/12/13 08:35:09 [error] 24103#24103: *315594 [lua] lets_encrypt.lua:40: issue_cert(): auto-ssl: dehydrated failed: env HOOK_SECRET=78a061f15ea4f4cd0ec14550328699a25e37076e5f5022c4510db0f578a4c943 HOOK_SERVER_PORT=8999 /usr/local/openresty/luajit/bin/resty-auto-ssl/dehydrated --cron --accept-terms --no-lock --domain www.example.com --challenge http-01 --config /etc/resty-auto-ssl/letsencrypt/config --hook /usr/local/openresty/luajit/bin/resty-auto-ssl/letsencrypt_hooks status: 256 out: # INFO: Using main config file /etc/resty-auto-ssl/letsencrypt/config
# INFO: Using additional config file /etc/resty-auto-ssl/letsencrypt/conf.d/custom.sh
startup_hook
Processing www.example.com
 + Checking domain name(s) of existing cert... unchanged.
 + Checking expire date of existing cert...
 + Valid till Jan 11 07:18:37 2020 GMT (Less than 30 days). Renewing!
 + Signing domains...
 + Generating private key...
 + Generating signing request...
 + Requesting new certificate order from CA...
 + Received 1 authorizations URLs from the CA
 + Handling authorization for www.example.com
 + 1 pending challenge(s)
 + Deploying challenge tokens...
deploy_challenge
 + Responding to challenge for www.example.com authorization...
 + Challenge is valid!
 + Cleaning challenge tokens...
clean_challenge
 + Requesting certificate...
 err:   + ERROR: An error occurred while sending head-request to https://acme-v02.api.letsencrypt.org/acme/new-nonce (Status 000)

Details:

  + ERROR: An error occurred while sending post-request to https://acme-v02.api.letsencrypt.org/acme/cert/046f082998c60c4ec958b81231352b2e920c (Status 400)

Details:
HTTP/1.1 400 Bad Request
Server: nginx
Date: Fri, 13 Dec 2019 08:35:09 GMT
Content-Type: application/problem+json
Content-Length: 112
Connection: keep-alive
Cache-Control: public, max-age=0, no-cache
Link: <https://acme-v02.api.letsencrypt.org/directory>;rel="index"
Replay-Nonce: 0001fgA4Y_cX4LlSjF3J4aj0CUOLQt4skPEGNSqr9Ptb4_g

{
  "type": "urn:ietf:params:acme:error:badNonce",
  "detail": "JWS has no anti-replay nonce",
  "status": 400
}

, context: ngx.timer
2019/12/13 08:35:09 [error] 24103#24103: *315594 [lua] renewal.lua:176: renew_check_cert(): auto-ssl: issuing renewal certificate failed: dehydrated failure, context: ngx.timer

I tried moving the account registration as suggested by @GUI above, then ran a renewal. A new registration key was created, but instead of trying to renew the certificate, it was immediately terminated:
2019/12/13 22:49:25 [notice] 24154#24154: *7910 [lua] renewal.lua:73: renew_check_cert(): auto-ssl: checking certificate renewals for www.example.com, context: ngx.timer
2019/12/13 22:49:25 [notice] 24154#24154: signal 17 (SIGCHLD) received from 26319

On another note, does anyone know how can I obtain the HOOK_SECRET key so I can try running the check on a specific domain by command line? I used to pull it from my error logs, but I can only get it if it actually runs...and it changes. TIA.

Could this issue be related to this one in Dehydrated?
https://github.com/lukas2511/dehydrated/issues/684

Hmm, well this is strange...
I ran the renewal again. This time all of the domains that were failing before were skipped(!), due to being more than 30 days from expiration?! I verified that the certs had in fact been renewed successfully.
Somehow they renewed, but without the normally verbose log output.
I added a new domain and the certificate was issued and the website loaded with the new certificate. But again the logs only show:
2019/12/14 00:14:13 [notice] 1318#1318: *691 [lua] ssl_certificate.lua:94: issue_cert(): auto-ssl: issuing new certificate for www.example1.com, context: ssl_certificate_by_lua*, client: <IP_ADDRESS>, server: <IP_ADDRESS>:443
2019/12/14 00:14:20 [notice] 1318#1318: signal 17 (SIGCHLD) received from 2351

Just in case if anyone run into this issue. This could also be caused by Cloudflare. "Always redirect to SSL" option. It cut off HTTP traffic to acme challage.

I'm seeing this problem on a new server where I'm trying to set up HTTPS. Running version v0.7.1 with dehydrated -f /etc/ssl/letsencrypt/dehydrated.conf --register --accept-terms:
# INFO: Using main config file /etc/ssl/letsencrypt/dehydrated.conf
+ Generating account key...
+ Registering account key with ACME server...
  + ERROR: An error occurred while sending post-request to https://acme-v02.api.letsencrypt.org/acme/new-acct (Status 400)

Details:
HTTP/2 400
server: nginx
date: Fri, 13 Jan 2023 11:08:42 GMT
content-type: application/problem+json
content-length: 112
cache-control: public, max-age=0, no-cache
link: <https://acme-v02.api.letsencrypt.org/directory>;rel="index"
replay-nonce: F977yPEwYkTmLVp3EfhyyxGkz6AS8gxj0ZGO8La6ije9b3U

{
  "type": "urn:ietf:params:acme:error:badNonce",
  "detail": "JWS has no anti-replay nonce",
  "status": 400
}

Error registering account key. See message above for more information.

Any idea how to debug this?

Seeing the same as @rixx above


Sheriff running slow for a large codebase even via excludeRoot

Hi @rainerhahnekamp I try to add Sheriff via excludeRoot in our large existing codebase (~1.8k TS files, 14k import lines) without libs yet and I managed to run it without issue, but is extremely slow.
We try to add new libs and extract some of them from root as we go, which seemed a good strategy to start using Sheriff.
Our existing codebase contains 11 existing index.ts barrel under apps/my-app/src/ folder.
_I would like to share what I did so maybe you can spot why is so slow in our case. 🤞 _
I use the following simplesheriff.config.ts generated by sheriff init:
import { SheriffConfig } from '@softarc/sheriff-core';

/**
 * Minimal configuration for Sheriff
 * Assigns the 'noTag' tag to all modules and
 * allows all modules to depend on each other.
 */
export const config: SheriffConfig = {
  excludeRoot: true,
  entryFile: 'apps/my-app/src/main.ts',
  tagging: {}, // apply tags to your modules
  depRules: {
    // root is a virtual module, which contains all files not being part
    // of any module, e.g. application shell, main.ts, etc.
    root: 'noTag',
    noTag: 'noTag',

    // add your dependency rules here
  },
};

I toggle each relevant eslint rule which lead to different execution times:
🚀  11 sec (turn both sheriff rules)
    {
      "files": ["*.ts"],
      "extends": ["plugin:@softarc/sheriff/default"],
      "rules": {
        "@softarc/sheriff/deep-import": "off",
        "@softarc/sheriff/dependency-rule": "off"
      }
    },

🐌  4 min (turn off dependency rule checks)
    {
      "files": ["*.ts"],
      "extends": ["plugin:@softarc/sheriff/default"],
      "rules": {
        "@softarc/sheriff/deep-import": "error",
        "@softarc/sheriff/dependency-rule": "off"
      }
    },

🐌  8 min (default both rules applied)
    {
      "files": ["*.ts"],
      "extends": ["plugin:@softarc/sheriff/default"],
      "rules": {
        "@softarc/sheriff/deep-import": "error",
        "@softarc/sheriff/dependency-rule": "error"
      }
    },

Further useful info:

sheriff verify is pretty fast and return "No issues found. Well done!"
sheriff export > export.json generates ~20k lines JSON (contains 1.5k appearances of "module": ".")

I really want to use sheriff if possible, but  only can use if it is fast enough, want to see where is the speed bottleneck.
Thank you so much for your help or further guidance what could be the issue. 🙇

Hi @attilacsanyi,
Short answer. You need a cache.
Long Answer: ESLint starts a new Sheriff run for each file, which means it goes through the file system and generates the dependency graph. sheriff verify is just one run.
sheriff export is expected to be that large. It forms the basis for future add-ons like visualizations.
If ESLint were as fast as sheriff verify, would that be acceptable? How fast is verify actually?

Thanks @rainerhahnekamp for the quick answer.

How can I turn on the cache, or this is something not possible yet?
sheriff verify is ~3 sec, which is acceptable

Let me know what should I do now to make it faster. Thank you as always

3 seconds for sheriff verify compared to 11 seconds for eslint without Sheriff? Yeah, that's a good number.
The cache is something that has to be implemented yet. Performance issues with ESLint is one of the main reasons why the CLI actually exists. There is another company which uses Sheriff for a large code base and they also run into similar issues.
I will create a separate issue for the caching feature.

Thanks for addig cache to the milestone @rainerhahnekamp .
Good to hear that others also experienced this.
Did they accept slowness this until caching will be implemented or they switched to @nx/boundaries until then as an alternative (but we need to configure tags/rules manually as in Sheriff config - but, without deep-import check feature)?
Thanks.

As far as I know, they are currently evaluating the Sheriff CLI. They moved from Nx to the Angular CLI.

Sheriff CLI.

We cannot do a lot with Sheriff CLI this moment without custom tool implementation isn't it?
I found just few commands available in Sheriff CLI yet, or how can this be used with Angular CLI to check boundaries? I might missed some docs?

Appreciate.

Sheriff is not bound to Nx. You can use Sheriff with the Angular CLI or with any other framework that uses TypeScript.
To use Sheriff's ESLint integration, your Angular CLI project needs to support ESLint, which you get from https://github.com/angular-eslint/angular-eslint
You don't need ESLint for the Sheriff CLI; it is faster, but I guess its main usage is in the CI run.

Hi @rainerhahnekamp just curious whether you can give an estimate when the caching milestone will be released and ready for production?
It would help us to decide our strategy how and which module boundaries tool should we integrate soon.
Thanks in advance as always :)

@attilacsanyi is there an option your application could act as "beta tester"? we are working on some randomized generated projects but if we have a real-world, big project to get quick feedback for those kind of features, it would improve the pace quite a bit.

I am happy to try how the caching improves the speed of the lint process. Just let me know the steps once you are ready with it. You can also reach me via my GitHub email.
Thanks for your contribution to make Sheriff faster. 🙏


PATCH request seems to just return body of the request

Using const rp = require('request-promise-native'); with the following options
const options = {
      method: 'PATCH',
      uri: getUrl('contacts'),
      json: true,
      headers: {
        Authorization: this.accessToken,
      },
      body: [{
        entity: 'email',
        identifier: this.updateEmailId,
        change: {
          value<EMAIL_ADDRESS>          attribute: 'value',
        },
      }],
    };
    const response = await rp(options);

Simply returns the body of the request
Is this to be expected?