Clarify why you need an adapter

Proposes a fix to https://github.com/withastro/docs/issues/793

Change "is enabled" to "can be enabled", as SSR is not enabled by default
Describe what a runtime is
Add an explanation for why we need an adapter: it provides a runtime
Clarification that if you don't need SSR, you don't need an adapter

LGTM, Dan!
Squash. Merge. Go forth and spread the word about why you need an adapter.

❤🚀🤹♀🧩


Clarified how to invoke the other two actions

Only one of three actions is described. The other two actions are different, these have no parameters defined. For clarity, this is shown in this extra example.

Hi @sandervandevelde, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). 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, MSBOT;

@sandervandevelde : Thanks for your contribution to the Azure documentation! The author, @olivierbloch, has been notified to review your proposed change.

#sign-off


ERROR: Unrecognized parameter: -F

The documentation mentions the existence of a -F option for bedtools intersect: http://bedtools.readthedocs.org/en/latest/content/tools/intersect.html
However, when I try to use it (with -F 1), I obtain the following:
***** ERROR: Unrecognized parameter: -F *****
***** ERROR: Unrecognized parameter: 1 *****

Tool:    bedtools intersect (aka intersectBed)
Version: v2.23.0
Summary: Report overlaps between two feature files.

Usage:   bedtools intersect [OPTIONS] -a <bed/gff/vcf/bam> -b <bed/gff/vcf/bam>

	Note: -b may be followed with multiple databases and/or
	wildcard (*) character(s).
Options:
	-ubam	Write uncompressed BAM output. Default writes compressed BAM.

	-bed	When using BAM input (-abam), write output as BED. The default
		is to write output in BAM when using -abam.

	-wa	Write the original entry in A for each overlap.

	-wb	Write the original entry in B for each overlap.
		- Useful for knowing _what_ A overlaps. Restricted by -f and -r.

	-loj	Perform a "left outer join". That is, for each feature in A
		report each overlap with B.  If no overlaps are found,
		report a NULL feature for B.

	-wo	Write the original A and B entries plus the number of base
		pairs of overlap between the two features.
		- Overlaps restricted by -f and -r.
		  Only A features with overlap are reported.

	-wao	Write the original A and B entries plus the number of base
		pairs of overlap between the two features.
		- Overlapping features restricted by -f and -r.
		  However, A features w/o overlap are also reported
		  with a NULL B feature and overlap = 0.

	-u	Write the original A entry _once_ if _any_ overlaps found in B.
		- In other words, just report the fact >=1 hit was found.
		- Overlaps restricted by -f and -r.

	-c	For each entry in A, report the number of overlaps with B.
		- Reports 0 for A entries that have no overlap with B.
		- Overlaps restricted by -f and -r.

	-v	Only report those entries in A that have _no overlaps_ with B.
		- Similar to "grep -v" (an homage).

	-f	Minimum overlap required as a fraction of A.
		- Default is 1E-9 (i.e., 1bp).
		- FLOAT (e.g. 0.50)

	-r	Require that the fraction overlap be reciprocal for A and B.
		- In other words, if -f is 0.90 and -r is used, this requires
		  that B overlap 90% of A and A _also_ overlaps 90% of B.

	-s	Require same strandedness.  That is, only report hits in B
		that overlap A on the _same_ strand.
		- By default, overlaps are reported without respect to strand.

	-S	Require different strandedness.  That is, only report hits in B
		that overlap A on the _opposite_ strand.
		- By default, overlaps are reported without respect to strand.

	-split	Treat "split" BAM or BED12 entries as distinct BED intervals.

	-sorted	Use the "chromsweep" algorithm for sorted (-k1,1 -k2,2n) input.

	-g	Provide a genome file to enforce consistent chromosome sort order
		across input files. Only applies when used with -sorted option.

	-header	Print the header from the A file prior to results.

	-nobuf	Disable buffered output. Using this option will cause each line
		of output to be printed as it is generated, rather than saved
		in a buffer. This will make printing large output files
		noticeably slower, but can be useful in conjunction with
		other software tools and scripts that need to process one
		line of bedtools output at a time.

	-names	When using multiple databases, provide an alias for each that
		will appear instead of a fileId when also printing the DB record.

	-filenames	When using multiple databases, show each complete filename
			instead of a fileId when also printing the DB record.

	-sortout	When using multiple databases, sort the output DB hits
			for each record.

	-iobuf	Follow with desired integer size of read buffer.
		Optional suffixes K/M/G supported.
		Note: currently has no effect with compressed files.

Notes:
	(1) When a BAM file is used for the A file, the alignment is retained if overlaps exist,
	and exlcuded if an overlap cannot be found.  If multiple overlaps exist, they are not
	reported, as we are only testing for one or more overlaps.

This option would be useful if it existed, as -a and -b files do not play a symmetrical role.

This option did not become available until version 2.25:. Sorry for the confusion: http://bedtools.readthedocs.org/en/latest/content/history.html#version-2-25-0-3-sept-2015

I had a quick look at https://github.com/arq5x/bedtools2/releases and didn't see mention of the -F option. I should have had a look at the link concerning version 2.25.


[Box] forward ref of view

Hi,
I'm using more and more your lib (and delete tons of styles), and I am often annoyed when I want to use a ref on a Box
I would like to measure it using https://reactnative.dev/docs/direct-manipulation#measurecallback
For the moment I wrap my Box with a view but I would like to measure the Box directly
What do you think ? Could we have a forward ref on Box ?

@mlecoq 👋  I think it's doable, but could you provide a simple snippet of your current approach? :)

Sure
Here it is

   <RemarkItemContainer first={first} ref={containerRef}>
        <Box padding={[10, 15]}>
        ....
        </Box>
   </RemarkItemContainer>

RemarkItemContainer is created with styles-components
const RemarkItemContainer = styled.View...
My goal is to be able to have
const RemarkItemContainer = styled(Box)...

   <RemarkItemContainer first={first} ref={containerRef} padding={[10, 15]}>
        ....
   </RemarkItemContainer>

And elsewhere
containerRef.current.measure....

@mlecoq 👋 sorry it took so loooong! I finally found spare time, the viewRef prop has been added to all components in v1.3.0. You can see the example here: https://github.com/mobily/stacks/blob/9a5deb65fbe73391988d7a4470bdae7ed26bafa8/example/src/typescript/screens/Playground/index.tsx#L23


The plugin no longer builds and runs with Java 8

The jar spdx-rdf-store seems to be compiled to Java 11?
This POM says Java 8 but running mvn clean install for this plugin says:
[INFO] -------------------------------------------------------------
[ERROR] COMPILATION ERROR :
[INFO] -------------------------------------------------------------
[ERROR] /C:/Users/ggregory/git/g/spdx-maven-plugin/src/main/java/org/spdx/maven/SpdxDependencyInformation.java:[69,29] cannot access org.spdx.spdxRdfStore.RdfStore
  bad class file: C:\Users\ggregory\.m2\repository\org\spdx\spdx-rdf-store\1.1.3\spdx-rdf-store-1.1.3.jar(org/spdx/spdxRdfStore/RdfStore.class)
    class file has wrong version 55.0, should be 52.0
    Please remove or make sure it appears in the correct subdirectory of the classpath.
[INFO] 1 error
[INFO] -------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  6.531 s
[INFO] Finished at: 2023-02-04T10:18:15-05:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) on project spdx-maven-plugin: Compilation failure
[ERROR] /C:/Users/ggregory/git/g/spdx-maven-plugin/src/main/java/org/spdx/maven/SpdxDependencyInformation.java:[69,29] cannot access org.spdx.spdxRdfStore.RdfStore
[ERROR]   bad class file: C:\Users\ggregory\.m2\repository\org\spdx\spdx-rdf-store\1.1.3\spdx-rdf-store-1.1.3.jar(org/spdx/spdxRdfStore/RdfStore.class)
[ERROR]     class file has wrong version 55.0, should be 52.0
[ERROR]     Please remove or make sure it appears in the correct subdirectory of the classpath.
[ERROR]
[ERROR] -> [Help 1]

Ah... the problems seems to be an eager update to Apache Jena, building spdx-rdf-store with Java 8 yields:
[INFO] -------------------------------------------------------------
[ERROR] COMPILATION ERROR :
[INFO] -------------------------------------------------------------
[ERROR] /C:/Users/ggregory/git/g/spdx-java-rdf-store/src/main/java/org/spdx/spdxRdfStore/RdfStore.java:[38,29] cannot access org.apache.jena.graph.Node
  bad class file: C:\Users\ggregory\.m2\repository\org\apache\jena\jena-core\4.7.0\jena-core-4.7.0.jar(org/apache/jena/graph/Node.class)
    class file has wrong version 55.0, should be 52.0
    Please remove or make sure it appears in the correct subdirectory of the classpath.

Please go back to supporting Java 8 or make it obvious that Java 11 is required.

@garydgregory Thanks for pointing out the inconsistency.  One of the dependencies required Java 11 (previous versions of the dependency have security vulnerabilities), so I'll update the POM file  to require Java 11.

@garydgregory Could you look at PR #77 and let me know if this resolves the issue.
Note that the dependency is only required if we're outputting RDF format SPDX.  For JSON, I think (but need to verify) we can continue to use Java 1.8.
If using Java 11 is a significant issue, perhaps we can explore a way of making the RDF format a more optional dependency.  Not quite sure how we would do that, but let me know if you have any thoughts.

Hi @goneall
I commented in the PR. Whichever Java version you require is up to you ;-) For us over at Apache Commons that means that if Java 11 is required we will have to run release builds using Java 11 instead of 8 which will end up being a problem likely if a component uses the NIO Buffer APIs where methods move from Java version to version in the hierarchy. I've only encountered the need for Java 11 with the spdx plugin when running a multi-module build, never in a simple Maven project. Eventually we will migrate to Java 11 but there are no immediate plans.

@garydgregory - Are you using the RDF format for your output or just JSON?  If JSON, then the library causing the problem isn't really being used.
BTW - Apache Jena is the library which is requiring the upgrade in Java versions.  Jena versions which use Java 8 have a security vulnerability which I though might impact downstream users.


Redirecting to home page when clicked on Brand Name

A path should be added to the Brand Name to redirect to the home page

If possibel, please assign me this under gssoc 2023

Raise this issue once you complete the previous one.


Add address to request

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@6834619). Click here to learn what that means.
The diff coverage is 100%.

@@            Coverage Diff            @@
##             master     #101   +/-   ##
=========================================
  Coverage          ?   99.87%
=========================================
  Files             ?       52
  Lines             ?      833
  Branches          ?        0
=========================================
  Hits              ?      832
  Misses            ?        1
  Partials          ?        0

Impacted Files
Coverage Δ

