Apple can’t check app for malicious software.

Operating System Info
macOS 13 Ventura
App Library Version
Version 0.1.0
Current Behavior
Apple Gatekeeper Rejected App Library, and say "Apple can’t check app for malicious software"
Please go through Apple's notary service.

Apologies!  The mac app release process is new to me 😅
App Library is now notarized in the 0.1.1 release.


[Quick Modelling] Binning

The squares in which the mean is taken might make the binning go wrong

Solved, But binning is only viable 2 powers of 2 down, or too much information is lost


python3Packages.django-anymail: fix package

Description of changes
Current django-anymail package doesn’t build:

Version 10.1 of the package doesn’t have a setup.py anymore (uses pyproject.toml with hatchling)
The test suite doesn’t use pytest
Some tests require network access (setting CONTINUOUS_INTEGRATION skips them)

(I tried updating the package to 10.2 but it uses the Django 5.0 classifier which doesn’t seem to be available in the hatchling version in nixpkgs)
Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/3100

No idea why this error is thrown, but it is the cause for ofborg claiming 0 rebuilds
[nix-shell:/dev/shm/nixpkgs-review/pr-272050]$ nom-build nixpkgs/ -A python3Packages.django-anymail
error: assertion '((pyproject != null) -> (format == null))' failed

       at /dev/shm/nixpkgs-review/pr-272050/nixpkgs/pkgs/development/interpreters/python/mk-python-derivation.nix:110:1:

          109|
          110| assert (pyproject != null) -> (format == null);
             | ^

Done.

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

4 packages built:

python310Packages.django-anymail
python310Packages.django-anymail.dist
python311Packages.django-anymail
python311Packages.django-anymail.dist


Adding more CSS Quesitons

Pull Request Checklist

[x] You are submitting only one flashcard.

[x] You have verified that the information is correct, via a book, ChatGPT etc.

[x] You are using the below pattern to add the flashcard:
###### Question number.

Question goes here

Answer

Answer goes here

Updating the question to a new one.


Mustache Integration

Create a module supporting Mustache templates. The actual integration will be based on Jersey MVC. Late we may create modules for  Freemarker and JSP templates.
This module will depend on bootique-jersey, and template rendering will be done via JAX-RS.

done integrating Jersey MVC.. Will need to tweak that for sanity.


Strange behavior when installing aiohttp on Python 3.6

Long story short

_websocket.cp36-win32.pyd and _websocket.cp36-win_amd64.pyd's are not compiled upon installing on Python 3.6
Expected behaviour

To be able to have those pyd files on Python 3.6 Like I have them on 3.5.
Actual behaviour

on 3.5:

on 3.6:

Steps to reproduce

On Python 3.5 x64:
python.exe -m pip install --target "E:\Users\Elsword\Desktop\DecoraterBot\Async\resources\Dependencies\win32-deps\3.5" --no-compile --upgrade aiohttp

On Python 3.5 x86:
python.exe -m pip install --target "E:\Users\Elsword\Desktop\DecoraterBot\Async\resources\Dependencies\win32-deps\3.5\x86" --no-compile --upgrade aiohttp

On Python 3.6 x64:
python.exe -m pip install --target "E:\Users\Elsword\Desktop\DecoraterBot\Async\resources\Dependencies\win32-deps\3.6" --no-compile --upgrade aiohttp

On Python 3.6 x86:
python.exe -m pip install --target "E:\Users\Elsword\Desktop\DecoraterBot\Async\resources\Dependencies\win32-deps\3.6\x86" --no-compile --upgrade aiohttp

Your environment

Python 3.5 & 3.6
aiohttp: v1.2.0
Windows 7 Ultimate x64 Build 7601
Note: The reason why I do both 32 and 64 bit installs is because I use both 32 and 64 bit python versions.

i don't think this is related to aiohttp. re-open if you have any actionable


Get-TssDirectoryServiceSyncStatus fails to convert output to Thycotic.PowerShell.DirectoryServices.DomainSyncStatus object.

Verified issue does not already exist?
No
What error did you receive
InvalidArgument: C:\Program Files\WindowsPowerShell\Modules\Thycotic.SecretServer\0.60.9\functions\directory-services\Get-TssDirectoryServiceSyncStatus.ps1:55
Line |
55 |  …             [Thycotic.PowerShell.DirectoryServices.SyncStatus]$restRe …
|                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| Cannot convert value "@{estimatedPercentComplete=0; startDateTime=2/16/2024 5:07:16 PM; endDateTime=2/16/2024
| 5:07:23 PM; nextSynchronizationDateTime=2/16/2024 6:07:23 PM; errorCount=0; domainStatus=System.Object[]}" to
| type "Thycotic.PowerShell.DirectoryServices.SyncStatus". Error: "Cannot convert value "@{domainId=1;
| newUsersCreated=0; newUsersCreatedAsDisabled=0; usersRemovedFromGroups=0; usersWithGroupMembershipChanges=177;
| domainUsersUpdatedSinceLastSynchronization=0; disabledUsers=0; lastLogEntry=Created 0 users.  Updated
| memberships for 177 users.  Removed membership for 0 users.  Disabled 0 users.  0 users were created as
| disabled.  Re-enabled 0 users. }" to type "Thycotic.PowerShell.DirectoryServices.DomainSyncStatus". Error:
| "Cannot convert the "@{domainId=1; newUsersCreated=0; newUsersCreatedAsDisabled=0; usersRemovedFromGroups=0;
| usersWithGroupMembershipChanges=177; domainUsersUpdatedSinceLastSynchronization=0; disabledUsers=0;
| lastLogEntry=Created 0 users.  Updated memberships for 177 users.  Removed membership for 0 users.  Disabled 0
| users.  0 users were created as disabled.  Re-enabled 0 users. }" value of type
| "System.Management.Automation.PSCustomObject" to type "Thycotic.PowerShell.DirectoryServices.DomainSyncStatus".""
Please run the command using -Verbose
VERBOSE: Command invocation: Get-TssDirectoryServiceSyncStatus -TssSession:TssSessionObject -Verbose:True
VERBOSE: Performing the operation GET https://arrow.secretservercloud.com/api/v1/directory-services/synchronization
InvalidArgument: C:\Program Files\WindowsPowerShell\Modules\Thycotic.SecretServer\0.60.9\functions\directory-services\Get-TssDirectoryServiceSyncStatus.ps1:55
Line |
55 |  …             [Thycotic.PowerShell.DirectoryServices.SyncStatus]$restRe …
|                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| Cannot convert value "@{estimatedPercentComplete=0; startDateTime=2/16/2024 5:07:16 PM; endDateTime=2/16/2024
| 5:07:23 PM; nextSynchronizationDateTime=2/16/2024 6:07:23 PM; errorCount=0; domainStatus=System.Object[]}" to
| type "Thycotic.PowerShell.DirectoryServices.SyncStatus". Error: "Cannot convert value "@{domainId=1;
| newUsersCreated=0; newUsersCreatedAsDisabled=0; usersRemovedFromGroups=0; usersWithGroupMembershipChanges=177;
| domainUsersUpdatedSinceLastSynchronization=0; disabledUsers=0; lastLogEntry=Created 0 users.  Updated
| memberships for 177 users.  Removed membership for 0 users.  Disabled 0 users.  0 users were created as
| disabled.  Re-enabled 0 users. }" to type "Thycotic.PowerShell.DirectoryServices.DomainSyncStatus". Error:
| "Cannot convert the "@{domainId=1; newUsersCreated=0; newUsersCreatedAsDisabled=0; usersRemovedFromGroups=0;
| usersWithGroupMembershipChanges=177; domainUsersUpdatedSinceLastSynchronization=0; disabledUsers=0;
| lastLogEntry=Created 0 users.  Updated memberships for 177 users.  Removed membership for 0 users.  Disabled 0
| users.  0 users were created as disabled.  Re-enabled 0 users. }" value of type
| "System.Management.Automation.PSCustomObject" to type "Thycotic.PowerShell.DirectoryServices.DomainSyncStatus".""
Provide a test case or steps to reproduce

Install either Thycotic.SecretServer module version 0.60.9 or 0.61.8 (verified an issue on both, the error is the same)
Run the following commands
Import-Module Thycotic.SecretServer
Get API token for your Admin user through SS portal
Save token in a variable, i.e. $Token = "the pasted token string from SS portal"
$SSsession = New-TssSession -SecretServer  -AccessToken $Token
Get-TssDirectoryServiceSyncStatus -TssSession $SSsession

Expected behavior
For the command to run and return the synchronization status.
What Edition of Secret Server?
Platinum
What version of Secret Server
Secret Server Cloud
What PowerShell host was used when producing this error
PowerShell Core (pwsh)
PowerShell Host Version
Name                           Value

PSVersion                      7.4.1
PSEdition                      Core
GitCommitId                    7.4.1
OS                             Microsoft Windows 10.0.17763
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

@premstad we will take a look at this issue.


Image and Button Tweaks

I added image width and height properties (HTML properties, not CSS), compressed the bathroom sign image and added transitions to the buttons.
Unrelated Changes

Added height: auto to a couple of images that were broken by the change

Resolves: https://trello.com/c/aMzh36nG and https://trello.com/c/SQP7YdDZ

There are issues with the following images:

VIP image is warped on desktop view
VIP image is now too big on mobile view and overflows the screen.
Hero image is stretched too long on mobile view and has warped the picture.

@Jo-Pickering Good catches. I should have checked those a bit more carefully. I figured out what needs changing in DevTools so I'll have another commit in a few minutes.

@Jo-Pickering I fixed them but I just noticed that the header gets stretched horizontally on desktop. The image is about 103 : 100 so could we crop it to 1:1? That will probably make fixing it easier. Also the issue existed before these changes.
Mobile:

Desktop:


Issue and PR templates

Add prototype templates for issues and pull requests.

Fiona looked at this informally.


first pr

 Onboarding pull request
This PR fixes #

Pull Request Test Coverage Report for Build 903477216

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 43.427%

Totals

Change from base Build 901159617:
0.0%

Covered Lines:
26574

Relevant Lines:
55609

💛  - Coveralls

Don't forget to give your PR a descriptive name, and to fill out the description!


 IF YOU DO NOT FOLLOW THE FORMAT OR MAKE A GENERIC TOKEN REQUEST YOUR ISSUE WILL BE DELETED WITHOUT COMMENT
YOUR JUSTLIST MUST FOLLOW THE JSON SPECIFICATION
https://github.com/justswaporg/justlists/blob/main/example.justlists.ts
Checklist

[x] I understand that this is not the place to request a token listing.
[x] I have tested that my JustList is compatible by pasting the URL into the add a list UI at justswap.org.
[x] I understand that filing an issue or adding liquidity does not guarantee addition to the justlists website.

Please provide the following information for your token.
JustList URL must be HTTPS.
JustList URL:
JustList Name: KAMPANAT THUMWONG
Link to the official homepage of the JustList manager:
@JustSwapTeam

