Get wallet working with a new testnet deployment

Deploy NF into a server using the instructions from here
The wallet will talk to the client deployed from the above
Proposer, Liquidity Provider, Challenger users will be started from the same server
Geth ropsten full node deployed in one of our servers will be used for this deployment

Definition of done: All the wallet functionality working on ganache to work with this ropsten testnet deployment

This issue requires the following PRs to be merged:
#334, #386, #389, #398 and #401

This needs to be done but for the new wallet.


Postgres Plugin should support configurations without an admin user (CREATEDB)

Currently, the experimental postgres plugin requires that you pass storage credentials for an admin user. In this case, admin really means a postgres user that has the CREATEDB role.
For example, with the MultiWalletSingleTable strategy, the following code runs on init:
        debug!("setting up the admin_postgres_url");
        // look to see if there is a specified db to use.  If not, use the default name
        let wallet_db_name: &str = get_multi_database_name(config);
        debug!("wallet_db_name: {:?}", wallet_db_name);
        let url_base = PostgresStorageType::_admin_postgres_url(&config, &credentials);
        let url = PostgresStorageType::_postgres_url(wallet_db_name, &config, &credentials);
        debug!("postgres_url: {:?}", url);
        debug!("connecting to postgres, url_base: {:?}", url_base);
        let conn = postgres::Connection::connect(&url_base[..], config.tls())?;

        debug!("creating wallets DB");
        let create_db_sql: String = str::replace(_CREATE_WALLET_DATABASE, "$1", wallet_db_name);
        debug!("create_db_sql: {:?}", create_db_sql);
        if let Err(error) = conn.execute(&create_db_sql, &[]) {
            if error.code() != Some(&postgres::error::DUPLICATE_DATABASE) {
                debug!("error creating database, Error: {}", error);
                conn.finish()?;
                return Err(WalletStorageError::IOError(format!("Error occurred while creating the database: {}", error)));
            } else {
                // if database already exists, assume tables are created already and return
                debug!("database already exists");
                conn.finish()?;
                return Ok(());
            }
        }
        conn.finish()?;

I think this is not an ideal implementation, because it does not cater to all potential security/architecture models when it comes to provisioning databases. If the admin_account does not have CREATEDB permissions, even if the wallets DB already exists, this code will fail to initialize as a different error will be returned than postgres::error::DUPLICATE_DATABASE.
As someone who wants to run the postgres plugin on a production deployment, I want the option to provision my postgres database in advance with an admin/super user account, but never actually give the application access to those credentials during runtime.
Possible fixes:

Have a storage configuration flag to disable database and schema creation and assume that the DB already exists
Instead of trying to create the database and check for DUPLICATE_DATABASE error, use some other method with the non admin user to determine if a database of that name in fact does already exist, and skip the database and schema creation if it does
If the admin user does not have permissions for CREATEDB, also check for this error code in addition to DUPLICATE_DATABASE, and assume the database exists like in the current flow

@msembinelli Thanks for raising this, I think that's valid concern and I agree with solution your've proposed. Except that I think if the second and third point of solution you've proposed is implemented well, I think the first point (the "configuration flag") would not be even needed.
@ianco what do you think?
@msembinelli would you be willing to implement this?

Hi @Patrik-Stas yes I agree @msembinelli has raise some good points about the database creation.
The intent was that the database could be created in advance, in which case the admin user would not be required and the plug-in would use the existing database, however as @msembinelli points out the duplicate database check is not sufficient for this.
I agree with the proposed solution.

@Patrik-Stas @ianco Thank you for responding!
I just got back from vacation, so I will look at creating a PR soon to implement this. Thanks!


New version: ImageAxes v0.6.10

Registering package: ImageAxes
Repository: https://github.com/JuliaImages/ImageAxes.jl
Created by: @johnnychen94
Version: v0.6.10
Commit: 2cde1bfcadf70403ae3b2eec93ad91c5fa3a8017
Reviewed by: @johnnychen94
Reference: https://github.com/JuliaImages/ImageAxes.jl/commit/2cde1bfcadf70403ae3b2eec93ad91c5fa3a8017#commitcomment-55584036

A second thought. I might release this patch too soon and the downstream package isn't ready yet. Let me pause this registration for a while until we're ready.


2022 Hyundai Santa Fe error messages

Describe the bug
While driving the car I can sometimes get vehicle error messages saying

Check rear cross traffic safety system
Check forward safety system
Check blind spot safety system

Auto pilot would beep, disengage & show in red
"Cruise Fault take control immediately!"
In addition, 1 out of 3 times when starting the car I would get the same vehicle error messages
And autopilot would say
" cruise Fault: restart the car to engage)
On a side note auto hold feature gets disabled as well.

Which car does this affect?
2022 Hyundai Santa Fe limited
Provide a route where the issue occurs
1493c38de09a381a|2023-02-01--07-36-19--85
openpilot version
0.9.0
Additional info
Since I am an automotive electrical engineer I did first try to troubleshoot on my own.
First thing; I turned the engine off then restart it
And all the messages were still there until I started driving a little bit.
I do the same whenever I get the error messages and it's usually goes away after a little bit of driving.
I also hooked up my scanner to check the codes and what looks to me as a: can communication failure
I tried unplugging the T- harness
And putting everything back to factory spec but that didn't take the error messages away until I drove a little bit.
If there is anything that I can do to help comma team figure this out I'll be more than happy to assist.

I see you're not using openpilot longitudinal, so all those DTCs about SCC messages being invalid is very strange. I didn't see any issues with the counters for any SCC message when it faulted. Have you ever gotten these errors before openpilot? What if you put the device in dashcam mode?

Thanks for getting back to me. I did not see any of these messages before I had installed my comma 3. I am going to try putting it into dash cam mode and seeing if these messages ever appear again. Also I'm pretty new to Comma and open pilot so I'm not exactly sure what longitudinal means.
Actually I'm starting to think that something is wrong with my car. Because on the website it says that the Hyundai Santa Fe 2022 is compatible with experimental mode. But what happens when I try to turn on experimental mode it says:
"Experimental mode is currently unavailable on this car, since the car's stock ACC is used for longitudinal control."
I would love to use experimental mode but I'm not sure if something is wrong with my vehicle or it's just not supported for some reason.

Actually I'm starting to think that something is wrong with my car. Because on the website it says that the Hyundai Santa Fe 2022 is compatible with experimental mode. But what happens when I try to turn on experimental mode it says: "Experimental mode is currently unavailable on this car, since the car's stock ACC is used for longitudinal control."

Your car also needs "Experimental openpilot longitudinal control" to run Experimental mode, which is only available in non-release branches. This is made more clear in the toggle text in the upcoming release. Check out https://discord.comma.ai for more info.

Oh, got it.
So what could Thea's error messages mean?
I have an automotive ship in NY. We do emergency vehicle upfitting. So I familiar with different types of error messages. To me it looks like sometimes there's a glitch & that causes a communication failure in the can network.

You're right in that it's likely a CAN communication error. Unfortunately, the OBD-C cable can fail very subtly. Did you bend the cable while installing the device? You can try swapping out that cable or bending it a bit while the car is on (and parked) to see if the errors show up.

Ok great, I'll crimp up an rj45 and run a brand new cable down to the obd2 port. Hopefully it's it'll solve this issue.
Btw I some how 2 questions on my comma. I'd love to know if I can shoot you an email with a couple of questions and you'll be able to answer those for me 🙏🏻🙏🏻

Ok great, I'll crimp up an rj45 and run a brand new cable down to the obd2 port. Hopefully it's it'll solve this issue.

It's not the one running down to the comma power; OBD-C is just what we call the USB-C cable.

Btw I some how 2 questions on my comma. I'd love to know if I can shoot you an email with a couple of questions and you'll be able to answer those for me 🙏🏻🙏🏻

The community discord is probably a better place for this.

Okay thanks. I'll try to ask around.
Do you have any recommendations on a usb c replace cable?

I checked your routes out in more detail and it appears that your right rear wheel speed sensor is defective. It's randomly jumping around, then going to the max signal value (which is when you see the faults). I would get this checked out at a dealer, since it's affecting ABS, traction control.

Wow. Pretty impressive that you were able to crack down on this. It's interesting because a speed sensor shouldn't go bad on a brand new 2022 vehicle with 10k miles on the clock.
I'll definitely take it to a dealership to have a look.
Lately I've been having this a lot. Almost every morning when I come in the vehicle after remote starting I will see all the air messages on the dash. All I need to do is to turn the car off then back on the error messages will still be there until I drive past 8mph. But besides of that speed sensor do you think it could have to do with my battery? Because my battery is pretty low lately and I'm getting messages almost every morning "battery discharging due to external electrical devices". So bottom line, are you certain that the speed sensor is what's causing the issue or it could be the battery as well or both?

I've never seen anything like this before, so it's hard to say what the cause is. Let me know when you go get it checked out!

@YUMISCOMMA did you get your vehicle checked out?

Thank you so much for reaching out.
At this time I'm already very frustrated with my car. I started hating her:)
I didn't go to the dealer because I know that they're going to blame a lot
of other things including my c3 & some aftermarket stuff that I've added
such as "hardwired dashcam & radar detector onboard air and air horns" even
though all my wiring and relays and crimps are done very professionally
because I do this for a living. I have a shop in New York called
"Autobuffny". You can check it up on Instagram we do lights and sirens for
emergency responders. So I'm pretty familiar with vehicle wiring and
schematics. And I definitely know the dealerships,  their hair to blame all
my aftermarket equipment. Now back to the car. I still get the error
message almost every morning when I remove start my car. But it's not
consistent. Sometimes yeah and sometimes no. What else I noticed is that
most of the time it happens when the vehicle is stopped. Such as upon
startup or a traffic on the vehicle comes to a full stop. What I usually
do, I wait until I hit a traffic light & I just restart the car. Once I hit
8 mph all the error codes go away. Most of the time it goes away till the
end of the trip but sometimes it does come back randomly. I really think
that my battery is what's causing it. Because I have a lot of accessories
Hooked up to it & it might be under 12v upon start up or low rpm's so thats
causing some computers to malfunction & trigger the errors.
Now to my main concern. I've had this twice and I almost killed myself.
"When the error message pops up I sometimes hear/feel vibration in my brake
pedal. It feels like the ABS pump is glitching. And whenever that happens
my brakes don't work! I've literally almost crashed into someone. My brake
pedal becomes hard as a rock and I cannot brake!  I'm very concerned.
What do you think I should do?
The dealership's next appointment is in April.
I actually called them and told them that it's an emergency my brakes
aren't working. They told me that I don't have loaners at the moment and I
can either drop off my car at the dealership lot or wait for the next
appointment.
So I'm pretty much screwed.
Do you think you'll be able to gather some more info if I send you more
routes and logs?
Thank you so much for
trying to help 🙏🏻🥰
Best regards
Ben
On Tue, Mar 21, 2023, 10:51 PM Shane Smiskol @.***>
wrote:

@YUMISCOMMA https://github.com/YUMISCOMMA did you get your vehicle
checked out?
—
Reply to this email directly, view it on GitHub
https://github.com/commaai/openpilot/issues/27177#issuecomment-1478848841,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A5TK2PJ7PZQQ3AO5DUOPAC3W5JSLVANCNFSM6AAAAAAUOEPXDM
.
You are receiving this because you were mentioned.Message ID:
@.***>

Yeah I would definitely hold off on driving the vehicle until you can get into the dealer to check it out. You can remove the comma three if you're concerned about the dealer saying anything, it's not a permanent install as you know.
From what we know about your faulty wheel speed sensors (or some other wiring), who knows how the modules in the car might respond to that.

Hi @YUMISCOMMA. I'm closing since this is a physical problem with your car, not openpilot, as noted above. Let me know if you have any other problems specifically with openpilot!

I appreciate it.
Yes you can actually close this case.
As a matter of fact I haven't received those errors for a couple of months
now. I'm not sure what caused it to stop coming. But so far so good.
Best regards.
On Wed, May 10, 2023, 3:33 AM Shane Smiskol @.***>
wrote:

Hi @YUMISCOMMA https://github.com/YUMISCOMMA. I'm closing since this is
a physical problem with your car, not openpilot, as noted above. Let me
know if you have any other problems specifically with openpilot!
—
Reply to this email directly, view it on GitHub
https://github.com/commaai/openpilot/issues/27177#issuecomment-1541496936,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A5TK2PNTAUOTM5OFDT2XN73XFNAGFANCNFSM6AAAAAAUOEPXDM
.
You are receiving this because you were mentioned.Message ID:
@.***>


just display the message of the errors in the CLI

Pull Request Overview
What does it do?
Closes https://github.com/fonoster/fonoster/issues/241
Before asking for review I...

[x] Have added all relevant information about my changes in this PR
[x] Have performed a self-review of my own code
[x] Have made sure my code follows the project's style guidelines
[x] Have checked my code and corrected any misspellings
[x] Have made sure my changes generate no new warnings

/cc @psanders

Looks good to me.


SOUNDS: Display waveform function is not very useful

const sound1 = sine_sound(25, 1);
const sound2 = noise_sound(1);

function add_sounds(sound1, sound2) {
    [redacted]
}

display_waveform(500, add_sounds(sound1, sound2));

The above code produces the image below:

Sounds of greater duration/frequency creates blocky images like below:

Suggestion 1) the curve should ideally span the left edge to the right edge
2) Is there a way to "slice" the waveform, or something?
3) For future consideration: Animation, animating of the waveform can help alot.

const sound1 = sine_sound(10, 0.5);
const sound2 = square_sound(10, 0.5);
const sound3 = triangle_sound(10, 0.5);

function add_sounds(sound1, sound2) {
    [redacted]
}

function display_waveform(num_points_per_second, sound) {
    let wave = get_wave(sound);
    let duration = get_duration(sound);
    let num_points = num_points_per_second * duration;
    return draw_connected_full_view(num_points)(t => pair(t, wave(duration * t)));
}

display_waveform(5000, add_sounds(add_sounds(sound1, sound2), sound3));

The above code produces the below image. Note the overriden display_waveform

Display waveform is useful for showing ADSR envelopes.

moved to modules: https://github.com/source-academy/modules/issues/120


Add user emails

Required before we can do #21

Coverage increased (+0.3%) to 69.008% when pulling 909df80941fb64c8aee43b317d2b58293637900b on emails into 4c95b830fe86c9bf57fa6dd918bba0c4c5390b34 on master.


Remove duplicate words

The word "國" was the topic of several rows, probably because it is part of several words.
We should remove all duplicate words. They might occur in separate lessons.

I removed all duplicates today and I will merge my changes in appx. 12 hours.

Fixed, thanks @leonfox1 ! :-)


Blocking for DInput devices

I'm emulating a DualShock4 controller with a Nacon Compact PS4 Controller and figured out while using Steam in Big Picture mode (for testing) that navigation felt super fast, I think it's due to the fact that the PC still seems to detect the Nacon controller because it moves 2 slots at a time every time I press a d-pad button or move the left stick, like if I was using 2 controllers at the same time. In UCR, Interception has an option to block the input from the physical device, is it possible to do the same with ViGEm ?

Sounds like a use-case for HidHide.

Perfect!


part: set up overridable options

Fix #000
Proposed Changes

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#804 : 2  dependent PRs (#807 , #810 )
#803
#812  👈
#809
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @RebeccaStevens and the rest of your teammates on  Graphite


Edit tasks functionality working

Naming Rules
Name your PR like this: ISSUENUMBER-TITLE-YOURNAME
Description
Edit task functionality, edit task button, opens task form, can edit task details then update in db. the task list on the users page, automatically re-renders and updates to reflect changes of task details.
Related to
Make sure you include the issue number with a hash sign # so Github can link this PR to the right issue, like this:
Fixes #1
Checklist:

[x ] My code follows the style guidelines of this project
[x ] I have carefully reviewed my own code
[ x] I have commented my code
[ x] I have updated any documentation

Thank you, reviewed this, great effort!


Sync branches

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


kubeless function call results into "FATA[0000] the server could not find the requested resource"

Is this a BUG REPORT or FEATURE REQUEST?:
BUG
What happened:
kubeless function ls
NAME 	NAMESPACE	HANDLER    	RUNTIME  	DEPENDENCIES	STATUS
hello	default  	hello.hello	python2.7	            	1/1 READY
test 	default  	test.hello 	python2.7	            	1/1 READY
kubeless function call hello --data "Hello"
ERRO[0000] {
"paths": [
"/apis",
"/apis/",
"/apis/apiextensions.k8s.io",
"/apis/apiextensions.k8s.io/v1",
"/apis/apiextensions.k8s.io/v1beta1",
"/healthz",
"/healthz/etcd",
"/healthz/log",
"/healthz/ping",
"/healthz/poststarthook/crd-informer-synced",
"/healthz/poststarthook/generic-apiserver-start-informers",
"/healthz/poststarthook/priority-and-fairness-config-consumer",
"/healthz/poststarthook/priority-and-fairness-filter",
"/healthz/poststarthook/start-apiextensions-controllers",
"/healthz/poststarthook/start-apiextensions-informers",
"/livez",
"/livez/etcd",
"/livez/log",
"/livez/ping",
"/livez/poststarthook/crd-informer-synced",
"/livez/poststarthook/generic-apiserver-start-informers",
"/livez/poststarthook/priority-and-fairness-config-consumer",
"/livez/poststarthook/priority-and-fairness-filter",
"/livez/poststarthook/start-apiextensions-controllers",
"/livez/poststarthook/start-apiextensions-informers",
"/metrics",
"/openapi/v2",
"/readyz",
"/readyz/etcd",
"/readyz/informer-sync",
"/readyz/log",
"/readyz/ping",
"/readyz/poststarthook/crd-informer-synced",
"/readyz/poststarthook/generic-apiserver-start-informers",
"/readyz/poststarthook/priority-and-fairness-config-consumer",
"/readyz/poststarthook/priority-and-fairness-filter",
"/readyz/poststarthook/start-apiextensions-controllers",
"/readyz/poststarthook/start-apiextensions-informers",
"/readyz/shutdown",
"/version"
]
}
FATA[0000] the server could not find the requested resource
What you expected to happen:
Expected to display "Hello" as output.
How to reproduce it (as minimally and precisely as possible):
Any number of calls made to Kubeless function results into an error.  I did try to reboot the master & worker nodes, yum update but had no change in the output.
Environment:
kubectl version --short
Client Version: v1.20.2
Server Version: v1.20.2
kubectl get nodes
NAME            STATUS   ROLES                  AGE   VERSION
kube-master     Ready    control-plane,master   34h   v1.20.2
kube-worker-1   Ready                     34h   v1.20.2
kube-worker-2   Ready                     34h   v1.20.2
kubectl get pods --all-namespaces
NAMESPACE     NAME                                          READY   STATUS    RESTARTS   AGE
default       hello-865cb85979-4fs4l                        1/1     Running   1          33h
default       test-6685b5f887-pdllk                         1/1     Running   1          33h
kube-system   coredns-74ff55c5b-8pcq6                       1/1     Running   1          34h
kube-system   coredns-74ff55c5b-qrr89                       1/1     Running   1          34h
kube-system   etcd-kube-master                              1/1     Running   1          34h
kube-system   kube-apiserver-kube-master                    1/1     Running   1          34h
kube-system   kube-controller-manager-kube-master           1/1     Running   1          34h
kube-system   kube-flannel-ds-ctp4s                         1/1     Running   1          34h
kube-system   kube-flannel-ds-lp5x9                         1/1     Running   1          34h
kube-system   kube-flannel-ds-tcfw7                         1/1     Running   1          34h
kube-system   kube-proxy-78lr8                              1/1     Running   1          34h
kube-system   kube-proxy-ggkm7                              1/1     Running   1          34h
kube-system   kube-proxy-w627z                              1/1     Running   1          34h
kube-system   kube-scheduler-kube-master                    1/1     Running   1          34h
kubeless      kubeless-controller-manager-99459cb67-f66qk   3/3     Running   3          33h

Cloud provider or physical cluster:
Physical cluster

This seems to be the same issue as https://github.com/kubeless/kubeless/issues/1130
At the moment, Kubernetes versions > 1.18 are not fully supported.

This seems to be the same issue as https://github.com/kubeless/kubeless/issues/1130
At the moment, Kubernetes versions > 1.18 are not fully supported.

Changing the Kubernetes to V1.18 resolved the issue.

Changing the Kubernetes to V1.18 resolved the issue.


EveCurveLineSet and animations

There are a few functions in the EveCurveLineSet constructor that I am interested in using: ChangeLineMultiColor and  ChangeLineAnimation but they don't seem to do anything apart from changing the colour of the lines. Does anyone have any examples where the do anything similar to their names?

The ChangeLineMultiColor function sets the second color for line segment and a fraction (from 0 to 1) where the primary color changes to this second color.
The ChangeLineAnimation function controls secondary texture ("OverlayTexMap" parameter) scrolling along the line segment.

Do you happen to have a working example of this, I am unable to get the scrolling to work.

There are a couple of errors still in this file which I've fixed elsewhere, I'll post a pull request later.


request-validator.config.allowed_content_types is an array

Review

@reviewer
Summary

https://docs.konghq.com/hub/kong-inc/request-validator/
The docs for the request validator plugin shows allowed_content_types to be a string, but it's actually an array of strings.

here's the source code https://github.com/Kong/kong-plugin-enterprise-request-validator/blob/master/kong/plugins/request-validator/schema.lua#L97-L103
Reason

Testing

Note that my single commit isn't enough to fix the above, but I couldn't quite see where to make the necessary change to update the various examples.  From what I can tell all of them are wrong.

