[openssl] Build Failure - Failure to Download

Host Environment

OS: Windows 10 Latest

To Reproduce
Steps to reproduce the behavior:
./vcpkg install openssl
Failure logs
-- Downloading https://repo.msys2.org/mingw/i686/mingw-w64-i686-libwinpthread-git-<IP_ADDRESS>06.c9a21571-1-any.pkg.tar.zst;https://www2.futureware.at/~nickoe/msys2-mirror/mingw/i686/mingw-w64-i686-libwinpthread-git-<IP_ADDRESS>06.c9a21571-1-any.pkg.tar.zst;https://mirror.yandex.ru/mirrors/msys2/mingw/i686/mingw-w64-i686-libwinpthread-git-<IP_ADDRESS>06.c9a21571-1-any.pkg.tar.zst;https://mirrors.tuna.tsinghua.edu.cn/msys2/mingw/i686/mingw-w64-i686-libwinpthread-git-<IP_ADDRESS>06.c9a21571-1-any.pkg.tar.zst;https://mirrors.ustc.edu.cn/msys2/mingw/i686/mingw-w64-i686-libwinpthread-git-<IP_ADDRESS>06.c9a21571-1-any.pkg.tar.zst;https://mirror.bit.edu.cn/msys2/mingw/i686/mingw-w64-i686-libwinpthread-git-<IP_ADDRESS>06.c9a21571-1-any.pkg.tar.zst;https://mirror.selfnet.de/msys2/mingw/i686/mingw-w64-i686-libwinpthread-git-<IP_ADDRESS>06.c9a21571-1-any.pkg.tar.zst;https://mirrors.sjtug.sjtu.edu.cn/msys2/mingw/i686/mingw-w64-i686-libwinpthread-git-<IP_ADDRESS>06.c9a21571-1-any.pkg.tar.zst -> msys-mingw-w64-i686-libwinpthread-git-<IP_ADDRESS>06.c9a21571-1-any.pkg.tar.zst...
[DEBUG] Feature flag 'binarycaching' unset
[DEBUG] Feature flag 'manifests' = off
[DEBUG] Feature flag 'compilertracking' unset
[DEBUG] Feature flag 'registries' unset
[DEBUG] Feature flag 'versions' unset
[DEBUG] Downloading https://repo.msys2.org/mingw/i686/mingw-w64-i686-libwinpthread-git-<IP_ADDRESS>06.c9a21571-1-any.pkg.tar.zst
[DEBUG] Downloading https://www2.futureware.at/~nickoe/msys2-mirror/mingw/i686/mingw-w64-i686-libwinpthread-git-<IP_ADDRESS>06.c9a21571-1-any.pkg.tar.zst
[DEBUG] Downloading https://mirror.yandex.ru/mirrors/msys2/mingw/i686/mingw-w64-i686-libwinpthread-git-<IP_ADDRESS>06.c9a21571-1-any.pkg.tar.zst
[DEBUG] Downloading https://mirrors.tuna.tsinghua.edu.cn/msys2/mingw/i686/mingw-w64-i686-libwinpthread-git-<IP_ADDRESS>06.c9a21571-1-any.pkg.tar.zst
[DEBUG] Downloading https://mirrors.ustc.edu.cn/msys2/mingw/i686/mingw-w64-i686-libwinpthread-git-<IP_ADDRESS>06.c9a21571-1-any.pkg.tar.zst
[DEBUG] Downloading https://mirror.bit.edu.cn/msys2/mingw/i686/mingw-w64-i686-libwinpthread-git-<IP_ADDRESS>06.c9a21571-1-any.pkg.tar.zst
[DEBUG] Download failed -- retrying after 1000 ms.
[DEBUG] Download failed -- retrying after 2000 ms.
[DEBUG] Download failed -- retrying after 4000 ms.
[DEBUG] Downloading https://mirror.selfnet.de/msys2/mingw/i686/mingw-w64-i686-libwinpthread-git-<IP_ADDRESS>06.c9a21571-1-any.pkg.tar.zst
[DEBUG] Downloading https://mirrors.sjtug.sjtu.edu.cn/msys2/mingw/i686/mingw-w64-i686-libwinpthread-git-<IP_ADDRESS>06.c9a21571-1-any.pkg.tar.zst
Error: Failed to download from mirror set:
https://repo.msys2.org/mingw/i686/mingw-w64-i686-libwinpthread-git-<IP_ADDRESS>06.c9a21571-1-any.pkg.tar.zst: failed: status code 404
https://www2.futureware.at/~nickoe/msys2-mirror/mingw/i686/mingw-w64-i686-libwinpthread-git-<IP_ADDRESS>06.c9a21571-1-any.pkg.tar.zst: failed: status code 404
https://mirror.yandex.ru/mirrors/msys2/mingw/i686/mingw-w64-i686-libwinpthread-git-<IP_ADDRESS>06.c9a21571-1-any.pkg.tar.zst: failed: status code 404
https://mirrors.tuna.tsinghua.edu.cn/msys2/mingw/i686/mingw-w64-i686-libwinpthread-git-<IP_ADDRESS>06.c9a21571-1-any.pkg.tar.zst: failed: status code 404
https://mirrors.ustc.edu.cn/msys2/mingw/i686/mingw-w64-i686-libwinpthread-git-<IP_ADDRESS>06.c9a21571-1-any.pkg.tar.zst: failed: status code 404
https://mirror.bit.edu.cn/msys2/mingw/i686/mingw-w64-i686-libwinpthread-git-<IP_ADDRESS>06.c9a21571-1-any.pkg.tar.zst: WinHttpSendRequest() failed: 12007
https://mirror.bit.edu.cn/msys2/mingw/i686/mingw-w64-i686-libwinpthread-git-<IP_ADDRESS>06.c9a21571-1-any.pkg.tar.zst: WinHttpSendRequest() failed: 12007
https://mirror.bit.edu.cn/msys2/mingw/i686/mingw-w64-i686-libwinpthread-git-<IP_ADDRESS>06.c9a21571-1-any.pkg.tar.zst: WinHttpSendRequest() failed: 12007
https://mirror.bit.edu.cn/msys2/mingw/i686/mingw-w64-i686-libwinpthread-git-<IP_ADDRESS>06.c9a21571-1-any.pkg.tar.zst: WinHttpSendRequest() failed: 12007
https://mirror.selfnet.de/msys2/mingw/i686/mingw-w64-i686-libwinpthread-git-<IP_ADDRESS>06.c9a21571-1-any.pkg.tar.zst: failed: status code 404
https://mirrors.sjtug.sjtu.edu.cn/msys2/mingw/i686/mingw-w64-i686-libwinpthread-git-<IP_ADDRESS>06.c9a21571-1-any.pkg.tar.zst: failed: status code 404

[DEBUG] D:\a\_work\1\s\src\vcpkg\base\downloads.cpp(656)
[DEBUG] Time in subprocesses: 0 us
[DEBUG] Time in parsing JSON: 2 us
[DEBUG] Time in JSON reader: 0 us
[DEBUG] Time in filesystem: 7231 us
[DEBUG] Time in loading ports: 0 us
[DEBUG] Exiting after 14.31 s (14284328 us)

