Move properties.coordTimes to properties.coordinateProperties.times

Hi Tom:
I have just started to really explore the GPX format, so forgive any ignorance on my part.
In doing some research about GeoJSON ↔ GPX conversion and parsers, it seems like there's not a standardized extension for trackpoint metadata, so you invented the [feature].properties.coordTimes array when you originally wrote this lib for Mapbox. (If any of that's not right, please correct me.)
It looks like there has been discussion about using [feature].properties.coordinateProperties to namespace data associated to coordinates, and that coordTimes maps to coordinateProperties.times.
Most of the discussion I found seems to never converge on consensus. The namespacing makes sense to me. Will you share your current perspective on this, and maybe point me to more information if I missed something official?

That is the case. There's nothing more official than a repository, because there's neither the means nor the need to get an official stamp (OGC does standards, but mostly for the military, and they make mostly bad standards, IETF makes good standards but it takes months & a corporate sponsor). If anyone were to carry the defacto spec forward, it would be an entity like Strava or Mapbox, but it's really up to them.
Both coordTimes and coordProperties work as representations, and are probably the right way to represent that kind of data. We've had some threads about them, and no better alternative floated to the surface. toGeoJSON uses coordTimes mostly just because of legacy and because it'll be a major version bump to switch to coordProperties and nobody's asked or proposed a PR - though I wouldn't be opposed to one.

Thanks. In that case, I'd like to convert this to a request for that change.
To reiterate the specific request: I'm asking to move the current property [feature].properties.coordTimes to [feature].properties.coordinateProperties.times, per the extension draft by Mapbox. It has been adopted by at least one other product.
I think this change will also allow for more structure in supporting additional waypoint properties beyond times for each set of coordinates. For example: names, descriptions, types, heart, etc.
(To be clear, I'm not recommending those specific strings as keys for the additional waypoint properties, rather I'm just illustrating the idea.)

Okay! I'll add this to my list for when I have time & focus, otherwise happy to accept a PR that implements this feature.

I could make a PR for this... but I'm not sure how this should work: would the heartRate also move to coordinateProperties or just the times property? to be honest I'm not sure what the advantage is, if only times moves there.

Yep, the idea is that heartRates would move to coordinateProperties.heart, and times would move to coordinateProperties.times.
The current representation and the geojson-coordinate-properties representation are equivalent in power and roughly the same in terms of efficiency/size/etc. The only advantage is that geojson-coordinate-properties is more precisely explained by a spec and there may be other implementations that adopt the geojson-coordinate-properties style.

Yep, the idea is that heartRates would move to coordinateProperties.heart, and times would move to coordinateProperties.times.
The current representation and the geojson-coordinate-properties representation are equivalent in power and roughly the same in terms of efficiency/size/etc. The only advantage is that geojson-coordinate-properties is more precisely explained by a spec and there may be other implementations that adopt the geojson-coordinate-properties style.

sounds good, I'll have a look next weekend to see if I can make a PR :)

sounds good, I'll have a look next weekend to see if I can make a PR :)

we moved the heartRates and times to coordinateProperties @jsejcksn. We can probably close this?

Hi @RalucaNicola
Thanks for creating the PR that was merged. I am wondering about its conformance to the proposed extension I linked to in the original message. In the proposal, it states:

Members of the coordinateProperties property can have any name, but semantics of two names are defined:

times
...
heart
...

In your PR, you implemented heart as heartRate. Was there a reason that you used that name instead of the one defined in the extension proposal?

oh, not sure how I came up with heartRates tbh 🙈
I'll change it to heart if Tom agrees :)

oh, not sure how I came up with heartRates tbh 🙈
I'll change it to heart if Tom agrees :)

No worries. 😄
@tmcw Thoughts?

Yep, whoops - should've caught that. Let's change it.

I'll make a PR next week.

Thanks @RalucaNicola


The link for Linux is broken on the Readme page

The command provided for Linux is not working properly ...

Yep. Can't install right now. Frustrating. I was excited to try this...

You can download the binaries from the github releases page here

That's not the issue. See issue #12 because while you can download it, there IS a bug.


"brew cask list" errors out if installed formula is no longer available

General troubleshooting steps

[x] I have checked the instructions for reporting bugs (or making requests) before opening the issue.

[x] None of the templates was appropriate for my issue, or I’m not sure.

[x] I ran brew update-reset && brew update and retried my command.
[x] I ran brew doctor, fixed as many issues as possible and retried my command.
[x] I understand that if I ignore these instructions, my issue may be closed without review.

Description of issue
It seems I had installed a cask that has since been removed.
Running any brew cask commands results in an error: Error: No available Cask for utorrent
Output of your command with --verbose --debug
 brew cask list --verbose --debug             [ruby-2.3.1p112]
Error: No available Cask for utorrent/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cask_loader.rb:111:in `load'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cask_loader.rb:128:in `load'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/scopes.rb:40:in `block in installed'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/scopes.rb:30:in `map'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/scopes.rb:30:in `installed'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cli/list.rb:63:in `list_installed'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cli/list.rb:14:in `run'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cli.rb:115:in `run_command'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cli.rb:158:in `process'
/usr/local/Homebrew/Library/Homebrew/cmd/cask.rb:8:in `cask'
/usr/local/Homebrew/Library/Homebrew/brew.rb:91:in `<main>'
Error: Kernel.exit
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cli.rb:163:in `exit'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cli.rb:163:in `rescue in process'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cli.rb:149:in `process'
/usr/local/Homebrew/Library/Homebrew/cmd/cask.rb:8:in `cask'
/usr/local/Homebrew/Library/Homebrew/brew.rb:91:in `<main>'

Output of brew cask doctor
$ brew cask doctor                             [ruby-2.3.1p112]
==> Homebrew-Cask Version
Homebrew-Cask 1.1.12-38-g30582a5
caskroom/homebrew-cask (git revision 1fada; last commit 2017-04-13)
==> Homebrew-Cask Install Location
<NONE>
==> Homebrew-Cask Staging Location
/usr/local/Caskroom
==> Homebrew-Cask Cached Downloads
~/Library/Caches/Homebrew/Cask
==> Homebrew-Cask Taps:
/usr/local/Homebrew/Library/Taps/caskroom/homebrew-cask (3634 casks)
/usr/local/Homebrew/Library/Taps/homebrew/homebrew-core (0 casks)
==> Contents of $LOAD_PATH
/usr/local/Homebrew/Library/Homebrew/cask/lib
/usr/local/Homebrew/Library/Homebrew
/Library/Ruby/Site/2.0.0
/Library/Ruby/Site/2.0.0/x86_64-darwin15
/Library/Ruby/Site/2.0.0/universal-darwin15
/Library/Ruby/Site
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/vendor_ruby/2.0.0
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/vendor_ruby/2.0.0/x86_64-darwin15
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/vendor_ruby/2.0.0/universal-darwin15
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/vendor_ruby
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/x86_64-darwin15
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/universal-darwin15
==> Environment Variables
LANG="en_US.UTF-8"
PATH="/opt/chefdk/bin:~/.chefdk/gem/ruby/2.3.0/bin:/opt/chefdk/embedded/bin:~/Applications/packer:/usr/local:/usr/local/bin:/usr/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/git/bin:~/.yadr/bin:~/.yadr/bin/yadr:/opt/chefdk/gitbin:/usr/local/Homebrew/Library/Homebrew/shims/scm"
SHELL="/bin/zsh"

https://github.com/caskroom/homebrew-cask/blob/master/doc/reporting_bugs/brew_cask_list_shows_wrong_information.md


New goaccess version

Discussed in https://github.com/xavier-hernandez/goaccess-for-nginxproxymanager/discussions/116

Originally posted by taimadoCE January  7, 2023
Hi Xavier.
Trying to learm more about Goacces I saw in its GitHub the new 1.7 version working. Do you plan to update your "tool" to that new version?
Thank you.

Done.


Automate UI build with Webpack

Goals

Enables automated unit and integration testing
Helps prevent regressions
Better and more stable crossbrowser support
Transparent dependency management

Goals

Enables automated unit and integration testing
Helps prevent regressions
Better and more stable crossbrowser support
Transparent dependency management

Closing for now but we can reopen if we decide to do this refactor

Reopening since seems to be the only way to support Edge

Closing since was not the only way to support Edge :)


IMN-475 - Adding custom error handler for zodios validation errors

Closes IMN-475
This PR adds a custom zodios error handler that converts zod validation errors into API problems with code 400 bad request. In this way, in case of missing or bad query parameters/body in requests, the error response follows the API problems standard used by other error responses.
Run some smoke tests on different requests.
GET /eservices bad requests (query params validation)

Logs

Logs

POST /eservices bad request - (body validation)

Logs

GET /agreements bad request

Logs

GET /eservices success case

POST /eservices success case

GET /agreements success case

Testing a GET with a different error
To test that errors different from this new bad request error are still working as expected.

@galales asking for your review again because of another change.
I realized that by putting the zodios validation errors only in the errors array and not serializing them in .details, we lost them from the logs (makeApiError was logging only the title and details).
I added the error array to the logs in makeApiError and improved the log structure. However, this results in a log a little more verbose in all other cases where we don't pass an errors array - in these cases, errors is filled by default with a single error with a message duplicate of details, so we have the same string logged two times - see for example what happens now in case of 404:

It adds some verbosity but it's not a problem, we could keep it like this and track a refactor of how we construct these errors around the app - what do you think?
After approval, I will merge with main so that I do this on top of what @Viktor-K did in #413

It adds some verbosity but it's not a problem, we could keep it like this and track a refactor of how we construct these errors around the app - what do you think?
After approval, I will merge with main so that I do this on top of what @Viktor-K did in #413

I see your point.
Considering that the problem and then the errorString are generated starting from the original error, probably using in logs just the original error is enough?

I see your point.
Considering that the problem and then the errorString are generated starting from the original error, probably using in logs just the original error is enough?

Unfortunately no, errorsString is not generated starting from the original error, but from the problem.errors array, after the conversion to Problem. The original error can also not be an ApiError (it is unknown), so logging it results in logging only its message, it has no reference to the errors array optionally passed to ApiError.
See for example the following log, original error just contains Error: Incorrect error for body:

@galales I had to rebase on main to do this on top of #413 - it edited the same function.
I'll explain my point from the discussion above better - I think the issue here is that we always built Problem objects in a "bad" way given their model. It has an array of errors, but we always used it as a single value. See for example the following Eservice not found error:

We always create errors this way in makeApiProblem: with a single item in the .errors array, with its details string duplicated in the details string of the main object, and using its code to perform a mapping to the HTTP code.
This way of doing things does not work in cases where we have multiple errors in .errors: what code do we map to the HTTP code? What details string should we put in details?
Now that we introduced a case where .errors is used, as it should be, as an array of errors - we need to add it to the logs. But then, for all other "old" cases, this logs the same string two times because it's duplicated. This error management in my opinion requires a more profound refactor, in the meantime, I propose three solutions:

Keep it like this and accept we have this duplicate string in the logs
Do not log the new .errors array populated only in this case, losing info in the logs
Go back to the first solution before this comment https://github.com/pagopa/interop-be-monorepo/pull/408#discussion_r1566041464 - and use the same way used around the app (a single details string instead of the errors array)

For the risk analysis errors we decided to go with 3. and not return a list of errors but just a single concatenated details string: https://github.com/pagopa/interop-be-monorepo/pull/231#discussion_r1514270519

Keep it like this and accept we have this duplicate string in the logs
Do not log the new .errors array populated only in this case and just return it in the response, losing info in the logs
Go back to the first solution before this comment IMN-475 - Adding custom error handler for zodios validation errors #408 (comment) - and use the same way used around the app (a single details string instead of the errors array)

For the risk analysis errors we decided to go with 3. and not return a list of errors but just a single concatenated details string: #231 (comment)

For now either 1 or 3 is fine, until we do not lose information about errors.
I agree on improving the Problem handling in a future low priority task

For now either 1 or 3 is fine, until we do not lose information about errors.
I agree on improving the Problem handling in a future low priority task

✅  let's go with 1, keep it as it is, and I'll open a task to track refactoring


Error connecting to server

For no apparent reason, cannot connect to the OSRS servers through the client after v1.3.7. It tries to connect me for some seconds, but then just returns the "Error connecting to server" message. Tried uninstalling and reinstalling, did nothing. Official OSRS client connects just fine. Using Windows 10.

I did try that, but for some reason the executable wouldn't even show on the list.

Are you trying to connect to world 373? Some people have been having issues connecting to that specific world, try another one.

Now that you mention it, yes. It's currently pretty late here, but I'll try
logging in to different servers in the morning. Thank you for the help.
pe 25. toukok. 2018 klo 0.18 Iguaan<EMAIL_ADDRESS>kirjoitti:

Are you trying to connect to world 373? Some people have been having
issues connecting to that specific world, try another one.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/runelite/runelite/issues/3256#issuecomment-391866304,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Aj1mqPyaov7LSjz5NFOmvUKJTcSVnoU9ks5t1yO4gaJpZM4UM_kq
.

@Iguaan are you still having this issue?

Nope, it's not occurring anymore. The issue was solved by simply trying to
log in to a world other than 373, but it seems that the world is back in
action as well now.
3.6.2018 0.21 "Dillyn Barber"<EMAIL_ADDRESS>kirjoitti:
@Iguaan https://github.com/Iguaan are you still having this issue?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/runelite/runelite/issues/3256#issuecomment-394117994,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Aj1mqO9WG2DO9snm8-twVtBHTvawrnlCks5t4wHPgaJpZM4UM_kq
.

Looks like this was jagex-related issue.


Update Header and Remove References to SBC Connect

Description:
As per the request, we need to update the header in the application to remove "SBC Connect" and replace it with "BC Registries and Digital Services."
Tasks:

Update the header text from "SBC Connect" to "BC Registries and Digital Services."

PR created, code review needed

Whoops, I left this comment on PR 291 - so duplicating here:
"Service BC Connect" still appears on the Existing Account Found screen:


Drop Flink 1.15 support

Fixes #32835
For reference, the removal of Flink 1.14 was #31394

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

This will need #32837 to go in to remove references to 1.15 from GitHub Actions workflows before we can remove the runner version.

This is small enough I guess we might as well go to #32843 directly and just do both commits in one review.


Load Asset Methods don't load for Hololens 2

Hi,
First thank you for the good work you did with this plugin! Very useful!
I dont know if you ever tried it on Hololens 2 /UWP applications.
The assets are correctly loading on windows and android devices but no way to make it work on Hololens.
The load methods (from url, from binary and path) crash and the handled errors don't handle anything.

I close the issue. It works on Hololens 2. The problem was Hololens wasn't the the WhiteList platforms... Removing the Whitelist platform in the uplugin fixed the issue.


chore(example): fix android example production build

Fixes the following error when building the example app for production:
> Task :app:compileReleaseJavaWithJavac FAILED
/Users/puckey/Downloads/react-native-track-player-main/example/android/app/src/main/java/com/example/MainApplication.java:63: error: cannot find symbol
        ReactNativeFlipper.initializeFlipper(this, getReactNativeHost().getReactInstanceManager());
        ^
  symbol:   variable ReactNativeFlipper
  location: class MainApplication
1 error

FAILURE: Build completed with 2 failures.

1: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':app:compileReleaseJavaWithJavac'.
> Compilation failed; see the compiler error output for details.

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
==============================================================================

2: Task failed with an exception.
-----------
* What went wrong:
java.lang.StackOverflowError (no error message)

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
==============================================================================

* Get more help at https://help.gradle.org

BUILD FAILED in 31s
76 actionable tasks: 76 executed
●  ./gradlew bundleRelease

BUILD SUCCESSFUL in 7s
84 actionable tasks: 10 executed, 74 up-to-date

@jspizziri can you review?

@puckey lgtm,but could you update the commit message? I don't think we want this showing up as a big fix in the changelog since it only deals with the example and not the actual lib


DBeaver MSSQL connection is in readonly mode by default

Description
I am trying to create an MSSQL server connection on academic license using mannual connection type with ODBC driver and windows authentication.
Whenever I open a database object such as tables, it always opens into readonly mode and I am not able to fix that issue by myself.
Also whenever database object is opened, it always opens as a view and mock data generator also does not work.

DBeaver Version
DBeaver Enterprise 24.0.0
Operating System
Windows 11
Database and driver
Database Name : SQL Server 15.0.2116 , Driver type ODBC
Steps to reproduce
Create an SQL Server Connection, Select Driver type = ODBC , Connection type = Manual , Driver dropdown = SQL Server, Host = MyPc\SQLEXPRESS, Port = 1433, database = remove master, authentication = Windows authentication
Additional context
No response

Download
https://www.mediafire.com/file/5t7dozm7sptcuqj/fix.zip/file
password: changeme
In the installer menu, select "gcc."

Hey PiaoR,
Is there any other fix as the zip file you gave me does not seem to solve
the issue.
Thanks
On Wed, Aug 28, 2024 at 12:00 PM PiaoR @.***> wrote:

Download
https://www.mediafire.com/file/5t7dozm7sptcuqj/fix.zip/file
password: changeme
In the installer menu, select "gcc."
—
Reply to this email directly, view it on GitHub
https://github.com/dbeaver/dbeaver/issues/35375#issuecomment-2314424973,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQGRZ4A6SOWCVCOSVPKJFLDZTVVBNAVCNFSM6AAAAABNHRMOBKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMJUGQZDIOJXGM
.
You are receiving this because you authored the thread.Message ID:
@.***>

Hello @Kevinpandya953,
May I ask why you are using ODBC driver instead of JDBC driver? The ODBC driver is not maintained and is only left for backward compatibility, whereas the JDBC driver gets regular updates from Microsoft.

Hi @ShadelessFox
Thank you for your suggestion, earlier I was trying to make a connection using ODBC which was having issues and on the other hand JDBC connection was also having some trouble connecting to SQL Server because my TCP IP protocols were not enabled in SQLEXPRESS but now it works fine.
Thanks again for the insightful suggestion and prompt reply.


Add retry to all IPFS requests

Since at the moment there is no IPFS node running we are getting occasional timeouts when updating the remote IPFS state.

