How do I write vim-latex like custom key bindings into the Overleaf (Codemirror) editor?

I am aware that Tampermonkey (https://www.tampermonkey.net/) could potentially do this. For example, the first block shown below works, but the second doesn't.
`
// ==UserScript==
// @name         Overleaf Editor Custom VIM Keybindings
// @namespace    http://tampermonkey.net/
// @version      0.1
// @match        https://www.overleaf.com/project/*
// @grant        none
// ==/UserScript==
(function() {
'use strict';
window.addEventListener("UNSTABLE_editor:extensions", (event) => {
const { CodeMirror, CodeMirrorVim, extensions } = event.detail;
// add custom keybindings - insert mode applies on insert
CodeMirrorVim.Vim.map("jj", "", "insert");
`
This (the above) works fine but the below doesn't. How can I write these bindings into, say, a userscript for Overleaf?
'
//    CodeMirrorVim.Vim.map("kk", "Right-Right", "insert");
//    CodeMirrorVim.Vim.map("ECI", "\cite{<++>}<++>", "insert");
//    CodeMirrorVim.Vim.map("aa", "", "insert");
//    CodeMirrorVim.Vim.imap("`a", "\alpha", "insert");
//    CodeMirrorVim.IMAP('FMB', "\mathbb{<++>}<++>", 'insert');
'
Thanks!!
p.s. In vim-latex, there are built-in keybindings for different modes. E.g., in insert mode, typing a specific three-letter combination automatically creates an equation environment with placeholders "<++>" in it in the .tex file.
\begin{equation}
<++>
\label{<++>}
\end{end}
One can also create custom keybindings for vim-latex.

Do these work with the old editor?
Also is <++> creating placeholder a default feature in vim or is it implemented by a plugin?

I have not tried these with the old editor.
The <++> is not a vim feature, but an implementation by the vim-latex plugin. I am not sure if this is a possible thing in Codemirror, but I am curious if this can be done.

@dabingougou I'm in the same boat. Here is my current attempt - https://gist.github.com/llinfeng/f50211be8ff2c8816934da266403f47d. The first thing I'd like to solve is to jump to the corresponding line in PDF via <localleader>lv, or ;lv. In the gist, the function is already defined. I just need a way to use ;lv as a mapping in normal mode. This is filed in issue #88.

Looks like you'd like to replicate the following from vim-latex on Overleaf:

To insert snippets (templates) in insert mode, like `a for \alpha for inline arguments, and, say EIT, EQN ... for multi-line snippets, and
A way to jump to the next <++> markers, say, with <c-j>, both in Normal mode and Insert mode.

I think these are doable by writing custom functions in JavaScript and making use of the rich set of VIM Mode API. Let me know if you want to cost-share and outsource this to someone more proficient in JavaScript.

https://github.com/replit/codemirror-vim/pull/105 fixes input mode mappings, so CodeMirrorVim.Vim.imap("`a", "\\alpha", "insert"); should work after it is merged.
Since the <++> snippet, is not a vim feature, it can't be emulated with map, you'll need to define a command using snippet feature of codemirror, or do something else if <++> doesn't behave like textmate snippets.

With recent fixes for keytokey mappings imap should work, and c-j for <++> can be implemented via search. Closing the issue, but please comment or open a new issue, if you still need further help.


Chromebook got unstable when opening a folder.

My Chromebook got unstable when I tried to open some folders where even just tens of pictures or folders.
When this is happen, the following message is shown at the right bottom of the screen and Chromebook was about to freeze.
'''
操作に予想より時間がかかっています。
中止しますか？
'''
I checked the console log and found that there were a huge access to the samba share, perhaps due to the file app creating the thumbnails of these pictures or folder tree in the folder.
Console log can't be attached as there were some personal data.
My Chromebook environment is:
ASUS C200MA
Version 46.0.2490.82 (64-bit)
Platform 7390.68.0 (Official Build) stable-channel squawks
Firmware Google_Squawks.5216.152.28

@akimitsuy Yes, your guess is almost correct. The Files.app creates many events to the FSP implementation depending on files/folders you have. I want to know more detail. Could you provide me the structure of your files/folders simply? For example...
/
+ foo/
    - files (x 1,234)
    + bar/                      <- I clicked here!
        - files (x 387)
    + hoge/
    ...
+ baz/
...

Please find attached folder_structure.txt.
For example, when I clicked dir_691 or dir_346, my chromebook got slower, or almost frozen.
The size of files in dir_691 are around 7MB (1.6M pix jpeg) or 18MB (1.6M pix DNG raw).
OTOH, I can browse dir_1 normally.


Sign the pre-built binaries

Avoid download / runtime warnings if possible?

Not going to worry about this for now, with such a small number of users and updates to this tool.


Bot unable to complete prune request if it is unable to send messages

Describe the bug
Using the prune command in a channel where the bot is not allowed to send messages will result in a failure. Even though this message is not strictly needed and will often not even be seen before the prune happens.
To Reproduce
Steps to reproduce the behavior:

Remove the send messages permission from the bot for a channel
Use the prune command
Bot will be unwilling to prune

Expected behavior
Pruning as usual, just without the bot saying that it is fetching messages.

Issue cannot be replicated. Has likely been resolved over the past years via slash commands.


[CT-1890] Reintroduce logging to manifest generation

As part of the work in #6565, event logging in the parse task was removed. This ticket captures the work to reintroduce it to ManifestLoader.get_full_manifest, likely behind an optional flag. I believe the best method to achieve this is to pass in the fire_event function to the method, defaulting to a noop function.

We also have a "fire_event_if" function in core/dbt/events/functions.py


Use the right metrics annotations for the webhook service

Hi!
I think there is a typo here, leading to adding .Values.metrics.service.annotations to the webhook service, even with webhook.metrics.service.enabled set to false.
Also currently webhook.metrics.service.annotations is ignored.

Hey @Baldinof thanks for this fix, could you please sign your commit? :pray:

/approve


Popups can align incorrectly with their anchor

Describe the bug
When a ComboBox popup is opened, we noticed it located a pixel offset to the right in Windows 11 from its anchor parent as seen here:

To Reproduce
The above was reproduced with Fluent theme in a simple window on a Windows 11 system with this code:
<ComboBox HorizontalAlignment="Stretch">
	<ComboBoxItem Content="Item 1" />
	<ComboBoxItem Content="Item 2" />
	<ComboBoxItem Content="Item 3" />
</ComboBox>

Expected behavior
The popup should perfectly align with the ComboBox like here:

Cause
In the WindowImpl.Position property setter (link to line), the HiddenBorderSize is returned.  But for popups, it's returning (-1, 0).  Whereas it should be (0, 0).  That is what causes the one pixel offset to the right.
Desktop (please complete the following information):
Windows 11 (latest)

Looks like it must be this code which returns (-1, 0) as the HiddenBorderSize:
https://github.com/AvaloniaUI/Avalonia/blob/c59e63ef6f17bdd73116df8ce177de747f894510/src/Windows/Avalonia.Win32/WindowImpl.cs#L564
What are the values for clientRect.left,  frameRect.left and borderWidth there? (Sorry unable to check right now)

@grokys  clientRect and frameRect are all zeros.  borderWidth is 1.

Hmm ok. I'm no expert at win32, but I suspect that no invisible border is added for popups (or windows with CanResize == false probably?) so the SM_CXBORDER shouldn't be used in those cases. Unfortunately I don't think the person who originally wrote this code is even on GitHub to ask any more.

@grokys I tried setting CanResize = false but a regular window still has the 7px hidden border there.  My guess is that comes from WindowStyles.WS_OVERLAPPEDWINDOW.  Perhaps in HiddenBorderSize you could call GetStyle() and if the WindowStyles.WS_POPUP flag is set, return PixelSize.Empty?

I noticed something wrong too with ComboBox popup but believed it was an issue with border rendering... Now it make more sense! Thanks for pointing out this issue.


feature: generate phyiscal plan in DPhyp

Signed-off-by: xiejiann<EMAIL_ADDRESS>Proposed changes
Issue Number: close #xxx
Problem summary
Describe your changes.
Checklist(Required)

Does it affect the original behavior:

[ ] Yes
[ ] No
[ ] I don't know

Has unit tests been added:

[ ] Yes
[ ] No
[ ] No Need

Has document been added or modified:

[ ] Yes
[ ] No
[ ] No Need

Does it need to update dependencies:

[ ] Yes
[ ] No

Are there any changes that cannot be rolled back:

[ ] Yes (If Yes, please explain WHY)
[ ] No

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 35.07 seconds
load time: 633 seconds
storage size:<PHONE_NUMBER>6 Bytes
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20221226102432_clickbench_pr_68797.html


Fix/marathon race

Fix race condition in marathon configuration

looks good to me. just testing it now

works!


Transaction Failed Say Horizon Error

When I submit transaction I get error with transaction failed horizon error status 400? how i fix this
{
"type": "https://stellar.org/horizon-errors/transaction_failed",
"title": "Transaction Failed",
"status": 400,
"detail": "The transaction failed when submitted to the stellar network. The extras.result_codes field on this response contains further details.  Descriptions of each code can be found at: https://www.stellar.org/developers/learn/concepts/list-of-operations.html",
"instance": "horizon-live-001/RcwS4gjlor-240066901",
"extras": {
"envelope_xdr": "AAAAAPs/IfFolFceFp69zD1OyC1GMy5eQp8FsGUM+xorCrdPAAAAZACtjykAAAAEAAAAAAAAAAAAAAABAAAAAAAAAAEAAAAAOytLG+UpV8K00nAAF9xaHfbvhQv0syvZqxsuMx5DsYcAAAAAAAAAABHhowAAAAAAAAAAASsKt08AAABAyUqLzDKmQhIYceQuHVKkQLlsM+ncwtodI8Tvgl3OyJfQdPtCxQKU6Ctg5UDKpGdptMh8G3/bk2K+5O5pz8gIAw==",
"result_codes": {
"transaction": "tx_bad_auth"
},
"result_xdr": "AAAAAAAAAGT////6AAAAAA=="
}
}

have the same problem, not buying more

same problem using python sdk

tx_bad_auth error happens when transaction is signed for a different network or is signed using a wrong secret key. If you have more questions please ask at: https://stellar.stackexchange.com


Improve explanation about installing menus

As reported in https://t.me/grammyjs/53649

KnorpelSenf is flying right now. He got 3 approves in a row.


Mention quoting special symbols won't help

Why:

Closes [issue link]
What's being changed:

Check off the following:

[ ] I have reviewed my changes in staging. (look for the deploy-to-heroku link in your pull request, then click View deployment)
[ ] For content changes, I have reviewed the localization checklist
[ ] For content changes, I have reviewed the Content style guide for GitHub Docs.

👋 @jidanni Since we don't say anything in this article about using " for any other use case, we don't need a disclaimer that they won't work in this situation. I'm going to close this PR.
Thanks for your continued passion and interest in GitHub docs!


Changes to site configuration render longstanding kata unusable (aka old dog cannot learn new tricks)

"You can't teach an old dog new tricks."  Neither can an author of a longstanding kata fix content issues that arise due to website configuration changes, apparently.
First, this is not a report of a content issue; rather, it is an issue with the way the website enforces the content editing process.  This has resulted in at least one longstanding kata being totally unusable.  (At first I thought this was merely a content issue, but after reviewing the discussion thread and previous content issue reports, it looks like the content issue cannot be fixed by the author due to the website issue I am reporting here.)
What has apparently happened in the case I discovered is this:

A kata was created, emerged from beta, etc.
The kata was completed by a good number of people. (1500+)
Changes to the site configuration rendered the kata unusable
Users discovered that the kata is unusable and reported the issues to the author.
The author informed the users that he is unable to correct the errors, because he no longer has access to the kata.
About a year after the first sign of trouble, my home page directed me to the kata and I discovered that the test cases will not execute.  At first, I thought this was merely a content issue, and was about to report it to the author.  However, after looking at the other issues reported the author claims to have no access to the kata.  I have no other prior relationship to the author other than as a user of the kata.

Somewhere the process has broken down, because I as a user was directed to a kata that has been broken for a year, with an author who is now active on the site willing to correct the issue if he only had access to do so.  No mechanism in the website apparently exists to resolve this.  That's the bug.
Looking at the steps leading up to this issue, I asked myself, "Could any longstanding kata be vulnerable to this bug, if a content issue comes up due to configuration changes and the author is denied access to fix the content issue?"  The answer is apparently yes, so the scope of this is beyond the content of the kata in question.
Once again to me, as a user, this looks like a bug in the website that leads to content issues in a longstanding and active kata being unable to be resolved by the author.  Why was I directed to a dead kata?  Can it be revived?  Where do kata go when they die?  Is there a way to filter out dead kata so I don't have this problem again?  It is possible that a policy decision may need to be made in order to resolve this bug.
To emphasize, I, as a user do not care about the policy implications.  I am just noticing that my kata is broken, with no mechanism to either avoid or fix it.  The usual method of reporting the issue to the author seems to not be working since the author has no access.
Will this issue become more serious as more kata mature and die?  Can these "old dogs" adapt to new tricks / configuration changes?
The kata I discovered to be affected by this issue is www.codewars.com/kata/5255892719453db6d2000a23 (Part 1: Evil Programming Government Restrictions).  The discourse page of this kata has multiple issue reports starting from a year ago.  The author is responsive; however nothing can be done to correct the content bug, due to the website bug I am reporting here.
Perhaps other kata will be affected by this bug as well?

I agree, there is a gap in the process that needs to be filled. Its kind of both a bug and an enhancement for different reasons. One thing we could do is automatically open up the kata to allowing edits if more than maybe 3 or 4 issues are logged. Also the kata should be revalidated that its solution actually passes whenever a new issue is added. In this case that would have failed and then we could have automatically placed the kata back into beta.

Just noticed there were some ideas in #163 about this as well, so I am cross-referencing here.

See #317, #320...

This issue is largely resolved with the recent 500 limit per-language change. We also now show issues within the kata header so users are aware that the kata may have problems. I'll leave this open as a reference for possible future enhancements but I think the severity of the issue has been minimized with recent updates.


Fixes iOS battery level

Description
On iOS the battery level was always -1, even on a real device.
Checklist

[x] I have tested this on a device/simulator for each compatible OS
[ ] I added the documentation in README.md.
[ ] I mentioned this change in CHANGELOG.md.

@machour should close in favor of #404 - it should be enabled once in AppDelegate not toggled off and on, so it's a documentation update really


#46

This PR is to resolve issue #46

Created class BalanceParentheses in Interview_Questions
testing a variety of sample input that will result in both types of output (yes/ no)
helper functions for logic used by the balanceParentheses function

Can you please add "hacktoberfest-accepted" label?

Can you please add "hacktoberfest-accepted" label?


Update data.json

I believe this project here: https://github.com/manuelruder/artistic-videos, Is the implementation for the "Artistic style transfer for videos" research paper here: https://arxiv.org/pdf/1604.08610v1.pdf
Neural-Style is probably the best implementation of Artistic Style Transfer, even Artistic-Videos, is based off it. The github wiki page for Neural-Style contains many similar projects. https://github.com/jcjohnson/neural-style
This is the implementation of the research paper described in the most recent video: https://github.com/junyanz/iGAN

I am unsure of what the syntax looks like for multiple implementations

Thank you so much for the contributions! I will accept all the changes once you are completed. Will you add the "Artistic style transfer for videos" paper to the "papers" array in the "StyLit, Illumination-Guided Artistic Style Transfer" video?

You can add multiple "implementations" and "papers" by separating each string with a comma and space.


Customize steering wheel rotation Angle

When I pass in a range of 180° through options, I can only go to 270°  .
I hope you can help me deal with it. Could you relax the rotation Angle that can be customized  .
The initial determination is in the setRange function at line 222 of the index.js file

Ah, I will need to get my wheel out of storage to test.
In the meantime, can you post the code you are using here? Where you are passing the options. That way I could use the same code once I get my wheel.

Thank you very much for helping me solve the problem so late. I am very happy and wish you a happy Christmas Eve .
My test code is listed below, please help to have a look, if you need other support, please contact me in time, thank you very much !
`const JoyG29 = require('logitech-g29');
const exec = require('child_process').execFile;
// I have to start  Logitech G HUB to get wheel data.
function turnLogitechExe() {
console.log("turn up Logitech G HUB!");
let execCmd = exec("C:/Program Files/LGHUB/lghub.exe", function (err, data) {
if (err) {
console.log(err);
}
});
execCmd.on('exit', (code) => {
console.log(get execCmd code: ${code});
})
}
// turnLogitechExe();
// I need to set the G29 wheel Angle to only rotate 90° left and right.
const options = {
autocenter: [1, 0.2],
range: 180,
}
JoyG29.connect(options, function (error) {
console.log('Ready')
})
JoyG29.on('changes', (data) => {
console.log(G29 data: ${data})
})
JoyG29.on('shifter-gear', (data) => {
console.log('shifter-gear: ' + data);
})
JoyG29.on('error', (error) => {
console.log(G29 is error!);
});`

Sorry for the delay. I retrieved my Logitech wheels from storage today and hope to be able to test with them a bit later today.

Good news. ^_^
I've been experimenting on my own local computer. I modified the setRange function in code/index.js line 222 to disable the 270 minimum range. The code below is what I disabled.
// if (options.range < 270) {
//     options.range = 270
// }

I then used the code below to test with.
const JoyG29 = require('logitech-g29');

const options = {
    autocenter: [1, 0.2],
    range: 180,
}

JoyG29.connect(options, function (error) {
    console.log('Ready')
})

JoyG29.on('changes', (data) => {
    console.log(data)
})

JoyG29.on('error', (error) => {
    console.log('Error', error);
});

The wheel does indeed report a full turn when rotated 90 degrees left or right. The wheel will resist turning more than 90 degrees but you can overpower it. I believe that is just how the Logitech wheel works. There is only a hard stop physically once you keep spinning the wheel in either direction.
So, I am not sure why I originally had a 270 degree minimum range set. Probably something I read in some specs somewhere or perhaps it was a limitation of the older G27 wheel that this G29 library came from. Either way, I will update the code and let you know once it is available here on GitHub and on NPM.

Updated version 1.3.0 is live here on GitHub and also on NPM (https://www.npmjs.com/package/logitech-g29)
Please update your library to 1.3.0 and then try setting your range to 180 to get 90 degree turns on either side of the wheel. ^_^

十分感谢，我今天升级到v1.3.0，使用方向盘测试正常，旋转角度已经能够达到180°.

Thank you very much. Today, I upgraded to V1.3.0. The steering wheel test is normal, and the rotation Angle can reach 180°.

Excellent. I will close this issue.
Happy coding. ^_^


Ported flavortext.h from Singularitron to Python

i am a stupid...
Did so many things wrong.
thanks for not merging


bug: "Returns:" section is not shown

Description of the bug
The "Returns:" section is not displayed for a function with the return value annotated.
To Reproduce

Run the following commands:
git clone https://github.com/mkdocstrings/griffe-typingdoc.git
cd griffe-typingdoc/
make setup

Append the following lines to the docs/examples/simple.py:
def return_value(
    param: Annotated[int, Doc("Parameter")],
) -> Annotated[int, Doc("Returned value.")]:
    """Showing off return values."""

Then serve the documentation:
make docs

Full traceback

Not applicable. See the additional context section for the screenshot of the generated documentation.
Expected behavior

In the documentation section for return_value function, the "Returns:" section is displayed with the description of the return value "Returned value."
Environment information

python -m griffe_typingdoc.debug  # | xclip -selection clipboard

System: Linux-<IP_ADDRESS>-microsoft-standard-WSL2-x86_64-with-glibc2.35
Python: cpython 3.12.1
Environment variables:
Installed packages:

griffe-typingdoc v0.2.4+editable

Additional context
Screenshot of the generated documentation:

Thanks for the report, I was able to confirm. Fixing ASAP!

Fixed in v0.2.5 :slightly_smiling_face:


Updating input coord API to functions

Earth2Studio Pull Request
Description

Closes: https://github.com/NVIDIA/earth2studio/issues/77
Checklist

[ ] I am familiar with the Contributing Guidelines.
[ ] New or existing tests cover these changes.
[ ] The documentation is up to date with these changes.
[ ] The CHANGELOG.md is up to date with these changes.
[ ] An issue is linked to this pull request.

Dependencies

/blossom-ci

/blossom-ci

/blossom-ci

/blossom-ci

/blossom-ci


PLAT-86483: Fix Button color bar height

Checklist

[X] I have read and understand the contribution guide

[X] A CHANGELOG entry is included

[ ] At least one test case is included for this feature or bug fix

[X] Documentation was added or is not needed

[ ] This is an API breaking change

Issue Resolved / Feature Added
Height of the color bar should be 9px for both small and large buttons.
Resolution

Added client class to publicClassNames in order to override it in IconButton which has different requirements for the size of the color bar.
Added/updated LESS variables for the sizes

Additional Considerations
I included client in our "not for public consumption" note since we've avoided exposing it in the past. I feel like we've expanded the list enough that we're nearing the point where exposing everything might be useful since the component is reused so broadly. Alternatively, we might make an internal/Button that is more open and inline it in moonstone/Button with a more limited API.
Links
Comments

I'm curious if by opening .client if there are other awkward workarounds we've implemented in the past to get around the fact that .client wasn't available that we could now simplify with this exposure.


Docs

Added better documentation

Documentation reorganization

Hi Sasank,
Version 0.13.5 is uploaded on pypi. I propose to keep the doc on
sourceforge and on some other site as you wish. Downloads are not more than
marginal on sourceforge, but the doc web site is well visited with half
from returning visitors.
Have a good day
2016-03-21 15:42 GMT-04:00 Sasank Chilamkurthy<EMAIL_ADDRESS>
Reopened #1 https://github.com/ctherien/pysptools/pull/1.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/ctherien/pysptools/pull/1#event-597668776

May be Let's host the docs on may be pythonhosted and let's redirect  to
there from sourcefourge?
On ఆది, 27, మార్చి 2016 02:16 ctherien<EMAIL_ADDRESS>wrote:

Hi Sasank,
Version 0.13.5 is uploaded on pypi. I propose to keep the doc on
sourceforge and on some other site as you wish. Downloads are not more than
marginal on sourceforge, but the doc web site is well visited with half
from returning visitors.
Have a good day
2016-03-21 15:42 GMT-04:00 Sasank Chilamkurthy<EMAIL_ADDRESS>
Reopened #1 https://github.com/ctherien/pysptools/pull/1.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/ctherien/pysptools/pull/1#event-597668776

—
You are receiving this because you modified the open/close state.
Reply to this email directly or view it on GitHub
https://github.com/ctherien/pysptools/pull/1#issuecomment-201928323

I can add a link to pythonhosted from the sourceforge doc site somewhere at
the beginning of the index.txt file. It's important that I have an admin
access for doing quick fix or something else.  It give a good idea of what part of the software
to put the development and documentation effort.
2016-03-27 0:16 GMT-04:00 Sasank Chilamkurthy<EMAIL_ADDRESS>
May be Let's host the docs on may be pythonhosted and let's redirect to
there from sourcefourge?
On ఆది, 27, మార్చి 2016 02:16 ctherien<EMAIL_ADDRESS>wrote:

Hi Sasank,
Version 0.13.5 is uploaded on pypi. I propose to keep the doc on
sourceforge and on some other site as you wish. Downloads are not more
than
marginal on sourceforge, but the doc web site is well visited with half
from returning visitors.
Have a good day
2016-03-21 15:42 GMT-04:00 Sasank Chilamkurthy<EMAIL_ADDRESS>:

Reopened #1 https://github.com/ctherien/pysptools/pull/1.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/ctherien/pysptools/pull/1#event-597668776

—
You are receiving this because you modified the open/close state.
Reply to this email directly or view it on GitHub
https://github.com/ctherien/pysptools/pull/1#issuecomment-201928323

—
You are receiving this because you modified the open/close state.
Reply to this email directly or view it on GitHub
https://github.com/ctherien/pysptools/pull/1#issuecomment-201985693


fixes for latest rust

removes derive FromPrimitive from enums which doesn't exist anymore and a deprecated function since the deprecation mechanism cannot be used outside of the std now

Instead of just removing FromPrimitive, can https://github.com/andersk/enum_primitive-rs be used instead?

Is FromPrimitive used all that much with glfw?


Warnings in Scrapy 1.0.5

I see the following warnings:
py.warnings - WARNING - /home/tsouras/Desktop/web2py/gluon/custom_import.py:74: ScrapyDeprecationWarning: Module scrapy.log has been deprecated, Scrapy now relies on the builtin Python library for logging. Read the updated logging entry in the documentation to learn more.
return NATIVE_IMPORTER(oname, globals, locals, fromlist, level)
2016-02-27 23:20:35,840 - py.warnings - WARNING - /home/tsouras/Desktop/web2py/gluon/custom_import.py:74: ScrapyDeprecationWarning: Module scrapy.dupefilter is deprecated, use scrapy.dupefilters instead
return NATIVE_IMPORTER(oname, globals, locals, fromlist, level
2016-02-27 23:20:35,841 - py.warnings - WARNING - /home/tsouras/Desktop/web2py/gluon/custom_import.py:74: ScrapyDeprecationWarning: Module scrapy.contrib.httpcache is deprecated, use scrapy.extensions.httpcache instead
return NATIVE_IMPORTER(oname, globals, locals, fromlist, level)
2016-02-27 23:20:35 [py.warnings] WARNING: /home/tsouras/Desktop/web2py/gluon/custom_import.py:74: ScrapyDeprecationWarning: Module scrapy.contrib.httpcache is deprecated, use scrapy.extensions.httpcache instead
return NATIVE_IMPORTER(oname, globals, locals, fromlist, level)
According to http://doc.scrapy.org/en/latest/news.html
the logging and the names of some modules have been changed on Scrapy version 1.0.0
I use scrapy 1.0.5 and linux Mint

Warning is at /home/tsouras/Desktop/web2py/gluon/custom_import.py - what is it?

I run scrapy from a module of web2py framework.
I use the following code in that module:
def runScraper(spider_name):
from scrapy.crawler import Crawler, CrawlerProcess
from scrapy.settings import Settings
settings=Settings(values={'BOT_NAME':spider_name, 'LOG_LEVEL':'INFO'})

if spider_name=='LeagueScraper':
    crawler = Crawler(LeagueScraper)
elif spider_name=='MatchFinder':
    crawler = Crawler(MatchFinder)
else:
    return "%s is an unknown spider name" % spider_name
crawlerProcess = CrawlerProcess(settings=settings)
crawlerProcess.crawl(crawler)
crawlerProcess.start() # the script will block here until the crawling is finished

I'm not sure we can do anything here. web2py imports deprecated scrapy modules for whatever reason (maybe to provide module reloading?), so scrapy issues warnings. I'd say web2py shouldn't do that. Maybe there is a way in web2py to avoid this, I don't know. You can use warning filters to suppress these warnings if they are annoying. Hope this helps.
It is certainly not a problem with scrapy-splash implementation (web2py imports deprecated modules from Scrapy), so I'm closing this ticket.

I think that I found what is the problem. I installed scrapyjs from pip. The version that I have is not the latest.
For example in the version that I have, in file dupefilter.py there is the command "from scrapy.dupefilter import RFPDupeFilter". In the latest version of githb in the same file there is the command "from scrapy.dupefilters import RFPDupeFilter".
I installed scrapyjs using pip today.

@tsouras yeah, this explains it.


protoc plugin does not respect ignores

Given a proto:
version: v1
lint:
  use:
    - DEFAULT
  allow_comment_ignores: true
  ignore:
    - IMPORT_USED

And a buf.yaml
syntax = "proto3";

// buf:lint:ignore IMPORT_USED
import "unused.proto";
import "validate/validate.proto";

Running a buf_lint_test outputs:
--buf-plugin_out: file.proto:1:1:Import "unused.proto" is unused.
file.proto:1:1:Import "validate/validate.proto" is unused.
file.proto:1:1:Files must have a package defined.
unused.proto:1:1:Files must have a package defined.

It's definitely reading the buf.yaml file: use: -RPC_REQUEST_STANDARD_NAME causes all the errors to go away.
Reproducible example: https://github.com/SpencerC/rules_buf/commit/e38bd77ec5b3a8a87ebe88668e936502373c5421
Related: https://github.com/aspect-build/rules_lint/issues/222

Hey! proto_library rules don't include the source code info by default, the comment gets stripped. There are two ways to solve this:

Use ignore_only to skip a rule for specific files. More on this here.
Add the build flag --experimental_proto_descriptor_sets_include_source_info. More on this here

Thanks @srikrsna-buf. --experimental_proto_descriptor_sets_include_source_info makes allow_comment_ignores work. However, there still seems to be a problem with ignore. When adding that flag to the complete example above, the errors appear when the buf:lint:ignore comment is present, but not when it isn't.

I think I see the issue, ignore is used to ignore files. Except is used to exclude rules: https://buf.build/docs/configuration/v1/buf-yaml#except


add indonesian language

added Indonesian language

Thank you for sending this PR.
Please sign your commits.
See

https://github.com/codeigniter4/CodeIgniter4/blob/develop/contributing/pull_request.md#signing
https://github.com/codeigniter4/CodeIgniter4/blob/develop/contributing/workflow.md#gpg-signing-old-commits

I have sign in my commits. Thank you

@asnanmtakim see https://github.com/codeigniter4/shield/pull/672#issuecomment-1468722608


Update the expected removal date for several deprecated API for release v0.14

Related to discussion: https://github.com/pytorch/vision/pull/6258#discussion_r977530571

Delay the removal for transforms/_functional_video.py and transforms/_transforms_video.py since we dont have alternatives, and we remove the expected date until we have alternatives and know we can safely remove these files.
Remove the expected removal date for pretrained=True models weight API, because we need more time to plan the deprecation strategy since it is widely used on other open source library

Let me know if you have any opinion on this!

Thanks Yosua.
Following our internal discussions, the changes relating to the transforms are not controversial.
However, I have reservations about removing the expected removal date of pretrained=True, which I started formulating in the original issue https://github.com/pytorch/vision/issues/6564#issuecomment-1243896436. From my understanding there are a few different scenarios for downstream libraries using torchvision:

a) They're fine pinning to the latest version. Great, we don't need to do anyting.

b) They want to use torchvision>=0.13 eventually, but need a bit of time to migrate from pretrained=True to weights=..., and they want to do that uniformly. They (understandably) need a bit more time than the 2 version cycles we give them. To address these we can treat this as an exception, and commit to removal in 0.16 (or 0.17 or whatever) instead of the current 0.15.

c) They want to support torchvision>=SOME_OLD_VERSION where SOME_OLD_VERSION < 0.13, as e.g. required if they want to support the LTS torch core version. These ones have a problem: they can't support 0.13+ onward unless they write custom code to account for the fact that pretrained=True will be removed in 0.15.

