The "not latest" banner does not show if branch naming strategy changes

We changed our branch names from pulp-2.1, pulp-2.2, etc pulp-2.3, etc to 2.4-release 2.5-release, etc. I expect that the pulp-2.* pages would show the "You are not using the most up to date version of the library. XXX is the newest version." but they don't.
Specifically on this page I expect it on this page: http://pulp-puppet-dev-guide.readthedocs.org/en/pulp-2.3/
I do see it on the 2.4-release page:  http://pulp-puppet-dev-guide.readthedocs.org/en/2.4-release/
This banner is produced through a javascript call on the page here. That call is made to the API handler here.
From some discussion on IRC it was suggested the issue is that distutils is getting the comparison wrong.
I feel that using the VCS tag is wrong for a version comparison given that sphinx explicitly sets this in conf.py.  http://sphinx-doc.org/config.html#confval-version
To implement a fix, when a RTD builder is built it should store the version in a way that the API handler can look at it without having to actually import conf.py.

Using the version number from conf.py seems like a good idea. But I'm not sure if that holds up in all situations. Maybe we can get some expert input on this from @agjohnson or @ericholscher here.

When I filed this issue I talked with @ericholscher. He indicated it would be difficult to do this in practice. Nevertheless, I maintain that RTD should use the version from conf.py. RTD is built around Sphinx and should not ignore the Sphinx version defined in conf.py in favor of its own. Not only is it theoretically wrong, but it makes the banners show up on the "latest" version in some cases which is wrong in practice.

I think we can divide this issue in two parts:

changing the style name version in the project

I would say that this is not more possible since the only supported way is semantic versioning (PEP440): http://docs.readthedocs.io/en/latest/versions.html?highlight=version#how-we-envision-versions-working
So, I think this is not a problem anymore.
>>> import unicodedata
>>> from packaging.version import Version
>>> version_name = '2.5-release'
>>> Version(unicodedata.normalize('NFKD', unicode(version_name)).encode('ascii', 'ignore'))
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/humitos/.pyenv/versions/rtd/lib/python2.7/site-packages/packaging/version.py", line 202, in __init__
    raise InvalidVersion("Invalid version: '{0}'".format(version))
packaging.version.InvalidVersion: Invalid version: '2.5-release'
>>>

This is part of the code in RTD at https://github.com/humitos/readthedocs.org/blob/a0a29e8bbb454d9296b91492d31ecbee396fe1fa/readthedocs/projects/version_handling.py#L109-L115

read the version from conf.py

I'm not sure if we want this, but it's something that has to be decided by @agjohnson or @ericholscher I suppose.

I'm -1 on reading from conf.py. Every single conf.py has a version and release which is likely not maintained in 95% of cases. We tie to VCS concepts wherever possible, so I don't think it makes sense to treat conf.py as canonical for this information. I've rather wanted to automate this through our conf.py template, rather then respect the version/release setting in conf.py.
I think we have some overlapping tickets on how we actually want to support "latest version", so I'm going to close this.


Bump to mermaid 10.3.0

@dreampuf this bumps to latest mermaid and cdproto
https://github.com/mermaid-js/mermaid/releases/tag/v10.3.0

Thanks!


Customizable default lane arrows and/or AI vehicles issue

For better understanding, I'll give an example that's the problem I'm having, by default, the second lane arrow (or the middle lane arrow) from six lane roads is set to the vehicles go to the front when there are 3 others 6 lane roads connected (you can check the screenshot if it's confusing), but the problem of this default lane arrows configuration is most of the vehicles will focus to go to the right or left of the road with it, consequently, the traffic can accumulate easily and will do the middle of the road most of the time useless ("because will be just decorative", what's bad to decrease the traffic)
That's why it's a nice idea to make the default configuration of the lane arrows customizable because when you expand the city, the amount of the four roads connection with six lanes are (or will be) too big to change manually. Also, is interesting improve the vehicles AI (if it's the mod case and if is the right place to report this), since can happen even though I set the modified lane arrows below, the vehicles can still insist to go to the right or left instead in the middle of the road at least 33-50% of the times depending on what direction them want to go (Notes section can explain it in the clear way)
Screenshots:

Defaulf configuration in this case

Modified Lane Arrows

Notes or questions:
The modified lane arrows screenshot is the configuration I wanted to every case of those connections with four roads with six lanes be like that way. About the possible vehicles AI issue, by default, the vehicles can just ignore the middle's road exists, so the idea I have is given a 33-50% chance of the vehicle go to the middle road, since it's 33-34% if the vehicle just can go to the left, right and middle in case to have 3 paths, or 50% in case of the vehicle can just go to the left or right, and middle, I mean, 2 paths

We already have dynamic (random) lane change option and it will help you mix the vehicles and lanes better, if you set it to 50-75%.

Exactly, dynamic selection slider tells the system (more or less) what percentage of vehicles should try to check if there is better lane and depends on vehicle speed (slower = more checks) vehicle may even check it every node. If internally calculated traffic flow of lane is not much better than the one which is original path lane vehicle won't switch lane, similarly when much better lane is too far (would require multiple changes) vehicle won't try to switch.
Moreover it also applies to vehicles following much slower vehicle - that situation may turn into fake overtaking behavior when speed difference is big enough (e.g.: vehicle behind could move 20% faster after switching lane, still following speed limit on the road)

Well, I tested the feature you said, looks like really efficient, so don't consider the AI vehicle feedback I did anymore, and just consider the customization of the default lane arrows, ok?


Automated testing

Fixes bug in the PFA method, and adds integration tests for DRGEPSA and PFA

The files expected to be produced by the reduction were generated and placed in the test directory.  For each method, the test will execute the reduction to produce a reduced solution, and read in the expected solution from the expected file.  Attributes of the final solution and the expected final solution are then compared for equivalence.

Or the files generated by the test could just be deleted, since they aren't needed.  Would that work?

Personally I think it's neater (and safer) to create a system temporary folder that will automatically be removed, rather than actually delete files—less room accidental deletion and leaving things behind.

The problem is that the function being called in the test generates the file in the cwd.  Should I also make a change where it generates the file on a given path?  And then change the test to make a temp directory and then generate the file in the temp directory?

Yes, I think the path should be changeable (as in, should be a function argument). And then have the test make a temp directory and make the file there.

On Oct 22, 2018, at 1:56 PM, Phillip Mestas<EMAIL_ADDRESS>wrote:
The problem is that the function being called in the test generates the file in the cwd. Should I also make a change where it generates the file on a given path? And then change the test to make a temp directory and then generate the file in the temp directory?
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub, or mute the thread.

What about moving the function call that writes the file up to the pymars function?  No need to call it in every method when it can just be called once at the end.  This will stop the files from being generated by the test too, removing the need for a temp directory.  The path to which the file is written can still be added as an argument to just the pymars function and not the function that does the actual reduction.

Pushed the changes stated above to the pull request

Moving that function up seems fine, but regardless I think any creation of files should be done in one of these temporary folders—it's just cleaner and safer than anything else.

Yup, the output files are no longer created by the test though, and those files are meant to be given to the user, so they shouldn't be deleted.  The hdf5 files probably should be stored in a tmp dir and deleted after, and I have that recorded as an issue.

Looks like there is a merge conflict now?

Merge conflict should be resolved now.


Run composer update

Package operations: 0 installs, 66 updates, 18 removals
  - Downloading symfony/flex (v1.21.8)
  - Downloading laminas/laminas-code (4.16.0)
  - Downloading friendsofphp/proxy-manager-lts (v1.0.18)
  - Downloading myclabs/deep-copy (1.12.1)
  - Downloading symfony/browser-kit (v6.4.13)
  - Downloading symfony/monolog-bridge (v7.1.6)
  - Removing symfony/process (v7.1.3)
  - Removing rector/rector (1.2.5)
  - Removing react/stream (v1.4.0)
  - Removing react/socket (v1.16.0)
  - Removing react/promise (v3.2.0)
  - Removing react/event-loop (v1.5.0)
  - Removing react/dns (v1.13.0)
  - Removing react/child-process (v0.6.5)
  - Removing react/cache (v1.2.0)
  - Removing phpstan/phpstan (1.12.3)
  - Removing php-http/message-factory (1.1.0)
  - Removing friendsofphp/php-cs-fixer (v3.64.0)
  - Removing fidry/cpu-core-counter (1.2.0)
  - Removing evenement/evenement (v3.0.2)
  - Removing composer/xdebug-handler (3.0.5)
  - Removing composer/semver (3.4.2)
  - Removing composer/pcre (3.3.1)
  - Removing clue/ndjson-react (v1.3.0)
  - Upgrading php-http/discovery (1.19.2 => 1.20.0): Extracting archive
  - Upgrading symfony/flex (v1.21.4 => v1.21.8): Extracting archive
  - Upgrading symfony/runtime (v6.4.0 => v6.4.14): Extracting archive
  - Upgrading symfony/routing (v7.0.2 => v7.1.6): Extracting archive
  - Upgrading symfony/polyfill-php83 (v1.28.0 => v1.31.0): Extracting archive
  - Upgrading symfony/http-foundation (v6.4.2 => v6.4.15): Extracting archive
  - Upgrading symfony/event-dispatcher (v7.1.1 => v7.1.6): Extracting archive
  - Upgrading symfony/var-dumper (v7.0.2 => v7.1.8): Extracting archive
  - Upgrading symfony/error-handler (v7.0.0 => v7.1.7): Extracting archive
  - Upgrading symfony/http-kernel (v6.4.2 => v6.4.15): Extracting archive
  - Upgrading symfony/finder (v7.1.4 => v7.1.6): Extracting archive
  - Upgrading symfony/filesystem (v7.1.2 => v7.1.6): Extracting archive
  - Upgrading symfony/var-exporter (v7.0.2 => v7.1.6): Extracting archive
  - Upgrading symfony/dependency-injection (v6.4.2 => v6.4.15): Extracting archive
  - Upgrading symfony/config (v6.4.0 => v6.4.14): Extracting archive
  - Upgrading symfony/cache (v6.4.2 => v6.4.14): Extracting archive
  - Upgrading symfony/framework-bundle (v6.4.2 => v6.4.13): Extracting archive
  - Upgrading symfony/stopwatch (v6.4.8 => v6.4.13): Extracting archive
  - Upgrading symfony/string (v7.1.4 => v7.1.8): Extracting archive
  - Upgrading symfony/console (v6.4.11 => v6.4.15): Extracting archive
  - Upgrading laminas/laminas-code (4.13.0 => 4.16.0): Extracting archive
  - Upgrading friendsofphp/proxy-manager-lts (v1.0.16 => v1.0.18): Extracting archive
  - Upgrading doctrine/persistence (3.2.0 => 3.4.0): Extracting archive
  - Upgrading symfony/doctrine-bridge (v6.4.2 => v6.4.13): Extracting archive
  - Upgrading doctrine/sql-formatter (1.1.3 => 1.5.1): Extracting archive
  - Upgrading doctrine/doctrine-migrations-bundle (3.3.0 => 3.3.1): Extracting archive
  - Upgrading doctrine/inflector (2.0.8 => 2.0.10): Extracting archive
  - Upgrading doctrine/common (3.4.3 => 3.4.5): Extracting archive
  - Upgrading doctrine/collections (2.1.4 => 2.2.2): Extracting archive
  - Upgrading doctrine/orm (2.17.2 => 2.20.0): Extracting archive
  - Upgrading symfony/yaml (v6.4.0 => v6.4.13): Extracting archive
  - Upgrading psr/http-factory (1.0.2 => 1.1.0): Extracting archive
  - Upgrading nyholm/psr7 (1.8.1 => 1.8.2): Extracting archive
  - Upgrading symfony/http-client (v6.4.2 => v6.4.15): Extracting archive
  - Upgrading php-http/multipart-stream-builder (1.3.0 => 1.4.2): Extracting archive
  - Upgrading php-http/promise (1.3.0 => 1.3.1): Extracting archive
  - Upgrading php-http/httplug (2.4.0 => 2.4.1): Extracting archive
  - Upgrading symfony/options-resolver (v7.1.1 => v7.1.6): Extracting archive
  - Upgrading php-http/message (1.16.0 => 1.16.2): Extracting archive
  - Upgrading php-http/client-common (2.7.1 => 2.7.2): Extracting archive
  - Upgrading php-http/cache-plugin (1.8.1 => 2.0.1): Extracting archive
  - Upgrading knplabs/github-api (v3.13.0 => v3.16.0): Extracting archive
  - Upgrading sebastian/resource-operations (3.0.3 => 3.0.4): Extracting archive
  - Upgrading sebastian/global-state (5.0.6 => 5.0.7): Extracting archive
  - Upgrading sebastian/exporter (4.0.5 => 4.0.6): Extracting archive
  - Upgrading sebastian/cli-parser (1.0.1 => 1.0.2): Extracting archive
  - Upgrading theseer/tokenizer (1.2.2 => 1.2.3): Extracting archive
  - Upgrading nikic/php-parser (v5.0.0 => v5.3.1): Extracting archive
  - Upgrading phpunit/php-code-coverage (9.2.30 => 9.2.32): Extracting archive
  - Upgrading phar-io/manifest (2.0.3 => 2.0.4): Extracting archive
  - Upgrading myclabs/deep-copy (1.11.1 => 1.12.1): Extracting archive
  - Upgrading phpunit/phpunit (9.6.15 => 9.6.21): Extracting archive
  - Upgrading masterminds/html5 (2.8.1 => 2.9.0): Extracting archive
  - Upgrading symfony/dom-crawler (v7.0.0 => v7.1.6): Extracting archive
  - Upgrading symfony/browser-kit (v6.4.0 => v6.4.13): Extracting archive
  - Upgrading symfony/dotenv (v6.4.2 => v6.4.13): Extracting archive
  - Upgrading symfony/lock (v6.4.2 => v6.4.13): Extracting archive
  - Upgrading monolog/monolog (3.5.0 => 3.8.0): Extracting archive
  - Upgrading symfony/monolog-bridge (v7.0.0 => v7.1.6): Extracting archive
  - Upgrading symfony/password-hasher (v7.0.0 => v7.1.6): Extracting archive
  - Upgrading symfony/security-core (v6.4.0 => v6.4.13): Extracting archive
  - Upgrading twig/twig (v3.14.0 => v3.15.0): Extracting archive
  - Upgrading symfony/twig-bridge (v6.4.2 => v6.4.13): Extracting archive
  - Upgrading symfony/twig-bundle (v6.4.0 => v6.4.13): Extracting archive
  - Upgrading symfony/web-profiler-bundle (v6.4.2 => v6.4.14): Extracting archive
  - Upgrading twig/extra-bundle (v3.8.0 => v3.15.0): Extracting archive
``

Friendly ping @fabpot


Update Calico from v2.5.1 to v2.6.0

Update cni sidecar image from v1.10.0 to v1.11.0
Lower log level in CNI config from debug to info

https://github.com/projectcalico/calico/releases/tag/v2.6.0

Merged as 8a9b6f12705b23583ffa4a8175676356da76dd66


Tutorials: Final steps of march tutorial

This PR goes on tutorial branch and is ready to review.
Please do not simply merge, but let's use this PR to improve it further together.
The PR provides the basic structure with all needed files, steps, instructions and xpath rules for the advanced tutorial (march) developed at #MEIOx . It also moves the individual steps into separate subfolders for a more readable structure. It does not change the main logic (tutorials.js), view (tutorials.html) or style (CSS) in regard of @kepper working on it at the moment.
It certainly still needs the proofreading of a native speaker (would you like to have a look @siennamw ? Everyone else is invited to take a look at it, too.)
@soniawronkowska @margrethesb could you please have a look especially at the proposed "...-desc.html" files here where all the instructions are included and give your feedback here via GitHub's review function? I had to stretch the tutorial to 12 steps in favor of having a better distinction of several issues.
@kepper could you (beside everythig else ;)) have a closer look at the xpath rules provided and the correctness of the content information in the instructions?
Looking forward to your feedback.

Do you think this is ready to merge? Any other reviewers want to chime in?

Just let's wait a little so that the other requested reviewers have time to take a look.
But feel free to approve (or deny) the latest changes I made after your review meanwhile. ;)
The latest two commits this morning are just updating the PR with the reverted commit on tutorial branch.

