Wifi with username/password

Having a hard time finding docs on turning on wifi for more complex networks that require an ssid, username, and password. Is this feature supported at all?

Yes it is, at least as far as it's supported by the raspi-config utility!
Check out these docs for how to access it.

Running on approved hardware, I get an error with Raspi-Config
"cannot communicate with wpa_supplicant"
wifi country, SSID, password, etc are all correct. the hardwire lan connection works, but the unit will need to be deployed in a wireless environment.
I've tried reflashing the SD card with fresh installs, but still get the same error. The hardware is known good in other distros.

@albatrossLol curious! Which hardware are you using? Have you tried flashing vanilla Raspbian? Can you join the WiFi with that?

@albatrossLol curious! Which hardware are you using? Have you tried flashing vanilla Raspbian? Can you join the WiFi with that?

Ok - so I decided to go all the way back down to the basics and do some additional parity testing. Turns out that the somewhere in between the install and implementationm, the wifi chip went bad on 1 of the Rpi 3b's (not +). It joined with eth0 but wlan0 would not show up.
Swapped boards out, reinstalled all and took it from the bench to production room. At first I thought it was hosed again - but I believe I got the connection reset this final time because it was trying to connect to eth0 first this time -- waited a bit and came back and it had switched over to wireless. woo! I'm up and running with no issues. Once it latched onto wireless it took it and ran. We LOVE this and allows us to run Dakboard as a command station for the family.
I had also tested on the Rpi 0 W and it worked very with the exception of rebooting nightly -- it would boot back into the raspi-config page each time until I manually rebooted. I know that piece of hardware wasn't on the list, but wanted to try it anyway.

Oh, just bad luck it seems. Glad you got it working!
Had to look up DAKboard, looks really nice.
A person at my work has actually also set up a 0W-based kiosk and I think at least their initial experiences were positive. If it ends up working for them let's see if we can make the 0W also officially supported!
Anyway, this issue seems sorted out, I'll go ahead and close.


Draft Feedback

When can we be expecting feedback/marks for our draft proposal submission? It seems that the due date for resubmission was today and the final due date is soon, however I haven't received any feedback yet - do we need to book a meeting with you?

Hi,
We will give feedback by the end of this week.

Hi, they should all be in the system now


How to build for other SBC's

Hi,
I want to build EZ-wifibroadcast other than Raspberrypi (like nanopi or tinkerboard). I want to use Debian version only. What are the things I need to take care.

Because this system is based on Raspbian, it can't work on other SBC. Raspbian is designed fro a Raspberry Pi and its CPU and GPU.
On an other SBC, with different CPU and GPU, video, OSD, and perhaps other things (USB ports ?) will not work.
Some people could make in work on a linux pc, but AFAK never on a non Pi SBC.

Well, what @Yes21 says is true to a certain extent.
The kernel modifications etc. can all be made to work on different SBC's.
The Wifibroadcast system itself is heavily dependant on the raspberry pi kernel and tools.
raspivid and the video player used are specific to the Pi.
Supporting different SBC is on my (personal) list of things to achieve. It will be a big effort, not something done in a few days or hours.

As a starting point i wanted to look at:
https://github.com/svpcom/wifibroadcast/issues/19
To see how this could be integrated in the builder.
As stated significant changes need to be made to the Wifibroadcast workings to not rely on raspivid and use gstreamer as a video player.

It seems that Lelik made it work on a nanoPi !
See here.

Thank you @Yes21 @RespawnDespair for leads. I will go through all necessary things to perform on other linux/kernel.

@chipvk Good Luck !!

@chipvk As the solution is not here in this github, please could you close this issue ?

One thing to keep in mind is that the Ground side is much easier to use different hardware (pi vs a pc) than the air side. The air side is very dependent on the code tied to the raspberry pi camera hardware and gpu. The ground side you can very easily get just video on a Linux machine. Telemetry is not all that hard to pump into a ground Linux machine as well.

One thing to keep in mind is that the Ground side is much easier to use different hardware (pi vs a pc) than the air side. The air side is very dependent on the code tied to the raspberry pi camera hardware and gpu. The ground side you can very easily get just video on a Linux machine. Telemetry is not all that hard to pump into a ground Linux machine as well.

Ok


DoctorKafka fails to start NullPointerException  at getProcessingStartOffsets

Hi
I got DoctorKafka to run previously with one broker on my local machine. I added two other brokers on same IP different ports. (Total kafka cluster with 1 zk node and 3 brokers). Doctor Kafka fails to start with below.
12:44:49.344 [pool-8-thread-1] ERROR com.pinterest.doctorkafka.DoctorKafkaMain - DoctorKafka start failed
java.lang.NullPointerException: null
        at com.pinterest.doctorkafka.util.ReplicaStatsUtil.getProcessingStartOffsets(ReplicaStatsUtil.java:28) ~[doctorkafka-<IP_ADDRESS>.jar:?]
        at com.pinterest.doctorkafka.replicastats.ReplicaStatsManager.readPastReplicaStats(ReplicaStatsManager.java:82) ~[doctorkafka-<IP_ADDRESS>.jar:?]
        at com.pinterest.doctorkafka.DoctorKafka.start(DoctorKafka.java:56) ~[doctorkafka-<IP_ADDRESS>.jar:?]
        at com.pinterest.doctorkafka.DoctorKafkaMain.lambda$run$0(DoctorKafkaMain.java:78) ~[doctorkafka-<IP_ADDRESS>.jar:?]
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0_252]
        at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_252]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_252]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_252]
        at java.lang.Thread.run(Thread.java:748) [?:1.8.0_252]
INFO  [2020-05-29 19:44:49,356] org.eclipse.jetty.setuid.SetUIDListener: Opened application@359066bc{HTTP/1.1,[http/1.1]}{<IP_ADDRESS>:8080}
INFO  [2020-05-29 19:44:49,359] org.eclipse.jetty.server.Server: jetty-9.4.18.v20190429; built: 2019-04-29T20:42:08.989Z; git: e1bc35120a6617ee3df052294e433f3a25ce7097; jvm 1.8.0_252-8u252-b09-1~18.04-b09
INFO  [2020-05-29 19:44:49,812] io.dropwizard.jersey.DropwizardResourceConfig: The following paths were found for the configured resources:

Dr. Kafka wasn't designed to have single node multi-broker operations so ideally your brokers should be well distributed across nodes with 1 broker per node.

Ok I understand that but it should not fail with NPE. Since this is valid Kafka setup for dev box.


There is no way to update the items as it only takes in the initialItems

Overview
We dynamically change the items but here the items are initial only? Was that intentional?
Package versions
react-vis-timeline: 2.0.3
vis version: 4.21.0
Steps to reproduce
Add step by step guide to reproduce issue

Creating the timeline sending in initialItems and initialGroups
Items were updated but the timeline stays the same

Code Snippet
           <Timeline
                options={timelineOptions}
                ref={timelineRef}
                initialItems={timelineItems}
                initialGroups={updatedGroups}
                rangechangeHandler={rangeChangeHandler}
            />

Related issues
Any issue which is related to this issue

e.g. issue 123

Screenshots (if appropriate)

what i did was instead of adding the items in initialItems I added them in a useEffect:
useEffect(
() => {
if (timelineRef.current.timeline) {
timelineRef.current.timeline.setItems(timelineItems);
}
},
[timelineItems]
);

what i did was instead of adding the items in initialItems I added them in a useEffect:
useEffect(
() => {
if (timelineRef.current.timeline) {
timelineRef.current.timeline.setItems(timelineItems);
}
},
[timelineItems]
);

Yes, your mehod is correct for changing the items.
initialItems is exists for more like static situations, when you have all data before and just want to display it once.
I know this can confusing - two ways for passing data. So I works on next version, which uses only react props, but also good at performance by using vis's native api.


T03.01 exercise and solution missing resource file number_list_item.xml

I want to work on this issue.

WORKAROUND: it can be copied from T03.03 (it is ALSO missing in T03.02).
NOTE: it is shown in the video so it must have been deleted at some point by accident.
Without it neither T03.01 nor T03.02 (both exercise and solution) can be compiled.

WORKAROUND: it can be copied from T03.03 (it is ALSO missing in T03.02).
NOTE: it is shown in the video so it must have been deleted at some point by accident.
Without it neither T03.01 nor T03.02 (both exercise and solution) can be compiled.

You can find that in the T03.02 solution. But it should add in T03.01(both exercise and solution) and T02.02(exercise).


Prevent the creation of "a.out" at the repo root

