Question:  Controller Content within Tab?

I've been trying to place a controller (say one that's grabbing data from a json url) within a tab, but can't seem to get anything working.  Any ideas?

Like this? Place ng-controller in the corresponding div.
<ion-content scroll="false">
    <ion-slide-box show-pager="false" ion-slide-tabs>
        <ion-slide ion-slide-tab-label="test">

Tab 1

</ion-slide>
        <ion-slide ion-slide-tab-label="secondTest">

Tab 2

</ion-slide>
</ion-content>

Yes. Once I add the controller in a slide-box everything disappears for that tab like it doesn't exist.


Certificate create policy parameter

I find the -p/--policy parameter for az keyvault certificate create a little bit misleading - it suggests, that if I want to load policy from a file, I should use @{file}. You can clearly miss the concept here as initially, you want to use @{my-policy.json} syntax instead of @my-policy.json. Extending the hint would help in proper usage of the command.

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

ID: a9c661d7-bf43-5354-015e-3859f30a42a2
Version Independent ID: fa69e552-5904-ce97-d02c-915c819bdde1
Content: az keyvault certificate
Content Source: src/azure-cli/azure/cli/command_modules/keyvault/_help.py
Service: key-vault
GitHub Login: @rloutlaw
Microsoft Alias: routlaw

Fixed by #9999


[Candidate 4v4 Dominion ZH v1] Units can move through large rocks

Observed behaviour
Units can move through large rocks.
Expected behavior
Units can not move through large rocks. Rocks are impassable or moved out of the way.
Screenshots

fixed (hope didnt miss anything)


Add "name" variable support for tf.einsum

This fix adds "name" variable support for tf.einsum
This fix fixes #11501
Signed-off-by: Yong Tang<EMAIL_ADDRESS>

Can one of the admins verify this patch?

@vrv Thanks for the review. If we use name=None at the end then it will thrown out a syntax error:
  File "/home/ubuntu/.cache/bazel/_bazel_ubuntu/ad1e09741bb4109fbc70ef8216b59ee2/execroot/tensorflow/bazel-out/local-opt/bin/tensorflow/python/special_math_ops_test.runfiles/org_tensorflow/tensorflow/python/ops/special_math_ops.py", line 85
    def einsum(equation, *inputs, name=None):
                                     ^
SyntaxError: invalid syntax

So I used **kwargs to get around it.

@tensorflow-jenkins test this please

Thanks @vrv for the review. The PR has been updated so that all invalid argument keys would be printed in case of error. A test case has been added as well.
I also updated with
   $ bazel-bin/tensorflow/tools/api/tests/api_compatibility_test \
          --update_goldens True

so that api_compatibility_test could pass on Jenkins.
Please take a look and let me know if there are any issues.

Thanks!  This looks good.
I'm not sure if this qualifies as something that needs API review -- presumably it does and it should be fine.
@tensorflow-jenkins test this please

Fine for API review.

@tensorflow-jenkins test this please

@yongtang It looks like you need to fix the expected error message in your test:
Traceback (most recent call last):
File "/var/lib/jenkins/workspace/tensorflow-pull-requests-cpu-python3/bazel-ci_build-cache/.cache/bazel/_bazel_jenkins/eab0d61a99b6696edb3d2aff87b585e8/execroot/workspace/bazel-out/local-py3-opt/bin/bazel_pip/tensorflow/python/special_math_ops_test.runfiles/org_tensorflow/bazel_pip/tensorflow/python/ops/special_math_ops_test.py", line 251, in test_invalid_keyword_arguments
invalid1="value1", invalid2="value2")
AssertionError: "invalid keyword arguments for this function: invalid1, invalid2" does not match "invalid keyword arguments for this function: invalid2, invalid1"

@rmlarsen Thanks for the review. The Jenkins error for was because dict in python is not ordered when iterate through. I have sorted the error message so that the output is repeatable. The PR has been updated now.

@yongtang thanks for the quick fix. Yeah, iterating over and unordered container is asking for trouble :-)
@tensorflow-jenkins test this please


run_sim should be parallelizable

in general, check its utility and whether it might as well be replaced by the script provided by uvsim. The main problem with uvsim is that it doesn't discard the imaginary part.

run_sim now definitely has a reason to exist, but should still make parallelizable


Annotation table section dividers

Description: Table section dividers are added to more easily identify which annotations are ground truth
Tasks:

[x] Add 2 section dividers with count: "# Ground Truth Annotations" and "# Other Annotations"

"#" represents the total count of annotations in that section (not just what's on the page)

[ ] Section overflows onto the next page (when using pagination), count in dividers should remain the same
[x] Applying filters will:

[ ] update the count within the section dividers to reflect
[ ] hide the section divider if there are no results in that section

Link to design: https://www.figma.com/file/gwX2PjfGPfMrbEWMMJq6rW/H1-2024---Annotations-Table-Update?node-id=561%3A162957&mode=dev

Here is a sample query for getting some of the basic information for this page:
query annotation_table_query($run_id: Int) {
  annotations(order_by: {ground_truth_used: desc, deposition_date: desc}, where: {tomogram_voxel_spacing: {run_id: {_eq: $run_id}}}) {
    id
    ground_truth_status
    deposition_date
    files_aggregate(distinct_on: shape_type) {
      nodes {
        shape_type
      }
    }
    confidence_precision
    confidence_recall
    object_name
    authors(order_by: {author_list_order: asc}) {
      author_list_order
      name
      id
      orcid
    }
  }
  ground_truth_count:annotations_aggregate(where: {tomogram_voxel_spacing: {run_id: {_eq: $run_id}}, ground_truth_status: {_eq: true}}) {
    aggregate {
      count(columns: id)
    }
  }
  other_annotation_count:annotations_aggregate(where: {tomogram_voxel_spacing: {run_id: {_eq: $run_id}}, ground_truth_status: {_eq: false}}) {
    aggregate {
      count(columns: id)
    }
  }
}

currently blocked, we need backend support to query the ground truth and non-ground truth annotation counts cc: @manasaV3

@manasaV3 Jeremy mentioned there's a backend ticket for this, could you help link when you have a chance?

@codemonkey800  and @junxini I believe the query above should help us get the annotation counts by ground_truth_status. If this is related to distinct count by annotation shapes: https://github.com/chanzuckerberg/cryoet-data-portal/issues/582

This work is now unblocked by this interim solution: https://github.com/chanzuckerberg/cryoet-data-portal/issues/582#issuecomment-2251260752

@Janeece @junxini Here's a run that doesn't have a ground truth annotation: https://frontend.cryoet.staging.si.czi.technology/runs/8413
For runs that have only either ground truth or non-ground truth annotations, should we still display the single divider?

For runs that have only either ground truth or non-ground truth annotations, should we still display the single divider?

good question. i think the majority of runs won't have ground truth annotations. it might not be intuitive for users to see a banner that says "Other annotations" in that context. maybe remove the dividers if the run only has non-ground truths or if it only has ground truths? @Janeece what do you think?

@bchu1 I sycned with @junxini and @kandarpksk and we decided that keeping dividers would be clearest for the user.

If a section is empty, show divider, count is 0
Behavior change: if use applies a filter that causes section to be empty, show divider & count is 0

Design mockup of updated behavior: https://www.figma.com/design/Kl03vJ6BID3ztPb8B0fsel?node-id=1-6108&m=dev#889949041

Copying over from Slack:

Janeece Pourroy
10:54 AM
The dividers always show IF if the section is on the page. So if ground truth ends on page 2…
Page 1: only ground truth  divider shows, "other" doesnt start until page 2
Page 2: both dividers now because both sections are on the page
Page 3: only "other" divider shows, "ground truth" ended on page 2
Examples are on page 1.4 thru 1.6


Set Content Type (mime code) for csv files

Describe the feature
When I upload .csv files using this client, the mime code is not inferred from the file extension and defaulting to application/octet-stream. I see a long list of file types in AmazonS3Util.cs class, but not for a common file type like .csv. Is there a reason why is the mime code text/csv or application/csv not inferred? Any of them would be much better than just defaulting to application/octet-stream.
Use Case
As a developer I want to have text/csv content type inferred by the sdk from extension, so I don't need to write workaround code to infer the content type in end users code, when it defaults to application/octet-stream.
Proposed Solution
Simply add a line  { ".csv", "text/csv" }, in the extensionToMime dictionary initialization.
Other Information
No response
Acknowledgements

[x] I may be able to implement this feature request
[ ] This feature might incur a breaking change

AWS .NET SDK and/or Package version used
Latest
Targeted .NET Platform
.NET 7
Operating System and version
Windows 11

Hi @stoilovkr,
Thank you for submitting this feature request. I understand how the automatic detection of the text/csv MIME type would improve the developer experience when uploading CSV files.
Will discuss this with the team to take it forward accordingly.
Regards,
Chaitanya

@stoilovkr Thanks for submitting feature request. We will discuss it with the team to get it prioritized. Feel free to contribute PR for the change.

@stoilovkr This change was released and you can find it in S3 v3.7.306


Add object access

Took me a couple of Minutes to find it out. Might be useful for the next one. Correct me if I'm wrong
Cheers Nico

Thanks @nicooler - sorry about the lacking documentation, but thank you for the pr


Replace manually written API calls in WebUI with SecHub Java API Client

Replace manually written API calls in WebUI with SecHub Java API Client. The SecHub Java API client was introduced as part of the system testing framework #2092.

Remark:
Inside this issue following was done

status page does now use real server connection
now centralized access via access service (no direct access to webclient possible)
changed structure. For example all parts which are visible on pages are in dedicated sub packages of com.mercedesbenz.sechub.webui.page
some additional i18 parts were added
user credential injection via spring value is now done directly into access service
some refactorings
added SecHub logo to web ui


[FIX] [ANCHOR: BE PYTHON] Add rate-limit to authentication routes and other necessary part.

Description
The authentication routes without rate-limits are open to all kinds of attacks and abuse like:
Brute-Force Attacks:
These attacks involve trying different password combinations repeatedly to gain unauthorized access. Rate limiting can significantly slow down these attempts, making them less effective.
DDoS Attacks:
Distributed Denial of Service (DDoS) attacks aim to overwhelm a system with numerous requests, making it unavailable to legitimate users. Rate limiting can help mitigate the impact of these attacks by preventing excessive traffic.
API Abuse:
Some malicious actors might try to exploit APIs by making excessive requests to gather data or perform unauthorized actions. Rate limiting can prevent such abuse.
Bot Attacks:
Bots can be used to automate login attempts or other malicious activities. Rate limiting can hinder the effectiveness of these bots.
Throttling:
If a system is experiencing high load, rate limiting can help prevent it from being overwhelmed by excessive login requests.
Expected Outcome
When concurrency is used in accessing the resources on the API, it comes to a point where the API slows down, with rate-limiting, the API is expected to block or deny access to this kind of abuse.

<EMAIL_ADDRESS>You are assigned this task

Assign to me


If you paste something into the ip address bar, you can't undo it via Ctrl Z

Also while you are working on the address bar, make it save the last address that was entered. A config var would be fine for this.

This problem is more fit for https://github.com/space-wizards/RobustToolbox/issues/748


make dockerfile multi arch compatible

The goal here was to make allow to build multi arch images.
So I optimized the dockerfile so that the fetch step, loads the dependencies using the host platform and then reuse them for each platform. This will only re-run if you change a Cargo.toml.
Then I removed the target in order to use the target the container is actually running on.
I finally updated the Makefile so that when we hit make push, it builds both platforms and pushes them to the docker hub.
As a side effect, I removed the dependency to openssl that made the build complicated. rustls is enough for what reqwest is doing here.

The git commmit message is way too short  IMNSHO.

The git commmit message is way too short IMNSHO.

I updated the commit message to give more content.

(FWIW: I have no privilege to approve (nor to reject) this merge request.)

The git commmit message is way too short IMNSHO.

I updated the commit message to give more content.

I hope you can do better.

The git commmit message is way too short IMNSHO.

I updated the commit message to give more content.

I hope you can do better.

Could you please elaborate? What do you expect in that commit message?

Feel free to suggest a better one, I'm open to suggestions.

While preparing advise on git commit message I stumbled upon missing docker buildx on my system
$ docker buildx
docker: 'buildx' is not a docker command.
See 'docker --help'
stappers@paddy:~
$ docker help build | wc
     44     252    2463
stappers@paddy:~
$ docker help buildx | wc
unknown help topic: buildx
      0       0       0
stappers@paddy:~
$ docker version
Client:
 Version:           20.10.25+dfsg1
 API version:       1.41
 Go version:        go1.21.5
 Git commit:        b82b9f3
 Built:             Mon Jan  8 00:09:17 2024
 OS/Arch:           linux/amd64
 Context:           default
 Experimental:      true

Server:
 Engine:
  Version:          20.10.25+dfsg1
  API version:      1.41 (minimum version 1.12)
  Go version:       go1.21.5
  Git commit:       5df983c
  Built:            Mon Jan  8 00:09:17 2024
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.6.24~ds1
  GitCommit:        1.6.24~ds1-1
 runc:
  Version:          1.1.10+ds1
  GitCommit:        1.1.10+ds1-1
 docker-init:
  Version:          0.19.0
  GitCommit:
stappers@paddy:~
$

We will see how much "for me works docker buildx" reports there will be.

While preparing advise on git commit message I stumbled upon missing docker buildx on my system

Just FYI, the current version of docker is 26.0.2. And it's now shipped with docker buildx by default.
You might want to update your installation.

For understanding what good commit messages are, I do recomment
to lurk on Linux kernel mailinglists e.g. Rust-for-Linux.
Find examples of good commit messages at https://github.com/ipxe/ipxe/commits
click on various three dots, ..., button.  The "mouse-over" on the button
says "Show description for SHORT_COMMIT_HASH".
Now an attempt for this merge request:
Added docker multi arch support and some optimize
Huge rewrite of Dockerfile. There are now three build steps

vendor
builder
"copy"
This brings .... as benefit.
It requires a docker version that has buildx support.

I changed the Makefile and Cargo.toml because I can.


Only working with "react-scripts": "2.1.8"

Node is up2Date, @v14.5.0. I tried to delede the node modules and the package-lock.js file, and run node install.
Better Explanation
This worked finally: StackOverflow
Defaulted, the installation will be with the newest package, but this gives this error:
C:\Users\*\Dokumente\NetBeansProjects\helloreact>npm start

><EMAIL_ADDRESS>start C:\Users\*\Dokumente\NetBeansProjects\helloreact
> react-scripts start

i ｢wds｣: Project is running at http://<IP_ADDRESS>:3000/
i ｢wds｣: webpack output is served from
i ｢wds｣: Content not from webpack is served from C:\Users\*\Dokumente\NetBeansProjects\helloreact\public
i ｢wds｣: 404s will fallback to /
Starting the development server...

events.js:291
      throw er; // Unhandled 'error' event
      ^

Error: spawn powershell ENOENT
    at Process.ChildProcess._handle.onexit (internal/child_process.js:268:19)
    at onErrorNT (internal/child_process.js:468:16)
    at processTicksAndRejections (internal/process/task_queues.js:80:21)
Emitted 'error' event on ChildProcess instance at:
    at Process.ChildProcess._handle.onexit (internal/child_process.js:274:12)
    at onErrorNT (internal/child_process.js:468:16)
    at processTicksAndRejections (internal/process/task_queues.js:80:21) {
  errno: -4058,
  code: 'ENOENT',
  syscall: 'spawn powershell',
  path: 'powershell',
  spawnargs: [
    '-NoProfile',
    '-NonInteractive',
    '–ExecutionPolicy',
    'Bypass',
    '-EncodedCommand',
    'UwB0AGEAcgB0ACAAIgBgACIAaAB0AHQAcAA6AC8ALwBsAG8AYwBhAGwAaABvAHMAdAA6ADMAMAAwADAAYAAiACIA'
  ]
}
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>start: `react-scripts start`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!      C:\Users\*\AppData\Roaming\npm-cache\_logs\2020-08-31T19_07_56_878Z-debug.log

2020-08-31T19_07_56_878Z-debug.log

Duplicate of https://github.com/facebook/create-react-app/issues/9527


Fix MetricsUploader

SetupConnection has one argument - string that will be used as suffix in
the metrics_uploader_client log file.
Removed FreeLibrary call that leads to crash.

Thank you Irina. I left some comments. :-)