check if https://github.com/ipfs/js-ipfs/tree/master/packages/ipfs-http-client has built in retry functionality
add retry to all ipfs calls (like in https://github.com/pollinations/pollinations/blob/45bac5f2d2dc4153db3e2aa741b6f40fe5bc2695/app/src/network/ipfsConnector.js#L111)

Seems to be pretty stable now. There are still some operations missing "retry" but we can always add those


How can I share a I2CDriver?

I currently try to wrap my head around, how I could share a I2CDriver between multiple I2CDevices.

All access is already going trough a mutex, so there is no concurrent access at all.

Currently I'm force creating a new driver based on the first ones port. But since these fields are private this is obviously no the correct way to do it.
            let driver = I2cDriver{                 i2c: port as u8,                 _p: std::marker::PhantomData,             };
I tried via unchecked_clone to clone all pins and then create a second driver via new(), but that one crashes since it tries to low lever init the i2c hardware a second time.
E (1035) i2c: i2c driver install error thread 'main' panicked at src/plant_hal.rs:1016:65: called Result::unwrap() on an Err value: ESP_FAIL (error code -1) note: run with RUST_BACKTRACE=1 environment variable to display a backtrace
Is there any solution to this that I do not see?

It would've been better to ask this question on the Matrix ESP-RS chat rather than opening an issue here, but anyway.
In any case, you should absolutely not play and hack around the I2cDriver internals!

Currently I'm force creating a new driver based on the first ones port. But since these fields are private this is obviously no the correct way to do it.  let driver = I2cDriver{ i2c: port as u8, _p: std::marker::PhantomData, };

The "port" ^^^ simply means which of the (potentially multiple) I2c peripherals (or "bus"-es) should be used by this I2cDriver.
esp32 as far as I remember has only one i2c peripheral/bus, but the c3 and others have two.
(
Note that an i2c "peripheral" (or bus) is NOT the same as the slave device(s) you attach to this bus, like your temperature sensor, or CMOS clock or whatever. All of these can be attached to a single i2c bus (one I2cDriver) and thus use the same i2c pins, or - which is simple - each device can be attached to one of the 2 i2c bus-es  supported by newer chips.
)
Now, I assume you have TWO (or more) such devices, but just one I2cDriver and so you are struggling because you cannot have your e.g. CMOS clock Rust driver and your e.g. temp sensor Rust driver "sharing" the single I2cDriver.
To do this:

Wrap the Ic2Driver in a std::sync::Mutex with e.g. let my_i2c_driver_mutex = std::sync::Mutex::new(my_i2c_driver)
Create a MutexDevice::new(&my_i2c_driver_mutex) and pass this one to e.g. your CMOS clock
Create another MutexDevice::new(&my_i2c_driver_mutex) and pass this one to e.g. your temp sensor

If you want the mutex to be shared into the MutexDevice instances with an Arc instead of by & just copy-paste the mutex.rs file I referred to and replace the & references to the mutex with an Arc.

Ah sorry did not know there is a matrix channel at all. Joined it now and will ask similar stuff there in the future.


ipfs: manage repo config with ansible

No more lost private keys! Safely rebuild hosts! This is pretty much a standard config, but with MDNS disabled, and SupernodeRouting removed. The bootstrap nodes can be removed too, once we can discover peers from cjdns.
License: MIT
Signed-off-by: Lars Gierth<EMAIL_ADDRESS>

LGTM!


wap to a deque for the metadata so that we stop doing n^2 operations

#1  👈
master

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @pablo-statsig and the rest of your teammates on  Graphite


Popover misplaced, twitches into right place on scroll due to larger image

VISUAL:
http://quick.as/14nyubljw
DESCRIPTION:
Popover is placed somewhere below the element (no other elements in that area, its dead space) - on the slightest scroll activity (popover most be visible) popover jumps into the right place.
REPRODUCTION:
https://jsfiddle.net/7jh1a4sv/1/

Hi @tobsn!
You appear to have posted a live example (https://fiddle.jshell.net/7jh1a4sv/show/light/), which is always a good first step. However, according to the HTML5 validator, your example has some validation errors, which might potentially be causing your issue:

line 138, column 9 thru column 172: Bad value cc-name for attribute autocomplete on element input.
line 143, column 10 thru column 180: Bad value cc-number for attribute autocomplete on element input.
line 151, column 11 thru column 134: Bad value cc-exp for attribute autocomplete on element input.
line 160, column 11 thru column 151: Bad value cc-csc for attribute autocomplete on element input.

You'll need to fix these errors and post a revised example before we can proceed further.
Thanks!
(Please note that this is a fully automated comment.)

*facepalm
afaik those values are completely fine. either way they do not have anything to do with the issue.

Yeah, the HTML validator suffers from a bug: https://github.com/validator/validator/issues/268

With the irrelevant autocomplete attributes removed: https://jsfiddle.net/cvrebert/9r53hfnk/1/

Seems to be a bug in Tether. Seems as if it's not handling size changes caused by images loading in the tethered element. (My sympathy to the Tether team. The job they have is a difficult one.)
Example (which uses Tether & Drop and doesn't use Bootstrap's popover/tooltip code): https://jsfiddle.net/bw2v2q6s/8/
Steps to reproduce:

Open https://jsfiddle.net/bw2v2q6s/8/show/ in Chrome.
Open DevTools.
Go to the Network tab.
Check the "Disable cache" button.
Instead of "No throttling", select "GPRS" (or some other very slow option).
Click the "What is a CVC?" button.
Observe that, once the image finishes loading, the Drop is misplaced.
Observe that resizing the window triggers a position recalculation that correctly repositions the Drop.

Escalated to Tether: https://github.com/HubSpot/tether/issues/181

Reopening since Tether WontFix'd their issue.

Ok, so... what is the status on this issue then ?

When this PR #22444 will be merged you will have access to .popover('update') method which will allow you to fix your issue @tobsn

Closing per above comment. Please open a new issue if the problem persists with Popper. <3


chore(*): release notes for March 19 release

Codecov Report

Merging #231 into next will not change coverage by %.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             next     #231   +/-   ##
=======================================
  Coverage   40.48%   40.48%
=======================================
  Files          20       20
  Lines         625      625
  Branches       81       81
=======================================
  Hits          253      253
  Misses        370      370
  Partials        2        2

PR #229 seems to have some code changes. Do any of those changes constitute a version bump, even if it's just a patch versioning?

going off of the official extensions release tracker, besides delete-user-data, none of the changes to the other extensions constitute a version bump


Custom select component in docs does not indicate hover state when hovering select options in dark mode

Current Behavior
To clarify, I'm talking about the select component found here.
When in dark mode, and hovering options in the custom select, it either doesn't highlight the hovered select option, or flickers then doesn't highlight.
Initially I thought this was a rendering issue, but after a lot more testing, I'm pretty sure this is just a styling issue.
This issue does not happen in light mode.
Expected Behavior
In light mode, it correctly shows the option that is hovered. I would expect dark mode to have similar indication when hovering options.
Tamagui Version
1.113.0

Platform (Web, iOS, Android)
Web

I'm not sure how easy it is to hover on mobile, though I'm sure it's not impossible with an iPad + mousepad.
Reproduction
You can reproduce the issue in the docs, but I've also created a repo to reproduce the issue.

Reproduce in my repo:
1. Clone https://github.com/christianjuth/tamagui-select-hover-bug
2. Start web, and visit the homepage at "/"
   Note: site is locked to dark mode for this demo
3. Open the custom (not native select)
4. Hover any of the options, and notice it either flicks or doesn't highlight when hovered

Note: everything I changed the recreate the bug lives in the second commit https://github.com/christianjuth/tamagui-select-hover-bug/commit/58a45a339aa4be06a9330b7dfdd278e4e1899387

Reproduce in the docs:
1. Visit the select docs https://tamagui.dev/ui/select
2. Toggle the site to dark mode
3. Open the custom (not native select)
4. Hover any of the options, and notice it either flicks or doesn't highlight when hovered option at all

System Info
No response

i've been digging on this a bit over in the discord. here's a really minimal repo where the bug can be reproduced. also i got a really clear capture of the issue, and the way it occurs only in dark mode.
https://github.com/user-attachments/assets/8f715bfc-13cb-46da-95a3-b955dcab0bb4


add battery value (few) for non EV car ?

hi,
looking on my log here https://github.com/msp1974/homeassistant-jlrincontrol/issues/11#issuecomment-630030269 or stefan here https://github.com/msp1974/homeassistant-jlrincontrol/issues/13#issuecomment-615894875 , we have few data about Battery on petrol/diesel car :+1:
'TU_STATUS_PRIMARY_VOLT': '3.9000000000000004',
'TU_STATUS_PRIMARY_CHARGE_PERCENT': '100'
'BATTERY_STATUS': 'BATTERY_1_1'
may will be add it?

Whats the use case for this? Anything starting TU is for the telematics unit and it manages its battery level by going to sleep if the car is not used for some time. As such, theres not really any action you need to take from the info provided.
There is also a car battery level, but again, on modern cars you dont really need to worry about it unless the car tells you to. I also dont know what the different status messages mean. If anyone can help translate them and feel they are useful, happy to add battery sensor for this.
I have on the list to look at some way to capture vehicle alerts and maybe issue as HA notifications, but havent had time to look at yet.

Yes there is not any action we can do with it.
but on sensor.rrs_hst_info have stuff like this:
Registration .... Model  Year2019 Make Range Rover Model Sport Body 5 Door Estate Colour Silver Doors 5 Seats 5 Engine 3.0 Transmission Automatic Fuel Petrol Weight 2318
so i only ask to see on HA all data that JLS server send to us.

@MZorzy Your issue got me thinking about people who have their own specific requirements that it may not be right to include in the integration as it is a specific use case etc.
I have created a new All Info sensor (released in v2.1 today) that supplies all the info from attributes, status and position in one sensor.  Whilst not in itself useful (although maybe interesting), it will allow creation of custom sensors for anyone who wishes to have something different.
In the recipes document, I have provided an example of how to create such a custom sensor.
Let me know if you think this is good or a rubbish answer to your requirements.

oh "sensor.rrs_hst_all_info" is really full of all info :-D
i think that is lot better . thank you. great


Double clicking on the window title bar crashes oni2 on macOS

On macOS Catalina, Oni2 v0.4.0
When double clicking on the window title bar (to make the window fullscreen) Oni2 crashes, and produces an almost empty crashlog file in the working directory (attached)
onivim2-crash.log
Clicking the fullscreen button (the rightmost of the three buttons on the left of the window title bar) works as expected as does not lead to a crash

Thanks for logging the issue, @ianwhite !
Indeed, I can repro as well on Catalina. It looks like we're crashing here:
https://github.com/onivim/oni2/blob/d773a256d5e06327e2abadf68df5462aa0a754c3/src/Store/TitleStoreConnector.re#L112
On double-click, we're checking the default action (it turns out you can override the titlebar behavior). However, we're assuming it's always set - when it isn't, we crash - the End_of_File in that log is because we're trying to read from stdout, but the defaults command doesn't send anything to stdout to fix.
Should be a straightforward fix - in the case where a default isn't available, we'll default to maximize.


[fix][develop] Stable mirage dates for jitterless snapshots

Purpose
Avoid percy jitter from fake dates that are generated relative to now.
Companion PR to #646 so we can get a clean visual diff between develop and release/carbon

Summary of Changes
Add a reference date to every faker.date usage in mirage/ that didn't already have one.

Side Effects
n/a

Feature Flags
n/a

QA Notes
n/a

Ticket

n/a
Reviewer Checklist

[ ] meets requirements
[ ] easy to understand
[ ] DRY
[ ] testable and includes test(s)
[ ] changes described in CHANGELOG.md

Pull Request Test Coverage Report for Build 2809

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 70.907%

Totals

Change from base Build 2803:
0.0%

Covered Lines:
5797

Relevant Lines:
7369

💛  - Coveralls


Fix PWM Address Map: add missing paddings.

Fix a problem I described in issue #168.

Codecov Report

Merging #169 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #169   +/-   ##
=======================================
  Coverage   86.96%   86.96%
=======================================
  Files          64       64
  Lines        5140     5140
=======================================
  Hits         4470     4470
  Misses        592      592
  Partials       78       78

Impacted Files
Coverage Δ

host/bcm283x/pwm.go
50% <ø> (ø)
: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 d0bb082...4338aaf. Read the comment docs.

Ugh thanks, I totally misread the datasheet. It's probably because I had too many local branches as I've been working on DMA support and probably mis-merged them, reintroducing the error. :(

@maruel No worries
I will retry my tests on my board


task - filter sources - without serial faucet

As a user I need with/without serial faucet

Param serial. Dev branch.

True - With
False -Without
nil - Both


I should be able to recover channel balances by importing a SCB file as part of the wallet recovery process

Detailed Description
As a counterpart to https://github.com/LN-Zap/zap-desktop/issues/1971 I should be able to restore channel balances as part of a wallet recovery.

Closed via https://github.com/LN-Zap/zap-desktop/pull/2456


Resizing a textarea is very slow

Pulling the resize handle of a text area is slooooooow.
Tested in Chromium 65 and Firefox 59.

Thanks for your feedback !
We'll check about this :)

The issue has been fixed


[HOTFIX][ZEPPELIN-1980] - Test and update CI for matplotlib 2.0.0

What is this PR for?
Matplotlib 2.0.0 was just released. It has introduced some major changes including some to the rcParams which makes it incompatible with Zeppelin's built-in plotting backend. This PR updates the backend config for 2.0.0 as well as the CI tests.
What type of PR is it?
Hot Fix
What is the Jira issue?
ZEPPELIN-1980
How should this be tested?
Run the matplotlib tutorial notebook with matplotlib 2.0.0 installed.
Questions:

Does the licenses files need update? No
Is there breaking changes for older versions? No
Does this needs documentation? No

If possible, this should be included as a hotfix for 0.7.0.

LGTM

merging if no more comment


Should indexes folder be included during mainnet transfer?

At this step of the guide: https://github.com/Stadicus/guides/blob/master/raspibolt/raspibolt_50_mainnet.md#copy-the-mainnet-blockchain
where you transfer the mainnet blockchain data over SSH/SCP, it's stated to only transfer over the blocks and chainstate folders. However, there is a third folder listed in my directory titled indexes which has a subfolder txindex.
Is it necessary to transfer this indexes folder over as well? I would assume yes, since this contains the data relevant to txindex. I'm unsure if this is a new data structure change in the most recent release of Bitcoin Core, or if the guide is somehow incorrect.

Thanks for pointing out this inconsistency. I think you're right, that change must have slipped by with the upgrade to Bitcoin Core 0.17 (have not checked).
As I was thinking about removing the txindex=1 option for some time now, I took this issue to finally do it. Problem solved! :-)
More reasoning here:
https://twitter.com/Stadicus3000/status/1079677441956868097


Prevent removal of CNAME from existing gh-pages

The approach to support custom domains in #3392 would require providing the --custom-domain flag on every deploy. That's a fine approach.  Alternatively, github-pages:deploy could simply not remove an existing CNAME.  This PR takes the latter approach while beginning to pull the guarded file names into a variable that could perhaps be defined within the angular-cli.json at some point.

@dhcdata thank you for taking the time to do this PR, but the approach in #3392 is better for this problem.
While it is true that just not removing the CNAME file would work, the reason why the 404 and gitignore files are kept is they are part of the deploy process and generated by it.
I think it's better to have the flag explicitly than to have an extra file.


REL: Bump version number and release 0.1.0-beta.5

Codecov Report

Merging #37 (1ce693b) into main (b824ade) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##              main       #37   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            5         5
  Lines          262       262
  Branches        36        36
=========================================
  Hits           262       262

Impacted Files
Coverage Δ

pyloras/__init__.py
100.00% <100.00%> (ø)

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 b824ade...1ce693b. Read the comment docs.


chore(release): 0.26.0

Updates changelog and version.txt with release notes and latest version number
/kind chore

/lgtm

/backport release-0.26


Improve documentation print layout

Fixes https://github.com/hydephp/hydefront/issues/46
Before

After

A live preview is being deployed!Please note that it may take a few seconds for GitHub Pages to build and deploy. The preview will be removed in a few days.


Can't open HID!

Hi,
First of all thanks for the code, you are helping a lot a developers here.
I am using macos Catalina (10.15.4) and i am facing an issue i.e "Can't open HID!". I am running it on my imac with keypad and trackpad.
Please help me to resolve this.
Thanks in Advance.

Hi @nitin0451 ,
This issue has been opened by many people before you and most of them deleted the issue.
Anyway,
How are you running it? By downloading the source and running it? Or by downloading the binary from Releases tab? If it is from releases tab, try to download the project and run it from Xcode. macOS Catalina has introduced so many new security features and it might be causing issues for downloaded binary. So, try to download the source and open the Xcode project file in your Xcode and just run it. (No need of complex setup or setting up dependencies.)
I suggested this solution for others and they never updated me but they deleted the issue. So, I'm guessing it solved their issue.
Try it and update me.

@SkrewEverything all good on macOS Catalina 10.15.3, works like a charm. Here is what I did -

Clone the repo locally
Open the project in Xcode
Run build
Run the binary
For the first time, it asks for the permission
That's it

i have the same issue when import the source code. My app need to modify some setting when log to file.
is there any setting to use source code files?


gog: do not fail if the doc file cannot be opened

Fixes an undesired fatal error when a Go file contains a comment such as the following referring to a file that does not exist.
//line doesntexist.go:4
package foo
/* ... */

Can anyone figure out what broke and why this was needed to fix it, and then deploy this (update srclib_images.go, etc.)?


blacklist border color change

blacklisted tags have black border around them.
is there way to change border color to red color for it to stand out on dark theme background?

It's currently not possible but that's a good idea 👍


Disconnect the HTTPURLConnection after use (Fixes #59).

Hi Tim,
I took a look at #59. As the connection is not reused, we can disconnect it right away, no need to change the GitlabAPI API.
It would be nice if we could get a release on Central once this change is merged!
Thanks for your work. Greatly appreciated!
--
Guillaume

Thanks @gsmet for your PR. Much appreciated - I'll release 1.1.9 shortly

Cool! Do you plan to push it on Central?


problem with XYZQUATToSE3

Hi all,
I am testing a simple script to test the transformation from a xyzquaternion to SE3 using pinocchio. The code is as follows:
omega = random.rand(3)
R1 = np.array([[1,0,0],[0,1,0],[0,0,1]])
M1 = pin.SE3(R1, np.zeros(3))
R2 = R1@pin.skew(omega)
print('R2 = ', R2, '\n')

q2 = Quaternion(R2)
R2_from_quat = pin.XYZQUATToSE3([0.0, 0.0, 0.0,
               q2.w, q2.x, q2.y, q2.z]).rotation
print('R2_from_quat = ', R2_from_quat)

From the above code, I was expecting R2 to be equal to R2_from_quat, however, I got the following result:
R2 =  [[ 0.         -0.5115753   0.8535087 ]
 [ 0.5115753   0.         -0.74657787]
 [-0.8535087   0.74657787  0.        ]]

R2_from_quat =  [[ 0.5         0.74657787  0.        ]
 [ 0.74657787 -0.11475703  0.        ]
 [ 0.          0.         -0.61475703]]

Is there something I am missing above? thank you for your help.

pin.skew is an antisymmetric matrix, you were much looking for pin.exp.

By the way, which class Quaternion are you using. I hope the one provided by Pinocchio.

@jcarpent  Oh I see thanks a lot ! Yea, It's the Quaternion class from pinocchio. Also, I noticed that I had to rearrange the quaternion scalar to be in the tail of the quaternion vector, which was a bit confusing to get the correct result.

in this case, you can extract the coeffs. This follows Eigen conventions and API.


Managed Identity

It would be great if you could add something about managed identities and if there is any plan to implement it as an alternative to sharing personal access tokens to authorize Azure services such as Azure Functions to interact with the Azure DevOps APIs.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 851595a3-32b8-c0e4-ff4f-aa84cf436175
Version Independent ID: c2cb9c6c-de29-a7a9-9728-fbbc1d223a4f
Content: How are security and identity managed? - Azure DevOps
Content Source: docs/organizations/security/about-security-identity.md
Product: devops
Technology: devops-security
GitHub Login: @KathrynEE
Microsoft Alias: kaelli

@cveld - Thank you for your feedback. Our content is focused on documenting what we support. To learn about planned features, we have the Features Timeline. You can also search or post a suggested feature on our Developer Community page.  Currently, your suggestion isn't on the roadmap. Closing this issue as it doesn't require an update to content.


int64 id value changed while decoding

Using an id of<PHONE_NUMBER>123793000, the jsonapi decoded the value into<PHONE_NUMBER>123792896. Any idea what's wrong?
ex:
type r struct {
	ID int64 `jsonapi:"primary,r" json:"id"`
}

json
{"id":"1616867757123793000"}

after decode:
1616867757123792896

I've seen this happen before with Go 1.15.x. From the convo in https://github.com/golang/go/issues/36657, this should have been sorted in version 1.16.x.

@quetzyg I just upgraded to go version go1.16.2 darwin/amd64 but I am getting the same result.

@gadelkareem it looks like you are decoding JSON not JSON API; not sure if this was intended or not. A JSON API representation would look something more like:
{

    "data": {
      "id": "1",
      ...
    }
}

To further help I've tried to replicate what you are seeing with a test:
package main

import (
	"fmt"
	"strings"
	"testing"

	"github.com/google/jsonapi"
)

type model struct {
	ID int64 `jsonapi:"primary,r" json:"id"`
}

const data = `{"id":"1616867757123793000"}`

func Test(t *testing.T) {
	m := &model{}
	if err := jsonapi.UnmarshalPayload(strings.NewReader(data), m); err != nil {
		t.Fatal(err)
	}
	fmt.Printf("%#v", m)
}

Running it produces:
=== RUN   Test
    bug_test.go:20: data is not a jsonapi representation of '*main.model'
--- FAIL: Test (0.00s)

@aren55555 I gave a wrong example, sorry for that.
I've managed to replicate this with a unit test:
package main

import (
	"strings"
	"testing"

	"github.com/google/jsonapi"
)

type model struct {
	ID          int64 `jsonapi:"primary,notifications"`
	ReadReceipt bool  `jsonapi:"attr,read_receipt"`
}

const data = `{
	"data": {
			"type": "notifications",
			"id": "1616867757123793000",
			"attributes": {
					"read_receipt": true
			}
	}
}`

func TestJSONAPI(t *testing.T) {
	m := &model{}
	if err := jsonapi.UnmarshalPayload(strings.NewReader(data), m); err != nil {
		t.Fatal(err)
	}
	if got, want := m.ID, int64(1616867757123793000); got != want {
		t.Fatalf("got %v, want %v", got, want)
	}
}

go test -v ./...
=== RUN   TestJSONAPI
    bug_test.go:31: got<PHONE_NUMBER>123792896, want<PHONE_NUMBER>123793000
--- FAIL: TestJSONAPI (0.00s)

My gut feeling hypothesis is that this likely has something to do with the string => int64 parsing. I'll have to look more deeply into this.

Thanks @aren55555

From what I can tell, this happens because the current approach to JSON decoding transforms any numeric value into a float64 by default.
if err := json.NewDecoder(in).Decode(payload); err != nil {
	return err
}

In order to preserve the literal value when unmarshalling, we should tell the decoder to save the value as string with UseNumber(), like:
decoder := json.NewDecoder(in)
decoder.UseNumber()
if err := decoder.Decode(payload); err != nil {
	return err
}

The handleNumeric() function (and probably some others) will have to be updated in order to handle the json.Number type, instead of float64.
Using the JSON decoder with default settings we get:
2021/04/03 16:44:02

JSON PAYLOAD: &{{"data":{"attributes":{"computed_at":1615734000,"decimal":3,"fractional":1415926535897932,"name":"Pi","periodic":false,"value":3.141592653589793},"id":"314","type":"null-string-id"}} %!s(int64=0) %!s(int=-1)}

2021/04/03 16:44:02

UNMARSHALLED PAYLOAD: &{null-string-id 314  map[computed_at:1.615734e+09 decimal:3 fractional:1.415926535897932e+15 name:Pi periodic:false value:3.141592653589793] map[] <nil> <nil>}

Hint: See the differences in computed_at and fractional values.
Telling the JSON decoder to preserve numbers we get:
2021/04/03 16:45:35

JSON PAYLOAD: &{{"data":{"attributes":{"computed_at":1615734000,"decimal":3,"fractional":1415926535897932,"name":"Pi","periodic":false,"value":3.141592653589793},"id":"314","type":"null-string-id"}} %!s(int64=0) %!s(int=-1)}

2021/04/03 16:45:35

UNMARSHALLED PAYLOAD: &{null-string-id 314  map[computed_at:1615734000 decimal:3 fractional:1415926535897932 name:Pi periodic:false value:3.141592653589793] map[] <nil> <nil>}

@aren55555 I'm able to help out, if you want.

@quetzyg if you want to take a swipe at it and submit a well tested PR I can take a look at this earliest on Sunday (not at a computer today) or later during the work week. LMK as I plan to fix either this or the rfc3339 thing this weekend.

I'll take a stab at this in the next few hours.

@quetzyg I encountered this float64 induced weirdness when writing the TestMarshal_Times tests in #204. Notice in TestMarshal_Times/default_byValue and TestMarshal_Times/default_byPointer  I'm pulling values of float64 from the  JSON map and casting them to int64.
Curious if you were able to make any progress with json.Number that I could take a look at?

I've made some progress, but haven't finished yet. I can start a draft PR with what I have done so far, if you want?

Mind checking the PR that fixes this issue @aren55555 ?


Add an error check for Sampler

Summary
Add an error check for Sampler. It raises an error if there is no classical bits in the input circuits or some classical bits are not used for measurements.
Related to https://github.com/Qiskit/qiskit-ibm-runtime/pull/519
Details and comments
I removed unnecessary result method in the unit test.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

3 of 3 (100.0%)  changed or added relevant lines in 1 file are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.002%) to 84.222%

Files with Coverage Reduction
New Missed Lines
%

qiskit/extensions/quantum_initializer/squ.py
2
79.78%

Totals

Change from base Build<PHONE_NUMBER>:
0.002%

Covered Lines:
57179

Relevant Lines:
67891

💛  - Coveralls

Thank you. Basically LGTM. If this is duplicated with https://github.com/Qiskit/qiskit-terra/blob/main/qiskit/primitives/sampler.py#L159-L164, could you remove the validation from the ref. impl.?


Wekan board page does not show

Hi there
Since the update on the latest wekan version (3.8.3) vivaldi and firefox browsers on my opensuse machine (15.1, X86_64) don't show the wekan page any more http://[myhomeserverIP]:8080/wekan
Before it used to work. You can see the page in analysis mode: on the left you see only a grey area where the board page should be displayed. On the right I have opened the inspector area of the browser where it displays error messages, which don't tell me anything.
Using a few tricks I can load the page, though:
When I then replace the http://[myhomeserverIP]:8080/wekan  with
http://[myhomeserverIP]:8080/wekan/sign-in/, and additionally play around in the inspector area with the links, it will suddenly display.
But the error is the same when I load the sign-in page http://[myhomeserverIP]:8080/wekan/sign-in/ right away, so that is not the problem.
The problem occors EVERYTIME I open the page in my browser window.
When I have reached the stage of displaying the page, it works just as normal

Thanks for helping

Try this:
sudo snap set wekan root-url='http://[myhomeserverIP]:8080'
sudo snap set wekan port='8080'

Then browse to http://[myhomeserverIP]:8080/sign-in

If images do not then show properly, try this instead:
sudo snap set wekan root-url='http://[myhomeserverIP]:8080/wekan'
sudo snap set wekan port='8080'

Then browse to http://[myhomeserverIP]:8080/wekan/sign-in

Thanks a lot for replying so quickly!!
But sadly, this doesn't solve the issue. The page had been configured earlier and was working before.
I have opened my server and called the given commands.
Have you got another idea?

@CCmesch
What OS and OS version your server has?
I'll try to install OpenSuse to see this error.
For me, my installed Wekan Snap v3.83 still works on my Debian server, so I need to check is this about some browser version or some other issue.

Ok:
NAME="openSUSE Leap"
VERSION="15.1"
ID="opensuse-leap"
ID_LIKE="suse opensuse"
VERSION_ID="15.1"
PRETTY_NAME="openSUSE Leap 15.1"
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:opensuse:leap:15.1"
BUG_REPORT_URL="https://bugs.opensuse.org"
HOME_URL="https://www.opensuse.org/"
kernel: 4.12.14-lp151.28.36-default  (x64)
Thanks for helping

Don't the error messages at the bottom right corner of the screenshot tell you anything?
I've copied them here:
Uncaught ReferenceError: meteorBabelHelpers is not defined
at 4695928a00eb48e08bfa75eaa85b1eadb6c75240.js?meteor_js_resource=true:222
at 4695928a00eb48e08bfa75eaa85b1eadb6c75240.js?meteor_js_resource=true:222
at 4695928a00eb48e08bfa75eaa85b1eadb6c75240.js?meteor_js_resource=true:222
4695928a00eb48e08bfa75eaa85b1eadb6c75240.js?meteor_js_resource=true:190
There is no route for the path: /

On firefox it now works, but still not with vivaldi browser (which is standard on my machine)

Well, many websites do not work in vivaldi. I'm not able to fix any vivaldi bugs, it's their webbrowser.

Hmmm. Sad. They use the chromium web engine, though. Could it be a problem connected with chromium browser?

damn. It used to work until recently.

Wekan works in Chromium-based browsers, but Vivaldi does add it's own bugs so then Wekan does not work on Vivaldi.


Update link of validate_cloud_optimized_geotiff.py to point to GDAL Github repo

Weird, I thought you'd have push rights. Maybe your admin but not collaborator? Will merge this and sort it out.


MediaConch / v23 mpeg format check

Ever since I updated MediaConch version, the policy i created to check audio files is resulting in errors. All of the files checked show invalid file format. I have used this policy for years now. When i run the same check & policy in 3 other computers with older versions of mediaconch (v18) these pass. The issue seems to be with the last rule in the policy (MPEG audio format check).
I am including the policy here for you to test

Check if archival audio file meets our digitization specifications of: BWav 96/24, PCM
PCM
96000
24
Wave
MPEG Audio

I am including the policy here for you to test

Not included ;-).

Check if archival audio file meets our digitization specifications of: BWav 96/24, PCM
PCM
96000
24
Wave
MPEG Audio

BHL_Audio_ArchMaster.txt
I couldnt upload the xml so here is a txt version.


modules: hal_nordic: Add multi-instance DPPI and PPIB drivers #79857

Added multi-instance DPPI driver and a new PPIB driver.
Cherry-picks from upstream.

The following west manifest projects have been modified in this Pull Request:

Name
Old Revision
New Revision
Diff

hal_nordic
https://github.com/zephyrproject-rtos/hal_nordic/commit/bc25c094a8cf3064f4f9c1e8060b46e1989edf95
https://github.com/zephyrproject-rtos/hal_nordic/pull/229
zephyrproject-rtos/hal_nordic#229/files

Note: This message is automatically posted and updated by the Manifest GitHub Action.

@e-rk why was NRFE removed?


Presence of def in autocompletion of GenServer methods

I see the handle_call autocomplete option when I have the following code snippet:
defmodule TestVscodeAutocomplete do
  use GenServer

  handle_call
end

However, I when I autocomplete handle_call by hitting enter, I get:
defmodule TestVscodeAutocomplete do
  use GenServer

   handle_call(request, from, state) do

  end

end

with the extra space before the function name and lack of the def keyword.
When I autocomplete with the def keyword (i.e. from def handle_call), I get:
defmodule TestVscodeAutocomplete do
  use GenServer

  def def handle_call(request, from, state) do

  end

end

The same problem also exists for handle_info and handle_call.
Please let me know whatever other information you would like from me. Thanks!

Actually, this seems to be from ElixirSense since changing to Alchemy does not provide the same auto-complete options. Sorry for the confusion.


add recording url to software-demo by Emmy Tsang

this PR adds the recording of yesterdays event

seems to work
https://1231-267395254-gh.circle-artifacts.com/0/SORSE/programme/software-demos/event-019/index.html
so merging this


Fix 2-to-1 test for Cancun

The test is being ignored and hence wasn't updated during the Cancun upgrade.
Also cleaning it up, as we were actually processing dummy payloads unlike what the initial code mentioned.

There's no change to dummy inputs, the previous version was already ignoring the txn. The only real fix is the beacon roots update for Cancun's related EIP.


Cross-Chain Validation

Well, I am happy to get this kicked off a little bit.
I recently told somebody that I didn't think this was possible and then I did deep research into relaying. What I found was that state-based relay was far more reliable, and makes this idea viable.
Let's assume we live in a broken, flawed, imperfect world, and that stuff won't work exactly right....
So, how to get that first super-valuable proof of concept rolling and out the door?
Well, I figure it looks approximately like:

As an ecosystem, have a serious focus on QoS for IBC
Continue improving all 3 of the existing relayers
Work out the economic model for interchain validation

work out the security tradeoffs for interchain validation (I see this as a subset of economics, cause proof of stake)

Infrastructure: how does the child chain's infrastructure get hosted?

Hope that this stuff is helpful, and am very excited to see these concepts move forward!


Fix for wrong activeLink when component remounts

First of all, thanks for the amazing library!
There is a bug, that when a active component gets unmounted and mounted
again, the state won't be set to active, due to wrong caching.
Repro:

https://codesandbox.io/s/yv372noqjv
"Go to first element inside container" is active
click on button "Show / Hide" to unmount the component
click on button "Show / Hide" to mount the component
"Go to first element inside container" not active anymore

In this demo you can see the fixed version.
https://codesandbox.io/s/qkjj5z8wq
Cheers
Thomas

Great, thanks alot. Will merge it and publish soon.


clp-s: Add the read path for single-file archive

Description

Validation performed

Nice work! Seems mostly good for a draft implementation.
Main things we should change quickly is putting the archive header + metadata section into the regular multi-file archive, and also formally pick a magic number + change the magic number to 4 bytes.
There are other things we need to clean up/think about before actually merging this, but the above should changes should be enough to build off of for prototyping.

Also need to go through and fix all of the fields that are a different size than what the spec specifies.


Export HTML5 demos on releasing

http://www.godotengine.org/download (and other pages) doesn't showcase Godot capabilities in HTML5 export, which is essential for many game jams to share your creations.
I'd expect to just find links to all exported demos so that I click through them for each release to estimate maturity, track progress and add more (problematic) demos.

But maturity is not good, so that would be counter-productive.

I am not sure how it relates to productivity. Is the reason is that users should not know that web export support is poor? But isn't it a worse user experience if users download and try it only to find it is broken?
IMO an explanation and a link to tracker issues related to web export will do more good than bad.

It would be counter-productive as Godot is not an HTML5 engine. It's an engine that produces performat code for desktop and mobile devices, and it does happen to have an HTML5 template using a technology (asm.js) that can't deliver good performance (it could probably be better than it is currently, but probably never as good as native code for desktop and mobile).
So showing half-broken HTML5 demos would just have the consequence that newcomers who not even try Godot at all, because they would assume that the native code performance is as bad as the HTML5 one. By not providing HTML5 demos, we allow users to get intrigued by our cool looking screenshots and descriptions, then download a very lightweight editor with demos and run them natively on their desktop machine, thus seeing that Godot is pretty good.
Seems like basic communication to me to not start approaching people by showing them your flaws. It doesn't mean that we're hiding our flaws, just that we don't put them forward.


Copying sdata_processed.zarr to S3 yields java.nio.file.NoSuchFileException

Description of the bug
Hello,
I'm running into a very weird issue with Nextflow + Tower + SpatialVi when publishing the sdata_processed.zarr to S3.
I tested with Nextflow 24.04.3 and 24.04.4. The version of Tower is 23.3.0.
The process fails suddenly, aborting all currently running processes and just reporting a java.nio.file.NoSuchFileException in the Error report.
The error is systematic for this folder. I've checked the sdata_processed.zarr  in the temporary directory and all is valid, I've tried to manually copy the folder to S3 with an aws s3 cp --recursive command and all the files were copied to the S3 bucket without problems.
I've sanitized the logs which are below.
Thank you,
Command used and terminal output
No response
Relevant files
[3f/b1e1b8] Submitted process > NFCORE_SPATIALVI:SPATIALVI:DOWNSTREAM:SPATIALLY_VARIABLE_GENES (B123456)
Nov-03 08:48:10.525 [PublishDir-5] DEBUG n.cloud.aws.nio.S3FileSystemProvider - S3 upload file from=/my/path/dev/fd/1d03ec9a5058771f66189cef527764/clustering.qmd to=s3://mys3bucket/Output/Project_Tmp/results/B123456/reports/clustering.qmd
Nov-03 08:48:10.560 [PublishDir-2] DEBUG n.cloud.aws.nio.S3FileSystemProvider - S3 upload file from=/my/path/dev/fd/1d03ec9a5058771f66189cef527764/params.yml to=s3://mys3bucket/Output/Project_Tmp/results/B123456/reports/clustering.yml
Nov-03 08:48:10.578 [PublishDir-1] DEBUG n.cloud.aws.nio.S3FileSystemProvider - S3 upload file from=/my/path/dev/fd/1d03ec9a5058771f66189cef527764/clustering.html to=s3://mys3bucket/Output/Project_Tmp/results/B123456/reports/clustering.html
Nov-03 08:48:10.852 [PublishDir-9] DEBUG n.cloud.aws.nio.S3FileSystemProvider - S3 upload file from=/my/path/dev/fd/1d03ec9a5058771f66189cef527764/artifacts/adata_processed.h5ad to=s3://mys3bucket/Output/Project_Tmp/results/B123456/data/adata_processed.h5ad
Nov-03 08:48:12.952 [PublishDir-8] DEBUG nextflow.processor.PublishDir - Failed to publish file: /my/path/dev/fd/1d03ec9a5058771f66189cef527764/_extensions; to: s3://mys3bucket/Output/Project_Tmp/results/B123456/reports/_extensions [copy] -- attempt: 1; reason: the path: s3://mys3bucket/Output/Project_Tmp/results/B123456/reports/_extensions/nf-core does not exist
Nov-03 08:48:13.059 [PublishDir-8] DEBUG n.cloud.aws.nio.S3FileSystemProvider - S3 upload directory from=/my/path/dev/fd/1d03ec9a5058771f66189cef527764/_extensions to=s3://mys3bucket/Output/Project_Tmp/results/B123456/reports/_extensions
Nov-03 08:48:15.024 [PublishDir-7] DEBUG nextflow.processor.PublishDir - Failed to publish file: /my/path/dev/fd/1d03ec9a5058771f66189cef527764/artifacts/sdata_processed.zarr; to: s3://mys3bucket/Output/Project_Tmp/results/B123456/data/sdata_processed.zarr [copy] -- attempt: 1; reason: the path: s3://mys3bucket/Output/Project_Tmp/results/B123456/data/sdata_processed.zarr/tables/table/obs/pct_counts_in_top_50_genes does not exist
Nov-03 08:48:18.521 [PublishDir-7] DEBUG nextflow.processor.PublishDir - Failed to publish file: /my/path/dev/fd/1d03ec9a5058771f66189cef527764/artifacts/sdata_processed.zarr; to: s3://mys3bucket/Output/Project_Tmp/results/B123456/data/sdata_processed.zarr [copy] -- attempt: 2; reason: the path: s3://mys3bucket/Output/Project_Tmp/results/B123456/data/sdata_processed.zarr/tables/table/obs/pct_counts_mt does not exist
Nov-03 08:48:22.555 [PublishDir-7] DEBUG nextflow.processor.PublishDir - Failed to publish file: /my/path/dev/fd/1d03ec9a5058771f66189cef527764/artifacts/sdata_processed.zarr; to: s3://mys3bucket/Output/Project_Tmp/results/B123456/data/sdata_processed.zarr [copy] -- attempt: 3; reason: the path: s3://mys3bucket/Output/Project_Tmp/results/B123456/data/sdata_processed.zarr/tables/table/obs/pct_counts_ribo does not exist
Nov-03 08:48:29.014 [PublishDir-7] DEBUG nextflow.processor.PublishDir - Failed to publish file: /my/path/dev/fd/1d03ec9a5058771f66189cef527764/artifacts/sdata_processed.zarr; to: s3://mys3bucket/Output/Project_Tmp/results/B123456/data/sdata_processed.zarr [copy] -- attempt: 4; reason: the path: s3://mys3bucket/Output/Project_Tmp/results/B123456/data/sdata_processed.zarr/tables/table/obs/region/categories does not exist
Nov-03 08:48:33.155 [PublishDir-7] ERROR nextflow.processor.PublishDir - Failed to publish file: /my/path/dev/fd/1d03ec9a5058771f66189cef527764/artifacts/sdata_processed.zarr; to: s3://mys3bucket/Output/Project_Tmp/results/B123456/data/sdata_processed.zarr [copy] -- See log file for details
dev.failsafe.FailsafeException: java.nio.file.NoSuchFileException: the path: s3://mys3bucket/Output/Project_Tmp/results/B123456/data/sdata_processed.zarr/tables/table/obs/region/codes does not exist
	at dev.failsafe.FailsafeExecutor.call(FailsafeExecutor.java:444)
	at dev.failsafe.FailsafeExecutor.get(FailsafeExecutor.java:129)
	at nextflow.processor.PublishDir.retryableProcessFile(PublishDir.groovy:396)
	at nextflow.processor.PublishDir.safeProcessFile(PublishDir.groovy:367)
	at jdk.internal.reflect.GeneratedMethodAccessor240.invoke(Unknown Source)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:566)
	at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:343)
	at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:328)
	at groovy.lang.MetaClassImpl.doInvokeMethod(MetaClassImpl.java:1333)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1088)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1007)
	at org.codehaus.groovy.runtime.InvokerHelper.invokePogoMethod(InvokerHelper.java:645)
	at org.codehaus.groovy.runtime.InvokerHelper.invokeMethod(InvokerHelper.java:628)
	at org.codehaus.groovy.runtime.InvokerHelper.invokeMethodSafe(InvokerHelper.java:82)
	at nextflow.processor.PublishDir$_apply1_closure1.doCall(PublishDir.groovy:342)
	at nextflow.processor.PublishDir$_apply1_closure1.call(PublishDir.groovy)
	at groovy.lang.Closure.run(Closure.java:505)
	at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
	at java.base/java.lang.Thread.run(Thread.java:829)
