Disable stacktrace on error

Is there a way to disable stacktraces in nextJS?
Currently, even when i'm running nextjs in production mode, on an error nextjs shows a stacktrace in the http response body, containing full filesystem paths which I really would like to disable.
For instance, calling a url like this:
http://localhost:3000/_next/dummy/page
returns the following response:
 window.__NEXT_REGISTER_PAGE('/', function() {
      var error = {"name":"Error","message":"INVALID_BUILD_ID","stack":"Error: INVALID_BUILD_ID\n    at Server._callee9$ (/home/user/development/project/node_modules/next/dist/server/index.js:451:29)\n    at tryCatch (/home/user/development/project/node_modules/regenerator-runtime/runtime.js:65:40)\n    at GeneratorFunctionPrototype.invoke [as _invoke] (/home/user/development/project/node_modules/regenerator-runtime/runtime.js:303:22)\n    at GeneratorFunctionPrototype.prototype.(anonymous function) [as next] (/home/user/development/project/node_modules/regenerator-runtime/runtime.js:117:21)\n    at step (/home/user/development/project/node_modules/next/node_modules/babel-runtime/helpers/asyncToGenerator.js:17:30)\n    at /home/user/development/project/node_modules/next/node_modules/babel-runtime/helpers/asyncToGenerator.js:35:14\n    at Promise.F (/home/user/development/project/node_modules/core-js/library/modules/_export.js:35:28)\n    at Object.<anonymous> (/home/user/development/project/node_modules/next/node_modules/babel-runtime/helpers/asyncToGenerator.js:14:12)\n    at Object._nextBuildIdPagePath [as fn] (/home/user/development/project/node_modules/next/dist/server/index.js:514:27)\n    at Router._callee$ (/home/user/development/project/node_modules/next/dist/server/router.js:81:60)","buildIdMismatched":true}
      return { error: error }
    })

Is there a way to disable this behaviour?

How are you running it in production? Next only has the stack trace enabled in development 🤔

@rprinsen this is a really good catch. It should do that. I've submitted a PR to fix it: #2843.

Great Tim! thanks for the quick response!
Would it be possible to merge this in the 2.x branch too?
We're running 2.4.9 now and are really close to a production release.
So not really keen on going to 3.x just yet :)

@rprinsen I'd highly recommend updating to v3, since it doesn't have real breaking changes, only a tiny bit of the getInitialProps of _document changed. The rest is the same + extra features / bugfixes / dev improvements etc 😄


Since commit 552d3833 the 'api' folder is missing, yet all the documentation still refers to it

This is making it rather difficult to install, as I'm not an expert in mvn, nmp, mongo or any of the tools you require.
Could you provide (or point me to) some updated documentation, please?

This is a duplicate of #3074 . please check the issue

@rvema Thanks for the prompt response, but closing the issue and redirecting doesn't exactly address the issue I raised.
I found the new API repo, that is not the issue.  The issue is the lack of documentation/ incorrect documentation.  Should I raise a new issue but word the title differently? "Documentation incorrect", perhaps?
I'd really like to use Hygieia, but it's really difficult to get started without guidance ;)

@denhamcoote Sorry for the inconvenience, We are in the mid of repository migration hence some of the documentation links are not functional. We should be done with this effort in couple of weeks and will fix the documentation asap.

@rvema Thank you for your efforts - I look forward to being able to get it working :)


[CSL-124] Optimise serialisation

@neongreen
Bitcoin tries to be smart about serialising its data (blocks, transactions, even integers). Should we do the same? This is a catch-all issue for listing and discussing optimisations.
I'll list the optimisations I can think of:

The transactions in the block are stored as a tree. Instead they could be stored as a list, with the tree being reconstructed during deserialisation. This would save us 2×tx_count bytes per block.

The numbers could be optimised better (Bitcoin uses a special “compact int” encoding for that purpose). Our ChainDifficulty is a 8-byte int; our SlotId is 8+2=10 bytes; our transaction inputs contain a 4-byte int for index, when in most cases it would fit into one byte; our Coin is 8 bytes but I'm not sure whether anything can be done here (other than assuming that multiples of 10^8 or 10^7 satoshi would be used more often than fine-grained amounts and optimising for them).

UPDATE: I have implemented varint and it's used for most things now, so #2 is obsolete. It might still be useful to use some kind of floating-point encoding for Coin, though (like Bitcoin does).

@gromak

Should we do the same?

Yes, of course. This issue is similar to CSL-114.

@volhovm
TLDR: https://github.com/bitcoin/bitcoin/blob/master/src/serialize.h

Variable-length number serialization (used everywhere -- in set/map/vector length as well).
Map and Set format is just sequential elements.

I think for now it's enough to abstract binary format to a separate module. Problems with libraries who require Serializable may appear if we declare our own typeclass for that. TBD

@georgeee

commit https://github.com/input-output-hk/cardano-sl/commit/969e35c58bc07a9e54338d76c03e0d3ca04631b4


[bug]: batchopenchannel return the change on a P2WPKH address instead of P2TR