Before submission deletes this line: THIS IS NOT A TOKEN LISTING REQUEST FORM. IF YOU DO NOT FOLLOW THE FORMAT OR MAKE A GENERIC TOKEN REQUEST YOUR ISSUE WILL BE DELETED WITHOUT COMMENT
YOUR JUSTLIST MUST FOLLOW THE JSON SPECIFICATION
https://github.com/justswaporg/justlists/blob/main/example.justlists.ts
Checklist

[x]  I understand that this is not the place to request a token listing.
[x]  I have tested that my JustList is compatible by pasting the URL into the add a list UI at justswap.org.
[x]  I understand that filing an issue or adding liquidity does not guarantee addition to the justlists website.

Please provide the following information for your token. JustList URL must be HTTPS.
JustList URL: JustList Name: KAMPANAT THUMWONG Link to the official homepage of the JustList manager: @JustSwapTeam

@Kongpcmail


chore: Adding user permissions in the response of get actions in view mode

Fixes #19055
(backend fix. frontend changes shall follow)

/ok-to-test sha=ba7c4bf

@trishaanand Should both backend & frontend changes be made in this same PR? Will that help us test this fix out more reliably?


nutsdb v0.12.0 does not support 386/arm architectures

Describe the bug
When building (cross-platform) using nutsdb v0.12.0, the build fails due to math.MaxUint32 introduced in https://github.com/nutsdb/nutsdb/pull/286/files -> https://github.com/elliotchenzichang/nutsdb/blob/master/tx.go#L182
To Reproduce
pull the 0.12.0 version
run go build targetting an ARM or 386 architecture
GOOS=linux GOARCH=arm GOARM=5 CGO_ENABLED=0 go build

or
GOOS=linux GOARCH=386 CGO_ENABLED=0 go build

fails with
.\tx.go:182:29: constant<PHONE_NUMBER> overflows int

Expected behavior
The code still compiles for GOARC 386/ARM
If applicable, add screenshots to help explain your problem.
please complete the following information :

OS: windows 11/ubuntu 20
NutsDB Version 0.12.0

Additional context
Should be fixable by either replacing
if len(entry.Meta.Bucket) >= math.MaxUint32 || len(entry.Key) >= math.MaxUint32 || len(entry.Value) >= math.MaxUint32 {
  return ErrDataSizeExceed
}

with
if len(entry.Meta.Bucket) >= math.MaxInt32|| len(entry.Key) >= math.MaxInt32|| len(entry.Value) >= math.MaxInt32{
  return ErrDataSizeExceed
}

side-effect -> reduces to max size from<PHONE_NUMBER> to<PHONE_NUMBER>
Or by introducing a const.go file with build directive for 386/arm or not
Happy to do a PR for any of those, as this is blocking my project ;)

@hivenet-philippe ok. please give me a PR to fix it

Seems we already fixed it. So I closed this issue.


Update top-right-bottom-left.mdx

Summary
Fixed numbering in the code to match the picture

@CurtisHumphrey thanks!


add-permanent-notation to function-scope

Deploy preview for js-primer ready!
Built with commit 94fcdbbaf31db56a154d4276fb6d625a4e4dada7
https://deploy-preview-403--js-primer.netlify.com


Debug should be in dependencies because dev dependencies of dependencies...

... (transative dev deps) aren't installed when running npm install.

Version 1.0.1 published on NPM.

Boom! Thanks @Prevole!


The order of multiple Heredocs might be wrong in syntax

According to the raku docs, this code should work
my ($first, $second) = qq:to/END1/, qq:to/END2/;
  FIRST
  MULTILINE
  STRING
  END1
   SECOND
   MULTILINE
   STRING
   END2
say $first;  # OUTPUT: «FIRST␤MULTILINE␤STRING␤»
say $second; # OUTPUT: «SECOND␤MULTILINE␤STRING␤»

while the syntax could only recognize (which could not compile)
my ($first, $second) = qq:to/END1/, qq:to/END2/;
   SECOND
   MULTILINE
   STRING
   END2
  FIRST
  MULTILINE
  STRING
  END1
say $first;  # OUTPUT: «FIRST␤MULTILINE␤STRING␤»
say $second; # OUTPUT: «SECOND␤MULTILINE␤STRING␤»

The interesting thing is that the Github seems only recognize wrong syntax as well

Hi @clouds56! Thanks for using the extension, I hope it's working well for you. For syntax highlighting, I mostly just copied the highlighting from here https://github.com/Raku/atom-language-perl6 . Looks like this issue is fairly similar: https://github.com/Raku/atom-language-perl6/issues/63 . Although the development in that repo is not very active, I think it's still good to centralize issues there.
Github has the same issue because it also uses that repo https://github.com/github/linguist/blob/master/vendor/README.md


Extract to folder

How do I extract to a folder not a file.

Okay I mananage to Extract to a directory however all text seems to be wrongly encoded. Any solution

Okay I manage to Extract to a directory however all text seems to be wrongly encoded. Any solution

Delaley, the library doesn't do anything with the content, either text or binary. If you have an encoding problem, it may be related to the receiving text stream object/class.


sqrt segfaults for some input

The following code example causes a segmentation fault after a few iterations
auto random = std::mt19937_64{std::random_device{}()};
auto number = std::uniform_real_distribution<float>{};
for(int i = 0; i < 10'000'000; ++i)
	smath::sqrt( number(random) );

It seems that the Babylonian algorithm goes infinite for some specific numbers, because it can never satisfy the is_close condition.
Using a condition like this instead seems to fix the problem,
std::abs(a - b) <= std::numeric_limits<T>::epsilon() * std::abs(a + b);

but I have no idea why or how, it's just something I found here.

Interesting, I'll try to have a look tonight and to fix it, thanks for reporting.

Sure, here are a few literals that do it for me.
4.916330874e-01F
3.804553151e-01F
4.505589902e-01F
3.162864149e-01F
4.889709353e-01F

Apparently I've got more issues of tests that don't compile anymore with the more recent compilers, I'll have to look at this further this week.

I added your tests, changed the formula to the one from cppreference and everything seems to compile. Thanks for the report :)
Too many things seem broken with new compilers though (I'm using GCC 9.2 and exp doesn't work), I guess that I will need to complete the continuous integration and open bug reports accordingly.


Consider additional documentation for setDimensionFilter.

Please consider adding an example for setDimensionFilter
I found a user on Stack overflow who is having issues.  I was unable to help them as i can find no information on how to properly use this method
Lnks to How to filter by dimension using Google Analytics Data API (GA4) Java client library?

Linda, thank you for flagging this. We are actually working on Java samples for the Data API v1 beta as we speak, will respond to the SO question asap.

Thank you @ikuleshov im sure the author will be happy for any assistance you can give.

Yes, thanks a lot for your help!

I second this request.

@laserpez  if they still haven't documented it let me know and i will do it myself.

@laserpez if they still haven't documented it let me know and i will do it myself.

I see that the issue is still open and I'm not able to find documentation regarding filtering other than the code in the sample. Maybe I'm not looking in the right place?


Add CRI-O support

This PR allows the runtime to be used by CRI-O.

Coverage decreased (-1.2%) to 33.15% when pulling a4039d49ad8e6a815a88030c1907479f480016b1 on sboeuf/crio_support into 42ae23405a7420e8b8990ca4ed28b93cfc9ddeac on master.

Coverage decreased (-1.2%) to 33.15% when pulling 25bd236700195bf81a5a3e063ddfbf970d072651 on sboeuf/crio_support into 42ae23405a7420e8b8990ca4ed28b93cfc9ddeac on master.

Coverage decreased (-1.2%) to 33.15% when pulling 25bd236700195bf81a5a3e063ddfbf970d072651 on sboeuf/crio_support into 42ae23405a7420e8b8990ca4ed28b93cfc9ddeac on master.

Coverage decreased (-1.4%) to 32.936% when pulling f2014dd5e286418e49a6e684efff1e07dc931416 on sboeuf/crio_support into 42ae23405a7420e8b8990ca4ed28b93cfc9ddeac on master.

Coverage decreased (-1.4%) to 32.936% when pulling f2014dd5e286418e49a6e684efff1e07dc931416 on sboeuf/crio_support into 42ae23405a7420e8b8990ca4ed28b93cfc9ddeac on master.

Coverage decreased (-1.5%) to 32.794% when pulling ad2247f305e07da7f9fe6d50ab64b1de193cd498 on sboeuf/crio_support into 42ae23405a7420e8b8990ca4ed28b93cfc9ddeac on master.

Coverage decreased (-1.7%) to 32.653% when pulling 4ed00b70358606bc5e961743286abfce5d06b26f on sboeuf/crio_support into 42ae23405a7420e8b8990ca4ed28b93cfc9ddeac on master.

Looks good, but there are a lot of new function here, but no new tests to support them.

@jodh-intel Don't worry, I want to get CRI-O working before I implement the corresponding unit tests ;)

Coverage decreased (-1.7%) to 32.967% when pulling bf24541c0ffcaeac47f85b6664337dc4099816a3 on sboeuf/crio_support into 94749ee99165fd367e899d6ccb754f81e7d12e5e on master.

Don't merge until https://github.com/containers/virtcontainers/pull/268 is merged.

Coverage decreased (-0.5%) to 34.178% when pulling a9421f2c81d86ee5c7a337933330187e3df5e0c9 on sboeuf/crio_support into 94749ee99165fd367e899d6ccb754f81e7d12e5e on master.

@jodh-intel PR updated.

Coverage decreased (-0.4%) to 34.24% when pulling ad58c67deb856665c0a9d654cda748c6a27be696 on sboeuf/crio_support into 94749ee99165fd367e899d6ccb754f81e7d12e5e on master.

Coverage decreased (-0.3%) to 37.988% when pulling c4566a78c007612ac83fb9ea646fe6e4a39a4c61 on sboeuf/crio_support into ae3bef160b97c2276e8234021134ca4fcf43f056 on master.

Coverage decreased (-0.3%) to 37.988% when pulling c4566a78c007612ac83fb9ea646fe6e4a39a4c61 on sboeuf/crio_support into ae3bef160b97c2276e8234021134ca4fcf43f056 on master.

Coverage decreased (-0.3%) to 37.988% when pulling 4299281a57b27fc367621477d10477325436cb08 on sboeuf/crio_support into 6fb3ff35fed039787090878ccf4fc51b3d2ae008 on master.

Coverage decreased (-1.1%) to 37.115% when pulling f33a22205e32b966c31bd75e39b2eab58d827982 on sboeuf/crio_support into 8e2f96e4def6fa273fe661c15b2c64f6952123d9 on master.

Coverage decreased (-1.1%) to 37.115% when pulling 81b4f3e2a9f8191560658ec090ef52b858a8c872 on sboeuf/crio_support into 8e2f96e4def6fa273fe661c15b2c64f6952123d9 on master.

Coverage decreased (-1.1%) to 37.115% when pulling 8f1760cf1a7efcafc7bbbc4ed00f3c92e2bf9d49 on sboeuf/crio_support into 8e2f96e4def6fa273fe661c15b2c64f6952123d9 on master.

@sameo @jodh-intel we now have the virtcontainers part merged. Let's merge this one ;)

