@hasOne and @belongsto is NOT bidirectional

Before opening, please confirm:

[X] I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
node 16
Amplify CLI Version
7.6.25
What operating system are you using?
windows
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
None
Amplify Categories
api
Amplify Commands
push
Describe the bug
Models and VTL created for @hasOne and @belongsTo is not connected.
Expected behavior
Should work as described by cli docs. Models of hasOne and belongsTo should reference each other.
Reproduction steps
I've responded to the other ticket aws-amplify/amplify-category-api#89 , but It seems that no one is follow up old tickets?
For a demo I've recreated the example in cli docs
The expected behavior is that hasOne and belongsTo should behave similar to hasMany and belongsTo. The cli docs describes has one like this:
Has One: Create a one-directional one-to-one relationship between two models. For example, a Project "has one" Team. This allows you to query the team from the project record.
Belongs To relationship: Make a "has one" or "has many" relationship bi-directional with the @belongsTo directive.
Model:
input AMPLIFY {
  globalAuthRule: AuthRule = { allow: public }
}

type Project @model {
  id: ID!
  name: String
  team: Team @hasOne
}

type Team @model {
  id: ID!
  name: String!
  project: Project @belongsTo
}

Then I set up a team and try to connect the project to the team.
Mutations:
mutation MyMutation {
  createTeam(input: {name: "test team1"}) {
    id
  }
}
### Response
{
  "data": {
    "createTeam": {
      "id": "d83d577a-cf84-4a59-a2c7-0dffdab03218"
    }
  }
}
### end response

mutation CreateProject {
  createProject(input: {name: "New Project", projectTeamId: "d83d577a-cf84-4a59-a2c7-0dffdab03218"}) {
    id
    name
    team {
      id
      name
      project {
        id
        name
      }
    }
  }
}

### Response
{
  "data": {
    "createProject": {
      "id": "c3f685f2-ef36-4914-b456-95dbe5be3b41",
      "name": "New Project",
      "team": {
        "id": "d83d577a-cf84-4a59-a2c7-0dffdab03218",
        "name": "test team1",
        "project": null
      }
    }
  }
}
### end response

You can see that the last response that team d83d577a-cf84-4a59-a2c7-0dffdab03218 is not connected to project. This is verified with a full query.
Query:

query MyQuery {
  listTeams {
    items {
      id
      teamProjectId
      project {
        name
        id
      }
      name
    }
  }
  listProjects {
    items {
      id
      name
      projectTeamId
      team {
        name
        id
      }
    }
  }
}

{
  "data": {
    "listTeams": {
      "items": [
        {
          "id": "d83d577a-cf84-4a59-a2c7-0dffdab03218",
          "teamProjectId": null,
          "project": null,
          "name": "test team1"
        }
      ]
    },
    "listProjects": {
      "items": [
        {
          "id": "c3f685f2-ef36-4914-b456-95dbe5be3b41",
          "name": "New Project",
          "projectTeamId": "d83d577a-cf84-4a59-a2c7-0dffdab03218",
          "team": {
            "name": "test team1",
            "id": "d83d577a-cf84-4a59-a2c7-0dffdab03218"
          }
        }
      ]
    }
  }
}

When I look at the internal schema generated by amplify cli (amplify\backend\api\awstest\build\schema.graphql) , the models do not have any connections....
Internal schema:

type Project {
  id: ID!
  name: String
  team: Team
  createdAt: AWSDateTime!
  updatedAt: AWSDateTime!
  projectTeamId: ID
}

type Team {
  id: ID!
  name: String!
  project: Project
  createdAt: AWSDateTime!
  updatedAt: AWSDateTime!
  teamProjectId: ID
}

input ModelStringInput {
  ne: String
  eq: String
  le: String
  lt: String
  ge: String
  gt: String
  contains: String
  notContains: String
  between: [String]
  beginsWith: String
  attributeExists: Boolean
  attributeType: ModelAttributeTypes
  size: ModelSizeInput
}

input ModelIntInput {
  ne: Int
  eq: Int
  le: Int
  lt: Int
  ge: Int
  gt: Int
  between: [Int]
  attributeExists: Boolean
  attributeType: ModelAttributeTypes
}

input ModelFloatInput {
  ne: Float
  eq: Float
  le: Float
  lt: Float
  ge: Float
  gt: Float
  between: [Float]
  attributeExists: Boolean
  attributeType: ModelAttributeTypes
}

input ModelBooleanInput {
  ne: Boolean
  eq: Boolean
  attributeExists: Boolean
  attributeType: ModelAttributeTypes
}

input ModelIDInput {
  ne: ID
  eq: ID
  le: ID
  lt: ID
  ge: ID
  gt: ID
  contains: ID
  notContains: ID
  between: [ID]
  beginsWith: ID
  attributeExists: Boolean
  attributeType: ModelAttributeTypes
  size: ModelSizeInput
}

enum ModelAttributeTypes {
  binary
  binarySet
  bool
  list
  map
  number
  numberSet
  string
  stringSet
  _null
}

input ModelSizeInput {
  ne: Int
  eq: Int
  le: Int
  lt: Int
  ge: Int
  gt: Int
  between: [Int]
}

enum ModelSortDirection {
  ASC
  DESC
}

type ModelProjectConnection {
  items: [Project]!
  nextToken: String
}

input ModelProjectFilterInput {
  id: ModelIDInput
  name: ModelStringInput
  and: [ModelProjectFilterInput]
  or: [ModelProjectFilterInput]
  not: ModelProjectFilterInput
  projectTeamId: ModelIDInput
}

type Query {
  getProject(id: ID!): Project
  listProjects(filter: ModelProjectFilterInput, limit: Int, nextToken: String): ModelProjectConnection
  getTeam(id: ID!): Team
  listTeams(filter: ModelTeamFilterInput, limit: Int, nextToken: String): ModelTeamConnection
}

input ModelProjectConditionInput {
  name: ModelStringInput
  and: [ModelProjectConditionInput]
  or: [ModelProjectConditionInput]
  not: ModelProjectConditionInput
  projectTeamId: ModelIDInput
}

input CreateProjectInput {
  id: ID
  name: String
  projectTeamId: ID
}

input UpdateProjectInput {
  id: ID!
  name: String
  projectTeamId: ID
}

input DeleteProjectInput {
  id: ID!
}

type Mutation {
  createProject(input: CreateProjectInput!, condition: ModelProjectConditionInput): Project
  updateProject(input: UpdateProjectInput!, condition: ModelProjectConditionInput): Project
  deleteProject(input: DeleteProjectInput!, condition: ModelProjectConditionInput): Project
  createTeam(input: CreateTeamInput!, condition: ModelTeamConditionInput): Team
  updateTeam(input: UpdateTeamInput!, condition: ModelTeamConditionInput): Team
  deleteTeam(input: DeleteTeamInput!, condition: ModelTeamConditionInput): Team
}

type Subscription {
  onCreateProject: Project @aws_subscribe(mutations: ["createProject"])
  onUpdateProject: Project @aws_subscribe(mutations: ["updateProject"])
  onDeleteProject: Project @aws_subscribe(mutations: ["deleteProject"])
  onCreateTeam: Team @aws_subscribe(mutations: ["createTeam"])
  onUpdateTeam: Team @aws_subscribe(mutations: ["updateTeam"])
  onDeleteTeam: Team @aws_subscribe(mutations: ["deleteTeam"])
}

type ModelTeamConnection {
  items: [Team]!
  nextToken: String
}

input ModelTeamFilterInput {
  id: ModelIDInput
  name: ModelStringInput
  and: [ModelTeamFilterInput]
  or: [ModelTeamFilterInput]
  not: ModelTeamFilterInput
  teamProjectId: ModelIDInput
}

input ModelTeamConditionInput {
  name: ModelStringInput
  and: [ModelTeamConditionInput]
  or: [ModelTeamConditionInput]
  not: ModelTeamConditionInput
  teamProjectId: ModelIDInput
}

input CreateTeamInput {
  id: ID
  name: String!
  teamProjectId: ID
}

input UpdateTeamInput {
  id: ID!
  name: String
  teamProjectId: ID
}

input DeleteTeamInput {
  id: ID!
}

GraphQL schema(s)

input AMPLIFY {
  globalAuthRule: AuthRule = { allow: public }
}

type Project @model {
  id: ID!
  name: String
  team: Team @hasOne
}

type Team @model {
  id: ID!
  name: String!
  project: Project @belongsTo
}

Log output
No response
Additional information
No response

Hi @bergmorten the hasOne <=> belongsTo relationship is slightly different than hasMany <=> belongsTo.
Using your schema as an example, here's what happens with @hasMany:
type Project @model {
  id: ID!
  name: String
  teams: [Team] @hasMany
}

type Team @model {
  id: ID!
  name: String!
  project: Project @belongsTo
}

In this case, Amplify will configure the Team records to have a projectTeamId field which stores the foreign key to the Project. A request for Project.teams will perform a query operation on the Team table looking for that project id. A request for Team.project will use the projectTeamId stored in the record to get the corresponding project record. Note that the Project records do not have any foreign key to Team records in this case. The Project record uses its own id when looking up Team records
Now let's look at your actual schema:
type Project @model {
  id: ID!
  name: String
  team: Team @hasOne
}

type Team @model {
  id: ID!
  name: String!
  project: Project @belongsTo
}

In this case, both the Project and Team records have a projectTeamId field that stores the foreign key to the other model. So for the bidirectional relationship to work, both records must have the id of the other set. This can be accomplished with the following mutation:
mutation MyMutation {
  createTeam(input: {id: "team-id-1", name: "my team", teamProjectId: "proj-id-1"}) {
    id
  }
  createProject(input: {id: "proj-id-1", name: "my proj", projectTeamId: "team-id-1"}) {
    id
  }
}

and tested with this query:
query MyQuery {
  getTeam(id: "team-id-1") {
    project {
      id
      name
      team {
        id
        name
      }
    }
  }
}

which returns:
{
  "data": {
    "getTeam": {
      "project": {
        "id": "proj-id-1",
        "name": "my proj",
        "team": {
          "id": "team-id-1",
          "name": "my team"
        }
      }
    }
  }
}

The underlying reason for this difference is @hasMany is using DynamoDB query operations under the hood whereas @hasOne is using DynamoDB getItem operations. The query operation is against a GSI that uses the Project id as an index. The getItem operation request the id of the record being queried.

@edwardfoyle  Then the both the documentation and example in the cli doc is wrong? https://docs.amplify.aws/cli/graphql/data-modeling/#belongs-to-relationship
Make a "has one" or "has many" relationship bi-directional with the @belongsTo directive.
From example in cli doc, it states that create project with a team, will return a team referring back to project.

mutation CreateProject {
  createProject(input: { name: "New Project", teamID: "a-team-id"}) {
    id
    name
    team { # query team from project
      id
      name
      project { # bi-directional query: team to project
        id
        name
      }
    }
  }
}

I am stuck in the same issue. seems the documentation is wrong or misleading?

@edwardfoyle  wanted to follow up here in case it got buried, is the documentation misleading or is there a way to set up a bidirectional 1:1 relationship where you can create model B and be able to query from model A without having to update A?

I'm having the same problem currently with the hasMany/belongsTo and hasOne/belongsTo, I can't query ítems from model B without having to update or query item A again.

