Prisma VSCode Plugin 2.27.0 memory leak/too many processes

Bug description
There seems to be some sort of issue with v2.27.0 of vscode plugin where if it is enabled in VScode then when running yarn dev terminal will eventually start throwing errors like below.
I believe it has something to do with prisma plugin watching files for changes.
Reverting to v2.26.0 resolves the issue.
Error 1
zsh: fork failed: resource temporarily unavailable

Error 2
yarn dev
yarn run v1.22.10
$ next dev
ready - started server on <IP_ADDRESS>:3000, url: http://localhost:3000
info  - Loaded env from /Users/user/Development/rc/ffs-dev/.env
info  - Using webpack 5. Reason: Enabled by default https://nextjs.org/docs/messages/webpack5
events.js:292
      throw er; // Unhandled 'error' event
      ^

Error: spawn /usr/local/bin/node EAGAIN
    at Process.ChildProcess._handle.onexit (internal/child_process.js:269:19)
    at onErrorNT (internal/child_process.js:465:16)
    at processTicksAndRejections (internal/process/task_queues.js:80:21)
Emitted 'error' event on ChildProcess instance at:
    at Process.ChildProcess._handle.onexit (internal/child_process.js:275:12)
    at onErrorNT (internal/child_process.js:465:16)
    at processTicksAndRejections (internal/process/task_queues.js:80:21) {
  errno: -35,
  code: 'EAGAIN',
  syscall: 'spawn /usr/local/bin/node',
  path: '/usr/local/bin/node',
  spawnargs: [
    '/Users/user/Development/rc/ffs-dev/node_modules/jest-worker/build/workers/processChild.js'
  ]
}
error Command failed with exit code 1.

How to reproduce
Steps to reproduce the behavior:

Open VScode
make sure prisma 2.27.0 vscode plugin is installed
in terminal iterm2 or any other, run project with yarn dev
Observer errors yarn dev will crash
try to run yarn dev again notice the following error

zsh: fork failed: resource temporarily unavailable

try running yarn dev again
Observer the error

eady - started server on <IP_ADDRESS>:3000, url: http://localhost:3000
info  - Loaded env from /Users/user/Development/rc/ffs-dev/.env
info  - Using webpack 5. Reason: Enabled by default https://nextjs.org/docs/messages/webpack5
events.js:292
      throw er; // Unhandled 'error' event
      ^

Error: spawn /usr/local/bin/node EAGAIN
    at Process.ChildProcess._handle.onexit (internal/child_process.js:269:19)
    at onErrorNT (internal/child_process.js:465:16)
    at processTicksAndRejections (internal/process/task_queues.js:80:21)
Emitted 'error' event on ChildProcess instance at:
    at Process.ChildProcess._handle.onexit (internal/child_process.js:275:12)
    at onErrorNT (internal/child_process.js:465:16)
    at processTicksAndRejections (internal/process/task_queues.js:80:21) {
  errno: -35,
  code: 'EAGAIN',
  syscall: 'spawn /usr/local/bin/node',
  path: '/usr/local/bin/node',
  spawnargs: [
    '/Users/user/Development/rc/ffs-dev/node_modules/jest-worker/build/workers/processChild.js'
  ]
}
error Command failed with exit code 1.

Kill vscode or install v2.26.0
Notice that you can now run yarn dev and no issues are happening anymore

Expected behavior

Prisma information

Environment & setup

OS: OSX Big Sur
Editor:

Version: 1.58.2
Commit: c3f126316369cd610563c75b1b1725e0679adfb3
Date: 2021-07-14T22:09:06.581Z
Electron: 12.0.13
Chrome: 89.0.4389.128
Node.js: 14.16.0
V8: <IP_ADDRESS>-electron.0
OS: Darwin x64 20.5.0

Extension version:v2.27.0
Vscode has no other extensions installed

Since version 3.8.0 of the Prisma VS Code extension released yesterday there is now a way to disable the File Watcher.
It's implemented as a (default = true) boolean in the settings

And can be enabled/disabled from the command palette UI like this

Could you check

That your problem still exists with version 3.8.0 or newer
Run the Prisma: Disable the File Watcher functionality for Prisma Client command
Did that solve the problem?

If no, try to reload VS Code.
If yes please let us know, it will be helpful for us.

Thank you will try!

Hi! @m3ki
I created a PR to fix the file watcher issue, I'm happy to report that on my computer (macOS m1) it's now fixed. (CPU goes from ~100% previously to 0%)
Could you confirm it's also fixed for you as well?
Follow these instructions
First, confirm that the CPU usage is high using the Prisma extension from the VS Code marketplace

Open your project using Prisma
If you disabled the Prisma File Watcher functionality, enable it again from the command palette:

Open the schema.prisma file from your project
Use "Open Process Explorer" from VS Code' menu or open the OS Activity monitor

Note / screenshot the CPU usage for the extension host above the Prisma extension process for the explorer or for the Activity Monitor, the Code Helper (Renderer) value and share it at the end

Second, confirm that with the new extension the CPU usage is low using a special build from my PR
Note: only the file watcher logic was changed.

Uninstall any Prisma extension installed (uninstall is preferred as only disabling might interfere in some ways)
Download https://github.com/prisma/language-tools/blob/artifacts/pull-request-artifacts/pr1243-prisma.vsix?raw=true
Click "Install from VSIX" from this button (screenshot) or command palette and select the pr1243-prisma.vsix file

Restart the VS Code application
Open the schema.prisma file from your project
Use "Open Process Explorer" from VS Code' menu or open the OS Activity monitor

Note / screenshot the CPU usage for the extension host above the Prisma extension process for the explorer or for the Activity Monitor, the Code Helper (Renderer) value and share it at the end

Third, if you have a TypeScript project, confirm that the file watcher works and that the types are refreshed

Open a TypeScript file from your project where you have Prisma Client queries like await prisma.user.findMany()
Open the schema.prisma file from your project
Both should have no errors
Edit the schema.prisma file and delete all the models (only keep the datasource & generator blocks)
Run npx prisma generate
In your TypeScript file, you should now instantly see a Type Error that should look like the following

Undo the changes in your schema.prisma
Run npx prisma generate
The Type Error(s) in the TypeScript file should be gone now

Please share something like the following:

Screenshot before showing ~100% CPU usage

Screenshot after showing ~0% CPU usage

Current extension: screenshot showing ~91% CPU (Note: CPU is only reported on the aggregated top line for some reason)

Using pr1243-prisma.vsix, screenshot after showing ~0% CPU usage 🎊

The typings were updated successfully after npx prisma generate, a Type Error was visible ✅

Thank you in advance 💚
Note: I'm waiting for some feedback before we switch to this new low CPU file watcher in a stable release on VS Code marketplace.

Will try this weekend

Thanks for the feedback 💚
The fix is now in the latest 4.4.0 version on the marketplace https://marketplace.visualstudio.com/items?itemName=Prisma.prisma 🎊
For those who disabled the File Watcher functionality, you can enable it again.


Configure dependabot

Closes #619

Also, some submodules can be automatically merged, but I have some troubles with synchronizing this action with CI's successfulness.

Download:
Environment: QT=5.12, ARCH=32, PYTHON_PATH=C:\Python37
Environment: QT=5.12, ARCH=64, PYTHON_PATH=C:\Python37-x64


chore(makefile): update release command

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

Project coverage is 99.48%.  Consider uploading reports for the commit 9d5ba92 to get more accurate results

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #198   +/-   ##
=======================================
  Coverage   99.48%   99.48%
=======================================
  Files           8        8
  Lines         387      387
=======================================
  Hits          385      385
  Misses          2        2

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


Modoaipmh 176

PURPOSE
Fix issue with posting configurations to mod-ocnfiguration while running TenantAPI & use ConfigurationCLient instead of HttpClientInterface

LFTM


Bump react-scripts from 3.4.3 to 4.0.1 Fails

Describe the bug

(Write your answer here.)
Version 4.0.1 is broken:

Open up dependabot pull requests
Go to Bump react-scripts from 3.4.3 to 4.0.1
Note: I do not see breaking changes listed
Compatibility is @ 57%
There are build errors here on your repo

Did you try recovering your dependencies?
n/a

(Write your answer here.)
Which terms did you search for in User Guide?
The change log in the dependabot PR

(Write your answer here if relevant.)
Environment

run yarn build
(paste the output of the command here.)
confidential...
Steps to reproduce
Upgrade to 4.0.1, run your existing react scripts (i.e. yarn start, yarn build, etc.)

(Write your steps here:)

Install new dependancy 4.0.1
Run existing scripts
Errors, but I can't seem to find guidance on breaking changes

Expected behavior

(Write what you thought would happen.)

Breaking changes are listed
Per breaking changes list, I can update my app
Then re-install 4.0.1 and the app works

Actual behavior

(Write what happened. Please add screenshots!)
Reproducible demo

(Paste the link to an example project and exact instructions to reproduce the issue.)

@single-stop-justin you may need to try this with 4.0.0 before 4.0.1.
The breaking changes and detailed change log are are listed here: https://github.com/facebook/create-react-app/releases/tag/v4.0.0

@single-stop-justin you may need to try this with 4.0.0 before 4.0.1.
The breaking changes and detailed change log are are listed here: https://github.com/facebook/create-react-app/releases/tag/v4.0.0

Thank you very much @shoedog !

Thank you very much @shoedog !


Modify README of any changes when trying out Getting Started Guide

Modify README to remove HoodieOutputFormat and any other changes you needed when you tried out the getting started guide.
cc @yssharma @vinothchandar

yes. Let me do that.

Submitted pull request. https://github.com/uber/hoodie/pull/112


Doesn't work in mac because of mapfile.

mapfile is not present in mac hence the following error:
./shlide: line 27: mapfile: command not found

