Issues on examples/example.py

❓ Questions and Help
Hi guys!
I have installed habitat-sim using conda with the following command:
conda install habitat-sim -c conda-forge -c aihabita-nightly.
However when I tried to run the example/example.py:
python examples/example.py
I met this error:
sim_cfg.physics_config_file = ./data/default.physics_config.json
Traceback (most recent call last):
File "examples/example.py", line 70, in
perf = demo_runner.example()
File "/home/yh/habitat-sim/examples/demo_runner.py", line 409, in example
start_state = self.init_common()
File "/home/yh/habitat-sim/examples/demo_runner.py", line 322, in init_common
self._cfg = make_cfg(self._sim_settings)
File "/home/yh/habitat-sim/examples/settings.py", line 65, in make_cfg
"sensor_subtype": habitat_sim.SensorSubType.PINHOLE,
AttributeError: module 'habitat_sim' has no attribute 'SensorSubType'
Could anymore provide some help?

This should get fixed tonight when the new nightly build goes out


Apple specific hardware testing

Lack of OSX related support for Apple's specific hardware.

Pip wheels for Apples M1/M2 chips are not done by the CI/CD pipeline implemented. Instead, when running pip install openmtpk on an Apple hardware specific machine (Macbooks 2020+), SWIG is needed as a dependency to build the wheel from scratch. This isn't an issue but would be nice to offer more support for this.
openMTPK's source API (C++) is also not tested on Apple specific hardware. This goes in hand with #27 where the build process on Apple computers hangs on the GoogleTest portion of the process.

Hi @akielaries, can you provide more context on the SWIG dependency? The fix that I'm working is being tested on a M2 machine and so far I faced zero issues even without SWIG installed.

In the openmtpk PyPI package files here it appears support for aarch64 OSX machines is now included. Let me confirm this on the M1 and I'll reply with my results

$ pip install --no-cache openmtpk
Collecting openmtpk
  Downloading openmtpk-0.9.7-cp311-cp311-macosx_11_0_arm64.whl (189 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 189.3/189.3 kB 3.3 MB/s eta 0:00:00
Installing collected packages: openmtpk
Successfully installed openmtpk-0.9.7

That's my output for pip install.

Yup, I went through pypa/cibuildwheel and you're in fact building wheels for multiple platforms (including Apple Silicon). I forced build from source and yup, swig is a requirement... You're right.
In my opinion, easiest way to handle this is to add it to build requirements while installing from source. What is your take on this? As far as wheel builds are concerned, the pipeline seems to be in good shape for any architecture on demand.

Thank you for pasting your output! This is very interesting I'll definitely need to test this on my machines.
So my only thoughts on improving this are sort of a pain and possibly a stretch. The current pipeline makes use of some 3rd party Github Actions, Docker, as well as QEMU to build & test the wheels for these platforms. I am thinking, if it is possible, to get an OSX M1 Docker/QEMU image to plug into this process. This wouldn't be to create the wheel but instead be apart of the post-PyPI upload tests that perform a pip install on the recently uploaded version and run the samples for Python that way we can test on OSX for M1 and M2. These post-upload tests are located here
Also feel free to reach out in any way if you'd like to brainstorm some possible solutions for this.

❯ g++-12 mtx.cpp -I/usr/local/include/ -L/usr/local/lib

  "__ZN4gpmp6linalg3Mtx11mtx_add_f90EPfS2_S2_m", referenced from:
      __Z11mtx_add_f90v in ccWB5MUw.o
  "__ZN4gpmp6linalg3Mtx11std_mtx_addIdEEvRKSt6vectorIS3_IT_SaIS4_EESaIS6_EESA_RS8_", referenced from:
      __Z16run_mtx_add_doubv in ccWB5MUw.o
  "__ZN4gpmp6linalg3Mtx11std_mtx_addIfEEvRKSt6vectorIS3_IT_SaIS4_EESaIS6_EESA_RS8_", referenced from:
      __Z15run_mtx_add_fltv in ccWB5MUw.o
  "__ZN4gpmp6linalg3Mtx11std_mtx_addIiEEvPKT_S5_PS3_ii", referenced from:
      __Z15run_mtx_add_arrv in ccWB5MUw.o
  "__ZN4gpmp6linalg3Mtx11std_mtx_addIiEEvRKSt6vectorIS3_IT_SaIS4_EESaIS6_EESA_RS8_", referenced from:
      __Z11run_mtx_addv in ccWB5MUw.o
  "__ZN4gpmp6linalg3Mtx7mtx_addEPKiS3_Piii", referenced from:
      __Z15run_mtx_add_arrv in ccWB5MUw.o
  "__ZN4gpmp6linalg3Mtx7mtx_addERKSt6vectorIS2_IdSaIdEESaIS4_EES8_RS6_", referenced from:
      __Z16run_mtx_add_doubv in ccWB5MUw.o
  "__ZN4gpmp6linalg3Mtx7mtx_addERKSt6vectorIS2_IfSaIfEESaIS4_EES8_RS6_", referenced from:
      __Z15run_mtx_add_fltv in ccWB5MUw.o
  "__ZN4gpmp6linalg3Mtx7mtx_addERKSt6vectorIS2_IiSaIiEESaIS4_EES8_RS6_", referenced from:
      __Z11run_mtx_addv in ccWB5MUw.o
ld: symbol(s) not found for architecture x86_64
collect2: error: ld returned 1 exit status

will need to dig into this error produced on OSX


Texture flip parameter should be None by default

Currently the flip parameter is True by default. This makes sense for 2d textures, but it doesn't make sense for texture arrays. Instead each loader type should have a default behavior when flip is None.

2d loader use True
array loader use False

Technically this is still true, but on a second thought I think this will just create confusion.


Grammatical and Spelling Errors

Hello,
The spelling of Sign Up and Bookmarks is wrong.
I think we should correct it!

Hello @CodeWithHV,
I want to take up this issue and resolve it.

All the best @HVbajoria


Add API Doc of artist

Add in API documentation (api_riocuartobandasderock.md) all routes of Artist and BandMember

finish in commit ddb93e8


Add hotel emoji as favicon (from EmojiOne)

I like to have hotel running in a pinned tab in Chrome. However, hotel doesn't have a favicon right now, so I can't find it straight away when I have other pinned tabs.
Since there is a fitting favicon in the form of the "Hotel" emoji U+1F3E8, I included that emoji from EmojiOne. My tab bar looks like this now:

🏨 👍

Personally, I think the EmojiOne version is a little too bright and lacks contrast on a gray background so I may replace it with another one (until hotel gets a real logo).
That said, that's a good idea. Hotel was lacking a favicon :)
Thank you for the PR!


optimize data import speed

Codecov Report

Merging #149 (ca2eb79) into master (c63daab) will increase coverage by 0.55%.
The diff coverage is 68.47%.

@@            Coverage Diff             @@
##           master     #149      +/-   ##
==========================================
+ Coverage   57.57%   58.12%   +0.55%
==========================================
  Files          41       41
  Lines        4782     4969     +187
==========================================
+ Hits         2753     2888     +135
- Misses       1668     1717      +49
- Partials      361      364       +3

Impacted Files
Coverage Δ

base/filter.go
100.00% <ø> (ø)

base/index.go
77.14% <ø> (ø)

base/random.go
100.00% <ø> (ø)

base/util.go
62.06% <ø> (ø)

config/config.go
91.86% <ø> (ø)

floats/floats.go
62.71% <ø> (ø)

storage/cache/database.go
33.33% <ø> (ø)

storage/cache/no_database.go
0.00% <ø> (ø)

storage/cache/redis.go
66.66% <ø> (ø)

storage/data/database.go
65.21% <ø> (-6.22%)
:arrow_down:

... and 7 more

Continue to review full report at Codecov.

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


Possible API gate regression due to openwhisk-client-go changes

There have been quite some changes in openwhisk-client-go. After we pin to the latest commit number of openwhisk-client-go, a lot of method calls have to be changed accordingly.
However, there is probably a API gateway regression in wskdeploy, since in the CreateAPI method of api.go,
_, _, err := deployer.Client.Apis.Insert(api, true) was changed to
_, _, err := deployer.Client.Apis.Insert(api, nil, true), in order to make sure the binary build passes.
We have to verify if the api gateway still works in wskdeploy and adding an integration would be a great option.
@lzbj Could you take a look? Thx. Please update your openwhisk-client-go to the latest.

@houshengbo take into account that there is a new api gateway implementation wsk api, the old wsk api-experimental would be sunset.

@houshengbo , so I'll add test code as you already submitted the fix right? sorry for late reply we were on labor's holiday, and the office resumed today.

@lzbj is there any status on this?

@mrutkows , I'll add test code for the api use case. As @csantanapr  said, currently the experimental api may sunset, we may also update the code as the latest implementation.

as the code that can build now, I would lower the pri to mid, please rise if not agree.

@mrutkows , when I try to fix this issue, I found there were 2  grammar in our spec, one is simple format, one is full grammar, but as our yaml parsers are predefined structures which is a reflection of our grammar structure, so I don't which grammar to support? could you help clarify this issue?

@lzbj we decided (together) to use the full grammar (for first pass) and open a new issue to subsequently support the simple grammar later.

The signature of the Insert() method is now correct in current build within ServiceDeployer.go


Revert per-config samples install directories

This PR reverts the changes made in #88 in which the install directories of the samples were modified to per-config install directories inside the bin folder.
Additionally, the MacOS CI job has been patched as it seems that the install directory of PoCL has changed (from /opt/homebrew/Cellar/pocl/6.0 to /opt/homebrew/Cellar/pocl/6.0_1) and thus the hard-coded vendors path used within the workflow was outdated (and triggering tests failures).

@bashbaug fyi: agreed with @MathiasMagnus to split the TODO work for SDK and Layers

@bashbaug  No further work is needed AFAIK


Add Bluesky for Danielle

Hi @djnavarro,
I'm working on adding a Bluesky integration for the R-Ladies bot and saw that you're also on Bluesky. Please let me know

if you agree to add your handle here as well so that the bot can use it to tag you when posting about your posts
if you're also OK to be featured in an R-Ladies starter pack

Thank you ☺

thanks @cosimameyer - yes I'm okay with the rladies bot tagging me on bluesky, and I'm okay being included on the rladies starter pack (not usually a fan of being listed in starter packs but rladies is an exception... much appreciated!)

Thank you so much! :)

Ref #97  - will be added to starter pack 🎉


Batch changes (and remove options[:every])

This removes the `every` option when initializing Filewatcher.

Though backwards incompatible, it's fairly simple to emulate the
previous behavior.

    filewatcher.watch do |changes|
      # to emulate every=true
      changes.each do |filename, event|
        # ...
      end

      # to emulate every=false
      filename, event = changes.first
      # ...
    end

The CLI option --every remains unchanged.

Oh, I see errors like:

expected [{}].empty? to return true, got false

I think it's easy to fix.
Let me know when there will be complicate fails.

Tests should work better after #116 (the second commit), so I recommend you to update (rebase) your branch.

Thanks for the review! I have a few questions, but I'll work on some of the comments you gave and push it up soon 😄

