Project abandoned

IMPORTANT NOTICE, 6 November 2017.
Without being able to expand on the reasons why and with immediate effect, I will no longer be maintaining this project or servicing tickets. I'm also unable to divulge any information regarding iOS/ iCloud mechanics or render any assistance in this regard.
I apologise for this.

Your language is clear. We hear what you're trying to say. I'm sorry that this happened. Thank you for helping me access my backups!

It's sad to hear that the tool has been discontinued. Thank you horrorho for all of your hard work! There is no doubt that maintaining InflatableDonkey was difficult and time-consuming.
InflatableDonkey is currently the only free program that can acquire backups and remains the only program that doesn't lock apple IDs ( #56 )

There is no doubt that maintaining InflatableDonkey was difficult and time-consuming.

@Yaldo425 I don't think that's the reason. @horrorho was working on an advanced iCloud tool for the best part of a year. It's an open secret that she had figured out how to circumnavigate things like 2FA.

Without being able to expand on the reasons why and with immediate effect, I will no longer be maintaining this project or servicing tickets. I'm also unable to divulge any information regarding iOS/ iCloud mechanics or render any assistance in this regard.

Reading between the lines of her statement, it sounds very much like either:

she was head hunted and bought out, everyone has their price.

Apple found out and came down on her like a ton of bricks.

Either way an NDA would be involved hence her being unable to expand on the reasons why.
For what it's worth I suspect she was bought out. She mentioned that her private tool would not become public. If this is the case then why put in all that effort to create something that has no consumer?
I don't mean this as a criticism but she has been known to be evasive. InflatableDonkey has always been able to download iPhotos and Photo Streams. She never released these updates to the public as she did not want to cater to the 'creeps' out there although she never commented as such, instead deferring to excuses about lack of time or other.
I've tried contacting her but she's no longer replying to my emails. Maybe others will have better luck establishing the facts.
@horrorho Please don't take any of this to heart if you do read this. I'm a great fan of your work and I've forever been in awe of your skill. However I think the community deserves an answer that understandably you're unable to provide. Peace out.


64-bit mac binary and build files

As far as I can see this looks good!
It'll take me a while to get to a computer, but once one materializes I'll test this and merge it in.
Thanks!

As I'm looking at this I see that you're replacing the 32 bit lib in the documentation. Also, the Linux build will compile the 64 bit version twice. So, I can't merge this as is.
But, I totally agree that this needs doing, so either you clean up the PR or I'll look into it myself.
The problem I had when I originally did this was that I couldn't detect if it was a 32 or 64 bit build in the include.nmml, meaning that I didn't know which library file to copy over (since they're named the same and needs to go in the same folder).

My original PR did accidentally replace the 32-bit lib

yep, I see where I screwed that up. fixing and sending a new PR now.


Fix duplicate uid

Docs Build status updates of commit 3daea8b:
:clock10: Full build: the average full build time is 76 min(s) 52 sec(s), this is based on the last 94 build(s) for this repository.

Docs Build status updates of commit fd5d6a1:
:clock10: Pending: waiting for processors (19 builds ahead of you)
:warning: Docs Build is busy, currently there are 19 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit fd5d6a1:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error-FailedToRestoreDependentRepository]

