Fix logback warning

Fixes #5902

Codecov Report

Merging #5903 (937593e) into develop (37f8312) will decrease coverage by 0.03%.
The diff coverage is n/a.

@@              Coverage Diff              @@
##             develop    #5903      +/-   ##
=============================================
- Coverage      43.30%   43.28%   -0.03%
+ Complexity      8796     8792       -4
=============================================
  Files           1090     1090
  Lines          76412    76412
  Branches        9981     9981
=============================================
- Hits           33091    33073      -18
- Misses         39174    39185      +11
- Partials        4147     4154       +7

Impacted Files
Coverage Δ

...org/apache/rocketmq/common/stats/StatsItemSet.java
41.79% <0.00%> (-8.96%)
:arrow_down:

...tmq/remoting/protocol/body/ConsumerConnection.java
95.83% <0.00%> (-4.17%)
:arrow_down:

...he/rocketmq/controller/impl/DLedgerController.java
66.49% <0.00%> (-2.62%)
:arrow_down:

.../apache/rocketmq/controller/ControllerManager.java
71.87% <0.00%> (-2.09%)
:arrow_down:

...mq/client/impl/consumer/RebalanceLitePullImpl.java
69.86% <0.00%> (-1.37%)
:arrow_down:

...mq/store/ha/autoswitch/AutoSwitchHAConnection.java
70.00% <0.00%> (-1.36%)
:arrow_down:

...apache/rocketmq/store/ha/GroupTransferService.java
92.30% <0.00%> (-1.29%)
:arrow_down:

...he/rocketmq/client/trace/AsyncTraceDispatcher.java
83.65% <0.00%> (-0.49%)
:arrow_down:

...he/rocketmq/client/impl/consumer/ProcessQueue.java
59.91% <0.00%> (-0.45%)
:arrow_down:

...main/java/org/apache/rocketmq/store/CommitLog.java
65.13% <0.00%> (-0.11%)
:arrow_down:

... and 6 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

Here is still a warning that https://github.com/apache/rocketmq/issues/5904 need to address, but I will start an independent PR to fix it.


added suppport for MULTIPLE-physical-groups on one gmsh-entity

Hi @yuan-feng, thanks for the PR! It seems that one gmsh test is failing; that'll need to be fixed first. Also, make format to make the linter happy.

Closing for lack of response. Feel free to reopen at any time!


feature: detect fedora image and update filesystem

feature: detect fedora image and update filesystem
What does this PR do?

Detects if the base image is based upon fedora
If it is based on fedora, auto-select the filesystem

Screenshot / video of UI

https://github.com/containers/podman-desktop-extension-bootc/assets/6422176/4f82f815-85e9-4b51-91c0-bea27700dbd1
What issues does this PR fix or reference?

Closes https://github.com/containers/podman-desktop-extension-bootc/issues/457
How to test this PR?

Select a fedora bootc image or manifest, it will auto-select XFS.
If you select a non-fedora bootc image, it will be default.
Tests also cover new feature
Signed-off-by: Charlie Drage<EMAIL_ADDRESS>

@deboer-tim Updated with the changes (removed the debugging, updated the fedora detected description)


Beta branch

Updated pleco to 0.3.0. Big updates for pleco_engine as well.

Created a better RootMoveList structure for the engine. This allows for faster concurrent editing and access of the root moves of each thread without relying on blocking synchronization primitives.
Added the UCITimer, a timer specific to the UCI protocol. This is still a work in progress, but most of it is done.
More work on the UCI interface, specifically parsing stdin tokens.
Better documentation.

Coverage increased (+0.1%) to 83.48% when pulling dd3453440efe5e8f1d45a37a04754124e59163f8 on Beta-Branch into 83d4af9d217001542af10111c2289b44205caf1c on master.


WIP: allow popups to be resized

adds table to keep track of Borders associated to popups
adds function to resize a popup
relies on nvim-lua/plenary.nvim#180

Initial commit is a first attempt and probably needs looking through closely to make sure I haven't missed anything.

Do you need anything from me here? I am trying to catch up on (very delayed) reviews in popup and plenary.

I honestly can't remember where I was up to on this and the related PRs in plenary and telescope.
I think I stopped to see how things worked with your async stuff, and then I could make sure that the picker resizing in telescope worked well with it.

Closing in favour of plenary PR as popup functionality has moved to plenary


Add baRulho

Insert URLs to the project here:
https://github.com/maRce10/baRulho

[x] The projects is active, documented, open source licensed, shows usage from external parties and is directly targeting environmental sustainability. Find more details in the Contribution Guide.

All issues labeled as 'Good First Issue' of the project listed on OpenSustain.tech will be visible on ClimateTriage.com. This is a great way to welcome new community members to your project.

@maRce10


hosts.suse.tmpl.j2 is rendering incorrectly

The hosts.suse.tmpl.j2 file is rendering with a blank line at the top of file, this blank line is preventing the template from rendering its variables during cloud-init.
With the blank line, the rendered /etc/hosts still contains {{fqdn}} and {{hostname}}.
This ensures there's no leading blank line after the {% raw %} block start.
Also adds the nodes expected, isolated IP to the template.

/backport release/1.5

/backport lts/csm-1.5


Some hints are incorrect for non-lifted types

Some hints (like Use const or Avoid lambda suggesting to use .) don't work for non-lifted types, since const, ., etc. aren't levity/representation-polymorphic.
If my assumption that hlint doesn't have any type information is correct, this can't be fixed, but it should at least be added to the bugs and limitations list.

I agree. I think this justifies adding another type of Note.

Adding it to the bugs/limitations section seems fine as a bullet point in the readme. The problem with adding a note is I think it would occur in many many hints, and that makes it a lot less useful as a hint. Your assumption that HLint doesn't have any type information is correct.


Debian

This PR contains a Debian folder necessary for installing BGPalerter loosely following Debian guidelines, however there are some aspects of this package which may not be Debian compliment.  specifically we vendor in all node dependencies.
The packaged produced will:

create a bgpalerter use
install systemd file
install the binary to /usr/bin/bgpalert
install dependencies
install the example config files to /etc/bgpalerter/

Hi @b4ldr,
Thanks for this PR!
I'm listing below things that I see missing:

the new files need to be added to .npmignore, including the debian directory (this is a minor thing, I can take care of it);
documentation, we need to add an item in the list of ways BGPalerter can be installed;
clarification about the changelog file, what level of detail do we need? can we automate it and just update the release version from package.json and refer to the github releases page for the changelog?

Thanks!

@massimocandela
Sorry this fell of my radar

* the new files need to be added to .npmignore, including the debian directory (this is a minor thing, I can take care of it);

Done

* documentation, we need to add an item in the list of ways BGPalerter can be installed;

Added something can expand

* clarification about the changelog file, what level of detail do we need? can we automate it and just update the release version from package.json and refer to the github releases page for the changelog?

I think that the Debian change log is normally meant to indicate changes between the upstream package and the Debian package.  If theses are the same then yuo9 can just add something like
$package_name ($version-1) unstable; urgency=medium

  * New upstream version $version

 -- $author_name <$author_email>  $date

e.g.
node-bgpalerter (2.0.0-1) unstable; urgency=medium

  * New upstream version 2.0.0

 -- John Bond<EMAIL_ADDRESS>Fri, 14 Jan 2022 13:43:04 +0100

See the following example, not that most comments refer to changes under the debian directory

Hi John, thanks for your contribution. I cannot find the items you marked above as done. If you push in the debian branch they should appear here, but I cannot see new commits.

sorry should be there now

Hi @b4ldr, I merged this.
Thanks a lot for your contribution! Let me know if you would like me to add Wikimedia to the friends list.

Let me know if you would like me to add Wikimedia to the friends list.

please do, our puppet repo is public so its already public that we use it :)


Add support for failover connections

Hello,
I'm using your library (thank you) to connect to Amazon MQ (ActiveMQ) which has a failover protocol with multiple endpoints. It currently runs in Standby mode which means there is one instance running at a time, and when needed a standby instance pops up. It happens when AWS upgrades MQ versions for example.
Do you think it would be interesting to handle this failover mechanism?
What's usually implemented is to pass multiple urls in options, try one, and if it's down, try another one. rhea doesn't seem to handle failover protocol.

Hi @amangeot,
Failover is not supported at the moment, mostly because rhea itself does not support it.
We had the exact same setup in one of our projects, with that our solution was to have both the Active and Standby brokers be present in the same target group, have a load balancer pointed to said target group, and have a nice CNAME pointing to the LB, and this CNAME is what we use in the application it self.


use github.com/String-Latin/DIN-91379-Characters-and-Sequences

Is it possible to include https://github.com/String-Latin/DIN-91379-Characters-and-Sequences dynamically?
Or just add a link.