Hm it looks like there's a flaky test here. I had the same issue locally, but I didn't look into it much.
Interestingly as I was running it repeatedly, I got a slightly different error.
D, [2020-04-20T17:33:49.370980 #67025] DEBUG -- : Thread #70136262500420 processed = []
#<Thread:0x00007f93be1fa708@/path/to/filewatcher/spec/spec_helper.rb:135 run> terminated with exception (report_on_exception is true):
Traceback (most recent call last):
	9: from /path/to/filewatcher/spec/spec_helper.rb:135:in `block in thread_initialize'
	8: from /path/to/filewatcher/spec/spec_helper.rb:140:in `setup_filewatcher'
	7: from /path/to/filewatcher/lib/filewatcher.rb:42:in `watch'
	6: from /path/to/filewatcher/lib/filewatcher/cycles.rb:14:in `main_cycle'
	5: from /path/to/filewatcher/lib/filewatcher/cycles.rb:30:in `watching_cycle'
	4: from /path/to/filewatcher/lib/filewatcher.rb:111:in `filesystem_updated?'
	3: from /path/to/filewatcher/lib/filewatcher.rb:104:in `mtime_snapshot'
	2: from /path/to/filewatcher/lib/filewatcher.rb:104:in `each'
	1: from /path/to/filewatcher/lib/filewatcher.rb:105:in `block in mtime_snapshot'
/path/to/filewatcher/lib/filewatcher.rb:105:in `mtime': No such file or directory @ rb_file_s_mtime - /path/to/filewatcher/spec/tmp/tmp_file.txt (Errno::ENOENT)

Interestingly as I was running it repeatedly, I got a slightly different error.

Oh, thank you. I usually see fails like this (from your branch): https://github.com/filewatcher/filewatcher/pull/115/checks?check_run_id=603280959
I'm trying to improve the situation in #119, but… with macOS, JRuby, CLI, files, threads, etc — it's very hard!
Sorry about this. I'll notice about updates.

@zachahn hello! Can you please rebase the branch? #119 and many other improvements of specs and CI was merged into master.

@zachahn sorry, but there are conflicts again… CI should pass faster and more accurate! Please, update the PR if you have a chance. I can try to help if you want.

@AlexWayfer No worries! Rebased and pushed

Pretty nice PR, thank you. I'm waiting for your response about new debug method.

@AlexWayfer Updated! I opted to use changes.inspect, but you're right, there was no difference in the output

@zachahn I see a fail with Ruby 2.5: https://cirrus-ci.com/task/5304049320853504?command=test#L1175
And it seems syntax error for this version, not something phantom. So, can you please fix it?

Strange! The only thing I changed was that debugging thing, so I'm inclined to believe it's a flaky test. Did you try rerunning the test? (Here's a diff showing what I changed, but since I rebased I'm not sure how long this link will work https://github.com/filewatcher/filewatcher/compare/929c5da3..d9f8914c. And it looks like 929c5da3 passed for Ruby 2.5)
I see that the test expects one hash, but it received two hashes. I'm not sure if this is the best way, but perhaps the best way to proceed would be to update the test to merge all the hashes together with something like changes.reduce(:merge).
I won't have time to look at this for the next few days. I'd appreciate it if you have a chance to fix it! I think I checked the box that lets maintainers push onto this branch. But otherwise I'll take a look at it later this week.

Did you try rerunning the test?

No.
Now I've tried and it passes. Hm…

I see that the test expects one hash, but it received two hashes. I'm not sure if this is the best way, but perhaps the best way to proceed would be to update the test to merge all the hashes together with something like changes.reduce(:merge).

I've understood the reason: there were two Filewatcher's triggers instead of expected one. I think, it's maybe OK to do reduce(:merge), or even add a sleep. And… merge can silent other unusual errors. So, because there is one action, create of a file, I suggest to wait more time. Due to this was splitted into two hashes, increase the interval of Filewatcher instance for this test.

I won't have time to look at this for the next few days. I'd appreciate it if you have a chance to fix it! I think I checked the box that lets maintainers push onto this branch. But otherwise I'll take a look at it later this week.

OK, thank you for your work and messages. I've tried and pushed a commit to this PR, so let's see.

Now it looks correct and passing, thank you again for your contributions.

Thank you for taking a look and fixing it! Happy to contribute, it was a pleasure :)

We forgot to update the README…


Support token authentication against elastic database

For openshift with a built in elastic server. The pod collecting logs has to authenticate itself against the elastic database with the built in token on the pod

duplicate


No diagnostics in JSON

Might be similar to https://github.com/microsoft/vscode-languageserver-node/issues/1128

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.78.2 (also insiders)
OS Version: Windows/macOS

This problems exists from 1.68.0. in 1.67.0 everything seems to be fine.

Extension code to reproduce:

// most probably you want to register it to some command
const testContent = '{test: 5}'

vscode.workspace
    .openTextDocument({
        content: testContent,
        language: 'json',
    })
    .then(async doc => {
        await vscode.window.showTextDocument(doc)
    })

Run the code

Actual: Diagnostics are present
Expected: Both editors have diagnostics
Text changes doesn't produce diagnostics in these editors. Of course, after reload diagnostics will be there.
### Tasks

I can reproduce by running the code above 2 times.
The second document (uri untitled:Untitled-2) does not have any diagnostics.
Looking at the JON language server log, no diagnostics for untitled:Untitled-2 are pulled.
Tested with running from source, using the latest vscode-languageclient (8.2.0-next.1)


driver/ RTO-1000 HDEF bandwidth issue

Fixes #856
Changes proposed in this pull request:

Add a parameter controlling the high def mode bandwidth
Document the use of this in the example notebook
Add a simulated instrument and an initialisation test

@jenshnielsen @AdriaanRol

@WilliamHPNielsen this does indeed solve the unusability of the HD mode as we can now use full the proper bandwidth.
It does not address all of issue #856 as the resolution (when not using HD mode) is still quantized at a too low bit value.
The following snippet is my current workaround that also makes the non-HD mode usable.
This is tested and working on our setup (rto 1024 scope). I expect the rto 1044 to behave in the same way.
        # we must have this nesting, since the parameter high_definition_state
        # only exists if HD
        # if self.channel._parent.HD:
        #     if self.channel._parent.high_definition_state() == 'ON':
        #         dataformat = 'INT,16'
        #     else:
        #         dataformat = 'INT,8'
        # else:
        #     dataformat = 'INT,8'

        # Hack to always use the high definition data transfer
        dataformat = 'INT,16'

Other than that :+1:

@AdriaanRol, I asked you about this over in #856, but let's try again 🙂
Do you know what the internally used resolution is when the instrument is not in high definition mode? When writing the driver, I assumed it to be 8 bit, but you seem to suggest that it is higher than that. I'll also search the manual. We can of course use 16 bit ints for data transfer always, but it's sort of pointless if the data is really only 8 bit.

@WilliamHPNielsen sorry for the confusion.
I can not directly answer the question as I was unable to find this in the manual. However, by reading out the data assuming it is 16 bits, the blockyness of the data (as shown in the screenshots) goes away without switching to HD mode (as can also be seen by looking at the scope display).
As such my experimental observation suggests that even when not using HD mode the data is transferred in more than 8 bits. I can not exclude that it is lower than 16 bits but the protocol at least seems consistent with that. Note that I also get a quantitative agreement between the data I read out and the data I see on the display of the scope when using this workaround.
Does this help?

@AdriaanRol no problem. Below is the part of the manual I (think I) based my assumption on (page 460 in my version, 1332.9725.02 ─ 10, look under "Data and File Management"):

...but it's quite ambiguous, at least to me. Can you do an extra quick test to convince me: count the number of unique values in your trace acquired using non-high definition mode but exported as 16 bit integers. I agree that you basically already proved that it's more than 8 bit, but now I'm curious.
In any case, l'll upgrade the driver to always use 16 bit integers for data export.

@WilliamHPNielsen I don't think I fully understand the test you want me to do. My signal does not cover the entire range of possible values of the scope so I guess counting unique values would be pointless. Do you instead want me to look at the smallest difference in values or something like that?

@WilliamHPNielsen I just ran into another bug that should be quite trivial to fix.
On lines 432-327 of the driver the number of averages can be set. However the get_cmd does not work.
This is because of an extra space between ACQuire:COUNt-? I have added a hyphen to denote where the space is now. By removing this space the asking for the number of acquisitions actually works.
        self.add_parameter('num_acquisitions',
                           label='Number of single acquisitions',
                           get_cmd='ACQuire:COUNt ?',
                           set_cmd='ACQuire:COUNt {}',
                           vals=vals.Ints(1, 16777215),
                           get_parser=int)

@AdriaanRol, it sounds like you totally understood the test 🙂  It was just in case you had a recorded signal covering the entire range "lying around", you could quickly count unique values. But I guess the minimal difference should tell us the same thing. I will in any case return to this PR this afternoon and then also play a bit with trying to figure out the bit depth.
Re bug 2: thanks for catching, I'll make sure to delete the space.

@WilliamHPNielsen
We ran into quite some problems with the "arithmethics" of the RTO acquistion mode not working correctly if a single run has not been completed. The snippet below implements checking for progress and should resolve this issue.
I think this should be included in the .trace() method that acquires a trace with potentially an option to disable this if fast acquisiton is required.
    rto.ch2.arithmetics('AVERAGE')  # other options: 'ENVELOPE' and 'OFF'
    rto.ch2.trace.prepare_trace()
    rto.run_single()  # and perform a single run.

    # This snippet should be included in the get_trace method
    t0 = time.time()
    timeout = 60
    num_avg = int(rto.ask('ACQ:COUNT?'))
    curr_acq =0
    while curr_acq < num_avg:
        curr_acq = int(rto.ask('ACQ:CURR?'))
        t1 = time.time()
        dt = t1-t0
        # prints the progress in a friendly manner :)
        print('\rAt {}/{} averages, acquiring for {:.2f}s'.format(
            curr_acq, num_avg, dt), end='')
        if dt> timeout:
            raise TimeoutError('More than {}s expired'.format(timeout))

    y = rto.ch2.trace()


There is about 5 hours without data updates, and then the probram shut down.
Similar problem links have been closed but no solutions have been given.
https://github.com/EOSIO/eos/issues/3029
https://github.com/EOSIO/eos/issues/3071
124168 2018-08-11T17:14:37.592 thread-0   producer_plugin.cpp:330       on_incoming_block    ] Received block fe897dfb2ba2cbfd... #10126000 @ 2018-08       -08T19:42:26.000 signed by teamgreymass [trxs: 6, lib: 10125677, conf: 0, latency: 250331596 ms]
124169 2018-08-11T17:14:37.600 thread-0   net_plugin.cpp:2155           operator()           ] Peer eosbp.buildteam.io:8532 closed connection
124170 2018-08-11T17:14:37.601 thread-0   net_plugin.cpp:1977           operator()           ] connection failed to eosnode.fi:9888: Connection refus       ed
124171 2018-08-11T17:14:38.546 thread-0   net_plugin.cpp:2155           operator()           ] Peer eu-west-nl.eosamsterdam.net:9876 closed connectio       n
124172 2018-08-11T17:14:40.304 thread-0   net_plugin.cpp:2155           operator()           ] Peer eosapi.blockmatrix.network:13546 closed connectio       n
124173 2018-08-11T17:14:44.211 thread-0   net_plugin.cpp:2155           operator()           ] Peer eu1.eosdac.io:49876 closed connection
124174 2018-08-11T17:14:48.405 thread-0   net_plugin.cpp:1977           operator()           ] connection failed to p2p-1.eosnetwork.io:9876: Connect       ion timed out
124175 2018-08-11T17:14:59.420 thread-0   net_plugin.cpp:1977           operator()           ] connection failed to mainnet.eosarabia.org:3571: Opera       tion canceled
124176 2018-08-11T17:14:59.426 thread-0   net_plugin.cpp:1977           operator()           ] connection failed to mainnet.eosoasis.io:9876: Connect       ion refused
124177 2018-08-11T17:14:59.427 thread-0   net_plugin.cpp:1977           operator()           ] connection failed to mainnet.eos.ren:9376: Connection        refused
124178 2018-08-11T17:14:59.428 thread-0   net_plugin.cpp:1935           connect              ] host: <IP_ADDRESS> port: 9876
124179 2018-08-11T17:14:59.428 thread-0   net_plugin.cpp:1935           connect              ] host: <IP_ADDRESS> port: 49876
124180 2018-08-11T17:14:59.428 thread-0   net_plugin.cpp:1935           connect              ] host: <IP_ADDRESS> port: 9876
...
...
127886 2018-08-11T17:32:07.800 thread-0   net_plugin.cpp:1222           process_next_message ] e.to_detail_string(): 8 out_of_range_exception: Out of        Range
127887 read datastream of length 1 over by 31
127888     {"method":"read","len":1,"over":31}
127889     thread-0  datastream.cpp:6 throw_datastream_range_error
127890 error unpacking N2fc14static_variantIJN5eosio5chain13chain_id_typeEEEE
127891     {"type":"N2fc14static_variantIJN5eosio5chain13chain_id_typeEEEE"}
127892     thread-0  raw.hpp:616 unpack
127893 Error unpacking field chain_id
127894     {"field":"chain_id"}
127895     thread-0  raw.hpp:368 operator()
127896 error unpacking eosio::handshake_message
127897     {"type":"eosio::handshake_message"}
127898     thread-0  raw.hpp:616 unpack
127899 2018-08-11T17:32:07.800 thread-0   net_plugin.cpp:2153           operator()           ] Error reading message from seed2.greymass.com:9876: Ba       d file descriptor
127900 2018-08-11T17:32:26.068 thread-0   net_plugin.cpp:1949           operator()           ] Unable to resolve bp.eosmedi.com:9877: Host not found        (authoritative)
127901 2018-08-11T17:32:26.076 thread-0   net_plugin.cpp:1949           operator()           ] Unable to resolve eos-p2p.worbli.io:33981: Host not fo       und (authoritative)
127902 2018-08-11T17:32:26.077 thread-0   net_plugin.cpp:1977           operator()           ] connection failed to dns1-p2p.oraclechain.io:49876: Co       nnection refused
127903 2018-08-11T17:32:26.453 thread-0   net_plugin.cpp:1977           operator()           ] connection failed to br.eosrio.io:9876: Co
...
...
272893 2018-08-12T00:03:07.623 thread-0   net_plugin.cpp:1935           connect              ] host: peering.eosio.cr port: 1976
272894 2018-08-12T00:03:07.623 thread-0   net_plugin.cpp:1935           connect              ] host: peering.eosio.cr port: 5418
272895 2018-08-12T00:03:07.623 thread-0   net_plugin.cpp:1935           connect              ] host: peering1.mainnet.eosasia.one port: 80
272896 2018-08-12T00:03:07.623 thread-0   net_plugin.cpp:1935           connect              ] host: peering2.mainnet.eosasia.one port: 80
272897 2018-08-12T00:03:07.623 thread-0   net_plugin.cpp:1935           connect              ] host: pub0.eosys.io port: 6637
272898 2018-08-12T00:03:07.623 thread-0   net_plugin.cpp:1935           connect              ] host: pub1.eostheworld.io port: 9876
272899 2018-08-12T00:03:07.623 thread-0   net_plugin.cpp:1935           connect              ] host: pub1.eosys.io port: 6637
272900 2018-08-12T00:03:07.623 thread-0   net_plugin.cpp:1935           connect              ] host: pub2.eostheworld.io port: 9876
272901 2018-08-12T00:03:09.837 thread-0   net_plugin.cpp:1977           operator()           ] connection failed to <IP_ADDRESS>:49876: Connection r       efused
272902 2018-08-12T00:03:09.861 thread-0   net_plugin.cpp:1977           operator()           ] connection failed to boot.eostitan.com:9876: Operation        already in progress
272903 2018-08-12T00:03:09.885 thread-0   net_plugin.cpp:1977           operator()           ] connection failed to boot.eostitan.com:9876: Operation        canceled
272904 2018-08-12T00:03:09.903 thread-0   net_plugin.cpp:1977           operator()           ] connection failed to <IP_ADDRESS>:9876: Connection re       fused
272905 2018-08-12T00:03:09.957 thread-0   net_plugin.cpp:1977           operator()           ] connection failed to pub1.eosys.io:6637: Connection re       fused
272906 2018-08-12T00:03:09.978 thread-0   net_plugin.cpp:1977           operator()           ] connection failed to <IP_ADDRESS>:9876: Connection re       fused
272907 2018-08-12T00:03:10.044 thread-0   net_plugin.cpp:1977           operator()           ] connection failed to <IP_ADDRESS>:5556: Connection r       efused
272908 2018-08-12T00:03:10.086 thread-0   net_plugin.cpp:1977           operator()           ] connection failed to <IP_ADDRESS>:9876: Connection r       efused
272909 2018-08-12T00:03:10.101 thread-0   net_plugin.cpp:1977           operator()           ] connection failed to <IP_ADDRESS>:80: Connection refus       ed
272910 2018-08-12T00:03:10.116 thread-0   net_plugin.cpp:1977           operator()           ] connection failed to <IP_ADDRESS>:9876: Connection ref       used
272911 2018-08-12T00:03:10.141 thread-0   net_plugin.cpp:2155           operator()           ] Peer 807534da.eosnodeone.io:19872 closed connection
272912 2018-08-12T00:03:10.146 thread-0   net_plugin.cpp:1977           operator()           ] connection failed to <IP_ADDRESS>:9806: Connection re       fused
272913 2018-08-12T00:03:10.147 thread-0   net_plugin.cpp:1977           operator()           ] connection failed to <IP_ADDRESS>:19866: Connection r       efused
272914 2018-08-12T00:03:10.292 thread-0   net_plugin.cpp:2155           operator()           ] Peer api.eosuk.io:12000 closed connection
272915 2018-08-12T00:03:10.417 thread-0   net_plugin.cpp:2155           operator()           ] Peer <IP_ADDRESS>:19877 closed connection
272916 2018-08-12T00:03:10.500 thread-0   net_plugin.cpp:2155           operator()           ] Peer <IP_ADDRESS>:59876 closed connection

