NETOBSERV-1617: use filter with packets capture feature

Description
add filter capability for pca feature
Example from running on Kind cluster

build commands locally and use agent custom image

NETOBSERV_AGENT_IMAGE=quay.io/netobserv/netobserv-ebpf-agent:f525832 ./build/oc-netobserv packets --protocol="TCP" --port=443

output pcap
tcpdump -r 2024-06-27T110645Z.pcap
reading from file 2024-06-27T110645Z.pcap, link-type EN10MB (Ethernet), snapshot length 262144
07:06:57.502363 IP <IP_ADDRESS>.41396 > ec2-52-204-93-25.compute-1.amazonaws.com.https: Flags [P.], seq<PHONE_NUMBER>:2078794438, ack<PHONE_NUMBER>, win 458, options [nop,nop,TS val<PHONE_NUMBER> ecr<PHONE_NUMBER>], length 31
07:06:57.502422 IP <IP_ADDRESS>.41396 > ec2-52-204-93-25.compute-1.amazonaws.com.https: Flags [F.], seq 31, ack 1, win 458, options [nop,nop,TS val<PHONE_NUMBER> ecr<PHONE_NUMBER>], length 0
07:06:57.531353 IP ec2-52-204-93-25.compute-1.amazonaws.com.https > <IP_ADDRESS>.41396: Flags [.], ack 31, win 114, options [nop,nop,TS val<PHONE_NUMBER> ecr<PHONE_NUMBER>], length 0
07:06:57.531372 IP ec2-52-204-93-25.compute-1.amazonaws.com.https > <IP_ADDRESS>.41396: Flags [F.], seq 1, ack 32, win 114, options [nop,nop,TS val<PHONE_NUMBER> ecr<PHONE_NUMBER>], length 0
07:06:57.531381 IP <IP_ADDRESS>.41396 > ec2-52-204-93-25.compute-1.amazonaws.com.https: Flags [.], ack 2, win 458, options [nop,nop,TS val<PHONE_NUMBER> ecr<PHONE_NUMBER>], length 0
07:06:58.819363 IP <IP_ADDRESS>.37132 > ec2-44-216-66-253.compute-1.amazonaws.com.https: Flags [P.], seq<PHONE_NUMBER>:1277682569, ack<PHONE_NUMBER>, win 461, options [nop,nop,TS val<PHONE_NUMBER> ecr 783897356], length 31

Dependencies
https://github.com/netobserv/netobserv-ebpf-agent/pull/359
Checklist
If you are not familiar with our processes or don't know what to answer in the list below, let us know in a comment: the maintainers will take care of that.

[ ] Is this PR backed with a JIRA ticket? If so, make sure it is written as a title prefix (in general, PRs affecting the NetObserv/Network Observability product should be backed with a JIRA ticket - especially if they bring user facing changes).
[ ] Does this PR require product documentation?

[ ] If so, make sure the JIRA epic is labelled with "documentation" and provides a description relevant for doc writers, such as use cases or scenarios. Any required step to activate or configure the feature should be documented there, such as new CRD knobs.

[ ] Does this PR require a product release notes entry?

[ ] If so, fill in "Release Note Text" in the JIRA.

[ ] Is there anything else the QE team should know before testing? E.g: configuration changes, environment setup, etc.

[ ] If so, make sure it is described in the JIRA ticket.

QE requirements (check 1 from the list):

[ ] Standard QE validation, with pre-merge tests unless stated otherwise.
[ ] Regression tests only (e.g. refactoring with no user-facing change).
[ ] No QE (e.g. trivial change with high reviewer's confidence, or per agreement with the QE team).

/ok-to-test

/retest

fixed the help strings to match with the new pca fmt for e2e to pass

Was this also meant to be no-qe? If not, why was it merged prior to testing?


Add to builtins

Hey Tal,
Instead of creating a module with a single function, and since sentinel is used 468 times in 58 different python files just in the standard library, I believe it justifies adding it to the builtins.

The usage of sentinel values is vast, and almost every Python module I write or contribute to has created at least one sentinel value.
Importing the module just about everywhere sounds a bit counter-productive, as creating sentinel objects should be as simple as creating a string, a "None" object, or an integer. Plus, I do not see how the "sentinels" module grows to have more than the single "sentinel" class. No matter how it grows, it'll break the uniqueness and thus one of the requirements of a sentinel value.
Lots of love ❤
Bar Harel.

Hey @bharel
This is a reference implementation. The goal has always been to get this into stdlib. See: https://peps.python.org/pep-0661/

Not stdlib, built-ins. It is common enough to justify it :-)

Thanks for the suggestion @bharel!
I disagree that this should be added to the built-ins, though. And even if I agreed, I very much doubt that that would be accepted; there would need to be a strong argument in favor of adding something to Python's built-ins, and I don't think we have one.


Not wokring in Landscape mode

When we try to edit the layout in landscape mode the keyboard cover the whole screen and we are not able to style our text in landscape mode

Yes I agree with that point! same issue with me.


Lesson learned from SPFx examples 🎁

Category

[X] Enhancement

(after 12 years) I am leaving the Microsoft Front-end world,
I believe in WebComponents, and that ain't fun with SharePoint rewriting my precious files
For the past year I have used SPFx examples in my JavaScript classes.
A shame to let educational resources go to waste.
https://github.com/Danny-Engelman/CKTA

This clearly is not an issue, so closing this one. We absolutely welcome pull requests towards existing samples. thx.


Remove Centos6 references from docs

What does this PR do?
Cleans up remaining mentions of Centos 6 in the documents
Which TC components are affected by this PR?

[x] Documentation
[ ] Grove
[ ] Traffic Analytics
[ ] Traffic Monitor
[ ] Traffic Ops
[ ] Traffic Ops ORT
[ ] Traffic Portal
[ ] Traffic Router
[ ] Traffic Stats
[ ] Traffic Vault
[ ] Other _________

What is the best way to verify this PR?
Read through the modified pages of the PR.
Check all that apply

[ ] This PR includes tests
[X] This PR includes documentation updates
[ ] This PR includes an update to CHANGELOG.md
[ ] This PR includes all required license headers
[ ] This PR includes a database migration (ensure that migration sequence is correct)
[ ] This PR fixes a serious security flaw. Read more: www.apache.org/security

Can one of the admins verify this patch?

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/trafficcontrol-PR/2697/
Test PASSed.


chore(dcos-ui): update package to 1.9.7

High-level description
Update the DC/OS UI package to include the latest fixes and improvements.
Corresponding DC/OS tickets (obligatory)
These DC/OS JIRA ticket(s) must be updated (ideally closed) in the moment this PR lands:

DCOS-37558: Remove track.js calls
DCOS-22399, DCOS-22403: Update privacy policy integration

Checklist for all PRs

[ ] Added a comprehensible changelog entry to CHANGES.md or explain why this is not a user-facing change:
[ ] Included a test which will fail if code is reverted but test is not. If there is no test please explain here:
[x] Read the DC/OS contributing guidelines
[x] Followed relevant code rules Rules for Packages and Systemd

Checklist for component/package updates:
If you are changing components or packages in DC/OS (e.g. you are bumping the sha or ref of anything underneath packages), then in addition to the above please also include:

[x] Change log from the last version integrated (this should be a link to commits for easy verification and review): https://github.com/dcos/dcos-ui/releases/tag/v1.9.7
[ ] Test Results:
[ ] Code Coverage (if available):

PLEASE FILL IN THE TEMPLATE ABOVE / DO NOT REMOVE ANY SECTIONS ABOVE THIS LINE
Instructions and review process
What is the review process and when will my changes land?
All PRs require 2 approvals using GitHub's pull request reviews.
Reviewers should be:

Developers who understand the code being modified.
Developers responsible for code that interacts with or depends on the code being modified.

It is best to proactively ask for 2 reviews by @mentioning the candidate reviewers in the PR comments area. The responsibility is on the developer submitting the PR to follow-up with reviewers and make sure a PR is reviewed in a timely manner. Once a PR has 2 ship-it's, no red reviews, and all tests are green it will be included in the next train.

This repo has @mesosphere-mergebot integration. You can interact with the following commands.
@mesosphere-mergebot merge-it
@mesosphere-mergebot bump-ee
@mesosphere-mergebot override-status
@mesosphere-mergebot label [Ready For Review |Holding |Work In Progress |Ship It |Request For Comment]

PR creators can apply one of  [Ready For Review |Work In Progress]. Owners can apply any label.

@mesosphere-mergebot bump-ee

@mesosphere-mergebot label [Ready For Review]

:wave: This PR has been inactive for 3 days. Please review the status checks to see what needs to be done to move it forward or change the label to Work in Progress. Thank you!


Power Status always on on reboot

Hello,
when the esp8266 is rebooted, the status of the air conditioner changes to on with the last mode used even if it is actually off.
I have tried what is written here  #2, but it doesn't work.
To solve I added this code:
switch (this-> power_) {
     case 0:
         this-> mode = climate :: CLIMATE_MODE_OFF;
         this-> publish_state ();
         break;
     default:
         break;
 }

inside void cbiStatusFunction (ACStatus status, int value) override before switch (status)

I have this too. Will give your solution a try.

Like this works indeed!

I've committed this workaround: https://github.com/ginkage/MHI-AC-Ctrl-ESPHome/commit/a43bc7187dba3ea520b662487ad94af0bdf9fdfb
Please check if it works correctly.

I can confirm it works, thanks!


Move to Sapphire: ts-config, eslint-config and prettier-config

Old code is good but after using the sapphire configs for a while, it's better for me to move to their configs.

Fixed with version 5.1.0


HTML

Is there a hightlight for html?

it would be really nice to support HTML

@LincCodes @fvisticot has anyone found a solution?

Hi @LincCodes @fvisticot, it supports HTML, use xml.
xml, html, xhtml, rss, atom, xjb, xsd, xsl, plist, svg are all under the xml language.


Remove _models.py

As discussed during the VIB Ghent 2024 hackathon with @giovp and @melonora, removing the legacy _models.py from the codebase, and access the data directly form layer.metadata['sdata'] would improve the robustness of the code.
In particular we should rely on get_values() for fetching annotations instead of the currently used get_obs(), get_var() etc.
A positive implication of this refactoring is that the mismatch between the annotation indices shown by napari, and the indices used by SpatialData, would disappear, therefore fixing this bug: https://github.com/scverse/napari-spatialdata/issues/242.

get_values won't entirely work. It requires a refactor because currently if you pass on an element it is not allowed to be a table.

This is resolved now, correct? @melonora

I think @melonora did some magic and indeed it automagically disappeared

Jup during the ghent hackathon


Move all logic in ui.ts into the popup

Currently we store/cache a lot of state in a background page for both Firefox and Chrome.
The popup then shares state with this persistent background page.
This is incompatible with uProxy for Cloud, which does not have a persistent background page.
We need to move all logic in the background page into either the popup or uproxy-core, which then minimizes the background page only responsible for setting up the core_connector

done in https://github.com/uProxy/uproxy/pull/1161


Why

I'm used to nano but I want some features from neovim (e.g. Github Copilot support) so why not