Coverage decreased (-1.1%) to 37.115% when pulling c8434c15298fcdd3598f17e5367277d7f2ef1ae9 on sboeuf/crio_support into 8e2f96e4def6fa273fe661c15b2c64f6952123d9 on master.

LGTM

I'd like to get @jodh-intel review though.

Coverage decreased (-1.2%) to 37.964% when pulling a84876053962e52101b0c1ea6ee409d71e8cd464 on sboeuf/crio_support into 66b54638c5125167fe852dce4a45c2a1d01c9e27 on master.

@jodh-intel I have no other testing in clearcontainers/tests. I know I have modified the way create/delete/... behave but we had no tests before that, and I still don't have tests for that.

We have the Semaphore tests (#168) which give us a level of confidence that we haven't broken basic container support. Are there any further tests that can be added there? Otherwise, how are we going to know that CRI-O support is still working?

Otherwise, how are we going to know that CRI-O support is still working?
CRI-O is not working at all without this PR :)

@sboeuf - do you have an issue assigned to add CRI-O integration tests?
In my view, we should have more tests on this PR. But if we must consider landing it like this, I think it is only reasonable that you get to fix any "CRI-O bitrot" down the line ;-)

Coverage decreased (-1.2%) to 37.964% when pulling 59baeac26507ac17869248124ea99521eda040de on sboeuf/crio_support into 66b54638c5125167fe852dce4a45c2a1d01c9e27 on master.

Coverage decreased (-1.2%) to 37.964% when pulling 9226fe7e0020751e9b61ed285cae507764ad5fe8 on sboeuf/crio_support into 66b54638c5125167fe852dce4a45c2a1d01c9e27 on master.

Coverage decreased (-1.2%) to 37.964% when pulling 2004e76a1fc97587feafcb67866f5e2b14dea16e on sboeuf/crio_support into 66b54638c5125167fe852dce4a45c2a1d01c9e27 on master.

Coverage decreased (-1.2%) to 37.964% when pulling 9c962db3ea983df268b1962822e6a60251beda80 on sboeuf/crio_support into 66b54638c5125167fe852dce4a45c2a1d01c9e27 on master.

Coverage decreased (-1.2%) to 37.964% when pulling 246695664ff99246ff787d7cd4ece871a5ae0963 on sboeuf/crio_support into 66b54638c5125167fe852dce4a45c2a1d01c9e27 on master.

Coverage decreased (-1.2%) to 37.964% when pulling 867da90cef1dc013abb5c82052fa9f6832d8968b on sboeuf/crio_support into 66b54638c5125167fe852dce4a45c2a1d01c9e27 on master.

Coverage decreased (-1.2%) to 37.964% when pulling 77967f6a23c939394f7291dae37cc69b2d4c804e on sboeuf/crio_support into 66b54638c5125167fe852dce4a45c2a1d01c9e27 on master.

Coverage decreased (-1.2%) to 37.964% when pulling cf5d9fc36fb70b73c04058be7467577adf2f95d2 on sboeuf/crio_support into 66b54638c5125167fe852dce4a45c2a1d01c9e27 on master.

Coverage decreased (-1.2%) to 37.964% when pulling 7010a49173463571f2e8ad269b57717040ebd1a0 on sboeuf/crio_support into 66b54638c5125167fe852dce4a45c2a1d01c9e27 on master.

Coverage decreased (-1.2%) to 37.964% when pulling bc4edc1f2f26923ee309db79483203e4409c79e8 on sboeuf/crio_support into 66b54638c5125167fe852dce4a45c2a1d01c9e27 on master.

Coverage decreased (-1.2%) to 37.964% when pulling 69b605ccfb9bbd87df0ed8f0045d7fdbe5739e99 on sboeuf/crio_support into 66b54638c5125167fe852dce4a45c2a1d01c9e27 on master.

Coverage decreased (-1.2%) to 37.964% when pulling 69b605ccfb9bbd87df0ed8f0045d7fdbe5739e99 on sboeuf/crio_support into 66b54638c5125167fe852dce4a45c2a1d01c9e27 on master.

@jodh-intel I have updated the PR by adding Semaphore CI tests for CRI-O.

Coverage decreased (-1.2%) to 37.964% when pulling d6c8e46d48be0ad0b8035b2ecad1cb799a8e34d9 on sboeuf/crio_support into 66b54638c5125167fe852dce4a45c2a1d01c9e27 on master.

@sboeuf - excellent, thanks! I appreciate it's all extra work, but I do think this was an essential part of this PR.
lgtm.

@sboeuf why does the CRI-O tests were added here? These tests should have been added in clearcontainers/tests repository.

@chavafg I know those tests should go to clearcontainers/tests, but we wanted this PR to be able to test CRI-O right away, and that was the only way.
But we need those tests properly ported to clearcontainers/tests, I agree.

+1 to moving them to the tests repo now, but yes, we had to "bootstrap" these tests into runtime initially.


Add more possible sources to second sentence

Based on code - list of supported azure compute services should be extended with arc and azure service fabric
private static ManagedIdentitySource SelectManagedIdentitySource(ManagedIdentityClientOptions options)
    {
        return
            ServiceFabricManagedIdentitySource.TryCreate(options) ??
            AppServiceV2019ManagedIdentitySource.TryCreate(options) ??
            AppServiceV2017ManagedIdentitySource.TryCreate(options) ??
            CloudShellManagedIdentitySource.TryCreate(options) ??
            AzureArcManagedIdentitySource.TryCreate(options) ??
            TokenExchangeManagedIdentitySource.TryCreate(options) ??
            new ImdsManagedIdentitySource(options);
    }

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

ID: 42c826d6-3da7-37f3-80a4-a2bdbf3be472
Version Independent ID: 1b1ff6a5-a8ad-8599-9644-66caad571a8a
Content: ManagedIdentityCredential Class (Azure.Identity) - Azure for .NET Developers
Content Source: xml/Azure.Identity/ManagedIdentityCredential.xml
Service: azure
GitHub Login: @rloutlaw
Microsoft Alias: routlaw

Thank you for your feedback.  Tagging and routing to the team member best able to assist.


Add a code coverage script/build

Need a script or separate Jenkins build to generate code coverage reports

This has been implemented


Using blink as primitive

I think making a LED blink is the 1st real program step in physical programming and having a command that does it is over-simplfying things too far.
Simplification should be used for complicated things like driving Neopixels/H-bridge motors etc
I think its also bit  debatable whether to use Led() straight out of the box just on simple things
I'd prefer a
LEDA = gpio17
while true:
LedA(On)
Wait(1)
LedA(Off)
wait(1)
type approach

The first example in recipes in the docs:

Turn an LED on and off repeatedly:

from gpiozero import LED
from time import sleep

red = LED(2)

while True:
    red.on()
    sleep(1)
    red.off()
    sleep(1)

Alternatively:

from gpiozero import LED

red = LED(2)

red.blink()

So as you can see, I completely agree with you that the while loop version is a great starting point introducing the concepts.
However, blink gives you the ability to blink an LED in the background, which is a very handy feature. It means you can set it blinking, then do some other stuff without being held up by your blinking loop.
GPIO Zero isn't meant to dumb things down, just make it easier to get going. It's about being able to tell it what you want to do, not how.

Well - I've never needed a threaded blinking LED before in a project myself  :)
But why have a LED class thingy - surely THAT is dumbing down :)
Surely the uses puts a LED on a pin - then says they want to control it.
Are you going to have a Bulb class, a solenoid class, anything else that goes on and off class ? :)
having a LED class makes sense for AddOn boards where the user doesn't know what pin the red led is connected to but its not right for plain pin control
IMO :)

GPIO Zero is a library for everyday components. I started by implementing everything in the CamJam kits. I'll implement anything I think is useful. Anything not covered by these classes, you can use the generic InputDevice and OutputDevice classes, or just fall back to the brilliant RPi.GPIO library.
Class interfaces give context to code. You create an LED object, you expect to be able to turn it on, turn it off, etc. You create a Dog object, you expect it to bark.

Sure we could have a Bulb class. It's definition will look like this:
Bulb = LED

Funnily enough, that's more or less what the LED and Buzzer classes look like now (they're both empty subclasses of DigitalOutputDevice bar the explanatory doc-string).

But GPIOZero is a software interface to hardware. :)

Well, I am pretty much a pure software person, so I can't really argue there (though I'm not sure how a hardware perspective would change my view)! Still, I would object to removing stuff on the grounds given:

You've never needed a threaded blinking LED on a project before. That's fine, but it certainly doesn't mean that no-one's ever needed (or ever will need) a threaded blinking LED in a project (I can think of several cases off the top of my head: e.g. a police siren demo where red and blue LEDs flash while we play a nee-naw sound, and possibly drive towards something).