You have a great many peers which are completely dead, which is not helping diagnose the problem.  Remove all peers logged with "Host not found" and "Connection refused".
Typically the problem you're encountering is one of the ports you are connected to is the API port, not the net_plugin port.  You'll need to discover which host and port is speaking the wrong protocol and remove it.
If you're not synching at all, you should update your peer list to something more recent.  It's possible you had only one valid peer, and its connection limit has been reached, so you're not able to maintain a connection anymore.  The more valid peers you have, the better your chances of maintaining synchronization.

you don't need you connect to all the peers. 2-3 peers should be ok for sync up.

It stopped again last night and prompted replay required When I restarted it this morning.
2018-08-16T17:43:13.534 thread-0   net_plugin.cpp:2155           operator()           ] Peer mainnet.eosnairobi.io:9876 closed connection
2018-08-16T17:43:13.534 thread-0   net_plugin.cpp:2155           operator()           ] Peer p2p.eosio.cr:1976 closed connection
2018-08-16T17:43:13.574 thread-0   net_plugin.cpp:2155           operator()           ] Peer eos-bp.bitfinex.com:9876 closed connection
2018-08-16T17:43:13.577 thread-0   net_plugin.cpp:2155           operator()           ] Peer node1.eosnewyork.io:6987 closed connection
2018-08-16T17:43:13.588 thread-0   net_plugin.cpp:2155           operator()           ] Peer api.tokenika.io:9876 closed connection
2018-08-16T17:43:13.927 thread-0   net_plugin.cpp:2155           operator()           ] Peer bp.eosbeijing.one:8080 closed connection
2018-08-16T17:43:13.932 thread-0   net_plugin.cpp:2155           operator()           ] Peer cpt.eosio.africa:9876 closed connection
2018-08-16T17:43:13.932 thread-0   net_plugin.cpp:2155           operator()           ] Peer eos.nodepacific.com:9876 closed connection
2018-08-16T17:43:13.932 thread-0   net_plugin.cpp:2155           operator()           ] Peer seed2.eos42.io:9876 closed connection
2018-08-16T17:43:16.513 thread-0   net_plugin.cpp:2155           operator()           ] Peer p2p.eosdetroit.io:3018 closed connection

2018-08-17T00:35:05.058 thread-0   chain_plugin.cpp:271          plugin_initialize    ] initializing chain plugin
2018-08-17T00:35:05.071 thread-0   chain_plugin.cpp:580          plugin_initialize    ] 13 St13runtime_error: database dirty flag set
rethrow database dirty flag set:
    {"what":"database dirty flag set"}
    thread-0  chain_plugin.cpp:580 plugin_initialize
2018-08-17T00:35:05.072 thread-0   main.cpp:118                  main                 ] database dirty flag set (likely due to unclean shutdown): replay required
2018-08-17T00:36:09.289 thread-0   chain_plugin.cpp:271          plugin_initialize    ] initializing chain plugin
2018-08-17T00:36:09.290 thread-0   chain_plugin.cpp:580          plugin_initialize    ] 13 St13runtime_error: database dirty flag set
rethrow database dirty flag set:
    {"what":"database dirty flag set"}
    thread-0  chain_plugin.cpp:580 plugin_initialize
2018-08-17T00:36:09.290 thread-0   main.cpp:118                  main                 ] database dirty flag set (likely due to unclean shutdown): replay required

The peers in config.ini:
p2p-peer-address = <IP_ADDRESS>:9876
p2p-peer-address = <IP_ADDRESS>:9876
p2p-peer-address = <IP_ADDRESS>:19876
p2p-peer-address = <IP_ADDRESS>:9876
p2p-peer-address = 807534da.eosnodeone.io:19872
p2p-peer-address = anvil.eosblocksmith.io:9876
p2p-peer-address = api.eos.wiki:39876
p2p-peer-address = api.eosuk.io:12000
p2p-peer-address = api.tokenika.io:9876
p2p-peer-address = api1.eosmetal.io:19877
p2p-peer-address = api2.eostribe.io:9115
p2p-peer-address = api-full1.eoseoul.io:9876
p2p-peer-address = api-full2.eoseoul.io:9876
p2p-peer-address = bp.antpool.com:443
p2p-peer-address = bp.cryptolions.io:9876
p2p-peer-address = bp.eosbeijing.one:8080
p2p-peer-address = bp.eosmedi.com:9877
p2p-peer-address = bp.superone.io:57576
p2p-peer-address = cpt.eosio.africa:9876
p2p-peer-address = dc1.eosemerge.io:9876
p2p-peer-address = eos.genesis-mining.com:19876
p2p-peer-address = eos.genesis-mining.com:19877
p2p-peer-address = eos.nodepacific.com:9876
p2p-peer-address = eos.staked.us:9870
p2p-peer-address = eosapi.blockmatrix.network:13546
p2p-peer-address = eosboot.chainrift.com:9876
p2p-peer-address = eos-bp.bitfinex.com:9876
p2p-peer-address = eosbp.buildteam.io:8532
p2p-peer-address = eosbp.kuna.io:9876
p2p-peer-address = eosbp-0.atticlab.net:9876
p2p-peer-address = eosdapp.oneeos.org:9000
p2p-peer-address = eos-mainnet-p2p.activeeos.com:9876
p2p-peer-address = eos-seed-de.privex.io:9876
p2p-peer-address = eu.eosdac.io:49876
p2p-peer-address = fn001.eossv.org:443
p2p-peer-address = fullnode.eoslaomao.com:443
p2p-peer-address = m.jeda.one:3322
p2p-peer-address = mainnet.eosamsterdam.net:9876
p2p-peer-address = mainnet.eoscalgary.io:5222
p2p-peer-address = mainnet.eoseco.com:10010
p2p-peer-address = mainnet.eosnairobi.io:9876
p2p-peer-address = mainnet.libertyblock.io:9800
p2p-peer-address = mars.fnp2p.eosbixin.com:443
p2p-peer-address = node.eosflare.io:1883
p2p-peer-address = node.eosio.lt:9878
p2p-peer-address = node.eosmeso.io:9876
p2p-peer-address = node.eosvenezuela.io:9875
p2p-peer-address = node1.blockgenesys.com:9876
p2p-peer-address = node1.bp.eosindex.io:9876
p2p-peer-address = node1.eoscannon.io:59876
p2p-peer-address = node1.eosnewyork.io:6987
p2p-peer-address = node1.eosvibes.io:9876
p2p-peer-address = node1.starteos.io:9876
p2p-peer-address = node1.zbeos.com:9876
p2p-peer-address = node2.liquideos.com:9876
p2p-peer-address = node2.starteos.io:9876
p2p-peer-address = node2.zbeos.com:9876
p2p-peer-address = node869-mainnet.eosauthority.com:9393
p2p-peer-address = p2p.bitmars.one:8080
p2p-peer-address = p2p.bp.fish:9786
p2p-peer-address = p2p.eos.bitspace.no:9876
p2p-peer-address = p2p.eos.blckchnd.com:19876
p2p-peer-address = p2p.eosargentina.io:5222
p2p-peer-address = p2p.eosdetroit.io:3018
p2p-peer-address = p2p.eosgermany.online:9876
p2p-peer-address = p2p.eosio.cr:1976
p2p-peer-address = p2p.eosio.cr:5418
p2p-peer-address = p2p.eossocal.io:9999
p2p-peer-address = p2p.eossweden.se:9876
p2p-peer-address = p2p.genereos.io:9876
p2p-peer-address = p2p.hkeos.com:9876
p2p-peer-address = p2p.libertyblock.io:9800
p2p-peer-address = p2p.mainnet.eospace.io:88
p2p-peer-address = p2p.meet.one:9876
p2p-peer-address = p2p.one.eosdublin.io:9876
p2p-peer-address = p2p.proxy1a.sheos.org:5556
p2p-peer-address = p2p2.eossweden.eu:9966
p2p-peer-address = peer.eosgeneva.io:9876
p2p-peer-address = peer.eosn.io:9876
p2p-peer-address = peer.franceos.fr:19876
p2p-peer-address = peer.main.alohaeos.com:9876
p2p-peer-address = peer.oraclechain.io:19876
p2p-peer-address = peer1.eosphere.io:9876
p2p-peer-address = peer2.eoshuobipool.com:18181
p2p-peer-address = peer2.eosphere.io:9876
p2p-peer-address = peer2.franceos.fr:19876
p2p-peer-address = peer2.mainnet.helloeos.com.cn:80
p2p-peer-address = peering.mainnet.eoscanada.com:9876
p2p-peer-address = peering1.mainnet.eosasia.one:80
p2p-peer-address = pub0.eosys.io:6637
p2p-peer-address = publicnode.cypherglass.com:9876
p2p-peer-address = seed.acroeos.one:9876
p2p-peer-address = seed.eoseco.com:10021
p2p-peer-address = seed1.eos42.io:9876
p2p-peer-address = seed1.greymass.com:9876
p2p-peer-address = seed2.eos42.io:9876
p2p-peer-address = seed2.greymass.com:9876
p2p-peer-address = v.rito.su:9876