I personally think addressing b) by upping the targetted removal to to e.g. 0.16 (or 0.17) is sensible, as long as we treat this as exceptional. But this PR tries to address c) by not committing to a removal date - this is where I'm becoming less comfortable with it.
First, a sad observation:

they can't support 0.13+ onward unless they write custom code to account for the fact that pretrained=True will be removed in 0.15.

This is what all libraries do. That's the sad reality of being a downstream libs: you have to write custom code to navigate deprecations and handle different versions of your dependencies. We have to deal with that ourselves in torchvision for our PIL dependency](https://github.com/pytorch/vision/blob/main/torchvision/transforms/_pil_constants.py)!
Next, some concerns: by not committing to a removal date, we are i) being inconsistent with our deprecation policy and the rest of our deprecated APIs, and ii) not encouraging downstream libraries to migrate: why would they migrate if they don't have to?
On top of that, not committing to a removal date essentially means that we'll only be able to remove these APIs after all downstream libs have migrated. Since we can't keep track of all of them, that essentially means, IIUC, that we can only remove these once a new LTS pops up?
Perhaps I'm missing or misunderstanding some things, but this change seems to open the door to various unexpected and undesirable situations (which go beyond torchvision BTW, since our deprecation policy comes straight from that of core). If possible, I'd like to discuss this more with the team in details and align on a path forward, where everyone is on the same page regarding the pros and cons of each alternatives.