CMake Error at scripts/cmake/vcpkg_download_distfile.cmake:84 (message):

      Failed to download file with error: 1
      If you use a proxy, please check your proxy setting. Possible causes are:

      1. You are actually using an HTTP proxy, but setting HTTPS_PROXY variable
         to `https://address:port`. This is not correct, because `https://` prefix
         claims the proxy is an HTTPS proxy, while your proxy (v2ray, shadowsocksr
         , etc..) is an HTTP proxy. Try setting `http://address:port` to both
         HTTP_PROXY and HTTPS_PROXY instead.

      2. You are using Fiddler. Currently a bug (https://github.com/microsoft/vcpkg/issues/17752)
         will set HTTPS_PROXY to `https://fiddler_address:port` which lead to problem 1 above.
         Workaround is open Windows 10 Settings App, and search for Proxy Configuration page,
         Change `http=address:port;https=address:port` to `address`, and fill the port number.

      3. You proxy's remote server is out of service.

      In future vcpkg releases, if you are using Windows, you no longer need to set
      HTTP(S)_PROXY environment variables. Vcpkg will simply apply Windows IE Proxy
      Settings set by your proxy software. See (https://github.com/microsoft/vcpkg-tool/pull/49)
      and (https://github.com/microsoft/vcpkg-tool/pull/77)

      Otherwise, please submit an issue at https://github.com/Microsoft/vcpkg/issues

Call Stack (most recent call first):
  scripts/cmake/vcpkg_download_distfile.cmake:309 (z_vcpkg_download_distfile_show_proxy_and_fail)
  scripts/cmake/vcpkg_acquire_msys.cmake:84 (vcpkg_download_distfile)
  scripts/cmake/vcpkg_acquire_msys.cmake:174 (z_vcpkg_acquire_msys_download_package)
  scripts/cmake/vcpkg_find_acquire_program.cmake:547 (vcpkg_acquire_msys)
  scripts/cmake/vcpkg_fixup_pkgconfig.cmake:198 (vcpkg_find_acquire_program)
  ports/openssl/install-pc-files.cmake:32 (vcpkg_fixup_pkgconfig)
  ports/openssl/portfile.cmake:21 (include)
  scripts/ports.cmake:142 (include)

Error: Building package openssl:x64-windows failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with `git pull` and `.\vcpkg update`.
Then check for known issues at:
  https://github.com/microsoft/vcpkg/issues?q=is%3Aissue+is%3Aopen+in%3Atitle+openssl
You can submit a new issue at:
  https://github.com/microsoft/vcpkg/issues/new?template=report-package-build-failure.md&title=[openssl]+Build+error
including:
  package: openssl[core]:x64-windows -> 1.1.1l#4
    vcpkg-tool version: 2021-11-24-48b94a6946b8a70abd21529218927fd478d02b6c
    vcpkg-scripts version: 5ddd7f026 2021-12-01 (7 months ago)

    vcpkg-tool version: 2021-11-24-48b94a6946b8a70abd21529218927fd478d02b6c
    vcpkg-scripts version: 5ddd7f026 2021-12-01 (7 months ago)

You must use a newer version of vcpkg. It has updated references for the MSYS2 build tools.

I can't use a newer version as that will update the ports as well

If you need particular versions of ports, you need manifest mode, with an up-to-date vcpkg.

Thanks for dg0yt's reply.
@Waffle1434 Did your issue resolved by manifest mode?

This is the documentation of manifest mode: https://github.com/microsoft/vcpkg/blob/master/docs/users/manifests.md

@Waffle1434 Does this issue resolved?

We hope your question was answered to your satisfaction; if it wasn't, you can reopen with more info.


Latest release will not launch app after install.

Hello Luis
I just replaced my install with the new .exe version, and the application will not start properly. I just get the timer circle swirling around and around, seemingly indefinitely.
Thanks
Andrew

Also, how do I uninstall it, and go back to a previous install? I don't see it in my list of apps to uninstall.
Thanks again
Andrew

This happens because current viewer was extracted in installation folder. Since you already have the latest viewer downloaded in %bling.exe%/Download/Versions it thinks it is updated but it is not. Thi new version extracts viewer in %bling.exe% so this never happens again.
To solve this, just remove anything inside download/versions and execute again.
Installation is done with another tool so it is not backwards compatible with the previous one. For uninstalling you may have to go to %localappdata%/Bling Desktop and execute uninstall. In future releases I will add shortcuts for windows.
Software upgrades is a bit of a mess right now but for next release I will try to make this as transparent as possible.

Hello Luis
That has resolved the issue, and allowed me to launch.
Thank you.
Andrew


MapOutline Issues After ArcPro 2.8 Update

MapOutLines tool started presenting errors after updating ArcPro for its latest version.
Below is the report after running the tool:
MapOutline
Parameters
SE longitude     -120.5
SE latitude     47.5
width (longitudinal extent)     0.04167
height (latitudinal extent)     0.04167
tic spacing     2.5
Is NAD27     true
output geodatabase     C:\Projects\Chiwaukum\Chiwaukum4SE.gdb
output coordinate system     PROJCS["NAD_1983_UTM_Zone_10N",GEOGCS["GCS_North_American_1983",DATUM["D_North_American_1983",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIMEM["Greenwich",0.0],UNIT["Degree",0.0174532925199433]],PROJECTION["Transverse_Mercator"],PARAMETER["False_Easting",500000.0],PARAMETER["False_Northing",0.0],PARAMETER["Central_Meridian",-123.0],PARAMETER["Scale_Factor",0.9996],PARAMETER["Latitude_Of_Origin",0.0],UNIT["Meter",1.0]]
scratch workspace     C:\Projects\Chiwaukum\New Folder
Messages
Start Time: Friday, August 13, 2021 12:09:55 PM
Failed script MapOutline...
Traceback (most recent call last):
File "C:\gems-tools-pro-2.4.8\Scripts\mapOutline_AGP2.py", line 20, in
checkVersion(versionString, rawurl, 'gems-tools-pro')
NameError: name 'checkVersion' is not defined
Failed to execute (MapOutline).
Failed at Friday, August 13, 2021 12:09:55 PM (Elapsed Time: 0.05 seconds)

Same issue running ArcGIS Pro (v 2.8.2) and GeMS Pro 2.5.1


Add your name!

Ready to make your first contribution? Goto the README.md file to learn how!

Can I take this up? Thanks.

@glaukiol1

Yes of course!

Im helping people getting their first contributions


gracefully handle footnoteReference and footnoteDefinition nodes in mdx field

currently, when an mdx document has a footnote, the keystatic mdx field errors with the following error message:
Field validation failed: content: Unexpected error: Error: Unhandled type footnoteReference Unhandled type footnoteDefinition

mdx document used:
---
title: test
---

Some text.[^1]

[^1]: Footnote content.

@stefanprobst How did you manage to fix this? How to use this code snippet exactly?

@adamlewkowicz i put together an example here: https://github.com/stefanprobst/keystatic-footnotes
in an .mdx file it will look like this:
This text has a footnote.<Footnote>This is the footnote text.</Footnote> This is the rest of the paragraph.

in the keystatic ui, it will look like this:

@stefanprobst Thanks a lot for the example! I've used this setup with remote-mdx and it's working 👍

I'm facing the same problem. A question on top of this problem:
Is there a way in Keystatic where one could could control the content of the markdoc/mdx content that would be written to the file, that goes beyond writing content components? I ask with the intention of being able to create first class prose mirror editor support for gfm footnotes, which astro's mdx integration for example, supports out of the box.
So if there was such a feature, doing
content: fields.mdx({
  label: 'Content',
  components: {
    Footnote: block({
      label: 'Footnote',
      schema: {
        inlineText: fields.text({
          label: 'Inline Text',
          validation: {
            isRequired: true,
          },
        }),
        footNoteText: fields.text({
          label: 'Footnote Text',
        }),
      },
    }),
  },
})

would give me the same control of clicking the Footnote prosemirror node ➡ opening a dialog to fill inlineText, footNoteText

but I'd be able to add them in remark gfm style instead of an inline React component.


[375] Removing degree prefix in degrees model

Context
The degrees model has unnecessary degrees_ prefixes in a couple of columns.

https://trello.com/c/zGqaCqZV/375-we-have-a-few-attributes-in-the-model-that-start-with-degree-could-the-prefix-be-removed-given-the-attribute-is-already-part-of

Changes proposed in this pull request
Migration to rename columns
Fix feature tests, params in controllers, controller tests and model validations
Guidance to review

 We have a few attributes in the model that start with degree_ , could the prefix be removed given the attribute is already part of the Degree model?


Link to blog post has no content

I got an DNS error from gm.zoomlab.it
I suggest use this url that works:
http://web.archive.org/web/20170227180224/http://gm.zoomlab.it/2015/template-engines-i-moved-from-love-to-meh-for-plates/

@SlavaAurim Thanks.
Yes I'm in the process of moving my old blog to my new domain. Will update the link when I'm done. Thanks!

Hi @gmazzap I see you removed the link from README altogether.
Plates has probably advanced in the last 3 years, maybe fixing up what made you write Foil. I was curious whether it still makes sense to spend energy on Foil, or perhaps a virtual "merge" upstream back to Plates is the more optimal idea. What are your current thoughts on this? I do see that Plates 4.0.0 is still "alpha" stage, which means they are probably struggling for resources and motivation, too.


suggestion to make a option to filter out log-in/log-out messages

Dear developers,
Being an iron-man on osrs it is annoying for other players if they continuously get a message when hopping servers.
Is it possible to filter out these messages so they do not display?
kind regards,
Jeroen

This is now an option in the vanilla settings menu.


Improve openvpn_config_parser

We can now validate both client and server configurations, and the block size padding is now configurable.

looks fine to me. thanks a lot.


Changing background ?

https://github.com/orickcorreia/caule-themes-pack-1/blob/d17270772d731e995a790c2ddaf63e443a959448/src/caule-themes-pack-1.yaml#L1024
I was wondering if this is refering some functionality to automatically change background if images are placed here?

Only if you use the same filename that is defined by the themes.


Rebrand to JsonPath4K and update dependencies

Nomen est Omen.
Release 2.2.0:

Rebranding to JsonPath4K

change Maven coordinates to at.asitplus:jsonpath4k
publish relocation POM for Version 2.0.0

Dependency Updates

Update to Kotlin 2.0.0
Update to Kotest 5.9.1
Update to kotlinx-serialization 1.7.1
Gradle 8.9

Since I don't know Jack about how this thing works internally, would you mind updating to the latest ANTLR-Kotlin version, while we're doing this?

repo will be renamed right after this PR it through


Add -i / --interactive flags

The -i / --interactive flags can be useful for preventing user errors. I use an abbreviation in fish so that rm and cp expand to rm -i and cp -i. So that I must first delete the flag in order to run a potentially dangerous operation.

Seems pretty reasonable. I think the way it would be implemented in this project is by showing you everything that is about to be deleted in one go instead of asking you successive questions. Otherwise you lose out on cross directory parallel deletions.

I'm not going to have the time to implement this (but I'm still open to somebody else sending a PR), so closing.
I'd recommend first using echo to check the files that will be operated on. Filed this for nushell: https://github.com/nushell/nushell/issues/11139


Vickel: Watch defra.ae

Vickel requests the watch of the watch_keyword defra\.ae. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

defra\.ae has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Jeff Schaller in Charcoal HQ


breaking changes in DryIoc.Microsoft.DependencyInjection 4.1.0

Today I upgraded DryIoc to the latest version - from 4.2.4 to 4.3.0 and the MS Dependency injection from 4.0.0 to 4.1.0. Next I knew, my code wouldn't compile as
DryIocAdapter.DryIocServiceProviderFactory
no longer seems to exist. What would be the replacement?

Fck, ok. I will return it back.

@ssteiner Ok, it seems a more messy situation...
I have moved DryIocServiceProviderFactory outside because of the rest of the types (e.g. DryIocServiceScopeFactory and DryIocServiceScope ) are also not nested and seemingly the  DryIocServiceProviderFactory was made nested by mistake.
The sample also relies on DryIocServiceScopeFactory to be not-nested.
Apparently som Users already adapted to this error (as expected) and are using the nested DryIocServiceScopeFactory.
So sorry, for confusion here - Let's keep the DryIocServiceScopeFactory outside to be at lease on the consistent side and to stop moving the target.
Please adjust your code accordingly.
Btw, I am not sure - should I release the current version as v5 and unlist the v4.1 from NuGet :(
Maybe will wait for other complaints.

If you strictly adhere to semantic versioning, I guess it needs to be v5.
I adapted my code and upgraded the 4.1.0 again :)

@ssteiner
DryIoc.Microsoft.DependencyInjection v5.0.0 is out.
https://github.com/dadhi/DryIoc/releases/tag/v4.5.0


working demo with tests for toMermaid()

The PR is here!
So I changed:

README has strings for example instead of integers on the enums
Extracted the Door class in the tests to make it re-useable
Saw there was a duplicate transition in the door class and removed it
Brought some dependencies up to more recent versions

Added:

StateMachine#toMermaid() method to output mermaid js code
Tests to cover the output of the Door class's toMermaid()
tools dir with a script to write-out the mermaid code of the Door class
package.json script to run the generator npm run diagram

I'm happy to change things if needed :)

This addresses #22

I apologize. My messy style of work in my own git repos is spilling. I didn't mean to touch so many things.
I will redo the whole PR :)

I was expecting only a new function and a test, but I've got a whole bunch of fixes.

I have never really worked on other peoples projects or on a team. I've always been a solo dev, so I have some bad habits.
Please don't look in my repos 😆


ValueError: bins should be a positive integer

#13570 Problem Description
Hello, I am using Python 3.7 via Spyder 3.3.6 (as part of the Anaconda suite) as part of a class I'm currently taking. (I'm new to Python, so I apologize in advance if the answer to resolving this error seems obvious.)
How do I move past this error?
What steps reproduce the problem?
import pandas
import numpy
import seaborn
import matplotlib.pyplot as plt
data = pandas.read_csv('classdata_pds.csv', low_memory=False)
sub2['PACKSPERMONTH']=sub2['NUMCIGMO_EST'] / 20
c12 = sub2.groupby('PACKSPERMONTH').size()
print(c12)
sub2['PACKCATEGORY']=pandas.cut(sub2.PACKSPERMONTH, 0, 5, 10, 20, 30, 147)
What is the expected output? What do you see instead?
Expect to see new bins for PACKSPERMONTH as defined above.
Instead receiving:  ValueError: bins should be a positive integer
Thank you!

Hi @MMS413 seems like your error isn't related with Spyder but rater with the code you are trying to run. Seeing your code I don't see where you are defining the sub2 variable neither you provide the whole traceback of the error.
However, seems like you are passing as the bins param  in the cut function the value 0 instead of a sequence of scalars (which maybe is what you are trying to do) like [0, 5, 10, 20, 30, 147]. For more info about the params that pandas.cut has, you can check the pandas docs: https://pandas.pydata.org/pandas-docs/stable/reference/api/pandas.cut.html
I will close this one since is not related with Spyder but hope the info above helps :)


Avoid thread locks

There have been reports of slow RPC and HTTP responses.
One issue, new messages have signatures and prev-hashes validated in the thread.
If there's a batch of new messages, they don't release the thread to the event loop until all sigs/hashes have been validated.
This PR has a test showing the issue (100 messages lock the thread for almost 2s on my laptop)
I'll add commits to release the thread after each validation, so that this issue can't occur.

Nope, this was wrong.
Turns out the validation pipeline is releasing the thread.
The delay I measured is from the multiple feed.add calls, which has to generate the prev hash and the message signature.
That's not an issue.
Learning is fun!
closing


0.0.6 beta2

Fix MemoryStream creation in ZipFileAnalyzer, ReadResult.Length --> ReadResult.Array.Length

Resolves #16


Duplicate records when use overwrite mode

I rarely faced that there are duplicate records when use overwrite by spark API (not sql).
Duplicate records are current incoming records with records in table before overwrite.
Expected behavior
A clear and concise description of what you expected to happen.
Environment Description

Hudi version : 0.9

