ISSUE: iCloud IMAP server not supported

Describe the bug
Using iCloud's IMAP server (imap.mail.me.com) will never find and process emails because IMAP's server does not support RFC822 fetch protocol.
The solution is to switch to BODY[]. I've done this in my local helpers.py and it works!
See: https://stackoverflow.com/questions/75444763/python-imaplib-fetching-icloud-mail-rfc822-not-working
I'll open a PR to fix as soon as I'm able.
Environment (please complete the following information):

OS: Docker
Type of device: Synology
Home Assistant version: 2024.11.2
Hassio/Docker/Core? Docker
Component version: 0.4.1

Logs
When using iCloud, the FETCH result will always look like this:
2024-11-18 10:36:51.087 DEBUG (SyncWorker_9) [custom_components.mail_and_packages.helpers] email_search value: ('OK', [b'1'])

Screenshots
N/A
Additional context
The fix may require introducing a new configuration variable to switch from RFC822 to BODY[] fetch parameters. Switching the core code to BODY[] for all mail servers may break backwards compatibility.

hi @rscheuermann - would you mind post more detail on how you resolved this please?

Anywhere email_fetch is called the (RFC822) will need to be adjusted in the call.
Plan is to modify the function to check if you're using iCloud's monstrosity of an IMAP server, and adjust the call accordingly in a single spot.

Please download the file:
https://github.com/firstof9/Home-Assistant-Mail-And-Packages/blob/fix-1005/custom_components/mail_and_packages/helpers.py
and place it in your custom_components/mail_and_packages/ directory and reload HA.
Please let me know if that solves your iCloud troubles.

Actually I'll drop this in a beta release for testing.

Thanks, I am getting a 404 - page not found when trying to access the fix-1005 link in the previous post.  Did it get pushed someplace else?

I dropped it into the latest beta available for upgrade via HACS

Just tried the install with the latest beta and it installed without any issues!  Thanks!!

No errors when it went looking for your mail?

@firstof9 im getting the following error:
Invalid config
The following integrations and platforms could not be set up:

[mail_and_packages](https://github.com/moralmunky/Home-Assistant-Mail-And-Packages)(http://homeassistant.local:8123/config/logs?filter=mail_and_packages))
Please check your config and [logs](http://homeassistant.local:8123/config/logs).

and the logs show:
`Log details (ERROR)
Logger: homeassistant.setup
Source: setup.py:334
First occurred: 10:13:59 AM (1 occurrences)
Last logged: 10:13:59 AM
Setup failed for custom integration 'mail_and_packages': Unable to import component: Exception importing custom_components.mail_and_packages
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/loader.py", line 1074, in _get_component
ComponentProtocol, importlib.import_module(self.pkg_path)
~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/util/loop.py", line 200, in protected_loop_func
return func(*args, **kwargs)
File "/usr/local/lib/python3.13/importlib/init.py", line 88, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "", line 1387, in _gcd_import
File "", line 1360, in _find_and_load
File "", line 1331, in _find_and_load_unlocked
File "", line 935, in _load_unlocked
File "", line 1022, in exec_module
File "", line 488, in _call_with_frames_removed
File "/config/custom_components/mail_and_packages/init.py", line 31, in
from .helpers import process_emails
File "/config/custom_components/mail_and_packages/helpers.py", line 100
Home-Assistant-Mail-And-Packages/custom_components/mail_and_packages/helpers.py at dev · firstof9/Home-Assistant-Mail-And-Packages
^
SyntaxError: invalid character '·' (U+00B7)
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/loader.py", line 1014, in async_get_component
comp = await self.hass.async_add_import_executor_job(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
self._get_component, True
^^^^^^^^^^^^^^^^^^^^^^^^^
)
^
File "/usr/local/lib/python3.13/concurrent/futures/thread.py", line 58, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/src/homeassistant/homeassistant/loader.py", line 1085, in _get_component
raise ImportError(f"Exception importing {self.pkg_path}") from err
ImportError: Exception importing custom_components.mail_and_packages
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/loader.py", line 1074, in _get_component
ComponentProtocol, importlib.import_module(self.pkg_path)
~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/util/loop.py", line 200, in protected_loop_func
return func(*args, **kwargs)
File "/usr/local/lib/python3.13/importlib/init.py", line 88, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "", line 1387, in _gcd_import
File "", line 1360, in _find_and_load
File "", line 1331, in _find_and_load_unlocked
File "", line 935, in _load_unlocked
File "", line 1022, in exec_module
File "", line 488, in _call_with_frames_removed
File "/config/custom_components/mail_and_packages/init.py", line 31, in
from .helpers import process_emails
File "/config/custom_components/mail_and_packages/helpers.py", line 100
Home-Assistant-Mail-And-Packages/custom_components/mail_and_packages/helpers.py at dev · firstof9/Home-Assistant-Mail-And-Packages
^
SyntaxError: invalid character '·' (U+00B7)
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/setup.py", line 334, in _async_setup_component
component = await integration.async_get_component()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/loader.py", line 1034, in async_get_component
self._component_future.result()
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
File "/usr/src/homeassistant/homeassistant/loader.py", line 1026, in async_get_component
comp = self._get_component()
File "/usr/src/homeassistant/homeassistant/loader.py", line 1085, in _get_component
raise ImportError(f"Exception importing {self.pkg_path}") from err
ImportError: Exception importing custom_components.mail_and_packages`
and
`Log details (ERROR)
Logger: homeassistant.loader
Source: loader.py:1074
First occurred: 10:13:59 AM (2 occurrences)
Last logged: 10:13:59 AM
Unexpected exception importing component custom_components.mail_and_packages
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/loader.py", line 1074, in _get_component
ComponentProtocol, importlib.import_module(self.pkg_path)
~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/util/loop.py", line 200, in protected_loop_func
return func(*args, **kwargs)
File "/usr/local/lib/python3.13/importlib/init.py", line 88, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "", line 1387, in _gcd_import
File "", line 1360, in _find_and_load
File "", line 1331, in _find_and_load_unlocked
File "", line 935, in _load_unlocked
File "", line 1022, in exec_module
File "", line 488, in _call_with_frames_removed
File "/config/custom_components/mail_and_packages/init.py", line 31, in
from .helpers import process_emails
File "/config/custom_components/mail_and_packages/helpers.py", line 100
Home-Assistant-Mail-And-Packages/custom_components/mail_and_packages/helpers.py at dev · firstof9/Home-Assistant-Mail-And-Packages
^
SyntaxError: invalid character '·' (U+00B7)`

Correct, no errors found when it went looking through email and I received my first mail notifications, USPS.

@firstof9 im getting the following error:

Looks like your download is corrupted. You can grab the zip file from the releases and manually extract over the directory.

Looks like your download is corrupted.

@firstof9  - So it was :), why i didn't spot that - okay updated without errors, guess i'll have to order something from amazon now to test it :)

Hi @firstof9 - so I've got an Order Confirmation email sitting in my inbox, should I be expecting that to be picked up by the sensor.mail_amazon_packages ? if so, this is not being picked up.

should I be expecting that to be picked up by the sensor.mail_amazon_packages ?

Only on the day of it's expected arrival.

hi @firstof9 - so got the:

Out for delivery
Your package will arrive
Today

email, however the sensor.mail_amazon_packages is showing as below (has the order number, but saying 0 Package(s))

There's no parsing for an amazon email stating "out for delivery".

Ah right, sorry, just my lack of understanding then - thanks for the help - could this be a future update :)

could this be a future update

Not really, I've never seen an "out for delivery" email from amazon ever.
Amazon parsing checks the date from the order confirmation email and uses that date to tick up the counter.

oh right, maybe it's a UK only thing coming form amazon.co.uk, can pass on if you want? - but got the package delivered and sensor.mail_amazon_packages_delivered updated as expected to show 1 package(s); still a bit confused as to what sensor.mail_amazon_packages does though.

till a bit confused as to what sensor.mail_amazon_packages does though.

I've covered it in the wiki


UI change faq section

UI CHANGE FAQ Section
The faq Section require a border as the background and button has very less contrast.
Actual:

Expected:

hi @karthik-nair-20, I have marked this pr as invalid as it is modifying the components in a way that doesn't align with the existing UI design, it is not solving any problems and it's a one liner.


Newlines not preserved in some circumstances (lists?)

I've observed some discrepancies in the server's formatting of new RSS entries vs. what appears in an RSS reader. Namely, the text preview lacks newlines where they exist in the original text. I think this may only occur with lists, but I don't have other feeds' outputs on hand to verify.
The view of a particular article in my RSS reader:

The corresponding output from the server:

The issue is that your server is stripping the formatting out of the post.  etc aren't allowed markup on many ActivityPub servers; certainly not on regular Mastodon. (I am not sure what system you are on.)
Eventually I would like more of these services to fully support messages coming in tagged as an Article in ActivityPub. The idea is that if Mastodon (for example) sees an Article come in (instead of a Note, which it currently converts things to), it would render it as full text article with at least minimum html formatting.
I originally had some rules that would turn bullet points into text bullets so they would come in like
- one
- two
-three

But the problem with that is false positives. It basically messes up a lot of the time. What we really need is full Article support.


My custom week do not work

Describe your bug here.
I made the file .json, put it in the weeks folder with the name of week1 and it didn't show up the week in story mode, also when I put the week icon in the file name .json it says that there is no png file with that name
Command Prompt/Terminal logs (if existing)
No response
Are you modding a build from source or with Lua?
Source
What is your build target?
Windows
Did you edit anything in this build? If so, mention or summarize your changes.
No

you might have the same problem with this
#14851

Also where did you put the week? If it's on the mods folder then it's making a conflict since you named the custom .json week file "week1" and it's breaking the assets folder

you can't name your week any of the existing weeks, otherwise it will not show up


Allow for evaluating the posterior.

At the moment you can evaluate the posterior by calling log_posterior_test = my_posterior.create_link(parameters_test).posterior, which is a little roundabout.
This could be replaced with a shortcut.

Do you think it's okay to wrap the statement in your message above, into a method of the posterior class ?

Hi @SaiAakash thanks for picking up on this.
Yes, I think that would be ideal. Maybe as a method Posterior.logpdf(x), and perhaps also a __call__() method that just evokes logpdf.

The logpdf method you have suggested is a separate from the Posterior.posterior_eval function right ?

@SaiAakash No I meant that the method should be called logpdf, to conform to the scipy convention.

Got it !

Fixed with https://github.com/mikkelbue/tinyDA/pull/52


Add dual annotation

Codecov Report

Merging #384 (1312f1f) into main (b6fb657) will decrease coverage by 0.14%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #384      +/-   ##
==========================================
- Coverage   76.19%   76.04%   -0.15%
==========================================
  Files          17       17
  Lines        4074     4066       -8
==========================================
- Hits         3104     3092      -12
- Misses        970      974       +4

Impacted Files
Coverage Δ

src/Enzyme.jl
86.64% <ø> (-0.05%)
:arrow_down:

src/compiler/orcv1.jl
76.92% <0.00%> (-3.85%)
:arrow_down:

src/compiler/validation.jl
64.35% <0.00%> (-0.67%)
:arrow_down:

src/compiler.jl
75.27% <0.00%> (-0.07%)
: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 b6fb657...1312f1f. Read the comment docs.

Maybe we should update the examples and tests?


Sysutil: add utilities to get stack traces

