Problem with pip installation and long path names

I ran into trouble installing and running apexpy on my Mac.  One issue I'm not sure what the problem is, the other one I was able to fix very simply:

installing using pip failed with:
Command /usr/bin/python -c "import setuptools, tokenize;file='/private/var/folders/jz/syw9ddrj3ds5_j1gcnxdzz6m0000gq/T/pip_build_ab763/apexpy/setup.py';exec(compile(getattr(tokenize, 'open', open)(file).read().replace('\r\n', '\n'), file, 'exec'))" install --record /var/folders/jz/syw9ddrj3ds5_j1gcnxdzz6m0000gq/T/pip-FM9MtN-record/install-record.txt --single-version-externally-managed --compile failed with error code 1 in /private/var/folders/jz/syw9ddrj3ds5_j1gcnxdzz6m0000gq/T/pip_build_ab763/apexpy
Storing debug log for failure in /Users/ab763/Library/Logs/pip.log

I grabbed the source code and did the install myself.  The everything was successful, but I couldn't use the routines because when I tried to initialise the Apex object I received this error:

At line 175 of file src/fortranapex/apexsh.f90 (unit = 23)
Fortran runtime error: Cannot open file '/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/apexpy-1.0.1-py2.7-macosx-10.12-x86_64.e': No such file or directory
Obviously, the path that my computer stored the data file was too long for the character limit allowed in the filename.  I changed the allowed length from 123 characters to 1000 characters in apexsh.f90 (in two places) and now the code runs fine.
Details about my system:
Your operating system name and version: MacOS Sierra v 10.12.6, python 2.7
Any details about your local setup that might be helpful in troubleshooting: I usually install things using macports
Detailed steps to reproduce the bug: use a long path name for the data file

Hi Angeline, thanks for the detailed bug report. Unfortunately I've left academia some years ago and haven't touched this package since (nor any other Python code, for that matter). Thus, I'm unable to make any significant contributions or fixes to apexpy (and AACGMv2).
If you or anyone else want to take over maintenance of these packages, I'm more than happy to arrange that. In any case, I'm going to leave this bug open.
Nice profile pic, btw. ESR is definitely one thing I miss from my PhD years.

Hi Christer,
I remember that you had left academia, but I wasn’t sure if you were still dabbling with the packages.  Thanks for contacting me, and not leaving the bug report hanging.  I’d be happy to take over the maintenance of these packages for the moment.  I’m working with some people (who have funding!) to develop a cohesive space physics python package.  So even if I don’t end up doing the maintenance myself, I’ll be able to ensure that the work you’ve done on these doesn’t need to be repeated.
Thanks!  That picture was a lot of fun :->
Cheers,
Angeline

On 15 Feb 2018, at 14:39, Christer van der Meeren<EMAIL_ADDRESS>wrote:
Hi Angeline, thanks for the detailed bug report. Unfortunately I've left academia some years ago and haven't touched this package since (nor any other Python code, for that matter). Thus, I'm unable to make any significant contributions or fixes to apexpy (and AACGMv2 https://github.com/cmeeren/aacgmv2).
If you or anyone else want to take over maintenance of these packages, I'm more than happy to arrange that. In any case, I'm going to leave this bug open.
Nice profile pic, btw. ESR is definitely one thing I miss from my PhD years.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/cmeeren/apexpy/issues/2#issuecomment-366054545, or mute the thread https://github.com/notifications/unsubscribe-auth/AGuC_g_0sxcGUuYWqSD_2wqfl_duKBUdks5tVJYTgaJpZM4SHYvh.

Thanks! Should I go ahead and transfer this repo and AACGMv2 to your user?

Also, I'll need your PyPI username to add you as an owner so you can publish updates.

Yes, go ahead and transfer apexpy and AACGMv2 to my user.  Here is my PyPI user name: aburrell.  Let me know if there’s anything else you need.
Cheers,
Angeline

On 22 Feb 2018, at 12:13, Christer van der Meeren<EMAIL_ADDRESS>wrote:
Also, I'll need your PyPI username to add you as an owner so you can publish updates.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/cmeeren/apexpy/issues/2#issuecomment-367770870, or mute the thread https://github.com/notifications/unsubscribe-auth/AGuC_t15ux_UaXbYBvFNPCRHtRNNQ8xdks5tXa5fgaJpZM4SHYvh.

Done. It would be great if you could give me your username (or register) at readthedocs.org, where the documentation is.
As for deployment, I've linked the repo with AppVeyor and Travis so that all tests are run for each commit. Travis tests on Linux and AppVeyor on Windows. Tagged commits are automatically pushed to PyPI from AppVeyor if tests succeed (that's where the compiled PyPI binaries come from). This requires the AppVeyor environment variables PYPI_USER and PYPI_PASS to be set to your PyPI username/password.
I have no idea if the deployment still works (it's been a while since the last deployment) or what happens now that things are transferred, but if you too want to have automated deployment you should be able to set things up fairly easily (hopefully) using your own accounts. I'll delete my stuff at AppVeyor and Travis.

Thanks Christer!
My username at readthedocs is also aburrell.
I was unaware of AppVeyor, I’ll check it out.  I’ve been having issues testing on Windows (since I don’t know many people who use that operating system) so it will be very helpful.  Travis has been a godsend.
I’ll let you know if I encounter any issues, but I think things should be good.  Thank you again for transferring these packages over.  It’s nice not to need to duplicate someone else’s good work.
Cheers,
Angeline

On 22 Feb 2018, at 12:46, Christer van der Meeren<EMAIL_ADDRESS>wrote:
Done. It would be great if you could give me your username (or register) at readthedocs.org, where the documentation is.
As for deployment, I've linked the repo with AppVeyor and Travis so that all tests are run for each commit. Travis tests on Linux and AppVeyor on Windows. Tagged commits are automatically pushed to PyPI from AppVeyor if tests succeed (that's where the compiled PyPI binaries come from). This requires the AppVeyor environment variables PYPI_USER and PYPI_PASS to be set to your PyPI username/password.
I have no idea if the deployment still works (it's been a while since the last deployment) or what happens now that things are transferred, but if you too want to have automated deployment you should be able to set things up fairly easily (hopefully) using your own accounts. I'll delete my stuff at AppVeyor and Travis.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/aburrell/apexpy/issues/2#issuecomment-367780460, or mute the thread https://github.com/notifications/unsubscribe-auth/AGuC_iYNUATD9MhFCN607ZJWf7mOdgQ4ks5tXbXugaJpZM4SHYvh.

Yep. And if you want to directly integrate the code into other packages, you're welcome to for my part.
Oh, and just a quick cc to @klaundal so he knows I don't have anything more to do with apexpy.

I've added you as a maintainer on readthedocs now. I can't seem to remove myself - could you remove me from both packages?

Hi @klaundal, I'll be sure to let you know if there's anything I need.
@cmeeren, I took you off of the readthedocs.  Thanks for handing everything over.
Cheers,
Angeline


Find Authorization without AuthorizationAction record not finding records

Find Authorization without AuthorizationAction record;  resulted in this notification:

even though my selected Authorization did not have an AuthAct record:

from Version Table:

Originally posted by @CanDKD in https://github.com/agrc/uic-addin/issues/30#issuecomment-532836153

I can't reproduce this. I'm going to close this and after the next release if this is still an issue lets reopen this with a bit more information about what data/version you are using.


Change how Future Scores and Knockout Fixtures are displayed.

Remove -1 from future scores
Teams for Knockout fixtures which are yet to be decided are displayed as TBD.

@ManrajGrover Thanks! Great tool btw, really made checking for football updates simple for me :) .


Fix a bug in lipm_traj_gen

A little bug caught by DRAKE_ASSERT() when I run the code with valgirnd.

This change is

Can you give an explanation for what the bug is? Why don't the initializations for K and A not cause the same error?

The number of polynomial segments should be equal to the number of columns of alpha.
https://github.com/RobotLocomotion/drake/blob/master/common/trajectories/exponential_plus_piecewise_polynomial.h#L45
When running in debug mode, we get a runtime error from this line of code in the link.
This bug might cause issues, but it's still better to remove it to prevent potential memory leak.

I'm just asking because I'm not convinced that this should be the source of the bug.

Hmm maybe my statement was confusing. I probably shouldn't call this a "bug".
I was debugging my code in a branch, but the program stopped early because of the DRAKE_ASSERT(). I had to make this one line fix to see valgrind outputing the message of the actual bug.

Another option is to remove K A and alpha and just use the default constructor - ie ExponentialPlusPiecewisePolynomial<double> exp;. This fix seems cleaner to me than setting a value for alpha and not using it later.

Yeah using default constructor is much cleaner!


Extra pixels under status bar

There are some extra pixels under the status bar. Increase the font size to see it more clearly. Also, resizing the window vertically will change the width of the extra pixels.

VSCode Version: 1.35.0
OS Version: Windows_NT x64 10.0.18362

Steps to Reproduce:

Launch VS Code

Does this issue occur when all extensions are disabled?: Yes

Can you try to reproduce with our nightly insider builds? You can give our preview releases a try from: https://code.visualstudio.com/insiders/

Same problem with insider build, the extra pixels are dark, and the right boarder also gets some. If you resize the window, the extra pixels will also change.

Yeah likely related to zooming, nothing we control as far as I know, but happy to learn otherwise.

This issue seems to originate from an upstream component and is not something VSCode can fix by making a change to the code. As such, I will go ahead and close it. If you can identify the component that is causing the issue, please report it upstream:

for UI, OS integration: https://github.com/electron/electron
for Rendering: https://bugs.chromium.org/p/chromium/issues/list
for file IO: https://github.com/nodejs/node

Thanks for understanding.


rethink sendTransaction's internal queue

I think I have my head wrapped around why our sendTransaction can sort of have a "failure cascade" and why this shows up most drastically with optimistic rendering, especially when the next write depends on the previous write.
Our current approach mirrors sendTransaction but uses an in-memory nonce counter and parallelizes everything except submitting the prepared tx to the mempool (to ensure nonce ordering). It looks something like:
tx1: simulate --> send --> return
tx2: simulate -----------> send --> return
tx3: simulate --------------------> send --> return

(the nonce isn't incremented until just before send, where we send the simulated/prepared tx to the mempool with the next nonce, to ensure we don't increment the nonce if the simulation fails)
The problem shows up if tx2 or tx3 depend on state from tx1, where the parallelized simulation step might end up with incorrect results, but we end up submitting it anyway. And our current approach makes it hard to signal that we should re-simulate a given tx and all the ones after it.
To allow for re-simulating a tx after a revert and to avoid doing too much unnecessary work ahead of time, we can restructure the queue to always have the next tx (or two?) in the queue simulated before sending to the mempool, and be able to retry the simulation in case of failures:
tx1: simulate --> send --> return
tx2:              simulate --> send --> return
tx3:                           simulate --> send --> return

If a send call to the mempool reverts, a retry might look like:
tx1: simulate --> send --> return
tx2:              simulate --> send --> revert --> simulate --> send --> return
tx3:                           simulate ----------------------> simulate --> send --> return

