CircuitOperation

Rewrite of #3515 to remove CircuitGates, plus a few other cleanup items. Part of #3235.
Note again the following features are absent from this PR:

Measurement in loops. The current measurement format (a 1:1 dict of keys to results) does not play well with repeating the same measurement multiple times, or with attempting to rename that measurement based on loop index.
Condensed serialization. This feature requires changes outside the CircuitGate itself to allow for references inside the serialization structure.
Condensed circuit diagrams. Similar to serialization, this requires changes to the diagram behavior for printing CircuitOperations separate from the rest of the circuit.

Test failure appears to be a flake; filed #3584 to track. This PR is ready for review.

Caught an issue in this PR while looking into serialization: the name field of FrozenCircuit is not preserved across serializations. The tests miss this because AbstractCircuit.__eq__ does not compare the name field. Working on a fix.

Opted to remove the name field for now, as it's kind of a non sequitur in this PR. Added a TODO to add it back in the condensed-serialization change.

I'd suggest that the CircuitOperation constructor could accept qubit_mapping, params, etc as keyword args (could even implement as a dataclass so you wouldn't have to write out all the boilerplate).

Converted CircuitOperation to a dataclass and cleaned up the repr. @balopat, I'll see if I can capture OP_TREE + InsertionStrategy + device as InitVar alternatives to circuit in the new structure.

All review comments are either addressed in code or require further discussion before implementing. PTAL

There's some weirdness going on with hashing:

from cirq import *
from sympy import *

# internal, level 2
q = LineQubit.range(3)
# internal level 1
k = LineQubit.range(3)
# external level 0
s = LineQubit.range(3)

level2_circ = FrozenCircuit(X(q[0]) ** Symbol('a'))

# "renames" internal 'a' to external 'a1'
op1_level2 = CircuitOperation(level2_circ).with_params({S('a'):S('a1')})
# "renames" internal 'a' to external 'a2'
op2_level2 = CircuitOperation(level2_circ).with_params({S('a'):S('a2')})

level1_circ = FrozenCircuit(X(k[0]) ** S('x'),
                      op1_level2.with_qubits(k[0]),
                      op2_level2.with_qubits(k[0]))
# renames level 1 params x, a1, a2 to external o1, o2, o3
op_level1 = CircuitOperation(level1_circ).with_params({S('x'): S('o1'), S('a1'): S('o2'), S('a2'): S('o3')})

# add an external-only o0 parameter
top_circ = Circuit(Y(s[0]) ** S('o0'), op_level1.with_qubits(s[0]))
print(top_circ)

Throws an error:

Traceback (most recent call last):
  File "scratch_10.py", line 26, in <module>
    print(top_circ)
  File "/Users/balintp/dev/proj/Cirq/cirq/circuits/circuit.py", line 215, in __str__
    return self.to_text_diagram()
  File "/Users/balintp/dev/proj/Cirq/cirq/circuits/circuit.py", line 1066, in to_text_diagram
    transpose=transpose,
  File "/Users/balintp/dev/proj/Cirq/cirq/circuits/circuit.py", line 1128, in to_text_diagram_drawer
    include_tags,
  File "/Users/balintp/dev/proj/Cirq/cirq/circuits/circuit.py", line 2085, in _draw_moment_in_diagram
    info = get_circuit_diagram_info(op, args)
  File "/Users/balintp/dev/proj/Cirq/cirq/protocols/circuit_diagram_info_protocol.py", line 168, in _op_info_with_fallback
    name = str(op.untagged)
  File "/Users/balintp/dev/proj/Cirq/cirq/circuits/circuit_operation.py", line 152, in __str__
    header = self.circuit.serialization_key() + ':'
  File "/Users/balintp/dev/proj/Cirq/cirq/circuits/frozen_circuit.py", line 93, in serialization_key
    key = hash(self)
  File "/Users/balintp/dev/proj/Cirq/cirq/circuits/frozen_circuit.py", line 89, in __hash__
    return hash((self.moments, self.device))
  File "/Users/balintp/dev/proj/Cirq/cirq/ops/moment.py", line 251, in __hash__
    return hash((Moment, tuple(sorted(self.operations, key=lambda op: op.qubits))))
  File "<string>", line 3, in __hash__
TypeError: unhashable type: 'dict'

There's some weirdness going on with hashing: {...}

Hashing weirdness should be resolved now.

Waiting on final review from @balopat. Balint, if I'm not around but everything looks good, you're welcome to merge this PR without further input from me.


[HUDI-2141] Support flink compaction metrics

Change Logs
Support flink compaction metrics
sub-task for HUDI-2141
Impact
Support flink compaction metrics
Risk level (write none, low medium or high below)
low
Documentation Update
Will update documents in another pr
Contributor's checklist

[x] Read through contributor's guide
[x] Change Logs and Impact were stated clearly
[ ] Adequate tests were added if applicable
[ ] CI passed

@danny0405 Hey Danny, could you help review this pr? Thanks

@hudi-bot run azure

Tested locally and only these four metrics are useless. Remove them until we support coordinator metrics. @danny0405  What do you think?

Tested locally and only these four metrics are useless. Remove them until we support coordinator metrics. @danny0405 What do you think?

+1

@hudi-bot run azure

@hudi-bot run azure

@hudi-bot run azure

@danny0405 Ci is green now, would you like to take a final pass~

@hudi-bot run azure


Replace all mentions of build cop with build on-duty

This is something we've been meaning to do for a while.
Companion PR: https://github.com/ampproject/amphtml/pull/33465
Next steps:

[x] Merge and deploy this PR
[x] Update the rotation tool to reflect this name
[x] Update the name of the GitHub team
[x] Merge https://github.com/ampproject/amphtml/pull/33465

FYI @ampproject/build-on-duty

@rcebulko @danielrozenberg I've deployed a new version with this commit, but do not have permissions to see if the amp-onduty-bot app on Google Cloud was correctly updated and the renamed (non-redacted) env vars were correctly set. Could I ask one of you to check at leisure? (There's no hurry since the next time this app needs to update the team (now renamed to @ampproject/build-on-duty is next week.)

Looks fine to me


[orchestra2md] duplicate "Updated EP" columns in tables

Some large message tables have duplicate columns for "Updated EP" pedigree. The data is duplicated in both columns.

See underlying issue in module md-grammar https://github.com/FIXTradingCommunity/md-grammar/issues/4. Not sure yet if this fully explains this bug.


add aws-alb-ingress-controller owners as approver/reviewer