Since this has been mentioned in multiple issues -
(here, here, here) - I am writing my workaround which is explained below:
Use Case
1. I want 1 Call to have exactly 1 Review (1:1 relationship).
2. E.g. when creating Review object, I do not want to also update Call object.
3. When querying Call objects, I want AppSync to auto populate Review object inside Call object.
4. When Review is deleted, Call object remains unchanged.
Workaround
The workaround is that the application layer is responsible for linking Call and Review objects by ID (Call ID needs to be the same as Review ID) // you would need to handle it on your own in your app logic.
Then - by using similar schema like this one - each AppSync operation should  give you the data you probably needed :
type Call @model  {
  id: ID!
  review: Review @hasOne(fields: ["id"])
}

type Review @model  {
  id: ID!
  rating: Int!
  call: Call @hasOne(fields: ["id"])
}

AppSync Results

Weak points
The only "maybe-problem" that I see when writing this comment could be during data deletion (e.g. if Call is deleted, the Review should be deleted too) - but this can be handled easily in your code, using DynamoDB streams, etc.

Why is this closed? I am also encountering this bug.


Forge test reports a huge gas number if vm.pauseGasMetering is in effect at the end of a test

Component
Forge
Have you ensured that all of these are up to date?

[X] Foundry
[X] Foundryup

What version of Foundry are you on?
forge 0.2.0 (0e33b3e 2023-07-28T00:23:39.362605000Z)
What command(s) is the bug in?
forge test
Operating System
macOS (Apple Silicon)
Describe the bug
If a test completes after calling vm.pauseGasMetering(), and without calling vm.resumeGasMetering(), it will report gas usage is exactly<PHONE_NUMBER>854754743 (2**63 - 21065?).
Minimal reproduction:
// SPDX-License-Identifier: MIT
pragma solidity ^0.8.17;

import {Test} from "forge-std/Test.sol";

contract PauseTest is Test {
    function testWeirdGas1() public {
        vm.pauseGasMetering();
    }

    function testWeirdGas2() public {
        uint256 a = 1;
        uint256 b = a + 1;
        require(b == 2, "b is not 2");
        vm.pauseGasMetering();
    }

    function testNormalGas() public {
        vm.pauseGasMetering();
        vm.resumeGasMetering();
    }
}

Output:
[⠰] Compiling...
[⠢] Compiling 1 files with 0.8.20
[⠰] Solc 0.8.20 finished in 729.32ms
Compiler run successful!

Running 3 tests for test/PauseTest.t.sol:PauseTest
[PASS] testNormalGas() (gas: 3179)
[PASS] testWeirdGas1() (gas:<PHONE_NUMBER>854754743)
[PASS] testWeirdGas2() (gas:<PHONE_NUMBER>854754743)
Test result: ok. 3 passed; 0 failed; 0 skipped; finished in 306.25µs
Ran 1 test suites: 3 tests passed, 0 failed, 0 skipped (3 total tests)

Related: https://github.com/foundry-rs/foundry/issues/4370


Upgrade to Foundry V11

hello, all my other games are up to date just pf2 arend, please fix this

How about a timeline for an eventual update to v11?


01 update bloat script to preserve at most 80 binary builds

Problem
Bloat report keeps 30 days work of binaries, however this consumes too much storage.
Summary of Changes
Try to adjust sizes to use a maximum count as well (this way we have a cap on storage)
fixes #2285

@hawk248 @saurabhst @jelderton ?


Does not compile under visual studio 2022

The wexflow.sln  does not compile.  It produces numerous errors and appears to be a mix of .net 4.8 and.net core projects.
How can i compile this with .net core only?

Did you set Any CPU in build configuration instead of Mixed Platform?

@TechyGuy99 I fixed some issues in Wexflow.sln and tested the compilation of the latest source code on the main branch on Visual Studio 2022 >= 17.8.0 and everything works fine on both .NET 4.8 and .NET 8.0.
Once you open Wexflow.sln, under src solution folder you have:

net solution folder which contains the source code of the .NET 4.8 version
netcore solution folder which contains the source code of the .NET 8.0 version (.NET Core)

You can compile with .NET Core only by compiling netcore solution folder only in Visual Studio 2022 >= 17.8.0.
For further information on how to run the solution from source code, check out this documentation.

@TechyGuy99 I fixed some issues in Wexflow.sln and tested the compilation of the latest source code on the main branch on Visual Studio 2022 >= 17.8.0 and everything works fine on both .NET 4.8 and .NET 8.0.
Once you open Wexflow.sln, under src solution folder you have:

net solution folder which contains the source code of the .NET 4.8 version
netcore solution folder which contains the source code of the .NET 8.0 version (.NET Core)

You can compile with .NET Core only by compiling netcore solution folder only in Visual Studio 2022 >= 17.8.0.
For further information on how to run the solution from source code, check out this documentation.

Ok, got latest and everything net core compiled. I  turned off the 4.8 and was fine.
Next, i added a workflow with zip files task. Not sure what i am supposed to enter in selected files. Seems to reject silently
and when debugging, i see no selectedFiles Value in the xml

You need to use FilesLoader task before Zip task to load the files you want to zip. Here is a sample Zip workflow: https://github.com/aelassas/wexflow/blob/main/samples/net/Wexflow/Workflows/Workflow_Zip.xml
In selectFiles you put the ID of the task that loads files: https://github.com/aelassas/wexflow/wiki/Getting-Started#how-tasks-communicate-between-each-other
You can find the doc of each task in the wiki.
For config files, you can change them as you want: https://github.com/aelassas/wexflow/wiki/Configuration


CocoaPod is not same version available on github

When I pull down from pod install I am not able to call validator.validateField because that function doesn't exist in the code the pod pulled down.

I checked and confirmed this as well. But is there any reason that you aren't using validator.validate? Calling this will call validator.validateAllFields which will, as its name suggests, validate all the fields registered to your validator.

Well certain fields I want to validate immediately when the user ends editing them. Seemed better to me at the time I was messing around with this to only validate the specific field they were working on instead of continuing to validate every field every time.

Understandable. I'm sure @jpotts18 will correct this when he sees it.

@davepatterson Is this something you can handle now that you are a collaborator?

@jpotts18 Definitely. I will tackle it tomorrow at the latest.

Awesome! When you are free let's set up a quick chat and lay out a roadmap for this project. My email is jeff.potter6[at]gmail.com add me and we can set up a hangout or facetime.

@jpotts18 Yep. My email is<EMAIL_ADDRESS>we will definitely chat soon. As for the fix, I added a tag (3.0.3) that is a copy of the master branch so it fixes the issue @AtheistP3ace was having. But unfortunately I am unable to push said tag to CocoaPods because I am not a contributor on the SwiftValidator pod.

This should be resolved now.

Thanks for the quick resolution! I'll give it a try later.

Same issue for me.

This is actually fixed in pod 3.0.3. Use pod 'SwiftValidator', '3.0.3' in your Podfile.


add a menu for open it by external program

in windows local desk mode. when selecting a file in file explorer of vsocde . please add a short cut menu for "open it by external program"
for example. my work space have some docx file . i want to open it by MS Word. that will be great to to have a menu to opn it.
also for linux /mac  desk mode.
and there are two potentialway

right click menu

select open it with then add a item name open it by extra program

not only for docx. but also any file type. please and thanks :dancers:

I believe that there was very useful for anybody using vs code. ah~


Fixed warning in README example

I just switched 'sys' to 'util' because 'sys' is deprecated.

Thanks


Makes writeValueRecursively iterative

The method _Private_IonWriterBase#writeValueRecursively is
recursive in two senses:

It visits all of the children in the provided IonReader's
current value recursively.
The method itself is implemented using recursion.

This patch modifies the implementation to be iterative,
eliminating a source of StackOverflowExceptions and offering
a modest reduction in CPU cost.
Benchmark
This benchmark creates an IonStruct that is 1,000 levels deep, wraps it in an IonReader, then uses writeValueRecursively to write it to a binary Ion stream 100k times. The source can be viewed here.
This change does not affect allocations or garbage collection, only CPU time.
Before
                                       Score           Error   Units
time                                1804.311 ±         7.401   ms/op
·gc.alloc.rate                      1089.760 ±         3.556  MB/sec
·gc.alloc.rate.norm<PHONE_NUMBER>.200 ±        70.340    B/op
·gc.churn.G1_Eden_Space             1092.004 ±        73.732  MB/sec
·gc.churn.G1_Eden_Space.norm<PHONE_NUMBER>.400 ± 180920323.756    B/op
·gc.churn.G1_Old_Gen                   0.171 ±         0.040  MB/sec
·gc.churn.G1_Old_Gen.norm         413110.400 ±     96520.541    B/op
·gc.count                            114.000                  counts
·gc.time                              83.000                      ms

After
                                       Score           Error   Units
time                                1735.452 ±        42.039   ms/op
·gc.alloc.rate                      1123.361 ±        21.138  MB/sec
·gc.alloc.rate.norm<PHONE_NUMBER>.000 ±         0.001    B/op
·gc.churn.G1_Eden_Space             1131.249 ±        89.896  MB/sec
·gc.churn.G1_Eden_Space.norm<PHONE_NUMBER>.200 ± 200798830.041    B/op
·gc.churn.G1_Old_Gen                   0.162 ±         0.046  MB/sec
·gc.churn.G1_Old_Gen.norm         380224.000 ±    112156.067    B/op
·gc.count                            105.000                  counts
·gc.time                              82.000                      ms

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Thank you for the detailed comments!


How to get the source route?

Can you please elaborate on your question? It isn't clear (to me at least) what you are referring to when you say "source route".

a page jumps to b page
In page b, how to get which page is jumping over
route.from?

Hi. From v0.1.13 you can use something like that:
const navigate = useNavigate();
const location = useLocation();

navigate('/some/path', { state: { prev: location.pathname } })

const location = useLocation<{ prev: string }>();
navigate(location.state?.prev || '/');

To avoid copy/paste you also can wrap this code into your own useNavigate and useLocation hooks.

I think this is a reasonable answer, that or the issue is stale. Closing it.


Vote delegation / vote weight - several optimizations

The vote delegation and vote weight feature needs some optimizations to be more user friendly. I will list the individual requirements below.
A) User Detail view lacks in a good overview layout, if a user has several vote delegations. Example image: The user has more than three vote delegations, but after three it is not possible to read them.

--> Solution: Voting delegations are shown in a numbered list below each other.
B) Participant list: The total amount of vote delegations is not readable.
--> Solution: The suitcase (red mark) should get a number with the total amount of vote delegations per user.
Image example which suitcase is meant:

C) Participant list: If a user has vote delegations, the total amount of vote weight is missing.
--> Solution: The gray vote weight information should be enhanced with information about the total amount of vote weights given per delegation. Example line "Vote weight: 1 plus (amount) voting weight from transferred votes."
Example which line is meant:

D) Participant list > Add new Filter 'Entitled to vote'.
The options for this filter should be 1.) 'is entitled to vote' and  2.)' is currently entitled to vote'.
E) Enhance information text in Participant list >  gray information text if filter in D is active.
If the new filter of D is active, there should be an information about how many rights to vote are given and the accumulated value for vote weights. This values should also change, if multiselection is used. The gray help text on the left side to filter and sort options should display' X of Y (Rights to vote 'value', accumulated vote weight 'value')'. Please take care, that this interacts with vote delegations. If a user has a vote delegation with a vote weight, this should also be accumulated.
Note: This information should only be displayed for the new filter. For all other scenarios the information should not be visible.
F) Visualization of vote weight in participant list needs to be improved and new help text for vote weight setting is needed
Current status: All person are displayed with vote weight 1, if the vote weight option in activated. This is irritating and not helpful, because not all users are entitled to vote.
Solution: The vote weight in the participant list should only be displayed for users which are in an entitled to vote group given by the settings of agenda, motions and elections. For all other users, which are not in a corresponding group, the vote weight should not be displayed. Additionally the vote weight setting should get a new help text: "The vote weight will only be shown in the participant list for participants which are in a default vote group".

After a discussion we decided the following, these are just additions to the descriptions:
A)
The menu should be a numbered list
The ten first delegations should always be displayed
If there are more than ten, then the eleventh (and upwards should be hidden/collapsed. The function should be list similar to a mat-expansion-panel or the comments/personal notes in a motion detail view)
B)
The number should be behind the delegation names
The number should only be displayed if there is an ellipse
The number describes the total amount of delegations
C)
The used string should be "Vote weigh: # + ##sum-of-delegations
The sum should be the total sum of delegations regardless of filters and settings
D)
The string "X of Y (vote weight: #)" should be changed to "X of Y (accumulated votes: #, accumulated vote weight: #)"
partly still in discussion:
either)
in the three dot menu is a checkbox which if activated changes the string
or)
There is a new filter
title:  'Entitled to vote'.
two option:  'is entitled to vote' and 'is currently entitled to vote'
'is entitled to vote' only activates the string display
'is currently entitled to vote' activates the string and filters like "is present" does
E)
Information text: "X of Y (accumulated votes: #, accumulated vote weight: #)"
"X of Y" stays as it is
"accumulated votes: #" ==> is the sum of unique votes which could be submitted by everyone in the list
"accumulated vote weight: #" ==> is the sum of all the unique votes from the accumulated votes
(meaning that if a principal and their proxy are in the list then the vote of the principal is only counted once and not twice)
F)
vote weight should be hidden (participant-list and participant-detail) if a participant is is none of the default poll groups


Is there a possibility to log a StackOverflowException?

I have a Service Fabric Application running. Yesterday I had performance impacts and found a console output which informs about a StackOverflowException but I couldn't find any stack trace or something more. AppInsights and ServiceFabric were both green.
So I took one memory dump after another and looked into the last one before the process goes down. Then it was no problem finding the problem.
Is there a possibility to configure AppInsights to log a StackOverflowExceptoin and create a dump in this case?

Apart from offering TrackException API to log any exception, there is no feature provided by this SDK to auto-trigger process dump.

Apart from offering TrackException API to log any exception, there is no feature provided by this SDK to auto-trigger process dump.


Update docs to mention support of Flink 1.19

:mag: Description
Issue References 🔗

Kyuubi actually supports Flink 1.19 since 1.9.0, the docs are outdated.
Describe Your Solution 🔧
Update docs
Types of changes :bookmark:

[x] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Test Plan 🧪
Review

Checklist 📝

[x] This patch was not authored or co-authored using Generative Tooling

Be nice. Be informative.

Merged to master/1.9


Multiple keys problem

I've been trying to use multiple keys in Cradle.
I use this query with an HTTP request and it brings me the results I expected:
gps_map/_design/carros/_view/teste?startkey=[353451044222222]&endkey=[353451044222222,{}]&limit=50

I tried to reach the same results with Cradle:
var car =<PHONE_NUMBER>22222;
db.view('carros/teste',{limit:50,startkey:[car],endkey:[car,{}]},function(err,res)

or
var car =<PHONE_NUMBER>22222,
     start = [],
     end = [car,{}];
start[0] = car;
db.view('carros/teste',{startkey:start,endkey:end,limit:50},function(err,res)

Some guys on Nodejs mailing list told me that this code should work, but It doesn't.

looks broken to me, i submit the following
,,,
{
start_key: [ 'acb2936dfcea47c119d8e7c645c7a88f',<PHONE_NUMBER>569 ],
end_key: [ 'acb2936dfcea47c119d8e7c645c7a88f' ]
}
and this is whats generated
,,,
_view/active?start_key=acb2936dfcea47c119d8e7c645c7a88f&start_key=1328281453261&end_key=acb2936dfcea47c119d8e7c645c7a88f

need to use 'startkey' and 'endkey' no underscore!
Even though it is 'start_key' and 'end_key' in the couched request.

Stunbled upon this issue today... still open ? No clues about solving it or using a workaround ?
As far as I can tell, Cradle escapes parameters' value a tad too much:
endkey : ["bar", {}] becomes &endkey=%5B%22bar%22%2C%7B%7D%5D

I gave up Cradle and used a raw http request
-- Victor Debone
2012/2/14 lmoran <
<EMAIL_ADDRESS>

Stunbled upon this issue today... still open ? No clues about solving it
or using a workaround ?
As far as I can tell, Cradle escapes parameters' value a tad too much:
endkey : ["bar", {}] becomes &endkey=%5B%22bar%22%2C%7B%7D%5D

Reply to this email directly or view it on GitHub:
https://github.com/cloudhead/cradle/issues/129#issuecomment-3964920

All: You need to use startkey and endkey not start_key or end_key


I want to add  another window when video call is ongoing for seeing my own when video is  ongoing what steps I have to do for that?

This is already implemented in Step 3 of the codelab. There are two separate videoviews, remote and local.

Hii I am using mqtt with webrtc ,DO u know what needs to be done?I am so
stuck in there
Richa Shah
Android Developer
email<EMAIL_ADDRESS>On Wed, Apr 1, 2020 at 2:04 PM Asrar<EMAIL_ADDRESS>wrote:

This is already implemented in Step 3 of the codelab. There are two
separate videoviews, remote and local.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/vivek1794/webrtc-android-codelab/issues/43#issuecomment-607112803,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEA54E22YWDPQBHUHZWZNBDRKL4CXANCNFSM4LLYRL6A
.

You are presumably using MQTT protocol for signaling (handshaking). I don't have any experience in this protocol but the problem that you are stating about adding the local videoview for your own local camera feed will be the same for any implementation of video calling app with webrtc it won't depend on the protocol you are using for signaling. I am using firebase for signaling and the entire implementation remains the same other than the signaling part.
You only have to change the SignallingClient class to fit your medium for handshaking (exchange of offer and answer), that's it other things remain the same.
If you're going to use the Xirsys turn server just letting you know that the API call to get the Ice servers is asynchronous so you should start the process after there is an API response otherwise the turn servers are never used. I was stuck here for some time.

okay thank you, for now, I am using ice server provided by google but
thanks for the info :)
Richa Shah
Android Developer | Smart Sense
email<EMAIL_ADDRESS>On Wed, Apr 1, 2020 at 3:21 PM Asrar<EMAIL_ADDRESS>wrote:

You are presumably using MQTT protocol for signaling (handshaking). I
don't have any experience in this protocol but the problem that you are
stating about adding the local videoview for your own local camera feed
will be the same for any implementation of video calling app with webrtc
it won't depend on the protocol you are using for signaling. I am using
firebase for signaling and the entire implementation remains the same
other than the signaling part.
You only have to change the SignallingClient class to fit your medium for
handshaking (exchange of offer and answer), that's it other things remain
the same.
If you're going to use the Xirsys turn server just letting you know that
the API call to get the Ice servers is asynchronous so you should start the
process after there is an API response otherwise the turn servers are never
used.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/vivek1794/webrtc-android-codelab/issues/43#issuecomment-607151252,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEA54E465RNCPO2CBG7KRRTRKMFBHANCNFSM4LLYRL6A
.

Hii Another thing I wanna ask u, I have a video calling app where I also
have taken only one PeerConnection obj and applied custom observer just
like u did ? is it req for me to take two object for streaming on both?
using mqtt
Richa Shah
Android Developer | Smart Sense
phone:<PHONE_NUMBER> <09016804343>
email<EMAIL_ADDRESS>On Wed, Apr 1, 2020 at 6:09 PM richa shah<EMAIL_ADDRESS>wrote:

okay thank you, for now, I am using ice server provided by google but
thanks for the info :)
Richa Shah
Android Developer | Smart Sense
email<EMAIL_ADDRESS>On Wed, Apr 1, 2020 at 3:21 PM Asrar<EMAIL_ADDRESS>wrote:

You are presumably using MQTT protocol for signaling (handshaking). I
don't have any experience in this protocol but the problem that you are
stating about adding the local videoview for your own local camera feed
will be the same for any implementation of video calling app with webrtc
it won't depend on the protocol you are using for signaling. I am using
firebase for signaling and the entire implementation remains the same
other than the signaling part.
You only have to change the SignallingClient class to fit your medium for
handshaking (exchange of offer and answer), that's it other things remain
the same.
If you're going to use the Xirsys turn server just letting you know that
the API call to get the Ice servers is asynchronous so you should start the
process after there is an API response otherwise the turn servers are never
used.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/vivek1794/webrtc-android-codelab/issues/43#issuecomment-607151252,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEA54E465RNCPO2CBG7KRRTRKMFBHANCNFSM4LLYRL6A
.

The number of PeerConnection objects on a single device serving as a single peer will depend on how many connections it is having with other peers. So if there are n devices connected to a single RTC connection there will be n-1 objects of PeerConnection on a single device that is connected to all n of them.
In simpler words, you have to make a new object for every new connection.
I have never implemented more than a 2-way communication, never needed it. I read the above info somewhere, so please confirm all this before trusting me blindly, but I am pretty sure about it.
Finally, I'm sorry to have you go through my code, it's a mess :(.

Okay , thank you :) and no problem
Richa Shah
Android Developer | Smart Sense
phone:<PHONE_NUMBER> <09016804343>
email<EMAIL_ADDRESS>On Sat, Apr 4, 2020 at 3:39 AM Asrar<EMAIL_ADDRESS>wrote:

The number of PeerConnection objects on a single device serving as a
single peer will depend on how many connections it is having with other
peers. So if there are n devices connected to a single RTC connection there
will be n-1 objects of PeerConnection on a single device that is
connected to all n of them.
In simpler words, you have to make a new object for every new connection.
I have never implemented more than a 2-way communication, never needed
it. I read the above info somewhere, so please confirm all this before
trusting me blindly, but I am pretty sure about it.
Finally, I'm sorry to have you go through my code, it's a mess :(.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/vivek1794/webrtc-android-codelab/issues/43#issuecomment-608710302,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEA54E64KSJGLQOCN2QC3VTRKZNCPANCNFSM4LLYRL6A
.

Hii about using turn server I need more clarification , everything is
working fine for me between android to android using google stun server but
unfortunately it's not working with ios in proper way .it goes to checking
mode.so can u provide me any proper sever details u come across or just
asking tht using turn server its working on all kind devices ?
Richa Shah
Android Developer | Smart Sense
email<EMAIL_ADDRESS>On Wed, Apr 1, 2020 at 3:21 PM Asrar<EMAIL_ADDRESS>wrote:

You are presumably using MQTT protocol for signaling (handshaking). I
don't have any experience in this protocol but the problem that you are
stating about adding the local videoview for your own local camera feed
will be the same for any implementation of video calling app with webrtc
it won't depend on the protocol you are using for signaling. I am using
firebase for signaling and the entire implementation remains the same
other than the signaling part.
You only have to change the SignallingClient class to fit your medium for
handshaking (exchange of offer and answer), that's it other things remain
the same.
If you're going to use the Xirsys turn server just letting you know that
the API call to get the Ice servers is asynchronous so you should start the
process after there is an API response otherwise the turn servers are never
used.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/vivek1794/webrtc-android-codelab/issues/43#issuecomment-607151252,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEA54E465RNCPO2CBG7KRRTRKMFBHANCNFSM4LLYRL6A
.


Update keyboard_layout_id.h

fix comment
Description
A clear and concise description of this pull request.
Issue IDs
Issue and/or discussion IDs related to this pull request.
Modified code locations
Files/directories of this pull request.
(e.g. src/data/oss/aux_dictionary.tsv, src/renderer/qt/)
Confirmation of the acceptable code locations
Check https://github.com/google/mozc/blob/master/CONTRIBUTING.md and
confirm whether all modified files are acceptable for pull requests.
"Yes" or "No"
If the answer is "No", instead of this PR, please file an issue at
https://github.com/google/mozc/issues with your investigations.
Steps to test new behaviors (if any)
A clear and concise description about how to verify new behaviors (if any).

OS: [e.g. Windows 11, macOS 13.1, etc]
Steps:

...
...
Confirm ...

Additional context
Add any other context about the pull request here.

Hi DJm00n,
Thank you for your PR. It looks good to me. We will merge the PR.
In parallel, would you update Description, Modified code locations and Confirmation of the acceptable code locations for future reference? Other items (i.e. Issue IDs) can be "N/A" for this PR.
Best,

@hiroyuki-komatsu done

We have merged this PR.
Thank you for your contribution!


17track.net / Seventeentrack Sensor - Two Different Errors / Issues - 0.83.0 Hassbian - Somewhat related to #18670

Home Assistant release with the issue:

0.83.0

Last working Home Assistant release (if known):
n/a, just introduced in 0.83.0
Operating environment (Hass.io/Docker/Windows/etc.):

Hassbian on Raspberry Pi3 Model B

Component/platform:

17track.net

Description of problem:
Upon updating to the 0.83.0 release of Home Assistant I added the 17track.net sensor to my configuration and restarted Home Assistant. Two separate issues occurred:

[ ] Prior to adding any tracking numbers to my 17track.net account at https://buyer.17track.net the sensors were created and the component would successfully load and display in my XX components loaded view in the dev-info view of Home Assistant. This is how I obtained the sensor entity IDs I added to my groups.yaml file that I added here.

[ ] Once I added packages with valid tracking numbers to my 17track.net dashboard at https://buyer.17track.net I did not see any updates to my frontend so I restarted the Home Assistant service and the 17track.net component no longer loads. I receive the traceback log that I have included below.

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
- platform: seventeentrack
  username: !secret seventeentrackemail
  password: !secret seventeentrackpassword

More here
Relevant Entities in my groups.yaml

    - sensor.packages_in_transit_2
    - sensor.packages_ready_to_be_picked_up
    - sensor.packages_not_found
    - sensor.packages_ready_to_be_picked_up

Traceback (if applicable):
Error while setting up platform seventeentrack
Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.5/site-packages/homeassistant/helpers/entity_platform.py", line 128, in _async_setup_platform
    SLOW_SETUP_MAX_WAIT, loop=hass.loop)
  File "/usr/lib/python3.5/asyncio/tasks.py", line 400, in wait_for
    return fut.result()
  File "/usr/lib/python3.5/asyncio/futures.py", line 293, in result
    raise self._exception
  File "/usr/lib/python3.5/asyncio/tasks.py", line 239, in _step
    result = coro.send(None)
  File "/srv/homeassistant/lib/python3.5/site-packages/homeassistant/components/sensor/seventeentrack.py", line 78, in async_setup_platform
    await data.async_update()
  File "/srv/homeassistant/lib/python3.5/site-packages/homeassistant/components/sensor/seventeentrack.py", line 263, in _async_update
    show_archived=self._show_archived)
  File "/srv/homeassistant/lib/python3.5/site-packages/py17track/profile.py", line 79, in packages
    packages.append(Package(package['FTrackNo'], **kwargs))
  File "<attrs generated init 1e2f778bb8606af2ada9f0ca9f47be0bba6741c6>", line 10, in __init__
    self.__attrs_post_init__()
  File "/srv/homeassistant/lib/python3.5/site-packages/py17track/package.py", line 272, in __attrs_post_init__
    self.package_type = PACKAGE_TYPE_MAP[self.package_type]
KeyError: 'CHICAGO, IL 60640'

Additional information:

Seems somewhat related to https://github.com/home-assistant/home-assistant/issues/18670. However, the component did successfully load and display in Home Assistant prior to me adding my valid tracking numbers to my https://buyer.17track.net/ dashboard.

CC: https://github.com/brianjking/homeassistant-config/issues/161

Duplicate of #18670.


Write a 'push_repo' script

This script will initialize and push an existing local repository to a newly created remote repository of the same name.

Hi @sahil-sagwekar2652. I would like to work on this issue as a GSSOC'23 participant. Can you please assign it to me?

Hello @shubham-deshmukh , thank you for showing interest in this project. You can join our slack server for further discussions -
https://join.slack.com/t/githubautomat-9t49360/shared_invite/zt-1v05p5kao-UBmelVfZd6EBjGuzd_6XYg

Hey @sahil-sagwekar2652 assign me this issue.
I can make changes so that the script takes the --path argument, which represents the path to the existing local repository. It initializes the local repository, creates a new remote repository with the same name, and pushes the changes to the remote repository.

@sahil-sagwekar2652 Does this involve writing a python script using selenium for pushing local file's to a remote github repo?

Hey everyone, great to see you all here.
The program managers for GSSoC'23 will be creating discord channels for each project.
So we will eventually have to move out discussions to the GSSoC discord server. Also, we haven't received any information about how we are going to track the contributions,
so till then I won't be able to merge your PRs. And just a quick reminder - We are all here to learn and grow so don't try to rush anything, let us discuss the ideas, take inputs and
then start the actual coding. Cutting with a sharpened axe is much easier.

I would like to work on the issue

Please assign me this issue so that I can resolve it under GSSOC-23

Hey everyone, the issues are being assigned on a first-come-first-serve basis. In the meanwhile, checkout the other issues, or feel free to create your own. Also, don't make a PR without raising an issue and getting it assigned to you.

@sahil-sagwekar2652 Thank you for assigning me this task/issue.

Hey @sahil-sagwekar2652
I want to provide an update on the task/issue #3.
As per my understanding,
the ask is Initialize and push an existing local repository to a newly created remote repository of the same name.

Objective:

Initialize the directory as local repo if it does not exist
Push the local repository to the newly created remote repository

Algorithm:
Arguments: {path of the directory, URL of newly created remote repo of the same name}

Validate Arguments :

If an invalid directory path
1. print (error)
2. exit
If an invalid remote repo URL
1. print (error)
2. exit
If inconsistency with the local repo name with the newly created remote repo name
1. print (error)
2. exit

If not a local repo

initialize the directory as local repo

Push the existing local repo (including all branches, tags, etc.) to the newly created remote repo.

Please provide your valuable feedback including other contributors.


Create dgbcombine.py

@hpratama , I have compiled a detailed gist along with codes on the first steps which include setting up the train function in dgbpy.dgbscikit  to first of all handle training with multiple chunks and multiple folds. You can get ideas from this to help with your implementation.
You can find it - here

Please rebase, and I can do a QC again


[Bug] Fix Unknown command-line option '--tag'.

Is there an existing issue for this?

[X] I have searched the existing issues

What product(s) are you seeing the problem on?
Sage Monorepo
Current behavior
This issue originates from #2089.
Expected behavior
No response
Anything else?
No response
Commit ID
No response
Are you developing inside the dev container?

[x] #2092

Code of Conduct

[X] I agree to follow this project's Code of Conduct

I thought that this PR implemented filtering for affected but it seems that it only did it for run-many.

The error is:
$ nx affected --tag=language:java --target=prepare --parallel=1

