text:
More backports to lwaftr-snabbvmx

#547 backport: Let out-ipv6-* counters also count internally generated ICMPv6 packets.

Run tests manually. Tests passed.
DIR       obj/testlog
TEST      core.timer
TEST      core.counter
TEST      core.lib
TEST      core.main
TEST      core.packet
TEST      core.app
TEST      core.memory
TEST      core.shm
TEST      core.link
TEST      core.histogram
TEST      apps.intel.intel_app
TEST      apps.intel.intel1g
SKIPPED   testlog/apps.intel.intel1g
TEST      apps.vhost.vhost_user
SKIPPED   testlog/apps.vhost.vhost_user
TEST      apps.ipv6.nd_light
TEST      apps.test.synth
TEST      apps.test.match
TEST      apps.virtio_net.virtio_net
SKIPPED   testlog/apps.virtio_net.virtio_net
TEST      apps.lwaftr.nh_fwd
TEST      apps.lwaftr.binding_table
TEST      apps.lwaftr.ctable_wrapper
TEST      apps.lwaftr.dump
TEST      apps.lwaftr.lwdebug
TEST      apps.lwaftr.ndp
TEST      apps.lwaftr.fragmentv4_test
TEST      apps.lwaftr.fragmentv4_hardened
TEST      apps.lwaftr.V4V6
TEST      apps.lwaftr.conf
TEST      apps.lwaftr.fragmentv6_hardened
TEST      apps.lwaftr.rangemap
TEST      apps.lwaftr.channel
TEST      apps.lwaftr.podhashmap
TEST      apps.lwaftr.arp
TEST      apps.rate_limiter.rate_limiter
TEST      apps.bridge.mac_table
TEST      apps.packet_filter.pcap_filter
TEST      apps.tap.tap
SKIPPED   testlog/apps.tap.tap
TEST      apps.vlan.vlan
TEST      apps.socket.unix
TEST      apps.socket.raw
TEST      apps.keyed_ipv6_tunnel.tunnel
TEST      lib.pmu
SKIPPED   testlog/lib.pmu
TEST      lib.ctable
TEST      lib.hash.murmur
TEST      lib.protocol.ipv6
TEST      lib.protocol.datagram
TEST      lib.protocol.tcp
TEST      lib.protocol.ipv4
TEST      lib.traceprof.traceprof
TEST      lib.ipc.shmem.shmem
TEST      lib.hardware.pci
TEST      lib.checksum
TEST      lib.ipsec.aes_128_gcm
TEST      lib.ipsec.esp
TEST      lib.numa
TEST      program.snabbnfv.neutron2snabb.neutron2snabb_schema
TEST      program.snabbnfv.neutron2snabb.neutron2snabb
TEST      program.snabbnfv.nfvconfig
TEST      selftest.sh
TEST      apps/solarflare/selftest.sh
SKIPPED   testlog/apps.solarflare.selftest.sh
TEST      apps/tap/selftest.sh
TEST      lib/watchdog/selftest.sh
TEST      program/lwaftr/tests/soaktest/selftest.sh
TEST      program/lwaftr/tests/end-to-end/selftest.sh
TEST      program/snabbnfv/selftest.sh
TEST      program/snabbnfv/neutron2snabb/selftest.sh
TEST      program/snabbvmx/tests/selftest.sh
TEST      program/snabbvmx/tests/end-to-end/selftest.sh
TEST      program/snabbvmx/tests/nexthop/selftest.sh
TEST      program/packetblaster/selftest.sh

authors: dpino teknico

repo: Igalia/snabb


text:
Is this project dead?

Despite everyone is busy, I don't see replied on new thread(s). I am trying to set a background color to label
0,215,79,41 but it show red and when I close open it's show the same color.
Does this many  time, nothing work. I am seeing that close (3 top button in right) is hiding behind  the top panel.
Listview show the scrollbar which I didn't find the way to fix.
Is this project dead or I am missing something here.

@SaitDev  ok, got it.

@SaitDev @IgnaceMaes  Is there anyone currently handling the open PRs and updating the Nuget packages? There are some great community provided features there but not sure if anyone is able to push them into master and update the nuget packages.

@brinehart He is busy and will not replied, I have opened 9 issues here, if he have time he certainly closed it. I see his linkedin profile 1-2 months ago and it's look like he is doing some kind of work (maybe mobile).

Im not maintainer of the project, i cant push nor public nuget package

source: gharchive/issue

authors: SaitDev anirudhagupta anirugu brinehart

repo: IgnaceMaes/MaterialSkin

license: mit

license_type: permissive

license_source: bigquery


text:
samp-server.exe is not shut down correctly

#include <a_samp>
#include <PawnPlus>

main() {}

When typing exit on console or calling SendRconCommand("exit");, the result is:

If I click on Debug, the result is:
The thread 0x... has exited with code 0 (0x0).
The thread 0x... has exited with code 3 (0x3).
The thread 0x... has exited with code 3 (0x3).
The program '[5928] samp-server.exe' has exited with code 3 (0x3).

I use Windows 7 Ultimate (SP1).

Hello, I am aware of the issue, which probably comes from one of the C++ destructors for static objects, but I haven't yet debugged the issue, since the stack trace doesn't point to my code and the issue shouldn't affect normal functioning of the server.

Re-ordering the plugins seems to fix it for now.

I have the same problem. Do you plan to fix it?

license: MIT

license_source: github-api


text:
Chunks aren't scanned when y=0 is void instead of bedrock

Presumably due to CaveBiomes and DatapackUtils checking for bedrock at y=0, the biomes and structures aren't loaded if that bedrock isn't present, such as with this generator. Tested on Snapshot 20w06a, in which it does work if the generator type is set to Surface.
Relevant Discord messages for bug discovery:

I seem to be having this issue as well. The area effect clouds are being summoned in 1.16.1 where they are created under the player, however they don't seem to expire. As a result, being AFK for long periods of time, or even sometimes during short gameplay, causes the game to crash because of the number of area effect clouds being generated. This issue is relevant to my situation because we were focusing on building farms in the End, and as a result, I did not feel inclined enough to file another issue.
Perhaps there was a command change in 1.16.1 that prevented the area effect clouds from being killed.

Support added in 1.2.0

authors: Axoonium ImCoolYeah105 SirMathhman


text:
Scene gadget exception handling

This takes David's exception handling fix from #1242, adds a test case, fixes the NULL m_state crash in a way I'm slightly happier with (no creation of an unused null reference), clears the partially complete scene, and ensures it is recreated fully subsequently once the error in the graph is fixed.

Although the tests passed fine on a workstation, they failed on Travis because there the selection mechanism falls back to an old GL_SELECT method. I've adjusted the test so that it copes in this situation.

@davidsminor does this look alright to you?

Yeah, looks good to me

source: gharchive/pull-request

authors: andrewkaufman davidsminor johnhaddon

repo: ImageEngine/gaffer


text:
Load model checkpoint with weights_only=True

On recent versions of PyTorch the following warning is issued:
FutureWarning: You are using `torch.load` with `weights_only=False` (the current default value), which uses the default pickle module implicitly. It is possible to construct malicious pickle data which will execute arbitrary code during unpickling (See https://github.com/pytorch/pytorch/blob/main/SECURITY.md#untrusted-models for more details). In a future release, the default value for `weights_only` will be flipped to `True`. This limits the functions that could be executed during unpickling. Arbitrary objects will no longer be allowed to be loaded via this mode unless they are explicitly allowlisted by the user via `torch.serialization.add_safe_globals`. We recommend you start setting `weights_only=True` for any use case where you don't have full control of the loaded file. Please open an issue on GitHub for any issues related to this experimental feature.
  checkpoint = torch.load(checkpoint_path, map_location=map_location)

Do we need anything else than the weights? I.e., should we be able to set weights_only=True or are we currently relying on the default value of False?

Turns out this warning is coming from a call from within the open_clip library, and it's the invocation within that library that would need to be updated. The only option we have here is to suppress this warning, possibly like so:
import warnings

# Suppress only FutureWarning messages
warnings.simplefilter(action='ignore', category=FutureWarning)

# Code that may produce FutureWarnings
# ...
# ...
# Re-enable all warnings
warnings.resetwarnings()

@johnbradley thoughts on whether this is worth doing?

thoughts on whether this is worth doing?

@hlapp I would rather leave the warning in and upgrade open_clip when this is resolved there. I'm wondering if there is an issue for this in open_clip.

I can't find it as an issue there.

I created issue https://github.com/mlfoundations/open_clip/issues/928.

Pytorch docs about security.

Loading un-trusted checkpoint with weights_only=False MUST never be done.

The model files (open_clip_pytorch_model.bin or *.pt) are pickled python code. Right now, by default, you are running whatever code is in the model file and not just reading model weights. The docs say that safetensors provides the safest option, but results in more restrictions.

You can supress the weights_only flag via the pytorch TORCH_FORCE_WEIGHTS_ONLY_LOAD environment variable:
export TORCH_FORCE_WEIGHTS_ONLY_LOAD=true
bioclip predict ...

In brief testing everything seems to work fine.

So maybe we can just set that through os.environ if it's not set already (so that people could override it in case some models actually need it to be false)?

authors: hlapp johnbradley

repo: Imageomics/pybioclip


text:
PR -- updated README, added widget to radiology paper notebook, csv links now points to IDC repo instead of ccosmin97

@fedorov

We can improve this further later, but it already improves the current content, so I am merging.


text:
Test image not working

Are there instruction on how to test using my own pictures? Trying to use a picture and got the error
Cannot feed value of shape (1,240,159,1,3) for tensor 'input_gray:0', which has shape '(?,?,?, 1)'

It expects a 1-color-channel image (-> greyscale), said with shape '(?,?,?, 1)'.
A regular color image has 3 channels, just as your image input as you can see your shape has these 3 channels in the last number. So you have to convert your 3-channel color image to a 1-channel one. Or google for one for testing.

As mentioned in Issue #12 you can change one line to convert the color image to 1-channel greyscale directly

authors: urikobi xAnatoliDick

repo: ImagingLab/Colorizing-with-GANs


text:
Übersichtlichere Ausgaben kritischer Fehler beim Frontend Linting

Während der Entwicklung stand ich bisher immer wieder vor dem Problem, dass der Linter meine Codeänderungen im Frontend nicht angenommen hat und ich die notwendigerweise zu korrigierenden Fehlerstellen suchen musste. Problematisch ist dabei nur, dass sich mittlerweile viele Warnungen angestaut haben, unter denen die Meldungen der kritischen Fehler erst gefunden werden müssen.
Ich möchte daher anregen, die Konfiguration des Linters soweit möglich für eine übersichtlichere Ausgabe zu überarbeiten. Ich bin mir sicher, dass die Frontendentwicklung beispielsweise von einer Bündelung der kritischen Fehler zum Schluss der Auflistung oder von farblichen Hervorhebungen profitieren würde. Inwiefern soetwas umsetzbar ist müsste allerdings noch geprüft werden.

Hast du eine beispiel?
Mit linting meinst du eslint oder? Wenn du den editor richtig einstellst sollte eigentlich alles passen, die .editorconfig sollte passen. Ansonsten klappt yarn lint --fixeigentlich immer um alles zu beheben. Manuelle suche bracht man eigentlich nicht.

kritisches fehler anders darstellen
Was genau meinst du? Wenn sich der linter beschwert oder es TS fehler gibt kann er nicht builden. Die warnings sollten überwiegend unused imports oder any nutzung sein.

Und tslint und eslint erros sind doch rot oder?

Zum Background: Bisher hatte ich den gradle bootRun Befehl immer in einem Terminalprogramm ausgeführt. Dieses unterstützt auch Farben und der Gradle-Progress wird auch farblich dargestellt. Die Linter-Ausgaben dagegen werden nicht farblich dargestellt. Ich habe testweise auch mal das --color Flag beim Aufruf von vue-service-cli in der package.json ergänzt. Dann funktioniert das mit der Farbe.
Ich habe jetzt gerade leider keinen Screenshot dazu parat, aber kritische Fehler (error Fehler) werden scheinbar je nach zeitlichem Auftreten in die Ausgabe reingeschrieben, wodurch ein Linter-Log so aussehen kann:
warning ...
warning ...
warning ...
...
warning ...
error ...
warning ...
...
warning
warning

1 error, 70 warnings

Das der Build bei kritischen Fehlern abbricht ist soweit klar und erwartet. Das große Manko ist halt die ein, zwei Stellen von den notwendigerweise zu behebenden error Ausgaben in dem Meer aus warnings zu finden, insbesondere ohne farbliche Kennzeichnung.

Ah, ich starte den client immer mit yarn serve vlt ist der output da unterschiedlich.
aber gut wenns mit dem color flag klappt :)