If I recall, the simulate call is there to ensure we can safely increment the nonce and to help us get nicer errors from reverts (where a send doesn't give us this data), so we could also flip this around to only simulate on a revert or increment nonce on success:
tx1: send --> nonce++ and return
tx2:          send --> revert --> send --> revert --> simulate and return error
tx3:                                                  send --> nonce++ and return

(the above assumes we only retry a reverted send call once)
There's also an open question around whether we should flush the queue if there are consistent reverts after retries, where tx3 in the above example wouldn't execute at all.

The above gets a little more complex if we look at writeContract, which uses the transaction simulation to estimate gas before submitting the tx, so we may not be able to blind-send approach there.

We may want conditionals for only local accounts, since MM and others do their own nonce handling?

MM and others do their own nonce handling?

This MetaMask doc page says, "MetaMask doesn't allow dapp developers to customize nonces".
https://docs.metamask.io/wallet/how-to/send-transactions/#nonce
Since sending many transactions in a short period is harder with external wallets than with burner wallets, can we just use the bare sendTransaction for external wallets?

Thought about this some more, and even the above approach of simulating the transaction in parallel with the send of the previous doesn't help us much except save some latency in best cases, get reverted txs in the worst cases. My understanding is that just submitting to the mempool doesn't simulate the tx result at all, only validates the nonce and maybe also gas?
I think the best path forward for now is to just simulate immediately before sending without any parallelization (for now) and we can figure out how to speed things up later.

closing for now since the underlying issues was addressed by https://github.com/latticexyz/mud/pull/2364


ui-router 0.2.18 and ui-router-extras 0.1.2

I update ui-router to 0.2.18 and ui-router-extras to 0.1.2 and now I got some error...
The navigation still occurs, but this error appears on the console:
ERROR When debug is true
angular.js:10137 TypeError: Cannot read property 'self' of undefined
at debugViewsAfterSuccess (ct-ui-router-extras.js:1260)
at transitionSuccess (ct-ui-router-extras.js:1206)
at processQueue (angular.js:15757)
at angular.js:15773
at Scope.$digest (angular.js:16841)
at Scope.$apply (angular.js:17133)
at bootstrapApply (angular.js:1713)
at doBootstrap (angular.js:1711)
at bootstrapAngular (Main.js:1885)
at InitApp (GlobalService.js:6)
ERROR When a state change happens
angular.js:10137 Error: Could not resolve 'undefined' from state 'ANY_STATE_NAME'
at Object.transitionTo (angular-ui-router.js:3179)
at Object.$state.transitionTo (ct-ui-router-extras.js:215)
at Object.$state.transitionTo (ct-ui-router-extras.js:1733)
at Object.$state.transitionTo (ct-ui-router-extras.js:1200)
at angular-ui-router.js:4143
at angular.js:18953
at completeOutstandingRequest (angular.js:5824)
at angular.js:6100
The angular version is 1.5.3.
If I use the old versions of ui-router 0.2.13 and ui-router-extras 0.0.14 everything works fine.

same here

We have the same issue with ui-router to 0.2.18 and ui-router-extras 0.1.2. However, when attempting to recreate the issue in a plunkr I can't get it to fail (http://plnkr.co/edit/yVulhiYUn5cEX2MyRuMo)

Hi Guys, i get the following error when trying to enable debugmode via
(function() {
  'use strict';
   angular.module('app.module', [])
      .config(routerConfig);

  /** @ngInject */
  function routerConfig($stateProvider,$stickyStateProvider) {
    $stickyStateProvider.enableDebug(true);
    $stateProvider
      .state('app.parent.child', {
....

    angular.js:13550 TypeError: Cannot read property 'self' of undefined
    at debugViewsAfterSuccess (ct-ui-router-extras.js:1253)
    at transitionSuccess (ct-ui-router-extras.js:1199)
    at processQueue (angular.js:15961)
    at angular.js:15977
    at Scope.$eval (angular.js:17229)
    at Scope.$digest (angular.js:17045)
    at Scope.$apply (angular.js:17337)
    at angular.js:19166
    at completeOutstandingRequest (angular.js:5869)
    at angular.js:6145

angular#1.5.5
angular-ui-router#0.2.18
ui-router-extras#0.1.2
any ideas?

Same issue.
angular#1.2.28
ui-router#0.2.16
ui-router-extras#0.1.2


ui: decrease brightness of placeholder in light theme

It feels that the placeholders in light mode are little bit too bright. On some screens it is hard to tell the difference from the background. Do you think it would be an improvement if they were a little darker?
📸 Before

📸 After

Just for reference, this would be the original Bootstrap style (applying currentColor):

its ok, go a little darker, but not that dark as in the last screenshot. a spinner per block would also help to visualize that something is loading

its ok, go a little darker, but not that dark as in the last screenshot. a spinner per block would also help to visualize that something is loading

Would you approve the PR if you are happy with the changes? :orange_heart:


SSL certificate have expired and Torch API outdated

There are some issues with the load_state_dict_from_url function.

the current import won't work for torch 2.0. The API has evolved and the function is now within the torch.hub module. (line 3 of iresnet.py should be changed)

With this change being done, an SSL certificate error will still be risen. This is due to outdated certificates. Luckily, a temporary fix can be done by changing the model URLs , i.e. switching the https within the URLs to http.

Hello, but it still cannot be found: urllib.error.HTTPError: HTTP Error 404: Not Found.
Regarding the iresnet34 model, the URL you provided (http://sota.nizhib.ai/pytorch-insightface/iresnet34-5b0d0e90.pth) appears to be invalid or the file may have been moved or deleted. Please help me.

Seems that the urls are not valid anymore. I have collected the weights stored in my machine cache and made them available at these urls  :
model_urls = {
'iresnet34': 'https://cdn.matix-media.net/dd/09944308',
'iresnet50': 'https://cdn.matix-media.net/dd/6fd38627',
'iresnet100': 'https://cdn.matix-media.net/dd/15963a78',
}
you can change the corresponding lines in  iresnet.py file and it should work. Normally the weights should be correct but don't hesitate to proceed with some tests to check that the resulting models have satisfying performances (I have only checked that no exceptions are raised). In particular, while the resnet34 and resnet50 are coming directly from my cache, I didn't have resnet100 weights, so I had to convert the corresponding weights from the insightface mxnet model , so if you aim to use it, you would likely want to make some tests to see if everything is allright.

Dear nizhib,
I hope this email finds you well. After implementing the changes you suggested, I encountered an issue related to model state dictionary loading. I'm hoping you can provide some guidance on how to address this.
Here's the traceback of the error I received:
Traceback (most recent call last):   File "/media/gq/9AE4359D52457624/code/AdaTrans-master/training/train.py", line 72, in <module>     ID_LOSS = IDLoss(crop=True, backbone='r34').cuda()   File "/media/gq/9AE4359D52457624/code/AdaTrans-master/models/ops/id_loss.py", line 13, in init     self.facenet = iresnet34(pretrained=True)   File "/media/gq/9AE4359D52457624/code/AdaTrans-master/models/ops/insightface.py", line 362, in iresnet34     **kwargs)   File "/media/gq/9AE4359D52457624/code/AdaTrans-master/models/ops/insightface.py", line 356, in _iresnet     model.load_state_dict(state_dict)   File "/home/gq/anaconda3/envs/stylegan/lib/python3.7/site-packages/torch/nn/modules/module.py", line 1605, in load_state_dict     self.class.name, "\n\t".join(error_msgs))) RuntimeError: Error(s) in loading state_dict for IResNet: 	Missing key(s) in state_dict: "prelu.weight", "layer1.0.prelu.weight", "layer1.0.bn3.weight", "layer1.0.bn3.bias", "layer1.0.bn3.running_mean", "layer1.0.bn3.running_var", "layer1.0.downsample.0.weight", "layer1.0.downsample.1.weight", "layer1.0.downsample.1.bias", "layer1.0.downsample.1.running_mean", "layer1.0.downsample.1.running_var", "layer1.1.prelu.weight", "layer1.1.bn3.weight", "layer1.1.bn3.bias", "layer1.1.bn3.running_mean", "layer1.1.bn3.running_var", "layer1.2.prelu.weight", "layer1.2.bn3.weight", "layer1.2.bn3.bias", "layer1.2.bn3.running_mean", "layer1.2.bn3.running_var", "layer2.0.prelu.weight", "layer2.0.bn3.weight", "layer2.0.bn3.bias", "layer2.0.bn3.running_mean", "layer2.0.bn3.running_var", "layer2.1.prelu.weight", "layer2.1.bn3.weight", "layer2.1.bn3.bias", "layer2.1.bn3.running_mean", "layer2.1.bn3.running_var", "layer2.2.prelu.weight", "layer2.2.bn3.weight", "layer2.2.bn3.bias", "layer2.2.bn3.running_mean", "layer2.2.bn3.running_var", "layer2.3.prelu.weight", "layer2.3.bn3.weight", "layer2.3.bn3.bias", "layer2.3.bn3.running_mean", "layer2.3.bn3.running_var", "layer3.0.prelu.weight", "layer3.0.bn3.weight", "layer3.0.bn3.bias", "layer3.0.bn3.running_mean", "layer3.0.bn3.running_var", "layer3.1.prelu.weight", "layer3.1.bn3.weight", "layer3.1.bn3.bias", "layer3.1.bn3.running_mean", "layer3.1.bn3.running_var", "layer3.2.prelu.weight", "layer3.2.bn3.weight", "layer3.2.bn3.bias", "layer3.2.bn3.running_mean", "layer3.2.bn3.running_var", "layer3.3.prelu.weight", "layer3.3.bn3.weight", "layer3.3.bn3.bias", "layer3.3.bn3.running_mean", "layer3.3.bn3.running_var", "layer3.4.prelu.weight", "layer3.4.bn3.weight", "layer3.4.bn3.bias", "layer3.4.bn3.running_mean", "layer3.4.bn3.running_var", "layer3.5.prelu.weight", "layer3.5.bn3.weight", "layer3.5.bn3.bias", "layer3.5.bn3.running_mean", "layer3.5.bn3.running_var", "layer4.0.prelu.weight", "layer4.0.bn3.weight", "layer4.0.bn3.bias", "layer4.0.bn3.running_mean", "layer4.0.bn3.running_var", "layer4.1.prelu.weight", "layer4.1.bn3.weight", "layer4.1.bn3.bias", "layer4.1.bn3.running_mean", "layer4.1.bn3.running_var", "layer4.2.prelu.weight", "layer4.2.bn3.weight", "layer4.2.bn3.bias", "layer4.2.bn3.running_mean", "layer4.2.bn3.running_var", "bn2.weight", "bn2.bias", "bn2.running_mean", "bn2.running_var", "features.weight", "features.bias", "features.running_mean", "features.running_var".  	size mismatch for conv1.weight: copying a param with shape torch.Size([64, 3, 7, 7]) from checkpoint, the shape in current model is torch.Size([64, 3, 3, 3]). 	size mismatch for layer2.0.bn1.weight: copying a param with shape torch.Size([128]) from checkpoint, the shape in current model is torch.Size([64]). 	size mismatch for layer2.0.bn1.bias: copying a param with shape torch.Size([128]) from checkpoint, the shape in current model is torch.Size([64]). 	size mismatch for layer2.0.bn1.running_mean: copying a param with shape torch.Size([128]) from checkpoint, the shape in current model is torch.Size([64]). 	size mismatch for layer2.0.bn1.running_var: copying a param with shape torch.Size([128]) from checkpoint, the shape in current model is torch.Size([64]). 	size mismatch for layer3.0.bn1.weight: copying a param with shape torch.Size([256]) from checkpoint, the shape in current model is torch.Size([128]). 	size mismatch for layer3.0.bn1.bias: copying a param with shape torch.Size([256]) from checkpoint, the shape in current model is torch.Size([128]). 	size mismatch for layer3.0.bn1.running_mean: copying a param with shape torch.Size([256]) from checkpoint, the shape in current model is torch.Size([128]). 	size mismatch for layer3.0.bn1.running_var: copying a param with shape torch.Size([256]) from checkpoint, the shape in current model is torch.Size([128]). 	size mismatch for layer4.0.bn1.weight: copying a param with shape torch.Size([512]) from checkpoint, the shape in current model is torch.Size([256]). 	size mismatch for layer4.0.bn1.bias: copying a param with shape torch.Size([512]) from checkpoint, the shape in current model is torch.Size([256]). 	size mismatch for layer4.0.bn1.running_mean: copying a param with shape torch.Size([512]) from checkpoint, the shape in current model is torch.Size([256]). 	size mismatch for layer4.0.bn1.running_var: copying a param with shape torch.Size([512]) from checkpoint, the shape in current model is torch.Size([256]). 	size mismatch for fc.weight: copying a param with shape torch.Size([1000, 512]) from checkpoint, the shape in current model is torch.Size([512, 25088]). 	size mismatch for fc.bias: copying a param with shape torch.Size([1000]) from checkpoint, the shape in current model is torch.Size([512]).
The error suggests there are missing keys in the state dictionary and size mismatches for certain parameters. I've attached the detailed list of discrepancies for your reference.
I'd greatly appreciate any insights or suggestions you might have to resolve this issue.
Thank you in advance for your time and assistance.
Best regards,
Qi Guo
632922175
@.***
Original Email
Sender:"afm215"< @.*** >;
Sent Time:2023/9/4 20:41
To:"nizhib/pytorch-insightface"< @.*** >;
Cc recipient:"guoqi0531"< @.*** >;"Comment"< @.*** >;
Subject:Re: [nizhib/pytorch-insightface] SSL certificate have expired andTorch API outdated  (Issue #11)
Seems that the urls are not valid anymore. I have collected the weights stored in my machine cache and made them available at these urls  :
model_urls = {
'iresnet34': 'https://cdn.matix-media.net/dd/09944308',
'iresnet50': 'https://cdn.matix-media.net/dd/6fd38627',
'iresnet100': 'https://cdn.matix-media.net/dd/15963a78',
}
you can change the corresponding lines in  iresnet.py file and it should work. Normally the weights should be correct but don't hesitate to proceed with some tests to check that the resulting models have satisfying performances (I have only checked that no exceptions are raised). In particular, while the resnet34 and resnet50 are coming directly from my cache, I didn't have resnet100 weights, so I had to convert the corresponding weights from the insightface mxnet model , so if you aim to use it, you would likely want to make some tests to see if everything is allright.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>

Hi Qi Guo,
Unfortunately, I am not nizhib, the author of this repository. It would have certainly made things easier...
I indeed have the same issue with Resnet 34, my apologies for not realizing it earlier. I have searched some workarounds but I could not succeed in making it work. It seems that the weights initially provided are not coming from the right model's architecture, and the original mxnet weights from insightface are nowhere to be found. The files might be under this link https://pan.baidu.com/s/1jKahEXw, but as a French person, I cannot download the files nor see the content...
I suggest you use resnet50 or resnet 100 which are running correctly. You can also use the onnx version of resnet 34 provided by insightface, which means not using this library.
All my apologies for not being able to solve this specific issue.
Best regards,
Alexandre

Dear Alexandre,
I'm very sorry for getting your name wrong. Thank you for your help!
Best regards,
Qi Guo
632922175
@.***
Original Email
Sender:"afm215"< @.*** >;
Sent Time:2023/9/5 19:45
To:"nizhib/pytorch-insightface"< @.*** >;
Cc recipient:"guoqi0531"< @.*** >;"Comment"< @.*** >;
Subject:Re: [nizhib/pytorch-insightface] SSL certificate have expired andTorch API outdated  (Issue #11)
Hi Qi Guo,
Unfortunately, I am not nizhib, the author of this repository. It would have certainly made things easier...
I indeed have the same issue with Resnet 34, my apologies for not realizing it earlier. I have searched some workarounds but I could not succeed in making it work. It seems that the weights initially provided are not coming from the right model's architecture, and the original mxnet weights from insightface are nowhere to be found. The files might be under this link https://pan.baidu.com/s/1jKahEXw, but as a French person, I cannot download the files nor see the content...
I suggest you use resnet50 or resnet 100 which are running correctly. You can also use the onnx version of resnet 34 provided by insightface, which means not using this library.
All my apologies for not being able to solve this specific issue.
Best regards,
Alexandre
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>


feat: eventshub sender can send to resources in other namespaces

Changes

Add a new k8s NamespacedAddress function to return an address in a different namespace than env
Add some eventshub options to send to resources in other namespaces

Release Note

Eventshub senders can deliver to resources in other namespaces

/cc @creydr @pierDipi @yijie-04
This should help with fixing the cross namespace e2e test PR in eventing core

/cc @pierDipi

/lgtm


AdoptOpenJDK Images are deprecated and we need to convert to Eclipse …

…builds #2814
Signed-off-by: Paul Bastide<EMAIL_ADDRESS>

Correct, unofficial ubi images were added as a stop gap until they can be added to RedHat's container registry. I'm not yet sure if we plan to maintain them once RH ones are there.

Thanks for the feedback @AdamBrousseau we'll definitely be watching


Clean up copyright name from title

Allow Copyright holder to vary from site title

I can see this being useful.


feat(@schematics/angular): Add directive and component selector rules

Here is the initial implementation and fix of https://github.com/angular/devkit/issues/570
Some questions:

When i add the schematics/angular/application/files/root/tslint.json, the workspace tslint file is not copied when i run ng new App, only the extending tslint exists in the created application. Is it not possible to create two files with the same name in different directories or am i missing something?
The LibraryOptions don't have a property for prefix, so i just chose lib for now. Should i add a prefix property and use it?
Should i add tests somewhere?

CC @filipesilva

@Brocco could you have a look please? Mike really is the authority on these things so I'd defer to him.

@Brocco I made all the changes.
Only the problem 1 persists and i don't really know what i can do.
As soon as i add schematics/angular/application/files/root/tslint.json, the schematics/angular/workspace/files/tslint.json isn't copied any more to a new angular project. If i rename the schematics/angular/application/files/root/tslint.json to tslint2.json, the workspace file is copied again. Any idea what the problem could be?

@chrste90 now that you mention it again, I think I ran into a similar problem in the library schematics...
https://github.com/angular/devkit/blob/master/packages/schematics/angular/library/index.ts#L181-L190
Having moved files with the same name should work, but is bugged and does not. The workaround is to have a template folder named __something__ with the problematic file there, passing the something var to the schematics. Schematics will replace that folder name with the path in the variable.
When I did that I removed the move in favor of using the template folder but I think it is more correct to leave it in, and only add the template folder for the problematic file.

Thanks @filipesilva
I made the changes and it seems that everything is working now.
So i think the changes are ready to review.

Also another thing (maybe you know already):
When i run the tests locally on my macbook, one test fails:
1) NodeJsSyncHost can watch
  Message:
    Expected 0 to be 3.
  Stack:
    Error: Expected 0 to be 3.
        at Promise.resolve.then.then.then.then.then.then.then.then (/Users/chris/Desktop/devkit/packages/angular_devkit/core/node/file:/Users/chris/Desktop/devkit/packages/angular_devkit/core/node/host_spec.ts:101:34)
        at <anonymous>

@chrste90 yeah that test is flaky on some environments. Not too sure why myself, but it is known.


isolate use of cl_gui_frontend_services to the /ui/ package

isolate use of cl_gui_frontend_services to the /ui/ package
@ThomasPloski

@ThomasPloski regarding the call to gui frontend services from the objects super class

would it be okay to have the super class call a method in the class from https://github.com/larshp/abapGit/pull/2516, code would not be perfectly separated, but it could be possible to inject a zif_frontend_service class without calls to cl_gui_frontend_services

todo:

it needs to be "hidden" behind a factory method, that way, a mock can be injected

it needs to be "hidden" behind a factory method, that way, a mock can be injected

@g-back did https://github.com/abapGit/abapGit/pull/5046 also solve this issue?

No, local types of class zcl_abapgit_transport_mass still contains direct references to it. Will decouple these some time this week.


Kanban Board Project

Github project
link
https://github.com/users/storres20/projects/2
Member's quantity: 02

storres20
YKerroum

Hi  Team
Your project is complete!  There is nothing else to say other than... it's time to merge it :shipit:
Congratulations! 🎉 :clap: :clap: :100:

Optional suggestions

[ ] Kindly Check the comments under the review._
Every comment with the [OPTIONAL] prefix is not crucial enough to stop the approval of this PR. However, I strongly recommend you to take them into account as they can make your code better.

Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.

_As described in the Code reviews limits policy  you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.


Recipe testing and output comparison for release 2.9.0

This issue documents recipe testing for the v2.9.0 release
Installation and environment
$ git clone git@github.com:ESMValGroup/ESMValTool
$ cd ~/ESMValTool
$ git checkout v2.9.x
$ mamba env create -n esmvaltool-v2.9.x-2023-06-20 -f environment.yml
$ conda activate esmvaltool-v2.9.x-2023-06-20
$ pip install .
$ cd ..
$ git clone git@github.com:scitools/iris
$ cd iris
$ git checkout v3.6.x
$ pip install .

Environment file
environment.txt
Config user file
All options at the default for Levante except search_esgf: when_missing.

Overview of the results
Webpage: https://esmvaltool.dkrz.de/shared/esmvaltool/v2.9.0rc1/debug.html
Successful: 135 out of 153
Recipes that failed with DiagnosticError

recipe_carvalhais14nat.yml
recipe_eady_growth_rate.yml
recipe_julia.yml (to be expected because Julia was not installed for the test)
recipe_rainfarm.yml (to be expected because Julia was not installed for the test)
recipe_seaice_drift.yml
recipe_shapeselect.yml

Recipes that failed of Missing Data

recipe_check_obs.yml https://github.com/ESMValGroup/ESMValCore/issues/1388

Recipes that failed of other reasons

recipe_climate_change_hotspot.yml
recipe_daily_era5.yml
recipe_lauer22jclim_fig3-4_zonal.yml
recipe_lauer22jclim_fig5_lifrac.yml
recipe_mpqb_xch4.yml
recipe_schlund20jgr_gpp_abs_rcp85.yml
recipe_schlund20jgr_gpp_change_1pct.yml
recipe_schlund20jgr_gpp_change_rcp85.yml
recipe_sea_surface_salinity.yml
recipe_thermodyn_diagtool.yml
recipe_wenzel14jgr.yml

And here are the results of the comparison with the results for v2.8.0. 61 recipes have different results, which seems like a lot. I will have a preliminary look at them and report some results here later.

61 is not a lot - it's in fact bang-on, I think I had some 50-60 myself for 2.7 and Remi had a bucketload too; Matplotlib changed so expect plots differing only. Great work, bud :beers:

well, rainfarm died bc you didn't install Julia; where are @schlunma 's schlund*gpp ones that failed?

Both lauer22 didn't actually exit - they seem to have been killed by SLRM mid-analysis, either node failure or memory-related?

Great work with this recipe testing, @bouweandela!

Both lauer22 didn't actually exit - they seem to have been killed by SLRM mid-analysis, either node failure or memory-related? Same with mpqb and sea surface salinity = gonna update your list there

Indeed, we have 7 recipes (last section of this https://github.com/ESMValGroup/ESMValTool/issues/3239#issuecomment-1602719758) who couldn't be run due to time/memory limitations even if those could be run in the previous release. Possible reasons:

Issues on Levante (filesystem, default slurm settings silently changed during maintenance (happened already), ...)
Iris issue with lazy aggregation (@schlunma's fix not yet merged)

And 4-5 diagnostic failures that we should try to fix together next week 🍻

so @ledm has just reported to CEDA/JASMIN that a bunch of his runs get kicked out of SLURM on basis of resources but obv nothing out of the ordinary (ie mem consumption order 2GB) - he's still to confirm that he's using the latest Core, but the symptoms look identical to these recipes here that didn't exit, but rather, were kicked out by the scheduler

carvalhais looks like a proper bug in iris - cube.core_data() when data is just a point, I'll have a closer look

lemme look into this now :portugal:

OK @ledm is running with latest:
esmvalcore                2.9.0.dev28+g179312e41          pypi_0    pypi
esmvaltool                2.9.0.dev32+ge17d1c8f6          pypi_0    pypi

and is seeing exacly what Bouwe saw for lauer22 etc - bizarre kickouts

Okay, glad it's not just me. Though I think that some of my recent issues originated with https://github.com/ESMValGroup/ESMValTool/issues/3240 and
https://github.com/ESMValGroup/ESMValCore/pull/2110

The file that get kills immediately every time on jasmin for me is: https://github.com/ESMValGroup/ESMValTool/blob/09c18280751323354b4f0aa1f0ef6e260589326d/esmvaltool/recipes/ai_mpa/recipe_ocean_ai_mpa_po4.yml

@bouweandela carvalhais goes through fine with iris=3.6.0 (deployed) so I am 99.9% there's an issue with iris=3.6.1 you using from source. Use this script and see if you catch the issue - it's clearly not liking realizing scalar cube data (this mimicks what's the hap in the bit of code that dies):
import iris
import iris.cube

def make_cube():
    """Make a scalar cube and save it."""
    cube1 = iris.cube.Cube(2.22, var_name='co2', units='J')
    cube2 = iris.cube.Cube(1e20, var_name='co2', units='J')
    cube = cube1 / cube2
    iris.save(cube, "~/scalar_cubey.nc")

def load_lazily(cube):
    """Load lazy data from scalar cube."""
    datum = cube.core_data()
    return datum

def main():
    """Run the show."""
    make_cube()
    cube = iris.load_cube("~/scalar_cubey.nc")
    lazy_data = load_lazily(cube)
    print(lazy_data)
    print(float(lazy_data))

if __name__ == "__main__":
    main()

I'm still struggling with this. I've changed the preprocessing stage of the recipe (removing custom order), I've tried a few older versions of esmvalcore (2.8.0, 2.8.1, and 2.8.1rc1)? No matter what, I'm still getting the "killed" message after 0.3GB of RAM usage.

@ledm Would it be OK to open a separate issue for your recipe? This issue is about testing recipes for the upcoming v2.9 release. Re the recipes listed above that are running out of memory: this is probably due to scitools/iris#5338.

Okay, I'm able to recreate the error! It looks like this may be something else? It seems like it's a extract_levels preprocessor bug/
Running interactively on jasmin:
import iris
from esmvalcore.preprocessor._regrid import extract_levels

fn = "/badc/cmip6/data/CMIP6/CMIP/MOHC/UKESM1-0-LL/historical/r2i1p1f2/Omon/po4/gn/v20190708/po4_Omon_UKESM1-0-LL_historical_r2i1p1f2_gn_200001-201412.nc"

cube= iris.load_cube(fn)
c2 = extract_levels(cube, scheme='nearest', levels = [0.1 ,])

Results in Killed, I'm on 3 for 3 times now, so there's that! I'll try other schemes and see if they are more resilient.
Let me know if this needs to go into it's own issue page!
Hope you all have lots of fun this week in Sweden!

Looks like stratify is one of @bjlittle's projects? Any idea what could be causing this bug, Bill?

Ooof, turns out stratify is a mix of C and python, and I'm not capable of debugging that!
Think my backup solution is to go back to this solution.
https://github.com/ESMValGroup/ESMValCore/issues/1039

Let me know if this needs to go into it's own issue page!

Yes, please

Done: https://github.com/ESMValGroup/ESMValTool/issues/3244

I ran the comparison tool again because there was an issue with it. NaN values did not compare as equal in arrays, so the tool flagged to many recipe runs as changed. The new comparison results are available
here. Now the number of recipes runs that are different from v2.8.0 is 61. I will add a more detailed comparison once it is ready.

Detailed comparison, including all kinds of information on what exactly changed in the output is available
here. Please scroll through the document to find your recipe. The indentation indicates what recipe/variable/coordinate the information applies to.

@bouweandela carvalhais goes through fine with iris=3.6.0 (deployed) and 3.6.x (pip-installed) - that's either a fluke or something related to distributed (which I did not run with); same dask as yours too; try rerunning the recipe, methinks

@bouweandela have you rerun this recipe to have it finish OK, by any chance?

@bouweandela carvalhais goes through fine with iris=3.6.0 (deployed) and 3.6.x (pip-installed) - that's either a fluke or something related to distributed (which I did not run with); same dask as yours too; try rerunning the recipe, methinks

@bouweandela have you rerun this recipe to have it finish OK, by any chance?

Just did with iris 3.6.1 and I'm still getting the same error.

By increasing the resources (from interactivate to compute partition, or from compute to compute 512G), I was able to run successfully a few more recipes: recipe_climate_change_hotspot, recipe_mpqb_xch4, recipe_sea_surface_salinity, recipe_thermodyn_diagtool. But these recipes have longer runtimes and memory consumption than found during v2.8 release (factor >2 ). I could run these recipes successfully before and after the latest iris PR was merged without any differences in terms of performance.

By increasing the resources (from interactivate to compute partition, or from compute to compute 512G), I was able to run successfully a few more recipes: recipe_climate_change_hotspot, recipe_mpqb_xch4, recipe_sea_surface_salinity, recipe_thermodyn_diagtool. But these recipes have longer runtimes and memory consumption than found during v2.8 release (factor >2 ). I could run these recipes successfully before and after the latest iris PR was merged without any differences in terms of performance.

I re-run some of these recipes with a distributed scheduler using the following .esmvaltool/dask.yml file:
cluster:
  type: distributed.LocalCluster
  n_workers: 8
  threads_per_worker: 4
  memory_limit: 32 GiB

(no idea how optimal those settings are).

[x] recipe_thermodyn_diagtool: ran with pretty-much the exact same ressources as during the v2.8.0 testing (1:30:00 hr, ~30GiB memory). Note that >90% of the run time of that recipe is taken up by the diagnostic, so I wouldn't expect a lot of improvement with the distributed scheduler (assuming the diagnostic is not optimized).
[ ] recipe_climate_change_hotspot: failed, see below.
[ ] recipe_mpqb_xch4: failed, see below.
[ ] recipe_sea_surface_salinity: failed, see below.
[x] recipe_daily_era5.yml: ran successfully in 18:00 min with 161 GiB of memory, but had a lot of warnings about gc.collect() took 1.933s. This is usually a sign that some tasks handle too many Python objects at the same time. Rechunking the work into smaller tasks might help. and Worker process still alive after 3.1999995422363288 seconds, killing. This is certainly not optimal (for v2.8.0, the recipe ran in 12 min and 31 GiB memory usage), but at least it runs. I am pretty sure this could be optimized with smarter dask settings.

The runs that failed exited with errors like concurrent.futures._base.CancelledError: compute_and_return_warnings-3ee342d0-affa-4e69-9f2a-09fc9e7cbe92 during the save step. I also see a lot of warnings like Sending large graph of size ... or full garbage collections took XX% CPU time recently in these runs, so my guess is that some of the preprocessors used in these recipes are not fully lazy yet.
Bottom line: I think for the fully lazy preprocessors we can achieve a similar (hopefully a much better with smarter configuration) run time and memory usage when using dask distributed, but the non-lazy preprocessors crash with that.

I tested recipe_daily_era5.yml with both iris 3.4 and 3.6.1 without configuring Dask Distributed and it runs fine with iris 3.4 and it runs out of memory with 3.6.1.

carvalhais goes through with dask=2023.3.0 but fails a couple lines down the diag at plotting:
Traceback (most recent call last):
  File "/home/b/b382109/ESMValTool/esmvaltool/diag_scripts/land_carbon_cycle/diag_global_turnover.py", line 819, in <module>
    main(config)
  File "/home/b/b382109/ESMValTool/esmvaltool/diag_scripts/land_carbon_cycle/diag_global_turnover.py", line 757, in main
    _plot_single_map(plot_path_mod, tau_ctotal,
  File "/home/b/b382109/ESMValTool/esmvaltool/diag_scripts/land_carbon_cycle/diag_global_turnover.py", line 654, in _plot_single_map
    plt.imshow(_get_data_to_plot(_dat.data),
  File "/home/b/b382109/miniconda3/envs/tool-latest/lib/python3.11/site-packages/matplotlib/pyplot.py", line 2695, in imshow
    __ret = gca().imshow(
            ^^^^^^^^^^^^^
  File "/home/b/b382109/miniconda3/envs/tool-latest/lib/python3.11/site-packages/cartopy/mpl/geoaxes.py", line 318, in wrapper
    return func(self, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/b/b382109/miniconda3/envs/tool-latest/lib/python3.11/site-packages/cartopy/mpl/geoaxes.py", line 1331, in imshow
    img, extent = warp_array(img,
                  ^^^^^^^^^^^^^^^
  File "/home/b/b382109/miniconda3/envs/tool-latest/lib/python3.11/site-packages/cartopy/img_transform.py", line 192, in warp_array
    array = regrid(array, source_native_xy[0], source_native_xy[1],
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/b/b382109/miniconda3/envs/tool-latest/lib/python3.11/site-packages/cartopy/img_transform.py", line 278, in regrid
    _, indices = kdtree.query(target_xyz, k=1)
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "_ckdtree.pyx", line 795, in scipy.spatial._ckdtree.cKDTree.query
ValueError: 'x' must be finite, check for nan or inf values

so cartopy is breaking it now

this is signaled nd raised here https://github.com/SciTools/cartopy/issues/2199 and it looks like they already have a PR to fix it :party

Summary of relevant differences
Recipes where the plots are identical, but (some) data differs

recipe_albedolandcover.yml
recipe_bock20jgr_fig_1-4.yml
recipe_bock20jgr_fig_6-7.yml
recipe_bock20jgr_fig_8-10.yml
recipe_clouds_bias.yml
recipe_clouds_ipcc.yml
recipe_extract_shape.yml
recipe_flato13ipcc_figure_98.yml
recipe_flato13ipcc_figures_92_95.yml
recipe_hydro_forcing.yml
recipe_ipccwg1ar6ch3_atmosphere.yml
recipe_ipccwg1ar6ch3_fig_3_43.yml
recipe_lauer22jclim_fig1_clim.yml
recipe_lauer22jclim_fig1_clim_amip.yml
recipe_lauer22jclim_fig6_interannual.yml
recipe_lauer22jclim_fig7_seas.yml
recipe_lauer22jclim_fig8_dyn.yml

Recipes where (some) plots differ, but not the data

recipe_ecs_constraints.yml

Plots and data are different

recipe_extreme_events.yml
recipe_flato13ipcc_figure_96.yml
recipe_flato13ipcc_figures_938_941_cmip3.yml
recipe_flato13ipcc_figures_938_941_cmip6.yml
recipe_ipccwg1ar6ch3_fig_3_42_b.yml
recipe_kcs.yml

Checked all recipes with names up to and including recipe_monitor.yml, recipes later in the alphabet not yet checked.

Out of interest, what was the last ESMValTool version that uses iris 3.4?

For the release of v2.8.0, we used iris-3.4.1 to test all recipes

@bouweandela  thanks for the list! The plot from recipe_spei.yml only changed the colour (because R chooses different ones every time, I should set fixed ones there but I guess there is not enough time to change that before the release now).
For recipe_flato13ipcc_figures_938_941_cmip3.yml, recipe_flato13ipcc_figures_938_941_cmip6.yml and recipe_weigel21gmd_figures_13_16.yml there is a somewhat different setting of the fx files now (see #3215), which explains the changed values.

Thanks for checking @katjaweigel! I was planning to make the release on Thursday next week, so if you still want to fix the plotting in recipe_spei.yml before that time you can do it.

Regarding the list of "Recipes that failed because they used too much memory" (in this https://github.com/ESMValGroup/ESMValTool/issues/3239#issuecomment-1602719758), I was able to run them successfully on Levante, except one, by increasing the computational resources required (see #3216). This does not really tell us where the problems come from but will nevertheless help the RM who gets less failures.
The biggest increase of resources required is for the 2 cloud recipes. Using 1024 GB compute nodes and max_parallel_tasks=3, I was able to run recipe_lauer22jclim_fig5_lifrac (Time for running the recipe was: 5:20:57.188249, Maximum memory used (estimate): 881.6 GB) but not recipe_lauer22jclim_fig3-4_zonal (ends with 1 tasks running, 1 tasks waiting for ancestors, 14/16 done after the 8h limit). FYI, @axel-lauer.

We did another round of test runs. The results are available here: https://esmvaltool.dkrz.de/shared/esmvaltool/v2.9.0/
Here is the environment.yml and here are the comparison results and the detailed comparison results. The comparison was done with the previous round of testing for this release. Because of disk space limitations, I had to remove the v2.9.0rc1 results from the webpage, but the results are still available in /work/bd0854/b381141/esmvaltool_output/esmvaltool-v2.9.x-2023-06-20 for those who have access to Levante.
All recipes ran successfully except for:

recipe_carvalhais14nat.yml TODO: create issue
recipe_seaice_drift.yml #3243
recipe_shapeselect.yml #3242
recipe_check_obs.yml https://github.com/ESMValGroup/ESMValCore/issues/1388
recipe_lauer22jclim_fig3-4_zonal.yml ran out of memory. The advice is the use iris 3.4.1 when running this recipe https://github.com/ESMValGroup/ESMValTool/issues/3239#issuecomment-1611343989

I think we can safely close this now that we have #3287 - @bouweandela since you put so much effort in it, I'd feel bad closing it myself, will you do the service pls :medal_military:

Hi, I've been away on vacation and didn't  see the mention to check differing plots before now. To me it looks like only consecutive dry days have changed, and I wondered if it's just that the version of consecutive dry days has changed from the one that caps the number at the end of a year to the one that runs over multiple years when the longest dry period extends across calendar years. That would explain the plot discrepancy, they weird end of the original plot (in 2.8), and would anyway be the more sensible thing to have plotted this way. I.e. I think that this is an improvement, then.


scope the projection selection properly when using the Mutation Conventions

added some context data to get the MutationPayload data field name
used that field name to fetch the proper selection to pass down to the projection executor
wrote some projection integration tests to verify this works as expected

Closes #5300

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

This looks already good ... thanks for contributing... I will have a look at it later tonight.

@hahn-kev I did a couple more refinements ... but I think its good now.

I created a new preview of 13.5 ... you can use it with the newest preview.

Tested it out and it works exactly how I expected. Looking forward to the full release. I'll try and use it and let you know if we find issues.


add README and LICENSE

📖

@BobrImperator let me know if you have any feedback as well – mainly interested in whether anything substantial is missing that should be in a README. There will be guides going into much more depth anyway.

It'd be awesome to include the commands and their explanation in generated project's README. Currently it only has a project's name.

Yes, that's to be done still

I think that the blueprint is missing a common place for starting other server dependencies. If I needed to create a background task, I'm forced to repeat the setup in both tests and the actual server.

I think that's something for a later release. There's quite some questions coming with that, e.g. what do you use as a persistent queue for a background tasks implementation.

Would it be OK to add the cli/ crate to .gitignore?

No since we want that to be checked in with the project. I understand you want to exclude it from your editor but I don't think adding it to .gitignore is the right way to achieve that.


pbr: Maybe fix weird dark artifacts in PBR

Looking at
https://github.com/Nadrin/PBR/blob/master/data/shaders/glsl/pbr_fs.glsl, this repo does PBR slightly differently. In general, the calculations are similar until they come to adding it to the color. This change ported from this renderer appears to help remove black artifacts.
Before

After

I'm going to merge this for 0.55. If we find a better solution, we should do that


Fix tab being blank for slow loading documents.

Task/Issue URL: https://app.asana.com/0/715106103902962/1206610402862961/f
Description

The change moves the hiding of the document to immediate rather than a timeout.
We also then change the address bar on onPageCommitVisible which also then shows the new document.

Steps to test this PR
Some details in: https://app.asana.com/0/72649045549333/1190194123689893
UI changes

Before
After

!(Upload before screenshot)
(Upload after screenshot)

#4390  👈
develop

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

Join @jonathanKingston and the rest of your teammates on  Graphite


undefined reference to `libusb_set_option'

Hi all,
I will try to compile the project on Windows 10 with MinGW-w64 without success.
The error is:
C:/stlink/src/sg.c:972: undefined reference to 'libusb_set_option'
My environement is:

Windows 10
texane/stlink 1.6.0 => This version requires the libusb-<IP_ADDRESS>z (downloaded manually)
MinGW-w64 i686-8.1.0-posix-dwarf-rt_v6-rev0

Can you help me?
Complete log of the compilation: log.txt
Thank you in advance.
Ju

Please try the develop branch instead. I am aware of fixes related to MinGW compilation since Release v1.6.0.

The mentinned error isn't displayed but the compilation failed.
log_w_develop_latest_commit_a09ef54.txt

I want to add a remark.
The last log indicates that I have already libusb in my system.
-- Found Libusb: C:/Windows/System32/libusb-1.0.dll
Sure this version is old.
What is your opinion about this.

@purjus74 I think the problem with libusb, that you download manually.
Please remove it. Clear all builds. And try one more time.

Just to give more details:
Before to use your project, my system had already a libusb instance.

If I let the batch mingw64-build.bat to download the libusb-<IP_ADDRESS>z, the extraction fails:
...
-- Could NOT find Libusb (missing: LIBUSB_INCLUDE_DIR)
-- downloading libusb 1.0.22

7-Zip 19.00 (x64) : Copyright (c) 1999-2018 Igor Pavlov : 2019-02-21

Scanning the drive for archives:
1 file, 2601 bytes (3 KiB)

Extracting archive: C:\stlink-develop\scripts\libusb-<IP_ADDRESS>z
ERROR: C:\stlink-develop\scripts\libusb-<IP_ADDRESS>z
C:\stlink-develop\scripts\libusb-<IP_ADDRESS>z
Open ERROR: Can not open the file as [7z] archive

ERRORS:
Is not archive
...

It seems that the archive is file is corrupted :(

@slyshykO: You are right, I did not notice at first that an external libusb library was present.

I think this behavior (error during libusb-<IP_ADDRESS>z downloading) is due to my compagny protection :(
This f*#! protection creates the wanted archive file but it contains an error html page !!!

But I'm not sure that is a problem to download before the good libusb archive and put it inside the build folder.
My first log illustrates that the mingw64-build.bat finds the archive, extracts it and uses it:
-- libusb archive already in build folder

7-Zip 19.00 (x64) : Copyright (c) 1999-2018 Igor Pavlov : 2019-02-21

Scanning the drive for archives:
1 file, 980895 bytes (958 KiB)

Extracting archive: C:\stlink\scripts\libusb-<IP_ADDRESS>z
--
Path = C:\stlink\scripts\libusb-<IP_ADDRESS>z
Type = 7z
Physical Size = 980895
Headers Size = 682
Method = LZMA2:23 BCJ
Solid = +
Blocks = 2

Everything is Ok

@purjus74: Does your whole compilation succeed now?
@slyshykO: I think we should add a note to the instructions on not to use external libusb packages when installing on windows, as this is not the first issue of its kind.

The problem is that windows have many options on how to install libusb, also many compilers with different ABI. That is why we should provide windows builds.

I just tried on other machine (without old libusb inside C:\Windows\System32) and it's work.
Therefore, the problem is due to other libusb version already stored and used by the others projects.

Thank you for your support and for your job ;)

Reopening this as documentation and related work remains outstanding...


Control speed of transition

I don't seem to find a way of controling the time the transition takes to complete/ the speed of the burger.
Is this really missing?

@Dan-GG Unfortunately that feature was never included. Many of them have very specific and intricate timelines, and adding the ability to customize the transition times is not a simple task considering the transitions are pure CSS.
For example, if you look at the source for one of the more complex animations like collapse, each part of the hamburger has very specific transition durations and delays, and they are different for when it goes from a hamburger to an X vs an X to a hamburger.

I found a rather simple way of working around the lack of this feature:
All you have to do is enclose within parentheses every time you state the speed or delay of anything and multiply it times $speed, which by default is 1. (0.5 = half the speed; 2 = twice the speed).
The final result is this:
/*example from .burger--emphatic*/
/*I also added transition and transform mixins for vendor prefixes*/
.burger-inner {
   @include transition(background-color (0.2s * $speed) (0.25s * $speed) ease-in);
}

I've implemented this feature in PR #73. My implementation (coincidentally) was similar to @Dan-GG's. Basically, it's just a linear scaling factor. By default, everything is based on 1s but if you simply scale ALL durations uniformly, it stays coordinated. See #73 for details! 😄


date-page-a-day-calendar displays day before in central time zone

I have used the date-page-a-day-calendar for some time and have not seen any issues. I had a user advise me that the date was displaying the day before, but I could not replicate this. When I remove the script date is correct in both time zones. On a whim I changed my timezone from Eastern to the users in Central. When I applied the script I was able to replicate the bug. The date reflects the day before. I do not see anything that stands out. The only places I found a "-1" in the code it was related to styling.
Can anyone replicate this, or see a way to fix it?
thanks

I created the issue!
https://github.com/SharePoint/sp-dev-docs/issues/9618


urlRoot does not work with parameters

Expected behavior

http://localhost:9876/hl?=en&id=34916909

Actual behavior

http://localhost:9876/hl?=en/?id=34916909

Enviroment Details

Karma version (output of karma --version): 0.13.22
Relevant part of your karma.config.js file: urlRoot: '/hl?=en'

Steps to reproduce the behaviour

Add a parameter to the urlRoot in your karma.config.js file
Launch a test
Now you can see that the URL parameter is not handled as parameter

according to the docs, urlRoot is treated as a path,


manually update downshift's internal state of input field

downshift 1.4.0:
node version: 7.4.0
yarn: 0.19.1

Relevant code or config
  onStateChange(selected, dsProps) {
    this.props.setInputAndSelectedType(dsProps.getInputProps().value, selected.type)
  },

Problem description:
Hi again. I'm using downshift for Instacart's main new search component and need to be able to replicate what we're currently doing, which is:
When a user highlights a suggested item (presses down), replace the input field with whatever is highlighted. This behavior can also be seen on google's search bar.
Right now, under downshifts actions, I don't see any exposed functions I can call to update downshifts internal state of the input field. Also, all the examples show that the input field is not being updated to correspond with the highlighted item.
So in the relevant code above, is there a way I can update downshift's internal state of the input field before setting this value in redux?
I understand that inputValue is a Control Prop and that my "child callback function" should be able to update this, but am still a bit unclear on how to do so.
Thanks for any help! :)
Suggested solution:
Expose function to update downshift's internal state of the input field.

Check out this example. Here's the code
If you'd like to clean up that example a bit and put it in a codesandbox then we could include it in the list on the README so folks will find it easier :)
Let me know if this doesn't solve your problem :)

Great, thank you. Yes, I'll definitely try to clean up this example and put in a codebox. Thanks for being so quick to respond, @kentcdodds! 👍


Categories broken

I upgraded my site to 0.20 and everything went fine, however all categories now return Sorry, we couldn't find any posts..
Had a look in the DB and the categories collection looks fine and all posts still contain the categories they're posted in.
Any ideas on what could be wrong here?

Hmm, I'm not quite sure what's going on here… Have you customized the site's code in any way?

Just some basic theme styling changes.
FWIW, this affects existing and new posts.
If you have pointers for how to debug, I'm happy to share or try whatever to figure it out.

Is this happening both locally and in production? How are you deploying? And can you share your code repo?

Yes, it happens both locally and in production.
I am using Meteor Up to deploy.
Since I was following the tips from the blog post to upgrade, I used the sample-project and modified that; I hope I didn't break something along the way, but I don't recall seeing anything remotely category related in it though.

I have the same issue on http://scope.hackbeat.org. It's deployed on heroku, with minimal styling
I added the posts first, then created categories, then edited the posts and saved with categories added.
The category pages returned no entries and "Sorry, we couldn't find any posts" Fx. at http://scope.hackbeat.org/category/demos
Not sure if it has any relation, but i noticed that setting the catogories first gave me fx. this link clicking in the sidebar http://scope.hackbeat.orgcategory/demos - until I added "/" to the site URL, like this "http://scope.hackbeat.org/" - it made the url look right, but still didn't solve the problem.

this is not broken, you have just to put the full domain name with the leading http://
in the settings so the categories show up
http://yourDomain.tld/

@capensisma I've had my site url specified properly with trailing slash for almost a year now, and categories worked as expected before the upgrade.

FWIW, I've dropped back to version 0.15.1 on my production site and am just mentioning that here in case anyone hits the link in my first comment and sees that the categories are indeed functioning as expected.
I still have a dev instance of the 0.20.4 version available if it is needed to help debug this issue.

@brianshumate @jespervega what happened is that the sample-project repo mistakenly had the wrong version (0.20 instead of 0.20.4) until a couple days ago. It'd be great to know if updating to 0.20.4 (meteor update locally) fixes the problem or not?

@SachaG great to know! I'll give it a try soon and report back. :)

@SachaG upgraded again to 0.20.4 and all is working as expected. Thanks!

Great! Sorry again about this issue, I'll be more careful about keeping everything up to date :)


fix is_secure switch

The argument coming back from kwargs.pop is a string, all non-empty strings evaluate to True in an boolean context (this also applies when using bool() )
is secure is now guaranteed to return a proper bool instead of a string

Release in version 0.2.4 . Thanks, David for your contribution.

Awesome, always happy to help. Any idea on when this will hit pip?
On Sat, 17 Sep 2016 21:33 Richard Huang<EMAIL_ADDRESS>wrote:

Release in version 0.2.4 . Thanks, David for your contribution.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/rickypc/robotframework-imaplibrary/pull/3#issuecomment-247801877,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AERDiIqrMLwoVTkcHdZOfs_fzCvBR9jOks5qrEB7gaJpZM4J9loo
.

It's already there :)
pip install -U robotframework-imaplibrary


Typer should reject functions doings side-effect on storage and transfers.

./tests/type-errors/no_side_effect_in_function1.arl
./tests/type-errors/no_side_effect_in_function2.arl

a new issue #252 has been created


Create file_create_edit_close.rb

Created a Ruby program that creates a new .txt file, writes to it, and then closes the file
File that is created is located in the directory that it is run in

Ran program multiple times with no errors thrown. Let me know if any changes need to be made.

Updated the file to allow for interactive prompts in the command line to show user input turned into the filename, and content of file created.

Hey @jpierce-coder
Thank you for your contribution 🚀

Of course, anytime. As I increase my skills in Ruby, I will be sure to add more. 🙂


Project TS

Context
Mosaic data is currently stored at the project level with subsequent AOIs of a given project inheriting the single mosaic type from their parent project. This has worked up until now as we have essentially only used the naip.latest mosaic for all projects.
Adding timeseries data complicates this model as it means that there is no relationship to be made between similiar AOIs that use mosaics with different timestamps. Although a user would be able to manually select mosaics that might overlap and compare them, a DB relationship wasn't possible.
This PR changes the way mosaic data is stored in the database and surfaced via the API. Mosaic data has been removed from the project data and is instead stored

Project - Just a container for a given Model ID
AOI - Contains Bound Data & Name
AOI_TimeFrame - Contains most of the data that AOI formerly did (classes, patches, etc) as well as a new mosaic ID & mosaic Timestamp field

Closes: https://github.com/developmentseed/pearl-backend/issues/36
cc/ @geohacker

@ingalls this is looking really great! thanks so much! One question I have is about mosaics (imagery source). I think we should have a table that registers mosaics which the frontend can list. And eventually the frontend will allow an interface to create them with the Planetary Computer API.
It can certainly be a separate PR but I do think currently it's unclear how we store mosaics.
cc @vgeorge

@geohacker should this be merged to a v2 branch?

I'm tempted to merge this to develop. Let me mull a bit


Add dev examples for images not loading and unconfiged ones

What this PR does / why we need it:

Special notes for your reviewer:
Release note:

The case for not loading images aka bad connection: https://5b703784c96592748e389ebe--syna-demo.netlify.com/dev/missing-images/
The case for unconfigured images: https://5b703784c96592748e389ebe--syna-demo.netlify.com/dev/unconfigured-images/
With this demo we can create a few issues and fix both cases to make them look good.

Fantastic. For missing images, should we display an error message or render it as is?

I would say for non configured images, render as is. There might be a specific reason for that and as long as it doesn't break the layout, that should be ok.

@stp-ip What about missing images? For non configured we mostly don't render the img tag altogether (logos and portfolio fragment require images so doesn't make sense to remove them, just make them better looking).

Missing images I think it maybe should fallback to sort of a blank placeholder aka keep the layout as if an image would be present. Such as an empty circle for member etc.


ARROW-274: Add NullableMapVector to support nullable maps

Aside, has there been any more discussion in drill of removing the NullableTYPEVector distinction (i.e. having just one container type per vector)?

@wesm For now, I'm fixing the gaps between the spec and the java implementation. Once that's done, we can refactor and remove unnecessary layers.

+1. The patch looks good to me. Thanks for the works.


how to refresh existing tokens???

i got an error message orig_iat field is required.
the settings is :
REST_FRAMEWORK = {     'DEFAULT_AUTHENTICATION_CLASSES': (         'rest_framework_jwt.authentication.JSONWebTokenAuthentication',         'rest_framework.authentication.SessionAuthentication',         'rest_framework.authentication.BasicAuthentication',     ), }

it is worked!!!! thanks a lot

How did you do it?

@SamsadSajid
first，the orig_iag is the token created time，this issue means the token we send to server don't have this parameter.
then we look the refresh source code， in rest_framework_jwt.serializers.py:
class RefreshJSONWebTokenSerializer(VerificationBaseSerializer):
    def validate(self, attrs):
        token = attrs['token']
        payload = self._check_payload(token=token)
       user = self._check_user(payload=payload)
       # Get and check 'orig_iat'
       orig_iat = payload.get('orig_iat')

       if orig_iat:
           # Verify expiration
           refresh_limit = api_settings.JWT_REFRESH_EXPIRATION_DELTA

           if isinstance(refresh_limit, timedelta):
               refresh_limit = (refresh_limit.days * 24 * 3600 +
                                refresh_limit.seconds)

           expiration_timestamp = orig_iat + int(refresh_limit)
           now_timestamp = timegm(datetime.utcnow().utctimetuple())

           if now_timestamp > expiration_timestamp:
               msg = _('Refresh has expired.')
               raise serializers.ValidationError(msg)
       else:
           msg = _('orig_iat field is required.')
           raise serializers.ValidationError(msg)

       new_payload = jwt_payload_handler(user)
       new_payload['orig_iat'] = orig_iat

       return {
           'token': jwt_encode_handler(new_payload),
           'user': user
       }

that's very clear :
     if orig_iag:
           xxxxxxxxxxxxxxx
     else:
            msg = _('orig_iat field is required.')
            raise serializers.ValidationError(msg)```
so, we should fix it?
because we through this method `jwt_payload_handler` to generate the `jwt-token`,
we must look the source code:

def jwt_payload_handler(user):
username_field = get_username_field()
username = get_username(user)
warnings.warn(
    'The following fields will be removed in the future: '
    '`email` and `user_id`. ',
    DeprecationWarning
)

payload = {
    'user_id': user.pk,
    'username': username,
    'exp': datetime.utcnow() + api_settings.JWT_EXPIRATION_DELTA
}
if hasattr(user, 'email'):
    payload['email'] = user.email
if isinstance(user.pk, uuid.UUID):
    payload['user_id'] = str(user.pk)

payload[username_field] = username

# Include original issued at time for a brand new token,
# to allow token refresh
if api_settings.JWT_ALLOW_REFRESH:
    payload['orig_iat'] = timegm(
        datetime.utcnow().utctimetuple()
    )

if api_settings.JWT_AUDIENCE is not None:
    payload['aud'] = api_settings.JWT_AUDIENCE

if api_settings.JWT_ISSUER is not None:
    payload['iss'] = api_settings.JWT_ISSUER

return payload

this ` if api_settings.JWT_ALLOW_REFRESH:`
it means if JWT_ALLOW_REFRESH exist then the handler to set the orig_iag,
and the JWT_ALLOW_REFRESH default is False, so we add it to the settings and set it to True

ps:
on the basis of `RefreshJSONWebTokenSerializer`, we can know
the JWT_REFRESH_EXPIRATION_DELTA's value means in this time field you can refreash!

hope good user for you

I've tested and found out that even though there is 'JWT_REFRESH_EXPIRATION_DELTA' on settins.py, it doesn't work. Only 'JWT_EXPIRATION_DELTA' works for refresh token.

I've tested and found out that even though there is 'JWT_REFRESH_EXPIRATION_DELTA' on settins.py, it doesn't work. Only 'JWT_EXPIRATION_DELTA' works for refresh token.

@seon54
Like I said above,the JWT_REFRESH_EXPIRATION_DELTA's value means in this time field you can refreash!  so you should set JWT_REFRESH_EXPIRATION_DELTA bigger than JWT_EXPIRATION_DELTA.
so base i understand, because i haven't research all django-jwt code. so i think two situation:
when your jwt token expired:
1、the operation of refresh need you take a intiative to call.
2、the operation of refresh autocall
but i browse the django-jwt source code ,I don't seem find autocall about refresh.
hope useful to u!

Hi Guys,
Just a comment and observation on my side about the same issue : for me, as soon as you set JWT_VERIFY_EXPIRATION to true, the decoder of the JWT is checking expiration of the token.
As such, even when running token refresh, the same decoding method is called and the program exits at this line of code :
payload = self._check_payload(token=token)
If you look at this line of code:
https://github.com/GetBlimp/django-rest-framework-jwt/blob/0a0bd402ec21fd6b9a5f715d114411836fbb2923/rest_framework_jwt/utils.py#L101
You see that expiration is always tested during decoding once set  in settings of Django. Even when asking for a refresh ...
For me, in case of refresh it should not check expiration time of the token but rather check JWT_REFRESH_EXPIRATION_DELTA.
So I wonder if we are not facing a bug here ... but I am not 100% sure.
What do you think ?


Change the initScripts field in NewClusterDTO to be an array

One of our processes failed with an error: com.fasterxml.jackson.databind.JsonMappingException: Can not deserialize instance of com.edmunds.rest.databricks.DTO.InitScriptInfoDTO out of START_ARRAY token
According to the Databricks API documentation "init_scripts" is an array of InitScriptInfo. Change the initScripts field in NewClusterDTO to be InitScriptInfoDTO[] to align with Databricks API requirements.

thank you for catching and implementing a fix for this!


improve(apiserver):move ldHandler for improving cohesion

What this PR does / why we need it:
move ldHandler from  NodeController to LocalStorageNodeController  for improving code cohesion. ldHandler located on NodeController is useless，because  NodeController just deal with checking request parameter and responsing to the client. Instead, LocalStorageNodeController  which served as a service layer is a better place for ldHandler
Special notes for your reviewer:
Does this PR introduce a user-facing change?

can you have a look? @peng9808 @Vacant2333

lgtm


[Event Change Request] table 5964  "Service Contract Line" - multiple publishers

Hello, would it be possible to add OnValidateServiceItemNoOnAfterCalcServiceItemNoIsNotEmpty2 event to table 5964  "Service Contract Line", like this:
There is an existing event OnValidateServiceItemNoOnAfterCalcServiceItemNoIsNotEmpty( that has been updated with additional parameters.
        field(5; "Service Item No."; Code[20])            trigger OnValidate()
...

                 ServiceItemNoIsNotEmpty := "Service Item No." <> '';
                 OnValidateServiceItemNoOnAfterCalcServiceItemNoIsNotEmpty(Rec, ServiceItemNoIsNotEmpty);
                 DoExit := false;
//Existing->                OnValidateServiceItemNoOnAfterCalcServiceItemNoIsNotEmpty(Rec, ServiceItemNoIsNotEmpty);
>                 OnValidateServiceItemNoOnAfterCalcServiceItemNoIsNotEmpty2(Rec, ServiceItemNoIsNotEmpty, xRec, HideDialog, DoExit); //New Event
                 if DoExit then
                     exit;
                 if ServiceItemNoIsNotEmpty then begin
                     GetServItem();

      [IntegrationEvent(false, false)]
//Existing->    local procedure OnValidateServiceItemNoOnAfterCalcServiceItemNoIsNotEmpty(var ServiceContractLine: Record "Service Contract Line"; var ServiceItemNoIsNotEmpty: Boolean)
     local procedure OnValidateServiceItemNoOnAfterCalcServiceItemNoIsNotEmpty2(var ServiceContractLine: Record "Service Contract Line"; var ServiceItemNoIsNotEmpty: Boolean; xServiceContractLine: Record "Service Contract Line"; HideDialog: Boolean; var DoExit: Boolean)
     begin
     end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 10745.


Added  particular file name

added the particular file  name Surface_Brightness_Control_v<IP_ADDRESS>.msi which will be used to control the surface brightness

@illfated @jvsam , Please review the changes, approve if found correct

The line breaks in the source text look a bit weird to me, even if they seem to be ignored when viewed as a web page. I will suggest some change to the text layout, because it looks like the text previously was restricted to max 100 characters, but I don't think that is a requirement anymore. @JohanFreelancer9 , you are very welcome to do a copy review and suggest changes of your own.

Very good, well spotted. I deleted my suggested change, since your suggestion covers the same line.


Integration Fails To Load

What happened?
2024-03-05 13:50:43.884 INFO (MainThread) [homeassistant.setup] Setting up lock_code_manager
2024-03-05 13:50:43.885 ERROR (MainThread) [homeassistant.setup] Error during setup of component lock_code_manager
Traceback (most recent call last):
  File "/config/custom_components/lock_code_manager/__init__.py", line 88, in async_setup
    res_id = next(
             ^^^^^
StopIteration

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/setup.py", line 390, in _async_setup_component
    result = await task
             ^^^^^^^^^^
  File "/config/custom_components/lock_code_manager/__init__.py", line 95, in async_setup
    data = await resources.async_create_item(
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'ResourceYAMLCollection' object has no attribute 'async_create_item'

Steps to reproduce the issue

download, unzip, and place in custom_components/lock_code_manager/
Add and configure integration
integration errors saying it cannot be setup
...

Home Assistant Version
2024.3.0b6
What version of Lock Code Manager are you running?
0.30
Lock make and model
Kwikset 916 zwave
Relevant log output
No response
Screenshots
No response
Anything else?
No response

damn, sorry about that, thought these two collection types were the same but clearly not. Easy fix once I get home

All good.  Happy to do what i can

OK so it looks like you can either use YAML or the UI. When you use YAML, it's read only, so we can't automatically add the resource.
I'll link a PR with a fix as well as instructions for how to make the frontend component available when you are using YAML to define resources

I did the UI


Linode IPv6 Range support, Optional region filtering, Missing fields in Documentation fixed

Linode:

Adds support for Discovering IPv6 Ranges routed to Linodes
Adds optional "Region" parameter to filter results thus making API calls faster, examples are "us-east", "us-central", "eu-west" ,etc.
Documentation for Linode service discovery updated to include missing fields
Tests updated to exercise the region filtering and new ipv6_ranges data availability

@brancz @metalmatze

This is super awesome thanks for doing this!

@tjhop  would you mind-re-reviewing?  I transitioned to TableDrivenTests as per your request

I don't know Linode, but the code change is quite small and the tests look extensive, so I'm happy to merge.
(from bug scrub meeting)

Yes, please!

Code change looks good and the test updates are a big improvement. The only other thing I think that's worth calling out is the fact that the event polling logic that happens in the refresh() method hasn't been updated to do any kind of regional filtering, it only happens in the refreshData method. So I think it would still be possible for an account event (ex: creating a VM in Japan) to trigger prometheus to update targets, even if it's filtering for targets in eg us-east:
https://github.com/prometheus/prometheus/blob/main/discovery/linode/linode.go#L179-L207
If that's not ok or expected, we may need to consider updating the refresh() method as well

Code change looks good and the test updates are a big improvement. The only other thing I think that's worth calling out is the fact that the event polling logic that happens in the refresh() method hasn't been updated to do any kind of regional filtering, it only happens in the refreshData method. So I think it would still be possible for an account event (ex: creating a VM in Japan) to trigger prometheus to update targets, even if it's filtering for targets in, say for example, us-east:
https://github.com/prometheus/prometheus/blob/de05d5e11b6292bfbdf7736e6f78e64ab07bb1dd/discovery/linode/linode.go#L179-L207
If that's not ok or expected, we may need to consider updating the refresh() method as well

Account events cannot be filtered on region
$ curl -H "Authorization: Bearer $TOKEN"   -H 'X-Filter: { "region": "us-east", "created": {"+gte": "2024-03-27T11:04:05"} }' https://api.linode.com/v4/account/events |jq .
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100    72  100    72    0     0    220      0 --:--:-- --:--:-- --:--:--   220
{
  "errors": [
    {
      "reason": "Cannot filter on region",
      "field": "X-Filter"
    }
  ]
}

Ah, fair enough. Seems good to me, then 👍

Thanks all!


Data frame Support

This PR now supports Data frame support with review changes.
The PR also accommodates relevant tests in test_scrpit.py file.

Thanks for this PR! I went through and addressed all your questions, added in some additional features, and merged it in. It's SO much better now :)


Commit directly to the master branch

In step 8, where can you commit directly to the master branch when only the save and run-button is active? I have a pipeline-project, so all my code is at GitHub.

Dokumentinformasjon
⚠ Ikke rediger denne delen. Den kreves for koblingen docs.microsoft.com ➟ GitHub-problem.

ID: 38f7a23b-ebd4-af3e-68a2-275f7e45c33e
Version Independent ID: f552a18c-ba29-00d4-03b6-254d7556d319
Content: Create your first pipeline - Azure Pipelines
Content Source: docs/pipelines/get-started-yaml.md
Product: devops
GitHub Login: @andyjlewis
Microsoft Alias: alewis

@charlottesoderstrom I'm sorry for the long delay in response. I was out of the office for a long period of time earlier this year. We've made a lot of fixes and changes since you posted this issue. I hope you were able to work out the issue, but please re-open if not.


Unable to bind hyperglass-agent to specific IP

I am unable to find any way to make the hyperglass agent listen only on a single IP address.
I do not wish to expose the hyperglass-agent HTTP service to the internet proper and have it listen only on our OOB interface, but also do not wish to run a firewall on our FRR box, as iptables etc. would massively impact performance.
Is there any way to make the agent listen only on a specific address/interface?
Thanks in advance! :)

Hi there,
Really sorry for not responding to this sooner.
Starting in hyperglass v1.0.0-beta.76, I've started deprecating hyperglass-agent. Moving forward, FRR & BIRD can be interacted with in the same manner as any other device, i.e. via SSH. See here for details/caveats). Everything will still work as-is for now, but I'd encourage you to try moving to frr_ssh/bird_ssh as the nos (and of course, let me know of any problems via a new hyperglass issue).
I'm going to go ahead and close this issue out.
Thanks,
Matt


backfill sync from an anchor checkpoint state

Motivation
This PR is to backfill in a scenario when wss checkpoint or any other anchor state is used to start the beacon node.

Description
Right now, this PR rebases https://github.com/ChainSafe/lodestar/pull/2637 on current master, making it workable base to build on top of the mentioned previous PR

Fixes:

[x]  Don't reject the entire syncrange sequence if a block in mid is missing making it a non linear
[x] Fixe the scenario where the syncrange keeps on resulting in a non anchored block at the end, i.e. end block is orphaned, and the previous head could be multi blocks behind, likely scenario in reorgs. Resolution, load the previous head in a solo request to set it as a new anchor
[x] before rangeSync or sync from outside, check the DB as DB could have had blocks saved from previous run, no need to verify their signatures and blocks in db should already be verified.
[x] Do a checkpoint check if a wss checkpoint has been provided which was in the past from the initialized beacon state (from DB because of a previous run). In case not provided compare against genesis when at genesis and panic if not same.
Created a backfilledSequences repository module, which tracks backfilled sequences like 384:key=> 211:value i.e. backfilled  from slot 384 to 211 both including, in normal operation will typically store two sequences, one used by the backfill process and one used by the forward moving chain (which will upon finalizing will write a new sequence finalizedSlot=>chainStarted/anchorSlot). Any gaps in the db because of restarting with checkpoint sync will result into a new sequence entry, but the previous entry will be eliminated when the backfill syncs up the gap
[x] Strategy to skip already filled sequence (needs a strategy to track gaps or filled sequences)
[x]  InvalidWSCheckpoint error (https://github.com/ChainSafe/lodestar/issues/3385)
[x] Schedule the processing/verification when the chain is supposedly free throttling chain by BATCH_SIZE in a single trigger cycle (in db reads or syncRange fetches)
[x] grafana dashboard

skipBackFillSync option?
backfillTill:  options i) till  wsCheckpoint  to be validated, ii)till GENESIS_SLOT (default) iii)till provided Slot
Tested Scenarios:

[x] sync test case: sync/wss.test.ts

[x] prater backfill sync to genesis (despite multiple restarts interrupting the sync, recovering using backfilled Sequences)

[x] stopping and starting multiple times creating gaps in the back filled sequences, backfiled sync filled the gaps and combined them with backfilled sequences to avoid redoing previous backfill sync.
example of backfillSync  recovering on a restart using previous backfilled sequence (jumped back from 1633696 to 1437564, and then continuing backfilling from there on:

[x] recovering from a persistent non anchored sequence in range sync (because of the orphaned block being served at the edge of range sync)

[x] recovering the backfilled to genesis state on a fully backfilled node restart

[x] stopped a fully backfilled node and restarted after a gap with new recent checkpoint - backfilled from the new recent checkpoint to previous finalized checkpoint when the node was stopped, and then correlated with already backfilled sequence till the GENESIS to switch to backfilled complete state

Closes #2556

example of backfillSync  recovering using previous backfilled sequence (jumped back from 1633696 to 1437564, and then continuing backfilling from there on:

@g11tech Remember to mark as "Ready for review" when appropiate! Draft PRs should be a transient state for unfinished work

Graphana dashboard:

This looks super good! Thank you so much for the detailed charts and progression :heart: Will do another review in depth asap and should be good to go.

This looks super good! Thank you so much for the detailed charts and progression heart Will do another review in depth asap and should be good to go.

thank you! :+1:

synopsis of a test run with the latest PR code:

Started backfill sync around 16:30
Restarted coouple of times between ~17:00-18:30, sync recovered the previous progress using backfillRanges
Synced to genesis at 20:00 but sync aborted with failiure as code was checking signature of genesis block as well
Fixed it around 22:00, and the sync recovered previous progress to genesis which it complete successfully

@dapplion : Kindly review and let know if anything further needs to be fine tuned.

@dapplion updated the PR with the discussed changes (and rebased with current master). test run where backfill sync recovered previous progress and completed sync to genesis. :slightly_smiling_face:

Excellent! Looking forward to many more like this in 2022 tada

Thank you! lodestar rocks! :rocket:
latest run on prater


Minor typo fixes for AVA documentation

Awaiting peer review

Looks good; we'll merge these editorial revisions. Thanks @jasonxian-msft.


Speed up tests

[x] Optional builds on macOS and JRuby (too long)
[x] Maybe smart sleep pauses for faster local running

Done!


Cross-ref .FormatColor property from object page

Cross-reference the ColorScaleCriterion.FormatColor property from the ColorScaleCriterion.FormatColor object page.
Also, delete the unnecessary cross-reference to the Excel Object Model Reference. Add a table of properties.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: italicize sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

VBA/Excel-VBA/articles/formatcolor-object-excel.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

VBA/Excel-VBA/articles/formatcolor-object-excel.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

All content in this repository has been migrated to a new repository (https://github.com/MicrosoftDocs/VBA-Docs). The changes in this PR have been applied in the new repository (as part of pull request #61), so this PR is being closed. The changes will be published to the live docs soon. Thank you for your contribution!


Filter implied points directly

Exporing one of my own suggestions on #368

I'm going to merge so I can apply the rest of my changes to my branch and avoid conflicts


Allow preview_title_position config top

Problem
A description of what is the problem that can be fixed with the feature you propose.
Feature
A description of the feature you propose.
Examples
One or more code examples that shows the feature in action.
Additional context
Any other context about the feature request here.

Closing this since I believe your other issue covers it.


RuntimeError: Duke

I have downloaded and put the dukemtmc data set in the corresponding location, but still reported a runtime error. Other data sets are no problem. Why is this happening? I also have this problem in several other paper codes that use this baseline, only the Duke data set has a problem

I have downloaded and put the dukemtmc data set in the corresponding location, but still reported a runtime error. Other data sets are no problem. Why is this happening? I also have this problem in several other paper codes that use this baseline, only the Duke data set has a problem


Feature request: Allow comments in karabiner.json

Hello,
Thanks for the excellent and free software! I'm happily using Karabiner to remap a whole bunch of keyboard combinations to enable Windows-like hotkeys on MacOS.
However, my karabiner.json is quickly becoming huge and very hard to read. Having the ability to put comments to serve as hotkey headers would be great for organizational purposes. Furthermore, it would be very nice if I could pepper my hotkeys with notes to myself as to why I specifically wrote a hotkey the way that I did, just like I do when I write code.
Other popular software, like Microsoft's Visual Studio Code (by Microsoft), also has user settings / hotkeys contained in a JSON preferences file. However, VSCode allows "JSON with comments", which is great - you can write a comment next to each setting describing exactly what it does. (e.g. // This is a comment and /* This is a comment */)
Can Karabiner follow Microsoft's lead with regard to JSON comments?

For others Googling, I've been using a comment as an arbitrary "description" field.


Freebsd Support for Other Memory Address methods and Queue types in GVNIC

Is there any intention or plans of adding the newer queuing/memory addressing code for gvnic to the Freebsd Driver?
Specifically Raw Memory Addressing and DQO ?

Hi ccater, I have just updated this tree to include the recently upstreamed support for DQO-RDA and DQO-QPL. These new datapaths allow making optimal use of NIC bandwidth on gen3 GCP vm shapes.


Notero preference is not showing up in tools

Describe the issue
Notero preference is not showing up in the tools even after restarting Zotero.

I am running this on intel Mac and Zotero version 7.0.0-beta.53+969031a37
I used the Notero version 0.5.0

I found that it's the issue with the Zotero ver 7.0.0, which is a beta. For Zotero 6.0.30 it works fine.

Hi @Aman-Basu, thanks for reporting! I'm sorry this isn't more clear, but in Zotero 7 the Notero preferences have moved into a section in the main Zotero preferences. Are you able to find them there?

I've added a note about this to the README.


Lint .less files with stylelint

In particular, prevent tabs, fixing #921.

Should node_modules be added as an ignore in the flowconfig?

@rrandallcainc I don't think so? Wouldn't it be good to test typing across all available modules?
Anyway, not sure that's relevant to this particular PR.

It looks like the new stylelint is causing the build to fail here when running flow. Perhaps a simple solution would be to add an ignore for stylelint for now?
Looks like an open thread on this issue here: https://github.com/stylelint/stylelint/issues/2322

Oops, sorry @rrandallcainc, now I see what you mean!  (I was looking at the Github post on my phone, which isn't the best interface, and didn't see the failed checks.)
As suggested in one of those threads, I added a link to node_modules/stylelint/decls to the libs section of .flowconfig and now it seems to work.


[Bug]: the --kit flag does not always work

What kit and version are you using?
n/a
What browser are you using?
n/a
What operating system are you using?
OSX
Actual Behavior
When I copy the command from the website with the --kit flag, it doesn't always work out of the box. For example, I tried:
npm create @this-dot/starter --kit solidstart-tanstackquery-tailwind-modules

and was prompted to select my kit.

Expected Behavior
When I copy a command from the website, it should work
Reproduction
Run:
npm create @this-dot/starter --kit solidstart-tanstackquery-tailwind-modules

Additional Information
No response

I think we discussed this on a thread on slack sometime last year. The issue is that the --kit flag works, the command just needs to include --. Something like this: npm create @this-dot/starter -- --kit solidstart-tanstackquery-tailwind-modules.
I will create a PR to correct the README for those commands that are broken

Ah yes - it's more important to fix the READMEs then to ensure that they're correct. This one was wrong for instance:

This was completed in #1275 and the -- is needed on npm 7+


How to choose the num-executors according to the cluster-size

Let's suppose I have a dataset of 1.2 million (1282143) records and as per TFoS the steps and steps_for_epoch are calucalted by the following formulae
	steps = epochs * num_records_per_epoch / batch_size
	steps_per_epoch = steps / num_workers

==> epochs = 20
==> steps = 20 * 1282143 / 100 ==> steps = 256428.6
==> steps_for_epoch = 256428 / num_workers (num_workers PICKED AS PER num-executors)
spark-submit
--driver-memory 64G
--executor-memory 24G
--num-executors _______ ( <---I want to maximize this value, so I can perform the job quicker)
--executor-cores 1
keras_model.py
--cluster-size _______ (Is it need to be same as num-executors always, if not how to choose the cluster-size)
and Let's assume I have 16 nodes and 25 cores each ==> 400 cores altogether
so now how to calculate the total executors that I can supply to the job for model training. could you help me crack that.

@vamsinimmala1992 --cluster-size is only used in our examples because it's hard to infer the number of executors on Spark Standalone clusters.  Note that on YARN clusters, it just defaults to --num-executors (the expected value) if it's not provided.
As for optimizing performance in your cluster, that's a much more complicated topic... There are many factors that go into the real-world performance of your training, and unfortunately, many of those can be directly related to your specific implementation and your hyper-parameter choices.  See this FAQ for some more details.
And if you have the full cluster at your disposal, you can just try setting --num-executors and/or --cluster-size to 16 to use the all of the physical nodes.