nx run openchallenges-challenge-service:prepare
       Unknown command-line option '--tag'.

       USAGE: gradlew [option...] [task...]

       -?, -h, --help                     Shows this help message.
       -a, --no-rebuild                   Do not rebuild project dependencies.
       -b, --build-file                   Specify the build file. [deprecated]
       --build-cache                      Enables the Gradle build cache. Gradle will try to reuse outputs from previous builds.
       --no-build-cache                   Disables the Gradle build cache.
       -c, --settings-file                Specify the settings file. [deprecated]
       --configuration-cache              Enables the configuration cache. Gradle will try to reuse the build configuration from previous builds.
       --no-configuration-cache           Disables the configuration cache.
       --configuration-cache-problems     Configures how the configuration cache handles problems (fail or warn). Defaults to fail.
       --configure-on-demand              Configure necessary projects only. Gradle will attempt to reduce configuration time for large multi-project builds. [incubating]
       --no-configure-on-demand           Disables the use of configuration on demand. [incubating]
       --console                          Specifies which type of console output to generate. Values are 'plain', 'auto' (default), 'rich' or 'verbose'.
       --continue                         Continue task execution after a task failure.
       --no-continue                      Stop task execution after a task failure.
       -D, --system-prop                  Set system property of the JVM (e.g. -Dmyprop=myvalue).
       -d, --debug                        Log in debug mode (includes normal stacktrace).
       --daemon                           Uses the Gradle daemon to run the build. Starts the daemon if not running.
       --no-daemon                        Do not use the Gradle daemon to run the build. Useful occasionally if you have configured Gradle to always run with the daemon by default.
       --export-keys                      Exports the public keys used for dependency verification.
       -F, --dependency-verification      Configures the dependency verification mode. Values are 'strict', 'lenient' or 'off'.
       --foreground                       Starts the Gradle daemon in the foreground.
       -g, --gradle-user-home             Specifies the Gradle user home directory. Defaults to ~/.gradle
       -I, --init-script                  Specify an initialization script.
       -i, --info                         Set log level to info.
       --include-build                    Include the specified build in the composite.
       -M, --write-verification-metadata  Generates checksums for dependencies used in the project (comma-separated list)
       -m, --dry-run                      Run the builds with all task actions disabled.
       --max-workers                      Configure the number of concurrent workers Gradle is allowed to use.
       --offline                          Execute the build without accessing network resources.
       -P, --project-prop                 Set project property for the build script (e.g. -Pmyprop=myvalue).
       -p, --project-dir                  Specifies the start directory for Gradle. Defaults to current directory.
       --parallel                         Build projects in parallel. Gradle will attempt to determine the optimal number of executor threads to use.
       --no-parallel                      Disables parallel execution to build projects.
       --priority                         Specifies the scheduling priority for the Gradle daemon and all processes launched by it. Values are 'normal' (default) or 'low'
       --profile                          Profile build execution time and generates a report in the <build_dir>/reports/profile directory.
       --project-cache-dir                Specify the project-specific cache directory. Defaults to .gradle in the root project directory.
       -q, --quiet                        Log errors only.
       --refresh-keys                     Refresh the public keys used for dependency verification.
       --rerun-tasks                      Ignore previously cached task results.
       -S, --full-stacktrace              Print out the full (very verbose) stacktrace for all exceptions.
       -s, --stacktrace                   Print out the stacktrace for all exceptions.
       --scan                             Creates a build scan. Gradle will emit a warning if the build scan plugin has not been applied. (https://gradle.com/build-scans)
       --no-scan                          Disables the creation of a build scan. For more information about build scans, please visit https://gradle.com/build-scans.
       --status                           Shows status of running and recently stopped Gradle daemon(s).
       --stop                             Stops the Gradle daemon if it is running.
       -t, --continuous                   Enables continuous build. Gradle does not exit and will re-execute tasks when task file inputs change.
       -U, --refresh-dependencies         Refresh the state of dependencies.
       --update-locks                     Perform a partial update of the dependency lock, letting passed in module notations change version. [incubating]
       -V, --show-version                 Print version info and continue.
       -v, --version                      Print version info and exit.
       -w, --warn                         Set log level to warn.
       --warning-mode                     Specifies which mode of warnings to generate. Values are 'all', 'fail', 'summary'(default) or 'none'
       --watch-fs                         Enables watching the file system for changes, allowing data about the file system to be re-used for the next build.
       --no-watch-fs                      Disables watching the file system.
       --write-locks                      Persists dependency resolution for locked configurations, ignoring existing locking information if it exists
       -x, --exclude-task                 Specify a task to be excluded from execution.
       --                                 Signals the end of built-in options. Gradle parses subsequent parameters as only tasks or task options.

       Warning: run-commands command "./gradlew --version 1> /dev/null --tag=language:java" exited with non-zero status code

A solution seems to be to use --include and --exclude:
  nx affected --target=prepare --exclude '!tag:language:java' --parallel=1
  nx affected --target=prepare --exclude 'tag:language:java'


Add helpers & refactor older hints

TITLE
Description
Description of the pull request changes and motivation.
Checklist

[ ] Linked to Github Issue
[ ] Unit tests added
[ ] Integration tests added.
[ ] This change requires new documentation.

[ ] Documentation has been added/updated.

Codecov Report

Merging #331 (1e0ecf3) into main (daaca31) will increase coverage by 1.02%.
The diff coverage is 94.88%.

@@            Coverage Diff             @@
##             main     #331      +/-   ##
==========================================
+ Coverage   97.05%   98.08%   +1.02%
==========================================
  Files          39       40       +1
  Lines       13808    13124     -684
==========================================
- Hits        13402    12873     -529
+ Misses        406      251     -155

Impacted Files
Coverage Δ

src/vm/hints/execute_hint.rs
100.00% <ø> (ø)

src/vm/hints/math_utils.rs
99.70% <ø> (ø)

src/types/relocatable.rs
95.25% <64.70%> (-2.21%)
:arrow_down:

src/vm/hints/hint_utils.rs
88.54% <84.70%> (+4.11%)
:arrow_up:

src/vm/hints/find_element_hint.rs
98.42% <93.15%> (+0.97%)
:arrow_up:

src/vm/hints/keccak_utils.rs
95.65% <95.00%> (+0.47%)
:arrow_up:

src/vm/hints/squash_dict_utils.rs
99.90% <98.71%> (+1.58%)
:arrow_up:

src/types/exec_scope.rs
97.75% <100.00%> (+0.05%)
:arrow_up:

src/vm/hints/blake2s_utils.rs
99.00% <100.00%> (+0.01%)
:arrow_up:

src/vm/hints/dict_hint_utils.rs
100.00% <100.00%> (+3.32%)
:arrow_up:

... and 10 more

Help us with your feedback. Take ten seconds to tell us how you rate us.


⚠ Topfarmacia has degraded performance

In f301685, Topfarmacia (https://www.topfarmacia.it) experienced degraded performance:

HTTP code: 200
Response time: 20934 ms

Resolved: Topfarmacia performance has improved in 3ec466d.


Post previews

Related issue: https://github.com/rla/blog-core/issues/104
Preview urls are possibly going to be defined with an API like:
bc_register_preview_url(EntryType, '/page/entry/%s').

When URL is registered for the type then the Preview button will be shown in the entry edit view.

Backend code for this has been implemented. The Preview button appears to be nontrivial as opening and controlling new windows/tabs is severely restricted on browsers.


testkube-operator-controller-manager proxy container image doesn't support arm64

Describe the bug
kubebuilder/kube-rbac-proxy:v0.8.0 doesn't support arm64 (support was added on v2.0.1 according to this. When testkube-operator-controller-manager runs in an arm64 node, it stays in crashloopbackoff state with exec user process caused "exec format error" error message.
To Reproduce
Steps to reproduce the behavior:

deploy a testkube-operator in a cluster with only arm64 nodes without changing any of the defaults values.

Expected behavior
to have testkube-operator-controller-manager running fine in an arm64 node.
Version / Cluster

Which testkube version? testkube-operator-1.16.11
What Kubernetes cluster? EKS
What Kubernetes version? 1.27

Screenshots
Additional context
Add any other context about the problem here.

thank you @maxforasteiro pinging @ypoplavs


Could not create SecurityManager: worker.org.gradle.process.internal.worker.child.BootstrapSecurityManager

We have been getting the following stack trace when the :test task gets executed:
Error occurred during initialization of VM
java.lang.InternalError: Could not create SecurityManager: worker.org.gradle.process.internal.worker.child.BootstrapSecurityManager
	at sun.misc.Launcher.<init>(Launcher.java:106)
	at sun.misc.Launcher.<clinit>(Launcher.java:57)
	at java.lang.ClassLoader.initSystemClassLoader(ClassLoader.java:1448)
	at java.lang.ClassLoader.getSystemClassLoader(ClassLoader.java:1433)

Could not write standard input to Gradle Test Executor 2.
java.io.IOException: Broken pipe
	at java.io.FileOutputStream.writeBytes(Native Method)
	at java.io.FileOutputStream.write(FileOutputStream.java:326)
	at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)
	at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140)
	at org.gradle.process.internal.streams.ExecOutputHandleRunner.forwardContent(ExecOutputHandleRunner.java:66)
	at org.gradle.process.internal.streams.ExecOutputHandleRunner.run(ExecOutputHandleRunner.java:51)
	at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:63)
	at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:46)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:55)
	at java.lang.Thread.run(Thread.java:745)
:test FAILED

FAILURE: Build failed with an exception

Expected Behavior
Test suite should be initialized without issues and build should go fine. On local enviroments it is working as expected
Current Behavior
Getting exception each time the test task gets executed, the only way the test task passes is if we comment out all the test classes. Even a dummy test class with assert true will break the build.
we have tried with spock, junit and testNG and all give the same exception even with dummy test classes.
Context
We have tried already by deleting the .gradle/caches folder and still no luck.
We also tried by overriding the SecurityManager and it still gave the same exception.
Our theory is that the gradle-worker.jar generated by :compileGroovy task is not working as expected.
As a note, if we skip the tests and build the app, it works fine and as expected, its only the test task which seems to be failing.
Your Environment
The build is being done with Jenkins in a LINUX slave server with Java 8, grails 3 and groovy.
Gradle being used is 4.6 but we had tried also with 3.5 and is the same error.

Thanks for reporting. I suggest you to do as follows:

Run your tasks/params with extra --info, e.g. gradle test --info
You'll find the line Starting process 'Gradle Test Executor X'. Working directory: XXX Command: XXX

In my machine it looks like this:
/Library/Java/JavaVirtualMachines/jdk1.8.0_121.jdk/Contents/Home/bin/java -Djava.security.manager=worker.org.gradle.process.internal.worker.child.BootstrapSecurityManager -Djunit.version=4.12 -Dorg.gradle.native=false -Dfile.encoding=UTF-8 -Duser.country=US -Duser.language=en -Duser.variant -ea -cp /Users/zhb/.gradle/caches/4.5/workerMain/gradle-worker.jar worker.org.gradle.process.internal.worker.GradleWorkerMain 'Gradle Test Executor 3'

Note the -cp /Users/zhb/.gradle/caches/4.5/workerMain/gradle-worker.jar worker.org.gradle.process.internal.worker.GradleWorkerMain part.
Check if the <HOME>/.gradle/caches/4.5/workerMain/gradle-worker.jar exists. If not, try to delete the whole <HOME>/.gradle/caches/4.5 as a workaround.
The detail of this bug is still not clear, if you could provide us with a minimum reproducible sample that would be great.

hi @blindpirate
I added the --info argument to the build and this is what we get:
Task ':test' is not up-to-date because:
  Task has failed previously.
Starting process 'Gradle Test Executor 2'. Working directory: /srv/jenkins_linux_workspace/workspace/projectName Command: /usr/local/java/versions/jdk1.8.0_65/bin/java -Dgrails.env=test -Dgrails.full.stacktrace -Dinfo.app.grailsVersion=3.3.0 -Dinfo.app.name=LDAPIServices -Dinfo.app.version=0.1 -Djava.security.manager=worker.org.gradle.process.internal.worker.child.BootstrapSecurityManager -Dorg.gradle.native=false -XX:+TieredCompilation -XX:TieredStopAtLevel=1 -XX:CICompilerCount=3 "-XX:-UseSplitVerifier -Xverify:none" -XX:-UseSplitVerifier -Xverify:none -Xms512m -Xmx1024m -Dfile.encoding=UTF-8 -Duser.country=US -Duser.language=en -Duser.variant -ea -cp /home/pebuild/.gradle/caches/4.6/workerMain/gradle-worker.jar worker.org.gradle.process.internal.worker.GradleWorkerMain 'Gradle Test Executor 2'
Successfully started process 'Gradle Test Executor 2'
Error occurred during initialization of VM
java.lang.InternalError: Could not create SecurityManager: worker.org.gradle.process.internal.worker.child.BootstrapSecurityManager
	at sun.misc.Launcher.<init>(Launcher.java:106)
	at sun.misc.Launcher.<clinit>(Launcher.java:57)
	at java.lang.ClassLoader.initSystemClassLoader(ClassLoader.java:1448)
	at java.lang.ClassLoader.getSystemClassLoader(ClassLoader.java:1433)

Could not write standard input to Gradle Test Executor 2.
java.io.IOException: Broken pipe
	at java.io.FileOutputStream.writeBytes(Native Method)
	at java.io.FileOutputStream.write(FileOutputStream.java:326)
	at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)
	at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140)
	at org.gradle.process.internal.streams.ExecOutputHandleRunner.forwardContent(ExecOutputHandleRunner.java:66)
	at org.gradle.process.internal.streams.ExecOutputHandleRunner.run(ExecOutputHandleRunner.java:51)
	at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:63)
	at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:46)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:55)
	at java.lang.Thread.run(Thread.java:745)
:test FAILED
:test (Thread[Task worker for ':',5,main]) completed. Took 1.416 secs.

maybe the jenkins user does not have permissons to copy inside the build server?
I did verify tath the gradle-worker.jar exists and it it, i even deleted and it gets automatically created again during :compileGroovy task.
we have trying by deleting the caches folder but not the whole path for .gradle

