Bug: Wrong error message when running func commands if the function is not initialized

Issue Summary:
When executing the commands func deploy, func run, and func build without first initializing a function (missing func.yaml file due to not running func create or func init), the error handling leads to an unclear message. This occurs even if the commands are typed correctly.
Current Behavior:
Attempting to run any of the above commands without initializing a function results in a misleading error message related to registry validation:
func build -b=s2i -v
A registry for function images is required. For example, 'docker.io/tigerteam'.
X Sorry, your reply was invalid: invalid registry ["quay.io/user-abc"]: name required
? Registry for function images:

The error message should clearly indicate that the function has not been initialized and provide guidance on the necessary steps to proceed.
Proposed Solution:
Improve the error message to more accurately reflect the issue and guide the user. Suggested new error message:
Error: No function has been initialized in the current directory ({path}). Please initialize a function by running either:
- func init --language <your language>
- func create <function name> --language <language>

Thanks @Leo6Leo,
This does look like a logic problem.  There should be a different error there.
I've added this to the roadmap

I would like to work on this issue!

@EraKin575 hello, are you still working on this issue?

I want to work on this issue, if no one else is interested anymore

@tarunsunny3 great! have a go and if you have questions, feel free to ask

Hi @gauron99
This is my second OSS contrubution(1st one was just a README update)
I forked the repo and started working on it and was going over the cmd/ folder and mostly where the changes need to be made
But before doing anything else, I wanted to run 'make' and see it and other commands(make check, etc) run properly
But it is throwing errors as shown below

I tried to debug, and ran git tag to see that it's giving empty output for VTAG, even after pulling the tags from the original repo, still VTAG seems to be empty and in Makefile we have the code where if VTAG is empty it's defaulting to ETAG, but ETAG was nowhere defined

Can you please share any beginner resources or a community to join?
Thanks!

Can you please share any beginner resources or a community to join?

sure, here is a CNCF slack knative-functions community
https://cloud-native.slack.com/archives/C04LKEZUXEE
as of other resources: we have docs for now.
(We are actually working on function templates and "better docs" as of right now and they are not done yet - sorry for that)
There is also knative quickstart that will walk you through the creation of the function, its building/deployment and you can take a look at other parts of knative if thats something that interests you.
sidenote: Im sorry I have not seen your error before, so cant provide quick fix. I will take a look and let you know if I find something helpful.

I do not believe this has to do with VTAG, but rather the value of LDFLAGS appears to be incorrect.
Can you please post the output of make -version?

I joined the Slack community, and got help from there
@matejvasek helped me
It was because I had an older version of Go, I updated it to 1.22 and it worked fine
Thanks!

I've made changes only to build.go, so that we can discuss if this okay


NO-JIRA: Remove specific pull secret watch in HCCO

What this PR does / why we need it:

Removes specific watch for pull secret as general watch for secrets already covers this.

Which issue(s) this PR fixes (optional, use fixes #<issue_number>(, fixes #<issue_number>, ...) format, where issue_number might be a GitHub issue, or a Jira story:
Fixes #
Checklist

[ ] Subject and description added to both, commit and PR.
[ ] Relevant issues have been referenced.
[ ] This change includes docs.
[ ] This change includes unit tests.

/test e2e-kubevirt-aws-ovn

/test e2e-kubevirt-aws-ovn

/test e2e-kubevirt-aws-ovn

/test e2e-kubevirt-aws-ovn

/test e2e-kubevirt-aws-ovn

/test e2e-aws

/retest-required

/test e2e-kubevirt-aws-ovn

/test e2e-kubevirt-aws-ovn

/retest

/lgtm


Minimize re-render, Truncate long SR names, add Selected section

merging this i'll check what we can do in order to make it less laggy on the inputs :+1:


[csrng] Select Canright S-Box implementation for AES cipher core

While checking top_earlgrey for ways to save FPGA logic utilization, I noted that for CSRNG always uses the LUT-based S-Box inside the embedded AES cipher core. This is good for FPGAs but for ASICs, the unmasked Canright S-Box should be used.
Therefore, this PR changes the default selection for the S-Box implementation inside the embedded AES cipher core from the LUT-based implementation the unmasked Canright design. This should reduce the area footprint of CSRNG a little bit. The LUT-based implementation is explicitly selected when working with FPGA targets.

Thanks @mwbranstad for having a look and approving this PR. Once I get approval from a committer, I will merge this.

Thanks @imphil :+1:


FINERACT-1528: Replace copy and pasted Swagger UI with Springdoc

Description
Introduce Springdoc instead manual Swagger UI. Now the Swagger test UI can be turned off in production. Moved legacy doc into a separate folder; now that we have the new documentation online we could consider getting rid of it.

yeah... that was an accident...
On Thu, Apr 28, 2022 at 4:31 PM Arnold Gálovics @.***>
wrote:

@.**** commented on this pull request.
In fineract-client/build.gradle
https://github.com/apache/fineract/pull/2300#discussion_r860963122:

 ]

 dependsOn = [
     ':fineract-provider:resolve'
 ]

}
-licenseFormatMain.dependsOn buildJavaSdk
Wait a sec. Are you sure this is gonna be replaced by the change below?
When I was fixing the incremental build for Gradle, this combination
worker flawlessly. Have you tested whether it's broken?
—
Reply to this email directly, view it on GitHub
https://github.com/apache/fineract/pull/2300#pullrequestreview-956542926,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAC4ZL76CI2766KZTE673KTVHKONDANCNFSM5UPU3LIA
.
You are receiving this because you authored the thread.Message ID:
@.***>

@galovics ... really don't know why that specific test is breaking... didn't touch anything concerning it. Any ideas? Is this happening in develop too?

@galovics great... it worked... but the tests are a bit wonky at the moment.


Make site error messages more descriptive

@antidipyramid will post screenshots of the current error messages (500 and 404) and @neilarellano will suggest changes.


shared/Avatar/Identicon warning

🙋♂

when this warning appear?

hey @leo-1228
i didn't see this warning anymore either on https://canary.kodadot.xyz
please check if you find it when running local
if not, lmk and i'll close this issue
thank you

this warning appears yet on local.

this warning comes from node_module, so i think we can not remove this warning.

I am waiting for your decision.

this warning appears yet on local

ok then, try and fix it

👋

@vikiival I investigated this issue and found that there's not much we can do to prevent it since it seems to be the issue with the @polkadot/vue-identicon package.


Update dependabot.yml

Hi @zhfeng, I updated the dependabot.yml

I think we should keep 1.x target since it is with quarkus 2.x


Link another command line guide, "The Art of Command Line."

Warning: Shameless self-promotion, as I wrote this one -- merge only if you think it's helpful! (It's a recently expanded Github version of some fairly popular answers from Quora.)
Part of my suggesting it is that it may actually be worth perusing this doc for further additions to awesome-shell as well. I actually think the two complement each other pretty nicely, as awesome-shell covers more novel, specific tools and fancy customizations, and TAOCL has the classic commands and tips everyone should know.

It's a nice, centralized source of answers. Definitely adding it! :+1:


Removal of master alias

Fixes #56
As soon as all deployed aliases have been removed, it is possible to remove the service by removing the master alias.

Coverage increased (+0.6%) to 55.337% when pulling 09b984ff6695b0b5d2da23a6b107406cc663b5d3 on removal-of-master-alias into 928a66c71e9e2964980869a44624106b44882de7 on master.

Coverage increased (+8.06%) to 62.827% when pulling 09b984ff6695b0b5d2da23a6b107406cc663b5d3 on removal-of-master-alias into 928a66c71e9e2964980869a44624106b44882de7 on master.

Coverage decreased (-0.9%) to 53.885% when pulling 4a93ce2a6e3dc1ac81ffd7c664722e349e6f2989 on removal-of-master-alias into 928a66c71e9e2964980869a44624106b44882de7 on master.

The implementation is finished and should do as expected. The coverage has to be turned positive now. Then it can be merged.

Coverage decreased (-1.1%) to 53.661% when pulling 3add03884f876979a9b2ea0638180eaf1713bfa5 on removal-of-master-alias into 928a66c71e9e2964980869a44624106b44882de7 on master.

Coverage increased (+6.4%) to 61.16% when pulling ceee07105546f36b3b4142d9cf0e61779f3d7bbd on removal-of-master-alias into 928a66c71e9e2964980869a44624106b44882de7 on master.

Coverage increased (+5.3%) to 60.08% when pulling 29046f46d1551acde319618dad55a2e525cf6162 on removal-of-master-alias into 928a66c71e9e2964980869a44624106b44882de7 on master.

Did the final tests. Everything workes as expected now.


Bump to lychee 0.8.2

I'd create a PR, but not sure which Docker tag corresponds to which version, TBH.

The Github pipeline recently got rewritten by @fauust and we need to add back version tags.
If you'd like to help out, here's the issue that needs to be fixed: https://github.com/lycheeverse/lychee/issues/417.

This is done in master and v1.13 now.


[New implementation] Refactor transform/detransform logic to be on the same component

Transforms and detransforms are on different components (URSM and ChunkManager) atm. These are tightly related and should be on the same component.
Discussion: https://github.com/aiven/tiered-storage-for-apache-kafka/pull/206#pullrequestreview-1416334242

I generally appreciate the motivation behind this, but would like to warn against making the code overly complex to achieve the goal if it comes to this. Let's stay practical :)

Sure, no priority for this until we have the RSM implementation merged into the new-implementation branch.
Just keeping track of the discussion on #206, let's revisit later.


Add optimize function and some docs

Add burn_from_targetleaves!, which removes all nodes connected to the target leaves via "Prod" operators.
Add docs for optimize.jl and forward_AD.

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

Comparison is base (69cf3d8) 64.45% compared to head (66e7940) 64.47%.

:exclamation: Current head 66e7940 differs from pull request most recent head b063a68. Consider uploading reports for the commit b063a68 to get more accurate results

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@               Coverage Diff               @@
##           computgraph     #141      +/-   ##
===============================================
+ Coverage        64.45%   64.47%   +0.02%
===============================================
  Files               56       56
  Lines             3688     3724      +36
===============================================
+ Hits              2377     2401      +24
- Misses            1311     1323      +12

Files
Coverage Δ

src/computational_graph/operation.jl
84.82% <ø> (-0.69%)
:arrow_down:

src/computational_graph/optimize.jl
94.48% <100.00%> (+0.90%)
:arrow_up:

... and 8 files with indirect coverage changes

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


Implement ex create image member openstack