So sehen die warnings bei mir aus, ich denk das meinst du. Aber die Errors sollten unten in rot kommen.
Langfristig können wir die warnings alle beheben, leider bietet ant design teilweise einfach schlecht types an. form ist bspw. any

Wir denken gerade scheinbar an verschiedene Linter :see_no_evil:. Der auf den ich mich beziehe (welcher auch immer das ist) ist der vom Gradle :client:lint Target. Und der gibt bei mir seine Warnungen und Fehler so aus:

oh ok, ja gut der output ist nervig 😁

Mit yarn serve siehts besser aus ;)
Die anys wegzubekommen ist schon aufwendig, langfristig aber sinnvoll denk ich. Ich wuerde das das ticket aber erstmal schliessen :)

authors: jabrandes jonathangpk


text:
npm run vite not work in Windows

Error message:
> node ./bin/vite

running: vite --config D:\MyFlie\Code\app\node_modules\vue-cli-plugin-vite\config\index.ts
events.js:292
      throw er; // Unhandled 'error' event
      ^

Error: spawn vite ENOENT
    at Process.ChildProcess._handle.onexit (internal/child_process.js:267:19)
    at onErrorNT (internal/child_process.js:469:16)
    at processTicksAndRejections (internal/process/task_queues.js:84:21)
Emitted 'error' event on ChildProcess instance at:
    at Process.ChildProcess._handle.onexit (internal/child_process.js:273:12)
    at onErrorNT (internal/child_process.js:469:16)
    at processTicksAndRejections (internal/process/task_queues.js:84:21) {
  errno: 'ENOENT',
  code: 'ENOENT',
  syscall: 'spawn vite',
  path: 'vite',
  spawnargs: [
    '--config',
    'D:\\MyFlie\\Code\\app\\node_modules\\vue-cli-plugin-vite\\config\\index.ts'
  ]
}

After do some below changes is OK:
const params = [
  './node_modules/vite/bin/vite.js',
  `${process.env.BUILD ? 'build' : ''}`,
  process.env.VITE_DEBUG ? '--debug' : '',
  '--config',
  `${configPath}`
].filter(Boolean)

console.log(`running: vite ${params.join(' ')}`)
const serveService = spawn('node', params, { cwd, stdio: 'inherit' })

@satrong
It is fixed by https://github.com/IndexXuan/vue-cli-plugin-vite/issues/1
what is your version of vue-cli-plugin-vite, 0.1.3 maybe OK

额，我是在你发0.1.3前安装的。现在可以了

authors: IndexXuan satrong

repo: IndexXuan/vue-cli-plugin-vite


text:
[Feature]:Add floating nav bar

Describe the feature
nav bar is not fixed  ,by adding floating nav bar we can either have a nav fixed nor not fixed
Add ScreenShots
No response
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

issue number #53 is addressing the same issue.

repo: Indie-Kart/ecommerce-store


text:
Add missing C# verification

[ ] Ensure no ClangSharpTypereference are present anywhere in the entire tree
[ ] Ensure no VoidTypeReference are present for fields, parameters, or underlying enum types. (Probably easier to check if they're allowed rather than when they're not.)
[ ] Ensure all TranslatedTypeReference actually resolve
[ ] Ensure TranslatedRecord.Members doesn't have any unexpected declarations.
[ ] Ensure TranslatedVTableField.Accessibility is <= TranslatedVTable.Accessibility
[ ] Ensure the relevant entries of a vTable were not moved or removed. (VTables are translated with sequential layout so this breaks the vTable. Adding to the end should be OK though.)
[ ] Verify that implicit values of enums are contiguous

Right now this is being done at output generation time.

[ ] Verify all identifiers are legal in C#. (We handle by replacing the illegal characters with obnoxiously long __UNICODE_0123__, so this should only be a warning. See CSharpCodeWriter.IsLegalIdentifier)

I've marked this with the relatively small label. Each one of these is small on its own, not the entire issue.

I've marked this with the relatively small label. Each one of these is small on its own, not the entire issue.

repo: InfectedLibraries/Biohazrd


text:
The scatterplot reset every time a dataset is loaded even if the source is the same

The scatterplot shouldn't completly reset if the dataset/config changes when there is overlap between the names of the fields.

In 24b5ec6dfe289dd50fbbd37b97d833bd0a927f22, the configured props no longer reset when loading a dataset which shares the selected fields.

repo: InformaticsMatters/react-sci-components


text:
Error in generator gui interface when clicking generate

I am using laravel 5.4 when trying to generate by the generator gui interface accuse Result! Fail error when clicking the generate button.
I made the installation according to the documentation.

+1 got same  behavior

I'm having the same problem.

+1 got same behavior

you can try this :
https://github.com/InfyOmLabs/generator-builder/pull/22

@mzaalan noooooo.... still not working, same error
"exception": "Symfony\Component\HttpKernel\Exception\HttpException"

+1

authors: evertonpaiva francis-santos henriqueraptor mafudelaptu morningmemo mzaalan

repo: InfyOmLabs/generator-builder


text:
feat: nested snap zone is not grabbable by default

Description

If a Snap Zone started a scene nested in an interactable object, the colliders of the snap zone were grabbable as an extension of the interactable object. This PR fixes this behavior.
Note: It is still possible to manually set the snap zones colliders as part of the interactable object.
Type of change

[x] New feature (non-breaking change which adds functionality)

How Has This Been Tested?

Place a snap zone inside an interactable object, then run the scene an try to grab the interactable object by the snap zone, it should not be possible anymore.

:tada: This PR is included in version 1.4.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

authors: Gusinuhe ci-innoactive

repo: Innoactive/XR-Interaction-Component


text:
BUG: Mark CMake variables as advanced

These are mostly from third party libraries. Add marked_as_advanced to
the vendored code.
Keep the standard configuration simple.
Closes #4446

Should ITK_WRAP_* (e.g. ITK_WRAP_complex_float) be advanced?

Should ITK_WRAP_* (e.g. ITK_WRAP_complex_float) be advanced?

No, we want the wrapped pixel types and dimension exposed --they are commonly.

authors: dzenanz thewtex

repo: InsightSoftwareConsortium/ITK


text:
setup: created settings for development

Added first files to set up the development environment

Merged (part of setup process)

repo: InspireCraft/ProjectOMG


text:
Add APIs for invalidating single and many items in section controller

Changes in this pull request

Added -[IGListCollectionContext invalidateLayoutForIndexPaths]
Added -[IGListCollectionContext invalidateLayoutForSectionController]

Unsure the best way to test these new methods, so a suggestion would be welcomed!
Closes #360
Pull request checklist

[x] All tests pass. Demo project builds and runs.
[ ] I added tests, an experiment, or detailed why my change isn't tested.
[ ] I added an entry to the CHANGELOG.md for any breaking changes, enhancements, or bug fixes.
[x] I have reviewed the contributing guide

Was building against macOS scheme so Xcode wasn't flagging errors, should be fixed now.

Will work on the tests ASAP, as you say I think a bit more work is needed just to create a different sort of test object that is usable for more complicated tests.
Amateur hour over here, but fun nonetheless!

@Sherlouk no hurry on this 😄 we don't need to bundle it w/ 2.2, take your time.

fun nonetheless!

🙌

Going to close this PR for the time being until I get a chance to work on this piece, will reopen then!

authors: Sherlouk rnystrom

repo: Instagram/IGListKit


text:
user_recent_media usage

Hello,
I'm trying to use this package to retrieve last media from user, but I'm having trouble (python3.4, python-instagram 1.3.2):
got (django StackTrace):
(404) Unable to parse response, not valid JSON.

(...)

response = wrapped_callback(request, *callback_args, **callback_kwargs) ...
▶ Local vars
(...)views.py in get_instagram_media
                media = SocialFeed.get_instagram_media(user_id) ...
▶ Local vars
(...)social_networks.py in get_instagram_media
                    recent_media, next_ = cls.instagram_api.user_recent_media(user_id=user_id, count=count) ...
▶ Local vars
(...)/lib/python3.4/site-packages/instagram/bind.py in _call
                    return method.execute() ...
▶ Local vars
(...)/lib/python3.4/site-packages/instagram/bind.py in execute
                            content, next = self._do_api_request(url, method, body, headers) ...
▶ Local vars
(...)/lib/python3.4/site-packages/instagram/bind.py in _do_api_request
                            raise InstagramClientError('Unable to parse response, not valid JSON.', status_code=response['status'])

My code (based on project documentation/stackoverflow)
class SocialFeed:
    instagram_api = InstagramAPI(client_id=settings.SOCIAL_AUTH_INSTAGRAM_KEY, client_secret=settings.SOCIAL_AUTH_INSTAGRAM_SECRET)

    (...)

    @classmethod
    def get_instagram_media(cls, user_id, count=6):
        recent_media, next_ = cls.instagram_api.user_recent_media(user_id=user_id, count=count)
        for media in recent_media:
            print(media.caption.text)
(...)

the user_id I'm testing with is "instagram"
Also tried with token (which I got performing token flow on my browser):
instagram_api = InstagramAPI(access_token=settings.SOCIAL_INSTAGRAM_TOKEN)

Forget it, I was using the user name instead of the user_id

repo: Instagram/python-instagram


text:
Clarify required linux kernel patches

Should we use vanilla linux kernel 4.19 or apply patch https://github.com/VCDP/linux-kmd/commit/d5cc059043749162c76285ea2c608da57bed8094 from https://github.com/VCDP/linux-kmd/commits/4.19_intel_media_kbl_19.1.0? (currently we use only SKL but intended to use KBL/CFL in near future)
Previous release MSS 2018 R2 HF2 required a bunch of 50 patches over vanilla linux kernel 4.14, but MSDK 2019 Q1 doesn't mention these patches and requires Kernel 4.14 or later (4.19 or later is recommended)

We have two types of releases: quarterly with broader platform scope targeting vanilla kernel. And
Media Server Studio releases which validated against patched version of i915 KMD which published at https://github.com/VCDP/linux-kmd/ on a limited set of platforms comparing to quarterly releases.
For 2019 Q1 validation was performed against vanilla kernel and I'd recommend to stick with it.

Thanks for information. I thought MSS is finally rebranded to MSDK as was stated in last year press release but seems it is not true yet.
We intended to use MSDK 2019 Q1 + linux 4.19 for both SKL and KBL to reduce moving parts but it seems it is not good release for SKL (suboptimal performance and quality in certain usages comparing to Media Server Studio on Broadwell and Skylake platforms in the release notes)
What do you recommend for production use (non-FEI) in terms of realibility/performance/picture quality given that we could use any linux kernel with/without patches?

Performance difference between MSDK and MSS significantly depends on the selected SKU and usage models. Let me try to give you some hints. The major patches over kernel which give MSS performance improvements are:

Dynamic VDBOX balancing. I.e. dynamic tasks orchestration from few independent workloads over 2 VDBOX engines. This means that SKU should have 2 VDBOX engines for this to take effect. On GT2 systems patch has no effect. Or if your usage models focus on the single workload running on the system this also might not be much relevant.
Slice shutdown. I.e. for the encoding it is better to power off some EU slices to achieve optimal performance. Again, this means that system should have more than 1 slice, hence patch takes effect with GT3 and GT4 SKUs, but for GT2 patch is doing nothing. Next, effect is limited to encoding only and lower the resolution - bigger effect. Specifically, on SD resolutions it is better to have just 1 slice since its resources are enough, for 720p and for some 1080 case typically 2 slices are good, for >=1080p 3 slices might give better performance. Anyhow, if encoding is not the bottle neck for your workloads or you focus on >=FHD cases, patch might not be needed as well.

A range of other patches were upstreamed and are actually available in 4.19.
I hope this helps.