we have not been able to replicate the issue on our locals :(

I'm seeing this error intermittently on my local machine which is Mac OS X High Sierra.
Happens with both Gradle 4.6 and Gradle 4.7.
I see it most frequently after I remove the ~/.gradle/caches directory to refresh all libraries and then run gradle test, something like:
$ rm -rf ~/.gradle/caches; ./gradlew test
Running gradle test immediately after getting this error results in success.

More details:
This happens almost every time I refresh the cache.
I am using Gradle 4.7 with the Junit 5 Jupiter engine tests enabled via:
test {
useJunitPlatform()
}

@tsgautier Thanks for the information, I've already reproduced it. I'll investigate it.

I think you need to kill the daemon after clearing the caches - then everything works fine again.

I had forgotten to updated this issue...
So, basically, after a month of debugging, the issue was that on the jenkins job of the build there were some parameters being passed to the vm that were making the gradle tests to crash.
GRAILS_OPTS="-XX:-UseSplitVerifier -Xverify:none"
we removed that

I suggest running ./gradlew --stop (if you're running gradle wrapper from your local project) or gradle --stop
That will stop the running daemon and should allow you to run the commands you need

We have been getting the following stack trace when the :test task gets executed:
Error occurred during initialization of VM
java.lang.InternalError: Could not create SecurityManager: worker.org.gradle.process.internal.worker.child.BootstrapSecurityManager
	at sun.misc.Launcher.<init>(Launcher.java:106)
	at sun.misc.Launcher.<clinit>(Launcher.java:57)
	at java.lang.ClassLoader.initSystemClassLoader(ClassLoader.java:1448)
	at java.lang.ClassLoader.getSystemClassLoader(ClassLoader.java:1433)

Could not write standard input to Gradle Test Executor 2.
java.io.IOException: Broken pipe
	at java.io.FileOutputStream.writeBytes(Native Method)
	at java.io.FileOutputStream.write(FileOutputStream.java:326)
	at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)
	at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140)
	at org.gradle.process.internal.streams.ExecOutputHandleRunner.forwardContent(ExecOutputHandleRunner.java:66)
	at org.gradle.process.internal.streams.ExecOutputHandleRunner.run(ExecOutputHandleRunner.java:51)
	at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:63)
	at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:46)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:55)
	at java.lang.Thread.run(Thread.java:745)
:test FAILED

FAILURE: Build failed with an exception

Expected Behavior
Test suite should be initialized without issues and build should go fine. On local enviroments it is working as expected
Current Behavior
Getting exception each time the test task gets executed, the only way the test task passes is if we comment out all the test classes. Even a dummy test class with assert true will break the build.
we have tried with spock, junit and testNG and all give the same exception even with dummy test classes.
Context
We have tried already by deleting the .gradle/caches folder and still no luck.
We also tried by overriding the SecurityManager and it still gave the same exception.
Our theory is that the gradle-worker.jar generated by :compileGroovy task is not working as expected.
As a note, if we skip the tests and build the app, it works fine and as expected, its only the test task which seems to be failing.
Your Environment
The build is being done with Jenkins in a LINUX slave server with Java 8, grails 3 and groovy.
Gradle being used is 4.6 but we had tried also with 3.5 and is the same error.

remove the environment property for gradle and delete .gradle folder from your home directory.
If you are not able to delete .gradle folder. then, remove environment property and restart your machine and then delete. now hit "gradle -v" in cmd. it will reconfigure your gradle. (we reconfigured this to get "gradle-worker.jar" which will be downloaded on reconfiguring.)

Remove the environment property for gradle and delete .gradle folder from your home directory.
If you are not able to delete .gradle folder. then, remove environment property and restart your machine and then delete. now hit "gradle -v" in cmd. it will reconfigure your gradle. (we reconfigured this to get "gradle-worker.jar" which will be downloaded on reconfiguring.)

Thanks for reporting. I suggest you to do as follows:

Run your tasks/params with extra --info, e.g. gradle test --info
You'll find the line Starting process 'Gradle Test Executor X'. Working directory: XXX Command: XXX in log

In my machine it looks like this:
/Library/Java/JavaVirtualMachines/jdk1.8.0_121.jdk/Contents/Home/bin/java -Djava.security.manager=worker.org.gradle.process.internal.worker.child.BootstrapSecurityManager -Djunit.version=4.12 -Dorg.gradle.native=false -Dfile.encoding=UTF-8 -Duser.country=US -Duser.language=en -Duser.variant -ea -cp /Users/zhb/.gradle/caches/4.5/workerMain/gradle-worker.jar worker.org.gradle.process.internal.worker.GradleWorkerMain 'Gradle Test Executor 3'

Note the -cp /Users/zhb/.gradle/caches/4.5/workerMain/gradle-worker.jar worker.org.gradle.process.internal.worker.GradleWorkerMain part.
Check if the <HOME>/.gradle/caches/4.5/workerMain/gradle-worker.jar exists. If not, try to delete the whole <HOME>/.gradle/caches/4.5 as a workaround.
The detail of this bug is still not clear, if you could provide us with a minimum reproducible sample that would be great.

Here, to get "gradle-worker.jar",
Remove the environment property for gradle and delete .gradle folder from your home directory.
If you are not able to delete .gradle folder. then, remove environment property and restart your machine and then delete. now hit "gradle -v" in cmd. it will reconfigure your gradle. (we reconfigured this to get "gradle-worker.jar" which will be downloaded on reconfiguring.)

