MacUpdater error

macOS version: 12.0 (21A344)
Kap version: Version 3.4.1 (<IP_ADDRESS>1)
Current behaviour
Every now and then, the app throws this error:
Unhandled Promise Rejection
Error: Could not get code signature for running application
    at Server.<anonymous> (/Applications/Kap.app/Contents/Resources/app.asar/node_modules/electron-updater/out/MacUpdater.js:105:44)

Closing as duplicate of #1046


Fixes for guidance and question definitions.

What is the context of this PR?
Will noticed a few issues around guidance and interstitials yesterday, these included strong text in question guidance and h2s instead of h1s on interstitial pages.
I have changed all usages of title inside guidance to description. I think this makes sense and matches up with how we've used description elsewhere.
Additionally, question guidance wasn't working correctly after https://github.com/ONSdigital/eq-survey-runner/pull/2091. Question definitions were showing a double title. This should fix that issue.
How to review
Double check that the census schema works correctly, paying particular attention to any content types like guidance or interstitials.
Checklist

[ ] New static content marked up for translation
[ ] Newly defined schema content included in eq-translations repo

NISRA degree guidance is a title not description, so shows up as bold.

NISRA- school-travel-mode is also on old schema for guidance


Need an easy way to dynamically add outputs

So, I have tried to add them in VueBlocksContainer,
this.blocks.find(t => t.id === block.id).outputs.push({           active: false,           label: 'New Match',           name: 'NewMatch'         })
But, as soon as this.updateScene() runs, they are cleared.
Any tips on dynamically adding outputs?
Thanks!

So I commented out the deletes in clonedBlocks.map inside exportScene. Everything seems to work fine.
Will this cause anything problems?

Hi. Thank you for your interest in the project.
I think your solution with clonedBlocks.map is correct.
The only problem is if you change the inputs/outputs of the block(in "blocksContent" array), they will not be updated in the saved scene.
Perhaps you should write some functionality that adds missing inputs/outputs to the prepareBlocks function. Although I can see that there is a merge of objects happening there, so there is a chance the problem will be solved automatically. Unfortunately, I am not able to verify this at the moment.


Remote Cache miss during docker build

What version of Turborepo are you using?
1.2.14
What package manager are you using / does the bug impact?
Yarn v2/v3 (node_modules linker only)
What operating system are you using?
Linux
Describe the Bug
I have set up my project to use remote-caching using vercel. When running turbo commands locally I get a cache hit and can see my assets uploaded to my dashboard in vercel. I have tested that it is receiving the assets from the remote cache, by deleting my local cache rm -rf ./node_modules/.cache/turbo.
I am using alpine node-lts in my docker build. When docker runs the build commands I do not see • Remote computation caching enabled (experimental) in the console like I do when running locally. I assume that I am missing something in my docker container to get it to work. I do not see any specified things needed in the documentation of external dependencies for remote caching to work
Expected Behavior
Remote caching to work during a docker build
To Reproduce
Clone this repo
https://github.com/StevenMatchett/turbo-repo-issue
npx turbo login
npx turbo link
yarn build
docker build .
Docker will not use remote cache files

