text:
Integration suddenly not working

Describe the bug
A clear and concise description of what the bug is.
If possible attach the JSON info file for your devices.
Expected behavior
If applicable, a clear and concise description of what you expected to happen.
Screenshots

Environment details:

Environment (HASSIO, Raspbian, etc):
Home Assistant version installed:
Component version installed:
Last know working version:
LG device type and model with issue:
LG devices connected (list):

Output of HA logs
Paste the relavant output of the HA log here.
Retrying setup: ThinQ platform not ready
2022-12-27 11:32:19.099 WARNING (MainThread) [homeassistant.config_entries] Config entry 'LGE Devices' for smartthinq_sensors integration not ready yet: ThinQ platform not ready; Retrying in background
Additional context
Add any other context about the problem here.

May be a temporary LG service down or there are new TOS to accept in mobile application.

No one else who has this problem???

@thoompje,
Please check you log for additional message. Based on information provided I can only suppose a problem related to LG, but if there are others errors in the log I can better investigate.

@thoompje,
Please check you log for additional message. Based on information provided I can only suppose a problem related to LG, but if there are others errors in the log I can better investigate.

Hello,
thanks for answering, i have debug log enabled but the only thing what i can see in the logs:
2022-12-27 16:15:29.100 ERROR (MainThread) [homeassistant] Error doing job: Unclosed client session
2022-12-27 16:15:29.103 ERROR (MainThread) [homeassistant] Error doing job: Unclosed connector
2022-12-27 16:15:49.099 WARNING (MainThread) [homeassistant.config_entries] Config entry 'LGE Devices' for smartthinq_sensors integration not ready yet: ThinQ platform not ready; Retrying in background
2022-12-27 16:15:49.113 ERROR (MainThread) [homeassistant] Error doing job: Unclosed client session
2022-12-27 16:15:49.117 ERROR (MainThread) [homeassistant] Error doing job: Unclosed connector

I don't see any specific error, really seems a problem in LG. Did you check your mobile application? Everything is working there?

I don't see any specific error, really seems a problem in LG. Did you check your mobile application? Everything is working there?

Don't see any errors in the app, everything is working fine. Is there an workaround or things to try?

Woulb be useful if you could enable debug and provide log. Or you could just try to reconfigure the integration.

Woulb be useful if you could enable debug and provide log. Or you could just try to reconfigure the integration.

Many thanks for replying! I enabled debug logging but there is no debug log. I deleted the intergration and added it again, but no luck see screenshot.

How do you enable the debug log?

How do you enable the debug log?

I enabled the debug like this

Also failing for me since last update. I see this log
`Logger: homeassistant.components.websocket_api.http.connection
Source: custom_components/smartthinq_sensors/wideq/core_async.py:345
Integration: Home Assistant WebSocket API (documentation, issues)
First occurred: 23:29:23 (5 occurrences)
Last logged: 23:33:41
[546951289568]
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 200, in handle_call_service
await hass.services.async_call(
File "/usr/src/homeassistant/homeassistant/core.py", line 1745, in async_call
task.result()
File "/usr/src/homeassistant/homeassistant/core.py", line 1782, in _execute_service
await cast(Callable[[ServiceCall], Awaitable[None]], handler.job.target)(
File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 213, in handle_service
await service.entity_service_call(
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 678, in entity_service_call
future.result()  # pop exception if have
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 943, in async_request_call
await coro
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 715, in _handle_entity_call
await result
File "/config/custom_components/smartthinq_sensors/climate.py", line 278, in async_set_hvac_mode
await self._device.power(False)
File "/config/custom_components/smartthinq_sensors/wideq/ac.py", line 704, in power
await self.set(keys[0], keys[1], key=keys[2], value=op_value)
File "/config/custom_components/smartthinq_sensors/wideq/ac.py", line 859, in set
await super().set(
File "/config/custom_components/smartthinq_sensors/wideq/device.py", line 551, in set
await self._set_control(
File "/config/custom_components/smartthinq_sensors/wideq/device.py", line 512, in _set_control
await self._client.session.set_device_v2_controls(
File "/config/custom_components/smartthinq_sensors/wideq/core_async.py", line 1163, in set_device_v2_controls
res = await self.post2(cmd_path, payload)
File "/config/custom_components/smartthinq_sensors/wideq/core_async.py", line 1000, in post2
return await self._auth.gateway.core.lgedm2_post(
File "/config/custom_components/smartthinq_sensors/wideq/core_async.py", line 334, in lgedm2_post
return self._manage_lge_result(out, is_api_v2)
File "/config/custom_components/smartthinq_sensors/wideq/core_async.py", line 345, in _manage_lge_result
raise API2_ERRORScode
custom_components.smartthinq_sensors.wideq.core_exceptions.NotLoggedInError
`

Think I solved, disabled the integration, restarted HA and re-enabled it, then it started to work, at least for now. Maybe the crash condition has not been met yet.

Think I solved, disabled the integration, restarted HA and re-enabled it, then it started to work, at least for now. Maybe the crash condition has not been met yet.

I disabled it and enabled it again, but no luck. Also de deletion and adding again no luck. Nothing is working at all. What can I do more to investigate the issue and solve it at the end? :)

@modem The most strange thing is when i going to add the integration again it says: Success!

What i also did this morning is redownload from hacs the repository and restarted home assistant and trying to add it again. Same result. Also with 1.26.1 and 1.27.1.
Hopefully anyone has an solution for this, we can't control the AC's now from Home Assistant

We can close this one, found it! In the core_async.py i searched for the OAUTH url
OAUTH_REDIRECT_URI = f"https://kr.m.lgaccount.com/{OAUTH_REDIRECT_PATH}"
Suddenly my Unifi dream machine blocked this URL because i am using country control, i changed nothing so its really strange that it suddenly stopped working. I added South Korea to the allow list temporary so its working again.

This is interesting, also because this url should not be used anymore with last release.
@thoompje, can you confirm that you are using last release?

This is interesting, also because this url should not be used anymore with last release. @thoompje, can you confirm that you are using last release?

Really interesting then. I allowed South Korea on the Unifi and directly after it, it started working again.

I think that there are some URL returned by the API that refer to KR, not that specific URL in the constant. But this is really a good catch, I should add some comment about this in readme.
Thanks,👍

I think that there are some URL returned by the API that refer to KR, not that specific URL in the constant. But this is really a good catch, I should add some comment about this in readme. Thanks,👍

Cheers, you welcome! Have a good NYE!

authors: modem ollo69 thoompje


text:
[Feature Request]Support for LG Ovens?

Any plans for adding oven support to this integration?  I can assist if necessary.  I have a Signature Duel Oven (Gas, Elec).

Does wideq support this?

Potentially it is possible, wideq is the protocol so is just a matter to manage the property that comes from the payload. Real complexity is to implement without having an oven device.
I put this in the todo list, but my priority here is implement controls so to be able to add climate entity and control existing sensors.

Oven now is supported, I close this request

source: gharchive/issue

license_type: permissive

license_source: github-api


text:
Create incident_cls.pt using GH Actions

We need to shift the incident_cls.pt creation to an automatic process, maybe using GitHub Actions, and this process should use the current state of the database, rather than a manually downloaded incidents.csv file

This is being developed on branch "4-reduce-size-of-incident-cls"

repo: olsonadr/nlp-lambdas

license: MIT


text:
uncompleted extra_data for access_token, code, and expires in Google+

Hi, I'm trying to authenticate in my web server from a SPA application using google+. I only have one problem when the user is authenticated. I don't get the extra data in social_auth_usersocialauth table, I mean I'm getting in the extra_data field
{"code": null, "access_token": "", "expires": null, "user_id": "10181231375248323"}.

the way i'm doing it is the next.
In my SPA i'm doing
 gapi.auth.signIn({
      "clientid" : "872066331548-m61m12384ii2gs5b82tbb2qlipesum6ee.apps.googleusercontent.com",
      "cookiepolicy" : "single_host_origin",
      "callback" : this.statusChangeCallback,
      "scope": "https://www.googleapis.com/auth/plus.login https://www.googleapis.com/auth/plus.profile.emails.read"
    });

In my web server
the endpoint receive the access_token in the request that was giving by spa and do authentication
api_view(['GET'])
@permission_classes((permissions.AllowAny, ))
@psa('social:complete')
def register_by_access_token(request, backend):

    token = request.GET.get('access_token')
    user = request.backend.do_auth(access_token=token, backend=backend)
    if user:
        login(request, user)
        serialize = UserSerializer(user, context={'request': request})

        return Response(serialize.data)
    else:
        return Response('ERROR')

and the settings are

AUTHENTICATION_BACKENDS = (

    'social.backends.facebook.FacebookAppOAuth2',
    'social.backends.facebook.FacebookOAuth2',
    'social.backends.google.GooglePlusAuth'
    'django.contrib.auth.backends.ModelBackend',
)
SOCIAL_AUTH_GOOGLE_PLUS_KEY = '872066331548-###################.apps.googleusercontent.com'
SOCIAL_AUTH_GOOGLE_PLUS_SECRET = '######################'

SOCIAL_AUTH_GOOGLE_PLUS_AUTH_EXTRA_ARGUMENTS = {
      'access_type': 'offline',
      'approval_prompt': 'auto'
}
SOCIAL_AUTH_GOOGLE_PLUS_SCOPE = [
    'https://www.googleapis.com/auth/plus.login',
    'https://www.googleapis.com/auth/plus.emails.read'
]
SOCIAL_AUTH_GOOGLE_PLUS_USE_UNIQUE_USER_ID = True

SOCIAL_AUTH_PIPELINE = (
    'social.pipeline.social_auth.social_details',
    'social.pipeline.social_auth.social_uid',
    'social.pipeline.social_auth.auth_allowed',
    'social.pipeline.social_auth.social_user',
    'social.pipeline.user.get_username',
    # 'social.pipeline.mail.mail_validation',
    'social.pipeline.social_auth.associate_by_email',
    'social.pipeline.user.create_user',
    'social.pipeline.social_auth.associate_user',
    'social.pipeline.social_auth.load_extra_data',
    'social.pipeline.user.user_details',

    'social.pipeline.debug.debug'
)

What i'm doing wrong??  i'm using the similar code to authenticate with facebook and the extra_data is completed. Some help is welcome. Thanks

What version are you using? There was a fix related to access token storage when using AJAX authentication a few days ago.

