[AIRFLOW-2077] Fetch all pages of list_objects_v2 response

Make sure you have checked all steps below.
JIRA

[X] My PR addresses the following Airflow JIRA issues and references them in the PR title. For example, "[AIRFLOW-XXX] My Airflow PR"

https://issues.apache.org/jira/browse/AIRFLOW-2077

Description

[X] Here are some details about my PR, including screenshots of any UI changes:
If you had more than 1000 results from list_keys or list_prefixes you would get the first 1000

Tests

[X] My PR adds the following unit tests OR does not need testing for this extremely good reason:
Covered by existing tests

Commits

[X] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

[X] Passes git diff upstream/master -u -- "*.py" | flake8 --diff

I'm sure this can be tested, right?

Codecov Report

Merging #3012 into master will increase coverage by 0.03%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #3012      +/-   ##
==========================================
+ Coverage   73.14%   73.18%   +0.03%
==========================================
  Files         177      177
  Lines       12394    12412      +18
==========================================
+ Hits         9066     9084      +18
  Misses       3328     3328

Impacted Files
Coverage Δ

airflow/hooks/S3_hook.py
88.67% <100%> (+2.31%)
: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 a0deb50...bc91644. Read the comment docs.

@bolkedebruin added two tests for the paged responses


Remove more reliance on Numpy C math functions

Reuse our math module implementations as much as possible.
Based on PR #1952.

[Current coverage][cc-pull] is 87.21%

Merging [#1954][cc-pull] into [master][cc-base-branch] will decrease coverage by 0.03%

@@             master      #1954   diff @@
==========================================
  Files           299        299
  Lines         53281      53249    -32
  Methods           0          0
  Messages          0          0
  Branches       5502       5498     -4
==========================================
- Hits          46486      46442    -44
- Misses         5883       5894    +11
- Partials        912        913     +1

Powered by Codecov. Last updated by [5bd208c...0539563][cc-compare]
[cc-base-branch]: https://codecov.io/gh/numba/numba/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/numba/numba/compare/5bd208c54b61d13c18412bed5d5ca9e3437f27f5...05395631e9507056cc2f844bbf7e561f2d7426d3
[cc-pull]: https://codecov.io/gh/numba/numba/pull/1954?src=pr


[Bug] Fix bug that BE core will loading empty json array

Proposed changes
When loading json data like [] (an empty array). BE will crash with stack:
*** Aborted at<PHONE_NUMBER> (unix time) try "date -d @1612273824" if you are using GNU date ***
PC: @           0xe0cce7 rapidjson::GenericValue<>::Accept<>()
*** SIGSEGV (@0xe) received by PID 36798 (TID 0x7f7812114700) from PID 14; stack trace: ***
    @     0x7f791b74b470 (unknown)
    @           0xe0cce7 rapidjson::GenericValue<>::Accept<>()
    @          0x169ff79 _ZN5doris10JsonReader17_print_json_valueB5cxx11ERKN9rapidjson12GenericValueINS1_4UTF8IcEENS1_19MemoryPoolAllocatorINS1_12CrtAllocatorEEEEE
    @          0x16a0689 doris::JsonReader::_write_values_by_jsonpath()
    @          0x16a2cb4 doris::JsonReader::_handle_flat_array_complex_json()
    @          0x16a3761 doris::JsonScanner::get_next()
    @          0x1659bd4 doris::BrokerScanNode::scanner_scan()
    @          0x165a671 doris::BrokerScanNode::scanner_worker()
    @          0x281f67f execute_native_thread_routine
    @     0x7f791b5001c3 start_thread
    @     0x7f791b7fd12d __clone

Types of changes

[x] Bugfix (non-breaking change which fixes an issue)

#5246


Navigation in the configuration UI's file tree is not working using arrow keys

The navigation in the file tree of the configuration UI is not working using the arrow keys.
If a user selects an element, e.g. a file, it is expected to select the next file when pressing the "down-arrow"-key or expanding or collapsing an directory using the left and right key, respectivelly.
Currently, the UI throws an execption when a user presses one of the arrow keys, if an element of the file tree is selected.

The problem is related to the use of drag&drop.
There is currently an issue at PrimeReact:
https://github.com/primefaces/primereact/issues/1183


Multi part validation

Hi there,
I came across an issue where I couldn't validate codes longer than 3 parts. Turns out, it wasnt documented, and I just needed to add the parts as a second positional argument.
This however is inconsistent with the interface for the generate method.
I've updated the validate method's arguments to match those of generates, and have also added a feature to set a default parts length.
I've also updated the readme (but only in english, I don't speak Korean unfortunately), and bumped the version.
I hope you find the changes to your liking :) Thanks again.

Thanks for contributing @gee-forr. Sorry for being late. I've been sick for the last couple days :cry:
As you pointed out, I agree that those #generate and #validate's method signatures are not consistent and it should be addressed.
However I'd prefer to leave current interface as it is because changing #validate's argument doesn't seem to improve the library's usability significantly. Instead, I am working on adding configuration so that the users of this gem can change the number of parts, the length of each part, etc.
The end result will look like:
CouponCode.configure do |c|
  c.parts = 5
  c.length = 6
  c.separator = '-'
end

I believe this approach will provide with more conventional use cases.
You can find working in progress code at #6. Please feel free to create another PR for other implementation suggestions.

I updated README to make that multi-part validation clearer for now: 0d40bb40091144fdcff4cbbaca4900fc46888bc6. Thanks again for your time and effort and my apology for being late :sob: I will be adding configuration as soon as possible.


use custom aggregate type mapping

resolves https://github.com/prooph/event-sourcing/issues/64

Coverage decreased (-3.7%) to 85.821% when pulling 00b8bbf53d1c4da74317dda9ff663b15322c6711 on aggregate_type_mapping into 43741b0366e1458aced6a5883014f4f9e8eba2fd on master.

Coverage decreased (-3.7%) to 85.821% when pulling 00b8bbf53d1c4da74317dda9ff663b15322c6711 on aggregate_type_mapping into 43741b0366e1458aced6a5883014f4f9e8eba2fd on master.

updated

Coverage decreased (-1.04%) to 88.476% when pulling 8d0172d6a8bceec72c5db2d20c6baf3f3657fa5f on aggregate_type_mapping into 43741b0366e1458aced6a5883014f4f9e8eba2fd on master.

Minor issue regarding docs but LGTM
@basz can you do a second review?

Coverage decreased (-1.04%) to 88.476% when pulling cba43c2c86fe66a4a635cb32921566d73d3534f6 on aggregate_type_mapping into 43741b0366e1458aced6a5883014f4f9e8eba2fd on master.

Actually we don't, but removing would be BC.
On Jun 21, 2017 3:00 AM, "Bas Kamer"<EMAIL_ADDRESS>wrote:

@basz commented on this pull request.
beside fromString still being here LGTM
In src/Aggregate/AggregateType.php
https://github.com/prooph/event-sourcing/pull/65#discussion_r123055883:

 }

 /**
  * Use this factory when the aggregate type is not equal to the aggregate root class

*

* @throws Exception\InvalidArgumentException
*/

public static function fromString(string $aggregateTypeString): AggregateType

do we still need this method now we go for fromMapping
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/prooph/event-sourcing/pull/65#pullrequestreview-45224617,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAYEvA2NmXmDzKr2YTFkOIb68POWtntRks5sGBbqgaJpZM4N_UVX
.

kk


Installation fails with npm v10.x

I get an error when trying to install textlint-rule-aws-service-name in a project using npm v10.x.
$ node -v
v20.12.0
$ npm -v
10.5.0
$ npm init
$ npm install textlint-rule-aws-service-name
npm ERR! code 127
npm ERR! path /Users/hoge/sample-pj/node_modules/textlint-rule-aws-service-name
npm ERR! command failed
npm ERR! command sh -c husky install
npm ERR! sh: husky: command not found

npm ERR! A complete log of this run can be found in: /Users/hoge/.npm/_logs/2024-05-16T04_48_10_912Z-debug-0.log

I have confirmed that it installs successfully in projects using npm v9.x.
$ node -v
v20.5.1
$ npm -v
9.8.0
$ npm init
$ npm install textlint-rule-aws-service-name

added 493 packages, and audited 494 packages in 2s

139 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities

I don't know if this is related to this case or not, but a similar phenomenon was reported, so I'll post a link.

https://github.com/npm/cli/issues/7322

@maroKanatani
Thank you for your report!
I maby fix on it #97.
❯ node -v
v20.12.0
❯ npm -v
10.5.0
❯ npm install textlint-rule-aws-service-name

added 492 packages, and audited 493 packages in 4s

139 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities

Please use 1.10.1 (latest version)
I close this issue. If you find a new. Please report me.
Thank you for your valuable contribution!


I can't write a tab

Describe the bug
I cant write a tab
To Reproduce
Steps to reproduce the behavior with the minimal config:

press tab in insert mode

Actual behavior

when I type Esc a zero appears
Expected behavior
write a tab

You should install vim-vsnip.


chore(deps): update dependency mongoose to v6.1.1

Simulators-API has incorrect typing when returning a simulator that need to be corrected. See the tests for #3760