Btw., @lpugin has found a way to validate against RelaxNG on the client. I don't know how performant that is, and it surely creates less helpful error messages, but together with an MEI-all-anystart.rng, this could greatly simplify the writing of tutorials and reduce the number of xpaths…

Yes: https://jsfiddle.net/lpugin/rmc18zkw/17/
It should be no problem to use anystart.rng . I will test it and see if we can get it integrated in the jekyll website.

Thanks for all your feedback. You adressed a lot of different issues that are very important.
But as this PR is only about the content of march tutorial, I suggest to keep things separated to not overload this PR with different issues. So let's discuss the visual appearance of the editor window in #64 and about simplifying file validation in another issue (I'll be happy to refactor/adapt it for the march tutorial in another PR if necessary).
@kepper I really understand your concern about this tutorial being "extreme" but I'd like to understand this rather as a compliment and as proof of concept. ;) It even works for a quite elaborated example.
Of course, this tutorial is not intended (and never was) to be the first one that a real absolute beginner is supposed to be confronted with. It is rather for "advanced beginners" that have gone through different simpler tutorials which adress the different topics of the march tutorial in separate "single topic" lectures. I would imagine to have links to these "single topic" tutorials from the different steps of the march tutorial  (How to write a note, How to write a beam, How to encode scoreDef?).
The good thing about having the "extreme", or extended" tutorial first, is that we now can just break it down into smaller learning chunks, using a lot of the already existing code or descriptions. I will be happy to work on these, if you agree that this could be a way to go.
@margrethesb told me that she can have a look at this PR in the next days. So I would like to give her a chance to give some feedback before merging this PR.
Would that be OK with everyone?

Sorry for my late reply, GitHub decided to deny my existence for a few days... Anyway, here goes:

Merging: Go ahead.
Tutorial: This needs more work. I'm not going to try to make suggestions related to the encoding issues, but there are several other things that should be reviewed. Things like lanuage/wording, pedagogy/target group, level of tutorial, whether it should be connected to an gentle text-based intro partly based on older material.
I'm happy to participate in this work, and with the aim of having it ready for MEC.

Thanks @margrethesb .
If I understand correctly, this PR is ready to be merged now, and further work will be done in the next PR's. So anyone with a license to merge is welcome to do so :)

Thank you everyone! This is fantastic.
Once we kick the tires and make sure it all works, an e-mail message to MEI-L from the 'tutorials group' would be brilliant. I think this also illustrates the value of having a work-focused meeting in the Autumn to help move community initiatives forward.
Once again, bravo @musicEnfanthen, @margrethesb and @soniawronkowska .

Once again, bravo @musicEnfanthen, @margrethesb and @soniawronkowska .

Thanks, but not to forget mastermind @kepper who, beside everything else, provided idea and programmatical logic for all of this. Thanks a lot!

As already mentioned in my comment to #66, tutorials are not ready to be included on master. Once they can be released from tutorials to master branch, we will be happy to provide an email message to the community.


No exported PropsWithChildren type

I'm trying to define a layout that takes in some children, but it doesn't look like the library exports a type for it.
Here's the index.d.ts for @elysiajs/html version ^1.1.0
import { createElement } from './h';
export * from './html';
export * from './options';
export * from './utils';
export { ErrorBoundary } from '@kitajs/html/error-boundary';
export { Html } from '@kitajs/html';
export { createElement };
export { html as default } from './html';

I saw some examples saying I should use Html.Children or Html.PropsWithChildren, but those are not properties in my Html object. I do however see that kitajs exports a PropsWithChildren type that is not being exposed by the elysia html library.
Can anyone tell me if I'm maybe doing something wrong?
Thanks

At some point, the developer of KitaJS/Html separated some types out of the Html namespace. Among these were Children and PropsWithChildren. The consequence of this is that Elysia/Html no longer includes these types implicitly. To solve the issue, perhaps
export { Html } from '@kitajs/html';

can be changed to
export * from '@kitajs/html';

any news?


Add information on using DPLACE graphics and logo to "How to Cite" page.

 Issue by fionajordan
Sunday Jan 24, 2016 at 16:51 GMT
Originally opened as https://github.com/NESCent/dplace/issues/225

 Comment by fionajordan
Sunday Jan 24, 2016 at 17:05 GMT

Suggested text:
Maps and trees from D-PLACE have an embedded watermark logo. Please do not erase this logo if you are using the SVG images in presentations, videos, or directly in any other form of publications. You may download data to create your own maps and tree visualisations, in which case no logo is required on the figure.
You may use the D-PLACE logo in presentations to acknowledge the data source or to describe the database. Please do not alter the D-PLACE logo by changing colours, fonts, or proportions.