What is the error reported immediately before nodeos terminates?  Connection closures do not cause nodeos to exit.

There is no error message，so I didn't know why It shut down.
What I can do is just restart it or restart it from backup files.

Without some error message, we have no way to diagnose why it shut down.
Check your system settings around RAM usage.    Mainnet currently has 43.69 GiB of reserved RAM.  Not all of it is in use, but a good deal of it is.  A system or container with less than 8 GB available is unlikely to be able to run a mainnet-synched nodeos.

The memory of my server is 8GB. Is this not enough?

Generally, how high the configuration of the main network node needs to be synchronized. After one year, after two years, how much configuration is needed? I need to prepare.

Ok, I will continue to observe, maybe It still will shut down.
The memory of my server is 8GB. Is this not enough?
Generally, what the configuration of the server needs to  synchronize main network node？
Then, after one year, two years, what configuration will needed? I need to know to prepare.

A mainnet node without history_plugin today has a virtual size of over 6 GB.  Actual RAM used is a little under 2 GB.  With the history_plugin, it is considerably bigger.  In theory 8 GB is sufficient without history_plugin.  In practice, due to interactions with how boost shared_memory tries to reserve memory and interactions with how virtual machines manage memory, it may not be.
It's difficult to say what the required minimum will be in one or two years.  If EOS.IO is widely adopted and heavily used, you would expect 90% of the RAM available to be used.  The producers have enabled RAM expansion in the system contract, which is now making available 69.90GiB.  This number rises slowly every day.  How much of the available memory is used will depend on the adoption rate, which is unpredictable.

Today, one of my nodes stopped again, but today I kept the system log.
The log shows that it's memory occupancy rate is too high and the system killed it. And also need to replay when i restart it. I can only start from the backup.
Can this 90% memory use rate be reduced by some way or Some configuration, like 80% or 60% and the rest in virtual memory. This not only avoids this abnormal stop, but also reduces the memory requirements on the server.
...
Aug 25 15:03:59  xxx-xxx-xxx-xxx kernel: [2781980.456483] Out of memory: Kill process 10614 (nodeos) score 963 or sacrifice child
Aug 25 15:03:59 xxx-xxx-xxx-xxx kernel: [2781980.458006] Killed process 10614 (nodeos) total-vm:83923900kB, anon-rss:15795692kB, file-rss:0kB
...

Use the mongo_db_plugin instead of the history_plugin.  History plugin stores everything in memory, and with a filter of "*", this is enormous, and will only get worse.  You will have to write your dapps to query mongo rather than nodeos RPC for history, but there are libraries available that make that easy.

I've tried to synchronize the Mongo database, but it was so was that far from keeping up with the master node. So, I gave up that way.
I know that the way filter-on * will be memory problems, so I just add filtering to my account instead of filtering * now.
I have made a script on another server with 8 gigabytes of memory. The script stops for backing up and starts nodeos server again once a day . The nodeos server has been running steadily for more than a week.
So , I feel that the daily restarting process can avoid nodeos takes up too much memory and being killed by linux. I don't know if I need to restart every 12 hours or even 1 hours in feture.

@quarksgluons   You need set this parameter "chain-state-db-size-mb = 16384".


Set up ARM64 Linux Runner

We need a ARM64 Linux runner because using QEMU or Docker on macOS is slowing us down.
Ping @acalcutt

I messed with this a little on my side. I made one of those free t4g instances in my account. The free instance is t4g.small and has 2 cores and 2GB memory. At first I was concerned this wouldn't be enough memory, but in my testing the build worked fine there on the apt-packages got installed.

I was wondering how this runner would be set up, would it use something docker like this some we can easily change OS/RUNNER_VERSION
https://github.com/shivammathur/setup-php/wiki/Dockerized-self-hosted-runner-on-Linux

Or is the instance throw away enough we would just do the actions runner directly on this machine

We do that for macOS now as well. It is not ideal, but also not a big problem as long as we don't store any senstive data on these machines and we make sure we can set them up easily again. This is why actions need to be triggered manually for first time contributors.
Good to know your test worked, I will set one up today!

It is added! Ubuntu 20.04.
It is easy to set up another one later.

First issue, It needs git.

Ah thanks. ;-)

I looked at my instance and I seem to have git. I also had trouble with apt-get.

My bad, accidentaly used Amazon Linux.

You must have fixed it, it gets further now. It looks like it needs 'libjpeg-dev'

I will add it to the list:
https://github.com/maplibre/ci-runners/blob/arm64-linux-runner/ubuntu.yaml

I think when doing a Debug release like node-ci does right now actually makes this run out of memory. I tried to change the release type to test that but the last job is stuck.
Testing on my arm64 instance I can build a "release" version, but the debug release gets stuck. I tried adding some swap space to get around it, but the build crashed instead of getting stuck.

So, my issue after I added swap was space. With this I was able to get the debug build to actually complete on this t4g.small instance
Starting with t4g.small with 15GB storage
sudo fallocate -l 2G /swapfile
sudo chmod 600 /swapfile
sudo mkswap /swapfile
sudo swapon /swapfile

git clone --recurse-submodules -j8 https://github.com/maplibre/maplibre-gl-native.git
cd maplibre-gl-native
ccache --clear --set-config cache_dir=~/.ccache
cmake . -B build -G Ninja -DCMAKE_CXX_COMPILER_LAUNCHER=ccache -DCMAKE_C_COMPILER=gcc-10 -DCMAKE_CXX_COMPILER=g++-10 -DCMAKE_BUILD_TYPE=Debug
cmake --build build -j $(nproc 2>/dev/null || sysctl -n hw.ncpu 2>/dev/null)

This build successfully with about 1G disk space left
A non-debug release works with 10G disk space and without the added swap. I'm not sure this workflow really needs to be a Debug release (though it may give more information in the ci)

Sounds like the t4g.small instance might be a bit too limited for our purposes. I enabled 2GB of swap, let's see!

Seems like it ran through (and pretty fast as well)! 🙂
They have 30GB storage available, but I can increase it a bit if needed, does not make sense to penny pinch there I think.

I had changed the ci to always run a Release version in, so it would probably work without the swap now.
I wasn't quite ready to merge https://github.com/maplibre/maplibre-gl-native/pull/873 since I planned on doing the node-release workflow too. I'll make a new PR for that.


BIP-1: Beam Schema Options

Introduce the concept of Options in Beam Schema’s to add extra context to fields and schemas. In contrast to the current Beam metadata that is present in a FieldType, options would be added to fields, logical types and schemas. The schema convertors (ex. Avro, Proto, …) can add options/annotations/decorators that were in the original schema to the Beam schema with these options. These options, that add contextual metadata, can be used in the pipeline for specific transformations or augment the end schema in the target output.
Imported from Jira BEAM-9275. Original Jira may contain additional context.
Reported by: alexvanboxel.

The following subtask(s) are associated with this issue: #20023

Given there's just one sub-task left let's go ahead and close this.


reason: uniform named "normalUvMatrix" not found