mongoose has already been updated to 6.1.2. Tests for simulators and simulators-api apps both pass.


Remove pkg:test as a direct dependency

https://github.com/kalismeras61/flutter_page_transition/blob/fcde655270103706c6df2b51709ad0781e6aa14c/pubspec.yaml#L12
Pretty certain this is NOT needed at runtime.

@kevmoo  you are right, I've tried a few things. I added it by mistake. Removed!

No worries. Just noticed it. Thanks for doing the safe transition!


[4.0] Regression bug? Admin loading spinner not disappearing after GridField operation

I'm pretty sure this falls under framework and not CMS issues, as I believe it's coming from the admin portion of framework.
After updating SS4 to dev-master today, the CMS loading spinner, i.e.:

...will not disappear following a GridField operation that attempts to return the user back to the main CMS interface.  For example, editing a record from a GridField and then clicking the Back button in the top-left.  This returns me to the interface for the Page with the GridField, but the loading spinner remains and steals focus for the entire CMS.  The only way to proceed is to refresh the CMS in the browser (or delete the spinner in the console).
I have cleared session, cookies, and temp files, plus tried in Chrome and Firefox, but the issue remains.

Just confirmed it also happens within the GridField edit form page, i.e. after creating a new record.

Yes real issue. Not sure why, but thanks for spotting!

I can confirm that this has been happening to me on a framework only project on master, see more on https://github.com/silverstripe/silverstripe-framework/issues/6545#issuecomment-275871452.
Reverting to 4.0.0-alpha4 fixed it for me.

On dev-master of framework I'm having trouble replicating this issue. Can someone confirm of this issue is still around?

Hi @tractorcow - I can confirm that on latest dev-master the issue is gone. 👍

Oh yay. :D


The point at infinity is only representable in the jacobian at y = 1.

(From upstream.) The y coordinate shouldn't be negated if it's zero.
This doesn't break any API invariants, but it does look like you're changing the library to expose more things.
See also https://github.com/scipr-lab/libsnark/issues/60.

Oops, PR from the wrong branch.


[DNM] [Just for testing] [Embedded] Add armv4t to list of recognized architectures

This adds armv4t as a recognized embedded architecture and builds a stdlib module for it.
Since LLVM natively supports armv4t, this is all that's needed to write Swift for the Game Boy Advance, if you combine it with the GBA LLVM toolkit from https://github.com/stuij/gba-llvm-devkit.

@swift-ci please build toolchain

@swift-ci please smoke test

Very nice! 😊


feat: add support for the dayz config file config setting

As a DayZ server admin,
I want the library to surface the new cfg file setting,
so I can query it.
setting:
"enableCfgGameplayFile": "0"

The library already has the ability to upload and download files, so the content can already be handled.
Still need to add the config item.


Content search

For reference: https://www.npmjs.com/package/hugo-elasticsearch

How to deploy on Amperage theme?


fix invalid bit range when allocate ipv6 address

Fixes #2296
Signed-off-by: Leno Hou<EMAIL_ADDRESS>

@houstar thanks for working on this, can you please add some test-cases as well

also TestValidRemoteDriver should be fixed in master, all tests should hopefully pass if you re-run tests

Thanks @houstar for submitting this PR. However, time as passed since it was originally submitted and I'm going to close it for the following reasons:

This repo has been moved to https://github.com/moby/moby/tree/master/libnetwork. Any new work should happen there, and backported in this repo iff required ;
As stated by @fabianfreyer, part of the problem is the use of a uint64 for doing computation on 128 bits. This is getting addressed in moby/moby#43033, although while working on that PR we uncovered other issues that require us to switch to some more advanced data structures to make sure two subnets don't overlap ;


[Storage] Update version numbers to preview.6

Closing this issue as @danieljurek is handling version updates across the board and we dont need service specific issue tracking

How about readmes?

I think we can remove the preview version from the npm install step in the readmes because we'll be releasing with the latest tag rather than the next tag.

@joheredi Please keep in mind and make a PR for this too if you're looking at the readme code snippets.


Logz dotnet

All SDK Contribution checklist:
This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] Please open PR in Draft mode if it is:

Work in progress or not intended to be merged.
Encountering multiple pipeline failures and working on fixes.

[ ] If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
[ ] I have read the contribution guidelines.
[ ] The pull request does not introduce breaking changes.

General Guidelines and Best Practices

[ ] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

SDK Generation Guidelines

[ ] The generate.cmd file for the SDK has been updated with the version of AutoRest, as well as the commitid of your swagger spec or link to the swagger spec, used to generate the code. (Track 2 only)
[ ] The *.csproj and AssemblyInfo.cs files have been updated with the new version of the SDK. Please double check nuget.org current release version.

Additional management plane SDK specific contribution checklist:
Note: Only applies to Microsoft.Azure.Management.[RP] or Azure.ResourceManager.[RP]

[ ] Include updated management metadata.
[ ] Update AzureRP.props to add/remove version info to maintain up to date API versions.

Management plane SDK Troubleshooting

If this is very first SDK for a services and you are adding new service folders directly under /SDK, please add new service label and/or contact assigned reviewer.
If the check fails at the Verify Code Generation step, please ensure:

Do not modify any code in generated folders.
Do not selectively include/remove generated files in the PR.
Do use generate.ps1/cmd to generate this PR instead of calling autorest directly.
Please pay attention to the @microsoft.csharp version output after running generate.ps1. If it is lower than current released version (2.3.82), please run it again as it should pull down the latest version,

Old outstanding PR cleanup
Please note:
If PRs (including draft) has been out for more than 60 days and there are no responses from our query or followups, they will be closed to maintain a concise list for our reviewers.
APISpec:
https://github.com/Azure/azure-rest-api-specs/pull/13317

A couple of minor issues, as noted. In addition:

Please add a link to your swagger PR in the PR description
Please add this project to the mgmt ci by adding a reference to the project directory here: https://github.com/Azure/azure-sdk-for-net/blob/master/eng/pipelines/mgmt.yml#L89
Please create an AssemblyInfo.cs for your dlls, similar to the assemblyinfo for other projects.

Done

@vakunch Please pull the latest from master to help clear the ubuntu issue.


feat: Remove the beta endpoint for Copilot usage

BREAKING CHANGE - Though the removed endpoint was on master it was never in a release!
Removes support for the beta endpoint for Copilot usage metrics, which is scheduled for removal by GitHub by the end of the year, see https://github.blog/changelog/2024-10-30-github-copilot-metrics-api-ga-release-now-available/. Support for the GA endpoint was implemented by https://github.com/google/go-github/commit/717e93fa2808da46013f98feb95275e3f6bedf2b.

