text:
Fix/daef 467 Fix all features eslint warnings

This PR introduces a fix for all features eslint warnings.
In this PR a new and working wallet-default.key is injected.
TODO:

[ ] Inspect one failing acceptance-test scenario: Scenario: User Sends Money from wallet with spending password to Receiver

Reviewing this now …

Merging this now as the travis PR CI was successful

authors: DominikGuzei tomothespian

repo: input-output-hk/daedalus


text:
Update index-state and nix updates

description
Update index-state and nix changes necessary for nix-build.
checklist

[x] compiles (cabal v2-build or stack build)
[x] tests run successfully (cabal v2-test or stack test)
[ ] documentation added
[ ] link to an issue
[ ] add milestone (the current sprint)

bors r+

bors r+

bors merge

bors merge

bors merge

bors merge

source: gharchive/pull-request

authors: CodiePP newhoggy

license_type: permissive

license_source: github-api


text:
GMC-253 vm healthcheck

https://iohk.myjetbrains.com/youtrack/issue/GMC-253

I have tested the following configurations:

Mantis VM

Internal
External

When running, healtheck is OK
When not running, healthcheck is ERROR

IELE VM, external (the only possible configuration)

When running, healthecke is OK
When not running, healthcheck is ERROR

Erroneous healtchcheck responses are in the form of:
    {
      "description":"virtualMachine",
      "status":"ERROR",
      "error":"Tcp command [Connect(localhost:8888,None,List(),None,true)] failed",
      "meta":{
        "type":"StreamTcpException"
      }
    },

I have not checked KEVM.
This looks good in general. We still need to take into account the case where the VM is executing a slow operation and will not be able to complete the healthcheck fast (e.g. IELE and KEVM cannot run more than one operation in parallel).

authors: loverdos pslaski

repo: input-output-hk/mantis-cardano

license: MIT


text:
Implement singleEraTransition for Shelley

Related to #2452.

For documentation of this update process, see https://github.com/input-output-hk/ouroboros-network/pull/1741/

In order to avoid the same problem that we had with Byron (#2455), we could take the following approach:

Blocks that came in within an epoch after the 4k/f voting deadline are not relevant.
Since there are gaps between blocks, we are probably only sure that there will be no more relevant block when we have seen the first block after the deadline.
If we count how many blocks we have seen post deadline, and we have reached k of them, we know that that last pre-* deadline block won't be rolled back anymore.
At this point we can look at the ledger state and see which proposals we accepted in the voting period, if any, and notify the HFC is one of them indicates a transition.

source: gharchive/issue

authors: edsko mrBliss

repo: input-output-hk/ouroboros-network


text:
p2p governor test improvements

Various improvements to the QC tests for the p2p governor:

Fix a bug in the shrinker for the governor mock environment. This was causing the shrinking of test cases to fail to terminate.
Add simple shrinker tests to catch (most instances of) this class of shrinker bug.
Improve the shrinker for scripts. This makes shrinking typically take fewer steps, and is hence typically quicker.
Tweak the script generator so we get a wider range of script lengths.
Change the strategy for the "pick scripts" to pick elements, not offsets, for better shrinker behaviour
Restructure the main governor tests.
Misc minor simplifications, and code clean-ups
A new (hopefully improved) livelock property test. In fact we split it into two: a basic no-livelock test, and a more sophisticated "no excessive busyness" test.

This PR was merged to p2p-master then it landed in master.

authors: coot dcoutts


text:
Add instance MonadThrow and MonadCatch for STM

Note that we already have MonadThrow for the Sim's STM, but not MonadCatch.
So the idea is you just requite a MonadThrow constraints for your use of STM m, but that we don't add throwSTM directly to the MonadSTM class. Clear as mud?

bors r+

authors: dcoutts mrBliss


text:
feat: move partner chains session pallet from polkadot-sdk fork

Description
Changes:

depends on polkadot-sdk with removed partner chains session and grandpa modifications
moved the partner-chains-session
NOT moved sp-partner-chains-session, because it was only providing CurrentSessionIndex that was only used by modified grandpa, so it was not used anymore
added pallet-session-runtime-stub and used it in runtime wiring - this is the new code and area where I need your critique the most

Checklist

[x] Commit sequence broadly makes sense and commits have useful messages.
~- [ ] New tests are added if needed and existing tests are updated.~ Only moved meaningful code.
~- [ ] Relevant logging and metrics added~
[x] CI passes. See note on CI.
~- [ ] Any changes are noted in the changelog.md for affected crate ~ - I'll update global changelog when the code is approved
[x] Self-reviewed the diff

@mpskowron @AmbientTea Thanks for review. I'll keep this PR open for now.
I have to prepare migration and test it. When it is done, then I'll merge this and open a small one with migration only.

Migration was unnecessary.

repo: input-output-hk/partner-chains


text:
Migration to Stack 2

Based on #1 by @qrilka, but I cannot push commits on that branch.
Seems to work!

My bad, I wanted to make the PR to my own repo: https://github.com/nh2/stack2nix/pull/2
@domenkozar Do you think you could transfer stack2nix to me?

@nh2 I don't have permissions for that. @disassembler


text:
Add a standard icon for notification

Pass a standard icon name to notify-send so the notification popup looks nicer.

I'm on the fence about this.  It seems like a good idea for graphical notification managers, but I think that libnotify spams /var/log/messaes with silliness when you use this kind of thing with dunst (which doesn't support icons, to my knowledge).  In any case, can you rebase your changes on current master and then we can play with it?

Rebased.
I am not aware of the dunst log spam issue but isn't that a separate problem about a notification server not properly handling arguments passed to notify-send? From gcalcli's point of view, you would want to present an attractive as possible interface.
Looks like dunst does support icons - from the dunst FAQ:
Icons are too big

Since the 1.2 version release, an option max_icon_size was introduced to scale down icons to a certain size. By default this option is set to 0 (it doesn’t scale down icons), to change this behaviour you need to set this option in the global section of the config file. For reference, check out the dunstrc config example file

Assuming you're OK with moving ahead with this, we probably should use a standard icon name from https://standards.freedesktop.org/icon-naming-spec/icon-naming-spec-latest.html such as appointment-soon.

I think you're right on all accounts, including the idea that we should try to follow any in-place standards.  Do you want to push another commit with appointment-soon instead of view-calendar-upcoming-events?  I haven't looked at the standards but I assume that you have.  I'm fine to merge this as is if view-calendar-upcoming-events is the preferred name.

I've changed the icon and squashed the commits.

LGTM.  Thanks!

authors: jcrowgey peterhoeg

repo: insanum/gcalcli


text:
High CPU utilization when stream disconnects