12-14 14:00:27.876 29560 29560 E Filament: in ssize_t filament::UniformInterfaceBlock::getUniformOffset(const char *, size_t) const:120
12-14 14:00:27.876 29560 29560 E Filament: reason: uniform named "baseColorIndex" not found
12-14 14:00:27.876 29560 29560 E Filament:
12-14 14:00:27.876 29560 29560 E Filament: in ssize_t filament::UniformInterfaceBlock::getUniformOffset(const char *, size_t) const:120
12-14 14:00:27.876 29560 29560 E Filament: reason: uniform named "normalIndex" not found
12-14 14:00:27.876 29560 29560 E Filament:
12-14 14:00:27.876 29560 29560 E Filament: in ssize_t filament::UniformInterfaceBlock::getUniformOffset(const char *, size_t) const:120
12-14 14:00:27.876 29560 29560 E Filament: reason: uniform named "metallicRoughnessIndex" not found
12-14 14:00:27.876 29560 29560 E Filament:
12-14 14:00:27.876 29560 29560 E Filament: in ssize_t filament::UniformInterfaceBlock::getUniformOffset(const char *, size_t) const:120
12-14 14:00:27.876 29560 29560 E Filament: reason: uniform named "aoIndex" not found
12-14 14:00:27.876 29560 29560 E Filament:
12-14 14:00:27.876 29560 29560 E Filament: in ssize_t filament::UniformInterfaceBlock::getUniformOffset(const char *, size_t) const:120
12-14 14:00:27.876 29560 29560 E Filament: reason: uniform named "emissiveIndex" not found
12-14 14:00:27.876 29560 29560 E Filament:
12-14 14:00:27.876 29560 29560 W Filament: Parent material does not have double-sided capability.
12-14 14:00:27.876 29560 29560 E Filament: in ssize_t filament::UniformInterfaceBlock::getUniformOffset(const char *, size_t) const:120
12-14 14:00:27.876 29560 29560 E Filament: reason: uniform named "clearCoatIndex" not found
12-14 14:00:27.876 29560 29560 E Filament:
12-14 14:00:27.876 29560 29560 E Filament: in ssize_t filament::UniformInterfaceBlock::getUniformOffset(const char *, size_t) const:120
12-14 14:00:27.876 29560 29560 E Filament: reason: uniform named "clearCoatRoughnessIndex" not found
12-14 14:00:27.876 29560 29560 E Filament:
12-14 14:00:27.876 29560 29560 E Filament: in ssize_t filament::UniformInterfaceBlock::getUniformOffset(const char *, size_t) const:120
12-14 14:00:27.876 29560 29560 E Filament: reason: uniform named "clearCoatNormalIndex" not found
12-14 14:00:27.876 29560 29560 E Filament:
12-14 14:00:27.876 29560 29560 E Filament: in ssize_t filament::UniformInterfaceBlock::getUniformOffset(const char *, size_t) const:120
12-14 14:00:27.876 29560 29560 E Filament: reason: uniform named "baseColorUvMatrix" not found
12-14 14:00:27.876 29560 29560 E Filament:
12-14 14:00:27.876 29560 29560 E Filament: in ssize_t filament::UniformInterfaceBlock::getUniformOffset(const char *, size_t) const:120
12-14 14:00:27.876 29560 29560 E Filament: reason: uniform named "metallicRoughnessUvMatrix" not found
12-14 14:00:27.876 29560 29560 E Filament:
12-14 14:00:27.876 29560 29560 E Filament: in ssize_t filament::UniformInterfaceBlock::getUniformOffset(const char *, size_t) const:120
12-14 14:00:27.876 29560 29560 E Filament: reason: uniform named "normalUvMatrix" not found
12-14 14:00:27.876 29560 29560 E Filament:
12-14 14:00:27.876 29560 29560 E Filament: in ssize_t filament::UniformInterfaceBlock::getUniformOffset(const char *, size_t) const:120
12-14 14:00:27.876 29560 29560 E Filament: reason: uniform named "occlusionUvMatrix" not found
12-14 14:00:27.876 29560 29560 E Filament:
12-14 14:00:27.876 29560 29560 E Filament: in ssize_t filament::UniformInterfaceBlock::getUniformOffset(const char *, size_t) const:120
12-14 14:00:27.876 29560 29560 E Filament: reason: uniform named "emissiveUvMatrix" not found
12-14 14:00:27.876 29560 29560 E Filament:
12-14 14:00:27.876 29560 29560 E Filament: in ssize_t filament::UniformInterfaceBlock::getUniformOffset(const char *, size_t) const:120
12-14 14:00:27.876 29560 29560 E Filament: reason: uniform named "clearCoatUvMatrix" not found
12-14 14:00:27.876 29560 29560 E Filament:
12-14 14:00:27.876 29560 29560 E Filament: in ssize_t filament::UniformInterfaceBlock::getUniformOffset(const char *, size_t) const:120
12-14 14:00:27.876 29560 29560 E Filament: reason: uniform named "clearCoatRoughnessUvMatrix" not found
12-14 14:00:27.876 29560 29560 E Filament:
12-14 14:00:27.876 29560 29560 E Filament: in ssize_t filament::UniformInterfaceBlock::getUniformOffset(const char *, size_t) const:120
12-14 14:00:27.876 29560 29560 E Filament: reason: uniform named "clearCoatNormalUvMatrix" not found
12-14 14:00:27.876 29560 29560 E Filament:
12-14 14:00:27.876 29560 29560 E Filament: in const SamplerInterfaceBlock::SamplerInfo *filament::SamplerInterfaceBlock::getSamplerInfo(const char *) const:110
12-14 14:00:27.876 29560 29560 E Filament: reason: sampler named "normalMap" not found
12-14 14:00:27.876 29560 29560 E Filament:
backtrace:
12-14 14:18:18.884  7393  7393 F DEBUG   :       #00 pc<PHONE_NUMBER>045684  /system/priv-app/MiuiCamera/MiuiCamera.apk!libfilament-jni.so (offset 0x733f000) (filament::MaterialInstance::setParameter(char const*, filament::Texture const*, filament::TextureSampler const&)+36) (BuildId: 51b0336f96aec8d77e7ebb48fe169b91ef5c2cf0)

When does this happen and with which version of Filament please?

And is there more to the logs?

 Could be a sceneform or app bug.

This is a very old version of Filament, not much we can do about it but it looks like something is trying to use the wrong material. Could be a sceneform or app bug.

I want to know emissiveUvMatrix/clearCoatUvMatrix/clearCoatNormalUvMatrix...  where are they?   in Filament or sceneform ?

There are defined in the materials of Filament's glTF loader. Something is trying to render a glTF asset without the proper material.


Enabling quick-fixes and its telemetry

This PR changes the documentSelector to use as string, this is a requisite for consuming code actions, it also adds the associated telemetry.
(A follow up PR will be created to bump the version of vscode-webhint)

@antross, @mliao95 friendly ping.

I'll leave this for @mliao95 to sign off on, but some other thoughts to consider:

For anything reporting sub-data like hintName is it consistently formatted across all our telemetry so queries to compare hover/ignore/disable/fix actions can be consistent? E.g., do we also need to update our existing hover telemetry?
Do we want to try to capture anything about specific browsers that are ignored? If so, this probably requires some more work on the webhint side.

@mliao95 this should be ready for next review round

GO FURTHER 😜


problem in RDP

Hi
i runned this keylogger on my server.
but it cannot log all keys that i have typed unless i type very slowly.
i connected to my server by remote desktop.

I don't have such problems. Maybe your server is fully loaded or your connection may be slow.


Destructors are not run when calling exit

We should probably avoid calling exit and instead throw an exception, catch it in main and then exit. This allows destructors to execute. This may be important because helpful error messages may be hidden by unhelpful error messages about "leaking" objects. See https://github.com/graphicsfuzz/get-image-egl/commit/063eb3b144f3581651929674ce40a3e072c09f8e
We should also include the above commit!

Sounds good!
It may be a bit more subtle here as the EGL / GLFW contexts are as isolated as possible in their own module.


⚠ Spryr has degraded performance