I have noticed that in linux the config parser isn't working as intended. I am fairly new to golang (installed it a few hours ago) so I am not really sure where to look, but I noticed that my .turbo/config.js file isn't being applied the same as on my macbook. Certain flags that are set for teamId and teamSlug are coming back being an empty string in docker unless I add the flag to the cli. `turbo run build --team="team-123" But I do not see a flag for teamId which if not set doesn't seem to work.
I know this isn't the right fix, but when I added this line along side in the if statement caching was working on linux.
partialConfig.TeamId = arg[len("--team="):]
https://github.com/vercel/turborepo/blob/main/cli/internal/config/config.go#L172

Fix for issue. Seems this logic is a little flawed
https://github.com/vercel/turborepo/pull/1527


ToutList?

This is probably a silly question, but what on earth does "Tout" stand for? I've realize it's an arbitrary name but I've been banging my head trying to figure out what "Tout" is short for.

https://www.google.com/?ion=1&espv=2#q=define tout

Yeah, a google search is the first thing I did but the definition still didn't make sense to me as far as why that naming convention was chosen.
I'm assuming it's based more on this context, am I correct?
synonyms: peddle, sell, hawk, offer for sale, promote
"street merchants were touting their wares"
Is a Tout-list or a Tout-block commonly used in design circles these days?
=============
tout/
verb
1.
attempt to sell (something), typically by pestering people in an aggressive or bold manner.
"Jim was touting his wares"
2.
NORTH AMERICAN
offer racing tips for a share of any resulting winnings.
noun
1.
a person soliciting custom or business, typically in an aggressive or bold manner.
2.
NORTH AMERICAN
a person who offers racing tips for a share of any resulting winnings.


Add Docstrings in the Python SDK

Proposed changes

Add docstrings in the Python SDK for all the classes and functions in the deepgram -> transcription.py file. Please add @geekchick as a reviewer on your pull request.

Context

This change is important so it can help other developers using the SDK to quickly understand what's happening in a class or function, therefore decreasing development time and helping junior developers get up and running.

hii @geekchick, i am new here. so don't know about pull request. can you help me please?

Closing this issue as Docstrings were added by @dotaadarsh .


feat(ingest/bigquery): Generate platform resource entities for BigQuery labels

Checklist

[ ] The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
[ ] Links to related issues (if applicable)
[ ] Tests for the changes have been added/updated (if applicable)
[ ] Docs related to the changes have been added/updated (if applicable). If a new feature has been added a Usage Guide has been added for the same.
[ ] For any breaking change/potential downtime/deprecation/big changes an entry has been made in Updating DataHub

The smoke test error doesn't seem to be related to this change


OCPNODE-2388: add UserNamespacesSupport to TechPreview feature gates

I think we should just carry this in https://github.com/openshift/api/pull/1939


Bug/fix upload download demo

Could you please make a fresh branch off of master and apply these changes in a single commit and PR that instead?
It feels a bit weird merging 13 commits just to change ~10 lines...


CAR-5199

added new method that returns currencies ordered by country name

This change requires us to manually update multiple lists. Can you think of a way to programmatically sort the list of currencies that are returned? We can do the sorting on the survey too.


replace copyrights headers/comments in kogito-pipelines

Closed by https://github.com/apache/incubator-kie-kogito-pipelines/pull/1123


[Q] Is there a way to merge sweeps?

Hello everyone,
I've executed two random sweeps with the same set of hyperparameters. I was wondering if it's possible to bundle their runs and analyze them all at once as a single sweep.
Thanks in advance!

Hey @artur-deluca , I think there's a couple of things you could do:

Create a Report, and add the runs from both sweeps to the run set.

or

Seed a new Sweep (docs) with the runs from both of your sweeps that you want to join.

Great! Thanks, @tyomhak


Bad Gateway, ECONNREFUSED

Checklist

Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?
Yes
Are you sure you're not using someone else's docker image?
Yes
If having problems with Lets Encrypt, have you made absolutely sure your site is accessible from outside of your network?
N/A

Describe the bug

A clear and concise description of what the bug is.
Will not connect to the database, error ECONNREFUSED and then it times out.  Tried multiple ways.  I can ping db just fine from the app console.
What version of Nginx Proxy Manager is reported on the login page?
v2.3.1

config.json
{
  "database": {
    "engine": "mysql",
    "host": "db",
    "name": "npm",
    "user": "npm",
    "password": "mypassword",
    "port": 3306
  }
}

docker-compose.yml
version: "3"
services:
  app:
    image: jc21/nginx-proxy-manager:latest
    restart: always
    ports:
      # Public HTTP Port:
      - 80:80
      # Public HTTPS Port:
      - 443:443
      # Admin Web Port:
      - 81:81
    environment:
      # Uncomment this if IPv6 is not enabled on your host
      DISABLE_IPV6: "true"
    volumes:
      # Make sure this config.json file exists as per instructions above:
      - /share/Docker/NGINXPM/config.json:/app/config/production.json
      - /share/Docker/NGINXPM/data:/data
      - /share/Docker/NGINXPM/letsencrypt:/etc/letsencrypt
    depends_on:
      - db
  db:
    image: mariadb:latest
    restart: always
    environment:
      MYSQL_ROOT_PASSWORD: "myrootpassword"
      MYSQL_DATABASE: "npm"
      MYSQL_USER: "npm"
      MYSQL_PASSWORD: "mypassword"
    volumes:
      - /share/Docker/NGINXPM/data/mysql:/var/lib/mysql

DB Logs

2020-08-01 01:13:14+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 1:10.5.4+maria~focal started.
2020-08-01 01:13:14+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
2020-08-01 01:13:14+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 1:10.5.4+maria~focal started.
2020-08-01  1:13:15 0 [Note] mysqld (mysqld 10.5.4-MariaDB-1:10.5.4+maria~focal) starting as process 1 ...
2020-08-01  1:13:15 0 [Note] InnoDB: Using Linux native AIO
2020-08-01  1:13:15 0 [Note] InnoDB: Uses event mutexes
2020-08-01  1:13:15 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2020-08-01  1:13:15 0 [Note] InnoDB: Number of pools: 1
2020-08-01  1:13:15 0 [Note] InnoDB: Using SSE4.2 crc32 instructions
2020-08-01  1:13:15 0 [Note] mysqld: O_TMPFILE is not supported on /tmp (disabling future attempts)
2020-08-01  1:13:15 0 [Note] InnoDB: Initializing buffer pool, total size = 134217728, chunk size = 134217728
2020-08-01  1:13:15 0 [Note] InnoDB: Completed initialization of buffer pool
2020-08-01  1:13:15 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2020-08-01  1:13:15 0 [Note] InnoDB: 128 rollback segments are active.
2020-08-01  1:13:15 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2020-08-01  1:13:15 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2020-08-01  1:13:15 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2020-08-01  1:13:15 0 [Note] InnoDB: 10.5.4 started; log sequence number 45093; transaction id 21
2020-08-01  1:13:15 0 [Note] Plugin 'FEEDBACK' is disabled.
2020-08-01  1:13:15 0 [Note] Server socket created on IP: '::'.
2020-08-01  1:13:15 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
2020-08-01  1:13:15 0 [Note] InnoDB: Buffer pool(s) load completed at 200801  1:13:15
2020-08-01  1:13:15 0 [Warning] 'proxies_priv' entry '@% root@ac19879d292b' ignored in --skip-name-resolve mode.
2020-08-01  1:13:15 0 [Note] Reading of all Master_info entries succeeded
2020-08-01  1:13:15 0 [Note] Added new Master_info '' to hash table
2020-08-01  1:13:15 0 [Note] mysqld: ready for connections.
Version: '10.5.4-MariaDB-1:10.5.4+maria~focal'  socket: '/run/mysqld/mysqld.sock'  port: 3306  mariadb.org binary distribution

App log

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] done.
[services.d] starting services
[services.d] done.
Generating dummy SSL certificate...
Generating a RSA private key
...............+++++
...................................................................+++++
writing new private key to '/data/nginx/dummykey.pem'

Complete
Disabling IPV6 in hosts
❯ Disabling IPV6 in hosts: /etc/nginx/conf.d
❯ /etc/nginx/conf.d/default.conf
❯ /etc/nginx/conf.d/include/assets.conf
❯ /etc/nginx/conf.d/include/block-exploits.conf
❯ /etc/nginx/conf.d/include/force-ssl.conf
❯ /etc/nginx/conf.d/include/ip_ranges.conf
❯ /etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf
❯ /etc/nginx/conf.d/include/proxy.conf
❯ /etc/nginx/conf.d/include/ssl-ciphers.conf
❯ /etc/nginx/conf.d/include/resolvers.conf
❯ /etc/nginx/conf.d/production.conf
Disabling IPV6 in hosts
❯ Disabling IPV6 in hosts: /data/nginx
[8/1/2020] [1:22:52 AM] [Global   ] › ✖  error     connect ECONNREFUSED <IP_ADDRESS>:3306
[8/1/2020] [1:22:53 AM] [Global   ] › ✖  error     connect ECONNREFUSED <IP_ADDRESS>:3306
[8/1/2020] [1:22:54 AM] [Global   ] › ✖  error     connect ECONNREFUSED <IP_ADDRESS>:3306
[8/1/2020] [1:22:55 AM] [Global   ] › ✖  error     connect ECONNREFUSED <IP_ADDRESS>:3306
[8/1/2020] [1:22:56 AM] [Global   ] › ✖  error     connect ECONNREFUSED <IP_ADDRESS>:3306
[8/1/2020] [1:22:57 AM] [Global   ] › ✖  error     connect ECONNREFUSED <IP_ADDRESS>:3306
[8/1/2020] [1:22:58 AM] [Global   ] › ✖  error     connect ECONNREFUSED <IP_ADDRESS>:3306
[8/1/2020] [1:22:59 AM] [Global   ] › ✖  error     connect ECONNREFUSED <IP_ADDRESS>:3306
[8/1/2020] [1:23:00 AM] [Global   ] › ✖  error     connect ECONNREFUSED <IP_ADDRESS>:3306
[8/1/2020] [1:23:01 AM] [Global   ] › ✖  error     connect ECONNREFUSED <IP_ADDRESS>:3306
[8/1/2020] [1:23:02 AM] [Global   ] › ✖  error     connect ECONNREFUSED <IP_ADDRESS>:3306
[8/1/2020] [1:23:03 AM] [Global   ] › ✖  error     connect ECONNREFUSED <IP_ADDRESS>:3306
[8/1/2020] [1:23:04 AM] [Global   ] › ✖  error     connect ECONNREFUSED <IP_ADDRESS>:3306
[8/1/2020] [1:23:05 AM] [Global   ] › ✖  error     connect ECONNREFUSED <IP_ADDRESS>:3306
[8/1/2020] [1:23:06 AM] [Global   ] › ✖  error     connect ECONNREFUSED <IP_ADDRESS>:3306
[8/1/2020] [1:23:07 AM] [Global   ] › ✖  error     connect ECONNREFUSED <IP_ADDRESS>:3306
[8/1/2020] [1:23:08 AM] [Global   ] › ✖  error     connect ECONNREFUSED <IP_ADDRESS>:3306
[8/1/2020] [1:23:09 AM] [Global   ] › ✖  error     connect ECONNREFUSED <IP_ADDRESS>:3306
[8/1/2020] [1:23:10 AM] [Global   ] › ✖  error     connect ECONNREFUSED <IP_ADDRESS>:3306
[8/1/2020] [1:23:11 AM] [Global   ] › ✖  error     connect ECONNREFUSED <IP_ADDRESS>:3306
[8/1/2020] [1:23:12 AM] [Global   ] › ✖  error     connect ECONNREFUSED <IP_ADDRESS>:3306
[8/1/2020] [1:23:13 AM] [Global   ] › ✖  error     connect ECONNREFUSED <IP_ADDRESS>:3306
[8/1/2020] [1:23:14 AM] [Global   ] › ✖  error     connect ECONNREFUSED <IP_ADDRESS>:3306
[8/1/2020] [1:23:15 AM] [Global   ] › ✖  error     connect ECONNREFUSED <IP_ADDRESS>:3306
[8/1/2020] [1:23:16 AM] [Global   ] › ✖  error     connect ECONNREFUSED <IP_ADDRESS>:3306
[8/1/2020] [1:23:17 AM] [Global   ] › ✖  error     connect ECONNREFUSED <IP_ADDRESS>:3306
[8/1/2020] [1:23:18 AM] [Global   ] › ✖  error     connect ECONNREFUSED <IP_ADDRESS>:3306
[8/1/2020] [1:23:19 AM] [Global   ] › ✖  error     connect ECONNREFUSED <IP_ADDRESS>:3306
[8/1/2020] [1:23:20 AM] [Global   ] › ✖  error     connect ECONNREFUSED <IP_ADDRESS>:3306
[8/1/2020] [1:23:21 AM] [Global   ] › ✖  error     connect ECONNREFUSED <IP_ADDRESS>:3306
[8/1/2020] [1:23:22 AM] [Global   ] › ✖  error     connect ECONNREFUSED <IP_ADDRESS>:3306
[8/1/2020] [1:23:33 AM] [Global   ] › ✖  error     connect ETIMEDOUT

Operating System
QNAP with latest QTS, Portainer 1.24.1
Additional context
At a loss here, tried everything.

@wschlotter
I got it working!
db_1 | 2020-09-19 12:31:16 0 [ERROR] InnoDB: The Auto-extending innodb_system data file './ibdata1' is of a different size 0 pages than specified in the .cnf file: initial 768 pages, max 0 (relevant if non-zero) pages!
All I did was delete the .ibdata1 file that shows 0kb
And then re-deploy the whole setup. Now it generates a new clean .ibdata file that is around 12Mb size

@codeagencybe
due to the fact that if have the same issue with my installation and I'm not too deep into docker, I'd like to ask how to delete the .ibdata1 file ? Can this be done when the container is up an running  ?

@Iron-Merlin-2000
If you do the Docker-compose up command, it will generate all those files in your volume the first run.
When that's done, ssh into server (or use SFTP) and go to the mount where you specified the app volume.
From there delete it and then redeploy again.
That's all I did and it works but this is not a permanent fix whatsoever.
It still requires a patch/fix so this doesn't happen on new deployments.

Hey! I'm a noob and I encounter the same problem. What do you type into your terminal to access the .ibdata1 file?

Hey! I'm a noob and I encounter the same problem. What do you type into your terminal to access the .ibdata1 file?


removing psi, pagespeed, and doc references

Addresses #893
Resolved conflicts in #894 by @fisch0920

Coverage remained the same at 98.77% when pulling e7bdb50f5240d2b4bb4e5f0dee5df87e98e71d46 on mkhazov:feature-remove-pagespeed into a0e32572ef3708ce6fdf4854a27f1a563f214db9 on mxstbr:master.

@mkhazov Plase base this off of and PR again dev branch.

Deploy preview failed.
Built with commit 5ebb79228544a32dae7072a8d2fabbbc12d34233
https://app.netlify.com/sites/react-boilerplate/deploys/585398276686742a37507b73


Security Team Budget Request v2

Scope
This budget request is for the security team comprised currently of two core contributors and one internship slots to continue contributing with security related work in the yearn ecosystem. It will keep the main plan, and scope of the previous version.
The list of updates published in the previous budget request.:

April 2023 (no included in the previous request)
May 2023
June 2023
July 2023

This request will cover one quarter (3 months) and continue the team's work on security reviews for all contracts under development in the yearn teams as capability allows. Over the following period, these budget requests should develop and provide a detail of work attempted and achieved.
This request also will detail an overview of the team's goals and objectives for the period.
Note that this budget request includes no revenue share.
Plan
Note that there are no clawbacks based on the below performance targets. But performance should impact future budget requests.
Security Reviews
The security team will continue to work on the following:

Internal security reviews for all contracts develop by yTeams and changes or updates in the current ones in production.
Internal security reviews for the Core Protocol, including v2 vaults, v3, yCRV, yETH and any other Yearn's product as required.
Management of the Risk Framework and internal security review process for v2 and v3 strategies.
Review scores and allocations frequently in the Risk Framework to ensure they are aligned regarding risk.
Coordinate with infrastructure team on support for risk framework updates, bugs and issues.
Help, guidance and coordination with auditors and external security reviewers for engagements with protocol-related contracts. (Each team needs to request their own audit security budget.)
Review and assess bounty requests through our multiple pre-established channels, such as Immunefi or any other source.

External Security Reviews & Audits Coordination
The security team will guide and coordinate all the external security reviews and audits when requested by yteams.
The process for coordinating audits and external security reviews is the following:

The yTeam that needs an audit/external security review will request coordination/help.
The security team will coordinate the slot/s with the audit firms or external reviewers.
Once and agreement with audit firm is reached, security team will create a group so yTeam and auditors can ask/answer questions. Coordination of payment and budget is managed by each yTeam.
Once the audit/review finishes, the security team will review the report and coordinate with yTeam to help review issues to ensure they are fixed or acknowledge.

Note that this process might change based on the team's needs.
Ad hoc
The security team will also continue working with existing Yearn teams (or new ones) to provide ad-hoc support. Including but not limited to offering:

War room support
Smart contract development
Product design
Protocol and Security related tooling development
Multisig coordination for emergency transactions
Security related events support e.g war room games, conferences talks, etc.

Reporting monthly in this issue.
Risk Framework on-chain
The security team plans to migrate the risk framework to an on-chain version. To do so, we already developed some smart contracts as a PoC to integrate them into the v3 vaults allowing it to set the max debt dynamically.
Although smart contracts are developed, they need unit tests, and we are coordinating efforts with the v3 team and strategists to push them forward.
Goals
The security team plans to:

Security

Help create and review Due Dilligence documents on new protocols used by yearn's strategies, when applicable.
Each security review differs in time and scope but we are estimating it based on normal strategy reviews.
Create an internal checklist with the common issues in the v3 strategies to help the strategists to improve the development.
Start/continue reviewing new strategies for v3.
Continue reviewing updates/new strategies for v2.

Risk Framework on-chain:

Completing the PoC and gathering feedback to improve the current design.
Review the current design to accept v2 and v3 strategies.
Deploying a version in an L2 chain
Selecting some v2 and v3 strategies to score and test it in the L2 chain.
Establishing a multi-sig as the owner of the contracts with the key stakeholders.
Making the repository public and transferring it to the Yearn organization.

Period
It will cover 3 months:

From: 2023-08-01
To: 2023-10-31

People

Storm0x
Rare Weasel
Tapir (intern)

Money
This budget request includes the following concepts:

2 core contributor grants.
1 internship slot.

Funds to be streamed over three months, starting 1 August 2023.
Total:
10.68 YFI
78,000.00 DAI
Any funds not spent at the end of the period will be transferred back to the yBudget team or considered for the next period.
Funds Details

Wallet address
0x4851C7C7163bdF04A22C9e12Ab77e184a5dB8F0E
Reporting
Monthly

Security Team August Updates

SEAL (Security Alliance) <> YEARN Attack Simulation

coordinate with SEAL on details and preparation for attack simulations.
tabletop exercise meeting with SEAL/ Yearn team

DDs & Security reviews

Followed up on previous security reviews.
Aave Lender v3: https://github.com/yearn/yearn-strategies/issues/533
Compound Lender v3: https://github.com/yearn/yearn-strategies/issues/534
yETH Rate Providers: https://github.com/yearn/yearn-strategies/issues/567
Maker DSR v3: https://github.com/yearn/yearn-strategies/issues/541
Maker DSR v3 router strategy: https://github.com/yearn/yearn-strategies/issues/579
stETH accumulator patch https://github.com/yearn/yearn-strategies/issues/584

V3 Security

Discussed the v3 review process with strategies and v3 teams.

https://hackmd.io/@D4Z1faeARKedWmEygMxDBA/H1SBqVdi

Reviewed v3 code to implement generic invariant/integration tests for v3 strategies.
Propose withdrawal healthcheck draft spec (https://hackmd.io/CLNtri9fSHimM9ClkbUi-g)

After discussion of spec Schlag added healthcheck hooks to withdraw https://github.com/yearn/tokenized-strategy-periphery/blob/14076aa2ccc8000cb78ee26a2c0952ad64ad8034/src/HealthCheck/BaseHealthCheck.sol#L172-L239

Created an internal repository to execute multiple analyzer/fuzzer tools in the v3 strategies (and also invariant tests soon).
Improved the V3 Gotchas doc: https://hackmd.io/r1Jcic8kRwG4dsvHw-N0cA

Risk Framework

Checked/fixed missing risk scores reported in Sync Yearn Farm website.
Planning phase for on-chain risk framework

4 Bounty Reports

Triage spam bounties from immunefi
Coordinated small bounty for Permit method lack of chain id in woofy token and ammended disclosure to remove from scope https://github.com/yearn/yearn-security/pull/79

Budget request approval for the next 3 months: https://github.com/yearn/budget/issues/145

Security Team September Updates

SEAL (Security Alliance) <> YEARN Attack Simulation

Coordinated the last details for the simulation attack.
Attended the simulation attack war room.

DDs & Security reviews

Followed up on previous security reviews.
Pearl DD: https://github.com/yearn/yearn-strategies/pull/588
3 Polygon separate V3 LST Strategies (polygon-stETH, polygon-stMATIC, mainnet-stETH): https://github.com/yearn/yearn-strategies/issues/570
Convex Frax Factory Template: https://github.com/yearn/yearn-strategies/issues/561
stETH accumulator upgrade: https://github.com/yearn/yearn-strategies/issues/584
yBAL zap update https://github.com/yearn/yearn-strategies/issues/568
Ongoing review of v3 Maker DSR and Router strategy https://github.com/yearn/yearn-strategies/issues/579
Quick review on minor PR for veYFI gauges https://github.com/yearn/veYFI/pull/228/files

V3 Security & Template

Discussed the v3 review process with strategies and v3 teams.

https://hackmd.io/@D4Z1faeARKedWmEygMxDBA/H1SBqVdi

Reviewed v3 code to implement generic invariant/integration tests for v3 strategies.
v3 Template: add summary table: https://github.com/yearn/yearn-strategies/pull/591
v3 Template: Add Risk score section: https://github.com/yearn/yearn-strategies/pull/592

Immunefi Bounty Reports

Triage spam bounties from immunefi.
Triage low bounty report in V3 code.
Added yETH production contracts to bounty page

Risk Framework

Off-chain

VelodromeV2 Factory Has Incorrect TVL (Op Network): https://github.com/yearn/ydaemon/issues/323
Create New "Generic Lev Aave v3" Group (v3 Polygon): https://github.com/yearn/ydaemon/issues/324
Missing Strategy in the "Curve Boosted Factory" (Ethereum) Group: https://github.com/yearn/ydaemon/issues/325
Group "Convex Factory" (Ethereum) Is Not Display in Risk Framework: https://github.com/yearn/ydaemon/issues/326

On-chain

Created the multi-chain multisigs for the ySecurity team and risk framework onchain.
Added more unit tests using Foundry, covering edge cases.
Added Integration tests (using forks).
Deployed in Base (testnet) and Polygon (testnet).
Added new unit tests to the RiskFramework contract.
Made small changes to improve the design.

CLI

Released First alpha version of CLI in python for risk fmk with heatmap command to display the risk framework map
https://github.com/storming0x/py-risk

Others

Fixed issue and re-deployed subgraph on Base network

https://thegraph.com/studio/subgraph/yearn-vaults-v2-subgraph-base

NOTE: some of the links for internal gh repos are access restricted for security purposes.

Security Team October Updates (still WIP)

DDs & Security reviews

Tangible: https://github.com/yearn/yearn-strategies/issues/573
DYFI PR: https://github.com/yearn/veYFI/pull/230
v3 Router https://github.com/yearn/yearn-strategies/issues/579
Aave V3 Lender: small changes due to new dependency tokenized-strategy release (v3.0.1)

V3 Security & Template

Add Experts & Test Coverage Sections: https://github.com/yearn/yearn-strategies/pull/597

Immunefi Bounty Reports

Triage spam bounties from immunefi.

Risk Framework

On-chain

Improved smart contracts design to support multi networks.
Tested with v2 and v3 strategies.
Deployed Risk Framework on-chain contracts on Polygon.
Developed subgraph for the risk framework contracts.
Made both Github repositories public and transferred to the Yearn organization.

Risk Framework: https://github.com/yearn/risk-framework
Risk Framework Subgraph: https://github.com/yearn/risk-framework-subgraph
Subgraph: https://thegraph.com/hosted-service/subgraph/yearn/yearn-risk-framework

CLI

Support heatmap graph
Support risk group data commands

Others

Multi-chain Factories: Created subgraph to query new vaults created dynamically (wip).
Prepared Security Team Budget Request v3.
Prepared Security Team Updates Presentation.

NOTE: some of the links for internal gh repos are access restricted for security purposes.


docs: fix data management section not appearing in documentation

Since the path data/ exists in .gitignore, DocArray push/pull section does not appear in the documentation because it belongs to a folder named data and CD ignores it when deploying new docs.
This PR fixes the issue by renaming the folder.

Codecov Report
Base: 85.20% // Head: 23.61% // Decreases project coverage by -61.59% :warning:

Coverage data is based on head (cd70041) compared to base (b18f5da).
Patch has no changes to coverable lines.

Additional details and impacted files
@@             Coverage Diff             @@
##             main     #967       +/-   ##
===========================================
- Coverage   85.20%   23.61%   -61.60%
===========================================
  Files         155      155
  Lines        8050     8050
===========================================
- Hits         6859     1901     -4958
- Misses       1191     6149     +4958

Flag
Coverage Δ

docarray
23.61% <ø> (-61.60%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

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

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


Kuery-ORM (0.1.1) seems to be adding a character to some table names

I have an existing table called availability on PostgreSQL
CREATE TABLE public.availability
(
  id bigint NOT NULL DEFAULT nextval('availability_id_seq'::regclass),
  starting timestamp with time zone,
  ending timestamp with time zone,
  overtime boolean,
  on_shift boolean,
  CONSTRAINT pk_availability PRIMARY KEY (id)
)
WITH (
  OIDS=FALSE
);
ALTER TABLE public.availability
  OWNER TO postgres;

Here's my model
struct Availability : Codable {

    var id: Int
    var starting: Date
    var ending: Date
    var onShift: Bool
    var overtime: Bool
}

extension Availability : Model {}

This is the error message from the database server
ERROR:  relation "availabilitys" does not exist at character 15
STATEMENT:  SELECT * FROM Availabilitys

Oddly, it does not do this with all entity names.  It would be great if one could specify table and column names, JPA style: let tableName = "whatever_name" is completely ignored.

Hey @fwgreen , I have realised that for the custom column names you can just use CodingKeys, like so:
extension Availability: Model {
    enum ColumnKeys: String, CodingKey {
      case id, starting, ending, overtime
      case onShift = "on_shift"
   }
}

@EnriqueL8 This is a potentially elegant solution, that at the moment doesn't work:  I only have one table without a snake-cased column name and it's the only one that Kuery-ORM can retrieve.  Everything else triggers an empty 500 error which isn't caught by the logger, but instead is only seen in my REST client.
PS: While tableName got rid of the original SQL error on the database server, there is still the underlying issue of the magical "s" being appended to some names.

Hey @fwgreen, the magical "s" is appended by default to the table names.
For the column names, I made a mistake instead of ColumnKeys is had to be CodingKeys
Like so,

Thanks for putting me on the right path!

Hello, i am quite new user to this project however, i believe an s behind every table just randomly need to be fixed, as this is a bug in the code. Right ?
Clearly its fine that struct name = table name but not struct name = table name + s . Especially working with existing tables like me this gives a whole lot of a mess.
The here presented solution is simply a work around on an issue that still seems to exist.
My example: I try to read out from a table: wp_amelia_providers_to_daysoff ... and i can simply not do it. unless i probably apply the work around which i will now try to do.
But i would still looking forward that the magical s bug is fixed.
By the way i am using now:
Swift Kuery: 3.0.1
Swift ORM: 0.6.0
SwiftKueryMySQL 2.0.2

@Beautylivery The problem is this is a deliberate design choice and not a bug.  The architects have assumed that all users are English speakers and all English nouns are pluralized by adding an "S".  Feel free to open a new issue.


Feature Request - Resizing and moving CefSharp browser

This feature will be useful because CefSharp fills the entire window with browser, which is very inconvenient.
I want it to look like this:

If you are using WinForms then the default is
Dock = DockStyle.Fill

You can change this to suite your own requirements.


ARROW-14096: [C++] add(time, duration) -> time kernel

This is to resolve ARROW-14096.

Needs rebasing now.

Sorry just rebased it.

Should be fine either way :).


Schema permissions can only be inserted/updated with mutual agreement between provider and delegator.

Schema permissions can only be inserted/updated (upsert) with mutual agreement between provider and delegator.  Granting, revoking/removing of schemas will be removed.
For example, a user signs up with a provider.  At a later time, provider deploys a new feature.  The user is prompted whether they want to use this new feature.  When they agree, the schema permissions are upserted to reflect it.
Acceptance Criteria

Permissions should not be able to be added without permission of both the delegator and the provider.
Permissions changes are not required to be additive only
Provider should resubmit to grant_delegation the new delegation (aka upsert) to replace the prior delegation
grant_schema_permissions should be removed (security issue)

grant_schema_permissions() should be deprecated (rather than simply removed), correct?

"The issue (with grant_schema_permissions()) is that it doesn't require signatures from both the delegator and the provider. So the delegator can force the provider into a relationship that it did not agree to." @wilwade

Here's my super-high-level user story:
Because sometimes I change my mind about what messages a Provider may post on my behalf, I want to be able to re-authorize a schema grant for a Provider that was previously revoked, so they can resume posting them from a specific point in time.
comments after discussion with @rlaferla  about how this would work:
(@p5150j your input?)
From the Provider standpoint:
So that I can provide premium services (in the form of types of messages I will submit) to certain users, I would like to be able to add/remove schema grants as needed for a given user, who may upgrade or downgrade their account services.
From ethical considerations standpoint:
If I as a user can never re-authorize a Provider to post messages on my behalf, this dramatically increases switching cost, because I will have to think really hard about de-authorizing a Provider.  This makes it much less likely for me to de-authorize and therefore it coercively reduces my freedom to choose Providers.
I think that these are important stories to try to fulfill and it makes me ask what fulfilling that looks like on chain.

This scenario should work, perhaps we need a test for it:

User A delegates to Provider X with Schema Ids 1, 2, and 3
User A revokes all delegation to Provider X at Block Number 100
User A delegates to Provider X again with Schema Ids 2, 3, and 4

Final State:

User A has a Delegation with Provider X
Schema 2, 3, and 4 are granted
Schema 1 is marked as revoked at Block Number 100

Acceptance Criteria Missed: grant_schema_permissions was not removed.


Block validator

Enhance block validator design, add block validation of completeness and signature. Enhance test framework to support this additional validation.
Add BlockValidator test for various fork conditions to resolve.
Clean up callback interface between BlockValidator and ChainController

The "fixes" and "clean up" commits should be squashed into the corresponding commits.


fix user_search() with non ascii name

to have the possibility to use non ascii char with user_search(q=name),
with for example : name = "Ксения Собчак”.
The error was : UnicodeDecodeError: 'ascii' codec can't decode byte 0xd0 in position 94: ordinal not in range(128)

Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. In order for us to review and merge your code, please sign up at https://code.facebook.com/cla - and if you have received this in error or have any questions, please drop us a line at<EMAIL_ADDRESS>Thanks!

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Facebook open source project. Thanks!


[Bug] [devops] The status is abnormal after the task is manually stopped.

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened
点击智能停止后，任务会处于一段时间reconnect状态，然后最后是unknown状态

What you expected to happen
正常状态应该为已停止
How to reproduce
点击智能停止后，任务会处于一段时间reconnect状态，然后最后是unknown状态

Anything else
No response
Version
1.0.0
Are you willing to submit PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Please provide the  dinky version and cluster execution mode

For the job status of perjob, the final result will be obtained through Yarn. The current unknow status is not as expected, which may be a bug.

dinky version:1.0.0-rc3
execution mode:yarn application

this is normal


Fix manylinux2010 compliance of GPU wheels.

Use GCC_HOST_COMPILER_PATH to point to the devtoolset compiler.
Use auditwheel to verify manylinux2010 compliance.
Fixes #3881
Fixes #4677

Thanks!


Fix undefined name in Sample 56, Node

Fixes #1943
- const reply = MessageFactory.text(`<b>${ file.Name }</b> received and saved.`);
+ const reply = MessageFactory.text(`<b>${ file.name }</b> received and saved.`);

Testing
Before:

After:

nice catch 😄 thanks!


v1.19, Google Pixel 4a (Android 12), Linux Mint Uma -> Segmentation fault

I'm trying version 1.19 using the Dockerfile here:
https://github.com/dbolser/scrcpy-docker/blob/feature/scrcpy-v1.19/Dockerfile
Used as described here:
https://github.com/pierlon/scrcpy-docker
However, I'm getting the following error:
docker run --rm -i -t --privileged -v /dev/bus/usb:/dev/bus/usb -v /tmp/.X11-unix:/tmp/.X11-unix -e DISPLAY=$DISPLAY scrcpy:intel
/ # adb devices -l
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
0A171JEC219692         unauthorized usb:1-4 transport_id:1

/ # adb devices -l
List of devices attached
0A171JEC219692         device usb:1-4 product:sunfish model:Pixel_4a device:sunfish transport_id:1

/ # scrcpy
INFO: scrcpy 1.19 <https://github.com/Genymobile/scrcpy>
/usr/local/share/scrcpy/scrcpy-server: 1 file pushed, 0 skipped. 215.9 MB/s (37330 bytes in 0.000s)
[server] INFO: Device: Google Pixel 4a (Android 12)
INFO: Renderer: opengl
INFO: OpenGL version: 4.6 (Compatibility Profile) Mesa 21.2.5 (git-53b2b224dc)
INFO: Trilinear filtering enabled
INFO: Initial texture: 1080x2336
Segmentation fault (core dumped)
/ #

The correct screen of my phone appears for a second before the core dump

Replace here:
RUN cd scrcpy && meson x --buildtype release --strip -Db_lto=true -Dprebuilt_server=/scrcpy-server

by
RUN cd scrcpy && meson x --buildtype debug -Db_sanitize=address -Dprebuilt_server=/scrcpy-server

You'll get a stacktrace on segfault. That will help.

Refs #1896.

Thanks for putting this right in the Dockerfile for me. I found I had to remove -Db_sanitize=address under as I couldn't find a way to install libsanitize-devel under alpine.

Ah, found it (with help from this, https://sigquit.wordpress.com/2009/03/13/the-core-pattern/). Attached.
core.scrcpy.25.10dba39b4976.1636717692.gz

Try to open gdb to print a backtrace:
export SCRCPY_SERVER_PATH=x/server/scrcpy-server
gdb x/app/scrcpy -c core.scrcpy.25.10dba39b4976.1636717692 -ex bt

(with the gunziped version of your core dump)

Sorry, I'm not super 1337 at this stuff...
Within the Docker container:
/ # apk add gdb
export SCRCPY_SERVER_PATH=/usr/local/share/scrcpy/scrcpy-server
/ # ls -l $SCRCPY_SERVER_PATH
-rw-r--r--    1 root root 37330 Nov 12 11:15 /usr/local/share/scrcpy/scrcpy-server
/ # gdb /usr/local/bin/scrcpy -c core.scrcpy.48.7a0f6ab02408.1636972511 -ex bt
Error relocating /usr/bin/gdb: qsort_r: symbol not found

Ahh... I think I solved it with 'apk update; apk upgrade`.
/ # gdb /usr/local/bin/scrcpy -c /tmp/core.scrcpy.142.7a0f6ab02408.1636973739 -ex bt
GNU gdb (GDB) 11.1
Copyright (C) 2021 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-alpine-linux-musl".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/local/bin/scrcpy...

