robonomics io write datalog error

Problem
Hi
I am trying to use robonomics io write datalog, but haven't got an expected result.
Test
In one terminal i launch:
echo "test" |  ./robonomics io write datalog -s <key>  --remote wss://ipci.rpc.robonomics.network

Result
As the result i got such error:
thread 'main' panicked at 'there is no timer running, must be called from the context of a Tokio 0.2.x runtime', /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-0.2.25/src/time/driver/handle.rs:24:32

I've tried to launch in local node as well:
./robonomics --dev
echo "on" | ./robonomics io write datalog -s <KEY>

but got the same result.
Robonomics version
./robonomics --version
robonomics 1.0.0-af3b009-x86_64-linux-gnu

Thank you for the report @tubleronchik, looks like something wrong with the execution runtime for this command. It will be fixed in the next patch release.

Hello.
I see the same error, when run robonomics io read launch command.
Test
First terminal:
 ./robonomics --dev --tmp

then, in other terminal:
$ ./robonomics io read launch

Result
thread 'async-std/runtime' panicked at 'there is no timer running, must be called from the context of a Tokio 0.2.x runtime', /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-0.2.25/src/time/driver/handle.rs:24:32
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

robonomics version - robonomics 1.0.0-af3b009-x86_64-linux-gnu

Should be fixed in https://github.com/airalab/robonomics/commit/99d70ca1baeccb19954c27fd29775d29f542497e


[Stretch] Improve celo-blockchain performance in the wallet

@nityas the epic is over but should this still be open?


[backport] Fallback to system headers for future CUDA 12.x versions

Backport of #8518 by @kmaehashi

/test mini


CLI doesn't save output from large input file (~16Go)

./build/bin/Holovibes.exe -i  C:/capture/240718_PUD0162_od.holo -o D:/cap/take_cli.holo -f 5000 -v 3 -e 2048
./build/bin/Holovibes.exe -i  C:/capture/240718_PUD0162_od.holo -o D:/cap/take_cli.avi --gpu -f 5000 -n 128 -v 3 -e 16384

File of size 1Go are already much much slower to process in cli dans gui mode
The CLI mode needs to be studied as it clearly doesn't share the same performances as the GUI mode.

The CLI seem to be abnormally slow in the current version, with result sometime being plain wrong (image feed being 4 image with 2 raw and 2 black)

Issue about the cli being slow on small file ~1Go fixed:
inputfps by default is 60, and --fps option doesn't set it properly

Issue about the cli being slow on small file ~1Go fixed:
inputfps by default is 60, and --fps option doesn't set it properly

##╗Its not actually the size that causes the infinite loop at the end of the bar
Taking a 16 Go file and separating it to a 1Go one doesn't get it to run on the cli still

Fixed, was due to a export_file category in the compute_settings that was hard wiring the pipeline into raw mode
export_file category has been removed in consequence.


hasImage() function throws exception instead of returning false

Description
Using the ->hasImage() function on a model with the HasMedias trait will always throw an exception when the result should be false. Seems like this is caused by the $this->findMedia($role, $crop); that gets called, as in the findMedia function itself, the exception is thrown when the given crop is not found.
Steps to reproduce
Call the ->hasImage function on a model with the HasMedias trait.
Expected result
Function returns false.
Actual result
Throws a MediaCropNotFoundException
Versions
Twill version:  2.7
Laravel version: 9.2
PHP version: 8.0.2

Hey @lindeVW,
This is a debug only exception. But I guess we can make it an optional one.
I added a pr.

Since this is causing a lot of confusion, and because I agree that hasImage should not be throwing an exception, even in debug, I would recommend we patch 2.7 by preserving the previous behavior of the hasImage function. In Twill 3, we can refactor to add a cropExists function as well as introduce the option as you already did. What do you think @haringsrob?


Feat/landing-page-design-update

I think we need to add a paragraph that explains this section too


Better support for drawn feature layer

Keep the layer of drawn features always on top
Add a button for removing all drawn features

Implemented.


feature/v2.3.0

Codecov Report
Base: 78.11% // Head: 78.13% // Increases project coverage by +0.02% :tada:

Coverage data is based on head (2508ce0) compared to base (7d1a508).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #2296      +/-   ##
==========================================
+ Coverage   78.11%   78.13%   +0.02%
==========================================
  Files         583      580       -3
  Lines       48448    48109     -339
==========================================
- Hits        37844    37591     -253
+ Misses       8592     8521      -71
+ Partials     2012     1997      -15

Flag
Coverage Δ

go-1.15-386
?

go-1.15-amd64
?

go-1.16-386
?

go-1.16-amd64
78.13% <0.00%> (+<0.01%)
:arrow_up:

go-1.17-386
?

go-1.17-amd64
?

go-1.18-386
?

go-1.18-amd64
?

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

Impacted Files
Coverage Δ

os/gcron/gcron_schedule_fix.go
87.50% <0.00%> (-12.50%)
:arrow_down:

os/gcache/gcache_adapter_memory_lru.go
89.13% <0.00%> (-8.70%)
:arrow_down:

os/gspath/gspath_cache.go
87.71% <0.00%> (-7.02%)
:arrow_down:

net/gtcp/gtcp_pool.go
72.22% <0.00%> (-3.34%)
:arrow_down:

net/ghttp/ghttp_server.go
65.31% <0.00%> (-0.64%)
:arrow_down:

container/gtree/gtree_avltree.go
95.40% <0.00%> (-0.58%)
:arrow_down:

contrib/config/kubecm/kubecm_kube.go

contrib/drivers/oracle/oracle.go

contrib/config/kubecm/kubecm.go

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


kv prewrite slow on insert with big rowsize

Bug Report
What version of TiKV are you using?

TiKV 4.0.0-alpha
Git Commit Hash:   4f782d4a74487484298c4a8473961bcbfabd9c25
Git Commit Branch: master
Rust Version:      rustc 1.37.0-nightly (0e4a56b4b 2019-06-13)
default tikv config parameters without modifying anything, deployed with ansible
What operating system and CPU are you using?

linux idc machine with 40core cpu 188GB mem 7TB nvme disk
What did you do?

runing tests on "load data statements",  that is inserts with batch size rows per transaction
schema like
CREATE TABLE `tin_n_10wb` (
  `pk` int(11) DEFAULT NULL,
  `col1` blob DEFAULT NULL,
  `col2` text DEFAULT NULL,
`col3` varchar(200) DEFAULT NULL,
  ...
 `col95` blob DEFAULT NULL,
 `col96` text DEFAULT NULL,
  ...

column content like
len("G2jOVOMOg3Cnub2jCuXtn0AO1V5hONfLftt0cBHX74itPKMm2uVj1Ax1GfykLLR6PxGclMhPRQxoCe8ZvYI096goa6CsxKHiBvpl7SOp0ax5vl1QNYUZq2x2") = 120

inserts with 100k rows, (one row 120 * 100 = 12KB,  batchsize = 5k, one batch = 60MB, batchsize = 1k, batchsize=12MB)
MySQL [b100c]> load data local infile '/data1/rwork/10wbigrow.dat' into table b100c;
Query OK, 100000 rows affected (13 min 18.90 sec)
Records: 100000  Deleted: 0  Skipped: 0  Warnings: 0

set tidb_dml_batch_size = 1000;
MySQL [b100c]> load data local infile '/data1/rwork/10wbigrow.dat' into table 1k_2;
Query OK, 100000 rows affected (1 min 1.28 sec)
Records: 100000  Deleted: 0  Skipped: 0  Warnings: 0

on tidb statistics, committing one txn on batchsize=5k costs about 40s, committing one txn on batchsize =1k cost about (300-800ms),  the rt on load stmt is quite different
prewrite on batchsize = 5k is quite slow from grafana data(32s), prewrite  on batchsize = 1k,  durations is also not very stable
tidb  kv request

tikv grpc details

does tikv has some perf problem on this workload(batch insert with many columns and big row size)
related bench on this tidb pr(https://github.com/pingcap/tidb/pull/11533)
What did you expect to see?
What did you see instead?

For the TiKV metrics, seems you didn't choose the same time range as TiDB?

kv metric is the latter tests on batch size = 2k, tidb prewrite metric shows 8s and 4s(the latter two blue line after 12:40)

another run on batchsize = 5k
TiDB metric

TiKV metric

solved. closed


[ENH] Add AEDRNNClusterer

Implements Clusterer based on Dilated Recurrent Neural Network (DRNN).

@aadya940 i think an issue is happening when importing the custom layer from the networks package, one possibility is because its wrapped under a condition, to debug this (i dont think its the best solution) can you implement as well the custom layer inside ae_drnn.py but the clusterer ? it is just to see if CI is failing because of this

@hadifawaz1999 Now they are the same :))

#1962


render: add wlr_egl_create_from_drm_fd function

This function relies on the extension EGL_WL_bind_wayland_display being present. If not, the creation of wlr_egl will fallback on using GBM.
I see in the logs that the client extensions are being printed twice, would you prefer the fallback to be in wlr_egl_create_from_drm_fd rather than in wlr_renderer_autocreate_with_drm_fd?
I also I fixed an issue regarding eglMakeCurrent when processing the error, EGL_NO_DISPLAY is not a valid display handle and will cause an EGL_BAD_DISPLAY error.

As with other commands taking EGLDisplay parameters, if display is not a valid EGLDisplay handle, an EGL_BAD_DISPLAY error is generated. (Some implementations have chosen to allow EGL_NO_DISPLAY as a valid display parameter for eglMakeCurrent. This behavior is not portable to all EGL implementations, and should be considered as an undocumented vendor extension).

https://www.khronos.org/registry/EGL/sdk/docs/man/html/eglMakeCurrent.xhtml
Fixes #2649

Note, the Mesa MR that makes the device platform work is: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/8638

Note, the Mesa MR that makes the device platform work is: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/8638

Unfortunately this PR breaks split display/render devices. This happens because Mesa doesn't create an EGLDevice for the display-only device, even if kmsro would make it work. See https://gitlab.freedesktop.org/mesa/mesa/-/issues/4178.

Unfortunately this PR breaks split display/render devices. This happens because Mesa doesn't create an EGLDevice for the display-only device, even if kmsro would make it work. See https://gitlab.freedesktop.org/mesa/mesa/-/issues/4178.

Want me to take a look at that issue?

Want me to take a look at that issue?

It's a tricky issue, I'm not sure what's the best way to fix it. I'd like to hear ideas from Mesa devs.

It's a tricky issue, I'm not sure what's the best way to fix it. I'd like to hear ideas from Mesa devs.

I'll keep an eye on the issue then, let me know if I can do anything to help

I'll keep an eye on the issue then, let me know if I can do anything to help

Unfortunately this PR breaks split display/render devices.

If we keep the GBM fallback, it should work fine. Unfortunately this means we can't get rid of GBM in the renderer yet.

Alpine failure because of some python trouble

The fix is finally in Mesa 21.1.0, I'll rebase the patch.