Set up signal handlers in all the command line utils so that if they
crash, they will print stack traces that will help track down CI or
user-side failure cases.
This relies on Boost >= 1.65 for its stacktrace library. When built
against older versions of boost, stacktrace() will return an empty
string and the stacktrace-printing signal handles will have no effect.
C'est la vie.

LGTM!


/neck/neck1/Concat: dimensions not compatible for concatenation(When I convert dynamic onnx to engine file)

🐛 Describe the bug
When I convert dynamic onnx to engine file, it happen
Error[4]: [graphShapeAnalyzer.cpp::processCheck::587] Error Code 4: Internal Error (/neck/neck1/Concat: dimensions not compatible for concatenation)
Error[2]: [builder.cpp::buildSerializedNetwork::636] Error Code 2: Internal Error (Assertion engine != nullptr failed. )
Versions
[12/15/2023-03:47:54] [I] TensorRT version: 8.4.3
[12/15/2023-03:47:55] [I] [TRT] [MemUsageChange] Init CUDA: CPU +574, GPU +0, now: CPU 583, GPU 69279 (MiB)
[12/15/2023-03:47:56] [I] [TRT] [MemUsageChange] Init builder kernel library: CPU +551, GPU +132, now: CPU 1153, GPU 69411 (MiB)
[12/15/2023-03:47:56] [I] Start parsing network model
[12/15/2023-03:47:56] [I] [TRT] ----------------------------------------------------------------
[12/15/2023-03:47:56] [I] [TRT] Input filename:   nas_l_dynamic.onnx
[12/15/2023-03:47:56] [I] [TRT] ONNX IR version:  0.0.7
[12/15/2023-03:47:56] [I] [TRT] Opset version:    14
[12/15/2023-03:47:56] [I] [TRT] Producer name:    pytorch
[12/15/2023-03:47:56] [I] [TRT] Producer version: 2.0.1
[12/15/2023-03:47:56] [I] [TRT] Domain:
[12/15/2023-03:47:56] [I] [TRT] Model version:    0
[12/15/2023-03:47:56] [I] [TRT] Doc string:
[12/15/2023-03:47:56] [I] [TRT] ----------------------------------------------------------------

sg version is 3.3.0

I assume you are trying to export YoloNAS model.
Since model.export(..) does not support export with dynamic axis at the moment you probably have your own export code.
Can you please provide a code snippet how exactly you are exporting a model with dynamic axis?
A few things that immediately come to my mind:

You may want to updated to latest SG, as there were some fixes to model & export code
TRT 8.4 is pretty old and my recommendation to use the 8.5 or 8.6 if possible as they have better support of ONNX operations
After export of ONNX file it's a good idea to run it through onnxsim. Sometimes it can drop some unnecessary stuff from the graph that may be confusing old TRT.


Add Ruby 2.3.1 to Travis file

Ensure Pageflow works with the latest ruby version

Coverage remained the same at 99.156% when pulling 7539fd0fa519bd9e44a36b9fff2dc0141d928f15 on tf:ruby-2-3 into 6b9807b4e1883e74e9bad259b7ba3f4398e112d6 on codevise:master.


DB2Rest and tests should be agnostic of FileSystem used (Windows, Linux, etc.)

Currently tests will fail on Windows systems (maybe others) because of path errors such as:
[ERROR]   PgJsonFileCreateControllerTest.createDirectorViaUpload:71 »
   InvalidPath Illegal char <:> at index 2: /F:/GitHubRepos/db2rest/api-rest/target/test-classes/testdata/director.json

This is because we're not agnostic enough for the filesystem through java.nio methods.
According to docs for java.nio.file.Path.of(), we should be agnostic of filesystems since we are providing a library, and instead use an existing Path instance as an anchor as explained:

The Path is obtained by invoking the getPath method of the default FileSystem.
Note that while this method is very convenient, using it will imply an assumed reference to the default FileSystem and limit the utility of the calling code. Hence it should not be used in library code intended for flexible reuse. A more flexible alternative is to use an existing Path instance as an anchor, such as:
Path dir = ...
Path path = dir.resolve("file");

Full log of current ERRORS on Windows building:
[ERROR]   MySQLJsonFileCreateControllerTest.createDirectorViaUpload:71 » InvalidPath Illegal char <:> at index 2: /F:/GitHubRepos/db2rest/api-rest/target/test-classes/testdata/director.json
[ERROR]   MySQLJsonFileCreateControllerTest.createFilmsViaUpload:91 » InvalidPath Illegal char <:> at index 2: /F:/GitHubRepos/db2rest/api-rest/target/test-classes/testdata/BULK_CREATE_FILM_REQUEST.json
[ERROR]   MySQLJsonFileCreateControllerTest.uploadActorFileNonJsonArray:56 » InvalidPath Illegal char <:> at index 2: /F:/GitHubRepos/db2rest/api-rest/target/test-classes/testdata/CREATE_ACTOR_REQUEST.json
[ERROR]   MySQLJsonFileCreateControllerTest.uploadActorsFile:36 » InvalidPath Illegal char <:> at index 2: /F:/GitHubRepos/db2rest/api-rest/target/test-classes/testdata/actor.json
[ERROR]   OracleJsonFileCreateControllerTest.createDirectorViaUpload:71 » InvalidPath Illegal char <:> at index 2: /F:/GitHubRepos/db2rest/api-rest/target/test-classes/testdata/director.json
[ERROR]   OracleJsonFileCreateControllerTest.createFilmsViaUpload:91 » InvalidPath Illegal char <:> at index 2: /F:/GitHubRepos/db2rest/api-rest/target/test-classes/testdata/BULK_CREATE_FILM_REQUEST.json
[ERROR]   OracleJsonFileCreateControllerTest.uploadActorFileNonJsonArray:56 » InvalidPath Illegal char <:> at index 2: /F:/GitHubRepos/db2rest/api-rest/target/test-classes/testdata/CREATE_ACTOR_REQUEST.json
[ERROR]   OracleJsonFileCreateControllerTest.uploadActorsFile:36 » InvalidPath Illegal char <:> at index 2: /F:/GitHubRepos/db2rest/api-rest/target/test-classes/testdata/actor.json
[ERROR]   PgJsonFileCreateControllerTest.createDirectorViaUpload:71 » InvalidPath Illegal char <:> at index 2: /F:/GitHubRepos/db2rest/api-rest/target/test-classes/testdata/director.json
[ERROR]   PgJsonFileCreateControllerTest.createFilmsViaUpload:91 » InvalidPath Illegal char <:> at index 2: /F:/GitHubRepos/db2rest/api-rest/target/test-classes/testdata/BULK_CREATE_FILM_REQUEST.json
[ERROR]   PgJsonFileCreateControllerTest.uploadActorFileNonJsonArray:56 » InvalidPath Illegal char <:> at index 2: /F:/GitHubRepos/db2rest/api-rest/target/test-classes/testdata/CREATE_ACTOR_REQUEST.json
[ERROR]   PgJsonFileCreateControllerTest.uploadActorsFile:36 » InvalidPath Illegal char <:> at index 2: /F:/GitHubRepos/db2rest/api-rest/target/test-classes/testdata/actor.json
[INFO]
[ERROR] Tests run: 342, Failures: 6, Errors: 70, Skipped: 9


chore(ci): protect master branch during releases

Proposed changes
Our release failed because a PR was merged during a release.
To avoid that, we should prevent commits from going into master during a release.
To do that, I limit who can commit to master to our bot.
To use the bot trusted identity, I need more convoluted ways of committing:

create the Git Tree and make it known to GitHub.
create a commit via GitHub APIs using the Git Tree
point master on the commit.

Testing
I will have to trigger a new release soonish after we complete a stable one to check the process.

Back to draft, there's quite some stuff to fix


Run list_contents.sh easily

Make sure can run .sh file just by tapping on it (or apk if necessary)

Have to open in Shell Script Editor


aws: use element() to look up controller subnet_id with wrap around

This PR re-introduces element in the AWS modules to look up subnet IDs for controllers. In these situations, element's wrap around behavior is required. Otherwise, if length(var.controller_count) > length(aws_subnet.public.*.id), Terraform fails.
With controller_count = 5 in us-west-2, for example:
Error: Invalid index

  on .terraform/modules/green.typhoon/aws/container-linux/kubernetes/controllers.tf line 52, in resource "aws_instance" "controllers":
  52:   subnet_id = aws_subnet.public.*.id[count.index]
    |----------------
    | aws_subnet.public is tuple with 4 elements
    | count.index is 4

The given key does not identify an element in this collection value.

Testing
I merged this change into our fork and can successfully plan.
Related
This regression was introduced in https://github.com/poseidon/typhoon/pull/605. I reviewed that and verified that the other cases use the same value for count in both resources and should raise index errors if the lists are not equal in length.

Thanks!


What is the proper range of  NT xent loss when the network converges?

After 80 epoch,my nt xent loss is about 5.I am not sure whether the network has learnt well.

Hello guys, that is a general message to say that I have refactored the whole project. Please I a look at the new impl and free to submit PR if you find any bugs. Thanks.

Hello guys, that is a general message to say that I have refactored the whole project. Please I a look at the new impl and free to submit PR if you find any bugs. Thanks.

After 80 epoch,my nt xent loss is about 5.I am not sure whether the network has learnt well.

I'm also meeting this problem, is it normal ? or how do you fix it?


GPU/SPIR-V codegen should lower hal.interface.workgroup.size ops.

Today it does not seem to lower to WorkgroupSize (SPIR-V) or blockDim (CUDA):
tools/test/iree-benchmark-executable.mlir:56:27: error: failed to legalize operation 'hal.interface.workgroup.size'
      %workgroup_size_x = hal.interface.workgroup.size[0] : index
                          ^
tools/test/iree-benchmark-executable.mlir:56:27: note: see current operation: %12 = "hal.interface.workgroup.size"() {dimension = 0 : index} : () -> index
tools/test/iree-benchmark-executable.mlir:44:1: error: failed to run translation of source executable to target executable for backend #hal.executable.target<"vulkan", "vulkan-spirv-fb", {spirv.target_env = #spirv.target_env<#spirv.vce<v1.3, [Shader, GroupNonUniform], [SPV_KHR_storage_buffer_storage_class, SPV_KHR_variable_pointers]>, api=Vulkan, #spirv.resource_limits<max_compute_workgroup_size = [128, 128, 64], subgroup_size = 64, cooperative_matrix_properties_khr = []>>}>