I have FFmpeg input and a module (#687). When I launch the bundle with:
docker compose -f samples/mjpeg_usb_cam/docker-compose.l4t.yml up usb-cam
[+] Running 2/0
 ✔ Container mjpeg_usb_cam-module-1   Running
 ✔ Container mjpeg_usb_cam-usb-cam-1  Created                                                                                Attaching to usb-cam-1

everything works normally, but when I stop the usb-cam, remaining module starts consuming a full core.

If start the source again, utilization drops to normal:
docker compose -f samples/mjpeg_usb_cam/docker-compose.l4t.yml up usb-cam

Looks like nvstreammux constantly aquiring and releasing buffer
0:01:08.011178000     1 0x7fe42407f4c0 LOG               bufferpool gstbufferpool.c:1134:default_acquire_buffer:<nvstreammuxbufferpool0> acquired buffer 0x7fe4342e36c0
0:01:08.011181888     1 0x7fe42407f4c0 TRACE        GST_REFCOUNTING gstobject.c:237:gst_object_ref:<nvstreammuxbufferpool0> 0x7fe4342e3990 ref 1->2
0:01:08.011190754     1 0x7fe42407f4c0 DEBUG             GST_BUFFER gstbuffer.c:2316:gst_buffer_add_meta: alloc metadata 0x7fe40a57a810 (NvDsMeta) of size 72
0:01:08.011195223     1 0x7fe42407f4c0 LOG               GST_BUFFER gstbuffer.c:1837:gst_buffer_map_range: buffer 0x7fe4342e36c0, idx 0, length -1, flags 0001
0:01:08.011198268     1 0x7fe42407f4c0 LOG               GST_BUFFER gstbuffer.c:305:_get_merged_memory: buffer 0x7fe4342e36c0, idx 0, length 1
0:01:08.011201735     1 0x7fe42407f4c0 TRACE        GST_REFCOUNTING gstminiobject.c:478:gst_mini_object_ref: 0x7fe43c019550 ref 1->2
0:01:08.011205903     1 0x7fe42407f4c0 TRACE            GST_LOCKING gstminiobject.c:233:gst_mini_object_lock: lock 0x7fe43c019550: state 00010000, access_mode 1
0:01:08.011210672     1 0x7fe42407f4c0 TRACE            GST_LOCKING gstminiobject.c:293:gst_mini_object_unlock: unlock 0x7fe43c019550: state 00010101, access_mode 1
0:01:08.011214248     1 0x7fe42407f4c0 TRACE        GST_REFCOUNTING gstminiobject.c:660:gst_mini_object_unref: 0x7fe43c019550 unref 2->1
0:01:08.011217054     1 0x7fe42407f4c0 TRACE        GST_REFCOUNTING gstminiobject.c:660:gst_mini_object_unref: 0x7fe4342e36c0 unref 1->0
0:01:08.011219929     1 0x7fe42407f4c0 TRACE        GST_REFCOUNTING gstminiobject.c:478:gst_mini_object_ref: 0x7fe4342e36c0 ref 0->1
0:01:08.011223255     1 0x7fe42407f4c0 LOG               GST_BUFFER gstbuffer.c:765:_gst_buffer_dispose: release 0x7fe4342e36c0 to pool 0x7fe4342e3990
0:01:08.011227934     1 0x7fe42407f4c0 LOG               GST_BUFFER gstbuffer.c:1694:gst_buffer_resize_range: trim 0x7fe4342e36c0 0-64 size:64 offs:0 max:64
0:01:08.011232302     1 0x7fe42407f4c0 DEBUG             GST_BUFFER gstbuffer.c:2514:gst_buffer_foreach_meta: remove metadata 0x7fe40a57a810 (NvDsMeta)
0:01:08.011238113     1 0x7fe42407f4c0 LOG               bufferpool gstbufferpool.c:1307:default_release_buffer:<nvstreammuxbufferpool0> released buffer 0x7fe4342e36c0 0
0:01:08.011242351     1 0x7fe42407f4c0 DEBUG             GST_BUFFER gstbuffer.c:1470:gst_buffer_is_memory_range_writable: idx 0, length -1
0:01:08.011247150     1 0x7fe42407f4c0 TRACE        GST_REFCOUNTING gstobject.c:264:gst_object_unref:<nvstreammuxbufferpool0> 0x7fe4342e3990 unref 2->1
0:01:08.011251849     1 0x7fe42407f4c0 LOG               bufferpool gstbufferpool.c:1134:default_acquire_buffer:<nvstreammuxbufferpool0> acquired buffer 0x7fe4342e3480

Posted a bug on Nvidia forum.

authors: bwsw tomskikh

repo: insight-platform/Savant


text:
NOISSUE: try to optimize send message

- What I did
Increased performance of watermill message sending a little bit. I got 10 -> 14 resp/s increase for benchmark on my lame notebook. Benchmark configuration: 5 discovery nodes, info log level, bench -c 10 -r 100.
- How I did it

Removed extra serialization/deserialization calls;
Replaced gob with protobuf serialization.

- How to verify it
Run unit & integration tests and benchmark

I'm going to merge this after tests are passed #3060

TestMessageBus_SendTarget looks a little bit senseless since both Payload and Metadata of the message are mutated in wrapMeta

TestMessageBus_SendTarget looks a little bit senseless since both Payload and Metadata of the message are mutated in wrapMeta

authors: dmitry-panchenko krestkrest

repo: insolar/insolar


text:
Fixed crash on firstResponder search

Hello
In apps first responder is not always viewController (e.g. it could be an UIApplication object). So an explicit typecast causes problems and crashes our application. Have a look on fix

Sounds good, thanks

repo: inspace-io/INSPullToRefresh

license: mit

license_source: bigquery


text:
ui: add local search history and suggestions

INSPIR-3408

Btw, I guess we don't care perfect multitab support, right? because currently it reads from storage only at the start and keeps write on it.
If user was to search via multiple tabs, history would be overwritten always by the tab where the latest search happened and we wouldn't able to save searches from the other tab.

@harunurhan that's a good point, let's see if we get any compains about that

authors: drjova harunurhan

repo: inspirehep/inspirehep


text:
Multiple body parameters are not allowed in swagger

In GitLab by @guyingyan on Apr 17, 2018, 15:42

In GitLab by @sokril on Nov 8, 2019, 07:49
fix issue with pr#1206

In GitLab by @sokril on Nov 8, 2019, 08:21
closed

In GitLab by @sokril on Nov 8, 2019, 08:21
assigned to @luotian-github

repo: inspursoft/board


text:
Without any data in the case of switching the time scale, the console error

In GitLab by @luotian-github on Sep 1, 2017, 11:45
add get dockerfile api in swagger

In GitLab by @liyanq528 on Nov 8, 2019, 07:35
fixed by push request #254

In GitLab by @sokril on Nov 8, 2019, 08:08
closed

In GitLab by @sokril on Nov 8, 2019, 08:08
assigned to @liyanq528


text:
Browser challenge is treated as wrong password by instagram4j

Requirements

instagram4j 2.0.3 version;
newly created instagram account to increase chances to trigger the "suspicious login" challenge;
Google Chrome browser (latest version).

Pre-Checklist
I made sure...

[+] I read the README.md
[+] I looked over the examples and wiki
[+] my issue hasn't been asked or solved before

Describe the bug
The misbehave of library happens from time to time randomly on different accounts. The library treats login request as credentials error, and says: "The password you entered is incorrect. Please try again".
However, if, with given credentials, we make an attempt to login into account using Chrome browser, we get the following redirect:

How to reproduce
val challengeHandler = IGClient.Builder.LoginHandler { client, response ->
            // Code that handles challenges
            // <...>
            //
            val state = IGChallengeUtils.requestState(client, response.challenge).join()
            println("Login state: ${state}")
            client.sendLoginRequest().join()
        }

// <...>

val client = val client = IGClient.builder()
                    .username(username)
                    .password(password)
                    .onChallenge(challengeHandler)
                    .client(IGUtils.defaultHttpClientBuilder()
                        .retryOnConnectionFailure(true)
                        .connectTimeout(120, TimeUnit.SECONDS)
                        .readTimeout(120, TimeUnit.SECONDS)
                        .writeTimeout(240, TimeUnit.SECONDS)
                        .cookieJar(cookieJar)
                        .build())
                    .login()

Expected behavior
The challengeHandler is invoked.
Actual behavior
The Password you entered is incorrect. Please try again error appears in logs, challengeHandler not getting called.

Got same error "The password you entered is incorrect. Please try again" with another challenge page. Attaching page itself in .zip

Desktop.zip

authors: dankarization ivkomarov


text:
Graceful handling of badNonce error, retry with new nonce

https://github.com/letsencrypt/pebble?tab=readme-ov-file#invalid-anti-replay-nonce-errors

While it should be possible to handle at a higher level, it seems to me like something that could be a good candidate to handle inside the ACME client, as the error could present itself in many places.

Sounds good, want to submit a PR?

Hi! I don't have time at the moment unfortunately, but if it crops up in
production I'm sure it will become a priority. Feel free to close, at least
it's here for the record
On Mon, 12 Aug 2024, 17:33 Dirkjan Ochtman, @.***>
wrote:

Sounds good, want to submit a PR?
—
Reply to this email directly, view it on GitHub
https://github.com/instant-labs/instant-acme/issues/62#issuecomment-2283283621,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABCRJ2QP6HLPJK7BRSKDP7LZRBQK5AVCNFSM6AAAAABMLOV36CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOBTGI4DGNRSGE
.
You are receiving this because you authored the thread.Message ID:
@.***>

I had a go at this in https://github.com/djc/instant-acme/pull/65 because I ran into it trying to do some testing against pebble. Let me know what you think.

authors: djc kellpossible nick96

repo: instant-labs/instant-acme


text:
Generate mmlu bench data with the original samples

The generated samples contain excess data that isn't
required and can clash with variables created in
pipelines and  data mixing.

Co-authored-by: Ben Browning <bbrownin@redhat.com>

Signed-off-by: Derek Higgins <derekh@redhat.com>

Fixes #202
Fix pulled from https://github.com/instructlab/sdg/pull/204#discussion_r1690607807
Data is the mmlu dataset file is now significantly smaller, I also tested with eval and works fine
### IMPROVEMENTS:
1. knowledge_technical_manual_curl (+0.09)

Allow mmlu_bench to return empty results

We can't control the model outputs and their ability
to produce the required format for the mmlu_bench
mcq's varys and is inconsistent.

Move the check for an Empty dataset so that we can
and use it to allow the mmlu pipeline to return an empty
dataset, while we ensure we check other pipelines for
entries.

Fixes #213

Merge when CI passes

CI failure is
  File "/home/runner/work/sdg/sdg/venv/lib/python3.11/site-packages/instructlab/sdg/pipeline.py", line 187, in _generate_single
    raise EmptyDatasetError(
instructlab.sdg.pipeline.EmptyDatasetError: Pipeline stopped: Empty dataset after running block: gen_mmlu_knowledge

CI failure is
INFO 2024-07-25 11:54:54,080 instructlab.sdg.pipeline:172: Running block: gen_mmlu_knowledge
INFO 2024-07-25 11:54:54,080 instructlab.sdg.pipeline:173: Dataset({
    features: ['icl_document', 'document', 'document_outline', 'domain', 'icl_query_1', 'icl_query_2', 'icl_query_3', 'icl_response_1', 'icl_response_2', 'icl_response_3'],
    num_rows: 10
})
...
  File "/home/runner/work/sdg/sdg/venv/lib/python3.11/site-packages/instructlab/sdg/pipeline.py", line 187, in _generate_single
    raise EmptyDatasetError(
instructlab.sdg.pipeline.EmptyDatasetError: Pipeline stopped: Empty dataset after running block: gen_mmlu_knowledge

looks like merlinite-7b-lab-Q4_K_M.gguf just isn't smart enough to run the mmlu pipeline, in most cases (not all) it fails to produce the required start/end tags

I've proposed a new config section for pipelines and switched to a draft while we discuss

CI failed again, this time on a different error, going to retrigger to see if this was a once off but leaving in draft until I figure it out

looks like merlinite-7b-lab-Q4_K_M.gguf just isn't smart enough to run the mmlu pipeline, in most cases (not all) it fails to produce the required start/end tags

This is a good point that this is likely something that should only run in the full pipeline, as most of the steps in the full pipeline don't work well with merlinite and expect a model along the lines of mixtral-8x7b to execute successfuly.

looks like merlinite-7b-lab-Q4_K_M.gguf just isn't smart enough to run the mmlu pipeline, in most cases (not all) it fails to produce the required start/end tags

This is a good point that this is likely something that should only run in the full pipeline, as most of the steps in the full pipeline don't work well with merlinite and expect a model along the lines of mixtral-8x7b to execute successfuly.

ya, it looks like merlinite-7b-lab-Q4_K_M.gguf just can't cope with the instructions, we should be ok once we deal with an empty dataset correctly

Merge when CI passes

Still stands :+1:

Just another thumbs up from me - the handling of the empty data and lack of answer column when we filter everything out of a small dataset looks good.

authors: bbrowning derekhiggins markmc

repo: instructlab/sdg


text:
Indian elephant

Topic: The Indian elephant is one of three extant recognized subspecies of the Asian elephant, native to mainland Asia. The species is smaller than the African elephant species.
Folder Location: taxonomy/knowledge/animals/indian_elephant
Downloads:

qna.yaml: indian_elephants.txt
attribution.txt

Wiki link: https://en.wikipedia.org/wiki/Indian_elephant

Hey @kelbrown20 , Can you please describe more about the issue?

Got a lot of great contributions for this one. Closing for scannability, proceeding with the contributions

repo: instructlab/taxonomy


text:
🛑 Dropzone is down

In 1f5d62e, Dropzone ($DZ_URL) was down:

HTTP code: 502
Response time: 404 ms

Resolved: Dropzone is back up in a5379ae.

repo: instruxmedia/webserver-uptime


text:
🛑 API Health is down

In 6e842f3, API Health (https://hq.intech.studio/healthz) was down:

HTTP code: 502
Response time: 471 ms

Resolved: API Health is back up in 70cd731.

repo: intechstudio/uptime


text:
Migrate to teaclave-v2.0.0

There are just so many benefits that would come with the teaclave v2.0.0, we should try to migrate soon.
However, it is not completely stable yet: https://github.com/apache/incubator-teaclave-sgx-sdk/tree/v2.0.0-preview
I have asked about migration guidance, but have not got a response yet:
https://github.com/apache/incubator-teaclave-sgx-sdk/issues/409

good news from Litentry: https://github.com/litentry/litentry-parachain/pull/2623

authors: brenzi clangenb

repo: integritee-network/worker


text:
Error: 'Not enough data for satisfy transfer length header.' during vllm serving on Arc

Scripts and Params
# start server
python -m ipex_llm.vllm.xpu.entrypoints.openai.api_server --served-model-name qwen-32b --port 8000 --model /opt/Qwen1.5-32B-Chat --trust-remote-code --gpu-memory-utilization 0.8 --device xpu --dtype float16 --enforce-eager --load-in-low-bit sym_int4 --max-model-len 9408 --max-num-batched-tokens 9408 --tensor-parallel-size 4

# start client
python benchmark_serving.py --model qwen-32b --tokenizer /opt/Qwen1.5-32B-Chat --random-input-len 7408 --random-output-len 900 --num-prompts 1 --dataset-name random

Server API Error
ERROR 08-16 18:23:54 async_llm_engine.py:470] Engine iteration timed out. This should never happen!
ERROR 08-16 18:23:54 async_llm_engine.py:41] Engine background task failed
ERROR 08-16 18:23:54 async_llm_engine.py:41] Traceback (most recent call last):
ERROR 08-16 18:23:54 async_llm_engine.py:41]   File "/usr/lib/python3.11/asyncio/tasks.py", line 500, in wait_for
ERROR 08-16 18:23:54 async_llm_engine.py:41]     return fut.result()
ERROR 08-16 18:23:54 async_llm_engine.py:41]            ^^^^^^^^^^^^
ERROR 08-16 18:23:54 async_llm_engine.py:41]   File "/llm/vllm/vllm/engine/async_llm_engine.py", line 441, in engine_step
ERROR 08-16 18:23:54 async_llm_engine.py:41]     request_outputs = await self.engine.step_async()
ERROR 08-16 18:23:54 async_llm_engine.py:41]                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
ERROR 08-16 18:23:54 async_llm_engine.py:41]   File "/llm/vllm/vllm/engine/async_llm_engine.py", line 211, in step_async
ERROR 08-16 18:23:54 async_llm_engine.py:41]     output = await self.model_executor.execute_model_async(
ERROR 08-16 18:23:54 async_llm_engine.py:41]              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
ERROR 08-16 18:23:54 async_llm_engine.py:41]   File "/usr/local/lib/python3.11/dist-packages/ipex_llm/vllm/xpu/ipex_llm_gpu_executor.py", line 443, in execute_model_async
ERROR 08-16 18:23:54 async_llm_engine.py:41]     all_outputs = await self._run_workers_async(
ERROR 08-16 18:23:54 async_llm_engine.py:41]                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
ERROR 08-16 18:23:54 async_llm_engine.py:41]   File "/usr/local/lib/python3.11/dist-packages/ipex_llm/vllm/xpu/ipex_llm_gpu_executor.py", line 433, in _run_workers_async
ERROR 08-16 18:23:54 async_llm_engine.py:41]     all_outputs = await asyncio.gather(*coros)
ERROR 08-16 18:23:54 async_llm_engine.py:41]                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
ERROR 08-16 18:23:54 async_llm_engine.py:41] asyncio.exceptions.CancelledError
ERROR 08-16 18:23:54 async_llm_engine.py:41]
ERROR 08-16 18:23:54 async_llm_engine.py:41] The above exception was the direct cause of the following exception:
ERROR 08-16 18:23:54 async_llm_engine.py:41]
ERROR 08-16 18:23:54 async_llm_engine.py:41] Traceback (most recent call last):
ERROR 08-16 18:23:54 async_llm_engine.py:41]   File "/llm/vllm/vllm/engine/async_llm_engine.py", line 36, in _raise_exception_on_finish
ERROR 08-16 18:23:54 async_llm_engine.py:41]     task.result()
ERROR 08-16 18:23:54 async_llm_engine.py:41]   File "/llm/vllm/vllm/engine/async_llm_engine.py", line 467, in run_engine_loop
ERROR 08-16 18:23:54 async_llm_engine.py:41]     has_requests_in_progress = await asyncio.wait_for(
ERROR 08-16 18:23:54 async_llm_engine.py:41]                                ^^^^^^^^^^^^^^^^^^^^^^^
ERROR 08-16 18:23:54 async_llm_engine.py:41]   File "/usr/lib/python3.11/asyncio/tasks.py", line 502, in wait_for
ERROR 08-16 18:23:54 async_llm_engine.py:41]     raise exceptions.TimeoutError() from exc
ERROR 08-16 18:23:54 async_llm_engine.py:41] TimeoutError
2024-08-16 18:23:54,093 - ERROR - Exception in callback functools.partial(<function _raise_exception_on_finish at 0x7f42b3835b20>, error_callback=<bound method AsyncLLMEngine._error_callback of <ipex_llm.vllm.xpu.engine.engine.IPEXLLMAsyncLLMEngine object at 0x7f42aa1a07d0>>)
handle: <Handle functools.partial(<function _raise_exception_on_finish at 0x7f42b3835b20>, error_callback=<bound method AsyncLLMEngine._error_callback of <ipex_llm.vllm.xpu.engine.engine.IPEXLLMAsyncLLMEngine object at 0x7f42aa1a07d0>>)>