@emersion rebased and ready to be reviewed :D


⚠ Secret Website 3 has degraded performance

In 17c9c0b, Secret Website 3 ($SECRET_WEBSITE_3) experienced degraded performance:

HTTP code: 200
Response time: 2137 ms

Resolved: Secret Website 3 performance has improved in bc5effc.


trival updates of mpt circuit

This PR update the specification of a maxium row usage for mpt circuit, eliminate the confusing on this option.
Notice it may break the consistency of vk/pk.
It also re-export some required structures, helping scroll-zkevm wrapping a stand-alone mpt circuit without depend on mpt-circuit crate directly.

Has been include in #291


Will Mcbist check all addresses of all DIMMs?

https://github.com/open-power/hostboot/blob/c4227d1e3dcf86b00ce0275cfebe2148d2035a24/src/import/generic/memory/lib/utils/mcbist/gen_mss_memdiags.H#L678
Will Mcbist check overwrite all memory cells? Also, is the error detected by Mcbist during the IPL process handled by the prdf module?
Thanks!

memdiags will initialize all addresses with good ECC and will verify all addresses have good ECC.

Yes - PRD will log ECC errors found during memdiags. However logging of CEs in memdiags requires enabling mnfg policy flag 'memdiags CE screening'.

So, if memodiag detects the same type of error(Maintenance IMPE for example) on different memory cells, will it record all incorrect addresses? Will each address also be processed once during PRDF processing?
What I want to do now is to record all memory errors on the system, whether they are recoverable or unrecoverable.

Okay，got it, thank you very much!


{Branch Management} Merge release 2.27.1 back to dev

Merge fix https://github.com/Azure/azure-cli/pull/19187 back to dev.
🛑 Don't squash merge but merge it locally and push.

Branch Management


"good" state for ListenerStatus feels logically inverted, difficult to understand

What would you like to be added:

Add ListenerConditionType Attached (or possibly Accepted for parity with other objects, ref #1111 ), deprecate Detached

Why this is needed:
From a quick glance, seeing a ListenerStatus with Detached and Conflicted conditions on a Gateway can be a red herring leading an operator to initially think a Listener is not working properly - this may be particularly confusing for new users unfamiliar with checking for the "negative" case of Detached: {status: false, reason: Attached}, Conflicted: {status: false, reason: NoConflicts} meaning that the Listener is actually in a "good" state.
This potential confusion about whether a Listener is working as expected is slightly exacerbated by the ListenerStatus field being a child of GatewayStatus rather than being a status field directly on Listener.
I initially considered if Conflicted should be changed too, but I think just this change alone could make the status conditions for a Listener feel a bit more intuitve.

Agreed, we should have the same Attached condition type across every place we use conditions, and have it mean the same thing.

/remove-lifecycle stale

GEP-1364 has been approved, deprecating ListenerConditionDetached and proposing that ListenerConditionAccepted be used instead.
This GEP also addresses the confusion with the Conflicted status by setting an expectation that positive polarity error status conditions should only be present when the error state exists.


Guard not Starting

Running ST3, Guard simply doesn't start when I run the start command. At first I thought my error was similar to #11 (like @ticktricktrack, there is no process running for Guard), however the error @dagobar found in the console differed from mine. I am getting the following:

FileNotFoundError: [Errno 2] No such file or directory: '/Users/[username]/Library/Application Support/Sublime Text 3/Packages/Guard/guard_wrapper'

Yeah, I was able to get it running by manually cloning the repo to the Packages folder and renaming it "Guard".

fixed by #83


Load programmer mode script on start

Hi,
I was wondering if its possible to automatically load some settings on start?
Currently when i start the app, it always starts on PrimeDice->btc, which i don't use.
Then i have to fill in the API key, which auto login does not seem to have a setting for.
And after this i also have to fill in the script that i want to use.
I would love it if it was possible to change the site that loads on start as wel as the default script it loads. Having an option for the API key at auto login would also be great (unless it automatically uses the password field for the API key, but i cannot find any info about this.)
Thanks a lot, and please let me know.
edit: part of this would be easily achieved by loading TempCodeBackup.txt on startup.

Settings are already being loaded on start. The bot should automatically load the last site that you used, but it does not select your currency.
Password in autologin can be used for API key.
The changes you're requesting are outside of the scope of maintenance I am doing on v3 (bug fixes, new sites). I barely have the time to work on the bot anymore, and any time I do have, I want to work on v4. If someone else makes these changes and does a pull request, I'll merge review and merge them if the code quality is good enough.


PHP Notice:  Undefined offset: 0 in disqus-php/disqusapi/disqusapi.php on line 79

Running the code in the README :
require 'disqus-php/disqusapi/disqusapi.php';

$disqus = new DisqusAPI(DISQUS_SECRET_KEY);
$threads = $disqus->trends->listThreads();
var_dump($threads);

outputs a notice message :
PHP Notice:  Undefined offset: 0 in disqus-php/disqusapi/disqusapi.php on line 79

I have tried the same with Laravel. I have tested in localhost and also in live server. In both cases it returns:
Undefined offset: 0
Is there anyone to help me with this problem?


Feature Request - Removal Reason hotkeys

Being able to select a removal reason through hotkeys would be extremely convenient, especially when there's a lot of posts coming in quickly.
Could use full alphanumerics 0-9 + A-Z.
Or allow the user to set hotkeys for selected removal reasons.

Closing this as we already have #845


Add 'ss' relative time key to typescript definition

Hi there,
This patch adds 'ss' to RelativeTimeKey to make the typescript definition more complete, and updates the typing tests to match.
First patch to moment.js, so please let me know if there's anything I'm missing or if you have any suggestions for improvements!

This is the same as #4138 but slightly better, maybe :)

Hi ichernev!
Is there anything that I need to address in the PR for it to be accepted?
Thanks,
Kexiang

@xkxx don't you also need https://github.com/moment/moment/pull/4138/files#diff-3dd6cebe542b0e207494192c4bbf4a22R217

Hi @ichernev,
How's the PR looking now? (Please ignore the git author screwup earlier :/)

Hello @ichernev again,
Could you take a look at this PR and see if there's anything else for it to be merged?
Thanks,
xkxx

Hello, just a friendly ping if anyone would like to take another look at the PR :)

I think this looks good -- tagging for inclusion in the next release.


WsContext class lacks method level java docs.

Describe your issue
Currently, the WsContext class has a class level java doc, but doesn't have any method level java docs. Making it difficult to understand some method functionalities, such as the WsContext#enableAutomaticPings method. You have to dig into the implementation to figure it out yourself.

I've noticed the method WsContext#enableAutomaticPings is not documented on the website at all.


Is this true color?

The 'NavBar' and "Home' should be different color (like yellow), I used treesitter (javascript) and also turn it on in the config
Or I miss out something

There was a big update, it should look like this with latest main:

This is what it should've looked like before:

Thanks for the update


[Question] Camera Location Search Error: You have exceeded your daily request quota for this API

Hi bro,
Thanks for your awsomes  library.
I have run your example and its work greate.
But when i reopen your app again and it gives me an error likes this.
[+2131 ms] I/flutter (16282): Camera Location Search Error: You have exceeded your daily request quota for this API. If you did not set a custom daily request quota, verify your project has an active billing account: http://g.co/dev/maps-no-account
Could you guy please help me explaint what's happen and how can i resolve this issues?
Thank you so much.

Google Maps requires you to have an active subscription. You have to provide your credit card etc., but they will not charge you for small usage. Have you worked yourself through the Getting started section?

Thank you so much


Level 5 Project Test Case5_4

Summary
Put a summary of the question
Description
Hi. Is anyone experiencing this error for Level 5 Project? My customer class takes in a Lazy serviceTime and it will only be called when it is an arrival or wait event but this error keep popping up. Would appreciate any advice! Thank you!

Arrival -> Serve and Arrival -> Wait

Wait -> Serve

Screenshots (if any):
Insert Images here if necessary

The service time of the customer is not known until he/she is being served. It seems like you are already called the customer's service time before being served .
Let's say there are two servers who are currently serving customers and the next two service times are
0.5
0.6
If we have the following events,
A arrives and wait at server 1
Server 2 done serving
B arrives
B served by server 2
A served by server 1
B's service time will be 0.5 as he is served first (determined when served), and A's service time will be 0.6.

Hi there,

does this mean that you only called the Lazy in the SERVE event, but not in the ARRIVE and WAIT event?

Yes, since it is stated that the service time of the customer is not known until he/she is being served. I don't think it is right to call it before SERVE event.

If so, how did you update the state of the servers in ARRIVE and WAIT without having the service time?

For ARRIVE -> SERVE, I update the server to be serving the customer.
For ARRIVE -> WAIT, I update the server to include the customer into the ImList of customers who are waiting.(multiple customers waiting for the same server level 6)
WAIT -> SERVE is a little more tricky and will depend on how you want to implement it. I think there is a good discussion here and here
I do not track the service time of the customer as an attribute of the server.

@hengyjj have you found a way to work around this problem? i have the exact same error in my level 5 test case 4 and i cant think of a way around it without redoing my code completely

@hengyjj have you found a way to work around this problem? i have the exact same error in my level 5 test case 4 and i cant think of a way around it without redoing my code completely

sorry for the late reply. but I have to redo my entire lvl 3 codes to make this work. I implemented an optional of type customer to store the customer that is waiting. so I would use this to check if the server is available or not, instead of using next available time which requires the use of getServiceTime().
I also have methods within my server to indicate if it is serving customer, or holding customer or finish customer, so it would return different states of the server based on the events it is at. this means if I'm at serve event, I would call for e.g. server.serveCustomer(customer, this.eventTime + this.customer.getServiceTime()) so this shld return a new state of the server, and update the server status, and add this updated server status into the server list.


Muscle Memory shows up at a step besides the first

Required Information
Class: Goldsmith
Level: 80
Craftsmanship: 2418
Control: 2432
CP: 519
Recipe Name: Purpure Bead
Recipe Level: 80 three star
Solver Seed:<PHONE_NUMBER>958
Other info: Excluded Rapid Synthesis 1/2 along with Hasty/Patient/Precise Touch, used Mejillones al Ajillo (HQ) and Commanding Craftsman's Syrup (HQ) to boost
Expected Behaviour
Muscle Memory used only on first action
Actual Behaviour
Muscle Memory was used in action 14
Steps To Reproduce
Generate with given seed and settings

this is fixed in #399 but it's waiting to be merged


Missing links to next page

Analyzer.md and aliasing2.md are both missing a link to the next page, requiring returning to the main page before progressing.

right you are. thanks!

should be good now.


Named child routes

