Restore operation failing because of a specific resource

Our env:

Rancher version: 2.5.8-patch1
Kubernetes version: 1.17.2

While trying to restore our production environment using rancher-backup, our restore operator wouldn't complete because of an error on a specific resource.
The error are:
ERRO[2021/08/05 18:43:21] Error restoring resource container-memory-usage-bytes-sum of type management.cattle.io/v3, Resource=projectmonitorgraphs: Post https://<IP_ADDRESS>:443/apis/management.cattle.io/v3/namespaces/p-hjgcn/projectmonitorgraphs: read tcp <IP_ADDRESS>:56318-><IP_ADDRESS>:443: read: connection reset by peer
ERRO[2021/08/05 19:31:19] Error restoring namespaced resources [error restoring container-memory-usage-bytes-sum of type management.cattle.io/v3, Resource=projectmonitorgraphs: Post https://<IP_ADDRESS>:443/apis/management.cattle.io/v3/namespaces/p-hjgcn/projectmonitorgraphs: read tcp <IP_ADDRESS>:56318-><IP_ADDRESS>:443: read: connection reset by peer]

We deleted the project (p-hjgcn) did a new backup and were able to restore it correctly.
Is there a way to ignore errors and allow the restore operation to complete? We don't really want to have a downstream cluster blocks our restore.
Thanks

hi @pgdagenais  We just added the option for ignoring errors during the restoring process: https://github.com/rancher/backup-restore-operator/pull/159
The feature will be available in the coming release, please keep tuned!

Awesome thanks for the update!


docs(page): Fix path

:tada: This PR is included in version 1.3.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Support weights=nothing in AtomsData

A small addition - since ace_fit.fit_params sets weights=nothing I think it would be good for AtomsData to recognise this case and set the default weights.

Resolved in #113 by setting the default weights to match AtomsData.


Refactor app get to use util instead of calling other command, Closes #5232

Closes #5232

And I am out of ideas how to respond 😅.
We will check this one ASAP. Thank you for your work 👍

setting to draft due to the following observations
I will provide more guidance how we should proceed with this PR in near future


Native support for raw transaction handling

New or updated methods:

BigDecimal getBitcoinBalance(Address address)
BigDecimal getBitcoinBalance(Address address, Integer minConf, Integer maxConf)
List<Map<String, Object>> listUnspent()
List<Map<String, Object>> listUnspent(Integer minConf, Integer maxConf)
List<Map<String, Object>> listUnspent(Integer minConf, Integer maxConf, Iterable<Address> filter)
Map<String, Object> signRawTransaction(String unsignedTransaction)
Sha256Hash sendRawTransaction(String hexTx)
String createRawTransaction(Address fromAddress, Address toAddress, BigDecimal amount)
String createRawTransaction(Address fromAddress, Map<Address, BigDecimal> outputs)
String createRawTransaction(List<Object> inputs, Map<Address, BigDecimal> outputs)

Most of it is in action in the specification BitcoinRawTransactionSpec.

It seems that this commit contains some code that is causing GroovyDoc to fail when building GroovyDocs/JavaDocs/APIDocs. This is a minor issue, but I created Github Issue #3 for tracking it.


Fix dependency vulnerabilities by upgrading

What happened?
Repository SBOM Report from Sonatype Lift
<EMAIL_ADDRESS>  [sonatype-2021-1694] CWE-502: Deserialization of Untrusted Data

<EMAIL_ADDRESS>  [sonatype-2020-0926] CWE-379: Creation of Temporary File in Directory with Incorrect Permissions

<EMAIL_ADDRESS>  [CVE-2021-22569] CWE-400: Uncontrolled Resource Consumption ('Resource Exhaustion')

<EMAIL_ADDRESS>  [sonatype-2021-0818] CWE-404: Improper Resource Shutdown or Release

Steps to reproduce
N/A
Expected Behavior
Passing check
Actual Behavior
Warnings during check
Versions used
0.3.0
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

Addressed by #634


⚠ Jenkins Plugins Artifactory has degraded performance

In 895b345, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 1208 ms

Resolved: Jenkins Plugins Artifactory performance has improved in c870a4b after 25 minutes.


Add option to set notification_host env variable

This adds possibility to set env variable ERRBIT_NOTIFICATION_HOST to have different URL in notifications.
PR straight to master, because why not.

:+1:


Select interpreter popup does not shown any system, pyenv or virtualenv choice.

Environment data

VS Code version: 1.53.2
Extension version (available under the Extensions sidebar): v2021.2.576481509
OS and version: OSX Catalina 10.15.7
Python version (& distribution if applicable, e.g. Anaconda): 3.8.7
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): virtualenv
Relevant/affected Python packages and their versions: XXX
Relevant/affected Python-related VS Code extensions and their versions: XXX
Value of the python.languageServer setting: Microsoft