Our clever "gcc" invocations were creating a spurious "a.out" file at the root of the repo (which just happened to be in ".gitignore" so we didn't notice it sooner).
A perfect example of why I'm a big fan of a very, very slim ".gitignore". :innocent:

LGTM when janky is happy!

LGTM


[SPARK-8601][ML] Add an option to disable standardization for linear regression

Merged build triggered.

Merged build started.

Test build #35853 has started for   PR 7037 at commit e47c574.

Test build #35853 has finished for   PR 7037 at commit e47c574.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #35879 has started for   PR 7037 at commit e54a8a9.

Test build #35879 has finished for   PR 7037 at commit e54a8a9.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

You don't cover all the test cases including with/without intercept. Also, for regParam = 0, they should converge to the same solution.

Merged build triggered.

Merged build started.

Test build #36173 has started for   PR 7037 at commit 99ce053.

Test build #36173 has finished for   PR 7037 at commit 99ce053.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Merged build triggered.

Merged build started.

Test build #36177 has started for   PR 7037 at commit b83a41e.

Test build #36177 has finished for   PR 7037 at commit b83a41e.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class StreamingLinearAlgorithm(object):
class StreamingLinearRegressionWithSGD(StreamingLinearAlgorithm):
      class SpecificOrdering extends $
    class SpecificProjection extends $
    final class SpecificRow extends $

Merged build finished. Test PASSed.

@dbtsai I've extended the test coverage.

@holdenk Cool. I'll work on this tonight. Thanks.

Merged build triggered.

Merged build started.

Test build #36975 has started for   PR 7037 at commit b83a41e.

Test build #36975 has finished for   PR 7037 at commit b83a41e.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Merged build triggered.

Merged build started.

Test build #36983 has started for   PR 7037 at commit eebe10a.

Test build #36983 has finished for   PR 7037 at commit eebe10a.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class KafkaRDD(RDD):
class KafkaDStream(DStream):
class KafkaTransformedDStream(TransformedDStream):
class GenericInternalRowWithSchema(values: Array[Any], override val schema: StructType)
case class StreamInputInfo(

Merged build finished. Test FAILed.

jenkins, retest this please

Merged build triggered.

Merged build started.

Test build #36985 has started for   PR 7037 at commit eebe10a.

Test build #36985 has finished for   PR 7037 at commit eebe10a.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class GenericInternalRowWithSchema(values: Array[Any], override val schema: StructType)

Merged build finished. Test PASSed.

Merged build triggered.

jenkins, retest this please

Merged build triggered.

Merged build started.

Test build #29 has started for   PR 7037 at commit eebe10a.

Merged build triggered.

Merged build started.

Test build #37572 has started for   PR 7037 at commit eebe10a.

Test build #29 has finished for   PR 7037 at commit eebe10a.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test build #37572 has finished for   PR 7037 at commit eebe10a.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Merged build triggered.

Merged build started.

Merged build finished. Test FAILed.

@holdenk can you merge master? Thanks.

Merged build triggered.

Merged build started.

Test build #37926 has started for   PR 7037 at commit 6b1dc09.

Test build #37926 has finished for   PR 7037 at commit 6b1dc09.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.


Use with existing volume?

Thanks for this plugin, I think it could come in very useful! :tada:
I have an existing volume, let's call it volume-nbg1-1-test, with the ID 1234567.
How would I go about using this volume and attaching it to a Docker container?
I tried a simple docker-compose.yml with:
version: "3.5"

volumes:
    volume-nbg1-1-test:
        driver: hetzner

But it returns:

Creating volume "docker-volume-test_volume-nbg1-1-test" with hetzner driver

So it's adding some prefix, and I assume it's not looking for existing volumes?

Yes, exactly. In this case you can either configure the plugin to use volume as a prefix (assuming this is a standard you have been using for other volumes), or, if it's about the single volume, just rename it to match the driver's default prefix.
TBH I haven't used the plugin myself for a while, but it should reuse the existing volume if the name matches.

Okay, I'll try the prefix thing. Perhaps the README could mention the use of an existing volume – I can provide a PR if I can get it to work. (Unfortunately I can't yet, see #6)

The problem with the prefix is that it will always be separated from the chosen volume name by a hyphen. Also, when creating the Docker volume, Docker Compose will additionally prefix the volume with the project name.
For example, I have the project docker-volume-test with the YAML config:
version: "3.5"

services:
    test:
        image: alpine
        volumes:
            - analytics:/test
        command: "tail -f /dev/null"

volumes:
    analytics:
        driver: hetzner
        driver_opts:
            fstype: xfs
            size: 10 # in GB, default: 10

Then it will create the following Hetzner volume:
docker-docker-volume-test_analytics

I'll shortly provide a PR that clarifies the README w.r.t. that.


Define a new folder structure

Leave suggestions below

Looking at the current structure of the project, there are some alarming things, namely the fact that the utilities package is a large part of the code base.
With that in mind, one possible solution is to:

Have code that is used throughout the whole website in a common package;
Code related to a single page should be separated into its own file; these files could live in a pages directory;
Things like tables can occur several times. In order to keep the same styles and structure, there could be a components directory containing code for these situations: each page would only need to include/run it when needed;
non-UI related code should live separately from UI code: things related to being authenticated and such could live in a auth folder;
This is just a personal opinion but if possible there should be any "utils" code at all. ON the rare occasion that it makes some sense to have said code, you could make some "localized" (i.e., annex to the code or bits of code that use it) utils package/file.

One other thing to keep in mind is to not run every bit of javascript in every page since this can slow down page loads. Instead (and as @LuisDuarte1 suggested) we should have a mapping from URLs to "Page scripts". My 2 cents on this is to have a centralized "page registry", kinda like:
// pageRegistry.js

const pageMapping = {} // mapping: URL Regex -> Function

const registerPage = (pageUrlRegex, pageLoader) => pageMapping[pageUrlRegex] = pageLoader;

const loadPage = (pageUrl) => {

    for (const urlRegex of pageMapping) {
        if (pageUrl.match(urlRegex)) {
            pageMapping[pageUrlRegex]();
            return;
        }
    }
}

The code might not be correct but you get the idea

This way, when a page loads, you only need to run the corresponding loader.
This is all based on personal experience and I invite other people to argue about the pros and cons of this structure and provide their own solutions.

P.S.: Typescript is cool :P

Closed in #173


updated tar package version to 4.4.8

Checklist

[x] npm install && npm test passes
[ ] commit message follows commit guidelines

Description of change
I updated tar package version in which there were vulnerabilities:
About vulnerability: https://app.snyk.io/vuln/SNYK-JS-TAR-174125
Reviewers
@TooTallNate

should package-lock.json actually be committed ? It is not until now.

AFAICT, the only BC break in v4 is https://github.com/npm/node-tar/commit/a22932a5ed3dd057994e4f53d9e7af0ff7e38a16

shouldn't this be patched in the 3.x to be able to have it in a 3.8.1 release ?

CI: https://ci.nodejs.org/job/nodegyp-test-pull-request/118/

/me follows thread so he'll know when 3.8.1 is tagged, to unblock builds 'n' stuff

When might this be released?

Running CI for v3.x branch - https://ci.nodejs.org/job/nodegyp-test-pull-request/119/

CI for v3.x fails. Could someone backport this? I'll try to publish as soon as we get tests to pass.

Gotta love it when you apply a security patch to your dependency (in this case, tar) and it includes breaking changes (TypeError: tar.Extract is not a function). </sarcasm>

Gotta love it when you apply a security patch to your dependency (in this case, tar) and it includes breaking changes (TypeError: tar.Extract is not a function). </sarcasm>
-  "tar": "^3.1.3",
+  "tar": "^4.4.8",

tar isn't going to backport the security patch to the 3-series, huh?

tar.Extract was removed in tar@3. <EMAIL_ADDRESS>is still using tar@2
https://github.com/nodejs/node-gyp/blob/e6699d13cdcd6abe543b250f4297808912a4a188/package.json#L35
When we bumped tar to 3 (https://github.com/nodejs/node-gyp/pull/1212) it was deemed a breaking change so it was made on master but not the v3.x branch. It was breaking for Node.js v0.10 and Node.js v0.12 which are long out of support, so maybe we can reconsider that decision? cc @nodejs/node-gyp

@richardlau confirmed that porting the changes from #1212 into the v3.x branch makes all the tests pass

Any idea when this will be released? All of our CI builds are complaining about the vulnerability.

@ebmeierj see https://github.com/nodejs/node-gyp/pull/1718 for the work on bring that in the 3.x codebase (currently, it is merged only in master, which is the WIP of 4.0)

Seems that a lot of people are having this issue... I suppose you could say they are stuck on the tar?

@smity81435 Yes that is where I am stuck.

Is there anything that we could in order to temporarily fix this ?

Change your package-lock and use npm ci to install your deps
On Fri, 26 Apr 2019, 13:21 iwaduarte<EMAIL_ADDRESS>wrote:

Is there anything that we could in order to temporarily fix this ?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/nodejs/node-gyp/pull/1713#issuecomment-487022833, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AA4MKIWDTZLONOIWN6LQGVDPSLQSTANCNFSM4HEGUDDQ
.

Change your package-lock and use npm ci to install your deps
…
On Fri, 26 Apr 2019, 13:21 iwaduarte, @.***> wrote: Is there anything that we could in order to temporarily fix this ? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#1713 (comment)>, or mute the thread https://github.com/notifications/unsubscribe-auth/AA4MKIWDTZLONOIWN6LQGVDPSLQSTANCNFSM4HEGUDDQ .

Change it how?

@jaysunwalter123 see https://github.com/sass/node-sass/issues/2625#issuecomment-482519446

Is it safe/recommended to modify npm manged file 'package-lock.json'? I've always thought it's not and such manual edits are discouraged.

Change your package-lock and use npm ci to install your deps

I am still getting this issue:
Error: node-gyp rebuild failed with: Error: Command failed: node-gyp rebuild
gyp info it worked if it ends with ok
gyp info using<EMAIL_ADDRESS>gyp info using<EMAIL_ADDRESS>| darwin | x64
gyp info find Python using Python version 2.7.15 found at<EMAIL_ADDRESS>gyp http GET https://nodejs.org/download/release/v10.16.0/node-v10.16.0-headers.tar.gz
gyp http 200 https://nodejs.org/download/release/v10.16.0/node-v10.16.0-headers.tar.gz
gyp ERR! UNCAUGHT EXCEPTION
gyp ERR! stack TypeError: tar.extract is not a function

any idea how to resolve this?
HF


[Enhancement] Ability to pass along additional Helm chart values

Current Behavior
Meshery Adapters do not support the ability to pass along any Helm chart values, but only specific values.
Slack Message

@leecalcote @Revolyssup I would like to take this up. Can you provide the resources to get started?

Context: https://layer5io.slack.com/archives/C017NA80S66/p1686685751408429


Vibrant Capacitor Bank Bug

I'm am experiencing the same bug as #1445 in the latest version of EnderIO in a modpack called SkyFactory version 2.2.3.
The Capacitor won't allow me to set input mode in the side where the tesseract is attached to.

The tesseract signals that is only accepts power and does not output power - that is why the cap bank won't offer input mode.


'$client' is of type 'unknown'.ts-plugin(18046) const $client: unknown

This is the code

And this is the error on $client
'$client' is of type 'unknown'.ts-plugin(18046)
const $client: unknown

Most of the time removing .nuxt folder and node_modules + reinstall fixes this issue

https://github.com/wobsoriano/trpc-nuxt/issues/91


Please add support for specifying an HTTP proxy

Feature request
like:
aicommits config set proxy="http://localhost:7890"
Why?
In some regions, accessing the internet requires the use of an HTTP proxy. Therefore, I request that support for specifying an HTTP proxy be added to the software. This would enable users in such regions to use the software without encountering connectivity issues.
Alternatives
Currently, you can use the system global proxy and soft router to set the proxy.
Additional context

Already happening here: https://github.com/Nutlope/aicommits/pull/139

Dear developer, not being able to use proxy is driving me crazy, please fix this ASAP, I will be very grateful ！！！🙏💗


🐛 [firebase_storage] No error handling on snapshotEvents.listen possible

Bug report
Describe the bug
When listening to snapshotEvents on uploading a file to the storage, it never catches errors, even though the exception is thrown and can be seen in the debug console:
E/StorageException(20373): StorageException has occurred.
E/StorageException(20373): User does not have permission to access this object.
E/StorageException(20373):  Code: -13021 HttpResult: 403
E/StorageException(20373): The server has terminated the upload session
E/StorageException(20373): java.io.IOException: The server has terminated the upload session
E/StorageException(20373): 	at com.google.firebase.storage.UploadTask.serverStateValid(UploadTask.java:339)
E/StorageException(20373): 	at com.google.firebase.storage.UploadTask.shouldContinue(UploadTask.java:308)
E/StorageException(20373): 	at com.google.firebase.storage.UploadTask.run(UploadTask.java:232)
E/StorageException(20373): 	at com.google.firebase.storage.StorageTask.lambda$getRunnable$7$com-google-firebase-storage-StorageTask(StorageTask.java:1072)
E/StorageException(20373): 	at com.google.firebase.storage.StorageTask$$ExternalSyntheticLambda3.run(Unknown Source:2)
E/StorageException(20373): 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
E/StorageException(20373): 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
E/StorageException(20373): 	at java.lang.Thread.run(Thread.java:923)
E/StorageException(20373): Caused by: java.io.IOException: {  "error": {    "code": 403,    "message": "Permission denied."  }}
E/StorageException(20373): 	at com.google.firebase.storage.network.NetworkRequest.parseResponse(NetworkRequest.java:445)
E/StorageException(20373): 	at com.google.firebase.storage.network.NetworkRequest.parseErrorResponse(NetworkRequest.java:462)
E/StorageException(20373): 	at com.google.firebase.storage.network.NetworkRequest.processResponseStream(NetworkRequest.java:453)
E/StorageException(20373): 	at com.google.firebase.storage.network.NetworkRequest.performRequest(NetworkRequest.java:272)
E/StorageException(20373): 	at com.google.firebase.storage.network.NetworkRequest.performRequest(NetworkRequest.java:289)
E/StorageException(20373): 	at com.google.firebase.storage.UploadTask.send(UploadTask.java:469)
E/StorageException(20373): 	at com.google.firebase.storage.UploadTask.uploadChunk(UploadTask.java:428)
E/StorageException(20373): 	at com.google.firebase.storage.UploadTask.run(UploadTask.java:231)
E/StorageException(20373): 	... 5 more
E/StorageException(20373): StorageException has occurred.

Steps to reproduce
Steps to reproduce the behavior:
I followed the documentation and tried to upload a file to a storage bucket where the user doesn't have permission. An error is thrown as can be seen in the debug console, but it doesn't enter the error case of the task snapshot's state.
Expected behavior
I expect to enter the case TaskState.error to be able to handle the error there.
Sample project

Additional context
I chose snapshotEvents.listen and not the await option inside the try-catch block because I need the updates on the upload progress.

Flutter doctor
Run flutter doctor and paste the output below:
Click To Expand
PASTE OUTPUT INSIDE HERE

Flutter dependencies
Run flutter pub deps -- --style=compact and paste the output below:
Click To Expand
PASTE OUTPUT INSIDE HERE

Thanks for the report @Vera-uveye
The log you provided is the Java stacktrace coming from native Firebase SDK. It logs errors by default, the plugin code itself for FlutterFire isn't logging/printing these. Also, it seems to be WAI since you can catch the error but it still logs it.

I followed the documentation

This documentation link is now archived and you should be following the link as mentioned in the screenshot.

So checkout this documentation and error handling section in it and see if it helps.

Hi,
The documentation is the same like the archived one. I cannot catch the
errors on the plugin. See what I marked in the attached screenshot. It
never enters that case.
Thanks for your help,
Vera
On Fri, Jan 6, 2023, 12:18 darshankawar @.***> wrote:

Thanks for the report @Vera-uveye https://github.com/Vera-uveye
The log you provided is the Java stacktrace coming from native Firebase
SDK. It logs errors by default, the plugin code itself for FlutterFire
isn't logging/printing these. Also, it seems to be WAI since you can catch
the error but it still logs it.
I followed the documentation
https://firebase.flutter.dev/docs/storage/upload-files/#full-example
This documentation link is now archived and you should be following the
link as mentioned in the screenshot.
[image: Screenshot 2023-01-06 at 3 38 39 PM]
https://user-images.githubusercontent.com/67046386/210982128-2997dd96-9645-4886-a9af-f1198fbe5f5d.png
So checkout this
https://firebase.google.com/docs/storage/flutter/upload-files
documentation and error handling section
https://firebase.google.com/docs/storage/flutter/upload-files#error_handling
in it and see if it helps.
—
Reply to this email directly, view it on GitHub
https://github.com/firebase/flutterfire/issues/10222#issuecomment-1373436363,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AY32FQIOJ3FEHIOWJDYN3FTWQ7WOTANCNFSM6AAAAAATSEHPLQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

Thanks for the update. I am unable to replicate this issue using the plugin example, so can you try the same and see if using it, you still get same error or not ? If not, and the error is triggering from your own code, we would need a minimal code sample along with exact steps to replicate.

Solved it by adding the .onError to handle these kinds of errors. The plugin apparently isn't catching/handling those.
Think if you want to add them, it would be nice!
Thanks.

Good to know you resolved the issue. Closing based on above comment.


Enable Style/OpenStructUse cop

[x] Have you followed the guidelines in our Contributing document?
[ ] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.

[x] Have you successfully run brew typecheck with your changes locally?
[ ] Have you successfully run brew tests with your changes locally?

I would like us to enable the Style/OpenStructUse cop. The official RuboCop docs cite "performance, version compatibility, and potential security issues", but an add'l issue in this repo is that it breaks typechecking.

Review period will end on 2023-02-28 at 16:58:22 UTC.

I looked a little bit into this a while ago and using it in cli/args didn't seem to be a significant performance issue. Still might be nice to remove it at some point but it'd be a major refactor.

I wouldn't be worried too much about CLI args too much as that's always going to be an auto-gen job when it comes to typing.

Review period ended.

@apainintheneck @MikeMcQuaid PTAL: I refactored away all but three uses, one in a rescue statement that I couldn't figure out how to hit, and two others that inherit from OpenStruct cops. (I didn't inline the rubocop:disable bc the accompanying comments show up in the public documentation). I don't have a plan to migrate cli/args or tab in the foreseeable future, but still feel this change is a net improvement. LMK what you think.


Grammatical updates in custom cleanup approach

Couple of small changes to make this section read better.

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

Verified the editorial updates.
@donaldgray - Thank you for submitting the pull request.


ANativeActivity_onCreate not found

After installing the master branch cargo-apk, and running cargo-apk build --release on examples\basic and succesfully installing the apk built with cargo-apk install I got the following error while running adb logcat:
08-31 17:03:21.909  1565  2982 I ActivityManager: Start proc 26269:rust.example/u0a554 for activity rust.example/android.app.NativeActivity
08-31 17:03:21.972  2718  3521 D OpenGLRenderer: endAllActiveAnimators on 0x7d0dd700 (RippleDrawable) with handle 0x854337e0
08-31 17:03:21.974 26269 26269 W System  : ClassLoader referenced unknown path:
08-31 17:03:21.987   817   904 I SFPerfTracer:      triggers: (rate: 0:2) (139306 sw vsyncs) (0 skipped) (3:866946 vsyncs) (5:1075669)
08-31 17:03:22.059 26269 26269 W NativeActivity: ANativeActivity_onCreate not found
08-31 17:03:22.060 26269 26269 D AndroidRuntime: Shutting down VM
08-31 17:03:22.060 26269 26269 E AndroidRuntime: FATAL EXCEPTION: main
08-31 17:03:22.060 26269 26269 E AndroidRuntime: Process: rust.example, PID: 26269
08-31 17:03:22.060 26269 26269 E AndroidRuntime: java.lang.UnsatisfiedLinkError: Unable to load native library "/data/app/rust.example-KW3icy8gwyxnx_5Bv9gl4w==/lib/arm/libexample.so": undefined symbol: ANativeActivity_onCreate
08-31 17:03:22.060 26269 26269 E AndroidRuntime:        at android.app.NativeActivity.onCreate(NativeActivity.java:174)
08-31 17:03:22.060 26269 26269 E AndroidRuntime:        at android.app.Activity.performCreate(Activity.java:7032)
08-31 17:03:22.060 26269 26269 E AndroidRuntime:        at android.app.Activity.performCreate(Activity.java:7023)
08-31 17:03:22.060 26269 26269 E AndroidRuntime:        at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1236)
08-31 17:03:22.060 26269 26269 E AndroidRuntime:        at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2814)
08-31 17:03:22.060 26269 26269 E AndroidRuntime:        at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2943)
08-31 17:03:22.060 26269 26269 E AndroidRuntime:        at android.app.ActivityThread.-wrap11(Unknown Source:0)
08-31 17:03:22.060 26269 26269 E AndroidRuntime:        at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1630)
08-31 17:03:22.060 26269 26269 E AndroidRuntime:        at android.os.Handler.dispatchMessage(Handler.java:106)
08-31 17:03:22.060 26269 26269 E AndroidRuntime:        at android.os.Looper.loop(Looper.java:164)
08-31 17:03:22.060 26269 26269 E AndroidRuntime:        at android.app.ActivityThread.main(ActivityThread.java:6626)
08-31 17:03:22.060 26269 26269 E AndroidRuntime:        at java.lang.reflect.Method.invoke(Native Method)
08-31 17:03:22.060 26269 26269 E AndroidRuntime:        at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:438)
08-31 17:03:22.060 26269 26269 E AndroidRuntime:        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:811)
08-31 17:03:22.063  1565  2988 W ActivityManager:   Force finishing activity rust.example/android.app.NativeActivity
08-31 17:03:22.065  1565 26283 W DropBoxManagerService: Dropping: data_app_crash (1271 > 0 bytes)
08-31 17:03:22.069  1565  1648 I ActivityManager: Showing crash dialog for package rust.example u0