Thank you for taking a look! I've updated the code


Updates for GHC 8.

Sorry for taking so long.
I made the changes conditional on the TH-version so it works on older versions.
Thanks for the patch!


Babylon Toolkit For Unity

Babylon Toolkit Unity Exporter Playground Update

Please make sure to label your PR with "bug", "new feature" or "breaking change" label(s).
To prevent this PR from going to the changelog marked it with the "skip changelog" label.

It wont let me click Labels in the right sidebar

Snapshot stored with reference name:
refs/pull/14738/merge
Test environment:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/14738/merge/index.html
To test a playground add it to the URL, for example:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/14738/merge/index.html#WGZLGJ#4600
Links to test babylon tools with this snapshot:
https://playground.babylonjs.com/?snapshot=refs/pull/14738/merge
https://sandbox.babylonjs.com/?snapshot=refs/pull/14738/merge
https://gui.babylonjs.com/?snapshot=refs/pull/14738/merge
https://nme.babylonjs.com/?snapshot=refs/pull/14738/merge
To test the snapshot in the playground with a playground ID add it after the snapshot query string:
https://playground.babylonjs.com/?snapshot=refs/pull/14738/merge#BCU1XR#0


Using defaults for unresolved environment variables result in not resolving the whole value

Another point here in 1.0.1:
Given the following YAML:
xxx: !ENV ${DATABASE_HOST:def}

The resulting dictionary from parse_config is always
{'xxx': '${DATABASE_HOST:def}'}

regardless whether the environment variable $DATABASE_HOST is set or not.
This is caused by the default value.
If changing the YAML to:
xxx: !ENV ${DATABASE_HOST}

and setting $DATABASE_HOST to abc resolving works:
{'xxx': 'abc'}

Couldn't this be caused by not escaping braceleft and braceright in the regular expression for the implicit resolver?
    pattern = re.compile(f'.*?\${{(\w+){default_sep_pattern}}}.*?')

->
    pattern = re.compile(f'.*?\$\{{(\w+){default_sep_pattern}}\}.*?')

I found the actual reason: I had to add the optional
config_iterable = parse_config('config.yml', default_sep=':')

I did not notice that this is mentioned in the documentation.
In this case - sorry, my fault.

Ah, I thought this might get a bit lost in the documentation, will make it more clear, thanks! 👍

Ah, I thought this might get a bit lost in the documentation, will make it more clear, thanks!

You mentioned it there, but it is not obvious for fast readers like me :-)
From my point of view I would make it a default, ':' or '|', instead of None, and document it in that way.
The only disadvantage would be that you have to handle escapes ot that character, if you want to use it in these expressions for a different purpose than as a separator character. This is also the case for the curly braces '{', '}', which might also get an escape handling, to be able to use all characters in default expressions.


HDDS-3607. Lot of warnings at DN startup.

What changes were proposed in this pull request?
The log message which is at WARN level before the PR, is printed for every edit in the raft log since the last snapshot during DataNode startup, as we replay the edits, we don't need to spam with this many warnings, especially as this is part of normal operations. The proposal is to change it to DEBUG level.
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-3607
How was this patch tested?
No tests were done, seems to be too trivial to be wrong :)

/retest

/retest

Hmm... there were an integration test failure that was not related (usual timeout we see in integration tests), I am unsure how to re-initiate testing, but it does not seem to work... :)

/retest

@fapifta Thanks for working on this!
@sodonnel @mukul1987 Thanks for the reviews!


service/resume_shutdown_race_test pass->fail on vm-win-release-arm64

log
This test seems to be evading deflakiness infrastructure as there are multiple similar failures for this test.
/===========================================================================\
| service/resume_shutdown_race_test/dds broke (Pass -> Fail, expected Pass) |
\===========================================================================/

--- Command "vm" (took 375ms):
set DART_CONFIGURATION=ReleaseARM64 & set DART_SUPPRESS_WER=1 & set DART_CRASHPAD_HANDLER=c:\opt\s\w\ir\cache\builder\sdk\out\ReleaseARM64\crashpad_handler.exe & out\ReleaseARM64\dart.exe --pause-isolate-on-exit --enable-vm-service=0 --disable-service-auth-codes -DUSE_DDS=true --sound-null-safety -Dtest_runner.configuration=vm-win-release-arm64 --ignore-unrecognized-flags --packages=C:\opt\s\w\ir\cache\builder\sdk\.dart_tool\package_config.json C:\opt\s\w\ir\cache\builder\sdk\runtime\observatory\tests\service\resume_shutdown_race_test.dart

exit code:
1

stderr:
ProcessException: The system cannot find the file specified.

  Command: C:\opt\s\w\ir\cache\builder\sdk\out\bin\dartaotruntime C:\opt\s\w\ir\cache\builder\sdk\out\ReleaseARM64\dds_aot.dart.snapshot http://<IP_ADDRESS>:63764// localhost 0 true true C:\opt\s\w\ir\cache\builder\sdk\out\ReleaseARM64\devtools false false
#0      _ProcessImpl._start (dart:io-patch/process_patch.dart:402:33)
#1      Process.start (dart:io-patch/process_patch.dart:38:20)
#2      _DebuggingSession.start (package:dartdev/src/commands/run.dart:417:35)
<asynchronous suspension>
#3      RunCommand.run (package:dartdev/src/commands/run.dart:290:14)
<asynchronous suspension>
#4      CommandRunner.runCommand (package:args/command_runner.dart:212:13)
<asynchronous suspension>
#5      DartdevRunner.runCommand (package:dartdev/dartdev.dart:249:18)
<asynchronous suspension>
#6      runDartdev (package:dartdev/dartdev.dart:57:16)
<asynchronous suspension>
#7      main (file:///c:/opt/s/w/ir/cache/builder/sdk/pkg/dartdev/bin/dartdev.dart:11:3)
<asynchronous suspension>

--- Re-run this test:
python3 tools/test.py -n vm-win-release-arm64 service/resume_shutdown_race_test/dds

/===============================================================================\
| service/resume_shutdown_race_test/service broke (Pass -> Fail, expected Pass) |
\===============================================================================/

