Update font-meslo-nerd-font-mono to 1.1.0

After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} left no offenses.
[x] The commit message includes the cask’s name and version.

Additionally, if updating a cask:

[ ] sha256 changed but version stayed the same (what is this?).
I’m providing public confirmation below.

Thank you for the contribution. It was merged directly as 648bfdac359ad583106009c135f543c45db973da. Your contribution is still credited to you.


Refetch CI status on dependency reopen

CI status is not reloaded if you already opened a dependency

I don't like the idea of automatically refreshing so I provided a manual data refetch


Moving domains: Domain snaps back to first timestep when there's no active renderer

To reproduce:

Open katrina, go to the last timestep, make and enable any renderer
Disable the renderer, and the domain will jump back to its position in the first timestep even though we are viewing the last

Additionally, if only the image renderer is active, the domain will snap back to the coordinates of the first timestep.


[CI] Ensure [tool.cibuildwheel.macos] also has DISABLE_NUMCODECS_AVX2=1

Closes https://github.com/zarr-developers/numcodecs/issues/473
This PR adds (back) DISABLE_NUMCODECS_AVX2=1  to [tool.cibuildwheel.macos] in pyproject.toml to prevent failures if runner doesn't support AVX2.
TODO:

[ ] Unit tests and/or doctests in docstrings
[ ] Tests pass locally
[ ] Docstrings and API docs for any new/modified user-facing classes and functions
[ ] Changes documented in docs/release.rst
[ ] Docs build locally
[ ] GitHub Actions CI passes
[ ] Test coverage to 100% (Codecov passes)

Going to skip the release note since this mainly influences development

Thanks Peter! 🙏


TableView doesn't Update

In a Nanos app create a Test in the Test menu. Click the "run" button and notice that the row doesn't update. If you leave the screen then return, then you'll see the update. I added pub() calls to the ClientDAO, but that doesn't work because the TableView is using listen(). It's confusing to have two dao listening methods at the moment.

Okay I've fixed this by not sending listen_ requests to the server, and instead using the regular AbstractDAO implementation and publishing events local listeners.
In the future I will look at actually supporting remote listeners on nanos.

Thanks
On Aug 1, 2017 8:38 PM, "adamvy"<EMAIL_ADDRESS>wrote:

Okay I've fixed this by not sending listen_ requests to the server, and
instead using the regular AbstractDAO implementation and publishing events
local listeners.
In the future I will look at actually supporting remote listeners on nanos.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/foam-framework/foam2/issues/568#issuecomment-319459373,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHHXs-DBIhHi0mvXgBqyBtZ3HAwoRDc6ks5sT3DBgaJpZM4OnOZp
.


Improve completion of bidi calls when there is an initial error

Towards improving the bidi-error situation noticed in https://github.com/grpc/grpc/issues/10526.
Currently, bidi calls don't raise grpc status errors or terminate their operation view's when there is an error while sending initial metadata.

test failures:

windows basic tests (on kokoro): https://github.com/grpc/grpc/issues/11188
interop cloud to prod (on kokoro): https://github.com/grpc/grpc/issues/11967


Opencv compilation

Hey Do we need to compile with opencv_contrib?
Do you have list of cmake flags needed to compile opencv for bgslib ?
Also,
After installing opencv on Windows, is it okay if i install bgslib with only these commands:
python setup.py build
&
python setup.py install
I want to use only python wrappers. Will these commands compile and install backend C++ algorithms and create python wrappers?
Please guide me.

Hi @mitesh741 ,
To compile the C++ code for BGSLibrary successfully, it is essential to build and install the official OpenCV library, even if you only need the Python Wrapper. Please note that the opencv_contrib python package does not include the necessary C++ libraries for compiling OpenCV apps.
Once you have built the BGSLibrary, you can utilize the opencv_contrib package to run the demo scripts. However, it's important to mention that the opencv_contrib package is optional. During the compilation of the official OpenCV library, you have the option to generate the Python wrappers (also known as the cv2 package).


Popsicle

Popsicle - Delightful, extensible Swift value interpolation framework :large_orange_diamond:

@DavdRoman do you know on what category we could add?

@lfarah I'd suggest Animation.

Thanks for helping us out, @DavdRoman! 😄


Feature/#2 docbox jedis manager

Fixes #2
Updated comments for each function in jedisManager.cfc.
Updated box.json for docbox
Updated gitignore for  files and folders in docs folder
docs folder with .gitkeep file
@rosscupidmedia @TheRealAgentK

I think I'd do this slightly differently.
Docbox as a dev dependency is the correct approach, but I wouldn't have any of the generated output ever in the repository.
Instead, I think what'd cleaner would be:
Have docbox generating scripts on box.json (similar to how we run fixinator etc. in Pulsar from box.json scripts) setup to generate the docs into a specific subdirectory (docs in your case). And that target directory exists with a .gitkeep file (there are tons of different approaches for that) and is otherwise ignored in .gitignore. So - people can create the docs, but they will never be commited back accidentally or on purpose.

Looks good, just noticed that you might to add a bit of HTML formatting into the CFC to get it to redner correctly in the docs.

Or, just leave the first two lines out.


GH-31506: [Python] Address docstrings in Streams and File Access (Factory Functions)

Which issue does this PR close?
Closes #31506
Rationale for this change
Ensure docstrings for Streams and File Access - Factory Functions - have an Examples section:
What changes are included in this PR?
Added docstring examples for:

pyarrow.input_stream
pyarrow.output_stream
pyarrow.memory_map
pyarrow.create_memory_map

Also pytest argument  --disable-warnings for pytest-cython is added, see https://github.com/lgpage/pytest-cython/issues/3:
=============================== warnings summary ===============================
opt/conda/envs/arrow/lib/python3.9/site-packages/pytest_cython/plugin.py:57
  /opt/conda/envs/arrow/lib/python3.9/site-packages/pytest_cython/plugin.py:57: PytestRemovedIn8Warning: The (fspath: py.path.local) argument to DoctestModule is deprecated. Please use the (path: pathlib.Path) argument instead.
  See https://docs.pytest.org/en/latest/deprecations.html#fspath-argument-for-node-constructors-replaced-with-pathlib-path
    return DoctestModule.from_parent(parent, fspath=path)

Are these changes tested?
Yes, locally with pytest --doctest-cython --disable-warnings pyarrow and on the CI with Python / AMD64 Conda Python 3.9 Sphinx & Numpydoc  build.
Are there any user-facing changes?
No.

Closes: #31506

It seems that this is lgpage/pytest-cython#24 not lgpage/pytest-cython#3 . There is a patch in lgpage/pytest-cython#24 but it's not pull request. How about making the patch a pull request for easy to merge by pytest-cython maintainer?

Correct! WIll do.

Could you also add the issue as a comment of --disable-warnings? We'll remove --disable-warnings when the issue is resolved.

Do I understand correctly that I should make a new issue to remove --disable-warnings once the patch is included in a new release of pytest-cython?

Do I understand correctly that I should make a new issue to remove --disable-warnings once the patch is included in a new release of pytest-cython?

Sorry. I wanted to say that I want you to add a comment something like the following:
diff --git a/docker-compose.yml b/docker-compose.yml
index 3774d55868..7cc10743e7 100644
--- a/docker-compose.yml
+++ b/docker-compose.yml
@@ -1101,7 +1101,10 @@ services:
       LANG: "C.UTF-8"
       BUILD_DOCS_CPP: "ON"
       BUILD_DOCS_PYTHON: "ON"
-      PYTEST_ARGS: "--doctest-modules --doctest-cython"
+      # GH-31506/GH-33609: Remove --disable-warnings once
+      # https://github.com/lgpage/pytest-cython/issues/24 is resolved
+      # and released a new version that includes the fix.
+      PYTEST_ARGS: "--doctest-modules --doctest-cython --disable-warnings"
     volumes: *conda-volumes
     command:
       ["/arrow/ci/scripts/cpp_build.sh /arrow /build &&

But creating a new issue for the removal as you said is a good idea!

That makes sense, thank you for explaining! Will do.

It seems that this is lgpage/pytest-cython#24 not lgpage/pytest-cython#3 . There is a patch in lgpage/pytest-cython#24 but it's not pull request. How about making the patch a pull request for easy to merge by pytest-cython maintainer?

The PR with the patch for pytest-cython just submitted: https://github.com/lgpage/pytest-cython/pull/26

Could you also add the issue as a comment of --disable-warnings? We'll remove --disable-warnings when the issue is resolved.

I have added a comment as suggested in the last commit and will create a GitHub issue when to remove --disable-warnings after this PR is merged.

Thanks!
Could you rebase on master to fix lint error?

Thank you @kou!
I have created new issue to remove --disable-warnings with new release of pytest-cython:
https://github.com/apache/arrow/issues/33715


Fluka.Cern integration

This PR includes the changes needed to use the Fluka.Cern interface to the hadron inelastic scattering process as in geant4-11.1.ref05:

changes in CMakeLists.txt (1d45ed6de2a11425ee21f7ba0180bf7e353f9760)
introduce the FTFP_BERT PL with Fluka process (0df32b91ca4c80e8f0198f569f1256d4d7c45c61<PHONE_NUMBER>2a7462aa1c04f4bd9baac2b872913b 49b800fa001d7bbd8873fab11e174dd58b642c83)
Format and small changes (3dcc24b3d07560abcb2c56501261a3c1d1562048 2414eeefa21308aa54aeb45680218df0c6f4c523)
Add documentation (5cef16fc1fc6b2ce7054495d4082cac4bd3e0367 e2f20e6289b92a060672d3ba27a70b2def9836ec)

Accepting PR #18


Adding drop shadow to the Card Items in Home page

Description

I would like to add some shadow in the card items as the color of the card items and the background is not distinguishable.
And adding to this we can also give some hover effect to the card items.
Solution Proposed
No response
Screenshots
No response
Additional Context
No response
Checklist

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[X] I would like to be assigned this task.
[X] I am a GSSoC'23 contributor

@muskandn thanks for raising issue. But sorry we don't need this. Please look for other improvements

Ohh okay... No problem.
On Tue, 6 Jun 2023, 6:23 am Anmol Agrawal, @.***> wrote:

Closed #274 https://github.com/anmode/grabtern-frontend/issues/274 as
completed.
—
Reply to this email directly, view it on GitHub
https://github.com/anmode/grabtern-frontend/issues/274#event-9439988148,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AXXY2SFDM6A6GYWFBJOHQCDXJZ5QHANCNFSM6AAAAAAY3K3OKI
.
You are receiving this because you were mentioned.Message ID:
@.***>


feat: update Containerd to 1.7.6

What problem does this PR solve?:
Which issue(s) does this PR fix?:

https://jira.d2iq.com/browse/D2IQ-NUMBER

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

Why can't we bump to 1.7.x?

Why can't we bump to 1.7.x?

Ah, we can! Just checked https://github.com/containerd/containerd/blob/main/RELEASES.md#kubernetes-support

We don't have the builds for 1.7.x yet https://teamcity.mesosphere.io/project/MesosphereOnly_ClosedSource_DkpReleases_UpstreamBuilds_Containerd?branch=&buildTypeTab=overview&mode=builds#all-projects

I don't think I would be comfortable merging a 1.7.x bump before testing some images built with KIB in Konvoy.

@faiq when did the podman build get broken? Will we need to backport for DKP 2.6? If so, please pull those commits out into  a separate PR.

To me the issue with podman seems to be rooted with using the binary with the embedded image. I'm not sure when this happened, but to work around it in the tests we are now pulling the image instead. For users that wish to you use podman as a container engine, it seems to me that they should not use the binary with the embeded image and opt to pull it instead.

Based on this conversation we actually cannot upgrade containerd at this time. The containerd version is constrained by our Flatcar LTS version; see the previous PR for K8s 1.26 and Flatcar LTS release notes.

Based on this conversation we actually cannot upgrade containerd at this time. The containerd version is constrained by our Flatcar LTS version; see the previous PR for K8s 1.26 and Flatcar LTS release notes.

@bcm820 do you mean here that you can't upgrade Flatcar, or are you saying we shouldn't upgrade Containerd at all?

@bcm820 do you mean here that you can't upgrade Flatcar, or are you saying we shouldn't upgrade Containerd at all?

As discussed in the thread, I was confused about the dependency on containerd. Please disregard :)