src/Services/Adapters/RequestAdapter.php
100% <100%> (ø)

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 6834619...b41fee5. Read the comment docs.


edit existing healthsite

Login with OSM
Go to:
https://healthsites.io/map#!/locality/node/6609222186
select edit button, update an attribute..indicate clinic, Save
'Error when uploading.
Duplication detected. Node with OKT Oud Oost name was found around the area.'

Already fixed


Customization to snooze

The snooze time configuration should also have an option to select a snooze time each time the snooze option is taken on a notification

Unfortunately, this is technically not feasible: Raising a dialog from a notification is not possible. I could start an activity that does it, but this would not be directly visible and still hidden behind the notification bar. I do not consider that very user friendly.
Therefore, I will not implement this feature.


Version 0.4.0 not on Maven Central

Couldn't find it at http://repo1.maven.org/maven2/com/github/romix/akka/akka-kryo-serialization_2.11/ or at http://search.maven.org/#search|gav|1|g%3A"com.github.romix.akka" AND a%3A"akka-kryo-serialization_2.11"

Can confirm, I wasn't going to ask hoping that maybe was a cache issue but it is not almost 24 hours.

It should be available on maven central now.

Thank you very much.


add getWalletInfo method

📦 Pull Request
[Provide a general summary of the pull request here.]
Adds new method getWalletInfo() which returns an object with the wallet type that the user is logged in with (magic, metamask, wallet_connect or coinbase_wallet)
✅ Fixed Issues