Is there a suggested way to make named child routes a la found?
My previous use case was for rendering views for the header, footer, and main content of the page based on the route:
    <Route path="/" Component={GlobalLayout}>
      {{
        header: [
          <Route Component={ErrorBoundary}>
            <Route path="games/:gameId" Component={GameContextProvider}>
              <Route path="/" Component={GameHeader} />
            </Route>
          </Route>,
          <Route path="(.*)?" Component={() => <Fragment>default header</Fragment>} />,
        ],
        footer: [<Route path="(.*)?" Component={DevNotes} />],
        main: [
          <Route path="games">
            <Route path=":gameId" Component={GameContextProvider}>
              <Route Component={DiceContextProvider}>
                <Route path="/" Component={GamePage} />
              </Route>
            </Route>
            <Route path="/" Component={() => <Fragment>Games Index</Fragment>} />
          </Route>,
        ],
      }}
    </Route>

Each key (header, footer, main) is essentially a sub-router. What's the navi way to do this?

There's no built-in way to do this yet, but it would certainly be possible to add to react-navi given the time. I'd be open to pull requests on this.


FindElement() for number strings not working Eg: driver.FindElement(By.Name("2")).Click();

Hi,
While finding an element with number string  eg: driver.FindElement(By.Name("2")).Click();
is giving and error as below:
Error Message:
OpenQA.Selenium.WebDriverException : Selector strategy 'css selector' with value '*[name ="\32 "]' is not supported
Stack Trace:
at OpenQA.Selenium.WebDriver.UnpackAndThrowOnError(Response errorResponse, String commandToExecute)
at OpenQA.Selenium.WebDriver.ExecuteAsync(String driverCommandToExecute, Dictionary2 parameters)    at OpenQA.Selenium.WebDriver.Execute(String driverCommandToExecute, Dictionary2 parameters)
at OpenQA.Selenium.WebDriver.FindElement(String mechanism, String value)
at OpenQA.Selenium.By.<.ctor>b__11_0(ISearchContext context)
at OpenQA.Selenium.By.FindElement(ISearchContext context)
at OpenQA.Selenium.WebDriver.FindElement(By by)
at FlaSelOne.POApprove.POApproveTest() in D:\KitePack\POC\CS\FlaUISelenium\FlaSelOne\POApprove.cs:line 48
at System.RuntimeMethodHandle.InvokeMethod(Object target, Void** arguments, Signature sig, Boolean isConstructor)
at System.Reflection.MethodBaseInvoker.InvokeWithNoArgs(Object obj, BindingFlags invokeAttr)
I tried with the escape sequence as well but had no luck.
The Inspect screenshot -

That is weird, I would not expect a \3 in that error message *[name ="\32 "].
It could be that the SimpleCssAttributeRegex (which is not so simple) does not work correctly. I'll check. See https://github.com/FlaUI/FlaUI.WebDriver/blob/8c0296268d60afe098ac72959a6d66c03a2940d8/src/FlaUI.WebDriver/Controllers/FindElementsController.cs#L126

Hi @lagori , this seems to be an issue in the Selenium .NET client that translates By.Name("2") into *[name ="\32 "]. Could you log this issue at https://github.com/SeleniumHQ/selenium/issues?
See https://github.com/SeleniumHQ/selenium/blob/0fe28e300f0fdc88b07cb3421fb303b4a8e42a8e/dotnet/src/webdriver/By.cs#L393


Stripe doesn't accept payments of less than 0.50 EUR

The website currently returns a 500 for such purchases. We should fix this to prevent such purchases:
PaymentError at /cart/payment/2d1fdfb1-7908-4855-98a3-******/
OrderedDict([('code', 'amount_too_small'), ('doc_url', 'https://stripe.com/docs/error-codes/amount-too-small'), ('message', 'Amount must be at least €0.50 eur'), ('type', 'invalid_request_error')])

This is an issue, but unlikely to happen often in production.

How can I reproduce this one?

On 21.04.2020 16:26, Stéphane Wirtel wrote:

How can I reproduce this one?

Either change a fare to e.g. 0.25 EUR or use a coupon with value
99.99% on one of the existing fares. All, on a test server, not the
prod one, of course.
--
Marc-Andre Lemburg
http://www.malemburg.com/


Jesse: Watch lepusjeweller.com

Jesse requests the watch of the watch_keyword lepusjeweller\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

Approved by Jeff Schaller in Charcoal HQ


"The dependencies needed to run the server did not install correctly, and I was unable to see the result in the preview tab."

Describe the bug
"The dependencies needed to run the server did not install correctly, and I was unable to see the result in the preview tab."
Link to the Bolt URL that caused the error
https://bolt.new/~/sb1-k4n6pz
Steps to reproduce

I opened the new project in bolt.new.
I installed the necessary dependencies according to the instructions.
I attempted to run the server from the development environment.
I accessed the "Preview" tab to see the result, but it did not load correctly.

Expected behavior
I expected the dependencies to install correctly and the server to run smoothly, allowing me to view the project output in the 'Preview' tab without issues
Screen Recording / Screenshot
No response
Platform
Browser name = Chrome
Full version = <IP_ADDRESS>
Major version = 130
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
performance.memory = {
  "totalJSHeapSize": 101810587,
  "usedJSHeapSize": 82618239,
  "jsHeapSizeLimit":<PHONE_NUMBER>
}
Username = daniemen2388
Chat ID = f653283b2c79

Additional context
No response

Appreciate the feedback! We are aware of this issue and are tracking it here: #2021


Internet explorer 11: TypeError - object doesn't support property or method 'startsWith'

Steps to reproduce:

Use Internet Explorer 11 (havn't tested lower version)
Navigate to itsyou.online
Fill in an incorrect username/password and click login
No feedback is given to the user

Open the developer tools and navigate to the console.
TypeError is displayed.

The documentation of the JS library states that IE is not supported for the method startsWith (https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/String/startsWith)
The same goes for retrieving a password based on username (email works)

@n-dury Thank your for the detailed bug report


Added generated PR notices into Group operations PR description

Description
What are you trying to accomplish?
Implementing a feature, https://github.com/dependabot/dependabot-core/pull/10399 to include generated PR notices into the PR which are created by the group operations. This ensures that important messages, warnings, and deprecations are clearly communicated in the PR description.
What issues does this affect or fix?
This enhancement adds the ability to pass generated PR notices into the PR message for update all versions, ensuring that relevant information is prominently displayed in the PR description. Currently, this includes the bundler v1 deprecation warning.
Anything you want to highlight for special attention from reviewers?

This PR extends the functionality of the  group operations to include generated PR notices in the PR description.
The generated PR notices can include various types of messages such as informational messages, warnings, and errors to provide a comprehensive overview of the updates.
Since we generated bundler v1 deprecation warning, currently it is aiming to add this warning into the PR for bundler eco-system when PR is generated by bundler v1

How will you know you've accomplished your goal?

Demonstration: The generated PR notices, including the bundler v1 deprecation warning, should appear in the PR description for security updates, ensuring that all relevant information is clearly communicated.

Checklist

[x] I have run the complete test suite to ensure all tests and linters pass.
[x] I have thoroughly tested my code changes to ensure they work as expected, including adding additional tests for new functionality.
[x] I have written clear and descriptive commit messages.
[x] I have provided a detailed description of the changes in the pull request, including the problem it addresses, how it fixes the problem, and any relevant details about the implementation.
[x] I have ensured that the code is well-documented and easy to understand.

The feature implemented in the following PR, https://github.com/dependabot/dependabot-core/pull/10421


carthage 0.14.0 complaining about missing shared framework schemes

Trying to add a carthage dependency on libextobjc and getting the following when running carthage update or carthage bootstrap:
*** Checking out libextobjc at "0.4.1"
*** xcodebuild output can be found in /var/folders/zx/_rxl1j717bb2bwk2g4wf0dcw0000gp/T/carthage-xcodebuild.hMhDtz.log
*** Skipped building libextobjc due to the error:
Dependency "libextobjc" has no shared framework schemes

If you believe this to be an error, please file an issue with the maintainers at https://github.com/jspahrsummers/libextobjc/issues/new

In the carthage checkout folder, the schemes do exist in the xcschemes folder.  I suspect this is a bug in carthage but filing here as well in case there is a workaround such as maybe simplifying the scheme names.

The error message is correct, but it's By Design™. libextobjc is not meant to be used as a monolithic framework. Please see the instructions in the README.


containsString: unrecognized selector sent to iOS 7

Hi!
In class RLMQueryUtil used selector containsString that appeared in iOS 8, but in your docs Prerequisites: iOS >= 7. Do you still support/test iOS 7?
Thank you!

Thank you reporting it. We fixed this at https://github.com/realm/realm-cocoa/pull/1896.


Doesn't get right week number for beginning of the year

Hello!
currentWeekNumber('01/01/2021') should return 1 as first week of 2021 but returns 53

Hello!
currentWeekNumber('01/01/2021') should return 1 as first week of 2021 but returns 53

@theopract The current week number is the ISOWeek according to ISO-8601. 01/01/2021 is in fact week 53 of 2020 since the first isoweek of the year starts on a Monday.
https://www.epochconverter.com/weeks/2021

Hello!
currentWeekNumber('01/01/2021') should return 1 as first week of 2021 but returns 53

@theopract The current week number is the ISOWeek according to ISO-8601. 01/01/2021 is in fact week 53 of 2020 since the first isoweek of the year starts on a Monday.
https://www.epochconverter.com/weeks/2021

Hi @Svennisen ,
thanks for reply, I had no idea of such details.


remove out of date fields from DNS Policy API

@philbrookes you need to regen the bundle also we will want to ensure docs call out the removal of these fields as this is a breaking change from the previous release 0.6.x

@philbrookes you need to regen the bundle also we will want to ensure docs call out the removal of these fields as this is a breaking change from the previous release 0.6.x

yes, I'm working on a docs update already in a separate branch. AFAIK I have regenerated the bundle, is something missing?


Defaultregisterer panic

This code panics when trying to test the pkg/runner. Because logrusctx uses DefaultRegisterer across instances, maybe.
@xaionaro

I see. Let's fix it, I'll stamp the fix :)


[Bug] Using image scrolling will increase the memory footprint constantly

Describe the Bug
Repeated use of the image switching function, memory continues to increase