Failed to restore dependent repository from URL 'https://github.com/Microsoft/templates.docs.msft', branch 'master' into folder '_themes'. Please open a ticket in https://SiteHelp and include exception details: System.TimeoutException: Git operation '-c http.extraheader="Authorization: *****" pull origin --no-edit' timed out. Details: git.exe (argument: -c http.extraheader="Authorization: *****" pull origin --no-edit, working directory: W:\kw5d-s\_themes) didn't exit in 180000 ms. Forced to exit..
   at Microsoft.OpenPublishing.Build.Common.ProcessUtility.ExecuteExeCore(ProcessExecutionInfo executionInfo, Action`1 outputAction, StreamWriter stderrStreamWriter, Int32 timeoutInMilliseconds, CancellationToken cancellationToken)
   at Microsoft.OpenPublishing.Build.Common.ProcessUtility.ExecuteExe(ProcessExecutionInfo executionInfo, StreamWriter stdoutStreamWriter, StreamWriter stderrStreamWriter, Int32 timeoutInMilliseconds, CancellationToken cancellationToken)
   at Microsoft.OpenPublishing.Build.DataAccessor.Git.ExternalGitAccessor.RunGitExeAndProcessOutputStream(String argument, String workingDirectory, Uri repositoryUrl, String branchName, Action`1 outPutStreamAction, Boolean silentException, Int32 timeout, Boolean retryOnTimeout)
   at Microsoft.OpenPublishing.Build.DataAccessor.Git.ExternalGitAccessor.PullCore()
   at Microsoft.OpenPublishing.Build.DataAccessor.Git.BaseGitAccessor.Pull()
   at Microsoft.OpenPublishing.Build.Applications.InitializeCRRTool.Program.InitializeDependentRepository(String dependentRepoPath, String cloneAccessToken, Boolean isCopiedFromCachedRepo, Boolean isPreservedTemplateFolder, Options options, DependentRepository dependentRepository)
   at Microsoft.OpenPublishing.Build.Applications.InitializeCRRTool.Program.InitializeCRRCore(String dependentRepoPath, String cloneAccessToken, Boolean isPreservedTemplateFolder, Boolean isCopiedFromCachedRepo, String branch, Options options, DependentRepository dependentRepository, List`1 lastDependencyStatus)
   at Microsoft.OpenPublishing.Build.Applications.InitializeCRRTool.Program.<InitializeCRRCoreAsync>d__8.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.OpenPublishing.Build.Applications.InitializeCRRTool.Program.<InitializeCRRAsync>d__5.MoveNext()

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Integers and decimal places

In the grid on a page I have several numbers that don't have decimal places. both int and short. However in the edit dialog both numeric values get appended to two decimal places. Is there any way I can stop that without resorting to Masks? As in a whole number editor. I tried IntegerEditor.  I could change them to be characters but this seems counter intuitive.

This is probably a bug related to jQuery version upgrade or changes made for TypeScript. You may try [IntegerEditor(MinValue = 0, MaxValue =<PHONE_NUMBER>)] till this is resolved in next version.

Thanks Volkan, the workaround works fine.

You're welcome, just keeping open to remember.

Should be resolved with 2.0.12


[Feature Request] Input Mask for el-input

Existing Component
Yes
Component Name
el-input
Description
Please include masking options for the simple input box. something mask="##-##-####" will accept values like 12-12-4323.
Thanks

We won't include this feature in the mainline.
You should wrap @input event and :value prop. This feature can be implemented externally after 2.5 release.


add an option to keep the modal open even if background overlay is cicked

Added a closeOnClick property so we can choose not close the modal when the background overlay is clicked

@yuanyan are you still maintaining this repo? I'd love to make contributions similar to this one but not if they'll be lost to the ether!


Prefix

How do we change the prefix?


requiry about the weight of DD

When I run backdoor on DD, I cannot return the weights of the models.
And when I use the saved dataset to evaluate it again, I cannot get the same results as the training log.

I will close this issue. Feel free to open it again.


Simple Polling Hard Coded Senior Center Status App

Here's a very simple "app" with JavaScript embedded in the html.  It polls every 10 seconds updating if the center is open or not.
The open times are just strings in the HTML of http://mountainview.gov/depts/cs/rec/senior/default.asp

Thanks for making this! Could you send your pull request to the gh-pages branch instead of master? That branch is the website of the project:
http://codeforsanjose.github.io/HackNightProjects/

Closing because the code has already been submitted to gh-pages


Corrected run script tomcat path.

The whole repository has been reorganized so that there are no image build here (but take from fabric8io-images github orga)


Add public and private zaps

This was almost very simple, but sadly doing private zaps with a NIP-07 extension isn't very well supported. The way clients generate the random npub is deterministic from the user's nsec, but since we don't have the user's nsec, we cannot do this. Private zaps will still work, we can just randomly generate the key, the problem is if we see the event in the future, we won't be able to decrypt it ourselves.

the problem is if we see the event in the future, we won't be able to decrypt it ourselves.

We'll still have some reference for it inside of mutiny, right? And for private zaps, the receiver will still see it was from us?

if I do a private zap Ben -> Tony, if I open up in Damus I will see you were private zapped

That's fine IMO, I don't care that much if we're limited here. But will it still show up in Mutiny is more my question.

That's fine IMO, I don't care that much if we're limited here. But will it still show up in Mutiny is more my question.

yes

needs rebase

New release of rust-nostr came out so was able to simplify


Allow "waves" of phishing activity

Currently one email goes to one recipient, which means a single domain and any associated file may only be sent to one user in the company. We should allow "waves" of phishing activity, wherein the same email is sent to a group of users

Added the ability for actors to send mutliple emails. We still need configure links so that the same attachment results after clicks


command_queue::command_queue problem with versions

I've intel-based system (output from clinfo.exe):
Number of platforms:                 2
Platform Profile:              FULL_PROFILE
Platform Version:              OpenCL 1.2
Platform Name:                 Intel(R) OpenCL
Platform Vendor:               Intel(R) Corporation
Platform Profile:              FULL_PROFILE
Platform Version:              OpenCL 2.0
Platform Name:                 Experimental OpenCL 2.0 CPU Only Platform
Platform Vendor:               Intel(R) Corporation
As we see there are two devices, supporting different OpenCL versions, however headers shipped with the newest SDK from Intel defines CL_VERSION_2_0. This is the problem, because command_queue::command_queue selects an initialization code using defines, and if it is called on device supporting version 1.2 then strange errors happen in a drivers. When I manually edited library code to use initialization for 1.2 everyting works ok.
Maybe API version should be obtained from a device info? Or is it a problem in vendor SDK?

It should be fixed by https://github.com/boostorg/compute/commit/60f4b31bdd374e088eb26262c9b7970a08f9ab8c.


DEBUG=true in env results in error

I have an environment with DEBUG set to "true", this leads to an error:
Can be reproduced with:
> DEBUG=true pre-commit run shell-lint
Shell Syntax Check.......................................................Failed
- hook id: shell-lint
- exit code: 1
[...]/pre_commit_hooks/shell-lint.sh: line 8: true: unbound variable

could you force a new version for this?

New release will be appreciated.


Fix auth login error messages and messaging when witnessing a delegation with 0 valid keys

When I remove a key from a delegation that has a single key, then I try to witness that delegation, signing fails because there are no valid keys for that delegation.  The error message was:
* fatal: signing keys not available, need 1 keys out of:  - I've fixed the error message to say there are an insufficient number of valid signing keys for the threshold required, basically.  We might want to move this error check up further to when we apply a witness change, since I think that might be the only time when we might have an invalid role.
Fixes #969 - that format string was in distribution, so I re-vendored.  I also added logic to check if the login username/password is a terminal, otherwise fail.
Note: possibly we want to rebase this to 0.4.0 so that it can be added to 0.4.1

Is there an easy way to get Godep to exclude the distribution *.md and build files?

I can manually remove them - Godep tried to include the vendor dir :|

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "fix-error-messages" git@github.com:cyli/notary.git somewhere
$ cd somewhere
$ git rebase -i HEAD~72
editor opens
change each 'pick' to 'edit'
save the file and quit
$ git commit --amend -s --no-edit
$ git rebase --continue # and repeat the amend for each commit
$ git push -f

Amending updates the existing PR. You DO NOT need to open a new one.

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "fix-error-messages" git@github.com:cyli/notary.git somewhere
$ cd somewhere
$ git rebase -i HEAD~72
editor opens
change each 'pick' to 'edit'
save the file and quit
$ git commit --amend -s --no-edit
$ git rebase --continue # and repeat the amend for each commit
$ git push -f

Amending updates the existing PR. You DO NOT need to open a new one.

@endophage @riyazdf sorry this took so long to update.  Tried to fix some of the messaging around witnessing an invalid delegation role as suggested above.


Can't edit thresholds

@AaronStGeorge

Want to flesh this one out a little more?

@AaronStGeorge The user can't edit their thresholds at all after they are set. What if they make a mistake? Also can you add the high and low thresholds to the monitor fragment so they display?

@skazn I see what you mean. Everything is set up so if you relaunch the fragment it should edit the threshold without any errors. Maybe a long click could re-open the fragment?

I can work on the high and low thresholds on the monitor fragment. The main page stuff was sort of yours now, do you want to get a long click or similar to re-open the threshold?

@AaronStGeorge @skazn I have longClick bound for deletion of fragments. We could piggyback and give them an option (edit or delete) but wait till I push changes to viewmanager (where the clicklisteners are now)


Change testing process by replacing unittest to pytest

Hello to everyone,
What do you think about switching from unittest to  pytest for our testing process ?
I remarked that some tests and especially validation ones can be really long and I think that it could be good to have the possibility to exclude some tests easily or to only include some of them. Pytest enables to do it easily by defining markers:
@pytest.mark.validation
def test_example():
    """Write the test here"""
    pass

Pytest also handle Pytest-cov to generate coverage test and help us improving our test process. It also handles tests parametrization so we wouldn't lose any testing ability.
Pytest can also execute unittest so the transition could be easy. We could write all new tests with pytest formalisme and progressively convert every tests and then remove ddt dependancy ?
Best regards,
Cédric

Hello Cedric,
Great idea :) I have two remarks to go further:

Is it possible to set several markers on a same test (for instance, "fast" "plot" "validation"...)? Whatever the answer we need to set some global marking rules to be consistent in the test.
If I remember well there is a tool to convert automatically a unittest script to a pytest one. It may cause some issue with ddt but we can use that on all the script that don't use ddt. By the way, what is the alternative for ddt in pytest ?

Best regards,
Pierre

Hi Pierre,
You can use different markers for a single test :)
I think that we can mark automatically tests according to their name.
To convert automatically I will check this project.
To replace ddt, there is a dedicated marker :
import pytest

from datetime import datetime, timedelta

testdata = [
    (datetime(2001, 12, 12), datetime(2001, 12, 11), timedelta(1)),
    (datetime(2001, 12, 11), datetime(2001, 12, 12), timedelta(-1)),
]

@pytest.mark.parametrize("a,b,expected", testdata)
def test_timedistance_v0(a, b, expected):
    diff = a - b
    assert diff == expected

Best regards,
Cédric

Hello everyone,
This could be the opportunity to set up an automated testing environment.
This way, any pull-request would be automatically tested.
I have several solution to propose:
Travis CI
GitLab CI
Coveralls
Codecov
Travis is already compatible with github, and it can be set up on the github repo in a few clicks. I believe  it is free for open-source project.
Best regards,
Raphaël

Closed with PR #148


Same as PR #2056 but merging into master branch

This pull request is the same as PR #2056 but merging into master branch rather than the tendermint branch.
The "root docs" show whatever is on the latest master branch so once this gets merged, the "root docs" will no longer show the big link/button to the CLI Transaction Tool.

Codecov Report

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

@@           Coverage Diff           @@
##           master    #2059   +/-   ##
=======================================
  Coverage   96.91%   96.91%
=======================================
  Files          60       60
  Lines        3045     3045
  Branches      411      411
=======================================
  Hits         2951     2951
  Misses         46       46
  Partials       48       48


UI Modal

Hi,
I am trying to use the directive inside a Modal however the handlefileselect function does not seem to get called in the modal controller.
I presume its because of the angular.element not properly registering the function due to the DOM not being loaded. I have tried to add a timeout and no luck.
Any suggestions greatly appreciated?
.controller('ProfilePictureModalInstanceCtrl', function ($scope, $modalInstance, items,$timeout) {

$scope.myImage = '';
$scope.myCroppedImage = '';

var handleFileSelect = function (evt) {

    alert("Here");

    var file = evt.currentTarget.files[0];
    var reader = new FileReader();
    reader.onload = function (evt) {
        $scope.$apply(function ($scope) {
            $scope.myImage = evt.target.result;
        });
    }
    reader.readAsDataURL(file);
}

angular.element(document.querySelector('#fileInput')).on('change', handleFileSelect);

$scope.ok = function () {
    $modalInstance.close($scope.optionItems);
};

$scope.cancel = function () {
    $modalInstance.dismiss('cancel');
};
});

The HTML for the modal is

I solved this by adding the following directive
.directive('customOnChange', function () {
return {
restrict: 'A',
link: function (scope, element, attrs) {
var onChangeHandler = scope.$eval(attrs.customOnChange);
element.bind('change', onChangeHandler);
}
};
})
and then I define the function in the controller
$scope.uploadFile = function (event) {

    var file = event.currentTarget.files[0];
    var reader = new FileReader();
    reader.onload = function (event) {
        $scope.$apply(function ($scope) {
            $scope.myImage = event.target.result;
            //console.log($scope.myImage);
        });
    }
    reader.readAsDataURL(file);

};

and it gets set to the HTML like so

Select an image file:
            <input type="file" id="fileInput" custom-on-change="uploadFile" />

Cropped Image:

I'm going to try your code later. I have this code inside the controller for my modalinstance and it's weird that it doesn't get called. I can see the myCroppedImage image on the browser gets updated correctly though but it doesn't update $scope.myCroppedImage
    $scope.$watch('myCroppedImage', function(newValue, oldValue) {
    	console.log('myCroppedImage on ImageToThumbnailController', newValue, oldValue);
      	DataURIStorage.storeDataUri(newValue);
    });

I'll keep you posted.

Actually, my issue is different. The issue is that inside my modal, the $scope.myCroppedImage doesn't get called. I am not sure why. I've already spent 8 hours debugging and I still can't figure it out. Any ideas?

I fixed my issue by using dotted notation

@yeremiapinggi I couldn't remember anymore but I'm sure I got it work a long time ago. Thanks.


About FOCALLOSS : avg_factor

In the function of loss_single() of xxx_head.py ,there is avg_factor and it is passed throught  'focal_loss' to function 'weight_reduce_loss',while I found that the programm still goes into 'if avg_factor is None:' branch .
so why does it happen? please help me :
###codes are :

loss_cls = self.loss_cls(
cls_score, labels, label_weights, avg_factor=num_total_samples) in anchor_head.py
loss = weight_reduce_loss(loss, weight, reduction, avg_factor) in focal_loss.py

if avg_factor is not specified, just reduce the loss

if avg_factor is None:
    loss = reduce_loss(loss, reduction)  in utils.py

as for fsaf_head.py ,the above question happened;while for retinanet,eveything goes normally.
But fsaf_head is inherited from retinanet and there is no particular switch to control avg_factor,which is quite confusing>>><<<

We simply follows the official implementation to use the avg_factor.


How to make EXE work with embedded python environment in subdirectory

I compile main.py with the following parameters: nuitka --mingw64 --nofollow-imports --full-compat --plugin-enable=upx --windows-disable-console --output-dir=out main.py
The main.exe can be used with the embedded python environment in the directory structure shown below.

I want to organize the directory structure as shown below.

Please let me know if there is a possible way to do this. Thanks a lot!

It is not possible, the embedded Python is incomplete and not supported.

@kayhayen The main.exe works well in the directory structure shown below.

It is not possible, the embedded Python is incomplete and not supported.

@kayhayen I use the full Python environment with Nuitka to compile, and then package the EXE file with embedded Python for distribution.


Incorrect handler delegation in OpenIdConnectAuthenticationHandler.InvokeReplyPathAsync

Looks like your new monster has been released too quickly in the wild :smile: :laughing:
An invalid scheme is used in OpenIdConnectAuthenticationHandler.InvokeReplyPathAsync and makes the OIDC client middleware totally buggy because it cannot delegate the principal persistence to the cookie middleware. You should use Option.SignInScheme instead.
https://github.com/aspnet/Security/blob/dev/src/Microsoft.AspNet.Authentication.OpenIdConnect/OpenidConnectAuthenticationHandler.cs#L569
(you should also fix the file name)

Thanks fix is pushed, I'll fix the file name in a different commit 0577454f13f6ec0e82a424225729ccb57e2911ac

Sadly, your fix is incomplete: it doesn't support setting the SignInScheme property via ExternalAuthenticationOptions.SignInScheme.
See https://github.com/aspnet/Security/pull/168/files#diff-960390b7edd1b3a479fbd7fcfd07fbe8R48

Yeah I know, I'm just trying to get MusicStore unblocked for now, the test coverage for OpenidConnect is...fairly lacking right now obviously, once all the existing tests are fixed, I'll look into adding some more coverage so we can catch this sort of failure before checkin...

You should maybe re-open this ticket to make sure this new issue is correctly tracked.

Merged 4a2a742ad5e52b2f9e0529b8c6f5f9decd3e80f0


Use new Raku file extensions and bump version

Conflict due to me having merged the 1.1 bump already :)

Mergeable now


python3Packages: init shap at 0.36.0

Motivation for this change
A unified approach to explain the output of any machine learning model
Things done

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

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[X] Fits CONTRIBUTING.md.

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

4 packages built:

python37Packages.shap
python37Packages.slicer
python38Packages.shap
python38Packages.slicer

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

1 package failed to build:

python38Packages.shap

3 packages built:

python37Packages.shap
python37Packages.slicer
python38Packages.slicer


fix: pad entry string in l1 to l2 tests

Description
fixes #795
Please provide a paragraph or two giving a summary of the change, including relevant motivation and context.
Checklist:

[ ] I have reviewed my diff in github, line by line.
[ ] Every change is related to the PR description.
[ ] I have linked this pull request to the issue(s) that it resolves.
[ ] There are no unexpected formatting changes, superfluous debug logs, or commented-out code.
[ ] The branch has been merged or rebased against the head of its merge target.
[ ] I'm happy for the PR to be merged at the reviewer's next convenience.

yeah its however fr.toString() does go to the smallest size, i think it was just a hash getting lucky and ending up being under 32 bytes. But yet again its all speculation


Adding new functions to utils.py

This new methods are good. I think we can better organize the data output. Let's pair on that to sort it out.


Oc php lib

you can use this PR to reset you branch andforce push it to open the PR against the main repo

Ii @ferishili!
So I have now made a few changes :-) I have directly changed all static calls and also implermentiert a new dependecy injection sontainer (there is already one, but I would like to get rid of it, maybe I still manage until tomorrow).
so the initialization of the API is also done in a different place, cih think this will be the place where all dependencies and configurations should be loaded in the future: https://github.com/elan-ev/OpenCast/pull/1/files#diff-2fc1d36ebe3f3b4ea95b517a7e63a55a1189d07c5d88f9f78360ea8830b8564dR59

Closing this as I have merged this PR and also added a few conflict related fixes!


= Operator Unexpected Results

I have a bill in the sandbox that has a date of 8/1/2022. This query returns no results:
Select * from Bill where VendorRef = 'my-vendor-ref-id' and TxnDate >= '2022-08-01' and TxnDate <= '2022-08-31' and Balance != '0.00' startposition 1
I went into the sandbox account and adjusted the bill date to 8/2/2022 and re-ran the query and it returned the bill.
The docs seem to indicate that providing a date (not a datetime) will work as I have it configured, but the results seem to indicate otherwise.

The docs use this specific example where it's just a date, not a datetime:
SELECT * FROM Invoice WHERE TxnDate > '2011-01-01' AND TxnDate <= CURRENT_DATE
Is this an issue, or am I doing something wrong?

I think the STARTPOSITION and/or MAXRESULTS might have been causing me problems. I've adjusted my query and it seems to be returning the right records now.


Update Swagger specs

For v0.1 @mederic-p has made excellent job to improve our swagger specs.
Cherry pick these changes and update to the current API state for master & v0.2.
Add ref to v0.2 specs in gh-pages (how :question: )

Followed up with @pnowosie and this is done via https://github.com/omisego/elixir-omg/pull/744


intToRgba to intToRGBA in jimp.d.ts

I suggest you don't remove intToRgba - keep it and also define a new function intToRGBA in the main js file and make it point to intToRgba.

intToRgba does not exist. is there a reason both cases should be supported? It will be more work and more confusing.

Ah, ok. I thought that you were renaming an old feature.
Though something like this is on another feature of jimp - check greyscale() and grayscale() - they both point to the same function in the main js file.

NB this is also fixed in this PR https://github.com/oliver-moran/jimp/pull/329 (which also covers a bunch of missing methods)


v3.5.2 update - beta

Added email verification module.

Added ability to resend verification link, just incase the first mail has expired or didn't send.

Updated app dependencies

Issue with SQLAlchemy, so maintaining previous dependency until I'm able to look into it.
Issue with PyJWT dependency, maintaining previous version.
Will check changes made to flask prior to upgrading to v2.

Need to run more test on this, closing for now.


Contacting for Code of Conduct Issues links back to Github repo page

Description
To report instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement, the link provided just redirects to github repo of reduced.to instead of any way of reporting.
Screenshots

Additional information
Would like to work on this issue and provide an alternate link like official e-mail id if maintainers allow me to

@iamanurag101 Hey!
Thank you for your contribution.
I know this is the case, at the moment I don't have an official mail for this project.


🧹 Handle slugs

Story
Refs https://github.com/scientist-softserv/adventist-dl/issues/582
Removes alternative_title from forms
Removes alternative_title from bulkrax mappings
Additional Background:
In the adventist implementation of slugs, the predicate "alternative" is being used to store the slug. If viewing the data, the predicate will contain the slug if there is one, and otherwise it contains the uuid.
A second term and predicate was added for slugs, but remediation of prior data into the new predicate has not yet happened, which would be beyond the scope of current work as it would require a data migration.
With the hyrax upgrade, alternative_title is now included by default. By removing the alternative_title from the any create or edit ability, the data for slugs is still saved in the same location as alternative_title would be, but does not impede any behavior.
Expected Behavior Before Changes
Work forms include alternative_title
Expected Behavior After Changes
Work forms do not include alternative_title
Screenshots / Video

BEFORE, with and without a slug:

Notes

todo: verify that updated specs work.

Will this also solve the reason we can't delete works that have slugs? @laritakr

(prob not but asking anyways) - Will this also solve the reason we can't delete works that have slugs? @laritakr

Hmmm I don't know. I didn't realize we couldn't! Is there a ticket for that?

https://github.com/scientist-softserv/adventist-dl/issues/567


FIX: Show correct address based on the desired chain on Station

Station is currently showing the terra address no matter which chain is selected, this PR should fix it.

lgtm


The titles from the job description are unnoticeably small and some sections have no diacritics - mobile

ENVIRONMENT
URL: https://oportunitatisicariere.ro/
Browser: Chrome
OS: Android
STEPS TO REPRODUCE:

Open the URL in the browser
Go to "Cum poti ajuta" section
Click on any job

EXPECTED RESULTS:
The titles are visible and all sections are written with diacritics (where is the case).
ACTUAL RESULTS:
The titles are too small and the content of the "Alte informatii (optional)" and "Ce oferim" sections has no diacritics.

Hello. Can you please check this again?

Check the font for the email section:

@adriandoinea Please fix the responsiveness for the Job Details page overall.

Hello @CameliaAM  @Florin201092 . Can you please check this again? :)

FIXED!


Action charges refactor

Fixes the slight godmoding of baseactioncomponent.
Gets back 1ms of server time.<

Breaking changes
Charges got moved to ActionCharges + ResetChargesComponents.

kid named LimitedChargesComponent


Adds additional chairs to arrivals shuttle

About the PR

As said in title, adds extra chairs
Why / Balance

People keep falling over and there isn't enough room.
Technical details

Media

[X] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes

Changelog
 :cl:

tweak: Arrivals now supports having extra chairs

What.

I'm blind and need to fix my mistakes.


Docker desktop 3.5+: "network default: network.external.name is deprecated in favor of network.name"

Docker (Windows 10 Home/WSL2) just updated to 3.5.0 (66024). Projects on ddev 1.17.6 generate a warning "network default: network.external.name is deprecated in favor of network.name". Projects with varnish (ddev contrib) generate an error, "services.varnish.ports must be a list" and fail. Updating to Docker 3.5.1 did not solve or change the issue.
Currently unsure of the cause and working around it.
The start log:
14:55 $ ddev start
Starting XYZ...
Pushed mkcert rootca certs to ddev-global-cache/mkcert
Running   Command=ip address show dev docker0
time="2021-06-25T14:55:25+02:00" level=warning msg="network default: network.external.name is deprecated in favor of network.name"
services.varnish.ports must be a list
Failed to start XYZ: Failed to run docker-compose [-f /home/heine/sites/XYZ/.ddev/.ddev-docker-compose-base.yaml -f /home/heine/sites/XYZ/.ddev/docker-compose.environment.yaml -f /home/heine/sites/XYZ/.ddev/docker-compose.redis.yaml -f /home/heine/sites/XYZ/.ddev/docker-compose.solr.yaml -f /home/heine/sites/XYZ/.ddev/docker-compose.varnish.yaml config], err='exit status 15', stdout='', stderr='time="2021-06-25T14:55:25+02:00" level=warning msg="network default: network.external.name is deprecated in favor of network.name"
services.varnish.ports must be a list'

Our varnish compose:
14:55 $ cat .ddev/docker-compose.varnish.yaml
# DDev Varnish recipe file.
#
# To use this in your own project:
# 1. Copy this file to your project's ".ddev" directory.
# 2. Create the folder path ".ddev/varnish/".
# 3. Make a file with the following content at
#    ".ddev/varnish/default.vcl".
#
# vcl 4.0;
#
# backend default {
#   .host = "web:80";
# }
#
# Notes:
# - The configuration files must be present before running "ddev start".
# - Changes to the configuration files will not be automatically applied.
#
# To access the site through Varnish after it is installed simply visit the ddev
# site as usual. To avoid going through varnish visit the the novarnish. subdomain.

version: '3.6'

services:
  # This is the service name used when running ddev commands accepting the
  # --service flag.
  varnish:
    # This is the name of the container. It is recommended to follow the same
    # name convention used in the main docker-compose.yml file.
    container_name: ddev-${DDEV_SITENAME}-varnish
    image: "varnish:6.2"
    # These labels ensure this service is discoverable by ddev.
    labels:
      com.ddev.site-name: ${DDEV_SITENAME}
      com.ddev.approot: $DDEV_APPROOT
    environment:
      # This defines the host name the service should be accessible from. This
      # will be sitename.ddev.site.
      # This is the first half of the trick that puts varnish "in front of" the
      # web container, just by switching the names
      - VIRTUAL_HOST=$DDEV_HOSTNAME
      # This defines the ports the service should be accessible from at
      # sitename.ddev.site.
      - HTTPS_EXPOSE=443:80,8026:8025
      - HTTP_EXPOSE=80:80,8025:8025
      - SIZE=256M
    volumes:
      # This exposes a mount to the host system `.ddev/varnish` directory where
      # your default.vcl should be
      - ./varnish:/etc/varnish
      - ".:/mnt/ddev_config"
    ports: []
    links:
      - web:web
  # This is the second half of the trick that puts varnish "in front of" the web
  # container, just by switching the names
  web:
    environment:
      - VIRTUAL_HOST=novarnish.$DDEV_HOSTNAME

I'm pretty sure ports: [] is just an error and that line should be removed.

Changed the title to focus this issue on the deprecation warning. The ports fix is just an error in the ddev-contrib varnish recipe and will be handled in https://github.com/drud/ddev-contrib/issues/144

Opened upstream issue: https://github.com/docker/compose-cli/issues/1856


Explain net favorability

"Net favorability refers to the difference between the percentage of those surveyed expressing agreement/support towards the more pro-UBI position, and those that expressed disagreement/opposition."


failed at Upgrading to Nextcloud version 20.0.1

FAILED: wget -O /tmp/nextcloud.zip https://download.nextcloud.com/server/releases/nextcloud-20.0.1.zip
-----------------------------------------
--2020-12-31 14:27:38--  https://download.nextcloud.com/server/releases/nextcloud-20.0.1.zip
Resolving download.nextcloud.com (download.nextcloud.com)... failed: Temporary failure in name resolution.
wget: unable to resolve host address ‘download.nextcloud.com’

I'm digging through the setup script now to see what I'm missing...  looks like I've still got a little way to go but will try to hack my way thru it.

Looks like an issue in your end. At the moment the download.nextcloud.com website is up. Did you try to run the setup again? Are you able to download nextcloud from your machine?

I went through the script and manually completed the rest of the steps... turns out I already had the latest version... no clue why it couldn't resolve the first time. Waiting for DNS to clear up but everything appeared to work.

I went through the script and manually completed the rest of the steps... turns out I already had the latest version... no clue why it couldn't resolve the first time. Waiting for DNS to clear up but everything appeared to work.


Update cloudwatch, sdk-core, ses, sns, sqs, ssm to 2.20.86

About this PR
📦 Updates

software.amazon.awssdk:cloudwatch
software.amazon.awssdk:sdk-core
software.amazon.awssdk:ses
software.amazon.awssdk:sns
software.amazon.awssdk:sqs
software.amazon.awssdk:ssm

from 2.20.80 to 2.20.86
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "software.amazon.awssdk" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "software.amazon.awssdk" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #2733.


Prioritise main/master mix ups

Fixing the mix up of branches main and master should have a higher priority than other rules, because it is more logical most of the time. One example:
$ git checkout main
error: pathspec 'main' did not match any file(s) known to git

The suggestion git checkout master should have the highest priority, rather than git checkout -b main which is the case now.

Presumably this can be closed now too?


[Bug] Windows - Install-Msys2.ps1 - remove msys2 p7zip / 7z package

Description
New tool, Bug fixing, or Improvement?  Bug
Due to conflicts with two installed versions
See https://github.com/actions/virtual-environments/issues/905

/azp run windows2016, windows2019

Rebased (duh) and added two minor changes.  Worked locally...

Reminder
Once MSYS2 has been rolled out, the current Windows Rubies can be replaced with standard installs.
The 'vendored' code in RubyInstaller2 Rubies will find the MSYS2 install, so there won't be an issues.  JFYI, the code looks for an embedded MSYS2 first, then checks C:/msys64.
In the most recent release:
https://github.com/oneclick/rubyinstaller2/releases/tag/RubyInstaller-2.7.1-1
The current download, rubyinstaller-devkit-2.7.1-1-x64.exe, is 131 MB, while the standard install, rubyinstaller-2.7.1-1-x64.7z, is 11 MB.  Given that there are four Rubies installed (2.4 thru 2.7), that should free up a lot of disk space, and remove a lot of duplicated files.
I'd do a PR for it, but I can't find the code...

@MSP-Greg , I think we don't need to remove p7zip to unblock only one particular customer case.
Try to count how many apps contains raise the same issue in the msys64 directory:
PS > dir C:\msys64\usr\bin | measure | % count
778

We can easily reproduce the issue for example with  make util:
runs-on: [windows-latest]
    steps:
    - name: Install Ruby toolchain
      uses: ruby/setup-ruby@v1
      with:
          ruby-version: "2.6.3"
    - name: make
      run: |
         which make
         make --version
      shell: bash

Normal behavior:
runs-on: [windows-latest]
    steps:
    - name: make
      run: |
         which make
         make --version
      shell: bash

As I know you provided the request to change git -> bash to msys64 -> bash that can resolve this  issue with correct initialization msys2 environment when we use bash shell.

@al-cheb
Everything you said is true.  I thought an exception for p7zip was warranted because:

I've used MSYS@ locally for a few years, and I've never installed the package.
It's an old version of 7z, which also implies other users of MSYS2 don't have a need for it.  Current 7zip version is 19.00, p7zip is 16.02.
7z is a 'native' windows app, and there's already two copies on the image.

With Windows CI, there's always going to be issues with GNU dev/build tools.  Or, I think 7z is in a different category than things like gcc, make, openssl, etc...
My POV is also biased from helping macOS/nix types get Windows CI working, which probably shows in how ruby/setup-ruby works with Windows.
Long story short, if you want to close, that's ok by me...

The 7z from MSYS2 seems clearly broken though, right?
/c/msys64/usr/bin/7z: line 2: /usr/lib/p7zip/7z: No such file or directory
##[error]Process completed with exit code 127.

What causes that?
Is there a way to make it work or is it completely unusable? If the latter I'd argue it should not be part of the installed packages.
Why does make fail above? I understand it will pick MSYS2's make, but shouldn't that make work too?
IIRC it seems most software already has to care to use make.exe explicitly on Windows to not get some half-broken gmake (by setting the MAKE env var). Which still seems unfortunate and confusing.
Since GitHub Actions is adding a MSYS2 installation, I would assume adding it to PATH should work reasonably well. If basic tools like 7z or make fail no matter the arguments it seems we need a way to fix that. AFAIK we had no such issues with the builtin Ruby MSYS2 DevKits from RubyInstaller.

@eregon
The problem is using the bash shell, which is from Git, it's not the MSYS2 bash shell.  See https://github.com/actions/runner/issues/497

Because the Git Bash does some initialization that MSYS2 binaries don't like, or conversely those binaries need some setup that MSYS2 bash does?
Why don't we see this issue with the RubyInstaller DevKit but we see them with GitHub Actions MSYS2? Simply because it has more packages?

Do you know of any repos using shell: bash in any workflow steps?
Puma, Ruby, RubyGems, & ruby-loco are all working fine?  I had to update setup-ruby-pkgs because of a GPG key issue (ruby 2.4 OpenSSL 1.0.2), and it builds the OpenSSL gem as a test, also ok...

BTW:

I got the version number of the MSYS2 p7zip package locally, so it at least that much works.

Action custom shells - They appear to not work, as I just tried.  Googled it, and found an issue I filed that I  forgot about: https://github.com/actions/runner/issues/460.  It seems to not be affected by changes to PATH by previous steps?

As I know you provided the request to change git -> bash to msys64 -> bash that can resolve this issue with correct initialization msys2 environment when we use bash shell.

Note that MSYS2 provides three different shells: MSYS, MINGW64 and MINGW32. Replacing git -> bash with msys64 -> bash is not enough, unless it defaults to MINGW64.

Since GitHub Actions is adding a MSYS2 installation, I would assume adding it to PATH should work reasonably well.

Ref #908.
MSYS2 provides a built-in mechanism to either inherit the PATH or set a new "clean" env for the shell. For reference, path-type is an option in eine/setup-msys2 and it defaults to strict. eine/setup-msys2 reuses the "default installation" when update: true. Examples of how the action is used can be found in https://github.com/ghdl/ghdl/actions, https://github.com/ghdl/ghdl-cosim/actions or https://github.com/ghdl/setup-ghdl-ci/actions.

@al-cheb, see also actions/toolkit#318.

I made changes to the script and ran it on Actions.  Tried to bullet-proof it, changed the output a bit, including the logging of packages installed.
See Actions step here
I can:

Do nothing
Push it here
Remove the the removal of p7zip and open a new PR

/azp run windows2016, windows2019

I think we can include these changes to the PR.

I've got changes that I can push as a separate commit here, the changes I'm referring to were in the CI I mentioned above, see See Actions step here.
The file is at https://github.com/MSP-Greg/actions-msys2-pkgs/blob/master/Install-Msys2.ps1#L50-L55, highlighted are the changes /additions, along with multiple taskkill /f /fi "MODULES eq msys-2.0.dll" statements.
Note that additional changes were made to logging, especially the package lists.
In general, the main issue here is that MSYS2 got to a state where 'standard update' code did not work (which is fixed in 20200517)).  I've been using MSYS2 for several years, and I think this is only the second time that has happened.
So, I'm not sure we can be certain that whatever code we use can be guaranteed to install/update MSYS2 at every moment in time in the future.  I haven't looked to see if MSYS2 has code checking this, if not, I'll suggest/contribute there.
@eine, any recollection of past issues?
@al-cheb - Thanks, can you have a look at the links?

@MSP-Greg, Thank you for updates. I have run the  Instal-Msys2.ps1 script on a local machine. It works as expected without pre-installed 7z.

@al-cheb
Should I move the changes here with another commit?  Are you ok with the other changes (logging, taskkill, etc)?
It's Friday, be nice for all of us if we can resolve this today...

@MSP-Greg , LGTM. I think we can include all changes in this PR.
@maxim-lobanov, What do you think?

@eine, any recollection of past issues?

Overall, I believe that whoever that will take care of maintaining MSYS2 support in this virtual environment, should watch the main repos of the project and should have close contact with the maintainers (through issues, chat or private channels).
As you said, updating MSYS2 does NOT fail often, but it is a rolling distribution, and it is expected to have issues more frequently than frozen distributions. This is specially so because the (your) decision was to auto-update the environment by default and to include additional packages, as opposed to providing a simple and stable solution. I already explained in our previous discusions that such an approach would imply complications in the maintenance.
To be precise, @lazka is working hard these last weeks, and the only mechanism to be aware of it is to get partially involved: https://github.com/msys2/MSYS2-packages/issues/1962#issuecomment-632703947

I haven't pushed another commit, but below is patch file:
diff --git a/images/win/scripts/Installers/Install-Msys2.ps1 b/images/win/scripts/Installers/Install-Msys2.ps1
index 8c5f859..90971b4 100644
--- a/images/win/scripts/Installers/Install-Msys2.ps1
+++ b/images/win/scripts/Installers/Install-Msys2.ps1
@@ -1,12 +1,14 @@
 ################################################################################
 ##  File:  Install-Msys2.ps1
-##  Desc:  Install Msys2 and 64-bit gcc, cmake, & llvm (32-bit commented out)
+##  Desc:  Install Msys2 and 64 & 32 bit gcc, cmake, & llvm
 ################################################################################

 # References
 # https://github.com/msys2/MINGW-packages/blob/master/azure-pipelines.yml
 # https://packages.msys2.org/group/

+$dash = "—" * 40
+
 $origPath = $env:PATH
 $gitPath  = "$env:ProgramFiles\Git"

@@ -17,7 +19,7 @@ $msys2Uri = ((Invoke-RestMethod $msys2_release).assets | Where-Object {

 $msys2File = "$env:TEMP\msys2.tar.xz"

-# Download the latest msys2 x86_64
+# Download the latest msys2 x86_64, filename includes release date
 Write-Host "Starting msys2 download using $($msys2Uri.split('/')[-1])"
 (New-Object System.Net.WebClient).DownloadFile($msys2Uri, $msys2File)
 Write-Host "Finished download"
@@ -31,7 +33,7 @@ $env:PATH = "$gitPath\usr\bin;$gitPath\mingw64\bin;$origPath"
 $tar = "$gitPath\usr\bin\tar.exe"

 # extract tar.xz to C:\
-Write-Host "Starting msys2 extraction from $msys2FileU"
+Write-Host "Starting msys2 extraction"
 &$tar -xJf $msys2FileU -C /c/
 Remove-Item $msys2File
 Write-Host "Finished extraction"
@@ -39,55 +41,52 @@ Write-Host "Finished extraction"
 # Add msys2 bin tools folders to PATH temporary
 $env:PATH = "C:\msys64\mingw64\bin;C:\msys64\usr\bin;$origPath"

-Write-Host "bash pacman-key --init"
+Write-Host "`n$dash bash pacman-key --init"
 bash.exe -c "pacman-key --init 2>&1"

 Write-Host "bash pacman-key --populate msys2"
 bash.exe -c "pacman-key --populate msys2 2>&1"

-Write-Host "pacman -Sy --noconfirm --needed pacman"
-pacman -Sy --noconfirm --needed pacman
-pacman -Su --noconfirm
-
-# Force stop gpg-agent to continue installation
-Get-Process gpg-agent -ErrorAction SilentlyContinue | Stop-Process -Force
-
-Write-Host "pacman --noconfirm -Syyuu"
+Write-Host "`n$dash pacman --noconfirm -Syyuu"
 pacman.exe -Syyuu --noconfirm
-pacman.exe -Syuu --noconfirm
+taskkill /f /fi "MODULES eq msys-2.0.dll"
+Write-Host "`n$dash pacman --noconfirm -Syuu (2nd pass)"
+pacman.exe -Syuu  --noconfirm
+taskkill /f /fi "MODULES eq msys-2.0.dll"

-Write-Host "Install msys2 packages"
+Write-Host "`n$dash Install msys2 packages"
 pacman.exe -S --noconfirm --needed --noprogressbar base-devel compression
+taskkill /f /fi "MODULES eq msys-2.0.dll"

-Write-Host "Remove p7zip/7z package due to conflicts"
+Write-Host "`n$dash Remove p7zip/7z package due to conflicts"
 pacman.exe -R --noconfirm --noprogressbar p7zip

 # mingw package list
 $tools = "___clang ___cmake ___llvm  ___toolchain ___ragel"

 # install mingw64 packages
-Write-Host "Install mingw64 packages"
+Write-Host "`n$dash Install mingw64 packages"
 $pre = "mingw-w64-x86_64-"
 pacman.exe -S --noconfirm --needed --noprogressbar $tools.replace('___', $pre).split(' ')

 # install mingw32 packages
-Write-Host "Install mingw32 packages"
+Write-Host "`n$dash Install mingw32 packages"
 $pre = "mingw-w64-i686-"
 pacman.exe -S --noconfirm --needed --noprogressbar $tools.replace('___', $pre).split(' ')

 # clean all packages to decrease image size
-Write-Host "Clean packages"
+Write-Host "`n$dash Clean packages"
 pacman.exe -Scc --noconfirm

-Write-Host "Installed mingw64 packages"
-pacman.exe -Qs --noconfirm mingw-w64-x86_64-
+Write-Host "`n$dash Installed mingw64 packages"
+pacman.exe -Q | grep ^mingw-w64-x86_64-

-Write-Host "Installed mingw32 packages"
-pacman.exe -Qs --noconfirm mingw-w64-i686-
+Write-Host "`n$dash Installed mingw32 packages"
+pacman.exe -Q | grep ^mingw-w64-i686-

-Write-Host "Installed msys2 packages"
-pacman.exe -Qs --noconfirm
+Write-Host "`n$dash Installed msys2 packages"
+pacman.exe -Q | grep -v ^mingw-w64-

-Write-Host "MSYS2 installation completed"
+Write-Host "`nMSYS2 installation completed"

-exit 0
\ No newline at end of file
+exit 0

@eine
See https://github.com/msys2/msys2-installer/issues/5.
Re rolling vs release, etc, etc --
I work a lot with Ruby master.  Given that, there is an interest in always using the most recent gcc available.  The most recent packages are zst files.  Without a full MSYS2 update, those can't even be installed.  One example, but there are also security updates (openssl, etc) and other examples.
Also, as I've mentioned before, the home page of msys.org shows updating as part of the normal user install process.  We disagree on this, but we can certainly work together and benefit.  Ok?

@MSP-Greg let's merge this PR for now to include it to next week deployment.
And we can make one more PR with remain changes.
Any concerns / objections?

@MSP-Greg, sure! I believe that tight integration between upstream MSYS2, this repo and setup-msys2 (or any similar Action) is required in order to provide a pleasant UX. Since we are users, we'd better work together to benefit all of us! Let's move the discussion about higher-level strategies to msys2/msys2-installer#5.

@maxim-lobanov
Just to clarify:

Any concerns / objections?

What, me worry?
Sorry.  No, progress is good, and thanks.

And we can make one more PR with remain changes.

So the patch file above I'll open a new PR?  Not sure if it will conflict with this, but I can wait until this is accepted...

@maxim-lobanov
Thanks.  See https://github.com/actions/virtual-environments/pull/928

Ref #355


Make searching for prefix_placeholder string and make async/parallel (and add progress bar?)

We are currently searching for the prefix placeholder string in the files one-by-one. It does take a little while for larger files. Would be nice to

make the function async
parallelize it and run over multiple files at once
Or even parallize it for single large files (chunk the file up and run multiple threads)

Example of a big file package:
package:
  name: big
  version: "0.1.0"

build:
  # prefix_detection:
  #   ignore_binary_files: true
  script:
    - dd if=/dev/urandom of=$PREFIX/bigfile bs=1M count=1000

It would also be good to only mmap the files instead of loading them in memory!

We can close this for now, I made a bunch of performance improvements.


Fix some leftover thing from the last ceil-as-or refactoring.

Make And usage explicit when computing and-of-ceil
Throw an error when or-of-ceil contains a substitution

Reviewer checklist

[ ] Test coverage: stack test --coverage
[ ] Public API documentation: stack haddock
[ ] Style conformance: stylish-haskell

This is not 100% done, I'll add/fix tests tomorrow.


post_delete receiver disappeared

with signal_disabler.disable():
    obj.delete()
# at this line my listeners are not in `post_delete._live_receivers()` anymore
# (and still here in post_delete.receivers)

It looks like Django clears dead receiver while sending corresponding signal, thus this entire package works incorrectly.

I seem to have met the same problem (although I use a slightly different implementation).
I also believe that is strongly correlated with the .delete() call.

Seems like this is the solution to the problem:
https://github.com/FactoryBoy/factory_boy/blob/ae780a38c2311cf6d306797889f09db4d395a6d4/factory/django.py#L297-L301


Write files at simulation run-time

Materials are generated and mutated as objects of the PseudoMaterial class, then dumped to .yaml files within the run directory. .def and .cif files are now created before starting the simulation within the temporary output__ directory.

@paulboone looks like I already PR'd this (with a few things that don't really belong).