implement ex_create_image_member and ex_accept_image_member in the OpenStack compute driver

Thanks! Can you please fix the lint?

According to https://bugs.launchpad.net/openstack-requirements/+bug/1753539, pinning libvirt-python to 4.0.0 should fix our issue.
Do you think you could open a pull request wich replaces all libvirt-python occurrences to libvirt-python==4.0.0 in tox.ini? That would be really helpful. Thanks!

sure, see https://github.com/apache/libcloud/pull/1180. I rebased this branch on that branch

Codecov Report

:exclamation: No coverage uploaded for pull request base (trunk@5231cec). Click here to learn what that means.
The diff coverage is 100%.

@@           Coverage Diff            @@
##             trunk    #1176   +/-   ##
========================================
  Coverage         ?   86.18%
========================================
  Files            ?      348
  Lines            ?    67173
  Branches         ?     5956
========================================
  Hits             ?    57891
  Misses           ?     6851
  Partials         ?     2431

Impacted Files
Coverage Δ

libcloud/test/compute/test_openstack.py
96.3% <100%> (ø)

libcloud/compute/drivers/openstack.py
84.44% <100%> (ø)

Continue to review full report at Codecov.

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

Thanks! Merged into trunk. ✨


[Feature Request] Make stacks collapsable

Description
In my container list i see a big collection of containers which are using the same stack:

why not adding a option to collapse them together?
heres a idea what would be very cool: (colors are just for the example)
Info: i added an example checkbox into the settings but its not checked. it should->

and the uncollapsed version:

Good point. I had a similar idea recently with the introduction of #1828 solving #461.
Now that we can list all the containers inside a cluster, I was thinking about listing only services and removing the containers view when connected to a Swarm cluster. In the services view,  I thought about making the services collapsable (pretty much as you show in your screenshots) with the underlying list of tasks when uncollapsed.
With #1828, that would allow us to redirect the user to the container details when clicking on any service task.
It should actually be possible to do the same with stacks, e.g. collapsable stacks with underlying collapsable services to give the user the ability to drill down to specific tasks from a stack.
I think this is an interesting discussion about UX, and that it should be continued after #1828 has been merged as it may help us determine a good direction to give a better UX when managing Swarm clusters.

At the moment, there is no point of using the agent on a single node Swarm cluster. Although in a near future we'll probably use the agent to collect host metrics.

i hope near time i will learn most of the Enterprise  definitions


Move 2019 font file to appropriate folder

@googlebot I signed it!
On Mon, Oct 7, 2019 at 11:41 PM googlebot<EMAIL_ADDRESS>wrote:

Thanks for your pull request. It looks like this may be your first
contribution to a Google open source project (if not, look below for help).
Before we can look at your pull request, you'll need to sign a Contributor
License Agreement (CLA).
📝 Please visit https://cla.developers.google.com/
https://cla.developers.google.com/ to sign.
Once you've signed (or fixed any issues), please reply here with @googlebot
I signed it! and we'll verify it.
What to do if you already signed the CLA Individual signers

It's possible we don't have your GitHub username or you're using a
different email address on your commit. Check your existing CLA data
https://cla.developers.google.com/clas and verify that your email is
set on your git commits
https://help.github.com/articles/setting-your-email-in-git/.

Corporate signers

Your company has a Point of Contact who decides which employees are
authorized to participate. Ask your POC to be added to the group of
authorized contributors. If you don't know who your Point of Contact is,
direct the Google project maintainer to go/cla#troubleshoot (Public
version https://opensource.google.com/docs/cla/#troubleshoot).
The email used to register you as an authorized contributor must be
the email used for the Git commit. Check your existing CLA data
https://cla.developers.google.com/clas and verify that your email is
set on your git commits
https://help.github.com/articles/setting-your-email-in-git/.
The email used to register you as an authorized contributor must
also be attached to your GitHub account
https://github.com/settings/emails.

ℹ Googlers: Go here
https://goto.google.com/prinfo/https%3A%2F%2Fgithub.com%2Fgooglefonts%2Fnoto-emoji%2Fpull%2F283
for more info.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/googlefonts/noto-emoji/pull/283?email_source=notifications&email_token=AH5CMSA3XALZLHT2D4626HLQNQTRJA5CNFSM4I6NT74KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEATAYAY#issuecomment-539364355,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AH5CMSH5T2BDVWAVF5GNPELQNQTRJANCNFSM4I6NT74A
.

Thanks for the PR!
I suggest accepting https://github.com/googlefonts/noto-emoji/pull/282 over this PR, as it fixes a bug in the font and updates the .ttf files.

@Some1NamedNate thanks. We'll remove the stale/duplicate file with #282.


feat(frontend): allow defining fixed modifier order in tfconfig

Description

Avoid unnecessarily fetching extension traces for excluded objects due to incorrect modifier order
Related issues

Special notes for your reviewer:

To be reviewed together with #150


switch to crates.io version of fiat-crypto

Previously, we vendored the generated code from the fiat-crypto
project. It was brought to our attention that the officially
published fiat-crypto on crates.io is sufficiently up-to-date
to use in Orion and that there's no need to manually vendor
the code.
Additionally, using the crates.io version integrates well
with Dependabot so we can get alerts when our version of fiat-crypto
is out of date. This was a challenge we would have had to solve
with the vendored code that we now get solved for free.

I left the module names the same and did the import with use fiat_crypto::curve25519_64 as fiat_curve25519_u64. @brycx let me know if you think it would be cleaner to just update all the module names. I personally don't have a strong opinion either way.

Rebasing upon master should fix the lint/deny actions previously failing.

The new release of the fiat-crypto crate should now provide no_std.


Can't use another port that default

Environment
Knex version: 0.21.5
Database + version: MySQL 8.0.21
OS: Manjaro Linux
Bug
I'm using this configurations to initialize the db connection:
{
  "host": "<IP_ADDRESS>",
  "port": 601,
  "user": "root",
  "password": "test",
  "database": "test"
}

Error message

Error: connect ECONNREFUSED <IP_ADDRESS>:3306
    at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1138:16) {
  errno: -111,
  code: 'ECONNREFUSED',
  syscall: 'connect',
  address: '<IP_ADDRESS>',
  port: 3306,
  fatal: true
}

@christian4leaflabs Could you please share full knex config? What you shared is a connection branch, I wonder if it is set correctly.
I've checked the code, and I think we are passing connection to mysql driver as-is, so that should work if used correctly.

@christian4leaflabs Could you please share full knex config? What you shared is a connection branch, I wonder if it is set correctly.
I've checked the code, and I think we are passing connection to mysql driver as-is, so that should work if used correctly.

Of course, the dbConfig var is the objet that i post before
dbCon = require('knex')({
    client: 'mysql2',
    connection: dbConfig,
    debug,
    pool: {
        min: 10,
        max: 30
    }
});

Of course, the dbConfig var is the objet that i post before
dbCon = require('knex')({
    client: 'mysql2',
    connection: dbConfig,
    debug,
    pool: {
        min: 10,
        max: 30
    }
});

@christian4leaflabs Can you try changing host in that dbConfig to see if config is actually being used and not overriden somewhere?

@christian4leaflabs Can you try changing host in that dbConfig to see if config is actually being used and not overriden somewhere?