Spark version : 3.0.1

Hive version : 3.1

Hadoop version : 3.2.2

Storage (HDFS/S3/GCS..) :

Running on Docker? no :

@njalan Have you used .mode("overwrite") ? Can you clarify your question please.

Yes I am using .mode("overwrite").
For example there are a,b,c.d in the existing table and  x,y,z are the new records.
After overwrite query return  a,b,c.d and x,y and z.

@njalan When I am testing with newer version i.e 0.12.3, 0.13.1, 0.14.0 , its working ok.
Can you test this in your setup.
val path="file:///tmp/test1"
val df = spark.sql("select 1 as uuid, 'test' as name, 1 as ts")
df.write.format("hudi").option("hoodie.table.name","test1").option("hoodie.datasource.write.recordkey.field","uuid").mode("overwrite").save(path)
spark.read.format("hudi").load(path).count()  // 1
val df2 = spark.sql("select 2 as uuid, 'test' as name, 1 as ts")
df.write.format("hudi").option("hoodie.table.name","test1").option("hoodie.datasource.write.recordkey.field","uuid").mode("overwrite").save(path)
spark.read.format("hudi").load(path).count() // 1

@ad1happy2go  It not happened every time and it just happened like once in two weeks.

@njalan Can you provide more insights on this when it happens. Can you reproduce this in a sample script?

@ad1happy2go  If I have one df with below 3 three records:
+---+----+
| id|name|
+---+----+
|  1|   a|
|  2|   a|
|  3|   c|
+---+----+
Then I run below command and there are 3 records in hudi table:
df.write.format("hudi").
options(getQuickstartWriteConfigs).
option(OPERATION.key(),"insert_overwrite_table").
option(PRECOMBINE_FIELD.key(), "id").
option(RECORDKEY_FIELD.key(), "name").
option(TBL_NAME.key(), tableName).
option(KEYGENERATOR_CLASS_OPT_KEY, "org.apache.hudi.keygen.NonpartitionedKeyGenerator").
mode(Append).
save(basePath)
Then I add option("hoodie.datasource.write.insert.drop.duplicates",true) to run again then there is no records in table :
df.write.format("hudi").
options(getQuickstartWriteConfigs).
option(OPERATION.key(),"insert_overwrite_table").
option(PRECOMBINE_FIELD.key(), "id").
option(RECORDKEY_FIELD.key(), "name").
option(TBL_NAME.key(), tableName).
option(KEYGENERATOR_CLASS_OPT_KEY, "org.apache.hudi.keygen.NonpartitionedKeyGenerator").
option("hoodie.datasource.write.insert.drop.duplicates",true).
mode(Append).
save(basePath)

You are right, We are seeing data loss when we tried that. Although I guess it's not related to the issue you were originally facing. Is that right?
Created JIRA to track - https://issues.apache.org/jira/browse/HUDI-7100
Reproducible code -
schema = StructType(
[
StructField("id", IntegerType(), True),
StructField("name", StringType(), True)
]
)
data = [
Row(1, "a"),
Row(2, "a"),
Row(3, "c"),
]
hudi_configs =
{ "hoodie.table.name": TABLE_NAME, "hoodie.datasource.write.recordkey.field": "name", "hoodie.datasource.write.precombine.field": "id", "hoodie.datasource.write.operation":"insert_overwrite_table", "hoodie.table.keygenerator.class": "org.apache.hudi.keygen.NonpartitionedKeyGenerator", }
df = spark.createDataFrame(spark.sparkContext.parallelize(data), schema)
df.write.format("org.apache.hudi").options(**hudi_configs).mode("append").save(PATH)
spark.read.format("hudi").load(PATH).show()

@ad1happy2go Yes it is not the originally facing. I am not able to reproduce it.

But curious to know why are we setting drop duplicates in this case? w/ INSERT_OVERWRITE operations, setting drop dups config does not make sense.


[IPC part 4] test cases for IPC strategies.

part 1: #1088
part 2: #1090
part 3: #1092

Add test cases that covers the 3 IPC strategies.

Also add enum 'Type' in BrokerCommunicationException.

Add test cases to cover BrokerOperationExecutor

Also change the thrown exception type of IIpcStrategy.communicateToBroker() from BaseException to BrokerCommunicationException (make it more specific).

exclude 'asm' module in org.robolectric:robolectric Issue only shows up in Android Studio 4.1, will figure it out later.

nimbus-jose-jwt is using asm 5.0.4, while Robolectric uses 7.0

The asm issue -  did that only happen for you locally or did that also happen on the pipeline (that was run as part of this PR)?

The asm issue - did that only happen for you locally or did that also happen on the pipeline (that was run as part of this PR)?

Local (otherwise we should've detected this in my previous PR already. I also ran that test with that commit locally and ran into the same issue).

Iteration 2:

Added IIpcStrategy.Type to IIpcStrategy

BrokerCommunicationException now takes this as an argument to identify what IIpcStrategy triggered the exception.

Extracted the implementation testXXXX() from IpcStrategyTest() to base class.

Operation supported by each strategy will eventually be branching out - so it doesn't make sense to have a shared implementation in one place.

Broker API will be added to ContentProvider only.
AccountManager updateCredential does not support MSAL operation.

force pushed to rebase the branch.


Best Practices in Testing

If there's no Best Practices content, why are we keeping this area in testing.md ? should we remove until someone send this data?

That's a good point @pragmaticivan.  @pjhampton any thoughts on whether we should come up with some content or remove this?  If either of you have suggestions for topics I can sit down and work on it.

@pragmaticivan @doomspork let's remove it for now and we'll come back to this later. I say this because we discussed adding Best Practices / FAQs at the end of each lesson.

That sounds good to me.  Do either of you want to tackle removing it across the languages?  Please use a PR.

@doomspork @pragmaticivan On it! :smile:

I think we can close this one? right @doomspork ?

Correct @pragmaticivan :+1:


Inclusive for...in range loop gives error in v2

for num in [0...10] Works
for num in [0..10] Error: Error: Parse error at [15:1]: Unexpected 'NUMBER' (/index.js:1)

Oh noes, I stupid... Should have put this under imba, not imba.io.


Using @Environment will crash in Preview

Description
Here is my code:
import SwiftUI
import Perception

@Perceptible
class HelloModel {
  var msg: String = "Hello, World"
}

struct HelloView: View {
  @Environment(HelloModel.self) var model

    var body: some View {
      WithPerceptionTracking {
        Text(model.msg)
      }
    }
}

#Preview {
    HelloView()
      .environment(HelloModel())
}

It crashes in preview:
== PAUSED REASON:

    processCrashed

== PREVIEW UPDATE ERROR:

    CrashReportError: Fatal Error in Environment.swift

    fito crashed due to fatalError in Environment.swift at line 54.

    No perceptible object of type HelloModel found. A View.environment(_:) for HelloModel may be missing as an ancestor of this view.

Checklist

[X] I have determined that this bug is not reproducible using Swift's observation tools. If the bug is reproducible using the @Observable macro or another tool from the Observation framework, please file it directly with Apple.
[X] If possible, I've reproduced the issue using the main branch of this package.
[X] This issue hasn't been addressed in an existing GitHub issue or discussion.

Expected behavior
No crash happened
Actual behavior
Crash happened
Steps to reproduce
Described in description
Perception version information
1.4.1
Destination operating system
iOS 16.0
Xcode version information
Version 16.1 (16B40)
Swift Compiler version information
No response

Using PreviewProvider is working:
struct HelloView_Previews: PreviewProvider {
    static var previews: some View {
      HelloView()
        .environment(HelloModel())
    }
}

Hi @zhuscat, since this works with preview provides I'm inclined to consider this an Apple bug. If someone finds a work around we will happily accept a PR, but this isn't something we personally have time to investigate.
Since this isn't an issue with the library I am going to convert it to a discussion. Please feel free to continue the conversation over there!


It crashes on sort.

If you click the header on the very left without any text, the Snooped application will crash.

I noticed that the sorting on the Value Source was broken due to a missing space. The case was 'ValueSource' instead of 'Value Source'. So, I fixed this before merging this pull request.


Creating a ratatosk mail/domain

For example Pinterest and a maximum coolnessfactor

Have we reached consensus on which domain to buy?

We have already collected some ideas, like i.e. rask.world but have not reached a conclusion yet. I suggest a price range of up to 20€ (could be more) which I would cover.

As I somehow get regular paychecks, I'd also contribute a bit of money, so we can enhance the monthly budget for that :D


Investigation on the archive process problem

Currently, there is few problem on the archive process.

Multi-compression process run next to each other.
The lambda timeout due to 15min limitation for a batch of +40min.

Estimation: 5

The multi-compression process was due to the retry of the lambda which was configured to more than one.
This was fix in the rolling-node MR.

The lambda timeout because of a problem with the nohup process.
A systemd service was the solution of this problem and avoid repetition if the lambda try to retry the archive process.


ImportError: cannot import name 'Iterable' from 'collections'

When using Python version 3.9 and later,
from causalgraphicalmodels import CausalGraphicalModel
results in
ImportError: cannot import name 'Iterable' from 'collections'
The following fix is described here:
try:
    # Python <= 3.9
    from collections import Iterable
except ImportError:
    # Python > 3.9
    from collections.abc import Iterable

I'm getting the same import error for Python 3.10
I tried to run from collections.abc import Iterable before from causalgraphicalmodels import CausalGraphicalModel but I still get the same error


[6.x] Fix phpredis "zadd" and "exists" on cluster

This PR fixes https://github.com/laravel/framework/issues/29637 and https://github.com/laravel/framework/issues/30473
By not using executeRaw, the cluster connection will call the correct redis command.

@themsaid
Removing exists() is a breaking change, because the parameters are now different. Previously passing multiple arguments was okay, but now only one argument can be passed.
My package's tests were passing and now they are failing because of that. See this: https://travis-ci.com/github/stancl/tenancy/builds/152720978#L2193
And this: https://github.com/stancl/tenancy/blob/2.x/src/StorageDrivers/RedisStorageDriver.php#L59-L61

@stancl but I can pass multiple keys no problem. Maybe you’re using a really old phpredis version?

@themsaid Hmm, possible. Seems like I'm using 3.1.6 in that build and the latest version is 5.2.0.
I guess I can find a way to update that, but I wonder if this would cause issues for others as well, since (for example) my code is a package.
But I see that you specified ^4.0 as phpredis version constraint, so I'll try with phpredis 4.


Implement reroute_to_grpc_interface for Ruby.

Resolves #430 for ruby.

Current coverage is 82.29% (diff: 100%)

Merging #450 into master will increase coverage by 0.07%

@@             master       #450   diff @@
==========================================
  Files           203        203
  Lines          7543       7570    +27
  Methods           0          0
  Messages          0          0
  Branches        999       1001     +2
==========================================
+ Hits           6202       6230    +28
+ Misses         1047       1046     -1
  Partials        294        294

Powered by Codecov. Last update 619640e...df4630d

cc: @garrettjonesgoogle.
A little bit of MVVM mixed in here.

It looks good, but I'd like to ask @garrettjonesgoogle for the further review.

@jmuk PTAL. I added the NodeJS fix to this since both the NodeJS and Ruby fixes follow the same mvvm pattern.

Hold off on reviewing this. Found a small bug.

Fixed. PTAL

I'm done with my first pass.

@jmuk PTAL. The changes we discussed about in node are up.

The generated files LGTM.

@jmuk thanks for taking a look!
@garrettjonesgoogle, I think this is ready for a second pass.

The rename suggestion is optional; the only remaining issue I think needs to be addressed is the comment I made on generateImports.

@garrettjonesgoogle This is ready for another pass.

LGTM