I'm using 0.2.6 the last

The flow i need is based on server-side-flow as i saw there the client send an "authorization code" to the server and use it to obtain credential. The code is a one-time code that the server can exchange with Google's servers for an access token. Maybe this approach isn't supported yet in psa.

This approach resembles the default server-side OAuth2 implementation, the user clicks the login button, get's redirected to the provider where it accepts, get's redirected back to the site with a code parameter, that's then exchanged for an access_token.
In theory (this is not tested), you can call request.backend.auth_complete() in your view implementation.

authors: omab zetahernandez

repo: omab/python-social-auth


text:
fixes typo in variable name -  https_letsencrypt_enabled

I noticed that the variable name at the end of the script has an underscore, while the actual variable that is checked in the script to conditionally run doesn't have an underscore. So, uncommenting the line at the end of the script and setting it to True doesn't actually do anything.

Thanks for the fix! Travis failure is unrelated.

source: gharchive/pull-request

authors: SteveO-sudo manics

repo: ome/prod-playbooks


text:
🛑 OME gate (443) is down

In aea3a35, OME gate (443) ($OME_GATE) was down:

HTTP code: 0
Response time: 0 ms

Resolved: OME gate (443) is back up in 1d1f9d4 after 9 minutes.

repo: ome/upptime


text:
🛑 OME demo server is down