@dimitropoulos you can also log DOCU tickets for any suggested updates. That way we can better track the plugin effort. Also if you think a schema needs a fix, please log a bug to the appropriate team to take care of that. Thanks for your PRs. Murillo and I have been chipping away at adding datatypes for the past year. Almost done. Tracking here: https://docs.google.com/spreadsheets/d/1nZJ0cPkOaZqTGTEICBrTa3TK2xIJqYkclZbJM04eROc/edit#gid=0


Support multiple permissions with a single CosmosClient instance

Context
We are currently using Cosmos DB with the SQL API as the storage option for a .NET project where we configured multiple containers each with its own user permission.
The .NET SDK v2 DocumentClient can be constructed using a list of permissions that allows us to use a Singleton instance of DocumentClient to access multiple containers based on their specific permssions.
Issue
We would like to upgrade to the Cosmos .NET SDK v3 but we have an issue:
The v3 CosmosClient can only be instantiated with a single Permission.Token, thus implying the creation of a CosmosClient for each CosmosDB call to a different container. As the Microsoft Docs recommend to only instantiate one CosmosClient throughout the lifetime of the application (Singleton), we cannot migrate to v3 without sacrificing security or performance. Thus, the only way to maintain a single instance of CosmosClient is to use the Master Key meaning we lose the granular container level access permissions.
Question/Suggestions
Is there a plan to support this type of scenario in the future?
For example:

CosmosClient instantiated with multiple permissions
OR allow passing the Permission.Token as part of the RequestOptions with each request

What is Microsoft's recommendation for the design mismatch between recommending a single instance of CosmosClient and only allowing a single permission to be used per CosmosClient instance?

I think this has already been reported under #651.


Jest reporting support

See #106 for one possible approach which was removed for 1.0.0

Basic support added in #189


Excon v0.111.0 has broken this gem

The VALID_REQUEST_KEYS constant is now frozen so a FrozenError is thrown when requireing this gem.
FrozenError: can't modify frozen Array: [:allow_unstubbed_requests, :body, :chunk_size, :debug_request, :debug_response, :dns_timeouts, :headers, :instrumentor, :logger, :method, :middlewares, :password, :path, :persistent, :pipeline, :query, :read_timeout, :request_block, :resolv_resolver, :response_block, :stubs, :timeout, :user, :versions, :write_timeout]

https://github.com/excon/excon/blame/master/lib/excon/constants.rb#L66

not nice to see this in our production env impacting 1000s of hosts today. How can we prevent this from happening in the future?

Invest in a CI setup and don't pull random updates into production?

Invest in a CI setup and don't pull random updates into production?

Chef automatically installs latest gem(s) that meet defined dependencies on each run. The only way to stop this would be to make sure it uses the Bundler flag --prefer-local so it uses the installed gems if they meet the requirements, but that feature didn't exist until December 2023 and Chef hasn't shipped a new version with that version of Bundler.
I suspect Puppet users are in the same situation.
The only other way this could have been avoided would be for docker-api to have more strictly pinned the version requirement of excon.
To work around it I had to modify the docker cookbook to pull the gem from my own rubygems server (geminabox) and build/upload a copy of "docker-api-2.2.1" from the fix-excon-frozenerror branch here.
Completely insane behavior all around, really.

Hi folks, release v2.3.0 which should fix this error.

Sorry to hear about this impact (I'm the author of excon). I hadn't seen any reason to believe this freeze would have this kind of impact since the excon test suite otherwise was not impacted by it. This may speak to the hijack middleware being somewhat unusual compared to other things and was doing something that was not expected. In any event, I'm glad you were able to find the fix quickly and feel free to reach out if you have issues or concerns in the future.

No worries @geemus, definitely our fault on this end for not updating to the proper interface.

Easy to overlook I'm sure, glad it was an easy fix.

@ls-todd-lunter, do you mean to add a v2.3.0 tag? I was looking to see if the new version was out and saw no tag and didn't realize it was already on rubygems.org

@b-dean sorry, yes. Pushed the tag now.


[opentelemetry-cpp] Update to 1.10.0

Fixes #33177, update opentelemetry-cpp to 1.10.0.

Remove deprecated option WITH_OTLP: CHANGELOG.md#L38-L39

Remove deprecated option WITH_JAEGER: CHANGELOG.md?#L145-L148, DEPRECATED.md#jaeger-propagator

All features are tested successfully in the following triplet:
x86-windows
x64-windows
x64-windows-static

The usage test passed on x64-windows (header files found):
opentelemetry-cpp provides CMake targets:

  # this is heuristically generated, and may not be correct
  find_package(opentelemetry-cpp CONFIG REQUIRED)
  # note: 26 additional targets are not displayed.
  target_link_libraries(main PRIVATE opentelemetry-cpp::api opentelemetry-cpp::ext opentelemetry-cpp::sdk opentelemetry-cpp::logs)

[x] Changes comply with the maintainer guide
[x] SHA512s are updated for each updated download
[ ] The "supports" clause reflects platforms that may be fixed by this new version
[ ] Any fixed CI baseline entries are removed from that file.
[ ] Any patches that are no longer applied are deleted from the port's directory.
[x] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
[x] Only one version is added to each modified port's versions file.

Higher version #33983.


Boom plugin clashes with grafana reporter

Hi there, great tool, thanks!
I want to customize the looks of our Grafana instance and I treid this: https://grafana.com/grafana/plugins/yesoreyeram-boomtheme-panel. There only problem is when generating a report; it fails with the following error: error rendering PNGs in parralel for dash. The problem is getting the render of the panel containg the theme selection:  error getting panel {Id:17 Type:yesoreyeram-boomtheme-panel
I can see the images of the dashboards be correctly saved in the tmp folder, but it doesnt work. As soon as I remove the dashboard from this plugin with the theme selection the report works.
Any idea if there is a fix?
EDIT: I just read here that exports are not expected to work. Is there a to make it work though?

EDIT: I just read here that exports are not expected to work. Is there a to make it work though?

Thanks for the link. No if not png rendering is not supported by the panel, it will not work.


Phoenix LiveView-like feature inside Dream

Would a Phoenix LiveView-like feature best be a part of the dream framework or live as a plug-in or library?
To those unknown, LiveView is the Elixir Phoenix library that allows servers to dynamically render HTML and serve it over websockets.
A few other frameworks exist that are beginning to do the same: Ruby Hotwire and Haskell IHP.
Another option may be to create an HTMX-compatible dream middleware much like how Sihl is doing so for a more dynamic UX without heavy JS.
Is the GitHub discussion available for this repo? This isn’t really an issue, but more a discussion.

I think it's better to keep it as a library for now. However, I'd be very happy to coordinate development with it, support it on the Dream side, and link to it.
My concern is that Dream has only one maintainer right now (me :P) and people might contribute a lot of interesting things, but then not stick around to really finish and maintain them. Meanwhile there is already a ton of work for me to finish only the core of Dream to a truly high level of quality. So I'd like to coordinate with multiple people independently and see what develops over time. Later, Dream might have some kind of stable team of people working on it (probably informal), and it will be clearer what can be upstreamed, if needed.
If you're interested in developing this, you may want to see example w-live-reload (perhaps you already have), contributed by @tmattio. It's, of course, not the same thing, but it's vaguely relevant :)
I'll be happy to link to a repo as proposed in https://github.com/aantron/dream/pull/58 and suggested in Contributing, and offer any other support to make it visible, usable, etc.

Is the GitHub discussion available for this repo? This isn’t really an issue, but more a discussion.

I disabled it for now because issues are still fine for basic discussion, and it's one less thing to deal with this early. However, if you think it should be enabled, please let me know.

I'm closing this issue for now to keep the tracker tidy, but please feel free to comment, and reopen the issue if needed.

I just came across this: https://erratique.ch/software/hc - https://discuss.ocaml.org/t/tutorial-full-stack-web-dev-in-ocaml-w-dream-bonsai-and-graphql/9963/13

Hc declares dynamic web pages by using HTML data attributes to seamlessly update the page with HTML fragments requested from the server.

Using hypertext as the interaction substrate keeps logic on the server and, in the simplest cases, reduces front-end client code to custom CSS animations and inclusion of a generic JavaScript driver.

It might be nice to look into for dream

Yeah, the docs describe it as being inspired by htmx. FWIW, that's the "front end" I'm using in my current project (mostly using htmx's websocket support and its "out of band" DOM updates); it's been very pleasant.


JOB Lifespan

What do you think about a JOB lifespan? For my experiments on fault tolerance I need Flink to be set up freshly before every job run, since I am killing nodes during job execution. Is that something other people might need as well?

Makes sense. We can meet and I will show you where to add the code.

Resolved by ed186688dadb0770f4842ba8150d4784b74999a4. @markus-h thanks for the fix!


[Feature Request] Navigate between picture previews without swiping effect

In picture preview page (one full screen image), swiping left/right to go to next/previous picture is standard, good, and intuitive.
However, I think it would be a real plus to have the possibility to also go to next/previous image without swiping effect. It would facilitate comparison for very similar images, if the images changed without any animation.
I imagine there could be a slideshow mode for example, in which images change from simply tapping in the left or right part of the screen (lots of browser galleries function this way).
Additionally, such mode could even allow swiping gestures to propose other functionalities like easy tagging, flagging or rating (swipe down to flag red, up for green, left or right could open side menus with tickboxes lists of tags).

I already implement an option to turn of the PageTransformer Animation.
https://github.com/kollerlukas/Camera-Roll-Android-App/commit/6b5fbb1c13fd94dd339afaaf946adf95fc5a611c
Expect this feature with the next update

I just installed the latest Camera Roll update from F-Droid, and I was looking into the settings. I found the PageTransformer Animation toggle, but it doesn't seem to allow the feature I described previously.
(I don't know if that makes any difference, but I'm using Android 7.1.2)
This is how it looks with animations:

This is how it looks without animations:

This is how would be the intended feature I was describing:


Implement Dimming actuator

This implements the Dimming actuator

I don't get it how to test the set_brightness() function

This implements the Dimming actuator

Have you been able to run tests locally? That'll help a lot in triaging the tests.
Setup a Python virtual environment and install the PyPi package pip install . while in the root directory.

This implements the Dimming actuator

Have you been able to run tests locally? That'll help a lot in triaging the tests.
Setup a Python virtual environment and install the PyPi package pip install . while in the root directory.

Thanks a lot for the explanation. I've set now everything in visual studio code and it seems to run, but ...
My local pytest displays all tests as passed, but here it shows "failed" again.

Thanks a lot for the explanation. I've set now everything in visual studio code and it seems to run, but ... My local pytest displays all tests as passed, but here it shows "failed" again.
Additionally, I think set_brightness is not fully tested, but I don't undetstand how to use the "dimming_actuator._api.set_datapoint.assert_called_with()" meaningfull as it returns different stuff as it should 😢

Your latest one is failing because of code coverage. You can view the results under the action summary.
https://github.com/kingsleyadam/local-abbfreeathome/actions/runs/11386836788
Once you run the test it'll publish a code coverage HTML output so you can see what still needs to be covered. It should be at: ./coverage/htmlcov/index.html

It's just one line where a device update wouldn't affect the state.

Thanks a lot for the explanation. I've set now everything in visual studio code and it seems to run, but ... My local pytest displays all tests as passed, but here it shows "failed" again.
Additionally, I think set_brightness is not fully tested, but I don't undetstand how to use the "dimming_actuator._api.set_datapoint.assert_called_with()" meaningfull as it returns different stuff as it should 😢

Your latest one is failing because of code coverage. You can view the results under the action summary.
https://github.com/kingsleyadam/local-abbfreeathome/actions/runs/11386836788
Once you run the test it'll publish a code coverage HTML output so you can see what still needs to be covered. It should be at: ./coverage/htmlcov/index.html

It's just one line where a device update wouldn't affect the state.

Sorry, I'm totally lost here. When I run the pytest-command as stated by you above I get a coverage-output stating that everything is OK.
Also, when I look at your hint I don't understand why this line is a problem. It is exactly the same like e.g. in MovementDetector

Sorry, I'm totally lost here. When I run the pytest-command as stated by you above I get a coverage-output stating that everything is OK.
Also, when I look at your hint I don't understand why this line is a problem. It is exactly the same like e.g. in MovementDetector

No worries, I'll take a look tomorrow.
I noticed an issue with how I setup the tests that make it really hard to triage in VS Code. I'll make a change tomorrow which will allow you to see coverage in VS Code and Debug the Test Code including stepping into the module code.


build error

Describe the bug
When I was building the image, an error occurred and I don't know where to adjust it
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots

Additional context
Add any other context about the problem here.

@luugh I can't reproduce the problem and the Dockerfile works fine on the GitHub Runner too.
May it be that you are behind a proxy or something like that?

@luugh  - error code 137 might indicate out of memory error

@luugh please provide more details.
How much RAM does the machine you run this build on have?
When running it, how much of the RAM is being used?
Did you set any app settings in the appsettings file, the Dockerfile, or as environment variables on the environment you ran this build in?

@luugh, check this issue from PowerShell repository
I guess the issue is not related to BaGetter

Closing issue due to no new information


Implement flatfile functionality for CNV and introduce cnvKompare

This PR introduces the flatfile functionality for CNV to avoid reliance on the database. The useful feature here is a new cnvKomare function that will compare CNV data for patients with multiple time points and calculate the overall concordance of CNV + other comparison data. It can also handle the comparison of CNV between different tools if needed.

This also addresses and resolves issue #19

Thanks for review Laura! I fixed these issues, and also added additional function to specify minimum similarity between cytobands to be considered concordant/discordant


Hope can save preference to my Microsoft account.

VSCode Version: Code 1.18.0 (dcee2202709a4f223185514b9275aa4229841aa7, 2017-11-08T21:22:49.932Z)
OS Version: Windows_NT x64 6.1.7601
Extensions:

Extension
Author (truncated)
Version

json-tools
eri
1.0.2

php-debug
fel
1.11.1

phpcs
ika
0.7.0

Go
luk
0.6.67

Steps to Reproduce:

Reproduces without extensions: Yes/No

If you mean, to sync preferences between computers, there is a "settings sync" extension for this. The suggestion for vscode is tracked in https://github.com/Microsoft/vscode/issues/33688


Added refresh interval and header text to config

Additional info:
If header text is empty it is taken from locale.

Hi, thx for PR :)
Currently page hangs, probably because there is no default value for refresh interval.
You should add interval to config.example.json too.
2 small fixes and I can merge this :)