Client side error log
ValueError: Initial test run failed - Please make sure benchmark arguments are correctly specified. Error: Traceback (most recent call last):
  File "/usr/local/lib/python3.11/dist-packages/aiohttp/client_proto.py", line 94, in connection_lost
    uncompleted = self._parser.feed_eof()
                  ^^^^^^^^^^^^^^^^^^^^^^^
  File "aiohttp/_http_parser.pyx", line 507, in aiohttp._http_parser.HttpParser.feed_eof
aiohttp.http_exceptions.TransferEncodingError: 400, message:
  Not enough data for satisfy transfer length header.

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/llm/backend_request_func.py", line 256, in async_request_openai_completions
    async for chunk_bytes in response.content:
  File "/usr/local/lib/python3.11/dist-packages/aiohttp/streams.py", line 50, in __anext__
    rv = await self.read_func()
         ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/dist-packages/aiohttp/streams.py", line 317, in readline
    return await self.readuntil()
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/dist-packages/aiohttp/streams.py", line 351, in readuntil
    await self._wait("readuntil")
  File "/usr/local/lib/python3.11/dist-packages/aiohttp/streams.py", line 312, in _wait
    await waiter
aiohttp.client_exceptions.ClientPayloadError: Response payload is not completed: <TransferEncodingError: 400, message='Not enough data for satisfy transfer length header.'>