@NicolasHug thanks for writing up your opinion, and I think it make sense and I agree that having "when" we will remove it can give urgency to downstream users (otherwise they will prefer not to change) and if we should have it if we really want the user to migrate to the new API.
That being said, I think for pretrained=True it is widely used and I think it need more than a warning on the code if we want to remove it. We should have a bigger announcement (article or blog) which tell people we will remove pretrained=True from torchvision in version x.x.x. (In general, I think deprecation and removal for a widely used API should have a bigger announcement)
And for us to decide when is the good version to remove, it also need effort to estimate and commitment to follow up after that (to give support to the internal users and oss to make sure we dont break too much things). And I think until release v0.14 we dont have enough time to decide when is the good version to remove.
In my opinion the option that we can do:

Don't change the removal version (still v0.15) but we may change them later when we release v0.15 if we need more time
We change the wording to may and we may change it later on v0.15 release:

"The 'torchvision.transforms._functional_video' module is deprecated since 0.12 and may be removed in v0.15 "

That being said, I think for pretrained=True it is widely used and I think it need more than a warning on the code if we want to remove it. We should have a bigger announcement (article or blog)

You're right for big changes or major features, it's worth raising awareness outside of the simple deprecation warnings. Vasilis has done a great job at that already, and the deprecation was announced in the following blog post: https://pytorch.org/blog/introducing-torchvision-new-multi-weight-support-api/#deprecations. The new API itself was announced in other posts / tweets / RFCs / release highlights so there's quite a bit of documentation about it already (and the fact that it replaces the old one)