shlide requires bash 4+, your Mac likely doesn't ship with that.
Feb 5, 2020 12:02:40 PM Jebin<EMAIL_ADDRESS>
mapfile is not present in mac hence the following error:
./shlide: line 27: mapfile: command not found
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub [https://github.com/icyphox/shlide/issues/2?email_source=notifications&email_token=AEG2RO2KQSVWNCLMYOC6XHLRBJMP7A5CNFSM4KQFURZKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4ILDQHKQ] , or unsubscribe [https://github.com/notifications/unsubscribe-auth/AEG2ROYRJPD4JBUKMDLO3CDRBJMP7ANCNFSM4KQFURZA] . [https://github.com/notifications/beacon/AEG2RO4AYXCECMMNTXUHC3LRBJMP7A5CNFSM4KQFURZKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4ILDQHKQ.gif]

Closing this because there's nothing that can be done from my end.


chore: pedersen hash in Noir

Description
Problem*
Related to  #4931
Summary*
Noir implementation for Pedersen Hash.
Additional Context
I added a derive_generators() built-in function, which only works for bn254, and then use pedersen commitments and scalar mul.
Documentation*
Check one:

[X] No documentation needed.
[ ] Documentation included in this PR.
[ ] [For Experimental Features] Documentation to be submitted in a separate PR.

PR Checklist*

[X] I have tested the changes locally.
[X] I have formatted the changes with Prettier and/or cargo fmt on default settings.

Checking with ilyas that this isn't going to break the AVM before we merge.

From @IlyasRidhuan:

right! so it will break everything because loads of contracts have storage mappings that use pedersen hashing.
Can you hold off on syncing until friday (best day to try a sync of course) and ill get the blackboxes added in the simulator/transpiler/prover on our side

We should probably just hold off from merging this on our side while AVM builds out support for "pedersen as MSM"

I am not sure why it would break anything, with this PR se simply do not use Pedersen hash opcode anymore, but we do not add/modify opcodes?

The issue is that the AVM transpiler currently has handling for pedersen hash opcodes but not for MSM opcodes. If we replace all the hashes with commitment + MSM then the AVM won't know what to do with them. There's also a bunch of usage of pedersen in aztec contracts so this will break.

Paging in @dbanks12  or @fcarreiro, who are more across the nuances within the contracts


[DO NOT REVIEW] Elisa/4030 touchpoints modal

Related Issue or Background Info
Adds code introduced in #345 back but with support for Firefox browsers as well
Changes Proposed
This adds onto #345 so please follow instructions on how to test there. In addition, please make sure this works on Firefox, Chrome, and Safari.
Additional Information
I've tested this on Chrome, Safari, and Firefox locally and on dev as well as Microsoft Edge by using CITGO. Feel free to check it out on dev.simplereport.gov. FYI: The deployed version had a console.log in it. This PR does not. 😅
Screenshots / Demos
Checklist for Author and Reviewer
Design

[ ] Any UI/UX changes have a designer as a reviewer, and changes have been approved
[ ] Any large-scale changes have been deployed to test, dev, or pentest and smoke-tested by both the engineering and design teams

Content

[ ] Any content changes (including new error messages) have been approved by content team

Support

[ ] Any changes that might generate new support requests have been flagged to the support team

Testing

[ ] Includes a summary of what a code reviewer should verify

@emyl3 I'm having some trouble testing on Firefox and Safari, Chrome/Brave work as expected. Should I be testing with different Shift+Tab combination for Firefox and Safari? It looks like this when I tab through:
Firefox
https://user-images.githubusercontent.com/89797785/186913395-8391dd3b-08a8-4028-ab0b-c8b7b93d42d6.mov
Safari
https://user-images.githubusercontent.com/89797785/186913575-87be3396-4a9d-4cba-879e-eb273d7b7291.mov

@georgehager For Safari I had to go to Safari -> Preferences -> Advanced and then check "Press Tab to highlight each item on a webpage"

I will look into Firefox again 😮💨 Thank you!!!

@georgehager For Safari I had to go to Safari -> Preferences -> Advanced and then check "Press Tab to highlight each item on a webpage"

@emyl3 ooh thank you! I tried this little setting, and safari looks great now!

@georgehager omg.... so after much googling I stumbled upon things like
https://www.scottohara.me/blog/2014/10/03/link-tabbing-firefox-osx.html
https://stackoverflow.com/questions/11704828/how-to-allow-keyboard-focus-of-links-in-firefox/11713537#11713537
So what I learned is that you also might have to do some setting changes to make it work as well... 😮💨 I followed the chosen solution here and it worked now... 😵💫 https://support.mozilla.org/en-US/questions/1278793
Let me know if it works for you now! 🙏

So what I learned is that you also might have to do some setting changes to make it work as well... 😮💨 I followed the chosen solution here and it worked now... 😵💫 https://support.mozilla.org/en-US/questions/1278793

@emyl3 omg apple! why is this not a default setting! anyway, I tweaked my macos and firefox settings and now it looks great. sorry to create extra concern.

@georgehager the trainings mention this a little - the majority of screenreader users are actually on Windows because Apple's accessibility settings are so bad 😬 (Apple also doesn't support the two major screenreaders, JAWS or NVDA)
There's a pretty nifty survey about screenreader user habits if you're curious! But yes, Chrome is definitely more widely used

So what I learned is that you also might have to do some setting changes to make it work as well... 😮💨 I followed the chosen solution here and it worked now... 😵💫 https://support.mozilla.org/en-US/questions/1278793

@emyl3 omg apple! why is this not a default setting! anyway, I tweaked my macos and firefox settings and now it looks great. sorry to create extra concern. unfortunately this kind of thing is something we can't resolve for accessible users, I wonder if the majority use chrome (which seems to have better default accessibility settings)...

hahah no need to be sorry at all! I learned a lot with this PR and you letting me know what wasn't working! Thank you!!! 🙏


Make each.next operation a function

Instead of:
for (const item of yield* each(stream)) {
  //...
  yield* each.next;
}

it becomes:
for (const item of yield* each(stream)) {
   //...
  yield* each.next();
}

Pros
Cons

consistent with most other operations which use functions to construct
each.next resembles a "builtin" construct more

forward compatible with passing a TNext value back up to a stream source (such as a predicate)

This poses another question: yielding to a bare object is really cool and pretty to look at but a little confusing to understand.  For example yielding to a stream to create a subscription:
function*() {
  const subscription = yield* stream;
}

I wonder if it would be easier for end-users to grok something more like this:
function*() {
  const subscription = yield* stream();
  // or
  const subscription = yield* stream.subscription();
}

Just thinking through the implications of this API change as well as being consistent across-the-board.

This is a really interesting point. So basically, you're saying that a stream should be:
type Stream<T, TClose> = () => Operation<Subscription<T, TClose>>;

Or rather stream should stay the same, and that the convention should be to return functions that return them? For example that the type of something likeChannel should be:
interface Channel<T, TClose> {
  //...
  stream(): Stream<T,TClose>;
}

because at the end of the day, a Stream is really just a very specific kind of resource.
I'd almost say that the right call is to have Channel be something like:
interface Channel<T, TClose> {
  send(value: T): Operation<void>;
  close(value: TClose): Operation<void>;
  subscribe(): Stream<T, TClose>;
}

Which is confusing, but makes sense when you think of what a stream really is which is just an operation that yields a subscription. If we expand the type, it makes more sense.
interface Channel<T, TClose> {
  send(value: T): Operation<void>;
  close(value: TClose): Operation<void>;
  subscribe(): Operation<Subscription<T, TClose>>;
}

Maybe that's the answer?

Another option is to make the Stream interface:
interface Stream<T, TClose> {
  subscribe(): Operation<Subscription<T, TClose>>;
}

It's a very small change, but it might reduce confusion by quite a bit. Everything would continue to work the same, but instead of saying yield* stream, you would just say yield* stream.subscribe()
yield* each(stream) would continue continue to work, but any time you're manually iterating a stream it would be a bit less confusing.


Compact Update

Essential Corrections were made.
PS: Sorry for the delay because of my unfamiliarity with github.

No worries, thank you :).


Using fragments to get nicer types on various queries

Not sure I'm missing something. But if my schema has various queries that gives back say a User object. Like, GetUserQuery and ListUsersQuery. When using the API.swift these comes out as different types. I.e GetUserQuery.Data.GetUser and ListUsersQuery.Data.ListUser, both which are a User object.
Now, I know you can get around this by using fragments in the queries, but since amplify builds all this for you, is there way to make this nicer, or to get amplify to set up fragments?

@helloniklas We fixed this issue as a part of https://github.com/aws-amplify/amplify-cli/pull/796 and is a part of our latest CLI version.


Remove packed and payloadJSON for memory savings

This patch is a first stab at reducing the sig chain memory usage.
It removes ChainLink.packed and ChainLink.payloadJSON.  With both of these gone, some GC happens.  With just one gone (I tried both options), memory usage stays the same.
I tried some other quick changes, but they either didn't work or were super destructive to existing code.
In a memory profile, the in-use memory is cut by about 50%.
In Activity Monitor, with this patch looking at profile in GUI of two users with large sigchains loaded from server shows memory usage of 435MB.  Master shows 690MB for same operation.

I wonder if we should rename that like UnmarshalPayloadJSON just to make it clear to future people that it is doing a computation.

Good idea.

It the CPU use is going to go up a bunch as a result of this, I wonder if we can pursue a simple compromise:

have an LRU that maps hash(jsonStr) -> json
before unmarsahling jsonStr, check the LRU for hash(jsonStr)
otherwise, unmarshal and then prime the LRU

This would almost implement the "streaming" behavior we'd have ideally.

To see if the above idea makes sense, just put a printf in the code in the jsonw accessor that prints out the hash of the payload json.  Then let's eyeball the access pattern to see if the LRU would help?

Sure, I can also run a cpu profile against this and master.

Should be easy to grep out of the logs into a sort | uniq -c | sort -n pattern to get a feel for how many times we hit the same hash.

I don't think that pipeline is telling you the right thing.  You'd want to see a log like:
A
A
A
B
B
B
C
C
C

to think the LRU is worth it.  Something like:
A
B
C
A
B
C

probably won't be a good access pattern, since for long chains, it's thrash the LRU and nothing will be achieved

Sent log via chat

So I can do the LRU quickly, that’s no problem.
But real performance solution is to just have unpack actually unpack everything. Then unmarshal only happens once.
Wanted this PR to be here in case we need mobile release to relieve increased memory pressure in old phones.
So next step can either be LRU or full unpack.
After that will be dropping unneeded sigs which will really fix mem issues.

Another idea is to reach into the sig to grab the payloadJSONstr. That's very doable


Not showing main desktop. help please.

Raspberry Pi 3b
HiLetgo 2.8" TFT
Managed to get the display to show something, but the mouse wont move and there is no desktop icons and taskbar. When I plug in an HDMI screen at the same time, I can view the boot info and move the mouse on that screen. The TFT remains static.
Used the below to build. Pins connectors double checked and in the right place.
EDITED to add 'desktop icons and taskbar and am aware that boot up will only show once its loaded when the OS starts, so I have been told.'
cmake -DILI9341=ON -DGPIO_TFT_DATA_CONTROL=24 -DGPIO_TFT_RESET_PIN=25 -DSPI_BUS_CLOCK_DIVISOR=8 -DDISPLAY_ROTATE_180_DEGREES=ON -DSTATISTICS=0 ..
Then edited config.txt with
hdmi_group=2
hdmi_mode=87
hdmi_cvt=320 240 60 1 0 0 0
hdmi_force_hotplug=1
and then added the following to  /etc/rc.local sudo /home/pi/fbcp-ili9341/build/fbcp-ili9341 &.
That's all I have done.
Any pointers would be nice.

so, just from the desktop background, I can see that the taskbar is "chopped off" it's like the image on the display is "zoomed in" have you added the extra lines to /boot/config.text from the instructions?
I highly recommend a full read-through of the instructions, I didn't have any luck until I read the instructions from top to bottom without stopping, instead of just trying to find bits I thought I needed to find.
I'm aware of an issue with freezing displays on the latest version of Raspberry Pi OS, Raspberry Pi OS desktop works fine for me on the (legacy) version of Raspberry Pi OS from the Raspberry Pi OS flasher tool.


Update OWNERS

Changes

/kind

Fixes #

Release Note

Docs

/hold
The OWNERS file should only reference groups in OWNERS_ALIASES, these are managed in https://github.com/knative/community/blob/9a329a095dd76ab945a409c2b59190e8a5806414/peribolos/knative-sandbox.yaml
I'm going to send an update to OWNERS to get this straight, to add new people to peribolos we need to update the file above (and run some script for dependent files).
@lance could you verify this list of people that should have write-access to this repo:
- lance
- lkingland
- matejvasek
- zroubalik
- omerbensaadon

I can then create the corresponding PR on the community repo.

Added salaboy to peribolos config in https://github.com/knative/community/pull/906 which then should be picked up when #783 is merged.


Cannot launch make server