[NOTE: If you suspect that your issue is related to the Microsoft Python Language Server (python.languageServer: 'Microsoft'), please download our new language server Pylance from the VS Code marketplace to see if that fixes your issue]
Expected behaviour
When click on select interpreter, the popup should shown all installed python interpreter including system, brew, pyenv and also virtualenv created under pyenv.
Actual behaviour
The select interpreter popup only shown the one interpreter under "/usr/bin/python3", no other interpreters shown like it use to be. However if manually select the desired interpreter/virtualenv through the system dialog box, everything else in python development seems to work just fine.
The extension output the following in the output window complaining of not able to resolve symbolic link, even though all those symbolic link are valid and create by default installation methods include system, brew or pyenv.
Error 2021-02-17 22:56:52: Failed to resolve symbolic link:  [Error: ENOENT: no such file or directory, lstat '../../System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7'] {
errno: -2,
code: 'ENOENT',
syscall: 'lstat',
path: '../../System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7'
}
Error 2021-02-17 22:56:52: Failed to resolve symbolic link:  [Error: ENOENT: no such file or directory, lstat<EMAIL_ADDRESS>{
errno: -2,
code: 'ENOENT',
syscall: 'lstat',
path<EMAIL_ADDRESS>}
Error 2021-02-17 22:56:52: Failed to resolve symbolic link:  [Error: ENOENT: no such file or directory, lstat<EMAIL_ADDRESS>{
errno: -2,
code: 'ENOENT',
syscall: 'lstat',
path<EMAIL_ADDRESS>}
BTW, I tested the same setup on linux or windows, it works fine.

Can also confirm this is happening to us.

+1. Have rolled back for now.

+1 For me as well. The "Python: Select Interpreter" dialog does not list any of the pyenv virtualenv environments.
Downgrading to version v2021.1.502429796 solves the problem.

Have you manually opted into experiments? Check for this setting "python.experiments.optInto" = ["All"]. We have a new discovery mechanism, and it might be failing. You can opt into specific experiments if you need that. If you are NOT opted in any experiment let us know, there might be some interference going on with the new discovery module and the old one.

My python.experiments.optInto was empty.
On Thu, 18 Feb 2021 at 16:58, Karthik Nadig<EMAIL_ADDRESS>wrote:

Have you manually opted into experiments? Check for this setting "python.experiments.optInto"
= ["All"]. We have a new discovery mechanism, and it might be failing.
You can opt into specific experiments if you need that. If you are NOT
opted in any experiment let us know, there might be some interference going
on with the new discovery module and the old one.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vscode-python/issues/15439#issuecomment-781488191,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQBK25UEXLLIWE2XW5V5LIDS7VBJVANCNFSM4XZYDJJA
.

@braineruption Can you try this and see if it helps? "python.experiments.optInto": ["pythonDiscoveryModule"]

I don't see any difference between having
"python.experiments.enabled": true,
"python.experiments.optInto": ["pythonDiscoveryModule"]

or not.

@albireox  Can you share the paths to the interpreters that it is failing to detect? Also, can you share PYENV specific environment variable values?

It seems to be failing to detect all the pyenv virtualenvs from installations that are not conda. Apparently it finds the pyenv installations and venvs from conda:

but not others such as ~/.pyenv/versions/3.9.1/bin/python ~/.pyenv/versions/flicamera/bin/python. These are my pyenv versions:
  system
  2.7.13
  2.7.17
  2.7.18
  2.7.9
  3.10.0a5
  3.7.6
  3.8.3
  3.8.3/envs/sdsstools
  3.8.5
  3.8.6
  3.8.6/envs/archon-38
  3.9.0
  3.9.1
  3.9.1/envs/archon
  3.9.1/envs/basecam
  3.9.1/envs/cherno
  3.9.1/envs/datamodel
  3.9.1/envs/flicamera
  3.9.1/envs/jaeger
  3.9.1/envs/roboscheduler
  3.9.1/envs/sdssdb
  3.9.1/envs/tree
  3.9.1/envs/tron
  STUI
  STUI2
  archon
  archon-38
  basecam
  cerebro
  cherno
  chernosim
  clu
  coordio
  datamodel
  default
  drift
* flicamera (set by /Users/albireo/Documents/Code/sdss5/flicamera/.python-version)
  fliswarm
  fps_monitor
  jaeger
  mangadesign
  miniconda3-latest
  miniconda3-latest/envs/3.9.0
  miniconda3-latest/envs/STUI
  miniconda3-latest/envs/STUI2
  miniconda3-latest/envs/cerebro
  miniconda3-latest/envs/chernosim
  miniconda3-latest/envs/clu
  miniconda3-latest/envs/coordio
  miniconda3-latest/envs/default
  miniconda3-latest/envs/drift
  miniconda3-latest/envs/fliswarm
  miniconda3-latest/envs/fps_monitor
  miniconda3-latest/envs/mangadesign
  miniconda3-latest/envs/pydl
  miniconda3-latest/envs/target_selection
  pydl
  roboscheduler
  sdssdb
  sdsstools
  target_selection
  tree
  tron

And the environment variables

My system also has Python installations from homebrew, but I don't use them for development.

@albireox thanks for details. I am able to repro the issue. Can you share the output of ls -la from ~./.pyenv/versions?

albireoproˇalbireo ~/.p/versions [master] » ls                                                    (3.9.1)
total 0
drwxr-xr-x  8 albireo 256 Aug 13  2020 2.7.13/
drwxr-xr-x  8 albireo 256 Nov 25 14:02 2.7.17/
drwxr-xr-x  9 albireo 288 Jun  3  2020 2.7.18/
drwxr-xr-x  9 albireo 288 Jun  3  2020 2.7.9/
drwxr-xr-x  8 albireo 256 Feb 12 09:13 3.10.0a5/
drwxr-xr-x  9 albireo 288 Jul 18  2020 3.7.6/
drwxr-xr-x  9 albireo 288 May 22  2020 3.8.3/
drwxr-xr-x  8 albireo 256 Sep 24 13:52 3.8.5/
drwxr-xr-x  9 albireo 288 Oct 26 23:39 3.8.6/
lrwxr-xr-x  1 albireo  59 Nov 19 19:22 3.9.0 -> /Users/albireo/.pyenv/versions/miniconda3-latest/envs/3.9.0/
drwxr-xr-x  9 albireo 288 Dec 11 12:53 3.9.1/
lrwxr-xr-x  1 albireo  58 Sep 25 17:18 STUI -> /Users/albireo/.pyenv/versions/miniconda3-latest/envs/STUI/
lrwxr-xr-x  1 albireo  59 Sep 25 21:48 STUI2 -> /Users/albireo/.pyenv/versions/miniconda3-latest/envs/STUI2/
lrwxr-xr-x  1 albireo  48 Jan 18 02:24 archon -> /Users/albireo/.pyenv/versions/3.9.1/envs/archon/
lrwxr-xr-x  1 albireo  51 Jan 22 13:51 archon-38 -> /Users/albireo/.pyenv/versions/3.8.6/envs/archon-38/
lrwxr-xr-x  1 albireo  49 Feb 10 18:46 basecam -> /Users/albireo/.pyenv/versions/3.9.1/envs/basecam/
lrwxr-xr-x  1 albireo  61 Aug 19  2020 cerebro -> /Users/albireo/.pyenv/versions/miniconda3-latest/envs/cerebro/
lrwxr-xr-x  1 albireo  48 Jan 31 12:08 cherno -> /Users/albireo/.pyenv/versions/3.9.1/envs/cherno/
lrwxr-xr-x  1 albireo  63 Sep 16 13:00 chernosim -> /Users/albireo/.pyenv/versions/miniconda3-latest/envs/chernosim/
lrwxr-xr-x  1 albireo  57 Aug 19  2020 clu -> /Users/albireo/.pyenv/versions/miniconda3-latest/envs/clu/
lrwxr-xr-x  1 albireo  61 Aug 14  2020 coordio -> /Users/albireo/.pyenv/versions/miniconda3-latest/envs/coordio/
lrwxr-xr-x  1 albireo  51 Jan 31 15:09 datamodel -> /Users/albireo/.pyenv/versions/3.9.1/envs/datamodel/
lrwxr-xr-x  1 albireo  61 Aug 14  2020 default -> /Users/albireo/.pyenv/versions/miniconda3-latest/envs/default/
lrwxr-xr-x  1 albireo  59 Aug 19  2020 drift -> /Users/albireo/.pyenv/versions/miniconda3-latest/envs/drift/
lrwxr-xr-x  1 albireo  51 Dec 13 09:33 flicamera -> /Users/albireo/.pyenv/versions/3.9.1/envs/flicamera/
lrwxr-xr-x  1 albireo  62 Nov 19 19:32 fliswarm -> /Users/albireo/.pyenv/versions/miniconda3-latest/envs/fliswarm/
lrwxr-xr-x  1 albireo  65 Aug 19  2020 fps_monitor -> /Users/albireo/.pyenv/versions/miniconda3-latest/envs/fps_monitor/
lrwxr-xr-x  1 albireo  48 Dec 11 12:54 jaeger -> /Users/albireo/.pyenv/versions/3.9.1/envs/jaeger/
lrwxr-xr-x  1 albireo  65 Sep 16 14:44 mangadesign -> /Users/albireo/.pyenv/versions/miniconda3-latest/envs/mangadesign/
drwxr-xr-x 15 albireo 480 Nov 21 20:59 miniconda3-latest/
lrwxr-xr-x  1 albireo  58 Aug 25 11:02 pydl -> /Users/albireo/.pyenv/versions/miniconda3-latest/envs/pydl/
lrwxr-xr-x  1 albireo  55 Jan 19 14:03 roboscheduler -> /Users/albireo/.pyenv/versions/3.9.1/envs/roboscheduler/
lrwxr-xr-x  1 albireo  48 Feb  1 22:49 sdssdb -> /Users/albireo/.pyenv/versions/3.9.1/envs/sdssdb/
lrwxr-xr-x  1 albireo  51 Jun 24  2020 sdsstools -> /Users/albireo/.pyenv/versions/3.8.3/envs/sdsstools/
lrwxr-xr-x  1 albireo  70 Aug 17  2020 target_selection -> /Users/albireo/.pyenv/versions/miniconda3-latest/envs/target_selection/
lrwxr-xr-x  1 albireo  46 Jan 31 15:06 tree -> /Users/albireo/.pyenv/versions/3.9.1/envs/tree/
lrwxr-xr-x  1 albireo  46 Dec 27 19:22 tron -> /Users/albireo/.pyenv/versions/3.9.1/envs/tron/

I tried the pythonDiscoveryModule but that made no difference. What's missing for me are the Homebrew installed pythons and the pyenv virtual envs, i.e. all the installations that are sym-linked.

@albireox thanks for details. I am able to repro the issue. Can you share the output of ls -la from ~./.pyenv/versions?
I think the extension is skipping the ones that are symlinks under that directory.

@karthiknadig: Yes, that's the problem I'm seing. The "base" pyenv-versions show up, but not the virtual environments based on the base versions. And they are all symlinks:
╰─ /bin/ls -1F ~/.pyenv/versions
3.5.3/
3.8.5/
3.8.6/
3.8.7/
3.9.0/
3.9.1/
codejam@
cookiecutter@
cookie-example@
cosmos_dump@
dateml@
datesim-fb-explorer@
datesim-predict@
IHS-demo@
IHS-engine@
jupyter@
meteogram@
mlfactory@
pscdetentions@
riskbasedverification@
visutils@

I mentioned in Issue #15457 that I am having the opposite problem on Windows 10 with WSL 2, using visual studio code insiders.
I finally managed to set up pyenv so that pyenv shims come first in the path, and added a symlink so that python in usr/bin/python points to usr/bin/python3 and thus system python is available when running pyenv versions.
Now, however, in visual studio code insiders, the system python doesn't show up as an available interpreter (which I would imagine should be found automatically in usr/bin/python. I can add it manually though, but it doesn't persist beyond one session. Should I be making another issue for this?

I have this issue too.
It seems like to be not detecting symbolic python versions in .pyenv/versions
This is my ls result in .pyenv/versions
> ls
3.7.9 3.8.6 kube  upbit

And this is python interpreter in vscode.

@brybalicious That sounds like a different issue. Please file a separate bug.

@Aiden-Jeon Can you confirm that you don't have any experiments that you have opted into? check for python.exeperiments in your settings.

If you're having the issue described in the OP, please add the thumbs-up (👍 ) reaction to the OP so this issue has more visibility.

I'm having the same issue. It seems that the discovery mechanism isn't able to follow symlinks any more.
A workaround that I've found is to use "Enter Interpreter Path..." and enter the full path to the env's binary without going through the symlink. For example, to use the venv my-env:
$ ls -l ~/.pyenv/versions/my-env
lrwxr-xr-x  1 rob  staff  42 Feb 19 11:02 ~/.pyenv/versions/test -> ~/.pyenv/versions/3.8.6/envs/test

In the"Enter Interpreter Path..." input, use:
~/.pyenv/versions/3.8.6/envs/test/bin/python

This seems fixed to me in the latest vscode-python insiders either with "python.experiments.optInto": ["pythonDiscoveryModule"] or without it, although I'm seeing some differences in the names of the venvs depending on whether the experiment is on or not.

We just pushed a point release with a fix for this. Please try and let us know.

Point release also works for me.

Point release also works for me too.

Works for me, thanks!

Glad it worked, closing this now. If it still happens let us know and we'll reopen the issue.

Do not work for me. 😢
I use pyenv-win on window 10. The "pyenv" function never worked for me but the version v2021.2.576481509. I was exciting when I found it worked.  Now it gone again. Is anything I need to config with my scene（pyenv-win)? Thanks!

Yup, worked for me too. Thanks for the quick turnaround.

@LeoAzLiu pyenv-win is detected in the new experimental version of the discovery code. You can get that by opting into it, ad this to your user settings:
"python.experiments.enabled": true,
"python.experiments.optInto": ["pythonDiscoveryModule"]

@karthiknadig Thanks a lot. It works great! By the way I think the pyenv-win is supported. Why the issue  #15304 is still marked as "needs decision"? It is just a little confuse. But it is OK. It works! Thanks again! 👍

For my case, What it was worked:
"python.defaultInterpreterPath": "/home/{USER}/.pyenv/versions/{PROJECT}/bin/python",
"python.experiments.enabled": true,
"python.experiments.optInto": [
    "pythonDiscoveryModule"
]

For me it worked on windows. I used "python.defaultInterpreterPath":  "%USERPROFILE%.pyenv\pyenv-win\bin"


"Failure unable to create stack" when attempting to update stack

Bug description
After portainer (with agent-support) runs for a while, we get instant "Failure unable to create stack" errors (top right, red popup) when attempting to update any existing stacks.
These existing stacks have not changed at all since they were last updated or deployed, and they are already running.
Updating the portainer and portainer-agent services and reloading my browser fixes the problem, and I am again able to update existing stacks.
When viewing the network tab Firefox dev tools, it shows a 500 PUT response to each request, and {} as the response payload.
Some recent portainer-agent tasks show as "failed" and "rejected" with task: non-zero exit (137) and assigned node no longer meets constraints error messages, respectively.
  Skipping the endpoint defined via CLI.,
2018/05/07 06:31:02 Starting Portainer 1.16.5 on :9000,

This is a 3 worker, 1 manager cluster provisioned by Docker for AWS 18.03.0-ce, letting them create the VPC which I believe allows "all traffic" between all nodes and managers within the cluster by default.
Expected behavior
Able to update existing stacks, either with or without making changes to the stack file.
Steps to reproduce the issue:
I can't reliably reproduce this on demand, but it has been happening intermittently over the last few days while I have been working with Portainer on this swarm.
Technical details:

Portainer version: portainer/portainer:agent-support and portainer/agent:develop
Docker version (managed by Portainer): 18.03.0-ce
Platform (windows/linux): Linux, Docker for AWS
Command used to start Portainer (docker run -p 9000:9000 portainer/portainer):
Browser: Firefox

I happen to also be running an instance of portainer/portainer (no tag) pointed at the same swarm cluster with a local unix socket endpoint.
I opened the portainer/portainer install which already happened to have one local stack that I can edit (the rest, created via the agent-support install show as "external"), clicked update the stack and got the same "unable to create stack" error immediately.
Attempting to copy paste that same stack and deploy it as a new stack named test gives me a yellow "deployment error", then clicking "deploy the stack" again gives me a yellow "stack already exists with that name" error.
navigating into the new test stack shows the stack file saved and no tasks are running. Clicking update the stack immediately gives the same "unable to create stack" error.
the portainer/portainer log doesn't seem to have anything useful:
2018/05/06 14:25:40 Starting Portainer 1.16.5 on :9000,
2018/05/06 14:36:01 http error: User not found (code=404),
2018/05/06 15:11:12 http error:  (code=500),
2018/05/06 15:11:22 http error:  (code=500),
2018/05/06 15:11:27 http error:  (code=500),
2018/05/06 15:11:29 http error:  (code=500),
2018/05/06 15:11:30 http error:  (code=500),
2018/05/06 15:12:18 http error:  (code=500),
2018/05/06 15:12:20 http error:  (code=500),
2018/05/06 15:14:20 http error:  (code=500),
2018/05/06 15:14:29 http error:  (code=500),
2018/05/07 07:19:26 http error:  (code=500),
2018/05/07 07:20:44 http error:  (code=500),
2018/05/07 07:21:13 http error: A stack already exists with this name (code=409),
2018/05/07 07:21:24 http error: A stack already exists with this name (code=409),
2018/05/07 07:21:59 http error:  (code=500),
2018/05/07 07:22:11 http error:  (code=500),

Here's the offending stack:
version: '3.4'
services:
  authorizedkeys:
    deploy:
      mode: global
      resources:
        limits:
          cpus: '0.05'
          memory: 10M
        reservations:
          cpus: '0.01'
          memory: 10M
      restart_policy:
        condition: on-failure
    environment:
      AUTHORIZED_KEYS: |
        ssh-rsa ...
    hostname: '{{ .Service.Name }}-{{ .Task.Slot }}'
    image: interaction/dockercloud-authorizedkeys:ixc
    volumes:
      - ${HOME_DIR:-/root}:/user

# HOME_DIR=/home/docker

I believe we can close this issue then.
Feel free to re-open if the problem arises again. We'll try to think about recommendations for resource reservation/limit.


Changing DNS Server's does not require a reboot

We were able to use "ipconfig /release && ipconfig /renew" to blip the NIC in our Windows VMs to gather the changes. This blips the network connection on the box for a few seconds but stops the need to reboot the VM. Unsure if this will work in all situations, but it really helped us in a live production change situation.
"ipconfig /release && ipconfig /renew" needs to happen in the same line, as /release occurs you will lose access to the box until it renews.

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

ID: b9cc98dc-ed9e-1759-c5f7-e18722420b69
Version Independent ID: 217f2e7b-80d3-c2ec-3728-fd2264bbb5aa
Content: Create, change, or delete an Azure virtual network
Content Source: articles/virtual-network/manage-virtual-network.md
Service: virtual-network
GitHub Login: @KumudD
Microsoft Alias: kumud

This is in response to Step 6 of Changing DNS Servers
Restart the VMs that are connected to the virtual network, so they are assigned the new DNS server settings. VMs continue to use their current DNS settings until they are restarted.

@mrklean , Thank you for your suggestion. But it is recommended to restart the machine rather than using guest os commands as during the restart, platform takes care of the updating the DNS server.

@mrklean , Do you have any update on this issue?

@mrklean , Please tag me if you have any further questions.


Add notes-app project

Proposed changes:

Project - Notes App

Type of change:

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Other (please specify)
[ ] This change requires a documentation update

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings

Additional info (if any):

Good work @HarshilMendpara


[T2A2][T09-A1] Annabel Eng Jing Wen

xx

@mauris - from PR bot, please review this.

Hi mauris, I'm not sure what I'm doing wrong here. Please advise thank you!

@annabeleng don't worry, just submit according to the instructions.


Remove favicon option as  Typedoc 0.27.0 now supports it

Also the plugin needs to be built as ESM now. I was going to do it be since I only use it for the favicon option....


Enhance/optional message args

See https://github.com/orgs/flucoma/teams/flucoma-dev/discussions/3

checks failed because it tried to run the tests on tl::optional without building them. will strop that happening

this is great. A few questions

at first I was surprised that the attrui was not updating but I reckon this is the desired behaviour - the 2nd message is optional
the radius part of the kdtree query brings an interesting question - should we add another (3rd) argument there?

this looks like a very promising development for all the artificial attributes, i.e. all those unliked to the state of the object

Just reviewed the SC version (https://github.com/flucoma/flucoma-sc/pull/77).
@weefuzzy This is great. I think it makes a lot of sense.


Pso fix

Quick fix to workaround multiprocessing/pickle interactions with the plugin manager for PSO optimization.  Also relevant to #135.

Looks like these test function plugins need to be removed now (https://github.com/NOAA-OWP/ngen-cal/blob/61c9672559832d5bb2edf7471f8d1c1cf959f9c6/python/ngen_cal/tests/test_plugin_system.py#L53-L59).

The problem was that I modifed setup_plugin_manager instead of setup_scoped_plugin_manager haha, I just corrected that.

The problem was that I modifed setup_plugin_manager instead of setup_scoped_plugin_manager haha, I just corrected that.

Nice!

In doing some local testing, we should be able to get around some of this if we use multiprocess. It uses dill an alternative to pickle, to serialize and deserialize objects.


Refactored the CI_Log line formatting

Extracted the CI_Log line formatting into a protected
function _format_log_line() so as to make it easy to
change the log line format via extending the class and
overriding the method.

Your code doesn't comply with our styleguide (you could've just taken the current code as an example) and if this is for extensibility - why a protected method instead of a property?

Thanks for the catch. I'll fix that.
I not only need to change the order of level, date and message but also change the separators and add more items to the log line.
I also want to add filler characters to the log level ("DEBUG","xINFO") to make the logs cleaner and appear in order.
How do I do this via a property?

I suspected you'd say you want to change the order of these tokens, but ... why?

In our company we have a ton of different applications built in many different ways. All of which write logs in a specific format. I am working on a couple of new services and want to write logs from codeigniter in the same format we've been using in all other places.

You could extend the CI_Log class, using application/core/MY_Log, with your custom formatting there.

Correct. That is exactly what I want to be able to do.
But I don't see a way to extend CI_Log without having to rewrite the whole of write_log() function. Since that function is the meat of CI_Log.
This patch will make it easier to make my own log line format.
It will extract the code that formats the log line into its own function inside CI_Log.

So that I can extend it in my MY_Log class like so.

@jim-parry @narfbg any updates on this?

@jspreddy Please be patient, it's holiday season. :)
On topic: I don't really like it, but what the hell ... it's not like CI_Log does much else anyway.
I'll leave some inline notes however ... the patch is still inconsistent with our other code.

@narfbg Anything else I need to change?


Fix the matrix representation in the documentation of CHGate

Summary
Fixes issue number #5207
(Originally addressed here https://github.com/Qiskit/qiskit/issues/1053)
Details and comments
The note on the documentation page for the CHGate displays an equation where a 1/sqrt(2) is incorrectly factored out the final matrix representation. This pull request fixes the terms in the final matrix representation by removing the 1/sqrt(2) outside the matrix and distributing it correctly to the bottom-right block of the matrix.
Here is a visual representation of what was changed:

 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.

Thanks for the contribution @g-ebbs! Could you give your pull-requests more detailed names so that we can see what they are about in the overview? 🙂 Also, if they are bugfixes or similar, they'll show up in the changelog.

Thanks for the contribution @g-ebbs! Could you give your pull-requests more detailed names so that we can see what they are about in the overview? 🙂 Also, if they are bugfixes or similar, they'll show up in the changelog.

Sounds good, I will make sure to describe the issue in the title of my future pull requests. I have been working with Qiskit for 2 years now, feels good to finally contribute to the GitHub! Also, is there a way I can assign a label like to the issues I open?


Deprecated APIs

@olivere Do you think it make sense to warn developers of using deprecated apis via logging (might need to introduce a dev/prod mode to turn these off). For example, count search type is now deprecated as of 2.0. It might make it easier for dev's this way to stay away from deprecated apis.
Just a thought. Feel free to close this, as its a bit out there 🎱
V
PS. Quick search link for deprecated apis

Hmm... sounds like a good idea until you try to implement it. How do I figure out if someone uses search_type? I would probably need to inspect parameters, right? Do you really want to go down that route? Besides, I think that most of the warnings would be because of Elastic using deprecated APIs and/or parameters. :-)
It's really time consuming to stay on top of the large API surface. You could figure out the top-level issues on the Elasticsearch GitHub repository that track these changes. But it's a full-time job I suppose, and I currently don't have the time to do that TBH.
But thanks for your idea. Maybe we can find a simple way to implement that. Will keep it open and add as "enhancement" to let it sink in.

@olivere agree! another option is to close this for now, until more users request it.

I think I'll close this for now. Maybe ES will return something from the server-side in future.
Still, thanks for the idea!


Cannot build a tag with several arguments and applied filters

Hi @markglenn
we are trying to bild a tag, that can render an other component, like:
{% render "component_name", binding1: 'foo' %}

This is easy to achieve, thanks to you cool extension mechanism.
problem
But now we wanted the component to be an argument with filters, which cannot be achieved:
{% render "component_name" | append: a_variables_content,
    binding1: 'foo' | bar: buzz, 'foo2',
    binding2: 'foo3'
%}

The problem is, that the argument list of a filter can have a keyword list at the end, which makes a string with a colon at the end ambigues (lib/liquex/parser/object.ex:36).
What is this keyword list for filters needed for? I haven't found a test for it nor have I found a shopify liquid example like that?
I'm asking for curiousity. I'm Still a big fan of this project :)
Cheers

Thank you for pointing this out. I honestly don't remember the reason behind allowing a keyword list at the end of a filter. I will have to go back and look at some of the examples I worked with in the past and my current custom component implementations and how they work with it.
I will look into it to see how the Liquid gem handles your use case since it really is ambiguously defined in the documents and test cases.
Just for clarity, how would you expect your render tag to be parsed? I know it's not standard liquid syntax, but where would you place parentheses around your block of code to make it not ambiguous? Where are you expecting the filters to be applied?

Hi @markglenn
I thought the ambiguity, would have been gone, when the keyword list is not parsed, because of the colon, that would mark the next binding of a render, like:

filter is marked with a pipe symbol: (| [^\s:]+:?( [^, ]+,?)*)*
binding parameter is marked without a pipe symbol: ([^\s:]+:? [^,\s]+,?)*

Regexes are not exact, but I hope they show my idea.

Hi @ouven,
I'm coming back to this issue and I'm again trying to dig into the issue.
I found where keyword lists at the end of a filter come into play. They don't exist in the base liquid gem, but do show up in the Shopify liquid documentation under the image_url filter.  In their example, they allow a keyword list to add URL parameters to an image:
{{ product | image_url: width: 100, height: 100 }}

You can find the test that showcases that in the code base at parser/object_test.exs:33. This test is pulled directly from my use case in Enology for Winestyr where this library is used.
In your use case, Liquid should parse this as [parentheses added for clarity]:
{% render "component_name" |
    (append: a_variables_content, binding1: 'foo') |
    (bar: buzz, 'foo2', binding2: 'foo3') %}

Or in plain English:

Render out the render custom tag
Run that result through the "append" filter with arguments a_variables_content and binding1: 'foo'
Run that result through the "bar" filter with arguments buzz, 'foo2', and binding2: 'foo3'

And that seems to follow what Shopify describes in their Liquid for Shopify documentation.
If I'm missing something, maybe that's because you're trying to write it in a generic way here with 'foo', 'buzz', etc. Can you give me a more concrete example so we can maybe find a work around or to help me understand how this library is not following the standard?

Hi @markglenn,
What we were trying to achieve was more like the following scenario:

we have a custom render tag, that can render another template with isolated context bindings bar: "buzz".
the name of the template is dynamic and is built by adding a_variables_content to our component_name_prefix.

{% render ("component_name_prefix" |  append: a_variables_content), bar: buzz %}

Now, by the fact, that a filter can have a keyword list, I cannot determine where the keyword list of the filter end and the binding list of the render tag starts. We can work around this easily, by just doing something like:
{% assign component_name = "component_name_prefix" |  append: a_variables_content %}
{% render component_name, bar: buzz %}

Actually I was not aware of the use case, that you did mention. I did not find an example for a dynamic variable list for a filter. I was only looking at the more generic documentation: https://shopify.github.io/liquid/filters
So I guess, we cannot solve this ambiguity and just keep assignments as replacement for parentheses :)