Since 0.15.1 (https://github.com/lightningnetwork/lnd/pull/6810) for the change on opening transaction it's used a taproot address but that's not the behavior on batch opening

cc @Torakushi I think you forgot to add the ability to add the change_scope for the batch_channel_openings command, I think we could also set the default change_scope for batch_channel_openings to p2tr?

Right! I don't think we need to make it configurable. only defaulting to P2TR should be enough. what do you think?

makes sense let's default to P2TR, should be a quick change do you wanna do it (I can do it too if you have no time)?

I will do it tomorrow! should be straight forward


Add db level api to get alert source by filter

What this PR does / why we need it:
Privode the db level api to get alert source by filter, which will be used by trap_receiver to get alert source by host.
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
Special notes for your reviewer:
Release note:

LGTM

LGTM
Please attach test report

Done! Thanks.


handling of vim.lsp.buf.execute_command deprecation

Description
I noticed that recently the vim.lsp.buf.execute_command has been deprecated and replaced with Client:exec_cmd, see. I have already adapted most of the occurrences, in the texlab configuration, of the old way to use the new method. However, the new method is only available on newer nightly versions. How should the new way be deployed , in order to cause the least amount of disturbance to the users?

ref utils.lua have nvim_eleven  you can use same logic in textleb config


Train pytorch model for UK moths

working for https://github.com/AMI-trap/on_device_classifier/commit/eca6238d301f45580e8d1ea56789c36d256a189f (on baskerville see on_device_classifier/02_model_training/pytorch/logs/turing-macro_v01_efficientnetv2-b3_2023-06-08-14-34.pt)


Str-711: bump RETH (and deps) to the latest version.

Description

Str-711: bump RETH (and deps) to the latest version. Also, fix lints.
Type of Change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature/Enhancement (non-breaking change which adds functionality or enhances an existing one)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation update
[x] Refactor
[ ] New or updated tests
[x] Dependency Update

Notes to Reviewers

This is a preparation work needed to remove boa from the dependency graph. And turn cargo-audit back on.
Checklist

[ ] I have performed a self-review of my code.
[x] I have commented my code where necessary.
[x] I have updated the documentation if needed.
[x] My changes do not introduce new warnings.
[ ] I have added tests that prove my changes are effective or that my feature works.
[x] New and existing tests pass with my changes.

Related Issues
EDIT(@storopoli): Closes https://github.com/alpenlabs/strata/security/dependabot/12

@storopoli

Oh, we need to fix the prover CI job that is failing. You might need to bump the nightly version.

Yes, I noticed it. The problem is some reth crates of version 1.1.3 require 1.82 rust, while the rust version in the sp1 toolchain is 1.81-dev...
I contacted succinctlabs on the telegram, asking to bump the rust version in the sp1 toolchain.

I contacted succinctlabs on the telegram, asking to bump the rust version in the sp1 toolchain.

Any update on this? Maybe move the PR to a draft before we figuring this out.

Any update on this? Maybe move the PR to a draft before we figuring this out.

@storopoli yes, there are updates.
They provided me with instructions on forking their toolchain, so I can do it myself while they are busy and it's not the priority. I tried doing everything according to the instructions, but turns out the default github runners are running out of disk space in the process of building the toolchain.
I just rented a vm in cloud and am trying to do it manually. If I fail, I'll convert this PR to draft and poke them from time to time.
Quite sad, because it means I have to rebase this big PR from time to time to maintain it. It is what it is...

@storopoli convering to draft. I tried building everything from scratch on my cloud vm, but failed somewhere in the middle. I give up on efforts to fork their toolchain, not worth the time.
I'll periodically update this branch to keep up with the updates from main.

Any update on this? Maybe move the PR to a draft before we figuring this out.

@storopoli yes, there are updates.
They provided me with instructions on forking their toolchain, so I can do it myself while they are busy and it's not the priority. I tried doing everything according to the instructions, but turns out the default github runners are running out of disk space in the process of building the toolchain.
I just rented a vm in cloud and am trying to do it manually. If I fail, I'll convert this PR to draft and poke them from time to time.
Quite sad, because it means I have to rebase this big PR from time to time to maintain it. It is what it is...

Oooof babysitting PRs is annoying...
Let me know if you need to share the load once the SP1 saga is solved.


Cannot connect to locally running Jupyter server on vscode.dev from edge browser

Start Jupyter lab locally
Open VS Code insiders in web (insiders.vscode.dev) in MS Edge browser
Attempt to connect to this url
Fails with a CORS error

Try the same in Chrome browser & it works
Note: this only applies to connecting to http://localhost:... from Edge Browser

@Yoyokrazy @rebornix
Please see updated instructions https://github.com/microsoft/vscode-jupyter/wiki/Connecting-to-a-remote-Jupyter-server-from-vscode.dev#allow-access-to-private-networks
Just as you have to pass a custom CLI argument for allow_origin* you will now need to set one more configuration item in the config file, this is defined in the above WIKI.
This is not an issue with the extension, but an issue that needs to be addressed by the end user launching JupyterLab/notebook.
Today if this is not configured, the user will be presented with a message and a link to the above WIKI.


Windows in FancyZone are sized under status bar

Microsoft PowerToys version
0.59.1
Running as admin

[X] Yes

Area(s) with issue?
FancyZones
Steps to reproduce
Set up 3 window split, with 0 margin. Align automaticity Firefox window to one of zones, bottom part will be hidden under status bar. This problem  is not related to Firefox, all apps are subjected to that problem, windows explorer status (element counter, and view mode) are also hidden when windows are aligned by Fancy Zone. Locking status bare dose not solve that problem.

✔ Expected Behavior
Windows should not be hidden under status bar.
❌ Actual Behavior
Windows are hiding under status bar.
Other Software
No response

OK, restarting Windows solves problem.

Had the same problem. Here we can see the actual zones definition (I reduced them vertically) and the snapped applications going about the status bar size bellow.
Fixed by either  autohiding the  status bar (this wont' do) or by enabling app auto resizing when zone size changes

/dup of https://github.com/microsoft/PowerToys/issues/10903


Find and add Industry of Employment data service (from ABS)

I pulled this out of the previous ABS issue because the rest of that should be solved now.
@AnaBelgun Do you have any more details on this?

@steve9164 I found an API for Industry of Employment on ABS stats.data:
http://stat.data.abs.gov.au/Index.aspx?DataSetCode=ABS_CENSUS2011_B44

It's here:
http://stat.data.abs.gov.au/ - Snapshots of Australia - Regional Statistics - LGA 2017, 2011-2017 - Economy and Industry - Industry of Employment (census) (last group at the bottom)


shoal_server.config could first look at env variable for config file path

For extra flexibility, the shoal_server configuration could first look at an environment variable (i.e., SHOAL_SERVER_CONFIG) for a config file path and load it from that path if given.

After a lot of digging there are a few problems with this.
Shoal server is actually run through apache (more specifically its run as the apache user). The apache user has no shell available so using a global env variable won't work.
Apache has a way of importing "enviroment" variables (SetEnv MY_VARIABLE_NAME my_variable value) in the apache conf file so they can be used by whatever web framework might be running on top of apache. In our case (web.py/wsgi) said variables can be accessed by web.ctx.env['MY_VARIABLE_NAME'] which seems great.
The problem is that web.py doesn't load the context until the first request of the web server has been made. This pretty much makes the environment variable useless for configuration since the webserver has to be active before the variables can be accessed this way.

I think this was brought up back when we envisioned Shoal agent as being easy to install and run from e.g. a user's home directory instead of installing into standard system locations. Doesn't seem as important anymore.


Add a document to describe how to define experiment scope

Signed-off-by: cwen0<EMAIL_ADDRESS>What problem does this PR solve?

Close #677

Codecov Report

Merging #678 into master will decrease coverage by 1.11%.
The diff coverage is 33.18%.

@@            Coverage Diff             @@
##           master     #678      +/-   ##
==========================================
- Coverage   55.78%   54.67%   -1.12%
==========================================
  Files          68       68
  Lines        4383     4569     +186
==========================================
+ Hits         2445     2498      +53
- Misses       1768     1883     +115
- Partials      170      188      +18

Impacted Files
Coverage Δ

api/v1alpha1/podchaos_types.go
37.14% <ø> (ø)

controllers/networkchaos/ipset/ipset.go
37.14% <0.00%> (ø)

pkg/utils/chaosdaemon.go
51.21% <0.00%> (ø)

pkg/utils/grpc.go
0.00% <0.00%> (ø)

pkg/webhook/inject/inject.go
73.49% <0.00%> (-0.68%)
:arrow_down:

pkg/store/experiment/experiment.go
24.27% <12.28%> (-14.51%)
:arrow_down:

pkg/httpfs/fs.go
31.48% <31.48%> (ø)

controllers/twophase/types.go
54.20% <40.00%> (-1.68%)
:arrow_down:

controllers/networkchaos/netem/types.go
47.27% <50.00%> (ø)

pkg/utils/selector.go
52.41% <66.66%> (+0.17%)
:arrow_up:

... and 6 more

Continue to review full report at Codecov.

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

/merge

LGTM

/merge


PROGRAM TWEAKS

[x]  Separate authorities (blacklist, parameters, admin council: reset, pausing + passthrough?)
[x]  Remove staker PDA in favor of State account
[x]  Add ValidatorList address to Config so we can validate the list in instructions that don’t pass in the stake pool
[x]  Test RemoveValidator for validators that don’t have score computed
[x]  Adjust increase_validator_stake reserve_lamports to protect transient stake rent for other accounts
[x]  Figure out a better system for persisting blacklist validator indices
[x]  Add a check for Deactivate* state at the index marked for removal in epoch_maintenance

Before merge:

[] Fix tests
[] Fix Steward CLI


engine mirroring to googlesource hasn't updated in 10 hours

https://chromium.googlesource.com/external/github.com/flutter/engine
@godofredoc

@keyonghan you need to open a ticket to the git team, you can use b/167733567 as an example and ping the team in the git chat.

replica gets back to normal. GOB team will continue to work to address the root cause of this.


feat(recordings): add recording segment generator

This adds a script to produce dummy recording segments for load testing the recording consumer.
I heavily based (read: copypasta) the code from what's in sentry's test_recordings.py.
Limitations:

chunked segments are only length 1, if we get rid of chunked messages soon this isn't a huge concern
the message payload is a fixed length, we should add something to simulate variable messages sizes
this will need to be changed to handle compressed messages (i.e. not using json.dumps())
I'm not super familiar with our recording schema

Let me know if anything looks wrong.

Example messages generated using fake_kafka_producer:
% python main.py -f settings.yaml -n 10
Settings:
{'num_messages': 10, 'topic_name': 'ingest-replay-recordings', 'repeatable': False, 'kafka': {'bootstrap.servers': '<IP_ADDRESS>:9092'}, 'metric_types': {}, 'org_id': 1, 'project_id': 10, 'message': '[{"hello":"world"}]', 'compressed': False, 'dry_run': False}
Sending data...
[{"type": "replay_recording_not_chunked", "replay_id": 0, "org_id": 1, "key_id": 123, "project_id": 10, "received":<PHONE_NUMBER>.333632, "retention_days": 30, "payload": "{\"segment_id\":1}\n[{\"hello\":\"world\"}]"}]
[{"type": "replay_recording_not_chunked", "replay_id": 1, "org_id": 1, "key_id": 123, "project_id": 10, "received":<PHONE_NUMBER>.333656, "retention_days": 30, "payload": "{\"segment_id\":1}\n[{\"hello\":\"world\"}]"}]
[{"type": "replay_recording_not_chunked", "replay_id": 2, "org_id": 1, "key_id": 123, "project_id": 10, "received":<PHONE_NUMBER>.3337018, "retention_days": 30, "payload": "{\"segment_id\":1}\n[{\"hello\":\"world\"}]"}]
[{"type": "replay_recording_not_chunked", "replay_id": 3, "org_id": 1, "key_id": 123, "project_id": 10, "received":<PHONE_NUMBER>.333718, "retention_days": 30, "payload": "{\"segment_id\":1}\n[{\"hello\":\"world\"}]"}]
[{"payload": "{\"segment_id\":1}\n[{\"hello\":\"world\"}]", "replay_id": 4, "project_id": 10, "id": 4, "chunk_index": 0, "type": "replay_recording_chunk", "org_id": 1, "received":<PHONE_NUMBER>.3337479, "retention_days": 30, "key_id": 123}, {"type": "replay_recording", "replay_id": 4, "replay_recording": {"chunks": 1, "id": 4}, "project_id": 10, "org_id": 1, "received":<PHONE_NUMBER>.333749, "retention_days": 30}]
[{"type": "replay_recording_not_chunked", "replay_id": 5, "org_id": 1, "key_id": 123, "project_id": 10, "received":<PHONE_NUMBER>.333767, "retention_days": 30, "payload": "{\"segment_id\":1}\n[{\"hello\":\"world\"}]"}]
[{"type": "replay_recording_not_chunked", "replay_id": 6, "org_id": 1, "key_id": 123, "project_id": 10, "received":<PHONE_NUMBER>.333802, "retention_days": 30, "payload": "{\"segment_id\":1}\n[{\"hello\":\"world\"}]"}]
[{"type": "replay_recording_not_chunked", "replay_id": 7, "org_id": 1, "key_id": 123, "project_id": 10, "received":<PHONE_NUMBER>.333812, "retention_days": 30, "payload": "{\"segment_id\":1}\n[{\"hello\":\"world\"}]"}]
[{"type": "replay_recording_not_chunked", "replay_id": 8, "org_id": 1, "key_id": 123, "project_id": 10, "received":<PHONE_NUMBER>.3338199, "retention_days": 30, "payload": "{\"segment_id\":1}\n[{\"hello\":\"world\"}]"}]
[{"type": "replay_recording_not_chunked", "replay_id": 9, "org_id": 1, "key_id": 123, "project_id": 10, "received":<PHONE_NUMBER>.3338282, "retention_days": 30, "payload": "{\"segment_id\":1}\n[{\"hello\":\"world\"}]"}]
Flushing !!!
Done!


tail is not terminated when service exits due to a failed start

I just updated to the latest master (as of time of writing) and am tinkering with a few things in the invocation. I've noticed that the tail command is not terminated along with the Factorio server when the server terminates abnormally (eg: missing save file).
I'm unsure if this appears in other situations, but this is where I've observed it.
dmulligan@dmulligan /opt/factorio-init [master]±% sudo service factorio start                                                                                !3658
dmulligan@dmulligan /opt/factorio-init [master]±% sudo service factorio status                                                                                !3659
● factorio.service - LSB: start and stop Factorio server
   Loaded: loaded (/etc/init.d/factorio)
   Active: active (running) since Mon 2016-09-12 16:56:16 EDT; 1s ago
  Process: 5186 ExecStart=/etc/init.d/factorio start (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/factorio.service
           └─5208 tail -f /opt/factorio/bin/x64/../../server.fifo

Sep 12 16:56:16 dmulligan.ca su[5202]: + ??? root:factorio
Sep 12 16:56:16 dmulligan.ca su[5202]: pam_unix(su:session): session opened for user factorio by (uid=0)
Sep 12 16:56:16 dmulligan.ca su[5204]: Successful su for factorio by root
Sep 12 16:56:16 dmulligan.ca su[5204]: + ??? root:factorio
Sep 12 16:56:16 dmulligan.ca su[5204]: pam_unix(su:session): session opened for user factorio by (uid=0)
Sep 12 16:56:16 dmulligan.ca su[5206]: Successful su for factorio by root
Sep 12 16:56:16 dmulligan.ca su[5206]: + ??? root:factorio
Sep 12 16:56:16 dmulligan.ca su[5206]: pam_unix(su:session): session opened for user factorio by (uid=0)
Sep 12 16:56:16 dmulligan.ca factorio[5186]: Started Factorio, please see log for details
Sep 12 16:56:16 dmulligan.ca systemd[1]: Started LSB: start and stop Factorio server.
dmulligan@dmulligan /opt/factorio-init [master]±% sudo service factorio stop                                                                                !3660
dmulligan@dmulligan /opt/factorio-init [master]±% sudo service factorio status                                                                                !3661
● factorio.service - LSB: start and stop Factorio server
   Loaded: loaded (/etc/init.d/factorio)
   Active: inactive (dead)

Sep 12 16:56:16 dmulligan.ca su[5204]: Successful su for factorio by root
Sep 12 16:56:16 dmulligan.ca su[5204]: + ??? root:factorio
Sep 12 16:56:16 dmulligan.ca su[5204]: pam_unix(su:session): session opened for user factorio by (uid=0)
Sep 12 16:56:16 dmulligan.ca su[5206]: Successful su for factorio by root
Sep 12 16:56:16 dmulligan.ca su[5206]: + ??? root:factorio
Sep 12 16:56:16 dmulligan.ca su[5206]: pam_unix(su:session): session opened for user factorio by (uid=0)
Sep 12 16:56:16 dmulligan.ca factorio[5186]: Started Factorio, please see log for details
Sep 12 16:56:16 dmulligan.ca systemd[1]: Started LSB: start and stop Factorio server.
Sep 12 16:56:20 dmulligan.ca systemd[1]: Stopping LSB: start and stop Factorio server...
Sep 12 16:56:20 dmulligan.ca factorio[5264]: No running server.
Sep 12 16:56:20 dmulligan.ca systemd[1]: Stopped LSB: start and stop Factorio server.
dmulligan@dmulligan /opt/factorio-init [master]±% sudo ps ax -F | grep factorio                                                                                !3662
factorio  5208     1  0  1460   708   0 16:56 ?        S      0:00 tail -f /opt/factorio/bin/x64/../../server.fifo
dmullig+  5311  2978  0  3182  2008   0 16:56 pts/0    S+     0:00 grep --color=auto --exclude-dir=.bzr --exclude-dir=CVS --exclude-dir=.git --exclude-dir=.hg --exclude-dir=.svn factorio

You can see that the server is not started successfully (no factorio process is spawned on start) but after stopping, the tail command remains active.

good catch, I'm not sure on the top of my head how to tackle this but I'll give it a think - thnx for reporting this

Just confirmed that tail also doesn't quit when the Factorio server stops after starting normally, so it's not just when the server fails to start.


Update F.js

Handle file addition flag (position 20 on fixed-format F spec) - When in combination with an I in position 17 should be an *input:*output file rather than just *input

Thanks!


Screen Translator

Description of the new feature / enhancement
Tool that allows you to translate any Windows screenshot text.
Scenario when this would be used?
It would be used when someone who is not familiar with a language and wants to quickly translate the text or image from the screenshot taken.
Supporting information
Similar tool: https://github.com/OneMoreGres/ScreenTranslator

/dup #18014


Interface name checks are too strict, esp. for kind: ext-container but also crpd

The interface name checks (added around v0.35) are too strict and are causing our labs to fail deployment. For instance, for the kind: ext-container, the default check applies, which means interfaces must be named ethX. Such a check is unreasonably strict given that it's an ext-container kind (which could be anything).
It is also causing trouble for the crpd kind in our labs, where our interface names are etX. The default check also applies here since the crpd kind does not override the check.
Here's an example lab showing the problem:
name: tmplab

mgmt:
  network: tmp

topology:
  nodes:
    container1:
      kind: ext-container
    container2:
      kind: ext-container

  links:
    - endpoints: ["container1:swp11", "container2:et12"]

Deploying such a lab using v0.34 works fine, but fails using v0.35, because interfaces are not named ethX (the default interface name check).
**Would it be possible to drop this check in a lab via a configuration parameter or something like this? **
For context, this is the default check, i.e. the failing check for ext-container and crpd container kind. I have removed the check in the below patch:
diff --git a/nodes/default_node.go b/nodes/default_node.go
index 2647d154..7882a3c1 100644
--- a/nodes/default_node.go
+++ b/nodes/default_node.go
@@ -175,15 +175,6 @@ func (d *DefaultNode) DeleteNetnsSymlink() error {
 // Checks the name pattern that is common for VM-based nodes. Container-based nodes override this function to implement
 // custom name checks.
 func (d *DefaultNode) CheckInterfaceName() error {
-       // allow ethX interface names
-       // https://regex101.com/r/C3Fhr0/2
-       ifRe := regexp.MustCompile(`eth[1-9][0-9]*$`)
-       for _, e := range d.Config().Endpoints {
-               if !ifRe.MatchString(e.EndpointName) {
-                       return fmt.Errorf("%q interface name %q doesn't match the required pattern. It should be named as ethX, where X is >0", d.Cfg.ShortName, e.EndpointName)
-               }
-       }
-
        return nil
 }

Fully agree!
@hellt changed the implementation in the PR before merging. My view would also be, that in DefaultNode the CheckInterfaceName() should basically be a noop and every Kind that has specific requirements should be able to limit the interface name-space as specifically required.
Lookking up the code I noticed that the DefaultNode CheckInterfaceName function comment mentions that a common behaviour is meant to be an implemented for the VM based nodes.
My suggestion would be to come up with another "abstract" struct that sits between DefaultNode and the actual Kind.  Maybe called VRNode... that aggregates behaviour for the vr based kinds.

If you require a hotfix, just download this build from the PR branch:
https://github.com/srl-labs/containerlab/suites/11305858076/artifacts/580360665

Fixed via #1276 next release will have the fix included.


fix(v2): animate dropdown properly

Motivation
Currently, in Infima we have height transition CSS property, but it won't work unless the element's height is explicitly specified.
This PR sets the dropdown height at click time so that the CSS transition can work as expected.
The desktop implementation looks trickier because we can have nested dropdowns, so the final height can be dynamic (depending on whether the nested dropdown is expanded or collapsed).
Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan
Preview.

Desktop
Mobile

Related PRs
(If this PR adds or changes functionality, please take some time to update the docs at https://github.com/facebook/docusaurus, and link to your PR here.)

What exactly is wrong? I need screenshots or videos because I don't see any issues with transition.

The multi-level collapsing of Guides seem to collapse subcategories first:

Here sometimes the category collapses without anim. Not sure how to reproduce this consistently but it happens maybe 5% or 10% of the time when I click randomly on a category:

The multi-level collapsing of Guides seem to collapse subcategories first:

I don't understand anyway, what is the problem?

Here sometimes the category collapses without anim. Not sure how to reproduce this consistently but it happens maybe 5% or 10% of the time when I click randomly on a category:

Can't reproduce this.
Anyway, I do the animation (transition) with CSS, I only set the height so that the CSS transition is possible :man_shrugging:

The 2nd is harder to reproduce. Sometimes I can't even make it happen 🤪
But the first is easy: when you click on "Guides" while it's expanded, the "Docs" subcategory also collapses, but its collapsing is not animated (Introduction / MD Features / Versioning disappear instantly). Maybe slowing down the animation would make it easier to see.
Is it expected that the subcategory also collapse when a parent collapse? That seems weird to me.

Yes, this is how CSS transition works, I don't see a big issue with that.
However, I did find bug when collapsed back nested dropdowns. I ended up simplifying the code, so the transition should work better now.

let's merge this for now and see if users give us feedbacks


Garbage Collection

We need a garbage collector to automatically remove the following potentially stale items:

Releases + Slugs (these can currently be removed manually with flynn release delete <id>)
Volumes
Jobs (these remain in flynn-host indefinitely and are retrieved every 30s by the scheduler in SyncJobs)

One approach for releases is to only keep the most recent N versions, but as @philiplb mentioned in #1569:

Keeping the N last versions might be troublesome in situations were you deploy N times in a row (shit happens). Now you can't rollback to the version from yesterday.
Proposal: Keep the last N versions and delete the other versions only if they reach a certain, configurable minimum age.

Once we merge #2744, we should have a cron-like component that makes periodic job requests to do things like this.

FYI not cleaning up old jobs lead to a scheduler bug: #3110.
The bug is fixed, but it does seem like wasted effort to be getting the status of thousands of stopped jobs every 30s, especially if they are already marked as stopped in the controller.

A large number of stopped jobs (e.g. 10,000) leads to quite high average bandwidth between hosts as each scheduler fetches ~10MB of jobs from each host every 30s, leading to about 6mbps average.
We should at the very least have a flynn-host command to just delete old jobs from the local state database.

Is there any progress on the command to delete old jobs? We have an app that failed to start over a day or so in our development environment which makes the online log view impossible to open (browser hangs and sometimes outright crashes). It's not a big deal since we can still see the logs with flynn log but it'd be nice to get this fixed at some point.

@mhlz we updated the scheduler to only sync active jobs in #3767 (which prevents a large number of stopped jobs slowing the scheduler down) so removing old jobs is now less of a priority (it is beneficial to keep jobs in the host to help with fixing broken clusters by resurrecting old jobs).

Flynn is unmaintained and our infrastructure will shut down on June 1, 2021. See the README for details.


LHS: reduce layout shift

There is layout shift in the navigation and on the search result page, preventing the LHS to be 100.
https://main--24life--hlxsites.hlx.live/
https://main--24life--hlxsites.hlx.live/search?q=san francisco
Observations:

The logo in the nav seems to push the content
The cards first render without the image, and then get pushed down by the image. We can set a fixed height for the image.

Tips: use Google Chrome to run the Lighthouse report. Then press "View Original Trace" to see each frame of the rendering.
https://web.dev/optimize-cls/

This is taken care via - https://github.com/hlxsites/24life/pull/159


Create a contact info block

Add links to social networks (LinkedIn, Facebook, Instagram), phone number, email, Telegram username, etc.

completed


Contact

Hello, I saw your new crate in the new crates section on crates.io. I also have a crate for working with S3. Maybe we should merge efforts?

Hi @paolobarbolini , sure, It will be better than standalone. I found your lib but it not cover my demand (Presigned Post and Presigned Get). Do you have discord server or chatting room for rusty-s3.

We don't have a chatroom for rusty-s3, but if you'd like to contact me I do have Matrix @paolobarbolini:matrix.org and Discord Paolo Barbolini#4465

Anyway we do support presigned urls. Not presigned POST ATM, but it would be very easy to add https://github.com/paolobarbolini/rusty-s3/blob/main/examples/sign_get.rs

Ah, I see. Sent request on discord.


Can't encode Non-BMP character

I get an error saying
"UnicodeEncodeError: 'UCS-2' codec can't encode character '\U0001f308' in position 0: Non-BMP character not supported in Tk",
when doing a simple print of tweets from my home page.
So, the '\U0001f308' character can't be encoded and the entire code breaks off. I don't have an issue with any other characters. Does anyone know how to fix this?
The '\U0001f308' character is a rainbow, by the way.

Sounds like you're printing non-ASCII to an improperly configured terminal.  This is almost certainly not a bug in tweepy. Run a python script in the same way that just does "print u'\U0001f308'" and you should see the same thing.

`import tweepy
auth = tweepy.OAuthHandler(consumer_key, consumer_secret)
auth.set_access_token(access_token, access_token_secret)
api = tweepy.API(auth)
public_tweets = api.home_timeline()
for tweet in public_tweets:
print(tweet.text.encode('UTF-8').decode('UTF-8'))
`
Try to use this it will encode all the bmp characters to utf-8 and then decode them.

As the error says, Tk does not support characters outside the Basic Multilingual Plane.
Emoji are an example of such characters, so you'll be unable to print that character using Tk.
If you're encountering this issue when using IDLE, Tk is the GUI toolkit that it uses.
This is a limitation of Tk/IDLE, and the solution is simply not to use Tk/IDLE.
This is not an issue with Tweepy.
GitHub issues for this repository should be used to report issues with this library.
They are not a medium for requesting help with Python.


fix(core): respect nullability of wrapped types for ScalarReference's

If one is to use a ScalarReference to get type-safe access to a lazily loaded scalar value it should be possible to encode in the types that the scalar may be null in the database. Currently, ScalarReferences, when de-referenced through .get() or .$ are typed with "NonNullable" variants of their wrapped types. That non-nullability is not reflected at runtime, which opens up code that perfectly type-checks to runtime exceptions because of null reference accesses. This is demonstrated in this reproduction: https://github.com/ropbastos/mikro-orm-reproduction
Briefly linking the "fixed" version of the library with my companies project I didn't see any types that looked wrong, and all tests still pass, so I'm creating this PR. However, I'm aware the NonNullable helpers are pretty explicit about their intent 😅. I'm not sure what I'm trying to do makes sense/why were they added in the first place, but in the off-chance that they are there by mistake (or they ceased to make sense), I've already done the small work of removing them 🙏
Here is a discussion I opened when I first encountered an error of the type represented in the reproduction repository: https://github.com/mikro-orm/mikro-orm/discussions/5711

Looks good, can you also mention this in the docs?
https://mikro-orm.io/docs/defining-entities#scalarreference-wrapper

Looks good, can you also mention this in the docs?
https://mikro-orm.io/docs/defining-entities#scalarreference-wrapper

Sure! Will be free in couple minutes, 1 hour tops, then I'll edit the docs to try to dispel what confused me :)


(BKR-76) created first pre-suite acceptance tests

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/763/
Test FAILed.

failures don't appear related, but transient.  Re-running tests

@puppetlabs-jenkins retest this please

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/765/
Test PASSed.

Just going to wait here on having the backend smoketest set up to exercise this code.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/775/
Test PASSed.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/779/
Test PASSed.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/820/
Test FAILed.

failures unrelated, but this is waiting on BKR-207 work.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/822/
Test PASSed.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/823/
Test PASSed.


Add BigQuery Spring Integration File Message Handler

This adds a Spring Integration MessageHandler implementation for data files for BigQuery load operations. This is the outbound channel adapter for loading data files into big query.
Contributes to #1764.

And general question: what is wrong with SpEL expressions suggestion?

Nothing wrong with it - however I thought it would just add some unneeded complexity as I imagined the dataset name and table names would just be static strings; these are the datasets/tables that the user loads their data into. But if the static assumption is incorrect then I will add SpEL.

But if the static assumption is incorrect then I will add SpEL.

It's definitely not correct.
See MongoDbStoringMessageHandler and its collectionNameExpression. Or RedisStoreWritingMessageHandler and its keyExpression.
BTW, default might be really expressed as values from headers, meanwhile user-defined static values also can be expressed as expressions: ValueExpression or LiteralExpression.
However this job can be done in the separate PR. What you have so far is OK to go.

But if the static assumption is incorrect then I will add SpEL.

It's definitely not correct.
See MongoDbStoringMessageHandler and its collectionNameExpression. Or RedisStoreWritingMessageHandler and its keyExpression.
BTW, default might be really expressed as values from headers, meanwhile user-defined static values also can be expressed as expressions: ValueExpression or LiteralExpression.
However this job can be done in the separate PR. What you have so far is OK to go.

In the latest commit I added SpEL expressions for the table name and dataset name. Also added support for the sync option; the handler now has polling and will return listenableFuture on completion of the load job.


Adding Host warning message where host is used in examples

Adding the warning about Host behavior wherever host is used, and adding further clarification about what changes are made to the cluster.
I encountered a user that was using Host.requestPolicy which modified the requestPolicy for the entire cluster for a user. They did not understand that this change was being applied outside of the Host in which they applied the configuration.
The source of the error with requestPolicy behavior was not immediately apparent until support asked the user if they had
applied other hosts with a different requestPolicy.
The docs state in the warning from this PR that only one requestPolicy can be applied to an Ambassador instance, and that all Hosts should share the same requestPolicy configuration.
This is expected behavior; however, we felt that it was a difficult issue for a user to figure out on their own without the assistance of support.  The purpose of this PR is to add clarity to the warning statement, describe in detail what changes are being made to the user's configuration, and copy the warning to other pages that make use of the Host CRD so that users can be aware of changes that they are making to the configuration of their cluster.
There is an issue  that further addresses the behavior described above.

Pushed a new commit to this branch to remove descriptions of the alphabetical behavior as well as change Ambassador to Edge Stack.


Allow psr/log v2 and v3

Thanks @carusogabriel

tests are failing when using psr/log@^3
I reverted possibility to use v3 - #321
@carusogabriel , do you want to work on v3 support?
(also a heads up, unfortunately Travis integration got broken - we may want first to move to GitHub Actions - #320 )

@keradus What needs to be done for v3 support?

@WyriHaximus , update locally to v3 and see the failing tests
(also , CI is back now, so we would detect it next time PR is raised as well ;) )


[Roadmap] Q3S2 (25th July - 2nd Aug)

Context & Strategic Focus
Open Collective builds our platform in 6-week sprints, with a week-long break every two sprints to review our strategic objectives:

#5486
#5487
#5488

If you'd like to know more about how we work check out this document and this video explainer.
Prioritisation
Every six weeks we invite members of the team to share ideas that are high impact and aligned with the strategic objectives. We discuss these ideas together as a team prior to running a final prioritisation call where we commit to projects for the next sprint.
We also run a poll to inform the process you can see the results here:

Roadmap and tracking
Based on this discussion we decided to prioritise the following issues.  You can follow progress on each of the issues above using our project board.
Large Projects (4 weeks)

#5704

Small Projects (4 weeks)

#5195
#5681

We proposed that we continue to work on the design for the snowboarding process, scoping with engineering as needed.

#3438

Papercuts (half a day, pick up as available)

#5426
#5435
#5407
#5171
#5341

We noticed a number of papercut issues were about virtual cards, however with @kewitz out for two weeks this sprint we thought that might not be the best focus, instead we could consider clearing some of the previously identified papercuts around expense workflows:

#4991
#3629
#4667
#5020
#4990

Checklist
This sprint is being facilitated by  @piamancini.
After prioritization meeting:

[x] Create/review Projects issue (basic skeleton is fine) for each prioritized project if it's not already created.
[ ] Make sure Engineering and Design people assigned to projects.
[ ] Create sprint meta-issue

[ ] Pin the issue.
[ ] Update GitHub homepage

[ ] Communicate prioritization to a wide audience:

[ ] internally: OC, OSC, OCF teams
[ ] externally: Slack General channel

scoping week (first week)

[ ] Make sure that scoping is happening, that team members speak to each others, are meeting each others
[ ] Make sure that scoping is being documented
[ ] Make sure that scoping are properly written and can be presented on Friday

On Friday after demos:

[ ] Communicate specifications to a wider audience and ask for final feedback

clearing some of the previously identified papercuts around expense workflows

I can't find the issue for this, but previously we identified that hiding the form fields until the user started typing the title was causing confusion, and that we should show the form fields from the start. Is that going to be addressed in here somewhere?


remove defunct markdown linting variable

Addresses https://github.com/knative/hack/issues/200
Removes a dead variable in the presubmit tests related to markdown linting

/approve
/lgtm


Installing in Blank Xamarin Forms project

Hi there,
I am attempting to install this package using the nuget package manager inside Visual Studio 2015.
However when I install I get the following error message:
Could not install package 'ThriveGmbH.BottomNavigationBar.XF 1.0.1'. You are trying to install this package into a project that targets '.NETPortable,Version=v4.5,Profile=Profile111', but the package does not contain any assembly references or content files that are compatible with that framework. For more information, contact the package author.
Any help please?

Done some more digging and it seems similar to issue 19. Basically I can install the package for the .Droid part of the solution but not for the main general part of the solution. Could someone please check that the nuget package is targeting the right PCL profile? Thanks.

While this does not fix the issue, as a workaround I have been able to build the BottomNavigationBarXF solution myself and then manually included the references in my App solution.

The same issue here!

Fixed by ice-j with PR #22 .


Use watching instead of polling to get update from Consul catalog

Using watching can significantly reduce the CPU resource usage and the number of TIME_WAIT socket introduced by polling
Change-Id: I966690ecfaa79364997e94e81559acaab46d6a9d
Signed-off-by: Huabing Zhao<EMAIL_ADDRESS>Please provide a description for what this PR is for.
And to help us figure out who should review this PR, please
put an X in all the areas that this PR affects.
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ X] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

@zhaohuabing: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

lint_istio
a25b5493511df4f599fdfe5ec853c02cccba9bde
link
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@zhaohuabing: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

lint_istio
a25b5493511df4f599fdfe5ec853c02cccba9bde
link
/test lint_istio

integ-security-k8s-tests_istio
a25b5493511df4f599fdfe5ec853c02cccba9bde
link
/test integ-security-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@zhaohuabing: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
a25b5493511df4f599fdfe5ec853c02cccba9bde
link
/test integ-security-k8s-tests_istio

lint_istio
a25b5493511df4f599fdfe5ec853c02cccba9bde
link
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@zhaohuabing: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

lint_istio
1842e95deee503958b1569e1db615e9bceff24da
link
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

it's no a good practice to reply on a ticket that is closed two years.
In latest version, istio support this scenario with mcp-over-xds.

it's no a good practice to reply on a ticket that is closed two years.
In latest version, istio support this scenario with mcp-over-xds.

Do you mean that MCP replaces the above solution that adapts to different centers? I thought MCP was abandoned, and was it alive?

MCP was abandoned, the new solution called mcp-over-xds.
IIRC, nacos supported this from v2.0.1, aeraki-mesh also use it.

@zirain https://github.com/aeraki-mesh/dubbo2istio


There are differences in depth values of cameras with the same parameters in different scenes.

Hi,
I'm a student and I'm trying to use MuJoCo for robot manipulation based on RL methods.
In my simulation, a camera is placed into a simulated sensor like the following.

Firstly, I constructed the sensor without any other objects in the scene. Then, I obtained the depth data of the camera,  which is proceeded to the next step.  Here is the code I obtain the depth value.
    viewer.render(gel_width,gel_height,camera_id=0)
    depth = viewer.read_pixels(gel_width, gel_height, depth=True)[1].copy()

After completing the debugging of relevant functions, I added the sensor to a simulated robot arm.
However, I found that whether there is a robot that will change the depth values of the camera. What's the problem?
Here is a model which explains my question:

minimal XML
<?xml version="1.0" encoding="utf-8"?>
<mujoco>
	<compiler angle="radian"  coordinate="local" meshdir="../stls/gel" ></compiler>
	<option timestep="0.002">
		<flag warmstart="enable"></flag>
	</option>
    <default>
        <light castshadow="false" diffuse="1 1 1" />
        <camera fovy="60" />
        <motor ctrllimited="true" ctrlrange="-0.04 0.04"/>
    </default>

    <visual>
        <rgba connect="1 0.2 1 1" joint="0.2 0.6 0.8 1"/>
        <map fogstart="3" fogend="5"/>
        <quality shadowsize="2048"/>
    </visual>
    <option gravity="0 0 0" iterations="100"/>

    <custom>
        <numeric name="N_GRIPPER_JOINTS" data="0" />
    </custom>

    <size nconmax="2000" njmax="10000" nstack="500000"/>

	<include file="shared.xml"></include>

	<worldbody>

		<geom name="floor0" pos="0 0 0" size="0.85 0.7 1" type="plane" contype="32" conaffinity="32" condim="3" material="floor_mat"></geom>
		<body name="floor0" pos="0 0 0">
			<site name="target0" pos="0 0 0.5" size="0.02 0.02 0.02" rgba="1 0 0 0.0" type="sphere"></site>
		</body>

                <include file="robot_digit.xml"/>

		<include file="digit_sensor.xml"></include>

		<body name="object1" pos="0.0 0.0 0.1">
            <site name="object1:site" pos="0 0 0" rgba="0 1 0 .1" size="0.02 0.02 0.02"/>
            <joint name="object:joint" type="free" damping=".001" limited="true"></joint>
            <geom name="object1" type="box" size=".02 .02 .02" contype="1" conaffinity="32" condim="3" rgba="1 1 0 1"></geom>
        </body>

        <light directional="true" ambient="0.2 0.2 0.2" diffuse="0.8 0.8 0.8" specular="0.3 0.3 0.3" castshadow="false" pos="0 0 4" dir="0 0 -1" name="light0"></light>
	</worldbody>
    <!-- Camera settings -->
    <visual>
        <!-- allows the camera to fit into smaller spaces without clipping through -->
        <map znear="0.001" zfar="1000"/>
    </visual>

</mujoco>

znear and zfar are scaled by the model extent
This is documented here, but should be added to the XML reference too.


Customer polling service should wait for payments to complete before responding to expiry

Right now, the customer polling service does not check whether there are any payments in progress before processing an expiry post by the merchant. This could lead to a dumb loss of funds if they post a revocation lock and immediately reveal the secret to the merchant (in the payment).
We could wait for the database to enter the Active state, but if a payment was stopped partway through, this might not ever happen. We could wait for a timeout to complete first? Or we can do something more complex to check whether there are any threads executing at the time, or watch a timeout to see how long it has been since the state last changed.

@yaymukund and I discussed this yesterday. Planned outcome is the following:

add a PendingPay status that a channel enters as soon as it starts a payment
add a FailedPay status that a channel enters if there's a cryptographic failure in a payment
make the polling service ignore the expiry update if the status is PendingPay, Started, or Locked

I am not completely sure about the last one---at some point, there will be a queue of operations that will make sure that a constant stream of payments can't prevent a party from plowing through the entire expiry period, but that depends the larger customerd update that Mukund is working on. They might have a better temporary solution for how not to start an expiry during a pay session.

This was closed by #342


Calling composite query from javascript agent

Describe the issue
I'm experiencing issues with the composite query functionality using the @dfinity/agent library in my Node.js application. When attempting to execute composite queries, the process gets stuck without failing or returning any results. Despite efforts, I couldn't find relevant documentation regarding composite queries for @dfinity/agent. While building the agent using the IDL of my canister, which includes a composite query method, I'm unsure if any additional specifications are required for composite queries compared to regular update or query calls. is there any limitation on composite query call from javascript side?Could someone provide guidance or direct me to appropriate documentation regarding composite queries with @dfinity/agent?
https://www.npmjs.com/package/@dfinity/agent?activeTab=readme

Sorry for the delay here - I haven't been able to reproduce this myself. Labeling composite_query in the IDL works as intended on mainnet and during local development in my own experience.
I'd be happy to take a look if you have reproducing code


this.tables.mapToClass is not a function: only when table is named "tables", works with other names

Here is where the db is initiated:
import Dexie, { DexieTable } from 'dexie'
import { v1 as uuidv1 } from 'uuid'

export class Table implements ITable {
  id: string
  project_id?: string
  parent_id?: string
  rel_type?: string
  name?: string
  label?: string
  single_label?: string
  label_fields?: string[]
  label_fields_separator?: string
  sort?: number
  option_type?: string
  client_rev_at?: Date
  client_rev_by?: string
  server_rev_at?: Date
  deleted?: boolean

  constructor(
    id?: string,
    project_id?: string,
    parent_id?: string,
    rel_type?: string,
    name?: string,
    label?: string,
    single_label?: string,
    label_fields?: string[],
    label_fields_separator?: string,
    sort?: number,
    option_type?: string,
    client_rev_at?: Date,
    client_rev_by?: string,
    server_rev_at?: Date,
    deleted?: boolean,
  ) {
    this.id = id ?? uuidv1()
    if (project_id) this.project_id = project_id
    if (parent_id) this.parent_id = parent_id
    if (rel_type) this.rel_type = rel_type
    if (name) this.name = name
    if (label) this.label = label
    if (single_label) this.single_label = single_label
    if (label_fields) this.label_fields = label_fields
    if (label_fields_separator)
      this.label_fields_separator = label_fields_separator
    if (sort) this.sort = sort
    if (option_type) this.option_type = option_type
    if (client_rev_at) this.client_rev_at = client_rev_at
    if (client_rev_by) this.client_rev_by = client_rev_by
    if (server_rev_at) this.server_rev_at = server_rev_at
    if (deleted) this.deleted = deleted
  }
}

export class MySubClassedDexie extends Dexie {
  tables!: DexieTable<Table, string>

  constructor() {
    super('capturing')
    this.version(1).stores({
      tables:
        'id, label, sort, project_id, parent_id, rel_type, option_type, server_rev_at',
    })
    this.tables.mapToClass(Table)
  }
}

export const db = new MySubClassedDexie()

(I removed all other tables to simplify)
This throws an error:
TypeError: this.tables.mapToClass is not a function
    at new MySubClassedDexie (webpack-internal:///./modules/initiateDb.ts:280:21)
    at eval (webpack-internal:///./modules/initiateDb.ts:286:12)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)

When tables is renamed to anything else, like ctables, it works as expected.
What could be wrong?
dexie is used in v3.2.1.

Dexie.tables is an existing property on Dexie instances so there's a name conflict as you name your table "tables". Either name your table differently, or use db.table('tables') to access it.

Thanks. And: Thanks so much for this GREAT tool


How to delete a message

I want to add functionality to delete a chat and  but don't want to delete chat using REST API .
So can you tell, how can i do that ?

Use the functions described in the API docs:

Messages.removeMessage
Channel.destroy


Add support for lottie-ios version 3.4.0

Hello guys, thanks for this PR 🙏🏻
I was wondering if you plan to release a 5.1.4 of this patch on NPM any time soon.
Thanks again, have a nice day !


Can't create agent when no plugins are specified

When no plugins are specified in the AgentConfigs, the following error occurs in the AgentAction controller:
2023-02-24T18:59:46Z	ERROR	Reconciler error	{"controller": "agentaction", "controllerGroup": "getporter.org", "controllerKind": "AgentAction", "AgentAction": {"name":"default","namespace":"ginkgo-tests-94672"}, "namespace": "ginkgo-tests-94672", "name": "default", "reconcileID": "9362a146-b03c-4f99-b42e-83013d9b34aa", "error": "error creating Porter agent job: Job.batch \"default-ktb6j\" is invalid: [spec.template.spec.volumes[3].persistentVolumeClaim.claimName: Required value, spec.template.spec.containers[0].volumeMounts[3].name: Not found: \"porter-plugins\"]", "errorVerbose": "Job.batch \"default-ktb6j\" is invalid: [spec.template.spec.volumes[3].persistentVolumeClaim.claimName: Required value, spec.template.spec.containers[0].volumeMounts[3].name: Not found: \"porter-plugins\"]\nerror creating Porter agent job\nget.porter.sh/operator/controllers.(*AgentActionReconciler).createAgentJob\n\t/workspace/controllers/agentaction_controller.go:468\nget.porter.sh/operator/controllers.(*AgentActionReconciler).runPorter\n\t/workspace/controllers/agentaction_controller.go:214\nget.porter.sh/operator/controllers.(*AgentActionReconciler).Reconcile\n\t/workspace/controllers/agentaction_controller.go:95\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Reconcile\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.14.4/pkg/internal/controller/controller.go:122\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.14.4/pkg/internal/controller/controller.go:323\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.14.4/pkg/internal/controller/controller.go:274\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.14.4/pkg/internal/controller/controller.go:235\nruntime.goexit\n\t/usr/local/go/src/runtime/asm_amd64.s:1594"}
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler
	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.14.4/pkg/internal/controller/controller.go:329
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem
	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.14.4/pkg/internal/controller/controller.go:274
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2
	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.14.4/pkg/internal/controller/controller.go:235

The problem is that it unconditionally looks up the name of the porter-plugins volume to mount into the agent and applies it to the job spec. When no plugins are specified, we don't need to mount a volume and the volume name is "".
I tried modifying the operator code to skip mounting when the volume name is empty, and that fixed the problem but I'm wondering if it should always mount the k8s plugin when none are specified? I think this may be a bug in our defaulting and the porter agent shouldn't run without plugins.

I'm going to fix this issue with the fix mentioned in the OP but @VinozzZ when you get a chance can you think about if in this case we should have defaulted to the k8s plugin? I can create a follow-up issue for that if you think that's the correct behavior.

Hmmm, this is not what I expected when no plugins are specified, the agent config controller should not have created a agent action? or is that still a possibility?

This is a problem in the AgentAction controller. When it creates the job for the agent action, the resolved agent config is coming back with no plugins, so the plugin pvc to mount into the agent is empty. If you see the PR, you can see where it's happening. I kind of expected that when the agent config is resolved, that the plugins would always be populated with at least the k8s plugin but instead it's empty.

Ohhh, duh, I actually remember adding the check locally lol
I think we landed on not having a default plugin set due to some other reason. I think it's documented in one of the issues

I'll go with the fix in #166 and if we decide later that we need the default plugin, we can update it. 👍


Azdo CI not running against master

NOTE: This needs to be done in Stabilization sprint

Dup of #4477


refactored the resource docs. also added a new helper that builds code tabs out of a directory on disk.

Are you seeing that happen? Any specific place?

ERRO[2018-10-06T18:39:24+02:00] docs/resources/_example/standard/templates/widgets/show.html: line 6: widgetsPath: unknown identifier duration=6.186841ms human_size="0 B" method=GET params="{\"lang\":[\"en\"],\"name\":[\"resources/_example/standard/templates/widgets/show/\"]}" path=/en/docs/resources/_example/standard/templates/widgets/show/ render="368.942µs" request_id=nqyCTlbmmU-oNblZnaIMI size=0 status=0
could not index /en/docs/resources/_example/standard/templates/widgets/show

Looks like the indexer is trying to index more than it should. :)

@stanislas-m indexer fixed, but my examples seem to be rendering fine.


Holes instead of random defaults

For example have a ("required") hole as the target of a call expression instead of the blank identifier which is currently inserted there.
This is also relevant for creating new children (using "ctrl-right"). We could insert holes as the children instead of random defaults. An alternative approach here would be to force the user to always choose a type when creating the node.

Solved in a hacky way: https://github.com/tehwalris/forest/commit/b4ed9441e0eb48f798204f3a8837a126a768e922


VHD utilities for Go not for USGov, China, Germany

Updating note to not waste people's time unless they are on supported cloud.

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot

@pburkholder : Thanks for your contribution to the Azure documentation! The author, @iainfoulds, has been notified to review your proposed change.

Sorry for the delay in responding, and for the issue you experienced.
I've been going back and forth with our PMs in the Azure government space on this. They are working on wider changes both within the platform for support issues like this, and within the doc set to improve areas where the govt clouds aren't quite at parity. As they already have plans for improvements here, I'd rather have this one PR closed so there's no conflicts with what they have planned. Ideally, the govt clouds will have feature parity so as to avoid these issues.
Apologies again for the inconveniences.
PR reviewers - #please-close


Both unmanaged and managed package installation failed in sandbox

Apex Rollup summer 23 Updates Release
Problem:

Dependent class is invalid and needs recompilation:
Class RollupEvaluator : Dependent class is invalid and needs recompilation:
Class RollupDateLiteral : Invalid date
Rollup: Dependent class is invalid and needs recompilation:
Class RollupEvaluator : Dependent class is invalid and needs recompilation:
Class RollupDateLiteral : Invalid date

Dependent class is invalid and needs recompilation:
Class Rollup : Dependent class is invalid and needs recompilation:
Class RollupEvaluator : Dependent class is invalid and needs recompilation:
Class RollupDateLiteral : Invalid date
RollupAsyncProcessor: Dependent class is invalid and needs recompilation:
Class Rollup : Dependent class is invalid and needs recompilation:
Class RollupEvaluator : Dependent class is invalid and needs recompilation:
Class RollupDateLiteral : Invalid date

Dependent class is invalid and needs recompilation:
Class RollupFieldInitializer : Dependent class is invalid and needs recompilation:
Class Rollup : Dependent class is invalid and needs recompilation:
Class RollupEvaluator : Dependent class is invalid and needs recompilation:
Class RollupDateLiteral : Invalid date
RollupCalcItemReplacer: Dependent class is invalid and needs recompilation:
Class RollupFieldInitializer : Dependent class is invalid and needs recompilation:
Class Rollup : Dependent class is invalid and needs recompilation:
Class RollupEvaluator : Dependent class is invalid and needs recompilation:
Class RollupDateLiteral : Invalid date

Dependent class is invalid and needs recompilation:
Class Rollup : Dependent class is invalid and needs recompilation:
Class RollupEvaluator : Dependent class is invalid and needs recompilation:
Class RollupDateLiteral : Invalid date
RollupCalcItemSorter: Dependent class is invalid and needs recompilation:
Class Rollup : Dependent class is invalid and needs recompilation:
Class RollupEvaluator : Dependent class is invalid and needs recompilation:
Class RollupDateLiteral : Invalid date

Dependent class is invalid and needs recompilation:
Class RollupCalcItemSorter : Dependent class is invalid and needs recompilation:
Class Rollup : Dependent class is invalid and needs recompilation:
Class RollupEvaluator : Dependent class is invalid and needs recompilation:
Class RollupDateLiteral : Invalid date
RollupCalculator: Dependent class is invalid and needs recompilation:
Class RollupCalcItemSorter : Dependent class is invalid and needs recompilation:
Class Rollup : Dependent class is invalid and needs recompilation:
Class RollupEvaluator : Dependent class is invalid and needs recompilation:
Class RollupDateLiteral : Invalid date

Dependent class is invalid and needs recompilation:
Class RollupCalcItemReplacer : Dependent class is invalid and needs recompilation:
Class RollupFieldInitializer : Dependent class is invalid and needs recompilation:
Class Rollup : Dependent class is invalid and needs recompilation:
Class RollupEvaluator : Dependent class is invalid and needs recompilation:
Class RollupDateLiteral : Invalid date
RollupCurrencyInfo: Dependent class is invalid and needs recompilation:
Class RollupCalcItemReplacer : Dependent class is invalid and needs recompilation:
Class RollupFieldInitializer : Dependent class is invalid and needs recompilation:
Class Rollup : Dependent class is invalid and needs recompilation:
Class RollupEvaluator : Dependent class is invalid and needs recompilation:
Class RollupDateLiteral : Invalid date

Invalid date
RollupDateLiteral: Invalid date

Dependent class is invalid and needs recompilation:
Class RollupAsyncProcessor : Dependent class is invalid and needs recompilation:
Class Rollup : Dependent class is invalid and needs recompilation:
Class RollupEvaluator : Dependent class is invalid and needs recompilation:
Class RollupDateLiteral : Invalid date
RollupDeferredFullRecalcProcessor: Dependent class is invalid and needs recompilation:
Class RollupAsyncProcessor : Dependent class is invalid and needs recompilation:
Class Rollup : Dependent class is invalid and needs recompilation:
Class RollupEvaluator : Dependent class is invalid and needs recompilation:
Class RollupDateLiteral : Invalid date

Dependent class is invalid and needs recompilation:
Class RollupDateLiteral : Invalid date
RollupEvaluator: Dependent class is invalid and needs recompilation:
Class RollupDateLiteral : Invalid date

Dependent class is invalid and needs recompilation:
Class Rollup : Dependent class is invalid and needs recompilation:
Class RollupEvaluator : Dependent class is invalid and needs recompilation:
Class RollupDateLiteral : Invalid date
RollupFieldInitializer: Dependent class is invalid and needs recompilation:
Class Rollup : Dependent class is invalid and needs recompilation:
Class RollupEvaluator : Dependent class is invalid and needs recompilation:
Class RollupDateLiteral : Invalid date

Dependent class is invalid and needs recompilation:
Class RollupLogger : Dependent class is invalid and needs recompilation:
Class Rollup : Dependent class is invalid and needs recompilation:
Class RollupEvaluator : Dependent class is invalid and needs recompilation:
Class RollupDateLiteral : Invalid date
RollupFinalizer: Dependent class is invalid and needs recompilation:
Class RollupLogger : Dependent class is invalid and needs recompilation:
Class Rollup : Dependent class is invalid and needs recompilation:
Class RollupEvaluator : Dependent class is invalid and needs recompilation:
Class RollupDateLiteral : Invalid date

Dependent class is invalid and needs recompilation:
Class Rollup : Dependent class is invalid and needs recompilation:
Class RollupEvaluator : Dependent class is invalid and needs recompilation:
Class RollupDateLiteral : Invalid date
RollupFlowBulkProcessor: Dependent class is invalid and needs recompilation:
Class Rollup : Dependent class is invalid and needs recompilation:
Class RollupEvaluator : Dependent class is invalid and needs recompilation:
Class RollupDateLiteral : Invalid date

Dependent class is invalid and needs recompilation:
Class Rollup : Dependent class is invalid and needs recompilation:
Class RollupEvaluator : Dependent class is invalid and needs recompilation:
Class RollupDateLiteral : Invalid date
RollupFlowBulkSaver: Dependent class is invalid and needs recompilation:
Class Rollup : Dependent class is invalid and needs recompilation:
Class RollupEvaluator : Dependent class is invalid and needs recompilation:
Class RollupDateLiteral : Invalid date

Dependent class is invalid and needs recompilation:
Class Rollup : Dependent class is invalid and needs recompilation:
Class RollupEvaluator : Dependent class is invalid and needs recompilation:
Class RollupDateLiteral : Invalid date
RollupFlowFullRecalcDispatcher: Dependent class is invalid and needs recompilation:
Class Rollup : Dependent class is invalid and needs recompilation:
Class RollupEvaluator : Dependent class is invalid and needs recompilation:
Class RollupDateLiteral : Invalid date

Dependent class is invalid and needs recompilation:
Class RollupAsyncProcessor : Dependent class is invalid and needs recompilation:
Class Rollup : Dependent class is invalid and needs recompilation:
Class RollupEvaluator : Dependent class is invalid and needs recompilation:
Class RollupDateLiteral : Invalid date
RollupFullBatchRecalculator: Dependent class is invalid and needs recompilation:
Class RollupAsyncProcessor : Dependent class is invalid and needs recompilation:
Class Rollup : Dependent class is invalid and needs recompilation:
Class RollupEvaluator : Dependent class is invalid and needs recompilation:
Class RollupDateLiteral : Invalid date

Dependent class is invalid and needs recompilation:
Class RollupAsyncProcessor : Dependent class is invalid and needs recompilation:
Class Rollup : Dependent class is invalid and needs recompilation:
Class RollupEvaluator : Dependent class is invalid and needs recompilation:
Class RollupDateLiteral : Invalid date
RollupFullRecalcProcessor: Dependent class is invalid and needs recompilation:
Class RollupAsyncProcessor : Dependent class is invalid and needs recompilation:
Class Rollup : Dependent class is invalid and needs recompilation:
Class RollupEvaluator : Dependent class is invalid and needs recompilation:
Class RollupDateLiteral : Invalid date

Dependent class is invalid and needs recompilation:
Class Rollup : Dependent class is invalid and needs recompilation:
Class RollupEvaluator : Dependent class is invalid and needs recompilation:
Class RollupDateLiteral : Invalid date
RollupLogger: Dependent class is invalid and needs recompilation:
Class Rollup : Dependent class is invalid and needs recompilation:
Class RollupEvaluator : Dependent class is invalid and needs recompilation:
Class RollupDateLiteral : Invalid date

Dependent class is invalid and needs recompilation:
Class RollupRepository : Dependent class is invalid and needs recompilation:
Class RollupQueryBuilder : Dependent class is invalid and needs recompilation:
Class RollupCurrencyInfo : Dependent class is invalid and needs recompilation:
Class RollupCalcItemReplacer : Dependent class is invalid and needs recompilation:
Class RollupFieldInitializer : Dependent class is invalid and needs recompilation:
Class Rollup : Dependent class is invalid and needs recompilation:
Class RollupEvaluator : Dependent class is invalid and needs recompilation:
Class RollupDateLiteral : Invalid date
RollupMetaPicklists: Dependent class is invalid and needs recompilation:
Class RollupRepository : Dependent class is invalid and needs recompilation:
Class RollupQueryBuilder : Dependent class is invalid and needs recompilation:
Class RollupCurrencyInfo : Dependent class is invalid and needs recompilation:
Class RollupCalcItemReplacer : Dependent class is invalid and needs recompilation:
Class RollupFieldInitializer : Dependent class is invalid and needs recompilation:
Class Rollup : Dependent class is invalid and needs recompilation:
Class RollupEvaluator : Dependent class is invalid and needs recompilation:
Class RollupDateLiteral : Invalid date

Dependent class is invalid and needs recompilation:
Class RollupFullBatchRecalculator : Dependent class is invalid and needs recompilation:
Class RollupAsyncProcessor : Dependent class is invalid and needs recompilation:
Class Rollup : Dependent class is invalid and needs recompilation:
Class RollupEvaluator : Dependent class is invalid and needs recompilation:
Class RollupDateLiteral : Invalid date
RollupParentResetProcessor: Dependent class is invalid and needs recompilation:
Class RollupFullBatchRecalculator : Dependent class is invalid and needs recompilation:
Class RollupAsyncProcessor : Dependent class is invalid and needs recompilation:
Class Rollup : Dependent class is invalid and needs recompilation:
Class RollupEvaluator : Dependent class is invalid and needs recompilation:
Class RollupDateLiteral : Invalid date

Dependent class is invalid and needs recompilation:
Class RollupCurrencyInfo : Dependent class is invalid and needs recompilation:
Class RollupCalcItemReplacer : Dependent class is invalid and needs recompilation:
Class RollupFieldInitializer : Dependent class is invalid and needs recompilation:
Class Rollup : Dependent class is invalid and needs recompilation:
Class RollupEvaluator : Dependent class is invalid and needs recompilation:
Class RollupDateLiteral : Invalid date
RollupQueryBuilder: Dependent class is invalid and needs recompilation:
Class RollupCurrencyInfo : Dependent class is invalid and needs recompilation:
Class RollupCalcItemReplacer : Dependent class is invalid and needs recompilation:
Class RollupFieldInitializer : Dependent class is invalid and needs recompilation:
Class Rollup : Dependent class is invalid and needs recompilation:
Class RollupEvaluator : Dependent class is invalid and needs recompilation:
Class RollupDateLiteral : Invalid date

Dependent class is invalid and needs recompilation:
Class RollupEvaluator : Dependent class is invalid and needs recompilation:
Class RollupDateLiteral : Invalid date
RollupRecursionItem: Dependent class is invalid and needs recompilation:
Class RollupEvaluator : Dependent class is invalid and needs recompilation:
Class RollupDateLiteral : Invalid date

Dependent class is invalid and needs recompilation:
Class RollupQueryBuilder : Dependent class is invalid and needs recompilation:
Class RollupCurrencyInfo : Dependent class is invalid and needs recompilation:
Class RollupCalcItemReplacer : Dependent class is invalid and needs recompilation:
Class RollupFieldInitializer : Dependent class is invalid and needs recompilation:
Class Rollup : Dependent class is invalid and needs recompilation:
Class RollupEvaluator : Dependent class is invalid and needs recompilation:
Class RollupDateLiteral : Invalid date
RollupRelationshipFieldFinder: Dependent class is invalid and needs recompilation:
Class RollupQueryBuilder : Dependent class is invalid and needs recompilation:
Class RollupCurrencyInfo : Dependent class is invalid and needs recompilation:
Class RollupCalcItemReplacer : Dependent class is invalid and needs recompilation:
Class RollupFieldInitializer : Dependent class is invalid and needs recompilation:
Class Rollup : Dependent class is invalid and needs recompilation:
Class RollupEvaluator : Dependent class is invalid and needs recompilation:
Class RollupDateLiteral : Invalid date

Dependent class is invalid and needs recompilation:
Class RollupQueryBuilder : Dependent class is invalid and needs recompilation:
Class RollupCurrencyInfo : Dependent class is invalid and needs recompilation:
Class RollupCalcItemReplacer : Dependent class is invalid and needs recompilation:
Class RollupFieldInitializer : Dependent class is invalid and needs recompilation:
Class Rollup : Dependent class is invalid and needs recompilation:
Class RollupEvaluator : Dependent class is invalid and needs recompilation:
Class RollupDateLiteral : Invalid date
RollupRepository: Dependent class is invalid and needs recompilation:
Class RollupQueryBuilder : Dependent class is invalid and needs recompilation:
Class RollupCurrencyInfo : Dependent class is invalid and needs recompilation:
Class RollupCalcItemReplacer : Dependent class is invalid and needs recompilation:
Class RollupFieldInitializer : Dependent class is invalid and needs recompilation:
Class Rollup : Dependent class is invalid and needs recompilation:
Class RollupEvaluator : Dependent class is invalid and needs recompilation:
Class RollupDateLiteral : Invalid date

Dependent class is invalid and needs recompilation:
Class RollupCurrencyInfo : Dependent class is invalid and needs recompilation:
Class RollupCalcItemReplacer : Dependent class is invalid and needs recompilation:
Class RollupFieldInitializer : Dependent class is invalid and needs recompilation:
Class Rollup : Dependent class is invalid and needs recompilation:
Class RollupEvaluator : Dependent class is invalid and needs recompilation:
Class RollupDateLiteral : Invalid date
RollupSObjectUpdater: Dependent class is invalid and needs recompilation:
Class RollupCurrencyInfo : Dependent class is invalid and needs recompilation:
Class RollupCalcItemReplacer : Dependent class is invalid and needs recompilation:
Class RollupFieldInitializer : Dependent class is invalid and needs recompilation:
Class Rollup : Dependent class is invalid and needs recompilation:
Class RollupEvaluator : Dependent class is invalid and needs recompilation:
Class RollupDateLiteral : Invalid date

Dependent class is invalid and needs recompilation:
Class Rollup : Dependent class is invalid and needs recompilation:
Class RollupEvaluator : Dependent class is invalid and needs recompilation:
Class RollupDateLiteral : Invalid date
RollupSchedulable: Dependent class is invalid and needs recompilation:
Class Rollup : Dependent class is invalid and needs recompilation:
Class RollupEvaluator : Dependent class is invalid and needs recompilation:
Class RollupDateLiteral : Invalid date

(rollupUtils) Unable to find Apex action class referenced as 'Rollup'.
rollupUtils: Unable to find Apex action class referenced as 'Rollup'.

@Jung-BEP I'm unable to reproduce this issue. If you are installing via the package installation screen, I would advise using the advanced options and specifying only compiling apex classes in the package. If you are doing a package upgrade from a version prior to 1.5, you may need to uninstall the existing package and reinstall because each minor version from (from 1.4 -> 1.5, for example) comes with breaking changes that necessitate further upgrade work.

Thank you @jamessimone  It is a logical suggestion. Didn't try that option. If the installation goes well, i will close out the issue.

hi @jamessimone
I think I found the cause. Our org is enabled with Custom Fiscal Year. So "SELECT Id FROM Opportunity WHERE CloseDate = THIS_FISCAL_YEAR" will flag as invalid.
When this following snippet was executed in Anonymous window, Invalid Date error displayed.
List oppList = [SELECT Id FROM Opportunity WHERE CloseDate = THIS_FISCAL_YEAR LIMIT 10];
system.debug(oppList);
I will close the issue as it is specific to an org with Custom Fiscal Year enabled.
Thank you!


Incompatibile Ignored

I am trying to use the incompatibility dictionaries. I added an incompatibility set (in both directions where A and B have matching rules for A to B and B to A) however the generation seems to ignore this rule. Is this a bug or am I doing something incorrectly in the setup? Note: I am using nested folders in parts of my setup like armor and armor accessories.
My File Structure:
- layers
    - facewear
        - None#50
        - Full Face Mask#10
        - Another Full Face Mask#10
        - White Half Mask#20
        - Black Half Mask#20
    -eyewear
        - None#50
        - Green Circle Glasses#20
        - Transparent Glasses#20

Note: I could put these all in one layer category but Black and White are half masks which only cover the mouth while eyes are exposed. That means we can have eyewear with these masks.  I've went back to the sample code and the following worked. The cause was a slight typo Facemask instead of Face mask
const incompatible = {
   "gold chain": ["MetallicShades"],
   "MetallicShades": ["gold chain"],
};


[Docs Bug 🐞 report]: fix spelling in streetlights tutorial header

Describe the bug you found in AsyncAPI Docs.
Thing to fix 😄
In the Streetlights tutorial, the last header of the page reads Conclusions.
There are 2 reasons why we want to fix this:

This is a spelling mistake, because it should not be plural.
We should have consistency in everything we write in our Docs, and in all of our other pages, when the header Conclusion was used, it was always in singular form.

Solution to implement 🙌🏻
Since this word needs to be singular, change the header to read Conclusion.
How do I get started contributing to this ticket for AsyncAPI Docs?
 At AsyncAPI, we value Doc contributions as much as every other type of contribution. ❤
To get started as a Docs contributor:

Familiarize yourself with our project's Contribution Guide and our Code of Conduct.
Head over to our Docs GH Board here and bookmark it.
Lleave a comment in the issue you're pickin up and introduce yourself. This is also the perfect place to leave any questions you may have on how to get started.
Open a PR and get started!

🏷 Tag Alejandra Quetzalli in your AsyncAPI Doc PRs
Do you have a documentation contributor question and you're wondering how to tag Alejandra into your GitHub discussion or PR? Never fear!
Tag me in your AsyncAPI Doc PRs or GitHub Discussions via my GitHub handle, alequetzalli 🐙.
Attach any resources that can help us understand the issue.

Code of Conduct

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

Here is a perfect good-first-issue for you, @luphieanza. 😃
If you have any trouble getting the PR up, let me know. 👍🏻

@alequetzalli So about this issue, did I need to fix the spelling in all of the streetlights.md section or just inside of the conclusions section?

@alequetzalli So about this issue, did I need to fix the spelling in all of the streetlights.md section or just inside of the conclusions section?

Hey @luphieanza, this issue and the title only say to fix the streetlights tutorial. Just follow the literal instructions in the issue ♥

Hi there,
If there's no update on this issue, I'd like to take it up and submit a PR for a fix.
@alequetzalli

@vickywane I think its been merged, I was PR for this issue but in the other issue, its my fault anyways to forget PR for each of issue cc @alequetzalli

Thanks for the update.
😊

Might you want to check this issue #587.

Yep, I will.

@luphieanza The PR still isn't merged, you need to address feedback on it 😄 . No rush, take your time on it. 🌟

I'm coming up with the revision :bullettrain_front: @alequetzalli

I'm coming up with the revision 🚅 @alequetzalli

Yay! thank you, you're a ⭐

BTW can you re-assign me for this issue, I click the wrong button yesterday 😅

Done ✅

Great job, you just made your first two contributions to the AsyncAPI Docs! 🏅


Honda: disengagement via braking sometimes triggers unnecessary red alert

Describe the bug
Since updating to 0.8.11, a frequent occurrence has been that disengaging via braking causes an immediate red alert.
What hardware does this issue affect?
comma three
Provide a route where the issue occurs
930ad2d3aa9a7438|2021-12-04--10-08-21
openpilot version
0.8.11
Additional info
I do not know if this is model-specific or not.

If its the cruiseDisabled Event Alert, this happens on Honda Civic Bosch Diesel as well. If you gently press brake  cruiseDisabled Event gets triggered. Havent noticed this on OP 0.8.10 only on 0.8.11

Yes, the message is that cruise is disabled so I assume that is the cruiseDisabled Event.

Any update on this Issue? Not knowing if pressing Brake will trigger Red Alert is annoying.  Please fix this in 0.8.13 or bring a Hotfix in 0.8.12

Just confirmed that the issue persists in 0.8.12.

I can also confirm that this issue  exists in 0.8.12
@adeebshihadeh

Same experience. It’s when you barely tap the brakes and continue coasting. When you brake and continue braking it’s fine.

Dear Comma Team
any updates on this issue?
Would be great if it could be solved with OP 0.8.13

Any Update on this issue? @pd0wm  Thanks in advance,


PyQVM

Simulate quantum programs without ever leaving the comfort of your python environment. Note: not as performant for large numbers of qubits as the QVM
Includes:

ReferenceWavefunctionSimulator
NumpyWavefunctionSimulator
ReferenceDensitySimulator

ReferenceXxxSimulators ported and cleaned up from https://github.com/rigetticomputing/reference-qvm

YAY!

Adding a 👍for another use of this merge. Currently to make noise model templates it's very useful to have matrix representations of all the standard gates accessible in the library. Right now I'm using referenceqvm for this, but it would be better to have these are part of the standard library.

just jumping in here to say that we should think hard on what sort of API we want to expose as part of the pyQVM. merging this as is I think would cause confusion and add noise to the overall API exposed by pyquil.

What's the latest on this?

I'll bring this up to speed with master, add some docs, and target merge after we release v2.1.0

checky checky

This has an incredible test suite 🎉

@ncrubin gets all (most) of the credit for the test suite

Have been using this a bit recently.
I would like to suggest that the API for using the pyQVM and the lisp QVM should be more similar. For example, if I want the wavefunction amplitudes from lisp QVM, I do this:
wf_sim = WavefunctionSimulator()
amplitudes = wf_sim.wavefunction(program).amplitudes

but on pyQVM, I do this:
wf_sim = PyQVM(n_qubits=n_qubits, quantum_simulator_type=NumpyWavefunctionSimulator)
amplitudes = wf_sim.execute(program).wf_simulator.wf

If someone wanted to write an app where the backend were interchangeable, this would cause difficulty.

WavefunctionSimulator should be analogous to NumpyWavefunctionSimulator and QVM should be analogous to PyQVM, so probably
wf_sim = NumpyWavefunctionSimulator(n_qubits)
amplitudes = wf_sim.do_program(program).wf

but we can also add a method wavefunction that returns a Wavefunction object.
Note that each simulator (NumpyWavefunctionSimulator, ReferenceWavefunctionSimulator, ReferenceDensitySimulator) support a common set of methods (ie do_program) but I currently didn't put any code to paper over the different "under the hood" representations (nd tensor, 1d array, 2d matrix resp). sim.wavefunction could help there

I'd like to echo Keri's comment - can we get to a point where simulators/QVMs have a smaller and more uniform interface?


Android 11 and above crashing on notification open

The app crashes while opening the notification and shows the following message
java.lang.NullPointerException: Attempt to invoke virtual method 'java.lang.Object android.os.Bundle.clone()' on a null object reference
currently using version 4.3.1
this patch fixes the problem
fiel path:

react-native-notifications/lib/android/app/src/main/java/com/wix/reactnativenotifications/core/notification/PushNotification.java

 private void notifyOpenedToJS() {
     Bundle response = new Bundle();
     response.putBundle("notification", mNotificationProps.asBundle());
     mJsIOHelper.sendEventToJS(NOTIFICATION_OPENED_EVENT_NAME, response, mAppLifecycleFacade.getRunningReactContext());
 }

to
 private void notifyOpenedToJS() {
        Bundle response = new Bundle();
        try {
            response.putBundle("notification", mNotificationProps.asBundle());
        } catch (NullPointerException e) {
            Log.e(LOGTAG, "notifyOpenedToJS: Null pointer exception");
        }

The patch worked. This should be merged 😓 Too bad wix has abandoned the repo?


Change algorithms from pending deprecation to deprecated

Summary
Supersedes https://github.com/Qiskit/qiskit-terra/pull/9532.
Details and comments

WIP because I want to see what test changes from https://github.com/Qiskit/qiskit-terra/pull/9532 are necessary.
Feel free to start reviewing the prod changes though!

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

30 of 30 (100.0%)  changed or added relevant lines in 16 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.02%) to 85.39%

Totals

Change from base Build<PHONE_NUMBER>:
-0.02%

Covered Lines:
67283

Relevant Lines:
78795

💛  - Coveralls

I will make a minor comment about the text though. Here is what comes out in the VQE class when you look at its docs. We talked about having refs in here instead so its not that. But when I read the first part The class xxxxx.. it almost sounds like some other class especially at the moment with that long ref there - I wonder whether This class xxxxx... would work out better for the docs here so it more seems to refer to what you are currently reading and would be ok in the error message too.

I think I like this class when it's in the docs. But "This class" maybe reads weird during a runtime warning?
FYI, if I recall correctly, I switched to the full module name because I encountered some deprecated function names that were the same function name but in different modules. I wanted to remove all ambiguity.

But "This class" maybe reads weird during a runtime warning?

Yes, that's kinda why I said work out better for the docs. Its a tradeoff given the duality of usage. Since the runtime message is coming from the class itself I though it would be kinda ok that it has this class - it does name itself too. It just seemed weirder in the docs to me where you kinda have to realize that "The class..." is what you are reading and not some other its referring to. The long ref in there at present did not help in that regard for me. Anyway its pretty minor. Its nice to have the notice coming out in the docs and something that is easily tweaked in the decorator right. Maybe its just me - can see what others think going forwards too.

Its nice to have the notice coming out in the docs and something that is easily tweaked in the decorator right.

Yes, very easy to change at any time.


New bug report

Hey there, I just encountered the following error with Alva:
When we want to click the button(in Alva) on windows we need to click the Windows button key instead of the Ctrl key. This must be replaced by the Ctrl key

And on Linux (Ubuntu 19.10 & Alva v0.9.2) it's a weird combination of the Alt+Windows keys in this order, so it only works if I first press Alt.
Really cool tool.


docs: delete deprecated app config design doc

What type of PR is this?
/kind cleanup

What this PR does / why we need it:
docs: delete deprecated app config design doc
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?

Additional documentation e.g., design docs, usage docs, etc.:

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage increased (+0.09%) to 73.97%

Files with Coverage Reduction
New Missed Lines
%

pkg/engine/operation/watch.go
1
85.93%

Totals

Change from base Build<PHONE_NUMBER>:
0.09%

Covered Lines:
7559

Relevant Lines:
10219

💛  - Coveralls


no TermGenie emails

I might have missed something but there are no longer email confirmations from TG term creations. This means if I have created a term one day but it take a a few days for it to get into the ontology, how do I find that term in the meantime? Last time I created it again until the reasoner said 'I found an identical term, would you like to use that one?' but it's a bit convoluted.
Thanks,
Birgit

Hi Birgit,
You must have missed this email:
Everyone, please note that TermGenie no longer sends out email
notifications when your terms are committed. Apologies for this
inconvenience.
We hope to have something working again when we switch to using GitHub
to manage the ontologies.
-D

@cmungall  do we have a time estimate on when these emails will start being sent again?

That's the one! I knew I saw something but couldn't find a GitHub ticket and didn't think about checking through the emails but might have been difficult to find the right one...

Hi @bmeldal
I'm going to close this one as it is a known issue that will hopefully be resolved once the switch is made.
-D


Should have way to get connecting Charge PointIds from Central System

I think it should have a way to know about connecting ChargePoints from Central System class.
When you run the Central System as container and connect it with other servers like this,
Charge Point <-> Central System <-> Your backend Server

and you want send request to Charge Point, you don't know which Central System is connecting to this specific Charge Point.
Its better if Central System can let us know about connecting ChargePointIds.
Here is my idea,
const cs = new CentralSystem();
const chargePoints = cs.getChargePointIds();
const targetChargePointId = 111;
const connecting = !!chargePoints.filter(c => c === targetChargePointId).length;
if (connecting) {
  // has connection with target chargePoint.
  const response = await cs.sendRequest();
}
// no connection

You could alternatively .addConnectionListener and keep this list of connected chargePoints outside of this module:
const connectedChargePointIds = new Set();
cs.addConnectionListener((cpId, status) => {
  if (status === 'connected') connectedChargePointIds.add(cpId);
  if (status === 'disconnected') connectedChargePointIds.delete(cpId);
});

I see, Thanks!


Add support for favicon.ico

Retrieving /favicon.ico always yields a 404, even though the file exists in the public dir.  The file (and all files with the .ico extension) should be supported in the same way as other image and text formats.
(I sent a pull request w/ a patch for this a few minutes ago).

Seems to have been fixed by 076350dcda83ce0b636674ae22d3f34e16a986f3