Deprecate this extension in favor of vscode-rust

@saviorisdead since the project seems abandoned, it would be beneficial to the community to officially deprecate this extension and point towards vscode-rust instead. A lot of people still install RustyCode since it has a higher version number and higher download count, but vscode-rust is the only one that is actively maintained.

A lot of people still install RustyCode since it has a higher version number

That's the author of vscode-rust own fault though. The project was forked from RustyCode, so it should have just kept the current versioning going instead of resetting the count.

but vscode-rust is the only one that is actively maintained.

An acknowledgement from the upstream developer would be nice.

i think not for while. Threre are feature that this extension is not supporting like the outline.

https://github.com/editor-rs/vscode-rust


Function for isoinfo-like data

Is there a way to use this library to get data similar to what is given by isoinfo -lR -i test.iso?
Sample output:
Directory listing of /
dr-xr-xr-x   5    0    0            2048 Oct  9 2020 [     29 02]  .
dr-xr-xr-x   5    0    0            2048 Oct  9 2020 [     29 02]  ..
dr-xr-xr-x   3    0    0            2048 Oct  9 2020 [     33 02]  EFI
dr-xr-xr-x   3    0    0            2048 Oct  9 2020 [     30 02]  images
dr-xr-xr-x   2    0    0            2048 Oct  9 2020 [     32 02]  isolinux
-r--r--r--   1    0    0             132 Oct  9 2020 [   4053 00]  zipl.prm
...
Directory listing of /images/pxeboot/
dr-xr-xr-x   2    0    0            2048 Oct  9 2020 [     31 02]  .
dr-xr-xr-x   3    0    0            2048 Oct  9 2020 [     30 02]  ..
-r--r--r--   1    0    0        80239428 Oct  9 2020 [   4182 00]  initrd.img
-r--r--r--   1    0    0       819969024 Oct  9 2020 [  43362 00]  rootfs.img
-r--r--r--   1    0    0         8924528 Oct  9 2020 [ 443738 00]  vmlinuz

Specifically I'm looking to get the file size and offset without first unpacking the image.

The data is there. What is missing from your ability to do it? The filesystem read example does a ReadDir which returns an os.FileInfo for each file. Is that not sufficient?

I'm specifically looking for the file's offset into the iso which isn't present in the file info.

More a property of the file as a part of the iso rather than the file if I were to extract it, if that makes sense.

Ah, I see.
That wouldn't be in the usual file/dir-level API, you would need something lower.
Part of it is there, you can look at how GetFilesystem is implemented, which really just calls iso9660.Read, which returns a iso96600.Filesystem, which, in turn, gives you the same ReadDir you saw above.
So getting an actual iso9660.FileSystem structure can be done either by GetFilesystem and than casting, or by calling the iso9660.Read directly.
The missing part is getting information about each file's on-disk location. Fortunately, the routines that walk the tree, primarily readDirectory already return a directoryEntry, which has that data. We just copy only the essentials over to []os.FileInfo before returning it.
So you could open a PR to create another func just on iso9660.FileSystem, say ReadDirDetails or similar, that returns iso9660.FileInfo. Then you are good to go.

Turns out all I needed for this was to expose the directory entry location info.
I just added a method on iso9660.File for that in https://github.com/diskfs/go-diskfs/pull/94


Added Binary Uuid generator

Your mysql storage will thank you for that. If you already have fragmented indexes, then at least make them only taking half the storage by using a binary type.
This is a predicate PR to enable an optimized DBAL event store here https://github.com/qandidate-labs/broadway

Should we actually fix this where we store it?

@asm89 Well, I would not call that a "fix". But you are right, it should be done on the EventStore level. I will close this now and create a PR on the https://github.com/qandidate-labs/broadway project


Vector3.Reflect and Bounce do not reflect/bounce from a normalized vector

Godot version
4.1 .Net
System information
Win10 x64 22H2
Issue description
I have a Vector3 called originPos that I want to bounce/reflect about another vector called endNormal.
Documentation says the axis must be normalized.
My code is originPos.Bounce(endNormal.Normalized()); and originPos.Reflect(endNormal.Normalized());
I get an error saying Argument is not normalized. (Parameter 'normal') even though the normal vector is normalized. Manually normalizing the vector by dividing it by the vector length/magnitude does not resolve.
However, changing the normal vector to one of the standard unit vectors like Vector3.Up works fine.
Steps to reproduce
Described in issue.
Minimal reproduction project
N/A

Related: https://github.com/godotengine/godot/issues/83922 these are most likely the same issue

Solved in https://github.com/godotengine/godot/issues/83922
It was user error, sorry!


vgg nets

VGG example using nn interface.

given that there is already a resnet, i don't think an additional vgg will help too much. instead, i suggest to put vgg and others in a model package, so users can get it through from foo.model import vgg

@mli will update following similar structure in image-classification. This was added because the fast-neural-style transfer example depended on VGG.

Moved model/vision.py back to example as vision_model.py for now. Also fixed lint along the way. Let me do more testing before merging.

closing now to update to the new interface. will resend


fix the scroll up icon and redesign it.

Description
scroll up icon doesn't show and not in well designed condition.
Steps to Reproduce
wants to fix it and make it better looking
Expected Behavior
No response
Actual Behavior
No response
Screenshots
No response
Additional Information
No response
What browser are you seeing the problem on?

[X] Firefox
[X] Chrome
[ ] Safari
[ ] Microsoft Edge

Checklist

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[X] I want to work on this issue. (optional)

this issue has been solved, so we are closing this issue.


problem with ospInit ospShutdown cycling

In ParaView 5.7.rc1 (w/ ospray 1.8.x), but only on mac, I run into problems when we shutdown and restart ospray.
Unfortunately I have not yet been able to reproduce this with a simple test program and ospinit/ospshutdown cycles work fine with the same libraries and compiler on a failing machine.
The crashes I am seeing occur where the objectFactory's internal cache of creationFunctionPointers contains a stale function pointer into in a previously freed library (ospray_module_ispc) instead of the newly reloaded version of the same library.
If I prevent the cache hit in objectFactory, we find and use the new creation function pointer in the new library fine.
If I call ospShutdown but disable library closure it also seems to work fine.
If I avoid calling ospShutdown entirely (which previous ParaViews used to do) things work fine too.
I am thinking that a clean solution would be to make ~library remove its entries in the objectFactory cache but don't see a good way to make that happen yet.

We cover ospInit ospShutdown cycling in tests and also fixed some problems. One known exception is the MPI device where multiple init/shutdown cycles won't be supported.


RFC for transitional into

Rendered

Today, this does not work in normal Rust because given this code:
impl<A, B, C> Into<C> for A
    where A: Into<B>, B: Into<C> {
    fn into(self) -> C {
        self.into().into()
    }
}

It fails with "B is unconstrained"

Is the proposal that this should be a blanket impl? Something like
impl <A, B, C> From<A> for C
where B: From<A>, C: From<A>
{
  fn from(a :A) -> C { from(from(a)) }
}

Does anyone know if there are weird coherence issues here?

@mark-i-m there can be multiple choices of B.

Also note that From implementation could be lossy and therefore different choices of B could lead to different results.
use std::collections::BinaryHeap;
fn main() {
    let a = vec![4, 12, 8];
    let b = BinaryHeap::from(a);
    let c = Vec::from(b);
    assert_eq!(c, vec![12, 4, 8]);
}

I think that this RFC is just not possible to implement, unfortunately.
As you’ve already found out, the compiler rejects such impls:
error[E0207]: the type parameter `B` is not constrained by the impl trait, self type, or predicates
   --> libcore/convert.rs:455:9
    |
455 | impl<A, B, C> From<A> for C
    |         ^ unconstrained type parameter

error: aborting due to previous error

But even if we were to change the language rules to accept an unconstrained type parameter and force the compiler to do an exhaustive search when trying to determine if this impl is applicable to a given call (which would have compiler performance implications), then we’d only hit the impl coherence rule that would make the trait very impractical at best: this new impl would likely conflict with existing impls. It might even conflict with itself, is multiple choices of B would satisfy the bounds.

I do agree with the fact that this is nearly impossible to implement, however I'm just throwing the idea out there.

The RFC process is more oriented to things that are possible to implement. A thread on internals.rust-lang.org might be better for something more speculative like this.

Taking into consideration the issues brought up here, it seems the RFC is impossible to implement. I will be closing this PR.

I think many people are experiencing a similar problem, so an internals thread might be a good starting point for discussion :)

I think many people are experiencing a similar problem, so an internals thread might be a good starting point for discussion :)


Web cors

Hello, I am trying to use your api on a flutter web app and I am getting CORS errors. I am not expert in CORS but I believe I cannot do anything about it on my side. Do you know if this is a problem with the way the Jisho API handles CORS?

Hello!
I don't know for sure about the inner workings of your web app, but I believe that the Jisho CORS setup blocks you from pulling websites using javascript within a browser. As far as I know, there is no workaround for this, because the browser is in control of setting the Origin of the HTTP request. You're gonna have to set up a backend responsible for using the API and forwarding the data to the user in order to make this work.

Ok that seems reasonable! Thanks for the reply.


Add REQUIRES: asserts to a test that I missed.

@swift-ci smoke test

@rintaro I think it's safe to force merge this if you'd like


Won't Connect to PSMove Service.

I had everything working earlier today, only to find out that I wasn't using the SteamVR version, so I deleted everything, moved my PC into another room, installed the SteamVR version, and now it says connecting to PSMove service, and never continues. In the command prompt window it says connected.

INFO [Renderer::init()] Initializing Renderer Context
[INFO] ClientNetworkManager::start_tcp_connect - Connecting to: <IP_ADDRESS>:9512...
[INFO] ClientPSMoveAPI - Successfully initialized ClientPSMoveAPI
[INFO] ClientNetworkManager::handle_tcp_connect - Connected to <IP_ADDRESS>:9512

I got it to go through twice but when i went to pair controllers it would get stuck as well.
I am using 3 Eye cameras, 2 move controllers, and an Oculus Rift Development Kit 2.
Many thanks, Safety

I have found the fix for this. You must disconnect from Wifi/Ethernrt can restart the program. I hope this is helpful.


haskell-src-exts support in codeworld-compiler

This PR adds haskell-src-exts support in codeworld-compiler to parse source code and look for errors from the generated tree.

Please have a look and suggest changes and improvements that can be done.
Also, can we keep the commented code, or should I remove that?

I hope the error message in badMatches is correct.

I updated the error messages of all the test-cases in order to match with haskell-src-exts error messages and also fix #541.


Failure to install under setuptools 10.x

