[SECURITY] Releases are built/executed/released in the context of insecure/untrusted code

CWE-829: Inclusion of Functionality from Untrusted Control Sphere
CWE-494: Download of Code Without Integrity Check
The build files indicate that this project is resolving dependencies over HTTP instead of HTTPS. Any of these artifacts could have been MITM to maliciously compromise them and infect the build artifacts that were produced. Additionally, if any of these JARs or other dependencies were compromised, any developers using these could continue to be infected past updating to fix this.
This vulnerability has a CVSS v3.0 Base Score of 8.1/10
https://nvd.nist.gov/vuln-metrics/cvss/v3-calculator?vector=AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
This isn't just theoretical
POC code has existed since 2014 to maliciously compromise a JAR file inflight.
See:

https://max.computer/blog/how-to-take-over-the-computer-of-any-java-or-clojure-or-scala-developer/
https://github.com/mveytsman/dilettante

MITM Attacks Increasingly Common
See:

https://serverfault.com/a/153065
https://security.stackexchange.com/a/12050
Comcast continues to inject its own code into websites you visit (over HTTP)

Source Locations
Nebula-Kotlin-Plugin

https://github.com/nebula-plugins/nebula-kotlin-plugin/blob/cc8c13ddeaf5cceff44693dcba7ca4414424a3d1/build.gradle#L36

Nebula-Closure-Plugin

https://github.com/nebula-plugins/nebula-clojure-plugin/blob/1102498ef0137db42114e2f28471a5bd0a1c0128/build.gradle#L25
https://github.com/nebula-plugins/nebula-clojure-plugin/blob/fdd0ea57bb270414c13419a241e37512dcb68cca/src/main/groovy/nebula/plugin/clojure/NebulaClojurePlugin.groovy#L33
https://github.com/nebula-plugins/nebula-clojure-plugin/blob/fdd0ea57bb270414c13419a241e37512dcb68cca/src/main/groovy/nebula/plugin/clojuresque/ClojureRepositoryConvention.groovy#L26

Nebula-Grails-Plugin

https://github.com/nebula-plugins/nebula-grails-plugin/blob/48871ede4a4886ede3daf2fc47a475d9d0f98148/src/main/groovy/com/netflix/nebula/grails/internal/DefaultGrailsProject.groovy#L122-L129

Nebula-Test

https://github.com/nebula-plugins/nebula-test/blob/aae7d89eb4231dfe6cd3c966ef608e74b452e184/src/test/groovy/nebula/test/SpecifiedGradleVersionIntegrationSpec.groovy#L81

Aside
I originally reported this to the Netflix Bug Bounty program but it was marked as "Not applicable". That report can be found here:
https://bugcrowd.com/submissions/ffe701c31fa7f2a54a9b63b69e48c6b165dedd91df72a8d0d0c088e6d6518687
Public Disclosure
Option 1: File for a CVE
A project maintainer for this project should probably file for a CVE number to inform the public about this vulnerability in the build for this project. The goal is to inform the public that there was a potential for published build artifacts to have been maliciously compromised in earlier releases.
If a maintainer on this project works for or is associated with a CNA, please have them file it with them:
cve.mitre.org/cve/request_id.html
Otherwise, an open source CVE should be filed for here:
iwantacve.org
Option 2: Manually validate the release artifacts
If this project's build is fully reproducible. An alternative to filing for a CVE is to go back and build the earlier releases (with the HTTPS patch applied) to confirm the artifacts were not tampered when they were built. This can be done by comparing the hashes of the artifacts built locally with the ones published. If the hashes of all previous artifacts match those that are published, you can safely assume that the releases were not tampered with.
Again, this assumes that the build if fully reproducible and will require significantly more work.

Thanks for reporting this, we have fixed this and released a new version

Without a resolution by June 1st, I'll move forward with the CVE submission process.


Toolkit is missing a proper uploader

As of currently, the uploader in the toolkit is a placeholder for a proper MongoDB uploader, and data generated by the toolkit is being added to MongoDB manually. We'll want to implement an uploader that seamlessly integrates into the existing toolkit, allowing us to upload scraped/parsed data from the CLI.

@Mohmed0112 How is this going? Is there any way I can assist?

Closed via #26.


YHS: use env vars for event-collector config if no yhs.yml specified

For when we eventually start using container-based YHS instances, the event-collector should search for and use environment variables for its settings, so a static container image can be used, and we inject the settings via pod env settings.
Alternately, for deployments, we could also do some sort of volume-mount of the config YML file on the YHS pod.

Hi, This issue seems interesting to me. Please assign it to me if you think it is something I can work on 😊

@sudiptob2 Excellent! I have assigned it to you. It should be not very difficult to also support using the built-in env vars support that the koanf library we are using for configs - see https://github.com/knadh/koanf?tab=readme-ov-file#reading-environment-variables
Thanks.

Thanks for the hint. Will start working on it.

Hi, @richscott
Wanted to confirm a few cases. koanf supports merging env variables from different sources. Should we also consider the following cases? Or we should only look into env vars if a configuration file is not passed.

Some configuration is defined in .yaml and others are passed as ENV VARs
yaml is passed but variables are also defined as ENV VARS, so ENV VARs should take precedence over .yaml config file.

Thank you so much for the details.


EDGEINV-3: Add support for ECS without DCB

Add support for ECS details: https://folio-org.atlassian.net/browse/EDGEINV-3

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

@izhunke Can you please recreate commits under Folio github account, there is a problem with license, seems you created commits under Ebsco account


Neutral tone doesn't seem to be handled

For example. 爸爸 which is ba4 ba5.
http://en.wikipedia.org/wiki/Standard_Chinese_phonology#Neutral_tone
Is there a way to handle neutral tone with the current software?

Sorry for the late reply. (This issue did not appear in our dashboard.)
No, we do not handle a neutral tone. We were quite short-sighted and did not expect to deal with the neutral tone. We also overlooked the possibility of tone sandhi and the nuances it entails. Google Chrome now appears to have a decent TTS engine that speaks Mandarin Chinese, Cantonese, and few other dialects.
We use it here:

https://github.com/pffy/chrome-chinese-frequency-tts

Here is the extension in Google Chrome Web Store:

https://chrome.google.com/webstore/detail/chinese-frequency-text-to/dbddkjboonoalnoecfcedkmbmfgagbmb


Crash reports

iphone 12 pro, safari, fast internet.
After user finished, it just kept uploading for over 5 minutes:

After closing and reopening browser (probably just minimizing and reopening), this screen appeared:

So it was never uploaded.
I asked the user to upload after just answering a single item (adding birth year) and we received it correctly. But twice it failed when the whole protocol was finished.
@satra , one thought is that this newer model does has heavier audio files which take too long to upload?
@sanuann any ideas?
But I believe this had happened before with an iphone 8 and safari when there was a bug that Sanu later fixed.

i think we should stage the upload and allow a retry if it fails. the code should be able to detect if the upload has not succeeded.

@satra he tried it with his computer using chrome and it also failed! So maybe it's his internet? He says it's fast...
This may be happening to more people but they're not reporting it.

@satra (read above) and he let upload on his computer and it finally uploaded after 15 minutes. Maybe the internet briefly breaks and it starts the uploading from scratch each time? He says his internet is fast and reliable.

i think this is something the client has to show a progress bar or something of the number of bytes transferred. otherwise it's difficult to debug.

so show upload progress
allow retry on fail

And then maybe we instruct them to download it (if they're on a PC/laptop) and send it to us by email or wetransfer?

you can also save it on a phone and contact us and we can send a dropbox link.

I'll look into this and fix it.

Uploading error with a new user (same as above)
Don't know browser and device for now.

Recording error, even though microphone was activated:

Browser properties: {"browser":{"name":"Chrome","version":"88.0.4324.152"},"os":{"name":"Android","version":"10"},"platform":{"type":"mobile"},"engine":{"name":"Blink"}}]

I'm trying to complete this survey but after recording the second response I can't hear it on playback nor can I continue on.

Let me know if I should follow up with them with a question.
Anyway we could have the upload intermittently throughout the study? I'm particularly worried for future studies where they will need to upload more data.


#189: Add JSON Support to where clause

Added JSON Support to where clause
We can now query nested JSON fields
Added unit and integration tests
Performed Benchmarking, Here are the becnhmark results JsonQueryBenchmark.txt

Thanks for adding the tests @YahyaHaq. Could you please rebase your branch on the latest master to resolve the conflicts?

Yes I'm doing that right now. Also uploading the benchmarks
On Sat, 17 Aug 2024, 9:33 pm Jyotinder Singh, @.***>
wrote:

Thanks for adding the tests @YahyaHaq https://github.com/YahyaHaq.
Could you please rebase your branch on the latest master to resolve the
conflicts?
—
Reply to this email directly, view it on GitHub
https://github.com/DiceDB/dice/pull/300#issuecomment-2294907048, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/APNRROZ4SFENS6X2YILBXGLZR53O7AVCNFSM6AAAAABMKV2MICVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJUHEYDOMBUHA
.
You are receiving this because you were mentioned.Message ID:
@.***>

@YahyaHaq Please check the warning mentioned in the lint check and follow the instructions given to fix it. Thanks

@YahyaHaq Please check the warning mentioned in the lint check and follow the instructions given to fix it. Thanks

Will merge this for now and fix the warnings myself as an exception. I am travelling tomorrow so I won't be able to check the PRs.

@JyotinderSingh @arpitbbhayani Thank you so much for merging. This was a great first issue for me and I learned quite a lot about the code base. For the next steps there are some features i think would really improve DiceDB:

Adding support for boolean values both in JSON Querying and SET, GET operations
Currently whenever we want to evaluate a qwatch query we go through all the keys present and check if they match the key regex provided. I am assuming there are going to be cases where the user provides an exact key that they wants to watch. In that scenario it would be overkill to loop over all the keys stored in our keypool. How about we check that if the user has not provided regex in the key string then we do an exact match from our keypool. This might make our qwatch operation faster for this usecase
Fixing the QWATCH bug that i identified that integers are being returned as strings.

Let me know what you think about these points and i will start to create PRs for these as now i have a strong idea on how to go by this

@JyotinderSingh @arpitbbhayani Thank you so much for merging. This was a great first issue for me and I learned quite a lot about the code base. For the next steps there are some features i think would really improve DiceDB:

Adding support for boolean values both in JSON Querying and SET, GET operations

Currently whenever we want to evaluate a qwatch query we go through all the keys present and check if they match the key regex provided. I am assuming there are going to be cases where the user provides an exact key that they wants to watch. In that scenario it would be overkill to loop over all the keys stored in our keypool. How about we check that if the user has not provided regex in the key string then we do an exact match from our keypool. This might make our qwatch operation faster for this usecase

Fixing the QWATCH bug that i identified that integers are being returned as strings.

Let me know what you think about these points and i will start to create PRs for these as now i have a strong idea on how to go by this

Amazing to hear this @YahyaHaq! I agree, the issues you mentioned would be good next steps. Could you create the issues for (1) and (3)? (2) is a good suggestion, let's discuss further on it on our discord.
Thanks!


Support mixed data types in zip_with

Currently, it only makes sense to use zip_with with objects that all have the same data type, since only the data type of the first object is used for dispatching. It might make sense to allow objects of different data types, but I'm not sure how that could be implemented. Questions that have to be answered and possible issues include:

Would it require multiple dispatch at the data type level?
Would it actually be useful? How could one implement a zip_with not knowing the data types of the objects?

Closing as too esoteric. Will reopen if someone wants to zip sequences with different tags.


Changing search-box from code.

Issue: Modifying Selectbox from Code Results in Errors
I’m trying to programmatically change the value of a selectbox in Streamlit, but I'm encountering errors. Here’s the code I used:
def change_searchbox(key, value):
    react_key = st.session_state[key]['key_react']
    st.session_state[key]['options_js'] = [{'label': value, 'value': 0}]
    st.session_state[key]['options_py'] = [value]
    st.session_state[react_key] = {'interaction': 'submit', 'value': 0}

However, I receive the following error:
streamlit.errors.StreamlitAPIException: `st.session_state.key_react_1729608586.803124` cannot be modified after the widget with key `key_react_1729608586.803124` is instantiated.

Is there a workaround for this, or is modifying a selectbox in this manner simply not supported?
Thanks in advance!
Bram

Hey, I believe you'd have to update/replace the whole key, not just partially and then rerun to reload the options. E.g.
import streamlit as st

from streamlit_searchbox import st_searchbox

KEY = "searchbox"

def change_searchbox(key, value):
    data = st.session_state[key]

    data["options_js"] = [{"label": value, "value": 0}]
    data["options_py"] = [value]
    data[data["key_react"]] = {"interaction": "submit", "value": 0}

    st.session_state[key] = data

def some_search(searchterm: str):
    return [f"{searchterm}_{i}" for i in range(10)]

st_searchbox(some_search, key=KEY, default="HI!")

if st.button("Change searchbox", key="button_change"):
    change_searchbox(KEY, "I am the new option!")
    st.rerun()

st.write(f"len() options: {len(st.session_state[KEY]["options_js"])}")

Yes this works! Thanks.
Right now the new option would be visible in the combobox, but is not being preselected.
Would it also be possible to preselect this "new option"? That it not only changes the combobox, but also submits this option?

Alright thanks for the help!


PDF support causes runaway goroutines

We appreciate the new formats and features being added to imgproxy, makes me glad we chose to use imgproxy to power our previewing system. When upgrading to version 2.15.0 (pro), I noticed that support for PDF as a source was added, so I decided to give it a try in our software to see what happens. We generate WebP "seed files" from almost every file using a slower method and give that to imgproxy as a source, but during the window of time between when a file is first added and before the seed is generated, we optionally will give imgproxy the original file as a source for "snappier" previews if we can.
When adding the option to feed PDFs directly into imgproxy, we noticed that connections to imgproxy began timing out 15-ish minutes after deployment, so we rolled back. Digging into our collected metrics, I noticed that imgproxy pods that were given PDFs as input files began creating goroutines at an alarming rate without decreasing:

(Slopes end when the pods were killed and replaced with new pods.)
Memory usage remained relatively normal during this time, but latency for establishing a new connection went up, and our proxy layer began timing out after 15 seconds trying to establish a connection to imgproxy.
I'm not sure what exactly went wrong here, but I supect one of these two possibilities:

There is a goroutine leak somewhere in the PDF implementation.
PDFs are simply expected to be slow, and at our volume of traffic (>10K requests/minute) imgproxy simply gets piled up with too many concurrent requests.

Though I am suspecting the first possibility (hence this issue) because we have imgproxy configured with IMGPROXY_CONCURRENCY=50 per instance, and >400 goroutines seems really high when this configuration is set.
Thoughts?

Hi!
I have just tried to spam imgproxy v2.15.0 with 200 concurrent requests of PDF processing while the concurrency was set to 50. I have got 400+ goroutines, but their number didn't grow. Since imgproxy doesn't do anything special with PDFs, ones shouldn't cause goroutines leak. Anyway, I'd appreciate some samples of your PDFs and imgproxy URLs.
You should know that IMGPROXY_CONCURRENCY != maximum of concurrent requests. IMGPROXY_CONCURRENCY is the number of images that can be processed simultaneously. If the number of concurrent requests if greater than concurrency, some requests will be put into a queue. The maximum number of concurrent requests can be configured with IMGPROXY_MAX_CLIENTS , and it's IMGPROXY_CONCURRENCY * 10 by default (500 in your case). Every request is processed in its own goroutine. Goroutines are also cast while working with channels. So if you have 200+ concurrent requests, you'll get 400+ goroutines with ease.
Also, PDFium is not thread-safe, and libvips wraps all PDF loading operations with mutexes. Thus if some of your PDFs are heavy to load, this may cause a jam in this place.
I always recommend scaling imgproxy horizontally rather than vertically. It's better to have 10 pods with a concurrency of 5 than a single pod with a concurrency of 50. Try to split your pods into smaller ones and see if it helps.

Thanks for your detailed response! Those numbers do make sense, though I'm still not entirely sure why connections to imgproxy were timing out if they ought to have been accepted (up to 500) and put in a queue for image processing. That part I'm still a bit puzzled by.

Also, PDFium is not thread-safe, and libvips wraps all PDF loading operations with mutexes.

Ah good to know, that was probably the real source of the bottleneck then; a couple dozens of large PDFs could easily put an imgproxy instance out of commision if we reach the concurrency limit with all PDF requests, since new requests will be queued, but the PDF requests will be processed more-or-less one at a time anyway.

I always recommend scaling imgproxy horizontally rather than vertically.

I guess we've done both, with IMGPROXY_CONCURRENCY=50 and 16 pods. I'll look into adjusting this to be more horizontal and see if that helps us. (it should since it increases the total number of parallel PDF operations.)

OK, so it turns out I'm not losing my sanity, and there indeed seems to be some sort of problem here. I'm not sure what, it isn't runaway goroutines, but it does indeed put imgproxy out of commission. Here's a new metrics graph:

I also grabbed the logs from this pod in order to correlate activity with the graph above. What I found is that, at 14:34:12, this particular imgproxy instance was given a PDF as a source file for making a thumbnail. Log message:
Started /insecure/w:250/h:250/rt:fit/bg:255:255:255/bga:0.0/[REDACTED].webp

As soon as this log message was emitted, not a single image request completed after this point. This can be observed by looking for log messages such as Completed in 170.317633ms /insecure/blah. There are tons before this point, and zero after this point. So it seems like sending this request immediately puts the pod out of commission.
After this point there are still plenty of Started /insecure/blah messages. But actually, there are exactly 99 of them between 14:34:18 and 15:12:27. Over this time period in the metric graph is when you see the number of goroutines steadily rise. This 99 likely corresponds to the value of IMGPROXY_MAX_CLIENTS. (I had increased the pod count and reduced IMGPROXY_CONCURRENCY to 10, so the effective value for IMGPROXY_MAX_CLIENTS should be 100.)
Finally, at 15:12:49, requests to the /health endpoint (which previously were succeeding during this time period) stopped responding, and so the kubelet restarted the pod, which is reflected on the graph as the goroutine count resetting back to normal.
Curious and surprised, I decided to attempt to reproduce this locally. No high traffic, no Kubernetes, just the Docker image (still the v2.15.0 tag BTW) and some manual requests to it. And to my surprise (or relief for being reproducible 😉), I was able to get the exact same behavior with a fresh Docker container. Simply send a request with a PDF as the source in it, and then while waiting try to send another request with literally anything as the source (in this case I used a plain old JPEG). As I am writing this, I am still waiting, and neither the initial PDF request nor the following JPEG request have returned after 10 minutes. Also, aborting the request doesn't do anything, though I wouldn't really expect it to either.
Now unfortunately, I cannot share the PDF file that caused this with since it is data confidential to our customers, but I did want to make sure that it wasn't something wrong with the PDF itself. It seems that is perhaps the case, since I couldn't reproduce it with this dummy PDF.
At the moment, I am trying to find another PDF that it is OK to share that also gives this behavior so that you can reproduce, but I guess my other question is: is there a way to timebox or timeout these requests? I wouldn't mind if a problematic PDF or two showed up a couple times an hour as long as imgproxy was able to abort the operation after 5 seconds or so.
My other question is, why does such a PDF put imgproxy immediately out of commission? I get that there's a mutex around PDF operations, but then why are subsequent non-PDF requests hanging when my concurrency level is 10? I'd expect imgproxy to continue processing up to 9 non-PDF operations at a time while the 1 PDF request is running.

