devcontainer with denoland/deno:alpine not working

using denoland/deno:alpine as a base image to run a devcontainer run in this error:
Error relocating /usr/local/lib/libgcc_s.so.1: _dl_find_object: symbol not found
Error relocating /usr/local/lib/libgcc_s.so.1: __cpu_indicator_init: symbol not found
Error relocating /usr/local/lib/libgcc_s.so.1: __cpu_model: symbol not found

i just ran into the same issue on denoland/deno:alpine trying to use ffmpeg.
/ # apk add ffmpeg

[...]

/ # ffmpeg
Error relocating /usr/local/lib/libgcc_s.so.1: _dl_find_object: symbol not found

works fine on the regular alpine image

I'm also getting similar errors due to switching to denoland/deno:alpine-2.0.3 from alpine:3.20.3, when using php:
PHP Warning:  PHP Startup: Unable to load dynamic library 'imagick' (tried: /usr/lib/php83/modules/imagick (Error loading shared library /usr/lib/php83/modules/imagick: No such file or directory), /usr/lib/php83/modules/imagick.so (Error relocating /usr/local/lib/libgcc_s.so.1: __cpu_indicator_init: symbol not found)) in Unknown on line 0

this is a serious issue

https://github.com/denoland/deno_docker/issues/350 is probably related

Also facing this issue.
RUN apk update && apk add --no-cache npm
RUN npm install pnpm yarn -g

 > [11/18] RUN npm install pnpm yarn -g:
0.408 Error relocating /usr/local/lib/libgcc_s.so.1: _dl_find_object: symbol not found
0.408 Error relocating /usr/local/lib/libgcc_s.so.1: __cpu_indicator_init: symbol not found
0.408 Error relocating /usr/local/lib/libgcc_s.so.1: __cpu_model: symbol not found
------
Dockerfile:27
--------------------
  25 |     ENV DENO_DIR=/usr/builds/deno-cache
  26 |     RUN apk update && apk add --no-cache npm
  27 | >>> RUN npm install pnpm yarn -g
  28 |     # DOCKERFILE-X:END file="./deno" includedBy="dockerfile_1730902581" includeType="include"
  29 |     # DOCKERFILE-X:START file="./base-after" includedBy="dockerfile_1730902581" includeType="include"
--------------------
ERROR: failed to solve: process "/bin/sh -c npm install pnpm yarn -g" did not complete successfully: exit code: 127

@Meldiron which version of the dockerfile are you using?

I'm hitting this issue too when trying to run lftp on the denoland/deno:alpine-2.1.3 image.
I was able to work around it by updating the LD_LIBRARY_PATH environment variable. It looks like the base deno alpine Docker image has LD_LIBRARY_PATH=/usr/local/lib which points to the libgcc_s.so.1 that is causing issues. On a plain alpine:3 Docker image it looks like lftp is linked to /usr/lib/libgcc_s.so.1 instead.
So by setting LD_LIBRARY_PATH=/usr/lib when running lftp I was able to run it in the Deno image without issue.
Interestingly, after updating the LD_LIBRARY_PATH deno also seemed to run fine, and when looking at the deno binary with ldd it looks like it's also failing to find some symbols in /usr/local/lib/libgcc_s.so.1 🤔
This is a bit above my pay grade so I'm not exactly sure of the repercussions, but could this potentially be resolved by not providing a custom libgcc in the base Dockerfile and instead using the one from /usr/lib (which I assume is being installed from apk)

I was having some trouble getting the VSCode Remote Server to run with Deno in the official image.  At first I had installed gcompat and gotten the VSCode server working, but that broke Deno, after reading @Tate-CC 's answer I realized I could just use the following and got both of them working.
ENV LD_LIBRARY_PATH /usr/lib:/usr/local/lib


[$500] Your location does not show full address in Distance expense

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

Version Number: 1.4.24-0
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @puneetlath
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1704809953374819
Action Performed:

create a workspace
Open workspace chat
Create a distance expense with start or stop waypoint as " your location"
OPen the receipt details

Expected Result:
Your location should show full address
Actual Result:
Does not show full address
Workaround:
unknown
Platforms:

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

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

Screenshots/Videos
Add any screenshot/video evidence

View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~0122ae0fa315e4c6b8
Upwork Job ID:<PHONE_NUMBER>821593600
Last Price Increase: 2024-01-17
Automatic offers:

esh-g | Contributor | 28117765

Proposal
from: @unicorndev-727
Please re-state the problem that we are trying to solve in this issue.
What is the root cause of that problem?
It is a new feature because we just set CONST.YOUR_LOCATION_TEXT as a address here.
https://github.com/Expensify/App/blob/7ae1ec7e74b908e6340bccaf7e42b0345d766711/src/components/AddressSearch/index.js#L348-L353
What changes do you think we should make in order to solve the problem?

We need to add a API that returns the full current address.
If the user select use your address, we should call above API in FE.

What alternative solutions did you explore?
N/A

This is the expected behavior since we set the address to Your Location when the user selects current location https://github.com/Expensify/App/blob/179d306f249993fd3ee7921d69b2c3e574ba1d62/src/components/AddressSearch/index.js#L351-L352
the way to make it show the address would be to call an external api that would take the lat and long and return the address info.

Proposal
Please re-state the problem that we are trying to solve in this issue.
For Distance Expenses, a generic message Your location  is displayed.
What is the root cause of that problem?
Here, when we use Geolocation API to fetch the current position, we explicitly set the address and name to a generic Your location text which is the root cause of this problem. As Your location text is a piece of generic information without any specifics it is not useful for reference purposes.
What changes do you think we should make in order to solve the problem?
As converting the location coordinates to a full address is not guaranteed, I would suggest that we include the location coordinate information after Your location text.
The format can be Your location,latitude,longitude or Your location[latitude][longitude] where latitude and longitude refer to the current position co-ordinates
E.g. Your Location,13.0644986,77.5702959 or Your Location[13.0644986][77.5702959] or any other agreed format
The format with comma seems to be simple to use.
The changes can be done here for address and name like this:
  address: CONST.YOUR_LOCATION_TEXT + `,`+ successData.coords.latitude + `,`+ successData.coords.longitude,
  name: CONST.YOUR_LOCATION_TEXT + `,`+ successData.coords.latitude + `,`+ successData.coords.longitude,

We may also want to prevent such locations from being added to the recent destination list.
For this, we can check if the address starts with Your location here like this:
if (waypoint?.address.startsWith(CONST.YOUR_LOCATION_TEXT)) {
    return;
}

What alternative solutions did you explore? (Optional)

@thesahindia can we get reviews today please? 🙇♂

@neil-marcellini mind confirming where we landed here?

@thesahindia @neil-marcellini @dylanexpensify

it seems this was built like this. Can you please confirm if we wanna change this and what should be the expected result?

While I also think it was built like this, I think there was an oversight of the implication on the e-receipt when it comes to Your location. I think it seems meaningless to see Your location as name and Your location as address in the e-receipt as shown in OP screenshot here. And I believe that is the issue here.
I think, at the minimum, we can set the address with the location coordinates in an agreed format which can solve this problem. This is my alternative solution in my proposal.

OK, there are still some things we want to change on the front-end, so I am going to mark this external as well.
Here is an update on the backend changes I am making:

I am now reverse geocoding "Your Location" to fill in the waypoints address field.
This will also set the waypoints name field to an empty string. This is so that the receipt doesn't show "Your location" to the admin, which is confusing because it was the requester's location. I believe that no other frontend changes are needed for this because the intention is to only show the address if one was found.
In the case that the address lookup fails, then the lat/lng will be put into the address field.

@rojiphil, let's definitely do "We may also want to prevent such locations from being added to the recent destination list."
The styling also needs to be fixed.

Would anyone like to modify their proposals to do these?

Proposal
Please re-state the issue we are trying to solve
The styling needs to be fixed.
What is the root cause?
Only a styling change (n/a)
What changes should be made to fix this?
We should set each title and subtitle like this:
const title = waypoint.name ? waypoint.name : waypoint.address;
const subtitle = waypoint.name ? waypoint.address : 'Your location'; // We can use a translation here

And then use them here:
https://github.com/Expensify/App/blob/599c005849cd065a53d35e015991b637c768f2da/src/components/DistanceEReceipt.js#L99-L100

@tgolen While adding the name field, I remember discussing this with @neil-marcellini whether we should use waypoint.address as the title if waypoint.name is not present. It was decided to keep them separate (as name is optional and address is mandatory) but maybe we can look into that again.

I think we still want to keep them separate for now. A few other things I noticed:

@esh-g your proposal is missing the piece about preventing the recent waypoints. Could you please add it?
I also noticed that the start address has the incorrect font style, so can you address that also?

@tgolen

Why would we want to prevent saving it in recent waypoint? There is no Your location text in that waypoint anymore... and it would be useful if user wants to use their last location
By 'start address' do you mean the 'Your location' text in the receipt you attached? If yes, then wouldn't that be reverse geo-coded to the actual address?

it would be useful if user wants to use their last location

That's a good point that I hadn't considered. OK, let's leave it for now.
To be more clear on my other point. I'm saying that both of these should use the same font style (and it should be the monospaced/white font style). Does that make more sense? I just want to be sure your solution covers both (maybe it does and I just didn't realize it).

Proposal
Updated with styling changes.
@tgolen
Additionally, wondering if we do not want to show name as there would always be an address to show.

Additionally, wondering if we can remove display of name in e-receipt as there would always be an address to show and the address would most likely also include the name.

Or maybe, skip name display in e-receipt if the address already includes name in its beginning. This seems even better.

@tgolen @thesahindia
The change suggested by @dukenv0307 is the same as mine. I just wanted to put this on record to avoid any confusion later.
Also, my proposal has one more suggested improvement to avoid duplicate names. Since we need to keep the same font and color for name and address, I think it's odd to see duplicates which we may want to avoid.

@Expensify/design Can you help weigh-in here on how you'd like the styles to be for the addresses?

The location address needs to be the same font and style as the location name (the monospaced font and white color).

@tgolen @shawnborton
My understanding was that we need to keep the same font, size, and color as there can be cases where name would be empty as mentioned here. In such a case, seeing the address with a smaller font size or a different color would look odd.
Or did I understand something wrong here?