Have you searched opened / closed issues on this repo for a similar problem?
Yes
Have you searched the fastai forums for a similar problem?
Yes
Hi -
I can't get make server to work. It worked the first time I set the repo up but not since. The localhost shows nothing and I get this docker error: covid_dz_jekyll_1 exited with code 1
I tried starting by deleting the docker images but it still did not work. Using make convert does convert the notebook to a post however and I can see the dashboard once I commit to master.
Not sure if this is the underlying issue: jekyll_1     | /usr/local/bundle/ruby/2.6.0/gems/jekyll-4.0.0/lib/jekyll/static_file.rb:70:in `stat': No such file or directory @ rb_file_s_stat - /data/data/LICENSE (Errno::ENOENT)
My repo is: https://github.com/btahir/covid_dz
Thanks!

Try
make stop
Followed by
make build

Sorry try make remove followed by make build

Still the same error.

run the command docker ps you will see a list of container ids, for each container id do
docker stop <container id>
then try make build and make server again

Its your data folder.  You need to hide this folder from jekyll, either by renaming it to _mydata  or by hiding that folder in _config.yml via the exclude parameter.
Note do NOT rename your folder to _data as that is somehting special in Jekyll
I was able to reproduce your error and resolved it with these steps.  Feel free to comment if you have any issues

Ah that did it. Thanks!


Implement Gradient Descent in Java

Implement Gradient Descent from scratch in

Java

Create new issue according to the template if you would like to implement a different algorithm (or) in a different language.

Hi, I'm really sorry but I won't have time to work on this actually.
Good Luck!

it is fine @lucblassel


Unable to import bricklink_api

Hi,
Thanks for the api - worked great until I updated conda, I guess.
Apologies for ignorance, I suspect there is an issue with envvars but here is the trace back that I am getting now:
`>>> import bricklink_api
Traceback (most recent call last):
File "", line 1, in
File "/Users/Gara/opt/miniconda3/envs/myenv/lib/python3.10/site-packages/bricklink_api/init.py", line 3, in
from . import order
File "/Users/Gara/opt/miniconda3/envs/myenv/lib/python3.10/site-packages/bricklink_api/order.py", line 4, in
from .method import method as _method
File "/Users/Gara/opt/miniconda3/envs/myenv/lib/python3.10/site-packages/bricklink_api/method.py", line 5, in
from . import auth as _auth
File "/Users/Gara/opt/miniconda3/envs/myenv/lib/python3.10/site-packages/bricklink_api/auth.py", line 4, in
import requests_oauthlib as _requests_oauthlib
File "/Users/Gara/opt/miniconda3/envs/myenv/lib/python3.10/site-packages/requests_oauthlib/init.py", line 3, in
from .oauth1_auth import OAuth1
File "/Users/Gara/opt/miniconda3/envs/myenv/lib/python3.10/site-packages/requests_oauthlib/oauth1_auth.py", line 9, in
from requests.compat import is_py3
File "/Users/Gara/opt/miniconda3/envs/myenv/lib/python3.10/site-packages/requests/init.py", line 134, in
from . import packages
File "/Users/Gara/opt/miniconda3/envs/myenv/lib/python3.10/site-packages/requests/packages.py", line 15, in
locals()[package] = import(package)
ModuleNotFoundError: No module named 'idna'`
Trying to install idna but it appears to be installed already:
`(myenv) MacBook-Air:bricklink Gara$ pip install idna
Requirement already satisfied: idna in /Users/Gara/opt/miniconda3/envs/myenv/lib/python3.10/site-packages (3.3)`
Any help would be much appreciated.
Thanks

God, should have googled a little more - fixed it with pip install -I --user idna


cocoapods support?

is it possible to add and publish a podspec for this project? i still use cocoapods and cannot use SPM.

Will add it!

Done! Sorry it took a few tries to get it right. It's under HammerTests in CocoaPods because the name Hammer was already taken


James0409 mockoon

After finding out how to get Mockoon working again with the app (Thanks, Joy), I wrote up some details on what to focus on when the time comes for setting up the OAuth. Let me know if there's anything else on this pull request that is needed. Thank you!

👍


fix(tauri-utils): include \n in io::read_line, closes #6388

What kind of change does this PR introduce?

[x] Bugfix
[ ] Feature
[ ] Docs
[ ] New Binding issue #___
[ ] Code style update
[ ] Refactor
[ ] Build-related changes
[ ] Other, please describe:

Does this PR introduce a breaking change?

[ ] Yes, and the changes were approved in issue #___
[x] No

Checklist

[x] When resolving issues, they are referenced in the PR's title (e.g fix: remove a typo, closes #___, #___)
[x] A change file is added if any packages will require a version bump due to this PR per the instructions in the readme.
[x] I have added a convincing reason for adding this feature, if necessary

Other information

I see the value of keeping this compatible with the Rust std library, but I worry this is a breaking change for some users. Maybe we could target this for v2 instead.
The use case of the issue is also a little weird ( but I need to know if that newline character was present or not in the stdout.). If there's no newline or \r in the output, Tauri will keep waiting for it to appear and never give the bytes to the user, so he will end up not knowing this anyway.
Currently if the line does not end with \r, then you're sure it ends with \n and can append it on your end.

I see the value of keeping this compatible with the Rust std library, but I worry this is a breaking change for some users. Maybe we could target this for v2 instead.

tbh I see it as a bug fix so not a breaking change

The use case of the issue is also a little weird ( but I need to know if that newline character was present or not in the stdout.). If there's no newline or \r in the output, Tauri will keep waiting for it to appear and never give the bytes to the user, so he will end up not knowing this anyway.
Currently if the line does not end with \r, then you're sure it ends with \n and can append it on your end.

While that maybe true, it is a bad DX (showcased in the example you added) and beside the use case of the issue, unix and windows had different behaviors which needs to align and if you align any of them to the other it will break for some users so I'd rather just fix the buggy behavior and align with rust.


add EmailWindow button and window to copy email

This PR is intended to address the User Story where the admin can retrieve a list of student emails for easy copy-pasting into an email domain. This PR involves addition of an EmailWindow class and altering the MainWindow class and its FXML files. When the Show Email button is pressed, if the EmailWindow object does not exists, it instantiates a new EmailWindow object. If not, the application will close the current EmailWindow object and open a new one to retrieve an updatedlist. The copy function utilises the Clipboard class to copy the text of emails into the User's operating system's clipboard.
The purpose of this PR is to get feedback for the initial implementation and request for comment.
It is part of a greater set of changes and is not dependent on any concurrent PR.
Things to consider:
With the addition of the new stackpane, filter tabs can be placed in the same pane to display to the user what their search requests is currently filtered by.

Codecov Report

Merging #83 (58deb93) into master (e680598) will decrease coverage by 1.81%.
The diff coverage is 0.00%.

@@             Coverage Diff              @@
##             master      #83      +/-   ##
============================================
- Coverage     71.76%   69.94%   -1.82%
  Complexity      487      487
============================================
  Files            79       81       +2
  Lines          1576     1617      +41
  Branches        167      169       +2
============================================
  Hits           1131     1131
- Misses          399      440      +41
  Partials         46       46

Impacted Files
Coverage Δ

src/main/java/seedu/address/ui/ActionBar.java
0.00% <0.00%> (ø)

src/main/java/seedu/address/ui/EmailWindow.java
0.00% <0.00%> (ø)

src/main/java/seedu/address/ui/MainWindow.java
0.00% <0.00%> (ø)

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more


Broker cannot use distributed cache to bypass historical querying for cached segment results

Found a bug in 0.22 related to caching, which would break the use case where broker can use distributed cache to get segment level cached results populated by historicals and thus bypassing sending query for that segment to the historical. When druid.broker.cache.useCache is set to true at broker it looks for cached segment results before sending query to the historical.
it was introduced by this PR - https://github.com/apache/druid/pull/10714 where it uses actual min/max time of rows in segment rather than segment interval to compute cache key. The PR changed the cache key calculation at historical side here, but same is not done at broker side here. In the current state, its not possible to do it at broker side as does not have actual segment and thus cannot read it to get the max/min time.
Affected Version
0.22.0

I am talking about the case where a remote/distributed cache like redis or memcached is used. In that case historical will populate that remote cache with the cache key generated at historical end where as broker will try to fetch the results using the key generated using code at broker end and these two keys will be different.

Got it. I missed this scenario where the same cache can be used by both historicals and the broker.


feat(remix-dev): support worker package exports for Cloudflare runtime

There are some packages define custom package exports dedicated for worker, e.g. https://github.com/maraisr/diary/blob/main/package.json#L21-L24
It would be really helpful if we can support this by setting up conditions specifically for cloudlfare-workers and cloudflare-pages serverBuildTarget.
Closes #2299

I'm going to add a test here for this and we'll get it merged.

@edmundhung Can you please rebase your branch onto latest dev & fix conflicts?

@MichaelDeBoey Since the mainFields change need a bit more thought as I mentioned earlier. We can consider merging this first as this should already help unblocking people using React 18 on Cloudflare Workers and Pages. I can create another PR after this with test cases explaining the problem and concerns there.

Hi @jacob-ebey is it included with v1.3.4 ?


What experiment tracker is a good choice?

Hello! I use Haiku+Jax for research. I have written a class that tracks my experiments in a simple folder structure. It is helpful for 10-20 runs. However, I want to use more powerful tools to track 100-1000 experiments and gather results from many computational nodes together.
What is a good experiment tracker for Haiku? I think PyMLPipe or DVCLive is a good choice, but I cannot make a choice. Is there something better?

I personally use Weights and Biases. They have remote logging via their website and explicitly focus on parameter sweeps etc. AFAIK they also have an option to host the server for the logging yourself.

i use mlflow because

i find its abstractions very useful as a general numerical experiment manager (deep learning, PDE simulations, coupled ODE solve etc.).
it's self hosted and can be run locally or on the cloud w/ a dedicated DB and object store (just like wandb).
it is open source


I am facing an issue.

Is this a bug report?
(Yes)

Did you try recovering your dependencies?

(Yes

)
Which terms did you search for in User Guide?

(Write your answer here if relevant.)
Environment

(paste the output of the command here)
Steps to Reproduce

(Write your steps here:)

Expected Behavior

(Write what you thought would happen.)
Actual Behavior

(Write what happened. Please add screenshots!)
Reproducible Demo

(Paste the link to an example project and exact instructions to reproduce the issue.)

try clearing npm cache (npm cache clean), turn off any firewalls and/or switch to yarn.

Thank you. It worked but with additional "--force" command.
Thanks


Invalid Tenant detected

After following the deployment steps and installing the expert Remote Support App the the team. When I click on Current on-call team, I get the 'Invalid tenant detected' error

Found the fix:
You have to use the Tenant ID found on the Teams URL link that you are using.
At the end of the URL you will find the 36 digit Tenant ID copy that and paste it to the Tenant ID field.


Don't work upload fotos and files in Telegram with FAST_MODE = True.

Subj.
AD_TAG has disabled.
Additional info: Proxy working on IPV6 address, pycrypto&pycryptodome don't installed (yet), because proxy working on mips.

Could you check the CPU load in the uploading time. If it is 100%, that means that its work, but slow. Are pycrypto and pycryptodome are available on mips?

I understood. Thx !
Burden much too long that telegram will disconnected from proxy.
I am currently trying to compile  pycrypto or pycryptodome on Entware, and there are some problems with that.
But debian has bin-apt for mips and mipsel, so it's probably possible.

Maintainer Entware of pycrypto compiled for mips.
Testing...


[FEATURE] Improve fcl.mutate and fcl.query argument input

Issue to be solved
When passing arguments into a cadence Transaction or Script, developers need to declare the argument type along with their value:
eg:
const cadence = `
pub fun main(address: Address, amount: UFix64) {
  ...
}
`

await fcl.query({
  cadence,
  args: (arg, t) => [ arg("0xABC123", t.Address), arg("1.0", t.UFix64) ]
})

Suggest A Solution
Instead of this, we could allow developers to pass in types as such:
await fcl.query({
  cadence,
  args: {
    address: "0xABC123",
    amount: "1.00"
  }
})

In this, we'd infer the type of address and amount by looking at the signature of the cadence script/transaction to learn that address is an Address and amount is a UFix64
This would allow developers to use fcl.muatate and fcl.query without having to declare types using FCL type library.
reference: https://github.com/onflow/fcl-js/issues/1533

Is this still in review @chasefleming?

Blocked by: https://github.com/onflow/fcl-js/issues/1678

Closing this. There are too many issues without having a Cadence parser.


added base window

@damiano5154, are you further developing the GUI?

can you give me more details about how you want the GUI?

I'll share the basic structure here tomorrow.


[Improvement]: Method Size Too Large

Description
During the compilation of a Ballerina program, the following error occurs:
ERROR [main.bal:(27:1,92:3)] method is too large: 'transformPacs009ToMt202COV'
error: compilation contains errors
This error indicates that the method transformPacs009ToMt202COV has exceeded the allowable size limit, likely due to an extensive number of operations or code complexity. This limitation could pose challenges for projects requiring large transformation logic in a single method.
Affected Version:
Ballerina 2201.10.1
test (2).zip
Use this to reproduce the error.
Describe your problem(s)
No response
Describe your solution(s)
No response
Related area
-> Compilation
Related issue(s) (optional)
No response
Suggested label(s) (optional)
No response
Suggested assignee(s) (optional)
No response

The cause of the issue is similar to https://github.com/ballerina-platform/ballerina-lang/issues/43710.
According to https://github.com/ballerina-platform/ballerina-lang/issues/43710#issuecomment-2551081922, we need to refactor the code by introducing local variables and moving them to separate functions.


Postgres memleak caused by prepared statements growing forever when prepareCache is overflowing

Our Postgres db keeps running out of RAM.
We have an infinity stream of events from Kafka, each we groupBy(number = 1000) then go to the db and fetch in batch
We have a few queries which are parametrized with lists like
sql """ select ...
where id in (${SomeCodecs.id.list(ids.size)});
"""
We have a session with a pool, prepareCacheSize = 1024
We have about 25 queries
I think what happens is that we have more prepared statements ( lets say about 25 x 1000 ) than the cache size ,
and when the local cache runs out of space it just disposed it from the local cache but not from the service with deallocate.
When the same query with same number of params to list  comes up, skunk just prepares again since it's no longer in the cache, so the number prepared statement prepared statement on the postgres server just keeps growing until it either dies or we restart the app
There are a few thing I could/will do at our side but I thought it make sense to report this as a bug

@silles79 Is there someway you can confirm this on the Postgres side of things?  I suspect something similar is happening but was hoping to see evidence of it in pg_prepared_statements but the table is empty.

@silles79 Ok, so only the connection that created the prepared statements can see what's in that table for them.
I modified my application to wake up and print out the contents of that table every 10 seconds and even with these values set to 10:
commandCache:  Int = 1024,
queryCache:    Int = 1024,
parseCache:    Int = 1024,

I'm seeing the count in pg_prepared_statements to only go up over time up and above my limit.  Same behavior even with it set to 0.

With debug on, I see Skunk sending the close message:
server  ← ReadyForQuery(Active)
server  → Parse(statement_3,select state from pg_stat_activity where state IN (($1)),List(25))
server  → Describe(S, statement_3)
server  → Flush
server  ← ParseComplete
server  ← ParameterDescription(List(25))
server  ← RowDescription(Field(state, 25))
server  → Bind(portal_4,statement_3,List(Some(1)))
server  → Flush
server  ← BindComplete
server  → Execute(portal_4,2147483647)
server  → Flush
server  ← CommandComplete(Select(0))
server  → Sync
server  ← ReadyForQuery(Active)
server  → Close(P,portal_4)
server  → Flush
server  ← CloseComplete

But then after that transaction has closed, we still see the statement:
server    3127 2024-12-16T01:56:50.168376Z statement_3 select state from pg_stat_activity where state IN (($1))

Ok, here's a full reproduction:
Run a Postgres container.  We're going to first customize the config file to show debug5 so we can see as much of the message protocol as possible:
> docker run -i --rm postgres cat /usr/share/postgresql/postgresql.conf.sample > my-postgres.conf
> echo "log_min_messages = debug5" >> my-postgres.conf
> docker run -v "$PWD/my-postgres.conf":/etc/postgresql/postgresql.conf -p5432:5432 --name some-postgres -e POSTGRES_PASSWORD=mysecretpassword -d postgres -c 'config_file=/etc/postgresql/postgresql.conf'
> docker logs -f some-postgres

In a separate window, run the attached test case.  In two separate sessions, we issue a prepared statement, and then query the prepared statements table:
//> using dep org.tpolecat::skunk-core:1.0.0-M8

import cats.effect.IOApp
import cats.effect.ExitCode
import cats.effect.IO
import cats.syntax.all.*
import skunk.*
import skunk.codec.all.*
import skunk.implicits.*
import cats.effect.kernel.Resource
import java.time.OffsetDateTime
import org.typelevel.otel4s.trace.Tracer.Implicits.noop

object SkunkMain extends IOApp {

  def inQuery(names: List[String]): Query[names.type, String] =
    sql"select state from pg_stat_activity where state IN (${text.values.list(names)})".query(text)

  val psPreparedStatements: Query[Void, (Int, String, String, OffsetDateTime)] =
    sql"select pg_backend_pid(), name, statement, prepare_time from pg_prepared_statements order by prepare_time"
      .query(
        int4 *: text *: text *: timestamptz
      )

  private def databaseSessionPool: Resource[IO, Resource[IO, Session[IO]]] =
    Session
      .pooled[IO](
        host = "localhost",
        port = 5432,
        user = "postgres",
        database = "postgres",
        password = "mysecretpassword".some,
        max = 1,
        commandCache = 0,
        queryCache = 0,
        parseCache = 0,
        debug = true
      )

  def run(args: List[String]): IO[ExitCode] =
    val activeStates = List("active")
    databaseSessionPool
      .use { sessions =>
        sessions.use { session =>
          IO.println("Preparing and using query") >>
            session.execute(inQuery(activeStates))(activeStates)
        } >>
          sessions.use { session =>
            session.execute(psPreparedStatements).flatMap { results =>
              IO.println(s"Prepared Statement Count: ${results.size}") >>
                results.traverse(IO.println)
            }
          }
      }
      .as(ExitCode.Success)
}

You'll see that Skunk sends the Close("P") command for portal_2
Preparing and using query
 → Parse(statement_1,select state from pg_stat_activity where state IN (($1)),List(25))
 → Describe(S, statement_1)
 → Flush
 ← ParseComplete
 ← ParameterDescription(List(25))
 ← RowDescription(Field(state, 25))
 → Bind(portal_2,statement_1,List(Some(active)))
 → Flush
 ← BindComplete
 → Execute(portal_2,2147483647)
 → Flush
 ← RowData(List(Some(active)))
 ← CommandComplete(Select(1))
 → Sync
 ← ReadyForQuery(Idle)
 → Close(P,portal_2)
 → Flush
 ← CloseComplete
 → Query(UNLISTEN *)
 ← CommandComplete(Unlisten)
 ← ReadyForQuery(Idle)
 → Query(RESET ALL)
 ← CommandComplete(Reset)
 ← ReadyForQuery(Idle)
 → Query(select pg_backend_pid(), name, statement, prepare_time from pg_prepared_statements order by prepare_time)
 ← RowDescription(Field(pg_backend_pid, 23); Field(name, 25); Field(statement, 25); Field(prepare_time, 1184))
 ← RowData(List(Some(78), Some(statement_1), Some(select state from pg_stat_activity where state IN (($1))), Some(2024-12-16 13:32:11.270206+00)))
 ← CommandComplete(Select(1))
 ← ReadyForQuery(Idle)

On the postgres side, you can see the bind to portal_2 occurring but there is no corresponding close message:
2024-12-16 13:43:40.409 GMT [79] DEBUG:  00000: parse statement_1: select state from pg_stat_activity where state IN (($1))
2024-12-16 13:43:40.409 GMT [79] LOCATION:  exec_parse_message, postgres.c:1422
2024-12-16 13:43:40.409 GMT [79] DEBUG:  00000: StartTransaction(1) name: unnamed; blockState: DEFAULT; state: INPROGRESS, xid/subid/cid: 0/1/0
2024-12-16 13:43:40.409 GMT [79] LOCATION:  ShowTransactionStateRec, xact.c:5626
2024-12-16 13:43:40.426 GMT [79] DEBUG:  00000: bind portal_2 to statement_1
2024-12-16 13:43:40.426 GMT [79] LOCATION:  exec_bind_message, postgres.c:1657
2024-12-16 13:43:40.443 GMT [79] DEBUG:  00000: CommitTransaction(1) name: unnamed; blockState: STARTED; state: INPROGRESS, xid/subid/cid: 0/1/0
2024-12-16 13:43:40.443 GMT [79] LOCATION:  ShowTransactionStateRec, xact.c:5626
2024-12-16 13:43:41.478 GMT [79] DEBUG:  00000: StartTransaction(1) name: unnamed; blockState: DEFAULT; state: INPROGRESS, xid/subid/cid: 0/1/0
2024-12-16 13:43:41.478 GMT [79] LOCATION:  ShowTransactionStateRec, xact.c:5626
2024-12-16 13:43:41.478 GMT [79] DEBUG:  00000: CommitTransaction(1) name: unnamed; blockState: STARTED; state: INPROGRESS, xid/subid/cid: 0/1/0
2024-12-16 13:43:41.478 GMT [79] LOCATION:  ShowTransactionStateRec, xact.c:5626
2024-12-16 13:43:41.493 GMT [79] DEBUG:  00000: StartTransaction(1) name: unnamed; blockState: DEFAULT; state: INPROGRESS, xid/subid/cid: 0/1/0
2024-12-16 13:43:41.493 GMT [79] LOCATION:  ShowTransactionStateRec, xact.c:5626
2024-12-16 13:43:41.493 GMT [79] DEBUG:  00000: CommitTransaction(1) name: unnamed; blockState: STARTED; state: INPROGRESS, xid/subid/cid: 0/1/0
2024-12-16 13:43:41.493 GMT [79] LOCATION:  ShowTransactionStateRec, xact.c:5626

Not evidence of much but interesting that I see one and not the other.  I took a Wireshark capture and confirmed Skunk's protocol.  So unless someone else has some ideas, I'm going to reach out to the postgres mailing list.

skunk_pg.pcapng.zip
Here is Wireshark capture of the exchange

Ok I think I have found the issue.  We are closing portals (Close('P')) but not statements (Close('S')).  Portal = prepared statement that is ready to execute.
We only actually clean up statements when Protocol.cleanup is called:
        override def cleanup: F[Unit] =
          parseCache.value.values.flatMap(xs => xs.traverse_(protocol.Close[F].apply))

I guess part of what I don't understand is how are folks using prepared statements in their code?  In addition to tons of our queries being dynamically generated leading to lots of unique statements, you also have the problem with IN queries:
select * from foo where id IN (?);
select * from foo where id IN (?, ?);
These are two different prepared statements.  Not saying my app doesn't have any stable queries but the dynamic ones far outweigh the stable ones.
I see a couple possible fixes:

Create opt-out execute methods in Session: Session.executeNoCache that clears prepared statement at statement end
If queryCache/commandCache are set to 0, we should always be cleaning these up
Expose cleanup to Session

Ok I think I have found the issue. We are closing portals (Close('P')) but not statements (Close('S')). Portal = prepared statement that is ready to execute.
We only actually clean up statements when Protocol.cleanup is called and that is only called when the session is really closed.
        override def cleanup: F[Unit] =
          parseCache.value.values.flatMap(xs => xs.traverse_(protocol.Close[F].apply))

There is a further bug which is exasperated if you set query/commandCache to low values. If you set the cache to 10 but create 100 prepared statements in your session, even calling cleanup won't solve this problem as the code above only knows about the first 10 items in the cache. I don't know that this is really an issue as when the connection is closed, Postgres will clear this memory.

I can confirm: yes when the connection is closed the server releases the sessions prepared statements.
My issue is that we never close the connections (unless we deploy a new app), because we have a infinity stream.
It takes a few days and postgress db runs out of RAM.

intKeyArrayCodec is just a wrapper and using Codecs.array.
This creates only 1 prepared statement.

I was looking at that too.  Was curious if there were any performance drawbacks to that but looks like Postgres rewrites the IN statement to an array one anyway:
localhost:5436 db@db=# explain select * from stream where id IN (1,2,3);
                                    QUERY PLAN
----------------------------------------------------------------------------------
 Bitmap Heap Scan on stream  (cost=12.89..24.56 rows=3 width=487)
   Recheck Cond: (id = ANY ('{1,2,3}'::bigint[]))
   ->  Bitmap Index Scan on stream_pkey  (cost=0.00..12.89 rows=3 width=0)
         Index Cond: (id = ANY ('{1,2,3}'::bigint[]))
(4 rows)

Time: 12.994 ms
localhost:5436 db@db=# explain select * from stream where id = ANY(ARRAY[1,2,3]);
                                    QUERY PLAN
----------------------------------------------------------------------------------
 Bitmap Heap Scan on stream  (cost=12.89..24.56 rows=3 width=487)
   Recheck Cond: (id = ANY ('{1,2,3}'::integer[]))
   ->  Bitmap Index Scan on stream_pkey  (cost=0.00..12.89 rows=3 width=0)
         Index Cond: (id = ANY ('{1,2,3}'::integer[]))
(4 rows)


Simplifications within if and return statements.

Nothing major, just a few pieces of logic that were simplified.

Cherry picked change in 2.x branch with d89c4fe

Cherry picked change in 3.x branch with 6e89efe

Didn't take all of it, but I did one of them. Thanks for putting together the PR!

It's cool, sometimes readability trumps simplifications. Thanks!


Server parameter validation

Current Behavior
Partially solves https://github.com/NethermindEth/near-sffl/issues/239 by introducing additional bounds checks to the checkpoint messages fetching. It also adds additional tests for parameter deserializing.
New Behavior
Ensures that ranges from - to are valid, that is from < to is always satisfied.
Breaking Changes
Certain queries that would previously return an empty result set now return an error message indicating that the range provided is invalid.
Observations
There is quite a complicated issue with the storage of BlockNumber and Timestamp as defined here:
https://github.com/NethermindEth/near-sffl/blob/18544a6716cb6fe0cb91f928ba1f476cc7bcaa5f/core/types/fields.go#L14-L15

I'm assuming that this timestamp is representing a Unix timestamp

These types are used in StateRootUpdateMessage
https://github.com/NethermindEth/near-sffl/blob/18544a6716cb6fe0cb91f928ba1f476cc7bcaa5f/core/types/messages/state_root_update.go#L18-L19
This message type then gets converted to a specific model when interacting with the DB:
https://github.com/NethermindEth/near-sffl/blob/18544a6716cb6fe0cb91f928ba1f476cc7bcaa5f/aggregator/database/models/state_root_update.go#L12-L13
As noted, there is a pending range check to perform. SQLite by default does not support uint64 values (and neither other DBs like Postgres), allowing only int64 values. For both fields, if we try to store math.MaxUint64 we'll get the following SQL error:
uint64 values with high bit set are not supported

I'm not 100% sure who is to blame here (gorm, SQLite), but this means that in the future, if we have either a BlockHeight or a Timestamp greater than math.MaxInt64 then we'll get an error.
Possible actions:

Do nothing since we can guess that such high values will not show up in the near future.
Add a check to prevent inserting these values in the DB. This is not that different from 1 but at least we control what to do on errors
Change the DB schema to store these values, ex. store them as text. Curiously we get the same error on BlockHeight despite technically using text as a type which makes things a bit confusing. Either way, changing the schema would mean a breaking change which we want to avoid at least for the time being.

We'll go with option 1. for now (Do nothing since we can guess that such high values will not show up in the near future)


Make the qa tool more robust

This improves the robustness of ghtools.qa in a couple of ways:

Ensures that the fontbakery report is posted as a GH comment just after fontbakery runs, so it is encapsulated from other methods.
Wraps each function in a decorator which catches exceptions so that an exception in one test does not crash the whole tool.
Posts a notification of any exceptions/failures to GH.

This is split into fairly small self-contained commits, so may be easiest to review one commit at a time.

Cool, thank you!


Add terrain_map_publisher to spirit_utils

And implement in planning examples.

Need some doxygen comments on the ImageToGridMap class, otherwise looks good. I see you fixed the build warning about depending on grid_map directly.

Oh, whoops, good catch - ImageToGridMap was supposed to be deleted, I merged it into the terrain_map_publisher class. Fixed, and updated the yaml and config files as well.


remove tests folder from packaging

As you can see,tests is not under the pytorch_lightning namespace.
Not an issue, but it's not correct.

site-packages/pl_examples/*
site-packages/pytorch_lightning-1.0.8.dist-info/*
site-packages/pytorch_lightning/*
site-packages/tests/backends/*
site-packages/tests/base/*
site-packages/tests/callbacks/*
site-packages/tests/checkpointing/*
site-packages/tests/core/*
site-packages/tests/loggers/*
site-packages/tests/metrics/*
site-packages/tests/models/*
site-packages/tests/plugins/*
site-packages/tests/trainer/*
site-packages/tests/tuner/*
site-packages/tests/utilities/*

It was first added in <IP_ADDRESS>

@Borda What's your opinion? Something we should look into.

yes, it shall not be there...

@orctom just tested and lited package of actual master and there are no more tests SOURCES.txt
These tests shall be ancient so feel free to remove them and no worries that with installation you would get any new 🐰


feat: add workflows and checks

Summary
Adds workflows as polled in https://canary.discord.com/channels/881118111967883295/962685290294673478
also removes CODEOWNERS as it only works for maintainers
NOTE
this targets a feature branch so all issues (pyright, format) can be resolved before adding to master

Checklist

[ ] If code changes were made then they have been tested.

[ ] I have updated the documentation to reflect the changes.

[ ] This PR fixes an issue.
[ ] This PR adds something new (e.g. new method or parameters).
[ ] This PR is a breaking change (e.g. methods or parameters removed/renamed)
[x] This PR is not a code change (e.g. documentation, README, ...)

Approved, although pyright may be a tad much given it's currently failing right? Unless you aim to also fix that

Approved, although pyright may be a tad much given it's currently failing right? Unless you aim to also fix that

Pyright basic with a few custom settings, this targets a branch so all fails can be resolved before in master

kinda confused will pyright ever become required?

kinda confused will pyright ever become required?

when its in master?

pre-commit.ci run

closing and opening to see if thats how pre-commit.ci works

commit ci may only run when its a pr to master, will see when that comes


Fixes crash when the Message Queue is out of Memory.

The function statistics(), called when the MessageQueue is out of memory, will still use the MessageQueue so it crashes.
Moving the error above will improve the behavior since the developer will find the crash reasons and the instruction on how to fix it.

IIUC this doesn't fix the crash, since it still calls statistics(). I would remove the call to statistics() if the only thing it does is crashing the engine in these cases.

The function statistics(), seems used only in that case though. Do you think we should remove the function completely? Or perhaps leave it, in case someone will call it to get some statistics?

The function statistics(), seems used only in that case though. Do you think we should remove the function completely? Or perhaps leave it, in case someone will call it to get some statistics?

Then it should probably be fixed if it's intended to be used specifically to report status on EOM.
Or indeed removed if it specifically cannot work in this case, but then I wonder why it was added in the first place.

Thanks!


SAM-2949 : Student View: Return to Assessment List link is not aligne…

…d & highlight colors

Solved alignment issues. Change the background color for "Return to
assessment list" tab is not viable, because it's difficult to see it.
This PR reverts in some way "SAM-2721 : use bootstrap classes and grid
for Samigo HTML" (https://github.com/sakaiproject/sakai/commit/87d4bc58e900101191011b1249ed14ed7b17a3ae) from
@ottenhoff committed on 8 Mar 2016. So which component is preferable :
h:dataTable, t:dataList or t:dataTable?

So which component is preferable h:dataTable, t:dataList or t:dataTable?

The preference is to use a table only when the data is tabular. Do not use a dataTable for layout reasons.

Ok, I can try use the dataList and modify the CSS to avoid the alignment problem. But, in order to maintain coherency, all other question-types should be revised and replace the dataTable component (e.g : deliverMultipleChoiceMultipleCorrect.jsp)


PostWorkshopAction: link to survey results

This PR adds a survey result link (reports_link) to PostWorkshopAction context.

@fmichonneau great catch! I would scratch my head in future if it stayed that way. 😄

thanks!


update to cql-execution 1.3.8

Pull requests into cqm-execution-service require the following. Submitter and reviewer should :white_check_mark: when done. For items that are not-applicable, note it's not-applicable ("N/A") and :white_check_mark:.
Submitter:

[ ] This pull request describes why these changes were made.
[ ] Internal ticket for this PR:
[ ] Internal ticket links to this PR
[ ] Code diff has been done and been reviewed
[ ] Tests are included and test edge cases
[ ] Tests have been run locally and pass

Reviewer 1:
Name:

[ ] Code is maintainable and reusable, reuses existing code and infrastructure where appropriate, and accomplishes the task’s purpose
[ ] The tests appropriately test the new code, including edge cases
[ ] You have tried to break the code

Reviewer 2:
Name:

[ ] Code is maintainable and reusable, reuses existing code and infrastructure where appropriate, and accomplishes the task’s purpose
[ ] The tests appropriately test the new code, including edge cases
[ ] You have tried to break the code

Codecov Report

Merging #116 into cypress_v5 will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           cypress_v5   #116   +/-   ##
=========================================
  Coverage         100%   100%
=========================================
  Files               1      1
  Lines              40     40
=========================================
  Hits               40     40

Continue to review full report at Codecov.

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


Caffe2 cannot be compiled with right version of cudnn

The question is, in my system there is a cudnn 5.1 library in /usr/local/cuda/lib64 and I want to use cudnn 6.0 in ~/local/lib64. I specified the cudnn include path and library path for cmake and the cmake output just looks fine. However, caffe2 is still compiled with cudnn 5.1 and keep giving those annoying warnings asking me to move to cudnn 6+. The build process successed but at the runtime it gives error message below indicating not using the same version of cudnn at compilation and runtime:
command:  python tests/test_spatial_narrow_as_op.py
net_drawer will not run correctly. Please install the correct dependencies.
E0302 10:04:02.605679 11097 init_intrinsics_check.cc:59] CPU feature avx is present on your machine, but the Caffe2 binary is not compiled with it. It means you may not get the full speed of your CPU.
E0302 10:04:02.605773 11097 init_intrinsics_check.cc:59] CPU feature avx2 is present on your machine, but the Caffe2 binary is not compiled with it. It means you may not get the full speed of your CPU.
E0302 10:04:02.605792 11097 init_intrinsics_check.cc:59] CPU feature fma is present on your machine, but the Caffe2 binary is not compiled with it. It means you may not get the full speed of your CPU.
Found Detectron ops lib: /home/ldk/usr/local/lib/libcaffe2_detectron_ops_gpu.so
E..
 How to fix this?

I believe your diagnosis is correct. Cmake can only include entire include directories at the moment, so i think you'd have to harcode including /usr/local/include before /usr/local/cuda/include, which could introduce other problems.
Do you need both cudnn's at the same time? If not, I recommend moving the cudnn in /usr/local/cuda to /usr/local/cudnn/5.1 or something similar and moving cudnn 6.1 to /usr/local/cudnn/6.1 and then installing a symlink in /usr/local/cuda to point to whichever cudnn you want to use at the moment. Then you won't have to pass in all these manual cudnn flags.

The problem is that I don't have sudo privileges so I have to put cudnn 6.1 under my home directory.

Can you copy the cuda installatino to your home directory and then pass -DCUDA_TOOLKIT_ROOT_DIR=?

But could I still get access to gpus if I install cuda under home directory.
https://stackoverflow.com/questions/39379792/install-cuda-without-root
It said cuda had to be installed with root to access gpus.

I have the same question with you,could you please tell me how to solve it??

@ty0803 this particular issue is only caused by having two versions of CuDNN and not being able to remove one of them. If this doesn't apply to you then please open a new issue at https://github.com/pytorch/pytorch/issues
If you do have two versions of CuDNN and can't remove one of them, then you have to install all CUDA related libraries (CUDA, CuDNN, NCCL) into another directory that you have full access to, such as ~/cuda_libs, and then add this to LD_LIBRARY_PATH and pass CUDA_TOOLKIT_ROOT_DIR=~/cuda_libs to your cmake command.

Could you please tell me how to remove cudnn5,and also I can't find cudnn6 in my computer .but it say "RuntimeError: [enforce fail at common_cudnn.h:118] version_match. cuDNN compiled (5110) and runtime (6021) versions mismatch".I really don't  know how to slove the problem. I sincerely hope you can  tell me .Thank you very much.

Please see http://docs.nvidia.com/deeplearning/sdk/cudnn-install/index.html for more info on CuDNN. You have built Caffe2 using CuDNN 6, but when you run it only CuDNN 5 is found. This http://docs.nvidia.com/deeplearning/sdk/cudnn-install/index.html and other questions on that page may be useful to you as well. You will need to find all of the CuDNN related libraries and header files and delete them. I cannot tell you where they are because their location varies wildly from each machine. I suggest reading the links above and searching on stack overflow for general help on how to manually uninstall packages on linux.


Added --live-from-now and --live-from support

Added support for '--live from now' to start downloading from the current time instead of the start of the stream.
Solves #149
Edit: Added support for '--live-from' to start downloading from a point in the past.
Solves #184
Edit: I didn't realize my new commits would add to the open Pull Request so I can split this into two if you want.

How does it work? can you share an example command, for example stream between 11:00 - 11:05 of any live stream?

@keredau would it be possible to download 5 minutes of a stream starting from 1h ago?

I'm re-working my code make the command clearer and easier to use and will post a new pull request soon.

I'm re-working my code make the command clearer and easier to use and will post a new pull request soon.

Thank you very much for your effort


Bluetooth Keyboard Arrow Keys not Working - IOS

Hardware keyboard Cursors Keys and Ctrl  not working inside the MS Word (afreerdp session).
Other keys like Shift, Delete etc. working perfectly.
How I can Fix this issue, Please Suggest.
I'm grateful for any help,
Thanks.

That tells something completely different than your own #5464
#5468 also sounds very familiar.
Also very interested in how you can get afreerdp running on iOS...
Considering this as spam, please stop or be banned.


FAQ selected entry background color needs to be lighter

To avoid making the links unreadable:

no longer applicable


Provider Status Endpoint Shows Very High GPU Count if Node is Mis-Labeled

Overview

Provider version - 0.4.6

Problem Summary
When Kubernetes nodes are labeled with GPU capabilities of false instead of true this leads to the provider's status API endpoint reporting a very large count of GPU resources erroneously.
Example label that would cause issue:
kubectl label node node1 akash.network/capabilities.gpu.vendor.nvidia.model.a4000=false
Example provider status endpoint output when a node is labeled in this manner and with a false value (note gpu count of the first index in the array):
      "available": {
        "nodes": [
          {
            "cpu": 20425,
            "gpu":<PHONE_NUMBER>3709552000,
            "memory":<PHONE_NUMBER>2,
            "storage_ephemeral":<PHONE_NUMBER>86
          },
          {
            "cpu": 2825,
            "gpu": 2,
            "memory":<PHONE_NUMBER>4,
            "storage_ephemeral":<PHONE_NUMBER>54
          }

Additional Details
Akash documentation suggest only setting GPU capabilities to true such as:
kubectl label node node1 akash.network/capabilities.gpu.vendor.nvidia.model.a4000=true
However users may believe that when a GPU is removed from a node the label should be updated to false.  Which is how this issue was discovered.  If the label is instead removed from the node - which we instruct users to do to resolve issue - no issues will occur.

Closing issue as this has been deemed not be an issue with improper label use.  Rather the issue occurs when a GPU is removed from a running/active/powered on host.


Add support for TIMEOUT in FT.Aggregate and FT.Search

Motivation
Provides support for the TIMEOUT argument in FT.Aggregate and FT.Search
Basic Code Example
await client.ft.search('idx', 'query', { RETURN: [], TIMEOUT: 5000 })
await client.ft.aggregate('idx', 'query', { STEPS: [...], TIMEOUT: 5000 })

I would love to take this up

@Nanak360 go for it.. :)
Thanks for contributing!!

https://github.com/redis/node-redis/blob/master/packages/search/lib/commands/AGGREGATE.ts
https://github.com/redis/node-redis/blob/master/packages/search/lib/commands/SEARCH.ts
@Nanak360 make sure to add tests as well :)

Hey @leibale, I've created a draft PR for this issue.
I have some doubts and would really appreciate your feedback or someone else's review of the changes.
I have added TIMEOUT as an optional parameter, but I'm a bit confused about the next steps. Currently, I have only included TIMEOUT in the return arguments.
You can find the draft PR here, and any modifications or suggestions you have would be greatly appreciated.

@Nanak360 I left one comment, but overall looks good! Good job! :)


Fix build on OCaml 4.06 and clean up warnings

You really need to start running dune build without the release profile to catch all these warnings..

I realize all the warning fixes may make reviewing this a little hard. I pinpointed the actual changes that make it compile on OCaml 4.06 in GH comments.

k, fixed in 82a1162

LGTM 🎉


TravisCI to auto deploy tagged releases to rubygems.org

Coverage remained the same at 98.374% when pulling b6304582e6f5bf7f25b2c3f83fc879eabfe23ad5 on ghoneycutt:autodeploy_to_rubygems into 90a2967c70e67cc0bcd554efd321de75c8a54a0c on mcanevet:master.


TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.
If you'd like for me to do this for you, comment TagBot fix on this issue.
I'll open a PR within a few hours, please be patient!

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/59081

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/66579


expect header parses to an atom (continue)

Cowboy is awesome -- thanks for making it!  Maybe the switch to cow_lib for parsing headers on Feb 4 caused this?
My app was latent by one or two seconds every post request because the client was doing Expect: Continue but not getting the "go ahead" back

Good catch, thanks!

Merged!


Load Balancer Name Too Long

When creating an entry point through the GUI, my entry point name was 22 characters long. It resulted in this error:
"ValidationError: LoadBalancer name cannot be longer than 32 characters status code: 400, request id: ..."
It saved my entry point and shows it in the list, but does not have an ELB address. When I attempt to delete this entry point, it shows the same error and will not delete the entry point.

Sorry for the delay on this, @mcrowson, and thanks for the report. I've added a validation on the domain field in #93.


发布第一个正式版

👍

在 2018年4月18日，下午2:16，shouweikun<EMAIL_ADDRESS>写道：
You can view, comment on, or merge this pull request online at:
https://github.com/shouweikun/estuary/pull/5 https://github.com/shouweikun/estuary/pull/5
Commit Summary
优化
Merge branch 'develop' into feature/taskInfoPersistence
优化策略
开始重写mysqlConnection
正在编辑mysqlConnection
backup
修复batcher计数问题
fix bug
修改scala版本
fix bug
logback print log to logfile
增加dummyDataJson
Merge branch 'feature/newMysqlConnection' into develop
修复json bug
修复json bug
修改刷新时间
打开日志设置
增加checksend日志
修复flush不能的bug
loggers = ["akka.event.slf4j.Slf4jLogger"]
Merge branch 'feature/newMysqlConnection' into develop
backup
backup
backup
完成第一版
增加web端配置
修复一些bug
优化
删除log
增加kafkaBean中ddlTopic
假数据开始
backup
初步完成ddl 分隔
完成ddl语句处理
Merge branch 'develop' into feature/dummyData
完成getSchema函数
初步完成假数据发送，需要测试
修改刷新机制log 的错误
修改功率控制策略，提高快速拉取数据优先级
Merge branch 'develop' into feature/dummyData
增加了SettingConstant，修改akka包名
Merge branch 'feature/dummyData' of https://github.com/shouweikun/estuary into feature/dummyData
完成假数据测试
增加测试
增加判断，ddlhandler才flush
remove 默认值
增加心跳的日志
修复schma信息为空的问题
todo 增加专门配置项
Merge pull request #3 from shouweikun/feature/dummyData
修复心跳未计数问题
Merge pull request #4 from shouweikun/hotfix/heartbeatscount
修复假数据导致的计数问题
eliminate 数据丢失风险
只有非空时才记录offset
解除bug
修复bug 的同事，优化拉取数据效率
优化策略
第一个正式版
File Changes
M pom.xml https://github.com/shouweikun/estuary/pull/5/files#diff-0 (29)
M src/main/resources/application.conf https://github.com/shouweikun/estuary/pull/5/files#diff-1 (25)
A src/main/resources/logback.xml https://github.com/shouweikun/estuary/pull/5/files#diff-2 (31)
M src/main/scala/com/neighborhood/aka/laplace/estuary/bean/datasink/KafkaBean.scala https://github.com/shouweikun/estuary/pull/5/files#diff-3 (4)
M src/main/scala/com/neighborhood/aka/laplace/estuary/bean/resource/MysqlBean.scala https://github.com/shouweikun/estuary/pull/5/files#diff-4 (2)
M src/main/scala/com/neighborhood/aka/laplace/estuary/bean/task/Mysql2KafkaTaskInfoBean.scala https://github.com/shouweikun/estuary/pull/5/files#diff-5 (21)
D src/main/scala/com/neighborhood/aka/laplace/estuary/core/akka/PowerAdapter.scala https://github.com/shouweikun/estuary/pull/5/files#diff-6 (117)
D src/main/scala/com/neighborhood/aka/laplace/estuary/core/akka/SyncDaemon.scala https://github.com/shouweikun/estuary/pull/5/files#diff-7 (44)
A src/main/scala/com/neighborhood/aka/laplace/estuary/core/akkaUtil/PowerAdapter.scala https://github.com/shouweikun/estuary/pull/5/files#diff-8 (191)
A src/main/scala/com/neighborhood/aka/laplace/estuary/core/akkaUtil/SyncDaemon.scala https://github.com/shouweikun/estuary/pull/5/files#diff-9 (51)
R src/main/scala/com/neighborhood/aka/laplace/estuary/core/akkaUtil/theActorSystem.scala https://github.com/shouweikun/estuary/pull/5/files#diff-10 (2)
M src/main/scala/com/neighborhood/aka/laplace/estuary/core/lifecycle/HeartBeatListener.scala https://github.com/shouweikun/estuary/pull/5/files#diff-11 (5)
M src/main/scala/com/neighborhood/aka/laplace/estuary/core/lifecycle/worker.scala https://github.com/shouweikun/estuary/pull/5/files#diff-12 (2)
M src/main/scala/com/neighborhood/aka/laplace/estuary/core/sink/AbstractKafkaSinkFunc.scala https://github.com/shouweikun/estuary/pull/5/files#diff-13 (4)
M src/main/scala/com/neighborhood/aka/laplace/estuary/core/sink/KafkaSinkFunc.scala https://github.com/shouweikun/estuary/pull/5/files#diff-14 (37)
A src/main/scala/com/neighborhood/aka/laplace/estuary/core/source/DataSourceConnection.scala https://github.com/shouweikun/estuary/pull/5/files#diff-15 (19)
A src/main/scala/com/neighborhood/aka/laplace/estuary/core/source/MysqlConnection.scala https://github.com/shouweikun/estuary/pull/5/files#diff-16 (212)
M src/main/scala/com/neighborhood/aka/laplace/estuary/core/task/TaskManager.scala https://github.com/shouweikun/estuary/pull/5/files#diff-17 (16)
M src/main/scala/com/neighborhood/aka/laplace/estuary/mysql/CanalEntryJsonHelper.scala https://github.com/shouweikun/estuary/pull/5/files#diff-18 (15)
M src/main/scala/com/neighborhood/aka/laplace/estuary/mysql/LogPositionHandler.scala https://github.com/shouweikun/estuary/pull/5/files#diff-19 (4)
M src/main/scala/com/neighborhood/aka/laplace/estuary/mysql/Mysql2KafkaTaskInfoManager.scala https://github.com/shouweikun/estuary/pull/5/files#diff-20 (58)
A src/main/scala/com/neighborhood/aka/laplace/estuary/mysql/NewLogPositionHandler.scala https://github.com/shouweikun/estuary/pull/5/files#diff-21 (366)
A src/main/scala/com/neighborhood/aka/laplace/estuary/mysql/SettingConstant.scala https://github.com/shouweikun/estuary/pull/5/files#diff-22 (19)
A src/main/scala/com/neighborhood/aka/laplace/estuary/mysql/akkaUtil/DivideDDLRoundRobinRoutingGroup.scala https://github.com/shouweikun/estuary/pull/5/files#diff-23 (23)
A src/main/scala/com/neighborhood/aka/laplace/estuary/mysql/akkaUtil/DivideDDLRoundRobinRoutingLogic.scala https://github.com/shouweikun/estuary/pull/5/files#diff-24 (41)
M src/main/scala/com/neighborhood/aka/laplace/estuary/mysql/lifecycle/BinlogEventBatcher.scala https://github.com/shouweikun/estuary/pull/5/files#diff-25 (171)
M src/main/scala/com/neighborhood/aka/laplace/estuary/mysql/lifecycle/ConcurrentBinlogSinker.scala https://github.com/shouweikun/estuary/pull/5/files#diff-26 (55)
M src/main/scala/com/neighborhood/aka/laplace/estuary/mysql/lifecycle/MysqlBinlogController.scala https://github.com/shouweikun/estuary/pull/5/files#diff-27 (78)
M src/main/scala/com/neighborhood/aka/laplace/estuary/mysql/lifecycle/MysqlBinlogFetcher.scala https://github.com/shouweikun/estuary/pull/5/files#diff-28 (93)
M src/main/scala/com/neighborhood/aka/laplace/estuary/mysql/lifecycle/MysqlBinlogPositionRecorder.scala https://github.com/shouweikun/estuary/pull/5/files#diff-29 (6)
M src/main/scala/com/neighborhood/aka/laplace/estuary/mysql/lifecycle/package.scala https://github.com/shouweikun/estuary/pull/5/files#diff-30 (1)
M src/main/scala/com/neighborhood/aka/laplace/estuary/web/akka/ActorRefHolder.scala https://github.com/shouweikun/estuary/pull/5/files#diff-31 (2)
M src/main/scala/com/neighborhood/aka/laplace/estuary/web/bean/Mysql2kafkaTaskRequestBean.java https://github.com/shouweikun/estuary/pull/5/files#diff-32 (36)
M src/main/scala/com/neighborhood/aka/laplace/estuary/web/controller/Mysql2KafkaTaskController.scala https://github.com/shouweikun/estuary/pull/5/files#diff-33 (22)
M src/main/scala/com/neighborhood/aka/laplace/estuary/web/service/Mysql2KafkaService.scala https://github.com/shouweikun/estuary/pull/5/files#diff-34 (5)
A src/test/scala/com/neighborhood/aka/laplace/estuary/CanalEntryJsonHelperTest.scala https://github.com/shouweikun/estuary/pull/5/files#diff-35 (20)
R src/test/scala/com/neighborhood/aka/laplace/estuary/TestContext.scala https://github.com/shouweikun/estuary/pull/5/files#diff-36 (17)
M src/test/scala/com/neighborhood/aka/laplace/estuary/actor/Application.scala https://github.com/shouweikun/estuary/pull/5/files#diff-37 (5)
D src/test/scala/com/neighborhood/aka/laplace/estuary/actor/LogPositionHandlerTest.scala https://github.com/shouweikun/estuary/pull/5/files#diff-38 (58)
Patch Links:
https://github.com/shouweikun/estuary/pull/5.patch https://github.com/shouweikun/estuary/pull/5.patch
https://github.com/shouweikun/estuary/pull/5.diff https://github.com/shouweikun/estuary/pull/5.diff
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/shouweikun/estuary/pull/5, or mute the thread https://github.com/notifications/unsubscribe-auth/AHcRRsXEzPv-yptzU2NhrpYjbghaFsWLks5tptorgaJpZM4TZenc.


Creater is not a word

I think creater is a typo. creator is correct.
How about?

@sachin21 Oops...thank you for pointing out. I will fix it!!

I fixed it. Thank you!!

You're welcome 😄


Performance issue when 1+ browser window open - MacOS

Steps to reproduce:

Launch browser and open more than one browser window.
Open more than one tab in each window and load some pages.

Expected:
Performance should not be adversely affected.
Actual:
Performance seriously impacted - browser process seen at around 100% of processor. Browser becomes extremely unresponsive, clicking on menu, changing tab etc doesn't work / takes excessively long.

Closing one browser window (after a delay of several seconds) will alleviate the issue and performance returns to normal:

Above behaviour observed on MacOS.
The same scenario in Linux Mint shows no effect on performance:

I've tried opening 5+ browser windows and many tabs in one window, as you said it went to 68% of CPU from 10% for few seconds, but it dropped to 8% and still it is in 8-10%. I didn't close any of the browser windows. still they are opened

this was fixed in #766

Tested latest commit on dev branch: 865e1b3c (HEAD -> dev, origin/dev, origin/HEAD) chore(deps-dev): bump eslint-plugin-jest from 22.5.1 to 22.6.4
Test machine - QA Mac:
``Model Name:	iMac
Model Identifier:	iMac11,3
Processor Name:	Intel Core i3
Processor Speed:	3.2 GHz
Number of Processors:	1
Total Number of Cores:	2
L2 Cache (per Core):	256 KB
L3 Cache:	4 MB
Memory:	12 GB
Boot ROM Version:	<IP_ADDRESS>.0
SMC Version (system):	1.59f2
Serial Number (system):	W80520B5DB6
Hardware UUID:	33D60AE5-DFAC-58BB-B43D-576149FE4F32```