It's dumbing stuff down too far. As Ben's pointed out, just because something's there doesn't mean people have to use it (e.g. in lessons one can leave out blink until later). For that matter, from my experience with picamera and its users, just because something's there (and thoroughly documented) doesn't mean anybody actually notices (one could make similar arguments for capture_continuous and capture_sequence in picamera but it's rare I seem them used in practice - most people just use sleep and capture for stuff like timelapses).
I'd also argue that the vast majority of beginners have no clue how to handle background threads, and it's probably not something we want to get into (in lesson situations) until much later. Yet the functionality is (or may be) useful in certain projects, and thus it's beneficial to expose a simple (limited) API to provide the functionality.

It'll lead to a proliferation of unnecessary classes. Again, I can think of a case where having otherwise redundant class aliases does serve a purpose. Consider the case of people using non-descriptive variable names in their script. Can you tell from the following script what's connected to pin 17?
foo = DigitalOutputDevice(17)

We can tell it's an output device (so an LED, or a buzzer maybe?) but the following script is blindingly obvious:
foo = LED(17)

So by encouraging use of these aliases we encourage nice clear code even in the event that people decide to use non-descriptive identifiers (it doesn't force people to use them instead of DigitalOutputDevice, but who wants to type all that?).

There is an argument to be made that with all those class aliases floating around doing something like from gpiozero import * pollutes the namespace excessively. But then this is only typical practice on the command line and is generally discouraged in scripts (in other words, I've got little sympathy for anyone that gets clobbered by using import *)

In other words, I can't say I'm convinced at the moment :)


RNIap.getSubscriptions(itemSkus) is not working

Please use Discussion board if you want get some help out of it. Please report issue if there is a bug.

Version of react-native-iap
8.0.5
Version of react-native
0.67.3
Platforms you faced the error (IOS or Android or both?)
Android
RNIap.getSubscriptions(itemSkus) is not working, the RNIap.initConnection() connected but not working subscriptions, I did all the steps base on documentation, but the response from getSubscriptions return empty array [], any idea?
Tested environment (Emulator? Real Device?)
Real Devices
Steps to reproduce the behavior

Hi @GezimVeliu,
I was facing the same issue that you.
Maybe these tips will help you and other developers.
1 - If you are publishing / enabling subscription the first time:

Try to use internal test channel (it will publish your app faster than close channel (alpha))

2 - If you are using close channel (Alpha)

It may take 24h to update google play server around the world.

3 - Check your products / subscriptions ids

Go to Google Play console, open subscriptions and check if the ids are the same that you are trying to fetch.

4 - Check if you are a user tester

Inside Internal test / closed test, you need to create a group of testers.
Add your user (it needs to be the same that you are using in your device)
After your app be published, look for the link to accept the tester invite ex: https://play.google.com/apps/internaltest/123456789

5 - Add your user in License testing

it allows you to use a google play sandbox to buy items and subscriptions.

If you follow these steps, I believe  you will get the subscriptions items from GooglePlay.
Good luck. :)

Thank you for the details @romulojjunior


Granular auto-wiring

Like haskell-flake: https://flake.parts/options/haskell-flake#opt-perSystem.haskellProjects.name.autoWire
But for rust-flake, so we can do:
autoWire = ["clippy" "doc"]; # All but the package itself

Ref: https://github.com/hercules-ci/flake-parts/issues/114

After doing this, make sure that multi-crate detection automatically wires clippy and doc


fix(REVERT): remove zone internal stack frames in error.stack (#632)

This feature was reverted because it was causing a performance regression.
The setup of all of the stack traces added about 20-25ms to the total
time of the Zone initialization. This was a bit more than 50% of overall
time zone needed to initialize. While this is a useful feature, the
performance cost does not justify its cost.

@JiaLiPassion FYI

@mhevery ,
I have following proposal.

should we make it as a helper method like error.getSimpleStack(), and when the method was first called, the detect procedure will be run once.
Or we make it a stand alone js just like longstacktrace, so user can decide to load it or not.

what do you think?

Yes we should brainstorm as to what is the best way to provide this functionality.


[IDEA] test webhook on GitHub & Discord

Description of the idea
Test
Add (multiple) screenshot links (if applicable)
No response
Add any other context about the idea here
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

It's working


Could not find multi_json-1.12.1 in any of the sources (Bundler::GemNotFound)

$ bundle env
Environment
Bundler       1.16.1
  Platforms   ruby, x64-mingw32
Ruby          2.2.6p396 (2016-11-15 revision 56800) [x64-mingw32]
  Full Path   C:/Ruby22-x64/bin/ruby.exe
  Config Dir  C:/ProgramData
RubyGems      <IP_ADDRESS>
  Gem Home    C:/Ruby22-x64/lib/ruby/gems/2.2.0
  Gem Path    C:/Users/kgande/.gem/ruby/2.2.0;C:/Ruby22-x64/lib/ruby/gems/2.2.0
  User Path   C:/Users/kgande/.gem/ruby/2.2.0
  Bin Dir     C:/Ruby22-x64/bin
Tools
  Git         2.14.1.windows.1
  RVM         not installed
  rbenv       not installed
  chruby      not installed

Bundler Build Metadata
Built At          2017-12-21
Git SHA           0034ef341
Released Version  true

 [exec] C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/bundler-1.16.1/lib/bundler/spec_set.rb:88:in `block in materialize': Could not find multi_json-1.12.1 in any of the sources (Bundler::GemNotFound)
     [exec]     from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/bundler-1.16.1/lib/bundler/spec_set.rb:82:in `map!'
     [exec]     from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/bundler-1.16.1/lib/bundler/spec_set.rb:82:in `materialize'
     [exec]     from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/bundler-1.16.1/lib/bundler/definition.rb:170:in `specs'
     [exec]     from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/bundler-1.16.1/lib/bundler/definition.rb:237:in `specs_for'
     [exec]     from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/bundler-1.16.1/lib/bundler/definition.rb:226:in `requested_specs'
     [exec]     from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/bundler-1.16.1/lib/bundler/runtime.rb:108:in `block in definition_method'
     [exec]     from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/bundler-1.16.1/lib/bundler/runtime.rb:20:in `setup'
     [exec]     from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/bundler-1.16.1/lib/bundler.rb:107:in `setup'
     [exec]     from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/bundler-1.16.1/lib/bundler/setup.rb:20:in `<top (required)>'
     [exec]     from C:/Ruby22-x64/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require'
     [exec]     from C:/Ruby22-x64/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require'
     [exec] Result: 6

Can you please share the whole output from bundle env, including your Gemfile? Thanks!

bundler-1.16.1.zip
prepareUI:
[echo] Preparing UIResource.resource...
[exec] parameters: + -optimizeUI
[exec] Creating UIPath...
[exec] mnadmin mnapp mncatalog mnconfig mnconfigadmin mnquote uifw
[exec] Generating CSS using production (optimized) mode...
[exec] (node:4208) [DEP0022] DeprecationWarning: os.tmpDir() is deprecated. Use os.tmpdir() instead.Running "compass:clean" (compass) task
[exec]
[exec] Warning: ↑ Use --force to continue.
[exec]
[exec] Aborted due to warnings.
[exec] C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/bundler-1.16.1/lib/bundler/spec_set.rb:88:in block in materialize': Could not find multi_json-1.12.1 in any of the sources (Bundler::GemNotFound)      [exec]     from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/bundler-1.16.1/lib/bundler/spec_set.rb:82:in map!'
[exec]     from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/bundler-1.16.1/lib/bundler/spec_set.rb:82:in materialize'      [exec]     from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/bundler-1.16.1/lib/bundler/definition.rb:170:in specs'
[exec]     from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/bundler-1.16.1/lib/bundler/definition.rb:237:in specs_for'      [exec]     from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/bundler-1.16.1/lib/bundler/definition.rb:226:in requested_specs'
[exec]     from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/bundler-1.16.1/lib/bundler/runtime.rb:108:in block in definition_method'      [exec]     from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/bundler-1.16.1/lib/bundler/runtime.rb:20:in setup'
[exec]     from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/bundler-1.16.1/lib/bundler.rb:107:in setup'      [exec]     from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/bundler-1.16.1/lib/bundler/setup.rb:20:in <top (required)>'
[exec]     from C:/Ruby22-x64/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in require'      [exec]     from C:/Ruby22-x64/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in require'
[exec] Result: 6
[echo] Preparing UIResource.resource...Done.


Add addressee layer name in the refine list like the other lists

Notification lists has addressee layer name, it will great if we can do the same for refine list, if there are more than one addressee layer, and more than one refine list, I think it will be helpful for the users.
very low priority for June release

@aparveen The way refine is implemented it is unique and only ever has one set even if you add/remove from multiple layers.

@aparveen The way refine is implemented it is unique and only ever has one set even if you add/remove from multiple layers. So you can still manage selections across all sets.
oh ok got it, so we don't need to change string for this

@aparveen correct...seems like we should go back

@aparveen correct...seems like we should go back

@jmhauck wondering if we need to mention anything about selecting input layer, it will be in cases where multiple input layers are available, in most cases it won't so not sure about this

@aparveen at the bare min we should probably update this to say something about "lists" rather than selection sets since this is the only spot that we say "selection sets". We only show the layer dropdown if they have made selections against multiple layers so if we do we should be careful how we word it.

This is what they put in for the main select page from their doc writer yesterday:

Select features from the input layer to add to your list. Draw with sketch tools, specify a search distance, and use features from another layer to select overlapping features.


Makefile: set VERSION to 0.2.0

Would it be better to bump to 0.3?

Closing this one as it's stale.


some update for postgres driver validation

-added pgsql in driver validation
-update gitignore

please check and approve.. i need this urgently

If you need this urgently I recommend you to just make use of your fork (which can be used immediately) instead of waiting a review + merge + release.

@wouterj the failure of Travis is unrelated (it's due to PHPUnit 6.x)

Thanks for discovering this bug! I have absolutely no idea why I used postgres in this bundle... (it was probably used in older Laravel versions).
I discovered sql server is also wrong. So I took your commit, added the sqlsrv name and triggered a deprecation warning for the old names. That resulted in a new PR: https://github.com/wouterj/WouterJEloquentBundle/pull/45


Browser Login

Can I use the session files to login to Instagram with the help of EditThisCookie chrome extension?
I am able to figure out some of the values required by the extension in the session file. If it's possible plz let me know. Thanks

I figured. It's possible.

@Deleora
Can you please share your findings? Trying to create a session file but the only thing I find here involves running scripts and that's sadly out of my league.

@Deleora
Can you please share your findings? Trying to create a session file but the only thing I find here involves running scripts and that's sadly out of my league.

@psonnosp Creating a session file does not involve any script (I mean you can use script but it isn't mandatory)
If you have Instaloader installed on your system simply run the following command on your terminal
instaloader --login YOUR-USERNAME
Then it'll prompt you to enter your password (which you won't be able to see on the screen), then hit Enter and your session file would be created in the default folder. You may also be asked to enter 2FA code in case you have it enabled.
If you need more help feel free to ask.
Cheers!

@psonnosp Creating a session file does not involve any script (I mean you can use script but it isn't mandatory)
If you have Instaloader installed on your system simply run the following command on your terminal
instaloader --login YOUR-USERNAME
Then it'll prompt you to enter your password (which you won't be able to see on the screen), then hit Enter and your session file would be created in the default folder. You may also be asked to enter 2FA code in case you have it enabled.
If you need more help feel free to ask.
Cheers!


Tasks - LMI Final Project

[ ] Task 1: D-Stability with polytopic uncertainties

[x] Choosing a linear state space model;
[x] Specifying performance requirements for the closed loop system;
[x] Defining a D-Stability region for the closed-loop poles;
[x] Defining the corresponding LMI problem;
[x] Defining parametric polytopic uncertainties;
[x] Including state-feedback integral action by finding the augmented space state model;
[ ] Verifying reference tracking and disturbance rejection for different polytope points.

[ ] Task 2: Robust control

[ ] Including the LMI conditions for the mixed H2-Hinf Control

It was not needed integral action since this project had no reference tracking.

Class finished


HotChocolate v13.7.0+ support

Due to a breaking change to the public API, we cannot support newer versions of HotChocolate until their replacement API (currently work in progress) is complete.

Right, noticed we are getting this exception after upgrading to Hotchocolate 13.7, hopefully a fix will come out soon, thanks
System.TypeLoadException: Method 'OnBeforeCreateSchema' on type 'ApolloGraphQL.HotChocolate.Federation.FederationTypeInterceptor' from assembly 'ApolloGraphQL.HotChocolate.Federation, Version=<IP_ADDRESS>, Culture=neutral, Publi
cKeyToken=null' is overriding a method that is not visible from that assembly.
at HotChocolate.ApolloFederationSchemaBuilderExtensionsV2.AddApolloFederationV2Definitions(ISchemaBuilder builder, FederationVersion version)
at HotChocolate.ApolloFederationSchemaBuilderExtensionsV2.AddApolloFederationV2(ISchemaBuilder builder, FederatedSchema schema)
at Microsoft.Extensions.DependencyInjection.ApolloFederationRequestExecutorBuilderExtensionsV2.<>c__DisplayClass1_0.b__0(ISchemaBuilder s)
at Microsoft.Extensions.DependencyInjection.RequestExecutorBuilderExtensions.<>c__DisplayClass0_0.b__1(ConfigurationContext ctx, IServiceProvider _)
at HotChocolate.Execution.RequestExecutorResolver.OnConfigureSchemaBuilderAsync(ConfigurationContext context, IServiceProvider schemaServices, RequestExecutorSetup setup, CancellationToken cancellationToken)
at HotChocolate.Execution.RequestExecutorResolver.CreateSchemaAsync(ConfigurationContext context, RequestExecutorSetup setup, RequestExecutorOptions executorOptions, IServiceProvider schemaServices, TypeModuleChangeMonit
or typeModuleChangeMonitor, CancellationToken cancellationToken)


Cant download it

Starting Install...
Creating required directories...
✅ Directory exists: C:\Users\Desktop\AppData\Roaming\BetterDiscord
✅ Directory exists: C:\Users\Desktop\AppData\Roaming\BetterDiscord\data
✅ Directory exists: C:\Users\Desktop\AppData\Roaming\BetterDiscord\themes
✅ Directory exists: C:\Users\Desktop\AppData\Roaming\BetterDiscord\plugins
✅ Directories created
Downloading asar file
❌ Failed to download package https://api.github.com/repos/rauenzi/BetterDiscordApp/releases
❌ Cannot read property 'assets' of undefined
The install seems to have failed. If this problem is recurring, join our discord community for support. https://discord.gg/0Tmfo5ZbORCRqbAd
When i try to download bd, that happens. What should i do?

Starting Install...
Creating required directories...
✅ Directory exists: C:\Users\maxmo\AppData\Roaming\BetterDiscord
✅ Directory exists: C:\Users\maxmo\AppData\Roaming\BetterDiscord\data
✅ Directory exists: C:\Users\maxmo\AppData\Roaming\BetterDiscord\themes
✅ Directory exists: C:\Users\maxmo\AppData\Roaming\BetterDiscord\plugins
✅ Directories created
Downloading asar file
✅ Package downloaded
Injecting shims...
Injecting into: C:\Users\maxmo\AppData\Local\Discord\app-1.0.9003\resources
✅ Injection successful
✅ Shims injected
Restarting Discord...


Upgrade ancient kubebuilder envtest tools for CRD v1 support.

I think this may need to merge before #1395 as I believe the CI system is using the build-image Dockerfile from master, not the PR.
/assign  @joelddiaz
/cc @suhanime

Good catch, updated.

/lgtm


UpdatePaymentStatusAsync expects wrong HTTP status code

Hi there!
Thank you for the great work on the client, it works without hassle so far. But now I do run into a problem...
When I update a payment status through the IBricklinkClient.UpdatePaymentStatusAsync method, I get a BricklinkHttpErrorException telling me that status code 200 was expected, but 204 was received.
I checked the source code and I found that the method is using the PutEnsureNoResponseDataAsync extension method, which in turn states that it expects the 200 status code.
I'm no expert in the Bricklink API and I'm not sure there are any endpoints that respond with a 200 for a PUT request. I can't change the expected code to 204 without knowing this, otherwise I would have submitted a PR.
Hope you can help!

Heyho,
thanks for reporting this issue.
There are 3 endpoints the PutEnsureNoResponseDataAsync is used for:

UpdateOrderStatusAsync
UpdatePaymentStatusAsync
SendDriveThruAsync

Do you have the possibility to check whether they all return 204? Currently I don't have access to active orders.
I remember that the API had some inconsistencies when I wrote this lib. It might be that some endpoints return 200 while others return 204.
If all (3) endpoints return 204 then the expectedCode can simply be replaced. Otherwise the expectedCode must be passed to the PutEnsureNoResponseDataAsync.
As a rapid workaround you can do the following:
        try
        {
            await client.UpdatePaymentStatusAsync(orderId, status);
        }
        catch (BricklinkHttpErrorException e)
        {
            if (e.ReceivedCode != 204)
            {
                throw e;
            }
        }


Revert "Fix panic when decoding"

Reverts Nullus157/async-compression#299

Took another look , I think the original impl was alright, it might be a decoder impl problem.


Use ConnectAsync for net472

#if v472 is never true and caused ConnectAsync not to be used on net472.
See how VS highlights that with net472 selected, the else part is used.

The correct preprocessor directive would be #if NET472.
I also took the liberty to rearrange this a bit as most of the code is identical, except net462 should use BeginConnect and non-netstandard should also catch ObjectDisposedException.
The GitHub diff might not be the easiest way to look at this.
Fixup to #1056

Well well, step by step one reaches maximum opt  :-)
I patched the diff and it certainly looks a real lot better that way.
Thanks for finding my "v472" blunder, funny that no-one discovered that earlier.
Looks like this now:
		private async Task<bool> ConnectAsyncHelper(IPAddress ipad, int port, CancellationToken token) {
			try {
				using (var timeoutSrc = CancellationTokenSource.CreateLinkedTokenSource(token)) {
					timeoutSrc.CancelAfter(ConnectTimeout);
#if NET462
					var connectResult = m_socket.BeginConnect(ipad, port, null, null);
					await EnableCancellation(Task.Factory.FromAsync(connectResult, m_socket.EndConnect), timeoutSrc.Token, () => DisposeSocket());
#else
					await EnableCancellation(m_socket.ConnectAsync(ipad, port), timeoutSrc.Token, () => DisposeSocket());
#endif
				}
			}
#if !NETSTANDARD
			catch (ObjectDisposedException) {
				throw new TimeoutException("Timed out trying to connect!");
			}
#endif
			catch (SocketException ex) when (ex.SocketErrorCode is SocketError.OperationAborted or SocketError.TimedOut) {
				throw new TimeoutException("Timed out trying to connect!");
			}

			return m_socket.Connected;
		}


Add install-sqltoolsservice to GI build pipeline

@anthonydresser in the build pipelines this step usually takes less than 20 seconds.  Why do you expect it will cause more impact here.  The value of having it as part of the CI is prevent build breaks related to changes here.  I'm open to other options to avoid this type of breaks, but I am not how running a whole different build is lower impact.

It looks like it only took a few seconds. I know we've been having issues with reliability in this area. Will this make the builds more unreliable? Just seems weird to use the PR validation to validate another build definition since the PR validation never uses the binaries from those steps.

One of the goals of the PR validation system is to verify that the PR won't break things downstream once merged.  So in this case this step would ensure that the PR doesn't break this aspect of our release builds without having to run the entire release pipeline.
If we think the build failures we saw in this area are a 1-off issue that we are highly unlikely to see again, and I suspect this is the case, then I'm fine saying it doesn't make sense to change every PR validation build in the future for a problem that isn't likely to reoccur.
I'll leave the PR pending and we can discuss with other build breaks in the weekly sync on Wednesday.  Thanks!

I mean those files that broke the build have never moved, this is the first, and now that they are in the root extension directory, there is no reason for them to move again.
I think a more reliable approach (but achieving the same goal) is to add a unit test that checks the presence of certain important files. This approach can also be used to catch other similar issues that have also caused problems.

Possibly, I expect this change would have caught the failures we saw today.  Though I suspect there are other mitigation that would server a similar purpose.  This change would also catch other errors such as incorrect config file contents, which I don't think unit tests could catch without actually downloading the bits.

I think the discussion was that we'll turn this on once we add the integration tests to the CI builds.  So I'll close this for now.


Pydantic architecture docs

We often get questions from contributors about the architecture / structure of Pydantic internals.
I think it'd be helpful to add a page to the docs that explains this in more detail, perhaps using a combination of descriptions + figures + charts.
While we're at it, we could link to a section of the contribution guide that could touch more on how to work on pydantic vs pydantic-core and better understand the relationship between the two.

@Viicos, just found this issue, wanted to ping you bc we chatted about this today :)


added polish and greek layouts

In response to issues:

#522
#490

Thanks for the contributions @maciej-sielski ! It's very much appreciated.
This is now live as of the latest release (1.13.1). It'll take a little bit to appear in the demos, since jsDelivr has a cache. Note: I also entered a few changes to make the layouts consistent with the other layouts.
Thanks again!
Francisco Hodge


Eliah Kagan: Watch iptchch.co.nz

Eliah Kagan requests the watch of the watch_keyword iptchch\.co\.nz. See the MS search here and the Stack Exchange search here.

iptchch\.co\.nz has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Shree in Charcoal HQ


_agro.standardized_precipitation_evapotranspiration_index creates NaNs

Generic Issue

xclim version: 0.44.0
Python version: 3.10.12
Operating System: Windows 10 Enterprise 22H2

Description
I am using ISIMIP chelsa-w5e5v1.0 30 arcsec resolution daily data from 1979 to 2016 (dimensions, time: 13880, y: 30, x: 57, bbox: [73.533, 18.967, 74.008, 19.217]) pr, tasmin and taxmax data to first calculate the pet (xci.potential_evapotranspiration) and the water budget (xci.agro.water_budget). No values are lost in these calculations and there are no NaNs present. However, when I then use xci.agro.standardized_precipitation_evapotranspiration_index to calculate the SPEI, two things happen:

Along the x axis, after a certain moment the SPEI values/pixels always become NaNs. These values do generally respond to the lowest SPEI values alongside the x-axis (in the west there is most rainfall due to orographic uplift, the eastern areas are substantially drier), however, there are lower water_budget values with other y coordinates that are not NaNs during other timesteps. Is it possible that at these pixels the algorithm is not able to fit distributions? If so, what would be a fix?
When I change the window below 12 periodically (corresponding to roughly 12 months) 3-5 timesteps (months) become NaNs. And with a window of 12 the first 10 timesteps become NaNs.

The settings for the function are as follows:
wb_cal = water_budget.sel(time=slice('1981-01-01', '2010-01-01'))

xci._agro.standardized_precipitation_evapotranspiration_index(wb = water_budget, wb_cal = wb_cal, freq = "MS", window = 12, dist = 'gamma', method = 'APP')

What I Received
For example, timestep 54 and 94:

And with a window of 6:

Does anyone know what could be going wrong?
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Have you seen https://github.com/Ouranosinc/xclim/issues/1416 and could it be related ?
If not, I would suggest trying to use the L-Moments method to fit the gamma distribution. This is not implemented at the moment though, but should be a simple fix if you're willing to tweak xclim (I suspect it would only require adding "PWM" to the dist_and_methods dict at the top of the spi function.

Hi, thanks for reporting this.
In this case #1416, the erroneous values obtained were ±np.inf, not NaN, so I'm not sure this is related. Also, the surrounding values of SPEI are not that extreme.  Just to describe #1416, this is not a big computation error, essentially for very unlikely values (0.000001 or 0.999999 in the CDF), once precision limits imposed by float32 make it so that we have probabilities 0.0 or 1.0, we get ±np.inf. This precision limit is addressed in #1311 by capping the values for standardized indices to reflect this precision limit.

however, there are lower water_budget values with other y coordinates that are not NaNs during other timesteps. Is it possible that at these pixels the algorithm is not able to fit distributions?

Ok, interesting (but those lower water_budget could still translate to larger SPEI values).
What if you shift the water budget by a positive value to ensure everything is positive in the computation? Since there are lower values of the water_budget that do not suffer from the problem, this probably won't solve everything, but it could reveal some instabilities in the fitting procedure nevertheless.

Thanks to you and your detailed report, it helped troubleshooting!
Just some last remarks for future discussions about this:

The SPEI function in xclim already shifts values by small amount, but your case seems to reveal this was not enough. The reason for choosing a fixed amount instead of something like I just proposed  e.g. : wb = wb - 1.01*wb.min() is that it can change a little the values SPEI. Say you calibrate with [1981,2010] that your whole dataset is [1981,2050], then you will have a given wb.min(). But if you extend your whole dataset to [1981,2100], then this could potentially change the wb.min() and change the shifting. So now, SPEI values in the original period [1981,2050]  could be modified a little (not that much, in principle the shifting should not affect the values of SPEI, but it can still have a little influence, which is not desirable).

In #1311, there will be an argument in SPEI function so that the user can choose the shifting value.

I believe the loc parameter would allow us to deal automatically with negative values in the gamma fitting, but this may bring its share of complications. This current way of proceeding in xclim was inspired by the monocongo library, but maybe I should look more into the R package (made the researcher who proposed SPEI).


Merge Wire Extras' holoAnim core with the vanilla hologram core

People have been talking about porting Wire Extras e2 cores on and off on the Wiremod discord for quite a while since Wire Extras might be undesireable for some server owners that don't want the abuseability of some of the other things added by it.
I fixed up the broken pose parameters and added some new functions that should make working with hologram animations easier.

It would be nice to have the ability to stop the entity from thinking too much when an animation is over, though i don't know any way to check if its over and not screw over looping animations.


allow multiple heroku install directives

Overview
This PR updates our fork of the heroku-buildpack-go project to allow installation of multiple pkgs via the
//+heroku install pkgName directive.
Story

n/a

Things That I Tested

deployed buildpack of this branch to analytics-api-staging dyno
deployed assessment-api#db-updates branch
multiple install directives are successfully run via

// +heroku install ./analytics/cmd/...
// +heroku install<EMAIL_ADDRESS>
Where More Testing Might Be Necessary

I'll do some QA on identity and assessment staging environments to ensure this isn't a breaking change.

Implementation Notes

Normally, we would have just been able to run something like // +heroku install ./anaytics/cmd/<EMAIL_ADDRESS>However, this fails due to a version mismatch between the packages.  Removing the early exit will gather every instance of the //+heroku install directive instead of just the 1st. I'm unsure if this will break anything else, but the pkgs variable seems like it was intended to be used for multiple packages based on other usages of for loops in the script.
I attempted to use the already built in functionality for bin/go-pre-compile and bin-go-post-compile, but was unable to get it working. I opened an issue in the original heroku repo here

Dependencies

n/a

Code Review Best Practices
Use code best practices for PR reviews

@jalandis Requesting a review from you here since I believe you were the one who originally did the setup for our custom heroku buildpacks. Let me know if I can provide any more context here for the changes being made.

Thanks for the speedy review!

I will approve now but wanted to confirm local dev expectations. Will developers be required to install this package version globally?

Could you elaborate on this? When you say developer will be required to install this package version globally, are you referring to<EMAIL_ADDRESS>or something else.

Thanks for the speedy review!

I will approve now but wanted to confirm local dev expectations. Will developers be required to install this package version globally?

Could you elaborate on this? When you say developer will be required to install this package version globally, are you referring to<EMAIL_ADDRESS>or something else.

Yah.  To be more precise, I was wondering how identity migrations would be executed when starting up the local dev server.  Or how developers would run up/down manually when creating new migrations.


Add support for vim-clap

This adds highlights for vim-clap

Hi @meck :wave:, thanks for your contribution :+1:
I'll review it in the near future and get back to you.

Can this be merged, please?

I would love to see this merged!

Sorry for this delay, life, other projects and tons of Nord issues/PRs keeps me busy 😐
I haven't checked and tested the actual code, but I'd like to throw in some thoughts regarding the design.
Nord's main accent is nord8 that can be combined with the other colors of the Frost palette. While Aurora colors like nord12 or nord13 might be used more often in other themes, Nord tries to keep they purpose as signal colors to style e.g. warnings and errors.
Therefore I'd like to propose to change the style for Vim Clap to use

nord4 as default foreground color.
nord8 as main color for matches
nord9 and nord10 for sub-matches since they have a darker appearance and nord8 should get the user focus while these both indicate that it might also match.

I use fzf as my main fuzzy finder for almost everything so I also use it together with [fzf.vim][]. While there's no official Nord port project for it (yet) I created a Nord theme for my personal use that is embedded into .dotfiles (large ZSH update coming soon™).
This is what is looks like when using the design I've described above:

Thanks again for the active feedback on this PR, really like the way the community works on such things 😄
Let me know what you think if we'd use this design for Vim Clap too.

I've cleaned this up a bit and conformed it to @arcticicestudio's suggestions, however I noticed Clap now has a auto-loaded theme system as used in liuchengxu/vim-clap#420. So it should probably be moved there (The same as airline and sightline)? Also all the providers have their own hl-groups, I've added a couple but the rest should probably be added as well.
Then there is the question if there should be a theme file in here and in the clap repo as well? I guess that is something for @liuchengxu and @arcticicestudio to agree on.

Then there is the question if there should be a theme file in here and in the clap repo as well?

The advantage of putting it in the colorscheme repo is when people use this colorscheme, they'll have the clap support aumatically and don't have to add the line let g:clap_theme = 'nord' explicitly. So I would second the former way if the clap theme has a original vim colorscheme.

Release Notes Assets


Memory leak in booster

@jberthold and @goodlyrottenapple identify that there is a probable memory leak in the booster via the C bindings; this needs to be minimised down to an example that can be run directly via a C program (or indeed, via valgrind).

I've collected a sample sequence of calls that seems to lead to slowly leaking memory. That is not really a minimal example unfortunately. The GHC evenlogs produced by tracing LLVM calls in the Booster grow very quickly, but I'm reluctant to try to minimize them to make sure the leak stays prominent.
Here's a gdrive link to llvm_calls.c. Note that it's 60 MB, and it has been produced during only a fraction of one 'execute' RPC call. Additionally, I had to filter out calls that are longer than 2^16 bytes long (most likely bytecode token initialization) for GHC infrastructure reasons.
I hope this would be enough to start iterating.

This looks great, thanks @geo2a - should be enough for me to take a look at fixing the leaks.

The approach of emitting api.kore* C calls from Booster proves to be cumbersome.
As an alternative, I've decided to try heaptrack, which is a Linux heap profiling tool. This tool runs much faster than valgring --leak-check=yes and the leaks that it detects seem to agree with memory residency that I see in htop.
What we're checking for leaks
First of all, we are running the booster-dev Haskell executable, which is a development version of kore-rpc-booster that does not fall back to kore-rpc (aka "the old Haskell backend"). This way we reduce the scope to the Haskell code in Booster and  the LLVM backend C library code it calls.
We're profiling a particular RPC execute request using KEVM-Foundry and a number of custom lemmas. The interaction is as follows:

start the server booster-dev definition.kore --llvm-backend-library ... --server-port ... --module ...
submit a request with rpc-client send execute-request.json, observer memory residency growing; repeat
stop the server

What we're seeing
Using the steps above, I've observed the memory residency grow by ~50 megabytes after each request. To get more specific data, we repeat the same steps, but now run the server under heaptrack, i.e. heaptrack booster-dev .... I'm attaching two profiles, produced by running the request ones and ten times:

heaptrack.booster-dev-llvm-leak-execute-1.zst
heaptrack.booster-dev-llvm-leak-execute-1.zst

We need to install heaptrack to browse the data using heaptrack_gui:
heaptrack_gui heaptrack.booster-dev-llvm-leak-execute-10.zst

That's how the summary window looks for the profile that sends the same execute request 10 times:

Interestingly, heaptrack does not instrument the Haskell runtime, so we don't get any noise from it in these profiles!
@Baltoli could you have a look at these profiles and see if they make any sense? I'm happy to meet at any time to describe the workflow in more detail if needed.

This profile makes more sense to me - we've experienced similar issues in the Python bindings previously: https://github.com/runtimeverification/llvm-backend/issues/770
It's worth noting that the Haskell backend does a slightly more restricted set of operations than Python (i.e. constructing a function term + simplifying it, rather than executing a program via rewriting). What is the concurrency model used by the booster? The difficulty with the current GC is that while we could in theory add a feature to clear all the memory allocated by the GC arenas, that would trample on other threads' objects (see https://github.com/runtimeverification/llvm-backend/issues/705 where we identified the need for a global GC lock previously).
If the booster makes calls via the shared library in a thread / memory-safe way then we can probably reduce the impact of this memory leak by adding a "free the world" function that gets called after each simplification is run (or at some other configurable threshold depending on performance). If not, given that this issue is cropping up for both Python and C bindings, we should perhaps try and find a way of redesigning / improving the LLVM backend's GC to avoid this pattern of leaking memory.

I seem to remember trying to run some GC function exported via the API, but that just caused seg-faults

Btw, the booster is currently single threaded-ish, in that we only ever run one request on the server (even tho it should be capable of handling multiple requests if there were multiple clients) and within that request, there are no concurrent calls to the LLVM shared library (I think).

Maybe that makes things easier then - will take a look at freeing the memory in a C example that doesn’t do rewriting, only function simplification and see where I get.

On 2 Aug 2023, at 10:47, Samuel Balco @.***> wrote:
Btw, the booster is currently single threaded-ish, in that we only ever run one request on the server (even tho it should be capable of handling multiple requests if there were multiple clients) and within that request, there are no concurrent calls to the LLVM shared library (I think).
—
Reply to this email directly, view it on GitHub https://github.com/runtimeverification/llvm-backend/issues/816#issuecomment-1661896126, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAKEPCV4YXXEYLIJ4ZMCYELXTIO4FANCNFSM6AAAAAA2YQIUV4.
You are receiving this because you were mentioned.

Unfortunately, calling the existing primitives, kllvm_init and kllvm_free_all_memory does not seems to work, please see this draft PR for details.
At his point, it is unclear what ways forward we have. Considering that we have other options to deal with mempry consumption in kore-rpc-booster, specifically killing the server and re-initializing it for long running proofs, I suggest we de-prioritize this issue for now.

The issue has been resolved by https://github.com/runtimeverification/hs-backend-booster/pull/263, feel free to close! Thanks everyone!


Allow to configure Accept header treatment

feat: support configuration of Accept header treatment
This commit changes default behavior. Set accept-header-policy to 'require' to have same handling of Accept header as before.
PR includes #18. If you like to merge them separately feel free to cherry-pick.
Closes #4

Thanks for submitting this PR.  This seems like a great addition.  @jlaswell Are you opinionated and/or do you want to review this?  Looks good to me.

I actually took a look at this earlier this morning and think it's a good idea for how to handle default behavior. Thanks for cleaning up the long standing issue, @jelhan! ^.^
Since this does affect default behavior, we should bump major version and dupe branches for a bit so we can backport any new features or fixes. :/ That'll require an update to the CHANGELOG, and then we should add a suggest to the composer.json to update the package to 2.x.x. I can handle those changes @jelhan, if you don't want to deal with those administrative tasks. I'd like to add it as part of this PR though, so that it all happens at the same point in time.

@jlaswell I would appreciate if you handle these changes since I haven't much spare time these days. Also I'm not quite sure if there are any other changes which should be taken into account when updating changelog. Will merge a PR against my branch as soon as possible.

@jelhan 👍  It's a Friday, and I'm wrapping up some work myself, but I'll make a note to get to this and hopefully have it in sometime Monday.

Any progress on this?


Add Dark Mode Feature to the Virtual Bubble Wrap

Description:
We would like to implement a Dark Mode option for the Virtual Bubble Wrap website, which respects the user's system-wide dark mode setting using the prefers-color-scheme media query.
Goals:

Automatically detect the user's system dark mode preference using prefers-color-scheme.
Add a toggle button or switch that allows users to manually override the system preference.

Suggested Steps:

Use the prefers-color-scheme CSS media query to apply dark mode based on the user's system setting.
Create a toggle button or switch to allow users to manually switch between dark and light mode.

Hi, @sirisayshello. I am a beginner at open-source contributions, do you mind if I go ahead and try to solve it?

Hi, @sirisayshello. I am a beginner at open-source contributions, do you mind if I go ahead and try to solve it?

Hi @SuvineetSingh, sure go ahead!

thanks!

Hi @sirisayshello , I have opened a merge request and am making the necessary changes. Please have a look, and let me know if I can make any more edits according to your suggestions.


[Task] prepare channelserver k3s min and max versions for release

What kind of request is this (question/bug/enhancement/feature request):
task
Description:
need to decide on k3s release to include in /releases for v2.4 and add them to kontainer-driver-metadata.

We've left in older versions for the purposes of testing, but we'll just have 1.17.4 in the list when we go live

@daxmc99 can we make a PR for this so that when it comes time, it's ready to merge and we can then test around it?

For reference: the root of truth repo for this is https://github.com/rancher/kontainer-driver-metadata/blob/dev-v2.4/data/data.json

https://github.com/rancher/kontainer-driver-metadata/compare/dev-v2.4...daxmc99:k3s_version_2.4?expand=1
Do we want to merge into the dev-v2.4 branch or is there going to be a release 2.4 branch I should make the PR to?

You can make a PR to dev-v2.4, but that whole branch will eventually be moved to create a new release 2.4 branch.

system-upgrade-controller should be version v0.4.0

Tested on master head - e78331527
Only 1.17.4 appears in version.

System-upgrade-controller has the version v0.4.0

An upgrade from v1.16.3 to v1.17.4 went through smoothly.


feat: support heap profiling

Support the generation of pprof profiles of heap usage by using jemalloc facilities.
This requires jemalloc to be configured with some special options, hence all the builds will have this settings enabled. This doesn't seem to cause performance regressions from what I've seen while doing load tests locally.
I've also added some instructions explaining how to memory and CPU profiling.

I've done the following changes:

jemalloc's pprof support is enabled by default, but is NOT active
when jemalloc's pprof is active there's a higher CPU usage
jemalloc's pprof is automatically activated once the 1st heap profile generation is requested
once activated, the pprof cannot be deactivate. I could change it, but that would require adding a new API endpoint. It's not then end of the world, but I don't think we need it


[12.0.x] ISPN-12730 NPE when mapping a repeated non-indexed field in a schema

https://issues.redhat.com/browse/ISPN-12730

Please backport the comments @gustavonalle

done @danberindei

Merged, thanks Gustavo!


[BEAM-13570] Remove erroneous compileClasspath dependency.

Please add a meaningful description for your change here

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

Run Spark ValidatesRunner

R: @lukecwik

Looks like tests are failing, but at least they build properly now.

Those tests are marked as skipped in the PVR suite for batch here: https://github.com/apache/beam/blob/c67bed4080734fdff9ae416483ce5591a98441f8/runners/spark/job-server/spark_job_server.gradle#L166
        excludeCategories 'org.apache.beam.sdk.testing.UsesPerKeyOrderedDelivery'
        excludeCategories 'org.apache.beam.sdk.testing.UsesPerKeyOrderInBundle'

that should allow the test to become green.

Run Spark ValidatesRunner

Run Java PreCommit


Introduce and use typing

Your project currently does not make use of typing: https://docs.python.org/3/library/typing.html
Everyone working with your library and / or implementing new plugins and renderers will have a hard time figuring out what you data structure looks like, what methods and parameters are expected, ...
In my experience using typing also vastly improves code quality and reduces mistakes.
Please consider to use typing for your v2 remake.

@lepture I found this comment for yours here:

please don't add type hint. Mistune is compatible with Python 2.7

I very much disagree with that.
Python 2 is no longer supported since 01.01.2020. That's now already one year. You are going to release a new major version of mistune. This is absolutely the right time to break python 2.7 support and only support python 3+.

@lepture I found this comment for yours here:

please don't add type hint. Mistune is compatible with Python 2.7

I very much disagree with that.
Python 2 is no longer supported since 01.01.2020. That's now already one year. You are going to release a new major version of mistune. This is absolutely the right time to break python 2.7 support and only support python 3+.

Yeah, it is time to support typing now.

added in v3.


npm fails on install (windows)

will run: cargo install --path crates/ra_lsp_server --locked --force
  Installing ra_lsp_server v0.1.0 (C:\Users\jasew\workspace\rust-analyzer\crates\ra_lsp_server)
    Updating crates.io index
    Finished release [optimized] target(s) in 0.61s
  Installing C:\Users\jasew\.cargo\bin\ra_lsp_server.exe
   Installed package `ra_lsp_server v0.1.0 (C:\Users\jasew\workspace\rust-analyzer\crates\ra_lsp_server)` (executable `ra_lsp_server.exe`)

will run: cmd.exe /c npm --version
6.12.1

will run: cmd.exe /c npm ci
npm WARN prepare removing existing node_modules/ before installation
npm ERR! code ENOENT
npm ERR! syscall open
npm ERR! path C:\Users\jasew\workspace\rust-analyzer\editors\code\node_modules\typescript\package.json
npm ERR! errno -4058
npm ERR! enoent ENOENT: no such file or directory, open 'C:\Users\jasew\workspace\rust-analyzer\editors\code\node_modules\typescript\package.json'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent

npm ERR!      C:\Users\jasew\AppData\Roaming\npm-cache\_logs\2019-11-30T20_42_18_971Z-debug.log
Error: install client

Caused by:
    `cmd.exe /c npm ci` exited with exit code: 0xfffff026
error: process didn't exit successfully: `target\debug\xtask.exe install` (exit code: 1)

Seems like typescript doesn't install before properly.
Looks like its to do with npm ci, when i install manually with npm install its fine.
I think this is only happening on windows

Hm, interesting...
Have no idea what's going on here, really. We use npm ci for installation because, as far as I know, it's the only install-like command that actually honors package-lock.json.

@matklad both ci and install honor the package-lock.json file
https://docs.npmjs.com/cli/install
I think ci will remove the entire node_modules folder and start again, plus it will error if a dependency isn't in the package-lock.json file.
https://stackoverflow.com/questions/52499617/what-is-the-difference-between-npm-install-and-npm-ci
Not sure why this issue happens though, looks like something tries to use typescript before the install is finished? or ci is not re-populating that dep

I have managed to fix some of this by using npx before the command so it will use the local node_modules dep instead of looking in the PATH globally.

both ci and install honor the package-lock.json file

Hm, I am pretty sure this wasn't the case a while ago. But yeah, looks like now install is OK?  I've change ci back to install in #2462

Ive set it to install which gets me further but now its trying to find vsce which doesn't exist

It should pick the one from node_modules: https://docs.npmjs.com/misc/scripts#path. I definitelly don't have vsce installed globally, but it works for me

ok interesting, i must have some weird symlink failure going on there.
Will need to investigate

@jasonwilliams Are you still having problems, or can we close the issue? :)

@kiljacken you can close, i will open a new ticket if it happens again :)