CQL to Set Consistency Level Seems Obsolete

I am using phantom 1.8.4 with Cassandra 2.0.8, in an experimental 3-node cluster setting. I modified SimpleRecipes example to set a consistency level for Insert query like this:
def insertRecord(recipe: Recipe): ScalaFuture[ResultSet] = {
    insert.value(_.id, recipe.id)
      .value(_.title, recipe.title)
      .value(_.author, recipe.author)
      .value(_.description, recipe.description)
      .value(_.ingredients, recipe.ingredients)
      .value(_.name, recipe.name)
      .ttl(150.minutes.inSeconds)
      .consistencyLevel_=(ConsistencyLevel.ALL)
      .future()
  }

I see that the query built is:
CQLQuery(INSERT INTO phantom_examples.nosheen_recipes (ident, title, author, description, ingredients, name)
VALUES(6f9b8507-cc06-4355-bac7-1ecfe0b260c7, 'Yummy Chicken', 'Nosheen Zaza', 'Grill on wooden skewers', { 'chicken', 'spice', 'more spice' }, 'Grilled Chicken')
USING TTL 9000 CONSISTENCY ALL)

I know that setting consistency level in USING clause like this is not supported in CQL 3, used in 2.0.* and 2.1.* versions in Cassandra. When running my code, I get an error.
Looking at Phantom's source code it does not seem like queries are built differently depending on CQL version. What is the problem here? And how can I set the consistency level correctly?

Hi @nosheenzaza,
This is definitely a bug on our end, thank you for reporting it.  We will include the bug fix in 1.9.0 to address the issue and our apologies for the inconvenience.
It will be released alongside all the new 1.9.0, including the new connectors framework and other niceties, hopefully by the end of this week or mid next week. We will also aim to push a quick fix for this shortly as we already have the means to introduce per version behaviour easily.
Regards,

Hi @nosheenzaza  ,
Currently the consistency level in the latest versions of the CQL protocol is set in a whole new way, in a use clause at protocol level. So you would have to execute two queries to effectively set the level of a query:

USE CONSISTENCY QUORUM;

UPDATE keyspace.table WHERE .. bla

This is somewhat misleading and a bit dangerous to do on the client because we would need to automatically batch queries and execute two things at once. There is also a problem is permanently having to reset the consistency level currently in use, in the event the "next" query does not have a consistency level set. So for every query, you would now have to run 3 queries, to set the consistency level, execute the actual query, and then unset it.
If you would use the Java driver, setting the consistency level produces the exact same query and having never set it in the first place, which means setting the level on a per query basis is no longer a possibility. We are very open to debate about this but our current understanding is that the level settings have indeed changed.
I know you've been doing work to research this in more depth, do you have any further insights we are currently missing on? As far as it's visible from here per query consistency level should be deprecated and removed for all protocol versions greater than 3.1 and we should do the exact same thing as the Datastax Java Driver does, which is to leave the query unchanged for protocol versions newer than 3.1.0
Regards,
Flavian

Hello Flavian,
The following is what I remember on top of my head but I will try to look more into it tomorrow.
Looking at [this issue] (https://issues.apache.org/jira/browse/CASSANDRA-4734) and examples of using the Java driver, I understand that clients should still allow setting the consistency level per statement, however not by allowing the user to pass the CQL query string with USING part, but by setting it as a parameter to the CQL statement, exactly like you do in your driver currently. The relevant point here is to avoid having to parse CQL statements as a string in order to figure out the specified consistency. I would assume this makes setting the consistency in phantom behind the scenes even simpler, because you do not have to append the consistency as a substring to your CQL statement string and then ask the session to execute it. You can instead generate the CQL statement string, pass along the consistency level then ask the session to execute it with the specified level. I am not how the session associates a consistency level to a statement behind the scenes, but I assume this is unimportant for the goal of updating phantom.
In summery, I believe phantom's interface should remain the same, and some refactoring should be done to the code that assembles the CQL query string. What do you think?

Hi @nosheenzaza,
That sounds like the perfect plan except I seriously fail to see where the Datastax Java driver sets the CQL internally. The cluster has some query options and we can also use SimpleStatement forwarding internally to try and forward the consistency level definitions invisibly.
This should hopefully be fixed with some more iteration done at more reasonable times of the day. Looks like this should be addressable after all, it's been a problem for some time. Many thanks for your advice and contributions!
Regards,

Hi @nosheenzaza,
I've finally had the time to do something about this and a pull request is now available here. Wouldn't mind some feedback on the implementation, which feels slightly hackish in an attempt to avoid having to make backwards incompatible changes.
Right now even though null defaults are propagated around, no queries in the tests or any code whatsoever was exposed to the end user and the change is invisible. Perhaps there are still improvements to be made while keeping this behaviour and avoiding the rather ugly solution at the same time.
Regards.

@nosheenzaza Phantom 1.12.2 is in the process of being synced to Maven Central, we've fixed support for consistency levels in all queries and added per CQL protocol version mechanisms that are backwards compatible with old versions of Cassandra as well. The issue is now fixed and can be closed. The tag is 1.12.2 so the diff is easy to review if need be.

Many many thanks! I did not have the time to have a look yet. Will try to do it over weekend.

Hello @alexflav23,
I'm still seeing this problem with phantom 1.12.2 and 1.12.3 on Cassandra <IP_ADDRESS>4/DSE 4.6.2 (CQL spec 3.1.1). Is there a flag I need to set somewhere to enable the correct behavior? (I admit I haven't looked at tag diffs for 1.12.2 or 1.12.3)
When I execute the query
insert
  .value(_.job_id, jobId)
  .value(_.checksum, checksum)
  .consistencyLevel_=(ConsistencyLevel.QUORUM)
  .ttl(ttl)
  .future()

I get the following exception
com.datastax.driver.core.exceptions.SyntaxError: line 1:87 missing EOF at 'USING'
 	at com.datastax.driver.core.Responses$Error.asException(Responses.java:122) ~[cassandra-driver-core-2.2.0-rc3.jar:na]
 	at com.datastax.driver.core.DefaultResultSetFuture.onSet(DefaultResultSetFuture.java:120) ~[cassandra-driver-core-2.2.0-rc3.jar:na]
 	at com.datastax.driver.core.RequestHandler.setFinalResult(RequestHandler.java:186) ~[cassandra-driver-core-2.2.0-rc3.jar:na]
 	at com.datastax.driver.core.RequestHandler.access$2300(RequestHandler.java:45) ~[cassandra-driver-core-2.2.0-rc3.jar:na]
 	at com.datastax.driver.core.RequestHandler$SpeculativeExecution.setFinalResult(RequestHandler.java:754) ~[cassandra-driver-core-2.2.0-rc3.jar:na]
 	at com.datastax.driver.core.RequestHandler$SpeculativeExecution.onSet(RequestHandler.java:576) ~[cassandra-driver-core-2.2.0-rc3.jar:na]
 	at com.datastax.driver.core.Connection$Dispatcher.channelRead0(Connection.java:994) ~[cassandra-driver-core-2.2.0-rc3.jar:na]
 	at com.datastax.driver.core.Connection$Dispatcher.channelRead0(Connection.java:916) ~[cassandra-driver-core-2.2.0-rc3.jar:na]
...(netty stuff)

Thanks,
JFK

If it helps any, the query string that is generated by phantom is
INSERT INTO docs.contents (job_id, checksum) VALUES('DDBFC8A4-9173-41DB-B42F-076B543E6CE9', '5a73b427f04db5ff7af8703063923a0a') USING CONSISTENCY QUORUM;