Look similar to #234. What NDK and SDK are you using?

This log is almost identical to mine in #234
08-31 18:23:06.465  1165  1208 I ActivityManager: Start proc 23557:rust.doze_widget/u0a266 for activity rust.doze_widget/android.app.NativeActivity
08-31 18:23:06.471 23557 23557 I ust.doze_widge: Late-enabling -Xcheck:jni
08-31 18:23:06.531 23557 23557 W System  : ClassLoader referenced unknown path:
08-31 18:23:06.553 23557 23574 D libEGL  : loaded /vendor/lib64/egl/libEGL_adreno.so
08-31 18:23:06.558 23557 23574 E libc    : Access denied finding property "vendor.debug.egl.profiler"
08-31 18:23:06.557 23557 23557 W rust.doze_widget: type=1400 audit(0.0:30796): avc: denied { read } for comm=45474C20496E6974 name="u:object_r:vendor_default_prop:s0" dev="tmpfs" ino=16625 scontext=u:r:untrusted_app:s0:c10,c257,c512,c768 tcontext=u:object_r:vendor_default_prop:s0 tclass=file permissive=0
08-31 18:23:06.560 23557 23574 D libEGL  : loaded /vendor/lib64/egl/libGLESv1_CM_adreno.so
08-31 18:23:06.573 23557 23574 D libEGL  : loaded /vendor/lib64/egl/libGLESv2_adreno.so
08-31 18:23:06.582 23557 23557 D OpenGLRenderer: Skia GL Pipeline
08-31 18:23:06.601 23557 23557 W NativeActivity: ANativeActivity_onCreate not found: undefined symbol: ANativeActivity_onCreate
08-31 18:23:06.601 23557 23557 D AndroidRuntime: Shutting down VM
08-31 18:23:06.603 23557 23557 E AndroidRuntime: FATAL EXCEPTION: main
08-31 18:23:06.603 23557 23557 E AndroidRuntime: Process: rust.doze_widget, PID: 23557
08-31 18:23:06.603 23557 23557 E AndroidRuntime: java.lang.UnsatisfiedLinkError: Unable to load native library "/data/app/rust.doze_widget-pGY_l-aNRaPr827BW82_MA==/lib/arm64/libdoze_widget.so": undefined symbol: ANativeActivity_onCreate
08-31 18:23:06.603 23557 23557 E AndroidRuntime:        at android.app.NativeActivity.onCreate(NativeActivity.java:175)
08-31 18:23:06.603 23557 23557 E AndroidRuntime:        at android.app.Activity.performCreate(Activity.java:7144)
08-31 18:23:06.603 23557 23557 E AndroidRuntime:        at android.app.Activity.performCreate(Activity.java:7135)
08-31 18:23:06.603 23557 23557 E AndroidRuntime:        at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1271)
08-31 18:23:06.603 23557 23557 E AndroidRuntime:        at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2931)
08-31 18:23:06.603 23557 23557 E AndroidRuntime:        at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3086)
08-31 18:23:06.603 23557 23557 E AndroidRuntime:        at android.app.servertransaction.LaunchActivityItem.execute(LaunchActivityItem.java:78)
08-31 18:23:06.603 23557 23557 E AndroidRuntime:        at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:108)
08-31 18:23:06.603 23557 23557 E AndroidRuntime:        at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:68)
08-31 18:23:06.603 23557 23557 E AndroidRuntime:        at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1816)
08-31 18:23:06.603 23557 23557 E AndroidRuntime:        at android.os.Handler.dispatchMessage(Handler.java:106)
08-31 18:23:06.603 23557 23557 E AndroidRuntime:        at android.os.Looper.loop(Looper.java:193)
08-31 18:23:06.603 23557 23557 E AndroidRuntime:        at android.app.ActivityThread.main(ActivityThread.java:6718)
08-31 18:23:06.603 23557 23557 E AndroidRuntime:        at java.lang.reflect.Method.invoke(Native Method)
08-31 18:23:06.603 23557 23557 E AndroidRuntime:        at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)
08-31 18:23:06.603 23557 23557 E AndroidRuntime:        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:858)
08-31 18:23:06.607  1165  3529 W ActivityManager:   Force finishing activity rust.doze_widget/android.app.NativeActivity
08-31 18:23:06.609 23557 23557 I Process : Sending signal. PID: 23557 SIG: 9
08-31 18:23:06.610  1165  1206 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.stats.service.DropBoxEntryAddedReceiver
08-31 18:23:06.610  1165  1206 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.chimera.GmsIntentOperationService$PersistentTrustedReceiver
08-31 18:23:06.611   849   849 E lowmemorykiller: Error writing /proc/23557/oom_score_adj; errno=22
08-31 18:23:06.616   705   705 I Zygote  : Process 23557 exited due to signal (9)
08-31 18:23:06.622  1165  9145 I ActivityManager: Process rust.doze_widget (pid 23557) has died: vis  +99TOP