@henriklundstrom - I'm confused - wasn't GitHub's OpenAPI spec updated to include your new endpoints?
Should I be updating the OpenAPI spec again?  (I think I updated it two days ago maybe in #3352.)

@henriklundstrom - I'm confused - wasn't GitHub's OpenAPI spec updated to include your new endpoints? Should I be updating the OpenAPI spec again? (I think I updated it two days ago maybe in #3352.)

@gmlewis There are two sets of endpoints for Copilot metrics. They do largely the same things and both of them were launched very recently. First there was a beta launch, and then shortly thereafter a GA version to replace it.
Beta:
The usage endpoints, see https://docs.github.com/en/rest/copilot/copilot-usage?apiVersion=2022-11-28. They are in public preview, and as far as I understand it from this announcement https://github.blog/changelog/2024-10-30-github-copilot-metrics-api-ga-release-now-available/, will be discontinued by the end of the year. This PR removes support for those endpoints, which was originally added about a month ago with https://github.com/google/go-github/commit/5e806b6a7e3f31f93d5e7b6225cd60f1d71d0c5a.
GA:
The metrics endpoints, see https://docs.github.com/en/rest/copilot/copilot-metrics?apiVersion=2022-11-28. They are in GA, were introduced very recently, after the usage endpoints, and as far as I understand it, are intended to replace them. These are the endpoints I implemented support for a few days ago with https://github.com/google/go-github/commit/717e93fa2808da46013f98feb95275e3f6bedf2b, and they will remain after this PR.

@gmlewis I should clarify as well that yes this is a breaking change in the sense that it removes the endpoints added by https://github.com/google/go-github/commit/5e806b6a7e3f31f93d5e7b6225cd60f1d71d0c5a, but that commit has not yet made it to any release, so in that sense it is not breaking with any previous release.

@henriklundstrom - thank you for the excellent explanation. That makes perfect sense.

Thank you, @alexandear !
Merging.


extend the query builder with sensible extension queries

Like "occurs during phase"
add any other ideas.

I assume that extension queries we show will depend on which term is selected?  A bit like how Canto offers different extensions for each term.
So we'll need quite a bit of configuration.

I'll put this on the list for a future meeting once the decks are cleared a bit.

I think this could be a bit simpler.
I suggest we just include a new 'type' of query  under "GO"
"Search phases or responses"
Retrieve genes annotated to a function process or location during a particular phase, or during a response to a particular stress (e.g. oxidative, DNA damage, osmotic).
There are not many query types that would be useful (for example the extensions of a specific gene product is available from the 'target of ' section of the gene page).
We could add additional queries later if I think of useful ones.

SO terms  and CHEBI chemicals in GO extensions might also be useful (I am not sure how common CHEBI terms are)

removed "next" as there is a lot of stuff more important.


Allow to pass undefined to modifier prop

Allow having isBig={undefined} as discussed in https://github.com/4Catalyzer/astroturf/issues/56
Since it could be a popular mistake.

Can we release it? My colleges afraid of these warnings.

@jquense friendly ping =^_^=


Updating Reply data structure

Ever since Version 6610 of Traceroute data, the reply result of a hop has err to be either a string or integer.
Case: Reply
"err" -- (optional) error ICMP: "N" (network unreachable,), "H" (destination unreachable), "A" (administratively prohibited), "P" (protocol unreachable), "p" (port unreachable) "h" (beyond scope, from fw 4650) (string) Unrecognized error codes are represented as integers
While using this library on the REST API, I encountered a Parsing error on that exact attribute because it was given a number instead of a string.
To combat this, I created a type ErrWrapper that is of type string. I set the Err attribute to type ErrWrapper. I made a custom UnMarshal Method on this type to convert it to a string. Let me know if there is a more elegant solution.

Or try https://github.com/DNS-OARC/ripeatlas/pull/26 | https://github.com/jelu/ripeatlas/tree/trace-reply-v4610

Sure here is the code snippet from my current project:
`func GetStaticTraceRouteData(measurementID string, startTime, endTime int) ([]measurement.Result, error) {
a := ripeatlas.Atlaser(ripeatlas.NewHttp())
channel, err := a.MeasurementResults(ripeatlas.Params{"pk": measurementID, "start": startTime, "stop": endTime})
if err != nil {
	log.Printf("Cannot get measurment results from Ripe Atlas Streaming API: %v\n", err)
}
var traceroutes []measurement.Result
for measurementTraceroute := range channel {
	if measurementTraceroute.ParseError != nil {
		log.Printf("Measurement could not be parsed: %v\n", measurementTraceroute.ParseError)
		log.Printf("%+v", measurementTraceroute)
	} else {
		traceroutes = append(traceroutes, *measurementTraceroute)
	}
}

return traceroutes, nil`

And I call the function with:
actualTraceRoute, _ := tracerouteData.GetStaticTraceRouteData("5001",<PHONE_NUMBER>,<PHONE_NUMBER>)

Fixed by #26


Trying to get in touch regarding a security issue

Hey there!
I'd like to report a security issue but cannot find contact instructions on your repository.
If not a hassle, might you kindly add a SECURITY.md file with an email, or another contact method? GitHub recommends this best practice to ensure security issues are responsibly disclosed, and it would serve as a simple instruction for security researchers in the future.
Thank you for your consideration, and I look forward to hearing from you!
(cc @huntr-helper)

Hello @benharvie, if the issue is not related to personal data or credentials you can very well disclose it here please.


Issue Loading OmniGen Model - FileNotFoundError

Hello everyone,
I'm encountering an issue while trying to load the OmniGen model for image generation. I'm using the Shitao/OmniGen-v1 model, and here is the code I'm using to load it:
pipe = OmniGenPipeline.from_pretrained("Shitao/OmniGen-v1")

However, I'm getting the following error:
FileNotFoundError: [Errno 2] No such file or directory: 'C:\\Users\\69299\\.cache\\huggingface\\hub\\models--Shitao--OmniGen-v1\\snapshots\\58e249c7c7634423c0ba41c34a774af79aa87889\\model.pt'

I have already checked the following:

Confirmed that the model path is correct, and the model file does not exist in the expected directory.
Tried clearing the Hugging Face cache (huggingface-cli clear-cache) and re-downloading the model.
Checked my network connection to ensure I can access the Hugging Face Hub.
Ensured that my user account has sufficient permissions to access and write to the cache directory.

However, the problem persists. It seems like the model file cannot be downloaded to the local cache. Here are some of my questions:

Is there another way to force download the model files locally?
Is this error due to an issue with Hugging Face's servers, or is it a problem with my local environment configuration?
Has anyone else encountered a similar problem and found a solution?

Any help or suggestions would be greatly appreciated!

This description should clearly outline the problem you're facing and the steps you've taken to try and resolve it. Hopefully, this will elicit useful responses from the forum community.

@wjf68888 , model.pt file have been deleted in HF repo, and it's not used in latest code.  You can clone latest code to use safetensor instead of pt.
git clone https://github.com/VectorSpaceLab/OmniGen.git
cd OmniGen
pip install -e .


Order of rules when combining new Grammar

Hey @leipert,
While working on the emphasis rules, I've noticed that emphasis is matched before links are, though I specifically specify that links come before emphasis in /rules/main.cson. Could you confirm if the order specified is actually preserved when the composited grammar is created?

After some trial-and-error research I believe the order of the rules in the grammar has absolutely no effect on anything. I can't be bothered to dig into first-mate, but I believe the input is just interpreted character by character, and any patterns that match stay in the pool. So a kind of reversed first-come-first-served.
A possible solution would be to create an intricate tree-like structure of includes, but I don't think it is worth the effort.


Handle panic during conversion to connectCode

What this PR does / why we need it:
If an unhashable error is given, the error cannot be converted to a connecteError with a map, causing a panic and shutting down the server.
Which issue(s) this PR fixes:

Fixes #944
Special notes for your reviewer:
Would it be a good idea to log errors in recover?
Does this PR introduce a user-facing change?:

Additional documentation:

Checklist:

[x] Added relevant tests or not required
[x] Didn't break anything

Summary by CodeRabbit

Bug Fixes

Improved error handling in the connection status function to enhance resilience against runtime errors.
Implemented panic recovery to prevent unexpected failures during execution.

@krapie No, it doesn't. Should we print or log errors in this case?

@blurfx I think printing out error details may help us to take actions upon that specific error like mongo.CommandError.

@krapie @blurfx It seems that an error will propagate to the callers and be output by the interceptor. 🤔
https://github.com/yorkie-team/yorkie/blob/54910c172e5d648235777c49a532ccc8eefdf222/server/rpc/interceptors/default.go#L52-L55


Pull "Build" page out into a separate repository

Lets consider turning this:
https://www.learnplasma.org/pages/build.html
Into ➡ https://github.com/ethsociety/awesome-plasma
The "build" page can be "build" or "ecosystem" in this site. The static generator can pull it in as a submodule or some technique similar to that.

Great idea, but the new repo and the "Build" page could co-exist. On GitHub, more tangential stuff could be added, e.g. a repo documenting and implementing a sparse Merkle tree.

Going to close this for now. Seems like enough work to just manage this ATM.


[Parse] Improve diagnostic for deprecated protocol<...> syntax

What's in this pull request?

Don't emit deprecated warnings for incomplete protocol<...>.
func fn(x: protocol<P) {}

Because other error diagnostics are already emitted
Moreover, the current fix-it tries to remove ) after P

Different message for single protocol compostion.
typealias MyError = protocol<Error>

Because "join the protocols using '&'" is not relevant in this case

CC: @DougGregor, @joewillsher

Before merging this pull request to apple/swift repository:

[ ] Test pull request on Swift continuous integration.

Triggering Swift CI
The swift-ci is triggered by writing a comment on this PR addressed to the GitHub user @swift-ci. Different tests will run depending on the specific comment that you use. The currently available comments are:
Smoke Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please smoke test
    All supported platforms     | @swift-ci Please smoke test and merge
    OS X platform               | @swift-ci Please smoke test OS X platform
    Linux platform              | @swift-ci Please smoke test Linux platform

A smoke test on macOS does the following:

Builds the compiler incrementally.
Builds the standard library only for macOS. Simulator standard libraries and
device standard libraries are not built.
lldb is not built.
The test and validation-test targets are run only for macOS. The optimized
version of these tests are not run.

A smoke test on Linux does the following:

Builds the compiler incrementally.
Builds the standard library incrementally.
lldb is build incrementally.
The swift test and validation-test targets are run. The optimized version of these
tests are not run.
lldb is tested.

Validation Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please test
    All supported platforms     | @swift-ci Please test and merge
    OS X platform               | @swift-ci Please test OS X platform
    OS X platform               | @swift-ci Please benchmark
    Linux platform              | @swift-ci Please test Linux platform

Lint Testing
    Language     | Comment
    ------------ | -------------
    Python       | @swift-ci Please Python lint

Note: Only members of the Apple organization can trigger swift-ci.

This looks great, I think maybe the error message should specify that the syntax ‘is deprecated and not needed here’ rather than implying the construct is useless?

@joewillsher Thank you for the suggestion! I'll do that.
Sorry, I'm not good at English 😓

No problem at all, thanks doing this!

Updated warning message for single protocol composition: protocol<P>

Thanks all!
@swift-ci please test and merge.

@swift-ci Please smoke test

@swift-ci  Please test

@swift-ci Please test

Tests passed, merging.

Looks great, thank you!


C# 300-Longest-Increasing-Subsequence.cs

File(s) Modified: Create 300-Longest-Increasing-Subsequence.cs
Language(s) Used: csharp
Submission URL: https://leetcode.com/submissions/detail/789347306/

