Basic AR implementation

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Done in :https://github.com/galacean/runtime/pull/1787


Change remote directory resource to work with domain users

Without this correction, I couldn't make the jenkins_windows_slave work when using a trusted domain account for the service.

Hi. I am an automated pull request bot named Curry. There are commits in this pull request whose authors are not yet authorized to contribute to Chef Software, Inc. projects or are using a non-GitHub verified email address. To become authorized to contribute, you will need to sign the Contributor License Agreement (CLA) as an individual or on behalf of your company. You can read more on Chef's blog.
GitHub Users Who Are Not Authorized To Contribute
The following GitHub users do not appear to have signed a CLA:

@eguerints

Please sign the CLA here.

Hi. Your friendly Curry bot here. Just letting you know that all commit authors have become authorized to contribute. I have added the "Signed CLA" label to this issue so it can easily be found in the future.

Thank you! I simplified this slightly and merged as 3e2343e12c1aa96f4da65b3372a483a139d3d3f5.


⚠ Bofrost.be has degraded performance

In 3cd71a0, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1765 ms

Resolved: Bofrost.be performance has improved in 103a212 after 13 minutes.


Added ability to add random obstacles to the race track

The F110Env class has a method .add_obstacles(n_obstacles, obstacle_size) which allows one to add a number of obstacles to the map.
Locations are randomly generated and then the map_img in the laser scanner is updated.
The obstacles are rendered in a similar manner to the cars

Thanks for the comments, I will make the changes recommended.

Thanks for the comments, I will make changes accordingly, and add them to the pull request.

I have made significant changes
The obstacles are now loaded according to the centerline.
I added a load_centerline method to load the centerline file, I hope this is ok.
I tried to fix as many of the issues you highlighted as possible.
I have also written a unit test to show that the randomness is repeatable.
Let me know if additional changes must be made

Closing for now as not planned in v1.0.0


[System stored procedures] sp_refreshview or sp_refreshsqlmodule are not supported in Azure Synapse SQL Serverless Pool

In our documentation1, and  documentation2 it looks like that sp_refreshview and sp_refreshsqlmodule can both be used in Azure Synapse Analytics.
In contrary, sp_refreshview nor sp_refreshsqlmodule are supported in Synapse SQL Serverless Pool.

@nstijepovic -- thank you for clear feedback.
@markingmyname -- please look into this issue.

#reassign @WilliamDAssafMSFT

Assigned to William based on Synapse info.

Thanks @nstijepovic for taking the time to provide this feedback, your suggestions help improve our documentation. This looks like a good opportunity to update the applicability of this article to dedicated SQL pools only. This doc update is in flight. Thanks again!


Warning about critical-pod non-functional

When running helm install node-exporter telemetry-aware-scheduling/deploy/charts/prometheus_node_exporter_helm_chart. a warning about critical pod popping out.

W1212 13:54:31.447663 280921 warnings.go:70] spec.template.metadata.annotations[scheduler.alpha.kubernetes.io/critical-pod]: non-functional in v1.16+; use the "priorityClassName" field instead

This file makes use of the critical pod.
While this does not stop the helm chart from being deployed, uncertain of the behavior that will result from the use of the non-functional property.

Hi!
As far as I could tell there should be no issues with the chart up until K8s v1.26 as that is the most recent I have tested TAS with.
I will add an item into our backlog to address this and will come back with an estimation to when this will be picked up.

Hi,
this problem has been fixed in https://github.com/intel/platform-aware-scheduling/pull/137 and PR is already merged in the master branch


Allow overriding the APIS_ENTITIES setting

The APIS_ENTITIES are created using the values that are stored in
the entity_settings attribute of entities. In some cases it might
make sense to be able to define those in the global settings file.
This commit changes the code so it checks for the existense of the
APIS_ENTITIES setting and only uses the entity_settings attribute
if the global settings is empty.

Relatedly, I think it would make sense if entity_settings were set up differently in general, see: https://github.com/acdh-oeaw/apis-ontologies/issues/9#issuecomment-1334010750 cc @sennierer

squashed, rebased and merged


autovmaf wants to change profile parameters through its interface. OSAAS api gets the profile from http. Make a decision and implement.

OSAAS encore api profile parameter description
User can provide a url to a profiles file on instance creation. If no such url is provided a url to default profiles is used.
If this is the case, then the user is required to have the profile hosted on http? Right now the default profiles are on github. I assume similar hosting would be required if one was to use their own profile.yml. As autovmaf is designed today, the user expects to have the ability to affect the resolution and bitrate of the transcoding output through the autovmaf interface. How do we want to solve this?
Local profile.yml pushed somewhere where the OSAAS encore api can access it?
Deliverable
Should be able to start a job in exact same process flow as local and aws pipelines. This likely implies that we will need some way for the autovmaf job parameters to be pushed to the hosted encore profile. Current control flow is that a .yml profile is stored on github or other http host, thereby accessible by the encore OSAAS api?
https://svt.github.io/encore-doc/#profiles
As described by the SVT encore documentation
A Profile can be seen as a general abstraction of an FFmpeg configuration - example, bitrate to use, thumbnail generation, the codec to use.
A Profile specifies a big part of the configuration used by an Encore Job - metadata, FFmpeg configuration and specific codec configuration.
A Profile is specified in the yaml-format.

We have a draft issue here: https://github.com/orgs/Eyevinn/projects/17/views/1?pane=issue&itemId=43049058
detailing a small change to the encore api in our fork that allows the api to accept a profile.yml in string format.


Typo

String 134 in Resources.resx says {0:p:1 hour|{} hours} hour ago

Oops! Thanks, I'll fix that


example for balanced shared registrations

pull request goes along with pull request https://github.com/crossbario/crossbar/pull/613 on crossbar

closing this, as we'll address the base issue in CB slightly different


Unable to hold down a key to insert a sequence of the same character

I would expect that holding down a key for a longer time would start to repeat the character. This is the behaviour of at least Terminal.app.
As far as I can remember this has worked some time ago and seems to be a regression?

Nope it never worked https://github.com/sourcelair/xterm.js/issues/265.


HTML node not extracting content

Current Behavior
This appears version related. Example flow does not produce output under 2.0.6 when using HTML node.
Expected Behavior
When running the flow, clicking the inject node, output should produce Obligaties Wereldwijd
Steps To Reproduce
Run example flow on both version 1.3.7 and 2.0.6.
Example flow
[{"id":"c5073e7167dfd3b0","type":"inject","z":"07c0e534b17ff9a0","name":"","props":[{"p":"payload"},{"p":"topic","vt":"str"}],"repeat":"","crontab":"","once":false,"onceDelay":0.1,"topic":"","payload":"Obligaties Wereldwijd	","payloadType":"str","x":482,"y":144,"wires":[["6ee0d520cb8a2368","a91557144a38bd23"]]},{"id":"a91557144a38bd23","type":"debug","z":"07c0e534b17ff9a0","name":"","active":true,"tosidebar":true,"console":false,"tostatus":false,"complete":"false","statusVal":"","statusType":"auto","x":790,"y":144,"wires":[]},{"id":"6ee0d520cb8a2368","type":"html","z":"07c0e534b17ff9a0","name":"","property":"payload","outproperty":"payload","tag":".name","ret":"text","as":"single","x":628,"y":96,"wires":[["a91557144a38bd23"]]}]

Environment

Node-RED version: 1.3.7 and 2.0.6
Node.js version:v14.17.6
npm version: 6.14.15
Platform/OS: LXC Debian container
Browser: Safari 14.1.1

The html parsing library, cheerio had a major version upgrade as part of the 2.0 release.
That library made significant breaking changes in how it handles HTML fragments vs complete HTML documents. We tried to maintain backward compatibility - and got to the point our unit tests pass cleanly. However your scenario here does appear to have changed behaviour.
As you've noted in the Discourse thread, feeding in: Obligaties Wereldwijd	 does not work, but feeding in
Obligaties Wereldwijd
 does.
I thought maybe the issue was trying to select on the top-level object, however passing in
Obligaties Wereldwijd
 does work as well. So I think this is specific to the  element. My guess is the library considers it an invalid fragment as the  tag cannot exist outside of a
.
Whilst it is not entirely satisfactory, I do not think there is anything we can do here. We needed to upgrade the cheerio library to pickup long-outstanding bug fixes - reverting it is not an option.

Reading a similar issue, it might have to do with the way DOM parsing works; no table, no tr/th/td. I will work around it with an xml node.


Akagi64 shows nothing

Hello.
Sorry for spamming, maybe you could help me.
My steps for building the project, Windows Defender is off.

Building  Akatsuki -> \output\x64\Release\Akatsuki64.dll
Building Fubuki -> \output\x64\Release\Fubuki64.dll, \output\Win32\Release\Fubuki32.dll
Building Yuubari  -> \output\x64\Release\UacInfo64.exe
Building Naka -> \output\x64\Release\Naka64.exe
Naka64 \output\x64\Release\Akatsuki64.dll -> \Naka\output\x64\Release\Akatsuki64.cd, Akatsuki64.key
Naka64 \output\x64\Release\Fubuki64.dll -> \Naka\output\x64\Release\fubuki64.cd, fubuki64.key
Naka64 \output\x64\Release\Fubuki32.dll -> \Naka\output\x64\Release\Fubuki32.cd, Fubuki32.cd.key
Naka64 \Source\Kamikaze\Kamikaze.msc -> \Naka\output\x64\Release\Kamikaze.cd, Kamikaze.key
naka64.exe --stable -> secrets64.bin (144 bytes), secrets32.bin (72 bytes)
Copying everything to \Source\Akagi\bin (Akatsuki64.cd, Fubuki32.cd, Fubuki64.cd, Kamikaze.cd, secrets32.bin, secrets64.bin)
Building Akagi -> \output\x64\Release\Akagi64.exe

Akagi64.exe does nothing... ProcMon shows Process Exit with Status: -1073741811

VS 2022, Platform Toolset - Visual Studio 2022 (v143), no errors during building

Hello there)
Thank you for the response. Maybe I got it wrong, but when run without parameters, it should display a message box like Naka64, no?

Thank you for the tip and your time! It works.


Creating an example feature extractor for use in documentation to sho…

Created an example feature extractor for use in documentation to show people who to develop external FE libraries.
The goal was to implement as little as possible but still portray the methods, class methods, and attributes that need to be implemented.

Closing this PR because the changes here have been incorporated into the new lsstdesc/resspect_external repository.


created CSS folder with proposed responsive design

I have made a proposed design decision for the layout. It is a responsive design that is to be discussed in the group.

Looks good Lee!

Feels cool... Can't say 'look' because I can't see it right now lol.


chore: adding cmst and mars asset pair to  pf config

Description

[X] check the canon-2 with this config for CMST and MARS prices

Author Checklist
All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.
I have...

[ ] included the correct type prefix in the PR title
[ ] added ! to the type prefix if API or client breaking change
[ ] added appropriate labels to the PR
[ ] targeted the correct branch
[ ] provided a link to the relevant issue or specification
[ ] added a changelog entry to CHANGELOG.md
[ ] included comments for documenting Go code
[ ] updated the relevant documentation or specification
[ ] reviewed "Files changed" and left comments if necessary
[ ] confirmed all CI checks have passed