--- Command "vm" (took 390ms):
set DART_CONFIGURATION=ReleaseARM64 & set DART_SUPPRESS_WER=1 & set DART_CRASHPAD_HANDLER=c:\opt\s\w\ir\cache\builder\sdk\out\ReleaseARM64\crashpad_handler.exe & out\ReleaseARM64\dart.exe --pause-isolate-on-exit --enable-vm-service=0 --disable-service-auth-codes --sound-null-safety -Dtest_runner.configuration=vm-win-release-arm64 --ignore-unrecognized-flags --packages=C:\opt\s\w\ir\cache\builder\sdk\.dart_tool\package_config.json C:\opt\s\w\ir\cache\builder\sdk\runtime\observatory\tests\service\resume_shutdown_race_test.dart

exit code:
1

stderr:
ProcessException: The system cannot find the file specified.

  Command: C:\opt\s\w\ir\cache\builder\sdk\out\bin\dartaotruntime C:\opt\s\w\ir\cache\builder\sdk\out\ReleaseARM64\dds_aot.dart.snapshot http://<IP_ADDRESS>:63763// localhost 0 true true C:\opt\s\w\ir\cache\builder\sdk\out\ReleaseARM64\devtools false false
#0      _ProcessImpl._start (dart:io-patch/process_patch.dart:402:33)
#1      Process.start (dart:io-patch/process_patch.dart:38:20)
#2      _DebuggingSession.start (package:dartdev/src/commands/run.dart:417:35)
<asynchronous suspension>
#3      RunCommand.run (package:dartdev/src/commands/run.dart:290:14)
<asynchronous suspension>
#4      CommandRunner.runCommand (package:args/command_runner.dart:212:13)
<asynchronous suspension>
#5      DartdevRunner.runCommand (package:dartdev/dartdev.dart:249:18)
<asynchronous suspension>
#6      runDartdev (package:dartdev/dartdev.dart:57:16)
<asynchronous suspension>
#7      main (file:///c:/opt/s/w/ir/cache/builder/sdk/pkg/dartdev/bin/dartdev.dart:11:3)
<asynchronous suspension>

--- Re-run this test:
python3 tools/test.py -n vm-win-release-arm64 service/resume_shutdown_race_test/service

cc @bkonyi

Failed again https://dart-ci.appspot.com/log/vm-win-release-arm64/vm-win-release-arm64/1029/service/resume_shutdown_race_test/dds

Fixed by derek's change https://dart-review.googlesource.com/c/sdk/+/342640


Parse  before  in XML config

Parse <Variable> before <Include> so we can use them in the included files.
TODO not sure, this is maybe a breaking change? (we cannot overwrite a var in a main.config)

breaking change = no merge


TextStyle copyWith doesn't work as expected

Related Issue : https://github.com/flutter/flutter/issues/75897
Same with me, where TextStyle ..copyWith() not working on flutter :
Flutter 2.2.1 • channel stable • https://github.com/flutter/flutter.git
Framework • revision 02c026b03c (2 weeks ago) • 2021-05-27 12:24:44 -0700
Engine • revision 0fdb562ac8
Tools • Dart 2.13.1
pubspec.yml
fonts:
    - family: Montserrat
      fonts:
        - asset: assets/fonts/Montserrat-Bold.ttf
        - asset: assets/fonts/Montserrat-Medium.ttf
        - asset: assets/fonts/Montserrat-Regular.ttf
        - asset: assets/fonts/Montserrat-Light.ttf
    - family: Roboto
      fonts:
        - asset: assets/fonts/Roboto/Roboto-Black.ttf
        - asset: assets/fonts/Roboto/Roboto-BlackItalic.ttf
        - asset: assets/fonts/Roboto/Roboto-Bold.ttf
          weight: 700
        - asset: assets/fonts/Roboto/Roboto-BoldItalic.ttf
          weight: 700
          style: italic
        - asset: assets/fonts/Roboto/Roboto-Italic.ttf
          style: italic
        - asset: assets/fonts/Roboto/Roboto-Light.ttf
        - asset: assets/fonts/Roboto/Roboto-LightItalic.ttf
          style: italic
        - asset: assets/fonts/Roboto/Roboto-Medium.ttf
        - asset: assets/fonts/Roboto/Roboto-MediumItalic.ttf
          style: italic
        - asset: assets/fonts/Roboto/Roboto-Regular.ttf
        - asset: assets/fonts/Roboto/Roboto-Thin.ttf
        - asset: assets/fonts/Roboto/Roboto-ThinItalic.ttf
          style: italic

class AppStyle {
  static const standart = TextStyle(
    fontSize: 14,
    fontWeight: FontWeight.w400,
    color: AppColors.textPrimary,
    fontFamily: 'Roboto',
  );
}

How Access?
Text(
            interst.name,
            style: AppStyle.medium
              ..copyWith(
                color: selected ? Colors.white : Color(0xFF0960ac),
              ),
          ),

Note:

No use 3rd library

.copyWith instead of ..copyWith.

@AlexV525 thanks, now working


Ex 65 doesn't build

It fails with this error after the other problems have been solved.
Compiling 065_builtins2.zig...
.\exercises\065_builtins2.zig:56:5: error: unable to evaluate constant expression
    var narcissus: Narcissus = Narcissus{};

@ricardomatias I just ran my checker script against the latest copy of Ziglings using a fresh snapshot of Zig:
$ zig version
0.10.0-dev.3394+1a1b7a3af

Compiling 065_builtins2.zig...
Checking 065_builtins2.zig...
PASSED:
A Narcissus loves all Narcissuses. He has room in his heart for: me myself.

That line 56 looks current.  And it should check your minimum Zig version. Hmmmm... Oh, I think there was an instance where somebody was running a new version of Zig, but an old version of the standard library. Maybe it's something like that?
Could you paste the result of zig env?
Here's mine:
$ zig env
{
 "zig_exe": "/home/dave/zig/zig",
 "lib_dir": "/home/dave/zig/lib",
 "std_dir": "/home/dave/zig/lib/std",
 "global_cache_dir": "/home/dave/.cache/zig",
 "version": "0.10.0-dev.3394+1a1b7a3af"
}

I have encountered same problem. Windows, Zig is 0.10.0-dev.3475+b3d463c9e.
On a side note, I think it uses local zig-cache in repo folder, not global one.
Even fiddling with official @This() example sometimes gives that error, so probably it's language issue
Btw, my understanding that you need to add (self: Narcissus) parameter, but it will complain about self not used, and supressing with _ = self explained only in Ex70. (I just happen to know this from somewhere)

@ratfactor sorry for the late reply.. here it is:
{
 "zig_exe": "C:\\Users\\Ricardo\\scoop\\apps\\zig-dev\\current\\zig.exe",
 "lib_dir": "C:\\Users\\Ricardo\\scoop\\apps\\zig-dev\\current\\lib",
 "std_dir": "C:\\Users\\Ricardo\\scoop\\apps\\zig-dev\\current\\lib\\std",
 "global_cache_dir": "C:\\Users\\Ricardo\\AppData\\Local\\zig",
 "version": "0.10.0-dev.3394+1a1b7a3af"
}

Wild. I do have a Windows desktop here I can test on.

@realgdman Well, a self parameter should not be required to complete this one.  I'm looking for a solution that uses builtins. You can peek at patches/patches/065_builtins2.patch to see what's expected.
Actually, @ricardomatias, this did not occur to me before for some reason, but could you check your answer versus the "official" answer :point_up:? Thanks!
It's possible that what's expected in this exercise is not clear, in which case it may need some fixing to make it more clear!

I just ran into this too 👀 and was stuck for a while.
going back to exercises on methods seem to explain what is going on here 😆

@ratfactor oh I got it, I misunderstand wording about "self parameter" and was fixing declaration instead of call.

Okay everybody, I think I've improved it.  I didn't fully realize how misleading and confusing the hints were on that one until I went in to fix it.  Here it is now:
    // Oh dear, we seem to have done something wrong when calling
    // this function. We called it as a method, which would work
    // if it had a self parameter. But it doesn't. (See above.)
    //
    // The fix for this is very subtle, but it makes a big
    // difference!
    const Type2 = narcissus.fetchTheMostBeautifulType();

I hope it's much clearer now that we want to change the calling site, not the declaration!  Thanks for all the helpful comments on this issue!


bug(Expansion Panel): Expansion Panel is set to closed, but is open and then gets closed being inside the Stepper

Is this a regression?

[ ] Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was
No response
Description
When you have a closed Expansion Panel as part of the Stepper it is open and then gets closed. It should be closed right away.
This only happens when the default animation of the Stepper is enabled.
Reproduction
Steps to reproduce:

Put a closed Expansion Panel into the first step of the Stepper
Keep default animation enabled of Stepper
Reload app mutiple time

Expected Behavior
Expansion Panel should be closed right away.
Actual Behavior
Expansion Panel is open for some milliseconds and then gets closed.
Environment

Angular: 13.2
CDK/Material: 13.2.4
Browser(s): Chrome 98.0.4758.109
Operating System (e.g. Windows, macOS, Ubuntu): macOS Monterey 12.2.1

Hello, we took a look at this and couldn't reproduce. Could you please provide a stackblitz reproduction of the issue?

This should be the same root cause as https://github.com/angular/components/issues/22785.


Feature Request: Render Markdown

Would be nice to render markdown in the description field.

This can be easily achieved by using markdown_to_html feature.
Edit line 142 in SharedProjectTimesheetsBundle/Resources/views/view/timesheet.html.twig:
    <td>{{ record.description | e | nl2br | markdown_to_html }}</td>

Clear and warmup the cache and it should work. Description now renders markdown als html correctly.
Note: Require adding twig/markdown-extra to composer dependencies


refactor(execution): move blockifier_bench.rs from native_blockifier to blockifier

This change is

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 77.39%. Comparing base (e64bf80) to head (e3a4cac).

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1836   +/-   ##
=======================================
  Coverage   77.39%   77.39%
=======================================
  Files          60       60
  Lines        8556     8556
  Branches     8556     8556
=======================================
  Hits         6622     6622
  Misses       1494     1494
  Partials      440      440

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Removed extra ) and unnecessary == true.

The extra ) produces a syntax error.  The == true is just strange.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Cannot sign CLA as the page is blank.


How to use timezone with timestamps(inserted_at, updated_at) columns?

Those fields are supposed to always be UTC.


How to get selected Node data

Hi!
Thanks for your wonderfull library.
I see in src/lib/Node.js that events are emitted when a node is selected.
How would I listen to that event to dynamically display the nodes data object into a Div?
If selectedNodeInfo() is run every time a node gets selected then this would work :
<template>

    <LiquorTree :data="dirTree" :options="treeOptions" ref="tree"/>

{{selected}}

</template>

Hi! Thanks for using the library :)
You can clone the library and run: npm run dev. It will open a browser with examples. Open Basic Usage and there you will see the first example.
Or just use v-model attribute. For your example:
<template>

    <LiquorTree :data="dirTree" :options="treeOptions" ref="tree" v-model="selected" />

{{selected}}

</template>

Thanks that worked! (v-model)
Keep up 👍

Great Library! This is exactly what I needed.
But how can I get the checked state?
The selected object is not updated. (I am loading in browser via CDN)

    {{ selected }}

    <tree
      ref="tree"
      :data="treeData"
      :options="treeOptions"
      v-model="selected"
    />

Hi! Thank for using the library :)
I had some thought about v-model and checkboxes. You can update library and check it out.
Also I've added examples (npm run dev and open Checkboxes page).
For your example:

    {{ treeModel.selected.map(el => el.text) }}

    {{ treeModel.checked.map(el => el.text) }}

    <tree
      ref="tree"
      :data="treeData"
      :options="treeOptions"
      v-model="treeModel"
    />