Issue with Unchanging Image in Web Development or Educational Diagram

Description:
The uploaded image, featuring a web development diagram with the MERN stack and additional tech domains like AI/ML, Cyber Security, and more, is not updating as expected. The issue might be related to browser caching, upload errors, or a platform glitch preventing the display of a newer version of the image.
ScreenShot:

@yatulearn label the issue

assigned


Update configuration-languages.md

Flag option changed? Or it was jurt a typo?

@salchichongallo Please sign CLA.

@salchichongallo Friendly ping

Original fork doesn't exist anymore.


systemd: Fix systemd-{cryptenroll,cryptsetup} TPM2 and FIDO2 support

Description of changes
With this change it is now possible to decrypt LUKs protected partitions with a FIDO2 or TPM2 token.
Reviving https://github.com/NixOS/nixpkgs/pull/171242
Things done

Built on platform(s)

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

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

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

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.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
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Is there anything that could be done to speed up merge of this PR? It's the only thing that keeps me from installing NixOS on my laptop, and I would be glad to help with anything

Is there anything that could be done to speed up merge of this PR? It's the only thing that keeps me from installing NixOS on my laptop, and I would be glad to help with anything

What needs to be done are:

Figure out the exact patches and changes needed
Make sure that they are actually secure
Create a NixOS VM test

I'll test out TPM2 and see how we can make those changes cleanly over the weekend.

I opened #189676 with the required changes and instructions to test.

Superseded by #189676


Create/use a base tsconfig file.

lgtm, happy to update the one in the scripts/ dir once this is in

Nw, tossed this in.


v0.17.1 release zip files missing locales and resources files

Expected behavior
The downloadable release zip files of 0.71.1 should contain the resources and locales files similar to what is in release 0.71.0.
Actual behavior
Folders  resources and locales in the 1.17.1 release zip file are empty
Information about the Issue
Kitematic.exe does not start when those folders are empty. I had to copy the folders from the 0.17.0 release in order to get 1.17.1 running on Windows 10.
Steps to reproduce the behavior

Download release v1.17.1
Unzip and try to run kitematic.exe and it will fail to start on Windows.

Yes, the folders are present, but empty. Are they supposed to be empty? Mine 0.17.1 would not run until I copied the contents of those two folders from 0.17.0 into 0.17.1.
Just to double check - I just downloaded https://github.com/docker/kitematic/releases/download/v0.17.1/Kitematic-0.17.1-Windows.zip on two different windows machines, with two totally different network and internet access points and both contain 0 bytes in the locales and resources folder.

Went ahead and updated the release Zip file to what I had:
https://github.com/docker/kitematic/releases/tag/v0.17.1
Let me know if the issue persists. Thanks for reporting this, feel free to re-open the issue if that doesn't fix the problem for you.


replace in-viewport mixin with ember-in-viewport

@twokul or @poteto you can review
closes #21

done

@fsmanuel thanks!

@twokul can you release a new version?

@fsmanuel done.


Add XCM DryRun Runtime API

Together with XcmPaymentApi this will help dApps estimate fees easily. This doesn't include the ED estimation yet.
https://github.com/paritytech/polkadot-sdk/pull/3872

To make it work with XcmPaymentApi 0.3.0 or 0.4.0 we would need first to upgrade to polkadot xcm 1.13 or 1.14 respectively.
The earlier versions of the runtime XcmPaymentApi don't contain the full functionalities...


Update Microsoft client tools Azure docs to include linux as supported platform

https://learn.microsoft.com/en-us/azure/storage/common/storage-explorers

PR has been opened, but still waiting for approval: https://github.com/MicrosoftDocs/azure-docs-pr/pull/270964

PR has been merged.


Configuring Ratify to trust a Certificate Authority + problems with Azure Key Vault

I want to enable the following scenario:

My company has a CA that generates certs

IMPORTANT: I don't run that CA, it's run by a separate "Infrastructure Team" or similar

I acquire a child cert for use with my CI pipeline to build & sign images
I want to configure Ratify to say "trust the company CA"

TLDR: This works fine until I need to reference that root/intermediate CA cert via Key Vault, because you can't have a KV cert that doesn't include the private key

Below is a walkthrough that shows what works + what doesn't as of today
Infra team: Create a Certificate Authority
To demonstrate the issue, we'll put on our Infra Team hat and stand up a simple local CA. Companies do this in a myriad of different ways, so we'll keep it straightforward for this demo
# https://github.com/notaryproject/notaryproject/blob/main/specs/signature-specification.md#certificate-requirements

# define extensions to create certs that comply with notation
cp /usr/lib/ssl/openssl.cnf openssl.cnf
cat <<EOF >> openssl.cnf
[ notation_ca ]
# Extensions for a typical CA
subjectKeyIdentifier=hash
authorityKeyIdentifier=keyid:always,issuer
basicConstraints = critical,CA:true
keyUsage = critical,cRLSign, keyCertSign

[ notation_cert ]
keyUsage = critical,digitalSignature
EOF

# create root CA key
openssl genpkey -algorithm RSA -out ca.key -pkeyopt rsa_keygen_bits:4096

# create root CA certificate
openssl req -x509 -new -nodes -key ca.key -sha256 -days 3650 -extensions 'notation_ca' -config openssl.cnf -out ca.crt -subj "/C=US/ST=WA/L=Redmond/O=My Company/OU=My Org/CN=ca.example.com"

Create a pipeline cert signing request
I interact with the infra team (web portal, service ticket, etc) to get a cert. Let's say in this case, I create a certificate signing request from Key Vault where the private key will stay and never be exported.
# IMPORTANT: cert chains *must* be stored in Key Vault in PEM format. PFX/PKCS12 is broken (notation-azure-kv enumerates certs in the wrong order)
# IMPORTANT: nonexportable private keys (ex: HSM) *must* use PEM format. PKCS12 support in Golang fails parsing when there is no private key. This will not be fixed.
POLICY=$(cat <<EOF
{
  "issuerParameters": {
    "certificateTransparency": null,
    "name": "Unknown"
  },
  "keyProperties": {
    "exportable": false
  },
  "secretProperties": {
    "contentType": "application/x-pem-file"
  },
  "x509CertificateProperties": {
    "ekus": [
      "<IP_ADDRESS>.<IP_ADDRESS>.3"
    ],
    "keyUsage": [
      "digitalSignature"
    ],
    "subject": "C=US, ST=WA, L=Redmond, O=My Company, OU=My Org, CN=pipeline.example.com",
    "validityInMonths": 12
  }
}
EOF
)

# create a certificate signing request via keyvault
# IMPORTANT: the response doesn't contain the necessary header/footer to the certificate signing request so we add it here
echo '-----BEGIN CERTIFICATE REQUEST-----' > pipelinecert.csr
az keyvault certificate create --vault-name noeltrash1 --name pipelinecert --policy "${POLICY}" --query csr -o tsv >> pipelinecert.csr
echo '-----END CERTIFICATE REQUEST-----' >> pipelinecert.csr

Infra Team: Complete the CSR
The infra team approves, and I get back a cert that's a child of my company CA root
# complete the certificate signing request using the local CA
openssl x509 -req -in pipelinecert.csr -CA ca.crt -CAkey ca.key -CAcreateserial -out pipelinecert.crt -days 365 -sha256 -extensions 'notation_cert' -extfile openssl.cnf

# append the CA cert to create a certificate bundle
cat ca.crt >> pipelinecert.crt

Upload the cert to Key Vault
I merge that cert into Key Vault, and now I can use it
# complete the signing request and push the cert to Key Vault
az keyvault certificate pending merge --vault-name noeltrash1 --name pipelinecert -f pipelinecert.crt

Sign an image using the leaf cert
I use it with notation to sign an image
# add the pipeline key
KEY_ID=$(az keyvault certificate show --vault-name noeltrash1 --name pipelinecert --query kid -o tsv)
notation key add pipelinecert --plugin azure-kv --id $KEY_ID

# notation login
export NOTATION_USERNAME=00000000-0000-0000-0000-000000000000
export NOTATION_PASSWORD=$(az acr login -n noelfdpo --expose-token --query accessToken -o tsv)

# sign an image
notation sign --key pipelinecert noelfdpo.azurecr.io/sample-plugin@sha256:f2c54ba629c4da68327efa4085e7e322964c6533f7c9bcfd8d69202950e20d7f

Verify the signature via notation
I validate the signature. Note that I'm using the CA root cert public key here (which I have access to), and not the leaf pipeline cert that directly created the signature.
# we trust the CA, not individual certs
notation cert add --type ca --store certs ca.crt

# verify the signature
notation verify noelfdpo.azurecr.io/sample-plugin@sha256:f2c54ba629c4da68327efa4085e7e322964c6533f7c9bcfd8d69202950e20d7f

Verify the signature via Ratify
Now, do the same thing with Ratify. I create a Ratify config with a simple trust policy that uses notation's trust store path (just saves me copying some files around)
{
  "executor": {},
  "store": {
    "version": "1.0.0",
    "plugins": [
      {
        "name": "oras"
      }
    ]
  },
  "policy": {
    "version": "1.0.0",
    "plugin": {
      "name": "configPolicy",
      "artifactVerificationPolicies": {
        "application/vnd.cncf.notary.signature": "any"
      }
    }
  },
  "verifier": {
    "version": "1.0.0",
    "plugins": [
      {
        "name": "notaryv2",
        "artifactTypes": "application/vnd.cncf.notary.signature",
        "verificationCerts": [
          "/home/vscode/.config/notation/truststore"
        ],
        "trustPolicyDoc": {
          "version": "1.0",
          "trustPolicies": [
            {
              "name": "default",
              "registryScopes": [
                "*"
              ],
              "signatureVerification": {
                "level": "strict"
              },
              "trustStores": [
                "ca:certs"
              ],
              "trustedIdentities": [
                "*"
              ]
            }
          ]
        }
      }
    ]
  }
}

Verify the image
ratify verify -s noelfdpo.azurecr.io/sample-plugin@sha256:f2c54ba629c4da68327efa4085e7e322964c6533f7c9bcfd8d69202950e20d7f

So far, so good!
At this point, we've seen that

notation can sign with a leaf cert
notation can verify a signature using only the CA public key
ratify can verify a signature using only the CA public key

Azure Key Vault behavior
Azure Key Vault certificates must include the private key. Here are some commands that will fail:
az keyvault certificate import --vault-name noeltrash1 --name myca --file ca.crt
# error: Private key is not specified in the specified X.509 PEM certificate content. Please specify private key in the X.509 PEM certificate content.

az keyvault key import --vault-name noeltrash1 --name myca --pem-file ca.crt
# error: Import failed: Could not deserialize key data. The data may be in an incorrect format or it may be encrypted with an unsupported algorithm.

So I can refer to a CA file, but can't refer to a CA cert in Key Vault (unless I have & am willing to upload its private key)
What's next?
So in this scenario, I can't store this CA cert in Key Vault. And in the above, we've shown that I don't actually need it. What I really need is to get the public key into my trust store. But that flow doesn't play nicely with Ratify + k8s as of today.
Q: Do we expect companies/users to be using cert chains in their software supply chain security?
I don't have a specific customer in mind right away, but I would assume the answer is "yes"?
Q: What's the "happy path" for pointing to a public key?
I can modify the Helm chart and pass in the root CA cert as a ConfigMap/Secrets, and then volume mount those files on disk. I fully expect folks on Azure to ask "Why can't I use the Key Vault feature?", and walk them through this journey as well.
Other thoughts
Doing something like expanding ratifyTestCert in Helm values into an array with one entry per public key, and then wiring everything up in the chart, would give this category of users a "better" experience. This would effectively mean that customers that have well-governed CA's (note: I personally think this pattern is reasonable and common) wouldn't use the Key Vault feature at all
We could say: don't tell Ratify to trust the root CA, but instead an intermediate CA. We do put that private key in Key Vault. This would work at a technical level (important note: even though it's not needed by notation), but asking someone to maintain a complicated CA chain just to use Ratify + Key Vault is, for me personally, unreasonable to ask someone to do.