I just ran into this on my semantic-tokens branch.

It looks like cargo xtask install is changing my npm from my local version to the one in C:\Program Files\nodejs


Initial Adoption of Continous Deployment using semantic-release

To ease the modification/contribution to publish pipeline there has been some discussion of adopting a continuous deployment system for AtomLinter packages. To accomplish this we are making use of semantic-release and @semantic-release/apm-config.
This pull request has been dynamically created using a script. While the result is not perfect, it does accompish most of the grunt work of adopting continous deployment. There is some reconciliation that needs to be done before this can be merged.
Among the things needed to be reconciled, an APM Token and GitHub Token will need to be added to this repo's continous integration (most likely Travis CI) configuration for automated deployments to work.
Again, this Pull Request has been created by a script made by @keplersj. Please mention him if something has gone wrong, and he'll be happy to help.
ref: AtomLinter/Meta#18
cc: @Arcanemagus

@AtomLinter/linter-pydocstyle Any objections to the Conventional Commits requirement? There are alternative standards available if somebody has a strong objection to that standard, but we need to pick one to finish implementing this 😉.

No objections


Check for unused CSS in CI

We have the rendered CSS and all the output HTML… it should be possible to look for unused CSS selectors or places where I have redundant selectors.
There are tools for doing this, e.g.