@philip-alldredge I don't know how I would check that, I'm using the latest from Android Studio.
It seems to be a known issue, look at #228:

Thanks to #232, I moved the native_app_glue into the android_glue crate with a simple build.rs that uses the cc crate. However, I'm currently figuring out issues whtere the native_app_glue's ANativeActivity_onCreate doesn't get included in the final library.

Maybe @mb64 could describe better what's happening.

@derezzedex  that hasn't been merged yet so I didn't expect that to be a problem. You are using the master branch, correct? That does seem like the issue though @mb64

@derezzedex Please try a debug build and let me know if you have the same issue.

@philip-alldredge Tried, same error.

What version of rust are you using. I was able to reproduce the issue with 1.37.0.

@philip-alldredge Sorry for the late answer, but this is it:
rustc --version
rustc 1.37.0 (eae3437df 2019-08-13)

cargo --version
cargo 1.37.0 (9edd08916 2019-08-02)

sdkmanager --list
  Path                                                | Version      | Description                                     | Location
  -------                                             | -------      | -------                                         | -------
  build-tools;29.0.0                                  | 29.0.0       | Android SDK Build-Tools 29                      | build-tools\29.0.0\
  build-tools;29.0.2                                  | 29.0.2       | Android SDK Build-Tools 29.0.2                  | build-tools\29.0.2\
  cmake;<IP_ADDRESS>88404                                | 3.10.2       | CMake <IP_ADDRESS>88404                            | cmake\<IP_ADDRESS>88404\
  emulator                                            | 29.0.11      | Android Emulator                                | emulator\
  extras;intel;Hardware_Accelerated_Execution_Manager | 7.5.2        | Intel x86 Emulator Accelerator (HAXM installer) | extras\intel\Hardware_Accelerated_Execution_Manager\
  lldb;3.1                                            | 3.1.4508709  | LLDB 3.1                                        | lldb\3.1\
  ndk;20.0.5594570                                    | 20.0.5594570 | NDK (Side by side) 20.0.5594570                 | ndk\20.0.5594570\
  patcher;v4                                          | 1            | SDK Patch Applier v4                            | patcher\v4\
  platform-tools                                      | 29.0.2       | Android SDK Platform-Tools                      | platform-tools\
  platforms;android-29                                | 3            | Android SDK Platform 29                         | platforms\android-29\
  system-images;android-28;google_apis_playstore;x86  | 8            | Google Play Intel x86 Atom System Image         | system-images\android-28\google_apis_playstore\x86\
  system-images;android-29;google_apis;x86            | 7            | Google APIs Intel x86 Atom System Image         | system-images\android-29\google_apis\x86\
  system-images;android-29;google_apis_playstore;x86  | 7            | Google Play Intel x86 Atom System Image         | system-images\android-29\google_apis_playstore\x86\
  tools                                               | 26.1.1       | Android SDK Tools                               | tools\

I believe we've found the issue. It is an incompatibility with rust 1.37.0. I have opened a pull request that has a fix. I'm unsure if that is the final fix or if the maintainer will have a better solution. In the meantime, you can use the branch referenced in #237.
Thanks for reporting this. Otherwise, we may not have realized that there was an issue to be fixed and that it was widespread.

This is exactly the "linker issues" I was investigating in #228 ; I though it was caused by that PR, but apparently not!
So what's happening here is that rustc provides the linker with a "version script" (which is oddly named – it has nothing to do with versioning and everything to do with exporting symbols) that looks something like:
libwhatever {
  global:
    // All the extern "C" functions
    android_main;
    rust_eh_personality;
    // If it's a cdylib, this is where it ends. If it's a dylib, it goes on to list all the mangled rust symbols:
    _Z...

  local:
    *; // All the other symbols are local, and get stripped by --strip-all
}

The solution in #237 (rename the native_app_glue version and call it from an extern "C" Rust wrapper) makes the most sense to me – there seems to be no way to change the impact of the version script by adding more linker args afterwards.  Ideally we could have our own version script that only exports ANativeActivity_onCreate, but there's no (good) way to do that.

Fixed by #237.  However, this is a very testable problem, so I'd like to see CircleCI making sure the symbol exists.  I'll work on that, and in the meantime keep this issue open.


Added socket send and recv timeout options

Added socket send and recv timeout options with implementation for posix platform
This is part of a extending support for sockets in WASI. https://github.com/bytecodealliance/wasm-micro-runtime/issues/1336
I've also added a WIP sample that sets and reads back the send and receive timeouts using the native function binding, however I still need to add the posix-like shim.

@loganek do you have any comments?


Hi, I just wonder how am I supposed to use bootstrap in gulp-front?

Do I need to change from Stylus to Sass? Sorry if the question is silly, I'm very new to this.

Hi. For Sass support you need add task for compile sass files.
Some time ago another developer was already asking about this.
#52 Question: Stylus to Sass

Thanks for replying. I saw the question but the solution wasn't what I looked for. I don't want to lose the CSS framework gulp-front has, and I has taken a liking to Stylus, I want to keep using it instead of replacing with Sass.  So I wonder if I can add tasks for compiling sass files but keep using Stylus at the same time?

Yes of course. You can use a stylus and sass files at the same time.

Add new task for sass compilation
Add your task to the build task
Add new gulp.watch to the watch task

ps. If you want using bootstrap it could be complicated on same page, because both gulp-front and bootstrap has same class names.
e.g. .button, .table or global styles for h1-6, p etc.


The “Backspace” button is absent on the digit keyboard after entering the data in the “HOW MUCH” field

Description
The “Backspace” button is absent on the digit keyboard after entering the data in the “HOW MUCH” field
Preconditions:

The user is logged in
The “Receive” page is opened with “HOW MUCH” text

Steps to reproduce:

Click the “1” on the digit keyboard
Pay attention to the digit keyboard

Actual result: The “Backspace” button is absent on the digit keyboard after entering the data in the “HOW MUCH” field
Expected result: The “Backspace” button is displayed on the digit keyboard after entering the data in the “HOW MUCH” field
Supporting data
Env https://goodqa.netlify.com
iPhone6 12.3.1, Safari
https://www.screencast.com/t/dCHDgexJ

@dariominones this should be solve by the flex layout we discussed with max-height so it doesnt look strange on large devices

Solved in this PR will close when merged

Checked on https://goodqa.netlify.com/
iPhone6 12.3.1, Safari
Fixed
https://www.screencast.com/t/8Y8sclJL


Can you update more facebook follow badges

You can update the facebook follow display feature on the shields, because I see that there are currently no facebook badges, and I think it is really necessary and useful. Thank you for making such a great utility.