In d86eafa, Spryr (https://spryr.com) experienced degraded performance:

HTTP code: 200
Response time: 3584 ms

Resolved: Spryr performance has improved in 46f8363 after 15 minutes.


RUF009 not covered by documentation

I am not sure which release introduced RUF009, but since ruff==0.0.262 it triggers additional detections in my codebase. I believe the rule is currently undocumented, i.e. is not listed on https://beta.ruff.rs/docs/rules/#ruff-specific-rules-ruf, which makes it hard to determine whether the detections are false positives or not.

I build docs locally and there is a description of rules in such docs. So it looks like a bug in the docs deployment process. Same like in #4089


Debugging into Matplotlib Widget functions with Spyder

Problem Description
Let' s take an example of widget from Matplotlib website:
https://matplotlib.org/gallery/widgets/buttons.html#sphx-glr-gallery-widgets-buttons-py
When we click on a button (on the GUI), some operations are done and a new trace is created. I have a  more complex program but it works the same way, and I want to read the variables inside the def of the widget (eg. I want to read the value of ydata inside 'def next(self, event)', for the example I provided). How to do it?
The problem is that the breakpoint will be reached only when I will press a button on the plot. And this event happens when all the program has already been read and the debugger is automatically closed at the end of the program...
What steps will reproduce the problem?
Take the program in the example and try to put a breakpoint at lines 28 or 29 (ydata = np.sin(2np.pifreqs[i]*t or l.set_ydata(ydata)). Then try to debug and have the program stop at the breakpoint. If you manage that I would very much know how you did!
What is the expected output? What do you see instead?
The debugger should stop at the breakpoint, but it does not.
Package Versions

Spyder: 3.2.8
Python: 3.6.5
Qt: 5.9.4
PyQt: 5.9.2
Operating System: Ubuntu 17.10

It took me a while, but I figured it out. These are my modifications to the MPL example you posted
import numpy as np
import matplotlib  ## <--
matplotlib.use('TkAgg')  ## <--
import matplotlib.pyplot as plt
from matplotlib.widgets import Button

freqs = np.arange(2, 20, 3)

fig, ax = plt.subplots()
plt.subplots_adjust(bottom=0.2)
t = np.arange(0.0, 1.0, 0.001)
s = np.sin(2*np.pi*freqs[0]*t)
l, = plt.plot(t, s, lw=2)

class Index(object):
    ind = 0

    def next(self, event):
        self.ind += 1
        i = self.ind % len(freqs)
        ydata = np.sin(2*np.pi*freqs[i]*t)
        import pdb; pdb.set_trace()  ## <--
        l.set_ydata(ydata)
        plt.draw()

    def prev(self, event):
        self.ind -= 1
        i = self.ind % len(freqs)
        ydata = np.sin(2*np.pi*freqs[i]*t)
        l.set_ydata(ydata)
        plt.draw()

callback = Index()
axprev = plt.axes([0.7, 0.05, 0.1, 0.075])
axnext = plt.axes([0.81, 0.05, 0.1, 0.075])
bnext = Button(axnext, 'Next')
bnext.on_clicked(callback.next)
bprev = Button(axprev, 'Previous')
bprev.on_clicked(callback.prev)

plt.show(block=True)

Please see the lines that have this inline comment ## <--. Those were the ones I changed.
In Spyder you need to also deactivate Matplotlib support, by going to
Tools > Preferences > IPython console > Graphics

and deselecting the option called Activate support.
Finally, after running your code with F5 and pressing the Next button in your plot, you'll enter our debugger and will be able to use the Variable Explorer to inspect ydata.

import pdb; pdb.set_trace() is a (not so known) way to generate a breakpoint in code, as opposed to setting them with our graphicals facilities.


Make it possible to customize the issuer claim and the access token expiration time

You guys are doing an amazing job and that is one of the most expected Spring project.
That is a simple feature request and please just let me know if you need more information or if the team needs some help to build the server.
Thanks

Hello. I'm not developing in the project, but I've seen your question about the access token expiration time. From what I see, this can be already configured via:
.tokenSettings(t -> {
t.accessTokenTimeToLive(Duration.ofHours(1));
})
I don't see indeed something about the issuer yet.

Hi @Ispil, its currently possible to configure the expiration token and the issuer claim, but there is no effect yet, they still using the default hard coded values

@lhmoraes @lspil Configuring the issuer is coming in #143 and the token expiration configuration will take effect in #145. Closing this as a duplicate.


[Issue]:  CTEST - Failures

Problem Description
Failure 1
ctest -R dataloader_multithread_gpu -VV
UpdateCTestConfiguration  from :/home/kiriti/develop/rocal-kiriti/build/DartConfiguration.tcl
Parse Config file:/home/kiriti/develop/rocal-kiriti/build/DartConfiguration.tcl
UpdateCTestConfiguration  from :/home/kiriti/develop/rocal-kiriti/build/DartConfiguration.tcl
Parse Config file:/home/kiriti/develop/rocal-kiriti/build/DartConfiguration.tcl
Test project /home/kiriti/develop/rocal-kiriti/build
Constructing a list of tests
Done constructing a list of tests
Updating test list for fixtures
Added 0 tests to meet fixture requirements
Checking test dependency graph...
Checking test dependency graph end
test 6
    Start 6: dataloader_multithread_gpu

6: Test command: /home/kiriti/develop/rocal-kiriti/build/tests/cpp_api/dataloader_multithread/dataloader_multithread "/opt/rocm/share/rocal/test/data/images/AMD-tinyDataSet" "1"
6: Test timeout computed to be: 1500
6: Number of GPUs: 1
6: Running on GPU: 0
6: shard_id: 0
6: Running on GPU: 0
6: shard_id: 1
6: OK: OpenVX using GPU device - 0: AMD Radeon PRO W6800 [gfx1030] with 60 CUs on PCI bus 0b:00.0
6: OK: loaded 115 kernels from libvx_rpp.so
6: OK: OpenVX using GPU device - 0: AMD Radeon PRO W6800 [gfx1030] with 60 CUs on PCI bus 0b:00.0
6: OK: loaded 115 kernels from libvx_rpp.so
6: Remaining images 128
6: Augmented copies count 1
6: output width 224 output height 3584 color planes 3 n 1
6: Remaining images 128
6: Augmented copies count 1
6: output width 224 output height 3584 color planes 3 n 1
1/1 Test #6: dataloader_multithread_gpu .......***Exception: SegFault  0.75 sec

0% tests passed, 1 tests failed out of 1

Total Test time (real) =   0.75 sec

The following tests FAILED:
	  6 - dataloader_multithread_gpu (SEGFAULT)
Errors while running CTest

Failure 2
ctest -R video_tests -VV
UpdateCTestConfiguration  from :/home/kiriti/develop/rocal-kiriti/build/DartConfiguration.tcl
Parse Config file:/home/kiriti/develop/rocal-kiriti/build/DartConfiguration.tcl
UpdateCTestConfiguration  from :/home/kiriti/develop/rocal-kiriti/build/DartConfiguration.tcl
Parse Config file:/home/kiriti/develop/rocal-kiriti/build/DartConfiguration.tcl
Test project /home/kiriti/develop/rocal-kiriti/build
Constructing a list of tests
Done constructing a list of tests
Updating test list for fixtures
Added 0 tests to meet fixture requirements
Checking test dependency graph...
Checking test dependency graph end
test 14
    Start 14: video_tests

14: Test command: /usr/bin/ctest "--build-and-test" "/home/kiriti/develop/rocal-kiriti/rocAL/tests/cpp_api/video_tests" "/home/kiriti/develop/rocal-kiriti/build/tests/cpp_api/video_tests" "--build-generator" "Unix Makefiles" "--test-command" "video_tests" "/opt/rocm/share/rocal/test/data/videos/AMD_driving_virtual_20.mp4"
14: Test timeout computed to be: 1500
14: Internal cmake changing into directory: /home/kiriti/develop/rocal-kiriti/build/tests/cpp_api/video_tests
14: ======== CMake output     ======
14: -- video_tests INFO:ROCM_PATH Set -- /opt/rocm
14: -- OpenCV Found -- Version-4.6.X Supported
14: Configuring done
14: Generating done
14: Build files have been written to: /home/kiriti/develop/rocal-kiriti/build/tests/cpp_api/video_tests
14: ======== End CMake output ======
14: Change Dir: /home/kiriti/develop/rocal-kiriti/build/tests/cpp_api/video_tests
14:
14: Run Clean Command:/usr/bin/make clean
14:
14: Run Build Command(s):/usr/bin/make && [ 50%] Building CXX object CMakeFiles/video_tests.dir/video_tests.cpp.o
14: [100%] Linking CXX executable video_tests
14: [100%] Built target video_tests
14:
14: Running test command: "/home/kiriti/develop/rocal-kiriti/build/tests/cpp_api/video_tests/video_tests" "/opt/rocm/share/rocal/test/data/videos/AMD_driving_virtual_20.mp4"
14: Test command failed: /home/kiriti/develop/rocal-kiriti/build/tests/cpp_api/video_tests/video_tests
14: Batch size : 1
14: Sequence length : 1
14: Frame step : 1
14: Frame stride : 1
14: OK: OpenVX using GPU device - 0: AMD Radeon PRO W6800 [gfx1030] with 60 CUs on PCI bus 0b:00.0
14: OK: loaded 115 kernels from libvx_rpp.so
14:
14: VIDEO READER
14:
14: Remaining images 601
14: Augmented copies count 1
14: output width 2048 output height 1024 color planes 3
14: Load     time 1515
14: Decode   time 83345196
14: Process  time 1118322
14: Transfer time 83298583
14: Processed 601 images/frames
14: Total Elapsed Time 83 sec 361666 us
14:
14: *** Exception executing: Segmentation fault
1/1 Test #14: video_tests ......................***Failed   87.56 sec

0% tests passed, 1 tests failed out of 1

Total Test time (real) =  87.56 sec

The following tests FAILED:
	 14 - video_tests (Failed)
Errors while running CTest

Operating System
Ubuntu 20/22
CPU
ALL
GPU
AMD Radeon Pro W6800
ROCm Version
ROCm 6.1.0
ROCm Component
No response
Steps to Reproduce
No response
(Optional for Linux users) Output of /opt/rocm/bin/rocminfo --support
No response
Additional Information
No response

Fixed with TOT
 ctest
Test project /root/rocal-test
      Start  1: rocAL_basic_test_cpu
 1/14 Test  #1: rocAL_basic_test_cpu .....................   Passed   20.10 sec
      Start  2: rocAL_basic_test_gpu
 2/14 Test  #2: rocAL_basic_test_gpu .....................   Passed   17.97 sec
      Start  3: rocAL_basic_test_gray
 3/14 Test  #3: rocAL_basic_test_gray ....................   Passed    1.89 sec
      Start  4: rocAL_basic_test_rgb
 4/14 Test  #4: rocAL_basic_test_rgb .....................   Passed   18.52 sec
      Start  5: rocAL_dataloader_mt_cpu
 5/14 Test  #5: rocAL_dataloader_mt_cpu ..................   Passed    3.41 sec
      Start  6: rocAL_dataloader_mt_gpu
 6/14 Test  #6: rocAL_dataloader_mt_gpu ..................   Passed    1.27 sec
      Start  7: rocAL_performance_tests_cpu
 7/14 Test  #7: rocAL_performance_tests_cpu ..............   Passed    3.14 sec
      Start  8: rocAL_performance_tests_gpu
 8/14 Test  #8: rocAL_performance_tests_gpu ..............   Passed    0.98 sec
      Start  9: rocAL_performance_tests_with_depth_cpu
 9/14 Test  #9: rocAL_performance_tests_with_depth_cpu ...   Passed    3.40 sec
      Start 10: rocAL_performance_tests_with_depth_gpu
10/14 Test #10: rocAL_performance_tests_with_depth_gpu ...   Passed    1.83 sec
      Start 11: rocAL_unittests_cpu
11/14 Test #11: rocAL_unittests_cpu ......................   Passed   17.04 sec
      Start 12: rocAL_unittests_gpu
12/14 Test #12: rocAL_unittests_gpu ......................   Passed   15.14 sec
      Start 13: rocAL_unittests_gray
13/14 Test #13: rocAL_unittests_gray .....................   Passed    6.24 sec
      Start 14: rocAL_video_unittests
14/14 Test #14: rocAL_video_unittests ....................   Passed   88.47 sec

100% tests passed, 0 tests failed out of 14

Total Test time (real) = 199.42 sec


Fix JSON operator syntax typos in docs

Found a couple typos in the docs for dynamic/2.

:green_heart: :blue_heart: :purple_heart: :yellow_heart: :heart:


send back Widget class name information in the widget rebuild/repaint count events

This PR:

adds tests to validate that we're collecting Widget class names in the widget kernel transformer
send back Widget class name information in the widget rebuild/repaint count events

List which issues are fixed by this PR. You must list at least one issue.

https://github.com/flutter/devtools/issues/3143

If you had to change anything in the flutter/tests repo, include a link to the migration guide as per the breaking change policy.
Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I signed the CLA.
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making or feature I am adding, or Hixie said the PR is test-exempt.
[x] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

I encoded the names in a new 'newLocationsNames' field in the returned event, but there might be other ways to encode the information.
The location is, line, and column are encoded in a List<int> in the 'newLocations' field, so would be challenging to include the name info (a String) there.


Missing functions in the pyhelics capi

I ran the following:
import subprocess
import shlex

names = subprocess.check_output(shlex.split("nm helics/install/lib/libhelics.3.2.1.dylib")).splitlines()

names = {str(name).strip().split()[-1].split(".")[0].strip("_").strip("'") for name in names if name.strip().split()[-1].startswith(b"_helics")}

import helics as h

print("These functions are missing in pyhelics {} with HELICS {}".format(h.__version__, h.helicsGetVersion()))

for name in sorted([n for n in names]):
    try:
        getattr(h, name)
    except:
        print(name)

to get this:
These functions are missing in pyhelics v3.2.1 with HELICS 3.2.1 (2022-06-16)
helicsBooleanToBytes
helicsComplexObjectToBytes
helicsComplexVectorToBytes
helicsDataBufferClone
helicsDataBufferConvertToType
helicsDataBufferIsValid
helicsDataBufferStringSize
helicsDataBufferToChar
helicsDataBufferToComplexObject
helicsDataBufferToComplexVector
helicsDataBufferToInteger
helicsDataBufferToRawString
helicsDataBufferToString
helicsDataBufferToTime
helicsDataBufferToVector
helicsDataBufferVectorSize
helicsEndpointSendMessageZeroCopy
helicsIntegerToBytes
helicsNamedPointToBytes
helicsRawStringToBytes

These functions need to be implemented.

Some of these are due to functions being renamed (Int and Bool were expanded to Integer and Boolean).  helicsDataBufferToInt is now helicsDataBufferToInteger). https://github.com/GMLC-TDC/HELICS/pull/2368 changed the function names.


error 401 unauthorized

Guys I need some help I can't create instance it appears unauthorized 401 error I'm using postman.

env.zip

Hi @jrCleber  I'm having the exact same issue. What am I doing wrong?

It should be fixed now.
Em ter., 12 de set. de 2023 às 16:53, abuhamsa @.***>
escreveu:

Hi @jrCleber https://github.com/jrCleber I'm having the exact same
issue. What am I doing wrong?
—
Reply to this email directly, view it on GitHub
https://github.com/code-chat-br/whatsapp-api/issues/69#issuecomment-1716332173,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BAG55XXS6EH5VPW5I6OIP4LX2C4TPANCNFSM6AAAAAA4EV2RQU
.
You are receiving this because you authored the thread.Message ID:
@.***>

--
http://www.jpiaget.com.br Rodrigo Damasceno de Carvalho
Supervisor de Tecnologia da Informação
(11) 4367-8303 / (11) 99124-9874
@.***

Checks if the credential to create the instance you are passing to the request header is the same as the one defined in the env.yml file.

Yes, it works!
Em qua., 13 de set. de 2023 às 08:12, Cleber Wilson <
@.***> escreveu:

Checks if the credential to create the instance you are passing to the
request header is the same as the one defined in the env.yml file.
—
Reply to this email directly, view it on GitHub
https://github.com/code-chat-br/whatsapp-api/issues/69#issuecomment-1717425299,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BAG55XT6AQ3YLVYCKE3P6RTX2GIJPANCNFSM6AAAAAA4EV2RQU
.
You are receiving this because you authored the thread.Message ID:
@.***>

--
http://www.jpiaget.com.br Rodrigo Damasceno de Carvalho
Supervisor de Tecnologia da Informação
(11) 4367-8303 / (11) 99124-9874
@.***


Added styles to buttons and added hovering effect

Added styles to buttons and added hovering effect to the buttons in the web page

@Its-Aman-Yadav Please label this PR under GSSoC

Thank you @SuhainaFathimaM


AttributeError: module 'clip' has no attribute 'load'

I've been working with CLIP for a few weeks now, but for some reason my code stopped working.
This is the code:
import torch
import clip
device = "cuda" if torch.cuda.is_available() else "cpu"
og_model, preprocess = clip.load('ViT-B/32', device)
then the error I get is the following

:
I tried testing the same code in a sagemaker notebook on aws and it worked there so I'm starting to think it might be because I'm working on a Mac? please let me know if there's something I can do to get it to work.

I think you need to install 'clip-by-openai', not 'clip':
pip3 install clip-by-openai

I think you need to install 'clip-by-openai', not 'clip': pip3 install clip-by-openai

Please note that clip-by-openai is not managed/endorsed by OpenAI.
I realize the OP might've installed clip from PyPI, which they shouldn't -- if that's the case, uninstall it by pip uninstall clip and follow the instructions in README.md to install CLIP properly.

Use the latest stable version by installing openai-clip:
pip install openai-clip

do you have a local directory named clip or a file named clip.py in the same directory?

wow! thanks!! you figure out what I am looking for!

@davitpapikyan thx!

I had some problems, but they worked out.
Firstly
pip3 install git+https://github.com/openai/CLIP.git
Looking in indexes: http://mirrors.aliyun.com/pypi/simple
Collecting git+https://github.com/openai/CLIP.git
  Cloning https://github.com/openai/CLIP.git to /tmp/pip-req-build-_f2vfa36
  Running command git clone --filter=blob:none --quiet https://github.com/openai/CLIP.git /tmp/pip-req-build-_f2vfa36
  fatal: unable to access 'https://github.com/openai/CLIP.git/': Failed to connect to github.com port 443: Connection timed out
  error: subprocess-exited-with-error

  × git clone --filter=blob:none --quiet https://github.com/openai/CLIP.git /tmp/pip-req-build-_f2vfa36 did not run successfully.
  │ exit code: 128
  ╰─> See above for output.

  note: This error originates from a subprocess, and is likely not a problem with pip.
error: subprocess-exited-with-error

× git clone --filter=blob:none --quiet https://github.com/openai/CLIP.git /tmp/pip-req-build-_f2vfa36 did not run successfully.
│ exit code: 128
╰─> See above for output.

then i upgrade the pip,pip install --upgrade pipthen it works.
pip3 install git+https://github.com/openai/CLIP.git --user
Secondly
python clip.py
Traceback (most recent call last):
  File "clip.py", line 38, in <module>
    clip_embeding = ClipEmbeding()
  File "clip.py", line 10, in __init__
    self.model, self.processor = clip.load("/root/clip/model/ViT-B-32.pt", device=self.device)
AttributeError: module 'clip' has no attribute 'load'

so, i tried the above method, pip install openai-clip, but it does not work.
then, i rename my python file name and the floder name, it works.

Previous file directory

/root/clip/:
code model

/root/clip/code:
clip.py  clip.ipynb  data  __pycache__  zore-shoot.py

/root/clip/code/data:
cifar-100-python  cifar-100-python.tar.gz

/root/clip/code/data/cifar-100-python:
file.txt~  meta  test  train

/root/clip/code/__pycache__:
clip.cpython-38.pyc  clip.cpython-39.pyc

/root/clip/model:
ViT-B-32.pt

Modified file directory

/root/clip-file/:
code  model

/root/clip-file/code:
clip-code.py  clip.ipynb  data  __pycache__  zore-shoot.py

/root/clip-file/code/data:
cifar-100-python  cifar-100-python.tar.gz

/root/clip-file/code/data/cifar-100-python:
file.txt~  meta  test  train

/root/clip-file/code/__pycache__:
clip.cpython-38.pyc  clip.cpython-39.pyc

/root/clip-file/model:
ViT-B-32.pt

Ending
hope these details can help you.


Enhancement: Have Display Precision Also Affect State

Is there a way to have the Display Precision affect the actual state of a sensor, instead of just the lovelace display? Lovelace will display the set precision such as "120 mL" but the actual state is still "120.0 mL".

What is logged in BabyBuddy? Data should be straight from there.


65c02 rev1: pulled signals

Pull-Up:
BE
RDY (done)
NMI (done)
IRQ (done)
RES? (through reset circuit?)

basically duplicate of #4.
RESET is held up by a 4k7 next to the reset button.


tox: use allowlist_externals option instead of whitelist_externals

whitelist_externals was removed and deprecated in tox v 4.0.0.rc4 We should use allowlist_externals instead.
https://tox.wiki/en/latest/changelog.html#deprecations-and-removals-4-0-0rc4

Thanks!


Contention in io_buffer_select when IOSQE_BUFFER_SELECT and IOSQE_ASYNC are used together

I'm trying out io_uring and am testing different ways of submitting requests. My test is a simple webserver-like application that accepts multiple sockets, and then alternatively reads and writes each socket. Everything is running on a single application thread within a single ring.
In general, using IOSQE_ASYNC does not seem to make too much sense for network reads because it often does strictly more work than using the default path. On the other hand, for a single threaded server, much CPU time will be spent inside of the kernel TCP stack, so using IOSQE_ASYNC could help by freeing the application thread for other work while the kernel threads do all the heavy lifting.
Looking into the performance with Linux 5.19.11 I noticed that the flamegraph shows lots of time spent in allocating buffers from the provided buffers:

Zooming in on io_read:

This is with max 128 concurrent reads. It seems in that scenario the amount of concurrent wqe_workers gets quite high (maybe even 1 per requests?), so if there's a mutex in the buffer selection path that cannot work well if many or all of the sockets are readable at the same time.
Is this contention expected and should be documented?

I would not recommend using provided buffers with IOSQE_ASYNC, as you have noticed they need to serialize with the ring mutex. This is generally not a concern, but it does certainly become one if you have a lot of io-wq activity due to marking the SQEs async. You'll be better off setting aside some threads in userspace, each with a ring, and using provided buffers with those.
In general, IOSQE_ASYNC isn't very efficient and should be avoided for most use cases.

Thanks for the quick answer. I agree, there are good alternatives.


Export Data to OneDrive or GDrive ?

Tutorial URL: https://developers.sap.com/tutorials/cp-ui5-ms-graph-export-drive.html
Regarding interface with OneDrive,
Does it work with GDrive or how could you set up a GDrive (spreadsheet) connector ?
Thank you
Amaury

Hi @AmauryVanEspen,
good question. The tutorial only focusses on the Microsoft SDK, so you cannot simply replace the OneDrive part with GDrive. Having said that, the flow for GDrive probably follows the same principles. First, you need to acquire a token and then you can use this token to upload a file to GDrive.


Reset transformer attributes between files

Codecov Report

Merging #258 (7880d43) into main (1a41975) will decrease coverage by 8.36%.
The diff coverage is 33.33%.

@@            Coverage Diff             @@
##             main     #258      +/-   ##
==========================================
- Coverage   97.00%   88.63%   -8.37%
==========================================
  Files          35       35
  Lines        2172     2174       +2
==========================================
- Hits         2107     1927     -180
- Misses         65      247     +182

Impacted Files
Coverage Δ

robotidy/transformers/AlignTestCases.py
99.15% <ø> (-0.01%)
:arrow_down:

robotidy/transformers/ReplaceBreakContinue.py
47.50% <33.33%> (-47.10%)
:arrow_down:

robotidy/transformers/InlineIf.py
26.66% <0.00%> (-71.12%)
:arrow_down:

robotidy/transformers/ReplaceReturns.py
44.18% <0.00%> (-51.17%)
:arrow_down:

robotidy/transformers/AddMissingEnd.py
75.75% <0.00%> (-18.19%)
:arrow_down:

robotidy/utils.py
89.09% <0.00%> (-8.54%)
:arrow_down:

robotidy/transformers/NormalizeSeparators.py
91.50% <0.00%> (-8.50%)
:arrow_down:

Continue to review full report at Codecov.

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


old branch throw an error after take the publish folder content to IIS

the old branch work like a charm locally in visual studio, but when try to publish the generated app everything goes as expected without throwing any error or exception, but when copy the content of publish folder to IIS and run the app the message shown to me that some error occured without any details
the content of message is:
Error.
An error occurred while processing your request.

how can I track the error, where things goes wrong, or any further details, is it IIS problem or should I have special configuration in IIS, even I tried to publish Test ASP Core Web Application to IIS everything goes as expected and the app hosted successfully
Any Help would be appreciated

Do you have Node 6+ installed as well?

I have node version 7.10, I catch the issue, I run dotnet command in generated publish folder with main dll file as argument when the app run I discovered from error shown in cmd that Client folder didn't moved to publish folder I copied it and all things goes as expected


Fix/transitions

A CSS transition was added to the height property of the iframe in #81 so that when transaction notifications were added and removed the height change would transition nicely. The problem was that when the height changed on the iframe for the onboarding modal, the transition made it look like the modal appears from the bottom of the screen the first time the modal is opened. This PR makes sure that the transition only applies to changing the height of the iframe when the transaction notifications are visible so that the modal appears as it previously did.


Typo in "Default interface methods"

"Default interface methods affects". I think it should be "affect" instead of "affects"

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

ID: c36588d0-6bdf-1740-220c-10b20bb88730
Version Independent ID: 587ed47f-f532-e018-9b0d-6ee76afd20e4
Content: What's new in C# 8.0 - C# Guide
Content Source: docs/csharp/whats-new/csharp-8.md
Product: dotnet-csharp
Technology: csharp-whats-new
GitHub Login: @BillWagner
Microsoft Alias: wiwagn

Hi @moerwald,
Thanks for posting this issue. I added the up-for-grabs label on this issue, and hope that you'd be willing to send a pull request our way. Feel free to propose the change with the "Edit" button on the article - https://github.com/dotnet/docs/edit/master/docs/csharp/whats-new/csharp-8.md. Otherwise, we will try to get to this change sometime later.

This issue was resolved by #18228

Resolved by #18228


Make it possible to wait until service is started

Summary
Our io.quarkus.test.bootstrap.BaseService#restart don't wait for started application, which is useful for Quarkus CLI tests that expects application to be unavailable right after restart, however I need to wait for restarted app when it crashed and I don't want to do it manually.
Please check the relevant options

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Dependency update
[x] Refactoring
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] This change requires a documentation update
[ ] This change requires execution against OCP (use run tests phrase in comment)

