Platformatic Composer: Fails to start with unknown dependency in services json config

When using Platformatic composer as standalone or as part of Platformatic runtime only, the composer fails to start. The following process to create the error.
Setup of composer only
pnpm create platformatic@latest

Lets start by creating a new project.
? Which kind of project do you want to create? Composer
? Where would you like to create your project? composer-test-demo
? What port do you want to use? 3042
? Do you want to run pnpm install? yes
[06:42:25] INFO: Configuration file platformatic.composer.json successfully created.
[06:42:25] INFO: Environment file .env successfully created.
✔ ...done!
? Do you want to create the github action to deploy this application to Platformatic Cloud dynamic workspace? no
? Do you want to create the github action to deploy this application to Platformatic Cloud static workspace? no

All done! Please open the project directory and check the README.

In the platformatic.composer.json file -
{
  "$schema": "https://platformatic.dev/schemas/v0.34.0/composer",
  "server": {
    "hostname": "<IP_ADDRESS>",
    "port": "3024",
    "logger": {
      "level": "info"
    }
  },
  "composer": {
    "services": [
      {
        "id": "example",
        "origin": "https://example.com",
        "openapi": {
          "url": "/documentation/json"
        }
      }
    ],
    "refreshTimeout": 1000
  },
  "watch": true
}

The package.json file -
{
  "scripts": {
    "start": "platformatic start"
  },
  "devDependencies": {
    "fastify": "^4.21.0"
  },
  "dependencies": {
    "platformatic": "^0.34.0"
  },
  "engines": {
    "node": "^18.8.0"
  }
}

Start composer
pnpm start

This is the following error:
> platformatic start

service 'composer-test-demo' has unknown dependency: 'example'. Did you mean 'composer-test-demo'?
 ELIFECYCLE  Command failed with exit code 1.

MacOs: 13.5
Editor: VsCode
Platformatic: 0.34.0

@mcollina UPDATE: This is caused when creating only a compose. The package.json script that is created has the default platformatic start, but instead should have platformatric composer start. I'm busy with a fix to accommodate this. Will revert when tested.

The command is actually correct, platformatic start should start every project.

The command is actually correct, platformatic start should start every project.

I know, you have said that before.... When using composer as part of runtime, then no package.json is created for composer. Yet when you create only a composer the package.json file is created. Its then running platformatic start that the project won't start. So what do you think?

@mcollina  When using a standard deploy for a Platformatic DB, Service or Composer  project.

no GitHub Actions
no additional packages

pnpm platformatic deploy \
--type static \
--workspace-id <MY-WORKSPACE-ID> \
--workspace-key <MY-WORKSPACE-KEY>

[02:26:22] WARN: Move platformatic dependency to devDependencies to speed up deployment
[02:26:22] INFO: Found Platformatic config file: platformatic.db.json
[02:26:22] INFO: No typescript configuration file was found, skipping compilation.
[02:26:24] INFO: Project has been successfully archived
[02:26:27] INFO: Uploading bundle (211 MB) to the cloud...
[02:26:27] ERROR: Failed to upload code archive: 413

I'm assuming the failed to upload code archive: 413 is a fly [Status Code 413 Payload Too Large] error.


Add support for stable-aarch64-unknown-linux-gnu

Is your feature request related to a problem or challenge? Please describe what you are trying to do.
I would like to be able to use DataFusion on a Raspberry Pi running Ubuntu 20.04.3 but it does not compile.
$ cargo test
   Compiling datafusion v6.0.0 (/home/ubuntu/arrow-datafusion/datafusion)
error[E0368]: binary assignment operation `+=` cannot be applied to type `OrderedFloat<f64>`
   --> datafusion/src/physical_plan/tdigest/mod.rs:329:13
    |
329 |             weight_so_far += next.weight();
    |             -------------^^^^^^^^^^^^^^^^^
    |             |
    |             cannot use `+=` on type `OrderedFloat<f64>`

Describe the solution you'd like
I would like the code to compile.
Describe alternatives you've considered
It looks like I can use cross to cross-compile from my desktop to this architecture:
cross build --release --target aarch64-unknown-linux-gnu

Additional context
$ cat /etc/issue
Ubuntu 20.04.3 LTS \n \l

$ uname -a
Linux pi1 5.4.0-1050-raspi #56-Ubuntu SMP PREEMPT Thu Jan 13 13:09:35 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux

$ rustup update
info: syncing channel updates for 'stable-aarch64-unknown-linux-gnu'
info: checking for self-updates

  stable-aarch64-unknown-linux-gnu unchanged - rustc 1.58.1 (db9d1b20b 2022-01-20)

I was able to get this to work on a different Raspberry Pi running the same OS. The only difference was 8 GB vs 4 GB memory. This doesn't make much sense to me but I am closing this issue.


Error: Value type of struct has infinite size. Issue building models with amplify codegen models

Describe the bug
This ticket is to track the progress of this error, I'm having the same exact error, that was from 2021, 2021... almost 3 years...
Here's my error:

Here's the schema:
type Wallet @model @auth(rules: [
  { allow: private, operations: [read] },
  { allow: owner }
]) {
  id: ID!
  walletName: String!
  walletAddress: String!
  verifiedOwnership: Boolean! # If a wallet is not verified will be considered in the watchlist
  userChains: [UserChain]! @hasMany
  analytics: WalletAnalytics @hasOne
  portfolio: Portfolio @belongsTo
}

type SharedWallet @model @auth(rules: [
  { allow: private, operations: [read] },
  { allow: owner }
]) {
  id: ID!
  wallet: Wallet! @hasOne
  portfolio: Portfolio @belongsTo
}

Can we please add support to fix this kind of issues
Amplify Categories
API, DataStore
Amplify Framework Version
2.8.0
Dependency manager
Swift PM
Swift version
5.8
CLI version
11.0.2
Xcode version
14.3 (14E222b)
Is this a regression?
Yes
Regression additional context
No response
Device
any
iOS Version
iOS 16

Also can someone advice on how to fix it for now (but leave this ticket open to track the progress on the real fix)?

Let me post the entire schema because this is dumb... there should be some better validation before letting anyone push the schema. Here's the full schema:
type User @model @auth(rules: [{ allow: owner }, { allow: private, operations: [read] }]) {
  id: ID!
  age: Int
  email: String
  name: String
  createdAt: String
  profileImage: String
  socialMedia: SocialMedia @hasOne
  portfolios: [Portfolio] @hasMany
  following: [UserFollower] @hasMany
  followers: [UserFollower] @hasMany
}

type SocialMedia @model @auth(rules: [
  { allow: private, operations: [read] },
  { allow: owner }
]) {
  id: ID!
  twitter: String
  facebook: String
  instagram: String
  linkedIn: String
  user: User @belongsTo
}

type UserFollower @model @auth(rules: [{allow: private, operations: [read]}]) {
  id: ID!
  user: User @belongsTo
  follower: User @belongsTo
}

type Portfolio @model @auth(rules: [
  { allow: private, operations: [read] },
  { allow: owner }
]) {
  id: ID!
  name: String
  description: String
  user: User @belongsTo
  wallets: [Wallet] @hasMany
  sharedWallets: [Wallet] @hasMany
  sharedPortfolios: [SharedPortfolio] @hasMany
  portfolioAnalytics: PortfolioAnalytics @hasOne
}

type Wallet @model @auth(rules: [
  { allow: private, operations: [read] },
  { allow: owner }
]) {
  id: ID!
  walletName: String!
  walletAddress: String!
  verifiedOwnership: Boolean! # If a wallet is not verified will be considered in the watchlist
  userChains: [UserChain]! @hasMany
  walletAnalytics: WalletAnalytics @hasOne
  portfolio: Portfolio @belongsTo
}

# Wallet analytics specific to the user
type WalletAnalytics @model @auth(rules: [{ allow: owner }]) {
  id: ID!
  totalValue: Float
  totalTokenCount: Int
  wallet: Wallet @belongsTo
}

# Portfolio analytics specific to the user
type PortfolioAnalytics @model @auth(rules: [{ allow: owner }]) {
  id: ID!
  totalValue: Float
  totalChains: Int
  totalTokenCount: Int
  portfolio: Portfolio @belongsTo
}

# The supported blockchains that are tracked by the user
type UserChain @model @auth(rules: [
  { allow: private, operations: [read] },
  { allow: owner }
]) {
  id: ID!
  chainId: Int!
  wallet: Wallet @belongsTo
}

type SharedPortfolio @model @auth(rules: [
  { allow: private, operations: [read] },
  { allow: owner }
]) {
  id: ID!
  showcase: Boolean!
  portfolio: Portfolio @belongsTo
}

# Be careful to not store any sensitive information here. This is a public model that is used to store the latest version of the app
type iOSAppMetadata @model @auth(rules: [
      { allow: public, provider: iam, operations: [read] },
      { allow: groups, groups: ["Admin"], operations: [update] }
    ]
  )
{
  id: ID!
  latestMajorVersion: String @default(value: "3.11.0")
  optionalQualityUpdate: String @default(value: "3.15.0")
  maintenanceMode: Boolean
}

and here are the errors I'm getting:

Hi @afern247 Thank you for reaching us. Did you get a chance to try out amplify codegen models using the latest Amlify CLI version as mentioned here - https://github.com/aws-amplify/amplify-swift/issues/1541#issuecomment-1435043402

Please use the latest version of the amplify CLI and review or make updates to cli.json (in the amplify folder) to ensure you have the following settings:
"transformerversion":2
"respectprimarykeyattributesonconnectionfield": true
"generatemodelsforlazyloadandcustomselectionset": true

I tried the same with the provided schema, and was able to build the project without any errors.


chore(main): release 0.7.1

:robot: I have created a release beep boop
0.7.1 (2022-11-05)
Miscellaneous

change imports, remove unused variables (c94683d)
move to vitest, chalk; remove babel, colorette, jest; es2022 (3ff18da)
remove json imports, load json using fs-extra (d73e09f)
use tsup instead of tsc, export to esm, add .d.ts to package (e475f45)

Chores

set node minimal version to v16.13 (a13c29c)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/smarlhens/npm-check-engines/releases/tag/v0.7.1 :sunflower:


Making Space Agency template fully responsive

Issue Type:

[x] Bug Report
[ ] Feature Request
[ ] Documentaion

Describe the bug
There is a folder named Space Agency template in the Cool-Front-End-Templates repo. Make that template fully responsive.
Screenshots

Can you assign me this task?

Complete this issue @Sourajita21 asap!

Okay sir.
On Tue, 5 Apr, 2022, 12:42 pm Kumari Astha Rani, @.***>
wrote:

Complete this issue @Sourajita21 https://github.com/Sourajita21 asap!
—
Reply to this email directly, view it on GitHub
https://github.com/arpit456jain/Cool-Front-End-Templates/issues/520#issuecomment-1088345144,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AUJT3QGBQIVQXJ7HH2AUQITVDPRWTANCNFSM5R4ABZCA
.
You are receiving this because you were mentioned.Message ID:
@.***>