hello @QuangNguyen1607 :wave: Thank you for reaching out, but I think this is a duplicate of #2120 and unlikely to go anywhere unless things have changed on the Facebook/Instagram end.
As an aside, we've structured our issue templates with a specific set of questions so that there's sufficient information to facilitate a more productive dialog. I imagine we'll need to close this just like the other prior Facebook requests, but on the off chance it is possible to proceed then we'd need you to provide responses to the questions that were posed in the issue template.
@PyvesB - I believe you were the most closely involved with the previous Facebook badge requests, what are your thoughts on this one?

I think the issues with the rate limits on the instagram/facebook APIs are still the same now as they were then.
If you just want follow buttons you can do  something like this with the static badges though

 https://img.shields.io/badge/follow--000?style=social&logo=facebook
 https://img.shields.io/badge/follow--000?style=social&logo=instagram


Loss of data when loading AnnData object with duplicated .obs column names from .h5ad

The following snippet demonstrates the issue:
import anndata as ad
import scanpy as sc
import numpy as np
import pandas as pd

adata = ad.AnnData(X=np.ones((2, 2)), dtype=np.float64)
adata.obs = pd.DataFrame(
    data=np.random.normal(size=(2, 2)),
    columns=['a', 'a'],
    index=['1', '2'],
)

adata.write_h5ad('test.h5ad')
adata_load = sc.read_h5ad('test.h5ad')

Then adata.obs will be something like
	        a	       a
1	-0.615750	0.524092
2	-0.004393	0.542863

while adata_load.obs looks like
  a a
1 a a
2 a a

Having an AnnData object with duplicated .obs column names is clearly an edge case, so perhaps the easiest fix is just to have write_h5ad() to throw an error when this happens?
Version information, in case it's relevant:
>>> (ad.__version__, sc.__version__, np.__version__, pd.__version__)
('0.8.0', '1.9.1', '1.23.5', '1.5.3')

Thanks for the report! I've also just run into this while writing up the specifications.
Would you be up for making a PR to add this error? The change would need to happen here:
https://github.com/scverse/anndata/blob/50b1b105ef32fd8bca91194b5fd07d250d18b4bf/anndata/_io/specs/methods.py#L502-L527
And would just include checking that the column names are unique.
I think it may be okay to have the index share a name with a column, but only if the values are the same. This wouldn't necessarily need to be addressed in the PR about unique column names.

Maybe we should just raise an Exception if someone tries to create duplicate column names?
I’d think that having multiple columns with the same name is a case for obsm


[PowerToys Run] Does not use default search engine in Vivaldi

Description of the new feature / enhancement
Currently the extension opens in my default browser (Vivaldi), but not my search engine (DDG).
Scenario when this would be used?
This would be used by people who can no longer use edge deflector and also use Vivaldi as their browser
Supporting information
I tried using PT Run with Firefox developer edition and it picked up my default search engine perfectly. Using Vivaldi opened Google even though both private and regular windows are set to use DDG. This may be an issue with Vivaldi and not PowerToys itself. I am running Vivaldi version 5.0.2497.35 and PowerToys 0.53.1. One solution would be to add an option to select the search engine directly.
Query URLs for various search engines:
DuckDuckGo - https://duckduckgo.com/?q=
Startpage - https://www.startpage.com/do/search?q=
Neeva - https://neeva.com/search?q=
Bing  - https://www.bing.com/search?q=
Ecosia - https://www.ecosia.org/search?q=
Kagi - https://kagi.com/search?q=

This issue shows up in v0.53.3 of PowerToys and I put a bug report in Vivaldi browser subreddit with my experience with the bug.

if you do vivaldi.exe "? foo" in the Win+R run prompt, does that pull up duck duck go?
msedge "? foo" does.  This is basiclaly the format we're using

Vivaldi defaults to google
Msedge defaults to bing
On Thu, Feb 24, 2022 at 4:59 PM Clint Rutkas @.***>
wrote:

if you do vivaldi.exe "? foo" in the Win+R run prompt, does that pull up
duck duck go?
msedge "? foo" does. This is basiclaly the format we're using
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/PowerToys/issues/15342#issuecomment-1050306113,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJJ24M3UN6OLQA5RQLZXMHLU42S4NANCNFSM5LQCSG2A
.
You are receiving this because you commented.Message ID:
@.***>

--
Abhimaan Mayadam

it should query whatever you set as your default engine.

I changed edge's to google and it pulls up google now for querying.

/needinfo

So it appears that Vivaldi doesn’t do the default search properly then. As I was in the middle of commenting the same thing. Setting my default search engine to Google pulls up Google.  Sent from Mail for Windows From: Clint RutkasSent: Thursday, February 24, 2022 5:05 PMTo: microsoft/PowerToysCc: AbhiMayadam; CommentSubject: Re: [microsoft/PowerToys] [PowerToys Run] Does not use default search engine in Vivaldi (Issue #15342) I changed edge's to google and it pulls up google now for querying.—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID<EMAIL_ADDRESS>
Tested again with:
Vivaldi 5.1.2567.49
PowerToys version 0.55.2
Result:
The default search engine is correctly selected.
PowerToys matched the behavior of Win-R vivaldi.exe "? foo"


testSpecName in Instrumentation tests

Hello,
I would like to know how can I use testSpecName in Instrumentation tests as declared in README.
With the version 1.3 of the plugin it doesn't seem to recognize it.
Regards,
Maciej Górski

Hi:
Can you provide a run URL where you are experiencing this issue? Additionally, can you provide the configuration you are utilizing in your gradle build? This is usually app/build.gradle.
Andy

Same issue. v1.3 did not have that feature yet.... Can someone release v1.4?

We're having the issue at https://forums.aws.amazon.com/thread.jspa?messageID=917263 where the solution is to run a custom test spec. But as mentioned here, that feature has not been released yet.
So for us, aws-device-farm-gradle-plugin is completely broken with or without testSpecName. The Minimal configuration at https://github.com/awslabs/aws-device-farm-gradle-plugin#minimal-configuration doesn't work.


Update to debian:10.2 base

See https://github.com/Senzing/docker-senzing-base/issues/42

Pull Requests

https://github.com/Senzing/docker-compose-demo/pull/59


Update the Import module to actually download the raw files from AWS

I'd like to take this issue. Boto3 looks straightforward, but I'll need credentials for an S3 user with "programmatic access".

Like this:
$ pip install boto3
import boto3
from pathlib import Path

BUCKET_NAME = "nc-campaign-finance-storage"
LOCAL_DIR = Path.cwd() / 'data'

s3_resource = boto3.resource('s3')
bucket = s3_resource.Bucket(BUCKET_NAME)
for obj in bucket.objects.all():
    s3_file = obj.Object()
    local_file = LOCAL_DIR / s3_file.key
    if local_file.exists():
        if local_file.stat().st_size == s3_file.content_length:
            print(f'{s3_file.key} already downloaded')
            continue
    local_file.parent.mkdir(parents=True, exist_ok=True)
    s3_file.download_file(str(local_file))
    print(f'{s3_file.key}')

print("Done")

The change needs to be dynamic to download any and all files not already located in the docker image(a static list of files is not sufficient) and should require elevated privileges requiring AWS secrets.


purging system ruby breaks layer-tls

Purging system ruby causes breakage in other layers -> http://paste.ubuntu.com/23091486/
To reproduce: juju deploy cs:~jamesbeedy/tls-test-0
Can we not purge system ruby?

not purging system ruby get me further, but not much -> http://paste.ubuntu.com/23091521/
To reproduce: juju deploy cs:~jamesbeedy/tls-test-1


Support iCloud Library photos.

ChattoAdditions supports iCloud stored photos now.
Whenever someone wants to send a photo from iCloud it would be downloaded with a circular progress indicator applied to a requested photo's cell.

Codecov Report

Merging #415 into master will decrease coverage by 0.63%.
The diff coverage is 22.02%.

@@            Coverage Diff             @@
##           master     #415      +/-   ##
==========================================
- Coverage   64.74%   64.11%   -0.64%
==========================================
  Files          70       74       +4
  Lines        4575     4720     +145
  Branches      234      238       +4
==========================================
+ Hits         2962     3026      +64
- Misses       1595     1676      +81
  Partials       18       18

Impacted Files
Coverage Δ

...ns/Source/Input/Photos/Camera/LiveCameraCell.swift
85.91% <ø> (ø)

.../Input/Photos/Camera/LiveCameraCellPresenter.swift
78.29% <ø> (ø)

...hotos/Placeholder/PhotosInputPlaceholderCell.swift
0% <ø> (ø)

.../Input/Photos/Camera/PhotosInputCameraPicker.swift
0% <ø> (ø)

...Input/Photos/Camera/LiveCameraCaptureSession.swift
0% <ø> (ø)

...at Items/PhotoMessages/Views/PhotoBubbleView.swift
75.33% <0%> (+0.49%)
:arrow_up:

...dditions/Source/Input/Photos/PhotosInputView.swift
1.65% <0%> (-0.02%)
:arrow_down:

...aceholder/PhotosInputPlaceholderCellProvider.swift
0% <0%> (ø)

...e/Input/Photos/Photo/PhotosInputDataProvider.swift
0% <0%> (ø)

...rogressIndicatorView/CircleProgressIndicatorView.m
45.39% <13.79%> (-1.86%)
:arrow_down:

... and 11 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 1d3b591...69f4508. Read the comment docs.


add --semantic flag

Like --final, --semantic compensates for differing platform conventions
regarding termination of the last line in a file. In contrast,
--semantic aims to preserve logical lines across representations.
This assumes windows conventions use CRLF as line separators, not terminators.
An equivalent formulation: lines are terminated by exactly one of CRLF or EOF.
Yet another: CRLF always starts a new line, even at file end.
The goal is to cope with the unterminated-line problem in a way that
allows lossless round-trips. In concept, git smudge and clean filters are
intended to be the inverse of one another, making changes that are fully
reversible. Adding a trailing blank line to a windows file is normally
inoffensive, but can be a nuisance in the presence of change-tracking.

Hello @perennialmind. Thanks a lot for your work, this is an interesting idea ! To be honest, I didn't even have the notion of Window's last char not being an EOL, vs Linux's well known convention.
I'll merge the pull request. But if you'll allow, I'll take some time to review it with a cold head. I've got a newborn child at home and, besides office time, moments for full concentration are far and short for now. Allow a few days.
With my best regards.

Hello @mdolidon. Wow - congratulations! And, obviously you have more important things to which to attend. I just wanted to share back the bits that were useful to me.
As you say, the unix conventions are explicit and set in stone, baked into C and POSIX. I think that the windows conventions are much looser. I take Notepad and Visual Studio to be authoritative, but as far as I can tell, the pattern extends to Windows-native plaintext editors in general. I've seen it attributed to a historical disregard for trailing whitespace, going back to the infinite-character-grid model of some early DOS editors.
Anyway, thanks for giving it a look. I won't be offended if it turns out not to be something you want to merge. Most folks seem to want exactly the approach you already had. EditorConfig even codified the practice with insert_final_newline, and they seem to have pretty solid uptake.
Let me know if there's anything you'd like changed. The option name, at least, could probably be improved.
P.S.

Hello perennialmind.
After lots and lots of changes and events in private and professional life over six months, I'm finally slowly coming back to Github.
I've been looking a little bit into this. It seems that the presence or absence of a final EOL in Windows is not really something that anybody really knows about, and therefore would want to enforce. As such, ,I have the feeling that this would eventually be a rather obscure option. I'd like to keep this software very simple and immediately understandable. That was part of the reason why I wrote it. :)
Therefore I think that I will not follow up on the pull request. However, I'd like to thank you for taking the time to share what you adapted !
Mathias