Did you want to squash this?

Back in your court... one thing you mentioned is addressed in a later PR.
On Thu, Mar 16, 2017 at 5:31 AM, Paul Boone<EMAIL_ADDRESS>wrote:

@paulboone requested changes on this pull request.
Ok, so the reason why you squash commits like this one...
reformatted writing files, writes them at simulation-time into temporary
dir
... into the prior one is so that I don't have to review the code twice. A
review of about this size takes over an hour and some of the comments on
the prior commit were unnecessary because you changed them here. Squashing
code should be trivial, but reviewing code actually requires a lot of
mental effort. So it is SUPER important to squash fixes into their parent
commits.
Regarding the code itself: I love this architecture change. It opens up a
lot of new things and potential simplifications. Some of the comments I
made have to to with increasing the extent of what your PseudoMaterial
class does, which should lead to further simplifications. We can discuss
more about those in person, if you like!
In htsohm/material_files.py
https://github.com/WilmerLab/HTSOHM-dev/pull/24#discussion_r105213931:

@@ -12,7 +12,7 @@

local application/library specific imports
import htsohm
from htsohm import config
-from htsohm.PseudoMaterial import PseudoMaterial
+from htsohm.pseudo_material import PseudoMaterial
This commit can be squashed into the main commit, since it is a correction
on it.
In htsohm/pseudo_material.py
https://github.com/WilmerLab/HTSOHM-dev/pull/24#discussion_r105214536:

 def __repr__(self):

   return ('%s(' % self.__class__.__name__ +

       'uuid=%r, ' % self.uuid +

       'lattice_constants=%r, ' % self.lattice_constants +

       'atom_types=%r, ' % self.atom_types +

       'atom_sites=%r)' % self.atom_sites

   )

   return ('{0.__class__.__name__!s}('

           '{0.uuid!r}, '

           '{0.lattice_constants!r}, '

           '{0.atom_types!r}, '

           '{0.atom_sites!r})').format(self)