@Sourajita21

@Sourajita21 ?

Yeah unfortunately I can't work in this issue.
On Sun, 24 Apr, 2022, 1:30 am Kumari Astha Rani, @.***>
wrote:

@Sourajita21 https://github.com/Sourajita21 ?
—
Reply to this email directly, view it on GitHub
https://github.com/arpit456jain/Cool-Front-End-Templates/issues/520#issuecomment-1107640400,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AUJT3QF2HJAGF3YQXA2OGZLVGRJELANCNFSM5R4ABZCA
.
You are receiving this because you were mentioned.Message ID:
@.***>


feature support debug point used in debug code

Proposed changes
Debug point is a code switch used for debug development.When a debug point is opened, the corresponding code can be executed.
Both fe and be support debug points.
For example， we want to debug publish version with TOO_MANY_VERSIONS error.  Then we can add debug code in BE:
Status   StorageEngine::do_publish_version() {
            .....

           //"test_too_many_versions" is a debug point,
           // if it's enabled,  then it will return error TOO_MANY_VERSIONS
          DBUG_EXECUTE_IF("test_too_many_versions",   {  return Err(TOO_MANY_VERSIONS); });

          ......
}

for fe, no macro DBUG_EXECUTE_IF,   but just use function DebugPointUtil.isEnable(debug_point) to test if enable a debug point;
To enable a debug point,  we need two steps:

start fe or be  with config.enable_debug_points = true;
post a http request  /api/debug_point/add/{debug_point_name} to the fe or be;

Http API:

add a debug point:   post /api/debug_point/add/{debug_point_name}[?execute=times&timeout=seconds]. execute is optional,  indicates the maximum number of times the debug point can take effect. timeout is optional, indicates the maximum number of seconds the debug point takes effect;
remove a debug point: post /api/debug_point/remove/{debug_point_name};
clear all the debug points: post /api/debug_point/clear.


Can we add gif as watermark

Can we add gif as watermark
there is a BitmapOverlayFilter.java class however it seems we can add only images , how can we add an animated gif as watermark

There is FrameSequenceAnimationOverlayFilter that does that. You will have to implement AnimationFrameProvider, which should be pretty straightforward. There should be an example in demo app.


Modal does not provide backdrop w/ bootstrap 3.3.2

Looks like bootstrap 3.3.2 does not have the bottom 0 anymore on modal-backdrop class
.modal-backdrop {
  bottom: 0;
}

This means that the modal dialog does not calc the correct height for the backdrop fade.
plunker here:
http://plnkr.co/edit/5vPyWJvl1Xzs4bYAAebC?p=preview

Dup of #3184? Discussion there indicates that this has been addressed in Bootstrap for a future release. Temporary fix is to override the Bootstrap styling for the backdrop.
.modal-backdrop {
    bottom: 0px;
    position: fixed;
}

This appears to be a Bootstrap issue with a simple workaround - feel free to reopen this issue with another comment if you believe a fix should be in UI Bootstrap.

As pointed out in:
https://github.com/angular-ui/bootstrap/issues/2830#issuecomment-82261304
A new bootstrap version is out: https://github.com/twbs/bootstrap/releases/tag/v3.3.4
which solves the issue, see https://github.com/twbs/bootstrap/blob/f5beebe726aa8c1810015d8c62931f4559b49664/less/modals.less#L65

i've retested this over the GlobaLeaks project and i confirm and the issue is solved in bootstrap 3.3.4


Why are PPL so low on PTB?

Hello
Many thanks for your work, it's great to (finally) see results reported on openly available LLMs 😊
However, I was surprised when I saw perplexities on PTB for OPT and BLOOM models: 10.33 and 13.63 respectively.
Indeed, GPT-3's paper reports a PPL of 20.50 on such dataset and I was wondering whether you had any explanation for this (nearly 2x) difference?
Thanks!

Hi,
our perplexity calculation is based on this HuggingFace link and works as follows: concatenate all dataset samples with basic separators, then split the resulting string into non-overlapping segments of 2048 tokens (the maximum sequence length of both OPT and BLOOM) and evaluate the average causal-LM loss on those segments; the exponentiated version of this result is the perplexity. We believe this is pretty standard.
For PTB, we use this version of the dataset and proceed exactly as explained above, without any extra preprocessing. One partial explanation for our lower PPL numbers may be the fact that we insert separators (following exactly the HuggingFace link mentioned above) in between samples; for most datasets like WikiText the impact of this is very minor, but since PTB is split per-sentence without punctuation, inserting separators between sentences appears to help models significantly. After disabling this by changing "\n\n" to " " at:
https://github.com/IST-DASLab/gptq/blob/9232a476641b1848cf720dd15bd0e616cd48702d/datautils.py#L40
the PPL for FP16 OPT-175B increases from 10.33 to 13.04. Beyond that, we are not really sure what differences there might be or if OPT is just more accurate on this dataset (on a related note, the ZeroQuant paper reports 20.47 PPL on PTB for a 6B model). If you are aware of any PTB evaluation details or a reliable reference implementation, we would be happy to learn about them.
Lastly, we would like to emphasize that the focus of our work is on the accuracy drop relative to the FP16 version (rather than absolute PPL values) and that we always evaluate all FP16 and quantized models using exactly the same code (in this repository) to ensure a fair comparison.


[az lab vm create] Possible values for --disk-type

> --disk-type
> Storage type to use for virtual machine.
Could we add what the possible values are, please?
Thanks!
--Neno

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

ID: ef5457fd-c38a-6fb8-1df4-24a15e6ba787
Version Independent ID: ef65acdc-464a-08c7-b013-d9e3f1560977
Content: az lab vm
Content Source: src/azure-cli/azure/cli/command_modules/lab/_help.py
Service: devtest-lab
GitHub Login: @rloutlaw
Microsoft Alias: routlaw

Since I was unable to find the solution, even in this GitHub issue;
The possible values I know of are: 'Standard' is for HDD and 'StandardSSD'.

Since I was unable to find the solution, even in this GitHub issue; The possible values I know of are: 'Standard' is for HDD and 'StandardSSD'.

The command failed with an unexpected error. Here is the traceback:
Expect <class 'bool'>, got Standard (<class 'str'>)
Traceback (most recent call last):
  File "/usr/lib64/az/lib/python3.9/site-packages/knack/cli.py", line 233, in invoke
    cmd_result = self.invocation.execute(args)
  File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/core/commands/__init__.py", line 666, in execute
    raise ex
  File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/core/commands/__init__.py", line 733, in _run_jobs_serially
    results.append(self._run_job(expanded_arg, cmd_copy))
  File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/core/commands/__init__.py", line 703, in _run_job
    result = cmd_copy(params)
  File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/core/aaz/_command.py", line 155, in __call__
    return self._handler(*args, **kwargs)
  File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/command_modules/lab/aaz/latest/lab/_create_environment.py", line 49, in _handler
    super()._handler(command_args)
  File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/core/aaz/_command.py", line 159, in _handler
    self.ctx = AAZCommandCtx(
  File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/core/aaz/_command_ctx.py", line 30, in __init__
    cmd_arg.apply(self.args, dest)
  File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/core/aaz/_arg_action.py", line 58, in apply
    self._assign_data(args, data, dest, *keys)
  File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/core/aaz/_arg_action.py", line 73, in _assign_data
    arg[key] = data
  File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/core/aaz/_field_value.py", line 76, in __setitem__
    self._data[name] = attr_schema.process_data(data, key=name)
  File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/core/aaz/_field_type.py", line 48, in process_data
    raise AAZInvalidValueError('Expect {}, got {} ({})'.format(self.DataType, data, type(data)))
azure.cli.core.aaz.exceptions.AAZInvalidValueError: Expect <class 'bool'>, got Standard (<class 'str'>)

With az version:
{
  "azure-cli": "2.65.0",
  "azure-cli-core": "2.65.0",
  "azure-cli-telemetry": "1.1.0",
  "extensions": {
    "ai-examples": "0.2.5",
    "ml": "2.30.1",
    "ssh": "2.0.5"
  }
}


Creating a new data object that the url is passed to

Anyone who has done something like that?

@adtoba Can you explain what you are trying to accomplish?. The title does not tell us anything.

I'm trying to use the library for a download activity in my browser app.
But then, I need to pass the unique URL gotten from the download manager
from my webview Into the model for my fetch download.. It should get the
new URL, pass it into the data then add it to a list in download activity
On Sat, Sep 29, 2018, 2:05 PM Tonyo Francis<EMAIL_ADDRESS>wrote:

@adtoba https://github.com/adtoba Can you explain what you are trying
to accomplish?. The title does not tell us anything.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tonyofrancis/Fetch/issues/249#issuecomment-425643878,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AXHPfzy1KV5BKTknTbyn3eYknujDHFItks5uf3AFgaJpZM4W9ftm
.

So just so I understand. You are using a webview. If the user downloads a file the file goes to the default download manager. What you want to achieve is get the url for that download and have Fetch download the request instead of the default download manager. Sounds correct?

Yes. Totally correct!  Can you do that for me?
On Sun, Sep 30, 2018, 4:58 PM Tonyo Francis<EMAIL_ADDRESS>wrote:

So just so I understand. You are using a webview. If the user downloads a
file the file goes to the default download manager. What you want to
achieve is get the url for that download and have Fetch download the
request instead of the default download manager. Sounds correct?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tonyofrancis/Fetch/issues/249#issuecomment-425730995,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AXHPf7zMED_fTS5a6Zjke896dFOO8Ep5ks5ugOoygaJpZM4W9ftm
.

@adtoba I cannot do that for you but point you to resources that will help. To get the download information from the download manager you can follow this guide: https://www.androidtutorialpoint.com/networking/android-download-manager-tutorial-download-file-using-download-manager-internet/
Also see the Fetch Sample app.


Bot is not responding

Bot is not responding at all
Ps: I followed usage instructions

Bot is not responding at all Ps: I followed usage instructions

same...

node deploy-commands.js

how to get the guildId bro?


Jewel Application - percentWidth & percentHeight issue

Hi all,
I have been working with the Jewel Application control.
I have noticed something curious, and it is that when the child (in my case a ResponseView control) has the percentWidth or percentHeight property assigned, we assign to the application control a fixed width and height corresponding to the size of the child ...
This is the code snippet I'm talking about
https://github.com/apache/royale-asjs/blob/develop/frameworks/projects/Jewel/src/main/royale/org/apache/royale/jewel/Application.as

Here is an example of the code transpiled to HTML;

The problem is that that size, we are passing through style in a fixed way, and it is never updated.
I don't know if this is being done for any particular reason... i think it could be removed.
thx in advance!

Hi,
as stated in the docs [1], ResponsiveView should not add width and height since is for responsive applications and the view itself define itself to have 100% on both properties.
In exchange, View (see [2]) is a normal view that can define width and height (and use BrowserResizeApplicationListener bead to manage resizing if needed) while ResponsiveView does all of this without the need to define a listener for window's resize event since its reason is to respond to browser window resizing.
TDJ uses ResponsiveView that way:
<j:initialView>
	<local:MainContent/>
</j:initialView>

where MainContent is a ResponsiveView that doesn't specify width or height at all.
HTH.
Carlos
[1] https://apache.github.io/royale-docs/component-sets/jewel/responsiveview
[2] https://apache.github.io/royale-docs/component-sets/jewel/view

However, in the ResponsiveView construct, the percentage of width and height is set to 100 by default
https://github.com/apache/royale-asjs/blob/3fb70737d6f8a7f3b06e8b372babef30e59ab2ff/frameworks/projects/Jewel/src/main/royale/org/apache/royale/jewel/ResponsiveView.as

I just compiled the TDJ, and the problem reproduces:
When you start the application, a fixed size is added to the style.

If we resize the application, the size does not change.

Ops, thanks for showing that. That line was for testing some issues and I thought I delete it before pushing the last refactor, but seems it was left by mistake. Sorry for the trouble, going to fix now. Thanks!


Whitespace around operation

I've encountered an issue with oelint-adv that an assignment with extra whitespace is not parsed correctly.
The recipe like:
VAR1 = "A"
VAR1  += "B"
VAR2  += "C"

is reported as false positive in the second line. I assume that has something to do with this regexp

I'd assume the fix might be:
-   __regex_var = r"^(?P<varname>([A-Z0-9a-z_.-]|\$|\{|\}|:)+?)(?P<varop>(\s|\t)*(\+|\?|\:|\.)*=(\+|\.)*(\s|\t)*)(?P<varval>.*)"
+   __regex_var = r"^(?P<varname>([A-Z0-9a-z_.-]|\$|\{|\}|:)+?)(?P<varop>(\s|\t)(\+|\?|\:|\.)*=(\+|\.)*(\s|\t))(?P<varval>.*)"

What should be the way to integrate it into the PR test pipeline?

Hmmm, how is that wrong?
With the original regex all of the following is parsed correctly
VAR1 = "A"
VAR1  += "B"
VAR2  += "C"
VAR2+= "C"

while with your patch only the first line will be caught, so I honestly think it makes it much worse.
I'm having a hard time to understand how VAR2<space><space>+= "C" is not wrong, the assignment needs to be VAR2<space>+= "C", a quick test returns
test.bb:2:warning:oelint.vars.spacesassignment:Suggest spaces around assignment. E.g. 'FOO = "BAR"'
test.bb:3:warning:oelint.vars.spacesassignment:Suggest spaces around assignment. E.g. 'FOO = "BAR"

which is the expected result IMO.
Could you please elaborate what you think the false positive is

Yes, it is parsed correctly, but VarOp is going to be  += in that case, that returns "error:oelint.var.override:Variable 'A' is set by 'recipe.bb'" for the first  <space><space>+= line. I agree that it's a strange formatting, but bitbake is OKish with that. Does it make sense? :)
You can reproduce it with this test case

ahhh now I see what the false positive is, so it ain't about the parser but the particular rule - will try to fix that in one of the next release (and also moving this ticket to the linter, as it's not an issue of the parser)