Legend!  Working now...  thanks!
However I think there is a small issue with selection. Try the following on your demo:

Select parent "Item 2"
Deselect all the children ("Item 2.1", "Item 2.2", etc)

You will see that Item 2 remains in the model although it does not appear to be selected.
And if you do this several times, "Item 2" will be repeated in the model.

Hi! Thank you for the library!
But how can I track blur event on the node, after I was editing its name?

Hi!
this.$refs.tree.$on('node:editing:stop', (node, prevNodeText) => {
  console.log('Stop editing: ' + node.text + ', ' + prevNodeText)
})

How do I get indeterminate nodes too?


Generate finetuned time annotations from kaldi worn alignments

Hello,
When i run activity_alignment.py(Generate finetuned time annotations from kaldi worn alignments), there is something wrong ，The following information is an error message：
ERROR - Chime5 Array Enhancement - Failed after 1 day, 10:27:41!
Traceback (most recent calls WITHOUT Sacred internals):
File "/kaldi/egs/chime6/pb_chime5/pb_chime5/scripts/run.py", line 91, in main
run(_run)
File "/kaldi/egs/chime6/pb_chime5/pb_chime5/scripts/run.py", line 128, in run
audio_dir_exist_ok=True
File "/kaldi/egs/chime6/pb_chime5/pb_chime5/core_chime6.py", line 381, in enhance_session
x_hat = self.enhance_example(ex)
File "/kaldi/egs/chime6/pb_chime5/pb_chime5/core_chime6.py", line 495, in enhance_example
debug=debug,
File "/kaldi/egs/chime6/pb_chime5/pb_chime5/core_chime6.py", line 533, in enhance_observation
masks = self.gss_block(Obs, acitivity_freq, debug=debug)
File "/kaldi/egs/chime6/pb_chime5/pb_chime5/core_chime6.py", line 183, in call
source_activity_mask=source_active_mask[f, ..., :T],
File "/kaldi/egs/chime6/pb_chime5/pb_chime5/pb_bss/pb_bss/distribution/cacgmm.py", line 223, in fit
initialization.shape, affiliation_shape
AssertionError: ((5, 1140), (5, 1165))
Do you know what I should do to solve this problem

Hello,
this error message tells you, that the shape of the initialization is wrong. It should have 1165 frames to match the observation, but has only 1140 frames.
My guess is, that your alignments are calculated on shorter data.
It is not clear, where zeros should be padded (front, end, symmetric, ...).
Can you check, if your worn data has the same length as the array data?


Undefined function

Re,
When creating a new expression with NewEvaluableExpressionWithFunctions, I get a "strange" error message if it contains a call to an undefined function: Cannot transition token types from VARIABLE [foobar] to CLAUSE [40] (the expression here was simply foobar(), which is not defined).
I'm afraid my end users won't understand this message properly. Is it possible to return something like "undefined function foobar"? Or build the expression anyway (like for undefined parameters) so it let me check FUNCTION tokens before calling Evaluate?
Thanks!

It's a bit tricky. The library only decides a token is a FUNCTION if it finds an unquoted string that matches a key in the functions map - it doesn't look ahead to see the parenthesis. So if there's no function given that matches the string, it assumes it's a VARIABLE. It does this because functions are given at parse-time and don't change (it doesn't keep a reference to the map or anything).
I can definitely see a good case for having a specific error message for that case (VARIABLE to CLAUSE grammar), because of how common it might be to typo function names (or assume a function is available that actually isn't).
I'll put together a change for this soon.

Nice, thanks.

Done as of https://github.com/Knetic/govaluate/commit/34df01f34403371daab5d0ac8a0cd2a4c4deb6fe


move GlyphIcon inner Component

move GlyphIcon inner Component because the new coomitWork with while loop.

Sorry, I've fixed this bug. Now it can run well without this PR.


Add MFA(TOTP)

What kind of change does this PR introduce?
MFA via TOTP
What is the current behavior?
We don't have MFA enabled
What is the new behavior?
We will have support for MFA flow.
Additional context
Attempts to partially address #14
TODOs
DB Schema

[x] Add Initial database schema
[x] Decide whether to split factor tables
[x] Validate foreign constraints
[ ]  Add indexes(or defer to later)

Core Endpoints

[x] Add tests for core endpoints
[x] Add core endpoints(Enroll a device, verify, challenge, Unenroll device(requires MFA code passed in))

Admin Endpoints

[ ] Add tests for admin endpoints
[ ] Add admin endpoints

Layer 2FA on top of existing endpoints

[ ] Upgrade tests
[ ] Add 2FA on top on login endpoints
[ ] Add 2FA on top of other associated endpoints

Log
Batch One:

Enable, Disable, generate_backup_codes, enroll (regular user)
Factor model, Backup code model + tests

@J0 btw you can consider making this the "parent" branch and then merging PRs into this one - that way the PRs will be more manageable to read and review :)

@kangmingtay sure, that's a good suggestion -- will go with that. Originally had a supabase/add_mfa_migrations branch and merged that in -- will create a branch and send review when the next core "milestone" comes in

Closing as it's no longer relevant since we're using the mfa branch


Filter out internals by default during ingestion

define a generic config for each service to avoid ingesting internal details (unless they're explicitly included in the generic filters).
Add a flag "exclude system assets"
E.g., information_schema for dbs, _confluent* topics in Kafka, etc.

Snowflake: information_schema, account_usage, organization_usage

@harshach @ayush-shah
It looks like solving this issue is suspended. Can I take over it?

@nakaken-churadata are you planning on contributing here?


[match] import cert key profiles path args

Checklist

[x] I've run bundle exec rspec from the root directory to see all new and existing tests pass
[x] I've followed the fastlane code style and run bundle exec rubocop -a to ensure the code style is valid
[x] I see several green ci/circleci builds in the "All checks have passed" section of my PR (connect CircleCI to GitHub if not)
[x] I've read the Contribution Guidelines
[x] I've updated the documentation if necessary.
[x] I've added or updated relevant unit tests.

Motivation and Context
https://github.com/fastlane/fastlane/discussions/21712
I have a need to manage profiles/certs independently in my match cert/key/profile repo from headless automation. I added some additional config options that lets someone specify paths to certs/keys and profiles rather than having to be prompted for them as well as import them independently from one another.
Description
You can now import certs/keys and profiles independently as well as not be prompted for the paths, but via args, such as the below. Without using any of the new options, the existing behavior works the same (the user gets prompted by the UI). If you are only importing profiles but not certs, the apple connect cert import operations won't occur.
# cert/key only
fastlane match import \
    --import_certificate_file_path /tmp/ccc/ABCD39Z700.cer \
    --import_certificate_private_key_file_path /tmp/ccc/ABCD39Z700.p12 \
    --git_url<EMAIL_ADDRESS>\
    --git_branch development \
    --skip_certificate_matching true \
    --import_suppress_ui_file_path_prompts true

# profile only
fastlane match import \
    --import_provisioning_profile_file_path /tmp/pprofile/my_001.mobileprovision \
    --git_url<EMAIL_ADDRESS>\
    --git_branch development \
    --import_suppress_ui_file_path_prompts true

# cert/key + profile
fastlane match import \
    --import_certificate_file_path /tmp/ccc/ABCD39Z700.cer \
    --import_certificate_private_key_file_path /tmp/ccc/ABCD39Z700.p12 \
    --import_provisioning_profile_file_path /tmp/pprofile/my_001.mobileprovision \
    --git_url<EMAIL_ADDRESS>\
    --git_branch development \
    --import_suppress_ui_file_path_prompts true

Testing Steps
See above, see unit tests.
docs
regarding the docs, i'd like to add info about this here: https://github.com/fastlane/docs/blob/master/docs/generated/actions/match.md?plain=1 however the source says this doc is auto-generated... however its unclear where the bulk of the content is coming.... as the source file referenced at https://github.com/fastlane/fastlane/blob/master/fastlane/lib/fastlane/actions/sync_code_signing.rb has none of that content.

also @nekrich regarding docs, can you point me in the right direction please?
i'd like to add info about this here: https://github.com/fastlane/docs/blob/master/docs/generated/actions/match.md?plain=1 however the source says this doc is auto-generated... however its unclear where the bulk of the content is coming.... as the source file referenced at https://github.com/fastlane/fastlane/blob/master/fastlane/lib/fastlane/actions/sync_code_signing.rb has none of that content.

Hi! How can I help move this forward?

The majority of actions has documentation generated based on contents of actions implementation files in ruby, but sync_code_signing has a custom documentation in file:
https://github.com/fastlane/fastlane/blob/master/fastlane/lib/fastlane/actions/docs/sync_code_signing.md
Docs update is started on release, you could check how it's generated in here:
https://github.com/fastlane/fastlane/blob/master/fastlane/Fastfile (update_docs)
https://github.com/fastlane/fastlane/blob/master/fastlane/lib/fastlane/documentation/markdown_docs_generator.rb

Hi @lucgrabowski - i'm just getting back to this PR to move it forward. Latest build again failed on doc but not sure why: https://app.circleci.com/pipelines/github/fastlane/fastlane/6347/workflows/b344c11f-ac30-41a3-887f-8f4376e0fb83/jobs/98623?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-checks-link&utm_content=summary
Regarding "The majority of actions has documentation generated based on contents of actions implementation files in ruby", I guess I'm still not following this. I'm not a ruby developer by trade so I'm going to need some assistance w/ this part; much appreciated.
What specific steps do I need to take to see that the additional arguments in the options.rb here show up in the generated docs? I would assume given the match doc already has a section for the options, and I just added some new ones, that they should be auto generated.

Hi! How can I help move this forward?


data did not match any variant of untagged enum SerializableTransactionType

Component
Anvil
Have you ensured that all of these are up to date?

[X] Foundry
[X] Foundryup

What version of Foundry are you on?
forge 0.2.0 (31c24b0 2024-11-14T00:20:56.222819000Z)
What command(s) is the bug in?
anvil --load-state
Operating System
macOS (Apple Silicon)
Describe the bug
Running:
anvil --load-state /path/anvil_data/state.json

Gives me:
error: invalid value '/path/anvil_data/state.json' for '--load-state <PATH>': failed to parse json file: "/path/anvil_data/state.json": data did not match any variant of untagged enum SerializableTransactionType at line 1 column 11125

However, this command worked on a previously working edition of foundry & anvil.
I was able to revert to an older version where I did not get such an error with the following command:
foundryup -C 1d2379a22a78d48a6f1a159868ca5978f31c5462

Here is the block that was erroring:
{
            "header": {
                "parentHash": "0x4974542d1b2db2ffc73b16aa6394fe5a90b338cc0586ebbecc47c146430d526b",
                "ommersHash": "0x1dcc4de8dec75d7aab85b567b6ccd41ad312451b948a7413f0a142fd40d49347",
                "beneficiary": "0x0000000000000000000000000000000000000000",
                "stateRoot": "0x230b4caf2bd80724bf342cdf4829b1940934848e6aad0f2783436ee72492f3ae",
                "transactionsRoot": "0xab916ba5327c96fc466ed5b8c97511a68fdee5969ed2664d355ebdb6ec79d47e",
                "receiptsRoot": "0xdcb8d1138a074583db4436c14009728a21adce5a5f31ff989a62bd20a239819f",
                "logsBloom": "0x00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000",
                "difficulty": "0x0",
                "number": "0x6",
                "gasLimit": "0x1c9c380",
                "gasUsed": "0x13c56",
                "timestamp": "0x66ff46ba",
                "mixHash": "0x0000000000000000000000000000000000000000000000000000000000000000",
                "nonce": "0x0000000000000000",
                "baseFeePerGas": "0x1eaa23e3",
                "blobGasUsed": "0x0",
                "excessBlobGas": "0x0",
                "extraData": "0x"
            },
            "transactions": [
                {
                    "transaction": {
                        "EIP1559": {
                            "chainId": "0x7a69",
                            "nonce": "0x1",
                            "gasLimit": "0x13c56",
                            "maxFeePerGas": "0x7a90ed8f",
                            "maxPriorityFeePerGas": "0x3b9aca00",
                            "value": "0x0",
                            "accessList": [],
                            "input": "0x61008061000f6000396100806000f35f3560e01c60026003820660011b61007a01601e395f51565b63d6d1ee14811861007257602436103417610076576004355f55005b63d09de08a81186100575734610076575f54600181018181106100765790505f55005b638381f58a81186100725734610076575f5460405260206040f35b5f5ffd5b5f80fd001800340072841880810600a1657679706572830004000013",
                            "r": "0x77e68ead43366987d79a008b4b2d170dde77cf8696b0621871de78e7882a7f3b",
                            "s": "0xa3ebb096729873e4e09287734cdd8bc043b31eb1a40bbeeb77f391ebc15a2d0",
                            "yParity": "0x1",
                            "hash": "0x5ef0b097eac1311b110fdb3b76e8d6029199c9f9bc3197f9ed51548834617c79"
                        }
                    },
                    "impersonated_sender": null
                }
            ], # Error here
            "ommers": []
        },

Where line 1 column 11125 was pointing to the spot I have marked Error here.
This state.json was created on an older version of anvil using --dump-state originally.

That did the job! Thank you.
Maybe flag a warning that this was deprecated? Although, IMO it's unlikely a lot of people use this feature... Maybe its OK just as a breaking change.

I'm OK with taking no action here, since the breaking change is already introduced and an workaround exists.
Also, in scope of v1.0 we're looking into removing all deprecation (as in https://github.com/foundry-rs/foundry/issues/8931, deprecated cheatcodes, etc.) so not sure we should introduce the warning now to just remove it in couple of weeks. @zerosnacks wdyt?

Re-opening, this will be added as part of https://github.com/foundry-rs/foundry/pull/9280#discussion_r1844004048


how to set http headers? how to support wss?

Addressed in 1.1.0.  Arbitrary urls are now allowed and headers from sqlmap are passed by default.


mina crashing when trying to synchronize

Trying to start coda/mina daemon for the first time - this happens while its attempting to sync.
command:
/usr/local/bin/coda daemon   -peer-list-file /home/mina/mina_work/peers.txt  -generate-genesis-proof true   -log-level Debug
Last few log lines with Debug logging enabled:
{
"payload": {
"common": {
"fee": "0.099463309",
"fee_token": "1",
"fee_payer_pk":
"B62qisP6CjtmVugadA2RfNfXBznGnZTKKwusXcATwuEkm8yLSmajszA",
"nonce": "108",
"valid_until": "4294967295",
"memo": "E4Yd67s51QN9DZVDy8JKPEoNGykMsYQ5KRiKpZHiLZTjA8dB9SnFT"
},
"body": [
"Payment",
{
"source_pk":
"B62qisP6CjtmVugadA2RfNfXBznGnZTKKwusXcATwuEkm8yLSmajszA",
"receiver_pk":
"B62qnbskrh5TMZKA6jzTpLxWHjjRCS8pdayJtmc5YbReTCGXm5BpJt2",
"token_id": "1",
"amount": "1500000"
}
]
},
"signer": "B62qisP6CjtmVugadA2RfNfXBznGnZTKKwusXcATwuEkm8yLSmajszA",
"signature":
"7mXTKQfnzpNZr37kX3rjSPyKMNzh4A68DMxve6JBDYdtRA7j3M8aJHq1wM8fk7Aeerx8DXHavgDWYkFU4idVvi6SPSWzko3L"
}
]
2021-01-08 00:55:21 UTC [Fatal] Unhandled top-level exception: $exn
Generating crash report
exn: {
"sexp": [
"Merkle_mask.Masking_merkle_tree.Make(Inputs).Attached.Dangling_parent_reference("bf0c1ef4-64cf-3559-0f20-36353122d54d", "File \"src/lib/transition_router/transition_router.ml\", line 508, characters 61-68")"
],
"backtrace": [
"Raised at file "src/lib/merkle_mask/masking_merkle_tree.ml", line 116, characters 10-57",
"Called from file "src/lib/merkle_mask/masking_merkle_tree.ml", line 121, characters 6-26",
"Called from file "src/lib/network_pool/transaction_pool.ml", line 1189, characters 29-65",
"Called from file "src/lib/network_pool/transaction_pool.ml", line 1202, characters 18-30",
"Called from file "src/lib/network_pool/network_pool_base.ml", line 101, characters 15-67",
"Called from file "src/lib/pipe_lib/strict_pipe.ml", line 155, characters 28-37",
"Called from file "src/deferred0.ml", line 56, characters 64-69",
"Called from file "src/job_queue.ml" (inlined), line 131, characters 2-5",
"Called from file "src/job_queue.ml", line 171, characters 6-47"
]
}
2021-01-08 00:55:21 UTC [Debug] Successfully wrote the visualization of the registered masks at location: /root/.coda-config/coda_crash_report_2021-01-08_00-55-21.968267/registered_masks.dot.
2021-01-08 00:55:22 UTC [Debug] Could not visualize transition frontier since daemon is currently bootstrapping
☠  Coda Daemon crashed.
The Coda Protocol developers would like to know why!
Please:
  Open an issue:
    <https://github.com/CodaProtocol/coda/issues/new>

  Briefly describe what you were doing and attach the crash report /root/.coda-config/coda_crash_report_2021-01-08_00-55-21.968267.tar.gz