Hi,
I get the following error while installing nltk 3.0.0 under buildout and setuptools 10.x
File "build/bdist.macosx-10.10-x86_64/egg/setuptools/sandbox.py", line 205, in run_setup
File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/contextlib.py", line 35, in exit
self.gen.throw(type, value, traceback)
File "build/bdist.macosx-10.10-x86_64/egg/setuptools/sandbox.py", line 157, in setup_context
File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/contextlib.py", line 35, in exit
self.gen.throw(type, value, traceback)
File "build/bdist.macosx-10.10-x86_64/egg/setuptools/sandbox.py", line 128, in save_modules
File "build/bdist.macosx-10.10-x86_64/egg/setuptools/sandbox.py", line 106, in save_modules
File "build/bdist.macosx-10.10-x86_64/egg/setuptools/sandbox.py", line 157, in setup_context
File "build/bdist.macosx-10.10-x86_64/egg/setuptools/sandbox.py", line 201, in run_setup
File "build/bdist.macosx-10.10-x86_64/egg/setuptools/sandbox.py", line 232, in run
File "build/bdist.macosx-10.10-x86_64/egg/setuptools/sandbox.py", line 200, in runner
File "build/bdist.macosx-10.10-x86_64/egg/setuptools/sandbox.py", line 46, in _execfile
File "/var/folders/r5/2ftstrwn70s8h7c0s634fmw40000gn/T/easy_install-qPQPP1/nltk-3.0.0/setup.py", line 37, in
AttributeError: 'module' object has no attribute 'finders'
An error occurred when trying to install nltk 3.0.0. Look above this message for any errors that were output by easy_install.
While:
Installing eggs.
Getting distribution for 'nltk==3.0.0'.
Error: Couldn't install: nltk 3.0.0
Jason R. Coombs the coder of setuptools pointed out that the issue is because
"NLTK needs to update its monkey patching of setuptools. It can either protect the code it's already using from errors or instead monkey-patch sdist._default_revctrl to always return an empty list, which is compatible with all versions."
https://bitbucket.org/pypa/setuptools/issue/322/failure-installing-nltk-300-using
Thanks a lot
Carlos

same issue as nltk#824
Is there any time frame for a new 3.0.1 release?
Carlos

I'll try to get 3.0.1 out this week.


Warn to console when multiple .bind() calls overwrite

tl;dr -- megaPlot should log a warning to the console any time two successive calls to Selection.bind() overwrite each other in the scheduler before the former call to .bind() starts work.
Background
In LIT, I'm using multiple Selections to act as proxies for layers in the Scene. One of these Selections is always bound to the entire dataset, and the other Selections are bound to com subset of the dataset (not that it matters for this issue, but one Selection can contain [0, N] datums and the other 3 can contain [0, 1] datums). For the Selections containing subsets, I assumed that calling .bind() with an empty array would mark all existing datums (and their associated Sprites) for removal from the Scene, effectively clearing the Selection and allowing me to make a successive call to .bind() with the new contents that would render the data I now cared about in the Scene. Some example code below.
const data = [/* let's assume this is populated */];

const container = document.querySelector('some_query');
const scene = new Scene({container});
const allData = scene.createSelection();
const someData = scene.createSelection();

allData.bind(data);

function update(someSentinel) {
  someData.bind([]);
  const interestingData = data.filter(d => /* some predicate */);
  someData.bind(interestingData);
}

This assumption was incorrect because of how the Selection.bind() uniquely identifies binding tasks. Calls to .bind() are transformed into bindingTasks that are uniquely identified by the Selection on which .bind() is being called. In the example above, the successive calls to .bind() effectively overwrite each other in the scheduler because they process before the next animation frame happens.
Desired Solution
It would be useful if MegaPlot could console.warn() when two successive calls to .bind() overwrite each other in the scheduler if the existing .bind() call has not yet started doing work. This would have made the behavior described above much easier to identify and mitigate.

Implemented in #14


[Design] Refactor WriteAttributeTo to enable Razor to utilize value removal for TagHelpers.

Refactored 3 methods out of the existing WriteAttributeTo. The refactoring was based on removing the Begin/EndContext for instrumentation bits which isn't valid in a TagHelper attribute scenario.

aspnet/Razor#247
Razor PR: https://github.com/aspnet/Razor/pull/446

:watch:

After the new WriteAttribute changes need to re-work how this is done. Closing for now, will re-open fresh.


Vijayasree/refactor:home-new-show-component

Changes:

...

Type of change

[ ] Bug fix
[ ] New feature
[ ] Update feature
[x] Refactor code
[ ] Translation to code
[ ] Translation to crowdin
[ ] Script configuration
[ ] Improve performance
[ ] Style only
[ ] Dependency update
[ ] Documentation update
[ ] Release

This will conflict with the PR that will come in from Crowdin with the new home page though. @prince-deriv @vijayasree-deriv

Adding do not merge tag to the card linked to this PR, if the change is big we will rather create a new PR later.

This is no longer needed after the release of the new homepage 🙏


Add a Heroku Deploy Option