AssertionError occurs for some reductions when CUB is enabled

I get some test suite failures in cupyimg when CUPY_ACCELERATORS="cub,cutensor" environment variable is set.

Conditions (you can just paste the output of python -c 'import cupy; cupy.show_config()')
CuPy Version          : 8.0.0b5
CUDA Root             : /usr/local/cuda-10.2
CUDA Build Version    : 10020
CUDA Driver Version   : 10020
CUDA Runtime Version  : 10020
cuBLAS Version        : 10202
cuFFT Version         : 10102
cuRAND Version        : 10102
cuSOLVER Version      : (10, 3, 0)
cuSPARSE Version      : 10301
NVRTC Version         : (10, 2)
Thrust Version        : 100907
CUB Build Version     : 100800
cuDNN Build Version   : 7605
cuDNN Version         : 7605
NCCL Build Version    : 2604
NCCL Runtime Version  : 2604
cuTENSOR Version      : 10001

Code to reproduce

import cupy as cp
x = cp.arange(2*4*3).reshape((2, 4, 3), order='F')
x.max(-1)  # or x.max(1), but not for x.max(0) which is the contiguous axis

This gives the correct result, but prints:
AssertionError

Exception ignored in: 'cupy.cuda.cub._preprocess_array'
AssertionError

Error messages, stack traces, or logs

cc @leofang: I haven't looked into it yet, but thought you may know offhand what the issue is?

This looks suspicious to me...I need to look into why I added it in the first place.
https://github.com/cupy/cupy/blob/97573d737beefb7a9ae9f81c294a005ed475bf4f/cupy/cuda/cub.pyx#L106-L107

#3562 is to blame 😅


Allow first user creation from only a specified ip address

It would be really nice to be able to specify a shared secret (passed via query string) and/or limit the first user creation to a specific IP address. I had a cluster pwnd because I wasn't fast enough and didn't realize what was going on until services started falling over.
What kind of request is this (question/bug/enhancement/feature request):
bug? feature?
Steps to reproduce (least amount of steps as possible):

Install Rancher to a kubernetes cluster.
Have a "friend" see your new DNS entry and be curious.
Your friend goes and creates a password you don't know while you wait for it to come up.


Embedd with downloadables

Ui adjustment @fredrikved

[ ] Visible download bar without scrolling in player if episode is downloadable

That's defined in the iframe element. We can't control the size of the embed from our side :/


added sidecar.istio.io/rewriteAppProbers annotation

For #13074

register sidecar.istio.io/rewriteAppProbers annotation
include this annotation upon checking whether should rewrite app probers (previously we checked only RewriteAppHTTPProbe flag in SidecarInjectionSpec)
tests added

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: arief-hidayat
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: hzxuzhonghu
If they are not already assigned, you can assign the PR to them by writing /assign @hzxuzhonghu in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

pilot/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Hi @arief-hidayat. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

I signed it!

/assign incfly

/unassign incfly
/cc @incfly

add pilot owners.

Another thing if you are interested, is to add this as a negative test into our e2e testing framework.
https://github.com/istio/istio/blob/master/tests/integration/security/healthcheck/mtls_healthcheck_test.go#L82
Basically, using annotations to turn off the feature and then verifies that aps.GetAppOrFail("healthcheck-disabled-via-annotations", t) will fail.
Purely optional, I can also do it later.

Hi @incfly
Thank you for the review comments. I have made corresponding changes except for e2e test framework. I am going to get familiarised and add the test later.
Thanks

/ok-to-test

@arief-hidayat: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-simpleTests.sh
0dc2bcdadc171580fa79955710617f757407cbc9
link
/test e2e-simpleTests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Overall, the code part lgtm.

@arief-hidayat: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-simpleTests.sh
0dc2bcdadc171580fa79955710617f757407cbc9
link
/test e2e-simpleTests

prow/istio-unit-tests.sh
0dc2bcdadc171580fa79955710617f757407cbc9
link
/test istio-unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@arief-hidayat: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
0dc2bcdadc171580fa79955710617f757407cbc9
link
/test istio-unit-tests

prow/istio-pilot-multicluster-e2e.sh
0dc2bcdadc171580fa79955710617f757407cbc9
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@arief-hidayat: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
0dc2bcdadc171580fa79955710617f757407cbc9
link
/test istio-unit-tests

prow/istio-pilot-multicluster-e2e.sh
0dc2bcdadc171580fa79955710617f757407cbc9
link
/test istio-pilot-multicluster-e2e

prow/istio-integ-k8s-tests.sh
0dc2bcdadc171580fa79955710617f757407cbc9
link
/test istio-integ-k8s-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@arief-hidayat: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-k8s-tests.sh
0dc2bcdadc171580fa79955710617f757407cbc9
link
/test istio-integ-k8s-tests

prow/istio-pilot-multicluster-e2e.sh
e028639e24f564601083c10718a5c32eab531955
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@arief-hidayat: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
e028639e24f564601083c10718a5c32eab531955
link
/test istio-pilot-multicluster-e2e

prow/istio-integ-k8s-tests.sh
e028639e24f564601083c10718a5c32eab531955
link
/test istio-integ-k8s-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/lgtm

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: arief-hidayat, hzxuzhonghu
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

pilot/OWNERS [hzxuzhonghu]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


fix error after logout and try to get status or to connect again

after logout and try to get status or connect agian

this pr fix this issue

same error

Already solved.


Connection of wallet-api with non live apps

Library name
No response
Describe your feature request
I see wallet API does provide minimal but good use cases. My question is - Can we send transport extracted from @ledgerhq/react-native-hw-transport-ble and use that to initialise the Wallet-API so I can use the useSignMessage hook?

This issue has been preview on the Pull Requests. To resolve,
Contact the dAppNode page to initiate a chat with the live agent on the chat button to get more information about your request via dAppNode
@gvash
Regards.


[remote-ast] Disable non-deterministic test failure.

This is failing for me ~10% of the time. It is resulting in spurious PR testing
failures.
SR-9908

Thanks Mishal!


Add ObjectExtractor tests

Refactor ObjectExtractor creation and initialization, remove unused getters.
Add more tests
Fix extract wrong page number.

@jazzido I'm sorry, I've got missed of what is happening with Icdar tests so I started to continue adding more tests in tabula. I'm running a coverage tool to get the % of coverage tested in each class, ObjectExtract class has 86.8% now. Also I made some refactors in the class and I fixed a little bug about extracting an out of bound page number.
After Matt can push his changes I could help making the icdar tests pass.

Thanks, Meli!


feat: use codegen client with service integrations

Replaces the old client.

Tests https://github.com/aiven/terraform-provider-aiven/actions/runs/10738790211


Python code is not rendered correctly

I am testing the demo of the Wiki and I have found an issue with pages containing Python code.
Text of the page
```
for i in range(3):
    print i
```

Result
``` for i in range(3):

System Message: WARNING/2 (<string> line 1) id2
Inline literal start-string without end-string.

System Message: ERROR/3 (<string> line 3)
Unexpected indentation.

print i
System Message: WARNING/2 (<string> line 4)
Block quote ends without a blank line; unexpected unindent.

```

System Message: WARNING/2 (<string> line 4) id4
Inline literal start-string without end-string.

System Message: WARNING/2 (<string> line 4) id6
Inline interpreted text or phrase reference start-string without end-string.

URL of the page http://waliki.pythonanywhere.com/newpage3/edit
See screenshot:

Hi @Muffo. I've tried the page you linked and I can't reproduce it, both in rst and md formats. The problem looks like the editor never knew you changed the default format (rst) to markdown, and it's rendering using the wrong processor for your markup.  this is done via javascript, when you click in the dropdown.
which browser do you use? do you have javascript disabled, may be? Does it also happen to you editing a page that already exists?

I am using the latest stable version of Chrome on Windows and after reloading the page it is working OK
I'll give you more details about what I did originally:

Open the URL of a non existing page
Create the page and add the markdown code
Click on Preview using restructured text (do not selecting "Markdown")
The error is displayed
Go back to the Editor view
Select Markdown and click again on Preview
The error is still there

Hope this helps

ok, great report, I can reproduce it now . I'll see asap. thanks

There's no hurry for the fix :)
I am glad this was useful!


DataTriggerBehavior fires only first time

The request is that the row of my ListView blinks when the property SelectedItem of the ViewModel raises change.
This is my code, the problem is that it works only first time SelectedItem became true.
<DataTemplate x:Key="myDataTemplate">     <Grid x:Name="myGrid">         <Interactivity:Interaction.Behaviors>             <Core:DataTriggerBehavior Binding="{Binding SelectedItem}" Value="True">                 <Media:ControlStoryboardAction>                     <Media:ControlStoryboardAction.Storyboard>                         <Storyboard>                             <ColorAnimation                                 To="#009ABF"                                  Storyboard.TargetName="myGrid"                                  Storyboard.TargetProperty="(Grid.Background).(SolidColorBrush.Color)"                                  AutoReverse="True"                                  Duration="0:0:1"                                 RepeatBehavior="1x" />                         </Storyboard>                     </Media:ControlStoryboardAction.Storyboard>                 </Media:ControlStoryboardAction>             </Core:DataTriggerBehavior>         </Interactivity:Interaction.Behaviors>         <!--OMISSIS-->     </Grid>
See detail here

I've taken a quick look at the code you posted to stack overflow (as it is easier to read than the unformatted one on this issue) and there's not much to go with just that... can you provide a working sample app for the issue?


Feature/test project meter runs

Addresses an issue in which the project class would not return all recent meter runs - it was overwriting meter runs of one consumption type with meter runs (from the same project) of another consumption type.

Update query to use the Manager.raw() SQL query function instead of using a custom connection, updates meter run
Still needs tests for the API endpoints which use this recent_meter_runs function. (Old tests didn't catch the problem - and didn't break with these initial commits.)

Those checks failed because the newest version of the eemeter (which they depend on to pass), has not yet been released.

Might add a docstring to recent_meter_runs that describes the format of the output (looks like you map it to some custom format).
Probably not worth a change, but I probably would have done += to the query strings to add the WHERE and ORDER BY rather than the sort of indirect format thing on itself that it does now (was sort of confusing to read at first).
Also, did you test it with multiple projects (to trigger the if project_pks: branch)? Doesn't like it glancing through the tests, but perhaps I'm missing it.

A docstring would be helpful, I'll add it. It's functionality is non-obvious, and frankly took me a while to figure out as well.
Great, I'm also in favor of += for readability, esp since we are in control and know that we're using the operation on strings. I'll go ahead and make the change. I had just retained the format @evz used orginally (tagged him in case there's something we're not thinking of that could make using .format( preferable).
Good catch - I'll add unit tests for that as well. It's tested implicitly in the views, but there's some potentially tricky logic in there (e.g. .recent_meter_runs() returns meter runs for all projects, but .recent_meter_runs(project_pks=[]) returns an empty dict) that makes it all the more important to test explicitly, and that might not be covered in the view tests.

BTW, the "tricky" logic above was tricky enough that I got it wrong trying to explain it's trickiness - all the more reason to test it.

Forgot to say earlier: nice catch with the test. Glad the review was productive.


DDPB-3290: Move remaining files to Symfony 4 structure

Purpose
Using the new file structure in preparation for Symfony 4 update. Although there are loads of files here the main changes were:

Moving contents of src/AppBundle -> src/
Moving contents of src/Resources/* -> templates/, translations/ and /assets
Changing the namespace AppBundle to App and updating any references
Using file locations in some config files rather than previous AppBundle namespaced references
Adopting the more modern twig reference style (e.g. AppBundle::two:three.html.twig -> AppBundle/two/three.html.twig) and update all references in controllers, services and templates
Removing database reset between each API unit test suite (due to pipeline failures after passing in env var for the app mode)

Fixes DDPB-3290
Learning
A happy accident resulted in halving the run time of the API tests. We were doing a database drop and fixture load using the Symfony console between each step which is where the slowdown was coming from, but due to some subtle changes in how we're setting the app mode during test runs following these updates that approach no longer worked. I had to tweak some tests to make then isolated which is why there are some test changes present but the end result is quicker tests 💪 .
Oh also, I faced my regex fears and managed to work out the right regex for doing all the twig updates:
Replace all instances of App: to have an @ at the front
/App:/

Replace text:

@$0

Change : to / in twig references:
/(?=\b\d*:\b).(?=.*\bhtml.twig\b)/

Replace text:

/

Checklist

[x] I have performed a self-review of my own code
[ ] I have updated documentation (Confluence/ADR/tech debt doc) where relevant
[x] I have added tests to prove my work
[ ] The product team have approved these changes

A happy accident resulted in halving the run time of the API tests.

Well that's great to hear!

A happy accident resulted in halving the run time of the API tests.

Well that's great to hear!

That approval wasn't final btw ^ I was testing to see if you could approve without clicking 'viewed' on all files :D turns out you can

That approval wasn't final btw ^ I was testing to see if you could approve without clicking 'viewed' on all files :D turns out you can


Language chips on commits aren't accurate

Seems like the language chips on commits are double counting languages or something....

closed via https://github.com/sedouard/gittrack/pull/79


Security fix for Prototype Pollution

:bar_chart: Metadata *
simple-deep-assign is vulnerable to Prototype Pollution.
Bounty URL: https://www.huntr.dev/bounties/1-npm-simple-deep-assign
:gear: Description *
Prototype Pollution refers to the ability to inject properties into existing JavaScript language construct prototypes, such as objects.
JavaScript allows all Object attributes to be altered, including their magical attributes such as __proto__, constructor and prototype. An attacker manipulates these attributes to overwrite, or pollute, a JavaScript application object prototype of the base object by injecting other values. Properties on the Object.prototype are then inherited by all the JavaScript objects through the prototype chain.
:computer: Technical Description *
Fix implemented by not allowing to modify object prototype.
:bug: Proof of Concept (PoC) *

Create the following PoC file:

// poc.mjs
import deepAssign from 'simple-deep-assign';

console.log('Before: ', {}.polluted})
deepAssign({}, JSON.parse('{"__proto__": {"polluted": "Prototype Polluted"}}'));
console.log('After: ', {}.polluted})

Execute the following commands in terminal:

npm i simple-deep-assign # Install vulnerable module
node poc.mjs #  Run the PoC

Check the Output:

Before : undefined
After : Prototype Polluted

:fire: Proof of Fix (PoF) *
I've also added unit test to check Prototype Pollution

+1 User Acceptance Testing (UAT)

I've executed unit tests.
After fix the functionality is unaffected.

@mzfr I've added clean fix and unit test for prototype pollution

@mzfr I've added clean fix and unit test for prototype pollution

Sorry arjunshibu, we enjoyed reviewing your fix but it has not been selected this time. If this bounty has not been closed, please feel free to try again with a new pull request!
We appreciate your effort and look forward to reviewing more of your fixes in the future! 🔨😎
Come join us on Discord

Sorry arjunshibu, we enjoyed reviewing your fix but it has not been selected this time. If this bounty has not been closed, please feel free to try again with a new pull request!
We appreciate your effort and look forward to reviewing more of your fixes in the future! 🔨😎
Come join us on Discord


field type not found in type fleetpkg.Owner

I'm seeing this error when using the generator on my machine. I also see it in the github actions output.
https://github.com/andrewkroh/terraform-module-fleet/actions/runs/6293534967/job/17084177136#step:7:23

Looking at this further, any packages that have the new Owner field are not processing at all

I should probably change something in to code so that it returns a non-zero exit code. Then at least I will get a notification about the GH action failing.
But updating to the latest go-fleetpkg should fix it. See #16.

That does the trick, thanks!

Add #20 to fail fast and set an exit code.


TypeInitializationException in .Net Core 2.1

Hey,
I know .Net Core 2.1 was just released today, but I'm already trying to upgrade some applications. :D
I'm actually using your commandline package which is how I noticed the issue first described here:

var converted = TypeConvert.Convert(value, typeof(string));

The call above eventually results in this exception under .Net Core 2.1 no matter what type is converted (while everything works just fine with .Net Core 2.0):
System.TypeInitializationException
HResult=0x80131534
Message=The type initializer for 'TypeConversion`2' threw an exception.
Source=TypeConvert
StackTrace:
at System.TypeConvert.Convert[FromType,ToType](FromType value, String format, IFormatProvider formatProvider) in C:\Projects\typeconvert\TypeConvert\TypeConvert.cs:line 528
at ConsoleApp1.Program.Main(String[] args) in C:\Projects\typeconvert\ConsoleApp1\Program.cs:line 12
Inner Exception 1:
TypeInitializationException: The type initializer for 'ConvertibleType`1' threw an exception.
Inner Exception 2:
BadImageFormatException: An attempt was made to load a program with an incorrect format. (Exception from HRESULT: 0x8007000B)
Edit:
Environment: Windows 10, x64
Tested by compiling in Any CPU, x86 and x64.

Found a problem. It is new ByRefLike types. They gives BadImageFormatException if you use them in generic types/method with inappropriate signature. Error message should be clearer, but I think this is unexpected case for runtime and error is kinda fatal level.
Fixed in new release 2.1.1


Definition list renders as

I'm using this remark plugin in astro, which uses remark under the hood. The plugin is working and has changed how my Markdown definition lists get rendered, but it's rendering them as div elements:
Pre-processing
: Happens when the request is malformed

Pre-processing

Happens when the request is malformed

(I know the p element does not come from your plugin.)
Am I missing something?

This appears to be something related to Astro. As far as I can tell, your plugin is working just fine.

Just to follow up in case anyone else looks for how to get this working in Astro. The issue was that defListHastHandlers wasn’t being passed to remark-rehype as shown in the README for this package.
Configuring this looks slightly different in Astro from with a standard unified.use(...) chain, so sharing that here:
// astro.config.mjs

import { defineConfig } from 'astro/config';
import {
  remarkDefinitionList,
  defListHastHandlers,
} from 'remark-definition-list';

export default defineConfig({
  markdown: {
    remarkPlugins: [remarkDefinitionList],
    remarkRehype: {
      handlers: {
        ...defListHastHandlers,
      },
    },
  },
});

Here’s a working example: https://stackblitz.com/edit/github-xpyk5h?file=astro.config.mjs

I had this same issue, and the Astro Discord community came to the rescue!
Here’s a working example
https://stackblitz.com/edit/github-xpyk5h?file=astro.config.mjs
Big 👏  to @delucis!


Redesign command line interface

Currently, benchcab uses two main program entry points: benchcab and benchsiterun. Having benchsiterun accessible at the same level as benchcab allows the user to run benchsiterun incorrectly, for example if the user tries to run benchsiterun before the work directory is generated. Ideally benchsiterun is invoked only by the job script submitted by benchcab and should be "hidden" to the user.
Move the benchsiterun main program entry point into benchcab.
Add the ability to run specific steps in the workflow in isolation via subcommands.
These steps include checkout, build, setting up the fluxnet task work directory and executing the fluxnet tasks.
Add the --no-submit flag to disable the job script submission when executing fluxnet tasks.
This flag can also be specified in the main workflow if the user wishes to execute tasks on the login node (if the computation is inexpensive enough so that the job doesn't get killed).
Add unit tests to test the command line arguments are parsed correctly.
This should provide a command line interface that makes it difficult for the user to incorrectly run benchsiterun (now benchcab fluxnet-run-tasks --no-submit).
Fixes #21
Testing

pytest success
pip install --user . success
benchcab fluxnet success
benchcab fluxnet --no-submit success (ran with a single science configuration and AU-Tum experiment)

@ccarouge I propose instead of having benchcab, we have benchcab run for executing the default workflow?
This way, subcommands such as checkout or build won't inherit optional arguments that are not needed from the default benchcab command. For example, passing the --no-submit flag to benchcab is valid but this design allows passing the same flag to benchcab checkout which doesn't really make sense.
I think sub commands is one of things where if you start using them, everything needs to become a sub command 😅

Yes, benchcab run is ok. That's easy enough to remember.

@ccarouge I've made the changes you requested. Can you review the changes made in b8a9471? This change is addressing your comment: https://github.com/CABLE-LSM/benchcab/pull/59#discussion_r1168201303

Would it be worth getting the list of tasks only once? I don't like having the call to get_fluxnet_tasks copied so many times. It's an easy line to mess up.
Maybe worth putting it after the call to validate_environment.

I thought putting get_fluxnet_tasks after the validate_environment line is not ideal as we would be calling it for every subcommand of benchcab. I've instead abstracted get_fluxnet_tasks into a single function _initialise_tasks which removes the repetition.
As for why I went with a class implementation: this was to reduce the repetition of common arguments between all the subcommands. This is all just code aesthetic at this point.


Unable to dereference from new

/datum/foo
   var/bar = 5

/proc/RunTest()
   ASSERT((new/datum/foo()).bar == 5)

Update: The issue seems to lie in the NewPath not assigning the Path property properly. Unrelated to the issue and PR referenced above.


chore(release): v0.11.4 🎉

:robot: I have created a release beep boop
0.11.4 (2023-09-14)
Bug Fixes

oidc: expose hash and code grants from challenge (3827798)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/whodisio/whodis-client/releases/tag/v0.11.4 :sunflower:


node_lag_duration_milliseconds vs nodejs_eventloop_lag_seconds

We appear to have nodejs_eventloop_lag_seconds that comes from prom-client, as well as node_lag_duration_milliseconds that we add, we should consider getting rid of node_lag_duration_milliseconds.

Closing in favour of #29.


Fix errors in event params in non-English languages

Change-Id: Ieb42a56f10605bcd7bbbde56be4e6328992b8376

Original report from the power users here.


[WIP] slirp interface implementation for pod network

[WIP] Create slirp interface and proxy network
Create new network type Proxy.
Create new interface type slirp using the slirp configuration of qemu.
Related to issue - 1078
Design the connection API - Done
Write unit test - Inprogress
Write functional tests
Add the new connection to the user-guide
Get all PRs merged
Basic implementation of the connection method

This change is

Great progress!
After an initial brief look, I think we should change the place where proxy is being referenced.
I think we have agreed that proxy should be a binding method under an interface and not a network, as it is laid out in the networking API document[1].
I have a previous implementation of an earlier proxy attempt, it should contain the logic as how everything should be setup; I would suggest to take a look at [2]
[1] https://docs.google.com/document/d/10rXr91aqn8MvVcLgHw33WX8BaQwHPZERp25PHxoZGgw/edit#heading=h.d2sg8ncc0555
[2] https://github.com/kubevirt/kubevirt/pull/787/files#diff-4cc299b396934683b5f4388deaff9e77

@vladikr Thanks for the comment I will take a look.
If I move the proxy from then network section to the interface (change the slirp name) I Should use the pod network?
I write it this way because we may have different types of proxy implementations that the user can use for every interface he create(slirp,nat,transparent)

If I move the proxy from then network section to the interface (change the slirp name) I Should use the pod network?

Yea, as it's one only network we support at the moment.

I write it this way because we may have different types of proxy implementations that the user can use for every interface he create(slirp,nat,transparent)

That shouldn't be a problem. We could model additional modes in the proxy struct in the future if we will need it.

Amazing work.
@SchSeba could you please add yaml example to see the API in action.
/me still wonders if we should call it proxy or something more specific. Let#s see.

In the recent patchset the changes was made to rename the api from slirp to proxy in order to align with the design document.
However, the design document was explicitly speaking about a proxy - which we do not resolve right now, but probably get back to at som epoint.
Thus here it is justified to explicitly use slirp within the API - also to take it out later on once we have a solution which is providing the same set of features.
The initial part of the paragraph was discussed with @SchSeba on irc.

@booxter could you please take another look? Perhaps you have other concerns.

ok to test

Is this PR still work-in-progress, as the title suggests? It seems like we are close to getting it complete and merged, so maybe change the title to reflect the progress.

Nothing major, we could merge (there is one issue with a log message but we could tackle it separately later too).

@vladikr I think this is ready to merge though note there are no fresh CI results. I would suggest to squash on merge since commits are not logically separated anyway.

Some functional tests failed, but not because of anything related to this PR.

retest this please

retest this please

Please eliminate the WIP in the description.
Looks great


Bind to IPv6 loopback address when the "localhost" is specified

Currently Kestrel only binds to the IPv4 loopback address (<IP_ADDRESS>) and not the IPv6 loopback address (::1) when localhost is specified.
#98

Also for host names and *, bind to IPv4 Any (<IP_ADDRESS>) and IPv6 Any (::)

Binding to IPv6Any already binds to IPv4Any. Libuv is using dual stack sockets by default and needs an explicit bind flag to disable that.

@Tragetaschen Thanks for the heads up. It appears this only applies to IPv6Any. My testing shows that binding to IPv6Loopback does not bind to IPv4Loopback. Binding to IPv4Any also doesn't seem bind to IPv6Any.

not sure if my experience is related to this issue; but I'm unable to get kestrel to listen on the hostname when the host has multiple network interfaces; even the localhost is unable to access the web application via the hostname; however localhost shows that kestrel is listening on the loopback interface.

Not sure if what I am seeing is also related but since switching to beta8 I have had a new issue pop up. Granted my use case is not common but I am running a Windows 10 VM on my Mac to host / debug my api host. Until switching to Beta8 I was able to make calls directly against the api hosted in the VM via port forwarding with no issues.
The only way I can get this to work now is by launching Kestrel with the vm host name instead of localhost as I previously had in beta7. The odd thing is that on the Mac side I can make REST calls using either the vm host name or localhost and it resolves just fine. As soon as I try to host it on Kestrel with anything other then the VM host name the request times out with no error response.

@esko22 I think this is expected. Before beta8 kestrel would always listen publicly on Any/*, no matter what you specified. Now if you specify localhost it listens only on ::1. As far as the VM is concerned the Mac is a separate machine so you need to listen on a public IP or *, not localhost.

Thanks @Tratcher. Using * works great.

Is this still an issue? Is there something to be fixed?

Yes, https://github.com/aspnet/KestrelHttpServer/pull/242#issuecomment-145688074

post RC2

I've published an announcement on this change: https://github.com/aspnet/Announcements/issues/185


NURBS curve interpolation functions and small bug fix [nurbs-interp-dev]

Second part of splitted PR https://github.com/mfem/mfem/pull/2724 just as PR #3226. Others will follow.
This PR adds curve interpolation function for NURBS curves and fixes a small bug in void NURBSPatch::DegreeElevate(int dir, int t). Furthermore, it adds an example to show the usage of curve interpolation functions.
It adds the following functions:

void KnotVector::FindMaxima(Array<int> &ks, Vector &xi, Vector &u): this function finds the location of the maxima of the shapefunctions of the knotvector. This is a good distance for the curve interpolation of NURBS curves with all weights being one: B-splines.
void KnotVector::FindInterpolant(Array<Vector*> &x): Finds the interpolant of the curve through the given points x. Routine from "The NURBS book" - 2nd ed - Piegl and Tiller.

To do:

Unsure if the location of the example is correct. It is now in miniapps/nurbs with the other NURBS examples.

PR
Author
Editor
Reviewers
Assignment
Approval
Merge

#3232
@JacobLotz
@tzanio
@v-dobrev + @dylan-copeland
10/26/22
4/29/23
5/6/23

PR Checklist

[ ] Code builds.
[ ] Code passes make style.
[ ] Update CHANGELOG:

[ ] Is this a new feature users need to be aware of? New or updated example or miniapp?
[ ] Does it make sense to create a new section in the CHANGELOG to group with other related features?

[ ] Update INSTALL:

[ ] Had a new optional library been added? If so, what range of versions of this library are required? (Make sure the external library is compatible with our BSD license, e.g. it is not licensed under GPL!)
[ ] Have the version ranges for any required or optional libraries changed?
[ ] Does make or cmake have a new target?
[ ] Did the requirements or the installation process change? (rare)

[ ] Update continuous integration server configurations if necessary (e.g. with new version requirements for each of MFEM's dependencies)

[ ] .github
[ ] .appveyor.yml

[ ] Update .gitignore:

[ ] Check if make distclean; git status shows any files that were generated from the source by the project (not an IDE) but we don't want to track in the repository.
[ ] Add new patterns (just for the new files above) and re-run the above test.

[ ] New examples:

[ ] All sample runs at the top of the example source file work.
[ ] Update examples/makefile:

[ ] Add the example code to the appropriate SEQ_EXAMPLES and PAR_EXAMPLES variables.
[ ] Add any files generated by it to the clean target.
[ ] Add the example binary and any files generated by it to the top-level .gitignore file.

[ ] Update examples/CMakeLists.txt:

[ ] Add the example code to the ALL_EXE_SRCS variable.
[ ] Make sure THIS_TEST_OPTIONS is set correctly for the new example.

[ ] List the new example in doc/CodeDocumentation.dox.
[ ] If new examples directory (e.g.examples/pumi), list it in doc/CodeDocumentation.conf.in
[ ] Companion pull request for documentation in mfem/web repo:

[ ] Update or add example-specific documentation, see e.g. the src/examples.md.
[ ] Add the description, labels and screenshots in src/examples.md and src/img.
[ ] In examples.md, list the example under the appropriate categories, add new categories if necessary.
[ ] Add a short description of the example in the "Extensive Examples" section of features.md.

[ ] New miniapps:

[ ] All sample runs at the top of the miniapp source file work.
[ ] Update top-level makefile and makefile in corresponding miniapp directory.
[ ] Add the miniapp binary and any files generated by it to the top-level .gitignore file.
[ ] Update CMake build system:

[ ] Update the CMakeLists.txt file in the miniapps directory, if the new miniapp is in a new directory.
[ ] Add/update the CMakeLists.txt file in the new miniapp directory.
[ ] Consider adding a new test for the new miniapp.

[ ] List the new miniapp in doc/CodeDocumentation.dox
[ ] If new miniapps directory (e.g.miniapps/nurbs), add it to MINIAPP_SUBDIRS in the makefile.
[ ] If new miniapps directory (e.g.miniapps/nurbs), list it in doc/CodeDocumentation.conf.in
[ ] Companion pull request for documentation in mfem/web repo:

[ ] Update or add miniapp-specific documentation, see e.g. the src/meshing.md and src/electromagnetics.md files.
[ ] Add the description, labels and screenshots in src/examples.md and src/img.
[ ] The miniapps go at the end of the page, and are usually listed only under a specific "Application (PDE)" category.
[ ] Add a short description of the miniapp in the "Extensive Examples" section of features.md.

[ ] New capability:

[ ] All new public, protected, and private classes, methods, data members, and functions have full Doxygen-style documentation in source comments. Documentation should include descriptions of member data, function arguments and return values, template parameters, and prerequisites for calling new functions.
[ ] Pointer arguments and return values must specify whether ownership is being transferred or lent with the call.
[ ] Any new functions should include descriptions of their intended use e.g. for internal use only, user-facing, etc., along with references to example code whenever possible/appropriate.
[ ] Consider adding new sample runs in existing examples to highlight the new capability.
[ ] Consider saving cool simulation pictures with the new capability in the Confluence gallery (LLNL only) or submitting them, via pull request, to the gallery section of the mfem/web repo.
[ ] If this is a major new feature, consider mentioning it in the short summary inside README (rare).
[ ] List major new classes in doc/CodeDocumentation.dox (rare).

[ ] Update this checklist, if the new pull request affects it.
[ ] Run make unittest to make sure all unit tests pass.
[ ] Run the tests in tests/scripts.
[ ] (LLNL only) After merging:

[ ] Update internal tests to include the new features.

This PR is now under review (see the table in the PR description). To help with the review process, please do not force push to the branch.

Hi @dylan-copeland, thank you for your comments! I see that the example is done a bit quick and dirty. I am currently out of office and will get back to you on Tuesday.

Merged in next for testing...

@JacobLotz was there a reason not to add nurbs_curveint to miniapps/nurbs/makefile? It has to be built individually. If it were in makefile, then make in the directory miniapps/nurbs should build nurbs_curveint.

@dylan-copeland I assumed that the makefile was created using CMake so I have only updated CMakeLists.text. As I understand now MFEM can be build in two ways and there is there is also a separate makefile. I use CMake to build MFEM so that is problably the reason why I did not notice it.
I wil create a separate pull request to fix these issues.


0.2.1-1 seems broken

Hi, thanks for maintaining this project. I found the newly released 0.2.1-1 seems to be broken on our build. Would you like to take a look? Thanks.
https://github.com/apache/opendal/actions/runs/10197254847/job/28212887362
  sudo "PATH=$PATH" luarocks make
  busted test/opendal_test.lua
  shell: /usr/bin/bash -e {0}
  env:
    RUSTFLAGS: -C force-frame-pointers=yes -C debuginfo=1
    RUST_BACKTRACE: 1
    RUST_LOG: opendal=trace
    CARGO_REGISTRIES_CRATES_IO_PROTOCOL: sparse
Missing dependencies for opendal 0.1.3-1:
   luarocks-build-rust-mlua (not installed)

opendal 0.1.3-1 depends on lua >= 5.1 (5.2-1 provided by VM)
opendal 0.1.3-1 depends on luarocks-build-rust-mlua (not installed)
Installing https://luarocks.org/luarocks-build-rust-mlua-0.2.1-1.src.rock

No existing manifest. Attempting to rebuild...
error: failed to run `rustc` to learn about target-specific information

Caused by:
  process didn't exit successfully: `/root/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/bin/rustc - --crate-name ___ --print=file-names --target target --crate-type bin --crate-type rlib --crate-type dylib --crate-type cdylib --crate-type staticlib --crate-type proc-macro --print=sysroot --print=split-debuginfo --print=crate-name --print=cfg` (exit status: 1)
  --- stderr
  error: Error loading target specification: Could not find specification for target "target". Run `rustc --print target-list` for a list of built-in targets

Error: Build error: Failed building.
luarocks-build-rust-mlua 0.2.1-1 is now installed in /usr/local (license: MIT)

I'm guessing it's related to https://github.com/mlua-rs/luarocks-build-rust-mlua/commit/44eb3ae7fbf225994948793e438471fb2a03ba69

Thanks for the report, I deleted this version until further investigation!

I published v0.2.2 that should have the issue solved

Thank you @khvzak for fix this, closing now.


Automated cherry pick of #6817: guestnetworks: use math/rand instead of crypto/rand

Cherry pick of #6817 on release/3.1.
#6817: guestnetworks: use math/rand instead of crypto/rand

Codecov Report

Merging #6819 into release/3.1 will decrease coverage by 0.37%.
The diff coverage is 9.70%.

@@               Coverage Diff               @@
##           release/3.1    #6819      +/-   ##
===============================================
- Coverage         7.48%    7.11%   -0.38%
===============================================
  Files              585      600      +15
  Lines            98953   105867    +6914
===============================================
+ Hits              7411     7528     +117
- Misses           90970    97765    +6795
- Partials           572      574       +2

Flag
Coverage Δ

#aFlag
7.11% <9.70%> (-0.38%)
:arrow_down:

Impacted Files
Coverage Δ

pkg/cloudcommon/policy/policy.go
1.58% <ø> (+<0.01%)
:arrow_up:

pkg/cloudcommon/policy/resources.go
0.00% <ø> (ø)

pkg/cloudprovider/objectstore.go
2.51% <0.00%> (-0.01%)
:arrow_down:

pkg/cloudprovider/securitygroup.go
0.00% <0.00%> (ø)

pkg/compute/guestdrivers/managedvirtual.go
0.00% <0.00%> (ø)

pkg/compute/models/buckets.go
1.24% <0.00%> (ø)

pkg/compute/models/cloudproviders.go
0.96% <0.00%> (-0.01%)
:arrow_down:

pkg/compute/models/disks.go
0.55% <0.00%> (-0.01%)
:arrow_down:

pkg/compute/models/guestdisks.go
0.58% <ø> (+0.01%)
:arrow_up:

pkg/compute/models/guestnetworks.go
0.21% <0.00%> (+<0.01%)
:arrow_up:

... and 43 more

Continue to review full report at Codecov.

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


Create a clean instance of the mock server so function tests don't bleed over

Goal
This is why I need to delete that friggin static logger: now the internal errors won't bleed over between functional test cases so those tests won't flake. HALLELUJAH!!!
I had to tweak some of the test clean up as well but that damn logger was the main blocker.
Testing
Functional tests won't flake after this.

#633  👈
master

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @bidetofevil and the rest of your teammates on  Graphite

Spinning this up and down should actually be pretty fast - especially compared to the time it takes to run the tests. Functions tests took 20m+ to run last week and the last successful run on top of these changes too 17m, so it's probably about the same.
I'll merge this as is right now but keep an eye on this. The run taking this long is probably a problem - but I don't think this adds to it materially 😅


Error when unmounting

Right now, the code uses the ref callback in React to get the node in order to embed the Elm component but after unmounting the callback gets called again, this time with null. This is by design https://facebook.github.io/react/docs/more-about-refs.html . The problem is that when it gets called with null it still tries to embed the Elm component throwing an error:

The component should either use some lifecycle method (like componentDidMount) or do a null check.
Thoughts?

Interesting, thanks for reporting this!
In an upcoming release, there will be a way to kill an Elm app so we can turn everything off properly. Fixing this is blocked on that feature.

It's a bug which prevents the ELM component to work in react-router?

Not sure @linyanzhong.
If you are running into this kind of thing, I'd recommend using Elm.MyThing.embed directly and setting up your ports directly, as described in this section of the guide. That is the actual Elm API. This package is mainly intended to cover simple cases and reveal to people that embedding Elm is actually relatively straight-forward.

Just reproduced the react-router problem in the example: Source

Click "Chat" for the first time, it works
Click "Hello", the console logs Chat.elm:6546 Uncaught TypeError: Cannot read property 'appendChild' of null, which points to parent.appendChild(domNode);
Click "Chat" again, the ELM component does not show

It seems possible to use react-router in a tricky way:
Use Elm.MyThing.embed and set up ports directly as mentioned by @evancz above, then write an empty React component, in its componentDidMount and componentWillUnmount, set the ELM component's .style.display to block or none.

I am seeing the same error with my component as well.

@arecvlohe , if you don't use react-router, and don't mind seeing the warning message in the console, maybe you can continue using this component and wait for the next elm release.
Now I'm using the tricky way described in my last comment: embed the elm component manually like interop javascript, and let react-router control its visibility via a dummy "proxy" react component like this one.

@linyanzhong I was able to get it to work as you described, with the error in the console. It works with react-router, but also slows page speed down a bit.
I am currently using this component in a side project to kind of test it out. If this gets to the point where it can be used in a robust React/Redux application, then I would be encouraged to introduce it at work and not look like a crazy person :)

I just ran into this bug when trying to integrate a standalone Elm app into a larger React app at work (which uses react-router).
@evancz will 0.18 unblock the fix? Based on reading the mailing list, it sounds like the teardown stuff will not land until 0.19. I love the idea of this React component and the "use Elm at work" blog post, but right now it's difficult to actually use it at-work where it's common to have an app that's complex enough to need a router.
In the interest of not getting blocked, I'm going to try @linyanzhong workaround. But if the real fix is a long way off, perhaps a workaround should be mentioned in the README? @rtfeldman did NoRedInk have similar problems? Any tips?

Same hear. Was super excited to finally be able to use it at work, and now it doesn't work. I guess I'll check Elm.MyThing.embed out.

Shouldn't it be somehow possible to get elm garbage collected before it causes issues ?

@MoeSattler that's what I'm hoping for--and in my case I'm just doing this on an internal admin page, so it's good-enough for me. I don't know enough about the Elm runtime nor JS internals, but it seems likely that there would be situations where the Elm runtime registers a callback with the Browser, and that without an explicit cleanup/teardown step, it would stay alive and not be able to be collected.

@klazuka
but it seems likely that there would be situations where the Elm runtime registers a callback with the Browser
I think that's the case with the ports.
But even when using the Elm.MyThing.embed recommended by @evancz, there must be a way of unmounting elm, right? Otherwise I don't see any way yo gradually introduce elm into a React project whatsoever.

@klazuka
Adding a null check fixes the situation for me. It feels very hacky though:

	initialize: function(node) {
		if (!node) return;
		var app = this.props.src.embed(node, this.props.flags);

		if (typeof this.props.ports !== 'undefined') {
			this.props.ports(app.ports);
		}
	},

Any input on this? Will this cause a memory leak?

If anyone is interested, I am trying to work on an alternative solution:
https://github.com/MoeSattler/reactify-elm
PRs are welcome

@kitofr This proposition was merged with #5 and I never had problems with it in reactify-elm, so I am pretty sure it should work fine.

Tnx

almost there.
I could have a port to handle unmount (stop subscription, minimize memory usage)
subscriptions : Model -> Sub Msg
subscriptions model =
    if model.mounted then
        Sub.batch
            [ unmount Unmount
            , Browser.Events.onResize WindowResize -- we'll stop seeing these after `unmount`
            ]

    else
        -- Elm runtime should unmount listeners and not leak memory
        Sub.none

I could extend the provided Elm component with componentWillUnmount handler...
class UnmountableElm extends Elm {
  componentWillUnmount () {
    this.app.ports.unmount.send(null)
  }
}

but I can't invoke that port and tell my app instance to clean up if there's no reference to the app which was created as a local var in initialize https://github.com/cultureamp/react-elm-components/blob/879c8ef784b85c23df3ecf28f715a0ac050b6859/index.js#L8-L12
PS: yes even after cleanup, my Elm app is still in memory until Elm allows me to remove the instance proper

can't invoke that port and tell my app instance to clean up

can be achieved after all
import { unmountWithPort, UnmountableElm } from './UnmountableElm.js'
import Counter from './elm/Counter.js'

function App () {
  return <UnmountableElm
          src={Counter.Elm.Counter}
          ports={unmountWithPort('unmount')}
          />
}

with a wrapper, e.g. UnmountableElm.js
import React from 'react'
import Elm from 'react-elm-components'

var unmountFunctionRefs = {}
export function unmountWithPort (portName, originalHandler) {
  return function (ports) {
    if (originalHandler) originalHandler(ports)
    if (ports && ports[portName]) {
      unmountFunctionRefs[this] = ports[portName].send // `this` refers to the react component instance
    }
  }
}

export class UnmountableElm extends Elm {
  componentWillUnmount () {
    let unmountThis = unmountFunctionRefs[this]
    delete unmountFunctionRefs[this]
    if (unmountThis) unmountThis()
  }
}


Create a QR Code type of modal window for Tag/Value alias

Description
The goal of this PR is to create a QR Code type of modal window for Tag/Value alias
Changes include

[ ] Bugfix (non-breaking change that solves an issue)
[x] New feature (non-breaking change that adds functionality)
[ ] Breaking change (change that is not backwards-compatible and/or changes current functionality)
[ ] Tests
[ ] Documentation
[ ] Other (for changes that might not fit in any category)

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

Project coverage is 35.76%. Comparing base (0bac17f) to head (a9e43e9).

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #797   +/-   ##
=======================================
  Coverage   35.76%   35.76%
=======================================
  Files          13       13
  Lines        1591     1591
=======================================
  Hits          569      569
  Misses       1022     1022

Flag
Coverage Δ

unittests
35.76% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

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


Cannot write track events with custom datasource

               CustomDataSource::Trace([](CustomDataSource::TraceContext ctx) {
                   auto packet = ctx.NewTracePacket();
                   packet->set_timestamp(42);
                   packet->set_for_testing()->set_str("Hello world!");
               });

                CustomDataSource::Trace([](CustomDataSource::TraceContext ctx) {
                    auto packet = ctx.NewTracePacket();
                    packet->set_timestamp(43);
                    auto trackEvent = packet->set_track_event();
                    packet->set_trusted_packet_sequence_id(23);
                    auto* event = packet->set_track_event();
                    event->add_categories("cat");
                    event->set_name("ev1");
                    event->set_type(perfetto::protos::pbzero::TrackEvent::TYPE_INSTANT);
                });

I can see a bunch of in the protobuffer result, but there are no packet with "timestamp: 43". If I remove packet->set_track_event(), I can see "timestamp: 43" in the result.
packet {
  first_packet_on_sequence: true
  timestamp: 42
  for_testing {
    str: "Hello world!"
  }
  trusted_uid: 0
  trusted_packet_sequence_id: 2
  trusted_pid: 0
  previous_packet_dropped: true
}

Why is this the case? How can I record data correctly as mentioned in https://perfetto.dev/docs/reference/synthetic-track-event ?

If you are emitting track_event using the SDK, is there a reason why you are trying to write the packets manually instead of using the track_event macros (https://perfetto.dev/docs/instrumentation/track-events)? The synthetic track_event page was designed for folks specifically not using the SDK i.e. they have some other trace format they want to convert to Perfetto to visualise it in the UI or query with trace processor. If you're already using the SDK, there is little need to look at that page at all.

To answer your actual question though, the problem is the line auto trackEvent = packet->set_track_event();. Protozero
(the proto library that Perfetto uses) expects that the fields of a sub-message are all written contiguously. Given that you call set_track_event twice, that causes undefined behaviour. The trusted_packet_sequence_id also should not be written if you are using the SDK: again that's only designed if you are writing track_event without using the SDK.
Your code should work if you do something like this:
                CustomDataSource::Trace([](CustomDataSource::TraceContext ctx) {
                    auto packet = ctx.NewTracePacket();
                    packet->set_timestamp(43);
                    auto* event = packet->set_track_event();
                    event->add_categories("cat");
                    event->set_name("ev1");
                    event->set_type(perfetto::protos::pbzero::TrackEvent::TYPE_INSTANT);
                });

If you are emitting track_event using the SDK, is there a reason why you are trying to write the packets manually instead of using the track_event macros (https://perfetto.dev/docs/instrumentation/track-events)? The synthetic track_event page was designed for folks specifically not using the SDK i.e. they have some other trace format they want to convert to Perfetto to visualise it in the UI or query with trace processor. If you're already using the SDK, there is little need to look at that page at all.

I'm trying to:

Record trace information lazily at a certain time rather
Display not perfectly nested data. According to ref "Users are recommended to emit TrackEvent instead"

It's still not clear to me if you have the following case:

you have a C++ program (library, binary whatever) you are trying to instrument to collect tracing information while the system runs
if you have some already existing data source you are trying to visualize in the UI without having a live tracing system

The "Synthetic Track Event" page is only appropriate for case 2). For case 1) you should be using the track_event macros in the SDK as described in https://perfetto.dev/docs/instrumentation/track-events. For case 2), you don't need (and shouldn't) use the SDK at all, you can just use any protobuf writing library (e.g. the official library) and just write protos directly. I explained how to do this a few days ago for Python, the instructions for C++ are very similar: https://github.com/google/perfetto/issues/779.


Fixed compilation with PHP 5.6

Tested against PHP 5.6.3 and 5.5.20.

Yes please :D

:+1:

Where are the maintainers to review this? I have clients that need to install Runkit and I don't feel comfortable telling them they need to use a patch from a non-official account... This should be a no brainer.

@Qix- I'd suggest to contact @zenovich directly and offer to pay him for that review and merge.

@tmuras Thanks for the snarky and useless comment :+1:

Any plans to add PHP 7 support as well?

I seriously doubt all this stuff is going to work with PHP7.
Most likely it'll require some serious modifications.


Sentiment Analyzer Web App added

Description 📜
Sentiment Analyzer Web App added using ml5.js API
Fixes #780

Type of change 📝
Please delete options that are not relevant.And in order to tick the check box just but x inside them for example [x] like this

[x] Add a new project

Domain of Contribution 📊
Please delete options that are not relevant.And in order to tick the check box just but x inside them for example [x] like this

[x] Project using HTML, CSS & JS

Checklist ✅
Please delete options that are not relevant.And in order to tick the check box just but x inside them for example [x] like this

[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I'm GSSoC'22 contributor

Screenshots / Gif (Optional) 📸
Add the screenshot of the changes you have made

This branch is 2 commits ahead, 168 commits behind khushi-purwar/WebDev-ProjectKart: master.
@shreya024

This branch is 2 commits ahead, 168 commits behind khushi-purwar/WebDev-ProjectKart: master.
@shreya024

It should not create any problem as it was only 2 commits ahead at the time of making the PR. However, I will still merge it

This branch is 2 commits ahead, 168 commits behind khushi-purwar/WebDev-ProjectKart: master.
@shreya024

It should not create any problem as it was only 2 commits ahead at the time of making the PR. However, I have still updated it. @gurjeetsinghvirdee Kindly merge

Not a problem with ahead but that your branch was behind, If you don't fetch upstream and I merge it then next it will give you complex conflicts that you can't resolve either me


Reproducible chart dependency archives

Currently (as of 3.3.4), helm dependency build doesn't produce reproducible .tgz archives at charts/ dir.
We're using file:// only dependencies, and expect two runs of the helm dependency build to generate the same charts/*.tgz files, however the sha256 sums are different.
This prevents us from using git lfs to store the charts/*.tgz dir.

This may be a symptom of https://github.com/helm/helm/issues/3612 as helm dependency build calls the same APIs as helm package to package the file::// dependencies.

Sounds very much like it.
I'm thinking about a workaround -if we copy-over/symlink the contents of the file:// dependencies to charts/, unarchived - this should allow us to both omit the lfs and work around this issue.
Does this sound like a good idea? Any hidden issues with this approach?

If someone wants to fix this issue... we would be happy to look at it.


when u mark the rocm 2.5 release  at source code repo ?

~/bin/repo init -u https://github.com/RadeonOpenCompute/ROCm.git -b roc-2.5.0
fatal: Couldn't find remote ref refs/heads/roc-2.5.0
when u mark the rocm 2.5 release ?

I know this is an old issue, but I just successfully repo synced 2.5.0, so I believe we eventually tagged everything correctly. :)


Test gitian build: MacOS Yosemite (v3.1.0-rc7.2)

PreRelease v3.1.00-rc7.2:

Downloads for Mac:

Logs (Mac)
build.log, install.log
Gitian signatures

@gitianuser   3.1.00-rc7.2-osx-unsigned

Community is not active, I dont use MacOS binaries and with that issue closed. If somebody tests and has any issues, feel free to reopne or create new issue.


Doomfist can noclip through walls using slam

Created by: Vortex4321
Video proof: https://youtu.be/9etuJCyrric
There are more spots than this one.

Created by: MaxwellJung
I'm aware his indicator slam is extremely buggy, but I'm trying to get doom "feature complete" before ironing out bugs.
There's still a lot of features missing in doom such as slam timer, single target rocket punch, slam bounche mechanic, etc that I want to add to the game before I fix indicator slam.

mentioned in issue ow1_emulator_backup#594

Created by: MaxwellJung
I thought v0.3.0 fixed it, but this bug is still replicable in v0.3.1

moved from ow1_emulator_backup#600


Modified NCF in DIT/MODIT also added some benchmark tests for MODIT

I noticed that the previous version of NCF in DIT/MODIT makes the computation time very slow (proportional to # of lines). So, I modified it using jax.ops.index_add. This modification makes the code very fast for large number of the lines (as written in the original paper of DIT).
You can test this modification by the benchmark codes in tests/benchmark:
python modit_bm_wide_test.py

or
pytest modit_bm_each_test.py

You can also check the results (comparison with DIT. MODIT and LPF) by a sample in tests/auto:
python modit_test.py

Thanks!

see also #122

d7878ad does not change the core part of modit/dit but confirmed HMC-NUTS with the current version works.
See Reverse modeling for methane using MODIT.ipynb

Thank you! I updated the codes based on the review.

mcmc = MCMC(kernel, num_warmup=num_warmup, num_samples=num_samples)?

Yes, I also noticed newer environments require these explicit options.


How to close WebView and save passwords automatically?

Like this
WebView.getSettings().setSavePassword(false)
How to configure?

@majiabin did you ever find a solution to this?


Swap modules A and B

Codecov Report

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

@@            Coverage Diff             @@
##           master      #72      +/-   ##
==========================================
+ Coverage   83.37%   83.68%   +0.31%
==========================================
  Files          21       21
  Lines        1606     1606
  Branches      160      160
==========================================
+ Hits         1339     1344       +5
+ Misses        226      220       -6
- Partials       41       42       +1

Impacted Files
Coverage Δ

robot.py
76.3% <ø> (ø)
:arrow_up:

autonomous/autonomous.py
65.21% <0%> (+1.97%)
: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 859c1c3...65d9580. Read the comment docs.

You forgot to swap them in the physics as well.


Fix:  JitPack is broken

Fix #1
Use before_install to force initialization of the JDK.

This looks like it is working correctly.


css inspector added

Description
i have added all the required files
and also added content and background js files
also done live testing on big website cehckout screenshot
Fixes:  #976

Type of change

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

Checklist:

[x] I have made this from my own
[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] My changes generate no new warnings

ATTACH SCREEN-SHOTS / DEPLOYMENT LINK
Before running Extension

on running and setting styles

after clicking apply button

@Sulagna-Dutta-Roy please mam check the file changes
and upgrade to level3 if you think it deserves


Using Oniguruma library (optionally)

Can be tested by $ make USE_ONIGURUMA=1. Of course Oniguruma should be installed, e.g. $ sudo apt install libonig-dev.
I only tested on Linux. ;)

@tavianator What else can I do in this PR?

Mostly I just need to try it out myself, haven't gotten to it yet.  Also, even if it's incomplete, if you have an example of how it would enable a new regex flavour that would be good to see.

if you have an example of how it would enable a new regex flavour

First we need to define a switches for RE dialects.
Maybe #21 is the best place for that.

There's already -regextype.  It would be nice to get close to full compatibility with GNU find there.

Ok, got it!
I assumed you would do a new release with this PR. So that users could test it. ;)

I'm open to a release that just adds the library without the new regex flavours, but I'd like to see that it's at least possible to implement them with this library

I'd like to see that it's at least possible to implement them with this library

https://github.com/kkos/oniguruma/blob/a2ac402a3549713e6c909752937b7a54f559beb8/src/oniguruma.h#L433-L445
/* predefined syntaxes (see regsyntax.c) */
#define ONIG_SYNTAX_ASIS               (&OnigSyntaxASIS)
#define ONIG_SYNTAX_POSIX_BASIC        (&OnigSyntaxPosixBasic)
#define ONIG_SYNTAX_POSIX_EXTENDED     (&OnigSyntaxPosixExtended)
#define ONIG_SYNTAX_EMACS              (&OnigSyntaxEmacs)
#define ONIG_SYNTAX_GREP               (&OnigSyntaxGrep)
#define ONIG_SYNTAX_GNU_REGEX          (&OnigSyntaxGnuRegex)
#define ONIG_SYNTAX_JAVA               (&OnigSyntaxJava)
#define ONIG_SYNTAX_PERL               (&OnigSyntaxPerl)
#define ONIG_SYNTAX_PERL_NG            (&OnigSyntaxPerl_NG)
#define ONIG_SYNTAX_RUBY               (&OnigSyntaxRuby)
#define ONIG_SYNTAX_PYTHON             (&OnigSyntaxPython)
#define ONIG_SYNTAX_ONIGURUMA          (&OnigSyntaxOniguruma)

