LDAP errors after upgrading Docker/Podman install from 2.x to 3.x

Describe the bug
After following the migration instructions and upgrading from OCIS 2.0 to 3.0, I am unable to log in. When I try to navigate to my instance, I get a login screen for half a second, then I'm redirected to an error page that says "Authentication failed" followed by "Please contact the administrator if this error persists."
My logs show:
{"level":"error","service":"idp","error":"ldap identifier backend get user error: user does not exist or too many entries returned","time":"2023-06-25T00:53:39.615054591Z","message":"IdentifierIdentityManager: fetch failed to get user from userID"}
{"level":"error","service":"idp","error":"ldap identifier backend get user error: user does not exist or too many entries returned","time":"2023-06-25T00:53:40.012277698Z","message":"IdentifierIdentityManager: fetch failed to get user from userID"}

(The line shows up twice every time I try to access the webpage.)
Steps to reproduce
Steps to reproduce the behavior:

Have a working OCIS 2.x Docker installation.
Stop the Podman container, pull the 3.0 image, and switch the Docker run command to 3.0.

Note: I did attempt to start the container multiple times at this point, which failed because the graph application ID was missing.

Add the graph application ID to ocis.yaml.
Delete all files under search/.
Ensure no users are accessing the instance.
Start the Podman container.

Expected behavior
Able to log in.
Actual behavior
Error message described above.
Setup
I'm running the official Docker image in a Podman container and am accessing the webpage via an Apache reverse proxy.
Additional context
This is the portion of the log from when the MessagePack migration was run; it included two LDAP errors (I am just using the default authentication mechanism within the Docker image, I do not have a separate LDAP server):
{"level":"info","root":"/var/lib/ocis/storage/metadata","time":"2023-06-25T00:41:14.540401064Z","caller":"github.com/cs3org/reva/v2@v2.14.0/pkg/storage/utils/decomposedfs/migrator/0003_switch_to_messagepack_metadata.go:45","message":"Migrating to messagepack metadata backend..."}
{"level":"info","time":"2023-06-25T00:41:14.668280604Z","caller":"github.com/cs3org/reva/v2@v2.14.0/pkg/storage/utils/decomposedfs/migrator/0001_create_spaces_directory_structure.go:33","message":"Migrating spaces directory structure..."}
{"level":"info","time":"2023-06-25T00:41:14.668864809Z","caller":"github.com/cs3org/reva/v2@v2.14.0/pkg/storage/utils/decomposedfs/migrator/0002_move_spacetypes_to_indexes.go:31","message":"Migrating space types indexes..."}
{"level":"info","root":"/var/lib/ocis/storage/users","time":"2023-06-25T00:41:14.669848662Z","caller":"github.com/cs3org/reva/v2@v2.14.0/pkg/storage/utils/decomposedfs/migrator/0003_switch_to_messagepack_metadata.go:45","message":"Migrating to messagepack metadata backend..."}
{"level":"error","service":"graph","error":"LDAP Result Code 200 \"Network Error\": dial tcp [::1]:9235: connect: connection refused","time":"2023-06-25T00:41:14.682578801Z","message":"could not get ldap Connection"}
{"level":"error","service":"graph","error":"LDAP Result Code 200 \"Network Error\": dial tcp [::1]:9235: connect: connection refused","time":"2023-06-25T00:41:14.682591635Z","message":"autoconnect could not get ldap Connection"}
{"level":"info","time":"2023-06-25T00:41:17.33888632Z","caller":"github.com/cs3org/reva/v2@v2.14.0/pkg/storage/utils/decomposedfs/migrator/0003_switch_to_messagepack_metadata.go:106","message":"done."}
{"level":"info","time":"2023-06-25T00:41:17.414632365Z","caller":"github.com/cs3org/reva/v2@v2.14.0/pkg/storage/utils/decomposedfs/migrator/0003_switch_to_messagepack_metadata.go:106","message":"done."}
{"level":"error","service":"proxy","error":"failed to verify access token: token is expired by 5m32.680410084s","authenticator":"oidc","path":"/api/v0/settings/values-list","time":"2023-06-25T00:41:41.681302293Z","message":"failed to authenticate the request"}
{"level":"error","service":"proxy","error":"failed to verify access token: token is expired by 5m32.698092228s","authenticator":"oidc","path":"/ocs/v1.php/cloud/user","time":"2023-06-25T00:41:41.699042617Z","message":"failed to authenticate the request"}

I had no further output after that until the LDAP errors previously described.

After realizing that idp is basically the web login page, I tried logging into the mobile app and it worked, so the issue is specific to the web login page (which is how I usually access my server.)
Not sure if https://github.com/owncloud/ocis/commit/7a4bc71e653d3dfe84bc2864f843cd8aeb9251a7 is related to this or will help in any way?

I should have tried this sooner, but logging in in a private window worked. I then cleared my cookies for this domain, and then I was able to load the login screen successfully and log in again.


Config should go into extra key

The way the configuration options are currently added to the autoload key in the composer.json file is incorrect, and causes the Composer files to not be validatable anymore.
Plugins should add all of their configuration to the extra key in the composer.json file instead, that's what this is for: https://getcomposer.org/doc/04-schema.md#extra
For backwards compatibility, the old key could still be supported, but users should be encouraged to move all configuration data to the extra key instead.

Thanks @schlessera! It was a silly decision on my part to allow one to use it from autoload.
I've been meaning to remove it and will do so as soon as possible.


Bug in Search

Description
When you search for a word and you select "Whole Word" option, DBeaver fails to match the whole word but instead contains other words with similar spellings. For example, as in the screenshot, I search for "status" and I select "Whole Word" option, it should find only the words "status". However, DBeaver also finds words like "statuses".

DBeaver Version
Version <IP_ADDRESS>407211303
Operating System
Windows 11 Enterprise
Database and driver
Server: Snowflake 8.27.1
Driver: Snowflake 3.14.4
Steps to reproduce
No response
Additional context
No response

Thank you for bug report.
It's a flaw of dark theme that selection and highlighting of the selected word occurrences have almost the same color.
It has yellow color in Light theme

You can turn off this option in preferences


[macOS] Add xcode 13.2.1

Description
Xcode 13.2.1 has been released.
Related issue:
N/a
Check list

[ ] Related issue / work item is attached
[ ] Tests are written (if applicable)
[ ] Documentation is updated (if applicable)
[ ] Changes are tested and related VM images are successfully generated

/azp run macos11, macos12


Add folds and inaccuracies to page

Hey, it is good to see that this thing actually works extremely smooth and i really appreciate the effort you put into this. But i want to ask from you that is there anything you can do to make these pages look less perfect??
I mean i did submitted the assignment but unfortunately my faculty was just too smart to caught me 😂 anyway but if there is something you could suggest me to edit the quality of pages or maybe introduce a random sequence of pages that'll look genuine.
These are too good to be true if you know what i mean.
If there's a way please do reply I'll really appreciate that!

I just had an idea of doing this! Lemme see if it works :D

oh oh we can already do this! Thank to #100 . You can click picture of a blank paper and upload it from the Upload Paper as Background option.


Login with ember.js app and JWT API

Hi,
I've an ember.js with JWT REST API as backend. Any chance to use with CASino auth?

Probably a proxy ticket. ?


Example section fails with 'NoneType' has no attribute 'strip'

Describe the bug
Example section does not work
To Reproduce
Try to render docs for Google style docstrings with an Example section. Here is a small repro based on https://sphinxcontrib-napoleon.readthedocs.io/en/latest/example_google.html#example-google:
(venv) paulius@xps:~/Documents/repro$ tree -I venv
.
├── docs
│   └── index.md
├── mkdocs.yml
└── repro.py

1 directory, 3 files

Contents of index.md:
# Welcome to MkDocs

:::repro

Contents of mkdocs.yml:
site_name: My Docs

plugins:
  - mkdocstrings

Contents of repro.py:
"""Example Google style docstrings.

This module demonstrates documentation as specified by the `Google Python
Style Guide`_. Docstrings may extend over multiple lines. Sections are created
with a section header and a colon followed by a block of indented text.

Example:
    Examples can be given using either the ``Example`` or ``Examples``
    sections.
"""

Bug
Upon running mkdocs server I get a rather large stacktrace, here is a truncated output:
(venv) paulius@xps:~/Documents/repro$ PYTHONPATH=. mkdocs serve
INFO     -  Building documentation...
INFO     -  Cleaning site directory
ERROR    -  Error reading page 'index.md': 'NoneType' object has no attribute 'strip'
Traceback (most recent call last):
  File "/home/paulius/Documents/repro/venv/bin/mkdocs", line 8, in <module>
    sys.exit(cli())
  File "/home/paulius/Documents/repro/venv/lib/python3.8/site-packages/click/core.py", line 1128, in __call__
    return self.main(*args, **kwargs)

[TRUNCATED]

  File "/home/paulius/Documents/repro/venv/lib/python3.8/site-packages/mkdocstrings_handlers/python/templates/material/_base/docstring/admonition.html", line 3, in top-level template code
    <summary>{{ section.title|convert_markdown(heading_level, html_id, strip_paragraph=True) }}</summary>
  File "/home/paulius/Documents/repro/venv/lib/python3.8/site-packages/mkdocstrings/handlers/base.py", line 219, in do_convert_markdown
    return Markup(self._md.convert(text))
  File "/home/paulius/Documents/repro/venv/lib/python3.8/site-packages/markdown/core.py", line 248, in convert
    if not source.strip():
AttributeError: 'NoneType' object has no attribute 'strip'

Information (please complete the following information):

OS: Ubuntu
mkdocstrings==0.18.0
mkdocstrings-python==0.5.2
mkdocstrings-python-legacy==0.2.1

Additional context
venv was created with the following requirements.txt:
mkdocs
mkdocstrings[python] >= 0.18
mkdocs-material

Thanks for the report, this is fixed in Griffe 0.11.5 :slightly_smiling_face:


[BEAM-6769] add it test for writing with bigquery io

This PR adds an IT test for writing data to BQ.
Discussion: https://issues.apache.org/jira/browse/BEAM-6769
Post-Commit Tests Status (on master branch)

Lang
SDK
Apex
Dataflow
Flink
Gearpump
Samza
Spark

Go

---
---
---
---
---
---

Java

Python

---

---
---
---

See .test-infra/jenkins/README for trigger phrase, status and link of all Jenkins jobs.

Run Python PostCommit

The test currently fails when writing b'\xab\xac\xad' to BQ in python 2:
beam.io.Create([{'bytes':b'\xab\xac\xad'}]) | beam.io.WriteToBigQuery(...)
This gives the following error:
ValueError: 'utf8' codec can't decode byte 0xab in position 0: invalid start byte.


support for doing action more than once

Similar to #3 but maybe a x2, x3 option that will repeat the previous action twice in one turn