Thanks. It is indeed due to OOM. Will adopt "enable split_qkv" patch and try again.

Improved with new release.

repo: intel-analytics/ipex-llm


text:
Add qwen2-1.5b-instruct into igpu performance

updated qwen2-1.5b-instruct to all 7 transformers==4.37 yaml files in igpu-perf

Please make sure this model is put into xx01 first. Then we can merge this PR.


text:
Video4Linux backend patching

System Configuration
Please complete Your Configuration detail below. Refer to the BKC at Configuration.

Version
Your Configuration

Operating System
Ubuntu 16.04 LTS

Kernel
4.4.0-040400-generic

Backend

ROS
kinetic

ROS RealSense
Cannot locate [realsense_camera]

librealsense
0.9.1

R200 Firmware
1.0.72.06

When I run the example program "cpp-capture", it only can last for 2 seconds and then it crashes. So, I suspect that maybe my Video4Linux backend isn't installed correctly. Then, I tried several times to reinstall the backend and all attempts seem failed.
Patching command:
$ ./scripts/patch-uvcvideo-16.04.simple.sh
After I reloaded the uvcvideo. I have some errors:
$ sudo dmesg | tail -n 50
...
[   27.284877] usb 4-1: Product: Intel RealSense 3D Camera R200
[   27.284878] usb 4-1: Manufacturer: Intel Corp
[   27.284879] usb 4-1: SerialNumber: SN_2421007586
[  146.474076] usb 4-1: usbfs: process 2512 (cpp-capture) did not claim interface 3 before use
[  146.477690] usb 4-1: usbfs: process 2512 (cpp-capture) did not claim interface 5 before use
[  152.267237] usb 4-1: usbfs: process 2514 (cpp-capture) did not claim interface 2 before use
[  152.283057] usb 4-1: usbfs: process 2514 (cpp-capture) did not claim interface 4 before use
[  162.653226] usb 4-1: USB disconnect, device number 2
[  597.419219] usb 4-1: new SuperSpeed USB device number 3 using xhci_hcd
[  597.437910] usb 4-1: New USB device found, idVendor=8086, idProduct=0a80
[  597.437916] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  597.437920] usb 4-1: Product: Intel RealSense 3D Camera R200
[  597.437923] usb 4-1: Manufacturer: Intel Corp
[  597.437926] usb 4-1: SerialNumber: SN_2421007586

I have reported this issue to IntalRealsense community. However, 5 days passed and nobody reply me. Could you please help me to solve this issue? Thanks!

Hi @jb892 filing the issue at librealsense is the right place to resolve this.  We have not encountered this issue on the ROS side, and I would recommend you review the installation docs at librealsense here: https://github.com/IntelRealSense/librealsense/blob/master/doc/installation.md

repo: intel-ros/realsense


text:
SGX DCAP Quote Generation Error

I'm trying to run SGX ECDSA Remote Attestation following the instructions in https://github.com/intel/intel-device-plugins-for-kubernetes/blob/main/cmd/sgx_plugin/README.md
$ kubectl describe node zhenhui-control-plane | grep sgx.intel.com
                    nfd.node.kubernetes.io/extended-resources: sgx.intel.com/epc
  sgx.intel.com/enclave:    110
  sgx.intel.com/epc:        4261412864
  sgx.intel.com/provision:  110
  sgx.intel.com/enclave:    110
  sgx.intel.com/epc:        4261412864
  sgx.intel.com/provision:  110
  sgx.intel.com/enclave    1           1
  sgx.intel.com/epc        1Mi         1Mi
  sgx.intel.com/provision  1           1

$ kubectl get po
NAME                                  READY   STATUS    RESTARTS   AGE
ecdsa-quote-intelsgx-demo-job-5jgjg   0/1     Error     0          5m23s
ecdsa-quote-intelsgx-demo-job-7wwpb   0/1     Error     0          5m10s
ecdsa-quote-intelsgx-demo-job-hfc6v   0/1     Error     0          5m48s
ecdsa-quote-intelsgx-demo-job-kdt6l   0/1     Error     0          5m44s
ecdsa-quote-intelsgx-demo-job-l4vxg   0/1     Error     0          5m27s
ecdsa-quote-intelsgx-demo-job-mt4kx   0/1     Error     0          5m31s
ecdsa-quote-intelsgx-demo-job-pg79b   0/1     Error     0          5m6s
intel-sgx-aesmd-ztlcx                 1/1     Running   0          6m28s
intel-sgx-plugin-748n9                1/1     Running   0          12m

$ kubectl logs ecdsa-quote-intelsgx-demo-job-pg79b

Step1: Call sgx_qe_get_target_info:Error in sgx_qe_get_target_info. 0xe001

But I can run DCAP QuoteGenerationSample successfully on my host os.
~/zhenhui/SGXDataCenterAttestationPrimitives/SampleCode/QuoteGenerationSample# ./app
sgx_qe_set_enclave_load_policy is valid in in-proc mode only and it is optional: the default enclave load policy is persistent:
set the enclave load policy as persistent:succeed!

Step1: Call sgx_qe_get_target_info:succeed!
Step2: Call create_app_report:succeed!
Step3: Call sgx_qe_get_quote_size:succeed!
Step4: Call sgx_qe_get_quote:succeed!cert_key_type = 0x5
sgx_qe_cleanup_by_policy is valid in in-proc mode only.

 Clean up the enclave load policy:succeed!

$ systemctl status pccs
● pccs.service - Provisioning Certificate Caching Service (PCCS)
     Loaded: loaded (/lib/systemd/system/pccs.service; enabled; vendor preset: enabled)
     Active: active (running) since Wed 2022-08-10 23:12:53 CST; 2 days ago
       Docs: https://github.com/intel/SGXDataCenterAttestationPrimitives/blob/master/QuoteGeneration/pccs/README.md
   Main PID: 224732 (node)
      Tasks: 11 (limit: 304204)
     Memory: 68.3M
     CGroup: /system.slice/pccs.service
             └─224732 /usr/bin/node -r esm /opt/intel/sgx-dcap-pccs/pccs_server.js

8月 12 22:28:40 i10 node[224732]: 2022-08-12 22:28:40.460 [info]: Client Request-ID : 6dd28643916845938986418d59c4a562
8月 12 22:28:40 i10 node[224732]: 2022-08-12 22:28:40.468 [info]: 127.0.0.1 - - [12/Aug/2022:14:28:40 +0000] "GET /sgx/cer>
8月 12 22:37:28 i10 node[224732]: 2022-08-12 22:37:28.208 [info]: Client Request-ID : 596bd47acce8461a95d41714b6a0f344
8月 12 22:37:28 i10 node[224732]: 2022-08-12 22:37:28.217 [info]: 127.0.0.1 - - [12/Aug/2022:14:37:28 +0000] "GET /sgx/cer>
8月 12 22:37:28 i10 node[224732]: 2022-08-12 22:37:28.275 [info]: Client Request-ID : 520e4c761da24780aa59642dce9b340c
8月 12 22:37:28 i10 node[224732]: 2022-08-12 22:37:28.284 [info]: 127.0.0.1 - - [12/Aug/2022:14:37:28 +0000] "GET /sgx/cer>
8月 12 22:37:28 i10 node[224732]: 2022-08-12 22:37:28.307 [info]: Client Request-ID : 3db53bd9a0c94f318a4e42bc527fa602
8月 12 22:37:28 i10 node[224732]: 2022-08-12 22:37:28.316 [info]: 127.0.0.1 - - [12/Aug/2022:14:37:28 +0000] "GET /sgx/cer>
8月 12 22:37:28 i10 node[224732]: 2022-08-12 22:37:28.337 [info]: Client Request-ID : d2201fa74ecf4c45b38f8efe12445031
8月 12 22:37:28 i10 node[224732]: 2022-08-12 22:37:28.345 [info]: 127.0.0.1 - - [12/Aug/2022:14:37:28 +0000] "GET /sgx/cer>

cat /etc/sgx_default_qcnl.conf
# PCCS server address
PCCS_URL=https://localhost:8081/sgx/certification/v3/

# To accept insecure HTTPS certificate, set this option to FALSE
USE_SECURE_CERT=FALSE

# You can use Intel PCS to get quote verification collateral
#COLLATERAL_SERVICE=https://api.trustedservices.intel.com/sgx/certification/v3/

# If you use PCCS service to get quote verification collateral, you can specify which API version is to be used
# The legacy 3.0 API will return CRLs in HEX encoded DER format, while the new 3.1 API will return raw DER format
#PCCS_API_VERSION=3.1

# Maximum retry times for QCNL. If RETRY is not defined or set to 0, no retry will be performed.
# It will first wait one second and then for all forthcoming retries it will double the waiting time
# By using RETRY_DELAY you disable this exponential backoff algorithm
#RETRY_TIMES=6