Thanks, @agnihotriketan!


Jest fails on use of require('warning')  v0.16

Jest tests which include React fail anywhere require('warning') is used by RN, which is in 57 places. I am using v0.16.0 and latest node. The first error is as follows.
Unexpected token ...
at Object.exports.runInContext (vm.js:43:16)
at Object. (node_modules/react-native/node_modules/react-haste/renderers/dom/shared/DOMPropertyOperations.js:19
If I remove the use of 'warning' in that file then the error is triggered on the next file which uses it

@adriansprod Can you test if this still happens with master?

cc @cpojer

I don't think this is still going to be an issue with jest 0.9.0.


Who have seen a message and support it

There are multiple members in a chat room, and I want to know a message I sent, which members have seen it,
Currently I use this package, but I found that seen is a boolean value, and I can only know if it has been viewed, not who has seen it
Can it be modified to support this feature

Yes it's a nice feature, I'll consider it as a future development

Hello @antoine92190
I hope all is well.  I just wanted to check in to see if you have planned this feature in the near future.  I too, would like to see this available.
Thanks!


Move evidence between operations

Provide the ability to move evidence from one operation to another. This is not as straightforward as just changing the foreign key in the row because the associated tags are references to tags that exist in the operation and not globally. Based on the recently added work to allow tagging at creation time, we have two options:

Delete tags that exist then move the evidence over
Try to match referenced tags to existing ones in the other project or create new ones, if they don't exist, remove existing tag references, the move the evidence over.

I'm open to either currently.

Questions on the semantics here:

Is this sharing evidence, or moving, or either (meaning: are we implementing this because someone uploaded evidence to the wrong operation, or are we implementing this because two operations happen to need the same evidence... or both?)
(in case this is a proper move) What do we do if the evidence is paired with a finding? Do we disallow moves here, or do we remove this evidence from the finding? I'm not sure how viable trying to re-associate moved evidence with some pre-existing finding... unless that finding consists entirely of that single evidence.

Presumably all other data-oriented aspects are copied over, which should be pretty trivial.

With respect to mapping tags, I suppose we'd compare names, and if they were exact matches (maybe ignoring spacing and case) we'd re-associate the evidence with the "new" tag. I'm somewhat concerned that generating actual new tags would create a kind of tag bloat, where you end up with two tags that are functionality identical, but technically separate. A guided process to re-map tags seems excessive to me, so I suppose I'd recommend we do the following with respect to re-tagging:

Get a list of associated tag names for the specific evidence
disassociate all tags from that evidence
Get a list of all tags for the "new" operation
For each tag, check if there's an approximate match.

If so: associate that tag with the moved evidence
If not: ignore that tag

This should help limit tag bloat, while allowing some reduced effort in migrating evidence.

Small recap from offline discussion:

For tags, we will try to match when tag names are close, and drop tags that are not close. Closeness metric is TBD, but likely something along the lines of mentioned above.
For tags that are not matched, we may opt to display what tags are being dropped, allowing users an easy to to re-add tags if they are missing.
For findings, we will drop evidence from the finding. It will be incumbent on the user migrating evidence to re-associate evidence with a finding in the new operation.

Addressed in PR #12


Updating run_tests with increased Java thread stack size

Tests sometimes fail with java.lang.StackOverflowError, during plan verification tests. It's likely a consequence of Catastrophic Backtracking (https://www.regular-expressions.info/catastrophic.html)
A workaround to this issue is to bump up the thread stack size for the java app as follows:
java -Xss40m ...

@Agirish change looks good, I am assuming we have a clean test run. LGTM.

Thanks! Yes, I've tested this change. Also, it's already in use in other branches - making this change for master branch now.


vimeo download url not working: racing4everyone.eu

I cannot download vimeo url https://player.vimeo.com/video/180633686
its says it not the embedded url
it is a private video of a formula 1 race from
http://racing4everyone.eu/2016/07/30/formula-1-2016-round12-germany/
I used to be able to download from this site....but not anymore
Can u please check thanks

It's not possible to download or watch with direct URL since they require passing Referer header, Use original URL http://racing4everyone.eu/2016/07/30/formula-1-2016-round12-germany/.


Assign random reviewer to PR

Summary
Assigns a random reviewer from .github/reviewer-lottery.yaml to the PR when it is marked as ready to review.
Test Plan
Issues
Closes #

Least messy actions PR history


ReferenceError: x is not defined

Note: for support questions, please join our Discord server

I'm submitting a ...
[x ] bug report
[ ] feature request
[ ] question about the decisions made in the repository

Action taken (what you did)

Expected result (what you hoped would happen)

Actual result (unexpected outcome)

Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, etc)

I found error while i accessing exchane bitcoin.co.id. Here the result:
ReferenceError: x is not defined
at Bitcoincoid._request (C:\Users\Mahar Santoso\Downloads\gekko-stable\gekko
-stable\node_modules\bitcoin-co-id\index.js:65:20)
at Bitcoincoid._get (C:\Users\Mahar Santoso\Downloads\gekko-stable\gekko-sta
ble\node_modules\bitcoin-co-id\index.js:20:8)
at Bitcoincoid.getTrades (C:\Users\Mahar Santoso\Downloads\gekko-stable\gekk
o-stable\node_modules\bitcoin-co-id\index.js:119:8)
at Trader.getTrades (C:\Users\Mahar Santoso\Downloads\gekko-stable\gekko-sta
ble\exchanges\bitcoin-co-id.js:113:20)
at Trader.bound [as getTrades] (C:\Users\Mahar Santoso\Downloads\gekko-stabl
e\gekko-stable\node_modules\lodash\dist\lodash.js:729:21)
at Fetcher._fetch (C:\Users\Mahar Santoso\Downloads\gekko-stable\gekko-stabl
e\core\budfox\marketFetcher.js:75:16)
at Fetcher.bound [as _fetch] (C:\Users\Mahar Santoso\Downloads\gekko-stable
gekko-stable\node_modules\lodash\dist\lodash.js:729:21)
at Fetcher.fetch (C:\Users\Mahar Santoso\Downloads\gekko-stable\gekko-stable
\core\budfox\marketFetcher.js:88:8)
at Fetcher.bound [as fetch] (C:\Users\Mahar Santoso\Downloads\gekko-stable\g
ekko-stable\node_modules\lodash\dist\lodash.js:729:21)
at Manager.retrieve (C:\Users\Mahar Santoso\Downloads\gekko-stable\gekko-sta
ble\core\budfox\marketDataProvider.js:31:15)
RECEIVED ERROR IN GEKKO<PHONE_NUMBER>71328
can anyone give me some advise ? Thank you

edit on node_modules/bitcoin-co-id/index.js

for (var key in options) {
requestOptions[key] = options[key]; // line 65
}

Hi Reza, i've change [Key] with my API Key, but still "RECEIVED ERROR IN GEKKO"

haha
requestOptions[x] = options[x]; // line 65
change to
requestOptions[key] = options[key]; // line 65
dont change with ur API key lol

maturnuwun suhu :)
thanks a lot


Dropdatabase is undefined