What this PR does / why we need it:
Add the owner of aws-alb-ingress-controller project as approver&reviewers for aws-alb-ingress-controller helm chart
Which issue this PR fixes
(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

fixes #

Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md

/ok-to-test
/lgtm


[WIP] Fixed get_current_namespace for in-cluster configuration

Issue link

What changes have been made

Verification steps

Checks

[ ] I've made sure the tests are passing.
Testing Strategy

[ ] Unit tests
[ ] Manual tests
[ ] Testing is not required for this change

Fixed in #543


[bug] Hosted Gorilla:

Exception: Error communicating with OpenAI: HTTPConnectionPool(host='zanino.millennium.berkeley.edu', port=8000): Max retries exceeded with url: /v1/chat/completions (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7ad587212b30>: Failed to establish a new connection: [Errno 111] Connection refused'))
Failed model: gorilla-7b-hf-v1, for prompt: I would like to see a astronaut riding on a horse on moon with indian flag in hand

Thanks for raising @AdityaPrasad275 The campus (UC Berkeley) lost power which led to this, this should now be fixed.


OnDidChange TextEvent values not set correctly upon single newline character.

Reproduce:
Subscribe to the TextEditor OnDidChange event and simply output the TextEvent object to the console log.
Enter a newline into a new text buffer in the UI (Hit Enter/Return) to fire off the OnDidChange event.
Examine the logged console object:

The TextEvent object field 'newText' does not include the newline character, it is an empty String.
The oldRange values are incorrect for the end/start fields.  They show the same position as the newRange.

Compare this to a backspace/delete that removes the newline and moves the cursor up one row.
The TextEvent object field 'oldText' includes the newline character that was deleted.
I think the two operations should be inverses, and the values of oldText/newText fields mirrors of each other in either situation at the very least.
Atom Version: 1.2.4
System: Ubuntu 14.04.3
Done When:

The TextEvent object field 'newText' is set to a newline character and not an empty String.
The TextEvent oldRange and newRange end/start positions are set correctly.

It looks like two events occur on a newline character being added.  One has the correct information in the TextEvent object, the other is incorrect.

Does this still need work? Should I take it up?

It's still open, so if you can still reproduce it, then yes feel free :grinning:

Well I am able to replicate this bug, and whenever I type in a newline, the onDidChange method is called two times. But the object being passed to the callback function doesn't have keys like oldText or newText like I expected. Instead it has keys like start, end, screenDelta and bufferDelta. Why is this so?

Oh well, ignore my previous comment, I sorted that out.
@james-y
I found that there are two cases which can occur when entering a newline char:
1. when you enter a newline on a line which has text in it
I think you were referring to this case in your original issue. Here, the text editor calls the onDidChange method twice: one for the new line char, and another one for the spaces/tabs it automatically inserts to auto-indent the new line properly. If there's no auto indent, the second textEvent object simply contains an empty string in its newText field. I think this is logical enough.
2. when a newline is entered on a blank line
In this case, the onDidChange method is called three times: one with the correct info, and other two containing empty strings in their newText field. I think I will work on this.


Update default version to 14.17.3

Description
Update default version to 14.17.3
Issues Resolved
NA
Check List

[ ] All tests pass. See TESTING.md for details.
[ ] New functionality includes testing.
[ ] New functionality has been documented in the README if applicable.

          1 Warning

:warning:
This Pull Request is probably missing tests.

  Generated by :no_entry_sign: Danger

Released as: 9.0.0


Release 2.0.0

PRE-RELEASE

[x] update CHANGELOG.md entries
[x] bump version to 2.0.0

package.json
CHANGELOG.md

[x] check successful CI runs

QA

[x] changelog testing

RELEASE

[x] create release tag 2.0.0

[x] successful CI run

[x] release artifacts are available

[x] check mdpresentation-viewer-2.0.0.zip

2.0.0 release is done.

https://github.com/JankariTech/web-app-presentation-viewer/releases/tag/2.0.0


updating release notes and minor fixes

Updated release notes for v4.3.1. Other minor fixes.

@sdwheeler,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

azureps-cmdlets-docs/ResourceManager/docs-conceptual/4.3.1/release-notes-azureps.md
:white_check_mark:Succeeded

azureps-cmdlets-docs/ResourceManager/docs-conceptual/4.3.1/release-notes-ps.md
:white_check_mark:Succeeded

azureps-cmdlets-docs/ResourceManager/docs-conceptual/get-started-azureps.md
:white_check_mark:Succeeded

azureps-cmdlets-docs/ResourceManager/docs-conceptual/install-azurerm-ps.md
:white_check_mark:Succeeded

azureps-cmdlets-docs/ResourceManager/docs-conceptual/overview.md
:white_check_mark:Succeeded

azureps-cmdlets-docs/ResourceManager/docs-conceptual/release-notes-azureps.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

azureps-cmdlets-docs/ResourceManager/docs-conceptual/4.3.1/release-notes-azureps.md
:white_check_mark:Succeeded

azureps-cmdlets-docs/ResourceManager/docs-conceptual/4.3.1/release-notes-ps.md
:white_check_mark:Succeeded

azureps-cmdlets-docs/ResourceManager/docs-conceptual/get-started-azureps.md
:white_check_mark:Succeeded

azureps-cmdlets-docs/ResourceManager/docs-conceptual/install-azurerm-ps.md
:white_check_mark:Succeeded

azureps-cmdlets-docs/ResourceManager/docs-conceptual/overview.md
:white_check_mark:Succeeded

azureps-cmdlets-docs/ResourceManager/docs-conceptual/release-notes-azureps.md
:white_check_mark:Succeeded

docfx.json
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

@TaraMeyer
#sign-off


[1.20.1] Framed Drawers Don't Support 128-bit textures

DO NOT REPORT AN ISSUE IF YOU HAVEN'T TESTED THE ISSUE WITH THE LATEST VERSION IN CURSEFORGE
Functional Storage Version:
1.20.1-1.2.10
Titanium Version:
1.20.1-3.8.27
I used to be able to use my 128-bit textures with framed drawers and it would render perfectly and fit in with all my textures. now it somehow is only using part of the texture to render the drawer.
I would expect when I use a 128-bit texture pack and use that texture on a framed drawer it would render with the 128-bit texture.

Can you attach a screenshot?

Can you attach a screenshot?

Yes, will try to get what it looked like before it didn't work and what it looks like now.

Does it happen only when you change resource packs?

It is the same resource pack just one is in 1.19.2 and the second one is in 1.20.1


ff-env-var-test

SUMMARY

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TEST PLAN

ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

Codecov Report

Merging #17 (774f815) into master (c35e84e) will decrease coverage by 3.87%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master      #17      +/-   ##
==========================================
- Coverage   79.04%   75.17%   -3.88%
==========================================
  Files         936      936
  Lines       47411    47377      -34
  Branches     5778     5875      +97
==========================================
- Hits        37476    35615    -1861
- Misses       9809    11559    +1750
- Partials      126      203      +77

Flag
Coverage Δ

cypress
?

javascript
68.85% <ø> (ø)

mysql
80.57% <ø> (ø)

postgres
80.61% <ø> (ø)

python
80.69% <ø> (ø)

sqlite
80.17% <ø> (ø)

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

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

/testenv up FEATURE_DASHBOARD_NATIVE_FILTERS=true


keypress-listener.js & other Aframe event listeners

Event listeners for window, document, etc should be attached to a-scene not any individual entity.
Make sure the listeners update the volume immediately - force volume.js update function to run
Do we even need keypress-listener.js? Is turning the clipping on and off separately from the controls something the user desires?

Combine all of the event listeners into a single file?


[MNT] Adjusting doc from EEGMiner

As requested by the authors.

Hey @SMLudwig!
You can check the rendered doc here:
https://output.circle-artifacts.com/output/job/e217e925-95b0-4285-8ea3-b238ff02dab8/artifacts/0/dev/generated/braindecode.models.modules.GeneralizedGaussianFilter.html#braindecode.models.modules.GeneralizedGaussianFilter
and here:
https://output.circle-artifacts.com/output/job/e217e925-95b0-4285-8ea3-b238ff02dab8/artifacts/0/dev/generated/braindecode.models.EEGMiner.html#braindecode.models.EEGMiner

Review by email:
"Hi Bruno,
the updated information on the page looks good.
Thanks, and I'd like to wish you good luck with the braindecode project!
Best regards,
Siegfried
"


Adds 'purview retentionevent get' command. Closes #4372

Adds purview retentionevent get command. Closes #4372

Staggering job @nanddeepn!
We'll try to review this ASAP.

Hi @nanddeepn, could you fix the merge conflicts on this PR? I'll review it after 👍

Hi @martinlingstuyl, merged the conflicts.

Can someone please help to rerun the test cases?

I think this is not ready for review @nanddeepn, am I correct? Im seeing some unresolved comments.

Merged manually, thank you 🤙


Wrong clickedNext trigger

When i clicked next button, clickedNext not triggered but if i click back button then clickedNext is triggered ?

Same problem here. Does anyone have a solution?

@Tiorzfk @Tiagofv Same here. Anyone solved this?

help?

same prb !!

same prb !!

same prob


Add ability to customize ObjC bindings names via attributes or xml

An initial stab was taken here:
https://github.com/mono/Embeddinator-4000/pull/366

let's make an RFC and consider all platforms and languages

Agreed. I was just closing the ancient PR and made the issue to not forget the work.

#481 is an older duplicate


Support of before and after actions in preorderschema traversal

Add support to perform an action before and after schema traversal in preorder fashion for schema
for object: structtype, maptype & listtype
Linked: https://github.com/apache/iceberg-python/issues/32

I don't think that this is necessary and I think it also breaks future uses of the visitor.
Despite the name, the visitor this updates doesn't actually perform pre-order traversal. It creates futures that can be called to produce the result of further processing. In Java, we call this the "custom order" visitor because you can use it for any order you want by calling the future at a different point.
This PR changes to actual pre-order traversal. That's fine, but it means that you can't actually customize as much.

Maybe it's me, but I don't understand the value of adding before and after callbacks to this visitor. A node's children are traversed when the future is called and that allows you to do whatever you want before and after further schema traversal. I think it makes more sense to consolidate the logic in the usual methods rather than use callbacks in this case.

Maybe it's me, but I don't understand the value of adding before and after callbacks to this visitor. A node's children are traversed when the future is called and that allows you to do whatever you want before and after further schema traversal. I think it makes more sense to consolidate the logic in the usual methods rather than use callbacks in this case.

It's still half baked I am working on it, but thanks for the feedback, will that into consideration.

This was suggested here: https://github.com/apache/iceberg/pull/7831/files#r1285259053 I'll leave it up to @rdblue to decide if he thinks this is valuable.

Let's keep it as is, and close this for now.


Dev/ft/ring 28333 basic crud

With this hdclient is capable of performing GET/PUT/DELETE on a single hyperdrive, with normally correct error handling (simplisitic since we have only 1 request).
Also added a HTTP server to quick test against a real hyperdrive (cannot until https://scality.atlassian.net/browse/RING-28458 is merged, or you apply the diff in the ticket and compile it yourself).
The keyscheme part is not unit tested. This is on purpose since it will have to change to support split and possibly erasure coding. Didn't seem worth the effort, and it is somewhat tested through the functional tests).

awesome start

@DavidPineauScality @cstoyanov-scality I will decline this PR. I worked a lot on the following branch (handle multipe hyperdrives) to the point it is almost ready. And it implies massive refactoring and code changes. Pointless to reveiw the 2 separately I think.
Better to to not try and diff. So I suggest you wait till I do the PR for RING-28615, then you review the diff against development/1.0


Fix installPhase

~ doesn't expand correctly with the result of overwriting config.xml every time the program starts, thus not being able to save an changes in options.
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Dear @a0x77ry ,
Do you plan to continue working on this?

@drupol No. I've solved it on my end.

Can we close the pr then ?

Yes, of course


Disable SRI for webchat.js hosted with DirectLine (vs CDN)

Disable SRI for webchat.js hosted with DirectLine (vs CDN)
Description
Disable SRI for webchat.js hosted with DirectLine (vs CDN). The hosted webchat gets signed differently during the service builds.

@p-nagpal Let me know when you have finished testing it.


Stop on DirectoryRecord reading

DIC 20170728 remains locked on the DirectoryRecord reading (173/2947) :
http://dl.free.fr/rwyVKJR5b
TiA ;-)

The Directory Record of LBA 40915 is corrupt. Is this no-error disc?

The disc is really in good physical condition. I made a copy with ISOBuster v4.0 and the ISO file has no corrupted sectors (checked with ECC/EDC data). This may be a mastering mistake?! You would have an idea to bypass the blocking of DIC?

Uploaded test version.
http://www.mediafire.com/file/eq80y20l9cwf48f/DiscImageCreator_test.7z

Thank you, it works but there is a risk on the quality of the copy?

Perhaps no. Just in case, please check all disc you have.

For AT4, it's ok. I will continue with DIC 20170728, this will allow me to identify other discs problem.
incorporating a warning in DIC would be interesting...


Null

Sorry, this took a while
When using with TLAC you'll want to use the ps4_official_slider option and disable other slider emulation keybinds.
I am not sure how to use it with MegaMix+ because I don't own the game.


call service not using py.test. rpc process can't get response.

I write a test_server and test_client to simple use nameko:
here is my repo : https://github.com/jiamo/nameko_research
python test_service_server.py
The test_service_client.py get some codes from cli module.
python test_service_client.py
can't get response.
So is there some misunderstandings in my repo.

Your server script starts and then immediately stops the service https://github.com/jiamo/nameko_research/blob/master/test_service_server.py#L32
You don't need to create a ServiceRunner yourself. You can use the nameko command line to run your service:
$ nameko run test_service_server --config nameko_server.conf
('config is ', {'AMQP_URI_CONFIG_KEY': 'amqp://guest:guest@localhost', 'max_workers': 10, 'AMQP_URI': 'amqp://guest:guest@localhost', 'parent_calls_tracked': 10, 'rpc_exchange': 'nameko-rpc'})
starting services: helloworld
Connected to amqp://guest:**@<IP_ADDRESS>:5672//

Also there is no need to implement the service client as you have. Just use the nameko command line:
nameko shell --config nameko_server.conf
>>> n.rpc.helloworld.hello(name='John')
u'Hello, John!'

Thanks. Some times we need run without  nameko command.
After using nameko run test_service_server --config nameko_server.conf
my client py can work now.
But after comment the  runner.stop(),  python test_service_server.py still can' t work.

You need to both apply the eventlet monkey patch and call wait() on the runner to block until it exits.
index e764db8..8597563 100644
--- a/test_service_server.py
+++ b/test_service_server.py
@@ -1,3 +1,6 @@
+import eventlet
+eventlet.monkey_patch()
+
 from nameko.rpc import rpc
 from nameko.runners import ServiceRunner
 from nameko.testing.utils import get_container
@@ -29,7 +32,7 @@ def main():
     # start both services
     runner.start()

-    runner.stop()
+    runner.wait()
     # container = ServiceContainer(HelloWorldService, config=config)
     # service_extensions = list(container.extensions)
     # print ("service_extensions is ", service_extensions)

You should really consider using the code from nameko.cli.run even if you don't use the command line script, because the signal handing is non-trivial. For example, see https://github.com/onefinestay/nameko/blob/master/nameko/cli/run.py#L134
I'm going to close this issue now. If you have more questions about how to use nameko please post them to the (new!) google group.


Generate features

This merge is to complete part of automatic generation of features in server configuration: https://github.com/OpenLiberty/open-liberty/issues/12983

@TrevCraw Need to get at least some of the builds passing before merging this PR.

@cherylking Is there an easy way to kick off another try without merging more code? This just needed the new ci.common merge.


Still alive?

As there is neither a commit from 2019, nor any issue: Is this project still alive? I'm currently looking for a SMTPD solution in plain Java and SubEtha looks promising, but I'm unsure whether SubEtha is still maintained.
Regards

Fabian

Hi Fabian, active fork with a number of improvements at https://github.com/davidmoten/subethasmtp.

Hi David
thanks a lot for this hint! I'll take a look and I'm really glad someone takes care of this project. 👍


Duplicate Text in Introduction Text

The second paragraph in the introductory text has the same content as the first paragraph:
You use cumulative flow diagrams (CFD) to monitor the flow of work through a system. The two primary metrics to track, cycle time and lead time, can be extracted from the chart.

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

ID: ea9310f2-b131-3903-0c15-5bbebbd95959
Version Independent ID: 22486f35-4e75-8dd4-7c97-cd3c6e8245fc
Content: Cumulative flow guidance - Azure DevOps
Content Source: docs/report/dashboards/cumulative-flow-cycle-lead-time-guidance.md
Product: devops
Technology: devops-analytics
GitHub Login: @KathrynEE
Microsoft Alias: kaelli

Documentation update is in https://dev.azure.com/mseng/TechnicalContent/_git/vsts-docs-pr/pullrequest/491370

@nbkhope -- Renan, thank you for your feedback.  I have updated the documentation and it should be live by tomorrow.
I am closing this issue now.  You are welcome to @ mention me for any followup.
We hope to hear from you again.


Prototype for Profile page.

Some changes were from Week 0. Still working on designing page and will add more tests.

Looks good to me!

Looks good to me!


Add unchecked Vector methods

The data validity checks that were used in the default implementation (added in #49) significantly slow the calculation of a harmonic mean with f32 and f64 data (Criterion benchmarks added in the same PR).
Consider adding an unchecked version that is more performant and assumes data validation by the user.  Perhaps under an optional feature and not part of the default crate distribution.  Panics will occur with zero values.  Use of values < 0.0 will not panic, but return f32 or f64 values that are not valid geometric means.
A refactor to:
let sum_of_reciprocal = self.components.iter().copied().map(|x| x.powi(-1)).sum::<T>();

in place of the #49 approach improves execution time from:
Vector mean_harmonic method: f64 5D Vector
                        time:   [4.6057 ns 4.6161 ns 4.6294 ns]
                        change: [+0.0120% +0.2572% +0.5116%] (p = 0.04 < 0.05)
                        Change within noise threshold.
Found 5 outliers among 100 measurements (5.00%)
  5 (5.00%) high severe

to:
Vector mean_harmonic method: f64 5D Vector
                        time:   [542.75 ps 543.07 ps 543.48 ps]
                        change: [-88.222% -88.193% -88.164%] (p = 0.00 < 0.05)
                        Performance has improved.
Found 11 outliers among 100 measurements (11.00%)
  3 (3.00%) high mild
  8 (8.00%) high severe

The f32 benchmark changes are comparable.
Test environment:
MBP 16" 2021
Apple M1 Max
32GB RAM
macOS 12.1
related #44
related #8

This likely applies to methods other than mean_harmonic.  I generalized the title and will look into this.  Perhaps under an optional feature.


C++ elastix cannot set a mask

Use RegisterImages api and set two masks like this:
error = rigid->RegisterImages(m_FixedImage, m_MovingImage, parameters, "../../output/", true, true, m_FixedMask, m_MovingMask);
but:
-fMask    unspecified, so no fixed mask used
-mMask    unspecified, so no moving mask used
because the Fixed(Moving)MaskContainer is created in elxElastixMain.cxx and deleted in elxElastixTemplate.hxx.
I don't know why c++ elastix must check that whether CommandLineArgument contains -fMask(-mMask) and why nobody found this obvious bug?
Can you fix this bug? Thx!

The pixeltype of mask image must be the "unsigned char", and it can work now


Tracking features for next iteration of Restore-DbaDatabase

Is this:
Just place "x" to indicate selection (e.g. "[x]")

[x] feature
[ ] bug:

A place to keep track of things people would like adding to the Restore-DbaDatabase functionality in the next iteration.
So far I've got (Ticked means I've got it working):

[x] IgnoreLogBackup will now make MaintenanceSolution skip the Log folder as well for extra speed
[x] DirectoryRecurse switch to make Directory filter recurse
[x] Standby is now an option for a restored db
[ ] Restore from Azure support (Backups and Headers done)
[ ] Continue restore on a db in recovery or standby modes
[ ] Potentially an option to allow fast and loose restores for log files (not convinced it's a great idea, but people seem to like the idea)

Anything else people would like?

It would be nice if there was a switch that if you pass something to DatabaseName, it would auto-rename the log and datafiles.
For example, if I want to restore AdventureWorks to AdventureWorks_Restore on the same server, it would be nice to rename the physical files to something like AdventureWorks_Restore.mdf and AdventureWorks_Restore_log.ldf.
I could set DestinationFilePrefix to the new database name, but then if the datafile of the original database was called AdventureWorks.mdf, it would name it AdventureWorks_RestoreAdventureWorks.mdf, which isn't very pretty. :)
Maybe I could make it work with FileMapping, but then I think I would have to know what the logical names & default file path are in advance, and I'm trying to write up something fairly generic that I could re-use.

How would you want it to handle multiple datafiles or logfiles? That's the
bit I couldn't come up with a decent plan for. Appending an id number is
one option, but how do we get them in the 'right' order for all users?
On Wed, 17 May 2017, 23:37 Bryan H<EMAIL_ADDRESS>wrote:

It would be nice if there was a switch that if you pass something to
DatabaseName, it would auto-rename the log and datafiles.
For example, if I want to restore AdventureWorks to AdventureWorks_Restore
on the same server, it would be nice to rename the physical files to
something like AdventureWorks_Restore.mdf and
AdventureWorks_Restore_log.ldf.
I could set DestinationFilePrefix to the new database name, but then if
the datafile of the original database was called AdventureWorks.mdf, it
would name it AdventureWorks_RestoreAdventureWorks.mdf, which isn't very
pretty. :)
Maybe I could make it work with FileMapping, but then I think I would have
to know what the logical names & default file path are in advance, and I'm
trying to write up something fairly generic that I could re-use.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/sqlcollaborative/dbatools/issues/1201#issuecomment-302250834,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFWoZqAwN1S1FJBO5rWw5MLXkkH0WCf-ks5r63ahgaJpZM4NaMVB
.

I see than @galador asked for things how SSMS do in restores, I want this too, and going to make my own branch for this naming behavior.
How SSMS do when you have more than 1 data file?
just adds **_x** (where x is 0...n)to file names starting with second data file

My backlog for Restore-DbaDatabase:

do restores as in this issue, this behavior is essential for many of us
having prefixes and suffixes for database names and/or files

template for names

restoring database with name $prefix$DatabaseName$suffix
changing data and log names to [$prefix]$Databasename[$suffix][$FileNumber].[mdf|ndf|ldf] if corresponding paramaters specified to command

Yes, basically if there was an option to handle the file renames like SSMS (which is to say, basically replace any instance of OldDatabaseName with NewDatabaseName), e.g.:

This example is renaming AdventureWorks2012 to AdventureWorks.

From Slack: add support to restore database with keep_cdc

keep_cdc is one of the few things they haven't surfaced in SMO atm. It can be done by getting the T-SQL and injecting it back in, but it's a bit of a hack as we'd then have to passed it back in via Invoke-DbaSqlCmd, so we'd also end up with a different output to other restores

Continue works with file based restores, Get-DbaBackupHistory needs some more work for that bit to work properly, and don't want to drag too many files into this PR.
Going to do a merge of dev to see how much work that's going to cause, and then I'll work on the renaming options

PR 1304 just done in
These features in:
IgnoreLogBackup will now make MaintenanceSolution skip the Log folder as well for extra speed
DirectoryRecurse switch to make Directory filter recurse
Standby is now an option for a restored db
Continue restore on a db in recovery or standby modes
Will add the others in a bit, keeping a branch out for too long is a bit problematic these days

Just pushing up a new PR with these features:
Restore from Azure
DestinationFileSuffix
Replace dbname in filename

Really, really not convinced about the auto numbering of files during restore being a good idea. SSMS only does that during file creation not restores.
Mainly because files can appear and disappear during restores. It's a logged operation so it 'happens' during the restore (SQL doesn't just go from A-Z, it goes via B,C,D,E, etc and if C means it adds 3 files it adds 3 files, then removes 2 at E and puts 3 more back at Q)
So we could scan all the filelists at the start of the restore and work it out. But then how do we tell if
Data1 -> C:\data\data_1.mdf at point C
is the same as
Data1 -> e:\data\data_1.mdf  at point M,
could have been moved, or it could have been dropped and recreated?
How do we decided the file ordering for numbering? Alphabetically, by size, by type? Each one will be wrong for someone if we try to preempt it. And any of those orderings could change the next time they run the restore.
If someone really wants to do that, they have 2 options to get it done properly:

Name their files upon creation wit x_of_y and stick with prefix and folders
Write a filemapping hash and push it in

If someone want to have a go they can, but I'll put money on the fact I can break it without too much trouble.
My aim with the restore stuff is reliability and repeatability over anything else.

It's not pretty (ie T-SQL hack) but CDC is now in -  https://github.com/sqlcollaborative/dbatools/tree/restorecdc
If anyone who actually uses CDC is reading this, take it for a spin please.

I get 404 error. We are using CDC and service broker. Would love to have this.

@TheRockStarDBA : it's been already committed to the repo, CDC should work fine

All of these are in now in some form or another. Will close this and let newer requests filter in in their own issues


x/exp/cmd/gorelease: expose analysis.Analyzer

Frequently I run gorelease as part of ci to test if anybody has introduced breaking changes. This works well, but is a separate workflow that I have to run in addition to all the linting that already goes on. It would be nice if I could simply add a phase to my current run of []*analysis.Analyzer and reuse the parsing that is already done.
IIUC, this would require fetching the previous versions' AST as an analysis.Fact, so I am neither sure how feasible or efficient this would be, but it would serve to be better integrable into existing metalinters.
EDIT: This may be of less value after #37561, but reparsing the AST does come at cost, so it would be a nice to have regardless.

Jay is for sure the expert here, but

add a phase to my current run of []*analysis.Analyzer and reuse the parsing that is already done

Could you enlighten me as to what this means? You have some existing tool - perhaps gopls - that is doing AST parsing, and you want to feed that AST to gorelease rather than it re-parsing?
What is the benefit - some performance gains? If so, how much do you anticipate gaining? Is this a nice-to-have, or blocking your workflow?
(I'm pretty ignorant to the broader tooling infrastructure, and trying to learn, so that's where the questions are aimed :) )

