Image captions are not applied to images within {% if  %} statements

Using the current gitbook and gitbook-plugin-image-captions images within version {% if  %} seem to be ignored. I didn't try other Templating features, but I gues they won't work either. If needed I can supply a demo gitbook, but it make take some time to prepare ;)

I've found a workaround:
Instead of writing
{% if book.projectName == "One" %}
  ![One](assets/one.png)
{% elif book.projectName == "Two" %}
  ![Two](assets/two.png)
{% endif %}

This one works:
{% if book.projectName == "One" %}

![One](assets/one.png)

{% elif book.projectName == "Two" %}

![Two](assets/two.png)

{% endif %}

I can't judge of this is intended or not, but for me the first example should work too.


Unable to set secrets on a new environment, which causes publish to fail

🐛 Bug Report

Environment

operating system: mac os x 10.13.6
output of rustc -V: n/a (not installed)
output of node -v: v12.1.0
output of wrangler -V: wrangler 1.8.1

Steps to reproduce
The wrangler.toml for the project can be found here: https://github.com/signalnerve/workers-auth0-example/commit/cdc45d2635fc71978aeb308fcb322a3e7d829ec7 (link to commit adding wrangler.toml environment)
What did you expect to see?
I'm able to set secrets and publish a new environment as defined in my wrangler.toml.
What did you see instead?
After defining a new environment in my wrangler.toml, I'm unable to create a new secret using wrangler secret put:
iMac:my-auth-test kristian$ wrangler secret put AUTH0_DOMAIN -e zone
Enter the secret text you'd like assigned to the variable AUTH0_DOMAIN on the script named my-auth-test-zone:
test
🌀  Creating the secret for script name my-auth-test-zone
🌀  Worker my-auth-test-zone doesn't exist in the API yet. Creating a draft Worker so we can create new secret.
Error: Something went wrong! Status: 400 Bad Request, Details {
  "result": null,
  "success": false,
  "errors": [
    {
      "code": 10021,
      "message": "Uncaught ReferenceError: AUTH0_DOMAIN is not defined\n  at line 7\n  at line 1 in n\n  at line 1\n  at line 1\n"
    }
  ],
  "messages": []
}

The accompanying code that is failing is this config object in my code:
const auth0 = {
  domain: AUTH0_DOMAIN,
  clientId: AUTH0_CLIENT_ID,
  clientSecret: AUTH0_CLIENT_SECRET,
  callbackUrl: AUTH0_CALLBACK_URL,
}

Because of this, I'm also unable to run wrangler publish:
iMac:my-auth-test kristian$ wrangler publish -e zone
⬇ Installing wranglerjs...
⬇ Installing wasm-pack...
✨  Built successfully, built project size is 3 KiB.
Error: Something went wrong! Status: 400 Bad Request, Details {
  "result": null,
  "success": false,
  "errors": [
    {
      "code": 10021,
      "message": "Uncaught ReferenceError: AUTH0_DOMAIN is not defined\n  at line 7\n  at line 1 in n\n  at line 1\n  at line 1\n"
    }
  ],
  "messages": []
}

this is fixed now with draft worker uploads

hey @EverlastingBugstopper, did this make it into the 1.9.0 rc? i'm still seeing this error on that version:
auth-runthrough$ wrangler secret put AUTH0_DOMAIN
Enter the secret text you'd like assigned to the variable AUTH0_DOMAIN on the script named auth-runthrough:
dev-tft4si-b.auth0.com
🌀  Creating the secret for script name auth-runthrough
🌀  Worker auth-runthrough doesn't exist in the API yet. Creating a draft Worker so we can create new secret.
Error: Something went wrong! Status: 400 Bad Request, Details {
  "result": null,
  "success": false,
  "errors": [
    {
      "code": 10021,
      "message": "Uncaught ReferenceError: AUTH0_DOMAIN is not defined\n  at line 7\n  at line 1 in t\n  at line 1\n  at line 1\n"
    }
  ],
  "messages": []
}

auth-runthrough$ wrangler --version
👷 ✨  wrangler 1.9.0-rc.0

hmmm... i'm not sure if it made it to the rc, wasn't around when it's cut. It does work on master though
$ wrangler secret put INPUT
Enter the secret text you'd like assigned to the variable INPUT on the script named secret-test:
world!
🌀  Creating the secret for script name secret-test
🌀  Worker secret-test doesn't exist in the API yet. Creating a draft Worker so we can create new secret.
✨  Success! Uploaded secret INPUT.

good to know! i can patch around it for now by doing let AUTH0_DOMAIN, i think by the time this tutorial i'm writing comes out, i won't have to patch it :)

I'm still encountering this on master using the site template.
🚀 ➟ wrangler secret put AUTH0_DOMAIN
Enter the secret text you'd like assigned to the variable AUTH0_DOMAIN on the script named my-auth-example:
inlining.auth0.com
 Creating the secret for script name my-auth-example
 Worker my-auth-example doesn't exist in the API yet. Creating a draft Worker so we can create new secret.
Error: Something went wrong! Status: 400 Bad Request, Details {
  "result": null,
  "success": false,
  "errors": [
    {
      "code": 10021,
      "message": "Uncaught ReferenceError: AUTH0_DOMAIN is not defined\n  at line 7\n  at line 1 in t\n  at line 1\n  at line 1\n"
    }
  ],
  "messages": []
}

@ObsidianMinor - are you on the latest version of Wrangler? (wrangler --version should be 1.9.0)

Yep Wrangler 1.9 through npm

I'm on wrangler 1.10.3 and experiencing this issue

wrangler 1.11.0 here with the same issue.

I'm also having this issue on 1.11.0. I was able to create a secret in the default environment, but not other environments.

Had the same issue, turns out I renamed the project on cloudflare and then tried to publish with the old name, which was creating a new worker on a new worker domain.
Renaming the name in wrangler.toml solved the issue.

Had the same issue, turns out I renamed the project on cloudflare and then tried to publish with the old name, which was creating a new worker on a new worker domain.
Renaming the name in wrangler.toml solved the issue.

Same issue using wrangler 1.13.0
(Work around by first creating a worker with the same name thrue dash UI)

I just ran into this problem again adding new secrets to an existing worker. After bashing my head for a while, I realized that you must add add secrets via the Wrangler CLI. Adding secrets via the web UI results in this problem
Hope that helps someone. Also created #1958 to document

@cloudflare/wrangler considering all the bug reports here, would it be appropriate to re-open this issue? it seems like this may still be a problem w/ wrangler

I just created a new worker for the first time in a while and hit this problem. I don't think the draft worker solution is working - the creation of the draft worker failed for me due to the secret not being defined.
Repro steps:

Deploy worker to new environment for the first time. Note that it fails to due a secret not being defined.
Run wrangler secret put -e new_environment SECRET_NAME to create new secret. Wrangler attempts to create a draft worker but fails due to the secret not being defined.

$ wrangler secret put -e staging ABLY_KEY
Enter the secret text you'd like assigned to the variable ABLY_KEY on the script named worker-staging:
SECRET
🌀  Creating the secret for script name worker-staging
🌀  Worker worker-staging doesn't exist in the API yet. Creating a draft Worker so we can create new secret.
Error: Something went wrong! Status: 400 Bad Request, Details {
  "result": null,
  "success": false,
  "errors": [
    {
      "code": 10021,
      "message": "Uncaught ReferenceError: ABLY_KEY is not defined\n  at line 22\n  at line 1 in r\n  at line 22\n  at line 1 in r\n  at line 22\n  at line 1 in r\n  at line 22\n  at line 1 in r\n  at line 1\n  at line 1\n"
    }
  ],
  "messages": []
}

The workaround of creating a worker with the same name in the web UI does work. Just create it with the hello world example code already defined in the web UI, run wrangler secret put to define your secrets, and then run wrangler publish.

So what do I do in the meantime?
Use the workaround described by jcapogna on Jun 17?

This chicken and egg problem bits every time you add a secret to your code then try to set its value with wrangler secret put. It still happens in 1.19.0. On another is someone suggested always referring to secrets as globalThis.SECRET so that it can be undefined during the publish. This seems like a rough edge on the secrets system that's a common part of the new user experience.

Still having this issue on August 29

We also just hit this issue today as well. Trying to build and deploy a wrangler project that references secrets and uses the wrangler-action to inject the secrets during the github action fail with the same error
[0] Error: Something went wrong with the request to Cloudflare...
[0] Uncaught ReferenceError: SECRET_NAME is not defined

I just faced the same issue:
I had to use @signalnerve solution using let
Example code:
let EMAIL_ACCESS_KEY;
let EMAIL_SECRET_ACCESS_KEY;
const accessKeyId: string = EMAIL_ACCESS_KEY;
const secretAccessKey: string = EMAIL_SECRET_ACCESS_KEY;

The globalThis "workaround" isn't working for me at all.

We were also hit by this. Is there anything we can do to speed up this? Maybe the bug isn't fixed yet because there are no clear repro steps?

@alexandernst This is the workaround...
https://github.com/cloudflare/wrangler/issues/1418#issuecomment-732761146

For anyone struggling with this issue and looking for a workaround with typescript and the "wrangler chicken egg problem" regarding secrets - this worked for me in typescript:

A d.ts file in a typings dir, included via tsconfig (in include paths) with the following content

declare global {

  type GS = typeof globalThis & GlobalSecrets

  interface GlobalSecrets {
    TYPED_SECRET1: string;
    TYPED_SECRET2: string;
  }
}

export {}

Usage within the handlers:
(globalThis as GS).TYPED_SECRET1
Hope this helps anyone...

I'm on wrangler 1.19.8 and experiencing the same issues ,
But somehow i was able to resolve it , by commenting all the SESSION_SECRET from the codes and .env ,
then after success added secret key , i'm restore the SESSION_SECRET to code and push then everything worked fine

I just tried this on Wrangler 2.0.14 and cannot reproduce the problem, so I believe it is fixed.
Please try updating to the latest version of Wrangler:
npm -g uninstall @cloudflare/wrangler
npm -g install wrangler@latest

Confirmed fixed. Thank you @petebacondarwin


Enhance documentation

Refined project documentation and added comments during an in-depth review to map out the project's architecture and component interactions. Open to feedback and further contributions.

A good addition to the docstring would also be to include an example tag (@example) to illustrate the general API/Interaction with what component is been documented.

Could you clarify what you mean by an example tag? If you're suggesting an example of how to use this component, I'm not convinced of its utility. Typically, when I'm navigating new code, my challenge isn't in figuring out how to use a component but in understanding its role within the broader application. In my view, time spent on crafting examples could be better spent on writing detailed comments that aid developers in comprehending the complexities of the code.