thanks you so much for writing this up , we really appreciate this all the context and thought here @noelbundick-msft! @toddysm , do you have additional insights to customer workflow , or any other possible workaround?

@susanshi Looking at the CertificateStore CRD, it seems like a good option in the future might be to implement a new spec.provider option named "inline" or similar, and enable me to do something like:
apiVersion: config.ratify.deislabs.io/v1alpha1
kind: CertificateStore
metadata:
  name: my-ca-root
spec:
  # this would tell Ratify to load directly from inline values rather than calling out to an external key store
  provider: inline
  parameters:
    # this would be only the public cert (chain) in PEM format
    certificate: |
      -----BEGIN CERTIFICATE-----
      MIIFxzCCA6+gAwIBAgIUBU8GfzuQwEbUNllUTvApn20BC2swDQYJKoZIhvcNAQEL
      BQAwazELMAkGA1UEBhMCVVMxCzAJBgNVBAgMAldBMRAwDgYDVQQHDAdSZWRtb25k
      MRMwEQYDVQQKDApNeSBDb21wYW55MQ8wDQYDVQQLDAZNeSBPcmcxFzAVBgNVBAMM
      DmNhLmV4YW1wbGUuY29tMB4XDTIzMDEyNzE5MTIzM1oXDTMzMDEyNDE5MTIzM1ow
      azELMAkGA1UEBhMCVVMxCzAJBgNVBAgMAldBMRAwDgYDVQQHDAdSZWRtb25kMRMw
      EQYDVQQKDApNeSBDb21wYW55MQ8wDQYDVQQLDAZNeSBPcmcxFzAVBgNVBAMMDmNh
      LmV4YW1wbGUuY29tMIICIjANBgkqhkiG9w0BAQEFAAOCAg8AMIICCgKCAgEAuHbv
      6GuyvA8Cza0wXJQfzYo90uh1rTRuSrBL6cGdvFMdZgy2UyxL8vmQs7qHHIJupbKw
      EjURPn0rmPrIHFBmmyK7kjojOQma+AjOHJowcXZy619Qar2wTkopk6+ubtwjx8PZ
      t0LdHSRK0dUrcZDINqrjWBv8KknsgVkyP9PdNsnHH58hu8Po2kZEp+V6Yj+hWJ00
      GgKdPgrE1LVReA6fzFR/RvS8XuAeWiP06EkuyLCeq9qCmo7Idm2pNRJ10B/Nbmb1
      3O9wC90ESw0CT8cBjFYt2PogjWDWJgj15BA0xDpYA7RVrZRkFQQb2JZAD76o+ruZ
      SOb6CiYHLFVE26gIT5me+OMsJYM0HIS4KHudcc4j853cw4g13nCm4CtgGKnDoUV6
      iDhvoix26NMfDuVC8MHr3AlVuXjg9ZHB9Qo4VCmcsPIP9W0SYsOc+Fp0SpzDprOb
      XVU1uTuztbCegHD34ZMWG9lCXQSgKm99IaF3K+K/Gd/s1j6cXajgRkGvheLbDIPr
      W10MA2/rJU5SB/YyO4/G6d9OOtuwdGZOCPVVF/SVkbMTs0UGF4cj3upCTLP2IuUN
      RFVp+Ug37ixNU5jLtqHuqEX+VeKzjTMGQccbdQ4O65jdefnj8NYGu5QQfGBuCdBG
      ZSTGj9BOgTki7619ek/yVFiffeioM7prwknQJB0CAwEAAaNjMGEwHQYDVR0OBBYE
      FBSoEha9qupyX8Rtf9v4Cc4YeIE2MB8GA1UdIwQYMBaAFBSoEha9qupyX8Rtf9v4
      Cc4YeIE2MA8GA1UdEwEB/wQFMAMBAf8wDgYDVR0PAQH/BAQDAgEGMA0GCSqGSIb3
      DQEBCwUAA4ICAQChgydMDDTrxjzEBy5zxq5hJq88aiLG5cxl9a8xfPQTS7AU6dYd
      90X8r9EOwi5ZMgfqkqNsu7g7SUpXE8BN6uoVcC0lIyVfeOK3lIv3a8XUy8os5Atf
      RyPdacCs60KYlKozO0+E+CAh0XgCWv2TXA6HKmR/XCj/p2NjIgPFEdDKfaZHkBgi
      AB/UuocxSRjkHzu/rPQkyFuaF09nHgj/6OJ0YFMd3LXVmm+zkuC/Wpdhluyk7Hys
      +CP5i0jIjR4OG83+Zbi4ikMyBrIcOWMN6sVSaJx8ACqA91zICcy5+DUOPuLCip7w
      elmRSdEFZmJysARKYV1Yy20dl+5nN3sLgj42j40PnCCnqMUhxKPi1mUr1DJgv4vk
      JLFx7N3s9zLu3fmtSRRGsnQEH991hezyaR84osIu3QArNsi+SO80Lc9p95jvJKT6
      MNY7Xo52rlzZV6Hl3uX00mTqheWPBOETBrS0RZ0wnRSsR59+rIjRm/trR4+hRl8z
      JsIx0X5jr7Bf+KRAnKveQwck0J1A6tPmgpDkd/G17nbNLKmA5CYy0E6ZqTHl1p/r
      027OjBAHnQMcP9Zr2cv4vC8EWOjmtDGSIJi2WYhRaIqCI5MDahGYS+aLrfXPaHCu
      0IMA3zXuwyaStKnYUxRomApvhjcWvrpAD1f/QxvkixYk4to7p6USOACkKQ==
      -----END CERTIFICATE-----

And then have the CertificateStoreReconciler add/remove that from the in-memory map like it does with the "azurekeyvault" provider.
I think we'll encounter more of these cases. Ex: I anticipate wanting to verify that I'm running properly signed images from mcr.microsoft.com, but I certainly won't have access to the private keys. This would give me a consistent way to specify my public certs without having to resort to Helm postrender ConfigMap/Secret volume mount hacks


update math expert

Features

xx
yy

Feature Docs

Influence

Result

Other

Codecov Report
Attention: Patch coverage is 0% with 199 lines in your changes are missing coverage. Please review.

Project coverage is 79.92%. Comparing base (bcf5f05) to head (01996fb).
Report is 16 commits behind head on code_interpreter.

Files
Patch %
Lines

metagpt/roles/mi/math_expert.py
0.00%
87 Missing :warning:

metagpt/actions/mi/code_reflection.py
0.00%
34 Missing :warning:

metagpt/strategy/math_planner.py
0.00%
34 Missing :warning:

metagpt/actions/mi/code_self_verification.py
0.00%
18 Missing :warning:

metagpt/actions/mi/math_write_code.py
0.00%
15 Missing :warning:

metagpt/actions/mi/math_output_answer.py
0.00%
11 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@                 Coverage Diff                  @@
##           code_interpreter     #947      +/-   ##
====================================================
- Coverage             81.19%   79.92%   -1.28%
====================================================
  Files                   226      232       +6
  Lines                 12478    12678     +200
====================================================
+ Hits                  10132    10133       +1
- Misses                 2346     2545     +199

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

@garylin2099


A player that is guessing should be able to see the username of the player that is creating an image

commit #e8c85ce


Add integration test support to travis.ci

This allows travis to run full integration tests with a working containerd.

Codecov Report

Merging #910 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #910   +/-   ##
=======================================
  Coverage   59.55%   59.55%
=======================================
  Files           5        5
  Lines         759      759
=======================================
  Hits          452      452
  Misses        199      199
  Partials      108      108

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 26183b3...bbb874a. Read the comment docs.

Update with checks of the health service to see if its running within 2seconds

LGTM

LGTM

LGTM


Add // <auto-generated/> to generated source

Is your feature request related to a problem? Please describe.
Generated source can report warnings due to a lack of an // <auto-generated/> comment at the top of the file.
Describe the solution you'd like
Add the comment to mark the source as auto-generated thus preventing warnings from appearing from generated code.

Mapperly uses the .g.cs filename suffix which should mark the file as auto generated. Did you experience an IDE reporting warnings for the Mapperly generated code?

I do have some warnings showing up in JetBrains Rider:
Riok.Mapperly/Riok.Mapperly.MapperGenerator/Mapper.g.cs(493,76): warning CS8714: The type 'string?' cannot be used as type parameter 'TKey' in the generic type or method 'Dictionary<TKey, TValue>'. Nullability of type argument 'string?' doesn't match 'notnull' constraint.

I see the // <auto-generated /> comment added from other source generators (including Microsoft's RazorSourceGenerator) -- is there is a reason not to add the comment?

I thought adding .g.cs as suffix should have the same effect as the // <auto-generated /> comment. But as the MS docs also use both, Mapperly should probably use both too.
Feel free to open a PR 😉
Implementation hints: Add a Comment() leading trivia in Riok.Mapperly.Emit.SourceEmitter.Build.


Instance is not availible after pc lock / sleep.

Instance is not availible after any pc lock / sleep. Reconnect button just close app.
Closing app and run from shortcut fixes it but i do it 10-20 times in a day.
Phone apps works fine.

Default setting with password login. HA has HACS and vscode extension.

I have the same issue, screen become white and I need to restart application, then it works sometimes all day or a few hours...

Having this issue too

same issue, I think that it should try to reconnect automatically (feature), and a fix for the reconnect button that's silently crashing the app (bug).

I have this issue as well on Windows 11 and Linux (NixOS). Every time I lock my system, I have to click restart. The reconnect button does not work.

I have the same issue. Windows 11

same on Win 10

Same issue on Windows 11, otherwise great application, thank you!


[Overload] Active requests resource monitor

As part of https://github.com/envoyproxy/envoy/issues/12419, I would like to introduce resource monitor for global count of active requests in overload manager.
The rationale is described in https://github.com/envoyproxy/envoy/issues/12419.
Active requests accounting logic lives in codec clients, so overload manager dependency will be propagated at this level.
This will be a proactive resource monitor (similar to active downstream connections monitor), which means resource pressure will be checked inline instead of being evaluated periodically in overload manager.
When threshold is saturated Envoy will enter overloaded state and invoke a fixed overload action, it will stop accepting new requests. Upon completion of an active request, resource usage for global counter will be decremented in overload manager, which in turn will let in new subsequent request.
Tagging  @KBaichoo @alyssawilk @yanavlasov here to validate high level design proposal.

SGTM

/assign


AWAKE Protocol: PIN validation step changes to allow choosing a device to link with

This tracks an idea for improving the UX of linking with a device in case there's multiple devices in a single websocket room at the same time.
At the moment, we're only keeping track of "one AWAKE protocol at a time" that we're running. So the provider will start trying to connect to the first requestor they heard about. At step 5 the provider will show the PIN they sent the requestor to make sure the user connects to the device they think they're connecting to.
If there are multiple devices in the same room at the same time, this might be the wrong room, and the user will wait for their other device to show a number indefinitely.
What we can do instead is keep track of all (or capped at 10/100) AWAKE protocols running with different DIDs in parallel. Once we get to step 5 in any of the protocol states, instead of showing the PIN on the provider side, we show an input field asking to enter the code the user sees on the other device.
Because the provider keeps a record of which codes it sent to which DIDs, it then knows which DID to send the delegated credentials to.