Build even more things from source. Fix that "-k" thing.

Revised version of previous pull request at https://github.com/google/end-to-end/pull/35
This builds all dependencies from HEAD.

This was fixed by #305, apart from Closure Templates compiler, but that is now using Maven instead of Ant, and we don't want to introduce even more dependencies.


Bigger image thumbs in explorer for small screen high DPI devices

Description of the new feature / enhancement
Winows 10 has a major shortcoming in Windows Explorer when it comes to showing image thumbnails on small screen/high DPI devices. The option "Extra large icons" produces thumbs of equal size to the "Large icons" option in the View settings.

Could PowerToys maybe correct/enhance this?
Scenario when this would be used?
Thumbnail view of images in Explorer: showing larger thumbnails on small screen/high DPI devices, like for instance the One Notebook Yoga 3Pro with its 8 inch 2560x1600 screen.
Supporting information
No response

I'd like to suggest you also file this in the Feedback hub


Integrated terminal slow to render output

Type: Performance Issue
In the past couple months the integrated terminal's rendering performance has become incredibly slow when there is a decent to large amount of output to the point it's essentially unusable for my day to day work. As shown below text rendering times can be 3x slower or more than using an external terminal. At first I thought it was just due to an increase in data given I generally tail a lot of log files however it affects my normal development actions like running ctest -j30 with a large number of unittest binaries. This occurs even with no extensions enabled other than vscode-remote (necessary).
It seems to be purely a rendering issue. I measured execution time of running the mentioned tests using a desktop stopwatch and compared the result to /usr/bin/time. In powershell/wt/cmd the tests execute in 11.8 seconds. In the integrated terminal it takes 39.7 seconds. However, if I run the unit tests in the integrated terminal and hide the terminal window it will take a similar 12-13 seconds. /usr/bin/time reports 11.27-11.5 seconds for all cases.
Additionally, if I have a separate powershell/wt connected to the same tmux session, the integrated terminal will render at relatively normal speed (visually it seems like it detects the lines are rendered elsewhere and skips ahead to keep up).
Other notes:
My setup is vscode remote and tmux on the remote machine. I have been using this daily for the past two years. I compared with other terminals (powershell, cmd, wt, integrated) to rule out network latency issues. I'm not sure exactly which version I started noticing the performance regression but it was probably sometime around April-May.
EDIT: the unit tests above produce 1669 lines of text total. cat-ing a capture of that runs in 1-2 seconds on integrated vs < 1 second elsewhere. So it seems to be an issue even when the amount of data isn't massive.
VS Code version: Code 1.70.2 (e4503b30fc78200f846c62cf8091b76ff5547662, 2022-08-16T05:35:13.448Z)
OS version: Windows_NT x64 10.0.19044
Modes:
Remote OS version: Linux x64 4.15.0-29-generic
Remote OS version: Linux x64 4.15.0-29-generic
Extensions (1)

Extension
Author (truncated)
Version

remote-ssh
ms-
0.84.0

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492cf:30256860
vstes627:30244334
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242:30382549
pythontb:30283811
vsjup518:30340749
pythonvspyt551cf:30345471
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscoreces:30445986
pythondataviewer:30285071
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30542924
vsaa593cf:30376535
pythonvs932:30410667
wslgetstarted:30449410
cppdebug:30492333
vscaat:30438848
pylanb8912:30545647
vsclangdf:30486550
c4g48928:30535728
d7fjc500:30543455
dsvsc012:30540252
azure-dev_surveyone:30548225
i497e931:30552240

Hi and thanks for all of the info in your report. Could you pls provide your settings.json?

Note: The GPU acceleration setting was from attempting to fix the problem locally by forcing gpu acceleration. The problem exists whether that's in the settings.json or not.
User settings.json:

{
    "remote.SSH.remotePlatform": {
        "sf-isimonson": "linux"
    },
    "workbench.colorTheme": "Dare (rainglow)",
    "workbench.editorAssociations": {
        "*.ipynb": "jupyter-notebook"
    },
    "workbench.sideBar.location": "right",
    "terminal.integrated.inheritEnv": false,
    "editor.minimap.enabled": false,
    "files.autoSave": "afterDelay",
    "terminal.integrated.commandsToSkipShell": [
        "-workbench.action.quickOpen",
        "-workbench.action.terminal.sendSequence",
        "-workbench.action.togglePanel",
        "-workbench.action.terminal.focusFind",
        "-editor.action.clipboardPasteAction",
        "-Terminal: Paste into Active Terminal",
        "-workbench.action.terminal.paste",
        "-workbench.action.quickOpenView"
    ],
    "terminal.integrated.allowChords": false,
    "clangd.onConfigChanged": "restart",
    "notebook.cellToolbarLocation": {
        "default": "right",
        "jupyter-notebook": "left"
    },
    "editor.renderWhitespace": "trailing",
    "editor.fontFamily": "'Inconsolata SemiExpanded Medium',Consolas, 'Courier New', monospace",
    "workbench.editor.navigationScope": "editorGroup",
    "terminal.integrated.enableMultiLinePasteWarning": false,
    "window.zoomLevel": -1,
    "terminal.integrated.gpuAcceleration": "on"
}

Remote settings:

{
    "C_Cpp.clang_format_path": "/home/isimonson/.local/llvm/latest/bin/clang-format",
    "C_Cpp.autocomplete": "Disabled",
    "C_Cpp.formatting": "Disabled",
    "C_Cpp.errorSquiggles": "Disabled",
    "C_Cpp.intelliSenseEngine": "Disabled",
    "clangd.path": "/home/isimonson/.local/llvm/latest/bin/clangd",
    "python.formatting.provider": "black",
    "cmake.generator": "Ninja",
    "python.experiments.enabled": false,
    "python.formatting.blackArgs": [
        "--line-length=100"
    ],
    "python.linting.flake8Args": [
        "--max-line-length=100",
        "--extend-ignore=E203"
    ],
    "remote.autoForwardPortsSource": "output",
    "cmake.clearOutputBeforeBuild": false,
    "cmake.configureOnEdit": false,
    "ols.server.path": "/home/isimonson/.local/bin/ols"
}

I fixed some performance regressions in the terminal renderers over the weekend actually, I expect this to be fixed in 1.72

Let's track in https://github.com/microsoft/vscode/issues/157432


Automated cherry pick of #3778: treewide: 避免使用fmt.Print记录日志

Cherry pick of #3778 on release/2.10.0.
#3778: treewide: 避免使用fmt.Print记录日志

Codecov Report

:exclamation: No coverage uploaded for pull request base (release/2.10.0@cf9576f). Click here to learn what that means.
The diff coverage is 0%.

@@               Coverage Diff                @@
##             release/2.10.0   #3785   +/-   ##
================================================
  Coverage                  ?   7.49%
================================================
  Files                     ?     418
  Lines                     ?   66610
  Branches                  ?       0
================================================
  Hits                      ?    4991
  Misses                    ?   61191
  Partials                  ?     428

Flag
Coverage Δ

#aFlag
7.49% <0%> (?)

Impacted Files
Coverage Δ

pkg/compute/models/schedpolicies.go
5.73% <ø> (ø)

pkg/compute/models/dynamicschedtags.go
7.38% <ø> (ø)

pkg/compute/models/loadbalancer_backendstatus.go
0% <ø> (ø)

pkg/cloudcommon/db/models.go
0% <0%> (ø)

pkg/compute/models/hoststorages.go
0.64% <0%> (ø)

pkg/compute/models/cloudaccounts.go
0.98% <0%> (ø)

pkg/compute/models/storages.go
1.12% <0%> (ø)

pkg/compute/models/disks.go
0.71% <0%> (ø)

pkg/compute/models/skus.go
1.47% <0%> (ø)

pkg/compute/models/dnsrecords.go
29.25% <0%> (ø)

... and 1 more

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 cf9576f...5b33b5b. Read the comment docs.

/lgtm

/approve


The gRPC protocol needs to support the JSON type

What type of enhancement is this?
Tech debt reduction, User experience
What does the enhancement do?
The GreptimeDB already supports JSON type via SQL statements.
But gRPC protocol doesn't support it.
There are two things need to be done:

Support JSON type in the proto file.
Support JSON type in the Go SDK and Java SDK.

Implementation challenges
No response

Java SDK done: https://github.com/GreptimeTeam/greptimedb-ingester-java/pull/52

@daviderli614 Let's add JSON Type support to the Go SDK.

Wait until I finish this PR：https://github.com/GreptimeTeam/greptimedb-ingester-go/pull/51

@daviderli614 Let's add JSON Type support to the Go SDK.

Wait until I finish this PR：https://github.com/GreptimeTeam/greptimedb-ingester-go/pull/51

Go SDK example: https://github.com/GreptimeTeam/greptimedb-ingester-go/blob/main/examples/jsondata/README.md

done


[18.09 backport] Fix client version not being pinned when set, and some refactoring

This backports https://github.com/moby/moby/pull/38909 (Fix client version not being pinned when set) to the 18.09 branch.
When backporting, I noticed that there were some refactorings and cleanups in this area, which I decided to include here as well;
note that those are not strictly needed for the actual fix; the fix is quite small, and could easily be modified to work on the 18.09
branch, but in light of future backports and maintenance, I thought it'd be good to include those refactors.
If this is a concern, I'm happy to create a modified patch and only backport the fix.
Included in this PR:

https://github.com/moby/moby/pull/38125 Add an op func to override Client.scheme
~https://github.com/moby/moby/pull/38486 Remove use of deprecated client.NewEnvClient()~
https://github.com/moby/moby/pull/38606 Move client opts, and deprecated client constructors to separate files
https://github.com/moby/moby/pull/38909 Fix client version not being pinned when set

Description for the changelog
Fix client version not being pinned when set.

@dperny @tiborvass @tonistiigi PTAL (see the first comment for the changes I picked; happy to get your feedback)

I'm fine with this, although it would be better to have a tool where you resolve the conflict once, and save that logic for further rebases until it's unable to decide again.

Looks like https://github.com/moby/moby/pull/38486 has been backported as part of https://github.com/docker/engine/pull/198; rebasing

Looks like this one may need to be vendored in docker/cli as well.

Looks like this one may need to be vendored in docker/cli as well.

Indeed. https://github.com/docker/cli/pull/2100


Use Ceph monitoring (not RGW) network for Dashboard

Use the existing cifmw_cephadm_monitoring_network parameter to configure the Ceph dashboard instead of the cifmw_cephadm_rgw_network parameter. This was not detected earlier because the Ceph playbook set them both to the Ceph public_network, but we recently added a feature to run RGW on a separate network [1].
Also, add retries/delay to the dashboard HTTP check and mange if HTTPS should be used.
[1] https://github.com/openstack-k8s-operators/ci-framework/pull/2301
Jira: https://issues.redhat.com/browse/OSPCIX-506
(cherry-picked from f6e464505a653befe9ee5c458974b6c4737c8129)

/approve


memcache support broken