Ah, that's clever. If you found an example somewhere that demonstrated
this, can you send it to me?
In htsohm/material_files.py
https://github.com/WilmerLab/HTSOHM-dev/pull/24#discussion_r106359762:

 ########################################################################

define pseudo atom types by randomly-generating sigma and epsilon values

NOTE :  assignment of partial charges is not supported in this version,

and not necessary when modelling gases without dipole moments

(such as methane). Charge assignment and mutation will appear

in the next stable release.

atom_types = []

db_row = Material(run_id)
db_row.generation = 0
material = PsuedoMaterial(db_row.uuid)

Two naming things here:

generally, it is bad form to assign your data query to a variable
name as generic as db_row, unless it really is a generic db row (such as if
you could be pulling from ANY table, and not a specific one; note that this
case rarely rarely exists). By the time you get to the end of the method,
it is not obvious what db_row is any more. The obvious name for that
variable is still 'material'.
I know you renamed that one so that the PsuedoMaterial (sp) could
be called material. This actually makes this harder to read though because
my reading expectation then is that material is an object of Material and
has the same fields, which it doesn't. The obvious name for this one is
pseudo_material, which I'm sure you skipped because it is long, but I'd
reconsider it. or maybe p_material, or psuedo_mat or something

In htsohm/material_files.py
https://github.com/WilmerLab/HTSOHM-dev/pull/24#discussion_r106360783:

########################################################################
material = Material(run_id)
material_name = run_id + '-' + material.uuid
material.generation = 0

def_dir = os.path.join(ff_dir, material_name)       # directory for material's force field
os.mkdir(def_dir)
force_field_file = os.path.join(def_dir, 'force_field.def')      # for overwriting LJ-params
write_force_field(force_field_file)

htsohm_dir = os.path.dirname(os.path.dirname(htsohm.file))
run_dir = os.path.join(htsohm_dir, run_id)
material_dir = os.path.join(run_dir, 'pseudo_materials')
if not os.path.exists(material_dir):

   os.mkdir(material_dir)

You have this block of code below too. Maybe extract it into methods with
signatures like:
def get_htsohm_dir():
return os.path.dirname(os.path.dirname(htsohm.file))
def get_run_dir(run_id):
return os.path.join(get_htsohm_dir(), run_id)
def get_material_dir(run_id):
material_dir = os.path.join(get_run_dir(run_id), 'pseudo_materials')
if not os.path.exists(material_dir):
os.mkdir(material_dir)
return material_dir
def get_dirs(run_id):
return [get_htsohm_dir(), get_run_dir(run_id), get_material_dir(run_id)]
In htsohm/material_files.py
https://github.com/WilmerLab/HTSOHM-dev/pull/24#discussion_r106362216:

 ########################################################################

copy pseudo_atoms.def

parent_forcefield_directory = os.path.join(ff_dir, run_id + '-' + str(parent.uuid))
parent_pseudo_file = os.path.join(parent_forcefield_directory, 'pseudo_atoms.def')
shutil.copy(parent_pseudo_file, child_forcefield_directory)    # COPY PSEUDO_ATOMS.DEF
print('  - pseudo_atoms.def\tWRITTEN.')

