Optional variables in requests

I studied the file td_api.tl. I discovered several issues with the file format.
When describing the variables of functions, it's not always clear which ones are mandatory and which ones are optional. In some cases, the annotation "pass null" is used for a variable, which likely indicates that this variable can be considered optional. However, for some optional variables, this phrase is not mentioned. For example, take the getChatHistory function. The request works fine without specifying from_message_id, offset, or only_local. But from the function description, it is unclear exactly which variables are optional. It's also not clear whether default values are used for any of these variables.
As for types, it seems somewhat clearer, as comments like "may be null" are provided. However, I'm not sure whether this covers all cases where a variable can be null.
Could you generate a new version of td_api, where the optionality of variables in the request is clearly marked in a consistent manner? Additionally, default values or flags indicating their absence should also be specified.
This would significantly simplify working with the library, as the user would be able to understand directly from the function code which data must be provided, which is optional, and what default values are applied to optional variables.
Here’s an example of a function that is currently generated. For optional variables, we need to indicate either "?" after the type or provide a default value. However, from the function description, there’s no clear guidance on when this can be done.
  /// Returns messages in a chat. The messages are returned in reverse
  /// chronological order (i.e., in order of decreasing message_id). For optimal
  /// performance, the number of returned messages is chosen by TDLib. This is
  /// an offline request if only_local is true
  ///
  /// [chat_id]
  /// Chat identifier
  ///
  /// [from_message_id]
  /// Identifier of the message starting from which history must be fetched; use
  /// 0 to get results from the last message
  ///
  /// [limit]
  /// The maximum number of messages to be returned; must be positive and can't
  /// be greater than 100. If the offset is negative, the limit must be greater
  /// than or equal to -offset. For optimal performance, the number of returned
  /// messages is chosen by TDLib and can be smaller than the specified limit
  ///
  /// [offset]
  /// Specify 0 to get results from exactly the message from_message_id or a
  /// negative offset up to 99 to get additionally some newer messages
  ///
  /// [only_local]
  /// Pass true to get only messages that are available without sending network
  /// requests
  Future<Messages> getChatHistory({
    required Int53 chat_id,
    required Int53 from_message_id,
    required Int32 limit,
    required Int32 offset,
    required bool only_local,
  }) async {
    return await sendRequest({
      '@type': 'getChatHistory',
      'chat_id': chat_id,
      'from_message_id': from_message_id,
      'limit': limit,
      'offset': offset,
      'only_local': only_local,
    }) as Messages;
  }

There are no optional parameters in the requests. The mentoned from_message_id, offset, and only_local parameters are required, despite rarely default values will fit. if a parameter is omitted in JSON interface, then it will have default value, which is false/0/empty string/empty array/null. If passing null as the value of a parameter has special meaning, then this is always documented.


Where to get MSBuild?

This is Windows 7 and I'm unable to install Visual Studio to get MSBuild. OmniSharp requires MSBuild to work. I have no idea where to get MSBuild without installing Visual Stdio. Please help. Thank you.

The VS 2019 MSBuild Tools supports Win7. You can install the latest by clicking the Build Tools link on this page.


Add version information