Opened five tabs in the browser, including one playing a video. No discernible effect upon performance could be seen. Indeed the highest drain on the CPU at the time was the instance of the Safari browser I had open at GitHub.

The only observation I would make is that the number of threads for the processes associated with SAFE Browser seems quite high. Is this anything that needs attention @joshuef @hunterlester ?

This issue (performance) has been resolved so moving this to done.


Including the word "from" in some content blocks causes an error

We confirmed that this happens in both 5.7 and version 8.00 sites.  When we add this content, it works fine:

PROJECT:  VALLEY PARK

Completed in 2001, the $12 million Valley Park Flood Management Project created a levee and floodwall to help protect about 130 homes that were ravaged by floods in 1997 and 1998.  The project is part of a group of projects that work together to reduce the risk of flooding on the Menomonee River.

Seven-foot-high, 800-foot-long levee.

Five-foot-high, 750-foot-long floodwall.

The acquisition of 18 homes for the construction of the levee and floodwall. (Some of the homes acquired by the District were replaced within the neighborhood, but outside of the floodplain. District officials worked closely with neighborhood residents to develop a relocation plan. Neighborhood residents were involved in selecting an architect and working closely with the contractor on home designs, and met frequently with District staff.)

An increase in Milwaukee County Parks land along the Menomonee River 1.5 acres to 3 acres.