[QUESTION] Do you plan to continue the development of beamui?

I just wanted to just make this question. I just saw your fork and got really interesting. I'm a n00b in D and in programming in general (well not so true but that's how I feel) amd I can't take the project on may own but I will be glad to help in the future when I get a little bit more confident. So yeah, what are your plans for now?

I plan to fix bugs and add my functionality when I encounter such a need. Made a fork because the beamui developer does not check the repository for too long.
I will be glad for any help. I will accept your pull requests in a reasonable amount of time, and I will also try to take the time to answer your questions.

Thank you!!!


snowpark-python 1.21.1

snowpark-python 1.21.1
Destination channel: defaults
Links

PKG-5664
Upstream repository
Upstream changelog/diff

Explanation of changes:

1.21.1 build

setup.py says the Documentation is https://docs.snowflake.com/en/developer-guide/snowpark/python/index.html (changed in 1ec8b19bb in 2022).
@JeanChristopheMorinPerso may have a view, here.  I may be misinterpreting project_urls.Documentation for what we want doc_url to point to.

setup.py says the Documentation is https://docs.snowflake.com/en/developer-guide/snowpark/python/index.html (changed in 1ec8b19bb in 2022).
@JeanChristopheMorinPerso may have a view, here. I may be misinterpreting project_urls.Documentation for what we want doc_url to point to.

