BuildVersion should be removed from $PSVersionTable

Steps to reproduce
$PSVersionTable. The major version should be 10 on Windows PowerShell build from PowerShell repo.
Expected behavior
Version is 10?
Actual behavior
BuildVersion                   <IP_ADDRESS>
Environment data
> $PSVersionTable
Name                           Value
----                           -----
PSVersion                      5.1.10032.0
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   <IP_ADDRESS>
GitCommitId                    v0.6.0-112-g3276846c401e0c2132cc260f89752b121c81abde
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>

@adityapatwardhan @SteveL-MSFT @HemantMahawar  is this something we need in PSCore for Win10? What is BuildVersion supposed to denote?

Looking at the code, it's the fileversion of sma.dll.  I don't think this property is actually useful particularly since we have the GitCommitId now.  Perhaps we should remove it even though it's a breaking change. @joeyaiello

@SteveL-MSFT I agree, it is better to introduce the breaking change now.

Not sure if this has already been discussed, but should GitCommitId actually refer to Git?  I know it's a great DVCS and all, but should the Property refer to something more generic?

@ebekker good question.  We don't have any reason or plans to move from GitHub and git now that we are Open Source, the GitCommitId literally allows someone to build the same version that was used to report an issue (if needed).  It's really only intended to be useful for developers of PSCore6.  End users should rely on PSVersion.


Retry when former leader failed.

If the former leader is no longer the leader, but we think that they are, when we attempt to query it with the session object, we will receive an error message.  That doesn't mean that we can no longer proceed, it only means we have to find the new leader by attempting one of the other nodes.

Addresses #33.

Closing to fix CRLF issues.


iOS 9 seems to have added its own support for UICollectionView

As far as I can tell, UICollectionView (at least for flow layout and vertical scrolling) has been updated in iOS 9.0 to work the way UITableView does now and automatically increases the content size and scrolls to the first responder text field/view. I haven't found an Apple release note or doc change mentioning it yet, though.
As far as my app is concerned, that means that TPKeyboardAvoidingCollectionView is completely broken on iOS 9+. The content size gets reset to be too small when the keyboard disappears (e.g., cells at the bottom are no longer visible).
Since I load the TPKeyboardAvoidingCollectionView in a storyboard, I modified my version to pretty much avoid doing anything if the version is iOS 9.0 or above.
For example:
 -(void)awakeFromNib {         if ([[NSProcessInfo processInfo] operatingSystemVersion].majorVersion < 9) {            [self setup];         }     }

This should be all good now; TPKB disables on iOS 9.

Thanks!


Make sure database is dropped on the day it expires

Issue spawned from #192
With current logic, it is possible that a database that expires on day X will only be dropped on day X+1, which can be a bit confusing, as on day X+1, users see that there's still a database that should've been dropped on day X.
The reason is because the goroutine that checks this runs every 24 hours starting from when the server was started. If a database expires on the same day but after the checking time, then it'll only be deleted the next day.
To resolve this, current logic should be altered:
Instead of checking whether the expirydate is earlier than the time the check happens, it should check whether the day of expiry is the same as the current date, and if so, drop.
Additionally, it would be nice if it ran at a predetermined time instead of 24h after server startup.

I'll give this a try.

Pull request: https://github.com/djavorszky/ddn/pull/203

Closed via #203, thanks!


Design document focusses on BLAS, and should cover other parallelism aspects