Curious what the rest of the @Expensify/design thinks, but I think if we have a location name (like Expo Guadalajara in the example above) it's okay if the address portion is smaller.

Proposal
Interesting comment here. I like the idea.
Updated with Option 1: If name is empty, show address with font style as that of name

Proposal
On testing further, I noticed a similar style issue in AddressSearch which we may want to fix here.
Updated with fix for style issue in AddressSearch

Curious what the rest of the @Expensify/design thinks, but I think if we have a location name (like Expo Guadalajara in the example above) it's okay if the address portion is smaller.

I agree that it's fine for the address text to be smaller than the name. I still think it would be ideal to create some separation between them using text and supporting-text colors—but I understand if that's not in the cards right now.

I prefer the frontend solution from @esh-g because it generalizes the approach to be based on title/subtitle which I think makes the styling easier to reason about for the next engineer that comes along.
I also want to credit @dukenv0307 for the backend change for reverse-geocoding.
What I would like to propose is that the payment for this issue is split 50/50 with $250 going to @dukenv0307 and $250 for the frontend solution.
@thesahindia @dylanexpensify Are you OK with this arrangement?

That works for me 👍

What I would like to propose is that the payment for this issue is split 50/50 with $250 going to @dukenv0307 and $250 for the frontend solution.

I understand that @dukenv0307 suggested the reverse geocoding, but it is reasonably obvious as we need the full address from the coordinates and using the API was the only way we can do that. Here is an issue in which the same happened to me: https://github.com/Expensify/App/issues/14493#issuecomment-1451109437
Although I'm not completely opposed to this arrangement if you think their contribution was important, then we can go ahead with this...

I understand we can't be consistent 100% of the time, but I do think this arrangement is fair. Thanks! Assigning @esh-g for the style changes.

The backend changes here were only applied to CreateDistanceRequest. The issue still persist when editing money request i.e. command UpdateMoneyRequestDistance

The BE changes caused a regression https://github.com/Expensify/App/issues/35245

cc @tgolen

You're right, I forgot about the update flow 🤦
I created this GH to track it so I can get that added this week.

payment today! @thesahindia to do checklist!

gentle bump @dylanexpensify

Payment summary:

contributor: @esh-g $500
contributor+: @dukenv0307 $250
contributor+: @thesahindia $250

Please accept offer or request!

@dukenv0307 will you apply when you can so I can pay you the money 🤑 !

@thesahindia coming from this comment it sounds like 50/50 split between you both cc @tgolen to confirm

Yeah, we need to do the 50/50 split on this one.

Ahhhh I see where I got confused! My apologies @thesahindia! Will payout 250 w/250 bonus to equal 500

@esh-g will request a refund of $250

Updated payment summary

@thesahindia sent invite to job

@dylanexpensify Issued the refund

ty both!

$500 approved for @thesahindia based on this summary.

Apologies @dukenv0307! Idk why I didn't get these notifications! Paid!


audio files with m4a extension don't play

updated example illustrating bug here: https://github.com/ultrasaurus/webgenr/pull/30
repro steps (using npm local-web-server):

from root of repo, build by running: ./examples/nested-files/build.sh
cd _website && ws

I thought it was a large audio file (which is still good to have as a test case, I think), but turns out that .m4a files were handled incorrectly and I don't think any of those files would have played

reopened: https://github.com/ultrasaurus/webgenr/issues/26 -- need to think about whether this new info changes our choice of crates (prolly not, but may be that additional refactoring is warranted)


[enhancement]: improve profile and artefacts page

improve the user interface and add responsiveness on the page

Great...
Go ahead, I am looking forward to your work.


Auto Message on successfully Merged PRs [BOT]

This Automation will keep the contributors motivated
Essential for this project
Solution
Using GitHub Action 1 .yml file will be pushed with all changed
@rish-singhal Please assign me this issue

@tarun26091999 @Rohan27s @rudrakshi99


Correct Teams deep-link web link format

The deep-link format for Teams web didn't agree with the examples (and appeared to be the format for Teams desktop/mobile).

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/build-and-test/deep-link-workflow.md
94
12
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/build-and-test/deep-link-workflow.md
94
12
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.


Rename repository name to <mapswipe.org>

Amateur changed it and broke the site. Obviously not as simple as just changing the name.

Created new repo so that we can point to docs folder. Now called website.


Upgrade to Vite 3

Announcement blog post: https://vitejs.dev/blog/announcing-vite3.html
Some changes noticeable for SvelteKit:

relative base support (https://github.com/sveltejs/kit/issues/595)
default port changed to 5173 in development mode
fixStacktrace now defaults to false
We can now set appType: 'custom' so that HTML middlewares are not added and we no longer have to remove many of them

v3 also added a new hook configurePreviewServer that has been backported to 2.9 and already leveraged in SvelteKit master which allowed us to switch to the vite CLI

@benmccann Does this allow debugging using IDE's now? For reference: https://github.com/vitejs/vite/pull/3928

I doubt it. That PR was closed without being merged

@benmccann looks like @Rich-Harris is waiting for reply on his question

I've updated the description to be clearer

The tests that are failing are the new create-svelte tests, which npm install the next version of SvelteKit instead of workspace:* (because they're instantiating a new project in order to check it). Because of that, there's a dependency mismatch that should resolve itself as soon as this PR is merged.
Not sure if we should come up with some tricksy workaround in the meantime, but I have a hunch that it won't be the last time we experience this issue in some form

i think this might work

[RON HOWARD VOICE] it did not work


Feature request: PPO early stopping, important for training stability

Hi TRL contributors,
Thanks a lot for creating this nice library.
While using TRL, I realised that an important feature is still missing, that's the early stopping during a PPO step.
Without this feature, the optimisation is prone to KL/loss spikes such as those mentioned in #101 .
In my experiments, I found this issue is alleviated through reducing the default num PPO epochs.
This feature is already implemented in the OpenAI official PPO and AllenAI RL4LMs.
Looking forward to your feedback.
Kind regards,
Shaojie

@lvwerra @lewtun  this might improve the issues we were discussing yesterday, I can add this feature if you like?

Sounds good! Yes, I agree this would be an easy and useful feature to add.

Thanks @edbeeching @lvwerra for your quick responses. Looking forward to the improvement.


Transpiling to JavaScript causes problems

Many users don't have Java on their machines anymore. Installing it is slow and confusing and a major blocker to adoption. Currently Closure Compiler uses GWT to transpile to a native JS distro.

GWT unicode support https://github.com/google/closure-compiler/issues/2383
Node process runs out of heap memory [citation needed]
Not 100% feature compatible [citation needed]

Aside from these bugs, supporting compiling to JS is an unnecessary distraction for the core team. Will you chase down the long tail of compatibility issues? What if we just stopped doing this?
Users may also want to use Bazel. (Angular has announced at ngConf day3 keynote that we'll push this.) So we still need a way to get a Java runtime onto their machines.
Bazel is about to release their solution to this problem:
https://github.com/bazelbuild/bazel/issues/1666
The approach:

ship an OpenJDK JRE to npm (for the three major architectures, windows, darwin x64, linux x64)
either statically link it into the google-closure-compiler package or make it a separate peerDependency
closure compiler binary runs Java without the user needing to know about it.

This is a potentially good idea, if the machinery is smart enough to use an already present JRE. Other than the folks selling hard drives, noone wants to expand the NPM install-another-copy-of-everything-in-every-package approach to installing another JRE for every Angular project on a dev's machine(!).
This approach is an interesting symmetry to what folks are doing from the Java side of things - a Maven package (Maven plugin) that installs a local Node for gulp/grunt/etc based sub-project builds.
https://github.com/eirslett/frontend-maven-plugin
It's not clear to me whether Maven or NPM deserves the topmost position as the package manager / ecosystem which installs a local copy of the other as needed. I imagine by 2018 there will be projects which install multiple nested copies of various JRE and Node versions using these mechanisms!

We're not really spending time on the JS version. We have it marked as "experimental" or something along those lines, and probably will keep it that way indefinitely. I think it makes sense for Angular to recommend to its users Bazel plus the Java version of the compiler.

@MatrixFrog I sat with a user yesterday at ngConf and spent the majority of the time installing Java over conference wifi. We'll recommend the Java version of the compiler, but still need to axe the Java installation step.
Just because they have Bazel on the machine doesn't give us a good way of running Closure (unless we do ../../../path/to/bazel/external/location/of/jre/java closure.jar
Why keep an "experimental" broken thing laying around? You're still getting new issues on the closure-compiler-js repo. We could resolve all those issues if closure-compiler-js used Java under the covers.

The JS version should work for most use cases so I don't think it's broken. Getting the Bazel integration working better and recommending it over the JS version is an orthogonal issue.

I would object to your characterization as "broken". There are some bugs. Some of those bugs will be a deal-breaker for some users. Most of them will probably get fixed eventually; the "experimental" labels serves primarily as a signal that they are not a priority for us at this time.

@alexeagle due to lack of resources, we can't spend time on the JS version for the next few months.

First off let me say that I'm very excited about the public Bazel support. Using bazel with a front-end  package has seemed like an incredibly powerful tool - but one that was a secondary thought.
As for using the Java version of the compiler - that is also the correct choice (though I fear it may be unpopular as there is a large population of NO JAVA ON MY MACHINE devs).
However, the idea of installing a JVM via npm is absolutely not a good idea. Prior to me creating the official NPM distribution of closure-compiler, one of the most popular plugins installed a JVM along with it. The experience was nothing but horrible. Bloated downloads and long post-install scripts are all part of what makes front-end developers dislike Java. In addition, if you aren't shipping some kind of auto-update facility, then it's just asking to create security issues.
For windows and Mac, the Java install is very easy and painless. Yes it's an extra step, but I've never had a developer have problems. For other unix based systems, it is admittedly a bit more work - but that's a good description for those OS's in the first place. Time would be much better spent using nailgun or drip to prevent incurring the JVM startup penalty for each small compile job.
As stated, the JS version of the compiler isn't really maintained by the closure-compiler team. And I can definitely say it's presence doesn't impede development on the java version in any way (though I do share your concerns about the gwt compilation process).
If you would like to help add a postinstall script to the java distribution to check for a compatible JRE and give install instructions if missing, I think that would be great. Feel free to file an issue at https://github.com/google/closure-compiler-npm and we can see what we can get done.
I'm closing this particular issue however as it's clear that the JS version isn't the destraction that has been assumed.


Add initial Windows E2E FIPS package test/support

What does this PR do?
Add E2E test that installs the Windows FIPS Agent and ensures the GOFIPS=1 triggers a panic when the system FIPS mode is disabled.
follow-up to https://github.com/DataDog/datadog-agent/pull/25520
Motivation
https://datadoghq.atlassian.net/browse/WINA-1212
Describe how you validated your changes

Possible Drawbacks / Trade-offs
Additional Notes

There will be a future PR to add support for installing the FIPS Agent via test-infra-definitions

/merge


HDX-9781 Add tables which reflect views

This PR implements a set of tables which replicate a subset of the views currently being used. The views replicated are those which do not simply replicate an existing table. The strategy to do this was to write a fake test which output to stdout the sqlalchemy table class based on the view (tests/test_fake_for_generating_tables_from_views.py).
The columns to be indexed are provided explicitly and tested, along with a test that the columns in the new table match those in the view (see, for example, tests/test_admin1.py).
20 files are changed because there are nine adjusted db_*.py files, and nine test_*.py files. There is an update to conftest.py to provide two new test fixtures and the pipeline definition file (.github/workflows/run-python-tests.yaml) has incidently been updated to remove the node.js depreciation warning.
It should be straightforward to update these definitions when the schema changes.

admin1_view
admin2_view
food_security_view
humanitarian_needs_view
national_risk_view
operational_presence_view
org_view
population_view
resource_view

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

214 of 214 (100.0%)  changed or added relevant lines in 8 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.4%) to 99.34%

Totals

Change from base Build<PHONE_NUMBER>:
0.4%

Covered Lines:
602

Relevant Lines:
606

💛  - Coveralls

Tests currently broken because hdx-python-database was updated to remove build_view and replace with prepare_view, build_view is used heavily in testing. I assume this must be on some branch.

@turnerm - I think this one is ready to merge. There are further views as tables to add, and we probably need to confirm what we want in terms of primary_keys and indexes in these tables but I'll make these in a separate PR.


Small fix on yaml templates.

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

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests-v1alpha3.sh
c9325bd47be085932bd79caeb4e132ffef80a669
link
/test e2e-bookInfo-envoyv2-v1alpha3

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

@myidpt: PR needs rebase.

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


Node numbering is inconsistent

Discussed in https://github.com/ansys/pymapdl/discussions/3119

Originally posted by YMDONG23 May 23, 2024
hello :)
When I use the BEAM188 unit to calculate, the node number displayed in the eplot window is not the same as the node number when vtk=False. What is the reason?
If you could discuss with me, thank you very much for your help！

Code to replicate this issue in: https://github.com/ansys/pymapdl/discussions/3119?notification_referrer_id=NT_kwDOAa2IUbQxMDc3OTQwNTU0MToyODE0OTg0MQ#discussioncomment-9571309

I think the error comes when plotting the labels. The node IDs seems correct.

This issue seems to happen not only on element numbering, but with general geometrical entities. Here is a minimal example creating 3 keypoints and connecting the first two with a line:
from ansys.mapdl.core import launch_mapdl

# Launch MAPDL instance
mapdl = launch_mapdl()

# Enter pre-processing mode
mapdl.prep7()

# Create keypoints 3 keypoints
mapdl.k(1, 0, 0, 0)
mapdl.k(2, 1, 0, 0)
mapdl.k(3, 1, 1, 0)

# Create line connecting keypoints 1 and 2
mapdl.l(1, 2)

# Plot the geometry
mapdl.lplot(show_line_numbering=False, show_keypoint_numbering=True, color_lines=True)

The output shows keypoint 1 connected to keypoint 3 instead of 2:

This is an import issue, specially when setting boundary conditions and/or mesh refinement over complex geometries.

There is a problem with the indexes. A fix is in progress.

Is this resolved? I plot my nodes and get a node numbered zero, which can't happen.

that's strange.....  I will check it.


Escaping markdown being passed in to parseTextEntities?

So I'm using tdlibjson and attempting to send text that has been parsed with parseTextEntities. The problem is, when text needs to be escaped before being passed in to parseTextEntities it seems to not work. For instance, when attempting to create an inline mention of a user with special characters in their name:
Joey [*NO PMs*] Smalls

This text should be escaped before being passed in to an inline mention, no? So the inline mention should look like this:
[Joey \[\*NO PMs\*\] Smalls](tg://user?id=1234567890)

tdlib seems to be interpreting the slashes literally though. Is there anything I can do about that?

TextParseMode type is Telegram Bot API parse mode and it is completely described in the Bot API documentation: https://core.telegram.org/bots/api#formatting-options.
In this particular case you need to remove all ']' chatacters from the name or switch to MarkdownV2.

So it's not possible to just escape the ']' characters? I guess I could probably just substitute them with a similar looking character.

From https://core.telegram.org/bots/api#markdown-style: "Escaping inside entities is not allowed".

Gotcha, alright then. Thanks for the help :)