I added interval and header to config.json and forgot about config.example.json.
Now it's fixed.

It still take 100% of my one CPU core on start, something is still wrong. I think I need more time to check this.

[src/views/home/index.js, line 22] while (window.config == undefined) {} - page is waiting for config.json and if it not exists page hangs.

That explains a lot.
Even if I have config.json my browser hangs.
Instead of while just set default values.
Someone like me or other person can forget about this file ale think that this project is broken and just use other one. Think more about usability :)

Fixed.

It works!
Awesome :+1:


Tag all code samples for box.dev

Verified that @cbetta has signed the CLA. Thanks for the pull request!

@cbetta The doc files you're modifying are autogenerated, and will be overwritten by the build tools in our next release.  I'm not sure what the best way to insert these comments is — let's sync offline

Ah 💩


[FEATURE REQ] Align with azcopy retry settings (20 attempts)

Library or service name.
All of Azure.Storage
Is your feature request related to a problem? Please describe.
I have ran into timeouts that look like this, trying to upload ~400MB files using slow connections:
System.AggregateException: Retry failed after 6 tries. (Error while copying content to a stream.) (Error while copying content to a stream.) (Error while copying content to a stream.) (Error while copying content to a stream.) (Error while copying content to a stream.) (Error while copying content to a stream.)
 ---> Azure.RequestFailedException: Error while copying content to a stream.
 ---> System.Net.Http.HttpRequestException: Error while copying content to a stream.
 ---> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host..
 ---> System.Net.Sockets.SocketException (10054): An existing connection was forcibly closed by the remote host.

I suspect azcopy has more optimized retry parameters, especially for upload. Looking at their code, the main difference seems to be the retry count of 20 (for uploads):  https://github.com/Azure/azure-storage-azcopy/blob/2c30af330b681d3a1f31db32e11245eafce9c5c3/ste/xfer.go#L36
Compare this to the Azure SDK retry count of 5 (which translates to a total of 6 attempts): https://github.com/Azure/azure-sdk-for-net/blob/00d31be869a010d4b5801726d11bf83f39031248/sdk/storage/Azure.Storage.Common/src/Shared/Constants.cs#L15

Thank you for your feedback.  Tagging and routing to the team best able to assist.

Hi,
I don't think it's right to change the MaxReliabilityRetries for all requests, because we could have other requests coming in that will consistently error out due to other reasons aside from slow connections (e.g. internal error, weird auth errors, throttling etc). So if we had a retry of say 20 and the user decides to do a call like list but runs into the service having internal errors, then they would wait a very long time to get an error back to say that the service isn't ready or available for this request, when they can receive it much quicker.
One solution we could think over is maybe having a different retry amount/policy for upload / download vs. other types of calls.
Another idea is allowing the user to manually set retry policies, but I'm not sure we're able to do that today. @seanmcc-msft is there a way to set the retry policy today or is that currently being worked on somewhere in Core?

Another idea is allowing the user to manually set retry policies, but I'm not sure we're able to do that today. @seanmcc-msft is there a way to set the retry policy today or is that currently being worked on somewhere in Core?

Yes, you can control the retry settings like this:
var serviceClient = new DataLakeServiceClient(serviceUri, credential, new DataLakeClientOptions
{
    Transport = new HttpClientTransport(new HttpClient { Timeout = Timeout.InfiniteTimeSpan }),
    Retry =
    {
        Mode = RetryMode.Exponential,
        NetworkTimeout = Timeout.InfiniteTimeSpan,
        MaxRetries = 19,
        //...
    }
});

One solution we could think over is maybe having a different retry amount/policy for upload / download vs. other types of calls.

This is what azcopy does. The partitioned uploader already sets some upload specific storage transfer defaults when not set specifically by the user (like max block size), perhaps the same could be done for retry: https://github.com/Azure/azure-sdk-for-net/blob/49081317e57fa4b44ac64dce9598e08a6460c9a3/sdk/storage/Azure.Storage.Common/src/Shared/PartitionedUploader.cs#L115

I don't think it's right to change the MaxReliabilityRetries for all requests, because we could have other requests coming in that will consistently error out due to other reasons aside from slow connections (e.g. internal error, weird auth errors, throttling etc). So if we had a retry of say 20 and the user decides to do a call like list but runs into the service having internal errors, then they would wait a very long time to get an error back to say that the service isn't ready or available for this request, when they can receive it much quicker.

The question is, are those failures transient or not? If they are not transient (e.g. auth errors), they should not be retried at all. If they are transient, I guess it's a question of how long it should take to give up. I concede that the answer might depend on the scenario (specifically, upload vs download or even list). But remember that the "user" could (most of the time?) be an automated program where it might be better to retry 20 times than to fail and force manual human intervention (which in the case of transient errors, would be a retry anyway).

If it's an automated program, then maybe the retries should be set to 20 then right? However in the case that a storage account is getting throttled, 503, (i.e. automated program overloading the storage account) then there needs to be a back-off mechanism to kick of to allow the storage account .
Another question to ask is how much of this should be heavily relied on the SDK. The SDK cannot predict the manner of the environment (e.g. VM size, concurrency, size of the blob) as well as external factors such as if the storage account/container/blob is being accessed by other users, region of the storage account, region of the request sent, and if there's any internal errors on the storage side. I think it's best to leave some of these things up to the user to determine rather than have the SDK set the default judgement, only to be incorrect just because of internal and external factors.
That being I'm not sure how open we are to changing the default value, if we don't have any other reasoning aside from this is what azcopy does. We need to ensure that the value being set works on all platforms, blob sizes, environments etc. Sorry if this doesn't help your issue.

If it's an automated program, then maybe the retries should be set to 20 then right? However in the case that a storage account is getting throttled, 503, (i.e. automated program overloading the storage account) then there needs to be a back-off mechanism to kick of to allow the storage account .
Seeing as this is an SDK, the reasonable assumption would be that it's used for automated programs. The default is already exponentials backoff...

Another question to ask is how much of this should be heavily relied on the SDK. The SDK cannot predict the manner of the environment (e.g. VM size, concurrency, size of the blob) as well as external factors such as if the storage account/container/blob is being accessed by other users, region of the storage account, region of the request sent, and if there's any internal errors on the storage side. I think it's best to leave some of these things up to the user to determine rather than have the SDK set the default judgement, only to be incorrect just because of internal and external factors.
I agree but at the end of the day you do have to have some default, which is what I'm suggesting to discuss here. At the very least, you could have different defaults for upload (which is typically >10X slower than download).

That being I'm not sure how open we are to changing the default value, if we don't have any other reasoning aside from this is what azcopy does. We need to ensure that the value being set works on all platforms, blob sizes, environments etc.
That's fair, but perhaps you could discuss it with the azcopy folks? The have similar considerations, and I think a lot of experience - azcopy has been around for many years...


Using headscale instead of tailscale

Hi, I am trying to use this with self-hosted headscale instance. Do you happen to have any information / experience using headscale with this container?
When I run this with headscale, the container restarts and "invalid key: unable to validate API key" can be seen in the logs. I can verify that my API key is correct.

Hi,
No I haven't tried configuring it for use with headscale. Expect it would require some modifications to tailscale.sh, which currently has api.tailscale.com hardwired for API access.
I'll check with the headscale documentation.