@oehme how does that advice relate to e.g. the recommended config for a Travis build, which has rm -fr $HOME/.gradle/caches/*/plugin-resolution/? Or is this bug about deleting the whole caches directory?

I suggest running ./gradlew --stop (if you're running gradle wrapper from your local project) or gradle --stop
That will stop the running daemon and should allow you to run the commands you need

This was the answer for me. I started always running my builds such as:
gradlew --stop && gradlew clean build

Please reopen this issue if someone finds a way to reproduce a problem with worker processes failing to start.
@h2hjastermereel Neither of those things should be necessary (running --stop and running clean all the time).  You're effectively running without the daemon, which means you'll pay the start-up cost penalty for the daemon without ever re-using it.  If you're running into issues, please open an issue.  Thanks!

@big-guy Hi, we are seeing this issue on our jenkins server, when jenkins is running gradle (wrapper, tried both 4.10.2 and 5.2.1).
We don't see it when manually invoking gradle from the CLI.
It's a Windows Server running Java 8_202.
At this point we're not sure how to solve the issue, it just started happening one day about 2 weeks ago. I disabled all of the junit tests, but the error still occurs when jenkins invokes the test task.
The daemon is completely disabled, we run gradlew --stop first, and include the --no-daemon flag when running the tests, and another gradlew --stop when done.
The error happens every time, when gradlew is invoked by jenkins.

@christopherbryanboyd It sounds like you may be running into a different problem with a similar symptom.   Could you open a new issue with some of the things you've tried? Thanks!

@big-guy will do, thank you

Old thread, but this happened to me also, when I deleted the gradle caches folder.
I have 2 jdks configurations (openjdk and oracle jdk).
Changing the jdk solved my problem.

after I delete gradle cache folder (gradle_user_home folder) ,I compiled success .

If you have deleted caches directory and you don't want to delete the whole gradle_user_home folder, you can delete daemon directory only. I have verified the case.

The solution to this is easier than you know:
./gradlew --stop;./gradlew clean;./gradlew build

In my case it wasn't a leading space in GRAILS_OPTS,  it was two consecutive spaces. Once I correct that, things returned to normal.

In my case it wasn't a leading space in GRAILS_OPTS, it was two consecutive spaces. Once I correct that, things returned to normal.

 Wasted countless hours on it.....

The scenario I encountered is that the <HOME>/.gradle/caches/6.7.1/workerMain/gradle-worker.jar does not exist. During compilation, it is found that four threads are executed concurrently. Considering that multi-thread conflicts may exist, the four threads are modified to single-thread compilation to solve this problem.
Actions performed:
delete caches folder :  «HOME> / .gradle/caches
Add  org.gradle.workers.max=1 to the gradle.properties file.
Execute compile cmd :  ./gradlew clean build -x test --stacktrace --info
The gradle.properties file is modified due to other problems.  I suggest you to do as follows:

Run your tasks/params with extra --info, e.g. gradle test --info
You'll find the line Starting process 'Gradle Test Executor X'. Working directory: XXX Command: XXX in log

In my machine it looks like this:
/Library/Java/JavaVirtualMachines/jdk1.8.0_121.jdk/Contents/Home/bin/java -Djava.security.manager=worker.org.gradle.process.internal.worker.child.BootstrapSecurityManager -Djunit.version=4.12 -Dorg.gradle.native=false -Dfile.encoding=UTF-8 -Duser.country=US -Duser.language=en -Duser.variant -ea -cp /Users/zhb/.gradle/caches/4.5/workerMain/gradle-worker.jar worker.org.gradle.process.internal.worker.GradleWorkerMain 'Gradle Test Executor 3'

Note the -cp /Users/zhb/.gradle/caches/4.5/workerMain/gradle-worker.jar worker.org.gradle.process.internal.worker.GradleWorkerMain part.
Check if the <HOME>/.gradle/caches/4.5/workerMain/gradle-worker.jar exists. If not, try to delete the whole <HOME>/.gradle/caches/4.5 as a workaround.
The detail of this bug is still not clear, if you could provide us with a minimum reproducible sample that would be great.


Program shows wrong Synch spread

Sometimes the program shows the wrong synch of the spreads. It says that a spread is Synchronizable but it isn't instead.

According to this post (http://www.smogon.com/forums/threads/sfmt-rng-in-sun-moon.3591281/page-2#post-7211058), blinking process may occurs 2 times after  synchronize. So sometimes it will be different from the tool.

Uh, ok. Just close this issue then and thanks for your great work!


USE with caution for resourceUtil rollout strategy, any way to alleviate??????

Generally worked as expected, but there is one case I found out causing potential issues: if new revision need to spin up, but unable to succeed, the killed healthy old revision won’t be coming back. With availability strategy, we won’t be in this situation, the worst case is old and new revisions with traffic split. The resourceUtil strategy is something we should use and mark with use with caution

The principle for the resourceUtil strategy is scaling down the old revisions first and then scaling up the new revisions. We cannot violate the rule by far, so this issue will remain being discussed.


MonitorScheduler is prone to clock drift

MonitorScheduler emits metrics periodically using a ScheduledExecutorService, provided ScheduledThreadPoolExecutor, which is prone to unbounded clock drift.
It's impossible to say whether any of the Monitors intricate the time, or any of the emitters (receiver monitoring systems) imply a time of the sendings, so to reduce the chance of getting unreliable metrics in case of clock drift, I suggest to use CronScheduler.

Can I take this up?

Yes

If no one is assigned to it, can I pick this?

Yes

@leventov I found out that CronScheduler has some known vulnerabilities:

CVE-2017-9525
CVE-2019-9704
CVE-2019-9705

Can this be a concern? Also, can you list some steps to test the clock drift issue?

@ayushkul2910 CronScheduler doesn't use Unix cron command, thus these CVEs are not applicable.

@leventov Can you please review the above PR?


GH-44607: [C++][Dev] Update bundled Thrift, update mirrors to use CDN

Rationale for this change
Builds with bundled Thrift could fail because of permanently offline download mirror URLs. ASF now provides a CDN.
What changes are included in this PR?

Updates the pinned versioned for bundled Thrift from 0.16.0 to 0.21.0. This was prompted by the fact the Apache CDN doesn't host anything newer than 0.20.1. Also because keep these dependencies up to date is good.
As a result of (1), updates bundled Boost to 1.86.0 because Thrift 0.21.0 doesn't seem to be compatible with earlier Boost versions.
Removes the set of URLs we were using to download Thrift in favor of just using the main CDN URL. We'll see how this works in practice.

Are these changes tested?
Yes. I configured a build with ...-DThrift_SOURCE=BUNDLED... and ran the full C++ test suite. I think further testing can be done in CI.
Are there any user-facing changes?
No.
Closes https://github.com/apache/arrow/issues/44607

GitHub Issue: #44607

@github-actions crossbow submit test-r-linux-as-cran

@github-actions crossbow submit -g cpp

@github-actions crossbow submit -g cpp

Windows MSVC is failing with :

D:\a\arrow\arrow\build\cpp\thrift_ep-prefix\src\thrift_ep\lib\cpp\src\thrift\TUuid.cpp(22): fatal error C1083: Cannot open include file: 'boost/uuid/string_generator.hpp': No such file or directory

rhub/ubuntu-gcc-12 is failing with:

/tmp/Rtmpa7sH8K/file73956317ada/thrift_ep-prefix/src/thrift_ep/lib/cpp/src/thrift/TUuid.cpp:22:10: fatal error: boost/uuid/string_generator.hpp: No such file or directory
22 | #include <boost/uuid/string_generator.hpp>
|          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

The two failing builds were both bundling Boost and Thrift and I was able to reproduce the failure locally. From looking around, it looks like you have to upgrade to Boost 1.86.0 if you use Thrift 0.21.0. To test that hypothesis, I lowered Thrift down to 0.20.0 in https://github.com/apache/arrow/pull/44685/commits/4886ad7e12b1c008d12e909d913dacaae15b620b to test. I think we can get away with bumping Boost to 1.86.0 and Thrift to 0.21.0 in this PR so I'll try that once CI finishes.

With Boost 1.86.0 and Thrift 0.21.0, the MSVC build fails with:
2024-11-09T17:43:07.4309013Z [550/608] Linking CXX shared library debug\parquet.dll
2024-11-09T17:43:07.4310713Z FAILED: debug/parquet.dll debug/parquet.lib
2024-11-09T17:43:07.4323359Z C:\Windows\system32\cmd.exe /C "cd . && "C:\Program Files\CMake\bin\cmake.exe" -E vs_link_dll --intdir=src\parquet\CMakeFiles\parquet_shared.dir --rc=C:\PROGRA~2\WI3CF2~1\10\bin\100226~1.0\x64\rc.exe --mt=C:\PROGRA~2\WI3CF2~1\10\bin\100226~1.0\x64\mt.exe --manifests  -- C:\PROGRA~2\MICROS~2\2019\ENTERP~1\VC\Tools\MSVC\1429~1.301\bin\Hostx64\x64\link.exe /nologo src\parquet\CMakeFiles\parquet_shared.dir\Unity\unity_5_cxx.cxx.obj src\parquet\CMakeFiles\parquet_shared.dir\Unity\unity_4_cxx.cxx.obj src\parquet\CMakeFiles\parquet_shared.dir\Unity\unity_3_cxx.cxx.obj src\parquet\CMakeFiles\parquet_shared.dir\Unity\unity_2_cxx.cxx.obj src\parquet\CMakeFiles\parquet_shared.dir\Unity\unity_1_cxx.cxx.obj src\parquet\CMakeFiles\parquet_shared.dir\Unity\unity_0_cxx.cxx.obj src\parquet\CMakeFiles\parquet_shared.dir\__\generated\parquet_constants.cpp.obj src\parquet\CMakeFiles\parquet_shared.dir\__\generated\parquet_types.cpp.obj src\parquet\CMakeFiles\parquet_shared.dir\level_comparison_avx2.cc.obj src\parquet\CMakeFiles\parquet_shared.dir\level_conversion_bmi2.cc.obj  /out:debug\parquet.dll /implib:debug\parquet.lib /pdb:debug\parquet.pdb /dll /version:1900.0 /machine:x64  /NODEFAULTLIB:LIBCMT /debug /INCREMENTAL -Wl,--version-script=D:/a/arrow/arrow/cpp/src/parquet/symbols.map  debug\arrow.lib  "C:\Program Files\OpenSSL\lib\VC\libcrypto64MDd.lib"  "C:\Program Files\OpenSSL\lib\VC\libssl64MDd.lib"  thrift_ep-install\bin\thriftmd.lib  "C:\Program Files\OpenSSL\lib\VC\libcrypto64MDd.lib"  kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib && cd ."
2024-11-09T17:43:07.4347738Z LINK Pass 1: command "C:\PROGRA~2\MICROS~2\2019\ENTERP~1\VC\Tools\MSVC\1429~1.301\bin\Hostx64\x64\link.exe /nologo src\parquet\CMakeFiles\parquet_shared.dir\Unity\unity_5_cxx.cxx.obj src\parquet\CMakeFiles\parquet_shared.dir\Unity\unity_4_cxx.cxx.obj src\parquet\CMakeFiles\parquet_shared.dir\Unity\unity_3_cxx.cxx.obj src\parquet\CMakeFiles\parquet_shared.dir\Unity\unity_2_cxx.cxx.obj src\parquet\CMakeFiles\parquet_shared.dir\Unity\unity_1_cxx.cxx.obj src\parquet\CMakeFiles\parquet_shared.dir\Unity\unity_0_cxx.cxx.obj src\parquet\CMakeFiles\parquet_shared.dir\__\generated\parquet_constants.cpp.obj src\parquet\CMakeFiles\parquet_shared.dir\__\generated\parquet_types.cpp.obj src\parquet\CMakeFiles\parquet_shared.dir\level_comparison_avx2.cc.obj src\parquet\CMakeFiles\parquet_shared.dir\level_conversion_bmi2.cc.obj /out:debug\parquet.dll /implib:debug\parquet.lib /pdb:debug\parquet.pdb /dll /version:1900.0 /machine:x64 /NODEFAULTLIB:LIBCMT /debug /INCREMENTAL -Wl,--version-script=D:/a/arrow/arrow/cpp/src/parquet/symbols.map debug\arrow.lib C:\Program Files\OpenSSL\lib\VC\libcrypto64MDd.lib C:\Program Files\OpenSSL\lib\VC\libssl64MDd.lib thrift_ep-install\bin\thriftmd.lib C:\Program Files\OpenSSL\lib\VC\libcrypto64MDd.lib kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib /MANIFEST /MANIFESTFILE:src\parquet\CMakeFiles\parquet_shared.dir/intermediate.manifest src\parquet\CMakeFiles\parquet_shared.dir/manifest.res" failed (exit code 1104) with the following output:
2024-11-09T17:43:07.4362016Z LINK : warning LNK4044: unrecognized option '/Wl,--version-script=D:/a/arrow/arrow/cpp/src/parquet/symbols.map'; ignored
2024-11-09T17:43:07.4363542Z LINK : fatal error LNK1104: cannot open file 'thrift_ep-install\bin\thriftmd.lib'

It looks like our build may be conflicting with a change in Thrift that appeared in 0.21.0:
https://github.com/apache/thrift/blob/b65ec607db09f2efdb7397acde88fd53cfb97f6b/build/cmake/DefineInstallationPaths.cmake#L23-L29
# For MSVC builds, install shared libs to bin/, while keeping the install
# dir for static libs as lib/.
if(MSVC AND BUILD_SHARED_LIBS)
    set(LIB_INSTALL_DIR "bin${LIB_SUFFIX}" CACHE PATH "The library install dir (default: bin${LIB_SUFFIX})")
else()
    set(LIB_INSTALL_DIR "lib${LIB_SUFFIX}" CACHE PATH "The library install dir (default: lib${LIB_SUFFIX})")
endif()

@github-actions crossbow submit -g cpp

@assignUser this is ready for a review. Three of the four failed crossbow jobs looks like test flakiness but another set of eyes would be good. The test-debian-12-cpp-amd64 fails due to a related issue but for ORC. I think I could do a follow-up PR to update those URLs after this one.

Due to the bcp issue with boost 1.86.0, I bumped Thrift down to 0.20.0 and Boost back to 1.81.0. We can update to Thrift 0.21.0 once  Boost 1.87.0 is out (and we can confirm the included bcp works).

CI passed and PR description updated. @assignUser I think we can merge this without re-running all of the crossbow jobs and just be mindful during the 18.1.0 release process to look out for any issues.

Merged, thanks.


Split account constructor into new account and existing account

What should be done?
Currently there is a single constructor for [Account]s:
https://github.com/0xPolygonMiden/miden-base/blob/38340550a077a488d0466118c6868fe1144a38fc/objects/src/accounts/mod.rs#L60-L74
This constructor is used for both fresh/new accounts as well for existing accounts from existing data. The issue is that new accounts have different validations than existing accounts, creating two individual constructors would make the code a bit easier to follow in some places.
How should it be done?

When is this task done?
Once the two constructors have been added
Additional context
I'm creating this issue to get input, because this is a breaking change and it may not be worth it.

Agreed! I think we can rename the current new() into something like from_parts() as it requires no validation, and then change new() to work something like this:
pub fn new(
    seed: Word,
    code: AccountCode,
    storage: AccountStorage,
) -> Result<Self, AccountError>

Closed by #699.


Fix code scanning alert - Uncontrolled data used in path expression

Tracking issue for:

[ ] https://github.com/Carson-We/Machine-Learning/security/code-scanning/1

This alert is not relevant


How to remove unused tags from Defender ATP

I once created a tag and assigned it to a device. The device now has been deleted and I would like to get rid of the tag. But it still appears in the filter list. How do I remove the tag from ATP?

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

ID: 5b42e708-e334-d434-bcc9-e1860ebb36b3
Version Independent ID: 92e251c5-8613-ce97-9569-02404c9a466a
Content: Create and manage device tags - Windows security
Content Source: windows/security/threat-protection/microsoft-defender-atp/machine-tags.md
Product: w10
GitHub Login: @mjcaparas
Microsoft Alias: macapara

You can use the Defender for Endpoint API to achieve that goal.

Request example:
POST https://api.securitycenter.microsoft.com/api/machines/1e5bc9d7e413ddd7902c2932e418702b84d0cc07/tags
Content-type: application/json
{
"Value" : "test Tag 2",
"Action": "Remove"
}

You can use the Defender for Endpoint API to achieve that goal.

Request example:
POST https://api.securitycenter.microsoft.com/api/machines/1e5bc9d7e413ddd7902c2932e418702b84d0cc07/tags
Content-type: application/json
{
"Value" : "test Tag 2",
"Action": "Remove"
}

Thanks, looks great and I will try that ASAP!

Thanks, looks great and I will try that ASAP!

@andrePKI Have you tested this? Did it work?

I tried, but it is not what I am looking for. The tag is not attached to any machine, but nevertheless present in the Defender Security Center, e.g. at the Device Inventory blade, in the filter list. Over time, this will clutter the list with unused tag values.
So, if anybody knows another way to remove the tag value from the tenant....

@andrePKI I suggest reaching out to support in order to get an answer.
Our goal here is to update the documentation if needed, so when you find an answer let us know what it is and we can add that information to the article you linked, so others can reference it in the future.


Drop "in the past week"?

#9 landed:

IBM has already released two "lab-enhanced" (via InstructLab) models on HuggingFace in the past week:

but while that was true when that text was written, "in the past week" will go stale quickly.  Can we drop it?  I think the point being made holds together without needing to commit to a fixed time-offset between the model-release date and "now".

a69a5978f43f8c71c seems to have blown away some history, but it drop the past-week wording, so I'm closing this issue.


Fix typos in README

Coverage remained the same at 95.833% when pulling 9be2fa523ad35a12de6b2ea318251fa36909703c on dbanck:patch-1 into 2278a9f309025da9d7a367f47b96fac0f232b816 on react-tracing:master.


fix(css): fix masthead nav styles

Related Ticket(s)
#2203
Description
This fixes masthead styles to address layout issues when platform name is included in the nav.
Changelog
Changed

fix masthead styles for when platform name is displayed
update license text

Looks good. I wonder if we should create platform name as a separate story in storybook so percy can pick this up in the future.

@jeffchew Sure, good idea.


Create a Digital Cookbook

Description:
We're modernizing recipes. Your task is to design a digital cookbook with an intuitive and culinary-themed design for food lovers.

Difficulty: beginner
Estimated Time: 4-5 hours

Hi Jayesh,
Hi there! I'm interested in working on this issue. Could you please assign it to me? I believe I can make a valuable contribution to this task.
Looking forward to your response. Thanks!

Hello User,
Thank you for your interest in working on this issue. I've assigned the issue to you, and you can now start working on it. If you have any questions or need any assistance, feel free to ask. Good luck with your contribution!
Best regards,
Jayesh


Not downloading

[%] Successfully launched Chrome Browser
[%] Successfully opened link.
[%] Scrolling down.
[%] Successfully clicked 'Show More Button'.
[%] Reached end of Page.
Traceback (most recent call last):
File "google_scraper.py", line 120, in
source = search(url)
File "google_scraper.py", line 55, in search
f = open('dataset/logs/google/source.html', 'w+')
FileNotFoundError: [Errno 2] No such file or directory: 'dataset/logs/google/source.html'

Hi, thanks for reporting this. For some reason, when I released the latest code, I reordered the variables, resulting in the searching to be conducted before the folder structure is generated. This should be fixed now.

Sorry. It seems I have driver issue. Do you know where the problem is?
[%] Successfully launched Chrome Browser
[%] Successfully opened link.
[%] Scrolling down.
Traceback (most recent call last):
File "google_scraper.py", line 129, in
source = search(url)
File "google_scraper.py", line 43, in search
browser.find_element_by_id("smb").click()
File "/Users/Tristan/anaconda3/envs/image/lib/python3.5/site-packages/selenium/webdriver/remote/webelement.py", line 80, in click
self._execute(Command.CLICK_ELEMENT)
File "/Users/Tristan/anaconda3/envs/image/lib/python3.5/site-packages/selenium/webdriver/remote/webelement.py", line 628, in _execute
return self._parent.execute(command, params)
File "/Users/Tristan/anaconda3/envs/image/lib/python3.5/site-packages/selenium/webdriver/remote/webdriver.py", line 312, in execute
self.error_handler.check_response(response)
File "/Users/Tristan/anaconda3/envs/image/lib/python3.5/site-packages/selenium/webdriver/remote/errorhandler.py", line 242, in check_response
raise exception_class(message, screen, stacktrace)
selenium.common.exceptions.ElementNotVisibleException: Message: element not visible
(Session info: chrome=64.0.3282.167)
(Driver info: chromedriver=2.33.506106 (8a06c39c4582fbfbab6966dbb1c38a9173bfb1a2),platform=Mac OS X 10.13.2 x86_64)

Hi,
browser.find_element_by_id("smb").click() is the "Show More Button". That generally always exists. What is your search term?
I ran the example, and it worked perfectly fine:
python3.5 google_scraper.py "https://www.google.com/search?q=cats&source=lnms&tbm=isch&sa=X&ved=0ahUKEwiCi-3ygMPZAhVJ2GMKHcIJBNYQ_AUICigB&biw=1825&bih=940"

The "cats" work for me as well. Can you try "one does not simply meme"?

I went ahead and committed a fix. I had no idea that there were searches with no "Show More Button".


Updated package.json to export type definitions

Without the types key in the export section of package.json the typescript compiler complains that cannot find a declaration file:
error TS7016: Could not find a declaration file for module '@vueuse/sound'. <EMAIL_ADDRESS>implicitly has an 'any' type.
  There are types at<EMAIL_ADDRESS>but this result could not be resolved when respecting package.json "exports". The '@vueuse/sound' library may need to update its package.json or typings.

21 import { useSound } from '@vueuse/sound';
                            ~~~~~~~~~~~~~~~

Found 1 error in src/App.vue:21

ERROR: "type-check" exited with 2.

Closes #42

I think this is quite a urgent issue with simple solution. Hope this PR can be merge so soon..

The package doesn't work on new TS versions, hope this PR resolve it soon

would appreciate if you can merge this @Tahul

I sincerely hope to get your help @Tahul

Please merge!

Can this be merged?

@Tahul Is this repo no longer maintain?

@Tahul Can you please merge this?

This is becoming an issue can this be merged?

@Tahul Can you please merge this soon?
Used his fix for quite a while and should have no problem.

Use this PR and pnpm patch temporarily to make the type work, hope handle soon

hi @antfu
I'm so sorry to interrupt, but this repository has not been maintained for a long time, and now a ts type export is needed, this pr has been ready for a long time, but no one has permission to handle it.
Please help to deal with it, I believe this is still a very popular package
Thanks

Thanks a lot for the PR and sorry for the late answer.
I've merged this PR and applied other fixes to make it work with latest Nuxt versions.
I've published2.1.0, let me know if that fixes your issue.


Add BoxStore to README

Codecov Report

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

@@           Coverage Diff           @@
##           master      #15   +/-   ##
=======================================
  Coverage   28.24%   28.24%
=======================================
  Files           7        7
  Lines         216      216
  Branches        8        8
=======================================
  Hits           61       61
  Misses        155      155

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 4aac765...5444479. Read the comment docs.


switch to commander, bump packages

Switched to commander, bumped some packages
/ cc @TylorS

:+1: :+1:
LGTM
Looks a whole lot better

sweet merging


Center GeoJSON dataframes at sampled centroid

Fixes #774
A sample of the GeoJSON coordinates is taken and it's centroid computed. This is used as the origin of dataframe coordinates in order to increase available numeric precision.

Note: it seems that there is a little little diff, but much better result now.

Also, I'll try to create a test for this one.


Add kernel simulator

Add kernel api software simulator.

Simulator runs completely in interpreted mode, no compilation or type inference is done.
Simulator consists of 2 parts:

kernel_sim_impl.py - api-independent kernel implementation

provides id/size/allocation/barrier proxies and execute_kernel function, which is simulator entry point.
Simulator user must provide need_barrier flag if kernel need any cross-workitem synchronization (or just always set it True in conservative case)
User must also provide replace_global_func hook to replace frontend-specific APIs with simulator calls (see _replace_global_func in  kernel.py)

kernel.py - wrapper for numba-dpex kernel api

Simulator need greenlet package to handle barriers and synchronization
Not all numba-dpex kernel APIs covered yet
Added simulator-based get_global/local_id tests as example

@diptorupd it's ready for review

@diptorupd it's ready for review

@Hardcode84 few general questions:
a) If we have this simulator should the dpex intrinsic functions like get_global_id be implemented as stubs? (refer https://github.com/IntelPython/numba-dpex/blob/main/numba_dpex/ocl/stubs.py). Is a better way to implement the intrinsic functions as overloads of the functions in the kernel_sim? Then the usage model can become: a user writes a kernel function in Python (with kernel API restrictions) and once they are ready they add @kernel decorator?
b) Another approach may be to add a kwarg to the kernel decorator (may be simulator=True) and invoke simulator that way?
What do you think?
Also, please add an example and eventually we will need docs before beta release.

@diptorupd it's ready for review

@Hardcode84 I will review in more detail, but starting with few general questions regarding UX:
a) Once we have the simulator we can re-implement the dpex intrinsic functions like get_global_id as overloads of the functions in the kernel_sim? Then the usage model can become: a user writes a kernel function in Python (with kernel API restrictions) and once they are ready they add @kernel decorator?
b) Another approach may be to add a kwarg to the kernel decorator (may be simulator=True) and invoke simulator that way?
What do you think?
Also, please add an example and eventually we will need docs before beta release.

I'm not sure exposing simulator api directly to user is good idea,  but we can call it from our get_xyz_id stubs , with proper error reporting if called if outside kernel context.
I initially did simulator as separate decorator to reduce cross-dependencies (simulator depends on actual kernel api but not the other way around).
Regarding separate decorator vs simulator=True arg from user perspective I don't have strong preferences either side.

Regarding separate decorator vs simulator=True arg from user perspective I don't have strong preferences either side.

Ok we can address it as a follow up.

@Hardcode84 Can you squash some of the commits together? Let us have three commits: one for the main changes, one for the unit test and one for the example.
I think after that it is good to go. We can further improve as follow up work.

Thank you @Hardcode84!
We took several inspiration from your PR and the new kernel_api module in numba_dpex is a direct result of that. As the kernel_api design is now tailored towards SYCL API rather than OpenCL. Your PR does not directly apply. I am closing this PR for that reason.


[Monaco] Integrate WASM LSP

Run WASM LSP as service worker locally.

[ ] hover function definitions
[ ] errors on correct line numbers
[ ] intellisense completion request

cc @bthesorceror


Fix null ptr exception

Not sure exactly why this happens, maybe when a map fails to load or you quit out v quickly.

Would be good to know what is null exactly: g_currentServicesMapInfo or challenge? Without understanding the real problem this feels like a hacky fix.

I made an issue for this before checking here (#3, sorry!). I tested and it seems the challenge is what's null in this case


Visual Scripting: 'Wait' node doesn't work when using a 'Condition' node.

Operating system or device - Godot version:
Nightly build from http://www.purpleorangegames.com/godot/ (Date: 09/21/16). Windows 10 64 bit
Issue description (what happened, and what was expected):
Please see this sample image with a simple set up: http://pasteall.org/pic/show.php?id=106959
Even using _ready instead of _process it never prints the string after the 'condition' node. This problem has been confirmed by 2 other users on the IRC channel.
Steps to reproduce:
Recreate the image from above, you can use _ready instead of _process if you want.
Link to minimal example project (optional but very welcome):
http://pasteall.org/pic/show.php?id=106959

Still a problem #10175. Sample project: test.zip.

dang.. now I will have to re-learn how the visual script VM works to fix this bug..

dang.. now I will have to re-learn how the visual script VM works to fix this bug..

I hope it's commented :P