This may be a memory issue. Original VM I ran this on had 16GB of RAM. I've spun up an instance with 64GB and it hasn't crashed yet.
Memory usage has exceeded 16GB already and I have nothing else installed - Fresh Ubuntu installation.
PID USER      PR  NI    VIRT    RES    SHR S  %CPU %MEM     TIME+ COMMAND
6149 mina      20   0 12.890g 0.011t  65460 R  82.4 18.5  26:19.93 coda
6471 mina      20   0 5328276 2.407g  29996 S  31.9  3.8   3:23.82 coda-libp2p_hel
6403 mina      20   0 2629344 2.136g  63740 S   0.0  3.4   4:01.73 exe
7147 mina      20   0<PHONE_NUMBER>20  64016 S 539.9  0.3   0:30.43 exe
mina@instance-1:~/.coda-config$ free -m
total        used        free      shared  buff/cache   available
Mem:          64324       16989       43664          12        3670       48083
Swap:             0           0           0

This may be a memory issue. Original VM I ran this on had 16GB of RAM. I've spun up an instance with 64GB and it hasn't crashed yet.
Memory usage has exceeded 16GB already and I have nothing else installed - Fresh Ubuntu installation.
PID USER      PR  NI    VIRT    RES    SHR S  %CPU %MEM     TIME+ COMMAND
6149 mina      20   0 12.890g 0.011t  65460 R  82.4 18.5  26:19.93 coda
6471 mina      20   0 5328276 2.407g  29996 S  31.9  3.8   3:23.82 coda-libp2p_hel
6403 mina      20   0 2629344 2.136g  63740 S   0.0  3.4   4:01.73 exe
7147 mina      20   0<PHONE_NUMBER>20  64016 S 539.9  0.3   0:30.43 exe
mina@instance-1:~/.coda-config$ free -m
total        used        free      shared  buff/cache   available
Mem:          64324       16989       43664          12        3670       48083
Swap:             0           0           0

Nevermind - adding more memory only seemed to allow it to run a bit longer.
The process eventually segfaulted after exceeding 20 GB of memory. I didn't get the exact amount of memory that was used as it died before I could check:
mina@instance-1:~/.coda-config$ free -m
total        used        free      shared  buff/cache   available
Mem:          64324       20407       40213          12        3703       44834
Swap:             0           0           0
mina@instance-1:~/.coda-config$ coda client status
{"timestamp":"2021-01-08 03:30:36.599258Z","level":"Debug","source":{"module":"Block_time","location":"File "src/lib/block_time/block_time.ml", line 76, characters 18-30"},"message":"Environment variable CODA_TIME_OFFSET not found, using default of 0","metadata":{"pid":7285}}
Coda daemon status
Global number of accounts:                     2687
Block height:                                  425
Max observed block length:                     723
Local uptime:                                  41m36s
Ledger Merkle root:                            jwR2Vj9bZmEoVtMbSrFej8PfNBW8QF4FXpPm5gunryw4nX771z8
Protocol state hash:                           3NKHWD1gj8vCpJ5kopzNDQjpmpiR2LCJ4M6Cz3qt2NC5Q2rfjzAq
Chain id:                                      2dbac725ebb5c6c8b1daf21cda9e3694951ab72afe9be99ff7ca47574112f43b
Git SHA-1:                                     [DIRTY]b7eff8e5c966b12bdc298160297c716eae7a35af
Configuration directory:                       /home/mina/.coda-config
Peers:                                         57 (<IP_ADDRESS>:10511 <IP_ADDRESS>:10506 <IP_ADDRESS>:8302 <IP_ADDRESS>:8302 <IP_ADDRESS>:8302 <IP_ADDRESS>:8302 <IP_ADDRESS>:8302 <IP_ADDRESS>:8302 <IP_ADDRESS>:8302 <IP_ADDRESS>:8302 <IP_ADDRESS>:8302 <IP_ADDRESS>:10510 <IP_ADDRESS>:8302 <IP_ADDRESS>:8302 <IP_ADDRESS>:8302 <IP_ADDRESS>:10001 <IP_ADDRESS>:8302 <IP_ADDRESS>:10519 <IP_ADDRESS>:8302 <IP_ADDRESS>:8302 <IP_ADDRESS>:8302 <IP_ADDRESS>:8302 <IP_ADDRESS>:8302 <IP_ADDRESS>:8302 <IP_ADDRESS>:10504 <IP_ADDRESS>:10516 <IP_ADDRESS>:8302 <IP_ADDRESS>:8302 <IP_ADDRESS>:8302 <IP_ADDRESS>:10513 <IP_ADDRESS>:8302 <IP_ADDRESS>:8302 <IP_ADDRESS>:8302 <IP_ADDRESS>:8302 <IP_ADDRESS>:8302 <IP_ADDRESS>:8302 <IP_ADDRESS>:10502 <IP_ADDRESS>:8302 <IP_ADDRESS>:8302 <IP_ADDRESS>:8302 <IP_ADDRESS>:8302 <IP_ADDRESS>:8302 <IP_ADDRESS>:10001 <IP_ADDRESS>:8302 <IP_ADDRESS>:8302 <IP_ADDRESS>:10501 <IP_ADDRESS>:8302 <IP_ADDRESS>:8302 <IP_ADDRESS>:8302 <IP_ADDRESS>:8302 <IP_ADDRESS>:8302 <IP_ADDRESS>:8302 <IP_ADDRESS>:8302 <IP_ADDRESS>:10909 <IP_ADDRESS>:8302 <IP_ADDRESS>:8302 <IP_ADDRESS>:8302)
User_commands sent:                            0
SNARK worker:                                  None
SNARK work fee:                                25000000
Sync status:                                   Catchup
Block producers running:                       0
Best tip consensus time:                       epoch=0, slot=2253
Best tip global slot (across all hard-forks):  2253
Next block will be produced in:                None this epoch… checking at in 6.53d
Consensus time now:                            epoch=0, slot=4005
Consensus mechanism:                           proof_of_stake
Consensus configuration:
Delta:                     0
k:                         290
Slots per epoch:           7140
Slot duration:             3m
Epoch duration:            14d21h
Chain start timestamp:     2020-12-30 19:14:30.000000Z
Acceptable network delay:  3m
Addresses and ports:
External IP:    <IP_ADDRESS>
Bind IP:        <IP_ADDRESS>
Libp2p PeerID:  12D3KooWKPMJBc5AiJKbU3bXiDMfrDYkhceFKnTF3cXid6vdMuKq
Libp2p port:    8302
Client port:    8301
2021-01-08 03:31:29 UTC [Info] Catch up to $target_hash
target_hash: "3NLWJGffCdRGCNe6fw15T6nGLtWe1id9ZQMcU8sYpHmYfARqWrfU"
2021-01-08 03:31:29 UTC [Info] Coda daemon is doing ledger catchup
2021-01-08 03:32:05 UTC [Warn] RPC call error for "get_transition_chain"
2021-01-08 03:32:05 UTC [Warn] RPC call error for "get_transition_chain"
2021-01-08 03:32:05 UTC [Warn] RPC call error for "get_transition_chain"
2021-01-08 03:32:07 UTC [Warn] failed to reset stream (this means it was probably closed successfully): $error
error: {
"string":
"RPC #20980 failed: "internal RPC error error: unknown stream_idx""
}
2021-01-08 03:32:09 UTC [Error] error sending message on stream 8819: $error
error: {
"string":
"RPC #21001 failed: "only wrote 0 out of 9 bytes error: libp2p error error: closed stream""
}
2021-01-08 03:32:09 UTC [Warn] RPC call error for "get_transition_chain"
2021-01-08 03:32:09 UTC [Error] error sending message on stream 8822: $error
error: {
"string":
"RPC #21016 failed: "only wrote 0 out of 9 bytes error: libp2p error error: closed stream""
}
2021-01-08 03:32:09 UTC [Warn] RPC call error for "get_transition_chain"
2021-01-08 03:32:10 UTC [Error] error sending message on stream 8819: $error
error: {
"string":
"RPC #21047 failed: "only wrote 0 out of 9 bytes error: libp2p error error: closed stream""
}
2021-01-08 03:32:10 UTC [Error] error sending message on stream 8822: $error
error: {
"string":
"RPC #21061 failed: "only wrote 0 out of 698 bytes error: libp2p error error: closed stream""
}
2021-01-08 03:32:45 UTC [Warn] RPC call error for "get_transition_chain"
2021-01-08 03:32:45 UTC [Warn] RPC call error for "get_transition_chain"
2021-01-08 03:32:53 UTC [Info] Sending transition_chain to $peer
peer: {
"host": "<IP_ADDRESS>",
"peer_id": "12D3KooWJXFVTDQQuHgZCC2y6z4UQ84y8QvGBSm2oEfS2fc2HASv",
"libp2p_port": 8302
}
Segmentation fault (core dumped)
mina@instance-1:~/mina_work$

