Avoid installation via curl & pipe

Could we maybe try to push releases to package management, particularly since you've made your canonical install script unusually difficult to vet?
 I count at least 4 separate sources of potentially malicious executable code, none of which is ever checked against known signatures, with the preflight check being the most difficult to vet. At least with Vagrant I can get it from a trusted source that signs their packages.

Just to make sure we are on the same page before discussing further, I think there are 3 separate downloads that could be verified:

The install script itself
The dusty binary that the install script downloads (the first curl command)
The plist file that the install script downloads (the second curl command)

The preflight check is run via the daemon you just downloaded and, assuming the daemon itself was not compromised, does not download any additional code (it just checks whether you have necessary dependencies installed). I don't see why the preflight would add any additional attack surface.
I think my preferred way to address this would be to do the following:

Add a checksum for the install.sh script itself to the Installation docs
Have the install script verify checksums of the binary and plist

This would require a tiny amount of extra automation in our Jenkins job but it doesn't sound particularly onerous.
I'm not a huge fan of Homebrew but that could potentially be an option? Though I prefer having full control over our releases and not having to rely on external registries. It should also be noted that Dusty has functionality to upgrade its own binary, I'm not sure how that might be reconciled with a package manager that expects to be able to track versions. Do you have any insight there that might be helpful?

I guess the real issue is that you seem to not consider GitHub a trusted source? Everything we have now is downloaded from GitHub, and if our GitHub repo was compromised then none of the stuff I just talked about would matter anyway.

OK, let's say I audit your code, right? I want to make sure that the code I'm installing is the same code I've already audited. There's currently no way for me to use the install script you've provided in that kind of an environment because the install script itself loads new code without verifying it. If you absolutely must go the route of install via curl, then publish a SHA-256 hash of the script and modify your install command to short circuit on hash mismatch. Then embed SHA-256 hashes of all the included executables, checking each one before running. This is, however, hopelessly redundant because literally every good package manager essentially already does this by bundling everything together and hashing the combined package. Installing this way just unnecessarily duplicates work while making your update mechanism more complicated.
Trust is not about "I trust GitHub" or "I trust X, Y, or Z". It's more like "I know an audit of this code was done by someone who knows their shit, that audit was done on the package with hash X and the software I just downloaded has hash X therefore I trust that I have the same code that was audited by aforementioned trusted party." The install mechanism you've opted for makes the latter essentially impossible and thus Dusty is really hard to use in any environment where security matters.

Unfortunately mac doesn't have great package managers... we did look into using homebrew at one point, but decided against it for reasons that I don't remember off the top of my head

Homebrew is far more reasonable than what's being done right now...

I think we could look into using Homebrew again, specifically the cask method where we provide binaries rather than installing from source (which might have been our gripe the first time around).

I would have recommended cask in any case. IIRC vagrant comes in a cask too.

@sporkmonger If you have any other insight or experience w.r.t Homebrew or any other options I'm sure it would be helpful. I understand where you're coming from with your request and I don't mean to come across as dismissive or unreceptive. Trusted install wasn't a priority for us when we first rolled out Dusty but I think everything you're saying makes sense.

TBH, happy to put a cask together for you to get the ball rolling, but I probably don't have the time to maintain it, so it'd be something I'd be handing off to you guys when I'm done.

So I've gone and thrown one together. It works with the releases you have as-is. However, it's noteworthy that the installer script stanzas are way, way more verbose and involved than necessary because you're publishing a naked binary instead of a binary tarball. If you published a binary tarball, you wouldn't need the chmod +x step in either the canonical install.sh script or the cask installer stanzas, since tarballs will preserve the execute bit, plus you get both the binary and the launchd plist file in a single container, which means you can verify both at the same time with the same sha256 hash, which eliminates 90% of the cruft in this cask.
dusty.rb

@sporkmonger This is a great help, thanks. I'll try to push this over the line at least to the point where we have a single release in brew, hopefully this weekend.

Awesome, really appreciate it.

Here's what it'd look like if you published a binary tarball containing both the binary and the plist:
dusty.rb

Much nicer, we'll for sure do that.

@sporkmonger Our cask recipe was just merged with the version we released today, 0.6.5. Could you please verify whether that's working for you and meets the needs of this issue?
We still have some cleanup work to do around documentation and our release process to maintain the cask going forward, so I think I'll leave this open until that's all taken care of.

