go-jsonnet: 0.16.0 -> 0.17.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/google/go-jsonnet/releases.
meta.description for go-jsonnet is: "An implementation of Jsonnet in pure Go"
meta.homepage for go-jsonnet is: "https://github.com/google/go-jsonnet"
meta.changelog for go-jsonnet is: ""
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 0.17.0 with grep in /nix/store/dv6g7cqgndi8b4wr7d5qszzcazihsh73-go-jsonnet-0.17.0

directory tree listing: https://gist.github.com/ecc64ec1cc2931839521258e16bb7525

du listing: https://gist.github.com/1018d5c87088c4df6da21997116e6991

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
go-jsonnet

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/dv6g7cqgndi8b4wr7d5qszzcazihsh73-go-jsonnet-0.17.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A go-jsonnet https://github.com/r-ryantm/nixpkgs/archive/d9768fece18bcefc63a3534d23050cc5cb958786.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/dv6g7cqgndi8b4wr7d5qszzcazihsh73-go-jsonnet-0.17.0
ls -la /nix/store/dv6g7cqgndi8b4wr7d5qszzcazihsh73-go-jsonnet-0.17.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review 1

1 package built:

go-jsonnet

Maintainer pings
cc @nshalman @kalbasit for testing.

Result of nixpkgs-review pr 104978 run on x86_64-darwin 1

1 package built:

go-jsonnet


Pluralsight HTTPError

Please follow the guide below

You will be asked some questions and requested to provide some information, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your issue (like this: [x])
Use the Preview tab to see what your issue will actually look like

Make sure you are using the latest version: run youtube-dl --version and ensure your version is 2018.12.09. If it's not, read this FAQ entry and update. Issues with outdated version will be rejected.

[ X ] I've verified and I assure that I'm running youtube-dl 2018.12.09

Before submitting an issue make sure you have:

[ X ] At least skimmed through the README, most notably the FAQ and BUGS sections
[ X ] Searched the bugtracker for similar issues including closed ones
[ X ] Checked that provided video/audio/playlist URLs (if any) are alive and playable in a browser

What is the purpose of your issue?

[ X ] Bug report (encountered problems with youtube-dl)
[ ] Site support request (request for adding support for a new site)
[ ] Feature request (request for a new functionality)
[ ] Question
[ ] Other

The following sections concretize particular purposed issues, you can erase any section (the contents between triple ---) not applicable to your issue