Thanks!
Now I can start working on a better Oniguruma integration! :)


Make travis test on Docker 1.13.1 as well

👍  i think it might make sense to start phasing out older versions as well

Codecov Report

Merging #646 into master will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #646   +/-   ##
=========================================
  Coverage     62.29%   62.29%
- Complexity      559      560    +1
=========================================
  Files           134      134
  Lines          2578     2578
  Branches        315      315
=========================================
  Hits           1606     1606
  Misses          826      826
  Partials        146      146

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 85697ea...11d6e33. Read the comment docs.


Support a donate_spec argument in filter_jit

As an analogue for donate_argnums.

Closing as done in the next release.


Misaligned Matrix/Vector Brackets

Description
The lack of alignment looks a bit weird to me:

Reproduction URL
No response
Operating system
Web app
Typst version

[X] I am using the latest version of Typst

If you want them to align I'd go with a 4x1 matrix instead of a vector. It's more cramped because it looks better in isolation.

it seems to make sense to "insert" a strut into each alignment cell like TeX does.
The problem is even more pronounced if there are more rows.

$
mat(a,b;c,d)mat(x;y)=
x mat(a;c)+y mat(b;d)=
mat(a x+b y;c x+d y)
$

looks like this which doesn't look good

While latex looks like this:
$$
\begin{bmatrix} a & b \\ c & d \end{bmatrix}\begin{bmatrix} x \\ y \end{bmatrix} = x\begin{bmatrix} a \\ c \end{bmatrix} + y\begin{bmatrix} b \\ d \end{bmatrix} = \begin{bmatrix} ax + by \\ cx + dy \end{bmatrix}
$$