Closing this as not planned (may revisit it later) because I don't think I'll be implementing this for the pokemon bot and I think we'll rely on #20 for increasing the number of actions taken


Fix some PropTypes validation errors when running the app and in test…

…s. r=bgrins

Coverage remained the same at 37.973% when pulling 9cbcd03453a0dbaf539ad159e995ae240c88eebe on jsantell:fix-some-prop-validations into 7e75d0b2a83fd50968c3e618a1ff6a8f6073080c on mozilla:master.

r+


Research moving API OpenID-Connect/OAuth2 support into configuration.

manageiq-api PR 737 added OpenID-Connect/OAuth2 support to the API.
It might be possible to simplify this solution by leveraging OpenID-Connect/OAuth2 setup in the mod_auth_openidc configuration files.
This issue will be used to track this investigation.

@miq-bot add_label core/authentication
@miq-bot add_label refactoring
@miq-bot assign @jvlcek

If this is not possible, then tests should be added to cover the code moved in #19936

Hi @jvlcek, was peeking at this today, looks like we should be able to protect our /api endpoint Location
using an AuthType of oauth20.  There's a good write-up on it at https://github.com/zmartzone/mod_auth_openidc/wiki/OAuth-2.0-Resource-Server
Hopefully we can kick the tire with some of these examples.

@abellotti Thank you for that pointer. I'm kicking away at the tires on it right now.


Update references, fix Dev15 build

Some (but not complete) fixes for plot integration tests. More to come. Also, separated SQL into a separate assembly so we don't need to ship DACfx assemblies as it is caused trouble. Separation also allows us to run with or without SQL Tools present (port from 0.5)
RHost is https://github.com/Microsoft/R-Host/pull/95

Do we block install if not on Update 3? If not, we should after this.
👍

We do

👍


[ICD] Implement client-side interaction buffering

Description
By definition, LIT ICD will not be reachable unless they have notified that they are available for communication. This implies that controllers will need to buffer their interactions until a LIT ICD checks in with a check-in message or subscription report.
Implement a buffering mechanism that stores all pending interactions until an ICD checks in.

https://github.com/CHIP-Specifications/connectedhomeip-spec/issues/7622
closed


[Spike or fix] E2E test flake in blockchain-api

Description
It's reported that the e2e tests for the blockchain-api project are failing with test flake a lot in the CI (but not locally). This makes it more difficult and frustrating to merge code, and reduces confidence in the test results.
Previously @dievazqu had spent some time investigating but could not find the root cause easily, so creating this ticket to block time to properly investigate.
Acceptance criteria

As we are unsure of the root cause, timebox this work to x days.
At the minimum, find the root cause. If time allows, fix the issue as part of this task or else create a new task to be prioritised.
the desired outcome is that tests should have at least 90% reliability (9/10 retries should be successful)

@dievazqu @kathaypacific I'd be happy to take a look at this code and see if I can help!


configmap not populating data in pod container env

This is a Bug Report

I have created a configmap from multiple files(Check below)
C:\shakti\K8s>kubectl get -o yaml cm teller-cm -n 106144-cicd-dev
apiVersion: v1
data:
options.defaults: |
PCEPAR_AUTHORIZATION_ROUTER_CONNECTION=localhost:8380
options.properties: |-
PCEPAR_MAIL_USER=ggamm
PCEPAR_MAIL_PW=ram
wlpoptions.defaults: |
PCEPAR_MAIL_USER=qq
PCEPAR_MAIL_PW=ww
kind: ConfigMap
metadata:
creationTimestamp: "2019-10-07T17:35:45Z"
name: teller-cm
namespace: dev
resourceVersion: "163984193"
selfLink: /api/v1/namespaces/dev/configmaps/teller-cm
uid: ee617869-a695-40cf-82dc-5f73e78638ff
Now i want to use this cm in my pod container environment(Check below the pod details)
apiVersion: apps/v1
kind: Deployment
metadata:
name: busybox
namespace: dev
spec:
selector:
matchLabels:
app: busybox
replicas: 1
template:
metadata:
labels:
app: busybox
spec:
terminationGracePeriodSeconds: 10
securityContext:
runAsUser: 99
runAsGroup: 99
fsGroup: 99
containers:
- name: busybox
image: /lrh7:latest
resources:
requests:
memory: "64Mi"
cpu: "3m"
limits:
memory: "128Mi"
cpu: "10m"
command: ["/bin/sh", "-c", "sleep 100000000 "]
envFrom:
- configMapRef:
name: teller-cm
restartPolicy: Always
But the problem is, when i am checking the pod env then it is also printing the file name, which i don't want. i only want to take content to env.
Proposed Solution:
I am not sure
Page to Update:
https://kubernetes.io/...

1.1.13

@shaktiprasadrath, GitHub is not the right place for support requests.
For help, check Stack Overflow.
You can also post your question on the Kubernetes Slack or the Discuss Kubernetes forum.
/triage support


WIP: COST-803: Grab the start/end dates from the pod usage report for the manifest

Need to finalize some things & add some more tests.

Codecov Report

Merging #57 (cff548f) into master (5702978) will decrease coverage by 0.39%.
The diff coverage is 72.22%.

@@            Coverage Diff             @@
##           master      #57      +/-   ##
==========================================
- Coverage   85.24%   84.85%   -0.40%
==========================================
  Files           9        9
  Lines        1159     1195      +36
==========================================
+ Hits          988     1014      +26
- Misses        112      117       +5
- Partials       59       64       +5

Flag
Coverage Δ