So I tried another version of DSE (Cassandra <IP_ADDRESS>2 | DSE 4.7.4 | CQL spec 3.2.1) and it seems to work now. Not sure what the issue was with the other version.


chore: release v0.6.1

:robot: I have created a release beep boop
0.6.1 (2023-11-05)
What's Changed

chore(cmd/gdenv): remove completions command until improved support is added in urfave/cli by @coffeebeats in https://github.com/coffeebeats/gdenv/pull/130

Full Changelog: https://github.com/coffeebeats/gdenv/compare/v0.6.0...v0.6.1

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/coffeebeats/gdenv/releases/tag/v0.6.1 :sunflower:


[usbdev] Fixes for I/O modes and expand their tests

The differental mode reception and conversion was being done in the iomux
and potentially not passing all information to the usb_fs_rx module. Reworked
to pass the single ended and differential data to usb_fs_rx, recover them
both and use the configured mode to forward appropriately.
This changes the usbdev_iomux to only synchronize and pinflip I/O and
pass the rx d, d+ and d- to receive logic.
As part of debug fixed verilator UNOPTFLAT complaint and added a link
state representing the link being active but never seen SOF because this
is where a flipped link gets stuck between FPGA board and Linux. (The
flipped pullup will make it look like a LS not FS link so the 1.5Mbit
chatter is enough to get rx PID erros but also keeps resetting the
link so host_lost never fires).
Update verilator top and usbdpi to manage all the I/Os. And add code
to the usbdpi to be able to simulate pinflip and differential as well
as the normal pin mode. Note that because there is no other signal it
uses the tx_mode_se signal to control use of differential mode in both
tx and rx directions (so it only works if both phy config bits are the
same). It uses the DN PULLUP being asserted to detect flip.
Update hello_usbdev.c to set the phy config from gpio pins. These
are switches on the nexysvideo and can be set using gpio-dpi in
verilator.
Update top_earlgrey_nexysvideo to be able to fake swapping of USB pins.
Uses DN pullup to cause the pins used for DP and DN to be swapped, allows
testing of both flip options with one FPGA build.
Tested with verilator that all four settings of PINFLIP and DIFFIO in
hello_usb.c get the same expected output. Added a script to run all
four simulations (setting the GPIOs to control).
Tested with FPGA that PINFLIP=0,1 both work by setting the switch.
Included changes requested in software and hardware reviews.
Fixes 2598
Signed-off-by: Mark Hayter<EMAIL_ADDRESS>

This is the rebase of #2753
@stefanlippuner I had trouble adding you to the review list, hope the reference here works.

@vogelpi I'm fine with comments in the other side, although I will address them here. I wanted people to be able to see the changes there (without distractions from the rebase).

Did @vogelpi fixes recommended in #2753 and rebased again.
Runs for me on Nexys Video with both pin flips and verilator works.
TODO: Extend script with expected output checking
I suspect usbdev needs to be run through the verilog and C code format tools, I didn't find good instructions in our docs for that yet but will look.

I think I got git clang-format to fix the C code (I found a hint at the bottom of the style guide)
Is there something similar for the verilog?

Then the commit will automatically close the associated issue upon merge.

Thanks @vogelpi  I have yet to find a way to get emacs to match our style, so will probably need to rely on lint or code formatting.

Pinging @mcy, please take another look at this PR. I think all your comments have been addressed. I would like to get this PR merged or at least push it forward as it solves a bug. From the HW side everything looks good.

Sorry @mdhayter , could you please once more rebase this PR? I merged a pretty old PR (#2821) and didn't expect this to cause a conflict.

Will rebase and fix the nits.

Addressed nits from @lenary @vogelpi and me
Rebased for #2821

Thanks @mcy , I am merging this now.


GSD Request

--- GSD JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from v4.6 to before v5.4.180",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=d71785ffc7e7cae3fbdc4ea8a9d05b7a1c59f7b8",
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=0b6087c6358656dd39dc714233d5183abc9c47a1"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "d71785ffc7e7cae3fbdc4ea8a9d05b7a1c59f7b8",
      "note": "introduced"
    },
    {
      "type": "commit",
      "value": "0b6087c6358656dd39dc714233d5183abc9c47a1",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "net: do not keep the dst cache when uncloning an skb dst and its metadata\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v5.4.180 by commit 0b6087c6358656dd39dc714233d5183abc9c47a1, it was introduced in version v4.6 by commit d71785ffc7e7cae3fbdc4ea8a9d05b7a1c59f7b8. For more details please see the references link."
}
--- GSD JSON ---

This issue has been assigned GSD-2022-1000339


rofi-emoji: 2.3.0 -> 3.0.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/rofi-emoji/versions.
meta.description for rofi-emoji is: "An emoji selector plugin for Rofi"
meta.homepage for rofi-emoji is: "https://github.com/Mange/rofi-emoji"
meta.changelog for rofi-emoji is: ""
Updates performed

Version update

To inspect upstream changes

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 3.0.1 with grep in /nix/store/n9nzsjxfzigzbvv9h8fm3fiiq1n36cws-rofi-emoji-3.0.1
found 3.0.1 in filename of file in /nix/store/n9nzsjxfzigzbvv9h8fm3fiiq1n36cws-rofi-emoji-3.0.1

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
rofi-emoji

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/n9nzsjxfzigzbvv9h8fm3fiiq1n36cws-rofi-emoji-3.0.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A rofi-emoji https://github.com/r-ryantm/nixpkgs/archive/ec0fdfcd3133a83bbb207379ccedea9a8f3df2d6.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/n9nzsjxfzigzbvv9h8fm3fiiq1n36cws-rofi-emoji-3.0.1
ls -la /nix/store/n9nzsjxfzigzbvv9h8fm3fiiq1n36cws-rofi-emoji-3.0.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

rofi-emoji

Maintainer pings
cc @cole-h for testing.

Built went fine, no breaking changes in the changelog. LGTM


IOS long disconnect time

As connect is fast but disconnect encountering 20s to process, in ios con setting it's show disconnecting ...

how to resolve

same as #21


[-] Attempts: 0 Long time no Attempts

SALAM ALYKOM Brother ^^
The Script keeps trying but without any attempts, attempts won't change
[-] Proxy-IP: <IP_ADDRESS>[FR]
[-] Wordlist: pass.txt
[-] Username: InstaUser
[-] Password: hsa11445
[-] Attempts: 0
[-] Proxies: 39
any solution or suggestion akhi ^^

same here

good thank you.

still no solution? :(

[-] Proxy-IP:
[-] Wordlist: realuniq.lst
[-] Username: N4R.1
[-] Password:
[-] Attempts: 0
[-] Proxies: 0
[+] Searching for proxies ...
i waiting 2h ;)

Never mind brO ♥ take your time , My suggestion is to make the script offer u to choose between setting proxy manual or automatic it will be so helpful , and i would thank u for your efforts never give up u are the best ;) SALAM

add new option : -p = proxy file


Script incorrectly calculates size of container when Page Blob VHD snapshots Exist