node_modules/mongoose-seeder/lib/mongoose-seeder.js:258
mongoose.connection.db.dropDatabase(function(err) {
^
TypeError: Cannot read property 'dropDatabase' of undefined

Hi @ecasilla
This is not really well documented but I guess that the problem is that you are not waiting for mongoose to be connected with the database.
Can you try something like this and let me know if it fixes the problem?
mongoose.connect(config, options);

mongoose.connection.on('connected', function() {
    seeder.seed(data);
});

Thanks

Closed due to no response.
Please reopen if you still experience the problem.


Check peer liveness

Goal: remove peers that timeouts often

add peer liveness check service:

periodically send ping request to peers
store ping responses in peer store metadata book
disconnect peers not responding to ping

Additional measures if those are timeouts only on block by range requests (my suspicion that these are shut down peers that aren't detected on libp2p side).

Can you ping peers as much as you can without that affecting your peer score?

Depends on client, I don't think we should spam it every few seconds though

closed with #1428


appium desktop1.16.0安装失败，有成功的吗

@myl8888 Could you please describe the issue briefly.

Closed due to no response.


chore(stable): Update stable to 3.0.1

:tada: This PR is included in version 3.0.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Clean Gameday View Plugin Small Bug

Hey suchmeme, new to this github thang so please bare with me. I wanted to report a small bug with the clean gameday view plugin for steam deck. The bug is when you are in the gameday view interface and scroll down, the top bar does not always come down properly only on some occasions it does when it feels like it but not all of the time. Get back to me as soon as you can.❤

This is a duplicate of #11


Clean source from remaining externs

Definitive, working and cleaned version of my previous PR

Ahh this is perfect, ty!!


Add CHANGELOG and v0.2.0 entry (build run with all-features doesn't work yet)

Add CHANGELOG and update to v0.2.0. Build doesn't work yet with all-features after updating the parser and ast packages to v0.2.0. We should fix those before doing the actual GitHub and crates.io releases.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

cargo build and cargo test work for this PR but running with "--all-features" (as part of the Code Coverage step) shows the build issues from upgrading the parser + ast to v0.2.0. I'll merge in the PR to at least add the CHANGELOG and cut a separate issue to track fixing

Created https://github.com/partiql/partiql-rust-cli/issues/4 to track fixing build failures before 0.2.0 cli release.


Ubuntu 17.04 installing atom results in segmentation fault, using snap results in broken html

So I am trying to atom with Ubuntu 17.04.
It isn't going very well (see https://github.com/atom/atom/issues/11743 )
So I tried using snap to install atom. Using snap works.... but only if you launch atom with sudo, e.g. sudo snap run atom <dir>, as snap run atom <dir> does nothing. When launching with sudo 1/10 times you will get atom as it is meant to be,  8/10 times you will get nothing, and 1/10 times you will get the following image

I have no idea what is going on.
So any ideas on how to get atom to work properly on 17.04 would be appreciated

Thanks for reaching out!
The snap version of Atom is community-maintained and not officially supported by the Atom maintainers. Therefore, you'll have to ask the snap package maintainers for guidance about issues. You can find out more about why we chose to not support unofficial distributions here.
See https://flight-manual.atom.io/getting-started/sections/installing-atom/#platform-linux for installing Atom from the official repositories.

For this issue: You can click the red icon in the top right corner to see an error message that might indicate what the problem is.

Hi @Ben3eeE thanks for the prompt response. My issue had two parts, the latter is snap - the former is the segmentation fault (when installed on linux without snap) which makes atom also unusable.

There is an open issue https://github.com/atom/atom/issues/15944 for a segfault on start that has been tracked down to electron and the suggested workaround is to clear XDG_CONFIG_DIRS /cc: https://github.com/atom/atom/issues/15944#issuecomment-346597890.
Though this issue is seems to be specific to Ubuntu 17.10?
Other things you can try are listed in the flight-manual debugging guide: https://flight-manual.atom.io/hacking-atom/sections/debugging/

@Ben3eeE  Im still working through the debugging guide, but that linked solution does not work in my case

@Ben3eeE also, it is interesting that launching via sudo is what aids in making this work


To test CP Firewall (IaaC) upgrade in ECF Forge

Describe the Issue
To test CP Firewall (IaaC) and ensure firewall upgrade does not affect the traffic
Additional Context
TBA

Upgrade likely to be done via ASEA configuration
Linux Upgrade
GAIA OS Upgrade

Acceptance Criteria

[ ] Detailed Step
[ ] Test Step
[ ] Rollback plan
[ ] Firewall is functioning as before after upgrade

.
.
.
.
.
.
.
.
.
.
.
Extra Template Info
Definition of Ready
These set of conditions will need to be met in order to bring a ticket into the sprint and start work. Protects the team from unclear requirements.
Issues (Task/Story/Spike) aligned to an EPIC and linked appropriately.
Assigned to the appropriate CPF MEMBER (and is not left blank in ZenHub) at the start of sprint (1st day of the sprint)
Acceptance has been defined for the issue and has been reviewed with CPF team and approved by the necessary approver.
Has been sized and estimated by the delivery team.
Detailed breakdown of the steps required to complete the story in the additional context
Any additional specifications have been documented, reviewed with CPF and approved by the necessary approver.
Acceptance Criteria
A set of pre-defined requirement that need to be met in order to mark the user story as “done”.
It should be testable with no room for interpretation
It should be either “pass” or “fail”
It should be clear enough for business stake holders to understand
As part of the user story, it should be written from the user perspective
A well written acceptance criteria is great for

managing expectations
defining scope
reducing ambiguity
establishing testing criteria for QA
Given (Pre-condition)
When (Action)
Then (Outcome)

Definition of Done
These set of conditions are met for work to be considered as complete on an issue.
All acceptance criteria(s) have been validated.
All the necessary documentation for the issue has been uploaded to Teams.
Functionality has been tested when applicable.
Functionality has been demonstrated to the relevant stakeholders (where applicable).
Story has been scheduled for a Sprint Demo/community update and impacted teams invited to the Demo.
Stories accepted by PO and documented for potential sharing with impacted users.

Documented = Captured in Community Update (CU) deck
Release notes = aspirational goal of providing a bulleted list of features and changes that our users can touch. Was going to store them in our Cloud Pathfinder repo. Can also display to users in the CU

As SECOPS (Chris C.) is taking up firewall support/update/migration, firewall ticket become irrelevant.


Next Button Issues When Inserting Pages

I discovered a bug that occurs during the WizardPage.Commit event.
If you Insert pages during the Commit event that appear after the WizardPage that just triggered the Commit event then it skips past all the inserted WizardPage controls.
For example:
Private Sub WizardPage1_Commit(sender As Object, e As AeroWizard.WizardPageConfirmEventArgs) Handles WizardPage1.Commit
    Dim pages As List(Of AeroWizard.WizardPage) = New List(Of AeroWizard.WizardPage)

    'Dynamically create the WizardPages
    Dim row As DataRowView
    For Each index As Integer In checkedListBox.SelectedIndices
        row = DirectCast(checkedListBoxCameras.Items(index), DataRowView)
        pages.Add(CreateCameraWizardPage(row("Name").ToString, row("IpAddress").ToString))
    Next

    'Insert the pages
    WizardControl1.Pages.InsertRange(2, pages)
End Sub

That event will skip all pages inserted to select the page that appeared next in the designer.
Originally posted: 2016-11-23T19:24:30

Check to make sure the NextPage property on your current page is set to null or set to the first page you've inserted.
Originally posted: 2017-01-12T12:14:35

No response.
Originally posted: 2017-03-13T11:21:20


Evaluate using HOSTMEM where available

HOST memory on selected shells allows direct DMA access into host DDR from the FPGA. Using HOST memory instead of FPGA DDR/HBM may reduce the latency of host-to-host collectives or primitives. Performance implications on throughput must be evaluated.

Host memory capability now present (although not extensively verified) in latest dev branch. Closing


Build eget from source

This makes it easier to get pre-release features
and simplifies the Dockerfile.
Change-type: patch

I self-certify!


Fix index-state syntax

Description
The second index-state stanza completely ovverides the first, resetting hackage index state to HEAD. See haskell/cabal#8568
Checklist

Branch

[ ] Commit sequence broadly makes sense
[ ] Commits have useful messages
[ ] The documentation has been properly updated
[ ] New tests are added if needed and existing tests are updated
[ ] If this branch changes Consensus and has any consequences for downstream repositories or end users, said changes must be documented in interface-CHANGELOG.md
[ ] If this branch changes Network and has any consequences for downstream repositories or end users, said changes must be documented in interface-CHANGELOG.md
[ ] If serialization changes, user-facing consequences (e.g. replay from genesis) are confirmed to be intentional.

Pull Request

[ ] Self-reviewed the diff
[ ] Useful pull request description at least containing the following information:

What does this PR change?
Why these changes were needed?
How does this affect downstream repositories and/or end-users?
Which ticket does this PR close (if any)? If it does, is it linked?

[ ] Reviewer requested

bors try

bors try

bors try

bors merge

bors cancel

bors merge

bors merge


[Coverity CID :186847] Parse warnings in /tests/kernel/mem_protect/mem_protect/src/inherit.c

Static code scan issues seen in File: /tests/kernel/mem_protect/mem_protect/src/inherit.c
Category: Parse warnings
Function:
Component: Tests
CID: 186847
Please fix or provide comments to square it off in coverity in the link: https://scan9.coverity.com/reports.htm#v32951/p12996

False positive, Hence closing it here and making it false positive in coverty.


[Multi-Actions] handle content fragment role on core side

get rid of the hack in dust apps to transform them into functions
do the right thing depending on model (likely, function_call + function for everyone except anthropic, user message for anthropic)

Discussed IRL with @spolu, we'll try a first version where we always include the content fragments messages inside the next user message as required by Anthropic, and see how it goes. This will be done in renderConversationForModelMultiActions at first.
If we need something specific for each model, we'll move it to core.

This is based on the response from Anthropic which suggest using a user message.
We can enforce the invariant that an array of content_fragments are always followed by a user message
Assuming this works with Mistral and OpenAI this would open a path to handling this in front as a first iteration.

👌

Done in this PR: https://github.com/dust-tt/dust/pull/5147


Export first character cannot be number

crasche@f1r2s16:~$ export 1abc
bash: export: `1abc': not a valid identifier

The var name can not start with a number. First char has to be alpha

fixed in 47b099e8786bdd4fc071a8740e55f98e23c3a7e0


Support zip export

I want to add an extension that adds zip and unzip commands to the CommandManager, with the goal of being able to unzip a .zip archive into your fs, and to export your fs to a .zip.  Prior art in:

https://github.com/filerjs/filer/blob/08f4b7e528b8891feec301f549ec9e58a7496304/src/shell/shell.js#L479-608 + https://github.com/Stuk/jszip
https://github.com/humphd/nohost/blob/master/src/webserver.js#L63-L84

The code for zip is in ZipUtils, we just need some UI for when to trigger it.

@flukeout, we need some kind of UX for doing this, the backend is in place.  The basic use case is: "Click here to download a .zip file with all your project files/folders in it."


Add every igloo

Assets:
https://drive.google.com/file/d/1BjpMunXmFGUubPLuDxZL8Y0pQpk9m1rj/view?usp=sharing
Raw:
https://drive.google.com/file/d/1Bl3VFwAPguojeaiQGuW-Hxds3wo1LMUd/view?usp=sharing
Explanation of all changes
src/data/igloo.js

Added all igloo scene data.

src/scenes/components/Button.js

Change setFrame functions to always keep the original size and origin of the base image, so that igloo doors which have pivot points set in TexturePacker don't randomly move when hovered over.

src/scenes/igloos/IglooScene.js

Checks if an igloo has a floor before setting its depth. This prevents the game crashing on an igloo with no floor.

Checks for a -igloo-physics.json file first before looking for a -physics.json file. This is so IglooScenes with the same name as RoomScenes (like cave) don't accidentally use each other's physics data. Same naming convention is used with all animation, pack and multiatlas files, for the same reason.

src/scenes/interface/game/iglooedit/gridview/GridView.js

Filters igloo inventory by which igloos are available in crumbs, rather than just != 0.

Also:

Updated Basic and all igloos that use the same physics to have correct triggers. (They were previously the wrong size).
Updated the existing 12 igloos to have doors which open when hovered and move to the trigger when clicked.
Updated the existing 12 igloos to open the map when standing on the trigger, as they should.

if my above comment is actually an issue, then i have a proposed solution
what if all igloo scene keys were appended with something like "Igloo"?
so IglooScene.js would have the following:
    constructor(key) {
        super(`${key}Igloo`)

And then createIgloo in RoomFactory.js would be something like this:
    createIgloo(args) {
        let config = this.igloos[args.type]

        const key = `${config.key}Igloo`

        if (config.key in this.scene.manager.keys) {
            this.scene.start(key, { args: args })

            return this.scene.get(key)

        } else {
            return this.scene.add(key, config.scene, true, { args: args })
        }
    }

@ChrisCPI

what happens when a room and an igloo share the same scene key? for example the Cave igloo and the actual Cave room having the same key "Cave"

You're right, I didn't test that in vanilla Yukon. It does indeed load the wrong scene in this case. Good fix proposal, will implement something similar.

Fixed.


Minor: add valueChangingOperation and mergeNode to StreamsGraphNode#toString

This PR adds valueChangingOperation and mergeNode to StreamsGraphNode#toString
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

\cc @guozhangwang @mjsax

Not sure what we want to include in toString() -- what about repartitionRequired and hasWrittenToTopology -- what is the reason to exclude them @bbejeck

what is the reason to exclude them @bbejeck

@mjsax just a subjective decision on my part, I didn't feel they were required.  But thinking more about it if we include one of those fields, we should add all of them, so I'm okay with it.

@bbejeck the changes seem not including valueChangingOperation part?

@bbejeck the changes seem not including valueChangingOperation part?

Not sure I follow, as valueChangingOperation is included in the toString


[builder] update uberon and tissue_general mapping to schema 4 standard

Fixes #1017
Fixes #841

@ebezzi - re-tagging you, as we added another fix to this (single-sourcing the TissueMapper code, resolving #841)


adds parcel data set to database

Added parcel data to ingestion code.
Note - data for NL000414 uses "U" for parcel_x/y values instead of "N" for null. We should probably have this cleaned up in future updates from prescat.

@jkwening re: the "U" for nulls, you can add it to the list of null values in the Cleaner for that table, like this:
row = self.replace_nulls(row, null_values=['U', '','Null',None])


CDS-92138 K8s Patch Step

https://harness.atlassian.net/browse/CDS-92138
Added a new topic in the CD documentation for Kubernetes Patch step

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://662e3780d291c3b530ab4723--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://662e3843d291c3b5eeab4728--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://662e38a1d83001b362070267--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://662e38dd1ac312b6a32252d9--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://662e3925b91121b5c557cf19--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://662f844d51b60b04353a79ea--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://662f84fa33d8c50515b9cc66--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://6630b0c2bf6a2ea04e6b8e3f--harness-developer.netlify.app


iptables: 1.4.21 -> 1.6.0

Things done

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

[x] NixOS
[ ] OS X
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

! Do not merge without #15196 !
This was already here but reverted because of a bug in connman.
The bug is now fixed (See #15196), so we can reintroduce the chance.
I'm not sure if I've done it correctly (cherry-picking the original commit or if i should have reverted the "reverts update") :grey_question:

I suppose it doesn't make that much of a difference, but I think we usually revert reverts


Fixed (Bug) Copper Prices are negative sometimes

https://discord.com/channels/1001847734766145607/1117804377328078928

Yes I opened a whole new pull request for this

Will you add the other issues? or do extra prs

Yes I opened a whole new pull request for this

Maybe

There's a chance the one I just pushed that fixes https://discord.com/channels/1001847734766145607/1167150855892512869 might stop your minecraft from starting up.
Also I need to remake the PSS public data system ASAP

I think I'm gonna change it so the public data system first will look for the config file. If there is nothing in the config file it will use the one from the repo first while requesting the new data. I will also make it so it updates every 24 hours

Also add a /pssupdaterepo command

Yeah, I'll add an update repo and reset repo command

Actually the best way to do this would be upon startup, unpack the jar if there's not - already files there

I mean do you want to test it?

eeh im lazy, so no


support for cell merge? (colspan, rowspan)

@TangMonk,
I am working to roll out a preliminary version of this feature in the coming release. The whole concept of HTML parsing is rather new to me, and to be frank, was not the initial route that I wanted to take with this plugin. With that being said, times are changing; I agree that capturing the presence of merged cells (either columns or rows) and being able to export those filtered results is a logical, intriguing, and viable next step for the TableExport plugin. I'll keep you all posted on the status.

The recently added colspan support doesn't quite work properly - it doesn't handle multiple colspanned cells in a row.
The fix seems to be quite simple however(at least it works for my problem case).
These 2 if blocks:
if (val.hasAttribute('colspan')) {...}
if (val.hasAttribute('rowspan')) {...}
should go before this one
if (rcMap[ir] && rcMap[ir][ic]) {...}
Because what happens is it detects the first colspan correctly, then in the next cell it goes into if (rcMap[ir] && rcMap[ir][ic]) and misses that it also has colspan.
Example table:
`
A1C1Should be E1, is D1
`
Anyway thanks for the script, keep up the good work!

Thanks for catching this, and more importantly providing a compendious
explanation and example. I had a feeling that I missed something with the
colspan/rowspan feature implementation. Keep an eye on the repo; I'll try
to get this patched this evening or tomorrow.
On Wed, Sep 7, 2016 at 7:43 AM, Edgars<EMAIL_ADDRESS>wrote:

The recently added colspan support doesn't quite work properly - it
doesn't handle multiple colspanned cells in a row.
The fix seems to be quite simple however(at least it works for my problem
case).
These 2 if blocks:
if (val.hasAttribute('colspan')) {...}
if (val.hasAttribute('rowspan')) {...}
should go before this one
if (rcMap[ir] && rcMap[ir][ic]) {...}
Because what happens is it detects the first colspan correctly, then in
the next cell it goes into if (rcMap[ir] && rcMap[ir][ic]) and misses
that it also has colspan.
Example table:

A1C1Should
be E1, is D1

Anyway thanks for the script, keep up the good work!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/clarketm/TableExport/issues/11#issuecomment-245303210,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJfv7jna7geQg3DmJCO5z9fTMzXwPgAmks5qns2ggaJpZM4I-zTK
.

--
Travis M. Clarke
Master of Business Administration**Master of Science in Industrial &
Systems Engineering
[image: Description: Description: Description:
<EMAIL_ADDRESS><EMAIL_ADDRESS>(804)398-8851
https://www.facebook.com/profile.php?id=7817356
https://twitter.com/TravisClarke3
https://plus.google.com/u/0/+TravisClarke87
https://www.linkedin.com/profile/view?id=86660665
http://stackoverflow.com/users/4279440/travis-clarke

Duplicate of Rowspan and Colspan #27.


Specifying a database port in DATABASE_URL does not work for connections on localhost

Setup
Versions

Rust: rustc 1.44
Diesel: 1.4.4
Database: mysql  Ver 15.1 Distrib 10.4.13-MariaDB, for Linux (x86_64) using readline 5.1
Operating System: Arch

Feature Flags

diesel: features = ["mysql", "chrono"]

Problem Description
Specifying the database port in DATABASE_URL does not work for localhost.
What are you trying to accomplish?
Connect to a mysql database that does not run on the default port (13306 instead of 3306).
DATABASE_URL=mysql://root:test@localhost:13306 diesel database reset

What is the expected output?
Connecting to a different port should work.
What is the actual output?
Diesel still tries to connect to 3306.
Are you seeing any additional errors?
Nope
Steps to reproduce
Start a database on a non-default port, for example:
docker run -e MYSQL_ROOT_PASSWORD=test --name test-db -p 13306:3306 mariadb:10.4

Then run any diesel command, for example
DATABASE_URL=mysql://root:test@localhost:13306 diesel database reset

This does not work, diesel still tries to connect to 3306. If you replace localhost with <IP_ADDRESS> it works as expected.

We are passing the port correctly to the lower level native mysql_real_connect connection function here. Therefore this seems to be caused by libmysqlclient itself as it tries to be helpful. According the libmysqlclient documentation here, the function does try to use a unix socket on linux if the host name is localhost, therefore the port number does not have any there.
Closed as this is not a bug in diesel itself.


Problems with PHP formatting

hi,i have a piece of code. As follows
        $college_jg_id = $admin->college_jg_id;
        $year = $admin->year;
        $year_arr = explode(',', $year);
        $class_No_id = $admin->class_No_id;
        $class_No_id_arr = explode(',', $class_No_id);
        $this->where = ['college_jg_id' => $college_jg_id];
        $this->whereIn[] = ['grade', 'in', $year_arr];
        $this->whereIn[] = ['class_No_id', 'in', $class_No_id_arr];

When I need to format. The following situation occurs where the code is not aligned but the equals sign is aligned
$college_jg_id     = $admin->college_jg_id;
$year                   = $admin->year;
$year_arr             = explode(',', $year);
$class_No_id       = $admin->class_No_id;
$class_No_id_arr = explode(',', $class_No_id);
$this->where      = ['college_jg_id' => $college_jg_id];
$this->whereIn[]                = ['grade', 'in', $year_arr];
$this->whereIn[]                = ['class_No_id', 'in', $class_No_id_arr];
see the link to the picture
https://www.hualigs.cn/image/63bfabdc911d8.jpg
expected effect
https://www.hualigs.cn/image/63bfad4213b45.jpg

Should be a bug, I will try to fix this.


Updated "Get Started" in Documentation

Fixed Training spaces in markdown text [MD009]
Fixed Headings for no line gap after heading [MD022]
Corrected Spellings
Replaced Doc 360 links with .md files from Git Repo
Updated [!Warning] to [!Tip] in step-by-step-configuration-guide

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

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

File
Status
Preview URL
Details

microsoft-community-training/get-started/microsoft-community-training-overview.md
:white_check_mark:Succeeded
View

microsoft-community-training/get-started/step-by-step-configuration-guide.md
:white_check_mark:Succeeded
View

microsoft-community-training/get-started/user-role-and-management-portal-overview.md
:white_check_mark:Succeeded
View

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

PRMerger Results

Issue
Description

File Change Percent
This PR contains file(s) with more than 20% file change.


Redirect With Query Issue

Version
3.5.2
Reproduction link
https://codesandbox.io/s/interesting-wave-xpvn7?file=/src/router/index.js
Steps to reproduce
One way to reproduce, is by adding a query to your redirect path, ex:
{
    path: '/bot/:id/vote',
    redirect: {
      path: '/bot/:id/?vote=true'
    },
},

What is expected?
It should load the component.
What is actually happening?
It's leading to a 404 page, but when I refresh the page it works.

Here is a video, of showing what happens:
https://user-images.githubusercontent.com/34258275/125176695-7e4fa600-e1a3-11eb-87de-235a7f75ffa9.mov

The only fix I was able to do was by using the beforeEnter method, but this temporarily shows a blank white screen which is not really nice.

Your reproduction is lacking the mentioned code and you should build a proper path in the redirect:
{
    path: '/bot/:id/vote',
    redirect: to => `/bot/:id/?vote=true`
},

The query cannot be in path, it must go in query.
Please, next time consider using the forum, the Discord server or StackOverflow for questions first. But feel free to come back and open an issue if it turns out to be a bug 🙂

I gave a similar replication use a param and query, the issue seem to be with a component being lazy loaded and using the methos i used prior:
{
    path: '/bot/:id/vote',
    redirect: {
      path: '/bot/:id/?vote=true'
    },
},

The working code is:
{
    path: '/bot/:id/vote',
    redirect: {
      path: '/bot/:id',
      query: {
        vote: true,
      },
    },
  },

Would like to thank for your contribution, help and maintaining of vue-router!


Remove version: Ryujinx.Ryujinx.Ava version 1.1.1174

part of #179207
All InstallerUrls returned 404 Not Found

https://github.com/Ryujinx/release-channel-master/releases/download/1.1.1174/test-ava-ryujinx-1.1.1174-win_x64.zip

Microsoft Reviewers: Open in CodeFlow

URL: https://github.com/Ryujinx/release-channel-master/releases/download/1.1.1174/test-ava-ryujinx-1.1.1174-win_x64.zip
Response status code does not indicate success: 404 (Not Found).
(Automated message - build 896)


Always configure a logger on the context

Always create and include a logger on the context, make logging package public
Release Note
Always include a logger object and make logging package public

/assign @mikehelmick


I don't understand what the problem is.

He appeared on Hass.io, but I don't know which configuration has a problem. May I ask my friends what's going on here?
2018-06-03 09:59:00 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/usr/lib/python3.6/site-packages/homeassistant/helpers/entity.py", line 287, in async_update_ha_state
self.entity_id, state, attr, self.force_update)
File "/usr/lib/python3.6/site-packages/homeassistant/core.py", line 743, in async_set
state = State(entity_id, new_state, attributes, last_changed)
File "/usr/lib/python3.6/site-packages/homeassistant/core.py", line 533, in init
"Format should be .<object_id>").format(entity_id))
homeassistant.exceptions.InvalidEntityFormatError: Invalid entity id encountered: zone.. Format should be .<object_id>

Invalid entity id encountered: zone.. Format should be .<object_id>

You have "zone.." somehwere in your yaml. I recommend you use Discord for troubleshooting configuration files.


CanonicalURLMiddleware default to all environments

Description
Having a Live/Prod only feature sets people up for bugs.  A common scenario for this one is a javascript feature that requests from an API - its easy to forget a trailing slash in this scenario and it will work on your local an your test environment - failing only once you deploy it to prod. I'd suggest we turn this on everywhere except the CLI by default (or, disable it by default).
Manual testing steps

Issues

Pull request checklist

[x] The target branch is correct

See picking the right version

[x] All commits are relevant to the purpose of the PR (e.g. no debug statements, unrelated refactoring, or arbitrary linting)

Small amounts of additional linting are usually okay, but if it makes it hard to concentrate on the relevant changes, ask for the unrelated changes to be reverted, and submitted as a separate PR.

[ ] The commit messages follow our commit message guidelines
[ ] The PR follows our contribution guidelines
[ ] Code changes follow our coding conventions
[ ] This change is covered with tests (or tests aren't necessary for this change)
[ ] Any relevant User Help/Developer documentation is updated; for impactful changes, information is added to the changelog for the intended release
[ ] CI is green

+1 for this, I ended up using axllent/silverstripe-trailing-slash anyway because of this to make sure it all behave consistently. I believe the way it's handled in the core should align with whatever that module is doing.
I'm not even sure why it was meaningful in the first place to take env into consideration for this

Bear in mind that this middleware is responsible for more than just the trailing slash redirection. I'm going to have to reject this PR, because this would break for anyone who sets forceWWW to true and expects it to not affect their development environments.
In a future major release we should probably get rid of enabledEnvs and just expect people to set environment-specific YAML config in the first place - but we can't change the default affected environments in a minor release without breaking functionality for some users.


[Bug]: Origin URL parse fails when using wildcard redirects

Preflight Checklist

[X] I could not find a solution in the documentation, the existing issues or discussions
[X] I have joined the ZITADEL chat

Environment
Self-hosted
Version
v2.43.1
Database
PostgreSQL
Database Version
15
Describe the problem caused by this bug
Since https://github.com/zitadel/zitadel/pull/7091 we allow glob patterns to be used in redirect URIs. The same redirect URIs are also used to construct the allowed origins. When a wildcard (*) is used inside the hostname or port, go's url.Parse throws an error.
time="2024-01-05T10:34:02Z" level=warning msg="unable to set allowed origins" caller="/home/tim/Repositories/zitadel/zitadel/internal/query/app.go:863" error="parse \"http://localhost:*/login_check\": invalid port \":*\" after host" logID=app oddFields=1

To reproduce

Create a project with app
Set a redirect URI like: http://localhost:*/foo
Complete a login flow and call userinfo
Observe logs for above warning log line.

Screenshots
No response
Expected behavior
The request to be completed without warn logs.
Operating System
Zitadel in Docker on Linux
Relevant Configuration
No response
Additional Context
It was discussed internally we might drop the hard Origin-check on the Application in OIDC related calls. As the check can already be disabled by omitting the origin header in the request. There is no added security here.

hei @muhlemmer  is this something we can plan for a next bug fixing Friday?
Or do wen need to plan it in a sprint?
Also how urgent is it?


Button styling is not applied in sent messages

Not every email clint supports CSS that is not inline

Local BrickHack issue.

Local BrickHack issue.


[Question] how does this differ from normal gem installation

I'm new to installing gems, so I may be missing something obvious.
How does installing a gem via brew gem differ from installing it via gem?

I see, thanks


Proposal: Graphs of different width

Hello,
first and foremost, I really like dfc. On my server I have multiple hard drives of different size:
FILESYSTEM      TYPE     (=) USED      FREE (-)  %USED   USED AVAILABLE  TOTAL MOUNTED ON
/dev/sdb1       fuseblk  [=================---]  81.0% 754.7G    176.9G 931.5G /media/00
/dev/mapper/vc1 ext4     [===================-]  90.2% 498.8G     57.1G 585.8G /media/01
/dev/mapper/vc2 ext4     [=================---]  82.0% 704.6G    164.6G 915.9G /media/02
/dev/mapper/vc3 ext4     [==============------]  69.0% 374.6G    181.4G 585.8G /media/03

Now, as you can see, the hard drives are of different sizes each so it's a bit hard at first glance to see which one has the most free space.
For this reason I was thinking of an alternative graph display where each graph resembles the absolute size of the fs and is filled up accordingly, something like this:
FILESYSTEM      TYPE     (=) USED      FREE (-)  %USED   USED AVAILABLE  TOTAL MOUNTED ON
/dev/sdb1       fuseblk  [==============----]    81.0% 754.7G    176.9G 931.5G /media/00
/dev/mapper/vc1 ext4     [=========-]            90.2% 498.8G     57.1G 585.8G /media/01
/dev/mapper/vc2 ext4     [=============---]      82.0% 704.6G    164.6G 915.9G /media/02
/dev/mapper/vc3 ext4     [=======---]            69.0% 374.6G    181.4G 585.8G /media/03

This is a very crude mock up of what I have in mind. (I know that my specific scenario is rather a thing for LVM but I'm to lazy.)
Let me know what you think about this and if you're interested in a feature like this, I'd work on a PR.

Hi!
I like your proposal and it makes sense to me. I'm not sure how dealing with partitions/disks of very different sizes will work in practice though (I'm trying to picture, say, a 20G partition and a 4TB one for instance) but it's also not like this needs extreme accuracy. I'd totally accept a PR that adds this functionality but I think it should be hidden behind a flag and not a default.


[Bug] Page jumps on editor re-focus when using smooth scrolling

Reproducible in vscode.dev or in VS Code Desktop?

[X] Not reproducible in vscode.dev or VS Code Desktop

Reproducible in the monaco editor playground?

[X] Not reproducible in the monaco editor playground

Monaco Editor Playground Code
No response
Actual Behavior
Consider the following scenario:

We enable scroll-behavior: smooth on the page.
Click any line in the editor (preferably at the top).
Click outside the editor, so that it loses focus.
Scroll the page, such that the previously focused line is outside the viewport.
Click another line in the editor.

https://user-images.githubusercontent.com/17034772/147591752-1c886e6c-fb83-46b0-bf1d-efd7f48860a5.mp4
There is a noticeable jump. My guess would be that under the hood, clicking the editor focuses and scrolls to the old cursor position and only then the position is updated and it scrolls back there. This jump is only perceivable with smooth scrolling enabled, otherwise these are just two immediate changes.
Expected Behavior
Here's the same scenario without smooth scrolling, there is no jump and that's the expected behaviour.
https://user-images.githubusercontent.com/17034772/147594953-24aa5074-a115-49b0-866e-6bbf45203b00.mp4
Additional Context
The described behavior happens in Firefox (95.0.2). In Chrome (96.0.4664.93) it's a bit different, it smoothly scrolls to the old cursor position and doesn't scroll to the new one.

Unfortunately, we don't have the resources to address this right now, but we're more than happy to accept a PR for this!

Closing due to inactivity.
If this bug still applies, please create a new issue. Make sure to select the form for bugs and include a minimal reproducible example that runs in the playground. Thanks!

I can still reproduce it in Firefox with the same steps as outlined above, but I understand if there's no capacity to solve this edge case :)

Happens on the main website. Here's a new video:
https://user-images.githubusercontent.com/17034772/224670562-d1df97f9-43e4-4131-9108-416283f2923f.mov
Note that in order to reproduce it the page itself needs to be scrollable with editor somewhere, while the playground has editor full-height.


Possible limitation

Hello all, I am currenlty evaluating astroturf and linaria to see which one fits our needs the best. So far astroturf is in the lead, but I think i found a possible limitation that would make it unusable for us. Or maybe I'm just missing some configuration flag or workaround.
I'm trying to assign different classes to an object, but I am greeted with the following error message:
There are multiple css tags with the same inferred identifier. Differentiate each tag by assigning the output to a unique identifier

and here is a sample code:
const styles = {
  App: css`text-align: center;`,
  header: css`background-color: #282c34;
    min-height: 100vh;
    display: flex;
    flex-direction: column;
    align-items: center;
    justify-content: center;
    font-size: calc(10px + 2vmin);
    color: white;`,
  link: css`color: #b318f0;`,
  logo: css`
    animation: logo-spin infinite 20s linear;
    height: 40vmin;
    pointer-events: none;

    @keyframes logo-spin {
      from {
        transform: rotate(0deg);
      }
      to {
        transform: rotate(360deg);
      }
    }
  `
}

Wouldn't it make sense to include the object key in the identifier in this case? Or what am I missing here?
Cheers.

does this not work already? I can totally make it work if it doesn't yeah

also you don't need to declare each class separately like this, stylesheet produces the same object with properties

yeah this isn't supported in astroturf, because the value of the interpolation isn't statically determinable. Linaria handles this by actually running your code to get the value of the fn, which has it's own downsides (its much slower and can create an uncanny valley around where code runs).
Astroturf supports dynamic values in the context of a component, where it can't replace the value with a CSS property, e.g.
function ({ color }) {
  return <div css={css`
       color: ${color}
    `} />
}

Thanks for the quick reply. Yes, I saw that, it is and interesting approach, but for our use case doesn't work. We're not even using react and this is required to run a function kinda like vanilla extract's sprinkle. In any case, I understand the design decision, and thank you for your time. Cheers.

also you don't need to declare each class separately like this, stylesheet produces the same object with properties

Hello. I am still trying to use astroturf instead of Linaria. :) Using this approach works alright, but, i don't seem to get any type inference.
const styles = stylesheet`
.root {
  color: red;
}
`

console.log(styles.root) // no ts validation
console.log(styles.something) // no ts error

Don't really know how to handle this, if you could shed some light on the matter that would be great.

this is just a hard limitation of ts, you'd need a type plugin for this to work and TS doesn't allow that (if something else is doing this let me know i will see how they manage it).
The simplest way to avoid is like you tried originally with css to declare individual classes on an object, There are some differences between that and the stylesheet approach but should be the same feature-wise.

this is just a hard limitation of ts, you'd need a type plugin for this to work and TS doesn't allow that (if something else is doing this let me know i will see how they manage it).
The simplest way to avoid is like you tried originally with css to declare individual classes on an object, There are some differences between that and the stylesheet approach but should be the same feature-wise.

I've been using this with plain css modules: https://github.com/mrmckeb/typescript-plugin-css-modules and it works great. Even parses sass and postcss plugins. But have no idea if you can adapt to to the inner workings of astroturf.

you definitely could get that to work, astroturf is just css-modules, so all you'd need to do is tell it which template tags are actually css-modules. (the author might even add support if we ask) but that's not the same as TS errors, e.g. tsc  -p .  wouldn't give you type errors, but I agree the intellisense is nice...there is already an astroturf vscode extension we could add this too as well...

Well, I suggested it in here: https://github.com/mrmckeb/typescript-plugin-css-modules/issues/220 So... 🤞


Dependency graph is unresolvable; found these conflicting requirements

Hi
While installing in the package getting the below error:-
**error: dependency graph is unresolvable; found these conflicting requirements:
Dependencies:
https://github.com/JohnSundell/Files @ 4.1.1..<5.0.0**
Any help will really be appreciated.
In Package file:-
.package(
url: "https://github.com/JohnSundell/Files",
.upToNextMajor(from: "4.1.1")
),
Thanks,
Aanchal

Hi @aanchalkalani
Thanks for info, can you please be more specific?
I have run make install:
matelo@DESKTOP-H8837T0 contentful-utilities.swift % make install swift package update Fetching https://github.com/contentful/contentful-persistence.swift Fetching https://github.com/kylef/Commander Fetching https://github.com/johnsundell/files.git Fetching https://github.com/mxcl/PromiseKit.git Fetching https://github.com/contentful/contentful.swift Fetching https://github.com/kylef/Spectre.git Completed resolution in 17.29s Cloning https://github.com/mxcl/PromiseKit.git Resolving https://github.com/mxcl/PromiseKit.git at 6.13.1 Cloning https://github.com/contentful/contentful-persistence.swift Resolving https://github.com/contentful/contentful-persistence.swift at 0.15.0 Cloning https://github.com/contentful/contentful.swift Resolving https://github.com/contentful/contentful.swift at 5.0.8 Cloning https://github.com/kylef/Commander Resolving https://github.com/kylef/Commander at 0.9.1 Cloning https://github.com/kylef/Spectre.git Resolving https://github.com/kylef/Spectre.git at 0.9.0 Cloning https://github.com/johnsundell/files.git Resolving https://github.com/johnsundell/files.git at 4.1.1 matelo@DESKTOP-H8837T0 contentful-utilities.swift %

closing due inactivity