warning: Can't open file /i915 (deleted) during file-backed mapping note processing

warning: Can't open file /memfd:xshmfence (deleted) during file-backed mapping note processing
[New LWP 142]
[New LWP 155]
[New LWP 148]
[New LWP 146]
[New LWP 153]
[New LWP 152]
[New LWP 156]
Core was generated by `scrcpy'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x0000000000000000 in ?? ()
--Type <RET> for more, q to quit, c to continue without paging--c
[Current thread is 1 (LWP 142)]
#0  0x0000000000000000 in ?? ()
#1  0x00007fdbcf0080f9 in ?? () from /usr/lib/libSDL2-2.0.so.0
#2  0x00007fdbcf00776f in ?? () from /usr/lib/libSDL2-2.0.so.0
#3  0x00007fdbcefd8865 in ?? () from /usr/lib/libSDL2-2.0.so.0
#4  0x00007fdbcef7cfc3 in ?? () from /usr/lib/libSDL2-2.0.so.0
#5  0x00007fdbcef7abc3 in ?? () from /usr/lib/libSDL2-2.0.so.0
#6  0x00007fdbceffc68f in ?? () from /usr/lib/libSDL2-2.0.so.0
#7  0x00007fdbceffcdad in ?? () from /usr/lib/libSDL2-2.0.so.0
#8  0x00007fdbceffdf0f in ?? () from /usr/lib/libSDL2-2.0.so.0
#9  0x00007fdbcef78d6d in ?? () from /usr/lib/libSDL2-2.0.so.0
#10 0x00007fdbcef78e57 in ?? () from /usr/lib/libSDL2-2.0.so.0
#11 0x000055a13f64ba32 in event_loop (s=0x55a13f6e0280 <scrcpy>, options=0x7ffd97180570) at ../app/src/scrcpy.c:180
#12 0x000055a13f64c306 in scrcpy (options=0x7ffd97180570) at ../app/src/scrcpy.c:417
#13 0x000055a13f642e09 in main (argc=1, argv=0x7ffd97180688) at ../app/src/main.c:92

Does that give you what you need?
Thank you!

1 0x000055a13f64ba32 in event_loop (s=0x55a13f6e0280 , options=0x7ffd97180570) at ../app/src/scrcpy.c:180

On v1.19, it is the call to SDL_WaitEvent(): https://github.com/Genymobile/scrcpy/blob/228e2c15f44849032e9006dce1e0c47ae6e108ee/app/src/scrcpy.c#L180
But then you don't have the SDL symbols down the backtrace. Probably an SDL bug (related to a permission issue or something?)

So I should compile and link a debugging version of SDL?
Else is there a known good SDL version?
Thank you so much for your help so far :-) I'm not sure how best to carry
this forward.
On Mon, 15 Nov 2021 at 11:07, Romain Vimont @.***>
wrote:

1 0x000055a13f64ba32 in event_loop (s=0x55a13f6e0280 ,
options=0x7ffd97180570) at ../app/src/scrcpy.c:180
On v1.19, it is the call to SDL_WaitEvent():
https://github.com/Genymobile/scrcpy/blob/228e2c15f44849032e9006dce1e0c47ae6e108ee/app/src/scrcpy.c#L180
But then you don't have the SDL symbols down the backtrace. Probably an
SDL bug (related to a permission issue or something?)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Genymobile/scrcpy/issues/2763#issuecomment-968785951,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAA7NE3HZNNFKE5KZMAB7LDUMDSVXANCNFSM5H2JCQPQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

I wondered if the permission issue you mentioned may be to do with Ctrl-c/Ctrl-v etc. so I tried scrcpy -n, however that failed in the exact same way. BUT, trying scrcpy -N -r blah.mkv 'worked' correctly. Of course I couldn't see my screen, but I could copy the recording and it was an accurate recording (up to Ctrl-c in the terminal).
Perhaps this is just an docker / X permission issue?
I didn't think this was the case because I do see the correct screen appear for an instant at startup. I would simply expect an X error on the command line if it were an X permission thing...
Anyway, suggestions welcome!

Host:
Graphics:
  Device-1: Intel UHD Graphics 620 driver: i915 v: kernel
  Display: x11 server: X.Org 1.20.11 driver: modesetting
  unloaded: fbdev,vesa resolution: 1680x1050~60Hz, 1920x1080~60Hz
  OpenGL: renderer: Mesa Intel UHD Graphics 620 (WHL GT2) v: 4.6 Mesa 21.0.3

I have the same problem on a Pixel 4a Android 12
on Pixel 3a with Android 11  scrcpy 1.16 still work.
2021-11-24 14:51:27.773 scrcpy[31103:3990848] INFO: scrcpy 1.16 <https://github.com/Genymobile/scrcpy> /usr/local/Cellar/scrcpy/1.16/share/scrcpy/scrcpy-serv...e pushed, 0 skipped. 34.6 MB/s (33622 bytes in 0.001s) [server] INFO: Device: Google Pixel 4a (5G) (Android 12) 2021-11-24 14:51:28.021 scrcpy[31103:3990848] INFO: Renderer: metal 2021-11-24 14:51:28.024 scrcpy[31103:3990848] INFO: Initial texture: 1080x2336 [server] ERROR: Exception on thread Thread[main,5,main] java.lang.AssertionError: java.lang.reflect.InvocationTargetException 	at com.genymobile.scrcpy.wrappers.SurfaceControl.setDisplaySurface(SurfaceControl.java:75) 	at com.genymobile.scrcpy.ScreenEncoder.setDisplaySurface(ScreenEncoder.java:216) 	at com.genymobile.scrcpy.ScreenEncoder.internalStreamScreen(ScreenEncoder.java:86) 	at com.genymobile.scrcpy.ScreenEncoder.streamScreen(ScreenEncoder.java:55) 	at com.genymobile.scrcpy.Server.scrcpy(Server.java:76) 	at com.genymobile.scrcpy.Server.main(Server.java:225) 	at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method) 	at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:355) Caused by: java.lang.reflect.InvocationTargetException 	at java.lang.reflect.Method.invoke(Native Method) 	at com.genymobile.scrcpy.wrappers.SurfaceControl.setDisplaySurface(SurfaceControl.java:73) 	... 7 more Caused by: java.lang.IllegalArgumentException: displayToken must not be null 	at android.view.SurfaceControl$Transaction.setDisplaySurface(SurfaceControl.java:3145) 	at android.view.SurfaceControl.setDisplaySurface(SurfaceControl.java:2214) 	... 9 more

I have the same problem on a Pixel 4a Android 12

No, this is not the same problem at all. Your error is #2129.
You must use a version of scrcpy >= 1.18 for Android 12.

Hello @rom1v
Thanks for the Android 12 support.
I'm currently using scrcpy 1.16 .
Do we any specific command for upgrade to scrcpy 1.18?

https://github.com/Genymobile/scrcpy/blob/master/BUILD.md#simple

I wondered if the permission issue you mentioned may be to do with Ctrl-c/Ctrl-v etc. so I tried scrcpy -n, however that failed in the exact same way. BUT, trying scrcpy -N -r blah.mkv 'worked' correctly. Of course I couldn't see my screen, but I could copy the recording and it was an accurate recording (up to Ctrl-c in the terminal).
Perhaps this is just an docker / X permission issue?
I didn't think this was the case because I do see the correct screen appear for an instant at startup. I would simply expect an X error on the command line if it were an X permission thing...
Anyway, suggestions welcome!

I have the same issue but could not find a way to fix it.
Did you find something ?


Undefined symbol: type metadata for CapacitorCommunitySqlite.JsonView

Describe the bug
After upgrading to version 3.2.2 from 3.2.0, I am getting the following error while building the IOS app in Xcode
Undefined symbols for architecture arm64:
  "type metadata for CapacitorCommunitySqlite.JsonView", referenced from:
      CapacitorCommunitySqlite.Database.importFromJson(jsonSQLite: CapacitorCommunitySqlite.JsonSQLite) throws -> [Swift.String : Swift.Int] in Database.o
ld: symbol(s) not found for architecture arm64
clang: error: linker command failed with exit code 1 (use -v to see invocation)

OS: [IOS]

EDIT
I am on Capacitor 3.2.3 and plugin version 3.2.0 does not have this error.

@t4tapas thanks for using the plug-in after updating to 3.2.2 did you remove the iOS folder from your app and after npm run build do npx cap add ios and after npx cap copy. Tell me if after having done this you still have the error. Which framework are you using?

@jepiqueau , I am using Ionic 5 with Angular. I will do the removing the iOS folder test and let you know.

@t4tapas Any news, i updated https://github.com/jepiqueau/angular-sqlite-app-starter to<EMAIL_ADDRESS>as well as @capacitor/android, @capacitor/ios and<EMAIL_ADDRESS>and i do not have any building issues.

@t4tapas Any progress on your side. if no news from you i will close the issue

@t4tapas Not having news from you, i assume it is solved so i close the issue. Feel free to re-opens it in case


Sandboxing when used in browser

As vm2 module is not available for browsers, and Node VM module is way too slow in browsers, I was wondering if Web Workers could be a solution to isolate the docx generation process ?
As webworkers provide access to Ajax and File APIs, it may proves a good alternative.
I am currently calling createReport() inside a dedicated worker, by feeding it a File object and a JSON object as input data. Everything works smooth, and I don't have access to window/localStorage/cookies from within the template.
Do you have any ideas or remarks regarding the use of webworker as a kind of security sandbox ?

I'm no security expert, sorry… But your approach certainly looks interesting.

v3.0.0 might help you in this. The new hook for running JS may allow you to implement such a solution.

@guigrpa hi, I have tried using the library within a web worker but it complains that document is not present (of course it's present only in the main app context). Are there any polyfills to have this library work in a web worker? I would like to avoid an annoying 3 seconds screen freeze when a document is generated. Thanks!

@GiordanoArman I used to have it work in webworker. It was 2 years ago but it worked. I don't recall having to use dedicated polyfills.

Same as for Deno see https://github.com/guigrpa/docx-templates#deno-usage

@vdechef @mathe42 ok, then I will try to disable the sandbox when using within a web worker, thanks!

maybe it could be helpful for other developers to mention explicitly in the docs that the sandbox needs to be disabled in order to use the library within a web worker?


Add option to create Flutures without type checking.

I think it would be nice if you could opt-out of runtime type checking and create a dev and prod version of this type. Similar to that in sanctuary-js

The sole reason Sanctuary has an opt-out from type-checking is because type-checking in Sanctuary is incredibly advanced, yet very taxing on performance (to the point where programs running with type-checking run about ten times as slow as without).
In Fluture's case, type-checking costs next-to-no performance (at the cost of some pretty repetitive code). I wouldn't be surprised if adding the option to disable it would actually end up costing performance, besides making the API less pleasant.
Are there any non performance-related reasons you would want to disable type-checking?

It was mostly for performance reasons but I haven't done any benchmarking with a non type-checking version of Flutures. I thought that with long Future chains you could probably get some improvement in performance if you weren't type-checking but perhaps, as you say, it's pretty negligible.
I'm also a little weary of doing so much type checking in libs as I feel like it's up to the developers/users of the lib to either add their own unit tests, linting, preventative measures, etc... It would also make the source code of the lib cleaner and easier to read.

My view is that the faster a program is able to fail, the better. The cases where I'm throwing a TypeError would otherwise have eventually lead to a much more cryptic error somewhere down the track (like m._f is not a function, or cannot read property _f of undefined). These errors would originate from within the library, and would've been difficult to prevent with plain JavaScript.
The reason that type-checking in Fluture is so cheap, is because I used some techniques for optimizing them:

The type-checks live in their own functions, which are expected to be called with similar types every time. This allows v8 to optimize these functions.
The actual throw statement lives yet one level deeper, allowing chrome to in-line the checks. The functions with the throw statements cannot be in-lined, but the code never reaches that path (unless it is already failing).
All of the weight of creating the error message, casting values to string, concatenating the messages, etc. is moved to behind the initial type-check, so is not executed unless we're already failing.
The type-checks themselves are usually just one or two simple if-statements.

So we end up with one or two in-lined if-statements, optimized where possible, per method. Of course, a version of Fluture without them would perform somewhat better, but a version of Fluture where all of that lives behind an additional if(typechecking === true)-check would certainly perform slower.
My original goal for Fluture was to create a stand-alone, type-checked version of Ramda Fantasy Future, because in working with Futures, I realized debugging the cryptic error messages was one of the biggest slowing-down factors. In adding type-checks to the library, I knew people would raise questions about performance, so I made sure to optimize, and as it stands, I believe Fluture is still the best performing Future library out there, despite its type-checking. So releasing a version of Fluture where the type-checks are removed is more than out-of-scope for me.

@Avaq Thanks for the detailed response! I agree that the faster a program can fail the better and I'm definitely going to employ some of those optimization techniques in my lib if I decide to do some type checking. I really don't have strong feelings about removing the type-checking in this lib and the issue I raised was more of a suggestion/question. At some point I may experiment with a technique similar to what debug uses as a method for type checking in dev mode but feel free to close this issue.


Docs overhaul

This change is

Probably best to browse here: https://github.com/shakacode/react_on_rails/tree/docs-overhaul
The diffs won't really make sense until we stabilize on overall file organization.
@jbhatab, @robwise we can work together on this PR.

Coverage remained the same at 87.411% when pulling db8d3edb89fe23c726e7a11242d117858ed4bc96 on docs-overhaul into 5929b3aeac7da3d3499308ecd8d8eb7defaf182b on master.

Coverage remained the same at 85.325% when pulling 37e54375b68a4b2ae6450e73e11bf27e41e85ae4 on docs-overhaul into bf834bc12864c677f6d9bf6ee555573c624e6774 on master.

@jbhatab @robwise @thewoolleyman Let me know if this one is ready to go.

Coverage remained the same at 85.325% when pulling de2384c21dc17c5e5cbf1e910f183fba76badb6c on docs-overhaul into 549f2d1f54e4494a8fcde1dbb1faa183e4eedb7c on master.

@justin808 ready to merge!!

Coverage remained the same at 85.325% when pulling 3f944438f42bbdc412034bed3e554a12f75f142a on docs-overhaul into 549f2d1f54e4494a8fcde1dbb1faa183e4eedb7c on master.

Coverage remained the same at 85.325% when pulling 3f944438f42bbdc412034bed3e554a12f75f142a on docs-overhaul into 549f2d1f54e4494a8fcde1dbb1faa183e4eedb7c on master.

Changes Unknown when pulling 7c3596b2f37164c74c76859c2745520af1b1eca1 on docs-overhaul into ** on master**.


Fixes for patches

patches/entities-arrow

{
	"op": "move",
	"frompath": "/client/shapeByType/*",
	"path": "/hax",
	"file": "game:entities/arrow.json"
},
{
	"op": "move",
	"frompath": "/hax",
	"path": "/client/shapeByType/*",
	"file": "game:entities/arrow.json"
},

  {
    "op": "move",
    "frompath": "/client/texturesByType/*",
		"path": "/hax",
    "file": "game:entities/arrow.json"
  },
  {
    "op": "move",
    "frompath": "/hax",
		"path": "/client/texturesByType/*",
    "file": "game:entities/arrow.json"
  }

patches/entities-spear

  {
    "op": "move",
    "frompath": "/client/shapeByType/*",
		"path": "/hax",
    "file": "game:entities/spear.json"
  },
  {
    "op": "move",
    "frompath": "/hax",
		"path": "/client/shapeByType/*",
    "file": "game:entities/spear.json"
  },

To make it clearer: Your patching way is destructive for other mods, I replaced remove patches with move ones, so instead removing wildcard it just moves it

Oh, the move op works now? That's great news, I remember having crash issues with it in 1.13 or so and sharing with Tyron, but I must have missed that it got fixed. That's definitely the method I want to use, thank you for letting me know!
I'll be releasing 2.2.4 soon to incorporate this and other 1.16 related issues :)


text/template {{call}} doesn't pass parameters to struct methods

Go version: go version go1.4.2 darwin/amd64
OS: OS X Yosemite Version 10.10.1
When using {{call ...}} in a template with a struct method the template parser fails to send any arguments to the method. This does work correctly if the method returns a function, or if the function you want to call is set to an attribute.
If this isn't intended to work, the error message could be a little clearer.
This can be replicated on the Go Playground here: https://play.golang.org/p/Ka8bN3_V1f and the source from the link is below.
package main

import (
	"os"
	"text/template"
)

type TestStructA struct {
	Test func(string) string
}

func test(s string) string {
	return "Test A Says " + s + "\n"
}

type TestStructB struct {
}

func (self TestStructB) Test() func(string) string {
	return func(s string) string { return "Test B Says " + s + "\n" }
}

// DOES NOT WORK
type TestStructC struct {
}

func (self TestStructC) Test(s string) string {
	return "Test C Says " + s + "\n"
}

func main() {
	tempStr := "{{call .Test \"hi\"}}"
	t := template.Must(template.New("test_temp").Parse(tempStr))

	testA := TestStructA{Test: test}
	err := t.Execute(os.Stdout, testA)
	if err != nil {
		panic(err)
	}

	testB := TestStructB{}
	err = t.Execute(os.Stdout, testB)
	if err != nil {
		panic(err)
	}

	// DOES NOT WORK
	testC := TestStructC{}
	err = t.Execute(os.Stdout, testC)
	if err != nil {
		panic(err)
	}
}

I admit the error message is poor but it is working as intended. You can't call something that doesn't have type func. If you look at case C, you'll see that it's missing one layer of "func" relative to cases A and B. Or, to put it another way, the evaluation of call's first argument must yield something of type 'func'. What it finds is a method, so it calls the method (without the tail of the action, which will become arguments to th function once it's evaluated). In cases A and B evaluating (calling) .Text yields another function, which call will invoke. But in case C, evaluating .Test fails because it a method of type func(string)string and there is no argument available. (Compare to {{call (.Test "hi") ''bye"}}.)
I believe you are just misunderstanding the call operation. The template you want for case C is just "{{.Test "hi"}}". The template you have is correct for cases A and B because the first argument to call evaluates (in the sense of calling the corresponding method) to a function whose type is func(string)string.

Thanks for the info. Completely missed that part of the docs, and it makes complete sense after understanding how it works. :smile:


Support ~ as the version operator.

Currently solidity-parser-antlr is unable to parse pragma solidity ~0.4.10, because ~ isn't listed as a version operator in this repo.
Please check out, that tilda-ranges are as valid as carret-ranges https://docs.npmjs.com/misc/semver#tilde-ranges-123-12-1

Thank you for reporting this @LogvinovLeon! I have a fix in b3f64a5e and will release a new JS parser shortly.

Also - what's the current situation with this grammar/parser vs solidity-parser? Looks like you're maintaining both. Which one is prefrable/deprecated? I've choosen this one for better API (really live the visit functionality) and speed.

solidity-parser is no longer receiving any updates. There have been some talks about replacing it with the antlr version but I haven’t got time to work on it yet.


Moving some of "dependencies" to be "peerDependencies" to support LTS versions and for backward compatibility

I think it is common for most of external modules to have peerDependencies of these dependencies that required but it does not make sense to add them again since they already will be fore sure exist in the main project, as for example, here for angularfire modules, it does not make sense at all to have dependencies of @angular/common to be installed while they will be for sure installed already in main project, so I suggest to move them to peerDependencies and devDependencies so you can warn user if something missing, AND install dependancies for developers who maintain the project.
The other MAJOR reason for this, I think Angular 6 will guarantee the backward compatibility, these dependencies will make issues for who want to user Angular 6 with the current version of Angular 5 thing, this will be going on for next versions as well, Angular 7 must be backward compatible with Angular 6 and so on: https://github.com/angular/angular/blob/master/docs/RELEASE_SCHEDULE.md
As you can see we need that for LTS matters as well! now there is no way to use current version with Angular 4 as for example.
What I suggest is moving the following dependencies to be peerDependencies and devDependencies:
    "@angular/common": "^5.0.0",
    "@angular/compiler": "^5.0.0",
    "@angular/core": "^5.0.0",
    "@angular/platform-browser": "^5.0.0",
    "@angular/platform-browser-dynamic": "^5.0.0",
    "rxjs": "^5.5.4",
    "zone.js": "^0.8.0"

What do you think?

Hi @almothafar! That is actually what we do. The top level package.json is for development of the library. There's a package.json in each feature's folder to uses peerDeps: https://github.com/angular/angularfire2/blob/master/src/database/package.json#L19-L28


snapshot read: Read 1 record exactly rather than 1 chunk at least per barrier

However, yesterday we suddenly realized this will cause problems: it forces every barrier must have more than 256 rows, which could cause barrier pile-up in some bad cases (such as when there is huge amplification in downstream MV)

For each barrier, we currently enforce to read 1 chunk at least. That could have issues when there's huge amplification.
So we enforce to read 1 row exactly instead, if no rows read before we recieved the barrier.
credit: @fuyufjh and @st1page

For each barrier, we currently enforce to read 1 chunk at leastt

IIRC, the background is to skip the tombstone in storage, right?

We spend a lot of time skipping tombstones when creating the iterator, but in the end, we are only going to read one line. This was quite wasteful and inefficient to me. 😕

We spend a lot of time skipping tombstones when creating the iterator, but in the end, we are only going to read one line. This was quite wasteful and inefficient to me. 😕

The dominant cost is skipping tombstones. Even though we only read 1 row, in the next epoch, since we already skipped the tombstones, we don't need to skip them again. So it will be pretty fast to read the next CHUNK_SIZE - 1 rows.
It's a worth while trade off IMO so we can deal with amplification cases.


Invalid MirrorNode stateproof endpoint

Given endpoint route /api/v1/:transaction-id/stateproof should be api/v1/transactions/:transaction-id/stateproof

thanks for the note! Updated!


Rename repository to dbus-native?

Is there a reason the package name doesn't match the repo name here?  I'll rename repo to dbus-native

done


🐞 - TuiSheet opens not it the bottom of the page with height less than 100vh

Playground Link
https://stackblitz.com/edit/angular-9tk9kb
Description
When page has not enough content to fill 100vh, TuiSheet opens in the bottom of page content, not in the bottom of the browser window
Angular version
12
Taiga UI version
3.23.1
Which browsers have you used?

[X] Chrome
[ ] Firefox
[ ] Safari
[ ] Edge

Which operating systems have you used?

[ ] macOS
[X] Windows
[ ] Linux
[ ] iOS
[ ] Android

Looks like we're missing height: 100% on the tui-root, I wonder if we can safely put it there 🤔

Looks like we're missing height: 100% on the tui-root, I wonder if we can safely put it there 🤔

I guess no, because otherwise there could be problem with vertically scrolled pages

Looks like we're missing height: 100% on the tui-root, I wonder if we can safely put it there 🤔

I guess no, because otherwise there could be problem with vertically scrolled pages

There shouldn't be, because overflow: visible would still make them properly scrollable. However if we can fix it without that it would be better. The reason the sheets host is sticky at the bottom and not fixed is so it does properly stick to the bottom during the address bar disappearance on iOS.

Looks like we're missing height: 100% on the tui-root, I wonder if we can safely put it there 🤔

I guess no, because otherwise there could be problem with vertically scrolled pages

There shouldn't be, because overflow: visible would still make them properly scrollable. However if we can fix it without that it would be better. The reason the sheets host is sticky at the bottom and not fixed is so it does properly stick to the bottom during the address bar disappearance on iOS.

I mean problem with TuiSheet again.
https://stackblitz.com/edit/angular-9tk9kb-3jjtcb

Fixed in a new SheetDialog component that we plan to use instead of Sheet.


devops: Update ics file for new dev call time

FYI for it to update for me, I had to delete the old one before opening this file


argscheck code cleanup

I did this cleanup to better understand the code for #198. Except for the removed console.warning, the code's behavior should remain unchanged by this PR.
IMHO, this could go into a patch release.

Do you know if this code is safe to run in the Android 4.4 webview?

@dpogue No, I don't know that. I already wondered what the oldest platform would be that this has to run on.
Would be great if we could run the automated tests on all supported platforms. But that would mean so much setup work 😣
The easier approach would probably be to run our built code through Babel. With a browserlist-based config we wouldn't have to worry about JS engine compatibility anymore.

Checking with ECMAScript compatibility table, Android 4.4 only supports  5% of ES6. Things used for example: const, arrow functions, and spread operator are not supported.


Check for: Code Indention

If the Code is not correct indented, it should be at least an warning.

Is this really needed? Auto Format should be enabled and executed on save, then you never need to care about indent

I see. I will keep it in the backlog but wont look into it now, as I would expect this to not be that easy to write and the benefit is not that huge as by now.


Feature - Set Gauge

This PF builds off of the naive gauge stacking functionality introduced by #1844 to provide a better internal API for dealing with gauges that have a set number of slots that can each only be filled by a specific value. Includes some timeline and tooltip display enhancements for empty values. Gauges displaying timeline content using this new type are:

Monk: Lunar and Solar Nadis
Samurai: Sen
Bard: Codas

Branch contains the changes also made in PRs #1844 and #1866. Merging this one will also merge those changes in. If you want to see the minimal set of changes introduced by this PR, merge those first.

Note that this PR will have merge conflicts with #1867. Take care when merging or get a hold of me to clean the other up after merging one of the two.


fix default nested keys returning none

If the "parent" key of a nested value exists in both the _config and _defaults dictionary, None will be returned if the value doesn't exist in the _config dict.
For example if we have the following config:
_config = {
    "foo": {
        "bar": {
            "foo": "bar",
        }
    }
}
_defaults = {
    "foo": {
        "bar": {
            "bat": "baz",
        }
    }
}

In current statev.get("foo.bar.bat") would return None as it never cascades through the _defaults dictionary. These changes would first search through the _config dictionary then fall back to defaults. Following the hierarchy that already exists. So the return of v.get("foo.bar.bat") would return "baz".

Thank you, I'll release this in a bit.

Released in v1.1.0.


runtime(lynx): Update for Lynx 2.8.9

Thanks, but why did you remove the :set cpo settings?

Because my local versions are in Vim9 script and I forgot to do the 'cpo' dance when converting them back to legacy script.
Sorry about that, I'll update it later today.

Thank you!


ENOENT while extracting an tar with hardlinks

File: gcc-arm-none-eabi-9-2020-q2-update-mac.tar.bz2 from https://developer.arm.com/tools-and-software/open-source-software/developer-tools/gnu-toolchain/gnu-rm/downloads/9-2020-q2-update
[Error: ENOENT: no such file or directory, link './arm-none-eabi/lib/libg.a' -> '/Users/XiNGRZ/****/arm-none-eabi/lib/libc.a'] {
  errno: -2,
  code: 'ENOENT',
  syscall: 'link',
  path: './arm-none-eabi/lib/libg.a',
  dest: '/Users/XiNGRZ/****/arm-none-eabi/lib/libc.a'
}

Just did some investigation and found:
https://github.com/kevva/decompress/blob/84a8c1046946add1a6ae01c54dbebf312e4ffc85/index.js#L121
I think x.linkname should be joined with the output path. Otherwise fsPromises.symlink can't find the target.

Finally I've fixed the problem. I would like to share my solution.
The issue was brought by hard links:

The source of hard link should be an absolute path, instead of a relative path
Creation of hard links should be deferred until all files are wrote to the file system

I've make a test case to reproduce the issue, as well as the solution. Since my fork was refactored far ahead from this project, I'm not going to make a PR.

I also encountered this error.
Is it possible to fix this package to include the patch suggested by @xingrz ?


[Feature] Widget Grouping Phase - 3 (Cut Copy Paste)

name: "Pull Request"
about: Create a pull request to submit new contributions to appsmith
title: "[FIX/FEATURE]"
labels:
assignees:

Pull Request Template
Use this template to quickly create a well written pull request. Delete all quotes before creating the pull request.

Description

[ ] Hot keys for cut(cmd/ctrl + x), copy(cmd/ctrl + c), paste(cmd/ctrl + v) for multiple widgets
[ ] UX for widget placement on paste
[ ] Implementing above UX(post discussion)

Fixes #5014
Fixes #5365

if no issue exists, please create an issue and ask the maintainers about this first

Type of change

Please delete options that are not relevant.

Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to not work as expected)
This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions, so we can reproduce.
Please also list any relevant details for your test configuration.

Test A
Test B

Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes

Test coverage results :test_tube:
:green_circle: Total coverage has increased
// Code coverage diff between base branch:release and head branch: feature/widget-grouping-3

Status
File
% Stmts
% Branch
% Funcs
% Lines

:green_circle:
total
54.17 (0.89)
36.15 (0.88)
32.83 (0.9)
54.66 (0.86)

:red_circle:
app/client/src/actions/batchActions.ts
71.43 (-14.28)
100 (0)
0 (-50)
100 (0)

:green_circle:
app/client/src/actions/controlActions.tsx
76.92 (7.69)
100 (0)
25 (25)
66.67 (11.11)

:red_circle:
app/client/src/actions/metaActions.ts
72.73 (-9.09)
100 (0)
0 (-33.33)
62.5 (-12.5)

:green_circle:
app/client/src/actions/widgetActions.tsx
82 (6)
0 (0)
46.67 (20)
76.47 (8.82)

:red_circle:
app/client/src/actions/widgetSelectionActions.ts
100 (0)
50 (-50)
100 (0)
100 (0)

:green_circle:
app/client/src/components/designSystems/appsmith/ContainerComponent.tsx
93.33 (0.47)
55 (0)
100 (0)
93.33 (0.47)

:green_circle:
app/client/src/components/editorComponents/DropTargetComponent.tsx
64.29 (1.02)
39.73 (1.37)
50 (6.25)
59.77 (1.15)

:green_circle:
app/client/src/components/editorComponents/CodeEditor/index.tsx
76.21 (2.42)
55.65 (5.22)
59.38 (3.13)
77.2 (2.59)

:green_circle:
app/client/src/constants/messages.ts
71.97 (0.32)
100 (0)
15.24 (0.95)
76.03 (0)

:green_circle:
app/client/src/pages/Editor/GlobalHotKeys.tsx
71.25 (18.24)
39.13 (39.13)
60 (24.52)
69.74 (19.11)

:red_circle:
app/client/src/pages/Editor/Explorer/Pages/PageContextMenu.tsx
71.43 (-0.79)
60 (0)
12.5 (0)
73.53 (-0.76)

:red_circle:
app/client/src/pages/common/CanvasSelectionArena.tsx
90.38 (-1.78)
57.58 (0)
82.35 (0)
90.1 (-1.82)

:green_circle:
app/client/src/reducers/entityReducers/metaReducer.ts
42.86 (14.29)
0 (0)
16.67 (16.67)
42.86 (14.29)

:green_circle:
app/client/src/reducers/uiReducers/dragResizeReducer.ts
85 (2.5)
61.54 (3.85)
63.64 (0)
87.18 (2.56)

:green_circle:
app/client/src/sagas/ApplicationSagas.tsx
19.9 (1.05)
3.39 (0)
9.09 (0)
22.84 (0.62)

:red_circle:
app/client/src/sagas/BatchSagas.tsx
25.81 (-16.13)
8.33 (-16.67)
20 (-20)
32 (-20)

:red_circle:
app/client/src/sagas/EvaluationsSaga.ts
17.5 (0)
1.3 (0)
3.85 (-3.84)
20.35 (0)

:green_circle:
app/client/src/sagas/RecentEntitiesSagas.ts
44.83 (0)
12.12 (1.51)
50 (0)
44.83 (0)

:green_circle:
app/client/src/sagas/WidgetOperationSagas.tsx
43.93 (33.38)
30.28 (29.03)
50.59 (43.65)
44.3 (32.92)

:red_circle:
app/client/src/sagas/WidgetOperationUtils.ts
54.87 (-8.09)
33.33 (-13.34)
69.23 (5.59)
55.45 (-7.22)

:red_circle:
app/client/src/sagas/WidgetSelectionSagas.ts
96.2 (-2.28)
93.48 (0.98)
100 (0)
95.77 (-2.54)

:green_circle:
app/client/src/utils/AppsmithUtils.tsx
56.42 (2.23)
29.07 (5.81)
43.24 (2.7)
52.26 (2.58)

:green_circle:
app/client/src/utils/DynamicBindingUtils.ts
90 (1.54)
80.28 (4.22)
76.19 (4.76)
88.5 (1.77)

:green_circle:
app/client/src/utils/helpers.tsx
53.59 (1.96)
26.76 (4.22)
23.08 (3.85)
47.5 (2.5)

:green_circle:
app/client/src/utils/storage.ts
43.48 (8.7)
13.64 (13.64)
22.22 (18.52)
36.59 (8.54)

:sparkles: :new:
app/client/src/utils/hooks/useCanvasMinHeightUpdateHook.ts
100
85.71
100
100

:green_circle:
app/client/src/widgets/BaseWidget.tsx
78.81 (0)
44.19 (2.33)
77.42 (3.23)
77.88 (0)

:red_circle:
app/client/src/widgets/MetaHOC.tsx
75 (-7.35)
47.37 (-10.52)
92.31 (0)
74.58 (-8.47)

:green_circle:
app/client/src/widgets/Tabs/TabsWidget.tsx
69.4 (2.98)
46.24 (9.68)
60.71 (0)
68.5 (3.15)

:sparkles: :new:
app/client/test/testCommon.ts
100
50
100
100

:sparkles: :new:
app/client/test/testMockedWidgets.tsx
100
100
100
100

:x:
app/client/test/testCommon.tsx
100
50
100
100

/ok-to-test sha=27fb6aa

/ok-to-test sha=b5b916b

/ok-to-test sha=915eb2b

/ok-to-test sha=915eb2b

@marks0351 Feature has been tested on the deploy preview and looks good.


is gpus no longer available?

Describe the bug
I haven'been able to access GPU any more since last 3 weeks  "There is no runtime available right now. Please change the compute type or try again later."
I haven't found any info regarding why it is constantly unavailable. I wonder if this is expected? Because I didn't see any pr release regarding this matter either.

We can use GPU but the resources reach the limit frequently. Sorry for the inconvenience and we are tackling this issue eagerly from the last year.

We can use GPU but the resources reach the limit frequently. Sorry for the inconvenience and we are tackling this issue eagerly from the last year.

thank you for the prompt respponse. I have been trying 20+ times in the past 4 hours but no luck
Do you have plan to give better access for paid subscribers? LIike what colab pro or colab pro plus is doing.

We can use GPU but the resources reach the limit frequently. Sorry for the inconvenience and we are tackling this issue eagerly from the last year.

I have tried the whole day and don't have access. I gave up.
Personally I feel like it was not resource issue but like a bug?
Anyway I just want to share that as a working professional I don't really mind paying for the service usage, therefore I do have a lot alternative choices. But it is your lab "environment", UI, response, all that make me feel more inclined to use it, more than Colab, Kaggle or other hosted services.

SageMaker Notebooks or SageMaker Studio. Those have no GPU limits.

Hi MicheleMonclova, The studiolab notebooks are being given as enabler for students. The GPU will help such students' projects. SInce the GPUs are no more available, and that a GPU can never be allowed after multiple trials, we request you to help on how the SageMaker Notebooks or SageMaker Studio be used with out extra cost or yearly limits etc.

Hi Bobycv06fpm - We are excited about a few things that we have planned to make our GPU capacity more available. Feel free to reach out to me on this form  and we can discuss further.  I would like to know the plans with your students, and if our new changes will indeed help.

I am concerned. Last week I tried to use SageMaker Sutdio Lab. Since yesterday I also tried again to enter the workspace by using GPU. All the time I have received There is no runtime available right now. Please change the compute type or try again later. Is there a way to know if my account was susspended or a at least you should provide with a expected time to restore access to gpu. Even CPU was locked with the message Too many requests.  Also the use of conda in SageMaker Studio, I think is a great feature. However, the fact that I can lunch a Colab session and not a GPU session in SageMaker is very dissapointing. So I would like to know if it is a problem with the account ¿which? is it a problem with providing free access to GPU? what is the problem? when can it be restored? will it not be restored in the near future so that I won't try it anymore and just make a backup of files and delete everything?

Hi LeninGF,
Based on what you described I don't think there is a problem with your account.  The demand for free GPU is never ending and we are working on ways to make if more fair so everyone can access it. We are working hard to make the architecture one you can really experiment and grow with. Thank you for your patience while we continue to work on this.
Michele

Hey all. Today we rolled out CAPTCHA to battle the bots and scripts that absorb compute. Hopefully you have better access getting user sessions.
Thank you for your patience.

Friends. The problem is not the bot vs. your infrastructure.
increase the number of computers now.
same error: There is no runtime available right now. Please change the compute type or try again later.

You're already blocking most codes. I saw it on the forum. Mining vs problematic works, you are already closing accounts.
What else can a bot account do? You are closing the account.
but your infrastructure is still incomplete.

Hi Bekahose. we are monitoring our capacity and everything looks good on our end.
Which forum are you referring to.
When you say we are blocking codes do you mean IP addresses?
I don't understand your second message.
Please explain.

Let us close this issue. We continously try to allocate our capacity for every data scientists / developers fairly.


New sails app, doesn't show the homepage

Sails version: v1.0.0-36
Node version: 6.10.2
NPM version: 4.5.0
Operating system: Windows 7

I did a clean install of the latest sail-beta, generated a project with sails new my-project.
When running sails lift nothing happens when I browse to http://localhost:1337/, the page keeps on loading and the homepage never comes.

Ok, fixed

@nojaf, can you provide an example repository? I just switched to 1.0.0-36 and have no problems.

I've pushed my sample to https://github.com/nojaf/sails-app

@nojaf, I just tested your repository and it works fine on Ubuntu. I recommend that you use logger for Sails.js and check where it stops. Another solution would be to use Docker or Vagrant.

How can I enable additional logging with sails lift?

You can set your logging level to silly. Check this:
http://sailsjs.com/documentation/reference/configuration/sails-config-log

Another thing you could try is starting Sails.js with node app.js instead of sails lift.

Hmm, not entirely sure why but changing the logging made the homepage appear.
Log output:
silly: Grunt :: >> 7 paths cleaned.
silly: Grunt :: Running "jst:dev" (jst) task
silly: Grunt :: >> Destination not written because compiled files were empty.
silly: Grunt :: Running "less:dev" (less) task
silly: Grunt :: >> 1 stylesheet created.
silly: Grunt :: Running "copy:dev" (copy) task
silly: Grunt :: Copied 3 files
silly: Grunt :: Running "coffee:dev" (coffee) task
silly: Grunt :: >> 0 files created.
silly: Grunt :: Running "sails-linker:devJs" (sails-linker) task
silly: Grunt :: padding length 4
silly: Grunt :: File "views/layout.ejs" updated.
silly: Grunt :: Running "sails-linker:devStyles" (sails-linker) task
silly: Grunt :: padding length 4
silly: Grunt :: File "views/layout.ejs" updated.
silly: Grunt :: Running "sails-linker:clientSideTemplates" (sails-linker) task
silly: Grunt :: padding length 4
silly: Grunt :: File "views/layout.ejs" updated.

Running "watch" task
Waiting...
silly: View override argument passed to res.view():  homepage
silly: Serving view at rel path:  homepage
silly: View root:  C:\Temp\sails-app\views
verbose: Rendering view: "homepage" (located @ "C:\Temp\sails-app\views\homepage")
verbose: • using configured layout:: layout (located @ "C:\Temp\sails-app\views\layout")

Then I reverted the change to the logging and I tried again: the app ran smoothly.
Not sure if sails has cached anything by now but the app seems to be working just fine.
Feel free to close this issue

@nojaf, nice to hear that. Maybe the port 1337 was blocked.

Might be the case, I noticed that ports 1342 and 1345 are in use, if these services use a range around 1300, there could have been a collision.
I've used port 8300 as a test and the homepage runs just fine.
set sails_port=8300
sails lift


export struct required to build Tools

Without this, Tools cannot be built outside this repo.

Good catch, thanks for fixing this!


HHH-10360 : Natural ID columns are nullable by default

I need to add a test that reproduces the bug.

Merged.


Create Marketing Campaigns Glossary Pages

To do:
Write brief Glossary entry for each of the following topics on a separate glossary page and link to these topics from the Terminology section of the Marketing Campaigns Overview Page:

Campaigns
Segments
Lists
Custom Fields
Reserved Fields
System Fields
Senders

I'd like to take this one :D

@alfredlucero go for it! thank you!

Made a PR for it for you all to see :) 👍

@alfredlucero, you did a really awesome job on this! thanks so much for your help!!

no problem glad to help :D.


NN-1805 Missing/unaccounted for prisoners

Still WIP but only visible by hitting /missing-prisoners directly.


perf(runner): Use global.performance.now instead of Date.now

Description

Close: #6377
Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

[x] It's really useful if your PR references an issue where it is discussed ahead of time. If the feature is substantial or introduces breaking changes without a discussion, PR might be closed.
[ ] Ideally, include a test that fails without this PR but passes with it.
[x] Please, don't make changes to pnpm-lock.yaml unless you introduce a new test example.

Tests

[x] Run the tests with pnpm test:ci.

Documentation

[x] If you introduce new functionality, document it. You can run documentation with pnpm run docs command.

Changesets

[x] Changes in changelog are generated from PR name. Please, make sure that it explains your changes in an understandable manner. Please, prefix changeset messages with feat:, fix:, perf:, docs:, or chore:.

Hi team! 👋
I'm seeing some flaky tests here. 🤔 Same code, different results – sometimes it passes, sometimes it fails. Not sure if we've got some unstable tests on our hands or if there's something else going on. Anyone else run into this?


ISPN-16031 Lock SIFS directories to avoid shared usage between instances

https://issues.redhat.com/browse/ISPN-16031
Create a global lock backed by the file system to control concurrent usage of files within and between virtual machines.
When creating the cache, an exception is thrown in case the current cache is not the unique owner of the cache data directory.
See, this change might mean a change in behavior for some applications. But it affects misconfigured embedded applications only.

Nice refactoring of the lock stuff


Multi-metadata support

Reduced minimal metadata to exclude IMS-specific fields
Put IMS-specific fields to a separate JSON schema as an extension of the minimal one
Added another JSON schema with LC-MS specific fields
Added Adducts field to Metaspace_options

@iprotsyuk merged into lcms-support

@intsco can you pull my last commit to lcms-support as well?

@iprotsyuk sure I will, meanwhile could you send a new PR into lcms-support branch?

ok, will do


Deployment

Deployment
User Story
As a bootcamp student,
I want a pre-work study guide webpage
so that I can easily access and review the information learnt during pre-work
Acceptance Criteria
GIVEN a Prework Study Guide website
WHEN I visit the website using the URL,
THEN I can access my website from any browser

Website is deployed, but receiving the following error in the console window
Error with Permissions-Policy header: Origin trial controlled feature not enabled: 'interest-cohort'.
DevTools failed to load source map: Could not load content for chrome-extension://hnfanknocfeofbddgcijnmhnfnkdnaad/content.js.map: System error: net::ERR_BLOCKED_BY_CLIENT
script.js:24 Here are the topics we learned through Prework:
script.js:6 HTML
script.js:6 CSS
script.js:6 Git
script.js:6 JavaScript
script.js:26 Which topic should we study first?
script.js:14 Let's study CSS!
DevTools failed to load source map: Could not load content for https://rararach-l.github.io/prework-study-guide/requestProvider.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE


feat: add native logging with headers and body to CloudEvent

Add better native logging to the CloudEvent class.
Proposed Changes
Logging a CloudEvent should call the toString of the CloudEvent.
Fixes https://github.com/cloudevents/sdk-javascript/issues/432

I'm getting errors with the index type of the symbol. Want to go with the existing test and perhaps you can add changes if appropriate after?

I'm getting errors with the index type of the symbol. Want to go with the existing test and perhaps you can add changes if appropriate after?

I was able to get the test to pass like this:
  it("serializes as JSON with raw log", () => {
    const ce = new CloudEvent({ ...fixture, data: { lunch: "tacos" } });
    const sym = (Symbol.for("nodejs.util.inspect.custom") as unknown) as string;
    const f = (ce[sym] as CallableFunction).bind(ce);
    expect(ce.toString()).to.deep.equal(f());
  });

Also, to eliminate the warnings that are being generated, the CE function should look like this:
  /**
   * The native `console.log` value of the CloudEvent.
   * @return {string} The string representation of the CloudEvent.
   */
  [Symbol.for("nodejs.util.inspect.custom")](): string {
    return this.toString();
  }

Great, thanks @lance. PTAL.


iOS: Push notifications sent for muted streams

The UI claims that push notifications will not be sent for muted streams unless you are mentioned, but that doesn't seem to be the case. I've been receiving notifications for a muted stream even when I am not mentioned.

@kunall17 do you know anything about that?
Also, likely this needs to be handled on the backend, so pinging @timabbott and @showell

If this were an issue, it would be on the backend, not the mobile app.

I’m not sure what you mean by if it’s an issue. It’s definitely an issue for me. Should I file a bug on the server repo? Provide more info? Something else?

On Oct 16, 2017, at 8:16 PM, Tim Abbott<EMAIL_ADDRESS>wrote:
If this were an issue, it would be on the backend, not the mobile app.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/zulip/zulip-mobile/issues/1314#issuecomment-337080256, or mute the thread https://github.com/notifications/unsubscribe-auth/AGytfnsvZNbCiovfGowD2GFHkhzO-iFgks5ss_HpgaJpZM4P7Iy1.

@tthoma24 sorry I was in a hurry and attempting primarily to communicate with @borisyankov here.  What I mean is just that the server is where the logic is that decides whether a push notification is triggered or not, so whatever the issue is here is almost certainly in the server code.  We'll move the issue if needed once we know more exactly what it is.
@tthoma24 can you check your settings for the stream in question for whether you have the "send push notifications for messages sent to this stream" setting checked in addition to the stream being muted?  Also, can you confirm whether the stream is muted or just the topic in the stream is muted?
If you can provide me with a specific stream name where you saw this happen, I can check these things directly, if that's easier for you.

Yes, that setting is checked (but greyed out since the stream is muted)

This is actually a backend bug; I'll take care of it.

Fixed in master, thanks for the report @tthoma24!


Display banner informing users about their SW subscription

This PR removes the pop-up modal shown to the users when they first log in to the deployment driver and replaces it with a permanent alert/banner across the top of the UI.
Based on number of SW subscriptions, the user will see different text in the banner however in each different banner the user is always presented with a link to the RH console.
Jira item: https://issues.redhat.com/browse/AAP-15157
Screenshots
Below are screenshots of the possible cases:
No SW subscription yet (probably the most common case)

Existing SW subscription

Error scenario (when the RH API does not respond)

Can you add:
Werkzeug>=2.0.0,<3.0.0
to requirements.txt?  It's picking up 3.x.y, which is not compatible.


Support latest Material Design Icons

Flutter does not seem to have the latest icons from Material Design in Icons.
For example, the Home section is completely missing as well as text_snippet etc.
Use case
The icon set seems to have been extended a fair bit and these additional icons should be included.
Proposal
Update the Material Design icons font and the Icons class.

Hi @creativecreatorormaybenot
follow up on https://github.com/flutter/flutter/issues/27956,
I'm closing the current one as duplicate.
If you disagree please write in the comments and I will reopen it.


'a' returns a valid date

date.DateDataParser().get_date_data('a')
Returns
{'date_obj': datetime.datetime(2016, 1, 4, 0, 0), 'period': 'month', 'language': 'en'}
also, single letters d, h, j, k, l, m, s, and v also return valid dates, some with 'en' as the detected language, as well as other languages.
OS: macOS 10.12.1

Update, seems related - "and a" returns January, i.e.:
DateDataParser(languages=['en'], settings={ 'RELATIVE_BASE' : datetime(5000, 6, 15) }  ).get_date_data('and a')
Returns
{'date_obj': datetime.datetime(5000, 1, 15, 0, 0), 'period': 'month', 'language': 'en'}

Interesting bug. So 'D' gets translated to 'Sunday' in ro language that's why it gives:
In [16]: DateDataParser().get_date_data('d')
Out[16]:
{'date_obj': datetime.datetime(2016, 12, 4, 0, 0),
 'language': 'ro',
 'period': 'day'}

Similarly for en language a translates to 1 and since the default order is MDY it assumes 1 to be the month (january).

In the meantime, how can I instantiate a DateDataParser that ignores "simplifications"?

As we closed this: https://github.com/scrapinghub/dateparser/issues/655 should we close this issue?
Should we allow to ignore simplifications? does have this any real use case or it's just for this weird requirement?
cc: @Gallaecio

I think this and #655 are duplicates. Re #655 closure - as I understand it's more of a "won't fix" (fixing it does not look feasible), not that it's an expected behaviour to treat "1" or "a" as a valid date?

Closing this issue. The reasons are explained in this comment: https://github.com/scrapinghub/dateparser/issues/330#issuecomment-731809713
Thank you for your feedback!


Macro system for standardizing wasm attribute emission/parsing

So I was recently banging my head against the wall trying to parse wasm attributes and I came up with an idea for making this process painless and convenient. It looks something like this right now but I'd be open to suggestions.
#[derive(Attrs)]
#[cw_serde]
pub enum ExecuteMsg {
    #[attrs = "HelloAttrs"]
    Hello{},
    #[attrs = "WorldAttrs"]
    World{}
}

#[derive(MsgAttr)]
pub struct HelloAttrs {
    /// The action field should be mandatory and unique so parsing
    /// any message can be fully automated. Perhaps the action field shouldn't even be part of the struct
    /// and just assumed to be present in the attributes.
    action: String,
    sender: Addr // <-- fields must be `Serialize + Deserialize`
}

MsgAttr derives From<Vec<Attribute>> and Into<Vec<Attribute>> to make parsing extremely easy, and
Then in the smart contract we can have
let res = Response::new().with_attributes(HelloAttrs{
    action: "hello".to_string(),
    sender: "foo bar baz".to_string()
});

The Attrs macro the creates a new enum that looks like this:
pub enum ExecuteMsgAttrs {
    Hello(HelloAttrs),
    World(WorldAttrs),
}

and we can access to a parsing function like this:
pub fn parse_attrs(attrs: Vec<Attribute>) -> Option<ExecuteMsgAttrs>

This could be made a little more robust by including wasm events as well but I haven't really thought that far ahead. Let me know what you think!

I have a similar problem/use case but only for the attribute emission part. Here the focus is to ensure stability for clients and avoid to easily break them because keys change.
But what's not so clear to me is the parsing. I assume you are referring to SubMsgResponse right? Is event parsing working well for you there? I guess it would be kindof unreliable because events can change with different versions of the host, we do some filtering in wasmd and events are not even covered by consensus. So the question is here, should event parsing be embraced at all and if yes, under which constions.
Happy for any thoughts or use case descriptions. See also https://github.com/CosmWasm/cosmwasm/issues/1995

But what's not so clear to me is the parsing. I assume you are referring to SubMsgResponse right? Is event parsing working well for you there? I guess it would be kindof unreliable because events can change with different versions of the host, we do some filtering in wasmd and events are not even covered by consensus. So the question is here, should event parsing be embraced at all and if yes, under which constions.

Ah sorry I wasn't clear. No, for my use case I would be parsing wasm events within a bot off chain. It's basically just a convenience feature for easily reconstructing these attributes.
#[derive(MsgAttr)] Would derive some trait like From<Vec<Attribute>> or something like that which could be used for parsing off chain.

Interesting, yeah that sounds more solid to me.
Do you already have that approach implemented somewhere? Is it working well? Or do you strictly need cosmwasm-std support here? I wonder if this is more a best practice question or in scope of cosmwasm-std.

Do you already have that approach implemented somewhere? Is it working well? Or do you strictly need cosmwasm-std support here? I wonder if this is more a best practice question or in scope of cosmwasm-std.

I've posted this here because in my dream world, all smart contracts would use #[derive(Attrs)] (Or it would be included in #[cw_serde]). This would make parsing attributes off chain a dream and indexing protocols extremely easy. It also comes with the benefits that you mentioned above, standardizing attribute emission.
I currently have a prototype of this working, and if you're interested in including it I'd be happy to chat with you about what the api should look like, polish it up, and contribute.

Right, but just like cw2 it can become something well established in the ecosystem but not necessarily in the standard library. cosmwasm-std is the slowest area in which we can innovate due to the extreme care required to ensure compiled contracts keep working.

Right, but just like cw2 it can become something well established in the ecosystem but not necessarily in the standard library. cosmwasm-std is the slowest area in which we can innovate due to the extreme care required to ensure compiled contracts keep working.

Yeah I totally get that! This derive wouldn't include any breaking changes so no need to worry about that. But I totally understand being hesitant to include changes like that. Ultimately your call, but I do think it would fit in nicely here ;)

We should think about how to handle this with the new schema #2206


Action is not working on Netflix/EVCache

https://github.com/drodriguezhdez/EVCache/runs/428170266

Now, working as action is compatible with used Gradle version.