The document seems like a really good description. However, there's a few biggish things that aren't covered. (I'm coming at this from the point-of-view of a scipy developer, although these comments represent my personal opinion)

The document is overly focused on parallelism in BLAS. There are several places in the scipy codebase that are parallelised (or could be parallelised) with multiprocessing or other threading models. The workers keyword in optimize.differential_evolution is one such example. I think the document needs to be expanded to cover parallelism in non-BLAS situations. The whole parallelism hierarchy is important because those situations could end up eventually calling other parallel routines such as BLAS.
The document doesn't cover parallelism and design choices in extension code. For example cython can use prange, or other extensions might use OpenMP/pthreads. How should extensions be designed to have a common parallelism approach?
@jjerphan

The Current Landscape section states how SciPy uses workers to mean multi-threading, multiprocessing, or pthreads. The APIs for Configuration Parallalism section reinforces this by stating the semantics for n_jobs and workers. That section also proposes workers from SciPy to configure parallalism for all libraries. I'll update it so it explicitly states that workers could mean anything the library wishes to use: multi-threading, multiprocessing, OpenMP threads, or pthreads.

The whole parallelism hierarchy is important because those situations could end up eventually calling other parallel routines such as BLAS.

With nested parallel calls, I think the public API should still be workers, but it is up to the library to do the right thing. For example, Scikit-learn does call BLAS routines from OpenMP threads and limits BLAS to be single thread.

For example cython can use prange, or other extensions might use OpenMP/pthreads. How should extensions be designed to have a common parallelism approach?

I think the first step is to have a common API such as a workers parameter. I prefer not to restrict libraries to only use OpenMP and allow libraries to use pthreads or any other mechanism they want for parallelism. If a library uses OpenMP, then I want to recommend linking to the OpenMP wheel. This way libraries can all share the same OpenMP thread pool.
The "Multi-threaded by Default" section is the status quo for SciPy's workers because it is serial by default. This is mostly a BLAS issue. "Interactions Between Different Forms of Parallelism" is mostly about OpenMP and different compilers and not BLAS.
In the end, I wanted to cover parallelism with a focus on what the issues are. Currently, the issues mostly revolves around BLAS and OpenMP. I do not see too many issues around multi-threading, multiprocessing, or pthreads besides over-subscription. I think most over-subscription issues can be resolved by "single-threaded by default". (I decided not to cover the standard trade offs between multi-threading and multi-processing in Python.)
Thank you for the feedback. It is very helpful and I will update the document based on it.

Based on your feedback, I added:

General reordering and explicitly state the workers parameter can mean any form of parallelism: https://github.com/thomasjpfan/parallelism-python-libraries-design/commit/c4c9ae8de5c57a0b37e003f7eeb1632d3973953d
FAQ entry on how workers means any form of parallelism: https://github.com/thomasjpfan/parallelism-python-libraries-design/commit/35424c2e8ac6d87202837cf2c816f15b0af97ded
Item on nested parallel calls: https://github.com/thomasjpfan/parallelism-python-libraries-design/commit/63185a9f2ea34d6440d639b7892b3928d2356546

For differential_evolution, there is a user provided function which is run in parallel using multiprocessing:
https://github.com/scipy/scipy/blob/cd57132feb6a9a17b78f32aecd9c511369147b76/scipy/optimize/_differentialevolution.py#L1123
If the user provided function is parallel and workers is not 1, then there could be over-subscription. In those cases, I do not think SciPy can do anything besides documenting that func is called in parallel when workers != 1.


Prometheus integration implementation

We've added Prometheus pushgateway emitter.
Currently labelled counter metrics for events/attacks/responses are pushed to the gateway.
We decided to exclude username label because of high cardinality of its values set.

@sidewalker @wylly This is really excellent work. If you can address that 1 comment, I'll be happy to merge.

@sidewalker @wylly merging this - outstanding! Consider adding a README.md to document what you've done here, in particular linking to the push gateway component.


Python 3 builtins via six

Replace the builtins that are different on Python 3 using six. This only includes changes in files where these functions are used. I'll open a second PR adding these new builtins to the remaining files later.

If tests pass :+1:. Please keep 3c9fc9f as a base commit, putting subsequent work on top of that.

OK, tests pass, but there might be one filter I missed somewhere that isn't caught right now. I'd prefer to have it in this PR instead of the next blanket one, so hold on for a bit.

Ah, I just missed the .krb file, so I think it should be good now (once tests pass).

Seems problematic...

Oops, I shouldn't do this so late at night...


feat: marker绑定点击事件

:tada: This PR is included in version 1.0.0-beta.1 :tada:
The release is available on:

GitHub release
npm package (@beta dist-tag)

Your semantic-release bot :package::rocket:

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

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


Fixed URLs to 'Full Source' for Get and Post examples in index.html.

Links no longer lead to 'Not Found' message.

Thanks!


Support various list write operations in chip-tool

Problem
Currently, there is no way to specify the various list write operations (section <IP_ADDRESS> ListDataWriteIB) via chip-tool
Proposed Solution
@vivien-apple suggested maybe dedicated commands like:

list-replace
list-delete
list-modify
list-add

For list-replace and list-add, there should be no index param needed
For list-modify and list-delete, the indices param is needed
For list-replace, list-modify, and list-add, the entries (list contents) param is needed

Note that there is no IM-level support, and none planned for 1.0, for list-delete, list-modify, and list-add.
The only thing supported is list-replace.

Thanks @bzbarsky-apple. I'll move this out of V1.0


Closed by 8380cd8fb7dcd22cc0dcfac9396dd87774c742aa


[BUG] Fix convo

Auto catching wrong intent
   Love you >> Love you
   user msg id:  359
   Flags:  {}
   intent: ['say_hello', 'love_you']

Auto catching wrong intent

Fixed.
Reason: yo was raw string and was in "you".
Fix: using pattern "( |^)yo( |$)" # (either start of line or space) and (either end of line or space), isolating "yo"


dropping constraint on action type

Motivation and Context

What has changed

How to test?

Links

/deploy terryj

/deploy baileyw

/deploy terryj


Fix travis

More updates.
Travis now runs and reports the number of failures (which is very high mostly due to missing attributes and methods)
@albertosm27 would you rather get PRs like this or that I just push to your branch?

Thanks!
@tacaswell The way you prefer the most, I have invited you as collaborator.


2002: media.peerconnection.ice.*

/* 2002: limit WebRTC IP leaks if using WebRTC
 * [1] https://bugzilla.mozilla.org/buglist.cgi?bug_id=1189041,1297416
 * [2] https://wiki.mozilla.org/Media/WebRTC/Privacy ***/
user_pref("media.peerconnection.ice.default_address_only", true); // (FF42-FF50)
user_pref("media.peerconnection.ice.no_host", true); // (FF51+)

Both of these are being reset to default false when FF restarts. And the first one, it's not deprecated, whats the 42-50 bit about?

OK, it's uBO's  "Prevent WebRTC from leaking local IP addresses" (info icon links to here)

checked, it resets those two prefs to default false
unchecked, it sets them to false (not sure if that's directly uBO, or FF using my previous state)

With Firefox 42 and higher AND uBlock Origin 1.3.4 and higher, it is possible to prevent local IP addresses leakage without completely disabling WebRTC.

If you're wanting to actually plug leaks (and WebRTC is enabled), uBO needs those prefs in order to do its plugging leaks job  - @gorhill is that correct? Are those the only two prefs it flips? TIA

Us:

Do we need to add something here to the user.js (since uBO overrides them, it does no harm to say nothing)
We could add this info to the Prefs vs Extensions sticky
and again, what's up with the 42-50 FF versioning - is it not used in FF51+ ?

uBO uses the privacy extension API to set webRTCIPHandlingPolicy to disable_non_proxied_udp.
From the code, it seems only the config media.peerconnection.ice.proxy_only should be touched: https://searchfox.org/mozilla-central/source/toolkit/components/extensions/parent/ext-privacy.js#112.
uBO clear() when the setting is unchecked in uBO, which means that the settings should return to the state it was before uBO changed it.

My comment was how it works in Firefox 60+. Firefox 52 ESR is obsolete.

I was replying to Pants:

what's up with the 42-50 FF versioning

you added that around October 3, 2016 but without mentioning any sources:
https://www.ghacks.net/2015/08/18/a-comprehensive-list-of-firefox-privacy-and-security-settings/#comment-3990128
this bug has some related information: https://bugzilla.mozilla.org/show_bug.cgi?id=1304600
test page (but I have no idea how you'd need to test that, probably need to be in a LAN to fully test if anything leaks): https://diafygi.github.io/webrtc-ips/

Man .. I think the sooner I GitHub this, the easier to follow discussions and not miss things

Thank goodness we came to github and have records of everything now.
https://bugzilla.mozilla.org/show_bug.cgi?id=1297416 I think is the bugzilla

https://bugzilla.mozilla.org/show_bug.cgi?id=1304600#c3

default_address_only does what it says on the tin; it prevents anything but the default route from being used. In order to prevent the use of any host candidates, you could use either media.peerconnection.ice.no_host, or the more extreme media.peerconnection.ice.relay_only.

comment5

I'm wondering whether media.peerconnection.ice.no_host is the pref that we should evangelize to people concerned about leaking their internal IP address (instead of having them disable WebRTC entirely).

It depends. If they are concerned with leaking any internal address, then this is the pref they want. If they're ok with advertising the default route, but do not want to expose anything more regardless of capture permissions, then default_address_only is what they want

So that clears that up. It's still used, but not in the way it was prior to 51.
I don't think it's worth documenting uBOs behavior because there is no downside (uBO takes care of what it needs on startup).
@earthlng Do you think we could should change the FF versioning to just [FF42] and improve the description?

also use this issue for the suggestion to add a [TEST] - if you read the bugzilla in previous post francois listed one, I think we have one in the wiki, I have on my speed dial individual test page as well

switch (value) {
  case "default":
    // All prefs are already set to be reset.
    break;

  case "default_public_and_private_interfaces":
    prefs["media.peerconnection.ice.default_address_only"] = true;
    break;

  case "default_public_interface_only":
    prefs["media.peerconnection.ice.default_address_only"] = true;
    prefs["media.peerconnection.ice.no_host"] = true;
    break;

  case "disable_non_proxied_udp":
    prefs["media.peerconnection.ice.proxy_only"] = true;
    break;
}

this is from the webextension Privacy API code. The 2nd non-default case sets both prefs (same as we currently do) and the last case is what uBO does. The mozilla dev said "proxy_only" is the more extreme but I don't know exactly what the difference is

lets just bury this issue and leave it as is


Duplicating PowerBI Measure wont save

I have a PowerBI file, when I duplicate a measure inside or outside of display folders and click save I get the below error

However, if I create the new Measure in TabularEditor it saves just fine

This is a known limitation of Power BI currently (one of the reasons for the warning when you connect to an instance of Power BI).
Some users were able to work around this, by deleting all annotations and extended properties on the duplicated measures, before saving. Alternatively, save the .bpix file as a Power BI Template (.pbit), then load the pbit file directly in Tabular Editor and make the changes to that.
Closed as a duplicate of #287


[e2e-test] Enhance loginAsGithubUser() to Handle Intermittent Pop-up Visibility Issues & Fix Quay test

Description
[e2e-test] Enhance loginAsGithubUser() to Handle Intermittent Pop-up Visibility Issues & Fix Quay test
Please explain the changes you made here.
Which issue(s) does this PR fix
https://issues.redhat.com/browse/RHIDP-1396
PR acceptance criteria
Please make sure that the following steps are complete:

[ ] GitHub Actions are completed and successful
[ ] Unit Tests are updated and passing
[ ] E2E Tests are updated and passing
[ ] Documentation is updated if necessary (requirement for new features)
[ ] Add a screenshot if the change is UX/UI related

How to test changes / Special notes to the reviewer

/cherry-pick 1.1.x

@subhashkhileri you need to issue the /cherry-pick command on the original MERGED pr for main, so it will pick it to the specified branch (1.1.x). Meanwhile #997 is generated and merged.


swb: update write barrier check plugin

Recent changes required a plugin update. The plugin can no longer relies on
alloc function name containing "WithBarrier", instead should simply assume
the type being allocated needs write barrier annotation if it is not a
"Leaf" allocation, as on xplat it would be allocated in write barrier
memory. Similarly with InfoBitsWrapper, skipped "WithBarrierBit" check.
Fixed one missing annotation after merging from master by running the fixed
plugin.

@dotnet-bot test Linux tests please

@dotnet-bot test Windows x86_debug please

@dotnet-bot test Windows x86_debug please


Bad Boolean Serialization

Version: Parquet.Net v3.2.5
Runtime Version: .Net Core v 2.1
OS: Windows 10
Expected behavior
JSON Serialization should serialize boolean values as lowercase.
Actual behavior
JSON Serialization serializes boolean values with first character as Uppercase. (false --> False, true --> True).
The issue is somewhere over here boolean.ToString() returns "False" or "True".

already fixed by @CurtHagenlocher


[Threading][TSan] Fix TSan errors from lazy init on Linux.

Move the TSan functionality from Concurrency into Threading.  Use it in the Linux ulock implementation so that TSan knows about ulock and will tolerate the newer swift_once implementation that uses it.
This should also slightly improve the performance of Concurrency, since the tsan tests will be inlined rather than it always doing a subroutine call.
rdar://110665213

Note that your new tsan test is not run on the linux CI, most likely because of #53973:
UNSUPPORTED: Swift(linux-x86_64) :: Sanitizers/tsan/once.swift (6673 of 16678)

@swift-ci Please smoke test

@swift-ci Please smoke test

(Rebased to fix conflict)

@swift-ci Please smoke test

I think this version will likely fail the unit tests on Linux, because various things besides the runtime libraries use the Threading library, and not all of them link against the runtime. It looks like I'm going to need to rearrange things a little more.

@swift-ci Please smoke test

@swift-ci Please smoke test


bigtable-hbase-2.x-hadoop. Cannot create an instance of Async Connection

Environment details

Specify the API at the beginning of the title. General, Core, and Other are also allowed as types
OS type and version: Windows10
Java version: 1.8
Version(s): 1.18.0

Code example
val conf = BigtableConfiguration.asyncConfigure(BigtableConfiguration.configure(instanceId, projectId))
ConnectionFactory.createAsyncConnection(conf)

Stack trace
java.lang.RuntimeException: java.lang.RuntimeException: class org.apache.hadoop.hbase.client.BigtableAsyncRegistry not org.apache.hadoop.hbase.client.ConnectionRegistry
	at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2427)
	at org.apache.hadoop.hbase.client.ConnectionRegistryFactory.getRegistry(ConnectionRegistryFactory.java:38)
	at org.apache.hadoop.hbase.client.ConnectionFactory.createAsyncConnection(ConnectionFactory.java:284)
	at org.apache.hadoop.hbase.client.ConnectionFactory.createAsyncConnection(ConnectionFactory.java:263)
	at BigTable$$anon$1.getHbaseConnection(BigTable.scala:35)

Any additional information below
ConnectionFactory.java#CompletableFuture createAsyncConnection(Configuration conf, final User user)
contains a line
ConnectionRegistry registry = ConnectionRegistryFactory.getRegistry(conf);
I believe that should be
AsyncRegistry registry = AsyncRegistryFactory.getRegistry(conf);
Explanation: in docs to "BigtableAsyncRegistry" there is a reference to AsyncRegistryFactory, but it is never used anywhere in code and I don't see any other way to get an instance of AsyncRegistry:
 details See {@link AsyncRegistryFactory#REGISTRY_IMPL_CONF_KEY}, and {@link
 ConnectionFactory#createAsyncConnection()}

except ConnectionFactory#createAsyncConnection() doesn't use AsyncRegistryFactory

Make sure to use org.apache.hbase.shaded-client. It has this issue fixed.


Remove dead code

Codecov Report

Merging #1170 (f092f5c) into devel (8b05628) will decrease coverage by 0.03%.
The diff coverage is 100.00%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@            Coverage Diff             @@
##            devel    #1170      +/-   ##
==========================================
- Coverage   90.98%   90.95%   -0.03%
==========================================
  Files          48       48
  Lines        5634     5606      -28
==========================================
- Hits         5126     5099      -27
+ Misses        508      507       -1

Files Changed
Coverage Δ

hahomematic/platforms/custom/__init__.py
100.00% <ø> (ø)

hahomematic/const.py
100.00% <100.00%> (ø)

hahomematic/platforms/custom/light.py
98.63% <100.00%> (+0.22%)
:arrow_up:

hahomematic/platforms/device.py
81.65% <100.00%> (-0.06%)
:arrow_down:

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


[ch33451]Use sl-dialog

TODO:

TAB nav - focus trap doesn't work in our app ,but it does in the https://shoelace.style/ demos - Reintroduced focus-trap package

toast is under the backdrop --sl-z-index-dialog - FIXED in etools-toast

handle theme - Done

see if createDynamicDialog still work- Fixed

etools-dropdown - remove code related to etools-dialog

Navigation with TAB- issue with invisible focus- the dialog swallows an invisible focus with TAB

Open/close animation missing - They work only if the dialog is already in the DOM ----> openDialog method needs modifs and opened atttribute to not be present from the beginning on the dialog

When replaced in apps:

Handle notifyResize errors: this.dialogElement.notifyResize is not a function
at ActivityItemsTable.resizeDialog
See README.MD for styling replacements

Issues:

Issue with text aligned to the right


Config webpack listen

Per #4 discussion, this allows environment variables to set the hostname, listening IP, and port for npm run dev. I also tossed in a title: 'TextThresher' config for  HtmlWebpackPlugin in order to set the page title used by the template.
Examples:

WEBPACK_PORT=3003 npm run dev
WEBPACK_HOSTNAME=<IP_ADDRESS> WEBPACK_LISTEN_IP=<IP_ADDRESS> npm run dev
WEBPACK_HOSTNAME=<IP_ADDRESS> WEBPACK_LISTEN_IP=<IP_ADDRESS> npm run dev
WEBPACK_HOSTNAME=thresher.example.com WEBPACK_LISTEN_IP=<IP_ADDRESS> npm run dev

<IP_ADDRESS> is not a routable address, just a hacky shorthand for 'all adapters', so the routable address or hostname has to be specified separately.
The hostname alone is insufficient, because very often, the externally reachable IP is not on the local adapter. For example, AWS EC2 instances use a private IP address, and the publicly accessible Elastic IP is assigned externally and lives on some set of Amazon routers and routes to the private IP. So you can't bind to the public IP.

Does this change how we run it? Do we always now have to specify the PORT and HOSTNAME variables when we run npm run dev?

@JasmineDeng no those are optional. defaults to our current options.

@normangilmore nice work. remove log and 👍

@btburton42 good catch, thanks! removed.
:shipit:


Support Drawing Rectangle in XY Plot

I've got a feature request that I think several charts may want - adding an overlay that allows drawing a transparent rectangle on the chart, in order to accomplish enhanced chart features like zooming or selection.
I'm thinking a new component (e.g., DrawingArea) that only handles drawing a rectangle on the svg, triggering a callback when the user lifts the mouse with the rectangle dimensions (in the appropriate x / y units). There would have to be some standard behavior such as the rectangle disappearing after a few seconds, etc...
I think zooming is a larger can of worms, so I think this overlay would be purely for drawing. That  would allow the user to define the follow-on behavior after drawing.

react-vis' composable architecture allows you to draw arbitrary components, the API interface needs to be clarified (e.g. usage of requiresSVG class indicates that it's an element to be rendered within the SVG element), but it you can add any custom components, even custom series types.

Ah interesting, I hadn't seen that in the docs. Can you give me a quick example of drawing an arbitrary component?
Sounds like it would be possible to do it without a supported react-vis component. However looking @ the docs and source, the XY Plot in particular doesn't expose enough mouse handlers to do the drawing. In particular, onmousedown and onmouseup would have to be exposed as props on the plot.
A few other questions - is the component rendered inside of the chart area (e.g., offset by the margins)? Can the component access the domain and range to determine where the rectangle falls on the scale?

PRs welcome for any additional event handlers you need for XYPlot.
The custom component has access to props that the MarkSeries/LineSeries use to render the points. The API is designed in such a way so we can add new types of Series on the XYPlot.
We have plans to add such a use case into the documentation as a cookbook-style example.
Meanwhile, the GridLines component is an example of a non-series component that gets properties like marginLeft from XYPlot and renders using a transform. It also demonstrates how to get the scale attributes (getAttributeScale).

Awesome, thanks. I wrote a custom component to handle it, which I hope to do a PR for soon. I'm hoping other people find it useful as well to add to their plots.

I've opened a PR for adding mousedown handling + exporting AbstractSeries to make this easier.

#197 handles the original ask here.


Is e2e testing possible?

We need to have some e2e tests and part of that is to do a file upload. Using this library, is it possible to trick browser to upload a file? To be exact, we do not use the directives on an input (type=file) tag but on a div (so we can style it and everything).
The library, however, creates a file input on click and shows the default OS dialog. This makes the e2e test hard send the file path into the library's file input.

Never mind, I think I got it.

@redhead Care to share the solution?

It is still a bit of a workaround though: I do not know if it was already fixed, but in the version we are using (4.2.4), the input[type=file] used to upload the files is created by library and appended to body when directive is added to the DOM, not after clicking on it. So in our tests we take that input in body, make it visible (through executeScript), then we call sendKeys on it with path to a file we want to upload and the directive does the rest. Then we hide the  input again.
The downside is that in this version the input doesn't get removed from body after directive's scope is destroyed, so I made a ngfSelect "override" directive which removes the element correctly after itself:
$scope.$on('$destroy', function () {
	if ($element.__ngf_ref_elem__) {
		$element.__ngf_ref_elem__.remove();
	}
});

@redhead Thanks for the help!


IGAPP-334: Setup flipper

This pull request belongs to an issue on our bugtracker.
You can find it there by looking for an issue with the key which is mentioned in the title of this pull request.
It starts with the keyword IGAPP.

I've had the the following issue
java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libflipper.so caused by: dlopen failed: library "libevent_extra-2.1.so" not found result: 0

with this solution: https://github.com/facebook/flipper/issues/824#issuecomment-611868592 + restarting the emulator

@maxammann from the page you linked: These instructions are aimed at people manually adding Flipper to a React Native 0.62+ app. This should only be necessary if you have an existing app that cannot be upgraded with the React Native Upgrade tool.
This is not necessary for us :) Or rather, it is already done.

@maxammann any idea why no sourcemap is generated on ios here? react native upgrade?


12/20/2022 Publish

Learn Build status updates of commit f40d883:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs-ref-conceptual/azure-cli-extensions-list.md
:warning:Warning
View
Details

latest/docs-ref-autogen/ams/asset.yml
:bulb:Suggestion
View (azure-cli-latest)
Details

latest/docs-ref-autogen/mariadb/server.yml
:bulb:Suggestion
View (azure-cli-latest)
Details

latest/docs-ref-autogen/mysql/flexible-server.yml
:bulb:Suggestion
View (azure-cli-latest)
Details

latest/docs-ref-autogen/mysql/server.yml
:bulb:Suggestion
View (azure-cli-latest)
Details

latest/docs-ref-autogen/postgres/flexible-server.yml
:bulb:Suggestion
View (azure-cli-latest)
Details

latest/docs-ref-autogen/postgres/server.yml
:bulb:Suggestion
View (azure-cli-latest)
Details

2017-03-09-profile/docs-ref-autogen/aks.yml
:white_check_mark:Succeeded
View (azure-cli-2017-03-09-profile)

2017-03-09-profile/docs-ref-autogen/aks/nodepool.yml
:white_check_mark:Succeeded
View (azure-cli-2017-03-09-profile)

2017-03-09-profile/docs-ref-autogen/billing-benefits.yml
:white_check_mark:Succeeded
View (azure-cli-2017-03-09-profile)

2017-03-09-profile/docs-ref-autogen/billing-benefits/reservation-order-aliases.yml
:white_check_mark:Succeeded
View (azure-cli-2017-03-09-profile)

2017-03-09-profile/docs-ref-autogen/billing-benefits/savings-plan.yml
:white_check_mark:Succeeded
View (azure-cli-2017-03-09-profile)

2017-03-09-profile/docs-ref-autogen/billing-benefits/savings-plan-order.yml
:white_check_mark:Succeeded
View (azure-cli-2017-03-09-profile)

2017-03-09-profile/docs-ref-autogen/billing-benefits/savings-plan-order/savings-plan.yml
:white_check_mark:Succeeded
View (azure-cli-2017-03-09-profile)

2017-03-09-profile/docs-ref-autogen/billing-benefits/savings-plan-order-aliases.yml
:white_check_mark:Succeeded
View (azure-cli-2017-03-09-profile)

2017-03-09-profile/docs-ref-autogen/reference-index.yml
:white_check_mark:Succeeded
View (azure-cli-2017-03-09-profile)

2017-03-09-profile/docs-ref-autogen/service-page/Azure Billing Benefits.yml
:white_check_mark:Succeeded
View (azure-cli-2017-03-09-profile)

2017-03-09-profile/docs-ref-autogen/TOC.yml
:white_check_mark:Succeeded
View (azure-cli-2017-03-09-profile)

2018-03-01-hybrid/docs-ref-autogen/aks.yml
:white_check_mark:Succeeded
View (azure-cli-2018-03-01-hybrid)

2018-03-01-hybrid/docs-ref-autogen/aks/nodepool.yml
:white_check_mark:Succeeded
View (azure-cli-2018-03-01-hybrid)

2018-03-01-hybrid/docs-ref-autogen/billing-benefits.yml
:white_check_mark:Succeeded
View (azure-cli-2018-03-01-hybrid)

2018-03-01-hybrid/docs-ref-autogen/billing-benefits/reservation-order-aliases.yml
:white_check_mark:Succeeded
View (azure-cli-2018-03-01-hybrid)

2018-03-01-hybrid/docs-ref-autogen/billing-benefits/savings-plan.yml
:white_check_mark:Succeeded
View (azure-cli-2018-03-01-hybrid)

2018-03-01-hybrid/docs-ref-autogen/billing-benefits/savings-plan-order.yml
:white_check_mark:Succeeded
View (azure-cli-2018-03-01-hybrid)

2018-03-01-hybrid/docs-ref-autogen/billing-benefits/savings-plan-order/savings-plan.yml
:white_check_mark:Succeeded
View (azure-cli-2018-03-01-hybrid)

This comment lists only the first 25 files in the pull request.

docs-ref-conceptual/azure-cli-extensions-list.md

Line 41, Column 2: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/azure/azure-arc/data/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 41, Column 113: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/azure/azure-arc/data/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 41, Column 2: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-us/azure/azure-arc/data/' will be broken in isolated environments. Replace with a relative link.
Line 41, Column 113: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-us/azure/azure-arc/data/' will be broken in isolated environments. Replace with a relative link.
Line 46, Column 2: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/python/api/overview/azure/ml/?view=azure-ml-py' will be broken in isolated environments. Replace with a relative link.
Line 46, Column 2: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL.  Otherwise, remove the view parameter. URL: https://docs.microsoft.com/python/api/overview/azure/ml/?view=azure-ml-py
Line 46, Column 167: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/python/api/overview/azure/ml/?view=azure-ml-py/HISTORY.rst' will be broken in isolated environments. Replace with a relative link.
Line 46, Column 167: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL.  Otherwise, remove the view parameter. URL: https://docs.microsoft.com/python/api/overview/azure/ml/?view=azure-ml-py/HISTORY.rst

latest/docs-ref-autogen/ams/asset.yml

Line 267, Column 93: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'indexToRemove' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 274, Column 116: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'value' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

latest/docs-ref-autogen/mariadb/server.yml

Line 79, Column 202: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'SingleIP' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 79, Column 214: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'StartIP-DestinationIP' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 468, Column 202: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'SingleIP' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 468, Column 214: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'StartIP-DestinationIP' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 472, Column 93: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'indexToRemove' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 479, Column 116: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'value' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

latest/docs-ref-autogen/mysql/flexible-server.yml

Line 819, Column 93: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'indexToRemove' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 829, Column 116: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'value' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

latest/docs-ref-autogen/mysql/server.yml

Line 79, Column 202: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'SingleIP' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 79, Column 214: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'StartIP-DestinationIP' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 468, Column 202: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'SingleIP' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 468, Column 214: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'StartIP-DestinationIP' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 472, Column 93: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'indexToRemove' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 479, Column 116: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'value' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

latest/docs-ref-autogen/postgres/flexible-server.yml

Line 743, Column 93: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'indexToRemove' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

This comment lists only the first 25 errors (including error/warning/suggestion) in the pull request.
For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Learn Build.
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.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel


Add Python CLI for Gmail

This is a script to manage your Gmail inbox right from your terminal!

For #37 and #65.

Now I've fixed some silly issues and make the code in some scripts little more documented and syntactically standard.


Update known issues in search docs

As reported here: https://mattermost.atlassian.net/browse/PLT-4060

+1

@jasonblais, can you clarify this a little more? It seems like the issue is that the dash is ignored?

+1


Add a well-known endpoint for catalog requests

A participant catalog may contain protected Datasets that require some proof to access. The mechanism for preseting a proof during a catalog request is outside the scope of the DSP Catalog Specification and should be detailed in a separate trust specification. For example, a trust specification may rely on W3C Verifiable Credentials and Verifiable Presentations as proof.
However, all trust specifications will require a mechanism for a client to discover which proof mechanisms are required to access protected catalog Datasets. The format of this metadata is specific to the trust specification, but the endpoint should be defined using a Well-Known Uniform Resource Identifiers.
The proposal is to add the following endpoint to the catalog specification:
/.well-known/dspace-trust
The contents of the response is a JSON object defined by individual trust specifications.

Task 1:

[ ] Verify whether  https://example.com/path-to-my-connector/.well-known/ is explicitly prohibited by the RFC.

Task 2: Decide on pattern for catalog vs. general trust information:
https://example.com/.well-known/dspace-catalog-trust
https://example.com/.well-known/dspace-trust
--> Decision: This is the pattern we want to use.

@sebbader-sap  means RFC 8615

We might want to add a note on multiple connectors under the same URI:

Connectors could use different sub-domains, but if they are not using sub-domains, then
probably the well-known endpoint cannot be used

We might want to add a note on multiple connectors under the same URI:

Connectors could use different sub-domains, but if they are not using sub-domains, then
probably the well-known endpoint cannot be used

They could use this by appending a path segment to the base well-known URL. Section 3 states:

Registrations MAY also contain additional information, such as the
syntax of additional path components, query strings, and/or fragment
identifiers to be appended to the well-known URI, or protocol-
specific details (e.g., HTTP [RFC7231] method handling).

So, for example, a connector URL of https://example.com/connector1 could use:
https://example.com/.well-known/dspace-trust/connector1


Tabs in mobile version auto expanded

Tabs and Tab component in mobile browser could be auto-expanded
Detailed description

Is this issue related to a specific component?
Tabs component

What did you expect to happen? What happened instead? What would you like to see changed?

I go to:
http://react.carbondesignsystem.com/?selectedKind=Tabs&selectedStory=Default&full=0&addons=1&stories=1&panelRight=0&addonPanel=storybook%2Factions%2Factions-panel

Select Tab 1 by default.

Select Tab 3.

Narrow the browser so it is in mobile version.  The tabs become a dropdown list.
Note the list is auto-expanded.

I expect the list is collapsed at the beginning until I click on it.

What browser are you working in?
FF but same for other browsers.

What version of the Carbon Design System are you using?
"carbon-components": "^8.18.3",
"carbon-components-react": "^5.41.0",

What offering/product do you work on? Any pressing ship or release dates we should be aware of?
console

(I don't seem to see any labels that I can choose)

this one is making the new docs homepage design not look great in Mobile...and hindering the view of content.

Instead of collapsed by default, it is expanded.


expose ExpressionField, and use slots for several class

Great Job. But the GA is not ok, just fix it and it is ok to me.

GA ?

Github Action lol

I'm sorry, but I still don't get what issue this is trying to solve... Are there any usage examples or benchmarks where this is proven to be faster than it currently is?


Peering statistics

Is your feature request related to a problem? Please describe.
One of the main features of this app is ability to provide your resources to help network perform better. But user have no visual indication of this process. He can't know if he was able to help someone to view some videos or not.
Describe the solution you'd like
App should show at least how much data was uploaded to peers. Per session and per installation.
Single number (MiB, GiB) should be fine, charts would be even better.
More detalized approach is to show such info per every shared video.
For example, near every list item at Library tab.
In such case user can analyze which videos are most popular and find more similar content to share.
Describe alternatives you've considered
It is possible to watch network statistics with third party programs like resmon, Process Explorer, DU Meter.
But their data is harder to analyze and it lacks detalization.

Huge +1! This seems even more important in the absence of LBC compensation for helping the network. Currently, the reward is much more abstract, and this would help reinforce what reward there is.

This ticket could use data currently available in lbrynet status, but does not have file-specific information at this time.
  "blob_manager": {
    "connections": {
      "incoming_bps": {},
      "max_incoming_mbs": 5.772843,
      "max_outgoing_mbs": 0.00589,
      "outgoing_bps": {},
      "total_incoming_mbs": 0.0,
      "total_outgoing_mbs": 0.0,
      "total_received": 214932306,
      "total_sent": 43660
    },
    "finished_blobs": 462
  },

yes please, i've asked for this for years.


fix: prioritize nft.metadata rather than nft.meta.id

Thank you for your contribution to the Koda - Generative Art Marketplace.
👇 __ Let's make a quick check before the contribution.
PR Type

[x] Bugfix

Context

Fix #9987

nft.metadata and nft.meta.id return different results:
{
  "data": {
    "nftEntityById": {
      "id": "115-2404377033",
      "metadata": "https://fxart-beta.kodadot.workers.dev/metadata/v1/json?chain=ahp&collection=115&nft=2404377033&metadata=ipfs:%2F%2Fbafybeid6qweu5csznxnfa26aundrrdejg3l3sfiyhotpbokbt5hvm347ze%2F2.json",
      "meta": {
        "id": "ipfs://bafkreih2bq7dqqmtz4xqhfdjbo6wsyr6ozfhtvn4dyqkeokggmtrrrrw3i"
      }
    }
  }
}

the correct one is nft.metadata. in this PR prioritize fetch nft.metadata instead of nft.meta.id
Did your issue had any of the "$" label on it?

[x] My DOT address: Payout

Screenshot 📸

[x] My fix has changed something on UI; a screenshot is best to understand changes for others.

nice that there is a solution, thank you!

I am not fan of this solution, as it is better to investigate why is it happening

pay 50

😍 Perfect, I’ve sent the payout
💵 $50 @ 8.28 USD/DOT ~ 6.039 $DOT
🧗 1xjvRADwdJcnmUCLWerEHR4iGCT5EBTm4D4fzLLg4LcAC9p
🔗 0x690f368700df7f453be1bae1719bd40db18a90093784ca57d293243d2300d724
🪅 Let’s grab another issue and get rewarded!
🪄 github.com/kodadot/nft-gallery/issues


fixed typo in class definition of shell command module

Running nanoc shell was producing the following error:
NoMethodError: undefined method `env_for_site' for Nanoc::CLI::Commands::Shell:Class
I changed the method env_for to env_for_site and now everything works fine.

Thanks for the fix!
The way the CLI is tested right now is unfortunately a little brittle. I’ll look into improving this, so that every command is tested at least on a high level by ensuring that invoking the command works.

I’ve opened #672 which contains this fix + a high-level test.


Improved UI and refactoring

This work in progress PR implements some of the suggestions from #10. Once finished, this will also fix #22 and #28.
I moved and refactored the graph editing code into a separate GraphEditPanel accessible via a tab widget and updated the UI.
Also various other bits and pieces:

[x] Move graph manipulation and undo stack out of the GraphScene
[x] Selection UI for current vertex type that is added via right click
[x] Selection UI for current edge type that is added via right drag
[x] Draw edge when dragging
[x] Update vertex locations in graph when moving (fixes issue where nodes "jump back" into their old position after applying rewrite)
[x] Make moving of vertices undoable
[ ] Hook up import/export/reset buttons
[ ] UI to change vertex type (double-click on button like tikzit?)
[ ] UI to change phase (double-click on vertex)
[x] Proof panel
[ ] Remove old code

This is still work in progress, but comments are welcome (in particular regarding UI)

Is highlighting multiple nodes hard to add?

I just pulled this, it looks like there is only the edit panel, and there is no rewrite panel. Is that correct?
Also, while this is already present in the main branch, it is particularly noticable here, which is that if you drag stuff, it leaves an after-image:

Any idea what this might be caused by?

Also, when you click a node, but you move your mouse (even just a single pixel), then it doesn't select the node. It looks like it is implemented that selection happens the moment you press down the mouse button. Is there instead a mouse-click event that can be used?

This might be too much for this PR, but considering #23, we should be considering https://doc.qt.io/qt-6/qgraphicsitem.html#setSelected
and the https://doc.qt.io/qt-6/qgraphicsitem.html#GraphicsItemFlag-enum flags ItemIsMovable and ItemIsSelectable. It looks like all the standard features we want are just part of Qt.

I just pulled this, it looks like there is only the edit panel, and there is no rewrite panel. Is that correct?

Yes, I just added the proof panel. Still work in progress :D

if you drag stuff, it leaves an after-image

That's interesting, I don't see it on my machine. I'm using MacOS, are you on Linux/Windows? Maybe it's some anti-aliasing issue?

Killing the selection when you move a vertex is probably undesirable behaviour anyway.

True, but selection needs to be redone anyways so we could probably leave that to another PR as you said

@y-richie-y

Is highlighting multiple nodes hard to add?

I think highlighting multiple nodes is already implemented? I did not touch the selection code

There is highlighting of multiple nodes, but not dragging of multiple nodes. In any case that will probably be dealt with once we use the built-in methods for that

Ok, this PR should be ready for review now

@mark-koch you seem to have the same problem as me in #30. If you drag a node, and then do to_gh, you can't undo the drag anymore.

Changing panel undoes the selection, can we not have that?

I added the color change rule and made it so that selection is maintained when changing tabs.


Revert all changes since "update deps", and make tests run a build before passing

Tests passed, which should (now) mean that the deploy will be successful. Hopefully.


decoder: pre-processed Arg (e.g. real structs instead of nested format strings)

The existing Format (and the upcoming FormatSlice) variants are a bit problematic/annoying because they require re-parsing the format string during display and (further) serialization.
If instead we assume that Arg will either be a primitive, a struct or a enum (the last two could recursively contain a struct or enum but ultimately contain primitives) then we can pre-process the Arg and flatten it in some cases.
A flattened Arg variant may look like this:
// (more optimized representations are possible:
//  e.g. interned strings or interned struct layouts)
enum Val<'t> {
    Ixx(i64),
    Uxx(u64),
    Bool(bool),
    F32(f32),
    Struct {
        name: String,
        fields: HashMap<String, Val>,
    },
    // Enum, etc.
}

This structure is easier to print and serialize, into say JSON, for inter-op with front-ends.
With this representation, data like this:
info!("x={:?}", 42u8);
[
    $index1, // "x={:?}"
    $index2, // "{:u8}"
    42,
]

can be processed into Val::Uxx(42) (last two bytes) -- today that would be Arg::Format { format: "{:u8}", args: [Arg::Uxx(8)] }
And data like this:
[
    $index1, // "X {{ y: {:?} }}"
    $index2, // "Y {{ z: {:u8} }}"
    42,
]

can be decoded into (hypothetical hash map literal) Struct { name: "X", fields: { "y": Struct { name: "Y", fields: { "z": Uxx(42) } }  } } -- today that's two nested Arg::Format values
Then log frames can become something like this:
struct Frame<'t> {
    pub level: Level,
    // Processed format string
    pub pieces: Vec<Piece<'t>>,
    pub timestamp: u64,
    pub args: Vec<Val<'t>>,
}

enum Piece<'t> {
    Str(&'t str),
    // index into `self.args` (simplified: bitfields make this more complex)
    Param(usize),
}

But to make this work we need to constrain Format implementations.
Right now they can be too free-form because write! is public.
The user could write:
struct S {
    x: u8,
}

impl Format {
    fn format(&self, f: &mut Formatter) {
        write!(f, "S; x = {:u8};", self.x)
    }
}

The chosen format string wouldn't match the decoder expectation (S {{ x: {:u8} }}) and it would not be possible to process it as a Val::Struct
To avoid that issue we can remove write! from the public API and instead provide customization of the Format implementation through attributes (like serde does)
.
For example, #[rename] could be used to rename fields and #[skip] could be used to skip fields.
// "S {{ loop: {:u8} }}"
#[derive(Format)]
struct S {
    #[rename = "loop"]
    _loop_: u8,
    #[skip]
    secret_key: [u8; 16],
}

Thoughts? @jonas-schievink

I think we can close this – structural logging can now be implemented using the defmt_derive tag, while we also have manual Format impls that can use write!.


compare command in Last.fm plugin is broken

"Unable to connect to Last.fm"

Well, as far as I can tell, Last.fm's API is telling me that the method no longer exists. I tried accessing their API docs and am getting a "502 Bad Gateway" error. Perhaps due to this: https://getsatisfaction.com/lastfm/topics/new-site-launch-temporary-service-disruption-information
Waiting on the docs to go back up so I can look into this further.

https://getsatisfaction.com/lastfm/topics/api-known-issues
Others have commented with the same problem.

It would appear that the Taste-o-meter has been removed from the Last.fm website as well, however there are plans to bring it back in the future.
https://getsatisfaction.com/lastfm/topics/sad-angry
https://getsatisfaction.com/lastfm/topics/user-compatibility
I will leave this issue open until that time.


Fix code scanning alert - Full server-side request forgery

Tracking issue for:

[x] https://github.com/zivenyang/osscs/security/code-scanning/1

fixed


Country flag

Would it be possible to add multiple methods to obtaining GeoIP information, or a more reliable way to obtain the information?  There are times where getting the GeoIP information doesn't work very well and the image flag isn't retrieved.  This has been happening often lately.
Also, not sure if this is intended but the country flag is located in the User@PC column.  Should it be located in the IP Address column?

Fixed the small bug, yes maybe one more. :)

Sounds good, thanks. :)


Server available as well ?

Interesting use case, do you have the server part as well ? I mean how do you publish the sensor data from Raspberry.
Btw, If you really want that I'll do a look why gesture is not working for you, you should open a ticket in my AndroidChart repo, I do not maintain dead MPAndroidChart

I don't have the server in Android. It's server agnostic as long as it's set up to publish raw binary data.
For ESP32, I'm using their example https://github.com/espressif/esp-idf/tree/master/examples/protocols/sockets/tcp_server.
For Pi Pico, https://github.com/raspberrypi/pico-examples/tree/master/pico_w/tcp_server was used.

The issue I was having a few months ago is fixed in your fork. Cannot reproduce it now. So I've switched MPAndroidChart to your fork. Thanks for maintaining it.

I see you also set up MideaPipe to work on Android. Nice.

I don't have the server in Android

Sure, the server is no Android stuff. But thanks for the pointers. In the past I did some websocket experiments. But I don't have that background knowledge, what's the benefit of TCPIP, so I want to see the code, maybe I understand then, what exactly TCPIP communication means.

Cannot reproduce it now.

This is my issue too 😀

Btw, please clarify the situation here as well https://github.com/PhilJay/MPAndroidChart/pull/5302


Attribute changelog_file not having an effect

Running python-semantic-release==9.7.1 as a part of a Gitlab CI/CD pipeline always creates the changelog file named CHANGELOG.md in the root of the repository, no matter what I specify in the changelog_file attribute of the pyproject.toml file.
As described in the documentation, by using the changelog_file attribute in the [tool.semantic_release.changelog] part of the pyproject.toml configuration file, one is suppose to be able to specify a name for the changelog file to be created by python-semantic-release.
My initial thought was to use this attribute to put the changelog file in a subdirectory. E. g. changelog_file = "./docs/CHANGELOG.md".
When this didn't work, out of curiosity I've tried to just change the name of the resulting changelog file and not the location. E.g. changelog_file = "REALLY_COOL_CHANGELOG.md". Still, changelog file that is created is simply named CHANGELOG.md which is also the default value.
I'm running python-semantic-release as a job in a GitLab CI/CD pipeline inside a Docker container based on Debian GNU/Linux 10 (buster).
python --version -> 3.11.4
pip --version -> 24.0
semantic-release --version -> 9.7.1

Same behavior happens regardless of using poetry or pip + requirements.txt
Configuration
[tool.semantic_release]
version_toml = ["pyproject.toml:tool.poetry.version"]
assets = []
commit_message = "{version}\n\nAutomatically generated by python-semantic-release"
commit_parser = "angular"
logging_use_named_masks = false
hvcs = "gitlab"
major_on_zero = true
tag_format = "v{version}"

[tool.semantic_release.branches.main]
match = "(main|master)"
prerelease_token = "rc"
prerelease = false
hvcs = "gitlab"

[tool.semantic_release.changelog]
template_dir = "templates"
changelog_file = "PRETTY_COOL_CHANGELOG.md"
exclude_commit_patterns = []

[tool.semantic_release.remote]
type = "gitlab"

[tool.semantic_release.remote.token]
env = "GROUP_GITLAB_TOKEN"

[tool.semantic_release.changelog.environment]
block_start_string = "{%"
block_end_string = "%}"
variable_start_string = "{{"
variable_end_string = "}}"
comment_start_string = "{#"
comment_end_string = "#}"
trim_blocks = false
lstrip_blocks = false
newline_sequence = "\n"
keep_trailing_newline = false
extensions = []
autoescape = true

Logs
semantic-release -vv version

[12:10:43] DEBUG    [semantic_release.cli.commands.main] DEBUG       main.py:105
                    main.main: logging level set to: DEBUG
           DEBUG    [git.util] DEBUG util.is_cygwin_git: Failed      util.py:439
                    checking if running in CYGWIN due to:
                    FileNotFoundError(2, 'No such file or
                    directory')
           DEBUG    [semantic_release.cli.commands.main] DEBUG       main.py:123
                    main.main: global cli options:
                    GlobalCommandLineOptions(noop=False,
                    verbosity=2, config_file='pyproject.toml',
                    strict=False)
           INFO     [semantic_release.cli.util] INFO                  util.py:78
                    util.load_raw_config_file: Loading configuration
                    from pyproject.toml
           DEBUG    [semantic_release.cli.util] DEBUG                 util.py:81
                    util.load_raw_config_file: Trying to parse
                    configuration pyproject.toml in TOML format
           INFO     [semantic_release.cli.config] INFO             config.py:238
                    config.select_branch_options: Using group
                    'main' options, as '(main|master)' matches
                    'master'
           DEBUG    [semantic_release.hvcs.util] DEBUG                util.py:48
                    util.build_requests_session: setting up default
                    session authentication
           DEBUG    [semantic_release.changelog.template] DEBUG   template.py:55
                    template.environment: {'template_dir':
                    'templates', 'block_start_string': '{%',
                    'block_end_string': '%}',
                    'variable_start_string': '{{',
                    'variable_end_string': '}}',
                    'comment_start_string': '{#',
                    'comment_end_string': '#}',
                    'line_statement_prefix': None,
                    'line_comment_prefix': None, 'trim_blocks':
                    False, 'lstrip_blocks': False,
                    'newline_sequence': '\n',
                    'keep_trailing_newline': False, 'extensions':
                    (), 'autoescape': True, 'autoescape_value':
                    True}
           DEBUG    [semantic_release.version.translator] DEBUG translator.py:40
                    translator._invert_tag_format_to_re:
                    inverted tag_format 'v{version}' to
                    'v(?P<version>.*)'
           DEBUG    [semantic_release.cli.masking_filter]   masking_filter.py:30
                    DEBUG masking_filter.add_mask_for:
                    Adding redact pattern
                    'context.hvcs_client.token' to
                    _redact_patterns
           DEBUG    [semantic_release.cli.masking_filter]   masking_filter.py:30
                    DEBUG masking_filter.add_mask_for:
                    Adding redact pattern
                    'context.hvcs_client.token' to
                    _redact_patterns
           DEBUG    [semantic_release.cli.commands.version] DEBUG  version.py:47
                    version.is_forced_prerelease: force_prerelease
                    = False, force_level = None, prerelease =
                    False
           DEBUG    [semantic_release.version.version] DEBUG      version.py:121
                    version.parse: attempting to parse string
                    '0.1.0' as Version
           DEBUG    [semantic_release.version.version] DEBUG      version.py:145
                    version.parse: version string 0.1.0 parsed as
                    a non-prerelease
           DEBUG    [semantic_release.version.version] DEBUG      version.py:148
                    version.parse: parsed build metadata '' from
                    version string 0.1.0
           DEBUG    [semantic_release.version.version] DEBUG      version.py:121
                    version.parse: attempting to parse string
                    '0.1.1' as Version
           DEBUG    [semantic_release.version.version] DEBUG      version.py:145
                    version.parse: version string 0.1.1 parsed as
                    a non-prerelease
           DEBUG    [semantic_release.version.version] DEBUG      version.py:148
                    version.parse: parsed build metadata '' from
                    version string 0.1.1
           DEBUG    [semantic_release.version.version] DEBUG      version.py:121
                    version.parse: attempting to parse string
                    '0.1.2' as Version
           DEBUG    [semantic_release.version.version] DEBUG      version.py:145
                    version.parse: version string 0.1.2 parsed as
                    a non-prerelease
           DEBUG    [semantic_release.version.version] DEBUG      version.py:148
                    version.parse: parsed build metadata '' from
                    version string 0.1.2
           DEBUG    [semantic_release.version.version] DEBUG      version.py:121
                    version.parse: attempting to parse string
                    '0.2.0' as Version
           DEBUG    [semantic_release.version.version] DEBUG      version.py:145
                    version.parse: version string 0.2.0 parsed as
                    a non-prerelease
           DEBUG    [semantic_release.version.version] DEBUG      version.py:148
                    version.parse: parsed build metadata '' from
                    version string 0.2.0
           DEBUG    [semantic_release.version.version] DEBUG      version.py:121
                    version.parse: attempting to parse string
                    '0.3.0' as Version
           DEBUG    [semantic_release.version.version] DEBUG      version.py:145
                    version.parse: version string 0.3.0 parsed as
                    a non-prerelease
           DEBUG    [semantic_release.version.version] DEBUG      version.py:148
                    version.parse: parsed build metadata '' from
                    version string 0.3.0
           INFO     [semantic_release.version.algorithm] INFO    algorithm.py:60
                    algorithm.tags_and_versions: found 5
                    previous tags
           INFO     [semantic_release.version.algorithm] INFO   algorithm.py:255
                    algorithm.next_version: Found 5 full
                    releases (excluding prereleases)
           DEBUG    [semantic_release.version.version] DEBUG      version.py:121
                    version.parse: attempting to parse string
                    '0.0.0' as Version
           DEBUG    [semantic_release.version.version] DEBUG      version.py:145
                    version.parse: version string 0.0.0 parsed as
                    a non-prerelease
           DEBUG    [semantic_release.version.version] DEBUG      version.py:148
                    version.parse: parsed build metadata '' from
                    version string 0.0.0
           INFO     [semantic_release.version.algorithm] INFO   algorithm.py:277
                    algorithm.next_version: The last full
                    release was 0.3.0, tagged as 'v0.3.0'
           DEBUG    [git.cmd] DEBUG cmd.execute: Popen(['git',        cmd.py:978
                    'merge-base', 'v0.3.0', 'master'],
                    cwd=/builds/username/test-cicd, stdin=None,
                    shell=False, universal_newlines=False)
           DEBUG    [git.cmd] DEBUG cmd.execute: Popen(['git',        cmd.py:978
                    'cat-file', '--batch-check'],
                    cwd=/builds/username/test-cicd, stdin=<valid
                    stream>, shell=False, universal_newlines=False)
           DEBUG    [git.cmd] DEBUG cmd.execute: Popen(['git',        cmd.py:978
                    'cat-file', '--batch'],
                    cwd=/builds/username/test-cicd, stdin=<valid
                    stream>, shell=False, universal_newlines=False)
           DEBUG    [semantic_release.version.algorithm] DEBUG   algorithm.py:89
                    algorithm.bfs: checking if tag 'v0.3.0'
                    (c5bc21de87f9da03f99d8[221](https://some-gitlab.company.com/username/test-cicd/-/jobs/825662#L221)a1433b75cc75602e)
                    matches commit
                    c5bc21de87f9da03f99d8221a1433b75cc75602e
           INFO     [semantic_release.version.algorithm] INFO    algorithm.py:96
                    algorithm.bfs: found latest version in
                    branch history: '0.3.0' (c5bc21d)
           INFO     [semantic_release.version.algorithm] INFO   algorithm.py:115
                    algorithm._bfs_for_latest_version_in_histor
                    y: the latest version in this branch's
                    history is 0.3.0
           INFO     [semantic_release.version.algorithm] INFO   algorithm.py:302
                    algorithm.next_version: The last full
                    version in this branch's history was 0.3.0
           DEBUG    [git.cmd] DEBUG cmd.execute: Popen(['git',        cmd.py:978
                    'rev-list', 'v0.3.0...', '--'],
                    cwd=/builds/username/test-cicd, stdin=None,
                    shell=False, universal_newlines=False)
           DEBUG    [semantic_release.version.algorithm] DEBUG  algorithm.py:374
                    algorithm.next_version: parsed the
                    following distinct levels from the commits
                    since the last release: set()
           INFO     [semantic_release.version.algorithm] INFO   algorithm.py:380
                    algorithm.next_version: The type of the
                    next release release is: no_release
           INFO     [semantic_release.version.algorithm] INFO   algorithm.py:382
                    algorithm.next_version: No release will be
                    made
0.3.0
           DEBUG    [semantic_release.version.version] DEBUG      version.py:121
                    version.parse: attempting to parse string
                    '0.1.0' as Version
[12:10:44] DEBUG    [semantic_release.version.version] DEBUG      version.py:145
                    version.parse: version string 0.1.0 parsed as
                    a non-prerelease
           DEBUG    [semantic_release.version.version] DEBUG      version.py:148
                    version.parse: parsed build metadata '' from
                    version string 0.1.0
           DEBUG    [semantic_release.version.version] DEBUG      version.py:121
                    version.parse: attempting to parse string
                    '0.1.1' as Version
           DEBUG    [semantic_release.version.version] DEBUG      version.py:145
                    version.parse: version string 0.1.1 parsed as
                    a non-prerelease
           DEBUG    [semantic_release.version.version] DEBUG      version.py:148
                    version.parse: parsed build metadata '' from
                    version string 0.1.1
           DEBUG    [semantic_release.version.version] DEBUG      version.py:121
                    version.parse: attempting to parse string
                    '0.1.2' as Version
           DEBUG    [semantic_release.version.version] DEBUG      version.py:145
                    version.parse: version string 0.1.2 parsed as
                    a non-prerelease
           DEBUG    [semantic_release.version.version] DEBUG      version.py:148
                    version.parse: parsed build metadata '' from
                    version string 0.1.2
           DEBUG    [semantic_release.version.version] DEBUG      version.py:121
                    version.parse: attempting to parse string
                    '0.2.0' as Version
           DEBUG    [semantic_release.version.version] DEBUG      version.py:145
                    version.parse: version string 0.2.0 parsed as
                    a non-prerelease
           DEBUG    [semantic_release.version.version] DEBUG      version.py:148
                    version.parse: parsed build metadata '' from
                    version string 0.2.0
           DEBUG    [semantic_release.version.version] DEBUG      version.py:121
                    version.parse: attempting to parse string
                    '0.3.0' as Version
           DEBUG    [semantic_release.version.version] DEBUG      version.py:145
                    version.parse: version string 0.3.0 parsed as
                    a non-prerelease
           DEBUG    [semantic_release.version.version] DEBUG      version.py:148
                    version.parse: parsed build metadata '' from
                    version string 0.3.0
           INFO     [semantic_release.version.algorithm] INFO    algorithm.py:60
                    algorithm.tags_and_versions: found 5
                    previous tags
No release will be made, 0.3.0 has already been released!
           INFO     [semantic_release.cli.github_act github_actions_output.py:70
                    ions_output] INFO
                    github_actions_output.write_if_p
                    ossible: not writing GitHub
                    Actions output, as no file
                    specified

Additionally, even though messages in the log above suggest that "No release will be made" the 0.3.0 release is indeed made as it should be in this demo case because previous version was 0.2.0 and feat commits were made in the meanwhile.
A custom template for the changelog file is used and the changelog created by the python-semantic-release is indeed based on that custom template, however it is not named correctly.
Obviously I've changed a few details in the presented pyproject.toml and log output because we are using python-semantic-release as a part of a private, company repository.
Am I doing something wrong or is this a bug?

Initially, if you are using the custom template directory (and the directory exists) then the changelog_file config option is unused. If you change the name of your template to a different name it should replicate the name from the template directory.

Ok, now everything makes sense.
Thank you very much! :)


feat : Support Leaky-ReLU Activation

Added support for Leaky-RELU activation function to the OpenCL kernel
Leaky-RELU uses parameter a as the negative slope.

TODO:

Add NEON implementation for Leaky-RELU.

Hello @gplhegde,
We have already added leaky relu support internally and it will be part of the next release.

Support of leaky relu was added in latest release v17.09. Closing this issue. Reopen if needed


Homebridge v2.0

Describe Your Problem:

Just got message:
homebridge-alphaess might not be ready for Homebridge v2.0
it is problem?
Logs:
Show the Homebridge logs here, remove any sensitive information.

Plugin Config:
Show your Homebridge config.json here, remove any sensitive information.

Screenshots:

Environment:

Plugin Version:
Homebridge Version:
Node.js Version:
NPM Version:
Operating System:

i havent tried, did you ?

Hi,
Probably due big update, sometimes even app does not show values.
From: zerwuff @.>
Sent: Monday, October 14, 2024 11:00 AM
To: zerwuff/homebridge-alphaess @.>
Cc: CharlieVD @.>; Author @.>
Subject: Re: [zerwuff/homebridge-alphaess] Homebridge v2.0 (Issue #17)
i havent tried, did you ?
—
Reply to this email directly, view it on GitHub https://github.com/zerwuff/homebridge-alphaess/issues/17#issuecomment-2410508077 , or unsubscribe https://github.com/notifications/unsubscribe-auth/BH7IC5WGM4DMEVTWPXSS5RLZ3OBX3AVCNFSM6AAAAABOCWVET6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMJQGUYDQMBXG4 .
You are receiving this because you authored the thread.  https://github.com/notifications/beacon/BH7IC5WJEBXOVCV6JH7VSRLZ3OBX3A5CNFSM6AAAAABOCWVET6WGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTUPVVXS2.gif Message ID: @.*** @.***> >


updated mechanics

required .step files for mechanics

Hey @dorsamehr for the names of the files, use snake_case naming structure. (see here) avoid using spaces in names since can generate problems in the repo


[release-4.11] OCPBUGS-4167: Run azure operations in sequence

This is a clean cherry-pick of https://github.com/openshift/cloud-network-config-controller/pull/52  and a log fix.
/cc @pperiyasamy @andreaskaris

/retest-failed

/lgtm

/hold
Doesn't the log fix first have to merge into 4.12?

/hold Doesn't the log fix first have to merge into 4.12?

Yup: https://github.com/openshift/cloud-network-config-controller/pull/80

/remove-hold

/label backport-risk-assessed

/retest-required

/label cherry-pick-approved