Migration to JCenter

I'm trying to remove JCenter, given it's now at end of life. Is there a plan to migrate away from it?

Please switch to v2 (with different artifact id and namespace, sorry about that, I had some trouble with the original namespace).
Basically, all the public APIs are the same, without the deprecated one. You can just change the dependencies in your build script and fix all the imports related to the lib's classes, and you are good to go.


Translate placeholder "search"

Hello everyone!
I'm going to ask how I can translate the "Search" placeholder, because my UI is in Spanish.
Thanks in advance for the guidance.

Hello 👋 @julortiz
Thanks for the feedback.
With the searchInputPlaceholder props you should be able to modify it.


Desktop package and test app

The desktop-viewer-test app will be re-purposed as the new CRA template for desktop (v1) once this is approved/merged. The next iteration will add true offline briefcase support with download/sync.
Will be adding unit tests for the package as this is being reviewed but wanted to get eyes on this ASAP in hopes of getting the CRA template out in Q2

 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.


收到，哈哈哈，我邮件作者要代码了，还没要到。然后我重新开了一个问题问一下作者。最后对你说一下抱歉，打扰了，我只是看到你以前问了这个问题，以为你也许复现过这篇论文，所以问一下你。

Hi Everyone,
We are working on a big project called Graph4NLP, which we intend to
release at the end of this summer. You will find many many components such
as automatic graph construction that may be useful for your NLP projects.
Please be patient with us and we will give you a big bonus.
Yours sincerely,
Lingfei (Teddy) Wu
Research Staff Member, AI Foundations Labs - Reasoning
IBM Research AI
IBM T. J. Watson Research Center, Yorktown Heights, NY 10598
Phone: +1<PHONE_NUMBER>
Email<EMAIL_ADDRESS><EMAIL_ADDRESS>On Thu, Jul 23, 2020 at 11:31 PM More1999<EMAIL_ADDRESS>wrote:

收到，哈哈哈，我邮件作者要代码了，还没要到。然后我重新开了一个问题问一下作者。最后对你说一下抱歉，打扰了，我只是看到你以前问了这个问题，以为你也许复现过这篇论文，所以问一下你。
Originally posted by @Tanjie1102 https://github.com/Tanjie1102 in #1
(comment)
https://github.com/IBM/Text-to-LogicForm/issues/1#issuecomment-546911430
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/IBM/Text-to-LogicForm/issues/5, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADCYONPBEP662D3XHV6P633R5D57JANCNFSM4PGKROYA
.


Dask cluster hangs while processing file using s3fs

So I have a function which loads nc files from S3 using s3fs and then select some specific region from files and then push back to different S3 bucket. Here's my function. I'm doing every thing in JupyterLab
def get_records(rec):

    d=[rec[-1][0:4], rec[-1][4:6], rec[-1][6:8], rec[-1][9:11], rec[-1][11:13]]

    yr=d[0]
    mo=d[1]
    da=d[2]
    hr=d[3]
    mn=d[4]

    ps = s3fs.S3FileSystem(anon=True)

    period = pd.Period(str(yr)+str('-')+str(mo)+str('-')+str(da), freq='D')
    dy=period.dayofyear
    print(dy)

    cc=[7,8,9,10,11,12,13,14,15,16]  #look at the IR channels only for now
    dy="{0:0=3d}".format(dy)

    # this loop is for 10 different channels
    for c in range(10):
        ch="{0:0=2d}".format(cc[c])

    # opening 2 different time slices of given particular record
        F1=xr.open_dataset(ps.open(ps.glob('s3://noaa-goes16/ABI-L1b-RadF/'+str(yr)+'/'+str(dy)+'/'+str("{0:0=2d}".format(hr))+'/'+'OR_ABI-L1b-RadF-M3C'+ch+'*')[-2]))[['Rad']]

        F2=xr.open_dataset(ps.open(ps.glob('s3://noaa-goes16/ABI-L1b-RadF/'+str(yr)+'/'+str(dy)+'/'+str("{0:0=2d}".format(hr))+'/'+'OR_ABI-L1b-RadF-M3C'+ch+'*')[-1]))[['Rad']]

    # Selecting data as per given record radiance
        G1 = F1.where((F1.x >= (rec[0]-0.005)) & (F1.x <= (rec[0]+0.005)) & (F1.y >= (rec[1]-0.005)) & (F1.y <= (rec[1]+0.005)), drop=True)
        G2 = F2.where((F2.x >= (rec[0]-0.005)) & (F2.x <= (rec[0]+0.005)) & (F2.y >= (rec[1]-0.005)) & (F2.y <= (rec[1]+0.005)), drop=True)

    # Concating 2 time slices togethere
        G = xr.concat([G1, G2], dim  = 'time')

    # Concatiating different channels
        if c == 0:
            T = G
        else:
            T = xr.concat([T, G], dim = 'channel')

    # Saving into nc file and storing them to S3
    path = rec[-1]+'.nc'
    T.to_netcdf(path)
    fs.put(path, bucket+path)

Now I want to use dask cluster to run this function parallelly like this this:
files = [ ]
for i in range(0, 100):
        s3_ds = dask.delayed(get_records)(records[i])
        files.append(s3_ds)

    files = dask.compute(*files)

So this thing was running perfectly fine last month but now when I try to do it again my clusters are not processing any files after a while. For example if I give 100 files to 10 cluster they won't process any files after 60-70 even though they have memory left and will just sit idle and do nothing. So next time I tried to give just 50 files, then they'll process around 30 files and then will sit idle. Even though they have memory left in them. I don't know what I'm doing wrong or is it some bug in library.  I upgraded all the library I was using, dask, s3fs and fssps. But still nothing is working.
Main thing is all this was working perfectly fine few weeks back, but now same code is not working anymore.
Environment:

Dask version: 2021.2.0
Python version: 3.8.8
S3fs version: 0.6.0
Fsspec: 0.9.0

Its some issue with fsspec==0.9.0 which was released April 5 2021.
You need to pin fsspec down to 0.8.7 and s3fs to 0.5.2.
fsspec==0.8.7 is not compatible with s3fs==0.6.0 (import error) so you'll need to pin that down to 0.5.2.
I think s3fs needs to change their requirements.txt for 0.6.x to be fsspec>=0.9.0
This slipped into our production environment recently, it was a bit of a head scratcher.
Unit tests can't catch this, we need to work on some integration testing :)

Its some issue with fsspec==0.9.0 which was released April 5 2021.
You need to pin fsspec down to 0.8.7 and s3fs to 0.5.2.
fsspec==0.8.7 is not compatible with s3fs==0.6.0 (import error) so you'll need to pin that down to 0.5.2.
I think s3fs needs to change their requirements.txt for 0.6.x to be fsspec>=0.9.0
This slipped into our production environment recently, it was a bit of a head scratcher.
Unit tests can't catch this, we need to work on some integration testing :)

Hello,
I also tried doing so earlier but still it didn't work me? :(
Did that solve your problem?

Yes, this is what we've been running for a long while.
We pushed some updates recently and upgraded s3fs to 0.6.0 and this bug popped into production.
Pinning it back down as described resolved everything.
The behavior we saw is that basically any call to S3FileSystem just hung forever.

Yes, that (s3fs==0.5.2 and fsspec==0.8.x) is what we've been running for a long while.
We pushed some updates recently and upgraded s3fs to 0.6.0 and this bug popped into production.
Pinning it back down as described resolved everything.
The behavior we saw is that basically any call to S3FileSystem just hung forever.

It doesn't seem to be working for me! :( what's the dask version you're using sir?

Oh sorry, this is outside of Dask.
We are using s3fs in a stand-alone Python application.

@jkornblum , if you are seeing a hang outside of dask, that might be easier to debug. Please post your code, and turn on s3fs logging to see what it it doing at the time of hang. Can you interrupt the code and run a debugger?

I encountered the same problem, but I had s3fs=2021.4.0 and fsspec=2021.4.0. Not using dask or anything, just simply using s3fs to access files. My other packages could be playing into this relationship, but it is still pretty strange.
Some combinations I tried
s3fs=2021.4.0, fsspec=2021.4.0 -- NO, hangs
s3fs=0.6.0, fsspec=2021.4.0 -- NO, hangs
s3fs=0.5.2, fsspec=2021.4.0 -- NO, import error
s3fs=0.4.0, fsspec=2021.4.0 -- YES
s3fs=0.5.2, fsspec=0.8.7 -- YES
s3fs=0.6.0, fsspec=0.8.7 -- conda install incredibly unhappy (read: slow and found conflicts)
s3fs=0.6.0, fsspec=0.9.0 -- NO, hangs

@swheaton , can you please give an idea of the operations you are running? This might just be the thing we can finally debug. It would be useful if you could set the environment variable S3FS_LOGGING_LEVEL=DEBUG too, so we can see what call(s) is being made.
Also it may be worth trying with the current latest main version of s3fs, and/or with aiobotocore alone, if you have the time.

Yes @martindurant, I was able to boil it down to the below code. It was a little more than 'simply using s3fs to access files' as I originally said, because we are using a multiprocess paradigm. I don't think it's the same issue as OP, because the code snippet does not hang using OP's python and s3fs/fsspec versions. Perhaps I should open under a new issue?
If broken, it will hang after printing 'created s3fs'. If not, it runs through and exits. In the hanging case, no debug output is given with S3FS_LOGGING_LEVEL.
from multiprocessing import Process
import s3fs
def f():
    print('start')
    my_s3fs2=s3fs.S3FileSystem()
    print('created s3fs')
    f=my_s3fs2.open('s3://blah/blah', 'rb')
    print('opened')
if __name__ == '__main__':
    my_s3fs = s3fs.S3FileSystem()
    p = Process(target=f)
    p.start()
    p.join()

I also discovered it hangs in python 3.6 and 3.7, but not in >=3.8.
Attached:

working_env.txt - conda env export, s3fs=2021.4.0, python=3.8.8
hang_me.txt - conda env export, s3fs=2021.4.0, python=3.7.10

Can you please try with multiprocessing.set_start_method('spawn') (or 'forkserver') ?

Thank you, using 'spawn' or 'forkserver' works, using 'fork' does not.
From the docs

Note that safely forking a multithreaded process is problematic.

Is s3fs creating threads by merely instantiating s3fs.S3FileSystem? Line copied again below. If I remove the S3FileSystem instantiation, the hang occurs.
if __name__ == '__main__':
    my_s3fs = s3fs.S3FileSystem()
    p = Process(target=f)

This would also explain why python 3.8 was working for me, as I was indeed running on Mac OS

Changed in version 3.8: On macOS, the spawn start method is now the default. The fork start method should be considered unsafe as it can lead to crashes of the subprocess. See bpo-33725.

Yes, creating an instance creates an event loop in a separate thread - both of which are likely to crash after fork.  The line here appears not to to catch the situation.