I am trying to deploy this app on heroku since 1 january 2020. But its not working , please suggest how to depoy this bot on vps because i can not run it on localhst.
this error got when deploying on heroku
2020-02-10T14:02:53.353094+00:00 app[web.1]: npm ERR<EMAIL_ADDRESS>start: `NTBA_FIX_319=1 node --max_old_space_size=128 ./out/index.js`
2020-02-10T14:02:53.353217+00:00 app[web.1]: npm ERR! Exit status 1
2020-02-10T14:02:53.353343+00:00 app[web.1]: npm ERR!
2020-02-10T14:02:53.353484+00:00 app[web.1]: npm ERR! Failed at the<EMAIL_ADDRESS>start script.
2020-02-10T14:02:53.353638+00:00 app[web.1]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
2020-02-10T14:02:53.360882+00:00 app[web.1]:
2020-02-10T14:02:53.361017+00:00 app[web.1]: npm ERR! A complete log of this run can be found in:
2020-02-10T14:02:53.361112+00:00 app[web.1]: npm ERR!     /app/.npm/_logs/2020-02-10T14_02_53_354Z-debug.log
2020-02-10T14:02:53.429745+00:00 heroku[web.1]: Process exited with status 1```
![Untitled](https://user-images.githubusercontent.com/60497650/74156616-b6fcf000-4c3c-11ea-88f7-937c492ba9a4.png)

I do not plan to provide support for Heroku. A bot like this is not something you should deploy on such a service, and it would break from time to time anyway.

Can You tell me where I can deploy your bot other than localhost.
On Tue 11 Feb, 2020, 8:42 AM Ritayan Chakraborty<EMAIL_ADDRESS>wrote:

I do not plan to provide support for Heroku. A bot like this is not
something you should deploy on such a service, and it would break from time
to time anyway.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/out386/aria-telegram-mirror-bot/issues/77?email_source=notifications&email_token=AONR54UO36DXWSET6V3FVD3RCIJRHA5CNFSM4KSOYIJ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOELLC3SQ#issuecomment-584461770,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AONR54T2Q2TLHFD7X3XSEP3RCIJRHANCNFSM4KSOYIJQ
.


Voting system allowing people to prioritize (Multiple points per user upvote)

Is your feature request related to a problem? Please describe.
Issue: Github "voting" system is binary: +1 or not.
We would like to let people express their own preferences. If I think this issue is more important to me than other ones, I would like to claim it.
We have tested the following system to sort the issues: each participant has 100 credits quarterly and he can put them on the issue(s) he wants to. He can put 100 credits on one issue or allocate it on several issues. The drawback of this method is that we need to do it by hand :(
Describe the solution you'd like
I don't know if it's possible to parse Github issues' comments, but we could use a system where people would vote with a simple syntax, something like: #My_credits_for_this_issue: 80 The parser might detect the hashtag and its corresponding amount, the user and the date of the comment. This way, it might be possible to establish a ranking based on people priorities. Do you think it's possible?
I understand that the drawback would be the multiplication of comments but it's already the case in many projects where people are adding "+1" in the comments.
Describe alternatives you've considered
Doing this by hand in a shared spreadsheet.
Additional context
No response

Is your feature request related to a problem? Please describe.
Issue: Github "voting" system is binary: +1 or not.
We would like to let people express their own preferences. If I think this issue is more important to me than other ones, I would like to claim it.
We have tested the following system to sort the issues: each participant has 100 credits quarterly and he can put them on the issue(s) he wants to. He can put 100 credits on one issue or allocate it on several issues. The drawback of this method is that we need to do it by hand :(
Describe the solution you'd like
I don't know if it's possible to parse Github issues' comments, but we could use a system where people would vote with a simple syntax, something like: #My_credits_for_this_issue: 80 The parser might detect the hashtag and its corresponding amount, the user and the date of the comment. This way, it might be possible to establish a ranking based on people priorities. Do you think it's possible?
I understand that the drawback would be the multiplication of comments but it's already the case in many projects where people are adding "+1" in the comments.
Describe alternatives you've considered
Doing this by hand in a shared spreadsheet.
Additional context
No response

Originally posted by @anuraghazra in https://github.com/anuraghazra/github-readme-stats/issues/2193

@CharlesNepote Thanks for your feature request. I thought of something similar, and I think what you are asking for is possible since the GraphQL API allows the following:

Check which users have upvoted a given issue in a given period (see https://docs.github.com/en/graphql/reference/enums#reactionorderfield and https://docs.github.com/en/graphql/reference/objects#reaction).
Parsing the issue comments for such a tag is also possible (see https://docs.github.com/en/graphql/reference/objects#issuecommentconnection).

Unfortunately, implementing such a system as a GitHub action would, I think, not be feasible with the current GraphQL API since this system would scale exponentially with the number of users and issues. This action would, therefore, quickly hit the GraphQL rate limits. A way to deal with this would be to run the action in multiple steps while keeping track of the GraphQL cost. Implementing this logic is complicated and would still be inefficient since old data is fetched on each run.
If I would implement this feature, in the form you suggested, I would likely not use a GitHub action but create a Github application. Doing this would allow me to run a cloud function whenever a user upvotes an issue or only periodically fetch new information. Storing this information in a server database would allow the logic to be run and coded on the server. This setup would allow for a nicer interface to show the most upvoted issues and allow users to assign more points to a given issue.
Nevertheless, I think implementing such an App would be a significant undertaking and only worth it if a lot of people/companies are interested in such an app and if there were no other alternatives. There are already (paid) feature voting apps for more advanced feature tracking use cases that can integrate with GitHub. To name a few:

https://sleekplan.com: I use this on my bigger projects.
https://www.shipright.co/product
https://www.upvoty.com/pricing
https://canny.io
https://usersnap.com/pricing

The reason I created https://github.com/rickstaa/top-issues-action was to have a free, easy to setup way to quickly see issues/feature requests/bugs/PR that were most upvoted. It was meant to be an extension of GitHub's own filtering abilities on the GitHub website.

@CharlesNepote Having that said, I might implement a GitHub app version if there is enough interest in this feature from the community. 🚀

Thanks a lot for your answer!

Unfortunately, implementing such a system as a GitHub action would, I think, not be feasible with the current GraphQL API since this system would scale exponentially with the number of users and issues.

Would it be possible to run it only once day or even once a week, to stay below the limits?

I suggest we switch to a GitHub App because a GitHub app can be triggered at every reaction that is added. This would allow us to store this information in a database, allowing us to create more complex top issues dashboards like the one you suggested.

Closing this as I currently do not have the time to implement a GitHub App version of this action.


Refresh page, client state are lost, navigation become disabled

Describe the bug

Version

Browser

[ ] Electron distribution
[x ] Chrome
[ ] Safari
[ ] Firefox
[ ] Edge

OS

[ x] macOS
[ ] Windows
[ ] Ubuntu

To Reproduce
Steps to reproduce the behavior:

Go to 'Bot Responses'
Click on browser 'Refresh page'
See left navigation become disabled

Expected behavior

Screenshots

Additional context

This was fixed with https://github.com/microsoft/BotFramework-Composer/pull/4316


WIP: refactor(docs): install ec-addon-docs & move demo app into sub route dir

closing due to inactivity


Add fixes, so we can enable back tests in TS

Summary
This PR includes the following changes:

Do not depend on fabric8 extensions directly

Please check the relevant options

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Dependency update
[x] Refactoring
[ ] Release (follows conventions described in the RELEASE.md)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] This change requires a documentation update
[x] This change requires execution against OCP (use run tests phrase in comment)

Checklist:

[ ] Example scenarios has been updated / added
[x] Methods and classes used in PR scenarios are meaningful
[x] Commits are well encapsulated and follow the best practices

run tests

@michalvavrik it seems so: https://github.com/quarkusio/quarkus/issues/43360 (see comments).
Case in point: when I enable this test and run it without this change, it hangs, but when I do the same with this change, the test works. You can try it for yourself.
Maybe the dependencies somehow leak to production scope.

@michalvavrik it seems so: quarkusio/quarkus#43360 (see comments).

Dependencies changes in https://github.com/quarkus-qe/quarkus-test-suite/pull/2059/files were not in the test scope. Build steps shouldn't be executed for these test dependencies because in native mode because we build production application, so Quarkus build shouldn't be in a test mode. If they are there, it is a mistake.

Case in point: when I enable this test and run it without this change, it hangs, but when I do the same with this change, the test works. You can try it for yourself.
Maybe the dependencies somehow leak to production scope.

If you are not in a hurry, I'd like to test it later this week. Also I am preparing https://github.com/quarkus-qe/quarkus-test-framework/pull/1375 that I'd like to reduce changes in that PR and finish this week. That alone should completely remove these test scope dependencies from the native build.
I don't think changes in this PR are wrong, I just want to understand them better. @mjurc please feel free to review & approve.

If you are not in a hurry, I'd like to test it later this week
I definitely not in a hurry. If you consider https://github.com/quarkus-qe/quarkus-test-framework/pull/1375 to be in a good shape, I can test locally, whether it fixes CliProdModeNativeIT; if it does, we can drop this change and go forth with yours, since other tests are not affected

If you are not in a hurry, I'd like to test it later this week

I definitely not in a hurry. If you consider #1375 to be in a good shape, I can test locally, whether it fixes CliProdModeNativeIT; if it does, we can drop this change and go forth with yours, since other tests are not affected

I basically need to drop everything I did there for OpenShift (because identifying criteria when to we can reuse native build in OCP is really hard) and re-check code. I'll prepare it and ask you for the review when it is ready. Thanks

@fedinskiy I had a look into CliProdModeNativeIT. #1375 has no effect over it because it doesn't deal with CLI tests. I tried to run this test in native mode and it succeeded without any Xmx adjustments:
20:02:03,045 INFO  [INFO] ------------------------------------------------------------------------
[INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 671.4 s -- in io.quarkus.ts.buildtimeanalytics.CliProdModeNativeIT

Could you try to enable it without any adjustments and see if GH CI pass, please?
I'll deal with #1375 separately.

BTW I think it would be really interesting to report it as a bug to upstream if you can gather some numbers for upstream engineers.


2.12 builds

Any chance that 0.7.0 could be built/published against 2.12.0-M2?

Hi @nbronson, Scala 2.12.0 final has been published, it would be cool to see a stm build built against it :)

As we rely on scala-stm in @openmole, we have some pre-built artefacts for Scala 2.11 and 2.12 on our own maven repo:
https://repository.iscpif.fr/maven/org/scala-stm/
This is built from @zenaptix-lab's fork.
Can't promise this will be a reliable solution for the years to come but hopefully it can help until an official release becomes available.
Thanks @romainreuillon for the build.

Looks like 0.8 has been published?

Yes. I'll update the web site today to match.
On Fri, Nov 18, 2016 at 3:19 AM Olli Helenius<EMAIL_ADDRESS>wrote:

Looks like 0.8 has been published
http://search.maven.org/#search|ga|1|a%3A"scala-stm_2.12"?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/nbronson/scala-stm/issues/48#issuecomment-261474009,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAH6WzhRWbZsotkhxqyF3VsJcirpaswVks5q_V-OgaJpZM4F6wPc
.


Added the ability to look up structural variations by their id

Made the necessary additions so that Structural Variants can be looked up through the search bar.
search.spec.js and Searchbox.spec.js seemingly contain unit tests and perhaps a simple search for a structural variant should be added to this list of tests? I'm not familiar enough with Javascript/Node.JS and not familiar enough with the code base to tinker with that.

@nawatts hm, commit history exploded (IDE hasn't been kind to me, had to dance around its integrated git system) anyways, everything should be in order now, a thing of note: When entering an SV id into the searchbar while a non SV dataset is selected from the dropdown the system tries to interpret the SV id as an SNP id (see photo):

this doesn't happen in the reverse case:

aught to be an issue somewhere in the existing codebase


add terraform-state-mover

Hi, Thanks for your awesome List.
I would lie to add the Tool "terraform-state-mover" to the tools section. It is a Handy tool that makes moving State a lot easier, It is for those "one time" Jobs where you will have to repair lot's of state Drift introduced by Outside forse by i.E. your Platform Provider.
I Really like it, and missed it on the List!
Thanks again!
Greetings
^C

Thanks @KeyboardInterrupt!

The PR description refers to this project https://github.com/mbode/terraform-state-mover, but the PR is for an entirely different project.


Manual approval required for workflow run<PHONE_NUMBER>

Workflow is pending manual review.
URL: https://github.com/ashishjullia/terraform-w-rollback/actions/runs/3475131507
Required approvers: [ashishjullia]
Respond "approved", "approve", "lgtm", "yes" to continue workflow or "denied", "deny", "no" to cancel.

approve


chore: Adds analytics for Property Pane keyboard navigation

Description
Adds PROPERTY_PANE_KEYPRESS event
Adds isUpdatedViaKeyboard parameter to WIDGET_PROPERTY_UPDATE event
Fixes #13217
TODO
As of now, the analytics event has been added only for DropdownControl.
It needs to be added for other controls as well.
Type of change

New feature (non-breaking change which adds functionality)

How Has This Been Tested?

Manual

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes

Test coverage results :test_tube:
:green_circle: Total coverage has increased
// Code coverage diff between base branch:release and head branch: pp-kbd-analytics

Status
File
% Stmts
% Branch
% Funcs
% Lines

:green_circle:
total
56.76 (0.05)
38.68 (0.01)
36.27 (0.05)
57.02 (0.06)

:green_circle:
app/client/src/components/ads/ButtonTabComponent.tsx
94.64 (0.76)
95.83 (0)
77.78 (0)
93.48 (1.17)

:green_circle:
app/client/src/components/ads/ColorPickerComponentV2.tsx
79.64 (0.79)
72.14 (0)
75 (0)
79.62 (0.85)

:green_circle:
app/client/src/components/ads/Dropdown.tsx
90.33 (0.23)
71.97 (0)
81.48 (0)
89.96 (0.29)

:red_circle:
app/client/src/components/ads/StepComponent.tsx
89.74 (-3.36)
83.33 (-6.67)
80 (-20)
89.74 (-3.36)

:red_circle:
app/client/src/components/ads/Switch.tsx
81.25 (-18.75)
50 (-25)
50 (-50)
81.25 (-18.75)

:green_circle:
app/client/src/components/ads/TreeDropdown.tsx
95.75 (0.18)
77.27 (-0.25)
97.37 (0)
96.92 (0.13)

:red_circle:
app/client/src/components/editorComponents/ActionCreator/Fields.tsx
35 (-0.31)
24.46 (-0.82)
10.39 (0)
34.34 (-0.31)

:green_circle:
app/client/src/components/editorComponents/CodeEditor/index.tsx
77.16 (0.19)
58.97 (0.56)
65.22 (0)
78.72 (0.26)

:red_circle:
app/client/src/components/propertyControls/ActionSelectorControl.tsx
82.35 (-5.15)
40 (-26.67)
75 (0)
85.71 (0)

:red_circle:
app/client/src/components/propertyControls/BaseControl.tsx
72.22 (-2.78)
44.44 (0)
40 (-10)
68.75 (-2.68)

:red_circle:
app/client/src/components/propertyControls/BorderRadiusOptionsControl.tsx
88.89 (-5.23)
25 (-25)
80 (0)
86.67 (-6.19)

:red_circle:
app/client/src/components/propertyControls/BoxShadowOptionsControl.tsx
89.47 (-4.97)
50 (-25)
80 (0)
87.5 (-5.83)

:red_circle:
app/client/src/components/propertyControls/ButtonTabControl.tsx
60.71 (-2.25)
23.08 (-4.19)
60 (0)
61.9 (0)

:red_circle:
app/client/src/components/propertyControls/IconSelectControl.tsx
91.45 (-0.04)
75.65 (-0.46)
92 (-3.83)
91.37 (-0.1)

:red_circle:
app/client/src/components/propertyControls/IconTabControl.tsx
69.57 (-3.16)
28.57 (-11.43)
75 (0)
75 (0)

:red_circle:
app/client/src/components/propertyControls/KeyValueComponent.tsx
15.38 (-0.2)
22.22 (-1.78)
0 (0)
16.67 (-0.23)

:red_circle:
app/client/src/components/propertyControls/LabelAlignmentOptionsControl.tsx
63.64 (-3.03)
25 (-8.33)
40 (0)
72.22 (0)

:red_circle:
app/client/src/components/propertyControls/NumericInputControl.tsx
46.15 (-3.85)
40 (0)
40 (-10)
47.83 (-2.17)

:red_circle:
app/client/src/components/propertyControls/OptionControl.tsx
66.67 (-4.76)
0 (0)
50 (0)
75 (0)

:red_circle:
app/client/src/components/propertyControls/StyledControls.tsx
54.08 (-1.24)
50.51 (0)
41.3 (0)
54.64 (-1.27)

:red_circle:
app/client/src/components/propertyControls/SwitchControl.tsx
87.5 (-5.36)
76.92 (-3.08)
71.43 (-3.57)
86.36 (-5.31)

:red_circle:
app/client/src/pages/Editor/PropertyPane/PropertyPaneView.tsx
87.76 (-1.98)
70.97 (1.4)
62.5 (2.5)
91.49 (-3.1)

:green_circle:
app/client/src/utils/AppsmithUtils.tsx
57.96 (0.88)
40.98 (0.15)
40.82 (1.24)
53.33 (0.9)

:red_circle:
app/client/src/utils/PropertyControlRegistry.tsx
87.1 (-12.9)
40 (-60)
91.67 (-8.33)
86.67 (-13.33)

:red_circle:
app/client/src/utils/WorkerUtil.ts
88.98 (-0.78)
70.59 (-1.96)
100 (0)
92.38 (-0.95)

:sparkles: :new:
app/client/src/utils/hooks/useInteractionAnalyticsEvent.ts
94.12
80
100
100

@riodeuno
Regarding separation of concerns:
Have a custom generic event keyboardAnalyticsEvent that is emitted from the DS component.
Capture this event in Property control and do whatever we want. What do you think about this?
Regarding 2nd point, let me try to implement the logic into the BaseControl. And add a hook that could be used by the components to emit events.

@aswathkk

Have a custom generic event keyboardAnalyticsEvent that is emitted from the DS component.

Yes, this makes sense to me. All our design system components can use a hook to do trigger events, which can be handled when it bubbles up. The reason for hooks, is once again separation of concerns, and making it DRY and re-usable.

@riodeuno The DP doesn't have the logs starting with "Event fired locally".
How could @vuiets take a look at this DP in that case?

@aswathkk I believe the loglevel localstorage key when set to "DEBUG" would show you the console logs in these scenarios. This is because, we use the log.debug function to log these entries on the console for debugging. (AnalyticsUtil.tsx).
The default value in our deploy previews for this is "ERROR" instead of "DEBUG".
We could do one of the following:

Set REACT_APP_CLIENT_LOG_LEVEL env variable for this particular PR in the vercel configuration. Not sure if this can be easily achieved.
Create a separate instance with the logging enabled so that @vuiets can review
Change one line in this PR so that logging is enabled. This can either be done by using log.error or hard-coding debug as the value for the config in configs/index.ts. However, we will need to tread carefully here, as it is important to revert this change once it has been reviewed, and the change has to be that one specific line which disables the logging.

@riodeuno Thanks for showing how this can be done.
Another hack that I found after going through the codebase is,
Just execute the following code snippet in the browser console to log the event:
window.analytics = {
    track: (name, data) => console.log("Event fired", name, data)
}

This is based on AnalyticsUtil.tsx:349

@aswathkk Sounds good, this is the third type of change, I recommended, where we need to revert it after review, before merging into release.

@riodeuno No. We don't have to make this change in the codebase. Rather we just need to execute it on the browser console of the DP.

Oh right, of course! Nice approach!

Looks good to me. Thanks @aswathkk!

@rahulramesha We are tracking only the tab keypress happening within the property pane. Nothing outside the property pane.

@rahulramesha We are tracking only the tab keypress happening within the property pane. Nothing outside the property pane.

yes, i understand that, just curious as to why, since it logs all navigation using tabs for propertyControls.

@rahulramesha we are trying to measure if a user is able to achieve their objective using keyboard navigation alone, for example if we want to we can now set up a funnel to see how many people used keyboard navigation to set the color of a button. If we don't log Tab events we would be able to say.
That being said do you see any performance issues in doing this?

@rahulramesha we are trying to measure if a user is able to achieve their objective using keyboard navigation alone, for example if we want to we can now set up a funnel to see how many people used keyboard navigation to set the color of a button. If we don't log Tab events we would be able to say.
That being said do you see any performance issues in doing this?

Got it. No issues, was just curious.

/ok-to-test sha=f6df9cc

@aswathkk Could we rename the "ADS" into something else? Like "DesignSystem" or simply "DS".

/ok-to-test sha=889a508

/ok-to-test sha=18c3350


Pass parameters to crud controller

Bug report
Hi ...
i have a problem when pass parameters to crud controller and i get the parameter in setup function :
 $passed_id = \Route::current()->parameter('id');
 error_log("test");
 error_log($passed_id);

the output show :
test
3
.
.
.
test
"empty line"
.
.
.
test
"empty line"
.
.
.

i don't andurstand why print "test" three times and i can't access the passed_id ?!
Does anyone know the problem? and how can i reach "id" at any time? ..
Thanks for help..
my backpack version is 4.0.x

Hi @Moaz-e ,
I recommend you take a look at the DeleteOperation for inspiration. There's not much different about parameters in Backpack - it's the same as in all Laravel apps. The only difference is that code that registered the route is inside the controller, not in a separate routes file.
The Delete operation for example uses the $id parameter by including it in the controller method:
    public function destroy($id)
    {
        $this->crud->hasAccessOrFail('delete');

        // get entry ID from Request (makes sure its the last ID for nested resources)
        $id = $this->crud->getCurrentEntryId() ?? $id;

        return $this->crud->delete($id);
    }

You could do that if you want. Or with any other way that Laravel can do this, Backpack won't restrict you. I'm going to close this as it's not a bug, and it's not Backpack-related.
Cheers!


Duplicate ids in templates

The following ids are non-unique:
GCS:DrugCurrentuse
VZ:UrineSampleCollected
VZ:UrineSampleNotCollectedReason
VZ:PipedTobaccoWeekly
VZ:UrineSampleCollectedId

If we change everything to numeric IDs in #92 this will be resolved. Maybe that's a good argument to change everything to numeric IDs.

Are these Ids non-unique in the source data dictionaries? That should be reported back to them! Even if we turn them into foreign id annotations, they should be unique, no?

Since I copied everything from the source data dictionaries, I believe so. I will review these in the original data though!

GCS:DrugCurrentuse
Appears on two different tabs in the data dictionary, but I suspect they are the same term. We should merge this one.
For Vukuzazi, it looks like they may be unintentional duplicates?

Perhaps it was meant to be something like VZ:UrineSample1Collected and VZ:UrineSample2Collected, like the swab samples shown above? This is something we should potentially report to them. Same with the other Vukuzazi duplicate IDs.

Maybe thats for @mcourtot to think about - communicating this back to the Vukuzazi people?

Since we are using numeric IDs now, I believe this is resolved.

Since we are using numeric IDs now, I believe this is resolved.


Add screenshots to README and docs

A few screenshots could make the tool more attractive. Currently, there is no impression given on how it looks like in action.

Shall I work on this issue? @mlange-42

Shall I work on this issue? @mlange-42

If you have some tracking data that is suitable to show off, or want to fake some for that purpose, this would be really welcomes!
If I may ask... are you a user of track already, or were you directed here by the good first issue label?

Shall I work on this issue? @mlange-42

If you have some tracking data that is suitable to show off, or want to fake some for that purpose, this would be really welcomes!
If I may ask... are you a user of track already, or were you directed here by the good first issue label?

Directed by a good first issue...

Shall I work on this issue? @mlange-42

If you have some tracking data that is suitable to show off, or want to fake some for that purpose, this would be really welcomes!
If I may ask... are you a user of track already, or were you directed here by the good first issue label?

But why this question❓

But why this question❓

Pure interest whether I have any users already 😆 (for which I should care about data backward compatibility 😉)
Just feel free not to answer it.

Shall I work on this issue? @mlange-42

Can I?

Do you want the screenshots only on the readme.md file? @mlange-42

Screenshots of what?

Documentation?

I think the most appealing would be the week and day reports. Particularly the week report could be placed prominently in the README and the intro page of the docs.
BTW, any feedback on other types of reports that could be useful is highly appreciated!

Do you want the screenshots only on the readme.md file?

I think the intro/title page of the docs would also be ok. But most importantly the README, yes.


feat(Text): add title attribute

Description
The full description of the changes made in this request.

add title props

Links
https://jira-eng-gpk2.cisco.com/jira/browse/SPARK-506030
Links to relevent resources.

title attribute has a poor Screen reader support and it has other UX and Accessibility issues. There are many articles about this problem, for example: https://www.a11yproject.com/posts/title-attributes/
Sorry, but I can not accept this PR until you describe your use case

I haven't noticed the effect of Screen reader. I will close the PR. Thanks!


#34656 Refactor navigator node rendering

https://github.com/user-attachments/assets/6e84a35c-e389-494d-9b81-71f537f449e0
Please test on:

[ ] Windows
[ ] Linux
[ ] macOS

Verified


blink_k20 fails to build

The read me at the root indicates to use the makefile to build; this doesn't work:
chris:zinc chrisjohnson$ EXAMPLE_NAME=blink_k20 make build
cd .
cargo build --example blink_k20 --release --target=thumbv7em-none-eabi --verbose --features mcu_k20
 Downloading num v0.1.27
 Downloading expectest v0.3.1
no example target named `blink_k20`
make: *** [target/thumbv7em-none-eabi/release/examples/blink_k20] Error 101

Further reading indicated I needed to 'care build' in the example directory, which initially failed due to my rust environment being stable, tried beta with the same error, so I tried nightly and got this new error:
chris:blink_k20 chrisjohnson$ cargo build
   Compiling ioreg v0.1.0 (file:///Users/chrisjohnson/zinc/examples/blink_k20)
   Compiling core v1.0.0 (https://github.com/hackndev/rust-libcore#d9dc4f94)
/Users/chrisjohnson/zinc/ioreg/src/builder/union.rs:179:22: 179:36 error: `ast::StructDef` does not name a structure [E0422]
/Users/chrisjohnson/zinc/ioreg/src/builder/union.rs:179     let struct_def = ast::StructDef {
                                                                             ^~~~~~~~~~~~~~
/Users/chrisjohnson/zinc/ioreg/src/builder/union.rs:179:22: 179:36 help: run `rustc --explain E0422` to see a detailed explanation
/Users/chrisjohnson/zinc/ioreg/src/builder/register.rs:166:13: 166:34 error: unresolved name `ast::TupleVariantKind` [E0425]
/Users/chrisjohnson/zinc/ioreg/src/builder/register.rs:166       kind: ast::TupleVariantKind(Vec::new()),
                                                                       ^~~~~~~~~~~~~~~~~~~~~
/Users/chrisjohnson/zinc/ioreg/src/builder/register.rs:166:13: 166:34 help: run `rustc --explain E0425` to see a detailed explanation
error: aborting due to 2 previous errors

It looks like some issue with ioreg?

Structs broke down in fun and unexpected way apparently, opened a PR to track a fix.

fixed in #351


Switch to API Token for PyPi uploads

Username/Password authentication is no longer supported. This PR migrates to using API Tokens per https://pypi.org/help/#apitoken. We use __token__ for the username and the org-wide PYPI_API_TOKEN secret for the password.
Reference:

https://github.com/pulumi/pulumi/pull/15048
https://github.com/pulumi/pulumi-policy/pull/322
https://github.com/pulumi/ci-mgmt/issues/751
https://github.com/pulumi/ci-mgmt/pull/767

This will need the same lint fix as in https://github.com/pulumi/pulumi-std/pull/35

This will need the same lint fix as in #35

I upgraded to actions/checkout@v4 and it did not alleviate the error I was facing. I tried adding set-safe-directory: true on top of it and that did not work either. I'm going to leave it as it is.

https://github.com/pulumi/pulumi-std/pull/35#discussion_r1441897473


Key bindings that open a new window in NeoVim deeply confusing

While editing a file, hit F1. At least for me, this silently opens the help buffer and switches to it inside of neovim (I think?). Suddenly the file is not modifiable and motion in the file doesn't actually move through the file in my window.
Amazingly, you can recover from this by sending :q to neovim (or otherwise closing the buffer).
At the least, it would be good to try and capture & override or fix all the default key bindings that can trigger this. I suspect there are other ways to get into this confusing state, so maybe it'd be better to intercept it at a lower level than key bindings and produce some kind of error or otherwise prevent the weird state from occurring?

Feel free to dup this one to #120 - especially as I was hitting that exact issue too.
Somehow wiring all vim window management operations to Sublime views (especially w/ origami like management of them) would be... really freaking cool.

I think we need external window layout for that (not landed in neovim yet): https://github.com/neovim/neovim/pull/5686
Some further reading: https://github.com/onivim/oni/issues/362

Seems like all but one subfeature of the mentioned RFC for neovim has been mergeed? (https://github.com/neovim/neovim/pull/5686#issuecomment-340711834)

nope:

There is still externalizing echo and error messages. It will be needed before external window layout.

"external window layout" is what we need.


feat: add walletconnect-v2 package to support WallectConnect v2

Description
Closes: #XXXX

This PR adds the @desmoslabs/desmjs-walletconnect-v2 package that supports the new WalletConnect v2 APIs.

Author Checklist
All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.
I have...

[x] included the correct type prefix in the PR title
[ ] targeted the correct branch (see PR Targeting)
[ ] provided a link to the relevant issue or specification
[ ] reviewed "Files changed" and left comments if necessary
[ ] confirmed all CI checks have passed

Reviewers Checklist
All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.
I have...

[ ] confirmed the correct type prefix in the PR title
[ ] confirmed all author checklist items have been addressed
[ ] confirmed that this PR does not change production code

@manu0466 There's the need to update Cosmjs to v0.29.5 to match #136


[Enhancement]: Would u like to add preloader to your indexpage

Do you want to have the enhancement of existing game ? 😀 Describe yourself..
Game enhancement
Adding preloader.
Describe the solution you'd like
Solution steps
Select program in which you are contributing
GSSoC24
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

Hey @Anjaliavv51 , You can't have another issue before completing the previous one 😀
you already have the following 1 open issues 👀 ! :
#3656

Hey @Anjaliavv51 ! Thank you so much for your raising the issue💗
It’s all yours, you can come anytime again and make some contributions! 🚀
Alone, we can do little, but together we can do so much! 😇

Hey @Anjaliavv51 !
Thank you for raising an issue 💗
You can self assign the issue by commenting /assign in comment 😀
Make sure you follow CODE OF CONDUCT and CONTRIBUTING GUIDELINES 🚀
Don’t Forget to ⭐ our GameZone🎮
Make sure you join our Discord🕹

Okay , i was confused

to whish issue i should rise that it

@kunjgit is this issue opened now?


evaluation code could use update

There should be a way of doing the evaluation without writing/reading files from disk.

Also not all annotations have to be read from disk

No more reading from disk, so it is much faster.


TextReplacer.SearchAndReplace cannot work on new WordprocessingDocument

using (WordprocessingDocument xxDoc = WordprocessingDocument.Create(dstPath, WordprocessingDocumentType.Document))
{
MainDocumentPart objMainDocumentPart = xxDoc.AddMainDocumentPart();
objMainDocumentPart.Document = new Document(new Body());
           //add paragraphs here

           TextReplacer.SearchAndReplace(xxDoc, tTarget, tKeyVP.Value, true);

}
SearchAndReplace will throw an exception. _exceptionMethod = {System.Xml.Linq.XDocument GetXDocument(DocumentFormat.OpenXml.Packaging.OpenXmlPart)}
It should be xxDoc cannot build the OpenXmlPart, what should I do? Please give me a method.
ps:
for example:
var inputDoc = WordprocessingDocument.Create("ttt.docx", WordprocessingDocumentType.Document);
        MainDocumentPart inputMainPart = inputDoc.AddMainDocumentPart();
        inputMainPart.Document = new Document(new Body(new
       DocumentFormat.OpenXml.Wordprocessing.Paragraph(new Run(new Text("Hello,world."))), new                       DocumentFormat.OpenXml.Wordprocessing.Paragraph(new Run(new Text("xxxx.")))));
        inputDoc.Save();

        TextReplacer.SearchAndReplace(inputDoc, "xxx", "ccc", false);

I got a null exception, whenever I save it then open the doc or I create it in memory like above.
Please tell me what should I do?
The word is here:
Hello,world.xxxx.

i suggest before you call search and replace , put a break point and check if your inputDoc has MainDocumentPart or not? you dont want this to be null before you calling textreplacer.
and what is it that you are trying to achieve here?

Closing all issues as this repo is being archived and will no longer be maintained by Microsoft. The project is licensed for continued use and development by forking to your own repo.


Frameless + Maximize / Minimize does not keep the current route.

I'm using AngularJS v1.3.15 and NW v0.12.1 with Windows 7 SP1 64 Bits.
My application (Web API) have a problem with window operations. When I called win.maximize() or anyone, the route change to Index.
I think that "var win = nw.Window.get();" see the index as your current window, because the window.location.path refers to index.
However, if I keep frame = true in my package.json, the frame buttons work perfectly.
The behavior of object window is different of nw than native frame.

It seems like it's nw.js problem.
Can you provide some example that causes that problem?
I add minimize/maximize buttons for frameless-window example https://github.com/zcbenz/nw-sample-apps/commit/1bf6b9f621d4429dd4da0ddfbf3a6fb05596cc64
Does that problem appear too? Sorry, I don't have windows computer near me to check

Sorry, I discovered the problem.
I remade my solution to be equal the examplo that I found (http://nodehead.com/node-webkit-custom-window-controls-26/).
In this example he uses ... This is the problem, but with one page (case of example) work perfectly.
I will close the issue.
Thanks!


batch transcription DisplayFull

Some of my responses from the batch transcription API do have a DisplayFull key, some of them do not.
Where's the documentation on this?
How can I ensure I get a DisplayFull every time?

@theonlygusti To assist you better on your query could you provide us with the link to the document you are referring to ?
In case your query in not related to document content, open a new forum thread either in MSDN or StackOverflow as it could be better place to get help on your scenario where the community members could provide their expert guidance to you based on their experience.

@SaurabhSharma-MSFT https://docs.microsoft.com/en-us/azure/cognitive-services/speech-service/batch-transcription

@theonlygusti I have forward this issue to product team, I will let you know the update when we have one. Thank you very much. I will close this issue for now.  We will now proceed to close this thread. If there are further questions regarding this matter, please respond here and @YutongTie-MSFT and we will gladly continue the discussion.


Update Xinmeitulu & Meitua.top: Support filter/search & translate

Checklist:

[X] Updated extVersionCode value in build.gradle for individual extensions
[X] Updated overrideVersionCode or baseVersionCode as needed for all multisrc extensions
[X] Referenced all related issues in the PR body (e.g. "Closes #xyz")
[X] Added the isNsfw = true flag in build.gradle when appropriate
[X] Have not changed source names
[X] Have explicitly kept the id if a source's name or language were changed
[X] Have tested the modifications by compiling and running the extension through Android Studio
[X] Have removed web_hi_res_512.png when adding a new extension

Added genre translation, but again, genre won't show in manga browse list & it's not available in manga's detail page. Is there anyway to pass SManga from popularMangaFromElement to mangaDetailsParse?

Added genre translation, but again, genre won't show in manga browse list & it's not available in manga's detail page. Is there anyway to pass SManga from popularMangaFromElement to mangaDetailsParse?

Oh right. Probably open an issue in Mihon lol.

Don't merge this yet. I'm doing more translation.

Closing because you seem to not have a good enough command of the Chinese language and are resorting to machine translation. Feel free to maintain the English versions on your own.


Internet Explorer 11 Support

I noticed while trying to use it in IE11 I'm hitting issues. In particular, the build includes arrow-functions which IE11 does not support at all.
Debugger:

So, more of a general question - what browsers does the library attempt to support? I might be one of the last people on planet earth considering supporting IE11 at this point, so I would completely get it if oidc-react does not support it. But it would be good to lay that out clearly. If it does try and support IE11, there may be a babel preset needed to cover this.

@pseudoramble how is this going? Is there anything I can help with?

Hi - Sorry this has fallen off my radar and is a bit lower priority now in our group. That being said, it's still of interest to me and I do plan on looking at it.

I was able to make a bit of progress on this finally. Rebuilding it with targeting ES5 does manage to eliminate these specific issues and I don't see any surprises that would bust IE11. However due to my current setup I don't have a great way to do a complete test of the actual features in IE11, but rather loading the code.
I'm happy to open up a PR to change the build target, but there could be more issues after this. What do you think?

We can open a pull request on it and see? 🤷♂

Ready for review when you're ready @cobraz! Thanks for the help!


Array agg

Allow array aggregate on pseudo-columns. One of the test cases will fail because the array aggregate function in ermrest is not deterministic and is not sorting the values. I wasn't sure if I should sort the values, or modify the test case to just look for the values and not the actual order (We should discuss this during the meeting).
#643

We decided to rely on the javascript sort function for now and simply sort the raw values that we're getting from ermrset.


Prometheus service scraping receive 403 when RBAC is enabled

Bug description
In k8s 1.14.0 with Istio 1.3 installed with (Helm) and mtls enabled. We have enabled ClusterRbacConfig in ON_WITH_EXCLUSION mode (excluding istio-system). Prometheus scrapper is running in the istio-system namespace.
We have te following ServiceRole:
apiVersion: "rbac.istio.io/v1alpha1"
kind: ServiceRole
metadata:
  name: access
  namespace: namespace
spec:
  rules:
  - services: ["service.namespace.svc.cluster.local"]
    methods: ["*"]
    paths: ["*"]

and ServiceRoleBinding:
apiVersion: "rbac.istio.io/v1alpha1"
kind: ServiceRoleBinding
metadata:
  name: access
  namespace: namespace
spec:
  subjects:
  - properties:
      source.principal: "cluster.local/ns/istio-system/sa/prometheus"
  # other access
  roleRef:
    kind: ServiceRole
    name: "access"

The pods running the service in the port 8080 has istio sidecar and the service is receiving requests from other services and istio-ingressgateway but from prometheus scraper no.
The url http://<IP_ADDRESS>:15090/stats/prometheus (Istio metrics) is accesible but https://<IP_ADDRESS>:8080/stats/prometheus (service metrics) are not accesible. If we run the same endpoint from other service (not prometheus) using http://service.namespace.svc.cluster.local/stats/prometheus the request is received in the service.
The service deployment has the following annotation:
        prometheus.io/path: /stats/prometheus
        prometheus.io/port: "8080"
        prometheus.io/scheme: https
        prometheus.io/scrape: "true"

If we disable rbac, the prometheus scrapper works again.

same issue +1

Istio 1.3 reaches its end of support. Please confirm whether this is reproducible from 1.4 as well.

Confirmed

It's likely the prometheus is calling using plain text instead of mTLS, it gets rejected by RBAC because it doesn't have the identity ("cluster.local/ns/istio-system/sa/prometheus") when using plain text.
@aalmazanarbs For 1.3, I think you probably have to disable the RBAC policy on port 8080, For 1.4, it's strongly recommended to use the v1beta1 authorization policy that deprecates the v1alpha1 RBAC policy, and also whitelist port 8080. For 1.5, I thought we did some work to add the sidecar to prometheus? (cc @lei-tang to confirm).

Thank you for your answer @yangminzhu
How can we check if prometheus is calling or not with mTLS? We would like to check it to understand
why, pod istio-ingressgateway (without istio sidecar), is able to reach service.namespace.svc.cluster.local if we configure in the ServiceRoleBinding source.principal: "cluster.local/ns/istio-system/sa/istio-ingressgateway-service-account" but prometheus no. My guess is that prometheus is using the IP of the pod and ingress uses the service...so can we whitelist that with ServiceRole or authorizationPolicy?
On the other hand, we can not whitelist port 8080 because that port is where the api of the service is exposed. But...if we get to expose prometheus api in other port, how can we disable RBAC policy (1.3) on a expecific port?

One quick way is just to run kubectl get <prometheus-pod> -n istio-system to see how many containers it has. If it's only one, then definitely it's not mTLS because there is no sidecar inside it. You could also follow https://archive.istio.io/v1.4/docs/ops/common-problems/security-issues/#ensure-proxies-enforce-policies-correctly to turn on the rbac:debug logging on your service and check the logging.
The pod istio-ingressgateway itself is an Envoy so it doesn't need sidecar, or you could think like it only has sidecar and doesn't have application container.

if we get to expose prometheus api in other port, how can we disable RBAC policy (1.3) on a expecific port?

Yes, this is totally possible, you just need to put the port using the destination.port constraint in ServiceRole and bind it with a ServiceRoleBinding that grants permissions to all (*): https://archive.istio.io/v1.4/docs/reference/config/security/constraints-and-properties/
Note, In RBAC policy,  the destination.port is the service port (not the workload port). In the new AuthZ policy, it has first-class field ports and it's the workload port (not the service port because the whole new AuthZ policy is based on workload and not service): https://archive.istio.io/v1.4/docs/reference/config/security/authorization-policy/

Thank you again @yangminzhu.
Following your advices our final solution is (keeping same port):
apiVersion: "rbac.istio.io/v1alpha1"
kind: ServiceRole
metadata:
  name: access
  namespace: namespace
spec:
  rules:
  - services: ["service.namespace.svc.cluster.local"]
    methods: ["GET"]
    paths: ["/stats/prometheus"]

apiVersion: "rbac.istio.io/v1alpha1"
kind: ServiceRoleBinding
metadata:
  name: access
  namespace: namespace
spec:
  subjects:
  - properties:
      source.namespace: "istio-system"
  roleRef:
    kind: ServiceRole
    name: "access"

Since the prometheus pod is in the istio-system, the RBAC works and ServiceRole is allowed only to that namespace. But this is a security problem because, in the istio-system names are the ingress so the endpoint may be exposed to outside cluster but it is filtered in the apigateway. I know another solution is move prometheus or ingress to other namespace but the best solution will be source.principal: "cluster.local/ns/istio-system/sa/prometheus" works.


cmd/go2go: conversion using type lists

Consider the following code (playground):
func Convert(type T interface{}, U interface{ type T })(t T) U {
	return U(t)
}

It does not compile, with the error:
prog.go2:4:11: cannot convert t (variable of type T) to U

It seems to me like this should compile: the design says

More precisely, the underlying type of the type argument must be identical to the underlying type of one of the types in the type list.

which I understand to mean the underlying type of U must be identical to the underlying type of T; the spec gives that as a sufficient condition to allow U(t).

Relatedly, it looks like the following more specialized function gives the same error:
func ConvertToString(type T interface{ type string })(t T) string {
	return string(t)
}

CC @griesemer
I think that strictly speaking the design draft says that this code should not compile.  It's an interesting case, though.

The reason I say that it maybe should not compile is that your argument hinges on the underlying type of T, which is a little murky.

I think both design draft and spec refer to underlying types on both sides in the relevant contexts?
Not that I would be particularly sad if it didn't, as long as it's clear: this code didn't end up being very useful to me for other reasons.

First case is similar a bit to https://github.com/golang/go/issues/39930#issuecomment-651426412.
operand.assignableTo function just fails to match two types.
It happens because there are not checks for underlying

*types.TypeParam and *types.top

Second example fails here https://github.com/golang/go/blob/6cf6bf162c4e1f30080461d04d6a6f28d3cebe81/src/go/types/operand.go#L269
Underlying types are identical, but both are Named.

@tdakkota That may be the reason for this failure but not the reasoning as to why it shouldn't fail.
@ianlancetaylor has pointed at the culprit: The outcome hinges on what the underlying type of a type parameter is. One answer is that it is described by the type list in its constraint. Another one is that the underlying type of a type parameter is itself. Currently we implement the latter. The correct answer may be some variation of the former. This is under active investigation.

The first example here is not valid code with Go 1.18. The second example (adjusted) works now as expected. Closing.


 Please fix it or delete the repo.

As a junior frontend developer, I appreciate your feedback. I understand that the UI may not meet expectations, and I'm eager to improve. Could you please provide specific details on what aspects of the UI you find lacking or problematic? This will help me learn and enhance my skills.

Buttons too sharp, colors too bright, you noob

Thank you for the specific feedback. I understand your concerns about the sharpness of the buttons and the brightness of the colors. I'll work on refining these aspects to create a more visually appealing and user-friendly UI.

Upon my meticulous review of the frontend interface, I am compelled to express my dissatisfaction due to a plethora of critical concerns. Firstly, the overall design appears to be a haphazard amalgamation of obsolete paradigms, egregiously failing to adhere to modern UX principles. The color scheme, reminiscent of a bygone era, severely lacks the visual hierarchy necessary for an intuitive user experience. Moreover, the responsiveness of the layout is abysmally subpar, egregiously faltering on various devices and screen sizes, thus undermining the fundamental principles of responsive web design. The navigation structure is a labyrinthine conundrum, convoluted to the extent of leaving users in a perpetual state of bewilderment. Additionally, the use of AJAX requests seems recklessly implemented, leading to egregious load times and a detrimental impact on the site's overall performance. In conclusion, this frontend is a stark embodiment of how not to approach modern web development, blatantly ignoring established standards and best practices in favor of a disjointed and antiquated user interface.

Your assessment of the frontend interface is thorough and critical, highlighting several crucial areas of concern. Here's a breakdown of the issues you've raised:

Obsolete Design Paradigms: You've pointed out that the design lacks modernity and coherence, potentially hindering user engagement and satisfaction.

Outdated Color Scheme: The choice of colors fails to establish a clear visual hierarchy, which is essential for guiding users through the interface efficiently.

Poor Responsiveness: The layout's inability to adapt seamlessly to different devices and screen sizes suggests a lack of attention to responsive design principles, which are essential for catering to diverse user needs.

Complex Navigation Structure: The convoluted navigation system adds unnecessary complexity, potentially frustrating users and impeding their ability to navigate the site effectively.

Inefficient Use of AJAX: The implementation of AJAX requests appears to be flawed, resulting in long loading times and negatively impacting the site's performance.

Your critique emphasizes the importance of adhering to modern UX principles, responsive design standards, and efficient implementation techniques in web development. It suggests the need for a comprehensive overhaul of the frontend interface to address these critical concerns and enhance the overall user experience.

Outmoded Design Methodologies: Highlighted the interface's lack of alignment with contemporary design trends, underscoring the need for a more cohesive and user-friendly approach to enhance user engagement.

Inadequate Color Palette: Noted the deficient visual hierarchy due to an antiquated color scheme. This lack of clarity in design elements can lead to a disjointed user experience, emphasizing the need for a more strategic use of color to guide user interaction.

Deficient Responsiveness: Addressed significant shortcomings in the layout's adaptability across various devices and screen sizes. This critique underscores the paramount importance of robust responsive design practices to accommodate a wide range of user environments.

Overcomplex Navigation System: Identified issues with the overly complicated navigation structure, which can lead to user confusion and frustration. This aspect highlights the necessity for a more intuitive and streamlined navigation design, ensuring easy access to information.

Suboptimal AJAX Implementation: Criticized the inefficient application of AJAX requests, contributing to prolonged loading times and poor site performance. This points to a need for optimizing request handling and data loading processes to enhance the website's efficiency and user satisfaction.

Your revised analysis further underscores the deficiencies in the frontend interface, emphasizing the urgency for improvement:

Outmoded Design Methodologies: Highlighting the interface's departure from contemporary design trends emphasizes the importance of updating design approaches to enhance user engagement and satisfaction.

Inadequate Color Palette: The mention of deficient visual hierarchy due to an antiquated color scheme highlights the necessity for a strategic use of color to improve user experience and streamline interaction.

Deficient Responsiveness: Addressing the layout's inability to adapt effectively to various devices emphasizes the critical need for robust responsive design practices to ensure accessibility and usability across different environments.

Overcomplex Navigation System: Pointing out issues with the navigation structure emphasizes the importance of simplifying and streamlining navigation to improve user comprehension and ease of use.

Suboptimal AJAX Implementation: Criticizing the inefficiency of AJAX requests underscores the need for optimizing data loading processes to enhance site performance and user satisfaction.

Overall, your analysis provides a comprehensive overview of the frontend interface's shortcomings and highlights key areas for improvement to enhance the user experience and align with modern design and development standards.

@FedeDC512 looks like:

Thank you to everyone who provided feedback and suggestions. Your insights have been incredibly valuable in helping me grow as a frontend developer. I am committed to continuously improving my skills, and I appreciate the opportunity to learn from your perspectives. In the future, I aim to revisit this project with enhanced expertise to create an even better user experience. Your support and guidance are greatly appreciated. ✨


gdal: 2.2.3 -> 2.2.4

Semi-automatic update generated by https://github.com/ryantm/nix-update tools. These checks were done:

built on NixOS
ran /nix/store/jdbh08lrbarwcp1j656y02qqjlcv28xf-gdal-2.2.4/bin/.epsg_tr.py-wrapped --version and found version 2.2.4
ran /nix/store/jdbh08lrbarwcp1j656y02qqjlcv28xf-gdal-2.2.4/bin/epsg_tr.py --version and found version 2.2.4
ran /nix/store/jdbh08lrbarwcp1j656y02qqjlcv28xf-gdal-2.2.4/bin/.gcps2vec.py-wrapped --version and found version 2.2.4
ran /nix/store/jdbh08lrbarwcp1j656y02qqjlcv28xf-gdal-2.2.4/bin/gcps2vec.py --version and found version 2.2.4
ran /nix/store/jdbh08lrbarwcp1j656y02qqjlcv28xf-gdal-2.2.4/bin/.gdal2tiles.py-wrapped -h got 0 exit code
ran /nix/store/jdbh08lrbarwcp1j656y02qqjlcv28xf-gdal-2.2.4/bin/.gdal2tiles.py-wrapped --help got 0 exit code
ran /nix/store/jdbh08lrbarwcp1j656y02qqjlcv28xf-gdal-2.2.4/bin/.gdal2tiles.py-wrapped --version and found version 2.2.4
ran /nix/store/jdbh08lrbarwcp1j656y02qqjlcv28xf-gdal-2.2.4/bin/gdal2tiles.py -h got 0 exit code
ran /nix/store/jdbh08lrbarwcp1j656y02qqjlcv28xf-gdal-2.2.4/bin/gdal2tiles.py --help got 0 exit code
ran /nix/store/jdbh08lrbarwcp1j656y02qqjlcv28xf-gdal-2.2.4/bin/gdal2tiles.py --version and found version 2.2.4
ran /nix/store/jdbh08lrbarwcp1j656y02qqjlcv28xf-gdal-2.2.4/bin/.gdal_auth.py-wrapped --version and found version 2.2.4
ran /nix/store/jdbh08lrbarwcp1j656y02qqjlcv28xf-gdal-2.2.4/bin/gdal_auth.py --version and found version 2.2.4
ran /nix/store/jdbh08lrbarwcp1j656y02qqjlcv28xf-gdal-2.2.4/bin/.gdal_fillnodata.py-wrapped --version and found version 2.2.4
ran /nix/store/jdbh08lrbarwcp1j656y02qqjlcv28xf-gdal-2.2.4/bin/gdal_fillnodata.py --version and found version 2.2.4
ran /nix/store/jdbh08lrbarwcp1j656y02qqjlcv28xf-gdal-2.2.4/bin/.gdal_merge.py-wrapped --version and found version 2.2.4
ran /nix/store/jdbh08lrbarwcp1j656y02qqjlcv28xf-gdal-2.2.4/bin/gdal_merge.py --version and found version 2.2.4
ran /nix/store/jdbh08lrbarwcp1j656y02qqjlcv28xf-gdal-2.2.4/bin/.gdal_polygonize.py-wrapped --version and found version 2.2.4
ran /nix/store/jdbh08lrbarwcp1j656y02qqjlcv28xf-gdal-2.2.4/bin/gdal_polygonize.py --version and found version 2.2.4
ran /nix/store/jdbh08lrbarwcp1j656y02qqjlcv28xf-gdal-2.2.4/bin/.gdal_proximity.py-wrapped --version and found version 2.2.4
ran /nix/store/jdbh08lrbarwcp1j656y02qqjlcv28xf-gdal-2.2.4/bin/gdal_proximity.py --version and found version 2.2.4
ran /nix/store/jdbh08lrbarwcp1j656y02qqjlcv28xf-gdal-2.2.4/bin/.gdal_sieve.py-wrapped --version and found version 2.2.4
ran /nix/store/jdbh08lrbarwcp1j656y02qqjlcv28xf-gdal-2.2.4/bin/gdal_sieve.py --version and found version 2.2.4
ran /nix/store/jdbh08lrbarwcp1j656y02qqjlcv28xf-gdal-2.2.4/bin/.gdalchksum.py-wrapped --version and found version 2.2.4
ran /nix/store/jdbh08lrbarwcp1j656y02qqjlcv28xf-gdal-2.2.4/bin/gdalchksum.py --version and found version 2.2.4
ran /nix/store/jdbh08lrbarwcp1j656y02qqjlcv28xf-gdal-2.2.4/bin/.gdalcompare.py-wrapped --version and found version 2.2.4
ran /nix/store/jdbh08lrbarwcp1j656y02qqjlcv28xf-gdal-2.2.4/bin/gdalcompare.py --version and found version 2.2.4
ran /nix/store/jdbh08lrbarwcp1j656y02qqjlcv28xf-gdal-2.2.4/bin/.gdalident.py-wrapped -h got 0 exit code
ran /nix/store/jdbh08lrbarwcp1j656y02qqjlcv28xf-gdal-2.2.4/bin/.gdalident.py-wrapped --help got 0 exit code
ran /nix/store/jdbh08lrbarwcp1j656y02qqjlcv28xf-gdal-2.2.4/bin/.gdalident.py-wrapped help got 0 exit code
ran /nix/store/jdbh08lrbarwcp1j656y02qqjlcv28xf-gdal-2.2.4/bin/.gdalident.py-wrapped --version and found version 2.2.4
ran /nix/store/jdbh08lrbarwcp1j656y02qqjlcv28xf-gdal-2.2.4/bin/gdalident.py -h got 0 exit code
ran /nix/store/jdbh08lrbarwcp1j656y02qqjlcv28xf-gdal-2.2.4/bin/gdalident.py --help got 0 exit code
ran /nix/store/jdbh08lrbarwcp1j656y02qqjlcv28xf-gdal-2.2.4/bin/gdalident.py help got 0 exit code
ran /nix/store/jdbh08lrbarwcp1j656y02qqjlcv28xf-gdal-2.2.4/bin/gdalident.py --version and found version 2.2.4
ran /nix/store/jdbh08lrbarwcp1j656y02qqjlcv28xf-gdal-2.2.4/bin/.gdalimport.py-wrapped --version and found version 2.2.4
ran /nix/store/jdbh08lrbarwcp1j656y02qqjlcv28xf-gdal-2.2.4/bin/gdalimport.py --version and found version 2.2.4
ran /nix/store/jdbh08lrbarwcp1j656y02qqjlcv28xf-gdal-2.2.4/bin/.gdalmove.py-wrapped --version and found version 2.2.4
ran /nix/store/jdbh08lrbarwcp1j656y02qqjlcv28xf-gdal-2.2.4/bin/gdalmove.py --version and found version 2.2.4
ran /nix/store/jdbh08lrbarwcp1j656y02qqjlcv28xf-gdal-2.2.4/bin/.mkgraticule.py-wrapped help got 0 exit code
ran /nix/store/jdbh08lrbarwcp1j656y02qqjlcv28xf-gdal-2.2.4/bin/mkgraticule.py help got 0 exit code
ran /nix/store/jdbh08lrbarwcp1j656y02qqjlcv28xf-gdal-2.2.4/bin/.rgb2pct.py-wrapped --version and found version 2.2.4
ran /nix/store/jdbh08lrbarwcp1j656y02qqjlcv28xf-gdal-2.2.4/bin/rgb2pct.py --version and found version 2.2.4
ran /nix/store/jdbh08lrbarwcp1j656y02qqjlcv28xf-gdal-2.2.4/bin/gdalinfo --version and found version 2.2.4
ran /nix/store/jdbh08lrbarwcp1j656y02qqjlcv28xf-gdal-2.2.4/bin/gdalserver --version and found version 2.2.4
ran /nix/store/jdbh08lrbarwcp1j656y02qqjlcv28xf-gdal-2.2.4/bin/gdal_translate --version and found version 2.2.4
ran /nix/store/jdbh08lrbarwcp1j656y02qqjlcv28xf-gdal-2.2.4/bin/gdaladdo --version and found version 2.2.4
ran /nix/store/jdbh08lrbarwcp1j656y02qqjlcv28xf-gdal-2.2.4/bin/gdalwarp --version and found version 2.2.4
ran /nix/store/jdbh08lrbarwcp1j656y02qqjlcv28xf-gdal-2.2.4/bin/nearblack --version and found version 2.2.4
ran /nix/store/jdbh08lrbarwcp1j656y02qqjlcv28xf-gdal-2.2.4/bin/gdalmanage --version and found version 2.2.4
ran /nix/store/jdbh08lrbarwcp1j656y02qqjlcv28xf-gdal-2.2.4/bin/gdalenhance --version and found version 2.2.4
ran /nix/store/jdbh08lrbarwcp1j656y02qqjlcv28xf-gdal-2.2.4/bin/gdaltransform --version and found version 2.2.4
ran /nix/store/jdbh08lrbarwcp1j656y02qqjlcv28xf-gdal-2.2.4/bin/gdallocationinfo --version and found version 2.2.4
ran /nix/store/jdbh08lrbarwcp1j656y02qqjlcv28xf-gdal-2.2.4/bin/gdalsrsinfo help got 0 exit code
ran /nix/store/jdbh08lrbarwcp1j656y02qqjlcv28xf-gdal-2.2.4/bin/gdalsrsinfo --version and found version 2.2.4
ran /nix/store/jdbh08lrbarwcp1j656y02qqjlcv28xf-gdal-2.2.4/bin/gdaltindex --version and found version 2.2.4
ran /nix/store/jdbh08lrbarwcp1j656y02qqjlcv28xf-gdal-2.2.4/bin/gdal_rasterize --version and found version 2.2.4
ran /nix/store/jdbh08lrbarwcp1j656y02qqjlcv28xf-gdal-2.2.4/bin/gdal_grid --version and found version 2.2.4
ran /nix/store/jdbh08lrbarwcp1j656y02qqjlcv28xf-gdal-2.2.4/bin/ogrinfo help got 0 exit code
ran /nix/store/jdbh08lrbarwcp1j656y02qqjlcv28xf-gdal-2.2.4/bin/ogrinfo --version and found version 2.2.4
ran /nix/store/jdbh08lrbarwcp1j656y02qqjlcv28xf-gdal-2.2.4/bin/ogr2ogr --version and found version 2.2.4
ran /nix/store/jdbh08lrbarwcp1j656y02qqjlcv28xf-gdal-2.2.4/bin/ogrlineref --version and found version 2.2.4
ran /nix/store/jdbh08lrbarwcp1j656y02qqjlcv28xf-gdal-2.2.4/bin/testepsg -h got 0 exit code
ran /nix/store/jdbh08lrbarwcp1j656y02qqjlcv28xf-gdal-2.2.4/bin/testepsg --help got 0 exit code
ran /nix/store/jdbh08lrbarwcp1j656y02qqjlcv28xf-gdal-2.2.4/bin/testepsg help got 0 exit code
ran /nix/store/jdbh08lrbarwcp1j656y02qqjlcv28xf-gdal-2.2.4/bin/gdalbuildvrt --version and found version 2.2.4
ran /nix/store/jdbh08lrbarwcp1j656y02qqjlcv28xf-gdal-2.2.4/bin/gnmmanage --version and found version 2.2.4
ran /nix/store/jdbh08lrbarwcp1j656y02qqjlcv28xf-gdal-2.2.4/bin/gnmanalyse --version and found version 2.2.4
ran /nix/store/jdbh08lrbarwcp1j656y02qqjlcv28xf-gdal-2.2.4/bin/gdal-config --version and found version 2.2.4
found 2.2.4 with grep in /nix/store/jdbh08lrbarwcp1j656y02qqjlcv28xf-gdal-2.2.4
directory tree listing: https://gist.github.com/9fbb0e6bcdf6a8ed1d3b5a8f20a84eca

cc @marcweber for review

Failure on x86_64-darwin (full log)
Attempted: gdal
Partial log (click to expand)
    return nullptr;
           ^
1 error generated.
[3/158] Building CXX object CMakeFiles/poppler.dir/goo/GooList.cc.o
[4/158] Building CXX object CMakeFiles/poppler.dir/goo/GooTimer.cc.o
[5/158] Building CXX object CMakeFiles/poppler.dir/goo/gfile.cc.o
ninja: build stopped: subcommand failed.
builder for '/nix/store/1hdp52grh3rz4cf8b2bip4hc0q6ckahh-poppler-glib-0.62.0.drv' failed with exit code 1
cannot build derivation '/nix/store/wq6rvxc54yi228ifpfg5xash020sshvy-gdal-2.2.4.drv': 1 dependencies couldn't be built
error: build of '/nix/store/wq6rvxc54yi228ifpfg5xash020sshvy-gdal-2.2.4.drv' failed

Success on x86_64-linux (full log)
Attempted: gdal
Partial log (click to expand)
shrinking /nix/store/jdbh08lrbarwcp1j656y02qqjlcv28xf-gdal-2.2.4/lib/python2.7/site-packages/osgeo/_gdal_array.so
shrinking /nix/store/jdbh08lrbarwcp1j656y02qqjlcv28xf-gdal-2.2.4/lib/python2.7/site-packages/osgeo/_ogr.so
shrinking /nix/store/jdbh08lrbarwcp1j656y02qqjlcv28xf-gdal-2.2.4/lib/python2.7/site-packages/osgeo/_gnm.so
shrinking /nix/store/jdbh08lrbarwcp1j656y02qqjlcv28xf-gdal-2.2.4/lib/python2.7/site-packages/osgeo/_gdalconst.so
strip is /nix/store/fzcs0fn6bb04m82frhlb78nc03ny3w55-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/jdbh08lrbarwcp1j656y02qqjlcv28xf-gdal-2.2.4/lib  /nix/store/jdbh08lrbarwcp1j656y02qqjlcv28xf-gdal-2.2.4/bin
patching script interpreter paths in /nix/store/jdbh08lrbarwcp1j656y02qqjlcv28xf-gdal-2.2.4
/nix/store/jdbh08lrbarwcp1j656y02qqjlcv28xf-gdal-2.2.4/bin/gdal-config: interpreter directive changed from "/bin/sh" to "/nix/store/q1g0rl8zfmz7r371fp5p42p4acmv297d-bash-4.4-p19/bin/sh"
checking for references to /build in /nix/store/jdbh08lrbarwcp1j656y02qqjlcv28xf-gdal-2.2.4...
/nix/store/jdbh08lrbarwcp1j656y02qqjlcv28xf-gdal-2.2.4

Failure on aarch64-linux (full log)
Attempted: gdal
Partial log (click to expand)
 int
/build/hdf-4.2.12/hdf/src/hfile.h:322:7: error: unknown type name 'intn'
       intn        special;      /* special element ? */
       ^~~~
/build/hdf-4.2.12/hdf/src/tbbt.h:290:56: error: unknown type name 'VOID'
                 (TBBT_NODE ** root, VOID(*fd) (VOIDP), VOID(*fk) (VOIDP));
                                                        ^~~~
building of '/nix/store/3scmdqgk832hw5qgjkybwjp9ghvn8hi9-hdf-4.2.12.drv' timed out after 3600 seconds
cannot build derivation '/nix/store/8gz3icbiwb32l87l5x0ih76jjwhcgfy9-gdal-2.2.4.drv': 1 dependencies couldn't be built
error: build of '/nix/store/8gz3icbiwb32l87l5x0ih76jjwhcgfy9-gdal-2.2.4.drv' failed


Method name as a label for thrift metrics

Title: Method name as a label for thrift metrics
Hey thrift owners @zuercher @JuniorHsu,
We would like expose some additional o11y for thrift proxy in the form of adding 3 new metrics (these can be either entirely new or just labels on the existing metrics):

{method_name}_response_success
{method_name}_response_errors
{method_name}_response_exception

Which contain method name as part of the label for the requests. Does this request make sense? WDYT?

Hello @davinci26
Thanks for raising this issue. It makes sense but there's a few notes:
(a) where's is the metrics emitting? we're able to emit in a new filter with bidirectional filter [1]. we could also send from connection manager view or cluster view (after routing decision) as well. actually we have a non-opensource metrics filter which basically does the jobs. The biggest thing is performance issue, tho we don't get latency degrade but it takes 50% more cpu on thrift data flow since we're using Stats::DynamicSavedName . Unsure if we could use table join like zone metrics [2] but iirc it's not possible in a filter (i might be wrong)
(b) Even we use a connmgr or cluster view metrics, most o11y has cardinality issue, which suggests those metrics with methods should be optional. Probably a repeated field like repeated method_name_metrics and empty means no metrics with method name. (filter is already optional by its nature)
(c) consider add exception_local/exception_remote which is the first thing we're trying to tell the bugs. we also have invalid type/decoding error in cluster view metrics iirc but not a problem usually.
[1] https://github.com/envoyproxy/envoy/pull/20816
[2] https://github.com/envoyproxy/envoy/blob/652a89b6a76e6a59521a46d764b2bd52317421a0/source/extensions/filters/network/thrift_proxy/router/router.h#L345-L356


tikv-ctl unsafe recover can lead to inconsistent replica list

Suppose region 1 has three replicas A, B and C, and A is leader. A adds a new replica D and then both A and D are corrupted, and B has applied the conf change while D has not. Using tikv-ctl will remove both A and D from B's local peer list and just remove A from C's. After B and C are started, C will apply the conf change add D to its list. So B's peer list becomes (B, C), and C's list is (B, C, D).
To get a consistent list, we need to skip mutating the list after an unsafe recovery. A simple way is maintain a tombstone store list on every node. When applying conf change, ignore the targets that locate on the store. Note that conf version should still be increased to reach the correct version.
/cc @disksing @hicqu

Stores could be only tombstone for some special regions, but still useful for other regions.
So, there are 2 question:

The list is for all regions, or for some special regions?
When will the list be clear?

Another way is to scan all the logs and mutate the id to a special value, which we should treat as no-op. It requires to update region peer list and logs atomically.

any update?

It's still under discussion.
I think the safest way for the problem is generating a snapshot from a node that has applied most up to date data, and restoring it on all other remaining node.
This approach is generic and work on many situation.

I have an idea for this problem: for each peer removed by tikv-ctl append one RemovePeer raft log on every peer of the region because every peer has these logs so they must commit and send to the apply worker. Also tikv-ctl remove peer from store's local peer list as before, and because there is at most one unapplied confchange, so at most one RemovePeer logs appended by tikv-ctl will success, others will result in a remove missing peer error log, for the epoch of these RemovePeer logs we can simply set to the same epoch { ver: exist_ver, conf_ver: exist_confver + 1 }.

because every peer has these logs so they must commit and send to the apply worker

So you mean propose a conf change after restarting all the remaining nodes?

because there is at most one unapplied confchange

No, it's only guaranteed that at most one uncommitted conf change.

So you mean propose a conf change after restarting all the remaining nodes
No, just append log (write to rocksdb) without propose when tikv-ctl remove peer.

No, it's only guaranteed that at most one uncommitted conf change.
I think the guaranteed is most one unapplied conf change.

No, just append log (write to rocksdb) without propose when the nodes are down.

How to guarantee safety? raft-rs can't distinguish difference of logs when they have the same term and index. So it's possible appending a log in followers can break consistency.

I think the guaranteed is most one unapplied conf change.

For example, if an isolated follower recover, it can receive multiple committed conf changes from leader and crash before applying.

I have a new idea. Instead of mutating the state manually, we rely on the log replication to handle changes correctly.
Let's introduce a FORCE_LEADER state. If a peer enters a FORCE_LEADER state, it will become leader immediately without counting majority votes. And all its logs will also be committed without replicating to majority. A node in FORCE_LEADER state will only accept new conf change proposals and EXIT_FORCE_LEADER proposal. After exiting FORCE_LEADER, it will need a new election to become leader again.
Because all fixing commands are proposed as logs, so all previous working logs will still being applied correctly. Fixing commands will also be replicated to other nodes and executing in the same order, so consistency is guaranteed in the end.
FORCE_LEADER state can be implemented as custom quorum function so that we can ensure logs will be replicated to all known working nodes.
PD should be the one to trigger FORCE_LEADER state transition. It can either broadcast failure node list to all alive nodes and let them triggering FORCE_LEADER state or send a command to control specific region. It's required that failure nodes should never be able to rejoin the cluster and should be physically stopped.

Let's introduce a FORCE_LEADER state. If a peer enters a FORCE_LEADER state, it will become leader immediately without counting majority votes. And all its logs will also be committed without replicating to majority. A node in FORCE_LEADER state will only accept new conf change proposals and EXIT_FORCE_LEADER proposal. After exiting FORCE_LEADER, it will need a new election to become leader again.

We may need mechanisms to ensure more things:

Only one alive peer enter FORCE_LEADER state, so conflict entries (same index with different term) won't be committed
The alive peer with the highest commit_index enter FORCE_LEADER state, so MsgAppend won't be rejected because log index lower than the receiver's commit_index


Overflow tab would not open cube properly.

I suggest updating the Help text at the top of the modal (if it is not already there) to mention support of copy/paste here.  Most users probably do not know they can copy/paste here.


Feat: add union type to nnc field

Description
Updating the nnc schema field to support objects of IPLD bytes. This is needed so we can send a nonce to Homestar to enable replays
Note: I haven't tested this yet, but it looks like zod supports union types in this format 🤷🏼
Link to sister PR
https://github.com/everywhere-computer/every-cli/pull/6
Type of change

[x] Refactor (non-breaking change that updates existing functionality)

i borked the signing. i'll clean this up shortly


improve test coverage

Now the test coverage is 70%, we must improve to 90% at lease.

This issue can be replaced by https://github.com/pingcap/pd/projects/4. Close it for now.


Logbook starts yesterday

Make sure you are running the latest version of Home Assistant before reporting an issue.
You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:
Home Assistant release (hass --version):
0.42.2 sorry yes it's still shows 0.42.2
Python release (python3 --version):
Python 3.4.2
Component/platform:
frontend
Description of problem:
When I open Logbook it starts with the day before today.
Expected:
Current day not past.

There's already an issue on this https://github.com/home-assistant/home-assistant/issues/7041
Please post there.


Need different coloring for "roman" messages

Should highlight in green the input value in "Unable to convert Roman numeral: 'x'", and in "Value X is out of range for conversion ..."

Actually, made the coloring consistent with other errors, which made the value yellow.


Feature Request - MP4 backgrounds

Summary of the new feature/enhancement
Currently, GIF animated backgrounds are supported. I'm not sure what other formats are - but mp4 would be great. I'm using a ~110MB gif and it uses ~10% CPU - the mp4 would be much smaller.

How about Twitch/Youtube integration?

👍

Have you tried it? I think it works.

Yes - it didnt. I can provide the mp4 if necessary

Oh - you weren’t really asking..?

No, I actually thought it was working!

The reason this won't work in the current implementation is that the backgroun pane image is set using Media::Imaging::BitmapImage which from system.windows.media.imaging.bitmapsource only supports image formats of:

Windows Presentation Foundation (WPF) natively supports compression and decompression of bitmap (BMP), Graphics Interchange Format (GIF), Joint Photographics Experts Group (JPEG), Portable Network Graphics (PNG), and Tagged Image File Format (TIFF) images.

Would webm be possible? The format would be better suited and MP4 converts over nicely.


Added label attribute to define whether or not using keys as column value

Using all the keys in first object of array to create the header for CSV file when csv-label set it to true.
It only accepts Boolean value.
ng-csv="dataArray" csv-label="true"
Input data:
$scopedataArray = [     {         "Vehicle": "BMW",         "Date": "30, Jul 2013 09:24 AM",         "Location": "Hauz Khas, Enclave, New Delhi, Delhi, India",         "Speed": 42     },     {         "Vehicle": "Honda CBR",         "Date": "30, Jul 2013 12:00 AM",         "Location": "Military Road,  West Bengal 734013,  India",         "Speed": 0     } ];
Output file:

Thank you!


Fix pasting html text not working in chrome (windows)

In chrome for windows, a paste event would look something like this:
"\n"Text here"\n"
When node.normalize was called, it would remove the html comments and
combine the leading trailing newlines with the text.
Then, when removeEmptyTextNodes was called, nothing would be removed
since the single text node did have content: \nText here\n
Because when we convert this plan text to paragraph tags, we only expect
one result back, so the first "paragraph" was an empty

 (the newline)
and the next paragraph, with the text we actually cared about, was
being discarded.
This simply removes empty nodes before normalizing, instead of after,
and that solves our problem.
https://app.bananastand.org/workspaces/1/tasks/5640638

@mogstad we do have two triage tasks waiting on this so if this looks ok to you it would be nice to merge :)

Without knowing anything about this, it seems pretty safe, but @mogstad please sign-off

This change seem pretty harmless, let’s try it out.


Is there a way to retrieve tape media inside the library?

I am looking for a way to retrieve a list of tape media inside the tape library and i cant seem to find anything in the documentation. Has anyone does this before?

Please open Commvault support ticket.


Grid Mode doesn't work

My grid Mode doesn't even activate ! is it just me ?

@Reiquem whats your OS and Browser version ?

Windows 10. I tried on chrome, mozilla firefox and opera gx

What steps do you take to activate it, context menu or a shortcut? What does happen — any console errors (opt-cmd-I on mac or ctrl-shift-I on windows)?

Closing as not enough info.


route.id and getRouteApi work inconsistently for routes with pathless parents

Describe the bug
If a route is a child of a pathless route, the pathless segment of it's path is included in its route.id. This makes it impossible to pass it as the to prop to <Navigate> or <Link>. Moreover, 'getRouteApi` also requires passing the full path, including the pathless segment.
Your Example Website or App
https://stackblitz.com/edit/github-puypjk-egbfth?file=src%2Fmain.tsx
Steps to Reproduce the Bug or Issue