Thanks for detailed explanation.
So performance issues of MSDK 2019 Q1 on SKL should not affect us (we use only SKL GT2 with multiple simultaneous workloads)
Could you explain suboptimal quality in certain usages part of the release notes?
Currently we use simple non-FEI transcoding pipelines (without advanced encoding options), deinterlacing and RGBA+NV12 composition.

We have successfully updated from MSS 2018 R1 (linux kernel 4.4+patches) to MSDK 2019 Q1 (linux kernel 4.19 vanilla)
FYI, here are our benchmark/test results on Skylake i3-6300:

transcoding speed roughly the same (MSDK 2019 Q1 0-5% faster in different testcases)
MSDK 2019 Q1 slightly degraded mpeg2 quality (average PSNR: 39.0->38.1, average SSIM: 14.2->13.5)
h264 quality has not changed

authors: alex3d dvrogozh onabiull

repo: Intel-Media-SDK/MediaSDK


text:
[SQL Index and Data Source Cache] The web UI cannot show cache size when using Plasma and q68.sql will be suspended to wait for cache free.

I run 9 IO-intensive queries of TPCDS for 3 rounds and use Plasma Service for data source cache. The data scale is 3TB and PEME is enough for cache. There are two issues were found:

When running queries for the 2nd round, q68.sql will be suspended and wait for cache free which causes the test fail:

The web UI cannot accuratly display the cache size:

cc @jikunshang

The first issue can be resolved by increasing spark.sql.oap.dcpmm.free.wait.threshold configuration, it's maximum cache size one executor could get.

authors: haojinIntel jikunshang zhixingheyi-tian

repo: Intel-bigdata/OAP


text:
Crashing in go after Annette after the elevator, the door that leads to the sewer

Seed: R520-G6EV-XQRV1FWLLA03

crash 3 times and i cant keep progress

Door 404

i use debug for teleport in another doors and keep crash

Possibly caused by enemy randomization. I have changed things, particularly this room and it doesn't appear to crash in dev. builds - so hopefully it is fixed.

repo: IntelOrca/biorand


text:
adding test checks for rambo

Rambo does not require a common data generation infrastructure since it does not use random data as input

I have fixed whitespaces and merged w/ main.

authors: PokhodenkoSA adarshyoga

repo: IntelPython/dpbench


text:
Add support for pipelined GPU kernel execution to numba-dpex

In numba.cuda host-device data movement can be overlapped with compute by launching multiple streams. Refer following example. We lack a similar feature in numba-dppy and will need to enable support for dpctl.SyclEvents to get such a functionality.
import numpy as np
import sys
import time

from numba import cuda

class CudaTimer(object):
    def __init__(self):
        self.times = []

    def __call__(self, stream):
        self.stream = stream
        return self.__enter__()

    def __enter__(self):
        self.es = cuda.event()
        self.ef = cuda.event()
        self.es.record(stream=self.stream)
        return self

    def __exit__(self, exc_type, exc_val, exc_tb):
        self.ef.record(stream=self.stream)
        self.times.append((self.es, self.ef))
        del self.stream
        del self.es
        del self.ef
        pass

    @property
    def dt(self):
        return sum(
            cuda.event_elapsed_time(es, ef)/1000
            for es, ef in self.times
        )

@cuda.jit
def increment_by_one(an_array):
    pos = cuda.grid(1)
    if pos < an_array.size:
        for _ in range(1300):
            an_array[pos] += 1

def pinned_array(array):
    src = cuda.pinned_array(array.shape, dtype=array.dtype)
    src[...] = array
    return src

def run_serial(a, threadsperblock, blockspergrid, n_itr):
    stream_a = cuda.stream()

    timer_t = CudaTimer()
    timer_c = CudaTimer()

    a_pinned = pinned_array(a)

    t0 = time.time()
    for _ in range(n_itr):
        with timer_t(stream_a):
            _a = cuda.to_device(a_pinned, stream=stream_a)

        with timer_c(stream_a):
            increment_by_one[blockspergrid, threadsperblock, stream_a](_a)

    stream_a.synchronize()
    dt = time.time() - t0

    return dt, timer_t.dt, timer_c.dt

def run_pipeline(a, threadsperblock, blockspergrid, n_itr):
    stream_a = cuda.stream()
    stream_b = cuda.stream()

    timer_t = CudaTimer()
    timer_c = CudaTimer()

    a_pinned = pinned_array(a)

    t0 = time.time()
    with timer_t(stream_a):
        _a = cuda.to_device(pinned_array(a), stream=stream_a)

    for i in range(n_itr-1):
        if i % 2 == 0:
            with timer_t(stream_b):
                _b = cuda.to_device(a_pinned, stream=stream_b)

            with timer_c(stream_a):
                increment_by_one[blockspergrid, threadsperblock, stream_a](_a)

        else:
            with timer_t(stream_a):
                _a = cuda.to_device(a_pinned, stream=stream_a)

            with timer_c(stream_b):
                increment_by_one[blockspergrid, threadsperblock, stream_b](_b)

    with timer_c(stream_b):
        increment_by_one[blockspergrid, threadsperblock, stream_b](_b)

    stream_a.synchronize()
    stream_b.synchronize()
    dt = time.time() - t0

    return dt, timer_t.dt, timer_c.dt

if len(sys.argv) > 1:
    n = int(sys.argv[1])
else:
    n = 102400000

if len(sys.argv) > 2:
    n_itr = int(sys.argv[2])
else:
    n_itr = 100

print("timing %d elements for %d iterations" % (n, n_itr), flush=True)

print("using %f MB of memory" % (n * 4 /1024/1024), flush=True)

a = np.arange(n, dtype=np.float32)

threadsperblock = 32
blockspergrid = (a.size + (threadsperblock - 1)) // threadsperblock

dtp = run_pipeline(a, threadsperblock,blockspergrid, n_itr)
print("pipeline time tot|pci|cmp|speedup: %s|%s|%s|%sx" % tuple(list(dtp) + [sum(dtp[1:]) / dtp[0]]), flush=True)

dts = run_serial(a, threadsperblock,blockspergrid, n_itr)
print("serial   time tot|pci|cmp|speedup: %s|%s|%s|%sx" % tuple(list(dts) + [sum(dts[1:]) / dts[0]]), flush=True)

@ZzEeKkAa Please see https://github.com/oleksandr-pavlyk/async-pipelining-example.git for an example of running this workflow based on dpctl.

@ZzEeKkAa can you please test out the example @oleksandr-pavlyk  has developed with the latest feature that got added in #1249.
It will be good to add it as an example and close this issue.

So, this is an example how it can be now implemented in dpex, but I was unable to get objective results locally. Memory copy operation was much faster than the computation deviation:
import time
import argparse

import numpy as np

import dpnp
import dpctl
import numba_dpex as dpex
import numba_dpex.experimental as dpex_exp

@dpex_exp.kernel
def async_kernel(x):
    idx = dpex.get_global_id(0);

    for i in range(1300):
        den = x.dtype.type(i+1)
        x[idx] += x.dtype.type(1) / (den * den * den);

def run_serial(host_arr, n_itr):
    t0 = time.time()
    q = dpctl.SyclQueue()

    a_host = dpnp.asarray(host_arr, usm_type="host", sycl_queue=q)
    usm_host_data = dpnp.get_usm_ndarray(a_host).usm_data

    batch_shape = (n_itr,) + a_host.shape
    device_alloc = dpnp.empty(batch_shape, usm_type="device", sycl_queue=q)

    for offset in range(n_itr):
        _a = device_alloc[offset]
        _a_data = dpnp.get_usm_ndarray(_a).usm_data

        q.memcpy(_a_data, usm_host_data, usm_host_data.nbytes)

        dpex_exp.call_kernel(
            async_kernel, dpex.Range(len(_a)), _a,
        )

    dt = time.time() - t0

    return dt, None, None

def run_pipeline(host_arr, n_itr):
    t0 = time.time()
    q = dpctl.SyclQueue()

    a_host = dpnp.asarray(host_arr, usm_type="host", sycl_queue=q)
    usm_host_data = dpnp.get_usm_ndarray(a_host).usm_data

    batch_shape = (n_itr,) + a_host.shape
    device_alloc = dpnp.empty(batch_shape, usm_type="device", sycl_queue=q)

    e_a = None
    e_b = None

    for offset in range(n_itr):
        _a = device_alloc[offset]
        _a_data = dpnp.get_usm_ndarray(_a).usm_data

        e_a = q.memcpy_async(_a_data, usm_host_data, usm_host_data.nbytes, [e_a] if e_a is not None else [])

        e_a.wait()

        _, e_a = dpex_exp.call_kernel_async(
            async_kernel, dpex.Range(len(_a)),(e_a,), _a,
        )

        e_a.wait()

        e_a, e_b = e_b, e_a

    q.wait()
    dt = time.time() - t0

    return dt, None, None

def main():
    parser = argparse.ArgumentParser(description='Process some integers.')
    parser.add_argument('--n', type=int, default=2_000_000,
                        help='an integer for the input array')
    parser.add_argument('--n_itr', type=int, default=100,
                        help='number of iterations')
    parser.add_argument('--reps', type=int, default=5,
                        help='number of repeats')
    parser.add_argument('--algo', type=str, default="pipeline",
                        help='algo')

    args = parser.parse_args()

    print("timing %d elements for %d iterations" % (args.n, args.n_itr), flush=True)

    print("using %f MB of memory" % (args.n * 4 /1024/1024), flush=True)

    a = np.arange(args.n, dtype=np.float32)

    algo_func = {
        "pipeline": run_pipeline,
        "serial": run_serial,
    }.get(args.algo)

    for _ in range(args.reps):
        dtp = algo_func(a, args.n_itr)
        print(f"{args.algo} time tot|pci|cmp|speedup: {dtp}", flush=True)

if __name__ == "__main__":
    main()

This issue can be closed now. If there are any performance issues, please feel free to open performance related issue.

authors: ZzEeKkAa diptorupd oleksandr-pavlyk

repo: IntelPython/numba-dpex


text:
Release 0.20.1

List of tasks that should be completed for the next tag:

[x] Prange reduction loops
[x] SyclQueue support and filter string performance regression issue
[x] dpbench dpnp compilation (best effort)
[x] dpcpp-llvm-spirv
[x] Update changelog
[x] tag release
[x] merge tag into gold/2021

Done


text:
[WIP] Refactor buildscripts

Remove extra useless recipes
Move Azure templates to azure folder
Add wheels build via conda recipe (second output - wheel)
Add single build.py and test.py script with interface
Add smoke tests after build (import and exec of calc Pi example)
Add conda installation on Windows
Refactor names in buildscripts and Travis & Azure
Add coverage config file; execute coverage on develop installation

Hello @Vyacheslav-Smirnov! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file buildscripts/build.py:

Line 23:81: E501 line too long (141 > 80 characters)
Line 24:81: E501 line too long (102 > 80 characters)
Line 25:81: E501 line too long (102 > 80 characters)
Line 26:81: E501 line too long (86 > 80 characters)
Line 27:81: E501 line too long (85 > 80 characters)
Line 32:15: E221 multiple spaces before operator
Line 33:11: E221 multiple spaces before operator
Line 34:10: E221 multiple spaces before operator
Line 36:17: E221 multiple spaces before operator
Line 37:81: E501 line too long (123 > 80 characters)
Line 53:81: E501 line too long (128 > 80 characters)
Line 54:81: E501 line too long (94 > 80 characters)
Line 55:81: E501 line too long (86 > 80 characters)
Line 62:81: E501 line too long (96 > 80 characters)
Line 65:5: E303 too many blank lines (2)
Line 71:32: E128 continuation line under-indented for visual indent
Line 72:54: E127 continuation line over-indented for visual indent
Line 72:81: E501 line too long (82 > 80 characters)
Line 74:81: E501 line too long (96 > 80 characters)
Line 75:81: E501 line too long (119 > 80 characters)
Line 77:14: E226 missing whitespace around arithmetic operator
Line 81:14: E226 missing whitespace around arithmetic operator
Line 87:5: E722 do not use bare 'except'
Line 88:18: E226 missing whitespace around arithmetic operator
Line 89:81: E501 line too long (87 > 80 characters)
Line 93:14: E226 missing whitespace around arithmetic operator
Line 100:14: E226 missing whitespace around arithmetic operator
Line 102:81: E501 line too long (85 > 80 characters)