That line would only fire if it were using the same s3fs instance inside the child process, but the child creates its own to use, so naturally the pids are equal. It could store to a class variable instead of / in addition to an instance variable?
So to be clear, are you saying that the code snippet above worked in earlier s3fs versions by "accident", and that it is the intention for this library to now explicitly disallow this by raising an exception?

That line would only fire if it were using the same s3fs instance inside the child process

Actually, instances are cached, so that if you use the same init kwargs, you get the same instance. In any case, the loop and thread are global and used by all instances unless you specify otherwise. Storing the PID elsewhere might not be a bad idea, though.

the code snippet above worked in earlier s3fs versions by "accident"

Previously, s3fs wasn't async, and didn't need to worry about loops and threads; and in the mean time, the default start-method changed.

it is the intention for this library to now explicitly disallow this

There is probably no (easy) way to code around it, so raising seemed appropriate and was the intended behaviour.

Actually, instances are cached, so that if you use the same init kwargs, you get the same instance.

I see that to be true in single process code, however the cache is cleared on this line when it determines it's inside a new process. My testing confirmed the two instances are unique by printing id(my_s3fs) and id(my_s3fs2), as well as seeing __init__ being reached.

Previously, s3fs wasn't async, and didn't need to worry about loops and threads

So even if asynchronous=False for all created instances, it's still going to set up threads and event loops and such at a global level? Any way to avoid overcomplicating things in the straightforward case (as in pre-async versions of s3fs)?

however the cache is cleared on this line when it determines it's inside a new process

That's good! At least some fork protection is working. So we also need to clear the global event loop and thread in this case - but only once for all classes (so perhaps the parent AsyncFileSystem class does this).

if asynchronous=False for all created instances, it's still going to set up threads and event loops and such at a global level

Yes

if asynchronous=False for all created instances, it's still going to set up threads and event loops and such at a global level

I'm afraid not - the internal calls are all async. It would amount to writing two complete implementations, and loosing the async benefits of bulk operations.

But really the short story is: don't use fork!

But really the short story is: don't use fork!

I think this would be a very important insight to be put in the documentation.


Production release

I want to fix a couple more things but I'm afk so please don't merge yet.
I'll fix it when I'm back in a couple of hours and push it in my other PR.
On Dec 5, 2017 22:11, "Joshua Mervine"<EMAIL_ADDRESS>wrote:

@jmervine approved this pull request.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/MaxCDN/bootstrap-cdn/pull/897#pullrequestreview-81320072,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAVVtSjJljws7TLC33JjZnqnlOQXc7rfks5s9aNfgaJpZM4Q2ydb
.

I'm jumping on a plane here shortly, so I'm not merging anything. ;)

@XhmikosR after merging the logo in the top left corner broke.

True. Doesn't happen in Firefox which I use. Please revert the logo
optimization commit and redeploy.
On Dec 6, 2017 03:30, "Justin Dorfman"<EMAIL_ADDRESS>wrote:

@XhmikosR https://github.com/xhmikosr after merging the logo in the top
left corner broke.
[image: image]
https://user-images.githubusercontent.com/398230/33639808-fa03060c-d9e1-11e7-93f5-9978d28a7f03.png
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MaxCDN/bootstrap-cdn/pull/897#issuecomment-349499829,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAVVtcJpe_JfhiRMjsMW4EzaTY1Ivbblks5s9e43gaJpZM4Q2ydb
.


[FEA] support of prefiltered brute force

The PR is one part of prefiltered brute force and should work with the PR of raft: https://github.com/rapidsai/raft/pull/2294

@rhdong this also needs to be exposed through the Python API.

/merge


Comment does not fold with function body if at end of function

Behaviour
Expected vs. Actual
Comment does not fold with function body, if at end of function.
Steps to reproduce:

Type this in a python file

def f(x):
    pass
    # this does not fold with function, even though it has the correct indentation

Diagnostic data

Python version (& distribution if applicable, e.g. Anaconda): 3.9.13
Type of virtual environment used (e.g. conda, venv, virtualenv, etc.): Conda
Value of the python.languageServer setting: Pylance

Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)

XXX

User Settings

Multiroot scenario, following user settings may not apply:

languageServer: "Pylance"

linting
• enabled: false
• mypyEnabled: true

formatting
• provider: "black"

Dupe of #2321


Not work Linux

checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for a sed that does not truncate output... /bin/sed
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking target system type... x86_64-unknown-linux-gnu
checking for cc... no
checking for gcc... no
configure: error: in /root/php-build-scripts-master/work': configure: error: no acceptable C compiler found in $PATH See config.log' for more details

Yes, it won't work for idiots.

You need basic compiler package group, build dependencies and ...


chore: reinstate migration

to fix: https://github.com/threefoldtech/tfchain/issues/480

Looks good. Any idea why the storage NodesByFarmID was not properly synced?

No idea, the linked issue seems to be an isolated case.


roll to 106842989b3b4b7c940152139b2949120f868dfd