how to use with custom utilities? such as for gradients

Hi there, wondering if you could assist in helping me understand how to add gradients to themes
Right now I have a custom gradients plugin:
const map = require('lodash/map');
const isPlainObject = require('lodash/isPlainObject');

const plugin = require('tailwindcss/plugin');

module.exports = plugin(({
  addUtilities, e, theme, variants,
}) => {
  const utilities = map(theme('gradients', {}), (gradient, name) => {
    const type = isPlainObject(gradient) && gradient.hasOwnProperty('type') ? gradient.type : 'linear';
    const colors = isPlainObject(gradient) ? gradient.colors || [] : gradient;

    return {
      [`.bg-gradient-${e(name)}`]: {
        background: `${type}-gradient(${colors.join(', ')})`,
      },
    };
  });

  addUtilities(utilities, variants('gradients', []));
});

and I define gradients like this in my tailwind.config.js:
module.exports = {
  theme: {
    gradients: {
      navbar: { type: 'linear', colors: ['90deg', '#98a8fb 0', '#71b3f8 100%'] },
    },
  },
  variants: {
    gradients: ['responsive', 'hover'],
  },
  plugins: [
    require('./tailwind-plugins/gradients.js'),
    require('./theme.config.js'),
  ],
};

How can I move this logic to your theme.config.js so that the gradients are associated with a theme, so I could have a different gradient applied when I switch from light to dark for example?
Many thanks!

Hey, you can use the .variable method from the Theme object.
Here's how you could do it, you can improve the code, I wrote it quickly for the example's sake:
// theme.config.js
const { ThemeBuilder, Theme } = require('tailwindcss-theming');

const defaultTailwindColors = new Theme()
  .name('light')
  .default()
  .assignable()
  .colors({
    'blue-100': '#ebf8ff',
    // ...
  })

  // This line adds the second parameter with the name `navbar` to the `gradient` key of Tailwind's theme, so it's accessible to plugins and can be used to generate utilities.
  .variable('navbar', 'linear-gradient(90deg, #98a8fb 0, #71b3f8 100%)', 'gradient')
;

module.exports = new ThemeBuilder()
  .asDataThemeAttribute()
  .default(defaultTailwindColors);

This adds this CSS variable:
:root {
  --gradients-navbar: linear-gradient(90deg, #98a8fb 0, #71b3f8 100%);
}

Then, in your Tailwind config:
// tailwind.config.js
const plugin = require('tailwindcss/plugin');
const map = require('lodash/map');

module.exports = {
  theme: {},
  variants: {
    gradients: ['responsive', 'hover'],
  },
  plugins: [
    require('./theme.config.js'),

	// Custom plugin
    plugin(({ addUtilities, e, theme, variants }) => {

	  // The
      const utilities = map(theme('gradients', {}), (value, name) => {
        return {
          [`.bg-gradient-${e(name)}`]: {
            background: value, // value here is equal to `var(--gradients-navbar)`
          },
        };
      });

      addUtilities(utilities, variants('gradients', []));
    }),
  ],
};

Pay attention to the plugins' order. This is important, since the theme plugin overwrites the configuration, and your custom plugin relies on it.

For further assistance, please come to the Tailwind Discord in the #plugins channel instead of creating issues, I'll respond faster and it will be more convenient.
Hope I helped!


Make cycle numbers optional in ui

Some users wants a clean UI and don't want cyclenumber to show up on all days. It's to messy.
Create a new setting and add a check to this setting in the current If-statement.
Setting should have value 0/1 in database and then maybe a switch in the UI?
When creating a new setting, remember to increase db version and take care of oncreate/on upgrade.
Should we create a new setting group or put this as other?

Fixed in db-version 7


Android test is broken due to Conscrypt socket support

A merge conflict with the AndroidQPlatform and ConscryptTest.  I'll work on the correct fix tomorrow.  I didn't think about what would happen if conscrypt is enabled since AndroidQPlatform is mostly the JDK9 platform code.

Also double import of Platform

okhttp.android.test.OkHttpTest > testConscryptRequest[New_Device_API_29(AVD) - 10] FAILED
	java.lang.AssertionError: expected:<h2> but was:<http/1.1>
	at org.junit.Assert.fail(Assert.java:88)
11:26:07 V/InstrumentationResultParser: INSTRUMENTATION_STATUS_CODE: -2
11:26:07 V/InstrumentationResultParser: INSTRUMENTATION_RESULT: stream=
11:26:07 V/InstrumentationResultParser:
11:26:07 V/InstrumentationResultParser: Time: 13.001
11:26:07 V/InstrumentationResultParser: There was 1 failure:
11:26:07 V/InstrumentationResultParser: 1) testConscryptRequest(okhttp.android.test.OkHttpTest)
11:26:07 V/InstrumentationResultParser: java.lang.AssertionError: expected:<h2> but was:<http/1.1>
11:26:07 V/InstrumentationResultParser: at org.junit.Assert.fail(Assert.java:88)
11:26:07 V/InstrumentationResultParser: at org.junit.Assert.failNotEquals(Assert.java:834)
11:26:07 V/InstrumentationResultParser: at org.junit.Assert.assertEquals(Assert.java:118)
11:26:07 V/InstrumentationResultParser: at org.junit.Assert.assertEquals(Assert.java:144)
11:26:07 V/InstrumentationResultParser: at okhttp.android.test.OkHttpTest.testConscryptRequest(OkHttpTest.kt:128)

Fixed on this PR https://github.com/square/okhttp/pull/5483


feat(compiler): allow HTML comments in template interpolation syntax

feat(compiler): Add support for parsing comments in template syntax
This commit introduces a new feature to the compiler that allows for parsing comments in the template syntax. Comments can now be written using the syntax , which will be treated as comments and not affect the parsing process.
To ensure the functionality of this feature, two new test cases have been added:
Test case: Parsing template with a comment
Description: This test verifies that the compiler can successfully parse a template that contains a comment.
Steps:
Create a template with a comment using the  syntax.
Invoke the compiler to parse the template.
Expected result: The compiler should parse the template without any errors and treat the comment as a comment, not affecting the parsing of other elements.
Test case: Parsing templates with comments and valid content
Description: Verify that the compiler can successfully parse templates that contain both comments and valid content, and correctly handle the comment sections.
Steps:
Create a template that includes both comments and valid content, using the  syntax for comments.
Invoke the compiler to parse the template.
Expected result: The compiler should be able to parse the template without errors, treating the valid content as valid and ignoring the comment sections.
In addition to the test cases, relevant method comments have been added to enhance code readability and maintainability.

New features are typically expected to go through an RFC, to allow the community to provide feedback on the proposal. As far as I'm aware there hasn't been an RFC for this feature.
The PR description doesn't really explain the motivation behind the feature, but it seems like #8629 goes into more detail. As noted there, JS /* */ comments already work inside text interpolation, so it's already possible to include comments.
I suspect we'd run into syntax collisions trying to mix HTML comments with JS expressions. For example:
{{ '<!-- I am not a comment -->' }}

Currently Vue will treat that as a string and output the 'comment' as text:

Playground - main

With the changes in this PR, that text is gone:

Playground - this PR

I'm not sure which would be considered correct.

see https://github.com/vuejs/core/issues/8629#issuecomment-1603875593


Install colorize, and fix bug

hmm... colorize must be already required by sshkit.
ok, i'll accept it but please remove sshkit dependency then.


Update firebase auth

Problem:
If someone is using firebase-ui-auth with the latest version of the following firebase libraries:
firebase-firestore
firebase-database
firebase-storage
firebase-function

The following error will occur:

E/AndroidRuntime: FATAL EXCEPTION: main
Process: meter.meter, PID: 13588
java.lang.NoSuchMethodError: No virtual method setTokenProvider(Lcom/google/firebase/internal/InternalTokenProvider;)V in class Lcom/google/firebase/FirebaseApp; or its super classes (declaration of 'com.google.firebase.FirebaseApp' appears in /data/app/meter.meter-Qosf8nECYGfI4HI93CwJrw==/split_lib_dependencies_apk.apk!classes2.dex)
at com.google.firebase.auth.zzp.create(Unknown Source:4)
at com.google.firebase.components.ComponentRuntime.lambda$new$0(com.google.firebase:firebase-common@@17.0.0:66)
at com.google.firebase.components.ComponentRuntime$$Lambda$1.get(Unknown Source:4)
at com.google.firebase.components.Lazy.get(com.google.firebase:firebase-common@@17.0.0:53)
at com.google.firebase.components.ComponentRuntime.initializeEagerComponents(com.google.firebase:firebase-common@@17.0.0:155)
at com.google.firebase.FirebaseApp.initializeAllApis(com.google.firebase:firebase-common@@17.0.0:642)
at com.google.firebase.FirebaseApp.initializeApp(com.google.firebase:firebase-common@@17.0.0:358)
at com.google.firebase.FirebaseApp.initializeApp(com.google.firebase:firebase-common@@17.0.0:321)

Solution:
Update the following in Config.kt to prevent the above issue:
const val auth = "com.google.firebase:firebase-auth:16.0.5"

into this:
const val auth = "com.google.firebase:firebase-auth:17.0.0"

For reference:
Release notes
Also this was asked on stackoverflow:
java.lang.NoSuchMethodError: No virtual method setTokenProvider

Thanks for reporting this!  We'll definitely include this in the next
release.
*From: *Peter<EMAIL_ADDRESS>*Date: *Sun, May 12, 2019, 8:01 AM
*To: *firebase/FirebaseUI-Android
*Cc: *Subscribed
Problem:

If someone is using firebase-ui-auth with the latest version of the
following firebase libraries:
firebase-firestore
firebase-database
firebase-storage
firebase-function
The following error will occur:
E/AndroidRuntime: FATAL EXCEPTION: main
Process: meter.meter, PID: 13588
java.lang.NoSuchMethodError: No virtual method
setTokenProvider(Lcom/google/firebase/internal/InternalTokenProvider;)V in
class Lcom/google/firebase/FirebaseApp; or its super classes (declaration
of 'com.google.firebase.FirebaseApp' appears in
/data/app/meter.meter-Qosf8nECYGfI4HI93CwJrw==/split_lib_dependencies_apk.apk!classes2.dex)
at com.google.firebase.auth.zzp.create(Unknown Source:4)
at
com.google.firebase.components.ComponentRuntime.lambda$new$0(com.google.firebase:firebase-common@
@17.0.0:66)
at com.google.firebase.components.ComponentRuntime$$Lambda$1.get(Unknown
Source:4)
at
com.google.firebase.components.Lazy.get(com.google.firebase:firebase-common@
@17.0.0:53)
at
com.google.firebase.components.ComponentRuntime.initializeEagerComponents(com.google.firebase:firebase-common@
@17.0.0:155)
at
com.google.firebase.FirebaseApp.initializeAllApis(com.google.firebase:firebase-common@
@17.0.0:642)
at
com.google.firebase.FirebaseApp.initializeApp(com.google.firebase:firebase-common@
@17.0.0:358)
at
com.google.firebase.FirebaseApp.initializeApp(com.google.firebase:firebase-common@
@17.0.0:321)
Solution:
Update the following in Config.kt to prevent the above issue:
const val auth = "com.google.firebase:firebase-auth:16.0.5"
into this:
const val auth = "com.google.firebase:firebase-auth:17.0.0"
For reference:
Release notes
https://firebase.google.com/support/release-notes/android#version_1700
Also this was asked on stackoverflow:
java.lang.NoSuchMethodError: No virtual method setTokenProvider
https://stackoverflow.com/questions/56099945/java-lang-nosuchmethoderror-no-virtual-method-settokenprovider
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/firebase/FirebaseUI-Android/issues/1633, or mute the
thread
https://github.com/notifications/unsubscribe-auth/ACATB2TAXANCMJUCKQEC3ZLPVAWNVANCNFSM4HMKRXSA
.

@samtstern Can I work on this?

@MonikaJethani it's probably not that hard.
First you need to update the version, then you need to check if it compatible with other versions and if it will fail on build and then you need to check if the Firebase Auth methods used in this library got deprecated when upgrading to version 17.0.0

@MonikaJethani I appreciate the enthusiasm but I think most of the work here has to do with the release process, we shouldn't need any code changes besides a change to Constants.kt

Closing as duplicate of #1606, fixing this now.

hey same issue with me but not solve by using  const val auth = "com.google.firebase:firebase-auth:17.0.0"
help me please...

It's better if you ask your issue on stackoverflow. Add the list of dependencies (build.gradle) in your question and the error that you are getting.
Also add a link to the Stackoverflow question so I can check it


"Invisible text" fix

Moved from a NWString/NWInt synch to a localized storage synched with net lib.
Fixed a bug that prevented the tool's right click (update) from working
Disabled drawing the background model.

Please note: I haven't had a chance to test with one of the affected users yet. Should probably delay actual merge until we've tested some more.

Thanks! :)


Add .devcontainer to GSD Web

Adds the configuration necessary for VS Code Dev Containers.
Related to #51, should hopefully streamline getting started working on the project.

looks good.


Mention settings in Docker instructions

Fix #59

Coverage remained the same at 100.0% when pulling 75615517f6f300dd5de46d4f278c1bd31402bdd6 on cuducos-docker-instructions into 36fc5f70087e6c9aef3fb8dfe5751f6494f18e29 on master.


WELZ: Watch wordcookiesanswersaz.com

WELZ requests the watch of the watch_keyword wordcookiesanswersaz\.com. See the Metasmoke search here and the Stack Exchange search here.

wordcookiesanswersaz.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Coverage remained the same at 65.779% when pulling 06ad722fca658268a84818c2cfe7608e7deffe2b on auto-blacklist-1518021095.7138035 into de2754f903e287daa078af8b4ae82700899c2aca on master.

!!/approve


Write a guide for Client based development

Client package was removed, this will need a framework that uses client style code


Disable TLS expiration notifications

Is your feature request related to a problem? Please describe.
I'm constantly receiving dozens of emails regarding TLS expiration of my services. I can't renew these certificates manually and most are self-signed and automatically generated/renewed.
Describe the solution you'd like
An option to disable the feature and/or the notification per Check.

From version 1.9.3 onwards you can use the ENV variable SMTP_DISABLE_TLS_EXPIRES_NOTIFICATIONS=true to disable TLS expiration notifications via E-Mail.


Added example usage in README.md

Per #11 (documentation on existing methods), I have included documentation for the following items...

initialization
authorization (and authorization control)
user lookup (w/ ids and usernames)
utility methods (show vs return methods as well as chunker and pause_until)