A new 15-foot-wide access road atop the levee for maintenance and security.

But if we add the word "from" anywhere in the content, it generates the following error when we save:
$cID = $request->request->get('cID'); } if ($cID) { $page = ConcretePage::getByID($cID); } if (is_object($page) && !$page->isError()) { $this->setPageObject($page); $request->setCurrentPage($this->page); } else { throw new \Exception(t('Access Denied')); } } public function setPageObject(ConcretePage $c) { $this->page = $c; $this->permissions = new Permissions($this->page); $this->set('c', $this->page); $this->set('cp', $this->permissions); }

This method in a fresh install of 8.03 gives this error:

This sounds like an issue with some security middleware on your server. I'd bet mod_security is being overly aggressive in flagging what it thinks are SQL injection attempts.

Especially since your content has "create" and "select" in it...I'm sure that's what's happening.


Critical: fix SocketUtil::send msg_iov pointing to the wrong address

The issue was discovered using gcc11 and release build.

Fixed in https://github.com/bloomberg/ntf-core/pull/112


Allow other service label prefixes than "traefik" to facilitate major version migration

Welcome!

[X] Yes, I've searched similar issues on GitHub and didn't find any.
[X] Yes, I've searched similar issues on the Traefik community forum and didn't find any.

What did you expect to see?
Hi!
This is a bit late, I know, since Traefik v1 is EOL. However, this suggestion might also be useful to facilitate future major version migrations, and there are likely others who also are still are running v1.
Background
I have to migrate a Docker cluster from using Traefik v1 to using Traefik v2. This of course involves replacing labels on every single service, of which there are a lot.
I'd like to avoid downtime as much as possible, so it seems to me that the safest way is to migrate services gradually rather than trying to switch all the services to use v2 at the same time. Doing everything at once, downtime will be unavoidable, there is a risk of errors piling up, and rollback is complicated.
I think this might be the simplest approach for gradual service migration:

Run both Traefik v1 and v2 at the same time, but let v2 map container ports 80 and 443 to some other host ports (e.g. 3000:80, 3001:443).
For each service, one by one: Add the v2-compliant labels without removing the v1 labels, making sure that both Traefik v2 and v1 route correctly to the updated services.
Remove the host port mapping from Traefik v1, and instead let Traefik v2 listen on the host ports 80 and 443.

After this, the migration is complete. The Traefik v1 service can be taken down and the v1 labels can be removed from all services.
Issue
However, I found this approach might not work because v1 and v2 labels can conflict and cause issues (one answer in the issue links to a guide for gradual migration, but that approach seems complex and also requires running v1 and v2 in parallel, so I'm not sure how that would be any better).
Feature request
A simple way to avoid label conflict between v1 and v2 could be to add an optional configuration setting to Traefik v2, to let Traefik look for some different label prefix than traefik on the Docker services, for instance traefik2.
So, for example, instead of setting this label on a service:
- traefik.http.routers.traefik-public-https.entrypoints=https

we would be able to set:
- traefik2.http.routers.traefik-public-https.entrypoints=https

This way, a service could have Traefik v1 labels, prefixed by traefik and Traefik v2 labels prefixed by traefik2. The Traefik v1 service would only look for traefik labels and the Traefik v2 service would only look for traefik2 labels, ignoring any traefik labels. No conflicts would occur.
The default label prefix in v2 would of course still be traefik so the change would be non-breaking.
Does this seem reasonable? :)