Hi,
if you could test out 0.1.17 with your headscale server that would be great. The README has been updated with how to configure for Headscale.


why the default xhr is async?can i set it sync?

why the default xhr is async?can i set it sync?
maybe an async option is better

+1

+1

in /src/http/client/xhr.js it's hard-coded as xhr.open(request.method, _.url(request), true); and I don't know any alternative way to make a xhr request sync except for opening it with a false at 3rd argument.
So maybe you can't turn it to sync for now.
One can set properties to xhr by doing this: Vue.http.get(url, data, params, { xhr: { something} }), the xhr field in options argument will be merged into actual xhr object. But I don't know whether there is a way to make a xhr sync by setting its property.

Duplicate, see #179


change all yum modules to dnf

Is your feature request related to a problem? Please describe.
prepare for move to Cent8 and change all yum modules to dnf
Describe the solution you'd like
Describe alternatives you've considered
Additional context

@j0hnL do we know if the dnf module will fall back to yum? See (#136) for related.

I would suggest to simply use package. That will take care of falling back and also reduces rework if you would liek to support non radhat family OS in future.

Thanks for the suggestion, @jlec!
@j0hnL and @sujit-jadhav: The documentation for package is here: https://docs.ansible.com/ansible/latest/collections/ansible/builtin/package_module.html
This would definitely solve the problem of possibly adding Ubuntu/Debain support. I'm trying to determine if it supports tdnf, as that would enable PhotonOS support (#130).


Makes the load balancer location a variable

Makes the load balancer location a variable and keep hel1 as the default.

Thank you for the PR.
A new module version has been released. https://github.com/wenzel-felix/terraform-hcloud-rke2/releases/tag/v0.5.3

Thank you, @wenzel-felix!


[proposal] Added amazonec2-use-default-network-interface option

Added amazonec2-use-default-network-interface option to skip NetworkInterfaces parameter.

With use default network option, it is possible to use automatic network offered by the provider.

Signed-off-by: Berk Gokden<EMAIL_ADDRESS>This is required for our on-promise cluster to work. I am not sure if it helps anyone other than us. So it would be nice if someone who is using aws could review it.

@nathanleclaire hi, can you look at it when you have time?

@nathanleclaire is there something you need before we can merge this?
@bgokden left our company so he may not need this anymore, but it is still necessary for our ec2 compliant private cloud.
I can help rebasing on master (or merge master into this branch?) to resolve conflicts. I did that already on my local machine, to validate this still works with latest version.


Fix TypeError when calling executable scripts

Maintainer of the AUR packages pypipe and pypipe-git here.
When I tried to adapt pypipe-git to the new hatchling-based workflow, I noticed that running any of the generated executable scripts would result in an error message.
For example:
$ ppp --version
Traceback (most recent call last):
  File "/usr/bin/ppp", line 8, in <module>
    sys.exit(main())
             ^^^^^^
  File "/usr/lib/python3.11/site-packages/pypipe.py", line 836, in main
    if len(argv) == 0 or argv[0] not in expected_1st_args:
       ^^^^^^^^^
TypeError: object of type 'NoneType' has no len()

That error seems to be caused by pip’s shim script calling the main() function without arguments.
This PR fixes this by setting the default value for the argv kwarg to sys.argv[1:] inside the signature of the main function.

After porting this change into the pypipe-git AUR package, I can now confirm that it fixes the issue:
$ ppp --version
pypipe 0.3.0a0

Pinging @diazona, who contributed #8, for visibility.

Oh good catch, thanks for the fix. When I originally started #8, there was not a main() function, and I had created one that takes no arguments. But then I rebased against the changes that are currently on the main branch which added a main() that does take arguments, and I didn't notice the difference. I should have run the test suite (which should be made to catch this if it doesn't already); my mistake!

the test suite (which should be made to catch this if it doesn't already)

Fyi, the pytest suite passed for me when I added the hatch build.
I caught this by installing the package and running it manually.

@claui Thanks! I didn't notice it. I really appreciate that you sent this PR before the PyPI release.
@diazona Sorry, I should have informed you that when adding the tests, an argument was added to the main function.

Oh no, it was my job to notice! I should have been more careful checking the changes when I rebased. (I guess ideally, the automated tests should have caught it... I can submit a PR for that.)

Thanks @bugen and @diazona!

I should have informed you

Oh no, it was my job to notice! I should have

In the German language, a saying goes: „Wo gehobelt wird, fallen Späne“ (literally: “when wood is planed, chips are going to fall off” or figuratively: “you’ve got to crack a few eggs to make an omelette.”)
Thanks to both of you for maintaining this project! The introduction of pyproject.toml and the build system is making my work much easier, especially going forward as the project (hopefully) grows.

@claui  I released v0.3.0.
I am an Arch user, so I'm very happy to see pypipe added to AUR. I never imagined it would happen within a month of releasing pypipe. Thank you so much!


Saner pylint defaults, remove flake8

By default, Visual Studio Code uses a minimal set of pylint checks detailed on https://code.visualstudio.com/docs/python/linting#_default-pylint-rules.
This PR settles on that set plus a check for unused imports and removes flake8; afaics, its checks are covered by pylint anyway.
Implicitly continues https://github.com/googlefonts/fontbakery/issues/838.
Current output:
************* Module fontbakery.utils
E:165, 2: No name 'urlopen' in module 'urllib' (no-name-in-module)
************* Module fontbakery.checkrunner
E: 71,33: Instance of 'Status' has no '__name' member (no-member)
E: 75,11: Instance of 'Status' has no '__name' member (no-member)
E: 79,11: Instance of 'Status' has no '__weight' member (no-member)
W:233, 2: Unused variable 'ex_type' (unused-variable)
W:233,11: Unused variable 'ex' (unused-variable)
W:952, 8: Unused variable 'section_name' (unused-variable)
E:1084,12: Instance of 'TypeError' has no 'format' member (no-member)
W:1148,17: Unused variable 'signature' (unused-variable)
W:1148,28: Unused variable 'scope' (unused-variable)
************* Module fontbakery.specifications.general
E: 86,15: Module 'plistlib' has no 'readPlistFromString' member (no-member)
************* Module fontbakery.specifications.googlefonts
W:255, 2: Unused variable 'file_path' (unused-variable)
E:315,17: Instance of 'LookupDict' has no 'ok' member (no-member)
W:633, 6: Unused variable 'i' (unused-variable)
E:1379,11: Instance of 'FamilyProto' has no 'fonts' member (no-member)
W:2317, 4: Unused variable 'warn' (unused-variable)
************* Module fontbakery.commands.check_specification
W:182,10: Unused variable 'unknown' (unused-variable)
************* Module fontbakery.reporters.terminal
W:212,12: Unused variable 'message' (unused-variable)
W:212,21: Unused variable 'identity' (unused-variable)
W:230,22: Unused variable 'section' (unused-variable)
W:230,31: Unused variable 'check' (unused-variable)
W:230,38: Unused variable 'iterargs' (unused-variable)
W:325, 4: Unused variable 'rows' (unused-variable)
W:398,22: Unused variable 'section' (unused-variable)
W:498,14: Unused variable 'check' (unused-variable)
W:498,21: Unused variable 'iterargs' (unused-variable)
W:528, 4: Unused variable 'status' (unused-variable)
W:528,12: Unused variable 'message' (unused-variable)
W:528,22: Unused variable 'section' (unused-variable)
W:528,31: Unused variable 'check' (unused-variable)
W:528,38: Unused variable 'iterargs' (unused-variable)
************* Module fontbakery.reporters
W: 86,21: Unused variable 'identity' (unused-variable)
W:106,21: Unused variable 'identity' (unused-variable)
************* Module fontbakery.reporters.serialize
W: 49, 4: Unused variable 'section' (unused-variable)
W: 49,13: Unused variable 'check' (unused-variable)
W: 49,20: Unused variable 'iterargs' (unused-variable)
W: 58, 4: Unused variable 'section' (unused-variable)
W:118, 4: Unused variable 'sectionorder' (unused-variable)

------------------------------------------------------------------
Your code has been rated at 9.83/10 (previous run: 9.83/10, +0.00)

Heh, this is amusing: pylint comes with some extra checkers
$ pylint --load-plugins=pylint.extensions.bad_builtin,pylint.extensions.check_elif,pylint.extensions.comparetozero --disable=all --enable=bad-builtin,compare-to-zero,else-if-used Lib/fontbakery
Using config file /home/nikolaus/Entwicklung/fontbakery/.pylintrc
************* Module fontbakery.callable
C:244,24: Avoid comparisons to zero (compare-to-zero)
************* Module fontbakery.utils
W: 21,39: Used builtin function 'map'. Using a list comprehension can be clearer. (bad-builtin)
W: 63,14: Used builtin function 'map'. Using a list comprehension can be clearer. (bad-builtin)
************* Module fontbakery.checkrunner
C:1317,19: Avoid comparisons to zero (compare-to-zero)
C:1345,26: Avoid comparisons to zero (compare-to-zero)
************* Module fontbakery.specifications.name
C:138, 7: Avoid comparisons to zero (compare-to-zero)
C:201, 5: Avoid comparisons to zero (compare-to-zero)
C:205, 7: Avoid comparisons to zero (compare-to-zero)
C:321, 7: Avoid comparisons to zero (compare-to-zero)
C:348, 5: Avoid comparisons to zero (compare-to-zero)
************* Module fontbakery.specifications.gdef
C: 42,33: Avoid comparisons to zero (compare-to-zero)
************* Module fontbakery.specifications.general
C:212, 5: Avoid comparisons to zero (compare-to-zero)
C:353,26: Avoid comparisons to zero (compare-to-zero)
C:355, 9: Avoid comparisons to zero (compare-to-zero)
C:443, 7: Avoid comparisons to zero (compare-to-zero)
C:469, 9: Avoid comparisons to zero (compare-to-zero)
C:553, 5: Avoid comparisons to zero (compare-to-zero)
C:579, 7: Avoid comparisons to zero (compare-to-zero)
C:619, 7: Avoid comparisons to zero (compare-to-zero)
************* Module fontbakery.specifications.head
R:101, 8: Consider using "elif" instead of "else if" (else-if-used)
************* Module fontbakery.specifications.prep
R: 36, 4: Consider using "elif" instead of "else if" (else-if-used)
************* Module fontbakery.specifications.hhea
C: 17, 5: Avoid comparisons to zero (compare-to-zero)
C: 19, 7: Avoid comparisons to zero (compare-to-zero)
C: 66, 7: Avoid comparisons to zero (compare-to-zero)
C: 69, 5: Avoid comparisons to zero (compare-to-zero)
************* Module fontbakery.specifications.fvar
C: 81, 5: Avoid comparisons to zero (compare-to-zero)
C:106, 5: Avoid comparisons to zero (compare-to-zero)
************* Module fontbakery.specifications.googlefonts
C:324, 5: Avoid comparisons to zero (compare-to-zero)
C:483, 5: Avoid comparisons to zero (compare-to-zero)
R:737, 6: Consider using "elif" instead of "else if" (else-if-used)
C:802, 5: Avoid comparisons to zero (compare-to-zero)
C:854, 5: Avoid comparisons to zero (compare-to-zero)
C:905, 5: Avoid comparisons to zero (compare-to-zero)
C:1028, 5: Avoid comparisons to zero (compare-to-zero)
C:1105, 5: Avoid comparisons to zero (compare-to-zero)
C:1359, 5: Avoid comparisons to zero (compare-to-zero)
C:1396, 5: Avoid comparisons to zero (compare-to-zero)
R:1401, 4: Consider using "elif" instead of "else if" (else-if-used)
C:1424, 5: Avoid comparisons to zero (compare-to-zero)
C:1455, 5: Avoid comparisons to zero (compare-to-zero)
C:1494, 5: Avoid comparisons to zero (compare-to-zero)
C:1793, 7: Avoid comparisons to zero (compare-to-zero)
C:1835, 7: Avoid comparisons to zero (compare-to-zero)
C:1835,36: Avoid comparisons to zero (compare-to-zero)
C:1955, 5: Avoid comparisons to zero (compare-to-zero)
R:2079, 4: Consider using "elif" instead of "else if" (else-if-used)
C:2379, 5: Avoid comparisons to zero (compare-to-zero)
C:2392, 7: Avoid comparisons to zero (compare-to-zero)
R:2397, 4: Consider using "elif" instead of "else if" (else-if-used)
C:2397, 7: Avoid comparisons to zero (compare-to-zero)
C:2482, 7: Avoid comparisons to zero (compare-to-zero)
C:2638, 7: Avoid comparisons to zero (compare-to-zero)
R:2724,10: Consider using "elif" instead of "else if" (else-if-used)
************* Module fontbakery.specifications.os2
C: 91, 9: Avoid comparisons to zero (compare-to-zero)
C: 94, 7: Avoid comparisons to zero (compare-to-zero)
************* Module fontbakery.reporters.terminal
C:151,49: Avoid comparisons to zero (compare-to-zero)
C:247,18: Avoid comparisons to zero (compare-to-zero)
C:510,31: Avoid comparisons to zero (compare-to-zero)
************* Module fontbakery.reporters
W: 77,29: Used builtin function 'map'. Using a list comprehension can be clearer. (bad-builtin)

Potentially also interesting: https://pylint.readthedocs.io/en/latest/technical_reference/extensions.html#parameter-documentation-checker

Regarding 32439a1 Do you want to participate in a code obfuscation contest? I think it can be very helpful to read code when you actually know what else is in the element you are unpacking. It's documentation.

actually, this is about all replace unused variables with _ commits. Please explain how this is useful, despite of making pylint happy.

The primary reason is to make it explicit that you only use specific variables. I was actually thinking that e.g. event might better be a named tuple or something, so you don't need unpacking at all.

I strongly disagree on picking up an arbitrary list of lint-checks just because Microsoft does so.
We already had our black-list of things we don't want to fix for now and it was good enough as it allowed us to gradually either introduce new lint-checks (by removing them form the maybe-later list) or declare that we have a strong reason not to fix them by adding them to the wont-fix list.
Let's not waste time on this. I won't merge d62d874084b2aa9c981eee666b1211efbd673c8f
Having said that, I am ok with removing flake8 (we had already done it in the past, by the way).

To be clear, I did not intend to sound rude in my previous message. For our past endeavors on code-testing please take a look at this other thread from a couple years ago: https://github.com/googlefonts/fontbakery/issues/838

If you bring back the whitelist (maybe-later) and blacklist (wont-fix) I can gladly review the rest of your proposed code changes.

Counter-proposal: no flake8, pylint with --disable=all --enable=F,E (for "fatal" and "error", should cover what flake8 is looking for). That way, we get just potential bugs and can add to the list at a later date.

Bring back the explicit lists we had, please. ;-)

In principle, I like to have the wont-fix and maybe-later explicit linter-check lists.
Even though I see that there is some other work done here, I feel like I should close this PR now because it is not clear if the code changes are only necessary to address this new minimal selection of lint-checks mimicking Visual Studio behaviour or if they have other purposes.
If you think there are code changes here that you really want to get into master, please consider opening another pull request which keeps the explicit lists in place and only addresses linter-errors/warns that are actually enabled in them.
It is probably OK if you decide to enable more lint-checks (by editing the maybe-later list) as long as we agree they are reasonable ones (i.e. they really help us improve quality and readability).


Refmt preserving spaces in modules.

I'm not sure if the style that the reason team landed on was to not preserve spaces within module and module type, if so then disregard this issue.
An example is:
my code:
module type Example = {
  let example0: someArg0::string => string;

  let example1: someArg1::string => string;

  let example2: someArg2::string => string;
}

gets turned into:
module type Example = {
  let example0: someArg0::string => string;
  let example1: someArg1::string => string;
  let example2: someArg2::string => string;
};

Same thing happens with module:
my code:
module Example = {
  let example0 someArg0 => "0";

  let example1 someArg1 => "1";

  let example2 someArg2 => "2";
};

gets turned into:
module Example = {
  let example0 someArg0 => "0";
  let example1 someArg1 => "1";
  let example2 someArg2 => "2";
};

Now imagine if the functions weren't one liners and mixed with other values aside from functions. This gets very hard to read and sometimes you skip a line reading code or it's hard to tell where something may have ended. Not to take a shot at the regl codebase or anything but when reading it I confused often when a functions was indeed over. These spaces are helpful in showing what may be one unit or feature. Also makes me as a programmer psychologically more at ease when I see spaces. But maybe I'm just being stupid over these spaces.

this may not be exclusive to modules but this is where i've noticed spaces not being preserved.

IIRC @IwanKaramazow was working on some automatic grouping/spacing changes for refmt which should address this.

Yes the core is ready, need to fix some issues with comments.
It'll group things of the same type & breaks if it's spreaded over multiple lines.
module Something = {
    type a = int;
    type b = string;

    let x = 1;
    let y = "test";

    let render {props, state} => {
        /* same type, e.g. a `let`, but has newline above for readability */
        let () = Lwt_main.run (something ());
        <div> props.x state.y </div>
    }
}

Whitespace will still be killed in the above example, because it's to short of a unit.
If let example3 consists of multiple lines, it'll get a newline above
module Example = {
  let example0 someArg0 => "0";
  let example1 someArg1 => "1";
  let example2 someArg2 => "2";

 let example3 () => {
     let a = 1;
     let b = 2;
     a + b
 };
};

That definitely looks like an improvement. That ending part where items that break get extra lines above them. Did someone specify that in a task, or did you intentionally/accidentally add it? It's interesting. I think it would work.
Someone else also suggested preserving additional newlines (any time you have n >= 1 blank lines, preserve and collapse to one line).

I just recently discovered Reason and have been browsing some public Reason projects.  I'm having a hard time getting over the lack of newlines that are usually used to separate ideas or blocks of code.  It makes understanding the code (and a new language) slightly more overwhelming than it needs to be.
Here's a sample before and after using refmt (Reason 2.0.0 @ 84e87c4):  https://gist.github.com/rostero1/efa9dca43254380af28d9ab7eb4152b2

I'm also having a hard time dealing with being given no choice over structuring and grouping my code. For example, having a lot of big functions in a let rec ... and ... and ... block becomes almost unreadable.

Someone else also suggested preserving additional newlines (any time you have n >= 1 blank lines, preserve and collapse to one line).

this would be perfect, imo. Agree with others that refmt removing newlines makes it a bit harder to navigate and read code

Someone else also suggested preserving additional newlines (any time you have n >= 1 blank lines, preserve and collapse to one line).

💯
This is prettier behavior and it works great imo.

Fixed =)