Steam Grid artwork not showing

While the tool does correctly create the custom games, it doesn't seem to set the artwork.

The artwork is, however, correctly copied from the grid folder into the grid folder located within the steam userdata folder.

I'm not sure if it's relevant, but I've used this tool before and it worked correctly, though that was a couple months ago I think. Since then I've had to install the Touhou games. In preparation for running this tool again, I removed both the custom games in Steam and the artwork in the userdata folder. Maybe something is left over in Steam which is preventing setting the artwork?

It seems like Valve broke something in a recent update, I can confirm this part of the functionality no longer works.
Unfortunately, generating the appID for non-Steam games is fiddly and there's no public algorithm Valve provides for this, the way I was doing it was a well-known hack, but it seems like they changed how it works.
I failed to figure out what the hell the new way of doing things is, so for now I disabled this functionality. I'll dig around a little more to see if I can fix it properly, and if anyone else has any idea what changed and how to make it work again, please feel free to send a PR.
I'm keeping this issue open and I'll try to do something about it, but keep in mind that there's a chance it might never be fixed.

There seems to be some relevant code here, with "old" and "new" app IDs. Seems like they're using the new format and creating symlinks from the old one for "backwards compatibility" (???).
strcpy(parsingAppid, exeStartChar);
strcat(parsingAppid, nameStartChar);
appid_old = crcFast(parsingAppid, strlen(parsingAppid));
appid = appid_old;
appid = (((appid | 0x80000000) << 32) | 0x02000000) >> 32;
appid_old = (((appid_old | 0x80000000) << 32) | 0x02000000);

However, I have attemped to use this formula and it failed to work. Not entirely sure why -- perhaps the algorithm used for their crcFast() isn't actually CRC-32? Could there be NUL bytes inside this string which are messing things up? Will have to dig further.

Slight chance the problem isn't even with the formula -- it seems that shortcuts.vdf has gotten a bunch of new weird properties that may be affecting some stuff. Unlikely, since the problem is with the artwork and not the shortcut itself, but who knows.

Another idea: maybe add artwork while Steam is running, perhaps there's some indexing thing? SGDBoop does that...

I'm giving up on this issue for now. I've tried every fix I could think of or conjure up online, but nothing seems to work. I'll try to look again in a few weeks to see if some other similar software runs into the problem and comes up with a fix, or perhaps if VALVe fixes this on their end. But until then, this will remain broken. Sorry.


Feature - All Fours Calypso

Implement 'All Fours' variant. ft,tr + must beat trump lead rank.

[x] Legal card rules
[x] Trick-winner rules
[x] Renounce indicator logic
[x] Indication in the display
[x] Warning message on illegal play
[x] Guard for in-progress games
[x] Review stats?

Needs more testing. In particular:

[x] checking the renounce indicators!
[x] check migration

Think we're there, just need to find a convenient time to deploy where I can follow-up in case it's a bit skew-whiff.


[Blocked] Add health endpoint

Purpose
Adding health endpoint
Changes
Add health endpoint
Checklist

[ ] My code follows the style of this project.
[ ] The code compiles without warnings.
[ ] I have performed a self-review of the changes.
[ ] I have documented my code, in particular the intent of the
hard-to-understand areas.
[ ] (If necessary) I have updated the CHANGELOG.

Blocked related to https://linear.app/concordium/issue/CCD-114/add-health-check-endpoint#comment-4736ced0


Remove body styles

Investigate why the below styles are being placed on body (and from where).

@andrewdamelio Are you gonna prioritize this?

status / does this matter?

not a big deal IMO @joeykrug

@JohnDanz did you make any progress on this? Can we close this issue


Issue with using Laravel Elixir and $path in CdnFacade.php

I've noticed a strange error using Laravel Elixir in v1.1.2.
On my production website, when I reference my CSS file in Elixir like so:
<link rel="stylesheet" href="{{ Cdn::Asset(elixir('css/all.css')) }}">

I get the following error:
Failed to load resource:
https://mybucket.s3.amazonaws.com/public/build//css/all-a6102320.css Failed to load
the server responded with a status of 403 (Forbidden)

I've deduced it's because of the / in the following code in the CdnFacade.php file:
$path = str_replace(
            "build",
            "build/" . $this->configurations['providers']['aws']['s3']['cloudfront']['version'],
            $path
        );

SHA 97a3cfd586b922469353696c0f2ac70ec97441a6


[Do Not Merge] Experiment disabling ASTScope lookup by default

Do not merge

@swift-ci Please test

@swift-ci Please Test Source Compatibility

Build failed
Swift Test Linux Platform
Git Sha -<PHONE_NUMBER>af33cd6283e430605ff5f5d23603bd

Build failed
Swift Test OS X Platform
Git Sha -<PHONE_NUMBER>af33cd6283e430605ff5f5d23603bd

@swift-ci Please test

What's your goal here?

Can one of the admins verify this patch?