I actually wanted to do that but it wasn't that easily possible.
Problem: Even in the most detailed csv (https://github.com/String-Latin/DIN-91379-Characters-and-Sequences/blob/main/latin_list_search_form_1.3.txt) there is less structured information than what we have in https://github.com/it-at-m/UnicodeEingabeKiwi2/blob/main/public/model/stringlatin-v2.xml.
E.g. the information about the "base char" (which we use for searching the corresponding variants), if it's a capital letter and we currently have some special characters which are not officially in the norm but useful nontheless.
It might be possible to make a contribution to their repo and then include a small csv to xml-parser in our build-process.


Support for WKWebView in HTML blocks.

Note: Does not actually enable said support while I investigate a web
content issue related to viewports.
See: https://openedx.atlassian.net/browse/MA-960
JIRA: https://openedx.atlassian.net/browse/MA-790

@mikekatz please review

👍


arma3server -port command line setting

After getting the -mod setting working, I started (tried) moving my other ARMA 3 instances over to linuxgsm for exclusive control. However, I've run into a big problem with how the port settings are configured.
Since the 1.22 build, ARMA 3 port settings have been moved exclusively to the command line port setting. This was removed in update #251, but it has to be added back.

STEAM ports in Arma 3 build 1.22.125469 or newer are hardcoded as now linked to game-port of the server instance (+1 query +2 report to master)

I understand this creates a lot of issues with how the monitoring works and currently limits port usage to the default ports only.
I am going to start working on the issue, so that linuxgsm supports multiple instances on a single server. It may make sense to try and integrate the #270 suggestions into these changes, but first thing first - the port setting, then monitoring, then hopefully the enhancements.

Thanks for this I will move this over. SOon


:fire: chore: Remove unimplemented volar packages

Description
We can get most of the LSP support without migrating to volar so deprioritize for now
Testing
Explain the quality checks that have been done on the code changes
Additional Information

[ ] I read the contributing docs (if this is your first contribution)

Your ENS/address:

Current dependencies on/for this PR:

main

PR #445   👈

This comment was auto-generated by Graphite.


Quick formatting support for groups of concepts.

fixed partially in #42

the next step will be to have some UI controls to use the mouse for this.


Copy-to with key links to original rather than to copy

Expected Behavior
If I have these key definitions:
<topicref href="alsocopykey.dita" keys="also1"/>
<topicref href="alsocopykey.dita" copy-to="alsocopykey-newname.dita" keys="also2"/>

Key references to also1 should resolve to alsocopykey.dita, while key references to also2 should resolve to the copied version, alsocopykey-newname.dita.
Actual Behavior
Key references to both also1 and also2 resolve to the original topic, alsocopykey.dita. When I generate HTML5, two topics are generated but all links are to the original; when I generate PDF, the topic appears twice but all links are to the original.
I also have a reference that appears only with copy-to, and is never referenced without the copy-to:
<topicref href="onlycopykey.dita" copy-to="onlycopykey-newname.dita" keys="only"/>
For that case, the HTML5 build generates both onlycopykey.html and onlycopykey-newname.html, but all uses of keyref="only" resolve to the original name. In the PDF, <xref keyref="only"/> results in blue text but no link, because the original file onlycopykey.dita is not in the PDF to provide a link destination.
Possible Solution
When the keyref value is resolved for key definitions that set @copy-to, the link should go to the copy specified in @copy-to. At this point don't yet know if that change is simple or would require a giant architectural change.
Steps to Reproduce
Sample map includes both variants described above. Tested with DITA-OT 3.0 and 2.5.
copykey.zip
This is related to #2841 (and is probably the preferred way to get the same result). Not sure if this overlaps #2826 at all, as my sample doesn't use branch filtering but does have a key that resolves to copy-to value.

Chatting further with @jelovirt about this as I tried to think through a solution. It felt like resolving @copy-to very early and updating @href to the new value -- before resolving keys -- would fix the problem, because at that point you resolve to the right target. But resolving @copy-to before keys is not possible if you also allow this markup:
<topicref keyref="a" copy-to="b.dita"/>

Fixed with #2935


Avoid circular imports in grid package

Avoid importing InlineGrid into utils.dev.js which results in circular import chain. The only purpose is of the import is to do a type check. A simpler approach is to compare  child.type.name. against a whitelist registry of allowed nested components instead of comparing react functions.

Coverage increased (+0.03%) to 81.98% when pulling dbfc95bae03bdc5187585a9dc8f43f9aad13454c on jarlef:circular-import-fix into 0330afd931af2ac99e3b73b4b9f1128f8830927f on SpareBank1:develop.


Add rotation option

It would be nice to have option to display text in portrait mode as well as landscape- this would allow more lines (but obviously less characters on each).

Sounds like a useful option. I will implement it after my exams(about 2 weeks). I will also implement a way to use the new json functions. This way, a free design, not constrained by any predefined services should be possible

I think now that the drawcustom service exists, this is not necessary anymore.


uucore: leading zeros are ignored in version compare

should fix tests/misc/sort-version.sh

Have you seen the previous discussion on this? In particular this thread: https://github.com/uutils/coreutils/pull/4325

@tertsdiepraam Ah, i totally missed that. thanks for pointing it out.
I was using this as a reference for the non-stable sorting. And i guess stable sorting just preserves the relative order in case when the values are equal?

Indeed. I'm not sure how intentional that is on GNU's side. We could start a discussion there too, because it is (in my opinion) a bit strange.

they do specify --stable here. Would make sense if they wanted something deterministic.

Interesting, I hadn't seen that sentence. That makes sense if it's about the last resort comparison. We shoud do the same then!

@tertsdiepraam should be ready for review

This does not fix the issue for both stable and unstable does it? I would imagine that version_cmp needs to stake a stable flag that defines the behaviour. Or do you think it should he fixed in some other way?

In my opinion, the comparison function should return Cmp::Ordering::Equals if they are equal. And the Caller should handle the equal case as it is done here
And i believe this pr fixes both stable and unstable case

Returning equal does make sense. How does this sovle both cases, though?

I can't find anything on how ls breaks ties. Nothing will necessarily be 'broken' because it would still sort correctly in a non-deterministic way which makes sense because ls doesn't do last resort comparison as you said.
If we wanted to provide our own rules, and make ls behave similar to sort, that would be a reasonable approach too.

Yeah not really broken, but it would be something we might need to fix. That could just mean that we need to open an issue, but we do need to know. Could you do some testing with ls with GNU and uutils before and after this patch?

I did some manual testing and looks like GNU's ls also behaves like sort when breaking ties.

Thanks :)
Still an improvement over the previous state :)


fix(DDI-880): Fix the modal focus jumping out when tab key is pressed

:tada: This PR is included in version 4.0.0-alpha.25 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0-alpha.82 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0-alpha.15 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 2.0.0-alpha.6 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 2.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 4.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Set the default startup project

Summary of the Pull Request
Visual Studio defaults the startup project to the first project listed in the solution. Set the default to CascadiaPackage, which launches the packaged terminal. This required moving both its solution folder and the project itself to the top of the solution.
The other moves in the file is VS "fixing" the ordering based on the move. This prevents the solution from being automatically changed by VS when other folks open it.
Validation Steps Performed

Opened solution with Visual Studio 2017 and Visual Studio 2019 on a clean enlistment (.vs deleted) and verified that CascadiaPackage project was the default.

The code change itself I'm fine with, but the real question I have for the rest of the team is is this something we want?

I don’t like that it’s magic. Perhaps we should bug the VS folks about why it is magic?

I'm one of the "VS" folks, and it's just picking the first debuggable project in the solution.
Today without this change, a new contributor opens the solution, presses F5 and the debugger complains the project is not debuggable.
After this change, a new contributor opens the solution, presses F5 and the debugger deploys and launches Terminal.

It's current configurable, but it's a per user setting (stored in the not committed .vs folder). It's definitely a reasonable suggestion to have it configured and stored in the solution itself.

@miniksa @adiviness can you merge this in? I don't have rights to.


Fix Antrea Octant plugin build

The plugin had 2 conflicting indirect Go dependencies:

github.com/googleapis/gnostic
github.com/google/gnostic

Having these 2 dependencies caused the same .proto file to be registered
twice, and caused the antrea-octant-plugin binary to panic on start.
github.com/googleapis/gnostic is the old module name, while
github.com/google/gnostic is the new one.
New K8s versions (e.g., v1.24 which is used by Antrea) depend on
github.com/google/gnostic, while older versions (e.g., v1.21 which is
used by Octant) depend on github.com/googleapis/gnostic. To resolve this
issue (at least temporarily), we ensure that only K8s v1.21 libraries
are used to build the plugin, and we eliminate the
github.com/google/gnostic dependency. This is achieved by adding a few
missing replace directives.
Fixes #4083
Signed-off-by: Antonin Bas<EMAIL_ADDRESS>

@tnqn this should be merged for the v1.8 release (and also backported to v1.7).

/skip-all


feat(decorators): honor flags in CustomField decorator

Just started reviewing :)

:tada: This PR is included in version 2.20.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 3.0.0-beta.8 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


refactor!: Calltree to be generic

What I did
When a non-EVM chain wishes to display traces, ape core should be able to accept a generic call tree. This PR makes a generic interface for call tree models.
fixes: ape-62
evm-trace will have to be released before this PR and the setup.py updated to reflect.
https://github.com/ApeWorX/evm-trace/pull/16
How I did it

How to verify it

Checklist

[ ] All changes are completed
[ ] New test cases have been added
[ ] Documentation has been updated

Failing test based on structure before evm-trace changes are released. However, this all works locally.

Thinking out loud here: My original interface ideas for ape core was to make it so printing a tree was just a method you could call, and however EcosystemAPI/ProviderAPI managed it under the hood would make it work.

Your original idea also includes that it must use the original display from evm-trace when it is unable to properly decode the contract data. That is the tricky part and why the design is like this - needs to reference the original display abilities on a line by line basis.

Requires this PR: https://github.com/ApeWorX/evm-trace/pull/17

Closing this ticket in favor of a SPIKE on refactoring tracing into ecosystems and pulling the logic up to a higher abstraction.


The Link component doesn't generate hashed links with hash history.

Describe the bug
when creating my app with hash history instead of browser history I would expect a rendered Link component to href to #/about for example but instead see it render href to /about.
Interestingly when I click on it it does render and set my browser location to #/about, so something seems to be correcting it post-click, but if I right-click to open in a new tab on that same link it opens at the /about href URL and breaks the hash route.
My router setup is basically the canonical tan router example app with hash history swapped in:
  const history = createHashHistory();
  const router = createReactRouter({ routeConfig, history })

This looks to be similar to (the same as?) https://github.com/TanStack/location/issues/300 but I am indeed running the latest version of tanstack router.
Your Example Website or App
https://stackblitz.com/edit/github-jssymk?file=src/main.tsx
Steps to Reproduce the Bug or Issue

Visit a page with a Link component.
Hover over link and note the URL it directs to.
Right click the link and open to a new tab, noting the browsers location.
click the link and not the the browsers location.

Expected behavior
At step 2 of reproduction I would expect step to to show a hashed url, for eg <Link to="/about"> should yield #/about but instead I see /about.
At step 3 of reproduction I would expect the tab to open at #/about, but instead it opens at /about.
At step 4 of reproduction I expect the browser location to reflect the broken not-hashed url but weirdly it shows the correct hashed URL.
Screenshots or Videos

Platform

OS: Linux
Browser: observed on Chrome and Firefox, likely the same on other browsers
Version: 0.0.1-beta.38

Additional context
No response

To add to this report:

I have this issue when using Github Pages with React Location. Github pages does not allow rerouting traffic to the index.html, so the hashurls are the only way to go (or some obscure 404.html workaround).
This issue gets more confusing once your deployed code is accessed in a sub-directory like GH Pages often is (eg https://osmberlin.github.io/osm-tag-updater/)
I worked around this issue for one link at https://github.com/osmberlin/osm-tag-updater/commit/9a18f40fef3cced7317d7345eb6aa0b3e83d8262#diff-59e03d506cb04167415dc0dc03fa3d4e803c88d666f29b2773579d9dbbed87ffR48-R55 by using navigate together with to which does feel hacky
That workaround breaks shift+click (new window) and option+click (new tab). The only way to open a new tab/window is via the right mouseclick menu. Therefore …

A good test case for a fix would be…

works with shift+click (new window)
works with cmd+click (new tab)
works with context menu "open in new tab"
works with context menu "open in new window"

I looked over onClick handler and it seems that ctrl-click is treated differently. In fact handleClick all it does is use navigate().
https://github.com/TanStack/router/blob/0575b2fca45e9aa73b1922b4d6b99a38e7218e66/packages/router-core/src/router.ts#L1322

@mfaradzheva-hubble the issue occurs before onclick fires.
at the point that the link is rendered onto the page, but before a click event, it is already wrong, you can see this when you hover the link.
In my screenshot you can see it as localhost:3001/about before it is clicked, when it should show as localhost:3001/#/about if it were generated correctly.

A good test case for a fix would be…
* works with shift+click (new window)

* works with cmd+click (new tab)

* works with context menu "open in new tab"

* works with context menu "open in new window"

Also add middle-clicking on a link to that list, that doesn't work either right now (probably gets fixed alongside with the context-menu fixes as those probably work the same in the browser)

I can also confirm that this still is an issue for me on v1.4.6 (the latest at the time of writing this)

If the team needs a minimal reproducible example... this was with v1.5.4
https://stackblitz.com/edit/stackblitz-starters-m1udae?file=src%2Findex.tsx

I still think it's this line of code that prevents the use of hash.
https://github.com/TanStack/router/blob/0575b2fca45e9aa73b1922b4d6b99a38e7218e66/packages/router-core/src/router.ts#L1325
`const handleClick = (e: MouseEvent) => {
if (
!disabled &&
!isCtrlEvent(e) &&
!e.defaultPrevented &&
(!target || target === '_self') &&
e.button === 0
) {
e.preventDefault()
if (pathIsEqual && !search && !hash) {
router.invalidateRoute(nextOpts)
}
      // All is well? Navigate!
      **navigate(nextOpts)**
    }
  }`

function isCtrlEvent(e: MouseEvent) {   return !!(e.metaKey || e.altKey || e.ctrlKey || e.shiftKey) }
I might be wrong. I don't have time to set environment up to test it. But by reading the code it seems like the issue.

a tag had the correct href attribute in the DOM somewhere before this commit
reverting the change in packages/react-router/src/router.ts to href: this.history.createHref(${pathname}${searchStr}${hashStr}`)` seems to cause other issues when the href is parsed again.

I have fixed it temporarily for myself using the following patch. It works for me because I know I will always use the hash router. But it may not be suitable for others.
diff --git a/dist/esm/link.js b/dist/esm/link.js
index b9b64766dabec3ac2fd505fedfddd330c6eccd35..fee51513e8d6cf147712f7223a51da785d49a184 100644
--- a/dist/esm/link.js
+++ b/dist/esm/link.js
@@ -143,7 +143,7 @@ function useLinkProps(options) {
     ...resolvedActiveProps,
     ...resolvedInactiveProps,
     ...rest,
-    href: disabled ? void 0 : next.maskedLocation ? next.maskedLocation.href : next.href,
+    href: '#'+(disabled ? void 0 : next.maskedLocation ? next.maskedLocation.href : next.href),
     onClick: composeHandlers([onClick, handleClick]),
     onFocus: composeHandlers([onFocus, handleFocus]),
     onMouseEnter: composeHandlers([onMouseEnter, handleEnter]),

@pSnehanshu perhaps you should wrap it in history.createHref 🤔

This has been fixed and released. You can get these changes on version 1.26.4.


Jokes Chrome Extension added

issue #216

@sejalc22 Thank you for your contribution. Looking forward to more such amazing contributions 🥂


Explore / filter by recent broken

In Explore tab, clicking filter by recent breaks down the page (no table or options shown anymore).
Also, maybe make recent the default filter? To make it immediately useful as a history.

Fixed in the next push. Not sure for recent as a default filter, since when you begin it is empty so not very explicit for the page ...


Constant name "all_gists" doesn't conform to UPPER_CASE naming style

https://github.com/lbonanomi/gRist/blob/27e8bad1df8ab5380e5a67697cb91b06aafed42d/grist.py#L217

Issues for naming style are now ignored.


[US] Signup flow

As an application user, I want to create an account so that I can log in to the platform afterward.

MoSCoW
Risk
Story Points

Must have
Medium
3

Acceptance Criteria

Administrator must have “registered” a user prior to its signup from the User Management view
The login view now accepts email accounts which have been “registered” but not created entirely
In which case, a user signup flow is presented to the user, containing fields to enter:

First Name
Last Name
Password: 12 characters with 1 uppercase, 1 lowercase, 1 special symbol
Password Confirmation

Validation on those fields is executed
Upon signup, login is executed

Risks

Manipulation of sensitive information
Access right management
Uncertainties

Pre-requisites

[ ] Meet with the stakeholder to clarify the requirements
[ ] Complete the requirements of this US
[ ] Read over carefully the User Management & Authentication proposal (see #89)

Tasks

[ ] Integrate verification of “registered” yet not fully created accounts from the front-end
[ ] Edit the login view to integrate the signup flow
[ ] Integrate the frontend signup with the corresponding database function via the API

Dependencies
#139
Notes
This story is a drop-off candidate for Iteration 8.

Demo Video
https://github.com/WillTrem/UInnovate/assets/64431699/12b36b61-3e67-4f82-adf6-14b70c9bb75d

Looks good!
Signing off!


[JavaScript] Serialize any type

remove the limit: root type must be an object

I have refactored the code generator in another pr #1313 , which had been remove the limit.


Newer Version: FujiApple.Trippy 0.8.0

Holding off merged due to Winget v1.5 and higher version is not yet released. Converting to draft.

Microsoft Reviewers: Open in CodeFlow

Do you know what happens to this pull request?

What the pull request gives me Validation-Executable-Error?

This package is expecting arguments:
error: the following required arguments were not provided:
  <TARGETS>...

Usage: trip.exe <TARGETS>...

For more information, try '--help'.

What the pull request gives me Validation-Executable-Error?

It can't tell if the program launched successfully or not. So a human reviews.

@mdanish-kh Do you know when the newer version winget-cli will release?

I'm not an MS employee so I can't say exactly but I recall it being mentioned that it's targeted for the end of this month.

Marking pull request is ready to review.

@stephengillie

@wingetbot waivers Add Validation-Executable-Error

Hmm, what the pipeline is happening.

/azp run

/azp run


openstack: fix project-scoped with project name

Fix openstack project-scoped with project name token authentication
Description
The project-scoped with project name should include
project domain id instead user domain name in scope
section according to current openstack API, example:
{
    "auth": {
        "identity": {
            "methods": [
                "password"
            ],
            "password": {
                "user": {
                    "id": "ee4dfb6e5540447cb3741905149d9b6e",
                    "password": "devstacker"
                }
            }
        },
        "scope": {
            "project": {
                "domain": {
                    "id": "default"
                },
                "name": "admin"
            }
        }
    }
}

Status
work in progress
Checklist (tick everything that applies)

[ ] Code linting (required, can be done after the PR checks)
[ ] Documentation
[ ] Tests
[ ] ICLA (required for bigger changes)

Codecov Report

Merging #1367 into trunk will increase coverage by <.01%.
The diff coverage is 80%.

@@            Coverage Diff             @@
##            trunk    #1367      +/-   ##
==========================================
+ Coverage   86.34%   86.34%   +<.01%
==========================================
  Files         372      372
  Lines       76156    76161       +5
  Branches     6971     6972       +1
==========================================
+ Hits        65755    65761       +6
+ Misses       7605     7604       -1
  Partials     2796     2796

Impacted Files
Coverage Δ

libcloud/test/common/test_openstack_identity.py
98.07% <ø> (ø)
:arrow_up:

libcloud/common/openstack_identity.py
77.15% <100%> (+0.03%)
:arrow_up:

libcloud/common/openstack.py
83.24% <75%> (-0.18%)
:arrow_down:

libcloud/test/compute/test_upcloud.py
91.39% <0%> (+1.32%)
:arrow_up:

Continue to review full report at Codecov.

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

Thanks for the contribution.
This looks reasonable.
Should we fall back to including name in the request if id is not specified (aka for backward compatibility reasons or similar)?

Should we fall back to including name in the request if id is not specified (aka for backward compatibility reasons or similar)?
Which name? The project name is left, this patch is fixing a mistake where user "domain name" was used in place of project "domain name", I don't believe this code ever worked. Btw, using both project domain name and project domain id at a same time does not work for me.

Hm, small correction, one can use both project domain name and project domain id at a time, or any of them according to openstack keystone/auth/schema.py file:
        'scope': {
.
.
.
            'type': ['object', 'string'],
            'properties': {
                'project': {
                    'type': 'object',
                    'properties': {
                        'name': {'type': 'string', },
                        'id': {'type': 'string', },
                        'domain': {
                            'type': 'object',
                            'properties': {
                                'id': {'type': 'string', },
                                'name': {'type': 'string', },
                            },
                        },
                    },
                },

and later
    if scope is not None and isinstance(scope, dict):
        project = scope.get('project')
        if project is not None:
            if 'id' not in project and 'name' not in project:
                msg = _(
                    'Invalid input for field scope/project: '
                    'id or name must be present.')
                raise exception.SchemaValidationError(detail=msg)
            domain = project.get('domain')
            if domain is not None:
                if 'id' not in domain and 'name' not in domain:
                    msg = _(
                        'Invalid input for field scope/project/domain: '
                        'id or name must be present.')
                    raise exception.SchemaValidationError(detail=msg)

Nevertheless there is no ex_ parameter for project domain name in libcloud.
And as I said earlier authentication user domain name should have never been used as project domain name.

@Kami could you please advise what should I do next to proceed with PR?

@kshtsk Thanks for the clarification.
I will look at it (and try to test it) and if everything looks OK, merge it into trunk.

Merged into trunk.
Thanks for the contribution :+1:

@Kami could we get a new release on pypi with this fix soon, please? that would make our life easier :)

@toabctl There is no currently no ETA for the next release yet (might take some time since there are some other larger changes in trunk and some other larger changes still need to land), but in the mean time you can use version from git "git+https://github.com/apache/libcloud.git@trunk@egg=apache-libcloud".


Consider using ECO codes in match_type?

https://www.ebi.ac.uk/ols/ontologies/eco

For now, we will go with a curated specialised set:
https://github.com/mapping-commons/semantic-mapping-vocabulary
which we could consider linking to ECO codes in the future.


How to use aider-helm

Love your work, thank you
But I don't understand how I can activate aider-helm.
The file in repo said I have to add it manually, what does that mean?

Oh I use this command: (load-file "aider-helm.el")
The helm history and fuzz match is useful to me, cause it is possible that I reuse my old prompt. I also try to let the project not depend on helm, cause not everyone use that.
Yes agree that maybe the command to load that .el should be improved. Let me know if you have some suggestion to improve the way to load that, and we can update the README.org for it.

Just merged a PR given aider's suggestion on this problem. Let me know if this way works. Thanks: https://github.com/tninja/aider.el?tab=readme-ov-file#optional-helm-support


Testing CI (#1735)

Testing CI

Disable tests for Pillow 7

Merged in https://github.com/pytorch/vision/commit/90f5aac1fe8f3da55cc8c316033419fad9272d7f


sync with 0.6.0

Sync with v0.6.0

@maxdebayser I created this branch off a two weeks old main. I rebased this on the latest main on this fork.

/lgtm


Update documentation about constructors for the v3 migration guide

I am using version 3.0.0-alpha02 in a Kotlin project.
I found that the class mentioned in the documentation, DefaultHttpNetworkTransport, did not exist, but after some fiddling around I pieced something together that seems to work. Please correct me if this is not what you intended.
Other than this, the migration to v3 was pretty smooth. Many thanks for the Kotlin support!
Offtopic for this PR:
One other minor confusion was about the @optional directive, I first thought that you wanted to replace nullability by the Optional class just as some other programming languages do, so I replaced all nullable variables in my query by Optional parameters.
But then I found that it didn't work because graphql will still attempt to pass null values for some reason (not in my code, I got it back as an error in the query result so no stacktrace. Maybe on the side of the GitHub api?).
So I keep my query as query MyQuery($nonNullable: String!, $nullable: String). I think the documentation just meant to speak about a situation where you really have optional parameters that are there or are not there (not sure when that would arise).
If I misunderstood the intention, I would appreciate if you let me know.

@PHPirates: Thank you for submitting a pull request! Before we can merge it, you'll need to sign the Apollo Contributor License Agreement here: https://contribute.apollographql.com/

Many thanks for the documentation fix 🙏.
About optional and/or nullable GraphQL variables, this is indeed super confusing. The GraphQL type system doesn't have optional types, only nullable. But there are cases where it is important to distinguish. For an example, in input types.
If you're coming from 2.x, the main change to remember is that Input is renamed to Optional.
The other change is that nullable GraphQL variables will be non-optional Kotlin properties by default (yea, I know this is a mouthful...)
For your query:
query TotalIssues($repository: String!, $owner: String!, $issuesCursor: String, $pullRequestsCursor: String, $issues: Int!) {

That should generate something like:
class TotalIssues(
  val repository: String,
  val owner: String,
  val issueCursor: String?, // Note how this is not `Optional<String?>`
  val pullRequestsCursor: String?, // Note how this is not `Optional<String?>`
  val issues: Int
)

If you want to be able to omit issueCursor (in order to use the schema defaultValue), you can declare the variable optional ($issuesCursor: String @optional), which will generate val issuesCursor: Optional<String?>.
The rationale was that in most cases, variables are meant to be present (else they wouldn't be added in the first place)
I hope that makes sense? Would you have preferred the other logic instead?

The GraphQL type system doesn't have optional types, only nullable.

Aha, I didn't know that, because of my lack of GraphQL knowledge I was assuming the contrary based on the apollo docs and that's probably what got me confused.
Yes, it is clear now, thanks!

👍👍 that'd certainly be a nice blog post along the way...


[RFC] add cli flag to analyze client bundle

Adds --analyze-client-bundle cli flag to build command.
Using it will add webpack-bundle-analyzer allowing teams to, well, analyze their bundles.
I picked the name analyze-client-bundle to allow to potentially add analyze-server-bundle at a later point. Imo there will never be more than two kinds of bundles to analyze so I considered two bools better and easier than using an enum.
Currently no options are passed to  the webpack-bundle-analyzer, which causes a server to be started and the analyzer page to be opened automatically.
I'm not sure what's best here. We could also configure it to write an .html file somewhere that users can open themselves. This would allow to add more stuff to the analyze-client-bundle flag, but would also come with less convenience.
What do you say? Do we want such a feature at all? And in what configuration?

I was wondering whether it was more appropriate associating --analyze-client-bundle to the start command, instead of build. Any idea?
Beside that, staring at my bundles was always a very teaching activity in my experience and I would definitely provide this flag as a dev tool.

If we shipped it as a part of the main hops package it means that we'd need a major hops release to extract it to a standalone package, right?

I don't think so, as it does not bring any public api.
We could introduce a new package and add this as dependency to the hops main package without any issues and breaking changes.

I was wondering whether it was more appropriate associating --analyze-client-bundle to the start command, instead of build. Any idea?

build seemed to be perfectly suitable to me.
Also, to get the production bundle info you'd have to use start -p which also causes a serve -p which often does not run out of the box on local machines. (missing dev proxy and env vars etc.)

👍 From my point of view we can merge it. The feature would also probably benefit from a few lines of documentation. I will take care of it.

I think it's a good idea to provide easier access to the analysis of the build artifact.
But I'm not really happy with the solution. It feels like this belongs into its own package, that adds a analyze-client-bundle-command to the Hops CLI, provides sane defaults (I'm not a friend of automatically opening the browser from within the terminal … 🤷♂) and takes (and passes on) the options of the plugin.
I would also not include this into the main Hops package right from the beginning. But rather get a feel for how people are using it.

I don't have much of an issue with putting into into its own package (although imo it's not warranted yet).
However, I'd not create a new command. In its current build you can analyze any build you want. -p -s whatever. It just works.
If we add a new command we'd have to duplicate all the build command flags.
Passing the other flags along to the plug-in only makes sense if never want to add anything else to this analyze flag/command than this very plugin.
I'm fine with not starting the server / opening the browser.

Separate bundle or not? I'd really like to see some analysing tools integrated in Hops.
Any further idea about it @ZauberNerd and @dmbch?

I picked the name analyze-client-bundle to allow to potentially add analyze-server-bundle at a later point. Imo there will never be more than two kinds of bundles to analyze so I considered two bools better and easier than using an enum.

That's not entirely true, we already have more bundles than that, for example the service worker ;)

Currently no options are passed to the webpack-bundle-analyzer, which causes a server to be started and the analyzer page to be opened automatically.
I'm not sure what's best here. We could also configure it to write an .html file somewhere that users can open themselves. This would allow to add more stuff to the analyze-client-bundle flag, but would also come with less convenience.

I'd prefer it to not open a browser automatically, since we don't do that with our server too.
I'm unsure about server vs static files - with static files we could write all reports at the same time and users could just pick which one to open. When we use the server, we can only analyze the results of one compiler (node, build, service worker, etc), but it feels simpler to just point the users to a url instead of presenting them with a file path.
I mean we could also set the log level of this plugin very high and print our own message about where to find and how to open the report, for example by printing a file:// url, we could have a url in the terminal that's actually clickable instead of just a file path, right?

What do you say? Do we want such a feature at all? And in what configuration?

:+1: :heart:

Separate bundle or not? I'd really like to see some analysing tools integrated in Hops.
Any further idea about it @ZauberNerd and @dmbch?

I don't mind it being in the main hops package.

Thanks everyone for pursuing this PR!
I'm just not really sure if pushing onto somebody else's PR without giving them a chance to do it themselves first is a common and good practice.
I personally don't mind in this case, just wanted to leave my concerns for future contributions.
Have a great day!

Thank's @robin-drexler!
We all attribute great importance to intellectual property and open source best practices at Xing.
I decided to directly operate on the branch you opened only because we're both member of the same team at Xing and it was the easier way to ship this feature to our users.
Any other external contribution we'll be welcomed with full-open source honours! 😄


Feature dissolve extra aggregations

Closes #3

Codecov Report

:exclamation: No coverage uploaded for pull request base (feature_dissolve_extra_aggregations@66c85a2). Click here to learn what that means.
The diff coverage is n/a.

:exclamation: Current head ae17465 differs from pull request most recent head ff27fa9. Consider uploading reports for the commit ff27fa9 to get more accurate results

@@                          Coverage Diff                           @@
##             feature_dissolve_extra_aggregations      #61   +/-   ##
======================================================================
  Coverage                                       ?   83.14%
======================================================================
  Files                                          ?       16
  Lines                                          ?     2540
  Branches                                       ?        0
======================================================================
  Hits                                           ?     2112
  Misses                                         ?      428
  Partials                                       ?        0

Continue to review full report at Codecov.

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


the method are in doubt

Thank you for your method. I repeated this method and used it for entity and relationship prediction. I found that the effect was not even as good as directly fine-tuning the model. What is the reason for this

Hello, how do you apply this method for entity/relation predition? As entity/relation prediction are ranking tasks, the design of the our prompt may not be suitable for the task and it's a valuable future direction.

I just did a simple experiment, made simple changes to the prompts and masked the entities and the embedding ids in our input to make LLM predict. The effect was not even as good as fine-tuning without prefix, I can't figure out why this is😢

Well, I think how to employ KoPA for link prediction task should be further considered. We did not explore this problem in our paper yet. It will be a good topic for the future research


Build / copy / adapt session (dynamic with query args) frontend to work with opentera-teleop-service signaling-server.

The generated project must be copied to signaling-static folder of the signaling-server, integrated to the opentera-teleop-service.

[x] Teleoperation with a virtual joystick or keyboard.
[x] Manage "rooms" to optimize bandwidth.
[ ] Allow invitation of "guests".
[x] Allow display of the robot's status (batteries, state, etc.)

See #14 for more details

Still missing invitation of guests.


Updates to MOI 0.4

Would be nice to get a tagged version of MOIMosek supporting MOI v0.4 before the JuMP-dev workshop.
This PR should contain all necessary updates

@ulfworsoe I am merging and tagging to make sure we get a tagged release accepted by METADATA before the start of the JuMP-dev workshop

Excellent, and thank you!


Not Appearing Act

Form items don't appear/select if you follow this specific pattern.

Go into Assembly Service
Click folder icon next to read file 1
Select a file (I used /public/PATRIC Workshop/Assembly/SRR3584989_1.fastq)
Reset the form
Click folder icon next to read file 1
Select the same file
It doesn't appear

This seems to happen on the Metagenomic binning service as well.  It may exist in multiple services.

@Tinyman392 sorry, we have not fixed it this one and it's related to the 2 issues you reported earlier: #2142 #2247
I will give this high priority when i'm back from my trip on 06/17. @nconrad please take a look if you have some bandwidth as this might come back and bite us next week in the wokrshop.

@Tinyman392 just wanted to let you know that we are not forgetting these issues. in fact, @nconrad and I looked at them together and we think these are related issues. we narrowed the area of focus, but we do not have a fix yet.


Update metric_sources.md

🚀 Deployed on https://659de2a189a08678a3d9ab49--cozy-fox-0defec.netlify.app


Make shortcuts in the Editor to be the same as the ones in the IPython console

Description of your problem
If I do Ctrl+D on my Mac in the Spyder editor window, I expect this to act like "Delete" on a PC and delete one character to the right of the cursor, or delete text I have highlighted. Instead, if I have not highlighted any text, it deletes the whole word to the right of the cursor. If I have highlighted text from left to right, it deletes the word to the right of the highlighted section. (If I have highlighted text from right to left, it deletes the highlighted text as expected. Ctrl+D also works as expected in the ipython console.)
What steps will reproduce the problem?

Place cursor in text in the Spyder editor.
Type Ctrl+D.

What is the expected output? What do you see instead?
Described above.
Please provide any additional information below
Versions and main components

Spyder Version: 3.0.1
Python Version: 2.7.11
Operating system: Mac OS El Capitan 10.11.6

Dependencies
Please go to the menu entry Help > Optional Dependencies (or
Help > Dependencies), press the button Copy to clipboard
and paste the contents below:
jedi >=0.8.1     :  0.9.0 (OK)
matplotlib >=1.0 :  1.4.3 (OK)
nbconvert >=4.0  :  4.1.0 (OK)
numpy >=1.7      :  1.10.4 (OK)
pandas >=0.13.1  :  0.18.0 (OK)
pep8 >=0.6       :  1.7.0 (OK)
psutil >=0.3     :  4.1.0 (OK)
pyflakes >=0.5.0 :  1.1.0 (OK)
pygments >=2.0   :  2.1.1 (OK)
pylint >=0.25    :  1.5.4 (OK)
qtconsole >=4.2.0:  4.2.0 (OK)
rope >=0.9.4     :  0.9.4 (OK)
sphinx >=0.6.6   :  1.3.5 (OK)
sympy >=0.7.3    :  <IP_ADDRESS> (OK)

Ctrl+D is assigned in Spyder to delete a line in Windows/Linux. The equivalent command in Mac is Cmd+D.

Sorry if I was not clear. I do not want to delete a line, just one character to the right of my cursor, or text that I have highlighted, using the same Ctrl+D command that will work in other Mac applications (I don't want to have to remember special key combinations for Spyder). I don't see any good reason for Ctrl+D behaving differently, and not in an intuitive way, in Spyder than in other applications on Macs.

You can remap those shortcuts by going to
Preferences > Keyboard shortcuts

In Mac you will find the current mapping by default
Delete -> Del
Kill next word -> Ctrl+D

So you can change them to suit your needs :-)

However, this let me thinking that we should use in the Editor the same shortcuts defined the IPython console (which can be reconfigured) for consistency.

However, this let me thinking that we should use in the Editor the same shortcuts defined the IPython console (which can't be reconfigured) for consistency.

Is this something that we can ask for over Jupyter?

We would have to do it ourselves because qtconsole is in maintenance mode now :-)

We would have to do it ourselves because qtconsole is in maintenance mode now :-)

Meaning nothing new can be added?

OK thanks very much, that sorted it out. Sorry, it hadn't occurred to me that this would be set as a keyboard shortcut. I'll close this issue now.

Please leave it open, we're thinking to improve things for our next release :-)

OK, sorry, didn't know the etiquette :-S

No worries :-)
El 03/11/16 a las 15:22, PAGWatson escribió:

OK, sorry, didn't know the etiquette :-S
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/spyder-ide/spyder/issues/3646#issuecomment-258262625,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAWS7dUelgBJivX0osX2GFhawQAnP4wLks5q6kKRgaJpZM4Kol4n.

Let's close this one in favor of #11679.


Unique key name isn't correctly set - DDC-1603

http://www.doctrine-project.org/jira/browse/DDC-1603

Move to a single PR.
https://github.com/doctrine/doctrine2/pull/261.


Error 500

2021-12-28 11:39:07,480 - INFO: Updating changed data in NetBox 2021-12-28 11:39:07,480 - DEBUG: First run, unset attributes if necessary. 2021-12-28 11:39:07,480 - DEBUG2: Resolving dependency: IP address 2021-12-28 11:39:07,483 - INFO: Updating NetBox 'IP address' object '<IP_ADDRESS>/24' with data: {'assigned_object_type': 'virtualization.vminterface', 'tags': [{'name': 'NetBox-synced'}, {'name': 'Source: vsphere-vcsa'}]} 2021-12-28 11:39:07,484 - DEBUG2: Sending PATCH to 'http://<IP_ADDRESS>:80/api/ipam/ip-addresses/140/' with data 'b'{"assigned_object_type": "virtualization.vminterface", "tags": [{"name": "NetBox-synced"}, {"name": "Source: vsphere-vcsa"}]}''. 2021-12-28 11:39:07,654 - DEBUG2: Received HTTP Status 500. NetBox returned: 500 Internal Server Error
Hey. What could be the problem?

Hey,
I would assume there is a problem within NetBox. 500 means that something in NetBox went wrong. Did you check the NetBox logs?

The problem was on my side. Fixed.


What happened with beautiful emmet!?

VSCode Version: 1.15.0
OS Version: Windows 10

Steps to Reproduce:

Creaty css file
Use Emmet

Reproduces without extensions: Yes

I very disappointed, because this code editor right now useless for me :( What happening? Any suggestions?

@kolyaraketa you can find the same issue here https://github.com/Microsoft/vscode/issues/32243

Solution:

Install insiders build
"emmet.triggerExpansionOnTab": true,

 		"editor.quickSuggestions": false
 	},```


Fix decodeExecRule so that it calls Prefetcher.firstFetchInstruction to read the current instruction and Prefetcher.deqFetchInstruction to decode instructions once done

decodeExecRule should call firstFetchInstruction to read the current instruction and then call deqFetchInstruction when the pipeline will not have to either fetch or decode/execute the current instruction. That is, we do not call deqFetchInstruction if an exception occured while trying to fetch the current instruction (e.g. the fetch was incomplete or the device was busy).
In addition ensure that all commit fifos are guarded by a check to ensure that the commit fifo is not full before executing the enqueue.

1222281


Allow to define entity setting priority

This is needed so that extension developer can control order of tabs/menus.

Wouldn't it be better to do what Menu does (from electron) and define both a "beforeEntry" and "afterEntry"?

But we're already using a similar priority field for KubeObjectDetailRegistration...

Fair, I guess. It was merely a suggestion. I would change the name though, priority is a strange name for this sort of field, maybe position.
I would say that before/after shows more intent but I am not set on it.

I think priority is ok. To change it we'd want to be consistent and change KubeObjectDetailRegistration too, which means a breaking change, not worth it, I think.

Yes, priority follows the existing logic.


[tool_crash] SessionNotCreatedException

Command
flutter drive --driver=test_driver/integration_test.dart --target=integration_test/app_test.dart -d chrome

Steps to Reproduce

...
...
...

Logs
SessionNotCreatedException
#0      parseW3cResponse (package:webdriver/src/handler/w3c/utils.dart:81:9)
#1      W3cSessionHandler.parseCreateResponse (package:webdriver/src/handler/w3c/session.dart:19:21)
#2      InferSessionHandler.parseCreateResponse (package:webdriver/src/handler/infer_handler.dart:106:34)
#3      AsyncRequestClient.send (package:webdriver/src/common/request_client.dart:96:32)
<asynchronous suspension>
#4      createDriver (package:webdriver/async_core.dart:62:19)
<asynchronous suspension>
#5      WebDriverService.startTest (package:flutter_tools/src/drive/web_driver_service.dart:144:19)
<asynchronous suspension>
#6      DriveCommand.runCommand (package:flutter_tools/src/commands/drive.dart:323:30)
<asynchronous suspension>
#7      FlutterCommand.run.<anonymous closure> (package:flutter_tools/src/runner/flutter_command.dart:1297:27)
<asynchronous suspension>
#8      AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
<asynchronous suspension>
#9      CommandRunner.runCommand (package:args/command_runner.dart:212:13)
<asynchronous suspension>
#10     FlutterCommandRunner.runCommand.<anonymous closure> (package:flutter_tools/src/runner/flutter_command_runner.dart:339:9)
<asynchronous suspension>
#11     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
<asynchronous suspension>
#12     FlutterCommandRunner.runCommand (package:flutter_tools/src/runner/flutter_command_runner.dart:285:5)
<asynchronous suspension>
#13     run.<anonymous closure>.<anonymous closure> (package:flutter_tools/runner.dart:115:9)
<asynchronous suspension>

[✓] Flutter (Channel stable, 3.13.6, on Ubuntu 20.04.6 LTS 5.15.0-91-generic, locale en_US.UTF-8)
    • Flutter version 3.13.6 on channel stable at /home/karthik/snap/flutter/common/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision ead455963c (3 months ago), 2023-09-26 18:28:17 -0700
    • Engine revision a794cf2681
    • Dart version 3.1.3
    • DevTools version 2.25.0

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
    • Android SDK at /home/karthik/Android/Sdk
    • Platform android-33, build-tools 33.0.0
    • Java binary at: /snap/android-studio/140/jbr/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.7+0-17.0.7b1000.6-10550314)
    • All Android licenses accepted.

[✓] Chrome - develop for the web
    • Chrome at google-chrome

[✓] Linux toolchain - develop for Linux desktop
    • clang version 10.0.0-4ubuntu1
    • cmake version 3.16.3
    • ninja version 1.10.0
    • pkg-config version 0.29.1

[✓] Android Studio (version 2022.3)
    • Android Studio at /snap/android-studio/128/android-studio
    • Flutter plugin version 76.1.2
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b829.9-10027231)

[✓] Android Studio (version 2023.1)
    • Android Studio at /snap/android-studio/140
    • Flutter plugin version 77.1.2
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.7+0-17.0.7b1000.6-10550314)

[✓] VS Code (version unknown)
    • VS Code at /snap/code/current
    • Flutter extension version 3.80.0
    ✗ Unable to determine VS Code version.

[✓] Connected device (2 available)
    • Linux (desktop) • linux  • linux-x64      • Ubuntu 20.04.6 LTS 5.15.0-91-generic
    • Chrome (web)    • chrome • web-javascript • Google Chrome 120.0.6099.109

[✓] Network resources
    • All expected network resources are available.

• No issues found!

Flutter Application Metadata
Type: app
Version: 1.0.0+1
Material: true
Android X: false
Module: false
Plugin: false
Android package: null
iOS bundle identifier: null
Creation channel: stable
Creation framework version: 135454af32477f815a7525073027a3ff9eff1bfd
Plugins
integration_test

Thanks for filing this issue @KarthikPrabhu123. This seems to be similar to https://github.com/flutter/flutter/issues/123602. You can see https://github.com/flutter/flutter/issues/123602#issuecomment-1490895875 and https://github.com/flutter/flutter/issues/123602#issuecomment-1662235796 for solution and check if it works for you.
Also check https://github.com/flutter/flutter/issues/131297#issuecomment-1651399775 and see what chromedriver version are you using and whether Downgrading chromedriver than your current version solves the issue or not.
Closing from here, as this isn't related to flutter but could be related to the chromedriver version's compatibility. If you disagree, write in comments and I'll reopen it.

As mentioned in the comment, I downgraded the Chrome driver version to (ChromeDriver 114.0.5735.90 ) and am currently facing the same error.

actually this issue doesn't relate to the chromedriver version's compatibility.
please check my issue detail : https://github.com/flutter/flutter/issues/148029


HEIMAN Siren HS2WD-E killed my homebridge

Issue

Hi
I have a big problem after adding HEIMAN Siren HS2WD-E
I have both Philips HUE and deconz, today I added the siren to deconz but homebridge stopped working, I continue to have "Cannot add a bridged Accessory with the same UUID as another bridged Accessory"
I tried to clean both persist accessories directories, no success..
removed siren from deconz and reboot.. no success..
At the moment my homebride is dead
Can you help me ?
Regards
Log Messages
May 10 20:24:26 raspberrypi homebridge[541]: [2018-5-10 20:24:26] [Hue] Error: Cannot add a bridged Accessory with the same UUID as another bridged Accessory: 4120af75-9013-4c44-8f63-5c955df196d1
Debug Files

I don't think this is related to the Siren.
Did you move any devices from your Hue bridge to deCONZ, without deleting the corresponding resource from the Hue bridge?  homebridge-hue bases the UUID on the ZigBee mac address, so having the same device on both the Hue bridge and deCONZ would cause this.
If that's not it, please attach the debug dump file (see https://github.com/ebaauw/homebridge-hue#debug-dump-file) and debug log file (see https://github.com/ebaauw/homebridge-hue#debug-log-file).

Hi ebaauw
thank you to help me.. !
I am almost sure there is something related with siren because I booted a backup SD from a couple of day ago, it worked.. after that  I re-added siren and AGAIN still the same error.. !
well I bricked both production an backup !! :(
Is seem something related with Daylight
May 10 23:46:00 raspberrypi homebridge[514]: [2018-5-10 23:46:00] [Hue] Initializing platform accessory 'Daylight'...
May 10 23:46:00 raspberrypi homebridge[514]: [2018-5-10 23:46:00] [Hue] Error: Cannot add a bridged Accessory with the same UUID as another bridged Accessory: 4120af75-9013-4c44-8f63-5c955df196d1
May 10 23:46:00 raspberrypi homebridge[514]:     at Bridge.Accessory.addBridgedAccessory (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/Accessory.js:264:13)
May 10 23:46:00 raspberrypi homebridge[514]:     at Server. (/usr/lib/node_modules/homebridge/lib/server.js:377:24)
May 10 23:46:00 raspberrypi homebridge[514]:     at /usr/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/util/once.js:16:19
May 10 23:46:00 raspberrypi homebridge[514]:     at request.then.catch.then.then.then (/usr/lib/node_modules/homebridge-hue/lib/HuePlatform.js:301:5)
May 10 23:46:00 raspberrypi homebridge[514]:     at Function.then (/usr/lib/node_modules/homebridge-hue/node_modules/deferred/_ext.js:67:13)
May 10 23:46:00 raspberrypi homebridge[514]:     at Deferred._settle (/usr/lib/node_modules/homebridge-hue/node_modules/deferred/deferred.js:97:26)
May 10 23:46:00 raspberrypi homebridge[514]:     at Deferred.resolve (/usr/lib/node_modules/homebridge-hue/node_modules/deferred/deferred.js:142:15)
May 10 23:46:00 raspberrypi homebridge[514]:     at fs.writeFile (/usr/lib/node_modules/homebridge-hue/lib/HuePlatform.js:372:11)
May 10 23:46:00 raspberrypi homebridge[514]:     at FSReqWrap.oncomplete (fs.js:135:15)
I am so tired..
Tomorrow I will send you all the logs
Best regards

Is seem something related with Daylight

Sounds like #328.  What version of deCONZ and of homebridge-hue are you running?

Hi ebaauw
I am running the latest version of homebridge-hue and deCONZ because i tried to update after the problem occurred, I do not remember which version was installed before.
"excludeSensorTypes": ["Daylight"] finally helped but all my configuration was destroyed.. I cut a lot of thinks and I was forced tho re-add homebride to HomeKit.. a lot of work was lost !! :(
I still do not understand well what happened.. can you explain ?
Regards

Dear ebaauw
Thank you very much for your great support I am unable to sen logs because at the moment everything is working, thank you again for your great job
Regards


charts/osm: allow additional root properties

Description:
Currently, the schema prevents additional
Helm chart properties other than OpenServiceMesh
which is the root property for all values.
This change enforces strict validation only
for the OpenServiceMesh root property. Other
root properties that might be leveraged by
Helm charts using the OSM chart as a dependency
will not be subjected to schema validations.

Affected area:

Functional Area

Install
[X]

Please answer the following questions with yes/no.

Does this change contain code from or inspired by another project? no

Did you notify the maintainers and provide attribution?

Is this a breaking change? no

Codecov Report

Merging #3479 (ea70ba5) into main (d858adb) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #3479   +/-   ##
=======================================
  Coverage   65.87%   65.87%
=======================================
  Files         169      169
  Lines        7886     7886
=======================================
  Hits         5195     5195
  Misses       2660     2660
  Partials       31       31

Flag
Coverage Δ

unittests
65.87% <ø> (ø)

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

Continue to review full report at Codecov.

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

@Mergifyio backport release-v0.9


Fix custom SQL generation issue - Github issue 4369

Impact

[x] Bug fix (non-breaking change which fixes expected existing functionality)
[ ] Enhancement/New feature (adds functionality without impacting existing logic)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Description
#4369

Things to be aware of

Things to worry about

Additional Context

Tested manually. Looks good to me.
Created test only ticket to automate customChange type https://datical.atlassian.net/browse/DAT-15319

It's been approved for over 3 months but not yet merged. Anything holding this PR back?

@marcelstoer seems we lost track of it. Thanks for bringing this to our attention, moving forward!

Thanks!

seems we lost track of it

Yeah, I guess it can be a bit overwhelming with so many open PRs. Currently 33 of them are approved waiting to get pushed on.

@rberezen is this one approved? As per the comment above seems so...

@filipelautert you are right, approved. Sorry for inconvenience


[BUG] Wrong storage class configured when creating a volume with the Harvester terraform provider

Describe the bug
This issue was spotted during the validation of https://github.com/harvester/harvester/issues/634
When I try to create a volume from an image with the Harvester terraform provider, the volume stays in NotReady status forever.
I've tried to debug it a little bit and looks like the storage class is wrong, the terraform provider adds the namespace in the storage class name:
hpd8s12 [~]$ kubectl get pvc
NAME                      STATUS    VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS                AGE
ubuntu20-dev-image-disk   Pending                                                                        longhorn-default-ubuntu20   11m
ubuntu20-dev-mount-disk   Bound     pvc-83933329-93e2-4876-955f-9bb0b16287f7   10Gi       RWX            longhorn                    11m

hpd8s12 [~]$ kubectl get sc
NAME                 PROVISIONER          RECLAIMPOLICY   VOLUMEBINDINGMODE   ALLOWVOLUMEEXPANSION   AGE
longhorn (default)   driver.longhorn.io   Delete          Immediate           true                   84m
longhorn-k3os        driver.longhorn.io   Delete          Immediate           true                   12m
longhorn-ubuntu20    driver.longhorn.io   Delete          Immediate           true                   12m

From my knowledge, the storage class is not a resource where you can use namespace:
kubectl api-resources --namespaced=false --sort-by=name | grep storageclasses
NAME                              SHORTNAMES   APIVERSION                             NAMESPACED   KIND
storageclasses                    sc           storage.k8s.io/v1                      false        StorageClass

I'm totally beginner with GO langage but the issue can comes from here
In my case, I tried to create a new storage class named longhorn-default-ubuntu 20 and this time, the PVC got the Bound status.
To Reproduce
Steps to reproduce the behavior:

Follow the step to configure the harvester terraform provider here
Follow the step to create the images by executing the image example
Create the volumes with the volume example
The volume ubuntu20-dev-image-disk will stay in the NotReady status forever.

Expected behavior
The volume should be ready using a correct storage class name.
Support bundle
harvester-supportbundle_58a64e6c-b087-49b5-89d2-6b3196a32355_2021-07-26T13-43-41Z.zip
Environment:

Harvester ISO version: master-2f810069-head + terraform-provider-harvester v.0.1.0 + Terraform v1.0.3
Underlying Infrastructure (e.g. Baremetal with Dell PowerEdge R630): 5 nodes cluster DL360 G9

Additional context
Add any other context about the problem here.

To test
Use the recreated release v0.1.0: https://github.com/harvester/terraform-provider-harvester/releases/download/v0.1.0/terraform-provider-harvester-amd64.tar.gz

After install, run rm .terraform.lock.hcl before terraform init

Tested successfully with the last master branch of harvester (master-2f810069-head
) and last release of the terraform provider.
hpd12s17 [~]$ kubectl get pvc
NAME                      STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS        AGE
ubuntu20-dev-image-disk   Bound    pvc-fb85d146-1241-479e-b040-377af43ff234   10Gi       RWX            longhorn-ubuntu20   11m
ubuntu20-dev-mount-disk   Bound    pvc-9b05b07e-f101-4c1f-89ee-7de24e8e3ade   10Gi       RWX            longhorn            11m

hpd12s17 [~]$ kubectl get sc
NAME                 PROVISIONER          RECLAIMPOLICY   VOLUMEBINDINGMODE   ALLOWVOLUMEEXPANSION   AGE
longhorn (default)   driver.longhorn.io   Delete          Immediate           true                   3h48m
longhorn-k3os        driver.longhorn.io   Delete          Immediate           true                   13m
longhorn-ubuntu20    driver.longhorn.io   Delete          Immediate           true                   13m


Investigate: Wallet "Updated By" gets set to now every time a tenant logs in?

Not sure if anything needs doing here, but something to look into quick and then action for later.
AC:

We know if we need to do anything with this?
A acapy issue is raised if it IS one.
We have a decision on if to show that field in the Tenant UI if it's not actually the "updated at" time.

Noticed that each time I log in with a tenant then the wallet settings show updated_at as that time

So in the tenant settings screen it would not really show you the last time those "settings" have been "updated"

nothing to do here, this is default acapy multitenant stuff. technically, each token would be an update to the wallet. in the basic multitenant, the single iat is stored in the wallet record, and in our plugins we followed the same process (store token validity in the wallet).

Ok, think  we can't treat the "updated by" as "the settings were last updated" then so I'll adjust it out in the tenant UI


Docs have wrong return type when tuples

Hi!
I think the Smart Contract API docs are wrong when showing tuple returns:
https://github.com/OpenZeppelin/openzeppelin-sdk/blob/c68234271a4a6e29b989fe1bac1902a246a298b3/packages/lib/docs/modules/ROOT/pages/api.adoc#getpackagestring-packagename--contract-package-var-typeuint643-item-kindpublic
Thanks,

Hi @ilanolkies! Thanks for reporting. This is a bug we've fixed in Contracts and haven't ported here yet.
However, this file shouldn't be in the repo in the first place. :slightly_smiling_face: It's generated in the docs build, and you should view it at docs.openzeppelin.com/upgrades/api.

Removed the file in 427fc2ce4305892459aca713f46d9f810ff24087, and fixed the template in f6e3f09efece6c2a36a6c48f982099f9948c1521.


Trying to implement jsmpeg in a angular proyect.

So im trying to make the player work in the angular and webpack and im getting an error like this
angular.js:14791 TypeError: this.fillArray is not a function
at webpackJsonp.216.window.jsmpeg .
is there a work around to avoid this issue?
i have no problem opening  using the example, so its obvious is a problem with the angular client.

import JSMpeg from '!!imports-loader?this=>window!exports-loader?JSMpeg!jsmpeg/jsmpeg.min.js';


Schedule Summary Diesel Gasoline Rounded Input

#1334 #1335
Added automatic commas for input field in Diesel and Gasoline
Changelog:

Summary Gasoline and Diesel Input fields  no longer allow decimals
Input fields should automatically add commas

 Compliance Report | Restrict Line 6 8 17 19 to whole numbers and adjust corresponding label accordingly |1|

 Compliance Report | Restrict summary section tooltip for Line 6 8 17 19 to whole numbers |1|


How do you rerun falcon with a different length_cutoff_pr?

Package name
Falcon (fc_run)
Expected behavior
I am trying to run falcon on the same data as previous run with the same fc_run.cfg parameters EXCEPT that the length_cutoff_pr is shorter. Is this possible without having to rerun the lengthy preassembly steps?

Closing due to lack of activity.


[ADD]: Ciphey tool

Aim
Addition of Ciphey tool
Details
Ciphey is an automated decryption tool that uses artificial intelligence and natural language processing to decrypt encrypted text.
The script defines a decrypt function that takes a ciphertext and uses the Ciphey tool to search for the decrypted text. It returns the decrypted text if successful or "Failed to crack" if decryption fails.
Do I want to work on this:

[X]  Yes
[ ] No

@avinashkranjan can you assign me this issue.

Go Ahead @Killer2OP


update deprecated htmlAttributes to hProperties

Fixes #40

Hey @ben-eb, when you get the chance could you please take a look at this PR?
Cheers!

Dude any plans to fix this?

I am maintaining a fork here https://github.com/thetutlage/remark-autolink-headings.
I updated all the dev dependencies and dependencies.

Removed eslint and using standard ( personal preference )
Using babel-preset-env over es2015
Added a githooks to create a final build and push the dist folder to Github ( since I am not publishing on npm)

Happy to create a PR, but I am not sure if author really wants all the changes.

I have a fork published to npm at @rigor789/remark-autolink-headings, I don't think the author uses this package anymore, so by the looks of it it has been abandoned.


Add Mysql string type in schema

Please add string schema type
I  mean
ta.Columns[index].MysqlType = columnType
in https://github.com/siddontang/go-mysql/blob/master/schema/schema.go#L59

Hi @arduanov
Why do you want this? If needed, could you send me a PR?
Btw, I prefer RawType or DescType :-)

Now I have only a digital columns type on the basis of which it is impossible to determine the source type Mysql columns
I need it for integration with other databases, specifically for the Apache Spark
I make PR soon, thanks


Investigate support for nio-transport-services

cross posting from #135
how this works is: You only need one #if ... and then you can
#if canImport(Network)
// Creating the "universal bootstrap" with the `NIOSSLClientTLSProvider`.
let tlsProvider = NIOTSClientTLSProvider(tlsOptions: .init())
let bootstrap = NIOTSClientTLSProvider(NIOTSEventLoopGroup(group: group), tls: tlsProvider)
#else
// TLS setup.
let configuration = TLSConfiguration.forClient()
let sslContext = try NIOSSLContext(configuration: configuration)

// Creating the "universal bootstrap" with the `NIOSSLClientTLSProvider`.
let tlsProvider = NIOSSLClientTLSProvider<ClientBootstrap>(context: sslContext, serverHostname: "example.com")
let bootstrap = NIOClientTCPBootstrap(ClientBootstrap(group: group), tls: tlsProvider)
#endif

// Bootstrapping a connection using the "universal bootstrapping mechanism"
let connection = bootstrap.enableTLS()
                     .connect(host: "example.com", port: 12345)
                     .wait()

For AsyncHTTPClient, you'll want to cache two bootstraps:
let tlsBootstrap: NIOClientTCPBootstrap = makeBootstrapForPlatform().enableTLS()
let plainTextBootstrap: NIOClientTCPBootstrap = makeBootstrapForPlatform()

and then you can just use the right one to bootstrap connections from depending on if that's TLS or not.

This was implemented in #184


Add Support for Observe Only Resources

Description of your changes
Adds support for Observe Only resources.
I have:

[x] Read and followed Crossplane's contribution process.
[x] Run make reviewable test to ensure this PR is ready for review.

How has this code been tested
N/A

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


On app launch, the useNetInfo hook fires with wrong information

Environment
System:
OS: macOS 10.15.4
CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
Memory: 529.11 MB / 16.00 GB
Shell: 5.7.1 - /bin/zsh
Binaries:
Node: 13.8.0 - /var/folders/lw/xjvz84855fz5p2w3k8m6dtbh0000gn/T/yarn--1588945240656-0.28786507373777126/node
Yarn: 1.22.0 - /var/folders/lw/xjvz84855fz5p2w3k8m6dtbh0000gn/T/yarn--1588945240656-0.28786507373777126/yarn
npm: 6.13.7 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
iOS SDK:
Platforms: iOS 13.4, DriverKit 19.0, macOS 10.15, tvOS 13.4, watchOS 6.2
IDEs:
Android Studio: 3.6 AI-192.7<IP_ADDRESS>00805
Xcode: 11.4.1/11E503a - /usr/bin/xcodebuild
npmPackages:
react: 16.9.0 => 16.9.0
react-native: 0.61.5 => 0.61.5
Platforms
Both
Versions

Android: Multiple versions
iOS: Multipe versions, tested on 12 and 13
react-native-netinfo: 5.8.0
react-native: 0.61.5
react: 16.9.0

Description
When i launch my app, the useNetInfo hook fires multiple times, but one of those times it returns wrong data.
state = {
  details: null
  isConnected: false
  isInternetReachable: false
  type: "unknown"
}

I am sure i do have internet, and this only happens during the initial load of the JS bundle. This results in my 'No Connection' overlay to flash into the view.
Reproducible Demo

Create RN app
Include this library
Use the hook in your Root Component
Alert.alert('Oops'); if state.isConnected === false

You will see the alert pop up once during launch.

Btw, this incorrect state is passed in the first time the hook runs. The following times it runs, it gives the correct state.

I also met

Happening for me as well. Had to use a well known timeout hack to make it work.

same here

Same issue

same issue here

😢

The same.

The same. For a short period of time it looks that there is no internet connection but for 100% there is one.

Is there any solution to this yet ? The fix is to add timeout ?

I'm facing a similar issue on ios. Haven't yet tested on android. I'll try the timeout hack while this is unresolved

Any updates on this? I'm getting false alarms too when app launches

I don't believe anyone has proposed a design or PR to stop it, so, no updates - someone from the community will have to propose something and drive it to closure
Workarounds have been posted where at the app level it is effectively handled by discarding the first one

Is there any solution to this yet ? The fix is to add timeout ?

I also have the problem, that isInternetReachable is null for a longer time. I need to call await NetInfo.fetch() multiple times, until isInternetReachable changes to true or false.

Fixed in v6.0.0 via #444


C# patterns reference: positional pattern

Contributes to #20584

@BillWagner thank you; I've applied both of your suggestions


Router.navigate Replace State

In writing a search component that live-updated the URL, I found that Router's navigateByInstruction and navigateByUrl both have optional parameters to replace the current state rather than pushing a new state to the browser's history. Why doesn't navigate have this option as well?
If it was not an intentional omission, I could create a PR with this change.

Thanks for filing, sorry for the delay in a response.
We're currently in the process of alpha-testing a new router, and we'll be pushing to GitHub/Pub shortly to get some external users to try it out. If you're blocked by this you might want to consider forking just the router components for a few weeks.


See if we can generate the index array data using const fn

Once we upgrade to Rust 1.31, we might be able to generate the static data used to fill the index array at compile time instead of at runtime - it's probably not a huge performance gain, but if it'd be easy it'd be nice to do it!

Apparently not for now, as you can't use variables or function references in a const fn.


Bto fix

Addressed issue with BTO order size of 0 and added user input validation

Removing an extra comment


Question: Where do I enter a GraphQL WebSocket URL (which is different from the /graphql endpoint)?

I'm using a GraphQL server (AWS AppSync) that has a completely different WebSocket endpoint than the main /graphql endpoint. I am able to run queries and mutations successfully but not subscriptions.
How do I let GraphQL-Playground know about the custom Websocket Endpoint?
This issue pertains to the following package(s):

[x] GraphQL Playground - Electron App
[ ] GraphQL Playground HTML
[ ] GraphQL Playground
[ ] GraphQL Playground Express Middleware
[ ] GraphQL Playground Hapi Middleware
[ ] GraphQL Playground Koa Middleware
[ ] GraphQL Playground Lambda Middleware

What OS and OS version are you experiencing the issue(s) on?
macOS High Sierra
What version of graphql-playground(-electron/-middleware) are you experiencing the issue(s) on?
1.7.0

Pass it like props to playground or have it inside config :) https://github.com/prisma/graphql-config#specifying-endpoint-info


Create docker image

Create docker image based on https://github.com/graphite-project/docker-graphite-statsd

Work in progress : https://github.com/iksaif/docker-graphite-statsd/commit/315b1cf7da2e813bf013f7f29ba9afecc0b0e359


Allow automatic creation of subtitles through AutoSub, served as WebVTT files

An important feature to support is captions, this is especially important for accessibility for those who cannot hear, as well as for non-native English speakers to be able to understand content better. Also, it's offered by YouTube and people should not have to feel like they are sacrificing features to use Odysee and we should aim for feature parity or even having additional features when compared to YouTube.
An issue is created for supporting captioning here:
https://github.com/lbryio/lbry-desktop/issues/2325
But I will make this ticket only to cover automatically generated captions, with the ability for people to upload their own captions during the upload process to be implemented as a separate ticket.
I tested out the AutoSub module, which is a CLI which integrates open-source Mozilla DeepSpeech for the speech to text functionality, and then through some clever programming is able to correspond that text with the proper timestamps, and it works actually quite well out of the box.
https://github.com/abhirooptalasila/AutoSub
They say they have the capability to output in WebVTT automatically, which I wasn't able to get working with a first attempt, but regardless .srt and .vtt formats are very similar so to convert between the two is trivial and there are a lot of packages that allow that to be carried out.
Once the .vtt file is created, it is trivial to serve it via videojs by adding to this line:
ui/component/viewers/videoViewer/internal/videojs.jsx:220
Something along the lines of
tracks: [{src: 'https://servestatic.tv/mysub.vtt', kind:'captions', srclang: 'en', label: 'English'}]
I implemented and tested this functionality and was quite impressed with how well Autosub worked. You can see it even properly transcribed the word 'prophylactic'. It was similar to what would be expected from YouTube so I would say that Autosub would work well enough out of the box to ship.

AutoSub is also built on top of Mozilla's Deep Speech which although I used against a model trained on an English speaking dataset, there are also models for different languages so we would be able to use those as well though I never tested using a non-English dataset myself. Although, I believe most of the content and viewers are English speaking so this could probably cover in Pareto distribution style maybe 80% of content creators/users right out of the gate. Would also be a great way to begin supporting captioning, at which point the ability for users to upload their custom captions during the upload process could be supported as well.

There is also https://github.com/BingLingGroup/autosub

There is also https://github.com/BingLingGroup/autosub

Yes but correct me if I'm wrong but it looks like all the actual speech to text translation is done using a 3rd party (paid) API, is it so?

You have the option to use a 3rd party API. But if you don't, you can use the free version of Google Translate API to create the subtitles.
All I had to do was:
autosub -i file.mp4 -S en-US

You're welcome.
Can you give us some more details or steps or commands you did to get the mozilla deepspeech autosub working? I am curious to try it out myself but not exactly sure how to use it.

Just follow the docs here: https://github.com/abhirooptalasila/AutoSub#installation
You may have to install DeepSpeech separately here: https://deepspeech.readthedocs.io/en/r0.9/?badge=latest


"+ligatures/install-patched-font" Does not Install 'Fira Code Symbol' Font to ~/.local/share/fonts

[X] I have searched the FAQ and the documentation for solutions.
[X] I have searched the issue tracker for similar issues (the closed issues too).
[X] I have searched the Discourse for any errors and solutions.
[X] I can reproduce my issue on the latest commit of Doom Emacs.
[X] I have read How to Debug Issues and found no solution.

What did you expect to happen?
I was attempting to enable ligatures for Fira Code. I followed the instructions provided in:
https://github.com/hlissner/doom-emacs/tree/develop/modules/ui/ligatures
See repro Below for steps.
After running the command "+ligatures/install-patched-font" and restarting doom-emacs I expected Fira Code Ligatures to be displayed properly but they were not.
What actually happened?
After running the script, ligatures were not displayed properly

Describe your attempts to resolve the issue
I discovered the script was not actually installing 'Fira Code Symbol' to the directory ~/.local/share/fonts/
I was able to resolve by running yay -S otf-fira-code-symbol. Ligatures now display properly
I resolved my issue, but I am thinking there could be a problem with the script.
Steps to reproduce

Set :ui (ligatures + fira) in $DOOMDIR/init.el
Set doom font to Fira Code: (setq doom-font (font-spec :family "Fira Code" :size 13)
doom sync
Restart Emacs and Run: M-x +ligatures/install-patched-font to install Fira Code Symbol
ls ~/.local/share/fonts | grep "Fira Code Symbol" returns nothing

System Information
https://pastebin.com/7aK5G8SG

I just ran into this on emacs 27.2, Mac OS.  The link in +fira.el installs "Fira Code", not "Fira Code Symbol", and the glyph mappings are not the same between the two fonts.  To solve this on mac, I downloaded https://github.com/tonsky/FiraCode/files/412440/FiraCode-Regular-Symbol.zip which is the file used by the yay command above, and installed the font.

I just ran into this on emacs 27.2, Mac OS. The link in +fira.el installs "Fira Code", not "Fira Code Symbol", and the glyph mappings are not the same between the two fonts. To solve this on mac, I downloaded https://github.com/tonsky/FiraCode/files/412440/FiraCode-Regular-Symbol.zip which is the file used by the yay command above, and installed the font.

I also did the same on Windows Subsystem for Linux, and now the Fira Code ligatures are showing correctly!


HTYI: Formatting breaking during voting stage

It's doing this consistently every round, currently playing with four players.

@esalling23 make sure to check up on this, as i assume this is happening due to some other issues you are working through

@jpailthorpe have a fix for the voting group screen, working on results screen now!

checked


Getting error in sypder old versions my python is 3.6.15 and sypder is 3.2.1

Description
What steps will reproduce the problem?

just typing sypder in anaconda, sypder will open and gives error and asked to submit to github

What is the expected output? What do you see instead?
Please provide any additional information below
File "C:\Users\UNIQUE\miniconda3\envs\spyenv\lib\site-packages\qtconsole\base_frontend_mixin.py", line 138, in _dispatch
Traceback (most recent call last):
File "C:\Users\UNIQUE\miniconda3\envs\spyenv\lib\site-packages\qtconsole\base_frontend_mixin.py", line 138, in _dispatch
Traceback (most recent call last):
File "C:\Users\UNIQUE\miniconda3\envs\spyenv\lib\site-packages\qtconsole\base_frontend_mixin.py", line 138, in _dispatch
File "C:\Users\UNIQUE\miniconda3\envs\spyenv\lib\site-packages\spyder\widgets\ipythonconsole\namespacebrowser.py", line 209, in _handle_execute_reply
Traceback (most recent call last):
File "C:\Users\UNIQUE\miniconda3\envs\spyenv\lib\site-packages\qtconsole\base_frontend_mixin.py", line 138, in _dispatch
Traceback (most recent call last):
Traceback (most recent call last):
File "C:\Users\UNIQUE\miniconda3\envs\spyenv\lib\site-packages\qtconsole\base_frontend_mixin.py", line 138, in _dispatch
File "C:\Users\UNIQUE\miniconda3\envs\spyenv\lib\site-packages\spyder\widgets\ipythonconsole\namespacebrowser.py", line 209, in _handle_execute_reply
Traceback (most recent call last):
File "C:\Users\UNIQUE\miniconda3\envs\spyenv\lib\site-packages\qtconsole\base_frontend_mixin.py", line 138, in _dispatch
File "C:\Users\UNIQUE\miniconda3\envs\spyenv\lib\site-packages\spyder\widgets\ipythonconsole\namespacebrowser.py", line 209, in _handle_execute_reply
Version and main components

Spyder Version: 3.2.1
Python Version: 3.6.15
Qt Versions: 5.12.9, PyQt5 5.12.3 on Windows

Dependencies
pyflakes >=0.6.0 :  2.4.0 (OK)
pycodestyle >=2.3:  2.8.0 (OK)
pygments >=2.0   :  2.10.0 (OK)
pandas >=0.13.1  :  None (NOK)
numpy >=1.7      :  None (NOK)
sphinx >=0.6.6   :  4.3.2 (OK)
rope >=0.9.4     :  0.22.0 (OK)
jedi >=0.9.0     :  0.17.2 (OK)
nbconvert >=4.0  :  6.0.7 (OK)
sympy >=0.7.3    :  None (NOK)
cython >=0.21    :  None (NOK)
qtconsole >=4.2.0:  5.2.2 (OK)
IPython >=4.0    :  7.16.1 (OK)
pylint >=0.25    :  2.11.1 (OK)

Hey @darknightush, thanks for reporting. Unfortunately, Spyder 3 (and also Spyder 4) are not maintained anymore.
This problem could be fixed in the latest Spyder 3 version. Please update by closing Spyder, opening the Anaconda Prompt and running there
conda install spyder=3.3.6

If that's not the case, please update to our latest version available in Anaconda (5.1.5).


Use MSAL instead of ADAL

ADAL is being deprecated.

Docs Build status updates of commit 4a8a729:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

office-365-management-api/get-started-with-office-365-management-apis.md
:white_check_mark:Succeeded
View

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

@markjjo FYI  ADAL is being deprecated, so updating for MSAL

#sign-off

@markjjo  Can you take a look at this?  I'm not sure what the process for merging is for this repo.  Thanks.


GH-2132: Deprecate ListenerUtils.recordToString

Resolves https://github.com/spring-projects/spring-kafka/pull/2133
Apply to 2.8.x, and 2.7.x.
In 3.0 they will be removed and KafkaUtils called directly instead.

This cannot be back-ported clearly.
Do, we really need to worry about those deprecations in version below 2.8.x?

Agreed; but then we need to revert part of the previous cherry-pick (just the consumer record parts).
I will do a new PR in the morning.


can not access to some pre-trained models

hello, I found that the links of some pre-trained models are invalid. Now only the link to VCTK Multi pretrained model can be access. Can you check what the problem is or reupload the models?

models were reuploaded


new Javascript pixi flump runtime.

You can take a look at it at https://github.com/mientjan/pixi-flump, Will add documentation to the runtime in the comming days.

Thanks!


readme: corrected a typo (missing github.com host)

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

Oh, #183

Thanks @notatestuser!  Merged #183.


BLS Pool Size

Describe the bug
Currently BLS pool size is number of cores. I think it should number of cores - 1 as we use 1 for the main thread
Also BLS pool size seems to be always 4

On contabo-20, it's really 4: cpu cores	: 4
But on hetzner-test0 it's 6: cpu cores	: 6

(checked with cat /proc/cpuinfo | grep "cores")

It doesn't really matter too much because in practice seems that only the first 2 workers take all the work. You can't really control on which core each worker will run really.

Also node-exporter shows that load is very evenly distributed across cores

I don't believe this is an issue. NodeJS native worker pool is always 4. Modern CPU can handle this mismatch in count just fine. We could worry about the extra overhead of more workers than necessary but it's a minor issue


Faster implementations

Seems you got this thought for use with api.
What about helping with this?

mainly targeted towards the creation of headless content management