add row to database

Technically, this doesn't add a row to the database any more (that only
happens with save). Maybe use: "Create material" ?
In htsohm/material_files.py
https://github.com/WilmerLab/HTSOHM-dev/pull/24#discussion_r106362797:

 ########################################################################

 # remove excess atom-sites, if any

if number_of_atoms < len(old_x):

   difference = len(old_x) - number_of_atoms

   old_x = old_x[:-difference]

   old_y = old_y[:-difference]

   old_z = old_z[:-difference]

if number_of_atom_sites < len(parent_material.atom_sites):

   parent_material.atom_sites = parent_material.atom_sites[

           :number_of_atom_sites]

You are recycling a variable here, this code implies to me that you are
changing the parent_material. Which would be a huge bug. Rather than
change the parent_material.atom_sites, create a new variable called
atom_sites, or just copy the parent_material.atom_sites to the child, and
perturb there.
In htsohm/material_files.py
https://github.com/WilmerLab/HTSOHM-dev/pull/24#discussion_r106363128:

 ########################################################################

 # remove excess atom-sites, if any

if number_of_atoms < len(old_x):

   difference = len(old_x) - number_of_atoms

   old_x = old_x[:-difference]

   old_y = old_y[:-difference]

   old_z = old_z[:-difference]

if number_of_atom_sites < len(parent_material.atom_sites):

   parent_material.atom_sites = parent_material.atom_sites[

           :number_of_atom_sites]

Also, if there are fewer atom sites than previously, do you want to pick
which ones you perturb randomly, as opposed to always taking the first n
sites?
In htsohm/material_files.py
https://github.com/WilmerLab/HTSOHM-dev/pull/24#discussion_r106363960:

########################################################################

write force_field.def

child_forcefield_directory = os.path.join(ff_dir, run_id + '-' + str(new_material.uuid))
os.mkdir(child_forcefield_directory)
force_field_file = os.path.join(child_forcefield_directory, 'force_field.def')
write_force_field(force_field_file)                        # WRITE FORCE_FIELD.DEF
print('  - force_field.def\tWRITTEN.')

parent_row = session.query(Material).get(str(parent_id))
parent_yaml = os.path.join(material_dir, '%s.yaml' % parent_row.uuid)
with open(parent_yaml) as load_file:

   parent_material = yaml.load(load_file)

Same naming thing as above: you're shortening the name
parent_pseudo_material to parent_material which confuses it with the actual
"parent material" which is called parent_row.
In htsohm/material_files.py
https://github.com/WilmerLab/HTSOHM-dev/pull/24#discussion_r106365656:

 ########################################################################

 # calulate new number density, number of atoms

old_ND = len(old_x) / (old_a * old_b * old_c)
random_ND = round(uniform(*number_density_limits), 4)
number_density = old_ND + mutation_strength * (random_ND - old_ND)
number_of_atoms = int(number_density * a * b * c)

old_LCs = parent_material.lattice_constants
old_vol = old_LCs['a'] * old_LCs['b'] * old_LCs['c']
old_number_density = len(parent_material.atom_sites) / old_vol
random_number_density = uniform(*number_density_limits)
new_number_density = (old_number_density + mutation_strength * (

       random_number_density - old_number_density))

new_LCs = child_material.lattice_constants
new_vol = new_LCs['a'] * new_LCs['b'] * new_LCs['c']
number_of_atom_sites = int(new_number_density * new_vol)

Since PsuedoMaterial is a class now, maybe we should load the yaml for the
parent straight into an instance of PsuedoMaterial. Then you could add
methods like density() and volume() and number_of_atoms() which would get
calculated straight off the instance variables. Then I think this code
could simplify to something like:
random_number_density = uniform(*number_density_limits)
new_number_density = parent.old_number_density + mutation_strength *
(random_number_density - parent.old_number_density)
child_material.number_of_atoms = int(new_number_density *
child_material.volume())
Probably we could simplify a lot of this method by consolidating the logic
into your PseudoMaterial class....
In htsohm/material_files.py
https://github.com/WilmerLab/HTSOHM-dev/pull/24#discussion_r106365939:

   atom_types.append(atom_type)

   mix_file = os.path.join(child_forcefield_directory, 'force_field_mixing_rules.def')

   write_mixing_rules(mix_file, atom_types)

   print('  - force_field_mixing_rules.def\tWRITTEN.')

perturb LJ-parameters

child_material.atom_types = []
for atom_type in parent_material.atom_types:

   new_atom_type = {'chemical-id' : atom_type['chemical-id']}

   new_atom_type['epsilon'] = (round(atom_type['epsilon'] +

           mutation_strength * (uniform(*epsilon_limits) -

           atom_type['epsilon']), 4))

   new_atom_type['sigma'] = (round(atom_type['sigma'] +

           mutation_strength * (uniform(*epsilon_limits) -

           atom_type['epsilon']), 4))

   child_material.atom_types.append(new_atom_type)

Copy, then perturb in place?
In htsohm/material_files.py
https://github.com/WilmerLab/HTSOHM-dev/pull/24#discussion_r106366119:

 # calculate new lattice constants

old_a = old_abc[0]
old_b = old_abc[1]
old_c = old_abc[2]
random_a = round(uniform(*lattice_limits), 4)
random_b = round(uniform(*lattice_limits), 4)
random_c = round(uniform(*lattice_limits), 4)
a = round(old_a + mutation_strength * (random_a - old_a), 4)
b = round(old_b + mutation_strength * (random_b - old_b), 4)
c = round(old_c + mutation_strength * (random_c - old_c), 4)
lattice_constants = {"a" : a, "b" : b, "c" : c}

child_material.lattice_constants = {}

this is redundant; should already be defined in PseudoMaterial, right?
In htsohm/material_files.py
https://github.com/WilmerLab/HTSOHM-dev/pull/24#discussion_r106366895:

 # calculate new lattice constants

old_a = old_abc[0]
old_b = old_abc[1]
old_c = old_abc[2]
random_a = round(uniform(*lattice_limits), 4)
random_b = round(uniform(*lattice_limits), 4)
random_c = round(uniform(*lattice_limits), 4)
a = round(old_a + mutation_strength * (random_a - old_a), 4)
b = round(old_b + mutation_strength * (random_b - old_b), 4)
c = round(old_c + mutation_strength * (random_c - old_c), 4)
lattice_constants = {"a" : a, "b" : b, "c" : c}

child_material.lattice_constants = {}
for i in ['a', 'b', 'c']:

   old_x = parent_material.lattice_constants[i]

   random_x = uniform(*lattice_limits)

   new_x = round(old_x + mutation_strength * (random_x - old_x), 4)

I wouldn't round here. Let your object contain full floats, then round
when we write to the YAML file. Same with other rounds. You want to have a
distinction between your in-memory model and your on-disk format /
presentation and this is mixing them.
In htsohm/material_files.py
https://github.com/WilmerLab/HTSOHM-dev/pull/24#discussion_r106368065:

old_b = old_abc[1]

old_c = old_abc[2]
random_a = round(uniform(*lattice_limits), 4)
random_b = round(uniform(*lattice_limits), 4)
random_c = round(uniform(*lattice_limits), 4)
a = round(old_a + mutation_strength * (random_a - old_a), 4)
b = round(old_b + mutation_strength * (random_b - old_b), 4)
c = round(old_c + mutation_strength * (random_c - old_c), 4)
lattice_constants = {"a" : a, "b" : b, "c" : c}

child_material.lattice_constants = {}
for i in ['a', 'b', 'c']:

   old_x = parent_material.lattice_constants[i]

   random_x = uniform(*lattice_limits)

   new_x = round(old_x + mutation_strength * (random_x - old_x), 4)

   child_material.lattice_constants[i] = new_x

if you used a copy / perturb pattern, this could look something like:
child_material.lattice_constants = parent_material.lattice_
constants.copy()
for i in ['a', 'b', 'c']:
old_x = parent_material.lattice_constants[i]
random_x = uniform(*lattice_limits)
child_material.lattice_constants[i] += mutation_strength * (random_x -
old_x)
Probably a way of simplifying it more
In htsohm/material_files.py
https://github.com/WilmerLab/HTSOHM-dev/pull/24#discussion_r106368573:

       atom_sites.append(atom_site)

cif_file = os.path.join(mat_dir, run_id + '-' + str(new_material.uuid) + '.cif')
write_cif_file(cif_file, lattice_constants, atom_sites)

return new_material

       new_atom_site = {

               'chemical-id' : choice(

                   child_material.atom_types)['chemical-id']}

       for i in ['x-frac', 'y-frac', 'z-frac']:

           new_atom_site[i] = round(random(), 4)

       atom_sites.append(new_atom_site)

material_file = os.path.join(material_dir, '%s.yaml' % uuid)
with open(material_file) as dump_file:

   yaml.dump(child_material, dump_file)

We might consider sticking the yaml save on your PseudoMaterial class so
the the PsuedoMaterial class knows how to save and load itself.
In htsohm/material_files.py
https://github.com/WilmerLab/HTSOHM-dev/pull/24#discussion_r106368892:

@@ -290,31 +292,45 @@ def write_cif_file(file_name, lattice_constants, atom_sites):
$(raspa-dir)/structures/cif/(run_id)-(uuid).cif

 """

htsohm_dir = os.path.dirname(os.path.dirname(htsohm.file))
run_dir = os.path.join(htsohm_dir, run_id)
material_dir = os.path.join(run_dir, 'pseudo_materials')
file_path = os.path.join(material_dir, "%s.yaml" % uuid)

same as before regarding consolidating this somewhere
In htsohm/material_files.py
https://github.com/WilmerLab/HTSOHM-dev/pull/24#discussion_r106369092:

@@ -290,31 +292,45 @@ def write_cif_file(file_name, lattice_constants, atom_sites):
$(raspa-dir)/structures/cif/(run_id)-(uuid).cif

 """

htsohm_dir = os.path.dirname(os.path.dirname(htsohm.file))
run_dir = os.path.join(htsohm_dir, run_id)
material_dir = os.path.join(run_dir, 'pseudo_materials')
file_path = os.path.join(material_dir, "%s.yaml" % uuid)
with open(file_path) as material_file:

   material = yaml.load(material_file)