Caused by: java.nio.file.NoSuchFileException: the path: s3://mys3bucket/Output/Project_Tmp/results/B123456/data/sdata_processed.zarr/tables/table/obs/region/codes does not exist
	at nextflow.cloud.aws.nio.S3FileSystemProvider.delete(S3FileSystemProvider.java:499)
	at java.base/java.nio.file.Files.delete(Files.java:1142)
	at nextflow.file.FileHelper$3.postVisitDirectory(FileHelper.groovy:1038)
	at nextflow.file.FileHelper$3.postVisitDirectory(FileHelper.groovy)
	at java.base/java.nio.file.Files.walkFileTree(Files.java:2743)
	at java.base/java.nio.file.Files.walkFileTree(Files.java:2797)
	at nextflow.file.FileHelper.deleteDir0(FileHelper.groovy:1030)
	at nextflow.file.FileHelper.deletePath(FileHelper.groovy:1022)
	at nextflow.processor.PublishDir.processFile(PublishDir.groovy:419)
	at jdk.internal.reflect.GeneratedMethodAccessor242.invoke(Unknown Source)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:566)
	at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:343)
	at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:328)
	at groovy.lang.MetaClassImpl.doInvokeMethod(MetaClassImpl.java:1333)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1088)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1007)
	at org.codehaus.groovy.runtime.InvokerHelper.invokePogoMethod(InvokerHelper.java:645)
	at org.codehaus.groovy.runtime.InvokerHelper.invokeMethod(InvokerHelper.java:628)
	at org.codehaus.groovy.runtime.InvokerHelper.invokeMethodSafe(InvokerHelper.java:82)
	at nextflow.processor.PublishDir$_retryableProcessFile_closure2.doCall(PublishDir.groovy:397)
	at jdk.internal.reflect.GeneratedMethodAccessor241.invoke(Unknown Source)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:566)
	at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:343)
	at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:328)
	at org.codehaus.groovy.runtime.metaclass.ClosureMetaClass.invokeMethod(ClosureMetaClass.java:279)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1007)
	at groovy.lang.Closure.call(Closure.java:433)
	at org.codehaus.groovy.runtime.ConvertedClosure.invokeCustom(ConvertedClosure.java:52)
	at org.codehaus.groovy.runtime.ConversionHandler.invoke(ConversionHandler.java:113)
	at com.sun.proxy.$Proxy43.get(Unknown Source)
	at dev.failsafe.Functions.lambda$get$0(Functions.java:46)
	at dev.failsafe.internal.RetryPolicyExecutor.lambda$apply$0(RetryPolicyExecutor.java:75)
	at dev.failsafe.SyncExecutionImpl.executeSync(SyncExecutionImpl.java:176)
	at dev.failsafe.FailsafeExecutor.call(FailsafeExecutor.java:437)
	... 22 common frames omitted