This does not describe spec changes. (Maybe someone misread "PIN validation step changes" for "spec changes"?)

Agreed, the whitepaper looks like it holds for these changes. Multiple devices does seem like an implementation detail. Same with the method by which the user confirms the pin (displayed to the user vs user enters pin).


Remove RummagerNotifier

We are turning on indexing of mainstream browse pages,
topics and organisations from notifications sent by publishing-api.
collections-publisher no longer needs to send these notifications itself.
Since the only tags collections-publisher handles are mainstream browse pages,
topics and archived topics, we can simply eliminate all notifications to Rummager.

We are turning on indexing of mainstream browse pages,
can you provide a link to a ticket/PR ?

Sorry, the ticket was unclear, added a comment here: https://trello.com/c/LbZA0i15


fix: pin axios to 0.18.x

Axios 0.19 contains a bug in which custom request parameters are not actually applied to the request.

Shouldn't the yarn.lock file also be updated?

@Cauldrath - good catch. Fixed.


Can't seem to get it to work in 1.21.0

Hi, thanks for maintaining this awesome mod!
I have used it successfully in the past (i.e. several Beat Saber versions ago). However, I can't get it to work on a new installation of 1.21.0. The settings work correctly, I can see the menu where you can select the different available JSON files and could verify that it indeed loads these JSON files (by breaking my JSON config deliberately to see if it shows an error, which it did). Afterwards, I loaded a JSON config that should work (without any error showing up).
However, the score numbers still are the plain Beat Saber score numbers.
How would I go forward to debug this? I have profound knowledge about C# and Visual Studio available, but did no Beat Saber modding so far, so I would be glad about some pointers on where to look.

Mind attaching your HSV config file so I can debug it myself?
I use Jetbrains Rider myself so don't really know how to properly debug using VS either, so is kinda hard to give you pointers on that. 😅

Hey, thanks for the fast response. I only got around to try it out once more today. It doesn't seem to be an issue with that specific HSV config, as it doesn't work for the default one nor for one from 115 Guild either. I uploaded them here, but I don't think they will not work for you.

Default
Mine
From 115 Guild

As I said, I can switch around these config files successfully ingame in the menu, but they have no effect on the numbers being shown. Are there known incompatibilities with other mods maybe?
My Beat Saber log only shows the mod being loaded. Does it maybe print something in the log when its hooks have been called successfully that is missing in my log?
Thanks for your help!

since this issue pertains to a very old version of the game, i'm declaring it stale and it will be closed now.


Update intersphinx list for track 2 dependencies

Need to add the base url where we would download teh objects.inv.
Example from @lmazuel
Add aiohttp https://aiohttp.readthedocs.io/en/stable/objects.inv  so that we can have a nice formatted link to the ref docs for that one.
This is not all generated packages, just dependencies that we require.

@scbedd, I think this is docs related, but I'm not 100% sure based on the title and description.  I put it in the github.io vNext epic.  If I got this wrong, let's find a better place for it.


Proof of concept of using client-side script in astro

This PR is for demo purpose, will close after @YayunHuang read it.

@pkong-ds seems approach 2 won't work too, I tried to put the pages to src/components and import the component in src/pages/xxxx.astro before and got same error document is not define, so let's use approach 1, thanks a lot! :adore2x: :adore2x:

As per offline discussion, will use approach 1.
Lemme close this


[Feature]: Adding a top button

Describe the feature
To add a "Back to Top" button on a website that smoothly scrolls the user back to the top of the page when clicked
Add ScreenShots

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

assign me


Don't crop Hero image to 9 colums

The theme assumes a 3 column sidebar. Crop to 12 columns when there isn't a sidebar.


Wrapper Improvements

Fixed deprecation warnings for step() and reset() in wrappers that extend the core wrapper. See: https://github.com/openai/gym/blob/master/gym/core.py#L223 for the source of the deprecation warnings
Fixed State & Action Bonus wrappers. They were broken due to:

Incorrect/outdated reference to agentPos and agentDir, which don't exist
The agent pos can be a numpy array and could not be stored in this format, converted it to tuple

Ensured that the previous env (wrapped or unwrapped) values get passed to the current wrapper using the same method as other wrappers
Modified FullyObsWrapper and AgentViewWrapper to utilise self.unwrapped as they didn't work well with wrapped environments, e.g. FullyObsWrapper had an identical grid for each timestep (as the agent_pos it referred to was not changing)

Thanks for taking the time to fix these problems @abdel!
I think I will take the time to add some basic automated tests for wrappers. It's problematic that these issues went undetected this long.

I am still having the issue of agent_pos not being updated. I am using a custom wrapper.
class RGBImgObsWrapper(gym.core.ObservationWrapper):
"""
Use the image as the only observation output, no language/mission.
use rgb values.
"""
def __init__(self, env):
    self.__dict__.update(vars(env))  # Pass values to super wrapper
    super().__init__(env)

    self.observation_space = spaces.Box(
        low=0,
        high=255,
        shape=(self.env.width*32, self.env.height*32, 3),  # number of cells
        dtype='uint8'
    )

def observation(self, obs):
    return copy.deepcopy(self.env).render(mode = 'rgb_array', highlight = False)

@idigitopia you'd need some magic Python trickery to lookup those variables on the environment being wrapped instead of the wrapper itself. Otherwise, doing env.unwrapped.agent_pos will give you what you want, I believe. If not, please open an issue and paste some code so we can see your specific use case.

yes i am currently using env.env.agent_pos. but seemed like a hack and the
code will not work if and unwrapped env is passed.
will the unwrapped be a better way to do it in this case ?
On Fri, May 3, 2019 at 10:09 AM Maxime Chevalier-Boisvert <
<EMAIL_ADDRESS>wrote:

@idigitopia https://github.com/idigitopia you'd need some magic Python
trickery to lookup those variables on the environment being wrapped instead
of the wrapper itself. Otherwise, doing env.unwrapped.agent_pos will give
you what you want, I believe. If not, please open an issue and paste some
code so we can see your specific use case.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/maximecb/gym-minigrid/pull/55#issuecomment-489169973,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKI2GRB7634UPHKLQDZJG63PTRWV5ANCNFSM4HAZA4UQ
.

--
Aayam K. Shrestha
Graduate Teaching Assistant
School of Electrical Engineering and Computer Science
Oregon State University
Room 3040, Kelley Engineering Center

Yes, env.unwrapped.agent_pos should work even for an unwrapped env.
On Fri, 3 May 2019 at 13:22, idigitopia<EMAIL_ADDRESS>wrote:

yes i am currently using env.env.agent_pos. but seemed like a hack and the
code will not work if and unwrapped env is passed.
will the unwrapped be a better way to do it in this case ?
On Fri, May 3, 2019 at 10:09 AM Maxime Chevalier-Boisvert <
<EMAIL_ADDRESS>wrote:

@idigitopia https://github.com/idigitopia you'd need some magic Python
trickery to lookup those variables on the environment being wrapped
instead
of the wrapper itself. Otherwise, doing env.unwrapped.agent_pos will give
you what you want, I believe. If not, please open an issue and paste some
code so we can see your specific use case.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<https://github.com/maximecb/gym-minigrid/pull/55#issuecomment-489169973
,
or mute the thread
<
https://github.com/notifications/unsubscribe-auth/AKI2GRB7634UPHKLQDZJG63PTRWV5ANCNFSM4HAZA4UQ
.

--
Aayam K. Shrestha
Graduate Teaching Assistant
School of Electrical Engineering and Computer Science
Oregon State University
Room 3040, Kelley Engineering Center
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/maximecb/gym-minigrid/pull/55#issuecomment-489173800,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAFOIJVFGMX6KRPGJRX3X43PTRYFDANCNFSM4HAZA4UQ
.

Thank you so much for the prompt response. I really appreciate it.
I guess the current version does not have an RGB-image obs wrapper. Is
there a better way to do this without the wrapper?
On Fri, May 3, 2019 at 10:25 AM Maxime Chevalier-Boisvert <
<EMAIL_ADDRESS>wrote:

Yes, env.unwrapped.agent_pos should work even for an unwrapped env.
On Fri, 3 May 2019 at 13:22, idigitopia<EMAIL_ADDRESS>wrote:

yes i am currently using env.env.agent_pos. but seemed like a hack and
the
code will not work if and unwrapped env is passed.
will the unwrapped be a better way to do it in this case ?
On Fri, May 3, 2019 at 10:09 AM Maxime Chevalier-Boisvert <
<EMAIL_ADDRESS>wrote:

@idigitopia https://github.com/idigitopia you'd need some magic
Python
trickery to lookup those variables on the environment being wrapped
instead
of the wrapper itself. Otherwise, doing env.unwrapped.agent_pos will
give
you what you want, I believe. If not, please open an issue and paste
some
code so we can see your specific use case.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<
https://github.com/maximecb/gym-minigrid/pull/55#issuecomment-489169973
,
or mute the thread
<

https://github.com/notifications/unsubscribe-auth/AKI2GRB7634UPHKLQDZJG63PTRWV5ANCNFSM4HAZA4UQ

.

--
Aayam K. Shrestha
Graduate Teaching Assistant
School of Electrical Engineering and Computer Science
Oregon State University
Room 3040, Kelley Engineering Center
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<https://github.com/maximecb/gym-minigrid/pull/55#issuecomment-489173800
,
or mute the thread
<
https://github.com/notifications/unsubscribe-auth/AAFOIJVFGMX6KRPGJRX3X43PTRYFDANCNFSM4HAZA4UQ
.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/maximecb/gym-minigrid/pull/55#issuecomment-489174747,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKI2GRFNYMO2A6KSEABX3OTPTRYPTANCNFSM4HAZA4UQ
.

--
Aayam K. Shrestha
Graduate Teaching Assistant
School of Electrical Engineering and Computer Science
Oregon State University
Room 3040, Kelley Engineering Center

I think a wrapper is a good solution.
On Fri, 3 May 2019 at 15:02, idigitopia<EMAIL_ADDRESS>wrote:

Thank you so much for the prompt response. I really appreciate it.
I guess the current version does not have an RGB-image obs wrapper. Is
there a better way to do this without the wrapper?
On Fri, May 3, 2019 at 10:25 AM Maxime Chevalier-Boisvert <
<EMAIL_ADDRESS>wrote:

Yes, env.unwrapped.agent_pos should work even for an unwrapped env.
On Fri, 3 May 2019 at 13:22, idigitopia<EMAIL_ADDRESS>wrote:

yes i am currently using env.env.agent_pos. but seemed like a hack and
the
code will not work if and unwrapped env is passed.
will the unwrapped be a better way to do it in this case ?
On Fri, May 3, 2019 at 10:09 AM Maxime Chevalier-Boisvert <
<EMAIL_ADDRESS>wrote:

@idigitopia https://github.com/idigitopia you'd need some magic
Python
trickery to lookup those variables on the environment being wrapped
instead
of the wrapper itself. Otherwise, doing env.unwrapped.agent_pos will
give
you what you want, I believe. If not, please open an issue and paste
some
code so we can see your specific use case.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<
https://github.com/maximecb/gym-minigrid/pull/55#issuecomment-489169973
,
or mute the thread
<

https://github.com/notifications/unsubscribe-auth/AKI2GRB7634UPHKLQDZJG63PTRWV5ANCNFSM4HAZA4UQ

.

--
Aayam K. Shrestha
Graduate Teaching Assistant
School of Electrical Engineering and Computer Science
Oregon State University
Room 3040, Kelley Engineering Center
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<
https://github.com/maximecb/gym-minigrid/pull/55#issuecomment-489173800
,
or mute the thread
<