Ok, we finally found that is was a "bad" PDF that causes the issue. It turns out that libvips wraps PDF-loading operations with a global lock https://github.com/libvips/libvips/blob/master/libvips/foreign/pdfiumload.c#L220. This, of course, leads to the locking of an unpredictable number of operations. Seems like it should use a separate mutex for PDFs. I'll try to prepare a PR that fixes the problem and patch the libvips build inside a Pro image. I'd appreciate it if you could provide a sample of that "bad" PDF so I could test a fix. I can guarantee it won't go anywhere from my laptop's hard drive which is encrypted.

At the moment, I am trying to find another PDF that it is OK to share that also gives this behavior so that you can reproduce, but I guess my other question is: is there a way to timebox or timeout these requests? I wouldn't mind if a problematic PDF or two showed up a couple times an hour as long as imgproxy was able to abort the operation after 5 seconds or so.

Unfortunately, we can't stop libvips operations in the middle. imgproxy surely checks the timings between the operations, but if an operation takes a long time, imgproxy has to wait until it's done.
We can set a hard timeout right in the server settings, but this will lead to "zombie requests": the request is timeouted but still waits for a long-running operation to stop. This will lead to the usage of additional resources and slowing down the entire imgproxy instance. IMHO this doesn't look anyhow better than the current case.

I haven't been able to find a PDF yet that I can share that exhibits this problem, but I can keep looking. Though whatever aspect of these PDFs that cause the problem must not be too uncommon, since when we enable PDF support in production, multiple PDFs from multiple customers of ours seem to cause this. It's definitely not a "heaviness" factor; imgproxy/vips seems to accept a large, image-heavy 200MB PDF just fine and returns in a second or two. When this issue happens, it hangs for at least 15 minutes or more, consuming very little CPU, so I am assuming that some particular element in the PDF triggers a codepath with a deadlock of some sort in PDFium.

By heaviness, I don't mean the file size but something inside the PDF doc that is hard for PDFium to render.