Description
After upgrading to 1.22.0 from 1.21.11 I see that the Gitea server fails to start when cache.ADAPTER is set to "memcache".
Gitea Version
1.22.0
Can you reproduce the bug on the Gitea demo site?
Yes
Log Gist
https://gist.github.com/tgerczei/2cf428ee26c0d04bc0e7df1ec0f6e81a
Screenshots
No response
Git Version
No response
Operating System
No response
How are you running Gitea?
Via the  gitea/gitea:1.22.0-rootless image pulled from Docker Hub.
Database
None

Sorry, I did search for the open issues first, didn't think of checking closed ones too so I hadn't realized I was duping. Thanks!

1.22-nightly is ready, could you try it? Thank you for reporting the issue and sorry for the inconvenience

Thank you! I've been running it for about 2 hours now, and it seems to have fixed this. Kudos!


fix: fix shape of eliminate_inner regression test

Proposed changes
fix shape of eliminate_inner regression test

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall


Fix dataplane status when roles aren't found

Currently, dataplane is set to ready when the roles aren't in place yet
closes #250

/test dataplane-operator-build-deploy-kuttl

/test dataplane-operator-build-deploy-kuttl

recheck

recheck

recheck

/retest

recheck

recheck

recheck

recheck

recheck

recheck

recheck

recheck

recheck

recheck

recheck

recheck

recheck

recheck

recheck

recheck

@rabi @slagle could you please take another look?

/test dataplane-operator-build-deploy-kuttl

@rabi @rebtoor I had to push changes for fixing the kuttl tests, please take another look

recheck

recheck

recheck


Saving models at timestamps

I am using the train_ppo_gym script and the problem with this script is that it does not save model when the training crashes or is closed for some reason.
Earlier with a3c i used to get 10_except as saved model in case i wanted to stop the training.
I want to save mdoels for evey 100th step or episode. Could you please provide an update on this behavior?

I am using the train_ppo_gym script and the problem with this script is that it does not save model when the training crashes or is closed for some reason.
Could you clarify this?

We have functionality that can checkpoint models periodically, though it has not been implemented for train_ppo_gym.  Checkout the train_ppo_ale.py example: https://github.com/chainer/chainerrl/blob/master/examples/atari/train_ppo_ale.py#L87

Does this answer your question?

Yeah this works. Just one more question is that whether any of the train_ppo files have used LSTM networks?

Checkout https://github.com/chainer/chainerrl/blob/master/examples/atari/train_ppo_ale.py#L131. Not LSTMS, but GRUs.


Fix: Added fallback when download files fails

Allow downloading workspace on phones / browsers where the DirectoryAPI is not available.

[X] Include this change in the Release Notes. If checked, you must provide an end-user friendly description for your change below

The Directory API is not available in all environments - I have intermittently even got errors when running it in chrome on desktop. We try it first, but then fall back to the traditional method of download.

To run this PR locally, use the following command:
docker run -it --rm   -p 3000:3000   -v /var/run/docker.sock:/var/run/docker.sock   --add-host host.docker.internal:host-gateway   -e SANDBOX_RUNTIME_CONTAINER_IMAGE=docker.all-hands.dev/all-hands-ai/runtime:908aa9b-nikolaik   --name openhands-app-908aa9b   docker.all-hands.dev/all-hands-ai/openhands:908aa9b

I wonder how difficult it would be to move this logic into a custom hook and utilize tanstack query for better error handling and retry logic

I think there are a few different error cases here:

Local device does not support the API
User has not given permission to use this API
Permission malfunction (User was not shown the dialog)
Error downloading a single file
Error generating / downloading the zip file.

I think the only one we really want might retry logic on here is Error downloading a single file. Maybe we can do this on a subsequent PR.


HBASE-28758 Remove the aarch64 profile

HBASE-28758 Remove the aarch64 profile

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 54s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

_ master Compile Tests _

+1 :green_heart:
mvninstall
4m 34s

master passed

+1 :green_heart:
compile
11m 23s

master passed

+1 :green_heart:
spotless
0m 52s

branch has no errors when running spotless:check.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m 57s

the patch passed

+1 :green_heart:
compile
11m 56s

the patch passed

+1 :green_heart:
javac
11m 56s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
xmllint
0m  1s

No new issues.

+1 :green_heart:
hadoopcheck
15m 31s

Patch does not cause any errors with Hadoop 3.3.6 3.4.0.

+1 :green_heart:
spotless
1m 19s

patch has no errors when running spotless:check.

_ Other Tests _

+1 :green_heart:
asflicense
0m 26s

The patch does not generate ASF License warnings.

58m 23s

Subsystem
Report/Notes

Docker
ClientAPI=1.46 ServerAPI=1.46 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6128/1/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6128

Optional Tests
dupname asflicense javac codespell detsecrets xmllint hadoopcheck spotless compile

uname
Linux 53b576f2aafa 5.4.0-186-generic #206-Ubuntu SMP Fri Apr 26 12:31:10 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / ca3c1e9ad24c42389895efed41971d9b32327426

Default Java
Eclipse Adoptium-17.0.11+9

Max. process+thread count
191 (vs. ulimit of 30000)

modules
C: . U: .

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
4m 11s

the patch passed

+1 :green_heart:
compile
3m 13s

the patch passed

+1 :green_heart:
javac
3m 13s

the patch passed

+1 :green_heart:
javadoc
2m 50s

the patch passed

+1 :green_heart:
shadedjars
7m 21s

patch has no errors when building our shaded downstream artifacts.

_ Other Tests _

+1 :green_heart:
unit
301m 11s

root in the patch passed.

345m 11s

Subsystem
Report/Notes

Docker
ClientAPI=1.46 ServerAPI=1.46 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6128/1/artifact/yetus-jdk17-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6128

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux d637c5ac1a4c 5.4.0-186-generic #206-Ubuntu SMP Fri Apr 26 12:31:10 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / ca3c1e9ad24c42389895efed41971d9b32327426

Default Java
Eclipse Adoptium-17.0.11+9

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6128/1/testReport/

Max. process+thread count
8768 (vs. ulimit of 30000)

modules
C: . U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6128/1/console

versions
git=2.34.1 maven=3.9.8

Powered by
Apache Yetus 0.15.0 https://yetus.apache.org

This message was automatically generated.


obsolete GO:0042256 Name mature ribosome assembly

One for Harold?
How does
GO:0001732
Name    formation of cytoplasmic translation initiation complex
Ontology    Biological Process
Definition  Joining of the large subunit, with release of IF2/eIF2 and IF3/eIF3. This leaves the functional ribosome at the AUG, with the methionyl/formyl-methionyl-tRNA positioned at the P site.
relate to
GO:0042256
Name    mature ribosome assembly
Ontology    Biological Process
Definition  The aggregation, arrangement and bonding together of the large and small ribosomal subunits into a functional ribosome.
MAture ribosome assembly sounds as though it should be part of translation iniitation, but currently it isn't?
Val
Reported by: ValWood
Original Ticket: geneontology/ontology-requests/11343

Hi Harold,
Did you ever follow up on this one?
Thanks
Val

No I did not.; my initial problem is still valid.
I would not make GO:0042256 part of translation. Just as tRNA biosynthesis is not part of translation.
I don't even know what this term is suppose to be for. The subunits join together during translation, as a complex with various initiation factors, the mRNA, and initiator tRNA.
I'm not sure a monomer really exists in vivo or if these are artifacts of fractionation.
par

I don't even know what this term is suppose to be for.

Thanks Harold, Thats helpful.
This term only has 10 experimental annotations.
http://www.ebi.ac.uk/QuickGO/GTerm?id=GO:0042256#term=annotation
Suggest reannotation and obsoletion?

It looks as though these are all earlier in small or large subunit assembly (at least the ones I looked at).

obsolete
GO:0042256
Name mature ribosome assembly
?
Can we obsolete this term, if Harold does not know what its for?

I don't object; let me run it by my super expert

There are experimental annotations to this term. The SGD one for SDO1 looks reasonable in a quick glance.
So, rather than obsoleting, it seems like it would also be an option to expand the definition to clarify that this occurs in a specific context, i.e. translation.
-Karen

;Yes, I know but I still think that there is no "ribosome assembly"
I hope I can getnTom RajBhandary to update me

Hi Harold. Did you find out yet if this is really a process?
val

@ValWood only 2 of the annotations appear to be literature based, and I think the term is missused. in these annotations and I suggest obsoletion
I think all of the non-subunit terms can go also
ribosome assembly <<<<< change to ribosome subunit assembly??
--mature ribosome assembly   <<<<<<< obsolete
mitochondrial ribosome assembly (4 genes, 5 annotations): <<<< mito ribo subunit assembly?
mitochondrial large ribosomal subunit assembly
ribosomal large subunit assembly
90S preribosome assembly <<<<<<< see note
mitochondrial large ribosomal subunit assembly
ribosomal small subunit assembly
90S preribosome assembly   <<<<<<<
small-subunit processome assembly
note: 90S preribosome assembly is actually a structure formed on the the primary rRNA transcript before it splits into the small subunit and large subunit portions.; it is NOT a 'pre-ribosome"
Suggest renaming to reflect this?

@hdrabkin  I think we should do as you suggest here.
The logic is that this term does not make sense.

So how many annotations are we seeing directly to
GO:0042256 mature ribosome assembly

245 total, 12 EXP

whew! not so bad.

confirms that it isn't aa useful term...annotations would be better elsewhere.

@hdrabkin @pgaudet  can we go ahead with this obsoletion?
cheers
Val

39,874 annotations
still only 12 EXP
but now has IBA

How about merging GO:0042256 mature ribosome assembly into 'GO:0042255 ribosome assembly ?

That works just fine.
v

GO:0042255 ribosome assembly
The aggregation, arrangement and bonding together of the mature ribosome and of its subunits.
and some of the immediate children
The mature ribosome is generated only during translation.
These are children of biogenesis,  and should only pertain to the subunits.
So these terms should go I think
mature ribosome assembly
mitochondrial ribosome assembly
ribosome assembly
The subunit terms are all ok and already placed ok except
90S preribosome assembly, which needs to be placed under ribosomal large subunit biogenesis, as does
mitochondrial large ribosomal subunit assembly (under ribosomal large subunit biogenesis)

Considering that the definition of 90S preribosome assembly is:

The aggregation, arrangement and bonding together of proteins and RNA molecules to form a 90S preribosome. The 90S preribosome represents the complex that forms on the primary rRNA transcript before it splits into the small subunit and large subunit portions.

I'm not sure it's appropriate to put the 90S preribosome assembly under ribosomal large subunit biogenesis since it is a precursor to both the large and small subunits, unless you think it's OK to put it under both, since it is actually true that it is part of the biogenesis of both the large and small subunits at the same time.

could this one be processed? It seems a shame that a term that doesn't make sense has so many annotations.
from above
39,874 annotations
still only 12 EXP
but now has IBA
probably more now...

This one looks like good fodder for the jamboree, open since 2014

To mature ribosome assembly and also (mature) mito rib assembly, make part of translation.
Currently 206 experimental.

GO:0042256    mature ribosome assembly
I only see 13 EXP?