Looks like prior issue, #16217, concerning this issue was closed without this script being fixed.
For example, I have a container with 2 VHD files and added the following write-host line for debug to the script:
$Blobs | ForEach-Object {
$blobSize = Get-BlobBytes $_ $IsPremiumAccount
write-host ("Detail: "+$_.name+" "+$blobSize)
Here is the script output when there are NO snapshots on the VHD files. Note that the VHD files are unlocked and not in use:
AzureContainerSize.ps1 -ResourceGroup rg-sample99 XXXXX-StorageAccountName XXXX -ContainerName zwpctxs0002-fa8a002b0b5c4536baa3882f1761650a
Calculating container zwpctxs0002-fa8a002b0b5c4536baa3882f1761650a ...
Detail: zwpctxs0002-datadisk-000-20191118-003436.vhd 735
Detail: zwpctxs0002-osdisk-20191118-003436.vhd<PHONE_NUMBER>7
Container 'zwpctxs0002-fa8a002b0b5c4536baa3882f1761650a' with 2 blobs has a sizeof 44146.01 MB.
Then I took a snapshot of the "osdisk" VHD and reran the script. The output now essentially doubled the size and this is incorrect:
Calculating container zwpctxs0002-fa8a002b0b5c4536baa3882f1761650a ...
Detail: zwpctxs0002-datadisk-000-20191118-003436.vhd 735
Detail: zwpctxs0002-osdisk-20191118-003436.vhd<PHONE_NUMBER>7
Detail: zwpctxs0002-osdisk-20191118-003436.vhd<PHONE_NUMBER>7
Container 'zwpctxs0002-fa8a002b0b5c4536baa3882f1761650a' with 3 blobs has a sizeof 88292.01 MB.
Either the script has a defect and needs correction, or the problem is in Get-AzStorageBlob which returns snapshots as if they were Blobs (not sure if this command is supposed to, since the documentation doesn't specify).

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

ID: 9efbe4da-1b80-3ea0-15c6-542899a2078a
Version Independent ID: 4b35cd4b-368d-c00e-9345-6b7b929cc5e2
Content: Azure PowerShell script sample - Calculate the total billing size of a blob container
Content Source: articles/storage/scripts/storage-blobs-container-calculate-billing-size-powershell.md
Service: storage
GitHub Login: @fhryo-msft
Microsoft Alias: fryu

@rssllptrs Thanks for your question. We are checking on this and will respond to you soon.

@rssllptrs Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.

#reassign: @tamram

@rssllptrs - Thanks for your feedback. The script currently won't calculate the correct billing size for snapshots. We're aware of the problem and the engineering team is working on a solution. In the meantime, I've added a note to the doc to clarify.
#please-close


Make length of QSHistory editable

Nothing much here. I realised the QSHistory preset in the catalog (Catalog > Quicksilver > Recent Objects) is limited to 50. That's not enough for me.
I made it a hidden preferences to allow you to edit this value (ideally it'd be a setting in the Catalog UI but I don't have the time for this :(

OK, but I say we get rid of MAXHIST entirely and set the default in QSDefaults.plist, since that’s the standard way we handle such things.

And I say "add it to the Advanced prefs" 😉. IIRC it's just about a few lines in a plist (if it supports integer values).

I did the things. 🆒

Looks good. Can I merge a PR that I started? I say yes! :D

Yup.

Of course I just noticed this, but you can’t actually change the number in Extras. You can see what it is, though! 😁

Gosh, I wonder whose fault it is 😁.
I was pretty sure it was working… Oh well, at least it's somewhat auto-documenting.

😨 Ooops!
I think we should try and do away with the 'Extras' tab in the future anyway. It's not very self-explanatory, and some of the prefs should maybe even be deleted. Another job for another day :P


Loader: Check for already-loaded files is broken

In Loader#loadFileRecursively, we attempt to check whether the prospective file has already been loaded; if it has, we skip processing it.  This check is broken - the unit test LoaderTest#crazyIncludes demonstrates this, but as we didn't assert on duplicate file loading there, we never noticed.  The result is that the loaded schema contains two copies of the same struct, which is no good.

On further investigation, this is an artifact on macOS due to its "unique" construct of /private/var/folders being the same as /var/folders; our test's temp files ended up there, File#getCanonicalPath() returned the former, but File#getAbsolutePath() returned the latter.  Thus the same file gets included twice, under different paths.
This isn't an issue of symlinks - the two paths are entirely unrelated, as far as the filesystem interface is concerned, but in reality are both views to the same data.  Pretty wild!  Will update the test to use File#getAbsolutePath() instead.

On second thought, it's pretty dirty to just bury this problem by altering tests to avoid it.  Let's just canonicalize all file paths that we load.


fix: release-plz-pr "needs" release-plz-release

If release-plz-pr sees that the local version is greater than the version in the crates.io registry, it does not create a new PR. We need to wait for the release to complete so that this step can trigger a new release PR.

Waiting to see what the release plz folks think of this: https://github.com/spiraldb/vortex/pull/1282


Fix the rest of the pytpye errors.

After #36.
This works with python 3.9
Opensourse pytype doesn't support py3.11 yet.
Most of them were just a find/replace | with Optional.
We'd be okay without switching to Optional.
Will add GH action to check pytype next.

Internal lint checks are forcing me to remove py3.9 typing, so that's a vote to only run the checks on 3.10+.
I guess the only thing that would be lost is for someone trying to check their project on 3.9. Oh well. I'll revert those.

Strange, there are a few commits on the branch that aren't showing up in the PR.


Rate limit time priod not respected?

Hey,
I am trying to use this library in the following setup:

Hammer
Hammer plug
Hammer redis backend

The plug setup is very simple, I am using the default ip option.
I am experimenting with smaller time frames, 20-30 seconds and 10 requests allowed in given timeframe.
In my test cases(uses ets) everything seems ok.
In reality it seems like something is off, could be my config.
If I put in let's say this plug config:
  plug Hammer.Plug,
       [rate_limit: {"public:clip", 60_000, 3}]
       when action == :public_clip

So 3 requests in 1 minute, and then just continuously refresh the page the limit is not being applied, same with new page loads.
I checked in redis and it seems there are multiple keys when I would expect 1, which explains why the limit is sometimes lifted, but I don't understand why.

This is what I mean. 1 ip but multiple entries with the part after the ip making the key different.
My Hammer config:
config :hammer,
  backend:
    {Hammer.Backend.Redis,
     [
       expiry_ms: 60_000 * 60 * 14,
       redis_url: redis_url,
       pool_size: 4,
       pool_max_overflow: 2
     ]}

Any ideas what is causing this?
Thank you

I am digging into the code, in hammer/lib/hammer/utils.ex:18 stamp_key/2 I am seeing the following:
I am using 60_000 ms as my scale_ms.
Case 1:
time_stamp:<PHONE_NUMBER>745
timestamp/scale_ms and truncated = 27717246
Case 2:
time_stamp:<PHONE_NUMBER>274
timestamp/scale_ms and truncated = 27717247
This results in a new bucket much sooner than it should.
If I understand correctly, this is due to the division and the truncation.
It works more like not 1 minute from the first request, but request in given 1 minute period.


Adding music

Are there any plans to map the key-presses to music? My proposal would be, to slide the key presses in rotation to align with a beat of a song.

This tool is more about mastering the timing of a rotation, so moving them to match a song beat is not really that helpful and way out of scope for this project, sorry.


Add onyx database to list of Graph databases.

I have added Onyx Database in the list of Graph NoSQL databases.  If you have any questions.  Please feel free to contact me via email<EMAIL_ADDRESS>

Manually inserted. I do not put newcomers on top without testing. But you might move up in time. Thanks and Regards

Perhaps this PR should be closed, given that the listing has been added manually?


guard on host connection create

For #9005

[x] Pull request represents a single change (i.e. not fixing disparate/unrelated things in a single PR)
[x] Title summarizes what is changing
[ ] Has a news entry file (remember to thank yourself!)
[ ] Appropriate comments and documentation strings in the code
[ ] Has sufficient logging.
[ ] Has telemetry for enhancements.
[ ] Unit tests & system/integration tests are added/updated
[ ] Test plan is updated as appropriate
[ ] package-lock.json has been regenerated by running npm install (if dependencies have changed)
[ ] The wiki is updated with any design decisions/details.

Codecov Report

Merging #9058 into master will decrease coverage by <.01%.
The diff coverage is 61.53%.

@@            Coverage Diff             @@
##           master    #9058      +/-   ##
==========================================
- Coverage   57.08%   57.08%   -0.01%
==========================================
  Files         551      551
  Lines       29086    29093       +7
  Branches     4394     4396       +2
==========================================
+ Hits        16605    16608       +3
- Misses      11573    11575       +2
- Partials      908      910       +2

Impacted Files
Coverage Δ

...ascience/jupyter/liveshare/hostJupyterExecution.ts
51.61% <61.53%> (+0.7%)
:arrow_up:

src/client/common/utils/platform.ts
70.58% <0%> (-5.89%)
:arrow_down:

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 85e9721...3e87cf0. Read the comment docs.


Input Mask

I've managed to add an Input mask in the add window. But when it comes to update a record row it doesn't work (I'm using jquery.inputmask.js plugin)

Any suggestions or is it definitely not possible?

I think it's possible because there is no limit to the cell editor system.
But without code or console log or error message, I can't help you.

the input mask plugin works fine on in the add record window using this In  of index.php:
.....

        <div class="row">
            <input type="text" id="chassi" name="chassi" placeholder="chassi" data-inputmask="'mask': '#################', 'placeholder': '.'" />
        ........
    </div>
	<script type="text/javascript">
		$(document).ready(function(){
			$(":input").inputmask();
		});
	</script>

What I can't find out is how to make it work in the grid

You must create a dedicated editor. Check this: https://github.com/webismymind/editablegrid/blob/master/editablegrid_editors.js.
We do a similar thing in DateCellEditor.  You have to create InputMaskEditor and bind inputMask in displayEditor()
Something like that :

InputMaskEditor.prototype.displayEditor = function(element, htmlInput)
{
	// call base method
	TextCellEditor.prototype.displayEditor.call(this, element, htmlInput);
	$(htmlInput).inputmask("99-9999999");
};


sourceRoot option

Introduce sourceRoot option.

options.sourceRoot is a root filepath for target test files.
It only works with options.path or options.sourceMap.
If set, filepath in power-assert output will be relative from options.sourceRoot.
When both options.sourceRoot and sourceMap's sourceRoot are given, options.sourceRoot has precedence over sourceMap's sourceRoot.

TODO

[x] document
[x] test
[x] implement
[x] refactor

Coverage increased (+0.09%) to 96.07% when pulling 0f55d16cbca596ee45e5ccae7b562f9ceb3199ed on source-root into e3220440c06e4e3ebe9c2ca190bf7b4826576d55 on master.


Unhandled Promise rejection: ... Cannot read property 'length' of undefined {}

Operating System: Windows 10
VSCode Version: 1.42.1
CMake Tools Extension Version: 1.3.1

One of our users is just getting started with a CMake project using VS Code.  He sees this exception:
[rollbar] Unhandled exception: Unhandled Promise rejection: build TypeError: Cannot read property 'length' of undefined {}

What might be the cause of this?
Could the error message be improved?

If you go to "Help" -> "Toggle Developer Tools" from the menu bar, do you see a callstack in the console?  If you could share that with us, that would help us locate exactly where the error is.

I might have found the error in our telemetry.  I have a PR open for it: https://github.com/microsoft/vscode-cmake-tools/pull/1113

@bobbrow Hopefully this is what you need:
kay.txt

Is there a workaround?

Can you try pointing to a specific version of cmake using the cmake.cmakePath setting?

(this looks like the same issue I just submitted a fix for)

CMake was not installed. We've installed it now and the exception does not occur.


Merge User Guide into Cookbook

As far as OSS docs, /I think/ I much prefer a cookbook (covers a little of each concept in a single standalone example/recipe) over the user-guide (covers each concept separately, step-by-step) styles.
I sort of find the current version of the user guide too verbose, carrying lots irrelevant details. I tend to believe that the combination of a rich cookbook (solves particular problems; gives initial impression) and readable source code (gives in-depth/implementation details) would give the community much more than the current user guide.
What do people think about this?

We have debated this same issue within our team as well because we noticed people coming to the docs with concrete issues to solve. Sometimes experienced developers and sometimes beginners. Both benefit from the recipe style but it also stimulates copy and paste programming which leads to less understanding and more questions about simple situations that are just a bit different from the recipe.
On the other hand the user guide is quite detailed and sometimes rather dry. This makes it possible to quickly get to thoroughly learn the framework from the bottom up but doesn't help when you just want to build a simple app.
This is why we decided on a best of both worlds: detailed user guides with details on how and why things work and recipes for things we see often.
Maintaining two distinct sets of documentation is quite a bit of work but I think it pays of in the end.
Personally, I really like the user guides with lots of details and explanations on why things are as they are on a conceptual level because it helps me think of how the library work.

I'd like to abandon that idea. I now think both user-guide and cookbook make a lot of sense.


Add a Music Player

Issue Type:

[ ] Bug Report
[x] Feature Request
[x] Documentaion

Description
A music player with  features like play, pause, next and many more.
Stacks Used

HTML
CSS
Javascript

I am a GSSOC'22 contributor. Please assign this issue to me.

I am a gssoc 22 participant , please assign me also in this  work


Issue with k8s.io//docs/reference/command-line-tools-reference/kube-scheduler/ [File: /content/en/docs/reference/command-line-tools-reference/kube-scheduler.md]

This is a...

[ ] Feature Request
[x ] Bug Report

Problem:
The options --address is deprecated, and replaced with --bind-address, but I do not see any information about --bind-address on this page. --port(replaced with --secure-port) also has no information on this page.
Proposed Solution:
Add --bind-address and --secure-port on the page.  Thanks!
Page to Update:
https://kubernetes.io/...

/cc


useMoralisAuth hook's AuthError type refers to unexisting module/directory "src"

New Bug Report
Checklist

[x] I am not disclosing a vulnerability.
[x] I have searched through existing issues and the Moralis Forum.
[x] I can reproduce the issue with the latest react-moralis release, latest SDK release, and my server is updated to the latest version.

Issue Description

Steps + code to reproduce

Setup your project with the following stack: Vite + Typescript + React.
Install moralis and react-moralis from npm
Run npm run build

Actual Outcome
1 Error:
node_modules/react-moralis/lib/hooks/core/useMoralis/_useMoralisAuth.d.ts:2:27 - error TS2307: Cannot find module 'src' or its corresponding type declarations.
2 import { AuthError } from "src";
Expected Outcome
0 Errors
Environment
Doesn't matter.
Server
Doesn't matter.
Client

react-moralis version: ^1.1.0
Moralis SDK version: ^1.1.2
Operating system: Windows 10 x64
Browser: Chrome latest

Logs
node_modules/react-moralis/lib/hooks/core/useMoralis/_useMoralisAuth.d.ts:2:27 - error TS2307: Cannot find module 'src' or its corresponding type declarations.
2 import { AuthError } from "src";

One way I found to get around this was to set skipLibCheck: true in your tsconfig.json. I'm really not sure what module it's trying to find since src/Errors.ts does not export AuthError either.


RX Buffer clear after reading

Thanks for the great example, I'm using it on the Nucleo-G474RE at the moment.
When I use the function ringbuff_read it works until the RX buffer is full (512Bytes). What am I doing wrong? With a terminal tool I send a string to the STM32, the STM32 sends it back. As soon as 512Bytes are in the Buffer, it doesn't works anymore. The data in the buffer should be marked as free after reading but something is not working on my code:
void UARTRxComplete(void)
{
uint8_t addr;
uint16_t len;
rxThisPos=UART_DMA_WRITE_PTR; //get current write pointer
len=(rxThisPos-rxLastPos+UART_RX_RINGBUFF_SZ)%UART_RX_RINGBUFF_SZ; //calculate how far the DMA write pointer has moved
if(len<=UART_RX_MAX_MESSAGE_LEN) { //check message size
ringbuff_advance(&rxRing,len); //move the ring buffer write pointer
rxLastPos=rxThisPos;
//test: send the received data out -> its working until 512bytes, then the RX buffer is full
ringbuff_read(&rxRing,processBuf,len); //read out the data to an array for processing
UARTAddToTxBuff(processBuf, len);
}
else {
while(1); //implement message to large exception
}
}

Issue not relevant to ringbuff.


Terraform Installer error: Invalid Connection Code

Hello, I'm trying to do Terraform installation on GCP and same error persists, "Invalid Connection Code" from https://1pd-scheduler.dev/.
This issue is the same as #94

I tried adding Firewall rule to allow all the traffic but same error persists. as suggested in the original. Tried removing and adding the rule as well.

Tried restarting after adding the rule as well.

Tried curl same command as original poster and it's also timing out.

Tried with custom api-key, Empty string in api-key, same api-key as in the original post. None worked. (Of course deleted everything before trying new ones)

can you suggest next steps?

Hi @psarchi, thanks for raising this.
I'll investigate if this is systemic and let you know.
The problem in #94 has since been solved by the addition of a Firewall rule in the installer and we have not seen similar issues since then, so this must be different. Is this a project created from scracth or do you happen to have other VPC rules that might be interfering here?

Hi, you could consider it as brand new, No Firewall rules or any other VPC-s in Google cloud. just what was installed by installation.

@caiotomazelli I dont think you have resovled #94
This is fresh install today

@caiotomazelli I dont think you have resovled #94 This is fresh install today

even with manually overriding the HTTP traffic in VM settings it still have same issue.

@psarchi I got the same issue aswell, Also could not ping the VM on external or internal IP from Google Cloud shell so it something wrong with the networking settings

@00kennedyp I just checked, same issue on my side as well. I can't even connect to VM with SSH (google cloud's SSH) I thought it was intended for security reasons.

Hi folks, can you please try again?
Just added some fixes that should fix the problem when connecting to 1pd-scheduler.dev
I still don't know why you folks are not able to override the default SSH blocking rule, but I'm investigating.
Do let me know if the problem is solved when connecting to 1pd-scheduler.dev though.


Crit indicator showing up as observer

Not sure on exact repro, but this is what happened.

Started round.
Got shot, entered crit, didn't leave body. Crit indicator (white circle thing) shows up.
Round ended while in crit.
Back to lobby, new round started, forgot to ready up.
Spawned as observer.

Crit circle was present around my observer ghost.

Cant reproduce


Tasks supported in agentless jobs

fixes #4672
Added list of tasks offered in Azure DevOps in the Classic pipeline tab.

@milbrandt : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Thanks @milbrandt!
#sign-off


Question regarding issue 446

Its not clear from the thread. The issue was when the detail view was closed the listing view did not autorotate to landscape, correct? I'm seeing this in my project. Should my root landscape screen autorotate to landscape when a modal is closed?
I downloaded the sample project: https://github.com/jamonholmgren/pm_issue_446. This exhibits the same behavior in the simulator as I see in my own project. The listing view, does not rotate back to landscape when you close the modal.

@majochoc Would you mind posting a screen capture of this behavior so I can understand what's happening a little better?
ref #446

When I start the app:

When I open the details:

When I close the details:

Should I expect the landscape screen to rotate back to landscape? For a screen that supports only landscape orientation you end up with the middle portion of the landscape screen positioned to the top of a portrait orientation. Leaving the whole bottom half of the screen blank. It rotates when a device is rotated, but behavior is a bit weird especially if you have a LandscapeRight screen. I can send you an example of my screen, but need to obfuscate it for NDA

Got it! Will look into it soon.

@majochoc
What are the values of:
# Rakefile
app.interface_orientations = [ ?? ]

And both screen supportedInterfaceOrientations and preferredInterfaceOrientationForPresentation methods?

The above screen shots are from your sample repository for pm_issue_446 untouched.
So:
app.interface_orientation not set
def supportedInterfaceOrientations
UIInterfaceOrientationMaskLandscape
end
def preferredInterfaceOrientationForPresentation
UIInterfaceOrientationLandscapeLeft
end
I mirror these settings in my own app, except I have LandscapeRight instead of Left.
I added app.interface_orientations = [:portrait, :landscape_right] to my rakefile, but the behavior did not change.

I was able to reproduce it: http://clrsight.co/jh/2015-02-27-q5kuy_0_edited.mp4
It looks like this isn't really a ProMotion bug -- other people are reporting it:
http://stackoverflow.com/questions/25391564/ios-7-dismiss-modal-view-controller-and-force-portrait-orientation
We're forwarding rotation requests to the visible view controller, which is the modal. If you override the methods like the second answer recommends, it hopefully will work as a workaround.
I'm not sure what to do within ProMotion to work around this behavior -- seems fairly specific to the use case. Any ideas, @majochoc ?

No good ideas. For now I'm going to avoid the issue and keep my screens portrait.

Gotcha. Let me know if you think of anything later on. Thanks for using ProMotion. :)


Add "shuffler", such that different widgets can be shuffled to test that it is unrelated to ordering

may do that later - may make test code harder to read


Table cell width

Is it possible to specify the cell width for a table cell? (PanelBuilders.table())
Flexibility similar to flexbox would be best. In the attached image, I would like to maximize the middle column (Plugin output) and minimize the two edges.
Thank you in advance.

.overrideCustomFieldConfig('width', 200)
Sorry.


feat(nuxt,schema): support v4 folder structure

🔗 Linked issue
resolves https://github.com/nuxt/nuxt/issues/26444
📚 Description
This implements the new folder structure, if future.compatibilityVersion is set to 4 (which will be enabled by default when Nuxt v4 is released) - see https://github.com/nuxt/nuxt/pull/26925.
The main points (all only relevant when v4 compatibility is enabled):

the new Nuxt default srcDir is app/ by default, and most things are resolved from there.
serverDir now defaults to  <rootDir>/server rather than <srcDir>/server
modules and public are resolved relative to <rootDir> by default. If you want to revert this, set dir.modules to 'src/modules' and dir.public to 'src/public'.
a new dir.app is added, which is the directory we look for router.options.ts and spa-loading-template.html - this defaults to <srcDir>/ (under v4) and <srcDir>/app in v3 mode
I have not changed app.vue to main.vue (as in the RFC) to avoid additional breaking changes
in v4 mode, if there is no app/ directory, we default to previous behaviour (and restart if the app/ directory is added)

The v4 folder structure.
.output/
.nuxt/
app/
  assets/
  components/
  composables/
  layouts/
  middleware/
  pages/
  plugins/
  utils/
  app.vue
  router.options.ts
modules/
node_modules/
public/
server/
  api/
  middleware/
  plugins/
  routes/
  utils/
nuxt.config.ts

What about the .config/ folder please ?

@Celibioux That is already supported.

@danielroe thank you for your answer ! I was asking about the conf folder because i've noticed that is Not mentioned in the V4 folder structure ☺

🔗 Linked issue
resolves #26444
📚 Description
This implements the new folder structure, if future.compatibilityVersion is set to 4 (which will be enabled by default when Nuxt v4 is released) - see #26925.
The main points (all only relevant when v4 compatibility is enabled):

the new Nuxt default srcDir is app/ by default, and most things are resolved from there.
serverDir now defaults to  <rootDir>/server rather than <srcDir>/server
modules and public are resolved relative to <rootDir> by default. If you want to revert this, set dir.modules to 'src/modules' and dir.public to 'src/public'.
a new dir.app is added, which is the directory we look for router.options.ts and spa-loading-template.html - this defaults to <srcDir>/ (under v4) and <srcDir>/app in v3 mode
I have not changed app.vue to main.vue (as in the RFC) to avoid additional breaking changes
in v4 mode, if there is no app/ directory, we default to previous behaviour (and restart if the app/ directory is added)

The v4 folder structure.
.output/
.nuxt/
app/
  assets/
  components/
  composables/
  layouts/
  middleware/
  pages/
  plugins/
  utils/
  app.vue
  router.options.ts
modules/
node_modules/
public/
server/
  api/
  middleware/
  plugins/
  routes/
  utils/
nuxt.config.ts

Since it duplicates the name app, it’s not nice, I suggest changing it to render since it renders the server and the client

🔗 Linked issue
resolves #26444
📚 Description
This implements the new folder structure, if future.compatibilityVersion is set to 4 (which will be enabled by default when Nuxt v4 is released) - see #26925.
The main points (all only relevant when v4 compatibility is enabled):

the new Nuxt default srcDir is app/ by default, and most things are resolved from there.
serverDir now defaults to  <rootDir>/server rather than <srcDir>/server
modules and public are resolved relative to <rootDir> by default. If you want to revert this, set dir.modules to 'src/modules' and dir.public to 'src/public'.
a new dir.app is added, which is the directory we look for router.options.ts and spa-loading-template.html - this defaults to <srcDir>/ (under v4) and <srcDir>/app in v3 mode
I have not changed app.vue to main.vue (as in the RFC) to avoid additional breaking changes
in v4 mode, if there is no app/ directory, we default to previous behaviour (and restart if the app/ directory is added)

The v4 folder structure.
.output/
.nuxt/
app/
  assets/
  components/
  composables/
  layouts/
  middleware/
  pages/
  plugins/
  utils/
  app.vue
  router.options.ts
modules/
node_modules/
public/
server/
  api/
  middleware/
  plugins/
  routes/
  utils/
nuxt.config.ts

/app/app.vue -> /app/render.vue Since it duplicates the name app, it’s not nice, I suggest changing it to render since it renders the server and the client

app.vue is a Vue Component, not a render function, so it doesn't make sense renaming it to render.vue.
Even when using TSX or setupSFC (VueMacros), the file is/contains a component and then you have a function to render the template.
Now, your concern about duplication is correct, but that's a standard pattern in DDD, for example Angular and NestJS:
NestJS:
src/
  domains/
    user/
  features/
    auth/
      auth.controller.ts
      auth.service.ts
      auth.module.ts
   app/
     app.module.ts
     app.controller.ts
     app.service.ts
   main.ts

Angular:
src/
  domains/
    user/
  features/
    auth/
      auth.component.ts
      auth.service.ts
      auth.component.html
   app/
     app.component.ts
     app.component.html
     app.service.ts
   main.ts

When you open a file in VSCode, it shows only the name, not the base dir, so let's say I have src/features/auth/module.ts and open it, it will show module.ts. what module!? 🤔🔎

🔗 Linked issue
resolves #26444
📚 Description
This implements the new folder structure, if future.compatibilityVersion is set to 4 (which will be enabled by default when Nuxt v4 is released) - see #26925.
The main points (all only relevant when v4 compatibility is enabled):
* the new Nuxt default `srcDir` is `app/` by default, and most things are resolved from there.

* `serverDir` now defaults to ` <rootDir>/server` rather than `<srcDir>/server`

* `modules` and `public` are resolved relative to `<rootDir>` by default. If you want to revert this, set `dir.modules` to `'src/modules'` and `dir.public` to `'src/public'`.

* a new `dir.app` is added, which is the directory we look for `router.options.ts` and `spa-loading-template.html` - this defaults to `<srcDir>/` (under v4) and `<srcDir>/app` in v3 mode

* I have not changed `app.vue` to `main.vue` (as in the RFC) to avoid additional breaking changes

* in v4 mode, if there is no `app/` directory, we default to previous behaviour (and restart if the `app/` directory is added)

The v4 folder structure.

Congrats on the new structure! It's amazing! 🔥😁💚👋🤩
I know Nuxt team don't want us to be hyped for Nuxt 4... but I am. 😎
"That's my secret Cap, I'm always hyped for Nuxt!"

🔗 Linked issue
resolves #26444
📚 Description
This implements the new folder structure, if future.compatibilityVersion is set to 4 (which will be enabled by default when Nuxt v4 is released) - see #26925.
The main points (all only relevant when v4 compatibility is enabled):

the new Nuxt default srcDir is app/ by default, and most things are resolved from there.
serverDir now defaults to  <rootDir>/server rather than <srcDir>/server
modules and public are resolved relative to <rootDir> by default. If you want to revert this, set dir.modules to 'src/modules' and dir.public to 'src/public'.
a new dir.app is added, which is the directory we look for router.options.ts and spa-loading-template.html - this defaults to <srcDir>/ (under v4) and <srcDir>/app in v3 mode
I have not changed app.vue to main.vue (as in the RFC) to avoid additional breaking changes
in v4 mode, if there is no app/ directory, we default to previous behaviour (and restart if the app/ directory is added)

The v4 folder structure.
.output/
.nuxt/
app/
  assets/
  components/
  composables/
  layouts/
  middleware/
  pages/
  plugins/
  utils/
  app.vue
  router.options.ts
modules/
node_modules/
public/
server/
  api/
  middleware/
  plugins/
  routes/
  utils/
nuxt.config.ts

/app/app.vue -> /app/render.vue Since it duplicates the name app, it’s not nice, I suggest changing it to render since it renders the server and the client

App/main.vue would be good as in the RFC and what Daniel said ^^

We'll go ahead and merge for testing. 🚨 Implementation details might change before the release of v4. 🚨

Imho the auto-fallback should be removed and causes more confusion than it's worth..
Users can opt out of it anyways by just changing the config? At least that would be verbose and nobody would have to guess if it's actually using the new structure or falling back..

@bernhardberger is there something not working, or inexplicable behaviour? if so, would you open a new issue with a reproduction?

@bernhardberger is there something not working, or inexplicable behaviour? if so, would you open a new issue with a reproduction?

Thing is: I have no clue if it's working.
See all my confusion, questions and answers by different guys pointing to contradicting YT "tutorials": https://github.com/nuxt/nuxt/discussions/20251#discussioncomment-10262761
I like the change, but it's (really) hard to gauge what goes where under which circumstances and what the implications of each are.
It's especially confusing what happens with modules, layers (why are layers not affected from the new structure?) as well as to what happens with other unmentioned directories in rootDir.

Where are the ,  and  folders supposed to fit in the Nuxt4 directory structure?
I suppose adjacent to ,  and  so that the data can be used in other .

Where are the /stores/ (types/, and /i18n/ folders supposed to fit in the Nuxt4 directory structure?
I suppose adjacent to /app/ and /server/  and /layers/ so that the data can be used in other /layers/.


nutrition info pushing down content

I changed the images to be horizontal.
Sent from my iPhone

On May 5, 2016, at 10:40 PM, Christina Rees<EMAIL_ADDRESS>wrote:
Closed #25 via 3a77ac8.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub


Dynamic max suggestions

This PR add a PreRun func to prompt command, to check if the terminal height is smaller that the supplied --max-suggestions flag value.
if It's the case, it changes the --max-suggestions value to $(terminal_height -1)

@hellt docs workflow doesn't trigger on merge PR now, right ?

Only on tagged release and docs- branches
On Sat, 24 Oct 2020, 04:27 Karim Radhouani<EMAIL_ADDRESS>wrote:

@hellt https://github.com/hellt docs workflow doesn't trigger on merge
PR now, right ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/karimra/gnmic/pull/201#issuecomment-715659002, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ABLKV5JDN4YYVPC2GFRUL5DSMI3SJANCNFSM4S4ZQAJA
.


[PE-D][Tester A] Badges on project website not linked to your repo's stats

Not related to user guide! But just wanted to flag that the badges on your website's home page are linked to the course repo's stats and not your own repo's! Probably need to change the links in the index.md file :)

Labels: severity.Low type.DocumentationBug
original: brennalaurentan/ped#6

Bless up


Observable Property dependent on other Observable Properties

Using Observable Property attribute, is it possible to have a Observable Property dependent on other Observable Properties?
`public partial class MyViewModel : ObservableObject
{
[ObservableProperty]
public bool propertyA;
[ObservableProperty]
public bool propertyB;

public bool PropertyC => PropertyA && PropertyB;

}
`

Where PropertyC is readonly and dependent on PropertyA and PropertyB...
Is this currently possible?  if not, is it already in the backlog or can it be submitted for new feature request?

Yes you can do this, you want to use the NotifyPropertyChangedFor  attribute.
Check out our documentation at:
https://learn.microsoft.com/en-gb/dotnet/communitytoolkit/mvvm/generators/observableproperty#notifying-dependent-properties


[2231] Add pgta route

Context
PGTA route
Changes proposed in this pull request
Added PGTA route
Guidance to review
Works as prototype

 [M] Add PGTA route

@defong I think this isn't being deployed to the review env because of conflicts

@defong I think this isn't being deployed to the review env because of conflicts

:face_with_head_bandage:
Needed to add deploy label

Get a 500 error on course details, not sure if this is specific to this route or if seeds need changing? It didn't seem to occur for other routes.

Looks good to me

@defong I get an error message when I select "Check this record." All the sections are complete.

@defong I get an error message when I select "Check this record." All the sections are complete.

Was discussed elsewhere as this is a wider bug in relation to diversities workflow.


Proof of concept for Localstack support

This commit adds a new Localstack module support. Localstack supports
multiple services, and we don't want to arbitrarily increase the number
of dependencies loaded in the test resources service, so this module
is split into a core module and support modules. The core module uses
service loading to locate local stack service providers. Those service
providers may add additional dependencies, and are the things which
can resolve extra properties. For example, there's an S3 provider which
can resolve the aws.s3.endpoint-override property.

Relates to #68

@alvarosanchez I added another example with DynamoDB. However, reading the docs I can't find any configuration property. So I made the test resources for Dynamo use aws.dynamodb.endpoint-override. I guess Micronaut AWS itself will require a number of changes?

All the AWS SDK v2 clients will need, at least, the following properties:

aws.accessKeyId
aws.secretKey
aws.region

There is no such aws.dynamodb.endpoint-override property being considered in micronaut-aws, and it seems to me that we need to honour it for all supported SDK clients.

All the AWS SDK v2 clients will need, at least, the following properties:

Yes, it's already what the core provider does. Then it delegates to services for S3, etc.

There is no such aws.dynamodb.endpoint-override property being considered in micronaut-aws, and it seems to me that we need to honour it for all supported SDK clients.

Yup.

@alvarosanchez was there a reason S3 was done alone vs doing it globally like the draft PR you commented on https://github.com/micronaut-projects/micronaut-aws/pull/831. Does someone just need to update that PR and switch S3's Client factory to use something common?

@alvarosanchez @melix  https://github.com/micronaut-projects/micronaut-aws/pull/831#issuecomment-1239986319

@scprek the reason was basically that I didn't realise that https://github.com/micronaut-projects/micronaut-aws/pull/831 was open. Thank you for moving it forward!

@melix @sdelamo @alvarosanchez Hoping I can help unblock https://github.com/micronaut-projects/micronaut-aws/pull/1456

@melix https://github.com/micronaut-projects/micronaut-aws/pull/1456 merged into 3.10.x


information error Something went wrong. Please try again later.

Hello,
whmcs version - Version: 8.5.1
Module Command Error
Cannot create service.
after that a create manully
error | Server not found
in whmcs admin error show

https://prnt.sc/3ZcsMpxtfyzY

error in client area side

https://prnt.sc/LZs6baT1GMgw
https://prnt.sc/gYnF0BSVcuqo

Thanks

Hey, we are about the release a new version of the module. Please open a new issue if this still persists.


deps: Temporarily use fork for @react-navigation/bottom-tabs

To get chrisbobbe/react-navigation@b2343cb25, which I've published
to NPM in<EMAIL_ADDRESS>It cherry-picks react-navigation/react-navigation@d87857e5d, which
is a compatibility fix for RN v0.65 that React Navigation published
in v6 but didn't backport to v5.
So this fix will become unnecessary when we're on React Navigation
6; that's issue #4936.
A small handful of things went wrong when building the .d.ts files
for the publish to NPM, so some TypeScript types are lost, which is
fine because we don't use TypeScript. But the runtime code looks
like it's updated in the ways we'd want and expect.

Thanks! Looks good -- merging.


latest Zanata translation changes in jbpm-form-modeler from 2016-09-05

Jenkins retest this please.

Jenkins retest this please.

+1


No option to input seconds

I have not found any material design datetimepicker which allows to input seconds as well. Will it be possible to add this functionality?
Also, is there an online demo for this component I can try?

There is currently no demo, will see if I can set something up at some point.
I am not sure if seconds input would be widely used. If you can provide a PR we can probably add it. I will most likely not implement this.

I'll see if I can work on a PR. Btw, the ability to input time including seconds is a common requirement in the Financial industry (especially in case of transactions) and right now there isn't a date time picker that allows that.


Alt+Space behavior

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

VS Code Version: any
OS Version: any Windows

This may be a rare case, but please consider:

Application window my by some unknown reason be hidden, collapsed into few-by-few pixels, removed almost outside the viewport
Usually, Alt+Space would easily resolve the issue, allowing to maximize the window and drag it to a better position.

You now say that "Mouse position is used to determine the behavior when triggering with Alt+Space, so the custom menu will appear if it sits on top of the title bar." - this might mean that the trick above would not work. Maybe this behavior could be applied also to cases when the cursor is outside the window or when the window has just received focus by Alt+[Shift]+Tab or Win+[Shift]+Tab, too? Please discuss this internally and decide how to proceed.

The behavior of alt-space with mouse position detection is explicitly designed to handle that case. When the window is off-screen or really small, the mouse is unlikely to be over the window, therefore, alt-space will trigger the native context menu which allows recovering/resizing/repositioning it.


Predictive interval fails for Dense model example

Hi, while trying to run the example of dense regression for fully connected NN, I run into an issue when I try to sample from the posterior of the model. I use exactly the commands as shown in the documentation.
My backend is pytorch,
Thank you so much !
# Compute 95% confidence intervals
lb, ub = model.predictive_interval(x_test, ci=0.95, batch_size=1)

# Plot em!
plt.fill_between(x_test[:, 0], lb[:, 0], ub[:, 0],
                 alpha=0.2, label='95% ci')
plt.plot(x, y, '.', label='Data')```

I get :

---------------------------------------------------------------------------
ValueError                                Traceback (most recent call last)
<ipython-input-61-eb2905895d26> in <module>
      3
      4 # Plot em!
----> 5 plt.fill_between(x_test[:, 0], lb[:, 0], ub[:, 0],
      6                  alpha=0.2, label='95% ci')
      7 plt.plot(x, y, '.', label='Data')

~/anaconda3/envs/causalode/lib/python3.8/site-packages/matplotlib/pyplot.py in fill_between(x, y1, y2, where, interpolate, step, data, **kwargs)
   2636         x, y1, y2=0, where=None, interpolate=False, step=None, *,
   2637         data=None, **kwargs):
-> 2638     return gca().fill_between(
   2639         x, y1, y2=y2, where=where, interpolate=interpolate, step=step,
   2640         **({"data": data} if data is not None else {}), **kwargs)

~/anaconda3/envs/causalode/lib/python3.8/site-packages/matplotlib/__init__.py in inner(ax, data, *args, **kwargs)
   1445     def inner(ax, *args, data=None, **kwargs):
   1446         if data is None:
-> 1447             return func(ax, *map(sanitize_sequence, args), **kwargs)
   1448
   1449         bound = new_sig.bind(ax, *args, **kwargs)

~/anaconda3/envs/causalode/lib/python3.8/site-packages/matplotlib/axes/_axes.py in fill_between(self, x, y1, y2, where, interpolate, step, **kwargs)
   5299     def fill_between(self, x, y1, y2=0, where=None, interpolate=False,
   5300                      step=None, **kwargs):
-> 5301         return self._fill_between_x_or_y(
   5302             "x", x, y1, y2,
   5303             where=where, interpolate=interpolate, step=step, **kwargs)

~/anaconda3/envs/causalode/lib/python3.8/site-packages/matplotlib/axes/_axes.py in _fill_between_x_or_y(self, ind_dir, ind, dep1, dep2, where, interpolate, step, **kwargs)
   5221                     f"must have the same size as {ind} in {func_name}(). This "
   5222                     "will become an error %(removal)s.")
-> 5223         where = where & ~functools.reduce(
   5224             np.logical_or, map(np.ma.getmask, [ind, dep1, dep2]))
   5225

ValueError: operands could not be broadcast together with shapes (101,) (101000,)

Hi!  Which matplotlib version are you using?  If you're using a newer one, it seems like something's broke with the latest release of matplotlib (I actually wasn't able to even import the package past 3.3.4 😕 , was getting this error).  Try using any matplotlib version <=3.3.4, that seemed to work for me (see this google colab for a working example and the versions used).
That said, you've made me realize there was a separate unrelated bug in that example!  Fixed it here https://github.com/brendanhasz/probflow/pull/65 Apparently torch doesn't like casting a torch tensor to a torch tensor (I think maybe it was cutting off the gradient propagation? But not sure tbh.  But anyway the updated example works).  So basically just make sure you have the x = torch.tensor(x) line only in your top-level module (which in that example is the DenseRegression class).
Thanks for letting me know about the error and hope that helps! 😄


Added devlabs

PR Template 🚀
🛠 Proposed Changes
Added Devlabs in active repos
🖼 Screenshots
Not required.
📝 Notes for Reviewers
Not required.
Checklist ✅

[x] All tests pass successfully.
[x] Code adheres to the project's coding standards.
[x] Documentation is updated to reflect the changes.
[x] No sensitive information is inadvertently exposed.
[x] Commit history is clear and concise.

Reviewer Tasks 🕵
Not required.
Additional Context ℹ
Not required.

Hi @harshjais369, can you please raise your PR for the main branch. Currently the raised PR is for the dev branch

Hey @anand346 , thank you for pointing out this. I've raised another pull request #70 , and added few more active repo links in it. Kindly check it out at your convenience time and let me know if still any adjustment remains there.


feat: camera control components

Related PRs:

https://github.com/decentraland/js-sdk-toolchain/pull/990
https://github.com/decentraland/unity-explorer/pull/1744

We've developed a similar implementation and noticed some differences in our approaches. Here's a brief comparison of the features:

feature
this implementation
protocol squad implementation

look at a target
supported
not currently supported (can be implemented by users)

specify transition
supported
not currently supported

select by area
not currently supported (can be implemented by users)
supported

allow user to orient camera (with constraints)
not currently supported
supported

zoom level
not currently supported
supported

It seems like we could combine our efforts to create a more robust solution. Going through item by item:

The transition feature looks useful, i think we should take it as is.

The "look at a target" feature is similar to existing PbBillboard functionality (which also offers fuller control over the axes). It might make sense to extend the PbBillboard with a target entity, or develop a new PbLookAt component with similar functionality. This could provide broader utility beyond just targeting cameras, such as turning NPCs to face the player.

For select by area, i think using the existing cameraModeArea infrastructure has some advantages

it allows for easier setup if you want different cameras when the player is in different locations
it makes clearer the interactions between the "virtual cameras" and cameraModeAreas - how does it work in your implementation if a user enters a force-first-person area while the camera is set to another entity?

The user camera controls i think are useful, but could be implemented in unity/alpha later.

The zoom level, we use the camera entity's scale.z component to specify a zoom, and the min/max range is for the user to zoom in/out manually as well.

What do you think about potentially merging our efforts to create a more comprehensive solution?

What do you think about potentially merging our efforts to create a more comprehensive solution?

Hello Rob, so from what I understand if we go with your proposal we would be scratching our implementation completely and basically implementing support for your approach and adding the transition feature only right?
In my opinion the CameraModeArea should only change the camera mode between First or Third person camera. And for more vesatile controls of the camera through the SDK, something separate has to be in place. Because the CameraModeArea limits/binds the camera controls capabilities of the scene to the player position and that doesn't need to be that way... if we can give more freedom to the scene to control the camera without having to have the player in a specific location.
Regarding the point mentioned of "allows for easier setup if you want different cameras when the player is in different locations", that can be done with a trigger area (or player pos checks) to change the camera in specific locations.
The same "easier setup" argument could be said about having the LookAt property in the VirtualCamera: the creator only has to reference an entity in there and the camera will always look at it, as easy as that. However I completely agree on the value of having a new target property in the Billboard component, that could be implemented separately and it's also super useful.
Regarding the interactions between the CameraModeArea and the VirtualCamera+MainCamera components in our approach, the MainCamera always has the priority, the CameraModeArea functionality starts running again when there is no "active virtual camera" (when MainCamera.virtualCameraEntity == 0)

The user camera controls i think are useful, but could be implemented in unity/alpha later.

If you mean the demo video, just to clarify it was just manipulating a VirtualCamera entity's transform with the global input, nothing related to the new components.
I do like your approach features of zoom level and allowing user input with constraints (this last one we also though to implement it in the future in the VirtualCamera itself).
I'm all in favor of doing a joint effort on the protocol layer additions/changes, it's just that in this case I believe the VirtualCameras + MainCamera (originally though of as "CameraDirector") components is more versatile for creators (and your approach features we are missing here could be built on top of this in a future iteration).

Here is the test scene I've been working with in case you want to take a look at the sdk API and usage for these new components: https://github.com/decentraland/sdk7-test-scenes/pull/13

the CameraModeArea limits/binds the camera controls capabilities of the scene to the player position

one can always make an infinite area, then it is exactly the same as using a central component. adding a separate way to control the camera for cinematic cameras only seems confusing to me. cinematic cams and forced 1st/3rd-person cams can't operate at the same time, so why not use the same mechanism for specifying them both?
then, if we started today, it might be better to not use cameraModeArea and use a global component. but given that we have the cameraModeArea already i would say it's better to extend it (or perhaps deprecate it entirely and put all the functionality into a global component).

We've developed a similar implementation and noticed some differences in our approaches. Here's a brief comparison of the features:
feature	this implementation	protocol squad implementation
look at a target	supported	not currently supported (can be implemented by users)
specify transition	supported	not currently supported
select by area	not currently supported (can be implemented by users)	supported
allow user to orient camera (with constraints)	not currently supported	supported
zoom level	not currently supported	supported
It seems like we could combine our efforts to create a more robust solution. Going through item by item:

The transition feature looks useful, i think we should take it as is.

The "look at a target" feature is similar to existing PbBillboard functionality (which also offers fuller control over the axes). It might make sense to extend the PbBillboard with a target entity, or develop a new PbLookAt component with similar functionality. This could provide broader utility beyond just targeting cameras, such as turning NPCs to face the player.

For select by area, i think using the existing cameraModeArea infrastructure has some advantages

it allows for easier setup if you want different cameras when the player is in different locations
it makes clearer the interactions between the "virtual cameras" and cameraModeAreas - how does it work in your implementation if a user enters a force-first-person area while the camera is set to another entity?

The user camera controls i think are useful, but could be implemented in unity/alpha later.

The zoom level, we use the camera entity's scale.z component to specify a zoom, and the min/max range is for the user to zoom in/out manually as well.

What do you think about potentially merging our efforts to create a more comprehensive solution?

For content creators having both VirtualCamera & MainCamera is really useful and easy to use. If you see pravus scene-templates is quite intuitive how they work, and they have tons of possibilities. I wont change them for a single PBCameraModeArea.. Whats the main reason on changing the whole approach of this PR for your already-supported implementation ?
For the not supported capabilties, we can re-iterate them in the future, is out of our scope now, and can be added later.
Also in the future if we want to change the lookAt to a PbLookAt component, (because there are more use cases that we want), we can deprecated that property, and start using that component, but using a Billboarcd component is way more complex and for now we don't want those features.
There is no need to do all it now, maybe with this aproach we are good enough, and its all that we need. It doesnt have to be perfect and cover all the cases that we may not use.

I'm merging this PR that adds MainCamera and VirtualCamera, since @nearnshaw and @leanmendoza had already talked about the Foundation implementation of the camera controls feature and already agreed that it would be a different implementation than the one previously accomplished by the protocol squad, both implementations can co-exist in the protocol layer and there is no problem with that.
In future iterations we can for sure enrich these components by not only adding the Foundation's planned extensions (camera transition overrides in MainCamera, FOV and similar properties in VirtualVamera) but also plan for adding other properties like the useful ones the protocol squad suggested (zoom, allowing input for rotation, extending the Billboard with a target property).
For next features we'll try to review deeper the potential protocol changes during features design, taking advantage of the weekly meeting between both teams, to try and reach a stronger agreement and also add value as a joint effort from both sides.


Contrastive loss

Need to setup BevoEncoder for MLM, or use off the shelf encoder.
[CLS] good  . [CLS] prompt > [CLS]. bad  [CLS].prompt
Per token basis like Electra?
What corruptions are allowed? As long we use the tokens from the data is anything fine?

Didn't really work?

We didn't really fully explore the space...


C# Client ProblemDetails from Validation Error

I'm building onto the Clean Architecture and Blazor solutions from Jason Taylor. After hitting a stumbling block, went back to his To Do example to see if it was working there, and it does not seem to.
With the PUT command, there is the following header on the Action:
[ProducesResponseType(StatusCodes.Status400BadRequest)]

This is not on the POST Action, even though a BadRequest can also be thrown by it. Now, after debugging, I found this in the generated C# Client code for the PUT Action, that is not in the POST Action, and this is where it gets interesting:
if (status_ == 400)
{
      var objectResponse_ = await ReadObjectResponseAsync<ProblemDetails>(response_, headers_, cancellationToken).ConfigureAwait(false);
      if (objectResponse_.Object == null)
      {
          throw new ApiException("Response was null which was not expected.", status_, objectResponse_.Text, headers_, null);
      }
      throw new ApiException<ProblemDetails>("A server side error occurred.", status_, objectResponse_.Text, headers_, objectResponse_.Object, null);
}

In the POST, it drops down into just reading the Content as a String, and shoving it into the Response, which works nicely to take it out again. But for the PUT, weirdly, when debugging, the objectResponse shows me an Object value of "null" but it seems to have the right ProblemDetails, but just in the Result field instead of the Response; Response is null, so I don't know what the Validation Errors are therefore.
So my workaround, is to remove the ProducesResponseType attribute, as per the POST method (they both can throw Validation errors, so not sure why the attribute for BadRequest was on one and not the other?).
Obviously, I think it's better to have the appropriate errors in the Documentation, but the generated C# Client then doesn't work for me, any advice would be appreciated?

Hello @gabs247 ,
I've faced the same issue, where the error response returned to the JavaScript client is getting casted to ProblemDetails which doesn't have the same fields as the returned response.
In order to overcome this issue you need to replace the attribute in the C# controller from:
[ProducesResponseType(StatusCodes.Status400BadRequest)]
To
[ProducesResponseType(typeof(BadRequestResult), StatusCodes.Status400BadRequest)]
By doing so, the generated TS client will parse the error response returned as is.

Thanks @Mcheimech, but unfortunately this still doesn't seem to work for me?
The code generated is this:
                        if (status_ == 400)
                        {
                            var objectResponse_ = await ReadObjectResponseAsync<FileResponse>(response_, headers_, cancellationToken).ConfigureAwait(false);
                            if (objectResponse_.Object == null)
                            {
                                throw new ApiException("Response was null which was not expected.", status_, objectResponse_.Text, headers_, null);
                            }
                            throw new ApiException<FileResponse>("A server side error occurred.", status_, objectResponse_.Text, headers_, objectResponse_.Object, null);
                        }

where a FileResponse is generated:
    public partial class FileResponse : System.IDisposable
    {
        private System.IDisposable _client;
        private System.IDisposable _response;

        public int StatusCode { get; private set; }

        public System.Collections.Generic.IReadOnlyDictionary<string, System.Collections.Generic.IEnumerable<string>> Headers { get; private set; }

        public System.IO.Stream Stream { get; private set; }

        public bool IsPartial
        {
            get { return StatusCode == 206; }
        }

        public FileResponse(int statusCode, System.Collections.Generic.IReadOnlyDictionary<string, System.Collections.Generic.IEnumerable<string>> headers, System.IO.Stream stream, System.IDisposable client, System.IDisposable response)
        {
            StatusCode = statusCode;
            Headers = headers;
            Stream = stream;
            _client = client;
            _response = response;
        }

        public void Dispose()
        {
            Stream.Dispose();
            if (_response != null)
                _response.Dispose();
            if (_client != null)
                _client.Dispose();
        }
    }

Maybe on to the right track, just not sure what to cast it to to get it return a useful result?

@gabs247 try with "Wrap DTO exceptions in a SwaggerException instance" option turned off in the "TypeScript client" settings in NSwagStudio.