Supporting this is needed to write portable inputs that lower to all backends (we can't use gpu dialect ops).
This input with iree-compile --iree-hal-target-backends=vulkan-spirv or =cuda fails in the same way, passes on llvm-cpu:
#pipeline_layout = #hal.pipeline.layout<push_constants = 0, sets = [
  #hal.descriptor_set.layout<0, bindings = [
    #hal.descriptor_set.binding<0, storage_buffer>,
    #hal.descriptor_set.binding<1, storage_buffer>,
    #hal.descriptor_set.binding<2, storage_buffer>
  ]>
]>
hal.executable.source public @executable {
  hal.executable.export public @elementwise_mul ordinal(0) layout(#pipeline_layout) attributes {
    workgroup_size = [1 : index, 1 : index, 1 : index]
  } {
  ^bb0(%device: !hal.device):
    // UNUSED
    %c1 = arith.constant 1 : index
    hal.return %c1, %c1, %c1 : index, index, index
  }
  builtin.module {
    func.func @elementwise_mul() {
      %lhs = hal.interface.binding.subspan set(0) binding(0) type(storage_buffer) alignment(32) : !flow.dispatch.tensor<readonly:tensor<4xf32>>
      %rhs = hal.interface.binding.subspan set(0) binding(1) type(storage_buffer) alignment(32) : !flow.dispatch.tensor<readonly:tensor<4xf32>>
      %dst = hal.interface.binding.subspan set(0) binding(2) type(storage_buffer) alignment(32) : !flow.dispatch.tensor<writeonly:tensor<4xf32>>
      %workgroup_size_x = hal.interface.workgroup.size[0] : index
      %workgroup_id_x = hal.interface.workgroup.id[0] : index
      %workgroup_count_x = hal.interface.workgroup.count[0] : index
      %base_i = affine.apply affine_map<()[s0, s1] -> (s0 * s1)>()[%workgroup_id_x, %workgroup_size_x]
      %step_i = affine.apply affine_map<()[s0, s1] -> (s0 * s1)>()[%workgroup_count_x, %workgroup_size_x]
      %end_i = arith.constant 4 : index
      scf.for %i = %base_i to %end_i step %step_i {
        %remaining = affine.min affine_map<(d0)[s0] -> (s0, -d0 + 4)>(%i)[%workgroup_size_x]
        %lhs_tile = flow.dispatch.tensor.load %lhs, offsets = [%i], sizes = [%remaining], strides = [1] : !flow.dispatch.tensor<readonly:tensor<4xf32>> -> tensor<?xf32>
        %rhs_tile = flow.dispatch.tensor.load %rhs, offsets = [%i], sizes = [%remaining], strides = [1] : !flow.dispatch.tensor<readonly:tensor<4xf32>> -> tensor<?xf32>
        %dst_init = tensor.empty(%remaining) : tensor<?xf32>
        %dst_tile = linalg.generic {
          indexing_maps = [affine_map<(d0) -> (d0)>, affine_map<(d0) -> (d0)>, affine_map<(d0) -> (d0)>],
          iterator_types = ["parallel"]
        } ins(%lhs_tile, %rhs_tile : tensor<?xf32>, tensor<?xf32>)
          outs(%dst_init : tensor<?xf32>) {
          ^bb0(%lhs_value: f32, %rhs_value: f32, %init_value: f32):
            %dst_value = arith.mulf %lhs_value, %rhs_value : f32
            linalg.yield %dst_value : f32
          } -> tensor<?xf32>
        flow.dispatch.tensor.store %dst_tile, %dst, offsets = [%i], sizes = [%remaining], strides = [1] : tensor<?xf32> -> !flow.dispatch.tensor<writeonly:tensor<4xf32>>
      }
      return
    }
  }
}

This seems to be already fixed.
on latest build following works fine.
./iree-compile --compile-mode=hal-executable --iree-hal-target-backends=cuda ~/dev/iree/tools/test/iree-benchmark-executable.mlir
./iree-compile --compile-mode=hal-executable --iree-hal-target-backends=vulkan-spirv ~/dev/iree/tools/test/iree-benchmark-executable.mlir

This is not fixed yet. It's easy to fix--just need to see how we convert IREE::HAL::InterfaceWorkgroupIDOp and do similar things.

Closing this issue as it has been addressed with https://github.com/iree-org/iree/pull/18145.


Add kube-aws node-pools destroy command

which had been missing since the first implementation of Node Pools

This is already tested manually while running E2E tests


Support for Swift 3 -  ios 10?

Are you having an explicit problem?

Actually i want to use it in my app. Just confirming that it is having support for ios10 and swift 3.

You should be fine.  There are a few deprecated APIs that are still used but those will disappear shortly.  However, there is nothing that should stop you right now.


Hanging UI at dispatch-id this-id-doesnt-exist

There is an harmless but unnecessary dispatch id existing in the UI code which when visited just shows a blank UI page with no details. We should remove this special case if it's not needed anymore. It look something like this:

@Prasy12 is this a front end test ID ?

@santoshkumarradha We don't have any test-ids in OS.
@kessler-frost  Can you let me know the steps to recreate this?
cc : @RaviPsiog

@Prasy12 after starting up covalent if we go to http://localhost:48008/this-id-doesnt-exist we see this page.

Is it been shown in the list of dispatches in the dashboard page?

And can you try any other random text? Something like
http://localhost:48008/abcd and see if you're getting the same error?
@kessler-frost

It's not. It's only if we go to this url precisely.

Okay we will check @kessler-frost

Oh, actually you're right, it is the case with any other random url as well, I see the same page.

@RaviPsiog Can you validate this when you find time? TIA!

@Kamalesh-suresh Please take a look at this.


Top-level page: One card per city