FullHuman/purgecss
peterbe/mincss
https://www.jitbit.com/unusedcss/

Run one of those in a Docker image against the build output before giving a green tick.
Spotted while working on #278.

I did look at using the CLI version of purgecss with the following command:
purgecss \
  --css '_site/theme/style.css' \
  --content '_site/**/*.html' \
  --rejected | jq --monochrome-output 'map(del(.css))[0].rejected'

but it turns out not to be as effective as I want.
In particular, the following CSS file:
p.unused {
  color: blue;
}

and HTML file:

Hello world

This is a link

will fail to spot the unused selector. It sounds like the way round this is to use an extractor, but I don't know if I can be bothered.


Introduce Bach.java as build tool

Overview
This draft PR introduces Bach.java as a potential new build tool for Silk DI.
Deliverables

[x] Introduce module descriptor se.jbee.inject with all bells and whistles.
[x] Core realm, including module se.jbee.inject, is compiled to Java SE release 8.
[x] Integrate in CI system via GitHub Actions
[x] Test realm with all unit and integration tests being green.
[ ] Create modular API documentation (javadoc 14 reports a bunch of warnings and errors).

Build

Install JDK 14
Call jshell https://sormuras.de/bach-build

Project Descriptor
The following printout of Silk's project descriptor is the current result of the configuration process encoded in Build.java, the custom build program. It will change over time, till the PR is ready for review. Find the latest-and-greatest printout in the .bach/workspace/summary.md file.