Description
2020-10-12<EMAIL_ADDRESS>Roll Dart SDK from 06536d68ca0f to e256855d07ba (6 revisions) (flutter/engine#21775)
2020-10-12<EMAIL_ADDRESS>Roll Skia from ceb6214a556a to 9213e610ed92 (8 revisions) (flutter/engine#21774)
2020-10-12<EMAIL_ADDRESS>Ignore analysis warning for doc comment (flutter/engine#21773)
2020-10-12<EMAIL_ADDRESS>Roll Skia from d71dc2d25b8b to ceb6214a556a (5 revisions) (flutter/engine#21772)
2020-10-12<EMAIL_ADDRESS>Roll Fuchsia Linux SDK from Nw5-0_sVF... to h-DeV4tgE... (flutter/engine#21771)
2020-10-12<EMAIL_ADDRESS>Use buildroot clang for scenario app (flutter/engine#21690)
2020-10-12<EMAIL_ADDRESS>Roll Fuchsia Mac SDK from 82ankF-Ht... to FFpTJfmj1... (flutter/engine#21768)
2020-10-11<EMAIL_ADDRESS>Roll Fuchsia Mac SDK from _0R2HD4c8... to 82ankF-Ht... (flutter/engine#21762)
2020-10-11<EMAIL_ADDRESS>Roll Fuchsia Linux SDK from YRTc9YoiB... to Nw5-0_sVF... (flutter/engine#21760)
2020-10-11<EMAIL_ADDRESS>Roll Fuchsia Mac SDK from gzhbqRUap... to _0R2HD4c8... (flutter/engine#21759)
2020-10-11<EMAIL_ADDRESS>Roll Skia from aa64c352b349 to d71dc2d25b8b (1 revision) (flutter/engine#21758)
2020-10-11<EMAIL_ADDRESS>Roll Fuchsia Linux SDK from EBX49sN_X... to YRTc9YoiB... (flutter/engine#21753)
2020-10-11<EMAIL_ADDRESS>Roll Skia from 13fc260c7080 to aa64c352b349 (1 revision) (flutter/engine#21752)
2020-10-10<EMAIL_ADDRESS>Roll Fuchsia Mac SDK from lqn8xmlDn... to gzhbqRUap... (flutter/engine#21749)
2020-10-10<EMAIL_ADDRESS>Roll Skia from 61003cde7688 to 13fc260c7080 (1 revision) (flutter/engine#21746)
2020-10-10<EMAIL_ADDRESS>Revert "fix On iOS, dialog titles are announced twice (#19826)" (flutter/engine#21714)
2020-10-10<EMAIL_ADDRESS>Roll Skia from 88cda17bbeb8 to 61003cde7688 (4 revisions) (flutter/engine#21744)
2020-10-09<EMAIL_ADDRESS>Remove uses of Dart VM bytecode mode from Flutter engine (flutter/engine#21741)
2020-10-09<EMAIL_ADDRESS>Migration to PlatformDispatcher and multi-window (flutter/engine#20496)
Also rolling transitive DEPS:
fuchsia/sdk/core/linux-amd64 from EBX49sN_XBGH to h-DeV4tgEk6j
fuchsia/sdk/core/mac-amd64 from lqn8xmlDnsqD to FFpTJfmj1EGx
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md

Do not land until we've confirmed the rollback was successful at resolving the flakes

Unfortunately we cannot do a partial rollback as web was broken during this period of time


Any related paper ?

Wiki page created with citations:
https://github.com/yangjames/Calico/wiki/References


scapegoatMaxErrors not working

I set the scapegoatMaxErrors value to 1 in my build.sbt to fail the build if there are any errors. I have 5 errors but still the build succeeds.
ThisBuild / scapegoatMaxErrors := 1
addSbtPlugin("com.sksamuel.scapegoat" %% "sbt-scapegoat" % "1.1.0")
scalaVersion := "2.11.8"

@mwz You are right I looked at the usage of scapegoatMaxErrors setting in the code. It is not referred anywhere apart from plugin definition


Timestamp field of MongoDB

Timestamp field added to fields and we can save timestamp in db with timestamp type.

Hi! Thank you for the PR. Could you pls provide some tests for this improvement?


SPRT-99 (Validation form and recaptcha)

I have applied the front-end validations in pukara.es, I have also applied a recaptcha and deleted the extra lines that are not used.

@GonzaEnrique27 resolve the merge conflict of the tailwind file, see if the deleted property is used.


Custom Request Matchers bug??

i rewrite match method in my matchers whitch extends RequestMatcherExtension,the code is no error,
and i config the mapping such as :
{
"request" : {
"customMatcher" : {
"name" : "extension-matcher",
"parameters" : {
"maxLength" : 2048
}
}
},
"response" : {
"status" : 422
}
}
，
At the beginning ， Custom Request Matchers can esponse the right matched,
but ,nothing is change , just after an exception，the same request can't matched!!

if restart the wiremock , the request Can match again


Different hideAfter value (or behaviour) depending on the Type

Hello,
Is it possible to parameter Messenger in such a way that:

Messages of Type "success" hides after e.g. 10 seconds (you just want to indicate that everything is ok);
Messages of Type "error" can only be hidden by clicking on the close button (or other possibility, it hides after e.g. 3 minutes). -> There is an error, you want it to be visible for a longer time and that the user performs an action in order to hide it.

thx

FYI, I've just solved this requirement by overriding the default  hideAfter value in case it is an error:
function showMessengerMsg(message, type) {
    var msgObj = {
        message: message,
        type: type,
        showCloseButton: true,
        id: "myMessengerAlert"
    };
    if (type == "error") {
        msgObj.hideAfter = 180;
    }
    Messenger().post(msgObj);
}


Global Token Expiration Time Update Issue in Single Page (SP) and Traditional Web Applications

Describe the issue:
When attempting to change the default token expiration time globally, two distinct issues have been identified:
Single Page (SP) Application Issue:
The global changes to the expiration time are not reflecting in Single Page (SP) applications. Despite updating the values via the global configuration, SP applications still operate with the previous expiration times.
After Changes

Traditional Web Application Issue:
In Traditional Web Applications, specifically in the "Access token expiry time" input field, is missing after updating the global configuration.
Before Changes

After Changes

How to reproduce:
Open the global configuration file (e.g., deployment.toml).
Change the default expiration times globally under [oauth.token_validation].
eg.
[oauth.token_validation]
app_access_token_validity=1800
user_access_token_validity=1800
refresh_token_validity = 96400

Save the changes and restart the application.
Observe the behavior in both Single Page (SP) and Traditional Web Applications.
Note : Changes are applied as expected with "standards based application" and Management console

Environment information (Please complete the following information; remove  any unnecessary fields) :

Product Version: wso2is-7.0.0-beta5-SNAPSHOT
OS: Mac
Database: H2
Userstore:JDBC

Some default values have been set from the FE.

The values for "userAccessTokenExpiryInSeconds" and "applicationAccessTokenExpiryInSeconds" should not have any default values or be 0. Please check all the expiry times and remove the defaults from the FE side.  Additionally we need to check the reason for not displaying the  "Access token expiry time" in the Traditional Web Applications.

This issue is there in 6.1 pack as well. Adding a fix by taking the values from the oidc meta endpoint.

Regarding the traditional web application issue mentioned in the description,
the Application access token expiry time field is hidden when client credentials grant type is not chosen.. this is expected. Shall we check again if you are getting this behaviour on enabling/disabling the grant type? @NilukaSripalim

Yes, it is updated after enabling client credential grant type in traditional web application, expected app access token expiration is updated when token time is updated globally.


[Workflow] Add module:authz label for changes in Authz module in labeler workflow

Why are the changes needed?

label changes in Authz plugin with module:authz label in Github labeler workflow

How was this patch tested?

[ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible

[ ] Add screenshots for manual tests if appropriate

[ ] Run test locally before make a pull request

Thanks, merged to master


[DO NOT MERGE YET] Adopt lexicalContext from swift-syntax-6.0.0.

This PR conditionally adopts the new lexicalContext member of MacroExpansionContext added in https://github.com/apple/swift-syntax/pull/1554. If the SwiftSyntax600 pseudo-module is available, then this member should be available for use and can be used to perform additional diagnostics for tests and to get the names of their containing types.
With this PR, if built against an older toolchain (5.11 or earlier), the old hacky "is there leading whitespace?" mechanism is still used.
A future PR will recursively perform suite-level diagnostics on the lexical contexts containing tests and suites, so that a test cannot be (easily) inserted into a type that cannot be used as a suite.
Resolves rdar://109439578.
Checklist:

[x] Code and documentation should follow the style of the Style Guide.
[x] If public symbols are renamed or modified, DocC references should be updated.

@swift-ci please test

@swift-ci please test

@swift-ci please test

@swift-ci please test

@swift-ci please test

@swift-ci please test Linux

Holding on to this PR for the moment as I'd like @DougGregor's review as well.

@swift-ci please test


Deterministic function support

In Python 3.8, sqlite3 added support for creating deterministic SQL functions via Connection.create_function. Adding this to aiosqlite can be achieved with a simple patch to pass through the deterministic kwarg:
diff --git a/aiosqlite/core.py b/aiosqlite/core.py
index 0135654..4992d79 100644
--- a/aiosqlite/core.py
+++ b/aiosqlite/core.py
@@ -196,12 +196,20 @@ class Connection(Thread):
         """Interrupt pending queries."""
         return self._conn.interrupt()

-    async def create_function(self, name: str, num_params: int, func: Callable) -> None:
+    async def create_function(
+        self, name: str, num_params: int, func: Callable, deterministic: bool = False,
+    ) -> None:
         """Create user-defined function that can be later used
         within SQL statements. Must be run within the same thread
         that query executions take place so instead of executing directly
         against the connection, we defer this to `run` function."""
-        await self._execute(self._conn.create_function, name, num_params, func)
+        await self._execute(
+            self._conn.create_function,
+            name,
+            num_params,
+            func,
+            deterministic=deterministic,
+        )

     @property
     def in_transaction(self) -> bool:
diff --git a/aiosqlite/tests/smoke.py b/aiosqlite/tests/smoke.py
index af6c239..243cff2 100644
--- a/aiosqlite/tests/smoke.py
+++ b/aiosqlite/tests/smoke.py
@@ -313,6 +313,21 @@ class SmokeTest(aiounittest.AsyncTestCase):
                 row = await res.fetchone()
                 self.assertEqual(row[0], 20)

+    async def test_create_function_deterministic(self):
+        """Assert that after creating a deterministic custom function, it can be used.
+
+        https://sqlite.org/deterministic.html
+        """
+
+        def one_arg(num):
+            return num * 2
+
+        async with aiosqlite.connect(TEST_DB) as db:
+            await db.create_function("one_arg", 1, one_arg, deterministic=True)
+            await db.execute("create table foo (id int, bar int)")
+            # Non-deterministic functions cannot be used in indexes
+            await db.execute("create index t on foo(one_arg(bar))")
+
     async def test_set_trace_callback(self):
         statements = []

The above patch passes the test suite on Python 3.8.
However, the deterministic kwarg is only available on Python >= 3.8 and aiosqlite supports >= 3.6. Is it possible to include support for this on only Python 3.8 installs? Perhaps conditionally defining aiosqlite.Connection.create_function with a different signature based on sys.version_info?

Should be enough to document "the deterministic parameter is ignored on versions below Python 3.8", and conditionally check whether to use it or not at runtime:
import sys

kwargs = {}
if sys.version_info >= (3, 8):
    kwargs["deterministic"] = deterministic

await self._execute(self._conn.create_function, name, num_params, func, **kwargs)

I don't like using kwargs, since that's more difficult to deal with type checking, but I think something like this (plus appropriate documentation) would be sufficient:
if sys.version_info < (3,8):
    await self._execute(..., func)
else:
    await self._execute(..., func, deterministic=deterministic)

PR welcome.

The kwargs would only be used internally inside the function, not be exposed to the user. It shouldn't affect user's type checking. The kwargs approach is slightly more compact but more importantly avoids duplicated code of a call (which makes it impossible to forget the call's arguments).

The kwargs would only be used internally inside the function, not be exposed to the user. It shouldn't affect user's type checking

I'm more concerned with type checking the library. In this case, by using kwargs, I believe mypy isn't able to statically analyze kwargs to know if valid arguments are being passed or not. By having separate calls (and by running mypy from CI on all supported versions of Python), mypy can verify that all keyword arguments are supported on the correct versions of Python standard library.
All that said, I'd rather see a PR passing CI that I can merge, regardless of implementation choice. 😅


Update member activity dropdown

closes TryGhost/Team#2250

Looking really solid, @lenabaidakova! I just noticed that in dark mode the borders were looking pretty bright. Look at the History one for inspiration 👌 Aside from that, all gravy!

Oh, also, this one isn't on you. But I noticed in dark mode that icon loses it's dot from the !. Any ideas how I can fix that in the SVG?


Newer vscode versions for ubuntu cause the navigation bar to turn white

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

VS Code Version:  1.84.1
OS Version: Linux version 5.4.0-150-generic (buildd@bos03-amd64-012) (gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04)) #167~18.04.1-Ubuntu SMP Wed May 24 00:51:42 UTC 2023

Steps to Reproduce:
You can see it as soon as you open vscode on Ubuntu, and no matter what theme you switch to, three-way or official, the top navigation bar is always white, even with a black theme. As a side note, this bug has been around for the last two to three versions.
here is screenshot

Hey Deepak, not sure who to assign, I thouhgt it's maybe related to electron? Feel free to reassign.

Are you using the native titlebar "window.titleBarStyle": "native" ?

Are you using the native titlebar "window.titleBarStyle": "native" ?

The user json file didn't have this setting, but when I changed it to custom, this problem was solved, thanks!


Feature request: fine progress

Currently, amplitude-song-slider's value is set by 1 percent. This looks very bad when the bar is large, since it sudenly updates once per 3 or even more seconds.
It is possible to set the range to finer values, such as 0 to nuber in seconds in the audio. That would make the progress bar look much better.

I agree with this. It feels very unnatural by default. We will review this and get this addressed in a release soon.

This seems to be fixed??

@carlsmith is right, this is fixed. We just need to make sure the headers are correct when scrubbing the song. To adjust on a finer value, we just need to set the step attribute of the input to be smaller for larger screens.


fix: theme fixes

Default theme Dark mode is now darker
Before:

After:

Alternate theme is now gray scaled

Visual flares are all simplified now to deal with older browsers lagging on scroll
Saturn Updates:

Mars:

Blue Planet:

Fixed unused variables and fixed one variable name throughout themes


How to modify the extension ae_loss code to fit Pytorch 1.0?

@DouYishun  I also encountered the same problem...
Do you solve it?

@teamo429 https://github.com/DouYishun/loss_collection/blob/master/AEloss/AE_loss.py

@DouYishun Thank you for providing a python AELOSS. Have you tested it? What's the effect? Looking forward to your reply！


fix mutate with replace klass

When registering mutation check for Node that replaced original one.
mutation are a map so only one entry.
Should fix  #4498

This looks like it solves the same problem as #6076 so it should close that as well if this PR is chosen. My review comments would be basically the same: https://github.com/facebook/lexical/pull/6076#pullrequestreview-2051214716

I think this approach is probably better, but without really any docs or test coverage it's hard to say if there are any additional caveats to this simpler solution

In that other PR you have a good point about chain of node replacements.
Currently this code doesn't support it, I will fix it when I have a second.

So I have added loop to support multilevel replacement.
But I have problem testing it, it seems like right now it isn't supported really well.
I think we should also loop over replace in $applyNodeReplacement()
But that's for different change.

Good idea, it seems that there is a lack of test coverage all around for this corner of the API!

If no-one picks this up - I'll look at it later to add some tests. I touched klasses already in the devtools

If no-one picks this up - I'll look at it later to add some tests. I touched klasses already in the devtools

That would be very welcome! I'll close https://github.com/facebook/lexical/pull/6076 since this one seems more in line with expectations.

Closed in favor of https://github.com/facebook/lexical/pull/6189 (tests added)


Postgresql search proposals

Hello
DBeaver 3.7.4 x86
Java build 1.8.0_101-b13 (x86)
Postgresql 9.5
When i type "from some_table" and press ctrl + space - DBeaver returns no results
When i type "from public.some_table" and press ctrl + space - DBeaver returns tables match
Is there some kind of setting " default schema " or is it a bug ?

DBeaver uses PG search path for completion proposals.
Sure, you can change default (active) schema. Just right click on schema name in navigator ans choose "Set Active".

public selected by default scheme , but the problem remains

It is a bug in PostgreSQL completion processor.

in DBeaver 3.7.5 x86 problem completely opposite
When i type "from some_table" and press ctrl + space - DBeaver returns tables match from active schema
When i type "from public.some_table" and press ctrl + space ("public" scheme is active)- DBeaver returns no results
there are still problems in PostgreSQL completion processor ?

Yep. That fix broke completion in another place.
This issue was already fixed in #763, wait for 3.7.6.


Migrate ListView to FlatList

Replace ListView from FlatList as it has been deprecated.
Change _dataSource and _renderRow methods to make them work with FlatList:

_dataSource: make it to immediately return options passed from props
_renderRow: change the parameter to rowParameter which consist of item object of FlatList.
: remove unrelated variable associated with Listview.
: amend several variable to make them work with rowParameter.
Modify _onRowPress
replace rowId with rowparameter.index
remove higlightrow as it undefined for FlatList

ListView is not removed in this commit, therefore error
ExceptionsManager.js:94 Unhandled JS Exception: Invariant Violation: Invariant Violation: Invariant Violation: ListView has been removed from React Native. See https://fb.me/nolistview for more information or use `deprecated-react-native-listview`.

This error is located at:
    in ModalDropdown (at loginForm.js:47)


Add cell dissociation and related terms.

Add new biosample method terms to represent samples obtained by various means of cell dissociation.
close #155

By 'cell suspension' do you mean 'suspension culture' (FBcv:0003161)? If so, it would be good to use the same terminology here, if not, it would be good to define what you mean by 'cell suspension'.

Also questioning whether chemical and mechanical subclasses should fall under 'chemical treatment' and 'physical treatment', respectively. They probably should given the current definitions, but I'm not sure if the 'treatment' terms are intended/used for experimental conditions rather than sample preparation methods.

Regarding “cell suspension”: No, “suspension culture” would apply to a sample made of non-adherent cultured cells (as opposed to a sample made of adherent cells, for which the term would be adherent culture).
Here, the new term is intended for cells that are not grown in culture (so any term under cell culture property, such as cell suspension, is not applicable), but are instead obtained from the dissociation of a dissected tissue or organ (or possibly an entire organism, especially for embryos).
I took the “separated into individual cells or a cell suspension” straight from the EFO term, but I agree this “cell suspension” bit is confusing and can be removed.

If you are using EFO as a source, you really should add the EFO term ID as a reference.
If you are sure that the 'treatment' terms are not supposed to apply to sample collection (and haven't been used this way in curation), then I am happy for you to disambiguate and reorganise these.


Establish RoadManager controls and updates

Purpose of this PR is to establish the hierarchy and controls of the RoadManager node, intended to be the parent of all Road* nodes, along with some appropriate triggers and settings.
This PR also covers a number of QoL improvements including in-editor warnings and instructions, and native ability to add road nodes from the create menu.

Here's what the updated icons look like now. Curious if you have any feedback before I merge these icons @bdog2112. Not looking for as much of a thorough testing this time, might be better to have you do one larger round of testing as I make further progress (but I'll still be breaking into several PRs along the way).

I've also locally set up a command line test runner, which eventually we could use to automate testing via github actions (once we figure out how to cache godot binaries between runs). For now, manually copying over.
Totals
Scripts:          4
Passing tests     17
Failing tests     0
Risky tests       0
Pending:          0
Asserts:          71 of 71 passed

17 passed 0 failed.  Tests finished in 1.6s

Here's what the updated icons look like now.

I think I like your proposed icons the best. To make sure, I mocked up some RoadPoint icons with circles instead of rectangles. The main intent was to observe the association between the word "point" and the circle. But, I felt like what I saw was more akin to clown juggling balls. ;-) Hence, I recommend sticking with the rectangular RoadPoint icons.
The outline around the your RoadContainer perfectly implies that it contains RoadPoints.
The map is also a great reference for a series of RoadContainers. So, again, good choice.
Didn't you rename "LaneSegments" to "RoadLanes"? If so, then the curve icon is perfect for them! So, yeah. Stick with the icons you proposed in your post.
Example Of Juggling Balls As RoadPoints:

Did you ask me to test something? If so, please let me know. It sounded like you were planning to do testing later.

Thanks @bdog2112 and super appreciate the idea of the circle/point! I also toyed with it quite a bit and never found something that I liked. Actually might be fun, for prosperity, to show some of the other iterations below here (also noting this early feedback I got on twitter)
No need for further testing, might have you do one round of more exhaustive testing once I've got more of the intersection system in place. Carry on with your curvy roadwork in the meantime in the WheelSteal project!
https://twitter.com/WheelStealGame/status/1705997712163045809
And the other variations:

And various iterations of nodes that I quickly tried and replaced in the editor (unfortunately didn't save those screenshots, so this is straight from Affinity)

There's even a couple others here I tried but tossed out and I coudln't get files for, I experimented with having RoadPoints be the lane widget arrow with or without a point or square in the middle, never quite felt good with the pixels we had to play with.


Implement test resources property provider factory

This commit introduces a new annotation, @TestResourceProperties, which can be applied on a test in order to tell that the test needs to resolve one or more test resource properties before the application context is available.
For example, with:
@MicronautTest
@TestResourcesProperties(
    value = "redis.url"
)
class SomeTest { ... }

Then the value of the redis.url property will automatically be fetched from the test resources service and made available as if it had been done in a TestPropertyProvider. The difference is that this without this annotation, it was required to call the test resources client directly in the provider, which was error prone. In particular, the properties argument of the resolve call are not easy to figure out.
This annotation is therefore a convention to avoid having to call the client directly. However, in some cases it might be necessary to read a property in order to compute a different one which needs to be available in the test.
This can be done by adding a providers argument to the annotation:
@TestResourcesProperties(
    value = "rabbitmq.uri",
    providers = RabbitTest.RabbitMQProvider.class
)
class RabbitTest {
  // ...
      @ReflectiveAccess
      public static class RabbitMQProvider implements TestResourcesPropertyProvider {
          @Override
          public Map<String, String> provide(Map<String, Object> testProperties) {
              String uri = (String) testProperties.get("rabbitmq.uri");
              return Map.of(
                  "rabbitmq.servers.product-cluster.port", String.valueOf(URI.create(uri).getPort())
              );
          }
      }
}

The TestResourcesPropertyProvider type has access to all properties which are already resolved at the moment it is called, which includes the properties asked in @TestResourcesProperties.
This should make the implementation of https://github.com/micronaut-projects/micronaut-nats/pull/321 easier.

Some reference docs would be nice

Some reference docs would be nice

Yes, but I'd like to finish the improvements first (there should be another PR on this topic, with scope management).


refactor(checks): migrate AWS ec2 to Rego

Related PRs:

#216

The error occurred on the Trivy side. Opened a PR with a fix. https://github.com/aquasecurity/trivy/pull/7377

@simar7 Trivy now contains Go checks that are not marked as deprecated, so they are not ignored before applying all checks as a result they are duplicated. But this will be fixed if we update trivy-checks in Trivy.


Remove tekton.dev/task label from ClusterTask TaskRuns

Expected Behavior
TaskRuns started from a ClusterTask should only have the label tekton.dev/clusterTask=<task name>.
Actual Behavior
TaskRuns started from ClusterTasks currently receive both tekton.dev/clusterTask= and tekton.dev/task=.
Steps to Reproduce the Problem

Run a TaskRun referencing a Cluster Task
View its YAML or its Pod's YAML
See tekton.dev/task label

Tekton Pipeline version: 0.12.0

This was announced as deprecated in 0.12.0 so should be removable from Pipelines on/after Jan 30 2021

PR #2527 for it but needs to be merged later

/kind cleanup

Can I suggest that we close this until the deprecation window has closed?  I'd prefer not to keep this PR open for 9 months.
What do others think?  I've documented the deprecation of the annotation here: https://github.com/tektoncd/pipeline/blob/master/docs/deprecations.md

I got error: 'error: unable to recognize "tekton/tasks/source-to-image.yaml": no matches for kind "Task" in version "tekton.dev/v1beta1"' today and it worked last week.
Is this related to this depreciation?
Thank you
Lee

@lee-zhg no, this change wasn't merged yet so it's unlikely to be related.  Feel free to create a new issue if your problem persists.  Please include any more information you can - Tekton version, the Task YAML, etc.

/remove-lifecycle stale

As this is a deprecation "follow-up", let's not mark it as stale
/remove-lifecycle stale
/lifecycle frozen

As this is a deprecation "follow-up", let's not mark it as stale
/remove-lifecycle stale
/lifecycle frozen

/milestone v0.21.0


proposal: errors: unwarap joinError to avoid deeply-nested joins

Proposal Details
The current implementation of joinError appends the given errors onto an internal []error. However, it does not take into account itself, leading to unexpected internal structures. This is perhaps best illustrated by an example:
var merrA error
merrA = errors.Join(merrA, fmt.Errorf("one"))
merrA = errors.Join(merrA, fmt.Errorf("two"))
merrA = errors.Join(merrA, fmt.Errorf("three"))

var merrB error
merrB = errors.Join(merrB, fmt.Errorf("one"), fmt.Errorf("two"), fmt.Errorf("three"))

One would likely expect merrA and merrB to be structurally equal. While they "print out" the same error, their internal representation differs:
merrA = &joinError{
  errs: []error{
    fmt.Errorf("one"),
    &joinError{
      errs: []error{
        fmt.Errorf("two"),
        &joinError{
          errs: []error{
            fmt.Errorf("three"),
          },
        },
      },
    },
  },
}

merrB = &joinError{
  errs: []error{
    fmt.Errorf("one"),
    fmt.Errorf("two"),
    fmt.Errorf("three"),
  }
}

My proposal is that errors.Join special-case the internal joinError type to "unwrap" the inner errors and flatten the slice.
I believe this change is fully backwards-compatible with any documented APIs and public interfaces. There are no test cases that cover this expected nesting as shown in https://github.com/golang/go/pull/65360.
I also believe this will lead to more performant error printing, since it reduces the need to recurse multierrors, but I do not have time to gather data and benchmark my gut feeling.
I could not find any corresponding issues, but "errors" and "unwrap" are not particularly unique keywords, so apologies if I missed them.

GitHub: https://github.com/golang/go/pull/65360
Gerrit: https://go-review.googlesource.com/c/go/+/559355

It was an explicit design choice not to flatten errors https://github.com/golang/go/issues/53435#issuecomment-1191752789

One would likely expect merrA and merrB to be structurally equal.

Why?
The documentation for Join says that it "wraps the given errors". If it flattened its inputs, that statement would not be accurate, because Join(err) could return an error that does not wrap err.
I do not believe changing this would be backwards compatible.
In addition, if Join flattened errors produced by Join, but not other errors implementing Unwrap() []error, this would be a point of confusion in the API. We currently don't preference errors produced by the errors package over errors produced by other packages in any way, and I don't think we should change that. This was a significant motivation in choosing the current behavior of Join--it is by design simple and without special cases.


MicroWebSrv2 on an ESP8266 gives a Memory Error

Thank you for your two great MicroWebSrv-Libraries!
I've create a project that controls staircase LED lights that are mounted inside wall boxes. The lights are triggered, by PIR , by lux-sensor or by RTC.  The project is controlled by an arduino pro mini. The arduino is also mounted in one of the wall boxes behind one of the led lights.
The only control is the wall light switch (power on/off). For more control I always have to open the wall box containing the arduino. In order to gain easier control over the arduino I want to add wifi-access. So I came across the ESP8266-12F (and I discoverd MicroPython!!! :-) My plan is to change from arduino pro mini to ESP8266-12F.
The 8266 mcu matches my requirements for power and space. Now I'm looking for the right web server library, that allows me to use my mobile browser to read a few values from the mcu and to post/change some values. The main task of the mcu is still to keep several timers running, handle interrupts and control the pwm output for the led.
Which web server would you recommend for my project? Is MicroWebSrv2 running on ESP8266? Is MicroWebSrv still maintained?
Looking forward hearing from you.

I've tested to run MicroWebSrv2 on an ESP8266-12F ( with 4MBit,  MicroPython v1.17 on 2021-09-02; ESP module with ESP8266
) by using your main.py and got this
>>> %Run -c $EDITOR_CONTENT

       ---------------------------
       - Python pkg MicroWebSrv2 -
       -      version 2.0.6      -
       -     by JC`zic & HC2     -
       ---------------------------

Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "MicroWebSrv2/__init__.py", line 15, in <module>
MemoryError: memory a

As told before, I'm new to MicroPython and ESP8266. Could you give me any hint if there is a change to get your webserver running on my mcu or should I try the previos version or is there a lightweight alternative?

Hae you found the solution yet? I'm stuck on the same thing.

Have you found the solution yet? I'm stuck on the same thing.

No, I gave up using MicroPython on ESP8266 and went back to good old c++


Change size of points as a free parameter in plot()?

Is it possible to set the point size to show another dimension of the data in Gadfly? I envision something like the following
plot(x=1:5, y=1:5, color=["a", "b", "b", "a", "c"], size=1:5, Geom.point)

Is this possible?

There does seem to be a problem with the point size aesthetic in Gadfly (also mentioned here #766).
One work around is to use Guide.annotation [http://dcjones.github.io/Gadfly.jl/guide_annotation.html].
For example, Compose.circle can take three vectors circle(x,y,size).
A fancier way is to make your own geometry. The following is a simple example:
using Compose, DataFrames

immutable PointGeom2 <: Gadfly.GeometryElement
    tag::Symbol

   function PointGeom2(; tag::Symbol=Gadfly.Geom.empty_tag)
        new(tag)
    end
end

function Gadfly.element_aesthetics(::PointGeom2)
   [:x, :y, :size, :color, :shape]
end

function Gadfly.render(geom::PointGeom2, theme::Gadfly.Theme, aes::Gadfly.Aesthetics)

    default_aes = Gadfly.Aesthetics()
   default_aes.color = DataArrays.PooledDataArray(Colors.RGBA{Float32}[theme.default_color])
    default_aes.size = Measure[theme.default_point_size]
   aes = Gadfly.inherit(aes, default_aes)
   ctx = context()
    compose!(ctx, circle(aes.x, aes.y, size, geom.tag), fill(aes.color))
   return compose!(context(order=4), svgclass("geometry"), ctx)
end

point2 = PointGeom2

D=DataFrame(x=1:5, y=randn(5), size=(1:5)/10, col=["a","b","b","a","c"])
size = D[:size]
p = plot(D,x=:x,y=:y, color=:col, point2)

Now back to the current version of Gadfly.  I think the issue with the size aesthetic (which seems to require an array of type Measure) is not in the point geometry render function itself [https://github.com/dcjones/Gadfly.jl/blob/master/src/geom/point.jl], but occurs earlier and hence may take some time sort out.


Can i use this with my android project, please help

I am trying to use it with my android project and its not working. I added the dependencies like this:
repositories {
    // Or use mavenCentral(). I prefer new and cool shit + HTTPS, hence jcenter():
    jcenter()
}

repositories {
    maven {
        // Quandl4j has a dependency not in Maven: 'com.opengamma.external.json:json:1.0.0.v20101106'
        // Source of this URL: https://github.com/jimmoores/quandl4j/blob/master/pom.xml
        url "http://maven.opengamma.com/nexus/content/groups/public"
    }
}

dependencies {
    compile fileTree(include: ['*.jar'], dir: 'libs')
    compile project(':payUMoneysdk')
    compile 'com.android.support:appcompat-v7:23.4.0'
    compile 'com.android.support:design:23.4.0'
    compile 'com.android.support:support-v4:23.4.0'
    compile 'com.android.support:recyclerview-v7:23.4.0'
    compile 'com.squareup.retrofit2:retrofit:2.1.0'
    compile 'com.squareup.retrofit2:converter-gson:2.1.0'
    compile 'com.squareup.okhttp3:logging-interceptor:3.3.1'
    testCompile 'junit:junit:4.12'
    compile 'com.jimmoores:quandl:1.3.0'
}

It gives this error while building:
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class

You need to add the OpenGamma maven repository to your list of
repositories. It's at maven.opengamma.com.  I'm not super familiar with
Gradle, but someone else documented how to use Quandl4J with Gradle in the
tutorial.
Hope that helps.
Jim
On 13 Oct 2016 9:56 a.m., "Rakesh Yadav"<EMAIL_ADDRESS>wrote:

I am trying to use it with my android project and its not working. I added
the dependencies like this:
`repositories {
// Or use mavenCentral(). I prefer new and cool shit + HTTPS, hence
jcenter():
jcenter()
}
repositories {
maven {
// Quandl4j has a dependency not in Maven: 'com.opengamma.external.json:
json:1.0.0.v20101106'
// Source of this URL: https://github.com/jimmoores/
quandl4j/blob/master/pom.xml
url "http://maven.opengamma.com/nexus/content/groups/public"
}
}
dependencies {
compile fileTree(include: ['*.jar'], dir: 'libs')
compile project(':payUMoneysdk')
compile 'com.android.support:appcompat-v7:23.4.0'
compile 'com.android.support:design:23.4.0'
compile 'com.android.support:support-v4:23.4.0'
compile 'com.android.support:recyclerview-v7:23.4.0'
compile 'com.squareup.retrofit2:retrofit:2.1.0'
compile 'com.squareup.retrofit2:converter-gson:2.1.0'
compile 'com.squareup.okhttp3:logging-interceptor:3.3.1'
testCompile 'junit:junit:4.12'
compile 'com.jimmoores:quandl:1.3.0'
}`
It gives this error while building:
Error⚠ Ignoring InnerClasses attribute for an anonymous inner class
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/jimmoores/quandl4j/issues/21, or mute the thread
https://github.com/notifications/unsubscribe-auth/AADG-_2CY7GsF_-KZN0Y7qYeGkjJ3nyVks5qzfJHgaJpZM4KVo6_
.

yes i did that already if you see the code in my question, i added
repositories {
    maven {
        // Quandl4j has a dependency not in Maven: 'com.opengamma.external.json:json:1.0.0.v20101106'
        // Source of this URL: https://github.com/jimmoores/quandl4j/blob/master/pom.xml
        url "http://maven.opengamma.com/nexus/content/groups/public"
    }
}

But the problem is i can't use your java library in my android studio. There is no tutorial on how to do that. I tried to import it as a module, but the there are so many errors i face after it.
First error is:
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Second is in file QuandlSession.java at this line:
result.append(JSON_COLUMN_NAMES_FIELD, DATE_COLUMN);
error cannot find symbol method append(string,string)
There are many errors i face after adding your library in android studio as a module, maybe its not compatible with android studio or i am doing something terribly wrong. Please help me with android integration if you can.

I'm not familiar with android studio at all. I'm happy to try and help but
I'm not able to try until tomorrow at the earliest. Are you using ProGuard?
Have you tried this:
http://stackoverflow.com/questions/35796144/progaurd-issue-warningignoring-innerclasses-attribute-for-an-anonymous-inner-c
Jim
On 13 Oct 2016 2:07 p.m., "Rakesh Yadav"<EMAIL_ADDRESS>wrote:

yes i did that already if you see the code in my question, i added
repositories {
maven {
// Quandl4j has a dependency not in Maven: 'com.opengamma.external.json:json:1.0.0.v20101106'
// Source of this URL: https://github.com/jimmoores/quandl4j/blob/master/pom.xml
url "http://maven.opengamma.com/nexus/content/groups/public"
}
}
But the problem is i can't use your java library in my android studio.
There is no tutorial on how to do that. I tried to import it as a module,
but the there are so many errors i face after it.
First error is:
Error⚠ Ignoring InnerClasses attribute for an anonymous inner class
Second is in file QuandlSession.java at this line:
result.append(JSON_COLUMN_NAMES_FIELD, DATE_COLUMN);
error cannot find symbol method append(string,string)
There are many errors i face after adding your library in android studio
as a module, maybe its not compatible with android studio or i am doing
something terribly wrong. Please help me with android integration if you
can.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/jimmoores/quandl4j/issues/21#issuecomment-253507468,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AADG-3-s2Iubs8uuvveq-rPmAk39fOh6ks5qziz3gaJpZM4KVo6_
.

Is this issue still open?

Yes i never found any solution so i made it using API endpoints directly, with out the library. Also the stackoverflow link, i followed those instructions but no luck. You can close it if you want, thanks for the help

Thanks for replying.


Add rule ECS0007

Related: https://github.com/BillWagner/EffectiveCSharpAnalyzers/issues/7
Closes #32
The problem addressed by this rule is the use of methods that should involve callback mechanisms without employing delegates for this purpose. Specifically, methods are being invoked directly without the use of delegate types such as Predicate<T>, Action<T>, or Func<T>, which are designed to handle callbacks in a type-safe and consistent manner.

 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.


next: Dialog.Content body scroll lock doesn't clean itself up properly

Describe the bug
styles added to body to prevent scroll when opening drawer (https://github.com/huntabyte/vaul-svelte/issues/96) never get removed after closing it.
https://github.com/huntabyte/bits-ui/blob/next/packages/bits-ui/src/lib/bits/utilities/scroll-lock/scroll-lock.svelte
https://github.com/huntabyte/bits-ui/blob/next/packages/bits-ui/src/lib/internal/use-body-scroll-lock.svelte.ts
https://github.com/huntabyte/bits-ui/blob/next/packages/bits-ui/src/lib/bits/dialog/components/dialog-content.svelte#L71
https://github.com/user-attachments/assets/c4d48e0c-d594-42b8-9538-af0788ca3f4f
this breaks vaul and possibly other components using body scroll lock
https://github.com/huntabyte/vaul-svelte/issues/96
all styles should be cleared not just overflow imo similar to how original vaul does this:

Reproduction
Update all packages to latest with pnpm update --latest and pnpm dev
https://github.com/huntabyte/vaul-svelte/
Logs
No response
System Info
Happens on every system

System:
    OS: Windows 11 10.0.22631
    CPU: (32) x64 AMD Ryzen 9 7950X3D 16-Core Processor
    Memory: 18.45 GB / 63.09 GB
  Binaries:
    Node: 20.11.1 - C:\Program Files\nodejs\node.EXE
    npm: 10.4.0 - C:\Program Files\nodejs\npm.CMD
    pnpm: 8.15.4 - ~\AppData\Local\pnpm\pnpm.EXE
    bun: 1.1.31 - ~\.bun\bin\bun.EXE
  Browsers:
    Edge: Chromium (127.0.2651.74)
    Internet Explorer: 11.0.22621.3527
  npmPackages:
    @sveltejs/kit: ^2.7.2 => 2.7.2
    bits-ui: ^1.0.0-next.22 => 1.0.0-next.22
    svelte: ^5.0.5 => 5.0.5
    typescript: ^5.6.3 => 5.6.3
    vaul-svelte: ^1.0.0-next.0 => 1.0.0-next.0

Severity
blocking an upgrade

Imo handling it with some attribute like data-scroll-locked will be much better than trying to figure out what was set before. Like if there were never any body styles applied before that I'd expect it to be that way when I close the dialog.

tried to play around with it but can't get pnpm link to work with bits-ui... I did pnpm link --global from local bits-ui repo and then I did pnpm link --global bits-ui from local vaul-svelte repo and it didnt work 😞