Not sure it's a good enough reason but other reverse proxy having docker provider like Caddy and reproxy both propose a way to use labels starting with whichever string the user likes, so at least it shows there is interest and I have another (although niche) use case myself too for this

I believe setting a custom prefix might also help with security-through-obfuscation. For example a person building a Docker image could set malicious labels on the image that expose critical endpoints to the public internet. But if you can customize the prefix you could mitigate this by setting a unique prefix for your own infrastructure, which only your sysadmins know and are able to see, like acmecorp-traefik. Then, only a acmecorp-traefik.enable=true label enables Traefik, but not a traefik.enable=true label. The person building the Docker image would have to know this.


feat(migrations): add data migrations from v0 to v1

Fix #116

The migration currently does not work because of the following panic:
link-1_1  | [00] panic: fail to get current host to check if it needs data migration from v0 to v1: fail to get current host: Host not found
link-1_1  | [00]
link-1_1  | [00] goroutine 1 [running]:
link-1_1  | [00] main.main()
link-1_1  | [00]        /go/src/github.com/Scalingo/link/main.go:51 +0x2419
link-1_1  | [00] (error exit: exit status 2)


v1.15: update cilium/certgen to v0.1.11

Backport of #31863 to the v1.15 branch.

/test-backport-1.15


⚠ Bofrost.de has degraded performance