From the discussion, it sounds like mature ribosome assembly represents the small and the large subunit assembling, which occurs during translation. In that sense it seems a legitimate process. The definition needs to be improved, because this is not at all stated.

and is that different from
GO:0001732
Name formation of cytoplasmic translation initiation complex
Ontology Biological Process
Definition Joining of the large subunit, with release of IF2/eIF2 and IF3/eIF3. This leaves the functional ribosome at the AUG, with the methionyl/formyl-methionyl-tRNA positioned at the P site.
?

duplicate of newer more comprehensive ticket
https://github.com/geneontology/go-ontology/issues/20873

Hi @ValWood
I changed the label  of 'mature ribosome assembly' to 'cytosolic ribosome assembly', so we now have
. ribosome assembly
.. mitochondrial ribosome assembly
.. cytosolic ribosome assembly
I think GO:0001732 formation of cytoplasmic translation initiation complex is different, because it contains elongation factors which are not part of the ribosome. See Fig 1 in PMID:29735639

I also tried to clarify the definition of  GO:0001732 formation of cytoplasmic translation initiation complex to
Joining of the large ribosomal subunit with the translation preinitiation complex, with release of IF2/eIF2 and IF3/eIF3 or IF5B/eIF5B. This leaves the functional ribosome at the AUG, with the methionyl/formyl-methionyl-tRNA positioned at the P site.
Please reopen if that doesn't address the issue.

no elongation factors in the initiation complex; just initiation factors.

thanks @hdrabkin I corrected my comment


principle of makeBEVMap

Anyone can help me. I really do not understand the principle of makeBEVMap function, can you explain it step by step. Thank you very much in advance!
def makeBEVMap(PointCloud_, boundary):
Height = cnf.BEV_HEIGHT + 1
Width = cnf.BEV_WIDTH + 1
# Discretize Feature Map
PointCloud = np.copy(PointCloud_)
PointCloud[:, 0] = np.int_(np.floor(PointCloud[:, 0] / cnf.DISCRETIZATION))
PointCloud[:, 1] = np.int_(np.floor(PointCloud[:, 1] / cnf.DISCRETIZATION) + Width / 2)

# sort-3times
sorted_indices = np.lexsort((-PointCloud[:, 2], PointCloud[:, 1], PointCloud[:, 0]))
PointCloud = PointCloud[sorted_indices]
_, unique_indices, unique_counts = np.unique(PointCloud[:, 0:2], axis=0, return_index=True, return_counts=True)
PointCloud_top = PointCloud[unique_indices]

# Height Map, Intensity Map & Density Map
heightMap = np.zeros((Height, Width))
intensityMap = np.zeros((Height, Width))
densityMap = np.zeros((Height, Width))

# some important problem is image coordinate is (y,x), not (x,y)
max_height = float(np.abs(boundary['maxZ'] - boundary['minZ']))
heightMap[np.int_(PointCloud_top[:, 0]), np.int_(PointCloud_top[:, 1])] = PointCloud_top[:, 2] / max_height
# try:
#     heightMap[np.int_(PointCloud_top[:, 0]), np.int_(PointCloud_top[:, 1])] = PointCloud_top[:, 2] / max_height
# except:
#     aa = 1

normalizedCounts = np.minimum(1.0, np.log(unique_counts + 1) / np.log(64))
intensityMap[np.int_(PointCloud_top[:, 0]), np.int_(PointCloud_top[:, 1])] = PointCloud_top[:, 3]
densityMap[np.int_(PointCloud_top[:, 0]), np.int_(PointCloud_top[:, 1])] = normalizedCounts

RGB_Map = np.zeros((3, Height - 1, Width - 1))
RGB_Map[2, :, :] = densityMap[:cnf.BEV_HEIGHT, :cnf.BEV_WIDTH]  # r_map
RGB_Map[1, :, :] = heightMap[:cnf.BEV_HEIGHT, :cnf.BEV_WIDTH]  # g_map
RGB_Map[0, :, :] = intensityMap[:cnf.BEV_HEIGHT, :cnf.BEV_WIDTH]  # b_map

return RGB_Map

Hi @cltdevelop
Please refer to section 2.1 in this paper


Update near-api-js to v3

This PR

52c4ce736bff0581b1e415afc21ae3589bf4791d: removes a few unused dev-dependencies and imports.
5c6f3c2405b8f80a0b01f3d05ae8909fc9478c32: deletes the duplicated nearPrice file (since it should have just been imported).
04584f43f53aacc8dee2ff1177d5524970f6d7fd: Update near-api-js everywhere
26ad431b6dd829c4b2695b170e4a4a5766ef79fc: Updates lerna because of some build error

The last few commits are just fixing CI errors (note that I am receiving inconsistent result logs for linter locally vs in CI)
Test Plan
Existing CI (i.e. project builds, is linted and tests pass).

This is a bit old and stale. Do we actually want to make this change? It would help a lot in the long run, but not sure how it will affect the system. Also, we would want to proceed with v4 soon after.

Oh -- its just mintbase-js. I guess this is fine because its a beta branch
Are we using the beta branch anywhere?

Oh -- its just mintbase-js. I guess this is fine because its a beta branch Are we using the beta branch anywhere?

yes our beta branch is used everywhere.

This is gonna be force-reverted


tree.min.js error

I'm receiveing the following error in Google Chrome Console:
852 three.min.js:302 Uncaught InvalidStateError: Failed to execute 'createPattern' on 'CanvasRenderingContext2D': The canvas width is 0.
The version of Google Chrome is Versión 49.0.2623.87 (64-bit)
My O.S. is Ubuntu 14.04
I can't figure out how avoid that error, and I can't see the video, I only see a grey box in the center of the player container.
I've donwloaded the demo.html and the same error.
I'll will appreciate if you can help us to solve this problem.
Thanks.

Update: I've attached an image with the error.

Hi Lusim,
I am getting the same error . as you are getting same error.
Any suggestion how the Issue can be solved.

Hi @adityait1
Not yet. I delegate the player feature of our site to the front end devs.

Hi luis
Can you pls suggest some way to play 360 videos in my browser
Can you pls share any sample code.
I shall appreciate.
Thank you
Aditya Venkat
Sent from my iPhone

On Jul 8, 2016, at 5:38 PM, Ricardo Luis Mender<EMAIL_ADDRESS>wrote:
Hi @adityait1
Not yet. I delegate the player feature of our site to the front end devs.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.


How to add an adetailer

Hello author, I have been following your library and there have been no updates recently. May I ask how to add adetailer to this library

Same question


[UpdatePlugin]  ehntoo binaryninja-svd v2.0.0

Please update my plugin:
Author: Me
Repo name: binaryninja-svd
Release: https://github.com/ehntoo/binaryninja-svd/releases/tag/v2.0.0
SVD annotations are now persistent, and includes an awesome new SVD Browser from @psifertex

\o/
(added)


Fix undefined this.args in visualizer

First of all thanks for this awesome library :)
Currently it will throw an error
        let around = this.args.linesBefore;
                               ^
TypeError: Cannot read property 'linesBefore' of undefined

when calling Parjs.visualizer, either in browser environment or using node 11.0.
I'm not quite sure about the purpose of using this here, but removing them will resolve the problem.

Thanks!
I'm glad you like the library and I'm grateful for your work :smile:


AdvancedDependencyConvergence rule

After the release of v3.2 of the plugin, I discovered some breaking changes in API, thus had problems migrating my rule https://github.com/alexey-anufriev/advanced-enforcer-rules to a new version along with the support of the previous plugin versions.
For this reason, I have reimplemented the missing features directly in the original rule.

Following this checklist to help us incorporate your
contribution quickly and easily:

[ ] Make sure there is a JIRA issue filed
for the change (usually before you start working on it).  Trivial changes like typos do not
require a JIRA issue.  Your pull request should address just this issue, without
pulling in other changes.
[x] Each commit in the pull request should have a meaningful subject line and body.
[ ] Format the pull request title like [MENFORCER-XXX] - Fixes bug in ApproximateQuantiles,
where you replace MENFORCER-XXX with the appropriate JIRA issue. Best practice
is to use the JIRA issue title in the pull request title and in the first line of the
commit message.
[x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[x] Run mvn clean verify to make sure basic checks pass. A more thorough check will
be performed on your pull request automatically.
[x] You have run the integration tests successfully (mvn -Prun-its clean verify).

If your pull request is about ~20 lines of code you don't need to sign an
Individual Contributor License Agreement if you are unsure
please ask on the developers list.
To make clear that you license your contribution under
the Apache License Version 2.0, January 2004
you have to acknowledge this by using the following check-box.

[x] I hereby declare this contribution to be licenced under the Apache License Version 2.0, January 2004

[ ] In any other case, please file an Apache Individual Contributor License Agreement.

For new rule parameter we need a jira issue - please create one


drumkv1: 0.9.0 -> 0.9.2

Motivation for this change
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Fits CONTRIBUTING.md.

@GrahamcOfBorg build drumkv1

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: drumkv1
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Success on x86_64-linux (full log)
Attempted: drumkv1
Partial log (click to expand)
shrinking /nix/store/sly7crb7s44ill8i9h14vpbddknrpk78-drumkv1-0.9.2/lib/libdrumkv1.so.0.9.2
shrinking /nix/store/sly7crb7s44ill8i9h14vpbddknrpk78-drumkv1-0.9.2/lib/libdrumkv1_ui.so.0.9.2
shrinking /nix/store/sly7crb7s44ill8i9h14vpbddknrpk78-drumkv1-0.9.2/bin/drumkv1_jack
gzipping man pages under /nix/store/sly7crb7s44ill8i9h14vpbddknrpk78-drumkv1-0.9.2/share/man/
/nix/store/vp40my263xk32f07788srrgl59rycsna-binutils-2.30/bin/strip is /nix/store/vp40my263xk32f07788srrgl59rycsna-binutils-2.30/bin/strip
stripping (with command /nix/store/vp40my263xk32f07788srrgl59rycsna-binutils-2.30/bin/strip and flags -S) in /nix/store/sly7crb7s44ill8i9h14vpbddknrpk78-drumkv1-0.9.2/lib  /nix/store/sly7crb7s44ill8i9h14vpbddknrpk78-drumkv1-0.9.2/bin
patching script interpreter paths in /nix/store/sly7crb7s44ill8i9h14vpbddknrpk78-drumkv1-0.9.2
checking for references to /build in /nix/store/sly7crb7s44ill8i9h14vpbddknrpk78-drumkv1-0.9.2...
postPatchMkspecs
/nix/store/sly7crb7s44ill8i9h14vpbddknrpk78-drumkv1-0.9.2

Success on aarch64-linux (full log)
Attempted: drumkv1
Partial log (click to expand)
shrinking /nix/store/1g3c3p10jjkfmcdnd48a4zi76z9siniv-drumkv1-0.9.2/lib/lv2/drumkv1.lv2/drumkv1.so
shrinking /nix/store/1g3c3p10jjkfmcdnd48a4zi76z9siniv-drumkv1-0.9.2/lib/libdrumkv1_ui.so.0.9.2
shrinking /nix/store/1g3c3p10jjkfmcdnd48a4zi76z9siniv-drumkv1-0.9.2/lib/libdrumkv1.so.0.9.2
gzipping man pages under /nix/store/1g3c3p10jjkfmcdnd48a4zi76z9siniv-drumkv1-0.9.2/share/man/
/nix/store/8wl4dykwswy42wxj671b6k7vk2ydxg86-binutils-2.30/bin/strip is /nix/store/8wl4dykwswy42wxj671b6k7vk2ydxg86-binutils-2.30/bin/strip
stripping (with command /nix/store/8wl4dykwswy42wxj671b6k7vk2ydxg86-binutils-2.30/bin/strip and flags -S) in /nix/store/1g3c3p10jjkfmcdnd48a4zi76z9siniv-drumkv1-0.9.2/lib  /nix/store/1g3c3p10jjkfmcdnd48a4zi76z9siniv-drumkv1-0.9.2/bin
patching script interpreter paths in /nix/store/1g3c3p10jjkfmcdnd48a4zi76z9siniv-drumkv1-0.9.2
checking for references to /build in /nix/store/1g3c3p10jjkfmcdnd48a4zi76z9siniv-drumkv1-0.9.2...
postPatchMkspecs
/nix/store/1g3c3p10jjkfmcdnd48a4zi76z9siniv-drumkv1-0.9.2


I'm failed when I  did start npm server  and I am using win10 os

D:\ReactNative\myfour>npm start

<EMAIL_ADDRESS>start D:\ReactNative\myfour
node node_modules/react-native/local-cli/cli.js start
events.js:160
throw er; // Unhandled 'error' event
^

Error: write EINVAL
at exports._errnoException (util.js:1022:11)
at WriteStream.Socket._writeGeneric (net.js:715:26)
at WriteStream.Socket._write (net.js:734:8)
at doWrite (_stream_writable.js:334:12)
at writeOrBuffer (_stream_writable.js:320:5)
at WriteStream.Writable.write (_stream_writable.js:247:11)
at WriteStream.Socket.write (net.js:661:40)
at WriteStream.stream.write (D:\ReactNative\myfour\node_modules\ansi\lib\newlines.js:36:21)
at Object.execFileSync (child_process.js:506:20)
at Object.run (D:/ReactNative/myfour/node_modules/react-native/local-cli/cliEntry.js:159:16)
npm ERR! Windows_NT 10.0.14393
npm ERR! argv "D:\Program Files\nodejs\node.exe" "D:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "start"
npm ERR! node v7.1.0
npm ERR! npm  v3.10.9
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>start: node node_modules/react-native/local-cli/cli.js start
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script 'node node_modules/react-native/local-cli/cli.js start'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the myfour package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node node_modules/react-native/local-cli/cli.js start
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs myfour
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls myfour
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     D:\ReactNative\myfour\npm-debug.log
D:\ReactNative\myfour>npm bugs myfour
npm ERR! Windows_NT 10.0.14393
npm ERR! argv "D:\Program Files\nodejs\node.exe" "D:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "bugs" "myfour"
npm ERR! node v7.1.0
npm ERR! npm  v3.10.9
npm ERR! code E404
npm ERR! 404 Registry returned 404 for GET on https://registry.npm.taobao.org/myfour
npm ERR! 404
npm ERR! 404  'myfour' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.
npm ERR! Please include the following file with any support request:
npm ERR!     D:\ReactNative\myfour\npm-debug.log

What are the contents of D:\ReactNative\myfour\npm-debug.log?
Can you try creating a new app with 'react-native init' and run that?

Same Issue here,
as attachment you can find my npm-debug.log which I made with a new init as you adviced.
npm-debug.txt

Closing this issue because it has been inactive for a while. If you think it should still be opened let us know why.


[BUG] ESLINT Typescript throws error: types/index.d.ts(87,2): 'addSection' lacks return-type annotation

Category

[ ] Enhancement
[X] Bug
[ ] Question
[ ] Documentation gap/issue

Version
Please specify what version of the library you are using: [3.3.1]
Please specify what version(s) of PowerPoint you are targeting: [ANY]
Expected / Desired Behavior / Question
No error or warning when linting testing or building my project.
Observed Behavior
The linting (and therefore building) crashes with the following error :
ERROR in ...MYPROJECT.../node_modules/pptxgenjs/types/index.d.ts(87,2):
87:2 'addSection', which lacks return-type annotation, implicitly has an 'any' return type.
    85 |         * @example pptx.addSection({ title:'Charts' });
    86 |         */
  > 87 |        addSection(section: PptxGenJS.SectionProps)
       |        ^
    88 |        /**
    89 |         * Add a new Slide to Presentation
    90 |         * @param {AddSlideProps} options - slide options

Steps to Reproduce
Use @nuxtjs/eslint-config-typescript to enforce ESLINT Typescript
https://typescript.nuxtjs.org/guide/lint.html#configuration
then build the project

Thanks @guillaumeprevost
Fixed in next release.
addSection(section: PptxGenJS.SectionProps): void


dart:ffi

The Dart FFI feature is now available.
This allows you to call c code direct in flutter without having to use Method Channels.
Hence its MUCH faster when you can talk directly to the c code.
https://github.com/flutter/flutter/issues/7053
https://github.com/dart-lang/sdk/blob/master/samples/ffi/sqlite/docs/sqlite-tutorial.md

This is relevant at the Sqflite level, which manages the connection to the database with method channels. This module is higher level and will not implement this.


Fix broken links on the site

I ran a local crawler on the site and here's the list of links that were broken:
http://localhost:8080/docs/maintainer-guide/governance links to missing page. List of links is ["http://localhost:8080/docs/maintainer-guide/contributing"]
Error 404 for http://localhost:8080/docs/maintainer-guide/contributing
http://localhost:8080/docs/6.0.0/user-guide/configuring links to missing page. List of links is ["http://localhost:8080/docs/6.0.0/rules/"]
Error 404 for http://localhost:8080/docs/6.0.0/rules/
http://localhost:8080/docs/5.0.0/developer-guide/working-with-rules links to missing page. List of links is ["http://localhost:8080/docs/5.0.0/rules/","http://localhost:8080/docs/5.0.0/rules/"]
Error 404 for http://localhost:8080/docs/5.0.0/rules/
http://localhost:8080/docs/5.0.0/user-guide/configuring links to missing page. List of links is ["http://localhost:8080/docs/5.0.0/rules/"]
http://localhost:8080/docs/4.0.0/user-guide/command-line-interface links to missing page. List of links is ["http://localhost:8080/docs/4.0.0/user-guide/formatters/","http://localhost:8080/docs/4.0.0/user-guide/formatters/","http://localhost:8080/docs/4.0.0/user-guide/formatters/","http://localhost:8080/docs/4.0.0/user-guide/formatters/","http://localhost:8080/docs/4.0.0/user-guide/formatters/","http://localhost:8080/docs/4.0.0/user-guide/formatters/","http://localhost:8080/docs/4.0.0/user-guide/formatters/","http://localhost:8080/docs/4.0.0/user-guide/formatters/","http://localhost:8080/docs/4.0.0/user-guide/formatters/","http://localhost:8080/docs/4.0.0/user-guide/formatters/","http://localhost:8080/docs/4.0.0/user-guide/formatters/","http://localhost:8080/docs/4.0.0/user-guide/formatters/"]
Error 404 for http://localhost:8080/docs/4.0.0/user-guide/formatters/
http://localhost:8080/blog/2016/02/eslint-v2.0.0-released links to missing page. List of links is ["http://localhost:8080/docs/developer-guide/code-path-analysis.html"]
Error 404 for http://localhost:8080/docs/developer-guide/code-path-analysis.html
http://localhost:8080/docs/2.0.0/developer-guide/working-with-rules links to missing page. List of links is ["http://localhost:8080/docs/2.0.0/developer-guide/code-path-analysis"]
http://localhost:8080/docs/2.0.0/developer-guide/code-path-analysis links to missing page. List of links is ["http://localhost:8080/docs/2.0.0/developer-guide/code-path-analysis/"]
Error 404 for http://localhost:8080/docs/2.0.0/developer-guide/code-path-analysis/
http://localhost:8080/blog/2015/06/eslint-0.24.0-released links to missing page. List of links is ["http://localhost:8080/blog/2015/preparing-for-1.0.0"]
Error 404 for http://localhost:8080/blog/2015/preparing-for-1.0.0
Total pages: 939. Errors found 7

I can look at this today, if you don't mind.
A spot check revealed some destinations are easy to figure out.

These three pages don't exist right now.

/docs/6.0.0/rules/
/docs/5.0.0/rules/
/docs/4.0.0/user-guide/formatters/

/3.0.0/rules/ and /4.0.0/rules/ have an index.liquid  5 and 6 do not.
user-guide/formatters/index.md exists in 3.0.0 and 5.0.0, but not in 4.0.0.
I'm not sure what the team would like to do about this.
The remaining two have obvious fixes:

http://localhost:8080/docs/2.0.0/developer-guide/working-with-rules links to missing page. List of links is ["http://localhost:8080/docs/2.0.0/developer-guide/code-path-analysis"]
can change to /docs/2.0.0/developer-guide/code-path-analysis.html
http://localhost:8080/docs/maintainer-guide/governance links to missing page. List of links is ["http://localhost:8080/docs/maintainer-guide/contributing"]
can probably change to /docs/developer-guide/contributing

Thanks for digging into that! I think you should be able to check out the version tags on the repo to find the missing files (for example, if you check out the v6.8.0, you should be able to find the missing rules index for v6).

Also https://eslint.org/docs/rules/no-useless-backreference.

@dotJoel Are you still willing to work on this?

@kaicataldo yea.. I will try to finish it up today.
I have some changes ready, but need to address broken links found by running LinkChecker myself.  Some seemed related to what I have done so far on this new pending branch.

@btmills this issue should be resolved by the two PRs. I was not using "refs" the second time to imply that there was work remaining.
I feel this issue is safe to close.


fix typescript issues (old node + previous @types/keyv compat issues) + apply consistent linter rules

Hello, I'm currently having problems using a dependent of this. The cause is that imports are being made from node:events, a notation that is only supported in very new versions of the @types/node package (I think 16.6 and up). To support node 12 and 14, I changed the imports to events and used the named import (the default import was actually broken for me).
Additionally, I resolved a compatibility issue for people that used the @types/keyv package - the new definitions were missing the Store type. Aliasing it to the "new" Keyv type works fine for now, but there should be some minor refactoring for this in the future, probably.

It is literally impossible to fix some of these errors without touching the linter config. You have conflicting rules set up. @typescript-eslint/object-curly-spacing is set up to prohibit spacing, while object-curly-spacing requires them.
So, how do you actually want it?

I see that the "override config" you're extending literally contains only object-curly-spacing, which conflicts with the TypeScript defaults. I'll see what I can do to fix this. I'll probably remove that base config.

Apparently, xo does something weird with the rules. For TS files only, it loads a separate ruleset and additional plugins. So I can't add the @typescript-eslint/* rule, because it would break all non-TS files.
There's a few different ways to fix this:

Add a tsconfig.json file to every package (which probably should be the case anyway) and enable the ts flag in the xo config
Opt for the default setting (no spaces allowed inside curly braces)
Get rid of xo and set up the linter manually (my personal favorite, but probably unlikely to happen 😉)

Okay, option 1 is out of the question, since there's a bunch of idioms in the JS files that just fail to check against the default TypeScript rules... Going for option 2 then.

Okay, this has become much more invasive than I thought it would.

If you want, I can undo the last commit, and you can then go and override the actions results, it's up to you.

Guys,
Thank you for working on this bug. I've no idea which package is relying on keyv.
I also now face critical issue with:
node_modules/@types/cacheable-request/index.d.ts(13,10): error TS2305: Module '"keyv"' has no exported member 'Store'.
node_modules/keyv/src/index.d.ts(1,8): error TS1259: Module '"node:events"' can only be default-imported using the 'esModuleInterop' flag
I'll post it here for whoever else has it and maybe will find this thread in future. My esModuleInterop is true

@d-fischer first, I want to thank you so much for taking the lead on this and starting to get a fix going for the types issue showing an error:
node_modules/@types/cacheable-request/index.d.ts(13,10): error TS2305: Module '"keyv"' has no exported member 'Store'.
node_modules/keyv/src/index.d.ts(1,8): error TS1259: Module '"node:events"' can only be default-imported using the 'esModuleInterop' flag

I would like to roll back all the changes except setting the type definition locally and fixing it to handle Store. Can we just fix that in the index.d.ts file? That is the major change on the 4.2.0 release is that we are now having local type definition files.
Once that is completed and fixed we can move to the next update which is if we should remove node:events to just events and run that as another pull request.
@alphmth - looks like your latest pull request with moving type definition locally is causing an error which we need to resolve ASAP.
@pavelkalin - go ahead and stay on the previous version until we resolve this.

node:events is not available if you use an older @types/node package. The one you are using is irrelevant, TS prioritizes the one that's in the end user's package.json. This is a breaking change and should be fixed ASAP, it shouldn't be reverted. I can revert the linter changes that make the Actions fail though.

Also, it's hard to just "stay on the previous version". For me, this is a deeply nested dependency and I have no control over its version range. This blocks me.

For the record, this is the console output if you have @types/node@^12 installed:
../../node_modules/@types/cacheable-request/index.d.ts:13:10 - error TS2305: Module '"keyv"' has no exported member 'Store'.
../../node_modules/keyv/src/index.d.ts:1:26 - error TS2307: Cannot find module 'node:events' or its corresponding type declarations.

For the record, this is the console output if you have @types/node@^12 installed, with the version of keyv that's currently on npm:
../../node_modules/@types/cacheable-request/index.d.ts:13:10 - error TS2305: Module '"keyv"' has no exported member 'Store'.
../../node_modules/keyv/src/index.d.ts:1:26 - error TS2307: Cannot find module 'node:events' or its corresponding type declarations.

@d-fischer Running the checks now. Do you believe this pull request is ready to be tested against?

I already did all the checks locally. They fail with a lot of linter errors, which is what the last commit was about, which you insisted I revert.
Before reverting, all the checks were fine on my local system, including both linter and tests.

I already did all the checks locally. They fail with a lot of linter errors, which is what the last commit was about, which you insisted I revert.
Before reverting, all the checks were fine on my local system, including both linter and tests.

OK. please apply all changes back in so I can validate. Sorry for the hassle on this as I wanted to get this in a better separation.

@d-fischer - running checks and validating code now.

@d-fischer - are you also using cacheable-request?

@d-fischer - are you also using cacheable-request?

My dependency chain according to yarn:
ngrok#got#cacheable-request#keyv

I added, "keyv": "4.1.1"  as a dependency to make it work. It works now. Workaround definitely.

@adityap31 The release of 4.2.1 allowed me to remove my workarounds.

Yes, thank you! no more issues from my side as well.


Allow #stimulate to use promises

Feature
Description
The basic idea here is that we keep a table of promises indexed by
randomly generated UUIDs. The UUIDs are sent to the server on each
reflex call and are returned with responses, and thus can be used to
look up the promise we kept in our table, which we then resolve or
reject. This allows us to do stuff like
this.stimulate('MyReflex#action')
  .then(() => this.doSomething())
  .catch(() => this.handleError())

Why should this be added
Primar benefits:

Using promises gives you the option to keep callback code near the location of #stimulate calls, as well as implement per-call behaviour as opposed to generalized callback methods.

You can take advantage of the full Promise API, including functions like Promise.all, Promise.allSettled, and Promise.race, allowing for simple reflex orchestration when you are making multiple calls to reflexes and need to ensure behaviour based on their overall executions.

You can use await/async syntactic sugar to further simplify some code patterns.

Checklist

[x] My code follows the style guidelines of this project
[x] Checks (StandardRB & Prettier-Standard) are passing

Having slept on this, I'm still excited about it, but there are a few things we should cover if we're going to merge this concept. It's a Venn diagram:

Can we make the data that you'd get back from a callback or DOM event available to the closure inside of then()? And the error info within catch()? I don't have much experience working with Promises so perhaps it's already there - but I don't think so. If you look at this data we make available in the callbacks for success and failure, this is what I have in mind: element, reflex, [error].
Can we make the UUID available to the callback and DOM events? I would add it as a third method to the signature eg. element, reflex, uuid and element, reflex, uuid, error

Essentially, I'm trying to get all three potential methods of responding to a Reflex operation to have similar data available to them; equal if possible.
Apologies in advance if any of the above seems to miss obvious points. Again, I'm not super-confident working with Promises.

Fixed and re-rolled. You now get a single argument (which is apparently all the Promise API supports which I had forgotten) which contains the following:

data, which contains all of the data structure that was sent in the first place to the reflex, which itself contains the promise UUID

element is the... element...

event as dispatched by the reflex

This looks solid. Thank you for putting in the work on this. I'll be testing tomorrow and over the weekend.

I've tested this and think it's a great addition. It also helped tease out a bug (that I'll fix shortly) with client side error handling of server errors.
Also, here's an example of how to extract data from the promise payloads.
this.stimulate('MyReflex#example')
  .then(payload => {
    const { data, element, event } = payload
    const { attrs, reflexId } = data
    // * attrs - an object that represents the attributes of the element that triggered the reflex
    // * data - the data sent from the client to the server over the web socket to invoke the reflex
    // * element - the element that triggered the reflex
    // * event - the source event
    // * reflexId - a unique identifier for this specific reflex invocation
  })
  .catch(payload => {
    const { data, element, event } = payload
    const { attrs, reflexId } = data
    const { error } = event.detail.stimulusReflex
    // * attrs - an object that represents the attributes of the element that triggered the reflex
    // * data - the data sent from the client to the server over the web socket to invoke the reflex
    // * element - the element that triggered the reflex
    // * error - the error message from the server
    // * event - the source event
    // * reflexId - a unique identifier for this specific reflex invocation
  })


Exception in viewLines.ts

I was editing a file, and this came up, couldn't reproduce it further. 😢

uh-oh


Problem in viewing my calendar

Steps to replicate

Access the web-app link: https://gonana-o.web.app/
Log in as a student
then book an appointment in the calendar

There is no sign of appointment in the calendar

You issue is acceptable, defect, as it is not included in the Developemnt calendar view feature to booking of appointment, I will grab this task

please verify this , the fix is already been mereged

Good evening po sir I checked it and move the Task in the async collab

please verify this , the fix is already been mereged

the problem is fixed po sir, for student to view a sign of appointment in the calendar

please verify this , the fix is already been mereged

I'm sorry for not verifying it yesterday po sir, but I checked and moved the task in async collab regarding this issue po sir Thank you for informing po sir


Canvas mouse move events not fired when another canvas put over top.

Fiddle with very simple example below.
Note the left side has the simple Canvas over top the polygon, while the right does not and is interactable
https://jsfiddle.net/9zy64frx/12/

Leaflet version I'm using: 1.3.1
Browser (with version) I'm using: Chrome 67.0.3396.87, IE Edge 41.16299.402.0, Firefox 60.0.2
OS/Platform (with version) I'm using: Win 10

When having preferCanvas enabled and drawing a Polygon, the Canvas object binds events to the Canvas object itself. If any 3rd party plug-in wants to also use a Canvas, depending on the order the two canvas's are added to the DOM, the Leaflet Canvas will not have the events fired when the other canvas is on top as the mouse is not interactive with the canvas below the other.
Without adding every object that can be created into the canvas, simply moving the binding for events from the Leaflet Canvas onto the Map itself should eliminate the issue.

Add the CSS rule
pointer-events: none;

to the canvas that you are overlaying. Your mouse events should now propagate through.
Here's an updated fiddle
https://jsfiddle.net/9zy64frx/14/

@jbccollins
This assumes the canvas you are creating does not want to be interacted with. If the canvas is made a little more complex, such as adding any type of interactivity, then the canvas you put over top will not be able to function due to this CSS.

Well. IMO handling mouse interactions with third party overlays (canvas or otherwise) is outside the scope of Leaflet core.
I personally use https://github.com/Sumbera/gLayers.Leaflet which extends Leaflet to give you a built in L.canvasLayer that plays nicely with other Leaflet elements.
const lat = 0;
const lng = 0;
L.canvasLayer().delegate({
      onDrawLayer: info => {
        // Draw whatever you need to draw right here
        var ctx = info.canvas.getContext('2d');
        ctx.clearRect(0, 0, info.canvas.width, info.canvas.height);
        const dot = info.layer._map.latLngToContainerPoint([lat, lng]);
        ctx.beginPath();
        ctx.arc(dot.x, dot.y, 5, 0, Math.PI * 2);
        ctx.fill();
        ctx.closePath();
      }
    });

And if you happen to be using React I can give you the React wrapper component I use for that as well :)

Please stop referencing or pointing to projects which have no interactivity on the canvas you are adding, this is arguing apples to oranges. If you want to know where this is coming from, it is with https://github.com/eJuke/Leaflet.Canvas-Markers project. This fulfills a gap in Leaflets implementation of canvas for allowing actual Markers (not Circle Markers) to be created in a canvas, with the implementation of everything that comes with markers.
Simply put, changing the bindings of Leaflet's canvas implementation to the map and stopping propagation when an element is "hit" will allow for other canvas's to interact with the map as well and not just Leaflets.
As a work around is to insure all Canvas implementations which are wanted to have interactions are pushed to the back of the Dom and is created in the overlay pane. This requires adding
L.DomUtil.toBack(this._container);
after the containers add to the Pane.

If you want to make a PR to Leaflet core that does this then go for it. I think it's unlikely to get merged but it can't hurt to try I guess.
In the meantime...
You could try using color masking hit detection for events drawn on a canvas to achieve interactivity.
Here's a working demo:
https://jsfiddle.net/uyhzx2qd/52/
Try clicking on the shapes
There are some drawbacks to doing that but I get the feeling that you won't be interested in this option so /shrug

I don't think we are on the same page...
It is not that I cannot get interactivity. It is the fact that when preferCanvas is enabled and anything is drawn on the Canvas (such as an L.polygon), you can not interact with the canvas when you draw over top it.
Taking your example: enabling preferCanvas & adding a Polygon before the adding of your canvas, prevents any interaction with the Blue polygon behind.
https://jsfiddle.net/uyhzx2qd/59/
This is also not an issue with Leaflet Core (Sorry, I did not realize Leaflet was split in this manor), it is dealing specifically with layer/vector/Canvas

Related to: #5739, #5752
This is definitely an issue.
Adding any kind of canvas layer blocks events to any other layers below it in the stack 😞
There is an event forwarding PR (#6012) that was previously considered but needs further work.

As @danwild says, this is a duplicate of #5739, so I'm going to close this; there are workarounds, although not nice.
#5752 is an attempt to address the issue, but it's not complete and it seems the author lost interest in finishing it (don't be fooled by the PR saying "Merged" - I accidentally merged it, but then reverted it, so it's still not in any release Leaflet version).

Hi @perliedman, given that this issue and #5739 are both closed, are we saying this is not an issue (IMO it is, given that canvas is supported by leaflet now)?
If not, at the very least it should probably be noted in the docs, that - when using a canvas layer, interaction with any other layers below it in the stack will be void.
I'd imagine many would think twice before using canvas if they were aware of this major limitation.
The only current forewarning in then docs are for IE8, and that "overlapping geometries might not display properly in some edge cases"

@danwild This is a quite fundamental difference between SVG and Canvas: Canvas is a solid layer that you can either disable pointer events entirely for, or it will catch all events. We could work around this fact with hacks (like #5752 attempts), but it will be hacks to emulate events passing through the layer. You can also work around it with the hack I linked to in #5739: https://gist.github.com/perliedman/84ce01954a1a43252d1b917ec925b3dd - I've used that in a Leaflet app with multiple Canvas / VectorGrid layers, it worked out ok.
I would agree that a word of warning in the docs would be nice, help in the form of a PR would be great. Perhaps finishing #5752, or even better turning it into a plugin, would also be a nice solution, IMO. Having said that, for a lot of common use cases, this is not an issue though, since interaction is with overlays that will all be in the canvas.

I understand the challenges introduced by canvas elements not existing in the dom as with other layers, but think that given leaflet supports multiple overlays, and is by it's own definition:

an open-source JavaScript library
for mobile-friendly interactive maps

Suggests (to me anyway) that it should handle interaction for more than one overlay at a time, but yes - I accept in reality any solution is going to be a hack (.."event emulation" sounds nicer? 😉).
Regardless - thanks for the additional info and gist, I will look a little closer and think about how a plugin might work (I'd like mousemove events so might be dreaming..).
I also understand a generic solution might be tricky given layers can be nested arbitrarily in panes..

Just a quick note - I went ahead and hacked a plugin together, it is based pretty heavily on the approach in your gist @perliedman.
Plugin is a little crude but pretty much achieves what I need.
Cheers,
Dan


[BUG]: sqlite-proxy - findMany query field mapping discrepancy in schema

What version of drizzle-orm are you using?
0.29.0
What version of drizzle-kit are you using?
No response
Describe the Bug
The findMany function, when invoked, retrieves records from the database but does not map the fields of these records in accordance with the schema.

Expected behavior
When executing a findMany query, the function is expected to retrieve multiple records from the specified table and accurately map these records' fields according to the structure defined in the schema. This mapping should correctly align database fields with their corresponding schema definitions, ensuring that the retrieved data is formatted and structured as per the model's design.
Environment & setup
OS: Ubuntu 20.04.2 LTS x86_64
Kernel: 6.2.0-1018-gcp
CPU: AMD EPYC 7B12 (8) @ 2.249GHz
https://replit.com/@hidemire/drizzle-sqlite-proxy
Feel free to ask additional questions.

Schema is sync. You can check the source code here https://github.com/hidemire/drizzle-sqlite-proxy

I may be wrong, but it seems that this is due to the lack of customResultMapper in the implementation of the prepareQuery method of the sqlite proxy session.
abstract prepareQuery()
implementation prepareQuery()
And it seems that there is already an open issue in this regard https://github.com/drizzle-team/drizzle-orm/issues/873

I'll check your reproduction and see if this pr solves it.

I'm trying to reproduce the code provided in this example from the repo.
Everything works fine. But when we add following lines in index.ts things break:
const allUsersResponse = await db.query.users.findMany();
console.log("allUsersResponse : ", allUsersResponse );
// prints: `allUsersResponse :  [ [ 1, 'user1'<EMAIL_ADDRESS>1 ] ]`

The field mapping doesn't work. However it does work when using the db.select syntax:
const allUsersResponse  = await db.select().from(users);
console.log("allUsersResponse : ", allUsersResponse );
// prints: `allUsersResponse :  [ { id: 1, name: 'user1', email<EMAIL_ADDRESS>cityId: 1 } ]`

Note: I did add the schema while intitializing the drizzle db:
const db = drizzle(
    async (sql, params, method) => {
      try {
        const rows = await axios.post("http://localhost:3000/query", {
          sql,
          params,
          method,
        });

        return { rows: rows.data };
      } catch (e: any) {
        console.error("Error from sqlite proxy server: ", e.response.data);
        return { rows: [] };
      }
    },
    { schema: { cities, users } }  // Added the schema here....
  );

Could you please try latest version?


[xxx] Use match_array to fix flakey spec

Context
This spec shouldn't need to test ordering, only that the elements match.
Changes proposed in this pull request
Use match_array to disregard order.
Guidance to review

Some fine work here


Correlation and causation ids

Greg Young explains correlation and causation ids succinctly as:

Every message has 3 ids, MessageId, CorrelationId, CausationId.
When you are responding to a message (either a command or and event) you copy the correlationId of the message you are responding to to your message. The CausationId of your message is the MessageId of the message you are responding to.

Currently, Commanded does not set causation id, and correlation id is set as a generated UUID  when appending events. It should follow the approach outlined by Greg above.

Quick and maybe unrelated question. Do you see the correlationId as being semantically the same as a saga identifier, from Hector Garcia-Molina's paper "sagas":

The begin-saga command can return a saga identifier to the program. This identifier can then be passed to the system on subsequent calls made by the saga.

Or am I mixing up two concepts here?

@fdbeirao No, I don't think so.
In Commanded you would use a process manager to implement a saga. So I would say the identity returned from the process manager's interested?/1 function is the identity for the process manager (aka saga).
In the example below it is the transfer_uuid that uniquely identifies a single instance of the transfer money process manager:
defmodule TransferMoneyProcessManager do
  use Commanded.ProcessManagers.ProcessManager,
    name: "transfer_money_process_manager",
    router: BankRouter

  def interested?(%MoneyTransferRequested{transfer_uuid: transfer_uuid}), do: {:start, transfer_uuid}
  def interested?(%MoneyWithdrawn{transfer_uuid: transfer_uuid}), do: {:continue, transfer_uuid}
  def interested?(%MoneyDeposited{transfer_uuid: transfer_uuid}), do: {:stop, transfer_uuid}
  def interested?(_event), do: false

  # ...
end


Support for multiple futures in a view model, each triggered by a different event

Hello!
Wonderful package. Loved it!
I've a very general use-case and I'm having a hard time achieving it with this architecture.
Suppose, a screen has multiple APIs associated with it and each of them is triggered by a separate event. For instance, when a screen opens up, I need to fire one of the associated APIs; on click of a button, I need to hit another API; finally, when the screen closes, 3rd API should be called.
Is there a way to achieve this using MultipleFutureViewModel keeping busy,  hasError, onError, onData and all other perks of future view model intact for each API?

@smokelaboratory No. The FutureViewModel is specifically for a ViewModel that requires data before it can function, that's why the data returned is stored locally in the object. So that we can access it in the view.
It's not for running a general Future. That you can simply do by extending the BaseViewModel. The FutureViewModel and StreamViewModel is specifically for fetching data using a future and storing that data in the model.

Ok. Thank you for explanation. Closing the issue.
Also, as I strictly want to follow the guidelines of your architecture in my project, what is the best way to do it using  BaseViewModel, keeping all features of a FutureViewModel for each future task?

i don't exactly know what you're asking. BaseViewModel is the basic viewmodel as I've been using through all the videos. It's just a change notifier where you can call notifyListeners in with some extra functionality that's not required. It's just there to make your life easier.


Extend Grafana client

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

Project coverage is 17.74%. Comparing base (f98a8e9) to head (bcbb175).
Report is 4 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #891      +/-   ##
==========================================
- Coverage   17.74%   17.74%   -0.01%
==========================================
  Files          41       41
  Lines        4564     4576      +12
==========================================
+ Hits          810      812       +2
- Misses       3666     3674       +8
- Partials       88       90       +2

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


Handle parent context for copying url.

This PR will add support for context[parent] inside url copy component.
How to test

Switch to this branch inside IDE.
Build modules.
Go to executive page and click Copy URL button.

Expected results

If opened inside snyk website, the url matches with app.snyk.io
If opened outisde snyk website, the url matches with current url.
Also copies all filters.

Maybe i am missing something, how can I test in new chrome as well?

@sareg0 Maybe i am missing something, how can I test in new chrome as well?

You'd need the feature flags on, and Emi's PR will need to be merged first. We can set you up with the correct feature flags when his PR is merged and we can test again.

This PR needs to be updated with the new context store added in this other PR: https://github.com/snyk/topcoat-core/pull/512


Add support for rendering cursors to rusttype

This implements the alternative cursors for the rusttype backend which were missed in the initial implementation.
I was going to change the way these are generated to make it more obvious but:

I'm lazy
Font-kit should invalidate most of this work anyway

Fixes https://github.com/jwilm/alacritty/issues/1676

@chrisduerr Thanks for the tip about the changelog, I wasn't sure if it needed it one because it's a fix to an addition that hasn't been 'released' yet.
I've made those changes.

Should be good to merge this I think.


WRKLDS-649: Guard pod set readiness probe endpoint explicitly

Pulling https://github.com/openshift/library-go/pull/1457 and setting the readiness endpoint to /readyz explicitly.

/retest-required

/hold
until https://github.com/openshift/library-go/pull/1457 merges

/hold cancel

/retest-required

/retest-required

yay!  I just found this.  Very glad to see this landing.

/retest-required

/retest

/retest

e2e-gcp-operator blocked by https://github.com/openshift/cluster-kube-apiserver-operator/pull/1436


Get tests to run

mocha uses require to load detected test files. However, our test files were defined as .mjs, and node's --experimental-modules flag does not allow require-ing an .mjs file. This is true even when using esm, since the library does not want to diverge from this behavior.
The easiest fix was to rename .mjs -> .js. If you want to keep .mjs, it's possible by maintaining a test/index.js that imports all test files, then tell mocha to run test/index.js only.

Thanks!

I'll worry about .mjs at a later point in time.


do not copy default.bkr to ~/.beaker #2994

default.bkr has been renamed to notebook-default.bkr
Default notebook name has been changed in the DefaulBeakerConfig class

:+1:


Check for bin directory before cloning pyenv

Travis creates cached directories if they are not present, so the pyenv repo was never getting cloned if the cache was empty.
Related to #595 and #596
cc/ @jonparrott

Thanks, @pferate!


Thief selection might still be cooked

Description

I'm intending it to always try to select up to three thieves but I've had some rounds with zero thieves and some round with three thieves. Zero shouldn't happen because the minimum is set to one...
https://github.com/space-wizards/space-station-14/pull/30393
I'll probably work on making a command to simulate antag selection at this rate so we can figure out what the distribution is like. At this moment I'm just viewing replay round end summaries to figure out if we have more than one thief or not.
Reproduction

Screenshots

Additional context

Thief isnt guaranteed to always be picked so thats why you can have 0 thieves

guh maximum

Alright I've seen enough round-end summaries, we're GOOD.


Update China's demand

Amount of pax killed by China's high speed rail should vary based on distance. Shorter flights have less pax overall.
Also considering on making some other changes to demand.
Fly or die

not very important


Which pretrain is used in the CV task?

Thanks to your great work to accelerate the research in SSL. After reading the paper, I have not figure out which pretrained model is used in the CV task. Unsupervised pretrain or supervised pretrain on imagenet?

For STL-10, we use unsupervised pretraining on ImageNet (MAE).
And for other datasets we use supervised pretrianing.

Why not to use unsupervised pretraining for all dataset?

At the beginning we didn't get good results from unsupervised pretraining. But now we do plan to update the unsupervised pretraining results.

I understand your concern on the model size. In my opinion, the motivation of SSL is to learn from limited label. But the supervised pretraining needs a lot of label data which is conflict to the motivation of SSL. What's more, the categories of downstream task may overlap with the pretrained categories. Therefore, I believe the plan to update the unsupervised pretraining results is more useful to the SSL community.


Draft CSV Reader

run tests

run tests

Can one of the admins verify this patch?

rerun tests

rerun tests

@BradReesWork In the failed build its the test_hashing.py:95 that is failing due to an AssertionError
I have seen this a few times now no matter the Python version but its not consistent
=================================== FAILURES ===================================
_________________________________ test_hashing _________________________________

    def test_hashing():
        # Make data
        nrows = 8
        dtypes = [np.int8, np.int16, np.int32, np.int64, np.float32]#, np.float64] # dtypes as number of columns

        # pytest for hashing fails if called collectively on folder and if number of columns>5, but works well if called seperately like
        # pytest --cache-clear -vvs ~/libgdf/python/tests/test_hashing.py

        hash_input = []
        for dt in dtypes:
            hi = np.array(np.random.randint(0, 28, nrows), dtype=dt)
            hi[-1] = hi[0]
            hash_input.append(hi)

        ncols = len(hash_input)
        magic = libgdf.GDF_HASH_MURMUR3

        with _make_hash_input(hash_input, ncols) as col_input:
            # Hash
            hashed_column = _call_hash_multi(libgdf.gdf_hash, ncols, col_input, magic, nrows)

        # Check if first and last row are equal
>       assert tuple([hashed_column[0]]) == tuple([hashed_column[-1]])
E       assert (-479244108,) == (-1102096448,)
E         At index 0 diff: -479244108 != -1102096448
E         Full diff:
E         - (-479244108,)
E         + (-1102096448,)

test_hashing.py:95: AssertionError
----------------------------- Captured stdout call -----------------------------
<cdata 'void *' 0x7f306e600000>
8
0x7f306e600000
<numba.cuda.cudadrv.driver.MemoryPointer object at 0x7f309b219128>
[ -479244108 -2078410840   502904503<PHONE_NUMBER>   767157442 -1627207307
   189202023 -1102096448]
===================== 1 failed, 543 passed in 4.36 seconds =====================
CMakeFiles/pytest.dir/build.make:61: recipe for target 'pytest' failed
CMakeFiles/Makefile2:227: recipe for target 'CMakeFiles/pytest.dir/all' failed
make[3]: *** [pytest] Error 1
make[2]: *** [CMakeFiles/pytest.dir/all] Error 2
CMakeFiles/Makefile2:234: recipe for target 'CMakeFiles/pytest.dir/rule' failed
make[1]: *** [CMakeFiles/pytest.dir/rule] Error 2
Makefile:238: recipe for target 'pytest' failed
make: *** [pytest] Error 2

rerun tests

rerun tests

Closing this pull request and shifting work to the re-factored version.


docs/translations: add a notice at the end of usage.md

In my forked repository, at least aux checker does not complain.


Indicate that RESIN_APP_RELEASE was deprecated in OS v2.12.x

In the example printenv of https://www.balena.io/docs/learn/develop/runtime/ we show that this variable exists, we should remove it from there and indicate that it was removed in OS v2.12.7 and the recommended method of getting the app commit is to use the supervisor API
 Front conversations

this has already been cleaned up


Update lerna to v4.0.0

Looks like I did this later without realizing you already had it in progress . . . we don't need this anymore.

Looks like I did this later without realizing you already had it in progress . . . we don't need this anymore.

@millerds Should we close this PR then?


Create Application Insights by default when creating Function Apps

Fixes #7890
@ahmedelnably @panchagnula

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

[x] The PR has modified HISTORY.rst describing any customer-facing, functional changes. Note that this does not include changes only to help content. (see Modifying change log).

[x] I adhere to the Command Guidelines.

Few comments about error messages, overall LGTM :)

@yugangw-msft / @tjprescott this should be good to merge :)

@yugangw-msft, Updated the PR to address comments


Feature: Cadl project file variable interpolation and emitter-output-dir

fix #1252
Breaking change entry

@markcowl Could you review this one? I feel like I don't remember enough context on the design.


error starting synctrayzor

everything was working great but i dont know what this error means as the program wont start anymore.
i have the current version of synctrayzor and 1.4 of syncthing
thanks!

Can this thing be related to this?
https://github.com/canton7/SyncTrayzor/issues/517

Yes that fixed it thanks!
Get Outlook for Android

From: Woren<EMAIL_ADDRESS>Sent: Sunday, April 5, 2020 8:38:13 AM
To: canton7/SyncTrayzor<EMAIL_ADDRESS>Cc: mocavo67<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [canton7/SyncTrayzor] error starting synctrayzor (#558)
Can this thing be related to this?
#517https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fcanton7%2FSyncTrayzor%2Fissues%2F517&data=02|01||050fde2c7c2e4e11843808d7d96696db|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637216906941015826&sdata=h3JaGTLzYd4tTVJ5ABtX1mYpKmuDlajjtOn9b0BPCXQ%3D&reserved=0
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fcanton7%2FSyncTrayzor%2Fissues%2F558%23issuecomment-609418195&data=02|01||050fde2c7c2e4e11843808d7d96696db|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637216906941015826&sdata=7LW93q7Z6R7FuQYR3cKDPlM653iNVhTZKMIW3t6X6nA%3D&reserved=0, or unsubscribehttps://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAJZQQNXNCES2ABGWQSEHWULRLCCULANCNFSM4LZXZFMQ&data=02|01||050fde2c7c2e4e11843808d7d96696db|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637216906941025819&sdata=ibR9m8oHaOVgzoQnc2pchW1nQxM7c49agVc8ewDooQs%3D&reserved=0.

Thanks Woren, copying the newer .exe fixed it right up using the method in that thread #517


prototype(tabs): create prototype tabs based on MDC web

Adds an implementation of the Angular Material tabs that is based on MDC web. The API is exactly the same, except for a couple of differences:

The ink bar has been switched to use MDC's tab-indicator. As such the styling and the animation are slightly different.
Previously MatTabLink used to be a Directive, however now it's a Component, because we need some extra markup around the content.

Note: this is not merge safe, because I had to move a few things around in the current tabs module.

cc @abhiomkar FYI

@jelbourn @mmalerba all of the feedback has been addressed.

Looks like I rebased this while there were build errors in master. It should be rebased once #16928 gets in.

@crisbeto when you get a chance, could you rebase this again?

Rebased @jelbourn.


Make version list work after typing @ for library id

https://github.com/aspnet/LibraryManager/issues/135 is fixed in this one


Support LWAN web server

This commit is the first try to support LWAN web server.
The changes includes:
Add patches for lwan.
Add script to CMakelist.txt to link library.
Add lwan-preload.c wrapper for lwan.
Add send() system call to wrapper.c.
When there is only one connection from the browser,
only send() will be called.
When there are  multiple connections, send() will be called
once and then sendfile() will be called.

Thanks for PR. There is a grammar error in the commit message.
Instead "The changes includes", it should be "The changes include".

@yaohwang99 , please also updates README.


Subclassing BaseMessageCollectionViewCell

Hi, I'm trying to subclass BaseMessageCollectionViewCell as you did with TextMessageCollectionViewCell and PhotoMessageCollectionViewCell, however even if I try to copy all of the code of TextMessageCollectionViewCell and rename it to something else I get several compiler errors such as: "Initializer does not override any method from its superclass".
Actually all I need to override is canPerformAction(action: Selector, withSender sender: AnyObject?) -> Bool function and add some methods for custom edit menu actions. I tried to do this in an extension of TextMessageCollectionViewCell but apparently Swift doesn't let me override canPerformAction in an extension. Do you have any suggestions or workarounds for this problem. Or any other way to add custom items to edit menu of chat bubbles. Thanks.

Inheriting from BaseMessageCollectionViewCell is missing public access level for init(frame:) and createBubbleView() so they can't be inherited outside ChattoAdditions module as I mentioned in https://github.com/badoo/Chatto/issues/26. Can you try that locally and make a PR if it works?

Do you mean changing those methods to public? And by working do you mean if I can subclass ChattoChatViewController outside of ChattoAdditions? If your answer to both of these questions are 'yes', I would be more than happy to attempt to contribute to Chatto.

Yes, I mean changing those methods to public and verifying it solves your problem (that you can subclass the cells). ChatViewController has no problems being subclassed (it's done in ChattoApp)

Just finished the work after struggling with Xcode for hours :/ With the changes in #48 I can successfully subclass BaseMessageCollectionViewCell.

@bcamur thank you!

You are welcome, and thank you; this was my first PR and contribution to an OSS project :)


nixos/nexus: allow overriding the package

Useful when pulling nixos-unstable in a stable NixOS installation.
Motivation for this change
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[x] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Fits CONTRIBUTING.md.

ah thanks for noticing. fixed now!

@GrahamcOfBorg test nexus

No attempt on aarch64-linux (full log)
The following builds were skipped because they don't evaluate on aarch64-linux: tests.nexus
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnfree = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnfree = true; }
to ~/.config/nixpkgs/config.nix.

Success on x86_64-linux (full log)
Attempted: tests.nexus
Partial log (click to expand)
server: exit status 1
syncing
server: running command: sync
server: exit status 0
test script finished in 323.88s
cleaning up
killing server (pid 593)
vde_switch: EOF on stdin, cleaning up and exiting
vde_switch: Could not remove ctl dir '/build/vde1.ctl': Directory not empty
/nix/store/kkzglfmzp9pav6bqvrqpkj6w5nccrnk9-vm-test-run-nexus