In e409fe9, OME demo server (https://demo.openmicroscopy.org) was down:

HTTP code: 0
Response time: 0 ms

Resolved: OME demo server is back up in 1bd8983 after 20 minutes.


text:
Add description prop in generateOpenApiSpec

const swaggerSpec = await generateOpenApiSpec(
  {
    ImageFileDTO,
    NewOrderImageDTO,
    GetOrdersResponseDTO,
    PaginationRequestDTO,
    GetOrdersRequestApiDTO,
    OrderDTO,
    ShortOrderDTO,
    NewOrderApiDTO,
    UpdatedOrderFieldsApiDTO,
    ValidationErrorDTO,
    AaaApiErrorDTO,
    AaaServerActionErrorDTO,
  },
  {
    securitySchemes: {
      BearerAuth: {
        type: 'http',
        scheme: 'bearer',
      },
    },
    security: [],
  }
);

swaggerSpec.info.description =
  'test description';

export { swaggerSpec };

generateOpenApiSpec does not have description prop. To have description, I have to set like that.
Can we have it as a param of generateOpenApiSpec?

Sure we can

Maybe it's even better to have whole InfoObject prop. I know that right now title and version are fetched from package.json, but it'd be good to override them if InfoObject was provided with corresponding props.

authors: GorgeousPuree omermecitoglu


text:
Can I use my own pretrained StyleGAN2-ADA?

I have trained a StyleGAN2-ADA generator on my own images and now trying different inversion methods.
My first question after reading your paper is if I can use my pretrained G and implement your code to train an encoder or if should I retrain a StyleGAN2 using psp framework.
I have trained my Generator using [https://github.com/NVlabs/stylegan3]. but for StyleGAN2-ADA not for version 3.
As far as I understood, your work is based on psp which maps Z into W+ in contrast to the original StyleGAN2 which is on W space.
So I suppose I need to train a psp first on my image and then use the trained G and follow your method.
Would be great if you can clarify this for me. Thank you very much in advance for your help.

I have trained a StyleGAN2-ADA generator on my own images and now trying different inversion methods. My first question after reading your paper is if I can use my pretrained G and implement your code to train an encoder or if should I retrain a StyleGAN2 using psp framework. I have trained my Generator using [https://github.com/NVlabs/stylegan3]. but for StyleGAN2-ADA not for version 3.
As far as I understood, your work is based on psp which maps Z into W+ in contrast to the original StyleGAN2 which is on W space. So I suppose I need to train a psp first on my image and then use the trained G and follow your method.
Would be great if you can clarify this for me. Thank you very much in advance for your help.

May I know if you have any progress in your research? I’m facing a similar situation and hope to seek your assistance.


text:
Fix relayer event query

Re-structure the event query logic in the Relayer to avoid situations where messages are not relayed until the service is restarted. I have also applied the same logic to the relevant section of the message-relayer-fast.

Codecov Report

Merging #146 (46310eb) into develop (dc7f2c1) will increase coverage by 17.79%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##           develop     #146       +/-   ##
============================================
+ Coverage    71.73%   89.52%   +17.79%
============================================
  Files           68       33       -35
  Lines         2257     1079     -1178
  Branches       335      150      -185
============================================
- Hits          1619      966      -653
+ Misses         638      113      -525

Flag
Coverage Δ

batch-submitter
?

contracts
89.52% <ø> (ø)

core-utils
?

data-transport-layer
?

message-relayer
?

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...kages/batch-submitter/src/batch-submitter/index.ts

...kages/data-transport-layer/src/utils/validation.ts

packages/batch-submitter/src/index.ts

...itter/src/batch-submitter/state-batch-submitter.ts

...ices/l1-ingestion/handlers/state-batch-appended.ts

packages/message-relayer/src/relay-tx.ts

...ckages/data-transport-layer/src/utils/contracts.ts

packages/core-utils/src/coders/index.ts

...h-submitter/src/batch-submitter/batch-submitter.ts

packages/data-transport-layer/src/utils/index.ts

... and 25 more

Continue to review full report at Codecov.

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


text:
Update copyright

ditto

test me

Build Passed :ok_hand:
You can safely merge 'update-copyright' into 'master'.

👍

authors: DavidMansolino cyberbotics-jenkins

repo: omichel/webots


text:
Upgrade truffle to newer version

Description
Seems like truffle new release 5.1.15 might solve the previous unstable migration issue:
In this PR: https://github.com/trufflesuite/truffle/pull/2808 of the change log, it claims to solve: https://github.com/trufflesuite/truffle/issues/2257
Should give it a try and make our DevOps happy 😛

This would make contract deployments less expensive!

Currently we have many failures due to the issue and it's costing us many ETH for re-trying the deployments. Is there any way we can try the new version?

authors: arthurk boolafish jbunce

repo: omisego/plasma-contracts


text:
Clean and update README.md

Closes #39
(Almost) complete rewrite of README.md with more complete CLI documentation.
Comments, edits, reviews welcome.

Tried install with this Readme.
Got stucked a little bit at:

leveldb
solidity installation

I think leveldb should be added to pre-installation dependancy as well.
And it would be nice to have some solidity installation guide for mac as well (like the one in another PR). The link for Solidity 0.4.18 doesn't have mac download : (

@boolafish Thanks for the feedback, I went ahead and updated the README to include better install notes for leveldb and solidity.

Whoops, you are correct! Thanks.

Thanks! Fixed.

@kfichter Read it over, and it looks good!  Merging.

authors: DavidKnott boolafish kfichter

repo: omisego/plasma-mvp


text:
[concept] AI Copilot

Currently the idea of copilot in tools are gaining popularity
I was wondering what mind mapping folks think about this
Below is a video form superus which demonstrates the concept
Watch Video
Another is a todo list that does itself for you
Personally when I run my-mind locally I set up a process called, aimon.sh, which monitors changes in a map that I make when I hit save (saved to nosDAV and it will

run a command
give myself a payment reward
use AI to expand questions
use NosDAV pubsub to replace firebase with an open system for realtime, collaborative, payments enabled maps

I dont yet have todolists that do themselves, but I think that would be kind of cool, and head towards AGI for mind maps.
I am wondering if there is an appetite for any of these features.

I am considering modifying my-mind to muck around with anythingllm which offers a pretty easy to use API for this purpose.

I reckon I could probably make some kind of plugin that hooks into subscribers in pubsub.ts (e.g. "item-change" events) to listen for changes to nodes. I'd probably keep it in a separate project and not pollute the lightweight code here. Thinking I might expose expose subscribers on a global scope rather than a module scope so I can access it from another script without needing to create some kind of plugin system.

There already is such code in there for firebase updates.  However firebase is proprietary.
I prefer a pub/sub solution over websockets called nostr:
https://nostr.how/en/what-is-nostr
Which does pub/sub over websockets.  More background on nostr here.  And it might be possible to apply for an open source grant to integrate my mind and nostr here

Yeah, I can see this in the firebase one:
pubsub.subscribe("firebase-list", this);
pubsub.subscribe("firebase-change", this);
...
case "firebase-change":
if (data) {
pubsub.unsubscribe("item-change", this);
app.currentMap.mergeWith(data);
pubsub.subscribe("item-change", this);
} else { /* FIXME */
console.log("remote data disappeared");
}
That's a good place to start. Thanks.

Yeah I like the idea of your nostr pub/sub backend. Probably go with something like that to keep it easy and use the firebase code for a bit of help.

@rquast awesome!  I would be happy to run a nostr relay if you want to test.  But there are a few 100 here
A nostr relay also be run with a single line of code if you have docker:
# docker pull scsibug/nostr-rs-relay
docker run -p 4445:8080 scsibug/nostr-rs-relay

authors: arkin0x melvincarvalho rquast

repo: ondras/my-mind

license: mit

license_source: bigquery


text:
Loads a blank screen in every browser

I just pulled down the new changes and it doesn't load in any browser. I reverted to sha c831747 and it works in Firefox

Damn. Well, I will investigate + fix - but not before Monday, as I will be gone for the whole weekend.

The problem is with toggle.js. It is included in the index.html, but not actually there.

Yeah, I forgot to git add that file after splitting the app into individual components.
It should be noted, though, that the latest commit (the one that does not really work) does not bring any radially new features (and therefore one has no real motivation to pull it). It is a scaffolding for a reworked storage system that will allow greater flexibility with remote storage servers.

Fixed in https://github.com/ondras/wwwsqldesigner/commit/dcea4c24e5efcb66cefb18eec8e7c9b596000867.

repo: ondras/wwwsqldesigner


text:
Some Warning and a Fatal Error

I cloned the repo into the Composer/vendor folder.  I run  on Command Prompt
php converter.php "C:/User/..../..../ Php7CodeFolder" "C:/Users/.../..../Php5CodeFolder"
It give me some "Warning"  -->

mkdir(): Invalid argument in C:\Users..........\Composer\vendor\php7backport\src\Bouda\Php7Backport\DirectoryBackporter.php on line 31

and a "Fatal Error" -->

Uncaught Error: Class 'PhpParser\Lexer\Emulative' not found in C:\Users.........\Composer\vendor\php7backport\src\Bouda\Php7Backport\Backporter.php:21

I don't understand why and how to resolve these errors.
Can you give me some help?

Hi Wakasaki, I just returned from holiday, sorry for the delay.

Uncaught Error: Class 'PhpParser\Lexer\Emulative' not found in

Did you run composer install?

mkdir(): Invalid argument in

I will look into it. It may be a bug. It is possible it cannot create nested directories.

authors: Wakasaki ondrejbouda


text:
should L0 have in-order queues?

L0 has had from the beginning only out-of-order queues, and layers above, like SYCL, have implemented in-order queues by using synchronization primitives like events and barriers.
Although using event or barriers is functionally correct, performance may vary on different generations of the same devices depending on the method used. One way to fix this is to have layers above like SYCL to implement device-dependent in-order queues, however, other more practical option, is to let the L0 driver implementation to directly implement the in-order queue as efficient as possible.
are there other scenarios where in-order queues are desired? or are there any cons on adding this to the spec?

From my point of view it should.
Driver knowing that it works with in order queue is beneficial and it can apply optimizations that are not possible without this knowledge.
In order execution is also well established standard in the industry, so a lot of applicaitons uses it.
Having efficient driver implementation for this is paramount.

I concur with @MichalMrozek that in-order can be seen mostly as a defacto. I was mostly thinking to provide a case where the SYCL queue construction is in-order and if the underlying L0 queue objects adopt some form of in-order fashion same as the upstream SYCL queue:  DAG construction by the scheduler, the submission of kernels, kernel-scheduling hints can default to oldest-first, dependency tracking, barriers/fences and their associated book-keeping might get simpler, might enable optimizations.
In reg to optimizations: I am not certain if it is beneficial for L0 to provide the optimizations or the driver to incorporate these.
More importantly helps applications which has hundreds of "low-runtime" kernel submissions in-order, math libraries and all the projects that are porting from CUDA to SYCL and adopt SYCL in-order as a the reason are some uses cases. Since these types of kernels are flagged to be in-order, any book-keeping overhead with out-of-order can be viewed as an additional overhead.

we can have a flag either per queue or per device. logically, it should be per queue, since it would give most flexibility to the application.
in practice, it may introduce extra complexity, so having it global per device would be easier for the implementation. If an application wants "out of order", it would need to use separate queues.

In Level Zero entity that needs to ensure in-order is command list , not command queue.
Hence we need command list property to enforce in order start & completion of appended commands.

repo: oneapi-src/level-zero-spec


text:
Intel Extension for Scikit-learn getting started sample

Adding a New Sample(s)
Description
New intel extension for a scikit-learn sample that does digit recognition using SVM classifier.
Checklist
Administrative

[x] Review sample design with the appropriate Domain Expert: Rachel Oberman
[x] If you have any new dependencies/binaries, inform the oneAPI Code Samples Project Manager: @JoeOster

Code Development

[x] Implement coding guidelines and ensure code quality. see wiki for details
[x] Adhere to readme template
[x] Enforce format via clang-format config file
[x] Adhere to sample.json specification. https://github.com/oneapi-src/oneAPI-samples/wiki/sample-json-specification
[x] Ensure/create CI test configurations for sample (ciTests field) https://github.com/oneapi-src/oneAPI-samples/wiki/sample-json-ci-test-object
[x] Run jsonlint on sample.json to verify json syntax. www.jsonlint.com

Security and Legal

[x] N/A OSPDT Approval (see @JoeOster for assistance)
[ ] Bandit Scans (Python only)
[X] Virus scan

Review

[ ] Review readme with Tom Lenth(@tomlenth) and/or Joe Oster(@JoeOster)
[X] Tested using Dev Cloud when applicable

@tomlenth please review the readme

@asirvaiy - Please supply the bandit report

Please note conda is failing on test machines, no eta on fix, merging despite the issues as its a env issue

authors: JoeOster asirvaiy

repo: oneapi-src/oneAPI-samples


text:
Update Listed required Python version

As of this time, ansible==9.0.1 requires Python >= 3.10

sudo apt-get install python3.10

sudo apt-get install python3.10-venv


text:
bring setup steps under one L2 heading

For easier reference and to make room for other L2 headings such as "Usage" and "FAQs".

Maybe instead of Step we use a different name since there would be substeps and subsubsteps?

We could use Stage, but there are no L4 headings that need to be referred to as substeps. Your call.

The substeps would be the ones with letters, e.g. 2a, 2b, 2c, etc..
Stage or section is probably fine unless you come up with a better name

Stage sounds good. Section sounds unnatural to me, e.g. "There are 6 sections to getting a Flux-managed cluster up and running."
One note on substeps: a good way to refer to them would be "Step 2b". And subsubsteps: "Step 3c(iii)"


text:
🛑 Identity Plus (EU) is down

In f0abbe8, Identity Plus (EU) (https://eu.onetimesecret.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Identity Plus (EU) is back up in b1a2fc5 after 25 minutes.

repo: onetimesecret/status


text:
undefined is not an object(evaluating 'container.setState')

Hai, I run your demo project,and check in device it working fine, But in index.ios.js, i added the some code for navigator, added some form code init.when click on signIn button i want to show the webRtc screen for that screen i just copied the main.js file code in RTcWebdemo project and added in my code, here is my code
index.ios.js
if (!window.navigator.userAgent) {
  window.navigator.userAgent = "react-native";
}
'use strict';
import React,{Component} from 'react';
var SignIn = require('./SignIn');
import {
  AppRegistry,
  StyleSheet,
  Navigator,
  AsyncStorage,
} from 'react-native';
class RCTWebRTCDemo extends Component {
  render() {
    return (
            <Navigator
                initialRoute={{
                  component:SignIn  //component declaration
                }}
                configureScene={(route) => ({
                  ...Navigator.SceneConfigs.HorizontalSwipeJump,
                  gestures: false
                })}
                renderScene={(route, navigator) =>{
                  return <route.component navigator={navigator} {...route.passProps} />;
                }}/>
        );
  }
};

signIn.js
onSignin(){
    this.props.navigator.push({
      component: main
    })
}

When click on signIn button of the below image calling the above function in main component i added the main.js file code

but when i run project before clicking on signIn button, It shows some error like this

please give me suggestions that how to resolve this

make sure you set container = this in the main WebRTCDEMO Component's ComponentDidMount.
my suggestion would be:  try to understand demo main.js logic, and applied it in to your own logic.

Hi  @shaikhussian
I am also facing same issue . If u find the solution of this issue then please help me  to resolve this .
Thanks

Would someone have the time to write the demo using React.Component instead of React.createClass and make it easier to understand? The official examples from OpenWebRTC are pretty good.

@davidperrenoud
Have you worked on this . if yes then pls provide solution to above issue.
Thanks

Yes, the easiest solution (not the best one) would be to build your app like the RCTWebRTCdemo with React.createClass:
https://github.com/oney/RCTWebRTCDemo/blob/master/main.js#L232
As @zxcpoiu said, you can then map the container variable to this in componentDidMount:
https://github.com/oney/RCTWebRTCDemo/blob/master/main.js#L247
(A prettier solution would be to put the sockets and WebRTC functions in two separate files and the React.Component in another file.)

Yes, i did same .
"
Yes, the easiest solution (not the best one) would be to build your app
like the RCTWebRTCdemo with React.createClass:
https://github.com/oney/RCTWebRTCDemo/blob/master/main.js#L232
As @zxcpoiu https://github.com/zxcpoiu said, you can then map the
container variable to this in componentDidMount:
https://github.com/oney/RCTWebRTCDemo/blob/master/main.js#L247
"
but still getting same issue when i started app .
On Thu, Sep 22, 2016 at 7:57 PM, David Perrenoud notifications@github.com
wrote:

Yes, the easiest solution (not the best one) would be to build your app
like the RCTWebRTCdemo with React.createClass:
https://github.com/oney/RCTWebRTCDemo/blob/master/main.js#L232
As @zxcpoiu https://github.com/zxcpoiu said, you can then map the
container variable to this in componentDidMount:
https://github.com/oney/RCTWebRTCDemo/blob/master/main.js#L247
(A prettier solution would be to put the sockets and WebRTC functions in
two separate files and the React.Component in another file.)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/oney/react-native-webrtc/issues/128#issuecomment-248919493,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AQlFJGis5hr4NtjZhLUFnKSdFNnvgSwxks5qspBDgaJpZM4Jxb09
.

It simply means you did not set it correctly.
it's a JS/react-native coding syntax issue.
as @davidperrenoud
you may want to try export your component, maybe as a singleton, and manipulate it in another file ( your main app.js with main logic )

Hi
I am also getting the same issue.
Please tell how to solve this one..

Put your code "socket.on" into componantdidMount function .
On Tue, Oct 18, 2016 at 4:28 PM, swaroopa94 notifications@github.com
wrote:

Hi
I am also getting the same issue.
Please tell how to solve this one..
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/oney/react-native-webrtc/issues/128#issuecomment-254474492,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AQlFJD3gzXjFfRpE33a2ocmilyzK59BKks5q1KZdgaJpZM4Jxb09
.

this is how I solved the problem: https://stackoverflow.com/questions/40109937/undefined-is-not-an-object-evaluating-container-setstate/40974201#40974201

thanks for the link @LoseTheQuit
for anyone who interest in app structure, see #167 as well

Nothing actionable for the plugin itself, closing.

authors: LoseTheQuit davidperrenoud rohitgupta87410 saghul shaikhussian swaroopa94 zxcpoiu

repo: oney/react-native-webrtc


text:
muting/unmuting remote streams

updates mediaStreamTrackSetEnabled to work for remote tracks as well as by local tracks.
so setting .enabled on a remote track in js will mute / unmute the track if it is audio.
applies to issues #338 and #179

@ippa yes this solution worked on 1.58.3 for muting remote audio tracks (local tracks already worked).  I updated to fix the merge conflict in 1.63.0.
With this change just call find the audio track in javascript (e.g. track = stream.getAudioTracks()[0]) and set track.enabled = false or track.enabled = true.
It's not tested with video tracks however.  I did see that in the jitsi fork there's a similar commit that  can mute video tracks too.  https://github.com/jitsi/react-native-webrtc/commit/49f678eed157ba95cbd7ec8bc19af1b002bb1513
Was wondering if perhaps that or the effort for M63 might have been keeping this from being merged.

I'm coming across an issue with this where if I mute both the local and remote tracks then the audiosession on ios gets deactivated, it then gets activated again when you unmute but the audio never comes back. Investigating some more

Sorry, this has fallen through the cracks again :-/ Can you please rebase? I'll include it for the 69 release.

Fixed the conflict, should be good to go now.

Actually it needs one fix first

Hey @weberjc, seems like the iOS part is missing now?

@saghul it looks like the ios part is still there, however i'm not in a position to test it at the moment.  It gets those remoteTrack vars from the other files like WebRTCModule+RTCPeerConnection.m.

I see it again now. I'll give it a test and merge it.

Is there a reason why this PR is closed or some alternative solution has been added to library itself?

authors: akashkrshukla danjenkins saghul weberjc


text:
eth_getLog() returns null instead of list if there are no transactions

example:
curl -XPOST 'https://testnet.evm.nodes.onflow.org' -H "Content-Type: application/json" -d '{"jsonrpc":"2.0","id":1318572,"method":"eth_getLogs","params":[{"blockHash":"0x4967b45f073cb74e750536d41fdb70ae3923d8a151abdbef25e4fd77d27fe253","address": ["0x0000000071727de22e5e9d8baf0edac6f37da032"],"topics": ["0x2da466a7b24304f47e87fa2e1e5a81b9831ce54fec19055ce277ca2f39ba42c4","0x49628fd1471006c1482da88028e9ce4dbb080b815c9b0344d39e5a8e6ec1419f","0xd1c19fbcd4551a5edfb66d43d2e337c04837afda3482b42bdf569a8fccdae5fb"]}]}' | jq
return:
{
  "jsonrpc": "2.0",
  "id": 1318572,
  "result": null
}

Problem
should return empty list instead of null

Completed by https://github.com/onflow/flow-evm-gateway/pull/697

repo: onflow/flow-evm-gateway


text:
invalid contract: Checking failed, not very helpfull error message

Instructions
When trying to deploy a contract that used to work https://github.com/versus-flow/auction-flow-contract/blob/upgrade-flow/contracts/Auction.cdc i now get an error that is not helpfull
Problem
The error message says:
DEBU[0079] ✉   Transaction submitted                   txID=468e7ba9ec94691de9d59303dc135150fe83dfef1859c61ccde4d91287673f48
ERROR Execution failed:
invalid contract: Checking failed

WARN[0079] ❗  Transaction reverted    ```

### Steps to Reproduce

1. Check out https://github.com/versus-flow/auction-flow-contract/tree/upgrade-flow
2. Use v0.11.2 of the flow emulator
3. In one terminal run ```make emulator```
4. In another terminal run ```make demo```

### Acceptance Criteria

There is an error message thrown that makes it easier to understand what is wrong with the contract

moved to cadence repo.

Thanks @bjartek!

authors: bjartek psiemens

repo: onflow/flow-go-sdk


text:
Language support for F# and Elixir?

I'm about to purchase a License for onivim2 :D
Looks so interesting off the bat but I have some questions such as support for 2 FP languages that  I use.
Count on me to chip in helping for issues, I like the ReasonML/Ocaml language ;)

Currently, the only real language support we have is syntax highlights. We don't bundle any for F# or Elixir, but it is just as simple as copying the VSCode ones over in the extensions folder.
Once we start to get LSP and code extension support, then it will broadly be the same. There won't be any out of the box support, but there will be the (hopefully) full set of code extensions that work over there, as well as some of the vim ones, so installing a plugin will give as much support as you'd reasonably expect from those two editors.

authors: CrossR Kavignon


text:
Upgrade ONNX-MLIR to ONNX v1.12.0 release.

@AlexandreEichenberger @chentong319 @hamptonm1 @cjvolzka
ONNX release v1.12.0 has been made available earlier this year.  Detail for the updates included are described on the ONNX releases web page https://github.com/onnx/onnx/releases.
The  ai.onnx opset version increased to 17 with the new operators: SequenceMap, LayerNormalization, DFT, HannWindow, HammingWindow, BlackmanWindow, MelWeightMatrix, and STFT.
The Scan operator was updated to remove an unused type constraint, but the version remains as opset 16.
Also included in the release are shape inference enhancements, bug fixes, infrastructure improvements, documentation updates, and wheel changes.
Let’s use this issue is to discuss moving to ONNX v1.12.0.  We plan on working on this without initially providing support for the new operators.
Note that the TreeEnsembleClassifier and TreeEnsembleRegressor operators show up as version 1 in ONNX-MLIR but were updated to version 3 in ONNX v1.11.0.

The SupportedONNXOps-cpu.md document at https://github.com/onnx/onnx-mlir/blob/main/docs/SupportedONNXOps-cpu.md states that TreeEnsembleClassifier and TreeEnsembleRegressor are unsupported.  Is the document correct?  Should these be updated to version 3 in ONNX-MLIR when we move ONNX to v1.12.0?

@mikeessen That is correct, we currently don't have code that lower these ops to CPU reference code. We typically mention a version only for the ops we support.
If some of these ops are important to your projects, we encourage folks to contribute their implementations.

@mikeessen That is correct, we currently don't have code that lower these ops to CPU reference code. We typically mention a version only for the ops we support.
If some of these ops are important to your projects, we encourage folks to contribute their implementations.

This looks good to me @mikeessen! Thanks for putting this together. Also @cjvolzka is it important to support these ops that @mikeessen mentioned or are we fine with what we are inheriting from onn-xmlir ?

PR #1835 added the new Ops into onnx-mlir's ONNX dialect definition. Further implementation support is needed

PR #1835 added the new Ops into onnx-mlir's ONNX dialect definition. Further implementation support is needed

Thanks for the information.... I am assuming @mikeessen will still update the documentation for this?

@hamptonm1 @chentong319 Yes, I will update SupportedONNXOps-cpu.md for this.

@hamptonm1 @chentong319 Yes, I will update SupportedONNXOps-cpu.md for this.

FYI @philass so you do not have to do duplicate work :)

Closing issue as completed as onnx-mlir has moved to onnx 1.12

repo: onnx/onnx-mlir


text:
compile error

╰─ cmake --build . -j 1                                                                                ─╯
[1/696] Running gen_proto.py on onnx/onnx.in.proto
Processing /Users/unicorn/workspace/onnx-mlir/third_party/onnx/onnx/onnx.in.proto
Writing /Users/unicorn/workspace/onnx-mlir/build/third_party/onnx/onnx/onnx-ml.proto
Writing /Users/unicorn/workspace/onnx-mlir/build/third_party/onnx/onnx/onnx-ml.proto3
generating /Users/unicorn/workspace/onnx-mlir/build/third_party/onnx/onnx/onnx_pb.py
[3/696] Running gen_proto.py on onnx/onnx-operators.in.proto
Processing /Users/unicorn/workspace/onnx-mlir/third_party/onnx/onnx/onnx-operators.in.proto
Writing /Users/unicorn/workspace/onnx-mlir/build/third_party/onnx/onnx/onnx-operators-ml.proto
Writing /Users/unicorn/workspace/onnx-mlir/build/third_party/onnx/onnx/onnx-operators-ml.proto3
generating /Users/unicorn/workspace/onnx-mlir/build/third_party/onnx/onnx/onnx_operators_pb.py
[5/696] Running gen_proto.py on onnx/onnx-data.in.proto
Processing /Users/unicorn/workspace/onnx-mlir/third_party/onnx/onnx/onnx-data.in.proto
Writing /Users/unicorn/workspace/onnx-mlir/build/third_party/onnx/onnx/onnx-data.proto
Writing /Users/unicorn/workspace/onnx-mlir/build/third_party/onnx/onnx/onnx-data.proto3
generating /Users/unicorn/workspace/onnx-mlir/build/third_party/onnx/onnx/onnx_data_pb.py
[7/696] Building CXX object third_party/onnx/CMakeFiles/onnx_proto.dir/onnx/onnx-ml.pb.cc.o
FAILED: third_party/onnx/CMakeFiles/onnx_proto.dir/onnx/onnx-ml.pb.cc.o
/usr/bin/c++ -DONNX_API="attribute((visibility("default")))" -DONNX_ML=1 -DONNX_NAMESPACE=onnx -D_DEBUG -D_GLIBCXX_ASSERTIONS -D_LIBCPP_ENABLE_ASSERTIONS -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -I/Users/unicorn/workspace/llvm-project/llvm/include -I/Users/unicorn/workspace/llvm-project/build/include -I/Users/unicorn/workspace/llvm-project/mlir/include -I/Users/unicorn/workspace/llvm-project/build/tools/mlir/include -I/Users/unicorn/workspace/onnx-mlir/build/third_party/onnx -isystem /opt/homebrew/include -fPIC -fvisibility-inlines-hidden -Werror=date-time -Werror=unguarded-availability-new -Wall -Wextra -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wmissing-field-initializers -Wimplicit-fallthrough -Wcovered-switch-default -Wno-noexcept-type -Wnon-virtual-dtor -Wdelete-non-virtual-dtor -Wsuggest-override -Wstring-conversion -Wmisleading-indentation -Wctad-maybe-unsupported -fdiagnostics-color -w -Wnon-virtual-dtor -g -O0 -std=gnu++11 -arch arm64 -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX13.3.sdk -fPIC -fvisibility=hidden -fvisibility-inlines-hidden   -D_DEBUG -D_GLIBCXX_ASSERTIONS -D_LIBCPP_ENABLE_ASSERTIONS -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -MD -MT third_party/onnx/CMakeFiles/onnx_proto.dir/onnx/onnx-ml.pb.cc.o -MF third_party/onnx/CMakeFiles/onnx_proto.dir/onnx/onnx-ml.pb.cc.o.d -o third_party/onnx/CMakeFiles/onnx_proto.dir/onnx/onnx-ml.pb.cc.o -c /Users/unicorn/workspace/onnx-mlir/build/third_party/onnx/onnx/onnx-ml.pb.cc
In file included from /Users/unicorn/workspace/onnx-mlir/build/third_party/onnx/onnx/onnx-ml.pb.cc:4:
In file included from /Users/unicorn/workspace/onnx-mlir/build/third_party/onnx/onnx/onnx-ml.pb.h:11:
/opt/homebrew/include/google/protobuf/port_def.inc:205:1: error: static_assert failed due to requirement '201103L >= 201402L' "Protobuf only supports C++14 and newer."
static_assert(PROTOBUF_CPLUSPLUS_MIN(201402L), "Protobuf only supports C++14 and newer.");
^             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from /Users/unicorn/workspace/onnx-mlir/build/third_party/onnx/onnx/onnx-ml.pb.cc:4:
In file included from /Users/unicorn/workspace/onnx-mlir/build/third_party/onnx/onnx/onnx-ml.pb.h:24:
In file included from /opt/homebrew/include/google/protobuf/io/coded_stream.h:130:
In file included from /opt/homebrew/include/google/protobuf/stubs/common.h:44:
In file included from /opt/homebrew/include/absl/strings/string_view.h:39:
In file included from /opt/homebrew/include/absl/base/attributes.h:37:
In file included from /opt/homebrew/include/absl/base/config.h:86:
/opt/homebrew/include/absl/base/policy_checks.h:79:2: error: "C++ versions less than C++14 are not supported."
#error "C++ versions less than C++14 are not supported."
^
In file included from /Users/unicorn/workspace/onnx-mlir/build/third_party/onnx/onnx/onnx-ml.pb.cc:4:
In file included from /Users/unicorn/workspace/onnx-mlir/build/third_party/onnx/onnx/onnx-ml.pb.h:24:
In file included from /opt/homebrew/include/google/protobuf/io/coded_stream.h:130:
In file included from /opt/homebrew/include/google/protobuf/stubs/common.h:46:
In file included from /opt/homebrew/include/google/protobuf/stubs/port.h:45:
/opt/homebrew/include/google/protobuf/port_def.inc:205:1: error: static_assert failed due to requirement '201103L >= 201402L' "Protobuf only supports C++14 and newer."
static_assert(PROTOBUF_CPLUSPLUS_MIN(201402L), "Protobuf only supports C++14 and newer.");
^             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from /Users/unicorn/workspace/onnx-mlir/build/third_party/onnx/onnx/onnx-ml.pb.cc:4:
In file included from /Users/unicorn/workspace/onnx-mlir/build/third_party/onnx/onnx/onnx-ml.pb.h:24:
In file included from /opt/homebrew/include/google/protobuf/io/coded_stream.h:130:
In file included from /opt/homebrew/include/google/protobuf/stubs/common.h:56:
/opt/homebrew/include/google/protobuf/port_def.inc:205:1: error: static_assert failed due to requirement '201103L >= 201402L' "Protobuf only supports C++14 and newer."
static_assert(PROTOBUF_CPLUSPLUS_MIN(201402L), "Protobuf only supports C++14 and newer.");
^             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from /Users/unicorn/workspace/onnx-mlir/build/third_party/onnx/onnx/onnx-ml.pb.cc:4:
In file included from /Users/unicorn/workspace/onnx-mlir/build/third_party/onnx/onnx/onnx-ml.pb.h:24:
In file included from /opt/homebrew/include/google/protobuf/io/coded_stream.h:132:
In file included from /opt/homebrew/include/absl/log/absl_check.h:38:
In file included from /opt/homebrew/include/absl/log/internal/check_impl.h:19:
In file included from /opt/homebrew/include/absl/log/internal/check_op.h:37:
In file included from /opt/homebrew/include/absl/log/internal/strip.h:24:
In file included from /opt/homebrew/include/absl/log/internal/log_message.h:41:
In file included from /opt/homebrew/include/absl/log/log_entry.h:36:
In file included from /opt/homebrew/include/absl/types/span.h:69:
/opt/homebrew/include/absl/types/internal/span.h:119:21: error: no template named 'remove_const_t' in namespace 'std'; did you mean simply 'remove_const_t'?
using Container = std::remove_const_t;
^~~~~
/opt/homebrew/include/absl/meta/type_traits.h:592:1: note: 'remove_const_t' declared here
using remove_const_t = typename std::remove_const::type;
^
In file included from /Users/unicorn/workspace/onnx-mlir/build/third_party/onnx/onnx/onnx-ml.pb.cc:4:
In file included from /Users/unicorn/workspace/onnx-mlir/build/third_party/onnx/onnx/onnx-ml.pb.h:24:
In file included from /opt/homebrew/include/google/protobuf/io/coded_stream.h:132:
In file included from /opt/homebrew/include/absl/log/absl_check.h:38:
In file included from /opt/homebrew/include/absl/log/internal/check_impl.h:19:
In file included from /opt/homebrew/include/absl/log/internal/check_op.h:37:
In file included from /opt/homebrew/include/absl/log/internal/strip.h:24:
In file included from /opt/homebrew/include/absl/log/internal/log_message.h:41:
In file included from /opt/homebrew/include/absl/log/log_entry.h:36:
In file included from /opt/homebrew/include/absl/types/span.h:69:
/opt/homebrew/include/absl/types/internal/span.h:130:24: error: no template named 'enable_if_t' in namespace 'std'; did you mean simply 'enable_if_t'?
using EnableIfIsView = std::enable_if_t<IsView::value, int>;
^~~~~
/opt/homebrew/include/absl/meta/type_traits.h:656:1: note: 'enable_if_t' declared here
using enable_if_t = typename std::enable_if<B, T>::type;
^
In file included from /Users/unicorn/workspace/onnx-mlir/build/third_party/onnx/onnx/onnx-ml.pb.cc:4:
In file included from /Users/unicorn/workspace/onnx-mlir/build/third_party/onnx/onnx/onnx-ml.pb.h:24:
In file included from /opt/homebrew/include/google/protobuf/io/coded_stream.h:132:
In file included from /opt/homebrew/include/absl/log/absl_check.h:38:
In file included from /opt/homebrew/include/absl/log/internal/check_impl.h:19:
In file included from /opt/homebrew/include/absl/log/internal/check_op.h:37:
In file included from /opt/homebrew/include/absl/log/internal/strip.h:24:
In file included from /opt/homebrew/include/absl/log/internal/log_message.h:41:
In file included from /opt/homebrew/include/absl/log/log_entry.h:36:
In file included from /opt/homebrew/include/absl/types/span.h:69:
/opt/homebrew/include/absl/types/internal/span.h:133:27: error: no template named 'enable_if_t' in namespace 'std'; did you mean simply 'enable_if_t'?
using EnableIfNotIsView = std::enable_if_t<!IsView::value, int>;
^~~~~
/opt/homebrew/include/absl/meta/type_traits.h:656:1: note: 'enable_if_t' declared here
using enable_if_t = typename std::enable_if<B, T>::type;
^
In file included from /Users/unicorn/workspace/onnx-mlir/build/third_party/onnx/onnx/onnx-ml.pb.cc:4:
In file included from /Users/unicorn/workspace/onnx-mlir/build/third_party/onnx/onnx/onnx-ml.pb.h:24:
In file included from /opt/homebrew/include/google/protobuf/io/coded_stream.h:132:
In file included from /opt/homebrew/include/absl/log/absl_check.h:38:
In file included from /opt/homebrew/include/absl/log/internal/check_impl.h:19:
In file included from /opt/homebrew/include/absl/log/internal/check_op.h:37:
In file included from /opt/homebrew/include/absl/log/internal/strip.h:24:
In file included from /opt/homebrew/include/absl/log/internal/log_message.h:43:
/opt/homebrew/include/absl/strings/internal/has_absl_stringify.h:46:8: error: no template named 'enable_if_t' in namespace 'std'; did you mean simply 'enable_if_t'?
T, std::enable_if_t<std::is_void<decltype(AbslStringify(
^~~~~
/opt/homebrew/include/absl/meta/type_traits.h:656:1: note: 'enable_if_t' declared here
using enable_if_t = typename std::enable_if<B, T>::type;
^
In file included from /Users/unicorn/workspace/onnx-mlir/build/third_party/onnx/onnx/onnx-ml.pb.cc:4:
In file included from /Users/unicorn/workspace/onnx-mlir/build/third_party/onnx/onnx/onnx-ml.pb.h:24:
In file included from /opt/homebrew/include/google/protobuf/io/coded_stream.h:134:
In file included from /opt/homebrew/include/absl/strings/cord.h:78:
In file included from /opt/homebrew/include/absl/container/inlined_vector.h:53:
In file included from /opt/homebrew/include/absl/container/internal/inlined_vector.h:30:
In file included from /opt/homebrew/include/absl/container/internal/compressed_tuple.h:40:
/opt/homebrew/include/absl/utility/utility.h:164:12: error: no member named 'in_place_t' in namespace 'std'
using std::in_place_t;
~~~~~^
/opt/homebrew/include/absl/utility/utility.h:165:12: error: no member named 'in_place' in namespace 'std'
using std::in_place;
~~~~~^
/opt/homebrew/include/absl/utility/utility.h:181:12: error: no member named 'in_place_type' in namespace 'std'
using std::in_place_type;
~~~~~^
/opt/homebrew/include/absl/utility/utility.h:182:12: error: no member named 'in_place_type_t' in namespace 'std'
using std::in_place_type_t;
~~~~~^
/opt/homebrew/include/absl/utility/utility.h:198:12: error: no member named 'in_place_index' in namespace 'std'
using std::in_place_index;
~~~~~^
/opt/homebrew/include/absl/utility/utility.h:199:12: error: no member named 'in_place_index_t' in namespace 'std'
using std::in_place_index_t;
~~~~~^
In file included from /Users/unicorn/workspace/onnx-mlir/build/third_party/onnx/onnx/onnx-ml.pb.cc:4:
In file included from /Users/unicorn/workspace/onnx-mlir/build/third_party/onnx/onnx/onnx-ml.pb.h:24:
In file included from /opt/homebrew/include/google/protobuf/io/coded_stream.h:134:
In file included from /opt/homebrew/include/absl/strings/cord.h:78:
In file included from /opt/homebrew/include/absl/container/inlined_vector.h:53:
In file included from /opt/homebrew/include/absl/container/internal/inlined_vector.h:30:
/opt/homebrew/include/absl/container/internal/compressed_tuple.h:107:36: error: no type named 'in_place_t' in namespace 'absl'
explicit constexpr Storage(absl::in_place_t, V&& v)
~~~~~~^
/opt/homebrew/include/absl/container/internal/compressed_tuple.h:120:36: error: no type named 'in_place_t' in namespace 'absl'
explicit constexpr Storage(absl::in_place_t, V&& v)
~~~~~~^
/opt/homebrew/include/absl/container/internal/compressed_tuple.h:143:48: error: no type named 'in_place_t' in namespace 'absl'
explicit constexpr CompressedTupleImpl(absl::in_place_t, Vs&&... args)
~~^
/opt/homebrew/include/absl/container/internal/compressed_tuple.h:144:24: error: no member named 'in_place' in namespace 'absl'; did you mean 'isspace'?
: Storage<Ts, I>(absl::in_place, absl::forward(args))... {}
^~
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX13.3.sdk/usr/include/_ctype.h:267:1: note: 'isspace' declared here
isspace(int _c)
^
In file included from /Users/unicorn/workspace/onnx-mlir/build/third_party/onnx/onnx/onnx-ml.pb.cc:4:
In file included from /Users/unicorn/workspace/onnx-mlir/build/third_party/onnx/onnx/onnx-ml.pb.h:24:
In file included from /opt/homebrew/include/google/protobuf/io/coded_stream.h:134:
In file included from /opt/homebrew/include/absl/strings/cord.h:78:
In file included from /opt/homebrew/include/absl/container/inlined_vector.h:53:
In file included from /opt/homebrew/include/absl/container/internal/inlined_vector.h:30:
/opt/homebrew/include/absl/container/internal/compressed_tuple.h:155:48: error: no type named 'in_place_t' in namespace 'absl'
explicit constexpr CompressedTupleImpl(absl::in_place_t, Vs&&... args)
~~~~~~^
fatal error: too many errors emitted, stopping now [-ferror-limit=]
20 errors generated.
ninja: build stopped: subcommand failed.

static_assert(PROTOBUF_CPLUSPLUS_MIN(201402L), "Protobuf only supports C++14 and newer.");

It seems that your c++ version is too old.
onnx-mlir has set(CMAKE_CXX_STANDARD 17)

I believe the problem is that you're using too new protobuf. We compile protobuf with c++11 so we cannot compile the newest protobuf. We build with the old protobuf 3.20.3, see:
https://github.com/onnx/onnx-mlir/blob/main/docker/Dockerfile.llvm-project#L66
If you can't move to a lower version of protobuf on your system you can try to build protobuf from source, like it's done in that docker file. (If you're on MacOS you need to do a few things different. And if you have a Mac with M1 or M2 chip, then you need to apply a this patch to 3.20.3.)

it works thank you; I forget to reply


text:
Only update the output shape if the infered shape is better - unary elementwise ops

Currently our shape inference always overwrites the output shape with a new shape. Sometimes, shape inference has not been powerful enough to infer static dimensions.
Meanwhile, in many onnx models, outputs of ONNX ops have static shape or partially static shape. In such cases, we should respect the existing shape and only update the output shape if the inferred shape is better, for example, the inferred shape can infer a static dimension.
This patch adds a function to check whether the inferred shape is better than the existing shape or not, and it applies the function to the shape inference of unary element-wise ops as the first candidates.
Resolves #1480
Signed-off-by: Tung D. Le tung@jp.ibm.com

Jenkins Linux ppc64le Build #6313 [push] Only update the output s... started at 10:11

Jenkins Linux amd64 Build #7245 [push] Only update the output s... failed after 26 min

Jenkins Linux s390x Build #7261 [push] Only update the output s... started at 10:10

Jenkins Linux ppc64le Build #6313 [push] Only update the output s... aborted after 48 min

Jenkins Linux s390x Build #7261 [push] Only update the output s... aborted after 2 hr 4 min

authors: jenkins-droid tungld


text:
Feature request: print subcase when an exception is thrown inside one

Description
If an exception is thrown in a SUBCASE, the logged error only contain the TEST_CASE name.
This might be related to #125
Steps to reproduce
Here's a simple program:
#define DOCTEST_CONFIG_IMPLEMENT_WITH_MAIN
#include "doctest/doctest.h"

TEST_CASE("tc")
{
SUBCASE("ab")
{
  std::cout << "ab" << std::endl;
}
SUBCASE("ab, c")
{
  throw std::runtime_error("fail");
}
}

The output is
ab
===============================================================================
test.cpp:4:
TEST CASE:  tc

test.cpp:4: ERROR: test case THREW exception: fail

===============================================================================

There is no information about which SUBCASE failed.
Extra information
SUBCASEs seems to be implemented as ifs, I'm not sure this feature can be implemented in such a way. Maybe SUBCASEs should actually set up a lambda, but that means the user needs to add a ';' at the end of each SUBCASE. Also it wouldn't work with C++ < 11.

doctest version: master cd1d747
Operating System: debian unstable
Compiler+version: clang 5.0.0

This seems reasonable! And indeed it is connected to #125
It can be implemented in C++98 without any troubles. Perhaps I'll look into fixing both issues!

I haven't made progress in this regard with the default console reporter but the just released version 2.3 supports xml as the output and there you will get a much better context of where the exception was thrown from.
Anyway this is still a deficit of the console reporter so this issue will remain open until I fix that.

fixed! releasing version 2.3.5 right now.

Just a message to thank you a lot for having fixed this.
I have around 400 test cases, which are mostly subcases because they are ideal to avoid duplicating function calls, so until now I've had a lot of troubles to track where exceptions came from.
Now it will be a lot easier.

authors: Scorbutics blastrock onqtam

repo: onqtam/doctest


text:
Wrong Contact header when GRUU enabled on registrar

#989 pull request was created to solve this issue.
Describe the bug
SIP.js UA puts GRUU contact value into REGISTER contact header.
To Reproduce (if possible)
Set up regId or instanceId or both parameters in registerer options.
Then if GRUU enabled on a registrar and it response with GRUU contact on second re-REGISTER SIP.js will use it as contact header.
Expected behavior
GRUU  contact can be used everywhere except REGISTER messages.
Environment Information

SIP.js version 0.20.0

According rfc5627

3.3. Using a GRUU
Once a user agent obtains GRUUs from the registrar, it uses them in
several ways. First, it uses them as the contents of the Contact
header field in non-REGISTER requests and responses that it emits
(for example, an INVITE request and 200 OK response). According to
RFC 3261 [1], the Contact header field is supposed to contain a URI
that routes to that user agent. Prior to this specification, there
hasn't been a way to really meet that requirement. The user agent
would use one of its temporary GRUUs for anonymous calls, and use its
public GRUU otherwise.
Second, the UA can use the GRUU in any other place it needs to use a
URI that resolves to itself, such as a webpage.

BTW I do not see recent activity at the project - is it still actively supported? @jscheid @nud @ibc @pedrokiefer @etamme

#989 has been picked onto the main branch.
Thank you.

authors: john-e-riordan zusrut


text:
A Typical Example with HTTP.jl (OpenTelemetrySDKHTTPExt) not working

Hi, trying A_Typical_Example_with_HTTP and can't get it working -  after using OpenTelemetrySDK.OpenTelemetrySDKHTTPExt: otel_http_middleware i got Package OpenTelemetrySDK not found, but a package named OpenTelemetrySDK is available from a registry.   │ Install package?, after 'yes' next line got error: UndefVarError: 'OpenTelemetrySDKHTTPExt' not defined. Looks like OpenTelemetrySDKHTTPExt extension do not loaded, but what i doing wrong? HTTP package already used, his hash same as in weakdeps:HTTP in src/api/Project.toml. In sources looks like OpenTelemetrySDKHTTPExt moved to OpenTelemetryAPI.OpenTelemetryAPIHTTPExt - but it's not working anyway.
Ubuntu 23.04
Julia 1.9.1
OpenTelemetry.jl 0.4.0

That's weird, maybe restart the REPL and try again?

That's weird, maybe restart REPL and try again?

Thanks for reporting, I'm looking into it.

The doc needs to be updated, OpenTelemetrySDKHTTPExt should be OpenTelemetryAPIHTTPExt.
Even though, the otel_http_layer still can't be found with julia@1.9. I guess the implementation was changed somehow in Julia@1.9.0 (I barely remember it works with a pre-release of julia@1.9)

I'll make a patch release later tonight.

authors: NoobsEnslaver ZhaoFancy findmyway


text:
iPad Air 3rd gen 16.0b1 20A5283p has 0% success rate

I have made around 5-10 attempts with each PUAF method and the exploit has always led to an immediate kernel panic without making it to the next stage.

not sure, might be b1 specific, try again on 2.0.5 though

No luck unfortunately. I did find that the exploits were panicking after a longer period than on 2.0.4 if that helps. Perhaps a way to manually set offsets might help for a unique beta build like this?

Any updates on this?

no

Still no success with 2.0.8

Can you send some panic logs?

panic-full-2024-02-28-213402.000.txt

All the panics are very similar if not the same functionally.

You sure it's failing during exploitation? Looks like some sort of broken offset to me

That was my initial theory (being offset related) but since patchfinding was visually succeeded according to the progress tracker, I thought it was exploit related. Would you like me to obtain the correct offsets?

iPad 11,3 16.0 20A5283p.txt
Here are the offsets. Stupid GitHub won't allow me to upload a .h file, so it's a .txt instead.

iPad 11,3 16.0 20A5283p.txt Here are the offsets. Stupid GitHub won't allow me to upload a .h file, so it's a .txt instead.

these aren't the relevant offsets for dopamine though

Oh I thought the KFD offsets were needed. Which offsets are required?

Any update?

Again always happy to help if you let me know what is needed

Try again in 2.1.

No luck unfortunately
On Wed, 1 May 2024 at 3:18 AM, Lars Fröder @.***> wrote:

Try again in 2.1.
—
Reply to this email directly, view it on GitHub
https://github.com/opa334/Dopamine/issues/329#issuecomment-2086081533,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHNAJA4XUWW7MHR2J23AUELY77G67AVCNFSM6AAAAABDM7CPBKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBWGA4DCNJTGM
.
You are receiving this because you authored the thread.Message ID:
@.***>

Please test latest nightly https://github.com/opa334/Dopamine/actions/runs/8988727802
(CC: @Lunariansia)

UPDATE: I tried the latest build, and it caused full panic on my device. It could sucessfuly be booted though. I will try to get the panic logs asap, they are extremely long though. Let's hope that other patchs do not bootload my device 🙏🏻

Panic Log.txt
Got the panic logs. Let's just hope that we can get this bug fixed for all.

well, you're getting the same panic as the OP of this issue now.

Tried the nightly build and still same problem as well. Happy to assist with fixing this as well if you let me know what needs to be done.

lets hope that we can get ios 16 beta working, OP

any updates?

I believe this case is dropped since there are no updates about the matter atm, but there havent been any updates for a while so I believe we may get an 16.0 beta update

does the new branch work on 16.0 beta?

authors: Lunariansia aydenbottos opa334


text:
I fixed WeightBufs.

You should just set IOSURFACE_OBJ_SIZE = 0x1

@opa334

And add check, that if we found IOSurface_location then exit, so it will fast up exploit.

@opa334


text:
Moretwins

add VICReg class subclassing the general parent class Twins for siamese networks.
Other losses could be easily implemented, e.g. SimCLR or the like.
Possible generalization: look into student-teacher networks such as BYOL

N.B: Twins signature has changed: [n, 2, d] -> [n, 2, d'] for consistency with the Module class

repo: opeltre/revert


text:
Handle create=false when exact matching

Overview
When a facility list item is submitted with create=false and there is
no match found, a FacilityListItem is created with facility_id=None.
When another facility list item is submitted which exact matches that
FacilityListItem, an error was being thrown. Instead, we now filter
out FacilityListItems where the facility_id=None, allowing us to match
to the next best option (if one exists) or pass the FacilityListItem
on to the dedupe process.
Connects #1580
Testing Instructions

Not on this branch, browse /api/docs/#!/facilities/facilities_create authorize with an API token
Submit a facility with create=false twice. The second submission should result in ERROR_MATCHING

{
    "country": "Turkey",
    "name": "BAŞARI TEKSTİL",
    "address": "Merkezefendi"
}

Switch to this branch and resubmit the facility. The submission should not throw an error.

Checklist

[x] fixup! commits have been squashed
[x] CI passes after rebase
[x] CHANGELOG.md updated with summary of features or fixes, following Keep a Changelog guidelines

Thanks for reviewing!


text:
How to distinguish which process the output stream line comes from

I have a output stream looking like this, however it doesn't work reliably because some lines simply do not have a prefix.
const outputStream = {
  write: (data) => {
    if (['[SDK]', '[bundle]', '[dts]'].some((str) => data.includes(str))) {
      sdkStream.write(data);
    } else if (data.includes('[Demo App]')) {
      demoStream.write(data);
    }
  },
};

May I know if there's any way I can tell reliably which process a line is coming form? Many thanks!

Not really. What you have is the best way right now.
However, we can change the output stream to have the command object alongside the text.
This would be a breaking change though.
PRs welcome, should be an easy change!

authors: LookRain gustavohenke

repo: open-cli-tools/concurrently


text:
🌱 Update deps of api and library to 0.14.0

Summary
Related issue(s)
Fixes #

/lgtm

repo: open-cluster-management-io/ocm


text:
test nested subscriptions with subscription-admin

Signed-off-by: Roke Jung roke@redhat.com

/lgtm

authors: rokej xiangjingli


text:
update docs

TODO: update the english document

Miss fengzhe

repo: open-compass/opencompass


text:
Force Fetch To Store

https://github.com/open-contracting/kingfisher/issues/58

This starts to put some common code into ocdskingfisher/cli/commands/base.py - in the future files like ocdskingfisher/cli/commands/check_different_schema_version.py will use these to.

repo: open-contracting/kingfisher


text:
[BUG] Data race if the provider set few times

Observed behavior
I have several tests with a similar setup: the provider is created, then configured, the tests are executed, and openfeature.Shutdown() is called for cleanup. However, when these tests are run with the race detector enabled, they consistently fail.
Expected Behavior
No response
Steps to reproduce
package openfeature_test

import (
	"context"
	"sync"
	"testing"

	of "github.com/open-feature/go-sdk/openfeature"
)

func TestDataRace(t *testing.T) {
	of.SetEvaluationContext(of.NewTargetlessEvaluationContext(map[string]any{}))

	err := of.SetProviderAndWait(newRaceProvider())
	if err != nil {
		t.Fatal(err)
	}

	of.Shutdown()

	err = of.SetProviderAndWait(newRaceProvider())
	if err != nil {
		t.Fatal(err)
	}
}

func newRaceProvider() of.FeatureProvider {
	return &raceProvider{
		state: of.NotReadyState,
	}
}

var (
	_ of.FeatureProvider = (*raceProvider)(nil) // ensure implements FeatureProvider
	_ of.StateHandler    = (*raceProvider)(nil) // ensure implements StateHandler
)

type raceProvider struct {
	state of.State
	mu    sync.RWMutex
}

func (p *raceProvider) Metadata() of.Metadata {
	return of.Metadata{
		Name: "racing",
	}
}

func (p *raceProvider) Status() of.State {
	p.mu.RLock()
	defer p.mu.RUnlock()

	return p.state
}

func (p *raceProvider) Init(evalCtx of.EvaluationContext) error {
	p.mu.Lock()
	defer p.mu.Unlock()
	p.state = of.ReadyState
	return nil
}

func (p *raceProvider) Shutdown() {
	p.mu.Lock()
	defer p.mu.Unlock()
	p.state = of.NotReadyState
}

func (p *raceProvider) BooleanEvaluation(ctx context.Context, flag string, defaultValue bool, evalCtx of.FlattenedContext) of.BoolResolutionDetail {
	return of.BoolResolutionDetail{}
}

func (p *raceProvider) StringEvaluation(ctx context.Context, flag string, defaultValue string, evalCtx of.FlattenedContext) of.StringResolutionDetail {
	return of.StringResolutionDetail{}
}

func (p *raceProvider) FloatEvaluation(ctx context.Context, flag string, defaultValue float64, evalCtx of.FlattenedContext) of.FloatResolutionDetail {
	return of.FloatResolutionDetail{}
}

func (p *raceProvider) IntEvaluation(ctx context.Context, flag string, defaultValue int64, evalCtx of.FlattenedContext) of.IntResolutionDetail {
	return of.IntResolutionDetail{}
}

func (p *raceProvider) ObjectEvaluation(ctx context.Context, flag string, defaultValue interface{}, evalCtx of.FlattenedContext) of.InterfaceResolutionDetail {
	return of.InterfaceResolutionDetail{}
}

func (p *raceProvider) Hooks() []of.Hook {
	return []of.Hook{}
}

Create a file with test and run go test -race ./...

@beeme1mr  I am trying to implement the provider and write some e2e tests for it. Using another provider doesn't help much. The issue is related to the providers which implement StateHandler interface.

In the next release, stage management moves to the provider. This is a non-breaking change but may address this problem. FYI @toddbaert

There have been substantial changes to the SDK recently like @beeme1mr said, which are yet unreleased.
The changes are significant enough that there's a chance this bug could be resolved. I would have liked to see the released already but there's a few more issues we have to iron out with it, namely the one you pointed out here: https://github.com/open-feature/go-sdk/pull/296#pullrequestreview-2465098493

Just keep this alive, the release 1.14.0 doesn't fix the issue. go-sdk uses reflect.DeepEqual()  to compare provider(s) internally and that doesn't play very well if provider has sync.Mutex probably.

I think that just running v.Shutdown() should solve the problem.

@blkt i gave it a quick shot and it seems to fix the problem. At least all tests pass, even with the race detector enabled. Cool.

go-sdk uses reflect.DeepEqual()  to compare provider(s) internally and that doesn't play very well if provider has sync.Mutex probably.

@erka yea using reflect.DeepEqual() to compare provider implementations is a problem...
Here are just some ideas:

Require the feature flag implementation to include a UniqueName() or Id() method that can be used to internally identify providers. Also not an ideal solution.
Serialize provider implementations into a format like JSON, which naturally excludes unexported fields and requires omitting problematic field types like sync.Mutex. However, this approach is also far from ideal.
Avoid directly using the FeatureProvider implementation within the SDK. Instead, create a providerReference wrapper during registration, assigning it a self-generated identifier. Subsequently, the rest of the code should work with providerReference values, enabling easy comparison using their IDs. This approach seems like the most promising. The effort strongly depends on how easy it is to change the code to not use FeatureProvider implementations directly.

@warber We could also add a kind field to providerReference and set it to reflect.TypeOf(FeatureProvider).Kind(). If the kind is ptr, we can perform a direct comparison of FeatureProvider. For struct, fallback to reflect.DeepEqual.

@warber We could add a kind field to providerReference and set it to reflect.TypeOf(FeatureProvider).Kind(). If the kind is ptr, we can perform a direct comparison of FeatureProvider. For struct, fallback to reflect.DeepEqual.

I'll give this a shot this week unless I see a PR from somebody else first.

My findings so far:

In addition to just doing v.Shutdown() as @blkt  suggested here, another simple (but inadequate, IMO) solution is to RLock the api mutex during shutdown:

	go func(forShutdown StateHandler) {
		api.mu.RLock()
		defer api.mu.RUnlock()
		forShutdown.Shutdown()
	}(v)

This is probably a bit better than just running shutdown synchronously, but it still means that we won't be able to register providers until the old provider is shut down, which is bad, we want the shutdown not to block anything - it's for side effects such as flushing telemetry, etc. It also hides the real issue, IMO...
The root problem of this entire issue, as far as I can tell, is that we are using DeepEqual, which is a problem specifically because it reads unexported fields (in this case the state of @erka 's provider), bypassing the mutex in their provider and causing the race (this is confirmed by the trace in the DATA RACE warning). I think this is a more general issue and we should not do it, or we risk a lot of this sort of issue.
I think the only real solution is to find a safe way to compare providers without using DeepEqual at all, so that provider's unexported fields are never read (perhaps the way @warber suggested in their last point here)

I think the only real solution is to find a safe way to compare providers without using DeepEqual at all, so that provider's unexported fields are never read (perhaps the way @warber suggested in their last point here)

I'm going to give this a shot.

authors: beeme1mr erka toddbaert warber

repo: open-feature/go-sdk


text:
Add multi-provider blog post

This PR
Adds a blog post introducing the new Multi-Provider in JavaScript and Node.js
Related Issues
This shouldn't be merged before the client-side multi-provider PR is merged, as it references the client-side provider

Thanks @emmawillis ! I'll added some reviewers. I'll review it myself in the next day or so!
Preview is here: https://deploy-preview-593--openfeature.netlify.app/blog/openfeature-multi-provider-release

authors: emmawillis toddbaert


text:
Unable to install deploy-mgmt-hub.sh All in One script

When using the All-in-one script to install the OH Management Hub, I keep getting an error message that says:
Error: http code 404 from: downloading https://github.com/naphelps/openbao-plugin-auth-openhorizon/releases/download/v0.1.0-test/openbao-plugin-auth-openhorizon_0.1.0-test_linux_x86_64.tar.gz, stdout: Not Found
I see there were commits made last week by @naphelps. Wondering if that affected the script.

@naphelps this is still not working. I am wondering if the issue lies in this forking from your branch (naphelps)? I have attached an image highlighting.
Error: http code 404 from: downloading https://github.com/naphelps/openbao-plugin-auth-openhorizon/releases/download/v1.0.0/openbao-plugin-auth-openhorizon_1.0.0_linux_x86_64.tar.gz, stdout: Not Found

repo: open-horizon/devops


text:
Unable to format LUN

So, I'm not sure if this is user error, or which component of this solution is currently causing these issues, but I'm having trouble formatting the exposed objects.
The below paste is a section of journalctl on the initiator which was attempting to format and mount the LUN.
There is also a paste of the targetcli ls at the bottom.
https://paste.ubuntu.com/p/TPpTZmgwJP/
These errors occured using the following packages:
Target:

CentOS 7
Gluster 4.0
TCMU-Runner 1.3
Gluster-Block 0.3
(The packages used were all included in the centos-release-gluster40.x86_64 repo)

Initiator:

Fedora 25

iSCSIadm

Windows Server 2016

I've also tried this same setup using gluster 3.12 and compiling both the gluster-block and tcmu-runner packages from git. I get the same result.
If there is instead a specific set of package versions I should be using, please let me know.
I'm not 100% this is a gluser-block issue, and so I'll also be raising an issue on the tcmu-runner git.
If any additional info is needed, please let me know.

Adding gluster developers @lxbsz @pkalever .
Does this only fail with gluster? Did you use the gluster block tools to set things up?
On the iscsi target logs are there any errors in journalctl or /var/log/tcmu-runner.log? Could you set
log_level = 4
in  /etc/tcmu/tcmu.conf and attach the  /var/log/tcmu-runner.log?

@BlackoutWNCT
Are you using the community version of glusterfs & gluster-block ? If so the tcmu-runner will crash I think, because there has one bug in glusterfs API.
If not, please attach the logs as Mike mentioned.

I've tested the TargetCLI without tcmu-runner or gluster-block and the exposed object was fine, however I've not tested with just tcmu-runner.
I did create the LUN using gluster-block.
I'm currently using the gluster packages contained within the CentOS repos. (I've tested on both 3.12 and 4.0 from centos-release-gluster312.noarch and centos-release-gluster40.x86_64 repos.)
gluster-block I've tried from both the centos-release-gluster40.x86_64 repo, and by cloning the current master git.
I've done the same for the tcmu-runner packages.
Requested logs are here:
https://paste.ubuntu.com/p/tKV3tDQ4rV/

@BlackoutWNCT
Actually  we meant the logs when you are doing the format or read/write. Did you get any errors in /var/log/tcmu-runner.log or journalctl ?
From your logs provided I couldn't see any problem.

Right of course.
Apologies, attached is a new paste dump of various logs for the format.
https://paste.ubuntu.com/p/9vf8kpXd5v/

authors: BlackoutWNCT lxbsz mikechristie

repo: open-iscsi/tcmu-runner


text:
Release 1.4.3 version

Please, release the 1.4.3 version :)
https://plugins.gradle.org/plugin/io.jumpco.open.gradle.s3

Please :)


text:
Data Quality - columnValuesToBeUnique & columnValuesToBeNotNull JSON UI

In https://github.com/open-metadata/OpenMetadata/pull/3255 we added a default property to both test definitions.
This is because we need to be able to differentiate both JSONs from the Python side in order to assign the proper class.
However, creating a test from the UI is not passing the testCase with the default attributes informed:
testCase: {config: {}, columnTestType: "columnValuesToBeNotNull"}

cc @Sachin-chaurasiya @ShaileshParmar11

repo: open-metadata/OpenMetadata


text:
Fix ISSUE-3790: Remove unnecessary public modifiers

Describe your changes :

I worked on fixing the code smells due to unnecessary public modifiers in the tests.
Closes #3790.

Type of change :

[ ] Bug fix
[x] Improvement
[ ] New feature
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation

Frontend Preview (Screenshots) :
For frontend related change, please link screenshots of your changes preview! Optional for backend related changes.

Checklist:

[x] I have read the CONTRIBUTING document.
[ ] I have commented on my code, particularly in hard-to-understand areas.
[ ] I have added tests that prove my fix is effective or that my feature works.
[x] All new and existing tests passed.

Reviewers

Thanks @shivamshrey

authors: harshach shivamshrey


text:
Why can't test after deleting the training set

When I delete the training set, the running test will report an error.
Original Traceback (most recent call last):
File "/home/xidian/anaconda3/envs/pro/lib/python3.6/site-packages/torch/utils/data/_utils/worker.py", line 287, in _worker_loop
data = fetcher.fetch(index)
File "/home/xidian/anaconda3/envs/pro/lib/python3.6/site-packages/torch/utils/data/_utils/fetch.py", line 49, in fetch
data = [self.dataset[idx] for idx in possibly_batched_index]
File "/home/xidian/anaconda3/envs/pro/lib/python3.6/site-packages/torch/utils/data/_utils/fetch.py", line 49, in
data = [self.dataset[idx] for idx in possibly_batched_index]
File "../pcdet/datasets/kitti/kitti_dataset.py", line 380, in getitem
calib = self.get_calib(sample_idx)
File "../pcdet/datasets/kitti/kitti_dataset.py", line 110, in get_calib
assert calib_file.exists()
AssertionError
Can you help me to analyze the reason?

I found that the code used training sets for testing.

Try to change the pkl file path in dataset config.

You actually delete the validation set, not the training set.

authors: Frank-DA Townjj jihanyang

repo: open-mmlab/OpenPCDet


text:
扩出来的图片两边会出现框、墙等

两边很容易出现墙、框、之类的遮挡，请问怎么解决

hi @hjj-lmx
这个确实是有一定概率会出现的。

如果你只想在推理的时候改善，你可以尝试输入一些 prompt，以及调整一下比例（但还是具有随机性）
如果想进一步改进，还是需要训练的时候，可以提高 outpainting 任务的训练比例和 outpainting 训练的 mask 的大小

repo: open-mmlab/PowerPaint


text:
Is it possible to pass allow_unused and materialize_grad to optim_wrapper?

Hi, there!
Im deal with a custom train pipeline which forward model partly from batch to batch. And when i trying to run a distributed train script, an error occurs

Expected to have finished reduction in the prior iteration before starting a new one. This error indicates that your module has parameters that were not used in producing loss. You can enable unused parameter detection by passing the keyword argument find_unused_parameters=True to torch.nn.parallel.DistributedDataParallel, and by
making sure all forward function outputs participate in calculating loss.
If you already have done the above, then the distributed data parallel module wasn't able to locate the output tensors in the return value of your module's forward function. Please include the loss function and the structure of the return value of forward of your module when reporting this issue (e.g. list, dict, iterable).
Parameters which did not receive grad for rank 1:
pipeline.neck_segmentation.spatial_path.conv_7x7.conv.weight ...
.......
......
Parameter indices which did not receive grad for rank 1: 45 46 47 ...

Possible solution doc is to pass allow_unused=True and materialize_grads=True into optim_wrapper.
Is it possible to pass those args by Config or somehow?
Looking forward for reply
Thanks :)

Solved by find_unused_parameters = True

Could you tell me which file should I add find_unused_parameters = True?

repo: open-mmlab/mmdetection


text:
Poor performance due to duplication of annotation ids

I'm trying to train my custom dataset on VFnet, but the loss reduces very slow but I could not find the cause.
Today, I train my data using detection2, the code throws the Assertion Error: annotation ids are not unique
And I check again my data and it's actually duplicated, I did not check more detail, but when I train again VFnet with the correct data format. The loss became stable.
=> I think we should check the annotation ids are unique or not in order to prevent this issue

Can you post a simple labeled example about duplication of annotation ids? We look for the cause of instability. Thank you!

{
    "info": {
        ...
    },
    "licenses": [
        ...
    ],
    "images": [
        {
            "license": 0,
            "id": 0,
            "url": null,
            "file_name": "fold1/images/c337c0c48cb14bcfac1ba739a785c2cb.jpg",
            "height": 1536,
            "width": 1536
        },
        {
            "license": 0,
            "id": 1,
            "url": null,
            "file_name": "fold2/images/c0a788fb3c78173e4a2a447b5fc70a93.jpg",
            "height": 1440,
            "width": 1152
        },
        ...
    ],
    "annotations": [
        {
            "id": 0,
            "image_id": 0,
            "iscrowd": 0,
            "category_id": 0,
            "bbox": [
                859.0,
                425.5,
                145.5,
                148.0
            ],
            "area": 21534
        },
        {
            "id": 1,
            "image_id": 0,
            "iscrowd": 0,
            "category_id": 13,
            "bbox": [
                1111.0,
                822.0,
                220.5,
                96.5
            ],
            "area": 21278
        },
        {
            "id": 2,
            "image_id": 0,
            "iscrowd": 0,
            "category_id": 13,
            "bbox": [
                1083.5,
                839.5,
                251.0,
                141.0
            ],
            "area": 35391
        },
        {
            "id": 0,   // I restart the counter, so it's duplicated here
            "image_id": 0,
            "iscrowd": 0,
            "category_id": 13,
            "bbox": [
                416.5,
                811.5,
                193.0,
                117.5
            ],
            "area": 22677
        },
        ...
    ],
    "type": "instances",
    "categories": [
        ...
    ]
}

It's because I restart the counter of id when creating data from k fold.
folds = [0, 1, 2, 3, 4]
# Put id = 0 here is ok
for fold in folds:
    id = 0 # It will be restart when loop over new fold
    for img_name in {list of images of this fold}:
          # Add a annotation record with id = id
          id += 1

Thank you！We will add this check.