Could you enlighten me as to what this means? You have some existing tool - perhaps gopls - that is doing AST parsing, and you want to feed that AST to gorelease rather than it re-parsing?

Sure, so I use golangci-lint, a metalinter, that uses the analysis.Analyzer interface to plug together all the govet checks and a bunch of third party ones from the community. It would be trivial to add a new gorelease linter to that project.

What is the benefit - some performance gains? If so, how much do you anticipate gaining? Is this a nice-to-have, or blocking your workflow?

In one of the worst examples, 200k loc, it takes 49s. While golangci-lint can take order of minutes, I imagine most of that delay for gorelease is file reading and AST parsing. Plus golangci-lint has a nice diff feature to just lint lines that changes, which is nice for local checks before pushing to ci.
That being said, we have a workflow today and with #37561, we could technically automate the reporting much like golangci-lint does today.

I like the idea of having an analyzer that protects against incompatible changes.
Architecturally, I guess this fits in somewhere between gorelease and apidiff. There isn't a layer there now, so this would be a pretty big change. I wonder if it should just be a separate tool from gorelease?
The weird bit here I suppose is that the analyzer needs a base version to compare against, which might require downloading a module into the cache. It's fine for gorelease to do that, but it seems unusual for an analyzer.

Yeah, putting this in a new package or apidiff would be fine by me.
Also you are not wrong, but it does feel like an Analysis.Fact or analysis.Analyser.ResultType, and I think I can make a solid case for it. And I have gotten traction on some weirder asks form the analysis team, #44753.