Commit the recent joke at the top

No need to scroll to the bottom to see the joke if it gets committed at the top 👆

Thanks @deepakr-28 🙌


Bug fixes and support for indicator LEDs

add reconnect logic
restart service if missing PN532 modules
blink LEDs when cards are present

cleanup to come later


Abstract the disk/lvol file operations in restore functions

https://github.com/longhorn/longhorn/issues/6576

cc @innobead


Add responsiveness to the site #36

Now: No horizontal slider

Before: There was a horizontal slider

@harshit1142 the navbar looks out of context from the side, leaving some spaces. could you fix that.

@Neel-07  let me try

@Neel-07  Yes,got

@Neel-07

Please Add hacktoberfest label if possible.


Question: Can i preload a webview in headless mode and then attach to InAppWebview Widget

this question may sound silly but this is what I'm looking for, my app uses webviews to show most of the features that my website has until i can build them in Flutter.
But the issue is webviews are slow and also my website need cookies to be set.
So is there a way i can preload a webview when app starts up and show it when required ?

You can use for example the Stack widget or IndexedStack widget and, then, show the InAppWebView widget child when you need it.


data-ajax--url how display text with json

result:
[{"id":"1","value":"1","label":"YES","description":null,"sort":null,"parentId":null,"type":null},{"id":“2”,"value":"2","label":"NO","description":null,"sort":null,"parentId":null,"type":null}]
How to show it as

 YES
 NO

customformater for data, they have an example in examples

Sounds like you are looking for either templateResult or templateSelection.


fix issue #1007 - [closed]

In GitLab by @tmon546596046 on Mar 19, 2018, 08:12
Merges grafanafix -> dev
now the pods and containers panel show total pods/containers instead of running ones.

In GitLab by @wknet123 on Nov 13, 2019, 10:40
the API Server Coverage is  19.8%   UI Coverage is 38.11%   check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:40
the it is failed check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:40
closed


slices: add Reduce function

I propose a small, trivial addition to the slices package.
func Reduce[S ~[]E, E any, T any](s S, f func(T, E) T, init T) T {
	for _, v := range s {
		init = f(init, v)
	}
	return init
}

I often use similar func in other languages (js, PHP) and I think it'll be useful for GO as well.
I'm happy to contribute a PR with tests if this is a good idea.

Duplicate of #61898


Add tests when prob_mutation is not specified

Fix #70

When using estimate_mutation_probability, a pathological case happened when the number of ref. haplotypes is 2 when running test_ts_simple_n6, because four haplotypes (which are then used as queries) are excluded from the simulated ref. panel. See #108

A temporary workaround is to not exclude the haplotypes chosen as queries from the ref. panel used downstream. The proper way is to rework get_examples* so that no haplotypes are excluded from the simulated ref. panel but the query haplotypes are randomly mutated copies of some of the haplotypes in the ref. panel. This will be addressed in a separate issue.


Use this package and sleeping-owl/admin

I can't use this package together with sleeping-owl/admin because Admin Display classes (e.g. table) does not have include method, am I missing something or I have to write a new Admin Display class?
Thanks,
Carlo