Nevermind - adding more memory only seemed to allow it to run a bit longer.
The process eventually segfaulted after exceeding 20 GB of memory. I didn't get the exact amount of memory that was used as it died before I could check:
mina@instance-1:~/.coda-config$ free -m
total        used        free      shared  buff/cache   available
Mem:          64324       20407       40213          12        3703       44834
Swap:             0           0           0
mina@instance-1:~/.coda-config$ coda client status
{"timestamp":"2021-01-08 03:30:36.599258Z","level":"Debug","source":{"module":"Block_time","location":"File "src/lib/block_time/block_time.ml", line 76, characters 18-30"},"message":"Environment variable CODA_TIME_OFFSET not found, using default of 0","metadata":{"pid":7285}}
Coda daemon status
Global number of accounts:                     2687
Block height:                                  425
Max observed block length:                     723
Local uptime:                                  41m36s
Ledger Merkle root:                            jwR2Vj9bZmEoVtMbSrFej8PfNBW8QF4FXpPm5gunryw4nX771z8
Protocol state hash:                           3NKHWD1gj8vCpJ5kopzNDQjpmpiR2LCJ4M6Cz3qt2NC5Q2rfjzAq
Chain id:                                      2dbac725ebb5c6c8b1daf21cda9e3694951ab72afe9be99ff7ca47574112f43b
Git SHA-1:                                     [DIRTY]b7eff8e5c966b12bdc298160297c716eae7a35af
Configuration directory:                       /home/mina/.coda-config
Peers:                                         57 (<IP_ADDRESS>:10511 <IP_ADDRESS>:10506 <IP_ADDRESS>:8302 <IP_ADDRESS>:8302 <IP_ADDRESS>:8302 <IP_ADDRESS>:8302 <IP_ADDRESS>:8302 <IP_ADDRESS>:8302 <IP_ADDRESS>:8302 <IP_ADDRESS>:8302 <IP_ADDRESS>:8302 <IP_ADDRESS>:10510 <IP_ADDRESS>:8302 <IP_ADDRESS>:8302 <IP_ADDRESS>:8302 <IP_ADDRESS>:10001 <IP_ADDRESS>:8302 <IP_ADDRESS>:10519 <IP_ADDRESS>:8302 <IP_ADDRESS>:8302 <IP_ADDRESS>:8302 <IP_ADDRESS>:8302 <IP_ADDRESS>:8302 <IP_ADDRESS>:8302 <IP_ADDRESS>:10504 <IP_ADDRESS>:10516 <IP_ADDRESS>:8302 <IP_ADDRESS>:8302 <IP_ADDRESS>:8302 <IP_ADDRESS>:10513 <IP_ADDRESS>:8302 <IP_ADDRESS>:8302 <IP_ADDRESS>:8302 <IP_ADDRESS>:8302 <IP_ADDRESS>:8302 <IP_ADDRESS>:8302 <IP_ADDRESS>:10502 <IP_ADDRESS>:8302 <IP_ADDRESS>:8302 <IP_ADDRESS>:8302 <IP_ADDRESS>:8302 <IP_ADDRESS>:8302 <IP_ADDRESS>:10001 <IP_ADDRESS>:8302 <IP_ADDRESS>:8302 <IP_ADDRESS>:10501 <IP_ADDRESS>:8302 <IP_ADDRESS>:8302 <IP_ADDRESS>:8302 <IP_ADDRESS>:8302 <IP_ADDRESS>:8302 <IP_ADDRESS>:8302 <IP_ADDRESS>:8302 <IP_ADDRESS>:10909 <IP_ADDRESS>:8302 <IP_ADDRESS>:8302 <IP_ADDRESS>:8302)
User_commands sent:                            0
SNARK worker:                                  None
SNARK work fee:                                25000000
Sync status:                                   Catchup
Block producers running:                       0
Best tip consensus time:                       epoch=0, slot=2253
Best tip global slot (across all hard-forks):  2253
Next block will be produced in:                None this epoch… checking at in 6.53d
Consensus time now:                            epoch=0, slot=4005
Consensus mechanism:                           proof_of_stake
Consensus configuration:
Delta:                     0
k:                         290
Slots per epoch:           7140
Slot duration:             3m
Epoch duration:            14d21h
Chain start timestamp:     2020-12-30 19:14:30.000000Z
Acceptable network delay:  3m
Addresses and ports:
External IP:    <IP_ADDRESS>
Bind IP:        <IP_ADDRESS>
Libp2p PeerID:  12D3KooWKPMJBc5AiJKbU3bXiDMfrDYkhceFKnTF3cXid6vdMuKq
Libp2p port:    8302
Client port:    8301
2021-01-08 03:31:29 UTC [Info] Catch up to $target_hash
target_hash: "3NLWJGffCdRGCNe6fw15T6nGLtWe1id9ZQMcU8sYpHmYfARqWrfU"
2021-01-08 03:31:29 UTC [Info] Coda daemon is doing ledger catchup
2021-01-08 03:32:05 UTC [Warn] RPC call error for "get_transition_chain"
2021-01-08 03:32:05 UTC [Warn] RPC call error for "get_transition_chain"
2021-01-08 03:32:05 UTC [Warn] RPC call error for "get_transition_chain"
2021-01-08 03:32:07 UTC [Warn] failed to reset stream (this means it was probably closed successfully): $error
error: {
"string":
"RPC #20980 failed: "internal RPC error error: unknown stream_idx""
}
2021-01-08 03:32:09 UTC [Error] error sending message on stream 8819: $error
error: {
"string":
"RPC #21001 failed: "only wrote 0 out of 9 bytes error: libp2p error error: closed stream""
}
2021-01-08 03:32:09 UTC [Warn] RPC call error for "get_transition_chain"
2021-01-08 03:32:09 UTC [Error] error sending message on stream 8822: $error
error: {
"string":
"RPC #21016 failed: "only wrote 0 out of 9 bytes error: libp2p error error: closed stream""
}
2021-01-08 03:32:09 UTC [Warn] RPC call error for "get_transition_chain"
2021-01-08 03:32:10 UTC [Error] error sending message on stream 8819: $error
error: {
"string":
"RPC #21047 failed: "only wrote 0 out of 9 bytes error: libp2p error error: closed stream""
}
2021-01-08 03:32:10 UTC [Error] error sending message on stream 8822: $error
error: {
"string":
"RPC #21061 failed: "only wrote 0 out of 698 bytes error: libp2p error error: closed stream""
}
2021-01-08 03:32:45 UTC [Warn] RPC call error for "get_transition_chain"
2021-01-08 03:32:45 UTC [Warn] RPC call error for "get_transition_chain"
2021-01-08 03:32:53 UTC [Info] Sending transition_chain to $peer
peer: {
"host": "<IP_ADDRESS>",
"peer_id": "12D3KooWJXFVTDQQuHgZCC2y6z4UQ84y8QvGBSm2oEfS2fc2HASv",
"libp2p_port": 8302
}
Segmentation fault (core dumped)
mina@instance-1:~/mina_work$

This is a duplicate of #6949. Closing.
The segfault issue is being tracked in #7333.

This is a duplicate of #6949. Closing.
The segfault issue is being tracked in #7333.


Main "browser" field exists but fail to resolve - resolver fallsback to "main" field resolving nodejs version of package

Bug report
Importing a npm package "handlebars" with browser support end up resolving to node version of the module.
What is the current behavior?
import Handlebars from 'handlebars'; // <- resolves to ./lib/index.js
import Handlebars from 'handlebars/runtime'; // <- resolves to ./dist/cjs/handlebars.runtime.js

Main fields in the handlebars package:
"main": "lib/index.js",
"types": "types/index.d.ts",
"browser": {
    ".": "./dist/cjs/handlebars.js",
    "./runtime": "./dist/cjs/handlebars.runtime.js"
},

Reference to code in Handlebar
If the current behavior is a bug, please provide the steps to reproduce.
npx<EMAIL_ADDRESS>test-handlebars
npm install handlebars

In ./src/App.js
import "handlebars";
// import "handlebars/runtime"; // Resolves correctly

