New refresh algorithm?

Hello,
I don't want to sound too petty, but I noticed a disturbing refreshing of the website since the new update. The Version before refreshs each "div" for weather and calendar, in a smooth fx. For me it was great to see, that there is a smooth refresh way per "div". NOW the whole page refreshs every 15min-20min (like pressing F5).
Is that how it should be?
Regards
Maurice

Hi Maurice,
The full page refresh is not intended. This is probably a bug which I can't seem to replicate. Is there a way you can give the new code a try on your desktop and investigate if you see any errors in the console?
Cheers,
Michael

Having same issue and the pi can't seem to refresh the page after the ~15 min interval, it just loads forever.  The only way is to click the url and press enter... which doesn't work in fullscreen and defeats the purpose of the autostart.
Is there anyway to disable this auto refresh?

I had this issue and could only fix this with by disabling the version component. I deploy mine on an Azure site, so I can't even use the Git refresh feature.

I have this issue to on my dev System which does not have a commandline git available for php. It's the version control for sure.

The auto reloading isn't working properly for me either. Feel free to remove or replace this feature in a pull request.

@MichMich  are you directly pushing to the repro the pi is running from or does the pi have a seperate clone to serve from?
The first might be troublesome because HEAD changes way more often.

Maybe we could change this feature by allowing to refresh the screen by a command line command. Usually after a git pull, you still need to change the config file. Maybe we could do something like
touch refresh

And let the mirror check the edit date of refresh
Any thoughts?

@MichMich First of all, thanks for this project! I've built a full-length version (The glass is 59 1/2" x 20", and the whole assembly is 70" x 32") after being inspired by your original creation.
Per live-reloading, I do feel that moving away from the githash solution would be a good idea, since I often want to test things without committing new code, but that just might be me. I think having the front end poll the backend for an update indicator is a good idea. Not sure the best way to generate that at the moment, though.

@DanWilkerson , I agree. Those are cases when you want manual reloading. With a bit of luck I might be able to spend some time on this coming weeks, so hopefully I can address this issue.


Google AdWords Enhanced Conversions documentation

Description of the change

Added documentation for Google AdWords Enhanced Conversions

Type of documentation

[x] New documentation
[ ] Documentation update
[ ] Hotfix

Notion ticket link
Google AdWords Enhanced Conversions

thanks for the review, @Sudip i have addressed your comments. Just have 2 minor queries:

do you think we should add reference to ConversionAdjustment used to send these events to Google Ads for enhanced conversions?
Are there any specific guidelines for city and state that we included in the mapping?

thanks for the review, @sudip i have addressed your comments. Just have 2 minor queries:
* do you think we should add reference to ConversionAdjustment used to send these events to Google Ads for enhanced conversions?

* Are there any specific guidelines for city and state that we included in the mapping?

@ItsSudip @ameypv-rudder
We can link the conversions API for further reference WDYT?

thanks for the review, @sudip i have addressed your comments. Just have 2 minor queries:
* do you think we should add reference to ConversionAdjustment used to send these events to Google Ads for enhanced conversions?

* Are there any specific guidelines for city and state that we included in the mapping?

@ItsSudip @ameypv-rudder We can link the conversions API for further reference WDYT?

Do we mean this link as mentioned in the spec?

thanks for the review, @sudip i have addressed your comments. Just have 2 minor queries:
* do you think we should add reference to ConversionAdjustment used to send these events to Google Ads for enhanced conversions?

* Are there any specific guidelines for city and state that we included in the mapping?

@ItsSudip @ameypv-rudder We can link the conversions API for further reference WDYT?

Do we mean this link as mentioned in the spec?

@utsabc  Yes we can link the conversionAjustment link. @ameypv-rudder Yes that is the link for conversionAdjustment.


utterances comments not showing up

Hello there,
I have been trying to set up the utterances comments for each post, I have downloaded the utterances app in the website repo and set the parameters in config.toml as below, but there is no comments showing up in local server or online web.
[params.utterances]
repo = "xiangli2pro/xiangli2pro.github.io"
issueTerm = "pathname"
theme= "preferred-color-scheme"
crossorigin="anonymous"

Here is the link to the repo https://github.com/xiangli2pro/xiangli2pro.github.io.
I only modified the config.toml,  added customer.css, and added .md files in the content folder. Here is the link to myconfig.toml and customer.css. https://drive.google.com/drive/folders/1oJoqyX1k6b1C-XxVT5yC9io6gkVuGnS1?usp=sharing. I updated the anatole theme yesterday.
I have also tried the disque, but it did not work either. I have been searching around but could not figure out, could you please tell me how to fix this?  Thank you,

Might be wrong here but I ran into a similar block setting up comments on my site, comments only appear on "post" types and I have my content structured slightly differently.
Adding
type: post

to the markdown files Font Matter fixed it for me.

@Xen-Echo is basically correct. The comments are only loaded for post types and if comments are not disabled globaly. Let me know if that fixed your issue, else I will have a look at your config/files.

Thank you all! That works for me!
After I add type: post in .md file, the post has comment box now, but the post disappear from the home page. I fix it by adding "post" into parameter mainSections in the config.toml.


[cherry-pick] Improve crc stop message for already stopped cluster

It'll check if machine is already stopped before attempting
to perform the cluster stop related tasks
If a machine is already stopped it prints the following:
$ crc stop
Cluster is not running

sorry deleted the branch by mistake :( will create a new PR


Cant connect to my local host

Type: Bug
below is the error message I get when trying to connect to my local host
Not Found
The requested URL was not found on this server.
Apache/2.4.54 (Win64) OpenSSL/1.1.1p PHP/8.0.25 Server at localhost Port 443
VS Code version: Code 1.77.3 (704ed70d4fd1c6bd6342c436f1ede30d1cff4710, 2023-04-12T09:16:02.548Z)
OS version: Windows_NT x64 10.0.22621
Modes:
Sandboxed: No

System Info

Item
Value

CPUs
11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz (8 x 2803)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_off

Load (avg)
undefined

Memory (System)
7.76GB (1.46GB free)

Process Argv
--crash-reporter-id 4e8ee9c0-18b7-45eb-97df-9d52f26d9918

Screen Reader
no

VM
0%

Extensions (7)

Extension
Author (truncated)
Version

blackbox
Bla
0.10.58

vscode-intelephense-client
bme
1.9.5

phpserver
bra
3.0.2

prettier-vscode
esb
9.10.4

auto-close-tag
for
0.5.14

LiveServer
rit
5.7.9

php-debug
xde
1.32.1

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
vserr242:30382549
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
pythondataviewer:30285071
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593:30376534
pythonvs932:30410667
cppdebug:30492333
vsclangdf:30486550
c4g48928:30535728
dsvsc012:30540252
pynewext54:30695312
azure-dev_surveyone:30548225
nodejswelcome1cf:30587006
2e4cg342:30602488
pyind779:30671433
89544117:30613380
pythonsymbol12:30671437
vsccsb:30705552
azdwalk:30687957
pythonms35:30701012
pythonfmttextcf:30716743
pythonclientmvcf:30713944

Hello, I'm new to open source contribution, is anyone working on this issue currently? If not where would be a good place for me to start?

@Riedstar can you share steps for how to reproduce this issue?

Thanks for creating this issue! We figured it's missing some basic information or in some other way doesn't follow our issue reporting guidelines. Please take the time to review these and update the issue.
Happy Coding!

@Riedstar can you share steps for how to reproduce this issue?

Hi Alex, I go to where the xampp is saved (which is in the c drive) then I go to htdocs, then php-crash folder, and then open the file with vs code. I hope this helps:-)

@Riedstar can you share steps for how to reproduce this issue?

Hi Alex, I go to where the xampp is saved (which is in the c drive) then I go to htdocs, then php-crash folder, and then open the file with vs code. I hope this helps:-)

@alexr00 see above

We closed this issue because it is a question about using VS Code rather than an issue or feature request. Please search for help on StackOverflow, where the community has already answered thousands of similar questions. You may find their guide on asking a new question helpful if your question has not already been asked. See also our issue reporting guidelines.
Happy Coding!


having a problem while running the node

Hello,
Im having the following problem while running the node:

Im using Jetson Xavier and trying to run yolov4 with video from my ZED2 camera.
the error is
ImportError: /home/greensail/cv_ws/devel/lib/python2.7/dist-packages/cv_bridge/boost/cv_bridge_boost.so: undefined symbol: _ZTIN5boost6python7objects21py_function_impl_baseE

@Hagaik92
it looks like there might be something wrong with your cv_birdge. Could you try rebuilding cv_bridge?
Note: cv_bridge requires OpenCV3 to run.

@Hagaik92
it looks like there might be something wrong with your cv_birdge. Could you try rebuilding cv_bridge?
Note: cv_bridge requires OpenCV3 to run.

i have tried to rebuild cv_bridge ,nothing has changed, im using OpenCv 3.4.0

i have tried to rebuild cv_bridge ,nothing has changed, im using OpenCv 3.4.0

Im not sure why you're having the errors. I'm currently using OpenCv 3.4 as well on the Xavier. Perhaps reinstall the OpenCV 3.4 from this link

Im not sure why you're having the errors. I'm currently using OpenCv 3.4 as well on the Xavier. Perhaps reinstall the OpenCV 3.4 from this link

I'll close this issue, feel free to reopen it if its not solved


Uses Set instead of Array for uniqueness.

Changes in this pull request
Uses Set instead of Array for uniqueness.
Pull request checklist

[x] All tests pass. Demo project builds and runs.
[ ] I added tests, an experiment, or detailed why my change isn't tested.
[x] I have reviewed the contributing guide

Ha, nice! Super simple.

This array initialisation is great use case for AnyGenerator. But what can write so far is much longer of what we already have. Unfortunately.


Fix/url value object

I'm making this pull request, with a small change in the code, I changed the regex of the url value object so that it can include urls in the local environment, such as http://localhost:4000

#221

Hey @ArturHamannRonconi thanks so much to contribute with types-ddd lib 🥇 .
Could you add a test for the invalid url case? For example:

const valueObject = UrlValueObject.create('invalid-url');

What will be the result?
Thanks!!!

All right, sorry for the delay in making the change, but I believe that now it is working as expected, I used the URL object as mentioned.
I only have one observation, in the last commit I made I modified some things in the unit tests, some functions that did not exist and were missing and I commented some parts of the code, however, I left all these changes in a commit in case you want to git revert it
with this pull request closes #222

@ArturHamannRonconi tests for password.value-object fails.
Could you please update "rich-domain" dep and check the test fot password.value-object and update this pull request?


update radard.py to enable visual radar showing lead

this should be tested first on both cars with and without radar

not necessary


hazelcast example is broken