Checklist:

[ ] Example scenarios has been updated / added
[x] Methods and classes used in PR scenarios are meaningful
[x] Commits are well encapsulated and follow the best practices

Ouch! This validation failure is not related, we experienced it (or brought it in) in https://github.com/quarkus-qe/quarkus-test-framework/pull/831
/cc @fedinskiy

Could not transfer artifact io.quarkus.qe:quarkus-test-core:pom:1.3.1.Beta21-SNAPSHOT from/to gradle-official-repository (https://repo.gradle.org/gradle/libs-releases-local/
This is just super strange, why Gradle?

@michalvavrik

Why gradle: it is the last repo in the list. We also didn't find the artifact in jboss-maven-central-proxy and google-maven-central.
If you've applied existing workarounds (full path to parent pom and new helm version), then the only option I see is to add building/installing of the framework before running validation. Or to create a bug for Quarkus guys, if you could make a sane reproducer

ping @mjurc


remove useless inspect command

fixes #161

Codecov Report

Merging #163 (b81c6ba) into master (b7447dc) will increase coverage by 0.65%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #163      +/-   ##
==========================================
+ Coverage   80.07%   80.72%   +0.65%
==========================================
  Files          57       56       -1
  Lines       16003    15835     -168
==========================================
- Hits        12814    12783      -31
+ Misses       3189     3052     -137

Impacted Files
Coverage Δ

pallets/balances/src/lib.rs
78.85% <0.00%> (+0.11%)
:arrow_up:

Continue to review full report at Codecov.

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

No strong reason, just think we don't need this custom command, to view a block or extrinsic we can use app.deeper.network or deepscan


feat: [PLATO-411] Tracking events

What will change?

Added Segment tracking events
Fixed an issue where the xray frame would nest anchors in anchors causing a HTML error

Ticket: https://contentful.atlassian.net/browse/PLATO-411
Tracking plan: https://contentful.atlassian.net/wiki/spaces/PROD/pages/4138500311/Templates+-+Segment+tracking#Tracking-plan
Testing steps

Make sure analytics cookies are accepted and AdBlockers are disabled (confirm there's no errors being thrown in the browser's console)
Make sure all events mentioned in the tracking plan, are correctly implemented and fired accordingly. This can be checked with the Segment Debugger, available in our staging environment. Credentials can be found on 1 password
We are aware that addition page events are fired when URL parameters change (this happens for the preview and xray mode). This is an accepted side effect.

QA in progress 👀


Add port to server configuration

I have also a recommendation. Try to add to account-sample.py a server port option.
And in pybot.py the following line of code to createbot:
'port' : self.account['port'],

sir, i have chosen my mini project for college as  game development using mine craft. But i am facing lot of difficulties in how to run the server in a website or having a front end log in page etc. Is there any solution for me. Please help me sir.........


Fixing issue #557

Fixing issue #557.
Notes on the changes:
I've created a new file to include classes that are going to be used as dummy inside the tests. I've done this because I needed to use different namespaces, and to be able to do that, I needed to include a file called Namespaced.php.
In MethodDefinitionPass.php at line 86, I've created an array to hold the TypeHints to be used in the method definition. The problem with this is that the code is not maintainable neither reusable. I  researched in the project for similar arrays, and I found at least three uses of those in the following files:

MockConfigurationBuilder at line 9
KeywordPatch at line 66.

I suggest to put those arrays in a functions.php file or any other file that can make this code more reusable and maintainable.

Any chance of this getting merged? I just ran into this myself.

Apologies! Adding new commits to a PR doesn't send any notifications, so I didn't know @TiagoMaiaL had addressed my comments...

Thank you!

No problems! Thanks for getting this merged.


LITE-30249 Product exporting plugin fails with TypeError

While exporting older Products which has no default localization were failing with TypeError. The fix adds more checks to avoid exception in such case

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


ci(integration): Drop common-instancetypes deployment

What this PR does / why we need it:
Drop the flag for common-instancetypes deployment that was removed previously.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:

None

/approve
/lgtm


build: vendored dependencies clash with golang.org/x/net

Build problem caused by exposing the vendor/ directory, related to https://github.com/Azure/azure-sdk-for-go/issues/4265 (but different in impact).
Problem
ce88814cecd48039e38c31553e7499883ae95d8c committed and exposed vendored dependencies. Inclusion of golang.org/x/net/trace is problematic, since it can be included only once.
Exposing it through vendor/ causes the following runtime error:
sh>./build/bin/cli
panic: /debug/requests is already registered. You may have two independent copies of golang.org/x/net/trace in your binary, trying to maintain separate state. This may involve a vendored copy of golang.org/x/net/trace.

goroutine 1 [running]:
golang.org/x/net/trace.init.0()
        /root/safehaven3/server/syntropy3/src/go/src/golang.org/x/net/trace/trace.go:123 +0x197

Please note that this happens at runtime, i.e. the problem is deceptive in that the build runs cleanly.
Requested fix
Please would you consider not vendoring golang.org/x/net/trace, due to the above described runtime problem.

Fixed in 393cbce7a5ef4e77ad9b316bae69cfc04f7e0eb3, tested to work. Thank you.


Change batch loader option to batch: {key: [SymboldOrCallable], loader: SymboldOrCallable, default: nil}

Changed in release 5.0


add tests for OSBS class

First test written in 9b0cc19.

:+1:

Still missing:

create_prod_build()
create_prod_without_koji_build()
create_simple_build()
create_build()
create_build_from_buildrequest()
wait_for_build_to_finish()

Tests status:

[x] create_prod_build()

[x] create_prod_without_koji_build()

[x] create_simple_build()

[x] create_build()
(in test_create_build_with_deprecated_params and test_create_prod_build_missing_args)

[ ] create_build_from_buildrequest()

[x] wait_for_build_to_finish()

Coverage has been improved.


Add a parameter to choose group timings displayed in report. Close #2924.

By default, keep previous behaviour: group timings displayed are
cumulated response times. This can be replaced in config to display
group duration instead.
Close #2924.

minor typo :)