rather than open / load the file here, maybe it would make more sense to
just pass it to the method? It would decouple that.
 IN THIS VERSION.

 """

temporary_charge = 0.

htsohm_dir = os.path.dirname(os.path.dirname(htsohm.file))
run_dir = os.path.join(htsohm_dir, run_id)
material_dir = os.path.join(run_dir, 'pseudo_materials')
file_path = os.path.join(material_dir, "%s.yaml" % uuid)
with open(file_path) as material_file:

   material = yaml.load(material_file)

Again, pass the pseudo_material file in, rather than load it? Also, we
have the naming confusion here again between a material and pseudo_material
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/WilmerLab/HTSOHM-dev/pull/24#pullrequestreview-26082554,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHtyl8Xieax58OqpCGPrHj9DapNbxvwoks5rmQFpgaJpZM4LyArm
.

--
Alec Kaija
PhD-candidate
WilmerLab, SSOE
University of Pittsburgh
www.wilmerlab.com
www.github.com/akaija/
CTO, Co-Founder
Aeronics
www.aeronicsinc.com

Learn to use git add --patch for the future.... some of these commits should be divided up. But code looks good.

Learn to use git add --patch for the future.... some of these commits should be divided up. But code looks good.


Support net8.0 TFM

New year, new https://github.com/fsprojects/Paket/issues/4119

If someone could provide a PR, then I'm happy to merge and release

Great stuff, thanks @forki 💪

Taking a look at it: #4219

thanks @smoothdeveloper . I just released it as 8.0.0-alpha001

It works, much obliged.


Build failure: z3

Steps To Reproduce
Steps to reproduce the behavior:

build Z3 on darwin: nix build #legacyPackages.z3 on nixpkgs 16e046229f3b4f53257973a5532bcbb72457d2f2

Build log

Build Log
error: builder for '/nix/store/pqpa53lbgzinil8gdv8m7qwbvdhj0ypm-z3-4.8.17.drv' failed with exit code 2;
       last 25 log lines:
       > src/nlsat/nlsat_evaluator.cpp
       > src/nlsat/nlsat_explain.cpp
       > src/nlsat/nlsat_solver.cpp
       > src/ast/ast_pp_util.cpp
       > src/ast/recfun_decl_plugin.cpp
       > src/ast/reg_decl_plugins.cpp
       > src/math/polynomial/upolynomial_factorization.cpp
       > In file included from ../src/math/lp/nex_creator.cpp:8:
       > In file included from ../src/math/lp/nex_creator.h:12:
       > In file included from ../src/math/lp/nex.h:10:
       > In file included from ../src/math/lp/nla_defs.h:13:
       > ../src/math/lp/column_info.h:50:58: error: no member named 'm_low_bound' in 'column_info<T>'; did you mean 'm_lower_bound'?
       >    50 |             (!m_lower_bound_is_set || m_lower_bound == c.m_low_bound) &&
       >       |                                                          ^~~~~~~~~~~
       >       |                                                          m_lower_bound
       > ../src/math/lp/column_info.h:37:17: note: 'm_lower_bound' declared here
       >    37 |     T           m_lower_bound;
       >       |                 ^
       > src/opt/opt_pareto.cpp
       > src/tactic/fpa/fpa2bv_model_converter.cpp
       > src/tactic/smtlogics/qfufbv_ackr_model_converter.cpp
       > src/tactic/smtlogics/smt_tactic.cpp
       > 1 error generated.
       > make: *** [Makefile:1524: math/lp/nex_creator.o] Error 1
       > make: *** Waiting for unfinished jobs....
       For full logs, run 'nix log /nix/store/pqpa53lbgzinil8gdv8m7qwbvdhj0ypm-z3-4.8.17.drv'.

Additional context

Possibly related: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281512
Metadata

 - system: `"aarch64-darwin"`
 - host os: `Darwin 24.2.0, macOS 15.2`
 - multi-user?: `yes`
 - sandbox: `no`
 - version: `nix-env (Nix) 2.24.9`
 - nixpkgs: `/nix/store/0z5aw6jjbjq9sqcd03gfa7zkk25nzwgc-source`

Notify maintainers

@thoughtpolice @ttuegel

Note for maintainers: Please tag this issue in your PR.

Add a :+1: reaction to issues you find important.

https://github.com/NixOS/nixpkgs/pull/368333


Unexpected "test" appears in Terminal output while packaging mobile

Example (before "NOTE"):

Adobe AIR code signing password:
testNOTE: The application has been packaged with a captive runtime.
Terminal will be reused by tasks, press any key to close it.

I think this is fixed already because I don't see the string "test" anywhere in my code.

Sorry, found it mentioned before, here https://github.com/BowlerHatLLC/vscode-as3mxml/issues/230
It is from AIR 19 adt:


Which Hygraph Endpoint do we use?

+1 which one?

You can find the Hygraph endpoint on Project Settings -> API Access -> Content API


Library use: allow resources as a template

Is your feature request related to a problem? Please describe.

As a user of copier API, I'd like to store my template together with my project, similar to direct Jinja usage (jinja.PackageLoader).
The template and the code are tightly coupled so it would make the development easier.
Describe the solution you'd like
Copier could accept a special resource:[project]:[path] URI as the src_path.
Internally it could use importlib.resources (or importlib_resources backport project) to find and load template files. Version could be resolved with importlib.metadata.version (would require copier to know the distribution package - [project] part).
Describe alternatives you've considered

Keeping template in a separate branch - doesn't really bring much from the developers perspective. It only helps keeping the template in the same repo. Needs some kind of versioning scheme.
inferring src_path from Path(__file__) - would not work if my project is installed from wheel
manually copying template from project to /tmp - looses versioning information and breaks run_update.
Copier could be changed to accept a path within the repository - this partial solution would still require committing and pushing changes before testing update.

Hi again! Probably the solution for your problem is something you already said:

Copier could be changed to accept a path within the repository

You can do this with _subdirectory already. See https://copier.readthedocs.io/en/stable/configuring/#subdirectory

this partial solution would still require committing and pushing changes before testing update.

If your template is local and you use vcs_ref="HEAD", it will include local dirty changes automatically.
Or at least that's what it's supposed to do. It seems there's a bug there somewhere. Follow #787 for the fix. But fixing that issue is more scoped than this proposal.
Remember that Copier aims to be not much python-specific, so we can template all kinds of projects. At first sight your proposal will mean more python-specific stuff and probably more complexity around what are the assumptions we have currently on templates, so it's not very appealing to implement TBH.
I'll close this as there are no plans to implement, but feel free to continue discussing or even propose a prototype.

Yeah, id does seem like the cost would outweigh the benefit. Abstracting VCS layer would allow copier to use other systems, like Mercurial, but... who cares really?
Thanks for the _subdirectory suggestion!

Abstracting VCS layer would allow copier to use other systems, like Mercurial, but... who cares really?

That was the initial idea, but you're right. Everybody uses git, after all, so it still hasn't become a real need.


MDC 30

[x] Rename SimpleMenu to Menu and all relevant classes
[x] Create an RMWC simple menu that can automatically handle the open state
[x] It seems like dark themes have been removed altogether? Validate this and adjust accordingly.
[x] Add a chip component
[x] remove cssOnly select
[x] add box version of Select and validate non-box version works appropriately
[x] mdc-text-field__bottom-line -> mdc-line-ripple
[x] mdc-checkbox__checkmark__path -> mdc-checkbox__checkmark-path
[x] Cards layouts have been completely gutted, respond accordingly
[x] addition of mdc-button__icon
[x] return of the mini fab... mdc-fab--mini
[ ] match minor version to MDC for next release.

What's the reason for removing all of the "css-only" components? Seems like something lot's of users actually need. Especially for a select component e.g. on mobile...

Regarding Textfield mdc-text-field__bottom-line. I think it is mdc-line-ripple now and it will be a new component in rmwc?

Also, how can I add breaking changes into the changelog? Regarding the change of SimpleMenu -> Menu?

Thanks for jumping on this one @j-o-d-o!

I think the reason they are removing the css-only components is because they can't guarantee styling or functionality across browsers. In the instance of select, it makes a lot of sense, but the cssOny one never matched up exactly with the JS one. Whats your thoughts on supporting a cssOnly select directly in RMWC? It would be the first attempt at preventing a breaking change but might also involve doing some stying which RMWC doesn't currently include.

You are correct on mdc-line-ripple. Apparently they called it bottom line first and then changed the name

for the changelog, follow the patterns here. For breaking you can simply type breaking(Select): my description.... I know it's annoying, but if you can amend that specific commit title then the changelog will be generated appropriately.

Lets keep that mdc30 branch open and keep working off of it until we get all of the features in there.

Maybe we can convince the people over at material-components-web to have a blog related to why they are doing the things they are? It would really help with dramatic changes like this. I don't know how to get them to do that though other than opening an issue that looks like I'm just complaining. Either way, I asked them to keep the docs updated politely and that hasn't happened at all :(.

I would opt against specific RMWC cssOnly components, mainly because of having to bring in styling from RMWC. Let's keep it simple ; ).
I'd much more prefer to know why major breaking changes are happening. Not sure though how to properly communicate that ... I think it would even be enough if they have a proper statement on the PRs instead of a message like: "Remove css only version of select." ... I mean, thanks a lot, I can see that information in the PR title already...
Changed the commit messages, had to rebase and force push, so I hope it doesn't mess up anything for others working on the branch.

Ya they seem to be chugging along to their own song. Seems like they are working on a Material 2.0 atm and material-web-components is moving in that direction. Think they will announce at I/O this year. They do have a pivotal tracker as well.

So when the rmwc user wants an menu with an open state, he/she has to use the startOpen property. But of course the open prop must be true also, otherwise it is open but will close onUpdate(). I'd say that is common sense?
Also I am not sure this is a bug, or is the menu supposed to be to the right of the button when using mdc-menu--open? https://codepen.io/j-o-d-o/pen/zppEdL

It doesn't make much sense to me to expose a startOpen prop. Open should mean open in case of React. We should just catch it and adjust accordingly.
The SimpleMenu component I mentioned in the list is just an idea to have a component that automatically manages the open state because in my experience, 99% of the time you just need the menu to open when you click a button, and close when something is clicked or clicked off of.
Believe it or not, I actually have another UI library for work that wrap this one (mostly to add additional items, and style for our apps). This is the wrapper I wrote for it:
/**
 * A Simplified menu component that allows you to pass a handle element and will automatically control the open state and add a MenuAnchor
 */
export class SimpleMenu extends React.Component<
  SimpleMenuPropsT,
  SimpleMenuStateT
> {
  static displayName = 'SimpleMenu';

  componentWillMount() {
    this.syncWithOpenProp(this.props.open);
  }

  componentWillReceiveProps(nextProps) {
    this.syncWithOpenProp(nextProps.open);
  }

  state = {
    open: false
  };

  syncWithOpenProp(open) {
    if (open !== undefined && this.state.open !== open) {
      this.setState({ open });
    }
  }

  render() {
    const {
      handle,
      onClose,
      children,
      rootProps = {},
      open,
      ...rest
    } = this.props;
    const wrappedHandle = React.cloneElement(handle, {
      ...handle.props,
      onClick: evt => {
        this.setState({ open: true });
        if (handle.props.onClick) {
          handle.props.onClick(evt);
        }
      }
    });

    const wrappedOnClose = evt => {
      this.setState({ open: false });
      if (onClose) {
        onClose(evt);
      }
    };
    return (
      <MenuAnchor {...rootProps}>
        <Menu onClose={wrappedOnClose} open={this.state.open} {...rest}>
          {children}
        </Menu>
        {wrappedHandle}
      </MenuAnchor>
    );
  }
}

Usage
<SimpleMenu handle={<Button>Open Me<Button>}>
  <MenuItem />
  ...
</SimpleMenu>

Btw, thanks for your help on this @j-o-d-o and @izakfilmalter . Haven't had time to get to it yet this week and it's awesome to see progress being made.

@jamesmfriedman yeah that actually makes more sense, I will adjust that!
The SimpleMenu looks like a convenient addition to the library.

I used the api.quickOpen to open the menu on mounting without animation if the initial state of open=true.

Perfect, thanks @j-o-d-o. I'm going to jump in and write some code for this tonight and tomorrow. Thanks for getting it off to a get start.

@j-o-d-o I'm going to work on chips, button icon, dark theme removal and fab mini

Just need to take care of the cards and we'll be good to go.
Also @lynnjepsen dropped an issue with #141. I'm curious at looking into doing a direct foundation implementation to see how it matches up. Probably out of scope for this particular release, but wanted to look into it and see if it was worth taking a simpler component and integrating with it.
Lastly, whats your thoughts on matching the release numbers up with MCW? We can't drop below the major version, but maybe make it 1.30.0 to kind of match MCW 0.30.0?

Pretty much wrapped up @j-o-d-o and @izakfilmalter. Please review the changes. I have one small issue I want to inspect (text field labels seems misaligned) but other than that I'm good to go.

I'm really rethinking the cssOnly select removal.
As far as RMWC goes, why not provide a wrapper? There is already a non-standard declarative way to handle selects in a data-driven way. It seems trivial to render a standard select element with options and just tell people they are required to style it on their own.
I know this would make @izakfilmalter life a lot easier. Otherwise you always have to handle both your self which seems pretty terrible.

I wouldn't mind if it was a package and this became like a mono repo. Long
term it's tough.
On Mon, Feb 12, 2018, 2:12 PM James Friedman<EMAIL_ADDRESS>wrote:

I'm really rethinking the cssOnly select removal.
As far as RMWC goes, why not provide a wrapper? There is already a
non-standard declarative way to handle selects in a data-driven way. It
seems trivial to render a standard select element with options and just
tell people they are required to style it on their own.
I know this would make @izakfilmalter https://github.com/izakfilmalter
life a lot easier. Otherwise you always have to handle both your self which
seems pretty terrible.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/jamesmfriedman/rmwc/issues/139#issuecomment-365030034,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFmimglJUAnAN4CF8DFbzzmToVlMxt88ks5tUI0ggaJpZM4R6c-g
.

Can you elaborate? Whats a mono-repo?

Kinda like create-react-app. I think they use https://github.com/lerna/lerna
to have many npm packages in the same repo.
On Mon, Feb 12, 2018, 3:16 PM James Friedman<EMAIL_ADDRESS>wrote:

Can you elaborate? Whats a mono-repo?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/jamesmfriedman/rmwc/issues/139#issuecomment-365048309,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFmimrkYVNUpdG4Dau6F0q3t4yUEbAPHks5tUJwFgaJpZM4R6c-g
.

Awww. Yes, I would like that a lot, especially because I want to support community packages and allow for people to only install what they need.
Until then, do you think we should the Select handle cssOnly in the main code base?

I think it's out of scope.
On Mon, Feb 12, 2018, 3:45 PM James Friedman<EMAIL_ADDRESS>wrote:

Awww. Yes, I would like that a lot, especially because I want to support
community packages and allow for people to only install what they need.
Until then, do you think we should the Select handle cssOnly in the main
code base?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/jamesmfriedman/rmwc/issues/139#issuecomment-365056226,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFmimkhwsnH6Xbbgct1Z0RIpgoDIlszpks5tUKMGgaJpZM4R6c-g
.

Didn't end up matching the minor version, but the rest is done and deployed. Good job guys! 🥇

Really nice but open=true doesn't seem to work when we have styles that override the styles of the MenuItem. I mean it still does the animation for the text and  background color of the MenuItems.

@binarybaba can you elaborate please? This is a really old issue, and the library has changed quite a bit since. If you’re experiencing a problem can you open a new issue?


Verbosity

What's the verbose syntax?

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

ID: 121d0d1b-bb16-7b85-2529-297856a6e8ca
Version Independent ID: 1795dd9d-a94b-3f47-a6d6-686fa9234a8c
Content: Namespaces (F#)
Content Source: docs/fsharp/language-reference/namespaces.md
Service: dotnet-fsharp
GitHub Login: @cartermp
Microsoft Alias: phcart

@RoswellMiller verbose syntax isn't mentioned in this article. Verbose syntax is documented today. I'll close this out unless there is a specific issue in this article.


Uncaught TypeError: startPoint is undefined

https://github.com/meshesha/PPTXjs/blob/45112145f958d379040b4ab6a726bdf83e75bc8e/js/pptxjs.js#L6837
When trying to open: 9119-3d-cubes-template.pptx

Download link: https://slidehunter.com/download/10642/

I can open the file with: https://github.com/g21589/PPTX2HTML

thank you. I'll check it out.

fixed in v1.21.00


Utf-8 issue with demo project with non english languages

All files used are from release Version 0.3.4.
Following instructions in readme i can't init demo project. See PrjLog.txt
Looking in solved problems I found issue #14, in a comment is requested change language to English of the operating system to solve a similar problem. And it have worked for me too.
My main language is Spanish, following your instrucions i have executed mklink command and I recieved this "mklink /J "E:\Projeny-tests\UnityProjects\jor" "E:\Projeny-tests\UnityProjects\SphereMover\ProjectSettings"
Unión creada para E:\Projeny-tests\UnityProjects\jor <<===>> E:\Projeny-tests\UnityProjects\SphereMover\ProjectSettings"
I thought that issue had already been fixed in the latest release, someone can help me?
Thanks in advance.

Hmm that's odd.  I just tried to reproduce the issue using Version 0.3.4 and with Spanish language enabled and it worked fine.  I also confirmed that executing "mklink /J x y" prints out "Unión creada para y <<===>> x" just like in your case.
Can you try running from source?  Would be helpful to see a call stack of where his is happening

Or alternatively, can you try installing this and trying it again?  It has a change I'm guessing might help
ProjenyInstaller-v0.3.4.zip

Hi svermeulen,
Is all my fault, I had an previous version of projeny and a windows path linked to that old version.
I'm really sorry I wasted your time.
Best regards.

Ok glad to hear you got it sorted


youtube device support error

When trying to download files, there is now a video in several languages saying that youtube is moving to a new version of the api, and directs to youtube.com/devicesupport . This page says that the old api is going down this month. Is there a workaround yet?

It's fixed in the git master, you'll have to wait until the next release or use the version from the repo. For future reports, please post the output you get with the --verbose option.


Version 0.10 release prep

[x] finalise version number
[x] changelog
[x] depend on updated regional visualisation plugin (pyproject.toml)

These are all done, v0.10 was released


Incorrect Tokenurl from metadata service (jfinscan)

Investigate token url & metadata on jfinscan

TODO:

[ ] StaticMetadataService  (https://testnet.jfinscan.com/address/0x999f325bddf75c810861c71388e5b65efefa8406)

rewrite so that uri() takes a token id and concat with base url https://discord.com/channels/1014811256684818513/1077912056696676464/1207938959179522118
initialize base url with https://jns-metadata.jfinchain.com/name/, https://jns-metadata.testnet.jfinchain.com/name/
apply new metadata service contract to NameWrapper

[ ] Deploy separated metadata services for mainnet vs testnet

mainnet : jns-metadata-service, map to jns-metadata.jfinchain.com
testnet : jns-metadata-service-testnet, map to jns-metadata.testnet.jfinchain.com


PydanticImportError: BaseSettings has been moved to the pydantic-settings package.

Initial Checks

[X] I confirm that I'm using Pydantic V2

Description
I am using the Chroma vector datastore and creating embeddings using OpenAI embedding. However, I am facing an error while imparting the Chroma database.

Example Code
No response
Python, Pydantic & OS Version
pydantic version: 2.3.0
        pydantic-core version: 2.6.3
          pydantic-core build: profile=release pgo=false
                 install path: C:\Users\Amitk\AppData\Local\Programs\Python\Python311\Lib\site-packages\pydantic
               python version: 3.11.4 (tags/v3.11.4:d2340ef, Jun  7 2023, 05:45:37) [MSC v.1934 64 bit (AMD64)]
                     platform: Windows-10-10.0.22621-SP0
     optional deps. installed: ['typing-extensions']

Hi @amitsubhashchejara,
Thanks for your question. Looks like you've got a dependency conflict going on. If this is indeed the package you're mentioning, its latest version requires Pydantic <2.0, whereas you have v2.30 installed. If you install Pydantic v1.10, this error should go away.


Multiple presenters per activity

The @RequiresPresenter annotation is not repeatable, but I have multiple presenters in my activity (one for populating a menu dynamically, one for the content, etc). Is there a way I can use nucleus? I really like how it handles config changes.

I see three options here:

Join presenters.
Split activity into separated views, each with its own presenter.
Create a custom base class - just copy-paste NucleusActivity code and have any amount of presenters you wish.

I'm looking at the NucleusActivity but can't tell what I need to change to able to accommodate multiple presenters.

Copy-paste `presenterDelegate as many times as you need presenters. Give them custom factories.


Obtain Production Servers

Work with ITS to provide us with the necessary server infrastructure to support this project.

[x] Establish a server on the DMZ for hosting the public facing mirror.
[x] Establish a server on the private network, behind the Joint VPN for administrative access.
[ ] Assure database backups are in place for both servers.
[x] Obtain a domain name, registered through UVA and attach it to the public mirror.
[ ] Test connections between the servers.

Dan, moving this ticket to "In Progress" since I remember you mentioning that you have done some/all of this ticket.  Pls move it further down the line if have completed this work, or check off the items done in the description.  Thx!

Closing per discussion with Dan.


pax-url-aether using org.apache.httpcomponents_httpclient v4.5.6 having CVE-2020-13956 vulnerability

pax-url-aether is having org.apache.httpcomponents_httpclient 4.5.6 which is vulnerable. Please update it to a non-vulnerable version like 5.0.3, 4.5.13.
This gets reflected in the security scans that run after production releases.
Ref: https://nvd.nist.gov/vuln/detail/CVE-2020-13956

Actually httpclient 4.5.6 is coming from wagon-http dependency. So, I have either:

upgrade wagon version
exclude httpclient from wagon and define httpclient in pax-url-aether
Let me check the wagon update first.

OK, upgrading to wagon 3.4.3 doesn't help as it still uses httpclient 4.5.6. I'm excluding httpclient from wagon-http and update httpclient in pax-url-aether.

Actually, for the record, I will update both wagon and httpclients all together.