npm run build

><EMAIL_ADDRESS>build
> react-scripts build

Creating an optimized production build...
Failed to compile.

Module not found: Error: Can't resolve 'fs' in '/home/raix/dev/test-handlebars/node_modules/handlebars/lib'

What is the expected behavior?
The application should build without the need for NodeJS builtin fallbacks

Other relevant information:
webpack version:  5.65.0
Node.js version: 16.5.0
Operating System: Mac OS
Additional tools:
(but issue repported by CRA users might be general)
Additional debug information
When logging from a resolve plugin I do see:

When importing "handlebars/runtime"

Creating an optimized production build...
--
 request.context.issuer: /home/raix/dev/create-react-app/packages/cra-template/template/src/App.js
 request.path /home/raix/dev/create-react-app/node_modules/handlebars/runtime
--
 request.context.issuer: /home/raix/dev/create-react-app/packages/cra-template/template/src/App.js
 request.path /home/raix/dev/create-react-app/node_modules/handlebars/dist/cjs/handlebars.runtime.js # Correct!
--

When importing "handlebars"

Creating an optimized production build...
--
 request.context.issuer: /home/raix/dev/create-react-app/packages/cra-template/template/src/App.js
 request.path /home/raix/dev/create-react-app/node_modules/handlebars
--
 request.context.issuer: /home/raix/dev/create-react-app/packages/cra-template/template/src/App.js
 request.path /home/raix/dev/create-react-app/node_modules/handlebars.web.mjs
--
 request.context.issuer: /home/raix/dev/create-react-app/packages/cra-template/template/src/App.js
 request.path /home/raix/dev/create-react-app/node_modules/handlebars.mjs
--
 request.context.issuer: /home/raix/dev/create-react-app/packages/cra-template/template/src/App.js
 request.path /home/raix/dev/create-react-app/node_modules/handlebars.web.js
--
 request.context.issuer: /home/raix/dev/create-react-app/packages/cra-template/template/src/App.js
 request.path /home/raix/dev/create-react-app/node_modules/handlebars.js
--
 request.context.issuer: /home/raix/dev/create-react-app/packages/cra-template/template/src/App.js
 request.path /home/raix/dev/create-react-app/node_modules/handlebars.json
--
 request.context.issuer: /home/raix/dev/create-react-app/packages/cra-template/template/src/App.js
 request.path /home/raix/dev/create-react-app/node_modules/handlebars.web.jsx
--
 request.context.issuer: /home/raix/dev/create-react-app/packages/cra-template/template/src/App.js
 request.path /home/raix/dev/create-react-app/node_modules/handlebars.jsx
--
 request.context.issuer: /home/raix/dev/create-react-app/packages/cra-template/template/src/App.js
 request.path /home/raix/dev/create-react-app/node_modules/handlebars/lib/index.js # Wrong!

When changing the handlebars package.json mainField "main" and import "handlebars" again it works

  "main": "./dist/cjs/handlebars.js", // Changed to force correct resolve
  "types": "types/index.d.ts",
  "browser": {
    ".": "./dist/cjs/handlebars.js",
    "./runtime": "./dist/cjs/handlebars.runtime.js"
  },

Creating an optimized production build...
--
 request.context.issuer: /home/raix/dev/create-react-app/packages/cra-template/template/src/App.js
 request.path /home/raix/dev/create-react-app/node_modules/handlebars
--
 request.context.issuer: /home/raix/dev/create-react-app/packages/cra-template/template/src/App.js
 request.path /home/raix/dev/create-react-app/node_modules/handlebars.web.mjs # Correct!
--

I don't think it's a good idea to fallback to other main fields if the one first in order exists. (not sure if we can already configure this behaviour?)
E.g. if we are building for the browser and a package contains "browser" and "main" we should not fallback to main when theres a "browser" main field? (rather fail the build with a reference to that package letting the maintainer fix that - otherwise we risk adding node js / backend code on in the browser code / front-end)

"./runtime": "./dist/cjs/handlebars.runtime.js"

That's not how the browser field works. It's a replacing configuration for files. The left file need to specify a file.
https://github.com/defunctzombie/package-browser-field-spec#replace-specific-files---advanced

@sokra I'm on CRA project not handlebars - yes I read the exports syntax, but following is unclear to me still:

Can "browser" be both exportFields and mainFields syntax?
For some reason the runtime actually resolves correctly not sure if it's ment to work?

(It seems like the intent of the package author was to use the exports syntax for sure, but the result is unexpected from my point of view)
We carried over the breaking change CRA as in Webpack, it seems more developers are using packages in the front-end not meant for it eg. "dotenv" - would be great to encourage the community to solve the confusion regarding npm packages and have package authors build specific bundles/declare dependencies on fallback versions etc.
If we blindly add the fallbacks then in this case the code ment for nodejs will load in the browser - seems unexpected?

is "." meant to work as a wildcard?
The thing not working is ".": "./dist/cjs/handlebars.js",

you should map
"./lib/index.js": "./dist/cjs/handlebars.js"

Bad bot!

This bot is super lame, the issue is legit. Last time I report something here


Some UP users are not able to post jobs to the AUPresses job site

Describe the bug
Users are logged into AUPresses, but when they go to the jobs site it does not reflect that they're logged in. When they try to post a job it prevents them from accessing it. The reporting user:
<EMAIL_ADDRESS>- https://registry.hcommons.org/registry/co_people/canvas/162535
To Reproduce
See video.

User's COmanage record and LDAP record look correct. They have a 'UP' badge on their profile. This looks like a bug, but further investigation is required. The next WP update will include logging for users who get this message.

Yeah, Nora from AUPresses tried and got an error when trying to post a new job, but was able to get in to post:
"Nora was using another employee's account. She is now registered with her own under her name but is getting error messages when trying to preview her post.
"I was able to get back to the job posting page under my login, so at least that piece worked! As soon as I pushed the Preview button it gave me an error message and deleted it, so I guess I’ll try the actual posting piece again tomorrow!"
I'm trying to get the text of the error message.

More information on the error: "When I click on preview after putting all of the info in, I get the below.  What’s odd is that when I did a test just before this error message, when I had only put a few random letters in the job description box it worked – so, I copied the full job description back in and then when I pushed preview again this is what I get."

The culprit was the "(TMS)" (no quotes) in the job listing. The theory is that WordPress choked on the "(TM." User has been able to post the listing. I'm closing this as it seems to be an odd occurrence. Will create another ticket if it continues.


Build Failure with node v6

running npm install xpc-connection caused a build failure for node v6.3.1 on Mac OS X

><EMAIL_ADDRESS>install /Users/wgillis/dev/node/micro_leads_stimulator_ui/node_modules/xpc-connection
> node-gyp rebuild

gyp WARN download NVM_NODEJS_ORG_MIRROR is deprecated and will be removed in node-gyp v4, please use NODEJS_ORG_MIRROR
gyp WARN download NVM_NODEJS_ORG_MIRROR is deprecated and will be removed in node-gyp v4, please use NODEJS_ORG_MIRROR
gyp WARN download NVM_NODEJS_ORG_MIRROR is deprecated and will be removed in node-gyp v4, please use NODEJS_ORG_MIRROR
  CXX(target) Release/obj.target/binding/src/XpcConnection.o
In file included from ../src/XpcConnection.cpp:7:
In file included from ../src/XpcConnection.h:10:
../../nan/nan.h:602:20: error: no type named 'GCEpilogueCallback' in 'v8::Isolate'
      v8::Isolate::GCEpilogueCallback callback
      ~~~~~~~~~~~~~^
../../nan/nan.h:608:20: error: no type named 'GCEpilogueCallback' in 'v8::Isolate'
      v8::Isolate::GCEpilogueCallback callback) {
      ~~~~~~~~~~~~~^
../../nan/nan.h:613:20: error: no type named 'GCPrologueCallback' in 'v8::Isolate'
      v8::Isolate::GCPrologueCallback callback
      ~~~~~~~~~~~~~^
../../nan/nan.h:619:20: error: no type named 'GCPrologueCallback' in 'v8::Isolate'
      v8::Isolate::GCPrologueCallback callback) {
      ~~~~~~~~~~~~~^
4 errors generated.
make: *** [Release/obj.target/binding/src/XpcConnection.o] Error 1
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:276:23)
gyp ERR! stack     at emitTwo (events.js:106:13)
gyp ERR! stack     at ChildProcess.emit (events.js:191:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:204:12)
gyp ERR! System Darwin 15.6.0
gyp ERR! command "/usr/local/bin/node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /Users/wgillis/dev/node/micro_leads_stimulator_ui/node_modules/xpc-connection
gyp ERR! node -v v6.3.1
gyp ERR! node-gyp -v v3.3.1
gyp ERR! not ok
npm WARN<EMAIL_ADDRESS><EMAIL_ADDRESS>install: `node-gyp rebuild`
npm WARN<EMAIL_ADDRESS>Exit status 1

Hi @wingillis,
Could you please try cloning this repo and changing the nan dependency in package.json to the latest (2.4.0). Then run npm install.

Great, that worked as expected! It installed without error and functioned correctly 👍

@wingillis great thanks for trying it out! Could you please submit a pull request with the change?

@sandeepmistry alright - I sent a pull request!

This is fixed by #14.


docs: add ELMO Cloud HR & Payroll to list of users on readme

SUMMARY
Add ELMO Cloud HR & Payroll to list of users on readme.md
ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Changes UI
[ ] Requires DB Migration.
[ ] Confirm DB Migration upgrade and downgrade tested.
[ ] Introduces new feature or API
[ ] Removes existing feature or API
[x ] Documentation

Codecov Report

Merging #9960 into master will decrease coverage by 0.19%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #9960      +/-   ##
==========================================
- Coverage   71.34%   71.14%   -0.20%
==========================================
  Files         585      184     -401
  Lines       30889    18035   -12854
  Branches     3237        0    -3237
==========================================
- Hits        22037    12831    -9206
+ Misses       8743     5204    -3539
+ Partials      109        0     -109

Flag
Coverage Δ

#cypress
?

#javascript
?

#python
71.14% <ø> (-0.40%)
:arrow_down:

Impacted Files
Coverage Δ

superset/views/database/mixins.py
59.64% <0.00%> (-21.06%)
:arrow_down:

superset/utils/cache.py
48.00% <0.00%> (-20.00%)
:arrow_down:

superset/db_engine_specs/mysql.py
78.26% <0.00%> (-13.05%)
:arrow_down:

superset/views/database/validators.py
78.94% <0.00%> (-5.27%)
:arrow_down:

superset/views/tags.py
35.13% <0.00%> (-4.11%)
:arrow_down:

superset/views/database/api.py
84.09% <0.00%> (-3.41%)
:arrow_down:

superset/views/sql_lab.py
59.06% <0.00%> (-3.29%)
:arrow_down:

superset/cli.py
36.72% <0.00%> (-3.14%)
:arrow_down:

superset/db_engine_specs/postgres.py
97.29% <0.00%> (-2.71%)
:arrow_down:

superset/views/database/views.py
87.17% <0.00%> (-2.57%)
:arrow_down:

... and 418 more

Continue to review full report at Codecov.

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


Forking

We can only implement it as it was in Devnet-py if the underlying Starknet state implementation has a separate State and StateReader.
First we need to switch to blockifier.

I will give it a try if possible.


Always getting a 404 - Not found response

