Lowercase the topic when consulting grandpa

Noticed twinkle vision pref didn't update when I used a capitalized topic, despite grandpa still talking about it.

By this logic there could be a behaviour that requires using capital
letters that would then be impossible to submit via mafia.
Make a big report to KoL I think.
On Wed, 4 Oct 2023, 05:44 codecov[bot], @.***> wrote:

Codecov
https://app.codecov.io/gh/kolmafia/kolmafia/pull/1995?src=pr&el=h1&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=kolmafia
Report
Merging #1995
https://app.codecov.io/gh/kolmafia/kolmafia/pull/1995?src=pr&el=desc&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=kolmafia
(912b41c
https://github.com/kolmafia/kolmafia/commit/912b41cdae7ae1d1fa030ec824d71a95efab927c)
into main
https://app.codecov.io/gh/kolmafia/kolmafia/commit/0a164751998190c819b5e7d8e1be948d2e2d8243?el=desc&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=kolmafia
(0a16475
https://github.com/kolmafia/kolmafia/commit/0a164751998190c819b5e7d8e1be948d2e2d8243)
will decrease coverage by 0.02%.
Report is 1 commits behind head on main.
The diff coverage is 100.00%.
Additional details and impacted files
[image: Impacted file tree graph]
https://app.codecov.io/gh/kolmafia/kolmafia/pull/1995?src=pr&el=tree&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=kolmafia
@@             Coverage Diff              @@##               main    #1995      +/-   ##
============================================- Coverage     36.95%   36.93%   -0.02%     + Complexity    19244    19236       -8
Files          1088     1088
Lines        167114   167114
Branches      35403    35403
============================================- Hits          61751    61725      -26     - Misses        95447    95478      +31     + Partials       9916     9911       -5
Files
https://app.codecov.io/gh/kolmafia/kolmafia/pull/1995?src=pr&el=tree&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=kolmafia Coverage
Δ
...t/sourceforge/kolmafia/request/GrandpaRequest.java
https://app.codecov.io/gh/kolmafia/kolmafia/pull/1995?src=pr&el=tree&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=kolmafia#diff-c3JjL25ldC9zb3VyY2Vmb3JnZS9rb2xtYWZpYS9yZXF1ZXN0L0dyYW5kcGFSZXF1ZXN0LmphdmE= 48.97%
<100.00%> (ø)
... and 7 files with indirect coverage changes
https://app.codecov.io/gh/kolmafia/kolmafia/pull/1995/indirect-changes?src=pr&el=tree-more&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=kolmafia
Continue to review full report in Codecov by Sentry
https://app.codecov.io/gh/kolmafia/kolmafia/pull/1995?src=pr&el=continue&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=kolmafia
.
Legend - Click here to learn more
https://docs.codecov.io/docs/codecov-delta?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=kolmafia
Δ = absolute  (impact), ø = not affected, ? = missing data
Powered by Codecov
https://app.codecov.io/gh/kolmafia/kolmafia/pull/1995?src=pr&el=footer&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=kolmafia.
Last update 0a16475...912b41c
https://app.codecov.io/gh/kolmafia/kolmafia/pull/1995?src=pr&el=lastupdated&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=kolmafia.
Read the comment docs
https://docs.codecov.io/docs/pull-request-comments?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=kolmafia
.
—
Reply to this email directly, view it on GitHub
https://github.com/kolmafia/kolmafia/pull/1995#issuecomment-1746126744,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABL4LSY44SVPHGVFQBVTDTX5TSUDAVCNFSM6AAAAAA5R7XDO6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONBWGEZDMNZUGQ
.
You are receiving this because your review was requested.Message ID:
@.***>

@gausie I don't follow. kol behaves properly, but mafia isn't setting the twinkle vision preference because I used "Hierfal" instead of "hierfal"

I noticed that the preference was not set for me when I asked about "Hierfal" as well.  There is precedent for assuming user input is case insensitive in which case this fix is reasonable.  If it is possible, likely, or currently true that the Grandpa topics could be case sensitive on KOL's side then this fix could introduce a problem in the future and changing the switch to trigger on "Hierfal" would be a better fix.

Oh! Totally misunderstood. This is good then.
On Wed, 4 Oct 2023, 01:13 libraryaddict, @.***> wrote:

@gausie https://github.com/gausie I don't follow. kol behaves properly,
but mafia isn't setting the twinkle vision preference because I used
"Hierfal" instead of "hierfal"
—
Reply to this email directly, view it on GitHub
https://github.com/kolmafia/kolmafia/pull/1995#issuecomment-1746149449,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABL4LUT6THIOFQTXBOMFCLX5TWA3AVCNFSM6AAAAAA5R7XDO6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONBWGE2DSNBUHE
.
You are receiving this because you were mentioned.Message ID:
@.***>


python preprocess/preprocess_flickr_train.py

Hi! Encountered issues where no output data is saved in the outputdirectory/frames. Is there anything wrong with the training dataset that I downloaded? Thanks!

Hello! Thanks for your interest in our work! I can't say for sure what the issue is without more information, but looking at the script I realized that I didn't add code to create the folder structure for the training data. I'm not sure if you did this already or if this is the problem, but try to manually create the folder structure, like this:
train/ train/frames train/audio train/flow train/flow/flow_x train/flow/flow_y
Let me know if this doesn't work or if something else is wrong!

Hi! Thanks for your reply! I did follow the suggestion you gave and it works! However, there are some missing files in both of the dataset links you gave which caused the errors while training the model. (Or maybe I missed out something). Here are some findings on the two datasets.

 - No data annotation files (.xml)
 - The mp4 files contain black screen only (Looks like mp3 instead of mp4)
Please enlighten me if there's any misunderstanding on my side. Thanks! Have a nice day!

Hello! My apologies; the read-me isn't clear on this part and I'll update it. You need to use flickr-soundnet-dl to download both the train AND test videos. The only thing you need to get from the second link is the Annotation folder, which contains the bounding boxes that previous work labeled. This is the exact problem we had originally, that the original test videos aren't available, meaning we need to download them manually and then just use Learning to localize sound sources annotations.
To reiterate steps:

Use flickr-soundnet-dl to download training AND testing samples. You can download all flickr samples and split, or you can manually separate the urls_public.txt into train and test sections, and download separately.
Then use our train and test scripts to create the training and testing audio-frame-flow pairs for the train and test set respectively.

I hope this answers all your questions and please comment again if you have an issue!
Thanks.

I recommend to split the urls_public.txt and download the training and testing samples separately, as that is what the preprocessing scripts are expecting. If you look at the differences between the train and test preprocessing scripts, this should make sense.

Given the nature of downloading these datasets from YouTube, you are most likely not able to download some videos that were recently deleted. I recommend further filtering out the test csv's based on the samples you do have access to.
Our flickr test set resulted in 178 samples, but you will most likely be missing a couple more from these.
I hope that makes sense.
If this isn't the problem you have, I recommend making sure you have your filepaths correct for the ground truth annotations folder.


Latest dbt version compatibility

Hey! Just wondering if you're thinking about supporting newer dbt-core versions anytime soon? Right now, it's stuck at <1.5.0. Really keen to try sqlmesh on my own to see how it can make my work easier before I fully switch over.

Sure thing!

Confirmed SQLMesh works with dbt-core 1.7.9. Created a PR to update the dependency.

Wow that's fast :) how about <2.0 instead. It will prevent keeping up to date. I would rather open an issue here because of a breaking change introduced in dbt-core than to request for an upgrade


Dependency package node-fetch has a new version available

We have identified a dependency on node-fetch (2.6.7). A new version (3.2.0) is available now.

This task should be taken up along with #19165

Hi just checking any update to upgrade node-fetch to 2.6.7 ?

Hey @snuffykl
Our current dependency on node-fetch is using the semver notation ^2.6.6 which should give you the latest minor and patch updates with major version 2. Are you looking for node-fetch to be updated to v3?

Hey @snuffykl
Our current dependency on node-fetch is using the semver notation ^2.6.6 which should give you the latest minor and patch updates with major version 2. Are you looking for node-fetch to be updated to v3?

Hi @ramya-rao-a
I am looking to get it to 2.6.7. Good to know it will give me 2.6.7.
Thank you.

Unfortunately we won't be able to upgrade to v3 in the short term. The reason is that node-fetch v3 dropped support on commonjs modules. In order to migrate we'd need to make our packages ESM-only which we are not ready to do at the moment.
There seems to be a big number of community members impacted by the commonjs drop in node-fetch (for reference: node-fetch/node-fetch#1263)
@praveenkuttappan is there any way to tell the Dependency checker to just look at new versions under 2.x.x for this package?

We will only log issues for available major version updates. v2.x.x will be auto updated when our automation do rush update --full.
We could move this to backlog then check back in the future.

Unfortunately we won't be able to upgrade to v3 in the short term. The reason is that node-fetch v3 dropped support on commonjs modules. In order to migrate we'd need to make our packages ESM-only which we are not ready to do at the moment.

@joheredi Do you have long term plans to migrate to v3 and make the SDK packages ESM-only?

@bterlson should be able to comment about the long-term plans for ESM-only packages in this repo.

Please consider updating to patch v2.6.7 to address high vulnerability issue per: https://github.com/advisories/GHSA-r683-j2x4-v87g
Update seems more urgent now.

We already updated to 2.6.7. Also since our dependency on node-fetch is a caret one, running npm update on your side would get you the latest version 2.6.7 without core-http releasing a new version


Automatically Update Algolia Search Results

Currently, Algolia search crawler does not automatically update on a regular basis or when new docs are added to .com/docs
Algoia search results should be updated at least on a regular interval, or ideally, whenever changes are made to the docs.

@adamsoffer we don't use the python scraper repo for that or do you have another solution?

@FullStackTiger let's move away from the manual python scraper we use currently and set up automatic scraping using github actions + Algolia DocSearch. Here's a decent tutorial on how to set that up. Seems fairly straight forward. Think you can tackle this?

I set up automatic scraping using GitHub actions with cron job here:
https://github.com/livepeer/algolia-docsearch-scraper/commit/cb71bf8cf4787a979b19cf6bace71d5d98858426
The python scraper runs when pushing the code to the main branch, and at 00:00 every day.
It is working well now.
@adamsoffer @pglowacky

@FullStackTiger Looks like the github action was set up properly. Nice work. Let's confirm it runs again as scheduled and then we can close this issue.

It is working well like this:


Move from master to main in travis.yml

I think Travis is still going to run this against master and not main since that's what this change is requesting, but they should be even.


Validate vcpkg release of packages on a cadence

Push all packages to the vcpkg fork nightly
Run vcpkg CI and confirm that it succeeds

This is merged


'Category' CodeableConcept column for Bot

https://github.com/medplum/medplum/issues/1954

Coverage: 94.262%. Remained the same when pulling 1a19020a44740e36db722756ff8f2b40acf033f7 on james-bot-type into f93a460aee648b7d479a93da4fb3dbfa8fa90b2d on main.


Installer cleanup

Toward #3191:

make bcbio_nextgen_install.py PEP8 compliant
remove unused code from install_conda_build()
remove unnecessary error handling around import of argparse module

Thank you! Also, thanks for being cool about the 100 character pep8 instead of 80.

No problem though I'd still prefer 79 :)


Lint warning

Fix lint warning

Codecov Report

Merging #2785 (44fd18d) into main (5f147f9) will not change coverage.
The diff coverage is 100.00%.

:exclamation: Current head 44fd18d differs from pull request most recent head 08103e9. Consider uploading reports for the commit 08103e9 to get more accurate results

@@           Coverage Diff           @@
##             main    #2785   +/-   ##
=======================================
  Coverage   65.89%   65.89%
=======================================
  Files         485      485
  Lines        9320     9320
  Branches     2001     2001
=======================================
  Hits         6141     6141
  Misses       3176     3176
  Partials        3        3

Impacted Files
Coverage Δ

...outes/views/components/dataToolbar/dataToolbar.tsx
6.55% <100.00%> (ø)

Continue to review full report at Codecov.

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


Why i get "loss is nan, but AP/AR is correct"

when i train my model, i obtained that the loss is nan, meanwhile AP/AR is right. Who can tell me why?

Can you show us the Config file ? 😊

@noobying We train the model on faster_rcnn_r50_fpn.py, what we change is

Seems your learning rate is zero

@noobying @jshilong I try other lr， also meet this issue。

Maybe your dataset is too small and this will make the loss to nan.


Support for other platforms

I looked at the discussion on staged-recipes about punting on win and osx and thought I would raise the issue that it would be nice to try to get these working. While ideally, we'd want to get both platforms supported, personally making progress on osx would be enough for me.
Does anyone have thoughts about the path forward on this?

I'd love to get it up and running on osx and windows. It's been a while,
but I believe we had successful recipes for all at one point in the
process. It's just a matter of piecing together the different methods and
calling the appropriate commands per os, with one recipe. This is my first
time building a non-pure python recipe, so its a lot that was new to me.
On Mon, Aug 3, 2020, 8:54 PM Joshua Adelman<EMAIL_ADDRESS>wrote:

I looked at the discussion on staged-recipes about punting on win and osx
and thought I would raise the issue that it would be nice to try to get
these working. While ideally, we'd want to get both platforms supported,
personally making progress on osx would be enough for me.
Does anyone have thoughts about the path forward on this?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/conda-forge/orjson-feedstock/issues/15, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AIQ7MPARUBBBA2MPZ7WVOE3R65S6JANCNFSM4PT4YCJA
.

closed by #16


KOGITO-8868: Remove workspace name 'TEST-DMN' from docs

JIRA https://issues.redhat.com/browse/KOGITO-8868:
Description:
Please make sure that your PR meets the following requirements:

[X ] You have read the contributions doc
[ X] Pull Request title is properly formatted: KOGITO-XYZ Subject
[ X] Pull Request title contains the target branch if not targeting main: [0.9.x] KOGITO-XYZ Subject
[ NA] The nav.adoc file has a link to this guide in the proper category
[ NA] The index.adoc file has a card to this guide in the proper category, with a meaningful description

Screenshot of the changes:

@akumar074 @ricardozanini to backport this for DP5, what is the correct branch?

Hey @ederign DP5 will be cut off from 1.35. I am adding the backport label for it.


ERROR	node.atxBuilder	failed to generate initial proof:	{"error": "post execution: error generating proof: status:GEN_PROOF_STATUS_ERROR"}

Environment

Smapp version: 1.6.4 | develop
Node version: v0.x.xx
OS: Windows 10 | macOS High Sierra (10.13) | Ubuntu 20.04

Describe the bug
Power outage caused issues with node (JS errors on startup) so decided to reinstall Smapp and relink to the POStT data Dir.  All seemed ok,  Startup OK, Node sync OK, Smesh working and finally network working.  In the background I can see that there is POST proof generation process going and can see this process incrementing through each of the postdata files.  Once this reaches the last file I get the following:
2024-07-23T23:38:37.952+0100    INFO    node    [2024-07-23T22:38:37Z ERROR post_service::client] failed proof verification: verifying proof    {"smesherID": "d2119a"}
2024-07-23T23:38:37.952+0100    INFO    node            {"smesherID": "d2119a"}
2024-07-23T23:38:37.952+0100    INFO    node        Caused by:    {"smesherID": "d2119a"}
2024-07-23T23:38:37.952+0100    INFO    node            MSB value for index: 558055458 (id: 0) doesn't satisfy difficulty: 65 > 0 (label: [102, 222, 93, 42, 5, 119, 69, 231, 117, 92, 108, 230, 216, 97, 14, 125])    {"smesherID": "d2119a"}
2024-07-23T23:38:37.952+0100    INFO    node            {"smesherID": "d2119a"}
2024-07-23T23:38:37.952+0100    INFO    node        Location:    {"smesherID": "d2119a"}
2024-07-23T23:38:37.952+0100    INFO    node            service\src\service.rs:208:14 (verification took: 0.6584143s)    {"smesherID": "d2119a"}
2024-07-23T23:38:37.952+0100    ERROR    node.atxBuilder    failed to generate initial proof:    {"error": "post execution: error generating proof: status:GEN_PROOF_STATUS_ERROR"}
The process then loops through restarts and fails over and over.  I cannot find and references to lookup regarding node.atxBuilder so am at a loss what to attempt.  Any ideas please as not want to go through another 2 month postdata build again!
Running on windows 10 with latest version.
Steps to reproduce
app-log.1.6.6.txt
spacemesh-log-7c8cef2b.txt
Try to narrow down your scenario to a minimal working/failing example. That is, if you have a big program causing a problem, start with deleting parts not relevant to the issue and observing the result: is the problem still there? Repeat until you get the most straightforward sequence of steps to reproduce the problem without any noise surrounding it.

Open this
Press that
Click here and there

Expected behavior
What should happen?
Actual behavior
What’s happening now?
Attach screenshots or GIF’s of what’s going on if it makes the issue more illustrative.
Logs
Attach app-logs.txt and spacemesh-log.txt

If you can find out the part of the logs that relates to the problem, attach them or paste in code-block.
How to fix
If you have an idea of how the bug can be fixed, provide a short description.

Have you been able to resolve this @Pheal22? I am in the same boat as you and don't really know how to resolve the issue.

No luck i'm afraid.  Tried running postcli to check the postdata files for errors and it seemed that all had an issue which to me implies that there was a mismatch between keys (post crash system vs new system).  Tried to ensure all keys matched the old system but unable to resolve so undergoing a month(+) re-generation of post data.  So annoying!!


Emit a descriptive error when the QPY version is too new

Summary
This commit updates the qpy load() function to ensure we are raising a descriptive error message when a user attempts to load a qpy version that's not supported by this version of qiskit. Previously it would fail but with a hard to understand internal error message which was just confusing and not helpful. For example, when trying to load a QPY version 10 payload with qiskit 0.25.2 (which only supported up to version 9) it would raise an error message like:
Invalid payload format data kind 'b'p''."

which doesn't tell you anything meaningful unless you are intimately familiar with the QPY file format and how the load() function works. With this commit it now checks if the version number is supported immediately and if it's too new it will raise an error message that says exactly that. So in the above scenario instead of that error message it will say:
The QPY format version being read, 10, isn't supported by this Qiskit
version. Please upgrade your version of Qiskit to load this QPY payload.

Details and comments

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

2 of 2 (100.0%)  changed or added relevant lines in 1 file are covered.
8 unchanged lines in 2 files lost coverage.
Overall coverage increased (+0.01%) to 86.898%

Files with Coverage Reduction
New Missed Lines
%

crates/qasm2/src/lex.rs
2
90.91%

crates/qasm2/src/parse.rs
6
97.6%

Totals

Change from base Build<PHONE_NUMBER>:
0.01%

Covered Lines:
73872

Relevant Lines:
85010

💛  - Coveralls

In general the QPY version is to document exactly that format changes which previous versions are incompatible with. Even in the small case you highlight of an addition to a type key for something that is incompatible with previous releases. If the user generates a qpy payload using that new type code they'll get an opaque message like "k" is not a valid type key or something like that and I feel this error is still appropriate in the general case even if there is a chance a new qpy payload format could be loaded with an older release. Especially in the case of 0.25.3 this is necessary because the format changes are quite large between version 9 and 10 which is why I tagged it for backport.
I think your concerns correctly raise we should not be backporting QPY version changes to stable branches (which is different than our current policy). Also, I'm totally fine with adding a version field to QPY for the next release (now is the time to do it). I was thinking along those lines too, but having a fixed set of support either version 10 or the current new (or whatever the version is for the 1.0 release).

For the first paragraph: yeah, if they get an error like the type-key thing, it'll be cryptic, though that can be mitigated by us making this new error a warning instead; the user should see that instead.  But my point there is that typically new type keys are for new features, and if a user isn't using those, the file will load correctly.  It's almost like we might want an "auditwheel" type thing that assigns the lowest possible QPY version to a file (though that'd be hard to do performantly with our implementation).  If we had that, I'd be more comfortable raising the exception here.
I'm ok if you want to go ahead and merge this - I'm not 100% convinced it's the right thing to do, but I'm equally not convinced that it's not.

What you're basically describing is closer to proper version negotiation. We've been very explicitly avoiding adding that kind of feature to QPY, because it doubles the maintenance burden to support multiple output format versions. But it is what I would have opted for if we were designing a more API endpoint focused format use case instead of as a save file format. But I think we would have changed a lot of QPY's design if we were thinking about that at the start.
I think for backport to 0.25.3 we definitely want this, it's necessary for any 0.25.3 users because version 10 is that much different than version 9. When we introduce QPY version 11 we can revisit this on main, maybe there is a better strategy we can come up with without changing how we handle versioning too drastically. I'm also fine skipping this for 0.45.0 (I'll just directly backport it to 0.25.3) and we can always backport it for 0.45.1 later if we deem it necessary when we introduce version 11.

In the meantime I pushed up #11094 to the stable/0.25 branch where this is really needed. It also turns out the branch's CI has been broken since 0.45.0rc1 was released because the backwards compat jobs have been trying to generate qpy from 0.45.0rc1 and load it with the stable branch's qiskit which emits the the type key error message described in the commit message. I put a cap in #11094 to unblock CI, but we'll probably want to do that on main too as we move to supporting >1 stable branch at a time.

We agreed on #11094 to merge this to stable. I'm still in favour of us adding a version argument to the QPY exporter with a default to the current QPY version, where we don't change the default version on backports to stable branches and emit an error if the circuit can't be exported at the given version, but that's beyond the scope for this PR.
It's fine to merge here for the same reasons as in #11094; all QPY 10 files are unreadable by QPY 9, and there's a chance of that happening again.  We should put in place a way to make it so that newer client-side Terras can be used with older ones with explicit feature restrictions, in order to make it easier to manage server code that depends on Terra, but that's beyond the scope of this PR.


fix(env_dir): Remove directories from the env dir passed to the compile

fixes https://github.com/deis/builder/issues/454 https://github.com/deis/builder/issues/455 https://github.com/deis/builder/issues/456 https://github.com/deis/slugbuilder/issues/124

This looks good, but I want to test it manually first, since I can reproduce the original issues.

I had trouble reproducing the original error now for deis/builder#454, but this looks good otherwise and doesn't cause any new problems I could see.


Using nonce for inline script elements with script-src-attr

Hi there!
I am loading the Lemon Squeezy's 3rd party js in my app with useHead but for that I need to set my script-src-attr to unsafe-inline:
// In page.vue, **not** inside onMounted hook
useHead({
  script: [
    {
      src: "https://app.lemonsqueezy.com/js/lemon.js",
      defer: true,
      onload: setupLemonSqueezy, // Does the post-load setup
    },
  ],
});

// In nuxt.config.ts
contentSecurityPolicy: {
    "script-src-attr": ["'unsafe-inline'"],
},

Of course, I'd prefer not to use unsafe-inline there. So I tried this to use a nonce approach:
// In page.vue, **not** inside onMounted hook
useHead({
  script: [
    {
      src: "https://app.lemonsqueezy.com/js/lemon.js",
      defer: true,
      onload: setupLemonSqueezy,
      nonce: useNonce(), // I understand this is a utility provided by Nuxt Security?
    },
  ],
});

// In nuxt.config.ts
contentSecurityPolicy: {
    "script-src-attr": ["'nonce-{{nonce}}'"],
},

But this nonce approach does not work because I get this error:
Refused to execute inline event handler because it violates the following Content Security Policy directive: "script-src-attr 'nonce-019l8soupC90awZL7QaK/A=='". Either the 'unsafe-inline' keyword, a hash ('sha256-...'), or a nonce ('nonce-...') is required to enable inline execution. Note that hashes do not apply to event handlers, style attributes and javascript: navigations unless the 'unsafe-hashes' keyword is present.

I tested useNonce inside the page to see what value it returns, but it appears to return undefined, so I am not sure how to use that, too.
Do you have any ideas what I am doing wrong here? Simply, I'd like to use a nonce and avoid unsafe-inline while using the onload callback of useHead.

Thank you very much @vejja, this was immensely helpful! I now understand the issue and solved my case with unsafe-hashes.

Thanks @vejja for the amazing help once again.


Handle rename event properly

In https://github.com/e-dant/watcher/issues/39, there was was some discussion about how to report rename events to the user: https://github.com/e-dant/watcher/issues/39#issuecomment-1752741290 https://github.com/e-dant/watcher/issues/39#issuecomment-1773569898
The platform adapters for linux (both inotify and fanotify) and darwin are mostly complete. We still need to put a few extra lines in the Windows adapter on that end, write automated tests to run on CI for rename events, and document how the user should handle them.


#644 | Start speech recognition in "Hot Word" mode when enabled from Settings

Closes #644
Description of Work
This PR fixes an issue where the SpeechRecognitionController would always fire up in "transcription" mode when the user first granted permissions. This is the desired mode when we grant permissions from the Listen category on the Home screen, however this is not what we want when permissions are granted from the Settings screen. Instead, the "hot word" mode should be activated, so the app can properly handle actions after it recognizes the Hot Word.

Test Verified!
Test Devices:

iPad Pro - Test Device - iOS 15.3.1
iPhone 11 - Simulator - iOS 15.4

Version:

1.4.1-1


istio-agent non-daemon mode (generate only)

We need to be able to run istio-agent - or a smaller standalone binary - to do the init and generate the
certificate files, but not start envoy or keep running.
This is needed for apps like Prometheus, which can use the mTLS certificate directly.
It is also needed for gRPC 'proxyless'. In this mode, we would also generate the bootstrap file for
gRPC which is similar but smaller than Envoy bootstrap.
Describe the feature request
Describe alternatives you've considered
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Additional context

As we discussed, for gRPC, I think we'll actually need daemon mode, because we'll need istio-agent to continue to update the cert files as the certs rotate.  So the main thing we need is for istio-agent to generate the gRPC bootstrap file, and it might make sense to split that into a separate issue.
In the future, we can collaborate on ways to eliminate the dependency on istio-agent.  This will probably involve having a CertificateProvider plugin that can speak the Istio CA API (https://github.com/istio/api/blob/master/security/v1alpha1/ca.proto) and adding the ability to set STS call creds for the communication with the xDS server.  At that point, we can move the code to generate the gRPC bootstrap file out of istio-agent and into a standalone bootstrap generator, which users can run on their nodes before starting their application.

Related: https://github.com/istio/istio/issues/28712

Agreed - I think we'll want both 'daemon' and 'exec/cron' mode ( similar with gcloud command ).

Updated requirement:

should be able to run as an XDS proxy ( performing istio-specific auth ), but without starting envoy
instead of starting envoy, should start an app, using the reminder of the command line ( i.e. if an app
is started with "/usr/local/bin/myApp --foo --bar", we can use "istio-agent /usr/local/bin/myApp --foo --bar"

This will be used until gRPC ( or other 'proxyless' frameworks ) support all required Istio-specific auth
methods and CA protocol. The apps will still have no proxy in the data path.

I think the exact CLI needs some adjustments. We should have separate flags to say:

Don't run envoy
Generate gRPC bootstrap (vs some other "proxyless" framework's bootstrap, or no bootstrap gen at all)
Start some other binary using the other flags.

Something like istio-agent --no-proxy --grpc-xds-bootstrap --exec /usr/local/bin/myApp --foo --bar.
I'm not fully convinced we should have the agent manage the lifecycle of the user's app. Having the agent run in another container does make the integration feel less "proxyless" but I don't see any major advantages?

@costinm Can we clarify a bit regarding the usage of exec mode? As John mentioned in https://github.com/istio/istio/pull/33528, user can either run istio-agent with --no-proxy --grpc-xds-bootstrap and run the user app in a separate command or they can run the user command within istio-agent exec mode.
What's the advantage of the latter?

Added a comment to the PR - the goal is to have istio-agent start, create the workload cert and any other file required by the app, and exec the app after, so app has a valid environment.
Otherwise the app will need to have complicated code to poll for the cert or XDS socket showing up, or fail - or relatively tricky shell scripts.

BTW - there is a use case for having exec even when envoy is used - for example a VM or app running in a single-container Docker, where we want to have the app start after everything is in a 'stable' state.
I would just add code to check if the CLI has some unprocessed args ( after -- ), and use them to exec even in envoy mode.

Is there anything else need to be done for this Issue? Last time when I talked to @costinm , he mentioned that this is not needed.
https://github.com/istio/istio/pull/33528#issuecomment-940557910


update compass font icon

Summary
Updating the Compass Icon font to the latest version to include new icons needed for ongoing features.

/update-branch

Looks like you don't have permissions to trigger this command.
Only available for the PR submitter and org members

/update-branch


LCP LSD device name is currently readium-desktop, will need to be updated to Thorium's own human-readable identifier

The LSD status document "events" section lists these human-readable names, so it is important that this gets updated when migrating from readium-desktop to "Thorium".
https://github.com/readium/readium-desktop/blob/663099c027717d3e58cdb772f1d2d1d2c68c2989/src/main/di.ts#L203
Note that r2-testapp-js utilises Readium2 Electron desktop app.

fixed in 7f12fb2281f4051af3a490d97975b0f19f1fd218


Add support for Z time zone and fractional seconds in date formats

I was having trouble getting my dates to parse, and realized it was because Z time zone was not being recognized. I changed it to use the built in "%+" format for parsing RFC3339 dates and added tests to check for this case.

@OinkIguana cheers!


[fix] Fix crash when audio duration is Infinity

This can happen because of a bug in the browser, or if the server serving the audio file doesn't support range requests.

Fixes #1846


Change gcd() implementation to avoid too deep recursion

to fix issue #870

This fix is good. However we have another gcd() (from numeric.hpp) and it is still used in iGemm Invokers (https://github.com/ROCmSoftwarePlatform/MIOpen/issues/870#issuecomment-831241668).


[EventRequest] Page 221 Resource allocated per Job - OnShowMatrixOnAfterSetJobFilters

Requesting a new event publisher on Page 221 Resource allocated per Job
Event
OnShowMatrixOnAfterSetJobFilters(VAR JobRec : Record Job)
Code
ShowMatrix - OnAction()
HorizontalRecord.SETRANGE("No.",ResourceFilter);
HorizontalRecord.SETRANGE(Type,HorizontalRecord.Type::Resource);
JobRec.SETRANGE("Resource Filter",ResourceFilter);

>>> New Code
OnShowMatrixOnAfterSetJobFilters(JobRec);

<<< New Code End
ResAllPerJobFormWithMatrix.Load(JobRec,HorizontalRecord,MatrixColumnCaptions,MatrixRecords,AmountType);
ResAllPerJobFormWithMatrix.RUNMODAL;

In Our Solution we use Jobs also to make configurations. These are not real Jobs, so we need the flexibility to filter these Jobs out. Please add the requested Publisher.

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


Migrating timemapper to datopian and site to e.g. timemapper.datahub.io

@jobarratt I'd like to relocate this datopian and move the site from timemapper.okfnlabs.org probably to datahub.io or a subdomain. Would that be ok?
Context:  this is another project that I created and maintained (https://github.com/okfn/timemapper/graphs/contributors). Not much has been happening on it since I left so i'd like to take it on again ...

What are the consequences for my pages (http://timemapper.okfnlabs.org/thtbln)?

@thtbln they would keep working as normal (should this migration happen).

Thanks, does that also mean the URL will be the same?

Yes.


there are many warnings in swift4.1 and xcode 9.3 like this ：'flatMap' is deprecated: Please use compactMap(_:) for the case where closure returns an optional value

Issues are used to track bugs and feature requests.
Need  help or have a general question? Ask on Stack Overflow (tag sqlite.swift).

Build Information

Include the SQLite.swift version, commit or branch experiencing the issue.
Mention Xcode and OS X versions affected.
How do do you integrate SQLite.swift in your project?

manual
CocoaPods
Carthage
Swift Package manager

General guidelines

Be as descriptive as possible.
Provide as much information needed to reliably reproduce the issue.
Attach screenshots if possible.
Better yet: attach GIFs or link to video.
Even better: link to a sample project exhibiting the issue.

there are many warnings in swift4.1 and xcode 9.3 like this ：'flatMap' is deprecated: Please use compactMap(_:) for the case where closure returns an optional value

#797

Fixed in master

Fixed in 0.11.5


Write a test for the case that token is undefined in useAuth hook

What is it and who's it for?
What
A test against the useAuth hook that ensures the correct UI is presented if the getToken function returns undefined.
For
Everyone (to make sure the site doesn't get into a broken state, such as it could pre #5195).

I don't think we even have a useAuth hook any more; closing.


Use of longjmp()/setjmp()

In the rasterizer, longjmp() and setjmp() are used.
https://github.com/sammycage/plutovg/blob/fa8002f43cf8ce0a233b582c8d54baaff944336d/source/plutovg-ft-raster.c#L293
I'm trying to port plutovg to a platform which doesn't support these. Is there a version of the rasterizer which doesn't need them?
I've tried bringing in an older version from freetype, but it seems to work differently - expecting a bitmap to render to rather than making callbacks.

Is there a version of the rasterizer which doesn't need them?

plutovg?? Noo

Could you please share the older version from FreeType? Let me take a look and see how I can assist you.


Remove charUnHex

High Level Overview of Change

Context of Change

Type of Change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Refactor (non-breaking change that only restructures code)
[ ] Tests (You added tests for code that already exists, or your new feature included in this PR)
[ ] Documentation Updates
[ ] Release

Thanks for looking closely
I fixed the bug you found

Merged as 83ac141f656b1a95b5661853951ebd95b3ffba99


Merge pull request #1 from apache/master

pull20150319

merge

@nonamexu Please close this pull request.


nixos: How to use usb smart cards (yubikey) with GnuPG?

I'd like to get a USB yubikey OpenPGP smart card to work on NixOS (unstable). Out of the box both GnuPG1 and GnuPG21 (e.g. --card-status) simply say that card cannot be found (lsusb does show the device). Any tips?

if lsusb doesnt see anything its wrong at lowest level.  do you see any messages relating to it in dmesg?  maybe do a dmesg -c before hand to be sure.

I don't have one but I found this. It could be gpg is looking for it on the wrong port number.

@rnhmjoj Thank you that tip lead to me to figure out that I must enable pcscd in configuration to support smart cards in NixOS.


Import issue for IE 11

Not an issue in itself, but maybe should be added in the docs, I spent an entire day finding this:
 import dropdown from 'vue-strap/src/Dropdown' is not ok for IE 11, (but works in Chrome and Firefox).
IE likes it only like this: import {dropdown} from 'vue-strap'

I have similar issue on IE. Works fine both on Chrome and Firefox. But there are errors on IE 11. I think that it is related to ES6.


Date/time error when creating view

Trying to run

ocdskingfisher-views-cli add-view 1512,1517,1515 ...

Getting this error

psycopg2.errors.DatetimeFieldOverflow: date/time field value out of range: "0000-04-30T13:46:38+01:00"

Looking at the log files, it's happening here

Oct 22 12:25:11 process1 2020-10-22 12:25:11,429 - 13935 - ocdskingfisher.views.refresh-views - INFO - Running 007-contracts

Any ideas?

@odscrachel I assume the source data might have a date value that is out of PostgreSQL's allowed range. I suppose a solution is for the query to filter out out-of-range dates. In that case, a note should perhaps be written to a table to let the user know that some dates were omitted from the aggregation.

This is due to dates starting with 0000 and for some reason postgresql does not like that year (it actually represents 1 BC)
We already exclude any non ISO looking dates from the results and null them.  I think it might be a separate issue to log these.  However, the idea was that these were going to be picked up as validation errors, so there was no need for separate log.
The validation errors could according to ISO be allowed to pick up on dates before 1583, see https://en.wikipedia.org/wiki/ISO_8601#Years.

Instead of a separate log, I've just requested a sentence in the docs in the PR.

Deployed #154. @odscrachel You can try again now.

Great, all is working fine now and view created. Thanks @kindly and @jpmckinney


Odd behavior with bulleted list in WYSIWYG

When you create a new piece of content with a markdown field, toggling the bulleted list in the WYSIWYG does not show the bullet in the editor. Even though the bullets are not shown in the editor, lists are saved correctly. Oddly enough, the bullets do show in the UI if you are editing a piece of content. They are only absent when you are adding new content.

this is a styling issue, some styles that should only be applied to the content list pages are applied overly broadly.
in this case the list is being rendered to the dom correctly:

but .site-page .content ul has list-style: none; applied to it. I'll open a PR to fix that selector.


Guide structure: Getting Data from Users

I have updated the guide on forms and tabular input and found that it may need some restructuring.

https://github.com/yiisoft/yii2/issues/7040
55196dc869d9af1391492cda3cd2f8c1bdde2843
97e3df1626bf4aa3047e42385b37f0f127d3ad3d

Currently there is the following structure:

Working with Forms

general intro about how to use ActiveForm
handling tabular input

validation
file upload
Getting Data for Multiple Models

The main problem is in the first part which covers creation of forms without handling validation but  already talks about tabular input.
I suggest to change it to something like this:

Working with Forms

general intro about how to use ActiveForm

validation
file upload
handling tabular input
Getting Data for Multiple Models

@yiisoft/core-developers opinions?

Agree.

Yes, the input-*.md (except input-validation.md) sections all need further improvement. It's good to see you start this effort. :)


Certificate Revocation List (CRL) support with https

Currently requests doesn't support checking if a certificate has been revokes in a CRL when using verify=True, it would be quite useful if this was supported.

I am also interested by this feature. When using an internal CA, the CRL as a file is the easiest path. Far easier than using an OCSP endpoint and more reliable than embedding an HTTP URL into the certificate (no way that the CRL can be unavailable due to a temporary outage).
@Lukasa I don't understand when you say this can be done outside requests. There is no way to preprocess the certfile with the CRL. The certfile is usually a root certificate and the CRL contains the serial numbers of revoked certificates. There is no way to apply a CRL to a root certificate.
With curl, you can specify it with --crlfile.

@vincentbernat Yeah, that's a fair point.
We're aiming to add support for providing an external SSLContext object, which should make this possible, but until that's done I don't think we can do much else.


long press on backspace should delete words not letters.

Currently, long pressing the backspace deletes letters consecutivly, we would rather like to delete words in this case.
This should be configurable as well from settings.

Word deletion is a good idea, I didn't consider that till now.
On the other hand I think the current behaviour is quite useful. What's about right -> circle -> right -> circle to start word  deletion?

don't have to add a new gesture... pressing right does a normal backspace, and keeping it pressed will initiate the word deletion. I don't think we need another gesture. This behavior is pretty standard in most other keyboards, so a new user will not find it awkward either.

Maybe have an option for the user to decide whether to delete characters or delete whole words because it might delete too fast (acceleration) and this could be an unexpected and undesirable behaviour.

I don't like the thought of this deleting words on rapid-fire. The main reason for this are web-links. I often want to delete parts of links (or parts of long words) and making rapid-fire-backspace delete whole words just forces users to

repeatedly tap backspace or
use the "mark text"-function (right -> center) to select text to finally delete it.

Maybe instead of making rapid-fire-backspace delete whole words, we could create another shortcut... Something like click and hold the left sector + click (or hold if you need rapid-fire) the right sector to delete words instead of letters.

This behavior is pretty standard in most other keyboards, so a new user will not find it awkward either.

Honestly, most keyboards I know just delete single letters. I can't even think of a single one I know that rapid-fires word-deletion.

Afaik, most keyboards delete whole words if you press and hold backspace. Just tapping it removes an individual character.
I personally see no issue with implementing it like that.

We already have a way to delete a lot of text very quickly. The up-arrow at the selection board. (This is an amazing functionality btw.)
Taking away single-character-deletion rapid-fire seems to just remove great editing features to me.
Also i would argue that deleting 5 letters is more common than deleting 5 words. At least that's the case in my experience.

While you can remove characters quickly with rapidfire single character deletion, what's the point? It's too fast so consistently only delete the text you want anyway, so you would have to stop before you hit the part you want to keep and finish deleting with some manual, single character backspace presses.
if you want to remove exactly 5 characters, it's easier to press the backspace sector 5 times than to hold and release shortly after, hoping that you didn't remove too much.
Also, I personally delete whole words and often sentences more often than having to remove a specific amount of characters.
Regarding URLs, I think that "whole word" deletion should recognize words as a group of characters surrounded by any of these characters: *?_-.[]~=&;!#$&(){}<>/\. That way, when deleting some part of the URL, it would remove one path level at a time. That's at least what I do most often when I remove part of an URL.

It's too fast so consistently only delete the text you want anyway, so you would have to stop before you hit the part you want to keep and finish deleting with some manual, single character backspace presses.

That argument works in both directions. It could also be used as a reason to not have rapid-fire for deleting words. So it doesn't help any side.

if you want to remove exactly 5 characters, it's easier to press the backspace sector 5 times than to hold and release shortly after, hoping that you didn't remove too much.

You're right. 5 Characters (or let's say 6 for the sake of the argument) probably is the cutoff-point though. Which means longer Words get awkward.
Actually, an even better example is when you want to delete 3 Words. Let's use your example:

if you want to remove exactly 5 characters

Now let's say, we have 5 words we want to delete. With word-deletion-rapid-fire. The same problem exists. You have to wait for the rapid-firing to start AND you have to try to not accidentally delete too many words. (which is easy when rapid-firing word deletions.) And when you mess up only by a single word, now you may either need re-type a whole word, or delete it (now spamming backspace, as we can't let it rapid-fire (since we have removed it from the app). And that's the best-case mess-up scenario, where you only missed the timing by one Word. What happens if you messed up by two words? It gets even more annoying.
Rapid-firing single-character-deletions would handle deleting 5 words just fine. It's fast enough and when messing up the timing, you might only need to re-type (or delete) two letters instead of two whole words.
We could of course decide to slow down word-deletion-rapid-fire so that it's easier to stop it at the right place. But if we slow it down... well, then where's the advantage over (a fast) single-character-deletion-rapid-fire? There is none.
If we summarize the situation with word-deletion-rapid-fire:

< 6 characters to delete: works fine (character-backspace)
6 or more characters to delete: doesn't work well (nothing)
< 6 words to delete: doesn't work well (nothing)
6 or more words to delete:  works fine` (word-backspace-rapid-fire or the selection-keyboard)

Keep in mind that the last point isn't as great of an argument for word-deletion-rapid-fire as it seems because of two reason:

There already is an option that works well in most instances for texts that long. (It works well in every instance where the text is allowed to have a line-break. Which is most of the time.)

We already have a way to delete a lot of text very quickly. The up-arrow at the selection board. (This is an amazing functionality btw.)

There's still the danger of deleting too few/too many words.

Now what happens if we add the functionality I suggested?

Maybe instead of making rapid-fire-backspace delete whole words, we could create another shortcut... Something like click and hold the left sector + click (or hold if you need rapid-fire) the right sector to delete words instead of letters.

Let's look at the same checklist again.
If we summarize the situation with word-deletion-rapid-fire:

< 6 characters to delete: works fine (character-backspace)
6 or more characters to delete: works fine (character-backspace-rapid-fire)
< 6 words to delete: works fine(word-backspace)
6 or more words to delete:  works fine`(word-backspace-rapid-fire or the selection-keyboard)

That argument works in both directions. It could also be used as a reason to not have rapid-fire for deleting words. So it doesn't help any side.

Now let's say, we have 5 words we want to delete. With word-deletion-rapid-fire. The same problem exists. You have to wait for the rapid-firing to start AND you have to try to not accidentally delete too many words. (which is easy when rapid-firing word deletions.) And when you mess up only by a single word, now you may either need re-type a whole word, or delete it (now spamming backspace, as we can't let it rapid-fire (since we have removed it from the app). And that's the best-case mess-up scenario, where you only missed the timing by one Word. What happens if you messed up by two words? It gets even more annoying.

First things first, I want to make clear that my main goal isn't trying to win "the argument" about why we should use the word deletion mode ;)
I just like to discuss some ideas and collectively think about how the keyboard could be improved. Therefore, I'm very happy that we can constructively share our thoughts about this topic here. It allows me to get a better understanding about the whole thing.
That being said, I hope that you can understand why I believe that using word-deletion mode for rapid-fire is an improvement. Feel free to ask if I didn't explain something well enough.
There are two factors we want to minimize and thus have to keep in mind when comparing the two rapid-fire deletion modes:

The probability of deleting too much. (Alternatively, the probability of not stopping deleting where we intended to.)
The number of characters that get deleted when we accidentally delete too much. (Alternatively, the effort needed to fix the mistake once it happens.)

Rapid-firing single-character-deletions would handle deleting 5 words just fine. It's fast enough and when messing up the timing, you might only need to re-type (or delete) two letters instead of two whole words.

I agree. When you hold delete for too long (i.e. delete too much), you may delete fewer characters in character-deletion mode, compared to word-deletion mode. After all, in the latter mode, the whole word disappears. In the former, you can possibly stop deleting, before the whole word is gone, so you only have to retype the missing letters.
Therefore character-deletion is better if we solely focus on the second factor:
Remove the least amount of characters when we accidentally have deleted too much.
However, I'd argue that we should mainly focus on trying to minimize the first factor:
Reduce the probability of deleting too much.
Why? Because from a usability and UX point of view, deleting too much should be the absolute exception.
Removing content you didn't intend to delete is at the very least frustrating. I wouldn't want to use a keyboard where I regularly delete content I wanted to keep, by mistake. In the best case, wrongly deleting content shouldn't happen at all. At the very least, it should only happen very rarely for it to be acceptable. I want to delete up until the point I chose to, without undercutting or overshooting my goal.
I'd argue that it is better to rewrite the whole word you mistakenly deleted once in a blue moon, compared to sometimes having to retype the few characters you accidentally removed. Would you also agree?
"Why would that rapid-fire mistake happen less often when using word-deletion, compared to character-deletion?"
I assume the deletion speed of both word-deletion and character-deletion to be roughly equal. So for example, if we estimate the median word length to be 5 characters long, deleting a word with word-deletion should roughly be as fast as deleting 5 characters in character-deletion. So far so good. But now comes a nice improvement that you tangentially commented on:

We could of course decide to slow down word-deletion-rapid-fire so that it's easier to stop it at the right place.

Indeed! That would really help with preventing deleting too much.

But if we slow it down... well, then where's the advantage over (a fast) single-character-deletion-rapid-fire?

To solve the related problem you mentioned we have to tweak the idea of slowing down rapid-fire without compromising its functionality, by adding pauses between word deletions! if you take a look at the way other keyboards implement this feature, you may notice that rapid-fire word-deletion usually appears to be "slower", giving you time to stop deleting where you want to. It just looks that way. The number of deleted characters per second should be roughly equal in both word-deletion and character-deletion mode. But because deleting a whole word in word-deletion mode takes as much time as deleting only one character in character-deletion mode, with word-deletion mode you can repurpose the leftover time (i.e. the time you'd need in character-deletion mode to remove the rest of the word) as a pause between word deletions.
Example:
You have the sentence I am using an awesome keyboard and want to delete the words awesome keyboard.

In character-deletion mode, in total you would spend 16 ticks deleting. One tick for each character.
If you accidentally hold delete for 3 ticks too long, you would remove 3 characters by mistake.
In word-deletion mode, in total you would spend 2 ticks deleting. One tick for each word. (If you wonder about the space, it's counted as part of awesome and thus deleted with it in one tick.) The remaining 14 ticks can therefore be used to add pauses between word deletions.
If you accidentally hold delete for 3 ticks too long, you wouldn't remove anything by mistake.:

tick 1 deletes keyboard
tick 2-7 are pauses and thus do nothing
tick 8 deletes awesome
tick 9-16 are pauses again

Note: When implementing the pauses of word-deletion mode, please don't count word lengths to generate the pauses. I did it in the example to illustrate the different between the two modes. The goal isn't to perfectly match the speed of character-deletion mode in word-deletion mode. It would even be counterintuitive if pauses had different lengths. It's perfectly fine to just assume that the length of each word is the average word length and to create a hard-coded pause length based on that. Or just set a hard-coded pause length that looks and feels okay. No need to over-complicate things at this point.
The speed between both modes is roughly equal, but you have more rapid-fire delete precision in word-deletion mode. It's a trade-off between "being able to stop deleting wherever you want to, but sometimes not stopping where you intended to ( = character-deletion)" vs. "only being able to stop deleting at word boundaries, but certainly stopping at the boundary location you intended to ( = word-deletion)". I think the latter - word-deletion mode -  is the better compromise. There are plenty of word boundaries not far away from each other. In most cases where you rapid-fire delete text, you want to (or it is at least okay if you) delete word by word. If you ever want to stop deleting at a certain location in the middle of a word, just delete up until the nearest word boundary after the word (which is easy to do, thanks the pauses increasing your precision) and afterwards use the single backspace a few times until you reach your chosen location within the word.
Note that applying the idea of using pauses to character-deletion would be awful, as having a pause long enough to confidently being able to stop where you want to between each and every character deletion is painful and wouldn't be "rapid-fire" anymore, as you have correctly stated.
Adding pauses between word deletions in word-deletion mode sounds reasonable, as there are less "pauses" which are long enough to allow for fast and precise deletion. This functionality fits the rapid-fire idea perfectly and adds the needed precision I mentioned as the first factor. Some keyboards (SwiftKey, for example) further improve this feature by gradually shortening the pauses between word deletions, the more you delete in one go. It thus slowly moves the focus from precision to speed (up to a certain point), which further fits common text deletion use cases. You get both the granularity you want when removing short sections of text, and the option of quickly deleting larger amounts of content, combined.

Maybe instead of making rapid-fire-backspace delete whole words, we could create another shortcut... Something like click and hold the left sector + click (or hold if you need rapid-fire) the right sector to delete words instead of letters.

I don't think this is a good idea. Not only because of the reasons I mentioned above in favor of word-deletion mode, but also because you would need more than one finger/hand to use your proposed shortcut. That would go against the underlying notion of this keyboard, don't you think?

First things first, I want to make clear that my main goal isn't trying to win "the argument" about why we should use the word deletion mode ;) I just like to discuss some ideas and collectively think about how the keyboard could be improved. Therefore, I'm very happy that we can constructively share our thoughts about this topic here. It allows me to get a better understanding about the whole thing.

I absolutely agree :)
By "argument" I meant something like "reason". It's just that no more precise words happened to pop into my mind.
This i quite a post, I'll reply as soon as I have time!

Ok, somehow trying to respond to this feels really tiring, so let me say this:

You have shown me that deleting words doesn't have to be as bad as I thought.
I personally still like normal-letter-rapid-fire better.
That being said, I guess i could live with word-deletion-rapid-fire and get used to it.

Also, please don't change right -> center to skip over whole words. Keep it at a character-rapid-fire.

Regarding URLs, I think that "whole word" deletion should recognize words as a group of characters surrounded by any of these characters: *?_-.[]~=&;!#$&(){}<>/\.

This is a really basic (common) thing in keyboards and it's absolutely essential should word-deletion-rapid-fire be implemented.

After reading through all the comments I believe the topic of word deletion is a lot more complicated then I originally thought.
So here is my current opinion :

Current 'character deletion' is pretty solid.
Longer continuous deletion is handeled pretty nicely with selection. It is really precise as you can fine tune selection before hitting delete.
Few folks are interested in word deletion and since the feature is pretty standard in available keyboards the feature can be turned off by default and users can have a choice to turn it on.

Also, I believe that this feature is not really a high priority and maybe we can table it for now.

Also, I believe that this feature is not really a high priority and maybe we can table it for now.

I agree, i think that other issues (language-specific-layouts) are way more important.

Few folks are interested in word deletion and since the feature is pretty standard in available keyboards the feature can be turned off by default and users can have a choice to turn it on.

I love the idea of being able to choose which one to use upon a long-press.

Ok, somehow trying to respond to this feels really tiring

Sorry for the wall of text. I'll try keeping it shorter from now on.

Also, I believe that this feature is not really a high priority and maybe we can table it for now.

Agreed. Let's focus on other issues first.

Few folks are interested in word deletion and since the feature is pretty standard in available keyboards the feature can be turned off by default and users can have a choice to turn it on.

That sounds like a good compromise.

Sorry for the wall of text. I'll try keeping it shorter from now on.

No worries, I tend do this myself. (I mean, just look at the monsters I created in "research diacritics".  ;)

Actually, I think I'm fine with word deletion instead of character deletion.  :)

On PC we can delete words by holding ctrl (option on mac) and tapping backspace.
Could the same be implemented in 8vim, tap ctrl and then backspace to delete the previous word?
I've long been thinking that 8vim should have a way to hold down ctrl for navigating by words and I made an issue about this: #333
Deleting by words would be another good use for this. Tapping ctrl twice to "lock" it and then use backspace to delete by words instead of by letters.

I'm against a new keymap, because it can break existing custom maps. I'm all for having a setting that allows me to specify the behavior, so I can decide on my own what behavior I prefer, because I would prefer the old behavior as well.

Having a ctrl button (working like shift) might be a good idea. if ctrl + backspace = word deletion, otherwise by letters.
Also, that button could control the cursor movement.  ctrl + left = left selection, otherwise move the cursor to the left.
Also, we could add a new setting controlling the behaviour?

there should be an option to restore the ctrl button in place of the new clipboard thing, as it was previously.
I dont understand why it was removed, I used it to move by words all the time.
and yes, an option to activate word deletion would be amazing 👍

@levigutt In PR #403 I've added a new option (default to character by character) to control how the cursor should move.
It's always possible to toggle from the keyboard.
Shift now can select the text when the cursor moves
output.webm

this looks amazing!!! 😊👍

New feature available in the latest RC: https://github.com/8VIM/8VIM/releases/tag/v0.15.0-rc.16


Enhancement: Other XPath features you'd like to see

Apex-XPath supports a simple core of XPath 1.0 syntax. I think it occupies the sweet spot between simplicity and comprehensiveness. It's simple enough to cover maybe 95% of your use cases directly. For the other 5%, Apex-XPath takes you close enough that you can finish filtering the results with minimal effort by using the standard Dom.Document & XmlNode classes.
So far it has covered 100% of my use cases, but I want to know if there are any features of XPath you've found yourself wishing it would support directly. Is there anything we could add to it that would greatly simplify your projects? Or should we keep the library nice & simple, and anything more would just give us diminshing returns of needless complexity?

Hi @JenniferSimonds,
I imagine you have left this behind at this point, but would appreciate a quick thought from you about how easy adding count (https://developer.mozilla.org/en-US/docs/Web/XPath/Functions/count) would be. We would do the work.
Thanks,
Keith

Hi @KeithClarke ,
I had decided not to add support for parsing XPath functions, since I've never had to use them myself.
For getting a count of results, since the methods return a list of XmlNodes, have you considered taking the size() of the result? Like this:
String xml = '---my xml source---';
XPath xp = new XPath(xml);
Dom.XmlNode root = xp.doc.getRootElement();
Dom.XmlNode[] nodes = xp.find(xp.root, '/a/b');

Integer count = nodes.size();

Hi @JenniferSimonds,
Thanks for getting back to me on this. I did play around with the count approach you mention. In the end I went for a simpler solution vthan XPath syntax: was great for engineers but tough for the intended configuration people.
Thanks again,
Keith


Promoting Teamnado 3886 and 3999 to main-stable

Codecov Report

Merging #47 (8ef20cd) into main-stable (ffeafca) will not change coverage.
The diff coverage is 100.00%.

:exclamation: Current head 8ef20cd differs from pull request most recent head 2687fee. Consider uploading reports for the commit 2687fee to get more accurate results

@@             Coverage Diff              @@
##           main-stable      #47   +/-   ##
============================================
  Coverage        95.82%   95.82%
============================================
  Files               32       32
  Lines              407      407
  Branches            96       96
============================================
  Hits               390      390
  Misses              14       14
  Partials             3        3

Impacted Files
Coverage Δ

src/hooks/useProducts.ts
92.85% <ø> (ø)

src/pages/DetailsPage/DetailsPage.tsx
100.00% <100.00%> (ø)

src/utilities/factories/product.ts
100.00% <100.00%> (ø)

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


Create cublas handle failed

Environment info
Operating System:
Ubuntu， cuda8.0
MXNet commit hash (git rev-parse HEAD):
e05129774e76206fe890b511c346953107b05fce
python2.7
Error Message:
Please paste the full error message, including stack trace.
incubator-mxnet/mshadow/mshadow/./stream_gpu-inl.h:115: Check failed: err == CUBLAS_STATUS_SUCCESS (1 vs. 0)
Minimum reproducible example
if you are using your own code, please provide a short script that reproduces the error.
ctx=mx.gpu(0)
doc_net = models.Inception3(classes=2)
doc_net.collect_params().initialize(mx.init.Xavier(magnitude=2.24), ctx=ctx,verbose=True)

I have also encountered this problem, when upgrading driver for 375.26 to 378.13.


Can we add a picture in this dialogue?

Make sure these boxes are checked before submitting your issue - thank you!

[ ] Check in the issue tracker whether
this issue wasn't already reported.
[ ] If it's a bug report check that clear steps to reproduce,
stacktrace, expected behaviour and other needed details are provided.
[ ] Feature requests contain a description of the feature
you're requesting as well as a brief scenario explaining
under what circumstances this might be useful.

Hi @saadbzu
Unfortunately there is no such option

Hi @pglebocki
Thank you for Help. I have one more question. How i dismiss the dialog when NegativeButton "Cancel" Click. I tried this: dialog.dismiss(); but it cannot sport "dismiss()".

Dismiss should be done inside dialog. I don't think that You need to call anything.
Please check app samples.


📄 Added MIT license

Codecov Report

Merging #22 into master will increase coverage by 0.72%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master      #22      +/-   ##
==========================================
+ Coverage   98.61%   99.33%   +0.72%
==========================================
  Files           3        3
  Lines         144      150       +6
  Branches       17       17
==========================================
+ Hits          142      149       +7
+ Partials        2        1       -1


gitlab: 12.8.9 -> 12.8.10

Motivation for this change
https://about.gitlab.com/releases/2020/04/30/security-release-12-10-2-released/
Things done

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

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

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

@GrahamcOfBorg test gitlab

Why does this have two commits with the same description?

Why does this have two commits with the same description?

It doesn't. It's Gitaly and GitLab.

Oh I see it now.

Looks good! Thanks!


Trying to use useState and update  custom props

Hi!
I'm trying to update state inside a singe-spa component that have a Parcel inside and replicate value to this Parcel custom prop:
This is a root.component (that include a Parcel Component)
const users = [
  { id: 1, name: 'Maria' },
  { id: 2, name: 'João' }
];

export default function Root(props) {
  const [user, setUser] = useState(users[0]);
  return (
    <StyledPage>
      <Menu />
      <div>
        <button onClick={() => { setUser(users[1]); }}>
          Change user
        </button>
        <Parcel
          mountParcel={singleSpa.mountParcel}
          config={() => System.import('@sciotta/userInfo')}
          wrapWith="div"
          user={user.name}
        />
      </div>
    </StyledPage>
  );
}

This is a Parcel (@sciotta/userInfo) declaration:
const lifecycles = singleSpaReact({
  React,
  ReactDOM,
loadRootComponent: (props) => new Promise((resolve, reject) => {
  resolve(() => <MyComponent {...props}/>);
}),
  errorBoundary(err, info, props) {
    return null;
  },
});

export const { bootstrap, mount, unmount } = lifecycles;

But loadRootComponent trigger once. How can I "force" child updating?

Hi @thiagog3, you should use rootComponent instead of loadRootComponent here.
const lifecycles = singleSpaReact({
  React,
  ReactDOM,
  rootComponent: (props) => <MyComponent {...props}/>,
  errorBoundary(err, info, props) {
    return null;
  },
});

export const { bootstrap, mount, unmount } = lifecycles;

The reason is that loadRootComponent is called once to download the code for the root component, but in this case you are not downloading the code for MyComponent so it's not needed. In using loadRootComponent you also have some bugs in how you returned the promise and are using the props.

@joeldenning I have been tried rootComponent before using loadRootComponent but is in the same issue.
The component  maintain the same original value. Something is very weird because I know Parcel (React Component) have componentDidUpdate on it.

Here's a code sandbox that shows that updates to the parcel work: https://codesandbox.io/s/dazzling-jackson-lmudo?file=/index.html.
Perhaps you could share a repository demonstrating the issue? That would help in diagnosing.

Closing due to inactivity

I'm dealing with the same problem. Can you reopen it?
My parcel export
import React from 'react';
import ReactDOMClient from 'react-dom/client';
import { Table as rootComponent } from './Table.view';

import singleSpaReact from 'single-spa-react';

export const { bootstrap, mount, unmount } = singleSpaReact({
  React,
  ReactDOMClient,
  rootComponent,
  errorBoundary(err, info, props) {
    return null;
  },
});

My parcel implementation
      <Parcel<TableParcelProps>
          config={config}
          parcelDidMount={() => setTableConfig(true)}
          key={wasChanged}
          columns={columns}
          data={data}
       />

You need to export update prop also
Change from this
export const { bootstrap, mount, unmount } = lifecycles;
To this
export const { bootstrap, mount, unmount, update } = lifecycles;


Added QR & Cholesky factorization

What changes were proposed in this pull request?
https://github.com/deeplearning4j/nd4j/issues/1725
Eigen was not done - it is already implemented in Eigen class
SVD is also already implemented
Added these 2 methods ( + supporting code )
public void geqrf(INDArray A, INDArray R );
public void potrf(INDArray A, boolean lower );
How was this patch tested?
Manual testing - compared to MATLAB
Added LapackTest class for each method
Please review
https://github.com/deeplearning4j/deeplearning4j/blob/master/CONTRIBUTING.md before opening a pull request.

BTW, if it's not possible to figure out some way to use ND4J's indexing, we can do manual loops pretty fast in Java with JavaCPP's indexers: http://bytedeco.org/news/2014/12/23/third-release/
This even works with the CUDA backend -- as long as we modify the array before it gets used by the ops, for example:
https://github.com/deeplearning4j/DataVec/blob/master/datavec-data/datavec-data-image/src/main/java/org/datavec/image/loader/NativeImageLoader.java#L276
Obviously this doesn't work on video memory, so if we need to go there, we'll need to modify libnd4j...

Pls review the proposed change - to remove asNioFloat() - using AddressPointer
https://github.com/rcorbish/nd4j/blob/master/nd4j-backends/nd4j-backend-impls/nd4j-native/src/main/java/org/nd4j/linalg/cpu/nativecpu/blas/CpuLapack.java

Hi @rcorbish and thanks a lot for this contribution. Once you're done adding commits, you can run mvn formatter:format at the root of the repo and commit the result. It will format your code according to our standard.

I can't figure out how to use INDArrayIndex to get a triangular array from the root.
Added @test \to missing test cases
Will get the formatting done
Will check on dups where not necessary

@rcorbish I'm not sure it's possible, we might have to enhance libnd4j for that. If it's just for moving data around though, JavaCPP's indexer are fast enough.

@huitseeker - loks like all formatting was bypassed:
Ran this from the nd4j directory
--- formatter-maven-plugin:2.0.0:format (default-cli) @ nd4j ---
[INFO] Using 'UTF-8' encoding to format source files.
[INFO] Number of files to be formatted: 342
[INFO] Successfully formatted:          0 file(s)
[INFO] Fail to format:                  0 file(s)
[INFO] Skipped:                         342 file(s)
[INFO] Read only skipped:               0 file(s)
[INFO] Approximate time taken:          2s

@saudet the indexing is to zero out the unused entries in a triangular matrix (esp. L'L decomp ). I might ask to leave it the way it is now and create a special indexer to extract upper/lower triangles

@rcorbish I'd be fine with that. Just get the formatting in place for now and we'll call it a day here.

Mind cleaning up the conflicts?


Investigates discrepancies

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (e31f25e) 84.23% compared to head (1aeeeec) 84.23%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #146   +/-   ##
=======================================
  Coverage   84.23%   84.23%
=======================================
  Files          56       56
  Lines        7020     7020
=======================================
  Hits         5913     5913
  Misses       1107     1107

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Allow file and directory names to contain percent character

This is a quick fix for #1137
EscapePound could be expanded to full blown url_encode probably using URL from net/url but I'm not sure how this will affect performance as it's a fairly frequently used function in templates.
Speaking of templates, every href attribute has to use EscapePound on user generated content i.e. various names (repo, user, directory, file) or risk invalid links.

Thanks!


Remove X-Powered-By: React/alpha or make optional

For security reasons, among others, we should remove the X-Powered-By header.

I'm in favor of this by passing an option array to the Server which passes a default headers array into the Response constructor. Any opinions on this @jsor @clue @cboden?

I agree that we should add an option to turn this off (though I'm not considering this to be security feature) :+1:

:+1:

I stumbled upon this while preparing a fix for #51.
You can actually omit sending the X-Powered-By header by explicitly setting an empty header value like this:
$response->writeHead(200, array('X-Powered-By' => array()));

I believe this should answer this ticket, but I'll leave this open until I've filed my upcoming PR that adds some documentation for this :+1:

It's a form of information disclosure and should be off by default.

This is now documented behavior via #107, do you feel this needs to changes further?
FWIW, PHP also exposes a similar header by default, unless otherwise configured: http://php.net/manual/en/ini.core.php#ini.expose-php

@clue tbh I agree with @andyfleming here, we're disclosing information we probably shouldn't from a security perspective. I know PHP, Nginx, Apache, Varnish etc etc all expose that but I won't consider that a good security practice. And while we're making breaking changes for 0.5.0 and 0.6.0 I wouldn't mind fixing this.

Most (if not all) of those have options to turn off the powered by header. It's a recommended best practice to not expose the service and version. It's to avoid revealing that a server is running an vulnerable (unpatched) version of a service.

Most (if not all) of those have options to turn off the powered by header.

So does this component?
I'm really not saying I disagree here, but what do you suggest? Can you file a PR that addresses the issue you're seeing? Thanks!
@WyriHaximus Sounds like a reasonable plan! I suppose we'll likely have to resolve this once #28 lands anyway, because creating the response object will likely be left up to the user anyway, so there's little chance for us to add any "default headers".

I'm not seeing any issue, per se, just suggesting we be Secure by Default.
It's not a big deal at all. Just advocating for best practices.

@clue agreed, all they have to do is return a response anyway after #28 landed. No need for us to provide that anymore :smile:

Any unhandled exception will still result in error 500 + revealed X-Powered-By. It must be secure by default without crutches.

Unhandled exception may still result in error 500 + revealed X-Powered-By. It must be secure by default without crutches.

@ethernidee I'm open for a PR that respects the expose_php ini setting like we done at several other places


[Bug] Paths generated by Markdown compiler are not relative

They are assumed to exist directly in the root directory.
There, the markdown compiler correctly replaces the relative paths.
For example, foo.png is replaced with /user/repo/raw/foo.png.
But if you have the same markdown file, e.g. in the subdirectory md, the path stays example.com/user/repo/raw/foo.png, even though it should be /foo/bar/raw/md/foo.png.

Not reproduced at develop branch.
![Logo](logo.png)

![Logo](m/logo.png)

works fine

Not reproduced

@makhov See here: https://try.gogs.io/da-kid/markdown So I think, you can reopen it.

Ok, I understood. You suggest, that relative path should work not from repo root, but from the file really is relative to the directory, which contains the readme file.
For example:
asd
 |-img/
   |-1.jpg
 |-README2.md
README.md

You guess, that img/1.jpg in README2.md should works (really, works asd/img/1.jpg).
I'm will be agree with you in any other project, but here I'm not sure.
I think, we should to hear @lunny, @tboerger and @fuxiaohei mentions.

Have you tried ./img/foo.png as a path?

I have tried it with latest develop version now. I think we should link relativ images without the requirement to write the full path.

That's what I wanted, yes.


Question: What is the difference between OTP, MFA and Verification?

I would like to know the different between the OTP, MFA and Verification because I'm going to be setting up registration and auth as mobile, not email.
Can Verification be and OTP?
Isn't MFA not needed if I allow users to login only via an OTP to their mobile device?
I would appreciate any answers to this question :) Thanks!

@jtruter7777 Please don't spam! The Q&A discussion is the better place for this type of posts. If someone can assist you then they will answer, I personally don't understand what do you mean and I can't help you.
https://github.com/pocketbase/pocketbase/discussions/5770

apologies, thanks for moving this.


[Tip] [Linux] The the app icon themed

OS: Manjaro Linux / Ubuntu 17.10
Issue Description: In order to get the icon themed, we can fool the icon theme into thinking the app is actually the Google Play Music Chrome extension, which is themed by several icon themes (Arc-Maia on Manjaro, Papirus too).
Steps to Reproduce: On an editor with root privileges:

Edit /usr/share/applications/gpmdp.desktop
Replace the value of the 'Icon' key with chrome-fahmaaghhglfmonjliepjlchgpgfmobi-Default (the chrome extension icon 'name')

Example edited .desktop file:
[Desktop Entry]
Name=Google Play Music Desktop Player
Comment=An electron wrapper for Google Play Music
GenericName=Google Play Music Desktop Player
Exec=gpmdp %U
Icon=chrome-fahmaaghhglfmonjliepjlchgpgfmobi-Default
Type=Application
StartupNotify=true
Categories=AudioVideo;Player;Audio;
StartupWMClass=Google Play Music Desktop Player

Sorry if this doesn't belong here, but I thought some might appreciate this little tip on getting the GPM icon to fit in with their theme.

See #2890


Eroor with symfony 3.1 and symfony 3.2

Tagged form type extension must have the extended type configured using the extended_type/extended-type attribute, none was configured for the "snowcap_im.form_extension" service.

@Moinax
this problem make a exception under symfony 3.1 and 3.2:
Script Sensio\Bundle\DistributionBundle\Composer\ScriptHandler::clearCache handling the post-update-cmd event terminated with an exception

  [RuntimeException]
  An error occurred when executing the "'cache:clear --no-warmup'" command:
  PHP Fatal error:  Uncaught Symfony\Component\DependencyInjection\Exception\InvalidArgumentException: Tagged form type extension must have the extended type configured using the extended_type/extended-type a
  ttribute, none was configured for the "snowcap_im.form_extension" service. in /var/www/html/vendor/symfony/symfony/src/Symfony/Bundle/FrameworkBundle/DependencyInjection/Compiler/FormPass.php:65
  Stack trace:
  #0 /var/www/html/vendor/symfony/symfony/src/Symfony/Component/DependencyInjection/Compiler/Compiler.php(120): Symfony\Bundle\FrameworkBundle\DependencyInjection\Compiler\FormPass->process(Object(Symfony\Com
  ponent\DependencyInjection\ContainerBuilder))
  #1 /var/www/html/vendor/symfony/symfony/src/Symfony/Component/DependencyInjection/ContainerBuilder.php(565): Symfony\Component\DependencyInjection\Compiler\Compiler->compile(Object(Symfony\Component\Depende
  ncyInjection\ContainerBuilder))
  #2 /var/www/html/vendor/symfony/symfony/src/Symfony/Component/HttpKernel/Kernel.php(484): Symfony\Component\DependencyInjection\ContainerB in /var/www/html/vendor/symfony/symfony/src/Symfony/Bundle/Framewor
  kBundle/DependencyInjection/Compiler/FormPass.php on line 65

in the changelog from symfony find this:

The alias option of the form.type_extension tag is deprecated in favor of
the extended_type/extended-type option.
Before:
<service id="app.type_extension" class="Vendor\Form\Extension\MyTypeExtension">
    <tag name="form.type_extension" alias="text" />
</service>

After:
<service id="app.type_extension" class="Vendor\Form\Extension\MyTypeExtension">
    <tag name="form.type_extension" extended-type="Symfony\Component\Form\Extension\Core\Type\TextType" />
</service>

i have in the moment th following 2 in file Resources/config/services.yml line 46  lines remove...
        tags:
            -  { name: form.type_extension, alias: snowcap_core_image }

But this is definitely not a solution.

Hi @ickbinhier , thank you to make a pull request with the bug fix


Disable save button on edit member modal and refactoring

What type of PR is this? (check applicable) 🚧

[x] ♻ Refactor
[x] ✨ Feature
[ ] 🐛 Bug Fix
[ ] 👷 Optimization
[ ] 📝 Documentation Update
[ ] 🔖 Release
[ ] 🚩 Other

Describe your PR request 🔥
Prevent making a put request if inputs match original member data by disabling button and remove repetitive timestamp variable.

Related Issues 🩹
Resolves #63
Closes #63

Very handy tweak. Thank you Brandon!


set max extent sample

Description
PR to add a new Kotlin sample "Set max extent" in Maps and Scenes category.
Using this sample, you can limit the view of a map to a particular area.
Links and Data
Sample Epic: runtime/kotlin/issues/1698
What To Review

Review the code to make sure it is easy to follow like other samples on Android
README.md and README.metadata.json files

How to Test
Run the sample on the sample viewer or the repo.

Thanks, for the review @hud10837 and @shubham7109. Merging in v.next


Loading VS Code with Broken TS File Causes Extension Not to Load

Loading VS Code with a TypeScript error in it causes the extension not to load with the error message "Something went wrong while activating React-TS-CSS extension":

Eg. this code, which results in an Identifier expected. error from TypeScript:
// page.tsx
import styles from './page.module.scss';

export default function Login() {
  return <div className={styles.} />; // 💥 "Identifier expected." error (because of the dot without any property)
}

@karlhorky Thanks for reporting this .
This should be an easy fix.
However the extension would work only after the TS errors are cleared.

@Viijay-Kr great, thanks for the quick fix! Testing v1.2.3 now...

Hm, it seems like the error is still there with v1.2.3 - do you think that there is another problem somewhere not solved by #22?

@karlhorky well I couldn't it reproduce it , do you have a different scenario that is breaking it ?

Interesting, now I cannot reproduce anymore either :)
The extension auto-updated itself to 1.3.0, although the changelog doesn't contain any entries for this version...

@karlhorky Thanks for pointing it out. I will update the change log . I missed it .

@karlhorky change log is update now

Great, thanks!


Watch in run mode

I'm now building my API using ncc instead of custom webpack config and it's really nice to skip all the extra boilerplate that I have. But I would like to use it in dev mode too, I'm running ncc run api/index.ts but I'm struggling to have a complete experience with watching the changes.
Is there any support for something like ncc run -w api/index.ts or another way to handle this?
Thanks!

For now we're cautious about introducing watching, because we want to see how fast we can get without it. In other words, watch mode aggressively optimizes for warm situations, and that has made authors a bit 'relaxed' about cold boots, which are also very important.

Understand. I was thinking of using ncc even under development so it would be handy. Is the recommended way to only use ncc to build?

@pontusab I'm using nodemon for watching during development and happy with it fwiw (__dev__.ts is a simple http server)
nodemon --exec 'ncc run' __dev__.ts


[SPARK-34772][TESTS][FOLLOWUP] Disable a test case using Hive 1.2.1 in Java9+ environment

What changes were proposed in this pull request?
This PR aims to disable a new test case using Hive 1.2.1 from Java9+ test environment.
Why are the changes needed?
HIVE-6113 upgraded Datanucleus to 4.x at Hive 2.0. Datanucleus 3.x doesn't support Java9+.
Java 9+ Environment
$ build/sbt "hive/testOnly *.HiveSparkSubmitSuite -- -z SPARK-34772" -Phive
...
[info] *** 1 TEST FAILED ***
[error] Failed: Total 1, Failed 1, Errors 0, Passed 0
[error] Failed tests:
[error] 	org.apache.spark.sql.hive.HiveSparkSubmitSuite
[error] (hive / Test / testOnly) sbt.TestsFailedException: Tests unsuccessful
[error] Total time: 328 s (05:28), completed Mar 21, 2021, 5:32:39 PM

Does this PR introduce any user-facing change?
Fix the UT in Java9+ environment.
How was this patch tested?
Manually.

Thank you for review and approval, @wangyum .
Also, cc @viirya and @attilapiros

Thank you, @maropu !

This is only a test coverage removal in Java9+ environment and I verified this locally as I described in the PR description.
With the two approval, I'll merge this PR. Thanks!

Merged to master/3.1/3.0.

Not very familiar with JDK9 .. thank you ! @dongjoon-hyun

lgtm

Thank you, @ulysses-you , @HyukjinKwon , @viirya .

late +1


How to simulate scratching / dynamic playback head

Hello,
This isn't really an issue, but I was wondering if it is possible to simulate scratching of a record player with AudioKit. Going forward and in reverse based on user input. As for now Im not even sure you can easily switch playing back and forward in AudioKit...
Any tips on documentation to achieve this?
Thnx

Ask that on StackOverflow please. You can post a link to the SO Post in here even after I close this issue.

Ask that on StackOverflow please. You can post a link to the SO Post in here even after I close this issue.

Ok. Here it is:
https://stackoverflow.com/questions/61116485/simulate-dynamic-playback-head-with-audiokit-scratching-tunrtablism


Run passing tests through Miri

I feel it would be nice to be able to run my passing tests through Miri.
I'm not quite sure how the API should look for that, but I could try to implement something if this seems like a reasonable addition. My first thought is to just have a method like .miri_pass(path) that works the same as .pass(path), except using Miri.
Off the top of my head, I can't think of any reason you would want compilation to pass but Miri to fail, so I'm not sure of the need for a failing miri test.
As an extension of this, it would also be nice to be able to run Miri tests for a custom target, mostly as a means to test endian correctness. I'm not sure how trybuild handles custom targets now (if at all) or how realistic this idea is.
Again, if any of this sounds reasonable, I'm willing to work on an implementation.

I think I would prefer not to build this into trybuild. Passing tests can be run via cargo miri test instead, and compile_fail tests don't make sense in miri because they would fail to compile prior to anything miri would do.


Could not find th 'dankeboy36.vscode-arduino-api' extension must be installed.

I have currently installed the 'esp-exception-decoder' on Arduino 2.0.4. When running the IDE, I encounter the following error: 'Could not find the 'dankeboy36.vscode-arduino-api' extension. It must be installed.'
Additionally, when I type 'ESP Exception Decoder: Show Decoder Terminal' in the Command Palette, nothing happens
please help

Thank you for trying the decoder extension.

on Arduino 2.0.4.

To use this feature, you need a more recent version of the Arduino IDE, at least 2.2.0. You can download the latest version from https://www.arduino.cc/en/software. 2.3.2 is the latest as of writing.
https://github.com/arduino/arduino-ide/pull/2110 has been available since Arduino IDE 2.2.0.
I am closing this ticket, but please feel free to ask for help. You can also use the official Arduino forum: https://forum.arduino.cc/c/software/ide-2-x/93.


browse Mode; Invalid Date

i updated caddy to 0.8.3. in browse mode the caddy does not show dates and just print "Invalid Date":

it was ok with v0.8.2 but this fail occurred after update.
the os is debian 8 x64

What browser are you using, and can you please post a line from the HTML output that contains the string <time? (One is enough.)

Firefox 45 and IE11. both have the same issue but Opera is ok and show correctly
<time datetime="2016-03-05 20:32:37+0000">03/05/2016 08:32:37 PM</time>

Thanks for reporting!
ISO 8601 datetime format allows a notation without T as delimiter between date and time, and Z as alias for the numeric timezone +0000. Internet Explorer and Firefox decided to implement a subset of the datetime notation. I've used one that all browsers parse.
Another new safeguard is that we check whether the datetime has been read correctly. If not then the listing will not be localized.
This is the change to the default template (browse accepts templates!) that will be pushed soon:
diff --git a/caddy/setup/browse.go b/caddy/setup/browse.go
index 4d3eaf8..6039480 100644
--- a/caddy/setup/browse.go
+++ b/caddy/setup/browse.go
@@ -385,7 +385,7 @@ footer {
                                                {{- else}}
                                                {{.HumanSize}}
                                                {{- end}}
-                                               <time datetime="{{.HumanModTime "2006-01-02 15:04:05-0700"}}">{{.HumanModTime "01/02/2006 03:04:05 PM"}}</time>
+                                               <time datetime="{{.HumanModTime "2006-01-02T15:04:05Z"}}">{{.HumanModTime "01/02/2006 03:04:05 PM -07:00"}}</time>

                                        {{- end}}

@@ -401,6 +401,12 @@ footer {
                                        return;
                                }
                                var d = new Date(e.getAttribute('datetime'));
+                               if (isNaN(d)) {
+                                       d = new Date(e.textContent);
+                                       if (isNaN(d)) {
+                                               return;
+                                       }
+                               }
                                e.textContent = d.toLocaleString();
                        }
                        var timeList = Array.prototype.slice.call(document.getElementsByTagName("time"));


is your code is about  Why Random Reshuffling Beats Stochastic Gradient Descent

great code thanks
is your code is about
https://arxiv.org/pdf/1510.08560.pdf
Why Random Reshuffling Beats
Stochastic Gradient Descent
do you know other python implementations for RR
for example for sparse big data tabular data regression or
sparse big data tabular data logistic regression (classification ) ?

Sorry for the delay in the reply. The code here was written for a different paper (https://arxiv.org/abs/2006.05988), but it is highly related to the one that you mentioned, in particular, the method (Random Reshuffling) is the same in both papers.
If you're interested in an efficient implementation of RR, you can check https://scikit-learn.org/stable/modules/generated/sklearn.linear_model.SGDClassifier.html
I think you need to provide argument loss="log" to use logistic regression loss. If I'm not mistaken, it's written in a mixture of Python and Cython.
Another option is to use the default data loaders in PyTorch, which typically permute the date. You can find many resources online on how to implement logistic regression in PyTorch. Unfortunately, I can't point to a specific reference.


strip query string from resolved context path

Coverage decreased (-0.1%) to 93.758% when pulling e78e30fe35267e5e1a6ea8c8ba85671fb1df97ab on context-query-regression into 7bc9678411f1b90acdbe162eefd4529ef9834a41 on master.


Webpack is not resolving ~/assets/ for css url

Version
v2.0.0
Reproduction link
https://github.com/laSinteZ/nuxt-assets-url-bug
Steps to reproduce
yarn
yarn dev or yarn generate
What is expected ?
You must see red boxes with ~/assets/ and no boxes with ~assets/
What is actually happening?
~/assets/ is not resolved by a webpack for css url(), but ~assets/ is resolved. for img src both options work.
Additional comments?
https://nuxtjs.org/guide/assets/ states that we should use ~/assets/ to resolve svg modules. However, for  both ~/assets/... and ~assets/... work, while for css's url() only ~assets/... works. Additional url with compiled files: https://dist-lxayhipvve.now.sh

This bug report is available on Nuxt community (#c7790)

From https://github.com/nuxt/nuxt.js/releases:

Due to css-loader upgradation, use ~assets instead of ~/assets for alias in CSS data type, e.g., background: url("~assets/banner.svg")

@P4sca1 my bad. I've missed this one :(


Control plane nodes display provisioned despite desired state not met

What happened:
When setting control plane to 3 nodes, even though the desired state (3 provisioned control plane nodes) has not yet been met, the cluster object has already transitioned to provisioned. This may happen when a control plane node takes longer to provision but the cluster is available.
What you expected to happen:
The cluster object should only transition to provisioned after the desired state (i.e. 3 control plane nodes are ready) are met.
How to reproduce it (as minimally and precisely as possible):
export CONTROL_PLANE_MACHINE_COUNT=3
Anything else we need to know?:
Environment:

CAPOCI version: v0.1.0
Cluster-API version (use clusterctl version): v1.0
Kubernetes version (use kubectl version): v1.22.5
Docker version (use docker info):
OS (e.g. from /etc/os-release):

This is not a bug wrt capoci, https://github.com/kubernetes-sigs/cluster-api/blob/main/internal/controllers/cluster/cluster_controller_phases.go#L53 the cluster is transitioned to provisioned as soon as cluster infra is ready which is infra specified in cluster spec. The Infra is set to ready as soon as cluster controller sets the ready status based on its infra https://github.com/kubernetes-sigs/cluster-api/blob/main/internal/controllers/cluster/cluster_controller_phases.go#L53 .