Windows Defender Trojan:Win32/Zpevdo.B detected in qpdf-10.3.2-bin-msvc32.zip

I am trying to download the qpdf-10.3.2-bin-msvc32.zip release, but I keep getting an error from windows defender saying that it has detected "Trojan:Win32/Zpevdo.B".
Not having the problem with the 64-bit version from 10.3.2, and not having that same problem on 10.3.1.
Any idea why this might be flagging up?

No, I have not seen this with the binary distribution. In the past, some test files in the source distribution would trigger some virus checkers because there were some invalid PDFs in the test suite that matched some signatures. I haven't seen anything like that in the binary distributions. Did you happen to check the signatures or checksums? Where did you download from? The sha256 of that file should be c546b1ba7cff79b55d4b153fcd44a31f86534ead913132a2a4445dfc2875670e.

I downloaded directly from the release page. We have some pretty aggressive new firewall rules at work, I can check some more tomorrow.

Okay, if you find out exactly what's going on, I'd be interested to know in case there's something I can do about it.

It seems to be the fix-qdf.exe file that is causing the flag. There are apparently 15 vendors flagging it as suspicious on virustotal.com - https://www.virustotal.com/gui/file/3f153e9b183d4e75111c0adb78c3590afa006ed14f39a525b1a344dc36c99bc4/detection

@nicolausdewitt This is helpful information. I'm not sure what to do though...I can rebuild and replace that zip file and see if the new version fares any better. Searching around on this, it seems this particular "virus" gets a lot of false positives as do some of the other ones virustotal is reporting. I'll need to educate myself a little more on what, if anything, I can do to prevent this or whether I'm just at the mercy of the antivirus engines. I have never seen virustotal before and don't know whether it's common for certain antivirus engines to be clustered together with false positives. I suspect a lot of packages use similar algorithms or heuristics. I'll have to study this.
In any case, it strikes me as extremely unlikely that there is actually a problem with it, unless something contaminated the build within GitHub actions. If in doubt, you can try one of the other binary distributions (unless you specifically need msvc 32-bit) or build it from source.
I'll try the rebuild thing and see if it helps. I will have to try to find a Windows system to test with, but that should be manageable.

@jberkenbilt I have no doubt it's a false positive, can't see how it wouldn't show up on the other builds from the same source if not. Sadly, I'm also at the mercy of our corporate firewall - the whole IT team got sent an email when I tried to update from version 8.x! :)
Microsoft have a link where you can submit a file you think has been incorrectly classified as malware for windows defender - https://www.microsoft.com/en-us/wdsi/filesubmission
I also noticed on the microsoft defender screenshot sent back from my IT team that it said the exe was unsigned. I noticed these guys (https://github.com/stride3d/stride/issues/285) got the same false positive assessment, and they were saying it was mainly because it was unsigned.
I hope that helps a bit, if there's anything else I can provide let me know!
Thanks for picking this up so quickly, it's appreciated.

Thanks for bringing it to my attention. I saw lots of stuff about the executables being unsigned. I'll have to look into what that means, exactly. I am not a Windows person. I've spent my entire software development life (which goes back over 35 years, before Windows existed) in non-Windows environments and know only enough to make qpdf work decently on that platform. I'll figure out what someone needs to do to be able to sign stuff, and whether whatever that is is available to individuals doing open source software. I'll see if I can reproduce this and get it resolved. Thanks again.

Well qpdf certainly works well on windows as far as my experience goes, so you are definitely doing something right there! :)
It's really easy to get stuff signed in visual studio, you just select a certificate from the store and it signs it with signtool.exe on publish. The more difficult part is getting a valid cert. Most of my stuff is just published internally so we just generate our own certs.
There do seem to be some linux alternatives, these couple of links might help get you a headstart:
This looks like a decent linux version of signtool:
https://github.com/mtrojnar/osslsigncode
It's mentioned on this question on SO:
https://stackoverflow.com/questions/18287960/signing-windows-application-on-linux-based-distros
Sigstore, from the Linux Foundation might be a nice way to get a free dev cert, they don't appear to be live quite yet though.
https://sigstore.dev/what_is_sigstore/
I guess that's all under the assumption that signing it will actually make a difference but who knows. Cheers again, have a nice weekend.

I rebuilt this in GitHub again, and for whatever reason, the new one doesn't fail. I was able to reproduce the error with the old one on my Windows VM. I will replace the zip file with a new one, which I guess I will call qpdf-10.3.2-bin-msvc32-rebuild.zip and will update the signatures, etc. I will also look into signing and submit the false positive. Thanks for all your helpful information.
I'll look into the signing. I do all my existing gpg signing after the fact because I don't want to deal with private keys in CI. I'm not sure it will be needed though or whether it would actually help. I guess I can eventually see if I can sign the one that's generating the alert and see if it helps. We'll see. Anyway, I'll put up the new binary distribution momentarily on github and sourceforge and post to<EMAIL_ADDRESS>when I've done it. I'll leave this open for now as a reminder to look into the signing and so forth.
Thanks again for bringing this to my attention.

You can find a new version at https://github.com/qpdf/qpdf/releases/download/release-qpdf-10.3.2/qpdf-10.3.2-bin-msvc32-rebuild.zip
Hopefully this one works.

Note to self: remaining actions: investigate code signing to decide whether it's something I need to do and, if so, how to do it.

Microsoft has already come back to say that this was in fact a false positive and that the next update of the definitions will not continue to flag this. I'm not sure about the other 14, but at least we got that confirmation.

I'm going to go ahead and close this. I don't think I'm going to go to the trouble of code signing for Microsoft.