Using the test link [https://www.cornerstonejs.org/live-examples/webloader](url)
Steps to Reproduce
as above
The current behavior
as above
The expected behavior
as above
OS
win10
Node version
16
Browser
chrome 110

We cache images, so that you don't network request when going back.

We cache images, so that you don't network request when going back.
I know that the image will be cached, the above example has already cached the image, the memory of the image after caching will not be larger than 100M, if the scrolling operation above is continued, the memory will be stacked indefinitely, more than 2G, when scrolling the image, is it repeated to load the image that did not get the cached image? You can test based on the above example, thanks.

I don't see the reported issue anymore in Cornerstone3D 2.0


C# client dead lock during server streaming call

What version of gRPC and what language are you using?
C# Grpc 2.26.0
What operating system (Linux, Windows,...) and version?
Windows Server 2019 / Windows 10
What runtime / compiler are you using (e.g. python version or version of gcc)
.NET Core 3.1 / .NET Framework 4.8
What did you do?
We use ASP.NET Core 3.1 with Grpc.AspNetCore 2.25.0 server and calls with server streaming from .NET Core 3.1 / .NET Framework 4.8 clients using Grpc 2.26.0.
When a client enumerates server stream with IAsyncStreamReader.MoveNext() it deadlocks after some (hard to tell) time.
What did you expect to see?
To move to the next message or respect given CancellationToken
What did you see instead?
Deadlock
When debugged in Visual Studio:

Anything else we should know about your project / environment?
Our scenario: We began to see these deadlocks in clients during server stream enumerations as described above and because these calls are kept on server to notify clients for long time (as long as possible during client runtime) we thought it is some keep alive issue, but server continued to send messages to clients without problems, but clients did not receive anything after some time. Anyway we have added gRPC channel options for keep alive on clients and veryfied the Kestrel server replied to HTTP2 pings well, but the issue was not solved. So we have decided to dispose old call already being enumerated and recall new one at the same server endpoint after some configurable time to avoid the problem, but the issue remains unsolved.

#21633 mentions similar behaviour.

@rolfik  can you provide a reproduction (ideally as a project in a git repo)? Without it the description of the problem is way too vague to be actionable.
Also please describe what exactly you mean by "deadlock" in this case.

@jtattermusch I have no simple reproduction now, but only complex applications.
By "deadlock" I mean what I have already written:
ASP.NET server keeps long time client (C wrapped with .NET) calls for streaming notifications to them.
It may send some notifications and wait longer time and send next ones. But even when server sends notifications after longer pause (hours) to client stream with success, the client still awaits MoveNext call while enumerating notification stream and does not receive the notification.
Another thing I have found is that when a CancellationToken passed to MoveNext is cancelled and MoveNext still awaits next message, the token is ignored and nothing is cancelled.
We have solved this in production now with custom MoveNext method which awaits two tasks and ends immediatelly after the cancellation is requested while still letting the original MoveNext in progress. This allows us to cancel MoveNext call after specified timeout, dispose it and call server again to begin new notification stream enumeration.
        /// <summary>
        /// Moves to next message
        /// </summary>
        /// <remarks>
        /// <paramref name="cancellation"/> is not honored between waiting for next call in <see cref="IAsyncStreamReader{T}.MoveNext"/>, so this method solves it with extra cancellation task respecting <paramref name="cancellation"/> and <see cref="Task.WhenAny"/>, but when <paramref name="cancellation"/> is cancelled between messages, <see cref="IAsyncStreamReader{T}.MoveNext"/> is still in progress which can be stopped by disposing its call.
        /// </remarks>
        /// <typeparam name="T">Message type</typeparam>
        /// <param name="stream">Stream</param>
        /// <param name="cancellation">Cancellation</param>
        /// <returns>Whether there is any next message</returns>
        public static async Task<bool> MoveNextWith<T>(this IAsyncStreamReader<T> stream, CancellationToken cancellation)
        {
            Validate(stream);
            bool next;
            if (cancellation.CanBeCanceled)
            {
                var cancellationTaskSource = new TaskCompletionSource<bool>();
                using var cancellationRegistration = cancellation.Register(
                    ct => ((TaskCompletionSource<bool>)ct).SetCanceled(),
                    cancellationTaskSource
                    );
                var moveNextTask = stream.MoveNext(cancellation);
                var task = await Task.WhenAny(moveNextTask, cancellationTaskSource.Task);
                if (task == cancellationTaskSource.Task)
                    throw new OperationCanceledException(cancellation);
                next = task.Result;
            }
            else
                next = await stream.MoveNext(cancellation);
            return next;
        }

Any news?

Ok, looks like your are actually using grpc-dotnet (not Grpc.Core) - I haven't noticed that before.
@JamesNK  can you please take a look?

There shouldn't be any issue with a Grpc.Core client calling Grpc.AspNetCore server. There are cases where you'd want to mix the two. For example, if you're in Kubernetes then you might want Grpc.Core's client side load balancing to talk to Grpc.AspNetCore servers.

@tonydnewell  can you please take a look and suggest the best next steps here?

@rolfik is this still an issue? I know you have a workaround but are you still able to reproduce the original problem? Are you able to provide a reproduction (ideally as a project in a git repo)? Or could you provide some diagnostic logging - see https://github.com/grpc/grpc/blob/master/TROUBLESHOOTING.md ?


Document locking gotcha's on Linux

From #23 people need to know that Linux doesn't have mandatory locking, validate that and get to know what workarounds portalocker helps in this situation.

I've added it to the readme :)


Adding Backtracking folder

I want to create a new folder which includes all Backtracking problems with codes.
Please assign this to me , I am interested to contribute my self in hacktoberfest_23 : )

You can add them under the Miscellaneous folder. We need templates for important algorithms, not solutions to specific problems.


add new section to Service Registry getting started on assigning role to service account

@wtrocki @EricWittmann @carlesarnal This PR makes it clear that you must assign a role to a service account for client applications. Please review for technical accuracy and let me know if you approve or have any more updates. Thanks.

Done another pass and verified it end to end.
I think we can merge that.

We should still have QA after all is published to the docs

Thanks @wtrocki  I've pinged QE on the appropriate Jira and copied you.


Simplify Local Frontend Development Workflow

This PR is intended to provide updates to simplify frontend development in jhub-apps. The current workflow involves developing initially through the standalone React App, then running a build and copy script, then starting JupyterHub to validate changes.
This change updates the build process and adds a watch script to allow the developer to run both JupyterHub and the watch script. Then as changes are made to the frontend (react app), the watch will cause a new build and copy of assets. From there, the developer needs only to perform a browser refresh from the JupyterHub app.
This PR also includes a husky pre-push hook to ensure a fresh build is always completed prior to a push.
Note: the developer can still work in the standalone React app.
Reference Issues or PRs
N/A
What does this implement/fix?
Put a x in the boxes that apply

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds a feature)
[ ] Breaking change (fix or feature that would cause existing features not to work as expected)
[ ] Documentation Update
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no API changes)
[ ] Build related changes
[x] Other (please describe):

Testing

[x] Did you test the pull request locally?
[ ] Did you add new tests?

Any other comments?

Adds an npm watch script and custom vite build script to handle rebuild and copy
Adds husky pre-push script to ensure react app is built before push
Updates intended to simplify and streamline the local frontend development process

Allows the developer to see React-based changes in JupyterHub without having to manually run scripts and restart JupyterHub

Then as changes are made to the frontend (react app), the watch will cause a new build and copy of assets. From there, the developer needs only to perform a browser refresh from the JupyterHub app.

Do you mean changes will visible in the "jupyterhub" as well?
I didn't change for me in the JupyterHub:
Frontend: http://localhost:8080/hub

JupyterHub http://<IP_ADDRESS>:8000/hub/home

Then as changes are made to the frontend (react app), the watch will cause a new build and copy of assets. From there, the developer needs only to perform a browser refresh from the JupyterHub app.

Do you mean changes will visible in the "jupyterhub" as well?
I didn't change for me in the JupyterHub:
Frontend: http://localhost:8080/hub

## JupyterHub http://<IP_ADDRESS>:8000/hub/home

I’m guessing you actually started the frontend. With this new setup you perform an ‘npm run watch’ on the ui and start Jupyterhub in another tab. Then as changes are made you’ll see them in Jupyterhub (after a refresh). No meed to have the ui actually running in dev mode with this setup…that said you can still run the ui separately if you just want to work in that environment.

Ah, I ran npm run watch now and got what I expected. This is excellent work. Can you add a line in the docs about it?


Belt bag isn't positioned well for dog players

When pocketed, the position is the same as with humans, and when equipped, there's an offset to it's position which looks a little odd.

Fixed in v1.1.3


README does not mention need for GIT-LFS

Seems I made quite a big oversight when I put the readme together and forgot to mention that git-lfs is required to pull the php executable bundled here, leading to some confusion for users not used to using lfs.

Requesting LFS as a feature in serverless itself: https://github.com/serverless/serverless/issues/4611


Drawer widget bug!?

I use FlutterView in my app, and it has a drawer widget. I use the method:
public void onBackPressed() {
if(flutterView != null) {
flutterView.popRoute();
}
}
When I touch 'back' button, the drawer close, but it cannot  open again.

It's correct that the drawer closes when the back button is pressed.  Why you say "it cannot open again", can you explain a bit more about what you mean?  What sequence of things do you do and what do you observe?

"It's correct that the drawer closes when the back button is pressed", yes it does. But after it closed, I pressed the left-top icon(and right slide gesture not work too) the drawer cannot open.

I think it should add a "onBackPressed" callback(like android), it could be more easy to controll the behaviour(not just pop a route).Because many android app, when touch "back" button, just make a toast tips: "touch again you will exist the app".

Do you get any exceptions in the logs if you do this in debug mode?

no exceptions in the logs


Task should do nothing if input file doesn't exist

We apply jacoco plugin to every Gradle project. However, some projects don't have tests. Could you please add @org.gradle.api.tasks.Optional annotation to the getter JacocoToCoberturaTask.inputFile so that JacocoToCoberturaTask is skipped if the input file doesn't exist.