In 5daae02, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1824 ms

Resolved: Bofrost.de performance has improved in ea70d08 after 30 minutes.


Update to Pydantic2 and ophyd_async 0.5.x

Fixes #679, paves route to #644 after p4p updated.
Instructions to reviewer on how to test:

Run system tests to ensure devices still connect

Checks for reviewer

[ ] Would the PR title make sense to a scientist on a set of release notes
[ ] If a new device has been added does it follow the standards
[ ] If changing the API for a pre-existing device, ensure that any beamlines using this device have updated their Bluesky plans accordingly
[ ] Have the connection tests for the relevant beamline(s) been run via dodal connect ${BEAMLINE}

Tagged 5 reviewers on this because there's a lot of lines changed so would really appreciate a few pairs of eyes over this.


relates to #1720: simple cached schema management

What this PR does:
Simple schema management for the Docs API V2 and Quarkus based applications in general.. Provides only keyspace fetching for now.. It's fully reactive implementation, with the support for the tenant aware keyspace cache.
Uses the built-in cache support from Quarkus that enables out-of-the-box:

specifying of all cache properties via configuration
metrics about cache hit rates

Small exception mapping was done in addition, in order to move to correct package and remove test warnings.
Which issue(s) this PR fixes:
Relates to #1720
Checklist

[x] Automated Tests added/updated
[x] Documentation added/updated

@olim7t This is the schema management I was talking about today.. Have a look, it's pretty simple and already tested well, reactive, has cache metric and tracing support oob.. What do you think?


"TypeError: e.onCancellationRequested is not a function" calling hover provider in Insiders

In Insiders, all of my Hover Provider tests are failing like this:
1) dart_hover_provider
       does not return hovers for blank areas of the document:
     TypeError: e.onCancellationRequested is not a function
      at Object.t.wireCancellationToken (file://.vscode-test/insiders/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:193:579)
      at Object.provideHover (file://.vscode-test/insiders/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:3819:10)
      at file://.vscode-test/insiders/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:1614:26
      at Array.map (native)
      at a (file://.vscode-test/insiders/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:1613:983)
      at file://.vscode-test/insiders/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:1520:441
      at file://.vscode-test/insiders/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:1518:178
      at e.invokeFunction (file://.vscode-test/insiders/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:1369:836)
      at t._tryExecuteCommand (file://.vscode-test/insiders/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:2945:960)
      at file://.vscode-test/insiders/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:2945:676
      at n.Class.define.cancel.then (file://.vscode-test/insiders/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:158:366)
      at t.executeCommand (file://.vscode-test/insiders/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:2945:650)
      at e.$executeCommand (file://.vscode-test/insiders/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:3099:842)
      at e._doInvokeHandler (file://.vscode-test/insiders/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:3158:983)
      at e._invokeHandler (file://.vscode-test/insiders/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:3158:701)
      at e._receiveRequest (file://.vscode-test/insiders/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:3157:767)
      at e._receiveOneMessage (file://.vscode-test/insiders/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:3157:536)
      at file://.vscode-test/insiders/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:3156:424
      at file://.vscode-test/insiders/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:3159:575
      at e.fire (file://.vscode-test/insiders/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:172:496)
      at c (file://.vscode-test/insiders/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:306:526)
      at Socket.<anonymous> (file://.vscode-test/insiders/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:306:703)
      at readableAddChunk (_stream_readable.js:178:18)
      at Socket.Readable.push (_stream_readable.js:136:10)
      at Pipe.onread (net.js:560:20)

I stripped the test back to this:
it.only("does not return hovers for blank areas of the document", async () => {
	await vs.commands.executeCommand("vscode.executeHoverProvider", doc.uri, doc.positionAt(0));
});

And my implementation back to this:
public provideHover(document: TextDocument, position: Position, token: CancellationToken): Thenable<Hover> {
	return Promise.resolve(null);
}

And the issue still occurs; so I don't think it's my fault. As far as I can tell, this isn't happening for normal editor hovers though; it may be specific to calling that command, or being within tests.

I've noticed the same.
await vscode.commands.executeCommand<vscode.Hover[]>('vscode.executeHoverProvider', uri, position); throws with this stack:
TypeError: e.onCancellationRequested is not a function
    at Object.t.wireCancellationToken (file:///C:/Program Files/Microsoft VS Code Insiders/resources/app/out/vs/workbench/workbench.main.js:193:579)
    at Object.provideHover (file:///C:/Program Files/Microsoft VS Code Insiders/resources/app/out/vs/workbench/workbench.main.js:3793:636)
    at file:///C:/Program Files/Microsoft VS Code Insiders/resources/app/out/vs/workbench/workbench.main.js:1606:26
    at Array.map (native)
    at a (file:///C:/Program Files/Microsoft VS Code Insiders/resources/app/out/vs/workbench/workbench.main.js:1605:983)
    at file:///C:/Program Files/Microsoft VS Code Insiders/resources/app/out/vs/workbench/workbench.main.js:1512:441
    at file:///C:/Program Files/Microsoft VS Code Insiders/resources/app/out/vs/workbench/workbench.main.js:1510:178
    at e.invokeFunction (file:///C:/Program Files/Microsoft VS Code Insiders/resources/app/out/vs/workbench/workbench.main.js:1361:808)
    at t._tryExecuteCommand (file:///C:/Program Files/Microsoft VS Code Insiders/resources/app/out/vs/workbench/workbench.main.js:2922:960)
    at file:///C:/Program Files/Microsoft VS Code Insiders/resources/app/out/vs/workbench/workbench.main.js:2922:676
    at n.Class.define.cancel.then (file:///C:/Program Files/Microsoft VS Code Insiders/resources/app/out/vs/workbench/workbench.main.js:158:366)
    at t.executeCommand (file:///C:/Program Files/Microsoft VS Code Insiders/resources/app/out/vs/workbench/workbench.main.js:2922:650)
    at e.$executeCommand (file:///C:/Program Files/Microsoft VS Code Insiders/resources/app/out/vs/workbench/workbench.main.js:3076:842)
    at e._doInvokeHandler (file:///C:/Program Files/Microsoft VS Code Insiders/resources/app/out/vs/workbench/workbench.main.js:3135:356)
    at e._invokeHandler (file:///C:/Program Files/Microsoft VS Code Insiders/resources/app/out/vs/workbench/workbench.main.js:3135:74)
    at e._receiveRequest (file:///C:/Program Files/Microsoft VS Code Insiders/resources/app/out/vs/workbench/workbench.main.js:3134:164)
    at e._receiveOneMessage (file:///C:/Program Files/Microsoft VS Code Insiders/resources/app/out/vs/workbench/workbench.main.js:3133:940)
    at file:///C:/Program Files/Microsoft VS Code Insiders/resources/app/out/vs/workbench/workbench.main.js:3132:863
    at file:///C:/Program Files/Microsoft VS Code Insiders/resources/app/out/vs/workbench/workbench.main.js:3135:942
    at e.fire (file:///C:/Program Files/Microsoft VS Code Insiders/resources/app/out/vs/workbench/workbench.main.js:172:496)
    at c (file:///C:/Program Files/Microsoft VS Code Insiders/resources/app/out/vs/workbench/workbench.main.js:306:259)
    at Socket.<anonymous> (file:///C:/Program Files/Microsoft VS Code Insiders/resources/app/out/vs/workbench/workbench.main.js:306:436)
    at emitOne (events.js:96:13)
    at Socket.emit (events.js:191:7)
    at readableAddChunk (_stream_readable.js:178:18)
    at Socket.Readable.push (_stream_readable.js:136:10)
    at Pipe.onread (net.js:560:20)


Make HAProxy stat authentication optional

HAProxy stats can be enabled without authentication.
With this PR the HAProxy-boshrelease could have the same functionality by making the user and password optional.
Additionally, authentication doesn't make sense when the service is bind to localhost and when the trusted_stats_cidrs is limited to <IP_ADDRESS>

Are you running into a problem somewhere with localhost metrics being password protected?

Hi @geofffranks: No, I'm not running into a serious problem. In my current implementation, I would like to configure stat without any authentication (I don't need it and the service is already bound to the localhost, not any service outside of the HAProxy) but since it is required in the release I have to define user and password.
I think it would be good to use authentication when it is required or when the credentials are set.

Did more digging on this, and the default endpoint is *:9000 for stats, not localhost. This is going to negatively impact people who have ha_proxy.stats_enable set. However, I'm open to PRs that won't negatively harm existing deployments, or lead to easy misconfigurations and insecure posture. Feel free to re-open a new PR?


Manifest merger failed

Execution failed for task ':app:processDebugManifest'.

Manifest merger failed : Attribute application@label value=(Kapt Issue) from AndroidManifest.xml:6:9-35
is also present at [com.pacioianu.david:ink-page-indicator:1.2.0] AndroidManifest.xml:12:9-41 value=(@string/app_name).
Suggestion: add 'tools:replace="android:label"' to  element at AndroidManifest.xml:4:5-14:19 to override.

In what version can I find the fix for the manifest merge issue? Version 1.2.0 is not working for me.

In the pull request from above.


@undefined profile id when posting news

Joined with google id and did not filled up user name into profile
proof
PS: I changed my username to 'undefined' and it got rederected to my account.

Hey @dmi3y is this still an issue?
The URL you posted does not really show the error, can you post a screenshot?