In the file buildscripts/sdc_pi_example.py:

Line 5:1: E302 expected 2 blank lines, found 1
Line 11:41: E226 missing whitespace around arithmetic operator
Line 14:1: E305 expected 2 blank lines after class or function definition, found 1
Line 14:19: W292 no newline at end of file

In the file buildscripts/test.py:

Line 23:43: W291 trailing whitespace
Line 24:81: E501 line too long (104 > 80 characters)
Line 25:81: E501 line too long (93 > 80 characters)
Line 26:81: E501 line too long (96 > 80 characters)
Line 27:81: E501 line too long (115 > 80 characters)
Line 28:81: E501 line too long (101 > 80 characters)
Line 29:81: E501 line too long (101 > 80 characters)
Line 30:81: E501 line too long (85 > 80 characters)
Line 33:81: E501 line too long (119 > 80 characters)
Line 37:14: E221 multiple spaces before operator
Line 38:17: E221 multiple spaces before operator
Line 39:11: E221 multiple spaces before operator
Line 40:10: E221 multiple spaces before operator
Line 41:17: E221 multiple spaces before operator
Line 42:17: E221 multiple spaces before operator
Line 43:17: E221 multiple spaces before operator
Line 44:81: E501 line too long (123 > 80 characters)
Line 60:81: E501 line too long (128 > 80 characters)
Line 68:81: E501 line too long (96 > 80 characters)
Line 71:5: E303 too many blank lines (2)
Line 71:21: E712 comparison to True should be 'if cond is True:' or 'if cond:'
Line 72:18: E226 missing whitespace around arithmetic operator
Line 75:81: E501 line too long (83 > 80 characters)
Line 76:9: E722 do not use bare 'except'
Line 77:81: E501 line too long (151 > 80 characters)
Line 80:21: E712 comparison to True should be 'if cond is True:' or 'if cond:'
Line 81:9: E113 unexpected indentation
Line 81:18: E226 missing whitespace around arithmetic operator
Line 85:81: E501 line too long (96 > 80 characters)
Line 86:9: E722 do not use bare 'except'
Line 87:22: E226 missing whitespace around arithmetic operator
Line 93:18: E226 missing whitespace around arithmetic operator
Line 98:5: E303 too many blank lines (2)
Line 102:5: E722 do not use bare 'except'
Line 103:18: E226 missing whitespace around arithmetic operator
Line 104:81: E501 line too long (86 > 80 characters)
Line 109:5: E303 too many blank lines (2)
Line 112:37: E128 continuation line under-indented for visual indent
Line 113:59: E127 continuation line over-indented for visual indent
Line 113:81: E501 line too long (127 > 80 characters)
Line 117:22: E226 missing whitespace around arithmetic operator
Line 118:81: E501 line too long (92 > 80 characters)
Line 122:22: E226 missing whitespace around arithmetic operator
Line 124:81: E501 line too long (93 > 80 characters)

In the file buildscripts/utilities.py:

Line 10:1: E302 expected 2 blank lines, found 0
Line 12:13: E221 multiple spaces before operator
Line 14:17: E221 multiple spaces before operator
Line 30:81: E501 line too long (102 > 80 characters)
Line 31:81: E501 line too long (97 > 80 characters)
Line 32:81: E501 line too long (120 > 80 characters)
Line 33:81: E501 line too long (120 > 80 characters)
Line 38:81: E501 line too long (91 > 80 characters)
Line 47:81: E501 line too long (112 > 80 characters)
Line 50:81: E501 line too long (103 > 80 characters)
Line 62:81: E501 line too long (89 > 80 characters)
Line 71:81: E501 line too long (91 > 80 characters)
Line 72:66: E261 at least two spaces before inline comment
Line 72:81: E501 line too long (87 > 80 characters)
Line 77:81: E501 line too long (95 > 80 characters)
Line 78:81: E501 line too long (114 > 80 characters)
Line 80:81: E501 line too long (88 > 80 characters)
Line 81:81: E501 line too long (113 > 80 characters)
Line 83:5: E722 do not use bare 'except'
Line 84:18: E226 missing whitespace around arithmetic operator
Line 85:81: E501 line too long (93 > 80 characters)
Line 92:14: E226 missing whitespace around arithmetic operator
Line 92:18: E241 multiple spaces after ','
Line 94:14: E226 missing whitespace around arithmetic operator
Line 94:18: E241 multiple spaces after ','
Line 98:81: E501 line too long (100 > 80 characters)
Line 102:14: E226 missing whitespace around arithmetic operator
Line 108:81: E501 line too long (111 > 80 characters)
Line 110:81: E501 line too long (118 > 80 characters)
Line 125:81: E501 line too long (83 > 80 characters)

Hi @Hardcode84 , @AlexanderKalistratov ,
Could you please review the changes?

repo: IntelPython/sdc


text:
request changelog

v0.15.0 has been released.
Are there any details about the changes from v0.13.0 to v0.15.0?
I found a few big changes. These are important pieces of information for developers.

removed serialPortType from SerialConfig (it is destructive change!)
add FHD_Rect to PreviewMode
add advanced_mode to DeviceConfig
add FaceRect to Image

Also, I have many other questions.

Release notes:
Added recognition-only authentication mode.
Auto-exposure.

what is recognition-only authentication mode?
how did you change auto exposure? (ON or OFF)

Please release changelog! I'm afraid undocumented changes.

BTW, this is too many changes in one commit. It is hard to track changes for developer.

Hi,
Most of the changes published in release notes.
Why do you need portType in addition to port number? Our library working seamless if it's USB or UART. Moreover we have auto-detection of port type.
The rest features you mentioned (FHD_Rect, advanced_mode...) they are not documented by purpose as available only to specific customers with special license.  Published FW doesnt support them.
RecognitionOnly mode not running Anti-Spoofing algo(s) as part of authentication.
Auto-exposure is controlled automatically by FW and starts upon preview. Users dont have control for it.
Currently all development is done in an internal github, then fully validated and the release is published to the public github.
In future we plan to establish automated CI and push smaller commits directly to public github

Why do you need portType in addition to port number? Our library working seamless if it's USB or UART. Moreover we have auto-detection of port type.

No, I'm not saying that change is bad. I think that change is a good one.
However, I'm afraid undocumented changes. That change is not even listed in the release notes.
We didn't know about that change until we read the code.

The rest features you mentioned (FHD_Rect, advanced_mode...) they are not documented by purpose as available only to specific customers with special license. Published FW doesnt support them.

Haha, Yes, that's it! I want a document with such an explanation.
We didn't even know that the feature was not available to the public until your comment.

RecognitionOnly mode not running Anti-Spoofing algo(s) as part of authentication.
Auto-exposure is controlled automatically by FW and starts upon preview. Users dont have control for it.

Good! It would be better if this is documented in changelog.

repo: IntelRealSense/RealSenseID


text:
No Frames Received!

librealsense
2.50.0 RELEASE

OS
Linux

Name
Intel RealSense L515

Serial Number
f0270634

Firmware Version
01.05.08.01

Camera Locked
YES

Usb Type Descriptor
2.1

Product Line
L500

Asic Serial Number
0003b53529cf

Firmware Update Id
0003b53529cf

No Frames Received in depth camera.

Hi @TongQY  Could you first try unplugging the micro-sized end of the USB cable from the base of the camera, reversing the connector's orientation and plugging it back into the L515 camera, please (USB-C cables are two-way insertion at the micro-sized end).  Does doing so make any difference?

Hi @TongQY  Do you require further assistance with this case, please?  Thanks!

Case closed due to no further comments received.

authors: MartyG-RealSense TongQY

repo: IntelRealSense/librealsense


text:
Introducing the RealSense D457 GMSL/FAKRA stereo camera

Hi everyone,
Intel have introduced a new member of the RealSense stereo camera family called the D457.  It is based around the D450 depth module and the new Vision Processor D4 V5.
https://www.intelrealsense.com/depth-camera-d457/
https://www.intel.com/content/www/us/en/newsroom/news/new-realsense-depth-camera-d457.html

The D457 is expected to be available in the fourth quarter of 2022 and its listing on the official RealSense Store can be found here:
https://store.intelrealsense.com/buy-intel-realsense-depth-camera-d457.html
To quote the store page:
"The Intel® RealSense™ Depth Camera D457 is our first GMSL/FAKRA high bandwidth stereo camera.  The D457 has an IP65 grade enclosure protecting it from dust ingress and projected water.  D457 has an on-board Maxim serializer chip.  A Maxim de-serializer is needed at host side to decode the streams".

The dedicated data sheet document for the D457 can be downloaded here:
https://dev.intelrealsense.com/docs/intel-realsense-d400-series-product-family-datasheet

Can i use only two lanes for D457 instead of three lanes?
Since only two lanes wired on our boards.
Thank you.

Hi @dennishuneou  Are you referring to the MIPI CSI-2 lanes, please?  If you are, the table below from the data sheet document for the D457 camera lists 2 lanes for the interface to the Vision Processor D4 and 1 lane for the interface to the RGB sensor.

when using GMSL2 for transmission,
Depth stream used one lane.
Left Image[y8] and IMU used one lane.
RGB used one lane.
Can i use only 2 lanes for 4 streams.

My colleagues confirmed that 2 lanes are being used now on D457.