it seems reasonable to me, in the meantime we could approve this and update it or add a note for the next version?


Android Status.paused is equal to Status.ready

Im using the r13 version, and i see that the constants Status.paused and Status.ready are both equal to 2. Is it on purpose? How do i distinguish between the two states?
Thanks!

I think this is a case of Android not matching one-to-one with iOS. On android when the player is paused it is the same as ready.
@Guichaguri can you canfirm?

Yes, READY is unused on Android. See #942


task100

@PerteGeorge thank you for reporting this. I'll assign someone to take care of it soon.

@PerteGeorge this is your task now, please go ahead. Deadline (when this ticket should be closed) is 2020-12-27T20:34:04.905724.
Estimation here is 100 minutes, that's how much you will be paid.
Remember, you don't have to solve everything in this ticket - you can solve it partially and leave todo markers in the code, which will become future tasks.
If you have any questions don't ask me, I'm not a technical person. Open new tickets instead.
If you don't have time or simply don't want to work on this, you can always resign.

@PerteGeorge thank you for resolving this ticket. I've just added it to your active invoice. You can always check all your invoices and more on the Contributor Dashboard.


Code Sample name and description dont match the linked repo

"Meeting stage view"
should be
"App monetization in tab"
"This app helps to enable and configure your apps for Teams meetings. It also demonstrates use of share in meeting feature."
should be
"This sample shows how to open purchase dialog and trigger purchase flow using teams-js SDK."
App monetization in tab

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

ID: fd29bf73-3680-24a6-5c05-76d06c1e40c1
Version Independent ID: 45035997-0a41-8f4b-575d-ea5ae8ef4bab
Content: Include a SaaS offer with your app - Teams
Content Source: msteams-platform/concepts/deploy-and-publish/appsource/prepare/include-saas-offer.md
Service: msteams
GitHub Login: @heath-hamilton
Microsoft Alias: surbhigupta

@Ryan365Apps - Thank you for reporting this issue, we will check and get the doc updated.

@surbhigupta12 - Could you please help to update the code sample section in this document - https://learn.microsoft.com/en-us/microsoftteams/platform/concepts/deploy-and-publish/appsource/prepare/include-saas-offer#code-sample
Please update as below -
Sample Name - App monetization in tab
Description - This is an sample tab application which shows how to open purchase dialog and trigger purchase flow using teams-js sdk


Styling

FetchData was renamed ItemsComponent and MyStore was renamed DMStoreStockComponent in my last pull request
Both are in DMStorefront/Client/Shared/DMStore now


fixed title

https://digital.dclg.gov.uk/jira/browse/FS-1195

Can we update the page <title> too? Currently it appears to be DLUHC Funding Service Design Iteration 2 We need a way to make this unique per page, so probably should be an attribute of the base template we can add a crumbtrail too.

Will naming the page in base.html "Funding Service Design - Task List" suffice?

Will naming the page in base.html "Funding Service Design - Task List" suffice?

@donshellywork No, as that will apply to all pages. I suspect we will need to use a pattern similar to this to override it on this page only:
https://github.com/communitiesuk/funding-service-design-frontend/blob/54a0faf287be75467d42f01efd23a562a37c991c/app/templates/404.html#L3


Improve log messages in leased register

What changes are proposed in this pull request?
A small improvement on logging and lease release logic for non-streaming register.
Although we have https://github.com/Alluxio/alluxio/issues/16698, this is NOT a fix.
Why are the changes needed?
If register lease is turned off, avoid the unnecessary lease check on the master and the extra warning log.
Does this PR introduce any user facing changes?
NA

alluxio-bot, merge this please


Add nr1 vscode extension to projects

This PR adds a project entry for the NR1 VSCode Extension

Looks like the test is failing due to snapshots being out of date. Since this PR is unrelated, I'm going to go ahead and merge.


aria-invalid not applied when submitting empty required fields

When a form is submitted, any required fields that are empty are given an error message and an error class, but the aria-invalid attribute is not added. Other types of errors (like an invalid email address) are given aria-invalid on submit, but not empty required fields.
This means that anyone using the error class as a selector for error styles (rather than an [aria-invalid="true"] selector) will be conveying the error state of those fields visually and not semantically, and anyone using [aria-invalid="true"] as a selector for error styles won't have the error state conveyed visually or semantically.
(Empty required fields are only given aria-invalid when the form is submitted and then the individual field is blurred.)
It looks like this can be resolved by moving the aria-invalid toggle into the highlight and unhighlight functions, not sure if there was a reason this wasn't done already. (Something may also need to be done for reset.)
Your environment