The --version command line switch as well as the get_version IPC command (see #98) could use this information. Should probably generated at compile time.
i3 IPC version information includes:
{
    "human_readable": "4.10.3-347-g586854b (2015-07-30, branch \"makepkg\")",
    "major": 4,
    "minor": 10,
    "patch": 3
}

Yeah, we need to figure out how to make cmake read the git tags (and also start tagging versions). Blocked until I decide to mark the first version of sway.

@Luminarys @minus7 IPC reminder

IPC taken care of, just needs to be patched up with better version information.

For the sake of everyone who isn't on IRC, sway will start being versioned once wlc starts being versioned.

I'll work on improving the tag information later tonight. Do you still want to do everything through macros defined at compile time?

Yep.

I'm closing this for the time being, as the output is now essentially the same as i3's with the exception of the version.


Submission 2211367_2213730_2213682_2213467_2213768

1. Implemented Algorithms: Corner Point and Best-Fit Decreasing
Corner Point: This algorithm uses the corner points of the stock material to determine suitable positions for the next piece. Pieces are sorted and placed into the stock material until no more pieces, even the smallest one, can fit. At that point, a new stock material is used. The algorithm prioritizes maximizing the utilization of leftover space by strategically placing pieces at effective corner positions.
Best-Fit Decreasing: This algorithm finds the stock material that offers the best leftover area for placing a piece. Larger pieces are prioritized and placed first, and they are fitted into the stock material with the smallest area that can still accommodate them. This approach minimizes wasted space and optimizes material usage.
2. Result
The results of the two algorithms are stored in the student_submissions/s2211367_2213730_2213682_2213467_2213768/results directory.
3. Additional Information
Manually created datasets are used to evaluate the strengths and weaknesses of each algorithm. These datasets allow for a detailed analysis of how the algorithms perform under different conditions.
Related Files:
data.txt: Contains the handcrafted dataset for testing and evaluation.
customEnv.py: Defines the custom environment for executing the algorithms.
customMain.py: The main execution file for running evaluations with the custom dataset.
How to Run:
Use the following command to execute and evaluate:
python student_submissions/s2211367_2213730_2213682_2213467_2213768/custom/ customMain.py

Thanks for your advice, I restored old folder s2210xxx, please check out and let me know if you face any issue


Users need to be notified when they go over their quotas

|    by ibc599

Need to notify users by email when they have used their disk quotas.
A possible solution is to have a cron job which run each day to check if any users have reached their limits. If so, email them.

Issue migrated from trac:54 at 2024-01-31 17:13:24 +1100

<EMAIL_ADDRESS>changed owner from rnb548 to rmb548

ibc599 changed status from new to assigned

ibc599 changed priority from major to minor

ibc599 changed owner from `` to rnb548

<EMAIL_ADDRESS>commented

Milestone Future deleted

<EMAIL_ADDRESS>commented

Bureau has agreed to supply software used to do this on Ngamai.
Robin

<EMAIL_ADDRESS>commented

Being over quota can cause hard to diagnose problems when the .Xauthority file can't be created.
Can we create a login warning message?

<EMAIL_ADDRESS>removed milestone (was Future)

<EMAIL_ADDRESS>commented

You could have something like this easily enough, just need a way for it to run on login:
# Print user quota
quota -s

if [ $? != 0 ]; then
    # Mail quota exceeded message
    quota -s | mail -s "Warning: Over disk quota on $HOSTNAME" $USER
fi


cfclient error (CF-RateLimitV2APIExceeded|10018) during creation of CF space

Description:
(CF-RateLimitV2APIExceeded|10018) Error during SPACE creation
Error requesting users: cfclient error (CF-RateLimitV2APIExceeded|10018): Rate Limit of V2 API Exceeded. Please consider using the V3 API
This is however reconciled after the API rate limit is reset but this creates issues during integration tests as the failure rate is high.
Current Client: github.com/cloudfoundry-community/go-cfclient/v2
Since, V2 is deprecated , could we check if we can start using go-cfclient/v3.

it may be relevant to https://docs.cloudfoundry.org/running/setting-rate-limit-cloud-api.html#v2-api-exclude

The current rate limit is 1k request / user / hour
As part of V2 depreciation , the request limit was reduced in Aug 2023 to accommodate only 3% of API calls via V2
current X-RateLimits can be checked by cf curl /v2/stacks -v ( after cf login -a )
X-Ratelimit-Limit-V2-Api: 1000
X-Ratelimit-Remaining-V2-Api: 900

I observed in the "CP CF core platform logs" that the API call statistics for the technical user responsible for creating CF spaces/instances have already exceeded the established limits. It's worth noting that this situation pertains to just a single type of request.
/v2/spaces/<GUID>/developers
having said that , the latest information is that by Q1 24 , the V2 API will be completely blocked on canary landscapes.
The Suggestion from BTP Control plan team is to migrate all calls to V3.

That is, we should migrate to github.com/cloudfoundry-community/go-cfclient/v3 (currently we use v2 of that module which has only partial CF V3 support).


Gazelle plugin does not handle swift GRPC / Proto library dependencies correctly

I'm working on transitioning to use the gazelle plugin provided by this repository. It seems to be working well for my regular code and SPM dependencies, but it fails for swift_proto_library and swift_grpc_library dependencies.
I define Proto targets in BUILD files like:
load("@build_bazel_rules_swift//swift:swift.bzl", "swift_proto_library")

swift_proto_library(
    name = "TokenProtos",
    visibility = ["//visibility:public"],
    deps = ["@protos//models/base/tokenmodels:tokenmodels_proto"],
)

And GRPC targets like this:
load("@build_bazel_rules_swift//swift:swift.bzl", "swift_grpc_library", "swift_proto_library")

swift_proto_library(
    name = "TokenGRPCProtos",
    visibility = ["//visibility:public"],
    deps = ["@protos//services/public/tokenservice:tokenservice_proto"],
)

swift_grpc_library(
    name = "TokenGRPC",
    srcs = ["@protos//services/public/tokenservice:tokenservice_proto"],
    flavor = "client",
    visibility = ["//visibility:public"],
    deps = [":TokenGRPCProtos"],
)

Where @protos is a local_repository containing my protos.
I import these from Swift like:
import models_base_tokenmodels_tokenmodels_proto
import models_base_usermodels_usermodels_proto
import services_public_tokenservice_tokenservice_proto
import services_public_userservice_userservice_proto

Because swift_proto_library and swift_grpc_library generate the module name from the proto package path + target name.
This builds fine with Bazel and inside my generated xcodeproj.
But when I run the Gazelle UpdateBuildFiles target, I get this error:
gazelle: Unable to find dependency labels for ant
gazelle: Unable to find dependency labels for os
gazelle: Unable to find dependency labels for models_base_tokenmodels_tokenmodels_proto, models_base_usermodels_usermodels_proto, services_public_tokenservice_tokenservice_proto, services_public_userservice_userservice_proto

Aside: The os system library should maybe be added to the list of known frameworks like Foundation and UIKit. I'm not sure where ant is coming from -- maybe a dependency? Is there a way to query the set of files visible to gazelle?

As far as expected behavior goes, I know adding full support for protos might be challenging but at least it would be nice if it could map those proto imports to manually created swift_proto_library and swift_grpc_library targets so it doesn't complain.
In an ideal world maybe there could be some way to configure gazelle to generate swift_proto_library and swift_grpc_library libraries in BUILD files that import proto modules. E.g. in your WORKSPACE or root BUILD file you could tell the Gazelle plugin which repository to resolve proto dependencies from.

Thanks @cgrindel ! Yes a way to supply a patch for swift_deps_index.json that could be persisted in the repo / survive //:swift_update_pkgs would help a lot.
That said, I do think that adding proper support for swift_proto_library and swift_grpc_library targets to the gazelle plugin is important too. When I have some more time I could try to put together a PR for it.
I think the way it would actually work is similar to how the Go gazelle plugin handles them.
When I run //:gazelle on my proto repository, given a GRPC proto definition:
syntax = "proto3";

package privateemailservice;

option go_package = "github.com/attilathefun/appengineserver/pb/services/private/privateemailservice";

import "models/base/emailmodels/email_name_and_address.proto";

// Interface exported by the server.
service Email {

    // Create a new email to one or more recipients.
    rpc CreateEmail(CreateEmailRequest) returns (CreateEmailResponse);
}

// CreateEmail

message CreateEmailRequest {

    // The email's to field.
    repeated emailmodels.EmailNameAndAddress emailTo = 1;

    // The email's subject field.
    string emailSubject = 2;

    // The email's body field.
    string emailBody = 3;
}

message CreateEmailResponse {
}

It generates this BUILD.bazel file:
load("@rules_proto//proto:defs.bzl", "proto_library")
load("@io_bazel_rules_go//go:def.bzl", "go_library")
load("@io_bazel_rules_go//proto:def.bzl", "go_proto_library")

proto_library(
    name = "privateemailservice_proto",
    srcs = ["email_service.proto"],
    visibility = ["//visibility:public"],
    deps = ["//models/base/emailmodels:emailmodels_proto"],
)

go_proto_library(
    name = "privateemailservice_go_proto",
    compilers = ["@io_bazel_rules_go//proto:go_grpc"],
    importpath = "github.com/attilathefun/appengineserver/pb/services/private/privateemailservice",
    proto = ":privateemailservice_proto",
    visibility = ["//visibility:public"],
    deps = ["//models/base/emailmodels"],
)

go_library(
    name = "privateemailservice",
    embed = [":privateemailservice_go_proto"],
    importpath = "github.com/attilathefun/appengineserver/pb/services/private/privateemailservice",
    visibility = ["//visibility:public"],
)

With the Swift plugin, I would add to that swift_proto_library and swift_grpc_library targets with similar structures. What do you think?

I see. There are two issues.

Add support  for protos in the Gazelle plugin.
Be able to override SPM dependencies.

Does that sound right? I missed that distinction previously. I will revert the title change so that reflects your original intent. Sorry.

I created #382 to track the SPM override feature.

Thanks! Yes those are the two issues. Even if the gazelle plugin supported the proto libraries I'd still need to patch the swift package manager dependencies to fix that swift-log conflict.


[Bug Report] Form validate not work when rules key is String and

Element UI version
2.0.8
OS/Browsers version
win8.1/chrome 63
Vue version
2.5.10
Reproduction Link
https://jsfiddle.net/1a510e91/2/
Steps to reproduce
click button "立即创建"
What is Expected?
test field is required
What is actually happening?
test is not required

update jsfiddle link

Fixed in https://github.com/ElemeFE/element/pull/8878


Inconsistent screenshots between two exact Pixel 2 API 27 devices

Hi there,
I take baseline screenshots locally using Pixel 2 API 27 emulator. Then, I compare local screenshots against generated Test Lab screenshots. I am using the same emulator device model + API level in test lab.
However, the screenshot comparison fails because the original screenshot dimension: 1080x1794 while the firebase test lab screenshot is 1080x1788 even though they are running in the same exact device model + API level.
Any idea why they are generating screenshots of different sizes?
Expected behaviour
Should generate same size screenshot
Actual behaviour
Generating images of different sizes that's why verification fails.

Steps to reproduce
Run ./gradlew screenshot task to generate baseline screenshot locally.
Run screenshot task in Firebase test lab.
Verify the two.
Version of the library
Latest.
I also made a post on Firebase Slack channel. Here's the thread:

Hi @sanginovs are you Jetpack Compose for your UI? If the device is the same I can ensure the screenshot will be the same. Could you please get the hardware details of the device you use in firebase test lab? If you are using compose ensure you run your baseline screenshots with the same Shot version you use to verify your tests. Between some shot versions the code compose provides to get a bitmap from a component has changed the way it works and can generate some differences between versions. Last question. Do your tests pass when you run the verification test in your emulator?

@pedrovgs i am not using Jetpack Compose. I looked up Firebase test lab device specs:

Here's my local emulator Pixel 2 specs:

Looks like the difference is screen size. As you can see from the screenshot, Firebase pixel 2 resolution is  1920 x 1080 while my emulator is 1080 x 1920. I will try to find a Firebase device that will exactly match my local emulator. Thanks for your time @pedrovgs

@pedrovgs here's an update. i just tested it again.

I manually downloaded generated screenshots from firebase and verified it locally by running this cmd: ./gradlew executeScreenshotTests -PrunInstrumentation=false. It's being verified and i dont run into different image size error.

However, when running the same cmd from CirceCI and verifying against the same baseline images, i am getting The size of the screenshot taken has changed for test .. error.

Any idea?

@pedrovgs i was able to resolve this issue. Looks like firebase test lab has different versions of Pixel2 device. i had to provide extra information: model=walleye,version=27,locale=en_US,orientation=portrait
That's what was causing this issue. thanks for your help.

Thanks for the extra info @sanginovs 😃 I'm happy to see you got it working.

Thanks for the extra info @sanginovs 😃 I'm happy to see you got it working.


Custom Context in the last version of Smart Tomcat for Intellij Community

Hello zengkid!
I'm a fan of the Smart Tomcat plugin from Intellij.
In the last versión of the plugin, i have a problem. The box “Custom Context” is missing in the run configuration. How can i specify a custom context for the execution?
Thank you very much for your time, and congratulations for it work.

Hello zengkid!
I'm a fan of the Smart Tomcat plugin from Intellij.
In the last versión of the plugin, i have a problem. The box “Custom Context” is missing in the run configuration. How can i specify a custom context for the execution?
Thank you very much for your time, and congratulations for it work.

@jlparrilla
Please put context.xml into webapp/META-INF/
Please find the example https://github.com/zengkid/smart-tomcat-sample

Ok. This solution is not valid for me.
I use diferent values of context variable for diferent environments. In the context.xml file of webapp/META-INF/ folder only have a referent to global environment variable. If i put the values in this file, it will travel with the war file, and it's not the objetive.
In the server, the value of global environments is in server.xml. With the missing "Custom Context" box, i could select one file of my local desktop that contains the values of this global environments variables for my local environment.
Exists another option for same solution?
Thank you.

@jlparrilla
you can create context_local.xml into webapp/META-INF/ folder
check sample : https://github.com/zengkid/smart-tomcat-sample/tree/master/web/src/main/webapp/META-INF

Ok! It work prefectly.
Thanks. Have a good day!


--report-path Requires File Name and Does Not Overwrite

When using --report-path it seems as if the full path must be used, for example C:\Windows\Logs\MyResults.csv and running the scanner a second time errors if the file is already present. It should either allow the path to be a directory only and then create a file like log4j2_scan_report_yyyyMMdd_HHmmss.csv or there should be a parameter to allow overwriting the file.

@PJMarcum
You can use relative path for --report-path option like this:
cmd> log4j2-scan.exe --report-path test_report.csv d:\tmp\verify
Logpresso CVE-2021-44228 Vulnerability Scanner 2.7.1 (2022-01-02)
Scanning directory: d:\tmp\verify
[*] Found CVE-2021-44228 (log4j 2.x) vulnerability in d:\tmp\verify\log4j-core-2.13.1.jar, log4j 2.13.1 (mitigated)
[*] Found CVE-2021-44228 (log4j 2.x) vulnerability in d:\tmp\verify\log4j-core-2.14.1.jar, log4j 2.14.1 (mitigated)
[*] Found CVE-2021-45105 (log4j 2.x) vulnerability in d:\tmp\verify\log4j-core-2.16.0.jar, log4j 2.16.0
[*] Found CVE-2021-44832 (log4j 2.x) vulnerability in d:\tmp\verify\log4j-core-2.17.0.jar, log4j 2.17.0

Scanned 139 directories and 1761 files
Found 2 vulnerable files
Found 0 potentially vulnerable files
Found 2 mitigated files
Completed in 1.60 seconds

cmd> type test_report.csv
"Hostname","Path","Entry","Product","Version","CVE","Status","Fixed","Detected at"
"RAPH","d:\tmp\verify\log4j-core-2.13.1.jar","","Log4j 2","2.13.1","CVE-2021-44228","MITIGATED","","2022-01-06 12:07:12"
"RAPH","d:\tmp\verify\log4j-core-2.14.1.jar","","Log4j 2","2.14.1","CVE-2021-44228","MITIGATED","","2022-01-06 12:07:12"
"RAPH","d:\tmp\verify\log4j-core-2.16.0.jar","","Log4j 2","2.16.0","CVE-2021-45105","VULNERABLE","","2022-01-06 12:07:12"
"RAPH","d:\tmp\verify\log4j-core-2.17.0.jar","","Log4j 2","2.17.0","CVE-2021-44832","VULNERABLE","","2022-01-06 12:07:13"

Use --report-dir to specify report output directory and use timestamp'd file name like this:
cmd> log4j2-scan.exe --report-dir d:\tmp\verify d:\tmp\verify
Logpresso CVE-2021-44228 Vulnerability Scanner 2.7.1 (2022-01-02)
Scanning directory: d:\tmp\verify
[*] Found CVE-2021-44228 (log4j 2.x) vulnerability in d:\tmp\verify\log4j-core-2.13.1.jar, log4j 2.13.1 (mitigated)
[*] Found CVE-2021-44228 (log4j 2.x) vulnerability in d:\tmp\verify\log4j-core-2.14.1.jar, log4j 2.14.1 (mitigated)
[*] Found CVE-2021-45105 (log4j 2.x) vulnerability in d:\tmp\verify\log4j-core-2.16.0.jar, log4j 2.16.0
[*] Found CVE-2021-44832 (log4j 2.x) vulnerability in d:\tmp\verify\log4j-core-2.17.0.jar, log4j 2.17.0

Scanned 139 directories and 1761 files
Found 2 vulnerable files
Found 0 potentially vulnerable files
Found 2 mitigated files
Completed in 0.46 seconds

cmd> type d:\tmp\verify\log4j2_scan_report_20220106_120934.csv
"Hostname","Path","Entry","Product","Version","CVE","Status","Fixed","Detected at"
"RAPH","d:\tmp\verify\log4j-core-2.13.1.jar","","Log4j 2","2.13.1","CVE-2021-44228","MITIGATED","","2022-01-06 12:09:34""RAPH","d:\tmp\verify\log4j-core-2.14.1.jar","","Log4j 2","2.14.1","CVE-2021-44228","MITIGATED","","2022-01-06 12:09:34""RAPH","d:\tmp\verify\log4j-core-2.16.0.jar","","Log4j 2","2.16.0","CVE-2021-45105","VULNERABLE","","2022-01-06 12:09:34"
"RAPH","d:\tmp\verify\log4j-core-2.17.0.jar","","Log4j 2","2.17.0","CVE-2021-44832","VULNERABLE","","2022-01-06 12:09:34"

If you want to append log, use --json-log-path or --csv-log-path option.


feat: add models and methods for AsyncAPI 3.0.0

Description
Add models and methods for AsyncAPI 3.0.0:

title, summary, description, tags, externalDocs and corresponding has* methods for core models
filterByTags method for core models
reply method in Operation model
host and pathname methods in Server model
new component methods
new OperationReply and OperationReplyAddress model
update Readme models
fix some models from 2.x.x perspective - add missed methods

cc @smoya @jonaslagoni

We should create a lighter version of this PR adding/changing only the necessary for releasing Parser-JS v2. Meaning all features of v3 that are not BC are out.

We should create a lighter version of this PR adding/changing only the necessary for releasing Parser-JS v2. Meaning all features of v3 that are not BC are out.

Created a PR for this matter https://github.com/asyncapi/parser-api/pull/93 @magicmatatjahu

Those are the changes I recently made to the API.
There are BC but I believe are worth:

Additions to Schema object:

Add schemaFormat(): string. This holds the schema format after converting to AsyncAPI Schema. It means it will only be application/vnd.aai.asyncapi+json;version=<version>.
Add originalSchemaFormat(): string. This holds the original schema format before converting to AsyncAPI Schema. It means it could be any of the formats, including the AsyncAPI one as well.

Removal of schemaFormat(): string from Message object. This is BC. This can be fetched from the message.payload().originalSchemaFormat().

Alternatives:

Change signature to schemaFormat(): string | undefined, because the payload of a message is optional. This will require to add the hasSchemaFormat(): boolean + the methods for the original format such as originalSchemaFormat(): string | undefined.

I removed the scopes() method that @magicmatatjahu added to the SecurityScheme since those can be fetched from the SecurityRequirement objects. More on https://github.com/asyncapi/parser-api/pull/86#discussion_r1270629633

I need your thoughts on this folks.
cc @fmvilas @derberg @magicmatatjahu @jonaslagoni

@smoya is schemaFormat(): string from Message object. the only breaking change we have ? can this justify pumping the API ?

@smoya is schemaFormat(): string from Message object. the only breaking change we have ?

Yes, it is as far as I can see.

can this justify pumping the API ?

It is a breaking change since libraries using that method will mostly break.
The alternative I mentioned was changing the return value for a union of string | undefined. That will potentially also break some (maybe not all) libraries anyway.
The reality behind that is that there is no other implementers of this api than our Parser-JS afaik, so in practice it wont really be a big problem if we consider a minor. But technically, it is a breaking change.

I updated my comment and remove the originalSchema methods so we keep doing the same behaviour until today, that is returning the original schema format right directly when calling schemaFormat().

I realized no one took care of this https://github.com/asyncapi/parser-js/pull/654/files#r1272712253 and we might want to implement the change here.

In order to reduce the breaking change impact regarding the message.schemaFormat(), I suggest we keep the function and only change the signature to become string | undefined. In that way, current users of message.schemaFormat() won't have a breaking change potentially. I also added the hasSchemaFormat(): boolean for the cases where the payload is empty (so no format is specified).
cc @jonaslagoni

@jonaslagoni @magicmatatjahu would you mind doing a last review?

Ping ping 😄

Closing in favor of https://github.com/asyncapi/parser-api/pull/101


Create SimpleRepaint.netkan

SimpleRepaint: Universal, simple and lightweight parts recoloring.
https://spacedock.info/mod/2820
https://github.com/judicator/SimpleRepaint
https://forum.kerbalspaceprogram.com/index.php?/topic/204419-18x-112x-simplerepaint-universal-simple-and-lightweight-parts-recoloring/

Wow, this is done without a new plugin. Thanks for the submission!


Integrate netlify-identity-widget capabilities into Decap CMS.

Is your feature request related to a problem? Please describe.
Are there plans for updating the netlify-identity-widget?  When we updated Decap CMS 3.0.12 to 3.1.1, the netlify-identity-widget stopped working.  We received the following error: "the uri was missing". Upon reverting back to 3.0.12, it began working again
Describe the solution you'd like
It would be awesome if the netfligy-identiy-widget could be taken over by decaporg and either updated to work with the latest versions of Decap CMS or even better, brough into Decap CMS itself so the widget does not have to be used at all.
Describe alternatives you've considered
Unfortunately, the only alternative we have found is to revert back to 3.0.12.

This is probably a problem with Decap, not the identity widget. We will not internalize authentication tools as this will bring more work.
To solve this, please rephrase your issue as a bug and provide more detail that will help somebody reproduce it.


Use quantum-resistant key establishment for preshared keys (PSK)

Ideally, we implement the rosenpass protocol which is based on this work on Post-Quantum WireGuard by Andreas Hülsing, Kai-Chun Ning, Peter Schwabe, Florian Weber, and Philip R. Zimmermann

Work to implement the Rosepass handshake in Go has been started: https://github.com/stv0g/go-rosenpass


Use this caching mechanism for custom image components

How can I use this caching library with https://wix.github.io/react-native-ui-lib/docs/components/media/Avatar ?

Hi @theobouwman unfortunately they do not support passing a custom component for the image as a prop. Your best bet would be to edit the source code of the Avatar and use patch-package to persist these changes between yarn install.


[Relay][Op] Add compute, schedule, and tests for expand_dims and squeeze

As the title states, these are compute and schedule primitives for operators expand_dims and squeeze, with tests included. Please review (e.g., @jroesch, @MarisaKirisame) for correctness and style.

Incidentally, is there a fundamental reason that Relay's squeeze needs to have a different calling convention from NNVM's? Namely, taking a list instead of a tuple and not allowing a single int in place of a list of one

Also is there a reason Relay's squeeze doesn't permit passing -1 (or negative dimensions in general) while NNVM's does?

topi squeeze doesn't handle nonpositive dimensions. implementing those properly will require some thought, because resolving them requires shape computation

the single int in place of a list could be handled by the register compute function

I see, regarding the shape computation issue (I am not sure I agree with the rationale since many other Relay functions do the same thing with axis args; we should be consistent).
I don't think the register compute function alone can or should handle the discrepancy in calling conventions because the Relay function nn.squeeze itself documents the calling convention of lists -- my questions is whether there is a reason for that, or if it should be made like NNVM's.

It seems that we will need to add negative axis support to topi, to make it compatible. Note that we only need to know the dimension of the shape and they are known in topi compute.
We can provide the support for passing a single int in the python wrapping, by detecting the input type.

@tqchen thanks for the explanation. If I understand correctly, couldn't we handle negative entries in squeeze_compiler without changing the topi implementation at all? Or would we prefer to avoid this sort of preprocessing before invoking topi functions?

This is a simple feature that seems would make topi more general, so we could do it in the topi side. Also given that this is already a simple function, our goal is to move most of the compute to c++

@joshpoll yes

Thanks, @joshpoll @slyubomirsky @jroesch @siju-samuel , this is merged.

see followup changes in https://github.com/dmlc/tvm/pull/2163/


python3Packages.garminconnect-aio: init at 0.1.4

Motivation for this change
Python module to interact with Garmin Connect
https://github.com/cyberjunky/python-garminconnect-aio
This is a Home Assistant dependency.

Target Home Assistant release: current

[ ] Update component-packages

[ ] Enable tests in Home Assistant

Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 126067 at 123ccb9e run on aarch64-linux 1

2 packages built successfully:

python38Packages.garminconnect-aio
python39Packages.garminconnect-aio

1 suggestion:

warning: maintainers-missing
Package does not have a maintainer. Consider adding yourself?
Near pkgs/development/python-modules/garminconnect-aio/default.nix:31:3:
   |
31 |   meta = with lib; {
   |   ^

Result of nixpkgs-review pr 126067 run on x86_64-linux 1

3 packages built:

home-assistant
python38Packages.garminconnect-aio
python39Packages.garminconnect-aio

This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
Result of nixpkgs-review pr 126067 run on x86_64-linux 1

3 packages built:

home-assistant
python38Packages.garminconnect-aio
python39Packages.garminconnect-aio


CNAM-286: Refactoring Patients

Refactoring Patients

I looked up your new commit, i think it's ok now. But did you make a full test in the cnam to be sure that you code will produce the same result as before ?


Fix blob structure

what started as just a tiny change to the advertisement blobs, turned into a big merge and some bug fixes

looks good

tested this locally and it works


Heavy first letters not being searched properly

Search kkkk for line found by kkkknsA. The line is actually k.kkk;nsA. We have a column called vishraam_first_letters, not heavy_first_letters.
Originally posted by @Harjot1Singh in Slack

I can do this

replace withVishraams parameter of firstLetters with an object that takes something like { heavy: true } and by default is {}

I cannot see the work committed to resolve this issue -- @Harjot1Singh was the "merge" label added by accident? I believe now that you've added the stripVishraams function, we should probably transfer this issue to database to fix:
/**
   * Given a string of first letters, return a query that searches for the shabad.
   * @param letters The first letters to search for a partial match of.
   * @param orderResults Apply sensible ordering too. `true` by default.
   * @param anywhere Search for `search` anywhere, not just at the beginning. `true` by default.
   */
  firstLetters( letters, orderResults = true, anywhere = true ) {
    return this.genericSearch( letters, 'first_letters', orderResults, anywhere, true )
  }

https://github.com/ShabadOS/database/blob/7097e360fdbba2fe627967c25a8ddd5e96ae125e/lib/models/Lines.js#L91

Added support for vishraam options in https://github.com/Harjot1Singh/gurmukhi-utils/commit/db6b14f8007bf199959ffea969ebf9cec42f3936.
Transferring to https://github.com/ShabadOS/database.


Bio-footprint calculation for greengas doesn't seem to work as expected

When changing the share of green gas in the gas network, the bio-footprint is expected to increase. This is indeed the case for PRO:

However, the bio-footprint (in the dashboard) doesn't increase when changing the shares for BETA:

At the production branch, the key typical_production_per_km2 is still included in the greengas.ad file, whereas it has been removed for beta. It should calculate the value recursively but this doesn't seem to be the case.
@antw Do you have any thoughts on this?

The area footprint calculation is pretty simple. It looks for the bio_footprint_calculation node group, and for each of its output it looks at the typical_production_per_km2 of each carrier.
@marliekeverweij @ChaelKruip Is it possible that new nodes added for the biomass project should have been added to the group, or that new carriers may be missing a typical_production_per_km2 value?

@marliekeverweij @ChaelKruip Is it possible that new nodes added for the biomass project should have been added to the group, or that new carriers may be missing a typical_production_per_km2 value?

We are on it!

The edge between energy_import_greengas and foreign_energy_upgrade_biogas was of type constant instead of share. Updating the edge type to share seems to have fixed the issue.


Add support for "Shared Drives"

This PR adds support for Google's "Shared Drives", see https://developers.google.com/drive/api/guides/enable-shareddrives
This PR updates the build to go 1.17

@adityak74

@jordanwmckee if you need this functionality, you can use my fork in the meantime:
- name: Upload to gdrive
  uses: timvlaer/google-drive-upload-git-action@main
  with:
     ...

@timvlaer @jordanwmckee - Thanks for contributing, new release v0.2 is now up!

@timvlaer Awesome, thank you, it works great! Would it be possible to add support for uploading folders as well?

@jordanwmckee - Can you post more specific requirements?

@adityak74- Well, I'm not very familliar with the creation process for these gh actions, so I'm not sure how difficult this would be, but in my current project, I have a directory that contains a few files and other sub-dirs and files. I would like to be able to upload that main directory to a folder in google drive and maintain the structure inside that directory. So in gdrive, it would have to create the new directories in the specified location I am uploading to, and upload the contents of those directories to the destination as well. Does that make sense?


[question] how to ignore specific error?

Hi there,
thanks for this work.
Is there a way to filter out some error from the query_failed metric? Let's say wrong auth credentials, login expired for example and so on....
Thanks

I am working on a new version that will allow customizing when specific metrics are gathered. I hope I will manage to finish it by the end of this week.


com.gargoylesoftware.htmlunit.html.DomNode.asText() returns nested elements with linebreaks

In the case of nested elements, the text of span element is output with linebreaks:

    <select name="day" size="1">...</select>
    <select name="month" size="1">...</select>
    <select name="year" size="1">...</select>

output:
1
JAN
2021
Therefore, real line breaks, like
 cannot be distinguished in output text from blocks. This worked fine in the earlier versions like 2.18
It seems that the status is set incorrectly after a block, see:
com.gargoylesoftware.htmlunit.html.HtmlSerializer.HtmlSerializerTextBuilder.append(String, Mode)

Good point - can you please provide some test (in com.gargoylesoftware.htmlunit.html.HtmlSelectTest)
like this one
/**
 * @throws Exception if an error occurs
 */
@Test
public void asTextInsideSpan() throws Exception {
    final String html = "<form>\n"
        + "\n"
        + "  <select name='day' size='1'>"
                + "<option value='1' selected>01</option>"
                + "<option value='2'>02</option></select>\n"
        + "  <select name='month' size='1'>"
                + "<option value='1' selected>Jan</option>"
                + "<option value='2'>Feb</option></select>\n"
        + "  <select name='year' size='1'>"
                + "<option value='1'>2022</option>"
                + "<option value='2' selected>2021</option></select>\n"
        + ""
        + "</form>";
    final HtmlPage page = loadPage(html);
    final DomElement elem = page.getElementById("test");
    assertEquals("01 Jan 2021", elem.asText());
}

Just to make sure we are agree on the same expectations for this (simples selects, multiple selects, different size attributes etc.)

From my point of view the implementation for multiple selects is also not correct.

Ok, i think i have to make a hard cut here, will implement a new method asNormalizedText() and make the old one deprecated. Looks like there is a lot of stuff that is still there for backward compatibility.
same for #283

Thank you. Here are some tests with expected values
/htmlunit/src/test/java/com/gargoylesoftware/htmlunit/html/HtmlTableTest.java:
    /**
     * Tests getTableCell(int,int).
     * @exception Exception If the test fails
     */
    @Test
    public void getCellAt() throws Exception {
        final String htmlContent
            = "<title>foo</title>\n"
            + "
\n"
            + "
cell1a
cell1b
	cell2	cell4
\n"
            + "
cell3
\n"
            + "
\n"
            + "";
        final HtmlPage page = loadPage(htmlContent);

        final HtmlTable table = page.getHtmlElementById("table1");

        final HtmlTableCell cell1 = table.getCellAt(0, 0);
        assertEquals("cell1 contents", "cell1acell1b", cell1.asText());

        final HtmlTableCell cell2 = table.getCellAt(0, 1);
        assertEquals("cell2 contents", "cell2", cell2.asText());

        final HtmlTableCell cell3 = table.getCellAt(1, 0);
        assertEquals("cell3 contents", "cell3", cell3.asText());
        assertSame("cells (1,0) and (1,1)", cell3, table.getCellAt(1, 1));

        final HtmlTableCell cell4 = table.getCellAt(0, 2);
        assertEquals("cell4 contents", "cell4", cell4.asText());
        assertSame("cells (0,2) and (1,2)", cell4, table.getCellAt(1, 2));
    }

    /**
     * Tests getTableCell(int,int).
     * @exception Exception If the test fails
     */
    @Test
    public void getCellAtWithBreaks() throws Exception {
        final String htmlContent
            = "<title>foo</title>\n"
            + "
\n"
            + "
cell1a

cell1b
	cell2	cell4
\n"
            + "
cell3
\n"
            + "
\n"
            + "";
        final HtmlPage page = loadPage(htmlContent);

        final HtmlTable table = page.getHtmlElementById("table1");

        final HtmlTableCell cell1 = table.getCellAt(0, 0);
        assertEquals("cell1 contents", "cell1a\ncell1b", cell1.asText());

        final HtmlTableCell cell2 = table.getCellAt(0, 1);
        assertEquals("cell2 contents", "cell2", cell2.asText());

        final HtmlTableCell cell3 = table.getCellAt(1, 0);
        assertEquals("cell3 contents", "cell3", cell3.asText());
        assertSame("cells (1,0) and (1,1)", cell3, table.getCellAt(1, 1));

        final HtmlTableCell cell4 = table.getCellAt(0, 2);
        assertEquals("cell4 contents", "cell4", cell4.asText());
        assertSame("cells (0,2) and (1,2)", cell4, table.getCellAt(1, 2));
    }

/htmlunit/src/test/java/com/gargoylesoftware/htmlunit/html/HtmlSelectTest.java:
    /**
     * @throws Exception if an error occurs
     */
    @Test
    public void asTextInsideSpan() throws Exception {
        final String html = "<form>\n"
            + "\n"
            + "  <select name='day' size='1'>"
                    + "<option value='1' selected>01</option>"
                    + "<option value='2'>02</option></select>\n"
            + "  <select name='month' size='1'>"
                    + "<option value='1' selected>Jan</option>"
                    + "<option value='2'>Feb</option></select>\n"
            + "  <select name='year' size='1'>"
                    + "<option value='1'>2022</option>"
                    + "<option value='2' selected>2021</option></select>\n"
            + ""
            + "</form>";
        final HtmlPage page = loadPage(html);
        final DomElement elem = page.getElementById("test");
        assertEquals("01Jan2021", elem.asText());
    }

Hello @rbri,
I saw that there was a commit to my problem. Thank you very mutch for the quick implementation. When I ran my sample unit tests again with the asNormalizedText () method, I found that the problem for the tables had unfortunately not yet been resolved. Would it be possible to look at that again?

Hi @dennisduysak ,
this is work in progress, i have not done much on this. The plan is

to introduce the new method and make the old deprecated (done)
switch from system dependent line separator to \n (done)
make unit tests for at least all the cases we have unit test for the old method
make sure to remove all the special cases we have implemented in the old hierarchy - have test for all the cases and adapt the impl to something meaningful (at this step your case might be fixed)
cleanup, add more tests and release

But please keep in mind i do all this in my spare time, having a real >40h per week job - means any help is welcome.

Thank you for the update. I know it's hard to get involved in such a project alongside a full-time job.


[Snyk] Upgrade @opentelemetry/auto-instrumentations-node from 0.39.0 to 0.39.2

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade @opentelemetry/auto-instrumentations-node from 0.39.0 to 0.39.2.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 2 versions ahead of your current version.
The recommended version was released a month ago, on 2023-08-31.

Release notes

Package name: @opentelemetry/auto-instrumentations-node

0.39.2 - 2023-08-31Dependencies

The following workspace dependencies were updated

dependencies

@ opentelemetry/instrumentation-dns bumped from ^0.32.1 to ^0.32.2
@ opentelemetry/instrumentation-fastify bumped from ^0.32.1 to ^0.32.2
@ opentelemetry/instrumentation-mongodb bumped from ^0.36.1 to ^0.37.0

0.39.1 - 2023-08-17Dependencies

The following workspace dependencies were updated

dependencies

@ opentelemetry/instrumentation-generic-pool bumped from ^0.32.1 to ^0.32.2

0.39.0 - 2023-08-14

    from @opentelemetry/auto-instrumentations-node GitHub release notes

Commit messages

Package name: @opentelemetry/auto-instrumentations-node

d1436eb chore: release main (#1651)
78472a7 chore: align @ types/node to core repo and disable renovate (#1653)
0b1f5b6 chore(tedious) align supported versions in code tests and docs (#1655)
67f66d2 fix(fastify): Make sure consturctor patching works with esm (#1624)
d9cd8d7 fix(instrumentation-dns): use caret range for semver regular dependency (#1654)
a556179 chore(deps): update dependency semver to v7.5.4 (#1646)
0fbacba chore: remove gts from packages (#1643)
808e614 chore(deps): update all patch versions (#1645)
3308a54 chore(deps): update dependency sinon to v15.2.0 (#1650)
ff29576 fix(mongodb): remove broken type export `V4Connection` (#1644)
d83b57b chore: release main (#1640)
651b4f8 fix(generic-pool): remove deps on types package for ts5 compatibility (#1637)

Compare

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Replaced with another PR.


MyLocationNewOverlay&PolyLine disappear when zoomLevel > 21

When i add a MyLocationNewOverlay and a PolyLine and zoom in to a zoomlevel higher than 21, they both disappear.
Is this a wanted behaviour or a bug?
And how to prevent them from disappearing?

Known issue, zoom 20 is really the max we can support
On Sep 14, 2016 8:56 AM, "gruelfin"<EMAIL_ADDRESS>wrote:

When i add a MyLocationNewOverlay and a PolyLine and zoom in to a
zoomlevel higher than 21, they both disappear.
Is this a wanted behaviour or a bug?
And how to prevent them from disappearing?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/osmdroid/osmdroid/issues/416, or mute the thread
https://github.com/notifications/unsubscribe-auth/AB4kGTMDQuHFtvZdcELDWwdV59bu7ymHks5qp-7igaJpZM4J8vYx
.

Known issue, zoom 20 is really the max we can support
Why is it like this?

#329  #230 #114 #46 here are some related tickets when I searched the issue list for "zoom". Essentially, it's an android View class limitation that causes integer overflow

I just added this bit to the FAQ for further clarity
https://github.com/osmdroid/osmdroid/wiki/FAQ#i-zoomed-past-level-20-and-the-everything-disappeared

I need this to display for Indoor Tiles. I hope there will be a solution in the future. Thanks for the FAQ!

Dear @spyhunter99, when will v5.6 be release? Is it really fix this issue as FAQ announcement? Appreciate if it is fixed soon :)

It was released yesterday.

It should be functional for zoom 20 to 22. 22 is still the max
On Dec 13, 2016 5:04 AM, "wolojoli"<EMAIL_ADDRESS>wrote:

It was released yesterday.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/osmdroid/osmdroid/issues/416#issuecomment-266697151,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB4kGTBj_oBy6Gjp6Tn_fptI_hPgDfazks5rHm1_gaJpZM4J8vYx
.


Fix alphabetical ordering.

@joachimmetz not going to wait for review of this, just moving the order around.

LGTM, no objections in changing order without review


docs(cleanup) Remove reference to stale AWS install guide

The EKS guide is already in the navigation menu, and is also referenced in setup/install/providers/aws/index.md (file in this PR).

@brian-armory please review

Thanks @akshayabd. I also added a redirect from the old page to the new (if anyone had it bookmarked).

@clareliguori pointed out that the old instructions had information we still want available to users. Chatted with @brian-armory and he suggested we first revert the PR, then make edits.


styles(*) Fix broken & missing styles

Summary

Updates type sizing classes (.xl-> .type-xl)
Adds color classes to utils (.color-blue-base)
Adds missing styles for <select />
Fixes svg sizing/spacing in KButton as well as the slot checks

PR Checklist

[x] Does not introduce dependencies
[x] Functional: all changes do not break existing APIs and if so, bump major version.
[x] Tests pass: check the output of yarn test packages/
[x] Naming: the files and the method and prop variables use the same naming conventions as other Kongponents
[x] Framework style: abides by the essential rules in Vue's style guide
[x] Cleanliness: does not have formatting issues, unused code (e.g., console.logs), or leftover comments
[x] Docs: includes a technically accurate README, uses JSDOC where appropriate

can you post a before/after screenshot just to see the visual changes easier? thanks

can you post a before/after screenshot just to see the visual changes easier? thanks

You can view the changes on the docs preview. The only real change is the KButton bug, the rest are additions for stuff we didn't have support for (css file)


[GENERAL -> request] Adding eiwd in the wyverkiss repository

I've seen that Dylan has eiwd in the kiss repository. May you also add it because its much more simpler and easier to manage than wpa supplicant.

Supporting iwd (or eiwd) is currently impossible.
See also:

<EMAIL_ADDRESS>https://github.com/OpenMandrivaAssociation/iwd/commit/ef9aaeb7858582f225b49cefe733b0cf861d1f75
https://github.com/kisslinux/repo/commit/6b7db9e42c5aa8103a1fca653af584169e5b9fcb#r53305492

Alright, I'll try compiling wicd from source and see what happens. I guess this would be better because gtk is shipped with firefox and so is python (already there).


Fair jsperf test for sql.js

Hey - please have a look at
http://jsperf.com/sql-js-vs-alasql-js/8#run
and let me know if think its a fair test.
Interesting to se how firefox and chrome performe different...

To make it more failr, you can also turn off caching of precompiled statements, like in this example:
jsPerf tests without caching
Now Firefox has significant optimization for asm.js, and I think to rewrite Alasql with ASM.js specifications to make it faster in FF and new IE.


dursun55

rejected:B1
It looks like you are trying to submit B1, however it seems like the following submission criteria are problematic:

Logs are missing
We’ve thus marked B1 as rejected, however if this is a mistake, please upload the log summary and we can re-review.

rejected:B2
reason:logs are missing

rejected:B2
reason:logs are missing

rejected:B3
reason:missing logs for 3 different startup types

rejected:B3
reason:missing logs for 3 different startup types

rejected:B6
reason:logs are missing

rejected:B6
reason:logs are missing

rejected:T1
reason:We cannot fully verify this submission. It looks like you are trying to submit T1, however, it seems like there are no supporting details(screenshots).

rejected:T1
reason:We cannot fully verify this submission. It looks like you are trying to submit T1, however, it seems like there are no supporting details(screenshots).

rejected:T2
reason:We cannot fully verify this submission. It looks like you are trying to submit T2, however, it seems like there are no supporting details(screenshots).

rejected:T2
reason:We cannot fully verify this submission. It looks like you are trying to submit T2, however, it seems like there are no supporting details(screenshots).

rejected:T4
reason:address missing

rejected:T4
reason:address missing

confirmed:B4
address:2wsLwUEDfMsWSFYHskf8pnLsp3NBcr2atJfs34d7dzmaLmSvni
baker:1064

confirmed:B4
address:2wsLwUEDfMsWSFYHskf8pnLsp3NBcr2atJfs34d7dzmaLmSvni
baker:1064

rejected:B5
address:2wsLwUEDfMsWSFYHskf8pnLsp3NBcr2atJfs34d7dzmaLmSvni
reason: no 'update baker account' or 'update baker key' transactions found on-chain


Rename Magento.gitignore to Magento1.gitignore

Because Magento1 and Magento2 have a very different folder structure.
In example, on Magento2 the folder vendor should be ignore by versionning. On Magento1 the folder vendor don't exist

@Nolwennig  apologies for the delay in replying to this.
I had a lot of these templates requested, but I couldn't quite figure out the right place for them. I ended up settling on #2857, and you'll see a Magento v1 template can now be found at community/PHP/Magento1.gitignore.
The current Magento.gitignore template should be for the latest version of Magento.
Feel free to submit any future improvements to that template, and thanks again for the contribution!

Great !
Thanks @shiftkey


error C2371 and C2572 with pre-compiled headers on MSVC

After zxing-cpp v2.2.1, It is impossible to compile libreoffice on Windows because it falls with error:
[build CXX] workdir/UnpackedTarball/zxing/core/src/datamatrix/DMReader.cpp
[build CXX] workdir/UnpackedTarball/zxing/core/src/datamatrix/DMSymbolInfo.cpp
C:/sources/libo-core/workdir/UnpackedTarball/zxing/core/src/DecodeHints.cpp(15): error C2371: 'ZXing::DecodeHints': redefinition; different basic types
C:\sources\libo-core\workdir\UnpackedTarball\zxing\core\src\ReaderOptions.h(176): note: see declaration of 'ZXing::DecodeHints'
C:/sources/libo-core/workdir/UnpackedTarball/zxing/core/src/DecodeHints.cpp(20): error C2572: 'ZXing::ReadBarcode': redefinition of default argument: parameter 1
C:\sources\libo-core\workdir\UnpackedTarball\zxing\core\src\ReadBarcode.h(21): note: see declaration of 'ZXing::ReadBarcode'
C:/sources/libo-core/workdir/UnpackedTarball/zxing/core/src/DecodeHints.cpp(25): error C2572: 'ZXing::ReadBarcodes': redefinition of default argument: parameter 1
C:\sources\libo-core\workdir\UnpackedTarball\zxing\core\src\Result.h(37): note: see declaration of 'ZXing::ReadBarcodes'
[build CXX] workdir/UnpackedTarball/zxing/core/src/datamatrix/DMVersion.cpp
[build CXX] workdir/UnpackedTarball/zxing/core/src/datamatrix/DMWriter.cpp
make[1]: *** [C:/sources/libo-core/solenv/gbuild/LinkTarget.mk:410: C:/sources/libo-core/workdir/GenCxxObject/UnpackedTarball/zxing/core/src/DecodeHints.o] Error 2
make[1]: *** Waiting for unfinished jobs....
make: *** [Makefile:289: build] Error 2

Do you know if the libreoffice scripts are compiling zxing-cpp as static or as dynamic library?

LibreOffice scripts compile zxing-cpp as static library.

Can you confirm that libreoffice compiles with the 2.2.0 release?

Yes.

Thanks for the info. The file DecodeHints.cpp is actually not required at all in a static build, so I can patch it such that it gets excluded in this case. That said, I'm reluctant to make yet another release just for this when the trivial solution is to compile libreoffice with 2.2.0. The only addition of 2.2.1 is the addition of the file that breaks your build.

Thanks, axxel. Yes, the build box was using pre-compiled headers as the log had:

checking whether to enable pch feature... yes (full)

@ilmari-lauhakangas thanks for the confirmation of my suspicion. Is simply going back to 2.2.0 a viable solution for your build issues?

The unmerged patch is https://gerrit.libreoffice.org/c/core/+/160528
Taichi has a lot of experience in applying additional patches on top of external dependencies, so I suppose your commits from today can be added as a .patch file.

Looking at that patch, the most strait forward fix would be to simply use 2.2.0 in https://gerrit.libreoffice.org/c/core/+/160528/4/download.lst . No need for any additional patching in that case. If you insist on using 2.2.1, then the only needed patch would be this one, I believe. With a static build, you would then simply have 2.2.0.

But what if Linux packagers want to use zxing from their system and thus would prefer 2.2.1 over 2.2.0, right?

But what if Linux packagers want to use zxing from their system and thus would prefer 2.2.1 over 2.2.0, right?

They can do that just fine. The only point of introducing 2.2.1 was to enable someone with a dynamically linked executable compiled with 2.1.0 (or 2.0.0) to still run with a 2.2.1 so-file (without recompilation).
That said, I just realized that I did not cater the other direction: if you dynamically link against 2.2.x, your executable will not work with a libZXing.2.1.0.so. That means your minimum required zxing-cpp version is 2.2.0 and packagers will have to take care for that. So if someone wants to have a new LibreOffice, they also need a new zxing-cpp (either 2.2.0 or 2.2.1).
Does that make sense to you?

It makes sense, thanks.

@th1722 I received an email notification for a comment you posted here about "backporting a patch to this repository". But in the web gui of github it does not show up. Did you delete it because it is obsolete or is there a bug in github?

Only now did I realize that LibreOffice does not use the cmake build files provided by zxing-cpp but rolls it's own (ughh) and that was the "attack vector" for the precompiled headers change.
Anyway, I see that LibreOffice now builds and runs on 2.2.1, so this issue fixed, right?


error when opening exe

i open exe file, im not using a vm. then it gives me error Traceback (most recent call last):
File "source_prepared.py", line 108, in
File "shutil.py", line 460, in copy2
FileNotFoundError: [WinError 3] The system cannot find the path specified
i ahve done all steps properly, i have AV disabled, and i reinstalled it, what should i do

Hey i also got a error like that

ok i will try it today

ok i will try it today

did it work??

Hey, just use the ModdedPysilon version, it covers every bug and it make sure your discord account never get banned.
Leave me a star if you like my project ;)


Training page (with wait time) needs to be more visible

Likely needs to be embedded into the dashboard or added to a main menu somewhere.

Mostly fixed with 269f0b3c372ff2e3b93cff05d16e814fc4be250e. May add to menu as well in future.


not working on chrome for Android

Hi,
on my phone the dialog screen asking for permission to use the microphone does not appear. On chrome for desktop I don't experience a problem. Maybe a similar issue to the safari one that got fixed recently?
Thank you for looking into this.

I figured it out with some extensive googling. The issue was due to chrome only allowing the usage of the microphone when the site uses https. I rewrote my app to use https locally and now the recording works.


MF-1525 - Add graceful stop for HTTP and GRPC servers

What does this do?
This pull request adds a graceful shutdown to HTTP and gRPC servers.
Which issue(s) does this PR fix/relate to?
This pull request resolves #1525.
List any changes that modify/break current functionality
There are no such changes.
Have you included tests for your changes?
Yes.
Did you document any new/modified functionality?
No, there is no need for that.
Notes
N/A

Codecov Report

Merging #1548 (17466ee) into master (ad8b7dd) will decrease coverage by 0.03%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master    #1548      +/-   ##
==========================================
- Coverage   67.60%   67.57%   -0.04%
==========================================
  Files         133      133
  Lines       10930    10938       +8
==========================================
+ Hits         7389     7391       +2
- Misses       2937     2943       +6
  Partials      604      604

Impacted Files
Coverage Δ

pkg/errors/errors.go
61.22% <0.00%> (-11.95%)
:arrow_down:

things/service.go
66.07% <0.00%> (+0.71%)
:arrow_up:

Continue to review full report at Codecov.

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

@arvindh123 Please, update your branch and resolve the conflicts

@arvindh123 please update the branch.
@dusanb94 can we please push this one forward.

@arvindh123 please update the branch.
@dusanb94 can we please push this one forward.

As soon as @arvindh123 updates the PR, it's ready.


Error creating new project

I followed the instruction to install bud, and bud create app doesn't work

OS: Arch linux
go: version 1.18.2
node: v14.19.2

This is due to trying to move files across partitions. /tmp/bud-create- Seems to not exist in whichever partition bud is expecting it to be. I’ve not looked at the source code, so not sure what functionality is needed/should be changed. But this should give someone who’s more familiar a good jumping off point

Thanks for opening this issue and trying out Bud @012e!
As @syke99 mentioned, this is a known issue with partitions. We're already tracking it in https://github.com/livebud/bud/issues/30, where I've written the planned next steps.
I'm going to close this issue as a duplicate of https://github.com/livebud/bud/issues/30

This is weird, I didn't put my /tmp in a different partition.
But I do have other un-formatted OS partitions with /tmp folder inside of it.
What bud create did to my /tmp folder:

Hmm, okay. It might be something different then, re-opening.
If you could try narrowing this down in the codebase, that'd be much appreciated. The create logic is in this package and I created a Contributing Guide today to help people get Bud installed locally.
Otherwise I'm still going to go with the plan in this comment and we'll try again once that's ready: https://github.com/livebud/bud/issues/30#issuecomment-1126880064

@matthewmueller I have just done a setup and tried to go run main.go -C create app
What happened:

Sweet! From your error it looks like the problem is coming from this code block: https://github.com/livebud/bud/blob/7bcf01d370b93878e22c945a84ca29d8eb7bf9f1/internal/command/create/create.go#L55-L70
Can you confirm?

@012e would you mind pulling down the branch in this PR and testing if this fixes your problem? https://github.com/livebud/bud/pull/50

@012e Would you mind pulling down the branch in the following PR and testing if this fixes your problem? https://github.com/livebud/bud/pull/50

Still not working, but bud create app created an unfinished project like the previous /tmp/bud-create-, probably something is wrong with npm's permissions

Do you need the log @matthewmueller?

@012e Ah, this is a different error and actually only a problem in the development build, not the production build.
From within the unfinished project directory, please try running the following:
npm link livebud $DIR_WHERE_YOU_GIT_CLONED_BUD/livebud

This should fail in the same way. I guess because of lack of npm permissions. I guess you could fix this with sudo npm.

Working perfectly @matthewmueller! BTW,  my default website zoom is 120% and something is off with the css. Was it supposed to look like this?

Closing the issue!

Working perfectly @matthewmueller! BTW, my default website zoom is 120%, and the cards are covering the footer

Closing this issue!

@012e happy to hear! Did the sudo npm work for you?
Also created an issue on the welcome page: https://github.com/livebud/welcome/issues/1

@012e happy to hear! Did the sudo npm work for you?
Also created an issue on the welcome page: livebud/welcome#1

That's how I fixed the problem


Protect games

Task/Issue URL: https://app.asana.com/0/488551667048375/1202942224713452/f
Description
This protects games and has a remote config to enable/disable that
functionality.
The PR incidentally also fixes a but we had in the
TrackingProtectionAppsRepository:isAppProtectionEnabled() method that
was causing games to show always as protected when going to the app
details screen.
This bug probably didn't manifest very often given that games protection
are disabled by default.
Steps to test this PR
Test the bug fix

[ ] install from develop
[ ] install Among us game
[ ] launch our app and enable AppTP
[ ] enable protection for among us and launch it
[ ] ensure trackers for Among us are blocked
[ ] disable protection for Among us
[ ] open DDG app and go to "App Tracking Protection" and in recent activity click on Among us row
expected: Among us toggle should be OFF in the screen that opens
actual: Among us toggle is ON in the screen that opens
[ ] install this branch and verify the expected behavior actually happens

Test game protection

[ ] In PrivacyConfigService replace the endpoint by https://jsonblob.com/api/jsonBlob/963471835740258304
[ ] install from this branch
[ ] launch and enable AppTP
[ ] Go to App Tracking protection -> "Having problems with an app" -> "Show all apps" and verify games are not protected
[ ] go to https://www.jsonblob.com/963471835740258304 and change the protectGames state to enabled. Also bump the version number at the beginning of the JSON file
[ ] force-close the app and re-open (remote config should be downloaded)
[ ] Go to App Tracking protection -> "Having problems with an app" -> "Show all apps" and verify games are protected
[ ] Open Among Us game and verify tracking attempts are blocked

Current dependencies on/for this PR:

develop

PR #2292   👈

This comment was auto-generated by Graphite.

Looks good and works as expected! 🎉 Left a few comments on test names, if you want to check those.

Thanks for the feedback. Agree to all!


Upload pynipap to PyPI

As far as I can tell, there's no package for pynipap on PyPI. So adding it to a requirements file isn't possible, which is not ideal for automation.

You are right, pynipap should be on pypi, which is why I've just uploaded it there! :)
Also updated release-document so we won't forget to update it in the future - see 43504ad28b27623137b7d806e81731b4315b01f2


[circuit~] update

Quite a few things:

New opamp2 object: a more advanced and accurate opamp than the other, more simple and fast one.

opamp2 also has models
These models are really needed to make the TS9, ProCo Rat and MXR Distortion+ examples sound realistic
The old opamp is still included because it's more efficient and easier to set up.

Added oversampling option. This helps to reduce aliasing in oscillators and distortion. Usually 2x or 4x is enough.
Optimised everything a bit
You can now set the oversampling and dcblock with the. -oversample and -dcblock flag. In many cases, you want these values to be fixed for the circuit you're working on, and not have to re-send the message every time.

Sorry if the helpfile sizes are shifting, I'm trying my best but every time I open/close a subpatch in pd, it shrinks a bit. I should probably report that if it hasn't been already.


firebase_core: ^0.5.2 FAILURE: Build failed with an exception.

Works fine when I use firebase 0.5.0+1
firebase_core: ^0.5.2 generates:
D8: Program type already present: com.google.protobuf.ByteString$CodedBuilder
FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':app:transformDexArchiveWithExternalLibsDexMergerForDebug'.

com.android.builder.dexing.DexArchiveMergerException: Error while merging dex archives:
Learn how to resolve the issue at https://developer.android.com/studio/build/dependencies#duplicate_classes.
Program type already present: com.google.protobuf.ByteString$CodedBuilder

Flutter doctor
/Users/stephan/development/flutter/bin/flutter doctor --verbose
[✓] Flutter (Channel stable, 1.22.3, on Mac OS X 10.15.7 19H2, locale en-NO)
• Flutter version 1.22.3 at /Users/stephan/development/flutter
• Framework revision 8874f21e79 (12 days ago), 2020-10-29 14:14:35 -0700
• Engine revision a1440ca392
• Dart version 2.10.3
[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
• Android SDK at /Users/stephan/Library/Android/sdk
• Platform android-30, build-tools 29.0.3
• Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
• Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)
• All Android licenses accepted.
[✓] Xcode - develop for iOS and macOS (Xcode 12.1)
• Xcode at /Applications/Xcode.app/Contents/Developer
• Xcode 12.1, Build version 12A7403
• CocoaPods version 1.9.3
[✓] Android Studio (version 4.1)
• Android Studio at /Applications/Android Studio.app/Contents
• Flutter plugin installed
• Dart plugin version 201.9245
• Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)
[✓] Connected device (1 available)
• LYA L29 (mobile) • LHS7N18A13001240 • android-arm64 • Android 10 (API 29)

Hi @StephanCassel
You need to enable multidex in your android app. Please follow https://developer.android.com/studio/build/multidex
Closing, as this isn't an issue with flutterfire itself. If you disagree, please write in the comments and I will reopen it.
Thank you

Hi @TahaTesser
Thanks for replay
I understand that is not nessary  minSdkVersion 21 and above.
"If your app only targets Android 21 or higher (minSdkVersion) then multidex is already enabled by default and you do not need the multidex support library."
Thanks again

Hi again,
It was a barcode plugin (discontinued) that came in conflict with firebase.
Stephan

What went wrong:
Execution failed for task ':app:transformDexArchiveWithExternalLibsDexMergerForDebug'.

This is usually thrown when multidex is not added and by default Flutter doesn't target API 21


Add handling for preferred location users

Current coverage is 6.99% (diff: 0.00%)

Merging #24 into dev will decrease coverage by 0.07%

@@               dev       #24   diff @@
========================================
  Files           89        90     +1
  Lines         3480      3516    +36
  Methods          0         0
  Messages         0         0
  Branches       365       373     +8
========================================
  Hits           246       246
- Misses        3220      3256    +36
  Partials        14        14

Powered by Codecov. Last update f051290...34b6683


⚠ Orpheus has degraded performance

In 8179bb2, Orpheus ($OPS) experienced degraded performance:

HTTP code: 200
Response time: 20710 ms

Resolved: Orpheus performance has improved in 08b9e60.


Add option to select which MouseButtons should trigger selection-start

This PR adds an option ignoredButtons to options.behavior that is by default empty - i.e. no buttons are ignored.
The user of the library may then supply a collection of MouseButtons (integers 0 through 4) for which the selection-start should not be triggered.
#212

I'm closing this PR and will open a new one, since the version changes are needed in my fork until this is merged as I'm currently hosting the fork in a private registry.


Handling refresh token by recall same request after refreshing the token

Hi,
I am trying to make a common interceptor to authorize all my outgoing requests.
My logic is as follows:
All my outgoing requests/API calls  passes through the interceptor first to check on my token expiry and in-case the response was un-authorized I make an internal call to refresh the token and update my storage keys with the new values.
Now I need to recall the original request with the new token value, but I can't figure out how to detect the original request that passed through the interceptor.
This is my code :
export  const unregister =  fetchIntercept.register({
  request: function (url, config) {
    return [url, config];
  },

  requestError: function (error) {
    return Promise.reject(error);
  },
  responseError: function (error) {
    return Promise.reject(error);
  },

  response: function (response) {
    if (response.status == 401) {
      Services.refreshToken((res)=>{
        if (res.message == 'success') {
          // if token has been refreshed
          // recall the request again
        }else {
          // login again
        }
      })
    }else {
      return response;
    }
  }
})

The problem is that I've no idea how to recall the same request that passed through the interceptor.. I did some search on this, but couldn't find a way to execute this.

You are on the right track; I built something similar two years ago. You just have to store the failed request somewhere and simply redispatch it; for this you must correlate the errors with the actual requests made; in the original Angular interceptor stuff, you could get the config of the original request and thus re-construct the actual request.

How about instead of retrying when there is 401 HTTP status, simply check earlier (in request interceptor) if token is expired or not? And if it's expired, then refresh the token?

Hi,
I am trying to make a common interceptor to authorize all my outgoing requests.
My logic is as follows:
All my outgoing requests/API calls passes through the interceptor first to check on my token expiry and in-case the response was un-authorized I make an internal call to refresh the token and update my storage keys with the new values.
Now I need to recall the original request with the new token value, but I can't figure out how to detect the original request that passed through the interceptor.
This is my code :
export  const unregister =  fetchIntercept.register({
  request: function (url, config) {
    return [url, config];
  },

  requestError: function (error) {
    return Promise.reject(error);
  },
  responseError: function (error) {
    return Promise.reject(error);
  },

  response: function (response) {
    if (response.status == 401) {
      Services.refreshToken((res)=>{
        if (res.message == 'success') {
          // if token has been refreshed
          // recall the request again
        }else {
          // login again
        }
      })
    }else {
      return response;
    }
  }
})

The problem is that I've no idea how to recall the same request that passed through the interceptor.. I did some search on this, but couldn't find a way to execute this.

Did find the solution? because I have the same issue

I am having the same issue. Not sure how to recall the failed request after refreshing token. Is there any solution for this?

How if, we intercept in the request, store the url in the storage, and then use the stored url after the refresh token used to get access token ?

How if, we intercept in the request, store the url in the storage, and then use the stored url after the refresh token used to get access token ?

Here is example of refresh token and recall the original request
const originalRequest = {}
export const interceptor = fetchIntercept.register({
    request: function (url, config) {
        originalRequest.url = url
        originalRequest.config = config
        return [url, config];
    },

    requestError: function (error) {
        // Called when an error occured during another 'request' interceptor call
        return Promise.reject(error);
    },

    response: async function (response) {
        if(response.status === 401)
        {
            const {url, config} = originalRequest
            if(url.includes('token'))
            {
                interceptor()
                return Promise.reject("Session expired");
            }
            else
            {
                return AppStore.dispatch(AuthActions.refresh_token())
                        .then((data) => {
                            config['headers']['Authorization'] = 'Bearer '+data.token
                            return fetch(url, config)
                        })
                        .catch((error) => {
                            return Promise.reject(error)
                        })
            }
        }
        else
        {
            return response
        }
    },

    responseError: function (error) {
        // Handle an fetch error
        return Promise.reject(error);
    }
});

Here is example of refresh token and recall the original request
const originalRequest = {}
export const interceptor = fetchIntercept.register({
    request: function (url, config) {
        originalRequest.url = url
        originalRequest.config = config
        return [url, config];
    },

    requestError: function (error) {
        // Called when an error occured during another 'request' interceptor call
        return Promise.reject(error);
    },

    response: async function (response) {
        if(response.status === 401)
        {
            const {url, config} = originalRequest
            if(url.includes('token'))
            {
                interceptor()
                return Promise.reject("Session expired");
            }
            else
            {
                return AppStore.dispatch(AuthActions.refresh_token())
                        .then((data) => {
                            config['headers']['Authorization'] = 'Bearer '+data.token
                            return fetch(url, config)
                        })
                        .catch((error) => {
                            return Promise.reject(error)
                        })
            }
        }
        else
        {
            return response
        }
    },

    responseError: function (error) {
        // Handle an fetch error
        return Promise.reject(error);
    }
});

This will not work if multiple requests were made in parallel. It will use the wrong url and config


Feat: Add support for OpenAI function call

Description: This PR proposes a simple implementation to add support for the Open AI function_call parameter and modifies the with_function for the plan method of the ChatOpenAIclass accordingly.
Issue: Right now, there is no way to force the model to generate a function call as enabled by the Open AI API.

@baskaryan

Apologies for the slow review! Pr has some merge conflicts, happy to re-review if you'd like to resolve

should be possible now


Add support for graphicsmagick

Adds support for taking screenshots with GraphicsMagick using gm import.

I like it, thanks! I'll update the documentation myself.


[Feature request] Page Persistence

It would be great if when you returned to a page that you have previously visited in the current rtv session it is in that same state you left it in.
For example: you open a submission, scroll down a dozen comments then exit the submission. When you reopen that same submission you should be at that same comment you scrolled to.

Agreed, this would be a neat feature. We would need to somehow cache the SubmissionContent() and the objects.Navigator() state, but beyond that I don't see anything that would make this impossible.

I would enjoy this feature. I find myself having to close rtv often and reopen it later.


⚠ Garbage Collector has degraded performance

In 8cae672, Garbage Collector (https://gc.fef.moe/login) experienced degraded performance:

HTTP code: 200
Response time: 9887 ms

Resolved: Garbage Collector performance has improved in abc9d2d.


Integrate ssapp-window component from pdm-web-components in leaflet-ssapp

[1] Integrated since https://github.com/webcardinal/webcardinal-core/commit/21e2e7aeb7cd4e04b1951b3c3901449fc60cf0e8
[2] CORS fix https://github.com/webcardinal/webcardinal-core/commit/817071e94ebe97e76675158e04138d01cfbe1b9e


POC attack against Score

Perform a proof of concept attack against the vulnerable service. Ideally should show how this works in a completely insecure environment, as well as ones secured by Shellbox and Firejail.

[x] Safemode disabled
[ ] Safemode enabled

Proof of concept work will remain local for the time being. An additional layer of complexity has been added to the project, as there is not one singular attack vector, but many.

Full completion of the second part of this objective will wait on milestone two. There is a live demonstration that works in a valid and expected use-case. However, the more complex situation needs to be investigated further.

Unlikely to be a sprint goal for implementation


Tilde ~ sometimes not quoted

import {quote} from "shell-quote";
console.log(quote(['cat', '~/.bashrc']));   // tilde not quoted
console.log(quote(['cat', '~/s p a c e'])); // tilde quoted

The treatment of ~ should be consistent at the very least. I find it surprising that ~ is not quoted since all other special Bash characters are quoted.
I suggest adding ~ to the list of characters to quote in this line:
https://github.com/ljharb/shell-quote/blob/da8a3abb4b2754dd9c1d3203142133e253c515a4/quote.js#L14
This quirk was showcased last week in a AmateursCTF challenge.

~ isn't universally replaced with $HOME, i believe. Which shells besides bash support that?

Which shells besides bash support that?

Zsh, Fish, dash, oilshell, nushell, PowerShell and probably more

node, however, does not, i think, if you pass it in child_process.exec?

node, however, does not, i think, if you pass it in child_process.exec?

const { exec } = require('node:child_process');
exec('echo ~', (error, stdout, stderr) => {
  console.log(`exec: ${stdout}`);
});

const { execFile } = require('node:child_process');
execFile('echo', ['~'], {shell: false}, (error, stdout, stderr) => {
  console.log(`execFile (shell=false): ${stdout}`);
});
execFile('echo', ['~'], {shell: true}, (error, stdout, stderr) => {
  console.log(`execFile (shell=true): ${stdout}`);
});

Unsurprisingly, the output is
execFile (shell=true): /home/me

execFile (shell=false): ~

exec: /home/me

ahh, the shell option is the difference :-) i've never passed that, so i've always been confused that ~ doesn't expand.
sounds like this would be a useful thing to quote. If we did it automatically, in what ways could that be a breaking change? (the case above where it quotes is because of the spaces, so it's not inconsistent right now)

in what ways could that be a breaking change?

Looking at the code, we see that ~ is already quoted when the input contains whitespace, a single quote, or a double quote. Otherwise we reach the return String(s).replace line, which does not quote ~.
https://github.com/ljharb/shell-quote/blob/da8a3abb4b2754dd9c1d3203142133e253c515a4/quote.js#L11-L14
Speaking of introducing breaking changes, you could consider quoting the percent sign % as well for good measure, as mentioned on Exploiting CVE-2021-42740.

Right, but the presence of ~ isn't triggering the quoting, which remains consistent currently - otherwise, you could claim that a is quoted on line 12 but not on line 14, which is true but a useless thing to measure.
The goal is to not introduce breaking changes, since that's the most harmful thing any package can do to the ecosystem.
My question was, if we change it so that ~ (or %) alone can trigger the quoting, what would that break for a user?


Demo URL not working

Hi!
I just wanted to give this a quick try and I noticed that the demo deployment is currently not working. Seems like the backend is not responding. The browser console shows the following:
WebSocket connection to 'wss://wss-samurize.bricolage.io/ws' failed: There was a bad response from the server.

Mhh, I left the tab open for a few hours and somehow it showed content now. Pressed refresh and it's gone again.

Hmm try clearing your application cache? Electric SQL isn't self-healing yet always so manually clearing the cache is the way to clean things up.


Quick note date format displays hectic file names

Preview and create quick note file names do not match what is entered with keyboard
The keys I enter are correctly displayed in the fill-in box on the right but are erroneous in the "Preview" text, as well as created file names
There are strange remapping of keys: on my French AZERTY keyboard, most keys display the correct preview, but some transfrom into incorrect mappings:

'Q' translates into '2'
'k' translates into '14'
'n' translate into 'AD'
'e' translates into '2'

The errors are systematic -- it means they are not random
It prevents from selecting a filename and a folder to store the quick notes into.

@Jeromandres if you check the format string definition in the Moment.js docs (which is linked in the option description), you'll see that this is expected behaviour: https://momentjs.com/docs/#/displaying/format/. Q gets replaced by the quarter, k gets replaced with the hour in 24hr time, N gets replaced with the era, and e gets replaced with the day of the week.
You can wrap characters in [square brackets] to avoid character replacements e.g. doing [Quick Note,] YYYY-MM-DD instead of Quick Note, YYYY-MM-DD.


About function Primitive.getGeometryInstanceAttributes

pipeLine is a Primitive instance.
data count about  100,000.
i want change geometryInstance's color attribute;
First call changeTest(),It takes 33 milliseconds;
but second call it ,It takes 3283 milliseconds;
I want change geometry's color by custom condition,How can i do? Thanks Thanks Thanks.

Hi there,
I would suggest reading through the Geometry and Appearances tutorial, particularly the portion on PerInstanceColorAppearance.
Cesium is a big project, so we use GitHub for feature requests and bug tracking exclusively. In the future, please take any questions to the Cesium Forum where there are members of the community and developers from the team who can help. Thanks!

Thanks!


Allow multiple potential public keys when using cosign

Describe the feature
For notary, the delegations feature allows using different keys for different signers either of which could sign a given image. For cosign, a similar feature would make sense to allow different people to sign the same image.
Optional: Is your feature request related to a problem? Please describe.
In more complex development setups with bigger teams, it may be useful to have multiple eligible signers.
Optional: Implementation ideas
One could use the policy[*].pattern[*].with configuration and either add wildcard parsing of trust_root or add a new boolean key any_trust_root.
A blocker may be if the uploaded cosign [digest].sig files are overwriting. This would need to be checked first.
Optional: Additional context
Cosign validator

Resolved by PR #428


[staging] grpc: override abseil to use same std=c++14 version

Description of changes
Reported broken on staging on comment: https://github.com/NixOS/nixpkgs/pull/165732#issuecomment-1087058576

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Will that affect
https://github.com/NixOS/nixpkgs/blob/f9180933cae3dea5546b6954c66da7b77e04ff4c/pkgs/development/libraries/grpc/default.nix#L67-L72

That's effectively dead code at this point, since we are defaulting to LLVM 11 or newer for everything but FreeBSD. On FreeBSD it's impossible to reach that point because cmake doesn't build anyway. So that shouldn't be a blocking concern for this PR and that code can probably be cleaned up.
I guess we could try
@ofborg pkgsLLVM.grpc
but it'll probably time out.

@ofborg  build pkgsLLVM.grpc

@ofborg build pkgsLLVM.grpc

CMake Warning at cmake/modules/Findc-ares.cmake:18 (find_package):
  Could not find a configuration file for package "c-ares" that is compatible
  with requested version "1.13.0".

  The following configuration files were considered but not accepted:

    /nix/store/nh777bwrcaz6z8rkzcs40xp80kdwsc67-c-ares-config.cmake/c-ares-config.cmake, version: unknown

Call Stack (most recent call first):
  cmake/cares.cmake:42 (find_package)
  CMakeLists.txt:312 (include)

-- Found c-ares: /nix/store/v5nz29zycv7iw9b85nqh1dqxa8hghbx6-c-ares-x86_64-unknown-linux-gnu-1.18.1/include (found suitable version "1.18.1", minimum required is "1.13.0")
-- Found Protobuf: /nix/store/0dz9js7a5w0jpg4cwnycdlnl4rm3w5jx-protobuf-x86_64-unknown-linux-gnu-3.19.3/lib/libprotobuf.so (found version "3.19.3")
-- Found PkgConfig: /nix/store/j44iq4s539mfs03ba6mghr9kgpa9h8za-x86_64-unknown-linux-gnu-pkg-config-wrapper-0.29.2/bin/x86_64-unknown-linux-gnu-pkg-config (found version "0.29.2")
-- Found RE2 via pkg-config.
-- Found OpenSSL: /nix/store/d2mvw2fzpcql6fabj4qiyan30qy1yhwz-openssl-x86_64-unknown-linux-gnu-1.1.1n/lib/libcrypto.so (found version "1.1.1n")
CMake Error at /nix/store/c5jhgwlnq0782aqxb7brkpxpb56h5bgh-cmake-3.22.3/share/cmake-3.22/Modules/FindPackageHandleStandardArgs.cmake:230 (message):
  Could NOT find ZLIB (missing: ZLIB_LIBRARY) (found version "1.2.12")
Call Stack (most recent call first):
  /nix/store/c5jhgwlnq0782aqxb7brkpxpb56h5bgh-cmake-3.22.3/share/cmake-3.22/Modules/FindPackageHandleStandardArgs.cmake:594 (_FPHSA_FAILURE_MESSAGE)
  /nix/store/c5jhgwlnq0782aqxb7brkpxpb56h5bgh-cmake-3.22.3/share/cmake-3.22/Modules/FindZLIB.cmake:120 (FIND_PACKAGE_HANDLE_STANDARD_ARGS)
  cmake/zlib.cmake:52 (find_package)
  CMakeLists.txt:318 (include)

-- Configuring incomplete, errors occurred!
See also "/build/source/build/CMakeFiles/CMakeOutput.log".
builder for '/nix/store/3rylbb0vg1ypmjhwk59glvmiamll49q7-grpc-x86_64-unknown-linux-gnu-1.44.0.drv' failed with exit code 1

CMake Warning at cmake/modules/Findc-ares.cmake:18 (find_package):
  Could not find a configuration file for package "c-ares" that is compatible
  with requested version "1.13.0".

since this PR is to address x86_64-linux gcc: gcc_10 → gcc_11 breakage that llvm issue seems to be unrelated, though currently present on staging.
Have no way to help since on the platform I am on the issue is not present: pkgsLLVM.grpc on x86_64-linux — Success
https://github.com/NixOS/nixpkgs/pull/167129/checks?check_run_id=5886474017

Could NOT find ZLIB (missing: ZLIB_LIBRARY) (found version "1.2.12")

Possibly another zlib cross issue? cc @Mindavi


Maintenance status?

Hi @qiangxue,
I'm currently using ozzo-dbx as part of another open source project that I'm soon planning to release and therefore I'm asking for the maintenance status of the package so that I can decide whether to use my fork as import path or postpone a bit the release until PRs #99, #100, #102 are reviewed and merged.
I really like ozzo-dbx and its lightweight query builder approach and hope its not getting abandoned.

I've decided to go with my own fork - https://github.com/pocketbase/dbx
Anyway, thanks @qiangxue for your open source work!


gildas: 20190701_a -> 20190901_a

Motivation for this change
Update Gildas to the latest upstream version.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[x] macOS
[x] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

This builds on Linux, but on Darwin I get the following error:
gildas-src-aug19a/integ/x86_64-darwin-gfortran-openmp/bin/hlp2tex \
      -L/private/var/folders/r2/zwnv7zsd4bd99mqkn4mhqxn800034l/T/nix-build-gildas-20190801_a.drv-0/gildas-src-aug19a/integ/x86_64-darwin-gfortran-openmp/lib -L/nix/store/7nrhz57r0h1g4avg0ba9m2n8asfwdb61-python-2.7.16/lib   -L/nix/store/d0xg488j5iw4z5zd19cp8a1mjgcjg50n-gtk+-2.24.32/lib -L/nix/store/w9fnipb9ficaz1iv1fryl1pvhvmq9zvc-glib-2.60.4/lib -L/nix/store/gclh8scc9wffh1drbx73yamaksiyrl2z-cairo-1.16.0/lib -L/nix/store/9vkdlyk2nwz2rh7i88881bgp8px5v398-fontconfig-2.12.6-lib/lib -L/nix/store/vwdvgl2dcxyw14plyz9p4517i39m7381-freetype-2.10.0/lib -L/nix/store/sdxb2xv1i7a1vvjmqpcx6rrj1xc5sv3k-pango-1.43.0/lib -L/nix/store/vk2fjbcc34ccr91wqq2hglaymy4x5ixl-gdk-pixbuf-2.38.1/lib -L/nix/store/9789bxxhv5dcs23yiqfgifk8864c026j-atk-2.32.0/lib -lgtk-x11-2.0 -lgdk-x11-2.0 -lpangocairo-1.0 -latk-1.0 -lcairo -lgdk_pixbuf-2.0 -lgio-2.0 -lpangoft2-1.0 -lpango-1.0 -lgobject-2.0 -lfontconfig -lfreetype -lgthread-2.0 -lglib-2.0 -L/nix/store/vvgvamfcrrkj4p57ff1krxnl8l6z5hc3-libpng-apng-1.6.37/lib -lpng16  -L/nix/store/7nrhz57r0h1g4avg0ba9m2n8asfwdb61-python-2.7.16/lib -ldl -framework CoreFoundation -lpython2.7 -L/nix/store/n3r2h80x5n0204vkvkhklpjj6gs4pljr-cfitsio-3.47/lib -L/nix/store/af9phazy6dmyy7zzcxf1rrzadgwgplc7-bzip2-<IP_ADDRESS>.1/lib -lcfitsio -lbz2  -lm -ldl
f951: Warning: unrecognized command line option '-Wno-unused-command-line-argument'
ld: framework not found CoreFoundation

After some investigation, I found that the configuration script for gildas calls python-config --libs, which returns: -lpython2.7 -ldl -framework CoreFoundation. This probably fails because nix does not search for frameworks in the standard locations. What directory should be added to the search path to find Nix version of this framework? Shouldn't this be added automatically when python-config --libs is called?
cc @matthewbauer

Built and tested successfully on Darwin and Linux with nix review.

@GrahamcOfBorg build gildas

Ofborg build on Linux fails because of an internal compiler error:
gfortran: internal compiler error: Killed (program f951)
Please submit a full bug report,
with preprocessed source if appropriate.
See <https://gcc.gnu.org/bugs/> for instructions.

I'm not sure why this fails on OfBorg but not on both local installations of NixOs Debian?

I tested the build on:

NixOS with sandboxing
Nix under Debian
Both build successfully...

I tested the build on:

NixOS with sandboxing
Nix under Debian
Both build successfully...

Yes, it looks like an issue with gfortran on OfBorg. I suppose we can just ignore it, since the package builds fine on all platforms.

It might be just running out of memory.


Is an instance a container?

It's not clear for me in project1:region:instance1 what to put in instance.
I am using kubernetes with 2 nodes, several services, several deployments. One of the replica sets of one of the deployments has a pod with 2 containers: cloudsql-proxy and my app container
Is it possible to clarify this in docs?

I understand now, it's the instance ID of the SQL instance.


images has copyright?

Hello,
images has copyright?
I want to use on my future project gym app, but I dont know if its possible.

Hello, images has copyright? I want to use on my future project gym app, but I dont know if its possible.

Hi @paulocometti ,
Did you find out anything about the copyright?

There is an information under the Unlicense section. https://github.com/yuhonas/free-exercise-db?tab=Unlicense-1-ov-file

Hey guys, see https://github.com/yuhonas/free-exercise-db/issues/2 i've been meaning to update the README.md as it's a recurring good & valid question


Add an intersection/union option for the tripartite and heatmap

Does this mean that intersection and union affect the node-link diagram as well?

Applies only do the tripartite and heatmap, not to the node-link diagram. Hopefully the way it appears in the layout make this clear.


feat: changed multiple commands to be used directly with console.log

Coverage report

St.:grey_question:
Category
Percentage
Covered / Total

🟢
Statements
100%
108/108

🟢
Branches
100%
6/6

🟢
Functions
100%
6/6

🟢
Lines
100%
108/108

Show new covered files 🐣

St.:grey_question:
File
Statements
Branches
Functions
Lines

🟢
getTimeString.ts
100%
100%
100%
100%

Test suite run success
9 tests passing in 2 suites.
Report generated by 🧪jest coverage report action from dc5176b1de6fb302ee0c8c28d5eab56c45faab23


DO NOT MERGE: make sure event loops properly use the deferment api.

make sure event loops properly use the deferment api.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report
Patch coverage: 100.00% and project coverage change: -0.02% :warning:

Comparison is base (e612539) 79.90% compared to head (fe42509) 79.89%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #598      +/-   ##
==========================================
- Coverage   79.90%   79.89%   -0.02%
==========================================
  Files          27       27
  Lines        5847     5849       +2
==========================================
+ Hits         4672     4673       +1
- Misses       1175     1176       +1

Files Changed
Coverage Δ

source/linux/epoll_event_loop.c
87.30% <100.00%> (+0.10%)
:arrow_up:

... and 1 file with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.