Unfortuntally doesn't seem to work @Optional on inputFiles.
I did it in the last releasea hoping it will fix it but realized it does non ;(
There's an old opened issue about it...
https://github.com/gradle/gradle/issues/2016

I agree with what is said in the discussion in #20 issue, it should be InputFile but I agree should be possible to set it as @Optional, so build won't fail because of that, but Gradle doesn't seem to agree so far.
So I'll keep it this way, because there's a workaround. I'll update the readme to specify it, by using onlyIf in the task definition:
For exemple:
tasks.jacocoToCobertura {
	dependsOn(tasks.koverXmlReport)
	val jacocoReport = project.layout.buildDirectory.file("reports/kover/report_that_does_not_exist.xml")
	onlyIf {
		jacocoReport.get().asFile.exists()
	}
	inputFile.set(jacocoReport)
	outputFile.set(project.layout.buildDirectory.file("reports/kover/cobertura.xml"))
}

Using this configuration jacocoToCopertura task won't run if the the file does not exist.
I think it's a easy workaournd that fixed the issue.


Application for Daksh

Application

@Daksh14 do you want me to look into this?

Sure

@Daksh14 I will revert in 2-3 days. Apologies that I missed the PR earlier.

Are there any updates on this? @niksmac


ABGR8888 causes DisplayLink reconnection loop on Wayland sessions

Freeze Issue with DisplayLink Monitors on Wayland with ARGB8888 Based Compositors
Summary
A significant issue has been identified affecting users of the Plasma 6 environment when connecting monitors through a Lenovo dud9011d1 docking station via DisplayLink to a Lenovo ThinkBook 14 G3 laptop. The core of the problem lies in the freezing of kwin_wayland when the compositor uses ARGB8888 pixel format. This freezing manifests shortly after the monitors are connected, either becoming static or entering a loop of continuous reinitialization.

Laptop Model: Lenovo ThinkBook 14 G3, AMD GPU
Docking Station: Lenovo dud9011d1, connected over USB-C with DisplayLink protocol
Monitors: Two 1920x1080, 75hz, Scaling 100%
Kernel Drivers on X11: evdi (version 1.14.2) and displaylink

Steps to Reproduce

Initiate a Plasma Wayland session (applicable to both Plasma 5 and 6).
Connect monitors using the Lenovo dud9011d1 docking station.
Attach the docking station to the laptop via DisplayLink.

Observed Behavior

Monitors may momentarily function (1-2 seconds) before the display freezes.
While the laptop's main screen remains responsive, the session is prone to frequent freezes, or the external monitors may repeatedly reinitialize.

System Information

Kernel Versions Tested: 6.7.6 and 6.1.59
Operating System: ArchLinux (as of 27.02.2024)
KDE Plasma Version: 5.27.8, with the issue persisting into Plasma 6.
KDE Frameworks Version: 5.110.0
Qt Version: 5.15.11

Resolution
The issue was effectively mitigated by switching the pixel format from ARGB8888 to XRGB8888, utilizing the KWIN_DRM_NO_AMS=1 environment variable. This adjustment resulted in the stable operation of all connected displays without the prior freezing or reinitialization issues.
Additional Context
Through extensive discussions and diagnostics tracked in the KDE bug report (#475922), the problem is suggested to stem from a driver-level inconsistency specifically related to the handling of the ARGB8888 pixel format by the DisplayLink technology. Switching to the XRGB8888 format, which Xorg usually uses by default, has been a solid quick fix for Plasma 6.

More details available at the KDE Issue Tracker -> https://bugs.kde.org/show_bug.cgi?id=475922

I have the same issue on my TUXEDO Aura 15 Gen1 Notebook:
CPU: AMD Ryzen 7 4700U
Graphic: AMD Radeon™ RX Vega Graphics
Docking station:
i-tec USB 3.0 / USB-C / Thunderbolt 3, 3x 4K Docking Station + Power Delivery 85W (CATRIPLE4KDOCKPD):
OS: KDE neon 6.0 (based on Ubuntu 22.04)
Kernel: Linux version 6.5.0-10022-tuxedo

You can fix that temporary for Plasma by setting KWIN_DRM_NO_AMS=1 env Variable
This will enforce XRGB8888 pixel formatting.

Also affected, workaround works:
# grep -s . /sys/devices/evdi/*
/sys/devices/evdi/count:2
/sys/devices/evdi/loglevel:4
/sys/devices/evdi/version:1.14.2

HP USB-C/A Universal Dock G2, model L61608-001
HP ProBook 455 G10, model 854L2ES#ABD, has a Ryzen 7 7730U Barceló-R family CPU and an integrated Vega CPU with Graphics Core Next (GCN) 5 instruction set

@YourSandwich Thank you! Your suggested workaround works for me :-)

Sorry to trouble  but I do not understand the effect of KWIN_DRM_NO_AMS=1
Will it affect any other things in the computer?

Right now it reduces the maximum bits per color on all displays to 8, and may increase latency a tiny bit. As a temporary workaround it's fine to use

Greeting, does Plasma 6.0.3 solve the problem?

No

Hello
Looks like that the latest released evdi=1.14.4-80 (released on 11.04.2024) is fixing this problem.
Could you please try to upgrade evdi and recheck if it is fixing this problem on your side as well?

Closing. Please reopen or create new issue if the problem reappears


Fix host ip

improve the logic for obtaining IP based on the hostname.

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


Major Style & Updates

Alright, this is a pretty big push...

Removed bloat files from starter code.
Redesigned the Navbar for Users not logged in.
Scrapped and Rebuilt the Signed In user Side Bar and Nav Bar complete with Initial styling. (There are some conflicting CSS styles, that I still need to clean up, but unless you know where to look for them, everything appears to work )
Added MBD Library for more flexibility on styling and Side/Nav bar.
Started Building out Multi Route folder, but not 100% sure It will be needed. I think with the New side/nav bars we should be able to just build pages then use the components in those pages.
Updated default profile page with correct model keys. (Changed "username" to "name") .
Imported Fontawesome Library just incase it easier to use those icons.
Started building out Layouts, but after some testing, it looks like they might be moot at this point, but if we need to go down the route the framework is there.
Create Logo for Dashboard

Items that need attention :

On the Sidebar Top Nav, the Account Dropdown link to profile doesnt work. Need to look at it.
Some Styling issues here and there.

DO NOT MERGE THIS... FOUND SOME MAJOR ISSUES.


Documentation: No example is provided for using disabledModules with an attribute set

Problem
The documentation on disabledModules describes three different ways to interact with disabledModules. However, no example is provided for the last method: using an attribute set.
This is specifically problematic because the documentation mentions a feature exclusive to this method ("The latter allows some modules to be disabled, despite them being distributed via attributes instead of file paths. The key should be globally unique, so it is recommended to include a file path in it, or rely on a framework to do it for you.").

Proposal
An example would be provided for how to use this. I would write the example myself, but I still don't understand how exactly it would look. If anyone is more knowledgeable on how using an attribute set within disabledModules works, I'd appreciate you letting me know, so I can make a PR myself.
Checklist

[x] checked latest Nixpkgs manual (source) and latest NixOS manual (source)
[x] checked open documentation issues for possible duplicates
[x] checked open documentation pull requests for possible solutions

Add a :+1: reaction to issues you find important.

Found a relevant PR with some additional info that clears things up a lot. I think the documentation could ideally be clarified a bit, since this conversation was much clearer than the documentation in my opinion.


[Typo] "reccomendations" should be spelled "recommendations"

In the documentation for Windows Spotlight: https://docs.microsoft.com/en-us/windows/configuration/windows-spotlight, there's a small typo:
The word "reccomendations" should be spelled "recommendations".
Steps to reproduce
Go to the website via the link above and Ctrl-F to search for "reccomendations". Notice the typo.

This is resolved Thanks! @gewarren #please-close


is it possible to share .env variables on repo level?

as we are using the same variables in different packages/sites, we could move the env vars to the root level if its possible.

I think this is not too important at the moment. Added the wontfix label, if we have time we can work on this later.


[FLINK-13429][table-common] Fix BoundedOutOfOrderTimestamps watermark strategy

What is the purpose of the change
Fixes a bug that was introduced with FLINK-13315 in de1a8a0444c231df6c57a70cefb689aa7126a502 while porting watermark strategies to Java. This ensures the old behavior and is also in sync with the DataStream API timestamp extractor.
Brief change log
BoundedOutOfOrderTimestamps updated.
Verifying this change
This change is already covered by existing tests, such as SQL Client e2e test.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changed class annotated with @Public(Evolving): yes
The serializers: no
The runtime per-record code paths (performance sensitive): no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: no
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature? no
If yes, how is the feature documented? not applicable

LGTM, I run the test_sql_client.sh locally and it also passes.

Thanks @dawidwys. Merging...


prevent push-docker-images from overwriting existing manifest

Issue #, if available:

During v1.3.0 release the docker manifest was overwritten with Windows image only which caused subsequent helm testing to fail due to Linux images not being available.

Description of changes:

enable experimental Docker CLI features before running manifest inspect to check if manifest exists already. Otherwise, manifest will be overwritten and the following error: docker manifest inspect is only supported on a Docker cli with experimental cli features enabled

related log from v1.3.0 release: https://travis-ci.org/github/aws/amazon-ec2-metadata-mock/jobs/716661941

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Once merged, I'll kick off another AEMM release. If this is the confirmed fix, then I can open a PR against NTH for the same


Add support for virtual hosting

Description
This PR adds rudimentary support for virtual hosting. Users can specify a hostname and an alternate root dir, and SWS will serve files from that alternate root dir if the "Host" header matches. All other settings are the same between virtual hosts (seems it would exponentially complicate the code otherwise).
I apologize for any non-idiomatic Rust, I'm learning!
Related Issue
#171
Motivation and Context
In places like NixOS, it's generally not possible to run more than one instance of a NixOS module on a single computer. Also resource-constrained environments (like my home router) can run SWS, but not two whole instances of SWS.
How Has This Been Tested?
make build
./target/x86_64-unknown-linux-musl/release/static-web-server --config-file tests/toml/newconf.toml --log-level debug

curl localhost:80
# Returns ./docker/public/index.html

curl -H "Host: example.com" localhost:80
# Returns a directory listing of ./docker

I do wish I could make a unit test for this. Seems it's difficult to test any code implemented outside of static_files::handle, which is where the other advanced features take effect. I'm also a fan of integration tests, apparently people recommend assert_cmd for that.
Screenshots (if appropriate):

At first glance, the PR looks fine. I definitely will give it a more detailed review as soon as I get some time today.

I do wish I could make a unit test for this. Seems it's difficult to test any code implemented outside of static_files::handle, which is where the other advanced features take effect. I'm also a fan of integration tests, apparently people recommend assert_cmd for that.

Sounds fine. In fact, it would be great to have integration tests

fo

Thanks 👍


Auto-create relevant directories

Noticed that lapdToRaw does not auto create the RAW directory to save the HDF5 file.  Suggest in general all directories for hd5 processing be auto-created if necessary.

This should definitely be done: I'll add it to the list.

Added this functionality to the lapd.py, tdiode.py, and bdot.py processes via the newly added hdf.requireDirs() function.


Cache.get() cancels coroutine when exception thrown

Expecting cache.get(key) { ... load value here ... } to propagate exceptions to the caller, as documented:

If the suspendable computation throws, the exception will be propagated to the caller.

What happens instead is the coroutine is cancelled and a JobCancellationException is thrown.
try {
    val cache = cacheBuilder<String, String>().build()

    cache.get("key") { throw IllegalArgumentException("Whoops") }
} catch (t: Throwable) {
    // this is a JobCancellationException; expected to be the thrown IllegalArgumentException
    println(t)
}

Exception: kotlinx.coroutines.JobCancellationException: TimeoutCoroutine is cancelling; job=TimeoutCoroutine(timeMillis=45000){Cancelling}@609ac453 (this is inside a kotest test)

Looking through the tests - they aren't up-to-date wrt cacheBuilder (most use caffeineBuilder) - the test for exception propagation works for caffeineBuilder but fails when changed to cacheBuilder
                // from unit test: https://github.com/sksamuel/aedile/blob/8d3ea128b474062dae9ad6b925f3f0c5d748a75d/aedile-core/src/test/kotlin/com/sksamuel/aedile/core/CacheTest.kt#L42
                // exception propagation works
                val cache = caffeineBuilder<String, String>().build()
                shouldThrow<IllegalStateException> {
                    cache.get("foo") {
                        error("kapow")
                    }
                }

                // using cacheBuilder instead
                // exception propagation fails - coroutine is cancelled
                val cache2 = cacheBuilder<String, String>().build()
                shouldThrow<IllegalStateException> {
                    cache2.get("foo") {
                        error("kapow")
                    }
                }

Setting useCallingContext to false in the configuration block will cause the correct exception to be thrown - this is fine for our usecase but may not be useful in others.
private val urlCache = cacheBuilder<CacheKey, URL> {
    useCallingContext = false
    dispatcher = Dispatchers.Default
}.build()

Can you try the latest snapshot from https://s01.oss.sonatype.org/content/repositories/snapshots/com/sksamuel/aedile/aedile-core/
And update to use Caffeine.newBuilder directly, add in your config, then call .asCache or .asLoadingCache.
No other changes needed.
If you're happy with that, I will release 2.0.0. final.

Actually I threw out at 2.0.0.RC1 stable release to make it easier to test with.


proxy-service: Add class shorthand

For a class, you should just be able to pass it into defineProxyService without a name or constructor.
import { defineProxyService } from '@webext-core/proxy-service';

class DatabaseService {
  construtor(db) { ... }
}

const [registerDatabaseService, getDatabaseService] = defineProxyService(DatabaseService);

registerDatabaseService(db);
const service = getDatabaseService();

In this case, it should use the class name for the message, and the constructor when registering it.

I would love to help out!

@tlarkin011 that'd be great, thanks! I'm not a big fan of classes in JS, so this is super low priority for me 😂 That's why I added the "good first issue" and "help wanted" labels lol.
I just created docs to help contributors get started. Let me know if you run into any issues or it doesn't make sense.
https://webext-core.aklinker1.io/guide/contributing.html
Otherwise I'll let you handle it! Thanks again 😄

@aklinker1 Thank you! The docs are great, I will reach out if I have any questions!

@aklinker1 Hello, I may need some help with the specific class updates.  Thank you!

@tlarkin011 Are you familiar with function overloading in TypeScript?
All we need to do is add a new override for defineProxyService that accepts a single argument, and class.
We'll need to replace this:
https://github.com/aklinker1/webext-core/blob/ade768187966a7aaf6eaf9adb7942bc2274006e6/packages/proxy-service/src/defineProxyService.ts#L6-L11
With something like this:
+export function defineProxyService<TService extends Service, TArgs extends any[]>(
+  classDefinition: { new (...arg: TArgs): TService },
+  config?: ProxyServiceConfig,
+): [registerService: RegisterService<TService, TArgs>, getService: GetService<TService>];
+
export function defineProxyService<TService extends Service, TArgs extends any[]>(
  name: string,
  init: (...args: TArgs) => TService,
  config?: ProxyServiceConfig,
-): [registerService: RegisterService<TService, TArgs>, getService: GetService<TService>] {
+): [registerService: RegisterService<TService, TArgs>, getService: GetService<TService>];
+
+export function defineProxyService<TService extends Service, TArgs extends any[]>(
+  arg1: any,
+  arg2: any,
+  arg3?: any,
+): [registerService: RegisterService<TService, TArgs>, getService: GetService<TService>] {
+  // Based on the overrides, create variables for all the old args
+  const isClassOverride = typeof arg1 !== "string";
+  let name: string = isClassOverride ? arg1.name : arg1;
+  let init: (...args: TArgs) => TService  = isClassOverride ? (...args: TArgs) => new arg1(...args) : arg2;
+  let config: ProxyServiceConfig | undefined = isClassOverride ? arg2 : arg3;
+
  let service: TService | undefined;
  ...

@aklinker1 I am familiar with them now.  great learning experience! thank you for your help!

No problem, let me know if you have any other questions!

I started on this today, and after some testing, have decided to NOT support a class shorthand.
When an extension is minified, it's name is not unique, and can cause problems.


Instead of Centos 6 dowloading Centos 7

If i try to get-source centos:6.9 or any other centos 6 its download centos:latest  - but i really need any version of Centos 6

#78 Fix worked for me.


Update routes.py for READ-and-LIST API

update READ and LIST API

Coverage is now 94%

Looks all good.


Issues with search field in SvelteKit documentation (on iOS).

Describe the bug
Some minor annoyances with the SvelteKit documentation on iOS:

It is impossible to tap the 'x' on the right that clears the search input. Instead, the hamburger menu always "steals" the tap. Workaround is to select the text and delete. Or keep tapping keyboard backspace until text is gone.
Perhaps related to the issue above, the search field seems to be covered by the navigation header. As you can see in the screen shots below, the input cursor overlaps the Svelte logo.
In dark mode, you cannot see the text you entered. This seems to only happen on iOS in dark mode. (Also tried Windows 11 Chrome and Android Chrome.) Happens in both Safari and Chrome. In the image below, you can see I entered 'test' into the search field, but you cannot see the search input text, only the input cursor.

Normally the search input is visible in light mode, but when in auto dark mode and forcing light mode via the iOS control center, it still invisible. Perhaps in normal light mode, the search input was low enough to see the text and 'x':

Reproduction
Search documentation on https://kit.svelte.dev/
Logs
n/a

System Info
- iOS version 16.0.3
- iPhone SE (2020)

Severity
annoyance
Additional Information
No response

It is impossible to tap the 'x' on the right that clears the search input. Instead, the hamburger menu always "steals" the tap. Workaround is to select the text and delete. Or keep tapping keyboard backspace until text is gone.

This is the expected behaviour. The 'x' closes the modal in both mobile and desktop. Although, I can agree it's confusing since most search bars use it to clear the input rather than close. Maybe this should be changed?

Perhaps related to the issue above, the search field seems to be covered by the navigation header. As you can see in the screen shots below, the input cursor overlaps the Svelte logo.
In dark mode, you cannot see the text you entered. This seems to only happen on iOS in dark mode. (Also tried Windows 11 Chrome and Android Chrome.) Happens in both Safari and Chrome. In the image below, you can see I entered 'test' into the search field, but you cannot see the search input text, only the input cursor.

I was only able to reproduce this on my iPhone 7 but not in Safari. It seems that the z-index CSS property is not being handled correctly? The nav bar is taking precedence with z-index: 101 although the search box has z-index: 9999.


Pass route name to controller when initialised

https://github.com/UKHomeOffice/passports-form-wizard/blob/master/lib/wizard.js#L45
The name of the route isn't passed to the controller when looping through steps. This means if we want to access the route within the controller we have to use req.url and strip /edit if present.
I suggest we extend options to include the route by adding options.route = route before the controller is initialised

This makes sense to me.


Removed uneeded dependency on symfony/finder

We do never use it.

The use statement in the Updater class should be removed too.

:+1:

Merging...merging...no explosions...merging ;) Thanks!

@padraic Thanks a lot! :)