unittests
84.85% <72.22%> (-0.40%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

packaging/packaging.go
80.09% <72.22%> (-1.54%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 5702978...cff548f. Read the comment docs.

Codecov Report

Merging #57 (cff548f) into master (5702978) will decrease coverage by 0.39%.
The diff coverage is 72.22%.

@@            Coverage Diff             @@
##           master      #57      +/-   ##
==========================================
- Coverage   85.24%   84.85%   -0.40%
==========================================
  Files           9        9
  Lines        1159     1195      +36
==========================================
+ Hits          988     1014      +26
- Misses        112      117       +5
- Partials       59       64       +5

Flag
Coverage Δ

unittests
84.85% <72.22%> (-0.40%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

packaging/packaging.go
80.09% <72.22%> (-1.54%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 5702978...cff548f. Read the comment docs.


{AzureContainerApp} fixes Azure/azure-cli-extensions#5781 fix for 'NoneType' object does not support item assignment

fixes Azure/azure-cli-extensions#5781
fix for TypeError: 'NoneType' object does not support item assignment while running the az containerapp dapr enable command

This checklist is used to make sure that common guidelines for a pull request are followed.

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
The precondition is to put your code inside this repository and upgrade the version in the pull request but do not modify src/index.json.

AzureContainerApp

Hi, I've submitted as PR for this problem here: https://github.com/Azure/azure-cli-extensions/pull/5782

could you try to add test for the none type scenario in https://github.com/Azure/azure-cli-extensions/blob/main/src/containerapp/azext_containerapp/tests/latest/test_containerapp_commands.py#L583

@navba-MSFT Could you please resolve these CI issues?


[TISPARK-2] Update spark support to Spark2.3.0

we will jump to Spark2.3 from Spark2.1.1

run-all-tests

/run-all-tests

/run-all-tests

The CI failure concerning decimal multiplication seems to be a bug in Spark2.3.0. I have raised an issue in Spark JIRA SPARK-24468

/run-all-tests

/run-all-tests

/run-all-tests

/run-all-tests

/run-all-tests

Codecov Report

Merging #360 into master will decrease coverage by 0.03%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #360      +/-   ##
==========================================
- Coverage   55.72%   55.68%   -0.04%
==========================================
  Files         127      127
  Lines        5739     5734       -5
  Branches      862      861       -1
==========================================
- Hits         3198     3193       -5
+ Misses       2251     2249       -2
- Partials      290      292       +2

Impacted Files
Coverage Δ

...ap/tikv/expression/ComparisonBinaryExpression.java
84.72% <0%> (-2.78%)
:arrow_down:

...rc/main/java/com/pingcap/tikv/codec/MyDecimal.java
66.42% <0%> (-0.73%)
:arrow_down:

...ava/com/pingcap/tikv/region/RegionStoreClient.java
58.78% <0%> (+1.72%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e1f433d...127c765. Read the comment docs.

/run-all-tests

/run-all-tests

/run-all-tests

/run-all-tests

/run-all-tests

/run-all-tests

/run-all-tests

/run-all-tests

Please add a section of migration guide. The section should tell user how to modify the code. For example, if user uses map table functions, please tell them to change it. And we must test if the old style still works since user might have a lot of jobs that uses the old way to map table.

Totally copy all the files to new version is kind of ugly. What I actually expected is, make individual folders for those files not compatible only. If change is too much, you might consider let user use 1.1 release for 2.1 support and master and future version for 2.3.

Totally copy all the files to new version is kind of ugly. What I actually expected is, make individual folders for those files not compatible only. If change is too much, you might consider let user use 1.1 release for 2.1 support and master and future version for 2.3.

As a matter of fact most files have changed when we switch to Spark 2.3. I think it is appropriate to stop supporting Spark 2.1.

/run-all-tests

/run-all-tests

/run-all-tests

/run-all-tests

/run-all-tests

/run-all-tests

/run-all-tests

/run-all-tests


feat: implement file explorer component (closes #201)

What
This implements an explorer that gives you an overview of your file structure and lets you navigate it (described in more detail in #201)

Features

navigation to pages via files
saving/reading of explorer state (what folders are opened/closed)
supports infinitely nested folders
lots of config options to customize behavior

Config
Config options for explorer include:

title: title of explorer component (defaults to Explorer)
folderClickBehavior: either collapse (collapses folders when clicking on folder label) or link (navigate to folder overview page [e.g. advanced links to www.quartz.com/advanced)
folderDefaultState: either collapsed (all folders closed by default) or open (all folders are opened by default)
useSavedState: boolean, wether to read/save explorer state (what folders are opened)

How
The component only has access to allFiles as an array (includes all files + path). To make rendering the explorer easier/possible, I first bring all file paths into a tree structure FileNode (root path as root node, child paths as child nodes).
A main Explorer.tsx component renders the Explorer outline, while ExplorerNode.tsx recursively renders all folders + children and files.
All logic is in explorer.inline.ts, responsible for things like collapsing folders, navigating, handling events, saving/reading localStorage.
Bugs
The last remaining mildly annoying bug is that the explorer has empty scroll space at the bottom, unless all/a lot of folders are opened.

ready for review now @jackyzha0, updated the PR description and fixed all major bugs (from my testing)

found a different solution that uses flexbox (switches between flex 1 and 0) instead of calculating and setting maxHeight, gonna try to rewrite explorer to use that instead before merging (should be a lot more stable and cleaner)

I think we should try to use the title of the folder where possible (e.g. if a folder a has a file a/index.md we should use the title of that file. So the feature folder would be Feature List.
We should also add the ability for users to pass in a map function and a filter function so people can transform the display name for folders and notes and also hide unwanted ones (e.g. remove the tags folder)

offtopic but the grid based approach re-write also fixes the "whitespace at the bottom" bug. gonna first rewrite the explorer to use cleaner collapsables, then implement your feedback :)

I think we should try to use the title of the folder where possible (e.g. if a folder a has a file a/index.md we should use the title of that file. So the feature folder would be Feature List.
We should also add the ability for users to pass in a map function and a filter function so people can transform the display name for folders and notes and also hide unwanted ones (e.g. remove the tags folder)

those sound like good ideas and ill gladly work on them in the future/next few days, but i think we should first merge a "base state" of the explorer, that should already be working for basic use cases and the expand it afterwards in a separate PR to improve it with the features you mentioned. otherwise, people will have to be stuck waiting even longer until all the new enhancements are working as expected, the mapping might be a bit more complex and both mapping/filtering would take a lot of testing to make sure it works as intended.
the first part seems straight forward, but could you outline how you expect the maps/filter functions to behave in an issue or something? how do you expect the syntax for mappers/filters to look like/how would you like them to get passed? (as functions via options or some other way)

I now implemented all your feedback and switched out the collapsables internally (from annoying jank way with setting heights/pointer-events manually to new grid based approached that does all of that automatically and only requires the open class to be set to work).
Also made folder icons work only through css selectors, no more state set through JS required, automatically updates if open state changes. Fixed a few small bugs ive noticed while refactoring.
Is now open to be reviewed again, should be ready now.

I think we should try to use the title of the folder where possible (e.g. if a folder a has a file a/index.md we should use the title of that file. So the feature folder would be Feature List.
We should also add the ability for users to pass in a map function and a filter function so people can transform the display name for folders and notes and also hide unwanted ones (e.g. remove the tags folder)

those sound like good ideas and ill gladly work on them in the future/next few days, but i think we should first merge a "base state" of the explorer, that should already be working for basic use cases and the expand it afterwards in a separate PR to improve it with the features you mentioned. otherwise, people will have to be stuck waiting even longer until all the new enhancements are working as expected, the mapping might be a bit more complex and both mapping/filtering would take a lot of testing to make sure it works as intended.
the first part seems straight forward, but could you outline how you expect the maps/filter functions to behave in an issue or something? how do you expect the syntax for mappers/filters to look like/how would you like them to get passed? (as functions via options or some other way)

Sounds good, yup this is not blocking for me. I think passing in functions as props is fine for those. Map would take FileNode => FileNode, filter would take FileNode => bool

lgtm! final request: can you write a documentation page for the new component?

Yeah, was planning to do that anyways, but ill get to that tomorrow as its 1am here already :)
Also fixed the last 2 issues

Added documentation for this component now (open to feedback)


release: add release notes for v1.0.5

What is changed, added or deleted? (Required)
add release notes for v1.0.5
Which TiDB Data Migration (DM) version(s) do your changes apply to? (Required)

[x] master (the latest development version, including v2.0 changes for now)
[x] v1.0 (TiDB DM 1.0 versions)

What is the related PR or file link(s)?

This PR is translated from:
Other reference link(s):

@TomShawn @WangXiangUSTC PTAL


[FR] Fix typo "quelle en est"

Describe your changes
Fix typo "quelle en est l'utilité"
Related issue number or link (ex: resolves #issue-number)
N/A
Checklist before opening this PR (put x in the checkboxes)

[X] This PR does not contain plagiarism

don’t copy other people’s work unless you are quoting and contributing it to them.

[X] I have signed off on all commits

signing off (ex: git commit -s) is to affirm that commits comply DCO. If you are working locally, you could add an alias to your gitconfig by running git config --global alias.ci "commit -s".

LGTM 🚀


Second GO app fails to run on Dokku

The first Go app on Dokku runs smoothly. But when pushing the second Go app which is identical to the first one, its subdomain.domain.com couldn't be accessed. Chrome shows the common bad URL request message "This webpage is not available - ERR_NAME_NOT_RESOLVED"
I am using godep following this tutorial (http://www.mircozeiss.com/host-your-golang-app-on-digital-ocean) and only update Procfile to have different project's folder name.
Here is the simple Go app I pushed for the first(works very well) and the second(seems server not running). Please share your thoughts.
main.go
package main

import (
	"fmt"
	"log"
	"net/http"
	"os"
)

func handler(w http.ResponseWriter, r *http.Request) {
	fmt.Fprintf(w, "Hello...")
}

func main() {
	port := os.Getenv("PORT")
	http.HandleFunc("/", handler)

	log.Println("Starting web server on", port)
	if err := http.ListenAndServe(":"+port, nil); err != nil {
		log.Fatal("ListenAndServe:", err)
	}
}

Sounds like either DNS or DNS caching. Make sure the hostname is in DNS, you can dig your new hostname, flush your machine DNS cache and restart Chrome. (It has its own DNS cache)

If the flushing cache means this (http://osxdaily.com/2014/11/20/flush-dns-cache-mac-os-x), I've already done it. Not work. For the "dig" to hostname, I am not sure how to check them as both of them show some information with "dig".
Here are the two identical Go app I pushed to dokku.  Added A Record for the second. Thank you so much @josegonzalez @michaelshobbs


Balance and history flashing wrong values

on iOS created a new node.
The history and balance are flashing with something strange ( first video). When I received a deposit in the node then it continued to flash the history or history and balance (second video).
l-breez.logs (6).zip
https://github.com/user-attachments/assets/3141c1e9-78fc-46b4-9c35-f35fe95340bf
https://github.com/user-attachments/assets/d5b0c805-5fa7-4510-a952-b7de680d7145

This was fixed in the previous versions but reappeared again:
l-breez.logs (9).zip

This happened again in the 6150.1 TestFlight version with one difference.
Previously it flashed the wrong balance and history at any point.
Now it showed the wrong balance and history only before I made the first transaction for a new node.
Then It kept the correct balance and the history.
l-breez.logs (15).zip

@Nackoo2000 can you reproduce with 6193.1 on TestFlight?


After a rollback, Swap to 'e' on boss not working

I've been having a lot of issues with rollbacks lately, and I'm noticing that if my team advances into a boss zone while offline, they will not swap to the 'e' formation to get out of jumping to boss zones.
I suspect it has something to do with the dash wait. It wants to do the dash wait, but won't do it on a boss zone, so I think it just keeps the Q formation in until dash is active, then it will switch to the E formation to get out of the boss loop.
Steps to replicate (hard to do because it relies on server rollbacks):

Settings: swap to 'e' enabled, dash wait enabled
Stack wait triggered at farm zone (e.g., z291)
Server rolls back to earlier zone (e.g., z216), but team has auto progressed offline due to speed pots. Autoprogression took them to boss zone (e.g., z220)

Actual behavior: Team stays in Q formation, repeatedly jumping through several bosses until (I think) dash timer activates (roughly z300), then they will switch to E formation and attempt stacking again
Expected behavior: Team switches to E formation immediately to get out of boss zones, dash waits there (e.g., z221), then continues normal behavior, attempting stack again at stack zone (z291).

Dashwait did not allow for formation checks. I have added that to the waiting loop so ideally this particular situation will be fixed, but as noted, it's very difficult to reliably test.
Also, server rollbacks should mostly be going away soon (fingers crossed).
For now I'm going to mark this closed.


(litmus-docs) Provide navigation (table) to individual experiment docs

Update the chaoshub section in the litmus-docs to link to the detailed experiment docs. A table to map the experiment to the corresponding page in the Experiments section is desirable.

This is now available with Litmus Doc Vers. 0.9.0


mon: do not hardcode ipv4

Problem: fail to deploy a containerized Ceph cluster with ipv6
Solution: do not hardcode ipv4 when bootstrapping the container.
Now use ip_version: ipv6 to get a containerized cluster deployed with
ipv6.
Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=1451786
Signed-off-by: Sébastien Han<EMAIL_ADDRESS>

jenkins test kraken-ansible2.2-docker_cluster


Added German language support

Added German language support

Thanks so much Gabbalo! Are you happy for me to fix your issue #9 first? Then you can translate the other strings too and we can get them merged together? :)

Sure, sounds like a good idea :)

Okay, I've completed the language support in c93efb2 so if you could update your pull request with those new translations I'll merge it. I will prepare a release once that's done :)


ENH: reconfigure css style

@DrDrij I have reconfigured the css based on our discussion in https://github.com/QuantEcon/lecture-python-intro/pull/493. Is that what you recommend re: priorities to get the title style to override in the context of other themes?

[x] reconfigure css hierarchy for remark
[ ] reconfigure css hierarchy for other admonitions

Closing in favour of #111


Update package file to create a target.

Fix the swift package manager discrepancy

Oh great! Thank you very much for your help!


Add a "registerData" command to the daemon and client

A transaction is created that puts the data in the arbitrary data field and pays the transaction fee,, a wallet needs to be unlocked for this to work off course.
Documentation on how to do this through the api is required as well

Since we already have the sendcoins command its probably best to see if there is a way to add an optional flag to this command to set the arbitrary date first

@LeeSmet Would be a possibility but sendcoins is also a specialization of "create transaction".
I think it is more clear for users to have a seperate command, especially considering the importance tfchain gives to this feature.

I do agree with what @robvanmieghem says here now, it might be useful to have it as a separate commands. It would also allow us to add any logic custom to registration of data, in the near future. The command could be called RegisterData, but I'm open to the naming.

Allright, lets go with the separate command then. Do we also allow sending coins here or do we try to only register data (not sending coins except for the minerfee if possible, or the minimum we need to send otherwise)?

Do we also allow sending coins here

It's funny you mention, as we did also think about that possibility. I think we should allow to also add an extra amount of coins to be send. As there might be some use-case somewhere for that, but I can't think of any from the top of my hat.

Since registerdata is a convenience function, I would keep it like that f for now. Should the need arise to do both, lets see where to add it ( here, the sendcoins command or a  new one,...) And indeed, the minerfee should be added.

Since registerdata is a convenience function, I would keep it like that for now

This sentence confuses me, what exactly do you mean?

not adding functionality not required right now

not adding functionality not required right now

So just having the registerData handle data, rather than also allowing it to send some extra coins on top of that?


Refresh call fills dropdown with already selected values

in ui-select-multiple, the initial list is filtered correctly, but after a call to the server, the objects don't match up anymore and the refresh call won't filter values out.
In uiSelectController ctrl.refreshItems
var filteredItems = data.filter(function(i) {return selectedItems.indexOf(i) < 0;});

This will work when the selectedItem and the items in data match exactly, however when pulled from the server, the item in selectedItems isn't the exact same item as in data.
a fix for this is to change the filter function to do angular.equals like so

var filteredItems = data.filter(function(i) {
   for(var j in selectedItems) {
     if(angular.equals(selectedItems[j],i)) {
       return false;
     }
   }
   return true;
});

I'm using something like this:
<div ui-select-choices
    repeat="
        language.language as language in
        languages.sorted | filter:$select.search
    ">
        {{language.description}}
</div>

While your solution apparently fixes your use case, mine is still going to be broken, because this function does not account for the property used here (language.language); it will compare the full record to the language key, which will obviously not match.

Is there a way to obtain/reference the binding property from the alias that is used  (myobject.property from repeat="myobject.property as myobject in mylistofobjects")?

What's the correct way to expose an expression for the filter function?
var filteredItems = data.filter(function(i) {return filteredItemsFunction(selectedItems, i); }     );

Others?

One should probably look into implementing a filter on the user's side for this.
Going to close as something already doable.


Ism7MQTT not starting - v0.0.16

I am running HA on a RPi4, 2024.4.0, with Mosquitto Broker.
However the Add-On does not start
Logger: homeassistant.components.hassio
Quelle: components/hassio/websocket_api.py:135
Integration: Home Assistant Supervisor (Dokumentation, Probleme)
Erstmals aufgetreten: 23:31:44 (1 Vorkommnisse)
Zuletzt protokolliert: 23:31:44
Failed to to call /addons/bf7963f0_ism7mqtt/start - Unknown error, see supervisor
Who can help me locate my problem? Greetings, Lukas

And what does the addons's log say?

Thank you for asking :-) I hope you can help, since I am clueless
The addons log only states: "Aktualisieren" (=push for update)
When doing so, nothing happens, unfortunately.
Config file:
device_name: Wolf
interval: 60
additional_devices: []
debug_logging: true
mqtt_port: 1883
ism7_ip: <IP_ADDRESS>
ism7_password: xxxxxxx
Any clue?

I think this is a problem in your HA, not with the addon... What kind of install are you running? HAOS? Did you try a reboot?

I am running HAOS on a Raspberry4. And I have rebooted many times.
Would you know where on HA to find further logs (or other indications) which I could gather for you to get a better picture?
Many thanks, Lukas

Well, it tells you to check the supervisor logs, so that's a good point to start.

I just spent plenty of time looking through the various logfiles and found some other warnings. In order to clean up, I removed some items and did multiple reboots.
Now I was able to start the addon and it just started collecting data. I will observe an learn as i go :-)
Thank you for the assistance and the patience. And even a bigger thank you for the programming work :-)


Can't parse FIT file when ride on in-door bike trainer

Hi,
I rode bike on indoor trainer using Garmin Edge800.
python-fitparse can't parse this file.
Traceback (most recent call last):
File "test.py", line 13, in
activity.parse()
File "/Users/mitsukuni/tmp/python-fitparse/fitparse/activity.py", line 29, in parse
return_value = super(Activity, self).parse(*args, **kwargs)
File "/Users/mitsukuni/tmp/python-fitparse/fitparse/base.py", line 82, in parse
self._parse_file_header()
File "/Users/mitsukuni/tmp/python-fitparse/fitparse/base.py", line 288, in _parse_file_header
throw_exception("Invalid header size")
File "/Users/mitsukuni/tmp/python-fitparse/fitparse/base.py", line 278, in throw_exception
raise FitParseError("Bad .FIT file header: %s" % error)
fitparse.exceptions.FitParseError: Bad .FIT file header: Invalid header size

Could you attach the FIT file in question -- or email it to me privately<EMAIL_ADDRESS>It seems like it's in a bad state and can't be parsed.
Thanks,
David

I looked at your .FIT file in your fork of my library, sample-activity-indoor-trainer.fit. What version of the firmware do you have on your Edge 800?
It seems like the header in your file is of size 14, contrary to what the FIT SDK documents as being 12. The last two bytes are null and everything lines up properly. I'll update the code to work with such a file now.

You should be able to parse the file now via 9edc1b4. Thanks!

This file generated on indoor trainer without GPS by Garmin Edge800 with firmware version 2.40.
Thank you for your response & quick fix! cool!

Happy to help!


preferences.defaults is being overwritten

Describe the bug
I experienced this bug recently where after using the following function to "reset" all preferences to defaults, setting preference values then began changing the values in preferences.defaults
// preferences.defaults = { app: { hidden: null } }

for ( const [ key, value ] of Object.entries( preferences.defaults ) ) {
	preferences.value( key, value )
}

preferences.value('app.hidden', 'hello')
preferences.defaults.app.hidden
// 'hello'

Hi @lacymorrow
woops.. that's not so ideal :)
It's indeed an issue when you use the defaults object and use the objects of its properties to insert them into the preferences. That means in the above example your preferences.defaults.app is the same object as preferences.preferences.app. Changing either of them will change them in both places. Woopsie...
I'll try to reproduce this and probably fix it by returning a clone of the defaults when accessing them.


XGBoost not aware of CPU limit set by cgroups v2

When running XGBoost in a containerized environment, where cgroups v1 is used, the library is correctly aware of the CPU limits set by the cgroup and spawns the appropriate amount of threads to do its calculations.
But when running in an environment where cgroups v2 is used, XGBoost no longer recognized the limits. Instead, it's using the host machine's core count as a reference for how many threads to spawn. This almost definitely results in needless context switching. In one of our cases, we are seeing about ~300 times slower processing.
I believe this is the code that does not work with the new cgroups API: https://github.com/dmlc/xgboost/blob/4d7a187cb0ebc2194abc1efe0aaee6f06af937c5/src/common/threading_utils.cc#L34-L35
As a comparison, in a simple python:3.11-based container running in the cgroups-v2-environment, the "/sys/fs/cgroup" structure looks like this (I've removed the non-cpu "files" for readability):
/sys/fs/cgroup/cpu.idle
/sys/fs/cgroup/cpu.max
/sys/fs/cgroup/cpu.max.burst
/sys/fs/cgroup/cpu.pressure
/sys/fs/cgroup/cpu.stat
/sys/fs/cgroup/cpu.uclamp.max
/sys/fs/cgroup/cpu.uclamp.min
/sys/fs/cgroup/cpu.weight
/sys/fs/cgroup/cpu.weight.nice
/sys/fs/cgroup/cpuset.cpus
/sys/fs/cgroup/cpuset.cpus.effective
/sys/fs/cgroup/cpuset.cpus.partition
/sys/fs/cgroup/cpuset.mems
/sys/fs/cgroup/cpuset.mems.effective

For now, we have solved our issue by manually setting the OMP_NUM_THREADS and OMP_THREAD_LIMIT environment variables to the number of threads appropriate for our use case. But it would be nice if XGBoost can once again handle this on its own.

Could you please share how you use cgroup? What specific commands/system calls are you using to construct the subgroup?

Our processes are running in Kubernetes v1.25.11 with containerd as container runtime and systemd as the cgroup driver. We use the resource limit feature that Kubernetes provides out of the box, so the cgroups are constructed by the container runtime.
As additional context - we recently upgraded our Kubernetes cluster to v1.25, which brought the cgroups v2 as a default setting. Kubernetes v1.24 and below are using cgroups v1 by default.

Hi, could you please help review https://github.com/dmlc/xgboost/pull/9651 ?


Does not work properly with svelte-portal

When attempting to use svelte-floating-ui with svelte-portal the floating element initially renders in the wrong position. Resizing the window or closing and opening the floating UI fixes it (at least, closing and opening controlled by display: none/block;). If I were to make an educated guess I would say that the floating ui calcualtions are being done before the floating element is moved to the portal.
Here is some example code:

<button
  id={ariaMenuButtonId}
  type="submit"
  class="h-10 rounded-sm"
  aria-haspopup="true"
  aria-controls={ariaMenuId}
  on:click={() => {
    open = !open;
  }}
  use:floatingRef>Open</button
>

<Portal>

Menu Item

</Portal>

This appears to work:
6c6
<   const [floatingRef, floatingContent] = createFloatingActions({
---
>   const [floatingRef, floatingContent, updatePosition] = createFloatingActions({
14a15,18
>
>   $: if (open) {
>     updatePosition();
>   }

I wonder if there's a way to support this use case more automatically?

Hi!
Apparently this is due to the work of Portal, possibly due to the fact that it renders content outside of the parent component
There is an updatePosition for such situations, it is perfect for non-standard cases
Thank you for reporting this, I hope it helps the others ✨


Release v0.1.4

@JuliaRegistrator register
Release Notes: Renamed the routines foo_nodeformation_rescaled() -> foo_undeformed().

Registration pull request created: JuliaRegistries/General/112722
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.4 -m "<description of version>" 047d691c45dce997b80718ae965526b32a58b8b2
git push origin v0.1.4


Parameter 'using: node18' is not supported

Just for your information:

  deploy-to-render:
    name: 🚀 Update the demo stand on render.com
    runs-on: ubuntu-latest
    steps:
      - uses<EMAIL_ADDRESS>        with:
          service_id: ${{ secrets.RENDER_SERVICE_ID }}
          api_key: ${{ secrets.RENDER_API_KEY }}
          clear_cache: false

Workflow run: https://github.com/tarampampam/webhook-tester/actions/runs/3478776542/jobs/5816542046

@tarampampam Fixed, use 1.2.2 instead. Thank you.


[CircleGraph/test] Initial test for CircleGraphCtrl

This will introduce initial unit test for CircleGraphCtrl class.
ONE-vscode-DCO-1.0-Signed-off-by: SaeHie Park<EMAIL_ADDRESS>

from #966

Nowadays, we are too hard to create so many negative TCs.
So I was thinking following things

Integrating some positive TCs which are just copy & pasted test codes.
Excluding source codes from TC analysis which are too hard to validate by TCs because of UI, message communication, etc.

I am checking second option for now.
If second option is accepted, this PR can be closed.
Otherwise, I will ask you to integrate positive TCs into one.
Please wait a moment :)

Since #1082 is merged, could you determine whether this PR will be closed or we may go as it is? :)
I am not against with merging this PR. Actually many TC is always right :D
But just worried about "Can negative TC be created...?"

could you determine whether this PR will be closed or we may go as it is? :)

I'll check with test coverage :)


check performance on dashboard

10x slower than other pages. why?

added some performance tweeks, using joins, removed unused data and their queries. went down to 180 ms :)


Add NonParametricMachine class

Cool! I think this pretty much what we discussed @vigsterkr and @karlnapf? Just had some minor comments

@LiuYuHui could you push to https://github.com/shogun-toolbox/shogun/tree/feature/machine_refactor instead? Same with the KNN PR and all the machine refactor

looks good so far!

Shall we merge this and split things into smaller PRs? This is currently based on the feature branch


Refactor update coordinates to better handle multi-coordinate indexes

[x] Closes #7563
[x] Closes #8039
[x] Closes #8056
[x] Closes #7885
[x] Closes #7921
[x] Tests added
[x] User visible changes (including notable bug fixes) are documented in whats-new.rst

This refactor should better handle multi-coordinate indexes when updating (or assigning) new coordinates.
It also fixes, better isolates and better warns a bunch of deprecated pandas multi-index special cases (i.e., directly passing pd.MultiIndex objects or updating a multi-index dimension coordinate). I very much look forward to seeing support for those cases dropped :).

Can you check if this benchmark regression is real
indexing.AssignmentOptimized.time_assign_no_reindex

@dcherian the benchmark regression is fixed.
I think this is ready for review.
Regarding the multi-index deprecation warnings: there are still a lot of places where pandas.MultiIndex objects are passed around directly as coordinates in xarray's internals (both code and tests). They may also be promoted indirectly as in swap_dims(), which doesn't show any warning when this occurs. I will fix that in a follow-up PR.

Can you silence these two?

Do you mind if I address this in a follow-up PR? I started silencing warnings (there are a few dozen more in the tests!). Also there are still quite many cases where the warning should be emitted but is not (e.g., passing pd.MultiIndex as DataArray coords). This will need more review that is out of the scope of this PR.


Project organisation, features ideas and technical questions

Hello guys,
I have a few ideas of features, and one in particular that could help a lot for the contributions.
Project Tracker
I guess you also have some features in mind. Do you have any tracker like trello, or githubproject to have sort of a backlog of what you want to add ?
Features ideas

[ ] Simple account management (possible to use firebase), to store the data of the climber in the cloud instead of the phone. This way, if you uninstall the app, change phone or else, you can keep your climbing history.
[ ] Contribute within the application using the map (I can make a POC of that, without the webservices call). I guess there is an endpoint to make the contribution ?
[ ] Make the sync of the boulders/zones at start of the application instead of being in the app (which needs an update of the app every time someone contributes

Technical questions

For the contribution part, how does it work to push the data ? Is there an API to add new content ?
In the android app, I saw the link to an api, but it seems used only to get the picture?

For a little of background,
I used to work 4/5 years ago on a similar project of yours, which is not existing anymore ( except here https://apkcombo.com/fr/beautifulboulders-the-application-of-climbers/novajox.io.beauxbloc/ ) for many reasons. If you're interested I can give you the full story another time :D
In this project, I also used mapbox, with firebase to store the data on the cloud and make the sync at the startup of the app.
So I'm so happy someone did what I wanted to do so long ago and make it work, that's really awesome :)

Hey,
Thank you for your message!
With @wang-li  we're currently discussing the upcoming roadmap, we should have something to share next week hopefully.

Simple account management (possible to use firebase), to store the data of the climber in the cloud instead of the phone. This way, if you uninstall the app, change phone or else, you can keep your climbing history.

Yes that's a great idea, and it's very high in our wish list :)
We'll probably use our own Rails backend, though.

Contribute within the application using the map (I can make a POC of that, without the webservices call). I guess there is an endpoint to make the contribution ?

We've only built the website for now, so there's no endpoints. And I'm afraid it's not high on our todo list right now, so the website will have to do for now.

Make the sync of the boulders/zones at start of the application instead of being in the app (which needs an update of the app every time someone contributes

Yes, that's actually a topic we've discussed several times with @wang-li !
We'd love to make updates more seamless (and faster).
This may be a complex endeavor hower, with several technical implications.
I'd be happy if you or @wang-li worked on a proof-of-concept 👍
But maybe we should get you started on an easier feature? What do you think?

In the android app, I saw the link to an api, but it seems used only to get the picture?

Yes, only the photos for now.
We want most of our app to work 100% offline, that's why we use the local database.
We may also use webviews in the future.
We want to use our native skills only on screens with high value (lots of UI interactions, offline, used often, etc).
I'll get back to you soon about the roadmap.
Cheers!

Hey
Thanks for the feedbacks ;)
Yes for long term, It will be better to update on the rails part instead of using something like firebase or else.
I used it because it was easier for me at this time, but using Boolder own infra, you will handle better what is possible.
For the sync at start up we can discuss if u want :) tell me when!
Yep np for something easy to start with
Cheers


Name collision for Plugin christoomey/vim-tmux-navigator

Error detected while processing function vundle#config#bundle..10_check_bundle_name:
line    2:
Vundle error: Name collision for Plugin christoomey/vim-tmux-navigator. Plugin christoomey/vim-tmux-navigator previously used the name "vim-tmux-navigator". Skipping Plugin christoomey/vim-tmux-navigator.

You probably have vim-tmux-navigator listed in two .vundle files, check your ~/.vundles.local or ~/.vim/.vundles.local

I don't have a .vundles.local and nothing in either directory
I have a bundle/vim-tmux-navigator directory and vundles/vim-improvments.vundle that has 'Bundle "christoomey/vim-tmux-navigator"' but not duplication that I can find and I haven't added anything manually myself
Doing a search in all of yadr I find:
.yadr/vim/settings/yadr-keymap.vim:94:" NOTE: This has moved to vim/settings/vim-tmux-navigator.vim.
.yadr/vim/vundles/vim-improvements.vundle:12:Bundle "christoomey/vim-tmux-navigator"

Try rake update and make sure you have no local changes? I would also try to rm -rf ~/.vim/bundle/vim-tmux

@skwp i've run rake update and also removed .vim/bundle/vim-tmux-navigator and still getting error:
Error detected while processing function vundle#config#bundle..<SNR>10_check_bun
dle_name:
line    2:
Vundle error: Name collision for Plugin christoomey/vim-tmux-navigator. Plugin c
hristoomey/vim-tmux-navigator previously used the name "vim-tmux-navigator". Ski
pping Plugin christoomey/vim-tmux-navigator.


Smarti Config UI: Change deletion dialog

When an admin wants to delete a Smarti client in the web interface (UI), the system asks if the admin is sure about this operation. The "Okay" is pre-selected in this dialog. This is a potential threat because it does not prevent misuse and therefore data loss.
The scope of this issue is to redesign this dialog. Possible solutions are:

Pre-select the abort action in the dialog
Add an additional layer (ask two times: "are you really sure - this will result in data loss")
Eliminate "delete" option and replace with "deactivate" option.
Eliminate "delete" option and replace with "deactivate" option. A "delete" option is available when a client has been deactivated.

@ja-fra This looks much more beautiful :) Is the delete button still pre-selected?

Nope, nothing is pre-selected. Pressing Esc for "Cancel" is the only keyboard shortcut.


No information on where conf/application.conf is

The documentation says to edit this file but no information about where it's located. I tried looking in the sbt directory and there's no such file.

https://github.com/oktadev/okta-play-oidc-example/blob/master/conf/application.conf


[Feature]: <Mutation/> is good?

Package Scope
@suspensive/react-query
Description
We should make depth to use useMutation.
const ExamplePage = () => {
  const posts = usePosts();

  return posts.map(post => <PostToUseMutation key={post.id} post={post} />);
};

// PostToUseMutation (This unnecessary name  should be made to use only useMutation)
const PostToUseMutation = ({ post }: { post: Post }) => { // props should be drilled to use useMutation
  const postMutation = useMutation({
    mutationFn: ({ content }: { content: string }) => api.editPost({ postId: post.id}),
  });

  return (
    <>

{post.content}

      <textarea onChange={e => postMutation.mutateAsync({ content: e.target.value })} />
      {post.comments.map(comment => (
        <CommentToUseMutation key={comment.id} post={post} comment={comment} isPostLoading={postMutation.isLoading} />
      ))}
    </>
  );
};

// CommentToUseMutation (This unnecessary name  should be made to use only useMutation)
const CommentToUseMutation = ({ post, comment, isPostLoading }: { post: Post, comment: Comment, isPostLoading: boolean }) => { // props should be drilled to use useMutation
  const commentMutation = useMutation({
    mutationFn: ({ content }: { content: string }) => api.editComment({ postId: post.id, commentId: comment.id, comment }),
  });

  return (

      {isPostLoading ? <Spinner/> : null}
      {comment.content}
      <textarea onChange={e => commentMutation.mutateAsync({ content: e.target.value })} />

  );
};

Possible Solution
const ExamplePage = () => {
  const posts = usePosts();

  return posts.map(post => (
    <Mutation
      key={post.id}
      mutationFn={({ content }: { content: string }) => api.editPost({ postId: post.id, content })}
    >
      {postMutation => (
        <>

{post.content}

          {post.comments.map(comment => (
            <Mutation
              key={comment.id}
              mutationFn={({ content }: { content: string }) => api.editComment({ postId: post.id, commentId: comment.id, content })}
            >
              {commentMutation => (

                  {postMutation.isLoading ? <Spinner/> : null}
                  {comment.content}
                  <textarea onChange={e => commentMutation.mutateAsync({ content: e.target.value })} />

              )}
            </Mutation>
          ))}
        </>
      )}
    </Mutation>
  ));
};

No response
etc.
No response

I think it's a good attempt! It can reduce unnecessary files and manage them cohesively at the same depth, which will greatly impact productivity.

When I look at this example("Possible Solution"), it is inconvenient to be able to access posts from nested Mutation. Make it with each component will reduce side effects.
I was wondering you are inconvenient to make depth.

it is inconvenient to be able to access posts from nested Mutation. Make it with each component will reduce side effects.

What side effect is? More info is required to explain side effects

I was wondering you are inconvenient to make depth.

Yes I feel inconveniency to make depth because depth will casue to make unnecessary duplicated type definition (props), and unnecessary component name, inflexibility to change structure of components combination. It's same reason with <SuspenseQuery/> https://suspensive.org/docs/react-query/SuspenseQuery

When make component like PostToUseMutation and CommentToUseMutation.
It is not possible to modify posts inside either component.
When callbacks such as onError, onSettled, and onSuccess are added, I do not want to be able to modify the data of the parent component.
I think the example code should be changed like this.
const ExamplePage = () => {
  const posts = usePosts();

  return posts.map(post => <PostToUseMutation key={post.id} post={post} />);
};

// PostToUseMutation (This unnecessary name  should be made to use only useMutation)
const PostToUseMutation = ({ post }: { post: Post }) => { // props should be drilled to use useMutation
  const postMutation = useMutation({
    mutationFn: ({ content }: { content: string }) => api.editPost({ postId: post.id}),
  });

  if (postMutation.isLoading) {
    return <Spinner/>;
  }

  return (
    <>

{post.content}

      <textarea onChange={e => postMutation.mutateAsync({ content: e.target.value })} />
      {post.comments.map(comment => (
        <CommentToUseMutation key={comment.id} post={post} comment={comment} />
      ))}
    </>
  );
};

// CommentToUseMutation (This unnecessary name  should be made to use only useMutation)
const CommentToUseMutation = ({ post, comment }: { post: Post, comment: Comment }) => { // props should be drilled to use useMutation
  const commentMutation = useMutation({
    mutationFn: ({ content }: { content: string }) => api.editComment({ postId: post.id, commentId: comment.id, comment }),
  });

  return (

      {comment.content}
      <textarea onChange={e => commentMutation.mutateAsync({ content: e.target.value })} />

  );
};

After writing the example code, I can understand the advantages of the <Mutation> component. Rather than thinking of it as a comment about the <Mutation> component, think of it as a comment about the example code.


Add templates for PRs and issues

I based these templates of of what Swift and Swift-DocC use.
In the pull request template, I linked to the full docs for the Swift CI bot — but this repository only has some of its features enabled.  (For example, it doesn't support "test and merge".)  I'm not sure it's worth getting into that level of detail there.
Under the issues template, are there other links we should add?
For now, I'm leaving blank issues enabled to cover things that don't fall under either template, like adopting new features added to DocC or blockers for publication to Swift.org from this repository.
In the future, when we publish from this version, I'd expect us to add a specific template for updating the docs after a Swift Evolution proposal is accepted.
Instead of just reviewing the YAML version of in the issues template, I've temporarily turned on GitHub Issues in my fork, so you can preview the templates before we merge:
https://github.com/amartini51/swift-book/issues/new/choose

@franklinsch Please feel free to add others from the Swift Documentation work group who might be interested in this workflow discussion.


Skip product image upload page for pre-Brexit notifications

Products notified before Brexit don’t need to upload a product image.
https://regulatorydelivery.atlassian.net/jira/software/projects/COSBETA/boards/24?selectedIssue=COSBETA-700
Review app: https://cosmetics-pr-1426-submit-web.london.cloudapps.digital

@tobyhughes would you mind re-reviewing this? Review app at https://cosmetics-pr-1426-submit-web.london.cloudapps.digital


Wide Residual Networks on imagenet

Hi,
Is there a version that works on imagenet? I tried using the pytorch model definition, but I think it only works if input images are 32x32. Thank you!

@antspy yes I have the pytorch code to train WRN on ImageNet, will try to push it today or tomorrow

@szagoruyko  Great! Thank you very much :-)

@szagoruyko  Where can I find the WRN train on imagenet? will like to especially get the hyper-parameters. Thanks!

@szagoruyko   The code for imagenet implementing using PyTorch has been released?

This code should work: https://github.com/pytorch/vision/blob/c187c2b12d86c3909e59a40dbe49555d85b98703/references/classification/train.py
just need to set --model wide_resnet50_2 or --model wide_resnet101_2


move docs from codehaus

Site http://docs.codehaus.org/display/MVNCONFSITE is dead.
Maybe ask Atlassian to provide confluence hosting for this plugin?

Hi
Thx for feedback
Actually I used codehaus just to show plugin's documentation in confluence format (eat-your-food approach). The official documentation is here
I didn't know that codehaus hosting was discontinued :-(
Anyway I think to try with Atlassian as you suggest

I've move the confluence docs on my public space [here] (http://support.softphone.it/confluence/display/~bsorrentino/confluence-reporting-maven-plugin-4.4)

Thanks!


estimateDefaultBridgeDepositL2Gas documentation inconsistent with implementation

🐛 Bug Report for zksync-ethers JavaScript SDK
📝 Description
The estimateDefaultBridgeDepositL2Gas function (function definition) accepts an amount argument.
The documentation for this argument states  * @param amount The deposit amount.. However looking at the actual implmentation of estimateDefaultBridgeDepositL2Gas we see the following call to estimateL1ToL2Execute (function definition)
return await providerL2.estimateL1ToL2Execute({
      contractAddress: to,
      gasPerPubdataByte: gasPerPubdataByte,
      caller: from,
      calldata: '0x',
      l2Value: amount,
    });

In the estimateL1ToL2Execute documentation l2Value is described as  * @param [transaction.l2Value] The current L2 gas value..
Which seems to contradict the use of this field as the deposit amount.
As a result, a bridge interface that uses the documented way to estimate L2 gas price, will receive a different L2 gas amount, depending on token input amount - which from my understanding makes no sense.
IMO the documentation estimateDefaultBridgeDepositL2Gas needs to be updated. To my understanding, instead of the deposit amount - the caller has to provide the current L2 gas value.
🔄 Reproduction Steps
Implement the call as estimateDefaultBridgeDepositL2Gas and execute with varying amount.
🤔 Expected Behavior
All else being equal, the estimated gas price should not change if the caller is intending to bridge more or less tokens.
😯 Current Behavior
The estimate L2 gas price on deposit changes with the deposit amount.

Thanks for reaching out, this is the issue with the docs. The l2Value is not the current l2 gas value, we will change it in the docs and we will also change the parameter name to amount in some future release since that would be breaking change.


Problems occured when reimplement  COSOC

Hi, when i tried to reimplement COSOC, I was confronted with two problems:

Multi-GPU training: I followed the guidance "4. Training COSOC" and finished the training of examplar and  running of COS algorithm. However, when I tried to use 2 TITAN V(12G) GPUs to running FSL algorithm with COS, it would cause error "CUDA out of memory". More exactly, as long as validation went on, it would cause such a problem. (When training was on but validation hadn't start it went on normally.)
I didn't modify any hyperparameters, the batchsize in this stage is still 128.

Training with single GPU and smaller batchsize: Given the problem in 1, I also tried training on single GPU with batchsize=32(the max supportable bs). But the validation results seemed as if nothing had been learned (36/60 epochs):

It would be very thankful for your reply!

Hi, thanks for reporting the bug! It is now fixed, please try again. (modification of set_config_COSOC.py and SOC.py. I change the val shot, the learning rate and the epoch number, and also add a plugin that removes the warning.  A bug in SOC.py is fixed.)

Hi, thanks for reporting the bug! It is now fixed, please try again. (modification of set_config_COSOC.py and SOC.py. I change the val shot, the learning rate and the epoch number, and also add a plugin that removes the warning. A bug in SOC.py is fixed.)

Thanks for your responsible reply and solution! It now can be sucessfully trained with multi-gpus. I am waiting for a reasonable result and this may cost a period of time. Hope you would not mind  my keeping this issue open for some while.


Proposal: Move prisma2 CLI into @prisma/cli npm package

We're considering moving the prisma2 CLI from the prisma2 npm package into @prisma/cli similar to how ionic, Angular and vue are doing it.
Note that you'll still invoke the CLI via the prisma2 command. For a global installation, this would be the upgrade flow:
$ npm uninstall -g prisma2
$ npm install -g @prisma/cli

# Invoke the new CLI from the new package:
$ prisma2 --help

Note that we're planning to change the prisma2 command to prisma upon the upcoming Prisma 2.0 launch.
Pros
• Clearer package naming ("you know what you get")
• Easier to distinguish versions of individual packages
• More consistent: Unifying Prisma's tools under the @prisma npm scope
Cons
• Another breaking change
• Easier to find/remember/understand when CLI package name and command are identical (e.g. netlify-cli npm package and netlify CLI command is one additional thing to remember)

I know that everything is in development phase right now, but I would really consider to think the most about those things in the beginning. For the newcomers and the community itself is not best to change regularly names of those things. Take example of Photon and Lift, it was strongly communicated and now it is renamed. For my viewpoint it makes harder to wrap your head around prisma2 to keep updated to those late updates.

As mentioned in our internal discussion, moving @prisma/cli would break dx for npx as you would need to specify the package name if you don't have @prisma/cli locally installing:
npx -p @prisma/cli prisma2 .....

I think we should not move @prisma/cli unless we want to force global or local installation

Kinda torn on this one, I think the most important thing is getting to a decision now, and then sticking with it.
Imho having all packages under @prisma/xyz feels a little cleaner, especially with the plans to rename the command anyways, so there will be differences no matter what.

On the npx side, I'm not to sure people using prisma with npx is even something to strife for, since it makes versioning extremely unreliablle and adds some quite significant overhead every time a command is run. Might be fine for runnning anintrospect, but as soon as generate and migrate are a part of your workflow, npx shouldn't be a valid option anymore.

On the npx side, I'm not to sure people using prisma with npx is even something to strife for, since it makes versioning extremely unreliablle and adds some quite significant overhead every time a command is run. Might be fine for runnning anintrospect, but as soon as generate and migrate are a part of your workflow, npx shouldn't be a valid option anymore.

Common misconception about npx, unfortunately. If you have the package in your package.json and installed locally, it will just use the local package with almost no overhead. Then it is basically an alternative for npm scripts, without the need to edit your package.json.

Since npx has been brought up a few times, I want to add a bit more context around this.
The general recommendation for installation of the Prisma 2 CLI is (and will be) to install it locally as a dev dependency to avoid version conflicts.
When installed locally as a dev dependency, you can invoke the CLI by prefixing it with npx or yarn, see the CLI installation docs. This is / will be the recommended workflow for using the Prisma CLI going forward:
# npm
npm install prisma2 --save-dev
npx prisma2 # invokes the CLI

# yarn
yarn add prisma2 --dev
yarn prisma2 # invokes the CLI

So, another question of changing the npm package is what happens to the local installation and invocation flows. I've tested these scenarios with the @vue/cli package, here's the results.
The following just works:
npm install @vue/cli --save-dev
npx vue --help # invokes the CLI

and
yarn add @vue/cli --dev
yarn vue --help  # invokes the CLI

If you don't have the CLI installed (neither globally nor locally), you can invoke it via npx like so:
npx @vue/cli --help  # invokes the CLI

The following doesn't work though:
npx vue --help # doesn't work, the npm package name is missing

As we also own prisma, we could in theory make npx prisma (the last case, that does not work for npx vue) work and tell the use to use the correct command once (and uninstall the prisma package again (or even to it semi automatically in the postinstall). But that would still be confusing, because after adding the local @prisma/cli dependency, the same command that just told them to do someething would then be the valid command to use the CLI.

This is live for alpha with 2.0.0-alpha.973 and will also happen with the next preview release 🚀


[BEAM-10546] Remove util.timeout

util.timeout is obsolete since the resolution of BEAM-9009.

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

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

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

R: @udim


Publish version 1.0.0 to npm

@irskep I recently merged and created a version 1.0.0 with breaking change of using the new core package. But I don't have permission to publish, so who does that part? If you like I could try and setup CI to do it automatically like I did with the core.

I probably have to do something on the npm site. I'll try to do it this weekend.

In the past I've just published from the command line on my machine.

Here I am
https://www.npmjs.com/~jason-green
On Mon, 5 Nov 2018, 03:28 Steve Landey<EMAIL_ADDRESS>wrote:

What's your npm username?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/literallycanvas/literallycanvas/issues/532#issuecomment-435745020,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADUfF5YzHHu12JNfckcXBQ4IA8E3R8Muks5ur7BRgaJpZM4X8bxS
.


Fix message headers for different OS text sizes

Fixes #291

Automated message from Dropbox CLA bot
@borisyankov, it looks like you've already signed the Dropbox CLA. Thanks!


Update README

Adds better setup instructions, adds note about TypeScript support.
Closes #12

Coverage remained the same at 100.0% when pulling 197d5ac6f267c4fbb09080b78d5277fe03e058b4 on readme-update into e0a30aee49d053d68296d7b534e2150f35b26dad on master.

No it's because we set flow: true in the babylon options! :blush:


event onAdLeaveApp  is never raised

Hi!
I noticed that the event 'onAdLeaveApp' is never raised.
instead the event 'onAdDismiss' is correctly raised when the user drop the interstitial.
i need 'onAdLeaveApp' to detect when the user click the ADV.
The event doesn't work in TEST mode, neither in production mode...
is there something i'm missing?
thanks

Sorry, my fault. it was a problem in my code. closing.


Ignore directories when collecting files to lint

Summary

Fixes #5739
Test Plan

Manually tested:
$ tree dir
dir
├── dir.py
│   └── file.py
└── file.py

1 directory, 2 files

$ cargo run -p ruff_cli -- check dir --no-cache
    Finished dev [unoptimized + debuginfo] target(s) in 0.08s
     Running `target/debug/ruff check dir --no-cache`
dir/dir.py/file.py:1:7: F821 Undefined name `a`
dir/file.py:1:7: F821 Undefined name `a`
Found 2 errors.

Is a unit test needed?

Thanks for contributing @harupy!
Do you think you could write a unit test for this?

Unfortunately we don’t have any unit tests for the file discovery behavior right now, so we’d need to establish some new patterns.
We have some “manual” tests that are document expected behavior here: https://github.com/astral-sh/ruff/blob/main/crates/ruff/resources/test/project/README.md.
Alternatively we could add an integration test? Those can rely on the binary which would make the test itself easier to write (but the output harder to introspect).
I’m comfortable with any outcome including just doing some manual testing since it’s “no worse than before”.

(The logic looks correct to me.)

@charliermarsh Thanks for the comment. I'm trying to write a unit test. My local diff looks like this:
diff --git a/Cargo.lock b/Cargo.lock
index f3ce5f85e..428d00996 100644
--- a/Cargo.lock
+++ b/Cargo.lock
@@ -1893,6 +1893,7 @@ dependencies = [
  "smallvec",
  "strum",
  "strum_macros",
+ "tempfile",
  "test-case",
  "thiserror",
  "toml",
diff --git a/crates/ruff/Cargo.toml b/crates/ruff/Cargo.toml
index b659730d8..8d22661c1 100644
--- a/crates/ruff/Cargo.toml
+++ b/crates/ruff/Cargo.toml
@@ -83,6 +83,7 @@ wsl = { version = "0.1.0" }
 [dev-dependencies]
 insta = { workspace = true }
 pretty_assertions = "1.3.0"
+tempfile = "3.6.0"
 test-case = { workspace = true }
 # Disable colored output in tests
 colored = { workspace = true, features = ["no-color"] }
diff --git a/crates/ruff/src/resolver.rs b/crates/ruff/src/resolver.rs
index ccbd7ecc3..3f3cc39c5 100644
--- a/crates/ruff/src/resolver.rs
+++ b/crates/ruff/src/resolver.rs
@@ -435,10 +435,12 @@ mod tests {
     use anyhow::Result;
     use globset::GlobSet;
     use path_absolutize::Absolutize;
+    use tempfile::TempDir;
+    use test_case::test_case;

     use crate::resolver::{
-        is_file_excluded, match_exclusion, resolve_settings_with_processor, NoOpProcessor,
-        PyprojectConfig, PyprojectDiscoveryStrategy, Relativity, Resolver,
+        is_file_excluded, match_exclusion, python_files_in_path, resolve_settings_with_processor,
+        NoOpProcessor, PyprojectConfig, PyprojectDiscoveryStrategy, Relativity, Resolver,
     };
     use crate::settings::pyproject::find_settings_toml;
     use crate::settings::types::FilePattern;
@@ -605,4 +607,37 @@ mod tests {
         ));
         Ok(())
     }
+
+    #[test_case("py")]
+    #[test_case("pyi")]
+    #[test_case("ipynb")]
+    fn python_files_in_path_excludes_directories_that_look_like_python_files(
+        ext: &str,
+    ) -> Result<()> {
+        let tmp_dir = TempDir::new().unwrap();
+        let tmp_dir = tmp_dir.path();
+        let file = tmp_dir.join(format!("file.{}", ext));
+        let dir = tmp_dir.join(format!("dir.{}", ext));
+        let another_dir = tmp_dir.join(format!("another_dir.{}", ext));
+        let another_file = dir.join(format!("another_file.{}", ext));
+        std::fs::create_dir(&dir).unwrap();
+        std::fs::create_dir(&another_dir).unwrap();
+        std::fs::File::create(&file).unwrap();
+        std::fs::File::create(&another_file).unwrap();
+        let files = python_files_in_path(
+            &[tmp_dir.to_path_buf()],
+            &PyprojectConfig::new(
+                PyprojectDiscoveryStrategy::Hierarchical,
+                Default::default(),
+                None,
+            ),
+            &NoOpProcessor,
+        )
+        .unwrap()
+        .0;
+        assert_eq!(files.len(), 2);
+        assert_eq!(files[0].as_ref().unwrap().path(), another_file);
+        assert_eq!(files[1].as_ref().unwrap().path(), file);
+        Ok(())
+    }
 }

@charliermarsh I manually ran the commands in https://github.com/astral-sh/ruff/blob/main/crates/ruff/resources/test/project/README.md. Here are the results.
> cargo run -p ruff_cli -- check crates/ruff/resources/test/project/
   Compiling ruff_python_semantic v0.0.0 (/home/haru/Desktop/repositories/ruff/crates/ruff_python_semantic)
   Compiling ruff_python_formatter v0.0.0 (/home/haru/Desktop/repositories/ruff/crates/ruff_python_formatter)
   Compiling ruff v0.0.278 (/home/haru/Desktop/repositories/ruff/crates/ruff)
   Compiling ruff_cli v0.0.278 (/home/haru/Desktop/repositories/ruff/crates/ruff_cli)
    Finished dev [unoptimized + debuginfo] target(s) in 11.34s
     Running `target/debug/ruff check crates/ruff/resources/test/project/`
warning: Detected debug build without --no-cache.
crates/ruff/resources/test/project/examples/.dotfiles/script.py:1:1: I001 [*] Import block is un-sorted or un-formatted
crates/ruff/resources/test/project/examples/.dotfiles/script.py:1:17: F401 [*] `numpy` imported but unused
crates/ruff/resources/test/project/examples/.dotfiles/script.py:2:17: F401 [*] `app.app_file` imported but unused
crates/ruff/resources/test/project/examples/docs/docs/file.py:1:1: I001 [*] Import block is un-sorted or un-formatted
crates/ruff/resources/test/project/examples/docs/docs/file.py:8:5: F841 [*] Local variable `x` is assigned to but never used
crates/ruff/resources/test/project/project/file.py:1:8: F401 [*] `os` imported but unused
crates/ruff/resources/test/project/project/import_file.py:1:1: I001 [*] Import block is un-sorted or un-formatted
Found 7 errors.
[*] 7 potentially fixable with the --fix option.

> (cd crates/ruff/resources/test/project/ && cargo run -p ruff_cli -- check .)
    Finished dev [unoptimized + debuginfo] target(s) in 0.07s
     Running `/home/haru/Desktop/repositories/ruff/target/debug/ruff check .`
warning: Detected debug build without --no-cache.
examples/.dotfiles/script.py:1:1: I001 [*] Import block is un-sorted or un-formatted
examples/.dotfiles/script.py:1:17: F401 [*] `numpy` imported but unused
examples/.dotfiles/script.py:2:17: F401 [*] `app.app_file` imported but unused
examples/docs/docs/file.py:1:1: I001 [*] Import block is un-sorted or un-formatted
examples/docs/docs/file.py:8:5: F841 [*] Local variable `x` is assigned to but never used
project/file.py:1:8: F401 [*] `os` imported but unused
project/import_file.py:1:1: I001 [*] Import block is un-sorted or un-formatted
Found 7 errors.
[*] 7 potentially fixable with the --fix option.

> (cd crates/ruff/resources/test/project/examples/docs && cargo run -p ruff_cli -- check .)
    Finished dev [unoptimized + debuginfo] target(s) in 0.08s
     Running `/home/haru/Desktop/repositories/ruff/target/debug/ruff check .`
warning: Detected debug build without --no-cache.
docs/file.py:1:1: I001 [*] Import block is un-sorted or un-formatted
docs/file.py:8:5: F841 [*] Local variable `x` is assigned to but never used
Found 2 errors.
[*] 2 potentially fixable with the --fix option.

> (cargo run -p ruff_cli -- check --config=crates/ruff/resources/test/project/pyproject.toml crates/ruff/resources/test/project/)
    Finished dev [unoptimized + debuginfo] target(s) in 0.07s
     Running `target/debug/ruff check --config=crates/ruff/resources/test/project/pyproject.toml crates/ruff/resources/test/project/`
warning: Detected debug build without --no-cache.
crates/ruff/resources/test/project/examples/.dotfiles/script.py:1:17: F401 [*] `numpy` imported but unused
crates/ruff/resources/test/project/examples/.dotfiles/script.py:2:17: F401 [*] `app.app_file` imported but unused
crates/ruff/resources/test/project/examples/docs/docs/concepts/file.py:1:8: F401 [*] `os` imported but unused
crates/ruff/resources/test/project/examples/docs/docs/file.py:1:1: I001 [*] Import block is un-sorted or un-formatted
crates/ruff/resources/test/project/examples/docs/docs/file.py:1:8: F401 [*] `os` imported but unused
crates/ruff/resources/test/project/examples/docs/docs/file.py:3:17: F401 [*] `numpy` imported but unused
crates/ruff/resources/test/project/examples/docs/docs/file.py:4:27: F401 [*] `docs.concepts.file` imported but unused
crates/ruff/resources/test/project/examples/excluded/script.py:1:8: F401 [*] `os` imported but unused
crates/ruff/resources/test/project/project/file.py:1:8: F401 [*] `os` imported but unused
Found 9 errors.
[*] 9 potentially fixable with the --fix option.

> (cd crates/ruff/resources/test/project/examples && cargo run -p ruff_cli -- check --config=docs/ruff.toml .)
    Finished dev [unoptimized + debuginfo] target(s) in 0.08s
     Running `/home/haru/Desktop/repositories/ruff/target/debug/ruff check --config=docs/ruff.toml .`
warning: Detected debug build without --no-cache.
docs/docs/concepts/file.py:5:5: F841 [*] Local variable `x` is assigned to but never used
docs/docs/file.py:1:1: I001 [*] Import block is un-sorted or un-formatted
docs/docs/file.py:8:5: F841 [*] Local variable `x` is assigned to but never used
excluded/script.py:5:5: F841 [*] Local variable `x` is assigned to but never used
Found 4 errors.
[*] 4 potentially fixable with the --fix option.

> cargo run -p ruff_cli -- check crates/ruff/resources/test/project/examples/excluded/
    Finished dev [unoptimized + debuginfo] target(s) in 0.07s
     Running `target/debug/ruff check crates/ruff/resources/test/project/examples/excluded/`
warning: Detected debug build without --no-cache.
crates/ruff/resources/test/project/examples/excluded/script.py:1:8: F401 [*] `os` imported but unused
Found 1 error.
[*] 1 potentially fixable with the --fix option.

> cargo run -p ruff_cli -- check crates/ruff/resources/test/project/examples/excluded/ --force-exclude
    Finished dev [unoptimized + debuginfo] target(s) in 0.08s
     Running `target/debug/ruff check crates/ruff/resources/test/project/examples/excluded/ --force-exclude`
warning: Detected debug build without --no-cache.
warning: No Python files found under the given path(s)

> cargo run -p ruff_cli -- check crates/ruff/resources/test/project/examples/excluded/ --force-exclude
    Finished dev [unoptimized + debuginfo] target(s) in 0.08s
     Running `target/debug/ruff check crates/ruff/resources/test/project/examples/excluded/ --force-exclude`
warning: Detected debug build without --no-cache.
warning: No Python files found under the given path(s)

I like where you're headed with that test, but I'd also be fine to add tests in a future PR for all of this behavior holistically rather than trying to figure out the right pattern for this bug fix. I defer to @zanieb as first reviewer :)

I'd also be fine to add tests in a future PR for all of this behavior holistically rather than trying to figure out the right pattern for this bug fix.

+1

@zanieb Can you take another look?


initial commit of proposal

Project Abstract

Please replace these instructions with a brief description of your project summarising key points (1-2 paragraphs).
If your application is a follow-up to a previous grant, please mention which one in the first line of the abstract and include a link to previous pull requests if applicable.

Grant level

[ ] Level 1:  Up to $10,000, 2 approvals
[ ] Level 2:  Up to $30,000, 3 approvals
[x] Level 3:  Unlimited, 5 approvals (for >$100k: Web3 Foundation Council approval)

Application Checklist

[x] The application template has been copied and aptly renamed (project_name.md).
[x] I have read the application guidelines.
[x] Payment details have been provided (bank details via email or BTC, Ethereum (USDC/DAI) or Polkadot/Kusama (USDT) address in the application).
[x] The software delivered for this grant will be released under an open-source license specified in the application.
[x] The initial PR contains only one commit (squash and force-push if needed).
[x] The grant will only be announced once the first milestone has been accepted (see the announcement guidelines).
[ ] I prefer the discussion of this application to take place in a private Element/Matrix channel. My username is: @_______:matrix.org (change the homeserver if you use a different one)

 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.


Change in Maps UI

What is the issue?

Go to Navigation bar, then Travel, then Real Time Locator, or
Select on any destination, then Hangouts, Monument or any other map item,
On going to any of above two, the map opens up with a lit of items.
Right now, the map shown zero items & clicking on card item shows the item on map

What to do?

Create the UI similar to the below image. Show all the items on map at once & highlight the item when it's card is clicked

Also, the list view is horizontal right now. Make it vertical only.

Increase the zoom level (Right now, it is very less)

The text (description) on map items sometime shows html tags. The tags should not be there, they should rather be converted to formatted text.

Taking this up!


minor edits

Docs Build status updates of commit 9f7edad:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/apps-in-teams-meetings/enable-and-configure-your-app-for-teams-meetings.md
:white_check_mark:Succeeded
View

msteams-platform/apps-in-teams-meetings/meeting-app-extensibility.md
:white_check_mark:Succeeded
View

msteams-platform/bots/calls-and-meetings/registering-calling-bot.md
:white_check_mark:Succeeded
View

msteams-platform/bots/how-to/get-teams-context.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/authentication/authentication.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/authentication/configure-identity-provider.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/build-and-test/deep-links.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/deploy-and-publish/appsource/prepare/include-saas-offer.md
:white_check_mark:Succeeded
View

msteams-platform/graph-api/rsc/test-resource-specific-consent.md
:white_check_mark:Succeeded
View

msteams-platform/m365-apps/extend-m365-teams-message-extension.md
:white_check_mark:Succeeded
View

msteams-platform/m365-apps/extend-m365-teams-personal-tab.md
:white_check_mark:Succeeded
View

msteams-platform/resources/moodleInstructions.md
:white_check_mark:Succeeded
View

msteams-platform/resources/schema/manifest-schema.md
:white_check_mark:Succeeded
View

msteams-platform/samples/integrating-web-apps.md
:white_check_mark:Succeeded
View

msteams-platform/tabs/how-to/access-teams-context.md
:white_check_mark:Succeeded
View

msteams-platform/tabs/how-to/authentication/auth-aad-sso.md
:white_check_mark:Succeeded
View

msteams-platform/tabs/how-to/authentication/auth-flow-tab.md
:white_check_mark:Succeeded
View

msteams-platform/tabs/how-to/authentication/auth-silent-aad.md
:white_check_mark:Succeeded
View

msteams-platform/tabs/how-to/authentication/auth-tab-aad.md
:white_check_mark:Succeeded
View

msteams-platform/tabs/how-to/create-personal-tab.md
:white_check_mark:Succeeded
View

msteams-platform/task-modules-and-cards/cards/cards-format.md
:white_check_mark:Succeeded
View

msteams-platform/task-modules-and-cards/cards/people-picker.md
:white_check_mark:Succeeded
View

msteams-platform/task-modules-and-cards/what-are-cards.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/TeamsFx-collaboration.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/provision.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/use-CICD-template.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 1d34d11:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/apps-in-teams-meetings/enable-and-configure-your-app-for-teams-meetings.md
:white_check_mark:Succeeded
View

msteams-platform/apps-in-teams-meetings/meeting-app-extensibility.md
:white_check_mark:Succeeded
View

msteams-platform/bots/calls-and-meetings/registering-calling-bot.md
:white_check_mark:Succeeded
View

msteams-platform/bots/how-to/get-teams-context.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/authentication/authentication.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/authentication/configure-identity-provider.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/build-and-test/deep-links.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/deploy-and-publish/appsource/prepare/include-saas-offer.md
:white_check_mark:Succeeded
View

msteams-platform/graph-api/rsc/test-resource-specific-consent.md
:white_check_mark:Succeeded
View

msteams-platform/m365-apps/extend-m365-teams-message-extension.md
:white_check_mark:Succeeded
View

msteams-platform/m365-apps/extend-m365-teams-personal-tab.md
:white_check_mark:Succeeded
View

msteams-platform/resources/moodleInstructions.md
:white_check_mark:Succeeded
View

msteams-platform/resources/schema/manifest-schema.md
:white_check_mark:Succeeded
View

msteams-platform/samples/integrating-web-apps.md
:white_check_mark:Succeeded
View

msteams-platform/tabs/how-to/access-teams-context.md
:white_check_mark:Succeeded
View

msteams-platform/tabs/how-to/authentication/auth-aad-sso.md
:white_check_mark:Succeeded
View

msteams-platform/tabs/how-to/authentication/auth-flow-tab.md
:white_check_mark:Succeeded
View

msteams-platform/tabs/how-to/authentication/auth-silent-aad.md
:white_check_mark:Succeeded
View

msteams-platform/tabs/how-to/authentication/auth-tab-aad.md
:white_check_mark:Succeeded
View

msteams-platform/tabs/how-to/create-personal-tab.md
:white_check_mark:Succeeded
View

msteams-platform/task-modules-and-cards/cards/cards-format.md
:white_check_mark:Succeeded
View

msteams-platform/task-modules-and-cards/cards/people-picker.md
:white_check_mark:Succeeded
View

msteams-platform/task-modules-and-cards/what-are-cards.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/TeamsFx-collaboration.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/provision.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/use-CICD-template.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/apps-in-teams-meetings/enable-and-configure-your-app-for-teams-meetings.md
97
4
link
:white_check_mark:

msteams-platform/apps-in-teams-meetings/meeting-app-extensibility.md
96
10
link
:white_check_mark:

msteams-platform/bots/calls-and-meetings/registering-calling-bot.md
93
15
link
:white_check_mark:

msteams-platform/bots/how-to/get-teams-context.md
90
9
link
:white_check_mark:

msteams-platform/concepts/authentication/authentication.md
87
11
link
:white_check_mark:

msteams-platform/concepts/authentication/configure-identity-provider.md
87
4
link
:white_check_mark:

msteams-platform/concepts/build-and-test/deep-links.md
81
57
link
:white_check_mark:

msteams-platform/concepts/deploy-and-publish/appsource/prepare/include-saas-offer.md
96
8
link
:white_check_mark:

msteams-platform/graph-api/rsc/test-resource-specific-consent.md
88
11
link
:white_check_mark:

msteams-platform/m365-apps/extend-m365-teams-message-extension.md
91
35
link
:white_check_mark:

msteams-platform/m365-apps/extend-m365-teams-personal-tab.md
93
33
link
:white_check_mark:

msteams-platform/resources/moodleInstructions.md
91
26
link
:white_check_mark:

msteams-platform/resources/schema/manifest-schema.md
91
31
link
:white_check_mark:

msteams-platform/samples/integrating-web-apps.md
86
18
link
:white_check_mark:

msteams-platform/tabs/how-to/access-teams-context.md
89
15
link
:white_check_mark:

msteams-platform/tabs/how-to/authentication/auth-aad-sso.md
94
16
link
:white_check_mark:

msteams-platform/tabs/how-to/authentication/auth-flow-tab.md
87
11
link
:white_check_mark:

msteams-platform/tabs/how-to/authentication/auth-silent-aad.md
93
10
link
:white_check_mark:

msteams-platform/tabs/how-to/authentication/auth-tab-aad.md
81
39
link
:white_check_mark:

msteams-platform/tabs/how-to/create-personal-tab.md
99
10
link
:white_check_mark:

msteams-platform/task-modules-and-cards/cards/cards-format.md
90
23
link
:white_check_mark:

msteams-platform/task-modules-and-cards/cards/people-picker.md
100
0
link
:white_check_mark:

msteams-platform/task-modules-and-cards/what-are-cards.md
89
9
link
:white_check_mark:

msteams-platform/toolkit/TeamsFx-collaboration.md
97
9
link
:white_check_mark:

msteams-platform/toolkit/provision.md
92
58
link
:white_check_mark:

msteams-platform/toolkit/use-CICD-template.md
88
49
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.