Description
I always get a 200 response with this content:
{
  results: [
    {
      code: 404,
      error: "Not found."
    }
  ]
}

I'm not sure if this error means that there is no coincidences on my search, or that the root resource is not found. I understand that is the server the one answering, so I guess I'm doing my request right.
Steps to reproduce
My Typesense server is started using docker. See this part of my docker-compose.yml:
version: '3.6'

services:
  typesense:
    container_name: typesense
    image: 'typesense/typesense:0.22.0.rcu7'
    entrypoint: sh -c "/opt/typesense-server --data-dir /data --api-key=86c5153b35cf --enable-cors"
    ports:
      - '8108:8108'
    volumes:
      - ./typesense-data/:/data
...

Having this gatsby-config.js (I made it so you can see the important part):
{
      resolve: "gatsby-plugin-typesense",
      options: {
        rootDir: path.resolve(__dirname, '../theme/wordpress/public/es-es'),
        collectionSchema: {
          name: "category",
          fields: [
            {
              name: "category_name",
              type: "string",
            },
            {
              name: "page_path",
              type: "string",
            },
            {
              name: "page_priority_score",
              type: "int32",
            },
          ],
          default_sorting_field: "page_priority_score",
        },
        server: {
          apiKey: "86c5153b35cf",
          nodes: [
            {
              host: "<IP_ADDRESS>",
              port: "8108",
              protocol: "http",
            },
          ],
        },
      },
    },
    {
      resolve: `gatsby-plugin-typesense`,
      options: {
        rootDir: path.resolve(__dirname, '../theme/wordpress/public/es-es'),
        collectionSchema: {
          name: "brand",
          fields: [
            {
              name: "brand_name",
              type: "string",
            },
            {
              name: "page_path",
              type: "string",
            },
            {
              name: "page_priority_score",
              type: "int32",
            },
          ],
          default_sorting_field: "page_priority_score",
        },
        server: {
          apiKey: "86c5153b35cf",
          nodes: [
            {
              host: "<IP_ADDRESS>",
              port: "8108",
              protocol: "http",
            },
          ],
        },
      },
    },
    {
      resolve: `gatsby-plugin-typesense`,
      options: {
        rootDir: path.resolve(__dirname, '../theme/wordpress/public/es-es'),
        collectionSchema: {
          name: "product",
          fields: [
            {
              name: "product_name",
              type: "string",
            },
            {
              name: "page_path",
              type: "string",
            },
            {
              name: "page_priority_score",
              type: "int32",
            },
          ],
          default_sorting_field: "page_priority_score",
        },
        server: {
          apiKey: "86c5153b35cf",
          nodes: [
            {
              host: "<IP_ADDRESS>",
              port: "8108",
              protocol: "http",
            },
          ],
        },
      },
    },

And, considering I have my pages stored in the rootDir folder:

Containing some dom elements inside like this one:

Abrigos

And this React component:
import { InstantSearch, SearchBox, Hits, Stats } from "react-instantsearch-dom"
import TypesenseInstantSearchAdapter from "typesense-instantsearch-adapter"
...

const typesenseInstantsearchAdapter = new TypesenseInstantSearchAdapter({
  server: {
    apiKey: config.typesenseApiKey,
    nodes: [
      {
        host: "<IP_ADDRESS>",
        port: "8108",
        protocol: "http",
      },
    ],
  },
  // The following parameters are directly passed to Typesense's search API endpoint.
  //  So you can pass any parameters supported by the search endpoint below.
  //  queryBy is required.
  collectionSpecificSearchParameters: {
    category: {
      queryBy: "category_name",
    },
    brand: {
      queryBy: "brand_name",
    },
    product: {
      queryBy: "product_name",
    },
  },
})
const searchClient = typesenseInstantsearchAdapter.searchClient

const Hit = ({ hit }) => (

    {hit.title} - {hit.description}

);

const Search = () => {
  return (
    <InstantSearch searchClient={searchClient} indexName="category" >
      <SearchBox />
      <Stats />
      <Hits hitComponent={Hit} />
    </InstantSearch >
  )
}

I'm getting the response 404 - Not found
Here you can see the network request that is being used:
http://<IP_ADDRESS>:8108/multi_search?x-typesense-api-key=86c5153b35cf
{"searches":[{"query_by":"category_name","sort_by":"","highlight_full_fields":"category_name","collection":"category","q":"abrigo","facet_by":"","page":1}]}

Expected Behavior
When I search, for example, "Abrigo", I would expect the server to return some hits.
Actual Behavior
I always get the response I mentioned above.
Metadata
Typsense Version:
I have followed this guide: https://medium.com/swlh/building-a-search-bar-for-your-gatsbyjs-site-with-typesense-3e277dc33942
So I have a typesense server started with docker, which version is typesense/typesense:0.22.1.
On the client, I have:
"typesense-instantsearch-adapter": "~2.2.0",
"gatsby-plugin-typesense": "~0.3.0"

OS:
Ubuntu 20.04LTS on WSL (Windows 10)

Hi @jasonbosco . I didn't know about that!
I have only tried running gatsby develop, so your suggestion looks promising.
As soon as I try it (if not today, it will be tomorrow for sure), I'll let you know here.
Thanks a lot

Hi again.
Sorry if I wrote it in the wrong place. I opened another issue on Typesense:
https://github.com/typesense/typesense/issues/505
Basically, after running npm run build I'm getting an error saying that my fields cannot be found in the collection schema.

I would like to share my directory structure, so you can see maybe where the problem is:

I have a lot of pages like this one, some of them have category_name as a data-typesense-field, others have brand_name and others have product_name.
I have those 3 definitions of schema in my gatsby config as you can see above.
What could then the problem be?
Thanks again

Some news.
I changed the gatsby config to only one collection:
{
      resolve: `gatsby-plugin-typesense`,
      options: {
        rootDir: `${__dirname}/public/es-es`,
        collectionSchema: {
          name: "pages_v1",
          fields: [
            {
              name: "category_name",
              type: "string",
            },
            {
              name: "brand_name",
              type: "string",
            },
            {
              name: "product_name",
              type: "string",
            },
            {
              name: "page_path",
              type: "string",
            },
            {
              name: "page_priority_score",
              type: "int32",
            },
          ],
          default_sorting_field: "page_priority_score",
        },
        server: {
          apiKey: "86c5153b35cf",
          nodes: [
            {
              host: "localhost",
              port: "8108",
              protocol: "http",
            },
          ],
        },
      },
    },

And now I'm getting this error...
[Typesense] Could not create document: Error: Request failed with HTTP code 400 | Server said: Field product_name has been declared in the schema, but is not found in the document.

@Richacinas If that field is not found on all pages, you want to set that field as "optional": true in the schema, right after defining its data type.

Hi again.
That worked, and now it looks like my whole setup is correct, except for one thing. I'm trying to build on a local environment, where my SSL certificates are self signed, and at the end of the process I get this error:
warn Request #1643904569511: Request to Node 0 failed due to "CERT_HAS_EXPIRED certificate has expired"
warn Request #1643904569511: Sleeping for 0.1s and then retrying request...
warn Request #1643904569511: Request to Node 0 failed due to "CERT_HAS_EXPIRED certificate has expired"
warn Request #1643904569511: Sleeping for 0.1s and then retrying request...

 ERROR

[Typesense] Could not create collection pages_v1_1643904569510: Error: certificate has expired

not finished onPostBuild - 0.284s

@Richacinas You would have to add your self-signed cert to the root certificate store in your OS, to get the certificate to be trusted. Something like this or an equivalent article might work.

After following similar steps to create a self signed certificate that is trusted on the local machine, I also had tu run the process like this in order to make it work (otherwise I got a similar error):
NODE_TLS_REJECT_UNAUTHORIZED=0 npm run build

Thank you for documenting that!


The loop is unconditionally terminated

Looks like these break should be there, isn't it?
https://github.com/coroot/coroot/blob/bd32d6f1ca3f8addd00ba097c96a79e10c684029/api/views/overview/health.go#L60
https://github.com/coroot/coroot/blob/bd32d6f1ca3f8addd00ba097c96a79e10c684029/api/views/overview/health.go#L72
Also, these 2 look suspicious to me
https://github.com/coroot/coroot/blob/bd32d6f1ca3f8addd00ba097c96a79e10c684029/watchers/deployments.go#L272
https://github.com/coroot/coroot/blob/bd32d6f1ca3f8addd00ba097c96a79e10c684029/watchers/deployments.go#L278

@cristaloleg,
The model allows having multiple SLIs of each kind, but in fact, Coroot supports only one for now. We are just checking if an SLI is defined.


Click Effect issue on Unclicked button

    public override VisualNode Render()
    => ContentPage( new MauiReactor.Button(text:"TEST").Center());

I found a problem where the click effect came out even if I didn't click on the button area.
I share a simple code to help you understand.
The buttons were placed in the middle of the Android environment.
And if you click on the Content Page area instead of the button, the effect will occur as if the button was clicked.
What's the reason?

For some reason, I shut down the emulator again, so it works again.


Add JoinCommaSeparatedBuilder

Summary
This PR introduces a new JoinCommaSeparatedBuilder that eases joining comma separated sequences, that should have a trailing comma.

Test Plan
I replaced the existing code that manually handled the trailing comma with the new builder. The snapshot tests remain unchanged.

Current dependencies on/for this PR:

main

PR #5342   👈

This comment was auto-generated by Graphite.


Tizen support for Xamarin Forms

Is Tizen support for Xamarin Forms in the planned pipeline?

Please fill out a proper issue template! Otherwise this will be closed.

Sorry I am new to this. Please can you explain what a proper issue template is. Many thanks in advance.

When pressing new issue, you select a topic, and then fill out all the fields.

Tizen support is already in.

System.NullReferenceException: Object reference not set to an instance of an object.
at MediaManager.Forms.Platforms.Tizen.VideoViewRenderer.OnElementChanged(ElementChangedEventArgs`1 args)
in xamarin forms v4.7 for tizen platform


Swapchain ..._get() functions not const

I don't know whether there is a reason for this, but most of the swapchain get() functions are not marked as const.

Fixed in ab98f0639bcb76e9c2baab0cd3c07b1e9ef1366d


isort always skips init.py files

I want to sort imports in my __init__.py files, too.
In settings, __init__.py is configured to be skipped as default:(https://github.com/timothycrosley/isort/blob/develop/isort/settings.py#L45)
When defining a custom settings file like this:
[settings]
line_length=100
skip=foobar.py

isort still skips __init__.py files in addition to skips defined by myself. I cannot turn of skipping these, only by changing settings.py of isort itself.
Either __init__.py should be removed from default skip settings, or its default value should be ignored if configfile contains a skip section, too.

did this ever get fixed? in 2019 this is still a problem

@manoadamro You can add the line not_skip = __init__.py to process __init__.py. Here is an example:
https://github.com/django/django/blob/master/setup.cfg#L17

This was fixed properly in v4.3.5.
not_skip = __init__.py is no longer required.

For those of you still using an older version of isort (Murphy's law dictates I currently have to use v4.3.4!), the not_skip trick will only work if you do not have the recursive switch on. I do not know well that code, but it is using two completely different paths to check if a file should be skipped depending if that flag is on or off. If the recursive path flag is on, the config file is read, then the dictionary is update with the arguments. If you do not specify any skip argument, it looks like the default value of init.py makes its way back to the config... The workaround I found is to specify to skip an empty string, or just a space char: isort -s " ".