Reviewers Checklist
All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.
I have...

[ ] confirmed the correct type prefix in the PR title
[ ] confirmed all author checklist items have been addressed
[ ] reviewed state machine logic
[ ] reviewed API design and naming
[ ] reviewed documentation is accurate
[ ] reviewed tests and test coverage
[ ] manually tested (if applicable)

@zarazan  Please merge this pr once you deployed the CMST to cresent production api


Add custom stopping criteria to ICL generate tasks

What does this PR do?
Modeled after EleutherAI implementation of generate tasks, we enable custom stopping criteria to be implemented.
This relies on five separate changes:

Implement a multi token stopping criteria modeled after this
Modify QA tasks' collate fn to add stopping criteria to generate kwargs as well as pass them along in the batch as raw strings
Modify the QA metric to post-hoc apply the stopping criteria to any outputs it wasn't applied to. This is necessary because stopping criteria don't stop until all outputs in a device batch reach the stopping criteria, so by definition all but one output per batch will need to have it manually applied post-hoc.
Modify the split_batch fn to properly handle list values that need to be broadcast (the string literal stopping criteria)
Make normalization optional, since GSM8K doesn't use the standard normalization.

What issue(s) does this change relate to?

Before submitting

[ ] Have you read the contributor guidelines?
[ ] Is this change a documentation change or typo fix? If so, skip the rest of this checklist.
[ ] Was this change discussed/approved in a GitHub issue first? It is much more likely to be merged if so.
[ ] Did you update any related docs and document your change?
[ ] Did you update any related tests and add any new tests related to your change? (see testing)
[ ] Did you run the tests locally to make sure they pass?
[ ] Did you run pre-commit on your change? (see the pre-commit section of prerequisites)

Couple small questions, logic seems right to me. Would love to see some unit tests.

I'll try and mock the __call__ function somehow in a unit test!

LGTM. Importing a function only to check if it exists is a little funny to me, but I understand the reasoning based on past discussions and think it's a fine solution!


CI: add workflows

adds some basic workflows that handle

checking documentation
auditing dependencies
testing formatting
build testing
unit testing (just the groundwork)
publishing crates

I've tested the workflows best I could using act, the publish workflow could not be tested as it needs tagging.

Left a FIXME comment in the build workflow. I'm currently unable to test it, so if anybody could and tell me if those deps are preinstalled on ubuntu, I can remove it, If not, we can wait until I am back on my workstation to test before merging.

This is great work, thanks @NotAShelf !
I think I'll merge it as is and then make changes if I see that sth doesn't work. :)


Fix: CODEOWNERS.

Description
The team is going away, replaced by the list of people in MAINTAINERS.md.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Also adjusted permissions


Cannot attach to running instances when global process hook

Hi,
I'm using renderdoc to inject GTA5. Since my game is on steam, I followed this instruction to do global process hooking.
After the game is launched, the in-app overlay appears and I can press F12 to capture. Then, I disabled global process hook as instructed. However, I cannot find the running instance under localhost in the 'attach to running instances' menu, and the diagnostic log shows that
RENDERDOC:  [14:26:46]    win32_network.cpp( 351) - Warning - Failed to connect to localhost:38920
RENDERDOC:  [14:26:46]    win32_network.cpp( 351) - Warning - Failed to connect to localhost:38921
RENDERDOC:  [14:26:46]    win32_network.cpp( 351) - Warning - Failed to connect to localhost:38922
RENDERDOC:  [14:26:46]    win32_network.cpp( 351) - Warning - Failed to connect to localhost:38923
RENDERDOC:  [14:26:47]    win32_network.cpp( 351) - Warning - Failed to connect to localhost:38924
RENDERDOC:  [14:26:47]    win32_network.cpp( 351) - Warning - Failed to connect to localhost:38925
RENDERDOC:  [14:26:47]    win32_network.cpp( 351) - Warning - Failed to connect to localhost:38926
RENDERDOC:  [14:26:48]    win32_network.cpp( 351) - Warning - Failed to connect to localhost:38927

Any idea? thanks.

It's possible that enough sockets were opened that the final target process wasn't able to open a socket within that range, although that seems quite unlikely.
Do you have any firewall software running (windows built-in or 3rd party)? Perhaps there's some issue connecting because of that. When you've disabled the global hook, the UI is still running elevated as an administrator. You could try to re-launch the UI as a normal user and see if you have more luck.

I just tried turn off windows built-in firewalls and launch the UI as a normal user but it didn't work.

Can you find the logfile from the GTA5 process? There should be a RenderDoc_app_<date>_<time>.log in your temporary folder, it will be one of those and it will say the executable it's injecting into for each .log. I wonder if it has any messages about failing to bind or listen.
I added a couple of extra log lines that might be helpful. If you're able to build a copy of renderdoc locally, can you try with the code I just pushed? Otherwise it will be in the next nightly build.
Also worst case, if you have successfully injected and captured that's the hard part over - you just have to look in your temporary folder to find them and open them manually. Attaching is convenient and makes it work nicer (and I'd like to fix the problem!) but it's not required.