There are 2 thing different:

it looks like there is a minimal height limit in latex: note the [a, c] is not that small in latex
typst stretches [ax + by, cx + dy] too high. In latex it's smaller

LaTeX set a minimal height for each matrix cell, it is the same as a invisible (

You may want to try https://typst.app/universe/package/natrix . It somehow "fix"es this bug. The root cause is that LaTeX will pad the height of each matrix cell to a certain minimal height and typst doesn't do it at this moment. I will also try fix this in rust.


Add error handling for repo cloning

Reference Issues/PRs

What does this implement/fix? Explain your changes.

This PR modifies the clone_repo function call in context_manager.py to handle failures more gracefully. The original implementation could lead to confusing FileNotFoundError messages. The new implementation checks if the clone_repo function succeeds and raises an explicit exception if it fails, providing a clearer error message.
Original implementation output:
Cmd('git') failed due to: exit code(128)
  cmdline: git clone -v --<EMAIL_ADDRESS>/Users/joezhu/dev/SWE-agent/evaluation/testbed/54f1acd8dd/django/3.1/tmppag9rw_s/django__django__3.1
  stderr: 'Cloning into '/Users/joezhu/dev/SWE-agent/evaluation/testbed/54f1acd8dd/django/3.1/tmppag9rw_s/django__django__3.1'...
POST git-upload-pack (175 bytes)
POST git-upload-pack (gzip 20567 to 10338 bytes)
error: 6737 bytes of body are still expected
fetch-pack: unexpected disconnect while reading sideband packet
fatal: early EOF
fatal: fetch-pack: invalid index-pack output
'
2024-05-20 00:31:05,969 - testbed - INFO - Cloned django/django to /Users/joezhu/dev/SWE-agent/evaluation/testbed/54f1acd8dd/django/3.1/tmppag9rw_s/django__django__3.1
2024-05-20 00:31:05,969 - testbed - INFO - Creating environment django__django__3.1
2024-05-20 00:31:42,454 - testbed - INFO - Installing dependencies for django__django__3.1; Command: . /Users/joezhu/dev/SWE-agent/evaluation/testbed/54f1acd8dd/django/3.1/tmpbd9g2x0y/miniconda3/bin/activate django__django__3.1 && echo 'activate successful' && pip install -r /Users/joezhu/dev/SWE-agent/evaluation/testbed/54f1acd8dd/django/3.1/tmppag9rw_s/requirements.txt
/Users/joezhu/dev/SWE-agent/evaluation/testbed/54f1acd8dd/django/3.1/tmppag9rw_s/django__django__3.1: 1 instances
❌ Evaluation failed: [Errno 2] No such file or directory:
'/Users/joezhu/dev/SWE-agent/evaluation/testbed/54f1acd8dd/django/3.1/tmppag9rw_s/django__django__3.1'
Traceback (most recent call last):
  File "/Users/joezhu/dev/SWE-agent/evaluation/evaluation.py", line 58, in main
    run_evaluation(
  File "/Users/joezhu/dev/SWE-agent/venv/lib/python3.10/site-packages/swebench/harness/run_evaluation.py", line 200, in main
    eval_engine(args)
  File "/Users/joezhu/dev/SWE-agent/venv/lib/python3.10/site-packages/swebench/harness/engine_evaluation.py", line 172, in main
    setup_testbed(data_groups[0])
  File "/Users/joezhu/dev/SWE-agent/venv/lib/python3.10/site-packages/swebench/harness/engine_validation.py", line 108, in
setup_testbed
    data_dict.func(distributed_task_list[0])
  File "/Users/joezhu/dev/SWE-agent/venv/lib/python3.10/site-packages/swebench/harness/engine_evaluation.py", line 95, in
evaluate_predictions
    with TaskEnvContextManager(
  File "/Users/joezhu/dev/SWE-agent/venv/lib/python3.10/site-packages/swebench/harness/context_manager.py", line 538, in __enter__
    os.chdir(self.testbed)
FileNotFoundError: [Errno 2] No such file or directory:
'/Users/joezhu/dev/SWE-agent/evaluation/testbed/54f1acd8dd/django/3.1/tmppag9rw_s/django__django__3.1'

Other comments

@ALiersEL We're very grateful for your detailed error message, explanation of the fix, and the fix itself.
The fix LGTM. I tested it and it works great + is much clearer, thanks so much for your contribution!


PyCharm isn't resolving namedspaced packages correctly

Seems that PyCharm can no longer (I'm not sure if it ever worked or if it did might have just be indeterministic) resolve python modules that share a package. google-cloud-* is a good example.
I depend on
google-api-core==1.26.3
google-auth==1.30.0
google-cloud-monitoring==1.1.0
google-cloud-pubsub==2.6.0

And my editor cannot find google.cloud.pubsub_v1.

When I go to the declaration for google.cloud it takes me here, which is inside google.cloud.monitoring

I'm using Python 3.9 with rules_python 0.6.0 and I am using pip_parse to install the dependencies.

Hello @caseyduquettesc, Could you please elaborate your query with more details like how is it related to bazel plugin. Thanks!

I only experience the problem when I use bazel, otherwise the packages resolve fine.