If Silk used a more JDK-like directory tree pattern below src/, Bach could scan that automatically.

Project
	title: Silk DI
	version: 1-ea
	realms: [core] << 1 distinct unit(s)
	declares: [se.jbee.inject]
	requires: [java.desktop, java.logging, java.management]
	external: []
	Realm core
		flags: []
		upstreams: []
		Unit se.jbee.inject
			Module Descriptor se.jbee.inject
				main-class: -
				requires: [java.base, java.desktop, java.logging, java.management]
			Sources
				path: src/core
				release: 8
				path: src/core-module
				release: 9

Preliminary marked as ready for review to let GitHub Actions kick in...

...which didn't happen. Converting PR back to draft.

Test run finished after 925 ms
[        93 containers found      ]
[         0 containers skipped    ]
[        93 containers started    ]
[         0 containers aborted    ]
[        93 containers successful ]
[         0 containers failed     ]
[       377 tests found           ]
[         0 tests skipped         ]
[       377 tests started         ]
[         0 tests aborted         ]
[       373 tests successful      ]
[         4 tests failed          ]

...with only 4 failed. Find them with stacktrace snippets below:
  JUnit Vintage:TestAggregatingEvents:dynamicAggregationIsPerformed
    MethodSource [className = 'se.jbee.inject.event.TestAggregatingEvents', methodName = 'dynamicAggregationIsPerformed', methodParameterTypes = '']
    => java.lang.NullPointerException
       se.jbee.inject/se.jbee.inject.event.$Proxy29.dynamic(Unknown Source)
       se.jbee.inject/se.jbee.inject.event.TestAggregatingEvents.dynamicAggregationIsPerformed(TestAggregatingEvents.java:101)

  JUnit Vintage:TestAggregatingEvents:staticAggregationIsPerformed
    MethodSource [className = 'se.jbee.inject.event.TestAggregatingEvents', methodName = 'staticAggregationIsPerformed', methodParameterTypes = '']
    => java.lang.NullPointerException
       se.jbee.inject/se.jbee.inject.event.$Proxy29.all(Unknown Source)
       se.jbee.inject/se.jbee.inject.event.TestAggregatingEvents.staticAggregationIsPerformed(TestAggregatingEvents.java:95)

  JUnit Vintage:TestRoundRobinComputeEvents:computationUsesAllAvailableServices
    MethodSource [className = 'se.jbee.inject.event.TestRoundRobinComputeEvents', methodName = 'computationUsesAllAvailableServices', methodParameterTypes = '']
    => se.jbee.inject.event.EventException
       se.jbee.inject/se.jbee.inject.event.ConcurrentEventProcessor.doCompute(ConcurrentEventProcessor.java:219)
       se.jbee.inject/se.jbee.inject.event.ConcurrentEventProcessor.doProcess(ConcurrentEventProcessor.java:212)
       se.jbee.inject/se.jbee.inject.event.ConcurrentEventProcessor.lambda$compute$5(ConcurrentEventProcessor.java:200)

  JUnit Vintage:TestServiceLoaderBootstrapBinds:serviceLoaderCanBeUsedToDeclareModuleRoots
    MethodSource [className = 'se.jbee.inject.bind.TestServiceLoaderBootstrapBinds', methodName = 'serviceLoaderCanBeUsedToDeclareModuleRoots', methodParameterTypes = '']
    => No matching resource found.
	 dependency: java.lang.Integer *
	available are (for same raw type): none

       se.jbee.inject/se.jbee.inject.container.Container$InjectorImpl.noResourceFor(Container.java:294)
       se.jbee.inject/se.jbee.inject.container.Container$InjectorImpl.resolveFromUpperBound(Container.java:277)
       se.jbee.inject/se.jbee.inject.container.Container$InjectorImpl.resolve(Container.java:262)
       se.jbee.inject/se.jbee.inject.Injector.resolve(Injector.java:59)
       se.jbee.inject/se.jbee.inject.bind.TestServiceLoaderBootstrapBinds.serviceLoaderCanBeUsedToDeclareModuleRoots(TestServiceLoaderBootstrapBinds.java:41)