Hi,
This is what I get using 2016-09-18 nightly build
RenderDoc_app_2016.09.17_21.12.35.log
RENDERDOC:  [21:12:35]             core.cpp( 312) - Log     - RenderDoc v0.32 x64 (b79f170e24f1c9b83b5addc4b080301672088860) capturing application
RENDERDOC:  [21:12:35]   win32_libentry.cpp(  66) - Log     - Loading into C:\Program Files\Rockstar Games\Grand Theft Auto V\GTA5.exe
RENDERDOC:  [21:12:35]            hooks.cpp(  49) - Log     - Loaded and hooked into kernel32.dll, PID 2476
RENDERDOC:  [21:12:35]            hooks.cpp(  49) - Log     - Loaded and hooked into opengl32.dll, PID 2476
RENDERDOC:  [21:12:35]            hooks.cpp(  49) - Log     - Loaded and hooked into d3d11.dll, PID 2476
RENDERDOC:  [21:12:35]            hooks.cpp(  49) - Log     - Loaded and hooked into d3d9.dll, PID 2476
RENDERDOC:  [21:12:35]            hooks.cpp(  49) - Log     - Loaded and hooked into dxgi.dll, PID 2476
RENDERDOC:  [21:12:35]            hooks.cpp(  49) - Log     - Loaded and hooked into d3d12.dll, PID 2476
RENDERDOC:  [21:12:35]            hooks.cpp(  49) - Log     - Loaded and hooked into vulkan-1.dll, PID 2476
RENDERDOC:  [21:12:42]     dxgi_wrapped.cpp( 518) - Warning - Querying IDXGIObject for interface: GUID {7abb6563-02bc-47c4-8ef9-acc4795edbcf}
RENDERDOC:  [21:12:43]    win32_network.cpp(  98) - Warning - accept: 10038
RENDERDOC:  [21:12:43]      d3d11_hooks.cpp( 267) - Log     - Created wrapped D3D11 device.
RENDERDOC:  [21:12:43]   target_control.cpp( 262) - Error   - Error in accept - shutting down server
RENDERDOC:  [21:12:43]     dxgi_wrapped.cpp( 518) - Warning - Querying IDXGIObject for interface: GUID {7abb6563-02bc-47c4-8ef9-acc4795edbcf}
RENDERDOC:  [21:12:43]      d3d11_hooks.cpp( 267) - Log     - Created wrapped D3D11 device.
RENDERDOC:  [21:12:43]     dxgi_wrapped.cpp( 518) - Warning - Querying IDXGIObject for interface: GUID {7abb6563-02bc-47c4-8ef9-acc4795edbcf}
RENDERDOC:  [21:12:43]     dxgi_wrapped.cpp( 518) - Warning - Querying IDXGIObject for interface: GUID {7abb6563-02bc-47c4-8ef9-acc4795edbcf}
RENDERDOC:  [21:15:29]     d3d11_device.cpp(2649) - Log     - Starting capture, frame 3274
RENDERDOC:  [21:15:29]     d3d11_device.cpp(2686) - Log     - Finished capture, Frame 3275
RENDERDOC:  [21:15:29]     d3d11_device.cpp(1705) - Warning - Not serialising texture 2D initial state. ID 5428
RENDERDOC:  [21:15:29]     d3d11_device.cpp(1710) - Warning - Detected Write before Read of this target - assuming initial contents are unneeded.
Capture again with Save All Initials if this is wrong
RENDERDOC:  [21:15:29]     d3d11_device.cpp(1705) - Warning - Not serialising texture 2D initial state. ID 5434
RENDERDOC:  [21:15:29]     d3d11_device.cpp(1710) - Warning - Detected Write before Read of this target - assuming initial contents are unneeded.
Capture again with Save All Initials if this is wrong
RENDERDOC:  [21:15:29]     d3d11_device.cpp(1705) - Warning - Not serialising texture 2D initial state. ID 5440
RENDERDOC:  [21:15:29]     d3d11_device.cpp(1710) - Warning - Detected Write before Read of this target - assuming initial contents are unneeded.
Capture again with Save All Initials if this is wrong
RENDERDOC:  [21:15:29]     d3d11_device.cpp(1705) - Warning - Not serialising texture 2D initial state. ID 5443
RENDERDOC:  [21:15:29]     d3d11_device.cpp(1710) - Warning - Detected Write before Read of this target - assuming initial contents are unneeded.
Capture again with Save All Initials if this is wrong
RENDERDOC:  [21:15:29]     d3d11_device.cpp(1705) - Warning - Not serialising texture 2D initial state. ID 5455
RENDERDOC:  [21:15:29]     d3d11_device.cpp(1710) - Warning - Detected Write before Read of this target - assuming initial contents are unneeded.
Capture again with Save All Initials if this is wrong
RENDERDOC:  [21:15:29]     d3d11_device.cpp(1705) - Warning - Not serialising texture 2D initial state. ID 5474
RENDERDOC:  [21:15:29]     d3d11_device.cpp(1710) - Warning - Detected Write before Read of this target - assuming initial contents are unneeded.
Capture again with Save All Initials if this is wrong
RENDERDOC:  [21:15:29]     d3d11_device.cpp(1705) - Warning - Not serialising texture 2D initial state. ID 5783
RENDERDOC:  [21:15:29]     d3d11_device.cpp(1710) - Warning - Detected Write before Read of this target - assuming initial contents are unneeded.
Capture again with Save All Initials if this is wrong
RENDERDOC:  [21:15:29]     d3d11_device.cpp(1705) - Warning - Not serialising texture 2D initial state. ID 6345
RENDERDOC:  [21:15:29]     d3d11_device.cpp(1710) - Warning - Detected Write before Read of this target - assuming initial contents are unneeded.
Capture again with Save All Initials if this is wrong
RENDERDOC:  [21:15:29]     d3d11_device.cpp(1705) - Warning - Not serialising texture 2D initial state. ID 6348
RENDERDOC:  [21:15:29]     d3d11_device.cpp(1710) - Warning - Detected Write before Read of this target - assuming initial contents are unneeded.
Capture again with Save All Initials if this is wrong
RENDERDOC:  [21:15:29]     d3d11_device.cpp(1705) - Warning - Not serialising texture 2D initial state. ID 6351
RENDERDOC:  [21:15:29]     d3d11_device.cpp(1710) - Warning - Detected Write before Read of this target - assuming initial contents are unneeded.
Capture again with Save All Initials if this is wrong
RENDERDOC:  [21:15:29]     d3d11_device.cpp(1705) - Warning - Not serialising texture 2D initial state. ID 6354
RENDERDOC:  [21:15:29]     d3d11_device.cpp(1710) - Warning - Detected Write before Read of this target - assuming initial contents are unneeded.
Capture again with Save All Initials if this is wrong
RENDERDOC:  [21:15:29]     d3d11_device.cpp(1705) - Warning - Not serialising texture 2D initial state. ID 6384
RENDERDOC:  [21:15:29]     d3d11_device.cpp(1710) - Warning - Detected Write before Read of this target - assuming initial contents are unneeded.
Capture again with Save All Initials if this is wrong
RENDERDOC:  [21:15:29]       serialiser.cpp(1447) - Log     - Compressed frame capture data from 59188672 to 38204179
RENDERDOC:  [21:15:29]       serialiser.cpp(1305) - Log     - Timer File writing - 200.905 ms
RENDERDOC:  [21:15:29]             core.cpp( 917) - Log     - Written to disk: C:\Users\yangky\AppData\Local\Temp\GTA5_2016.09.17_21.11.02_frame3275.rdc
RENDERDOC:  [21:15:32]     d3d11_device.cpp(2649) - Log     - Starting capture, frame 3326
RENDERDOC:  [21:15:32]     d3d11_device.cpp(2686) - Log     - Finished capture, Frame 3327
RENDERDOC:  [21:15:32]     d3d11_device.cpp(1705) - Warning - Not serialising texture 2D initial state. ID 5428
RENDERDOC:  [21:15:32]     d3d11_device.cpp(1710) - Warning - Detected Write before Read of this target - assuming initial contents are unneeded.
Capture again with Save All Initials if this is wrong
RENDERDOC:  [21:15:32]     d3d11_device.cpp(1705) - Warning - Not serialising texture 2D initial state. ID 5434
RENDERDOC:  [21:15:32]     d3d11_device.cpp(1710) - Warning - Detected Write before Read of this target - assuming initial contents are unneeded.
Capture again with Save All Initials if this is wrong
RENDERDOC:  [21:15:32]     d3d11_device.cpp(1705) - Warning - Not serialising texture 2D initial state. ID 5440
RENDERDOC:  [21:15:32]     d3d11_device.cpp(1710) - Warning - Detected Write before Read of this target - assuming initial contents are unneeded.
Capture again with Save All Initials if this is wrong
RENDERDOC:  [21:15:32]     d3d11_device.cpp(1705) - Warning - Not serialising texture 2D initial state. ID 5443
RENDERDOC:  [21:15:32]     d3d11_device.cpp(1710) - Warning - Detected Write before Read of this target - assuming initial contents are unneeded.
Capture again with Save All Initials if this is wrong
RENDERDOC:  [21:15:32]     d3d11_device.cpp(1705) - Warning - Not serialising texture 2D initial state. ID 5452
RENDERDOC:  [21:15:32]     d3d11_device.cpp(1710) - Warning - Detected Write before Read of this target - assuming initial contents are unneeded.
Capture again with Save All Initials if this is wrong
RENDERDOC:  [21:15:32]     d3d11_device.cpp(1705) - Warning - Not serialising texture 2D initial state. ID 5455
RENDERDOC:  [21:15:32]     d3d11_device.cpp(1710) - Warning - Detected Write before Read of this target - assuming initial contents are unneeded.
Capture again with Save All Initials if this is wrong
RENDERDOC:  [21:15:32]     d3d11_device.cpp(1705) - Warning - Not serialising texture 2D initial state. ID 5484
RENDERDOC:  [21:15:32]     d3d11_device.cpp(1710) - Warning - Detected Write before Read of this target - assuming initial contents are unneeded.
Capture again with Save All Initials if this is wrong
RENDERDOC:  [21:15:32]     d3d11_device.cpp(1705) - Warning - Not serialising texture 2D initial state. ID 5783
RENDERDOC:  [21:15:32]     d3d11_device.cpp(1710) - Warning - Detected Write before Read of this target - assuming initial contents are unneeded.
Capture again with Save All Initials if this is wrong
RENDERDOC:  [21:15:32]     d3d11_device.cpp(1705) - Warning - Not serialising texture 2D initial state. ID 6345
RENDERDOC:  [21:15:32]     d3d11_device.cpp(1710) - Warning - Detected Write before Read of this target - assuming initial contents are unneeded.
Capture again with Save All Initials if this is wrong
RENDERDOC:  [21:15:32]     d3d11_device.cpp(1705) - Warning - Not serialising texture 2D initial state. ID 6348
RENDERDOC:  [21:15:32]     d3d11_device.cpp(1710) - Warning - Detected Write before Read of this target - assuming initial contents are unneeded.
Capture again with Save All Initials if this is wrong
RENDERDOC:  [21:15:32]     d3d11_device.cpp(1705) - Warning - Not serialising texture 2D initial state. ID 6351
RENDERDOC:  [21:15:32]     d3d11_device.cpp(1710) - Warning - Detected Write before Read of this target - assuming initial contents are unneeded.
Capture again with Save All Initials if this is wrong
RENDERDOC:  [21:15:32]     d3d11_device.cpp(1705) - Warning - Not serialising texture 2D initial state. ID 6354
RENDERDOC:  [21:15:32]     d3d11_device.cpp(1710) - Warning - Detected Write before Read of this target - assuming initial contents are unneeded.
Capture again with Save All Initials if this is wrong
RENDERDOC:  [21:15:32]     d3d11_device.cpp(1705) - Warning - Not serialising texture 2D initial state. ID 6384
RENDERDOC:  [21:15:32]     d3d11_device.cpp(1710) - Warning - Detected Write before Read of this target - assuming initial contents are unneeded.
Capture again with Save All Initials if this is wrong
RENDERDOC:  [21:15:32]     d3d11_device.cpp(1705) - Warning - Not serialising texture 2D initial state. ID 6485
RENDERDOC:  [21:15:32]     d3d11_device.cpp(1710) - Warning - Detected Write before Read of this target - assuming initial contents are unneeded.
Capture again with Save All Initials if this is wrong
RENDERDOC:  [21:15:32]     d3d11_device.cpp(1705) - Warning - Not serialising texture 2D initial state. ID 6870
RENDERDOC:  [21:15:32]     d3d11_device.cpp(1710) - Warning - Detected Write before Read of this target - assuming initial contents are unneeded.
Capture again with Save All Initials if this is wrong
RENDERDOC:  [21:15:32]     d3d11_device.cpp(1705) - Warning - Not serialising texture 2D initial state. ID 11183
RENDERDOC:  [21:15:32]     d3d11_device.cpp(1710) - Warning - Detected Write before Read of this target - assuming initial contents are unneeded.
Capture again with Save All Initials if this is wrong
RENDERDOC:  [21:15:32]     d3d11_device.cpp(1705) - Warning - Not serialising texture 2D initial state. ID 11186
RENDERDOC:  [21:15:32]     d3d11_device.cpp(1710) - Warning - Detected Write before Read of this target - assuming initial contents are unneeded.
Capture again with Save All Initials if this is wrong
RENDERDOC:  [21:15:32]     d3d11_device.cpp(1705) - Warning - Not serialising texture 2D initial state. ID 11189
RENDERDOC:  [21:15:32]     d3d11_device.cpp(1710) - Warning - Detected Write before Read of this target - assuming initial contents are unneeded.
Capture again with Save All Initials if this is wrong
RENDERDOC:  [21:15:32]       serialiser.cpp(1447) - Log     - Compressed frame capture data from 64325568 to 37600808
RENDERDOC:  [21:15:32]       serialiser.cpp(1305) - Log     - Timer File writing - 165.891 ms
RENDERDOC:  [21:15:32]             core.cpp( 917) - Log     - Written to disk: C:\Users\yangky\AppData\Local\Temp\GTA5_2016.09.17_21.11.02_frame3327.rdc

RenderDoc_replay_2016.09.17_21.16.01.log
RENDERDOC:  [21:16:01]             core.cpp( 309) - Log     - RenderDoc v0.32 x64 (b79f170e24f1c9b83b5addc4b080301672088860) loaded in replay application
RENDERDOC:  [21:16:05]  replay_renderer.cpp(1532) - Log     - Creating replay device for C:\Users\yangky\AppData\Local\Temp\GTA5_2016.09.17_21.11.02_frame3275.rdc
RENDERDOC:  [21:16:05]      d3d11_hooks.cpp( 267) - Log     - Created wrapped D3D11 device.
RENDERDOC:  [21:16:05]     d3d11_replay.cpp(2064) - Log     - Created device.
RENDERDOC:  [21:16:05]  replay_renderer.cpp(1551) - Log     - Created replay driver.
RENDERDOC:  [21:16:06]     d3d11_device.cpp(1090) - Log     - Timer chunk initialisation - 568.749 ms
RENDERDOC:  [21:16:10]    win32_network.cpp( 352) - Warning - Failed to connect to localhost:38920
RENDERDOC:  [21:16:11]    win32_network.cpp( 352) - Warning - Failed to connect to localhost:38921
RENDERDOC:  [21:16:11]    win32_network.cpp( 352) - Warning - Failed to connect to localhost:38922
RENDERDOC:  [21:16:11]    win32_network.cpp( 352) - Warning - Failed to connect to localhost:38923
RENDERDOC:  [21:16:11]    win32_network.cpp( 352) - Warning - Failed to connect to localhost:38924
RENDERDOC:  [21:16:12]    win32_network.cpp( 352) - Warning - Failed to connect to localhost:38925
RENDERDOC:  [21:16:12]    win32_network.cpp( 352) - Warning - Failed to connect to localhost:38926
RENDERDOC:  [21:16:12]    win32_network.cpp( 352) - Warning - Failed to connect to localhost:38927

The relevant part seems to be this:
RENDERDOC:  [21:12:43]    win32_network.cpp(  98) - Warning - accept: 10038
RENDERDOC:  [21:12:43]   target_control.cpp( 262) - Error   - Error in accept - shutting down server

Which happens a 8 seconds after startup. If these are definitely the two logs though, this means the error happened long before you tried to connect in the UI - is that correct? That you started the game, made a couple of captures, and only tried to connect 4 minutes later? 8 seconds is long enough that it could be some kind of timeout, so this might be the first accept() call that is failing. I'm far from a networking expert so I'm just guessing.
It indicates something is going very wrong with the socket connection but I'm at a loss to say what exactly. Especially 10038 which is WSAENOTSOCK when clearly the socket should be fine. My instinct says this points to something else on the system interfering since it's so consistent for you but to my knowledge hasn't happened to anyone else, but it might be some weird edge case.
Can you test by launching a smaller test application normally from RenderDoc (without the global hook), and see if you can attach to it successfully? I'm curious if the problem is limited to the global hook and GTA5, or if it's system-wide for you.
Are you able to build RenderDoc yourself? The next step is to add a lot more debug logging, so I'll put it on a branch which won't go into the nightlies - either you'll need to build a local copy, or I can build one and upload it somewhere.

Hi,
I tested with the Tutorial 1 in Direct3D Samples, it worked fine. The problem seems to be specific for global hooks. I have no problem building RendorDoc

