Disable item sorting when dropping new file

Hi there,
I'm using Filepond for a project and it works pretty great so far, thanks. One feature i could really use right now is disabling the sorting of items when dropping files. Our backend doesn't support adding additional metadata at the moment so i can not persist the sort order.
Simply dropping a new file on top of the list without additional sorting enabled would be perfect, is that something which could be done perhaps?

Do you mean not allowing the user to drop it in the list at a specific location?

Hi Rik,
Thanks for the response, yes exactly. Perhaps i am overlooking an option, i already tried the sort() and itemInsertLocation() options but those do not seems to prevent this behaviour.
I am using the React component by the way, not sure if that matters in this case.

Adding it now 👍

Added itemInsertLocationFreedom in version 4.1.0, set to false to stop users from picking drop locations.

@rikschennink that's great. Works like a treat, thanks!


Airlock UT fix: Add missing mock and property value

Resolves #2935
What is being addressed
Added missing mock patch and added an azure_resource_id property to the airlock review resource mock object to fix broken test

/test-force-approve

/test-force-approve


feat: initial kubectl layer construct

This is nearly a direct copy from https://github.com/aws/aws-cdk/tree/main/packages/%40aws-cdk/lambda-layer-kubectl with some changes to make it v2-compatible and projen-compatible.
Note: this exposes a kubeCtlLayer construct, not the final form kubeCtlAsset. I figure it is better to start here and then update this repo in subsequent PRs. However, that means there are some inconsistencies with what I say this library exposes -- since this is not meant for active use right now, I feel like that is ok and will be corrected in a future PR.

Is there an integration test to bring over from aws-cdk? Otherwise, looks good

No integ test in this module


⚠ Processors has degraded performance

In d03dbe0, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 52 ms

Resolved: Processors performance has improved in 8b067e8.


Emmet single or multicursor not working on Laravel Blade

VSCode Version: 1.14.1
OS Version: Windows 7 32bit

Steps to Reproduce:

Followed instruction on the release notes. Single cursor works if I removed the change the emmet.useNewEmmet to false
Blade extension https://marketplace.visualstudio.com/items?itemName=onecentlin.laravel-blade

"emmet.syntaxProfiles": {
    "blade": "html"
},
"emmet.useNewEmmet": true,

Reproduces without extensions: No

@mrkalmdn You need to use emmet.includeLanguages and not emmet.syntaxProfiles
In the new emmet model, we are restricting the use of emmet.syntaxProfiles setting to as described in https://docs.emmet.io/customization/syntax-profiles/
As in to define how the output should look like. eg: use case, self closing tags etc.
Also, when you set emmet.includeLanguages, reload VS Code for the change to take affect.
I just fixed this issue of needing the reload, so you won't need to reload in Insiders from tomorrow.

Thank you @ramya-rao-a. However, your suggestion only works for single cursor.
Sent from my Google Nexus 5 using FastHub

Works for multi cursor as well

That's wierd. I will try it again later and will update you with the result. Thanks again.
Sent from my Google Nexus 5 using FastHub

Its working. I just forgot to set the emmet.showExpandedAbbreviation to always. Thanks

no problem, Happy Coding!


Add TypeScript demo to Checkbox

[ ] I have followed (at least) the PR section of the contributing guide.

I'm not understanding this failure at all.  Any advice?

@donigianrp I have accepted the changes. We have a flakiness issue.


Paste Entire History

It would be cool to paste the entire history delimited by a newline.

@shammellee There is no plan to implement the function to paste all the history by newline.
However, since the history export function will be implemented in the future, please substitute with it.
Thanks 👍

Cool!


Feature: Show processedBy on jobs

We've been using BullMQ to distribute workloads across multiple servers, and so far have been amending the job data to include a __workerHost: "hostname1" property so we can tell where a job was processed.
Reading through the BullMQ docs today, I noticed that jobs can have a processedBy property that is set when a Worker is instantiated with a name option.
What are your thoughts on adding it to the job card, perhaps under the "Process started at" part of the timeline (see attached screenshot)?
Happy to submit a PR for same if that's something people would find useful.

Thanks!

Hi, this looks great to me.
Can you make a PR for it?

Think it's ready for review! Tested locally with BullMQ v5.7.1 and working as expected.


Invalid value for argument cmd: 'fish' is not executable

environment

vim: Nvim 0.7
OS: Windows 11 Pro (22H2)
What is your airline configuration: ???
if you are using terminal:
terminal: Powershell (on Windows Terminal)
if you are using Neovim:
does it happen in Vim: Yes

problem
Hi, today I installed vim-airline via vimplug and it gave me an error like:
Error detected while processing function airline#extensions#branch#get_head[1]..airline#extensions#branch#head[6]..<SNR>85_update_untracked[42]..airline#async#vcs_clean[6]..airline#async#nvim_vcs_clean: line   24: E475: Invalid value for argument cmd: 'fish' is not executable
I tried to delete the files and reinstall them but it didn't help. What should I do?

check your shell configuration. Apparently you have set shell option to fish?

Where can I check it?

Well, how did you configure neovim?

check :verbose set shell?

Wow thanks! I found it, should I change it to "powershell"?

I don't know. What shell are you using?

Powershell currently, and yeah I change it to that and it fixed it. Thanks a lot!

I have the same issue but I am trying to use a login shell:
let &shell='/bin/bash --login'

https://vi.stackexchange.com/questions/16019/neovim-terminal-not-reading-bash-profile
to get this behavior . It works fine without vim-airline.

Please show the complete error message

Am 16.08.2022 um 21:46 schrieb satishskamath @.***>:

I have the same issue but I am trying to use a login shell:
let &shell='/bin/bash --login'
https://vi.stackexchange.com/questions/16019/neovim-terminal-not-reading-bash-profile
to get this behavior . It works fine without vim-airline.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.

also, can you please check what your shell is actually set to? Because if you have set the shell option to bash then vim-airline cannot complain about the shell being set to fish

Hi @chrisbra ,
Thanks for your reply.
Error detected while processing function airline#extensions#branch#get_head[1]..airline#extensions#branch#head[6]..<SNR>83_update_untracked[42]..airline#async#vcs_clean[6]..airline#async#n
vim_vcs_clean:
line   24:
E475: Invalid value for argument cmd: '/bin/bash --login' is not executable

This is the error, that I see and it is because I am trying to launch a login shell rather than a normal bash shell. The operating system is RHEL and the default shell is bash.
If I remove:
Plug 'vim-airline/vim-airline'

I don't see the error message.

so it works with :set shell=bash?

Try to configure it properly:
``
set shell=bash
set shellcmdflag=-lc

The error goes away with:
set shell=bash
set shellcmdflag=-lc

But the whole purpose I did it for was to open terminals within neovim such that they will be treated as login shells. The terminal within does not use shellcmdflag it seems. But that is a problem of neovim terminal itself I guess. This issue can be considered resolved. Thanks @chrisbra .

I don't understand why you need a login shell. Note: I believe yo can also use :term bash --login Setting the 'shell' option with additional arguments is going to ask for trouble as you noticed.

I wanted a login shell as I want the terminal to execute certain commands in my .bash_profile but I now moved them to my .bashrc. So those are working now. Thanks for the note. :)


GTAG Not loading when expected

Describe the bug
GTAG script doesn't appear in the page source upon first page load of a new session. I've observed this in our installation, the script doesn't appear in the source code for a new session until the page is completely refreshed. When opening a page in a new browser or in incognito mode, the site's source code lacks the presence of gtag.js as the user navigates through the site. It only becomes visible in the source code after the user refreshes the page. I’ve tested this a few times and it seems to be very consistent and there does appear to be data flowing to Google analytics. But I fear it’s only showing people that have previous sessions cached in their browser. I’ve posted the question in the community slack channel to see if I can get some insight.
Before Refresh and while navigating around after accepting the terms.

After Page Refresh

To Reproduce
Steps to reproduce the behavior:

Add GTAG key to config and restart service
Navigate to site with a browser that doesn't have a cached session
View source code (notice gtag script isn't present)
Navigate site without refreshing page and the code is still not there.
Refresh page and script suddenly shows up at the bottom of the code.

Expected behavior
Gtag script should have been processed and delivered upon initial page load.
I'm not sure if it's intentionally being blocked until after the user click "That's OK" but I would assume the script would than be automatically loaded, otherwise a lot of useful metrics will be lost.

Related work
N/A

@DonRichards : I can verify that the GTag is intentionally blocked until the user gives permissions via the popup asking them to allow tracking.  Per GDPR (and similar privacy policies), DSpace cannot do any tracking until the user provides permissions to do so.  So, yes, initial data may not be tracked until the user provides permissions.  That's how the code is expected to work at this time.
That said, I haven't had a chance to retest the behavior of the GTag locally at this time.  It's possible there is a bug where it's not being loaded after permissions are given by the user.

@tdonohue Just a suggestion, but it's likely beneficial to have the page reload upon granting permissions. This ensures that the page load and subsequent AJAX-style fetches are accurately tracked.

I wouldn't mind offering but I don't know where this logic is stored so I can't estimate how much effort it would take.

@DonRichards : I admit, I'm not the best person to provide advice on how to fix this issue.  It may need some investigation as to how best to force a reload, as the tool used to granting permissions is a plugin called Klaro: https://klaro.org/   So, some of the code in this tool is not under control by DSpace.  The main Klaro configs are found here: https://github.com/DSpace/dspace-angular/tree/main/src/app/shared/cookies
So, you are welcome to investigate this and see if you can figure it out.  If so, send us a PR.  If not, no worries.  (We do not require an estimate of effort or anything like that.)


callbacks, The Context is already closed

Trying to handle JavaScript like
events.on('event', (event) => {
   event.setState(5);
});

with Graal/Java like
try (Context context = Context.newBuilder().allowAllAccess(true).build()) {
  context.getBindings("js").putMember("events", new Events(this));
  context.eval("js", javascript);
}

...

public class Events {
  public void on(String event, Consumer<Event> callback) {
    // ...
  }
}

when the event happens Java-side, I use callback.accept(javaEvent) to trigger it.
But, this throws the error:
java.lang.IllegalStateException: The Context is already closed.
Is there a better solution to adding event handlers via JavaScript?

You do not provide a full test-case. So, it is hard to see what is your problem exactly. Isn't the main problem that you close your Context (by exiting the try-with-resources block) before you use your callback?

@iamstolis yes, the problem is exactly that I close the context before calling the callback.
But the callback could be called at any time, and any number of times, before the application ends.
Am I forced to keep the context open the whole time? Seems like it might get out of hand when there are multiple contexts.
That's why I ask the last question, is there an established best way to have callbacks in graal?

Am I forced to keep the context open the whole time?

Yes, the Context holds all the necessary context needed for the execution of your code. If you close it then you cannot use it.

Seems like it might get out of hand when there are multiple contexts.

It is like any other resource (for example, OutpuStream or InputStream). If you do not manage it carefully then things may "get out of hand".

I am closing this, if you have any follow-up questions please re-open, thanks.

I had the same problem , graaljs version is 22.2.0   @wirthi
Instructions:
// This code will be abnormal in the spring bean
private  Context.Builder ctxBuilder; // ctxBuilder build in afterPropertiesSet method
public void evalJS(){
try ( Context context = ctxBuilder.build()){
context.eval(JavaScriptLanguage.ID, script);
Value jsFunc = context.getBindings(JavaScriptLanguage.ID).getMember(func);
return jsFunc.execute(params).as(Object.class);
}
}
Solution：
not use try resource

I believe you should not return the result from that function. That is highly dangerous - at the very least, this might lead to a huge memory leak, as you open many new Context objects and never close them (as long as the returned value still lives).
If you really require that, then you should have a global Context for this thread and execute all similar cases via that shared context. Of course, this has other downsides, like weaker encapsulation (might be a problem in multi-tenant setups).
What kind of Objects do you return here, what do they represent? JavaScript arrays, JavaScript objects, ...? A safer bet would be to return Java data structures.

Thanks , The return value type of this method is JavaObject, Serialize it to JsonNode using jackjson,and close Context

2022年11月24日 22:02，Christian Wirth @.***> 写道：
I believe you should not return the result from that function. That is highly dangerous - at the very least, this might lead to a huge memory leak, as you open many new Context objects and never close them (as long as the returned value still lives).
If you really require that, then you should have a global Context for this thread and execute all similar cases via that shared context. Of course, this has other downsides, like weaker encapsulation (might be a problem in multi-tenant setups).
What kind of Objects do you return here, what do they represent? JavaScript arrays, JavaScript objects, ...? A safer bet would be to return Java data structures.
—
Reply to this email directly, view it on GitHub https://github.com/oracle/graaljs/issues/374#issuecomment-1326494600, or unsubscribe https://github.com/notifications/unsubscribe-auth/AY4IYSPWIJNEYECG6UX77HDWJ5YQJANCNFSM4TUEA6AA.
You are receiving this because you commented.


Use axel for downloading?

It's really slow right now...

I see adding axel as a really bad idea. It’s latest stable release is almost 5 years old, and after trying it extensively in real situations with download urls present in casks, I can say that the amount of times the “too many redirects” error occurs is absolutely ridiculous (lots of similar found only, without any resolutions). aria2 is always mentioned as the superior alternative.
Alternatives aside, the point is we’re just going to create more issues1. The opinions expressed in homebrew seem extremely valid, to me.
If any maintainer feels strongly about including this, feel free to reopen it. I say we wait and see.

1Issues that are incredibly difficult to debug. curl is predictable down to its version, because it comes with OS X. Third-party downloaders are the extreme opposite.


SSH Tunneling

⚠ Please verify that this feature request has NOT been suggested before.

[X] I checked and didn't find similar feature request

🏷 Feature Request Type
API
🔖 Feature description
Is there an option to use SSH Tunneling so we can access services which are not publicly accessible (from a remote server)?
We have mysql and mongodb services from other servers that are not externally accessible and I want to monitor it from an uptime kuma instance from different server.
✔ Solution
none
❓ Alternatives
No response
📝 Additional Context
No response

I am assuming your environment is

internal
public

database
backend, uptime-kuma

And the backend also has an uptime monitor.
Would it not be better to include the status of the underlying infrastructure in the backend status?
Reasoning:

This would alert you in case one of the infrastructure pieces goes down
Databases are build like tanks nowadays.
The logs from the backend will tell you clearly that the database is not healthy.
=> not a big downside to include this here
Adding such a tunnel adds extra complexity which you will have to maintain.

Another option is to use the push monitor, i.e. the database tells uptime-kuma periodically that it is healthy. see #279

Oh I did not know about this. I think this would be a great alternative to ssh tunneling.  Thanks for recommending me this option (push monitor).
I think I missed this while browsing the list of monitors.


Add missing button titles

Issue: #6123
What I did

Added titles to some of the image buttons that were missing them. This helps to meet WCAG 2.1 (Level A) for accessibility.

WCAG 2.1 Understanding Success Criterion 4.1.2: Name, Role, Value
Deque University's guidance on buttons having discernible text

How to test
Run any of the examples and inspect the adjusted buttons to see that they now have a title attribute specified. These issues can also be picked up by Lighthouse in the Accessibility audit in the Chrome Developer Tools.

Good job @aamct2
One notice: when you update UI you must regenerate snapshots for test passes.
More information you can read here.
When the snapshots will be updated i will merge PR.
Could you update the snapshots?

Thanks!


start path with file:/// so that intellij turns it into a link in the console

Your feature request may already be reported!
Please search in the issues before creating a new one.
Expected Behavior
one can click in the console on the path related to the issue and can jump there immediately
Current Behavior
the path is in the console but one has to go there manually
Context
Following an example:
/home/robert/projects/kbox/src/jvmMain/kotlin/ch/tutteli/kbox/JvmSynchronized.kt - 5min debt
        EndOfSentenceFormat - [JvmSynchronized] at /home/robert/projects/kbox/src/jvmMain/kotlin/ch/tutteli/kbox/JvmSynchronized.kt:3:1

if it would be the following, then it would be recognised by intellij as link and would be clickable:
/home/robert/projects/kbox/src/jvmMain/kotlin/ch/tutteli/kbox/JvmSynchronized.kt - 5min debt
        EndOfSentenceFormat - [JvmSynchronized] at file:///home/robert/projects/kbox/src/jvmMain/kotlin/ch/tutteli/kbox/JvmSynchronized.kt:3:1

Much nicer isn't it? :slightly_smiling_face:
I can also provide a PR if you can give me a pointer where to look

Yes it makes sense 👍 Perhaps all the paths should be updated (not just the second one in your example)?
If you want to contribute you should look into those files:
https://github.com/detekt/detekt/tree/main/detekt-core/src/main/kotlin/io/gitlab/arturbosch/detekt/core/reporting/console

As a side note, running the detekt tasks in the IDE allows me to click on the link directly

Version: IntelliJ Idea 2021.1.3

Perhaps all the paths should be updated (not just the second one in your example)?

I would only update paths which include a line number. I'll draft a PR.

Echoing @marschwar, it works for me in intelliJ console without the additional file://

@chao2zhang when you say in the IntelliJ console, then you are also referring to the detekt-plugin right? if you ran ./gradlew detekt then it does not, isn't it?

🤔 I'm not 100% sure here. For example, the "basic" Terminal from mac doesn't allow to click that kind of links. But iTerm2 does. I'm a bit worried that adding file:// could break another terminals.

Terminal wise I don't see an issue, either the terminal renders such things as links and allows clicking on it or it does not (or ask beforehand and the like). Why do you think it could break someone's terminal?


[format][changelog-json] Remove the support of changelog-json format

[task] Remove changelog json format support #901

And the link incorrectly points to an empty page in GitHub wiki. I think we can add a footnote here suggesting changelog-json is deprecated, and fix the broken link.

Nice catch, I decide to delete the piece as they're rarely used( if users use it they have found the link error).


[PE-D][Tester E] findT [d/DESCRIPTION]does not work as documented in the User Guide

tried to findT with d/[description], but was given an empty list

Labels: severity.Medium type.FunctionalityBug
original: wongyewjon/ped#2

duplicate


UNSAFE_componentWillReceiveProps console error

Describe the bug
Deprecated lifecycle console error. It seems like some dependency components may need upgrading.
To Reproduce
Open the palette.
Expected behavior
No errors in console.
Desktop (please complete the following information):

OS: macOS 11.4
Browser Chrome
Version 91.0.4472.114

Additional context
Warning: Using UNSAFE_componentWillReceiveProps in strict mode is not recommended and may indicate bugs in your code. See https://reactjs.org/link/unsafe-component-lifecycles for details.

* Move data fetching code or side effects to componentDidUpdate.
* If you're updating state whenever props change, refactor your code to use memoization techniques or move it to static getDerivedStateFromProps. Learn more at: https://reactjs.org/link/derived-state

Please update the following components: Autosuggest, Autowhatever

That leads to a react-autosuggest issue: https://github.com/moroshko/react-autosuggest/issues/624. Apparently fixed and merged (https://github.com/moroshko/react-autosuggest/pull/681), but seems like they haven't released a new version since then. I'll leave this issue open until they release the fix. In case they release it and you don't want to wait for a new release from this package, use the resolve option in package.json to resolve the new version.

@adi518 I've created a simple example you can reference. Please note that I cannot reproduce your issue. Can you publish an example of your code that cause the error message?

Closing unable to reproduce

Sorry for the delayed response.

@adi518 react-command-palette is on react-autosuggest v10.0.1. I've been unable to reproduce your error, we can continue to troubleshoot you issue outside this repo

I realized what the actual issue is. I'm using React 17 in strict mode, so that issue is not really relevant. As for the react-autosuggest version. Their latest version is 10.1.0. GitHub collapses the last three releases, so you can miss it. I'm not saying it will fix it (it won't), but might consider upgrading to latest.
The relevant react-autosuggest issue is this: https://github.com/moroshko/react-autosuggest/issues/624. Probably applicable to react-autowhatever as well.

@adi518 I routinely update all dependencies. As soon as the react-autosuggest team pushes a fix I’ll bump my package.json. There will be a new issue for that so I’ll leave this closed for now. Thanks for the update.


Develop simple UI

Query components: https://dev-blog.apollodata.com/query-components-with-apollo-ec603188c157

Use: https://github.com/frontsideair/yarnhook

Use Strip font smoothing and text rendering

https://www.leejamesrobinson.com/blog/how-stripe-designs-beautiful-websites/


Replaced shims for atob and btoa with native implementations

Changes

Removed external packages for atob and btoa
Added vendors based on the buffer implementation for atob and btoa to expose them via require
Global access to be enabled via uniscope
⚠ Global access to these is not considered deprecated now

@greptileai

@greptileai


Ability to tag all resources and individual resources in the config.

Describe the feature you'd like
We've deployed this solution as part of the Migration Acceleration Program (MAP) from AWS. One of the requirements in this program is to tag all resources in an AWS account with a specific key.
Would be nice to be able to tag all resources with a specific key/value.
Next to that it would also be great if we can tag resources seperately. For now it only seems that the vpc config (resources) can handle adding tags to its properties.

Yes, keen to have tagging feature which can be deployed to all the resources.

I am closing this issue as a duplicate of #99. This feature will be released in the next major LZA release currently planned for the end of Q3.

This issue has not been resolved


MINOR: don't merge: testing dataset-serialize benchmark

Using this PR to test whether https://github.com/apache/arrow/pull/38466 fixed https://github.com/apache/arrow/issues/38438.

@ursabot please benchmark name=dataset-serialize lang=Python


problem with ODBC connection to exasol

Hi,
I am trying to run the following code:
library(RODBC)
library(exasol)

drv <- dbDriver("exasol") **PASS**
con <- dbConnect(drv, exahost = "host", uid = "my_id", pwd ="my_pass", schema = "SCHEMA") .  **PASS**
dbListTables(con) **Throws an error**

error:
Error in try(.Call(C_asyncRODBCQueryFinish, slot, 1)) :
Unknown ODBC error
Error in exa.readData(conn, qstr, ...) :
Could not allocate SQLAllocHandle
Error in exa.readData(conn, qstr, ...) : Unknown ODBC error
I am using mac, os 10, Exasol ver 5.17, and am able to access the DB from the Exaplus and see tables etc..
thanks!
Shahar

Is there any update on this ? I have a same issue with Mac OS 10.14.
error:
Error in try(.Call(C_asyncRODBCQueryFinish, slot, 1)) :
  Unknown ODBC error
Error in exa.readData(conn, statement, ...) :
  Could not allocate SQLAllocHandle (-2)
Error in exa.readData(conn, statement, ...) : Unknown ODBC error

Can you tell more about the tools/drivers/components you use? Version numbers and the like?
I have some faint memories of seeing the same (or very similar error message) when I tried to use unixodbc. I had to remove it and use libiodbc. May it be the source of the issue in your case?

I'm facing the same issue
MacOS 10.14.6
Tried both libiodbc 3.52.13 from brew and unixodbc
Also downloaded and configured based on https://docs.exasol.com/connect_exasol/drivers/odbc/odbc_linux.htm
Exasol 6.2.4
platform       x86_64-apple-darwin15.6.0
arch           x86_64
os             darwin15.6.0
system         x86_64, darwin15.6.0
status
major          3
minor          6.3
year           2020
month          02
day            29
svn rev        77875
language       R
version.string R version 3.6.3 (2020-02-29)
nickname       Holding the Windsock

Hey all,
I am going to close this ticket. Please try out with the updated versions.
Please open another ticket if the issue still persists.


contracts

here is stable contracts by order of priority:

[ ] escrow_basic
[ ] escrow
[ ] erc20
[ ] competition
[ ] governance
[ ] health_care

tasks:

[x] getmethod must have prog behavior on require and failif sections
passed/get_in_require_failif.arl
[x] the should be implicit (#117 issue)
passed/implicit_the.arl
[x] handle partial record when a default value is set for a field
passed/partial_record.arl
[x] state must be a constant when states is defined
passed/state_var.arl
[x] state cannot be assigned
type-errors/state_assignment.arl
[x] reject when 2 fields have the same identifier
type-errors/same_field_name.arl
[x] the error message is not explicit when there is not otherwise for let in formula
type-errors/no_otherwise.arl
[x] handle ghost variable in specification
passed/var_in_spec.arl
[x] tez * int should work like int * tez
passed/arith_tez.arl
[x] fill invariants variable declaration (invs in variable)
passed/test_var.arl

The field effect of Ast.specification should be an instruction, not a expression.

It is unclear in which context the variables invariants should be typed. Does a variable invariant can refer to some other variables. In the former case, could we have mutually recursive invariants (w.r.t their respective variables)?


Python API remove dependency on numpy

Dependency on numpy package in the Python API complicates the install of the materials-commons module (from PyPI). The numpy package is used in the API measurement interface for matrix value. In the method add_numpy_matrix_measurement, I am immediately pulling two lists from the numpy matrix: matrix.shape and matrix.value.toList() . I could get rid of the need for the numpy package , if I just made shape_list and value_list arguments to the API interface. Also, I would then need to rewrite the one test that makes a call to this method.

Not going to do this, now.


Update

What issue do you have? Please be as thorough and explicit as possible.
I'm on 3.9.0 version and hoobs inform me to update on 4.7.3
Process update seems complete fine but still in 3.9.0
Details of your setup.

Do you use (1) Homebridge (+ config-ui), (2) Homebridge (CLI) or (3) HOOBS?
Hoobs

Which version of Homebridge/HOOBS do you have?

3.3.2

Which platform do you run Homebridge/HOOBS on (e.g. Raspberry Pi/Windows/HOOBS Box)? Please also mention your version of Node.js/NPM if known.

Which version of this plugin (homebridge-ewelink) do you have? Has the issue started since upgrading from a previous version?

3.9.0

Which eWeLink devices do you have that are causing issues? Please include product models if applicable.

Please paste any relevant logs below.

15/2/2021, 09:15:10  WARN notsup Not compatible with your version of node/npm<EMAIL_ADDRESS>15/2/2021, 09:15:10
15/2/2021, 09:15:10 npm
15/2/2021, 09:15:10  ERR! code EEXIST
npm ERR! path /home/hoobs/.hoobs/node_modules/gtoken/node_modules/.bin/mime
15/2/2021, 09:15:10 npm
15/2/2021, 09:15:10 ERR! Refusing to delete /home/hoobs/.hoobs/node_modules/gtoken/node_modules/.bin/mime: is outside /home/hoobs/.hoobs/node_modules/gtoken/node_modules/mime and not a link
npm ERR! File exists: /home/hoobs/.hoobs/node_modules/gtoken/node_modules/.bin/mime
npm ERR! Remove the existing file and try again, or run npm
npm ERR! with --force to overwrite files recklessly.
15/2/2021, 09:15:10
15/2/2021, 09:15:10 npm ERR!

Solved. Needs to update the node


Fixed class_attributes_separation processing class with multiple trait imports

Closes https://github.com/FriendsOfPHP/PHP-CS-Fixer/issues/5954.

Coverage remained the same at 92.358% when pulling c891de1349ff9a1099183b84d8e0cc2a24b9c645 on GrahamCampbell:failing-test-class-attributes-sep-method into a339a06f3116d18050173f45f0c574651bbaa259 on FriendsOfPHP:master.

Thank you @GrahamCampbell.


Add command to migrate playlist scores from multiplayer_scores to solo_scores

This is to be used to preserve ongoing featured artist / spotlight room's scores as we migrate scores to the new table.
It means we can continue to move forward without worrying about breaking things, basically.
It's made to only run for playlists, and not migrate all scores, but could be expanded in the future if we want to have more coverage.

This should be ready for a re-review. I've tested against production (without running the actual inserts) and things look to be correct.

Aside from https://github.com/ppy/osu-queue-score-statistics/pull/154/commits/6c8918bc7cf9ddae66ad62df343f2050c9167151, is good :+1:


Fix typos

nit;

the plural form of whitespace would be correct.
'replace A with B' sounds much better.

Thanks @xissy :)


Add Chorus to the list of example Blacklight projects

Per this thread: https://groups.google.com/forum/#!topic/blacklight-development/9TX0QO04BsU

Okay, opened a PR.   Going to close this now.


refactor(@angular-devkit/core): remove deprecated fs, object and array APIs

BREAKING CHANGE:
The below APIs have been removed without replacement

fs namespace
clean
mapObject

@dgp1130, actually users will need to create a similar functionality in their project. Node itself doesn't provide these helpers.

Right, I just meant that users should compose existing Node APIs just like we did. I get that it's probably a suboptimal interface when all they want to know is "Is this a directory?" But that's a Node problem, not an Angular one, so it makes sense that they shouldn't rely on devkit for such a use case.


Add Wikibase repo technical context

https://deploy-preview-37--wikidata-wikibase-architecture.netlify.app/systems/WikibaseRepo/03-Context_and_Scope.html#technical-context
Bug: T271951

Comparing this diagram to the tech context diagram for client that is merged I notice that:

In client we represent MediaWiki, we have not done that here, or at least not in the same way? (MW in boxes vs a bit grey MediaWiki box)
If Repo DB is going to be a building block in Repo, then perhaps we should also make Client DB a building block in client (not needed in this PR, just a thought)
Should we split EntityUI and SpecialPages in this tech diagram? I have no doubt that we will split them into separate blocks further into the documentation?
Should Kafka actually be represented as an external block rather than just text that on a label arrow?

Comparing this diagram to the tech context diagram for client that is merged I notice that:

In client we represent MediaWiki, we have not done that here, or at least not in the same way? (MW in boxes vs a bit grey MediaWiki box)
If Repo DB is going to be a building block in Repo, then perhaps we should also make Client DB a building block in client (not needed in this PR, just a thought)
Should we split EntityUI and SpecialPages in this tech diagram? I have no doubt that we will split them into separate blocks further into the documentation?
Should Kafka actually be represented as an external block rather than just text that on a label arrow?

Thanks, good questions! I had reasons for most of the differences, but I'm not sure if we're all on the same page there!

Comparing this diagram to the tech context diagram for client that is merged I notice that:

In client we represent MediaWiki, we have not done that here, or at least not in the same way? (MW in boxes vs a bit grey MediaWiki box)

This again boils down to documenting Repo as a system/an application vs a MediaWiki extension. The difference in the two diagrams as they stand tells me that WikibaseClient is a "plugin" (= extension) that lives inside MediaWiki and adds functionality to another system, whereas Wikibase Repo is a system of its own, which makes sense to me. When regarded as a system I don't think that it makes sense to regard MediaWiki as an external system to the Repo. I imagine it should show up in the building block view, though.

If Repo DB is going to be a building block in Repo, then perhaps we should also make Client DB a building block in client (not needed in this PR, just a thought)

Repo DB is in this diagram because it's a component that is directly used by an external system (Client). Is this the case for the Client DB too?

Should we split EntityUI and SpecialPages in this tech diagram? I have no doubt that we will split them into separate blocks further into the documentation?

Yup, that sounds good to me. I'll change it. I grouped them here initially because they fulfill similar functions, but I can see why we might want to separate them.

Should Kafka actually be represented as an external block rather than just text that on a label arrow?

I documented it as a protocol in the spirit of this tip. If it's more than that, it probably deserves its own block, but I don't know enough about it.

Thanks, good questions! I had reasons for most of the differences, but I'm not sure if we're all on the same page there!

Comparing this diagram to the tech context diagram for client that is merged I notice that:

In client we represent MediaWiki, we have not done that here, or at least not in the same way? (MW in boxes vs a bit grey MediaWiki box)

This again boils down to documenting Repo as a system/an application vs a MediaWiki extension. The difference in the two diagrams as they stand tells me that WikibaseClient is a "plugin" (= extension) that lives inside MediaWiki and adds functionality to another system, whereas Wikibase Repo is a system of its own, which makes sense to me. When regarded as a system I don't think that it makes sense to regard MediaWiki as an external system to the Repo. I imagine it should show up in the building block view, though.

If Repo DB is going to be a building block in Repo, then perhaps we should also make Client DB a building block in client (not needed in this PR, just a thought)

Repo DB is in this diagram because it's a component that is directly used by an external system (Client). Is this the case for the Client DB too?

Should we split EntityUI and SpecialPages in this tech diagram? I have no doubt that we will split them into separate blocks further into the documentation?

Yup, that sounds good to me. I'll change it. I grouped them here initially because they fulfill similar functions, but I can see why we might want to separate them.

Should Kafka actually be represented as an external block rather than just text that on a label arrow?

I documented it as a protocol in the spirit of this tip. If it's more than that, it probably deserves its own block, but I don't know enough about it.

In client we represent MediaWiki, we have not done that here, or at least not in the same way? (MW in boxes vs a bit grey MediaWiki box)

This again boils down to documenting Repo as a system/an application vs a MediaWiki extension. The difference in the two diagrams as they stand tells me that WikibaseClient is a "plugin" (= extension) that lives inside MediaWiki and adds functionality to another system, whereas Wikibase Repo is a system of its own, which makes sense to me. When regarded as a system I don't think that it makes sense to regard MediaWiki as an external system to the Repo. I imagine it should show up in the building block view, though.

Makes sense to me.
I feel like we need to document this in our docs somehow.

If Repo DB is going to be a building block in Repo, then perhaps we should also make Client DB a building block in client (not needed in this PR, just a thought)

Repo DB is in this diagram because it's a component that is directly used by an external system (Client). Is this the case for the Client DB too?

No, I think you've done the right thing here and the client db should not be exposed at this level.

Should Kafka actually be represented as an external block rather than just text that on a label arrow?

I documented it as a protocol in the spirit of this tip. If it's more than that, it probably deserves its own block, but I don't know enough about it.

So we probably want to add some more detail here, but also, not just add Kafka as a block.
So MediaWiki / EventLogging sends the events that it generates to an API / Service called EventGate https://wikitech.wikimedia.org/wiki/Event_Platform/EventGate
EventLogging / MediaWiki itself is unaware of backends, other than the fact that it sends events to an API in a certain JSON structure.
EventGate (a node service) then does stuff and writes things to a backend, in WMF production this is kafka.
The Query update then reads data directly from kafka topics.
So I guess it could be worth showing EventLogging -> EventGate -> Kafka -> Updater at this level?

In client we represent MediaWiki, we have not done that here, or at least not in the same way? (MW in boxes vs a bit grey MediaWiki box)

This again boils down to documenting Repo as a system/an application vs a MediaWiki extension. The difference in the two diagrams as they stand tells me that WikibaseClient is a "plugin" (= extension) that lives inside MediaWiki and adds functionality to another system, whereas Wikibase Repo is a system of its own, which makes sense to me. When regarded as a system I don't think that it makes sense to regard MediaWiki as an external system to the Repo. I imagine it should show up in the building block view, though.

Makes sense to me.
I feel like we need to document this in our docs somehow.

If Repo DB is going to be a building block in Repo, then perhaps we should also make Client DB a building block in client (not needed in this PR, just a thought)

Repo DB is in this diagram because it's a component that is directly used by an external system (Client). Is this the case for the Client DB too?

No, I think you've done the right thing here and the client db should not be exposed at this level.

Should Kafka actually be represented as an external block rather than just text that on a label arrow?

I documented it as a protocol in the spirit of this tip. If it's more than that, it probably deserves its own block, but I don't know enough about it.

So we probably want to add some more detail here, but also, not just add Kafka as a block.
So MediaWiki / EventLogging sends the events that it generates to an API / Service called EventGate https://wikitech.wikimedia.org/wiki/Event_Platform/EventGate
EventLogging / MediaWiki itself is unaware of backends, other than the fact that it sends events to an API in a certain JSON structure.
EventGate (a node service) then does stuff and writes things to a backend, in WMF production this is kafka.
The Query update then reads data directly from kafka topics.
So I guess it could be worth showing EventLogging -> EventGate -> Kafka -> Updater at this level?

I feel like we need to document this in our docs somehow.

+1 yup.

So I guess it could be worth showing EventLogging -> EventGate -> Kafka -> Updater at this level?

After reading a bit more about it, that definitely makes sense to me. I added it to the diagram!

I feel like we need to document this in our docs somehow.

+1 yup.

So I guess it could be worth showing EventLogging -> EventGate -> Kafka -> Updater at this level?

After reading a bit more about it, that definitely makes sense to me. I added it to the diagram!

In client we represent MediaWiki, we have not done that here, or at least not in the same way? (MW in boxes vs a bit grey MediaWiki box)

This again boils down to documenting Repo as a system/an application vs a MediaWiki extension. The difference in the two diagrams as they stand tells me that WikibaseClient is a "plugin" (= extension) that lives inside MediaWiki and adds functionality to another system, whereas Wikibase Repo is a system of its own, which makes sense to me. When regarded as a system I don't think that it makes sense to regard MediaWiki as an external system to the Repo. I imagine it should show up in the building block view, though.

Makes sense to me.
I feel like we need to document this in our docs somehow.

It's somewhat documented in Developing Wikibase Repo as a mw extension, and we can also write things down in the section "Solution Strategy". Seems like it's the appropriate place judging by arc42's docs.

In client we represent MediaWiki, we have not done that here, or at least not in the same way? (MW in boxes vs a bit grey MediaWiki box)

This again boils down to documenting Repo as a system/an application vs a MediaWiki extension. The difference in the two diagrams as they stand tells me that WikibaseClient is a "plugin" (= extension) that lives inside MediaWiki and adds functionality to another system, whereas Wikibase Repo is a system of its own, which makes sense to me. When regarded as a system I don't think that it makes sense to regard MediaWiki as an external system to the Repo. I imagine it should show up in the building block view, though.

Makes sense to me.
I feel like we need to document this in our docs somehow.

It's somewhat documented in Developing Wikibase Repo as a mw extension, and we can also write things down in the section "Solution Strategy". Seems like it's the appropriate place judging by arc42's docs.

Good point, I created https://phabricator.wikimedia.org/T272382 so we don't forget about it.

Good point, I created https://phabricator.wikimedia.org/T272382 so we don't forget about it.

beat my by seconds

beat my by seconds


:sparkles: WFP-2222: grab pageUrl to use as survey monkey custom vari…

…able
So this is a PR just to show what I did to grab the url and add into the survey monkey link so we can get the url of the page where the user has come from and see if they think the page is useful or not.
This ticket https://dsdmoj.atlassian.net/jira/software/c/projects/WFP/boards/601?selectedIssue=WFP-2222 has more information about how it works with survey monkey.
When picking up the piece of work we'd need to add a banner that links to the survey but in this PR I've just added it into the footer as I just wanted to see if we'd get the results coming through the survey.

Closing this PR as we have done this and allowed for global access without the need to add pageUrl to the individual controller methods


Fail to start ECM - MySQLNonTransientConnectionException

Describe the bug
After installation, when I run the script to start the ECM (ENGINECONNMANAGER), it fail after few seconds, and the error log shows as below:
"Failed to register info to linkis manager: com.webank.wedatasphere.linkis.common.exception.ErrorException: errCode: 0 ,desc: operation failed(操作失败)s！the reason(原因)：MySQLNonTransientConnectionException: Public Key Retrieval is not allowed ,ip: <IP_ADDRESS> ,port: 9101 ,serviceKind: linkis-cg-linkismanager"
after a while , the java application is killed, showing in logs like that
"
2021-08-17 18:33:31.320 [INFO ] [SpringContextShutdownHook               ] c.n.u.c.ShutdownEnabledTimer (72) [cancel] - Exception caught (might be ok if at shutdown) java.lang.IllegalStateException: Shutdown in progress
at java.lang.ApplicationShutdownHooks.remove(ApplicationShutdownHooks.java:82) ~[?:1.8.0_292]
"
I also try to add some configuration inside the linkis.properties to enable the public key. But it doesn't help.
wds.linkis.server.mybatis.datasource.url=jdbc:mysql://<IP_ADDRESS>:3306/linkis?characterEncoding=UTF-8&allowPublicKeyRetrieval=true
The Mysql in my environment is 8.0.26, and run the whole things on MacOS.
The rest service can run in a long time, except from this one.
Hopefully can get help, Thanks!
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

Downgrade to MySQL 5.7, and watch the processlist inside DB, make the maximum connection larger and keep the wait_timeout within few minutes.


preview_definition not working anymore

I am pretty sure this feature (preview_definition) worked when I first installed lspsaga, but now I get an error every time I call it:

Other feature (including finder) are still working.

Yeah I encountered this issue some weeks ago...I don't know what is wrong...

Seems that this patch fixes the issue:
diff --git a/lua/lspsaga/provider.lua b/lua/lspsaga/provider.lua
index 22c0d86..3bc7321 100644
--- a/lua/lspsaga/provider.lua
+++ b/lua/lspsaga/provider.lua
@@ -443,7 +443,15 @@ function lspfinder.preview_definition(timeout_ms)
     print("No location found: " .. method)
     return nil
   end
-  result = {vim.tbl_deep_extend("force", {}, unpack(result))}
+
+  -- Result is not empty - there must be at least one element at this point
+  for k, v in pairs(result) do
+      if v ~= nil then
+        non_empty_res = v
+      end
+  end
+
+  result = {vim.tbl_deep_extend("force", {}, non_empty_res)}

   if vim.tbl_islist(result) and not vim.tbl_isempty(result[1]) then
     local uri = result[1].result[1].uri or result[1].result[1].targetUri

at least for me ( tested lua, python, php language servers ). Main problem is that the result in table is expected at index 1 but for example for pyright the result is returned at index 2 in table while unpack by default index from 1. I need to read up little bit documentation for nvim lsp and mainly vim.lsp.buf_request_sync than I could create pull request. I am not sure if this is also related to this issue https://github.com/glepnir/lspsaga.nvim/issues/230.

seems that there is already waiting merge request https://github.com/glepnir/lspsaga.nvim/pull/196 for this.


why is there a fork here?

https://github.com/andikscript/react-native-custom/blob/a73a15776a18e8b3aeb44d7808c3d4f9618dcea9/components/HeaderFolding/HeaderFolding.js#L65

used to set the status bar when the folding header has arrived at the border of the status bar header so that the color changes

ok thank for your answer


Signature mismatch while signing JSON message

I'm making a call to the RugCheck API and need to authenticate in order to get higher rate limits.  I have what I think is a fairly simple example.
Overall synopsis:
String secret key is converted to an int array
Keypair constructed via Keypair.from_bytes()
Message signed and verified
Signature converted to byte array
Body constructed with message and signature
Request sent
import json
import os
import time
import aiohttp
import asyncio
from solders.keypair import Keypair

# Load the configuration file
def load_config():
    return 'your secret key here'

# Generate the keypair from the stored secret key
def get_keypair():
    secret_key = load_config()
    secret_key_list = [int(x) for x in secret_key.split(',')]
    keypair = Keypair.from_bytes(secret_key_list)
    return keypair

# Sign the message using the keypair
def sign_message(keypair, message_obj):
    # Convert the message object to JSON string and then to bytes
    message_json = json.dumps(message_obj).encode('utf-8')
    return keypair.sign_message(message_json)

# Authenticate with the RugCheck API
async def authenticate_with_rugcheck():
    keypair = get_keypair()
    public_key = keypair.pubkey()

    # Construct the message object to sign
    message_to_sign = {
        "message": "Sign-in to Rugcheck.xyz",
        "timestamp": int(time.time() * 1000),  # Use milliseconds like in JavaScript
        "publicKey": str(public_key)
    }

    # Sign the message
    signature = sign_message(keypair, message_to_sign)

    # Verify with Solders
    message_bytes = json.dumps(message_to_sign).encode('utf-8')
    is_valid = signature.verify(public_key, message_bytes)
    assert is_valid, "Signature verification failed!"

    # Convert the signature to a list of integers
    signature_ints = signature.to_bytes_array()

    # Prepare the authentication request payload
    request_body = {
        "signature": {
            "data": signature_ints,
            "type": "ed25519"
        },
        "wallet": str(public_key),
        "message": message_to_sign
    }

    # Send the request to the RugCheck API
    async with aiohttp.ClientSession() as session:
        async with session.post('https://api.rugcheck.xyz/auth/login/solana', json=request_body, headers={"Content-Type": "application/json"}) as response:
            response_text = await response.text()
            if response.status == 200:
                data = await response.json()
                return data['token']
            else:
                print(f"Authentication failed. Status: {response.status}, Response: {response_text}")
                return None

# Main function to run the authentication
async def main():
    token = await authenticate_with_rugcheck()
    print(f"Token: {token}")

# Run the authentication process
asyncio.run(main())

Seems very simple but I get this back from RugCheck:
Authentication failed. Status: 400, Response: {"error":"signature mismatch"}
Here is the payload sent:
{
    "signature": {
        "data": [
            251,
            69,
            255,
            110,
            133,
            177,
            178,
            242,
            125,
            28,
            167,
            93,
            168,
            204,
            130,
            32,
            179,
            66,
            129,
            7,
            242,
            96,
            250,
            159,
            162,
            1,
            89,
            17,
            209,
            0,
            7,
            179,
            93,
            86,
            84,
            65,
            48,
            179,
            143,
            201,
            252,
            46,
            143,
            35,
            95,
            239,
            24,
            90,
            225,
            95,
            40,
            55,
            164,
            99,
            63,
            208,
            2,
            55,
            12,
            215,
            193,
            222,
            203,
            12
        ],
        "type": "ed25519"
    },
    "wallet": "4bKmYhhabZmUDWV6x9z4L79kaBMUBufE7NcL21nKHgN3",
    "message": {
        "message": "Sign-in to Rugcheck.xyz",
        "timestamp":<PHONE_NUMBER>249,
        "publicKey": "4bKmYhhabZmUDWV6x9z4L79kaBMUBufE7NcL21nKHgN3"
    }
}

I have a near carbon copy in JavaScript that works, so I know the endpoint works.  Clearly I am doing something wrong.

Can you check if the signature_ints and message_bytes look the same in your JS code?

Oh the message ints are different:
In Python we have 58, 32, 34
Whereas in JS we have 58, 34, 83

yeah this is just something to do with JSON and spaces - before Solders has any involvement


⚠ Processors has degraded performance

In 9181d96, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 161 ms

Resolved: Processors performance has improved in b4f4d81.


Crash: When trying to see anything with REI, the game just crashes

What were you doing when the crash occured? How can we replicate it?

First, Have REI (all updated) with Paradise Lost mod
Next, Try to see a recipe or just pass the mouse icon over the REI interface (REI items on right side)
Finally, The game crashes

Did it crash the client or server?
Both
Mod Version
1.6.5 - 1.17
Fabric API Version
0.12.12
Crash Report
https://pastebin.com/tMamPUx5

Other mods
You can see the mods i use in the 'latest.log' in Crash Report.
Additional Information
Using LauncherPhenix to play
(Couldnt paste the files due to "body is too long (maximum is 65536 characters).")

Idk why, but i linked crash report but it disappeared when i submitted,
anyway

https://pastebin.com/qDXGdSgM

I remember seeing this type of crash before and its due to whoever has the namespace of "uk.me.desert_island.rer.rei_stuff".
The Aether was not present within the actual trace of this crash, so im obliged to say its due to that other namespace, but @Jack-Papel can feel free to correct me if Im wrong here.

I don't know what that means exactly, can you explain more?
But i tested with various mods, and when i put the Paradise Lost in the game, it just crashes, so i'm pretty sure the Aether mod is the cause for the crash.
Thank you for the help btw!

@CDAGaming I wouldn't be too surprised if it was RecipeConfidence

@Jack-Papel that's weird
i do see the gud_recipe_confidence.jar in my latest.log
i do see Recipe Confidence in Mod Menu
but i can't see the actual .jar file in my .minecraft mods, i'm dumb or somethin? i'll link prints of my mods (some aren't in the actual name for some reasons, don't mind)

(Towelette is disabled via LauncherFenix tool)

Nope, you're not dumb. RecipeConfidence is a library we use for certain recipe stuff. It's included in the jar file of our mod, so you won't see it in your folder

Okay, thanks

From the logs, it looks to me like an issue with a Modern Industrialization REI plugin, but I'm not entirely sure. Though I don't think it's Paradise Lost causing it.
I recommend forwarding the issue to RoughlyEnoughItems, since they can probably diagnose the issue better than we can, or to Modern Industrialization.

Okay, i'll do that, but so the issue is compability with Modern Industrialization?
Because i am currently in my world with 150+ hours, and decided to put some adventure mod (and i cant even use REI in my world now, and can't load my world without Paradise Lost), and never crashed like that

Has this been resolved @MontMontgomery @Jack-Papel ?

Nope

and decided to put some adventure mod

Oh, I missed this before. The crash only occurs with this adventure mod? What's the mod called?

and decided to put some adventure mod

Oh, I missed this before. The crash only occurs with this adventure mod? What's the mod called?

Just Paradise Lost crashes, if a disable Paradise Lost, the game works just fine with REI

Looks like the actual error is caused by RoughlyEnoughResources, which must have some strange interaction with one of our dependencies, recipe confidence. Unfortunately it looks like you're playing on 1.17 which we can't easily support any longer, but removing RoughlyEnoughResources likely will fix the problem


Allow the access of the variable stack from within a function, not just the current context.

Not required.


Cannot find 'angular/compiler'

Hi,
I'm on windows 7 and when I run npm install I get the follow error.
'angular/compiler' is not in the npm registry.
How do I install angular 2.0 using npm ?

hi,your node version is so old. upgrade your node and npm.

Using the RC1 now. Should be installing @angular/.... Are you really using this quick start?


Switch uuid library to gofrs/uuid

Fixes https://github.com/Azure/azure-sdk-for-go/issues/3158

You will need to run gulp updatetestdep to update the test dependencies with the new package.

Hi @jhendrixMSFT I just updated the dependencies. But please hold on merging, I am working to see how many packages are impacted and if not so many, we could regenerate all of them in the next major version.
I am opening a PR in go SDK to see whether the APIs in these two packages are identical

@ArcturusZhang when do you want to release with this change?  Also note the merge conflicts.

@ArcturusZhang when do you want to release with this change?  Also note the merge conflicts.

@ArcturusZhang when do you want to release with this change? Also note the merge conflicts.

it may be better if we only have one big series of breaking changes in one major version.
Considering we just made the future mocking change, could we postpone this to the next next major version after we regenerate everything to pick up the future mocking fix?

@ArcturusZhang when do you want to release with this change? Also note the merge conflicts.

it may be better if we only have one big series of breaking changes in one major version.
Considering we just made the future mocking change, could we postpone this to the next next major version after we regenerate everything to pick up the future mocking fix?

Hi @jhendrixMSFT could you please merge this? We would like to release this change in this week's release.

Thanks!


Added test resources and import samples for Products and Events

Added:

Import Products samples
Import Products tests
Import Events samples
Import Products samples
Create and Delete test resources classes in TestResourcesSetupCleanup project.
Create BQ table/ Gcs bucket for Events in RetailEvents.Samples project setup folder
Create BQ table/ Gcs bucket for Products RetailProducts.Samples project setup folder

@vasilypascal Can we close this PR now that we have #1699 . Thanks!

@mkoshurnikov let me know about this one


SelectPanel2: Use html dialog

Drop AnchoredOverlay in favor of html dialog
using useAnchoredPosition for positioning now
Implemented click outside behavior suggested by @maximedegreve, see code comment for full context

https://github.com/github/primer/assets/1863771/f2a202cb-e2fc-4b9a-ac87-65d1d0815210
Alt text: When a SelectPanel is opened, it renders a dialog with a focus trap, you see that the accessibility panel only shows a dialog. Pressing the Esc key closes the panel. Looking at the elements panel, you can see that the dialog is rendered in a top layer

Question for @maximedegreve related to html dialog:
[Answered] We decided clicking outside the panel should not close the panel, we still hold the same opinion? Is there something we can do to make this not feel like a bug? See demo in storybook.
Update: If the user clicks outside, we nudge the user to use the actions in the footer. See demo

Hey @siddharthkp
I've previously raised this concern within Slack as well.
The cancel and save buttons are visually clear to indicate confirming is required in the dialog. However, this pattern isn't obvious to everyone, which can be frustrating. This is particularly true for long-time users, who have been on our platform for over 10 years and may find these changes annoying. Additionally, clicking on the background without any response can make it seem as though we've deliberately worsened the user experience, especially for those who are not familiar with those accessible patterns.
The best thing I think we can do now is introducing a gelatine or bounce effect on the buttons when this annoyance occurs? This could be an interesting and engaging way to guide users towards understanding and adopting the new behavior, without giving the impression that we've overlooked something that is an accessibility requirement.
https://github.com/primer/react/assets/980622/13f50498-66d3-43a3-b16c-53eaafc5b25d

I really like @maximedegreve's suggestion to "highlight" the buttons when somebody tries to close by clicking the background scrim.
I think we should also add this functionality to Dialog. @maximedegreve and other reviewers - how do you feel about this? This doesn't have to be part of this PR - we could create a follow-up issue or PR to do this.


expose boto3 clients

This to allow the package be used as library with an external client already configured

Thanks for the MR!
I have published a new version with your changes, including an update of the dependencies.
Unfortunately I am not spending too much time on AWS these days so also this project gets a little less attention than it deserves.


Incorrect TODO parsing with multiple todo sets in one file

Often it may make sense to have multiple sets of todo keywords in a file, but orga handles this incorrectly, with only the last parsed set of TODO keywords taking affect
Example from the org mode docs ( https://orgmode.org/manual/Per_002dfile-keywords.html )
#+TODO: TODO | DONE
#+TODO: REPORT BUG KNOWNCAUSE | FIXED
#+TODO: | CANCELED

Given how orga's updateTODOs function works, the previous TODOs are simply replaced with the newer ones. Instead, they should be collected then, if none are found before parsing headlines, it should default to ["TODO", "DONE"]

I do think there's a more essential problem here though that needs to be addressed, actually, in that orga needs to take two passes so that it can handle in-buffer settings like with todo keywords. While it's reasonable to assume they'll be at the top of most files, that can't be assumed to be universally true since it isn't enforced in org mode

This is fixed in v1.5.3. It can be separated from #28. Fell free to reopen, or create another one if any issues.


Only use JxlTest when JXL_IS_AVAILABLE is defined

Summary:
Jxl tests should only run if Jpeg-XL support is enabled.
This fixes the Github build of vrs.
Differential Revision: D43127711

@georges-berenger If I understand the situation correctly, it looks like I need a maintainer's approval to run Github CI "Build and Test" on this PR

approved. Should work for you from now on. Apparently, we need to approve a new contributor, hopefully only once.

@georges-berenger, CI failed last time and it looks like I may need approval to run CI on my updated PR :(


Can't publish

Hi,
i have install your plugin on my SBT plugin project, but the command sbt publish continue to try to publish on SonaType. Is configuration steps are missing from your README ?

I was able to publish,

set my ~/.bintray/.credentials correctly with API Key as password.

Add this project sbt-bintray as instructed to my sbt project.

in my build.sbt

bintrayPackage := "sbt-osgi-felix-p"

bintrayRepository := "sbt-osgi-felix-p"

bintrayOrganization := Some("philandrew") // The organization is not the same as the username I logged into bintray with

publishMavenStyle := true // true or false, it still published

licenses += ("MIT", url("http://opensource.org/licenses/MIT"))

bintrayReleaseOnPublish in ThisBuild := false // true or false, it still published

I can tell you that worked for me.

I'm also somewhat stuck releasing and was not able to upgrade my other plugins to this one...
My build:
sbtPlugin := true
publishTo := Some(Classpaths.sbtPluginReleases)
publishMavenStyle := false

// bintray config
bintrayOrganization := Some("ktosopl")
bintrayRepository := "sbt-plugins"
bintrayPackage := "sbt-multi-release-jar"

I have write access to the organisation and have created the specific package as well.. so this should work fine.
It fails in a very weird way with a 404 on publishing:
sbt:sbt-multi-release-jar> publish
[info] Packaging /Users/ktoso/code/sbt-multi-release-jar/target/scala-2.12/sbt-1.0/sbt-multi-release-jar-0.1.0.jar ...
[info] Done packaging.
[info] :: delivering :: com.lightbend.sbt#sbt-multi-release-jar;0.1.0 :: 0.1.0 :: release :: Tue Aug 29 20:54:57 JST 2017
[info] 	delivering ivy file to /Users/ktoso/code/sbt-multi-release-jar/target/scala-2.12/sbt-1.0/ivy-0.1.0.xml
[error] java.io.IOException: PUT operation to URL https://repo.scala-sbt.org/scalasbt/sbt-plugin-releases/com.lightbend.sbt/sbt-multi-release-jar/scala_2.12/sbt_1.0/0.1.0/jars/sbt-multi-release-jar.jar failed with status code 404: Not Found
[error] 	at org.apache.ivy.util.url.AbstractURLHandler.validatePutStatusCode(AbstractURLHandler.java:82)
[error] 	at sbt.internal.librarymanagement.ivyint.GigahorseUrlHandler.upload(GigahorseUrlHandler.scala:167)
[error] 	at org.apache.ivy.util.url.URLHandlerDispatcher.upload(URLHandlerDispatcher.java:82)
[error] 	at org.apache.ivy.util.FileUtil.copy(FileUtil.java:150)
[error] 	at org.apache.ivy.plugins.repository.url.URLRepository.put(URLRepository.java:84)
[error] 	at org.apache.ivy.plugins.repository.AbstractRepository.put(AbstractRepository.java:130)
[error] 	at sbt.internal.librarymanagement.ConvertResolver$ChecksumFriendlyURLResolver.put(ConvertResolver.scala:

I'm logged in and credential work...
sbt:sbt-multi-release-jar> bintrayEnsureCredentials
[success] Total time: 0 s, completed 29 Aug 2017, 20:56:42
sbt:sbt-multi-release-jar> bintrayWhoami
[info] ktosopl

Any idea what might be wrong here? The build I'm trying to fix is: https://github.com/sbt/sbt-multi-release-jar

The moment I posted this I realised the mistake:
Note in my above code I'm using the old publishTo style - that's bad, and once I removed that it published just fine.
sbtPlugin := true
//publishTo := Some(Classpaths.sbtPluginReleases) // THIS IS BAD IN THE CURRENT PLUGIN VERSION
publishMavenStyle := false

// bintray config
bintrayOrganization := Some("ktosopl")
bintrayRepository := "sbt-plugins"
bintrayPackage := "sbt-multi-release-jar"

Leaving this here in case it might help someone with a similar migration issue.
Happy hakking!

Cheers Konrad. As a stopgap we should add that caveat to the readme.

Several different issues were discussed here with the original issue lacking additional information. Therefore closing this.


build(deps): replace deprecated trove with trove4j

We had the ~19-year-old Trove and the ~12-year-old Trove4j on the CP. To avoid confusion and to keep the dependencies up to date, I replaced the former with the latter, because that is the continuation of that library.

To be verified by reviewers

[ ] Relevant public API members have been documented
[ ] Documentation related to this PR is complete

[ ] Boundary conditions are documented
[ ] Exceptions are documented
[ ] Nullability is documented if used

[ ] Touched existing code has been extended with documentation if missing
[ ] Code is readable
[ ] New features and fixed bugs are covered by tests

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


Replace verilog code in Readme with pre-formatted HTML to avoid breaking website

While we find a definitive fix for the issue where the collapsed code does not get formatted on the website, I've replaced the code block with the HTML that is already formatted.
Contributor Checklist

[ ] Did you add Scaladoc to every public function/method?
[ ] Did you add at least one test demonstrating the PR?
[ ] Did you delete any extraneous printlns/debugging code?
[x] Did you specify the type of improvement?
[ ] Did you add appropriate documentation in docs/src?
[ ] Did you state the API impact?
[ ] Did you specify the code generation impact?
[ ] Did you request a desired merge strategy?
[ ] Did you add text to be included in the Release Notes for this change?

Type of Improvement

documentation

API Impact
None

Backend Code Generation Impact
None

Desired Merge Strategy

Squash: The PR will be squashed and merged (choose this if you have no preference.

Release Notes

Reviewer Checklist (only modified by reviewer)

[ ] Did you add the appropriate labels?
[x] Did you mark the proper milestone (Bug fix: 3.4.x, [small] API extension: 3.5.x, API modification or big change: 3.6.0)?
[x] Did you review?
[ ] Did you check whether all relevant Contributor checkboxes have been checked?
[ ] Did you do one of the following when ready to merge:

[ ] Squash: You/ the contributor Enable auto-merge (squash), clean up the commit message, and label with Please Merge.
[ ] Merge: Ensure that contributor has cleaned up their commit history, then merge with Create a merge commit.

Kinda hack with the same "Markdown all in one" extension from VSCode... there is a command to "Print Markdown to HTML" that generated a Readme.html. I then copied the code part only to the Readme.md file :)


Unable to customize sun.png

When I add a sun.png, I get the error Duplicate file.
\app\build\intermediates\res\debug\drawable-xxhdpi\sun.png: Original is here. The version qualifier may be implied.
I assume, I would need to set the merger to use my project's sun.png, but not sure how to do it.

@gouravd Do you change it inside the library? Have you cleaned project before building it?


unexpected behavior in Dataset in bm/migrate-to-torch

@BenjaminMidtvedt:
I was expecting this code:
train_dataset = dt.pytorch.Dataset(pipeline, inputs=source, length=1000, replace=0.2)
train_loader = DataLoader(train_dataset, batch_size=32, shuffle=True)
where source is a path to an image folder,  to use 1000 images per epoch and replace them with replace probability. However, it seems to perform the training using all the images in the source for each epoch.

Ah, interesting use-case. I will think about if this can be implemented. Main difficulty is that I don't think dataloader notifies the dataset when a new epoch starts (unlike tensorflow).

I see... but still, it should only use length images, no?

My idea was that length was used to determine the number of images if not using sources. I can propose something in a bit, see if it suits your needs

In that case, let’s leave it as is. There are alternative ways to control lenght when using source.


Voice is sending to STT without waking word

Hi,
I started using this satellite on my raspberry pi, with the wake word component and i figured out that google charged me like i used 24 hours of STT.
The STT addon is not the problem because I used it before and i didn't have this issue.
What can be the problem?
https://github.com/chatziko/ha-google-cloud-stt/issues/8

Are you using the local wakeword on the satellite? You must use it to avoid hitting Home Assistant server with the request.
Can you post your debug log from the satellite?
Here's a typical output when using the local wake word:
Jan 12 10:46:17 nabu1 run[8263]: INFO:root:Waiting for wake word
Jan 12 10:46:32 nabu1 run[8263]: DEBUG:root:Streaming audio

Note it stays on Waiting for wake word and logs Streaming audio only after it was detected locally.
At that point you will stream to HA (and Google in your case).

Are you using the local wakeword on the satellite? You must use it to avoid hitting Home Assistant server with the request.
Can you post your debug log from the satellite?
Here's a typical output when using the local wake word:
Jan 12 10:46:17 nabu1 run[8263]: INFO:root:Waiting for wake word
Jan 12 10:46:32 nabu1 run[8263]: DEBUG:root:Streaming audio

Note it stays on Waiting for wake word and logs Streaming audio only after it was detected locally.
At that point you will stream to HA (and Google in your case).

I used the guide form this repository https://github.com/rhasspy/wyoming-satellite/blob/master/docs/tutorial_2mic.md
The local waking word was on, i checked it in the service log

Can you confirm you have modified your service definition and have these two parameters there?
ExecStart=/home/pi/wyoming-satellite/script/run ... --wake-uri 'tcp://<IP_ADDRESS>:10400' --wake-word-name 'ok_nabu'

Can you confirm you have modified your service definition and have these two parameters there?
ExecStart=/home/pi/wyoming-satellite/script/run ... --wake-uri 'tcp://<IP_ADDRESS>:10400' --wake-word-name 'ok_nabu'
You must also see this line in your log when debug is enabled: Jan 12 10:46:16 nabu1 run[8263]: DEBUG:root:Connecting to wake service: tcp://<IP_ADDRESS>:10400

this is the config line:
ExecStart=/home/liran/wyoming-satellite/script/run --debug --name 'my satellite' --uri 'tcp://<IP_ADDRESS>:10700' --mic-command 'arecord -D plughw:CARD=Audio,DEV=0 -r 16000 -c 1 -f S16_LE -t raw' --snd-command 'aplay -D iec958:CARD=Audio,DEV=0 -r 22050 -c 1 -f S16_LE -t raw' --wake-uri 'tcp://<IP_ADDRESS>:10400' --wake-word-name 'alexa'
i can see a lot of this WARNINGs:
Jan 11 07:56:41 raspberrypiHA run[885]: WARNING:root:Event(type='error', data={'text': 'speech-to-text failed', 'code': 'stt-stream-failed'}, payload=None)
Jan 11 07:56:44 raspberrypiHA run[885]: WARNING:root:Event(type='error', data={'text': 'speech-to-text failed', 'code': 'stt-stream-failed'}, payload=None)
Jan 11 07:56:45 raspberrypiHA run[885]: WARNING:root:Event(type='error', data={'text': 'speech-to-text failed', 'code': 'stt-stream-failed'}, payload=None)

I don’t see any way this can happen other than missconfiguration (not using the local wake word). Can you confirm the issue still persists even after manually starting wake word before the satellite and confirming the right messages in the log?

The warning message is coming from the server probably because you blocked the STT from Google after the issue. Either way this message shall not occur if you are using the local wake word.

The warning message is coming from the server probably because you blocked the STT from Google after the issue. Either way this message shall not occur if you are using the local wake word.

this is my "Assist in progress" sensor in the HA satellite, i looks like that STT was ON for more then 12 hours.

this is API calles of the google cloud STT


Fix broken imports of downsample.max_pool_2d

The module theano.tensor.signal.downsample was removed in Theano, and downsample.max_pool_2d was moved to pool.pool_2d.
https://github.com/Theano/Theano/commit/1960ddab6cb681ab75f714f0d0215a0e725c9ef3
https://github.com/Theano/Theano/commit/372939b1512eadf32bfe3c3aa38b3e4faf9dd792

Thanks. I'm merging at it is good. travis failure are not related. Travis config for pylearn2 is broken.
Note, pylearn2 isn't supported anymore.


[PDI-17113]-CSV input step with UTF-8 encoding still reads BOM as data

-fixed

Build Completed
:x: This pull request has errors. They will need to be addressed before it can be accepted. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands
mvn -B -fn -f 'pom.xml' -pl 'engine' -P '!assemblies' -Dsurefire.runOrder=alphabetical -Daudit -amd clean install

Cleanup Commands
mvn -B -f 'pom.xml' -pl 'engine' -P '!assemblies' -amd build-helper:remove-project-artifact

Changed files
  engine/src/main/java/org/pentaho/di/trans/steps/csvinput/CsvInput.java
  engine/src/main/java/org/pentaho/di/trans/steps/fileinput/text/BOMDetector.java
  engine/src/test/java/org/pentaho/di/trans/steps/csvinput/CsvInputUnicodeTest.java

Unit Test Coverage
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.

:warning: Coverage Changes (click to expand)
org.pentaho.di.job.entries.getpop.MailConnectionMeta

Branch Change: -1% :small_red_triangle_down:
Complexity Change: -1.5% :small_red_triangle_down:
Instruction Change: -0.3% :small_red_triangle_down:

org.pentaho.di.trans.steps.ldapoutput.LDAPOutputMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.replacestring.ReplaceStringMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.googleanalytics.GaInputStepMeta

Branch Change: -1.9% :small_red_triangle_down:
Complexity Change: -1.1% :small_red_triangle_down:

Checkstyle violations
The code submitted is not complying with one or more of our guidelines. To perform these checks locally, please use this tool.
/home/buildguy/project/engine/src/main/java/org/pentaho/di/trans/steps/csvinput/CsvInput.java

:heavy_exclamation_mark: Using the '.' form of import should be avoided - java.io.. at Line: 25

Build Completed
:fire: This pull request has some issues. It would be preferable to fix them in order for it to be just perfect. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands
mvn -B -fn -f 'pom.xml' -pl 'engine' -P '!assemblies' -Dsurefire.runOrder=alphabetical -Daudit -amd clean install

Cleanup Commands
mvn -B -f 'pom.xml' -pl 'engine' -P '!assemblies' -amd build-helper:remove-project-artifact

Changed files
  engine/src/main/java/org/pentaho/di/trans/steps/csvinput/CsvInput.java
  engine/src/main/java/org/pentaho/di/trans/steps/fileinput/text/BOMDetector.java
  engine/src/test/java/org/pentaho/di/trans/steps/csvinput/CsvInputUnicodeTest.java

Unit Test Coverage
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.

:warning: Coverage Changes (click to expand)
org.pentaho.di.job.entries.sql.JobEntrySQL

Instruction Change: -3.4% :small_red_triangle_down:
Line Change: -3.8% :small_red_triangle_down:

org.pentaho.di.trans.steps.csvinput.CsvInputMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.dimensionlookup.DimensionLookupMeta

Method Change: -1% :small_red_triangle_down:

org.pentaho.di.trans.steps.groupby.GroupByMeta

Branch Change: -2% :small_red_triangle_down:
Complexity Change: -2.1% :small_red_triangle_down:
Instruction Change: -0.2% :small_red_triangle_down:
Line Change: -0.7% :small_red_triangle_down:

org.pentaho.di.trans.steps.replacestring.ReplaceStringMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.textfileinput.TextFileInputMeta

Branch Change: -0.5% :small_red_triangle_down:

org.pentaho.di.trans.steps.uniquerows.UniqueRowsMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.googleanalytics.GaInputStepMeta

Branch Change: -1.9% :small_red_triangle_down:
Complexity Change: -1.1% :small_red_triangle_down:
Instruction Change: -0.2% :small_red_triangle_down:
Line Change: -0.3% :small_red_triangle_down:

org.pentaho.di.trans.steps.salesforceupsert.SalesforceUpsertMeta

Instruction Change: -0.1% :small_red_triangle_down:

@bmorrise please review the changes


‘fetch error' will be prompted when 'name' is used as the field name in the model and the model is referenced in consumers

To Reproduce
##model##
class User:
name = doc.String
password = doc.String
##user_blueprint##
@blueprint.put('/login')
@doc.consumes(models.User, location='body', content_type='application/json')
Environment (please complete the following information):

OS: Windows
Version :0.6.1

Hi there,
It is work on my laptop.

Verified with this code snippet:
from sanic import Sanic
from sanic.response import json
from sanic_openapi import swagger_blueprint, doc

app = Sanic()
app.blueprint(swagger_blueprint)

class User:
    name = doc.String
    password = doc.String

@app.route("/")
@doc.consumes(User, location="body", content_type="application/json")
async def test(request):
    return json({"hello": "world"})

if __name__ == "__main__":
    app.run(debug=True)

I remember I met the same issue in old version but I think it is already fix.
You can check related source code:https://github.com/huge-success/sanic-openapi/blob/c7b96bf0df7112689119f8dded49a39901b06134/sanic_openapi/doc.py#L130

Thank you very much for your answer
But I ran into some problems after updating to 0.6.1
I tried the sample you provided and found the same mistake
I think there's something wrong with my environment,
but I can't solve it
Can you help me with this problem
Thank you in advance!
This is my environment.yml
environment.zip

@chenjr0719 Is this also a windows/ujson bug like in #155?

I think this issue is related to windows/ujson issue. And I just confirm there is another issue when using the new version of ujson in #168.


Fixed Central Kurdish (Sorani) translations of date-related strings.

See logs.

buildbot, test on selenium.


Play campaign maps with bots but have some problems

Some maps don't allow you spawn weapon through spawn menu or commands and bots keep trying spawning weapons, also they don't know how to press +use key.
Could you add a feature that make you be able to give orders to bots, give them formations while following you, tell them to stop, pick up a weapon, move there, press something (through +use key)etc.

Hello @Gvbavx, I have been planning to do this for a while. After finishing the most recent update #30 I wanted to experiment with this bot base for a bit with other gamemodes. I have more confidence now that I will be able to properly implement this properly and efficiently.

To stop the bot from trying to spawn in weapons use this console command TBotSpawnWithPreferredWeapons.
To make the bot not attempt to spawn with its weapons enter the following into your console: TBotSpawnWithPreferredWeapons  0
To allow the bot to spawn in weapons again enter the following into your console: TBotSpawnWithPreferredWeapons  1

The bots do know how to press their +use key, they only use it to open doors currently, but in this next update, I allow you to command bots to press their use key on other entities. I will also add some of the commands you suggested here.

Two new commands I suggest Teleport:Teleport the bots to the owner's location or the positon where the owner is aiming at because they usually get stuck Attack:Bots attack the target selected by its owner because they can't tell if a Nextbot is hostile or friendly.

Definitely going to add the Teleport command, but I will change its name to Warp because it sounds better. Example: Bot warp instead of Bot teleport
It shouldn't be too hard to implement an attack command. I mean the TBotAttackNextBots makes the bots hostile to all NextBots, but this would probably be better in some cases.
I noticed you edited your message about the scan area command. It might not be a bad idea for me to add a console command or ConVar to make the bots always look around their surroundings for potential threats.

Ok, then you can add the scan area command if you want to.

Got a decent implementation right now. After some testing and one opening of a pull request and we should be good to go.


Add failing test for #16774

This PR is not a fix, just the failing test for #16774

@bot-gradle test ACC

OK, I've already triggered AllConfigCacheTestsReadyForMerge build for you.

@bot-gradle test and merge

Your PR is queued. See the queue page for details.

OK, I've already triggered a build for you.


Activate re-add button only if active speaker is true

closes #3352

@Elblinator see https://github.com/OpenSlides/openslides-backend/issues/2262 respective https://github.com/OpenSlides/openslides-backend/pull/2263


Update fedora-with-test-tooling image to the latest.

What this PR does
Before this PR:
The old fedora-test-tooling image is having netcat command not found issue for s390x, this issue is fixed and rebuit the fedora-test-tooling image to reflect the changes. This is the pr that has updated the fedora-test-tooling image
https://github.com/kubevirt/kubevirtci/pull/1268
After this PR:
This pr updates the fedora-test-tooling image with latest hash.

Fixes #
Why we need it and why it was done in this way
The following tradeoffs were made:
The following alternatives were considered:
Links to places where the discussion took place:
Special notes for your reviewer

Checklist
This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.

[ ] Design: A design document was considered and is present (link) or not required
[ ] PR: The PR description is expressive enough and will help future contributors
[ ] Code: Write code that humans can understand and Keep it simple
[ ] Refactor: You have left the code cleaner than you found it (Boy Scout Rule)
[ ] Upgrade: Impact of this change on upgrade flows was considered and addressed if required
[ ] Testing: New code requires new unit tests. New features and bug fixes require at least on e2e test
[ ] Documentation: A user-guide update was considered and is present (link) or not required. You want a user-guide update if it's a user facing feature / API change.
[ ] Community: Announcement to kubevirt-dev was considered

Release note

NONE

/cc @brianmcarey

/release-note-edit  update fedora-test-tooling to latest

/release-note-none

/approve


eksa-admin node should include unattended-upgrades

The EKS-A Admin node is running Ubuntu 20.04. We should ensure the latest updates are installed and continue to be installed through use of the unattended-upgrades package.

Adding the following to the cloud-init should do it.
- sed 's,//      "${distro_id}:${distro_codename}-updates";,        "${distro_id}:${distro_codename}-updates";,' /etc/apt/apt.conf.d/50unattended-upgrades
- sed 's,//Unattended-Upgrade::Automatic-Reboot "false";,Unattended-Upgrade::Automatic-Reboot "true";,' /etc/apt/apt.conf.d/50unattended-upgrades

We'll also want to ensure (somehow) that the node isn't rebooted while the cluster is coming up for the first time.
Maybe we can disable it at install and at schedule the enablement for a few hours later.

Options:

disable autoreboot
Set reboot time to 2AM
Do your at scheme.
Calculate the autoreboot time to be 2 hours (or some other offset) from current time.

Looks like the upfront upgrade (package_upgrade: true) may be a bad idea. Adds 15 minutes plus to the initial deployment.


[cli] generate entity for SYSTEM VERSIONED tables on MariaDB

PR Info

Closes https://github.com/SeaQL/sea-orm/issues/848

Dependencies:

https://github.com/SeaQL/sea-schema/pull/76

Adds

[x] Generate entity file for MariaDB's SYSTEM VERSIONED tables

https://github.com/SeaQL/sea-schema/releases/tag/0.9.3


[Insets] Missing WindowInsets.navigationBarsWithIme

Modifier.navigationBarsWithImePadding() is extremely helpful, but there does not appear to exist any equivalent for WindowInsets.
To get correct content padding for my LazyColumn I had to do this to work around it:
    val imeInsets = LocalWindowInsets.current.ime
    val navigationBarsInsets = LocalWindowInsets.current.navigationBars
    val insets = if (imeInsets.isVisible) {
        imeInsets
    } else navigationBarsInsets
    LazyColumn(contentPadding = insets.toPaddingValues()) {
        // Content
    }

Or, for a reusable version:
val WindowInsets.navigationBarsWithIme: Insets
    get() = if (ime.isVisible) ime else navigationBars

If you look at how navigationBarsWithImePadding(), it's actually just:
val navigationBarsWithIme = LocalWindowInsets.current.let {
    it.ime.coerceEachDimensionAtLeast(it.navigationBars)
}

coerceEachDimensionAtLeast() is currently an internal function, but we could make it public.

That would make it easier, yeah. I just thought since navigationBarsWithImePadding exists as a modifier, adding an equivalent on LocalWindowInsets.current would make it consistent, but I might be misunderstanding things here :)
Adding own extension property is easy enough.

The modifiers are different as it's difficult to compose custom logic in them (although still possible). They are also designed to cover common use-cases.
Reading LocalWindowInsets is definitely in the 'doing it manually' territory so I think the linked PR is fine. Similarly, I don't want to start creating combinations of insets in WindowInsets as it will lead to a combinational explosion.


feat: Improves Azure SPN setup docs

Updates it to the latest links from Azure and the latest API requirements.
Adds more information/insight about EA account setup.
CU-kd6xvb
Felix please read through it if you think something is misleading/incomplete. I tried to not directly describe every step but rather point to the respective Azure docs and only fill in the info misleading in Azure documentation, so in case they update something we are not having older information in our documentation. Or do you think this is a bad idea and should it rather be completly described by our own docs?

Task linked: CU-kd6xvb Azure Integr. Docs not suitable for EA Account Setup

In general, I think pointing to the Azure docs and explaining why we need them is fine.
But I am missing references to specific API versions outside of the REST API URIs you mention. If I understood it correctly, we need to give permissions via specific versions of some APIs. Are the specific versions only important for those APIs for which we specify the URIs? And what about the difference between legacy and new? I mean maybe we should only list the new version, once we are confident it works.

But I am missing references to specific API versions outside of the REST API URIs you mention. If I understood it correctly, we need to give permissions via specific versions of some APIs. Are the specific versions only important for those APIs for which we specify the URIs? And what about the difference between legacy and new? I mean maybe we should only list the new version, once we are confident it works.

As far as I know Azure only mentioned the API difference for EA Account role assignment (the versions used to create an actual subscription and the role assignment obviously don't match, but I just used the version they mentioned). I try to make this a bit clearer.
I wanted to avoid describing the legacy way as this should not really be used anymore. So every new customer can just be onboarded via the new way. We btw need to change this for the existing customers as well!


Closing the context menu by clicking

Right now there is no
 element in this library at all and the left mouse button clicks on the elements that are in the background. I need the mouse click to be stopped with a
 element and event.stopPropagation(). After that the context menu and
 should be closed.
We can move this function to MenuOptions.

Thank you for your question, In version 1.3.0 add clickCloseClassName and clickCloseClassName for ignore clicking of some element. You can set clickCloseClassName property in MenuOptions, If your element in menu item has this className, click it will ignore event and close hole menu.

Here's what worked for me so far:
export function showContextMenu(e: MouseEvent, items: MenuItem[] | undefined) {
  const contextMenuInstance = Vue3ContextMenu.showContextMenu({
    x: e.x,
    y: e.y,
    theme: darkColorScheme.value ? "mac dark" : "mac",
    items,
    closeWhenScroll: true,
    clickCloseClassName: 'mx-context-no-clickable', // it's not working
  });
  // it's working
  nextTick(() => {
    const el = document.getElementById( 'mx-menu-default-container')!;
    el.style.pointerEvents = 'all';
    el.addEventListener('click', (e) => {
      e.stopPropagation();
      contextMenuInstance.closeMenu();
      el.style.pointerEvents = 'none';
    });
  });
  return contextMenuInstance;
}


I’m unable to build a project using Vue3+Vite.

After deploying the project, I encountered the following problems:
I received a warning about circular references. I temporarily resolved this issue by setting the manualChunks property in vite.config.js.
I tested all the code in the project and found that as long as CornerstoneTools is referenced, this error will occur, but it works normally in the development environment.
Next, when I built the production environment code and enabled the property of not compressing the code, I got the error: Cannot access 'elementCursor' before initialization. To ensure the error is reproducible, I re-added a Vue3 project and only imported CornerstoneTools, and the error was consistent. How should I solve this problem?

I have the same issue with vite/react, how did you solve it?


NIFI-2199 & NIFI-3112 - Handle propagation of stderr and allow ssh restart

NIFI-2199
NIFI-3112
Pipe stdout to /dev/null and allow stderr to propagate through.
This correction does not make NiFi fully LSB spec compliant but does solve the two issues presented in the listed tickets.  This will allow stderr to propagate through and restart through SSH.
ssh can be tested by issuing a
ssh user@remote-host <path to nifi>/bin/nifi.sh restart
from a local machine to a remote host
3112 can be verified by changing a property to bootstrap causing it to be invalid and running the above.  As listed in the prior discussion of 3112, making graceful.shutdown.seconds a negative number such as below:

graceful.shutdown.seconds=-20

Will cause an error to be triggered and the appropriate contents transmitted.

Thank you Aldrin, as a part of NIFI-2199 I was thinking about the solution of changing the RunNifi java app to close the relevant streams. Would be cleaner and as I already introduced problems with stream redirection using bash, i would go for changing the Java part.

I tried this out, and it does appear to work when I run ssh user@remote-host "sudo service nifi restart".  However, when I do the same with a salt command, it still hangs:
salt nifi cmd.run "sudo service nifi restart"
I believe salt uses the python "subprocess" call to invoke a command this way.  Since this was working in 1.1.x, I feel like there should be a way to get it working again in 1.2.x.

Hey @gresockj,
Don't have a lot of familiarity with python or Salt.  Would you happen to have a sample salt script you would be able to share?  I have a couple ideas on how to work with RunNiFi to make this happen.

Salt is easy to set up with this walkthrough.  You can run salt-master and salt-minion on the same nifi box if you want in order to reproduce this behavior.  Once you have it installed, you can run the command:
salt 'minionID' cmd.run "service nifi start"

thanks, will see what I can find

@apiri I'd be happy to help dig into the salt use case if you would like

@kevdoran Sounds good!  I propose we incorporate this PR for the time being to solve the prior two cases listed in the mentioned JIRAs and can open up a new JIRA to track issues with Salt and presumably other tools/scripts that may be Python driven.  @gresockj let me know your thoughts.  I will create a separate issue to track the Python side of the house.

Created https://issues.apache.org/jira/browse/NIFI-3899

@apiri sounds good

@apiri will review

@apiri validated ssh command on remote host with with start/stop/restart.  All worked as expected, with NiFi starting appropriately and the IO stream for ssh was closed.  Also validated that bootstrap errors are appropriately routed to the output stream and displayed before stream is closed.
+1
will merge shortly. Thanks Aldrin!


Allow Window Installer Without Admin

Is your feature request related to a problem? Please describe.
My problem is I want to install don't need admin, it is similar with Visual Studio Code .

Describe the solution you'd like
Can continue to install no need admin confirm
Describe alternatives you've considered

Allow option install for all user or separate user.

Additional context
Add any other context or screenshots about the feature request here.

Duplicate of #498