Thank you for merging! Could you tag 1.0.3?

I'll be tagging shortly @Nyholm


[improvement] - make fields prop accept undefined as well

Since the form might be in a loading state we should accept fields as Field[] or undefined.

Yes, it is right. I noted that maybe we can remove the child with fields:
<Form …>
   {({ fields }) => // could be remove

   }
</Form>


Fix double escaped &

Are there any values in any of the .po values that need to be updated since you are changing a "key"?

@Fryguy : We probably have to discuss that. We could do that in batches. Before some translation updates or maybe before a release? We could also do this automatically using some bot. Or we should do it in each commit that changes a "key"?
@jzigmund : what do you think?

I'm just wondering about these specific strings...I'm not really concerned with any of the others.  Shouldn't any PR that changes a UI String also change the .po files and by extension, invalidate the ones that are completely wrong?
Incidentally, this is why I like the "normalized key" approach rather than the "English string is the key" approach.  :trollface:

I would be curious what Foreman does, since we followed their lead.  I do know that they have code in to actually show strings in the UI with XX prefix and suffix markers when a string is missing in the translation files, so that seems to tell me that they don't automatically update the .po files.
Regardless, I am merging this.

This makes no sense to change the key in one place, but not the other.  Why wouldn't this PR update the dictionary (.po) files?

@chessbyte : I do not object against doing it that way. Exactly, why not. I hope we will run the first round of translations soon and fill in the gaps in the process.

@chessbyte we should probably come up with a process for those updates.  There is a rake task to run and we have a first cut of a document that is being used to get a first round of translations done.  The idea behind the rake task is that each person that adds/changes a string doesn't have to worry about changing the .po files and they can be done in bulk at whatever points in the process we decide as it will identify all needed translations.


Tidy up build info using unwrap

With Rust 1.83, we can use Option::unwrap in a const context and remove the untidy hack we had to resort to in order to get the commit hash.
Does this change impact existing behavior?
No.
Does this change need a changelog entry?
No.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license and I agree to the terms of the Developer Certificate of Origin (DCO).

Ha. We cannot in fact use this:
error[E0080]: evaluation of constant value failed
  --> mountpoint-s3/src/build_info.rs:31:35
   |
31 |     const COMMIT_HASH_STR: &str = built::GIT_COMMIT_HASH_SHORT.unwrap();
   |                                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ the evaluated program panicked at 'called `Option::unwrap()` on a `None` value', mountpoint-s3/src/build_info.rs:31:64

Let's keep the original hack.


vrf: Merge table ID from current

When desire state does not contain table ID for existing VRF interface,
we merge it from current.
In code:

expand pre_edit_cleanup() to accept current: Option<&Interface>.
expand pre_verify_cleanup() to accept
pre_apply_current: Option<&Interface>

Integration test case included.

Really small nit, thank you!


included cuModuleGetGlobal_v2

There's a lot of other changes here that I'm hesitant to include. Including cuModuleGetGlobal is fine, but the other changes are breaking. If they are necessary for cuModuleGetGlobal, please include details about why.

it's just a personal project requirement for me. I will close this PR. Thank you for your work.


Improve issue template

Since we already have discussions, and I've noticed that many people are opening bugs without filling the template, or haven't read the documentation, I've decided to add more strict templates.
So far, there are only two

bug reports
feature requests

Each one has fields that are required to open an issue.
If people want to talk about random stuff, or ask for help, maybe discussions is a better place for that.
Open to suggestions/improvements.
As always, feel free to close if you don't like this :)

Yeah cool. Let's try it out.
The main thing I really want to avoid is people basically writing "can you write my code for me?" posts. A particularly common version of that is "I'm incidentally using dlib and my program isn't working.  Can you debug it for me?".  99.9% of the time I get questions like that it's just that someone has a bug in their code that's unrelated to anything in dlib.  In most cases the act of turning their broken program into some small reproduction of the issue causes them to discover the bug.  Which is no surprise since one of the important steps of debugging is narrowing down the scope of the problem :)

Let's see if forcing people to fill the template properly improves this situation.
Maybe we'll have to tune it, since both templates now add labels to the issues, which will prevent the bot from closing them…

Ha, yeah.  I thought about that.  The bot is just there so it's not me personally closing issues :)

The main thing I really want to avoid is people basically writing "can you write my code for me?"

We already have ChatGPT for that, haha.


match without opening namespace

The following code gives a funny error. The problem is that I didn't open bool.
variables {P : bool → Type} {x : P bool.tt} {y : P bool.ff}