https://github.com/notifications/unsubscribe-auth/AAFOIJVFGMX6KRPGJRX3X43PTRYFDANCNFSM4HAZA4UQ

.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<https://github.com/maximecb/gym-minigrid/pull/55#issuecomment-489174747
,
or mute the thread
<
https://github.com/notifications/unsubscribe-auth/AKI2GRFNYMO2A6KSEABX3OTPTRYPTANCNFSM4HAZA4UQ
.

--
Aayam K. Shrestha
Graduate Teaching Assistant
School of Electrical Engineering and Computer Science
Oregon State University
Room 3040, Kelley Engineering Center
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/maximecb/gym-minigrid/pull/55#issuecomment-489205286,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAFOIJX5O7PXTPGJTT2NYZLPTSD2ZANCNFSM4HAZA4UQ
.


Token indices sequence length is longer than the specified maximum sequence length

Hi,  thank you for your excellent work. I meet a problem and really need your help:
When I conducted the  step 1: Generation by running the following code:
accelerate launch --main_process_port=2950 spin/generate.py --input_dir /SPIN_iter0 --batch_size 8 --frac_len 800 --data_frac 2 --output_dir /generated/iter1
It returns a warning:

Token indices sequence length is longer than the specified maximum sequence length for this model (2392 > 2048). Running this sequence through the model will result in indexing errors.

I am wondering whether this will affect the following training step? Is there any way to address this issue? Or can I just ignore it?
Thanks in advance!

Hi, thank you for your interest! The warning will not affect the training step and can be ignored.


use $uibtooltipprovider.option in pop over template

The issues forum is NOT for support requests. It is for bugs and feature requests only.
Please read https://github.com/angular-ui/bootstrap/blob/master/CONTRIBUTING.md and search
existing issues (both open and closed) prior to opening any new issue and ensure you follow the instructions therein.
Bug description:
Link to minimally-working plunker that reproduces the issue:
Version of Angular, UIBS, and Bootstrap
Angular:
UIBS:
Bootstrap:

Closing due to no actionable/respondable content


Summon should include Create Undead

I may just be implementing it incorrectly to tie it to the Pathfinder 2E Spell Create Undead, as I have a necromancer in one of my groups and this implementation would make using these types of spells a lot more streamlined.

I will try to make the Macro myself, just odd that I am not getting the summon options using Create Undead

I did figure out how to configure the trait filter since only one creature has Undead in the name, which is a good work around for now, interesting the Create Undead PF2E Animations macro is not working for Create Undead

I just realized that you were talking about the ritual "Create Dead", not the spell "Animate Dead".
Yes, Create Dead has not been automated in PF2e Animations. You can just copy over the Animate Dead settings in Automated Animations.


Add opts.autoclose in test.createStream() #465

Tries to solve #465

Problem
The stream created inside results was being closed only when the process was exiting. Changed the API to introduce opts.autoclose that is provisioned over canEmitExit so that results get closed when the results are done. In normal usage(from command line) harness closes on process end.
autoclose is required beacause throughs queue method is storing the results untill the end where it is ended only when harness is closed.
Normal usage
const tapSpec = require('tap-spec');
const {add, divide} = require('../index.js');
const test = require('./tape/index.js');

// piping programatically
test.createStream()
  .pipe(tapSpec())
  .pipe(process.stdout);

test('should add', t => {
  t.equal(add(3, 4), 7);
  t.end();
});

test('should divide', t => {
  t.equal(divide(8, 2), 4);
  t.end();
});

we get the output:
> node test/test.js

  should add

    √ should be equal

  should divide

    √ should be equal

opts.autoclose set to true
test.createStream({
  autoclose: true,
})
  .pipe(tapSpec())
  .pipe(process.stdout);

we get
> node test/test.js

  should add

    √ should be equal

  should divide

    √ should be equal

  total:     2
  passing:   2
  duration:  43ms

/pinging @ljharb @substack

Closing per https://github.com/substack/tape/pull/466#discussion_r283122484, but happy to reopen if there's still a need!


Param almost works on pypy

I have heard from a reliable source that param (maybe not numbergen) almost works on pypy. :-)
The only thing that needs to be changed is how we register numpy RandomState with script_repr. The official numpy version that is currently available for pypy lacks RandomState so instead of an ImportError you get an AttributeError.
One fix is to change except ImportError: to simply except: without trying to catch any particular exception. Although not completely ideal, this might be worth considering if anyone wants to use param with pypy.

We're getting more and more interested in pypy, so this might be of use for me.  Thanks for filing the ticket so that I could see that this is out there.

Looks like the import of numpy has been changed to have an empty except: already as of 6334350

Based on my original notes, that suggests param should be working with pypy. @timsnyder Could you confirm? If not I'll set up pypy and try it myself...

pypy is already in the travis test matrix: https://travis-ci.org/ioam/param/jobs/226012979

I forgot that was added! Looks like this issue can be closed.

Though perhaps RandomState is still an issue and is simply not tested. So we might need to look out for that...


Pass environment variables to child process

Currently when you pass an environment variable to istanbul cover, it doesn't get to the covered file.

$ cat test.js
console.log(process.env.FOO)
$ istanbul cover test.js
undefined
[...]

False positive. I forgot to pass the variable..


fix(select): Propagate value in formControl

WIP

[ ] Update documentation
[ ] Update unit tests
[ ] Include breaking change note

Closes #411

PR #419 will need to be merged before this PR.

Closing PR and re-opening


gtree: 1.7.50 -> 1.7.51