# Sleep this amount of seconds before each retry when a transfer has failed with a transient error
#RETRY_DELAY=10

https://github.com/intel/SGXDataCenterAttestationPrimitives/issues?q=0xe001
0xe001 looks like an unexpected error, how can I debug this problem? Thanks for help.

0xe001 looks like an unexpected error, how can I debug this problem? Thanks for help.

Is your aesmd pod configured to access this PCC:
https://github.com/intel/intel-device-plugins-for-kubernetes/blob/main/deployments/sgx_aesmd/base/sgx_default_qcnl.conf

Is your aesmd pod configured to access this PCCS: https://github.com/intel/intel-device-plugins-for-kubernetes/blob/main/deployments/sgx_aesmd/base/sgx_default_qcnl.conf

I just use
kubectl apply -k https://github.com/intel/intel-device-plugins-for-kubernetes/deployments/sgx_aesmd?ref=main to deploy aesmd pod, without changing any configuration.

The comparison of running ./app on the host vs ecdsa-quote-intelsgx-demo-job not apples to apples because the latter uses aesmd.
Two things to check:
# SGX_AESM_ADDR=1 ./app

Do you see the /var/run/aesmd/aesm.sock?

# SGX_AESM_ADDR=1 ./app

~/zhenhui/SGXDataCenterAttestationPrimitives/SampleCode/QuoteGenerationSample# SGX_AESM_ADDR=1 ./app

Step1: Call sgx_qe_get_target_info:succeed!
Step2: Call create_app_report:succeed!
Step3: Call sgx_qe_get_quote_size:succeed!
Step4: Call sgx_qe_get_quote:succeed!cert_key_type = 0x5

Do you see the /var/run/aesmd/aesm.sock?

~/zhenhui/SGXDataCenterAttestationPrimitives/SampleCode/QuoteGenerationSample# ls -lt /var/run/aesmd/
total 0
srwxrwxrwx 1 aesmd aesmd 0 8月  11 18:13 aesm.socket

the file name is not aesm.sock but aesm.socket