I've pushed up to a branch debug-logging, can you compile from that branch and see what log output you get for the GTA5 process? It should at least give some clue exactly where and when the problem happens, hopefully that will lead somewhere else.
Please take careful note of the logfiles so that you can match the exact ones for both the captured process and the UI together, to get accurate timestamps from both sides of the socket.

Hi,
My work requires some in-depth usages of RenderDoc, I'm going to read the code and hopefully will be able to figure out this problem myself. Thanks for your assistance!

Sure thing, let me know if you need any more help.

I'm not sure why I wasn't able to earlier, but I was able to actually repro this with GTA 5. It turned out to be a GTA 5 specific bug, the application was calling WSACleanup() before it had ever called WSAStartup() - which meant that it destroyed the sockets I had created while hooking in initially.
I fixed it just by hooking those two functions and preventing broken applications from doing anything - it just returns an error value without actually doing the cleanup. Hopefully that should fix it now.

It works now. Thanks!


Master release: veramo library support, yarn 4.3, Pure ES-package compiles

https://github.com/Tonomy-Foundation/Tonomy-ID-SDK/pull/395
https://github.com/Tonomy-Foundation/Tonomy-ID-SDK/pull/396
https://github.com/Tonomy-Foundation/Tonomy-ID-SDK/pull/398
https://github.com/Tonomy-Foundation/Tonomy-ID-SDK/pull/399
https://github.com/Tonomy-Foundation/Tonomy-ID-SDK/pull/401
https://github.com/Tonomy-Foundation/Tonomy-ID-SDK/pull/402
https://github.com/Tonomy-Foundation/Tonomy-ID-SDK/pull/403

:tada: This issue has been resolved in version 0.22.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


An option to set max and min on the price scale would be nice.

Is your feature request related to a problem? Please describe.
Yes, I want to be able to set the price scale's min and max value displayed.
Describe the solution you'd like
chart.setOption({ priceScale: { min: , max:  } })

Related https://github.com/tradingview/lightweight-charts/issues/360#issuecomment-596995263.

chart.setOption({ priceScale: { min: , max: } })

I think it'd better to have such API in price scale itself.

Also, applying price range would force to disable auto scaling. Also, it can't be applied in percentage mode and should throw an error in run-time.
The open question here is what to do with overlay scales - they are always autoscaled, an user can't enable autoscale for them somehow (for non-overlay it might dbl click on price axis for instance).

I think it's fair to disable the auto-scaling option if one wants to use price max and min. Currently, I'm able to scroll on the price scale to keep it fixed.
In the meantime, is there any workaround I can use?

In the meantime, is there any workaround I can use?

No. If you wish, you can try to fix it and provide PR.


TreeNSearch in Position based dynamics(PBD)

Your paper is wonderful， especially the brachless part, really get so much out of it

Background

Recently, I implemented  a rigidbody simulator with PBD, which learned from papers  written by interactive graphics and nvidia

output.webm

But just as you metioned in your paper, uniform grid usually work with particle based method
If I want put two rigid body into the simulator, the difference of size for them can‘t be too large
Because the particle number is in a cubic relationship with object size，if we keep the same particle radius for all, memory will explode
So maybe a hierarchy data structure + mixed radius size  will help and that‘s exactly your paper do in sph
While in your paper you also mentioned TreeNSearch works not very well in the situation that objects move rapidlly

The Question

Is this data structure suitable for Position based dynamics , including rigidbody, cloth and fluid simulation

Hello,
thank you very much for your kind words. We are happy to see that people find our work interesting.
To your particular question: I always suggest to try out ideas. It is very hard to know which method is the best for each application just by thinking about it. That said, I think our approach might indeed suit your application, it is relatively easy to set up so you shouldn't need too much time. However, keep in mind that our target problem is wildly different to yours: we want to find neighbors in very large simulations with millions of particles. For what I can see, you are working on real time simulations and much smaller problem (in terms of amount of data) so you may find other solutions more effective than ours.
Best regards,
José.

Hello,
thank you very much for your kind words. We are happy to see that people find our work interesting.
To your particular question: I always suggest to try out ideas. It is very hard to know which method is the best for each application just by thinking about it. That said, I think our approach might indeed suit your application, it is relatively easy to set up so you shouldn't need too much time. However, keep in mind that our target problem is wildly different to yours: we want to find neighbors in very large simulations with millions of particles. For what I can see, you are working on real time simulations and much smaller problem (in terms of amount of data) so you may find other solutions more effective than ours.
Best regards, José.

Thank you for you advice,  I will try it out and find more potential solution.
Learned a lot from interactive graphics， like the sdf generate Discregrid which I used in my project

More Info

I start from small data and real time simulation by now which is not complicated about modern hardware achitechture
But  large scale and offline simulator will be a long term to acheive
Currently, we are building a system with AI to detect flood , forrest fire，debris flow, so kind of natural disaster
It is really hard to gather such kind of data, so we aim to generate synthetic data by simulation
Now we are using rigidbody simulation to train our robot picking task


Killing a process making ptop exit abruptly

My guess is that pid of the process is not getting picked up by the kill function properly

Just pass the arguments *args,**kwargs to _kill_process()

@vinusankarsiitgn are you sure thats gonna help. args and kwargs are not used in the function anywhere. If it was the case it should not be an intermittent issue or they are passed not always i guess ?

@darxtrix as you rightly said, the kill function does not pass args and kwargs always. But without them you get this issue while killing a process. But with those, I am able to run kill() properly and its working fine. Please see pr #41


Thorough API documentation

The internals of the API should be documented somewhere: what the method calls take, what the return, where to find them, etc.
Right now the website is the only consumer of the API, but that may not always be the case. If someone, say, wanted to create an app that was compatible with the site, it would be very handy to have this kind of reference.
IMO, this could be written in markdown in some top-level docs folder in the repo, but I'm open to suggestions.

Fixed by #71


Add a separate "Status" field to each applicant

Instead of lumping the "Pending" and "Rejected" values into an applicants "role", we should have a separate field called "status" to keep track of an applicant's acceptance progress.
Action Items