This would be a fair significant change. analysis.Analyzers work on a single package at a time. These can communicate using Fact edges from imported packages (within the same Analyzer) and Results between Analyzers on the same package. {single,multi}checker.Main() take a list of packages and a list of analyzers and output a a list of Diagnostics (+ some extra output). Packages are loaded using packages.Load().
I am looking into making analysis support running list of root packages.Packages and a list of analysis.Analyzers and returning the Facts and Diagnostics of the root actions. (Exposing Results runs into trouble with unitchecker's requirements.) Calling this would likely happen outside of a {single,multi}checker.Main(). I suspect this is not quite compatible with your all of your goals.
The main problem with trying to do this in the analysis package is that it is missing information. You need to load pkg@123 and pkg@234, and encode that there is a relationship between pkg@123 and pkg@234. You will need to make this available to a single Pass, i.e. (Analyzer, Package) pair, that can see all of this information at once. How do you plan on making all of this information available to a Pass?

It would be a bit of duplication of effort, but I think that, for a given pkg@234: the current code in a repo, a single analysis.Analyzer could calculate and parse the information for the same package, from the current release of a given module, pkg@123 in your example, then then analysis.Analyzers looking to compare to the "latest release" can depend on that package and do a diff, gorelease being one of them. (I am assuming that some teams may want to introduce different compatibility guarantees, since I have already seen evidence of this, and want to make my abstract design scalable.)
It would be nice to have a module level, I think "root packages.Packages" in your parlance, task that can calculate "latest release" then each package can generate off this, but "fetch latest release" is pretty cheap, and you can still do the ast parsing at the package level for the old version.

@timothy-king: Let me know if this is unclear or you would like more detail.


Fix for WFCORE-2205. NPE in completion with invalid command

Swallow exceptions thrown during completion. Avoid to complete some obvious invalid structures. Added unit test.

@bstansberry , thank-you to pinpoint this, updated.


Update redirectUrl returned by getEmbeddedAppUrl utility

WHY are these changes introduced?
Fixes https://github.com/Shopify/shopify-dev/issues/31542
Partner feedback reported incorrect redirect URL. Confirmed change with @byrichardpowell
WHAT is this pull request doing?
Updates method in auth.js for redirecting to the URL returned by the getEmbeddedAppUrl utility
Note to reviewers
Note to reviewers, not sure how to add/update the test for this change
Checklist
Note: once this PR is merged, it becomes a new release for this template.

[ ] I have added/updated tests for this change
[ ] I have made changes to the README.md file and other related documentation, if applicable

I don't think this file exists any more, it was removed when we introduced the Express package.

I updated outdated content. Closing this PR.


./chunker.go:39:14: cannot assign 1 values to 2 variables

Does not build with:

gopkg.in/check.v1 20d25e2804050c1cd24a7eea1e7a6447dd0e74ec (latest commit)
github.com/satori/go.uuid 1.2.0  (latest stable release)
golang 1.9.4
on x86_64

+ go build -buildmode pie -compiler gc -tags=rpm_crashtraceback -ldflags ' -X github.com/aphistic/golf/version.commit=3dd8b1cba42bfeb69fd0408b7fd1c3c345b2aba6 -X github.com/aphistic/golf/version=0 -B 0x0459c7b20df674541676718023286c91e54799c7 -extldflags '\''-Wl,-z,relro  '\''' -a -v -x -o _bin/golang-github-aphistic-golf github.com/aphistic/golf

[…]

/usr/lib/golang/pkg/tool/linux_amd64/compile -o $WORK/github.com/satori/go.uuid.a -trimpath $WORK -shared -goversion go1.9.4 -p github.com/satori/go.uuid -complete -installsuffix shared -buildid c25cf3cf87b907b089dd00d0d968205f952d5da6 -D _/usr/share/gocode/src/github.com/satori/go.uuid -I $WORK -pack ./codec.go ./generator.go ./sql.go ./uuid.go
github.com/aphistic/golf
mkdir -p $WORK/github.com/aphistic/golf/_obj/
mkdir -p $WORK/github.com/aphistic/
cd /builddir/build/BUILD/golf-3dd8b1cba42bfeb69fd0408b7fd1c3c345b2aba6/_build/src/github.com/aphistic/golf
/usr/lib/golang/pkg/tool/linux_amd64/compile -o $WORK/github.com/aphistic/golf.a -trimpath $WORK -shared -goversion go1.9.4 -p github.com/aphistic/golf -complete -installsuffix shared -buildid 14453bd4c3f951b5b25be8bb2ae332dc66d374c0 -D _/builddir/build/BUILD/golf-3dd8b1cba42bfeb69fd0408b7fd1c3c345b2aba6/_build/src/github.com/aphistic/golf -I $WORK -I /usr/share/gocode/pkg/linux_amd64_shared -pack ./chunker.go ./client.go ./json.go ./log.go ./log_default.go ./logger.go ./main.go ./message.go
# github.com/aphistic/golf
./chunker.go:39:14: cannot assign 1 values to 2 variables

Hey! This is caused by the go.uuid library changing the interface for generating a random uuid and returning an error in addition to the uuid now (on the master branch).  If you use commit 4d95b0abb24e76b21d0f20060632c08734b5928b of golf it should work for you on the latest stable version of go.uuid.  Will that work for your use case?

That works indeed, sorry for the bother. Would you terribly mind doing a release every time  github.com/satori/go.uuid does a release ? That would avoid people doing the same mistake as me.

No problem! I'm not sure how I feel about tying releases to other libraries, though.  That might make for a lot of superfluous releases if there are a number of dependencies.  In the past I've read that Go libraries shouldn't vendor things and should strive to support the master branch on dependencies, so that's why I ended up changing it on master in golf as well.
If it makes it easier for you I can definitely tag that commit as a release so you can target that instead of a commit hash.  If you don't mind, how are you handling your dependency management? Are you using something like glide or dep?

As far as I understand release (or tags but in github a release is pretty much a tag) should mark a stable API state of your project and of the things it depends on. (and gopkg.in is great for best practices)
It's quite right to have a master of dev branch that follows other upstreams latest state, as long as it is released once in a while (do remind the other projects you use to do the same or state is never stabilized). Vendoring is quite evil as it incites projects to vendor API states which have not stabilized, and forget to update to  stable releases of the other libraries afterwards. Once they notice they are hopelessly out of date trying to resync can seem a Sisyphean task and the project dies (or rots).
Right now our dep management is delegated to the system package manager (rpm). Computing the other projects a piece of code needs is delegated to https://github.com/gofed/symbols-extractor.
Sadly this is all unversioned and the versions to use are picked by hand (with the following basic rules: always use latest release of the major version needed if it exists, only fall back to a commit if there is a particular bug that needs it or the project has let hundreds of commits accumulate without releasing).
As soon as dep matures and gets used a little more we're probably couple the symbol extractor to dep to extract version constrains, as long as they are sane (if every project tries to depend on a different commit we'll just ignore go dep. An automated tracker can only work if projects converge to a limited number of releases)


Some fixes

[] windowbg2 style does not use with SMF 2.1 more.
[] small fix for undefined index 'name' on Canned Replies area.
Signed-off-by: Bugo<EMAIL_ADDRESS>

Hi @dragomano ,
Thanks for the fixes.  Could you cleanup the changes pointed out in Scrutinizer and this should be good to merge: https://scrutinizer-ci.com/g/SimpleDesk/SimpleDesk/inspections/159787c7-6eeb-4f00-af02-ad1af9c0b370


Grid breakpoint issues

Hey all,
I've been testing the grid system out a bit and I've run into a few bugs every now and then.
Biggest issue seems to be that my defined breakpoints are ignored. I've noticed that sometimes the media queries in the generated CSS seem to be out of order– for instance, I'll get the large breakpoint styling overriding the medium breakpoint styling when my viewport is clearly a medium size.
Heres one I'm currently seeing. I've set my breakpoints for a grid below:

I then notice that the large breakpoint grid layout does not go into effect until 993px. Sure enough, when I inspected the cell element, I see that the css media query is set to 992px.

It seems that maybe thats a default breakpoint that you guys might have in the code. I haven't checked the src yet. As you can see, there is a media query that matches my defined break point a little lower– but it seems to precede the 992px query, which overrides it.
I really like the developer experience of this grid system though. Keep it up!

Hey Jacob, I just realized I never responded and closed this. January was a wild month!
Thanks for all your help. You ended up pointing me in the right direction. Because I needed different grid providers within the same app, I ended up using the scopeCSSTo prop and everything was great after that!

💥


Basic autocomplete

We need @JahdielSantander

Fixed z-index
Fixed rounded pagination

It should be done on the user side. For instance, check the example, there is a fixed list of objects for autocomplete. Dobunce should not be done, but for fetched item. It should, so it depends on the user.
Sent from my iPhone

On Nov 14, 2018, at 7:32 PM, Yoel<EMAIL_ADDRESS>wrote:
@MackYoel commented on this pull request.
In src/components/Autocomplete.vue:

 value: '',

 showItems: true,

 itemsHover: false,

 selectedItem: undefined,

 selectedIndex: undefined

}
},

watch: {
items(newItems) {

 this.selectedIndex = newItems.length <= this.autoselect ? 0 : undefined

}
},