Open the example link
See that <Link>, <Navigate> and getRouteApi error

Expected behavior
I expected to be able to

pass route.id to as to prop to <Navigate> and <Link> just like with routes without pathless parents
not have to specify the pathless segment of a route in getRouteApi

Screenshots or Videos
No response
Platform

OS: Windows
Browser: Chrome
Version 127.0.6533.119 (Official Build) (64-bit)

Additional context
No response

Route.id is not a valid navigation to option.

Route.fullPath is what'd you'd want to use when setting it on <Link> and navigate.

The string literal parameter accepted by the getRouteApi helper, expects the routeId to be its input. See docs.

Since it requires a valid routeId to be its input, the pathless/layout route segments do comprise that string.
If you've got the router-devtools, you can open the panel and confirm the routeId's value at runtime by viewing it in the tree.

Thanks a lot! I also noticed the Route.to field. Using it instead of Route.fullPath seems to result in the same outcome. Could you please clarify the difference and how to know which one of the two should be used?

Thanks a lot! I also noticed the Route.to field. Using it instead of Route.fullPath seems to result in the same outcome. Could you please clarify the difference and how to know which one of the two should be used?

ATM I don't quite remember why we introduced both. We've always pushed people to use Route.fullPath, so I'd stick with that for now.
If bundle size is a concern at all, I'd not go out of my way to import external Route configs into a file, and just stick with the string literals instead. Plus, you sometimes run the risk of having circular imports.