Solution is just use
Model::with('other')


Access site.data in a module template?

As far as I can tell, we have access to site.data from pages (e.g., src/page_name/index.nunjucks), but not modules (e.g., _modules/link/link.nunjucks).  Is there a way to access site.data from a module?
Thank you.

Hey @saun4app,
While you can't access site.data within a nunjucks/jade module directly, you can pass the data to the module if you would like. Here is an example:
{{link.content({
    href: 'https://github.com/larsonjj/generator-yeogurt#yeogurt-generator---',
    text: 'documentation',
    site: site
})}}


can u add this ? it looks so nice for Mac Screen Saver

Perfect Balance Circles
The circles will be perfectly synchronized after about 30 m.
The Program is made by Pezzza's Work and all credit goes to him.
His YT Channel: https://www.youtube.com/channel/UCFR-QlAx0qFHN9-QmcrpHnQ/
Pezzza's Work GitHub: https://github.com/johnBuffer/NoCol
wallpaper engine:https://steamcommunity.com/sharedfiles/filedetails/?id=2446231725
it looks so nice . it is perfected mac screen saver

@nonfxck
This does look really good, but I'm not sure that would fit in Aerial, I don't see that looking good on top of a video for example.
It may be a good idea for an alternate, standalone, screensaver though ?

@nonfxck
This does look really good, but I'm not sure that would fit in Aerial, I don't see that looking good on top of a video for example.
It may be a good idea for an alternate, standalone, screensaver though ?

ya, I don't think it will fit in aerial well too
but as u say, it is a good standalone screensaver


[google_maps_flutter_web] show only single infoWindow

Description
Currently google_maps_flutter_web shows multiple infoWindow . This PR will make it show only single infoWindow.
Related Issues
Fixes flutter/flutter#67380
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[X] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[X] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
[X] All existing and new tests are passing.
[X] I updated/added relevant documentation (doc comments with ///).
[X] The analyzer (flutter analyze) does not report any problems on my PR.
[X] I read and followed the Flutter Style Guide.
[X] The title of the PR starts with the name of the plugin surrounded by square brackets, e.g. [shared_preferences]
[X] I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy.
[X] I updated CHANGELOG.md to add a description of the change.
[X] I signed the CLA.
[X] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?

[X] No, this is not a breaking change.

@ditman can you please review this.

I'll merge this once the tree goes green again (I updated the changelog and the test slightly, to be more compliant with the changes I've been making lately). Thanks for your contribution again, @balvinderz!

Forgot to mention here that this is published as google_maps_flutter_web: ^0.1.0+6!


Be able to update billing information and contact

Hello,
Could you please add the option to add/update the billing information (billing_address, billing_email_address and tech_email_address, etc..) of a Aiven project
Thank you in advance,
Benjamin

Hello, isn't this already possible?
Example:
resource "aiven_project" "project" {
  project         = var.project_name
  account_id      = var.account_id
  billing_address = <<EOT
    MyCompany
    Address1
    Address2
    EOT
  billing_emails = [
<EMAIL_ADDRESS><EMAIL_ADDRESS>  ]
  country_code = "SE"
  technical_emails = [
<EMAIL_ADDRESS><EMAIL_ADDRESS>  ]
}

@arvidviderberg indeed billing_address, billing_email_address and tech_email_address fields are already available and we will add support for billing_extra_text, billing_currency soon.

Hum nice, i will try to do it, it's not explain in the documentation i think
I have tried to do with the python Aiven CLI https://github.com/aiven/aiven-client, but it was not available
Thank you guys

Recently we have added support to aiven_billing_group resource, which can be associated with the project, please use it to set all billing-related information for a project.


Error: spawn C:..\node_modules\esbuild\esbuild.exe ENOENT

Describe the bug
npm run build error
System Info

vite version: 2.0.0-beta.5
Operating System: Windows 10
Node version: v15.5.1
Optional:

npm version: 7.0.9

Logs (Optional if provided reproduction)
$ npm run build --debug

><EMAIL_ADDRESS>build
> vite build && mv ../public/_admin/index.html ../resources/views/admin.blade.php

building for production...
node:events:353
      throw er; // Unhandled 'error' event
      ^

Error: spawn C:\Users\Administrator\code\lykee\admin\node_modules\esbuild\esbuild.exe ENOENT
    at Process.ChildProcess._handle.onexit (node:internal/child_process:276:19)
    at onErrorNT (node:internal/child_process:476:16)
    at processTicksAndRejections (node:internal/process/task_queues:80:21)
Emitted 'error' event on ChildProcess instance at:
    at Process.ChildProcess._handle.onexit (node:internal/child_process:282:12)
    at onErrorNT (node:internal/child_process:476:16)
    at processTicksAndRejections (node:internal/process/task_queues:80:21) {
  errno: -4058,
  code: 'ENOENT',
  syscall: 'spawn C:\\Users\\Administrator\\code\\lykee\\admin\\node_modules\\esbuild\\esbuild.exe',
  path: 'C:\\Users\\Administrator\\code\\lykee\\admin\\node_modules\\esbuild\\esbuild.exe',
  spawnargs: [ '--service=0.8.29' ]
}
npm ERR! code 1
npm ERR! path C:\Users\Administrator\code\lykee\admin
npm ERR! command failed
npm ERR! command C:\WINDOWS\system32\cmd.exe /d /s /c "vite build && mv ../public/_admin/index.html ../resources/views/admin.blade.php"

npm ERR!      C:\Users\Administrator\AppData\Local\npm-cache\_logs\2021-01-05T06_28_01_397Z-debug.log

I know how to fix it. Run: node ./node_modules/esbuild/install.js.
This should be written in package.json, but the custom package.json does not have this sentence, so you can run it manually.

I know how to fix it. Run: node ./node_modules/esbuild/install.js.
This should be written in package.json, but the custom package.json does not have this sentence, so you can run it manually.

Check npm config get ignore-scripts. Your npm config seems to ignore esbuild's postinstall hook.

Check npm config get ignore-scripts. Your npm config seems to ignore esbuild's postinstall hook.

Check npm config get ignore-scripts. Your npm config seems to ignore esbuild's postinstall hook.
If that's not the problem, try installing esbuild directly in a fresh project - if that doesn't work also, then it's a esbuild bug and should be reported to esbuild instead.

npm config get ignore-scripts returns false. manually run esbuild/install.js can fix the problem indeed. why it's ignored since the ignore-scripts is empty?

It turns out npm v7 has a bug that corrupts package-lock.json files: https://github.com/npm/cli/issues/2606. When this happens, packages like esbuild with post install scripts can break. You may be experiencing this bug. A workaround is to delete and recreate your package-lock.json file.

I know how to fix it. Run: node ./node_modules/esbuild/install.js.
This should be written in package.json, but the custom package.json does not have this sentence, so you can run it manually.

yes，this is right

I had this exact error but for a different reason. I was on a machine with App Locker enable and it prevented the execution of esbuild.exe.

just run npm run esbuild that's all

Just run npm install esbuild that's all

Check npm config get ignore-scripts. Your npm config seems to ignore esbuild's postinstall hook.
If that's not the problem, try installing esbuild directly in a fresh project - if that doesn't work also, then it's a esbuild bug and should be reported to esbuild instead.

这个bug居然还在 不应该呀尤大

It turns out npm v7 has a bug that corrupts package-lock.json files: npm/cli#2606. When this happens, packages like esbuild with post install scripts can break. You may be experiencing this bug. A workaround is to delete and recreate your package-lock.json file.

it works for me!

I know how to fix it. Run: node ./node_modules/esbuild/install.js.
This should be written in package.json, but the custom package.json does not have this sentence, so you can run it manually.

EL HOMBRE!

I know how to fix it. Run: node ./node_modules/esbuild/install.js.
This should be written in package.json, but the custom package.json does not have this sentence, so you can run it manually.

it worked!

这个是vite的bug还是npm的bug

package-lock.json中"node_modules/esbuild"缺少"hasInstallScript": true。
这个是npm生成packag-lock.json时出错了吗？还是说需要自己进行配置

node ./node_modules/esbuild/install.js

package-lock.json 中 "node_modules/esbuild" 缺少 "hasInstallScript": true , 所以esbuild的install.js没有运行生成esbuild.exe
这个是npm生成packag-lock.json时出错了吗？还是说需要自己进行配置

node ./node_modules/esbuild/install.js 为啥我运行这一句也不行了呢？？呃

相同的问, 需要执行node ./node_modules/esbuild/install.js
所以这不是BUG吗  不修一下吗

Just run npm install esbuild that's all

it works for me


docs: update welcom fragments & readme