Guess, some of them require the "example" project to be available on the class path. Working that out tonight. Or will ignore them for the time being... 😱

will ignore them for the time being

That is fine. Does not look to be critical or hard to fix later ones.
BTW if you need me to do something or have a closer look please ping me and make that explicit. Currently not much online and might miss that otherwise.

"Fixed" one or two by keeping them close to the example module. The other tests are ignored.
Yeah, please take a look at this screenshot attached to sormuras/silk#2 -- maybe you can spot the code setting the null at first glance.

Wohoo! 🎶


MLOps - data pipeline 跟 3 pipeline architecture 文章撰寫

MLOps - data pipeline 跟 3 pipeline architecture 文章撰寫

KM

took 8 hrs
done


RBR is shown in the report preview for the pending card transaction even though these reports can be approved

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number:
Reproducible in staging?:
Reproducible in production?:
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?:
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @tgolen
Slack conversation (hyperlinked to channel name): expensify bugs
Action Performed:

Submit a card expense to the approver
As a approver open the expense (card expense is not merged yet)
Observe there is a GBR in the LHN and RBR in the report preview

Expected Result:
Since the card transaction can be approved even in if the card transaction is in pending state there should be GBR
Actual Result:
RBR is shown for the card transactions
It would be nice then if it was a green dot and the text was more like "Approve without waiting for credit card merge [APPROVE]"
Workaround:
unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android: Standalone
[ ] Android: HybridApp
[ ] Android: mWeb Chrome
[ ] iOS: Standalone
[ ] iOS: HybridApp
[ ] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

View all open jobs on GitHub

This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989

Tagging in @Expensify/design to weigh in on any thoughts on text/how we communicate this to users. This sounds like a new feature.

I've read the Slack thread, I'm not 100% sure what the right move here is. I think the confusing thing is that we have GBR in LHN and RBR on the report. This feels conflicting. cc @JmillsExpensify and @trjExpensify here too

Yeah, I'm not sure what the best answer is either, curious for Jason & Tom's thoughts.
Also cc @dannymcclain this is another place where we need to consider how the category/tag line on an expense preview will look alongside this "Receipt pending match with card transaction" message...

Good call. I'm a bit confused though—I was initially going to say we could treat it the same way as the pending card transaction with something next to the "Card" eyebrow: Card • Pending or Card • Receipt matching or something... But looking at the screenshot, that preview looks like it's a report preview, not an expense preview? The eyebrow text "NewDot Test EC Feed only - Expensify coffee owes:" is worded like a report, not an expense? Have I lost all my marbles here?

Ah good observation, I think you are right. I'd be curious what this one looks like at the expense level, if it even exists? cc @grgia for thoughts there

Yeah, I'm not sure what the best answer is either, curious for Jason & Tom's thoughts.

We're removing the GBR that's showing to the approver if all the transactions on the report are pending in this issue, because there's not really any action for them to take yet. The PR for that is up for review.

What Tom said.

I would say that the answer to that question is yes, as you still need to fix issues/violations if they are present. That said, I want to make sure that this initiative remains consistent with this issue, and this comment in particular.

Do we only close the report once the transaction is posted? If so, then yes your statement sounds right to me.

In the instant+no approvals case? Yah.

Apologies, just catching up here - so if I'm understanding correctly, we want to move forward with fixing this so the 🔴 appears in the LHN?

For which user now?

Sorry, the LHN for the approver (i.e. @tgolen in this case)

So @trjExpensify is there anything here that actually needs to be fixed? I'm getting quite confused.

I don't think so, because the GBR in the LHN is being removed in this issue: https://github.com/Expensify/App/issues/52315

Awesome, thanks Tom - closing!


When switching to land in VTOL, update land target during back trans

Currently, when switching to LAND mode on a vtol, it will perform a back transition and landing simultaneously. This prevents the vehicle trying to navigate back to where the back transition started during landing as it might result in a landing while tilted.

@PX4TestFlights Due to weather conditions i am unable to test this safely.
Could you test fly on a vtol:
Param NAV_FORCE_VT: enabled (this is default)
Fly in any mode and switch to LAND. It should do a back transition and land at the location it came out of the backtransition. Before this PR it will attempt to navigate back to the place where the LAND command was initiated while descending.

We need to be careful here and make sure the throttle and speed is set in the position setpoint.

This is also a problem for regular multicopters if you flip into LAND mode with any velocity.
Something like the simple state machine in other nav states like RTL would work well. First come to a full stop (including back transition if a VTOL), then create the land waypoint below.
Similar to https://github.com/PX4/Firmware/pull/8101.
@Stifael FYI

I think it is similar to https://github.com/PX4/Firmware/pull/8057

Should we get this in after testing and work on a better state machine for 1.8?


Wiki - Rules Schema has a broken link

Rules schema is available in the [schema file](https://github.com/microsoft/RulesEngine/blob/master/schema/workflowRules-schema.json). The workflow rules are how we store the rules in the system. ...
Current URL
https://github.com/microsoft/RulesEngine/blob/master/schema/workflowRules-schema.json
Proposed URL
https://github.com/microsoft/RulesEngine/blob/main/schema/workflow-schema.json
It may be that the entire wiki needs to be reviewed to change "master" to "main" for URLs.

Fixed wiki links to point to main


Speed improvements to RadarDataset

Description

Many improvements to RadarDataset.
Related issues:
Instructions to review the pull request
The following script ran on 271.5 seconds on SURF Research Cloud:
import time

from bird_cloud_gnn.radar_dataset import RadarDataset

st = time.perf_counter()
try:
    dataset = RadarDataset(
        "data/parquet",
        ["x", "y", "z"],
        "BIOLOGY",
        min_neighbours=25,
        max_distance=500.0,
        max_edge_distance=250.1,
    )
    print(dataset)
    print(dataset[0])
    print(dataset[0][0])
except ValueError as ex:
    print("Error:", ex)
print("Total time:", time.perf_counter() - st)

data/parquet contains all data converted to parquet files (114 files). The results:
Dataset("Radar", num_graphs=383288, save_path=/home/asoaressiq/.dgl/Radar)
(Graph(num_nodes=25, num_edges=487,
      ndata_schemes={'x': Scheme(shape=(3,), dtype=torch.float64)}
      edata_schemes={'a': Scheme(shape=(), dtype=torch.float64)}), tensor(0))
Graph(num_nodes=25, num_edges=487,
      ndata_schemes={'x': Scheme(shape=(3,), dtype=torch.float64)}
      edata_schemes={'a': Scheme(shape=(), dtype=torch.float64)})
Total time:<PHONE_NUMBER>749871

That looks very quick! I'm currently also playing around with it.


As a student, I can type part of the tag name and get the tag as search suggestions

... so that I can search faster and minimize the chance of an unsuccessful search.
For example:
search t/fa will show tags starting with fa.

Move this to milestone v1.3 after the search command and tag features are completed.


Set the name of the included build from the include name

As discussed on Slack, please make it so that
gitRepositories {
    include("fonts_v3_0") {
        uri.set("git@git.company.com:fonts")
        tag.set("v3.0")
        includedBuild {
            name = "fonts_v3_0"
        }
    }
}

could simply be
gitRepositories {
    include("fonts_v3_0") {
        uri.set("git@git.company.com:fonts")
        tag.set("v3.0")
    }
}

I am actually a bit confused. The checked out directory should be named after the include name. So it should be fonts_v3_0 already.

Now I'm confused too.
I removed the name =  lines at the included builds seem to be named like I want it.
But for some reason I had to set the name explicitly. :-/
Sorry for the noise.


The "Read the code" button deletes everything without warning

why why why why why

I just completely wiped a collaborative document other people were working on because I was curious what the button does. Please change the behaviour of the button to either open a new document with the code, or give a confirmation dialog before the contents are wiped.