methods: {
onInput($event) {
What about debounced input ?

—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub, or mute the thread.


Installation issue on Macbook with apple M1 chip

When I try to install the GUI on a MACbook with apple M1 chip, and MacOS Ventura 13.0. The GUI file does not appear, I get the following message in the installation:
/Users/Pelon/Downloads/bruker2nifti-master/setupper/run_setupper_MAC ; exit;
Pelon@Javier-MacBookPro-2 ~ % /Users/Pelon/Downloads/bruker2nifti-master/setupper/run_setupper_MAC ; exit;
Creating virtual environment, installing the libraries and deactivating:
./setupper_MAC.sh: line 16: pip: command not found
./setupper_MAC.sh: line 17: virtualenv: command not found
./setupper_MAC.sh: line 18: venv/bin/activate: No such file or directory
Saving session...
...copying shared history...
...saving history...truncating history files...
...completed.
[Process completed]
Any help on how to fix this is greatly appreciated

This has nothing to do with apple M1, your python environment is incomplete.

Hello!
The takeaway is:
./setupper_MAC.sh: line 16: pip: command not found

So you do not have a python installed from where you are starting the environment.
You would have the same issue if running the CLI or if running the command in any other way.
More info about dependencies in python can be found on this guide:
https://www.fullstackpython.com/application-dependencies.html

More specifically to your question, you can follow the guide there:
https://www.freecodecamp.org/news/pip-command-not-found-mac-and-linux-error-solved/

The page suggest to check if pip in installed with:python3 -m pip --version
If not, then to go over this page https://pip.pypa.io/en/stable/installation/ and follow the instrcutions.

I'm closing the issue for now. Please open a new issue if you have any further question, or if something goes wrong after installing pip.


[$250] Track expense - "Join" button appears in report details page when tracking expense in self DM

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 9.0.1-0
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Issue reported by: Applause -Internal Team
Action Performed:

Go to staging.new.expensify.com
Go to self DM
Track a manual expense
Go to transaction thread
Click on the chat header

Expected Result:
"Join" button will not appear in report details page
Actual Result:
"Join" button appears in report details page
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence

https://github.com/Expensify/App/assets/78819774/609b50b0-fad6-4647-af21-0734a99d7de4
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~011a02e6fd1b333eff
Upwork Job ID:<PHONE_NUMBER>935465741
Last Price Increase: 2024-06-24

Issue OwnerCurrent Issue Owner: @akinwale

@twisterdotcom  FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

We think that this bug might be related to #vip-vsp

Proposal
Please re-state the problem that we are trying to solve in this issue.
Join button shows in the track expense report details page.
What is the root cause of that problem?
We already hide the join button if it's an expense report.
https://github.com/Expensify/App/blob/017605269c9f3a351522784aec04dd12644ec564/src/pages/ReportDetailsPage.tsx#L450
But the expense report only covers invoice, IOU/expense report, and IOU/expense transaction thread.
https://github.com/Expensify/App/blob/017605269c9f3a351522784aec04dd12644ec564/src/pages/ReportDetailsPage.tsx#L123
What changes do you think we should make in order to solve the problem?

Add a new condition to check if it's a track expense report.
const canJoin = !isExpenseReport && !ReportUtils.isTrackExpenseReport(report) && ReportUtils.canJoinChat(report, parentReportAction, policy);

we can optionally move the condition to canJoinChat

@arosiclair or @akinwale - can we assign @bernhardoj here?

Just moving this ahead before Andrew comes online. @bernhardoj, can you please raise the PR for this quickly as it's a deploy blocker? Thanks!

Merged the PR. Asking for a CP

Fix works on staging

BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

[x]  [@c3024] The PR that introduced the bug has been identified. Link to the PR: #43251
[x]  [@c3024] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment: https://github.com/bernhardoj/Expensify/commit/9c88ab83f3a9402b28f10f716e861791f311da2d#r144232517
[x]  [@c3024] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion: No, this could not have been identified earlier.
[x]  [@c3024] Determine if we should create a regression test for this bug. No, this was caught in staging. So, no separate test is required.
[x]  [@c3024] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again. NA

Hello folks, sorry I was OOO last week. I have a bunch to do, I will get them all done today. Thanks for your patience.

Payment Summary:
@bernhardoj paid $250 here (Contributor)

@c3024 paid $250 here (Contributor)


canonicalLocaleIdentifierFromString crashes with invalid input

CFLocaleCreateCanonicalLocaleIdentifierFromString may return nil, so it crashes when we force cast it to String. We're already handling this properly in the internal function, so just call into that one.
Resolves rdar://110547526

@swift-ci  please test

@swift-ci test


[BUG] Application Insights crashes Smart TV application after 15 minutes

Description/Screenshot
Recently I have performance problems with applicaciont insights. Application sends differents events using trackPageView() and trackEvent(). When we have deactivated application inshights analytics, apllication works properly.
Steps to Reproduce

Navigate between different pages.
Open video player
Send beat events and actions (play, pause and so on).

OS/Browser: WebOS LG Smart TV Chrome/53.0.2785.34
SDK Version [e.g. 22]: 2.7.4, 2.4.4
How you initialized the SDK:

    (<any>window).appInsights = new ApplicationInsights({
            config: {
              instrumentationKey: this._insightsId,
            }
      });
      (<any>window).appInsights.loadAppInsights();

Expected behavior
Prevent application crash or degradation services
Additional context
We haven't got any more information with debugger

@JESUMH  so just to double confirm that is ApplicationInsights analytics plugin causing crashes of your website or just lowering your website performance? there are some configs that might help:
enableDebugExceptions disablePageUnloadEvents disablePageShowEvents disableDbgExt

@JESUMH we would need some additional information to understand how / why this is occurring as we work really hard to avoid crashing any hosting application.
As you mentioned that this is a Smart TV, I will also assume that this is a low memory environment. As the SDK is targeted at web browsers the defaults are set based on the common environment. There are several optional configuration options that you could try adjusting to better support the low memory environment such as

eventsLimitInMem to reduce the number of batched events
maxBatchInterval to change the amount of between sending batched events (defaults to 15 seconds 15000)
isRetryDisabled to drop events if the SDK can't talk to the endpoint (which could lead to an excessive number of events in memory because of multiple retries.
enableSessionStorageBuffer While events are waiting for an acknowledgement they are also stored (by default) into session storage, if the SDK can't reach the endpoint the events will continue to be stored (and added) to session storage. If this is disabled it uses an in-memory array buffer (so events will be lost between restarts)

I'm not sure if any of these would "solve" the crashing (as it depends on what is causing the crash), as a JS SDK there should not be anything that we can directly do to crash a runtime, but memory exhaustion can have unexpected consequences.

@MSNev @Karlie-777 we enabled debug flag and we saw an error exception (max ajax call overflow). We tested the following app insights options (disableAjaxTracking: true and disableFetchTracking: true) and finally, apps works properly.
Thank you for your attention,


Reproducible Build

[ ] use cargo make
[ ] add Cargo.lock to repo
[ ] add rust-toolchain.toml
[ ] update ci to use cargo make rules
[ ] update CONTRIBUTING.md to mention cargo make
[ ] update pre-commmit.yaml to use cargo make

ref: https://github.com/0xPolygonMiden/miden-vm/issues/1259
This would replace the current Makefile

This might be interesting to you:

https://github.com/lurk-lab/ci-workflows/issues/16
https://github.com/lurk-lab/ci-workflows/pull/4
That is, actions-rs CI is, besides being unmaintained, incompatible with the more recent rust-toolchain.toml (and the absence of that rust-toolchain.toml makes life hard for e.g. dependabot).

But you could depend on the smaller dtolnay/rust-toolchain in CI to follow your local rust-toolchain.toml to install what you need.


[ERROR] Error: Invalid sidebar file at "sidebars.js".

git clone https://github.com/dfinity/portal
cd portal
npm ci
npm run start

><EMAIL_ADDRESS>start
> docusaurus start --host <IP_ADDRESS>

[INFO] Starting the development server...
[INFO] showcase.json validation passed
[WARNING] Warning: no env variables found for Contentful integration. Using mock conversations data.
[WARNING] Warning: no env variables found for Airtable integration. Using mock airtable data.
[WARNING] Warning: no env variables found for Youtube integration. Using mock youtube data.
[ERROR] Loading of version failed for version current
[ERROR] Error: Invalid sidebar file at "sidebars.js".
These sidebar document ids do not exist:
- developer-docs/developer-tools/cli-tools/cli-reference/dfx-bootstrap
- developer-docs/developer-tools/cli-tools/cli-reference/dfx-build
- developer-docs/developer-tools/cli-tools/cli-reference/dfx-cache
- developer-docs/developer-tools/cli-tools/cli-reference/dfx-canister
- developer-docs/developer-tools/cli-tools/cli-reference/dfx-deploy
- developer-docs/developer-tools/cli-tools/cli-reference/dfx-deps
- developer-docs/developer-tools/cli-tools/cli-reference/dfx-envars
- developer-docs/developer-tools/cli-tools/cli-reference/dfx-generate
- developer-docs/developer-tools/cli-tools/cli-reference/dfx-help
- developer-docs/developer-tools/cli-tools/cli-reference/dfx-identity
- developer-docs/developer-tools/cli-tools/cli-reference/dfx-info
- developer-docs/developer-tools/cli-tools/cli-reference/dfx-ledger
- developer-docs/developer-tools/cli-tools/cli-reference/dfx-new
- developer-docs/developer-tools/cli-tools/cli-reference/dfx-nns
- developer-docs/developer-tools/cli-tools/cli-reference/dfx-parent
- developer-docs/developer-tools/cli-tools/cli-reference/dfx-ping
- developer-docs/developer-tools/cli-tools/cli-reference/dfx-quickstart
- developer-docs/developer-tools/cli-tools/cli-reference/dfx-replica
- developer-docs/developer-tools/cli-tools/cli-reference/dfx-schema
- developer-docs/developer-tools/cli-tools/cli-reference/dfx-sns
- developer-docs/developer-tools/cli-tools/cli-reference/dfx-start
- developer-docs/developer-tools/cli-tools/cli-reference/dfx-stop
- developer-docs/developer-tools/cli-tools/cli-reference/dfx-upgrade
- developer-docs/developer-tools/cli-tools/cli-reference/dfx-wallet
- developer-docs/developer-tools/cli-tools/cli-reference/index
- developer-docs/developer-tools/cli-tools/dfxvm/docs/cli-reference/dfx/dfx
- developer-docs/developer-tools/cli-tools/dfxvm/docs/cli-reference/dfxvm-init/dfxvm-init
- developer-docs/developer-tools/cli-tools/dfxvm/docs/cli-reference/dfxvm/dfxvm-default
- developer-docs/developer-tools/cli-tools/dfxvm/docs/cli-reference/dfxvm/dfxvm-install
- developer-docs/developer-tools/cli-tools/dfxvm/docs/cli-reference/dfxvm/dfxvm-list
- developer-docs/developer-tools/cli-tools/dfxvm/docs/cli-reference/dfxvm/dfxvm-self-uninstall
- developer-docs/developer-tools/cli-tools/dfxvm/docs/cli-reference/dfxvm/dfxvm-self-update
- developer-docs/developer-tools/cli-tools/dfxvm/docs/cli-reference/dfxvm/dfxvm-uninstall
- developer-docs/developer-tools/cli-tools/dfxvm/docs/cli-reference/dfxvm/dfxvm-update
- developer-docs/developer-tools/cli-tools/quill-cli-reference/ckbtc/quill-ckbtc
- developer-docs/developer-tools/cli-tools/quill-cli-reference/ckbtc/quill-ckbtc-balance
- developer-docs/developer-tools/cli-tools/quill-cli-reference/ckbtc/quill-ckbtc-retrieve-btc
- developer-docs/developer-tools/cli-tools/quill-cli-reference/ckbtc/quill-ckbtc-retrieve-btc-status
- developer-docs/developer-tools/cli-tools/quill-cli-reference/ckbtc/quill-ckbtc-transfer
- developer-docs/developer-tools/cli-tools/quill-cli-reference/ckbtc/quill-ckbtc-update-balance
- developer-docs/developer-tools/cli-tools/quill-cli-reference/ckbtc/quill-ckbtc-withdrawal-address
- developer-docs/developer-tools/cli-tools/quill-cli-reference/index
- developer-docs/developer-tools/cli-tools/quill-cli-reference/quill-account-balance
- developer-docs/developer-tools/cli-tools/quill-cli-reference/quill-claim-neurons
- developer-docs/developer-tools/cli-tools/quill-cli-reference/quill-generate
- developer-docs/developer-tools/cli-tools/quill-cli-reference/quill-get-neuron-info
- developer-docs/developer-tools/cli-tools/quill-cli-reference/quill-get-proposal-info
- developer-docs/developer-tools/cli-tools/quill-cli-reference/quill-list-neurons
- developer-docs/developer-tools/cli-tools/quill-cli-reference/quill-list-proposals
- developer-docs/developer-tools/cli-tools/quill-cli-reference/quill-neuron-manage
- developer-docs/developer-tools/cli-tools/quill-cli-reference/quill-neuron-stake
- developer-docs/developer-tools/cli-tools/quill-cli-reference/quill-parent
- developer-docs/developer-tools/cli-tools/quill-cli-reference/quill-public-ids
- developer-docs/developer-tools/cli-tools/quill-cli-reference/quill-qr-code
- developer-docs/developer-tools/cli-tools/quill-cli-reference/quill-replace-node-provider-id
- developer-docs/developer-tools/cli-tools/quill-cli-reference/quill-scanner-qr-code
- developer-docs/developer-tools/cli-tools/quill-cli-reference/quill-send
- developer-docs/developer-tools/cli-tools/quill-cli-reference/quill-transfer
- developer-docs/developer-tools/cli-tools/quill-cli-reference/quill-update-node-provider
- developer-docs/developer-tools/cli-tools/quill-cli-reference/sns/quill-sns
- developer-docs/developer-tools/cli-tools/quill-cli-reference/sns/quill-sns-balance
- developer-docs/developer-tools/cli-tools/quill-cli-reference/sns/quill-sns-configure-dissolve-delay
- developer-docs/developer-tools/cli-tools/quill-cli-reference/sns/quill-sns-disburse
- developer-docs/developer-tools/cli-tools/quill-cli-reference/sns/quill-sns-disburse-maturity
- developer-docs/developer-tools/cli-tools/quill-cli-reference/sns/quill-sns-follow-neuron
- developer-docs/developer-tools/cli-tools/quill-cli-reference/sns/quill-sns-get-sale-participation
- developer-docs/developer-tools/cli-tools/quill-cli-reference/sns/quill-sns-get-swap-refund
- developer-docs/developer-tools/cli-tools/quill-cli-reference/sns/quill-sns-list-deployed-snses
- developer-docs/developer-tools/cli-tools/quill-cli-reference/sns/quill-sns-make-proposal
- developer-docs/developer-tools/cli-tools/quill-cli-reference/sns/quill-sns-make-upgrade-canister-proposal
- developer-docs/developer-tools/cli-tools/quill-cli-reference/sns/quill-sns-neuron-permission
- developer-docs/developer-tools/cli-tools/quill-cli-reference/sns/quill-sns-new-sale-ticket
- developer-docs/developer-tools/cli-tools/quill-cli-reference/sns/quill-sns-pay
- developer-docs/developer-tools/cli-tools/quill-cli-reference/sns/quill-sns-register-vote
- developer-docs/developer-tools/cli-tools/quill-cli-reference/sns/quill-sns-split-neuron
- developer-docs/developer-tools/cli-tools/quill-cli-reference/sns/quill-sns-stake-maturity
- developer-docs/developer-tools/cli-tools/quill-cli-reference/sns/quill-sns-stake-neuron
- developer-docs/developer-tools/cli-tools/quill-cli-reference/sns/quill-sns-status
- developer-docs/developer-tools/cli-tools/quill-cli-reference/sns/quill-sns-transfer
- developer-docs/web-apps/http-compatible-canisters/custom-http-canisters
- developer-docs/web-apps/http-compatible-canisters/serving-json-over-http
- developer-docs/web-apps/http-compatible-canisters/serving-static-assets-over-http
- motoko/main/about-this-guide
- motoko/main/actor-classes
- motoko/main/actors-async
- motoko/main/base-intro
- motoko/main/base/Array
- motoko/main/base/AssocList
- motoko/main/base/Blob
- motoko/main/base/Bool
- motoko/main/base/Buffer
- motoko/main/base/CertifiedData
- motoko/main/base/Char
- motoko/main/base/Debug
- motoko/main/base/Deque
- motoko/main/base/Error
- motoko/main/base/ExperimentalCycles
- motoko/main/base/ExperimentalInternetComputer
- motoko/main/base/ExperimentalStableMemory
- motoko/main/base/Float
- motoko/main/base/Func
- motoko/main/base/Hash
- motoko/main/base/HashMap
- motoko/main/base/Heap
- motoko/main/base/Int
- motoko/main/base/Int16
- motoko/main/base/Int32
- motoko/main/base/Int64
- motoko/main/base/Int8
- motoko/main/base/Iter
- motoko/main/base/IterType
- motoko/main/base/List
- motoko/main/base/Nat
- motoko/main/base/Nat16
- motoko/main/base/Nat32
- motoko/main/base/Nat64
- motoko/main/base/Nat8
- motoko/main/base/Option
- motoko/main/base/Order
- motoko/main/base/Prelude
- motoko/main/base/Principal
- motoko/main/base/RBTree
- motoko/main/base/Random
- motoko/main/base/Region
- motoko/main/base/Result
- motoko/main/base/Stack
- motoko/main/base/Text
- motoko/main/base/Time
- motoko/main/base/Timer
- motoko/main/base/Trie
- motoko/main/base/TrieMap
- motoko/main/base/TrieSet
- motoko/main/base/index
- motoko/main/basic-concepts
- motoko/main/caller-id
- motoko/main/compatibility
- motoko/main/compiler-ref
- motoko/main/control-flow
- motoko/main/cycles
- motoko/main/errors
- motoko/main/heartbeats
- motoko/main/language-manual
- motoko/main/local-objects-classes
- motoko/main/message-inspection
- motoko/main/modules-and-imports
- motoko/main/motoko
- motoko/main/motoko-grammar
- motoko/main/mutable-state
- motoko/main/overview
- motoko/main/pattern-matching
- motoko/main/sharing
- motoko/main/stable-regions
- motoko/main/stablememory
- motoko/main/structural-equality
- motoko/main/style
- motoko/main/timers
- motoko/main/upgrades
- references/http-gateway-protocol-spec
- references/ic-interface-spec
- references/ii-spec
- references/samples/hosting/godot-html5-template/README
- references/samples/hosting/photo-storage/README
- references/samples/hosting/static-website/README
- references/samples/hosting/unity-webgl-template/README
- references/samples/motoko/actor_reference/README
- references/samples/motoko/auth_client_demo/README
- references/samples/motoko/basic_bitcoin/README
- references/samples/motoko/basic_dao/README
- references/samples/motoko/calc/README
- references/samples/motoko/cert-var/README
- references/samples/motoko/classes/README
- references/samples/motoko/composite_query/README
- references/samples/motoko/counter/README
- references/samples/motoko/defi/README
- references/samples/motoko/dip721-nft-container/README
- references/samples/motoko/echo/README
- references/samples/motoko/encrypted-notes-dapp-vetkd/README
- references/samples/motoko/encrypted-notes-dapp/README
- references/samples/motoko/factorial/README
- references/samples/motoko/hello_cycles/README
- references/samples/motoko/http_counter/README
- references/samples/motoko/ic-pos/README
- references/samples/motoko/icrc2-swap/README
- references/samples/motoko/internet_identity_integration/README
- references/samples/motoko/invoice-canister/README
- references/samples/motoko/ios-notifications/README
- references/samples/motoko/ledger-transfer/README
- references/samples/motoko/life/README
- references/samples/motoko/minimal-counter-dapp/README
- references/samples/motoko/persistent-storage/README
- references/samples/motoko/phone-book/README
- references/samples/motoko/pub-sub/README
- references/samples/motoko/quicksort/README
- references/samples/motoko/random_maze/README
- references/samples/motoko/send_http_get/README
- references/samples/motoko/send_http_post/README
- references/samples/motoko/simple-to-do/README
- references/samples/motoko/superheroes/README
- references/samples/motoko/threshold-ecdsa/README
- references/samples/motoko/vetkd/README
- references/samples/motoko/whoami/README
- references/samples/rust/basic_bitcoin/README
- references/samples/rust/basic_dao/README
- references/samples/rust/canister-info/README
- references/samples/rust/composite_query/README
- references/samples/rust/counter/README
- references/samples/rust/defi/src/frontend/README
- references/samples/rust/dip721-nft-container/README
- references/samples/rust/encrypted-notes-dapp-vetkd/README
- references/samples/rust/encrypted-notes-dapp/README
- references/samples/rust/nft-wallet/README
- references/samples/rust/performance_counters/README
- references/samples/rust/periodic_tasks/README
- references/samples/rust/pub-sub/README
- references/samples/rust/qrcode/README
- references/samples/rust/send_http_get/README
- references/samples/rust/send_http_post/README
- references/samples/rust/threshold-ecdsa/README
- references/samples/rust/tokens_transfer/README
- references/samples/rust/vetkd/README

Available document ids are:
- concepts/canisters-code
- concepts/glossary
- concepts/governance
- concepts/nodes-subnets
- concepts/subnet-types
- concepts/tokens-cycles
- concepts/trust-in-canisters
- developer-docs/backend/motoko/0.11.0-migration-guide
- developer-docs/backend/motoko/access-control
- developer-docs/backend/motoko/at-a-glance
- developer-docs/backend/motoko/calculator
- developer-docs/backend/motoko/candid-ui
- developer-docs/backend/motoko/counter-tutorial
- developer-docs/backend/motoko/define-an-actor
- developer-docs/backend/motoko/deploying
- developer-docs/backend/motoko/dev-env
- developer-docs/backend/motoko/explore-templates
- developer-docs/backend/motoko/hello-location
- developer-docs/backend/motoko/index
- developer-docs/backend/motoko/infrastructure
- developer-docs/backend/motoko/intercanister-calls
- developer-docs/backend/motoko/mo-doc
- developer-docs/backend/motoko/multiple-actors
- developer-docs/backend/motoko/optimizing
- developer-docs/backend/motoko/phonebook
- developer-docs/backend/motoko/sample-apps
- developer-docs/backend/motoko/scalability-cancan
- developer-docs/backend/motoko/simple-cycles
- developer-docs/backend/motoko/upgrading
- developer-docs/backend/python/index
- developer-docs/backend/rust/access-control
- developer-docs/backend/rust/candid
- developer-docs/backend/rust/counter
- developer-docs/backend/rust/deploying
- developer-docs/backend/rust/dev-env
- developer-docs/backend/rust/generating-candid
- developer-docs/backend/rust/index
- developer-docs/backend/rust/infrastructure
- developer-docs/backend/rust/intercanister
- developer-docs/backend/rust/optimizing
- developer-docs/backend/rust/project-organization
- developer-docs/backend/rust/quickstart
- developer-docs/backend/rust/samples
- developer-docs/backend/rust/searching-records
- developer-docs/backend/rust/stable-structures
- developer-docs/backend/rust/timers
- developer-docs/backend/rust/upgrading
- developer-docs/backend/solidity/index
- developer-docs/backend/typescript/index
- developer-docs/cost-estimations-and-examples
- developer-docs/daos/nns/neurons-fund
- developer-docs/daos/nns/nns-app-quickstart
- developer-docs/daos/nns/overview
- developer-docs/daos/nns/proposal-requirements
- developer-docs/daos/nns/staking-voting-rewards
- developer-docs/daos/overview
- developer-docs/daos/sns/index
- developer-docs/daos/sns/integrating/frontend-integration
- developer-docs/daos/sns/integrating/index
- developer-docs/daos/sns/integrating/index-integration
- developer-docs/daos/sns/integrating/ledger-integration
- developer-docs/daos/sns/introduction/dao-alternatives
- developer-docs/daos/sns/introduction/sns-architecture
- developer-docs/daos/sns/introduction/sns-intro-high-level
- developer-docs/daos/sns/introduction/sns-launch
- developer-docs/daos/sns/launching/index
- developer-docs/daos/sns/launching/launch-steps-1proposal
- developer-docs/daos/sns/launching/launch-summary-1proposal
- developer-docs/daos/sns/managing/cycles-usage
- developer-docs/daos/sns/managing/making-proposals
- developer-docs/daos/sns/managing/manage-sns-intro
- developer-docs/daos/sns/managing/managing-nervous-system-parameters
- developer-docs/daos/sns/managing/sns-asset-canister
- developer-docs/daos/sns/testing/testing-before-launch
- developer-docs/daos/sns/testing/testing-locally
- developer-docs/daos/sns/testing/testing-on-mainnet
- developer-docs/daos/sns/tokenomics/index
- developer-docs/daos/sns/tokenomics/predeployment-considerations
- developer-docs/daos/sns/tokenomics/preparation
- developer-docs/daos/sns/tokenomics/rewards
- developer-docs/daos/sns/tokenomics/sns-checklist
- developer-docs/daos/sns/tokenomics/tokenomics-intro
- developer-docs/defi/asset-custody/custody-options
- developer-docs/defi/asset-custody/self-custody-quickstart
- developer-docs/defi/exchange-rate-canister
- developer-docs/defi/icp-tokens/account-trimming
- developer-docs/defi/icp-tokens/icp-index-local-setup
- developer-docs/defi/icp-tokens/ledger-local-setup
- developer-docs/defi/icp-tokens/overview
- developer-docs/defi/icp-tokens/using-the-ledger
- developer-docs/defi/icrc-1/icrc1-index-setup
- developer-docs/defi/icrc-1/icrc1-ledger-setup
- developer-docs/defi/icrc-1/using-icrc1-ledger
- developer-docs/defi/nfts/considerations-for-nft-devs
- developer-docs/defi/overview
- developer-docs/defi/rosetta/hotkeys
- developer-docs/defi/rosetta/neuron-lifecycle
- developer-docs/defi/rosetta/overview
- developer-docs/defi/rosetta/staking-support
- developer-docs/defi/rosetta/staking-tutorial
- developer-docs/defi/rosetta/transfers
- developer-docs/developer-tools/cli-tools/advanced-dfx/dfx-migration
- developer-docs/developer-tools/cli-tools/advanced-dfx/networks-json
- developer-docs/developer-tools/cli-tools/advanced-dfx/specifying-replica-version
- developer-docs/developer-tools/cli-tools/dfx-json-reference
- developer-docs/developer-tools/cli-tools/ic-admin
- developer-docs/developer-tools/dev-tools-overview
- developer-docs/developer-tools/ide/gitpod
- developer-docs/developer-tools/ide/playground
- developer-docs/developer-tools/ide/vs-code
- developer-docs/developer-tools/off-chain/agents/javascript-agent
- developer-docs/developer-tools/off-chain/agents/nodejs
- developer-docs/developer-tools/off-chain/agents/overview
- developer-docs/developer-tools/off-chain/agents/rust-agent
- developer-docs/developer-tools/on-chain/cdks
- developer-docs/gas-cost
- developer-docs/getting-started/accounts
- developer-docs/getting-started/cycles/converting_icp_tokens_into_cycles
- developer-docs/getting-started/cycles/cycles-faucet
- developer-docs/getting-started/cycles/cycles-wallet
- developer-docs/getting-started/default-template
- developer-docs/getting-started/deploy/local
- developer-docs/getting-started/deploy/mainnet
- developer-docs/getting-started/development-workflow
- developer-docs/getting-started/hello-world
- developer-docs/getting-started/install/index
- developer-docs/getting-started/install/windows-wsl
- developer-docs/getting-started/overview-of-icp
- developer-docs/getting-started/quickstart/react-quickstart
- developer-docs/multi-chain/bitcoin/ckbtc
- developer-docs/multi-chain/bitcoin/local-development
- developer-docs/multi-chain/bitcoin/overview
- developer-docs/multi-chain/bitcoin/read-state
- developer-docs/multi-chain/bitcoin/submit-transactions
- developer-docs/multi-chain/ethereum/cketh
- developer-docs/multi-chain/ethereum/evm-rpc
- developer-docs/multi-chain/ethereum/overview
- developer-docs/multi-chain/ethereum/siwe
- developer-docs/multi-chain/faq/ckbtc-faq
- developer-docs/multi-chain/faq/ckerc20-faq
- developer-docs/multi-chain/faq/cketh-faq
- developer-docs/multi-chain/faq/signatures-faq
- developer-docs/multi-chain/faq/user-faq
- developer-docs/security/formal-verification
- developer-docs/security/general-security-best-practices
- developer-docs/security/rust-canister-development-security-best-practices
- developer-docs/security/web-app-development-security-best-practices
- developer-docs/smart-contracts/advanced-features/composite-query
- developer-docs/smart-contracts/advanced-features/handling-get-post-requests
- developer-docs/smart-contracts/advanced-features/https-outcalls/https-outcalls-get
- developer-docs/smart-contracts/advanced-features/https-outcalls/https-outcalls-how-to-use
- developer-docs/smart-contracts/advanced-features/https-outcalls/https-outcalls-overview
- developer-docs/smart-contracts/advanced-features/https-outcalls/https-outcalls-post
- developer-docs/smart-contracts/advanced-features/https-outcalls/making-http-requests
- developer-docs/smart-contracts/advanced-features/management-canister
- developer-docs/smart-contracts/advanced-features/periodic-tasks
- developer-docs/smart-contracts/advanced-features/serving-http-request
- developer-docs/smart-contracts/advanced-features/system-canisters
- developer-docs/smart-contracts/best-practices/architecture
- developer-docs/smart-contracts/best-practices/general
- developer-docs/smart-contracts/best-practices/storage
- developer-docs/smart-contracts/best-practices/troubleshooting
- developer-docs/smart-contracts/build/overview
- developer-docs/smart-contracts/call/arguments
- developer-docs/smart-contracts/call/overview
- developer-docs/smart-contracts/candid/candid-concepts
- developer-docs/smart-contracts/candid/candid-howto
- developer-docs/smart-contracts/candid/index
- developer-docs/smart-contracts/deploy/larger-wasm
- developer-docs/smart-contracts/deploy/overview
- developer-docs/smart-contracts/deploy/sharing
- developer-docs/smart-contracts/encryption/signing-transactions
- developer-docs/smart-contracts/encryption/t-ecdsa
- developer-docs/smart-contracts/encryption/using-vetkeys
- developer-docs/smart-contracts/encryption/vetkeys
- developer-docs/smart-contracts/maintain/control
- developer-docs/smart-contracts/maintain/delete
- developer-docs/smart-contracts/maintain/history
- developer-docs/smart-contracts/maintain/import
- developer-docs/smart-contracts/maintain/recovery
- developer-docs/smart-contracts/maintain/resource-limits
- developer-docs/smart-contracts/maintain/settings
- developer-docs/smart-contracts/maintain/state
- developer-docs/smart-contracts/maintain/storage
- developer-docs/smart-contracts/maintain/upgrade
- developer-docs/smart-contracts/overview/canister-lifecycle
- developer-docs/smart-contracts/overview/inside-canisters
- developer-docs/smart-contracts/overview/introduction
- developer-docs/smart-contracts/test/pocket-ic
- developer-docs/smart-contracts/test/reproducible-builds
- developer-docs/smart-contracts/test/staging-environment
- developer-docs/smart-contracts/test/troubleshooting
- developer-docs/smart-contracts/topping-up/cycles_management_services
- developer-docs/smart-contracts/topping-up/topping-up-canister
- developer-docs/smart-contracts/write/choosing-language
- developer-docs/web-apps/application-frontends/add-stylesheet
- developer-docs/web-apps/application-frontends/custom-frontend
- developer-docs/web-apps/application-frontends/existing-frontend
- developer-docs/web-apps/application-frontends/overview
- developer-docs/web-apps/application-frontends/serving-static-assets
- developer-docs/web-apps/application-frontends/webpack-dev-server
- developer-docs/web-apps/browser-js/js-frameworks
- developer-docs/web-apps/browser-js/js-request-api
- developer-docs/web-apps/custom-domains/dns-setup
- developer-docs/web-apps/custom-domains/using-custom-domains
- developer-docs/web-apps/design-dapps
- developer-docs/web-apps/frameworks/juno
- developer-docs/web-apps/independently-verifying-ic-signatures
- developer-docs/web-apps/user-login/email-password
- developer-docs/web-apps/user-login/internet-identity/alternative-origins
- developer-docs/web-apps/user-login/internet-identity/creating-ii
- developer-docs/web-apps/user-login/internet-identity/integrate-identity
- developer-docs/web-apps/user-login/internet-identity/overview
- developer-docs/web-apps/user-login/nfid
- home
- motoko/tutorial
- motoko/version
- other/updates/index
- other/updates/release-notes/0.10.0-rn
- other/updates/release-notes/0.6.20-rn
- other/updates/release-notes/0.6.21-rn
- other/updates/release-notes/0.6.22-rn
- other/updates/release-notes/0.6.23-rn
- other/updates/release-notes/0.6.24-rn
- other/updates/release-notes/0.6.25-rn
- other/updates/release-notes/0.6.26-rn
- other/updates/release-notes/0.7.0-rn
- other/updates/release-notes/0.7.1-rn
- other/updates/release-notes/0.7.2-rn
- other/updates/release-notes/0.7.7-rn
- other/updates/release-notes/0.8.0-rn
- other/updates/release-notes/0.8.1-rn
- other/updates/release-notes/0.8.2-rn
- other/updates/release-notes/0.8.3-rn
- other/updates/release-notes/0.8.4-rn
- other/updates/release-notes/0.9.0-rn
- other/updates/release-notes/0.9.2-rn
- other/updates/release-notes/0.9.3-rn
- other/updates/release-notes/release-notes
- other/updates/release-notes/sdk-release-notes
- references/asset-canister
- references/bitcoin-how-it-works
- references/candid-ref
- references/ckbtc-reference
- references/clang-supported-languages
- references/https-outcalls-how-it-works
- references/icrc1-standard
- references/id-encoding-spec
- references/ledger
- references/message-execution-properties
- references/t-ecdsa-how-it-works
- references/vetkeys-overview
- samples/overview
- tutorials/developer-journey/index
- tutorials/developer-journey/level-0/dev-env
- tutorials/developer-journey/level-0/ic-overview
- tutorials/developer-journey/level-0/ic-terms
- tutorials/developer-journey/level-0/index
- tutorials/developer-journey/level-0/intro-canisters
- tutorials/developer-journey/level-0/intro-dfx
- tutorials/developer-journey/level-0/intro-languages
- tutorials/developer-journey/level-1/1.1-live-demo
- tutorials/developer-journey/level-1/1.2-motoko-lvl1
- tutorials/developer-journey/level-1/1.3-first-dapp
- tutorials/developer-journey/level-1/1.4-using-cycles
- tutorials/developer-journey/level-1/1.5-deploying-canisters
- tutorials/developer-journey/level-1/1.6-managing-canisters
- tutorials/developer-journey/level-1/index
- tutorials/developer-journey/level-2/2.1-storage-persistence
- tutorials/developer-journey/level-2/2.2-advanced-canister-calls
- tutorials/developer-journey/level-2/2.3-third-party-canisters
- tutorials/developer-journey/level-2/2.4-intro-candid
- tutorials/developer-journey/level-2/2.5-unit-testing
- tutorials/developer-journey/level-2/2.6-motoko-lvl2
- tutorials/developer-journey/level-2/index
- tutorials/developer-journey/level-3/3.1-package-managers
- tutorials/developer-journey/level-3/3.2-https-outcalls
- tutorials/developer-journey/level-3/3.3-certified-data
- tutorials/developer-journey/level-3/3.4-intro-to-agents
- tutorials/developer-journey/level-3/3.5-identities-and-auth
- tutorials/developer-journey/level-3/3.6-motoko-lvl3
- tutorials/developer-journey/level-3/index
- tutorials/developer-journey/level-4/4.1-icp-ledger
- tutorials/developer-journey/level-4/4.2-icrc-tokens
- tutorials/developer-journey/level-4/4.3-ckbtc-and-bitcoin
- tutorials/developer-journey/level-4/4.4-nns-governance
- tutorials/developer-journey/level-4/4.5-using-quill
- tutorials/developer-journey/level-4/4.6-motoko-lvl4
- tutorials/developer-journey/level-4/index
- tutorials/developer-journey/level-5/5.1-vetKeys-tutorial
- tutorials/developer-journey/level-5/5.2-ICP-ETH-tutorial
- tutorials/developer-journey/level-5/5.3-token-swap-tutorial
- tutorials/developer-journey/level-5/5.4-NFT-tutorial
- tutorials/developer-journey/level-5/5.5-auction-tutorial
- tutorials/developer-journey/level-5/5.6-next-steps
- tutorials/developer-journey/level-5/index
- tutorials/hackathon-prep-course/authentication
- tutorials/hackathon-prep-course/deploying-first-fullstack-dapp
- tutorials/hackathon-prep-course/exploring-the-backend
- tutorials/hackathon-prep-course/exploring-the-frontend
- tutorials/hackathon-prep-course/index
- tutorials/hackathon-prep-course/integrating-with-tokens
- tutorials/hackathon-prep-course/managing-canisters
- tutorials/hackathon-prep-course/obtaining-cycles
- tutorials/hackathon-prep-course/resources
- tutorials/hackathon-prep-course/sample-starter-projects
- tutorials/hackathon-prep-course/what-is-icp
    at Object.checkSidebarsDocIds (/Users/daviddalbusco/projects/lab/portal/node_modules/@docusaurus/plugin-content-docs/lib/sidebars/utils.js:181:19)
    at addDocNavigation (/Users/daviddalbusco/projects/lab/portal/node_modules/@docusaurus/plugin-content-docs/lib/docs.js:206:19)
    at doLoadVersion (/Users/daviddalbusco/projects/lab/portal/node_modules/@docusaurus/plugin-content-docs/lib/index.js:106:55)
    at async loadVersion (/Users/daviddalbusco/projects/lab/portal/node_modules/@docusaurus/plugin-content-docs/lib/index.js:113:28)
    at async Promise.all (index 0)
    at async Object.loadContent (/Users/daviddalbusco/projects/lab/portal/node_modules/@docusaurus/plugin-content-docs/lib/index.js:121:33)
    at async /Users/daviddalbusco/projects/lab/portal/node_modules/@docusaurus/core/lib/server/plugins/index.js:35:25
    at async Promise.all (index 0)
    at async loadPlugins (/Users/daviddalbusco/projects/lab/portal/node_modules/@docusaurus/core/lib/server/plugins/index.js:34:27)
    at async load (/Users/daviddalbusco/projects/lab/portal/node_modules/@docusaurus/core/lib/server/index.js:76:58)
[INFO] Docusaurus version: 2.4.3
Node version: v18.16.0

Hey @peterpeterparker,
There are many sources that are pulled in as submodules. Please try following the instructions in the readme:
cd portal/
git submodule update --init
npm install
npm start

https://github.com/dfinity/portal?tab=readme-ov-file#install-and-run-locally

git submodule update --init resolved it. thx.
Not sure why you don't setup an npm prepare script that would resolve this automatically.


Sipmask:mmdetection CUDA out of memory error

Hi,when training with the original code,I got RuntimeError as below:
pred_masks = torch.stack([pos_masks00, pos_masks01, pos_masks10, pos_masks11], dim=0)
RuntimeError: CUDA out of memory. Tried to allocate 464.00 MiB (GPU 1; 10.76 GiB total capacity; 7.33 GiB already alloca
ted; 97.19 MiB free; 1.19 GiB cached)

There was no one using GPU when I trained it. First I thought it might be a batchsize issue. But even though I changed the batch size from 16 to 1,the same error still occured .The only difference between batchsize 16 and batchsize 1 is ,when changed to batchsize 1,the training was able to run for half epoch,then the error occurred.
I wonder if the code didn't clear the grad during training .
BTW,my GPU is  GeForce RTX 2080 Ti ,11019M.During training I used 2 GPUs.
My environment is
pytorch = 1.1.0 torchvision = 0.3.0 mmcv = 0.4.3
Please tell me how to deal with it.Thanks a lot!

Generally, it may need some more memory if for image instance segmentation. If you want to reduce the memory, maybe you can try use 2x upsampling about the basis mask.

Generally, it may need some more memory if for image instance segmentation. If you want to reduce the memory, maybe you can try use 2x upsampling about the basis mask.

@JialeCao001 I see.Thanks for your reply!I noticed that you used 8GPUs during training.Could you tell me what the memory size of per GPU?

@JialeCao001 I see.Thanks for your reply!I noticed that you used 8GPUs during training.Could you tell me what the memory size of per GPU?

I remember about maybe 20G per GPU.

I remember about maybe 20G per GPU.

I remember about maybe 20G per GPU. If we limit the number of proposals for mask prediction per GPU, it maybe less than 20G.

Thank you very much for your prompt reply!It really helps me a lot.

I remember about maybe 20G per GPU. If we limit the number of proposals for mask prediction per GPU, it maybe less than 20G.

Thank you very much for your prompt reply!It really helps me a lot.


Pentadactyl vs Waterfox

Waterfox is an open-source web browser based on Mozilla Firefox for 64-bit Windows, macOS and Linux systems. What is important for us, Pentadactyl users, it's that Waterfox team plans to continue supporting XUL.
However, as of current version, Pentadactyl  doesn't seem to function properly with the latest Waterfox 54.0: it installs fine (I used this signed version) but then just nothing happens. Same version, however, is working perfectly with Firefox ESR 45.9.0.
Any ideas?

(partially?) solved in #209

Thanks, that seems to work!


Add my awesome dynamic profile.

What type of PR is this? (check all applicable)
https://github.com/akshitagupta15june/akshitagupta15june
This profile comes under dynamic category have a look.

[x] 🚀 Added Name -done
[x] ✨ Feature - dynamic features
[ ] ✅ Joined Community -want to join this community
[ ] 🌟 ed the repo
[x] 🐛 Grammatical Error
[x] 📝 Documentation Update
[x] 🚩 Other

Description
My profile comes under dynamic category have a look.
Add Link of GitHub Profile
https://github.com/akshitagupta15june/akshitagupta15june

Check my readme profile

@abhisheknaiidu

@Lakshrp112 thanks for submitting my profile


[YOUTUBEJS][Player]: Failed to extract signature decipher algorithm.

Steps to reproduce
I am currently getting the following error:
[YOUTUBEJS][Player]: Failed to extract signature decipher algorithm.
YouTube, based on YT-DLP and other projects, has updated the signature extraction process. I believe the current signature extraction method is outdated, which is causing this issue.
Failure Logs
[YOUTUBEJS][Player]: Failed to extract signature decipher algorithm.

Expected behavior
actually extract it
Current behavior
not extracting it
Version
Default
Anything else?
No response
Checklist

[X] I am running the latest version.
[X] I checked the documentation and found no answer.
[X] I have searched the existing issues and made sure this is not a duplicate.
[X] I have provided sufficient information.

Same issue

Same issue

same issue

if (typeof uwg === "undefined")
    return J;

The nsig algorithm needs to be handled here, otherwise it will return the same value as the argument

if (typeof uwg === "undefined")
    return J;

The nsig algorithm needs to be handled here, otherwise it will return the same value as the argument

Jinter does not handle undefined vars the same way browsers and other JS engines do (I didn't bother implementing it the proper way). So we don't have to do anything about that because typeof uwg === "undefined"  will always return false. In Jinter, uwg is literally "uwg", if that makes any sense.


npm tasks

This supersedes #248
/cc @gaearon

How does making a Github release fit into this workflow? Should I just do a release via web interface separately based on the pushed tag?

When you do a release, a github tag is created. Then you need to manually create the release note for that existing tag (but that's always a manual process).
Or do you mean something else?

Yeah this seems right.
Some tools also automate creating release notes so I just wanted to clarify.
This looks great to me.

Cool :+1:
One thing though to remember: the patch/minor/major tasks work for normal semver numbers, so normal lifecycle releases.
If you want to release alpha/beta/-rc/whatever you should directly use the mversion cli (see examples), or do it manually, just to be sure.

Oh, okay, thanks for explaining.

@gaearon ok, I made the changes and force pushed. Should be ok now.

@gaearon feel free to do the final tweaks the way you like it ;)

Sure, thanks! I'll actually use some of these for a boilerplate I'm preparing. (Tired of doing the same setup for every lib.)

Tired of doing the same setup for every lib

I know! :)
PS: Glad to help.

Thanks again! I'll merge tomorrow.
In the meantime, I extracted some stuff into https://github.com/gaearon/library-boilerplate

Good idea! Thanks for the link.

Wow this PR clarifies the build process a lot and makes it easier to start hacking on redux. :+1:

(Window compatibility)
npm tasks that set environment variables for Node, it requires a slight change.
For example (from/to):
"build:umd": "webpack src/index.js dist/redux.js && NODE_ENV=production webpack src/index.js dist/redux.min.js"

"build:umd": "webpack src/index.js dist/redux.js && set NODE_ENV=production&& webpack src/index.js dist/redux.min.js"

I mentioned it in https://github.com/gaearon/library-boilerplate/issues/2.  Should work for Mac as well (I hope) to make it all cross-platform.  The no space after setting variable is the hack discovery that makes it possible in Windows.

@mikekidder This doesn't pass NODE_ENV=production to Webpack for some reason.

I tried to fix Windows build in #379.

Yes, "set" on OS X was questionable, I didn't have a Mac to test.  I'll respond further in #379


Server error 500 on POST

Hi, I am having issues with POST method in my React-Redux app. GET works perfectly fine.

Error in Chrome devtools: POST https://my-json-server.typicode.com/casvil/recipes/recipes 500 (). Uncaught (in promise) SyntaxError: Unexpected token T in JSON at position 0

Error in Postman: TypeError: Cannot read property 'id' of undefined
at Function.createId (/app/node_modules/json-server/lib/server/mixins.js:46:39)
at Function.insert (/app/node_modules/lodash-id/src/index.js:47:49)
at /app/node_modules/lodash/lodash.js:4379:28
at arrayReduce (/app/node_modules/lodash/lodash.js:704:21)
at baseWrapperValue (/app/node_modules/lodash/lodash.js:4378:14)
at LodashWrapper.wrapperValue (/app/node_modules/lodash/lodash.js:9067:14)
at create (/app/node_modules/json-server/lib/server/router/plural.js:226:50)
at Layer.handle [as handle_request] (/app/node_modules/express/lib/router/layer.js:95:5)
at next (/app/node_modules/express/lib/router/route.js:137:13)
at next (/app/node_modules/express/lib/router/route.js:131:14)

This is the fetch request:
export const createRecipe = (recipeData) => dispatch => {
    fetch('https://my-json-server.typicode.com/casvil/recipes/recipes', {
      method: 'POST',
      headers: {
      'Content-Type': 'application/json'
    },
    body: JSON.stringify(recipeData)
  })
    .then(res => res.json())
    .then(recipe => dispatch({
      type: NEW_RECIPE,
      payload: recipe
    }));
}

db.json:
{
  "recipes": [
    {
      "name": "Tortillicas fatas",
      "difficulty": "2/5"
    },
    {
      "name": "Croquetas de pollo",
      "difficulty": "3/5"
    }
  ]
}

If I use instead your Posts json-server, the POST method works fine. https://jsonplaceholder.typicode.com/posts.
Is it possible that my db.json file is wrong, might have any wrong character?
Thanks!

The db.json file needs an "id" property

thank you!!

Thank you

just wanted to clarify here that the ids are auto-assigned on post requests sent to json-server, but any data that you've added to db.json yourself needs to have an id property with an integer value.

I had the same problem, I added an "id" and it worked! thank you! but anyway I don't understand why it needs an "id"

The db.json file needs an "id" property

thank you!

thank you ❤❤❤


Function timeout while calling Js function from python?

When I try calling a javascript function from inside python, I have noticed that if the javascript function takes more than ~10 seconds to execute then value returned to python is None, even though the js functions returns a non-null value (confirmed by printing it in console).
In situations where input size is small, js functions returns correctly to python.
Is there a setting I can change to increase this time limit, if this indeed is the issue?

Hi @RahulBadenkal, sorry for the slow reply.
You're right - we do have a hard-coded limit of about 10 seconds for function execution at the moment. I think it's a fair idea to make this configurable. Although it's a slightly hacky implementation at the moment, it feels relatively easy to unblock you on this (hopefully it's not too late), so I'll go ahead and put a PR up to expose this as configuration for now.

Thanks!