example (b : bool) : P b :=
match b with
| tt := x
| ff := y
end

Interestingly, for non-dependent functions I don't need to open bool:
variables {P : Type} {x y : P}

example (b : bool) : P :=
match b with
| tt := x
| ff := y
end

Can you let Lean accept the first example? Otherwise, can you improve the error message?

I just realized that my original example is not solved by just opening the namespace bool. My full example is
structure diagram [class] :=
  (Iob : Type)
  (Ihom : Type)
  (ob : Iob → Type)
  (dom cod : Ihom → Iob)
  (hom : Π⦃j : Ihom⦄, ob (dom j) → ob (cod j))

inductive pushout_ob :=
| tl : pushout_ob
| tr : pushout_ob
| bl : pushout_ob

open pushout_ob bool

universe variable u
variables {TL TR BL : Type.{u}} {f : TL → TR} {g : TL → BL}

definition pushout_diag : diagram :=
diagram.mk pushout_ob
           bool
           (λi, match i with | tl := TL | tr := TR | bl := BL end)
           (λj, match j with | tt := tl | ff := tl end)
           (λj, match j with | tt := tr | ff := bl end)
           (λj, match j with | tt := f  | ff := g  end) --error

--the following definition is included purely to show that my above definition should work
definition pushout_diag' : diagram :=
diagram.mk pushout_ob
           bool
           (λi, pushout_ob.rec_on i TL TR BL)
           (λj, bool.rec_on j tl tl)
           (λj, bool.rec_on j bl tr)
           (λj, bool.rec_on j g  f)

@fpvandoorn The whole thing is tricky.
First some remarks.

The definition package and match expressions are a little bit problematic because they add new variables to the context. We are simultaneously declaring variables and patterns.

If an identifier is not a constant/parameter/hypothesis/axiom/alias, then lean assume we are adding/declaring a new variable.

The first example fails because Lean is assuming tt is a variable.
It is interpreting the example as
example (b : bool) : P b :=
match b with
| z := x
| z := y
end

It has two overlapping equations.
The second example (the non dependent one) doesn't really work. It is not defining the term you expect. It is really treating tt and ff as variables. It works because there is no dependency.
Your real example is quite trick to process without auxiliary annotations.
It works when you use bool.rec_on because all unification constraints are being solved  simultaneously.  Each match expression term is compiled independently of each other.
So, one trick is to provide the expected type for the last match-expression.
definition pushout_diag : diagram :=
diagram.mk pushout_ob
           bool
           (λi, match i with | tl := TL | tr := TR | bl := BL end)
           (λj, match j with | tt := tl | ff := tl end)
           (λj, match j with | tt := tr | ff := bl end)
           (λj, show pushout_ob.cases_on (bool.cases_on j tl tl) TL TR BL → pushout_ob.cases_on (bool.cases_on j bl tr) TL TR BL,
                from match j with | tt := f | ff := g end)

Opening namespaces automatically is not that simple. We may have to open several of them. For example, suppose we are pattern matching on list (nat x bool x nat). The patterns may have constructors of four different datatypes.

Hmm... I see, that is indeed tricky. I think the lesson is to only use match when the corresponding namespaces are open.
However, this does sometimes lead to unintuitive behavior, as in the examples of my first post. Is it possible to enhance the error message from my first example and add some information (or is this the generic type-mismatch error message)? Maybe if the free variables written by the user are in the error message this could help. For the first example this would be something like
type mismatch at definition 'match', has type
  P bool.ff
but is expected to have type
  P bool.tt
(The following identifiers are treated as free variables
  in the match expression: tt, ff)

For the example in my second post, it seems that a tactic proof is most convenient for this definition, where I can use cases. Then the type of the last argument is already elaborated when it is needed.
I can see that the definition in my example is hard to elaborate, because I give very little type information. However, if I replace the last line by _, Lean can figure out exactly which type is needed there. It would be nice if there was some notation which we can use which means "initially treat this part of the term as an underscore, only when you have elaborated the rest of the term, start elaborating what's here". This is how I try to use proof ... qed, but this often doesn't lead to desired results (I don't know exactly why, but I guess it has to do with moving to the tactic framework). For example: adding proof...qed to the last line doesn't help:
definition pushout_diag {f : TL → TR} {g : TL → BL} : diagram :=
diagram.mk pushout_ob
           bool
           (λi, match i with | tl := TL | tr := TR | bl := BL end)
           (λj, match j with | tt := tl | ff := tl end)
           (λj, match j with | tt := tr | ff := bl end)
           (λj, proof match j with | tt := f  | ff := g end qed) /- error -/

Derailing the issue even more: begin refine (match j with | tt := _  | ff := _  end) end gives a failed to synthesize placeholder-error. If it's not hard, it would be nice to allow this.

Maybe if the free variables written by the user are in the error message this could help.

I agree.

This is how I try to use proof ... qed, but this often doesn't lead to desired results (I don't know exactly why, but I guess it has to do with moving to the tactic framework).

Note that proof T qed is an "one way road". That is, information inferred from T is not available for elaborating the term surrounding the proof ... qed.

Derailing the issue even more: begin refine (match j with | tt := _ | ff := _ end) end gives a failed to synthesize placeholder-error. If it's not hard, it would be nice to allow this.

I have to think about this one. Recall we do not have match-expressions in the language. They are all compiled into recursors. I know the feature you requested will not work in full generality. Example: recursive calls.
In Lean, we can have nested recursive definitions.
https://github.com/leanprover/lean/blob/master/library/data/list/perm.lean#L200-L202

For the record, I have also made the mistake of writing "succ n" in a function definition without opening nat, and from the error message I was confused about what it does not work. ("succ is not a constructor, ..."). It took me a while to figure out that succ was interpreted as a variable. So the better error message would have helped me.
I just met with Andrew, who is writing proofs in elementary set theory. We tried to clean them up to make them look natural to undergraduate students.  When we tried putting a subproof in a "proof ... qed" block, we had to replace every "have" we used by "assert" to make it visible (or use "using"). I don't remember having to do that in the past -- did it change?

I just met with Andrew, who is writing proofs in elementary set theory. We tried to clean them up to make them look natural to undergraduate students. When we tried putting a subproof in a "proof ... qed" block, we had to replace every "have" we used by "assert" to make it visible (or use "using"). I don't remember having to do that in the past -- did it change?

Recall that we changed how proof ... qed is compiled.
I described the change in the mailing list:
https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!msg/lean-discuss/vk291scwbfo/DsQQs1B_ficJ
Now proof t qed is compiled using by exact t. This is why we need an assert.
The modification was performed to simplify the elaboration procedure and make the control flow simpler to understand.

Note that proof T qed is an "one way road". That is, information inferred from T is not available for elaborating the term surrounding the proof ... qed.

Yes, but that shouldn't be a problem in my example. If I replace the proof ... qed by _, everything is elaborated correctly (except the value of _ of course). Is the term inside proof ... qed elaborated after its type is fully known? Because then I don't understand why your example (with show ... from ...) does work, but proof ... qed doesn't.

did it change?

Yes, see this mail.

Oh, good. I remember the e-mail now. I'll make sure the tutorial explains this.

Yes, but that shouldn't be a problem in my example. If I replace the proof ... qed by _, everything is elaborated correctly (except the value of _ of course).

The type inferred for _ is not the type I entered in the show. I did not invest time trying to understand the inferred type, but it looks different:
pushout_ob.cases_on
  (bool.cases_on j (λ (e_1 : j = ff), tl) (λ (e_1 : j = tt), tl) (eq.refl j))
  (λ (e_1 : bool.cases_on j (λ (e_1 : j = ff), tl) (λ (e_1 : j = tt), tl) (eq.refl j) = tl), TL)
  (λ (e_1 : bool.cases_on j (λ (e_1 : j = ff), tl) (λ (e_1 : j = tt), tl) (eq.refl j) = tr), TR)
  (λ (e_1 : bool.cases_on j (λ (e_1 : j = ff), tl) (λ (e_1 : j = tt), tl) (eq.refl j) = bl), BL)
  (eq.refl (bool.cases_on j (λ (e_1 : j = ff), tl) (λ (e_1 : j = tt), tl) (eq.refl j))) →
pushout_ob.cases_on (bool.cases_on j (λ (e_1 : j = ff), bl) (λ (e_1 : j = tt), tr) (eq.refl j))
  (λ (e_1 : bool.cases_on j (λ (e_1 : j = ff), bl) (λ (e_1 : j = tt), tr) (eq.refl j) = tl), TL)
  (λ (e_1 : bool.cases_on j (λ (e_1 : j = ff), bl) (λ (e_1 : j = tt), tr) (eq.refl j) = tr), TR)
  (λ (e_1 : bool.cases_on j (λ (e_1 : j = ff), bl) (λ (e_1 : j = tt), tr) (eq.refl j) = bl), BL)
  (eq.refl (bool.cases_on j (λ (e_1 : j = ff), bl) (λ (e_1 : j = tt), tr) (eq.refl j)))

Is the term inside proof ... qed elaborated after its type is fully known?

The tactics are invoked after the unification constraints have been solved.
The type may not yet be fully known. In this case, it is, but it doesn't mean it is the one we want.
Moreover, we will not backtrack and try another solution if the type is not the one we want.
That is, a tactic failure does not trigger backtracking in the unification constraint solver.
Could we try to backtrack? Yes, we could, but it would be too expensive and produce counter-intuitive behavior when we have several different tactic blocks.

Sorry, I still don't exactly understand what is going on.
First of all: I agree that it would be terrible to backtrack in the unification constraint solver when a tactic fails.
Where did you put the underscore to get the inferred type you posted? I can't reproduce something which looks like that.
If I write the following (this is the same code as before, except the last term replaced by _)
structure diagram [class] :=
  (Iob : Type)
  (Ihom : Type)
  (ob : Iob → Type)
  (dom cod : Ihom → Iob)
  (hom : Π⦃j : Ihom⦄, ob (dom j) → ob (cod j))

inductive pushout_ob :=
| tl : pushout_ob
| tr : pushout_ob
| bl : pushout_ob

open pushout_ob bool

universe variable u
variables {TL TR BL : Type.{u}} {f : TL → TR} {g : TL → BL}

definition pushout_diag : diagram :=
diagram.mk pushout_ob
           bool
           (λi, match i with | tl := TL | tr := TR | bl := BL end)
           (λj, match j with | tt := tl | ff := tl end)
           (λj, match j with | tt := tr | ff := bl end)
           (λj, _)

The inferred type of _ is
pushout_ob.cases_on (bool.cases_on j tl tl) TL TR BL →
  pushout_ob.cases_on (bool.cases_on j bl tr) TL TR BL

Let's call this type T. If I now replace the underscore by
show T, from
  match j with | tt := f  | ff := g end