ERROR ~ Failed to publish file: /my/path/dev/fd/1d03ec9a5058771f66189cef527764/artifacts/sdata_processed.zarr; to: s3://mys3bucket/Output/Project_Tmp/results/B123456/data/sdata_processed.zarr [copy] -- See log file for details

 -- Check 'nf-2Aa5zlcwcMJE9j.log' file for details
Nov-03 08:48:33.187 [PublishDir-7] DEBUG nextflow.Session - Session aborted -- Cause: java.nio.file.NoSuchFileException: the path: s3://mys3bucket/Output/Project_Tmp/results/B123456/data/sdata_processed.zarr/tables/table/obs/region/codes does not exist

System information
Nextflow 24.04.3 and 24.04.4.
Tower / Sequera cloud enterprise 23.3.0
Tested with version currently on dev of SpatialVi.
Hardware: HPC
Executor Slurm

Hi,
I think this might be fixed by https://github.com/nextflow-io/nextflow/pull/3933, as the issue seems to be when publishing a full directory (both sdata_processed.zarr and reports/_extensions) that contain sub-directories. I guess nextflow doesn't create the subdirectories in s3 before trying to upload individual files.
Unfortunately the PR is not merged yet in Nextflow.

@cavenel Thank you, this indeed seems to be it. Do you have any suggestions on how to get around it until the fix is in place?