Diff: https://github.com/ddddddO/gtree/compare/v1.7.50...v1.7.51
Changelog: https://github.com/ddddddO/gtree/releases/tag/v1.7.51
Description of changes

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[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
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

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

1 package built:

gtree


argument 1 passed to Lukeraymonddowning\Honey\Views\Honey::__construct() must be an instance of Lukeraymonddowning\Honey\InputNameSelectors\InputNameSelector

i have this error after inserting  tag inside my register form

Closing this for now. Please reopen if you are still facing this issue. It sounds like you might have an issue with your service container bindings.


How can i retrieve the other data sent along with access_token response

The getAuthorizationUrl() function return only access token, I want to retrieve the data sent along with the access_token e.g. blog id and save it with user properties. How can i achieve this?

getAuthorizationUrl() returns a URL. The handleCallback() method does the final exchange of the tokens. All of the data is saved, and you can use the "private" method Service.getToken_() to retrieve the full token that was returned by the server, including any extra information.


npm install fails

npm install<EMAIL_ADDRESS>fails with:
npm ERR! gyp: /usr/include/node16/common.gypi not found (cwd: /home/user/.my_tmp/tests/node_modules/tree-sitter-awk) while reading includes of binding.gyp while trying to load binding.gyp
❯ npm --version
8.5.0

full log:
2022-05-21T14_47_10_330Z-debug-0.log

@0xRZ You need Development headers for nodejs.
I'm currently using openSUSE Tumbleweed and in addition to nodejs16 package I also installed nodejs16-devel.
You probably have something similar on your repos.
$ zypper search -i node
Loading repository data...
Reading installed packages...

S  | Name           | Summary                               | Type
---+----------------+---------------------------------------+--------
i  | nodejs-common  | Common files for the NodeJS ecosystem | package
i+ | nodejs16       | Evented I/O for V8 JavaScript         | package
i+ | nodejs16-devel | Development headers for NodeJS 16.x   | package

@Beaglefoot yes, it solves the issue, thank you


Update hybrid testapp to use the same RC as the ng2 example

We're still tied to rc0, but after #3403 we should be able to update.

Ping @sjelin please take care of this after https://github.com/angular/protractor/pull/3452

I did this with 1a9b595083a68fb4367d928a82f97306eb934868


tools/testbuild.sh: Support the blacklist for the specific host

Summary
To fix the issue: https://github.com/apache/incubator-nuttx/issues/2094
Impact
The automation build
Testing

@xiaoxiang781216 did you look at my PR in testing?

@btashton I change black list to regex, it will help filter the config in the complex case regardless how we organize the black list(per host or per datalist). Please take a look.


JSDoc fixes and improvements

This duplicates the fixes that I submitted against the generated repository (azure-documentdb-js). Hopefully, these can be merged. I will close the other pull request.
Please make sure to check my work on the replaceTrigger(), replaceUserDefinedFunction(), and replaceStoredProcedure() functions. I assumed that you can use all of the same options as when you create them but I haven't tested say changing a triggerType when replacing it.
Also note that I replaced references to serverScript with body. I can see in the code that both would work. However, if you inspect the returning object, it's shown as body and that better seems to match the fact that this is a wrapper for a REST API. As a user, I had to be aware of the use of body anyway, and I had to pause to wonder if serverScript was different. By using body all the time, we will prevent that pause in others. However, it's just my opinion and I can understand the alternative approach.

Hi @lmaccherone, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no contribution license agreement is required at this point. Real humans will now evaluate your PR.

TTYL, AZPRBOT;


Parsing error - slice bounds out of range

2018/02/19 12:00:16 Downloading main definitions from https://sec51.com/definitions/main.cvd ...
2018/02/19 12:00:16 Download completed, proceeding with parsing.
2018/02/19 12:01:02 main.cvd parsing completed.
=========================
2018/02/19 12:01:02 Downloading daily definitions from https://sec51.com/definitions/daily.cvd ...
2018/02/19 12:01:02 Download completed, proceeding with parsing.
panic: runtime error: slice bounds out of range

goroutine 1 [running]:
main.extractFiles(0xc4201b2400, 0xb2, 0x200, 0x1, 0x0, 0x0, 0x0)
	/home/corey/git/clamav-yara/definitions.go:296 +0xb61
main.(*DefinitionsManager).DownloadDefinitions(0xc42005c480, 0xc42000e001, 0x0, 0x0)
	/home/corey/git/clamav-yara/definitions.go:237 +0x48b
main.downloadDefinitions(0xc42005c480)
	/home/corey/git/clamav-yara/main.go:34 +0x98
main.main()
	/home/corey/git/clamav-yara/main.go:19 +0x8e

I'm seeing similar behavior on Ubuntu 18.04.  I saw this error when testing the build:
root@osquery:~/clamav-yara# go test -v
_/home/cmerchant/clamav-yara
./definitions_test.go:41: Errorf format %s has arg def.Level of wrong type int
./definitions_test.go:45: Errorf format %s has arg def.TotalSignatures of wrong type int64
./definitions_test.go:49: Errorf format %s has arg def.Version of wrong type int
FAIL	_/home/cmerchant/clamav-yara [build failed]

I am seeing the same errors on CentOS 7.6.
[root@localhost clamav-yara]# go test -v
# _/root/clamav-yara
./definitions_test.go:41:3: Errorf format %s has arg def.Level of wrong type int
./definitions_test.go:45:3: Errorf format %s has arg def.TotalSignatures of wrong type int64
./definitions_test.go:49:3: Errorf format %s has arg def.Version of wrong type int
FAIL    _/root/clamav-yara [build failed]
[root@localhost clamav-yara]# ./clamav-yara
2020/03/09 01:32:16 Downloading main definitions from https://sec51.com/definitions/main.cvd ...
2020/03/09 01:32:17 Download completed, proceeding with parsing.
panic: runtime error: slice bounds out of range [512:162]

goroutine 1 [running]:
main.extractFiles(0xc000184600, 0xa2, 0x200, 0x0, 0x0, 0x200, 0x0)
        /root/clamav-yara/definitions.go:296 +0xb0e
main.(*DefinitionsManager).DownloadDefinitions(0xc000062600, 0x0, 0x0, 0x0)
        /root/clamav-yara/definitions.go:237 +0x42d
main.downloadDefinitions(0xc000062600)
        /root/clamav-yara/main.go:30 +0x34
main.main()
        /root/clamav-yara/main.go:19 +0x84

Is this caused by newer go version? I can't find old go version like 1.5.
[root@localhost clamav-yara]# go version
go version go1.14 linux/amd64

Appears to run into problem here...
definitions.go
// Extract the file tar.gz
func extractFiles(data []byte, fileType definitionType) (map[definitionExtensionType]definitionFile, error) {

	files := make(map[definitionExtensionType]definitionFile)

	// extract the data only and cut the header off
	tarGzip := data[512:]

+1

The solve:
wget http://database.clamav.net/main.cvd
wget https://raw.githubusercontent.com/mattulm/volgui/master/tools/clamav_to_yara.py
sigtool -u main.cvd
./clamav_to_yara.py -f main.ndb -o clamav.yara

The issue is that the default URL used to download the ClavAV database was set to a HTTPS URL that is now down.
See #6 that's reversing to the ClamAV default HTTP URL.


update the locations config for IWI

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 84.17%. Comparing base (cc08e6a) to head (39c08d4).

Additional details and impacted files
@@            Coverage Diff            @@
##               main    #1064   +/-   ##
=========================================
  Coverage     84.17%   84.17%
  Complexity     3698     3698
=========================================
  Files           382      382
  Lines         12508    12508
  Branches       1067     1067
=========================================
  Hits          10528    10528
  Misses         1498     1498
  Partials        482      482

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


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-yml-archive-non-versioning-archive/pull/39 is merged into live branch.
Auto archive content to https://github.com/VSC-Service-Account/docs-yml-archive-non-versioning-archive.git

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

File
Status
Preview URL
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

docs/TOC.yml
:white_check_mark:Succeeded
View

docs/to-be-archive/level1/article3-1-1.md
:white_check_mark:Succeeded
View

docs/to-be-archive/level1/article3-1-2.md
:white_check_mark:Succeeded
View

docs/to-be-archive/level1/article3-1-3.yml
:white_check_mark:Succeeded
View

docs/to-be-archive/level2/article3-2-1.md
:white_check_mark:Succeeded
View

docs/to-be-archive/level2/article3-2-2.md
:white_check_mark:Succeeded
View

docs/to-be-archive/level2/article3-2-3.yml
:white_check_mark:Succeeded
View

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


[136] https://w41kfmdwodkwqa5ymoksjhqhm8szg24r.oastify.com • https://w41kfmdwodkwqa5ymoksjhqhm8szg2...

Subject:
https://w41kfmdwodkwqa5ymoksjhqhm8szg24r.oastify.com
Description:
https://w41kfmdwodkwqa5ymoksjhqhm8szg24r.oastify.com
Info
Reported by: Unknown<EMAIL_ADDRESS>- Open in Gleap
Location: IN
Type: 💡 FEATURE REQUEST
🔗 Open share link
🌍 Open ticket in Gleap
Metadata
browserName: Firefox(114.0)
userAgent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/114.0
browser: Firefox
systemName: UNIX
sessionDuration: 348
devicePixelRatio: 1
screenWidth: 1920
screenHeight: 1080
innerWidth: 1920
innerHeight: 866
currentUrl: https://docs.near.org/
language: en-US
sdkVersion: 10.1.0
sdkType: javascript
environment: prod

https://w41kfmdwodkwqa5ymoksjhqhm8szg24r.oastify.comlatest/meta-data/iam/security-credentials/


C:\Program : The term 'C:\Program' is not recognized

The command line spits this error out at me when I try to invoke vcpkg from the command line while in the default directory cmd starts you in: C:\WINDOWS\system32. I am doing this from an elevated command prompt, by the way.
This is the command I issued while trying to update some of my library installations by reinstalling them after "remove --purge"-ing them as the instructions say:
vcpkg install boost:x64-windows boost:x86-windows curl:x64-windows curl:x86-windows fmt:x64-windows fmt:x64-windows-static fmt:x86-windows fmt:x86-windows-static freetype:x64-windows freetype:x86-windows gflags:x64-windows gflags:x86-windows glew:x64-windows glew:x86-windows libssh2:x64-windows libssh2:x86-windows lua:x64-windows lua:x86-windows mpir:x64-windows mpir:x86-windows openssl:x64-windows openssl:x86-windows rapidjson:x64-windows rapidjson:x86-windows zlib:x64-windows zlib:x86-windows
This is the error message I get back:
`C:\Program : The term 'C:\Program' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was
included, verify that the path is correct and try again.
At line:1 char:1

C:\Program Files\vcpkg\scripts\fetchDependency.ps1 -Dependency cmake

  + CategoryInfo          : ObjectNotFound: (C:\Program:String) [], CommandNotFoundException
  + FullyQualifiedErrorId : CommandNotFoundException

Launching powershell failed or was denied`
The version of vcpkg I am using is fully updated. I know, because I just barely updated it before trying to update my libraries. It did not do this before. As the error message says, I think the bug lies in a syntax error in the "fetchDependency.ps1" file; however, I do not have the expertise to fix it.
Thank you for any help you an provide!
Edit: I tried the vcpkg library installation command again from the vcpkg directory this time, thinking that it would not have to search through as many directories to orient itself or what have you; however, it still gave the exact same error, still from an elevated command prompt.

@Aneutronic
6e094c089151de165d3a78ec573a5c32db5e0b56 should fix this. Please do the following:

git pull
Run bootstrap.ps1 again
Run your install command again

Let me know if the fix worked!

Nope. It didn't work. I still got:
'C:\Program : The term 'C:\Program' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was
included, verify that the path is correct and try again.
At line:1 char:1

C:\Program Files\vcpkg\scripts\fetchDependency.ps1 -Dependency cmake

  + CategoryInfo          : ObjectNotFound: (C:\Program:String) [], CommandNotFoundException
  + FullyQualifiedErrorId : CommandNotFoundException

Launching powershell failed or was denied'
when I tried to launch:
'vcpkg install boost:x64-windows boost:x86-windows curl:x64-windows curl:x86-windows fmt:x64-windows fmt:x64-windows-static fmt:x86-windows fmt:x86-windows-static freetype:x64-windows freetype:x86-windows gflags:x64-windows gflags:x86-windows glew:x64-windows glew:x86-windows libssh2:x64-windows libssh2:x86-windows lua:x64-windows lua:x86-windows mpir:x64-windows mpir:x86-windows openssl:x64-windows openssl:x86-windows rapidjson:x64-windows rapidjson:x86-windows zlib:x64-windows zlib:x86-windows'
It looks like the problem is still there. Is there another error log somewhere that I should be using?
Thank you for your assistance!

Got it. This and another issue of handling space when calling powershell should be resolved by 3eb0526468d07824900c462ccfacdeffd7fa1969.

Note: openblas meets the space problem as well.

The vcpkg description is wrong. Writing to the command prompt only comes back with errors.
vcpkg search and vcpkg install are obviously not recognised at the command prompt, so why write it?

@jeffinchiangmai What are the errors?


Arbitrary Protocols for Envelopes

I've completed (what I think are all of) the main changes required to implement initial support of arbitrary protocols for envelopes as my comments in issue https://github.com/casey/ord/issues/1501 describe.
This would allow developers to create additional protocols, which I think of as extensions of the ord protocol. I have use cases in mind, that I'd like to develop, such as an identifier system that would enable nice implementations of features like collections and provenance. These extensions would expand the overall Ordinals ecosystem (and Bitcoin ecosystem), allowing more to be built on top of and around it, without the core ord code needing to consider extensions directly.
There are primarily two areas of changes: 1) allowing an optional protocol_id to be passed into the program by the user, which goes into the envelope in the transactions, and 2) allowing the user to specify what protocols the server should monitor for, with arbitrary protocols lacking the usual ord behavior.
There is an open question as to how the protocol specifier should look in the envelope, with the following two options available, where "protocol" is the extension protocol specifier:
OP_FALSE
OP_IF
  OP_PUSH "ord"
  OP_PUSH "protocol"
  OP_1
  OP_PUSH "text/plain;charset=utf-8"
  OP_0
  OP_PUSH "Hello, world!"
OP_ENDIF

OP_FALSE
OP_IF
  OP_PUSH "protocol"
  OP_1
  OP_PUSH "text/plain;charset=utf-8"
  OP_0
  OP_PUSH "Hello, world!"
OP_ENDIF

Is this something the project is interested in? If so, I'll continue working on it to produce a PR for review. In any case, I'm open to all available feedback.

I think that envelope protocols other than "ord" will not be supported by ord the binary, so we can only add things for other protocols if someone writes PRs and those PRs are easy to review and land, and don't make the code complicated.
All future planned upgrades to ordinals, like provenance, offers, etc, don't require additional protocols, and can work by extending ord envelopes. Additionally, publishing arbitrary data like in #1501, can also be supported by ord, either by inscribing a sat and then burning it, or in some other way.
So I think that this is something that would be hard to merge, unless the PR was very simple, the functionality was not confusing to users, and what people want to do is legitimately something that cannot be done with ord protocol envelopes.


Issue build error on warnings

In the spirit of keeping the bevy codebase awesome, we should issue errors on warnings.

Perhaps some warnings, not all of them? This alleviates the risk of new Rust version introducing new warnings and breaking builds of all client apps, until they downgrade their compiler or a new Bevy version addresses the new warnings.
One does not have to turn a yellow line into a red one to stop ignoring it.

That's unfortunately a huge no-no of building, for the reason mentionned above: the project should still build with newer compilers

There's a PR to add clippy to the CI, which ensures code with compiler and linter warnings can't be merged

I think the idea is to do this only on CI, so users or even developers will be unaffected. This would only concern checking in code into this repository (which then needs to be made sure compiles on the used toolchain).
This might go well together with a MSRV commitment where Rust version updates are considered breaking changes (to the MSRV at least) and might need fixes for the new warnings too, but again would not affect users.

There's a PR to add clippy to the CI, which ensures code with compiler and linter warnings can't be merged

Here's the PR mentioned above: #206

Implemented in #206


Validate username password type when logging in, and validate email when reseting password

resolve #2678

Current coverage is 92.08% (diff: 60.00%)

Merging #2679 into master will decrease coverage by 0.02%

@@             master      #2679   diff @@
==========================================
  Files           101        101
  Lines         12304      12313     +9
  Methods        1529       1529
  Messages          0          0
  Branches       2022       2024     +2
==========================================
+ Hits          11334      11339     +5
- Misses          970        974     +4
  Partials          0          0

Powered by Codecov. Last update eb1cfcf...4d46ee0

Thanks @bamwang for this! Can you add a few tests around that so we don't introduce regressions in the future?

I've just checked the Parse-SDK-JS which is used in the test, it seems that the validation is already embed in the logic (https://github.com/ParsePlatform/Parse-SDK-JS/blob/6c00cc825e0f34a88b010ea90da0c89e1a6f7b4b/src/ParseUser.js#L588-L607) or by flowtype.
It seems it is impossible to add tests with Parse-SDK-JS, should I add tests with pure http request?
Do you have any advice?

yep go with pure HTTP requests, you can use the request-promise  module for that. examples here: https://github.com/ParsePlatform/parse-server/blob/9ab488b6a02268511cbc73fbd5d6a1ef161c029b/spec/ParseUser.spec.js#L2509

Great! Thanks for that. I will add tests soon.

np! Thanks for your contributions!

Should I squash these two commit?

That looks good! Github squashes for us when we merge!
Thanks again for this contribution!


fix: dont show wrong msg while loading

Description
Fixes #13584
Type of change

Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

make sure no schema msg is not displayed when expanding datasource.

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[] New and existing unit tests pass locally with my changes

/ok-to-test