@jcupitt I have considered poppler in the first place, but as you mentioned it's licensed under GPL. We can't afford any GPL libs to be used by imgproxy since we have a commercial version of it. More of it, poppler licensing is a kind of complex thing: it is based on Xpdf which is also GPL. Xpdf has a kind of commercial license, but poppler doesn't since it's based on GPL software. So it seems like there is literally no way to use poppler in non-GPL software :(

OK, apologies for the delay, but I have finally acquired a PDF document that reproduces this problem that I can post here. I've removed all images, vector elements, text, and metadata from this PDF, and yet it still causes some sort of deadlock that causes imgproxy/vips/PDFium to never return; it just hangs forever no matter how long you wait. I've also uncompressed the PDF stream itself to be easier to inspect:
deadlock-pdf-blank-stripped-uncompressed.pdf.zip
Note that all the PDF tools at my disposal see no issue with this PDF and simply display it (yes it is a blank page) correctly, including Acrobat, PDF.js, macOS Preview, Chrome, and Ghostscript. Now I'm not too knowledgeable about the PDF format or PostScript, but I have been spending a considerable amount of time fiddling around with it. My suspicion is it has to do with what appears to be an embedded color profile, since if I remove it and replace references to it with a reference to device CMYK, imgproxy seems to no longer hang and instead returns a thumbnail instantly.
Also, is it not the case that Google Chrome uses PDFium internally for its builtin PDF viewer? I find it interesting that Google Chrome had no problem whatsoever rendering this PDF. Perhaps libvips is using an outdated version that has a fix for this already?
Is there a more appropriate place to report this bug?

Hi @sagebind,
That's interesting, I tried at the command-line using PDFium 4290 and git master libvips:
john@yingna ~/pics $ /usr/bin/time -f %M:%e vipsthumbnail deadlock-pdf-blank-stripped-uncompressed.pdf
35816:0.06
john@yingna ~/pics $ vipsheader tn_deadlock-pdf-blank-stripped-uncompressed.jpg
tn_deadlock-pdf-blank-stripped-uncompressed.jpg: 128x83 uchar, 3 bands, srgb, jpegload

ie. it makes the thumbnail in 60ms and needs 35mb of memory.
Do you know the libvips and PDFium versions you see the deadlock with?

If pkg-config is to be believed, I am using libvips 8.10.1, I'm not sure about PDFium. I am using one of the latest prebuilt imgproxy-pro Docker images, @DarthSim would probably know the PDFium version included.

Could you try vipsthumbnail at the command-line? If that locks up, we've got a nice, simple test case.

Yes, I am able to reproduce with the vipsthumbnail command, though only with the libpdfium.so packaged in the imgproxy Docker image. So far, I am trying various versions of PDFium from https://github.com/bblanchon/pdfium-binaries/releases and am not able to reproduce. So I am wondering if there is something wrong in particular with the libpdfium.so I have been given.

Wow, that's strange. It's great you've found a fix anyway.

Thank you for digging this out! I found what causes this issue. I build PDFium to reuse as much system-wide installed libraries as possible instead of statically linking ones that are distributed with PDFium. It occurred that lcms2 that comes with PDFium is very patched. It seems like one of those patches fixes this issue. I'll try to release the fixed image ASAP.

I'm really sorry for the huge delay. Looks like I make it work in the latest build.

@DarthSim Indeed, it looks like this problem is totally fixed in the very latest image. Thanks!


Implement Sangita in Bengali

Task List for getting Started

[ ] Implement Tokeniser for Bengali

[ ] Find Datasets for the Language to move forward with.

Pretty good page of a person already working on the same thing: [https://www.isical.ac.in/~utpal/resources.php](ISI - UTPAL).
Not exactly what we want but kaggle has this bengaliAI group solving Bengali datasets for recognizing handwritten numeric digits in Bengali. [https://www.kaggle.com/BengaliAI/numta](Kaggle - BengaliAI)

@lavishsaluja good one
Lets connect at night.

Some other resources:

http://docs.cltk.org/en/latest/bengali.html
https://github.com/banglakit/awesome-bangla(It contains links to multiple datasets)
Handwritten Text in Bengali: https://data.mendeley.com/datasets/hf6sf8zrkc/2( May not exactly fit into the given specifications)
https://github.com/AtikRahman/Bangla_ABSA_Datasets Contains 2 excel files whose data has been used for sentiment analysis in some other project(License not added on Github)


Movie Show Times

Add nearby and upcoming movie show times.

Making a note to discuss this at the feature meeting on 9/23

Looking into using Fandango API
This looked promising, but it was powered by Google Movies which was discontinued about a month go. The maintainer is trying to move over to Fandango so maybe we could just wait.

Alternatively we could work with UCSD Box Office for some sort of integration

I'd like to review this again to see if it's worth building and/or something people want.
If it is, let's turn it into a real task and flesh out the details.

If it's only for movie times I don't think it'd be worth the effort. If it was something that integrated with the UCSD Box Office, I could see it being valuable.

Adding this as a feature could be a good subject for a mobile poll question.

We will revisit this under our internal feature request board.


[RCTImageLoader][0.33 & 0.34] Crash

Issue Description
When scrolling a listview with items that have image views the app will eventually crash in
RCTImageLoader.m#L383 (Crashlytics Crashreport)
or in
RCTImageLoader.m#L502 (Crashlytics Crashreport)
Steps to Reproduce / Code Snippets
In our app just scroll a longer list that has remote images, eventually it will crash.
Expected Results
The app should not crash.
Additional Information

React Native version: 0.33.0
Platform: iOS
Operating System: macOS

This seems to have been introduced in this commit going into RN 0.33: https://github.com/facebook/react-native/commit/14188289fc6254b6704460f7c58e4334f8aa1e25 at least it touches exactly the line that is crashing

I'm getting lots of crashes also, all related I think:
http://crashes.to/s/96034f860eb
http://crashes.to/s/e5f0b80d061
http://crashes.to/s/40184834c7e

Hey guys, we have a similar crash, affecting consistently a number of our users - I think related to the problems people have mentioned so far.
http://crashes.to/s/518580ef4b9 (line 383)
http://crashes.to/s/8ebd91bfbf8 (line 385)
Both crashes on React Native 0.33.

same crash issue
need your help, @javache

We were able to prevent this crash by prefetching images

We have seen these crashes disappear in v34.

@javache Great! I'll test it out and report back.

Same on 34 RC  :(
http://crashes.to/s/7c31b33b411

Seeing this as well - also present in 0.32.

@javache I can confirm the same severity in 0.34 as was in 0.33. In our app you just have to scroll 2 - 3 pages worth and it crashes. Very reproducible.

This has prevented us from upgrading from 0.32. :(

Same issue here, definitely excited to get this fixed and make the upgrade!

@chiplay for me Strong reference don't solve this problem :/
http://crashes.to/s/c55a4e38ab1

Closing this issue since https://github.com/facebook/react-native/issues/9849 is tracking the same bug -- subscribe to that one.


Dead/HTTP Error 404 Not Found links at DKRZ

I am using the links scanner from https://github.com/valeriupredoi/check_links_in_site and found two dead links:
WARNING: https://www.dkrz.de/daten-en/wdcc?set_language=en gives HTTP Error 404: Not Found
WARNING: https://www.dkrz.de/daten-en/data-services/Datapublication gives HTTP Error 404: Not Found

Kerstin says: These broken links you found must be really old - we changed the website
structure underlying these links around 2015 and I guess the content of
the page also changed several times since then, thus I do not know,
which content was once linked, and where it is now...
You could try to contact the author of the pages, where these links are
referenced to find out what the content of these links were and then I
could try to help to find a proper link on our pages.... or you simply
mark the links as "outdated" ;-)
@SophieMacadamia @fannyadloff please advise what to do with these links :beer:

I will contact someone at DKRZ and ask.

awesome, cheers much, Fanny! I mean, we could just forget about them, here are the latest test results https://github.com/IS-ENES3/Tests/runs/7244006560?check_suite_focus=true - note that the MPIMET one actually works, it just returns a 404 (maybe we should tell them?)

Hi V,
The 2 links from DKRZ (previous message) should be replaced by:
(1) https://wdc-climate.de/
(2) https://docs.dkrz.de/doc/dataservices/publishing_dissemination/index.html

For the MPI one, it works for me without a 404!

and now we don't have any more broken links https://github.com/IS-ENES3/Tests/actions/runs/2636040080 - yay, cheers guys! :partying_face:


Add -s/--skip flag to skip packages that already exist.

Note that this also contains a minor refactor of the code to move all database access into a dedicated module.

Example output:
When -s or -f are not set,
haddocset: Failed to write documentation for Boolean-0.2.3. Documentation for it already exists. Use -f/--force to overwrite it or -s/--skip to skip it.

When -f is set,
QuickCheck-2.8.1: Found existing documentation. Deleting.
QuickCheck-2.8.1 ........*****
ReadArgs-1.2.2: Found existing documentation. Deleting.
ReadArgs-1.2.2 .

When -s is set,
pcre-light-<IP_ADDRESS>: Found existing documentation. Skipping.
pem-0.2.2 ..
persistent-2.2 .......***
persistent-sqlite-2.2 .....
persistent-template-<IP_ADDRESS> .
pipes-4.1.6: Found existing documentation. Skipping.

merged:smile: but I failed notify it to github system, sorry...


report NoWhitespaceAfter bug

Hi @XenoAmess. Happy to have a test that reproduces an issue. Can you add a @Issue("https://github.com/openerwirite/issues/...") and @Disabled annotation? Thank you!


Fix BaseLevel3.gemm order arg (get from GemmParams in case of duping)

DO NOT MERGE
Attempts to fix: https://github.com/deeplearning4j/deeplearning4j/issues/4776#issuecomment-371745349
Order arg should be obtained from GemmParams.
Note however this is not sufficient to fix the afore-mentioned issue.

Is this still viable?

I completely forgot about this. The alpha/beta stuff there (instead of 0s and 1s) should probably be implemented/fixed. Maybe I'll close this and do a separate PR for that.


sphere loss

when using spere loss, meet with the following error
Traceback (most recent call last):
File "/home/ligh/hby/huawei_DIGIX/DIGIX-ImageRetrieval-master/train_arcLoss.py", line 183, in
scheduler=scheduler,
File "/home/ligh/hby/huawei_DIGIX/DIGIX-ImageRetrieval-master/train_arcLoss.py", line 54, in train_model
out= model(inputs,labels)
File "/home/ligh/anaconda3/envs/yolov5/lib/python3.7/site-packages/torch/nn/modules/module.py", line 532, in call
result = self.forward(*input, **kwargs)
File "/home/ligh/anaconda3/envs/yolov5/lib/python3.7/site-packages/torch/nn/parallel/data_parallel.py", line 152, in forward
outputs = self.parallel_apply(replicas, inputs, kwargs)
File "/home/ligh/anaconda3/envs/yolov5/lib/python3.7/site-packages/torch/nn/parallel/data_parallel.py", line 162, in parallel_apply
return parallel_apply(replicas, inputs, kwargs, self.device_ids[:len(replicas)])
File "/home/ligh/anaconda3/envs/yolov5/lib/python3.7/site-packages/torch/nn/parallel/parallel_apply.py", line 85, in parallel_apply
output.reraise()
File "/home/ligh/anaconda3/envs/yolov5/lib/python3.7/site-packages/torch/_utils.py", line 394, in reraise
raise self.exc_type(msg)
TypeError: Caught TypeError in replica 0 on device 0.
Original Traceback (most recent call last):
File "/home/ligh/anaconda3/envs/yolov5/lib/python3.7/site-packages/torch/nn/parallel/parallel_apply.py", line 60, in _worker
output = module(*input, **kwargs)
File "/home/ligh/anaconda3/envs/yolov5/lib/python3.7/site-packages/torch/nn/modules/module.py", line 532, in call
result = self.forward(*input, **kwargs)
File "/data_2t/home/ligh/hby/huawei_DIGIX/DIGIX-ImageRetrieval-master/modeling/models.py", line 103, in forward
logits = self.final(feature)
File "/home/ligh/anaconda3/envs/yolov5/lib/python3.7/site-packages/torch/nn/modules/module.py", line 532, in call
result = self.forward(*input, **kwargs)
TypeError: forward() missing 1 required positional argument: 'label'

The number of pictures needs to be divisible by batch size. So you can change the batchsize,


Recipe Reviews

Name: Leave recipe reviews
Actor(s): User
Description: leave star rating and comment on recipes
Preconditions: selected recipe to review
Basic Flow: The user clicks the star corresponding to the rating, and then is able to leave a comment below the recipe
Alternate Flows: If the user has already left a review before, ask if they want to review it again.
Postconditions: The user has now left a review that is publicly viewable and linked to their account.
User Story 7: As a user, I want to leave reviews for recipes so that I can share my experience and help other users decide if they want to try the recipe.
Feature 7: Leave Reviews for Recipes
•	Scenario 1: User successfully leaves a review for a recipe
o	Given the user is logged in and viewing a recipe
o	When the user clicks the “Leave Review” button and submits a review
o	Then the system adds the review to the recipe’s review section
•	Scenario 2: User edits their review
o	Given the user has already left a review for a recipe
o	When the user clicks the “Edit Review” button and submits changes
o	Then the system updates the user’s review with the new content
•	Scenario 3: User deletes their review
o	Given the user has already left a review for a recipe
o	When the user clicks the “Delete Review” button
o	Then the system removes the user’s review from the recipe’s review section

I have rating working and it is pushed to branch 'ReviewsAndRatings'.


[Excel] (Custom Functions) Adjust parameter address note

The yo office issue that inspired this !IMPORTANT note has been resolved, and the manually-created JSON process is no longer required to detect parameter addresses.

Docs Build status updates of commit a0709d7:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/excel/custom-functions-parameter-options.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


keyword extraction using sommy

there are lot of redundant codes as comment

Could you please use the test set and generate tags for those as well?

Hey @yadavabhishekkumar I was just going through the notebook. Its slightly hard to understand whats happening is it possible to clean it a bit ? Once you are done with that I can merge it
Thanks!!! :+1:


FAM support Spar: return user email information in Cognito

Describe the task
Team Spar wants to get the email information of the login user, we need to include that in the return data from Cognito. Update the read and write attributes in the infrastructure/server/oidc_clients_spar.tf file to include email. We have to add to write attribute because Cognito needs the write permission to capture the user information.
Acceptance Criteria

[ ] Return email of the login user for Spar
[x] Notify team Spar that they need to take care of the user information and include in their PIA

Email sent:


Umple json generation fails in certain cases when traits present

The following code fails when attempting to generate json from it as occurs, for example, when drawing editable diagrams in UmpleOnline.
class Color {}

trait TDrawable {
  0..1 -> * Color color;
}

class Z {
  isA TDrawable;
}

This results in the compiler crashing
at JsonGenerator.extractClassName
Note that a much large example of this is the Geometric Objects example in UmpleOnline. That will generate graphviz. Somebody has special-cased the example to avoid it trying to generate Json.
People using this example regularly crash UmpleOnline, so this problem needs fixing quickly.

Was reading through the description of a Trait and noticed that the last line in the first paragraph on this page is repeated: http://cruise.eecs.uottawa.ca/umple/Traits.html
I'm not sure where to report typos like that so I'll post it here for now.

I'm not sure where to report typos like that so I'll post it here for now.

Thank you, Josh. I fixed them and push a new branch. I'll merge it soon.

After discussing with Vahdat, there are few things to note about this issue:

The association defined in TDrawable still exists in the model's list of associations when generating the json - this is why the null pointed exception is thrown in extractClassName(). I believe that the only association that should exist is 0..1 Z -- * Color color. This association does exist, but it is missing its coordinates since it is applied to the class after postTokenLayoutAnalysis(). When the Json generator executes, it gives it a coordinate of (-1, -1), (-1, -1).
Vahdat noted that the associations should be maintained at the model level for futrueproofing the project (in case it needs to be used later). So I've created a solution which just skips generating Json for any association that involves traits, which should be sufficient for solving this issue.

The coordinates of the associations are never set because the trait's associations are applied to a class in the function applyTraits() which is called after the postTokenLayoutAnalysis() function is executed (which generates all the coordinates for classes, associations, etc.)
I am going to have to rearrange the code somehow, which I will investigate further.

@AlexJoshuaMcManus  I brought back associations added to the model.
Please check the branch named association_traits and see if this is what you were looking for or not.
Once you confirm, I'll merge it.
Thanks

@vahdat-ab I looked over the changes and it appears to recover the associations at the model level, which is what I was hoping for. If you feel that adding this back will not compromise the architecture of the system, then please merge it. Thanks.

@AlexJoshuaMcManus  it's done.

Pull request was merged in


http_server stream on_read should not be called again after connection error

https://github.com/litespeedtech/lsquic/blob/ff412f2f22c7486c86e97e9bf30a36de5f4504c1/src/liblsquic/lsquic_stream.c#L2170
After stream->stream_if->on_read, connection may happen some unexpected ERROR, like INVALID settings frame, but ( (stream->sm_qflags & SMQF_WANT_READ && lsquic_stream_readable(stream)) == TRUE, then on_read will be called again, which will lead to read_payload-->assert(READER_SKIP == fr->fr_state.reader_type).

What is the value for fr->fr_state.reader_type when it happens?
the on_read() callback may needed as it is the way to tell application there is an error with the stream.  need to avoid the assert() in this situation.

What is the value for fr->fr_state.reader_type when it happens?
the on_read() callback may needed as it is the way to tell application there is an error with the stream. need to avoid the assert() in this situation.

As I have found, fr->fr_state.reader_type is a random, like 725118769,<PHONE_NUMBER>,<PHONE_NUMBER>, etc.

Probably need to check why it is not initialized.

Probably need to check why it is not initialized.

fr was malloced without set to zero, all elements in fr->fr_state are random value.

Does the patch fix the assert failure?

Does the patch fix the assert failure?

I have create invalid SETTINGS frame request to test this patch,  it can fix the assert failure when invalid SETTINGS frame in.
There may have other scenes, but I cannot confirm them as so far.

thanks. merged.


Godot 3.2.4 beta 4 not supported by your gpu drivers message (it runs anyway)

Godot version: 3.2.4 beta 4 standard
OS/device including version: Linux Pop Os 20.10 and windows 10
Notebook lenovo x240 (linux) and AMD ryzen 3400g with integrated vega 11 (win)
Issue description:
When creating a new project in the project manager, under the OpenGL ES 3.0 option, appear the "not supported by your gpu drivers" message.
Anyway, it let me create the project and run it with GLES 3 renderer.
Steps to reproduce: Open Godot 3.2.4 beta 4 and create a new project. The message appear under OpenGL 3.0
The project seems to run well, it's only the message.
It doesn´t happen in 3.2.4 beta 3 and previous versions.
thanks

This is fixed with #44302.


Azure Functions: Explain impact of restart on running functions

I would like to add @alexkarcher-msft note to the documentation - https://github.com/MicrosoftDocs/azure-docs/issues/30494#issuecomment-549595061. I believe that's quite important information. But I guess it's not the best place (and not the best wording) so I would be glad if somebody could help me with this.

@ebashmakov : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Thanks @ebashmakov for helping to fix this. I am working on a similar fix to the same issue in the private repo. I'm going to cherry-pick your commit in with my PR so you can still get credit for helping out with the article.

Thanks @ebashmakov for helping to fix this. I am working on a similar fix to the same issue in the private repo. I'm going to cherry-pick your commit in with my PR so you can still get credit for helping out with the article.

@ggailey777 sounds good! thank you!

Your commit is now in the main branch in our private repo, so I'm going to close this PR.
Thanks again for your help. #please-close


Purchasing Auto-Renewing Subscriptions Fails (Unknown Error)

Version of flutter_inapp_purchase
0.8.5
Platforms you faced the error (IOS or Android or both?)
iOS
Expected behavior
Purchase of auto-renewing subscription would work.
Actual behavior
Fetching of the products works as expected, however, when I call buyProduct on the item (an auto-renewing subscription), the transaction fails and the error message is: "An unknown or unexpected error has occurred. Please try again later." Tried to debug in XCode and can only see that the transaction state goes from purchasing to failed. I've checked that in app purchases are enabled in capabilities in the XCode project, all the products are set up appropriately in AppStoreConnect, and canMakePurchases returns true every time. Curious if anyone has run into this issue and what was done to mitigate. Thanks!
Tested environment (Emulator? Real Device?)
Real device

Since this plugin is delivered by react-native-iap which has more matured issue list, you may check this one. There are many unknown side-effects in IAP especially in ios that we covered and that we need to cover in the future.
Also, please give a PR when you've solved your problem to share with others.

Have you logged out of the device and only use a Sandbox account when the purchase dialog appears in app?
I've seen this error when testing a purchase but have forgotten to log out of the device's account. Don't forget to not login to the device with the Sandbox account either or it will create a "real" user

I'm also getting this error using an iOS simulator, if i find a fix i'll post an update.

Is this issue still open?

Have you logged out of the device and only use a Sandbox account when the purchase dialog appears in app?
I've seen this error when testing a purchase but have forgotten to log out of the device's account. Don't forget to not login to the device with the Sandbox account either or it will create a "real" user
Update: You get this error when trying to access IAP on iOS when using a proxy (like Charles) as well

I do not understand what you mean by the various log in log out tips. I'm running into this as well. With a real account and with a sandbox account. I would consider this open...

I'm running into this issue as well with a non-renewing subscription. The error log is below. I've confirmed that I can get this IAP to work with a Sandbox User in a previous version of the app that was built using only Swift.
Purchase Started !!
2019-05-08 11:44:47.819382-0500 Runner[16255:3743382]
Purchase Failed  !!
2019-05-08 11:44:47.824961-0500 Runner[16255:3743449] flutter: Caused err. Set additionalSuccessPurchaseListenerIOS.
2019-05-08 11:44:47.825483-0500 Runner[16255:3743449] flutter: PlatformException(E_UNKNOWN, An unknown or unexpected error has occured. Please try again later., null)
2019-05-08 11:44:47.829865-0500 Runner[16255:3743449] [VERBOSE-2:ui_dart_state.cc(148)] Unhandled Exception: PlatformException(ios, platform not supported, null)
#0      FlutterInappPurchase.buyProduct (package:flutter_inapp_purchase/flutter_inapp_purchase.dart:269:5)

#1      _PurchaseSubscriptionPageState.buyProduct (package:undaunted_golf_flutter/PurchaseSubscriptionPage.dart:98:58)

#2      _PurchaseSubscriptionPageState.build. (package:undaunted_golf_flutter/PurchaseSubscriptionPage.dart:344:25)

#3      _InkResponseState._handleTap (package:flutter/src/material/ink_well.dart:511:14)
#4      _InkResponseState.build. (package:flutter/src/material/ink_well.dart:566:30)
#5      GestureRecognizer.invokeCallback (package:flutter/src/gestures/recognizer.dart:166:24)
#6      TapGestureRecognizer._checkUp (package:flutter/src/gestures/tap.dart:240:9)
#7      TapGestureRecognizer.acceptGesture (package:flutter/src/gestures/tap.dart:211:7)
#8      GestureArenaManager.sweep (package:flutter/src/gestures/arena.dart:156:27)
#9      _WidgetsFlutterBinding&BindingBase&GestureBinding.handleEvent (package:flutter/src/gestures/binding.dart:225:20)
#10     _WidgetsFlutterBinding&BindingBase&GestureBinding.dispatchEvent (package:flutter/src/gestures/binding.dart:199:22)
#11     _WidgetsFlutterBinding&BindingBase&GestureBinding._handlePointerEvent (package:flutter/src/gestures/binding.dart:156:7)
#12     _WidgetsFlutterBinding&BindingBase&GestureBinding._flushPointerEventQueue (package:flutter/src/gestures/binding.dart:102:7)
#13     _WidgetsFlutterBinding&BindingBase&GestureBinding._handlePointerDataPacket (package:flutter/src/gestures/binding.dart:86:7)
#14     _rootRunUnary (dart:async/zone.dart:1136:13)
#15     _CustomZone.runUnary (dart:async/zone.dart:1029:19)
#16     _CustomZone.runUnaryGuarded (dart:async/zone.dart:931:7)
#17     _invoke1 (dart:ui/hooks.dart:233:10)
#18     _dispatchPointerDataPacket (dart:ui/hooks.dart:154:5)
2019-05-08 11:45:22.597897-0500 Runner[16255:3743779] [BoringSSL] nw_protocol_boringssl_get_output_frames(1301) [C4.1:2][0x10ab13540] get output frames failed, state 8196
2019-05-08 11:45:22.598180-0500 Runner[16255:3743779] [BoringSSL] nw_protocol_boringssl_get_output_frames(1301) [C4.1:2][0x10ab13540] get output frames failed, state 8196
2019-05-08 11:45:22.598613-0500 Runner[16255:3743779] TIC Read Status [4:0x0]: 1:57
2019-05-08 11:45:22.598659-0500 Runner[16255:3743779] TIC Read Status [4:0x0]: 1:57

same for us, identical behavior only for renewable products
Version of flutter_inapp_purchase
0.9.2
Platforms you faced the error (IOS or Android or both?)
iOS
Expected behavior
Purchase of auto-renewing subscription would work.
Actual behavior
Fetching of the products works as expected, however, when I call buyProduct on the item (an auto-renewing subscription), the transaction fails and the error message is: "An unknown or unexpected error has occurred. Please try again later." Tried to debug in XCode and can only see that the transaction state goes from purchasing to failed. I've checked that in app purchases are enabled in capabilities in the XCode project, all the products are set up appropriately in AppStoreConnect, and canMakePurchases returns true every time. Curious if anyone has run into this issue and what was done to mitigate. Thanks!
Tested environment (Emulator? Real Device?)
Real device

Before testing, have you logged out of your device by going to Settings -> TAP Your name Apple ID at the top -> Sign Out
Then do the purchase again. You will be prompted to login with your Apple ID, use the Sandbox user.

getting the same things as tjviking.  I started using this plugin 2 days ago for the first time.  I've test in_app purchases before as an IOS developer, first time with flutter.  I am logging in with sandbox account when trying to purchase and it is successfully pulling down the products for display.
Purchase Started !!
Purchase Failed  !!
flutter: Caused err. Set additionalSuccessPurchaseListenerIOS.
flutter: PlatformException(E_UNKNOWN, An unknown or unexpected error has occured. Please try again later., null)
flutter: PlatformException(ios, platform not supported, null)

@jodymac @tjviking I had this same exact issue. Switching to the Google Flutter team plugin was the best way to solve this. This exact error was reported out differently by this other plugin and it was much easier to debug. Link here: https://pub.dev/packages/in_app_purchase

Thanks.  I don’t suppose you could send an example of working code for this.  I found very little on the internet to work with and the example doesn’t work for me.  I am trying to download two subscriptions and be able purchase them, on iOS first.

On Jun 13, 2019, at 4:45 PM, ericduffett<EMAIL_ADDRESS>wrote:
@jodymac https://github.com/jodymac @tjviking https://github.com/tjviking I had this same exact issue. Switching to the Google Flutter team plugin was the best way to solve this. This exact error was reported out differently by this other plugin and it was much easier to debug. Link here: https://pub.dev/packages/in_app_purchase https://pub.dev/packages/in_app_purchase
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/dooboolab/flutter_inapp_purchase/issues/47?email_source=notifications&email_token=AF7MOFAWX77YNA6KLUEFJI3P2LLZPA5CNFSM4GATPQH2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXVKPGQ#issuecomment-501917594, or mute the thread https://github.com/notifications/unsubscribe-auth/AF7MOFFT7XPX6KCFDPXQPETP2LLZPANCNFSM4GATPQHQ.

subscriptions download ok for me I can show products, but when calling buyProduct or buySubscription with valid SKU , I got PlatformException which states that Product id is wrong, which is not possible, product was added and accepted by Appstore connect and is valid
@jodymac maybe you do not use non-consumable subscription product, if its non-consumable non-subscription product it all works ok

@jodymac @tjviking I'm thinking back on this and how I fixed it after switching plugins. One thing that came to mind is that I think one of the issues I ran into was that I hadn't accepted the latest agreements from apple in appstoreconnect or my apple developer account. Before you do any more coding, try going there and making sure you've accepted the latest terms and conditions on both platforms.
I don't have any code for auto-renewing subscriptions, but I have successfully implemented non-renewing subscriptions by treating them like a consumable. I don't have any code I can share, but I am happy to move this chat to another channel to discuss in more detail.

I suppose we should move this somewhere else.  But, I have it downloading and buying.  Just need to parse receipts so I can keep features enabled on valid subscription and the required restore button for purchase in the app store.

On Jun 14, 2019, at 5:08 AM, ericduffett<EMAIL_ADDRESS>wrote:
@jodymac https://github.com/jodymac @tjviking https://github.com/tjviking I'm thinking back on this and how I fixed it after switching plugins. One thing that came to mind is that I think one of the issues I ran into was that I hadn't accepted the latest agreements from apple in appstoreconnect or my apple developer account. Before you do any more coding, try going there and making sure you've accepted the latest terms and conditions on both platforms.
I don't have any code for auto-renewing subscriptions, but I have successfully implemented non-renewing subscriptions by treating them like a consumable. I don't have any code I can share, but I am happy to move this chat to another channel to discuss in more detail.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/dooboolab/flutter_inapp_purchase/issues/47?email_source=notifications&email_token=AF7MOFDWBMZIYT4CJJFLDQLP2OC4LA5CNFSM4GATPQH2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXWTFRQ#issuecomment-502084294, or mute the thread https://github.com/notifications/unsubscribe-auth/AF7MOFHQJQEX2TMOVJTKE4TP2OC4LANCNFSM4GATPQHQ.

@jodymac
I just had the error
Purchase Failed !!
flutter: Caused err. Set additionalSuccessPurchaseListenerIOS.
flutter: PlatformException(E_UNKNOWN, An unknown or unexpected error has occured. Please try again later., null)
flutter: PlatformException(ios, platform not supported, null)

Trying to purchase an autorenewing subscription while still logged in as a previous sandbox user. I forgot to sign out at Settings -> iTunes and App Store -> Scroll down to SANDBOX ACCOUNT

When testing an autorenewing purchase you need to create a new sandbox account each time you want to test a purchase

Yes, I've test with sandbox user and on my actual device.  Didn't make a difference.  I was really hoping to use this plugin as it's apparent the developer had put some thought into it and the example/documentation was much better than the others.  I switched to in_app_purchase and have successfully initiated purchases, but am trying to figure out restore and checking receipt for expiration date on subscription.

I switched to in_app_purchase and it works nicely with subscriptions, so stop wasting you time :P move on

Sorry that I was so busy these days and couldn't follow up all the threads promptly. I knew that Google's official plugin has been raised and I even lost myself potent to maintain this plugin since it is so meaningless for me to handle all this by myself when there is already an official one.
I am thinking of deprecating this plugin and recommend users to use official one instead.

2.0.0+ has raised today. Please feel free to reopen after trying out 2.0.0+5 or above.

This issue is still happening for me.
I am using the flutter_inapp_purchase: ^5.1.2 version.
This issue is happening in the Sandbox environment.


docs: wrong threshold for LLMQ_25_67

Invalid number of minimum members in comments for LLMQ_25_67
Issue being fixed or feature implemented
Invalid number of minimum members in comments for LLMQ_25_67
What was done?

Replaced 67 with 17

How Has This Been Tested?
None
Breaking Changes
None
Checklist:

[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have added or updated relevant unit/integration/functional/e2e tests
[x] I have made corresponding changes to the documentation
[x] I have assigned this pull request to a milestone (for repository code-owners and collaborators only)

We DO NOT create branches for PRs on this repo. Please don't do so in the future, instead create PRs from a fork only.


getAutomaticTypeDirectiveNames should ignore directories starting with a dot

From https://stackoverflow.com/q/52275074 (if my suspicion is correct).  It's probably reasonable to expect automatic type reference directives to ignore directories starting with a dot, just as the normal ** wildcard for files does.

TypeScript Version:  master (ee7d0e2)

Search Terms: automatic type reference directive getAutomaticTypeDirectiveNames dot hidden
Code
Run the following shell script in an empty directory:
mkdir -p<EMAIL_ADDRESS>echo 'console.log(42);' >a.ts
echo '{}' >tsconfig.json
tsc

Expected behavior: Successful compilation.
Actual behavior: error TS2688: Cannot find type definition file for '.svn'.
Playground Link: N/A
Related Issues: None found

Fixed by #27260.


mackerel_service create failure if memo includes "&"

Setting to reproduce
resource "mackerel_service" "foo" {
  name = "foo"
  memo = "foo&"
}

terraform apply result
actual
Error: API request failed: Internal server error.

expected
mackerel_service.foo: Creation complete

Note

Probably occurs on mackerel_role, too.
My workaround is using full width ＆ not half width &

Environment
(2021/8/11 Add)

terraform 1.0.4
terraform-provider-mackerel 0.0.3

Slack でもお伝えしたのですが、改めて再現確認を行ったところ全く起きなかったので対応の優先度は下げていただいて良いです。。

Thank you for double-checking.
I think the error is due to a temporary problem with the service.
Please change the value of memo to foo& and try again.

Since this is caused by a temporary service error, please let me close this Issue.
If the problem occurs again, please reopen the Issue.


CSS <source-size-*> are no longer extracted from HTML spec

Release notes of Webref v6 says that Reffy no longer extracts re-definitions of selectors from the HTML spec (on purpose).
Explicitly, this means that <source-size-*> are no longer extracted, but I cannot find their definitions in any other CSS spec.
Statically defining these three types on my side is not a problem, but I just wanted to clarify the reason why they are not extracted anymore.

That is unrelated. These constructs are not selectors. They are no longer extracted because the spec fails to specify their type (no data-dfn-type attribute) and the extraction logic now relies on that type.
Ideally, the definitions should be completed with data-dfn-type="type" attributes, not to confuse them with "regular" terms and so that crawlers such as Reffy may understand that they are looking at CSS type definitions. Would you be up for a PR against the HTML spec?

Oh ok. I can submit a PR, of course.
Aside: I was looking in the Bikeshed doc if it would also require data-dfn-for with the HTML sizes attribute name, and I am still unsure of what a value is, because it says that there is only value and descriptor that can have data-dfn-for, ie. type, which are annotated in <> cannot be namespaced.

Yeah, good points, this is allowed.
You are also right for sizes. data-dfn-for is not intended to namespace a CSS value with an HTML attribute. I was just checking.


Fix Client.stop promise

The inner promise needs to be returned otherwise consumers will only
have waited for resolveConnection() and not shutdown().

Hi @kentor, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, MSBOT;

Hi @kentor, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, MSBOT;

not sure why test is failing

Yeh, I've noticed the CI system is not compiling the PR but rather the master branch.
In one of my PRs I moved the err'ing file, messageReader.ts, elsewhere yet I still get a similar error in my PR: https://travis-ci.org/Microsoft/vscode-languageserver-node/builds/175949270. I guess this (not compiling the PR) was intentended.
I guess something like below might help:

Reproduce build env locally. If you figure out how pls do share.
Open each project as separate windows in vscode, this way build errors are shown.

This is fixed on master in the following way:
		return this.resolveConnection().then(connection => {
			return connection.shutdown().then(() => {
				connection.exit();
				connection.dispose();
				this.state = ClientState.Stopped;
				this._connection = null;
				let toCheck = this._childProcess;
				this._childProcess = null;
				// Remove all markers
				this.checkProcessDied(toCheck);
			})
		});

Any objection to close this PR

👍 either way works


Kotlin DSL isn't marked with @DslMarker

I think you force pushed the Kotlin branch and you must've forgot to recreate the annotation annotated with @DslMarker to mark the DSL methods as DSL methods.

I did not forget - I was told that it was useless there. If you can link to some documentation that says otherwise, I will re-add it.

https://kotlinlang.org/docs/type-safe-builders.html

That shows the annotation being applied to classes, not methods.

Also, in addition to that, it makes the colour of the functions go a nice colour in IntelliJ (it goes one of four colours)

Let me cite some of my own uses of the @DslMarker annotation

https://github.com/BomBardyGamer/komponent/blob/master/src/main/kotlin/me/bardy/komponent/dsl/ComponentDSL.kt

I'm not asking for your code, I'm asking for official documentation that the annotation being on methods is supported.

Actually, there isn't any official documentation about it, you're right. That's strange, since it's perfectly fine to annotate functions with @DslMarker, and it does work as intended on functions.


Release artifact for release v1.0.4

Release artifact for release v1.0.4
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

/cc @jaypipes

Skipping 1.0.3?

@RedbackThomson Looks like we already released 1.0.3 - my PR in https://github.com/aws-controllers-k8s/sqs-controller/pull/35/files#diff-ab3e9fcf0ffe762ed2805586f2e116f0c38db08c3b34d6ba2cfa90e871a1d918 unintentionally downgraded the version. 1.0.4 is the correct next version


Deployment failed. Correlation ID: c6882a90-c481-4051-9e2f-f6fd35aa595b. Internal server error.

This is another error as well following the guide using default vnets
az aro create --resource-group $RESOURCEGROUP --name $CLUSTER --vnet aro-vnet --master-subnet master-subnet --worker-subnet worker-subnet --client-id xxxxxxxxxxxx --client-secret XXXXXXXXXXX
Deployment failed. Correlation ID: c6882a90-c481-4051-9e2f-f6fd35aa595b. Internal server error.
[Enter feedback here]

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

ID: 08eb181a-b377-c854-69cc-3b9307f59f72
Version Independent ID: 2142cb43-b027-86a1-6d3c-2f77bf86d177
Content: az aro
Content Source: src/azure-cli/azure/cli/command_modules/aro/_help.py
GitHub Login: @rloutlaw
Microsoft Alias: routlaw

aro

Hey @medavamshi . This is not the repo we are monitoring constantly. If you raise issue in Azure/ARO-RP we will get into it faster for bugs, not questions, it this relates to service itself, not CLI,
This particular failure is because of CSX Master Policy failure. And few other failures. I would be reluctant to share more details here as it might be sensitive information for you. And this is not the right place to do this kind of support.
If you raise an incident with msft support and ask it to be assigned into "Azure Red Hat OpenShift / RP" queue, we will pick it up with more details and particular polies in question here.

I actually tried to created it under the ARO , and it accidentally created it here.  Tried to delete it and couldnt find it. thank you.  Appreciate your help


Async pattern does not support Application Insight logging

Can you confirm that for async functions, Application Insight logging works? We are working with a Java codebase and it appears that when we implement an async function, Application Insight logging no longer works.
Seems to be the same issue with Python https://github.com/Azure/azure-functions-python-worker/issues/898
We are only implementing async due to the hard 230 second timeout from Azure Load Balancer, this issue was our first suprising disappointment.
Now that we have implemented async, we discover that Application Insights doesn't work. For a "headless" function it's critical to have back end logging to see what's going in.
If Application Insights doesn't work for the async pattern, please make it clear in the doco
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 6fea460c-4fac-723f-8df4-9d0811855a68
Version Independent ID: 4be364ca-aee7-7b49-13e1-3a94408ed7b9
Content: Asynchronous Request-Reply pattern - Azure Architecture Center
Content Source: docs/patterns/async-request-reply.yml
Service: architecture-center
Sub-service: design-pattern
GitHub Login: @martinekuan
Microsoft Alias: architectures

@ElectricLlama
Thank you for bringing this to our attention.
I've delegated this to content author @martinekuan, who will review it and offer their insightful opinions.


Notice branch WIP

There's a branch called 'notion' that contains a WIP for toggling CHAP vs PAM authentication.  It pulls in the notion fork.  Untested so if anyone happens to use it, I'd be ecstatic to find out.

My notion forked branch was mostly for some specific changes to the hard-coded files.  Once I got it working, I proceeded to forget about it  :)
Recently, I needed to support a Google IPSec tunnel, which spawned a trove branch (new company name).  This branch comes with the following changes and I'm happy to submit a PR if those changes are desired for this repo

install packages at the same time
move all config file settings to cookbook attributes and generate the config files automatically
If a config file changes, restart the service once at the end of the Chef run
allow ipsec package to be replaced (by strongswan)
sort ipsec.secrets wildcard records to the bottom

Sample JSON config using StrongSwan
{
        "l2tp-ipsec": {
                "ipsec-package": "strongswan",
                "public_interface": "ens4",
                "private_interface": "ens7",
                "ppp_link_network": "<IP_ADDRESS>/24",
                "ipsec-conf": {
                        "config": {
                                "config setup": {
                                        "charondebug": "\"enc 0, net 0\""
                                },
                                "conn l2tp-psk": {
                                        "authby": "secret",
                                        "auto": "add",
                                        "dpdaction": "clear",
                                        "dpddelay": "30",
                                        "dpdtimeout": "120",
                                        "keyingtries": "1",
                                        "left": "PU.BL.IC.IP",
                                        "leftprotoport": "17/1701",
                                        "rekey": "no",
                                        "right": "%any",
                                        "rightprotoport": "17/%any",
                                        "type": "transport"
                                },
                                "conn gcp-vpn": {
                                        "authby": "secret",
                                        "auto": "start",
                                        "dpdaction": "clear",
                                        "dpddelay": "30",
                                        "dpdtimeout": "120",
                                        "left": "PU.BL.IC.IP",
                                        "leftsubnet": "<IP_ADDRESS>/16",
                                        "right": "RE.MO.TE.IP",
                                        "rightsubnet": "<IP_ADDRESS>/16",
                                        "type": "tunnel"
                                }
                        }
                },
                "xl2tpd-conf": {
                        "config": {
                                "lns default": {
                                        "unix authentication": "yes",
                                        "ip range": "<IP_ADDRESS>-<IP_ADDRESS>",
                                        "local ip": "<IP_ADDRESS>"
                                }
                        }
                },
                "options-xl2tpd": {
                        "config": {
                                "login": ""
                        }
                },
                "ipsec-secrets": {
                        "config": {
                                "PU.BL.IC.IP RE.MO.TE.IP": "PSK \"SECRET\"",
                                "PU.BL.IC.IP %any": "PSK \"ANY_SECRET\""
                        }
                }
        }
}

Ah, thanks @devsibwarra for the info.    Instead, I'll add a pointer to the README to trove branch if that's okay for people who might be interested in more of the smart version of the cookbook.


Revisit logs in plugins

As reported in slack by Martin Mobius, we should revisit all of the plugin logs and update the log level accordingly.
[Martin Möbius](https://app.slack.com/team/U022GLC8D55)  [1:34 PM](https://netapppub.slack.com/archives/C02072M1UCD/p1654848275095899) I get an error about collecting disk data. Failed to collect disk data error="no instances" I saw in the code you do a disk-encrypt-get-iter request. This doesn't return any disks if the disks have no encryption capability. I am not sure if this is intended. getDiskData function name and the error messages don't imply that the lookup is about encryption disks.

Verified Martin's issue is addressed in release/22.08.0 a05a0279. Also verified the other plugin logger changes.


Signature algorithms cert extension

Resolved issues:
resolves #2247, resolves #1538
Description of changes:
This pr adds functionality for receiving the signature_algorithms_cert extension which allows clients to choose which signature algorithm they accept for certificate signing.
Call-outs:
The integration test is coming in a later pr. Previously the extension and integration test were in the same pr (#2311), but the discussion disparate so I decided to split the pr.
Testing:
I included both unit tests and functional tests.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

Merging #2329 into main will increase coverage by 5.98%.
The diff coverage is 66.66%.

@@            Coverage Diff             @@
##             main    #2329      +/-   ##
==========================================
+ Coverage   81.56%   87.54%   +5.98%
==========================================
  Files         267      167     -100
  Lines       18163    13927    -4236
==========================================
- Hits        14814    12193    -2621
+ Misses       3349     1734    -1615

/cbmc run checks

Closing this as project plan has changed.


fix rsync deploy script

The var @local  was being used throughout the script but the @site_dir was checked for existence. Fixed the rsync deploy script to refer to @local.
Also changed the git deploy script to reflect the same var name: @site_dir -> @local (thought it'll avoid confusion in the future).

@kaushikgopal Thanks!

This was released in 1.2.7. Thanks again! :)

my pleasure :) rock on!


histgram: use millisecond resolution for coarse timer

The processors in an SMP system do not start all at exactly the same time
and therefore the timer registers are typically running at an offset.
Use millisecond resolution for ignoring the error.
CC pingcap/tikv#2165

PTAL @BusyJay

Benchmark:
test histogram::bench_histogram_coarse_timer            ... bench:          51 ns/iter (+/- 0)
test histogram::bench_histogram_timer                   ... bench:          86 ns/iter (+/- 0)
test histogram::bench_local_histogram_coarse_timer      ... bench:          53 ns/iter (+/- 0)
test histogram::bench_local_histogram_timer             ... bench:          87 ns/iter (+/- 2)

LGTM


bootstrap: If password or key file are required we should tell the flags to do so

If you try to bootstrap a node using a username in the URI you will receive a train error instead of a friendly knife error. The user shouldn't see train errors since they don't need to know what handles the transport under the hood. Additionally if there are flags missing we should make sure to let people know what flags they can use so they don't have to hit help or the docs site on their own.
bundle exec knife bootstrap<EMAIL_ADDRESS>--channel unstable -N tim_test
Creating new client for tim_test
Creating new node for tim_test
Connecting to ec2-34-221-181-2.us-west-2.compute.amazonaws.com
ERROR: Train::ClientError: Your SSH Agent has no keys added, and you have not specified a password or a key file

Also: Knife call it an identity file vs. train calling it a key file, which further confuses the issue

Address in https://github.com/chef/chef/pull/8856

Fixes #8856 merged in master


fix senderStaffId issue for dingtalk

Fix issue #439

It turn out the issue only impacting the Test environment.  close it.


Django Logging Formatting Issue

Hi @willmcgugan,
I would just like to ask about configuration for the logging formatting/handling within Django.
Following your post on your blog, I have attempted to configure my own logging within my Django project.
There are 2 major differences between what your blog post, and indeed the project's README displays when compared to my implementation.
For reference, your blog post's screenshot:

The project's README screenshot (albeit not Django):

My implementation displays as:

There are 2 issues with the way my logging is formatted:

You will see that my logging does not have the colorised formatting.

The width is somewhat constrained even though the width of my iTerm terminal window is plenty wide enough. Even when I widen it further, it remains constrained in its width.

It's worth mentioning that my project is in Docker, so I don't know if that's an issue. I have also tested reviewing the development server output within the stock terminal app in Mac OS which gave me the same result.
The timed grouping (with just the time element) and the warning levels both look good so it appears the Rich config is somewhat working.
@willmcgugan For reference, do you have an exact commit reference that points exactly to the settings.py file you referred to in your blog post? Should it matter if it's in Docker instead of just Django's local development server?
I don't know whether this is a config issue from my side, or whether there is a bug or missing feature from Rich itself.
My full logging config in my settings.py file is:
...

    LOGGING = {
        'version': 1,
        'disable_existing_loggers': False,

        'filters': {
            'skip_static_requests': {
                '()': 'django.utils.log.CallbackFilter',
                'callback': skip_static_requests,
            }
        },

        'formatters': {
            'rich': {'datefmt': '[%X]'},
        },

        'handlers': {
            'console': {
                'class': 'rich.logging.RichHandler',
                'formatter': 'rich',
                'level': 'INFO',
                'filters': ['skip_static_requests'],
            }
        },

        'loggers': {
            'django': {
                'handlers': ['console'],
                'level': 'INFO',
                'propagate': False,
            },
        }
    }
...

Please could you advise?
Many thanks,
Wayne

Hi Wayne,
I suspect what is happening is that Rich has detected that it is not writing to a terminal. When that happens, color will be disabled and the width will default to 80.
Docker might explain that, but if you are saying that you get the same result with terminal, then maybe there is something else capturing output.
If you could add this to your project somewhere, it will give us more information:
from rich import get_console
print(get_console())
print(get_console().file)

Also, please check you are running the latest version from Pypi

Hi Will,
Thanks for your very fast reply.
I added the snippet to my project and it gave the following output within the dev server.

Just a few things to clarify:
I am using Docker within iTerm (like screenshot) and did an additional test still using Docker (i.e. docker-compose up) but within the standard terminal app. The same result appears in both.
I haven't actually tested my logging config in any other project using Django's standard runserver command on localhost:8000 so I wouldn't know if that works. I am guessing it would as per your blog post because I cannot see anything wrong with my config.
Yes, I am using the most recent version from PyPi v5.2.0

Hi Will,
Further to above and your original answer, I did some research and found the following StackOverflow post.
It suggested that I need the following key adding to my web service (for my setup) within my docker-compose.yml file:
tty: true

Following that addition, then rebuilding my images and bring up the containers again, I now have...

As you can see, now I have colour, however the width still seems to be constrained to 80 chars.

That's progress.
can you do print(get_console().size).
I suspect that will return 80x25 which means it has failed to detect the terminal size, or it has been override somehow.
Can you also do print(shutil.get_terminal_size()) which is the terminal size as reported by the OS.

OK, following a bit more research, I found a solution to the issue.
There is a variable in zsh (and other Unix shells) called COLUMNS. From this discovery, I then amended the Dockerfile responsible for the dev build and added a step within it's build process:
...
# Set the COLUMNS variable for the terminal's output width
ENV COLUMNS 164
...

Someone else may need to customise that value for their desired window width.
After the rebuild, bringing the container (dev server) back up, and widening the iTerm window, it gave me the following:

Perfect!
For anyone wanting to use Django, Docker, and Rich together, I have recorded the overall solution to the issue in a commit.

Changes Required Git Diff
Check the settings.py file for the LOGGING config

Thanks for your help, @willmcgugan


New DNS errors

Hello everyone,
there's a catch in the new DSN given by Sentry, the component signals it as invalid and no further action will be done.
Someone have already a workaround for it?

Hey @Tbaile, my guess is that you are on an older version of the SDK that does not accept a DSN without the private key... try updating to 0.10.x of this library, that should fix it.

Already tried, currently I'm working with sentry/sentry 1.9.0 and sentry/sentry-laravel 0.10.0.
The system avoids the error using the old DSN with the secret in it.
Some suggestion where to start debugging the whole thing so I can give a hand?

You are a bit behind then 👍

https://github.com/getsentry/sentry-php/releases/tag/1.9.1

So updating to sentry-php of at least 1.9.1 should fix it!

 The issue was in the .lock that "magically" kept all the time the 1.9.0.
Sorry and thank you for the help! 😄

Ah! Happens to the best of us 👍 glad you found it!


Add context to affjax errors when hitting plutip-server so we can debug CI

Debugs #1055.
I've been having difficulty recreating 1055's issue, so to try and gain some more information I've added some context to the problem sites when the problem occurs in the wild
Pre-review checklist

[x] All code has been formatted using our config (make format)
[x] Any new API features or modification of existing behavior is covered as defined in our test plan
[x] The changelog has been updated under the ## Unreleased header, using the appropriate sub-headings (### Added, ### Removed, ### Fixed), and the links to the appropriate issues/PRs have been included

It happens during cluster starting, not server starting or cluster shutdown


T265  connction error

Hello, I am trying to connect realsense d415 and t265 at the same time on my computer. However   when I try to use  realsense-viewer  to see whether the cameras works or not, sometimes I couldnot found t265 device. When I trying to unplug t265 and connected it again, then realsense-viewer can found the device. Did anyone meet similar problem before. I am confused ...

I also encountered an unstable connection in the same environment. Sometimes the device can be seen through the realsense-viewer, sometimes not at all. An exception was encountered while reading with the sample rs-pose-and-image: "No device connected".

Hi @ttomchy, @mickeyouyou,
This should be similar with #4331.

What's your OS? Is T265 recognized as USB2 when you connect T265 without running any librealsense app like realsense-viewer or rs-pose?
Are both d415 and t265 on one USB3 hub and then connected to the host?
Please also show "lsusb" and "dmesg" log before and after you run the librealsense app.

Hi @ttomchy, @mickeyouyou,
Any update? Is the issue clarified?

maybe this is my codes problem. It has been sovled. thank you .

Hi @ttomchy,
Do you also clarify the issue?

Hi @ttomchy,
Any update? Is any USB hub used for T265 and D415?

I will close this if no further question.


Roll Flutter Engine from 8a038a6f7099 to 1d78ba18f024 (4 revisions)

https://github.com/flutter/engine/compare/8a038a6f7099...1d78ba18f024
2024-09-10<EMAIL_ADDRESS>Roll Skia from c62380453c72 to 5dc067350ab5 (1 revision) (flutter/engine#55072)
2024-09-10<EMAIL_ADDRESS>Roll Fuchsia Linux SDK from kIWQ460iagZLxVRPc... to 8XJTJm4D4Go1dBaTi... (flutter/engine#55071)
2024-09-10<EMAIL_ADDRESS>Roll Skia from 9bea95918e69 to c62380453c72 (1 revision) (flutter/engine#55070)
2024-09-10<EMAIL_ADDRESS>Roll Dart SDK from a60078a23978 to d59138eb6ec2 (2 revisions) (flutter/engine#55068)
Also rolling transitive DEPS:
fuchsia/sdk/core/linux-amd64 from kIWQ460iagZL to 8XJTJm4D4Go1
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC aaclarke@google.com,rmistry<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Commit queue failed; closing this roll.


Xamarin cycle 8 compatibility issues

Yesterday I followed the release of the new and stable version of Xamarin and its components just to find that rb-forms-barcode is not longer working. So I dowloaded the sample project to see if the same problems occurs running clean sample and the problem does occur.
The problem persists every time.
As soon as I try to open the scanner page app crashes with the following message:
" Got a SIGABRT while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries. "
Has anyone else experienced such behaviour after following the upgrade to cycle 8?

Hello @NaurisAndzans
I am as well on cycle 8 and everything is working on ios and android for me. Can you clean and build the project completly new please.
What are you doing. I need more infos to help you in this case.

I forgot to add that I'm working on a Macbook and I encounter this problem only with iOS builds. Android builds works as expected.
As soon as the following line gets called the app crashes with the message I posted previously.  Detail.Navigation.PushAndRemovePrevious(ScannerPageControl.Instance.CreateScannerPage(), 1);

we work as well on mac....
and you think that happens due to the scannerlibrary?

can you please create a sample github project that contains the bug.

can you please create a sample github project that contains the bug.

No need, cause I used your original sample without introducing any new features for testing this behaviour. Any other information or additional logs I can provide you with ?

@NaurisAndzans

the exact build version
the version of the iphone
the version of ios
xcode version
if possible the complete stack trace.
mac os version

@armintelker

Rb.Forms.Barcode 0.6.6 and Rb.Forms.Barcode 0.7.1
5S and iPad Air
iOS 10.0.1
XCode 8
Native stacktrace from our app. Your clean sample produced the same results as soon as I tried to access barcode library:

OSX 10.11.6

I am also experiencing the same issue.  Everything was working fine before iOS10.  Now, as soon as the page opens and gets past the default constructor, it crashes.  I am only testing with iOS and have not yet implemented for Android.
RB.Forms.Barcode 0.7.1
Xamarin Studio 6.1
Xamarin.iOS <IP_ADDRESS>
XCode 8/iOS 10

I appears to be crashing in RootPage.xaml.cs line 21:  await cameraPermission.RequestCameraPermissionIfNeeded();
I am wondering if there is some new plist setting we need?

Yep, just figured out the solution.
@NaurisAndzans add this to your info.plist:
Property: "Privacy - Camera Usage Description"
Value:  "Use the camera for XYZ"