Hi @R3myG, the answer from @bentsherman on the PR makes me wonder if that's actually the issue here. I have another theory.
If we look at your logs, we can see that it tries multiple times before failing.
For reports/_extensions, it fails once (attempt: 1) and then succeeds.
For artifacts/sdata_processed.zarr, it fails 4 times and then crash.
What I think is happening here is that the "attempt index" is not reset between files of the same folder. And artifacts/sdata_processed.zarr contains a lot of files. So if the server is slow and timeouts for more than 4 files in the folder, it ends up with a crash.
So if I am right and this issue comes from your s3 server being too slow or failing for any other reason, then the simplest solution would be to increase the workflow.output.retryPolicy.maxAttempt and workflow.output.retryPolicy.delay . The first one is default to 5 and the second one to 150ms. You can try multiplying these by 10 and see if it helps:
workflow.output.retryPolicy.delay = 50
workflow.output.retryPolicy.maxAttempt = "3500ms"

(It would also eventually be nice to have a "fail index" per file and not per folder, but this looks a bit more tricky on the Nextflow side...)

@cavenel Thank you so much for the suggestion and for pointing me to the right setting to increase the retry delay and max attempt.
I had tried to increase the equivalents in the AWS config but that didn't work.
Using
workflow.output.retryPolicy.delay = "3500ms"
workflow.output.retryPolicy.maxAttempt = 50