the resulting term gets accepted:
definition pushout_diag : diagram :=
diagram.mk pushout_ob
           bool
           (λi, match i with | tl := TL | tr := TR | bl := BL end)
           (λj, match j with | tt := tl | ff := tl end)
           (λj, match j with | tt := tr | ff := bl end)
           (λj, show pushout_ob.cases_on (bool.cases_on j tl tl) TL TR BL →
                     pushout_ob.cases_on (bool.cases_on j bl tr) TL TR BL, from
                       match j with | tt := f  | ff := g end )

This is how I think about the elaboration when I write proof match j with | tt := f  | ff := g end qed. But apparently this intuition is wrong, since the latter is not accepted. To be more precise, the following is not accepted:
definition pushout_diag {f : TL → TR} {g : TL → BL} : diagram :=
diagram.mk pushout_ob
           bool
           (λi, match i with | tl := TL | tr := TR | bl := BL end)
           (λj, match j with | tt := tl | ff := tl end)
           (λj, match j with | tt := tr | ff := bl end)
           (λj, proof (match j with | tt := f  | ff := g end) qed)

Disturbingly: if I replace proof t qed by by exact t, the definition is accepted.
definition pushout_diag {f : TL → TR} {g : TL → BL} : diagram :=
diagram.mk pushout_ob
           bool
           (λi, match i with | tl := TL | tr := TR | bl := BL end)
           (λj, match j with | tt := tl | ff := tl end)
           (λj, match j with | tt := tr | ff := bl end)
           (λj, by exact (match j with | tt := f  | ff := g end))

But proof t qed is supposed to be syntax sugar for by exact t, right? Is that a bug?

Where did you put the underscore to get the inferred type you posted? I can't reproduce something which looks like that.

I put in the same place you inserted it.

the resulting term gets accepted:

definition pushout_diag : diagram :=
diagram.mk pushout_ob
           bool
           (λi, match i with | tl := TL | tr := TR | bl := BL end)
           (λj, match j with | tt := tl | ff := tl end)
           (λj, match j with | tt := tr | ff := bl end)
           (λj, show pushout_ob.cases_on (bool.cases_on j tl tl) TL TR BL →
                     pushout_ob.cases_on (bool.cases_on j bl tr) TL TR BL, from
                       match j with | tt := f  | ff := g end )

Same for me.

But proof t qed is supposed to be syntax sugar for by exact t, right? Is that a bug?

A fixed a problem today with proof ... qed. https://github.com/leanprover/lean/commit/107763a506772d9fcc294fb536d24d5fce02dbab
It was being mapped to by rexact t.

I'm still exploring alternatives for this one.

It is not trivial to add the extra information to the error messages. The errors are produced when constraints cannot be solved. The constraints are created in many different places (e.g., in the type checker). Most of these places are not even aware of the existence of match-expressions.

The extra information is not a complete solution. We would still get counter intuitive behavior for examples such as:

   open nat
  definition to_nat : bool -> nat :=
  | tt := 1
  | ff := 0

  open bool
  eval to_nat tt  -- produces 1 (correct)
  eval to_nat ff  -- produces 1 (error)

The problem is that tt and ff were treated as variables instead of constructors when we compiled to_nat.

It is not feasible to open namespaces for the reasons I described above. It would generate  confusion. Recall that the order we open namespaces matter.

So, I'm thinking about the following solution: on the left-hand-side of equations we reject variables names that are suffixes of unary constructors. For example, we will reject tt, ff, and zero because we have the constructors bool.tt, bool.ff and nat.zero.
Non-unary constructors are not problematic because the compiler would reject a term such as (succ n). It generates an error such as
 invalid argument, it is not a constructor, variable, nor it is marked as an inaccessible pattern
  succ n
in the following equation left-hand-side
  add (succ n) m

Update: after commit https://github.com/leanprover/lean/commit/107763a506772d9fcc294fb536d24d5fce02dbab
The following also works:
definition pushout_diag {f : TL → TR} {g : TL → BL} : diagram :=
diagram.mk pushout_ob
           bool
           (λi, match i with | tl := TL | tr := TR | bl := BL end)
           (λj, match j with | tt := tl | ff := tl end)
           (λj, match j with | tt := tr | ff := bl end)
           (λj, proof (match j with | tt := f  | ff := g end) qed)

The following also works:

Great. That solves that part of the issue.

So, I'm thinking about the following solution: on the left-hand-side of equations we reject variables names that are suffixes of unary constructors.

It might be problematic if we have something like the following, though
structure this_is_almost_never_used (A : Type) := (n : A) (k : A)

or more realistically:
structure pair (A : Type) := (x : A) (y : A)

This can be especially problematic, since we don't even have to open the corresponding namespace of the these structure, we only have to import the file where they are declared...

Maybe this idea works.
If I write something like this
definition foo : bool × nat × list num → Type :=
| /- big list match expression here -/

is it easy to extract the datatypes which we could potentially match over (so prod, bool, nat, list, num in the above example)? If so, the match expression could generate a warning when (declarations from) one of these namespaces is not opened. Would that work?

or more realistically:

structure pair (A : Type) := (x : A) (y : A)

Yes, this would be a mess.

is it easy to extract the datatypes which we could potentially match over (so prod, bool, nat, list, num in the above example)?

For the example you posted is easy. However, this is not true in general.
Suppose we have match t with ... end, the type of t is only known after we perform type inference and solve unification constraints. Even after we find the type, the exact datatypes used are only known after we normalize. Moreover, we are not necessarily matching against all of them.
Only in the pattern matching compiler, we obtain this information. To make things messier, the pattern matching compiler is unaware of the existence of the open command, aliases, etc.

Hmm... I see how this can be hard in general.
I give up, I'm out of ideas. Maybe we should just add make sure that you open all relevant namespaces when writing match expressions bolded and in huge font in the tutorial. :-)

I'll add an explanation next time I settle down to work on the tutorial.

After the two commits above, Lean produces the following error message for:
528.lean:6:5: error: type mismatch at definition 'match', has type
  P bool.ff
but is expected to have type
  P bool.tt
The following identifier(s) are introduced as free variables by the left-hand-side of the equation:
  ff

Lovely!


Problem: in multi selection mode, click the selected photo repeatedly, and the original zoom of the photo will be reset.

My English is not good, I hope you understand.
Problem: in multi selection mode, click the selected photo repeatedly, and the original zoom of the photo will be reset.
Method: after restoring the scale of the selected photo, add the scale record to the array again.
If the original intention is to reset, would you please tell me the reason?
Thank you very much.
问题：在多选模式下，重复点击已选中的照片，照片原有缩放会被重置
方法：在复原选中照片缩放比例后，将缩放记录再次添加到数组內
如果本意就是重置，那能否告知原因，十分感谢

@XinHaoZhuang check https://github.com/raywenderlich/swift-style-guide and update accordingly.

@XinHaoZhuang nice catch ! Thank you so much for taking the time to fix it for everybody 🥇

@NikKovIos I'll take care of the code styling update.


Added Troubleshooting section and CSS Classes subsection to readme

Initiated from discussion in https://github.com/bevacqua/dragula/issues/142

Made a bunch of inline comments. Please fix those issues and then squash the commits. I'll merge this in then. Thanks!!

Done. Sorry for the added work ! Doing the pull request now.

Let's add a note about gu-mirror elements, there's the gotcha where people sometimes style elements with selectors like .list .item and then don't understand why their .item isn't styled properly when it isn't a child of .list

Makes sense, I'll throw some infos about it in my next commit (as a matter of fact, I had the exact same problem because of my scss classes nesting)

Okay, I'm not totally satisfied with the way I wrote it but I'm not sure any other way would be easier to grasp. If you're okay with it, i'll commit and push the change right away :

gu-mirror is added to the clone. It handles fixed positionning and z-index (and removes any prior margins on the element). Note that the clone element is appended to the document.body, not to its initial container. Keep that in mind when styling your elements with nested rules.

to the clone mirror image
positionning
Note that the clone element mirror image
add an explicit "like .list .item { padding: 10px; }" at the end

Noted. Two quick remarks though :

If we use the terms "mirror image" here, we should use these in every class description so it's not confusing (see gu-transitdescription). Are you okay with it ?

The "like .list .item ..." example looks really confusing to me since neither .list or .item have been explained or even mentioned as-is in the readme. I'm obviously okay to add it if necessary but are you really sure ?

Yes, the clone term is confusing because of the copy option. So we should use the mirror image and copy terms, which are more precise and consistent with existing documentation.
Re: .list .item I think it's good enough for now and we can adjust it over time, but I'd like to merge this in as soon as we can

When you're done please squash the commits

As per #144, we should probably add a note mentioning that you should actually include the styles in dist/dragula.css in your site, even though they are like four of them.

@hezad got any spare minutes for this one?

Hey again, sorry for the delay.
I'll add the info about the CSS inclusion and commit right away !

Okay commited. Tell me if you have remarks about the wording in commit 0a67e2ac78b60c51c3eed9ec87456062a597fd47
I won't be available for two weeks starting sunday but I'll be able to commit stuff tomorrow if necessary. I'll also be happy to help about documentation at my return if needed !

Looks great.


Unable to run Template Framework Project

I'm having a trouble running Template Framework Project.
I cloned this repo, installed CocoaPods and followed the instruction to add Podfile to my directory.

I then ran

pod install
which seemed to have worked.

However, I get the following error when I try to run the app in Xcode:

ld: framework not found TesseractOCR
clang: error: linker command failed with exit code 1 (use -v to see invocation)

How can I fix this?
Thanks so much in advance!!

You need to add the TesseractOCR.framework manually, as you can see those files are in red. So, erase the files in red and add the TesseractOCR.framework manually.
I upload the framework you need to add in this comment for you.
TesseractOCR.framework.zip

@yosukesugishita, why do you add Template Framework Project to your own project?
It's not a framework! It's a template, which shows the way to use the TesseractOCR-iOS framework.
Pls, use cocoapods correctly to integrate the pod into your project. Also you don't need to clone the repo, if you use cocoapods.

I'm troubled by a error, when I use CoreImage Framework and Tesseract.  I use CIDetector to recognize QR code，It returns nil for it need arm64，but my tesseract don't support arm64.how can i  solve the problem.
Thanks so much in advance!!

@quchangle, which TesseractOCR-iOS version do you use?
It supports the arm64 architecture in current version.

@ws233 do you have current version of TesseractOCR-iOS which supports the arm64? could you help me? I really need this framework for my program.In our country ,the development of technology is not very mature and there are not so many resources.I can't find the resources of TesseractOCR -iOS.I really need your help. thank u very  very  very  very  very  very  very  very  very  very  very  very  very  very much!
Thanks so much in advance !!

@quchangle, just clone this repo.

oh~ i find! so great you are. I love you!!!hahhhhhh


Upgrade vite to 3.0.3，@vitejs/plugin-vue to 3.0.1

Description

What is the purpose of this pull request?

[ ] Bug fix
[x] New Feature
[ ] Documentation update
[ ] Other

Now<EMAIL_ADDRESS>still has some problem  👉 https://github.com/electron-vite/electron-vite-vue/issues/212