Yes, when i change the host it throw me this error (the host that i use don't exist)
Error: connect ETIMEDOUT
    at Connection._handleTimeoutError (/home/path_to_project_folder/node_modules/mysql2/lib/connection.js:178:17)
    at listOnTimeout (node:internal/timers:556:17)
    at processTimers (node:internal/timers:499:7) {
  errorno: 'ETIMEDOUT',
  code: 'ETIMEDOUT',
  syscall: 'connect',
  fatal: true
}

Yes, when i change the host it throw me this error (the host that i use don't exist)
Error: connect ETIMEDOUT
    at Connection._handleTimeoutError (/home/path_to_project_folder/node_modules/mysql2/lib/connection.js:178:17)
    at listOnTimeout (node:internal/timers:556:17)
    at processTimers (node:internal/timers:499:7) {
  errorno: 'ETIMEDOUT',
  code: 'ETIMEDOUT',
  syscall: 'connect',
  fatal: true
}

@christian4leaflabs As you can see in #4232, port resolution works.
Can you try latest knex version? I don't think we changed any related code, but doesn't hurt to double-check.

@christian4leaflabs As you can see in #4232, port resolution works.
Can you try latest knex version? I don't think we changed any related code, but doesn't hurt to double-check.

Of course, i just update knex to the version 0.21.15 and the error is the same
Don't know if this help but if i do a log of the dbCon
console.log(dbCon.context.client);

i get this
<ref *1> Client_MySQL2 {
  config: {
    client: 'mysql2',
    connection: {
      host: '<IP_ADDRESS>',
      user: 'root',
      password: 'test',
      database: 'test',
      port: 601
    },
    debug: false,
    pool: { min: 10, max: 30 }
  },
  logger: Logger {
    _inspectionDepth: 5,
    _enableColors: true,
    _debug: undefined,
    _warn: undefined,
    _error: undefined,
    _deprecate: undefined
  },
  connectionSettings: {
    host: '<IP_ADDRESS>',
    user: 'root',
    password: 'test',
    database: 'test',
    port: 601
  },
  connectionConfigExpirationChecker: null,
  driver: {
    createConnection: [Function (anonymous)],
    connect: [Function (anonymous)],
    Connection: [class Connection extends EventEmitter],
    createPool: [Function (anonymous)],
    createPoolCluster: [Function (anonymous)],
    createQuery: [Function: createQuery],
    Pool: [class Pool extends EventEmitter],
    createServer: [Function (anonymous)],
    PoolConnection: [class PoolConnection extends Connection] {
      statementKey: [Function: statementKey]
    },
    escape: [Function: escape],
    escapeId: [Function: escapeId],
    format: [Function: format],
    raw: [Function: raw],
    createConnectionPromise: [Getter],
    createPoolPromise: [Getter],
    createPoolClusterPromise: [Getter],
    Types: [Getter],
    Charsets: [Getter],
    CharsetToEncoding: [Getter],
    setMaxParserCache: [Function (anonymous)],
    clearParserCache: [Function (anonymous)]
  },
  pool: Pool {
    destroyed: false,
    emitter: EventEmitter {
      _events: [Object: null prototype] {},
      _eventsCount: 0,
      _maxListeners: undefined,
      [Symbol(kCapture)]: false
    },
    creator: [AsyncFunction: create],
    destroyer: [Function: destroy],
    validate: [Function: validate],
    log: [Function (anonymous)],
    acquireTimeoutMillis: 60000,
    createTimeoutMillis: 30000,
    destroyTimeoutMillis: 5000,
    idleTimeoutMillis: 30000,
    reapIntervalMillis: 1000,
    createRetryIntervalMillis: 200,
    propagateCreateError: true,
    min: 10,
    max: 30,
    used: [],
    free: [],
    pendingCreates: [],
    pendingAcquires: [],
    pendingDestroys: [],
    pendingValidations: [],
    interval: null,
    eventId: 1
  },
  valueForUndefined: Raw [object] {
    client: [Circular *1],
    sql: 'DEFAULT',
    bindings: undefined,
    _wrappedBefore: undefined,
    _wrappedAfter: undefined,
    _debug: false
  },
  makeKnex: [Function: makeKnex],
  _events: [Object: null prototype] {
    start: [Function (anonymous)],
    query: [Function (anonymous)],
    'query-error': [Function (anonymous)],
    'query-response': [Function (anonymous)]
  },
  _eventsCount: 4
}

Of course, i just update knex to the version 0.21.15 and the error is the same
Don't know if this help but if i do a log of the dbCon
console.log(dbCon.context.client);

i get this
<ref *1> Client_MySQL2 {
  config: {
    client: 'mysql2',
    connection: {
      host: '<IP_ADDRESS>',
      user: 'root',
      password: 'test',
      database: 'test',
      port: 601
    },
    debug: false,
    pool: { min: 10, max: 30 }
  },
  logger: Logger {
    _inspectionDepth: 5,
    _enableColors: true,
    _debug: undefined,
    _warn: undefined,
    _error: undefined,
    _deprecate: undefined
  },
  connectionSettings: {
    host: '<IP_ADDRESS>',
    user: 'root',
    password: 'test',
    database: 'test',
    port: 601
  },
  connectionConfigExpirationChecker: null,
  driver: {
    createConnection: [Function (anonymous)],
    connect: [Function (anonymous)],
    Connection: [class Connection extends EventEmitter],
    createPool: [Function (anonymous)],
    createPoolCluster: [Function (anonymous)],
    createQuery: [Function: createQuery],
    Pool: [class Pool extends EventEmitter],
    createServer: [Function (anonymous)],
    PoolConnection: [class PoolConnection extends Connection] {
      statementKey: [Function: statementKey]
    },
    escape: [Function: escape],
    escapeId: [Function: escapeId],
    format: [Function: format],
    raw: [Function: raw],
    createConnectionPromise: [Getter],
    createPoolPromise: [Getter],
    createPoolClusterPromise: [Getter],
    Types: [Getter],
    Charsets: [Getter],
    CharsetToEncoding: [Getter],
    setMaxParserCache: [Function (anonymous)],
    clearParserCache: [Function (anonymous)]
  },
  pool: Pool {
    destroyed: false,
    emitter: EventEmitter {
      _events: [Object: null prototype] {},
      _eventsCount: 0,
      _maxListeners: undefined,
      [Symbol(kCapture)]: false
    },
    creator: [AsyncFunction: create],
    destroyer: [Function: destroy],
    validate: [Function: validate],
    log: [Function (anonymous)],
    acquireTimeoutMillis: 60000,
    createTimeoutMillis: 30000,
    destroyTimeoutMillis: 5000,
    idleTimeoutMillis: 30000,
    reapIntervalMillis: 1000,
    createRetryIntervalMillis: 200,
    propagateCreateError: true,
    min: 10,
    max: 30,
    used: [],
    free: [],
    pendingCreates: [],
    pendingAcquires: [],
    pendingDestroys: [],
    pendingValidations: [],
    interval: null,
    eventId: 1
  },
  valueForUndefined: Raw [object] {
    client: [Circular *1],
    sql: 'DEFAULT',
    bindings: undefined,
    _wrappedBefore: undefined,
    _wrappedAfter: undefined,
    _debug: false
  },
  makeKnex: [Function: makeKnex],
  _events: [Object: null prototype] {
    start: [Function (anonymous)],
    query: [Function (anonymous)],
    'query-error': [Function (anonymous)],
    'query-response': [Function (anonymous)]
  },
  _eventsCount: 4
}

@christian4leaflabs This looks correct and should work correctly. Can you try debugging and see if the error is actually being  thrown from this particular client instance and not from something else?

@christian4leaflabs This looks correct and should work correctly. Can you try debugging and see if the error is actually being  thrown from this particular client instance and not from something else?

I just create a simple project, the connection works fine with any port, it should be an error in my code, thanks for your help

I just create a simple project, the connection works fine with any port, it should be an error in my code, thanks for your help


Add method to convert GitHub issue to markdown

This pull request introduces GitHub issue conversion support to the markitdown project. The main changes include adding the pygithub dependency, implementing a method to convert GitHub issues to markdown, and adding corresponding tests.
GitHub issue conversion support:

pyproject.toml: Added pygithub to the list of dependencies.
src/markitdown/_markitdown.py: Added a new method convert_github_issue to convert GitHub issues to markdown format. This includes handling GitHub authentication and parsing issue details.
src/markitdown/_markitdown.py: Added a check for the optional GitHub issue support by importing the Github class from the pygithub library.

Tests:

tests/test_markitdown.py: Added a test case test_markitdown_github_issue to test the new GitHub issue conversion feature, including a skip condition if the GitHub token is not provided. [1] [2]

Looks good, but I'll test it when I get back in to town today.

I think my approach won't work with the CLI tho, I need to fix that.

I fixed the cli issue as well. still not sure if convert_stream would work.


Confusing bs::SceneObject/Components transform duplication

We create a light:
HSceneObject lightSO = SceneObject::create("Light");
HLight light = lightSO->addComponent<CLight>();

now we do:
lighSO->setPos({-1,0,0});
bs::Transform tf;
tf.setPosition({1,0,0})
light->_getLight()->setTransform(tf);

So have we set two positions on a single light ?
I think it's pretty confusing that Component such as Light or CAudioListener have embedded in themselves a whole other transform, independent from the SceneObject they are a part of.
Is my understanding incorrect, are Components in bsf not meant to be modeled after ECS components ?

In bsf components act as wrappers around lower level objects. Those lower level objects can then be implemented efficiently in their own systems, without needing to have an overhead or even the knowledge of the component system. Components usually require additional code and this approach cleanly separates the two. As an extra bonus it allows the whole framework to be used in a way without components.
Note that in your case _getLight() is an internal method and should not be called by normal users (as stuff will break unless used in a specific manner, as you have shown). Normally the SceneObject transform changes will get transfered to the underlying object, as the system deems necessary. This duplication could ultimately be eliminated, but probably be wont until profiling shows its impact is relevant.

Thanks for explaining :)


Fabo/rename classes

Description:
Renames the classes ni- to ti- as the preferred new namespace.

❤ Thank you!

tm- not ti-

Arrrrrr <<
will change this on Monday

Close in favor of #975


feat(Page): add headerTemplate and footerTemplate to PDF options

The Stable RC (1.3) release of Chrome DevTools Protocol includes new options for providing a custom header and footer templates to Page.printToPDF method - https://github.com/ChromeDevTools/devtools-protocol/blob/0956b7c770c81c49682f0e50589652dd818655fc/changelog.md#page-modified-command
They are available in Chrome Canary so we can start using them today.

this is great, thank you. The functionality was added recently in https://chromium-review.googlesource.com/c/chromium/src/+/813177; we need to roll first, and then we'll merge this in.
Also, this fixes the #373.

Sad it wasn't done with standards compliant css

@graingert agreed. CamelCase CSS classes are not very common

@aj-dev no I'm not refering to the CSS name 'defacto standard'
I'm talking about https://www.w3.org/TR/css3-page/


Spurious 'nil' named devices

Somehow some devices are being created with lots of nil information (for name, model_id, etc). Clearly this should not be happening but importantly these have been found to cause errors with the /devices endpoints. It is not clear at the moment where these are coming from although it may be related to running Hive Mind without the correct plugins installed.

Hive Runner IOs has been fixed to stop creating these spurious devices but there still needs to be a fix in Hive Mind to guard against it happening again.


[fix][tests] PersistentStreamingDispatcherBlockConsumerTest#testBrokerSubscriptionRecovery

Motivation
test example: https://github.com/apache/pulsar/runs/8128077384?check_suite_focus=true
We can expand read timeout to avoid missing messages.
Modifications
-Expand receive timeout from 500 million seconds to 10 seconds.
Verifying this change

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

(Please pick either of the following options)
This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end deployment with large payloads (10MB)
Extended integration test for recovery after broker failure

Does this pull request potentially affect one of the following parts:
If yes was chosen, please highlight the changes

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API: (yes / no)
The schema: (yes / no / don't know)
The default values of configurations: (yes / no)
The wire protocol: (yes / no)
The rest endpoints: (yes / no)
The admin cli options: (yes / no)
Anything that affects deployment: (yes / no / don't know)

Documentation
Check the box below or label this PR directly.
Need to update docs?

[ ] doc-required
(Your PR needs to update docs and you will update later)

[x] doc-not-needed
(Please explain why)

[ ] doc
(Your PR contains doc changes)

[ ] doc-complete
(Docs have been already added)

Hi @mattisonchao
Sorry, I think it is not the root cause, I have submitted another PR to fix this flaky-test :

#17418

Hi @mattisonchao
Sorry, I think it is not the root cause, I have submitted another PR to fix this flaky-test :

#17418

Got it, thanks


make sure all users are in Mobile Commons and MailChimp

from both Friday afternoon and Saturday night

There is a disparity in the numbers. Drupal reports about 4700 users being added during that period, but Mobile commons and Northstar numbers are off by up to 2000.  Digging deeper to figure out the correct number and diff.

Creation numbers during the Saturday night downtime match up a lot closer:
From 2015-10-03 20:25:00 GMT - 2015-10-04 06:30:00 GMT:
Northstar: 462
Drupal: 447
Mobile Commons: 551

Could this be the Niche imports? I'm seeing 1,638 on Oct 3rd and 1,428 on Oct 4th

Potentially eff'd pending resolution of this ticket. If not effed, at least blocked by: https://github.com/DoSomething/phoenix/issues/5549

Re-check this pending resolution of #5549

User accounts accurate here as well.


Add stackdriver instance monitoring to auto run script

Apologies for all of the commits... Squash!!

Why does Travis crash in Selenium all the time? What is that dude's problem!!?


Replace io.ReadAll usage with pre-allocated buffers of appropriate size

There is a potential performance/memory improvement when reading the contents of a nested jar by replacing io.ReadAll:
Internally, io.ReadAll will allocate a byte slice (initially 512 bytes) and then expand the size of the buffer as needed when each (io.Reader).Read call is executed. In practice this means a slice will be allocated and resized multiple times when reading most jar files.
Because the size of the file is already known the buffer could be allocated initially at the exact size required. This is essentially what os/io.ReadFile does internally and the implementation could be copied almost exactly into a helper method.

Hey @lyoung-confluent,
We generally won't take performance CLs unless there's an associated benchmark that demonstrates that benefit it meaningful. Premature optimization and all that :)
We had someone looking at the performance internally, and there are definitely places to improve.
If you are looking into improve performance, please look at a tool like https://pkg.go.dev/golang.org/x/perf/cmd/benchstat so there are comparisons.

@lyoung-confluent See #40 which should resolve this.

Closed via https://github.com/google/log4jscanner/pull/40


Reworks on ImlValue

This pull request is intended to do several reworks on ImlValue.

Closed this PR due current lack of time and unable to find a better solution for the current implementation instead of rewriting huge parts of the compiler again.


Prototype issues with documents containing elements named <proto>

Hi,
This issue might have a security impact (albeit I personally think the severity is minor). Since most people prefer to receive security reports privately, I attempted to email first. However I received no response, so I decided to file an issue.
If the XML document being parsed uses names like __proto__, it could cause the returned objects prototype to be replaced. This could cause confusion, and might result in documents being misinterpreted. Note, as far as i can tell, this only allows replacing the prototype, and not modifying the existing prototype, which I believe limits the severity of this bug.
As an example, say you wanted to know if the root element of a document is <foo>. You might do something like
require('xml2js').parseString( '<foo></foo>', {},
  (e,r) => {
    if('foo' in r) {
      console.log( "We have a foo document");
    }
  }
);

However, the code won't work as expected with the following document:
require('xml2js').parseString( '<__proto__><foo></foo></__proto__>', {},
  (e,r) => {
    if('foo' in r) {
      console.log( "We have a foo document");
    }
  }
);

This will say its a foo document, eventhough the root element is not foo.
One potential fix for this issue, would be to create the objects using object.create( null ); so that keys named __proto__ don't have special meaning.
Credit for discovering this issue should go to Dylan Katz of Leviathan Security.

Thanks for the report. Closed by #603.

Thanks for the report. Closed by #603.

I'm seeing a similar issue with these changes.  It results in "[Object: null prototype]" in each level of the result object, which wasn't there before.  So my test was failing, until I resolved by surrounding with "JSON.parse(JSON.stringify(result))".
Example, for this input:
"200Accepted"
Expected:
{       lsResponse: {         status: [           {             code: [ '200', [length]: 1 ],             reason: [ 'Accepted', [length]: 1 ]           },           [length]: 1         ]       }     }
But received:
``
[Object: null prototype] {
  lsResponse: [Object: null prototype] {
    status: [
      [Object: null prototype] {
        code: [ '200', [length]: 1 ],
        reason: [ 'Accepted', [length]: 1 ]
      },
      [length]: 1
    ]
  }
}
``

With jest, "expect(result).toStrictEqual(expected);" was now failing, until the above mentioned parse/stringify was added.

I assume this is just how "data-only" object (that is such without prototypes) are rendered in string form, it's not additional data (if anything, it is less data). So you'd need to change your expected object to be one that also doesn't have prototypes.

Every JS object has a prototype implicitly when you create it via e.g. {}.
The reason why xml2js was bumped from 0.4 to 0.5 was the breaking change from #603 which started creating the objects returned by xml2js without prototypes.
So you're comparing objects without prototypes to objects which have prototypes and they're not equal. So you either need to use a comparison function that ignores it or remove the prototypes from your expected result.


ci(build): Reusable private cloud build

Thanks for submitting a PR! Please check the boxes below:

[x] I have run pre-commit to check linting
[x] I have added information to docs/ if required so people know about the feature!
[x] I have filled in the "Changes" section below?
[x] I have filled in the "How did you test this code" section below?
[x] I have used a Conventional Commit title for this Pull Request

Changes
Contributes to #3718.
This pull request improves our build toolchain to clarify our shipping targets and make building them more accessible. It integrates Private Cloud builds into our platform PR workflow, allowing us to run the E2E test suite against it. It streamlines our deployment workflows, allowing deploy jobs to benefit from Depot caching and cleanly segregates deployment configurations between GitHub environments. It sets up Trivy Docker image scan result uploads to the repo's Security tab, enabling us to address detected vulnerabilities ahead of releases. This PR is large, so I'll break down the changes below.
Single Dockerfile for all targets
I consolidated multiple Dockerfiles into a single Dockerfile containing all build stages. We ship multiple Docker targets:

Private cloud: Unified
SaaS: API
Open Source: API, Frontend, Unified

Previously, Private Cloud and SaaS were awkwardly distributed between API and Unified Dockerfiles and corresponding GHA workflows. The private backend code was manually pulled by the workflow, and a special build argument controlled whether the dependencies for it should be installed. SaaS deployments required specifying private backend code versions for each environment. Changes to the private side required touching two Dockerfiles and 2-3 workflows and hoping the build worked since it was only reproducible in GHA.
Now, every target, including Private Cloud and SaaS, can be built using docker build, provided the required secrets are mounted. The final stages are minimal, assembled from building blocks factored out of our former Dockerfiles and GHA workflows. All stages are documented for easy navigation.
The CI_COMMIT_SHA, .versions.json, and edition markers are now explicitly requested by the Docker build instead of being added by GHA workflows. Permanent caching for the backend's get_version_info utility has been added.
To demonstrate improved build sanity, I've added a Private cloud API target. The stage's code is just 5 lines. I've also created private-cloud-api private repositories in our GitHub Container registry and Docker Hub organization.
The docker build -t flagsmith:local . command remains fully backward compatible due to the oss-unified stage being the last one.
Private cloud images built for PRs and on merge to main
The "Platform Pull Requests" workflow now builds a Unified Private cloud image, enabling faster testing of enterprise features. E2E tests are now run against both Open Source and Private cloud API image versions. We can also deliver improvements and bug fixes to enterprise clients ahead of releases by offering a PR or a staging image.
ECS deployments with less fat
Deployment configuration data values have been moved to their respective GHA environments, allowing a reusable ECS deployment workflow for both staging and production. The workflow uses Depot and the new Dockerfile to leverage cached build stages. The change also results in less infrastructure-specific data in our workflow code.
Platform workflow publishes all Docker images
All Docker image building and publication have been consolidated in .github/workflows/platform-docker-build-test-publish.yml, triggered on merges to main and releases. Images are built for every merge and release, and published on release only if an E2E run is successful. After successful image publication, a PR to flagsmith-charts is created. Individual Docker image publication workflows have been removed.
CodeQL reports
CodeQL has been enabled for the repository. In addition to free code scanning, Docker image scan results are now available as part of CodeQL reports. Alerts/CI failures will occur on newly detected critical issues.
Bits and Pieces

Added the install-private-modules Makefile target for use outside of Docker builds, i.e., by the "Run API tests with private package" workflow.
Removed .ubi Dockerfiles as they are no longer needed.
Removed E2E image publication to Docker Hub; those needing it can pull from ghcr.io/flagsmith/flagsmith-e2e.

To do / to think on

Consider making the SSE PGP key a runtime dependency to build the SaaS API target once per deployment, not per environment.
Avoid invoking docker build on release trigger; re-tag the main branch images instead. To do that, ensure release jobs run after the latest main branch builds complete, e.g. using a concurrency group.
Reevaluate Uffizzi's reusable workflow to remove boilerplate.
Consider adding the E2E image to the mega-Dockerfile targets.
Avoid duplicating the Private cloud build for the "Run API tests with private package" workflow.

How did you test this code?
Docker builds were tested locally with docker build.
We need a plan for testing the ECS deployment workflow.

One general question I had though is around the Dockerfile and whether we're always building all stages and then using the relevant builds to output the target image, or if docker is smart enough to know, for example, to not build the stages it doesn't need.

@matthewelwell Buildkit (which we use) does skip unneeded stages: https://docs.docker.com/build/building/multi-stage/#differences-between-legacy-builder-and-buildkit


Remove Properties accordion from the Properties Pane

There will be no need for this accordion as all of the information shown there will be displayed under Providers accordion now, once issue #662 is implemented.

@igor-ka Can this be removed now, or should it wait for the #662 implementation?

It was already removed in 662 normally


[BUG] SQL transformations result in "Relation does not exist" error when mapping from CSV file

I am using a csv file perseusDemoTable, and getting this error when I attempt to use any transformations:

SOLVED: The problem goes away when I rename the csv file perseusdemotable (no caps) and re-scan data

Can you share the csv file that cause the error?

perseusDemoTable.csv

fix was added to perseus-api


B1

Name: minikfare
Id: bbc350348054be0f

concordium-testnet-node-1b7b0619f86edef0a0481d2a7e2a82c80108a77c767e61fad852cc30eab77f2a.log
concordium-testnet-system-report.log

confirmed:B1
node:bbc350348054be0f


[msal-node] SilentFlow node interface

This PR adds support for:

acquireTokenSilent in msal-node
getAccounts() and removeAccount support in msal-node/CacheManager.ts

Pending:

Unit tests for silent flow
Sample for silent flow

Coverage remained the same at 77.514% when pulling 56f38efe43141672274a6aabc11ddc47745af6fb on msal-node-silent-flow-client into f842023c056f985e6603330666e7775f11870ccd on dev.


tf.nn.relu on nan inputs returns zeros on GPU

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): Yes, see below.
OS Platform and Distribution: Ubuntu 16.04, Google Colab
TensorFlow installed from: binary
TensorFlow version: 2.2
Python version: 3.6.9
CUDA/cuDNN version: 10.1, 7.6.5
GPU model and memory: GeForce GTX 1080 (8GB) (and Google Colab)

Describe the current behavior
The behavior of tf.nn.relu when fed with nan-valued inputs is inconsistent between GPU and CPU:

The CPU returns nan (as expected).
The GPU returns 0, obfuscating nan in the computation.

Similar (but not quite identical) behavior has been described for TF1.14 in #32730 and subsequently fixed in TF1.15.3, but remains in TF2.2
Describe the expected behavior
All devices should show consistent behavior like the CPU, returning nan.
Standalone code to reproduce the issue
The following snippet can also be found in this Colab notebook.
The first three assertions do not fail. The last three assertions all fail. This is a bit different from #32730, where the x1 assertion worked.
x1 = tf.nn.relu(np.nan)
x2 = tf.nn.relu(np.nan * tf.random.normal(shape=[]))
x3 = tf.nn.relu(tf.Variable(np.nan))
with tf.device("/cpu:0"):
    x1_cpu = tf.nn.relu(np.nan)
    x2_cpu = tf.nn.relu(np.nan * tf.random.normal(shape=[]))
    x3_cpu = tf.nn.relu(tf.Variable(np.nan))

assert np.all(np.isnan(x1_cpu.numpy()))
assert np.all(np.isnan(x2_cpu.numpy()))
assert np.all(np.isnan(x3_cpu.numpy()))

assert np.all(np.isnan(x1.numpy()))
assert np.all(np.isnan(x2.numpy()))
assert np.all(np.isnan(x3.numpy()))

I am able to replicate the issue, please find the gist here Thanks!

Please be aware of https://github.com/tensorflow/tensorflow/issues/42885#issuecomment-687151509 if you are going to retest this on colab again.
That duplicated issue was closed as solved but it isn't solved.

@msoelch Looks like this was resolved in 2.4rc3 that was just released. Can you please check and let us know whether it was resolved or not for you. Here is the gist for our reference. Thanks!

Looks good, thank you!


Aspen 0.37

Rebased on master and added commits for notifications.json.spt.

I may have muddied the water with that last commit, @Changaco, but your commits lgtm.


Updating dependencies status bar label never disappears

Spotted why this happens as part of #365 and fixed there. (Although there's a bug there that means it won't succeed yet!) I'll close this for now. Once 365 is closed please try develop branch again.


[Bug] Plugin makes it impossible to apply patches using the Git plugin

Nevermind

Do you have any further context on how I can reproduce the issue? :)