I followed the instructions in the [tutorial] (https://github.com/GoogleCloudPlatform/kubernetes/tree/master/examples/hazelcast) and got this output:
$kubectl get pods hazelcast
POD         IP           CONTAINER(S)   IMAGE(S)              HOST                                     LABELS           STATUS    CREATED         MESSAGE
hazelcast   <IP_ADDRESS>                                        kubernetes-minion-7jsw/<IP_ADDRESS>   name=hazelcast   Running   About an hour
                         hazelcast      pires/hazelcast-k8s                                                             Running   9 seconds       last termination: exit code 1

Note the "last termination: exit code 1".
And [here] (http://pastebin.com/1mNt57Ps) is the log.
It seems to be a problem of hazelcast rather than Kubernetes. @pires @nikhiljindal

@pires: Cant assign the issue to you, but I assume you are the right person to look at this?

@nikhiljindal I will take a look, yes but this has been changed recently, even by the user who just opened this ticket. How did his PR got merged without testing, I wonder?
@caesarxuchao what version of Kubernetes is this?

It's 0.16.0.
In that PR, I updated the .yaml files to use the latest API version (v1beta3). I tested the original .yaml files, which are using v1beta1 API, and it causes the same problem.

@caesarxuchao my only question is why merge something that wasn't working in the first place? No harm done. I will try with your changes and without, but most probably it's something related to how the apiserver replies now and the library I'm using.

@pires I will take caution next time. Thanks.

PR is up, please review.

aha, endpoints contain a list of subsets...that's why my fix to cassandra is not working yet

@caesarxuchao yeah, tried to discuss that with you over IRC, but you don't seem to have received my messages.


Allow setting sharp's limitInputPixels option

I've got a give with 150 frames in 2560x1080 causing next-image-export-optimizer to fail:
#13 177.4       Error while optimizing image EnterArena.gif
#13 177.4       Error: Input image exceeds pixel limit
#13 177.4
#13 177.4 node:internal/process/promises:279
#13 177.4             triggerUncaughtException(err, true /* fromPromise */);
#13 177.4             ^
#13 177.4
#13 177.4 [Error: Input image exceeds pixel limit]

To fix that, the limitInputPixels sharp constructor option should be exposed.

(Sorry about the other issue, github just had an outage and apparently despite returning 500 actually submitted the issue)

Closed by #133


Remove user creation script

What
This functionality is being moved to PaaS Admin.
See alphagov/paas-admin#686
How to review

Sanity check

I think you can also delete:

scripts/reset-org.py
scripts/list-org-owners.sh
scripts/org-usage-report.rb
scripts/reset-org.py

Also although it is logically separate you can also delete scripts/find_diverged_forks.py

Done


Style checks for Ada code

We do not currently have any style checks enabled for our SPARK tests. In projects that have those enabled, this is a problem (especially when compiling with warnings-as-errors as we do).
We should base the default switches for our tests on the switches we use for our other projects (e.g. SXML). If for some style checks code is too hard to generate, we should discuss those situations and consider switching them off inside the generated code.
One issue that I noticed was a warning about a superfluous others in a case statement of an enumeration.

-gnatwh (hiding)

That seems very restrictive and requires many changes in the code generation. I'm not really convinced that it increases the readability when always a suffix to the affected names is added. Do you think it is worth the effort?

-gnatwt (tracking of deleted conditional code)

function Read_File_Ptr (Name : String) return Bytes_Ptr is
      package Byte_IO is new Ada.Sequential_IO (Byte);
      Input_File : Byte_IO.File_Type;
      Buffer : constant Bytes_Ptr := new Bytes (1 .. Index (Ada.Directories.Size (Name)));
      Value : Byte := 0;
      I : Length := 0;
   begin
      Byte_IO.Open (Input_File, Byte_IO.In_File, Name);

spark-file_io.adb:12:07: warning: in instantiation at a-sequio.adb:77 [-gnatwt]
spark-file_io.adb:12:07: warning: this code can never be executed and has been deleted [-gnatwt]

What is the issue with package Byte_IO is new Ada.Sequential_IO (Byte)? Byte_IO is obviously used afterwards.

-gnatys Check separate specs.

   procedure Store_Payload_Length (Buffer : RFLX_Builtin_Types.Bytes);

   procedure Store_Payload_Length (Buffer : RFLX_Builtin_Types.Bytes) is
   begin
      Payload_Length := Buffer'Length;
   end Store_Payload_Length;

What is the advantage of enforcing a separate spec? For local subprograms this leads to useless replicates like shown above.

spark-file_io.adb:12:07: warning: in instantiation at a-sequio.adb:77 [-gnatwt]
spark-file_io.adb:12:07: warning: this code can never be executed and has been deleted [-gnatwt]

What is the issue with `package Byte_IO is new Ada.Sequential_IO (Byte)`? `Byte_IO` is obviously used afterwards.

The issue is in Sequential_IO:
   procedure Byte_Swap (Siz : in out size_t) is
      use System.Byte_Swapping;
   begin
      case Siz'Size is
         when 32     => Siz := size_t (Bswap_32 (U32 (Siz)));
         when 64     => Siz := size_t (Bswap_64 (U64 (Siz)));
         when others => raise Program_Error;
      end case;
   end Byte_Swap;

'Size is 64, so the compiler correctly deduces that the case statement for case 32 can never be executed.

@Jellix Thanks for the explanation! So I suppose there is nothing we can do but suppress this warning for this instantiation.

@Jellix Thanks for the explanation! So I suppose there is nothing we can do but suppress this warning for this instantiation.

If the standard library is flagged with a warning we should consider removing -gnatwt from our list of checks alltogether.

If the standard library is flagged with a warning we should consider removing -gnatwt from our list of checks alltogether.

I'm undecided. It is unpleasant to have to suppress warnings caused by the standard library, but the quick detection of unused code could be helpful. In case of RecordFlux this flag is not a big issue: Only the above mentioned case is affected. So I tend to keep the flag.

I'm torn wrt. to hiding. Prohibiting hiding has helped me in the past, especially in nested procedures when accidentally using the same for parameters and local variables or the same local variables as an outer scope.

When writing code from hand I definitely want to have hiding checks because of the reason you stated.

As it was helpful for both of you in the past, I will take a deeper look at the changes needed.

This has often helped me recognizing missed subprogram bodies when doing API changes. E.g. you remove a procedure from the spec and forget to remove the body from the package body it will warn you about the stray body. I think it would be useful to enforce this only on the package level as I can understand your issue with seemingly useless declarations for local subprograms.

I see that this can be helpful in some cases, but I do not like boilerplate code. So I would favor not enforcing this for RecordFlux.

I think it would be useful to enforce this only on the package level as I can understand your issue with seemingly useless declarations for local subprograms.

Do you know a way to disable this check for subprograms, but have it enabled at package level? While I find it useful for packages, too, having to place as spec directly next to the local subprogram always annoyed me.

I'm undecided. It is unpleasant to have to suppress warnings caused by the standard library, but the quick detection of unused code could be helpful. In case of RecordFlux this flag is not a big issue: Only the above mentioned case is affected. So I tend to keep the flag.

If this is the only place I also tend to suppress it there and keep the flag.

I see that this can be helpful in some cases, but I do not like boilerplate code. So I would favor not enforcing this for RecordFlux.

I agree. We should define how we handle flags that we do not support in RecordFlux. Do we disable them through a pragma in the generated code or does the user need to change the flags for generated files. IMHO the former would be more convenient.

I agree. We should define how we handle flags that we do not support in RecordFlux. Do we disable them through a pragma in the generated code or does the user need to change the flags for generated files. IMHO the former would be more convenient.

Until now I solved this problem by importing all generated code as a separate library with its own gpr file. When you use libraries in a strict environment you have to do this anyway since most libraries won't meet the required standards anyway.
Generally my opinion is that we don't need to aim for the same standards with generated code as we do with hand written code. And lessen the requirements for handwritten code because we want to include generated code by source is a bad argument IMHO.

I see no issue with most of the style checks. In my current state of work all our style checks are fulfilled with the exception of three: L9 (nesting level), M120 (line length), s (separate spec). I would suggest to add the following style check pragma to each generated file: pragma Style_Checks ("N3aAbcdefhiIklnOprStux"). This resets all exisiting style checks (e.g., defined in the project file) and only activates checks which can be fullfilled by the generated code.

If you can set a style per file I think that's a good option.

I see two issues related to validity checks:

-gnateV causes a bug box in current GNAT versions.
-gnatVo causes failing preconditions although the code is proven correct by GNATprove. This issue seems to be related to a 'Old aspect.

All of the warning-related switches can be fullfilled by the generated code.

-gnateV causes a bug box in current GNAT versions.

I remember that we had commented this out in earlier versions of our switches.gpr due to a bug in GNAT Community 2018. We added it again when we couldn't remember what the bug was. It seems you found it again. Maybe we should add it to the workarounds so we won't forget it again in the future.

I see two issues related to validity checks:
* `-gnateV` causes a bug box in current GNAT versions.

* `-gnatVo` causes failing preconditions although the code is proven correct by GNATprove. This issue seems to be related to a `'Old` aspect.

All of the warning-related switches can be fullfilled by the generated code.

We should file a ticket for each of the two issues. The -gnateV issue could indeed be related to what we saw with Community 2018. Maybe there is an explanation for the failing precondition with -gnatVo (even though I think that either our proofs or the check are false).

gnatwc (which is part of -gnatwa) seems not to be compatible with our lemmas for SPARK.
Just one example:
   procedure Mult_Limit (Value_1 : Long_Integer;
                         Exp_1   : Natural;
                         Value_2 : Long_Integer;
                         Exp_2   : Natural) with
     Pre  => 2**Exp_1 <= Long_Integer'Last
               and 2**Exp_2 <= Long_Integer'Last
               and 0 <= Value_2
               and Value_1 <= 2**Exp_1
               and Value_2 <= 2**Exp_2,
     Post => Value_1 * Value_2 <= 2**(Exp_1 + Exp_2),
     Ghost;

GNAT complains with -gnatwc about 2**Exp_1 <= Long_Integer'Last and 2**Exp_2 <= Long_Integer'Last:
rflx-rflx_lemmas.ads:12:23: warning: condition can only be False if invalid values present [enabled by default]
rflx-rflx_lemmas.ads:13:29: warning: condition can only be False if invalid values present [enabled by default]

But this part of the precondition is needed by GNATprove to show absence of overflow errors.

Does removing it from the precondition and adding a
pragma Assert (2**Exp_1 <= Long_Integer'Last);
pragma Assert (2**Exp_2 <= Long_Integer'Last);

at the beginning of Mult_Limits body help (and still prove the lemma)? If that alone does not help, we could disable that particular check in the body. I'd like to keep -gnatwc as I think it's helpful in finding logic bugs.

Not only preconditions are affected, but also assertions in the body. The warnings shown above are also only examples. There are more issues in our lemma package:
rflx_lemmas.adb:50:27: warning: condition can only be False if invalid values present [enabled by default]
rflx_lemmas.adb:87:27: warning: condition can only be False if invalid values present [enabled by default]
rflx_lemmas.adb:93:27: warning: condition can only be False if invalid values present [enabled by default]
rflx_lemmas.ads:12:23: warning: condition can only be False if invalid values present [enabled by default]
rflx_lemmas.ads:13:29: warning: condition can only be False if invalid values present [enabled by default]

To the example: Moving these preconditions into the body would lead to failing preconditions (e.g., overflow error for Value_1 <= 2**Exp_1).
I would suggest to disable -gnatwc for the lemma package

I agree. If it's not problem outside the lemma package, then we should just disable it there.

As it turned out, the error messages vanish when -gnato13 is used. In some circumstances during my tests this flag was not enabled for the lemmas package. As we need this flag anyway, no suppression of -gnatwc warnings is needed.


[BUG] Why chip tools still send InteractionModelRevision = 1 instead of 10?

Reproduction steps
When you look at the commands that chip tool and also the chip apps send all interaction messages are send with
InteractionModelRevision = 1
The Matter spec 1.0 had set this revision number to 10, so why this is not used? versions 1..9 are some "versions of the Zigbee Cluster Library chapter 2 which combined the interac tion model with encoding" ...
Bug prevalence
always
GitHub hash of the SDK that was being used
any
Platform
other
Platform Version(s)
No response
Anything else?
No response

@Apollon77 Please list the actual github hash involved, not "any".   This was fixed in https://github.com/project-chip/connectedhomeip/pull/28645 over a month ago.

@Apollon77 That said, if you are in fact seeing that on tip, please reopen as needed.  Also, note that the spec has been updated to make it clear that the revisions the 1.0 SDK sent did not match the 1.0 spec.  How things got there... that's a separate story.

@bzbarsky-apple sorry for it ... I thought I updated but in fact did not ... basically I run (again ... had that before, learned and forgot ;-) ) into https://github.com/project-chip/connectedhomeip/pull/29299 ... so now I tried to update and run into https://github.com/project-chip/connectedhomeip/issues/29300 because newest builds of chip tool do not have tests in any more and no docs were updated :-(

But yes now after I managed to somehow get it running the reported revision is 11 (most likely Matter 1.2 coming .. soooo) is fine now. Thank you


Don't set 'content-length' with 'transfer-encoding'

When updating the response content for a response, avoid adding the
'content-length' header if the response contains a 'transfer-encoding'
header, from the spec [1]:

When a message does not have a Transfer-Encoding header field, a
Content-Length header field can provide the anticipated size, as a
decimal number of octets, for a potential payload body

Note the 'transfer-encoding' header is not used with HTTP/2
https://httpwg.org/specs/rfc7230.html#header.content-length
Description

Checklist

[X] I have updated tests where applicable.
[ ] I have added an entry to the CHANGELOG.

Thanks for tackling this!
Let's copy this check here so that things are consistent:
https://github.com/mitmproxy/mitmproxy/blob/0ca458fd6475ee48728147f3b529467a75e912a4/mitmproxy/net/http/http1/assemble.py#L30
A stylistic device I like to use for cases like this is to have an explicit pass case with documentation: That emphasizes the intent here and also makes sure that we have test coverage for both cases:
if "chunked" in headers.get("transfer-encoding", "").lower():
    pass  # http://tools.ietf.org/html/rfc7230#section-3.3: do not add a content-length header to a chunked message.
else:
    self.headers["content-length"] = str(len(self.raw_content))

I've pushed the second part for #4824 on top of your commit so that we have everything in one place. :)

Thanks for the review!

I've pushed the second part for #4824 on top of your commit so that we have everything in one place. :)

Perfect, thanks

A stylistic device I like to use for cases like this is to have an explicit pass case with documentation

Good idea, done with c5036d795

Let's copy this check here so that things are consistent:

I think these are separate checks: I said in the issue that this was only for 'chunked' transfer encodings, but I believe it's for any request with a transfer-encoding set

Ah, yes, you are right. Thanks for checking this so thoroughly! 🍰


Add New Tag to imputation Model

There are several case where none of the imputation method was eligible to apply to fill the observe null values . Previously we tag those as observed. However, in our meeting we decided to tag this kind of case as "Observed_unimputed"  to avoid any confusion by the tagging

this task is completed


[WIP] Protocol oriented integers

This is not the final proposal yet. Still working on some details.

Overall this is looking fantastic, Max.  Please accept my PR into your branch and address the two items above.  Then, as far as I’m concerned, it’s ready to go.

@moiseev Please email me (off list) when you're ready for this to be merged.  I'll take care of kicking off the review from there.

Should this proposal describe how the new floating point system and extant numeric protocols fit in? As far as I can tell, FloatingPoint could inherit from SignedArithmetic. Do SignedNumber and AbsoluteValuable still exist after this has been implemented?

@natecook1000 it was designed with floating point in mind, it's just that floating point landed earlier. There are several places in the current implementation of floating point numbers where the code is commented out because there are no corresponding protocols yet. Answering your questions: yes, the SignedArithmetic should be adopted by floats and SignedNumber should disappear, as well as the AbsoluteValuable and the ~> operator.


UI/UX full review and polishing

Conduct a comprehensive review and polishing of the UI/UX to ensure a seamless and visually appealing user experience. This includes verifying all functionalities, refining spacing and design details, optimizing responsiveness and typography, fixing minor UI bugs, and ensuring proper image loading and link functionality.
Tasks:

Verify that all functionality works as intended.
Check and adjust spacing cadence across different viewports.
Identify and implement design details missing from Figma.
Review and adjust responsiveness and typography sizes.
Fix minor UI bugs (e.g., adjust icons by 1px, better centering elements).
Review and optimize image loading.
Ensure all links are functional.
Verify that the 404 page works correctly.

Do it agains develop branch.  https://dev.bitlauncher.ai

Some feedbacks here related to the issue -> https://docs.google.com/document/d/15zFOB_D0ngf0AKOnbOZcv9-XDfNAU0pyHs9_DiNb794/edit
cc - @Bran18

 [Bitlauncher] Landing UI/UX Tweaks and Bugfixes


Fix warnings reported by gcc 5.3.0 on Mac OS

This should make xrdp warning-free and set a higher standard for new code contributions.

+1
Thanks for your work on this.


Hi fellow bot framework creator

@RationalAnimal I tried really hard to find you public contact but it seems you prefer to be in shadows :)
Anyways, I stumbled upon your npm package when was looking for nlp tools for to extend my bot framework and I was astonished by the amount of work you already did. Congrats 🎉
Saying that, I have a proposal to collaborate and maybe integrate our tools and create something better together then we would do otherwise on our own.
If you're interested, please connect with via email<EMAIL_ADDRESS>
P.S. It seems from your name you might be speaking Russian, if that's the case, I would be thrilled to continue dialogue in Russian.

Hi there
I'll respond in private email; closing this issue.
Thank you
Ilya


Endpoint.connect() with TLS fails with InvalidDNSNameError

Bug Report
Version
tonic v0.1.0
tonic-build v0.1.0
Platform
Darwin x86_64
Crates
webpki v0.21.0
Description
Creating a channel by calling connect() on an Endpoint configured with a TLS config fails with the error
    Error(hyper::Error(Connect, InvalidDNSNameError))

unless the domain_name option on the ClientTlsConfig is set. Contrary to the docs, the domain_name option is used (and required) even when the rustls_client_config option is set on the config.
The inner InvalidDNSNameError comes from the webpki crate, returned at this line: https://github.com/hyperium/tonic/blob/5fc6762435494d8df023bea8e35a5d20d81f2f3b/tonic/src/transport/service/tls.rs#L88
When the ClientTlsConfig builds a TlsConnector, the entire connection URI string is used as the domain name if the domain name has not been set on the config. https://github.com/hyperium/tonic/blob/5fc6762435494d8df023bea8e35a5d20d81f2f3b/tonic/src/transport/channel/tls.rs#L83-L86
I would expect the domain_name option to actually be optional, and for connections to succeed in the common case when the host component of the connection URI matches the domain name for TLS SNI.

@corhere thanks for writing this up! If I understand correctly you are suggesting that we use uri.host() instead of uri.to_string()?

@LucioFranco that is correct


Fix Bundle logic to output proper XLIFF 1.2 . Fixes #5

Fixing XLIFF related issues @yumaoka pls review/merge.

Coverage increased (+0.1%) to 47.821% when pulling b1420bee51775b574008d9240f5be3a666b12236 on JCEmmons:issue5 into 0528e99697ee196555851619d975d161c92a6510 on IBM-Bluemix:master.


Changes to Package Loading interface

We currently have a diverse zoo of functions for loading packages, such as readPoseidonPackage, findPoseidonPackages, loadPoseidonPackagesIgnoreChecksums, loadPoseidonPackages and so forth.
We discussed several steps that are needed to make this interface simpler and securer:

We need to integrate the base path to a package into the package data structure. This will facilitate loading of files within the package, and make the current strategy of making absolute paths obsolete. This will affect all file-loading functions (genotypes, janno, bib-file, etc.) as well as the checksum-checking.
We rename the loading functions. The core loading function will be renamed: loadPoseidonPackages -> readAllPoseidonPackages, and other functions will be renamed to make the usage of find and read consistent, and avoid load.
We remove the option to load packages with ignoring checksum-checks. Checksum-Checks are always to be done if the files can be found. If not, then not.

All of this is covered now by the behemoth #29


feat: enabled smart contract addresses in contract store

Closes #19
Checklist

[x] Implemented C... smart contract checking logic
[x] Ensured everything works correctly by running yarn build

Hi @ElliotFriend, please review and merge this PR under ODHack 8.0!

@ElliotFriend please review the PR for any changes required

I think your change on line 52 is exactly what we need, though! As soon as you get the new changes merged in and remove the other two changes, I can get this merged right awya.

@ElliotFriend, conflict resolved!

@ElliotFriend can you please review it again? been more than a day since i merged the conflicts


Refactor to avoid using setNativeProps

setNativeProps is not implemented in react-native-web, and it causes performance bottlenecks with frequent re-renders (which is common in this type of progress indicator). This module should be refactored to avoid using the setNativeProps API.

A lot of changes has been introduced in the lib since v1. reopen this ticket if this still needs attention


[Bug] Parsing class names wrapped in backquotes not work correctly (OrientDB 2.1.1)

Example:
CREATE CLASS Contains EXTENDS V
Class created successfully.
SELECT FROM `Contains`  or SELECT FROM Contains
Error: com.orientechnologies.orient.core.sql.OCommandSQLParsingException: Error on parsing command at position #0: Encountered "  "FROM "" at line 1, column 8.
Screening by backquote (`) worked good before v. 2.1.1, and also in this version was added fix for this issue: https://github.com/orientechnologies/orientdb/issues/4768, maybe the fix broke class screening?

Hi @ivmakk
it seems to be already fixed, the backtick quoted version
SELECT FROM `Contains`

works fine in 2.1.x branch, could you please confirm?
Thanks

Excuse me @luigidellaquila, my mistake, SELECT really works fine.
But CREATE EDGE `Contains`  not work.
How to recreate (in v2.1.1 & v2.1.2):
CREATE CLASS Contains EXTENDS E
Class created successfully. Total classes in database now: 12

CREATE VERTEX V
Created vertex 'V#9:0 v1' in 0.009000 sec(s).

CREATE VERTEX V
Created vertex 'V#9:1 v1' in 0.004000 sec(s).

CREATE EDGE `Contains` FROM #9:0 TO #9:1
Error: com.orientechnologies.orient.core.sql.OCommandSQLParsingException: Error on parsing
command at position #0: Class '`CONTAINS`' was not found

After last step (CREATE EDGE `Contains` ) in v2.0.0 edge created successfully with message Created edge '[Contains#11:0{out:#9:0,in:#9:1} v1]' in 0.034000 sec(s).
But in both last vesions (I checked it in v2.1.1 & v2.1.2): Error: com.orientechnologies.orient.core.sql.OCommandSQLParsingException: Error on parsing command at position #0: Class '`CONTAINS`' was not found
Maybe edge can be created in some other way for avoiding incorrect parsing keywords?

Ah, ok, thanks for the details.
I can fix it quickly.
If you need a quick work-around, you can try to disable strictSql (from Studio, DB tab, Configuration, bottom of the page), it should work as before (without backtick)
Thanks

fixed in branch 2.1.x, cherry-picking to develop

also fixed in develop branch.
Please confirm that it also solves your use case, so that I can close

Please confirm that it also solves your use case, so that I can close

Ok, thank you, I think the fix will solve this bug

Perfect, thanks.
Closing


API Documentation

There is a lack of documentation as to how to configure mappings using API instead of using XML. For example, I am trying to set the set-method for a field mapping however, it isn't clear as to how this can be accomplished and there is a lack of documentation as to how this can be accomplished. Another example would be setting the mapNull to false as a global configuration. It's not clear if global configurations can only be accomplished in XML still or it can be accomplished in API and how.
Any insight on these would be greatly appreciated.

No, global config is not supported via APIMappings, as per:

https://github.com/DozerMapper/dozer/search?q=ConfigurationBuilder&unscoped_q=ConfigurationBuilder

API mappings are not 100% feature comparable with XML

After such a long time passed, does the author have plans to provide an API-based global configuration?

@FirstJavaMaster ; do you want to contribute the code?

@FirstJavaMaster ; do you want to contribute the code?

Thanks. I will give it a try. But I need some time to understand the existing code. Don't hold too much hope...


Problem with .gif files on Chrome and Edge

Hello,
I started to test this repo locally and saw one strange thing:
When you are creating the avatar which contains a .gif file,
this .svg pattern causes problems on Chrome and Edge i.e. gif doesn't play:
svg-template.ts
<defs>
    <pattern id="backImg" patternUnits="userSpaceOnUse" x="0" y="0" width="270" height="270">
       <image href="data:${mimeType};base64,${backgroundImage}" width="270" height="270" />
     </pattern>
</defs>

It works fine on Mozilla though..
Token with which you can test:

68490925849223255967220569990002994150459005267277907137130096426365483329544

What seems to be working normally is the old patter of image display that you used:
Image

Hello, I was just working on this improvement. Seemingly chromium has a bug if image served under pattern, so I updated our svg template without using pattern. https://github.com/ensdomains/ens-metadata-service/pull/141


Backend Swift IP configuration is not allowed

swiftstack ProxyFS 1.5.3 can not be configurable that assign another Swift IP address than <IP_ADDRESS> because it's hard corded in the go swiftclient.
For performance consideration, it may be ok as design because setting other proxy server than localhost might cause performance issue from the connection over the IP network. However, the hard code to <IP_ADDRESS> is a bit problematic to my case because I'd like to configure my proxy-sever other than <IP_ADDRESS>. (i.e. configure the swift's bind_ip to a specific out-bound network ip.) Then, proxyfsd can not talk with the proxy-server.
I thought I may create a new proxy-server conf to bind to <IP_ADDRESS> but it will have resource overhead to make duplicate proxy-server caused by just a bind ib difference.
I tried to touch around the code to enable the backend swift ip as configurable [1], and it looks to work in my local environment. If it's suitable for ProxyFS community, I'll push a pull request to support the staff in upstream.
Any ideas?
1: https://github.com/bloodeagle40234/ProxyFS/commit/3fe824b735a7f0d12b470d07d694794dd9289e22

Yes, the jrpcclient is currently assumed to be talking to the proxyfsd only on the same node. That said, the ipaddr being listened to by jrpcfs should actually be the cluster-facing ipaddr. This is because the pfs middleware in each Swift Proxy needs to be able to talk to any proxyfsd instance.
In any case, proxyfsd should not be listening on <IP_ADDRESS> as this would allow untrusted client machines to gain privileged access to the file system.
Longer term, there is a lot of interest in scaling out the jrpcclient function beyond just the local node where proxyfsd is running. Indeed, some folks are at work enabling the NFS protocol to leverage jrpcclient to gain this same scale out capability.
I'd love to hear others chime in on Kota's request as I think it an excellent one.

I should add a bit more here.
The various .conf files in (primarily) the proxyfsd/ subdirectory are mere examples perhaps useful in development. As Kota points out, the proxyfsd process listens for connections on the PrivateIPAddr specified...and the examples in those .conf files are typically <IP_ADDRESS> - though this is easily changed.
I should also comment that one can try out config changes by overriding their values on the command line when starting proxyfsd by  following the .conf file with Section.Key=Value sequences. But in this case, Samba needs to know the PrivateIPAddr as well...so one minimally needs to (also) modify the smb.conf being used.

Let me clarify my case. I meant the connectivity from proxyfsd to Swift cluster, the proxyfsd uses golang swiftclient that can connect only <IP_ADDRESS>. I don't think the "proxyfsd -> swift" uses the jrpcclient but "swift pfs_middleware -> proxyfsd" does.
But anyway, configurable options for the cluster facing internal networ for BOTH "proxyfsd -> swift" and "swift -> proxyfsd" sounds nice to have to me.

Aha Kota! Now I understand what you are looking at.
The proxyfsd process needs a path to Swift that does not have the pfs middleware in it. In addition, this path need not perform authorization since that has already been done. Indeed, at times it would be difficult bto associate requests for that the proxyfsd process makes to Swift with a particular client. In any event, the auth models of SMB & NFS are quite different than for Swift or S3.
As such, the ProxyFS setup requires what we call a "NoAuth" Swift Proxy pipeline. Lacking authorization, this pipeline certainly cannot bind to <IP_ADDRESS> lest unauthorized traffic do bad things. And, of course, such access would be presented with a rather incomprehensible set of checkpoint and file log segment objects. This would be akin to allowing normal processes access to the blocks on a disk formatted with a file system.
So you will see a NoAuth Swift Proxy instance (along side a normal Swift Proxy instance) on every ProxyFS node. This NoAuth Proxy binds specifically to localhost as you have observed and is only used by the colocated proxyfsd instance.
It sounds like you'd like it to be useable by other proxyfsd instances? Additionally, you'd like a given proxyfsd instance to be able to use NoAuth Proxies other than the one colocated with it.
I guess I don't understand why that would be beneficial.
One change that we could do is have the NoAuth Proxy binds to the cluster IP (the so-called PrivateIPAddr in the ProxyFS .conf files) and, then, proxyfsd could connect to that one (still colocated). Perhaps this is the change you are looking to do. A side benefit is that moving to an all IPv6 world would not require hard code changes of <IP_ADDRESS> to ::1 - not that moving to IPv6 necessarily eliminates the 127.0.0.X instance(s) of localhost...but it's a thought.

So you will see a NoAuth Swift Proxy instance (along side a normal Swift Proxy instance) on every ProxyFS node. This NoAuth Proxy binds specifically to localhost as you have observed and is only used by the colocated proxyfsd instance.

I think this is an constraint that any operators have to consider to compose proxyfsd and no-auth swift proxy any time then we cannot divide the operation between proxyfsd and swift proxy. An management issue is updating swift ring for the proxy, if we update the ring for capacity planning every proxyfsd node should be updated to get the new swift cluster object allocation. Then that might be painful.

It sounds like you'd like it to be useable by other proxyfsd instances? Additionally, you'd like a given proxyfsd instance to be able to use NoAuth Proxies other than the one colocated with it.

Yes, saying more than operating issue above, actually we already operates no-auth proxy for our in-house fuse system that mounts swift cluster so at first, I'd like to re-use the no-auth swift endpoint but it's impossible in current proxyfsd deployments model.

One change that we could do is have the NoAuth Proxy binds to the cluster IP (the so-called PrivateIPAddr in the ProxyFS .conf files) and, then, proxyfsd could connect to that one (still colocated). Perhaps this is the change you are looking to do.

I know. I already has the change[1] before this issue reported so if the proxyfsd community would think it as nice to have, I'll push a pull request for this. Before doing so, I'd hear the opinion if it's beneficial for proxyfsd community at the issue tracker following an OSS convention.
1: https://github.com/bloodeagle40234/ProxyFS/commit/3fe824b735a7f0d12b470d07d694794dd9289e22

So the real ask is to be able to separate proxyfsd from the no-auth-swift proxy. I see... interesting to understand why that would be helpful... this is not the swift proxy that clients use... it's only there to enable proxyfsd to talk to the cluster.
Meanwhile, did you suggest there is value in separating SMB/NFS serving (via jrpcclient) and proxyfsd? Much like how any proxy instance can talk to every proxyfsd instance in the cluster, the goal here would be able to allow any SMB (Samba->VFS->jrpclient) / NFS (Ganesha NFS->FSAL->jrpcclient) to talk to every proxyfsd instance in the cluster as well. What do you think about that?

Meanwhile, did you suggest there is value in separating SMB/NFS serving (via jrpcclient) and proxyfsd? Much like how any proxy instance can talk to every proxyfsd instance in the cluster, the goal here would be able to allow any SMB (Samba->VFS->jrpclient) / NFS (Ganesha NFS->FSAL->jrpcclient) to talk to every proxyfsd instance in the cluster as well. What do you think about that?

I'm not sure I get your mean correctly but it seems like, "yes". containerized processes for each endpoint (NFS, SMB, proxyfsd, and Swift Proxy) may be useful to make the cluster topology elastic. In fact, before trying to do this, I tried to build a docker container image to deploy proxyfsd (and NFS servers) to be located any cluster facing nodes, that is separated from Swift proxy. It was unfortunately not able though. That is because current proxyfs doesn't have any Ganesha NFS staffs so far.
If you don't like to get the elastic configuration, I don't want to continue to force to add the option here (probably, just forking in-house) but if you could think like 'it might be useful, it might be nice to have'. I'm happy with giving my pull request with a few fixes (like no-default configuration you suggested) in the future.
Thought?

@charmster Thanks for clarifying my idea. Those look right. You understand my thought correctly. And the note is same with my understanding. So... my suggestion on this issue is we may have more flexible deployment model like separating proxyfs and swift-proxy nodes. The concern is just like as what you wrote down above.


Improve frontend build pipeline to generate contract artifacts

Currently, the folders packages/frontend/artifacts/contracts/ and packages/frontend/types/typechain/ are kept in git. These files are generated from the contracts with npx hardhat compile from the hardhat workspace package. Because of this, every time the contract is changed, all these files need to be updated in git. And merge conflicts can arise if different people change the contracts.
So I propose that

these files are removed from git and ignored and
the frontend build pipeline should generate them

resolved in https://github.com/yieldgate/yieldgate/commit/cb6dc41817a305cd7c995aad27d8f2b329bfddc9


Turtlebot4 simulator dock/undock?

Hello,
How does one make Turtlebot4 dock or undock in its simulator?
Thank you.

Hello @languyen14507, you can send the dock and undock commands via the Create3 Dock and Undock Actions:
There is a more in depth description here:
https://iroboteducation.github.io/create3_docs/api/docking/
However to save a click here are the commands:
Undock
ros2 action send_goal /undock irobot_create_msgs/action/Undock "{}"

Dock
Galactic
ros2 action send_goal /dock irobot_create_msgs/action/DockServo "{}"

Humble
ros2 action send_goal /dock irobot_create_msgs/action/Dock "{}"

Can the Turtlebot 4 simulator run SLAM and Navigation like the Turtlebot 3 simulator? I have never been able to undock the Turtlebot 4 simulation successfully so I couldn't tell. The undocking process always stopped and never finished because the undock goal was always canceled by the simulator before it has change to finish. Thanks.

I don't see any RTL on the simulator gazebo display but I see these messages on the terminal where I activated the simulator:
spawner-20] [INFO] [1684166862.565217662] [spawner_joint_state_broadcaster]: Configured and started joint_state_broadcaster
[parameter_bridge-3] [INFO] [1684166862.692902468] [cmd_vel_bridge]: Passing message from ROS geometry_msgs/msg/Twist to Ignition ignition.msgs.Twist (showing msg only once per type)
[INFO] [spawner-20]: process has finished cleanly [pid 50118]
[INFO] [spawner-37]: process started with pid [51358]
[ign gazebo-1] [INFO] [1684166863.133635835] [controller_manager]: Loading controller 'diffdrive_controller'
[spawner-37] [INFO] [1684166863.211148035] [spawner_diffdrive_controller]: Loaded diffdrive_controller
[ign gazebo-1] [INFO] [1684166863.212986343] [controller_manager]: Configuring controller 'diffdrive_controller'
[spawner-37] [INFO] [1684166863.321551000] [spawner_diffdrive_controller]: Configured and started diffdrive_controller
[INFO] [spawner-37]: process has finished cleanly [pid 51358]
[turtlebot4_node-32] [INFO] [1684166871.830227083] [turtlebot4_node]: Undocking
[turtlebot4_node-32] [INFO] [1684166871.830622690] [turtlebot4_node]: Waiting for undock action server
[turtlebot4_node-32] [INFO] [1684166872.831421095] [turtlebot4_node]: undock action server available, sending goal
[motion_control-23] [INFO] [1684166872.831893474] [motion_control]: Received new undock goal
[turtlebot4_node-32] [INFO] [1684166872.832237148] [turtlebot4_node]: undock goal accepted by server, waiting for result
[turtlebot4_node-32] [ERROR] [1684166880.632648365] [turtlebot4_node]: undock goal was canceled
[motion_control-23] [WARN] [1684166880.637115688] [motion_control]: Reached backup limit! Stop Driving robot backward or disable from safety_override parameter!
[motion_control-23] [WARN] [1684166953.540066712] [motion_control]: Reflex Exceeded Runtime without clearing hazard

When trying the run NAV2 with the Turtlebot 4 simulator with the command
ros2 launch turtlebot4_ignition_bringup ignition.launch.py nav2:=true slam:=off localization:=true
I got the following error messages:
[ign gazebo-1] [Wrn] [OgreGpuRays.cc:253] Horizontal FOV for GPU rays is capped at 180 degrees.
[controller_server-38] [INFO] [1684169154.433378486] [local_costmap.local_costmap]: Timed out waiting for transform from base_link to odom to become available, tf error: Could not find a connection between 'odom' and 'base_link' because they are not part of the same tree.Tf has two or more unconnected trees.
[controller_server-38] [INFO] [1684169154.933372248] [local_costmap.local_costmap]: Timed out waiting for transform from base_link to odom to become available, tf error: Could not find a connection between 'odom' and 'base_link' because they are not part of the same tree.Tf has two or more unconnected trees.
[ign gazebo-1] [GUI] [Wrn] [ColladaLoader.cc:2394] Triangle input semantic: 'COLOR' is currently not supported
[ign gazebo-1] [GUI] [Wrn] [ColladaLoader.cc:2394] Triangle input semantic: 'COLOR' is currently not supported
[controller_server-38] [INFO] [1684169155.433371462] [local_costmap.local_costmap]: Timed out waiting for transform from base_link to odom to become available, tf error: Could not find a connection between 'odom' and 'base_link' because they are not part of the same tree.Tf has two or more unconnected trees.
[controller_server-38] [INFO] [1684169155.933372924] [local_costmap.local_costmap]: Timed out waiting for transform from base_link to odom to become available, tf error: Could not find a connection between 'odom' and 'base_link' because they are not part of the same tree.Tf has two or more unconnected trees.
[controller_server-38] [INFO] [1684169156.433373573] [local_costmap.local_costmap]: Timed out waiting for transform from base_link to odom to become available, tf error: Could not find a connection between 'odom' and 'base_link' because they are not part of the same tree.Tf has two or more unconnected trees.
[controller_server-38] [INFO] [1684169156.933385483] [local_costmap.local_costmap]: Timed out waiting for transform from base_link to odom to become available, tf error: Could not find a connection between 'odom' and 'base_link' because they are not part of the same tree.Tf has two or more unconnected trees.

You should see a fluctuating percentage value at the bottom right corner of the scene. If you expand that you should see something like this:

The RTF value just fluctutates around 10 and 11%

That's quite low. The simulation is basically running at 10% real-time, which can cause issues.
Does your PC have a dedicated GPU?

It has an Nvidia GEForce GTX 1650 Mobile and an Intel UHD Graphics 630 Mobile

If you enter nvidia-settings into your terminal, you should be able to go to PRIME Profiles and select NVIDIA (Performance Mode) to force the sim to use your GPU. You can also try changing the PowerMizer power mode to performance.
I think the sim is using your integrated graphics right now which is causing the poor performance.

I was able to switch the laptop to using the Nvidia GPU driver but the RTF value only increases to 13-14%. The undocking is still canceled due to reaching backup limit. The NAV2 run still has the  tf error: Could not find a connection between 'odom' and 'base_link' because they are not part of the same tree.Tf has two or more unconnected trees.

I'm running  the sim on a GTX1650Ti and get about 70% RTF so I think the sim is still using integrated graphics here. You may need to dig some more in your GPU settings.

I was able to correct the GPU driver settings and the simulation ran fine after that (70-80% RTF). Thanks so much.

I was able to correct the GPU driver settings and the simulation ran fine after that (70-80% RTF). Thanks so much.

hey @languyen14507 i am having the same issue. may i know how you fixed the driver settings?

Instead of selecting "from nvidia-driver-530-open" as shown in the picture above, I changed the selection to  "from nvidia-driver-418-server", clicked Apply Changes, waited until Aplly Changes is finished then reboot the computer.

Instead of selecting "from nvidia-driver-530-open" as shown in the picture above, I changed the selection to "from nvidia-driver-418-server", clicked Apply Changes, waited until Aplly Changes is finished then reboot the computer.

I have a GeForce 940M, do you have any hint how you selected the correct driver from the list in order to fix the RTF issue?

I'm running the sim on a GTX1650Ti and get about 70% RTF so I think the sim is still using integrated graphics here. You may need to dig some more in your GPU settings.

Do you have any driver suggestion for a GeForce 940M (about 20% RTX on average)? (see

picture attached)

I would suggest to cycle through the list of available drivers until you find one that works.

I also encountered the same problem, has solved, thank you very much.
My original RTF was only 2%, but with Performance Mode in nvidia-settings, my RTF was around 10%. However, the RTF remains unchanged after switching the driver.
I refer to the https://cloud.tencent.com/developer/article/2046885, terminal input inxi - G, found the OpenGL use sets show here.
My computer, Intel+NVIDIA combination, is now in centralized display mode. However, after switching the single-display mode, the OpenGL of inxi-G still uses intel.
Looking up the information, I found that although I have switched to NVIDIA single display mode, the NVIDIA driver may not be enabled correctly because the current Wayland session is used. NVIDIA single display mode is more stable in X11 environment, especially in OpenGL rendering.
After logging out and re-selecting Ubuntu on Xorg, I logged in, the inxi-G display was NVIDIA, and finally the RTF was about 60%.


Ledger implementation does not interact well with option aliases - repro

This change breaks view state:
node bin\near state test.near now produces Make sure to connect your Ledger and open NEAR app

What happens is that in the code, shell uses a camelCase convention for option values throughout. Most of time times aliases work because aliasing options results in all the possible cases being set in the options object which is being passed around. However, this is an example of usage which refers to some other entity which does not get stuff set according to aliases


feat: support ts import type modifiers on import names

This feature is introduced in TypeScript 4.5:
https://www.typescriptlang.org/docs/handbook/release-notes/typescript-4-5.html#type-modifiers-on-import-names
And recommended in @vue/tsconfig:
https://github.com/vuejs/tsconfig/blob/26fc528db347dbbbbaa2ea15d3c2d95c197887b7/tsconfig.json#L19-L23
Sucrase does not support it yet:
https://github.com/alangpierce/sucrase/issues/668
So I replaced it with @babel/standalone.
Babel supported the new syntax since v7.16.
So I also updated the project dependencies to ensure that
vue/compiler-sfc can also parse this syntax.
The bundle is a lot bigger after this change:
dist/vue-repl.js   5040.05 KiB / gzip: 840.42 KiB

But it is still much smaller than the size of a full TypeScript compiler
or esbuild-wasm, which are 9MiB+ in size.

Babel is huge and slow... maybe we should consider using esbuild-wasm instead

esbuild-wasm has a 9.79MB binary…<EMAIL_ADDRESS>


WAM silent SSO using the signed in windows account

closes #39222

API change check
APIView has identified API level changes in this PR and created following API reviews.
Azure.Identity

It is not supported in other languages MSAL library.
Do we want to make it available only in .net?

It is not supported in other languages MSAL library.
Do we want to make it available only in .net?

We should raise this question of supporting the equivalent of PublicClientApplication.OperatingSystemAccount to MSAL.


Update to Polymer 1.0

It would be nice to have this updated to new Polymer 1.0

working on this over here
https://github.com/tastejs/todomvc/tree/sjs/polymer-1.0/examples/polymer
will PR it back in

pr https://github.com/tastejs/todomvc/pull/1426


Allow different database environments

In my projects I use combustion not only for RSpec specs but also to run the engine as an application via rackup and rack-console. It would be nice to have the option to run those commands in the development environment since this would allow to run the app and specs at the same time (and other things).
Currently the database is hardcoded to the test environment, maybe this could either check for Rails.env or something like:
Combustion.initialize! :all, database_reset: false, database_environment: :development

in config.ru.
If anybody is having the same issue, I currently use the following workaround (combustion v0.8):
In config.ru:
unless Rails.env.development?
  abort "Combustion should not be reopened in #{Rails.env} environment."
end

module Combustion
  module Databases
    class Base
      def reset
        drop
        create

        establish_connection :development
      end
    end
  end
end

module Combustion
  class Database
    class Reset
      def call
        configuration = ActiveRecord::Base.configurations['development']
        adapter = configuration['adapter'] || configuration['url'].split('://').first
        operator_class(adapter).new(configuration).reset
      end
    end
  end
end

In rails_helper.rb/spec_helper.rb:
require 'rails'

unless Rails.env.test?
  abort "Combustion should not be reopened in #{Rails.env} environment."
end

module Combustion
  class Database
    class Reset
      def call
        configuration = ActiveRecord::Base.configurations['test']
        adapter = configuration['adapter'] || configuration['url'].split('://').first
        operator_class(adapter).new(configuration).reset
      end
    end
  end
end

This allows me to run a rackup session and rspec at the same time.

Oh, didn't see the additions to the comment until just now!
In 6d2fe4ed1b6cb3539158dfcbb8f3ea579fc1bc33 I've removed the hard-coded references to the environment - so using RAILS_ENV to dictate which env you want should hopefully do what you're after? (The default will still be test).
If that doesn't quite fit, do let me know.

That was quick. Thanks a lot. I'll give it a spin in the next days!

Just saw your additional thoughts now…
I just want to confirm I'm understanding your point - most people use rackup for dev environments, but by default in engines with combustion, it'd be the test env - and this difference is the concern? (Not saying you're wrong to have this concern! Just want to make sure I'm understanding it correctly)

So until this commit the environment always defaulted to the test database. Now this behaviour would change for all projects since rackup defaults to development environment.
So before it was:
development environment & test database
Now it would be:
development environment & development database
I'm not sure how many projects would be negatively affected by this.
Also I figured out that the datbase reset always occurs on all databases, which prohibits running a rackuped application and specs at the same time.
I'm on holiday in Marocco at the moment and have very spotty internet, so my answers could take a while. But I'm going to submit a merge request in the beginning of march that would allow to run reset only on the database of the current Rails.env.

@pat The code I submitted excludes default databases in Rails environments that are not currently in use from beeing resetted. The feature to reset other databases by default is kept tough. Ie. when you run in the development environment, the test will not be reset, the database foo will tough.
I personally don't think this is a very good approach since its inconsistent and can't account for environments that developers might add later, ie. staging. But I could not come up with a better solution.
What do you think

Closing this now that #83 is merged.


ci(Mergify): configuration update

This change has been made by @VelvetThePanda from https://mergify.com config editor.

This PR adds checks for draft PRs and marked PRs that should be excluded. e.g. #576


Disable this test on watchOS

I've not been able to fill in the 32-bit expectations here yet. Until I can do that, this won't work on any 32-bit platforms.

@swift-ci Please test


Clickable highlighted region and non-clickable backdrop.

How to make this happen?
using md-tour

Hi @hakimio ,
Thanks for your reply and quick help. Its says that we have to modify the library code. I am adding the library as a dependency in my angular app and using a custom template. Something like this...
<ng-template #defaultTemplate let-step="step">                ...   </ng-template>
How do we modify in the custom template?

@aniket-02 you can't. You have to modify the line in the library indicated by Isaac in his comment.

@hakimio thanks for the help.
@isaacplmann Are there any immediate plans of providing an endpoint / API for the toggling of the above feature?


colour change of object

After converting the object to asset object colour has been changing every time how can I get same color as object after converting asset.
Please give me some solution
Thank you

For advice and general questions, please use the Sceneform tag on
Stack Overflow: https://stackoverflow.com/questions/tagged/Sceneform
In addition, please see the Sceneform SDK developer documentation and API reference.


[FEA] Add in tests for special parquet/ORC compression formats

Is your feature request related to a problem? Please describe.
Spark does not support some compression types without extra jars.  We need a way to know if
these are available or not so we can properly test them.
'lzo', 'lz4', 'brotli', 'zstd'
Parquet supports all of these types, ORC only supports 'lzo'

CuDF only supports brotli at this time.


Add custom labels to projects in Flyte control plane

Motivation: Why do you think this is important?
Providing custom labels to projects will make it easier to attach metadata to Flyte projects in a scalable, general way that would benefit Lyft and other users.
Goal: What should the final outcome look like, ideally?
An ideal outcome would involve the Projects data to have a new field that can hold arbitrary K/V pairs for labeling projects, e.g. with contact information, escalation policy, etc.
Describe alternatives you've considered
Instead, we can store this metadata outside Flyte.
Flyte component

[ ] Overall
[ ] Flyte Setup and Installation scripts
[ ] Flyte Documentation
[ ] Flyte communication (slack/email etc)
[ ] FlytePropeller
[ ] FlyteIDL (Flyte specification language)
[ ] Flytekit (Python SDK)
[x] FlyteAdmin (Control Plane service)
[ ] FlytePlugins
[ ] DataCatalog
[ ] FlyteStdlib (common libraries)
[ ] FlyteConsole (UI)
[ ] Other

Is this a blocker for you to adopt Flyte
No; Flyte is currently being used at Lyft.

https://github.com/lyft/flyteadmin/pull/114

👀 @EngHabu @kumare3 — updated both of these PR's.

This is part of 0.8.0 release


Intros

@drakonux I've added content to these pages so they don't look empty. They need more work to be more attractive.


Paypal about:blank window not closed on iOS

Describe the bug
After submitting the payment data using the paypal smart button the pop up window stays in loading and it is not closed.
The action passed from backend is:
{ type: 'redirect', paymentData: '', method: 'GET', url: 'https://test.adyen.com/hpp/checkout.shtml' }
The only way that i had to handle the action from backend is using createFromAction method from adyen components.
I set the status of dropin to ready after action is received but nothing happens.
Expected behavior
Close the pop up window after createFromAction and redirection to paypal
Smartphone (please complete the following information):

Device: iPhone 6s
OS: iOS 14.2
Browser Safari

Additional context
As backend i use magento with magento-adyen 6.6.5 plugin and as front end the PWA using Vuestorefront and adyen-web 3.18.2

Hi @gepdev, and thanks for reaching out.
That action object doesn't seem to be correct.
The PayPal component should return a paymentMethod object which includes the subtype:
  "paymentMethod": {
    "type": "paypal",
    "subtype": "sdk"
  }

in order to the /payments response to contain an action of type sdk:
"action": {
  "paymentData": "...",
  "paymentMethodType": "paypal",
  "sdkData": {
    "token": "..."
  },
  "type": "sdk"
}

Could you check if this is the case? Is the component returning the subtype?

Hi @pabloai, thanks for your reply.
action is of the type redirect which i'm gettind as response of the V1/adyen/orders/:orderId/payment-status endpoint from magento api. Consider that i'm using magento pwa type of integration.
https://docs.adyen.com/checkout/components-web/#step-4-additional-front-end
This is example of the response of the endpoint:
{
  "code": 200,
  "result": {
    "threeDS2": false,
    "checkoutAPM": true,
    "threeDSType": "RedirectShopper",
    "resultCode": "RedirectShopper",
    "action": {
      "type": "redirect",
      "method": "GET",
      "url": "https://test.adyen.com/hpp/checkout.shtml?u=redirectPayPal&p=",
      "paymentData": "..."
    },
    "details": [
      {
        "key": "payload",
        "type": "text"
      }
    ]
  }
}

With this type of action paypaDropin.handleAction(action) throws error as it needs different type of action as in you example.
So my solution was to handle this redirect action using the method checkout.createFromAction(action).mount($refs.checkout)
https://docs.adyen.com/checkout/components-web/#step-4-additional-front-end
And this in my case works but then after redirection to the url https://test.adyen.com/hpp/checkout.shtml only in iOS the pop up window doesn't close. All other device types the pop up is closed.
I set paypalDropin.setStatus('ready') before executing createFromAction()
Is it ok how i'm doing? Is there any solution/workaround to manage the opened window?

Hi @gepdev,
There was an issue with our API which caused a wrong action object to be returned for PayPal. This was fixed yesterday and should be back to normal. Could you check if your issue was related to this? Let us know if the issue persists.
As stated before, the action type should be sdk, and passing the action object to the handleAction method should work.
Let us know if this helps, cheers.

Hi @pabloai,
no i have tried with my current configuration but i still have the issue.
Should I update the magento adyen plugin? Currently I use 6.6.5
Thanks for your help
cheers

Hi @pabloai this is not an issue anymore. Thanks for the support


service not available 403 Forbidden

Hi,
i update the repository and now i receive the message Forbidden.

does anyone have this error too?
Best Regards
Thomas

Yes, I have the same error after my update today

In the Z2UI5_CL_HTTP_HANDLER there is a fixed name for the pathname that is beeing used:
 sap.z2ui5.pathname = "/sap/bc/http/sap/y2ui5_http_handler/";

OK, commenting line 356 did the trick for me.

ah forgot to delete my test setup, sorry and thanks. updatet the main branch (https://github.com/abap2UI5/abap2UI5/pull/358), should work now.

i comment the line and it works.
Thank you for the help.


test: relax partial_evict_tenant

Hopefully handles #3978 (leaving it open for now). test_partial_evict_tenant can fail multiple times so even though we retry it as flaky, it will still haunt us.
I do not have an explanation why this happens, I think it's related to the different sizes of the "last" smallest layer. See most recent analysis: https://github.com/neondatabase/neon/issues/3978#issuecomment-1735472290 (2 + 3 failures on a single run).

No partial_evict_tenant failure for first commit a6a1b9f

:see_no_evil: a build-neon failure, fixing that in #5386.

This still has a local failure rate of 11/68 or 16%.

Local failure rate: 0/132 with the latest push.

Unrelated note after watching the RUST_LOG=pageserver=debug logs:
$ grep 'timeline resident layers count:' test_output/test_partial_evict_tenant\[debug-pg*\]/repo/pageserver_1/pageserver.log
test_output/test_partial_evict_tenant[debug-pg14]/repo/pageserver_1/pageserver.log:2023-09-27T06:32:41.126716Z DEBUG timeline resident layers count: 16 tenant_id=4d5a746881005831fc91cb486e85c8fd timeline_id=55efa8d1b6671a55965e7ecdb3e1d278
test_output/test_partial_evict_tenant[debug-pg14]/repo/pageserver_1/pageserver.log:2023-09-27T06:32:41.126745Z DEBUG timeline resident layers count: 22 tenant_id=0c0bb3f0a673610f2b2d33f6e67f82ea timeline_id=4e0f26bae97d9cbc9a647c529596d532
test_output/test_partial_evict_tenant[debug-pg15]/repo/pageserver_1/pageserver.log:2023-09-27T06:32:53.840114Z DEBUG timeline resident layers count: 16 tenant_id=268a6b12057548c72ebc7c85d291bccf timeline_id=db3af6d3d5195377b72126011a28bbb2
test_output/test_partial_evict_tenant[debug-pg15]/repo/pageserver_1/pageserver.log:2023-09-27T06:32:53.840145Z DEBUG timeline resident layers count: 21 tenant_id=e45154ed0c92a5f8bac5b2196aafc538 timeline_id=eb7c0f3b2b5714f017eef4055fdec200
test_output/test_partial_evict_tenant[debug-pg16]/repo/pageserver_1/pageserver.log:2023-09-27T06:33:10.728316Z DEBUG timeline resident layers count: 26 tenant_id=6978cc128eb6646663633d2e430eb7f2 timeline_id=072a26a8cc3d24650b7c800657d6dd10
test_output/test_partial_evict_tenant[debug-pg16]/repo/pageserver_1/pageserver.log:2023-09-27T06:33:10.728360Z DEBUG timeline resident layers count: 36 tenant_id=cf903f4e2be93bc039f91d5fe70edd24 timeline_id=209e3dda564155907362e7b8b02e9f3a

So test_partial_evict_tenant creates many more layers for pg16 than for pg14 or pg15.

No flaky tests in the last report!


java.lang.NullPointerException

I set up some configuration, with some tomcat instance, and a webapp.
I'm running plugin version v3.0.2 on Windows 7, IntelliJ CE 2019.1
When I click "run", Event Log shows the following error message:

Error running 'MyProject Tomcat': java.langNullPointerException

Does the plugin create a logfile?
Can I debug the plugin short of compiling it?

I set up some configuration, with some tomcat instance, and a webapp.
I'm running plugin version v3.0.2 on Windows 7, IntelliJ CE 2019.1
When I click "run", Event Log shows the following error message:

Error running 'MyProject Tomcat': java.langNullPointerException

Does the plugin create a logfile?
Can I debug the plugin short of compiling it?

please update intellij ce 2019.3 version and smart tomcat 3.6.0 version


Summary by CodeRabbit

New Features

Enhanced collision prevention logic by incorporating entity state checks, ensuring that actions are only processed for alive entities.

Bug Fixes

Improved handling of collision events to prevent unnecessary processing for entities that are not alive.

mald pr

mald pr

crawling's main advantage is in a fight how can you not understand that !!
deleting stuff for the reason of "unbalanced" is uncool. we still have unlimited scram implants and nobody said a thing

send media

also mald pr


Clarify the usage of callback fields inside oneof sections in the docs

Add a few lines to the docs to resolve #357.

Thanks


create to_json function

Fixes #33
add new function "to_json" inside new file "utilities.py"

No, I think we were going to close this as I believe @bradlo had something else in mind.


Add Grouping Rows

I propose to add grouping/sub-grouping of rows.
The grouping would be in a custom column on the left of the jExcel table, and would look similar to

.
Optionally, later, we could add an option to show summary at top/bottom like

Here is another example of how we could approach this:
http://www.ok-soft-gmbh.com/jqGrid/OK/hasSubrgid.htm


初步运行出现错误，已经提供详细信息

环境
python37
由于setp.MD里的tensorflow并不支持10我安装了tensorflow最新版
错误信息
(chineseocr) ybt@ybt:~/chineseocr$ ipython app.py 8080
Nms engine gpu_nms: None ,cython_nms: None ,python_nms: <function nms at 0x7fb08f051ea0>
WARNING: Logging before flag parsing goes to stderr.
W0702 16:04:14.308718<PHONE_NUMBER>20352 deprecation_wrapper.py:119] From /home/ybt/chineseocr/text/opencv_dnn_detect.py:12: The name tf.ConfigProto is deprecated. Please use tf.compat.v1.ConfigProto instead.

W0702 16:04:14.308851<PHONE_NUMBER>20352 deprecation_wrapper.py:119] From /home/ybt/chineseocr/text/opencv_dnn_detect.py:13: The name tf.Session is deprecated. Please use tf.compat.v1.Session instead.

2019-07-02 16:04:14.315120: I tensorflow/core/platform/cpu_feature_guard.cc:142] Your CPU supports instructions that this TensorFlow binary was not compiled to use: AVX2 FMA
2019-07-02 16:04:14.318736: I tensorflow/core/platform/profile_utils/cpu_utils.cc:94] CPU Frequency:<PHONE_NUMBER> Hz
2019-07-02 16:04:14.319547: I tensorflow/compiler/xla/service/service.cc:168] XLA service 0x559a40226ee0 executing computations on platform Host. Devices:
2019-07-02 16:04:14.319561: I tensorflow/compiler/xla/service/service.cc:175]   StreamExecutor device (0): <undefined>, <undefined>
2019-07-02 16:04:14.319677: I tensorflow/stream_executor/platform/default/dso_loader.cc:42] Successfully opened dynamic library libcuda.so.1
2019-07-02 16:04:14.429587: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:1005] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2019-07-02 16:04:14.429986: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1640] Found device 0 with properties:
name: GeForce RTX 2070 major: 7 minor: 5 memoryClockRate(GHz): 1.62
pciBusID: 0000:01:00.0
2019-07-02 16:04:14.430014: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:1005] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2019-07-02 16:04:14.430388: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1640] Found device 1 with properties:
name: GeForce RTX 2070 major: 7 minor: 5 memoryClockRate(GHz): 1.62
pciBusID: 0000:02:00.0
2019-07-02 16:04:14.430425: I tensorflow/stream_executor/platform/default/dso_loader.cc:42] Successfully opened dynamic library libcudart.so.10.0
2019-07-02 16:04:14.430441: I tensorflow/stream_executor/platform/default/dso_loader.cc:42] Successfully opened dynamic library libcublas.so.10.0
2019-07-02 16:04:14.430454: I tensorflow/stream_executor/platform/default/dso_loader.cc:42] Successfully opened dynamic library libcufft.so.10.0
2019-07-02 16:04:14.430467: I tensorflow/stream_executor/platform/default/dso_loader.cc:42] Successfully opened dynamic library libcurand.so.10.0
2019-07-02 16:04:14.431135: I tensorflow/stream_executor/platform/default/dso_loader.cc:42] Successfully opened dynamic library libcusolver.so.10.0
2019-07-02 16:04:14.431159: I tensorflow/stream_executor/platform/default/dso_loader.cc:42] Successfully opened dynamic library libcusparse.so.10.0
2019-07-02 16:04:14.432786: I tensorflow/stream_executor/platform/default/dso_loader.cc:42] Successfully opened dynamic library libcudnn.so.7
2019-07-02 16:04:14.432822: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:1005] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2019-07-02 16:04:14.433208: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:1005] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2019-07-02 16:04:14.433596: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:1005] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2019-07-02 16:04:14.433975: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:1005] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2019-07-02 16:04:14.434346: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1763] Adding visible gpu devices: 0, 1
2019-07-02 16:04:15.979509: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1181] Device interconnect StreamExecutor with strength 1 edge matrix:
2019-07-02 16:04:15.979534: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1187]      0 1
2019-07-02 16:04:15.979539: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1200] 0:   N N
2019-07-02 16:04:15.979542: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1200] 1:   N N
2019-07-02 16:04:15.979759: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:1005] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2019-07-02 16:04:15.980162: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:1005] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2019-07-02 16:04:15.980545: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:1005] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2019-07-02 16:04:15.980923: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:1005] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2019-07-02 16:04:15.981297: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1326] Created TensorFlow device (/job:localhost/replica:0/task:0/device:GPU:0 with 6419 MB memory) -> physical GPU (device: 0, name: GeForce RTX 2070, pci bus id: 0000:01:00.0, compute capability: 7.5)
2019-07-02 16:04:15.981711: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:1005] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2019-07-02 16:04:15.982093: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:1005] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2019-07-02 16:04:15.982459: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1326] Created TensorFlow device (/job:localhost/replica:0/task:0/device:GPU:1 with 6938 MB memory) -> physical GPU (device: 1, name: GeForce RTX 2070, pci bus id: 0000:02:00.0, compute capability: 7.5)
2019-07-02 16:04:15.983536: I tensorflow/compiler/xla/service/service.cc:168] XLA service 0x559ab9533340 executing computations on platform CUDA. Devices:
2019-07-02 16:04:15.983546: I tensorflow/compiler/xla/service/service.cc:175]   StreamExecutor device (0): GeForce RTX 2070, Compute Capability 7.5
2019-07-02 16:04:15.983549: I tensorflow/compiler/xla/service/service.cc:175]   StreamExecutor device (1): GeForce RTX 2070, Compute Capability 7.5
W0702 16:04:15.984309<PHONE_NUMBER>20352 deprecation.py:323] From /home/ybt/chineseocr/text/opencv_dnn_detect.py:14: FastGFile.__init__ (from tensorflow.python.platform.gfile) is deprecated and will be removed in a future version.
Instructions for updating:
Use tf.gfile.GFile.
W0702 16:04:15.984464<PHONE_NUMBER>20352 deprecation_wrapper.py:119] From /home/ybt/chineseocr/text/opencv_dnn_detect.py:15: The name tf.GraphDef is deprecated. Please use tf.compat.v1.GraphDef instead.

W0702 16:04:17.332983<PHONE_NUMBER>20352 deprecation_wrapper.py:119] From /home/ybt/chineseocr/text/opencv_dnn_detect.py:21: The name tf.placeholder is deprecated. Please use tf.compat.v1.placeholder instead.

W0702 16:04:17.389131<PHONE_NUMBER>20352 deprecation_wrapper.py:119] From /home/ybt/chineseocr/text/keras_detect.py:12: The name tf.get_default_graph is deprecated. Please use tf.compat.v1.get_default_graph instead.

W0702 16:04:17.390870<PHONE_NUMBER>20352 deprecation.py:506] From /home/ybt/anaconda3/envs/chineseocr/lib/python3.7/site-packages/tensorflow/python/ops/init_ops.py:1251: calling VarianceScaling.__init__ (from tensorflow.python.ops.init_ops) with dtype is deprecated and will be removed in a future version.
Instructions for updating:
Call initializer instance with the dtype argument instead of passing it to the constructor
2019-07-02 16:04:20.481785: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:1005] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2019-07-02 16:04:20.482196: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1640] Found device 0 with properties:
name: GeForce RTX 2070 major: 7 minor: 5 memoryClockRate(GHz): 1.62
pciBusID: 0000:01:00.0
2019-07-02 16:04:20.482234: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:1005] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2019-07-02 16:04:20.482606: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1640] Found device 1 with properties:
name: GeForce RTX 2070 major: 7 minor: 5 memoryClockRate(GHz): 1.62
pciBusID: 0000:02:00.0
2019-07-02 16:04:20.482634: I tensorflow/stream_executor/platform/default/dso_loader.cc:42] Successfully opened dynamic library libcudart.so.10.0
2019-07-02 16:04:20.482643: I tensorflow/stream_executor/platform/default/dso_loader.cc:42] Successfully opened dynamic library libcublas.so.10.0
2019-07-02 16:04:20.482653: I tensorflow/stream_executor/platform/default/dso_loader.cc:42] Successfully opened dynamic library libcufft.so.10.0
2019-07-02 16:04:20.482660: I tensorflow/stream_executor/platform/default/dso_loader.cc:42] Successfully opened dynamic library libcurand.so.10.0
2019-07-02 16:04:20.482679: I tensorflow/stream_executor/platform/default/dso_loader.cc:42] Successfully opened dynamic library libcusolver.so.10.0
2019-07-02 16:04:20.482686: I tensorflow/stream_executor/platform/default/dso_loader.cc:42] Successfully opened dynamic library libcusparse.so.10.0
2019-07-02 16:04:20.482701: I tensorflow/stream_executor/platform/default/dso_loader.cc:42] Successfully opened dynamic library libcudnn.so.7
2019-07-02 16:04:20.482727: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:1005] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2019-07-02 16:04:20.483106: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:1005] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2019-07-02 16:04:20.483485: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:1005] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2019-07-02 16:04:20.483865: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:1005] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2019-07-02 16:04:20.484302: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1763] Adding visible gpu devices: 0, 1
2019-07-02 16:04:20.484385: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1181] Device interconnect StreamExecutor with strength 1 edge matrix:
2019-07-02 16:04:20.484392: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1187]      0 1
2019-07-02 16:04:20.484395: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1200] 0:   N N
2019-07-02 16:04:20.484397: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1200] 1:   N N
2019-07-02 16:04:20.484558: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:1005] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2019-07-02 16:04:20.484943: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:1005] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2019-07-02 16:04:20.485329: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:1005] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2019-07-02 16:04:20.485700: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1326] Created TensorFlow device (/job:localhost/replica:0/task:0/device:GPU:0 with 6419 MB memory) -> physical GPU (device: 0, name: GeForce RTX 2070, pci bus id: 0000:01:00.0, compute capability: 7.5)
2019-07-02 16:04:20.485728: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:1005] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2019-07-02 16:04:20.486094: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1326] Created TensorFlow device (/job:localhost/replica:0/task:0/device:GPU:1 with 6938 MB memory) -> physical GPU (device: 1, name: GeForce RTX 2070, pci bus id: 0000:02:00.0, compute capability: 7.5)
W0702 16:04:23.937996<PHONE_NUMBER>20352 deprecation_wrapper.py:119] From /home/ybt/chineseocr/text/keras_detect.py:23: The name tf.keras.backend.get_session is deprecated. Please use tf.compat.v1.keras.backend.get_session instead.

---------------------------------------------------------------------------
InvalidArgumentError                      Traceback (most recent call last)
~/chineseocr/app.py in <module>
     12 from PIL import Image
     13 web.config.debug  = True
---> 14 import model
     15 render = web.template.render('templates', base='base')
     16 from config import DETECTANGLE

~/chineseocr/model.py in <module>
     28 else:
     29     ## keras版本文字检测
---> 30     from text import keras_detect as detect
     31
     32 print("Text detect engine:{}".format(opencvFlag))

~/chineseocr/text/keras_detect.py in <module>
     24 image_shape = K.placeholder(shape=(2, ))##图像原尺寸:h,w
     25 input_shape = K.placeholder(shape=(2, ))##图像resize尺寸:h,w
---> 26 box_score = box_layer([*textModel.output,image_shape,input_shape],anchors, num_classes)
     27
     28

~/chineseocr/text/keras_yolo3.py in box_layer(inputs, anchors, num_classes)
    371         scores.append(box_score)
    372
--> 373     boxes = concatenate(boxes, axis=0)
    374     scores = concatenate(scores, axis=0)
    375

~/anaconda3/envs/chineseocr/lib/python3.7/site-packages/tensorflow/python/keras/layers/merge.py in concatenate(inputs, axis, **kwargs)
    685       A tensor, the concatenation of the inputs alongside axis `axis`.
    686   """
--> 687   return Concatenate(axis=axis, **kwargs)(inputs)
    688
    689

~/anaconda3/envs/chineseocr/lib/python3.7/site-packages/tensorflow/python/keras/engine/base_layer.py in __call__(self, inputs, *args, **kwargs)
    559       # framework.
    560       if base_layer_utils.needs_keras_history(inputs):
--> 561         base_layer_utils.create_keras_history(inputs)
    562
    563     # Handle Keras mask propagation from previous layer to current layer.

~/anaconda3/envs/chineseocr/lib/python3.7/site-packages/tensorflow/python/keras/engine/base_layer_utils.py in create_keras_history(tensors)
    198     keras_tensors: The Tensors found that came from a Keras Layer.
    199   """
--> 200   _, created_layers = _create_keras_history_helper(tensors, set(), [])
    201   return created_layers
    202

~/anaconda3/envs/chineseocr/lib/python3.7/site-packages/tensorflow/python/keras/engine/base_layer_utils.py in _create_keras_history_helper(tensors, processed_ops, created_layers)
    244             constants[i] = backend.function([], op_input)([])
    245       processed_ops, created_layers = _create_keras_history_helper(
--> 246           layer_inputs, processed_ops, created_layers)
    247       name = op.name
    248       node_def = op.node_def.SerializeToString()

~/anaconda3/envs/chineseocr/lib/python3.7/site-packages/tensorflow/python/keras/engine/base_layer_utils.py in _create_keras_history_helper(tensors, processed_ops, created_layers)
    244             constants[i] = backend.function([], op_input)([])
    245       processed_ops, created_layers = _create_keras_history_helper(
--> 246           layer_inputs, processed_ops, created_layers)
    247       name = op.name
    248       node_def = op.node_def.SerializeToString()

~/anaconda3/envs/chineseocr/lib/python3.7/site-packages/tensorflow/python/keras/engine/base_layer_utils.py in _create_keras_history_helper(tensors, processed_ops, created_layers)
    244             constants[i] = backend.function([], op_input)([])
    245       processed_ops, created_layers = _create_keras_history_helper(
--> 246           layer_inputs, processed_ops, created_layers)
    247       name = op.name
    248       node_def = op.node_def.SerializeToString()

~/anaconda3/envs/chineseocr/lib/python3.7/site-packages/tensorflow/python/keras/engine/base_layer_utils.py in _create_keras_history_helper(tensors, processed_ops, created_layers)
    244             constants[i] = backend.function([], op_input)([])
    245       processed_ops, created_layers = _create_keras_history_helper(
--> 246           layer_inputs, processed_ops, created_layers)
    247       name = op.name
    248       node_def = op.node_def.SerializeToString()

~/anaconda3/envs/chineseocr/lib/python3.7/site-packages/tensorflow/python/keras/engine/base_layer_utils.py in _create_keras_history_helper(tensors, processed_ops, created_layers)
    244             constants[i] = backend.function([], op_input)([])
    245       processed_ops, created_layers = _create_keras_history_helper(
--> 246           layer_inputs, processed_ops, created_layers)
    247       name = op.name
    248       node_def = op.node_def.SerializeToString()

~/anaconda3/envs/chineseocr/lib/python3.7/site-packages/tensorflow/python/keras/engine/base_layer_utils.py in _create_keras_history_helper(tensors, processed_ops, created_layers)
    242             constants[i] = op_input
    243           else:
--> 244             constants[i] = backend.function([], op_input)([])
    245       processed_ops, created_layers = _create_keras_history_helper(
    246           layer_inputs, processed_ops, created_layers)

~/anaconda3/envs/chineseocr/lib/python3.7/site-packages/tensorflow/python/keras/backend.py in __call__(self, inputs)
   3290
   3291     fetched = self._callable_fn(*array_vals,
-> 3292                                 run_metadata=self.run_metadata)
   3293     self._call_fetch_callbacks(fetched[-len(self._fetches):])
   3294     output_structure = nest.pack_sequence_as(

~/anaconda3/envs/chineseocr/lib/python3.7/site-packages/tensorflow/python/client/session.py in __call__(self, *args, **kwargs)
   1456         ret = tf_session.TF_SessionRunCallable(self._session._session,
   1457                                                self._handle, args,
-> 1458                                                run_metadata_ptr)
   1459         if run_metadata:
   1460           proto_data = tf_session.TF_GetBuffer(run_metadata_ptr)

InvalidArgumentError: 2 root error(s) found.
  (0) Invalid argument: You must feed a value for placeholder tensor 'Placeholder_368' with dtype float and shape [2]
	 [[{{node Placeholder_368}}]]
	 [[strided_slice_10/_2295]]
  (1) Invalid argument: You must feed a value for placeholder tensor 'Placeholder_368' with dtype float and shape [2]
	 [[{{node Placeholder_368}}]]
0 successful operations.
0 derived errors ignored.

咱们问题一样，不知道其他人用cuda10 用的啥版本的tensorflow

咱们问题一样，不知道其他人用cuda10 用的啥版本的tensorflow

我已经完成了，在安装的时候不安装 keras 即可，因为使用 cuda10 的 ts 已经自带了 keras 按照指定版本后方法参数变了

@StringKe 我刚刚也弄好了，把tensorflow 换成 1.13.1 就好了

@StringKe 我刚刚也弄好了，把tensorflow 换成 1.13.1 就好了

我也使用的 1.13.1, 不太清除post返回的box里的数组是什么


[fix] #validate_imported_groups when imported_gws_group is nil

Coverage increased (+0.05%) to 59.7% when pulling e34028720677bb65c92077a77daeca80b14088eb on itowtips:fix-webmail-user into 716dbbf5d1e8aeea661eb55e91551c3d2986da5f on shirasagi:master.


Unfriendly error messages

Account creation - duplicated user's name in domain
Actual result:

Expected result: The user user name already exists in domain domain name

User creation - duplicated user's name in account
Actual result:

Expected result: The user user name already exists in account account name

VM - expunge of an already expunged vm
Actual result:

Expected result: VM vm name already expunged

VM - starting the vm of disabled account
Actual result:

Expected result: You can't start VM because it's owner account name is disabled

Images tags - creating a tag with a key duplicated value via main Add button or via tag edit
Actual result:

Expected result: Tag with key key value already exists

Connected Feature ID:
account_create
account_user_create
vm_expunge
vm_start
image_tag_create
image_tag_edit

All these errors come from the server. So this is not a bug, this requires additional functionality.
A possible solution can be is to store error numbers and display our custom messages.

@tamazlykar @ershovaelena
Not a bug. Open new feature for each. Don't fix it.


How can I add a background page?

I need add one background for all pages like:

How can I do that?

Sorry I don't know.
You may want to check out this.
Sorry for the late reply!


Typescript bug: if I try use typescript file with .ts extension as a manifest script, build incorrectly replace the script name

Expectations:

I set up typescript for the project
I would like to use .ts extension for the scripts as a manifest script
I am waiting that everithing will going correct

Reality:
If I try to use .ts scripts inside manifest, build replace them to incorrect script name:
{
  "name": "Name",
  "commands": [
    {
      "name": "Run",
      "identifier": "run",
      "script": "./run.ts"
    }
  ]
}

Will replace to:
{
  "name": "Name",
  "commands": [
    {
      "name": "Run",
      "identifier": "run",
      "script": "./__run_ts"
    }
  ]
}

NOTICE, that ./__run_ts incorrect script name!

PR added to fix this issue: #283