:white_check_mark: Build TheIdServer 7.2.3-feat-saml2p1-0047 completed (commit https://github.com/Aguafrommars/TheIdServer/commit/9b4b6e6bce by @)


Remove vue-server-renderer as a peer dependency

What problem does this feature solve?
renderToString was added in beta.12 , which uses vue-server-renderer.
I don't expect many users will call this method, as it's intended use is for testing server side code. Adding it as a peer dependency will warn users that they need to install it, even though they probably won't use the renderToString method.
What does the proposed API look like?

Remove vue-server-renderer as a peer dependency and handle it ourselves, using something like ensureRequire—https://github.com/vuejs/vue-jest/blob/master/lib/compilers/haml-compiler.js#L6. Users will still need to add additional config to webpack, because webpack will try to bundle native node modules in vue-server-renderer.
Split @vue/test-utils, and @vue/server-test-utils. @vue/test-utils will expose mount and shallow, @vue/server-test-utils will expose renderToString.

Seems reasonable to me.

This breaks compatibility with tests that utilize webpack, too. For example with mocha-webpack:

@timoschwarzer A temporary workaround is to add this to your webpack config:
{
  node: {
    fs: 'empty'
  }
}

See https://github.com/webpack-contrib/css-loader/issues/447
This isn't a great solution, and we shouldn't force users to add extra config.
We could split vue-test-utils into two packages, vue-test-utils and vue-test-utils-server 🤔

I thought about this a bit more. Is there any merit to removing/splitting?

It would mean people could bundle with webpack without having to add extra config, and it would solve the peer dependency issue

Can't people bundle with webpack either way? Maybe I don't fully understand this part.
Considering both packages are maintained by the Vue core team, is it so bad to have a peer dependency? I understand it's better not to have them, though.

vue-server-renderer uses node modules, like path and fs.
To bundle these with webpack and run in node you need to add target:node to your config.
If you want to bundle to run tests in the browser (like with karma), you need to tell webpack not to bundle the native node modules vue-server-renderer uses (like path and fs).
This extra config makes it more difficult to set up webpack to compile tests for either node or the browser.
I don't think renderToString will be used by most users. It has only been requested as a feature recently. So we're making the setup for tests more difficult to support a few users.
Instead, we could turn vue-test-utils into a monorepo that generates two packages. @vue/test-utils, and @vue/server-test-utils. @vue/test-utils will expose mount and shallow, server-test-utils will expose renderToString.
That way, most users can carry on bundling their tests with webpack, without additional config. Any users who want to test SSR could download @vue/server-test-utils.

Ok, I understand now. Thanks for that explanation.
In light of this, your proposal seems best.

I'm working on converting the repo into a monorepo this week. I'd appreciate feedback on the structure once I've finished 😄

I am facing the same problem as @timoschwarzer using 1.0.0-beta.12

Even when you include vue-server-renderer and target: 'node' (or resolve node.fs and node.module to "empty") this workaround still shows CriticalDependencyErrors and is pretty annoying. The tests seem to work but you'll always be getting "red" tests because of the peer dependency is using fake target node environment. Please split these apart into packages that we can use for client side and server side like @eddyerburgh recommended.

@kdocki It's been split into seperate packages. We'll release soon

I am getting these errors. Are they related?

WARNING in ./node_modules/jsdom/lib/jsdom/utils.js
203:21-40 Critical dependency: the request of a dependency is an expression
 @ ./node_modules/jsdom/lib/jsdom/utils.js
 @ ./node_modules/jsdom/lib/jsdom/living/node-filter.js
 @ ./node_modules/jsdom/lib/jsdom/living/index.js
 @ ./node_modules/jsdom/lib/jsdom/browser/Window.js
 @ ./node_modules/jsdom/lib/api.js
 @ ./node_modules/jsdom-global/index.js
 @ ./test/unit/setup.js

WARNING in ./node_modules/parse5/lib/index.js
55:23-49 Critical dependency: the request of a dependency is an expression
 @ ./node_modules/parse5/lib/index.js
 @ ./node_modules/jsdom/lib/jsdom/browser/htmltodom.js
 @ ./node_modules/jsdom/lib/jsdom/living/nodes/Document-impl.js
 @ ./node_modules/jsdom/lib/jsdom/living/generated/Document.js
 @ ./node_modules/jsdom/lib/jsdom/living/domparsing/DOMParser-impl.js
 @ ./node_modules/jsdom/lib/jsdom/living/generated/DOMParser.js
 @ ./node_modules/jsdom/lib/jsdom/living/index.js
 @ ./node_modules/jsdom/lib/jsdom/browser/Window.js
 @ ./node_modules/jsdom/lib/api.js
 @ ./node_modules/jsdom-global/index.js
 @ ./test/unit/setup.js

WARNING in<EMAIL_ADDRESS>Module not found: Error: Can't resolve 'vue-server-renderer' in '/Users/katsanos/frontend/node_modules/@vue/test-utils/dist'
<EMAIL_ADDRESS>4706:15-45
 @ ./src/components/geofences/create/create.test.js
 @ ./src ^\.\/(?!main).+(\.js)$
 @ ./test/unit/index.js

ERROR in ./node_modules/sntp/lib/index.js
Module not found: Error: Can't resolve 'dns' in '/Users/katsanos/frontend/node_modules/sntp/lib'
 @ ./node_modules/sntp/lib/index.js 6:12-26
 @ ./node_modules/hawk/lib/index.js
 @ ./node_modules/request/request.js
 @ ./node_modules/request/index.js
 @ ./node_modules/request-promise-native/lib/rp.js
 @ ./node_modules/jsdom/lib/api.js
 @ ./node_modules/jsdom-global/index.js
 @ ./test/unit/setup.js

This has been removed in beta-13.
@vue/server-test-utils is now in its own package.

@eddyerburgh  do I need the server-test-utils if I dont do snapshot/dont use Jest?

No, server-test-utils is only useful for testing SSR code.

Yeah! Finally, thanks @eddyerburgh and your team

If like me you want renderToString to work on a client side rendered app (or you use another server than node). I couldn't get around the critical dependency error even after trying everything in this thread. Using mount was a pain because it didn't seem to recognise mocks on window or global.
This is how I got it to work:
Move all the SSR code into something like ssr-testing.js, import renderToString there, and ignore that file and your unit tests from webpack.
In webpack update your babel loaders regex to something like:
/^(?!(.*\.spec)|(ssr-testing)).*\.js$/
That way webpack will ignore the SSR stuff.


Create OpenSource : 3. Blog what you do and be more social

Description 📜
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context.
Fixes #32

Type of change 📝

[ ] Audio (Should be in mp3 format Includes speech clarity, Concise ,Low distortion)
[ ] Video (Animations, screen-recordings, presentations and regular explanatory films are all possibilties etc)
[x] Documentation (Content Creation in the form of codes or tutorials)
[ ] Other (If you choose other, Please mention changes below)

Domain of Contribution 📊

[ ] Android Dev (Flutter, Java, Kotlin)
[ ] Backend Dev (Java, .NET, Python)
[ ] C/CPP
[ ] Competitive Programming
[ ] Cyber Security
[ ] DSA
[ ] Database
[ ] Datascience with Python
[ ] Datascience with R
[ ] Frontend Dev (HTML, CSS, JS)
[ ] Frontend Dev (React, Angular, Vue)
[ ] Golang
[ ] Interview Prep
[ ] Java
[ ] JavaScript
[ ] MERN
[ ] Machine Learning
[x] Open Source
[ ] Python
[ ] Rust
[ ] Statistics
[ ] UI/UX

Checklist ✅

[x] I follow Contributing Guidelines & Code of conduct of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I'm GWOC'21 contributor

Screenshots / Gif (Optional) 📸

@Ash-KODES  Some changes: 👇

Add extension .md to your file
Add` images, flowcharts, graphs to explain what you did
Once you are done with the above changes, Let me know 😉

@Ash-KODES Some changes: 👇

Add extension .md to your file
Add images, flowcharts, graphs to explain what you did
Once you are done with the above changes, Let me know 😉

ok

@Ash-KODES Any updates ??

@Ash-KODES Any updates ??

ya i am on it!

@Aryamanz29 I have made a new pr please review it

Closing this PR , Since same one already been  merged


Add Mysterious Projects: Dr. Lirius Rover from Kerbal Stuff

This pull request was automatically generated by Kerbal Stuff on behalf of nazari, to add Mysterious Projects: Dr. Lirius Rover to CKAN.
Please direct questions about this pull request to nazari.

Closed by https://github.com/KSP-CKAN/NetKAN/pull/2467


Add a std::future/std::promise to send I/O options to tlIO

Currently, there's some modules that would benefit from a mechanism to send a std::map<std::string, std::string> (ioOptions?) of options to tlIO.  For example, the USD reader has all sets of parameters to control its visualization that now are sent only on start up.  Changing them means re-loading the file to take effect.
Any thoughts on this, Darby?

This could be useful though there may be some options that only apply when opening the file, I guess they could either be ignored or the file closed and re-opened. Maybe in addition to passing the options to the constructor they could also be passed to the readVideo and readAudio functions.
However I just realized there is a bug with the options, the I/O cache does not take them into account which means they will be ignored if the requested image is already in the cache. I need to fix this first...

I fixed the bug with the cache and added the option arguments to readVideo and readAudio. Note the options passed to those functions are merged with the options passed when constructing the reader. Currently only the USD plugin is using the new functionality, I added some UI to "tlplay-gl" and "tlplay-qt" for testing it out and it seems to be working OK:

I also added this to mrv2.  You are also using the options in the EXR reader to read the layer.


JSON parse error

Adapter version
1.1.2
JS-Controller version
5.0.12
Node version
18.17.1
Operating System type
Linux
Operating system version
Debian Bullseye
Describe the bug
I am constantly getting this error:
`

eusec.0
2023-10-10 11:31:50.463
error
JSON  parse error [{"error":{"message":"SyntaxError: Unexpected end of JSON  input","stacktrace":"SyntaxError: Unexpected end of JSON input\n    at  JSON.parse ()\n    at parseJSON  (/opt/iobroker/node_modules/eufy-security-client/build/utils.js:154:21)\n     at ParameterHelper.readValue  (/opt/iobroker/node_modules/eufy-security-client/build/http/parameter.js:50:63)\n     at BatteryDoorbellCamera.updateRawProperty  (/opt/iobroker/node_modules/eufy-security-client/build/http/device.js:127:57)\n     at  /opt/iobroker/node_modules/eufy-security-client/build/http/device.js:54:22\n     at Array.forEach ()\n    at  BatteryDoorbellCamera.update  (/opt/iobroker/node_modules/eufy-security-client/build/http/device.js:53:35)\n     at EufySecurity.updateDevice  (/opt/iobroker/node_modules/eufy-security-client/build/eufysecurity.js:344:44)\n     at EufySecurity.handleDevices  (/opt/iobroker/node_modules/eufy-security-client/build/eufysecurity.js:560:22)\n     at HTTPApi.  (/opt/iobroker/node_modules/eufy-security-client/build/eufysecurity.js:167:50)"},"data":"{"r"}]

`
To reproduce

Go to '...'
Click on '...'
Scroll down to '....'
See error

Screenshots & Logfiles
No response
Additional context
No response

It is not a bug.
You can find the explanation here.
Will only be displayed in debug mode in the next version.


Introduce debug flag in chart-verifier

chart-verifier currently slurps output messages that have been
streamed to Stdout by default in chart-testing, but we would like to
instead stream those to Stderr when the --debug flag is passed.

@mmulholla  I believe this can be closed as well. The debug flag exists in the chart-verifier today.


Setting load balancer IP field in service after IP acquisition.

Closes #31.

Works like a charm. But the resource manager indeed patches away the field. But still better than before + will be fixed in the future.

Related gardener-resource-manager PR: https://github.com/gardener/gardener-resource-manager/pull/108


README.md still includes ai features and G checker, also has censored G's

suggested README.md
h-bot10000
a reddit bot that does lots of shit
features

h
more h

extremely detailed how-to guide

go to https://old.reddit.com/prefs/apps
scroll to the bottom and click "are you a developer? create a new app"
set the bot type to script and set the name to whatever you want
create the app
write down the client id (the long string of text underneath the bots name and type), and the bot secret
download this bot by using git or by downloading the zip file
in the bot's code's folder, make a file called .env and make this the contents:

SECRET=(your secret in quotation marks)
ID=(your client id in quotation marks)
USERNAME=(your account's username in quotation marks)
PASSWORD=(your account's password in quotation marks)

install python if not installed, and then open up command prompt for windows or terminal for mac and run

pip3 install poetry==1.5.1
poetry install
poetry run python3 default.py & poetry run python3 additions.py

if it is successful, the terminal should show successfully connected to reddit. you can press ctrl c to stop the bot at any time.
if you do not plan on deploying the bot to https://fly.io/, then you can delete the .dockerignore, swapenable.sh and fly.toml files. otherwise, you can just run the command

fly deploy

to deploy the bot to https://fly.io/.

sned a pr

https://github.com/hcorporation/h-bot10000/pull/4

closed with #4