... and updated the issue accordingly.
I added everything to the README.md per the issue's request however I was wondering if it makes more sense to break this out into separate Wiki Pages? Thoughts?
Also, let me know your thoughts on what I've documented so far. I approached writing everything as if it was for the other lab members so I was trying to be overly clear - not sure if it's too much detail (or maybe I'm still missing something).
Let me know your thoughts.

@mr-devs you are amazing!


topic notification doesnt show after upgrade to new react native fcm version

My previous app used get topic notifications but after upgrading the library versions i just get this below message in the logcat.
MessagingService: Remote message received
My previous library versions (working with this versions)
"react": "16.0.0",
"react-native": "0.51.0",
"react-native-fcm": "^13.3.1",
"react-navigation": "^1.0.0-beta.29",
New library versions(stopped working with this versions)
"react": "16.3.1",
"react-native": "0.55.3",
"react-native-fcm": "14.1.3",
"react-navigation": "^1.5.11",
I using nexus 6 and oneplus 5 mobiles to test. I tried in both forground and background, just receiving the message MessagingService: Remote message received in log cat but no notifications are shown. I am sending topic notifications.
This is my backend java code using to send the message
// topic either article, message etc...
Message.Builder builder = Message.builder()
.putData("type", topic)
.putData("id", id)
.putData("title", title)
.setApnsConfig(ApnsConfig.builder()
.setAps(Aps.builder()
.setBadge(42)
.build())
.build())
.setAndroidConfig(AndroidConfig.builder()
.setTtl(606024*10) // 10 days
.setPriority(AndroidConfig.Priority.HIGH)
.build())
.setTopic(topic);
if(StringUtils.isNotBlank(body)){
builder.putData("body", body);
}
if(StringUtils.isNotBlank(image)) {
builder.putData("image", image);
}
Message message = builder.build();
String response = FirebaseMessaging.getInstance().sendAsync(message).get();

this is nothing to do with the version, fcm message wasnt working because of body is required. and my message wasnt sending a body. so notification didnt show up.


Add priority to task during task creation

I find myself frequently creating tasks that I know I'd like to give a priority of 2 or 3. However, the way this is done now is two steps:
tb -t 'My created task'
tb -p @<task_id> 2

It'd be great if we could have an option on the --task option to do one of the following:
tb -t -p=2 'My created task'
tb -t -p 2 'My created task'
tb -t 'My created task' -p 2

You can do it with this syntax (example from documentation):
$ tb -t @coding "Fix issue #42" p:3
Note p:3 at the end.

More on how to define a priority level on task initialization; flight-manual#set-priority.


add OpenConnect GUI v1.5.3

Checklist for Pull Requests

[X] Have you signed the Contributor License Agreement?
[ ] Is there a linked Issue?

Manifests

[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?

[ ] Does your manifest conform to the 1.6 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Automatic Validation ended with:
(Automated response - build 880.)

This application is another case that requires support for installing drivers.

Once the install can complete without user interactivity the package may be added to the community repository.


#34906 Set affinity to text for sqlite, if column data type is unknown

Full text search should work now.

verified


azureFunctions.pickProcess only works if preLaunchTask is the last task in tasks.json

Does this occur consistently? Yes
Repro steps:

Check out https://github.com/bijeebuss/vscode-azurefunctions-bug
Launch the Config1 debug config (it fails)
Launch Config2 (it works)
Switch the order of task1 and task2 in tasks.json and now its the other way around

Action: azureFunctions.pickProcess
Error type: Error
Error Message: Failed to find "task1" task.
Version: 0.23.0
OS: win32
OS Release: 10.0.18363
Product: Visual Studio Code
Product Version: 1.48.0
Language: en

Call Stack
extension.bundle.js:334:122218extension.bundle.js:334:122218
fulfilled extension.bundle.js:334:121117
processTicksAndRejections task_queues.js:85:5

I am open to suggestions if there is a better way to have multiple debug configurations with different env variables

Well it's a bit of a hack, but if you change one of "command": "host start" to "command": "start" - it should make both tasks work. I guess VS Code thinks they're the same task if "command" is the same and using "start" instead tricks VS Code into thinking they're different. We're just lucky "host start" and "start" both exist and both do the same thing

After doing some testing I don't think the extension supports debugging multiple function apps at once either way, so I'm going a different route with this.

We do support debugging multiple function apps at once. See this doc: https://github.com/microsoft/vscode-azurefunctions/wiki/Multiple-function-projects

oh good to know. Although I have been having issues with multi root workspaces as well. I think it is related to this
https://github.com/OmniSharp/omnisharp-vscode/issues/3988

In my case I don't think that would help anyway since I wanted to start two instances of the same function app project with different env variables

@bijeebuss yeah haven't really thought of that scenario. Sounds like you might be "going a different route" anyways? If so, we'll probably close this issue.

I decided to just combine my function apps into one project and I will deploy it to different function app instances with different configurations. I still think this is a bug but you can close if you want since I wont be needing a fix

Looked into it and added a comment to this VS Code bug: https://github.com/microsoft/vscode/issues/94381#issuecomment-681187182


Responding to StarScream connection error codes

I am using version 3.1.1 and we are trying to respond to connection error codes. I see in an example we cast an error as WSError so that we can respond based on a code but from testing I can see that we dont get back a WSError when a connection error does occur.
Example it never seems to hit the WSError block and give us just an error with a message and no code.
        if let error = error as? WSError {
            if error.code != CloseCode.normal.rawValue {
                delegate?.didReceiveResponse(errorCode: error.code, errorMessage: error.message)
                onErrorReceived?(error.code, error.message)
            } else {
                delegate?.didDisconnect()
                onConnected?(false)
            }
        } else if let error = error { // We seem to get this... If I turn on airplane mode during a connection I would expect a WSError not an Error with a code to indicate the network has been lost?
            delegate?.didReceiveResponse(errorCode: nil, errorMessage: error.localizedDescription)
            onErrorReceived?(nil, error.localizedDescription)
        } else {
            delegate?.didDisconnect()
            onConnected?(false)
        }
    }

Do you have any idea what is server giving back?

Well the server doesn't and wont give anything back if I cut the connection with using Airplane mode for example. Trying to simulate the server either going away or the connection cutting to get 2 different errors to respond accordingly to.

Solved if you cast the error as NSError as below you will get a code you can switch on
            print("\(error.code)")
        }```


Attempt to reduce usage of runtimeType

Description
Don't toString expensive debugLabels in release mode.
Related Issues
https://github.com/flutter/flutter/issues/31695

As is this isn't quite good enough. it doesn't disable them in profile mode which is showing up in the fuchsia benchmarks. Will update when I've added kDebugMode and kProfileMode

Currently passing environment defines to a JIT application requires us to wire up something in the engine, but only until the constant evaluation update lands. In the meantime we can still define kDebugMode in terms of kReleaseMode and kProfileMode.


Postfix operator: improve codegen

Closes #648
Now, using dup instruction to create duplicate and apply operator to it, PostfixIncrementDecrementExpression returns old value (before operator)
I added new types of expression:

DiscardResultExpression (used to discard result of expression in statement)
DuplicateValueExpression (load and duplicate value)
ValuePreservationExpression (we specify that, after the expression, there will definitely be a value)

Codegen diff example:
int main()
{
    int x = 0;
    if (x++ == 0) { return 777; }
    return x;
}

Was:
System.Int32 <Module>::main()
  Locals:
    System.Int32 V_0
  IL_0000: ldc.i4.0
  IL_0001: stloc.0
  IL_0002: ldloc.0
  IL_0003: ldc.i4.1
  IL_0004: add
  IL_0005: stloc.0
  IL_0006: ldloc.0
  IL_0007: pop
  IL_0008: ldloc.0
  IL_0009: ldc.i4.1
  IL_000a: sub
  IL_000b: ldc.i4.0
  IL_000c: ceq
  IL_000e: brfalse IL_0019
  IL_0013: ldc.i4 777
  IL_0018: ret
  IL_0019: nop
  IL_001a: ldloc.0
  IL_001b: ret

Now:
System.Int32 <Module>::main()
  Locals:
    System.Int32 V_0
  IL_0000: ldc.i4.0
  IL_0001: stloc.0
  IL_0002: ldloc.0
  IL_0003: dup
  IL_0004: ldc.i4.1
  IL_0005: add
  IL_0006: stloc.0
  IL_0007: ldc.i4.0
  IL_0008: ceq
  IL_000a: brfalse IL_0015
  IL_000f: ldc.i4 777
  IL_0014: ret
  IL_0015: nop
  IL_0016: ldloc.0
  IL_0017: ret

Before we have this PR, I see issue like that
char s[1024];
int i, c;
for (i=0; (c = getchar()) != '\n'; i++)
    s[i] = c;
s[i] = '\0';

Currently last character from input eaten up.

Can you please verify, or better somehow add integration test which capture that this change fix an issue (at least I hope so)


testFrameworkProperty cannot be changed any further

After upgrading standalone sample to Gradle 8.1.1 (I've upgraded 3.1.x, 4.0.x and main branches) I've started seeing exceptions in the dsl/http-server project
* Where:
Build file '/home/marcin/repo/spring-cloud-contract/samples/standalone/dsl/http-server/build.gradle' line: 49

* What went wrong:
A problem occurred evaluating root project 'http-server-dsl-gradle'.
> The value for task ':contractTest' property 'testFrameworkProperty' cannot be changed any further.

@shanman190 can you check it out in your spare time :pray:  ?

@marcingrzejszczak sure, I'll try to take a look. Based on the output, it immediately points me toward something about the Test task setup likely with useJUnitPlatform(). I vaguely recall an issue similar to this on a 7.x patch release for Gradle. I'm sure we'll figure something out for it.

So the issue here is related to the finalization of testFramework on read within Gradle proper specifically for jvm-test-suites. The good news is that the finalization has been removed as part of https://github.com/gradle/gradle/issues/24331. The bad news is that this change is only available in the latest snapshots or 8.2 RC1 build and will be available once 8.2 is actually released.
As a workaround that we can do right now, would simply be to drop the useJUnitPlatform() invocation on line 49 of the sample as that is exactly the same as the default we apply to the contractTest suite in the plugin itself. For other cases where include or exclude tags are being used, those would be blocked until 8.2 is released...

Found a workaround for include/exclude tags. It involves moving from configuring the options on the task itself from the top level to modifying the options from inside of the test suite.
So this:
contractTest {
    useJUnitPlatform {
        includeTags "fast"
    }
}

Should work as (untested):
testing.suites.named("contractTest").configure {
    useJUnitPlatform {
        includeTags "fast"
    }
}

Hmm I tried to fix it through this https://github.com/spring-cloud/spring-cloud-contract/commit/169a39d481a5d32f5f9d05246f40aeff7c03365b but it didn't help. Most likely I misunderstood you :grimacing:

Hmm. That doesn't sound right given we have it configured explicitly inside of the plugin.
https://github.com/spring-cloud/spring-cloud-contract/blob/main/spring-cloud-contract-tools/spring-cloud-contract-gradle-plugin/src/main/java/org/springframework/cloud/contract/verifier/plugin/SpringCloudContractVerifierGradlePlugin.java#L137
Prior to the change to explicitly configure JUnit Platform, I would have expected the tests to fail as the JUnit 4 engine couldn't run JUnit 5 tests, but now we've explicitly told Gradle to by default use the JUnit 5 engine unless someone changes it later. I'll pull it down here in a bit and try a few things, but I would honestly have expected that to work presently.

So I've found the following to be true:

3.1.x works with Gradle 8.1.1 with the snippet that @marcingrzejszczak commented out uncommented (ie. no changes).
4.0.x works with Gradle 8.1.1 with the snippet that @marcingrzejszczak commented out uncommented and useJUnitPlatform() commented out. However, there are some failing contracts at least on Windows.
main fails for me due to what I'm suspecting is lacking a JDK 21 EA installation on my test machine. I'm assuming that commenting out useJUnitPlatform() only would also succeed like it did in the 4.0.x branch test.

The reason for this difference across the versions is due to the jvm-test-suite plugin being introduced in the 4.0.x releases. So for that one and onward, useJUnitPlatform() presently cannot be specified on the contractTest task. For 3.1.x, that predates the introduction of the jvm-test-suite plugin, so this needs to have useJUnitPlatform() still in order to properly execute tests.

Ehh so why is the Github Actions build broken for all of those branches? :grimacing:

:facepalm: I moved the useJUnitPlatform() to doFirst {} and now it's working fine. This is ridiculous

Actually it worked fine for 3.1.x and 4.0.x - the build is green (which doesn't mean that it's how it should be done). In other words the build is green so feel free to fix it however you think it should be done ;)


chore: Release 0.10.0

Description

Changes proposed in this pull request:

Bump Images and modules to 0.8.0

Related Issues and Documents

Closes:
Related issues:
Traceability

[ ] The PR is linked to a GitHub Issue.
[ ] New features have a milestone label set.
[ ] New features have defined acceptance criteria in a corresponding GitHub Issue, and all criteria are satisfied with this PR.
[ ] The corresponding GitHub Issue has a respective area label.
[ ] The follow-up issues (if any) are linked in the Related Issues section.

Testability
The feature is unit-tested:

[ ] Yes.
[ ] No, because unit tests are not needed.
[ ] No, because of ...

The feature is e2e-tested:

[ ] Yes.
[ ] No, because e2e-tests are not needed.
[ ] No, because of ...

Tests conducted for the PR:

Codebase

[ ] My code follows the Effective Go style guidelines.
[ ] The code was planned and designed following the defined architecture and the separation of concerns.
[ ] The code has sufficient comments, particularly for all hard-to-understand areas.
[ ] This PR adds value and shows no feature creep.
[ ] I have augmented the test suite that proves my fix is effective or that my feature works.
[ ] Adjusted the documentation if the change is user-facing.

documentation link fix: https://github.com/kyma-project/telemetry-manager/pull/388

/retest


Feature Request: Support for Razer Base Station Chroma, Steelseries Devices

Would it be possible to provide support for the Razer Base Station Chroma and Steelseries devices such as the rival 310/600/700?

The rival 310/600/700 should be working properly through the Steelseries support that has already been implemented. Just need to select a mouse that has a similar lighting layout and it should be fine. The Razer Base Station chroma will be supported when I finish reworking the device layout system.

Fixed with latest Chroma Link update.


proporti.onl HTTPS certificate has expired

Chrome says "There are issues with the site's certificate chain (net::ERR_CERT_DATE_INVALID)"
Expiry date was Thursday, September 21, 2017 at 5:49:00 AM

Thanks. I have got to find a better way of managing letsencrypt certs on PythonAnywhere.

Fixed, and I'm going to move to a 3-year signed certificate instead of Let's Encrypt. Thanks for the heads up.


type 'Null' is not a subtype of type 'String'

i'm using a new version of flutter
i get this error:  type 'Null' is not a subtype of type 'String'
at the 3rd this line of the code (plan_services.dart):
  Plan createPlan(String name) {
    final model = _repository.create();
    print('my name $name');                                           //the name in not null here
    final plan = Plan.fromModel(model)..name = name;            //error here
    savePlan(plan);
    return plan;
  }

after debugging, i got name=null here (plan.dart)
  Plan.fromModel(Model model)
      : id = model.id,
        name = model.data['name'],             //the name is null here
        tasks = model.data['task']
                ?.map<Task>((task) => Task.fromModel(task))
                ?.toList() ??
            <Task>[];

can you explain why? thank you

Hey @amkfat can you please also provide the chapter and page number of the exercise you are following? We will try to reach out to author and provide you with an explanation and resolution for your queries.


Spatial view stuff auto retry

Description
Ported over the command auto retry utility that I had in the ww repo.
This isn't tested etc. Just up to let people have a look at it.

Added tests and some utils around it.
entity query support for the op list builder is still WIP and for some reason the entity command request tests are failing atm.

Only nit I have is that is is a bit tedious to go through mostly similar code dealing with-almost-but-no-quite-so-similar commands.
For example, if someone has an idea on how to reduce the amount of code in CommandRetryHandler, we should do it because there is a lot of duplicated boilerplate. I tried and failed to come up with something significantly better, so maybe it is as good as it gets.

Which code do you mean? As it's templated I thought the command retry handler is pretty lean at this point.