Fixed the functionnality of the Carousel (dev)

Aligned the Close button to the right.
Escape keydown now closes the Carousel.
Opening the carousel now properly focuses it.
Fixed a bug where closing the carousel would instantly close instead of doing its animation like the opening.

Is this correctly rebased ?

Is this correctly rebased ?

Your PR to master looks legit so I'd assume yes.


uuids instead of display names are shown in detail view of VM snapshot

ISSUE TYPE

Bug Report

COMPONENT NAME

Primate UI

CLOUDSTACK VERSION

4.15.0

CONFIGURATION

OS / ENVIRONMENT

SUMMARY

On details view of an VM snapshot uuids instead of display names for "VM name" and "Zone" are shown
STEPS TO REPRODUCE

create VM snapshot
open detail view for created snapshot

EXPECTED RESULTS

real displayname for "VM name" and "Zone" is shown
ACTUAL RESULTS

@mib1185 listVmSnapshot API was not havin name parameters, I've created a PR to add them

@mib1185 listVmSnapshot API was not havin name parameters, I've created a PR to add them

Closed with #4604
@mib1185 please re-open if the issue still persists


Calculator stopped working

Hi,
first of all: thanks for the calculator! Very useful for larger bases.
But it stopped working today. I have a bookmark for all science packs (1400 per minute) and "end-tech"-settings that used to work ok, but now the output in the "factory"-tab doesn't show the full list anymore. It only shows two rows for red and green science, but no other resources and no oil. When I create a new list, it doesn't work either... some resources don't show up and the factory table is not updated correctly.
I think the "visualization" is still ok, but I never used that.
Also there is now a column "waste/m", probably for Bob's, but I play vanilla.
I use the latest Firefox on Linux, cleared the cache, reloaded, but that doesn't help.
The url I used is this one.
Thanks!

@viktro78 : That did the trick! Had to switch two times back and forth, but now it works again! Issue closed. Thanks!

There was a bug here, which was that I had broken certain old URLs. This should be corrected in a74d4603d6501232a80814bcfb2a6e0f0ece3e70.


Scanner permissions 'don't ask again' checkbox question

(Pasted from Slack discussion)
@7mto, when you go to the scan menu, it asks for permission to take pictures and record video. When you check the 'don't ask again' box, the 'Allow' button is greyed out, means you can only choose to always deny in future. This is a problem, because if someone checks the box and Denies access, then every time they go to the Scan menu it will deny access. I'm not sure how they will re-enable access to the camera if they want to scan.
If anything it should be the other way round, they should be able to give permanent access for the app to take pictures, so that they don't have to answer the dialog every time. Going through the dialog every time is bothersome and the scanning ceases to be a nice 'one-click' feature.
Do we have the ability to change this? Or is this dialog box built into the package?

The dialog is by the Android system not our app. That's their problem. We are not here to baby sit users. If they want to reset the permission, they can by resetting the app settings from Settings->Apps->Sustainability. If they don't check the box "which does not exist on my phone", it's their problem.
We can add that information to the help page but that's it for me. What do you think?

Ok. If I accidentally pressed the checkbox I would have had no idea how to bring it back up, and likely some people will not be familiar with apps. I'll add that information to the help page.


OrientDB connection to docker not working

Hi,
first of all thanks for your YCSB Benchmark and all your voluntary work. I am desperately trying to benchmark OrientDB with YCSB and came to a point where I need your help.
I set up OrientDB via docker container (docker compose), everything is working fine. I can access the server through localhost:2480, create databases, log in with them, change stuff, create stuff, etc.
orientdb:
    image: orientdb:latest
    environment:
      - ORIENTDB_ROOT_PASSWORD=root
    ports:
      - '2480:2480'
      - '2424:2424'
    volumes:
      - "orient-data:/orientdb/databases"

When executing YCSB, I use the following code to load data into OrientDB:
./bin/ycsb load orientdb -s -P workloads/workloada -p orientdb.url=remote:localhost:2424/ycsb -p orientdb.user=root -p orientdb.password=root -p orientdb.remote.storagetype=plocal -p orientdb.newdb=true

I can see in the OrientDB docker log, that a new ycsb database is created:
orientdb_1       | 2020-07-27 09:48:53:737 INFO  Dropped database 'ycsb' [OConnectionBinaryExecutor]
orientdb_1       | 2020-07-27 09:48:53:745 INFO  Direct IO for WAL located in /orientdb/databases/ycsb is allowed with block size 4096 bytes. [OCASDiskWriteAheadLog]
orientdb_1       | 2020-07-27 09:48:53:746 INFO  Page size for WAL located in /orientdb/databases/ycsb is set to 4096 bytes. [OCASDiskWriteAheadLog]
orientdb_1       | 2020-07-27 09:48:53:790 INFO  Storage 'plocal:/orientdb/databases/ycsb' is created under OrientDB distribution : 3.0.30 - Veloce (build eae50981ca31c79c85e4524fb376fced313acc23, branch UNKNOWN) [OLocalPaginatedStorage]

I can also see the newly created database in the GUI under localhost:2480. So there must be some connection to my database on the container. But nothing is inserted and there are several errors occuring.
2020-07-27 11:48:53 INFO  OrientDBClient:94 - OrientDB loading database url = remote:localhost:2424/ycsb
Warning: Nashorn engine is planned to be removed from a future JDK release
Juli 27, 2020 11:48:53 AM com.orientechnologies.common.log.OLogManager log
WARNING: The Client driver version is different than Server version: client=36, server=37. You could not use the full features of the newer version. Assure to have the same versions on both
2020-07-27 11:48:53 INFO  OrientDBClient:132 - OrientDB drop and recreate fresh db
2020-07-27 11:48:54 ERROR OrientDBClient:169 - Could not initialize OrientDB connection pool for Loader: com.orientechnologies.orient.core.exception.ODatabaseException: Cannot open database url=remote:localhost:2424/ycsb
com.orientechnologies.orient.core.exception.ODatabaseException: Cannot open database url=remote:localhost:2424/ycsb
	at com.orientechnologies.orient.core.db.document.ODatabaseDocumentTx.open(ODatabaseDocumentTx.java:295)
	at site.ycsb.db.OrientDBClient.init(OrientDBClient.java:153)
	at site.ycsb.DBWrapper.init(DBWrapper.java:86)
	at site.ycsb.ClientThread.run(ClientThread.java:91)
	at java.base/java.lang.Thread.run(Thread.java:832)
Caused by: java.lang.NumberFormatException: For input string: "nothing"
	at java.base/java.lang.NumberFormatException.forInputString(NumberFormatException.java:68)
	at java.base/java.lang.Integer.parseInt(Integer.java:652)
	at java.base/java.lang.Integer.parseInt(Integer.java:770)
	at com.orientechnologies.orient.core.config.OStorageConfigurationImpl.fromStream(OStorageConfigurationImpl.java:517)
	at com.orientechnologies.orient.core.config.OStorageConfigurationImpl.load(OStorageConfigurationImpl.java:218)
	at com.orientechnologies.orient.client.remote.OStorageRemote.open(OStorageRemote.java:369)
	at com.orientechnologies.orient.core.db.document.ODatabaseDocumentTx.open(ODatabaseDocumentTx.java:259)
	... 4 more
DBWrapper: report latency for each error is false and specific error codes to track for latency are: []
java.lang.NullPointerException
	at site.ycsb.db.OrientDBClient.insert(OrientDBClient.java:199)
	at site.ycsb.DBWrapper.insert(DBWrapper.java:221)
	at site.ycsb.workloads.CoreWorkload.doInsert(CoreWorkload.java:601)
	at site.ycsb.ClientThread.run(ClientThread.java:135)
	at java.base/java.lang.Thread.run(Thread.java:832)
Error inserting, not retrying any more. number of attempts: 1Insertion Retry Limit: 0
Exception in thread "Thread-2" java.lang.NullPointerException
	at site.ycsb.db.OrientDBClient.cleanup(OrientDBClient.java:187)
	at site.ycsb.DBWrapper.cleanup(DBWrapper.java:114)
	at site.ycsb.ClientThread.run(ClientThread.java:152)
	at java.base/java.lang.Thread.run(Thread.java:832)
2020-07-27 11:48:54:583 1 sec: 0 operations; est completion in<PHONE_NUMBER>67300 days 15 hours [INSERT: Count=0, Max=0, Min=9223372036854775807, Avg=NaN, 90=0, 99=0, 99.9=0, 99.99=0] [INSERT-FAILED: Count=1, Max=1880, Min=1880, Avg=1880, 90=1880, 99=1880, 99.9=1880, 99.99=1880]
[OVERALL], RunTime(ms), 1333
[OVERALL], Throughput(ops/sec), 0.0
[TOTAL_GCS_G1_Young_Generation], Count, 1
[TOTAL_GC_TIME_G1_Young_Generation], Time(ms), 3
[TOTAL_GC_TIME_%_G1_Young_Generation], Time(%), 0.22505626406601648
[TOTAL_GCS_G1_Old_Generation], Count, 0
[TOTAL_GC_TIME_G1_Old_Generation], Time(ms), 0
[TOTAL_GC_TIME_%_G1_Old_Generation], Time(%), 0.0
[TOTAL_GCs], Count, 1
[TOTAL_GC_TIME], Time(ms), 3
[TOTAL_GC_TIME_%], Time(%), 0.22505626406601648
[INSERT], Operations, 0
[INSERT], AverageLatency(us), NaN
[INSERT], MinLatency(us),<PHONE_NUMBER>854775807
[INSERT], MaxLatency(us), 0
[INSERT], 95thPercentileLatency(us), 0
[INSERT], 99thPercentileLatency(us), 0
[INSERT], Return=ERROR, 1
[INSERT-FAILED], Operations, 1
[INSERT-FAILED], AverageLatency(us), 1880.0
[INSERT-FAILED], MinLatency(us), 1880
[INSERT-FAILED], MaxLatency(us), 1880
[INSERT-FAILED], 95thPercentileLatency(us), 1880
[INSERT-FAILED], 99thPercentileLatency(us), 1880
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by com.orientechnologies.common.directmemory.OByteBufferPool (file:/Users/timgeisler/.m2/repository/com/orientechnologies/orientdb-core/2.2.37/orientdb-core-2.2.37.jar) to method sun.nio.ch.DirectBuffer.cleaner()
WARNING: Please consider reporting this to the maintainers of com.orientechnologies.common.directmemory.OByteBufferPool
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release

Similar docker setups were already done for ArangoDB, PostgreSQL, Oracle, MongoDB, Couchbase, Redis and Memcached. Everything is working fine with those databases, except OrientDB. I googled the problem for quite a while now and just can't help myself anymore. Can you help? Thanks in advance!