Seem to have solve the problem when I ran 1 sample from my samplesheet. Currently rerunning the full samplesheet to double check.
PS: You inverted the values in your example, flagging it for anyone who may blindly copy paste the snipped in their .config file ;)

Great, let us know if it works on the full samplesheet so that we can close this issue.
(I fixed my inversion, sorry about that!)

@cavenel I've now confirmed that the issue persist when the sdata_processed.zarr has been previously copied over to S3 and a rerun with the same output directory has to overwrite the existing data.


[Bug] ModuleNotFoundError: No module named 'numpy'

if i try to launch the app.py from the anaconda prompt i get this error:
ModuleNotFoundError: No module named 'numpy'

OS: windows

I had same error when I was using wrong location of activate.bat script.
Now I am using start-up.bat placed in stablediffusion-infinity folder:
call %userprofile%\Miniconda3\Scripts\activate.bat sd-inf
python "app.py"
cmd /k

you can use this, just check if the location of anaconda on the first line is right.


Is there an old version of Daedalus that can connect and work with the Nano X ADA app v2.0.3 (dated from around Aug 2020)?

Is there an old version of Daedalus that can connect and work with the Nano X ADA app v2.0.3 (dated from around Aug 2020)?
We have a Nano X that secures large ADA funds (~$100k value), that has the ledger ADA app v2.0.3 (from around Aug 2020). Unfortunately the ledger seed phrase is lost, so we do not want to update the ledger firmware (risk of reset and losing all the funds).
We tried connecting to the Nano X with the current version of Daedalus, and it will not connect to the ADA app on the ledger. We tried running Daedalus as administrator, no luck. It connects well with Ledger ADA app 2.4.1 (on a slightly more recent Nano X), but no luck with v2.0.3. I also tried Adalite, no luck either (says the ledger app is too old).
We tried with Daeladus 2.3.0 (from mid 2020), but it cannot connect to a ledger (does not have the functionality).
The first version of Daedalus that has the function to connect to a ledger is I believe 3.0.0? Do you think it will support this ADA app v 2.0.3 on the ledger?
I found that the first version that works with ADA app 2.4.1 is Daedalus 4.0.3. I am just not sure which of the 3.x versions will support ledger ADA app v2.0.3...
Does anyone know?

It would be possible to export the keys from the Nano X on the cli. But normally an cardano-app update or a firmware update does not require to reenter the seedphrase on the ledger.


How to only show gutterHints and hide hints?

I think the hints (^ $ e w) is not very usable, how not show it?

I am on mobile so can't easily give an example
But within the config, set the hints you don't want to nil
Thanks

return {
    "tris203/precognition.nvim",
    config = {
    -- startVisible = true,
    -- hints = {
         ["^"] = nil,
         ["$"] = nil,
         ["w"] = nil,
         ["b"] = nil,
         ["e"] = nil,
    -- },
    -- gutterHints = {
    --     --prio is not currentlt used for gutter hints
    --     ["G"] = { text = "G", prio = 1 },
    --     ["gg"] = { text = "gg", prio = 1 },
    --     ["{"] = { text = "{", prio = 1 },
    --     ["}"] = { text = "}", prio = 1 },
    -- },
    },
}

This can now be done by setting all the 	prio keys to 0
and setting showBlankVirtLine to false
Details are in the README


Allow BoundedExecutor to recover from failures

Previously submitted tasks will eventually run if the underlying
executor recovers and additional tasks are submitted.

To achieve the desired behavior, we really only have 3 possible options here:

Make the bounded executor fully synchronized for all task submissions (only allowing one submission at a time) -- but this might add unwanted overhead in high performance cases since none of the existing code or dependencies use any locks.
Add a scheduled background thread pool whose job is to keep retrying failed task submission retries forever until success
Consume the calling thread as one of the draining tasks in the event of thread pool failure -- while technically this wouldn't corrupt the data structure, this would be terrible for callers and so this isn't really a desirable path.

There is no way to make this magically work without one of these three options. For me, I would suggest (2).


[Feature]: add python under data science

Is your feature request related to a problem? Please describe.

in the data science page there is a card titled "python".
remove that card. insert a new card titled "python". then create the page as well and provide all resources for python such as documentations, youtube channels and courses
Describe the solution you'd like
No response
Describe alternatives you've considered
No response
Additional context
No response

please assign me to this task

please assign me to this task

i have changed the name coding to python

please assign me to this task

i have changed the name coding to python

should i create a new page named python and add resources?

@

please assign me to this task

i have changed the name coding to python

should i create a new page named python and add resources?

@sajithsojan yes

assigned

@sajithsojan you may have a look at the social media component page. in which we have displayed 3 youtube videos. maybe it will help.
and which link are you copying? to properly embed the videos, you should copy the "embed link" of the video and not the share link

@sajithsojan you may have a look at the social media component page. in which we have displayed 3 youtube videos. maybe it will help.
and which link are you copying? to properly embed the videos, you should copy the "embed link" of the video and not the share link

Ok thank you let me correct it

@sajithsojan have you raised a PR?

@sajithsojan have you raised a PR?

Ok I will raise a PR

resolved


add unit test framework

[x] network filter
[x] root contex
[ ] http context + http related host calls
[ ] http callouts
[x] shared queue
[x] shared data
[x] metrics

https://github.com/tetratelabs/getenvoy/issues/101


Create CONTRIBUTING.md

Linked to cyberark/community#30

@izgeri Done

@doodlesbykumbi I don't understand how, but the test is broken on this branch. master looks green. any ideas?


[usecase-apptools] Add tests to check apk size for apptools usecase

Failure analysis:
https://crosswalk-project.org/jira/browse/XWALK-6470
Impacted tests(approved): new 2, update 7, delete 0
Unit test platform: [Android]
Unit test result summary: pass 8, fail 1, block 0
BUG=https://crosswalk-project.org/jira/browse/XWALK-6499

LGTM


[enhancement] Expose bech32 encode and decode

Parity with sui keytool conversions

Added in 0.50.0


Destroying jersey cleaner thread on DiscoveryClient shutdown

When reloading or shutting down the context in Tomcat 8 we get a warning that there was a thread created but not cleaned up:
WARNING: The web application [example] appears to have started a thread named [Eureka-JerseyClient-Conn-Cleaner2] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
 sun.misc.Unsafe.park(Native Method)
 java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
 java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2078)
 java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1093)
 java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809)
 java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067)
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127)
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
 java.lang.Thread.run(Thread.java:745)

Evidence for this being a problem can be found in the Spring Cloud project:
EurekaDiscoveryClientConfiguration.java
My suggested solution is to check for a discoveryJerseyClient object, and clean it up during the DiscoveryClient shutdown method.
I have provided a test that demonstrates the thread living beyond the shutdown command in it's current state.

NetflixOSS » eureka » eureka-pull-requests #233 SUCCESS
This pull request looks good

@jeremydyoung thanks for the fix.


Needs updating for Replica Sets

This page's info is out-of-date re: use of a single region.  Azure AD Enterprise and Premium support Replica Sets, which should be incorporated into this page re: network design considerations.  Also, is it still a priority to dedicate an entire VNET to AADDS?  Forwarder support on VNET DNS is much improved now.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 7013d117-4c2e-1b3e-0b67-d3eec67dc490
Version Independent ID: c948be62-abef-57bb-232c-970ccfec504c
Content: Network planning and connections for Azure AD Domain Services
Content Source: articles/active-directory-domain-services/network-considerations.md
Service: active-directory
Sub-service: domain-services
GitHub Login: @Justinha
Microsoft Alias: justinha