Hi, I'm one of the maintainers of Homebrew Cask.
brew cask install dusty is now available. (https://github.com/caskroom/homebrew-cask/pull/16966)
FYI, As the Cask just calls a script from the downloaded .tar.gz to finish setup, everything should now be fully auditable (no more curl-ing out.

Thanks @adityadalal924!

Made minor doc changes to Installation and Contributing sections. They won't show up in stable on RTD until we do another release, but they'll make it out there before too long.

Going to close this for now, please reopen if you have any other concerns


Refresh icon missing on macOS 10.9

The screenshot shows 10.9 at the top compared to 10.12 at the bottom.

@Aoiike: any ideas? I think this pertains to the problem we discussed with having separate PDF variants for different UI scales.

Does it still do this with the Icon in my EX Branch? and is that the only one affected?

OK I checked the logs in 10.9
15/07/2017 5:17:31.632 pm	Vienna[242]	CUICatalog: Can't find rendition for name: NewFeedTemplate scale factor: 1 device idiom: 0 device subtype: 0
15/07/2017 5:17:31.632 pm	Vienna[242]	CUICatalog: Can't find rendition for name: NewFeedTemplate scale factor: 1 device idiom: 0 device subtype: 0
15/07/2017 5:17:31.632 pm	Vienna[242]	CUICatalog: Can't find rendition for name: NewFeedTemplate scale factor: 1 device idiom: 0 device subtype: 0
15/07/2017 5:17:31.633 pm	Vienna[242]	Could not find image named 'NewFeedTemplate'.
15/07/2017 5:17:31.633 pm	Vienna[242]	CUICatalog: Can't find rendition for name: SyncTemplate scale factor: 1 device idiom: 0 device subtype: 0
15/07/2017 5:17:31.634 pm	Vienna[242]	CUICatalog: Can't find rendition for name: SyncTemplate scale factor: 1 device idiom: 0 device subtype: 0
15/07/2017 5:17:31.634 pm	Vienna[242]	CUICatalog: Can't find rendition for name: SyncTemplate scale factor: 1 device idiom: 0 device subtype: 0
15/07/2017 5:17:31.634 pm	Vienna[242]	Could not find image named 'SyncTemplate'.

I think NewFeedTemplate has been fixed though, because I was testing a newer build for PR #945 and it only complained about SyncTemplate:
18/07/2017 12:00:18.274 am	Vienna[242]	CUICatalog: Can't find rendition for name: SyncTemplate scale factor: 1 device idiom: 0 device subtype: 0
18/07/2017 12:00:18.274 am	Vienna[242]	CUICatalog: Can't find rendition for name: SyncTemplate scale factor: 1 device idiom: 0 device subtype: 0
18/07/2017 12:00:18.275 am	Vienna[242]	CUICatalog: Can't find rendition for name: SyncTemplate scale factor: 1 device idiom: 0 device subtype: 0
18/07/2017 12:00:18.275 am	Vienna[242]	Could not find image named 'SyncTemplate'.

I will note that the "problem" icons have 1x and 2x versions in the asset catalogue, the other icons are single scale.

Would it be difficult to drop the 2x versions only on Mavericks?

It sadly means that we have to create this toolbar item in code and set the image based on system versions at runtime. It would be good to know first if this pertains to Yosemite as well.

I actually cannot reproduce this on Mavericks. Seems to be working fine on my machine.


Remove waffle.io throughput activity chart from readme

Waffle.io is going away :(

Don't forget the waffle badge at the top for the issues 😢


@aws-cdk/aws-certificatemanager 0.26.0 is corrupt

I've been trying to install the @aws-cdk/aws-certificatemanager 0.26.0 package and I get the same error across different computers(win10, high sierra) and package managers (yarn, npm).
Coworkers are experiencing the same.
NPM error:
"npm WARN tarball tarball data for<EMAIL_ADDRESS>(sha512-MeCTe9fPcQe1CnJGJA0E9mkOZMOEQ98CXsL/JozWglR5yz6XneiOlPa1xLAFCpxbBxXVpGE5BwECoiGGNP6E1Q==) seems to be corrupted."
Yarn error:
"error<EMAIL_ADDRESS>Extracting tar content of undefined failed, the file appears to be corrupt:"
Running yarn add any-other-package works in all cases, it's only this package that results in the error.

Thanks for the heads up!

I've managed to install it once with npm now, but not a second time. I'm wondering if this is a network issue or npm registry issue rather than anything to do with this repo actually :)

Well that would make me feel a lot better if true.

WOMM:
$ npm install<EMAIL_ADDRESS>npm WARN<EMAIL_ADDRESS>No description
npm WARN<EMAIL_ADDRESS>No repository field.

+<EMAIL_ADDRESS>added 21 packages from 1 contributor and audited 744 packages in 10.039s
found 0 vulnerabilities

This is from Europe.

I'm gonna chalk this up to some sort of network issue, even though it's only this package that experiences this issue. It might be the cloudflare cache nodes in front of the registries we're hitting here are having some sort of issue, since if I try to download the package using wget or curl it works, but npm/yarn fails with different flavors of timeouts and file corruption errors.


[FEATURE] update flutter connectivity plugin

Is your feature request related to a problem? Please describe.
The version of flutter's connectivity plug we use to detect if a user is online also provides access to specific wifi connection information, such as SSID and BSSID. We are being required to disclose how we use SSID and BSSID, even though we are not using it in the app. This is making store submission very difficult.
Newer versions of connectivity (>2.0) remove wifi connection information.  Wifi details are now in their own plugin, wifi_info_flutter.
Can we update the plugin so we no longer have access to specific wifi information we do not need?
https://pub.dev/packages/connectivity/changelog
Describe the solution you'd like
Update the connectivity plugin to a newer version that does not have access to specific wifi connection information like SSID and BSSID.

Fixed in version 2.9.12


Include some degit flags

ghat uses degit under the hood. It could include some flags, like mode=git, which enables getting workflows from private repos.

The plan is to avoid using debit since it's not meant to be used this way and is heavy.
Ideally it will be replaced by hosted-git-info for parsing + untar specific folders and files. For any specific degit features, it's best to open specific issues.


move choose_rand into a blanket impl of Set

cargo test errored because it hasn't been updated, make sure to fix that first.

done, although i won't be updating your docs, you will have to do that yourself.

Also build failed btw

Are you not using an ide? Check if it compiles before pushing code.


follow redirects

I am sorry that I did not test my changes sufficiently.
This should make it work :P.

@vale981 Are all of your changes good to go now?  If so I'll merge this PR.

@vale981 Are all of your changes good to go now?  If so I'll merge this PR.

networking.interfaces.enp0s5.preferTempAddress = false; does not work unfortunately

networking.interfaces.enp0s5.preferTempAddress = false; does not work unfortunately


Prisma.Decimal values do not handle the infix '+' operator correctly

Bug description
Prisma.Decimal values do not handle the infix '+' operator correctly
new Prisma.Decimal(100) + 1 === '1001'
How to reproduce

Have a schema with a Decimal type

model Order {
  id             Int            @id @default(autoincrement())
  amount    Decimal

  @@map("orders")
}

Application code to reproduce bug:

await prisma.order.create({data: {amount: 100}});

const order = await prisma.order.findFirst({});
console.log(order.amount); // 100

const x = order.amount + 1; // x is the string '1001' rather than the number 101

Expected behavior
Prisma.Decimal types should handle the infix '+' operator like regular javascript numbers (i.e. perform number addition rather than string concatenation)
Prisma information

// Add your schema.prisma

model Order {
  id             Int            @id @default(autoincrement())
  amount    Decimal

  @@map("orders")
}

// Add your code using Prisma Client

await prisma.order.create({data: {amount: 100}});

const order = await prisma.order.findFirst({});
console.log(order.amount); // 100

const x = order.amount + 1; // x is the string '1001' rather than the number 101

Environment & setup

OS: Ubuntu 20.04
Database: PostgreSQL 13.8
Node.js version: 16.16

Prisma Version
prisma                  : 4.4.0
@prisma/client          : 4.4.0
Current platform        : debian-openssl-1.1.x
Query Engine (Node-API) : libquery-engine f352a33b70356f46311da8b00d83386dd9f145d6 (at<EMAIL_ADDRESS>Migration Engine        : migration-engine-cli f352a33b70356f46311da8b00d83386dd9f145d6 (at<EMAIL_ADDRESS>Introspection Engine    : introspection-core f352a33b70356f46311da8b00d83386dd9f145d6 (at<EMAIL_ADDRESS>Format Binary           : prisma-fmt f352a33b70356f46311da8b00d83386dd9f145d6 (at<EMAIL_ADDRESS>Format Wasm             : @prisma/prisma-fmt-wasm 4.4.0-66.f352a33b70356f46311da8b00d83386dd9f145d6
Default Engines Hash    : f352a33b70356f46311da8b00d83386dd9f145d6
Studio                  : 0.474.0

@ackinc
I think you would need to do this
new Prisma.Decimal(100).plus(1)

Prisma.Decimal is from Decimal.js, see docs https://mikemcl.github.io/decimal.js/#add
Let me know if that works.

Hi @ackinc and thank you for your feature request! Unfortunately JavaScript doesn't allow operator overloading, and it is not possible to implement the behavior of + operation for a custom type. There is a Stage 1 proposal (https://github.com/tc39/proposal-operator-overloading), but it doesn't seem to be moving much lately.


College Placement Prediction Model

Related Issues or bug
Predicting college placements accurately is challenging due to:

Variety of Influencing Factors: Academic scores, previous experience, and other personal characteristics affect placement outcomes.
Data Quality: Differences in available data for each student can affect model accuracy.
Feature Engineering: Identifying key predictive factors is crucial for improving the model’s performance.

Fixes: #854
Proposed Changes
The model is built using several machine learning algorithms, including:

Logistic Regression
Decision Trees
Random Forest
Support Vector Machine (SVM)

@Varunshiyam once check your score from my repo if it exceeds 200 I can't accept more features from you.


add a warning for yammllint

Add a warning to show the message for the custom rule invalid config

I have an alternate PR in #61.

sure

Superseded by #61.


Prevent override of Org Level Service Policy action when imported into resource

upstream: https://github.com/Juniper/terraform-provider-mist/issues/36

fixed in latest release


Fix build on Windows with recently added lzma dependency.

The python script was using 'file' and 'tar' commands. These are not
available on Windows.
Remove the hooks to fetch the SDK, there is no need to download it,
it's small enough to import the files directly in our repository.

We also need a README.xwalk similar to the README.chromium files that Chromium adds to its third-party libraries, with information such as where the code came from, the license, what it does etc. See the README.chromiums in src/third_party, for example.

If we go that road, in order for the infra, as well as dev checkouts to not fail we would need to land https://github.com/crosswalk-project/crosswalk/pull/3015 first.

ping @halton @d0ngjun

LGTM

given the bot errors are unrelated, let's merge


Updates for 4.0.x

Fixes error when using the translator for REFEDS MFA.
Updates dependencies to latest library versions.
Modifies code only to support newer Java and Opensaml changes. No new features.
Supports Java 11.

Looks good. @pspaude Good to merge and cut 4.0 jar


Add Single Entry pages for tools

tracking issue

While this page isn't "done" it's done in the general sense that this issue is for, and other things will be followed up on in subsequent issues. Closing.


[Bug] Updating config should trigger restarting the pod

At present, modifying starrocksBeSpec.config and starrocksFESpec.config merely updates the configmap without restarting the pod, thereby config changes fails to take effect.
The correct approach shall updating the configmap and restarting the pod to effectuate the updated configuration.

@kevincai @shileifu can you please add this issue?
Thank you!

@dengliu the ability will be provided in the next operator version, the CRD version v1.

the ability has been supported in v1.6. we closed the issue, any questions about the ability can reopen it.


Find in dependency Jars throwing an error

Describe the bug
Trigger a :MetalsFindInDependencyJars and search for something. When it returns you'll see:
Error executing vim.schedule lua callback: ...vim/HEAD-030417d/share/nvim/runtime/lua/vim/lsp/util.lua:141: Invalid encoding: 20
stack traceback:
        [C]: in function 'error'
        ...vim/HEAD-030417d/share/nvim/runtime/lua/vim/lsp/util.lua:141: in function '_str_byteindex_enc'
        ...vim/HEAD-030417d/share/nvim/runtime/lua/vim/lsp/util.lua:1659: in function 'locations_to_items'
        ...te/pack/packer/start/nvim-metals/lua/metals/handlers.lua:125: in function 'handler'

Expected behavior
I'd expect this to correctly display the results.
Operating system
macOS
Version of Metals
0.11.5+59-6c52212e-SNAPSHOT
Commit of nvim-metals
most recent

One other thing I just noticed with this is that you can get metals attached with will give you the metals commands. Then you navigate to a .conf file where metals isn't attatched, but you still have the command but it does nothing, which is confusing.


Changing Label background color

hey, thanks for the amazing library! My question is that can I change the background color of the FAB label?
Thank you so much.

@theaidorus That'd be awesome for this library.
If you really need to change label background, try this:
https://github.com/wangjiegulu/RapidFloatingActionButton
It has some deep issues on changing label text and icon but rest is good.

Yes. FloatingActionMenu has these xml attributes for that:
fab:menu_labels_colorNormal="#333333"
fab:menu_labels_colorPressed="#444444"
fab:menu_labels_colorRipple="#66FFFFFF"

or you can use a style:
fab:menu_labels_style="@style/YourCustomLabelsStyle"

How can i stop the animation in floating point point button in android


OO/rhood/3780 Std CSV - Fix Fake Data Error

This PR contains modifications outlined ticket #3780  to fix errors during fake data generation, clear invalid Illness Onset Date, set the trackingElement on all schemas, and re-implement IfNotPresent on ordering_facility_street2.
If you are suggesting a fix for a currently exploitable issue, please disclose the issue to the prime-reportstream team directly outside of GitHub instead of filing a PR, so we may immediately patch the affected systems before a disclosure. See SECURITY.md/Reporting a Vulnerability for more information.
Test Steps:

To test fake data errors, run the CLI ""./prime data --input-fake 100 --input-schema manualupload/csvuploadertest-covid-19 --output junk/StdCSV-fake.csv"
Run  ./prime generate-docs | grep Tracking and make sure the schemas "manualupload/csvuploadertest-covid-19" and "upload-covid-19" are not listed.
Using the attached test file for Std CSV, run the CLI "./prime data --input result_files/StandardCSV-Test.csv --input-schema manualupload/csvuploadertest-covid-19 --output-dir junk --route" and make sure the Illness Onset Date of "22/22/2021" is cleared and the OBX for illness onset date is not created for the 3rd row.  Also, make sure the error for ordering_facility_street2 for Mapper and canBeBlank doesn't appear.

StandardCSV-Test.csv
Changes

[x] Added "type: TEXT" to all temporary fields.  The field names ended with "_temp".
[x] Added "trackingElement: message_id" to the following schemas.
- upload-covid-19
- manualupload/csvuploadertest-covid-19
[x] Added nullifyValue: true to illness_onset_date in the schema upload-covid-19.
[x] Added the IfNotPresent Mapper back to ordering_facility_street2

Checklist
Testing

[x] Tested locally?
[x] Ran ./prime test or ./gradlew testSmoke against local Docker ReportStream container?
[ ] Downloaded a file from http://localhost:7071/api/download?
[ ] Added tests?

Process

[ ] Are there licensing issues with any new dependencies introduced?
[ ] Includes a summary of what a code reviewer should verify?
[ ] Updated the release notes?
[ ] Database changes are submitted as a separate PR?
[ ] DevOps team has been notified if PR requires ops support?

Fixes
List GitHub issues this PR fixes

#3780

Pull reviewers stats
Stats for the last 30 days:

User
Total reviews
Median time to review
Total comments

MauriceReeves-usds
37
18m
2

cwinters-usds
19
13m
2

sean-usds
18
13m
5

jimduff-usds
17
13h 14m
13

carlosfelix2
10
2h 58m
63

TomNUSDS
10
1h 6m
16

jorg3lopez
8
1h 22m
1

jbiskie
6
2h 8m
0

whytheplatypus
5
23h 29m
13

kevinhaube
5
10h 16m
5

brick-green-agile6
5
1h 26m
4

clediggins-usds
5
1h 14m
3

RickHawesUSDS
4
3h 17m
0

ahay-agile6
3
10h 22m
6

sethdarragile6
3
4h 52m
0

oslynn
2
18h 57m
38

jeremy-page
1
3m
0

Pull reviewers stats
Stats for the last 30 days:

User
Total reviews
Median time to review
Total comments

MauriceReeves-usds
41
14m
2

cwinters-usds
22
1h 43m
4

jimduff-usds
20
12h 29m
13

sean-usds
19
10m
4

carlosfelix2
10
4h 2m
43

TomNUSDS
10
1h 8m
14

jorg3lopez
9
1h 42m
1

whytheplatypus
6
1d 2h 23m
11

jbiskie
6
2h 8m
0

brick-green-agile6
6
1h 24m
4

kevinhaube
5
10h 16m
5

clediggins-usds
5
1h 14m
3

RickHawesUSDS
4
3h 17m
0

ahay-agile6
3
10h 22m
6

oslynn
3
18h 57m
21

sethdarragile6
3
4h 52m
0

jeremy-page
1
3m
0

@brick-green-agile6 The ORC.22.2 should be blank.  This appears to be a bug in the IfNotPresent Mapper.  I've rolled back this one change and committed the change.


Make text in sunburst path more readable

Make the text color be black or white based on lightness of background color.

@williaster @xrmx
superseeds https://github.com/airbnb/caravel/pull/674/files

Coverage decreased (-0.2%) to 81.248% when pulling 6095c579bffc8c9a0982d688b47f1b9fbb17b367 on mistercrunch:sunburst_readable into 131372740e79fa0d6ebd7484026cb9ac5918f631 on airbnb:master.

Thanks!


-g fails on linux

Debug symbol info compiler switch causes following error:

clay -g main.clay
clay: /home/jeremy/Dev/clay/projects/clay_aur/llvm-clay-git/src/llvm/lib/Analysis/DIBuilder.cpp:80:  void llvm::DIBuilder::createCompileUnit(unsigned int, llvm::StringRef, llvm::StringRef, llvm::StringRef,   bool, llvm::StringRef, unsigned int): Assertion `Lang <= dwarf::DW_LANG_D && Lang >= dwarf::DW_LANG_C89 &&  "Invalid Language tag"' failed.
Aborted

Looks like it has something to do with my llvm install, i'll reinstall and try again.

Looks like LLVM assert builds are overly restrictive when it comes to language tags. It should also admit language tags in the user region.

Here's an LLVM patch that fixes the problem:
https://github.com/jckarter/llvm-3.0/commit/ddf85620afc7a04617e4184fe7a555471a54345f
I can make Clay pretend to be C++ or something so it works with vanilla LLVM 3.0 in the meantime.

Not sure if this is an issue:
This compiles and runs OK:
clay main.clay -lm -run > out.txt
However, including debug symbols gives:
clay -g main.clay -lm -run > out.txt
pseudo instructions should be removed before code emission
UNREACHABLE executed at
/tmp/yaourt-tmp-jeremy/aur-llvm-clay-git/src/llvm/lib/Target/X86/X86CodeEmitter.cpp:735!
Stack dump:
0.    Running pass 'X86 Machine Code Emitter' on function
'@"numbers.floats.floats.floatFromBits(UInt64) Float64 clay"'
Aborted
On 07/01/12 18:10, Joe Groff wrote:

Here's an LLVM patch that fixes the problem:
https://github.com/jckarter/llvm-3.0/commit/ddf85620afc7a04617e4184fe7a555471a54345f
I can make Clay pretend to be C++ or something so it works with vanilla LLVM 3.0 in the meantime.

Reply to this email directly or view it on GitHub:
https://github.com/jckarter/clay/issues/160#issuecomment-3397130

-run is pretty buggy since llvm::ExecutionEngine is a total hack. The frontend should maybe refuse to accept -g and -run together.

Another thing we could try is enabling JITEmitDebugInfo to see if that helps:
http://llvm.org/docs/doxygen/html/classllvm_1_1TargetOptions.html#a2d997cfe1f0dd48066f5df7686350e9e


On Android phones,  running the main.dart file in the pay/example  prompts an error

flutter-plugin-main/pay/example/android/app/src/main/java/io/flutter/plugins/GeneratedPluginRegistrant.java:24: 错误: 找不到符号
flutterEngine.getPlugins().add(new io.flutter.plugins.pay_android.PayPlugin());
^
符号:   类 PayPlugin
位置: 程序包 io.flutter.plugins.pay_android
1 个错误
FAILURE: Build failed with an exception.

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

Compilation failed; see the compiler error output for details.

Please help me successfully run the project.

Hi @LingLuoJack, can you add more details about the compilation error you see in the output?

thank you , I  have resolved this error.


fix(botocore.py): extract Kinesis put_records data

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


make test， It will have compilation errors.

make test， It will have compilation errors.
can not find libcheck files

1, download the source code form https://github.com/libcheck/check
2, README.md, then setup the libchek .


DataGrid: Add OnSorting event

I'm currently trying the DataGrid, and I've found that there is no OnSorting event.
This is not a major issue, but it would be useful if there was an event that would fire when a column is being sorted.

Done https://github.com/AvaloniaUI/Avalonia/pull/4687


Removing clean-out option for general file

Solves https://github.com/cagov/wordpress-to-github/issues/96

Q: will this prevent general file OR FOLDER PATH from being removed?

Yes.  Inspired by your folder destruction discovery.


Received status code 405 from server: Method Not Allowed

Hi, I started to receive failures when trying to publish to maven repo at bintray:
> Failed to publish publication 'my publication' to repository 'maven'
   > Could not PUT 'https://my-bintray-maven-repo/group-id/artifact-id/1.1.2-SNAPSHOT/maven-metadata.xml'. Received status code 405 from server: Method Not Allowed

The same gradle configuration has been working just fine (the last time about month ago). I've checked permissions and everything else I can think of but could not see any issues on my side.
I wonder is that possible that bintray has migrated to an artifactory version which is not fully compatible with gradle-bintray plugin v. 1.8.4 ? Did anybody else experience similar issues lately?
Thank you.

Andre, never mind, gradle bintray plugin works great! I've found the problem - it was my mistake.

I'm running into the same issue currently.  Any hints as to how you fixed it would be helpful.


Service "uptime"

This service would return now()-pg_postmaster_start_time().
I don't know if this would be useful to integrate something based on  pg_conf_load_time() ; too

Hi @Krysztophe,
What would be the thresholds for such services? When would you raise a warning or critical alert?
Is it only for graphing purpose?

The use would similar to the uptime Nagios probe, mainly for graphs.
Currently, looking at OPM graphs, I can't know for sure if there was a restart/conf reload somewhere.
Thresholds would be optional, perhaps raising a critical if uptime<15 min, just to have  a mail sent stored somewhere ; and a conf reload would raise a warning.
I'll try to make a first version in the next days, at least as an exercise for me.

At first glance, I couldn't find a good use of such service. As we're thinking to move to Grafana to replace the current OPM GUI, this probe will provide us an easy way to add annotations on graphs to show when the database was restarted and when the configuration was reloaded.
So, I'm OK to include this new service. @ioguix do you agree ?

PR merged, thanks ! The new service will appear in next release.


 The issue is by the mod or by my pixel shader version?

If you're experiencing this issue, your graphics card may not meet the requirements for this mod.


monaco: improve handling of glyph margins

In my previous PR #202048, I added another glyph margin lane. However
I didn't realize in some cases the support I added was incomplete since
the rendering code did not fully handle an unbounded number of lanes.
Also, I noticed in existing issues with hover and click handling because
some parts of VS Code still assume there's at most a single glyph widget
visible. It is hard to determine which glyph widget is interacted with
without checking what classes are applied to the glyph element, which
is what most existing code does. And we probably shouldn't do that in
e.g. the MouseHandler to determine what glyph is being clicked on.
So in this PR I added a GlyphMarginLanesModel that contains the
information necessary for rendering. I also want to expose it in a place
that the MouseHandler or MouseTarget can get at, but I wasn't sure the
best way to do that, any suggestions @alexdima?
Implementation-wise I opted for a flag Uint8Array. A 1024 line file with
decorations on the last line, it would take 384 bytes to hold decoration
positions. I also tried out a Range array based implementation, but I
think this is faster (for cases where there are lots of decorations)
and much simpler, in exchange for higher memory usage in pathological cases
(very long files with decorations near the end.)

Also, I did something similar to what was suggested in https://github.com/microsoft/vscode/pull/202048 where coverage decorations request persistLane: true which ensure the lane gets rendered (and not collapsed) if any decoration is present in the file, which avoid the jumping.


Fix typos in eventregistration & blog post

This PR fixes some typos discovered by @DerVogel2020 in https://github.com/corona-warn-app/cwa-website/pull/1132#pullrequestreview-643532898.
This PR also changes "Corona warning app" to "Corona-Warn-App" in the English blog post "2021-04-23-qr-code-generator-website".

Thanks!

LGTM

@Ein-Tim @MikeMcC399 Many thanks.


Make clear the product is ALPHA

Maybe add  - ALPHA after "Dartpad" ?

Or perhaps, add an alpha channel to the color?

@sethladd, it's here: https://github.com/dart-lang/dartpad_ui/blob/master/web/dartpad.html#L33
Feel free to tweak.


Reimplemented parts of matplotlibs history mechanism for TopViews

Works now also for stereographic projections and projection changes.
Fix issue #919

Changed behaviour. Projection change now resets history. Home button goes back to defined projection. Consistent and probably what people want.


Reset / clear selection

I'm having an issue where I get an error if the current datasource changes and the previously selected items don't match the new datasource. This behaviour mirrors the standard dropdownbutton behaviour which is fine, however, dropdown button offers access to the selected item so it can be set to null. It would be great if this feature could be implemented or some way to clear or reset the selected items.

is there any update for that

I'm facing the same issue.
My solution is wrapping this MultiSelect widget with a new Form and give a new _formkey such as _multiSelectFormkKey.
Once you get a new datasource then call _newFormkKey.currentState.reset(); to reset the multiSelectDropDownForm.
All previous selectedOptionsInfoText and selected items will be reset.
It works like a charm.
But remember now you have a form embedded in another so validate both formKeys as needed.
For example if you are calling formkey.currentState.save(); or formkey.currentState.validate() don't forget to do the same thing to _multiSelectFormkKey.

@bobppsureway : Can you send me a runnable example with your problem?

List dropDownData1 = [
{
"display": "Australia",
"value": 1,
},
{
"display": "Canada",
"value": 2,
},
];
List dropDownData2 = [
{
"display": "India",
"value": 3,
},
{
"display": "United States",
"value": 4,
},
];
List dropDownData= dropDownData1;
generateDropDownData(bool switch) {
if(swich==true)
{
setState(() {
controlPlanDropDownData = dropDownData1;
});
}
else
{
setState(() {
controlPlanDropDownData = dropDownData2;
});
}
}
Form(
key: _formKey,
child: MultiSelect(
autovalidate: false,
titleText: title,
validator: (value) {
if (value == null) {
return 'Please select one or more option(s)';
}
},
errorText: 'Please select one or more option(s)',
dataSource: dropDownData,
textField: 'display',
valueField: 'value',
filterable: true,
required: true,
value: null,
onSaved: (value) {
print('The value is $value');
}
)
)
If you select Australia and Canada then call generateDropDownData(false); then the dropdown populates with dropDownData2 info. This is right but the previously selected items are not reset. If you don't select any item with the new dropdown, call _formkey.save();  Returned value will be [Australia,Canada]. If select India and United States with the new dropdown the outcome will be  [Australia,Canada, India, United States].
Obviously the previous values are  stored in the cache.
We need a way to clear or reset the selected items.
Additionally, if the dropdown populates with initialValue [Australia, Canada] then set initialValue=null and call _formkey.currentState.reset(); It looks like the dropdown get reset but call _formkey.currentState.save(); outcome is [Australia, Canada].
Please help. Thank you.

If the dropdown populates with initialValue then setState on initialValue=null.
Use async call
await Future.delayed(
Duration(milliseconds: 100), () {
_formKey.reset();
});
Then the selected items are reset.


ping_exporter: init at 1.1.0

Description of changes
This adds @czerwonk's ping_exporter to Nixpkgs. ping_exporter is a "Prometheus exporter for ICMP echo requests".
A Grafana dashboard is also available via https://grafana.com/grafana/dashboards/18194.
The commit messages are not fitting CONTRIBUTING.md, because I did not know how to split them without giving them all the same message.
As this is my first contribution to nixpkgs, feedback is highly appreciated. :slightly_smiling_face:
Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[x] 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
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 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
[x] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Thanks @mweinelt and @pearzt for their great support!

The commit message for adding the module should probably be
nixos/(module): init module

(Motivation for change. Link to release notes. Additional information.)

and only the package should include the version. I think the tests should go in the same commit as the module as well, and since 23.11 is out now, release notes should probably go in the next release?

I think the tests should go in the same commit as the module as well

No, they shouldn't.

I think the tests should go in the same commit as the module as well

No, they shouldn't. Check existing commits on nixos/tests/.

Thanks, my bad on that one :)

also please rename your commits to look like:
maintainers: add Nudelsalat
prometheus-ping-exporter: init at 1.1.0
nixos/prometheus-ping-exporter: init
nixos/tests/prometheus-ping-exporter: init
and squash the release-notes commit into the nixos/prometheus-ping-exporter: init

Thank you all for you input and sorry for the long delay! I think I incorporated all of your suggestions. Hopefully this is ready for merge right now. 🙂
Last but not least: Have a wonderful christmas time! :christmas_tree: :santa:


Coq style guide

First pass at a Coq style guide! I just wrote down the invisible code-style rules I use for myself (that I could remember off the top of my head). Happy to agree on different standards if anything seems tedious or counter-intuitive.

It would be useful at some point to have a shell script that just does something like awk and checks for style violations
To proceed with the style guide I'd suggest we opportunistically make edits and then at some point in the future make a sweep for remaining violations

I agree with the way to proceed for now, and I think a shell script is a great idea. Right after we make the shell script is probably a great time to do a sweep, too.


PHP Fatal error when calling stream destructors

Guzzle version(s) affected: 7.4.2
PHP version: 8.1.4
cURL version: 7.74.0
Description
On our production server we see a lot of the following errors:
PHP Fatal error: Couldn't execute method GuzzleHttp\\Handler\\CurlMultiHandler::__destruct in Unknown on line 0
Couldn't execute method GuzzleHttp\\Psr7\\Stream::__destruct in Unknown on line 0
We still have no clue under which circumstances this happens. We do not see this error in our dev / staging environment, which is kind of odd and makes debugging really hard. We use AWS SDK in general, but the requests which produces the error do not access AWS in this context. Maybe somebody has a clue what's going on here and what we could try to analyze it. The request itself will pass our application controller, the final log which is written in the shutdown_function says everything was fine. The error seems to occur when PHP calls all the destructors, the load balancer then responds with 502 Bad Gateway error.
How to reproduce
Still hard to tell..

@klammbueddel were you able to replicate?

No, we had to rollback to PHP 7.4 in order to fix this.

in Unknown on line 0

This is weird. Do you by chance run with opcache enabled? If so, can you try disabling it on PHP8?

No, opcache was not yet enabled.

Any idea how this could be somehow reproduced ?

No, I hoped anybody could help or maybe saw this in other context. I found nothing related in the internet, so I opened this issue.

Hi, I face the same issue when I upgraded to PHP 8 and trying to fix it since few days. Just found this open issue.
PHP 8.0.20
Guzzle 7.5.0
Curl 7.74.0

I am facing the same issue as well since I upgraded to PHP 8.1. I have tried multiple solutions but nothing seemed to work.
Tried upgrading to PHP 8.2 but no luck.

in Unknown on line 0

This is weird. Do you by chance run with opcache enabled? If so, can you try disabling it on PHP8?

I had tried disabling this but still no change.

Same here! The issue for me came exactly at the same point when I upgraded to Php 8.1 and no solutions are working for me so far.
Looking for support.

Hi guys! I have upgraded to php-8 and start facing this issue. I think issue is with Guzzlehttp GuzzleHttp\Handler\CurlMultiHandler  we had to roll back to previous version of php.  anyone is able to fix this please reply.

We still have this issue, but I want to share some findings with you:
In our code, we registered the Aws stream wrapper with Aws\S3\StreamWrapper::register or Aws\S3\S3Client::registerStreamWrapper in every request. Once we removed this and only register the stream wrapper on demand, we significantly reduced the error count and finally could switch to PHP 8.2.
Still, we see the error even in requests, where no stream wrappers are registered. We are running our code in a Kubernetes cluster. We see significant more errors during deployments, when Pods are terminated and recreated and in the minutes / hours after a deployment the error count fades out.
Maybe anybody has a clue what is going on here. Could it be some corrupt memory, where  PHP is trying to destroy objects that never exists in this context but maybe did in another?


Add image-to-image translation tutorial (T1 to T2)

Please add a tutorial illustrating how to train a model (e.g. 3d pix2pix, ..) to translate a T1 into a corresponding T2 (or CT, PS,...) image.
Dataset: IXI, ...

Any updates on translating a T1 into a corresponding T2 (or CT, PS,...) image?

This isn't being worked on at the moment. The closest we have would be repurposing this DDPM tutorial designed for segmentation. Replace the segmentation target with a paired T2 (or other modality) and you have image-to-image translation

Thank you.

Due to this issue being replied to and inactivity, I am closing this issue. On a last note, the ControlNet tutorial can also be applied to image-to-image translation tasks.


Add --custom argument for passing additional installer arguments

[x] Have you signed the Contributor License Agreement?
[x] Are you working against an Issue?

#239
#1403

I chose the argument based on what made sense to me and what was in the referenced issues. If a different name is desired, I'm open to suggestions.
Decided to name the arg type CustomSwitches to avoid future confusion; again, if there's a better name, feel free to suggest.

// Installation failure was expected as the '/?' argument brings up the MSI help menu

PS D:\Git\winget-pkgs> wingetdev install --manifest D:\Git\winget-pkgs\manifests\7\7zip\7zip\22.01 --custom /? --verbose --open-logs
Found 7-Zip [7zip.7zip] Version 22.01
This application is licensed to you by its owner.
Microsoft is not responsible for, nor does it grant any licenses to, third-party packages.
Downloading https://www.7-zip.org/a/7z2201-x64.msi
  ██████████████████████████████  1.82 MB / 1.82 MB
Successfully verified installer hash
Starting package install...
Installer failed with exit code: 1639
One of the installation parameters is invalid. The package installation log may have additional details.

2023-01-09 22:29:04.465 [CLI ] Installer args: /passive /norestart /log "C:\Users\Trenly\AppData\Local\Packages\WinGetDevCLI_8wekyb3d8bbwe\LocalState\DiagOutputDir\WinGet-7zip.7zip.22.01-2023-01-09-22-29-04.465.log" /?
2023-01-09 22:29:04.466 [CLI ] Starting: 'C:\Users\Trenly\AppData\Local\Temp\WinGet\7zip.7zip.22.01\7z2201-x64.msi' with arguments '/passive /norestart /log "C:\Users\Trenly\AppData\Local\Packages\WinGetDevCLI_8wekyb3d8bbwe\LocalState\DiagOutputDir\WinGet-7zip.7zip.22.01-2023-01-09-22-29-04.465.log" /?'

Microsoft Reviewers: Open in CodeFlow

/azp run

Thanks for the pr. The change looks great. But as this will be a supported feature, for feature parity, we'd better add it to Com api around here with related implementation, also this should be added as contract version 6 since winget v1.4 just got finalized. And this is also a good one to update Powershell module around here with related tests.
Or alternatively, if you feel not comfortable adding above changes at the moment, we can add it behind an experimental feature, and we'll implement the Com api and PS module during winget v1.5 milestone and remove experimental feature later.

Thanks for the pr. The change looks great. But as this will be a supported feature, for feature parity, we'd better add it to Com api around here with related implementation, also this should be added as contract version 6 since winget v1.4 just got finalized. And this is also a good one to update Powershell module around here with related tests.
Or alternatively, if you feel not comfortable adding above changes at the moment, we can add it behind an experimental feature, and we'll implement the Com api and PS module during winget v1.5 milestone and remove experimental feature later.

Thanks for the feedback! I think I got it implemented, but I couldn't find where the tests were for the PowerShell module. Any guidance you can provide on where I should be adding additional tests would be appreciated

I also decided to add some whitespace handling just in case. I didn't think it made sense to error on whitespace, but if there's some other way you'd like it handled (or if you'd like the whitespace handling reverted) just let me know

Thanks for the pr. The change looks great. But as this will be a supported feature, for feature parity, we'd better add it to Com api around here with related implementation, also this should be added as contract version 6 since winget v1.4 just got finalized. And this is also a good one to update Powershell module around here with related tests.
Or alternatively, if you feel not comfortable adding above changes at the moment, we can add it behind an experimental feature, and we'll implement the Com api and PS module during winget v1.5 milestone and remove experimental feature later.

Thanks for the feedback! I think I got it implemented, but I couldn't find where the tests were for the PowerShell module. Any guidance you can provide on where I should be adding additional tests would be appreciated

Thank you. The Powershell tests are here. But after a closer look, they are just some basic smoke tests. So it's probably fine with the current unit tests only.

/azp run

/azp run

We're running out of letters :)
Naming things is hard.
--augment
--custom
--switches
What happens if we have both "--override" and this new argument?
I had a discussion with the Visual Studio team about this feature a few days ago. It's common for users to want to add switches to their Visual Studio install so they can include workloads. We might also have a situation where the default install from WinGet is "Silent with progress" and the user attempts to add another switch that conflicts with the ones WinGet already has for install mode or scope. I don't know if installers would take the first argument, the last argument, or throw an exception.

What happens if we have both "--override" and this new argument?

Override takes precedence and only the value for override is used

I had a discussion with the Visual Studio team about this feature a few days ago. It's common for users to want to add switches to their Visual Studio install so they can include workloads. We might also have a situation where the default install from WinGet is "Silent with progress" and the user attempts to add another switch that conflicts with the ones WinGet already has for install mode or scope. I don't know if installers would take the first argument, the last argument, or throw an exception.

Most installers would throw exception (from what I've seen). However, the idea of "adding your own switches" to the default switches winget uses is almost certainly a power user feature, or at least one that most users should understand to check their input before blaming the cli


why the scannet needs two phase training?

Thanks for your great work!
But something confused me. Why the scannet needs two-phase training, while the sunrgbd only have one-phase training?

Solved

solved


Help On Multiple Destination IPs

Please Help on how to show the attacks on multiple destination IPs. Please share the codes if anyone solved it already !

For multiples destinations I created the table Target, but the application is in Portuguese and at my google drive. If you want, you can download at https://segurancaopensource.blogspot.com.

Say I have multiple honeypots deployed in multiple locations, then my query is how to plot the attacks on that multiple destination honeypots from multiple source of attackers? Please help I am new to this area.

@diegodblr

As I said earlier, I created a version that has a table with the Attack Targets. I don't know if it's available in the Matthew version, but in my Portuguese version it is.

@diegodblr Can you link me to the code you did on the Attack Targets table? I'm at your site but I don't know Portuguese.

The link with te code: https://drive.google.com/open?id=15WSjNn_UQFoxBjheiZoqekv_AImySFqt


macOS Support

see #1 for more details

made appveyor build command, added an icon and a custom DMG background. pretty much done.


Bugfix for Elliptic Curve serialization

by mistake i serialized Elliptic Curve Private Keys as DER Encoding. Instead the private_numbers().private_value should be serialized.

We're currently processing your upload.  This comment will be updated when the results are available.

Thanks! Sorry for the late review.


Refactor global attack modifier to a getter

Refactoring the additional attack modifiers to a getter, which would allow monkey-patching it so a module could let you edit the modifiers without making any other changes to rollAttack().

There is a bug when you open the dialog multiple times, it will keep appending to the config object. Localization is also missing.
However, as wildj79 is planning to ship a build today I will merge it in this case and fix it for you, as we discussed in Discord.


UX improvements to host-based access

Handle cases where a Resource is created for the host the Gateway is running on, and there's no valid DNS record the Gateway can use to access the Resource (itself).
Edge case, lower priority for now,

[ ] Prevent localhost and <IP_ADDRESS> from being used for Resource address
[ ] Could use a name convention to specify host-based access

Closing in favor of #2801


Recent Octave: can not add variable "x" to a static workspace

On recent Octave dev version, all doctests fail, e.g., doctest doctest.
Some change in core Octave within the last few months.  I will try to bisect it later.

The first bad revision is:
changeset:   23864:4b0e0cae49db
user:        John W. Eaton<EMAIL_ADDRESS>date:        Wed Aug 09 13:11:54 2017 -0400
summary:     disallow dynamic variable creation in static scopes (bug #51698)

See https://savannah.gnu.org/bugs/?51698


Updates and changes required for compatibility with latest boo

Huge review. I don't see anything that's obviously questionable, and the staging projects are green.


Unable to connect to API

Hi, tried adding the integration and I am getting two errors:
2022-01-02 15:53:13 ERROR (MainThread) [homeassistant.components.litterrobot.hub] Unable to connect to Litter-Robot API
And
2022-01-02 15:53:13 ERROR (MainThread) [homeassistant.components.litterrobot.hub] Unable to connect to Litter-Robot API 2022-01-02 15:53:13 WARNING (MainThread) [homeassistant.config_entries] Config entry 'redacted' for litterrobot integration not ready yet: Unable to connect to the Litter-Robot API.; Retrying in background
Running:
home Assistant; core-2021.8.1
Python; 3.8.12
PS, reading through what you have done here creating the API and then the custom integration and eventually getting it incorporated with core is incredible.

Going on 36 hours of the integration retrying a connection to the API every ~1 minute and still not working. I've tried disabling and re-enabling the integration as well as restarting home assistant altogether multiple times to no avail either.
Am I doing something wrong?

It looks like your instance of Home Assistant is 4 months behind. There have been some changes, including one with the August release of Home Assistant that required a bump of the underlying auth library that had some breaking changes. HA release 2021.8.2 pulled the change for this in, so you'll need at least that version.
https://www.home-assistant.io/blog/posts/2#release-202182---august-5

OMG I never replied to this! Sorry!!!
I updated and everything is working fine! For what it's worth, I'm current at 2022.2.2 now and it's working like a dream, I made some conditional cards that change what's displayed in case it's off/ cleaning/ "idle" and then a button that I press and hold to reset the waste drawer (so that I don't just accidentally tap it and reset it)
One of my favorite integrations honestly haha


Remove SourceToCloud feature from 2023-05-02-preview

ARM (Control Plane) API Specification Update Pull Request
PR review workflow diagram
Please understand this diagram before proceeding. It explains how to get your PR approved & merged.

Purpose of this PR
What's the purpose of this PR? Check all that apply. This is mandatory!

[ ] New API version. (Such PR should have been generated with OpenAPI Hub, per this wiki doc.)
[ ] Update existing version for a new feature. (This is applicable only when you are revising a private preview API version.)
[ ] Update existing version to fix swagger quality issues in S360.
[x] Other, please clarify:

removing a feature from a new API version that has not been released yet

Due diligence checklist
To merge this PR, you must go through the following checklist and confirm you understood
and followed the instructions by checking all the boxes:

[x] I have reviewed the general guidance on the spec PR review process: https://aka.ms/specprreview.
[x] I confirm this PR is modifying Azure Resource Manager (ARM) related specifications, and not data-plane related specifications.
[x] I commit to follow the Breaking Change Policy.
[x] I have reviewed following Resource Provider guidelines, including
ARM resource provider contract and
REST guidelines (estimated time: 4 hours).
I understand this is required before I can request review from an ARM API Review board.

ARM API changes review

If you want for the ARM team to review this PR, you must add the ARMReview label.
The automation may automatically add the ARMReview label, if appropriate.
If this happens, proceed according to guidance given in GitHub comments also added by the automation.

Breaking change review
If you have any breaking changes as defined in the Breaking Change Policy,
follow the process outlined in the High-level Breaking Change Process doc.
Getting help

For guidance on fixing this PR CI check failures, see the hyperlinks provided in given failure
and https://aka.ms/ci-fix.
For additional help, see https://aka.ms/azsdk/support/spectools.

@rkmanda not sure why the pipelines are not running, could you please kick them off? thanks

/azp run

Was able to get the pipelines to run by closing and reopening. @rkmanda could you please help review and merge this PR？

For context, removed ARM review labels that I added manually, as we are removing a feature from an API version that has not been released. So this does not require an ARM reviewer

Hi @rkmanda, was hoping to get this merged in soon if possible. Please let me know if there is someone else I should reach out to in order to get it merged. Thanks.

@pauld-msft I would recommend adding WaitForARMFeedback to get on the PR review queue which is quite long.
Details on why here:
Roopesh Manda: Expect long delays for ARM swagger reviews
posted in Azure SDK / API Spec Review on Friday, July 7, 2023 11:52 AM

/azp run


Update font-babelstone-han to latest

After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} left no offenses.
[x] The commit message includes the cask’s name and version.

Merged as f029b5b2b00676a4a5562e175c45c8c383efc0f6.


Suggestions

I have 2 suggestions for this project:
Create a LocalApps directory that resembles NextStep
Add a poweroff/logout dialog like NeXT does.

GSDE follows OS X naming (e.g. /Applications, /System/Application, ~/Applications). I personally find NextStep's paths a bit confusing.

logout can be accomplished in following ways: Workspace menu, right-click the desktop menu, WorkspaceLougout from the command line

poweroff can be usually done from a login manager (wdm calls it halt). Or you can simply add poweroff menu item calling "poweroff" to your desktop menu or via StepTalk script to your Workspace.

BTW: although GSDE does look kind of similar to NextStep, it doesn't try to re-implement it. As GSDE evolves, I can imagine it will diverge even more.
NextSpace will give you the true NextStep-like experience.

Could you attempt to implement a more Mac-like look and feel? GNUStep has the ability to draw Mac-style menus and widgets.

While I'm on the subject of recommendations, what about adding https://github.com/gnustep/libs-xcode for the development environment?

I merged the libs-xcode PR, thanks!

In addition, would you consider adding the CoreFoundation Library?


Removed Inc/Exc patterns from preset, replaced with comment

Also fixed some UI issues.
Should resolve #656

Codecov Report

Merging #657 into master will increase coverage by <.01%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master     #657      +/-   ##
==========================================
+ Coverage   17.53%   17.53%   +<.01%
==========================================
  Files         221      221
  Lines      125531   125519      -12
  Branches    12124    12124
==========================================
- Hits        22011    22009       -2
+ Misses     102654   102643      -11
- Partials      866      867       +1

Flag
Coverage Δ

#2017
17.53% <0%> (ø)
:arrow_up:

#Debug
17.53% <0%> (ø)
:arrow_up:

#Release
?

Impacted Files
Coverage Δ

src/PerfView/Dialogs/ManagePresetsDialog.xaml
0% <ø> (ø)
:arrow_up:

src/PerfView/StackViewer/StackWindow.xaml.cs
25.8% <ø> (-0.04%)
:arrow_down:

src/PerfView/Dialogs/ManagePresetsDialog.xaml.cs
0% <0%> (ø)
:arrow_up:

src/PerfView/StackViewer/Preset.cs
7.04% <0%> (+0.46%)
: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 6ce6c5e...d277252. Read the comment docs.


A black rectangle lingers after removing a video on the campaign template

https://staging.dosomething.org/us/campaigns/teens-jeans

@angaither we need a solution for this for Monday's Teens for Jeans soft launch.

strange, it seems to still be pulling a video from an old revision.
@sergii-tkachenko @blisteringherb any idea why this would happen?
cleared cache a million times, replaced the video, removed the video, nothing.
my local correctly removes the reference to the video

@angaither Note: video is not yet translatable.

@sergii-tkachenko not trying to translate the field, it had a value in a previous revision and now it's removed, but the dpm shows it's still pulling something

Yes, just decided to mention that it should not be affected by all the translation stuff.

Could it be redis cache?

@sheyd and I just tried clearing redis cache, and it still appears. maybe it needs 100 clears?

@angaither The field is empty on the backend.

So it shoes empty html

right, but if you look at the dpm, that html is there because field_video is not empty


Update constants import to use module-level access #1172

This PR addresses issue #1172 by updating the way constants are imported and used throughout the Hugging Face Hub codebase. Instead of directly importing specific constants, we now import the entire constants module and access constants as its attributes.

@WizKnight code quality seems to be complaining. To fix this, you must run make style locally which will fix the issues. Then you can run make quality to check everything's good. Finally, commit and push the changes.

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.

Hi @WizKnight, I've checked out locally your changes to test typing issues you were having. I can't reproduce them and the CI either. I suspect that we are not on the same version (currently using mypy==1.5.1 in CI). For now I reverted the typing-related changes from this PR (see https://github.com/huggingface/huggingface_hub/pull/2453/commits/62af016c88a46356d2b351c137eb96bb3b2ee76c). I'll have a look to what you mention though but keeping it for a separate one.


Move dependency on general audio DSP tools from NeuralAmpModelerCore to AudioDSPTools

Resolves #373
Paves the way for NAM's core to specialize on its RT implementations of NAM models, leaving the general audio tools that other builders are likely not interested in as a separated-out dependency.

Interesting--doesn't build on my Windows machine...digging into it to be sure the Solution is configured correctly.

*Deep breath*


[BEAM-8292] Portable Reshuffle for Go SDK

This adds a Reshuffle transform to the Go SDK.

In particular, it configures windowing & trigggers for a GBK to allow for fusion breaks, where parallelism needs to increase, or decrease due to data bundling properties.
Previous element window and timestamps are preserved.
The SDK operations are wrapped with a higher level reshuffle URN so runners can optimize this step better.
The Go Direct Runner is aware of the Reshuffle and correctly ignores it, as it's a single bundle runner.

Note: While this should work for streaming cases, it hasn't been tested with them yet, due to the current state of streaming the Go SDK.
It further adds one small optimization for the internal Decoding interface, called the DecodeTo method to avoid extra allocations to the heap incurred by returning a *FullValue. Can't avoid extra allocations for KV types at present, but value PCollections should have lower overhead. A subsequent PR will use the DecodeTo method at a other applicable places in the decode stack.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

Run Go Postcommit

R: @youngoli

I'm definitely not merging this until both the PostCommit runs, and someone more familiar with windowing/trigger semantics looks over the configuration I copied over from python:
https://github.com/apache/beam/pull/11197/files#diff-ef420fdb9afbce0674282b4ed4481042R530

Retest this please

Run Go Postcommit

Post commits run and pass which is a good sign!


idp display name not available

the display name config field is not available. one there cannot change the name od the apple idp

True that.
The Apple extension behaves the same way as all the other social providers do. The name is hardcoded so to say.
I'll provide another alpha version soon

In any case: If you need to support multiple languages you might consider overriding the Apple-Login button in your login theme anyways, as you can only define one text in the admin ui.

The displayname is editable in the latest release


Use Map rather than object-as-Map in our Redux state

This is an optimization, and a code cleanup, that will also help us toward #3949.
Our Redux state tree is currently made up entirely of primitive values, plain arrays, and plain objects. These are very nice for struct-like data structures like User or Message. They're not so nice for key-value maps: we end up using objects as maps, and that's messier in the code and for type-checking than a proper Map. It also turns out to be about 2x slower for building them up and making new ones, as measured in https://github.com/zulip/zulip-mobile/issues/3339#issuecomment-462963242 .
So, where we use an object as a map, we should use a real Map instead. (Better, perhaps, an Immutable.Map -- that's #3949. But this will be a step on the way.)
We've already converted lots of objects-as-maps to real Maps in much of our code, notably in the return values of caching selectors. The reason we haven't yet done so at all in our Redux state tree is a technical obstacle that shouldn't fundamentally be complicated once we work out how, but will require some working out: we'll need to serialize and deserialize these data structures for redux-persist.
Specifically we'll need to study the docs of redux-persist and friends, then possibly their implementations where docs are inadequate, in order to see how to wire up appropriate serialization and deserialization functions.
Relatedly, we'll want to think through and test the migration path: what happens when a version of the app using a new data structure (for a given spot in the Redux state tree) first launches and there's existing data serialized by a version of the app that used the old data structure.
Some quick notes (adapted from notes I made after some reading in 2019-04) on possible tools for the persistence side:

The redux-persist feature we want is "transforms": https://github.com/rt2zz/redux-persist#transforms
In particular remotedev-serialize looks like a pretty good-quality implementation of serializing things like Map and Set. It'll also support Immutable.js data structures if we go on to adopt those in the future (#3949). The implementation is here:
https://github.com/kolodny/jsan/blob/master/lib/cycle.js
and enabled here:
https://github.com/zalmoxisus/remotedev-serialize/blob/master/constants/options.js

The migration will happen one data structure at a time; each one is pretty much independent of others. Most of the work will probably come as part of doing the first one, though -- figuring out just how to handle persistence and any migration, and getting that set up.

I think this is now subsumed in #3949.
We've now experimented with Immutable.Map, done the work to be able to use it, and started doing so in various parts of the state. That'll usually be preferable to plain JS Map for anything within Redux, because it lets us make updates efficiently.

I think this is now subsumed in #3949.
We've now experimented with Immutable.Map, done the work to be able to use it, and started doing so in various parts of the state. That'll usually be preferable to plain JS Map for anything within Redux, because it lets us make updates efficiently.


Implement proxy settings for TestCafe

Are you requesting a feature or reporting a bug?
feature
What is the current behavior?
In corporate networks, where browser have specified proxy settings for access to WEB, TestCafe cannot establish connection to the remote resources, cause all requests are sent directly to the remote host, bypassing corporate proxy.
What is the expected behavior?
TestCafe should provide capability to setup proxy options, like http proxy url, http proxy port etc

https://github.com/DevExpress/testcafe-hammerhead/issues/1032

Let determine API for this feature.
My proposal:
CLI:
New options:
--proxy-url
--proxy-ignore

testcafe chrome tests/ --proxy-url x.x.x.x --proxy-ignore "a.com,b.com"

Programming Interface:
const proxyUrl = 'x.x.x.x'
const ignoreHosts = ['a.com', 'b.com'];

runner
    .proxy(proxyUrl, ignoreHosts)

/cc @DevExpress/testcafe-docs @inikulin @VasilyStrelyaev

What's proxy ignore options are for?

maybe proxy-bypass instead of proxy-ignore (if I get it right)?

So, as I understand, we've decided don't add proxy-ignore option for now.
CLI:
New option:
--proxy-url

testcafe chrome tests/ --proxy-url x.x.x.x

Programming Interface:
const proxyUrl = 'x.x.x.x'

runner
    .proxy(proxyUrl)

Is it ok?

@AlexanderMoskovkin, we can specify proxy port in the url, if it necessary. I mean, change 'x.x.x.x' to 'x.x.x.x:yyyy' in these snippets (in the docs in the future).

any update ?

@tiagorosendo We are working on it. More likely it will be released in alpha in a couple of weeks.

Ok thanks !

Why did you guys decide on not adding proxy-ignore option? Is there any plan to add this in future and if not can I help contribute?

@anescobar1991 We've decided to start with minimal feature set and advanced features afterwards if there will be a demand for them. If you are interested in this feature, open new issue, please. PRs are welcome as well.

any update on this?

It's already available (since the 0.15.0 version). See the --proxy option for details.

It seems that the proxy option sets the proxy even for requests to localhost, I think it would make sense to ignore the proxy for requests to localhost or <IP_ADDRESS>. What do you think?

@n0v1, It sounds reasonable. We'll think about it in the context of the #1791 issue.

@AlexanderEgorov
I tried below your solutions to implement Proxy setting but did not get any proper solution:
1)I tried with command (testcafe chrome tests/ --proxy-url x.x.x.x --proxy-ignore "a.com,b.com")  but it does not work for me . Can you please provide the exact syntax.
2)test runner -It's saying proxy is not a function
Also i gone thorugh http://devexpress.github.io/testcafe/documentation/using-testcafe/common-concepts/browsers/user-profiles.html and tried to create new user profile but it  also does work for me .
It would be great if you can reply ASAP.

Hi @MishraApa,
You can find the correct TestCafe API in our documentation.
Now TestCafe has option --proxy which specifies the proxy server in your local network to access the Internet.
The proxy-ignore feature is not implemented yet but will be included in the next TestCafe release.

Hi @AlexanderMoskovkin
I have tried above solution provided in documentation to host proxy  but none of the solution is working for me .Could please suggest how to do proxy setting testcafe ?
Thanks
Aparna

Could you please describe your issue in details?


Timber initializing too early

Expected behavior
Timber to initialize after all plugins or mu-plugins are able to hook into WordPress functions.
This bug is specific for timber-library (WP plugin), since initialization for timber/timber will have be done by the theme developer.
Actual behavior
Timber initializes before this happens (at inclusion). This is especially a problem in Multisite, because network plugins are loaded before muplugins_loaded is called.
Right now, plugins are forced to be a mu-plugin AND cannot use muplugins_loaded to register their actions. Possibly, Timber should even be initialized on setup_theme instead or at least at plugins_loaded.
Use case
Related to #1056: Timber\ImageHelper::add_constants() is run on inclusion as well (when initializing Timber). This does not allow plugins to hook into home_url() and change it.
The specific use-case would be when mapping a WordPress Multisite install to a domain. In this case, a filter should be used to change the home_url().
I'm not sure if the problem is as broad as "Timber initializing too early" or if it's a specific bug for this use-case.
Steps to reproduce behavior
For the specific use-case:

Use WordPress Multisite
Create a subdirectory install
Map this website to a domain by filtering home_url() or using a plugin that does this
Sideload an image (for example, by resizing an external image)

What version of WordPress, PHP and Timber are you using?
WordPress 4.5.2, PHP 7.0, Timber 1.0.4.
How did you install Timber? (for example, from GitHub, Composer/Packagist, WP.org?)
Composer via WPackagist.

+1
I've experienced the same issue when running Wordpress with Bedrock, it changes the default content directory and install location for Wordpress.

+1
Its also an issue if you have Timber library installed, but local version in your own theme. Timber plugin registers and initializes itself as soon as the plugin php file gets loaded, which causes issues if theme uses different version of Timber.

@haroldangenent  @mahagr Is this still something you're actively working on or need addressed? Please respond in two weeks or we'll close this thread

Yes, nothing has changed so I believe this is still an issue when using the plugin. It should at least be documented that timber/timber should be used for multisites that use domain mapping.

I'm using bedrock with Timber and didn't had any problems. I'm also using domain mapping. The only difference is the fact I'm not using the plugin but the composer module.
I'm also using "roots/multisite-url-fixer": "*".
Can you try using the module and this mu-plugin.

It's no issue if you're using Composer package, but you really shouldn't install the plugin or you're in trouble when it updates and you're still using the old version in the theme.

From what I know Timber 2.0 will be available only as a composer package.
So I'm not sure about fixing those bugs. Let's wait for Jared's or Lukas
opinion.
śr., 7 lis 2018, 18:54: Matias Griese<EMAIL_ADDRESS>napisał(a):

It's no issue if you're using Composer package, but you really shouldn't
install the plugin or you're in trouble when it updates and you're still
using the old version in the theme.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/timber/timber/issues/1058#issuecomment-436716661, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACO-OhBmbfR248R3ice4ZLWhjPrFILGrks5usx5kgaJpZM4IxAdu
.

From what I know Timber 2.0 will be available only as a composer package.

Yes, that’s right. Releasing Timber 2.0 with the plugin version would break so many websites because of all the breaking changes. And Timber probably wouldn’t be accepted as a new plugin for version 2, because it’s not a "real" plugin. That’s why from 2.0, it will only be available as a Composer package.
Because the issue here is a case that can easily be circumvented by using the Composer package, I wouldn’t invest the time to fix this for the plugin version that will be outdated soon. But we could add a hint in the documentation for 1.x. Pull requests welcome 🙂.

@gchtr Well, the issue is opposite. If you have Timber plugin installed, Timber 2.0 based themes will not work. You need to uninstall Timber plugin to get them to work.

@mahagr That’s exactly what I meant or tried to say. Maybe I wasn’t clear enough.


I'm having problem seeing the entire table

Link to article:
"Tell us where exactly a problem occurs."
https://docs.microsoft.com/en-us/windows/win32/direct3ddxgi/hardware-support-for-direct3d-12-1-formats
Problem:
"What's wrong with the article?"
I have a very wide display and I want to view the table on this article, but no matter what I do (using Chrome or IE browser, making window size larger) I only see a small region of the table on screen with scroll bars.  How can I make the table fill the screen so it is easy to read?

That seems like a tough issue to solve. Adding @stevewhims to take a look.

Yes, this is very tricky. All of the topics in this series of topics have this same problem. This is the only topic in the series that has tried to break a single table down into multiple tables (breaking at arbitrary places in the list of 115 formats) presumably to try and alleviate slightly the scrolling issue. It doesn't alleviate it enough, though.
What I'm inclined to do is this. Break the topic down into 115 sections; one for each format. The "in this article" sidebar on the right will serve as a list of formats with links to the appropriate section. Each section will contain a table with a row per target. None of the tables will need to scroll at all. The entire web page will scroll vertically like all web pages do. I realize it'll mean duplicating the list of targets 115 times, but I see no better alternative. A table with frozen rows/column labels and always onscreen scrollbars would be better than what we have here, but we can't achieve that technically.
I'll add fixing this to my TODO list and get to it asap.
~Steve

So my use case is to look up a certain format, like "R10G10B10A2_UNORM", and see all the information about that format, preferably with as much information on screen at once.  Are suggesting making one table per format with all of the information on one or two tall columns, so no horizontal scrolling?  (I think I'm confused when you say "table with a row per target".)

This is the result (see attached image) of some hacking and browser extensions.  Is this not possible to achieve on the Microsoft website?  Why is the table width restricted so much?

@ChuckM2, what I'm thinking is that each format would be represented by its own section. Here's what just the first format's section would look like:
The images are broken here, but they won't be in the final topic. And you could then navigate to the topic, search for the format(s) you're interested in, and view the table in that section. As I say, the "in this article" sidebar on the right would serve as a list of formats with links to the appropriate section.
So there would be 115 tables like this, one for each format.
DXGI_FORMAT_UNKNOWNL (0)

Target
Support

Bits Per Element (BPE)
0

Format Support

Buffer

Input Assembler Vertex Buffer
-

Input Assembler Index Buffer
-

Stream Output Buffer
-

Texture1D
-

Texture2D
-

Texture3D
-

TextureCube
-

Shader ld
-

Shader sample (any filter)
-

Shader sample_c (comparison filter)
-

Shader sample (mono 1_bit_filter)
-

Shader gather4
-

Shader gather4_c
-

Mipmap
-

Mipmap Auto- Generation
-

RenderTarget
-

Blendable RenderTarget
-

Output Merger Logic Op
-

Depth/Stencil Target
-

Raw UAV and SRV
-

Structured UAV and SRV

Typed UAV
-

UAV Typed Store
-

UAV Typed Load
-

UAV Atomic Add
-

UAV Atomic Bitwise Ops
-

UAV Atomic Cmp&Store/ Cmp&Exch
-

UAV Atomic Exchange
-

UAV Atomic Signed Min/Max
-

UAV Atomic Unsigned Min/Max
-

CPU Lockable

4x Multisample RenderTarget
-

8x Multisample RenderTarget
-

Other Multisample Count RT
-

Multisample Resolve
-

Multisample Load
-

Display Scan-Out
-

Cast Within Bit Layout
-

Video Decoder Support
-

Video Processor Input
-

Video Processor Output
-

Shared Resource
-

BackBuffer Castable Even Fully Typed

Tiled Resource

I'll go ahead and close this GitHub issue now that it's resolved. Thanks, all!
-Steve


[staging-next] python3Packages.poetry*: fixes

Motivation for this change
Looks like nix-update picked up a pre-release, and I didn't do enough testing on the previous PR
Things done

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

[x] 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/)
[ ] 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.

https://github.com/python-poetry/poetry-core/releases/tag/1.1.0a3
Clearly marked as pre-release, but the release atom feed does not seem to reflect that.
<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xmlns:media="http://search.yahoo.com/mrss/" xml:lang="en-US">
  <id>tag:github.com,2008:https://github.com/python-poetry/poetry-core/releases</id>
  <link type="text/html" rel="alternate" href="https://github.com/python-poetry/poetry-core/releases"/>
  <link type="application/atom+xml" rel="self" href="https://github.com/python-poetry/poetry-core/releases.atom"/>
  <title>Release notes from poetry-core</title>
  <updated>2021-04-09T15:37:58Z</updated>
  <entry>
    <id>tag:github.com,2008:Repository/238972646/1.1.0a3</id>
    <updated>2021-04-09T15:49:33Z</updated>
    <link rel="alternate" type="text/html" href="https://github.com/python-poetry/poetry-core/releases/tag/1.1.0a3"/>
    <title>1.1.0a3</title>
    <content type="html">
Fixed

Fixed dependency markers not being properly copied when changing the constraint (#162).

</content>
    <author>
      <name>sdispater</name>
    </author>
    <media:thumbnail height="30" width="30" url="https://avatars.githubusercontent.com/u/555648?s=60&v=4"/>
  </entry>
  <entry>
    <id>tag:github.com,2008:Repository/238972646/1.0.3</id>
    <updated>2021-04-09T15:45:11Z</updated>
    <link rel="alternate" type="text/html" href="https://github.com/python-poetry/poetry-core/releases/tag/1.0.3"/>
    <title>1.0.3</title>
    <content type="html">
Fixed

Fixed an error when handling single-digit Python markers (#156).

Fixed dependency markers not being properly copied when changing the constraint (#163).

</content>
    <author>
      <name>sdispater</name>
    </author>
    <media:thumbnail height="30" width="30" url="https://avatars.githubusercontent.com/u/555648?s=60&v=4"/>
  </entry>
  <entry>
    <id>tag:github.com,2008:Repository/238972646/1.1.0a2</id>
    <updated>2021-04-08T15:57:30Z</updated>
    <link rel="alternate" type="text/html" href="https://github.com/python-poetry/poetry-core/releases/tag/1.1.0a2"/>
    <title>1.1.0a2</title>
    <content type="html">
Fixed

Fixed performance regressions when parsing version constraints (#152).

Fixed how local build versions are handled and compared (#157, #158).

Fixed errors when parsing some environment markers (#155).

</content>
    <author>
      <name>sdispater</name>
    </author>
    <media:thumbnail height="30" width="30" url="https://avatars.githubusercontent.com/u/555648?s=60&v=4"/>
  </entry>
  <entry>
    <id>tag:github.com,2008:Repository/238972646/1.1.0a1</id>
    <updated>2021-03-30T15:21:27Z</updated>
    <link rel="alternate" type="text/html" href="https://github.com/python-poetry/poetry-core/releases/tag/1.1.0a1"/>
    <title>1.1.0a1</title>
    <content type="html">
This version is the first to drop support for Python 2.7 and 3.5.

If you are still using these versions you should update the requires property of the build-system section

to restrict the version of poetry-core:

[build-system]
requires = ["poetry-core&lt;1.1.0"]
build-backend = "poetry.core.masonry.api"

Changed

Dropped support for Python 2.7 and 3.5 (#131).

Reorganized imports internally to improve performances (#131).

Directory dependencies are now in non-develop mode by default (#98).

Improved support for PEP 440 specific versions that do not abide by semantic versioning (#140).

Fixed

Fixed path dependencies PEP 508 representation (#141).

</content>
    <author>
      <name>sdispater</name>
    </author>
    <media:thumbnail height="30" width="30" url="https://avatars.githubusercontent.com/u/555648?s=60&v=4"/>
  </entry>
  <entry>
    <id>tag:github.com,2008:Repository/238972646/1.0.2</id>
    <updated>2021-02-05T20:24:14Z</updated>
    <link rel="alternate" type="text/html" href="https://github.com/python-poetry/poetry-core/releases/tag/1.0.2"/>
    <title>1.0.2</title>
    <content type="html">
Fixed

Fixed a missing import causing an error in Poetry (#134).

</content>
    <author>
      <name>sdispater</name>
    </author>
    <media:thumbnail height="30" width="30" url="https://avatars.githubusercontent.com/u/555648?s=60&v=4"/>
  </entry>
  <entry>
    <id>tag:github.com,2008:Repository/238972646/1.0.1</id>
    <updated>2021-02-05T19:54:21Z</updated>
    <link rel="alternate" type="text/html" href="https://github.com/python-poetry/poetry-core/releases/tag/1.0.1"/>
    <title>1.0.1</title>
    <content type="html">
Fixed

Fixed PEP 508 representation of dependency without extras (#102).

Fixed an error where development dependencies were being resolved when invoking the PEP-517 backend (#101).

Fixed source distribution not being deterministic (#105).

Fixed an error where zip files were left open when building wheels (#122).

Fixed an error where explicitly included files were still not present in final distributions (#124).

Fixed wheel filename matching for recent architecture (#125, #129).

Fixed an error where the &amp; character was not accepted for author names (#120).

Fixed the PEP-508 representation of some dependencies (#103).

Fixed the Requires-Python metadata generation (#127).

Fixed an error where pre-release versions were accepted in version constraints (#128).

</content>
    <author>
      <name>sdispater</name>
    </author>
    <media:thumbnail height="30" width="30" url="https://avatars.githubusercontent.com/u/555648?s=60&v=4"/>
  </entry>
  <entry>
    <id>tag:github.com,2008:Repository/238972646/1.0.0</id>
    <updated>2020-09-30T23:13:50Z</updated>
    <link rel="alternate" type="text/html" href="https://github.com/python-poetry/poetry-core/releases/tag/1.0.0"/>
    <title>1.0.0</title>
    <content>No content.</content>
    <author>
      <name>sdispater</name>
    </author>
    <media:thumbnail height="30" width="30" url="https://avatars.githubusercontent.com/u/555648?s=60&v=4"/>
  </entry>
  <entry>
    <id>tag:github.com,2008:Repository/238972646/1.0.0rc3</id>
    <updated>2020-09-30T20:36:22Z</updated>
    <link rel="alternate" type="text/html" href="https://github.com/python-poetry/poetry-core/releases/tag/1.0.0rc3"/>
    <title>1.0.0rc3</title>
    <content type="html">
Changed

Removed intreehooks build backend in favor of the backend-path mechanism (#90).

Directory dependencies will now always use a posix path for their representation (#90).

Dependency constraints can now be set directly via a proper setter (#90).

</content>
    <author>
      <name>sdispater</name>
    </author>
    <media:thumbnail height="30" width="30" url="https://avatars.githubusercontent.com/u/555648?s=60&v=4"/>
  </entry>
  <entry>
    <id>tag:github.com,2008:Repository/238972646/1.0.0rc2</id>
    <updated>2020-09-25T13:41:45Z</updated>
    <link rel="alternate" type="text/html" href="https://github.com/python-poetry/poetry-core/releases/tag/1.0.0rc2"/>
    <title>1.0.0rc2</title>
    <content>No content.</content>
    <author>
      <name>sdispater</name>
    </author>
    <media:thumbnail height="30" width="30" url="https://avatars.githubusercontent.com/u/555648?s=60&v=4"/>
  </entry>
  <entry>
    <id>tag:github.com,2008:Repository/238972646/1.0.0rc1</id>
    <updated>2020-09-25T10:55:37Z</updated>
    <link rel="alternate" type="text/html" href="https://github.com/python-poetry/poetry-core/releases/tag/1.0.0rc1"/>
    <title>1.0.0rc1</title>
    <content type="html">
Fixed

Fixed Python constraint propagation when converting a package to a dependency (#84).

Fixed VCS ignored files being included in wheel distributions for projects using the src layout (#81)

</content>
    <author>
      <name>sdispater</name>
    </author>
    <media:thumbnail height="30" width="30" url="https://avatars.githubusercontent.com/u/555648?s=60&v=4"/>
  </entry>
</feed>

https://github.com/python-poetry/poetry-core/releases.atom
There is a better api endpoint that we already use in the home-assistant update script.
{
  "url": "https://api.github.com/repos/python-poetry/poetry-core/releases/41192682",
  "assets_url": "https://api.github.com/repos/python-poetry/poetry-core/releases/41192682/assets",
  "upload_url": "https://uploads.github.com/repos/python-poetry/poetry-core/releases/41192682/assets{?name,label}",
  "html_url": "https://github.com/python-poetry/poetry-core/releases/tag/1.0.3",
  "id": 41192682,
  "author": {
    "login": "sdispater",
    "id": 555648,
    "node_id": "MDQ6VXNlcjU1NTY0OA==",
    "avatar_url": "https://avatars.githubusercontent.com/u/555648?v=4",
    "gravatar_id": "",
    "url": "https://api.github.com/users/sdispater",
    "html_url": "https://github.com/sdispater",
    "followers_url": "https://api.github.com/users/sdispater/followers",
    "following_url": "https://api.github.com/users/sdispater/following{/other_user}",
    "gists_url": "https://api.github.com/users/sdispater/gists{/gist_id}",
    "starred_url": "https://api.github.com/users/sdispater/starred{/owner}{/repo}",
    "subscriptions_url": "https://api.github.com/users/sdispater/subscriptions",
    "organizations_url": "https://api.github.com/users/sdispater/orgs",
    "repos_url": "https://api.github.com/users/sdispater/repos",
    "events_url": "https://api.github.com/users/sdispater/events{/privacy}",
    "received_events_url": "https://api.github.com/users/sdispater/received_events",
    "type": "User",
    "site_admin": false
  },
  "node_id": "MDc6UmVsZWFzZTQxMTkyNjgy",
  "tag_name": "1.0.3",
  "target_commitish": "01c0472d9cef3e1a4958364122dd10358a9bd719",
  "name": "1.0.3",
  "draft": false,
  "prerelease": false,
  "created_at": "2021-04-09T15:33:40Z",
  "published_at": "2021-04-09T15:44:43Z",
  "assets": [

  ],
  "tarball_url": "https://api.github.com/repos/python-poetry/poetry-core/tarball/1.0.3",
  "zipball_url": "https://api.github.com/repos/python-poetry/poetry-core/zipball/1.0.3",
  "body": "### Fixed\r\n\r\n- Fixed an error when handling single-digit Python markers ([#156](https://github.com/python-poetry/poetry-core/pull/156)).\r\n- Fixed dependency markers not being properly copied when changing the constraint ([#163](https://github.com/python-poetry/poetry-core/pull/163))."
}

https://api.github.com/repos/python-poetry/poetry-core/releases/latest
Aaaaand I guess I'll file an issue with nix-update.


com.ctc.wstx.exc.WstxParsingException while reading some emails

We have a java web application which connects to exchange webservice api and reads emails.
5% to 10% of emails were failing throwing exception as below:
    [com.ctc.wstx.exc.WstxLazyException] com.ctc.wstx.exc.WstxParsingException: Invalid character reference: null character not allowed in XML content.
    ...
    GetItemRequest(SimpleServiceRequestBase).internalExecute() line: 58
    ...
    microsoft.exchange.webservices.data.ServiceRequestException: The request failed. Invalid character reference: null character not allowed in XML content. at [row,col {unknown-source}]: [254,5]]

Via debugging we saw the response XML contains NUL or 0x0000 (represented as the character reference �) which is illegal in XML.
It is a well-formedness (fatal) error.
For some particulars, see http://www.w3.org/TR/REC-xml/#NT-Char

This problem is not so rare, there are some solutions like http://stackoverflow.com/questions/4237625/removing-invalid-xml-characters-from-a-string-in-java.
To clean invalid characters (based on XML spec) from XML response microsoft.exchange.webservices.data.SimpleServiceRequestBase#readResponse can be modified.

I could fix it by surrounding assertions of EwsXmlReader.isEmptyElement() method with try/catch block:
	public boolean isEmptyElement() throws XMLStreamException {
		boolean isPresentStartElement = false;
		boolean isNextEndElement= false;
		try {
			isPresentStartElement = this.presentEvent.isStartElement();
		} catch ( Exception e ) {
		}
		try {
			isNextEndElement = this.xmlReader.peek().isEndElement();
		} catch ( Exception e ) {
		}
		return isPresentStartElement && isNextEndElement;
	}

Guys I'm with a problem that I think is very much like this and do not know what to do. To capture some emails I get the following error message:
The request failed. ParseError at [row, col]: [1.1475]
Message: Character Referece "&# at microsoft.exchange.webservices.data.SimpleServiceRequestBase.internalExecute(SimpleServiceRequestBase.java:71)
I enabled the trace and saw the xml response that causes the problem, as stretch below:
<t:Subject>Pendencia(s) COVSB600 - PV 1582 - CONVENIO 975300 - CASEBRS CAIXA ASSIS</t:Subject>

Within the subject it has a special character (CASEBR&#x1A represents a little arrow);. Could anyone help me?
Regards,
Lucas

Can you please provide a way to disable XML validation, skip or replace invalid XML characters, or otherwise provide access to the response InputStream so that we may do our own filtering?

Are characters you are seeing valid XML 1.1? I have run into a number of cases where EWS provides a XML 1.0 preamble but includes unicode escape characters that are only valid under XML 1.1. Fixing the preamble prior to parsing resolves the issue across the board without having to disable validation.

Any news here?
Got the same "issue" 👍
 m.e.w.d.property.complex.ItemAttachment  : com.ctc.wstx.exc.WstxParsingException: Illegal character entity: expansion character (code 0xb
Is there any build in solution?

@OS-JaR there's a fix for it here but it introduces a dependency. It works for me. https://github.com/OfficeDev/ews-java-api/pull/409

@easel: Nearly one year later I'm back here. Thanks alot for #409 , I already implemented it and it works well for me. Now I have two new cases:
The request failed. Invalid character reference: null character not allowed in XML content.\r\n at [row,col {unknown-source}]: [1284,834]
and
Illegal character entity: expansion character (code 0xffff\r\n at [row,col {unknown-source}]: [234,3633].
This can't be fixed by replacing xml 1.,0 with xml 1.1. I tried to implement a ExtendedInvalidXmlCharacterModifier, based on this one. Does anyone have some tips and/or experience? Does it work? Any ideas how to test it, especially how to insert those chars into emails to got such invalid responses?


chore(*): reformat codebase using pre-commit

What Changed

Reformatted codebase using pre-commit configuration (isort/black)
Added some exclusions to pre-commit for data, migration files, minified files, etc

Limitations
n/a

@mehaase @emmanvg this PR reformats and is ready to go. The only CI failure is related to the diff coverage being lower than 94.5% (at 93.61%) which can be safely ignored.


Error with illuminate/database

Fatal error: Uncaught InvalidArgumentException: The database connection must be an instance of either PdoDatabase, PdoDsnorPDO in C:\wamp\www\phpus\vendor\delight-im\auth\src\UserManager.php:90 Stack trace: #0 C:\wamp\www\phpus\vendor\delight-im\auth\src\Auth.php(45): Delight\Auth\UserManager->__construct(Object(Illuminate\Database\Capsule\Manager), NULL, NULL) #1 C:\wamp\www\phpus\index.php(29): Delight\Auth\Auth->__construct(Object(Illuminate\Database\Capsule\Manager)) #2 {main} thrown in C:\wamp\www\phpus\vendor\delight-im\auth\src\UserManager.php on line 90

Thanks!
How did you install this library? Using Composer or manually?
The error occurs because illuminate/database is the wrong database component.

Using Composer

Thanks!
Please take a close look at the following section of the README again:
https://github.com/delight-im/PHP-Auth#creating-a-new-instance
The database instance that you pass to new \Delight\Auth\Auth($db) must not be of type \Illuminate\Database\Capsule\Manager. The README shows how to create the database instance – in several possible ways.


[LML] AnimatedImage and non-continuous rendering

It appears like AnimatedImage is not compatible with non-continuous rendering mode, and should call Gdx.graphics.requestRendering() inside of Actor#act().
I feel like non-continuous rendering case was just dropped during development and never tested. So maybe there is more code that doesn't not support it in the repo.

Gdx.graphics.requestRendering() will be called after each frame update.

Unfortunately this won't work, since updateFrame() triggers by counter from act(float) and thus requires act(float) to be called continuously every frame.
I'm afraid the easiest way to solve this is to call Gdx.graphics.requestRendering() inside of act(float). There is also another way to update frames - use Timer, but this will involve a bit more changes and also few more checks should be considered due to Timer may trigger callbacks after related actor removed from the stage...