that failure is happening within the OrientDB client code, so it's going to be hard to track down. what version of the orientdb server are you using?

I am using the latest docker image, which is version 3.1.1


Extension 'mtxr.sqltools' FAILED to handle event: TypeError: Cannot read properties of undefined (reading 'document')

Describe the bug
Opened VSCode today and started seeing the following error in the Output tab of the terminal:
[ExtensionListenerError] Extension 'mtxr.sqltools' FAILED to handle event: TypeError: Cannot read properties of undefined (reading 'document'): Error: [ExtensionListenerError] Extension 'mtxr.sqltools' FAILED to handle event: TypeError: Cannot read properties of undefined (reading 'document')     at i.value (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:171:28731)     at r.B (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:90:732)     at r.C (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:90:802)     at r.fire (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:90:1018)     at c.$acceptEditorPropertiesChanged (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:163:34921)     at y.S (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:158:5968)     at y.Q (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:158:5734)     at y.M (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:158:4767)     at y.L (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:158:3602)     at i.value (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:158:2297)     at r.B (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:90:732)     at r.fire (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:90:949)     at a.fire (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:115:14463)     at i.value (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:184:8635)     at r.B (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:90:732)     at r.fire (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:90:949)     at a.fire (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:115:14463)     at MessagePortMain.<anonymous> (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:184:6761)     at MessagePortMain.emit (node:events:519:28)     at Object.MessagePortMain._internalPort.emit (node:electron/js2c/utility_init:2:2619)
To Reproduce
Steps to reproduce the behavior:

Open VS Code
Open Terminal
Go to Output tab
See error

Expected behavior
Not to see this error
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

SQLTools Version [v0.28.3]
VS Code Version: [1.93.0]
OS: [Mac]
Driver:

[ ] PostgreSQL/Redshift
[ ] MySQL/MariaDB
[ ] MSSQL/Azure
[X] SQLite
[ ] Other? Which...

Database version: [not applicable as I was not attempting to connect to any database]

Additional context
Note, this was not any specific attempt to connect to a database. Simply opening VSCode throws this error

Which channel of the Output tab on Panel is selected when that error displays?
Does the SQLTools channel of Output show information about the extension initializing?
Does the problem also occur when you open a new VS Code window with no folder/file(s)/workspace opened?

Update: I disable both sqltools and sqltool sqllite driver. Closed VSCode overnight. Re-enabled the plugins and now I am not seeing the error. I don't know what else changed.
I'll report back if I re-encounter the error.

Thanks for the update. Closing for the moment.

Please re-open ticket.
Running SQLTools v0.28.3 from 2024-11-12. Still getting this error over latest VSCode 1.95.3/Windows.
I disabled primary extension and drivers. Completely restarted VSCode, no error. Enabled primary extension, no drivers, got same "reading 'document'" error in Extension Host output window. No driver enabled, no documents open.
I'm happy to help diagnose this if I can.

I'm doing extension cleanup and wanted to see if I could find anything more about this anomaly.
I disabled all extensions and I'm re-enabling them one by one. As I do this I have my Extension Host output window open in a separate window - easier to see - as exthost.log.
With this one .log window open I enabled SQLTools and it goes into what seems like an infinite loop on this error.
I hope that helps.


for build datalake scenario create a new project of handoop sdk  to support release-v3.0.0-beta

old project need be renamed and sealed

The old cubefs-hadoop repository has been renamed cubefs-adoop-sealed。


Add blog post for cancellation in JS

@jongio in the mangeld #1226 pointed out two things I want to make sure are reflected in the discussion

The point about separation of concerns between controller and signal isn't clear. Any suggestions on how to improve would be appreciated!
In the intro, we could use a bulleted list instead of prose (and maybe add more scenarios besides). Anyone feel strongly here?

@adrianhall can you check out the new intro paragraph?


Check Digit

Description
Check wether given character is a digit (0-9).
Input  : 1
Output : Digit

Program added successfully :tada:
Thanks for your contribution :hugs:


can it be compared with elasticsearch

can it be compared with elasticsearch, https://www.elastic.co/, i know elastic is served for a while, but can hoot get the same functionalities even in the future

They are two different things, hOOt can be compared with lucene engine in elastic (although it has less functionality than lucene).

In short, Elasticsearch is more feature-rich and powerful, and it is more suitable for large-scale projects.


Lecasy API test is frozen because of unexpected Error raising

Are you requesting a feature or reporting a bug?
bug
What is the current behavior?
test is frozen because of unexpected Error raising
What is the expected behavior?
test should pass
How would you reproduce the current behavior (if this is a bug)?
Run following test
Provide the test code and the tested page URL (if applicable)
Test code
01.test.js:
"@fixture 01. KitchenSink - 'Form' View";

"@page https://js.devexpress.com/Demos/KitchenSink/#Form";

"@test"["'Form' view"] = {
    '@testCases': './device_cases.json',

    'Force device': function () {
        sessionStorage.setItem('dx-force-device', JSON.stringify(this.device.info));
        act.navigateTo("?reload" + document.location.hash);
    },

    "1. Wait 5s": function () {
        act.wait(5000);
    },

    "2. Scroll view": function () {
        act.drag(".dx-active-view .dx-scrollview-content", 0, -300);
    },

    "3. Type in hidden input": function () {
        // Test is frozen because 'VisibleElementAutomation._ensureElement' method raise error
        // after call 'VisibleElementAutomation._checkElementState'
        act.type(".dx-autocomplete input", "123");
    },

    "4. Wait 5s": function () {
        act.wait(5000);
    }
};

device_cases.json
[
    {
        "@name": "iPhone IOS7/8",
        "device": {
            "name": "iPhone",
            "info": {
                "platform": "ios",
                "deviceType": "phone",
                "device": "phone",
                "version": [ 7 ]
            }
        }
    }
]

I'm working on this