Do you have any further context on how I can reproduce the issue? :)

Sorry for the late response, some steps to reproduce the issue:

Open a project in IntelliJ
Make some changes and don't commit them
Click Git > Patch >  Create patch from Local Changes...
Click Create Patch...
Select the "To file" radio box
Enter a path you'll remember (we need it for later)
Click OK
Rollback your changes
Click Git > Patch > Apply Patch...
Navigate to the folder where you saved the patch in Step 6
Select the patch
The "OK" button will be disabled, which does not occur without the plugin.

Reproducible on my machine. I will try to find a solution soon-ish.
Thanks for reporting! :)

This plugin creates new file type Diff/Patch.  And if we assign *.diff/*.patch for this file type, we can see highlighting, but lose ability to apply patch.
But there is present file type named Patch. If we assign *.diff/*.patch for this file type, we can't see highlighting, but can apply patches.

@plamenjm PRs are very welcome! I have not yet found out how this problem occurs.

Above you said that you can reproduce it ;)
I just wanted to clarify for someone else who wonder what and why
Rename the file to ".txt" and it works.

Indeed, I can reproduce it... But I cannot fix it apparently :)


[url_launcher] Clarify supported platforms

Description
Clarify supported platforms for url_launcher which incorrectly states that only Android and iOS are supported.
Related Issues
None.

We apologize for the long delay in triaging this PR. We’re in the process of overhauling our PR triage system to respond much more quickly, as well as working through the backlog.
Thanks for the contribution, but this has since been fixed in another PR, so I'm going to close this as obsolete.


Upgrade to React 18

The current UI is running on React 17.
Now that react 18 is 2 years old, and that I've seen some libraries have a react dependency react@^18, upgrading UI should be done.
React 18 upgrade guide

Also upgrade:

[ ] react-markdown


Dsylaiev/tdi 38816 add check that schema and db filled

What is the current behavior? (You can also link to an open issue here)
Wizard show all tables without filling "schema" and "database" properties
What is the new behavior?
Wizard show error message
Please check if the PR fulfills these requirements

[x] The commit message follows Talend standard
[x] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features) ?
[ ] The code coverage on new code >75%
[ ] The new code does not introduce new technical issues (sonar / eslint)

What kind of change does this PR introduce?

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build / CI related changes
[ ] Other... Please describe:

Does this PR introduce a breaking change?

[ ] Yes
[x] No

If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...
Other information:

Pull request test result: success :star:


How to receive en forward email?

Hi,
What I want and can't achieve is receive an email from an external system, and forward it to another email.
I understand postal has no IMAP / POP, but forwarding is great enough for me.
As you know, there is not so much free emails that allow you to use custom domain, so this would be my use case. Also would use it to blacklist emails and optimize bounce rate.
Now, I try to create the email<EMAIL_ADDRESS>When an external system send an email to<EMAIL_ADDRESS>it should be redirected to<EMAIL_ADDRESS>I Created an address Endpoint<EMAIL_ADDRESS>Then I created a route:
Name<EMAIL_ADDRESS>Endpoint<EMAIL_ADDRESS>My MX Domain is green : mx.mail.kendozone.com
But when I send an email from Mac Mail, I get : 550 5.1.1<EMAIL_ADDRESS>User unknown
What am I forgetting?

Probably a DNS cache. That error isn't from the Postal SMTP server.

Looking at the DNS for kendozone.com you have two MX records. One for mx.zoho.com and another for mx.mail.kendozone.com. A message could be sent to either of these servers.

Can't I use both? I actually use zoho to send my emails, I would love to replace it with Postal, but I wouldn't like to interrupt system.

Ok, I deleted my olds MX records. I will wait now...

When I make a try in Send Message > Incoming, I get :
550-Verification failed for<EMAIL_ADDRESS>550-The mail server could not deliver mail to<EMAIL_ADDRESS>The account or domain may not exist, they may be blacklisted, or missing the proper dns entries. 550 Sender verify failed
Time: 0.42s
Support Ref: ZDDCWXVX

In DNS, I have : psrp CNAME rp.mail.kendozone.com
So it should be ok.

Your DNS is broken/wrong/incorrect.
pob:~$ host psrp.kendozone.com
pob:~$
That does not resolve to anything, which is probably why you're getting that error.


Figure out why font 'names' table is invalid

OS X is complaining about an issue with the font 'name' table. Need to look into this.
The font installs fine though.

Closed by 9d77cc2ca6c830c7ce4feb65e82b70119cfc2e69
Wrong issue #


[Feature Request] Open Space Page

Is your feature request related to a problem?
Open space page should be ready. It should have a detail description of this activity.
Describe the solution you'd like
Copy the open space page template from 2019 and change the style to 2020 theme.
Additional context
This would be a collaboration between the Design and Program team. A draft page can be copied first and make it available to the Design team so they can work on the style for this year. Program team member can work on the data in parallel.

@Lee-W 這邊要麻煩議程組生文案 (中文/英文)。

其實他們已經有產文案了 不過有一部分的的英文沒還沒翻譯完成。


Middleware deployment icons not being shown [due to invalid path]

While visiting a middleware deployment details page, the icon on the left is missing/broken (both for WAR and EAR).
See from the screenshot that the path is invalid, as it misses (at least) the extension, and I guess also the  hash string other images paths have.

@miq-bot add_label providers/hawkular, ui, bug
cc @abonas

@ammendonca thanks for reporting this, is this similar or different than this issue I opened recently?

imo it sounds related to #8780 , but it's about a font icon, while here this is about png?
please check if this is middleware (hawkular) specific bug or a more general like the other one.
in the latter case, please rephrase the issue accordingly as a more general one.

@abonas, indeed, this looks similar to #8780 but, since yours was font icon related and fix is likely different, thought it would be good to create a separate issue.
I don't have anything else provisioned at the moment to check, will try to confirm if this is a more general issue.
Anyway, while testing a bit more, I have noticed that the same issue happens when switching to tile or grid view in "Middleware Servers" for instance.

imo this is caused by #8734 cc @mzazrivec

@abonas All but middleware decorators use path rather than the image name. Some of
the models have the listicon image under 100/, some of them under ico/, some of them
under svg/, some under pictures/. So today we can use a png image for, tomorrow we can
switch it to svg.
If we'd have only the image name in the decorators, we'd have to have the per-model logic
of what's going to be where somewhere else, scattered all across our code.
@himdel ?

Yes, there was a confusion about what the decorator should return, I'm probably partly responsible, sorry :)... But we definitely need to be consistent and we do want the whole path in the decorator now, because otherwise, we'd still need some logic somewhere to determine the directory and extension .. which is exactly what the decorator is for :).
If we were using the directories as something like "use 100/ for big icons and ico/ for small ones", and always had 100/foo and ico/foo for any foo, then sure, that'd make sense. But what we're really doing is we're pretty much using the directory to distinguish between new icons, older icons and user-submitted icons. And for that... well, the only thing that really makes sense is having the whole path in the decorator, so that doing image_path(decorator_output) will always give you the right file.

Btw @himdel the usage of we do want the whole path in the decorator now is inconsistent, as topology and listview work without full path, while the quadicon requires the full path.


[documenttranslator] Migrate @azure-rest/ai-document-translator to ESM/vitest

Packages impacted by this PR

@azure-rest/ai-document-translator

Issues associated with this PR

https://github.com/Azure/azure-sdk-for-js/issues/31338

Describe the problem that is addressed by this PR
Migrates the @azure-rest/ai-document-translator package to ESM/vitest using code automation.
What are the possible designs available to address the problem? If there are more than one possible design, why was the one in this PR chosen?
Are there test cases added in this PR? (If not, why?)
Provide a list of related PRs (if any)
Command used to generate this PR:**(Applicable only to SDK release request PRs)
Checklists

[ ] Added impacted package name to the issue description
[ ] Does this PR needs any fixes in the SDK Generator?** (If so, create an Issue in the Autorest/typescript repository and link it here)
[ ] Added a changelog (if necessary)

API change check
API changes are not detected in this pull request.


create form for donations backend

create a web form to post information to the database mentioned in issue #8

Can i take up this issue?

answered in that thread.


How to inserting outer text in VUEMCE Editor where the cursor is?

There is a text which is outside the editor By clicking on it, this will add where the cursor is located.
The outer text will be multiple.

Have the same question, have you ever figured this out?

Doesn't Ctrl+C/Ctrl+V work in this case?

Well in my case I needed to programmatically insert an image at current cursor position of the editor, managed to achieve that with this code
//items is an array of image sources
addImages(items){
            let images = items.map(el => el.image);
            let ed = tinymce.activeEditor;             // get editor instance
            images.map(el => {
                let range = ed.selection.getRng();                  // get range
                let newNode = document.createElement("img");  // create img node
                newNode.src = el;                           // add src attribute
                newNode.classList.add('img');
                newNode.classList.add('h-auto');
                range.insertNode(newNode);
            });
        }

@Eazymov Oh, I didn't know about this as I'm new to tinymce. Thanks!


Typo in UserModel

User model has a typo:
playerLevel:{type: Number, default: 1, requried: true},
Should be "required"

Resolved


Install camera-plus

install the camera-plus plugin?

This does not describe any issue that you are having.
Please explain the issue you are encountering, examples or logs of the problem, anything that can help.

This does not describe any issue that you are having.
Please explain the issue you are encountering, examples or logs of the problem, anything that can help.

@Codex- I try to install the plugin in my ns7 project, but it installed version 3.2.2.
Using the instructions that are in nativescript-plugins / packages / nativescript-camera-plus /

@Codex- I try to install the plugin in my ns7 project, but it installed version 3.2.2.
Using the instructions that are in nativescript-plugins / packages / nativescript-camera-plus /

@Codex- I too am having issues installing the latest version from NPM (3.2.2). I get Module not found: Error: Can't resolve 'tns-core-modules/file-system/file-system' when i run the app, and under closer inspection, it appears as though the NS7 PR you made (and in this repo) have not been applied as all the imports are from tns-core-modules rather than @nativescript/core

@Codex- I too am having issues installing the latest version from NPM (3.2.2). I get Module not found: Error: Can't resolve 'tns-core-modules/file-system/file-system' when i run the app, and under closer inspection, it appears as though the NS7 PR you made (and in this repo) have not been applied as all the imports are from tns-core-modules rather than @nativescript/core

We haven’t published a nativescript 7 version of camera plus yet - it’s in progress on this repo and currently just working with some iOS updates.

We haven’t published a nativescript 7 version of camera plus yet - it’s in progress on this repo and currently just working with some iOS updates.

I have tried the plgunin camera-plus using plain / typescript but with angular it does not work, I have tried to load the module or with registerElement but the camera does not show. I have tested it with android and ios.

I have tried the plgunin camera-plus using plain / typescript but with angular it does not work, I have tried to load the module or with registerElement but the camera does not show. I have tested it with android and ios.

I have a project with angular, which loads the module but does not show the camera and does not generate any error.

I have a project with angular, which loads the module but does not show the camera and does not generate any error.

I have the same problem

I have a project with angular, which loads the module but does not show the camera and does not generate any error.

I have the same problem

I have a project with angular, which loads the module but does not show the camera and does not generate any error.

Following.

I have the same problem

I have a project with angular, which loads the module but does not show the camera and does not generate any error.

Add inside main.ts registerElement("CameraPlus", () => CameraPlus);
In NS7 works fine with android, but iOS need updates


Cannot connect to remote Rclone repository over SSH

I'm not able to access a repository running via Rclone on a remote server over SSH.  If I select the RCLONE method, and enter the "rclone:remote-storage:bucket_name" for the Bucket, I get:

Failed to open repository: Fatal: unable to open repo at rclone:remote-storage:bucket_name: cmd.Start: exec: "rclone": executable file not found in $PATH

Normally I run it like this:

/usr/bin/restic --option rclone.program="ssh<EMAIL_ADDRESS>rclone" --option rclone.args="serve restic --stdio --b2-hard-delete --drive-use-trash=false --verbose" --repo rclone:remote-storage:bucket_name --password-file /etc/restic/password --verbose ${@}

Maybe there's no allowance for starting the REST server over SSH and running Rclone through the tunnel?  Is this the problem?
The Restic documentation for this is at Other Services via rclone.

I am seeing the same error but this is the command I use which works from terminal on macos
`restic -r rclone:onedrive:..... snapshots'

There's an unpublished fix for the rclone PATH handling here: https://github.com/emuell/restic-browser/pull/92
You can download binaries containing this fix here: https://github.com/emuell/restic-browser/actions/runs/7425075508
The fix will lookup rclone in some "common" paths and also adds a command line arg to specify the path to rclone manually.
The rclone.args option is not supported, but can probably be set via rclone's regular environment settings. However, you will need to run Restic Browser from the terminal then to set the environment variables.

Working - thanks.

I'm not able to access a repository running via Rclone on a remote server over SSH. If I select the RCLONE method, and enter the "rclone:remote-storage:bucket_name" for the Bucket, I get:

Failed to open repository: Fatal: unable to open repo at rclone:remote-storage:bucket_name: cmd.Start: exec: "rclone": executable file not found in $PATH

Normally I run it like this:
* `/usr/bin/restic --option rclone.program="ssh<EMAIL_ADDRESS>rclone" --option rclone.args="serve restic --stdio --b2-hard-delete --drive-use-trash=false --verbose" --repo rclone:remote-storage:bucket_name --password-file /etc/restic/password --verbose ${@} `

Maybe there's no allowance for starting the REST server over SSH and running Rclone through the tunnel? Is this the problem?
The Restic documentation for this is at Other Services via rclone.

I was in a similar situation. I solved with this workaround:
restic-browser --repo rclone:remote-storage:bucket_name --password-file /etc/restic/password \
--restic /absolute_path/restic.sh

where restic.sh is
#!/bin/bash
/usr/bin/restic --option rclone.program="ssh<EMAIL_ADDRESS>rclone" \
--option rclone.args="serve restic --stdio --b2-hard-delete --drive-use-trash=false --verbose" $@


docs: espcoredump.py now esp-coredump? (v5.0) (IDFGH-7782)

With release/v5.0 branch out I'm now developing against that. I saw it mentioned in the forum that API would likely not be changing much, but looks like there's still things trickling in.
Do not see anything about these methods changing in the docs yet:

espcoredump.py - still in PATH but no longer executable, seems like you need to now execute esp-coredump?
spi_flash_erase_range - removed, now must use esp_flash_erase_region?

If more comprehensive doc edits are on the way feel free to close, but just thought I'd document these.

Hi @someburner,
Thanks for reporting the issue about espcoredump missing the executable flag! This was also noticed internally and the fix is on the way. We will also update the docs.
As for the spi_flash API removal, this is mentioned in the migration guide: https://docs.espressif.com/projects/esp-idf/en/latest/esp32/migration-guides/peripherals.html#breaking-changes-in-legacy-apis. If you have noticed any other place in the docs which still references the old functions, please let us know and we'll fix that!

I was going to mention that the json file in the IDF needed to be writeable which causes problems on linux if you have read-only access to the toolchain. But looks like you made a new issue https://github.com/espressif/esp-idf/issues/9329


Cannot display ads using React native 0.60.4 android

I upgraded my project to react native 0.60
Everything is fine.
Using test ads is working
IOS is working
But in android, I can’t always show ads.
Error: The ad request was successful, but no ad was returned due to lack of ad inventory.
Install an old version of apk to display ads
But the apk under react native 0.60 can't display ads.
Can someone help me?

buildTypes {
        debug {
            debuggable true
        }
        release {
            minifyEnabled enableProguardInReleaseBuilds
            signingConfig signingConfigs.release
            proguardFiles getDefaultProguardFile("proguard-android.txt"), "proguard-rules.pro"
        }
    }

Edit
In /app/build.gradle
signingConfig signingConfigs.debug
to
signingConfig signingConfigs.release


add more types

:pushpin: Commit 1e7a8d1 has been approved by japaric

@homunkulus r+

:hourglass: Testing commit 1e7a8d1 with merge 1e7a8d1...

:sunny: Test successful - status-travis
Approved by: japaric
Pushing 1e7a8d1997b2a59d4a39bc18d1dab226e67d135f to master...


hover doen not work in jupyter notebook when use pylance server

Environment data
version: 1.52.1 (user setup)
commit: ea3859d4ba2f3e577a159bc91e3074c5d85c0523
date: 2020-12-16T16:34:46.910Z
Electron: 9.3.5
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.18363
##issue screen

Is this the new notebooks view, or the old one? The updated one should work, but I don't believe the older webview-based one works with hover.

Is this the new notebooks view, or the old one? The updated one should work, but I don't believe the older webview-based one works with hover.

Yes, it is the old one jupyter in latest stable version vscode,

Yes, it is the old one jupyter in latest stable version vscode,

Yeah, I don't think the old one will work. Can you try out the new notebook view, which shouldn't have that limitation?

Yeah, I don't think the old one will work. Can you try out the new notebook view, which shouldn't have that limitation?

Do you mean the new jupyter is in insider vscode? There are still many problems with that version of jupyter.

Do you mean the new jupyter is in insider vscode? There are still many problems with that version of jupyter.

Yes, but it's the more featureful of the two given it plugs directly into VS Code's UI, hence why I am asking.

Yes, but it's the more featureful of the two given it plugs directly into VS Code's UI, hence why I am asking.

Hi, any plane to solve this issue?

Hi, any plane to solve this issue?

I don't think there is anything we can do on this tracker; we will answer any hover call we get, so it is up to the Jupyter extension to call the code. My impression is that they get this feature "for free" with new notebooks, versus old notebooks missing this due to it needing to be implemented from scratch.
I'm going to transfer this issue, since we can't affect the UI that calls us (and we can figure out what's going on with the right people present).

I don't think there is anything we can do on this tracker; we will answer any hover call we get, so it is up to the Jupyter extension to call the code. My impression is that they get this feature "for free" with new notebooks, versus old notebooks missing this due to it needing to be implemented from scratch.
I'm going to transfer this issue, since we can't affect the UI that calls us (and we can figure out what's going on with the right people present).


gutentags fails while writing working copy with fugitive :Gdiff if index is modified

Hi, encountered a bit of a corner case: If I use :Gdiff (from fugitive) and I make some change to the index (left) (e.g. dp from working copy), then decide to modify something in the working copy (right) and write it to disk using :w without having written the index (left) I get the following error from gutentags:
Error detected while processing function <SNR>148_write_triggered_update_tags[3]..<SNR>148_update_tags[34]..gutentags#ctags#generate:
line 113:
"fugitive:///path/to/repo/.git//0/filename.ext" E212: Can't open file for writing
Error detected while processing function <SNR>148_write_triggered_update_tags:
line 3:
E170: Missing :endfor

Hi!
I tried reproducing this but I wasn't able to.... the index buffer (left) was left edited, and Vim only asked me to save it when I discarded it (to which I said "no"). Maybe somehow you have something that auto-saved your edit?

Ludovic Chabant writes on april 19, 2017 7:14:

Hi!
I tried reproducing this but I wasn't able to.... the index buffer (left) was left edited, and Vim only asked me to save it when I discarded it (to which I said "no"). Maybe somehow you have something that auto-saved your edit?

Hm, weird - that might be, I'll re-try on a few other repositories as
well.
Regards, Gaute

I've also encountered this issue. Looks like the setting autowriteall is what causes this auto saving.  I've hacked together this change that looks like it fixes the issue for me.
diff --git a/autoload/gutentags.vim b/autoload/gutentags.vim
index 563eb5d..57575fd 100644
--- a/autoload/gutentags.vim
+++ b/autoload/gutentags.vim
@@ -270,7 +270,7 @@ function! gutentags#setup_gutentags() abort
     let l:bn = bufnr('%')
     execute 'augroup gutentags_buffer_' . l:bn
     execute '  autocmd!'
-    execute '  autocmd BufWritePost <buffer=' . l:bn . '> call s:write_triggered_update_tags(' . l:bn . ')'
+    execute '  autocmd BufWritePost <buffer=' . l:bn . '> if &bufhidden !=# "delete" | call s:write_triggered_update_tags(' . l:bn . ') | endif'
     execute 'augroup end'

     " Miscellaneous commands.

The buftype is normal but it looks like bufhidden is set to delete, so there could be a check for that, like I did in my hacky work around.
When you edit the index version you can selectively choose changes that you would like to stage and staging the file is what stages those changes, to be committed. It is sort of like improved git add --patch inside vim.

Does the bug happen with arbitrary buffers with bufhidden=delete set? If I understand correctly what this option does, it might be the correct behavior for gutentags to ignore it anyway?

I wouldn't say Gutentags should generally ignore those, no... you could have bufhidden=delete on a buffer for some reason, and still edit it and go :w a few times, and you would expect the symbols to be indexed.
I wonder if the problem here is that autowriteall is writing the buffer on close, but bufhidden=delete is deleting it on close, and so it's trying to read a deleted buffer? I'll need to do more testing.

Ah right, yes.

Closing old issues, and can't repro this anymore.

I still get this bug, but I can't figure out how to trigger it. I use Vim every day, but it only occur a few times.
It disappears when I restart vim.


Timescale DB extension version

Hi, would it be possible to state the current version of the Timescale DB extension that's currently used in Azure PostgreSQL?

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

ID: 08d2543f-f47a-e9dc-1f80-1ac5ad7a71ad
Version Independent ID: cc5f4337-01f7-4774-6c26-fda65fadbdbf
Content: Use PostgreSQL extensions in Azure Database for PostgreSQL - Single Server
Content Source: articles/postgresql/concepts-extensions.md
Service: postgresql
GitHub Login: @rachel-msft
Microsoft Alias: raagyema

@j0h We are looking into this and will try to add this information.

@j0h The following document given the version for Azure Postgres as "Only TimescaleDB v1.1.1 is available on Azure Database for PostgreSQL"
https://docs.timescale.com/latest/getting-started/installation/azure/installation-windows-azure
Also you can use query "SELECT * FROM pg_available_extensions;" for finding the extension versions as the engine keeps on changing and the document can easily get outdated if not changed.
Hope this helps and get back to us if you have any other question.

@j0h Please let us know if there is anything else we can help you with or we will go ahead and close this thread.

Thanks for the response @NavtejSaini-MSFT. I did read somewhere that the above query is what you are expected to run when you want to find out extension versions, however, this means that I would at all times need to go through the process of setting up an instance to find this information out. In this instance, if I had done that, it would have been time wasted as version 1.1.1 of the TimescaleDB extension is outdated and our migration would fail due to functionality we are using in later versions of the extension.
Are there any plans to upgrade this extension and/or introduce it in pg11? If not, is the only alternative to run our own VM as I believe clients don't have the ability to upgrade extensions within Azure Postgres?

@j0h Thanks for the detailed feedback. We are checking this with our Product team and will get back to you once we have an answer regarding the same.

Version 1.3 will be available for Postgres 11. We expect it to rollout in September.

@rachel-msft Thanks for the help.
@j0h Hope this information has helped and you can schedule your migration accordingly. If there is no other question at this moment we will close this thread.

Thanks for the response @rachel-msft, looking forward to it. @NavtejSaini-MSFT, appreciate you getting in touch with the product team, can close this thread now.

Thanks for the response @rachel-msft, looking forward to it. @NavtejSaini-MSFT, appreciate you getting in touch with the product team, I'll close this thread now.


Adds Wemo event support - so wemo devices update HA more quickly

This PR adds support for WeMo event handling. It requires a new version of pywemo (https://github.com/balloob/pywemo/pulls)
I've left the should_poll true so that the worst case is this defaults to the current code. I suspect that some of this might not survive WeMo devices changing their port number etc. As I see issues I'll update the code.
There is one thing outstanding, I need to shutdown the wemo subscriptions on exit - but I'm not sure how best to call the close down code when HA exits. I'll add this is someone can point me in the right direction.

Add the following code to listen for shutdowns:
def stop_wemo(event):
    […]

hass.bus.listen_once(ha.EVENT_HOMEASSISTANT_STOP, stop_wemo)

@balloob My shutdown callback doesn't seem to be called, anything obvious wrong?

How do you close Home Assistant? It will fire a stop event and wait for it to stop when you are quiting HA using ctrl+c while running as a command line or when HA receives a sigterm signal.

The code looks good to me :dolphin: . Merge when you're ready.

I tried via sending a stop service from the gui. I also just tried with ctrl+C. This was the log (no sign of my trace)
^CINFO:homeassistant.core:Stopping
INFO:homeassistant.core:Bus:Handling <Event homeassistant_stop[L]>
INFO:homeassistant.components.recorder:Closing database

@balloob Should be sorted now. Don't have merge permissions here (just pywemo)


Multiline support for inline editing of last message + Complete editing by pressing Enter

[x] Add ability to insert line breaks like in message box
[x] Add ability insert line breaks to any location
[x] Line breaks only by Ctrl + Enter
[x] Enter for accept message editing
[ ] Write additional acceptance tests

Time spent:   4h 27m 18.09.2019
Time spent:   4h 24.09.2019
Time spent:   5h 25.09.2019

Need to fix problem with inserting line breaks at end of text

Need to add additional acceptance tests

Previous method for inserting \n at the end of text not working properly and after checking method used inside Slack client, decide to change content editable to use  for each line

Need to fix selection of child instead of ql-editor element for inserting partial elements before or after selected line
Need to change and fix scenarios

Need to fix other scenarios for editing


Camera Zoom acting differently on Mac and Windows

Godot version
4.0 alpha
System information
Windows,  MacOSX
Issue description
extends Camera2D
func zoom_to_player(player_position):
global_position = player_position
self.zoom = Vector2(1.6, 1.6) ### Running on Windows, it zooms in, while on MacOSX, it zooms out
set_process(false)
Steps to reproduce
No steps necessary.  Just run on Mac and Windows, to see the difference
Minimal reproduction project
No steps necessary.  Just run on Mac and Windows, to see the difference

4.0 alpha

4.0 has been in alpha for 6 months :) Please specify which alpha build you're using exactly (alpha 10, or specific commit you built yourself, etc.).

Camera2D zoom was inverted in https://github.com/godotengine/godot/pull/57392.

I think this was a misunderstanding from using two different versions of Godot before and after that change.


Incorrect copyright header

https://github.com/GoogleChromeLabs/pywebsocket3/blob/89c9228434100e4dabb19f61d0d4f55625940638/mod_pywebsocket/websocket_server.py#L1
I notice this copyright header has 202 as the year, this is likely a mistake.

Thanks!
@quasi-mod could you look at this when you have time?

Fixed on PR #5
Thank you!


yarn start and  documentation build are VERY slow

React InstantSearch has been moved here: https://github.com/algolia/react-instantsearch
This issue has either been rewritten or placed inside our backlog.


How to withdraw BTC to a BTC wallet address using this library

Is there a way? it will simply say "invalid address"

need an answer for this

You need to do what client app does. Actually it is just sending assets to some address, maybe you need to get this address from some service. The best way is spy which request classic client sends and do same thing.


CRI proxy

[x] Patch k8s to support 'mixed' runtime mode
[x] Basic docker-shim interception on kubeadm clusters
[x] ImageService proxying
[x] RuntimeService proxying with multiple runtime support based on annotations (test with cri-o)
[x] Fix proxy startup race (in 'mixed' mode, wait for the runtime to be able to handle Version() call successfully)
[x] Support virtlet
[x] Add proper credits pointing at the places in k8s source from where some  of the code was copied

After merging this PR and showcasing virtlet, we need to refactor 'mixed' mode and submit PR to upstream.
mixed container runtime k8s fork: https://github.com/ivan4th/kubernetes/tree/mixed-container-runtime-mode
Sample dump from CRI proxy (captures startup of kube-proxy pod on the node)
How to use with kubeadm-dind-cluster:

Build criproxy
Start the cluster with dind/dind-cluster.sh update && dind/dind-cluster.sh up
Prepare to change the runtime on a node by copying criproxy, killing kubelet and currently active docker containers and updating kubelet config:

docker cp criproxy kube-node-1:/usr/local/bin/
docker exec kube-node-1 systemctl stop kubelet
docker exec kube-node-1 bash -c 'docker ps -qa|xargs docker rm -fv'
echo -e "[Service]\nEnvironment='KUBELET_EXTRA_ARGS=--hostname-override=<IP_ADDRESS> --v=4 --experimental-cri --container-runtime=mixed --container-runtime-endpoint=/run/criproxy.sock --image-service-endpoint=/run/criproxy.sock'" | docker exec -i kube-node-1 /bin/bash -c 'cat >/etc/systemd/system/kubelet.service.d/20-hostname-override.conf'
docker exec kube-node-1 systemctl daemon-reload

Start criproxy:

docker exec -it kube-node-1 /usr/local/bin/criproxy -v 3 -alsologtostderr

In another terminal window start kubelet (this currently should be done quickly after starting criproxy as it probably may time out - need to check/fix):

docker exec kube-node-1 systemctl start kubelet

This change is

Reviewed 19 of 19 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

One minor thing - this cri proxy assumes that image service is accessible through same unix socket as runtime service. It's correct in our case, but we should probably add support to distinction of this if needed.
This is now good and should not be changed until we will be asked for this by other cri runtime implementer.

Yes, this likely needs to be done if/when proxy is spun off into a separate project.


broken images

any idea why all the photos for tomatoes are broken
https://openfarm.cc/en/crops/tomato
Looks like an AWS permission - i get 403 errors.
https://s3.amazonaws.com/openfarm-project/production/media/pictures/attachments/5d6063d2fd619c00041d4371.jpg?1566598095

I've uploaded photos of feijoa (there were none). They save into s3, but they have some permission error and
https://openfarm.cc/en/crops/feijoa
Saved image : https://s3.amazonaws.com/openfarm-project/production/media/pictures/attachments/5d7f034b5186a00004e90299.jpg?1568605002
Returns a http 403

Thanks for the bump on this @Br3nda, I've asked @RickCarlino to take a look :)

@roryaronson this is still broken. Can i have heroku access to look further into this error?

@Br3nda yes, thank you for offering to help. Can you email me<EMAIL_ADDRESS>with the email address you want to use to access Heroku with? I'll also need to add you to the AWS account I think. Rick is also looking back into this again today. We unfortunately got sidetracked the last month

I only uploaded one image  yet there are multiple broken images attached to the crop. Could be a offline or rake task that is running over and over.

Possible root cause: https://github.com/dtan4/terraforming/issues/235
Still investigating :hourglass_flowing_sand:


Support Hadoop-free 1.4

The scripts currently don't support the absence of a Hadoop version, though Flink 1.4 now includes a Hadoop-free release.
Update the scripts to build a Hadoop-free image, and ideally, change the Hadoop-ful images to use it as an upstream, only adding the additional jar to /opt/flink/lib.

added hadoopless here - https://github.com/docker-flink/docker-flink/pull/38

There's a bit of trickiness actually introducing the hadoopless images due to how we've done tagging thus far: currently, omitting the "hadoopX" part of the tag implies the latest hadoop variant (currently 2.8), but omitting that part is also how the upstream release archives indicate hadooplessness.
I propose that we introduce the hadoop-free images with Flink 1.5 (due to be released soon), making them the default (i.e. when a hadoop version is not specified), at the same time dropping the 1.3 images.

+1 @patricklucas It sounds easier to do at the moment of the switch to 1.5. And better not to change the expected labels of 1.4.

This is done, though I'm still not sure how to go about making the hadoop images downstream from the hadoop-less ones. I don't think this is a critical issue since it's mostly a disk space optimization.


Bump version in Docker images

Fix #3494

Jenkins, test this please

Jenkins CI test (for commit af553e945dc62a58640d8e9ea84cdf0dcbbd056c, target branch master) succeeded!


Thresholds are not working

The build succeeds even if the thresholds are crossed. For example, on enabling verification and having value of 1 for all the thresholds,

The build succeeds even if the alerts for medium risk and low risk is more than one.

Hi, a new version of the task (v2.0.5) is released now, Please check to see if this issue still exists. If so let me know here. Sorry for the delayed response.

@nikhiljainonline It works iwth v2.0.7 now.

I guess this can be closed?


Voice Kit v2, and  a "aplay: playback:2787" with the Mic...

I just installed the latest AIY SD card image on my v2 voice kit but the Mic fails with this error:
aplay: playback:2787; read error
I tried updating the image via apt update and upgrade but then it found no sound card at all, so I re-imaged with the 11-2018 image.
What is going on here and how can I fix this?

Can anyone please chime in here on this issue?
I am unable to proceed to use my Kit due to this.

There have been issues with running apt-get update and apt-get upgrade breaking the AIY voice kit functionality. It seems to be an issue with the fact that the latest kernels do not work well with the AIY hardware. But it doesn't look like there is recent official development going on that will fix it. You can try the solution here, otherwise re-installing the image and don't run update or upgrade

agreed with @rickyklu

@SalvorinFex Can you try to reflash your kit with https://github.com/google/aiyprojects-raspbian/releases/tag/v20191113 and see if the issue still persists ?

Please reopen this one if the issue still exists on the latest SD card image.


Need Logo [Urgent]

@suhailsinghbains @rbrishabh @chocos10 @nishadey logo dedo koi  -_-
@CuriousLearner need help for a logo for the website ;)

Done with #13


No output emitted even for correct files in Project References if one file has error

TypeScript Version:  3.9.2
Search Terms:
project references emit error force noEmitOnError
Code
tsconfig.json
{
  "files": [],
  "references": [
    { "path": "./project1" }
  ]
}

project1/tsconfig.json
{
  "noEmitOnError": false
}

project1/ok.ts
console.log('Hello world');

project1/fail.ts
const foo: string = 42;  // TS error
console.log(foo);

Expected behavior:
When I run tsc --build --force --verbose, I expect at least project1/ok.js to be output, because:

ok.ts compiles correctly
there are no dependencies mentioned in the Caveats section on Project References
I've specified "noEmitOnError": false explicitly in project1/tsconfig.json
I've passed the --force flag

Actual behavior:
Nothing is generated.
Reproduction repo:
https://github.com/dandv/ts-project-ref-bug

I'm not sure about this. We currently emit zero files on purpose, since:

There might be errors not associated with any file, so if we emitted files that don't have errors, we could end up putting the project in the "up to date" state despite it having errors
You'll have to recompile anyway, so...

Why do you want this to happen?

This is working as intended. tsc -build indirectly means --noEmitOnError. Having said that we not emit tsbuildinfo if there are errors so incremental builds should be speedy

Why do you want this to happen?

For my project, typescript errors are generally not a big deal. Usually red squiggles mean something needs to be casted to the correct type. I want to be able to test my code before I fix all type errors, so I have noEmitOnError: false. Nothing about this changes for me when I move to multiple projects and --build. I still have squiggles and I want to run my code.

This is working as intended. tsc -build indirectly means --noEmitOnError. Having said that we not emit tsbuildinfo if there are errors so incremental builds should be speedy

Does tsbuildinfo contain the error messages? I think that would allow failing the build even if the project is in the up-to-date state.

Why do you want this to happen?

We want to just run the plain JS to see if it works.
Sometimes there are type errors, but the code works perfectly fine, and sometimes we want TS to be out of the way and let us show that neat prototype we just made (the person viewing the prototype doesn't need to know there are type errors).
Boss: can you show the prototype in the meeting?
Dev: Yeah sure thing.
Dev(thinking): Oh crap, @types/node globals and other garbage getting in the way causing errors, I don't have time for this now. TypeScript won't let me build my code so I can just run it!! It's just JS anyways! Why is TS not letting me do what I need to do!

#32651 discusses tsc -b when there are errors


Test-Run Trigger (on branch: sim_0)

This is a mock pull request only intended only to trigger tests-runs on this branch (sim_0) using test-scripts on branch "add-test-workflow". See below for the test-run details. This PR will not be merged.

The GitHub Workflow action tests were triggered as expected. See test details by following the link https://github.com/ParticularMiner/string_grouper/actions/runs/743678469. In summary,
All Ubuntu-run tests succeeded on this branch (sim_0).
All Windows-run tests succeeded on this branch (sim_0).


Deployment Generation/Export utility

Fixes #485
TODO

[x] Add usage guide and documentation
[x] Error handling

Codecov Report

Merging #486 (9d15669) into main (2b71644) will decrease coverage by 0.22%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #486      +/-   ##
==========================================
- Coverage   37.41%   37.19%   -0.23%
==========================================
  Files          22       22
  Lines        9130     9141      +11
==========================================
- Hits         3416     3400      -16
- Misses       5313     5341      +28
+ Partials      401      400       -1

Impacted Files
Coverage Δ

KubeArmor/monitor/syscallParser.go
78.24% <0.00%> (-1.74%)
:arrow_down:

KubeArmor/feeder/feeder.go
44.55% <0.00%> (-1.02%)
:arrow_down:

KubeArmor/core/kubeUpdate.go
42.34% <0.00%> (-0.17%)
:arrow_down:

KubeArmor/feeder/policyMatcher.go
39.37% <0.00%> (+0.14%)
:arrow_up:

Continue to review full report at Codecov.

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

@daemon1024, once you make the changes for resource limits and convert it to normal PR, I could test this again and we can merge it. Sounds ok? Thanks

Tested on vagrant vm with ubuntu 18.04


KAFKA-16162: resend broker registration on metadata update to IBP 3.7-IV2

We update metadata update handler to resend broker registration when metadata has been updated to >= 3.7-IV2 so that the controller becomes aware of the log directories in the broker.
We also update DirectoryId::isOnline to return true on an empty list of log directories while the controller awaits broker registration.

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

CC: @showuon @OmniaGM @cmccabe @pprovenzano

Looks straightforward fix! however the pipeline is failing with
 > Task :core:compileTestScala
[2024-01-26T15:19:03.811Z] [Error] /home/jenkins/workspace/Kafka_kafka-pr_PR-15270/core/src/test/scala/unit/kafka/server/BrokerLifecycleManagerTest.scala:278:21: Invalid literal number
[2024-01-26T15:19:03.811Z] [Error] /home/jenkins/workspace/Kafka_kafka-pr_PR-15270/core/src/test/scala/unit/kafka/server/BrokerLifecycleManagerTest.scala:285:3: ')' expected but '}' found.
[2024-01-26T15:19:03.811Z] two errors found

Can you fix these please. Assuming these are fixed can @rondagostino, @showuon and @cmccabe one of you have a look into this please?

Thanks! Turns out _ in numerals doesn't work in Scala 2.12. Should be fixed with 747cfad

Thanks @gaurav-narula . The overall approach looks good to me.
There is a consistent test failure here:
Gradle Test Run :core:test > Gradle Test Executor 2 > BrokerMetadataPublisherTest > testFindStrayReplicas() FAILED
    org.mockito.exceptions.misusing.UnfinishedVerificationException:
    Missing method call for verify(mock) here:
    -> at kafka.server.metadata.BrokerMetadataPublisherTest.testMetadataVersionUpdateToIBP_3_7_IV2OrAboveTriggersBrokerReRegistration(BrokerMetadataPublisherTest.scala:402)

    Example of correct verification:
        verify(mock).doSomething()

    Also, this error might show up because you verify either of: final/private/equals()/hashCode() methods.
    Those methods *cannot* be stubbed/verified.
    Mocking methods declared on non-public parent classes is not supported.
        at app//kafka.server.metadata.BrokerMetadataPublisherTest.mockLog(BrokerMetadataPublisherTest.scala:153)
        at app//kafka.server.metadata.BrokerMetadataPublisherTest.testFindStrayReplicas(BrokerMetadataPublisherTest.scala:100)```

I expect the test needs to be updated to fix the mock.

Thanks, all. Committed.