Is this mandatory?
I’m working for D457 on our hardware platform.
HW-SYNC
SerDes Depth Trigger Path MFP7 > MFP8
sudo i2cset -f -y 2 0x48 0x02 0x82c5 w #MFP7
sudo i2cset -f -y 2 0x48 0x02 0x1fc6 w
sudo i2cset -f -y 2 0x40 0x02 0x84d6 w #MFP8
sudo i2cset -f -y 2 0x40 0x02 0x60d7 w #OUT_TYPE bit to 1
sudo i2cset -f -y 2 0x40 0x02 0x1fd8 w
SerDes RGB Trigger Path MFP9 > MFP0
sudo i2cset -f -y 2 0x48 0x02 0x82cb w #MFP9
sudo i2cset -f -y 2 0x48 0x02 0x1bcc w
sudo i2cset -f -y 2 0x40 0x02 0x84be w #MFP0
sudo i2cset -f -y 2 0x40 0x02 0x60bf w #OUT_TYPE bit to 1
sudo i2cset -f -y 2 0x40 0x02 0x1bc0 w
Best Regards,
Dennis Hu
Neousys Technology America Inc.
3384 Commercial Ave., Northbrook, IL 60062 | (D) 847-656-3395 | (P) 847-656-3298 X407
From: MartyG-RealSense @.>
Sent: Wednesday, March 15, 2023 12:55 PM
To: IntelRealSense/librealsense @.>
Cc: Dennis Hu @.>; Mention @.>
Subject: Re: [IntelRealSense/librealsense] Introducing the RealSense D457 GMSL/FAKRA stereo camera (Issue #10964)
My colleagues confirmed that 2 lanes are being used now on D457.
—
Reply to this email directly, view it on GitHubhttps://github.com/IntelRealSense/librealsense/issues/10964#issuecomment-1470496578, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AY7R4PPQBQOQ3GNIZKUG4A3W4H67DANCNFSM6AAAAAAQ4Y6TVM.
You are receiving this because you were mentioned.Message ID: @.@.>>

Hi @dennishuneou  Could you provide further information about your question, please?  Are you asking if D457 having 2 lanes instead of 3 is mandatory?

Hi ,
I ported d4xx driver and dts into Xavier NX.
I can’t capture video when running realsense-viewer.
I read out registers of Max9295, I found that the pixclk is not locked.
So, I think that maybe we must send external trigger signal to camera.
The following content comes from Serdes_D457_1.0.0.A.sh
HW-SYNC
SerDes Depth Trigger Path MFP7 > MFP8
sudo i2cset -f -y 2 0x48 0x02 0x82c5 w #MFP7
sudo i2cset -f -y 2 0x48 0x02 0x1fc6 w
sudo i2cset -f -y 2 0x40 0x02 0x84d6 w #MFP8
sudo i2cset -f -y 2 0x40 0x02 0x60d7 w #OUT_TYPE bit to 1
sudo i2cset -f -y 2 0x40 0x02 0x1fd8 w
SerDes RGB Trigger Path MFP9 > MFP0
sudo i2cset -f -y 2 0x48 0x02 0x82cb w #MFP9
sudo i2cset -f -y 2 0x48 0x02 0x1bcc w
sudo i2cset -f -y 2 0x40 0x02 0x84be w #MFP0
sudo i2cset -f -y 2 0x40 0x02 0x60bf w #OUT_TYPE bit to 1
sudo i2cset -f -y 2 0x40 0x02 0x1bc0 w
Best Regards,
Dennis Hu
Neousys Technology America Inc.
3384 Commercial Ave., Northbrook, IL 60062 | (D) 847-656-3395 | (P) 847-656-3298 X407
From: MartyG-RealSense @.>
Sent: Monday, March 20, 2023 11:39 AM
To: IntelRealSense/librealsense @.>
Cc: Dennis Hu @.>; Mention @.>
Subject: Re: [IntelRealSense/librealsense] Introducing the RealSense D457 GMSL/FAKRA stereo camera (Issue #10964)
Hi @dennishuneouhttps://github.com/dennishuneou Could you provide further information about your question, please? Are you asking if D457 having 2 lanes instead of 3 is mandatory?
—
Reply to this email directly, view it on GitHubhttps://github.com/IntelRealSense/librealsense/issues/10964#issuecomment-1476575631, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AY7R4PNEAYYPICNEWGG5YGLW5CBYVANCNFSM6AAAAAAQ4Y6TVM.
You are receiving this because you were mentioned.Message ID: @.@.>>

Camera firmware driver 5.14.0.0 and RealSense SDK version 2.53.1 are minimum requirements.  Can you confirm if you are using this firmware and SDK version please?
The MIPI reference driver is also designed for use with Intel's own de-serializer board at the link below.  Furthermore, the MIPI driver is designed for use with AGX Xavier specifically, whilst you are using Xavier NX.  I note though that you have ported the driver, which should be a solution for these issues.
https://store.intelrealsense.com/buy-intel-realsense-des457.html

I bought camera week ago.
The firmware version is 5.13.0.53.
Realsense SDK is 2.50.0. installed from vcpkg.
Best Regards,
Dennis Hu
Neousys Technology America Inc.
3384 Commercial Ave., Northbrook, IL 60062 | (D) 847-656-3395 | (P) 847-656-3298 X407
From: MartyG-RealSense @.>
Sent: Monday, March 20, 2023 11:55 AM
To: IntelRealSense/librealsense @.>
Cc: Dennis Hu @.>; Mention @.>
Subject: Re: [IntelRealSense/librealsense] Introducing the RealSense D457 GMSL/FAKRA stereo camera (Issue #10964)
Camera firmware driver 5.14.0.0 and RealSense SDK version 2.53.1 are minimum requirements. Can you confirm if you are using this firmware and SDK version please?
The MIPI reference driver is also designed for use with Intel's own de-serializer board at the link below. Furthermore, the MIPI driver is designed for use with AGX Xavier specifically, whilst you are using Xavier NX. I note though that you have ported the driver, which should be a solution for these issues.
https://store.intelrealsense.com/buy-intel-realsense-des457.html
—
Reply to this email directly, view it on GitHubhttps://github.com/IntelRealSense/librealsense/issues/10964#issuecomment-1476599659, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AY7R4PP2IU7XD3RVYRDZEE3W5CDXNANCNFSM6AAAAAAQ4Y6TVM.
You are receiving this because you were mentioned.Message ID: @.@.>>

SDK 2.50.0 does not have MIPI support as it had not been implemented yet in that SDK version.  SDK 2.53.1 which introduces MIPI support should be used, and firmware should be updated to 5.14.0.0.
If MIPI is not an absolute requirement for your project then there is also the option to move a switch under the camera's removable casing cap from 'MIPI' position to 'USB' position so that it is detected and performs as a D455 USB camera, as described at https://github.com/IntelRealSense/librealsense/issues/11010#issuecomment-1433488437

authors: MartyG-RealSense dennishuneou


text:
depth_aligned_to_color for librealsense + openCV

Required Info

Camera Model
R200

Firmware Version

Operating System & Version
Ubuntu

Kernel Version (Linux Only)
4.0

Build System
Makefile

Hey guys!
I am testing  " depth_aligned_to_color" (the synthetic stream) in Ubuntu and OpenCV, still no success in showing the image.
This is how I am showing RGB: (I would like to have something similar with depth_aligened_to_color"
cv::Mat rgb_show;
const uint8_t * rgb_frame = reinterpret_cast<const uint8_t* (dev->get_frame_data(rs::stream::color));
cv::Mat rgb = cv::Mat(480, 640, CV_8UC3, (void*)rgb_frame);
cvtColor(rgb, rgb_show, CV_BGR2RGB);
cv::imshow("RGB", rgb_show);
Thanks.

Hello @l3s777 ,
Do you still need help with this issue?
Regards,
Jesus G.
Intel Customer Support


text:
Can't build devleopment branch using Unity page instructions.

Before opening a new issue, we wanted to provide you with some useful suggestions (Click "Preview" above for a better view):

Consider checking out SDK examples.
Have you looked in our documentations?
Is you question a frequently asked one?
Try searching our GitHub Issues (open and closed) for a similar issue.

All users are welcomed to report bugs, ask questions, suggest or request enhancements and generally feel free to open new issue, even if they haven't followed any of the suggestions above :)

Required Info

Camera Model
L515

Firmware Version
1.4.2.1

Operating System & Version
{Win 10)

Kernel Version (Linux Only)

Platform
PC

SDK Version
2.36 development branch}

Language
unity }

Segment

Issue Description
I am trying to run a build for the development branch to test if the L515 will work now.  I'm using instructions at:  https://github.com/IntelRealSense/librealsense/tree/master/wrappers/unity
I can get through the CMake step which creates the files in the build folder.  However, it then asks me to open the realsense.sln project, but there is only a file named "librealsense.sln".  If I open the file "librealsense.sln" with Visual Studio 2019 it tells me it cannot reference "realsense.sln".
I then tried to change the target for the C# wrappers to .NET 3.5 and it tells me 3.5 will not run System.xaml.  If I run the build I get hundreds of errors and a failure.
If I try to run the Unity examples without rebuilding the code, I have to use the old version of the unitypackage file and am assuming that's why I can't connect to the L515.
Any help?
Is it looking for the wrong files?

assembly name of intel.realsense.dll is wrong. the assembly name is currently "intel.realsensed" who realsensed this realsense in the past should fix it.

I tried to build 2.37 from github and had problems with atlcom.h and similar headers missing,.  I read some github issue here that said an atl installer had been added to your installer.  reinstalled everything including visual studio 2019 and still was not able to build.
I installed the binary 2.37(pre release) SDK installer and 2.37 unitypackage  and lidar works with realsense viewer but not unity..  unity 2019.3.13 Windows 10 L515 Fimrware 1.4.2.1
even newer device D455 works with Unity on windows using the new 2.37 unitypackage.

Hi @VisibleMeasurement
I see you were able to get things working based on your comments on the other github thread:  https://github.com/IntelRealSense/librealsense/issues/6859
There looks like others that were not able to get it working, if you can outline what you've done that would be great.
*If we don’t hear from you in 7 days, this issue will be closed.

I did manage to get the L515 running in Unity, but I did not compile the code myself.  I used the newest unity package that was compiled by the RealSense team.  With that assest set loaded, I could open the default project provided and see the camera running in Unity.  Functionality was very similar to RealSense Viewer, so still have work to do before implementing anything more, like SLAM.

Thanks for the update @VisibleMeasurement

@VisibleMeasurement
Is there anything else needed on this one?
*If we don’t hear from you in 7 days, this issue will be closed.

authors: RealSenseSupport VisibleMeasurement chrisrogers3d sldprt


text:
The depth start of get_distance() function ?

Required Info

Camera Model
D400

Issue Description
When I use get_distance() to get the distance from camera to the surface in its front. There is always about 4mm error if I set the depth start at the imager, so I guess the function return the distance to front cover glass.
Is that so ? The depth starts from front cover glass ?

Hi @gywhitel   Yes, on the cased versions of RealSense 400 Series cameras, depth is measured from the front glass.  On the caeless Depth Kit versions of RealSense cameras, depth is measured from the lens or from the back of the module.
You can get the ground truth of measurements by adding a minus value to them.  On the D435 and D435i models, that is -4.2 mm

Thanks ! Problem solved.

Thanks very much @gywhitel - I'm pleased I could help.  I have updated the table graphic to show the value for the D455 model too.

authors: MartyG-RealSense gywhitel


text:
particle radius

Hi
I am simulating the code with particles with a radius of 0.005 and the number of particles are 20000. But when I change the radius from 0.005 to 0.003 a problem appears. when the particles reach the solid body, they are exploding.
Is there any restriction for the particle radius?
Regards

There is no restriction. However, if the dimension of the particles gets smaller, you probably also have to adapt the time step size. You could also try with a different boundary handling (Akinci).

authors: hosseinrezaa janbender


text:
CUDAException when running scene file

I build SPlisHSPlasH with Use GPU neighborhood search" ON. I tried to run an example scene file but I get an error with 'CUDAException'

Output directory: /home/jason/splisplash/bin/output/CoilingModel_Weiler2018
Load scene file: /home/jason/splisplash/data/Scenes/CoilingModel_Weiler2018.json
Initialize static boundary simulation
Initialize fluid particles
Number of fluid particles: 956
OpenGL version 4.6
Using GLEW 1.12.0
Vendor: NVIDIA Corporation
Renderer: GeForce GTX 750 Ti/PCIe/SSE2
Version: 4.6.0 NVIDIA 455.23.05
terminate called after throwing an instance of 'CUDAException'
what():  no kernel image is available for execution on the device
Aborted (core dumped)

When I run make I get the following warning but no error

Cloning into 'Ext_GenericParameters'...
Cloning into 'Ext_Discregrid'...
-- cuNSearch::Real = float
-- Configuring done
CMake Warning (dev) in CMakeLists.txt:
Policy CMP0104 is not set: CMAKE_CUDA_ARCHITECTURES now detected for NVCC,
empty CUDA_ARCHITECTURES not allowed.  Run "cmake --help-policy CMP0104"
for policy details.  Use the cmake_policy command to set the policy and
suppress this warning.
CUDA_ARCHITECTURES is empty for target "cuNSearch".
This warning is for project developers.  Use -Wno-dev to suppress it.
-- Generating done
-- Build files have been written to: /home/jason/splisplash/extern/cuNSearch/src/Ext_NeighborhoodSearch-build

Hm, this is hard to tell. Which Cuda version did you install?

The issue is probably cause by CUDA 11.1. No issue after I switch to CUDA 9.0.


text:
Feat (optimizer): add new optimizer for spliting zero tensor

Thanks for your contribution and we appreciate it a lot. The following instructions would make your pull request more healthy and more easily get feedback. If you do not understand some items, don't worry, just make the pull request and seek help from maintainers.
Motivation
A new optimizer which uniformly splits the parameters in the optimizer state into each rank in zero parallelism.
functions implemented：

[x] dp
[x] tp
[x] pp
[x] fsp and msp
[x] isp
[x] zero1.5
[x] overlap grad
[x] overlap param
[x] checkpoint

Check
trace:
overlap param and grad

loss:
dp8:

dp2_tp2_pp2_fsp:

isp:

BC-breaking (Optional)
Does the modification introduce changes that break the backward compatibility of the downstream repositories?
If so, please describe how it breaks the compatibility and how the downstream projects should modify their code to keep compatibility with this PR.
Use cases (Optional)
If this PR introduces a new feature, it is better to list some use cases here and update the documentation.
Checklist
Before PR:

[ ] Pre-commit or other linting tools are used to fix the potential lint issues.
[ ] Bug fixes are fully covered by unit tests, the case that causes the bug should be added in the unit tests.
[ ] The modification is covered by complete unit tests. If not, please add more unit test to ensure the correctness.
[ ] The documentation has been modified accordingly, like docstring or example tutorials.

After PR:

[ ] If the modification has potential influence on downstream or other related projects, this PR should be tested with those projects.
[ ] CLA has been signed and all committers have signed the CLA in this PR.

/LGTM

repo: InternLM/InternEvo


text:
[Bug] 多图推理效果不佳

Checklist

[X] 1. I have searched related issues but cannot get the expected help.
[X] 2. The bug has not been fixed in the latest version.

Describe the bug
多图推理
你好，使用该示例进行多图推理时回答效果很差，我放了三张图片，都是可以访问的，但是返回了五张图片的描述。
请问下多图推理是因为InternVL-Chat-V1-5具有多图处理能力，还是在推理侧做了什么改动？
Reproduction
我的代码：
from lmdeploy.vl import load_image

pipe = pipeline('`InternVL-Chat-V1-5`',
                backend_config=TurbomindEngineConfig(session_len=8192, tp=2))

image_urls=[
    'https://i0.wp.com/wx3.sinaimg.cn/orj360/008yp4y7gy1hqfhh0d5eij30uq0r6tgo.jpg',
    'https://i0.wp.com/wx4.sinaimg.cn/mw2000/006tMkIxgy1hqvuzwc4bsj30u00u0wko.jpg',
    'https://i0.wp.com/wx2.sinaimg.cn/thumb180/0082PBjgly1hqvs524n96j30qo1a2qb6.jpg'
]

images = [load_image(img_url) for img_url in image_urls]
response = pipe(('describe these images', images))
print(response)```

### Environment

```Shell
ys.platform: linux
Python: 3.10.14 | packaged by conda-forge | (main, Mar 20 2024, 12:45:18) [GCC 12.3.0]
CUDA available: True
MUSA available: False
numpy_random_seed: 2147483648
GPU 0,1,2,3,4,5,6,7: NVIDIA A100-SXM4-80GB
CUDA_HOME: /usr/local/cuda
NVCC: Cuda compilation tools, release 12.4, V12.4.131
GCC: gcc (Debian 10.2.1-6) 10.2.1 20210110
PyTorch: 2.2.2+cu121
PyTorch compiling details: PyTorch built with:
  - GCC 9.3
  - C++ Version: 201703
  - Intel(R) oneAPI Math Kernel Library Version 2022.2-Product Build 20220804 for Intel(R) 64 architecture applications
  - Intel(R) MKL-DNN v3.3.2 (Git Hash 2dc95a2ad0841e29db8b22fbccaf3e5da7992b01)
  - OpenMP 201511 (a.k.a. OpenMP 4.5)
  - LAPACK is enabled (usually provided by MKL)
  - NNPACK is enabled
  - CPU capability usage: AVX512
  - CUDA Runtime 12.1
  - NVCC architecture flags: -gencode;arch=compute_50,code=sm_50;-gencode;arch=compute_60,code=sm_60;-gencode;arch=compute_70,code=sm_70;-gencode;arch=compute_75,code=sm_75;-gencode;arch=compute_80,code=sm_80;-gencode;arch=compute_86,code=sm_86;-gencode;arch=compute_90,code=sm_90
  - CuDNN 8.9.2
  - Magma 2.6.1
  - Build settings: BLAS_INFO=mkl, BUILD_TYPE=Release, CUDA_VERSION=12.1, CUDNN_VERSION=8.9.2, CXX_COMPILER=/opt/rh/devtoolset-9/root/usr/bin/c++, CXX_FLAGS= -D_GLIBCXX_USE_CXX11_ABI=0 -fabi-version=11 -fvisibility-inlines-hidden -DUSE_PTHREADPOOL -DNDEBUG -DUSE_KINETO -DLIBKINETO_NOROCTRACER -DUSE_FBGEMM -DUSE_QNNPACK -DUSE_PYTORCH_QNNPACK -DUSE_XNNPACK -DSYMBOLICATE_MOBILE_DEBUG_HANDLE -O2 -fPIC -Wall -Wextra -Werror=return-type -Werror=non-virtual-dtor -Werror=bool-operation -Wnarrowing -Wno-missing-field-initializers -Wno-type-limits -Wno-array-bounds -Wno-unknown-pragmas -Wno-unused-parameter -Wno-unused-function -Wno-unused-result -Wno-strict-overflow -Wno-strict-aliasing -Wno-stringop-overflow -Wsuggest-override -Wno-psabi -Wno-error=pedantic -Wno-error=old-style-cast -Wno-missing-braces -fdiagnostics-color=always -faligned-new -Wno-unused-but-set-variable -Wno-maybe-uninitialized -fno-math-errno -fno-trapping-math -Werror=format -Wno-stringop-overflow, LAPACK_INFO=mkl, PERF_WITH_AVX=1, PERF_WITH_AVX2=1, PERF_WITH_AVX512=1, TORCH_VERSION=2.2.2, USE_CUDA=ON, USE_CUDNN=ON, USE_EXCEPTION_PTR=1, USE_GFLAGS=OFF, USE_GLOG=OFF, USE_MKL=ON, USE_MKLDNN=ON, USE_MPI=OFF, USE_NCCL=1, USE_NNPACK=ON, USE_OPENMP=ON, USE_ROCM=OFF, USE_ROCM_KERNEL_ASSERT=OFF,

TorchVision: 0.17.2+cu121
LMDeploy: 0.4.2+708e919
transformers: 4.41.2
gradio: Not Found
fastapi: 0.111.0
pydantic: 2.7.4
triton: 2.2.0

Error traceback
Response(text='1. 这张图片展示了一位女士站在一座山间的石阶上。她穿着一件黄色的外套，戴着墨镜，手持一根手杖，看起来像是在进行徒步旅行。背景中可以看到茂密的树木和岩石，给人一种宁静而自然的感觉。\n\n2. 这张图片是一盘食物。在盘子的中央是一块炸鸡块，旁边是一根玉米棒，还有几种蔬菜，包括豆角、洋葱和可能是蘑菇的食材。在盘子的旁边，有一双筷子放在盘子上。\n\n3. 这张图片展示了一个装有水果的碗。碗里装满了各种水果，包括苹果、蓝莓和桃子。水果的颜色鲜艳，看起来非常新鲜。\n\n4. 这张图片展示了一个装有液体的玻璃杯，可能是水或其他饮料。玻璃杯的设计非常独特，有着复杂的图案和装饰。\n\n5. 这张图片是一张风景照，拍摄的是山间的小路。小路蜿蜒曲折，两旁是郁郁葱葱的树木和植被。远处可以看到一座红色的建筑，可能是寺庙或亭子。整体上，这张图片给人一种宁静和自然的感觉。', generate_token_len=228, input_token_len=1835, session_id=0, finish_reason='stop', token_ids=[312, 281, 262, 72998, 68467, 69552, 89967, 72661, 70421, 73127, 60631, 71991, 60941, 61527, 60370, 60355, 60564, 71294, 70599, 80342, 74829, 60353, 84035, 61945, 61458, 60353, 81722, 73004, 60454, 63293, 60353, 69835, 60770, 68657, 68274, 87281, 70077, 60355, 68807, 60366, 69363, 62824, 83225, 77054, 60381, 75851, 60353, 80255, 79917, 60458, 68519, 69440, 60355, 402, 314, 281, 262, 72998, 68467, 68321, 60957, 68757, 60355, 60361, 60957, 68787, 68887, 68321, 61006, 61652, 82710, 60353, 70185, 68321, 60772, 69502, 61963, 60353, 68350, 71961, 69644, 60353, 68469, 76367, 60359, 70549, 60381, 69454, 73073, 60354, 68572, 60355, 60361, 60957, 68787, 70185, 60353, 68510, 60968, 71762, 68677, 60957, 71024, 60355, 402, 308, 281, 262, 72998, 68467, 69552, 68849, 80824, 69397, 60354, 61679, 60355, 74452, 60634, 75117, 68459, 69397, 60353, 68469, 68963, 60359, 81216, 60381, 86973, 60355, 69397, 71588, 79057, 60353, 69835, 68335, 70022, 60355, 402, 319, 281, 262, 72998, 68467, 69552, 68849, 80824, 61258, 69743, 69601, 61540, 60353, 69454, 60456, 76531, 71886, 60355, 69601, 61540, 71011, 68335, 70216, 60353, 69703, 75263, 70742, 60381, 69565, 60355, 402, 317, 281, 262, 72998, 68467, 68321, 60862, 70400, 60863, 60353, 69582, 68332, 60631, 60470, 68447, 60586, 60355, 60398, 60586, 91014, 83452, 60353, 60583, 61723, 60357, 62117, 62117, 61303, 61303, 60354, 77054, 60381, 88944, 60355, 81121, 69363, 73127, 74789, 68620, 60353, 69454, 82576, 60535, 62608, 60401, 60355, 69217, 60370, 60353, 72998, 68467, 80255, 79917, 60381, 68519, 69440, 60355], logprobs=None)

可以看一下InternVL置顶的issue，应该有解释。https://github.com/OpenGVLab/InternVL/issues
目前 的InternVL-Chat-V1-5 训练的时候应该是单图来训练的，所以多图能力并不强，他们说六月会出多图训练的模型，huggingface上面目前貌似还没有看到。

好的，感谢回复

authors: irexyc stay-leave

repo: InternLM/lmdeploy


text:
Remove subchapter on Versioning

The HTTPS Catalog Binding does not need an own chapter on the supported protocol versions, as https://github.com/International-Data-Spaces-Association/ids-specification/blob/main/common/common.binding.https.md explains it already.

Relates to #15


text:
Update CoExtendedAttributesController.php

The TIMESTAMP column does not work without DEFAULT in some recent versions of mysql. This causes a nasty, unexplained DB error in COmanage when attempting to create extended attributes.

Which version of MySQL does this patch apply to?
Unfortunately I don't think we can merge as is since prior to v5.6.5 MySQL does not allow multiple default current timestamps in the same table.
Server version: 5.5.52-0+deb8u1 (Debian)
mysql> create table test (id serial primary key,
                          created timestamp default current_timestamp,
                          modified timestamp default current_timestamp);
ERROR 1293 (HY000): Incorrect table definition; there can be only one TIMESTAMP column with CURRENT_TIMESTAMP in DEFAULT or ON UPDATE clause`

I am having difficulties reproducing the behaviour I originally detected. It probably was a MariaDB error, but I think I ran into it during provisioning on a platform I cannot recall at the moment. The code as it is seems to work fine on the platform I am currently using, so I am closing this PR.

authors: boshrin mheder muisit


text:
Governance Action: Treasury Withdrawal

The community discusses a proposal on the Cardano Forum from the SanchoTrust trustees to obtain 1,000,000 SanchoAda from the SanchoNet treasury
The community agrees that it wants to fund the proposal
A treasury withdrawal governance action is prepared that links to the discussions and moves 1,000,000 SanchoAda to the SanchoTrust address
The action is submitted on-chain on SanchoNet
The constitutional committee confirms the action is constitutional
DReps vote
If the action gets enough votes before the expiry date, it is ratified.
The treasury withdrawal happens immediately on ratification

Tests added.

repo: IntersectMBO/cardano-node-tests


text:
Make Unroll an open type family

This PR contains an alternative approach to un-rolling AsData-types: it uses an open type family for it.
This has its own pro:

Users are free to specify how to unroll any type (including custom AsData types)
by provinding a TF instance, for example:
type instance Unroll AsDataFoo = '[AsDataFoo, Bool, Integer]

and con:

There is no default un-rolling of generic types, instead users need to instantiate the Unroll TF for every custom data type:
type instance Unroll MyGenericFoo = GenericUnroll Foo

Decided not to implement it.

repo: IntersectMBO/plutus


text:
NotReadableException in AbstractDecoder.php line 302: Image source not readable

Hello Intervention.
While using the intervention Library, I find an error and leave an issue.
This is my error
NotReadableException in AbstractDecoder.php line 302: Image source not readable
This is my stack trace

NotReadableException in AbstractDecoder.php line 302:
Image source not readable
in AbstractDecoder.php line 302
at AbstractDecoder->init('http://macaron.dev/img/event/8/data/기부%20조심.jpg') in AbstractDriver.php line 64
at AbstractDriver->init('http://macaron.dev/img/event/8/data/기부%20조심.jpg') in ImageManager.php line 50
at ImageManager->make('http://macaron.dev/img/event/8/data/기부%20조심.jpg') in Facade.php line 237
at Facade::__callStatic('make', array('http://macaron.dev/img/event/8/data/기부%20조심.jpg')) in EventController.php line 69
at EventController->boilerPlate('34')

However, the URL shown in error has not been proved wrong.

Please check this situation.
Thank you and sorry for my poor english.

Reading remote images via HTTP is sometimes problematic with Intervention Image. Especially with korean characters.
See https://github.com/Intervention/image/issues/558 or https://github.com/Intervention/image/issues/438.

authors: endlessdev olivervogel

repo: Intervention/image


text:
Animated Gif Resize

Hi guys like everyone, I had the problem of resizing an animated gif image.
Doing some research I found a class that does a good job, tested and resizes gifs without losing animation.
Place the link
http://www.tahapaksu.com/2012/02/php-gif-resizer/
Maybe you can integrate it

This feature is now available in version 3.

authors: olivervogel sergioxdev


text:
trim(): specify which colors to trim

Currently the first parameter $base is a string that could be: top-left (default), bottom-right or transparent as the doc: trim().
There some way to trim by color? In my case, I need trim transparent and/or white color, only. Eg.: trim([ 'transparent', 'white', '#FF0000']) to trim transparent, white and red. The problem is that first parameter is string.

The trim() function is part of Intervention Image 2, which has reached the end of life status. The successor version 3 unfortunately no longer supports this function.
The reasons for this can be found here: https://github.com/Intervention/image/issues/1239
However, your idea sounds interesting and will be considered in the event of a new integration of trim().

authors: olivervogel rentalhost


text:
feat: token authentification

Implemented the authentification option for static tokens, normal token after login have priority!
Types of changes

[ ] Bug fix (a non-breaking change which fixes an issue)
[x] New feature (a non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes (if not applicable, please state why)

Will close #31
And answer the newest discussion #51
@craigharman @mklueh

@Intevel after cursing Directus's permission model and creating dozens of users / roles for two hours while testing on the master branch I finally realized that I was on the wrong branch and can confirm now, that it is working 😊

Thanks for your time 😂

I will merge & release it tomorrow.

@Intevel thank you for your effort ;)

Thanks!

authors: Intevel mklueh vanling

repo: Intevel/nuxt-directus


text:
check standard data file when initializing EyeLink

Right now the default file gets move to the indicated target location and name after the session is complete. However, we don't know what happens if the default file already exists. An existing file could be overwritten by the new file, which might mean a loss of data. It could also be that the new data file gets saved under a different name, but then the old file would get moved to the target location. This would mean we get the data messed up.
It would be good to at least check if the standard data file already exists when initializing the EyeLink, and issue a warning (with a pause) so that the experimenter can do what is necessary.
Alternatively, we could move, rename or even delete it in some predictable way. Here is a suggestion. We make a folder to move such pre-existing default files into, and we rename them with the date and time added. That way no data gets lost, and we know the file is from some session before that date and time. Most probably the immediately preceding one.

This is more a solution for the target file issue I also raised, but this is exactly what I meant there. Since it works on your end: mind if I copy this code into the eye-tracker object? Will prevent potential issues for both the EyeLink and the LiveTrack side of things.
In the mean time, the standard data file "et_data.EDF" in the working directory might also exist, and this could cause trouble on your end, since it's EyeLink specific. This could also be solved in the eye-tracker object in some predictable, data-loss-preventing way. Could also be left to your version of the experiments. I'm open to whatever.

Yes I got mixed up, for this I guess it doesn't hurt to check, if a file already exists it implies that something went very wrong in the previous run so that could at least raise a warning and move it somewhere so it's not overwritten (that's what happens with edf files).

OK, neither should take long to implement. Especially the one you already solved.

Added some lines for the default EyeLink file as well, on initialization. Lines 490-498 right now.
Check if this works? And is useful?

Tried to run my testing script after putting a default edf file in the directory, it works.

authors: ClementAbb thartbm


text:
🛑 ppmprosjekt.no is down

In 8053b10, ppmprosjekt.no (https://ppmprosjekt.no) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ppmprosjekt.no is back up in 4349b83 after 22 minutes.

repo: Intus-AS/Types-status


text:
🛑 intus.no is down

In 7d9018c, intus.no (https://intus.no) was down:

HTTP code: 0
Response time: 0 ms

Resolved: intus.no is back up in 7d6087c after 23 minutes.


text:
🛑 mus.as is down

In 619f01d, mus.as (https://mus.as) was down:

HTTP code: 0
Response time: 0 ms

Resolved: mus.as is back up in 2b9ba33 after 31 minutes.


text:
🛑 utpaasjoen.no is down

In 40a5d60, utpaasjoen.no (https://utpaasjoen.no) was down:

HTTP code: 0
Response time: 0 ms

Resolved: utpaasjoen.no is back up in 0e65f5f after 17 minutes.


text:
🛑 all-ror.no is down

In 0263421, all-ror.no (https://all-ror.no) was down:

HTTP code: 0
Response time: 0 ms

Resolved: all-ror.no is back up in 27f2e1f after 35 minutes.


text:
🛑 smålandbåtforening.no is down

In 64931c5, smålandbåtforening.no (https://smålandbåtforening.no) was down:

HTTP code: 0
Response time: 0 ms

Resolved: smålandbåtforening.no is back up in b954b47 after 30 minutes.


text:
Maximum force does not read correctly

OUTCAR.txt
POSCAR.txt
I think cgrad gives the correct force:
   1 Energy:-1268.30125  Log|dE|: 3.1  SCF: 51  Avf|F|: 0.048  Max|F|: 0.151  AtomInd:128z  Time: 48.67
   2 Energy:-1268.30533  Log|dE|:-2.4  SCF:  6  Avf|F|: 0.036  Max|F|: 0.215  AtomInd:132z  Time:  4.99
   3 Energy:-1268.30507  Log|dE|:-3.6  SCF: 10  Avf|F|: 0.041  Max|F|: 0.287  AtomInd:132z  Time:  8.26
   4 Energy:-1268.30770  Log|dE|:-2.6  SCF:  9  Avf|F|: 0.036  Max|F|: 0.123  AtomInd: 84z  Time:  7.05
   5 Energy:-1268.31102  Log|dE|:-2.5  SCF:  6  Avf|F|: 0.045  Max|F|: 0.168  AtomInd:138x  Time:  5.20

I wrote a quick script to verify this:
     1  -1268.23086765  10)      0.151413
     2  -1268.23502776  13)      0.214847
     3  -1268.23461562  14)      0.286599
     4  -1268.23711316  14)      0.122645
     5  -1268.23991888  9)       0.168318

This is the results from rsgrad rlx:
  #Step  TOTEN_z/eV LgdE   Fmax #SCF Time/m Mag/muB
      1 -1268.23087  3.1  0.071   51  50.06   NoMag
      2 -1268.23503 -2.4  0.034    6   6.10   NoMag
      3 -1268.23462 -3.4  0.048   10   9.37   NoMag
      4 -1268.23711 -2.6  0.059    9   8.16   NoMag
      5 -1268.23992 -2.6  0.081    6   6.31   NoMag

This is a rsgrad bug raised by the incorrect nions:
Here
https://github.com/Ionizing/rsgrad/blob/0eb3249dff9557cf3715eb50a95598ea42c4d50e/src/vasp_parsers/outcar.rs#L763
let len = self._data.len();
let dynamics = self._constraints.as_ref()
                   .unwrap_or(&vec![[true; 3]; len])
...

should be
let len = self._data[0].positions.len();
let dynamics = self._constraints.as_ref()
                    .unwrap_or(&vec![[true; 3]; len])
                    .iter()
...

Patch with the modification above, the rsgrad should produces correct Fmax information.
[2024-08-02T03:53:15Z INFO  rsgrad::commands::rlx] Parsing file "/Users/ionizing/Downloads/OUTCAR (1).txt" and "./POSCAR"
[2024-08-02T03:53:15Z WARN  rsgrad::commands::rlx] Reading constraints from POSCAR file "./POSCAR" failed
  #Step  TOTEN_z/eV LgdE   Fmax #SCF Time/m Mag/muB
      1 -1268.23087  3.1  0.151   51  50.06   NoMag
      2 -1268.23503 -2.4  0.215    6   6.10   NoMag
      3 -1268.23462 -3.4  0.287   10   9.37   NoMag
      4 -1268.23711 -2.6  0.123    9   8.16   NoMag
      5 -1268.23992 -2.6  0.168    6   6.31   NoMag
      6 -1268.24152 -2.8  0.109   11  10.26   NoMag
      7 -1268.24196 -3.4  0.124   15  12.90   NoMag
      8 -1268.24466 -2.6  0.118   11   9.64   NoMag
      9 -1268.24572 -3.0  0.208    7   7.07   NoMag
     10 -1268.24759 -2.7  0.109   10   9.49   NoMag
     11 -1268.24785 -3.6  0.150   10   9.88   NoMag
     12 -1268.25007 -2.7  0.088   13  11.87   NoMag
     13 -1268.25065 -3.2  0.200   14  12.22   NoMag
     14 -1268.25239 -2.8  0.080   14  12.14   NoMag
     15 -1268.25229 -4.0  0.134    9   8.08   NoMag
     16 -1268.25568 -2.5  0.096    6   6.26   NoMag
     17 -1268.25506 -3.2  0.105   10   9.30   NoMag
     18 -1268.25517 -3.9  0.210   10   9.14   NoMag
     19 -1268.25636 -2.9  0.145   15  12.85   NoMag
[2024-08-02T03:53:15Z INFO  rsgrad] Time used: 7.594309ms

Fixed via 7a0d159964d2b3c950c06723ea73e908248d2024

repo: Ionizing/rsgrad


text:
Validate initcode size

As mentioned in #32, there is now a limit on initialization code size in addition to deployed code size.  Initialization code size is also exposed in the compilation artifacts, so the plugin could (optionally?) also validate initialization code size.
See here: https://eips.ethereum.org/EIPS/eip-3860#parameters

Personally I'd just throw it in a 3rd column. I don't think it's at the point of information overload yet. Happy to help contribute.

Done!
https://github.com/ItsNickBarry/hardhat-contract-sizer/pull/36

authors: ItsNickBarry RyanRHall

repo: ItsNickBarry/hardhat-contract-sizer


text:
Move IPPICV binaries to GitHub opencv_3rdparty repository

3rdparty repo scripts: https://github.com/Itseez/opencv_3rdparty/pull/3

:+1:

authors: alalek vpisarev

repo: Itseez/opencv


text:
App is stuck

Hello thank you so much for great plugin
 let controller = UIViewController()
        controller.transitioningDelegate = SPStorkTransitioningDelegate()
        controller.modalPresentationStyle = .custom
        present(controller, animated: true, completion: nil)

controller.transitioningDelegate = SPStorkTransitioningDelegate(): Instance will be immediately deallocated because property 'transitioningDelegate' is 'weak'
I got app stuck when using this code
thank you

Hi! Thanks for your feedback.
It is not correct. SPStorkTransitioningDelegate  deist only after close controller. You can add code:
deinit {
        print("here")
    }

in SPStorkTransitioningDelegate and see result.
I am close your issue

Hi,
Any example in programmatically ?
thank you

repo: IvanVorobei/SPStorkController


text:
Snapshot frame width

Hello Ivan. I was looking at Apple Music card UI and noticed that the snapshot card frame is wider than SPStorkController and I think it looks better this way. Can I make the frame wider or can you update it and make it wider liker Apple Music please?

I recently noticed this too.  I think this has been changed in recent updates.  Yes, I plan to do the same.

Thank you!

I am upload new version 1.6.2 for this future. You can update and see it. Thanks!

Thank you Ivan, I see it on multiple Simulator devices and It looks better now, but I have iPhone 5s real device and the frame still the same as the old version.

After pod update need clean project.

Okay let me try.

Yes it works now, thanks so much!

authors: IvanVorobei fawzirifai


text:
keyboard enhancements

When creating an new item keyboard should pop up automatically. At the moment I have to touch on "Artikel" (I'm from germany).
The same applies to when I want to modify the count value for an item on the list. At the moment I have to touch on the "number" to get the keyboard. Keyboard should pop up automatically AND the current value should be preselected, so when I enter "2" I get "2". At the moment I get "12" because cursor is behind the current value.

Morgen!
Thanks for you feedback!
And I, as well as several others, agree that the current behavior is not very elegant.

Done! Thanks!


text:
Adding profile.md

Just adding a profile.md file.

I have created a branch, created a file, and made a commit.

repo: J-Reece/introduction-to-github


text:
Modulo push

[ ] git push :  Se utiliza para enviar commits del repositorio local a repositorios remotos

Utilizara canales por sockets que simplemente tendran permitido modificar commits, por ende push solo trae commits y hace el merge


text:
feature request: tailwind support

I think we should ask if the user wants to setup their frontend app with tailwind or not

@Judge-Paul this feature is already being worked on . check issue #24

authors: JC-Coder Judge-Paul

repo: JC-Coder/startease


text:
Bugfix for Soca2Cice (don't search when there's nothing to be found)

Description
Soca2Cice shuffle option is failing on develop with high res (https://github.com/JCSDA-internal/soca/issues/1050). This happens when KD tree search is performed on a stencil that has no background points with ice. In this case there is nothing to search from, and the accessor to the first element of an empty array fails:
https://github.com/JCSDA-internal/soca/blob/116c20eb94015ee31a480765343731ad4af77de0/src/soca/VariableChange/Soca2Cice/soca_soca2cice_mod.F90#L237
When this happens on develop, it often (always for my particular run) happens when analysis has veeeery small ice concentration (e.g. 4.72E-174, 9.97E-052…). I don’t think we care!
This PR fixes this problem by:

skipping the search if there are no ice points in the background.
making ice concentration analysis below arbitrary 1e-4 look like no ice. I’m happy to change to something else or make yaml configurable.

Issue(s) addressed

fixes https://github.com/JCSDA-internal/soca/issues/1050

Testing

Tested with gdasapp high-res tests by turning on "shuffle" option (orion + intel), run fails on develop and succeeds with this fix.
Ran soca tests with icepack (orion + gnu). The reference slightly changed because now the few previously very low ice concentration points are zeros.

@guillaumevernieres good idea! I didn't find anything in icepack (min thickness is 0.01m for thermodynamics); cice seems to have 0.001 min ice concentration for computing velocities: https://github.com/NOAA-EMC/CICE/blob/513f8d153924e18ae0f91f5440195d15210a489e/doc/source/cice_index.rst#L30

I've pushed an update and verified that soca test is passing. I'll rerun the high-res experiment for sanity check (I'm pretty sure it works with just the remaining change), and report back.

I can test highres on Discover if necessary
What is the purpose of the shuffle option?

I can test highres on Discover if necessary
What is the purpose of the shuffle option?

add seaice where the analysis has ice but the background has none.

add seaice where the analysis has ice but the background has none.

more precisely, shuffle in* seaice where analysis has ice, and background's ice is smaller than seaice edge in yaml.
*replace by sea ice background state from one of the nearby gridpoints that has total ice concentration closest to what analysis should be.

I can test highres on Discover if necessary

that would be great, thank you! I just lost my setup.

Confirming that gdasapp high res case runs with the shuffle option on and the updated fix.

This is not related to this PR (more towards Anna's the previous PR) but could there be applications where arctic and antarctic domains for soca2cice used separately?

Maybe regional?

This is not related to this PR (more towards Anna's the previous PR) but could there be applications where arctic and antarctic domains for soca2cice used separately?

Maybe regional?

Right but when I accidentally didn't have the antarctic section as well as arctic in the yaml it failed. Maybe I had other issues so I can test again.

authors: Dooruk guillaumevernieres shlyaeva

repo: JCSDA-internal/soca


text:
JSON support for settings

Podpora JSONu v hodnotách jednotlivých options v nastavení.

Pokud bude rozpoznán v hodnotě JSON, dekóduje jej jako stdClass (struktura) nebo array (pole)
Pokud bude součástí hodnoty pole, asociativní pole nebo stdClass či array, bude podle toho zakódován jako JSON string.

Nakonec nebude řešeno jako JSON. Otevřená nová issue #56 která přichází s jiným řešením.

repo: JDCofficial/songator


text:
表格生成器支持复制某列功能

Describe the solution you'd like
表格生成器支持复制某列功能，并可以导出该列配置数据。ots about the feature request here.

repo: JDFED/drip-table


text:
bug report Code text block App UI

when AI like Phi3 generating a code block it has cannot word wrap
therefore some of code text is hidden.

I will investigate the issue, but it could take a while. I'm currently not at my main coding setup. Could you provide a screenshot as an example?

And you're not able to scroll, right? If so I'll look into it

And you're not able to scroll, right?

yes, i cannot

Hi there, sorry that it took a while. I investigated and found the issue.
As described in this issue, the drawer does not pass scrolls to below widgets. We'll have to wait for a fix for the problem.
In the meantime, I implemented a small fix. Could you try if scrolling works in this build ollama.zip after enabling the fix in interface settings?

horizontal scroll still not work
same problem

Did you enable the fix in settings?

oh i enabled fixed thank you

but a bad UI when i try to select text from AI response
it show me new pop windows

If you don't like it you can add a better solution yourself and contribute to the project

i have very good idea for selecting ui in chat
a think like last version of Telegram Messenger
in this idea you can select multi message for delete copy or select part of message
and a button top of code block to copy just all codes in block not all textbot message

when typing message:

when sent message:

This is a new issue, feel free to open a new one if needed


text:
Right-click doesn't work in LabVIEW 2014

In LabVIEW 2014 (14.0.1) 32bit:

Right-click doesn't open the SM editor UI, although CTRL+SPACE -> CTRL+J does open it and it is functional.
Right-click seem to be "disabled" for all functions of the SM editor, for example for the "find data accessors".

How does it work under the hood? What should I check to help you and to find the cause or a workaround?

Hi, you’re right. The right click menus only work in LabVIEW 2015 or
greater. That’s a known issue and nothing we can do about it. Thanks.
Jim Sent from my mobile.

The only solution is to upgrade to LabVIEW 2015 or greater. Sorry.
Jim Sent from my mobile.

authors: jimkring kombela

repo: JKISoftware/JKI-State-Machine-Editor


text:
chore: let CI run on all Node LTS versions

This PR replaces Node 15 with Node 16 for the tests in the CI pipeline.
The pipeline has to be updated again at the end of this month, when Node 12 reaches EOL status.

Pull Request Test Coverage Report for Build 2180654457

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 80.769%

Totals

Change from base Build 2180649685:
0.0%

Covered Lines:
145

Relevant Lines:
172

💛  - Coveralls

authors: JKRhb coveralls

repo: JKRhb/node-red-contrib-coap


text:
Installing files in a pacman fakeroot environment fails without access to '/usr/local'

The package in the AUR fails to build because the Makefile tries to install it in the real filesystem root. When building pacman packages, a fakeroot is created so the files owned by the package can be placed in the filesystem properly.
I pushed a patch upstream to the AUR so the package builds properly. Here's the patch currently in upstream:
diff --git a/Makefile b/Makefile
index 6e25cbf..cc4f066 100644
--- a/Makefile
+++ b/Makefile
@@ -14,8 +14,8 @@ all:

 install:
 	mkdir -p "$(DESTDIR)$(PREFIX)/bin"
-	install $(__NAME__) "/usr/local/bin/$(__NAME__)"
-	install $(__NAME_C__) "/usr/local/bin/$(__NAME_C__)"
+	install $(__NAME__) "$(DESTDIR)/usr/local/bin/$(__NAME__)"
+	install $(__NAME_C__) "$(DESTDIR)/usr/local/bin/$(__NAME_C__)"
 	cd ./man; $(MAKE) install

 clean:

This looks good to me and successfully builds locally. Go ahead and open a pull request and I can merge.

That's why I opened the issue. I know it breaks the workflow, but I prefer not doing pull requests if I don't have to.

Ok. I'll make the changes. Thanks for doing this.

I noticed that you reverted the change. Was there some sort of issue?

Ah yes I was going to ping you about this soon. The package builds with the patch so long as I don't change the Makefile. Making the changes here cause the build to fail, however.

I'll keep the patch upstream in the AUR for now. This'll be on my #TODO when the issue occurs again.

Hi! Trying to make a package for crux but the problem is the same, I can't use the fakeroot to build the package and the patch is not working... Is possible to change the make file to use fakeroot?
Thanks!

Hi! Trying to make a package for crux but the problem is the same, I can't use the fakeroot to build the package and the patch is not working... Is possible to change the make file to use fakeroot?
Thanks

@jolupa  The patch I have above worked for JLErvin for a little while, but had to go back to his previous version because there were build errors.
The patch above suggests using an environment variable during build, in which you set the fakeroot to the current folder. In your PKGBUILD's  build() function, suffix the call to make (or whatever) with DESTDIR="$pkgdir" and make sure it's present in the Makefile like above.

@FlashDaggerX Oh! thank you that worked!
But I think that needs to be some easy way of doing the install in a fakeroot for packages building.
Thanks.

@jolupa if the included makefile were like the one that @FlashDaggerX included above, does the build work?

@JLErvin Yeah! it worked perfectly... In a few minutes I will try it to see if it works!
Thanks.

Ok I'll push a commit that changes the default Makefile to the one above. I believe that the patch breaks if we use the new makefile instead of the old one. Once I push, can you remove the patch? @FlashDaggerX

Will do. Something is bothering me though, because this wasn't happening a few weeks ago. I can't find any significant changes to your makefile, so something must've changed on Arch's side.

Not relevant in current master (83dfb3d), will open once it occurs again.

authors: FlashDaggerX JLErvin jolupa

repo: JLErvin/berry


text:
Add album image in search bar

Thank you so much @Bhacaz!

authors: Bhacaz JMPerez

repo: JMPerez/c


text:
Adds the Couchbase link as Database supported in the site

We need to add the couchbase logo as a database that we have support.
http://couchdb.apache.org/

done

authors: andresgalante otaviojava


text:
Use an ARP override when sending unicast WoL packets

This PR contains two changes:

The first commit implements the solution discussed in #19, where we add a system-wide ARP table override to ensure Unicast WoL packets can be sent even if the TV is not responding to ARP requests.
The second commit starts from the assumption that this new mechanism makes Unicast inherently more reliable than broadcast in most cases, and updates defaults and docs accordingly.

Arguably this is more controversial so feel free to drop this commit if you think it's going too far.

Thanks Etienne, nice clean code! Agree with the theoretical plausibility this is the best default mode


text:
private vs. protected in visitor / deparser

Is there a reason why deparsers and the buffer are private in the visitor and deparser classes?
Shouldn't they be protected instead?
For example, I would like to insert some extra output during Insert statement deparsing.
But the StatementDeParser class defines its members as:
public class StatementDeParser implements StatementVisitor {
private ExpressionDeParser expressionDeParser;
private SelectDeParser selectDeParser;
private StringBuilder buffer;
The InsertDeParser defines these members similarly.
If I try to write
@Override
public void visit(Insert insert) {
buffer.append("-- an insert statement");
...
}
I get an error saying that buffer is private.
There is a getBuffer method, but using it makes the code cumbersome.
There is no get method for expressionDeParser or selectDeParser, so its much harder
to write code which accesses or manipulates these members.
The value of the visitor and deparser framework would seem to be the ability to modify
selected parts of the deparsing by subclassing and overridding selected methods.
Since these classes are supposed to be subclassed, shouldn't important member variables
be protected instead of private?

The deparsers are unfortunately the way to go here. A better way to manipulate the syntax tree is to use the visitor adapter classes. But they contain far less visit logic (at the moment).

The example I wrote has the effect of inserting a comment, and then would access the deparser.
But the deparser is written similarly:
public class InsertDeParser implements ItemsListVisitor {
private StringBuilder buffer;
private ExpressionVisitor expressionVisitor;
private SelectVisitor selectVisitor;
I'm asking if these member fields are intentionally private,
or if perhaps they can be made protected?
(I did see the src/main/java/net/sf/jsqlparser/util/SelectUtils.java and other examples).

ExpressionDeParser and SelectDeParser has a getBuffer method.
I dont know if private or protected is better. Nevertheless I switched to protected.

authors: ted-johnson wumpz

repo: JSQLParser/JSqlParser