version of jquery-validate: 1.19.3
jQuery 3.6.0 (also encountered with 3.2.1)
which browser and its version: Chrome v93.0.4577.82 and Firefox Developer Edition v94.0b9

Steps to reproduce
CodePen Example

Enter "a" in the Email field.
Hit the enter key to submit the form (Note: moving focus outside the email field before activating the submit button with mouse or keyboard will also result in the same errors on both fields, but clicking submit with your mouse without first moving focus outside the email field causes an error message on just the email field, which may be a separate bug)

Expected behaviour

The name and email fields are both given aria-invalid="true" along with the error message and class
Actual behaviour
Only the email field is given aria-invalid="true" and both fields are given the error class. The name field does not have the aria-invalid attribute added, only the error message and the error class.

Screenshot is from Firefox developer edition.
After submitting the form following steps 1 and 2 under Steps to Reproduce, the following additional steps will cause the aria-invalid attribute to be added to an empty required field:

Move focus to the name field
Tab away from it without entering any content
Notice aria-invalid is added be added.

I mention this mainly for context/completeness.

Looks like aria-invalid is only ever set in the element function, which is not called for all fields when the form is submitted. It's not the submit event that's causing aria-invalid to be added for fields with other types of errors, it's happening because pressing enter to submit is also a keyup, and clicking/tabbing to a submit button is a focusout.

This issue persists in 1.19.5.  I assume this will not be fixed?

This should be re-opened and stale issues shouldn't be closed if they are waiting for the maintainers to comment on them. aria-invalid is a bit all over the place, none of my fields are marked invalid, however, when an invalid (required) field is then entered, aria-invalid='false' is added.