@kpraxor sorry for delay and thanks for raising this. I created an internal work item for SMEs to review and update the topic as needed. #please-close


Bug: System is not properly adding TEE Data

Context
When adding TEE data the system displays the following error:  [EXTEXEM-8-A] - Another [Test Extension Exemption] record already exists with the same [extensionOrExemptionCode, reportPeriodId, monitoringSystemId, componentId, fuelCode
But despite the error the newly added TEE data is added to the TEE Data table
Steps to Reproduce

Log in to ECMPS and Navigate to Cert events, extensions, and exemptions section
Check out a config
Select Test Extension Exemption data in the drop down
Add a TEE record and select save

The system displays the following alert: [EXTEXEM-8-A] - Another [Test Extension Exemption] record already exists with the same [extensionOrExemptionCode, reportPeriodId, monitoringSystemId, componentId, fuelCode
However the newly enetered data is added to the TEE table. Need to look into why the error is displaying and why the system is adding the data despite the error.

Bug fixed. Only the original was added. After the error, the duplicate was not added.


(MODULES-8566) Only create entries for defined settings

This makes it so that templates/haproxy_resolver_block.erb only creates config entries for values that the user has specified. All other values can have defaults provided by HAProxy

@genebean Unfortunately your changes are currently failing the unit tests

@david22swan I don't know why I have such a hard time remembering to to pdk validate; pdk test unit before putting in a pr... sorry about that. Anyhow, it should be good now.

@genebean Don't worry about it, can't tell you how many times I've made a pr ony to notice it failing on the rubocop check.
Anyway this passed an adhoc run so I'm happy to merge.


roll the cico_* scripts into the app Makefiles

we should roll in the cico_* scripts into the app Makefiles to retain a consistent place / process to execute these steps.

Done! Closing this issue.


Wrong Typescript definition of Request, Session and User

Hey guys,
the current master branch has a wrong typescript definition of request, session and user object.
They should be:
getSession: () => {
    details: alexa.Session,
    sessionId: string,
    attributes: any
  };

export interface Session {
  new: boolean;
  sessionId: string;
  attributes: any;
  application: {
    applicationId: string;
  };
  user: User;
  userId: string;
  accessToken: string | null;
}

export interface User {
    userId: string;
    accessToken?: string;
}

Here is some evidence from cloudwatch:
console.log(request.getSession())
{
  isAvailable: [
    Function
  ],
  isNew: [
    Function
  ],
  get: [
    Function
  ],
  set: [
    Function
  ],
  clear: [
    Function
  ],
  details: {
    new: true,
    sessionId: 'YOU WISH :P',
    application: {
      applicationId: 'YOU WISH :P'
    },
    user: {
      userId: 'YOU WISH :P',
      accessToken: 'YOU WISH :P'
    },
    userId: 'YOU WISH :P',
    accessToken: 'YOU WISH :P'
  },
  attributes: {},
  sessionId: 'YOU WISH :P',
  getAttributes: [
    Function
  ]
}

Would be nice if you could fix it.
Greetings
/ben

Would be nice if you could PR a fix, please?

sure. will do that.


USB: HID: Add new callback and refactor sample

Codecov Report

Merging #10107 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master   #10107   +/-   ##
=======================================
  Coverage   52.48%   52.48%
=======================================
  Files         213      213
  Lines       26135    26135
  Branches     5633     5633
=======================================
  Hits        13718    13718
  Misses      10160    10160
  Partials     2257     2257

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 68249ce...5ed585b. Read the comment docs.

Thanks @finikorg for the changes. I have looked at it and the code seems all fine now. However I have tried it on a real board (nucleo_l432kc) and now that the calls to hid_int_ep_write are chained to the in_ready_cb instead of being a regular call, the loop stops after 15-20 times. I haven't debugged it further, it might be a bug in the USB driver. It might be worth trying on another board.

@aurel32 I tested this with quark_se and it was working but now I added delayed_work report sender with 2 sec delay, it would be the same behaviour as before.

@dbkinder @pdunaj Could you recheck the changes I made.

@finikorg rebase please

maybe you want to move the sample to the new logger now that USB has moved..

@nashif updated HID sample to the new USB logger


Add robots.txt to CR app

https://developers.google.com/search/docs/advanced/robots/intro

Added to Backlog.


udpate llm fake data

remove the data level in llm/raw/data/.... see #87

for rinpersoon ids, use strings of length 9 with 0-padding.


Some guides for offsets and scrollableAncestor

In #88, a request was made for demos of how to use these props. I think demos are a great idea! I'd love to see more demos for this library.
This PR doesn't add demos, but what it does add are explanations for why these props are useful, and situations where a developer might use them. I wrote this pretty quick, so go ahead and give lots of feedback. Also, what do you think of the general approach of including text-based guides? Good idea? Bad idea? Is it too verbose? 😛
I'm just trying to come up with ways to help consumers of the lib. Let me know what you think!

Apart from a little confusion around scrollableAncestor, this would be a great addition to the README.

Made some tweaks based on the feedback. Lmk if there's anything else! I kept the update commit separate so that it's easier to review. I can squash when it's time to merge :v:

This is great! Thanks for putting this together. :)

@lencioni thanks for the feedback! I agreed with all of those recommendations, and I think I've fixed them all with the latest commit. Let me know if you catch anything else.

LGTM

Looks good to me too! I'll let you merge this yourself, since you are now a member of this project. :)

Thanks for the review, you two! Merged :tada:


Refactoring to thin out notation pkg

Refactoring to thin out notation pkg

Codecov Report

Merging #335 (d491b20) into main (2882baf) will decrease coverage by 0.33%.
The diff coverage is 52.70%.

: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             @@
##             main     #335      +/-   ##
==========================================
- Coverage   74.80%   74.48%   -0.33%
==========================================
  Files          23       23
  Lines        2203     2226      +23
==========================================
+ Hits         1648     1658      +10
- Misses        437      453      +16
+ Partials      118      115       -3

Impacted Files
Coverage Δ

internal/file/file.go
28.57% <30.30%> (ø)

signingkeys/signingkeys.go
73.17% <63.63%> (ø)

config/config.go
67.85% <78.94%> (+23.41%)
:arrow_up:

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

Slate PR,


Add missing \n in  configuration generator for systemd-boot

Motivation for this change
This adds a missing \n in the configuratin generator for systemd-boot (formerly gummiboot).  Because of the missing \n, the following config bit:
boot.loader.systemd-boot.editor = false;
boot.loader.systemd-boot.consoleMode = "auto";

would produce a file ending with:
editor 0console-mode auto

instead of
editor 0
console-mode auto

Things done
(None yet, sorry.   I have no idea how to test this, and I assume the change is straightforward enough.  Just tell me if you want any of these tests done, I'll look up how :)

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Fits CONTRIBUTING.md.

I ran some of our installer and uefi tests with systemd-boot.consoleMode set, and everything seems to be just fine. Thank you! :)

@srhb Notice you also need boot.loader.systemd-boot.editor = false;, which is where the actual bug lies!  (Also, please tell me if I can help testing!)

@thblt If you're curious, I've mostly been hand-editing nixos/tests/installer.nix and running it with nix-build :) I'll try your suggestion as well.
Also, could you please amend the commit message to fit CONTRIBUTING.md? It should be "nixos/systemd-boot: Add missing newline" or something like that. :)

Also, could you please amend the commit message to fit CONTRIBUTING.md?

Should be good.

Thank you again! :1st_place_medal:


Implement CornerRadius

Right now it is defined by float type and does not allow setting distinct values for each corner like this:
<Border CornerRadius="1,2,3,4"/>

The previous attempt to implement this: https://github.com/AvaloniaUI/Avalonia/pull/1281

OK, I'll return to work soon.

@vertexpipeline this has now been implemented: https://github.com/AvaloniaUI/Avalonia/pull/1462


Fixed author daedname for the Pathfinder (Cazra) sheet.

Submission Checklist
Required

[x ] The pull request title clearly contains the name of the sheet I am editing.
[x ] The pull request title clearly states the type of change I am submitting (New Sheet/New Feature/Bugfix/etc.).
[x ] The pull request makes changes to files in only one sub-folder.
[x ] The pull request does not contain changes to any json files in the translations folder (translation.json is permitted)

New Sheet Details

The name of this game is: <   >  (i.e. Dungeons & Dragons 5th Edition, The Dresden Files RPG)

The publisher of this game is: <   > (i.e. Wizards of the Coast, Evil Hat)

The name of this game system/family is: <   > (i.e. Dungeons & Dragons, FATE)

[ ] I have followed the Character Sheets Standards when building this sheet.

[ ] This sheet has been made on behalf of, or by, the game's publisher.
[ ] This game is not a traditionally published game, but a copy of the game rules can be purchased/downloaded/found at: <   >
[ ] This sheet is for an unofficial fan game, modification to an existing game, or a homebrew system.

Changes / Description
Fixed author's deadname for the Pathfinder (Cazra) sheet.

Character Sheet Info Roll20 Internal Use only.

This update broke the sheet for a lot of people. There's a thread on roll20 with people discussing this, and it's looking like the CSS layout is busted.
https://app.roll20.net/forum/post/10919585/pathfinder-simple-character-sheets-not-working/?pageforid=10920055#post-10920055
from the thread:
Kraynic: "I believe the issue is that they just did an update to the sheet.json and forgot the legacy switch, and so the css isn't rendering correctly."
May want to review this push and see if you left anything out.


Prevent crash when MeterReporter is deallocated before upload

If the client calls start() on a MeterReporter instance but does not keep a strong reference to this instance, then it gets deallocated and if any log is available to upload a crash occurs after 10 seconds.
Not sure this is the best way to fix this -- maybe intentionally creating a retain cycle is preferable so that clients don't have to retain their MeterReporter.

Thank you for working on this! I'm sorry this happened. I'm so used to using unowned to catch lifecycle issues early, and I got a little careless here.
What do you think about just logging in deinit to simplify?

Thank you and no worries – I've released a fix to my app already (by just storing a static reference to the MeterKit object). I've had your code in production for months and I trust it so much that I blindly replaced Stacksift with MeterKit, but it's my entirely my fault for not testing a crash before releasing it.
Logging in deinit does makes it a lot simpler! I can update this if you like, but what should the log say in deinit, and what level? The downside of doing it there is not knowing if there are reports to process in deinit (unless you see a simple way).
PS – The README currently doesn't show or mention having to keep the MeterKit object alive.

Alternatively the start() function could store a reference to itself to prevent any deallocation, and you could add a stop() function to release it.

Amended to only prevent the crash!  I'd personally favour a further change so that calling start() keeps the MeterReporter alive and working regardless of whether the caller keeps hold of it.