[x] Update the user model in backend/src/models/userData.js. "denied" should be moved from "role" into a new enum called "status." Status should also have the options "got_initial_email," "responded_to_email," and "approved."
[x] Update users in the database to have their own status field. Remove the current users in userDatas and add new ones if necessary (there's only 3 in there currently 🤷♀)
[x] Update the ApplicantList component to display the applicant status in the RoleBadge instead of the role (so just change the prop being passed)
[x] Update the component Shared/RoleBadge.jsx to show the correct color based on status. As of now, it should be red for "denied," green for "approved," and yellow for the other intermediate steps.

Possible improvements

It's nice to show an applicant's status in the applicant list on the side, but what about when they're approved? I'd say maybe if an applicant's status is "approved," their RoleBadge in the list should show their role (admin, manager, etc.) instead.

Working!


camerapreview plugin fix

editing this plugin's code will fix an issue on camerapreview's plugin
https://github.com/cordova-plugin-camera-preview/cordova-plugin-camera-preview/issues/369
can this be confirmed by someone else?

Please share your project files on github.
Since this plugin handles the touch events, it seems this modification breaks this plugin behavior.
If you share your project files (or demo project files), I will check it. Otherwise, I don't support it. (Usually I don't support the compatibility with other plugins

i think that already is a demo:
https://github.com/cordova-plugin-camera-preview/cordova-plugin-camera-preview-sample-app
i use ionic3/ang4 but i think it will be the same: adding cordova-plugin-googlemaps will prevent the html to stay above camera

No. I asked the demo app including the camera page and the map page both.

ping.

https://github.com/maxborgatti/camerapreview-vs-maps
use your api keys in config:
    <plugin name="cordova-plugin-googlemaps" spec="https://github.com/mapsplugin/cordova-plugin-googlemaps#multiple_maps">         <variable name="API_KEY_FOR_ANDROID" value="YOUR_API_KEY" />         <variable name="API_KEY_FOR_IOS" value="YOUR_API_KEY" />     </plugin>
comment the camerapreview code if you want to see the html below
      this.cameraPreview.startCamera(this.cameraPreviewOpts).then(         (res) => {           console.log(res);         },         (err) => {           console.log(err);       });       this.cameraPreview.show();
the camera should go below html
    toBack: true,
but it does not until you remove the map plugin

This is the screen record of just built your app.

The demo is ok, and i hope the issue is clear also to you: camera stays on top, ignoring toBack value.
If you remove maps plugin and make bg transparent (i think i'd already set scss like that) you'll se the bug disappear and the camera going back html

The camera plugin and this plugin changes the view order(hierarchy). The both manipulate the click event with the same approach. That's why the both plugin are conflict.
This is not a bug.
You need to remove the map when you want to open the camera.

i did update repo, commenting out map. you can pull and test. nothing changes.
removing plugin like this, fixes (the camera goes back html):

am i missing something?

No. What I mean is you need to execute map.remove() when you oepn the canera

no effects

please feel free to edit demo code your own. also, did you take a look to my suggestion?
https://github.com/cordova-plugin-camera-preview/cordova-plugin-camera-preview/issues/369

Your suggested way breaks this plugin (did you read my commnet?).

Unfortunately this plugin and the camera plugin are conflict. You need to give up one of them.

Fortunately, I fixed this problem on another issue fixing.
https://github.com/wf9a5m75/camerapreview-vs-maps


GDScript: inferred type is used as hard type

Godot version: v4.0.dev.custom_build 35ff38b3d
OS/device including version: windows 10
Issue description:
func _ready():
	var dynamic_type     = "string"
	var integer_type:int = dynamic_type; ## <-- invalid (should be valid)

This isn't a bug, it's correctly telling you that this is incompatible. This will give an error at runtime anyway, so it's better that you catch it in the editor.
Hard type is only for assignment so this:
var dynamic = "string"
dynamic = 3

Should still infer the type as String in the declaration, but should still allow the integer to be assigned.

What error messages does it give? Sounds like it could do with being clearer if possible?

the problem is that when it comes to add control flow between, we can't predict the type of the dynamic variable when it assign
the below infered dyn_var = 2 but at runtime it's node -> should be an error

the below infered dyn_var = Node but at runtime it's int -> shouldn't be an error

Okay, so it's an issue with inference in general. I have an idea how to fix this.

Related to godotengine/godot#43503
What is the correct behavior if a variable is declared as null? If the type is unknown, must it be Variant?


Function for updating the options values using external query.

I'm use this tool in own project, but I have a lot of options.
So, a need use a set of options from database. Then I add this changes for use a external query (in my case sql query) for display options.
Sorry for my english :)

hi @AlexTinbSys
thanks for your work. Unfortunately you've changed build files which are always overwritten based on src files so it would be awesome if you could update them and revert changes in build files.
best,
Jan

Yes, I Know that. But I don't now how make it in src files.
I have all changes and version if you need.
Alex


Large package size due to test binary data

I noticed that this installer is quite large due to the inclusion of test data.
Would it be acceptable to remove the test data from this package?

It takes about 17MB of the 26MB package.

I just removed the testing phase.

Could run the tests during the build

will consider for next update.


Welcome .NET 8

This PR will migrate the overall stack to .NET 8.
Major changes:

7thHeaven will now required the .NET 8 runtime
The installer will now install by default the .NET 8 runtimes

Waiting for https://github.com/actions/runner-images/issues/8797


Upload build logs on error

Upload build logs and temporaries as an artifact when the CI build fails. This will really help debugging.

Implemented in v0.1.34.


Css attr error from "postcss-gap" plugin

Hi there,
I'm having this error with Webpack 5:
Error: Module build failed (from ../node_modules/postcss-loader/dist/cjs.js):
SyntaxError
(1:1) from "postcss-gap" plugin: <css input> Unknown word
> 1 | attr(width)/attr(height)
    | ^

These are the main parts of my setup:
package.json
"devDependencies": {
    "flex-gap-polyfill": "^4.2.0",
    "postcss": "^8.4.30",
    "postcss-loader": "^7.1.0",
    "webpack": "^5.84.0",
  },

webpack.config.js
const FlexGapPolyfill = require('flex-gap-polyfill');

module.exports = (env, argv = {}) => {
    ...

    module: {
      rules: [
        {
          test: /\.(sa|sc|c)ss$/,
          use: [

           ....

            {
              loader: 'postcss-loader',
              options: {
                postcssOptions: {
                  plugins: [
                    [
                      require('autoprefixer'),
                    ],
                    [
                      'flex-gap-polyfill',
                      {
                        flexGapNotSupported: '.no-flexgap',
                      },
                    ],
                  ],
                },
              },
            },

           ....
          ],
        },

    ...
};

main.scss
//https://jakearchibald.com/2022/img-aspect-ratio/
//https://www.andreaverlicchi.eu/aspect-ratio-modern-reserve-space-lazy-images-async-content-responsive-design/
img[width][height] {
  height: auto;
  aspect-ratio: attr(width) / attr(height);
}

The error appears only when I enable your plugin, and with the plugin enabled it disappears only by commenting the line aspect-ratio: attr(width) / attr(height); of the scss file.
What could it depend on?

Hi @frugan-it. Hmm, this is an odd one. I can't recreate the issue when I create an example repo with webpack and postcss-loader.
This is my webpack.config.js file:
module.exports = {
	// ...
	module: {
		rules: [
			{
				test: /\.css$/i,
				include: path.resolve(__dirname, 'src'),
				use: ['style-loader', 'css-loader', 'postcss-loader'],
			},
		],
	},
}

Can you provide a repo so I can test?
As far as I know, the plugin shouldn't be doing anything to the property aspect-ratio. So I wonder if something else is tripping it up, and the error about attr(width)/attr(height) is just a red herring.

Hi @gavinmcfarland, thanks for the support!
I created this test repository https://github.com/frugan-it/flex-gap-polyfill-issue-85.
If you try to comment these lines https://github.com/frugan-it/flex-gap-polyfill-issue-85/blob/master/webpack.config.js#L187-L192 everything works correctly.
I tried to isolate the problem as much as possible, but I don't understand what it could depend on..

So, I've looked into it a bit more.
There is a conflict between sass-loader and a dependency my plugin uses called postcss-values-parser.
sass-loader is removing the spaces between attr(width) / attr(height), which then postcss-values-parser trips over because it's expecting a  space before and after the /. I don't know which is correct in this case, but that's what's causing the issue.
You can try the following to work around it.
Tell flex-gap-polyfill to ignore processing the rule:
img[width][height]{
  /* added by fgp */
  height: auto;
  aspect-ratio: attr(width) / attr(height);
}

Or you can manually apply the polyfill:
img[width][height]{
  /* added by fgp */
  --fgp-height: var(--element-has-fgp) calc(auto + var(--fgp-gap-row, 0%));
  height: var(--fgp-height, auto);
  aspect-ratio: attr(width, 1) / attr(height, 1);
}

I tried to disable the modification that Sass applies but it seems a little unpredictable. I found some others have had difficulty with it too. https://github.com/webpack-contrib/sass-loader/issues/763
Let me know how you get on.

I can probably also release a fix by adding some logic to avoid reading the values like the ones in the aspect-ratio prop as it doesn't need to.

Thanks @gavinmcfarland, sorry for the late reply..
I didn't know you could tell flex-gap-polyfill to ignore some lines, maybe that should be specified in the README?
Anyway thank you, now with this comment it seems to work!

No worries. I initially never saw the need to ignore certain rules, but I remembered the plugin ignores rules it's already processed, which have a comment of * added by fgp */ in them. I'll add more official support for this when I get chance.

I know you created this issue a while ago but I'm just updating this issue.
It should be fixed now because flex-gap-polyfill no longer looks at values in properties such as aspect-ratio.


UNLOAD query with column name containing \b fails

Driver version

N/A as issue is reproducible in redshift query runner through AWS console. Additionally, issue is reproducible through <IP_ADDRESS> version as well.
Redshift version

PostgreSQL 8.0.2 on i686-pc-linux-gnu, compiled by GCC gcc (GCC) 3.4.2 20041017 (Red Hat 3.4.2-6.fc3), Redshift 1.0.78014
Client Operating System

N/A
JAVA/JVM version

N/A
Table schema

CREATE TABLE test_schema.tcn_abackslash4q3ju8a1ml (
    key character varying(50) ENCODE lzo,
    a\backslash` character varying(50) ENCODE lzo
)
DISTSTYLE AUTO;

Problem description

Below select query with table having a column name containing \b works.
SELECT "a\backslash`" FROM "test_schema"."tcn_abackslash4q3ju8a1ml";

However, corresponding UNLOAD command
UNLOAD ('SELECT "a\backslash`" FROM "test_schema"."tcn_abackslash4q3ju8a1ml"') TO 's3://bucket/location/' IAM_ROLE 'arn:aws:iam::1234567890:role/test_role' FORMAT PARQUET REGION AS 'us-east-1' MAXFILESIZE AS 5 MB;

fails with
[42703] ERROR: column "aackslash`" does not exist in tcn_abackslash4q3ju8a1ml

Expected behaviour: UNLOAD select query should have worked as well.
Actual behaviour: UNLOAD select query fails
Error message/stack trace:
Any other details that can be helpful:

JDBC trace logs

Reproduction code

Nothing special about reproduction.

UNLOAD query text requires certain illegal characters to be escaped.
ie if we replace  "a\backslash`" with  "a\\backslash`" in the UNLOAD query then the query will succeed.
UNLOAD ('SELECT "a\\backslash`" FROM "test_schema"."tcn_abackslash4q3ju8a1ml"') TO 's3://bucket/location/' IAM_ROLE 'arn:aws:iam::1234567890:role/test_role' FORMAT PARQUET REGION AS 'us-east-1' MAXFILESIZE AS 5 MB;


Reverses removal of default args

Reverses the removal of default args for Mariner images. Reverts the changes made to build_temurin
Adds in a default arg for Ubuntu. Also keeps the workaround suggested for this image.

Would like to hold off merging this PR until @brunoborges has reviewed.


[docs] Update main README Golang version build requirement to v1.20

What does this PR do?
Nit fix of an outdated Golang version requirement text in the main README so that it now matches the actual build system version (v1.20).
Motivation
Outdated documentation
Additional Notes
N/A
Possible Drawbacks / Trade-offs
It's theoretically possible that someone might be able to build the agent on 1.18 and/or 1.19 but we don't verify that level of backwards compatibility.
Describe how to test/QA your changes
N/A
Reviewer's Checklist

[x] If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
[ ] Use the major_change label if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.
[ ] A release note has been added or the changelog/no-changelog label has been applied.
[ ] Changed code has automated tests for its functionality.
[x] Adequate QA/testing plan information is provided if the qa/skip-qa label is not applied.
[x] At least one team/.. label has been applied, indicating the team(s) that should QA this change.
[ ] If applicable, docs team has been notified or an issue has been opened on the documentation repo.
[ ] If applicable, the need-change/operator and need-change/helm labels have been applied.
[ ] If applicable, the k8s/<min-version> label, indicating the lowest Kubernetes version compatible with this feature.
[ ] If applicable, the config template has been updated.

Failing test (Serverless Integration Tests / test) is unstable on main right now. Merging.


[Mixed_precision] Model#call() behavior is different when using tf.Tensor input and when using tf.Variable input.

System information

OS: colab (Ubuntu 18.04.5)
Where TensorFlow installed from : pre-installed in colab
TensorFlow version: 2.4.1
Python version: 3.7.10
GPU model and memory: Tesla K80, 12GB

The current behavior
On default (float32) policy environment, I have to load and use a keras model that is loaded from a h5 file that was created with mixed_float16 policy.
When using tf.Variable instead of tf.Tensor as input value to model, a error bellow is occurred.
ValueError: Incompatible type conversion requested to type 'float32' for AutoCastVariable which is casted to type 'float16'

I want to calculate the gradient with respect to the input value and update the input value itself iteratively.
To do so, the input value needs to be tf.Variable.
The expected behavior
I believe that the behavior of both (tf.Tensor and tf.Variable) should be same, that's, the error should be NOT occurred.
Standalone code to reproduce the issue
The steps for reproducing:

Set mixed_float16 policy
Create a model file
Set float32 (default) policy
Load model and When using tf.Tensor for input of model that is loaded from h5 file, Model#call() will NOT throw the error.
Load model and When using tf.Valiable for input of model that is loaded from h5 file,Model#call() will throw the error.

I've uploaded a notebook to reproduce the error:
https://gist.github.com/keisen/087713c2e547b05a6867506ea5402b93
Other info / logs
N/A
Thanks!

Was able to reproduce the issue in TF 2.4 and Nightly versions. Please find the gist here. Thanks!

@keisen,
AFAIK, this behavior is expected because Tensorflow Variables are used when the values are not constant and if they change continuously, like the Weights in a Model. They are not used for Inputs  to the Model because Inputs to a Model is a Tensor, not a Variable.
What do you think?

@rmothukuru , Thank you for your response!
I've been implementing a library (tf-keras-vis) that provide Model Feature Visualization.
This algorism need to calculate the gradient with respect to the input value and to update the input value itself iteratively.
I believe, to do so, the input value needs to be tf.Variable, not tf.constant.
Since version 1.x, Tensorflow has helped realize this algorism!
So I expect Tensorflow will help realize it even if it adopts mixed-precision mechanism.
Thanks!

@keisen The idea still applies that the inputs to keras layers needs to be constant
There are multiple ways to achieve this, but the one that involves fewer codes is to have tf.Variable in that layer to track the inputs.
i.e.
def call(self, inputs):
        self.my_tf_var.assign(tf.cast(inputs,self.variable_dtype))
        ...

And then, you can take the gradient with respect to this my_tf_var and applies updates to the appropriate tf.Variable that suits you purpose, maybe the variables in other layers.
Please see if this would help

@laplacericky , Thank you for your reply.
I didn't understand what you said.
Our library receives user's model instance, and then calculates the features of it with gradients.

There are multiple ways to achieve this, but the one that involves fewer codes is to have tf.Variable in that layer to track the inputs.

Do you mean that our library have to re-build our user's model and replace target layer to be containing a variable instance?, or we have to define Input layer class that have a tf.Variable attribute?
In any cast, I don't think it's a good idea.
Could you explain that in a little more detail?
Thanks!

@keisen I am just replying to your comment,

This algorism need to calculate the gradient with respect to the input value and to update the input value itself iteratively.
I believe, to do so, the input value needs to be tf.Variable, not tf.constant.

And actually tensorflow can get gradient with any possible tensors and I was just suggesting ways to achieve it. Please forget that if you find confusing.
After viewing your gist, I guess this is what you want to do.
input_value = tf.Variable(tf.random.uniform((1, 224, 224, 3), dtype=tf.float32))
model = tf.keras.models.load_model('model-with-mixed_float16-policy.h5')
with tf.GradientTape() as g:
   Loss=objective_function(model(input_value.value()))

dL_dinput_value=g.gradient(Loss,input_value)

This is how you can get gradient with respect to the input_value while still enjoying mixed_precision speed up of the model, and, without error message. Then you can take the dL_dinput_value and apply update back to input_value which is a variable.

@laplacericky , Thank you for your great reply!

This is how you can get gradient with respect to the input_value while still enjoying mixed_precision speed up of the model, and, without error message. Then you can take the dL_dinput_value and apply update back to input_value which is a variable.

I have tried the way you suggested, and tested for  various situations, and then understood this is the best for us.
To be honest, at first, I thought that it was pretty tricky. However it has had no problem.
Thank you so much!
Best regards.

@laplacericky , I reopened this because of facing a issue.
It's that the result of the method you proposed and the result of the method adopted by our library are different.
Please see the notebook below for details.
https://gist.github.com/keisen/63724e83f843bc8585ec1c97d68b824e
Assuming one of them is the wrong value, which it is?
We're investigating the cause, but we don't know that for now.
Anyway, to avoid this or any similar problem, we want to understand the problem enough.
Thanks!

@keisen It is because tf.keras.optimizers.Adam() is stateful by default. If a new instance of tf.Variable is passed into it every time, it cannot apply the correct stateful effect on the variable like moment estimate, etc, because it would be treated as if it was a separate and new variable. Therefore, the same instance of variable has to be passed into it. You can use tf.keras.optimizers.SGD() with zero momentum and the two versions of codes will give the same results.

Thank you for your quick response!
I didn't know that. You're amazing!
Thanks!


Styled Decorator

Could you add in the following code where appropriate:
styled.decorator = (strings, ...values) => (Component) => styled(Component)(strings, ...values);

So that we can begin using styled-components in the following way:
@styled.decorator`
    padding: 10px;
    background: blue;
    font-size: 12px;
`
export class SomeThing extends React.Component {
    render() {
        return
Hello World
;
    }
}

It would look much cleaner than writing:
class SomeThingComponent extends React.Component {
    render() {
        return
Hello World
;
    }
}

export const SomeThing = styled(SomeThingComponent)`
    padding: 10px;
    background: blue;
    font-size: 12px;
`

In my opinion there is no need to support a HOC or a decorator because that's a pattern we don't recommend to use with styled-components. What speaks against this version for you?
const Text = style.div`
    padding: 10px;
    background: blue;
    font-size: 12px;
`

export class SomeThingComponent extends React.Component {
    render() {
        return <Text>Hello World</Text>;
    }
}

This way you don't need to pass a classname down to a component which is a cleaner way to use styled-components.

Sometimes one might not want to create an entirely separate  component class if it will only be used in that one place. Also imagine if the styled component takes say 10 different arguments which would determine the style. In that case: which would be easier:
This:
const Text = styled.div`
    height: ${{height} => height}px;
    width: ${{width} => width}px;
    color: ${{color} => color};
    position:  absolute;
    top: ${{offset} => offset * 2}px;
    left: ${{offset} => offset * 4 + 3}px;
`

class SomeThingComponent extends React.Component {
    render() {
        return <Text height={this.props.height} width={this.props.width} color={this.props.color} offset={this.props.offset}>Hello World</Text>;
    }
}

Or this;
@styled.decorator`
    height: ${{height} => height}px;
    width: ${{width} => width}px;
    color: ${{color} => color};
    position:  absolute;
    top: ${{offset} => offset * 2}px;
    left: ${{offset} => offset * 4 + 3}px;
`
class SomeThingComponent extends React.Component {
    render() {
        return
Hello World
;
    }
}

You can also spread the props into the Text component:
class SomeThingComponent extends React.Component {
    render() {
        return <Text {...props}>Hello World</Text>;
    }
}

Which makes the first example of you not much longer or complicated then the example with the decorator.

That may be so, but that doesn't solve the problem of needing to create an entirely separate component class. Someone might not want to do that.

Your solution also creates another problem. What if within those props, there is a onClick function passed, and the developer wants that function bound on something other than the Text component.
With the decorator solution, they could do the following:
@styled.decorator`
    ...
`
class SomeThing extends React.Component {
    render() {
        return
<button onClick={this.props.onClick}>Hello World</button>

    }
}

but with your solution:
class SomeThing extends React.Component {
    render() {
        return <Text {...props}><button onClick={this.props.onClick}>Hello World</button></Text>;
    }
}

this would have unintended consequences.

This would be the solution:
class SomeThing extends React.Component {
    render() {
        const { onClick, ...props } = this.props
        return <Text {...props}><button onClick={onClick}>Hello World</button></Text>;
    }
}

I don't think we will support decorators because there was already a discussions about HoC. @mxstbr said at https://github.com/styled-components/styled-components/issues/316#issuecomment-267761139 that we will not support them with the explanation

that the core idea behind styled-components is that you couple DOM nodes to their styles to enforce the presentational/container component split.

Because decorators are basically HoCs I think we will not support them as well.

If the decorator would only be one line, why not support that one line? It shouldn't be too big of an increase to maintain. I can maintain it if nobody else wants to.
If the answer to that question is the philosophy for styled-components dictated by @mxstbr above, then why are you supporting this?
styled(SomeThing)`
    color: black;
    margin-left: ${props => props.leftMargin}px;
`

This is basically creating a higher-order component.
a higher-order component is a function that takes a component and returns a new component.

That may be so, but that doesn't solve the problem of needing to create an entirely separate component class. Someone might not want to do that.

Why is creating a separate component a problem that needs to be solved?  Performance issue? Code aesthetics?  Just trying to understand the motivation 😄

Code aesthetics and readability.

I can create the PR.

I don't think we're going to support this officially I'm afraid, for the reasons stated above. I'm not convinced this adds any value to the library, in fact I think it takes away from the value of using it.

I really like the idea as well 👍  it would make the code cleaner (less components to declare).

I also like the idea. It can be a sepparate package on NPM that adds more sugar to styled-components.

FWIW, I just do this:
// with_styles.js
import styled from 'styled-components';

export default function (strings, ...items) {
    return function (WrappedComponent) {
        return styled(WrappedComponent)(strings, ...items);
    };
}

import with_styles from './with_styles';

@with_styles`
    border: 2px dotted lime;
`
class MyComponent extends React.PureComponent {
    // ...
}

It's simply not possible and not supported, because it would allow users to easily go against or enforced best practices and methodologies.
By default we do offer passing in any component into the styled factory function, and that can be used as an escalation e hatch or even to make this possible with a helper, but it's mainly for complex stacks of components and third party components.
It's not recommended to use this frequently, as building up your component structures from bottom to top leads to cleaner architectures that scales. At the bottom you'll find pure presentational components, above them structural ones, and at the top container/smart components. This can of course be nested and combined in different ways.
But by allowing this pattern by default, we'd be recommending to put the presentational components, like a stylesheet, at any position of this component stack, which is less desirable.
So if you really want to do this, we're not stopping you. But try to keep this in mind, and we believe you'll likely find more scalable styling code as a result.


Wrong url when downloading attachments

Using a built of 7.x of confluence, looks like attachments are building downloaded with the '/wiki/' prefix. Removing that fixes it for me

Nothing out of the ordinary.  Running a local instance temporarily. It's
probably a versioning issue
On Thu, Aug 18, 2022, 8:25 AM Gergely @.***> wrote:

This works for me on my confluence cloud instance, are you doing anything
non-standard?
—
Reply to this email directly, view it on GitHub
https://github.com/gergelykalman/confluence-markdown-exporter/issues/22#issuecomment-1219427675,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAPCIGN5NBX42AYIZUKA2W3VZYTQBANCNFSM56MJJBLQ
.
You are receiving this because you authored the thread.Message ID:
@.***
com>

Ok, let me know if this persists for you and I can create a fix. I will leave this open in case someone else has the same problem. I have no idea if this is common or not.

the specific version is 7.13.2. still an issue

Hi,
just wanted to report that I have the same issue with a self-hosted instance of confluence. I've removed the /wiki/ prefix as suggested by @spyhunter99  and it works for me too.
Thanks for providing this package!

If you can send me a patch or a pull request I'd be happy to merge this.


Fix lvalue npy_file heap corruption in MSVC (was Pair allocator allocation and deallocation)

std::allocator supports combine or optimize away heap allocations
beyond ::operator new, which means, they use the same heap only
when they use heap, but they may not be using heap.  So it's
reasonable for MSVC to require pairing new and delete, allocate
and deallocate.
fixes: QuantStack/xtensor-io#59

Changed the title to reflect the symptom.  Explanation is in https://github.com/QuantStack/xtensor-io/issues/59#issuecomment-515750472

makes a lot of sense. Thanks for this PR!


Add Github Changelog

The idea is to replace Weekly Report with a Changelog that will document all of the merged actions on Github. The file will be updated every month (instead of current every week) and with help of Docusaurus plugin will display all of it on Developer Portal.
Preview:

@rphair it's a proposal for versioning: .. that uses .. that we thought might make more sense for ongoing things like the developer portal instead of doing V1.1, V1.2 etc


bin/setup process fails

Description

https://docs.shopware.com/en/shopware-platform-dev-en/system-guide/installation?category=shopware-platform-dev-en/system-guide
> bin/setup

Database password:
 >

 ! [NOTE] Checking database credentials

 ! [NOTE] Running post installation tasks

error:
PHP Fatal error:  Uncaught TypeError: Argument 1 passed to Symfony\Component\Process\Process::__construct() must be of the type array, string given, called in development/bin/setup on line 37 and defined in development/bin/vendor/symfony/process/Process.php:141

Possible Solution

edit bin/setup
line 37
$process = new Process(['php', 'psh.phar', 'install']);

Is fixed with https://github.com/shopware/development/commit/b372df485a37c0f3090d32276a64b686f87c32af


how to get component instance from manager

Type of question
community best practice to implement a specific feature
Question
I want to implement web ui which shows some useful information based on custom resources data. There are two CRD resources: crdA and crdB to display in single interface. Here is what I did:

Added two CRD controllers (pkg/controller/crdA, pkg/controller/crdB) to watch for these resources.
Created "web ui" instance using Runnable interface:

	if err := mgr.Add(&ws.WebServer{}); err != nil {
		log.Error(err, "")
		os.Exit(1)
	}

Want from CRD controllers to trigger webui instance methods when create/update/delete events come but can't understand how CRD controller gets webui instance from manager

Questions are:

is it the recommended way to inject instances to controller or better one exists?
how can I inject webui instance to controller so controller can use webui methods? looks like I've missed something due to my skills or lack of documentation

Thank you.

H @afoninsky,
I am not sure if I understood properly your question. Shows that you'd like to read the CR of some CRD applied in the cluster and show this data in some web project/UI. Am I right?
Note that the goal of the operators is a simple way to say, just to better explain my idea here, is to manage data/objects in the cluster so it will do CRUDS (create/read/update/delete) the ks8, OCP, and other third-party APIs objects in the reconcile method. If you would like to read an object and show the data in another project ( e.g a web app ) you may solve this need by calling a REST API endpoint of your project/service which will receive this data and store it in you solution DB to show in some UI.
Note that the watches are like observers. They will trigger the reconcile if they check that the KIND/Object watched was created/update/delete in the cluster.
Also, I'd like to recommend you follow and check the Getting Started example which is very fast just for you get a better idea of how the things work if you did not it yet and here you can see an example of an operator project using a REST API.
I hope that it is the info that you are looking for.

Yes you do understand me correctly.
Thank you for your response. Everything is clear so far.


The library should not throw ArgsParsingException when building parser with invalid configurations.

The library should not throw ArgsParsingException when building parser with invalid configurations.
Please think the following questions:

What kind of error does ArgsParsingException represent?
When do you throw ArgumentNullException, ArgumentException and ArgumentOutOfRangeException?

Fixed, change ArgsParsingException to internal, 3a14f68f22b817fc2638990f361bd4240dc63fc8


lxd/resources: Handle ethtool not supported

Signed-off-by: Stéphane Graber<EMAIL_ADDRESS>

@tomponline good to go

Lgtm!


Alsa sound card and channel

Hi, I had found this project recently, I didn't know how to I check which soundcard and channel that I have, I really hope that I can make part of my volume() code into C.

Sorry, what?

/* alsa sound */
static const char soundcard[] = "PCM";
static const char channel[]   = "0";

How do I check which soundcard and channel I should be using, I am using an rpi2.

Oh, now I get it! :smile:
I think it should be like this on most systems:
/* alsa sound */
static const char soundcard[] = "default";
static const char channel[]   = "Master";

Yeah, I tried that, but it didn't work. I think one of the option should be PCM and the other one have a different value. For mine:
vol = runcmd("amixer get PCM | grep -o '[0-9]*%'");

I assume you only have one soundcard, thus it should be like this:
/* alsa sound */
static const char soundcard[] = "default";
static const char channel[]   = "PCM";

Tell me if it works with these settings! :wink:

@drkh5h Thanks a lot, it works, but the number of the volume is just a bit weird (-425%). The temp is broken but I doesn't care about that. Now I am going to check how do you get the cpu and ram usage.

No problem @pickfire! :wink:
But that number is very strange... Maybe it has to do with the alsa version? Which one do you use?

> sudo pacman -Qi alsa-
alsa-firmware  (1.0.29-1)  alsa-lib  (1.1.0-1)  alsa-oss  (1.0.28-1)  alsa-plugins  (1.1.0-2)  alsa-utils  (1.1.0-1)

I just saw, that the PCM channel has 2 values? I think you will have to use it with Master... Just set PCM to 100% and change the volume via Master.

What do you mean? Can you please show me, I don't have a lot of experience with alsa.

Ok, the PCM channel in alsa is a "sub-channel" of Master, so if you set PCM to the max (via alsamixer) you can control the volume via the Master channel. Do you get it now? :wink:

I always have the "Speaker", "Headphone" and "PCM" channels on 100% and control the volume via the "Master" channel.

@drkh5h Ah, it seems like it is working now, how do you normally set the volume using command line?

It seems like it drops 25% each time I lower the volume once.

@pickfire I just use the command line tool "alsamixer"

@pickfire use "+" and "-" keys instead of arrows?

Okay, it seems like you have a site like I do, the cluster article looks interesting but I really hope that it can have more information.


Local llama

Fixes # No Llama-CPP llm available
Note, I'd like to know where I need to contribute a basic example for the docs, I look forward to discussing.

Whoa I was just about to start looking at this! Yes this would be awesome!

I think this package might be a better choice as it's more established? https://github.com/Atome-FE/llama-node

@jacoblee93 k I'll take a look and update, I just happened to be playing with node-llama-cpp, I'll we work the library. BTW for docs where is a good point to add the appropriate page?

No worries, was just wondering!

np, I just took a look over the llama-node repo, it looks like they are using a back level llama.cpp so currently only support ggml models not gguf. Although with llama.cpp going through internal changes gguf support will be in flux for a bit. This will need a close eye on updates!

BTW I'm using a env variable LLAMA_PATH for the test code so the test has a level of portability. As a result I added the env var to .env.example even though it's only used for the tests. I was not 100% sure that was the correct approach.

Hey @nigel-daniels, I bumped the package you're using to 2.1.0 and changed a few things - however I got stuck trying to run a model locally - kept getting:
MacBook-Pro:llama.cpp jacoblee$ python3 convert.py models/7B/
Loading model file models/7B/consolidated.00.pth
Traceback (most recent call last):
  File "/Users/jacoblee/langchain/llama.cpp/convert.py", line 1172, in <module>
    main()
  File "/Users/jacoblee/langchain/llama.cpp/convert.py", line 1120, in main
    model_plus = load_some_model(args.model)
  File "/Users/jacoblee/langchain/llama.cpp/convert.py", line 1042, in load_some_model
    models_plus.append(lazy_load_file(path))
  File "/Users/jacoblee/langchain/llama.cpp/convert.py", line 744, in lazy_load_file
    elif struct.unpack('<Q', first8)[0] < 16 * 1024 * 1024:
struct.error: unpack requires a buffer of 8 bytes

Can you verify the updated package version works? And any ideas/other guides that could be helpful to link in the docs

I also just tried out 2.1.0 as it adds temperature to the model parameters, however it looks like a typo in the index.ts broke things, I just submitted a PR over there. I'll update when it's fixed and update their PR with that and the guide to getting a llama2 model in place.

Thank you, appreciate the followup!

Ok just added a commit with an updated (working!) node-llama-cpp, also gave detailed instructions to converting the Llama2 model and quantizing it. Afaik the model you tried out was the base download from Meta, you will need to run it thru the llama.cpp conversion, the quantizing then makes it way smaller :)
With the new version of node-llama-cpp there is support for temp, and some added properties for the call, so I added LlamaCppCallOptions, hopefully that is the correct way to do this.

I think I was trying to compile with metal support - seems to be working properly with your guide! Thank you!

It's very slow though - might be good to include some bare-metal instructions at some point, but that can come later.

Build failure looks unrelated, I'll figure it out!

@nigel-daniels were you able to get this to build with GPU/metal support?

There is an option for node-llama-cpp to run a download to install a metal or cuda version of llama.cpp, npx node-llama-cpp download —metal. read me. I can always add a mention to the docs.

I couldn't seem to get it to work - kept getting the above error.
If you found a reliable set of instructions would you be up for adding them?

@jacoblee93 I think the error you get is unrelated to node-llama-cpp.
Try downloading and running this model with the latest version of node-llama-cpp: https://huggingface.co/TheBloke/Yarn-Llama-2-7B-128K-GGUF/blob/main/yarn-llama-2-7b-128k.Q5_K_M.gguf


Memory Usage of a model

I'd like to have a method which returns the needed memory for a model since the allocated VRAM does not reflect the actual usage.

@Arktius
Please provide details about what platform you are using (operating system, architecture). Also include your TensorFlow version.Please, fill issue template.
Do you have any use case that requires the feature you are interested in? Please feel free to submit a PR if you have use cases that supports that feature.Thanks!

Microsoft Windows [Version 10.0.18362.418]
Nvidia 2060 Super
TF version 2.0.0
Are you willing to contribute it (Yes/No): Don't know yet.

Who will benefit with this feature?

Everyone who's interested in optimizing lots of models while logging needed memory.
Everyone who wants to shift an application to another machine with a different hardware setup.

The problem is that the following commands do not free the allocated memory.
tf.compat.v1.reset_default_graph()
tf.keras.backend.clear_session()
gc.collect()

One can use
gpu = tf.config.experimental.list_physical_devices('GPU')
tf.config.experimental.set_memory_growth(gpu[0], False)

to give as much memory as the GPU needs. Nevertheless, the allocated memory is correctly displayed only for a single model. After training several models, the allocated memory that is displayed by nvidia-smi is the one of the largest model.
How can I submit a PR(pull request)?

For submitting a pull request see https://www.tensorflow.org/community/contribute/code

Hi @Arktius ! Does get_memory_usage api resolve this api? You can add this before model training and get memory usage. Thanks!


Amount transformer error

I have an account with balance of 0.02 Near, so when I try to get balance it throw me error in the method "static String yoctoNearToNear(String yoctoNearAmount)"
The network response is succesfully:
Get response status code(200)Response body ({jsonrpc: 2.0, result: {amount:<PHONE_NUMBER>0000000000000, block_hash: ErnpsB3LVDtQVG18wZDXbBp5y54byvj6hWKZQqJKf8zo, block_height: 132312843, code_hash:<PHONE_NUMBER>1111111111111111111111, locked: 0, storage_paid_at: 0, storage_usage: 182}, id: dontcare})
But the transformer throw:
RangeError (end): Invalid value: Not in inclusive range 0..23: -1

I fixed it in 1.0.0-beta.9 version , pls make update


⚠ sandbox-api.piste.gouv.fr healthcheck has degraded performance

In c01b0c2, sandbox-api.piste.gouv.fr healthcheck (https://sandbox-api.piste.gouv.fr/cassation/judilibre/v1.0/healthcheck) experienced degraded performance:

HTTP code: 200
Response time: 2743 ms

Resolved: sandbox-api.piste.gouv.fr healthcheck performance has improved in ce8f83a.


v7 can support elasticsearch 8.0？thanks

Somehow. You can try to set the REST API compatibility headers as described in REST API compatibility

we can't, more details here


docs: small simplification and added comments in the mangling grammar doc.

@swift-ci smoke test and merge


Openlane flow fails in LVS Stage

Description
This block is picked from caravel design and I am facing LVS Issue is specific to this block. I have check the LVS in lef and gds option, both are showing similar failure
LVS reports:
net count difference = 175
device count difference = 65
unmatched nets = 21
unmatched devices = 48
unmatched pins = 0
property failures = 0
Total errors = 309
Expected behavior
Expected clean LVS
Environment
dinesha@lenovo-i3-10100-07IMB05:~/workarea/efabless/MPW-7/OpenLane$ python3 ./env.py issue-survey
Kernel: Linux v5.15.0-46-generic
Distribution: ubuntu 20.04
Python: v3.8.10 (OK)
Container Engine: docker v20.10.17 (OK)
OpenLane Git Version: b6bacc9d1ab469917fda7ceea61ea3a18984b818
pip: INSTALLED
python-venv: INSTALLED
---
PDK Version Verification Status: OK
---
Git Log (Last 3 Commits)

b6bacc9 2022-08-24T21:21:29+02:00 Build Script Fixes (#1283) - Mohamed Gaber -  (HEAD -> master)
f0f6055 2022-08-24T19:36:18+02:00 Remove `-echo` flags from `read_sdc` (#1284) - Anton Blanchard -  ()
9452129 2022-08-20T13:41:59+02:00 Fix 'run_yosys' invocation during -synth_explore (#1278) - meta -  ()
---
Git Remotes

origin	https://github.com/efabless/OpenLane.git (fetch)
origin	https://github.com/efabless/OpenLane.git (push)

Reproduction Material
Here is small test case
test.tar.gz
34-digital_pll.lef.log
34-digital_pll.lvs.lef.log
cd test/openlane
make digital_pll
Logs
[WARNING]: Skipping Tap/Decap Insertion.
    while executing
"flow_fail"
    (procedure "quit_on_lvs_error" line 12)
    invoked from within
"quit_on_lvs_error -log $count_lvs_log"
    (procedure "run_lvs" line 79)
    invoked from within
"run_lvs"
    (procedure "run_lvs_step" line 10)
    invoked from within
"[lindex $step_exe 0] [lindex $step_exe 1] "
    (procedure "run_non_interactive_mode" line 52)
    invoked from within
"run_non_interactive_mode {*}$argv"
    invoked from within
"if { [info exists flags_map(-interactive)] || [info exists flags_map(-it)] } {
    if { [info exists arg_values(-file)] } {
        run_file [file nor..."
    (file "/openlane/flow.tcl" line 401)
make: *** [Makefile:44: digital_pll] Error 1
```

@dineshannayya There are no fill,  decap, or vpwrvgndtap cells in the layout.

@d-m-bailey  Sorry, I wrongly copied some of the constraints from top-level.  We can close this issue

@dineshannayya @d-m-bailey  Sorry，I met the same error and I have little experience of this situation. I check the detail log of lvs, it certainly because the decap cells in the layout, but how can I interfere with this process, please give me some specific methods. thank you very much. Do I need to check some specific parameter or check my design.

@hello-eternity Can you post your log files on the slack #lvs channel?


Support Databox API version 3

Update SDK to support API version 3
changes:

[ ] implement POST /metrickeys
[ ] update GET /lastpushes to support paging
[ ] implement GET /lastpushes/{id} to return specific push
[ ] implement DELETE /data
[ ] handle new format & exceptions

Coverage remained the same at 96.667% when pulling 1040ca273a6018face336232f1108c39759cec6e on pushapi-v3 into fdd61bf43c764b2c2a9ceaa4a2960e77fe6d303e on master.

Coverage remained the same at 96.667% when pulling 1b011aa932a9794be93617bccce36a3122972558 on pushapi-v3 into fdd61bf43c764b2c2a9ceaa4a2960e77fe6d303e on master.

Coverage decreased (-12.9%) to 83.784% when pulling 9b2238b054e300723fa8abb4ec2ae97cc5e31c40 on pushapi-v3 into fdd61bf43c764b2c2a9ceaa4a2960e77fe6d303e on master.

Coverage decreased (-19.2%) to 77.5% when pulling 4d6c9d4f3cb7e84ea0345491e4a2d58ca225c51e on pushapi-v3 into fdd61bf43c764b2c2a9ceaa4a2960e77fe6d303e on master.

Coverage decreased, income increased. 👍

Coverage decreased (-19.2%) to 77.5% when pulling 503745559f1ddc391995aac822e78ada88ac142c on pushapi-v3 into fdd61bf43c764b2c2a9ceaa4a2960e77fe6d303e on master.

Coverage increased (+3.3%) to 100.0% when pulling 097b6ffecc5f1be4291e5672faed1506b06c409d on pushapi-v3 into fdd61bf43c764b2c2a9ceaa4a2960e77fe6d303e on master.


Allow AP over-bookings when marking an Arrival

AP beds can now be overbooked for manual Bookings - this was missed for arrivals though

 Allow overbookings on Arrivals for AP Bookings


Immortal rat

I killed the rat in the first chamber. The rat is still there, so I tried to kill it again executing the file again. The rat is still alive.

I could rm the rat script once it's killed, but I thought the users might want to inspect the scripts later on. I guess I could just hide it or move it somewhere else.

Maybe rename it to rat_dead and manage a way to make the executable check itself if is dead?


Ublox_gnss_node not publishing odometry

Hello there!
I was trying to check what is inside the odom messages but it shows no info, is not being publish but is declarated, I was trying changing booleans as CFG_ODO_USE_ODO/COG to true but still nothing.
Could you please point me out on how to see the odometry calculated?
thanks a lot.

Try setting this parameter CFG_MSGOUT_UBX_NAV_ODO_USB to say 10 either in the launch file, via RQT or command line

Could you give me an example on how to do it in command line? I try this:
ros2 param set /ublox_dgnss CFG_MSGOUT_UBX_NAV_ODO_USB:=10
with the node going. the answer is :the following arguments are required: value

Have a look at the sample launch files. Need to copy one and set the values for your environment. That will be easier then setting them all with ros2 run

Yes, you are right, better with the launch file.
I got the /fix publishing but at a rate of 2 messages / minute, or even less. in the other hand, nav_status publishes every 3-4 seconds.
On my i set those values, is there anything wrong?
params = [{'CFG_USBOUTPROT_NMEA': False},
{'CFG_RATE_MEAS': 100},
{'CFG_RATE_NAV': 1},
{'CFG_MSGOUT_UBX_NAV_HPPOSLLH_USB': 1},
{'CFG_MSGOUT_UBX_NAV_STATUS_USB': 5},
{'CFG_MSGOUT_UBX_RXM_RTCM_USB': 1},
{'CFG_MSGOUT_UBX_NAV_COV_USB':1},
{'CFG_MSGOUT_UBX_NAV_ODO_USB':1}]
what can I do to get a publish rate as /ubx_nav_hp_pos_llh

Geoff created that node to publish NavSatFix. I don't use it myself.
Looking at the code
https://github.com/aussierobots/ublox_dgnss/blob/main/ublox_nav_sat_fix_hp_node/src/ublox_nav_sat_fix_hp_node.cpp￼
ublox_dgnss/ublox_nav_sat_fix_hp_node/src/ublox_nav_sat_fix_hp_node.cpp at main · aussierobots/ublox_dgnss
github.com
It needs to receive a Ubx Nav Status and Ubx Nav Cov then it will allow the next UBX Nav HP Pos LLH to be published as the Nav Sat Fix.
This might be too restrictive. Have noticed that Ubx Nav Status is a lower priority message.
Maybe create a local node and try commenting these lines out where the have_recd_ variables are set to false;
https://github.com/aussierobots/ublox_dgnss/blob/8e72b574aec3d38aa2a1bb73b1927035538979ff/ublox_nav_sat_fix_hp_node/src/ublox_nav_sat_fix_hp_node.cpp#L95￼
ublox_dgnss/ublox_nav_sat_fix_hp_node/src/ublox_nav_sat_fix_hp_node.cpp at 8e72b574aec3d38aa2a1bb73b1927035538979ff · aussierobots/ublox_dgnss
github.com

On 11 Oct 2023, at 12:13 am, miguelao33 @.***> wrote:
Yes, you are right, better with the launch file.
I got the /fix publishing but at a rate of 2 messages / minute, or even less. in the other hand, nav_status publishes every 3-4 seconds.
On my i set those values, is there anything wrong?
params = [{'CFG_USBOUTPROT_NMEA': False},
{'CFG_RATE_MEAS': 100},
{'CFG_RATE_NAV': 1},
{'CFG_MSGOUT_UBX_NAV_HPPOSLLH_USB': 1},
{'CFG_MSGOUT_UBX_NAV_STATUS_USB': 5},
{'CFG_MSGOUT_UBX_RXM_RTCM_USB': 1},
{'CFG_MSGOUT_UBX_NAV_COV_USB':1},
{'CFG_MSGOUT_UBX_NAV_ODO_USB':1}]
what can I do to get a publish rate as /ubx_nav_hp_pos_llh
—
Reply to this email directly, view it on GitHub https://github.com/aussierobots/ublox_dgnss/issues/13#issuecomment-1755513432, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAVTAVCY2GJMD7M7JT6FZWDX6VJZFAVCNFSM6AAAAAA5ZQQEDWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONJVGUYTGNBTGI.
You are receiving this because you commented.

Great, is publishing now with a good rate.
I've also check this: [https://stackoverflow.com/questions/63037315/how-to-receive-gps-data-faster-using-kumarrobotics-ublox-package]
Thanks a lot, have a nice one!

Its a bit of playing around sometimes to get what you want out of the devices .. glad you've got a result :)
There are a backlog of changes coming through. I might also look at revising some of that code in the UBLOX Nav Sat Fix Hp node such that its not so reliant on updates from the none UBX Nav HP Pos LLH messages


Sideload to web

-Enables sideloading to web for Excel, OneNote, PPT and Word
-Implements sideload-web command that takes a documentUrl, dev-server port and manifest file path

Added tests

I need to revert that last merge commit.  Not sure why it picked up all the files from origin/master. I explicitly tried to avoid that

You may want to rebase off master. You don't want to merge in a revert of a merge, so it won't be a big deal if you squash this PR for check-in, but don't merge it.

I was thinking of just starting with a clean branch and kicking off a new PR.  Does that seem acceptable?  This new branch will already be up to date with master so no need for a merge

That's what rebasing effectively does except using the existing branch name. The commits on the branch would then be off of the latest commit on master. If you close this PR and start a new one, the only down side is you then lose the comments in the PR.

All our taskpane projects use HTTPS for the SourceLocation.  For example, Office-Addin-Taskpane:

I would like to wrap up this PR so we can get the sideloading to web feature out the door soon.  Once this PR is done, our Writers are going to document the feature and then we consider it done.
Thanks

I would like to wrap up this PR so we can get the sideloading to web feature out the door soon.  Once this PR is done, our Writers are going to document the feature and then we consider it done.
Thanks

I am taking a look. Are there any breaking changes with the CLI commands or the exported package functions?

I am taking a look. Are there any breaking changes with the CLI commands or the exported package functions?

I am taking a look. Are there any breaking changes with the CLI commands or the exported package functions?

I am taking a look. Are there any breaking changes with the CLI commands or the exported package functions?

@akrantz yes it should now be unified between desktop and web

@akrantz yes it should now be unified between desktop and web

@akrantz I didn't introduce any breaking changes here (e.g having an object with properties rather than an ever-growing list of parameters for startDebugging) - at least none that I know of

@akrantz I didn't introduce any breaking changes here (e.g having an object with properties rather than an ever-growing list of parameters for startDebugging) - at least none that I know of

Looks like my last change introduced a test failure. Investigating

Looks like my last change introduced a test failure. Investigating


add clear of serviceworkers

When you delete the cache on a running servieworker you might get a problem,
therefore please add the possibility to delete those too:
  const emptyRegistration = async () => {
    if ('navigator' in window) {
      const regs = await navigator.serviceWorker.getRegistrations();
      await Promise.all(
        regs.map(reg => { reg.unregister() })
      )
    }
  }

You can do it manually.


Usage with SwiftUI

Hello,
does anyone uses the package with SwiftUI?
Everything works so far, but changes are not fetched in the background.
I have a list that contains the values from the allKeys()-methods.  So if I add a new password, the list doesn't update because the new password isn't fetched. Same for cloud-sync. If there is a new key in the cloud, I have to call the allKeys()-method manually to fetch changes.
How can I do that automatically?
Help would be great :)

have you resolved this?

have you resolved this?

No. As far as I understand is the Keychain not capable of automatic background updates/ fetching. You have to do it manually.