Add a simple card layout to the top-level page (i.e. https://monitoring.localzero.net/):

[ ] One card per city
[ ] Prominent display of city name
[ ] 3-line display of introduction
[ ] If content of introduction is too long, abbreviate it, e.g. with "...".
[ ] (Re-)move the menu for selection of the city. (optional)

I would keep the selection menu for now because I think it will get pretty annoying for the user to find the right card when we get more cities.

Why do you think it makes a difference to find a city on the card vs finding a city in the menu? Both cards and menu should be ordered alphabetically.


Using Mainnet data joining node not  progressing historical syncing while in keepup

Issue: Using mainnet data when one node is joined to the network it is keepingup but unable to progress on historical sync. We see a checksum warning as well( see below) but that is expected
Name: ajith-mainnet-clone
Network: 5 + 2
Branch: dev
Chain: public
Commit: 17ef14ddd9ac426ffed45b5ace8e7e700ebeeb1c
Config Override: None
Joining Node Testing Mainnet Snapshot ( 1034499 )
Tests:
1 x sync_to_genesis joining
Results: Transitioned to KeepUp but not progressing with historical sync
Observations:

**joining node transitioned to KeepUp and in-sync with tip

status - block_sync ( not progressed since 1+hrs)**

"acquisition_state": "have global state(1034492) for: block hash 01c9..3011"
seeing events as 'checksum uncheckable execution results'
{"timestamp":"2023-01-18T04:10:21.664255Z","level":"INFO","fields":{"message":"BlockSynchronizer: need next for block hash 95bd..31b9: execution results for block hash 95bd..31b9 or chunk #0 (checksum uncheckable execution results)"},"target":"casper_node::components::block_synchronizer"}
"block_sync": {
"historical": {
"block_hash": "95bda7601307f5d1d954bae9938f6ee70121bd2ef90077d9daddb33c2e4731b9",
"block_height": 824808,
"acquisition_state": "have global state(824808) for: block hash 95bd..31b9"
},
"forward": null
}
Dumps: http://genesis.casperlabs.io/ajith-mainnet-clone/casper-node-dumps/ajith-mainnet-clone/18012023_0405/dump_download_list.txt

@thamps-casp for visibility

Keeping the issue as Open since the fix should be confirmed by @thamps-casp

This was closed by a fix here https://github.com/casper-network/casper-node/pull/3665


Fix for #29: implementing a solution for tabular data

This implements a fix for #29 by creating an abstraction over HTML table elements.

@chrisblock  - Thanks for this pull request.  Lots of interesting stuff around table manipulation.  Thanks for including so many tests to demonstrate the use of the abstraction.
I am wondering if the Columns property of ITable interface should be Headers instead.  Thoughts?
Also, I am wondering if we ought to call GetHeader HeaderAs, GetRows RowsAs and GetFooter FooterAs so that the client will see both options side-by-side.  Example, .Headers, .HeaderAs.  Thoughts?

@toddmeinershagen - I agree with your suggestions and have put in another commit containing those changes.

@chrisblock - Thanks for issuing this request.  I think this functionality will definitely make it easier for users to deal with simple table structures in their application.  In the future, I think similar functionality to make repeating rows (without headers/footers) that are not dependent on a <table> element would be beneficial as well.  Using SpecificBlock is still not as intuitive.
I took a look at your changes and have a few questions.

Do we need to upgrade Selenium from 2.42 to 2.44?  If so, we need to update the .nuspec file to make that a minimum so that clients are upgraded.
I like the browser environments that you created, although, I have already taken that idea and implemented the various browsers in the main package.  Would you remove your implementations and just use the built-in ones for this request?
Please remove the RhinoMocks reference.  If you needs mocks, let's use NSubstitute.
Does it make more sense to provide an ITable so that people who develop pages can specify how a table should be interpreted instead of leaving that up to the tester writing the test scripts against those objects using the RowsAs, HeadersAs, FooterAs?  It might make it more reusable across tests.

@chrisblock - I merge your changes and think this will be a good addition to the existing elements we support.  So, thank you...
I made the mods as mentioned above and fixed a test for threaded sessions that was failing.  Instead of calling the Wait() method on each task, it needed to call Task.WaitAll() and pass in the array of tasks that were started/run.


feat: :sparkles: Sub-Pixel Convolutional

Learns a set of upscaling filters to transform low-resolution feature maps into high-resolution outputs by rearranging sub-pixels spatially

Changes made in tinygrad/:
------------------------------------------------------------
files                             insertions       deletions
------------------------------------------------------------
tinygrad/nn/image.py                      18               0
tinygrad/tensor.py                         3               1
------------------------------------------------------------
total                                     21               1
------------------------------------------------------------
lines added in the tinygrad folder: 20

Can you add some tests?

What models is this used in? I've never seen it before.
Also, like @jla524 said, all added features need tests. And I'm not sure this belongs in main tinygrad, it's +28 lines.

Hello
I didn't have time this morning lol
This layer is used in the majority of SOTA super-resolution models (30% according to statistics). It was introduced by ESPCN.
I haven't finished my PR, I'll add more tests, and I wanted to add a real model example.
docs:
https://paperswithcode.com/method/pixelshuffle
https://medium.com/@hirotoschwert/introduction-to-deep-super-resolution-c052d84ce8cf

At the very least, I don't think this belongs in nn.

as you wish, that's how it is in pytorch. I thought I heard you say you wanted to keep a similar api

I missed an rebase, I made a mess I will cleanup

I added tests

as you wish, that's how it is in pytorch. I thought I heard you say you wanted to keep a similar api
https://pytorch.org/docs/stable/generated/torch.nn.PixelShuffle.html

We want to keep the interface similar. At the same time, we really want to keep tinygrad minimal.
If these layers are only used in one example, then I suggest to move the code to the same file as the example. So everything goes in examples/espcn.py or models/espcn.py.

I totally understand your point of view,
you don't want to implement things that are rarely used or "fashionable" but PixelShuffle is an essential building block for super-resolution models.
From my point of view, your logic of minimalism should be on the interface -> backend side only,
PixelShuffle reuses existing functions it doesn't need to modify backends, or add a new ops.
user engineers' point of view :
Ease of model creation
integrator engineers' viewpoint :
Make it easier to implement their accelerator/platform inside the library to run the models.
In this logic, I'm only improving the user experience without touching the integration.
Besides, letting users implement PixelShuffle themselves, however simple, can lead to bugs. For a long time, PixelShuffle didn't work properly in Pytorch, until it caused problems with the ONNX runtime.

Closing, citing @jla524's last post. If operators are only used in one or two models, they belong in the model itself, not core tinygrad.


HOLD: Demo alternate sharing approach

Do not merge! This PR is intended to demonstrate a prototype of this alternate sharing approach.
Additions

Adds dependence on cfpb/wagtail-sharing app for sharing of draft Wagtail content.

Changes

Use wagtailsharing URL router instead of Wagtail default.
Disable reliance on a staging server hostname (e.g. content.localhost:8000) in favor of a hostname that allows for viewing of latest draft content.

 Create a new (draft only) page, and then also modify an existing published page with an unpublished change.
Browse to these pages using the standard http://localhost:8000 hostname. You should get a 404 (not published yet) and see the old content, respectively.
Browse to these pages using the new http://content.localhost:8000 hostname. You should see the draft content with a warning banner.

Screenshots

Checklist

[X] Changes are limited to a single goal (no scope creep)
[X] Code can be automatically merged (no conflicts)
[X] Code follows the standards laid out in the front end playbook
[X] Passes all existing automated tests
[X] New functions include new tests
[X] Project documentation has been updated (including the "Unreleased" section of the CHANGELOG)
[X] Reviewers requested with the Assignee tool :arrow_right:

The WAGTAILSHARING_HOSTNAME can be anything, theoretically, right?  I set mine to share.localhost:8000 because it feels weird to test on content.localhost:8000 since that's already configured to load shared pages in the code, so even if you don't set the hostname, content will show you something.  On share.localhost:8000 I can't view anything unless it's also published.

Why is it that path_components here https://github.com/cfpb/wagtail-sharing/blob/master/wagtailsharing/views.py#L61 is empty if the page exists within Wagtail, and is set to the slug name if it doesn't exist?  Is there not a way to just check if the page exists directly?

@richaagarwal thanks for the review. Needing to add WAGTAILSHARING_HOSTNAME as an additional site with the duplicate home page is something that I should have added to the wagtail-sharing docs; I'll do that.
Regarding path_components: this code is (somewhat painfully) hooking into how Wagtail determine "if the page exists directly", which is to parse the request URL path, piece by piece. So, say, the URL is /foo/bar/baz. First it'll try routing the path /foo under the site root page, which usually means "is there a page with slug foo under the root page?" but not always, due to the existence of RoutablePageMixin. Assuming that /foo is found, then the process is repeated, looking for /bar, and so on.
The line you linked to attempts to determine why an Http404 is raised for a given path: is it because the page does not exist or because the page is not live? We want to handle the second case specially, and catch that Http404 and turn it into a valid page request (by serving the draft version of the page).
Does that help clarify? I can add some comments to that code to better explain what's happening there.

@richaagarwal see PR that adds new documentation at wagtail-sharing#3.

After looking at https://github.com/wagtail/wagtail/blob/c6666c6de5e83bf94d18324858c121e6584ba47d/wagtail/wagtailcore/models.py#L656 I have a better understanding of the need for the logic in get_requested_page. Thanks for the hard work on this Andy!

@richaagarwal I went back to look at how sharing works because of your comment

Update: Nevermind! Forgot to add it to "Sites".

I was confused about this but confirmed that you shouldn't need to add the sharing hostname under Sites at all. You do have to make sure that any test page you create exists under the site root of an existing Site, though (e.g. creating under CFGOV not next to it). I added some additional unit tests that check this at wagtail-sharing#4, and also verified it works locally with this PR using:
$ WAGTAILSHARING_HOSTNAME=drafts.localhost:8000 ./runserver.sh

Create a new draft page under CFGOV (e.g. slug "foo") and it should be visible at http://drafts.localhost:8000/foo/ but not http://localhost:8000/foo/. Similarly, make unpublished edits to a page (just save them), and they should only show up at the shared hostname.

Based on some feedback to this PR and elsewhere, I'm going to close this and re-open with a slightly different approach that's simpler and will work better for us. For posterity I tagged the version of wagtail-sharing that this PR was written against with version 0.1.


Raise CouchRest specific errors instead of RuntimeError

I think couchrest should raise CouchRest::NotFound and CouchRest::Conflict and wrap all backed specific errors instead of raising RuntimeError.

This is now done in the new 2.0.0 version. The only exception are timeouts and network errors.


Festive modal layout. Progressive background image.

Festive modal layout #9 . In true ugly 90's look to match the mandril style. Let me know if you want it to look good instead.
Snow falling on the site (of course, we need that)
Enhanced background image with AI. And made it progressive jpg. Please test if this fixes the slow-loading issue from #8
Added development variable to quicky enable the opening of doors during development.

@heidipi the hero we don't deserve, but we so direly need!

Det er fedt!


🐛 Cannot read property '__callAsync' of undefined only on iOS production

What were you trying to do?
spent over a week deep diving on this. Can’t figure out this issue.
Cannot read property '__callAsync' of undefined

TypeError: Cannot read property '__callAsync' of undefined
    at _f (/[path]/app/node_modules/react-native-vision-camera/src/hooks/useFrameProcessor.ts (28:21):1:183)
    at _f (native)

Apps work fine on Android, development and production.
Works fine on iOS on devices in development but frame processors do not work on iOS archived production / testflight.
Having tried react-native 0.66.4, 0.69.6, 0.70.6
Tried react-native-reanimated from 2.5 to 2.13 (crashed before 2.8)
Tried Xcode 14 and 13.4
With and without hermes.
react-native-vision-camera 2.14 with patch and latest 2.15
Ensured CLANG_CXX_LANGUAGE_STANDARD to match between reanimated, vision camera and Hermes.
{
    "react-native": "0.70.6",
    "react-native-reanimated": "2.13.0",
    "react-native-vision-camera": "2.15.2",
    "vision-camera-code-scanner": "^0.2.0",
    "vision-camera-ocr": "^1.0.0",
    "@react-native-firebase”: 14.11.0

}

Podfile
require_relative '../node_modules/react-native/scripts/react_native_pods'
require_relative '../node_modules/@react-native-community/cli-platform-ios/native_modules'
ENV['SWIFT_VERSION'] = '5.2'
$iOSMinimumDeployVersion = '13.0'
$flipperkit_version = '0.161.0'
install! 'cocoapods', :deterministic_uuids => false
$RNFirebaseAnalyticsWithoutAdIdSupport=true
platform :ios, '13.0'

def sharedPods
  config = use_native_modules!
  production = ENV["PRODUCTION"] == "1"
  flags = get_default_flags()

  use_react_native!(
    :path => config[:reactNativePath],
    :production => production,
    :hermes_enabled => true,
    :fabric_enabled => flags[:fabric_enabled],
    :flipper_configuration => FlipperConfiguration.enabled(["Debug"], { 'Flipper' => $flipperkit_version }),
    :app_path => "#{Pod::Config.instance.installation_root}/.."
  )

  permissions_path = '../node_modules/react-native-permissions/ios'
  rn_maps_path = '../node_modules/react-native-maps'
  pod 'React', :path => '../node_modules/react-native/'
  pod 'Permission-LocationWhenInUse', :path => "#{permissions_path}/LocationWhenInUse"
  pod 'Permission-Contacts', :path => "#{permissions_path}/Contacts"
  pod 'Permission-Camera', :path => "#{permissions_path}/Camera"
  pod 'react-native-google-maps', :path => rn_maps_path
  pod 'GoogleMaps', '7.0.0'
  pod 'Google-Maps-iOS-Utils'
  pod 'VisionCamera', :path => '../node_modules/react-native-vision-camera'

  # flipper_configuration!({'Flipper' => $flipperkit_version}) # should match the version of your Flipper client app
end

target 'app' do
  sharedPods
end
target 'app development' do
  sharedPods
end
# end
post_install do |installer|
  flipper_post_install(installer)
  react_native_post_install(
    installer,
    :mac_catalyst_enabled => false
  )
  __apply_Xcode_12_5_M1_post_install_workaround(installer)

   installer.pods_project.targets.each do |target|
     target.build_configurations.each do |config|
       config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = '12'
       config.build_settings['EXCLUDED_ARCHS[sdk=iphonesimulator*]'] = "arm64"
       config.build_settings['SWIFT_VERSION'] = '5.2'
     end
   end

   installer.pods_project.build_configurations.each do |config|
     config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = '12'
   end

   installer.generated_projects.each do |project|
    project.targets.each do |target|
      target.build_configurations.each do |config|
          config.build_settings["DEVELOPMENT_TEAM"] = "TEAMID"
        end
    end
  end

    installer.target_installation_results.pod_target_installation_results
      .each do |pod_name, target_installation_result|
      target_installation_result.resource_bundle_targets.each do |resource_bundle_target|
        resource_bundle_target.build_configurations.each do |config|
          config.build_settings['CODE_SIGNING_ALLOWED'] = 'NO'
        end
      end
    end
  `sed -i -e  $'s/__IPHONE_10_0/__IPHONE_14_0/' Pods/RCT-Folly/folly/portability/Time.h`
 end

.podspec
Pod::Spec.new do |spec|
   spec.compiler_flags = '-fno-modules'
   s.swift_version = "5.2"
 end

Considering writing the frame processors ourselves but feels like this is close and have a hunch its a build
Issue solved from Podfile.
Using multiple frame processors (OCR / QR) reader but get the same results building with either or.
Suggestions?
Reproduceable Code
<Camera
              audio={false}
              device={device}
              isActive={isFocused}
              frameProcessorFps={1}
              frameProcessor={frameProcessorQR}
              photo
              zoom={1}
              onLayout={(event: LayoutChangeEvent) => {
                setPixelRatio(
                  event.nativeEvent.layout.width /
                    PixelRatio.getPixelSizeForLayoutSize(event.nativeEvent.layout.width)
                )
              }}
              preset="hd-1280x720"
              orientation="portrait"
              ref={cameraRef}
              style={StyleSheet.absoluteFill}
            />

What happened instead?
no frameprocessors loading and or crash depending on reanimated / vision camera versions.
Relevant log output
default	10:45:54.432471+0100	app	FrameProcessorBindings: Setting new frame processor...
default	10:45:54.432498+0100	app	FrameProcessorBindings: Adapting Shareable value from function (conversion to worklet)...
default	10:45:54.432604+0100	app	FrameProcessorBindings: Successfully created worklet!
default	10:45:54.432652+0100	app	FrameProcessorBindings: Converting worklet to Objective-C callback...
default	10:45:54.433259+0100	app	FrameProcessorBindings: Frame processor set!
Cannot read property '__callAsync' of undefined

error	10:45:55.849438+0100	app	Cannot read property '__callAsync' of undefined

TypeError: Cannot read property '__callAsync' of undefined
    at _f (/[path]/app/node_modules/react-native-vision-camera/src/hooks/useFrameProcessor.ts (28:21):1:183)
    at _f (native)

Device
iPhone 11, iPhone 14, moto e7
VisionCamera Version
2.15.2
Additional information

[ ] I am using Expo
[X] I have read the Troubleshooting Guide
[X] I agree to follow this project's Code of Conduct
[X] I searched for similar issues in this repository and found none.

Closing as this is a stale issue - this might have been fixed with the full rewrite in VisionCamera V3 (🥳) - if not, please create a new issue.
If your issue has been fixed, consider sponsoring me on GitHub to say thanks 💖

Hey!
JFYI; VisionCamera V3 now includes a QR/Barcode Scanner! 😍  Check out the CodeScanner Documentation 🚀
Try upgrading to V3 if you can, it has a much more stable yet flexible foundation.


Remove: purocean.YankNote version 2.9.1

## .\Tools\YamlCreate.ps1 -SkipPRCheck -Mode 5 -PackageIdentifier purocean.YankNote -PackageVersion 2.9.1

[X] Have you signed the Contributor License Agreement?
[X] Have you checked that there aren't other open pull requests for the same manifest update/change?

[X] Does your manifest conform to the 1.0 schema?

Microsoft Reviewers: Open in CodeFlow

/azp run


WIP: new vendor ide version support

The .tm file is not being processed
Signed-off-by: YRabbit<EMAIL_ADDRESS>

Still most of the I/O modes are disabled, not because they won't work, but to speed up base generation for CI debugging purposes.

Yay. GW1NSR-4C next?

It's possible. At this point it's probably just copy-pasting a few lines. But there are also some other high priority features and bugs so we'll see.
If you want to give it a go yourself, have a look at https://github.com/YosysHQ/apicula/commit/fef98e568a9605f45f2f76407cce693a92acd219 for an example.


Link: make a link look like a Button

Description
I'm not sure if this feature already exists, but would it be possible to make a link look like a button using the Link component?
Here are examples from Altinn Studio, where we have links that look like buttons:

Additional Information
No response

Good morning!
We aim to provide polyformism for most of our components, which means you can change the underlying html element.
We added this feature to Button last week actually in release 0.31.0 of react!
You can now use as on Button to change it into an a element like so: <Button as='a'>Send me somewhere!</Button>


Logs me out after adding 2 new translations

Describe the issue
Hi Team,
When ever I tried to add new translations it logs me out after adding 2 new translations, and I need to wait for an hour, to add other translations again it logs me out.
Can you please help !!
Regards,
Raman Muthu
I already tried

[X] I've read and searched the documentation.
[X] I've searched for similar issues in this repository.

Steps to reproduce the behavior

Go to '...'
Scroll down to '...'
Click on '...'
See error

Expected behavior
No response
Screenshots
No response
Exception traceback
No response
Additional context
No response

Do you get some error?

We get the below error when it logs out..

Can you please get the full exception for the error? See https://docs.weblate.org/en/latest/contributing/debugging.html
PS: You should upgrade, it is possible that the issue you are facing was fixed in the newer releases.

Hi upgraded the weblate app to 4.8.1 and I dont see the issue with superuser.. as mentioned in the document..
but we have a new issue, the integration is not working with the application
do we need to change anything regards to integration? my previous app version is 4.5

I have no clue what kind of integration are you using and what is not working...
Also, the latest version is 4.10.1.

Rest Api endpoint for /api/translations/app-20-tenant-98-global/common/en_US/file
worked on older version, on this version it is not working

There was no change in the API URLs. Is the full URL correct (especially look for missing/extra slashes)? Is the authentication token correct?

Yes I have verified the URL aswell..
we are using AKS cluster and used Helm charts.. I can see the latest version in Helm chart is 4.8.1.

Upgrading to Latest version helped to fix Log out issue, now with superuser , we dont see any limits for new translations


Q: timestamps from inconsistent clocks (microcontroller? or camera?)

Hey guys,
we are recently grabbing images (rgb, depth and fisheye), IMU readings and the relevant timestamps from the ZR300 sensor. We have correctly enabled the enable_motion_tracking but the timestamps for the rgb and depth seem from the camera clock instead of the motion microcontroller. This situation can be solved by increasing their frame rate to >60 but this problem remains if we drop the frame rate back to 30.
It is pretty easy to reproduce this problem. You could run the official example "cpp-motion-module" by changing the rgb and depth frame rate (around line 89-93) from 60 to 30.
I am wondering what's the problem here? how can we keep getting the timestamps consistently from motion microcontroller for all the steams (at lower frame rate).

Hi @vinben
Could you please share the header of cpp-enumerate-devices that contains firmware versions of the various components?


Skip Pre- and Post-Database-Processing if ITs are skipped.

@jhorstmann @lukasniemeier-zalando Please have a look.

:+1:


Layout not loading consistently

When more that 2 persons are in a call and then one of the users reloads the entire page, sometimes other users views on other screens also disappear. see https://www.screenmailer.com/v/x2xhwM4I3Sa2aTo

I'm not sure exactly what is happening here. Could you talk me through steps to reproduce this problem? Perhaps also link me to your app or some sample code that displays the issue.

Hi Adam,
I am the product lead at mpowr (and the second person in the screencast).
The app can be found here: https://mpowr.io. You'll need to sign up via Slack to test it as a host. Alternatively, you can attend my room without signing up here: https://mpowr.io/Max_Benz1
Let me know if you have some time. I would be glad to explain the issue and to reproduce the problem with you.


Ember Engines support?

Wasn't sure if it was officially supported or not.

Tbh, I don't know, as I am not an engines user and not sure what it takes to support it. I think it all depends on broccoli-concat to emit the stats output for the engine's bundles, and it could very well already do that, but I am not sure.

If there was an issue here, then it will very likely been fixed by #26


Add support for GLFW/glfw3.h

Updated from #28. I also removed the OpenGL parts to make it easier to merge.

Thank you for taking the time to update it! Do you plan to send OpenGL changes as well, or there are issues with it?

I could. It would have to be later this week though.


chore: read shared model list from remote

Description
Instead of using a hardcoded list of supported shared models, this reads from a remotely hosted endpoint
Checklist

[ ] Code compiles correctly and linting passes locally
[ ] For all code changes, an entry added to the CHANGELOG.md file describing and linking to this PR
[ ] Tests added for new functionality, or regression tests for bug fixes added as applicable
[ ] For public APIs, new features, etc., PR on docs repo staged and linked here

Per follow-up discussion, we shouldn't actually need the list at all.  We can simply check for a distinct error status such as 404 when the model is invoked, to tell us that the model is not available.


Add an example program using CLI11

🎉 Add an example program using CLI11
Shows basic usage in CMakeLists to build and link against the CLI11 wrapper in ignition
Test it
To test with the vendored CLI11 version, build a colcon workspace with ign-utils and ign-cmake with
         "-DIGN_UTILS_VENDOR_CLI11:BOOL=ON"

and then build the example program.
To test with the system CLI11 version, build a colcon workspace with ign-utils and ign-cmake with
         "-DIGN_UTILS_VENDOR_CLI11:BOOL=ON"

and then build the example program.
Checklist

[x] Signed all commits for DCO
[ ] Added tests
[x] Added example and/or tutorial
[ ] Updated documentation (as needed)
[ ] Updated migration guide (as needed)
[ ] codecheck passed (See contributing)
[ ] All tests passed (See test coverage)
[ ] While waiting for a review on your PR, please help review another open pull request to support the maintainers

Note to maintainers: Remember to use Squash-Merge

@traversaro just a quick example to demonstrate CMakeLists.txt for using utils.

Codecov Report

Merging #23 (55dce06) into ign-utils1 (036faa9) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head 55dce06 differs from pull request most recent head f457d4a. Consider uploading reports for the commit f457d4a to get more accurate results

@@             Coverage Diff             @@
##           ign-utils1      #23   +/-   ##
===========================================
  Coverage       89.58%   89.58%
===========================================
  Files               3        3
  Lines              48       48
===========================================
  Hits               43       43
  Misses              5        5

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 036faa9...f457d4a. Read the comment docs.


recreate http client on resume()

In testing concurrent actions (multiple activations in same container) we noticed that when a container is used after Container.suspend(), the http connection may be re-created multiple times (and may have side affects of losing connections each time a new one is created.
Description

This PR addresses this by:

using a separate function for creating the connection - this will be invoked first during /init
same function will be invoked again during Container.resume() (which means that subclasses must invoke super.resume())

This way the subsequent + multiple calls to /run will arrive after connection has already been recreated.
I extended the ContainerProxyTests to assert connection state (exists or not) after suspend() and after resume().
Related issue and scope

[ ] I opened an issue to propose and discuss this change (#????)

My changes affect the following components

[ ] API
[ ] Controller
[ ] Message Bus (e.g., Kafka)
[ ] Loadbalancer
[x] Invoker
[ ] Intrinsic actions (e.g., sequences, conductors)
[ ] Data stores (e.g., CouchDB)
[ ] Tests
[ ] Deployment
[ ] CLI
[ ] General tooling
[ ] Documentation

Types of changes

[ ] Bug fix (generally a non-breaking change which closes an issue).
[x] Enhancement or new feature (adds new functionality).
[ ] Breaking change (a bug fix or enhancement which changes existing behavior).

Checklist:

[x] I signed an Apache CLA.
[x] I reviewed the style guides and followed the recommendations (Travis CI will check :).
[x] I added tests to cover my changes.
[ ] My changes require further changes to the documentation.
[ ] I updated the documentation where necessary.

Codecov Report

Merging #4185 into master will increase coverage by 20.83%.
The diff coverage is 80%.

@@             Coverage Diff             @@
##           master    #4185       +/-   ##
===========================================
+ Coverage   60.55%   81.39%   +20.83%
===========================================
  Files         152      152
  Lines        7292     7283        -9
  Branches      472      474        +2
===========================================
+ Hits         4416     5928     +1512
+ Misses       2876     1355     -1521

Impacted Files
Coverage Δ

...la/org/apache/openwhisk/core/mesos/MesosTask.scala
72.09% <0%> (+72.09%)
:arrow_up:

...sk/core/containerpool/docker/DockerContainer.scala
96.2% <100%> (+5.06%)
:arrow_up:

...containerpool/kubernetes/KubernetesContainer.scala
94.73% <100%> (+94.73%)
:arrow_up:

...pache/openwhisk/core/containerpool/Container.scala
87.17% <83.33%> (+5.48%)
:arrow_up:

...e/openwhisk/core/containerpool/ContainerPool.scala
92.62% <0%> (+1.63%)
:arrow_up:

.../scala/org/apache/openwhisk/core/entity/Exec.scala
85% <0%> (+1.66%)
:arrow_up:

.../org/apache/openwhisk/core/entity/EntityPath.scala
100% <0%> (+1.88%)
:arrow_up:

...a/org/apache/openwhisk/core/entity/Parameter.scala
95.45% <0%> (+2.27%)
:arrow_up:

.../org/apache/openwhisk/http/PoolingRestClient.scala
90% <0%> (+3.33%)
:arrow_up:

...hisk/core/controller/actions/SequenceActions.scala
92.1% <0%> (+3.5%)
:arrow_up:

... and 92 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 1686a85...d83124d. Read the comment docs.


Confusing terminology

Issue in help/using/integration/sending-audience-data/batch-data-transfer-explained/inbound-ftp-filenames.md
In the documentation it refers to DPID which looks like it's referring to the single customer ID (PID). However Jess and others are saying that it actually refers to the Data Source ID. Can this be clarified? There's the same issue in the S3 page as well.
Thanks,
Jonathan

Hi @jweissba  - we reached out to our Engineering team and will post a response here and update the documentation to clarify the PID vs. DPID question as soon as possible.

Hi @jweissba - I can confirm that PID is not part of inbound file names. Jess is correct and we refer to Data Source ID in the documentation.
We'll update the documentation and follow up on this thread once we do that.

@jweissba  - we have now made further updates to:

Amazon S3 Name and File Size Requirements for Inbound Data Files
FTP Name and File Size Requirements for Inbound Data Files

Following a review with the Engineering team, we updated the DPID and DPID_TARGET_DATA_OWNER fields with new definitions and clearer examples.
Closing this ticket. Please reopen if further updates are needed.
Best,
Victor


Please merge revision #fe05e7b90516fe2d853a65233a7258e8afb958c0 into dev channel

@ricowind @whesse @mit-mit @kasperl
update the sdk documentation generation to use the 0.5.0 version of dartdoc
revisions to be merged
fe05e7b90516fe2d853a65233a7258e8afb958c0  update dartdoc, markdown in DEPS
f0b81a44bb801dc1fd0025a2b26073f4a5bad6a1 fix failing docgen tests on pkg bots
5abf4fef9ce23341af2b63edb98648ebe178a5da  fix failing tests on pkg bots

Also merge 9fa9698caa8063ced35a352da8102a91bfad1299, which uses the mirror for markdown.

Merged to 1.12.0-dev.5.5.


[NEXT] Cannot import useLocalePath manually. TypeError: Cannot read properties of undefined (reading 'Symbol(vue-i18n-routing-gor)')

Version
@nuxtjs/i18n: 8.0.0-beta.2
nuxt: 3.0.0-rc.12
Nuxt configuration
Please change to [x] if relevant for this issue:

[x ] Applies to a site deployed to a static server (site generated with nuxt generate)
[ ] Applies to a site deployed to a server with a Node backend

@nuxtjs/i18n configuration

Reproduction Link
https://stackblitz.com/edit/github-1pmwyi?file=nuxt.config.ts
The reproduction shows an additional error: "Not available in legacy mode" 🤷♂
Steps to reproduce
In .vue file
import { useLocalePath } from 'vue-i18n-routing';

const localePath = useLocalePath();
console.log(localePath('index'));

What is Expected?
Working localePath.
What is actually happening?
localePath work only if is auto-imported.
Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'Symbol(vue-i18n-routing-gor)')
    at getGlobalOptions (vue-i18n-routing.mjs:457:16)
    at getI18nRoutingOptions (vue-i18n-routing.mjs:586:19)
    at Object.resolveRoute (vue-i18n-routing.mjs:633:130)
    at Object.localePath (vue-i18n-routing.mjs:618:39)
    at vue-i18n-routing.mjs:895:20
    at setup (index.vue:8:2)
    at callWithErrorHandling (runtime-core.esm-bundler.js:155:22)
    at setupStatefulComponent (runtime-core.esm-bundler.js:7204:29)
    at setupComponent (runtime-core.esm-bundler.js:7159:11)
    at mountComponent (runtime-core.esm-bundler.js:5508:13)

The reproduction shows an additional error: "Not available in legacy mode" 🤷♂

This is an issue, so I'll fix it.

import { useLocalePath } from 'vue-i18n-routing';

BTW, In @nuxtjs/i18n, useLocalePath is exported from vue-i18n-routuing is doesn't work (and other composable functions)
So, You need to use auto-imported compsable functions.

@kazupon it's a pity i have used it so far. I think users should be able to explicitly import and know where composables is imported from. Sometimes there are so many composables that it's hard to remember everything. Not to mention the new people to the project. But it's your decision.
If someone like me has auto-imports disabled, you can use this workaround:
import { useLocalePath } from '#imports';

@szulcus
You can use import with  #imports
import { useI18n, useLocalePath } from '#imports'

I've just released v8.0.0-beta.3
close


Event counter just like note counter

What feature do you want to get added on the base engine?
Basically the same as how much note(s) it has, but what about how much event(s) it does have?
(apply to the chart editor)
To test your sight, and reliability, please select the option of what should NOT be requested.
Stage Editor and 6K+ Support.

edited because i misclick "optimization" instead of "stage editor and 6k+ support"

No

:( ok


Chan Zuckerberg Initiative logo not visible properly when user use github dark theme

📚 Documentation

Institutional partner logo is not properly visible if user use GitHub dark theme.
Dark theme:

Light theme:

I've moved this to the theme as I think it's more of an issue here. Might be wrong though, looking for guidance from @codemonkey800 et al. :pray:

I do not think that it is a theme problem. It is problem that napari uses a logo with transparent background.
Especially I show screenshots from GitHub readme, not form documentation.

Oops! Interesting. Having said that, I think the "right" way of doing this is to use different logos for different themes (?), rather than using a non-transparent background?

But, as far as I know, markdown do not provide a way to declare this (both screenshots are from github.com).


Edit campaign handler tests

Partial fix for #59
Found a couple of tests I'd written but not submitted.

Yah tests! :shipit:


kpt-merge directive missing in downstream packages created using porch APIs

Expected behavior
In porch, when I create a downstream package using clone operation,  I expect # kpt-merge: directive to be added to the resources in downstream package. This is required for updating the downstream package in future to reconcile identity of downstream resources with upstream ones. An example of downstream resource:
apiVersion: v1
kind: ResourceQuota
metadata: # kpt-merge: example/default
  name: default
  namespace: backend
spec:
  hard:
    cpu: "40"
    memory: 40G

Actual behavior
# kpt-merge directive is missing. Quick look at the code in porch suggests, addmergecomment.AddMergeComment is not being applied after fetching the downstream resources.
Steps to reproduce the behavior

$ kpt alpha rpkg clone <upstream-pkg> backend-1 --repository <deployment-repo> -n default

$ kpt alpha rpkg pull <downstream/pkg/with/name/backend-1> -n default

# resources don't have `kpt-merge` directive.

Sidenote: I think storing original identity of the resource in annotation might be better to foolproof it because comments are more likely to get dropped in the transport (or serialization/deserialization).

/cc @mortent @natasha41575 found this today and is a blocker for the update operation.

@natasha41575 feel free to pick this up if you want to :)

I can take a look
/assign

So I think the real question here is why the logic for clone differs between kpt and porch. Adding the same logic in porch as we have in kpt is a good temporary fix, but we want to avoid duplicating too much functionality.
Can we make the get/fetch logic from kpt available as a library in a way so we can use the same code in porch? We have the same issue with the update logic where we have code copied from kpt.
@droot Have you looked at making the code from kpt available as a library so that we can use it in porch?

Adding the same logic in porch as we have in kpt is a good temporary fix, but we want to avoid duplicating too much functionality.

I think for the time being we may have to duplicate at least some things. If porch depends on the kpt library before https://github.com/GoogleContainerTools/kpt/issues/3297 is done, won't we see the same circular dependency problems that we found in https://github.com/GoogleContainerTools/kpt/pull/3301#discussion_r894039417 ?

So I think the real question here is why the logic for clone differs between kpt and porch. Adding the same logic in porch as we have in kpt is a good temporary fix, but we want to avoid duplicating too much functionality.

Some background:
Actually the goal is to share as much as code possible between kpt and porch. We started with the pieces that are sort of decoupled from storage (git/oci/porch-native etc.) and prioritized render, eval, package init etc. and integrated them. The pieces that depends on storage git and oci etc. are slightly complicated because the underlying mechanism to fetch packages in kpt CLI and porch is a bit different. Also, porch has slightly different requirements around caching etc. since it needs to serve those packages as API. So this requires more thought. Though the lower level pieces are available as library in kpt, for ex. the code that adds merge-key directive to a set of resources is implemented as kio.Filter, but the layer just above that can be shared between kpt CLI and porch mutation machinery needs to be worked out.
Martin's suggestion has been to avoid premature refactoring and doing it along the way, and that's what we have done so far.

I think for the time being we may have to duplicate at least some things. If porch depends on the kpt library before https://github.com/GoogleContainerTools/kpt/issues/3297 is done, won't we see the same circular dependency problems that we found in https://github.com/GoogleContainerTools/kpt/pull/3301#discussion_r894039417 ?

the Go module in porch apiserver is setup to use kpt as library (through some magic.. dont remember the details) so this isn't a problem. We are already sharing code from kpt in porch.


Incorrect semantic mask accquired from habitat-api

Hi,
I used the habitat-api to get the semantic mask in the ARNzJeq3xxb scene of the mp3d dataset:
In the reset() function:
scene = self.habitat_env.sim.semantic_annotations()
instance_id_to_label_id = {int(obj.id.split("_")[-1]): obj.category.index() for obj in scene.objects}
self.mapping = np.array([ instance_id_to_label_id[i] for i in range(len(instance_id_to_label_id)) ])
semantic_mask_gt = np.take(self.mapping, obs['semantic'])

In the step() function:
semantic_mask_gt = np.take(self.mapping, obs['semantic'])

I save the  mask of the plant using the code below:
semantic_mask_plant = np.ones(semantic_mask_gt.shape) * 255
semantic_mask_plant[semantic_mask_gt==14] = 0 # plant
cv2.imwrite("./mask_plant_" + str(self.timestep).zfill(6) + ".png",semantic_mask_plant)

However I noticed the semantic mask of the plant has the wrong region,
The RGB image and semantic mask of the plant at timestep 19 are shown below:

The RGB image and the semantic mask of the plant at timestep 196 are shown below:

The semantic mask at timestep 19 is totally wrong, and the semantic mask at timestep 196 has both the incorrect and the correct region.
I want to know how to get the totally correct semantic mask.
Can you help me to solve this problem?
Thanks

Not commenting on this specific case (because I can't visually understand what's going on), but in general, MP3D annotations are known to be noisy (and the simulator cannot change that; noise in, noise out). Try HM3D-Semantics (https://aihabitat.org/datasets/hm3d-semantics/); still not noise-free, but better. If you still see such gross errors in HM3D-Semantics, then it's worth looking at your code.

Thanks for your reply, I'll try the HM3D-Semantics dataset.


Bugfix -> deltachat-desktop

According to the tests made with the binary, the problem is in the libdeltachat version, I have up the default.nix for more information.
Thanks to support -> @hugosenari
Print of build ->
Default.nix with the corrections  -> https://github.com/stnert/My-Configuration-NixOS/blob/main/default.nix
Notify maintainers
@thiagokokada @Misterio77
maintainer:
@dotlambda

https://github.com/NixOS/nixpkgs/issues/195741


Use xml2js for xmlToJson()

To resolve issue #9 & #47 , open this draft PR for tracking code changes.
Since xml2js provides an async interface, the usage of xmlToJson() has to be updated.
The output JSON structure has been changed as well -->
Old JSON:
[
  {
    "type": "cmd",
    "success": true,
    "cmd": "RTVJOBA USRLIBL(?) SYSLIBL(?)",
    "data": [
      {
        "name": "USRLIBL",
        "value": "QGPL       QTEMP      QDEVELOP   QBLDSYS    QBLDSYSR"
      },
      {
        "name": "SYSLIBL",
        "value": "QSYS       QSYS2      QHLPSYS    QUSRSYS"
      }
    ]
  },
  {
    "type": "sh",
    "data": "..."
  },
  {
    "type": "pgm",
    "success": true,
    "pgm": "QWCRSVAL",
    "lib": "QSYS",
    "data": [
      {
        "value": "1",
        "type": "10i0"
      },
      {
        "value": "44",
        "type": "10i0"
      },
      {
        "value": "0",
        "type": "36h"
      },
      {
        "value": "QCCSID",
        "type": "10A"
      },
      {
        "value": "B",
        "type": "1A"
      },
      {
        "value": "",
        "type": "1A"
      },
      {
        "value": "4",
        "type": "10i0"
      },
      {
        "value": "37",
        "type": "10i0"
      },
      {
        "value": "1077936194",
        "type": "10i0"
      },
      {
        "value": "1",
        "type": "10i0"
      },
      {
        "value": "QCCSID",
        "type": "10A"
      },
      {
        "value": "",
        "type": "[object Object]",
        "io": "both",
        "len": "rec2"
      }
    ]
  },
  {
    "type": "sql",
    "success": true,
    "stmt": "call qsys2.tcpip_info()",
    "result": [
      [
        {
          "desc": "HOSTNAME",
          "value": "UT25BP17.RCH.STGLABS.IBM.COM"
        },
        {
          "desc": "VRM",
          "value": "V7R2M0"
        },
        {
          "desc": "DBGROUP",
          "value": ""
        },
        {
          "desc": "IPTYPE",
          "value": "NONE"
        },
        {
          "desc": "IPADDR",
          "value": "UNKNOWN"
        },
        {
          "desc": "PORT",
          "value": "0"
        }
      ]
    ]
  }
]

New JSON:
[
  {
    "type": "cmd",
    "exec": "rexx",
    "error": "fast",
    "success": true,
    "cmd": "RTVJOBA USRLIBL(?) SYSLIBL(?)",
    "data": [
      {
        "name": "USRLIBL",
        "value": "QGPL       QTEMP      QDEVELOP   QBLDSYS    QBLDSYSR"
      },
      {
        "name": "SYSLIBL",
        "value": "QSYS       QSYS2      QHLPSYS    QUSRSYS"
      }
    ]
  },
  {
    "type": "sh",
    "error": "fast",
    "data": "..."
  },
  {
    "type": "pgm",
    "name": "QWCRSVAL",
    "lib": "QSYS",
    "error": "fast",
    "success": true,
    "cmd": "QSYS QWCRSVAL ",
    "data": [
      {
        "io": "out",
        "param": [
          {
            "type": "10i0",
            "value": "1"
          },
          {
            "type": "10i0",
            "value": "44"
          },
          {
            "type": "36h",
            "value": "0"
          },
          {
            "type": "10A",
            "value": "QCCSID"
          },
          {
            "type": "1A",
            "value": "B"
          },
          {
            "type": "1A"
          },
          {
            "type": "10i0",
            "value": "4"
          },
          {
            "type": "10i0",
            "value": "37"
          }
        ]
      },
      {
        "param": {
          "type": "10i0",
          "value": "1077936194"
        }
      },
      {
        "param": {
          "type": "10i0",
          "value": "1"
        }
      },
      {
        "param": {
          "type": "10A",
          "value": "QCCSID"
        }
      },
      {
        "io": "both",
        "param": {
          "type": "[object Object]",
          "io": "both",
          "len": "rec2"
        }
      }
    ]
  },
  {
    "type": "sql",
    "data": [
      {
        "command": "prepare",
        "error": "fast",
        "conn": "conn1",
        "stmt": "stmt1",
        "success": true,
        "sql": "call qsys2.tcpip_info()"
      },
      {
        "command": "execute",
        "error": "fast",
        "stmt": "stmt1",
        "success": true,
        "sql": "stmt1"
      },
      {
        "command": "fetch",
        "block": "all",
        "desc": "on",
        "stmt": "stmt1",
        "success": true,
        "sql": "stmt1",
        "result": [
          {
            "desc": "HOSTNAME",
            "value": "UT25BP17.RCH.STGLABS.IBM.COM"
          },
          {
            "desc": "VRM",
            "value": "V7R2M0"
          },
          {
            "desc": "DBGROUP"
          },
          {
            "desc": "IPTYPE",
            "value": "NONE"
          },
          {
            "desc": "IPADDR",
            "value": "UNKNOWN"
          },
          {
            "desc": "PORT",
            "value": "0"
          }
        ]
      },
      {
        "command": "free",
        "success": true,
        "sql": ""
      }
    ]
  }
]

I'm not sure changing Xml2Json format and how it's used (async) is such a good idea. That's a breaking change and will affect all users. Perhaps instead, we leave Xml2Json as-is and allow users to opt-in to xml2js somehow, instead?
Or do we not necessarily care about compatibility before 1.0?

I'm not sure changing Xml2Json format and how it's used (async) is such a good idea. That's a breaking change and will affect all users. Perhaps instead, we leave Xml2Json as-is and allow users to opt-in to xml2js somehow, instead?
Or do we not necessarily care about compatibility before 1.0?

Agree. It is better to keep the old xmlToJson API (mark it as deprecated?) and provide a new one (xmlToJs ?).
The old xmlToJson API breaks the structure of the original xml output, especially for the pgm and sql output. So the new API (to keep all the original data and order) can not be 100% compatible with the old one.

Now the code changes pass all test cases.
One comment -> https://github.com/IBM/nodejs-itoolkit/pull/53/files#diff-e7cfb3504922bf38f952e03a86b73ca9R146
As a fix for issue #11 , previously the BLANK item has a value of '', now it is undefined.

I think the best thing to do for compatibility is to have an option to use XmlToJson instead of using xml2js, just like we have for returning an error. The deprecated constructors would use XmlToJson always, but the object constructor could have an option to use XmlToJson if desired (off by default and deprecated). Then at V2 we can remove XmlToJson.

I think the best thing to do for compatibility is to have an option to use XmlToJson instead of using xml2js, just like we have for returning an error. The deprecated constructors would use XmlToJson always, but the object constructor could have an option to use XmlToJson if desired (off by default and deprecated). Then at V2 we can remove XmlToJson.

The basic functions like CommandCall, ProgramCall, SqlCall ( or the old iCmd, iPgm, iSh, iSql... ) require calling xmlToJson/xmlToJs explicitly and the usages are very different, I do not think an option is needed to distinguish them.
const results = xmlToJson(xmlOut); vs. const results = await xmlToJs(xmlOut);
As for the toolkit APIs (lib/Toolkit.js), we can check a new option in the Connection object to use xmlToJson or xmlToJs.
@kadler, So the option only affects the toolkit APIs, right?

Ok, so it seems that the only usages of xmlToJson within the code is usage by tests and internal implementation defails of the high level wrappers (eg. sendToDataQueue). From that point of view, we don't have any compatibility issues to deal with.
I would suggest then not exporting any xmlToJs API or similar. Let users import and use xml2js themselves (and recommend it to users). We can internally use it in place of xmlToJson, but I don't see much use for wrapping it in our own xmlToJs API.

The v1.0-dev branch is no more. Please re-open to master.


Significance of "step-xxxx-audio.wav" audio files

Hi All,
Apologies if this is already covered in another question, but I have searched and cannot find what I am looking for.  My experience here has been that the step 1000 --> 6000 wav files that are generated significantly improve in quality (1000 sounding very grainy and robotic, and 6000 starting to sound a lot like the input audio), but that from 6000 --> 20000 there is very little additional improvement in this audio.
I understand from the reading that this audio has nothing to do with the ability to actually generate speech, but I would still like to understand what is the detail behind this audio.
Kind Regards,
HS.

The neural network (NN) is learning the patterns in the training data. Learning means that correlations between the randomly initialized NN weights and training data are strengthened.
Based on your description the NN quickly learns "some major correlations". Or in other words the NN weights align in such way that it is able to recreate the training data audio from the given <audio,text> pairs.
NNs are very sensitive creatures. So even if it can produce convincing audio for the training data texts, it does not mean that it will work at all for text that does not appear in the training data. I visualize it so that the initial training creates these paths from "training_text_0001" to "training_audio_0001". It can walk through that path quite ok even at step 6000, like you have noticed. But if you give it "not_training_text_xxx", the resulting will be garbage, because there is no path created for that input.
It will take time and lots of good quality training material for the NN to learn to generalize so that it works well with text outside the training data. After 200000 steps the NN has learned not just "paths", but more like "landscapes", where you can travel from any text to corresponding convincing audio.


Add a shorthand for accessibilityIdentifier

It would be nice to be able to take any Anchorage expression and add + "someString" to it, and get a constraint that has an identifier. Constraint identifiers show up in debug logs and the Xcode view debugger, and they also appear on wtfautolayout.com.
I’m guessing that overloading func +(lhs: LayoutExpression, rhs: String) might adversely affect compile times, so I’d be OK with exploring other operators, but it’s hard to beat good ol’ + for readability.

It would also be nice to put + AnchorageDebug() at the end of an Anchorage expression and have it capture the file, line number, and function name for debugging purposes.


SSH Proxy Support

Can you please add SSH proxy support.
Thanks

Dealing with SSH is not easy thing, for example, need to detect when connection is closed and reconnect.
It is better to keep SSH stuff out of BAS executable. Anyway, you can use that tool https://bablosoft.com/shop/MassTunneler to use SSH with any software including BAS.
Here is e example on how to start/stop MT with BAS. https://www.dropbox.com/s/decjhytgqj0t7xg/MTStartStop.xml?dl=0

Thanks, I will have a look.


Republish dronedeploy-functions-api as functions-wrapper [AM-910]

https://dronedeploy.atlassian.net/browse/AM-910

we should also change the name of this repo

yup, just opening this one so people could review the file changes
was thinking I'd create a new repo for the new project name, or should we modify the name of this repo?


Feature/output json string

Hey @bleonard,
This is a PR which adds support for a JSON formatter (see #12). I'm not sure what is the preferred/best way to tell rake stats to output JSON instead of a table in the console. Do you have any ideas about that?
Please ignore the test/dummy and all the duplicated code (I had to branch out of #10 to add coverage for this feature)
This set of changes includes a small-ish refactor:

It splits up code_statistics.rb into two (calculator calculates, formatter formats output)
It adds a superclass for the formatters

Please check it out when you get a minute. It might be easier to review this PR when you merge #10. 😄
Thanks!

@etagwerker I think this needs a rebase

@etagwerker https://github.com/fastruby/rails_stats/pull/18 is merged 👍


Error for all admins

Describe the bug
All Program and CiviForm Admins are unable to access CiviForm. I attached the error message. Residents are still able to login and submit applications. First time error was reported was 5:00 pm on Friday, 3/25.
To Reproduce
Steps to reproduce the behavior:

Go to https://civiform.seattle.gov
Click on "Admin"
See error

Screenshots
Attached

Logs are showing "Question not found for Program 590". I'm gathering more details right now.

Logs are showing "Question not found for Program 590". I'm gathering more details right now.

I was working on a program Friday afternoon... I probably triggered it. It's the Ride Now program for SDOT.

Here are the relevant id's:

program 590
version 228 obsolete
version 229 active
question 226 obsolete
question 928 active

The program's block_definition had a reference to an obsoleted question (q226). The fix was to update the old question id in the block_definition and replace it with the active version question id (928).
Linking this to #2047 since they may be related.

I've figured out the root cause of this issue.
Repo:

Publish a program (ID 1 for example) that uses a question (ID 30 for example).

Open the Admin Program page and Questions page in 2 tabs.

In the Question tab, make a new version of the question (ID 31)
Notice: A DRAFT of the program (ID 2) is made that now references the new question version ID 31

In the Programs tabs, make a new version of the program.
Notice: The Draft of the program now refers to the original version of the program. ID 30

By have the Program tab cached, the page only know about Active Program ID 1, if you were to refresh it would then know about Draft program ID 2
I'm not exactly sure what's happening, but seemingly in Step 4 the configuration from ID 1 (With Question ID 30) is copied into ID 2.  When we publish, Question ID 30 is made Obsolete, and Question ID 31 and Program ID 2 are made ACTIVE.  So not Program ID 2 references an obsolete question ID 30.
The fix could come in a few forms.

When the user tries to "make a new version" and a draft exists, detect that and show the user a message that there's already a draft.
When the user tries to "make a new version" and a draft exists, load the actual draft and display it seamlessly to the user.


WAR 6.2 Support

Bumping potencies, nothing else to see here. Why did this take so long? I forgot it wasn't done yet and thought the support was already in, because I am very smart and know how to use a TODO list (this is a lie).

It failed lint (._.) @ayyaruq


Fix dependencies used in pre-push githook

The current gradle version used is 5.2.1. Mac OS Catalina requires gradle version 6.3 to work.
javacoco requires toolVersion 0.8.7 to be compatible
Add fields in checkstyle to fail build when there are failures or warnings, and disallow push

Codecov Report

Merging #4 (fa591b3) into master (4c9f75d) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master       #4   +/-   ##
=========================================
  Coverage     72.15%   72.15%
  Complexity      399      399
=========================================
  Files            70       70
  Lines          1232     1232
  Branches        125      125
=========================================
  Hits            889      889
  Misses          311      311
  Partials         32       32

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 4c9f75d...fa591b3. Read the comment docs.


Standard Wokwi and Verilog demo inclusion

Greets,
Uncertain if these are all in for 3.5.  They are the standard wokwi projects and verilog demo, migrated to TT3.5.
I will also be pushing one of my projects and hopefully one or two "fpga" type deals, today, and list them here.
https://github.com/psychogenic/tt03p5-verilog-demo
https://github.com/psychogenic/tt03p5-UARTcharacter
https://github.com/psychogenic/tt03p5-UARTstring
https://github.com/psychogenic/tt03p5-padlock
https://github.com/psychogenic/tt03p5-7segstringdisplay

Can you please sort them from "most interesting" to "least interesting"? We'll fit as many as possible

That's one for Matt!

@mattvenn

verilog demo is the least interesting. The other 4 are wokwi designs and it's useful to have gone through the tt3p5 process. So if there are any free slots, just choose at random.


Update to Spring 4.3.10

The Current GA Spring version, 4.3.10.GA, is available from maven central. NEBA should update to this version.

Done


Update NavigatorIOS.ios.js

Thanks for submitting a pull request! Please provide enough information so that others can review your pull request:

Unless you are a React Native release maintainer and cherry-picking an existing commit into a current release, ensure your pull request is targeting the master React Native branch.

(You can skip this if you're fixing a typo or adding an app to the Showcase.)
Explain the motivation for making this change. What existing problem does the pull request solve?
I'm new to React-Native and noticed a broken link in the documentation.  It's just a quick fix.
Prefer small pull requests. These are much easier to review and more likely to get merged. Make sure the PR does only one thing, otherwise please split it.
Test plan (required)
Demonstrate the code is solid. Example: The exact commands you ran and their output, screenshots / videos if the pull request changes UI.
Make sure tests pass on both Travis and Circle CI.
Code formatting
Look around. Match the style of the rest of the codebase. See also the simple style guide.
For more info, see the "Pull Requests" section of our "Contributing" guidelines.
Adjusted a broken link to the Navigator component

By analyzing the blame information on this pull request, we identified @caabernathy and @hramos to be potential reviewers.

@facebook-github-bot shipit

Thanks for importing. If you are an FB employee go to Phabricator to review internal test results.


Image:commamd text area has not confrim button [REPLACEMENT ISSUE]

The original issue
Id: 1162
Title: Image:commamd text area has not confrim button

could not be created.
This is a dummy issue, replacing the original one. It contains everything but the original issue description. In case the gitlab repository is still existing, visit the following link to show the original issue:
TODO

In GitLab by @liyanq528 on Nov 8, 2019, 07:49
fixed by pull request #1177

In GitLab by @sokril on Nov 8, 2019, 08:20
assigned to @cuiaq123

In GitLab by @liyanq528 on Nov 11, 2019, 08:52
mentioned in merge request !485

In GitLab by @liyanq528 on Nov 12, 2019, 02:22
mentioned in merge request !872

In GitLab by @liyanq528 on Nov 13, 2019, 04:37
mentioned in merge request !603

In GitLab by @liyanq528 on Nov 13, 2019, 07:25
mentioned in merge request !507


CTE support

Is your feature request related to a problem? Please describe.
I'm always frustrated when I see another async ORM without CTE. TortoiseORM, orm (from encode), and now ormar.
Describe the solution you'd like
I'd like to have CTE (and especially Recursive CTE) in ormar. There is a good implementation in PeeWee library, that I use right now.
Describe alternatives you've considered
Additional context

Hi, with orms that actually try to parse the results into corresponding Models and validate the results it's always challenging to allow users to produce derived columns and subqueries and still be able to parse the result into the meaningful end models (either also derived based on input columns or manually specified somewhere).
Similar to issue #266 and corresponding discussions.

hello, any progress on this issue?


Add Octave GUI

Add Octave GUI 4.0.3
If there’s a checkbox you can’t complete for any reason, that's okay, just explain in detail why you weren’t able to do so.
After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} reports 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.

Additionally, if adding a new cask:

[x] Named the cask according to the token reference.
[x] brew cask install {{cask_file}} worked successfully.
[x] brew cask uninstall {{cask_file}} worked successfully.
[x] Checked there are no open pull requests for the same cask.
[x] Checked the cask was not already refused in closed issues.
[x] Checked the cask is submitted to the correct repo.

Thanks @commitay I hadn't understood the appcast.

Please complete all the steps in the PR template.

Does this conflict with the Homebrew formula for Ocatve?

Hi, checklist ready. This is not an update to a cask, so sha hasn't changed.

@miccal I installed it and have no problem on running both the app, and the brew formula.

The original has an --without-qt flag. Doesn’t that mean it gets built with a GUI by default? What does this cask offer over the formula?

The original has an --without-qt flag. Doesn’t that mean it gets built with a GUI by default?

It looks like this option was removed when octave migrated from science to core.
https://github.com/Homebrew/homebrew-core/pull/15909, https://github.com/Homebrew/homebrew-core/issues/15986

--without-qt is still there (brew cat octave). But even if it were --with-qt, is there anything we gain by this duplication that the formula can’t provide?

The current options for installing the octave formula are:
--with-java
	Build with java support
--HEAD
	Install HEAD version

as described by brew info octave. If building octave with the --with-qt flag would install the drop-in replacement for Matlab that the Octave app is, then this cask would add nothing to that, but it's not currently the case. The GUI doesn't even start by force(--force-gui) after building with qt.

The point of removing the Qt option was that upstream has not fixed the option so that it works with the current version of Qt. Merging this cask isn't exactly helping with the goal of encouraging them to fix that.

@ilovezfs Was unaware of that. https://github.com/caskroom/homebrew-cask/pull/38549


Wrong Open Api definition in /api/v1/contracts/{contractId}/actions

Please provide us with the following information:

This issue is for a: (mark with an x)
- [x] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Hello, I have generated a C# client for the Azure Workbench Api using Nswag and I am having trouble when calling
/api/v1/contracts/{contractId}/actions endpoint
The swagger.json description specifies that this endpoint returns a type called WorkflowStateTransitionList with a  json property called "workflowStateTransitions" but it is actually returning a property called "workflowFunctions" that represents a different type so autogenerated clients can't deserialize the response properly.

Thanks, will track swagger updates in your other issue #89


Fix re-rendering in Popup and dioxus-toast

What this PR does 📖

This PR eliminates a double-render in the Popup element and fixes dioxus-toast.
the dioxus-toast crate caused everything that used it to re-render every 100ms. I forked it, submitted a PR, and switched to the forked version in the mean time.

Which issue(s) this PR fixes 🔨

Resolve #140

Special notes for reviewers 🗒
Additional comments 🎤
The IconInput element also re-renders on every key-press. That may be able to be improved but there are higher priorities right now.

Put Change Requested just for the minor Merge Conflict. Otherwise couldn't find any bugs that weren't already on dev 👍


PHP Fatal Error -> must be string, null given

Plugin Version 1.0.13
PHP 8.1
#35 {main}
thrown in /path removed/includes/src/Plugin/Payment/Method.php on line 97
[31-Dec-2023 11:07:04 Europe/Berlin] PHP Fatal error:  Uncaught TypeError: JTL\Plugin\Payment\Method::__construct(): Argument #1 ($moduleID) must be of type string, null given, called in /path removed/plugins/jtl_post
financecheckout/Webhooks/Strategies/PostFinanceCheckoutNameOrderUpdateTransactionStrategy.php on line 83 and defined in /path removed/includes/src/Plugin/Payment/Method.php:97

hi @Alcpaone , did this happened often or it was a one time thing ?

@thibault-mambour
i will check the php log again to see if there is any actual error. I saw this error just after a update of the plugin when i checked the logfile. Was Plugin Version 1.0.13 or 1.0.12

@thibault-mambour happens again and again also with Plugin Version 1.0.20
I can't say if this is the same error. If not, please let me know and i open a new issue.
#32 {main}
thrown in path_removed/plugins/jtl_postfinancecheckout/frontend/postfinancecheckout_iframe.php on line 14
[24-Jan-2024 18:29:20 Europe/Berlin] PHP Fatal error:  Uncaught TypeError: strtolower(): Argument #1 ($string) must be of type string, null given in path_removed/plugins/jtl_postfinancecheckout/frontend/postfinancecheckout_iframe.php:14
When will be there a new release? There are so many issues open.

with release 1.0.23 still error in log:
thrown in /......./plugins/jtl_postfinancecheckout/vendor/postfinancecheckout/sdk/lib/ApiClient.php on line 497
[06-Mar-2024 14:52:42 Europe/Berlin] PHP Fatal error:  Uncaught TypeError: strtolower(): Argument #1 ($string) must be of type string, null given in /......./plugins/jtl_postfinancecheckout/frontend/postfinancech
eckout_iframe.php:14


Suggetsion

Add 2fa codes so when u trying to log in into a user account with 2fa that the codes send to u idk if its possible but luna grabbers has it

Backup codes for roblox i mean

Let me tell you how Luna Grabber's "backup codes" feature work.
It will simply search the downloads folder for a file named "discord_backup_codes.txt". If the file is found, it will copy the file.
But this feature is not guaranteed to give the correct details, hence this grabber do not have the feature.

Backup codes for roblox i mean

Roblox works on Authy or Google Authticator too, and so its not possible (or easy) to make it a feature.

Let me tell you how Luna Grabber's "backup codes" feature work.
It will simply search the downloads folder for a file named "discord_backup_codes.txt". If the file is found, it will copy the file.
But this feature is not guaranteed to give the correct details, hence this grabber do not have the feature.

Backup codes for roblox i mean

Roblox works on Authy or Google Authenticator too, and so its not possible (or easy) to make it a feature.

A another quostion i was trying to make my own theme but when i run the gui nothing works or did i do something wrong

I was like trying to create a icon but it didnt work

I want to make it like this

I can't help with that. I have seen various people just changing the theme and posting as their own creation (either backdoored or not). This may have bad impacts for this project.

O Np i understand

 I want to make it like this

A Chungus stealer lol