Instead of creating Fragment every time on menu click how it's possible to check by findFragmentByTag()?

  override fun createFragment(row: Any): Fragment {
    row as PageRow
    return PageFragment.newInstance(menuItem = row.menuItem)
  }
}```

I have just changed it to Kotlin,
and every time clicking menu item ,creates new instance of Fragment (edited)
my question how is it possible instead of creating check
by supportFragmentManager.findFragmentByTag()
and if it null then create ?

This sample has been migrated to a new location and updates are happening there (check README for more information).
As recommended by GitHub, we are closing all issues and pull requests now that this older repo will be archived.
If you still see this issue in the updated repo, please reopen the issue/PR there. Thank you!


Ashenafi: Check-Ins

Week 1 repo
Learning Objectives
🥚 Git Remote/Local Connection: I can:

[x] create a local git repository
[x] commit changes
[x]  connect a remote repository
[x]  push changes to the remote.

Linting: what is it? why does it matter?

[x] can write CSS & Markdown that passes a linting check

🥚 Git Branching Workflow: I can:

[x] manage your work locally using branches
[x] pull remote changes
[x]  create a new branch
[x]  push the branch to the remote repository
[ ]  open a PR with passing Continuous Integration checks
[x]  merge changes to main/master.

🥚 Command Line Interface (CLI): I can:

[x] navigate a directory
[x]  manage folders/files
[ ]  make small changes in a file using nano/vim, and much more (list coming soon).

🥚 NPM: You can:

[x] install npm dependencies
[ ]  use npm scripts (dev, lint and format)

🥚 Browser + DevTools: I can:

[x] open a local HTML/CSS project in your browser
[x]  inspect the elements
[x] emulate different devices
[x]  inspect the source

🥚 File Extensions: I can:

[x] identify all of the languages covered at HYF and give the correct file extension. (You don't need to know the languages, just recognize them!)

🥚 VSCode: I can complete these workflows in VScode, and can use keyboard shortcuts when possible:

[x] Opening a repository in a new window
[x] Opening the repository in VSCode terminal
[x] Adding a new file
[x] Adding a new folder
[x] Deleting a file
[x] Deleting a folder
[x] Previewing a Markdown File
[x] Opening an HTML file with the LiveServer extension
[x] Viewing the repository's git history with Git Graph extension

🐣 Touch Typing: I can:

[ ] write a README without looking at my keyboard to find any letters, numbers or special characters. (slowly is ok!)

🐣 User Stories: Given pictures of a website, I can:

[x] describe the page with user stories: As a type of user I can do something so that something good happens.

🐣 Planning and Collaborating: I can comfortably complete these steps of the Planning and Collaborating process described in the Student Guidebook:

[x] Repository Setup
[x] Project Definition
[x] Communication Plan
[ ] Backlog
[ ] Wireframe

🐣 Development Strategies: I can:

[ ] work as a group to follow the steps in a development strategy
[x]  reconstruct a web page when the code is provided.
🐣 Atomic Commits & Feature Branches: You can:
[ ] organize your development process using small single-purpose commits on feature branches. You will learn to develop each of these features on a separate branch and to merge it to main/master on GitHub when the feature is complete.

🐣 GitHub: I can:

[x] create new repositories
[x]  turn on GitHub Pages
[x]  connect the repository to your local computer
[x]  push/pull different branches
[ ] pass Continuous Integration checks for code linting and validation.

🐥 GitHub Collaboration: I can:

[x]  collaborate in a single repository and contribute a markdown file.
[x] create a new branch
[x] create and edit a file on that branch
[x] send a pull request
[x] address any requested changes
[x]  review +merge a classmate's pull request. (this can all be done from the GitHub UI)

🐥 Code Review: I can:

[x] use a code review checklist in a Pull Request to check a classmates code before merging.

Check In
What went well?

Creating issues and pull requests

Assigning people (including myself) for an issue and PRs

Cloning a repository using SSH

Creating a branch from the cloned (local) repository

Creating files in different directories/folders, making commits with commit messages to the branch using both Terminal and VS code

Pushing changes to remote repository

Creating a pull request and assign reviewers

Created a list of Git terminal commands and pull request for the vocabulary deliverable in the class repo

Discussions and supports among our group members

What went less well?

Unable to pass lint checks :wink:

Learning a lot of github jargons at the same time.

Unable to get a common time to discuss with all group members

I need help with

linting

Lessons learned

Git terminal is fast and reliable if you can use it correctly.

I realized GitHub is not only version controlling but much more than that.

Stack overflow is like a programming encyclopedia. A  lot of questions and helpful answers and discussions

I still need to learn a lot.

Study time

I have dedicated at least a few hours a day for my HYF class related activities

Preparation for Sunday class

I have briefly skimmed the contents of the planning and collaborating topic

Thank you @gelilaa  for the comments and  feedbacks.
I really hope I will be able to master Github in the coming weeks to take advantage of its features.
👏🙏🙏

Week 2

week 2 repo

What went well?

Creating issues and pull requests

Assigning people (including myself) for an issue and PRs

Cloning a repository using SSH

Creating a branch from the cloned (local) repository

Creating files in different directories/folders, making commits with commit messages to the branch using both Terminal and VS code

Pushing changes to remote repository

Creating a pull request and assign reviewers

Created a list of Git terminal commands and pull request for the vocabulary deliverable in the class repo

Discussions and supports among our group members

What went less well?

Unable to pass lint checks :wink:

Learning a lot of github jargons at the same time.

Unable to get a common time to discuss with all group members

I need help with

linting

Lessons learned

Git terminal is fast and reliable if you can use it correctly.

I realized GitHub is not only version controlling but much more than that.

Stack overflow is like a programming encyclopedia. A  lot of questions and helpful answers and discussions

I still need to learn a lot.

Study time

I have dedicated at least a few hours a day for my HYF class related activities

Preparation for Sunday class

I have briefly skimmed the contents of the planning and collaborating topic

Exercise repository (Week 2)
Learning Objectives (Week 2)

🐣 User Stories: Given pictures of a website, I can:

[x] describe the page with user stories: As a type of user I can do something so that something good happens.

🐣 Planning and Collaborating: I can comfortably complete these steps of the Planning and Collaborating process described in the Student Guidebook:

[x] Repository Setup
[x] Project Definition
[x] Communication Plan
[ ] Backlog
[ ] Wireframe

🐣 Development Strategies: I can:

[ ] work as a group to follow the steps in a development strategy
[x]  reconstruct a web page when the code is provided.

🐣 Atomic Commits & Feature Branches: I can:

[ ] organize your development process using small single-purpose commits on feature branches. You will learn to develop each of these features on a separate branch and to merge it to main/master on GitHub when the feature is complete.

🐣 GitHub: I can:

[x] create new repositories
[x]  turn on GitHub Pages
[x]  connect the repository to my local computer
[x]  push/pull different branches
[ ] pass Continuous Integration checks for code linting and validation.

🐥 GitHub Collaboration: I can:

[x]  collaborate in a single repository and contribute a markdown file.
[x] create a new branch
[x] create and edit a file on that branch
[x] send a pull request
[x] address any requested changes
[x]  review +merge a classmate's pull request. (this can all be done from the GitHub UI)

🐥 Code Review: I can:

[x] use a code review checklist in a Pull Request to check a classmates code before merging.

Check-In [Week 2]

Exercise repository ( week 2)

What went well?

My experience on how to use GitHub is getting better and better
Collaborating with teams to build a project
Creating exercise repo

setting up access management,
adding group members to the group repo,
setting up project board,
turn on discussions,
setting up live URL,
adding rules for code review for PRs,  etc of the exercise repo which is generated from a template repo .

Contributing to a project by following the planning and collaborating guides
Creating group issue in the class repository.
Creating pull request
Reviewing PRS
Able to write a code that passes all the checks

What went less well?

We couldn't manage to have a meeting with all members
Differences on understanding the assignment instructions among our group members. This opened a discussion that takes longer time than the actual project task. I guess this is expected. :smile:

I need help with

I feel I understand the lessons and assignments so far. Hence, I have no questions or don't need any help for now. :wink:
I am using googling for minor questions and doubts :smile:

Lessons learned

I learned the basic planning and collaborating skills every programmer/developer has to learn.

Preparation for Sunday class

I am reading on some of the suggested study materials for chapter 3 : Agile Development


Ph eval benchmarking

@yaseminbridges and I have merged all our changes into the structure of the project in 'main' and deleted the original directories. I'd like you to exercise some leniency with this as we're trying to align what we have (working code!) with the eventual destination of something different....
I'd rather have this in here now and refactor rather than have it languishing in a feature branch until its 'perfect'. For example, the exomiser directory will eventually need to come out into its own plugin project for pheval.
@yaseminbridges will work on making the code more testable and add some unit tests over the next few days, weeks...

@souzadevinicius has an exomiser plugin ready we wanted to handover to you.. Would you like to join us Thursday 3pm UK time for a hackathon so we show you how it works? This way we can do separation of concerns right from the start.

@souzadevinicius has an exomiser plugin ready we wanted to handover to you.. Would you like to join us Thursday 3pm UK time for a hackathon so we show you how it works? This way we can do separation of concerns right from the start.

Yes, this would be great.

@souzadevinicius has an exomiser plugin ready we wanted to handover to you.. Would you like to join us Thursday 3pm UK time for a hackathon so we show you how it works? This way we can do separation of concerns right from the start.

Happy to join

@yaseminbridges this is amazing and very impressive if I may say so. I did not do a proper code code review, but I looked through all of the files, the structure, and the design, and I love it. I will leave it to @souzadevinicius and @julesjacobsen to look a bit more closely at the code if they want, but from my perspective, this is good to go, and we can iterate in the future.
The one thing I would like to see is better documentation for all the utility commands, but we will deal with this once @souzadevinicius has set up a basic sphinx system.

Great! Went over the code today with @julesjacobsen and implemented the changes he has suggested. Once @souzadevinicius has gone over the code with any feedback etc I'll merge this branch in

:tada: Nice one @yaseminbridges !


multiplying durationMilliseconds by 1000

I (I say I, someone far smarter than I) had noted that the code (linked below) is just wrong:
https://github.com/appium-userland/appium-flutter-driver/blob/3eac68ffc7bf6f27cff0eeea11a6ceadfb2b9a81/driver/lib/commands/execute/wait.ts#L13
The documentation example as a result is also wrong:
https://github.com/appium-userland/appium-flutter-driver/blob/3eac68ffc7bf6f27cff0eeea11a6ceadfb2b9a81/example/nodejs/src/index.js#L147
example in test:
I would expect to be able to pass duration in milliseconds as standard, however, as it's being given as milliseconds*1000 it cause breaks all expectations and results in my day ruined:
driver.execute('flutter:waitFor', finder, 1);
expected approach:
driver.execute('flutter:waitFor', finder, 100);

For those that are having issues with this:
the finder function we have:
:
  async function isPresent(finder) {
    try {
      console.log(`Waiting 100ms for ${ finder }...`);
      await driver.execute('flutter:waitFor', finder, 1);
      return true;
    } catch (e) {
      return false;
    }

How it looks in test:
if (await assertionCommands.isPresent(find.byValueKey())) {
      await inputCommands //do all the fancy things you want to do
    }

I hope this helps someone. sharing is caring

Thank you. So, the * 1000 was redundant, correct?
I'm not the person who implemented it ordinally, so I just read https://github.com/flutter/flutter/blob/74cfc3db67dc89d617ebccd2763301777106c7fd/packages/flutter_driver/lib/src/common/message.dart#L18-L23 . I guess the endpoint to do flutter_driver command is expected milliseconds. then, actually * 1000 could be redundant in https://github.com/appium-userland/appium-flutter-driver/blob/3eac68ffc7bf6f27cff0eeea11a6ceadfb2b9a81/driver/lib/commands/execute/wait.ts#L13

^ correct on what you said.
The multiply here is completely redundant and can be removed. Soon as it is, I'll be able to pass through a normal millisecond parameter.

Personally, it makes sense to send ms as same as regular flutter driver side expectation. Let me create a draft pr.

https://github.com/appium-userland/appium-flutter-driver/blob/main/driver/CHANGELOG.md#170
1.7.0 has the change.


Problem with enter text when language is persian

When language is persian cant type everything .

Yes, RTL support has been added to Riot, and will be available on the next release


Move to @conventional-commits-rs

Hey!
Quick update on the future of this crate. I am in the process of building the conventional commits ecosystem over at @conventional-commits-rs for Rust based on already existing crates by forking them if unmaintained or complete new re-writes if that improves ergonomics and code quality.
Currently on the plan are:

commitlint, a simple commit linting tool. Can be used to verify that your commit matches organization-specific settings.
cargo-semantic, a cargo plugin used to create semantic releases. It automatically detects the changes and runs checks, tests, pushes the new tag and publishes to crates.io
Some kind of changelog generator.

Almost done are some generic utility crates for parsing and type definitions.
This repository will move in the near future over to the organization once I have implemented the linting tool. This puts all related crates into one place, allow for easier collaboration and (hopefully!) keep the fully automated release toolbox dream alive!
Cheers!

Thanks for the hard work! What's the status on @conventional-commits-rs? I'm having some trouble finding a good rust commitizen tool and would love to see this one get some love :)
Thanks!

University took most of my freetime up :( I hadn't really time to pick up the project again. Most of the stuff I program are assignments or tools to help me with assignments haha.
I'd be happy to get some help though! The parser has some smaller bugs. Might be worth thinking about moving to a grammar based one with pest for example.
The changelog generator is quite simplistic as well. It generates the whole document over again instead of parsing the existing one and doing a diff. This has some drawbacks. Manual editing is not possible for example.
I do have a month free, starting mid September. Ivr already put the org on the top of my to-do list.
I nerd the tools myself. I do use the existing ones. But they're buggy sometimes and not really user friendly right now.

Can we help in some ways? Because it seems an interesting and useful project :)


Web: Adding MSI support take 2

This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information

[x] The title of the PR is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
[x] Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
[x] If applicable, the PR references the bug/issue that it fixes.
[x] Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

[ ] I have read the contribution guidelines.
[ ] My spec meets the review criteria:

[ ] The spec conforms to the Swagger 2.0 specification.
[ ] The spec follows the guidelines described in the Swagger checklist document.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR.

@veronicagg

This is correcting PR https://github.com/Azure/azure-rest-api-specs/pull/1866

Thanks @LukaszStem . ARM had already signed off on the referred PR, so looks good to approve and merge now. Please see https://github.com/Azure/azure-rest-api-specs/pull/1824 for conversation details.

No modification for AutorestCI/azure-sdk-for-node

 https://github.com/Azure/azure-sdk-for-python/pull/1536

 https://github.com/Azure/azure-sdk-for-ruby/pull/1057


controller chart: trust-manager ClusterRole name collision

It would be helpful to have the ability to install a dedicated trust-manager with the ziti-controller because trust-manager can only have one "trusted namespace", and it needs to either be inside the same namespace as the controller or be configured to trust the controller's namespace. The trust-manager chart always creates a ClusterRole named "trust-manager", but it might be possible to override
{{ include "trust-manager.name" . }}

in https://github.com/cert-manager/trust-manager/blob/main/deploy/charts/trust-manager/templates/clusterrole.yaml#L6

If the name of the ClusterRole can not be set with a chart value, then it may be necessary to add a step to the controller install when it is desired to have multiple instances of Ziti controller in a single K8s cluster. The extra step would involve using Helm to render the manifests then patching with Kustomize to set the name of the clusterrole for that particular instance of Ziti.

The default ClusterRole name is overriden by .Values.nameOverride.


Video scales incorrectly when theater mode is enabled

Observed result (PROBLEM):

Minimal YouTube, theater mode scales the video to fit to width, which results in the top/bottom of the video getting cut off:

Expected result:

Regular YouTube, theater mode scales the video to fit to height, which doesn't result in any of the entire video getting cut off:

Probably best for scaling to consider both the width and height.


Explore idea of showing regional breakdown of employment for young people

A nice to have might be showing geographic breakdown (at something lower than regional). Data to be drawn from Annual Population Survey rather than census.
(If YFF ask, the census only shows data from 2021 whereas the APS is released quarterly.)

This feels like a nice to have, with a lot of other things on. As such, I suggest we close this?

Aye agreed, closing as not planned


sallacampus.fi

official website URL: https://peda.net/salla/sallan-lukio
official website where a long-term (>1 year) IT related course is offered: https://peda.net/salla/sallan-lukio

@ajlakanen Thank you for your patience while waiting for a review and processing your request. Pull request merged.
Please start requesting the licenses in about an hour, to let the changes to propagate through our system.


Menu misaligned after build 0.8.0_test

Build 0.8.0_test is working great for me (thanks a lot!), since 0.8.0_test2 the menu is misaligned again (my preferred resolution is 4587 x 1920 - NVIDIA DSR):

Could you probably keep the temporary solution for 3D menu elements being invisible at ultrawide resolutions as an OPTION, 0.8.0_test worked perfectly well for me ;)

So this could potentially break things in the 0.8.0 release compared to 0.7.9? If so, I will have to use 0.8.0_test for the time being...

Hmm, but for me 0.8.0 (release) causes those invisible labels, 0.8.0_test FIXES it. So I was thinking to keep the fix applied in 0.8.0_test as an option, I hope we have no misunderstanding...

Same issue here using 0.8.0 release

I didn't have this issue in 0.7.9 but now have it in 0.8.0. I have an ultra wide monitor if that helps and the only value I changed in the .ini are
Resolution = 0.5
Volume = 2.0

If you want to use the override for the master volume value I suggest to download “MetaphorFix_v0.8.0_test.zip” from this thread: https://github.com/Lyall/MetaphorFix/issues/22
This is the latest version which fixes the menus with my widescreen configuration, all (test) builds afterwards unfortunately cause those misaligned / invisible labels.

Fixed in 0.8.1 - again, thanks a lot!
I am pretty sure ATLUS is not going to fix most of the reported technical issues anytime soon and will never add features like increased draw distance or widescreen support as this would make the PC version too far superior compared to the console versions.
Your mods are truly essential for PC gaming and very much appreciated!


New release?

The latest release (v0.5.0) currently doesn't compile with the latest(v12.1.0) gcc with -std=c++20
This was fixed in #43, but it would be nice if there was a release that contains that fix.
Any plans for the next release?

Yes, hope to do a GitHub release later today. Thanks for the heads-up.

Just published release v0.6.0.

thank you :+1:


Packages loading texts from other packages.

Hello,
My project is having some troubles with using translations in multiple packages.
When using a text in package-1 it will search in the language file of package-2.
Imagine I have two packages with the following language files:
register-package:
  { 	"hello": "Hello", 	"sign_in": "Sign in", 	"sign_out": "Sign out", 	"welcome": "Welcome!"  }
login-package:
{ 	"test": "Test", 	"first_name": "First name", 	"last_name": "Last name", 	"login": "Login", 	"logout": "Logout", 	"welcome": "Welcome!"  }
When I want to get the string "login" on the login page it will show "login" on the front-end.
But when I move the property "login" to the language file of "register-package" it will load the right way.
Is there some way so I can make sure the code will search in its own package first?

Hey Jesse,
This issue seems to be a regression.
At the very moment, I am quite busy with other stuff for the next 3-4 weeks. Let me know whether you can try to debug the thing and make it work according to documentation, if guidance from me will be necessary let me know.
Thanks,
-Daniel

I am still experiencing this error.
Temporary fix was to move all translations to a global file.
This is not the fix I desire, but it works for now.

Hey, we published v2.0.1 that might address this issue. If it is still something you work on, please give it a try and let me know if it helped.


disabled hdf5 by default in external_stir.cmake

There was an issue, for me, where I could not use SIRF as it would throw a HDF5 related error whenever I tried to do anything with it. I have disabled HDF5 by default in External_STIR.cmake which solves the problem for me.

Can you give more information on the error? I'm not sure how HDF5 is used in STIR but it seems a shame to disable it if we can solve the problem.

Also, although it's not merged yet, https://github.com/CCPPETMR/SIRF-SuperBuild/pull/289 will mean that STIR variables are passed from the SuperBuild as cached variables. This would mean that your addition would have to be given as -DDISABLE_HDF5_SUPPORT:BOOL=ON. So if we accept this PR, that will have to be changed :)

Whenever I tried to do quite literally anything (either using the STIR binaries or importing SIRF in Python) I would get this error "terminate called after throwing an instance of 'H5::PropListIException'". I didn't try debugging it in a C++ IDE but I imagine that might help find the issue.
I have amended the PR as you asked

Ok, how about in External_STIR.cmake you create an option along the lines of STIR_DISABLE_HDF5_SUPPORT. Default to OFF. Then pass to STIR with:
-DDISABLE_HDF5_SUPPORT:BOOL=${STIR_DISABLE_HDF5_SUPPORT}

That way, for most users functionality will be unchanged, but you'll have the option to disable support.

I've made the change you suggested. The only reason I wrote it as I did in the first place is because I was told that it was expected for HDF5 support to be turned off when STIR was built using the superbuild, it can be on or off now.

Ok, I have no strong opinion as to what the default should be, I'll leave that for @KrisThielemans. The rest looks good for me.

This is fine for me, although we'll need to switch the default to ON once STIR Signa support has been merged (and we're using it in SIRF).
At present, STIR master nor 4.0.0-alpha doesn't use HDF5, so let's postpone merging this after tagging the SB for v2.1.

Note that the run-time error seenby @ALEXJAZZ008008 was most likely related to 2 different versions of HDF5 used for compilation/running.


Documentation

Steps to reproduce

Doing this to avoid the template bot

scroll down

and see what the actual issue is about

Expected behavior
We should have more robust documentation in the Wiki section of the repo
Actual behavior
There is currently no wiki
Crashlog
Nan.
Configuration
Version of the Plugin: 2.1.0
Platform: Android 10 / iOS 14
Device: e.g. iPhone X, Google Pixel 4
We Need a more robust Documentation section to help beginners. This is the best Bluetooth Library for Xamarin Forms and we need everyone to contribute as much knowledge as possible to the wiki section.
Things like;
Getting Started
Discovering Devices
Connected To Devices
Handling Disconnections
Handling Errors
Getting Services
Getting Characteristics
Getting Descriptors
Getting Data from a device
Streaming data from a device
Sending Data to a device
Getting response data from a device
Advanced Features
Best Practices
FAQs

Hi @ske66,
I'm the friendly issue checker.
Thanks for using the issue template :star2:
I appreciate it very much. I'm sure, the maintainers of this repository will answer, soon.


git-integration-api load configuration from env variables

Hi Curity,
first I want to thank you for this project.
I'd like to suggest adding a possibility to override configuration of git-integration-api service with env variables. This would be really helpful when deploying to k8s (and for example injecting secrets using external secrets operator).
Would you be interested in adding such feature here?

Thanks for the feedback - we added a small PR here. Let us know if this works for you and we will merge it.

Awesome, yes that works, thanks :)


⚠ Mobitopup has degraded performance

In 9391b01, Mobitopup (https://napcard.voz.tech) experienced degraded performance:

HTTP code: 200
Response time: 3260 ms

Resolved: Mobitopup performance has improved in 0a3d9d2.


S2 Popover token updates - color only

Description
Added net-new tokens:
Component-specific

popover-border-color

This color token was added into both light and dark sets. And variables were created in S2/Variables.

Motivation and context

These changes occurred as a result of scaling things for S2 design language and experiences.
Related issue
View Jira task
View Popover non-color updates PR

Types of changes

 [ ] Patch (bug fixes, typos, mistakes; non-breaking change which fixes an issue)
 [X] Minor (add a new token, changing a value, deprecating a token; non-breaking change which adds functionality)
 [ ] Major (deleting a token, changing token value type, renaming a token by deprecating the old one; fix or feature that would cause existing functionality to change)
Checklist:

 [X] I have signed the [Adobe Open Source CLA](https://opensource.adobe.com/cla.html).
 [X] I updated the token in all applicable sets. This applies if updating, adding, or deleting a token that has data across different sets (for example, if the value differs across color themes.)

TESTING spectrum2-colors
READING spectrum-tokens: /spectrum-tokens/packages/tokens/src/
READING   tokens studio: /spectrum-tokens-studio-data/src/tokens-studio/spectrum2-colors/
TOKENS STUDIO DATA IS COLOR ONLY
STUDIO SYNC SUMMARY
UPDATED METADATA - SPECTRUM UUID: spectrum2/component.Component.popover.border

SPECTRUM SYNC SUMMARY
NEW TOKENS: (1) popover-border-color

TEST COMPLETE

This is a new token in the color set. This set is synced with the figma variables collection. So, this PR should also show a new token in the $theme.json, unless you haven't synced the tokens studio data with Figma? Otherwise we will get the changes in another PR. That lead to confusion the other day cc @nabuhasan @lynnhao

@karstens @lynnhao I did sync TS with S2/Variables and I see the popover border color present for both themes. I also updated this information in both light and dark sets in TS JSON. Am I missing something?

This is a new token in the color set. This set is synced with the figma variables collection. So, this PR should also show a new token in the $theme.json, unless you haven't synced the tokens studio data with Figma? Otherwise we will get the changes in another PR. That lead to confusion the other day cc @nabuhasan @lynnhao

@karstens @lynnhao I did sync TS with S2/Variables and I see the popover border color present for both themes. I also updated this information in both light and dark sets in TS JSON. Am I missing something?

yes, there is something missing in this PR. In the $themes.json, there should be the mapping from the tokens studio token name to the figma variable ID. Did you run "create styles" or "sync styles"? I am not sure, why this is happing, I just know, that it is either a bug or something else...
See screenshot?

@nabuhasan did you create this PR before or after syncing the variables with Figma?

This is a new token in the color set. This set is synced with the figma variables collection. So, this PR should also show a new token in the $theme.json, unless you haven't synced the tokens studio data with Figma? Otherwise we will get the changes in another PR. That lead to confusion the other day cc @nabuhasan @lynnhao

@karstens @lynnhao I did sync TS with S2/Variables and I see the popover border color present for both themes. I also updated this information in both light and dark sets in TS JSON. Am I missing something?

yes, there is something missing in this PR. In the $themes.json, there should be the mapping from the tokens studio token name to the figma variable ID. Did you run "create styles" or "sync styles"? I am not sure, why this is happing, I just know, that it is either a bug or something else... See screenshot?

@karstens I didn't create or sync styles, instead I selected "Create variables", that's the action I take when there are new color variables we need to add and is also what we documented as our process.

This is a new token in the color set. This set is synced with the figma variables collection. So, this PR should also show a new token in the $theme.json, unless you haven't synced the tokens studio data with Figma? Otherwise we will get the changes in another PR. That lead to confusion the other day cc @nabuhasan @lynnhao

@karstens @lynnhao I did sync TS with S2/Variables and I see the popover border color present for both themes. I also updated this information in both light and dark sets in TS JSON. Am I missing something?

yes, there is something missing in this PR. In the $themes.json, there should be the mapping from the tokens studio token name to the figma variable ID. Did you run "create styles" or "sync styles"? I am not sure, why this is happing, I just know, that it is either a bug or something else... See screenshot?

@karstens I didn't create or sync styles, instead I selected "Create variables", that's the action I take when there are new color variables we need to add and is also what we documented as our process.
Also, I always pull updates in main then create a branch off of main, create or update what is required, then create variables (specifically for color tokens). My understanding is that once these are incorporated, then Cable runs a script to create styles (for any new additions) based on the latest changes in S2/Variables. Would it help to re-do this again and we delete this?

@nabuhasan Sorry, I meant "create variables" vs "sync styles". You are right and all that you describe sounds correct. The documented process, as well as the actions you list, as well as Cable's script to ”create the styles".
Did you create/sync the changes of this pr into a branch of the figma variables library? I think, if we don't merge this git branch, and so tokens of this PR are in a branch of the S2/Variables, that hasn't been merged yet, we could delete this and try again.

TESTING spectrum2-colors
READING spectrum-tokens: /spectrum-tokens/packages/tokens/src/
READING   tokens studio: /spectrum-tokens-studio-data/src/tokens-studio/spectrum2-colors/
TOKENS STUDIO DATA IS COLOR ONLY
STUDIO SYNC SUMMARY
UPDATED METADATA - SPECTRUM UUID: spectrum2/component.Component.popover.border

SPECTRUM SYNC SUMMARY
NEW TOKENS: (1) popover-border-color

TEST COMPLETE

Closing pull request to ensure the $themes.json includes the popover border color for light and dark. Will try including updates in a new PR.


A way to handle premium problems

need a way to filter out premium problems for people who don't have LeetCode premium

Might have to edit web scraper to check if it's premium (might also change JSON file format to include if isPremium)

how to handle the problem if it is premium? should the user be directed to lintcode?

If that problem exists on lintcode, I think that would work perfectly.
If not we can either filter the problems where isPremium is false and only use those questions.
Another option is in the popup.js/popup.html could have them toggle on/off premium problems.


Add ability to find all models matches a key and value

Tests not passing yet. Closing request without merge.


An index signature parameter type must be 'string' or 'number' - why not string | number?

This:
interface A {
    [key: string | number]: boolean;
}

specifies that the key must be either a string or a number, but produces an error saying that the key must be either string or number! But I guess this helps with clarity, ensuring that a value inserted with a string key "123" is not read with a number key 123 and vice versa.
But in the generic case:
interface A<K extends string|number> {
    [key: K]: boolean;
}

I could instantiate this with K = string|number, but more likely the intent is to pass one or the other, in which case this seems totally reasonable, but we currently can't do it.

But I guess this helps with clarity, ensuring that a value inserted with a string key "123" is not read with a number key 123 and vice versa.

Actually you can get a value inserted with a string key "123" by using the number key 123, but the reverse will result in an any.
Consider
interface Keyed {
  [key: string]: {};
}
interface Numbered { // This is just named "Numbered" for fun ;)
  [key: number]: {};
}

const x: Keyed = {};
const y: Numbered = {};

const a = x[1]; // {}
const b = y['1']; // any

Yes. number is convertible to string, so really (in the first example) string | number would effectively be equivalent to string, so in truth the existing behaviour doesn't help that much in the simple case, though with --noImplicitAny the reverse is properly caught.
This looseness extends to access via union key type:
declare const m: { [key: string ]: boolean};
declare const k: string | number;

m[k] = true;

However, the generic case (which is what I'm actually interested in) is a bit tighter:
function foo<K extends string | number>(k: K) {

    var m: { [key: string ]: boolean}; // try using string as workaround

    m[k] = true; // type K cannot be used to index...
}

So the indexer key type is string, and K is one of (string|number), string, number, all of which are fine outside generics. But instead it errors.
So the complete workaround is to use string as the key type and stick in a type assertion m[k as string] everywhere you use the indexer. Or equivalently, use 'number' and use m[k as number] everywhere. It doesn't matter which one you pick, as in the generic case the convertibility of number to string does not appear to be relevant.
My guess is that if an indexer could be declare with a generic key type, as long as that key type was one of (string|number), string, number, then no workaround would be needed.

I am not sure why this was closed?

I don't understand why this was closed too, but I did figure out how to work around the problem.
You basically can not use the OR | operator for types on a key, but you can define overloaded accessors of different types.
interface A<T extends string | number> {
    [key: string]: any;
    [key: number]: any;
}

If you are using the generics type to define the accessor for a function parameter. You have to define both types as string or number like this:
interface A<T extends string | number> {
    get(data: {[key:string]:any} | {[key :number]:any})
}

I see this as just a work around. If anyone has a better approach please share it.


[BEAM-670] BigQueryServicesImpl: fix issues in insertAll and add better tests

R: @lukecwik
CC: @vikkyrk

PTAL

LGTM

Travis is a flake (3/4 passed, 4th went into never land), Jenkins passed. Merging.


I couldn't run the Web Server

I followed the instructions given in this section Running the MQTT Broker and Web Server and I did all steps; however, I couldn't run the web server it gives me some errors(see the attached picture). I tried to refresh the webpage and no use. What you think I am doing wrong here?
FYI: I am running the web server on another laptop, not on my jetson nano. I am also using Ubuntu 20.4

Hi @alrah003, did you try restarting the docker-compose environment?


fix: display deprecation warning for simp lemmas on the lemma name

Closes #4452

In the Zulip chat it was suggested to add a test.  Would this (updated to the correct message) work?
import Lean.Elab.Command

@[deprecated]
theorem hi : True := .intro

open Lean Elab.Command
elab "msgs_lines " cmd:command : command => do
  elabCommand cmd
  let msgs := (← get).messages.unreported.toList
  if let [m] := msgs then logInfo m!"{(m.pos, m.endPos)}"

/--
warning: `hi` has been deprecated
---
info: (⟨20, 2⟩, some (⟨22, 3⟩))
-/
#guard_msgs in
msgs_lines
example : True := by
  simp [
    hi
  ]

In the Zulip chat it was suggested to add a test. Would this (updated to the correct message) work?

Haha, I like it. The traditional way is to do it like the tests in tests/lean/interactive/.

@semorrison I managed to get the tests correctly :) I don't think I can remove the awaiting-author label, so I assume the right thing is to ping you instead?

It seems that this was not fixed by #4484, please re-open if I am confused. Thanks for helping, though!

Absolutely, thanks for the fix!

I also tried the web-server and I can still see the old simp-underlining.  Would you mind also adding dsimp to the test, just to make sure that the same modifications fix both?  Thanks!

I also tried the web-server and I can still see the old simp-underlining.

Did you try the "Nightly" version of the webeditor? (go to settings and change the project) It seems to be as intended:
MWE on web editor nightly

Ah, no, I did not know that this was possible!  I can confirm that on the "nightly", the issue that I had raised is resolved, both for simp and for dsimp!
I am not really able to comment whether this is the "right" solution, but I would be very happy if this behaviour became standard!  Thanks!

Oh, I realize now that you are saying that this already is the behaviour, it just has not trickled down to Mathlib!  Anyway, this is great, thanks!

exactly, I assume that means it'll be in v4.10.0 and the corresponding rcs


Error in accessing post detail page due to missing reverse URL for category

Description:
When accessing a post detail page on the website, an error occurs indicating a missing reverse URL for the category. This error prevents users from viewing the post and disrupts the expected navigation flow.
Steps to reproduce:

Create a category in the admin site and assign it a slug of "webdev".
Create a post with a slug of "elite_class_app".
Navigate to the home page where all posts are listed.
Click on the post with the slug "elite_class_app" to open it.

Expected behavior:
The post detail page should open successfully, displaying the content of the post and any associated information.
Actual behavior:
Upon clicking the post, an error page is displayed with the following message:
NoReverseMatch at /post/elite_class_app/
Reverse for 'blog-category' with arguments '('Web Dev',)' not found. 1 pattern(s) tried: ['category/(?P<slug>[-a-zA-Z0-9_]+)/\\Z']

Additional information:
This error seems to be related to the reverse URL lookup for the category. The error message suggests that the reverse URL for the "blog-category" view with the argument "Web Dev" is not found. This issue prevents the post detail page from being accessed.
Proposed solution:

Investigate the existing URL configuration and ensure that the URL pattern for the "blog-category" view is correctly defined.
Verify that the slug used for the category matches the one specified in the URL pattern.
Check the corresponding view and template to confirm that the category information is correctly passed and rendered on the post detail page.

Alright

The issue might be that there is a space in the category name. I can look into this one.
Okay. Let me know what you come up with

I tried to reproduce this by creating a new category called "Web Dev" and it automatically changes to WebDev.
I think this category was introduced a while back before there was stricter rules on spaces in category names.
I suggest deleting that category and creating it again.
You shouldn't be able to get yourself into this situation again.

Are you sure this is the first step?

Create a category in the admin site and assign it a slug of "webdev".

If that is the case, the error shouldn't have a space in it. I think you might have two categories. One called webdev and another called Web Dev that was created a long time ago.
Please confirm for me.

I tried to reproduce this by creating a new category called "Web Dev" and it automatically changes to WebDev.
I think this category was introduced a while back before there was stricter rules on spaces in category names.
I suggest deleting that category and creating it again.
You shouldn't be able to get yourself into this situation again.

Okay, let me delete the category

Are you sure this is the first step?

Create a category in the admin site and assign it a slug of "webdev".

If that is the case, the error shouldn't show a category with a space in it. I think you might have two categories. One called webdev and another called Web Dev which was created a long time ago.
Please confirm for me.

No, I only have one category called "Web Dev". It's slug is "webdev"

I deleted and went over the whole process again, and I'm getting same errors

It breaks whenever I try to open the post after creation. I feel it could be from one of the templates

We had a zoom call about it and weren't able to figure it out.
I pushed some changes that will allow you to debug the application while it runs. Let me know if you can hit breakpoints and let's take it from there.

Fixed in https://github.com/jsolly/blogthedata/commit/f67d639e74e4311531151612077434788e610f58
The issue was that the URLs were using the category name and using the template option |slugify to turn it into a 'slug'
This only worked because the categories and names I have been using were very similar.
Now we only use the slug when manufacturing URLS for blog posts or categories.
@freedompraise is this working for you now?

Yes, it works for me