If the purpose of this issue is a bug report, site support request or you are not completely sure provide the full verbose output as follows:
Add the -v flag to your command line you run youtube-dl with (youtube-dl -v <your command line>), copy the whole output and insert it here. It should look similar to one below (replace it with your log inserted between triple ```):
youtube-dl.exe --username PRIVATE --password PRIVATE https://app.pluralsight.com/library/courses/sccm-current-branch-deploy-manage-applications/table-of-contents -o "C:/temp/Pluralsight/%(playlist)s/%(chapter_number)02d - %(chapter)s/%(playlist_index)02d - %(title)s.%(ext)s"  --sleep-interval 35 --max-sleep-interval 120 --sub-lang en --sub-format srt --write-sub --verbose
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['--username', 'PRIVATE', '--password', 'PRIVATE', 'https://app.pluralsight.com/library/courses/sccm-current-branch-deploy-manage-applications/table-of-contents', '-o', 'C:/temp/Pluralsight/%(playlist)s/%(chapter_number)02d - %(chapter)s/%(playlist_index)02d - %(title)s.%(ext)s', '--sleep-interval', '35', '--max-sleep-interval', '120', '--sub-lang', 'en', '--sub-format', 'srt', '--write-sub', '--verbose']
[debug] Encodings: locale cp1252, fs mbcs, out cp850, pref cp1252
[debug] youtube-dl version 2018.12.09
[debug] Python version 3.4.4 (CPython) - Windows-10-10.0.17134
[debug] exe versions: none
[debug] Proxy map: {}
[pluralsight:course] sccm-current-branch-deploy-manage-applications: Downloading JSON metadata
[pluralsight:course] sccm-current-branch-deploy-manage-applications: Downloading JSON metadata
ERROR: Unable to download JSON metadata: HTTP Error 403: Forbidden (caused by HTTPError()); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpg8efod20\build\youtube_dl\extractor\common.py", line 605, in _request_webpage
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpg8efod20\build\youtube_dl\YoutubeDL.py", line 2212, in urlopen
  File "C:\Python\Python34\lib\urllib\request.py", line 470, in open
  File "C:\Python\Python34\lib\urllib\request.py", line 580, in http_response
  File "C:\Python\Python34\lib\urllib\request.py", line 508, in error
  File "C:\Python\Python34\lib\urllib\request.py", line 442, in _call_chain
  File "C:\Python\Python34\lib\urllib\request.py", line 588, in http_error_default

...
<end of log>

Description of your issue, suggested solution and other information
Explanation of your issue in arbitrary form goes here. Please make sure the description is worded well enough to be understood. Provide as much context and examples as possible.
If work on your issue requires account credentials please provide them or explain how one can obtain them.

@dstftw Duplicate of what?
I found a few bug reports but different line-errors.

Found a workaround:
I was still able to watch it via the Pluralsight website on my own IP but not able to download via youtube-dl
Switched to the wifi of my neighthours and i was able to download them again.
So change your IP-address or connection. Looks like an IP-softban.

@TerrorSource ThankYou very much ! It's working with another wifi or network :-)


feat(number): add wrap utility

See wrap
Returns a number whose value is limited to the given range, just like clamp.
The difference is that clamp does return the lower or upper limit if
the value is outside the range. Instead, wrap returns the value wrapped
around the range.
https://lovetoknow.github.io/love-utils-js/mathUtils.js.html

The snippet is now available at https://1loc.dev/number/wrap-a-number-between-two-values/
Thanks you, @iamandrewluca 👍


0.9.6-rc1 deletes .tsm files before closing file descriptor

This might be jumping the gun a little, but I noticed strange / conflicting values from df and du on my 0.9.6-rc1 system:
$ df -h /srv
Filesystem      Size  Used Avail Use% Mounted on
/dev/md0        738G   26G  676G   4% /srv

$ sudo du -skh /srv
3.0G	/srv

If I restart InfluxDB, the used space reported by df then lines up with du. Digging deeper, it appears that the influxd process has file descriptors to non-existent files:
$ sudo lsof -c influxd -a -d DEL
COMMAND   PID     USER  FD   TYPE DEVICE SIZE/OFF     NODE NAME
influxd 13214 influxdb DEL    REG    9,0          35520616 /srv/influxdb/data/perfdb/default/2/000000180-000000003.tsm
influxd 13214 influxdb DEL    REG    9,0          35520613 /srv/influxdb/data/perfdb/default/2/000000178-000000003.tsm
influxd 13214 influxdb DEL    REG    9,0          35520618 /srv/influxdb/data/perfdb/default/2/000000182-000000002.tsm
influxd 13214 influxdb DEL    REG    9,0          35520617 /srv/influxdb/data/perfdb/default/2/000000181-000000002.tsm
influxd 13214 influxdb DEL    REG    9,0          35520612 /srv/influxdb/data/perfdb/default/2/000000178-000000002.tsm
...

I suspect that InfluxDB is unlinking these files before closing the FD. Peeking inside /proc/$(pidof influxd)/fd however, there are only descriptors to legitimate files / sockets. I have to admit, I've never seen this behaviour before, but my gut feeling is that the ext4 superblock "free block count" is not being updated as a result of these orphaned FDs - hence the disagreement between df and du. And I'm pretty sure I know what will happen when ext4 says there are no free blocks left...

@jwilder

I'll take a look.  The code should be closing before deleting any TSM files.  It's done here: https://github.com/influxdb/influxdb/blob/master/tsdb/engine/tsm1/file_store.go#L346-L352, but possibly something else is going on.

@dswarbrick Fix for this should be in the next nightly/RC build.  Thanks!

@jwilder awesome! I'll check it out tomorrow morning. Thanks for the quick resolution!


added hashes generated from cargo-leptos

This is accompanying PR for https://github.com/leptos-rs/cargo-leptos/pull/256

Overall this looks pretty good, my question would be what would happen if you were not using cargo-leptos? We still want to maintain compatibility with that use case

I believe that shouldn't be a problem. The server code looks if the hash.txt exists and only if it does adds the hashes to the file names.

The failing check doesn't seem to be from my code

Any way this gets backported to leptos 6?

This was done for Leptos 0.6 👍🏼


add woff2 generation

Most modern browsers support WOFF2 font format (see here). This PR adds code to generate .woff2 files and adds generated files to /dist.

@BendingBender Published to npm in version 1.2.0. Thanks again for your contribution.


Update pos _tag_transformers function

What does this changes
update pos_tag_transformers function by clean up the code, add docstring, fix deprecation, and change the output format of the function to make it be the same format as other tagger in PyThaiNLP
What was wrong
in #857 , pos_tag_transformers was added which consist of 3 models, however, to call and engine, the full name of it must be specified, also the output still not the same format as another tagger. For example
pos_tag_transformers(words="แมวทำอะไรตอนห้าโมงเช้า", engine = "bert-base-th-cased-blackboard")
# outputs
# [{'entity_group': 'NN', 'score': 0.910759, 'word': 'แมวมา', 'start': 0, 'end': 5},
#  {'entity_group': 'VV', 'score': 0.9462489, 'word': '##ทำ', 'start': 5,  'end': 7},
# {'entity_group': 'NN', 'score': 0.8325567, 'word': '##อะไรตอนห้าโมงเช้า',  'start': 7, 'end': 24}]

which is very hard for the normal user to remember its entire name, and may result in more mess in the internal code if another transformers model trained on new corpus are added. we will end up with a lot of if-else condition in order to call a model in the future
How this fixes it
i've cleaned up the code to let a user call a model with parameters named engine and corpus same as what we have from the former function that is pos_tag and pos_tag_sents and also fix output format. This will reduce how hard to remember the entire model name. Here is the newly added version:
from pythainlp.tag import pos_tag_transformers
txt = pos_tag_transformers(sentence="แมวทำอะไรตอนห้าโมงเช้า", engine="mdeberta", corpus='pud')
# outputs
# [[('แมว', 'NOUN'), ('ทําอะไร', 'VERB'), ('ตอนห้าโมงเช้า', 'NOUN')]]

Your checklist for this pull request
🚨Please review the guidelines for contributing to this repository.

[ ] Passed code styles and structures
[ ] Passed code linting checks and unit test

Hello @pavaris-pm! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file pythainlp/tag/pos_tag.py:

Line 183:19: W291 trailing whitespace
Line 186:2: E225 missing whitespace around operator
Line 193:101: E501 line too long (135 > 100 characters)
Line 194:101: E501 line too long (122 > 100 characters)
Line 196:101: E501 line too long (140 > 100 characters)
Line 226:15: E203 whitespace before ':'
Line 230:24: E203 whitespace before ':'
Line 231:19: E203 whitespace before ':'
Line 249:101: E501 line too long (107 > 100 characters)
Line 253:21: W292 no newline at end of file

In the file tests/test_tag.py:

Line 378:80: W291 trailing whitespace
Line 379:63: W292 no newline at end of file


Document Attestation in SCS

Thanks for contributing to the Harness Developer Hub! Our code owners will review your submission.
Description

Please describe your changes: __________________________________
Jira/GitHub Issue numbers (if any): ______________________________
Preview links/images (Internal contributors only): __________________

PR lifecycle
We aim to merge PRs within one week or less, but delays happen sometimes.
If your PR is open longer than two weeks without any human activity, please tag a code owner in a comment.
PRs must meet these requirements to be merged:

[ ] Successful preview build.
[ ] Code owner review.
[ ] No merge conflicts.
[ ] Release notes/new features docs: Feature/version released to at least one prod environment.

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

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


Clarification of Write consistency wrt Cassandra

Many customers assume we support full consistency range - we provide mapping. We also do not allow to change consistency on writes on individual request basis

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

#sign-off


Interp vectorize

[ ] Closes #9049
[ ] Adds support for vectorized (broadcast) 1d interpolation using SciPy interpolants, including "akima" and "makima"
[ ] Does not add support for deprecated SplineInterpolator (but upholds preexisting functionality). I wanted to add a deprecation warning but this caused tests to fail so I left it commented.
[ ] Akima and makima cases added to test_interp.py::test_interpolate_vectorize

Something has gone kinda wrong with git here! Maybe try squashing to a single commit?

Something has gone kinda wrong with git here! Maybe try squashing to a single commit?

yes, done, thanks!

Sounds good! I actually wanted it to be a "draft PR" as I'm still double-checking it, though perhaps submitting it this way is confusing on the maintainers' end and I should rescind until it's ready.

though perhaps submitting it this way is confusing on the maintainers' end and I should rescind until it's ready

we're actually happy to have PRs developed like this, it allows us to guide people more easily in case there's any issues. This includes advising in case the direction is seriously wrong (which I don't think it is in this case, but I also don't know this area too well)

(fyi we squash on merge, so you needn't squash every change)

Thanks @hollymandel !


artifactory_manager::space_used does not count the space taken by directories

artifactory_manager::space_used does not count the space taken by directories.  This does not amount to much of a difference now, because there are only two directories.
After the the artifact manager is modified to allow it to scale to hundreds of millions of artifacts, there will be many directories and this discrepancy will be significant.

No longer seems relevant
//cc @MitaliBo


500 error on writing data out of policy range

Writing data outside of policy range should result in a 4xx error that the client can understand not to retry sending the data. It's expected behavior that 5xx errors received by clients should result in the client re-transmitting the same data to avoid data loss.
This issue was raised by a customer here https://github.com/influxdata/telegraf/issues/8571
Steps to reproduce:
I've configured a bucket with a retention policy of 2 weeks. When I write some measurements that are older than those two weeks, influxdb response with an 500 error.

setup influxdb v2
create bucket with a retention policy of N weeks
send some data to this bucket that is older than N weeks. E.g. via curl.

Expected behavior:
server responds with an error indicating client error, eg 4xx. such as. 406 Not Acceptable  or 422 Unprocessable Entity
Actual behavior:
Server responds with 500 Internal Server Error
Environment info:

InfluxDB version: 2.x

Logs:
see logs from https://github.com/influxdata/telegraf/issues/8571

Added @danxmoran for tracking what we'll need to add for OSS.

this is the set of default errors allowed by the swagger definition enum:             - internal error             - not found             - conflict             - invalid             - unprocessable entity             - empty value             - unavailable             - forbidden             - too many requests             - unauthorized             - method not allowed
422: Unprocessable Entity should be used rather that 406: unacceptable, as unacceptable is not on our list

@StacieClark do we have any timeline for this?

I'm looking at it today. I'll let you know when I know what the fix is

I configured a bucket to have a 1 hr retention policy.
`curl -i -XPOST 'http://localhost:8080/api/v2/write?org=dev&bucket=1hr&precision=s' --header "Authorization: Token $INFLUX_TOKEN" --data-raw "note mod=13 1234567"
HTTP/1.1 204 No Content
Date: Tue, 22 Dec 2020 15:31:45 GMT
Server: Caddy
`
The content does not get inserted. No timestamp or a timestamp within the hour do get inserted.
So this is incorrect as well.

Looks like an OSS isse

why are you getting Server: Caddy in the response? seems like you're not getting a response from the right server.

That is local cluster. From an AWS cluster:
curl -i -XPOST<EMAIL_ADDRESS>--header "Authorization: Token $INFLUX_TOKEN" --data-raw "note mod=15 12345"
HTTP/2 204
date: Mon, 04 Jan 2021 19:29:57 GMT
strict-transport-security: max-age=15724800; includeSubDomains

That is local cluster. From an AWS cluster:
curl -i -XPOST<EMAIL_ADDRESS>--header "Authorization: Token $INFLUX_TOKEN" --data-raw "note mod=15 12345"
HTTP/2 204
date: Mon, 04 Jan 2021 19:29:57 GMT
strict-transport-security: max-age=15724800; includeSubDomains

Is this an OSS issue and not cloud?

Is this an OSS issue and not cloud?

I can confirm this is a problem on OSS master, I can prioritize working on a fix for the upcoming 2.0.4 release. I'm unclear about the desired behavior change, though: do we want OSS to match cloud and return a 204, or do its own thing and return some 4xx code? My main concern about returning a 4xx is that users might think all of their data was rejected, but in reality any of the points that fell inside the RP will have been accepted & stored.

I can confirm this is a problem on OSS master, I can prioritize working on a fix for the upcoming 2.0.4 release. I'm unclear about the desired behavior change, though: do we want OSS to match cloud and return a 204, or do its own thing and return some 4xx code? My main concern about returning a 4xx is that users might think all of their data was rejected, but in reality any of the points that fell inside the RP will have been accepted & stored.

@danxmoran In general, we should always be staying in sync with cloud.  We can have a deeper discussion if there are aspects that aren't applicable to one or the other.

@danxmoran In general, we should always be staying in sync with cloud.  We can have a deeper discussion if there are aspects that aren't applicable to one or the other.


Error using frameworks compiled with Java 8 to test pure java projects

Hi,
I have an Android project with a pure java (i.e. not Android) project dependency. I'm using AssertJ, version 3 of which is compiled using Java 8, for unit tests. I have all the relevant JAVA*_HOME variables set, and gradle is running using Java 8.
What I observe:

I can run the unit tests for the Android project just fine from both Android Studio and the command line.
The unit tests for the library project run fine from Android Studio.
The unit tests for the library project fail when I run them from the command line with java.lang.UnsupportedClassVersionError: org/assertj/core/api/Assertions : Unsupported major.minor version 52.0.

I have an example project here. For me, running ./gradlew lib:test will induce the failure.
Can you provide any advice? I've already taken all the steps suggested in other issues which mention this error (e.g. #133).
Great work on this project btw.

I have this same issue. Did you figure anything out?

@Arnesen Unfortunately not, although I haven't had a chance to look at this for a while.

Unsupported major.minor version 52.0 usually indicates that whatever you're trying to run there needs Java 8 and you're not running it with Java 8.

I just ran into this exact issue.


ParallelDOM: New high level API for descriptive text

When an accordian box contains a complex node that isn't available in the pdom, we should be able to put a descriptive paragraph there in the pdom - similar to the way alt-text is used for images.

Sounds great. The issue has been transferred and I updated the title to reflect this idea.

I think we need to approach how we refer to this kind of description (essentially a Static State description) differently, and understand that the description may need more structure than just a paragraph. See Molecules and Light's Light Spectrum Diagram as a good example. This diagram is implemented in an non-modal dialog, but it could exist in an accordion box, or in a modal dialog.

I think we could be general and just call it a "description" or an "accessibleDescription", and the API needs to offer document structures in addition to a paragraph.
Could "accessibleDescription" be the higher-level API, defaulting to a paragraph, but offering devs an easy way to add document structures for all sorts of descriptions. It would be the responsibility of the description designer to indicate what structures are needed for a complex description like in the case of the Energy Spectrum Diagram.

I think this Buoyancy commit is related to to making additional information and RichText accessible.
https://github.com/phetsims/density-buoyancy-common/blob/6ba45b6a5fdbece5cba9590f520571a529697b35/js/buoyancy/view/ReadoutListAccordionBox.ts#L127-L130

Yes, seems useful for @jessegreenberg to look at. Perhaps this provides ideas about an higher level optional API piece for RichText in general?

This same kind of text (technically dynamic state descriptions) are also in the Values accordion box in Trig Tour
![Screenshot 2024-11-27 at 15 37 22](https://github.com/user-attachments/assets/cae9610d-f61b-4c24-a8

f9-bbe5a2238daf)

We want it to be straightforward to make screen text accessible. For the Voicing feature, this non-interactive but still dynamic on-screen text would need to be made into reading blocks in order to be voiced.

We are going to try this out in the context of trig-tour as we need it for the rows fo content in this AccordionBox:

Yes we want the high level API.

I have boilerplate ready for a new high level function in ParallelDOM. We should meet to discuss:

What should it be called?
What should be the default behavior (elements in the PDOM)?
How should it behave with other high level functions? Can you set both an accessibleName and this new "descriptive text" on a components? Or is that a use case for "accessibleName" and "helpText"?

I'm sketching out this example in psuedo HTML code
BUTTON + H3: {{Cosine}} Values
DIV

what is the name we need for content like this?
P: (x,y) = {{value01}}
P: angle = {{value02}} degrees
P: {{cos}} = {{value03}}

H4: Angle Units
UL
LI: degrees (accessible name for radio)
LI: radians
Additional question: Can the high-level API for accessible name and help text for accordionbox and radiobutton group be used along side this other yet-to-be-named high-level API?
Somewhere along the design/implementation cycle, someone needs to choose the HTML structure for the content (static or dynamic) that is displayed as on-screen text or as an on-screen diagram.
Name idea brainstorming (just ideas):

Accessible Description for onscreen text
Accessible Description for onscreen Image, Diagram, or Chart
Accessible Description for non-interactive visual content
In all three cases, structure for the accessible descriptions will be needed. We could default to a Paragraph fro short descriptions, or default to a list for meaningful groups of related content.

@terracoda @kathy-phet and I met today to discuss this. We decided on this:

setAccessibleParagraph( content ): A high level API setter that will make the Node a p element with the provided content.
setAccessibleList( content[], type ): A high level API setter that will make the Node an 'ul' or an 'ol' and then add list items for each content within it.

In my patch above I had started with accessibleDescription, but that provides too much flexibility. This setter should ALWAYS create a list, and if that is not sufficient then you need to use the lower level functions.
I am going to add these and then we can describe it to the dev team.
We also discussed that #855 is an important part of the high level API.

Here is a patch for accessibleParagraph I will finish and commit on Monday:

Subject: [PATCH] Sound drag listeners optionally take a TSoundPlayer instead of creating one internally, see https://github.com/phetsims/scenery-phet/issues/889
---
Index: js/accessibility/pdom/ParallelDOM.ts
IDEA additional info:
Subsystem: com.intellij.openapi.diff.impl.patch.CharsetEP
<+>UTF-8
===================================================================
diff --git a/js/accessibility/pdom/ParallelDOM.ts b/js/accessibility/pdom/ParallelDOM.ts
--- a/js/accessibility/pdom/ParallelDOM.ts	(revision 26c7e12c241702eee9d00507f86f8a3ab4a73b1e)
+++ b/js/accessibility/pdom/ParallelDOM.ts	(date<PHONE_NUMBER>671)
@@ -208,6 +208,7 @@
   'accessibleNameBehavior',
   'helpText',
   'helpTextBehavior',
+  'accessibleParagraph',
   'pdomHeading',
   'pdomHeadingBehavior',

@@ -572,6 +573,9 @@
   // Function that returns the options needed to set the appropriate accessible name for the Node
   private _accessibleNameBehavior: PDOMBehaviorFunction;

+  // Sets the 'Accessible Paragraph' for the Node.
+  private _accessibleParagraph: PDOMValueType | null = null;
+
   // Sets the help text of the Node, this most often corresponds to description text.
   private _helpText: PDOMValueType | null = null;

@@ -892,6 +896,37 @@
     }
   }

+  /**
+   * TODO - document this API
+   */
+  public setAccessibleParagraph( accessibleParagraph: PDOMValueType | null ): void {
+    assert && assert( this.tagName === null || this.tagName === 'p', 'accessibleParagraph can only be set on a Node with a p tag' );
+    if ( accessibleParagraph !== this._accessibleParagraph ) {
+
+      // Forward to the lower level API.
+      this.tagName = 'p';
+      this.innerContent = accessibleParagraph;
+
+      this._accessibleParagraph = accessibleParagraph;
+    }
+  }
+
+  public set accessibleParagraph( accessibleParagraph: PDOMValueType | null ) { this.setAccessibleParagraph( accessibleParagraph ); }
+
+  public get accessibleParagraph(): string | null { return this.getAccessibleParagraph(); }
+
+  /**
+   * Get the accessible name that describes this Node.
+   */
+  public getAccessibleParagraph(): string | null {
+    if ( isTReadOnlyProperty( this._accessibleParagraph ) ) {
+      return this._accessibleParagraph.value;
+    }
+    else {
+      return this._accessibleParagraph;
+    }
+  }
+
   /**
    * Remove this Node from the PDOM by clearing its pdom content. This can be useful when creating icons from
    * pdom content.
@@ -1133,6 +1168,11 @@
   public setTagName( tagName: string | null ): void {
     assert && assert( tagName === null || typeof tagName === 'string' );

+    // For the higher level API, if using accessibleParagraph the tag name must be 'p'.
+    if ( this._accessibleParagraph ) {
+      assert && assert( tagName === 'p' || tagName === null, 'accessibleParagraph can only be set on a Node with a p tag' );
+    }
+
     if ( tagName !== this._tagName ) {
       this._tagName = tagName;


[Suggestion/Ideia] Others icon's

Hi, first just want to say that I love your code, and works amazing. And i want to ask if it's possible to add more icons for others languages.
I use Pawn (its used for sa:mp(gaming)) and Processing for example, and maybe you could put a icon for others languages that people use, or you could add a little file that people can edit and insert himself.
I don't know if it's possible, but it's only a suggestion. ^^
Thanks and keep the good work.

Good idea to complement programming language icons

If you have icons for the programming langs I can add them to the application.

I dont know if you need a especif size, but i am gonna send one on a bigger size and other in small size. I am only sending for processing and pawn, because it's the languages that i use.

I am not too sure for the pawn icon, but I can definitely add processing. Do you know the extension (or whatever to put in AVAILABLES_ICONS)?

I am not too sure for the pawn icon, but I can definitely add processing. Do you know the extension (or whatever to put in AVAILABLES_ICONS)?

The extension for processing is .pde and the Pawn is .pwn


metrics-server missing endpoints

I am on a raspberry pi 3 B+ using v0.9.1 because when I tried v0.10.2, k3s installation still exits with an error code. I am trying to install the metrics-server. I cloned github.com/rancher/metrics-server and deployed the 1.8+ version, but when i do kubectl get apiservices, under available, it says "False (missing endpoints)" and the pod is on CrashLoopBackOff.
I see that in the latest release metrics-server is included by default and a metrics-server directory is added in manifests. That would be helpful to me now, but i am unable to use the latest version. Any ideas on how to troubleshoot/how to make adjustments to metrics-server that could help?
I saw that someone said rancher/metrics-server:v0.3.6 is available and compatible with arm, but i can't seem to find it on the repo, so i am on v0.3.5 based on the image k8s.gcr.io/metrics-server-amd64:v0.3.5.
Thanks

May we ask why you are not able to use the latest? It also has other fixes for armhf (pis) and is suggested. We will be releasing v1.0 soon in less than a week.

here is part of the output of journalctl -xe. the same thing happened with 0.10.0 and 0.10.1
`A start job for unit k3s.service has begun execution.
-- The job identifier is 2197.
Nov 06 21:28:33 under2 k3s[1667]: time="2019-11-06T21:28:33.622572826-05:00" level=info msg="Starting k3s v0.10.2 (8833bfd9)"
Nov 06 21:28:33 under2 k3s[1667]: time="2019-11-06T21:28:33.633636368-05:00" level=info msg="Kine listening on unix://kine.sock"
Nov 06 21:28:33 under2 k3s[1667]: time="2019-11-06T21:28:33.636280795-05:00" level=info msg="Fetching bootstrap data from etcd"
Nov 06 21:28:33 under2 k3s[1667]: time="2019-11-06T21:28:33.659381837-05:00" level=info msg="Running kube-apiserver --advertise-port=6443 --allow-privileged=
Nov 06 21:28:33 under2 k3s[1667]: Flag --basic-auth-file has been deprecated, Basic authentication mode is deprecated and will be removed in a future release
Nov 06 21:28:33 under2 k3s[1667]: I1106 21:28:33.661652    1667 server.go:650] external host was not specified, using <IP_ADDRESS>
Nov 06 21:28:33 under2 k3s[1667]: I1106 21:28:33.663432    1667 server.go:162] Version: v1.16.2-k3s.1
Nov 06 21:28:33 under2 k3s[1667]: I1106 21:28:33.699299    1667 plugins.go:158] Loaded 11 mutating admission controller(s) successfully in the following orde
Nov 06 21:28:33 under2 k3s[1667]: I1106 21:28:33.699537    1667 plugins.go:161] Loaded 7 validating admission controller(s) successfully in the following ord
Nov 06 21:28:33 under2 k3s[1667]: I1106 21:28:33.705152    1667 plugins.go:158] Loaded 11 mutating admission controller(s) successfully in the following orde
Nov 06 21:28:33 under2 k3s[1667]: I1106 21:28:33.705273    1667 plugins.go:161] Loaded 7 validating admission controller(s) successfully in the following ord
Nov 06 21:28:33 under2 k3s[1667]: I1106 21:28:33.839664    1667 master.go:259] Using reconciler: lease
Nov 06 21:28:33 under2 k3s[1667]: I1106 21:28:33.967723    1667 rest.go:115] the default service ipfamily for this cluster is: IPv4
Nov 06 21:28:35 under2 k3s[1667]: W1106 21:28:35.625867    1667 genericapiserver.go:404] Skipping API batch/v2alpha1 because it has no resources.
Nov 06 21:28:35 under2 k3s[1667]: W1106 21:28:35.751014    1667 genericapiserver.go:404] Skipping API node.k8s.io/v1alpha1 because it has no resources.
Nov 06 21:28:35 under2 k3s[1667]: W1106 21:28:35.877572    1667 genericapiserver.go:404] Skipping API rbac.authorization.k8s.io/v1alpha1 because it has no re
Nov 06 21:28:35 under2 k3s[1667]: W1106 21:28:35.901123    1667 genericapiserver.go:404] Skipping API scheduling.k8s.io/v1alpha1 because it has no resources.
Nov 06 21:28:35 under2 k3s[1667]: W1106 21:28:35.980025    1667 genericapiserver.go:404] Skipping API storage.k8s.io/v1alpha1 because it has no resources.
Nov 06 21:28:36 under2 k3s[1667]: W1106 21:28:36.111472    1667 genericapiserver.go:404] Skipping API apps/v1beta2 because it has no resources.
Nov 06 21:28:36 under2 k3s[1667]: W1106 21:28:36.111584    1667 genericapiserver.go:404] Skipping API apps/v1beta1 because it has no resources.
Nov 06 21:28:36 under2 k3s[1667]: I1106 21:28:36.226640    1667 plugins.go:158] Loaded 11 mutating admission controller(s) successfully in the following orde
Nov 06 21:28:36 under2 k3s[1667]: I1106 21:28:36.226765    1667 plugins.go:161] Loaded 7 validating admission controller(s) successfully in the following ord
Nov 06 21:28:36 under2 k3s[1667]: time="2019-11-06T21:28:36.292521211-05:00" level=info msg="Running kube-scheduler --bind-address=<IP_ADDRESS> --kubeconfig=/va
Nov 06 21:28:36 under2 k3s[1667]: time="2019-11-06T21:28:36.306747669-05:00" level=info msg="Running kube-controller-manager --allocate-node-cidrs=true --bin
Nov 06 21:28:36 under2 k3s[1667]: I1106 21:28:36.336465    1667 controllermanager.go:161] Version: v1.16.2-k3s.1
Nov 06 21:28:36 under2 k3s[1667]: I1106 21:28:36.339405    1667 deprecated_insecure_serving.go:53] Serving insecurely on [::]:10252
Nov 06 21:28:36 under2 k3s[1667]: I1106 21:28:36.339994    1667 server.go:143] Version: v1.16.2-k3s.1
Nov 06 21:28:36 under2 k3s[1667]: I1106 21:28:36.340432    1667 defaults.go:91] TaintNodesByCondition is enabled, PodToleratesNodeTaints predicate is mandato
Nov 06 21:28:36 under2 k3s[1667]: W1106 21:28:36.346640    1667 authorization.go:47] Authorization is disabled
Nov 06 21:28:36 under2 k3s[1667]: W1106 21:28:36.346724    1667 authentication.go:79] Authentication is disabled
Nov 06 21:28:36 under2 k3s[1667]: I1106 21:28:36.346787    1667 deprecated_insecure_serving.go:51] Serving healthz insecurely on [::]:10251
Nov 06 21:28:46 under2 k3s[1667]: time="2019-11-06T21:28:46.322559800-05:00" level=fatal msg="starting tls server: Get https://<IP_ADDRESS>:6444/apis/apiextensi
Nov 06 21:28:46 under2 systemd[1]: k3s.service: Main process exited, code=exited, status=1/FAILURE
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
`

So i was able to install v0.11.0-alpha4 successfully, and the metrics-server is here but still has the missing endpoints problem.

It sounds like you tried to install an amd64 version of metrics server on the rpi3, which is arm.
I think the pod is in a backoff state from the previous errors and might resolve itself eventually, but the easiest thing to do would be to completely uninstall k3s and install the newest rc.

it seems like the metrics-server is working now, thanks!


v20210131: suggestion: add link on version release notes to avnav updater screen

the update-plugin worked nicely for me, displaying and installing today's update. Perfect!
Looking for release notes, I went to github to check if some special actions were required after updating. As well as to check which features were added. This step could be easier if a link to release notes was provided on the updater screen.
In certain cases (like updating avnav ) reading release notes is a must,
i.e. when manual changes or additions to avnav_server.xml are to be applied

Maybe this could be done...
Basically the avnav release notes are always at https://www.wellenvogel.net/software/avnav/docs/release.html#h2:Versionen (de) or https://www.wellenvogel.net/software/avnav/docs/release.html?lang=en#h2:Versions (en)


TN: HF20: Support different asset symbols & testnet configurations

As a python developer on Steem I want to be able to easily connect to all Steem based blockchains using only simple configuration.
AC

[x] determine what changes are necessary to support the stated goal
[x] outcome of previous in a comment titled # Results with a set of recommended stories.

Results
In order to support custom networks following file has to be changed with chain properties: https://github.com/steemit/steem-python/blob/master/steembase/chains.py
This would be manual change everytime there is new network.
Better solution,
From what I can see, it will require some refactoring to generalize chains.py to something that could be changed dynamically. This file needs refactoring: where steemd connection or chain parameters are defined: https://github.com/steemit/steem-python/blob/master/steem/steemd.py#L60

Chain specific changes, HF20 and/or Appbase (asset style changes)
Asset style changes will require more deeper changes, in multiple files.. starting with https://github.com/steemit/steem-python/blob/master/steem/amount.py and https://github.com/steemit/steem-python/blob/master/steembase/operations.py

And of course,
deprecated and new operations from HF20 and Appbase should be added here:
https://github.com/steemit/steem-python/blob/master/steembase/operationids.py
https://github.com/steemit/steem-python/blob/master/steembase/operations.py
I would suggest 3x2 separate stories for each section changes (implementation and testing)

@feruzm

refactoring to generalize chains.py to something that could be changed dynamically.

Is your thinking that the users of the library should pass in an object of their own to the constructor in steemd.py?  Perhaps the library could allow either a string for configurations currently in chains.py or the user-supplied object as mentioned above?  Should a file uri with configuration be an option?

@relativityboy Something similar to how private keys are used in library. User credentials are stored locally steembase/storage.py and used dynamically. Chains could use similar approach, much more flexible.


how to disable justMyCode in unittest debug?

I search it , and i cannot find solution

LS does not provide debugging so please either ask in the extension GH https://github.com/Microsoft/vscode-python or in debugger: https://github.com/Microsoft/ptvsd


Sugar throwing a runtime exception in Angular v6 application.

I have used the following import syntax for the Sugar date module through Angular v5.2.10 and CLI v1.7.4 with success. Upon upgrading the version of Angular and its companions I observe the following issue reported by Sugar v2.0.4.
import * as Sugar from 'sugar/date';

I have also tried the following without success...
import {Sugar} from 'sugar/date';

I understand that this may be an Angular related issue, but I was curious if others have observed this upon upgrading their Angular applications.

Thanks for this! I'll have a look into it too but for a workaround can you get in there and try to figure out which global it's trying to reference?

I'll try to help out the best I can without being too familiar with the internals of the library.
It looks like this error occurs during the mapping of the NATIVE_NAMES constant specifically when name === 'Object'
forEachProperty(NATIVE_NAMES.split(' '), function(name) {
  createNamespace(name);
});

// seems to be undefined
globalContext["Object"].prototype;

I doubt that strict mode makes this object undefined.
I fixed it by putting this workaround in polyfills.ts.
window['global'] = window;

I doubt that strict mode makes this object undefined.

That's one of the features of strict mode, though: https://coderwall.com/p/jes4dw/strict-mode-this-keyword-in-javascript

We just ran into this issue as well. @tasuku-s does your workaround have any consequences in terms of AOT etc?

@gaiottino
I have no idea to answer this question.
But, it works with AOT build mode in my application.
I wonder why strict mode makes this undefined only under angular6 environment.
It seems like global issue, if sugar.js apply this to globalContext under strict mode.
In actual, sugar.js bind this without strict mode.
https://github.com/andrewplummer/Sugar/blob/master/dist/sugar.js#L13473
So maybe webpack or typescript wrap around with strict mode.
There is some option to solve this issue.

Is https://github.com/andrewplummer/Sugar/commit/0cd73d1fc83e16a7b51e02c5b19b9db18d7ac180 intended to be the fix for this issue?


My JSON Profile

Thank you @krishguptadev

Please do not commit package-lock files and

I guess the file got updated when new versions of some packages were installed. Should I delete the file in the pull request I created?


Override an existing resource

An example of what is meant is listed below:
declare PlayerCharacterTemplate {
  override (#128) {
    Cash = 50000;
  };
};

This is now done, as of PR #40.


testrpc interface panel

It would be great to have a panel on the contract page where we could send testrpc messages to blockchain environment.  This is specifically useful in testing when you need to simulate the passage of time.
   web3.currentProvider.sendAsync({
            jsonrpc: "2.0",
            method: "evm_increaseTime",
            params: [86400 * 34],
            id: new Date().getTime()
          }

There may be a better handle for doing this, but when I try to inspect source and call this it gets ahold of the metamask instance and not my local rpc instance that I'm running.
Looks like the web3 is in the ExecutionContext.  I couldn't quickly find a handle on that object.

yes that's planned soon

will be addressed by https://github.com/ethereum/browser-solidity/issues/535

now that you can use web3 in the terminal that should be doable.


created a preprocessor Median blur

solved the alignment issue in template.json file of sample 6(OMRChecker\samples\sample6\template.json) along with using median blur as a medium for smoothing .
created a new preprocessor called MedianBlur (OMRChecker\src\processors\builtins.py).

this is the output before editing the code

this is the output after editing the code

I added a plugin class MedianBlur(OMRChecker\src\processors\builtins.py), this plugin uses median blur instead of gaussian blur
median blur is an algorithm based library.
Here, the central element of the image is replaced by the median of all the pixels in the kernel area.
due to this ,the darkened circles appears more clearly and becomes easy to read.

Looks good! Thanks


Add alternate links to sitemap

Added support for issue #6
In order to have alternate links to sitemap the first argument of addItem method should be an array where keys are 'default' or hreflang codes and values the different url's.

How is it going?


[Vertex AI] Add pod to FirebaseManifest

Added the FirebaseVertexAI pod to the FirebaseManifest.
Note: Currently needs allowWarnings: true because we emit the following warning on watchOS and tvOS. https://github.com/firebase/firebase-ios-sdk/blob/413dfef9ef85c7af866b0c528b85372d0f5b98f5/FirebaseVertexAI/Sources/Constants.swift#L17-L19
#no-changelog

LGTM on green zip build and tests and testing the zip binary instructions in a Vertex AI sample app.

I tested the zip (see #13607) and CocoaPods (see #13609) integrations in our sample app and didn't notice any issues.
Note: Although the version is 11.2-beta, zip and pod support won't be available until the Firebase 11.3 release.


Fix jittering in Treebeard with on scroll

Purpose
Fixes the issue #1661 . Scrolling by dragging the scrollbar with mouse should not cause jitters
Changes
Replaces the commit sha reference for treebeard in bower.json so the treebeard changes can be installed.
Side effects
Does not effect scrolling otherwise. Tested in Chrome, Safari, Firefox and IE 11.  Safari has still a tiny jitter but that should not hold up the fix.

I'm still seeing this when scrolling on staging and production.

http://webmup.com/a62b0/


python310Packages.pytest-cases: 3.6.14 -> 3.8.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.pytest-cases is: Separate test code from test cases in pytest
meta.homepage for python310Packages.pytest-cases is: https://github.com/smarie/python-pytest-cases
meta.changelog for python310Packages.pytest-cases is: https://github.com/smarie/python-pytest-cases/releases/tag/3.8.0
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 3.8.0 with grep in /nix/store/8zzwqjarq22canw9f7in9r0w9806ilgp-python3.10-pytest-cases-3.8.0
found 3.8.0 in filename of file in /nix/store/8zzwqjarq22canw9f7in9r0w9806ilgp-python3.10-pytest-cases-3.8.0

Rebuild report (if merged into master) (click to expand)

7 total rebuild path(s)

7 package rebuild(s)

First fifty rebuilds by attrpath
home-assistant-component-tests.sia
python310Packages.labelbox
python310Packages.pysiaalarm
python310Packages.pytest-cases
python311Packages.labelbox
python311Packages.pysiaalarm
python311Packages.pytest-cases

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/8zzwqjarq22canw9f7in9r0w9806ilgp-python3.10-pytest-cases-3.8.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python310Packages.pytest-cases https://github.com/r-ryantm/nixpkgs/archive/6df5326620e4f9d6f005b51ed53d775b60354192.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/6df5326620e4f9d6f005b51ed53d775b60354192#python310Packages.pytest-cases

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/8zzwqjarq22canw9f7in9r0w9806ilgp-python3.10-pytest-cases-3.8.0
ls -la /nix/store/8zzwqjarq22canw9f7in9r0w9806ilgp-python3.10-pytest-cases-3.8.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

7 packages built:

home-assistant-component-tests.sia
python310Packages.labelbox
python310Packages.pysiaalarm
python310Packages.pytest-cases
python311Packages.labelbox
python311Packages.pysiaalarm
python311Packages.pytest-cases

Maintainer pings
cc @fabaff for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.pytest-cases is: Separate test code from test cases in pytest
meta.homepage for python310Packages.pytest-cases is: https://github.com/smarie/python-pytest-cases
meta.changelog for python310Packages.pytest-cases is: https://github.com/smarie/python-pytest-cases/releases/tag/3.8.1
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 3.8.1 with grep in /nix/store/fvlgsxzlp340ngwz64wb42gxr6q4lj26-python3.10-pytest-cases-3.8.1
found 3.8.1 in filename of file in /nix/store/fvlgsxzlp340ngwz64wb42gxr6q4lj26-python3.10-pytest-cases-3.8.1

Rebuild report (if merged into master) (click to expand)

23 total rebuild path(s)

23 package rebuild(s)

First fifty rebuilds by attrpath
home-assistant-component-tests.sia
python310Packages.cloudpathlib
python310Packages.fastai
python310Packages.labelbox
python310Packages.pysiaalarm
python310Packages.pytest-cases
python310Packages.spacy
python310Packages.spacy-lookups-data
python310Packages.spacy-transformers
python310Packages.textacy
python310Packages.textnets
python310Packages.weasel
python311Packages.cloudpathlib
python311Packages.fastai
python311Packages.labelbox
python311Packages.pysiaalarm
python311Packages.pytest-cases
python311Packages.spacy
python311Packages.spacy-lookups-data
python311Packages.spacy-transformers
python311Packages.textacy
python311Packages.textnets
python311Packages.weasel

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/fvlgsxzlp340ngwz64wb42gxr6q4lj26-python3.10-pytest-cases-3.8.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python310Packages.pytest-cases https://github.com/r-ryantm/nixpkgs/archive/1ab7cc5d03d0f498e4a3318a84a172e5e8e0eca2.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/1ab7cc5d03d0f498e4a3318a84a172e5e8e0eca2#python310Packages.pytest-cases

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/fvlgsxzlp340ngwz64wb42gxr6q4lj26-python3.10-pytest-cases-3.8.1
ls -la /nix/store/fvlgsxzlp340ngwz64wb42gxr6q4lj26-python3.10-pytest-cases-3.8.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

2 packages failed to build:

python310Packages.labelbox
python311Packages.labelbox

21 packages built:

home-assistant-component-tests.sia
python310Packages.cloudpathlib
python310Packages.fastai
python310Packages.pysiaalarm
python310Packages.pytest-cases
python310Packages.spacy
python310Packages.spacy-lookups-data
python310Packages.spacy-transformers
python310Packages.textacy
python310Packages.textnets
python310Packages.weasel
python311Packages.cloudpathlib
python311Packages.fastai
python311Packages.pysiaalarm
python311Packages.pytest-cases
python311Packages.spacy
python311Packages.spacy-lookups-data
python311Packages.spacy-transformers
python311Packages.textacy
python311Packages.textnets
python311Packages.weasel

Maintainer pings
cc @fabaff for testing.

Already on master.


Question: syntax

Thanks for the useful decorator! I was hoping you could explain the syntax at the line below, specifically the usage of the negation operator. It looks like it's being used as an existential operator, but that follows a different syntax. Just trying to demystify this so I can understand more about writing my own decorators.
https://github.com/NoHomey/bind-decorator/blob/master/src/index.ts#L14

It's to ensure type validity since TypedPropertyDescriptor<T>.value is optional value of type T.

Ah! Finally found it! Thanks for helping me learn a new TS trick!


Migrate asynctest to stdlib's AsyncMock

Asynctest doesn't work with Python 3.8 and above.
Asynctest upstream is aware of this breakage and recommends using the built-in AsyncMock instead.
See also Martiusweb/asynctest#144 and Martiusweb/asynctest#126

Hmmm interesting, that's probably why the python3.8 branch tests didn't work. However it's not that easy as we still want to run tests for 3.7, 3.6 versions so would have to have a way to have both when running the test suite

I believe there are packages that implement the AsyncMock interface for Python 3.6 and Python 3.7, so we wouldn't need to mess around with two different approaches.
https://pypi.org/project/asyncmock/ seems to do this, but a better approach would probably be to use the backported mock 4.X package: https://pypi.org/project/mock/

https://github.com/argaen/aiocache/pull/513 added python3.8 to the pipeline and tests seem to run and pass so closing for now.


Refactor and Simplify Iterable Macro

This removes the requirement to wrap single component types in (T,). This is backwards compatible in order to simplify any user macros which may try to implement a trait over all tuples like we are doing here, by not requiring them to special case the single component scenario.

LGTM , thank you!


Handle relative path when using Go modules

This is a follow up to #1661 which correctly handles relative paths when using go modules.
#1661 didn't account for situations where you want to generate server code in a sub package of your module, so it generated the wrong imports because it used the go module path as base import instead of go module + relative package.
E.g. if you had a module github.com/a/b and wanted to generate go-swagger code from the package github.com/a/b/my-server then the import paths would be github.com/a/b/restapi/.. instead of github.com/a/b/my-server/restapi/...

This makes generation go a lot slower for some reason

I have noticed this as well. I don't think it's related to this particular change but I suspect it has to do with using Go modules in general. I assume when using Go modules you hit the network a lot when invoking go during the generation.
I have not yet verified this though.


Can I call a function from a personal Python Scripit in Power BI

In Python Script option inside Power BI, I would like to use:
from personal_script.py import function
In order to use some personal functions to do some data transformation inside Power BI
Is there a way of doing this?
I have tried:
from personal_script.py import function
I expect the output of being able to use my personal function collected in my personal Python Script, but I got:
Unable to connect
We encountered an error while trying to connect.
Details: "ADO.NET: Python script error.
Traceback (most recent call last):
File "PythonScriptWrapper.PY", line 9, in
from personal_script import function
ImportError: No module named 'personal_script'
https://community.powerbi.com/t5/Desktop/Can-I-call-a-function-from-a-personal-Python-Scripit-in-Power-BI/m-p/813584#M391150

This should get you on your way: https://stackoverflow.com/questions/2349991/how-to-import-other-python-files


cannot create resource "events" in API group "events.k8s.io" in the namespace "utils"'

What version of descheduler are you using?
descheduler version: k8s.gcr.io/descheduler/descheduler:v0.25.0
Does this issue reproduce with the latest release?
Yes
Which descheduler CLI options are you using?
Not using CLI
Please provide a copy of your descheduler policy config file
I'm running it as HELM (descheduler/descheduler, 0.25.0) chart with the following values:
kind: CronJob
schedule: "*/15 * * * *"

resources:
  limits:
    cpu: 500m
    memory: 256Mi
  requests:
    cpu: 100m
    memory: 128Mi

tolerations:
  {}

affinity:
  {}

nodeSelector:
  {}

deschedulerPolicy:
  evictFailedBarePods: true
  evictLocalStoragePods: true
  ignorePvcPods: false
  maxNoOfPodsToEvictPerNamespace: 10
  maxNoOfPodsToEvictPerNode: 10
  strategies:
    LowNodeUtilization:
      enabled: true
      nodeFit: true
      params:
        nodeResourceUtilizationThresholds:
          targetThresholds:
            cpu: 70
            memory: 70
          thresholds:
            cpu: 40
            memory: 40
    PodLifeTime:
      enabled: true
      params:
        namespaces:
          include:
          - mysql57
          - influxdb
          - mongodb
          - etcd
          - utils
        podLifeTime:
          maxPodLifeTimeSeconds: 86400
    RemoveDuplicates:
      enabled: false
      nodeFit: true
    RemovePodsHavingTooManyRestarts:
      enabled: true
      params:
        podsHavingTooManyRestarts:
          includingInitContainers: true
          podRestartThreshold: 20
    RemovePodsViolatingInterPodAntiAffinity:
      enabled: true
      nodeFit: true
    RemovePodsViolatingNodeAffinity:
      enabled: true
      nodeFit: true
      params:
        nodeAffinityType:
        - requiredDuringSchedulingIgnoredDuringExecution
    RemovePodsViolatingNodeTaints:
      enabled: true
      nodeFit: true
    RemovePodsViolatingTopologySpreadConstraint:
      enabled: true
      nodeFit: true
      params:
        includeSoftConstraints: false

successfulJobsHistoryLimit: 1
failedJobsHistoryLimit: 1

priorityClassName: system-cluster-critical

cmdOptions:
  v: 3

What k8s version are you using (kubectl version)?
kubectl version Output
Client Version: version.Info{Major:"1", Minor:"22+", GitVersion:"v1.22.6-eks-7d68063", GitCommit:"f24e667e49fb137336f7b064dba897beed639bad", GitTreeState:"clean", BuildDate:"2022-02-23T19:32:14Z", GoVersion:"go1.16.12", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"23+", GitVersion:"v1.23.7-eks-4721010", GitCommit:"b77d9473a02fbfa834afa67d677fd12d690b195f", GitTreeState:"clean", BuildDate:"2022-06-27T22:19:07Z", GoVersion:"go1.17.10", Compiler:"gc", Platform:"linux/amd64"}

What did you do?
I'm getting the following error in the logs
'events.events.k8s.io is forbidden: User "system:serviceaccount:ops:descheduler" cannot create resource "events" in API group "events.k8s.io" in the namespace "utils"' (will not retry!)

full output:
klon ops -l app.kubernetes.io/instance=descheduler

node="ip-10-110-7-206.us-west-2.compute.internal"
ops/descheduler-27732750-hs7xg[descheduler]: E0923 20:30:30.551327       1 event_broadcaster.go:253] Server rejected event '&v1.Event{TypeMeta:v1.TypeMeta{Kind:"", APIVersion:""}, ObjectMeta:v1.ObjectMeta{Name:"xxx-xxx-psql-6c86c4c489-dnkq8.1717976114452b5c", GenerateName:"", Namespace:"utils", SelfLink:"", UID:"", ResourceVersion:"", Generation:0, CreationTimestamp:time.Date(1, time.January, 1, 0, 0, 0, 0, time.UTC), DeletionTimestamp:<nil>, DeletionGracePeriodSeconds:(*int64)(nil), Labels:map[string]string(nil), Annotations:map[string]string(nil), OwnerReferences:[]v1.OwnerReference(nil), Finalizers:[]string(nil), ManagedFields:[]v1.ManagedFieldsEntry(nil)}, EventTime:time.Date(2022, time.September, 23, 20, 30, 30, 544378065, time.Local), Series:(*v1.EventSeries)(nil), ReportingController:"sigs.k8s.io.descheduler", ReportingInstance:"sigs.k8s.io.descheduler-descheduler-27732750-hs7xg", Action:"Descheduled", Reason:"PodLifeTime", Regarding:v1.ObjectReference{Kind:"Pod", Namespace:"utils", Name:"xxx-xxx-psql-6c86c4c489-dnkq8", UID:"b7a7fcde-5eb0-4e5e-af50-29e695f11e8f", APIVersion:"v1", ResourceVersion:"753022310", FieldPath:""}, Related:(*v1.ObjectReference)(nil), Note:"pod evicted by sigs.k8s.io/descheduler", Type:"Normal", DeprecatedSource:v1.EventSource{Component:"", Host:""}, DeprecatedFirstTimestamp:time.Date(1, time.January, 1, 0, 0, 0, 0, time.UTC), DeprecatedLastTimestamp:time.Date(1, time.January, 1, 0, 0, 0, 0, time.UTC), DeprecatedCount:0}': 'events.events.k8s.io is forbidden: User "system:serviceaccount:ops:descheduler" cannot create resource "events" in API group "events.k8s.io" in the namespace "utils"' (will not retry!)
ops/descheduler-27732750-hs7xg[descheduler]: I0923 20:30:30.579421       1 evictions.go:160] "Evicted pod" pod="utils/xxx-xxx-mongodb-7d97495d7b-rltfv" reason="" strategy="PodLifeTime"

What did you expect to see?
Event to be written in the namespace where the eviction happened.
What did you see instead?
'events.events.k8s.io is forbidden: User "system:serviceaccount:ops:descheduler" cannot create resource "events" in API group "events.k8s.io" in the namespace "utils"' (will not retry!)

Hi @dmitry-mightydevops, this is odd because the clusterrole for Helm has events permission by default. Could you check the clusterrole was set up properly? It should be something like kubectl get -o yaml clusterrole/descheduler

To update this, we found that our helm chart was not actually using the right role (https://github.com/kubernetes-sigs/descheduler/issues/986#issuecomment-1280851913) so we opened some PRs to fix this. Thank you for reporting!


Basic Ivy support (configurations, repositories), SBT plugin

Fixes https://github.com/alexarchambault/coursier/issues/8, https://github.com/alexarchambault/coursier/issues/52, https://github.com/alexarchambault/coursier/issues/71, https://github.com/alexarchambault/coursier/issues/83, https://github.com/alexarchambault/coursier/issues/87.
Deprecates https://github.com/alexarchambault/coursier/issues/41 (more / better cache policies), https://github.com/alexarchambault/coursier/issues/53 (repositories not named anymore).


Rewrite the code in JS/Node

Hello, can u rewrite the code in js/node , it's hard for me to understand the code in vue.js, i never used this framework, so im a bit wasted.
Should be very appreciate ! ,Thanks for your work.

sorry no

Hi, how can do so ?


Change links to override forward

From which version can we use forward function?

@knorth55 V5. Here is the reference: https://docs.chainer.org/en/stable/upgrade.html?highlight=upgrade#use-forward-instead-of-call-in-links.

pfnCI, test this please

Please fix these errors.

2019-03-18 11:10:02.161407 STDOUT 2074] | def _predict(self, imgs):
-- | --
2019-03-18 11:10:02.161414 STDOUT 2074] | xs = chainer.Variable(self.xp.asarray(imgs))
2019-03-18 11:10:02.161421 STDOUT 2074] | with chainer.using_config('train', False):
2019-03-18 11:10:02.161427 STDOUT 2074] | >           scores = F.softmax(self.forward(xs)).array
2019-03-18 11:10:02.161434 STDOUT 2074] | E           AttributeError: Parameterized test failed.
2019-03-18 11:10:02.161440 STDOUT 2074] | E
2019-03-18 11:10:02.161448 STDOUT 2074] | E           Base test method: TestPSPNetResNet.test_predict_gpu
2019-03-18 11:10:02.161455 STDOUT 2074] | E           Test parameters:
2019-03-18 11:10:02.161486 STDOUT 2074] | E             model: <class 'chainercv.experimental.links.model.pspnet.pspnet.PSPNetResNet50'>
2019-03-18 11:10:02.161524 STDOUT 2074] | E
2019-03-18 11:10:02.161533 STDOUT 2074] | E
2019-03-18 11:10:02.161539 STDOUT 2074] | E           (caused by)
2019-03-18 11:10:02.161546 STDOUT 2074] | E           AttributeError: 'PSPNetResNet101' object has no attribute 'forward'

2019-03-18 11:10:02.494948 STDOUT 2074] | self = <chainercv.experimental.links.model.pspnet.pspnet.PSPNetResNet50 object at 0x7f88b82a05d0>
-- | --
2019-03-18 11:10:02.494955 STDOUT 2074] | imgs = array([[[[   0.       ,    0.       ,    0.       , ...,    0.       ,
2019-03-18 11:10:02.494962 STDOUT 2074] | ...  , ...,   39.060997 ,
2019-03-18 11:10:02.494969 STDOUT 2074] | 128.061    ,  -56.939003 ]]]], dtype=float32)
2019-03-18 11:10:02.494975 STDOUT 2074] |
2019-03-18 11:10:02.494976 STDOUT 2074] | def _predict(self, imgs):
2019-03-18 11:10:02.494982 STDOUT 2074] | xs = chainer.Variable(self.xp.asarray(imgs))
2019-03-18 11:10:02.494988 STDOUT 2074] | with chainer.using_config('train', False):
2019-03-18 11:10:02.494994 STDOUT 2074] | >           scores = F.softmax(self.forward(xs)).array
2019-03-18 11:10:02.495000 STDOUT 2074] | E           AttributeError: Parameterized test failed.
2019-03-18 11:10:02.495006 STDOUT 2074] | E
2019-03-18 11:10:02.495012 STDOUT 2074] | E           Base test method: TestPSPNetResNet.test_predict_gpu
2019-03-18 11:10:02.495018 STDOUT 2074] | E           Test parameters:
2019-03-18 11:10:02.734602 STDOUT 2074] | E             model: <class 'chainercv.experimental.links.model.pspnet.pspnet.PSPNetResNet50'>
2019-03-18 11:10:02.734638 STDOUT 2074] | E
2019-03-18 11:10:02.734648 STDOUT 2074] | E
2019-03-18 11:10:02.734656 STDOUT 2074] | E           (caused by)
2019-03-18 11:10:02.734663 STDOUT 2074] | E           AttributeError: 'PSPNetResNet50' object has no attribute 'forward'

I apologize to have missed chainercv/experimental/links and I'm working on them.

can you also modify FCIS and Yolov2Tiny in experimental if possible?

Sorry. I had not checked this seriously.
Could you change chainercv.utils.testing.constant_stub_link.py?
Also, could you change all TrainChains in examples?

pfnCI, test this please

How do you think of the following items that contains __call__?
*.rst files
https://github.com/chainer/chainercv/blob/45624ca3badfb3d530a9726375fa4ff9df7c5ced/chainercv/utils/testing/constant_stub_link.py#L14-L15
https://github.com/chainer/chainercv/blame/45624ca3badfb3d530a9726375fa4ff9df7c5ced/examples/faster_rcnn/README.md#L16

I didn't change them because chainer.Link and chainer.Chain don't include :meth:forward in their documentation.
However, I noticed that other Links like L.Convolution2D and Chains like ResNet50Layers included :meth:forward.
So, let me change them too.

*.rst files still contain __call__.
https://github.com/chainer/chainercv/blame/7af64e81012759314f7cff467bc19b350b7bcab7/docs/source/reference/links/faster_rcnn.rst#L26

Do you think it's better to remove all __call__?
2019年3月22日(金) 13:26 Toru Ogawa<EMAIL_ADDRESS>
*.rst files still contain call.
https://github.com/chainer/chainercv/blame/7af64e81012759314f7cff467bc19b350b7bcab7/docs/source/reference/links/faster_rcnn.rst#L26
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/chainer/chainercv/pull/835#issuecomment-475489822,
or mute the thread
https://github.com/notifications/unsubscribe-auth/APcP051MJ7rYosDtXfH2AqxVBCdvkxPAks5vZFtwgaJpZM4b4Jdy
.

Since __call__ does not have its docstring and nothing is rendered, we should remove them.

LGTM


Update logging v1 to 0.2.3

Motivated by: https://github.com/rancher/rancher/issues/30279
Backport issue: https://github.com/rancher/rancher/issues/30569
Minimum validation: Logging v1 0.2.3 works on clusters with at least one Windows Server 1909 node, and in both VXLAN and Host GW configurations.

on 2.5-head - commit id: bb69b03

Deployed windows 1809 Windows_Server-2019-English-Full-ContainersLatest and 1909 Windows server english core base nodes clusters - 1 etcd, 1 control, 1 worker node linux and 3 windows worker nodes.
Enabled cluster level logging using elastic search and Fluentd
0.2.3rancher-logging app is deployed.
Logging on the cluster works fine - Deployed workloads, logs seen in Kibana and fluentd container.

Verified logging on 2.5-head - commit id: bd660e1
Logging v1 on linux cluster works fine. Version: 0.2.3
Verified upgrade usecase from 2.5.3 to 2.5-head - commit id: bd660e1

Deploy a cluster, enable logging v1 - cluster level using elastic search.
Upgrade rancher to 2.5-head.
Logging is upgraded to 0.2.3
Deploy some workloads. Logging v1 works on a linux cluster.


Matching on K/KItem sort injections

@dwightguth has pointed out a case when a function should not be applied, but the booster does apply the owise case. Namely:
given
syntax Bool ::= isInt(K) [function]
rule isInt(I:Int) => true
rule isInt(_) => false [owise]

and a configuration with isInt(X:KItem), the booster rewrites this term into false. Here is the simp trace for the application of this function:
isInt(VarX:SortKItem{})
Symbols differ:
kseq(Eq#VarInt:SortInt{}, dotk())
VarX:SortKItem{} @(hs-backend-booster-0.0.0-inplace:Booster.Pattern.ApplyEquations library/Booster/Pattern/ApplyEquations.hs:488:5)
[Simplify] Simplifying term
isInt(VarX:SortKItem{})
to
"false"

The issue above is the special treatment of injections into K, namely if we look at the kore definition of isInt and its internalisation, we get these two equations:
isInt(kseq{}(inj{SortInt{}, SortKItem{}}(Var'Unds'Gen1:SortInt{}),dotk{}())) = \dv{SortBool{}}("true")
isInt(VarK:SortK{})                                                          = \dv{SortBool{}}("false")

This is problematic because when applying the equations to the term isInt(inj{SortKItem{}, SortK{})(VarX:SortKItem{})), the match between kseq{}(..) and VarX:SortKItem{} obviously fails... Not sure if this is an issue with how pyk generates kore for the K term isInt(X:KItem) (possibly related to https://github.com/runtimeverification/pyk/issues/565, i have not tested with a new enough version of pyk which contains the fix for this) or if the booster is supposed to handle the kseq(..., dotk{}) patterns as a special case when matching...

kseq and dotk are just regular constructors. What is supposed to happen, if I understand correctly, is that the first rule doesn't apply because pattern matching fails, but the second rule also doesn't apply because unification of the pattern with the first rule succeeds nontrivially.

I would assume that the booster should determine that the match between the first pattern isInt(I:Int) and isInt(X:KItem) is indeterminate because KItem is a super-sort of Int and could therefore apply. Then, because the first equation is indeterminate, no other equations should be attempted to be matched and we should abort.
Is this intuition correct?

I mean, it ought  to be safe to apply any rules that have the same priority; but no rules of lower priority should apply.

Reading through this issue description and the slack discussion, I noticed that we should also clarify whether/why isInt(inj{SortKItem{}, SortK{}}(...) would be accepted in the booster, given that SortKItem is not a subsort of SortK.
The syntax for isInt  stipulates an argument of sort K but the rules in K are formulated with arguments of other sorts.
From what @goodlyrottenapple writes, the compilation translates those by wrapping them into kseq.

What happens if we use input term kseq(X:SortKItem{}, dotk: SortK{})?
Are incorrect injections (non-subsort injections) detected by booster when internalising input?


indexOf() is not working properly in Mutations challenge

Challenge Name

Issue Description

Browser Information

Browser Name, Version:
Operating System:
Mobile, Desktop, or Tablet:

Your Code

Screenshot

`function mutation(arr) {
var str=arr.join('');
var teststr=str.toLowerCase();
var len=arr[0].length;
var tstr=arr[1].toLowerCase();
var ans= teststr.indexOf(tstr,len);
if(ans!==-1)
return true;
else
return false;
}
mutation(["Hello", "hey"]);`

Hi @Sree-001. Unfortunately your code is not correct, and will always return true for any valid input.
Please visit the HelpJavaScript chat room for help with the algorithm challenges before raising an issue related to specific code.
Thanks and happy coding!


iOS app: Can't set custom status cleaning after some time in different timezone

Summary
If I set manual app timezone (it is Moscow in application) and my device is in different local zone (for example in India, Mumbai) then I can't set custom status with "Clear After ...".
Environment Information

Device Name: iPhone 15 Pro
OS Version: 17.3
Mattermost App Version: 2.13.0
Mattermost Server Version: 9.4.2

Steps to reproduce

Set manual timezone (in app settings) different from those you use in your iOS device.
Try to set custom status "Out for lunch" with "Clear after 1 hour"

Expected behavior
Set custom status as expected
Observed behavior (that appears unintentional)
When I press "Done" nothing happens.

After about 10 times problem disappeared 🤨

After 10 times problem dissapeared


Renamed sub-package 'args' to 'cli' for consistency

This change is

LGTM

Coverage remained the same at 86.826% when pulling c85e472ee8d92c5298e93433e6464d7812e2ca96 on renamed-args-to-cli-for-consistency into 615fa64ad4197fc43b874d7efff3c0cec323c58d on master.

Coverage remained the same at 86.826% when pulling c85e472ee8d92c5298e93433e6464d7812e2ca96 on renamed-args-to-cli-for-consistency into 615fa64ad4197fc43b874d7efff3c0cec323c58d on master.


Multi select on ios selecting items as I swipe.

Ionic version:  (check one with "x")
(For Ionic 1.x issues, please use https://github.com/ionic-team/ionic-v1)
[ ] 2.x
[X ] 3.x
[ ] 4.x
I'm submitting a ...  (check one with "x")
[X] bug report
[ ] feature request
Please do not submit support requests or "How to" questions here. Instead, please use one of these channels: https://forum.ionicframework.com/ or http://ionicworldwide.herokuapp.com/
Current behavior:

I could not get cors working with WKWebView.   Ended up switch over to UIWebView.
Was able to build an ios app.
In testing the app, noticed that multiselect was selecting items just from me just swiping/scrolling.
I was able to record the screen, and make it gif.
https://drive.google.com/file/d/1GlCtseYgtWmQva2rtm8Byc3GmzX9jqTD/view
The hard part is you can't see where I'm clicking.
Seems like there is a sweet spot in the scrolling, not to fast and not to slow it works pretty well.
Expected behavior:

I would expect it to work like the Android one.  Swiping up and down does not select the times.  (ok maybe one here and there).
Steps to reproduce:

Build a Multi select box.
https://ionicframework.com/docs/api/components/select/Select/
With a lot of items in the list, 30 or so.
Build the code to an iphone.
Swipe up and down one hand,  right thumb doing the scrolling.
Related code:

<ion-item class="btn-primary formlabel">
                    <ion-label style="margin-left:40%;color:white;font-size:15px;font-family: MuseoSans;">{{'SELECT_INFO'|translate}}</ion-label>
                    <ion-select (ionChange)="addInfo($event)" multiple="true" style="max-width:0%">
                        <ion-option *ngFor="let info of addInfoList" [value]="info">{{info|translate}}</ion-option>
                    </ion-select>
                </ion-item>

I don't see anything that would cause it to be sensitive.
Other information:

Ionic info: (run ionic info from a terminal/cmd prompt and paste output below):
I post this over on the community form.
https://forum.ionicframework.com/t/multiple-value-checkboxes-to-sensitive-on-ios/118563
cli packages: (/usr/lib/node_modules)

    @ionic/cli-utils  : 1.19.1
    ionic (Ionic CLI) : 3.19.1

global packages:

    cordova (Cordova CLI) : 7.0.1

local packages:

    @ionic/app-scripts : 3.1.7
    Cordova Platforms  : android 6.4.0 browser 4.1.0 ios 4.5.4
    Ionic Framework    : ionic-angular 3.8.0

System:

    Android SDK Tools : 26.1.1
    Node              : v6.12.0
    npm               : 3.10.10
    OS                : Linux 3.13

Environment Variables:

    ANDROID_HOME : /home/Android/Sdk

Misc:

    backend : legacy

Hi, I'm having the same issue, here. It is randomly selecting items while scrolling up and down on iOS. I not even touched some of these items while swiping.
cli packages: (/usr/local/lib/node_modules)

    @ionic/cli-utils  : 1.19.2
    ionic (Ionic CLI) : 3.20.0

global packages:

    cordova (Cordova CLI) : 8.0.0

local packages:

    @ionic/app-scripts : 3.1.9
    Cordova Platforms  : android 7.1.0 ios 4.5.4
    Ionic Framework    : ionic-angular 3.9.2

System:

    ios-deploy : 1.9.2
    ios-sim    : 6.0.0
    Node       : v8.9.4
    npm        : 5.6.0
    OS         : macOS High Sierra
    Xcode      : Xcode 9.3 Build version 9E145

Environment Variables:

    ANDROID_HOME : not set

Misc:

    backend : pro

@hinnerk-a  What WebView are you using?
The severity of the problem seems to be related to how you scroll.  (I still feel like there is some bug)
We kind of have had to just accept  the buggy version and are just hoping people aren't to aggressive of scrollers.

@newuser44 It seems that I don't use any WebView as I cannot find that string in my entire project. Should I use one?
With the current state our client, my wife and me, we cannot find a way to scroll without accidentally selecting options.

@hinnerk-a - you are using a webview one way or another when running on a mobile device because that is where Ionic applications need to run.  By default, Cordova will use UIWebView on iOS devices and you need to use a plugin in order to use WKWebView. The default plugin for Ionic apps is cordova-plugin-ionic-webview and in newly generated apps it will be included by default. Check your package.json file and config.xml file and make sure that plugin is there.
If it is not there, you may want to install it (ionic cordova plugin add cordova-plugin-ionic-webview), but be sure to read the docs first as it comes with some caveats that may be an issue for you if you have not been using WKWebView from the start. I have not been able to replicate this issue when using WKWebView.
Side note: Capacitor will be using WKWebView by default since that is Apple's go-forward direction as webviews go. Hopefully, that will alleviate some of this confusion as to which webview is actually being used, at least for projects that use Capacitor.

It seems like this happens all the time.  How bad it happens just seems to depend on how you have learned to scroll and select things.  It also seems like just different builds can also be a factor.
The problem we had was CORS.  Trying to get an existing WS to allow localhost mobile apps through was causing problems.


[Story][CL]: Simulator testing for concentrated liquidity

Background

As an engineer, I would like to have randomized testing for concentrated liquidity, so that I can be more confident that the core logic works as expected under various situations

Suggested Design
Implement a simulator for all concentrated liquidity messages, that would be similar with the gamm simulator( cref: https://github.com/osmosis-labs/osmosis/tree/main/x/gamm/simulation)
Tasks
We want to have the following components tested via simulator

Random Create Position Msg
Random Withdraw Position Msg
Random create concentrated liquidity pool
RandomSwapExactAmountIn
RandomSwapExactAmountOut
Random CollectFees

We also want to add simulator testings for the pool manager module if possible
Acceptance Criteria

simulator is implemented for concentrated liquidity
all messages are tested

Hi @stackman27. Could you please break this down into tasks?

yup will do apologies for the delay

#4241 blocked by https://github.com/osmosis-labs/osmosis/issues/4366

Addressed now


update debug-puppeteer example to 2.10.4

coverage: 99.245%. remained the same when pulling ec622d26b9558bea7538f2bd7c87ca5a0750ba42 on rc-2.10.4-example-update into eecfc8b9bac9d521b62b024e7bb26e6f90a12f04 on master.


{"ok":false,"error":"invalid_auth"}%

I have generated token at this page https://api.slack.com/web#auth
But getting error when I try to confirm it

You have to replace TOKEN part with your actual token.


Remove NodeIndex and LeafIndex

NodeIndex and LeafIndex are huge foot guns and should be replaced with more usable indices, i.e. only NodeIndex aka u32.

I proposed to actually do this in the standard, but people were not too happy about the idea. It's probably still a good idea to do this in the implementation, though. Just note, that the standard requires certain messages to contain leaf indices, but we could just map those to node indices when encoding/decoding.

The standard really only uses node indices (the "roster" concept was removed at some point). I was always annoyed by this but it's causing too many issues and costing too much time by now that we finally have to do something about it.

What are your specific concerns @franziskuskiefer?
I always thought that having both types reduces the risk for confusion and in practical terms it has eliminated some problems that existed in earlier versions.
In my mind, the ideal scenario would be to only use LeafIndex on the outside and NodeIndex should be limited to the binary tree (I know we don't have a good abstraction layer).

The entire approach is way too error prone. Look for example at something like this.
let index = tree.get_some_index();
do_something(index.as_u32());

You have to know the function signature of get_some_index in order to know what value you pass to do_something.
Getting rid of these indices will probably be part of rewriting the tree.

The standard really only uses node indices (the "roster" concept was removed at some point). I was always annoyed by this but it's causing too many issues and costing too much time by now that we finally have to do something about it.

The standard says we have to use leaf indices, for example in messages. That's what I meant. See also Richard's reponse in this thread: https://github.com/mlswg/mls-protocol/issues/432

There is ongoing work in the MLS WG to get rid of NodeIndex, which would also solve our problem. See https://github.com/mlswg/mls-protocol/pull/507.

Closing this in favour of the upcoming spec changes (#918, #892).


More fixup for uploading artifacts

This one should cover all projects using Common makefile.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: abhay-krishna
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [abhay-krishna]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/lgtm

@abhay-krishna: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

cri-tools-tooling-presubmit
ad232b05981954554491fd4a07fa6d093382c9eb
link
/test cri-tools-tooling-presubmit

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

/test cri-tools-tooling-presubmit

New changes are detected. LGTM label has been removed.

@abhay-krishna: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

cri-tools-tooling-presubmit
988df59e86aedb0b0cb4eff20dd04e5112d55ca5
link
/test cri-tools-tooling-presubmit

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: abhay-krishna, jaxesn
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [abhay-krishna,jaxesn]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/retest


Revisiting PerfView/PerfView64

Following some (minor, and now resolved) confusion about the PerfView and PerfView64 artifacts that get attached to the AppVeyor builds, I wanted to revisit the separation of these binaries. During the discussion of #175, the concern for unification appeared to be the performance impact of running in 64-bit mode when not necessary. However, my overall observation regarding PerfView performance has been the following:

Trace files which are small enough to load in the 32-bit build do not face performance problems in either the 32-bit or 64-bit builds.
Trace files which encounter performance problems cannot load successfully in the 32-bit build, thus any potential performance advantage of it is moot.

It appears that the current separation of these binaries does not provide performance-related value to end users. It would make sense in this case to simplify the build by releasing only a single binary, which is an AnyCPU build with the Prefer 32-bit flag set back to false.

It'd be nice to put this issue to bed once and for all.
Can we back up your observations with (non-subjective) data?
Presumably, we need a trace that is small enough to fit 32-bit, but large enough to generate meaningful timing metrics.

@pharring Currently this is only a perspective observation. I rarely have a trace that fits in the 32-bit process (typically only happens if I'm trying to make that happen specifically). When I do see performance problems using smaller traces, I find that it indicates a bug in PerfView () more than indicating a case where the 64-bit version is slower.
The weakest point in my argument is the 64-bit version requires more physical memory in order to load the same trace. However, it does not seem like an unreasonably limiting assumption that developers assigned to performance investigations will have systems where an additional 3.5GiB (at the very most) of additional memory in use for the investigation will cause substantial problems.

For what it is worth, my experience is exactly the opposite.   I can count on one hand the number of times I have needed a 64 bit version of PerfView, and I do a lot of performance investigations.     My guess is that using 64 bit when you don't need to will cost you 10-20% in throughput (because caches are used less efficiently this is what it costs servers to go from 32 to 64 bit).   This is not huge from a human perspective, but it certainly is not pay for play.
There is another argument that says, that frankly that any time you are manipulating GB of data, things will not be fast.   It would be (much) BETTER if we can invest in keeping the data smaller (probably mostly through sampling or reprocessing).   It really should be the case that MOST scenarios don't need HUGE amounts of data for you to do an effective performance analysis.   I would like that option thoroughly explored before we give up and say you need 4GB+ traces routinely to get the job done.
Now that said, I understand that until we do that, there are people who have the issue today.   That is why I was OK with the 64 bit build.   I am even OK making it so that PerfView can relaunch itself as a 64 bit app, and even making this so that particular users can make it do that by default.   PerfView already had to know how to relaunch itself (for elevation, and to avoid locking files on file shares), so doing this is pretty easy.
I do understand that making just one build is simpler, but I would want some non-trivial data that shows a non-trivial part of the user base is running into the issue
If you get 50+ bonafide perfView users giving a thumbs up on this issue, that would certainly get my attention (I would look into reducing memory consumption and if that failed, I would make 64 bit the default).

I've given up using the 32-bit version of PerfView. Even if there is a performance impact (which anecdotally I haven't noticed), I find it easier to have a single version than guessing whether or not the 32-bit version is going to OOM or not.
It does feel like we're on different sides of the world though, almost all my traces are huge - maybe I'm missing something to reduce the traces that I'm looking at? Almost all performance issues that I'm investigating are due to huge solutions and find it easier and better timewise to quickly grab a trace and investigate those than breaking the repro down to something manageable.

I don't have a problem with you using PerfView64 all the time.   By all means do so, that is what it is for.
Ideally we would figure out ways of getting your scenarios to NOT need GBs of memory (since I think that should be possible and would significantly improve your experience (it would be faster)), but I am not actively looking at that, so using PerfView64 is fine.

Was just perusing old issues, seems this one can be closed since PerfView 3.x is now 64bit only?

Yup, thanks @mahamr.


feat(0001): Variables

I think many people are more receptive to const rather than let mut. I quite like the rust way, but if you are targeting this at JS devs, then familiarity would be quite useful. Zig provides a good example of how this would work, and as a lot of the philosophies seem lifted from it, it might be useful to carry that along.

the language is going to be a rusty js with extensive differences from JavaScript and it's primary goal is to be Typescript 2 without the incrimental change so I don't see the point in const. Additionally let vs let mut is very obvious in code and using modifiers for keywords is a nice paradigm I'd like to keep for the future.

I think many people are more receptive to const rather than let mut. I quite like the rust way, but if you are targeting this at JS devs, then familiarity would be quite useful. Zig provides a good example of how this would work, and as a lot of the philosophies seem lifted from it, it might be useful to carry that along.

I've discussed with a lot of people internally the answer is basically: let mut looks to be the best option. At first it seems arbitrary. Why would I want two keywords instead of one keyword to do the same thing? It turns out that this is critical to future language components. Let's say we went with var and const like zig. How would functions with immutable / mutable arguments work?
fn <name>(var x: <type>, const y: <type>) {

}

looks and feels bad, but unless we want to define more keywords, this is kind of the only way to do it. Let's suppose though that you keep insisting. We could do
fn <name>(var x: <type>, y: <type>) {

}

but from a beginner perspective, what the heck is var doing there. What does var represent? I would struggle to read that. mut is a much clearer keyword imo.
But even then, let's suppose that you think this is fine. New issue for you: object destructuring. What if you want some destructured values to be mutable and some not to be mutable. With the mut keyword, it's pretty clear:
let (x, mut y, z) = <value>;

It starts to be very dicey otherwise, and it becomes very unclear how to do this. You could do
const (x, var y, z) = <value>;

but that looks incredibly gross. You could also do
(const x, var y, const z) = <value>;

which looks potentially even grosser. The reason why zig didn't pick let mut is because they didn't have destructuring until just recently. Even then, it's just array destructuring. Even then, it looks really gross. We can do better.

This RFC has been limited in scope to only include immutable variables due to some conflicts. Mutable variables will be discussed later.


Added Car Brand Classification

Solves  #108

Thanks for Contributing 🎉  Please leave a Star for the Repository!


Certain globals need polyfilling for React Native

✅ Prerequisites

[x] Did you perform a cursory search of open issues? Is this bug already reported elsewhere?
[x] Are you running the latest SDK version?
[x] Are you reporting to the correct repository (magic-sdk)?

🐛 Description
atob, btoa, and process is not defined in React Native.
🧩 Steps to Reproduce

Set up React Native Project
Import/instantiate Magic
Broken 😢

🤔 Expected behavior
React Native should work!
😮 Actual behavior
Undefined globals if the environment is not correctly polyfilled.
💻 Code Sample
None.
🌎 Environment

Software
Version(s)

magic-sdk

Browser

yarn

Operating System

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


fix fix that thrift struct sequence number is not consistent in 1.1-lts and master

Definition of TQueryOptions in gensrc/thrift/PaloInternalService.thrift
is not consistent:
1.1-lts:   47: optional i32 num_free_block_in_scan
master:   47: optional bool enable_local_exchange
Proposed changes
Issue Number: close #xxx
Problem summary
Describe your changes.
Checklist(Required)

Does it affect the original behavior:

[ ] Yes
[ ] No
[ ] I don't know

Has unit tests been added:

[ ] Yes
[ ] No
[ ] No Need

Has document been added or modified:

[ ] Yes
[ ] No
[ ] No Need

Does it need to update dependencies:

[ ] Yes
[ ] No

Are there any changes that cannot be rolled back:

[ ] Yes (If Yes, please explain WHY)
[ ] No

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 38.8 seconds
load time: 568 seconds
storage size:<PHONE_NUMBER>1 Bytes
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20221031154510_clickbench_pr_36569.html


Unknown scheduler: DDIM_tiled

When 'temporal_tiling' is selected in context options, the cogvideoxfun sampler gives following error:
Temporal tiling enabled, changing scheduler to DDIM_tiled
!!! Exception during processing !!! Unknown scheduler: DDIM_tiled
Traceback (most recent call last):
File "D:\AI\ComfyUI_windows_portable\ComfyUI\execution.py", line 323, in execute
output_data, output_ui, has_subgraph = get_output_data(obj, input_data_all, execution_block_cb=execution_block_cb, pre_execute_cb=pre_execute_cb)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "D:\AI\ComfyUI_windows_portable\ComfyUI\execution.py", line 198, in get_output_data
return_values = _map_node_over_list(obj, input_data_all, obj.FUNCTION, allow_interrupt=True, execution_block_cb=execution_block_cb, pre_execute_cb=pre_execute_cb)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "D:\AI\ComfyUI_windows_portable\ComfyUI\execution.py", line 169, in _map_node_over_list
process_inputs(input_dict, i)
File "D:\AI\ComfyUI_windows_portable\ComfyUI\execution.py", line 158, in process_inputs
results.append(getattr(obj, func)(**inputs))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "D:\AI\ComfyUI_windows_portable\ComfyUI\custom_nodes\ComfyUI-CogVideoXWrapper\nodes.py", line 1051, in process
raise ValueError(f"Unknown scheduler: {scheduler}")
ValueError: Unknown scheduler: DDIM_tiled

BTW, in the webui of cogvideox-fun we can generate i2v video with frames longer than 49, the result is quite smooth. I guess it is temporal_tiling or something like it to work

That was a mistake I made when refactoring the context options, should be fixed now.
Fun models can do up to 73 frames without any tiling or contexting, after that it starts to loop from beginning. It's the same with these nodes. It's just the official I2V model which can't do anything but 49 frames.

That was a mistake I made when refactoring the context options, should be fixed now.
Fun models can do up to 73 frames without any tiling or contexting, after that it starts to loop from beginning. It's the same with these nodes. It's just the official I2V model which can't do anything but 49 frames.

thank you, but there is another error now😂
Temporal tiling enabled, changing scheduler to CogVideoXDDIM
!!! Exception during processing !!! 'CogVideoX_Fun_Pipeline_Inpaint' object has no attribute '_gaussian_weights'
Traceback (most recent call last):
File "D:\AI\ComfyUI_windows_portable\ComfyUI\execution.py", line 323, in execute
output_data, output_ui, has_subgraph = get_output_data(obj, input_data_all, execution_block_cb=execution_block_cb, pre_execute_cb=pre_execute_cb)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "D:\AI\ComfyUI_windows_portable\ComfyUI\execution.py", line 198, in get_output_data
return_values = _map_node_over_list(obj, input_data_all, obj.FUNCTION, allow_interrupt=True, execution_block_cb=execution_block_cb, pre_execute_cb=pre_execute_cb)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "D:\AI\ComfyUI_windows_portable\ComfyUI\execution.py", line 169, in _map_node_over_list
process_inputs(input_dict, i)
File "D:\AI\ComfyUI_windows_portable\ComfyUI\execution.py", line 158, in process_inputs
results.append(getattr(obj, func)(**inputs))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "D:\AI\ComfyUI_windows_portable\ComfyUI\custom_nodes\ComfyUI-CogVideoXWrapper\nodes.py", line 1075, in process
latents = pipe(
^^^^^
File "D:\AI\ComfyUI_windows_portable\python_embeded\Lib\site-packages\torch\utils_contextlib.py", line 115, in decorate_context
return func(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^
File "D:\AI\ComfyUI_windows_portable\ComfyUI\custom_nodes\ComfyUI-CogVideoXWrapper\cogvideox_fun\pipeline_cogvideox_inpaint.py", line 863, in call
t_tile_weights = self._gaussian_weights(t_tile_length=t_tile_length, t_batch_size=1).to(latents.device).to(self.vae.dtype)
^^^^^^^^^^^^^^^^^^^^^^
File "D:\AI\ComfyUI_windows_portable\python_embeded\Lib\site-packages\diffusers\configuration_utils.py", line 143, in getattr
raise AttributeError(f"'{type(self).name}' object has no attribute '{name}'")
AttributeError: 'CogVideoX_Fun_Pipeline_Inpaint' object has no attribute '_gaussian_weights'

Right, I never actually tried the temporal tiling as I was working on mostly adding the context scheduling, which is a far better method, albeit slower, this should be fixed now though.

Right, I never actually tried the temporal tiling as I was working on mostly adding the context scheduling, which is a far better method, albeit slower, this should be fixed now though.

Great work, it works now!


Update trainings for v2.0

This change is

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/d24406de0c6b798fc5cf318fd172ad0b82a310a9/