I fixed the typo.
When you merge à pull request can you perform a rebase prior to merging ?

git rebase -i HEAD~2
change last commit to f (for fix-up)
git push origin feature-groupTimingsSwitch2 -f

magico


Add GitHub documentation link

This will also double as an update to the last commit in the repository.
Most developers will see that it's from 2016 and dismiss it as something unmaintained, luckily for me I had a look at the issues and saw that version 4 is coming.

Awesome, thanks!


TypeScript Vue Plugin (Volar) breaks VSCode

TypeScript Vue Plugin (Volar) breaks VSCode:

breaks syntax highlighting:
breaks autocompletion for imports, object fields and etc.

My Environment:

app & software
version

vscode
1.72.0

volar
1.0.0

Duplicate of #1946

Please try v1.0.1.

#1946
Updated, but this doesn't work either.

Can you reproduce this problem in https://github.com/johnsoncodehk/volar-starter?

Sorry, what do you mean?

Could you try clone https://github.com/johnsoncodehk/volar-starter and than install depends, and see is there some way to reproduce the problem you mentioned in a certain repo file.

Yeah, everything works in .vue files.
https://user-images.githubusercontent.com/87207122/194722139-290a28b1-6298-4f38-aaf3-a2be459c7093.mov

But everything breaks with, for example, .ts files:
https://user-images.githubusercontent.com/87207122/194722163-763fbdb7-1827-4168-aa7e-407fd4db12c3.mov

@MaximFedarau thanks, will check it later, you can try use takerover mode instead of TS plugin for now.

Please try v1.0.2.

YES.
1.0.2 solves the issue!

1.0.2 solved the issue!
I only don't use Take Over mode because it makes Go To Definition stop working in monorepos with Project References (https://github.com/johnsoncodehk/volar/issues/1344), else I would use it without problems.


fix(#19): use sh -c to invoke aliased command

As aliased command could consist in &&, ||, & or other terminal specific combination.
I did not chose to rewrite a (buggy) parser and prefer to rely on sh -c "command" style invoke.

Checks won't be ok because it does not build for Windows targets.


mco client needs cert, key and ca to issue commands in case of middleware_ssl

If we set middleware_ssl to true, mco client can't ping because of those errors:
mco ping
error 2014/03/11 13:14:22: activemq.rb:306:in `ssl_parameters' Failed to set full SSL verified mode: RuntimeError: cert, key and ca has to be supplied for verified SSL mode
The ping application failed to run, use -v for full error backtrace details: Could not connect to ActiveMQ Server: cert, key and ca has to be supplied for verified SSL mode
Fix:
move cert and key configuration from server to common class:
mcollective::server::setting { "plugin.activemq.pool.${name}.ssl.cert and key
mcollective::common::setting { "plugin.activemq.pool.${name}.ssl.cert and key

i'm pretty, and sure, this is already fixed.


mixed precision

Hi,
What happened to pulp-nn-mixed directory? I want to use a mixed-prec. quantized network if possible. Thanks.
Best regards,
Beran

Hi @berab,
We temporary closed the repository for an internal review. You should now find public access. Let us know if you run into any issues.
Best regards,
Nazareno


docs: 📚 show property documentation in storybook

Description

get/set properties are missing the documentation in Storybook
Rationale

Documentation is part of the webcomponents.json but it is not shown in storybook. Instead the documentation field is empty.

when generating the webcomponents.json properties the description field must be flagged properly

This is now visible in Storybook, see attached screenshot.


getusermedia stream callback contains error

trying to get started with webrtc,
in getusermedia i get this error
09-09 12:40:58.527  1312  2578 I ReactNativeJS: 'getUserMedia success', { [TypeError: undefined is not an object (evaluating 'WebRTCModule.getUserMedia')]

my code
webrtc.getUserMedia({
    audio: true,
    video: {
      mandatory: {
        minWidth: 640, // Provide your own width, height and frame rate here
        minHeight: 360,
        minFrameRate: 30,
      },
      facingMode: (true ? "user" : "environment"),
    }
  }, function (stream) {
    console.log('getUserMedia success', stream);
    // callback(stream);
  });

Please show the entire snippet. What is the “webrtc “ object?
Also, anything else in the logs?

@saghul
var webRTC = require('react-native-webrtc');
no that's all the log i get

i have this error for all of webrtc methods WebRTC like peerconnection
TypeError: undefined is not an object (evaluating 'WebRTCModule.peerConnectionInit')

@moeinrahimi JS variable names are case sensitive.

@brunsy
unfortunately that is not the case

Have you tried running a clean and making sure the package is up to date.
Also have you tried using import?
import {
	RTCPeerConnection,
	RTCDataChannel,
	RTCIceCandidate,
	RTCSessionDescription,
	MediaStreamEvent,
	MediaStreamTrack,
	MediaStream,
	getUserMedia
} from 'react-native-webrtc';

my react-native-webrtc version is 1.67.1 and i tried using import instead of require the result is same as before .

Well then i'm not really sure what to say, not having the issues and can't reproduce.
It is as if you don't have the package installed.

well this is not working on a physical device, it is working fine on android emulator


Morph

Once we're using the BioNano mol viewer (https://github.com/Autodesk/molecular-design-applications/issues/53), implement morph on the results page (switching between pdbs).

Works without animation in this PR: https://github.com/Autodesk/molecular-design-applications/pull/125


POC of HMR working in app for changes in packages/react

Based on Approach 2 from this discussion.
This could of course be extended to other libraries besides @medplum/react.
One caveat is that it currently isn't possible to specify a different tsconfig file besides the default tsconfig.json in Vite which is kind of wild. If we actually wanted to pursue this, we'd need to use or build a plugin like the ones in this discussion or get creative in our package.json scripts to swap in/rename the appropriate tsconfig file for dev vs building.

Finalized here: https://github.com/medplum/medplum/pull/3229


Bug with the production queue and building repaired (on a conquered city ?)

The city view is shown even if there're things on the queue if the last item was a repair. It often occur when it's on a newly conquered city (maybe it's only a coincidence)

It's this line https://github.com/Azurency/CQUI_Community-Edition/blob/0ffe1f5ff3c72936d24a4eb2a82265e2e3ad8004/Assets/UI/Panels/productionpanel.lua#L3468 the city is already in the function parameters, why getting it that way ? Removing this line purely resolved the bug.
Removing this line should not lead to any other bug since MoveQueueIndex is always called with a city parameter.


Solution

Link

Need to update condition in docker-ci job. This step shouldn't skip

Changed. Link


Add link to relevant types

Please add a link to relevant types, like Virtualize component documentation page.
Also add information about how to control the height of the component (to get the scrollbar instead of a long list of items as default).

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

ID: 0f4ab8b4-4d2e-9e1b-793e-dbb17f6d694d
Version Independent ID: 26ed2425-63ec-e206-edcb-e51f17edb844
Content: ASP.NET Core Blazor component virtualization
Content Source: aspnetcore/blazor/components/virtualization.md
Product: aspnet-core
Technology: aspnetcore-blazor
GitHub Login: @guardrex
Microsoft Alias: riande

Thanks @maloo for the feedback. I'm buried in work ⛏⛰ for the next couple of weeks then out for an extended ⛄ holiday vacation 🎁, but I've added this to my Post-holiday Triage issue list and will take a look when I return. Sorry for the delay, but I must get some long-standing priorities resolved before leaving, so only serious bug fixes will be addressed before I get some (much needed 😅) rest. I assure you that this won't get lost.

No hurry, I solved my issue. But in general the type docs are in really bad shape. But there are lots of really good articles and examples on most types hidden in the docs. I think all of docs would benefit from an auto generated cross reference between these type doc pages and the articles/examples.

We don't have a facility such as that. We have to manually create cross-links to the API docs. Also note that such links can't be created until AFTER GA (5.0 just released a couple of weeks ago) because they don't activate preview API docs for us to link. The framework is in churn before GA as they work on it, so API docs only get the final, approved, released API coverage when the framework reaches GA. I tend to return to docs after GA and get the types cross-linked in the weeks and months following release.

I understand, but as a user that sounds like a technical issue (that can/should be resolved). As a user you just want the cross ref, doesn't matter how docs are generated ;)

you just want the cross ref

That's the crux of it tho ..... there is nothing to cross ref ... nothing that we can link to. When the framework is in preview, the best one can do is go into the framework source code, issues, and PRs themselves on the product unit repo at ...
https://github.com/dotnet/aspnetcore/
They can't make API docs out of something that's under active development by the product unit engineers. It changes constantly. Our docs flow downstream from that point. After they've settled on everything and worked out the final bugs and bits, then the API docs go live (at GA) and then we can cross-link the API. Until that point tho, there's nothing to cross-link.
What is a bit troubling is that we have no way to set up a pre-API doc cross-link when writing preview docs. If we make API doc links today during preview, they create broken links that we don't want to trouble readers (or ourselves) with. They'll click ... the link will break (404) ... we'll get issues opened every hour of every day during preview if we do that. We'll be flooded with issues! 😨
If you want to provide feedback about that aspect ... an XREF API doc link that doesn't break during preview ... you can provide that feedback, but that's not something we take care of here. We just work on ASP.NET Core doc content here. Provide the feedback at ...
https://github.com/MicrosoftDocs/feedback/issues

btw ... are you aware of the API Browser? ....
https://docs.microsoft.com/en-us/dotnet/api/
At least with that, you can get the API during the period while we're updating docs post GA.

@maloo ... I'm back from vacation now.

On the API docs cross-links. I'll see if I can address that right now to close this out. This issue will close automatically when the PR goes in.
On "control the height of the component," I've marked that on the UE tracking issue for this topic, and I'll address that with all of the updates to this topic that I make at that time.

@maloo ... I'm back from vacation now.

On the API docs cross-links. I'll see if I can address that right now to close this out. This issue will close automatically when the PR goes in.
On "control the height of the component," I've marked that on the UE tracking issue for this topic, and I'll address that with all of the updates to this topic that I make at that time.