´systemctl status aesmd`

you have aesmd running both on the host and in the container? only one is enough.

you have aesmd running both on the host and in the container? only one is enough.

Yep, I tried to stop the one on host with systemctl stop aesmd , but it doesn't help, there must be other reasons for the error.

If aesmd pod works correctly, should there be a socket file in /var/run/aesmd/ on host os?
After I stop the aesmd service on host os, /var/run/aesmd/ now contains no socket.
$ kubectl get po
NAME                                  READY   STATUS    RESTARTS   AGE
ecdsa-quote-intelsgx-demo-job-58mgf   0/1     Error     0          5m10s
ecdsa-quote-intelsgx-demo-job-68nwh   0/1     Error     0          5m2s
ecdsa-quote-intelsgx-demo-job-c22wt   0/1     Error     0          4m37s
ecdsa-quote-intelsgx-demo-job-h5gcl   0/1     Error     0          4m50s
ecdsa-quote-intelsgx-demo-job-wnw9t   0/1     Error     0          5m6s
ecdsa-quote-intelsgx-demo-job-x46q4   0/1     Error     0          4m54s
ecdsa-quote-intelsgx-demo-job-xrm7x   0/1     Error     0          4m58s
intel-sgx-aesmd-7d4s8                 1/1     Running   0          6m41s
intel-sgx-plugin-748n9                1/1     Running   0          135m

$ ls -l /var/run/aesmd/
total 0

If aesmd pod works correctly, should there be a socket file in /var/run/aesmd/ on host os?

yes. perhaps the webhook is not mutating correctly for you. can you describe the demo job and aesmd pods' output

yes. perhaps the webhook is not mutating correctly for you. can you describe the demo job and aesmd pods' output

$ kubectl describe po intel-sgx-aesmd-9898b
Name:         intel-sgx-aesmd-9898b
Namespace:    default
Priority:     0
Node:         zhenhui-control-plane/172.21.0.3
Start Time:   Sat, 13 Aug 2022 00:46:35 +0800
Labels:       app=intel-sgx-aesmd
              controller-revision-hash=647857d559
              pod-template-generation=1
Annotations:  sgx.intel.com/epc: 1Mi
              sgx.intel.com/quote-provider: aesmd
Status:       Running
IP:           172.21.0.3
IPs:
  IP:           172.21.0.3
Controlled By:  DaemonSet/intel-sgx-aesmd
Containers:
  aesmd:
    Container ID:   containerd://c23a6802da868a755d42fd6523f9a139014eec997878e14c30d801a9989aba59
    Image:          intel/sgx-aesmd-demo:devel
    Image ID:       docker.io/library/import-2022-08-12@sha256:aeb55ce8810b059d1adb902ade638fe57a3682200dcde3fbdf5550057489cf79
    Port:           <none>
    Host Port:      <none>
    State:          Running
      Started:      Sat, 13 Aug 2022 00:47:10 +0800
    Ready:          True
    Restart Count:  0
    Limits:
      sgx.intel.com/enclave:    1
      sgx.intel.com/epc:        1Mi
      sgx.intel.com/provision:  1
    Requests:
      sgx.intel.com/enclave:    1
      sgx.intel.com/epc:        1Mi
      sgx.intel.com/provision:  1
    Environment:
      SGX_AESM_ADDR:  1
    Mounts:
      /etc/aesmd.conf from aesmdconf (rw,path="aesmd.conf")
      /etc/sgx_default_qcnl.conf from qplconf (rw,path="sgx_default_qcnl.conf")
      /var/run/aesmd from aesmd-socket (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-w6g6r (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             True
  ContainersReady   True
  PodScheduled      True
Volumes:
  aesmdconf:
    Type:      ConfigMap (a volume populated by a ConfigMap)
    Name:      sgx-attestation-conf
    Optional:  false
  qplconf:
    Type:      ConfigMap (a volume populated by a ConfigMap)
    Name:      sgx-attestation-conf
    Optional:  false
  kube-api-access-w6g6r:
    Type:                    Projected (a volume that contains injected data from multiple sources)
    TokenExpirationSeconds:  3607
    ConfigMapName:           kube-root-ca.crt
    ConfigMapOptional:       <nil>
    DownwardAPI:             true
  aesmd-socket:
    Type:          HostPath (bare host directory volume)
    Path:          /var/run/aesmd
    HostPathType:  DirectoryOrCreate
QoS Class:         BestEffort
Node-Selectors:    <none>
Tolerations:       node.kubernetes.io/disk-pressure:NoSchedule op=Exists
                   node.kubernetes.io/memory-pressure:NoSchedule op=Exists
                   node.kubernetes.io/network-unavailable:NoSchedule op=Exists
                   node.kubernetes.io/not-ready:NoExecute op=Exists
                   node.kubernetes.io/pid-pressure:NoSchedule op=Exists
                   node.kubernetes.io/unreachable:NoExecute op=Exists
                   node.kubernetes.io/unschedulable:NoSchedule op=Exists
Events:
  Type     Reason            Age                From               Message
  ----     ------            ----               ----               -------
  Warning  FailedScheduling  15m                default-scheduler  0/1 nodes are available: 1 Insufficient sgx.intel.com/epc. preemption: 0/1 nodes are available: 1 No preemption victims found for incoming pod.
  Normal   Scheduled         15m                default-scheduler  Successfully assigned default/intel-sgx-aesmd-9898b to zhenhui-control-plane
  Normal   BackOff           15m                kubelet            Back-off pulling image "intel/sgx-aesmd-demo:devel"
  Warning  Failed            15m                kubelet            Error: ImagePullBackOff
  Normal   Pulling           14m (x2 over 15m)  kubelet            Pulling image "intel/sgx-aesmd-demo:devel"
  Warning  Failed            14m (x2 over 15m)  kubelet            Failed to pull image "intel/sgx-aesmd-demo:devel": rpc error: code = Unknown desc = failed to pull and unpack image "docker.io/intel/sgx-aesmd-demo:devel": failed to resolve reference "docker.io/intel/sgx-aesmd-demo:devel": pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed
  Warning  Failed            14m (x2 over 15m)  kubelet            Error: ErrImagePull
  Normal   Pulled            14m                kubelet            Container image "intel/sgx-aesmd-demo:devel" already present on machine
  Normal   Created           14m                kubelet            Created container aesmd
  Normal   Started           14m                kubelet            Started container aesmd

kubectl logs intel-sgx-aesmd-9898b
The path of system bundle: System Bundle
ecdsa_quote_service_bundle_name:2.0.0
linux_network_service_bundle_name:2.0.0
pce_service_bundle_name:2.0.0
quote_ex_service_bundle_name:2.0.0
system_bundle:4.0.0

kubectl describe po intel-sgx-plugin-dqr6j
Name:         intel-sgx-plugin-dqr6j
Namespace:    default
Priority:     0
Node:         zhenhui-control-plane/172.21.0.3
Start Time:   Sat, 13 Aug 2022 00:45:04 +0800
Labels:       app=intel-sgx-plugin
              controller-revision-hash=794496974c
              pod-template-generation=1
Annotations:  <none>
Status:       Running
IP:           10.244.0.7
IPs:
  IP:           10.244.0.7
Controlled By:  DaemonSet/intel-sgx-plugin
Init Containers:
  intel-sgx-initcontainer:
    Container ID:   containerd://2e2505ef24e89c4e64380d40aa0587130149fccdfea919a108489c1399f1591a
    Image:          intel/intel-sgx-initcontainer:devel
    Image ID:       docker.io/intel/intel-sgx-initcontainer@sha256:92a43fe2b96717c63c9023f12d17ec7f25c13c73c51952a01981e9164d0159df
    Port:           <none>
    Host Port:      <none>
    State:          Terminated
      Reason:       Completed
      Exit Code:    0
      Started:      Sat, 13 Aug 2022 00:45:31 +0800
      Finished:     Sat, 13 Aug 2022 00:45:31 +0800
    Ready:          True
    Restart Count:  0
    Environment:    <none>
    Mounts:
      /etc/kubernetes/node-feature-discovery/source.d/ from nfd-source-hooks (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-b2fm8 (ro)
Containers:
  intel-sgx-plugin:
    Container ID:   containerd://328b994a24ca07d35b2440ace4fa945f59f61e6a5f75f157174fb2571616f889
    Image:          intel/intel-sgx-plugin:devel
    Image ID:       docker.io/intel/intel-sgx-plugin@sha256:903e1548c8857556860eb914c0a4c46e3bef7f45b1f06e871deb528759991c0e
    Port:           <none>
    Host Port:      <none>
    State:          Running
      Started:      Sat, 13 Aug 2022 00:46:04 +0800
    Ready:          True
    Restart Count:  0
    Environment:    <none>
    Mounts:
      /dev/sgx_enclave from sgx-enclave (ro)
      /dev/sgx_provision from sgx-provision (ro)
      /var/lib/kubelet/device-plugins from kubeletsockets (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-b2fm8 (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             True
  ContainersReady   True
  PodScheduled      True
Volumes:
  nfd-source-hooks:
    Type:          HostPath (bare host directory volume)
    Path:          /etc/kubernetes/node-feature-discovery/source.d/
    HostPathType:  DirectoryOrCreate
  kubeletsockets:
    Type:          HostPath (bare host directory volume)
    Path:          /var/lib/kubelet/device-plugins
    HostPathType:
  sgx-enclave:
    Type:          HostPath (bare host directory volume)
    Path:          /dev/sgx_enclave
    HostPathType:  CharDevice
  sgx-provision:
    Type:          HostPath (bare host directory volume)
    Path:          /dev/sgx_provision
    HostPathType:  CharDevice
  kube-api-access-b2fm8:
    Type:                    Projected (a volume that contains injected data from multiple sources)
    TokenExpirationSeconds:  3607
    ConfigMapName:           kube-root-ca.crt
    ConfigMapOptional:       <nil>
    DownwardAPI:             true
QoS Class:                   BestEffort
Node-Selectors:              kubernetes.io/arch=amd64
Tolerations:                 node.kubernetes.io/disk-pressure:NoSchedule op=Exists
                             node.kubernetes.io/memory-pressure:NoSchedule op=Exists
                             node.kubernetes.io/not-ready:NoExecute op=Exists
                             node.kubernetes.io/pid-pressure:NoSchedule op=Exists
                             node.kubernetes.io/unreachable:NoExecute op=Exists
                             node.kubernetes.io/unschedulable:NoSchedule op=Exists
Events:
  Type    Reason     Age   From               Message
  ----    ------     ----  ----               -------
  Normal  Scheduled  18m   default-scheduler  Successfully assigned default/intel-sgx-plugin-dqr6j to zhenhui-control-plane
  Normal  Pulling    18m   kubelet            Pulling image "intel/intel-sgx-initcontainer:devel"
  Normal  Pulled     18m   kubelet            Successfully pulled image "intel/intel-sgx-initcontainer:devel" in 25.720694391s
  Normal  Created    18m   kubelet            Created container intel-sgx-initcontainer
  Normal  Started    18m   kubelet            Started container intel-sgx-initcontainer
  Normal  Pulling    18m   kubelet            Pulling image "intel/intel-sgx-plugin:devel"
  Normal  Pulled     17m   kubelet            Successfully pulled image "intel/intel-sgx-plugin:devel" in 31.173730203s
  Normal  Created    17m   kubelet            Created container intel-sgx-plugin
  Normal  Started    17m   kubelet            Started container intel-sgx-plugin

@astronaut0131 everything seems correct. you could always try running aesmd on the host and undeploy that aesmd container.

@astronaut0131 everything seems correct. you could always try running aesmd on the host and undeploy that aesmd container.

Using aesmd on host only gives:
$ kubectl logs ecdsa-quote-intelsgx-demo-job-w2gbd

Step1: Call sgx_qe_get_target_info:Error in sgx_qe_get_target_info. 0xe040
[init ../../../psw/ae/aesm_service/source/core/ipc/UnixCommunicationSocket.cpp:225] Failed to connect to socket /var/run/aesmd/aesm.socket

The socket actually appears on the host
$ ls /var/run/aesmd/
aesm.socket

Sample works correctly
$ SGX_AESM_ADDR=1 ./app

Step1: Call sgx_qe_get_target_info:succeed!
Step2: Call create_app_report:succeed!
Step3: Call sgx_qe_get_quote_size:succeed!
Step4: Call sgx_qe_get_quote:succeed!cert_key_type = 0x5

Shall I mount this socket onto the job demo pod or something?

Shall I mount this socket onto the job demo pod or something?

It is mounted:
    Mounts:
      /var/run/aesmd from aesmd-socket (rw)
...
  aesmd-socket:
    Type:          HostPath (bare host directory volume)
    Path:          /var/run/aesmd
    HostPathType:  DirectoryOrCreate

Image:          intel/intel-sgx-plugin:devel

can you try with version 0.24.0?

Image:          intel/intel-sgx-plugin:devel

can you try with version 0.24.0?

same error
$ kubectl describe po intel-sgx-plugin-hckfz
Name:         intel-sgx-plugin-hckfz
Namespace:    default
Priority:     0
Node:         zhenhui-control-plane/172.21.0.2
Start Time:   Sat, 13 Aug 2022 03:04:23 +0800
Labels:       app=intel-sgx-plugin
              controller-revision-hash=79f8f5cd9d
              pod-template-generation=1
Annotations:  <none>
Status:       Running
IP:           10.244.0.11
IPs:
  IP:           10.244.0.11
Controlled By:  DaemonSet/intel-sgx-plugin
Init Containers:
  intel-sgx-initcontainer:
    Container ID:   containerd://edace9707de247e6787c14edc28c098c4a1fcae1e9b46f3f669a004dfd9d0157
    Image:          intel/intel-sgx-initcontainer:0.24.0
    Image ID:       docker.io/intel/intel-sgx-initcontainer@sha256:da7f4ad1c2d0b9690744841a6b228ce33efe06087a8027c945e06353d5416fb9
    Port:           <none>
    Host Port:      <none>
    State:          Terminated
      Reason:       Completed
      Exit Code:    0
      Started:      Sat, 13 Aug 2022 03:04:57 +0800
      Finished:     Sat, 13 Aug 2022 03:04:57 +0800
    Ready:          True
    Restart Count:  0
    Environment:    <none>
    Mounts:
      /etc/kubernetes/node-feature-discovery/source.d/ from nfd-source-hooks (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-927lg (ro)
Containers:
  intel-sgx-plugin:
    Container ID:   containerd://078879155314cd6ca4a07c17ddfe2b10db1262ad98987df2fa51883555aaee25
    Image:          intel/intel-sgx-plugin:0.24.0
    Image ID:       docker.io/intel/intel-sgx-plugin@sha256:1fc6756cc3423ae05df07605cb30e2615725c2cb0192805d7da2bf67eb1b678c
    Port:           <none>
    Host Port:      <none>
    State:          Running
      Started:      Sat, 13 Aug 2022 03:05:18 +0800
    Ready:          True
    Restart Count:  0
    Environment:    <none>
    Mounts:
      /dev/sgx from sgxdevices (ro)
      /dev/sgx_enclave from sgx-enclave (ro)
      /dev/sgx_provision from sgx-provision (ro)
      /var/lib/kubelet/device-plugins from kubeletsockets (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-927lg (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             True
  ContainersReady   True
  PodScheduled      True
Volumes:
  nfd-source-hooks:
    Type:          HostPath (bare host directory volume)
    Path:          /etc/kubernetes/node-feature-discovery/source.d/
    HostPathType:  DirectoryOrCreate
  kubeletsockets:
    Type:          HostPath (bare host directory volume)
    Path:          /var/lib/kubelet/device-plugins
    HostPathType:
  sgxdevices:
    Type:          HostPath (bare host directory volume)
    Path:          /dev/sgx
    HostPathType:  DirectoryOrCreate
  sgx-enclave:
    Type:          HostPath (bare host directory volume)
    Path:          /dev/sgx_enclave
    HostPathType:  CharDevice
  sgx-provision:
    Type:          HostPath (bare host directory volume)
    Path:          /dev/sgx_provision
    HostPathType:  CharDevice
  kube-api-access-927lg:
    Type:                    Projected (a volume that contains injected data from multiple sources)
    TokenExpirationSeconds:  3607
    ConfigMapName:           kube-root-ca.crt
    ConfigMapOptional:       <nil>
    DownwardAPI:             true
QoS Class:                   BestEffort
Node-Selectors:              kubernetes.io/arch=amd64
Tolerations:                 node.kubernetes.io/disk-pressure:NoSchedule op=Exists
                             node.kubernetes.io/memory-pressure:NoSchedule op=Exists
                             node.kubernetes.io/not-ready:NoExecute op=Exists
                             node.kubernetes.io/pid-pressure:NoSchedule op=Exists
                             node.kubernetes.io/unreachable:NoExecute op=Exists
                             node.kubernetes.io/unschedulable:NoSchedule op=Exists
Events:
  Type     Reason       Age    From               Message
  ----     ------       ----   ----               -------
  Normal   Scheduled    2m44s  default-scheduler  Successfully assigned default/intel-sgx-plugin-hckfz to zhenhui-control-plane
  Warning  FailedMount  2m42s  kubelet            MountVolume.SetUp failed for volume "kube-api-access-927lg" : failed to sync configmap cache: timed out waiting for the condition
  Normal   Pulling      2m41s  kubelet            Pulling image "intel/intel-sgx-initcontainer:0.24.0"
  Normal   Pulled       2m10s  kubelet            Successfully pulled image "intel/intel-sgx-initcontainer:0.24.0" in 31.333289507s
  Normal   Created      2m10s  kubelet            Created container intel-sgx-initcontainer
  Normal   Started      2m10s  kubelet            Started container intel-sgx-initcontainer
  Normal   Pulling      2m9s   kubelet            Pulling image "intel/intel-sgx-plugin:0.24.0"
  Normal   Pulled       109s   kubelet            Successfully pulled image "intel/intel-sgx-plugin:0.24.0" in 19.330088346s
  Normal   Created      109s   kubelet            Created container intel-sgx-plugin
  Normal   Started      109s   kubelet            Started container intel-sgx-plugin

$ kubectl logs ecdsa-quote-intelsgx-demo-job-mjxl4
[init ../../../psw/ae/aesm_service/source/core/ipc/UnixCommunicationSocket.cpp:225] Failed to connect to socket /var/run/aesmd/aesm.socket

Step1: Call sgx_qe_get_target_info:Error in sgx_qe_get_target_info. 0xe040

Could this problem relate to linux permission?
ll /var/run/aesmd/
total 0
drwxr-xr-x  2 aesmd aesmd   60 8月  13 01:46 ./
drwxr-xr-x 41 root  root  1420 8月  13 02:57 ../
srwxrwxrwx  1 aesmd aesmd    0 8月  13 01:46 aesm.socket=

@astronaut0131 good to hear it works!

but I ignored that user should mount volumn manually from host to kind node on bootstrap.

maybe share what you learned here so that if someone hits the same problem they will find it here

Sure, I've made a pull request to add deployment notes to avoid this problem.
https://github.com/intel/intel-device-plugins-for-kubernetes/pull/1099


text:
FPGA: Migrate to ClearLinux, use native go and kernel APIs

Build all the tools from the source in ClearLinux environment

Codecov Report

Merging #199 into master will decrease coverage by 0.59%.
The diff coverage is 50%.

@@            Coverage Diff            @@
##           master     #199     +/-   ##
=========================================
- Coverage   79.17%   78.58%   -0.6%
=========================================
  Files          11       11
  Lines        1508     1508
=========================================
- Hits         1194     1185      -9
- Misses        281      289      +8
- Partials       33       34      +1

Impacted Files
Coverage Δ

cmd/fpga_crihook/main.go
78.33% <50%> (-3.75%)
:arrow_down:

Continue to review full report at Codecov.

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

looks good to me except of reduced test coverage.

authors: bart0sh codecov-io kad


text:
xfail test_tensor_atomic_rmw for fp64 as unsupported type

Closes #1548.

I am not sure if I should have updated all scripts/skiplist/*/language.txt files. Let me know if it is required and why.

Will the existing free function work -
def check_type_supported(dtype, device):

Good catch! I didn't notice it. Addressed.

I think this change could be upstreamed to Triton. Can you give it a try @YarShev ?

Is there relevant AMD or NVIDIA hardware that does not support fp64? Otherwise I suspect they will reject the change.

authors: YarShev alexbaden etiotto

repo: intel/intel-xpu-backend-for-triton


text:
Fix broken TPs (includes FSharp.Data)

Type providers can emit code which currently cause a failure in FCS TAST traversal, see https://github.com/fsharp/FSharp.Compiler.Service/issues/568
Solutions:

(workaround in WS) finish ReflectedDefinition-based fallback translation - needs the "corrector" logic ported from WS3 (removing outer lambda expressions based on argument currying info)
add a fallback case in FCS to expose unresolved IL calls through the TAST API, handle these calls in WS4 F# code reader

This has now been solved by FCS improvements

repo: intellifactory/websharper


text:
Continue providing errors structured similarly to pre-Rails-6.1

merge work done last year for Rails 6.1 to master branch

Merging, but going to keep the branch because it is currently specified in Exceed's gem file


text:
Change Download Location

Is there anyway to change the download location?

@riichdog is this working for you?

The code is no longer running, but why?? even it not download the test twitter videos.. any solution??

authors: Bilal4801 riichdog yarodevuci

repo: inteoryx/twitter-video-dl

license: Unlicense


text:
Scroll back to top after clicking bottom links

After clicking on bottom links, the next page is scrolled to the bottom. Would prefer it to stay at the top of the page.
Can that be disabled or configured?

Which browser are you using? This should work fine.

Using Chrome 66 on a Mac. Stays at the bottom when running locally but works fine after building.

repo: interactivethings/catalog


text:
BLE Incorrect MTU

I've tested version 2.0.1 a few more times. It looks that MTU is calculated incorrectly sometimes. The log after a few runs look like:
INFO smp_characteristic.max_write_without_response_size=20
INFO smp_characteristic.max_write_without_response_size=495

It seems that this should be still added
        # BlueZ doesn't have a proper way to get the MTU, so we have this hack.
        # If this doesn't work for you, you can set the client._mtu_size attribute
        # to override the value instead.
        if self._client._backend.__class__.__name__ == "BleakClientBlueZDBus":
            await self._client._backend._acquire_mtu()

There is a Windows-specific workaround, but it looks like it may be required for Linux as well... either way, I'd like to hear more from Bleak about the "best way".
https://github.com/intercreate/smpclient/blob/0f47207c8d44b843a599d23ff7dd202dcdac25c2/smpclient/transport/ble.py#L73-L85

Hmmm, BlueZ gets it here: https://github.com/hbldh/bleak/blob/b8149a5b5504eaacbd45ee56c1339fa4395e1345/bleak/backends/bluezdbus/manager.py#L697-L699

Right now it defaults to 20 %50 of times. Calling this explicit works 100% time https://github.com/tomaszduda23/smpclient/blob/d25c8035ae2858fd41a106058297b619d58fbcb5/smpclient/transport/ble.py#L84
It seems that there is a race in bleak. Perhaps value is set only once and sometimes it happens before MTU negotiation is completed.
Could you consider adding this code temporary? It is main blocker for me know.

@tomaszduda23 Agreed that we need the fix now, I will add it back!
I’ll be advocating for Bleak to add acquire_mtu() to the public interface.

I've tested 3.0.1 and MTU works correctly :+1:

repo: intercreate/smpclient


text:
fix: oracle hotfix

Hotfixes the oracle bug fix to Interlay

Can't be hotfixed - missing utility.

repo: interlay/interbtc-ui


text:
Add IlpOverHttp and FX connection settings to ConnectorSettings

Fixes #453

@sappenin I added a bunch of javadocs and cleaned everything up!


text:
Default range filters with now are not visible

E.g. if the month filter is like this:
[NOW-6]:&[NOW-1]
meaning last 5 months
it is not visible in filters and in widgets in the implied filter indicator.

fixed try to update to 3.2.10

Still doesn't work if the filter is a range:

example please
without calendar
months

Here is the example
https://pie-chart-bug.demo.community.intersystems.com/dsw/index.html#/USER/Two Subject Areas Together.dashboard
And the filter value syntaxis

The data is filtered fine, but the filter value itself is not displayed.

fixed in 3.2.17

@evshvarov could you please see it on your data and close issue if all is good

Filters still show whole range of dates. On top of that data does not filter according to filter values

authors: Frisle Lena-Ev evshvarov gnibeda

repo: intersystems-community/DeepSeeWeb


text:
Additional Escape Sequence

Escape sequence [m  not working, should be equivalent to [0m

Thanks for reporting! Expect this to be fixed soon.

Fixed in WebTerminal v4.2.3, please update. Thanks for reporting!

authors: ZitRos denhamson

repo: intersystems-ru/webterminal


text:
🛑 New Zeeuws Museum is down

In 152d4b4, New Zeeuws Museum (https://new.zeeuwsmuseum.nl/nl/over-het-museum/publicaties/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: New Zeeuws Museum is back up in 5438877 after 22 minutes.

repo: intk/intk-upptime


text:
import json file affected by "intifly/nuxt3" module installation

when i import json file with typescript i get values wrapped in functions
here is my code:

const getMapping = async () => import('~/config/mapping.json').then((r: any) => r.default || r)
const mapping = await getMapping()
console.log(mapping)

console.log result
{
  type: [Function: fn] { source: 'wordpress' },
  fields: {
    headline: [Function: fn] { source: 'title' },
    dateModified: [Function: fn] { source: 'modified' }
  }
}

original json file :
{
    "type": "wordpress",
    "fields":{
        "headline": "title",
        "dateModified": "modified"
    }
}

output file when I comment module '@intlify/nuxt3'
{
  type: 'wordpress',
  fields: { headline: 'title', dateModified: 'modified' }
}

installing the module changes the way all JSON files from a nuxt project are imported, is this a bug?

How are you fixing this issue?

authors: duyleekun johan-Rm


text:
Split readme.md into smaller files or/and create structured documentation

I like the readme for its expressive explanation and details. It enables one to get started right away.
Loading/rendering the site takes some time and sometimes it's difficult to find the right content.
I would propose to create an overview readme that explains roughly what karate what it is and does and to move the complete documentation into a github page with different subpages.

the main reason why I'd like to keep it the way it is - is because of feedback that doing a CTRL+F is an effective way to find a keyword in the entire doc
also note: https://intuit.github.io/karate/ - you are welcome to improve that render via CSS etc and use this issue as a reference when you submit a PR
closing as wontfix

authors: peterquiel ptrthomas

repo: intuit/karate


text:
Debugging an UnknownError

I encountered an unknown error like this
UnknownError:
error(::Memento.Logger, ::LibPQ.Errors.PQResultError{CUN,EUNOWN}) at loggers.jl:439
#handle_result#48(::Bool, ::typeof(LibPQ.handle_result), ::LibPQ.Result) at results.jl:226
#handle_result at none:0 [inlined]
#execute#49(::Bool, ::Base.Iterators.Pairs{Union{},Union{},Tuple{},NamedTuple{(),Tuple{}}}, ::typeof(LibPQ.execute), ::LibPQ.Connection, ::String) at results.jl:278
execute at results.jl:274 [inlined]
#resample_bar#3(::String, ::String, ::String, ::String, ::String, ::String, ::String, ::String, ::String, ::String, ::String, ::typeof(DBFunc.resample_bar)) at DBFunc.jl:29
(::getfield(DBFunc, Symbol("#kw##resample_bar")))(::NamedTuple{(:table, :bucket, :where_cond, :limit),NTuple{4,String}}, ::typeof(DBFunc.resample_bar)) at none:0
#calc_macd!#1(::String, ::Nothing, ::String, ::String, ::typeof(Main.MacdMon.calc_macd!), ::Main.MacdMon.CaredMACD) at MacdMon.jl:26
calc_macd!(::Main.MacdMon.CaredMACD) at MacdMon.jl:20
top-level scope at run_ind.jl:8

I tried the execution string in pgweb and it works, it basically is a query with subquery on timescaledb to get resampled frequency of stock bars.

My fault , Thanks.


text:
Problems with connection timeouts and multihreadding

Hello,
I have a code where I write data into a Postgres db (using LibPQ.jl) which runs in parallel task. I had general issues with multithreading but hose could be solved, see https://discourse.julialang.org/t/no-real-multithreading-possible/77920.
Now I can observe that if there is a connection timeout to my Postgres-db make a libpq call taking longer, the thread calling libpq library is blocking all other threads. I am wondering if multithreading is only working correctly with pure julia code or if this is an issue with LibPQ
Any hint is welcome.
TIA, agcm

There are a number of things that can cause blocking; a traceback from an interrupt when the blocking is happening would be useful to narrow it down. I'm also not sure how I would tell the difference between a blocking C library call and monopolizing a thread (which sounds like it can happen from the linked discussions?), without instrumenting LibPQ (which you could try on your machine).
One thing is if you're using a hostname, then DNS lookups can block: https://www.postgresql.org/docs/10/libpq-connect.html#LIBPQ-PARAMKEYWORDS
I'm afraid I haven't kept up with multithreading in Julia so I'm not sure if there's a difference between running on the "main thread" or another thread, and I don't know whether async code can monopolize a thread or something. I can say that, as is, LibPQ.jl connections should yield as appropriate while connecting as long as the restrictions are met and the standard library's poll_fd yields properly.

@iamed2: Thanks for the fast reply and especially for the hint with the DNS lookup because: we actually use two different Postgres Servers: one, which is accessible via the internet using and DNS and one accessible via a VPN extranet and its VPN IP. The one access via VPN and its IP so fare never had the described problem. The DNS one does. The two servers are not the same one and hosted by different provides (most probably also not the same version of Postgres server application) so we first though it be rather an issue of the different servers and not the DNS lookup. I will try accessing the DNS based server using its IP to verify that it is actually that.

To deal with this you can perform the DNS lookup in advance and cache it using the stdlib:
julia> using Sockets  # stdlib

julia> getalladdrinfo("google.com")  # all IPs, useful to handle failover
2-element Vector{IPAddr}:
 ip"142.250.191.110"
 ip"2607:f8b0:4009:817::200e"

julia> getaddrinfo("google.com")  # first IP
ip"142.250.191.110"

Then pass that as hostaddr instead of host in the DSN.

@iamed2: Good idea. I will incorporate that in my code and give feedback once it's active again and runs without errors (or if the error still exists)

I think I still have the same issue, also when using the hostaddr instead of the host. I rather think it's a timeout problem. In the documentation here I saw that the default value of the connection parameter connect_timeout means wait indefinitely ... I have now set connect_timeout=10 in the LibPQ connection string and will evaluate if things are better now.


text:
settings: cannot rename when only changing capitalisation

Steps to Reproduce

Create a new community with an identifier, e.g. Zenodo.
Now, try to rename the identifier to zenodo (lower-case z).

Expected behavior
That I'm able to fix upper/lower case issues in the identifier.

Closing since now all input gets converted to lowercase (thus there's no way to create a community with any uppercase letters)

authors: lnielsen slint

repo: inveniosoftware/invenio-communities


text:
community header: layout improvements

Needs https://github.com/inveniosoftware/invenio-app-rdm/pull/1574
Reduced the amount of space needed for the header content.

Moved description to accordion
Changed details listing to be inline on computer (needs PR mentioned above - use of .flex does not solve the issue, as this class does not break the content on smaller screens.)
Made logo slightly smaller on tablet

Screenshots

nice idea with "About this community" button! would it make sense to be always "open" on desktop ? and folded when there is not enough space?

Hey
Over all I'd like to significantly reduce the header size. Goal issomething like GitHub as an example:

Thus,

I would reduce logo size even further
Agree that description should be default be hidden
New upload button is ok to vertically centre when the entire header size is reduced:

NOTE: Updates needs PR https://github.com/inveniosoftware/invenio-app-rdm/pull/1606 for styling!
Updated screenshots

authors: jennur kpsherva lnielsen


text:
legacy: deprecation warnings addition

INCOMPATIBLE Specifies deprecation warnings for legacy modules
bibcirculation, bibdocfile, bibedit, elmsubmit,
websearch_external_collections, and websubmit.

Signed-off-by: Jiri Kuncar jiri.kuncar@cern.ch

:shipit:

authors: jirikuncar tiborsimko

repo: inveniosoftware/invenio


text:
global: Invenio 3.0 initial structure

Prepares code structure for Invenio 3 and aligns package
structure with current package standards.

Removes all remaining legacy code from Invenio.

Removes docker scripts from Invenio (to be move to Invenio-Base or
Invenio-Demosite).

Leaves current documentation in place.

Signed-off-by: Lars Holm Nielsen lars.holm.nielsen@cern.ch

LGTM besides (1) the above-mentioned cookiecutter leftovers:
$ git grep -Hni cookiecutter
docs/Makefile:90:       @echo "# qcollectiongenerator $(BUILDDIR)/qthelp/cookiecutterproject_name.qhcp"
docs/Makefile:92:       @echo "# assistant -collectionFile $(BUILDDIR)/qthelp/cookiecutterproject_name.qhc"
docs/Makefile:107:      @echo "# mkdir -p $$HOME/.local/share/devhelp/cookiecutterproject_name"
docs/Makefile:108:      @echo "# ln -s $(BUILDDIR)/devhelp $$HOME/.local/share/devhelp/cookiecutterproject_name"
docs/make.bat:130:      echo.^> qcollectiongenerator %BUILDDIR%\qthelp\cookiecutterproject_name.qhcp
docs/make.bat:132:      echo.^> assistant -collectionFile %BUILDDIR%\qthelp\cookiecutterproject_name.ghc

and (2) Docker removal that we may partially still keep here to reproduce what python venv is doing.  This may be important as the tests suite grows.  For now, it's OK to remove them, but perhaps just rephrase the commit log message to:
* Removes docker scripts temporarily from Invenio.

and we'll address this later.  (E.g. the demo site could perhaps even be moved here under a new setup.py target, or the Docker scripts moved to base... Let's keep the options open.)

@tiborsimko I've updated the PR now.

authors: lnielsen tiborsimko