findMany / OR accepts non-array value - should only accept arrays

Bug description
findMany accepts a non-array value when filtering with OR even though OR requires an array.
The following is 'allowed' but does NOT return the expected results:
  const orIncorrect = await prisma.post.findMany({
    orderBy: {
      id: 'asc'
    },
    where: {
      OR: {
        title: {
          equals: "Prisma makes databases easy"
        },
        authorId: {
          equals: 2
        }
      }
    }
  });

Correct syntax is:
const orCorrect = await prisma.post.findMany({
   orderBy: {
     id: 'asc'
   },
   where: {
     OR: [{
       title: {
         equals: "Prisma makes databases easy"
       },
     }, {
       authorId: {
         equals: 2
       }
     }]
   }
 })

Expected behavior
OR does not accept non-array value.
Prisma information
Schema from TypeScript starter project (https://www.prisma.io/docs/getting-started/quickstart?lang=typescript):
generator client {
  provider = "prisma-client-js"
}

datasource db {
  provider = "sqlite"
  url      = env("DATABASE_URL")
}

model Post {
  authorId  Int?
  content   String?
  id        Int     @default(autoincrement()) @id
  published Boolean @default(false)
  title     String
  User      User?   @relation(fields: [authorId], references: [id])
}

model User {
  email   String   @unique
  id      Int      @default(autoincrement()) @id
  name    String?
  Post    Post[]
  Profile Profile?
}

model Profile {
  bio    String?
  id     Int     @default(autoincrement()) @id
  userId String  @unique
  User   User    @relation(fields: [userId], references: [id])
}

Environment & setup

Prisma version: 2.0.0-beta.2

Thanks for reporting!
Although the behavior is very ugly, it's the expected behavior right now.
Therefore I remove the bug label.
This is for sure something we can change, just a bit of more thinking and product work is needed.

Here's the relevant internal discussion.

Thanks a lot for reporting 🙏
This issue is fixed in the latest alpha version of @prisma/cli.
You can try it out with npm i -g @prisma/cli@alpha.
In case it’s not fixed for you - please let us know and we’ll reopen this issue!


[SPARK-29914][ML][FOLLOWUP] CountVectorizer del big attribute array

What changes were proposed in this pull request?
CountVectorizer del big attribute array
Why are the changes needed?
Previous discussion is here

vocabulary is a big number, for example 1 << 18 by default. We will keep a big attribute array here.

Does this PR introduce any user-facing change?
No
How was this patch tested?
existing testsuites

Test build #114900 has started for PR 26767 at commit a7876a0.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/19722/
Test PASSed.

Test build #114900 has finished for PR 26767 at commit a7876a0.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/114900/
Test FAILed.

ping @viirya
I am going to remove the large attribute array in CountVectorizer, but it will revert https://github.com/apache/spark/pull/20313
How do you think about it?

oh, I see. This is long time ago.
Going to remove attributes from CountVectorModel will make some transformer fail. I think it will be a regression.

OK, I will close this PR


Support custom fs (tailing)

This allows one to provide a custom fs implementation to send with .e.g. tailing (growing) support.

Hi @ronag, thanks for your pull request! If you can, please check out the tests, as there are a bunch of failures with these changes.
I also don't see anything about a .growing property in the Node.js documentation: https://nodejs.org/api/fs.html#fs_class_fs_stats what does it mean and where does it come from?
In addition, I'm not sure about this module ever sending back a 202, because it is described as the following in RFC 7231:

The 202 (Accepted) status code indicates that the request has been accepted for processing, but the processing has not been completed. The request might or might not eventually be acted upon, as it might be disallowed when processing actually takes place.  There is no facility in HTTP for re-sending a status code from an asynchronous operation.
The 202 response is intentionally noncommittal.  Its purpose is to allow a server to accept a request for some other process (perhaps a batch-oriented process that is only run once per day) without requiring that the user agent's connection to the server persist until the process is completed.  The representation sent with this response ought to describe the request's current status and point to (or embed) a status monitor that can provide the user with an estimate of when the request will be fulfilled.

To me, that describing the accepting of the given request (i.e. the GET or HEAD request that this module will respond to), rather than indicate that some process is still pending (i.e. that you're checking to see if something is done yet).

Hi @ronag, I'm closing this due to no response in over 2 months. If you get back to me on my questions/comments above, I'll happily re-open this pull request!


RouterLink renders href with full file path in hash mode

In hash mode the rendered href includes the full file url. Should be just the hash.

I realised in vue router 3, the full file url is also included when there is a base but otherwise the href only has the hash. Since the base is already on the URL, I imagine it would make sense to make it consistent and always have only the hash.
What does this change at the end?


Web - Chat - Contacts are not displayed in LHN when trying to fetch a chat for a closed account

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Go to https://staging.new.expensify.com
Log in with<EMAIL_ADDRESS>(credentials below)
Check your contacts in LHN

Expected Result:
Contacts are displayed in LHN for any account
Actual Result:
Contacts are not displayed. Occurs only with this account
Email used<EMAIL_ADDRESS>Password : Feya86Katya
Workaround:
Unknown
Platform:

Where is this issue occurring?

Web

Version Number: <IP_ADDRESS>
Reproducible in staging?: Yes
Reproducible in production?: Yes
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos:
https://user-images.githubusercontent.com/43996225/139500413-6b552c94-1ea6-4591-ad2f-77674766dba0.mp4
https://user-images.githubusercontent.com/43996225/139500399-2d9f7a7f-2777-4a7d-b3b6-9664a1f51118.mp4
Email used<EMAIL_ADDRESS>Password : Feya86Katya
Expensify/Expensify Issue URL:
Issue reported by: Applause
Slack conversation:
View all open jobs on GitHub

Triggered auto assignment to @danieldoglas (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

Starting to work on this.

@kavimuru , is it only happening if 2FA is enabled, or if you disable will it also happen?
Also, is there a way for me to access that account?

Issue reproducible during KI retests.

@danieldoglas The issue is only happening with this account
Staging credentials. You should be able to login
Email used<EMAIL_ADDRESS>Password : Feya86Katya

@mvtglobally even in staging, I can't access that account because of 2FA.

If you disable 2FA, is the bug still happening? If not, please disable so I can debug it.
And in case it only happens when 2FA is enabled, I can enable it on my device and disable again for you.

@mvtglobally let me know if you have any news on this.

I'll change this issue to Weekle.

@danieldoglas  I am getting confirmation. Will share update shortly

@danieldoglas  tester removed 2FA and looks like issue is still reproducible. You should be able to login now using the same credentials as mentioned above

Thank you @mvtglobally !

Get chatList is returning 200+ chats.

After using chatList we call reportSummaryList. This method is returning an error:
  "jsonCode": 404,
  "message": "Auth GetRestrictedAuthTokenByEmail returned an error",
  "codeRevision": "b063edb61e2aaadeeda087e5895e2cfebf31dc07",
  "requestID": "6ac194558dd83338-SAN"
}```

Probably that's why we can't list the chats.

Investigating what's happening there. I suspect it is related to the amount of chats this account has.

Did a test request.
logs here
Seems like we couldn't find personal details for<EMAIL_ADDRESS>and there was a chat previously created with that user.

The account<EMAIL_ADDRESS>was closed in 2021-10-18, and when we try to get a Token for it, we're sending 'receiptUpload' as a type. In our conditions, we don't allow a token generation for closed accounts with that type (GetRestrictedToken.cpp line 121-127).
@pecanoro , it seems like you were the last one to change something in this logic. Do you know if we can get a token in this case?

Hmm, this is really interesting, if they account is closed they should be getting the prompt to reopen the account by email verification and not this. Maybe the flow does not work properly when 2FA is enabled. cc/ @bondydaa

tester removed 2FA and looks like issue is still reproducible.

To confirm this problem is happening without 2FA enabled as well right?
Daniel looks right that we're just failing to get a restricted authToken for the user who has a closed account.
6ac194558dd83338-SAN | virt1.sjc | 2021-11-10 19:10:11 016 |<EMAIL_ADDRESS>| Bedrock\Client - Starting a request ~~ command:  'GetRestrictedAuthToken' clusterName: 'auth' headers: '[email<EMAIL_ADDRESS>type:  'receiptUpload' validateCode: '<REDACTED>' partnerName:  'expensify.com' idempotent: '1' logParam<EMAIL_ADDRESS>commitCount: '13979113877' requestID: '6ac194558dd83338-SAN' lastIP:  '<IP_ADDRESS>' writeConsistency: 'ASYNC' priority: '500' timeout:  '290000']'
6ac194558dd83338-SAN | db2.sjc | 2021-11-10 19:10:11 017 |<EMAIL_ADDRESS>|<EMAIL_ADDRESS>request authtoken type = receiptUpload
6ac194558dd83338-SAN | db2.sjc | 2021-11-10 19:10:11 018 |<EMAIL_ADDRESS>| Throwing exception with message: '404 Account not found' from auth/command/GetRestrictedAuthToken.cpp:131
6ac194558dd83338-SAN | db2.sjc | 2021-11-10 19:10:11 018 |<EMAIL_ADDRESS>| Error processing command 'GetRestrictedAuthToken' (404 Account not found), ignoring.
6ac194558dd83338-SAN | db2.sjc | 2021-11-10 19:10:11 018 |<EMAIL_ADDRESS>| Transaction rollback with 3 queries attempted, 0 served from cache.
6ac194558dd83338-SAN | db2.sjc | 2021-11-10 19:10:11 018 |<EMAIL_ADDRESS>| command 'GetRestrictedAuthToken' timing info (ms): 1 (1), 0 (0), 0, 0, 0, 0, 1, 0, 0. Upstream: 0, 0, 0, 0.
6ac194558dd83338-SAN | db2.sjc | 2021-11-10 19:10:11 018 |<EMAIL_ADDRESS>| About to reply to command GetRestrictedAuthToken
6ac194558dd83338-SAN | db2.sjc | 2021-11-10 19:10:11 018 |<EMAIL_ADDRESS>| Replied
6ac194558dd83338-SAN | virt1.sjc | 2021-11-10 19:10:11 018 |<EMAIL_ADDRESS>| Bedrock\Client - Request finished ~~ host: 'db2.sjc' command:  'GetRestrictedAuthToken' jsonCode: '404 Account not found' duration: '2'  net: '0.717' wait: '1.283' proc: '0' commitCount: '13979113877'
6ac194558dd83338-SAN | virt1.sjc | 2021-11-10 19:10:11 018 |<EMAIL_ADDRESS>| Auth - AuthRequest #41 ~~ command: 'GetRestrictedAuthToken' jsonCode: '404' size: '181' duration: '2ms' host: 'db2.sjc'
6ac194558dd83338-SAN | virt1.sjc | 2021-11-10 19:10:11 018 |<EMAIL_ADDRESS>| Auth - Call GetRestrictedAuthToken return 404
6ac194558dd83338-SAN | virt1.sjc | 2021-11-10 19:10:11 018 |<EMAIL_ADDRESS>| Throw ExpException - 5a298b2fb32635da318ee93f6e1feeee ~~ message: '404  Account not found' exceptionMessage: 'Auth GetRestrictedAuthTokenByEmail  returned an error' exceptionFile:  '/git/releases/expensify.com/b063edb/lib/Auth.php' exceptionLine: '112'  exceptionCode: '404'

I'm not sure why we're calling to get a restricted authToken here so I would try to figure out why we're doing that and if it's 100% necessary, if it is needed then maybe see if we can check to see if the account we're trying to get the token for is closed before making the call OR make sure we gracefully handle the error being thrown so that it doesn't prevent loading of all chats because an account is closed.

@bondydaa , you are right. I'll do a review on the flow to check why we do that.

Working on some daily tasks, will get back to this later.

Back to reviewing this task.

Changed to monthly for now.

Triggered auto assignment to @NicMendonca (Internal) because issue was reported by a contributor who needs to be compensated if this issue is fixed

☝ not reported by contributor so removing my assignment


Can't use project's root folder in runner config

Package version
4.0.0
Describe the bug
Hi,
When I try to use project's root folder to set up runner config, I'm getting the following error
   ReferenceError: describe is not defined

   ⁃ Object.<anonymous>
     node_modules/json-schema-traverse/spec/index.spec.js:6
   ⁃ async importFiles
     node_modules/@japa/runner/build/index.js:151

My bin/test.js file looks like
import { assert } from '@japa/assert'
import { pathToFileURL } from 'node:url'
import { apiClient } from '@japa/api-client'
import { specReporter } from '@japa/spec-reporter'
import { processCliArgs, configure, run } from '@japa/runner'

configure({
  ...processCliArgs(process.argv.slice(2)),
  ...{
    files: ['./**/*.spec.js'],
    plugins: [assert(), apiClient('http://localhost:3333')],
    reporters: [specReporter()],
    importer: (filePath) => import(pathToFileURL(filePath).href),
  },
})

run()

Reproduction repo
No response

What is describe? Japa does not have any method called describe

Okay, I think I get it.
The error is coming from the node_modules, so it seems like the files glob is reading and importing files from node_modules as well.
I think, we will need a way to ignore certain directories. I will fix it

Fixed in https://github.com/japa/runner/releases/tag/v3.1.0


Data Export not working

Dear Team,
Currently it's not possible to export data from projects. After clicking "Generate", the loading indicator stays forever and the system seems to be stuck in generating the file.
Any help would be appreciated!

Thanks for the notice. Exports should be working again. We had an issue where a new feature was using up all capacity, preventing other tasks from being run.

Yes, it works again. Thanks!


Annotate references with the name of the function in which they occur

When finding references, it would be really useful if each reference was annotated with the name of the function in which the reference occurs (in addition to the name of the file, which is already there).
For example, given this code:
void target();

void function1() {
  target();
}

void function2() {
  target();
}

if you perform "Find References" on target(), I would like an editor to be able to show output similar to this:

Notice how, beside each reference, there is the name of the function in which the reference occurs.
In terms of implementation, this likely needs the same sort of infrastructure as call hierarchy (storing a SymbolID inside Ref).

Today LSP doesn't have a way of attaching "snippets/details" to references response (it's just a list of locations). this might be implemented as an extension, but on the client side requires extra work to display that detail and most of the clients already display the text at the reference side as a snippet.
So I don't think this is worth as providing an extension today, even though we have all the infra ready. WDYT @HighCommander4 ?

(oops didn't mean to close)

In my experience, this is one of the most noticeable remaining feature gaps between clangd and Eclipse CDT. The "code surrounding the reference" snippet helps somewhat, but is only a few lines long and typically needs to be scrolled to bring function name into view.
I'd like to work on an extension that implements this (including an LSP extension), just haven't gotten around to it yet.

I found this idea quite interesting and wanted to try it out at work next week, so I threw together a quick and dirty prototype here: https://reviews.llvm.org/D137894
@HighCommander4 Are you still planning on working on this?

@tom-anders I would love to have this! I haven't had a chance to get to it myself -- if you're interested in working on it, please feel free!
Note that it will require client-side changes too (until a suitable LSP extension is accepted upstream).

Cool, I'll polish up the patch a bit in the next few days then :)
Regarding client side changes: I'm using neovim's builtin LSP, so I'd be happy to adapt clangd_extensions.nvim for this. Someone else would need to adapt the vscode plugin though.

Yeah I can believe this is really useful, refs is a heavily-used feature and benefits from context for quickly scanning the list.
However the VSCode extension API (which their LSP library implements) has no facility to include this information, it's just a list of Locations. So I think this can't be implemented in vscode-clangd without reinventing the several find-refs UIs in VSCode (which I think is probably a bad idea outside prototyping, for maintenance reasons).
So this likely needs to be a feature request to VSCode itself rather than just LSP (I think it's a good one, but that doesn't mean it'll be added). Happy to vote for such a FR!
IMO this shouldn't block adding the extension to clangd: it seems useful and unintrusive enough even without vscode support.


Updated link

Fixed old url to Which mode to use

@bezbeli thx for the PR, I've fixed all workbox broken links on #304 using this PR, thx again for the contribution


Migrating Superset from version  0.22.1 to version 0.35.0

We are currently running on superset 0.22.1 with python 2.7 on Ubuntu 16.04 LTS.
We are planning to upgrade superset to 0.35.0 version with python 3.6.9 on Ubuntu 18.04.3 LTS.
Can you kindly let us know whether we can use old superset 0.22.1 dashboards after upgrading to superset 0.35.0 ?
OR
Should we build all the superset dashboards from scratch after upgrading to 0.35.0 version ?
Environment

OS: Ubuntu 16.04 LTS
superset version:  0.22.1
python version:  2.7

Hi @srikark16, thanks for the question! 0.22.1 is certainly an older version at this point. I can't tell you with certainty that everything will work. Superset is pre-1.0 so breaking changes are not out of the question at this point.
My recommendation for an upgrade that substantial would be to duplicate Superset's metadata database, set up a new install of Superset configured to point at the copy, and perform the upgrade on that. You'll then be able to check on your charts and dashboards in the new version to determine the best approach for your organization. I hope that's helpful!

Thank you @willbarrett

@srikark16 @willbarrett  Hi,  How do I upgrade？ Now, I want Migrate Superset from version 0.30.1 to version 0.35.0,  I backed up the Database ， use 0.35.0 connect copy database,  then commnd：superset db upgrade,  the error :ERROR [root] Error: Can't locate revision identified by 'e96dbf2cfef0'

same happening here. what can i do?

current revision:
superset=> select * from alembic_version
superset-> ;
 version_num
--------------
 f959a6652acd
(1 row)


Please update README to reflect release of Dialogflow Enterprise Edition Beta

Declining to do this for the moment unless asked by the API team. They have been consistently asking that we keep Dialogflow things out of this area for branding reasons.
If this request is from the API team and you were forwarding, please reopen. :-)


Getting wrong error "Strings not allowed in JSX files" in prop

I'm getting error in this:
<div className={`col-12 grid input-cont ${shouldUseDefaultClasses && defaultContClass} ${contClass}`}>

The error is:
error  Strings not allowed in JSX files: “`col-12 grid input-cont ${shouldUseDefaultClasses && defaultContClass} ${contClass}`”  react/jsx-no-literals

There is no string in the className, not sure what am I missing here.

Is this something I could start working with? Or is it WIP?

@pawelnvk #2146 already exists

My mistake 😄 Thanks.

@pawelnvk #2146 already exists

Should this issue be closed then?

Yep, now that it's merged. Thanks!


generics on abstract classes where a superclass explicitly declares them are 'unknown' when inferred unless there is some implementation.

Bug Report
🔎 Search Terms
infer, generics, class, superclass, extends, abstract classes

🕗 Version & Regression Information
tried on version 5.0.3, 5.1.5, and nightly.

This is the behavior in every version I tried, and I reviewed the FAQ for entries about inference, classes, generics, and superclasses

⏯ Playground Link
Playground link with relevant code
💻 Code

// this does not work

// setup for test 1
abstract class ISchemaOne<R> {}
class ExtendedSchemaOne<N, R> extends ISchemaOne<N | R> {}
type SchemaTypeOne<T> = T extends ISchemaOne<infer R> ? R : never;

// test 1
type Test1 = SchemaTypeOne<ISchemaOne<string>>; // string
type Test2 = SchemaTypeOne<ExtendedSchemaOne<string, number>>; // expected (string | number) got unknown

// this *does* work

// setup for test 2
abstract class ISchemaTwo<R> {
    private nop(v: R) {}
}
class ExtendedSchemaTwo<N, R> extends ISchemaTwo<N | R> {}
type SchemaTypeTwo<T> = T extends ISchemaTwo<infer R> ? R : never;

type Test3 = SchemaTypeTwo<ISchemaTwo<string>>; // string
type Test4 = SchemaTypeTwo<ExtendedSchemaTwo<string, number>>; // (string | number)

🙁 Actual behavior
when there is no method or property on an abstract classes that uses the generic, even though the generic is explicitly defined by the superclass, an infer will return unknown rather than the expected type.
🙂 Expected behavior
an explicitly declared generic should not be unknown when inferred by another type.

https://github.com/microsoft/TypeScript/wiki/FAQ#why-doesnt-type-inference-work-on-this-interface-interface-foot--

Remember: You should never have unused type parameters!

ah-hah fair enough.
Sorry for taking up the time.

@RobMayer I like to explain it like this: generic inference is structural, so inferring an unused type argument is like asking TS to solve for x * 0 = 0 - not only is any x is a valid solution but you can’t possibly recover the original x from only the 0 you got as output.


fix: broken FieldNote test

...
Checklist:
Remove the checklist to signal you've completed it. Enable auto-merge if the PR is ready to merge.

[ ] If the pull request requires a cryptography review (e.g. cryptographic algorithm implementations) I have added the 'crypto' tag.
[ ] I have reviewed my diff in github, line by line and removed unexpected formatting changes, testing logs, or commented-out code.
[ ] Every change is related to the PR description.
[ ] I have linked this pull request to relevant issues (if any exist).

Benchmark results
No metrics with a significant change found.

Detailed results
All benchmarks are run on txs on the Benchmarking contract on the repository. Each tx consists of a batch call  to create_note and increment_balance, which guarantees that each tx has a private call, a nested private call, a public call, and a nested public call, as well as an emitted private note, an unencrypted log, and public storage read and write.
This benchmark source data is available in JSON format on S3 here.
Values are compared against data from master at commit db67aa1e and shown if the difference exceeds 1%.
L2 block published to L1
Each column represents the number of txs on an L2 block published to L1.

Metric
8 txs
32 txs
128 txs

l1_rollup_calldata_size_in_bytes
45,444
179,588
716,132

l1_rollup_calldata_gas
222,996
868,184
3,447,800

l1_rollup_execution_gas
842,083
3,595,292
22,203,169

l2_block_processing_time_in_ms
2,015
7,496 (-1%)
29,833

note_successful_decrypting_time_in_ms
290
854
3,116 (-3%)

note_trial_decrypting_time_in_ms
93.0
61.0
134 (-1%)

l2_block_building_time_in_ms
13,219
52,522
209,207

l2_block_rollup_simulation_time_in_ms
11,897
47,281 (+1%)
188,125

l2_block_public_tx_process_time_in_ms
1,280
5,109
20,586

L2 chain processing
Each column represents the number of blocks on the L2 chain where each block has 16 txs.

Metric
5 blocks
10 blocks

node_history_sync_time_in_ms
21,607
42,279

note_history_successful_decrypting_time_in_ms
2,027 (-1%)
3,955 (-1%)

note_history_trial_decrypting_time_in_ms
119 (-2%)
144 (-23%)

node_database_size_in_bytes
1,628,585
1,097,883

pxe_database_size_in_bytes
29,748
59,307

Circuits stats
Stats on running time and I/O sizes collected for every circuit run across all benchmarks.

Circuit
circuit_simulation_time_in_ms
circuit_input_size_in_bytes
circuit_output_size_in_bytes

private-kernel-init
72.3
61,697
18,841

private-kernel-ordering
43.6
24,233
8,089

base-rollup
1,773
656,309
811

root-rollup
77.6
4,072
1,097

private-kernel-inner
53.6 (+1%)
81,504
18,841

public-kernel-private-input
41.8 (+1%)
41,455
18,841

public-kernel-non-first-iteration
26.7 (+1%)
41,497
18,841

merge-rollup
0.964 (+6%)
2,592
873

Miscellaneous
Transaction sizes based on how many contracts are deployed in the tx.

Metric
0 deployed contracts
1 deployed contracts

tx_size_in_bytes
8,723
27,240


Strava sync Github action fails...

果然被玩坏了 =_=|||

root cause https://github.com/hozn/stravalib/issues/215 fixed yesterday. kudos


MINOR: update release script for streams quickstart

@guozhangwang these are the updates i think are needed for the release script. I've verified that the sed command works, but i don't know how i can possibly test the rest of the script.

Thanks for doing this! This could be tested by doing a fake 1.0.0 RC0.

@ijuma the release script aborts because there are open JIRAs tagged with 1.0.0.

I had forgotten about that. What I did in the past is comment out the JIRA and local changes check, which is a bit painful. Maybe we could change the script so that there's a way to ignore the JIRA check.

There is another file where you need to remove -SNAPSHOT: in quickstart/java/src/main/resources/archetype-resources/pom.xml
<properties>
        <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
        <kafka.version>1.0.0-SNAPSHOT</kafka.version>
        <slf4j.version>1.7.7</slf4j.version>
        <log4j.version>1.2.17</log4j.version>
    </properties>

I've updated the release script to include the archetype-resources/pom.xml. Also fixed it so that it works and tested it (painfully)

@dguy do you want to address @ijuma 's comment before merging this PR?

We don't need to block this PR on that. Would be good to file a JIRA for it though.

it would be good to have dryrun option that skips that step and perhaps some others?

@dguy yeah, something like that would be helpful.

I created: https://issues.apache.org/jira/browse/KAFKA-5939

Merged to trunk.


[Fix][broker] Fix JDK17 compatibility issues.

Fixes #15539
Master Issue: #15539
Motivation
See #15539
Modifications

Add --add-opens java.base/sun.net=ALL-UNNAMED
Add --add-opens java.management/sun.management=ALL-UNNAMED

Verifying this change

[x] Make sure that the change passes the CI checks.

Documentation

[x] no-need-doc
[x] doc-not-needed

@heesung-sn
Please take a look, thanks.

Thank you for taking care of this issue. I am wondering if removing reflection could resolve the issue too. Adding --add-opens seems radical unless required.
For example, can we directly use the static functions in InetAddressCachePolicy for this code?, https://github.com/openjdk/jdk17/blob/master/src/java.base/share/classes/sun/net/InetAddressCachePolicy.java#L154-L160
static {
        int ttl = DEFAULT_TTL;
        int negativeTtl = DEFAULT_NEGATIVE_TTL;
        try {
            // use reflection to call sun.net.InetAddressCachePolicy's get and getNegative methods for getting
            // effective JDK settings for DNS caching
            Class<?> inetAddressCachePolicyClass = Class.forName("sun.net.InetAddressCachePolicy");
            Method getTTLMethod = inetAddressCachePolicyClass.getMethod("get");
            ttl = (Integer) getTTLMethod.invoke(null);
            Method getNegativeTTLMethod = inetAddressCachePolicyClass.getMethod("getNegative");
            negativeTtl = (Integer) getNegativeTTLMethod.invoke(null);
        } catch (NoSuchMethodException | ClassNotFoundException | InvocationTargetException
                 | IllegalAccessException e) {
            log.warn("Cannot get DNS TTL settings from sun.net.InetAddressCachePolicy class", e);
        }
        TTL = useDefaultTTLWhenSetToForever(ttl, DEFAULT_TTL);
        NEGATIVE_TTL = useDefaultTTLWhenSetToForever(negativeTtl, DEFAULT_NEGATIVE_TTL);
    }

Similarly for this code path, we can use the static functions in ManagementFactoryHelper
https://github.com/openjdk/jdk17/blob/master/src/java.management/share/classes/sun/management/ManagementFactoryHelper.java
    private static Method getTotalSafepointTimeHandle;
    private static Method getSafepointCountHandle;

    private Map<String, GCMetrics> gcMetricsMap = new HashMap<>();

    static {
        try {
            runtime = Class.forName("sun.management.ManagementFactoryHelper")
                    .getMethod("getHotspotRuntimeMBean")
                    .invoke(null);
            getTotalSafepointTimeHandle = runtime.getClass().getMethod("getTotalSafepointTime");
            getTotalSafepointTimeHandle.setAccessible(true);
            getSafepointCountHandle = runtime.getClass().getMethod("getSafepointCount");
            getSafepointCountHandle.setAccessible(true);

            // try to use the methods
            getTotalSafepointTimeHandle.invoke(runtime);
            getSafepointCountHandle.invoke(runtime);
        } catch (Throwable e) {
            log.warn("Failed to get Runtime bean", e);
        }
    }

@heesung-sn
I see, thanks for your explanation, I will try to another way solve this problem.
Convert this PR to draft.

#15349 is about DnsResolverUtil

@heesung-sn The benefit of the reflection based solution is that it's possible to target Java 8 with --release 8 (maven.compiler.release) when compiling with Java 17. Since DnsResolverUtil must support targeting Java 8, I don't think we have another option than using the --add-opens solution for DnsResolverUtil.
IIRC, --add-exports will be needed at compile time when reflection isn't used and I don't think that is compatible with --release 8. That's the reason for the use of reflection in both of these cases.
It might be better to get rid of the sun.net.InetAddressPolicy class usage and just duplicate the logic in DnsResolverUtil.

Ack. If there is no other option, I am ok with the --add-opens solution. Thank you for clarification.

@mattisonchao Please help create a PR for branch-2.10, lots of conflicts when I cherry-picking this PR.

@mattisonchao Please help create a PR for branch-2.10, lots of conflicts when I cherry-picking this PR.

+1 @mattisonchao

@mattisonchao Please help create a PR for branch-2.10, lots of conflicts when I cherry-picking this PR.

+1 @mattisonchao  I am cherry-picking this PR to branch-2.10. But I found the place of this PR modified does not exist in branch-2.10.
Could you please take a look at whether this Pr needs to cherry-pick to branch-2.10?


How can I disable/hide this footer section in a post?

Create a flag that indicates hide/show ContentBottomMdx?

Hi!
If I understand correctly what you want to do, do this:
In src/gatsby-theme-chronoblog/
Create a file called content-bottom.mdx
Inside, fill it like this:
<hr />
<FeedSearch />
<Tags />
<FeedItems />

And ... now you can add and remove anything from here. You can leave it empty and then there will be nothing, or add or remove something.

Magic.
The building process will take my custom content-bottom.mdx instead of gatsby-theme-chronoblog 's content-bottom.mdx, right?

Yes, this is called "Shadowing", you can read more about it here: https://www.gatsbyjs.org/docs/themes/shadowing

Let me try.
Thank you very much <3


'lxc stop' starts hanging after some time of LXD daemon's hard work

Distribution: Ubuntu
Distribution version: 16.04 (xenial)

# lxc info
config:
  core.https_address: '[::]:8443'
  images.compression_algorithm: pbzip2
api_extensions:
- storage_zfs_remove_snapshots
- container_host_shutdown_timeout
- container_stop_priority
- container_syscall_filtering
- auth_pki
- container_last_used_at
- etag
- patch
- usb_devices
- https_allowed_credentials
- image_compression_algorithm
- directory_manipulation
- container_cpu_time
- storage_zfs_use_refquota
- storage_lvm_mount_options
- network
- profile_usedby
- container_push
- container_exec_recording
- certificate_update
- container_exec_signal_handling
- gpu_devices
- container_image_properties
- migration_progress
- id_map
- network_firewall_filtering
- network_routes
- storage
- file_delete
- file_append
- network_dhcp_expiry
- storage_lvm_vg_rename
- storage_lvm_thinpool_rename
- network_vlan
- image_create_aliases
- container_stateless_copy
- container_only_migration
- storage_zfs_clone_copy
- unix_device_rename
- storage_lvm_use_thinpool
- storage_rsync_bwlimit
- network_vxlan_interface
- storage_btrfs_mount_options
- entity_description
- image_force_refresh
- storage_lvm_lv_resizing
- id_map_base
- file_symlinks
- container_push_target
- network_vlan_physical
- storage_images_delete
- container_edit_metadata
- container_snapshot_stateful_migration
- storage_driver_ceph
- storage_ceph_user_name
- resource_limits
- storage_volatile_initial_source
- storage_ceph_force_osd_reuse
- storage_block_filesystem_btrfs
- resources
- kernel_limits
- storage_api_volume_rename
- macaroon_authentication
- network_sriov
- console
- restrict_devlxd
- migration_pre_copy
- infiniband
- maas_network
api_status: stable
api_version: "1.0"
auth: trusted
public: false
auth_methods:
- tls
environment:
  addresses:
  - x.x.x.x:8443
  - y.y.y.y:8443
  architectures:
  - x86_64
  - i686
  certificate: |
    -----BEGIN CERTIFICATE-----
    ...
    -----END CERTIFICATE-----
  certificate_fingerprint: 9d138df151b84d54a9d3583dab6859759910911922481c3afc40b07291dae84f
  driver: lxc
  driver_version: 2.0.8
  kernel: Linux
  kernel_architecture: x86_64
  kernel_version: 4.4.0-104-generic
  server: lxd
  server_pid: 13090
  server_version: "2.21"
  storage: zfs | dir
  storage_version: <IP_ADDRESS>-0ubuntu16 | 1

I have couple of VMs acting as Jenkins nodes for building LXD images. Containers are constantly being created, configured, published and deleted, mostly several containers in parallel.
After some undetermined time of such work a node stops serving LXD commands. systemctl restart lxd usually solves the problem, but sometimes it hangs as well and I have to reboot the node.
Today it hung again and I had a couple of minutes to investigate. This time it acts like this: you can create container, but when you try to stop it with lxc stop <container-name>, it hangs. You can take a look at lxc list (terminate command execution with Ctrl+C or open another session) to see the container has actually been stopped.
/var/log/lxd/<container-name>/lxc.log says:
lxc_commands - commands.c:lxc_cmd_rsp_recv:177 - Command get_cgroup failed to receive response: Connection reset by peer.

strace says lxc stop process waits on futex:
strace -fp $(pgrep -f 'lxc stop')
strace: Process 26142 attached with 6 threads
[pid 26142] futex(0xe482d0, FUTEX_WAIT, 0, NULL <unfinished ...>
[pid 26147] futex(0xc420178110, FUTEX_WAIT, 0, NULL <unfinished ...>
[pid 26146] futex(0xe673e0, FUTEX_WAIT, 0, NULL <unfinished ...>
[pid 26145] futex(0xc420034b90, FUTEX_WAIT, 0, NULL <unfinished ...>
[pid 26144] epoll_wait(4,  <unfinished ...>
[pid 26143] restart_syscall(<... resuming interrupted futex ...>

Output of lxc stop --debug <container-name> and lxc monitor are attached to the issue.
lxd_monitor.log
lxd_stop.log

Are you seeing any lxc-monitord processes on your system? If so, does killing that process help?
Also, does passing --force to lxc stop fix this issue?
When calling lxc stop without --force, all that LXD does is send a signal to the container's init process, then wait for it to turn itself off. That's very similar to sending an ACPI event to your VM for a clean shutdown.
So it can be that for some reason your init system in the container is misbehaving too. Trying with --force would clarify that.

Yes, I'm seeing lxc-monitord process. Killing that process makes lxc stop execution fail with an error "shutting down the container failed", but after that start/stop operations go smoothly. lxc-monitord is running again after that.
Since killing lxc-monitord worked, I haven't had a chance to try lxc stop --force.
Is lxc-monitord's misbehavior some kind of known fact and are there any workarounds to prevent it from hanging?

Yeah, lxc-monitord is known to occasionally hang, in which case killing it usually unsticks whatever's going on. We've fixed that particular issue in liblxc 2.0.9, unfortunately most distros aren't yet on that version and so still suffer from this issue.
In your case, an option would be to switch from the LXD deb that you're using (out of backports it looks like) and switch to the LXD snap instead. The snap bundles a much more recent version of liblxc which actually entirely did away with lxc-monitord.
You may want to try that on one of your systems, the migration should just be:

snap install lxd
lxd.migrate

Which will walk you through moving all existing data from the deb to the snap and subsequently removing the deb from your system.
Closing this issue since it's a liblxc issue which has already been corrected upstream.


vimPlugins.eyeliner-nvim: init at 2023-09-16

Description of changes

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release 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

[x] Fits CONTRIBUTING.md.

> nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD"
Nothing to be built

Looks like it's just been added.


dependancy 3.0.1-SNAPSHOT not found

After adding the repository to the top of my maven pom file:
<repositories>
        <repository>
            <id>sonatype</id>
            <url>https://oss.sonatype.org/content/repositories/snapshots/</url>
            <snapshots />
        </repository>
</repositories>

when i adjust the dependancy to use the version 3.0.1-SNAPSHOT:
<dependency>
    <groupId>com.jayway.restassured</groupId>
    <artifactId>rest-assured</artifactId>
    <version>3.0.1-SNAPSHOT</version>
</dependency>

I get dependancy 3.0.1-SNAPSHOT not found.
Failure to find com.jayway.restassured:rest-assured:3.0.1-SNAPSHOT/maven-metadata.xml in https://oss.sonatype.org/content/repositories/snapshots/
Any ideas as to why?
Sorry for creating another issue but noticed the one I originally created was closed and couldn't re-open.
I can close this and add the comment to the original issue if that is better.
thanks.

See https://github.com/rest-assured/rest-assured/wiki/ReleaseNotes30#highlights

is this snapshot still available?


Running in local and please update README.md

Hi Cristian, thanks for your awesome hnpwa-vanilla repo. I just want to learn the code and how it works, but when I do npm run dev as per documentation it doesn't work. I check in package.json and it doesn't contain "scripts": { "dev": "bla bla bla" }. I go to your commit history and it shows that you replace several dependecies with microbundle and you remove the scripts { "dev": "bla bla bla" }. I go to microbundle repository and do as per documentation:

npm i -D microbundle
In package.json I add dev env in scripts: "scripts": { "build": "microbundle",  "dev": "microbundle watch" }
npm run dev but it just bundling and didn't show the URL that I must hit in browser.

Could you please give the solution about this with update README.md. Thanks a lot.

Hey Satya!
First of all, thank you for submitting the issue! Really appreciate it.
Second, indeed, when switching to microbundle I skipped the dev script. Usually I just run a python -m SimpleHTTPServer 8080 in my dist folder 😄, not really dev oriented.
I'll add it back asap.
Thanks again!


fix golint issues

As of now, issues in ./pkg/...:
ENG000656:builder aaronschlesinger$ golint ./pkg/...
pkg/conf/config.go:7:1: exported function EnvConfig should have comment or be unexported
pkg/gitreceive/build.go:29:6: don't use leading k in Go names; func kGetCmd should be getCmd
pkg/gitreceive/build.go:174:2: don't use leading k in Go names; var kCreateCmd should be createCmd
pkg/gitreceive/build.go:207:2: don't use leading k in Go names; var kLogsCmd should be logsCmd
pkg/gitreceive/config.go:7:6: exported type Config should have comment or be unexported
pkg/gitreceive/config.go:24:1: exported method Config.App should have comment or be unexported
pkg/gitreceive/run.go:26:1: exported function Run should have comment or be unexported
pkg/gitreceive/git/sha.go:15:6: exported type ErrInvalidGitSha should have comment or be unexported
pkg/gitreceive/git/sha.go:23:6: exported type SHA should have comment or be unexported
pkg/gitreceive/git/sha.go:28:1: exported function NewSha should have comment or be unexported
pkg/gitreceive/git/sha.go:35:1: exported method SHA.Full should have comment or be unexported
pkg/gitreceive/git/sha.go:36:1: exported method SHA.Short should have comment or be unexported
pkg/gitreceive/storage/bucket.go:10:2: exported var ACLPublicRead should have comment or be unexported
pkg/gitreceive/storage/bucket.go:13:1: exported function BucketExists should have comment or be unexported
pkg/gitreceive/storage/bucket.go:29:1: exported function CreateBucket should have comment or be unexported
pkg/gitreceive/storage/client.go:9:1: exported function GetClient should have comment or be unexported
pkg/gitreceive/storage/object.go:10:1: exported function ObjectExists should have comment or be unexported
pkg/gitreceive/storage/object.go:20:1: exported function UploadObject should have comment or be unexported
pkg/gitreceive/storage/slug_builder_info.go:31:1: exported method SlugBuilderInfo.PushKey should have comment or be unexported
pkg/gitreceive/storage/slug_builder_info.go:32:1: exported method SlugBuilderInfo.PushURL should have comment or be unexported
pkg/gitreceive/storage/slug_builder_info.go:33:1: exported method SlugBuilderInfo.TarKey should have comment or be unexported
pkg/gitreceive/storage/slug_builder_info.go:34:1: exported method SlugBuilderInfo.TarURL should have comment or be unexported
pkg/sshd/config.go:3:6: exported type Config should have comment or be unexported

duplicate of #230, closing


⚠ TorrentLeech has degraded performance

In 53187d5, TorrentLeech ($TL) experienced degraded performance:

HTTP code: 200
Response time: 3089 ms

Resolved: TorrentLeech performance has improved in 4be21a2 after 8 minutes.


Write tests for LiveFileConnector operations that are untested

wip

https://github.com/zio/zio-connect/pull/13


fix(typo): Fix typo in request.test.ts

Fixed what appears to be a typo in the test case.
The author should do the following, if applicable

[ ] Add tests
[ ] Run tests
[ ] bun run format:fix && bun run lint:fix to format the code
[ ] Add TSDoc/JSDoc to document the code

@yasuaki640 Thanks!


generic data processing capabilities I

Generalize and improve current data processing pipeline, with the goal to allow easy utilization of data as part of the projects, facilitate technical debugging, facilitate understanding of data science background and challenges and to separate those challenges from another.
In a minimalistic setting, this includes:

[x]    Catching data related errors as soon as possible in the MLOps pipeline

[ ]   Providing functions that connect the tasks with the interface to include/exclude data types from loading

[x]   Check on data loading success status

In addition, the following features would be nice to have: (now or later)
4) Ability to get data science style diagnosis of data on the interface (label distribution, before/after training evaluation)
5) capabilities to handle advanced bugs relating to data loading - handle corrupt/invalid data in an optimal way
6) minimize RAM/VRAM data and possibly provide overview on the UI
As a follow up, this would require current tasks/projects to be tested and checked again and verified, with possibly changes in the testing functions currently set up separately. Some tasks might be better connected to the UI and UI changes would improve the overall usability. (possibly in a separate issue)
If data loaders work similar to the python version, a lot of these tasks can be handled naturally, but some sub tasks would require follow ups.

Minimalistic version has been done with #100  - follow up on 2) with #101


Develop

Codecov Report

Merging #41 (4ea4c48) into main (bac3a20) will decrease coverage by 1.33%.
The diff coverage is 0.00%.

@@             Coverage Diff             @@
##               main     #41      +/-   ##
===========================================
- Coverage     11.16%   9.83%   -1.34%
  Complexity       14      14
===========================================
  Files            32      35       +3
  Lines           591     671      +80
  Branches         40      51      +11
===========================================
  Hits             66      66
- Misses          523     603      +80
  Partials          2       2

Impacted Files
Coverage Δ

.../primihub/controller/FusionResourceController.java
0.00% <0.00%> (ø)

...java/com/primihub/convert/DataResourceConvert.java
0.00% <0.00%> (ø)

.../com/primihub/entity/copy/dto/CopyResourceDto.java
0.00% <0.00%> (ø)

...ihub/entity/resource/enumeration/AuthTypeEnum.java
0.00% <0.00%> (ø)

...ihub/entity/resource/param/OrganResourceParam.java
0.00% <0.00%> (ø)

...ub/entity/resource/po/FusionOrganResourceAuth.java
0.00% <0.00%> (ø)

...om/primihub/entity/resource/po/FusionResource.java
0.00% <0.00%> (ø)

.../primihub/entity/resource/vo/FusionResourceVo.java
0.00% <0.00%> (ø)

...ain/java/com/primihub/service/ResourceService.java
0.00% <0.00%> (ø)

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


TypeScript version: openai-realtime-api

@khorwood-openai mentioned in another issue possibly replacing the current JS package with a TS version. I think most of the community would prefer that, since it's the only way to guarantee a solid DX and internal consistency, so I went ahead and took a stab at it.
See https://github.com/transitive-bullshit/openai-realtime-api

This is a strongly-typed fork written in TypeScript.
All classes, events, and methods are the same as in the JS version, so it's meant as a drop-in replacement, just with much stronger typing guarantees.
My main contribution is that all events and handlers are typed via events.ts and RealtimeEventHandler.ts.
The event types explicitly separate between server events, client events, and the 5 unofficial custom utility events.
It also includes fixes for #3, #11, #12, #14, #17, #29, #34, #35, #37, #43, #44, and likely others.
When porting to TS, there were lots of places where the strong typing resulted in small bug fixes that are not necessarily captured by current issues.
There are a few places where I updated the code to use more modern TS conventions (e.g., one example is using structuredClone(data) instead of JSON.parse(JSON.stringify(data)))
It includes several Node.js demos to make it easier to test the realtime API.
It includes an imported version of OpenAI's Realtime Console, modified to replace @openai/realtime-api-beta with openai-realtime-api. It's a 99% drop-in replacement; I just had to tidy up some types since openai-realtime-api is a bit more strict.
When I started out, I wasn't sure how 1:1 the TS port would be, so I created a new repo versus forking, but it shouldn't be too hard to compare between the two.

Very open to feedback && would love to merge any part of my TS port back upstream. Ideally once the official version of updated to use TS and stronger typing, I can deprecate my package.
cc @Stevenic and @ZJONSSON who both seem active on the TS side of things in addition to the rest of the OpenAI's team.

thanks for contributing this... will definitely take a look

Hi, @transitive-bullshit
I used your library and found a little problem:
The waitForNext method doesn't work, no matter what the event name is
const client = new RealtimeClient({
  url: "wss://my-relay-server-domain.com",
  sessionConfig: {
    turn_detection: {
      type: "server_vad",
    },
  },
});

client.waitForNext("session.update").then(ev => {
   // This line never works. I've checked by setting a breakpoint,
   // and when dispatch method call, there's no event name registered in your eventHandlers.
   console.log("session.update", ev);
});

client.connect()


further detailed messaging

we'd like some indication if we changed a scenario that it needs to be recomputed - not just if the selected data changed

the above comment has been resolved, but there are a number of todo statements on messaging in the impact area scenario class which need to be resolved before release

make sure that stage-damage messaging is getting to the user too

in the scenario validation, the biggest lift is going to be the curve overlap stuff. When found to not overlap, we need some way to transmit back the strings of function types, some kind of out argument maybe...

we can report an error message, but I wonder if we should use property rule for curve overlap, too

in impact area scenario simulation, also need to address levee is valid, and convergence criteria,

stage-damage errors are being written to the log file, but the user is not being notified that there are fatal issues and that they should check the log file. @Brennan1994 do you have thoughts on how we could let the user know?


test restarting

fatal error -> close -> start again
is this work?

have to wait until joinhandles are consumed.

have to wait until bound socket is dropped.


Add option to specify Subject

Could not find any related issue/discussion. It would be nice to set a ce-subject in build/send commands. If you think that's useful I can create a PR.

Makes sense, although Subject is considered optional. I'm thinking that maybe a general way of setting optional Cloud Event fields be better?!? Something similar to --field arg, like:
kn event build \
  --ce-field subject=Acme \
  --field<EMAIL_ADDRESS>
WDYT?

Makes sense, although Subject is considered optional. I'm thinking that maybe a general way of setting optional Cloud Event fields be better?!? Something similar to --field arg, like:

I think that makes a nice API and could later be combined with a --ce-version flag to indicate and validate against a specific CE version (breaking/non-breaking).
So do you think of migrating the existing CE metadata fields as well, i.e. not only optional fields in --ce-field for consistency?

I feel like the non-optional fields should stay as they are, as they are often used. Exposing them would be easier to use and easier for newcomers to get familiar with CE basics - they can just invoke kn event build --help to get help on common options.

I understand your rational but that would ultimately lead to an inconsistent API, especially for newcomers I think.
So I'm in favor of harmonizing them with consistent prefixes, provide defaults (e.g. for required fields), descriptions and examples in the help section.
E.g. one might want to add additional context attributes later, which could be passed with --ce-attribute so everything is consistent for envelop fields.

All those required fields have some defaults already. Calling:
$ docker run --rm -p 8080:8080 quay.io/openshift-knative/knative-eventing-sources-event-display &
$ kn event send --to-url http://localhost:8080
Jun 30 13:56:36.582   INFO Event (ID: c7665942-d711-4036-849e-e87956ab34d4) have been sent.
☁  cloudevents.Event
Validation: valid
Context Attributes,
  specversion: 1.0
  type: dev.knative.cli.plugin.event.generic
  source: kn-event/v0.3.0-8-g7ac0651
  id: c7665942-d711-4036-849e-e87956ab34d4
  time: 2021-06-30T11:56:36.580565532Z
  datacontenttype: application/json
Data,
  {}

So, the type, source, id and time are all set, by default.

Yes, I know they exist :)
But consider the changes for optional envelop fields, we would end up with different fields for:

required fields (e.g. id)
optional fields (e.g. --ce-subject)
payload fields (--field)

So my thought was keeping --field but harmonizing required/optional envelop fields with --ce- prefix for consistency.

Closing this as there is no consensus.

Closing this as there is no consensus.

I think it's worth having this ticket open for a while longer, as this is a real issue. We just need to settle on an API, and I think we could get to it shortly.
/cc @rhuss

tbh,  for known fields i'm woudl support typed fields over key=value options for these reasons:

Better help messages that show the possible options
Bash/Zsh completion easily possible
Better validation on the option parsing level
Easier to memorize
The usual way how to work on a UI

However, I probably would even omit the ce- prefix as it sounds redundant.

/remove-lifecycle stale

/remove-lifecycle stale

/reopen
/remove-lifecycle stale
/triage accepted


An error occurred running this command to configure the environment(python setup.py develop)

(CYhssda) lab@lab-Precision-5820-Tower:~/hdd/cy/cy/HSSDA-main$ python setup.py develop
/home/lab/anaconda3/envs/CYhssda/lib/python3.7/site-packages/setuptools/dist.py:529: UserWarning: Normalizing '0.5.2+0000000' to '0.5.2+0'
warnings.warn(tmpl.format(**locals()))
running develop
/home/lab/anaconda3/envs/CYhssda/lib/python3.7/site-packages/setuptools/command/easy_install.py:147: EasyInstallDeprecationWarning: easy_install command is deprecated. Use build and pip and other standards-based tools.
EasyInstallDeprecationWarning,
/home/lab/anaconda3/envs/CYhssda/lib/python3.7/site-packages/setuptools/command/install.py:37: SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and pip and other standards-based tools.
setuptools.SetuptoolsDeprecationWarning,
running egg_info
writing pcdet.egg-info/PKG-INFO
writing dependency_links to pcdet.egg-info/dependency_links.txt
writing requirements to pcdet.egg-info/requires.txt
writing top-level names to pcdet.egg-info/top_level.txt
reading manifest file 'pcdet.egg-info/SOURCES.txt'
adding license file 'LICENSE'
writing manifest file 'pcdet.egg-info/SOURCES.txt'
running build_ext
error: [Errno 2] No such file or directory: '/usr/local/cuda-12.2/bin/nvcc': '/usr/local/cuda-12.2/bin/nvcc'

But the cuda I installed is 11.1 version, including the setting of environment variables is also 11.1 version, I do not know why it can not find cuda12.2 error

can you help me,thank you very much,you will get many nice papers

I've fixed the problem, it seems to be a cuda problem, cuda11.8 is successful, re-run python setup.py develop


logfile growing without bound if we keep writing empty WriteBatch (1.20)

Hi all,
I am using leveldb 1.20.0, and I found that if we keep writing empty WriteBatch. the logfile size will increase without bound.
#include <iostream>
#include <sstream>
#include <leveldb/db.h>
#include <leveldb/env.h>
#include <leveldb/write_batch.h>

using std::cout;
using std::endl;
static void print_usage(const char *pname) {
	cout << "Usage: " << pname << " <dbpath> <empty_put_cnt> " << endl;
}

int main(int argc, const char **argv) {
	if (argc != 3) {
 		print_usage(argv[0]);
		return -1;
	}

	const std::string &dbpath {argv[1]};
	std::istringstream iss {argv[2]};
	uint64_t cnt = 0;
	if (!(iss >> cnt)) {
		print_usage(argv[0]);
		return -1;
	}

	leveldb::Options options;
	options.create_if_missing = true;
	options.write_buffer_size = 65536; // 64KB
	leveldb::DB *db_handle {nullptr};
        leveldb::Status status = leveldb::DB::Open(options, dbpath, &db_handle);

	if (!status.ok()) {
		cout << "Open db " << dbpath << " failed : " << status.ToString() << endl;
		return -1;
	}

	leveldb::WriteOptions write_options;

	cout << "Start to put " << cnt << " Empty KV" << endl;
	for (size_t i = 0; i < cnt; i++) {
		leveldb::WriteBatch wb;
		leveldb::Status w_status = db_handle->Write(write_options, &wb);
		if (!w_status.ok()) {
			cout << "Write db failed : " << w_status.ToString() << endl;
			return -1;
		}
	}
	return 0;
}

[root@7d2b7faa12eb ~]# ./test_empty_wb_write ./empty_wb_1000 1000
Start to put 1000 Empty KV
[root@7d2b7faa12eb ~]# ./test_empty_wb_write ./empty_wb_1000000 1000000
Start to put 1000000 Empty KV
[root@7d2b7faa12eb ~]# ./test_empty_wb_write ./empty_wb_1000000000<PHONE_NUMBER>
Start to put<PHONE_NUMBER> Empty KV
[root@7d2b7faa12eb ~]# ls -alh empty_wb_1000
total 40K
drwxr-xr-x 2 root root 4.0K Jun  3 05:34 .
dr-xr-x--- 6 root root 4.0K Jun  3 05:43 ..
-rw-r--r-- 1 root root  19K Jun  3 05:34 000003.log
-rw-r--r-- 1 root root   16 Jun  3 05:34 CURRENT
-rw-r--r-- 1 root root    0 Jun  3 05:34 LOCK
-rw-r--r-- 1 root root   57 Jun  3 05:34 LOG
-rw-r--r-- 1 root root   50 Jun  3 05:34 MANIFEST-000002
[root@7d2b7faa12eb ~]# ls -alh empty_wb_1000000
total 19M
drwxr-xr-x 2 root root 4.0K Jun  3 05:34 .
dr-xr-x--- 6 root root 4.0K Jun  3 05:43 ..
-rw-r--r-- 1 root root  19M Jun  3 05:34 000003.log
-rw-r--r-- 1 root root   16 Jun  3 05:34 CURRENT
-rw-r--r-- 1 root root    0 Jun  3 05:34 LOCK
-rw-r--r-- 1 root root   57 Jun  3 05:34 LOG
-rw-r--r-- 1 root root   50 Jun  3 05:34 MANIFEST-000002
[root@7d2b7faa12eb ~]# ls -alh empty_wb_100000000
total 1.8G
drwxr-xr-x 2 root root 4.0K Jun  3 05:37 .
dr-xr-x--- 6 root root 4.0K Jun  3 05:43 ..
-rw-r--r-- 1 root root 1.8G Jun  3 05:42 000003.log
-rw-r--r-- 1 root root   16 Jun  3 05:37 CURRENT
-rw-r--r-- 1 root root    0 Jun  3 05:37 LOCK
-rw-r--r-- 1 root root   57 Jun  3 05:37 LOG
-rw-r--r-- 1 root root   50 Jun  3 05:37 MANIFEST-000002

I think is caused by memtable size not triggering the minor compaction , but keep appending log to logfile.
Is this a known and expected behavior, or is it already fixed in the later leveldb version?

One way I've found to mitigate this issue was skipping the write of empty WriteBatches. Unfortunately WriteBatch doesn't expose an empty() method and I have to resort to checking ApproximateSize() <= 12 (12 is the private constant leveldb::kHeader).

@philix, thanks for the information.
I had a WriteBatch wrapper class to record the put count ourselves and check the count before write to avoid writing empty.


Does your project not support implementation?

I want to make a k-pop artist gif wallpaper app. Your gif wallpaper seems to be the best in terms of resizing and speed. I want to use your app as a library, but don't want to support it? I have implemented gifwallaperservice, but your project is much faster and provides smoother gifs so I really want to use your project.

Hey! That's a cool project you have!
Ah you have seen, Gif wallpaper is open source, under the Apache 2 license, so feel free to fork it and reuse code that you like.
And keep me posted, I'm curious about what you will create!

thank you! But I'm a beginner, so I don't think I can modify it and use it! It would be great if it was made into a library and used as a module, but I'm so sorry!

Ah I see. Well, then sorry, I can't help you with this, as it would take a lot of time.
I would recommend that you get in development if it's dear to you, or that you find a developer that is also fan of this k-pop artist to help you.
Good luck.


[CI] Nit fix for QAT

It seems that QAT will always init without the config file which causes error report in CI as #1315
Nit fix for code logic

btw, @marceloamaral , @rootfs why not we use golang once to init the driver?

it seems QAT error been removed from log https://github.com/sustainable-computing-io/kepler/actions/runs/8418037293/job/23047689366?pr=1316


Test Standalone Hardware Component Functionality

Test each hardware component as they come in before combining into the proof of concept.

Completed as individual functionality has been configured and the system is currently being integrated.


Display Layer View State: Improvements to status handling

Create status string as needed.
Include all statuses in the status string.
Reload rows only for layers whose status has changed.

@sbaskaran Could you please review this at your earliest convenience?


Document "data snapshot" aspect/intent of AbstractDbData and subclasses more explicitly

Dear AssertJ-DB team, Dear Joel,
I found one of my friends wrapping Table to allow for a "data reload feature". As I understand the JavaDoc of that class, the intended purpose of this class and the sibling AbstractDbData subclasses is to hold a snapshot of DB data and provide a fluent assertion API for this data snapshot.
The web site http://joel-costigliola.github.io/assertj/assertj-db-concepts.html states for e. g. Table and Request, that these objects represent a "Table in" or a "Request on" the database.
This probably misled my friend (who has a decent background in RDBMS) into thinking that a Table object could / should also be used in more complex query/update scenarios, whereas its original purpose is "only" to contain the data snapshot used for upcoming fluent assertions.
Would it be possible to make this intention of holding a data snapshot from different sources (Table, Request) more explicit in the "Concepts" / "Elements of the Database" page, maybe a "Caution" paragraph elaborating a bit on this? In particular, I consider a hint like "If you need to re-load data after DB update operations, please create a new Table instance" very useful.
Looking forward to your feedback. Thanks in advance & keep up the good work. Very much appreciated.

@ansgarkonermann I'm not really involved in that module, @regis1512 is the man!


Trigger wallet sync after claiming youtube channel

A new certificate is created when a youtube channel is imported so we need to sync the wallet.
A user ran into an issue recently where they imported their channel and then closed the web and tried to access it on mobile - the key was not synced until they went back to the web version.

Another user ran into this recently.


Drawing a rectangle with a mismatched sign for width and height does not work

if you write
DrawRectangle(100,100,-100,-100,BLACK);
ray lib will draw a rectangle that looks the same as
DrawRectangle(0,0,100,100,BLACK);
however if you write
DrawRectangle(100,100,-100,100,BLACK);
or
DrawRectangle(100,100,100,-100,BLACK);
no rectangle will be rendered.

Yeah, that's the expected behaviour. You're providing a negative width and height for the size of the rectangle.
Actually, first form shouldn't work...

Is there a reason for that to be the expected behavior? It would make some cases a lot simpler if the width and/or height could be negative.
For example when implementing a drag selection box that updates when you move the mouse, you would only need to set the X and Y of the rectangle when pressing the mouse button and then updating the width and height with the new mouse positions when it moves.
The code becomes much more complex when negative width/height are not allowed as you need to also change the X and Y when the end points move to the left/up of the starting XY.

@jkaup Personally I find more logical to not support negative width and height for a rectangle drawing.

Fair enough, it makes sense from the mathematical perspective. Thanks for your response.


Create Image

This project incorporates Modal Functionality

like this

Toastify Functionality

Window pop up before taking delete action

Delete Opreation is Done.


rendering bug

A simple example with ionic vanilla js.
First rendering is OK, after all the page vanished...

Document

<script>
    let app = new Reef('#app', {
        template: function(props) {
            return `
            <div class="ion-page" id="main">
            <ion-header>
            <ion-toolbar>
                <ion-buttons slot="start">
                    <ion-menu-button></ion-menu-button>
                </ion-buttons>
                <ion-title>Rivages 2.1</ion-title>
            </ion-toolbar>
            </ion-header>
            <ion-content> <input /> ${props.clock} </ion-content>
            </div>
            `;
        },
        data: {
            clock: new Date(),
        },
    });
    app.render();
    setInterval(function() {
        app.data.clock = new Date();
    }, 1000);
</script>

Can you please provide a reduced test case in the form of a codepen demo?

Thx for reply, here it is :
https://codepen.io/szucatti/pen/JjWOvdy

The reason is the original template is modified afterwards by web components (added class...) so when it is rendered again, it fails because reef compare to the original template and not the updated DOM. A workaround would be to listen to dom changes via mutation observer but how can I bind my original template to events ? Maybe I wrong with this approach...

I'd recommend decoupling the Ionic component and the Reef Component from each other. The Reef component should be its own standalone thing.


Add a package.json

To install dependencies and to ensure that everyone as the good version (packages, engines).

Hey @masterT, this is probably a good idea, and I’d welcome a pull request. However, since it’s not required for Meteor apps, and I have a major re-factor of ReaDB in the incubation stage, it’s not a top priority at the moment…


Exchange fee education view

Description
Added fee information in exchange and created Exchange fee education view.
Note: this PR needs de work related to retrieve the fee exchange.
Tested
Tested on Android device changing the language to ensure that all the texts are ok.
Related issues

Fixes #955

Backwards compatibility
Totally compatible with previous versions.

Mostly looks good! In addition to the comments please:

Create a new issue for retrieving the tobin tax
Add screenshots to the PR (we typically do this for UI changes)
Add a snapshot test for the new FeeExchangeEducation screen

Can you provide me more information about snapshot tests?


Move job handler's pre-checks in a new class

Job handlers should be retriable and may have a CeleryTask reference.
If a job handler is instantiated just for calling the pre-check method
then it can not be given a CeleryTask reference.
The pre_check method is now a classmethod for any job handler.
The job handler's pre_check method will invoke the pre_check method of
a list of new checker classes.
A checker class needs all the parameters needed by a job handler class
but it does not need the CeleryTask reference.
All the common code between checkers and handlers has been moved
in mixin classes.
Fixes #1581

We will try pair review on this PR with Maja


Yoink search bar from Takoyomi

Describe your suggested feature
TF's Android studio is broken, so he can't PR.
Search bar doesn't autohide, need cleanup
A gift for Sy stable users who waited 8 months for updates!
https://github.com/CrepeTF/Takoyomi/commits/search-bar
Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open issue.
[X] I have written a short but informative title.
[X] If this is an issue with an extension, I should be opening an issue in the extensions repository.
[X] I have updated the app to version 1.8.0.
[X] I will fill out all of the requested information in this form.

https://github.com/CrepeTF/Takoyomi/compare/master...search-bar


Updating azure CNI overlay existing cluster command is wrong in the documentation

Updating existing cluster command is wrongly mentioned for resource group argument should be --resource-group not --group

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

ID: 64f0ba71-573f-b860-1c2c-802a62cae120
Version Independent ID: 28990db8-fce7-c356-da6f-c052a9c201ee
Content: Configure Azure CNI Overlay networking in Azure Kubernetes Service (AKS) - Azure Kubernetes Service
Content Source: articles/aks/azure-cni-overlay.md
Service: azure-kubernetes-service
Sub-service: aks-networking
GitHub Login: @asudbring
Microsoft Alias: allensu

@saikumar0412
Thanks for your feedback! We will investigate and update as appropriate.

@saikumar0412
Thanks for reporting this! We have created a PR for this issue and the changes should go live soon.


ls: illegal option -- -

I have issue using ls command mostly in tmux but It happen sometimes in regular terminal session.
ls: illegal option -- -
usage: ls [-ABCFGHLOPRSTUWabcdefghiklmnopqrstuwx1] [file ...]

❯❯❯ zsh --version
zsh --version
zsh 5.1 (x86_64-apple-darwin14.5.0)

❯❯❯ which ls                                                                                ⏎
which ls
ls: aliased to ls --group-directories-first --color=auto

I'm using OSX 10.10.5 and iTterm2 Build 2.9.20150905-nightly but I do not thing that issue is related to terminal emulator.
Thanks for any help.

The problem is in condition
if is-callable 'dircolors'; then

modules/utilitity/init.zsh
function is-callable {
  (( $+commands[$1] )) || (( $+functions[$1] )) || (( $+aliases[$1] ))
}

modules/helper/init.zsh
In my case this should return false but return true instead. I can fix it with redefinig ls alias in my .zshrc file for now.

I also have this problem, but it started when I swapped the default ls in OSX for the GNU version using brew. Looks like when the shell is initing it does not have access to the correct ls, rendering the error at first, but the command works as normal.

@filipekiss this doesn't work for me:(

@turboMaCk I'm guessing you installed coreutils package via brew? If that's the case, remove the coreutils package and install it again using the following option:
brew install coreutils - - default-names

Then load the gnu-utility package on your prezto and see if that works. :)

@filipekiss Yeah! It works now. Thanks a lot man.

I ran into this again on my new machine. brew install coreutils - - default-names does not work for me now and brew install coreutils --with-default-names do not fix this issue. Any idea?

Just checked brew info and found this:

==> Caveats
All commands have been installed with the prefix 'g'.
If you really need to use these commands with their normal names, you
can add a gnubin directory to your PATH from your bashrc like:
PATH="/usr/local/opt/coreutils/libexec/gnubin:$PATH"
Additionally, you can access their man pages with normal names if you add
the gnuman directory to your MANPATH from your bashrc as well:
MANPATH="/usr/local/opt/coreutils/libexec/gnuman:$MANPATH"

This should work for ZSH/prezto as well. Can you try this and let me know how it goes? :)

Sound reasonable. I had not much time look at this right now (working hard to finish sprint). But I definitely look at this later and post solution in here for a record. THX for your advice. I see the same guid when running brew info coreutils so I believe that this should fix this issue.

No problem! Let me know how this goes. :)
On Fri, Jan 15, 2016 at 2:17 PM Marek Fajkus<EMAIL_ADDRESS>wrote:

Sound reasonable. I had not much time look at this right now (working hard
to finish sprint). But I definitely look at this later and post solution in
here for a record. THX for your advice. I see the same guid when running brew
info coreutils so I believe that this should fix this issue.
—
Reply to this email directly or view it on GitHub
https://github.com/sorin-ionescu/prezto/issues/966#issuecomment-172004239
.

--
Filipe Kiss
————————
+55 11 972-417-669
<EMAIL_ADDRESS>www.filipekiss.com.br

RESOLVED
I have to replace old:
export PATH="$PATH:$(brew --prefix coreutils)/libexec/gnubin"

with new:
export PATH="/usr/local/opt/coreutils/libexec/gnubin:$PATH"

Just bumped into this one in the future, installing coreutils and adding it to the PATH resolved the issue.

For reference:
brew install coreutils
export PATH="/usr/local/opt/coreutils/libexec/gnubin:$PATH"

For reference:
brew install coreutils
export PATH="/usr/local/opt/coreutils/libexec/gnubin:$PATH"

Thanks. That worked!

For reference:
brew install coreutils
export PATH="/usr/local/opt/coreutils/libexec/gnubin:$PATH"

Thanks. That worked!

Thanks. That worked! (I had the same issue after reinstalling brew and I forgot I already have found the solution - don't judge me!).

If you use MacPorts:
sudo port install coreutils
Add to .zshrc: export PATH="/opt/local/libexec/gnubin/:$PATH"


Write question service API tests

Summary:

replaced node alpine with buster image

or else mongodb-memory-server will not work, which is crucial for testing the functionality of APIs

set up and configure jest test suite
wrote test cases covering most API usage scenarios

Next steps:
Tests run well on local machine but can't seem to get it to work properly on Docker (gives some Segfault Error on occasion, or doesn't even run at all). Need help from docker and nodejs expert.
Caveats:
Tests do not cover ALL cases yet, but this should suffice for now.

Closes #18


[bazel] Turn off default debug prints during OTP splicing

This PR:

Refactors the bitstream_splice rule to use the args constructor
Switches the default debug value for bitstream_splice to false. This should remove about 90,000 extra lines of debug output from bitstream splicing when running the full suite of cw310 tests.

More specifically, this gets rid of all the output that looks like this:
Dump the BRAM Initialization Strings.
  ^^^ Bitlane with BRAM Location: RAMB18_X3Y119
  INIT_00:0000000000000000000000000000000000000000000000000000000000000000
  INIT_01:0000000000000000000000000000000000000000000000000000000000000000
  INIT_02:0000000000000000000000000000000000000000000000000000000000000000
  INIT_03:0000000000000000000000000000000000000000000000000000000000000000
  INIT_04:0000000000000000000000000000000000000000000000000000000000000000
  INIT_05:0000000000000000000000000000000000000000000000000000000000000000
...


Create SECURITY.md

Hello 👋
I run a security community that finds and fixes vulnerabilities in OSS. A researcher (@yuligesec) has found a potential issue, which I would be eager to share with you.
Could you add a SECURITY.md file with an e-mail address for me to send further details to? GitHub recommends a security policy to ensure issues are responsibly disclosed, and it would help direct researchers in the future.
Looking forward to hearing from you 👍
(cc @huntr-helper)

Sent a magic link to<EMAIL_ADDRESS>:) Let me know if that works

Hi @psmoros, I received your email and responded, thanks! I'll re-open this issue since we have not yet created the SECURITY.md file, and I think it would be a good idea for us to do so.
Note to team: We can base the file off of sklearn's: https://github.com/scikit-learn/scikit-learn/blob/main/SECURITY.md


customized exception body in openapi schema

Usual
{
  "detail": [
    {
      "loc": [
        "string"
      ],
      "msg": "string",
      "type": "string"
    }
  ]
}

customized exception_handler
@app.exception_handler(RequestValidationError)
async def validation_exception_handler(request: Request, exc: RequestValidationError):

    exc_str = f'{exc}'.replace('\n', ' ').replace('   ', ' ')
    content = {'code': 10001, 'data': None, 'message': 'some message ...'}
    return JSONResponse(content=content, status_code=422)

the aim is
{
 "code": 10001,
 "data": ...,
 "message": ""
}

how to show like this in openapi schema?

see the additional responses section of the documentation.

thanks, helpful

Thanks for the help here @ycd ! 👏  🙇
Thanks for reporting back and closing the issue @panla  👍

Sorry for the long delay! 🙈  I wanted to personally address each issue/PR and they piled up through time, but now I'm checking each one in order.


Illegal Access Error to access Bouncycastle Class

Description
Jwkms raise the below error when signClaims:
Caused by: java.lang.IllegalAccessError: failed to access class org.bouncycastle.asn1.DEROutputStream
from class org.bouncycastle.cert.CertUtils
(org.bouncycastle.asn1.DEROutputStream and org.bouncycastle.cert.CertUtils are in
unnamed module of loader org.springframework.boot.loader.LaunchedURLClassLoader @573f2bb1)

Can be related with bouncycastle libraries versions.

Aligned the eidas-psd2-sdk library version to fix the transitive bouncycastle dependency version to avoid the error defined in the issue.


Feature/ascii stick diagrams

@desmonddak First stab at an ascii diagram. Test builds the same thing as the m2_m3 test.

The ASCII language is spot on.   I think the only thing needed for generality is to capture a crossing versus a via.  '+' is a perfect via.  You could use '-' instead of '=' for a crossing.  All it tells you is the metal continues in both directions.     The next level of issues is going to be multiple parallel metals.  One way is to use different characters, but this gets really clumsy.  An interesting other way is to slice into pairs of layers with separate ASCII files, reusing the same characters.   In this case, you did M2/M3, and showed down connections to M1.  The same letters can be reused for M5/M4::  '=' is m4 and '|' is m5.  This gets hard because you need to work off a grid multiple.  But you just need an LCM to the grid below for each layer pair, making this tractable.

It seems that the hard issue if if you specify m3 (say with |) how do you know what is under it. I guess it can be the following:

nothing
m2 wire
m2 wire, v1
m2 wire, v2
m2 wire, v1, v2
If there are vias, we specify +, /, or * (both), and assume the m3 is there if it was directly below or if the character is '/' or '*' (meaning a v2).
If we specify | then the m2 wire is there depending on whether there is a = directly to the left.

I guess this works because we can't start or stop a wire without a via.
Let me know if this makes sense. File a new PR with a testcase if this is not a good idea.

I was thinking you could use '-' for an M2 under M3 as it is similar to '='.  The vias you propose would complete '+', '/'. '*'.  This way the language makes no assumptions about starting or stopping (or at least no logic needed in the spec).   I think the big thing is:  can you create an ascii language from multiple 2-layer specifications that compose using these characters.   So really = is the horizontal metal, | is the vertical.  Then '+' and '/' are via-up and via-down, etc.   I think it works, but only when pitches have reasonable multiples up/down the stack.

I think only in the case of a bidirectional metal would you absolutely require a 'metal under metal'' character.  At least I can think of a case where the ambiguity would not be locally resolvable.


Vulkan: MeshInstance3D nodes with Dynamic Bake mode are very expensive in VoxelGI, regardless of quality settings

Godot version
4.0.dev (5efe80f30)
System information
Fedora 34, GeForce GTX 1080 (NVIDIA 470.74)
Issue description
Even when using primitive BoxMeshes and very simple world geometry, VoxelGI updating takes a lot of time. It typically doubles the frametime required to render a scene, making it difficult to sustain a 60 FPS target on anything but the highest-end GPUs. Dynamic VoxelGI becomes relatively affordable at low VoxelGI quality + half-resolution GI, but this causes overall GI quality to take a noticeable hit.
I remember dynamic VoxelGI being less expensive a while ago (late 2019-early 2020), so a regression may have occurred. If this turns out not to be a regression, we should figure out a way to reduce the cost to make the feature more usable in real world scenarios (such as by revoxelizing less often at the cost of quality).
See the FPS counters in the top-left corner of each screenshot:
VoxelGI high quality

Dynamic and static
Dynamic only
Static only
No static or dynamic

VoxelGI low quality

Dynamic and static
Dynamic only
Static only
No static or dynamic

VoxelGI low quality + half-resolution GI

Dynamic and static
Dynamic only
Static only
No static or dynamic

Steps to reproduce

Add a VoxelGI node.
Add a MeshInstance3D with bake mode set to Baked. Assign an emissive material to it.
Add second MeshInstance3D with bake mode set to Dynamic. Assign an emissive material to it.
Bake the VoxelGI node.
Notice how performance plummets whenever the dynamic MeshInstance is visible, even when it doesn't move.

Minimal reproduction project
test_voxelgi_performance.zip
Press D to toggle dynamic mesh visibility.
Press S to toggle static mesh visibility.

Still reproducible as of 4.2.dev 16a93563bfd3b02ca0a8f6df2026f3a3217f5571 on Linux, even on a much faster GPU: https://github.com/godotengine/godot/pull/80356#issuecomment-1667256042


Test DocumentCollection.php

Q
A

Bug fix?
N

New feature?
N

BC breaks?
N

Deprecations?
N

Fixed tickets
N

Test for DocumentCollection.php

Hello, your branch "test/Documentcollection" is not up to date with our "develop" branch. Can you merge the latest version of develop in your branch?

It also seems than one of our automated tests are not passing (phpstan or phpcs) could you verify and resolve that also?

Looking at the build error, you should upgrade phpstan to ^7:
"phpunit/phpunit": "^7.0",

Looking at the build error, you should upgrade phpstan to ^7:
"phpunit/phpunit": "^7.0",

You can do this in the composer.json file, and then run "composer update phpunit/phpunit" to test it locally

In fact this point was blocking because of a dependency issue. PHPunit needs to be at version 7 (I upgraded to 8.5) for this to work. I will close this PR in favor of #92
Both of your PR's have shown a bug in our code! Those are solved now! 👍


[Release] sdk/resourcemanager/msi/armmsi/0.7.0

https://github.com/Azure/sdk-release-request/issues/2948

SDK change looks as expected.  Please merge and release.


[Bug] Infinite loop in polling function of Forward

Here describes an scenario that hangs stream.forward(sink) in the polling function of Forward (code). The code below is simplified version of the polling function.  It goes back and forth between part A and B in the case that the stream always returns an item when being polled, and sink is always ready to receive an item. There is no chance to escape the loop.
loop {
    if buffered_item.is_some() {
        // part A
        ready!(si.as_mut().poll_ready(cx))?;  // return here if pending or error
        si.as_mut().start_send(buffered_item.take().unwrap())?;
    }

    match stream.as_mut().poll_next(cx) {
        Poll::Ready(Some(item)) => {
            // part B
            *buffered_item = Some(item);
        }
        /* return in other cases */
    }
}

A simple experiment can be done in the example below, in which the polling of future fut1 never ends. The future fut2 has no chance to be executed.
let fut1 = stream::repeat(()).map(Ok).forward(futures::sink::drain());
let fut2 = async {
    rt::sleep(Duration::from_secs(1)).await;
    dbg!();  // never print this.
};
futures::join!(fut1, fut2);

A simple fix is to remove the loop and call cx.waker().wake_by_ref() to request polling next time. It slightly adds up runtime cost but effectively eliminates the hanging issue.
if buffered_item.is_some() {
    // part A
    ready!(si.as_mut().poll_ready(cx))?;  // return here if pending or error
    si.as_mut().start_send(buffered_item.take().unwrap())?;
}

match stream.as_mut().poll_next(cx) {
    Poll::Ready(Some(item)) => {
        // part B
        *buffered_item = Some(item);

        // Fix: wake itself and return
        cx.waker().wake_by_ref();
        return Pending;
     }
    /* return in other cases */
}

Thanks for the report. The way good than yield per poll to fix this is to limit iterations. See https://github.com/tokio-rs/tokio/pull/3625 for more.


SPIKE: Migrate off of create-react-app to Vite

Background
Create react app bloats the application. Vite would potentially give us a faster build time and quicker recompiles within the app itself. CRA is potentially leading to a lot of slow CI/CD runs; Vite would speed this up significantly.
Action requested
Attempt to move to Vite. Timebox the effort to no more than a week.

Will present findings during eng sync on Thursday Nov 17th

Findings presented at engineering sync on 11/17; going to continue with React migration and sass bundler improvements.


Added nodeComponent property to FlowyNode.

Enables Flowy to use a standard component for block set as prop, without including it in dataset. If block component is set in data, this will override parameter.

@remcoplasmeyer is this repo disbanded?


[reactive-element] @query decorator not working during testing with Web Test Runner

Which package(s) are affected?
Lit Core (lit / lit-html / lit-element / reactive-element)
Description
I am building a simple Pill component that needs to add or remove a -hover class when hovered.
In order to select the correct element I use the query decorator.
Everything seems to work fine in a regular browser environment, but the result of the query-annotated property is always null when it's being tested with Web Test runner (suggested test framework from the docs), using Mocha/Chai.
Using a getter inside the Pill (that extends from LitElement) solves this problem, but I don't understand why the decorator doesn't work during testing.
After some research both the getter and the query decorator should perform the same functionality.
Both are evaluated at the moment they are accessed.
So I don't understand why the decorator doesn't work, but the explicit getter in TypeScript does.
Steps I have taken

I have made sure the decorator is imported properly
I have made sure the element exists and is being queried with the correct selectors
The renderRoot / shadowRoot is correctly initialized before the query is performed
I have created my own custom decorator that performs the same functionality, but it also doesn't work

Web Test Runner is configured with the esBuildPlugin, so that  it understands TypeScript
Reproduction
Using a query-decorated property during testing with Web Test Runner.
This will always result in null.
As a consequence the test fails.
Workaround
Using a getter inside the Pill (that extends from LitElement) solves this problem, but I don't understand why the decorator doesn't work during testing.
Is this a regression?
No or unsure. This never worked, or I haven't tried before.
Affected versions
2.7.2
Browser/OS/Node environment
Browser: Chrome (Web Test Runner)
OS: Windows 10
Node version: 16.13
NPM version: 8.1.2

Can you make a reproduction repository? We can't really tell what's wrong without that. Our tests of the @query decorator use Web Test Runner, so something else must be going on.

I think I ran into the same issue after updating my dependencies with my decorators ceasing to function when run from web-test-runner as well as web-dev-server. I located the cause to be updating from<EMAIL_ADDRESS>to<EMAIL_ADDRESS>so I'm sticking to v0.3.3 for now. Hope this might be helpful to you as well.
I think this might be related to https://github.com/modernweb-dev/web/issues/1921.

oh... are you building TypeScript with Web Test Runner?

We were in the process of setting up a test repository to show the problem.
However thanks to @difosfor, we got a working solution, by specifying the tsconfig in the esbuildPlugin.


Upgrade to Vue3

What I will do ?
Upgrade Logoly from Vue2 to Vue3.
Why I post this issue?
I want to know is here any one work on Vue2, may be must postpone your work.
Time
will start at 2022-03-15 UTC+8:00 20:00

@yes1am @kentwood

hi @bestony , can i add some meta data about your site? some things like og tags, metatags?
if u can create a issue with hacktoberfest label for me... thanks a lot!

Done with https://github.com/bestony/logoly/pull/400


internal error when we don't know how to handle input

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


Fix errors created by new math bilfac redesign

This fixes the errors created by removing bilinear group factory in the math library. The uses of the factory have been replaced by direct instantiations of bilinear groups of the desired type.

The pull request travis build fails, but that is meaningless I believe.

The pull request travis build fails, but that is meaningless I believe.


Allow to run programs through a shell receiving huge argument lists

Invoke commands through a shell in the pattern of
/bin/sh -c 'command "${@}"' -- arg1 arg2 ...
Add an option to system to receive arguments for "${@}"
Use the new system overload in the compiler linker invocation

Please say quickly whether or not this is acceptable, so we can get to a solution asap.

Note that we can later expand this to allowing $1, $2 etc, so this basically gives us "bind params" for system, so something like system("echo $1 | tee $2 | foo", {user_input, "path/with space"})

Also note that the issue mentioned in https://github.com/manastech/crystal/issues/300#issuecomment-135418839 is not present here.

Rebased.


phantom.create callback doesn't work

I have two server host
centos5.9 node10.20 phantomjs 1.92 python Python 2.7.3
var phantom = require("phantom");
phantom.create( function (ph) {
            console.log("cb...........");

});
one can work ,the other cann't work. and throw nothing.

Cleaning out old bugs. If it is still valid, let's reopen.


add new apple squeeze method

closes #1

Other than the little nit it looks good to me 🚀

thanks @NomiAdam
fixed the typo.
but you might want to change the v1 callback method and align it maybe with the newer versions. i could not test it since my ipad was >= 17.5 already.

@NomiAdam ping

@AlexanderThiele Thank you for your work, appreciate it. I have been a bit busy so it didn't get to it yet, put it onto my todo list for this week. I will test everything out on my side to see if there is anything wrong and needs updating or not. I will update those issues accordingly 🤞

Looks good 🚀


Build only PRs with Appveyor

This PR:

Instructs Appveyor to build PRs only.
Fixes Security issue related to Jackson.
Updates JS tests to newer generated code API (which fixes singular vs. plural in repeated fields).
Bumps dependencies to newer stable versions.
Forces dependencies to make them predictable.
Version of Servlet API downgrades from 4.0.0 to 3.1.0 because v4 is not supported by App Engine.

The JS lib version advances to 0.18.0.

@serhii-lekariev, FYI.


Feat Request: Custmizable delay before activating blame

Could we have an option to set a delay before the blame is activated?
Use case: Having enabled inline blame, when sifting through code, the inline blame often lags behind the cursor, This can be jarring as the inline blame is not a subtle color. I can post a video later.
Having a delay can sorta mitigate this, like the cursor has to stay on a line for several 100 ms before the blame would get activated.

Hey Ajith! Thank you for the feature request.
I think I understand the issue. I currently don't have a lot of time to spend on the extension but I do accept pull requests if you (or anybody else) want to make an attempt at building it.

Hey Albin, I understand.
TS/JS is not my speciality, but I'll try to give it a go :D

@Sertion i got some time to look into the code and test some things. Initial thought was just to wait for few ms and display the line blame. This sorta works partially, but when zipping around, you see a trail of the past blames and this makes it even worse than before 🙃
After thinking it through, a better solution would be have an event handler which captures cursor events (up/down cursor movements) and events which remain unchanged for x ms would triggers the line blame.
Now that i think about it, this is much more complex than adding a delay and may not be worth adding for a minor annoyance.
Do you have something else in mind or maybe give me some pointers?

@aaravind100 Thanks a lot for having a look.
The entire extension is sort of build around the idea that everything happens "eventually". Perhaps something can be done similar to how the statusbar element is updated and super short Promise.race?

@aaravind100 Thanks a lot for having a look.
The entire extension is sort of build around the idea that everything happens "eventually". Perhaps something can be done similar to how the statusbar element is updated and super short Promise.race?

@Sertion adding a delay in this method kinda a solves the problem.
Before:
Before
After adding 200ms delay:
After
Would you like me to create a pr for this?

Impressive! Please do!

@Sertion i've created this (#141) pr

Merged.

A new version has been released. It sometimes can take a few hours before it is available for everyone.
Thank you for your time and effort!

Thanks a lot!!


Pages tree is empty cms >= 3.2.2

The page /admin/cms/page/ which show the page tree is empty when django-cms version is > 3.2.1.
It works with 3.2.1.
With django-debug-toolbar enabled, the debug information is where the page tree sould be.

this looks like an error with static files. Be sure to run collectstatic again and empty any server- and client- side cache

I did, but it does not work better.

@alexandrenorman eventually some caching issues? Try a force refresh?

Caching issue was my first idea.
To be sure I already tried with a browser I don't use without more success.
Digging in generated html, I have:

            <div class="cms-pagetree js-cms-pagetree" data-json='{
                "urls" : {
                    "tree" : "/fr/admin/cms/page/get-tree/",
                    "move" : "./{id}/move-page/",
                    "copy" : "./{id}/copy-page/",
                    "copyPermission" : "./{id}/dialog/copy/",
                    "theme" : "/static/cms/css/"
                },
                "csrf" : "oz7YMLzpFiW5yiGpYOwOenxf0Lk48gD6",
                "static" : "/static/",
                "permission" : "true",
                "debug" : true,
                "filtered" : false,
                "site" : 1,
                "lang" : {
                    "code" : "fr",
                    "success" : "Déplacement réussi",
                    "changes" : "Les changement dans l\u0027arbre peuvent nécessiter un rafraichissement.",
                    "error" : "Error : ",
                    "apphook" : "This page cannot be copied because an application is attached to it. See the Page\u0027s Advanced settings to manage apphooks.",
                    "publish" : "Êtes\u002Dvous sûr de vouloir § cette page ? ",
                    "reload" : "Reload",
                    "loading" : "Chargement…",
                    "newNode" : "New node",
                    "nodes" : "nodes"
                },
                "columns" : [{
                    "title" : " ",
                    "key" : "",
                    "width" : "100%"
                }, {
                    "title" : "coller ”,
                    “key” : “view”,
                    “cls” : “jstree-grid-cell-regular-options”
                }, {
                    “title” : “View”,
                    “key” : “preview”
                }, {
                    “title” : “FR”,
                    “key” : “fr”
                },  {
                    “title” : “Menu”,
                    “key” : “menu”
                }, {
                    “title” : “Actions”,
                    “key” : “options”
                }, {
                    “title” : “Info”,
                    “key” : “info”
                }]
            }’ data-settings-url=”/fr/admin/cms/usersettings/session_store/”>

the data-json tag seems unclosed with bad encoding... could it come from that ?

@vxsx you have any idea?

  first thing that comes to mind is some kind of typography middleware tbh

@alexandrenorman can you share your setup, I cannot reproduce this on clean install?
the json looks malformed, that's likely the reason pagetree won't initialize

Well seen. I forgot about it… but you pointed it: the problem comes from our custom typography middleware !
After disabling it, django-cms works as expected.
I need to find why it used to work and it doesn't anymore… but that's on our side.
Thanks for your help ! Problem solved.


closes #69 - allow missing template path

This allows the default views directory to be used by express internally

removed default template path
check if templatePath if defined before prepending

@gavboulton @easternbloc @JoeChapman @HughePaul would you mind having a look at this? It would be a major bump as any app currently using wizard without a templatePath will have it implicitly set to 'pages'

Can you add a test please.
This will be a breaking change.

@gavboulton test added

LGTM :+1:

LGTM

@gavboulton can you merge that now pwease and gis a version bump

<EMAIL_ADDRESS>published.


MSlogger file

Hi ,
in pods MSlogger file is conflicting with other pods . they are are also using same file name so I am getting error like files are duplicated .
can you please change the file and update the code .

Hi Arjunna,
I will update the logger file to a unique name.
John

Closing this issue as we are archiving this repository. Please see https://github.com/microsoftgraph/msgraph-training-ios-objectivec for an Objective-C sample.


feat: Support PEP561

🚨Please review the guidelines for contributing to this repository.
Description
Added PEP561 support.
Checklist

[ ] Created tests which fail without the change (if possible)
[x] All tests passing
[x] Added a changelog entry
[ ] Extended the README / documentation, if necessary

Hi @hebertjulio!
Thank you very much for your contribution! :) I am happy to merge this PR as is, but as #748 is marked with the "Hacktoberfest" label, I want to ask if you are participating and if so, then let you know that all PR should be created from Oct 1 to match the Hacktoberfest rules. Let me know if you want this PR to be counted towards the Hacktoberfest goal. Then you can create a new one tomorrow and make it count. If not, then I'll merge this PR today

Yes, I want this to be counted the Hacktoberfest goal. Sorry for my anxious PR, tomorrow I will create a new PR. Thx.

Yes, I want this to be counted the Hacktoberfest goal. Sorry for my anxious PR, tomorrow I will create a new PR. Thx.

No worries! Let me know if I can help :)
I will just add a note that you are working on this issue in #748