@DougGregor There's a bug in code completion where unqualified lookups doesn't work in fast-completion. Since ASTScope is not enabled for code-completion, we need to modify legacy UnqualifiedLookup code. I just wanted to make sure, it still works perfectly. When I have a fix for the completion bug, I will re-use this PR to check that the fix is also good for compilations.

@swift-ci Please test

@swift-ci Please Test Source Compatibility

Build failed
Swift Test Linux Platform
Git Sha -<PHONE_NUMBER>af33cd6283e430605ff5f5d23603bd

Build failed
Swift Test OS X Platform
Git Sha -<PHONE_NUMBER>af33cd6283e430605ff5f5d23603bd


Sky3ds

May i using sky3ds as the cart while modding a console? it's will same as using the cartridge?
Like put the cubic ninja inside then act as the cartridge then boots the homebrew...
Plan to buy a sky3ds to mod the ver10.7 console....

You could do that, but on 10.7 it would probably be cheaper just to buy Cubic Ninja or another exploit game. Sky3DS is pretty expensive, and you won't need any of its features after completing the guide. Your options are pretty much get Cubic Ninja, Freakyforms, or Ocarina of Time 3D and a Datel Powersaves.

Yes you can use the sky3ds

Because if i use the sky3ds, i can put the diff rent region inside to mod different region console right.
No need to buy 3 cubic ninja, haha

Well, if you mod many different consoles, yeah get a sky3ds.

I can use every type of sky3ds? because as i saw online, there got alot of version....lol

I suppose you could, but I'm not about to officially recommend piracy...


nuc and rpi-clone

Hello,
Is it possible to use rpi-clone with à NUC running debian 10 and to restore it after à crash ?
If yes, how ?
Thanks for your help
Cheers
Michel

Did you try?


Update zio-sbt-ci, zio-sbt-ecosystem, ... to 0.4.0-alpha.26

About this PR
📦 Updates

dev.zio:zio-sbt-ci
dev.zio:zio-sbt-ecosystem
dev.zio:zio-sbt-website

from 0.4.0-alpha.22 to 0.4.0-alpha.26
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "dev.zio" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "dev.zio" }
}]

labels: sbt-plugin-update, early-semver-pre-release, semver-spec-pre-release, commit-count:1

Superseded by #452.


[WIP] Fix race in aec_miner process between mining and block posting

Change for testnet. Part of PT-152968563.

Preparing new PR. (Testing it locally.)


time.Time values are scanned in the local timezone

See sqlite3.go#L545 for example.
I was wondering why this choice was made ? It would seem more consistent to always scan to UTC, and let the user change the timezone as needed.

go-sqlite3 should work as same as another RDBMS (ex. pg). If go-sqlite3 returns UTC, all of ORMs should have conversion for go-sqlite3. I think.

That's a point, but in the other hand, the convention for SQL-stored dates is to always store them in UTC and let the application do the timezone shifting as necessary.

@porjo
https://github.com/mattn/go-sqlite3/commit/0b05acc293a940d3bfedf2df5fba12c49ac9ec35
Do you have any opinion?

Sorry, I'm a little confused about this myself. According to sqlite3 doco, datetimes stored as TEXT should follow ISO8601. According to Wikipedia for ISO8601, datetime without timezone designator should be read as local time. Go-sqlite3 does not currently do this however, reading them as UTC...
As for dates stored as INTEGER, these will always are always UTC while in integer form, so it would make sense for these to remain as UTC when converted to a Go time value.

The question is a mess, that sure.
In my opinion, the time.Time scanned should be returned to the
end-user as an UTC time. But it doesn't prevent the driver to implement
correctly ISO 8601, that is to detect whether the timezone is noted in
the date, and consider it as local timezone if not. Then shift it to UTC
before returning. That way both the norm and the convention are
observed, and the behavior of the driver is consistent.
Maybe with a mention of this particular working on the driver's page, so
users are made aware of this point.

@porjo What go-sqlite3 should do, do you think?

I added loc=XXX parameter to handle timezone.
4c5c4e526100f23b17fda84d39a8109cfec00118
If someone want to store datetime as local string, loc is required.


change after review

@polesye please review

@den99f Where can I find commit thet reverts your changes in edx-platform?


Update specarray.py

Hey I love the package, i've been looking for something in python to do this for a while now.  I thought since it seemed like the package was based around this spectral separation it would be nice to have the reference in place, I added as a reference in the docstring.  If i have the reference wrong, please forgive me!

Thanks for the reference @SBFRF , I'm merging your pull request and this will be available in pypi with the next release!


missing subckt in cdls in the pdk

To run spare_logic_block lvs I am missing these cells in the cdl:
ppolyf_u_1k_6p0
nmos_6p0
pmos_6p0
mim_2p0fF

for calibre - no longer required.


Add Progress Indicators

Added Progress Indicators:

Linear Progress
Circular Progress

All with determinate and indeterminate mode.
Issue #592

@castrolol General comment: I mean this in the most constructive way; my goal is not to offend you. Before starting work on a feature or resolution of an issue, be sure no one else is already working that feature/issue. This is the second time someone else has worked the same effort; now my development time is essentially wasted. This can be quite frustrating/irritating to some individuals and may turn them away from the open source community (or from supporting a repo) and I ask that you confirm no one has explicitly indicated s/he is working a feature/issue. That being said, your overall approach is similar to the one that I took.

@jkruder I apologize for doing it that way, I'm new on github and still do not have this expertise. I'll pay attention to it, I saw that you were working on it but as I was about 12 days believed had redirected their efforts. I will try to be more communicative. Thank you: D

@castrolol Thanks!

@jkruder  I'll do it, I believe it is possible with JS, but I'm still worried the complexity of code reading and performance. Today I will send the adjustments. I wanted to work in the AutoComplete but I saw the need for progress bar to stay nice.

@hai-cea @jkruder I made the changes as we talked, the new way was more simple. In the circular I used SVG.

@castrolol It looks like you're still requiring ./styles/animations in your components.

@hai-cea sorry for the mistake, fixed!

@castrolol Can you sync with master please?

@hai-cea it's done!

@castrolol Just a friendly tip, but when syncing with master you should be rebasing instead of merging.  I'm new to github, I work with TFS and confuse me by the similarity of the terms. I'll update me about it

Thanks @castrolol :+1:


Server Side Tracking silently fails

It seems that if there is an error when sending the Server Side Tracking request, the error is silently ignored.
After one painful debugging session later I would suggest that the the error should be at least logged so that it would be visible in Traefiks logs.
It would not hurt if there would also debug logging in other critical places. It would be a way easier to understand what is wrong with the configuration.

Thank you for the issue, due to time constraints I cannot work on this plugin right now but want to do so in the future!


explaining ethics principles in new heading

It would be nice to start a new heading to explain the ethics principles for beginners to understand in depth what each of those principles mean. Ethics, I believe, is underrepresented in formal academia and we could explain each of the points in 'ethics principles' so that more clarity is imparted to the visitors.

There is the principles.md file where you could expand upon the elements with descriptions and references. A first step would be matching the principles in the readme.md with those in the principles.md file (see PR 39 and issue 34 for details).
You could also build a table of contents in the readme.md that better directs people to its contents and the other contents in the ethics-resources repo.

Great! I shall get started.

Hey Joe! I apologize for not being regular. Exams are coming up. I want the org to know that I am on it and planning the process and time.

No worries. I'm wrapping up my semester as well. Just let me know if you need any assistance when you pick things back up.

sure thing.


Flaky test: TestAPIRepoMigrate