While we're revising that page, here is a small clarification to the text already there (suggest replacing current text with this):
Research that uses data from D-PLACE should cite both the original source(s) of the data and this paper (e.g., research using cultural data from the Binford Hunter-Gatherer dataset: “Binford (2001); Binford and Johnson (2006); Kirby et al. Submitted).” The reference list should include the date data were accessed and URL for D-PLACE (http://d-place.org), in addition to the full references for Binford (2001) and Binford and Johnson (2006).

@kirbykat "Research that uses data from D-PLACE..." is online.
!! Important !! You're talking about http://d-place.org . Do we own this domain? And if yes, who?

@Bibiko http://d-place.org is owned by @michaelcgavin. Our plan has been to transfer the site there once launched publically. If you have concerns, please let us know!

Marking as completed following email discussion.


Add QNN tutorial

Closes https://github.com/Qiskit/documentation/issues/1172
Adding the QNN Tutorial with more comments in the code, longer text descriptions and a bit at the end about scaling up to more qubits

@iheuze thanks for your contribution. Unfortunately we're not accepting new tutorial contributions and have moved tutorials to an inner-source repo. If you've made significant changes to the notebook, consider sharing your work by self-hosting it with GitHub pages. If you're looking for ways to get involved, you can check for good first issues in this repo or in the Qiskit SDK.


Implement basic in-memory session store

Sessions are stored in a non-persistent Hash.  Only String values are allowed.  A reaper fiber regularly removes any sessions which expire due to inactivity.
See also #91.

This is great 👍 Thanks @mperham.
Before merging how about adding a secret_key for configuration?

Wow. It's a feature that I'd wear my fez when it's merged 🤘

There's no encryption so there's no need for secrets.

On Jun 27, 2016, at 23:19, Serdar Dogruyol<EMAIL_ADDRESS>wrote:
This is great 👍 Thanks @mperham.
Before merging how about adding a secret_key for configuration?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

I see, that makes sense. Let's get this merged then :+1 Thanks again.


VSIX rework

Summary of changes

Refactor the Visual Studio extension so a single extension works in Visual Studio 2010+
Fully support Visual Studio 2010-2013 language services
Visual Studio 2015 support is a placeholder - the assembly exists but the service factory throws NotSupportedException

Fixes #4
Work left

This is a preview branch which does not include the changes in #61. #61 needs to be merged first, and then I will update this pull request (I have a branch in my fork that's already prepared to do this efficiently).
Some files are missing copyright headers

:question: What is the policy on this? Ideally we could just use the two-line comment from corefx

I forgot to add [assembly: ProvideBindingPath] (just remembered while writing this)
Update the build script. buildMSI10.xml and/or Setup10.proj will need major work

Only one VSIX is created
ILMerge cannot be used on the interfaces assembly or the version-specific assemblies for 2010-2015

@SergeyTeplyakov The copyright headers question is for you and/or Mike and/or similar.
@hubuk Do you want to see this merged before the setup scripts are updated for it, or afterwards?
Aside from the [ProvideBindingPath] issue which is straightforward for me to correct, I don't have any immediate plans to change this pull request until I get more feedback about the direction. :smile:

:thought_balloon: The [ProvideBindingPath] attribute likely eliminates much of the need for using ILMerge on the contents of the VSIX.

I'm fine with using that copyright header.

@hubuk This is now complete (i.e. ready for review) aside from the required changes to the installer. How would you like to proceed?

@sharwell I will be reviewing all your changes, but it may take a wile. I will comment any questions here and mark a changsets as reviewed by submitting +1 on each individually. Do you think that this will help to organize review better?
And regarding a merge. I think that your PR may goes first. I will prepare installer changes by tomorrow.

@hubuk re: the installer changes, would those have any effect on or benefit from PR #36 at all?

@billings7 No, my changes only contain a new version update mechanism in buildMSI10.xml
Regarding #36:
The change you introduced worked fine. Unfortunately now it is marked as conflicting and I think it requires some more changes. In addition it would be better not to commit CodeTools binaries into git but build them and use compiled image instead. If you can take a look into this it would be great. If no, I can recreate your changes and align them in a new PR when I finish my current work.

@hubuk @billings7 Pull requests created prior to #61 will show merge conflicts in the UI, but in many cases will not actually have merge conflicts when the merge is run from the command line (and/or the merge conflicts are automatically resolved).

@hubuk I will have a look into that when I can. Changing how CodeTools is built would probably be better in a different PR, from what I can remember some part of it needs VS2012 to build it.

I added 3 commits which are the first part of editor support for VS 2015. Locally I only have 2 more methods to implement (GetAnyCallNodeAboveTriggerPoint and GetTargetAtTriggerPoint) before I can test the editor extensions within Visual Studio 2015.

Does it means that the integration with VS2015 itself is working fine already (except the async part)?

This pull request only deals with the editor extensions. The other compatibility issues for VS 2015 are actually not due to the IDE itself, but rather the new build tools (MSBuild 14.0 and Roslyn-related differences in the IL).

Does it mean that #36 is all that we need for VS2015 support?
I already fixed issues with differentce in the IL in #74 (at least, everything that I know about this issue). If you have anything related to roslyn-based behavior, could you shared it with me?


Fix rivet config validate print flag as potitional argument

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

Current dependencies on/for this PR:

main

PR #175

PR #176

PR #177

PR #178   👈

This stack of pull requests is managed by Graphite.


SSL Error when working with custom host

api = webuiapi.WebUIApi(host='https://xx.gradio.live', port=7860, use_https=True)
api.img2img(images=[img1],                                         mask_image=img2,                                         inpainting_fill=1,                                         prompt="sks man face, 4k, realistic, detailed, HDR, 64k",                                         negative_prompt="nude, black and white, close up, cartoon, 3d, denim, (disfigured), (deformed), (poorly drawn), (extra limbs), blurry, boring, sketch, lackluster, signature, letters, watermark, low res, horrific, mutated, artifacts, bad art, gross, b&w, poor quality, low quality, cropped",                                         seed=-1,                                         steps=50,                                         controlnet_units=[unit1, unit2],                                         cfg_scale=5.0,                                         inpaint_full_res=True,                                         denoising_strength=0.7,                                         restore_faces=True)
Error
requests.exceptions.SSLError: HTTPSConnectionPool(host='https', port=443): Max retries exceeded with url: //-ecfa-4760.gradio.live:7860/sdapi/v1/img2img (Caused by SSLError(SSLEOFError(8, 'EOF occurred in violation of protocol (_ssl.c:1129)')))

how u solve this?

Hi @see2run,
To solve this you need to remove the https:// and set the port 443, https default port...
So, replace this
api = webuiapi.WebUIApi(host='https://whatever.gradio.live/', port=7860, use_https=True)
to this
api = webuiapi.WebUIApi(host='whatever.gradio.live/', port=443, use_https=True)
Best regards,
David Martin Rius


Enabling R8 Full mode breaks the demo apps

Describe the bug
When R8 full mode is on, the demo code breaks. This is important cause from gradle version 8.0+ R8 full mode is on by default
To Reproduce
Ive created a demo here. All you need to do is build the release variant of the snowplow-demo-compose
Expected behavior
Whether R8 full mode is on or off tracking should work
Screenshots
When I compile the demo with the android.enableR8.fullMode set to true, I get this error

If I still minify the app, but disable R8 Full mode, the app works normally
Device informatoin (please complete the following information):

Device: Any
OS: Any
Version: Any

Only requirement is that you minify your code using R8 full mode

Thanks for reporting this @Andr3Carvalh0, we will look into it!

Looks similar to an issue I've had in the past - https://issuetracker.google.com/issues/188703877


Needed Server System to Connect To

We need a server system for the exascalesystem.js file to connect to so we can solve millions of calculations in less than a second.

How does this work?

It will connect to a server with AJAX and will run things very fast.

@Narulacodes It's time for PHP!

YAY!


Easier ruby use

What are you trying to accomplish with this PR?
Make it easier to use our Ruby interface, i.e. DeployTask, RunnerTask, RenderTask and RestartTask by:

Moving requires around so that requiring a specific task (e.g. require 'kubernetes-deploy/deploy_task') actually gets you the dependencies you need to run it (and not dependencies you don't need).
Making all the tasks give you a logger out of the box if you don't pass one in. People rarely want to customize the logger (outside our tests), so making them construct one of our fancy loggers is unnecessary friction.
Making require kubernetes-deploy require ALL the tasks so that it still has a purpose in the world where the correct way to require any specific task--including DeployTask--is require kubernetes-deploy/TASK.

cc @stefanmb
What could go wrong?
The requires could be incomplete, causing the tasks to blow up in production when executing a line my manual tests didn't cover. I tried making the test files only require the code for their respective tasks, but in addition to being a bit of a mess, it was pointless because all but the RenderTask suite need to require DeployTask (i.e. most of the code) for setup purposes.
Todo

[x] Look carefully about which files each task is losing access to
[ ] Investigate the OJ conflict with Rails apps and consider requiring that file from common While a valid issue, this is not actually related to this PR.

After review but before shipping, test the tasks:

[x] invoke each of the tasks from the command line with various options to make sure none are broken
[x] invoke each of the tasks from a Ruby console session to make sure this PR works as stated
[ ] use cumulus-cat's Shipit task to test this branch

@Shopify/cloudx This is ready for review. @dturn kindly offered to take over getting it merged. I already manually tested invoking all the tasks with all possible args from the command line, plus requiring only the stated files in the console and successfully invoking the task from ruby. If changes are required after review, some of those tests may need to be repeated, but otherwise this just needs a test deploy using cumulus-cat.
We need to document our Ruby interface, both with inline docs and in the readme. That could be added to this PR, but at this point I'd be inclined to save it for Krane.

I wasn't able to test kubernetes-run in my local, will try to figure it
out

I used:
be exe/kubernetes-run cloud-portal-staging tierstaging-us-east1-2
flush-cache
On Wed, Aug 28, 2019 at 12:22 PM Jessie<EMAIL_ADDRESS>wrote:

🎩 in my local

kubernetes-deploy ✅

REVISION="4f7d6697fb5a20d4c960cd1cc6530774069489b6" bundle exec kubernetes-deploy cumulus-cat-production tier4 --template-dir=/Users/jessie.ning/src/github.com/Shopify/cumulus-cat/config/k8s/resources<EMAIL_ADDRESS>
kubernetes-render ✅

REVISION="4f7d6697fb5a20d4c960cd1cc6530774069489b6" bundle exec kubernetes-render --template-dir=/Users/jessie.ning/src/github.com/Shopify/cumulus-cat/config/k8s/resources<EMAIL_ADDRESS>
kubernetes-restart ✅

REVISION="4f7d6697fb5a20d4c960cd1cc6530774069489b6" bundle exec kubernetes-restart cumulus-cat-production tier4
😞 I wasn't able to test kubernetes-run in my local, will try to figure
it out
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Shopify/kubernetes-deploy/pull/487?email_source=notifications&email_token=AC5A4BSRXSWNA3NT2KVE7MDQG3GALA5CNFSM4HPLG3M2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5MGI7Q#issuecomment-525886590,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AC5A4BU7FBTEK4DLPL6CXTLQG3GALANCNFSM4HPLG3MQ
.


Sign message using an onchain key

@bumi this is different from https://github.com/getAlby/nostr-wallet-connect-next/issues/108 right? should the issue be in progress?

#108 is using the LN node's key. but not the key of an onchain wallet address.

I seem to be stuck with this one. Do you have any examples of the relevant methods in any of the APIs? I'm not sure I even understand how to get the onchain wallet address 🤔

Here is how to sign using the wallet key (which won't work in this case): https://github.com/getAlby/ldk-node/blob/main/src/wallet.rs#L457
Here is how to get an address: https://github.com/getAlby/ldk-node/blob/main/src/wallet.rs#L188
It might also be helpful to look at BDK: https://docs.rs/bdk/latest/bdk/wallet/struct.Wallet.html#method.get_address (note: we would want the address index to still auto-increment using AddressIndex::New)
I think we need to use the message_signing crate (what the LDK wallet uses) but instead of using the wallet node secret key, we need to derive a private key from the same derivation path as the generated onchain address (the AddressInfo has the index and the KeychainKind will be External).
I'm not sure the best way to do that (the most manual way I think would be to use the secp context: https://docs.rs/bdk/latest/bdk/wallet/struct.Wallet.html#method.secp_ctx but maybe there is a better way)
Does that help? you might need to dig in a bit further to see how the addresses are created and if you can somehow get the private key of the address.

Regarding how the derivation works, you can see the image here - each address will have its own derivation path (where the last item in the path is the address index): https://trezor.io/learn/a/what-is-bip32

I don't think we should derive the keys ourself. the LDK/BDK library should have an option to sign a message already.
if it does not have that, then we should not do this now.

hmm, seems this is not supported so far? https://github.com/bitcoindevkit/bdk/issues/989
but there is: https://github.com/bitcoindevkit/bdk/pull/601/files
Maybe we can take a minute to look into this and see how easy it is to implement. but I worry that it's too complicated, so we leave it.

Not prioritizing for now - this is more complicated than expected and not necessary


Review code

[x] Util methods don't need to be part of the class
[x] Object is destructed and then constructed again
[ ] Cache this array to string conversion
[ ] Remove waitForInputTime  this config option from class?

https://github.com/Shopify/hotshot/commit/aaaf4ea79ecfdab9c0a201adafe518e9fcabb14b

https://github.com/Shopify/hotshot/commit/fbac931b62786422d3fac777142c104eca49fa82

Not removing waitForInputTime option for now as its an optional config param anyway and gives some extra flexibility.


Update school eligibility to include City Technology Colleges

We determine state funded schools by two pieces of information: the school type group and the school type. We explicitly rule out schools that have a type group of independent as not being state funded. However it turns out that City Technology Colleges are state funded and
have a type group of independent.
We have another card in the backlog to look at any other types of state funded schools that we're missing from our rules.
City Technology Colleges have a phase of "not_applicable", however they do teach secondary age students. We can determine this by looking at the statutory high age for the school.
Example of a City Technology College: "Emmanuel College" (URN 108420)
irb(main):002:0> MathsAndPhysics::SchoolEligibility.new(School.find_by(urn: "108420")).eligible_current_school?
=> true
irb(main):003:0> StudentLoans::SchoolEligibility.new(School.find_by(urn: "108420")).eligible_current_school?
=> true

 Update school eligibility for CTC schools


Detecting attachment open from search list

When I try to search all emails with attachments, then click directly on a PDF (for example), internal Gmail viewer opens but it doesn't seem like email open event triggers. Well, email wasn't open afterall :)
Any way to listen to this event and get attachment ID?
Thank you in advance!

Not that I know of. Sorry. PRs welcome 😄


Weekly build triage for the week starting 2023/04/08

This week's build triage summary:

Date
Day
JDK Version
Pipeline
Pass/Build Fail/Test Fail
Triage Status
Triager
Breakdown

2023/04/nn
E.G.day
JDKnn
Link
50/3/19
Pending

Link

Note: "Test Fail" is for when all the "build" jobs passed (build, sign, installer, etc) but one of the test jobs failed and the
status propagated upstream to the build job. Note that "unstable" test job status can be considered a pass, as these are
triaged in more detail elsewhere (e.g. the adoptium/aqa-tests repo).
Comment template:
Triage breakdown for <Pipeline link>
Table of failures:
| Build Fail/Test Fail | Platform   | Failed Job | Response                            | Issue | Triage Status              | Notes  |
| --------------------- | ---------- | ---------- | ----------------------------------- | ----- | -------------------------- | -----  |
| Build Fail/Test Fail | e.g. win64 | Link       | New (Issue)/Existing (Issue)/Ignore | Link  | Pending/In Progress/Done | Borked |

Triage breakdown for https://ci.adoptium.net/job/build-scripts/job/openjdk8-pipeline/2528/
Table of failures:

Build Fail/Test Fail
Platform
Failed Job
Response
Issue
Triage Status
Notes

Build Fail/Test Fail
e.g. win64
Link
New (Issue)/Existing (Issue)/Ignore
Link
Pending/In Progress/Done
Borked

Build Fail/Test Fail
e.g. win64
Link
New (Issue)/Existing (Issue)/Ignore
Link
Pending/In Progress/Done
Borked

Build Fail/Test Fail
e.g. win64
Link
New (Issue)/Existing (Issue)/Ignore
Link
Pending/In Progress/Done
Borked

Build Fail/Test Fail
e.g. win64
Link
New (Issue)/Existing (Issue)/Ignore
Link
Pending/In Progress/Done
Borked

Build Fail/Test Fail
e.g. win64
Link
New (Issue)/Existing (Issue)/Ignore
Link
Pending/In Progress/Done
Borked

Build Fail/Test Fail
e.g. win64
Link
New (Issue)/Existing (Issue)/Ignore
Link
Pending/In Progress/Done
Borked

Build Fail/Test Fail
e.g. win64
Link
New (Issue)/Existing (Issue)/Ignore
Link
Pending/In Progress/Done
Borked

Build Fail/Test Fail
e.g. win64
Link
New (Issue)/Existing (Issue)/Ignore
Link
Pending/In Progress/Done
Borked

Build Fail/Test Fail
e.g. win64
Link
New (Issue)/Existing (Issue)/Ignore
Link
Pending/In Progress/Done
Borked

Triage breakdown for https://ci.adoptium.net/job/build-scripts/job/openjdk8-pipeline/2529/
Table of failures:

Build Fail/Test Fail
Platform
Failed Job
Response
Issue
Triage Status
Notes

Build Fail/Test Fail
e.g. win64
Link
New (Issue)/Existing (Issue)/Ignore
Link
Pending/In Progress/Done
Borked

Build Fail/Test Fail
e.g. win64
Link
New (Issue)/Existing (Issue)/Ignore
Link
Pending/In Progress/Done
Borked

Build Fail/Test Fail
e.g. win64
Link
New (Issue)/Existing (Issue)/Ignore
Link
Pending/In Progress/Done
Borked

Build Fail/Test Fail
e.g. win64
Link
New (Issue)/Existing (Issue)/Ignore
Link
Pending/In Progress/Done
Borked

Build Fail/Test Fail
e.g. win64
Link
New (Issue)/Existing (Issue)/Ignore
Link
Pending/In Progress/Done
Borked

Build Fail/Test Fail
e.g. win64
Link
New (Issue)/Existing (Issue)/Ignore
Link
Pending/In Progress/Done
Borked

Triage breakdown for https://ci.adoptium.net/job/build-scripts/job/openjdk11-pipeline/2336/
Table of failures:

Build Fail/Test Fail
Platform
Failed Job
Response
Issue
Triage Status
Notes

Build Fail/Test Fail
e.g. win64
Link
New (Issue)/Existing (Issue)/Ignore
Link
Pending/In Progress/Done
Borked

Build Fail/Test Fail
e.g. win64
Link
New (Issue)/Existing (Issue)/Ignore
Link
Pending/In Progress/Done
Borked

Build Fail/Test Fail
e.g. win64
Link
New (Issue)/Existing (Issue)/Ignore
Link
Pending/In Progress/Done
Borked

Build Fail/Test Fail
e.g. win64
Link
New (Issue)/Existing (Issue)/Ignore
Link
Pending/In Progress/Done
Borked

Build Fail/Test Fail
e.g. win64
Link
New (Issue)/Existing (Issue)/Ignore
Link
Pending/In Progress/Done
Borked

Triage breakdown for https://ci.adoptium.net/job/build-scripts/job/openjdk17-pipeline/668/
Table of failures:

Build Fail/Test Fail
Platform
Failed Job
Response
Issue
Triage Status
Notes

Build Fail/Test Fail
e.g. win64
Link
New (Issue)/Existing (Issue)/Ignore
Link
Pending/In Progress/Done
Borked

Build Fail/Test Fail
e.g. win64
Link
New (Issue)/Existing (Issue)/Ignore
Link
Pending/In Progress/Done
Borked

Build Fail/Test Fail
e.g. win64
Link
New (Issue)/Existing (Issue)/Ignore
Link
Pending/In Progress/Done
Borked

Build Fail/Test Fail
e.g. win64
Link
New (Issue)/Existing (Issue)/Ignore
Link
Pending/In Progress/Done
Borked

Triage breakdown for https://ci.adoptium.net/job/build-scripts/job/openjdk17-pipeline/669/
Table of failures:

Build Fail/Test Fail
Platform
Failed Job
Response
Issue
Triage Status
Notes

Build Fail/Test Fail
e.g. win64
Link
New (Issue)/Existing (Issue)/Ignore
Link
Pending/In Progress/Done
Borked

Triage breakdown for https://ci.adoptium.net/job/build-scripts/job/openjdk20-pipeline/179/
Table of failures:

Build Fail/Test Fail
Platform
Failed Job
Response
Issue
Triage Status
Notes

Build Fail/Test Fail
e.g. win64
Link
New (Issue)/Existing (Issue)/Ignore
Link
Pending/In Progress/Done
Borked

Build Fail/Test Fail
e.g. win64
Link
New (Issue)/Existing (Issue)/Ignore
Link
Pending/In Progress/Done
Borked

Build Fail/Test Fail
e.g. win64
Link
New (Issue)/Existing (Issue)/Ignore
Link
Pending/In Progress/Done
Borked

Build Fail/Test Fail
e.g. win64
Link
New (Issue)/Existing (Issue)/Ignore
Link
Pending/In Progress/Done
Borked

Any reason we want to have a weekly triage for build?
if we want to do this, need to keep it update per week. otherwise, having tickets opening without outcome data is just waste.
each jdk version should only get one link from jenkins if it is from weekly run.
e.g jdk8 nr. 2528 is weekly, nr. 2529 is not from weekly, the test cases running are different


Why perform crop in validation and test?

Dear author, thanks very much for this excellent repo.  But I am confusing the crop operations in validate and test, as shown in the attached figure.  What's the purpose of this operation? Is it a form of data augmentation or a trick to improve the test performance? I can't find any explanation in the paper.
Also, can you give me some advice on the data augmentation? Should we use random crop? i.e.  to resize the input image to a larger size and randomly crop a specific sized?
I read in the ACSCP paper that says such operation is not appropriate since the image interpolation may change the crowd count from a density map.  What's your view on this matter?
Looking forward to your answer!@gjy3035

Our repo processes high-resolution images (~2048pixels). Some networks need more than 12GB memory. So we need to crop the test images with a small size.
Our interpolation operation is pre-processed before the training phase and saves the dot map, and the cropping is on the dot map. Thus, the counting number is just suffered from a very slight fluctuation.

Thanks very much. I see that now.


TypeError: undefined is not a function, js engine: hermes

I installed correctly react-native-reanimated and I have the exact issue of:
https://github.com/mrousavy/react-native-vision-camera/issues/798
but can't find a way to fix it, even moving around the import of react-native-reanimated.
The full stack is:
Error: ENOENT: no such file or directory, open '/Users/francescoclementi/Documents/development/parkingmgmt-native/http:/localhost:8081/index.bundle?platform=android&dev=true&minify=false&app=com.parkingmgmtnative&modulesOnly=false&runModule=true'
    at Object.openSync (fs.js:476:3)
    at Object.readFileSync (fs.js:377:35)
    at getCodeFrame (/Users/francescoclementi/Documents/development/parkingmgmt-native/node_modules/metro/src/Server.js:919:18)
    at Server._symbolicate (/Users/francescoclementi/Documents/development/parkingmgmt-native/node_modules/metro/src/Server.js:992:22)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
    at async Server._processRequest (/Users/francescoclementi/Documents/development/parkingmgmt-native/node_modules/metro/src/Server.js:403:7) {
  errno: -2,
  syscall: 'open',
  code: 'ENOENT',
  path: '/Users/francescoclementi/Documents/development/parkingmgmt-native/http:/localhost:8081/index.bundle?platform=android&dev=true&minify=false&app=com.parkingmgmtnative&modulesOnly=false&runModule=true'
}
Error: ENOENT: no such file or directory, open '/Users/francescoclementi/Documents/development/parkingmgmt-native/http:/localhost:8081/index.bundle?platform=android&dev=true&minify=false&app=com.parkingmgmtnative&modulesOnly=false&runModule=true'
    at Object.openSync (fs.js:476:3)
    at Object.readFileSync (fs.js:377:35)
    at getCodeFrame (/Users/francescoclementi/Documents/development/parkingmgmt-native/node_modules/metro/src/Server.js:919:18)
    at Server._symbolicate (/Users/francescoclementi/Documents/development/parkingmgmt-native/node_modules/metro/src/Server.js:992:22)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
    at async Server._processRequest (/Users/francescoclementi/Documents/development/parkingmgmt-native/node_modules/metro/src/Server.js:403:7) {
  errno: -2,
  syscall: 'open',
  code: 'ENOENT',
  path: '/Users/francescoclementi/Documents/development/parkingmgmt-native/http:/localhost:8081/index.bundle?platform=android&dev=true&minify=false&app=com.parkingmgmtnative&modulesOnly=false&runModule=true'
}
 ERROR  TypeError: undefined is not a function, js engine: hermes
 ERROR  Invariant Violation: Module AppRegistry is not a registered callable module (calling runApplication). A frequent cause of the error is that the application entry file path is incorrect.
      This can also happen when the JS bundle is corrupt or there is an early initialization error when loading React Native., js engine: hermes
 ERROR  Invariant Violation: Module AppRegistry is not a registered callable module (calling runApplication). A frequent cause of the error is that the application entry file path is incorrect.
      This can also happen when the JS bundle is corrupt or there is an early initialization error when loading React Native., js engine: hermes

Check this https://www.youtube.com/watch?v=kOYP2Xun_6o&list=PLQhQEGkwKZUrempLnmxjt7ZCZJu1W3p2i&index=77


add docs about compiling

why default is npm run compile and what to do if not using that. link to ent.yml option
https://github.com/lolopinto/ent/pull/55 is relevant

I copied this script into my package.json, but don't really use it. Should I be?

depends on how you end up converting typescript -> js and if you use tsconfig-paths and have src/foo/ paths. if you're just using standard tsc, you'll need it. if you're using babel or some complicated js stack thing ,you're probably fine
if you have ent.yml, and codegen.relativeImports is true e.g. https://github.com/lolopinto/ent/blob/main/examples/simple/ent.yml#L15-L16, don't need it
basically, the issue is typescript supports pretty paths and doesn't provide away to maintain those paths when running tsc which means your javascript didn't work.
at the time, I didn't want to deal with maintaining relative imports for every file so i worked around it with the compiler. i eventually had to support relative imports so should probably have changed the default at that point to relative but didn't because I prefer the absolute paths


Update custom key bindings example

In my testing selfinsert doesn't seem to work, it inserts one white-space character instead of an actual tab, changing it to insert makes it work perfectly.

I found that this example didn't work on windows, I added a fix but there is still a bug in rustyline where inserting a tab in windows inserts a tab but the cursor doesn't move, I added a workaround for it (inserting 4 spaces).


Update contents.json

[x] Project URL:
[x] Update contents.json instead of README
[x] One project per pull request
[x] Project added at the end of the list (a script sorts projects automatically)
[x] Avoid iOS or open-source in description as it is assumed
[x] Use this commit title format if applicable: Add app-name by @github-username
[x] Use approved format for your entry

Seems screenshots part I forget to quote my last file


Skip image conversion when importing from ovirt

When importing a VM from ovirt provider the images (disks) don't require
conversion to kubevirt. The virt-v2v pod and execution should be skipped
to save time and resources.

The itinerary supports conditionally skipping steps, which may allow you to achieve what you want without having to duplicate the itinerary. Consider perhaps adding a RequiresConversion flag to the conversion steps, and updating the Predicate.Evaluate() function to operate on the flag.
	coldItinerary = libitr.Itinerary{
		Name: "",
		Pipeline: libitr.Pipeline{
			{Name: Started},
			{Name: PreHook, All: HasPreHook},
			{Name: StorePowerState},
			{Name: PowerOffSource},
			{Name: WaitForPowerOff},
			{Name: CreateDataVolumes},
			{Name: CreateVM},
			{Name: ScheduleVM},
			{Name: CopyDisks},
			{Name: CreateGuestConversionPod, All: RequiresConversion},
			{Name: ConvertGuest, All: RequiresConversion},
			{Name: PostHook, All: HasPostHook},
			{Name: Completed},
		},
	}

//
// Evaluate predicate flags.
func (r *Predicate) Evaluate(flag libitr.Flag) (allowed bool, err error) {
	switch flag {
	case HasPreHook:
		_, allowed = r.vm.FindHook(PreHook)
	case HasPostHook:
		_, allowed = r.vm.FindHook(PostHook)
	case RequiresConversion:
		allowed = r.context.Source.Provider.Type() == api.VSphere
	}

	return
}


[Question]: How to be smoother when i'm displaying my marker in driver mode?

Please check the following before submitting a new issue.

[X] I have searched the existing issues.
[X] I have carefully read the documentation.

Please select for which platform(s) you need help

[X] Android
[ ] iOS
[ ] Linux
[ ] macOS
[ ] Web
[ ] Windows

Your question
I'd like to know how to get a more natural version of my marker's movement.
Here are two examples:
Here, my version of flutter map + geolocator + marker

Here a smooth version of OsmAnd app with the same route:

How can I make moving the marker more natural? I'm using the Geolocator stream, but it refreshes every 3-5 seconds.
Thanks
Version
last

any updates ?
can i manipulate the update interval of Geolocator ?
i have tried to implement a timer to run every second and in each iteration I'm requesting the current location , but every 3 to 5 seconds to get a new location update


Is it possible to convert windows emoji to apple emoji using your library?

I work on Windows, I write posts in the project through markdown,
I insert Windows emoji there,
I would like to convert emoji to apple style at the output in markdown files,
as Telegram does
GIF how it works in Telegram
https://imgur.com/a/dq2fzTq
My code where I convert markdown to html
https://github.com/1alexvash/AlexCodeBlog/blob/master/helpers/markdownToHtml.ts

its not, this library is just wrapping the emojis from emojipedia as a react component and is not capable of doing such thing.

Correct, closing.


Refactor CSV has_header inference

@mrocklin this could use a bit of review when you get a chance

things are passing on all win64 py27 and py34 as well as osx py27 and py34


Make the AppVeyor shell script stop on error

(Currently it should be failing on generateprojects.sh, but it's not)
This PR will include a follow-up PR to make it stop failing, but I want to see it fail first.

(This failed as expected after just the first commit.)


@derivedFrom fields null if id: Bytes!

Derived fields of entities are null if the source entity has an id of type Bytes
Example:
Before:
type ERC721Campaign @entity {
  id: ID!
  //...
  claims: [ERC721Claim!]! @derivedFrom(field: "erc721Campaign")
}

type ERC721Claim @entity(immutable: true) {
  id: ID!
  //...
  erc721Campaign: ERC721Campaign!
}

After:
type ERC721Campaign @entity {
  id: Bytes!
  //...
  claims: [ERC721Claim!]! @derivedFrom(field: "erc721Campaign")
}

type ERC721Claim @entity(immutable: true) {
  id: ID!
  //...
  erc721Campaign: ERC721Campaign!
}

only changed the ERC721Campaign.id from ID to Bytes and made corresponding changes to mappings
now both the below asserts that used to work are erroring with Cannot return null for a required field.
assert.assertNotNull(erc721Campaign.get("claims"))
assert.assertNotNull(erc721Campaign.claims)

logStore() doesn't contain claims List either

Seemingly related issue:
Following assertion works fine:
assert.assertNotNull(erc721Claim.get("erc721Campaign"))

But following fails with error:
assert.assertNotNull(erc721Claim.erc721Campaign) // intellisense says type is `Bytes`
/*
ERROR TS2322: Type '~lib/@graphprotocol/graph-ts/common/collections/ByteArray | null' is not assignable to type '~lib/@graphprotocol/graph-ts/common/collections/ByteArray'.

     assertTrue(value != null);
                         ~~~~
 in ~lib/matchstick-as/assembly/assert.ts(70,25)
*/

The stacktrace is also confusing with the above error

Derived relations handling has been changed in https://github.com/LimeChain/matchstick/releases/tag/0.6.0-rc.3


remove Windows TERM env var hack and -Zmiri-env-exclude

The hack should not be needed any more since https://github.com/rust-lang/rust/pull/100206. And that also mostly removes the need for -Zmiri-env-exclude -- if needed, users can still achieve the same by running (unset VAR; cargo miri test).
I am keeping -Zmiri-env-forward since it is still useful, e.g. to have RUST_BACKTRACE=full set in an otherwise deterministic execution.
@rust-lang/miri any objections to removing -Zmiri-env-exclude?

Somehow the macOS runner keeps taking more than a second for a few lines of code?!? But this only started recently. Very strange.

@bors r=oli-obk

:pushpin: Commit dd80b1aaba5ae373f22de2318562108d0177aa11 has been approved by oli-obk
It is now in the queue for this repository.

:hourglass: Testing commit dd80b1aaba5ae373f22de2318562108d0177aa11 with merge dfa6f8894e6d56f3c01062f0735f87a70e180fd0...

:sunny: Test successful - checks-actions
Approved by: oli-obk
Pushing dfa6f8894e6d56f3c01062f0735f87a70e180fd0 to master...


Fix backward compatibility with pickles before v22.2.0

Summary
Unfortunately we're using django-redis to cache some attrs instances and the change to make __getstate__ and __setstate__ use dict values instead of tuple values prevents reading any values from the cache when updating to attrs>=22.2.0. We get an AttributeError raised for all attributes.
This happens because the tuple of values stored in the original pickle is checked for the name of the attribute and so none of the attributes are set on unpickle.
To address this I've made a change so that __setstate__ will still be able to handle values pickled as tuples allowing existing pickles to be unpickled.
The test just contains a pre-pickled value due to the complexities around tying to mock methods on a slotted as documented^1.
I realise that documentation also mentions that we should "think twice" before using pickle, but sometimes those decisions predate our involvement in a project! In addition, pretty much all of Django's cache implementations are built around using pickle by default. This change will allow an easier path to upgrade by unpickling and repickling all values in the cache.
Regression in 89a890a3262273514619d1881c6a8b0fe26c66ac.
Pull Request Check List

[x] Added tests for changed code.
Our CI fails if coverage is not 100%.
[x] New features have been added to our Hypothesis testing strategy.
[x] Changes or additions to public APIs are reflected in our type stubs (files ending in .pyi).

[x] ...and used in the stub test file tests/typing_example.py.
[x] If they've been added to attr/__init__.pyi, they've also been re-imported in attrs/__init__.pyi.

[x] Updated documentation for changed code.

[x] New functions/classes have to be added to docs/api.rst by hand.
[x] Changes to the signature of @attr.s() have to be added by hand too.
[x] Changed/added classes/methods/functions have appropriate versionadded, versionchanged, or deprecated directives.
Find the appropriate next version in our __init__.py file.

[x] Documentation in .rst files is written using semantic newlines.
[x] Changes (and possible deprecations) have news fragments in changelog.d.
[x] Consider granting push permissions to the PR branch, so maintainers can fix minor issues themselves without pestering you.

Is there any way to add a warning when someone uses the antipattern of persisting pickles across versions? I think a lot of people don't realize that this is a profoundly bad idea. If attrs is going to enable this behavior (even on a best-effort basis), it might be a good idea to at least tell people they are doing something wrong here.

Cc @djipko for overall assessment

Is there any way to add a warning when someone uses the antipattern of persisting pickles across versions?

Across versions - in a general way - sounds difficult as you'd need to store the version in the pickle itself and then you may still suffer from not being able to unpickle in older versions anyway - it'd be backward incompatible. The only viable way would be to store (<version>, <instance>) so you could then compare the <version> in __setstate__() before handling the <instance>...
...but then we'd be changing the state again and we'd need to know that the tuple contained a version in the first item rather than being the tuple state from a pre-v22.2.0 version of attrs.

I think a lot of people don't realize that this is a profoundly bad idea.

This is true. Others of us are saddled with these issues until we have resources to be able to undo decisions made by others in the past.

If attrs is going to enable this behavior (even on a best-effort basis), it might be a good idea to at least tell people they are doing something wrong here.

This. I think a nice big admonition in the documentation would be a good idea. A documentation search yields very little - one small warning in the slotted classes glossary entry. It may also be worth stating that some cache implementations, e.g. Django's caching framework, make use of pickle serialization by default, which could lead to compatibility issues across versions.
Further, I know that whether this is considered public API is a possible grey area, but given the fragility it's probably worth mentioning backward incompatible changes to pickle serialization in the release notes in future. That linked comment did also say "So if you can make it compatible" which I would argue didn't happen, hence this PR.

Another thought: Do we want to add a DeprecationWarning to the tuple branch?

I think that's not great because it would warn about exactly one version change, as you wrote. Kinda a mix of enough to be annoying, but not enough to solve the problem.
While I agree with Paul that it's not great to pickle across versions, with attrs it shouldn't be a problem and I bet people do it and love it and are gonna yell at us if we annoy them (just as they yelled at us about the 3.6 warning).
IOW I agree, but I'm afraid it's too disruptive.
I think I'm fine with the code as it is. I'd just like @djipko to give it a look to ensure we're not breaking something only he knows and then it's ready to merge.

While I agree with Paul that it's not great to pickle across versions, with attrs it shouldn't be a problem and I bet people do it and love it and are gonna yell at us if we annoy them (just as they yelled at us about the 3.6 warning).
IOW I agree, but I'm afraid it's too disruptive.

I mean, I think people shouldn't save pickles to disk at all, but :shrug:
FWIW, this issue also has blocked me from upgrading attrs internally for now, but I don't mind when this happens so much because it's a decent way to ferret out programs that are inappropriately using pickle. There are a bunch of other ways that this sort of thing can go wrong in much more subtle ways, so I appreciate when things break a bit more loudly.
Also, I understand the perspective of "people do it and love it", but I suspect that in reality people are neutral about it. They think pickle is the way you serialize stuff and don't think about it until it breaks, at which point their reactive "You broke me" emotions kick in. It's kind of a thankless job to be like, "Oops you were doing it wrong sorry pickle exists" but it's almost certainly educational.
That said, in some ways I think you are a kinder person than me and not as inclined to say, "This is for your own good." when breaking private APIs, and I'm not going to lobby too hard for just letting this stuff break. I figured this point where we know that someone is relying on cross-version unpickling might be a good place to put a warning (annoying enough to show people they are doing the wrong thing but not difficult to silence or fix, and with no blast radius outside of this particular subset), but it's not a hill I'm interested in dying on (or even just getting grass stains on my knees on).

I think the change itself is fine and something I considered doing in the first place when I proposed to move to dict. If it's breaking enough people and stopping them from upgrading, even though they are doing something that's known to be "a bad idea" (tm), on the whole, that's a bad thing.
But as demonstrated in the issue I raised, using tuple is inherently unsafe - now everyone's just broken which is, in some ways better than their code doing the wrong thing (even if it's an edge case that doesn't come up as often).
With this change, everyone is still vulnerable to the original issue though which is not great either. Here's what I propose if @hynek agrees - let's have an issue open for say next version (v23.0.0 or whatever) to really remove tuple then? While I don't doubt this will still break some people even then - most folks would have had enough time to re-process data if there are any stragglers.
I'd be happy to keep an eye on such issue and put up a fix and land it when safe!

...even though they are doing something that's known to be "a bad idea" (tm)...

I know, I know! 🙈 I'm the victim, I promise! 😛
I'm happy if you want to remove it again in a major version bump - I'd expect nothing less 😄
What this provides is a (few) version(s) where we can read the tuple and dict versions and write the dict version only. That allows for a seamless upgrade of cache values to the new pickle format - via a load-and-dump cycle of the cache - which is not currently possible.
Yes, the original issue is still a problem in a sense, but only as far as reading existing pickles goes. With a load-and-dump upgrade this potential issue will go away for us (although our structure is not currently at risk of changing).

Any chance of cutting a dot release with this?

One thing to note before cutting an official release with this patch - if code was susceptible to the original issue #1004 i.e. unpickling will assign wrong data to an attribute, and someone runs the newly cut release, that reads and then saves data again, the saved pickled data will now be permanently corrupted (read as tuple which does the wrong thing, but then saved as dict).
Releasing it officially will make it more likely people hit this.
Now I am not saying not to release it - ultimately saving pickled data is very error prone anyway (hence this patch) - but I feel silently corrupting data is a slightly worse kind of edge case then just loudly breaking.

Why isn't that a great lose-lose scenario. ;)
My impression of the situation is that people who will take advantage of this bw-fix are probably holding back their upgrades and had all the time in the world to fix it. There's only so much we can do...

My impression of the situation is that people who will take advantage of this bw-fix are probably holding back their upgrades…

Yes, I am.

…and had all the time in the world to fix it.

No, I don't. Storing pickles was a choice made by somebody else long before I came along. Although wrong, it worked "fine", then it got broken by a backward incompatible change. attrs makes big claims of backward compatibility and no (or little) mention of any exception with regard to pickling. Fixing this issue by manually rewriting all stored data to be stored serialised in a different format is way down the list of priorities. (It'll happen eventually…)

Releasing it officially will make it more likely people hit this.

I'm sorry, but I think this is misleading. It'd only be the case if you upgraded and reordered attributes. Having this fix released would allow for stored pickles to be replaced automatically and gradually with a "safer" version. (Yes, we'd still need to not reorder attributes until we were sure that all stored data had been upgraded.)
I just get the impression that the argument being made is that we should just break so hard that we intentionally make everyone's lives difficult rather than stick to the promises of backward compatibility and issue a big fat warning.

That's what I meant. You either held back and have the same pickles as before, or upgraded and fixed your pickles and therefore aren't affected anymore.

Sorry, I didn't mean to come across so grumpy!
Yeah, it's definitely lose-lose 🤷🏻♂

I also think we should release this personally but wanted to make sure we are considering all the angles. It is indeed a lose lose.

23.1.0 is on PyPI


Stellar: Receive and use a buildPaymentID

@keybase/react-hackers CC @mlsteele
This PR just:

asks for a buildPaymentID when opening the send form

keeps track of it and passes it down to future calls to buildPayment and sendPayment

invalidates ("stops") it when the form closes

(And then core will prevent us from reusing it, sending a stopped one, sending it if the amount is different from the built amount, and so on.)
BuildPaymentIDs aren't used for requests.
I would merge this into master alongside the reviewPayment PR, just splitting them up for reviewability.

Was gonna merge this alongside reviewPayment, but it looks like it's useful (prevents double send etc) by itself and reviewPayment's gonna take a while longer on the Core side, so I'll merge it now.


Check if softdevice is programmed

Not sure if there is an easy way to do this (or any way) but it would be AWESOME if the flashing scripts would run make from-scratch automatically for you if the softdevice hasn't been programmed because I ALWAYS forget to.

Definitely possible, but it would add the time overhead of doing a JLink
Read of the entire softdevice to every flash and comparing it to the
current softdevice. Unless we write a softdevice checksum somewhere...
On Sep 30, 2015 3:46 PM, "Brad Campbell"<EMAIL_ADDRESS>wrote:

Not sure if there is an easy way to do this (or any way) but it would be
AWESOME if the flashing scripts would run make from-scratch automatically
for you if the softdevice hasn't been programmed because I ALWAYS forget to.
—
Reply to this email directly or view it on GitHub
https://github.com/lab11/nrf5x-base/issues/3.

Done. Commit 121778e554289055c8e03b0e1fe3da422a647c48 updates nrf51-pure-gcc-setup, which has been updated to check and upload the softdevice whenever necessary in commit d8dc8bb43f3834b27ca724ebb7c3fb78b674b9fa


my script file can not run by crontab

I have a script file can be run in the shell, but not by crontab timed run.
The script file content is :
#! /bin/sh
/usr/local/hadoop/bin/hadoop jar /home/yst-0.0.1-SNAPSHOT.jar cmb.yst.LogClassify
The crontab file content is :
0 * * * * /home/yst/test.sh
The purpose of the script file is run every morning hadoop of mapreduce program

Sorry but I don't understand the issue here.

@Tracy6465 does this cronjob work when manually set in crontab? If not, then it's not really a problem with this library.
A couple things that might help:

Check the system log for errors.
 cat /var/log/syslog

Make sure the crontab's user account has permission to execute the script, and all directories from root.
 chmod 755 /home/yst /home/yst/test.sh

You said that you want the script to "run every morning" but 0 * * * * means to run every hour on the hour. To run every day at 1:00 AM would look like this:
 0 1 * * * /home/yst/test.sh


Fixes #5105; Don't hardcode root as navigation action path

The plone.restapi navigation endpoint will compute a navigation root from a context path, but the problem is that Volto will trigger the navigation endpoint either on root or on the lang folder.
https://github.com/plone/plone.restapi/blob/ed070e0769c4ac3efda05448db8846f61dae255c/src/plone/restapi/services/navigation/get.py#L40
https://github.com/plone/volto/blob/4523b13d6586891b9dad7db1caedaab5f6f7dd4b/src/components/theme/Sitemap/Sitemap.jsx#L115C21-L115C21
https://github.com/plone/volto/blob/4523b13d6586891b9dad7db1caedaab5f6f7dd4b/src/actions/navigation/navigation.js#L21

this should also be taken into account in https://github.com/plone/volto/pull/3537

@tiberiuichim revisiting this PR in order to do a more complete use of the navroot endpoint (#3537), I see quite easy to change the usage of isMultilingual and toBackendLang here.
But I don't get at all how this could be done for the SSR part (I guess, that's what it's done in the asyncConnect part, right?
Perhaps, if #3537 is merged, I can prepare a PR bringing the usage of @navroot here and we can discuss there how to bring it also to the SSR part.


Keybinding for stack adjust graph view and update of adjust value display in unresolved stack view

Version and Platform (required):

Binary Ninja Version: Version 3.2.3913-dev
OS: Windows
OS Version: 10
CPU Architecture x64

Bug Description:
There does not seem to be a way to enter the stack usage graph again after "fixing" it. However it seems that it might still be possible to adjust it in disassembly views, but getting back to the graph would be nice.
Also inside the graph view the adjust value does not update.
call    sub_423540  { Adjust by 0 }    -> change adjust via right click menu to 8
still shows adjust by 0, until the graph view is closed and opened again.
Tested on this years flare-on(9) challenge 5, function sub_404680.
When trying to fix the stack adjustments I made some errors, but it seems I adjusted everything, so the button to enter the graph view disappears, however I could not find any way to enter that view again.
(side note, in general it seems I have to test this sample more, did not get the function calls in that function to display proper parameter in HLIL at all)
Expected Behavior:
A keybinding / command palette option to enter the stack adjust graph view.
Update of the adjustments in the graph view, without the need to reopen them
I hope this is clear enough, the reopen of the view might be considered a feature, but the update of the Adjust value seems like a bug, so I hope it is fine to have this as one issue.

The reason for this is that the stack adjustment graph removes nodes as they're resolved. BN doesn't see a broken stack adjustment it has literally nothing to display. It seems what you'd like is simply a graph of the stack adjustments and not the unresolved stack adjustments.  This can be seen in the low level il if you use the command "Show Stack Pointer Value"

Which gives you the following annotations:


do-syntax

import qualified Plutarch.Monadic as P

P.do
  PTxInfo y <- pmatch (x :: Term s PTxInfo)
  PTrue <- pmatch $ pcon PFalse -- calls `P.fail errormsg` if there's not a match, which is `ptrace errormsg perror`.
  z <- P.let $ x + y
  ptrace "ahduawhdw"
  perror

I like this syntax.

I've tried not to do anything that will cause the base library to fail to compile with GHC 8.10, albeit the tests won't work obviously.

should be fine, plutus itself is probably likely to start requiring ghc9 anyway


Add info_text for Y chromosome xrefs

Description
The core DB has dangling object_xref records related to Y-PAR genes after the xref pipeline is run on the new core DB (containing Y-PAR genes and and genes on patches).
Use case
When running the xref pipeline using the core DB with the new Y-PAR genes, xrefs are duplicated from X-PAR ones and dumped into the file created by CoordinateMapper.pm in the dump_xref method. However, when this data is uploaded into the core DB, these duplicated xrefs cause a duplicate unique key error in the database UNIQUE KEY id_index (dbprimary_acc, external_db_id, info_type, info_text, version). Also, since the object_xref data is uploaded before the xref is, all object xrefs telated to these duplicated xrefs would already be added. This leads to having dangling object xrefs int he core DB with no parent xref rows. To fix that, a string "Y Chromosome" has been added into the info_text field (which was previously kept empty) to differentiate the Y-PAR xrefs and allow inserting them into the DB.
Benefits
No duplicate unique key error, leading to no dangling object_xref records.
Possible Drawbacks
N/A
Testing
Have you added/modified unit tests to test the changes?
If so, do the tests pass/fail?
Have you run the entire test suite and no regression was detected?
Test suite is failing due to the Perl::Critic issue which was fixed in #635 . Once that is merged in, the tests can be re-run.

Coverage decreased (-0.06%) to 82.259% when pulling d3572bc9fb3fc4d916344076bdf3ae00c78154a1 on fix/xref_ypar into ae51b636c20a5f5a45a82544a6cfe31f62d391d7 on main.


Chore/chore update

Replace all hash algorithm to fxhash
Remove shared crate, using workspace.dependency to control common library version

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: JSerFeng:x: fengyu.shelbyfengyu.shelby seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Add cursor to schemes in relation to the issue #391

#391

@znck could you please merge this pr? would love to see Cursor support


solveFor-var in exponent not recognized, equation not solved

solve(x=2^x/4,x) gives back a term still containing x, instead of 2 numerical values

Fixed in 73789742e9b0cbc2fab3ab9f8fdb2915d2930b2d


The first example uses 30% of the cpu.

Why? It's just a green screen...

I changed the while loop for the event_loop.run_forever method showed in the window.rs example, it is working and isn't using 30% cpu

I still worried about the cpu use, it in idle, is using 6%, when I resize uses 12, I don't know if it's just I being a morron...

Eventloop v2 prolly helps this. If you are still concerned over cpu use, reopen


batchget with parse: true returns empty array

Describe the bug
Unmarshal doesn't work with batchGet, setting parse to true results in empty array.
To Reproduce

Steps to reproduce the behavior:

Clone this repository. Must test against the current master branch in the repository.
Edit your reproducible, MINIMAL, stand-alone test case into the test/debug.ts file.
Run via jest debug or run VS code in the top level directory.

If you don't provide a complete debug.ts that demonstrates your issue, then your issue will not receive priority.

Sorry! Feels like a lot of work to do to just report an issue
Schema
const Schema = {
  format: "onetable:1.1.0",
  version: "1.0.0",
  indexes: {
    primary: { hash: "PK", sort: "SK" },
    gs1: { hash: "GSI1PK", sort: "GSI1SK" },
  },
  models: {
    Song: {
      PK: { type: String, value: "USER#${username}" },
      SK: { type: String, value: "SONG#${id}" },
      GSI1PK: { type: String, value: "SONG" },
      GSI1SK: { type: String, value: "SONG#{id}" },
      username: { type: String, required: true },
      genre: { type: String, enum: Object.values(Genre) },
      id: { type: String, required: true },
      albums: {
        type: Array,
        default: [],
      },
    },
    Album: {
      PK: { type: String, value: "USER#${username}" },
      SK: { type: String, value: "ALBUM#${id}" },
      GSI1PK: { type: String, value: "ALBUM" },
      GSI1SK: { type: String, value: "ALBUM#{id}" },
      username: { type: String, required: true },
      genre: { type: String },
      id: { type: String, required: true },
      songs: {
        type: Array,
        default: [],
      },
    },
  },

How I am fetching
  const batch = {};

  for (const album of albums) {
    await Album.get({ id: album.id, username: userId }, { batch});
  }

  const albumsRes = await SongTable.batchGet(batch);

  console.log(JSON.stringify(albumsRes, null, 4));

What do I get in response
        "songs": {
            "L": [
                {
                    "M": {
                        "title": {
                            "S": "there there"
                        },
                        "id": {
                            "S": "1234"
                        }
                    }
                }
            ]
        },

Expected behavior
It should return the parsed object like
{
  GSI2PK: 'LIKE_COUNT',
  songs: [ { title: 'there there', id: '1234' } ],
  GSI1PK: 'ALBUM',
  release_date: '2022-05-21',
  SK: 'ALBUM#01G3JZ01ABV6BF1WRJQH1VVP90',
  GSI1SK: 'ALBUM#01G3JZ01ABV6BF1WRJQH1VVP90',
  PK: 'USER#4114fcd0-9659-4ee8-9395-a35a79cdcdfd',
  album_art: 'ziki-images/defaultCover.png',
  GSI2SK: 0,
  title: 'Test Album'
}

Environment (please complete the following information):

OS - manjaro linux
Node Version - v16.14.2
OneTable Version - ^2.3.6
TypeScript Version - ^4.6.4

pass parse: true on options for batchGet method

Did you even read my issue properly?

well, the main issue here is parse: true returning empty array, and not calling batchGet without parse not parsing, that is the expected behavior, rename the issue so people will be aware of the real issue "batchget with parse: true returns empty array"

I'll try to debug here and find why it would happen

I'll rename the issue, but you should not blame someone else because you didn't read the first two lines of the issue.

Works here in our batch unit test. BatchGet with parse: true is working.
The reason we ask for a test case is exactly for this situation where it works for us, but not for you.
I'll close this issue, but please feel free to reopen with debug.ts that demonstrates the issue.

@mobsense aren't you guys mocking DynamoDB in the unit test? Is it testing against a real database?

Yes and yes.

I don't if this is was your case, but I was having a similar problem and the reason for {parse: true} to return an empty array was that I had some entries on database (entries that I was trying to get) without the field "_type".
I had created this entries manually. Maybe your records are just inconsistent for the library?


Use Array API instead of Numpy

Will make it more interoperable with other libraries

You can assign it to myself @epg323. Working on it already.

That would be good, welcome

That would be terrific

There's plenty of issues below that weight too, including readthedocs documentation and similar
Welcome!


How to Transfer Text messages from Samsung S4 to S7

As you know, samsung galaxy s4 have been out, cause with the new samsung galaxy s7 or galaxy s7 edge, i prefer to choose the new samsung s7/s7 edge.
But lots of sms text messages have stored in my old samsung galaxy s4, how can i import all my text messages from samsung galaxy s4 to s7/s7 edge?
Method to Transfer text messages from samsung galaxy s4 to samsung s7/s7 edge:
Phone to Phone Transfer, you can easily transfer data text messages from Samsung galaxy S3/S4/S5 to new Samsung galaxy S7, if you don’t know how to use this Mobile Transfer to transfer messages from old Samsung galaxy phone to new Samsung galaxy S7, please follow the next easy steps to solve your problem.
Steps to Transfer text messages from Samsung s4 to Samsung S7/S7 Edge:
Step 1: Launch Mobile Transfer on your PC
Step 2. Connect the Samsung Galaxy S4 and Galaxy S7 to the PC
Step 3. Transfer text messages from Samsung galaxy S4 to Samsung galaxy S7
More info:
Transfer Text Messages from S3/S4/S5/S6 to S7/S7 Edge
How to Transfer Contacts from Samsung Galaxy to Galaxy S7
Video guide:
https://youtu.be/oyO_UBuOQXA

Phone Transfer is the all-in-one phone to phone transfer program which can sync all data from one Android devices to another in a click. So, you can easily transfer text messages from Samsung S4 to S7/S7 Edge with its helps.
Related Tutorial:
Transfer contacts from iPhone to Samsung S7 edge
Transfer contacts from HTC to Samsung S7 edge
Transfer all data from Samsung to S7 edge

Here I got two solutions for all of you:
With the tool called Android Transfer: download and run it on your PC, connect both your Samsung devices, this tool can manage two Android devices at the same time, first you can transfer messages from S4 to computer, and then you can import them to your S7
With the tool Phone Transfer: download and run it on your PC,  connect both your Samsung devices, after scanning, you can move data from one to another directly.

You can use Samsung kies to transfer data from your Samsung S4 to pc and save them, then connect your S7 to pc, some data can be saved to S7 from pc.
If you have Google account, sign in to sync data from S4, then download them to your S7.
Or, you can also try some phone transfer programs, just link your two phones to pc together, and transfer data between them.

Samsung Transfer is an useful phone to phone transfer tool designed by Samsung, Android, iOS. By using it, you can transfer all data from Samsung to Samsung without any data loss, including contacts, music, videos, photos, text messages, apps, etc.
How to transfer data from Samsung to Samsung
How to save text messages to computer

Thanks for your post, if you want to transfer data between android and android, there're many android data transfer apps could help, it could transfer data between android device and computer in few steps.
You can transfer data from one phone to computer first, then connect the other one to computer and import contacts from computer to it.
how to transfer samsung sms to computer

Actually, there're many special designed android data backup apps could transfer everything between your phone and computer, you can connect your two phones to computer separately to transfer data between them.


Allow binding an annotated service method without a path

(From @KarboniteKream)
Let's assume we have the following annotated service:
Server.builder()
      .annotatedService("/my/service", new Object() {
          @Get("/")
          String root() {
              return "hello";
          }
      });

In this case, GET /my/service will not work while GET /my/service/ will. To be precise, GET /my/service will be redirected to GET /my/service/, i.e. a client needs to handle redirects.
Although this is working as intended, but it'd be nice if a user is allowed to handle a request at /my/service as well. What would be the best way to support this use case? Here are some ideas:

Allow specifying an empty path, e.g. @Get("")@Get("") @Get("/")
String root() { ... }

Allow leaving a path as unspecified, e.g. @Get without @Path annotation@Get @Get("/")
String root() { ... }

I'm slightly in favor of the former, but let me know what you think.

I will work on it 😊


How to debug torchtune

Hi, thanks for the framework,

I can't figure out how to debug torchtune, I want to set breakpoint in recipe, but how can I debug.
Do you plan to add rlhf like dpo, ppo ？

Hey @leo-young, thanks for the question.
The easiest way to debug I've found is to use the python debugger pdb.
import pdb

# Set a breakpoint in your code
pdb.set_trace()

For RLHF, we do have a recipe for DPO. See https://github.com/pytorch/torchtune/blob/main/recipes/lora_dpo_single_device.py. PPO is actively being discussed on our discord (cc @SalmanMohammadi and @kartikayk). Here is the issue discussing it: #812

hi @leo-young
To debug, i.e. directly launch python code instead of using the CLI (which won't hit break points) you can use the following code I wrote (wIll need some changes)
import argparse
from pathlib import Path

from torch.distributed.run import get_args_parser as get_torchrun_args_parser, run
from torchtune._cli.cp import Copy
from torchtune._cli.download import Download
from torchtune._cli.ls import List
from torchtune._cli.run import Run
from torchtune._cli.validate import Validate

MODEL_NAME = "meta-llama/Meta-Llama-3-8B-Instruct"
RECIPE = "full_finetune_single_device"
MODEL_CONFIG = "llama3/8B_full_single_device"

ACTIVATE_WANDB = True
MAX_STEPS_PER_EPOCH = 20
EPOCHS = 2

HF_CHECKPOINTER = True
# HF_CHECKPOINTER = False

run_command = [
    "run",
    RECIPE,
    "--config",
    MODEL_CONFIG,
]

run_command.append(f"model_name={MODEL_NAME}")

if ACTIVATE_WANDB:
    run_command.append("metric_logger._component_=torchtune.utils.metric_logging.WandBLogger")
    run_command.append("metric_logger.project=torchtune")

if MAX_STEPS_PER_EPOCH:
    run_command.append(f"max_steps_per_epoch={MAX_STEPS_PER_EPOCH}")
if EPOCHS:
    run_command.append(f"epochs={EPOCHS}")

if HF_CHECKPOINTER:
    run_command.append("checkpointer._component_=torchtune.utils.FullModelHFCheckpointer")

class TuneCLIParser:
    """Holds all information related to running the CLI"""

    def __init__(self):
        # Initialize the top-level parser
        self._parser = argparse.ArgumentParser(
            prog="tune",
            description="Welcome to the TorchTune CLI!",
            add_help=True,
        )
        # Default command is to print help
        self._parser.set_defaults(func=lambda args: self._parser.print_help())

        # Add subcommands
        subparsers = self._parser.add_subparsers(title="subcommands")
        Download.create(subparsers)
        List.create(subparsers)
        Copy.create(subparsers)
        Run.create(subparsers)
        Validate.create(subparsers)

    # def parse_args(self) -> argparse.Namespace:
    #     """Parse CLI arguments"""
    #     return self._parser.parse_args()

    def parse_args(self, args=None) -> argparse.Namespace:
        """Parse CLI arguments"""
        return self._parser.parse_args(args)

    def run(self, args: argparse.Namespace) -> None:
        """Execute CLI"""
        args.func(args)

def main():
    parser = TuneCLIParser()
    args = parser.parse_args(run_command)
    parser.run(args)

if __name__ == "__main__":
    main()

@optimass I'm a bit surprised to hear you don't hit breakpoints when running via CLI. Personally I have no issues doing this via the method described by @RdoubleA. Are you sure that it's not due to running on a distributed recipe (there are other issues in that case that are unrelated to CLI)?

could be that I'm using Vscode's visual debugger!

Closing this since I think it's resolved. But feel free to re-open if you run into other issues here!


Show P2Pool version in node list

Hi, I cannot seem to find your change here? Also, could you please recreate your PR against the 1.9-dev branch?


[jvm-package] Try fixing spark failure. [skip ci]

Based on https://github.com/dmlc/xgboost/pull/6275 .  This is just an attempt on removing the need to handle exception in worker.

Related: https://github.com/dmlc/xgboost/issues/6276


Game Over

Game Over
User Story
AS A coding boot camp student
I WANT to take a timed quiz on JavaScript fundamentals that stores high scores
SO THAT I can gauge my progress compared to my peers
Acceptance Criteria
GIVEN I am taking a code quiz
WHEN all questions are answered or the timer reaches 0
THEN the game is over

The game over function was added to the Coding Quiz application.  It will end the quiz when the timer reaches zero or there are not any additional questions.


⚠ Samsung has degraded performance

In 1f4ab3b, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2457 ms

Resolved: Samsung performance has improved in da1e424.


Glog reinitializes and fails in custom auth plugins

Purpose
To avoid glog being initialized again in plugin auth implementations.
Approach
Separated authn and authz interfaces from authn and authz packages and moved to api package.
Test environment
go version: go1.12.5 darwin/amd64
OS: Mac OS 10.14.5

ok, looks good. can you squash into 1 commit and rebase onto latest master please?

Squashed into 1 commit


SyntaxError: Unexpected token punc «)»

ERROR in static/js/vendor.9d36f5eb05df163409d5.js from UglifyJs
SyntaxError: Unexpected token punc «)», expected punc «(» [./~/vue-momentjs/index.js:12,0]
If this part of code
$moment: {
				get() {
					return moment;
				}
			},

rewrite this way
$moment: {
				get: function() {
					return moment;
				}
			},

there will be no errors

This has been fixed, thanks for reporting!
It seems this was an issue with an older version of UglifyJS which doesn't support ES6. But nevertheless, a small library like this should use an ES5 syntax for better compatibility.


Functional style formatter. Color range is all float numb…

Fix #32235.
Per discussion points in #32235

Color value ranges. Now we only expose float number between 0...1 .
Color.fromHex, Color.fromHSL are removed from the API.
Color Insertion. This is not done, but it's not a blocker to the API finalization.

With the new API,

The title of Color Picker only shows four color format, RGB, HEX, HSL, HSA, which are representatives of RGB color model. When users click on it, we iterate through them.
When users move the cursor inside the saturation box, we only make updates to the document when mouse up.
Since we only make changes when the color is finalized (mouse up), we ask the provider for string representative of selected color. We don't flood the extensions of both API call or content change.
Extensions format the color per Color Format users select in the color picker.

For now, the four formats are good enough as long as we are only targeting RGB color model. If there is other feature request, we need to update both provideColorRange and resolveColor as the color can no longer be represented as RGB. cc @joaomoreno @jrieken

Aligned the API name with other providers, now it works the same way as before and our API surface is based on RGB color model. Extensions do the parsing and resolving.

Good job!


avoid dynamically allocating memory

We've added max_msg_size in v7 (not sent yet), see https://libmuser.slack.com/archives/C01AFGCSPTR/p1605195853082400 for more details.

I think we can close it. The only performance-relevant path where this could really matter would be ioregionfd/ioeventfd handling, and that doesn't exist right now.


Format presentation changes for JSON column

Changes in format presentation function, the formatting logic has been removed from the get value() function and the JSON condition has been added to formatPresentation function()

Please add a test case to make sure the connected issue is resolved. And also always assign the PRs that you create to yourself.


ChainDB.StateMachine: testing wiping the VolatileDB

Fixes #1628.
Please review commit per commit.

I have added two "Feedback: .." commits to make reviewing easier. When approved, I will squash each in the commit right before it.

bors r+


fix non-quoted db&catalog issues

Type of PR

[x] BUG
[ ] FEAT
[ ] MAINT
[ ] DOC

Is your Pull Request linked to an existing Issue or Pull Request?
See https://github.com/moj-analytical-services/splink/issues/1556
Give a brief description for the solution you have provided
Previously, we weren't quoting catalog and database names which was resulting in unusual catalog and database combinations causing SQL errors.
I've simply added quotes to self.splink_data_store (the only location both catalog and db are used) and it appears to be resolving the issue.
To test, you can try creating a random database named 1111 and setting that as your target db from within the linker object:
# Create a database called '1111'
spark.sql("CREATE DATABASE IF NOT EXISTS `1111`")

# Run our actual link job
linker = SparkLinker(
    df_spark,
    settings_dict,
    database="1111"
)

PR Checklist

[ ] Added documentation for changes
[ ] Added feature to example notebooks or tutorial (if appropriate)
[x] Added tests (if appropriate)
[x] Made changes based off the latest version of Splink
[x] Run the linter

CI tests are all failing still... I've fixed this here.

@ThomasHepworth That is great. Thanks a lot. I also started on a PR and was stuck trying to add a proper test for it. I think it would be nice to also add this as part of the PR.

@espenfl ah, sorry, I wasn't aware you were also working on a fix!
I'm happy to close this PR and let you polish up a fix and a proper test if you'd like to make a contribution?
Our contribution guide is available here. Please add myself and Robin as reviewers once you're done, if you're up for it.

@ThomasHepworth No problem. That happens. No way for you to know this as I was a bit slow submitting a draft. I learned some new things and we will get it fixed. That is all that matters. Please let this PR be open. Greatly appreciated. I was actually trying to make a new catalog name which involved figuring out how to set this in the Spark config. Easier and better to just do it with a new database as you do it here as the names are combined anyway in the issue that we want to solve.

@ThomasHepworth Can I contribute with something to get this one merged?

https://github.com/moj-analytical-services/splink/pull/1558#issuecomment-1698660953
👋 apologies for the delayed reply, I was on leave last week.
Please do. I think it may in fact be easier if you submit a pull request as then I'll be able to QA and merge it personally.
I'll close this PR once you've opened another.

@ThomasHepworth Unfortunately I am unable to get this done in the next two weeks so maybe we can just leave this as is and get it merged when the dev team find it suitable? Thanks.


Add engineering helms for BoD

New engineering helms drop at 415, they should be included in the azerite gear sims.

[x] Charged SP1-R1-73D Synthetic Specs
[x] SP1-R1-73D Synthetic Specs
[x] Surging Synthetic Specs
[ ] Emblazoned Synthetic Specs

surging and emblazoned look the same, only added surging


updates initial compliance info function and updates tests

Coverage remained the same at 25.798% when pulling b31d05ff432460a4709cc012966ce8de1fbc4553 on theseyi:master into a186ff6db4929f4ed938610ea63563d8d95a2ae4 on linkedin:master.


Add random and randompalette prop

Add random and randompalette prop
This PR adds random and randompalette prop.
Add random prop
Random
The random prop is used to generate the avatar randomly, independent of the name.
<Avatar name="Clara Barton" random/>

Or you can leave the name empty.
<Avatar name=""/>

Or you can not use it at all.
<Avatar />

Preview:

Add randompalette prop
Random Palette
The randompalette prop is used to change the color palette of the avatar with a random color palette.
<Avatar name="Lucy Stone" randompalette/>

Add random prop
Random
The random prop is used to generate the avatar randomly, independent of the name.
<Avatar name="Clara Barton" random/>

Or you can leave the name empty.
<Avatar name=""/>

Or you can not use it at all.
<Avatar />

Preview:

Add randompalette prop
Random Palette
The randompalette prop is used to change the color palette of the avatar with a random color palette.
<Avatar name="Lucy Stone" randompalette/>

Up to avoid stale.


AST Explorer is broken

http://iamdustan.com/reworkcss_ast_explorer/
reports
Uncaught TypeError: Cannot read property 'initialize' of undefined
    at Object.<anonymous> (app.js:16)
    at Object.203 (app.js:16)
    at i (app.js:1)
    at app.js:1
    at Object.<anonymous> (app.js:16)
    at Object.206../Parse (app.js:16)
    at i (app.js:1)
    at app.js:1
    at Object.<anonymous> (app.js:16)
    at Object.212../ASTOutput (app.js:18)

Still broken as of today