[List any fixed issues here like: Fixes #XXXX]

🚨 Test instructions
[Describe any additional context required to test the PR/feature/bug fix.]
⚠ Don't forget to add a semver label!

patch: Bug Fix?
minor: New Feature?
major: Breaking Change?
skip-release: It's unnecessary to publish this change.

https://app.shortcut.com/magic-labs/story/58953/add-getwalletinfo-to-connect-sdk

:rocket: PR was released in<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>:rocket:


org.mapdb.DB.checkNotClosed(DB.kt:153)

Hi,

I create a DBMaker.memoryDB() and overflow goes to DBMaker.fileDB()
then I create HTreeMap with a given key later i clear and close HTreeMap instance
and I have not closed my  both DB (memory and file) the I try to create again a  HTreeMap with the same key then i get the following exception
java.lang.IllegalAccessError: DB was closed
at org.mapdb.DB.checkNotClosed(DB.kt:153)
at org.mapdb.DB$Maker.make2(DB.kt:1373)
at org.mapdb.DB$Maker.createOrOpen(DB.kt:1363)
at org.mapdb.DB$HashMapMaker.createOrOpen(DB.kt:961)

i am using mapdb 3.0.7 version


Add Finish FMI stations

https://en.ilmatieteenlaitos.fi/weather-observations

@AdamRJensen, has somebody told you that they are actually doing DNI and DHI measurements? On their website, they give very little information, and when trying to download solar irradiance data, they only have GHI, LWD, and UV.

I am not convinced...

I have sent an email to contacts at the University of Turku.

Based on the email from Turku, there are three Tier 1 active stations in 2024. Data can be accessed here.
Just for documentation:

The website is not very user-friendly in identifying historical measurements. When I was trying to figure out when the Tier 1 stations started measuring DNI, more stations were popping up for some years, so it is possible that historical DNI data are available for more locations.
Also, there are a number of stations measuring only GHI and DHI, but since they don't give specific information on the instruments used, I did not include them.

One of the stations is duplicate: the space station one. I suggest consulting the two websites to see how best to merge the info. I suggest keeping the comment about poor data quality.


License model

Could you tell me what's the license model of your package? Thanks in advance.

Select2 is currently licensed as MIT: https://github.com/select2/select2/blob/master/LICENSE.md.

Currently unlicensed.  I'll change it to MIT.
On Thu, Nov 12, 2015 at 11:15 AM, Pierre-Eric Marchandet <
<EMAIL_ADDRESS>wrote:

Select2 is currently licensed as MIT:
https://github.com/select2/select2/blob/master/LICENSE.md.
—
Reply to this email directly or view it on GitHub
https://github.com/nate-strauser/meteor-select2/issues/19#issuecomment-156152415
.

Thanks, you rock :+1:


Check variant maintenance gets stuck

https://github.com/abaplint/abaplint-sci-client/blob/4ea4188f87bcc6a5f4dd2dc2c6d614c76a08fea2/src/zcl_abaplint_check.clas.abap#L126
Would it be possible to remove / move this call? For some time we couldn't edit any check variants because after selecting it and pressing edit you would get a loading indicator and nothing would happen. There also isn't a process in SM50. After some debugging I noticed that it's the abaplint check that is responsible. The call above causes a network call which apparently get's stuck for some reason in our setup (but doesn't time out either anytime soon). We aren't actively using this check just have it installed. You also cannot deactivate the check to fix this temporarily as the option in the menu where you enable and disable checks cannot be opened either. I assume both screens cause the class constructor to be called for every check class including this one.

stupid class_constructor, move the logic out of the class constructor instead, call it when its needed


Remove the hard coded RepositoryUrl and leave it up to SourceLink to …

…determine the value
Mainly because it makes it simpler to do a build out of https://github.com/BoldonJames/JpegXmpWritePluginMDE and get the correct URL, but it also means that local builds from test branches get the right value, e.g.

Nothing official on nuget.org.
I think you can host packages in Github artifacts, but I've never tried it

Alright, the reason why I am asking is because we need a nuget API access key to be able to be able to push. It is setup for this repo not sure if build from any fork will work (not even sure if we always want to push to nuget). I will approving this PR anyway

(not even sure if we always want to push to nuget)

Not for every build, but it might be useful to attach the nuget package to the artifacts for CI builds, so that it can be downloaded and tested locally if needed?

Sounds good. Seems like there's documentation on how to do that. https://docs.github.com/en/packages/working-with-a-github-packages-registry/working-with-the-nuget-registry. Will try to squeeze that in


Move permission validators into WASM Plugin

See Triggers RFC
Also add corresponding instructions for their update at runtime.

@Arjentix please convert into epic and track changes


Read PATCH requests as UTF-8 encoded input streams

Resolves: https://jira.duraspace.org/browse/FCREPO-1993

So I am guessing you need to be on a system with a default encoding scheme that is NOT UTF-8 to be able to test this properly, yes?

Theoretically, no, but it could make for some messiness in Maven Surefire and Failsafe. Still, we might want to do it.

This looks good to me, especially given the integration test and error handling provided by the related
tickets:
https://jira.duraspace.org/browse/FCREPO-1973
https://jira.duraspace.org/browse/FCREPO-1979

So we are leaving this as being tested manually by Windows users? I don't have a particular problem with that, just wondering.

Anyone can test this by starting the JVM with the file.encoding property set to something other than utf-8. Using a Mac, without the file.encoding value set, this fixes PATCH requests containing utf-8 characters.

Given the other testing context around this PR, I am happy to see this move through as-is.


Ban Appeal

So i havent been on for days and aperently i got banned again. It states that they talked to me,but that is not true . It said they asked me to read the rules,they didn't. Futher sinds my temporarly ban i hardly left our town cos i was affraid of doing something wrong without knowing.  Pjlesure said something about togekiss, but dunno why that has anything 2 do with afk avoidence tho

Hello, don't u think it's about time 2 respond?!?!

I apologise for the delay in the response, so i'll forgive the tone.
In regards to your ban, you have broken few server rules, such as using AFK machines and griefing unclaimed bases. You were temporarily banned after your 2nd offence, which was also your final chance. And now you were permanently banned for griefing another unclaimed base. Its hard to argue that you unaware of the server rules, as you would've been told to read them at some point, or you should've read the rules if you were 'afraid of doing something wrong without knowing'. On these grounds, I am declining your appeal.

I never used AFK machines so that is defently not true. After i got warned and gave stuff back for taking stuff from a unclaimed base. I didn't do that on purpose either. They said i wasn't allowed to take stuff from unclaimed bases so i didn't. I did take some stuff from bases that were already distroyed. Didn't think that was an isseu coz than it is given back to nature right?


Fix import for migration deconstruction

This field moved its "canonical" location a long time ago (tests pass on supported versions of Django), and while the .fields location works, it results in unstable migrations when an EnumField is compared to previous migrations, for a compound field comprised of an EnumField and something else. A motivating use-case for this would be a MoneyField that combines a DecimalField and an EnumField.

thanks; merged and released as 1.7.0.


[Proposal] dynamic subscription model loading to offer flexibility of using non elequent model

We had some trouble try to use cashier in Mongo db using non elequent based models though packages like laravel-mongodb. and to make it work we overwrited the billable trait function subscriptions , and added our own version of subscription models.
My suggesion is:

add a new config for subscription model like we you made with user model and make it fallback to package version of subscription
add subscription function as a trait  and added to the model

Now anyone need it will easily change the config , create a new model subscription (extends from whatever ) and added the trait to it. if he wants to use the default he don't need to add anything the package will load the default model.

This goes a little beyond what Cashier is intended to do. In most Laravel apps you would add this to a User model or Team model. If you want you can just make these changes for your own use case or release your own package. But it's going a little too far for Cashier itself.


Vulnerability roundup 85: rake-12.3.2: 1 advisory [8.1]

search, files

[ ] CVE-2020-8130 CVSSv3=8.1 (nixos-20.03, nixos-unstable)

Scanned versions: nixos-20.03: a84b797b28e; nixos-unstable: 22c98819ccd. May contain false positives.
Cc @manveru
Cc @nicknovitski

Resolved through ad33f1800f2b2352d74ead11af39a0297875071e. Not considered for backport to 22.11.


updated changelog to reflect release 1.0.1

Current coverage is 81.20% (diff: 100%)

Merging #4590 into master will decrease coverage by 0.19%

@@             master      #4590   diff @@
==========================================
  Files          1297       1297
  Lines         44203      44203
  Methods           0          0
  Messages          0          0
  Branches       6991       6991
==========================================
- Hits          35981      35897    -84
- Misses         5554       5630    +76
- Partials       2668       2676     +8

Powered by Codecov. Last update 1ddcb27...bb3bbe9


Compressed SceneItem cannot be reloaded

When a SceneItem is loaded using loadSceneHierachy  it will mutate and remove  the compressedFormat field. If this scene is subsequently unloaded  and then reloaded the compressedFormat field does not exist and will throw an error.
Steps
loadSceneData('config.json')
const scene = app.scenes.find('sceneName')
app.scenes.loadSceneData(scene)
app.scenes.loadSceneHierarchy(scene)// <-- removes compressedFormat field

// some point later delete scene

app.scenes.loadSceneHierarchy(scene) // <-- Throws error

It makes sense that SceneItems are immutable, but there may be a reason why it is deleted. Either way this throws an error

@zachpeterpaul one for you?


wrong script src in "dist/book.html"

Hi there,
I think it shoud be "scripts/main.min.js" in "dist/book.html"
<!-- build:js scripts/main.min.js -->
<script src="scripts/main.js" async></script>
<!-- endbuild -->

we need to do a replacement in gulpfile.babel.js

the uncss package execute promisifyAll('fs') with { multiArgs: true }
this option cause the fails of critical
https://github.com/addyosmani/critical/blob/master/lib/file-helper.js#L347
the critical package would like to execute promisifyAll('fs') with default options.
return fs.readFileAsync(file.path).then(contents => {
    file.contents = contents;
    return file;
});

so the html task will abort at critical pipe.
https://github.com/GoogleChrome/essential-image-optimization/blob/0a4fcb22fc057eb1328463ece9d66cfb05fcc122/gulpfile.babel.js#L193-L206
and the output of  dist/index.html disappeared.
and <script src="scripts/main.js" async></script> would not be replaced. #

I opened a new issue to uncss
https://github.com/giakki/uncss/issues/341
Since

There is a work-in-progress branch that migrates away from Bluebird to native promises.

upgrade to the upcoming release of uncss will fix this issue.
For now, I think we could just skip uncss pipe in gulpfile.
https://github.com/GoogleChrome/essential-image-optimization/blob/0a4fcb22fc057eb1328463ece9d66cfb05fcc122/gulpfile.babel.js#L28
https://github.com/GoogleChrome/essential-image-optimization/blob/0a4fcb22fc057eb1328463ece9d66cfb05fcc122/gulpfile.babel.js#L112-L115

Can I fix this issue ?

Sure.
As uncss fixed this issue in 0.16.0,
upgrade devDependencies should work.
<EMAIL_ADDRESS>depends on<EMAIL_ADDRESS>We need a<EMAIL_ADDRESS>:D


A bug?

https://github.com/facebook/jest/commit/bb720d2e180e15b0d0962d255bb8f76901da4a66#diff-ad0be0b5e1f4711c408a42bdbea512bcR43-R57
:point_up: @SimenB This code change in your recent commit does break some tests in my code which used to work before. The issue I experience is that it is getting called from @jest/transform/build/ScriptTransformer.js:364:31 with null passed in as inputOptions argument, in this case the default {} value is not applied to inputOptions, it remains null and the code crashes at the line ...inputOptions.caller due to access to a field of null.

PR welcome changing to
diff --git i/packages/babel-jest/src/index.ts w/packages/babel-jest/src/index.ts
index 50259e0ec..5a23c4fdb 100644
--- i/packages/babel-jest/src/index.ts
+++ w/packages/babel-jest/src/index.ts
@@ -41,8 +41,9 @@ interface BabelJestTransformOptions extends TransformOptions {
 }

 const createTransformer = (
-  inputOptions: TransformOptions = {},
+  userOptions?: TransformOptions | null,
 ): BabelJestTransformer => {
+  const inputOptions: TransformOptions = userOptions ?? {};
   const options: BabelJestTransformOptions = {
     ...inputOptions,
     caller: {

along with some tests 🙂

Can I take this issue?

Go for it @yinm!


Require login to view job and project data

Description

Following the model of Jupyter, generate a token when launched. Users must login with that token before they can view sensitive data. All routes are protected, except for static content.
This feature requires an additional dependency: flask-login: https://flask-login.readthedocs.io/ which appears to be the best maintained package for the job.
Motivation and Context

On multi-user systems, anyone with access to the system can connect to servers running on open ports. This opens Dashboard user's projects to be read (and written to in the case of some modules) by anyone with access to the host system.
This pull requests prevents that access. Like Jupyter, it generates a login token when invoked on the command line. Following the security guidelines in the documentation, users will receive this token over a secure SSH channel.
$ python3 dashboard.py run
/home/joaander/venv/lib/python3.10/site-packages/signac/contrib/project.py:95: FutureWarning: This method will soon become a property and should be used without the call operator (parentheses).
  warnings.warn(
To access this server, connect to: http://localhost:8888/login?token=<hidden>
 * Serving Flask app 'signac-dashboard'
 * Debug mode: off
WARNING: This is a development server. Do not use it in a production deployment. Use a production WSGI server instead.
 * Running on http://localhost:8888
Press CTRL+C to quit

Other users that attempt to access the dashboard are greeted with:

In future work, we could add username/password authentication, where the user provides a hashed password in a config file.
Fixes #122
Checklist:

[x] I am familiar with the Contributing Guidelines.
[x] I agree with the terms of the Contributor Agreement.
[x] The changes introduced by this pull request are covered by existing or newly introduced tests.
[ ] The package documentation and framework documentation in signac-docs are up to date with these changes.
[x] I have updated the changelog and added any related issue and pull request numbers for future reference.

Documentation:
I will submit a request to update the framework documentation after this request is approved.

Should it be possible to disable the token-based login? e.g. if ACCESS_TOKEN is None.

This would make it more convenient for users on systems such as OLCF Marble, which already adds a layer of security. We could make this possible and warn users about it in the security page.

This looks good at a high level. I haven't tested it locally yet but I am fine with this PR being merged if others have tested it.

I have tested it. @cbkerr, have you?

@joaander @cbkerr I think this can merge when you are ready.

I have run it locally with my test dashboard and a test signac project with the Statepoint, ImageViewer, JobDocument, ProjectSchema, Notes and Document Editor modules, but not all modules.


Add dependabot

Adds dependabot to keep all the dependencies up to date

I would suggest either renovate or forking-renovate instead, since it seems to support more sources and not require individual configuration for everything.
Particularly relevant here might be corepack (package.json PackageManager field), nvm and node-version support should any get enabled in the repository.

I think it's already there? See: https://github.com/thlorenz/doctoc/pull/238


Extension Management Profiles

While it's nice that one can enable/disable Extensions per Workspace, I find myself with quite a few Workspaces that tend to have the same sets of extensions enabled or disabled (for example: Go projects, Vue.js projects, C projects, and so on).
Having to perform the enable/disable for every Workspace to narrow the set of appropriate Extensions is cumbersome and requires revisiting all Workspaces when a new Extension becomes applicable for a certain project type.
I'm wondering if there are plans to create an Extension Profile Manager in order to create distinct sets of enabled/disabled Extensions, depending on a user-defined project type?
And if not, would the current VSCode API even allow for this? So that I can maybe start working on such an Extension?

/duplicate

@sandy081 any reference to the issue(s) it's duplicating?

Please search for existing issues here using label extensions


Some of the account are not parsing into account table

Bug description
Some of the account from the genesis file is not on the account table

I think we need some examples to sort this out

I think we need some examples to sort this out


Preparation for release on PyPI

Closes #49
Based on #82:

Updates metadata
Sets version to 1.0.0

Test version at https://test.pypi.org/project/archeryutils-jatkinson1000/1.0.0/
Checklist:

[X] ~Source code updated to address issue~
[X] ~Style and formatting applied~
[X] ~Tests written to cover changes~
[X] ~Docstrings included/updated in code~
[X] Project documentation updated as necessary

Re-based on main to resolve conflicts


Embed type command capped at 256 characters in description only

In the new rich embed command type, the text for the description section is capped at 256 characters even though discord supports up to 2048 characters.
This same restriction is not placed on footer though, making the limit seemingly pointless.

Fixed in v2.0.2. This now checks footer like it should do.


Cannot package django-supervisor with py2app due to version.txt

If I use py2app to package a Django application with django-supervisor, it will not run as it's looking for version.txt within the site-packages.zip directory. I can work around this by hard-coding in the version number in the lines mentioned below but I do not believe this is a great solution. I will work to figure out a patch.
Traceback (most recent call last):
  File "/Users/kevinlondon/dropbox/programming/python/django/sample_app/dist/sample_app.app/Contents/Resources/lib/python2.7/manage.py", line 14, in <module>
    execute_from_command_line(sys.argv)
  File "/Users/kevinlondon/dropbox/programming/python/django/sample_app/dist/sample_app.app/Contents/Resources/lib/python2.7/django/core/management/__init__.py", line 453, in execute_from_command_line
    utility.execute()
  File "/Users/kevinlondon/dropbox/programming/python/django/sample_app/dist/sample_app.app/Contents/Resources/lib/python2.7/django/core/management/__init__.py", line 392, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/Users/kevinlondon/dropbox/programming/python/django/sample_app/dist/sample_app.app/Contents/Resources/lib/python2.7/django/core/management/__init__.py", line 272, in fetch_command
    klass = load_command_class(app_name, subcommand)
  File "/Users/kevinlondon/dropbox/programming/python/django/sample_app/dist/sample_app.app/Contents/Resources/lib/python2.7/django/core/management/__init__.py", line 77, in load_command_class
    module = import_module('%s.management.commands.%s' % (app_name, name))
  File "/Users/kevinlondon/dropbox/programming/python/django/sample_app/dist/sample_app.app/Contents/Resources/lib/python2.7/django/utils/importlib.py", line 35, in import_module
    __import__(name)
  File "/Users/kevinlondon/dropbox/programming/python/django/sample_app/dist/sample_app.app/Contents/Resources/lib/python2.7/djsupervisor/management/commands/supervisor.py", line 39, in <module>
    from supervisor import supervisord, supervisorctl
  File "supervisor/supervisord.pyc", line 41, in <module>
  File "supervisor/options.pyc", line 56, in <module>
IOError: [Errno 20] Not a directory: '/Users/kevinlondon/dropbox/programming/python/django/sample_app/dist/sample_app.app/Contents/Resources/lib/python2.7/site-packages.zip/supervisor/version.txt'

Thanks for reaching out. Unfortunately I am no longer actively maintaining this project, so I'm going to move it into archive mode:
https://rfk.id.au/blog/entry/archiving-open-source-projects/


[Bug]: Code for face embedding operator "inceptionresnetv1" is wrong

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
Code for face embedding operator "inceptionresnetv1" is wrong
https://towhee.io/face-embedding/inceptionresnetv1
import towhee

towhee.glob('./img.png') \
  .image_decode.cv2() \
  .face_embedding.inceptionresnetv1() \
  .tolist()

Expected Behavior
tolist() -> to_list()
import towhee

towhee.glob('./img.png') \
  .image_decode.cv2() \
  .face_embedding.inceptionresnetv1() \
  .to_list()

Steps To Reproduce
https://towhee.io/face-embedding/inceptionresnetv1

Environment
- Towhee version(e.g. v0.1.3 or 8b23a93): towhee 0.7.3.dev32 (models latest)
- OS(Ubuntu or CentOS):
- CPU/Memory:
- GPU:
- Others:

Anything else?
No response

it has been fixed.

Fixed, so close it.


End 2 end tracker desktop 556

@keybase/react-hackers
This adds the logged out tracker state and fixes styling stuff.
Preview

@cecileboucheron let me know if anything is off with this preview
please play around with it and make sure it looks good.

Icons are for another PR since there is a separate ticket for that.

Logged out should have a solid white background and not the transparent one:

vs

Hm, I can't trigger the cross to close in top right, it's that area where the OS grabs it as the titlebar -- was the cross farther down before, maybe, and that's why it used to work but now doesn't?

From what I see now:

The font color on the yellow is wrong, should be brown 60%.
The button color for the Close is wrong, should be lightGrey2 (#ebebeb)
The number of followers and following should be bold
The proof icons are the wrong ones, they're all available in the 'Icons 2' sheet in Zeplin
The list of proofs are pushed down, we can push them up (see position diff in nojima's comment above)
The service icons (Twitter, Github, website) are not aligned with the usernames, they're a tiny bit too high
The close button is too close to the edge on the right side.
The following green badge on the avatar is not a plain round shape but a green circle:

@keybase/react-hackers
New stuff that addresses the missing stuff from the comments and fixes the linux version.
The key on linux is you had to use globalStyles.windowDraggingClickable to undo the windowDragging and be able to click it.

:+1: % the svg renaming thing (sorry)

:thumbsup: tested on Linux


🐛 Bug Report: Repo Tools - API Reports - Process swallowed if args are not correct

📜 Description
If you have a space in the command like this, the space is in the args being sent to the -o flag:
backstage-repo-tools api-reports -o ae-wrong-input-file-type, ae-undocumented --validate-release-tags
The command will only output:
# Compiling TypeScript

👍 Expected behavior
I "think" the behaviour in this case should be an error that the command is wrong and that perhaps saying it got unexpected arguments.
👎 Actual Behavior with Screenshots
If you have a space in the command like this, the space is in the args being sent to the -o flag:
backstage-repo-tools api-reports -o ae-wrong-input-file-type, ae-undocumented --validate-release-tags
The command will only output:
# Compiling TypeScript

👟 Reproduction steps
This works best when you have changes that would need the API Reports to be updated.
In this repo or the Community Plugins repo update a build:api-reports:only script to pass args to the -o flag with a space between them like this:
backstage-repo-tools api-reports -o ae-wrong-input-file-type, ae-undocumented --validate-release-tags
Then run yarn build:api-reports notice that it does not generate a new API Report
Notice: the API Reports are not updated/generated
📃 Provide the context for the Bug.
I made the mistake of adding a space when I was upgrading the Azure DevOps plugins to 1.32.x. As this does not cause any errors it was merged in. Then in follow up PRs where I expected the API Reports to change I noticed this issue and fixed it.
This is problematic as it won't get picked up by the CI and you can easily move forward without these reported being updated.
🖥 Your Environment
This repo or the Community Plugins repo
👀 Have you spent some time to check if this bug has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
No, but I'm happy to collaborate on a PR with someone else

@awanlin Oddly, I tried reproducing the issue by executing the script directly (and logging what the API reports script is getting after parsing the omitMessages argument and it seems to error out as expected:

However, when setting the build:api-reports:only script as you mentioned, the bug occurs:

The script fails to obtain the second argument. I guess we could check that the omitMessages are all valid options, or perhaps just error out if any of the options are empty strings? Let me know your thoughts about it! 🙂
I can make a PR and also update the unit tests with the extra edge case.

I just made a quick PR for this issue! Given the way yarn parses the arguments by default, when adding a comma followed by a space and without wrapping with quotes, the raw omitMessages argument ends up as something that ends with a comma.
Also updated the unit tests to cover this edge case!


Problems creating docker entrypoint with '--' as last argument

Hi,
I'd really like to create a few base containers which can be used in production, but i couldn't get entrypoint of the docker_build rule in bazel to work properly.
Every time i need a closing '--' in an docker entrypoint bazel removes it and outputs an empty array, generating invalid docker metadata which docker refuses to load.
Is there a workarround i simply do not know in bazel to get this to work?
Generated metadata:
% cat bazel-bin/init/init-base.config
{"architecture": "amd64", "author": "Bazel", "config": {"Entrypoint": ["/tini", []], "User": "user"},
                                                                                ^^^

bazel log output
exec ${PAGER:-/usr/bin/less} "$0" || exit 1
-----------------------------------------------------------------------------
+ init/init-base
Skipping 2115094ee05658502a4cc9c28712baf34771c16b3de76f4a33499b463b8d7db5, already loaded.
Skipping 59fcdb78566467803b3ace1801501ca8b6754e55abe23d737be5a4245c1f21ea, already loaded.
Loading d58de6f97f4bb229e55abb7d6a13fbaf19590dc39b8939b66ede14fb6cd2e841...
json: cannot unmarshal array into Go value of type string
Use --strategy=TestRunner=standalone to disable sandboxing for the failing actions.

Bazel BUILD file example
docker_build(
    name = "init-base",
    base = "//base:base",
    entrypoint = ["/tini", "--"],
    tars = [
        ":tini.tar",
        ":init_passwd.passwd.tar",
    ],
    user = "user",
)

Link to my experiment (my redis branch contains both the init and redis container)
https://github.com/mgit-at/distroless/blob/redis/init/BUILD#L28

This looks like a docker_build bug, so I'm going to open a new issue on the right repo to track it.

Seems like a bug in argparse since --entrypoint=-- is coming through as a [] entry in our list...

A bug in argparse for sure.  A workaround is possible by postprocessing arg.entrypoint just after parsing, replacing all [] with '--'.  It seems to be only '--' that is affected, '-' or '---', or '--anything' works fine.
Note that --entrypoint= (empty string) is distinguishable from --entrypoint=[], so you don't have to worry about that:
python ./foo.py --entrypoint=-- --entrypoint=foo --entrypoint=''
[[], 'foo', '']

Here's the argparse bug: https://bugs.python.org/issue14364

Thanks @duggelz I will add some logic to do this.

Just to close things here, the linked issue is closed now.  LMK if you have any problems.


Shortlink is incorrect in Comment class

The Shortlink field Comment class is populated with weird links such as: https://oauth.reddit.com/r/teslamotors/comments/6ujtwe/_/dm0u4y1
The links go to HTTP 403 Forbidden
I am using NuGet 2.0.0-CI00028

That oauth should be a www. Otherwise that is the correct shortlink for comments (the "true" shortlinks with http://redd.it/etc only exist for posts).
Dang, wish I would have caught that when fixing the other shortlink issue.


Mast: Watch kvm-avindia.co.in

Mast requests the watch of the watch_keyword kvm-avindia\.co\.in. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

kvm-avindia\.co\.in has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by tripleee in Charcoal HQ


Confirmation about the URL and port for Azure AD connect in Azure China Cloud.

Hi guys,
Our customer follow the directions to open the Office 365 URL and IP Address Range operated by 21Vianet to config the connectivity of Azure AD Connect on Azure China Cloud.

The system show IP address is incomplete and finally they resolve this issue by appending the AzureActiveDirectory IP address in Service Tag in configuration.
There are three customer's concerns need your help to confirm:

Could you please share the complete URL and port for Azure China Cloud?

Could you please share he URL and port for writeback password?
In this troubleshoot article, there is no sample for configuring writeback password.
The customer try to configure and not sure what is the correct URL and port on Azure China.

Whether the O365 is mandatory for configuration of Azure AD Connect?
If not, Could you please share one Azure AD connect sample that contain only Azure URL and port because there are certain customers have no Office 365 account in China.

Best Regards,
Edward Chen

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 06faa428-c7b6-ca5c-271e-3f98d9536d4f
Version Independent ID: 63adb39a-c4fa-92bb-480d-59bee8e2dc24
Content: Azure AD Connect: Prerequisites and hardware
Content Source: articles/active-directory/hybrid/how-to-connect-install-prerequisites.md
Service: active-directory
Sub-service: hybrid
GitHub Login: @billmath
Microsoft Alias: billmath

Hi @rockboyfor, Thank you for the detailed question.  I have assigned the issue to the content author to evaluate and update this doc as appropriate

@Grace-MacJones-MSFT,
Could you please share any schedule for updating the following articles when necessary?
articles/active-directory/hybrid/how-to-connect-install-prerequisites.md
articles/active-directory/hybrid/tshoot-connect-connectivity.md
The customer are eager to find the resolution for corresponding content .
Best Regards,
Edward Chen


fftpack test failure in test_import

Reported by Derek Homeier on scipy-dev list (https://mail.scipy.org/pipermail/scipy-dev/2016-January/021173.html)
I found a single error trying to decode as ascii instead of unicode on running the tests for the
Python3 versions within the package build system, which occurs in general when LANG is not set,
or set to ‘C’ in the environment:

Running unit tests for scipy
NumPy version 1.10.4
NumPy relaxed strides checking option: False
NumPy is installed in /sw/lib/python3.5/site-packages/numpy
SciPy version 0.17.0rc2
SciPy is installed in /scratch.noindex/fink.build/root-scipy-py35-0.17.0rc2-1/sw/lib/python3.5/site-packages/scipy
Python version 3.5.1 (default, Jan  8 2016, 14:14:02) [GCC 4.2.1 Compatible Apple LLVM 7.0.2 (clang-700.1.81)]
nose version 1.3.7
…
......................................................
======================================================================
ERROR: test_fftpack_import (test_import.TestFFTPackImport)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/scratch.noindex/fink.build/root-scipy-py35-0.17.0rc2-1/sw/lib/python3.5/site-packages/scipy/fftpack/tests/test_import.py", line 29, in test_fftpack_import
    for line in file),
  File "/scratch.noindex/fink.build/root-scipy-py35-0.17.0rc2-1/sw/lib/python3.5/site-packages/scipy/fftpack/tests/test_import.py", line 28, in <genexpr>
    assert_(all(not re.fullmatch(regexp, line)
  File "/sw/lib/python3.5/encodings/ascii.py", line 26, in decode
    return codecs.ascii_decode(input, self.errors)[0]
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc2 in position 351: ordinal not in range(128)

----------------------------------------------------------------------
Ran 20182 tests in 279.411s

FAILED (KNOWNFAIL=97, SKIP=1647, errors=1)

The test is here: https://github.com/scipy/scipy/blob/master/scipy/fftpack/tests/test_import.py,
it was added in https://github.com/scipy/scipy/pull/5295.
From  a cursory glance it seems that it's the test which needs fixing.

Probably, yes. Looks like it is barfing on the first utf-8 encoded file it opens (here scipy/io/__init__.py) when it has to match a line with non-ascii characters. So I guess one needs to tell re to always use a utf-8 compatible encoding (assuming all non-ascii source files are using some kind of utf-8) instead of taking the default from the environment.
Ideally, I suppose the encoding would be set individually for each file by first parsing its header string...

Ah, it actually seems to be already the opening that's failing. So changing that to
    with path.open(encoding="utf-8") as file:

"fixes" the issue. Just wondering now how one is supposed to use the encoding string in the file to open it with the right encoding...

I wonder if we could just paper over the root cause
$ git diff test_import.py
diff --git a/scipy/fftpack/tests/test_import.py b/scipy/fftpack/tests/test_import.py
index 7562ca6..bd85993 100644
--- a/scipy/fftpack/tests/test_import.py
+++ b/scipy/fftpack/tests/test_import.py
@@ -24,10 +24,19 @@ if sys.version_info >= (3, 4):
             for path in base.rglob("*.py"):
                 if base / "fftpack" in path.parents:
                     continue
-                with path.open() as file:
-                    assert_(all(not re.fullmatch(regexp, line)
-                                for line in file),
-                            "{0} contains an import from fftpack".format(path))
+                try:
+                    with path.open() as file:
+                        assert_(all(not re.fullmatch(regexp, line)
+                                    for line in file),
+                                "{0} contains an import from fftpack".format(path))
+                except UnicodeDecodeError:
+                    # gosh darn
+                    with path.open(encoding="utf-8") as file:
+                        assert_(all(not re.fullmatch(regexp, line)
+                                    for line in file),
+                                "{0} contains an import from fftpack".format(path))

Sorry to be dumb - but don't we know the encoding of all these files in the test directory?  Or, more specifically, is it not true to say that we can assume that all the files are UTF-8 (or ASCII)?

Yes, I had thought about implementing a try: as well, but in either case we have to assume anything that's not ASCII is UTF-8 (or indefinitely extend the trys), and it feels to me like testing for the exception will be rather costlier than opening everything as UTF-8 right away (if there is any penalty at all to the latter).
As a matter of fact, all source files I could find with an encoding specified are
./scipy/io/__init__.py:# -*- encoding:utf-8 -*-
./tools/authors.py:# -*- encoding:utf-8 -*-
./tools/gh_lists.py:# -*- encoding:utf-8 -*-

and the ones in tools don't go into the library (at least they are not in Path(scipy.__file__).parent).

@dhomeier Does removing the encoding shebang from io/__init__.py fix the issue on your machine? If it does, please send a PR :-).
Author lists need to use Unicode, but the rest of the code base does not (AFAICS we don't use it anywhere and this issue is the first one we had so far).

With just removing the header line it raises the error on reading the guilty characters (which are the trademark ®s of MATLAB and IDL, so it's all evil proprietary software's fault ;-).
I don't know if there is a general scipy rule against using non-ASCII text in the Python source; otherwise you'd perhaps have to discuss with the persons in charge of io (@matthew-brett, any comments?) if it's worth just putting literal (R)s in there.
Personally I find it reasonable to treat all files as UTF-8, if in doubt (there might always come up the occasion of including personal names or other non-ASCII strings).

No objection from me for removing the trademark characters - but UTF-8 seems pretty reasonable as a default.

Yes, I had thought about implementing a try: as well, but in either case we have to assume anything that's not ASCII is UTF-8 (or indefinitely extend the trys), and it feels to me like testing for the exception will be rather costlier

In general, I don't think we should worry too much about optimum performance in tests (unless there is an actual pressing need, that is). In this particular case: The try branch is essentially cost-free. The except branch is going to be only used once as your analysis shows. Thus I don't believe there is a need to worry about performance.
Either way, I don't have a preference of whether to remove three characters from io.__init__ or to add five lines to a test (two of which should be comments :-)). Would you be interested in implementing either of these @dhomeier ? Otherwise I'd do it, does not matter to me.

Just had in mind that @rgommers had already reported the original test to be somewhat slow, but it the try: does not cost anything, all the better. I'd go for modifying the test then, because

whichever solution we pick, the convention would have to be communicated to everyone to make absolutely sure this does not happen in the future - i.e. either no python files with non-ASCII encoded are allowed in the scipy source tree at all, or .py files should always be opened with UTF-8 encoding (or at least when plain ASCII fails).

this would most closely reproduce the previous behaviour in all environments with a UTF-8 LANG setting.

For info, the "proper" way to open a source taking the encoding modeline into account is https://docs.python.org/3/library/tokenize.html?highlight=encoding#tokenize.detect_encoding
I guess I should have known that.

Good to know. So
   with tokenize.open(path.as_posix()) as file:

fixes it as well. I am only worried how the path.as_posix() will behave on Windows - tokenize.open() only accepts a file name, not a PosixPath object, but perhaps str(path) would be the better way to go?

You should just call str(path) (https://docs.python.org/3/library/pathlib.html#operators).

Of course,
Simple is better than complex.

fixed in gh-5720, closing


testkit addPlugin behavior does not match envelop's

Issue workflow progress
Progress of the issue based on the
Contributor Workflow

[ ] 1. The issue provides a
minimal reproduction available on
Stackblitz.

Please install the latest @envelop/* packages that you are using.
Please make sure the reproduction is as small as possible.

[x] 2. A failing test has been provided
[ ] 3. A local solution has been provided
[ ] 4. A pull request is pending review

Describe the bug

addPlugin behavior differs for createTestkit vs passing plugins into graphql-yoga's createYoga
To Reproduce Steps to reproduce the behavior:
import { useApolloTracing } from "@envelop/apollo-tracing";
import { handleStreamOrSingleExecutionResult } from "@envelop/core";

import { assertSingleExecutionValue, createTestkit } from "@envelop/testing";
import { makeExecutableSchema } from "@graphql-tools/schema";

const useExample = () => {
  return {
    onPluginInit({ addPlugin }) {
      addPlugin(useApolloTracing());
    },
    onExecute() {
      return {
        onExecuteDone(payload) {
          handleStreamOrSingleExecutionResult(payload, ({ result, args, setResult }) => {
            // during test, this will log without the trace
            // but during normal execution, this will log with the trace
            console.log(result);
          });
        }
      }
    },
  }
}

// JEST TEST
test("calls #track", async () => {
  const schema = makeExecutableSchema({
    typeDefs: `
      type Query {
        foo: String
      }
      `,
    resolvers: {
      Query: {
        foo: jest.fn().mockResolveValue("ok"),
      },
    },
  });
  const testInstance = createTestkit([useExample()], schema);
  const result = await testInstance.execute(`{ errors }`);
});

Expected behavior

test kit flow call order should match yoga server / envelop server.
In both cases for the example above, the result should include the trace data.
Environment:

OS:
NodeJS:
@envelop/* versions:

@envelop/core: 5.0.0
graphql-yoga: 5.1.1
envelop/testing: 7.0.0

Additional context
If instead of implementing onExecute, I use addPlugin to add the same logic, it calls in the expected order from the testkit

Hi, thank you for raising this to our attention!
I have just added a test to our testing kit, and it appears the execution order is correct in both Envelop and Testkit.
So the problem you are facing is probably not related to this.
In fact, from what I see, it's a bit strange that you are seeing traces in the the normal execution, since your plugin's hooks should be executed before useApolloTracing ones (and if I well remember, it adds the tracing in onExecuteDone too. So if it happens in normal execution, it means something else is actually putting this tracing information elsewhere. Are you sure you don't also have the tracing plugin directly in your yoga configuration?


bug fix

response size added for subscription and ingestion apis

Can one of the admins verify this patch?

ok to test


google_sign_in requires too much (unnecessary?) setup work.

I'm attempting to pull a profile avatar, and google sign in seems to be the closest I can get to that in flutter. so if this is the wrong place forgive me.
however it seems to require google-services.json file, which seems to come from firebase.
I don't want to have to manage yet another system.
google play services make no references to firebase in its setup documentation.
the plugin itself has no imports of firebase code.... all of this leads me to believe this is unnecessary for the actual signin functionality and there is a simpler way to setup the plugin without firebase.
there is also a TODO:
        // Only requests a clientId if google-services.json was present and parsed
        // by the google-services Gradle script.
        // TODO(jackson): Perhaps we should provide a mechanism to override this
        // behavior.
        int clientIdIdentifier =
            registrar
                .context()
                .getResources()
                .getIdentifier(
                    "default_web_client_id", "string", registrar.context().getPackageName());
        if (clientIdIdentifier != 0) {

tl;dr; is firebase really necessary for simple signin on android?

side note: what lead me down this path is I'm seeing an error in the logs when attempting to use this plugin:
12-30 10:33:47.606   320   320 W SignIn  : [Activity,SignInChimeraActivity] Failed to record the consent.
with no additional information, and further digging into the relevant APIs only thing I can guess is that I am missing an android oauth2 client ID.
however manually specifying the client ID in the code did nothing to resolve the error.

I'm happy to implement this feature once #25909 is addressed.

@james-lawrence do the comments in #36673 explaining on how to implement Google sign in with just a few steps and no use of Firebase answer your question?

Without additional information, we are unfortunately not sure how to resolve this issue. We are therefore reluctantly going to close this bug for now. Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.
Could everyone who still has this problem please file a new issue with the exact descriptions what happens, logs and the output of 'flutter doctor -v'  please.
All system setups can be slightly different so it's always better to open new issues and reference related issues.


Updates for Winston 3.0

Changes should be complete. Basic tests passing.

Could this PR be merged?

Ok so loggly has a fork of the transport under another name -- https://github.com/loggly/winston-loggly-bulk -- do we want to maintain this repo under winstonjs or is loggly happily maintaining their own transport now?  Would be great if someone from loggly could chime in (@Shwetajain148 ? not sure).  If the community would prefer to stick to winstonjs/winston-loggly then we can merge this PR, keep the original name, push to npm, and advise loggly/winston-loggly-bulk users to switch to winstonjs/winston-loggly.  In either case we should solve this with just one repo, not two.  Let me know what the community's preferences are -- just tell me what to do :)  Happy to merge relevant PRs or have more discussion.


Align center - time to departure

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

#206  👈
#205
main

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

Join @ksharma-xyz and the rest of your teammates on  Graphite


854 canary add multi select documentation to site

Summary of the change
Code examples for multi select
Related issue
#854

Closing as will be overwritten by work done in #929


Da Vinci Payer Data exchange: Add Implementation Guide for PDEX 0.1.8

Is your feature request related to a problem? Please describe.
Da Vinci Payer Data exchange: Add Implementation Guide for PDEX

Opened JIRA issue https://jira.hl7.org/browse/FHIR-28451


Nightly build not building ?

I just wanted to do a test run for a specific project with the latest PHP 8.4 (well, "latest" as in: build somewhere in the last 24 hours), what with so many PHP 8.4 deprecation commits going in over the last few days.
To verify which deprecation commits would be included for the test run, I checked the commit hash:
 ==> Setup PHP
✓ PHP Installed PHP 8.4.0-dev (634708a14f9546cc81bc5f9bf269ec0c46743a0f)

... which takes me to a commit from three days ago: https://github.com/php/php-src/commit/634708a14f9546cc81bc5f9bf269ec0c46743a0f which surprised me.
It may well be fine, but I figured a heads-up to check if the nightly builds are still building may be appropriate ?

Just found https://github.com/shivammathur/php-builder and I can see in the build failures in the Actions summary, so my suspicion has been confirmed.
@shivammathur I can also see that you have fixed this a couple of times in the last week already, only for things to break again the next day. Sorry PHP 8.4 is causing you so much work!

@jrfnl
Yes, recent changes have required the patches to be updated quite frequently.
It has been fixed for now.

Thank you @shivammathur!


TLS feature implementation

Integrated openssl and asio libraries.
Implemented SSL TLS support.

Test FAILed.

verify

Test FAILed.

verify

Test FAILed.

Test FAILed.

Test FAILed.

verify

Test PASSed.

Test PASSed.

Test FAILed.

Test FAILed.

Test FAILed.

Test FAILed.

Test FAILed.

Test FAILed.

Test FAILed.

Test FAILed.

Test PASSed.

Test PASSed.

Test PASSed.

Test FAILed.

verify

Test FAILed.

Test FAILed.

Test FAILed.

Test FAILed.

Test FAILed.

Test FAILed.

Test PASSed.


upgrade to the latest CM and TD features

upgrade to the latest CM and TD features. Closes #114 #113 #110 #109 #104 #94
I have:

followed the codebase contribution guide: https://clima.github.io/ClimateMachine.jl/latest/Contributing/
followed the style guide: https://clima.github.io/ClimateMachine.jl/latest/DevDocs/CodeStyle/
followed the documentation policy: https://github.com/CliMA/policies/wiki/Documentation-Policy
checked that this PR does not duplicate an open PR.

In the Content, I have included

relevant unit tests, and integration tests,
appropriate docstrings on all functions, structs, and modules, and included relevant documentation.
I have read and checked the items on the review checklist.

Thank you for all of this. And apologies you had to deal with so many API changes!

bors r+


Not working

Today one of our live app stop working, it is asking for update every time user start the app. seem like issue with Harpy server. please check

There is no Harpy server. See itunesURL method which builds the URL that is checked. You can hit the URL in the browser and inspect the result.
What is the generated iTunes URL for the app? Sometimes Apple updates this URL when you publish a new version before distributing the version.

This is URL https://itunes.apple.com/lookup?bundleId=com.caregiver.caregivelite and version is 5.6 still it is showing as pop-up

@differenz-system
We need a lot more information.

What version of Harpy does your app use?
What was the previous version of your app?
What's the current verison of your app?
What alert-type setting did you use? Force? Optional? Skip?
How often does the alert pop up? (immediately, daily, weekly)

Any sample code you can provide would be helpful.

@ArtSabintsev,
Please see my comment below.
What version of Harpy does your app use?

4.1.9
What was the previous version of your app?
5.6
What's the current version of your app?
5.7
What alert-type setting did you use? Force? Optional? Skip?
Force
How often does the alert pop up? (immediately, daily, weekly)
immediately

Thanks
Jignesh

Hey @jigneshk - sorry for taking so long to respond. Please open up a new ticket if this is a still a problem, and I'll get back to you soon.


U/pingraham/working branch

Thanks everyone.
Rather than squashing all the commits, I copied the content of this branch to a new branch called SITCOM-504, then merged that. No content changes were made on that branch. I was unable to squash all the commits (and also hesitant to do so). So we can leave this branch hanging until we're sure we don't need the history.


rename template files from *.c to *.h

This eases inclusion into VS projects since it would not cause an attempt to "compile" our templates; though the file-extension marks our templates as translation unit. This change also requires some update in our Makefile based build system; at this point we employ a special rule to explain that any change to templates/*.c files should trigger recompile of everything (like with headers). Back to VS, we currently (manually) marked all templates/*.c files to not participate as translation unit.

Completed some time ago (master revision).


Fix undef matrix variable

Follows 0dc097ff729fb91d1c08b8478c0da5603fcdcead.
Based on the most recent build, GitHub silently expand it to null, which setup-php then ignores in favour of the default, which is currently 8.3.

Thanks!


roxygen to markdown

convert Roxygen fields to markdown

Codecov Report

Merging #6 into devel will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##            devel       #6   +/-   ##
=======================================
  Coverage   74.59%   74.59%
=======================================
  Files           6        6
  Lines         122      122
=======================================
  Hits           91       91
  Misses         31       31

Impacted Files
Coverage Δ

R/sft.R
100% <ø> (ø)
:arrow_up:

R/fpr_fs.R
0% <ø> (ø)
:arrow_up:

R/selection_freqs.R
95.23% <ø> (ø)
:arrow_up:

R/extract_params.R
94.73% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Create a github action to run data_preprocessing automatically on pushed data

Need to change the json file to the same format as the csv. Remember, we shall query the dataset in this way
data[1,"MAT"] more precisely data[1,"MAT"][1]


Allow for subdirectories in snippets/ and sections/

What are you trying to accomplish with this PR?
Allow for subdirectories to be used in the snippets/ and sections/ directories by updating the core.js webpack config in slate-tools to use a separate a file-loader rule when dealing with these two directories.
The resolution order for how namespace collisions are handled is done alphabetically by directory name (with the last directory winning), and from topmost directory to bottom (with the topmost directory winning). For example:

sections/test.liquid beats sections/aaa/test.liquid
sections/zzz/test.liquid beats sections/aaa/test.liquid
sections/zzz/zzz/test.liquid beats sections/zzz/aaa/test.liquid
sections/zzz/test.liquid beats sections/zzz/zzz/test.liquid

Please provide a link to the associated GitHub issue.
https://github.com/Shopify/slate/issues/289
Checklist
For contributors:

[x] I have updated the docs to reflect these changes, if applicable. (I'm not entirely sure where this should go but I think the explanation of the resolution order should suffice)

For maintainers:

[ ] I have :tophat:'d these changes.

not totally sure what's happening here, but if anybody would be willing to give me a little insight/direction, I could start poking around and try fixing this on my own.

Should this be able to work like {% include 'collections/hero' %} or does the include still need to be written as just {% include 'hero' %}?

my preference would be for {% include 'hero' %} so that people could write snippets in a style where they initially inherit a core set of snippets and then if they want to use their own, different version of the snippet, instead of creating a snippet with a different name and then updating the reference/include everywhere in their liquid, they just create another one with the same name that overwrites the core one and is automatically used instead, similar to how something like oh-my-zsh handles custom plugins/themes.

My hope is that we can eventually reference snippets and sections with relative paths like:
{% include '../snippets/collections/hero.liquid' %}

And then on build replace the path with resolved path:
{% include 'hero' %}

This would allow us to resolve naming conflicts internally and never let the developer worry about them. For example, if we had these two includes:
{% include '../snippets/hero.liquid' %}
{% include '../snippets/collections/hero.liquid' %}

they would be resolved to the following on build:
{% include 'hero' %}
{% include 'hero2' %}

Thoughts?
This PR is moving in that direction, so I'm not opposed to the solution proposed here for now.

tbh, i'm not really that attached to this pull request since everything that it does and that I want it to do can be accomplished from within slate.config.js. As I briefly alluded to earlier, what I'm looking to accomplish is set up a base theme that comes with a core set of snippets, let's call them "snippet components, e.g, button.liquid, link.liquid, input.liquid, hero.liquid, list.liquid, option-group.liquid, etc., which are located in snippets/core/, and represent the different components used when building a store.
Then, when a developer starts building a new theme, they get all the core snippets and can use them to build out their store, but if they need a component that differs wildly from the version that core snippet component offer, they would made a snippet with the exact same name in a different directory (e.g. snippets/core/button.liquid and snippets/custom/button.liquid).
Like I mentioned, I can get all of this already with a few modifications to my slate.config.js, so it's not a huge bummer to me if this doesn't get merged in. I think the conversation about path resolution and name collisions is interesting and valuable, but not really something this PR set out to accomplish.

Going to let this one brew for a little since it's not critical and as you mentioned, it can be achieved via the Slate config.

but if they need a component that differs wildly from the version that core snippet component offer, they would made a snippet with the exact same name in a different directory (e.g. snippets/core/button.liquid and snippets/custom/button.liquid).

What's the advantage of this over just modifying the original? What you're proposing sounds like Wordpress child themes, which existed to facilitate versioning the core/parent theme.

I think the conversation about path resolution and name collisions is interesting and valuable, but not really something this PR set out to accomplish.

True. Thanks for clarifying further your goal with this PR.

@t-kelly i'm with you in that i definitely feel you should be using some sort of patch to include things as opposed to magic resolving.
Only think i'd potentially change is instead of
{% include 'hero' %}
{% include 'hero2' %}

It would be something like:
{% include 'hero' %}
{% include 'collectionshero' %}

I see "built" liquid files as slightly different to built CSS / JS. They can still somewhat be used to read and don't get obscured as much as JS / CSS so keeping it semi readable would be good imo

What's the advantage of this over just modifying the original? What you're proposing sounds like Wordpress child themes, which existed to facilitate versioning the core/parent theme. Shopify themes don't really have anything similar to this, nor does Slate?

My main motivation here was to give devs in our organization a set of building blocks written in a way that prevents from making errors and comes prebuilt with functionality already baked in. The moment people start altering the core snippet library, bad things are liable to happen. Versioning the core snippets with something like a submodule was something I was also interested in as well. However, after reading you inputs and thinking about it, I might pivot on this a bit.
Anyways, as has been mentioned a few times before, I can get what I want without this PR so feel to do whatever you'd like with it. Merge it, close it, ridicule it, worship it, whatever, I won't lose any sleep over it.

Versioning the core snippets with something like a submodule was something I was also interested in as well.

Sounds a little like https://github.com/Shopify/slate/issues/336


Revamped error handling

As mentioned by @ilanbm in #6 currently we throw for missing messages.
After some research I can think of two use cases where you want to keep the app running even if messages are missing:

You don't have the messages yet. They'll be provided by a translator later on and you'd like to have a functioning app during development. However a warning would be helpful here.
During unit tests you might want to assert for message ids to avoid hardcoding labels.

In both occasions it would be good to print the error by default, but opting out might be helpful.
What we could do, is to add an optional onError property on the provider which will allow the user to decide if and how errors should be handled. This can for example be used to turn off warnings about missing messages in unit tests.
I think errors should have the following properties:

code: An identifier that the user can detect.
message: A human readable message. This is only provided during development to reduce bundle size in production.
level: An enum with ERROR or WARN keys but which correspond to integers to be able to do checks like error.level >= NextIntlErrorCode.WARN.

Generally I can think of three categories of errors currently:

Configuration issues which will break the app (e.g. missing NextIntlProvider). This is an ERROR, but we can't use a user-defined onError in this particular example, as there's no provider.
Formatting errors which the developer has to fix (e.g. a missing value of a message). These use the WARN level, as we can render the message instead.
Missing messages which need a translator to fix. These use the WARN level and render the ID instead, as the developer might not be able to fix it.

The default onError handler should throw an error for ERROR and print a console error for WARN (only in development).
TODO:

[x] Log missing messages errors to console instead of throwing.
[x] Introduce structured error instances and configurable onError prop to cover useTranslations.
[x] Decide about an API to customize what is returned when a message is missing (e.g. <NextIntlProvider getMessageFallback={({path, error, message}) => ''} />)
[ ] Decide if we want to add error handling to useIntl functions as well. These should typically only be triggered by missing APIs (due to missing polyfills) or if the native APIs are used in an invalid way. Maybe it's ok to simply use the native error handling here as it's the developers job to fix it and there's e.g. no translator necessary.

Nice work!

You don't have the messages yet. They'll be provided by a translator later on and you'd like to have a functioning app during development. However a warning would be helpful here.
During unit tests you might want to assert for message ids to avoid hardcoding labels.

It is more than that. You have also production running apps that are connected to translation services that affect production live (like i18next with locize.com), or deployed occasionally with new locales files that were not created by developers. Its a production issue, not dev mode - hence should be warning and not error.

...add an optional onError property

Maybe you meant to it but I guess onError should also have access to returning a fallback value (could be none, could be the key)
In a lot of projects, the key is actually the English text to be translated, in others it is not.
so if it is not a separate flag (fallback: key, fallback: none) then it should be handled somehow as an option in onError

You have also production running apps that are connected to translation services that affect production live

True, good point. With next-intl you can theoretically fetch translations from a remote resource – I wasn't sure if that's a valid use case.

Maybe you meant to it but I guess onError should also have access to returning a fallback value (could be none, could be the key)
In a lot of projects, the key is actually the English text to be translated, in others it is not.
so if it is not a separate flag (fallback: key, fallback: none) then it should be handled somehow as an option in onError

Right. I was thinking about providing a useful built-in handling here, but I guess it's justified that a user might wants to customize this.
I think it might be necessary to have a separate API from onError though, as for errors that originate from other issues than non-existing messages, returning a fallback might not be useful.
I've added a bullet above. My first API draft is:
<NextIntlProvider getMessageFallback={({path}) => ''} />

By using a function we can provide as much context as we have and the user can decide case-by-case what fallback should be used.
Does that look reasonable to you?

yep, seems legit

@ilanbm I've just released the discussed error handling capabilities in 0.3. Let me know if it works as expected for you!

@amannn Nice work!


Improve query performance of the generated "tables"

What is the problem?
There ware a lot of the queries that consumes a lot of time. And this is on a small set of data. The query performance needs to be improved before doing benchmarks. Here are some possible options:

If there is no update

Create a table of the result of the last query in data_prep.sql

If there are some updates

Explore possibility of using materialized views
Use a simple function to decided the amount of time that a specific word is present

This is not an issue any more. Materialized a lot of the things to make it work guick


Testing improvements (unit, integration)

The repository currently has a fairly limited set of tests in place despite CI making use of go test to run the implemented unit tests.
Additional unit tests would provide value to packages in helping quickly identify failures in areas of the code base following contributions. There is a PR adding some tests for the currently implemented feeds at https://github.com/ossf/package-feeds/pull/76.
As for other testing, do people see value in adding more integration style tests in place to test the application in CI in binary form? Testing could use the stdout publisher to log packages and be verified afterwards, some mock feed configuration would need to be used like a localhost service with a pre-defined response.

It would be nice to see some form of E2E used for testing here, potentially integrating https://github.com/ossf/package-analysis in a contained environment.


cas-527 updated error messages and handling

•updates error messages by creating controller level constants as discussed with German, the heading and body message are separated by double colons for easy parsing in the client

I am wondering if we can use this ticket to implement some best practices in our error handling. Some suggestions I have:

Let's make our error codes follow a standard like ERR_1000, ERR_1001, etc. This keeps all error codes the same format/length and are easily readable.

Can we create an ErrorCode struct that we return as JSON with the following format:

type ErrorResponse struct {
  code        string
  message string
  details     string
}

The message is what can be used as the title of the modal, and the details used as the body of the modal. Can we just use JSON instead of a custom format with delimiters?

Can we define friendly constants for the errors in our code? eg. ErrIncompleteRequest, ErrCreateCommunity, ErrFetchBalance, etc. I am concerned that using the error codes as variable names makes the code less readable.

If we don't want to go with the ErrorCode struct, can we declare the above variables as errors.New() or perhaps better fmt.Errorf() so we can just pass them straight to respondWithError without having to call errors.New() every time? I would like to see something like respondWithError(w, Status, ErrIncompleteRequest.Error())

One thing I saw in a few blog posts is recommending the use of fmt.Errorf() over errors.New() (e.g. this post). Could we adopt that as a standard for our code?

thanks for this feedback! The format of ERR001::header::body was only decided upon as @germanurrus asked for me to implement it this way so that he can easily parse it on the front end.

Yes happy to use this format for the constants.

I'm up for either JSON or using fmt.Errorf(), perhaps we to use fmt.Errorf() as I think the front end code to parse ERR001::header::body this format have already been written? Unless we would all prefer JSON. I think I actually don't mind either one.

Yes.

Yes, that's a good idea.

Yes

@rvmelkonian @jbluks I don't have any hard feelings with using a JSON format. I'm using a function to parse the string, but if that becomes a JSON that can be easily updated: https://github.com/DapperCollectives/CAST/pull/513/files#diff-96d40116d41a7df3efad28fc0649d0596486ab914aa726596521fbec0a19ce5dR16

@rvmelkonian This should be targetting release-v1.5.0


bug: slimline freezes nvim when closing buffers

The following keymap causes nvim to freeze on occasion - completely unresponsive:
vim.keymap.set("n", "<leader>bo", "<cmd>%bd|e#|bd#<cr>", { desc = "Delete Other Buffers" })

Sadly I'm not able to reproduce consistently, but maybe you have an idea why?
Slimline itself contains the render function, instead of show its UI:
require('slimline').render()

Sorry I can't give more info 😞

Hey,
thanks for reporting an issue.
I tried reproducing that by using your keymap and with several open buffers. It works fine for me.
Does it happen every time?
Does it also happen when disabling slimline?

Hey, thanks for reporting an issue.
I tried reproducing that by using your keymap and with several open buffers. It works fine for me. Does it happen every time?
Does it also happen when disabling slimline?

Sorry, I missed your comment in my notifications! It doesn't happen consistently, but it has been happening more frequently... I am able :q though now.
I think it may be a race condition with rendering, it seems to happen more when I'm moving fast and things that should show up in slimline change due to a keymap or plugin, like filetype and diagnostics.
When I get more conclusive information I will add another comment.

Hey @sschleemilch, I'm going to close this. I have been using slimline for a few months and I've not had it happen again.

Good to know. Thanks!


Cookiecutter template updating

Automatic update option

Delayed after initialization (may need to adjust those delays)
Check for update command
Update template command

Reduce code duplication in CookiecutterViewModel

Enum variables instead of multiple bool variables for state
Pass down the Redirector so that writing to output is immediate (especially good for when generating files), reduces client code needed to print to output, and simplifies the APIs that don't need to return captured output

Some non integration tests enabled, will add more over time.

:shipit:


Icons not showing up on Android with Expo

🐛 Bug Report
Using Expo and Icons are not being displayed on Android.
On web they display fine.
Using the following versions:
ui-kitten/components: 5.1.2
ui-kitten/eva-icons: 5.1.2
react-native-svg: 12.3.0
I have also tried react-native-svg with the following versions:
13.4.0
13.6.0
Any suggestions would be hugely appreciated.
Thanks!
To Reproduce
Steps to reproduce the behavior:
Expected behavior

Link to runnable example or repository (highly encouraged)

UI Kitten and Eva version

Package
Version

@eva-design/eva

@ui-kitten/components

Environment information

@juliantreweeke can you share the test project? Because it seems working for me.
(Also, please make sure you specified all necessary props for the component)


Some field values missing formatting

Seems to have occurred since 2.2.0.
In the screenshot it happens in the surface field, however I've seen it in other field as well.

The values shown in blue, variable-spaced font and title-cased are the ones explicitly listed for translation, although translations aren’t getting pulled in yet: #8600. The monospaced font is intended to emphasize that the other values are raw values that haven’t been manually curated but were instead pulled in from taginfo based on frequency in the database.
https://github.com/openstreetmap/id-tagging-schema/blob/e8d86eb0bdbad8e466a6e06a62899f422440175a/data/fields/surface.json#L6-L19

@mbrzakovic have you closed this issue because it has been or will be fixed?
Because I also noticed the opening hours field with a monospaced font for its text.

That’s intentional: the Opening Hours field accepts a raw value rather than a translatable one. The use of monospaced font in fields is new in v2.20.0.

1ec5 gave correct explanation. Shortly: What you are seeing is a feature, not an issue.

Hmm. What's the need for this feature? Does an end user need to know whether a value is translatable or not?
In other fields like buildings the monospaced font is used for the entire set of values in the dropdown. Was this change to add worse looking text discussed anywhere on here?

Sorry for not providing more context earlier. Please take a look at following: https://github.com/openstreetmap/iD/pull/8238, https://github.com/openstreetmap/iD/issues/2708

Thanks - my next question is where can people contribute to these translations and is it publicised anywhere so that users who see the monospaced font can go and help with the translations? 😉

https://github.com/openstreetmap/iD/blob/develop/CONTRIBUTING.md#translating. What should be of interest to you is 'Presets' translations that would be pulled in https://github.com/openstreetmap/id-tagging-schema


Group notification icon color option

May you please add an option to set the group notification icon color to white? The tiny red icon is slightly unpleasing to look at while every other tiny icon is always white. Just my two cents. Thank you for your time!

On different devices and versions of android, the icon may be different.
Can you provide screenshot and phone model?

On different devices and versions of android, the icon may be different. Can you provide screenshot and phone model?

Yes, here you are

Fixed in the latest app release v2.53.1 (rollout started). This icon is now white.


WIP - md-* helpers

Addresses #67
New proposed helpers
{{md-badge}}
{{md-btn-submit}}
{{md-btn}}
{{md-card-action}}
{{md-card-collapsible}}
{{md-card-content}}
{{md-card-panel}}
{{md-card-reveal}}
{{md-card}}
{{md-check}}
{{md-checks}}
{{md-collapsible}}
{{md-copyright}}
{{md-input-date}}
{{md-input-field}}
{{md-input}}
{{md-loader}}
{{md-navbar}}
{{md-pagination}}
{{md-parallax}}
{{md-radio}}
{{md-radios}}
{{md-range}}
{{md-select}}
{{md-switch}}
{{md-switches}}
{{md-tab}}
{{md-tabs}}
{{md-textarea}}

Nice! ember-try has now detected that we still have computed properties using the old syntax.

I will go through and see if I can address those too

Ok, this is ready for review/merge.

Well done.

Can you add modal, then i will merge

This should be ready to go now. One of our dependencies is not canary-friendly so I changed our build configuration to allow test failures against that ember-try scenario.


[YouTube] Discussions post and comments extraction

Checklist

[X] I'm reporting a site feature request
[X] I've verified that I'm running yt-dlp version 2022.05.18 (update instructions) or later (specify commit)
[X] I've checked that all provided URLs are playable in a browser with the same IP and same login details
[X] I've searched the bugtracker for similar issues including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue
[X] I've read about sharing account credentials and I'm willing to share it if required

Region
Southern California, USA
Example URLs
https://www.youtube.com/c/TheGreatUnknownProductions/community
https://www.youtube.com/channel/UCgP9fheyDumxpk_35IgB3bw/community
Description
Community posts are text, links to videos, images, polls, and comments on youtube. Although it may be out-of-scope, you should add support for downloading community posts, their metadata, and their comments.
Verbose log
not done yet

Although it may be out-of-scope, you should add support for downloading community posts, their metadata, and their comments.

No


add note about not invalidating valid and available blocks

This came up on the call today as a path that is not entirely clear in the spec.
I think that this note is either appropriate here (before is_data_available()) or embedded as a comment in on_block() around the call to is_data_available(). Open to thoughts on how to make sure we are abundantly clear here.

okay, the warning is now in both places and makes a note about these being in addition to the expected/referenced blobs


Map: Highlight auto-target

Like this. This is the one functionality that TB is missing that prevents me from not using the default compass.

Added for next release, https://github.com/HasKha/GWToolboxpp/commit/527c20397e0e70224602b3376271a735da3da626


[fix]list[BatchEncoding] typehint error

def call(self, features) -> list[BatchEncoding]: TypeError: 'type' object is not subscriptable
cannot work in python3.8
change into List[BatchEncoding]
Now it work in python3.8

https://github.com/FlagOpen/FlagEmbedding/issues/1299


Add SuperGATConv

I added SuperGAT, which will be presented at ICLR 2021. (Kim and Oh, How to Find Your Friendly Neighborhood: Graph Attention Design with Self-Supervision)
One thing I want to consult is TorchScript support. The current implementation contains methods that do not support TorchScript (such as negative_sampling, dropout_adj), thus I separate and wrap them with @torch.jit.ignore. This is my first time using TorchScript, and I am not sure this is appropriate in PyTorch Geometric.
Thanks in advance.

Thanks and congratulations to your paper acceptance :)
This looks super good already. Please don't worry about TorchScript support, I will make it work (probably after ICML deadline, sorry for the delay).

Thanks and congratulations to your paper acceptance :)
This looks super good already. Please don't worry about TorchScript support, I will make it work (probably after ICML deadline, sorry for the delay).

Thank you! It couldn't be done without PyTorch Geometric.
And also good luck with your submission.

Thank you! It couldn't be done without PyTorch Geometric.
And also good luck with your submission.

Thanks once again for this PR! It's always a pleasure to see PyG utilized so well :)
I really like SuperGAT and the idea of guiding attention via self-supervision is really clever. Results are pretty good, too. Congratz!
I made a pass through the PR and modified the following things:

Moved SuperGAT into its own example.
Reformulated attention loss computation: This method does now return the attention loss for a single layer. I think this is more intuitive.
Made same things more efficient (e.g., separting att into att_l and att_r to avoid the usage of torch.cat).

I will look into JIT compatibility later, as this is not critically for merging.

Thank you, it really looks good to me.
I always learn something when I make a pull request to PyG.
Also, I made some small improvements in examples/super_gat.py with a new pull request.

made Net use x and edge_index in a local scope (like examples/gat.py)
changed a hyperparameter.


Weird results when applying SemGCN to 2D pose from image

Inference on images in the wild using SemGCN has been partially covered in this thread and others, but only the overall process has been made clear. I.e.:

Step 1: Use a 2D pose estimation network to generate 2D pose in MPII format.
Step 2: Convert 2D pose from MPII format to H36M format as done here.
Step 3: Pre-process the 2D input pose as done here.
Step 4: Use the pre-processed 2D pose in H36M format as input to the SemGCN SH model. It outputs 3D pose in H36M format.

Below i will follow each step, using the test image of size 300x600 to the left.

For Step 1, i use EfficientPose to generate the MPII format 2d pose of the test image as shown above on the right, here's the numeric output:
positions = [[[108. 512.]	# Right ankle
              [114. 428.]	# Right knee
              [124. 320.]	# Right hip
              [186. 324.]	# Left hip
              [178. 426.]	# Left knee
              [176. 512.]	# Left ankle
              [156. 322.]	# Pelvis
              [162. 152.]	# Thorax
              [164. 114.]	# Upper neck
              [166.  24.]	# Head top
              [ 60. 322.]	# Right wrist
              [ 78. 238.]	# Right elbow
              [ 96. 148.]	# Right shoulder
              [230. 154.]	# Left shoulder
              [240. 246.]	# Left elbow
              [224. 326.]]]	# Left wrist

For Step 2, i run this:
positions = positions[:, SH_TO_GT_PERM, :]
To get the output:
positions = [[[156. 322.]
              [124. 320.]
              [114. 428.]
              [108. 512.]
              [186. 324.]
              [178. 426.]
              [176. 512.]
              [162. 152.]
              [164. 114.]
              [166.  24.]
              [230. 154.]
              [240. 246.]
              [224. 326.]
              [ 96. 148.]
              [ 78. 238.]
              [ 60. 322.]]]

For Step 3, i run this:
positions[..., :2] = normalize_screen_coordinates(positions[..., :2], w=300, h=600)
To get the output:
positions = [[[ 0.0399  0.1466 ]
              [-0.1733  0.1333 ]
              [-0.2400  0.8533 ]
              [-0.2799  1.4133 ]
              [ 0.2400  0.1600 ]
              [ 0.1866  0.8399 ]
              [ 0.1733  1.4133 ]
              [ 0.0800 -0.9866 ]
              [ 0.0933 -1.2400 ]
              [ 0.1066 -1.8400 ]
              [ 0.5333 -0.9733 ]
              [ 0.6000 -0.3600 ]
              [ 0.4933  0.1733 ]
              [-0.3600 -1.0133 ]
              [-0.4800 -0.4133 ]
              [-0.6000  0.1466 ]]]

For Step 4, the above is used as input to the SemGCN SH model running this:
inputs_2d = torch.from_numpy(positions)
inputs_2d = inputs_2d.to(device)
outputs_3d = model_pos(inputs_2d).cpu()
outputs = outputs_3d[:, :, :] - outputs_3d[:, :1, :]

Which gives the output:
outputs = [[[ 0.0000  0.0000  0.0000 ]
            [-0.0769 -0.6899 -0.2520 ]
            [ 0.0847 -0.4062 -0.0607 ]
            [ 0.4154  0.2318  0.4062 ]
            [ 0.2708 -0.5181 -0.0504 ]
            [ 0.3431 -0.7337  0.3018 ]
            [ 0.6379  0.6684  0.2033 ]
            [ 0.1650 -0.9141 -0.8496 ]
            [ 0.5825 -2.1341  0.2762 ]
            [ 1.1561 -1.5364 -0.6433 ]
            [ 1.1612 -1.1453 -0.2103 ]
            [ 0.9097 -0.6763  0.2361 ]
            [ 0.8202 -0.2971  0.2679 ]
            [ 0.8008 -1.1936 -0.1120 ]
            [ 0.2124 -1.3246  0.5563 ]
            [ 0.5093 -0.4762  0.3473 ]]]

When visualized this looks completely wrong... See image below. Can anyone highlight on where the problem lies? Is it a problem with the pre-processing, or with the model?

@duckduck-sys I think there are two points to note about the data:

location: the neck should be halfway between the shoulders, and the thorax should be roughly halfway between the neck and the hips.
scale: normalization depends on the image width(mapping to [-1,1] based on the w), thus, the proportion of human body in the image needs to match H36M.

raw output

after scaling the locations

after modifying the location of the neck and the thorax

@duckduck-sys I think there are two points to note about the data:

location: the neck should be halfway between the shoulders, and the thorax should be roughly halfway between the neck and the hips.
scale: normalization depends on the image width(mapping to [-1,1] based on the w), thus, the proportion of human body in the image needs to match H36M.

raw output

after scaling the locations

after modifying the location of the neck and the thorax

hi, how do you calculate the spine point

hi @duckduck-sys
大神，你的数据归一化后有点奇怪，还有我想请教下您现在能正确回归出3d pose了吗，主要是hip和spine节点我不懂计算，还有就是hip节点要假定为(0,0)吗

@develduan Hi Duan, can you share this solution? I'm also facing somewhat same problem.
Thanks

@develduan Hi. I also face the same problem  about how to figure out the spine point, because the stack-hourglass doesn't output the spine point

@lisa676 @dandingol03  Hi, I'm sorry that I stopped following this project because it didn't work very well on my dataset(the wild environment). In my dataset, all pedestrians stand upright, so I simply treated the midpoint of the neck and the pelvis as the thorax/spine: positions_mpii[i_thorax] = (positions_mpii[i_neck] + positions_mpii[i_pelvis]) / 2 . After normalize_screen_coordinates, scale the locations with a factor to fit the proportion of human body in the image of H36M, in my case: positions = positions / 2.
In my case, I want to get the 3D posture directly from the image instead of getting a 2D posture and then a 3D posture,  and I got a better result by following this paper "Angjoo Kanazawa, Michael J. Black, David W. Jacobs, Jitendra Malik. End-to-end Recovery of Human Shape and Pose".

@develduan  Firstly, thanks for your kindly apply. Secondly, the paper " End-to-end Recovery of Human Shape and Pose" is cool, i will delve into the paper soon. And last, here is my email<EMAIL_ADDRESS>maybe someday we can exchange idea about 3d pose estimation~