https://github.com/go-gitea/gitea/actions/runs/4927752928/jobs/8805178261
    api_repo_test.go:360:
        	Error Trace:	/home/runner/work/gitea/gitea/tests/integration/api_repo_test.go:360
        	Error:      	unexpected error '%v' on url '%s'
        	Test:       	TestAPIRepoMigrate
        	Messages:   	Migration failed: Clone: exit status 128 - fatal: unable to access 'https://github.com/go-gitea/test_repo.git/': The requested URL returned error: 503
        	            	.%!(EXTRA string=https://github.com/go-gitea/test_repo.git)

At that time, GitHub is down ..........

Generally I think we should not have external dependencies in our tests so they work offline too.
Otherwise, adding some failed test retries in gotestsum may help.

Right, so I guess to realistically test GH, it has to be GH. Might just go with the retry variant.

Closing for now as it is rather unactionable.


return node in pgn::from_board

@flok99 I think you need to rebase your branch to master.

@flok99 I think you need to rebase your branch to master.

Ttried that. Fails dramatically.


Testing: Ingest Maya userSetup

Changelog Description
Suggesting to ingest userSetup.py startup script for easier collaboration and transparency of testing.
Testing notes:

Run Maya testing .\tools\openpype_console.bat runtests C:\Users\tokejepsen\OpenPype\tests\integration\hosts\maya\test_publish_in_maya.py
Comment out tests\integration\hosts\maya\lib.py line 42 and validate Maya only launches.

Split from https://github.com/ynput/OpenPype/pull/5644

To be honest, I don't see a benefit to moving this from startup script inside (I tottaly see benefit of setting up pyblish, I am guessing this could be done for all DCC in test classes).
I tried to push most of the configuration to one place and chose test zip files, we could argue if that was good choice. If we would be moving out some parts, suddenly one needs to check multiple locations for configurations.
How will this behave, if I would like to have different startup scripts per test class?
I think that bringing in all the dumps, expected files from testing zip files will be unmanageable (unless we separate tests into different repo). And we had similar discussion before this was implemented and separate zip files with resources was requirement.
But I am open to wide discussion.

I tried to push most of the configuration to one place and chose test zip files, we could argue if that was good choice. If we would be moving out some parts, suddenly one needs to check multiple locations for configurations.

This PR is a split from https://github.com/ynput/OpenPype/pull/5644, where I've suggested to ingest all input and expected files. This would make the test workflow easier than the current setup, since its all in one place.

How will this behave, if I would like to have different startup scripts per test class?

We can setup the tests to define their own startup script location.

I think that bringing in all the dumps, expected files from testing zip files will be unmanageable (unless we separate tests into different repo). And we had similar discussion before this was implemented and separate zip files with resources was requirement.

My issue with having the input and expected files in a separate GDrive storage, is to do with ease of use and transparency for collaboration. Currently for an external collaborator there is no way of viewing or updating the files on GDrive.
Ingesting the files into the repository will make it easier to collaborate since we can make PRs and all data is transparent to the community.

How will this behave, if I would like to have different startup scripts per test class?

Usually test suites define "tests" with their setUp() and tearDown(). You run the host, run the tests.
It's up to the tests to ensure there setup and teardown ensure a clean slate.
So the this 'startup' logic should actually be along the lines of:
Pseudocode
from tests import run_tests
run_tests()

Which in essence runs all found tests in the current test suite:
with host_global_setup():
    for test in find_tests():
        try:
            test.setup()
            test.run()
         finally:
            test.teardown()

Where the host_global_setup could e.g. be doing a teardown at the end of the context, e.g. for maya forcing a quit to avoid exit errors for mayapy. For example for maya it could be:
import contextlib

@contextlib.contextmanager
def host_global_setup():
    setup_logging(DEBUG)
    try:
        yield
    finally:
        cmds.quit(force=True)

Then for any host we can define any test suite (usually it's just tests in a particular folder). Where tests could be:
class TestWithZip(ZipTest):
    def setup(self):
         self.unpack(url, destination)

    def run(self):
        # do whatever the test should

    def teardown(self):
         self.remove_unpacked()
         self.remove(published_file_x)

The tests themselves could define whether they should be loading tests from zips or whether they are just local tests. A test could be as trivial as testing whether a particular Maya quirk is still present, e.g. if getAttr for a particular attribute type still returns a list. Another could be downloading a huge (legacy) maya scene and just trigger "publish" to confirm backward compatibility is still in place.

Adding @antirotor to discussion. Main discussion point here https://github.com/ynput/OpenPype/pull/5734#issuecomment-1759276043
tl;dr: Should be ingest .zip test files inside to OP repo? Eg. ingest expected, input. Currently it is about 10MB of data, could be  made a bit smaller with decreasing of size of expected files (that would limit possibility of comparing by content, now it is only comparing by presence.)

By the way - just to mark my input: I'm currently not against having some files be based on data from the web - as long as users are also able to freely download them easily outside of the tests and that it's basically only done for files that absolutely require it. The (test) repo should not contain 100s of MBs but 10 MB of source files should be fine maybe?
The fact that test files should remain quite static (for sake of backwards compatibility) is an argument too so them being somewhat static on a google drive shouldn't be too big of a hurdle since they should not need to update that daily anyway.
Nonetheless - with the current state of testing I personally have no idea how I could even contribute to tests. That's either lack of documentation but maybe also obscurity due to the zips.

By the way - just to mark my input: I'm currently not against having some files be based on data from the web - as long as users are also able to freely download them easily outside of the tests and that it's basically only done for files that absolutely require it. The (test) repo should not contain 100s of MBs but 10 MB of source files should be fine maybe?

This is my argument as well. The current test files are on a GDrive which is not accessible. I think we should start with a suite of source files with a small data footprint, which we can run fast and often.
If the source files start to become 100s of MBs, those files might need some procedural generated content rather than user based.

The fact that test files should remain quite static (for sake of backwards compatibility) is an argument too so them being somewhat static on a google drive shouldn't be too big of a hurdle since they should not need to update that daily anyway.

True when you have an established test suite, but it is not at the moment so better to get it all ingested so we can iterate faster on the test suite.

Nonetheless - with the current state of testing I personally have no idea how I could even contribute to tests. That's either lack of documentation but maybe also obscurity due to the zips.

Yup, had the same issue. Without access to the source files, no one can run tests. If we open up the source files by ingesting into the repository we can iterate better.

I guess this all comes with decision we haven't yet made - when we'll split the OpenPype repo into individual addon repos, what will happen with tests?
Logically, every DCC integration addon should have it's own tests and with the test the testing data. But in most cases, the testing data can be shared between different integration addons - you can run test on the same alembic file in maya/nuke/houdini...
So what about having those "shared" in separate addon?

So what about having those "shared" in separate addon?

Is this maybe planning too much ahead?
I personally dont see the need for sharing testing data between hosts atm. Better to get it all up and running, for testing fast and often. Then its easier to refactor the testing data to be shared.

I personally dont see the need for sharing testing data between hosts atm. Better to get it all up and running, for testing fast and often. Then its easier to refactor the testing data to be shared.

Then it makes sense to include it in the repo instead of keeping it on the GDrive. But it was somewhat limited on GH on non-enterprise accounts and git lfs can be real mess.

But it was somewhat limited on GH on non-enterprise accounts and git lfs can be real mess.

Yeah, I agree that having massive source files to test on will be a problem.
I think we can do without large source files for now, while building the testing suite. Later when needing to test on large source files, I think we can work out a solution. Easier to work on data issues with an established test suite.

Easier to work on data issues with an established test suite.

Agree, as a first step, it would be enough to even work on something procedurally generated, even though it won't work later in some test and it might be lengthy process to generate them each time you run testing suite. But with the current state of testing, we need at least something to work with easily.

So what about having those "shared" in separate addon?

Actually - I think if whatever the Google Drive is now could be a separate openpype_test_files or whatever repository that'd still allow us to have artists get more control on it. Not required as first separation I'd say but I wouldn't be bothered to much if the tests were a repo of their own (might be hard to keep them synced up somehow maybe?)

(might be hard to keep them synced up somehow maybe?)

yeah, think that would be tricky. Especially if you want it running on PRs and merges.


How to make the CF API endpoint to be accessed from outside

Hello, all
I tried to deploy CF to AWS based on this documentation.
After BOSH CLI is installed, I tried to add some environment variables like:
export BOSH_AWS_ACCESS_KEY_ID=AKIAID5ROSDFQDMDLSA
export BOSH_AWS_SECRET_ACCESS_KEY=z0dfTG6zjSFSXSDFdJaaVGbjWr1xOsLoPPWqDN1i2H
export BOSH_LITE_SECURITY_GROUP=sg-f0be7
export BOSH_LITE_SUBNET_ID=subnet-a41dadc
export BOSH_LITE_PRIVATE_KEY=/home/ubuntu/.ssh/id_rsa
export BOSH_LITE_KEYPAIR=bosh
export BOSH_LITE_NAME=vagrant
With these settings and followed the steps I can have CF installed on AWS VM.
But I got a problem to access the CF API endpoint.
In a local environment, we use
cf login -a api.bosh-lite.com -u admin -p admin --skip-ssl-validation &&
cf enable-feature-flag diego_docker
Here api.bosh-lite.com is a internal IP address like 10.244.xx.xx
But for this AWS CF, how should I make it accessible to outside?
If I login the BOSH lite VM I can see the CF works there.
From some documentation, it's said we need to access it via
deploying BOSH-Lite to AWS, use https://api.BOSH-LITE-PUBLIC-IP.xip.io instead, how should I set it?
If the environment is there already, is there a way to change it to make it accessible?

Hi, @StanleyShen,
You should be able to follow the instructions at http://docs.cloudfoundry.org/deploying/boshlite/ to configure your CF deployment manifest to use BOSH-LITE-PUBLIC-IP.xip.io as the system domain, and to derive the other publicly routable CF component domains from that. Once the CF manifest is generated with the correct domains, the Diego manifest should require no additional configuration. If that doesn't work correctly, please let us know!
The instructions give in the diego-release README are intended to be verbatim only for a local BOSH-Lite instance. I'll amend the documentation soon to clarify that.
Thanks,
Eric, CF Runtime Diego PM

Oh, by the way, those aren't your real AWS credentials, right?

Thanks for replying.
I followed the instructions mentioned by you, but I still cannot access the CF API endpoint.
do I need to change the CF configuration file for the domain value?
Or if there is some environment variables for it, is it BOSH_VPC_DOMAIN ?
They are not really AWS credentials.

Hi, @StanleyShen,
Yes, the 'Create a Deployment Manifest Stub for AWS' section of the instructions mentions supplying an additional stub to the CF manifest-generation script with properties.domain set to the intended system domain (in your case, <BOSH-LITE-PUBLIC-IP>.xip.io). You should then be able to redeploy CF with the manifest that contains the correct domain for your BOSH-Lite deployment.
Phew, glad those AWS credentials weren't real! :)
Best,
Eric

Hello, Eric
I created the stub file and set the domain value to .xip.io
After re-generating the cf.yml, I can see the domains are changed to .xip.io related.
for example:
srv_api_uri: https://api.<IP_ADDRESS>.xip.io
And I reployed CF again.
But in my local I still cannot access the CF API endpoint.
I tried to login the BOSH LITE VM,
I can see "cf login -a api.bosh-lite.com -u admin -p admin --skip-ssl-validation" is not working for 404 errors, which is a right behavior.
And I also cannot use "cf login -a https://api.BOSH-LITE-PUBLIC-IP.xip.io -u admin -p admin  --skip-ssl-validation" on that VM.
I have opened port 443, 80 etc in security group already.
The IP of the BOSH lite is not a pre-allocated one, does it matter?
+------------------------------------+---------+---------------+--------------+
| Job/index                          | State   | Resource Pool | IPs          |
+------------------------------------+---------+---------------+--------------+
| api_z1/0                           | running | large_z1      | <IP_ADDRESS> |
| consul_z1/0                        | running | small_z1      | <IP_ADDRESS>  |
| doppler_z1/0                       | running | medium_z1     | <IP_ADDRESS> |
| etcd_z1/0                          | running | medium_z1     | <IP_ADDRESS>  |
| ha_proxy_z1/0                      | running | router_z1     | <IP_ADDRESS>  |
| hm9000_z1/0                        | running | medium_z1     | <IP_ADDRESS> |
| loggregator_trafficcontroller_z1/0 | running | small_z1      | <IP_ADDRESS> |
| nats_z1/0                          | running | medium_z1     | <IP_ADDRESS>   |
| postgres_z1/0                      | running | medium_z1     | <IP_ADDRESS>  |
| router_z1/0                        | running | router_z1     | <IP_ADDRESS>  |
| runner_z1/0                        | running | runner_z1     | <IP_ADDRESS>  |
| uaa_z1/0                           | running | medium_z1     | <IP_ADDRESS> |
+------------------------------------+---------+---------------+--------------+
does it matter that the ha_proxy VM is still <IP_ADDRESS>?


Test (cross-compilation) actions fail on this repository

The error message is:

actions/cache@v3 is not allowed to be used in microsoft/windows-rs. Actions in this workflow must be: within a repository that belongs to your Enterprise account or matching the following: actions/checkout@v2.

Where are you seeing this? Can you link to the particular test run? I don't see any failures in recent commits.

https://github.com/microsoft/windows-rs/actions

I walked right into that one, thanks.

Need to figure out why its not failing the CI validation for PRs - and then we should be able to add the necessary action.

I allowed that cache action but it still seems to fail:
https://github.com/microsoft/windows-rs/actions/runs/2873464088
Might need to revert https://github.com/microsoft/windows-rs/pull/1883 until we can figure this out.

Oh, that's unfortunate but probably there is no other choice.
It'd be nice if https://github.com/microsoft/windows-rs/pull/1961 could be reconsidered instead before next release.

Last build seemed to pass https://github.com/microsoft/windows-rs/actions/runs/2905093873, looks okay now.

The build passed but it still skipped the cross compilation workflow.

OK, I was looking at an older build that should also have succeeded but at least the latest build seems green. 👍

So, I'll close this now - the fix was to enable the cache action (which I did) and the CI build finally seems to have caught up to that fact. 😜


[ARCHITECTURE] Let's do some quality

Dependency injection / test framework and test / Read me setup ...

When are you planning on merging these changes. I would like to help but don't want to make it hard to merge in your branch.

@BCNelson It's almost finish, I hope at the end of the weekend.
I need to create a dependency graph and use this new component in the presenter lawyer.


[language] draft of source code map for bytecode

Adds a basic functionality for tracking source locations the IR in the
bytecode. There is a lot of work left to do here, but I wanted to start getting eyes on this as soon as possible.
High level idea
The basic idea is that every function definition in the module has two mappings associated with it:

<codeOffset> -> <sourceLocation>; and for locals
localIndex -> (name, sourceLocation).

Since a single source location may lead to multiple bytecode instructions, we represent these offsets as a segment tree (using a btree and appropriate range queries). You can read more in the implementation.
NB: this is still an early draft and I need to work on adding in code display (etc) and making this usable once you have the source map (along with general cleanup). There are also a couple places in the compiler where the AST needs to be altered in order to correctly track source locations (e.g. in function arguments).
An Example
Compiling this module:
module Foo {
  public foo(): u64 {
    let x: u64;
    let y: u64;
    x = 1;
    y = 2;
    return move(x) + move(y);
  }

  public bar(x: u64) {
    let t: &u64;
    let y: u64;
    y = move(x);
    t = &y;
    return;
  }

  public flip(b: bool): u64 {
    if (move(b)) {
      return 1;
    } else {
      return 0;
    }
  }
}

Is compiled to this bytecode:
...
function_defs: [
            FunctionDefinition {
                function: FunctionHandleIndex(0),
                flags: 1,
                acquires_global_resources: [],
                code: CodeUnit {
                    max_stack_size: 2,
                    locals: LocalsSignatureIndex(0),
                    code: [
                        LdConst(1),
                        StLoc(0),
                        LdConst(2),
                        StLoc(1),
                        MoveLoc(0),
                        MoveLoc(1),
                        Add,
                        Ret,
                    ],
                },
            },
            FunctionDefinition {
                function: FunctionHandleIndex(1),
                flags: 1,
                acquires_global_resources: [],
                code: CodeUnit {
                    max_stack_size: 1,
                    locals: LocalsSignatureIndex(1),
                    code: [
                        MoveLoc(0),
                        StLoc(2),
                        ImmBorrowLoc(2),
                        StLoc(1),
                        Ret,
                    ],
                },
            },
            FunctionDefinition {
                function: FunctionHandleIndex(2),
                flags: 1,
                acquires_global_resources: [],
                code: CodeUnit {
                    max_stack_size: 2,
                    locals: LocalsSignatureIndex(2),
                    code: [
                        MoveLoc(0),
                        BrFalse(4),
                        LdConst(1),
                        Ret,
                        LdConst(0),
                        Ret,
                    ],
                },
            },
        ],
...

With a source mapping as follows:
ModuleSourceMap {
    module_name: (
<PHONE_NUMBER>000000000000000000000000000000000000000000000000000000,
        Identifier(
            "Foo",
        ),
    ),
    map: {
        1: FunctionSourceMap {
            locals: [
                (
                    Identifier(
                        "x",
                    ),
                    Span {
                        start: ByteIndex(0),
                        end: ByteIndex(0),
                    },
                ),
                (
                    Identifier(
                        "t",
                    ),
                    Span {
                        start: ByteIndex(155),
                        end: ByteIndex(156),
                    },
                ),
                (
                    Identifier(
                        "y",
                    ),
                    Span {
                        start: ByteIndex(172),
                        end: ByteIndex(173),
                    },
                ),
            ],
            code_map: {
                0: Span {
                    start: ByteIndex(188),
                    end: ByteIndex(195),
                },
                1: Span {
                    start: ByteIndex(184),
                    end: ByteIndex(185),
                },
                2: Span {
                    start: ByteIndex(205),
                    end: ByteIndex(207),
                },
                3: Span {
                    start: ByteIndex(201),
                    end: ByteIndex(202),
                },
                4: Span {
                    start: ByteIndex(213),
                    end: ByteIndex(219),
                },
            },
        },
        0: FunctionSourceMap {
            locals: [
                (
                    Identifier(
                        "x",
                    ),
                    Span {
                        start: ByteIndex(43),
                        end: ByteIndex(44),
                    },
                ),
                (
                    Identifier(
                        "y",
                    ),
                    Span {
                        start: ByteIndex(59),
                        end: ByteIndex(60),
                    },
                ),
            ],
            code_map: {
                0: Span {
                    start: ByteIndex(75),
                    end: ByteIndex(76),
                },
                1: Span {
                    start: ByteIndex(71),
                    end: ByteIndex(72),
                },
                2: Span {
                    start: ByteIndex(86),
                    end: ByteIndex(87),
                },
                3: Span {
                    start: ByteIndex(82),
                    end: ByteIndex(83),
                },
                4: Span {
                    start: ByteIndex(100),
                    end: ByteIndex(107),
                },
                5: Span {
                    start: ByteIndex(110),
                    end: ByteIndex(117),
                },
                6: Span {
                    start: ByteIndex(100),
                    end: ByteIndex(117),
                },
                7: Span {
                    start: ByteIndex(93),
                    end: ByteIndex(117),
                },
            },
        },
        2: FunctionSourceMap {
            locals: [
                (
                    Identifier(
                        "b",
                    ),
                    Span {
                        start: ByteIndex(0),
                        end: ByteIndex(0),
                    },
                ),
            ],
            code_map: {
                0: Span {
                    start: ByteIndex(264),
                    end: ByteIndex(271),
                },
                2: Span {
                    start: ByteIndex(288),
                    end: ByteIndex(289),
                },
                3: Span {
                    start: ByteIndex(281),
                    end: ByteIndex(289),
                },
                4: Span {
                    start: ByteIndex(317),
                    end: ByteIndex(318),
                },
                5: Span {
                    start: ByteIndex(310),
                    end: ByteIndex(318),
                },
            },
        },
    },
}

:umbrella: The latest upstream changes (presumably abab0df60c3e041069424b23db09d80df286b71b) made this pull request unmergeable. Please resolve the merge conflicts.

:umbrella: The latest upstream changes (presumably 89323bf9cc762b03579be91a41eb6f45230c0e03) made this pull request unmergeable. Please resolve the merge conflicts.

:umbrella: The latest upstream changes (presumably cf9de8019d072e3ea76db2ac121c0fcd24fcdb4c) made this pull request unmergeable. Please resolve the merge conflicts.

:umbrella: The latest upstream changes (presumably 32684764dd9116147e2b36da23593b1960777ebc) made this pull request unmergeable. Please resolve the merge conflicts.

FYI: Changing some things around, so don't review this yet.

:umbrella: The latest upstream changes (presumably 5d9ed1a868390cd9ce5959a05b753370de825577) made this pull request unmergeable. Please resolve the merge conflicts.

@bors-libra r=tnowacki

:pushpin: Commit d47155d has been approved by tnowacki

:hourglass: Testing commit d47155dd666f89b6774f771cafa754077f0a6b65 with merge bee6064e90404ad9333144f34094dada9cf7cc1b...

:sunny: Test successful - checks-circle_commit_workflow
Approved by: tnowacki
Pushing bee6064e90404ad9333144f34094dada9cf7cc1b to master...


Bluetooth crash after +-1hour (IDFGH-12209)

Answers checklist.

[X] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

IDF version.
idf 4.3.1
Espressif SoC revision.
ESP32
Operating System used.
Windows
How did you build your project?
Eclipse IDE
If you are using Windows, please specify command line type.
CMD
Development Kit.
Custom board with esp32
Power Supply used.
External 3.3V
What is the expected behavior?
Bluetooth should always work with all sorts of clients
What is the actual behavior?
After 1 hour bluetooth crashes with recent android or IOS models.
Steps to reproduce.

Start from the a2dp sink example
Connect a samsung tablet Tab S6 with android 12
Play music from spotify for about one hour

Debug Logs.
Guru Meditation Error: Core  0 panic'ed (StoreProhibited). Exception was unhandled.

Core  0 register dump:
PC      : 0x40101b13  PS      : 0x00060f30  A0      : 0x80100e98  A1      : 0x3ffe67f0
0x40101b13: reassemble_and_dispatch at C:/Users/simon/esp/esp-idf-v4.3.1/components/bt/host/bluedroid/hci/packet_fragmenter.c:175
 (inlined by) reassemble_and_dispatch at C:/Users/simon/esp/esp-idf-v4.3.1/components/bt/host/bluedroid/hci/packet_fragmenter.c:136

A2      : 0x3fffdf90  A3      : 0x000002ab  A4      : 0x000003cd  A5      : 0x00000080
A6      : 0x00001100  A7      : 0x00000000  A8      : 0x80101b10  A9      : 0x3ffe67a0
A10     : 0x00000000  A11     : 0x000003d5  A12     : 0x00000000  A13     : 0x00000018
A14     : 0x00000020  A15     : 0x00000024  SAR     : 0x0000001c  EXCCAUSE: 0x0000001d
EXCVADDR: 0x00000002  LBEG    : 0x4000c46c  LEND    : 0x4000c477  LCOUNT  : 0x00000000

Backtrace:0x40101b10:0x3ffe67f0 0x40100e95:0x3ffe6820 0x4011974a:0x3ffe6840 0x40112de7:0x3ffe6870 0x40119658:0x3ffe6890 0x401136cf:0x3ffe68b0
0x40101b10: reassemble_and_dispatch at C:/Users/simon/esp/esp-idf-v4.3.1/components/bt/host/bluedroid/hci/packet_fragmenter.c:174
 (inlined by) reassemble_and_dispatch at C:/Users/simon/esp/esp-idf-v4.3.1/components/bt/host/bluedroid/hci/packet_fragmenter.c:136

0x40100e95: hal_says_packet_ready at C:/Users/simon/esp/esp-idf-v4.3.1/components/bt/host/bluedroid/hci/hci_layer.c:413

0x4011974a: hci_hal_h4_hdl_rx_packet at C:/Users/simon/esp/esp-idf-v4.3.1/components/bt/host/bluedroid/hci/hci_hal_h4.c:296
 (inlined by) event_uart_has_bytes at C:/Users/simon/esp/esp-idf-v4.3.1/components/bt/host/bluedroid/hci/hci_hal_h4.c:304

0x40112de7: fixed_queue_process at C:/Users/simon/esp/esp-idf-v4.3.1/components/bt/common/osi/fixed_queue.c:254

0x40119658: hci_hal_h4_rx_handler at C:/Users/simon/esp/esp-idf-v4.3.1/components/bt/host/bluedroid/hci/hci_hal_h4.c:170

0x401136cf: osi_thread_run at C:/Users/simon/esp/esp-idf-v4.3.1/components/bt/common/osi/thread.c:68

More Information.
With an older samsung tablet or a windows PC, the problem did not seem to occure

@SimonPVS  Please upload the elf file with this issue and show me  the  git commit id of IDF.

NWPxxx.zip
git commit id: SHA-1: 2e74914051d14ec2290fc751a8486fb51d73a31e

Are you sure this elf was used when an error occurred, after disassembling, it was found that the code address does not match .
With this log ,I think there may be a error on  packet_fragmenter.c:174
" partial_packet == NULL"
The code does not handle malloc failures.

Yess i copied the file from the build folder. Maybe something went wrong with zipping it, so I renamed the extension to txt so if you can rename it back to .elf, it should'nt be modified. (github does not allow me to send a .elf file)
NWPxxx.txt
Indeed I noticed there is a osi_calloc function which i think is failing, but i tried printing something when partial_packet == NULL without result. (Or maybe the print can't get executed?)

What can be the reason of failing there?

I downloaded "NWPxxx.tx" , but it is still  not match.
After you modify any line of code, rebuilding will change the elf file, what I need is the elf file when running the error.
StoreProhibited  means store a prohibited address,
0x40101b10: reassemble_and_dispatch at C:/Users/simon/esp/esp-idf-v4.3.1/components/bt/host/bluedroid/hci/packet_fragmenter.c:174
Only when  partial_packet == "a prohibited address "  will this error be reported on the line 174.
But I don't have the elf file, so I can't confirm how it went wrong.

Ok sorry for the misunderstanding.
NWPxxx.zip
`I (2213203) BT_APP_CORE: bt_app_work_dispatch event 0x4, param len 12
I (2213203) BT_AV: Play position changed: 50048-ms
partial_packet == NULL, full length: 973
Guru Meditation Error: Core  0 panic'ed (StoreProhibited). Exception was unhandled.
Core  0 register dump:
PC      : 0x40101b34  PS      : 0x00060d30  A0      : 0x80100ea4  A1      : 0x3ffe66f0
0x40101b34: reassemble_and_dispatch at C:/Users/simon/esp/esp-idf-v4.3.1/components/bt/host/bluedroid/hci/packet_fragmenter.c:185
(inlined by) reassemble_and_dispatch at C:/Users/simon/esp/esp-idf-v4.3.1/components/bt/host/bluedroid/hci/packet_fragmenter.c:136
A2      : 0x3ffffcdc  A3      : 0x00000000  A4      : 0x000003cd  A5      : 0x00000080
A6      : 0x00001100  A7      : 0x00000000  A8      : 0x80101b2e  A9      : 0x3ffffce4
A10     : 0x0000002a  A11     : 0x3ffe689c  A12     : 0x00000000  A13     : 0x00000018
A14     : 0x00000020  A15     : 0x00000024  SAR     : 0x00000004  EXCCAUSE: 0x0000001d
EXCVADDR: 0x00000002  LBEG    : 0x4000c46c  LEND    : 0x4000c477  LCOUNT  : 0x00000000
Backtrace:0x40101b31:0x3ffe66f0 0x40100ea1:0x3ffe6720 0x4011976a:0x3ffe6740 0x40112e07:0x3ffe6770 0x40119678:0x3ffe6790 0x401136ef:0x3ffe67b0
0x40101b31: reassemble_and_dispatch at C:/Users/simon/esp/esp-idf-v4.3.1/components/bt/host/bluedroid/hci/packet_fragmenter.c:184
(inlined by) reassemble_and_dispatch at C:/Users/simon/esp/esp-idf-v4.3.1/components/bt/host/bluedroid/hci/packet_fragmenter.c:136
0x40100ea1: hal_says_packet_ready at C:/Users/simon/esp/esp-idf-v4.3.1/components/bt/host/bluedroid/hci/hci_layer.c:413
0x4011976a: hci_hal_h4_hdl_rx_packet at C:/Users/simon/esp/esp-idf-v4.3.1/components/bt/host/bluedroid/hci/hci_hal_h4.c:296
(inlined by) event_uart_has_bytes at C:/Users/simon/esp/esp-idf-v4.3.1/components/bt/host/bluedroid/hci/hci_hal_h4.c:304
0x40112e07: fixed_queue_process at C:/Users/simon/esp/esp-idf-v4.3.1/components/bt/common/osi/fixed_queue.c:254
0x40119678: hci_hal_h4_rx_handler at C:/Users/simon/esp/esp-idf-v4.3.1/components/bt/host/bluedroid/hci/hci_hal_h4.c:170
0x401136ef: osi_thread_run at C:/Users/simon/esp/esp-idf-v4.3.1/components/bt/common/osi/thread.c:68`

Is it normal that i recieve this message at a very high rate when streaming music from an android 12 tablet?

This is normal. When receiving data from CTRL, it is subcontracted and packaged ,  all applications will use it here.

Thanks for the support!
I have updated to 4.4 (not to 5.x because of the breaking changes)
The music is playing stable now for more than 2 hours and still going.
Now the heap decreases much slower, but unfortunatly it keeps decreasing. Is this normal?
Directly after connecting the heap goes to 42k. After 2 hours the heap is at 37k. (and I think it keeps decreasing further)

It seems that there is a memory leak.
Please refer to  :
https://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-reference/system/heap_debug.html#how-to-diagnose-memory-leaks


Remove minimum indents under nested condition

I didn't fully understand the code but it did resolve #1339 and the tests are passing, except:

 tests/test_regressions.py::test_windows_newline_issue_1277

Codecov Report

Merging #1340 into develop will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##           develop     #1340   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           34        34
  Lines         2235      2235
=========================================
  Hits          2235      2235

Thank you!


Page background opacity not working

While I can select a custom page background, the background is always 100% opaque whether or not I pass an argument for page-background opacity. A minimal example of this is as shown:
 ---
 title: "Title Here"
 author: Author
 page-background: "backgrounds/background5.pdf"
 page-background-opacity: 0.5
 ---
 # Content here

I installed texlive latex extra and the packages listed on the readme, and I use xelatex to write to pdf. If it helps, I am running this on Manjaro Linux with KDE.

EDIT: although changing the pdf engine to the default setting threw errors, using the lualatex engine fixed this problem.

Using latest release (2.5.0) I have this same issue - page backgrounds are full opacity no matter the setting when using --pdf-engine=xelatex but work correctly with --pdf-engine=lualatex.


Fix UTF-8 unsoundness in string::merge

Fixes #193

Note that the merge implementation does not clear the existing value, as the protobuf spec suggests it should. If it did, the guard code would be simpler and marginally more efficient.

Thanks again @mzabaluev, this is a great catch!

This RP seems to fix unsoundness that can be triggered in practice. Please file a security advisory at https://github.com/RustSec/advisory-db so that dependents can check if their crate is affected and upgrade.


turbodbc is faster at downloading

In my benchmarks, it seems like Turbodbc with use_async_io=True is 20–30% faster than arrow-odbc-py with fetch_concurrently().
I haven't done any profiling on this yet.

Btw, here https://github.com/pacman82/arrow-odbc-py/issues/47#issuecomment-1661655693 you @pacman82 suggested to use odbc2parquet if you want to go from ODBC to Parquet without the Arrow intermediary. To me this implies that it's also faster than going through arrow-odbc-py. In my benchmarks with comparable settings however, odbc2parquet is ~ 20% slower than going through arrow-odbc-py (with read_concurrently()) + pyarrow.parquet.

According to my profiling, 75% of the time is spent in the ODBC buffer -> RecordBatch conversion if you use fetch_concurrently(). But only 50% of time if you don't use it. Either this is a profiling artifact, or it means that the concurrent mode has significant overhead in the "Arrow thread". Also, it probably means that we could reasonably get up to a 1.5x speedup "just" by optimizing/parallelizing RecordBatch construction. Although I'm pretty sure that would require significant effort.

On another query arrow-odbc is much faster. Interesting.

Faster is always better, but I am closing this issue. Not sure what the definition of done here would be.


Update tenant list for new design

We have new mockups for the tenant page that HPD and advocacy groups see. It provides better summary data and controls.

organization-wide view

see all tenants grouped by building
see summary info without having to click on individual tenants
if they're currently in violation
how many violations that week

filtering & sorting

only violations that are more than 2ºF below the limit
see buildings with the most violations
see buildings with multiple tenants on multiple floors with no heat

20160711_heatseek_mockup (1).pdf

👍
I'm currently traveling, but hope to PR the updates to the tenant forms for setting buildings and apartments next week so that the data will be there to serve these new views.


SpatialMapping on Hololens Emulator crashes the app.

Overview
I am trying to use Spatial Mapping in Hololens Emulator. I created a test scene and build it to run on Hololens Emulator, but as soon as the scene loads the app crashes.
Expected Behavior
App not to crash when using Hololens Emulator.
Actual Behavior
App crashes when using Spatial mapping in Hololens Emulator.
Output from Debug
Last couple of lines from Debug Output in Visual Studio.
Windows Mixed Reality spatial locatability state changed to 3.

(Filename: C:\buildslave\unity\build\Runtime/VR/HoloLens/HoloLensWorldManager.cpp Line: 388)

UnloadTime: 2.686400 ms

Display is Transparent

(Filename: C:\buildslave\unity\build\artifacts/generated/Metro/runtime/DebugBindings.gen.cpp Line: 51)

Starting the observer.

(Filename: C:\buildslave\unity\build\artifacts/generated/Metro/runtime/DebugBindings.gen.cpp Line: 51)

Failed to retrieve bytes for vertex positions from surface mesh!

(Filename: C:\buildslave\unity\build\Runtime/VR/HoloLens/SpatialMapping/SpatialSurface.cpp Line: 135)

The program '[5092] Hololens-Model-Demo-2017.4.exe' has exited with code -2147483645 (0x80000003).

Steps to reproduce

Create an empty project.
Create a new scene.
Apply MRTK Project Settings. (Check Target Windows Universal UWP, Enable XR, Build for Direct3D, Enable .NET Scripting Backend, Set Default spatial mapping layer)
Apply MRTK Scene Settings. (Check all options including 'Add the spatial mapping prefab')
Add the scene to build.
Build the unity project from MRTK build window.
Open built project in Visual Studio
Debug the app using Hololens Emulator.

Versions

Unity - 2017.4.19f1
Visual Studio - 2017
Hololens Emulator - 10.0.17763.134

Mixed Reality Toolkit Release Version
MRTK 2<IP_ADDRESS> Refresh

Never mind. The issue is due to the version of emulator itself. Older version of Hololens Emulator (10.0.17134.0) supports the Spatial Mapping Properly.


Automator: update common-files@master in istio/istio@master

Generated by Automator - 2020-03-16T18:11:20+00:00

@istio-testing: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
c84116801d332e635c9d86f3005a110d2f881a9b
link
/test lint_istio

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

@ostromart can you take a look at
./operator/cmd/mesh/testdata/manifest-generate/output/component_hub_tag.golden.yaml
  133:17    error    too many spaces after colon  (colons)
  136:17    error    too many spaces after colon  (colons)
  139:17    error    too many spaces after colon  (colons)
  142:17    error    too many spaces after colon  (colons)
  145:17    error    too many spaces after colon  (colons)
  148:17    error    too many spaces after colon  (colons)
  151:17    error    too many spaces after colon  (colons)
  154:17    error    too many spaces after colon  (colons)
```?

I think the yaml linter was temporarily broken and this fixes it

I agree that a prior change prevented the yaml linter from running. This update re-enables the yaml linter so anything that might have gotten through needs to be updated.

@istio-testing: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
498a13471d33a0f66cc69903afc5990fb19e65d4
link
/test unit-tests_istio

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

/retest


Don't loop over TLS records for SNI

Motivation:
The AbstractSniHandler previously was willing to tolerate up to three non-handshake records before a ClientHello that contained an SNI extension field. This is, so far as I can tell, completely unnecessary: no TLS implementation will be sending alerts or change cipher spec messages before ClientHello.
Given that it was not possible to determine why this loop is in the code to begin with, it's probably just best to remove it.
Modifications:
Remove the for loop.
Result:
The AbstractSniHandler will more rapidly determine whether it should pass the records on to the default SSL handler.

@rkapsi as well PTAL

Here's the PR #4703 that introduced it ~2 years ago. Is it one of these things that are technically possible because the spec allows it but practically they're nonsense?

@rkapsi yep I talked with @cconroy about it but cant really remember anymore why I thought this would be a good change :(

@netty-bot test this please

@Lukasa sorry that it took so long...


RethinkDB module not supported

i am trying to do an app that uses RethinkDB and this module seems not to be supported not suported
\\npm install rethinkdb
var r = require('rethinkdb');

It RethinkDB using websockets under the hood to keep connected to the databse? (ala firebase)

so as i haven't found their package in npm, it has been difficult to findhow this works. after a bit of digging around they are not using directly any package similar to sockets.io, but regarding communication they seem to be using nodes net and tls packages. (plus other dependencies: cripto, events, and (npm) bluebird).
for you to have more info you will need to add to a node project the package of rethinkdb (npm install rethinkdb), and look inside node_modules.

@kanekotic Thanks for the details... i think there might be something missing in the dependend node packages. @ralfstx do you have any insights?

I don't know this module but it appears that the git repo involves a lot of C++ code. Does the npm module include binary code? If so, this would not run on the mobile platforms out of the box.
@kanekotic What is the exact symptom of not working? Do you get an exception?

@ralfstx The project that is a database is mostly C++ code, agreed. But the projects that use this db need an npm package that is purely javascript. It can be added to any node based project by:
npm install rethinkdb --save

This npm package to the extend of what i have seen by review it on the node_modules folder, it rely mostly in the node api. As per your question the symptom is when i run it shows on screen the message: cannot find the module net. After reviewing the package code is this node library net.
This error happens by just adding to the basic tabris project any of the next js codes:
var r = require('rethinkdb');

require("tabris-js-node");
var r = require('rethinkdb');

I have create a base project  if you want to clone it and try.

Right, the Node.js net module is not yet supported.

Closing as npm modules that include binary code (C++) can not be supported by Tabris.js.


AOT compilation failed

Hi, I've this project structure

app.module
--template.module (only available if people login)
--auth.module (login component)

I put in the shared.module
`@NgModule({
imports: [],
exports: [
CommonModule,
NgSlimScrollModule
],
declarations: []
})
export class SharedModule {
}`
and then I import the shared.module only in template.module. No problem with ng serve.
When I try to compile with: ng build --aot it fails with

ERROR in Can't export value NgSlimScrollModule in S:/app/node_modules/ngx-slimscroll/index.d.ts from SharedModule in S:/app/src/app/shared/shared.module.ts as it was neither declared nor imported!

ERROR in ./src/main.ts
Module not found: Error: Can't resolve './$$_gendir/app/app.module.ngfactory' in 'S:\app\src'
@ ./src/main.ts 4:0-74
@ multi ./src/main.ts
My Environment:
"dependencies": {     "@angular/animations": "^4.1.0",     "@angular/common": "^4.1.0",     "@angular/compiler": "^4.1.0",     "@angular/core": "^4.1.0",     "@angular/forms": "^4.1.0",     "@angular/http": "^4.1.0",     "@angular/platform-browser": "^4.1.0",     "@angular/platform-browser-dynamic": "^4.1.0",     "@angular/router": "^4.1.0",

any update on this ?


Add an identification code filter to advanced search for principal organizations

Currently to search on the identification code, the user has to use the "Search term" data field. It would be more intuitive for the users to have a unique filter.
(from https://github.com/NCI-Agency/anet/issues/200#issuecomment-345459168 )

@dspCarlson can you please confirm if still valid?

Currently not required, and already works with PostgreSQL.


Topic/ghc

! @jystic

! @erikd-ambiata

The checks seem to be missing some 8.0 builds. Egf optparse, eithert, show etc

Yeah I'll add the other things, I just did this one since it had a 8.0.1 lock file.

Or 8.0.2 unfortunately
On Wed, Nov 8, 2017 at 8:25 AM, Erik de Castro Lopo <
<EMAIL_ADDRESS>wrote:

@erikd-ambiata commented on this pull request.
In framework/master.toml
https://github.com/ambiata/x/pull/139#discussion_r149508026:

HADDOCK = "true"
HADDOCK_S3 = "$AMBIATA_HADDOCK_BRANCHES"

+[build.branches-8-0]

GHC_VERSION="8.0.1"

@etorreborre https://github.com/etorreborre We're haven't upgraded to
8.2 yet.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ambiata/x/pull/139#discussion_r149508026, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAKbuclnjwHFJTRn7N5lK8gOCPYEqrv6ks5s0MrEgaJpZM4QSwEQ
.


Example throws errors

Describe the bug
The example in the docs throws errors ...
[
  {
    index: 0,
    config: { type: 'int', name: 'age', width: 2 },
    errors: [ 'Start must be defined.' ]
  },
  {
    index: 1,
    config: { name: 'name', width: 12, type: 'string' },
    errors: [ 'Start must be defined.' ]
  }
]

and the object resulting from the constructor is undefined
To Reproduce
Follow the docs example
const { FixedWidthParser } = require('fixed-width-parser');

const fixedWidthParser = new FixedWidthParser([
  {
    type: 'int',
    name: 'age',
    width: 2,
  },
  {
    name: 'name',
    width: 12,
  },
]);

Expected behavior
fixedWidthParser should be a usable instance of FixedWidthParser
Additional context
nodejs v12

Both examples throw the same error, because they are missing the start property.
To fix the first (parse):
const fixedWidthParser = new FixedWidthParser([
           {
               name: 'age',
               start: 0,
               type: 'int',
               width: 2,
           },
           {
               name: 'name',
               start: 3,
               width: 12,
           },
       ]);

To fix the second (unparse):
        const fixedWidthParser = new FixedWidthParser([
           {
               name: 'age',
               start: 0,
               type: 'int',
               width: 2,
           },
           {
               name: 'name',
               start: 3,
               width: 12,
           },
       ]);

Sorry about that. Fix coming through now.
Not sure why I haven't been seeing email notifications from this repo. I'll try to get that fixed as well on my end so I don't miss these reports.
Thanks for catching this!