Add alternate deck layout for 2+ expansions in play (#647)

Lgtm

you could do this all of the time.  the little number bubbles are great.

you could do this all of the time. the little number bubbles are great.

Let's see what people think first! The main disadvantage is that you can't as easily tell how many cards are in the stack unless you read the number (since the cards are stacked closer together).


Transient dependencies fail silently

a.styl:
@import '../../node_modules/nib/lib/nib/index'; // to simplify the case I import nib manually, although using nib as plugin does the same

html, body, ng-view > div {
    height: 100%;
}

nav {
    background: linear-gradient(top, beige, bisque);
}

b.styl:
@import './a.styl'
nav {
    background-color: aqua;
}

If I compile it with command line stylus the output is OK:
./node_modules/stylus-loader/node_modules/stylus/bin/stylus b.styl

html,
body,
ng-view > div {
  height: 100%;
}
nav {
  background: -webkit-linear-gradient(top, #f5f5dc, #ffe4c4);
  background: -moz-linear-gradient(top, #f5f5dc, #ffe4c4);
  background: -o-linear-gradient(top, #f5f5dc, #ffe4c4);
  background: -ms-linear-gradient(top, #f5f5dc, #ffe4c4);
  background: linear-gradient(to bottom, #f5f5dc, #ffe4c4);
}
nav {
  background-color: #0ff;
}

But if I compile it with webpack:
module.exports = "nav {\n  background-color: #0ff;\n}\n"

It completely ignores @import a.styl statement because it has the @import in it.
If I remove the nib import then it compiles into this:
module.exports = "html,\nbody,\nng-view > div {\n  height: 100%;\n}\nnav {\n  background: linear-gradient(top, #f5f5dc, #ffe4c4);\n}\nnav {\n  background-color: #0ff;\n}\n"

Obviously a.styl got imported properly but I'd like to be able to use nib.
Thanks

Was it fixed?

i'm interested as well for some update on this issue

Hey guys, it feels like this is still an issue in v.1.5.1.


Added getGraphDiameter to ChannelRouter struct

Hi,
I added the graphDiameter method on the ChannelRouter as we discussed. I went for uint8 for diameter and decided to have the default value for uncached values be 0 as oppose to -1.
Let me know what you think
Ladi

Hmmm, the checks are failing, but Im not sure why. Will look into this further later today.

Hmm, the checks are failing but im not sure exactly why. I think  I missed a parenthesis, will look into it later tonight.

Yeah, I know. Roasbeef said to make it uint16. Havent gitten around to updating because Ive been swamped.

Ok, nm. Putting things in a heap isnt helping at all, because you could remove nodes in the graph that lie on the path between a src and dest node, and you wouldnt have any way of knowing that you have to update that path (unless you used some kind of encoding scheme where you knew all paths that were affected by a given node)
Ok, Im gonna work on this this weekend

Coverage decreased (-0.3%) to 73.812% when pulling 566e3f5cae7c12c578f6641acff92a6aee3e4375 on Lldenaurois:master into dc0ab06d9119b97598595dcb9431904197500c69 on lightningnetwork:master.


using ionSideMenus

i see you have something ported for side menus, but could you explain how to replace the required angular directive? Or is that already done?
http://ionicframework.com/docs/api/directive/ionSideMenus/
function ContentController($scope, $ionicSideMenuDelegate) {
  $scope.toggleLeft = function() {
    $ionicSideMenuDelegate.toggleLeft();
  };
}

looks like something needs to be connected to get the scrolling across to work?
is there an example anywhere of these being used? i couldn't see it in the two example apps.

just to recap what i tried:
taking the ionic markup example:

<ion-side-menus>
  <!-- Center content -->
  <ion-side-menu-content ng-controller="ContentController">
  </ion-side-menu-content>

  <!-- Left menu -->
  <ion-side-menu side="left">
  </ion-side-menu>

  <!-- Right menu -->
  <ion-side-menu side="right">
  </ion-side-menu>
</ion-side-menus>

and converting to your Template tags like:
<template name="layout">
  {{#ionBody}}

    {{#ionSideMenus}}

      {{#ionSideMenuContent}}
        side content
      {{#ionSideMenuContent}}

      {{#ionSideMenu side='left'}}
      left
      {{/ionSideMenu }}

      {{#ionSideMenu side='right'}}
      right
      {{/ionSideMenu }}

    {{/ionSideMenus}}

  {{/ionBody}}
</template>

note this is in the apps main layout (no yield yet for content area)
I left the JS alone hoping that maybe this would help that.
however what i see is this:

unless sideMenus are still work in progress?

@dcsan https://github.com/meteoric/demo/blob/master/client/layout.html shows a great example of using the sideMenus code.

@dcsan yeah the demo app has an example, I think you're just missing ionSideMenuContainer.


Update AdaptiveRecyclerView dependency

Update AdaptiveRecyclerView source. Right now dependency loading from Bintray. Need to change it and retrieving from GitHub. More info here.

Not implemented.


Having a problem when syncing schema

Any ideas what? cheers.
$ subql-node -f ./project.yaml --batch-size 30 --db-schema acala_evm --log-level debug --port 4040 --unsafe --unsafe
2022-12-12T18:55:58.973Z <subql-node> WARN UNSAFE MODE IS ENABLED. This is not recommended for most projects and will not be supported by our hosted service
2022-12-12T18:55:59.447Z <indexer> INFO indexer manager start
2022-12-12 18:55:59        REGISTRY: Unknown signed extensions SetEvmOrigin found, treating them as no-effect
2022-12-12T18:55:59.700Z <store> INFO Historical state is disabled
2022-12-12T18:56:00.981Z <store> ERROR Having a problem when syncing schema
Error
    at Query.run (/mnt/fast1/ACALA_DATA/acala/node-v16.15.0-linux-x64/lib/node_modules/@subql/node/node_modules/sequelize/lib/dialects/postgres/query.js:50:25)
    at /mnt/fast1/ACALA_DATA/acala/node-v16.15.0-linux-x64/lib/node_modules/@subql/node/node_modules/sequelize/lib/sequelize.js:313:28
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async Function.sync (/mnt/fast1/ACALA_DATA/acala/node-v16.15.0-linux-x64/lib/node_modules/@subql/node/node_modules/sequelize/lib/model.js:976:11)
    at async Sequelize.sync (/mnt/fast1/ACALA_DATA/acala/node-v16.15.0-linux-x64/lib/node_modules/@subql/node/node_modules/sequelize/lib/sequelize.js:377:9)
    at async StoreService.syncSchema (/mnt/fast1/ACALA_DATA/acala/node-v16.15.0-linux-x64/lib/node_modules/@subql/node/node_modules/@subql/node-core/dist/indexer/store.service.js:204:9)
    at async StoreService.init (/mnt/fast1/ACALA_DATA/acala/node-v16.15.0-linux-x64/lib/node_modules/@subql/node/node_modules/@subql/node-core/dist/indexer/store.service.js:48:13)
    at async ProjectService.initDbSchema (/mnt/fast1/ACALA_DATA/acala/node-v16.15.0-linux-x64/lib/node_modules/@subql/node/dist/indexer/project.service.js:175:9)
    at async ProjectService.init (/mnt/fast1/ACALA_DATA/acala/node-v16.15.0-linux-x64/lib/node_modules/@subql/node/dist/indexer/project.service.js:66:13)
    at async bootstrap (/mnt/fast1/ACALA_DATA/acala/node-v16.15.0-linux-x64/lib/node_modules/@subql/node/dist/main.js:40:9)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

That's it i think - deleted the database, created a new one, and it appears to be working.


[#794] improvement(operator): support delete ShuffleServer pod with Evicted status

What changes were proposed in this pull request?
Support delete ShuffleServer pod with Evicted status
Why are the changes needed?
When ShuffleServer pod is Evicted, we can't delete it.
Fix: #794
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Manual testing

Codecov Report

Merging #795 (7a559a3) into master (567872b) will decrease coverage by 2.69%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master     #795      +/-   ##
============================================
- Coverage     60.67%   57.99%   -2.69%
- Complexity     1901     1927      +26
============================================
  Files           239      276      +37
  Lines         13031    12027    -1004
  Branches       1091     1151      +60
============================================
- Hits           7907     6975     -932
+ Misses         4686     4649      -37
+ Partials        438      403      -35

see 127 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

cloud you add an ut for this change? The related ut should already been there

I have tried but i found it is difficult. Because this operation involves updating the exclude-nodes and checking whether the shuffle server pod can be deleted. I think we need test it by integration test.

cloud you add an ut for this change? The related ut should already been there

I have tried but i found it is difficult. Because this operation involves updating the exclude-nodes and checking whether the shuffle server pod can be deleted. I think we need test it by integration test.

I believe you may extract the status check into a small method and add ut for that small method. You can check how rss_test.go is constructed.

Updated


vopr: disable new storage faults before transitioning to liveness mode

Resolves the failed VOPR seed (./zig/zig build -Drelease -Dvopr-state-machine=testing vopr --<PHONE_NUMBER>0949771184) on main (5378e181bcd5030ceac012ae6cecd428c6b0d3d2). The seed is a false positive, VOPR panics with @panic("block found in core"); since we disable network & process crash faults while transitioning to liveness mode in the VOPR, but storage faults are kept enabled. This PR disables storage faults as well.
This is solved by zeroing storage fault probabilities before transitioning to liveness mode (similar to what we do for network & process faults: https://github.com/tigerbeetle/tigerbeetle/blob/34e85703da17cb9b890c43855453580dfcd74c06/src/vopr.zig#L602-L606)
Additionally, this PR changes restart_replica in vopr.zig such that it doesn't unconditionally enable storage faults. Instead it honors the faulty parameter specified by the caller. Whether storage faults should be enabled/disabled post restart should be at the callers' discretion.

CI failure mystifies me completely. It's clearly unrelated to the changes though


Please release current version to pypy

Hi -- please release the version that depends on pycryptodomex to pypy -- this will solve some nasty deployment issues. The current 1.1.7 version does not include the pycryptodomex change and hance cannot be installed with any other package that requires pycrypto.

Looks like<EMAIL_ADDRESS>was released on 5-Oct.

Done, 1.4.0 is out the door.


The hack has glitched out

I used this hack a few times before but I forgot how to use it a few months back and then quit going online for personal reasons. Recently fixed it and redownloaded the files from scratch. I logged into AJ today and I'm in Aldan all by myself. It says that my buddies are online but I can't go to them because when I click the follow button, it comes with a World Login Error. I went to the server list and they're all unlit and only a few of the many servers are present.
I have no idea whether I did things wrong (I'm very new to coding and files),  if it's to do with the age of the program (out-dated), or if it plainly just doesn't work anymore. I hope I can get a response to this because I'm very confused and loved this program before.

im not really into coding myself but it seems like its just outdated. i think the latest version you can find is here: https://github.com/sxip/jam .  But as i said im not really into coding so i dont how to get it to connect to animal jam. Lol

anyone know how to set the new one up? cause not working for me

I think they took it down.
On Wed, Dec 16, 2020 at 5:58 AM Measurableowl3<EMAIL_ADDRESS>wrote:

anyone know how to set the new one up? cause not working for me
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/zyvexedpyro/jam-master/issues/1#issuecomment-746100577,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APCJU5OCR4EGR7S3P6N3BK3SVCHGZANCNFSM4MBXN4KA
.

I think they took it down.
On Wed, Dec 16, 2020 at 5:58 AM Measurableowl3<EMAIL_ADDRESS>wrote:

anyone know how to set the new one up? cause not working for me
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/zyvexedpyro/jam-master/issues/1#issuecomment-746100577,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APCJU5OCR4EGR7S3P6N3BK3SVCHGZANCNFSM4MBXN4KA
.

it works

i use it in firefox


Maven Support for Repository

Mostly so it can be used with jitpack.io

@tjohns @silvolu @omervk anyone is watching it?

@kroikie will take a look at this, but we won't be able to merge this PR if @omervk doesn't sign our CLA.

Hi @n0mer have you had a chance to sign the CLA.

Should I? That was not my commit.
I can sign, no problem.
-----Original Message-----
From: "Arthur Thompson"<EMAIL_ADDRESS>Sent: 9/9/2015 4:12 PM
To: "google/gcm"<EMAIL_ADDRESS>Cc: "Nikolay Gorylenko"<EMAIL_ADDRESS>Subject: Re: [gcm] Maven Support for Repository (#79)
Hi @n0mer have you had a chance to sign the CLA.
—
Reply to this email directly or view it on GitHub.

@n0mer you can sign it if you want, but yeah we need @omervk to sign it to merge this PR

Hey guys,
Sorry for taking time to reply on this. I've actually made this change during work hours, so I'll have to have my employer sign the CLA. This will only be possible on Wednesday at the earliest since we have a national holiday until then.
Thanks for your patience.

Going over old PRs of mine. I never got approval from this past employer. I doubt this code is even relevant anymore :(


schema_only mode seems to be slow when replicating database with a lot of tables.

There is a debezium configuration parameter schema.history.internal.store.only.captured.tables.ddl which should only include the ddl for the tables listed in the parameter.
But during testing it looks like a lot of time is spent during startup to retrieve the schema for all the tables.
Implementation:
Try to create a database with 15k tables with the configuration variables set in debezium.

The following configuration works in limiting debezium to only snapshot the tables listed in the table.include.list
table.include.list: "sbtest.table1,sbtest.table2,sbtest.table3"
schema.history.internal.store.only.captured.tables.ddl: "true"
schema.history.internal.store.only.captured.databases.ddl: "true"

Before configuration with 15k tables:
[output_before.log](https://github.com/Altinity/clickhouse-sink-connector/files/14749835/output_before.log)

After configuration: limiting to 3 tables:
output.log
[debezium-mysqlconnector-embeddedconnector-change-event-source-coordinator] INFO io.debezium.relational.RelationalSnapshotChangeEventSource - Snapshot step 3 - Locking captured tables [sbtest.table1, sbtest.table2, sbtest.table3]


Add option to finetune models with LoRA

Adds an option to do LoRA finetuning for SD2 and SDXL models.
One can use it by passing the desired lora_rank in the config, like so:
model:
  _target_: diffusion.models.models.stable_diffusion_xl
  clip_qkv: null
  pretrained: true
  lora_rank: 64
  precomputed_latents: false
  encode_latents_in_fp16: true
  fsdp: true
  val_metrics:
  - _target_: torchmetrics.MeanSquaredError
  val_guidance_scales: []
  loss_bins: []

By default this is off, and LoRA will only be used if a lora_rank is set.
To use it with a custom checkpoint, pass the desired load_path to the trainer, and also set
load_weights_only: true
load_strict_model_weights: false

Hmmm... This would be fragile if we start using unet models without attn_processors attribute (is this likely?). What do you think about setting the LoRA parameters to be a part of the ComposerModel in addition to setting it in the unet? Then in train.py, you can specifically check for model.lora_layers
self.lora_layers = make_lora_layers(unet, lora_rank)

Closing this because diffusers API has changed.


Use interconnect names without spaces

Trivial fix - interconnect names must not contain spaces (name="i to o"), else they are interpreted as multiple nets (a compound name containing "i", a net named "to", and a net named "o").

Thank you for sending this! Could you add a "Signed-off-by" line to your commit?
       -s, --signoff
           Add Signed-off-by line by the committer at the end of the commit log message. The meaning of a signoff depends on the project, but it typically certifies that committer has the rights to submit
           this work under the same license and agrees to a Developer Certificate of Origin (see http://developercertificate.org/ for more information).

See https://probot.github.io/apps/dco/ for more info too.


Add examples for auth endpoints

@IanMayo sure, I'll wait for @AbegaM review too.
Btw I added another example for Rows endpoints in Auth mode, please kindly review them as well.

dismissed

Sure @IanMayo , I will check them now

Hello @thevahidal, Thanks for the auth documentation, it looks good,  i have shared some minor fixes in the review, let me know if you have any questions

Hello @thevahidal, I have pushed a commit that fixes the comments i posted here, and i will approve the PR

@IanMayo @AbegaM
Thanks, guys, great teamwork!


[Snyk] Upgrade rehype-stringify from 9.0.3 to 9.0.4

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade rehype-stringify from 9.0.3 to 9.0.4.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 1 version ahead of your current version.
The recommended version was released 8 months ago, on 2023-08-16.

Release notes

Package name: rehype-stringify

9.0.4 - 2023-08-16(release to regenerate and fix types)

9.0.3 - 2022-01-29See<EMAIL_ADDRESS>

    from rehype-stringify GitHub release notes

Commit messages

Package name: rehype-stringify

e97afa1 rehype-stringify: 9.0.4
476d219 rehype-parse: 8.0.5
0782171 Add `rehype-class-names` to list of plugins
7a95a44 Add `rehype-remove-images` to list of plugins
7d0d0e4 Add sponsor
95c7bed Add `rehype-mermaidjs` to list of plugins
bf91abb Fix TypeScript build
29d839f Add `rehype-color-chips` to the list of plugins
44e1760 Add `rehype-sectionize` to list of plugins
864e813 Update `tsconfig.json` to use use node16 module resolution
b9e9b99 Update Actions
09ba3f1 Add `ignore-scripts` to `.npmrc`
c9f3e87 Fix internal types for TS 4.9
f78ef85 Update Node in Actions
04b8377 Update dev-dependencies
98f2170 Add `rehype-extract-meta` to list of plugins
620bb9c Add `rehype-jargon` to list of plugins
842d6ab Add `rehype-slug-custom-id` to list of plugins
8f8454c Add `rehype-lodash-template` to list of plugin
c260d62 Add `rehype-postcss` to list of plugins
ed19943 Add `rehype-ignore` to list of plugins
fdc2395 Fix typo
4740b3d Add `.gitattributes`
2003432 Replace skypack w/ esm.sh

Compare

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

👷 Deploy Preview for boisterous-rugelach-efa48d processing.

Name
Link

🔨 Latest commit
380346ef5ed5d57692c9479ba5cf349f32bb4fab

🔍 Latest deploy log
https://app.netlify.com/sites/boisterous-rugelach-efa48d/deploys/6623fa67bbf9100008975f16


French date + added city info + better embed formatting

Hello, I improved your nice script to display the french formatted date in the embed and added the city via the API :)
Fixed description trailing commas and few spaces as well
I hope someone will find it useful! Thanks

Hi,
Thank you .


Added en_PH unit test folder + AddressTest.php

Added unit test folder and AddressTest.php for en_PH Provider.
Thank you.

That's it, the unused class is now removed.

That's a random build fail again:

Faker\Test\Provider\InternetTest::testIpv4NotLocalNetwork
Failed asserting that '<IP_ADDRESS>' does not match PCRE pattern "/\A1./".

Thanks


MLIL_VAR size vs var size mismatch

Loading the following code into binja
_start:
mov  ebp,esi
test   edi,edi
jz     l1
lea    edi,[rsi-0x1]
l1:
ret

creates an MLIL operation
rdi = zx.q((arg2 - 1).d)

where the arg2 is an MLIL_VAR operation of size 8 but arg2 is a var of type int32_t which has a width of 4. The guessed type comes from the mov ebp, esi instruction.
The MLIL_VAR operation size should match the type width of the src var.

Here the guessed type from mov ebp, edi keeps effecting rdi even after it's been written to as a qword creating an MLIL_VAR size mismatch were the MLIL size is 4 but the var type width is 8:
mov ebp, edi
mov rdi, [rsp-8]
call free
ret

>>> current_mlil[2]
<il: rax = 0x4002c0(rdi)>
>>> current_mlil[2].params[0].operation
<MediumLevelILOperation.MLIL_VAR: 8>
>>> current_mlil[2].params[0].size
4L
>>> current_mlil[2].params[0].src.type.width
8L

The size should be 8.

Here's one that creates a MLIL_SET_VAR with incorrect size:
test edi, edi
jz l1
mov edi, esi
l1:
movsxd rax, edi
ret

>>> current_mlil[3]
<il: arg1 = zx.q(arg2.esi)>
>>> current_mlil[3].operation
<MediumLevelILOperation.MLIL_SET_VAR: 1>
>>> current_mlil[3].size
8L
>>> current_mlil[3].dest.type.width
4L

As of version 2.1 this issue has been resolved.


Bumping Scala version to 2.11.8 to fix SI-9375

This bumps the Scala version to 2.11.8, and removes the workaround we patched in to the java.io.Serialization of Attr objects.
It's not actually listed as being a bug fixed in Scala 2.11.8 due to a JIRA oddity, but the backport commit for it is https://github.com/scala/scala/pull/4757 and I've verified the fix is in the binary from scala-lang.org.

Could you update this PR for latest version of Factorie and update Build.scala (to update the version for sbt)? If all goes well I will happily merge

Sure. The Build.scala in master currently says 1.2, should it say 1.3-SNAPSHOT?

Oops, yes! Thanks for catching that.
On Mon, Apr 25, 2016 at 12:44 PM Adam Pocock<EMAIL_ADDRESS>wrote:

Sure. The Build.scala in master currently says 1.2, should it say
1.3-SNAPSHOT?
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/factorie/factorie/pull/356#issuecomment-214435924

I pushed the merge commit, so it should be good.


ffi no support elelctron 5.0 ?

ffi no support elelctron 5.0 ?
my dependencies is elelctron 5.0 and ffi 2.3.0

please tell me how to do it

I have the same issue, but can't find the solution.

ffi 2.30 doesn't have support for node 12 yet.
There are a few pull requests (e.g https://github.com/node-ffi/node-ffi/pull/544) that add support for node 12, however, until they go through you will need to change your package.json to point to them specifically.
"dependencies": {
    "ffi": "github:lxe/node-ffi#node-12",
    "ref": "github:lxe/ref#node-12",
    "ref-struct": "github:lxe/ref-struct#node-12",
  }

Has anybody found the PR branches to be stable? I'm paranoid about native crashes in my Electron app.

ffi 2.30 doesn't have support for node 12 yet.
There are a few pull requests (e.g #544) that add support for node 12, however, until they go through you will need to change your package.json to point to them specifically.
"dependencies": {
    "ffi": "github:lxe/node-ffi#node-12",
    "ref": "github:lxe/ref#node-12",
    "ref-struct": "github:lxe/ref-struct#node-12",
  }

Thanks very much!

In theory https://github.com/node-ffi-napi/node-ffi-napi  should be more stable since it is based of napi. I was use patched version of this but it broke again on later node versions. Because ffi-napi uses napi I hope it will be more stable over the long haul.

Great! Electron ^6 has issues with 'ref', btw.

The LXE forks didn't work for me at first.
I got errors like these:
c:\users\venryx\appdata\local\node-gyp\cache\12.14.0\include\node\v8.h(3461): note: see declaration of 'v8::Object::G
  et' (compiling source file ..\src\binding.cc)
c:\root\apps\@v\@modules\vdm-automation-v\main\node_modules\nan\nan_object_wrap.h(24): error C2039: 'IsNearDeath': is n
ot a member of 'Nan::Persistent<v8::Object,v8::NonCopyablePersistentTraits<T>>' [C:\Root\Apps\@V\@Modules\vdm-automatio
n-v\Main\node_modules\ref\build\binding.vcxproj]
          with
          [
              T=v8::Object
          ] (compiling source file ..\src\binding.cc)
  c:\root\apps\@v\@modules\vdm-automation-v\main\node_modules\nan\nan.h(1574): note: see declaration of 'Nan::Persisten
  t<v8::Object,v8::NonCopyablePersistentTraits<T>>'
          with
          [
              T=v8::Object
          ] (compiling source file ..\src\binding.cc)
c:\root\apps\@v\@modules\vdm-automation-v\main\node_modules\nan\nan_object_wrap.h(67): warning C4996: 'v8::PersistentBa
se<v8::Object>::MarkIndependent': was declared deprecated (compiling source file ..\src\binding.cc) [C:\Root\Apps\@V\@M
odules\vdm-automation-v\Main\node_modules\ref\build\binding.vcxproj]
  c:\users\venryx\appdata\local\node-gyp\cache\12.14.0\include\node\v8.h(563): note: see declaration of 'v8::Persistent
  Base<v8::Object>::MarkIndependent' (compiling source file ..\src\binding.cc)
c:\root\apps\@v\@modules\vdm-automation-v\main\node_modules\nan\nan_object_wrap.h(124): error C2039: 'IsNearDeath': is
not a member of 'Nan::Persistent<v8::Object,v8::NonCopyablePersistentTraits<T>>' [C:\Root\Apps\@V\@Modules\vdm-automati
on-v\Main\node_modules\ref\build\binding.vcxproj]
          with
          [
              T=v8::Object
          ] (compiling source file ..\src\binding.cc)
  c:\root\apps\@v\@modules\vdm-automation-v\main\node_modules\nan\nan.h(1574): note: see declaration of 'Nan::Persisten
  t<v8::Object,v8::NonCopyablePersistentTraits<T>>'
          with
          [
              T=v8::Object
          ] (compiling source file ..\src\binding.cc)

I was able to install the forked versions correctly by creating an empty folder elsewhere, running npm init (default entries), then running: npm install github:lxe/node-ffi#node-12 github:lxe/ref#node-12 github:lxe/ref-struct#node-12
Then I just copied the contents of its node_modules folder into my actual project's node_modules folder (in one project, replacing contents -- in the other, needed to skip for the overlaps).

I've now switched to just using node-ffi-napi. It works just as well, but is compatible with the latest versions of NodeJS (I'm on Node 14 currently), and is being maintained.
I can understand if @TooTallNate is short on time. But the readme should at least be updated to mention the incompatibility with newer NodeJS versions, and preferably a link to node-ffi-napi as a working alternative (at least until he has time to return).
(Leaving it as it is is causing a lot of wasted time, and frustration, for new users.)


Upgrade Artifactory plugin to fix compatibility issue with latest Gradle version bump

The engine Jenkins build started failing after #3743, the minor Gradle upgrade. At least that's my theory based on logging in Jenkins. With this version bump to the associated Artifactory plugin for Gradle it publishes normally again, at least locally. PR test won't show it (no publish step) so this PR is for doc purposes and will be merged immediately to test the fix in Jenkins.

Uh oh, something went wrong with the build. Need to check on that


formspec issue with WorldEdit

I can't open the WorldEdit formspec anymore, when ts_skins is installed.

Thanks for reporting this bug! it should be fixed now.

Thanks for reporting this bug! it should be fixed now.


On unikernel info page display block device sizes

Currently we display the name and block size, but the total size of the block device is not present. This would require extra query(ies) to albatross

either extra queries, or adjusting the unikernel configuration / unikernel_info command to transport not only the block device name, but as well its size.


Crash when setting font more than 2 times in a draw cycle

When setting the font to draw with love.graphics.print(), if it is set 3 times in a draw cycle, then a crash occurs. The cause of this is unknown, however, it could possibly be a garbage collection issue.
The following code causes a crash:
one = love.graphics.newFont('Vera.ttf', 12)
two = love.graphics.newFont('Vera.ttf', 14)
three = love.graphics.newFont('Vera.ttf', 16)

function love.draw()

	love.graphics.setFont(one)

	love.graphics.print('Test', 0, 0)

	love.graphics.setFont(two)

	love.graphics.print('Test', 25, 25)

	love.graphics.setFont(three)

	love.graphics.print('Test', 50, 50)

end

But commenting out the line with love.graphics.setFont(three) fixes it.
Another thing to note is that LövePotion will continue to work as usual in Citra, but with a spam of memory errors in the console. It doesn't seem to fully crash in Citra.

If it's memory errors in the console, then it does sound like it's a garbage collection issue.

It should be stated, that even just creating fonts (not drawing them) can cause issues.


Points [graphics] in the map display cannot be selected

Current behavior
When points [graphics] are in the map display, either from the Map Point Tool, or an imported CSV, those points cannot be selected with the Select Point tool.
Expected behavior
When points [graphics] are in the map display, either from the Map Point Tool, or an imported CSV, those points can be selected using the Select Point tool. When they are selected using the Select Point tool, the graphic should highlight with the typical green halo, and the coordinate should be highlighted in the list.
Found on ArcGIS Pro 2.3 and 2.4 build 19590 CC build 94
This was also observed with ArcMap 10.3.1 CC build 94
Did not observe on ArcMap with the released version of MT (227) but did observe on ArcGIS Pro even with the released version of Military Tools

This issue was was found while testing issue #586

@saip we would like to discuss if there will be time to bring in this one and #600 for this release.
@lfunkhouser fyi

Tested this with @ljuru . Selecting points in the map is working as expected. Once a point is highlighted though, it cannot be clicked again to unselect it. I would expect that both selecting/unselecting points is part of the way this would operate. @saip are you able to deliver that as part of this issue, or is that a larger effort?

https://solutionsdev.arcgis.com/defense/help/coordinate-conversion/resources/june-2019-coordinate-conversion.htm
https://solutionsdev.arcgis.com/defense/help/military-tools/resources/june-2019-military-tools-for-arcgis.htm
\...\DefenseSolutions\CoordinateConversion\Testing\CTLocalGovTeam-dev\132\
\...\DefenseSolutions\MilitaryToolsforArcGIS\Dev\294\

Tested on MT dev 307 and CC dev 139
Verified on solutionsdev website


Operator class issues

Issues in implementation order:
1 - chop only in one representation at a time
2 - make sure summand operator is not updated in additions
3 - set to None other representations when using add or chop functions in one representation
4 - initialize diagonal representation as sparse

Items 1 and 3 still need to be fixed.


Embed analytics snippet simple

The html generated from ipynb files does not contain the google analytics snippet that pelican kindly embeds in its generated html.
Simple addition to the publishconf.py file, which is executed when using make publish in the pelican directory, to add this snippet to the html files.
There may well be more efficient and elegant ways to achieve this (maybe when the html of the notebook is created).

Checked that viewing the html pages with injected snippets are registered on google analytics; so this seems functional (at least).

LGTM, I was wondering why the request wasn't going through when I tried testing the generated HTML page with the injected analytics snippet and it was being blocked by ublock origin, so as a heads don't be too surprised if not that much data gets logged as I expect a lot of people use blockers now.

Thanks!


Multiple hyphens not converted to dashes

Ideally, the double hyphen (--) should be rendered as en dash (–), and triple hyphen (---) as em dash (—), just like org-mode already does when exporting to HTML (source).

I had a branch I was getting ready to PR into Hugo this week that fixed this, but it looks like @niklasfasching PR'ed a new org parser, so I'm closing all the issues here, deprecating and archiving goorgeous.


Add at least one other maintainer (bus-factor)

@hjoliver, @dwsutherland, @oliver-sanders, any volunteers?
At the moment I am the only one set as maintainer of the conda package. It is a dependency of our Cylc UI Server feedstock.
I pinged the maintainers of the OSS package, but they were busy with other tasks and haven't volunteered to maintain the feedstock (yet, I expect them to join us later).

I volunteer :raised_hand_with_fingers_splayed:


docs(ansi): fix functional example command

👋  Was playing around with the examples and tried out the functional example from the README, which resulted in an error:
❯ deno run https://deno.land/x/cliffy/examples/ansi/functional.ts
error: Uncaught PermissionDenied: Requires net access to "deno.land", run again with the --allow-net flag
    at deno:core/core.js:86:46
    at unwrapOpResult (deno:core/core.js:106:13)
    at Object.opSync (deno:core/core.js:120:12)
    at opFetch (deno:extensions/fetch/26_fetch.js:43:17)
    at mainFetch (deno:extensions/fetch/26_fetch.js:170:61)
    at deno:extensions/fetch/26_fetch.js:395:7
    at new Promise (<anonymous>)
    at fetch (deno:extensions/fetch/26_fetch.js:357:15)
    at https://deno.land/x/cliffy@v0.19.2/examples/ansi/functional.ts:3:24
❯ deno --version
deno 1.11.4 (release, x86_64-apple-darwin)
v8 9.1.269.35
typescript 4.3.2

I've updated the example to include Deno's --allow-net flag, and now the example works as expected.

Thx @macklinu!
LGTM


Small cmd refactoring to use the same cli helper as docker/cli

This makes it easier to unit test sub-commands.
This will help us share more code with docker/cli in the near
future.

This also contains some refactoring on packager and render
packages, mainly for input/output handling.
Signed-off-by: Vincent Demeester<EMAIL_ADDRESS>

Sorry for the duplication in comments, GH had some weird bug 🤔


Update .ruby-version to 3.2.2

Upgrades Ruby to 3.2.2. See commits for more details.
This PR should be tested before merge, as per https://docs.publishing.service.gov.uk/manual/ruby.html#update-ruby-version-in-the-relevant-repos.
Trello card: https://trello.com/c/K1grjTiC/3373-upgrade-ruby-versions-to-322-2

I see the following deprecation warning in the test log:
WARNING: MYSQL_OPT_RECONNECT is deprecated and will be removed in a future version.

However, this seems to have been there before the Ruby version bump.
Looking into it more closely, it seems as if the problem lies with the mysql2 gem which sets MYSQL_OPT_RECONNECT to false even if the reconnect option is not specified in database.yml. See this code. Given that others have already raised an issue, I'd assume this will be fixed at least by the time MySQL removes the option altogether. So I don't think any action is required by us for now.

I deployed this branch to integration and clicked around the app a bit. I didn't see any problems with the app's behaviour, I didn't see any spike in errors in the Graphana dashboard, and I didn't see any exceptions reported in Sentry. So I think this is good to merge.


Added Write Support in the PDS3Image.

refs#45

All of the sudden all Python 3 tests are erroring with:
urllib.error.HTTPError: HTTP Error 403: Forbidden

I went back and reran the previously passed v0.3.0 test for 3.5 and it now fails.  Maybe the IP from which the 3+ tests are running is now being blocked by PDS due to repeating requests or something.

We may have to mirror our test data ourselves.

Tasks to be performed in this ticket:

Write tests after adding 'save' support.
I swapped the byte-order in case of 3-band Images. I will fetch the byte order information from the label now and then will swap if its required.

@bvnayak you can ignore these comments until next week, since I know you're studying.
I have a number of concerns with this PR:

save() is implemented in Image but currently only handles saving PDS3 images.  What happens when a user tries to save an Isis cubefile?  Probably not the right thing.  So we can either leave save() up here and raise an exception when an Isis cubefile is being saved or we can move save() down to the PDS3Image class.  This implementation looks pretty PDS3 specific so maybe it should be moved down into pds3image.py.
The overwrite keyword doesn't do what I had intended for it to do.  save() should test to see if a file matching file_to_write  is present, if it is present and overwrite=False then an exception should be raise with the message "File already exists: filename".  ONLY if overwrite=True should the file be overwritten.  The whole point is that save() should never overwrite an existing file without explicit permission.  This can probably be accomplished in the missing else: branch of the if overwrite: test.

Lastly, I've realized that many of our tests for pds3image are implemented incorrectly.  They should be testing image.label and image.data.  They mostly test the convenience properties that should maybe be considered internal and changed to band -> _band.  But at the very least, label values need to be tested explicitly since that's the interface users should be using.  Please modify your new tests here to include tests of image.label and image.data.  I will file another ticket to change the older tests.

Added the write support on the updated master branch. Closing this.


SameDiff: performance profiler

Collecting and printing Op execution stats runtime is easy - we have simple SameDiff listener for this:
https://github.com/KonduitAI/deeplearning4j/pull/42
It would be great to have this output in a format usable by Chrome Tracing:
https://aras-p.info/blog/2017/01/23/Chrome-Tracing-as-Profiler-Frontend/
It's simple JSON, format described here, should be quite easy to implement: https://docs.google.com/document/d/1CvAClvFfyA5R-PhYUmn5OOQtYMH4h6I0nSsKchNAySU/preview

Implemented some time ago.


Why does it add *zoom: 1?

Very interesting project.
My question is why is the output of, say, lost-utility: clearfix adding a *zoom: 1 declaration in there? there are other places where it does that too.
calc() can only be used by IE9+ so it doesn't make sense to me that lost is outputting *zoom rules which are meant to address issues for < IE7.
Thanks!

With the calc polyfill I believe calc works in IE7. Regardless it's good practice to support older browsers if it doesn't hurt anything.


React Native App runs using Metro instead of regular React Native

So I was in the middle of working on my React Native project and received this when I re-ran my project:

The terminal indicated that it was running on Metro. This was extremely weird to me because for half of my project, I had been receiving the usual:

I was fine with this at first until I discovered that I couldn't fast refresh. This meant that when I saved or made changes to my project, it wouldn't reflect on my emulator. Additionally, certain packages that were installed just fine in React Native could not be installed successfully in Metro.
I spent hours troubleshooting and configuring in order to restore React Native to its previous state. I tried clearing cache and node modules, creating a new project, uninstalling React Native globally and even reinstalling npm. They all failed.
Help.

I am struggling with the same problem. did you find a way to fix this?

I am also getting these errors :-

Had the same error too in my original project. What I did was keep the project as is, create a brand new React Native project and put all the code from the old project into the new one. My statement about fast refresh was false. Make sure fast refresh is enabled. Also, with enough trial and error, you can install the packages you need into the project. With enough effort is was able to restore my project in the Metro Bundle.
You CAN develop in this new Metro Bundle. Make sure you run your android/ios folder in their respective IDEs beforehand. The commands for running your code on the emulator are the same (react-native run-android or react-native run-ios). I suggest starting by replacing everything in App.js with a simple hello world, test if the refresh is responsive, and build from there to restore your project.
As for Metro, I'm still going to have to wait and see and communicate more until this matter receives more attention. I'm pretty sure we are not the only ones dealing with this issue. I tried to run RN apps on two other computers, including one which never had npm installed. I still got the same result. As for now, I guess we'll have to deal with Metro being the new way to run projects.

Thanks a lot for your answer notakmihe

I want to get back to android activity from react-native activity using backkey .
MainActivity.java
public class MainActivity extends AppCompatActivity {

Button button;

@Override
protected void onCreate(Bundle savedInstanceState) {
    super.onCreate(savedInstanceState);
    setContentView(R.layout.activity_main);
    button = (Button) findViewById(R.id.button);
    button.setOnClickListener(new View.OnClickListener() {
        @Override
        public void onClick(View v) {
            startRNPage();
        }
    });
}

private void startRNPage() {
    Intent intent = new Intent(this, ReactNativeActivity.class);
    startActivity(intent);
    finish();
}
}

ReactNativeActivity.java
public class ReactNativeActivity extends AppCompatActivity {
private ReactRootView mReactRootView;
private ReactInstanceManager mReactInstanceManager;

@Override
protected void onCreate(Bundle savedInstanceState) {
    super.onCreate(savedInstanceState);
    SoLoader.init(this, false);

    mReactRootView = new ReactRootView(this);
    List<ReactPackage> packages = new PackageList(getApplication()).getPackages();
    // Packages that cannot be autolinked yet can be added manually here, for example:
    // packages.add(new MyReactNativePackage());
    // Remember to include them in `settings.gradle` and `app/build.gradle` too.

    mReactInstanceManager = ReactInstanceManager.builder()
    .setApplication(getApplication())
    .setCurrentActivity(this)
    .setBundleAssetName("index.android.bundle")
    .setJSMainModulePath("index")
    .addPackages(packages)
    .setUseDeveloperSupport(BuildConfig.DEBUG)
    .setInitialLifecycleState(LifecycleState.RESUMED)
    .build();
    // The string here (e.g. "MyReactNativeApp") has to match
    // the string in AppRegistry.registerComponent() in index.js
    mReactRootView.startReactApplication(mReactInstanceManager, "firstpro", null);

    setContentView(mReactRootView);
    }
@Override
public void onBackPressed() {
    if (mReactInstanceManager != null) {
        mReactInstanceManager.onBackPressed();
    } else {
      super.onBackPressed();
    }
}
}

I also tried the following code in ReactNativeActivity.java
public void onBackPressed() {
    if (mReactInstanceManager != null) {
        mReactInstanceManager.onBackPressed();
    } else {
        Intent intent = new Intent(this, MainActivity.class);
        startActivity(intent);
    }
}

If I pressed the back button it didn't get back to android activity.
How can I get back to android activity from react-native activity using backkey?


Could not find socket: /tmp/dwm.sock)

Checklist

[X] I have read the appropriate section in the contributing
guidelines
[ ] I believe this issue is a problem with polybar itself and not a misconfiguration on my part.
[X] I have searched for other open and closed issues that
may have already reported this problem.
[x] I have checked the known issues page for this problem.

Describe the bug
When I launch polybar it just says it can't find the socket /tmp/dwm.sock. My polybar launches fine and all of my modules works fine except the dwm module, so I can't see what tag I am on.
Expected behavior:
I expected it to connect to the socket and showed me the dwm module inside of my polybar.
Actual behavior:
Nothing happens, it just does not show the dwm module.
To Reproduce

...
modules-left = bspwm i3 dwm
...

...
[module/dwm]
type = internal/dwm
format = <label-tags> <label-layout> <label-floating> <label-title>
; Path to dwm socket (default: /tmp/dwm.sock)
; socket-path = /tmp/dwm.sock
...

Polybar Log

error: Disabling module "dwm" (reason: Could not find socket: /tmp/dwm.sock)

Screenshots

Environment:

WM: dwm
Distro: Arch
Output of polybar -vvv:

polybar 3.5.2-94-g6b54ea27

Features: +alsa +curl +dwm +i3 +mpd +network(libnl) +pulseaudio +xkeyboard

X extensions: +randr (+monitors) +composite +xkb +xrm +xcursor

Build type: Release
Compiler: /usr/bin/c++
Compiler flags: -D_FORTIFY_SOURCE=2 -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -Wall -Wextra -Wpedantic -O3 -DNDEBUG
Linker flags: -Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now

I hope somebody can help me out!

I am very sorry for opening this issue... I fixed it by applying the dwm ipc patch manually and now it works great!

I am very sorry for opening this issue... I fixed it by applying the dwm ipc patch manually and now it works great!


[1.12] fix(ci): update cli version for system tests

since we released 1.12, lets use the correct CLI version 👍
Testing

Trade-offs

Dependencies

Screenshots

Looks like it didn't fix the issue


Faster .rank .select

Hello,
This PR follow-up https://github.com/RoaringBitmap/RoaringBitmap/issues/191
The general idea is to cache cardinalities, cumulated through buckets. This yield better performance when doing a lot of .rank and .select operations over a RoaringBitmap which is not written anymore.
Raw performance results (see TestRoaringBitmap_FastRank):
AddOnlyThenSelectOnly FastRankRoaringBitmap=207ms
AddOnlyThenSelectOnly RoaringBitmap=6064ms

AddSelectRemoveAreMixed FastRankRoaringBitmap=1055ms
AddSelectRemoveAreMixed RoaringBitmap=375ms

I am not fully-convinced FastRankRoaringBitmap is a proper naming for this class

Coverage decreased (-0.3%) to 90.168% when pulling c0d3955897960237070f999c30202ba58d2c4ba0 on blasd:FastRankSelect into b257e874cf2205c38d1cbd64719beb518b7c0595 on RoaringBitmap:master.

I changed the way to mark the cardianlity cache as dismissed. It enables re-using the int[] used as cache. The performance seems not improved but it will lower the GC pressure when doing a lot of consecutive .add/.select
AddSelectRemoveAreMixed LargeInts FastRankRoaringBitmap=937ms
AddSelectRemoveAreMixed LargeInts RoaringBitmap=387ms
AddSelectRemoveAreMixed SmallInts FastRankRoaringBitmap=732ms
AddSelectRemoveAreMixed SmallInts RoaringBitmap=625ms
AddOnlyThenSelectOnly FastRankRoaringBitmap=184ms
AddOnlyThenSelectOnly RoaringBitmap=5696ms

Coverage increased (+0.08%) to 90.527% when pulling 8c8caaf7db1c251315ca19227ac19f7bde2b7a0d on blasd:FastRankSelect into b257e874cf2205c38d1cbd64719beb518b7c0595 on RoaringBitmap:master.

@blasd
I understand what you did and why you did it, and I am fine with merging it if you recommend merger. However, I have to ask...
I find it awkward to use a special value located in the first component of the vector to determine whether the cache is valid. It is not entirely intuitive, though it is clear enough.
Couldn't we, more simply, have a boolean flag.
So instead of
highToCumulatedCardinality == null || highToCumulatedCardinality[0] == DISMISSED_MARKER;

just have...
boolean isCacheDismissed;

The downside is that we add about a word of storage to store the boolean value, but that's probably negligible. It may even end up improving performance in that it is cheaper to check one flag than doing an array access.
I don't think it is a big deal, but it is a matter of elegance/simplicity.

Hello,
I am completely fine to rely on a dedicated boolean.
Current implementation extends RoaringBitmap. Then, it does not work with ImmutableRoaringBitmap. It would require much less duplicated code to handle both case (and possibly part of Roaring64NavigableMap) if RoaringArray and PointableRoaringArray shared a common interface (e.g. getContainerAtIndex(int i) ; and the same for Container.getCardinality and MappeableContainer.getCardinality()). These additional interfaces would enable FastRankRoaringBitmap to be a decorator over underlying XXX (XXX being another interfaces as I guess would we not add .getContainerAtIndex to ImmutableBitmapDataProvider).
As these modifications requires many changes to existing interfaces (or changes to existing one), I guess it should be done in a later step.

Coverage increased (+0.08%) to 90.528% when pulling 9b706580222bb085072a84a70d653c448ac095ee on blasd:FastRankSelect into 19d6fd6acacc91657aaea3dbbb1d7ac8a3e24b28 on RoaringBitmap:master.

Ok. So let us be clear: you recommend as-is merge and release... but you’ll consider improvements later.
Is that correct?

It can be merged as-is. I am not fully satisfied with the naming but if you
are ok with it, we are good to go.
I am also ready to try to implement the suggested improvments (soon enough
to differ merging) but I need your feeling about it. Anyway, even if you
are ok with the suggested refactoring, it may be preferable to do first an
intermediate (but still functional) release.
Le 13 déc. 2017 2:05 PM, "Daniel Lemire"<EMAIL_ADDRESS>a
écrit :
Ok. So let us be clear: you recommend as-is merge and release... but you’ll
consider improvements later.
Is that correct?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/RoaringBitmap/RoaringBitmap/pull/192#issuecomment-351385282,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACBRF93Wt0z5nU_MOR8394EvnHqRL9uVks5s_8twgaJpZM4Q5MBm
.

The introduction of described interfaces seems somewhat related to https://github.com/RoaringBitmap/RoaringBitmap/issues/196, as they may help mixing different Containers implementation inside some HybridRoaringBitmap

I'll merge and release soon.

Merged. Sorry for the delay.


Coordinate systems and transformation matrices

In the dumpData method you calculate viewMatrix and projectionMatrix which is then stored to database along with other snapshot data.
Both are 4x4 matrices, but when I see the values, projection matrix has all elements non-zero, but view matrix has last row [0, 0, 0, 1] in all cases.
And here starts my confusion. View matrix seems like representing rotation and translation in homogenous coordinates, and I do not understand between which coordinates systems it performs the transformation.
Also, I thought projection matrix reduces the dimansion, and projects object on some hyperplane (to space with lower dimension), but since the projection matrix is 4x4 with all elements non-zero, it does not look like performing projection.
Also, I do not understand how exactly does depth in depth matrix exactly relate to coordinate system of the world and how does it relate to viewer coordinate system (from camera's perspective).
I tried to track where do these matrices come from, but I ended here where it seems to me like matrix values are somehow magically being filled without calling any GTA V related function.
I would be glad for any clarification.

So all the transformation matrices are "graphics style" instead of vision style. In graphics we like to keep everything 4x4, since it's (a) better aligned in memory, (b) does not discard any information. The view matrix transforms things from "world space" to "camera space". This is rigid. The projection matrix goes from there to normalized device coordinates, which is some cube, usually with sides of 2 units. The actual transformation into image space (or fragment space) gets done for us on the graphics card.
The reason that all elements are nonzero is because we pull these transforms out of GPU memory before a render call, and GTA sends just one transformation to the GPU, (P * V). We then construct a view matrix based on the camera location as reported by the scripting API and use it to extract just the projection matrix. The nonzero elements come about from floating point precision losses during this process. The nonzero elements (aside from the usual nonzero elements of a projection matrix) should be quite close to zero.
The depth is in NDC space.

Thanks for answers. I am still not sure whether I understood all of it.
What exactly is the device coordinates and how does it differ from the "camera space"?
And I did not get that "with sides of 2 units" means.
So when actual transformation into image space gets done for us on the graphics card, does it mean that it's not possible to calculate it from matrices in the postprocessing, but we need to calculating during the extraction, when GTA V is running, via the native call for transformation?

Device coordinates is the "image space" that a GPU uses, it differs
from what we'd refer to as image space in machine vision in that
it's always the same no matter what the actual framebuffer resolution
you're using is. The graphics hardware deals with mapping these NDC
values to screen space ((0, 0) -> (1920, 1080) for example on a 1080p
monitor). The idea here is that you can change the render resolution by
simply changing how the GPU samples points and how it does the NDC ->
viewport transform.
For a much more clear and thought out explanation I recommend sections
2 through 4 of "Real time Rendering, Third edition" (ISBN 978-1-56881-
424-7)
Charlie
On Wed, 2017-11-29 at 11:39 +0000, Matěj Račinský wrote:

Thanks for answers. I am still not sure whether I understood all of
it.
What exactly is the device coordinates and how does it differ from
the "camera space"?
And I did not get that "with sides of 2 units" means.
So when actual transformation into image space gets done for us on
the graphics card, does it mean that it's not possible to calculate
it from matrices in the postprocessing, but we need to calculating
during the extraction, when GTA V is running, via the native call for
transformation?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

@barcharcraz So, I read these sections you recommented, and tried to transform coordinates from NDC to world coordinates, but with no luck.
If I understand it correctly, in directX NDC, X and Y are in range [-1, 1] and Z is in range [0, 1], inverted.
So, if I have some point in the image I want to project from the image back to the world coordinates, i already have dpeth in NDC, and I transform the X and Y from pixel position to NDC, like this
def pixel_to_normalized(pixel, size):
    p_y, p_x = pixel
    s_y, s_x = size
    return ((2/s_y)*p_y - 1, (2/s_x)*p_x - 1)

that maps from (0, 0), (width, height) to (-1, -1), (1, 1).
Then I have these coordinates [x, y, z] in NDC.
When extending them to homogeneous coordinates, it is [x, y, z, 1].
Then, since the NDC coordinates are obtained by using view and projection matrix, I do the inversion:
vec_camera = np.linalg.inv(proj_matrix) @ np.array([x, y, z, 1])[:, np.newaxis]
vec_world = np.linalg.inv(view_matrix) @ vec_camera
# these matrices are extracted from game using the managed plugin

and according the pipeline described in the Real Time Rendering book, I should have world coordinates now, but I do not.
Am I missing something, or is there need to reconstruct these matrices from camera parameters due to floating proint precision issues?


Code Completion and Linting options menu not working properly.

Issue Report Checklist

[ v ] Searched the issues page for similar reports
[ v ] Read the relevant sections of the Spyder Troubleshooting Guide and followed its advice
[ v ] Reproduced the issue after updating with conda update spyder (or pip, if not using Anaconda)
[ N/A ] Could not reproduce inside jupyter qtconsole (if console-related)
[ v ] Tried basic troubleshooting (if a bug/error)

[ v ] Restarted Spyder
[ v ] Reset preferences with spyder --reset
[ v ] Reinstalled the latest version of Anaconda
[ v ] Tried the other applicable steps from the Troubleshooting Guide

[ v ] Completed the Problem Description, Steps to Reproduce and Version sections below

Problem Description
I tried to work without completions, but changing the options at the preferences menu didn't work properly.

Checking the box "Enable code completion and linting in the editor" makes the menu disappear from Preferences afterwars - had to use spyder --reset to make it reappear.
Clearing Completitions check boxes either has no effect - the completitions menu keeps appearing at the editor - or disables linting.

What steps reproduce the problem?

Open the preferences menu, clear the "enable code completion and linting in the editor", the corresponding submenu will disappear from the preferences menu; In the terminal prompt from which I called the spyder executable, had an warning or error message:

Pruned plugin: outline_explorer
Missing requirement: completions
Restart plugins pruning by REQUIRES check

Even before that, unchecking the Completion boxes in the Completions and Linting submenu made the Linting to stop.

What is the expected output? What do you see instead?
For problem 1), I was expecting the option to be avaialable the Completion and Linting option again;
For problem 2), I was expecting to be able to use code linting without completion.
Paste Traceback/Error Below (if applicable)

PASTE TRACEBACK HERE

Versions

Spyder version: 5.0.5
Python version: 3.7 and 3.8 (Problem happened with both, in two different environments.
 You said

For problem 1), I was expecting the option to be avaialable the Completion and Linting option again;

We're aware of this bug (see issue #15594) and right now we're working to fix it. Unfortunately, it requires a significant overhauling of the way we load and unload plugins in Spyder (see PR 16012), so it'll be available in a couple of months.

For problem 2), I was expecting to be able to use code linting without completion.

You can do that right now by deactivating the option called Show completions on the fly:

That way completions will only appear when you press Tab or Ctrl+Space in the editor. It's not ideal, but it's the best that we can do at the moment.

I'm going to close this as a duplicate of #15594 because it's basically the same problem.

thanks for the reply, and sorry for not finding it among the reported issues. Just as side note, your suggestion of deactivating "Show completions on the fly" didn't work for me, completions kept appearing. But that's ok, I can change the other options in order for now.


Display default method value on the Node

Our methods have lots of default values to make sure that we can try to show a preview once a method is selected in the Component Browser.
However, some of these defaults are not that obvious. To take as an example, let's look at Table.join. The new default to do is to join on the first column of left table and the column with the same name in the right table (if it exists). This is pretty intuitive, but not obvious, so when the user adds the node join to the workspace, they will see that it joins over some column. But the user will not know which one - they need to guess that it is the first one.
Instead, what we can do is make the IDE display that default value on the node itself. Then it will be explicitly visible, for example in the join case - that the merge is done on the first column.
This may pose a challenge to do right, since the default is like:
join : Table -> Join_Kind -> Join_Condition | Text | Vector (Join_Condition | Text) -> ... -> Table
join self right join_kind=Join_Kind.Left_Outer on=[self.column_names.first] ... =

The issue is that on the node, the name self will not be syntactically correct - if I do:
my_table.join other on=[self.columns.first] - that is ill-formed, it should be my_table.join other on=[my_table.columns.first].
Thus, the IDE/engine would need to perform some kind of translation:

either resolve what name the self should be translated to (but that may not always be possible, if I do (t1.zip t2).join t3 on=[self.column_names.first] then self would need to be rewritten into (t1.zip t2) but that is a bit problematic I think (e.g. the potentially costly operation is now computed twice).
compute the result and generate a code representation for it - ideally, we should just compute that in the given context [self.column_names.first] is for example ["My Id"] and display that. The computation is already +- there since that's exactly the same logic as for computing the value of default argument when applying the function. The only issue here is to get a 'code-representation' of that value. However, we've already been chatting with @jdunkerley that this kind of to_code_representation could be useful for some cases. We can implement it like to_display_text and generate automatically for atoms and have implementations for primitive types like Integer, Text, Vector - it does not have to work for all values - just ones that we use as defaults in our methods.

It is also up to discussion if all default values should be displayed like this or if we should be able to select which ones get displayed. I think displaying all may just be simpler.

To illustrate look at:

This is a simple example so we can see that both were joined on X. But with the latter it's just so much clearer what is happening, because we can see the important arguments on the node, not "hidden behind defaults".

I assigned the issue to IDE for now because the SuggestionEntryArgument has an optional defaultValue that can be shown on the node. If anything else is required from the engine, we'll extend the protocol


Added Topological Sort using BFS

Pull Request Type
What kind of change does this PR introduce?
[ ] Solved an issue/task
[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:
What is the current behavior?

Issue Number: [Insert Issue Number (if applicable)]
What is the new behavior?

Other information

@nikohoffren
Kindly review my Pull Request and merge it.


chromedp does not load whole page if the page contains too many javascript-generated elements

What versions are you running?

$ git rev-parse HEAD
ac47d6ba0e04cf60a7c5375fd139a743fe443fe6
$ google chrome version:
Version 73.0.3683.86 (Official Build) (64-bit)
$ go version
go version go1.11.4 darwin/amd64

What did you do?
When trying to navigate to a page that generate a lot of elements using javascript, it is very likely (see further analysis) that chromedp cannot see the generated elements. Here is an example code:
func main() {
	ctx, cancel := chromedp.NewContext(context.Background())
	defer cancel()

	ctx, cancel = context.WithTimeout(ctx, 30*time.Second)
	defer cancel()

	var result string
	err := chromedp.Run(ctx,
		chromedp.Navigate(`https://streamelements.com/shanksy/store`),
		chromedp.WaitReady(`md-card`, chromedp.ByQuery),
		chromedp.Text(`md-card`, &result, chromedp.ByQuery),
	)
	if err != nil {
		panic(err)
	}

	fmt.Println(result)
}

The code simply navigate to https://streamelements.com/shanksy/store and wait for any md-card element to be ready then get text.
What did you expect to see?
Helios Prime SwitchdescriptionMR8 Helios Prime Switch MR8 Helios Prime Switchshopping_basket  4 items leftmonetization_on20000 chat!redeem helios_prime_switchRedeem item (The first item currently for sell on the website)
What did you see instead?
panic: context deadline exceeded

Further analysis
Being doing more test on this and the results are listed below:

There is a chance that the code will success without timing out, sometimes it took me 1 try, sometimes 28 tries, sometimes 183 times. I tested it using this script on my mac: bash i=0 && while ! go run fetch.go; do sleep 1 && (( ++i )) && echo $i; done
Increasing the context timeout to 100s, 200s, 300s does not solve the problem.
If I change url to another streamelement store, say https://streamelements.com/lacari/store, the go code always retrieve the text successfully. It seems like it is because the number of items is less than the one in my go code (49 comparing to 280).

By the way I do not have chromium installed, so I guess the chromedp was running on my google chrome browser.

Is the element you're looking for inside an iframe, by any chance? If so, this is a duplicate of #72, as we lack proper support for iframes currently.

I have the same issue. And no, there is no one iframe on a page.

You have the same issue with the same page? If not, please post a program to reproduce your problem.

go.mod
github.com/chromedp/cdproto v0.0.0-20190407221054-e2ccc0cc2d77
github.com/chromedp/chromedp v0.1.4-0.20190408165214-b481eeac5108

go version go1.12.4 windows/amd64
chrome version 73.0.3683.103

First of all, i checked code snippet of @dynahcatq got the same result.
My code snippet:
func main() {
	for i := 0; i <10; i++ {
		str, err := getLink()
		if err == nil {
			log.Println(str)
			break
		}

		log.Println(err)
	}
}

func getLink() (string, error) {
	ctx, cancel := chromedp.NewContext(
		context.Background(),
		chromedp.WithLogf(log.Printf),
	)
	defer cancel()

	c, cancel := context.WithTimeout(ctx, 30*time.Second)
	defer cancel()

	var links []*cdp.Node
	err := chromedp.Run(c,
		chromedp.Navigate(`https://www.fragrantica.ru/search/?query=Brocard%20Vintage%20Rose%20Water%20Vintage`),
		chromedp.WaitVisible(`//button[text()[contains(., 'Показать больше результатов')]]`),
		chromedp.Nodes(`//div[contains(@class, 'card-section')]/*/a[1]`, &links),
	)

	if err != nil {
		return "", err
	}

	str := ""
	for _, link := range links {
		str = link.AttributeValue("href")
		break
	}

	return str, nil
}

Output
2019/04/17 21:45:14 context deadline exceeded
2019/04/17 21:45:44 context deadline exceeded
2019/04/17 21:46:15 context deadline exceeded
2019/04/17 21:46:45 context deadline exceeded
2019/04/17 21:47:15 context deadline exceeded
2019/04/17 21:47:17 https://www.fragrantica.ru/perfume/Brocard/Rose-Water-Vintage-35501.html

If I decrease timeout to 10 seconds then I get the correct result in the second iteration.

@mvdan I believe that the element (md-card tag) is not inside an iframe based on three observations:

document.getElementsByTagName("iframe")[0].contentWindow.document.getElementsByTagName("md-card") gives an empty HTMLCollection.
The same code I provided worked well sometimes, while most of the time it reached timeout. If it was an iframe issue, the code should always reach timeout.
As I described, the original code that could often hit timeout navigates to https://streamelements.com/shanksy/store; and while I changed the url to https://streamelements.com/lacari/store, it works perfectly fine all the time. Which means that chromedp can always see md-card tag when navigate to the later url. Based on the fact that these two url are all from https://streamelements.com (they are just different store), I believe they generates elements in a same way, thus eliminate the iframe concern.

Thanks all for the details. I'll have a proper look soon.

I have the same problem too.

I had a look, and this is definitely one weird page. It navigates to five frames in total, which seems to trigger some sort of race which results in chromedp never loading the nodes you're after.
I'm not a JS expert, and it doesn't help that the page is very slow to load and has lots of obfuscated JS code. If anyone can reproduce this with a single short HTML file, that would be very appreciated and speed up my debugging.

Ok, after an exhaustive amount of debugging, I finally figured out what's the problem. It is related to child frames (like iframes) after all, but not in the way I was initially suspecting.
The issue is that the page loads a number of child frames before the top frame has finished loading its nodes. chromedp was incorrectly seeing the child frames as the new top-level frames, so the original frame was left behind and we never saw its interesting nodes.
The fix is simple, all the tests pass (including a regression test for this case), so I see no reason to not include this into v0.2.0. Thanks all for the patience.
Also, to clarify - this fix is somewhat related to #72, in that it's a required step to have iframes work well, but it's not a full fix for that issue.

Ok, after an exhaustive amount of debugging

Can confirm. I spent days debugging and only get to the racing part, but have no idea what was causing the race. Really appreciate your effort and the fix @mvdan.


Isam update 21april2023

Contact:
[Sergey Napelenok], U.S. Environmental Protection Agency
Type of code change:
Bug fix
Description of changes:
This fixes several recently identified ISAM issues including:
ISAM is crashing when compiled in debug mode and PM_TOT tagclass is activated. Some logic was added to SA_WRAP_AE to limit calculations when JAEM array contains zero indexes.
AORGCJ is not calculated correctly. AORGCJ is tracked when 'ALL' tagclass is invoked, however, no calculations for this species were added to aqchem. Similarly MGLY is missing from ISAM gas species, but it is a precursor to AORGCJ.
ISAM crashes in debug mode with the 'TAG CLASSES |ALL' configuration.
Ground level PROD/LOSS calculation is incorrect in layer 1.
Summary of Impact:
Should have no impact on CMAQ concentrations. ISAM output now performs calculations as directed when in PM_TOT tagclass mode and more correctly calculates attribution of AORGCJ and both standard and debug compilations. The necessary addition of MGLY to the ISAM species lists may slightly impact ozone chemistry apportionment in some ISAM applications.
Tests conducted:
This PR passes the following build and run checks:
Compilers: Intel, GNU, Portland Group
Compile Mode: Optimized, Debug
Model Scenario: 2016 Southeast U.S. Benchmark
Tests conducted have been on the 2018 benchmark domain and fortran compiler in debug mode. More extensive evaluation was performed for hemispheric EQUATES ISAM application comparing based release version and this update.
Here is a spatial comparison of differences in tags for ATOTIJ and AORGCJ for the new and old code. This shows that the updated code does not always produce higher tag contributions (except for AORGCJ), indicating that the changes to the vdiff code can impact a number of different tags and species. For example, many tags show decreases rather than increases west of India for ATOTIJ, despite the addition of non-zero AORGCJ (note: V54P in the plot labels below is equivalent to BASE):

Finally, this set of plots compares the sum of tags from the two runs not only to each other, but also to the bulk concentrations from the ACONC files from the corresponding runs

This PR passes required tests and is ready to merge. Thank you @sergeynk for this update!


Full Documentation

Document every method and every class.
Update Readme with explanation of each class and mechanism.

In progress.


Option to disable catch all server

What this PR does / why we need it:
For https://github.com/Shopify/edgescale/issues/813
This add the option to disable catch-all server for an ingress controller.
Which issue this PR fixes:
Special notes for your reviewer:
This is open for comment before submitting upstream.
@Shopify/edgescale

@ElvinEfendi what about now? :)

LGTM. Let's make upstream PR and get a final review there as well.

rebased, will submit upstream


bug: Lazy Loading FzF and Leap

Did you check docs and existing issues?

[X] I have read all the lazy.nvim docs
[X] I have searched the existing issues of lazy.nvim
[X] I have searched the exsiting issues of plugins related to this issue

Neovim version (nvim -v)
0.8.0
Operating system/version
MacOS 13.2
Describe the bug
Lazy loading on keys and cmd don't work.
Steps To Reproduce

Press <leader>o to run the command of :Files
Waiting for FzF dialogue box to come out
I see:

E117: Unknown function: fzf#vim#with_preview
E116: Invalid arguments for function fzf#vim#files
Press ENTER or type command to continue

Press "s" to start the motion navigation of Leap.nvim
Nothing

Expected Behavior
I expect to be able to see Fzf and Leap loaded.
Repro
lua/plugins/init.lua:
return {
    {
        'junegunn/fzf.vim',
        dependencies = {
            'junegunn/fzf',
        },
        keys = {
            { '<leader>o', ':Files<CR>', mode = 'n' },
        },
    },
    {
        'ggandor/leap.nvim',
        dependencies = {
            'tpope/vim-repeat',
        },
        keys = {
            { 's', { mode = 'n' } },
        },
    },
}

init.lua:
-- Map leader to space
vim.g.mapleader = ' '

-- For lazy.nvim
local lazypath = vim.fn.stdpath('data') .. '/lazy/lazy.nvim'
if not vim.loop.fs_stat(lazypath) then
    vim.fn.system({
        'git',
        'clone',
        '--filter=blob:none',
        'https://github.com/folke/lazy.nvim.git',
        '--branch=stable', -- latest stable release
        lazypath,
    })
end

vim.opt.rtp:prepend(lazypath)
require('lazy').setup('plugins', {

    defaults = {
        lazy = false,
    },
    concurrency = 5,
    install = {
        colorscheme = { 'everforest' },
    },
    ui = {
        -- a number <1 is a percentage., >1 is a fixed size
        size = { width = 0.8, height = 0.8 },
        wrap = true, -- wrap the lines in the ui
        -- The border to use for the UI window. Accepts same border values as |nvim_open_win()|.
        border = 'none',
        icons = {
            cmd = ' ',
            config = '',
            event = '',
            ft = ' ',
            init = ' ',
            import = ' ',
            keys = ' ',
            lazy = '鈴 ',
            loaded = '●',
            not_loaded = '○',
            plugin = ' ',
            runtime = ' ',
            source = ' ',
            start = '',
            task = '✔ ',
            list = {
                '●',
                '➜',
                '★',
                '‒',
            },
        },
    },
})

---- Fzf stuff
local keymap = vim.api.nvim_set_keymap
keymap('n', '<Leader>o', ':Files<CR>', { noremap = true, silent = true })

-- fzf
-- Files function
vim.api.nvim_create_user_command(
    'Files',
    'call fzf#vim#files(<q-args>, fzf#vim#with_preview(), <bang>0)',
    { bang = true, nargs = '?' }
)

-- Buffers function
vim.api.nvim_create_user_command(
    'Buffers',
    'call fzf#vim#buffers(<q-args>, fzf#vim#with_preview(), <bang>0)',
    { bang = true, nargs = '*' }
)

not sure about fzf
but quite sure you have to call the setup function for leap

leap.nvim unlike its successor doesn't set default keymaps

E117: Unknown function: fzf#vim#with_preview
E116: Invalid arguments for function fzf#vim#files
Press ENTER or type command to continue

Can't reproduce, the error only happens when fzf.vim is not loaded, I read the code for lazy-loading mappings there seems to be no way lazy.nvim didn't try to load the plugin before executing :Files
As this is not the first time it happens which clearly showed you didn't have fzf.vim installed.

fzf is telling you that your user command is wrong. For leap you indeed need to call setup.
Closing this, since this is not a lazy issue

Turns out, you need to put all the Fzf custom mappings before the require('lazy').setup part.
Also, @nullchilly, leap.nvim is the successor of lightspeed,

I suggest you to make more effort into reading the README.md before commenting on issues.

Turns out, you need to put all the Fzf custom mappings before the require('lazy').setup part.

I put your custom mapping after and it still works, probably just undefined behavior.

leap.nvim is the successor of lightspeed

Yes I know, I migrated from lightspeed to leap.. I am just bad at English


Add precommit (#65)

Local make multiversion fails if pre-commit is installed without --allow-missing-config option, but the branches do not have a .pre-commit-config.yaml file.

I don't know what causes the CI using such an old sphinx version, which fails then. Make multiversion from the master works.

the --no-verify option introduced with #96 would also fix this, but the code formats are worth merging too imho.


Documentation uses "percent", means "ratio"

Throughout the documentation are several examples like this:

The size_hint is a tuple of values used by layouts to manage the sizes of their children. It indicates the size relative to the layout’s size instead of an absolute size (in pixels/points/cm/etc). The format is:

`widget.size_hint = (width_percent, height_percent)`

The percent is specified as a floating point number in the range 0-1. For example, 0.5 is 50%, 1 is 100%.

This is a misuse of the term percent, which as its name suggests, is a ratio expressed as a fraction of 100.
A better term is "ratio".
This error threw me for a bit. I acknowledge I am coming from a mathematical background, and perhaps this is clear to others, so I haven't just gone ahead and made the change. I thought I would check it would be approved.

I agree 1%. This should definitely be changed.

Fixed in #6963.


Linking.openURL within Headless JS task will remount the entire app

[x] Review the documentation: https://facebook.github.io/react-native
[x] Search for existing issues: https://github.com/facebook/react-native/issues
[x] Use the latest React Native release: https://github.com/facebook/react-native/releases

Environment
React Native Environment Info:
   System:
     OS: macOS High Sierra 10.13.6
     CPU: x64 Intel(R) Core(TM) i7-4770HQ CPU @ 2.20GHz
     Memory: 38.88 MB / 16.00 GB
     Shell: 5.3 - /bin/zsh
   Binaries:
     Node: 8.9.4 - ~/.nvm/versions/node/v8.9.4/bin/node
     Yarn: 1.3.2 - ~/.nvm/versions/node/v8.9.4/bin/yarn
     npm: 5.6.0 - ~/.nvm/versions/node/v8.9.4/bin/npm
     Watchman: 4.9.0 - /usr/local/bin/watchman
   SDKs:
     iOS SDK:
       Platforms: iOS 11.4, macOS 10.13, tvOS 11.4, watchOS 4.3
     Android SDK:
       Build Tools: 23.0.1, 23.0.3, 25.0.0, 25.0.1, 25.0.2, 26.0.1, 26.0.2, 27.0.2, 27.0.3
       API Levels: 23, 25, 26, 27
   IDEs:
     Android Studio: 3.0 AI-171.4443003
     Xcode: 9.4.1/9F2000 - /usr/bin/xcodebuild
   npmPackages:
     react: 16.3.1 => 16.3.1
     react-native: 0.57.0 => 0.57.0
   npmGlobalPackages:
     react-native-cli: 2.0.1
     react-native-create-library: 3.1.2
     react-native-rename: 2.2.2
     react-native-version-up: 1.0.8

Description
I am starting a Headless JS task when I receive a push notification when the app is in not in foreground. In my Headless JS task I perform some logic and then I will use Linking.openURL('myapp://myapp') to launch the app.
In cases where the app is running in the background, the Linking.openURL will bring the app to foreground, but it will remount the entire app, as if I was launching it for the first time.
This would be fine, as long as the "old" app to be unmounted, but it's as if the "old" app is also running, so all my event listeners and react lifecycle methods run double. As if I was running two instances of the app simultaneously.

I'm not sure how to make a reproduction case for this, @rcidt - is there any chance you can make something simple, it'd make it much easier to diagnose


toNumber() doesn't work as expected in 7.0.0-alpha3

This behaviour has started happening in 7.0.0-alpha3:
const nlp = require('nlp_compromise');
const test = nlp('test one okay').values().toNumber().plaintext();
console.log(test);
// ' 1'

I expected to get test 1 okay but actually got  1.
Perhaps I'm using the new API incorrectly (which is awesome btw) - do let me know! :smile:

hey thanks ben!
yeah, i've been monkeying around with it today/yesterday on the v7 branch.
so .values() should find a subset ('one') and to 'zoom out' you can do .all()
 nlp('test one okay').values().toNumber().all().plaintext();

alternatively, it's mutable, so:
var m= nlp('test one okay')
m.values().toNumber()
m.plaintext();

if that doesn't work, lemme know and I'll fix it today
cheers

Nice one, both those work great - cheers!


Feature Request - Push to remote branch

In our environment, we would like to perform drift detection and ensure that configurations that are present, should be present, and cherry pick those that are. In order to do this, we push changes from the local system to a remote branch and then merge request them back into master branch.
Something along the lines of (pseudocode):
git commit -m "auto"
git push origin master:drift_20201504
git reset --soft HEAD~1
git reset HEAD

Hi @auzroz
Please let me know if I have misunderstood this request, but it sounds like you are trying to get code changes from the repository TO splunk.  Unfortunately this is not possible with this git_for_splunk app as it is designed for one-way  from Splunk TO the repository. This is primarily becuase merge conflicts can occur (becuase Splunk will change files itself) and the app provides no method to resolve these.
the KSconf app  https://github.com/Kintyre/ksconf might be of interest to you
All the best,
Chris

Sorry, I was misunderstood. I am looking at committing changes from Splunk TO the repository, but don't want to commit those changes directly to the remote master branch in the event that introduces unauthorized or breaking changes.

Hmm, OK. As long as this doesn't require user input, then it should be possible.  Unless there is wide demand for such a feature, then it's probably fastest to just fork your own version of this repository and change the code to do what you want. I expect the only file you will need to change is this one: https://github.com/ChrisYounger/git_for_splunk/blob/master/bin/input_module_gitforsplunk.py
That file should hopefully be easy enough to understand. It's just over 100 lines of code.
If you think this is something that many others would benefit from, then please let me know.
All the best :)


fix alphabetical sorting

Closes https://github.com/bitcointranscripts/bitcointranscripts.github.io/issues/45 as an alternative to https://github.com/bitcointranscripts/bitcointranscripts/pull/188 to also keep the date taxonomy
Default sorting in Hugo is defined by
Weight > Date > LinkTitle > FilePath (src)
thus adding dates broke the behavior.
This fixes sorting back to alphabetical

@kouloumos: Why do you want/need the date in the header? I get why you want a speaker field in the header for the Twitter bot but I don't get why you need a date field. The date is already in the file name by default. Unless you need it for something I think it is probably better to make the header a little less crowded and remove the date.

@michaelfolkson The thinking behind that is that having the date as part of the title doesn't offer any more utility. But by adding it in the metadata we could potentially sort by date, display date in other format, etc.
Also the speaker is not only for the twitter bot, by adding the speaker taxonomy, another page has been created at https://btctranscripts.com/speakers/ from which you could see all the talks by a speaker (as soon as we have that metadata for every transcript)

@kouloumos: By having a YYYY-MM-DD at the beginning of the filename an alphanumeric sort of the filenames gives you the files in date order without needing to sort by the date in the header?
If you feel strongly about it, need it for something and have a fix in this PR then I'm ok with it. Just providing pushback so that header doesn't get unnecessarily big and convoluted.

Also the speaker is not only for the twitter bot, by adding the speaker taxonomy, another page has been created at https://btctranscripts.com/speakers/ from which you could see all the talks by a speaker (as soon as we have that metadata for every transcript)

Indeed, agreed. That seems a nice change.

test ACK d232cd2
Let's fix and move on


Teacher Tool: Import and Export Rubric

This change enables exporting rubrics to a file and importing them again. I've tucked the options behind a new "Action Menu", which is just a meatball menu on the right side of the toolbar. I didn't spend a ton of time styling that, just wanted to get something fairly quick working.
I'm not in love with the way the import modal looks. Definitely open to recommendations on how to make that look nicer, but this was as good as I could get it without feedback :)
Screenshots:

Upload Target: https://makecode.microbit.org/app/ef53963093d3ce1b2679fe56fa95bc3497df8e51-cefc5556d6--eval

It's great to get this functionality in, but there's a lot of UI here that needs design. I question the need for the preview.

It's great to get this functionality in, but there's a lot of UI here that needs design. I question the need for the preview.

I really love the preview. I think, like Thomas said, it gives peace of mind to the user.
I'm also thinking that if, in the future, we want to supply pre-built rubrics, we might be able to put them here. There might be a better place for it, but it was something I thought of as I was playing around with this. In a pre-built case, you'd want to show the user a preview before importing.

It's great to get this functionality in, but there's a lot of UI here that needs design. I question the need for the preview.

I really love the preview. I think, like Thomas said, it gives peace of mind to the user.
I'm also thinking that if, in the future, we want to supply pre-built rubrics, we might be able to put them here. There might be a better place for it, but it was something I thought of as I was playing around with this. In a pre-built case, you'd want to show the user a preview before importing.
Edit and sidenote: If we want to talk more about design, can we avoid using GitHub comments? Being that you can't reply in a thread, I find conversations trying to happen with GitHub comments are hard to follow.

I like preview a lot, but it seems like a detail that should come later. If we add it now, we have to make it work well. That is time taken from other areas.
Happy to chat more in the Teacher Tool channel if GitHub isn't working well. I'm also updating in the Figma to represent this idea.


Go To Facebook.com

I see this issue hasn't been solved... so I decided to re-open it.
It appears that the iframe option is not working as you would expect.
It was my understanding that setting this option would fix the issue that occurs when a user logs in to a canvas facebook app they would incorrectly see the "Go to facebook.com" message.
https://skitch.com/peternicholls/rwka9/google-chrome
It looks like iFrame canvas app's are going to become more popular so it may be a good bug to fix?
In production.rb I have:
Rails.application.config.middleware.use OmniAuth::Builder do
provider :facebook, 'abc', 'xxx',  :scope => "publish_stream", :iframe => true
end
Rails 3.0.5
Any ideas?
Comments

I'm using omniauth (0.2.6).
In a recent app, my config/initializers/omniauth.rb looks like this:
Rails.application.config.middleware.use OmniAuth::Builder do
  provider :facebook, ENV['FB_APP_ID'], ENV['FB_APP_SECRET'],
    :iframe => true,
    :scope => "publish_stream,email,user_likes",
    :client_options => { :ssl => { :ca_file => '/usr/lib/ssl/certs/ca-certificates.crt' } }
end

if Rails.env.production?
  OmniAuth.config.full_host = ENV['OMNIAUTH_FULL_HOST']
end

sessions_controller.rb:
class SessionsController < ApplicationController
  def create
    auth = request.env["omniauth.auth"]
    # raise auth.to_yaml
    user = User.find_by_uid(auth["uid"]) || User.create_with_omniauth(auth)
    user.update_attributes(:token => auth["credentials"]["token"])
    session[:user_id] = user.id

    redirect_to Rails.env.production? ? (session[:auth_origin] || new_canvas_profile_path) : new_canvas_profile_path
  end

  def destroy
    session[:user_id] = nil
    redirect_to root_url, :notice => "Signed out!"
  end
end

User#create_with_omniauth
# create user from omniauth hash
#
def self.create_with_omniauth(auth)

  create! do |user|
    user.uid        = auth["uid"]
    user.email      = auth["user_info"]["email"]
    user.first_name = auth["user_info"]["first_name"]
    user.last_name  = auth["user_info"]["last_name"]
    user.image      = auth["user_info"]["image"]
    user.name       = auth["user_info"]["name"]
    user.token      = auth["credentials"]["token"]
    user.gender     = auth["extra"]["user_hash"]["gender"].capitalize
  end

end

With this config can you run your app inside and outside Facebook? Even for the first login inside Facebook when the user authorize the app?

This is for running it inside the Facebook iframe as a canvas application. It basically makes sure that the user is redirected to the canvas url (http://apps.facebook.com/yourappname/) rather than the URL where your app is actually hosted.
If you want to use it outside of the canvas, you just have to remove the Omniauth.config.fullhost line.

Can we set an OmniAuth.config.full_host for each of  the providers we have?
Thanks


importlib.metadata.distributions() doesn't surface all installed packages/endpoints, breaking pytest plugins

I tried to migrate a project to uv, but pytest could no longer find its plugins pytest-cov and pytest-testmon.
$ uvx pytest --testmon
ERROR: usage: pytest [options] [file_or_dir] [file_or_dir] [...]
pytest: error: unrecognized arguments: --testmon

On investigation it seems that pytest uses Pluggy to load the plugins, and Pluggy uses importlib.metadata.distributions() to identify and load installed packages that have entrypoints matching its naming convention (see Pluggy source)
I made an empty project with "uv init", added dependencies [ "pytest", "pytest-cov", "pytest-testmon" ], ran "uv sync" successfully (I can see the installed files in .venv/lib/site-packages) and ran the following code
for dist in list(importlib.metadata.distributions()):
    print("name: ", dist.name)
    for ep in dist.entry_points:
         print("ep: ", ep.name, ep.group)

Under my regular project this code prints (among other things):
name:  pytest-cov
ep:  pytest_cov pytest11
name:  pytest-testmon
ep:  pytest-testmon pytest11

Under my uv test project those modules/endpoints are not in the list, even though they have been successfully installed.
$ uv --version
uv 0.3.0 (dd1934c9c 2024-08-20)

and this is on Win11.

I think the problem you're running into here is that uvx runs in an environment isolated from your project. Can you try uv run pytest instead? Or even uv run --with pytest pytest if it's not part of your project environment?

Some documentation on this at https://docs.astral.sh/uv/concepts/tools/#relationship-to-uv-run
We may be able to improve the documentation though, if you have any questions.

Yes, that's fixed it! Thanks 👍
I think it might have helped if this page here: https://docs.astral.sh/uv/guides/tools/  had a section right at the top clarifying why one would or wouldn't want to run a tool without installing, and pointing to the section on how to run a tool WITH installing (or without installing but with plugins, which is mentioned, but much further down the page).
The info I needed was all there, but I didn't realise it would be relevant when I first read it, and I didn't know where to look for solutions once I ran into the problem.

Addressing that with https://github.com/astral-sh/uv/pull/6454 — let me know if that's not helpful.

That looks spot on 👍


Pass config files as a cmd parameters

when starting Ferrum as application we initialize it as follows:
    app := application.CreateAppWithConfigs("./config.json", "./data.md", "./keyfile")

We should be able to pass only name of the first main config (otherwise use default name - ./config.json)

Will be implemented during #9


Changes to support Neo4j v3

The following changes appear to be necessary to work with Neo4j v3

Coupling.cypher needs parenthesis
Default port is 7474

@markburns sounds good, changed.

Hey thanks


Better CLR interop (for collections).

Better CLR interop.

.NET collections are wrapped in ObjectInstance, which doesn't look like an array to Jurassic.
Added a intermediate dispatch function ClrInstanceWrapper.Create which returns an ArrayInstance or ObjectInstance based on the .NET type.

Support for Nullable<>.

Modified the CLR method generator so that it supports Nullable types.
First it emits a call to HasValue and returns null if it doesn't.
Then it emits a call to GetValue and lets the existing type conversion code run.

Also modified UserDefinedFunction so it shared CompilerOptions with the engine.

Thanks!