Build(deps-dev): Bump @typescript-eslint/eslint-plugin from 5.27.0 to 5.27.1 (#3588)

Pull request opened by the merge tool on behalf of #3588

Merged in fa49ab8ad8e32dfee660a4b244d901a4237a83da


Bump glob to ^4.4.0

Coverage remained the same at 100.0% when pulling d2a1aa4aea36103e35256704dea3ffad5004e9e9 on bump-glob into c7a1c13525dcdf8c4381ec9202a52a22f56785e6 on master.


fixed some bugs

fixes issue https://github.com/rjaviervega/tree-view-git-modified/issues/3 by inserting only the li element straight into the (.tree-view-scroller .list-tree) element instead of as a sibling to it the (.tree-view-scroller) element with its own div wrapper
also fixes the issue where when we navigate away from a project with Project Viewer (great package) and then back again atom.project.repositoryForDirectory.bind(atom.project) will return null for the repo.repo and you cant create another paneSub. To avoid this instead of destroying the pane subs when we navigate away, we just hide them and if we navigate back again we show them again.

I just realised i left two console.log statements inside lib/tree-view-git-modified-view.coffee
maybe take those out when you merge this in

Thank you looks good, lets merge it!


(python3) Add NoLockdown parameter to not change permissions

Description
This adds a "/NoLockdown" parameter to python3 to bypass the lockdown
of write permissions to administrators only.
It completely bypasses the Protect-InstallFolder helper function.
Note added to the readme/description
Motivation and Context
Fixes chocolatey-community/chocolatey-coreteampackages#1431
Related to chocolatey-community/chocolatey-coreteampackages#1547
How Has this Been Tested?

Ran update.ps1 with IncludeStream set to 3.10 to get a built package.
Installed in the test env without parameters to check it works as normal
Installed again in the test env with the nolockdown parameter to check that it works
Uninstall from the test environment
Installed on a windows 10 machine with the parameter

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Migrated package (a package has been migrated from another repository)

Checklist:

[x] My code follows the code style of this repository.
[x] My change requires a change to documentation (this usually means the notes in the description of a package).
[x] I have updated the documentation accordingly (this usually means the notes in the description of a package).
[x] All files are up to date with the latest Contributing Guidelines
[x] The added/modified package passed install/uninstall in the chocolatey test environment.
[x] The changes only affect a single package (not including meta package).

Thanks for this contribution - from which version of the installer will this take effect in?

@vattybear This should be available with the next version of the python3 package. Presumably, that would be version 3.10.1
It also will be available with any future updates to previous minor versions. (e.g. 3.x.n+1)


Slider color changing

I would like to change the color of the slider and  make it more appeling.

We are not looking for this right now


External / HTTP links don't work while using Tor

Brief Description:
http links in listings or profiles do not open a Browser while Tor is enabled
Operating System (OS and version): Mint 18
OpenBazaar version (shown on About OpenBazaar page in menu):  client 2.0.13, server 0.9.3
Hardware:
Reproducible (Always / Almost Always / Sometimes / Rarely / Couldn't Reproduce):
Always
Steps to reproduce:

Enable Tor
Klick any http link

Observed Behavior:
Nothing happens, No Error, No Warning
Expected Behavior:
opens Browser tab
Additional info (links, images, etc go here):
Feel free to contact me on slack

I can't reproduce this one. For me when I click an external link, I get the following warning:

If I click Yes, proceed, it opens the link in my browser.
If you you wanted to run the client from source and see if you are getting any errors in the JS console, it could give us a clue as to the problem.
@SamPatt @cpacia This user is on Linux and is unable to open external links when using Tor. I can't reproduce it on OSX. Are you able to open external links on Tor when on Linux?

This Window is new to me. It never showed up.


Add ability to filter account history by a particular address

@rowandh is there an issue on the board for this? Please create one so that the tester guys can test this 👍

Yes, see https://stratisplatformuk.visualstudio.com/StratisBitcoinFullNode/_workitems/edit/4198


[CFD-104] create event page

Description
Created event page and also created an EventDayTab component since its not exactly the same as the week one. 🥳
Uses dummy data structures for now.
Reason for Change
Completes CFD-104
Type of change

[X] New feature (non-breaking change which adds functionality)

Testing

I tested using the general event page but you can try doing this
import React from "react";
import { Text } from "react-native";
import { SafeAreaView } from "react-native-safe-area-context";
import { Stack } from "expo-router";
import Event from "./event";
import { EventListTemp } from "./event";
const event: EventListTemp = {
  name: "Event Name",
  venue: "CFD Center",
  startTime: new Date("2023-10-09T08:00:00.000"),
  duration: 480,
  events: [{name: "Event Name", startTime: new Date("2023-10-09T08:00:00.000"), duration: 85}, {name: "Event Name", startTime: new Date("2023-10-09T10:00:15.000"), duration: 55, venue:"Venue"}, {name: "Event Name", startTime: new Date("2023-10-09T11:00:15.000"), duration: 55, venue: "Venue"}, {name: "Event Name", startTime: new Date("2023-10-09T15:00:15.000"), duration: 90}]

}
const Calendar = () => {
  return (
    <SafeAreaView className="">
      <Stack.Screen options={{ title: "Calendar", headerShown: false }} />
      <Event event={event} />
    </SafeAreaView>
  );
};

export default Calendar;

https://github.com/uoftblueprint/centre-for-dreams/assets/113125436/cde4f3f0-8e63-4432-930b-516e9e580344

OOPs let me remove a comment rq

Sorry baker


Support Linux kernel 5.15 and newer opensbi version

In order to use the Litex Ethernet driver on kernel 5.15+, I am now actively working on bringing up kernel 5.15 on BP.
Also, with kernel 5.15, we might want to use newer version of opensbi because I have seen the kernel emit rdtime instruction in U-mode and the current opensbi version in our SDK doesn't seem to emulate that instruction properly. I'm now also looking at this as well, and I will file a PR for each of them in the future.

Cool!

I was able to run Linux kernel 5.15 + opensbi v1.0 on dromajo with multicore support (at least I haven't encountered any kernel panic).
Before creating PR, I think first we need to sync the master branch from our forked opensbi repo with the official repo. After that, should I base my work on branch 'blackparrot_mods' or should I create a brand-new branch starting right from the latest master branch after the sync? I think creating a new one would be easier for me because most of the changes in 'blackparrot_mods' are outdated, but by doing so we will end up creating a branch whenever we bump opensbi.

Cool! Make a new branch

Is this ready for a PR and update to the SDK master branch? I see the following PRs both merged already in the respective repos:

https://github.com/black-parrot-sdk/bp-linux/pull/6
https://github.com/black-parrot-sdk/opensbi/pull/2

Are there any other changes required (i.e., Dromajo, RTL, etc.)?

Think it should be good to go, just need FPGA validation

@Yuan-Mao Single core linux looks good. I was able to boot on FPGA, including with 2 GiB of DRAM allocated and showing available to the OS in /proc/meminfo.
Multicore linux (2 or more cores) is failing in Dromajo simulation when the boot reaches secondary CPU bringup. Dromajo reports an invalid physical address of 0x1300000.
I believe there is also a bug related to the param rom implementation in Dromajo, which needs a small update for the latest aviary param rom changes.

This issue appears to be present on current SDK master, too. I'm guessing it is an unimplemented BP thing, perhaps?

Invalid physical address sounds more like a device trying to get initialized that doesn’t exist? But would have to see the trace to make sure

Update: false alarm on multicore linux on dromajo. Turns out the --ncpus flag to dromajo is important... I've successfully emulated 2, 4, and 8 core Linux boots. Still need to verify multicore linux on multicore FPGA build.

Closed with #41


 Specifically NBA Elo https://github.com/fivethirtyeight/data/tree/master/nba-elo

What about the code behind NBA players projected plus/minus? I would be happy if you publish that :)

We don't have plans to publish the code, but we've made more historical data available:
https://github.com/fivethirtyeight/data/tree/master/nba-carmelo
https://github.com/fivethirtyeight/data/tree/master/nfl-elo
https://github.com/fivethirtyeight/data/tree/master/mlb-elo
https://github.com/fivethirtyeight/data/tree/master/soccer-spi

yeah that would be helpful


Codeflow: Multiple issues with github.com/nrwl/nx

Describe the bug
The first load caused a "Failed to resolve dependencies" error.
The second attempt installed dependencies fine and then died trying to start a project:
Error: > Couldn't find a `pages` directory. Please create one under the project root
    at Object.findPagesDir (/home/nrwl/nx/node_modules/next/dist/lib/find-pages-dir.js:42:19)
    at new DevServer (/home/nrwl/nx/node_modules/next/dist/server/dev/next-dev-server.js:107:66)
    at NextServer.createServer (/home/nrwl/nx/node_modules/next/dist/server/next.js:137:20)
    at eval (/home/nrwl/nx/node_modules/next/dist/server/next.js:149:42)
    at async NextServer.prepare (/home/nrwl/nx/node_modules/next/dist/server/next.js:127:24)
    at async eval (/home/nrwl/nx/node_modules/next/dist/cli/next-dev.js:141:9)

Link to the blitz that caused the error
https://stackblitz.com/~/github.com/nrwl/nx
Steps to reproduce
No changes to the code have been made. The project has just been loaded and fails at the install/setup phase.
Expected behavior
Installation and starting the project would succeed.
Parity with Local

[X] I have run the project in my local machine and I could not reproduce the issue.

Screenshots
No response
Platform
Version = 1.67.0
Hash = 781d7336116100a3cea72283913b570818ac125e
WebContainer = ea2f6b48b77806aba8e6fe3b6311530cc7674f64

Browser name  = Chrome
Full version  = <IP_ADDRESS>
Major version = 106
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
performance.memory = {
  "totalJSHeapSize": 125293390,
  "usedJSHeapSize": 121730214,
  "jsHeapSizeLimit":<PHONE_NUMBER>
}

Additional context
My guess is that this is a broader issue with nx workspaces or workspaces in general. (not certain though)
Looking closer, I noticed this:
info security We found `install` scripts which turbo skips for security reasons. For more information see https://turbo.sh/install-scripts.
├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>└─<EMAIL_ADDRESS>

:wave: We're closing this due to inactivity. Please, feel free to open a new one if you're still encountering any errors.


Update compiler to check for cms tags in Java source code.

Check for tags relating to the cms and add them tot he output rst.

Thanks Martyn - done now.


working

Hey, im getting tons of errors. Did i get the latest version?
Thanks for the great work by the way ;)

It's in a very early state at the moment. What errors are you getting? And what version of python?

Hey, it looks like I went too fast. It is working I used the wrong version of python. Good catch!,

hey, congrats on your progress. I was about to ask you if there was the possibility to update podcast status but it seems like it is something you already thought about.
I am just having some difficulty with the synthax. Would you mind providing me with an example on how to use
pocket. update_starred(podcast, episode, starred)?
Thanks,Jonathan

The easiest way to use update_starred is with the getters and setters of the episode class, which call the method behind the scenes e.g.
>>> import pocketcasts
>>> p = pocketcasts.Pocketcasts(user, password)
# Just getting a podcast episode to star
>>> podcast = p.get_featured()[0]
>>> episode = p.get_podcast_episodes(podcast)[0]
>>> episode.starred
False
>>> episode.starred = True
>>> episode.starred
True

If you did want to use the method, the syntax is using a pocketcasts.Podcast class, a pocketcasts.Episode class and a boolean.

Great, thanks so much!
From: exofudge<EMAIL_ADDRESS>Sent: 10 March 2017 19:49
To: exofudge/Pocket-Casts
Cc: darkzbaron; State change
Subject: Re: [exofudge/Pocket-Casts] working (#1)
The easiest way to use update_starred is with the getters and setters of the episode class, which call the method behind the scenes e.g.

import pocketcasts
p = pocketcasts.Pocketcasts(user, password)

Just getting a podcast episode to star

podcast = p.get_featured()[0]
episode = p.get_podcast_episodes(podcast)[0]
episode.starred
False
episode.starred = True
episode.starred
True

If you did want to use the method, the syntax is using a pocketcasts.Podcast class, a pocketcasts.Episode class and a boolean.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub https://github.com/exofudge/Pocket-Casts/issues/1#issuecomment-285752308 , or mute the thread https://github.com/notifications/unsubscribe-auth/AE8Nd7-RIuf8eph0FCJQppYwVw5M5SfHks5rkZs1gaJpZM4LrbJC .  https://github.com/notifications/beacon/AE8Ndzur7vSb4nrckKoTbTfA7BATM_pxks5rkZs1gaJpZM4LrbJC.gif


Remove sentiment API key

Direct users on how to get their own API key

Just a clue would be nice!

Hey @stevehemingway, thanks for prompting me on this
I did add this to the README

Now you'll need to add your Twitter keys to the .env file. Just input the keys in their corresponding fields and save the file.
The SENTIMENT_KEY you can get a new API key at https://market.mashape.com/vivekn/sentiment-3 your key is in the REQUEST EXAMPLE
CONSUMER_KEY=Fw***********P9
CONSUMER_SECRET=TD************Cq
ACCESS_TOKEN=31**************UC
ACCESS_TOKEN_SECRET=r0************S2
SENTIMENT_KEY=Gj************lF

Then you can then add some keywords into the strings.js file for what you want to search for as well as sub-queries.

Is that not clear enough?
I mean the only other thing I could think of was adding a picture :+1:

Resolved with #22

Sorry, yes, it is obvious now you mention it!

I've added a gif detailing the process now as well, thanks again for the nudge :smile:


Run ncov-ingest on Terra

Description
Allow users with GISAID API endpoint access to run ncov-ingest with their credentials on Terra.
Possible solutions
Create a separate task in the ncov WDL workflow that downloads and runs the ingest workflow.

Done and working

ncov ingest code: https://github.com/nextstrain/ncov/blob/wdl/temp_ingest/workflow/wdl/tasks/ncov_ingest.wdl#L3
Import into Terra via Dockstore: https://dockstore.org/workflows/github.com/nextstrain/ncov:wdl/temp_ingest?tab=info
User Guide: https://github.com/nextstrain/ncov/blob/wdl/temp_ingest/docs/src/guides/run-ingest-on-terra.rst
Whole Workflow Diagram: https://raw.githubusercontent.com/j23414/wdl_pathogen_build/main/data/Terra.png


Fix it so list->string prints a list representation for lists instead of a sequence of pairs

Currently list->string prints the representation of pairs instead of the more streamlined list representation. It worked before, so something has been changed that broke printing lists.

It looks like this is only an issue in the REPL, which doesn't use print and so doesn't call list->string. Closing because it will be fixed with the new updates to the REPL.


Cashu redeem

We can close #885 and go with this
I added string handling, redeem screen stuff, and mild support in DMs. in the future we can do contact tagging and auto-sweep for DMs, but this seemed easy enough for now.

Works on signet but seems like there are some problems redeeming with real mainnet mints so switching to draft until we figure that out

requires https://github.com/MutinyWallet/mutiny-node/pull/1139

this should work with the latest release


invalid sha1 on dependency download

I'm encountering download problem on flyway-sbt.   Check that these dependencies exist with the requested attributes.
[warn] 		org.flywaydb:flyway-sbt:3.1 (scalaVersion=2.10, sbtVersion=0.13)
[warn]
It used to work on my local and our jenkins but now it fails.

Please try again. Nothing has changed on this end.

My suspicion is that this happened while GitHub pages was updating the site for some unrelated change.
I'll look into moving the repo to bintry in the future to avoid this: #927

We're falling on the same issue. A workaround for meanwhile: upload to amazon S3 bucket with the following layout: org/flywaydb/flyway-sbt_2.10_0.13/3.1/flyway-sbt-3.1.jar and org/flywaydb/flyway-sbt_2.10_0.13/3.1/flyway-sbt-3.1.pom and add your bucket as a repository.


While looping the scond time noo need buffer player Again..

Am using start() method for looping video ( giraffePlayer.start() )..its working fine but every time its getting buffer .second time no need buffer the video,,could you please suggest solution

any suggestion regarding this ??


Revert-to-upstream

Undoing a lot of the changes and reverting to as close as possible to the original. Focus on just integrating payload.

I think you have made a PR to the wrong repo @jancbeck, this doesn't really fit the bill of ct3t.

you are right @Wundero. I forked the repo and accidentially created the PR upstream instead of origin. Sorry!


Istio AuthorizationPolicy allow requires defining a port number if HTTP Host header includes a port number

Bug Description
We have a third party service whose source code we have no control over. Some HTTP requests made by this service to our cluster with Istio worked and some were denied with RBAC "policy matched none". The service is using mTLS and has some heavy Istio configuration. Maybe this is not relevant but gives some context about the pain on trying to find the problem.
We now have a cluster wide AuthorizationPolicy for allow with two entries for each host:
apiVersion: security.istio.io/v1beta1
kind: AuthorizationPolicy
metadata:
  name: allow
  namespace: istio-system
spec:
  action: ALLOW
  rules:
    - to:
      - operation:
          hosts:
          - "*.ourdomain.com"     # <-- Earlier we had only this one, a host without a port
          - "*.ourdomain.com:443" # <-- This issue is about having to also define the host with the port number
  selector:
    matchLabels:
      istio: istio-ingressgateway

When a HTTP request is made and the Host: header of this request includes the port number, Istio will fail the request. We are able to replicate this issue with Postman. Issue cannot be reproduced by curl because curl removes the port number from the HTTP request's Host header.
For example: Host: lolcat.ourdomain.com:443 where normally the HTTP request would have Host: lolcat.ourdomain.com.
It seems each hostname needs to be duplicated in the allow list with one including the port number.
Which is surprising and it is not really documented anywhere.
Is it expected behaviour from Istio that one needs to consider port numbers in the hosts field of an AuthorizationPolicy?

If yes, let's document the behaviour.
If not, let's fix this.
If we're not going to anything about this - here's at least a Github issue for fellow developers in the future.

Version
$ istioctl version
client version: 1.16.2
control plane version: 1.16.2
data plane version: 1.16.2 (66 proxies)

Additional Information
Target cluster context: redacted

Running with the following config:

istio-namespace: istio-system
full-secrets: false
timeout (mins): 30
include: {  }
exclude: { Namespaces: kube-node-lease,kube-public,kube-system,local-path-storage }
end-time: 2023-03-23 18:04:22.388775 +0200 EET

Cluster endpoint: https://redacted
CLI version:
version.BuildInfo{Version:"1.16.2", GitRevision:"3e5fd5a1d70ea535ad5d18fb66a76c5cce905876-dirty", GolangVersion:"go1.19.5", BuildStatus:"Clean", GitTag:"1.16.2"}

The following Istio control plane revisions/versions were found in the cluster:
Revision default:
&version.MeshInfo{
    {
        Component: "pilot",
        Info:      version.BuildInfo{Version:"1.16.2", GitRevision:"3e5fd5a1d70ea535ad5d18fb66a76c5cce905876", GolangVersion:"", BuildStatus:"Clean", GitTag:"1.16.2"},
    },
    {
        Component: "pilot",
        Info:      version.BuildInfo{Version:"1.16.2", GitRevision:"3e5fd5a1d70ea535ad5d18fb66a76c5cce905876", GolangVersion:"", BuildStatus:"Clean", GitTag:"1.16.2"},
    },
}

The following proxy revisions/versions were found in the cluster:
Revision default: Versions {1.16.2}

Fetching proxy logs for the following containers:
[.. redacted .. ]

Maybe you can use the env ISTIO_GATEWAY_STRIP_HOST_PORT to force data plane to remove port from host before authz filter processing.
The env ISTIO_GATEWAY_STRIP_HOST_PORT cannot effect the sidecar proxy. But your case is only gateway and I think you can use it.

https://istio.io/latest/docs/ops/best-practices/security/#writing-host-match-policies
You can specify a wildcard suffix
apiVersion: security.istio.io/v1
kind: AuthorizationPolicy
metadata:
  name: ingress-host
  namespace: istio-system
spec:
  selector:
    matchLabels:
      app: istio-ingressgateway
  action: DENY
  rules:
  - to:
    - operation:
        hosts: ["example.com", "example.com:*"]

The user case is *.example.com.  We can't use the prefix wildcard and suffix wildcard in the same time.


New Feature : if user type more than certain character, user cant type anymore

Hello, very thanks for your fixing, Thats good! But, some people needs user cant type anymore when get limit max character. current condition, if user type more than certain character, we just do controoler.disable() then if we want enable, must add a trigger button for controller.enable() this UX feels wrong :( ... please keep up! thank you so much!!!! <3

Fixed via 4286817f065152ca5d2b743470e70b3c483203ba

我尝试了它,发现并没有作用.也可能是我使用的不对

我尝试了它,发现并没有作用.也可能是我使用的不对

What is your Html() widget code? Make sure to set characterCount in the htmlEditorOptions.

我用的是 html_editor_enhanced: 2.4.0,终端为安卓

that seems right. Are you typing in Chinese text or English text? Maybe it is an issue with Chinese text but works okay in English text.

用的是英语

hmmm... I think I only tested for web if I remember correct. I will test for Android when I have time to try and fix it. Sorry for the inconvenience!

好的,感谢

Unfortunately after looking deeper, the character limit cannot be supported in Android with the current implementation. Every android keypress is recorded as key 229 so I cannot distinguish between backspace and some character press.
I would recommend using callback onChange and checking character count, then providing an error when the user goes over the allowed character count.

thank you so much for suggestion! i will try it thanksss!!!
On Mon, Jan 10, 2022 at 4:12 AM Tanay Neotia @.***>
wrote:

Unfortunately after looking deeper, the character limit cannot be
supported in Android with the current implementation. Every android
keypress is recorded as key 229 so I cannot distinguish between backspace
and some character press.
I would recommend using callback onChange and checking character count,
then providing an error when the user goes over the allowed character count.
—
Reply to this email directly, view it on GitHub
https://github.com/tneotia/html-editor-enhanced/issues/144#issuecomment-1008424648,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AH73WH6LYFMQBSRDZJEDUTLUVH22BANCNFSM5EU6LMIQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID:
@.***>


fix/docs/chunk

@dcvz
I was a bit late to review your chunk operation. It's very nice but I found something was wrong with the doc. I made a test that explains why I'm changing it. Is this the behaviour you want?

@dcvz now it should have the right behaviour


fix(publish): update peer dependencies before publish

Lerna ignores peerDependencies completely whilst they need to be in line with devDependencies.
Also, add missing modules to components

@EisenbergEffect at the moment, dependencies are specified as peer deps. This is to combat an issue where users would have duplicated version of a modules. Though this makes lerna skip updating dependencies of packages, as it ignore peers section.
Do you see any issues with hooking into prepublishOnly? Description:

prepublishOnly: Run BEFORE the package is prepared and packed, ONLY on npm publish. (See below.)

No objections from me.

@MaximBalaganskiy is there any other hook that let us have "what you see in git is what you get in npm"?

version hook suits better - it's run right before the commit

The description of version commands from https://docs.npmjs.com/misc/scripts. If we want t enhance this more, maybe use some more from lerna and https://docs.npmjs.com/cli/version.html
preversion: Run BEFORE bumping the package version.
version: Run AFTER bumping the package version, but BEFORE commit.
postversion: Run AFTER bumping the package version, and AFTER commit.

Looks suitable for this to me. Thanks @MaximBalaganskiy


xtensa/esp32s3: Separate address and command flag for QSPI DMA transfer

Summary
Some spi slave device set address with special command, no address required in read command, so separate address and command setting.
Impact
esp32s3 qspi
Testing
esp32s3-devkit

@Kevin-Zhou11 please fix coding style issues reported in the CI Check


add plugin-sass with new onChange/markChanged interface

Changes

Resolves https://github.com/pikapkg/snowpack/issues/1121

adds a new onChanged() hook for plugins to listen for changed files during development.
adds a new markChanged() method that plugins can call to mark a file as changed.

Adds a new Sass plugin to test the new interface: @snowpack/plugin-sass (@drwpow sorry I beat you to it :)

Testing

TODO Tests added.

Docs

TODO: Docs added to README, plugins guide, and sass recipe

@drwpow ready for another look


[v2] Ignore files which are ignored by IntelliJ

The plugin should ignore errors in ignored files:

It probably should not completely ignore the files, because there may be cases where types are defined in vcs-ignored files, but I think it would be good if it would ignore errors in ignored files.
Version and Environment Details
Operation system: Linux Mint
IDE name and version: 2019.1 EAP
Plugin version: 2.0.0-alpha-8

Hi Luca.
Thanks for testing the alpha.
Can you describe your use case in more detail, and include the error message you're seeing?
The reason I'm asking is that I don't think it always makes sense to disable error highlighting just because a file is ignored in vcs.
So just trying to understand your use case, as there might be an alternative solution.
Best regards,
Jim.

Sure, makes sense!
My use case is basically Prisma. I write SDL, code gets generated, and additionally I output a schema.graphqls with the generated prisma graphql server so I have completions in my seed *.graphql files. However, now that prisma generates a second schema, now I have conflicts because my original config declares type User but so does the prisma GraphQL server.
I see that this is a special case, in the only reason I generate the extra schema.graphqls file is I can't seem to find an option in the .graphqlconfig file to get the schema from a server instead of an extra generated graphql file... so feel free to close if this is out of scope.

Hi Luca.
You should be able to get this working without duplicate type errors by separating your two "logical" schemas. Take a look at https://github.com/jimkyndemeyer/graphql-config-examples which shows various examples of how to control schema discovery via .graphqlconfig globs.
You'd then have one "SDL authoring schema" and your "Production schema" that you can consume from UI components for example.
Once you get it sorted, I'd appreciate a PR or a "how-to" issue in the graphql-config-examples repository as this could help other Prisma users.
Thanks for the kind words about the plugin :)
Let me know if you have any questions.
Best regards,
Jim.

Thanks for the hint. I can get my schema from a remote now, but I still end up having a local graphql schema file which does not solve my original problem.

This can be solved using projects. Didn't hat the time to fully test it but it fixes my main problem.


Add 'beakerbrowser' executable with npm link?

The current package.json runs the browser through npm start using gulp. Using a "bin" entry in package.json, npm link could be used to add a beakerbrowser executable to the user's PATH.
I began trying to work this out but gulp makes this pattern very difficult.

Oh yeah, that'd be nice. Let me spend a few minutes and see if I can get that working.

Done! Pull master and try it out

It works! Yay! Thank you :D


Update known_good.json

Updated MoltenVK to latest known good release (v1.2.6)

CI Vulkan-Tools build queued with queue ID 69046.

CI Vulkan-Tools build queued with queue ID 69046.

CI Vulkan-Tools build # 1244 running.

CI Vulkan-Tools build # 1244 passed.


Adding support for Map type fields

This leverages existing features MultiValue feature in Pinot. A Map is represented as two Multi-valued columns - __KEYS and __VALUES. This convention is used in only one place - real-time ingestion and segment generation. When pinot sees a FieldSpec name that ends with __KEYS or __VALUES, it checks for the field in the input Record. If that object turns out to be a map, then we convert it into two columns -> keyArray and valueArray.
Once we ingest a map as two arrays, we can access map['keyName']  via udf map_value(keyColumnName, 'KeyName', valueColumnName). We can support the simpler syntax when we move to calcite.
Sample queries
select map_value(myMap__KEYS, 'k1', myMap__VALUES) from myTable
select count(*) from myTable group by map_value(myMap__KEYS, 'k1', myMap__VALUES)
select count(*) from myTable where map_value(myMap__KEYS, 'k1', myMap__VALUES) = 'v1'
NOTE:
While this solution is not elegant, it is a good first step towards supporting Map and Struct data types.
Supporting Map as a DataType was bit invasive and requires us to first introduce the concept of CompositeColumnDatasource.

Codecov Report

Merging #4388 into master will increase coverage by 9.75%.
The diff coverage is 89.79%.

@@             Coverage Diff              @@
##             master    #4388      +/-   ##
============================================
+ Coverage      55.7%   65.46%   +9.75%
  Complexity       20       20
============================================
  Files          1066     1067       +1
  Lines         55403    55448      +45
  Branches       7894     7902       +8
============================================
+ Hits          30865    36300    +5435
+ Misses        22150    16570    -5580
- Partials       2388     2578     +190

Impacted Files
Coverage Δ
Complexity Δ

...segment/creator/impl/SegmentDictionaryCreator.java
87.75% <ø> (+3.97%)
0 <0> (ø)
:arrow_down:

...realtime/stream/AvroRecordToPinotRowGenerator.java
100% <100%> (+7.69%)
0 <0> (ø)
:arrow_down:

...r/transform/function/TransformFunctionFactory.java
69.09% <100%> (+6.12%)
0 <0> (ø)
:arrow_down:

...ache/pinot/core/data/readers/AvroRecordReader.java
86.2% <100%> (ø)
0 <0> (ø)
:arrow_down:

.../transform/function/MapValueTransformFunction.java
86.95% <86.95%> (ø)
0 <0> (?)

...ain/java/org/apache/pinot/core/util/AvroUtils.java
53.33% <91.3%> (+7.79%)
0 <0> (ø)
:arrow_down:

...ator/transform/function/BaseTransformFunction.java
29.95% <0%> (+0.42%)
0% <0%> (ø)
:arrow_down:

...ment/creator/impl/SegmentColumnarIndexCreator.java
87.45% <0%> (+0.76%)
0% <0%> (ø)
:arrow_down:

...r/transform/function/ValueInTransformFunction.java
39.2% <0%> (+0.8%)
0% <0%> (ø)
:arrow_down:

... and 323 more

Continue to review full report at Codecov.

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

Please open issues for things not handled in the PR.
Will create issues for

supporting map type syntax map['key']. This will be handled automatically when we start using calcite.
Anything else you can think of?

The __KEYS and __VALUES columns have specific semantics in the code, however, they are stored as MV columns. Are there any issues in allowing these columns to be treated as regular MV columns when the queries are not of the form specified in the PR description?
Not really.
Would be good to add a real world example that this feature can help solve, in the description.

will update the docs. I think the need for map type is pretty obvious.  classic cases - tags/labels, sparse dimensions, etc.

This PR seems to have commits that are already part of apache/pinot, and not related to map-type support. Probably the PR was not created correctly?


validation wordembedding glov miss

File "linguistic_style_transfer_model/models/adversarial_autoencoder.py",
line 645, in train
shuffled_one_hot_labels, inverse_word_index, current_epoch, sess)
File "linguistic_style_transfer_model/models/adversarial_autoencoder.py",
line 655, in run_validation
glove_model = content_preservation.load_glove_model(options.validation_embeddings_file_path)
File "inguistic_style_transfer_model/evaluators/content_preservation.py"
, line 22, in load_glove_model
embedding = np.array([float(val) for val in split_line[1:]])
I didn't find any glov model for validation, so i just use train word embedding

Sorry about the confusion. I've added a note to the README
The validation embeddings should not be the same as the training embeddings.
https://github.com/vineetjohn/linguistic-style-transfer/commit/9de4d1ff44cecd09d7426fa2939bd64142dbbd1c


[FIX] Exclude sessions missing a queried property from matches

Closes #324

Changes proposed in this pull request:

Use the BOUND function in subquery for matching phenotypic sessions to exclude any results where a variable being filtered for does not have a value ("unbound" results - these are included by default, leading to inaccurate counts of matches)
Make having a phenotypic session non-optional in query (since subjects should not end up in the graph if they don't have any phenotypic info)
Minor refactoring of query template for efficiency

Checklist
This section is for the PR reviewer

[ ] PR has an interpretable title with a prefix ([ENH], [FIX], [REF], [TST], [CI], [MNT], [INF], [MODEL], [DOC]) (see our Contributing Guidelines for more info)
[ ] PR has a label for the release changelog or skip-release (to be applied by maintainers only)
[ ] PR links to GitHub issue with mention Closes #XXXX
[ ] Tests pass
[ ] Checks pass

For new features:

[ ] Tests have been added

For bug fixes:

[ ] There is at least one test that would fail under the original bug conditions.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>8
Details

8 of 8 (100.0%)  changed or added relevant lines in 3 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage increased (+0.05%) to 95.972%

Files with Coverage Reduction
New Missed Lines
%

app/api/utility.py
1
86.21%

Totals

Change from base Build<PHONE_NUMBER>6:
0.05%

Covered Lines:
691

Relevant Lines:
720

💛  - Coveralls


[TF 2.0 API Docs] tf.image.transpose

Doc link: https://www.tensorflow.org/versions/r2.0/api_docs/python/tf/image/transpose
Description of issue (what needs changing):
Usage example
No usage example is provided.

@Aqsa-K This was already fixed here in the recent TF version. Thanks!
I am closing this issue as this was resolved. Thanks!


Models no longer exist on HF.

https://huggingface.co/SWivid/F5-TTS/tree/main

Looks like models have been split into two projects

https://huggingface.co/SWivid/E2-TTS
https://huggingface.co/SWivid/F5-TTS

Ah, thanks!


Fixes to how questions in a community are displayed

See this thread for full context: https://metaculus.slack.com/archives/C02J55VPUCX/p1734722237162839
We're proposing the following:

Make it so the community display only appears when the community is the default project
Make it so the community is always included as a tag in the sidebar

We want to avoid this, where a metaculus main question that's cross-posted to a community, such that the community is not the default project, doesn't show the community visualization:

I'll implement the community tag portion of this. Then pass it off to another eng,

The Tag portion of this is now implemented and will be visible at next deployement. Dropping down to medium priority.
@ncarazon , would you be able to take over this ticket to tackle: "Make it so the community display only appears when the community is the default project"?

@lsabor yeah, will take a look

@ryooan @lsabor

Make it so the community display only appears when the community is the default project

The app already functions this way. The community navbar is displayed only when the community is set as the default project. In the Slack thread you referred to, the community is the default project, which is why you see the alternative navbar:

So you just need to update post configuration. Here is an example from localhost:

@ncarazon ah thank you! Sorry for that, thought I had checked that but I guess not.


fix: support inquirer 8

With npm 7 and the new way peerDependencies are installed, this module currently fails when using inquirer 8.
After looking through the code, it appears this module supports inquirer 8.
This PR adds support for it and uses >= in order to prevent this problem in the future. An alternative would be to use 7.x || 8.x instead.

@ehmicky thanks for tackling this! Good catch. And thanks for the Twitter shout-out! 🙌


feat(callout): web-component created

Related Ticket(s)
#3638
Description
Callout internal pattern was created.

@RaphaelAmadeu there are some build issues, can you take a look?

@RaphaelAmadeu looks like there was an impact on the React side, can you doublecheck?

Marking as request changes as there looks like a number of diffs on the React side.

@jeffchew They are now resolved.


Release Google.Cloud.Billing.Budgets.V1Beta1 version 1.0.0-beta04

Changes in this release:

Commit ac367e2: feat: Regenerate all APIs to support self-signed JWTs

Created release for Google.Cloud.Billing.Budgets.V1Beta1-1.0.0-beta04


How the planes is generated?

Hi
The project provided a planes directory for model's input. I'm a little curious about the way it was generated and It seems cannot be found in the paper. Could you please suggest some related resources? Thanks!

@memoiry for ground plane generation, we used a mixture of older methods that are probably considered obsolete now:

Ground segmentation and occupancy grid generation using probability fields:
https://www.researchgate.net/profile/Ali_Harakeh2/publication/282866885_Ground_Segmentation_and_Occupancy_Grid_Generation_Using_Probability_Fields/links/56baf64008ae0a6bc9557788/Ground-Segmentation-and-Occupancy-Grid-Generation-Using-Probability-Fields.pdf

http://www.cs.toronto.edu/objprop3d/

It looks like the ground plane algorithm is a little time-consuming, is that only the kitti testing, you are using this ground plane detection.
But when you are really deploying the model, it is a different story, for example, you are using a fixed ground plane ?

Yes for deployment, we do constant ground plane to eliminate the time required for estimation. It works well in practice for deployment,  but I doubt it to be a good approach for beating the KITTI benchmark.

Thanks, my issue is solved

@ @memoiry @yzhou-saic  Have you solved the problem of ground plane  about the test set?

@hulaifeng @asharakeh  So, how to generate the ground plane when testing?

@jinfagang http://www.cs.toronto.edu/objprop3d/

is it possible to do ground removing before AVOD and feed the points without ground into AVOD model? Is there any flag to disable using ground plane in AVOD?

@memoiry for ground plane generation, we used a mixture of older methods that are probably considered obsolete now:

Ground segmentation and occupancy grid generation using probability fields:
https://www.researchgate.net/profile/Ali_Harakeh2/publication/282866885_Ground_Segmentation_and_Occupancy_Grid_Generation_Using_Probability_Fields/links/56baf64008ae0a6bc9557788/Ground-Segmentation-and-Occupancy-Grid-Generation-Using-Probability-Fields.pdf
http://www.cs.toronto.edu/objprop3d/

The second link is dead. Could you please update?

The second link is dead and planes in README is also dead.

2. http://www.cs.toronto.edu/objprop3d/

I see the page in this link


Text size too small .

Text size is too small

I will fix this issue. Kindly assign it to me and add hacktoberfest-accepted, hacktoberfest labels.

i will fix this within an hour after assigning please assign this to me . please add hacktoberfest and gssoc labels .


acs: list and show with table option shows same output

@yuganagw-msft Show should display agent count, master count, orchestrator, public ssh key, resource group, location , dns-prefix, Master and agent FQDN's, vm size

@sauryadas
For table, that is too many fields to fit in one line.
How about you try out yourself using query expression such as --query "{name:name, masterAccount:masterProfile.count}", when are satisfied with the display, let me know the fields list

Can we close this, I'm doing some of this work here:
https://github.com/Azure/azure-cli/pull/1641
@sauryadas please comment on that PR for the set of fields you'd like to see.

closing will be fixed as a part of #1641


how should keyword filters apply to spatial coverages?

the geo-map view currently allows filtering on stelle__text__autor, stelle__id, stelle__use_case as well as key_word. Keyword filters are thus applied on the single keyword explicitly associated with a spatial coverage.
this may be confusing (at least it was for me) when a user searches for "Dani", which can be either a "Keyword (Ethnonym)" (ID 53) or a "Keyword (Region)" (ID 228). selecting the former will return results, selecting the latter will return none. however it looks like other spatial coverages do have "Region" keywords associated, not "Ethnonym" :
curl "https://mmp.acdh-dev.oeaw.ac.at/api/spatialcoverage/" | jq '.features[].properties.key_word.art'

should SpatialCoverage allow multiple keywords?
should /api/spatial-coverages expose a stelle__key_word filter?

x-ref #159


How to index datetime value with JSON?

I want to index datetime value with JSON.
In the schema, the following date field has created with the name timestamp:
...
  {
    "name": "timestamp",
    "type": "date",
    "options": {
      "indexed": true,
      "stored": true,
      "fast": "single"
    }
  }
...

When I index JSON with the timestamp value set as follows:
"timestamp" : "2019-12-06T12:22:54.341Z",

The following error occurred:
thread '<unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: ValueError("timestamp", TypeError("Expected an integer, got String(\"2019-12-06T12:22:54.341Z\")"))', src/libcore/result.rs:1084:5
stack backtrace:
   0: std::panicking::default_hook::{{closure}}
   1: std::panicking::default_hook
   2: std::panicking::rust_panic_with_hook
   3: std::panicking::continue_panic_fmt
   4: rust_begin_unwind
   5: core::panicking::panic_fmt
   6: core::result::unwrap_failed
   7: bayard::server::server::IndexServer::apply_entry
   8: bayard::server::server::IndexServer::async_applier::{{closure}}
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

Since integer data is expected, change the timestamp value to an integer value as follows:
"timestamp" :<PHONE_NUMBER>000,

The following error occurred:
thread 'thrd-tantivy-index0' panicked at 'This is not a date field.', /Users/m-osuka/.cargo/registry/src/github.com-1ecc6299db9ec823/tantivy-0.10.3/src/schema/value.rs:167:18
stack backtrace:
   0: std::panicking::default_hook::{{closure}}
   1: std::panicking::default_hook
   2: std::panicking::rust_panic_with_hook
   3: std::panicking::begin_panic
   4: tantivy::indexer::segment_writer::SegmentWriter::add_document
   5: tantivy::indexer::index_writer::index_documents
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

What format is good for expressing datetime in JSON?
Tantivy version is 0.10.3.

This is a bug. Let's fix it for 0.11 which should be released soonish.

Thank you for your reply!


Gripper Connection Problem

Hi,
I was able to install the ABB ros server on my Yumi robot, the server is working good for controlling the two arms using Orebro/yumi package. However I'm still having problems in connecting the grippers to the ROS server. I installed all the required files and modules for grippers control and I run the RAPID check program and I got no errors. The main problem is that the Grippers Motion Server and the Grippers State server are still not connected to the ROS server. Any help with this issue?? and some instructions to control the grippers

Hi,
I am answering also here for completeness sake. Try to run the yumi_gripper_node executable from the yumi_hw package. This should connect to the RAPID servers and should let you call open/close service calls for each hand.

I did so several times with different files from different branches. Even I made an edit in gripper_node.h by try to change the port value but without any benefit. The problem is that the  yumi_gripper_node  is not correctly connected to RAPID servers. That's why I'm not able  to call open/close service calls.
The GRIP_State and GRIP_motion servers are never connected to my ROS PC client even after running the node.

@YoshuaNava Hi Yoshua, I have been following the instructions on the wiki page. The arm control is working, however the grippers tasks is giving error with no description when the rapid scripts from the yumi_hw/grippers/* is used. It would be great if you can point if i am something missing. Seems like rapid scripts for gripper seems to have an error. Thank you.


Splink dummy data

Type of PR

[ ] BUG
[x] FEAT
[ ] MAINT
[ ] DOC

Is your Pull Request linked to an existing Issue or Pull Request?
No
Give a brief description for the solution you have provided
In writing some documentation, I realised that it might be useful, particularly for new users, to have some dummy data to get up-and-running with pre-baked into Splink, without them having to copy files and read in manually
This works simply from the user perspective - simply import splink_data_sets, and each attribute is a pandas dataframes:
from splink.datasets import splink_data_sets

df = splink_data_sets.fake_1000
...
linker = DuckDBLinker(df, settings)

Under-the-hood this downloads the dataset, or retrieves it from a local cache folder if it has been downloaded previously, so as not to bloat the size of the package. This only happens as datasets are accessed, so we could potentially include very large / rich datasets without any performance / storage penalty if they are never accessed.
There is a basic test - there should probably be more detailed tests which properly deal with stuff around downloading/caching, but that will be fairly fiddly so probably best as a follow-up.
Things not considered (probably for future PRs):

range of data sets to include
where the datasets should live
whether options aside from pandas would be useful (load directly into your backend?)
haven't checked if caching works properly when splink is installed
any kind of niceness if downloading is slow / fails

PR Checklist

[x] Added documentation for changes
[ ] Added feature to example notebooks at tutorials in splink_demos (if appropriate)
[x] Added tests (if appropriate)
[x] Made changes based off the latest version of Splink
[x] Run the linter

I've been meaning to reach out to your team about a related topic, because I've just gotten to beta on a python package for generating simulated data for cases like this: https://pseudopeople.readthedocs.io/
Might this be an opportunity to brainstorm potential pseudopeople integration into splink docs?  Let me know if
You can see a notebook using it with splink here: https://colab.research.google.com/drive/1YVnK1G9vk_RPqH4kv52eZj_qCC8UtWMS?usp=sharing

@aflaxman that looks fantastic.  I'd definitely be up for adding an example to the Splink docs that uses a dataset generated by pseudopeople.  Do you have a suggestion of a pre-created dataset that we could use?  Or would you suggest that the example both generates and then links a dataset?  If it turns out well we could also consider adding to these proposed inbuil datasets
Please could we continue the discussion here to separate it from this issue

@ADBond love this!  I'd probably start with the fake_1000 dataset only, simply because I think we want to think a little carefully about what are the best example datasets to include (i.e. which ones we actually want people to play with), but I wouldn't want that to sidetrack getting this feature added

@aflaxman that looks fantastic. I'd definitely be up for adding an example to the Splink docs that uses a dataset generated by pseudopeople. Do you have a suggestion of a pre-created dataset that we could use? Or would you suggest that the example both generates and then links a dataset? If it turns out well we could also consider adding to these proposed inbuilt datasets
Please could we continue the discussion here to separate it from this issue

Great, I've responded with some initial thoughts on #1361 .  Thanks to all of you for your work on this amazing project!

One additional thought, if these datasets are going to become more of a mainstay for Splink, do you think it is worth migrating all the datasets we are going to build in to a separate repo? Then they can be called from the demos or by users? It may not be worthwhile but just popped into my head that splink_demos and the data could be made separate as a result of this work.

All works as expected bar one small thing. When downloading the data I got a SSLCertVerificationError which I was able to get rid of using the ssl package with ssl._create_default_https_context = ssl._create_unverified_context which made it run fine, but may not be best practice.

Hmm that's strange - I wonder why the certificate was failing there. Have not been able to recreate this error.
What do you think the best thing to do here is? I'm a bit reluctant to put something like this directly in the package as it feels a little iffy to be getting people to bypass certification errors, but maybe if this error happens it could direct the user to a note with this workaround on the docs page (with some words of caution)?

One additional thought, if these datasets are going to become more of a mainstay for Splink, do you think it is worth migrating all the datasets we are going to build in to a separate repo? Then they can be called from the demos or by users? It may not be worthwhile but just popped into my head that splink_demos and the data could be made separate as a result of this work.

Yes I think ultimately it is probably worth separating out where the data lives to its own location. Might be worth a bit of a conversation about this when deciding any further datasets to include, and whether any alternate places to store them make any sense

@ADBond yes agreed that moving the data is a problem for another day once we figure out what our overall strategy for managing these datasets is.
On the Certification Error stuff - I will have another play with this to try and figure out why I was getting the issue. I'm just wary of merging something that could error out like this when it will go into tutorials, example notebooks etc

Hey ADBond, I have tried this with a few different environments this afternoon and it is working fine. Don't know what was happening the other day but I think this is good to go.
I will approve now, but a couple of small docs things before you merge. Would you mind:

Rebasing onto master and adding a blurb on inbuilt datasets on the documentation index page
Adding to the example in Getting Started

Hmm, that's weird. Can you open up a new issue for it and I can add it to my list?


discord-canary: 0.0.125 -> 0.0.126

Motivation for this change
discord-canary needs to be updated to 0.0.125 to 0.0.126 in order to function correctly
Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Relase notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Seems like its a duplicate of #128594


Support --polling parameter

https://github.com/purescript/purescript/issues/2249, on Windows we need this to lower the CPU usage, need to start purs ide server --pooling. https://github.com/kRITZCREEK/purescript-psc-ide/blob/master/src/PscIde/Server.purs does not support this now, except watch | !watch.

Do you maybe want to submit a PR? I think it's fine to just add a Boolean to the server args and add it to the command pretty printer.


Update status of resiliency issues.

Moved fixed issues to a separate section.
For still open issues link to the ES resiliency page instead of GH issues/PRs.

Something is wrong with gh here. doesn't show new commits. Opened https://github.com/crate/guide/pull/37 from a new branch.


[Task]: Show launch screen while app is loading on mobile

Task description
We need to add a splash screen for the mobile version of the application while it is loading.
Requirements

[ ] Design splash screen for mobile
[ ] Add splash screen to iOS project (light and dark)
[ ] Add splash screen to android project (light and dark)

Acceptance criteria
Splash screen is correctly displayed for each theme on both iOS and Android while the app is loading.
Creation checklist

[X] I have assigned this task to the correct people
[X] I have added the most appropriate labels
[X] I have linked the correct milestone and/or project

Icons was made with this https://github.com/ionic-team/capacitor-assets that could be used to splashscreens

refs:
https://developer.apple.com/design/human-interface-guidelines/ios/visual-design/launch-screen/
https://material.io/design/communication/launch-screen.html#usage
we should use this plugin https://capacitorjs.com/docs/apis/splash-screen
and call  SplashScreen.hide()

Since it's not possible to use light/dark launch screens with current Capacitor plugins, we'll need to create an specific one for this task.
I've added a new task to do this in the future. #2524


Add project_title in Project and create_project

What's in the PR
Project gains attribute project_title and create_project gains argument project_title
Linked to https://github.com/inception-project/inception/issues/5156
How to test manually
from pycaprio import Pycaprio
client = Pycaprio(inception_host = host, authentication = (user, password))
projects = client.api.projects()
print(projects)
projects[0].project_title

proj = client.api.create_project("hello_world", project_title = "Hello World", creator_name="other user")
proj.project_title
Automatic testing

[x] PR includes unit tests

Documentation

[x] PR updates documentation

@jwijffels Thanks for the PR. The linter fails. Try running make lint. I thought we had a make black as well... maybe that went missing when I changed the build setup...
I think it might be helpful if the pycaprio API mapped the fields not as in the response, but rather as what they mean:

title -> name
name -> slug

WDYT?

Thanks for taking over the maintenance of pycaprio!
I'll look into the linter.
About the change of title = name, name = slug, For me ok, but that's a breaking change. Not sure what is your position on breaking changes.

About the change of title = name, name = slug, For me ok, but that's a breaking change. Not sure what is your position on breaking changes.

I try to avoid them. That is why I didn't change the properties in the HTTP response JSON when I changed the name to be the slug and added the title. Because at the time, I couldn't make pycaprio releases and if I had made that change, it would have broken pycaprio for everybody.
However, we are pre-1.0.0. Also I think it is confusing if the names do not reflect the semantics.
I don't have a very strong opinion, but at some point, it needs to be changed anyway - so why not now?
If you have a better idea or different opinion, glad to hear it.

My preference is to always be backwards compatible where possible to avoid breaking changes but if you intend to have a lot more changes planned, yes it makes sense to do them. This slug/name also already got me confused as well :)


Charging Image shown when truck not charging

from rivian-charging-card.yml: 167-174

'- type: conditional
conditions:
- entity: binary_sensor.maeve_charger_connection
state_not: "on"
card:
type: picture-elements
image: >-
https://github.com/tmack8001/ha-rivian-card/blob/main/src/images/r1t/side_charging/dark/r1t-launch-green.png?raw=true'

Should this be linked to a side view image not plugged in?
Image is showing a plugged in R1T, when it is not charging

Probably, though there isn't a great image of the truck/suv from the side without the charging cable. The best you can get from rivian provided images is just the front end (see latest mobile app) and thus then makes it impossible to see a difference between R1T and R1S models.
I will likely add those images to this repo to have them to hold on to, also recently added them to the beta releases of HA so feel free to switch out to those if you prefer.


[FLOC-1174] Docker discover environment

Fixes FLOC-1174
This branch adds environment information to DockerClient.list, disregarding the HOME and PATH variables that are added to all containers, thereby returning only custom environment variables that have been injected as part of an image, links or when launching the container (i.e. an Application environment).
Also adds functionality to discover custom environment variables in P2PNodeDeployer, distinguishing between variables injected to represent links and custom environment.

I don't think we can merge this as is due to the calculation issue. We can discuss offline if you want.

Looks good, except for a bunch of missing tests. Once those are in and buildbot is green merge (don't want to merge this until we're sure acceptance tests pass!).


Feat/robustness epoch metrics

Adds possibility to track Epoch Metrics (metrics that are computed as an aggregate over intermediate results tracked during an epoch). Examples include tracking the robustness of the features coming from the encoder of a segmentation model wrt a slide's center, measured using AUC.

LGTM.


Batch Mapping & Sink

Summary
I'mm looking for the ability for a mapper and sink to take a batch of items at once. Today these take single item at once, regardless of readBatchSize limiting the ability to take advantage of bulk APIs/processing,.
Use Cases
I have three main use cases that interest me. All of these desire to operate at near real-time, and the messages aren't necessarily required to be ordered for histogram/statistic type metrics, Thus, horizontal scaling should be easy for my use cases

Bundling: I have a use case receiving 100k+ messages per sec, but each message is very small, < 1k. For throughput purposes it would make sense to take batches of those messages (say up to 1000), and group them into a single bundle. The overall MB of messages may not be changed, but it, from my rough experimentation, I can get more ISB throughput when operating on this smaller quantity of messages. Implementation of this bundling is of course user centric, but being able to receive mulitple messages at once would facilitate this.

Input would be N messages with 1-N responses (typically 1 in my personal use-case).

Bundled transactions: Some operations can be generally more efficient by sending multiple data items through at once vs a single call for each. Ex. Elasticsearch BatchAPI, or pykafka producer (ignoring numaflow's built-in kafka sink).

Typically more of a 'sink' use case,

Batching for performance: In a language like python, if you're doing the same operation on a lot of datasets using numpy/scipy/etc, it's useful to group them together and call the math logic once. If we could pull a batch of items at once, we can organize them for faster processing, and then write back out the results as appropriate.

This specific case would still be N messages in, N messages out, but could be combined with Bundling

If there's a way to accomplish any of this today, I'm happy to adopt that, but I don't think the reduce capability quite fits my expectations, particularly with the time based windows and limitations of horizontal scaling in order to meet the ordering expectations.

Message from the maintainers:
If you wish to see this enhancement implemented please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.
### Tasks
- [ ] GRPC and Protobuf Definitions (numaflow-go)
- [ ] Map Handling Implementation (numaflow)
- [ ] Python UDF Server Implementation (numaflow-python)

Since I'm interested in this, I wanted to take a first attempt at implementing this following the patterns that currently exist. I'll expect to have some PRs up shortly for first few items I made on check list over this week. This will be my first contribution to this community, so will hopefully be able to work well with everyone to work through details

@magelisk - For sinks, the batch operation is already there in the interface exposed to the developers with streaming data from the gRPC clients, I don't expect there will be too much performance enhancement to send the data with a unary call from the client in a batch.

I think we should do batching on top on gRPC streaming, we have an issue to track this https://github.com/numaproj/numaflow/issues/1564

Thanks for the input. I hadn't used the streaming sink so I wasn't familiar with it's interface taking the iterator, that's very useful.
Following that and the recommendation that at this be built on top of the streaming interface I think I've wrapped my head around this. I see that #1564 was already given an assignment to @yhl25 . I don't know if any work has been done on this on his part (I couldn't find anything in his accessible repos), so I did an initial draft for my own personal learning opportunity. I don't wan to step on anyone, so feel free to kick it away, but hopefully I can contribute something to help.
protodef: https://github.com/numaproj/numaflow-go/pull/129
numaflow core: https://github.com/numaproj/numaflow/pull/1707
python client: https://github.com/numaproj/numaflow-python/pull/163
The biggest question of these - I did this with a NEW gRPC endpoint, so now the mapping streamer has to Fn handlers. This is a deviation from existing patterns but allows maintaining backwards combability. Not sure how the numaflow team hope to handle these kinds of breakages generally speaking.

@magelisk, thank you for being a contributor to Numaflow. We (the Numaflow team) would like to know how the community and you are using the platform, learn about the use cases, and take some feedback. Would you be open for a chat with us based on your availability?

@syayi  would be happy to talk at some point. I'm generally pretty free, and US EST based

Thanks @magelisk ! Sure, drop me a note here or on slack based on what works best for you, and happy to schedule a call

We have a conversation tomorrow, but so that there's a written record I'll put this here now to solicit and document thoughts.
The currently implementation I did was one that has new gRPC call within existing service. This works, though breaks the 'function-only' method as-is. So I think there are a few options

Remove/Replace existing map function which takes a single datum and let it take the multiple requiring caller to iterate over stream explicitly

Consistent with user defined sink patter
Not quite consistent with a map handler function that's typically used

A new Service for this which contains single endpoint.

A fair bit of additional overhead/new classes that are nearly duplicates of existing. Could share common classes between protos, but again, this isn't something that's currently done so would need to balance DRY vs compartmentalization
Should maintain full backwards compability

Use as-is in current MR  (MapFn and BatchMapFn, and find some other work around, or adjust interface definition to have styles that still work with function-only patter

I think this is more complex, more moving parts, but should maintain existing backwards compatibility (I haven't prototyped this to see what final impact to the interface classes are

We have included this in the 1.3.0 release.


Class properties doesn't inherit types from interface

Moved from Microsoft/vscode#2881
From @moostad

#6118 should fix this, right @sandersn?

No, #6118 only fixes contextual typing of implemented properties. The fix is probably related, but they are two separate bugs.

Raw notes
Where did it come from: base class or implemented interface
Is it: Initializer, property declaration, method declaration, or constructor declaration

Initializers of property declarations without type annotations

Contextually type from base class if it exists
Contextually type from implemented interfaces if all declarations have identical types
Otherwise none

Method declarations

Return expressions get contextually typed by base signature's return type
Unannotated parameters get contextually typed by base signature's parameter types

Unannotated uninitialized declarations

Simply get base type's type
foo; is as if you had written foo = undefined;, e.g. get foo: string if that was your base type's foo

Same for static declarations and constructor parameters

This still seems to be an issue, any development on it? Feels trivial to re-type everything that is already defined in implemented interface

We re-discuss it every six months or so, and haven't come up with any new ways to fix it without breaking old code.

Tracking at #10570 now