Querying over entity objects with multiple bidirectional association objects caused stackoverflow

To further demonstrate this issue, lets say we have 3 entity classes namely Books, Categories and Languages.

Books and Categories are bidirectionally associated i.e. Many Books can belong to a single Category and One Category can have many Books. The fetch type is 'EAGER' both side.
Similarly, Books and Languages are bidirectionally associated with fetch type being 'EAGER' both side.

Books.java
@Entity
@Table(name = "books")
public class Books {
    @Id
    @Column(name = "book_id")
    private int bookId;

    private String title;

    private String author;

    @ManyToOne(cascade=CascadeType.ALL,fetch = FetchType.EAGER)
    @JoinColumn(name = "language")
    private Languages language;

    @ManyToOne(cascade=CascadeType.ALL,fetch = FetchType.LAZY)
    @JoinColumn(name = "category")
    private Categories category;

   //setter and getters
}

Categories.java
@Entity
@Table(name = "book_categories")
public class Categories {

    @Id
    @Column(name = "category_id")
    private int categoryId;

    @Column(name = "category_name")
    private String categoryName;

    @OneToMany(fetch = FetchType.EAGER, mappedBy = "category")
    private List<Books> books;

    //setters and getters
}

Languages.java
@Entity
@Table(name = "book_languages")
public class Languages {

    @Id
    @Column(name = "language_id")
    private int languageId;

    private String language;

    @OneToMany(fetch = FetchType.EAGER, mappedBy = "language")
    private List<Books> books;

    //setters and getters
}

Now, while querying over any of these entity classes, the code throws a stack overflow exception. The exception is mainly due to eager fetching which causes the code to enter an infinite recursive loop while fetching associated objects.

Fixed. Released with Kundera-2.15.
Chhavi


Same matching topics in Match Template

Steps to reproduce:
Create a Match Template.
Add a matching topic.
Add the same topic (with same values of Strings) again.
Expected Behaviour:
Toast "Two entries cannot be same." should appear and the matching topic should not be added. Even after editing, the check should be done.

Observed Behaviour:
Same topics get added.

@opticod Please look into it and assign. I can send a PR then.

@shikharbhuddi
I have solved this issue earlier
Please build the app using latest code.

@free4murad Thanks!

@shikharbhuddi Latest codes are merged into bug-fixes branch, so for development purpose refer it.

@opticod Thanks!


403 Forbidden

I configured my Chef Server and Chef Compliance instances for integration.  When I attempting to run an audit cookbook this is the error message I am getting:

================================================================================
    Error executing action `fetch` on resource 'compliance_profile[linux]'
    ================================================================================

    Net::HTTPServerException
    ------------------------
    403 "Forbidden"

    Cookbook Trace:
    ---------------
    /var/chef/cache/cookbooks/audit/libraries/server_api.rb:23:in `binmode_streaming_request'
    /var/chef/cache/cookbooks/audit/libraries/profile.rb:55:in `block (2 levels) in <class:ComplianceProfile>'
    /var/chef/cache/cookbooks/audit/libraries/profile.rb:46:in `block in <class:ComplianceProfile>'

    Resource Declaration:
    ---------------------
    # In /var/chef/cache/cookbooks/audit/recipes/default.rb

     25:   compliance_profile p do
     26:     owner o
     27:     action [:fetch, :execute]
     28:   end
     29: end

    Compiled Resource:
    ------------------
    # Declared in /var/chef/cache/cookbooks/audit/recipes/default.rb:25:in `block in from_file'

    compliance_profile("linux") do
      action [:fetch, :execute]
      retries 0
      retry_delay 2
      default_guard_interpreter :default
      declared_type :compliance_profile
      cookbook_name "audit"
      recipe_name "default"
      owner "base"
      profile "linux"
    end

Running handlers:
[2016-04-08T16:13:15-07:00] ERROR: Running exception handlers
Running handlers complete
[2016-04-08T16:13:15-07:00] ERROR: Exception handlers complete
Chef Client failed. 0 resources updated in 05 seconds
[2016-04-08T16:13:15-07:00] FATAL: Stacktrace dumped to /var/chef/cache/chef-stacktrace.out
[2016-04-08T16:13:15-07:00] FATAL: Please provide the contents of the stacktrace.out file if you file a bug report
[2016-04-08T16:13:15-07:00] ERROR: compliance_profile[linux] (audit::default line 25) had an error: Net::HTTPServerException: 403 "Forbidden"
[2016-04-08T16:13:15-07:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef run process exited unsuccessfully (exit code 1)

Both servers are able to access each other over 443.

Both servers are able to access each other over 443.

While this is a necessary, it's unfortunately not sufficient.

Can you look into your chef-server's chef_gate logs? (/var/log/opscode/chef_gate/current)? It's verifying the request's signature before chef-server's nginx forwards the request.
If you only see HTTP 200 in there, it might be that your chef-server's chef_gate and your chef-compliance instance don't properly share the same "shared secret". Please ensure that next, e.g. by checking the configuration, or by looking into chef-compliance's core's logs (/var/log/chef-compliance/core/current).

Thanks!

I actually have the same issue, during converge the audit cookbook simply gives error 403 "Forbidden". My chef_gate log looks like this:
2016-05-09_14:47:09.15733 [GIN] 2016/05/09 - 16:47:09 | 400 |    8.515589ms | <IP_ADDRESS> |   POST    /compliance/organizations/$CHEF_SERVER_URL/inspec 2016-05-09_14:47:09.15735 Error #01: Couldn't find principal for $NODE_NAME (orgs $CHEF_SERVER_URL)
I also completely reinstalled compliance (still evaluating), but this did not change anything. Is there any log on the compliance server, that could help with this?

@JTabel this is a stab in the dark, but does your node in question has a node_name != client_name?  The described code path in chef_gate does this: given a signed request coming from a chef-client, it fetches the client's public key using GET /principals/NAME, and verifies the signature. So if to figure out what is wrong here, you could use chef-shell (or any chef API library you like using) with the pivotal key of chef_gate's chef-server, and lookup that endpoint for your node's name.

I ended up cleansing the install, upgrading to the latest version of compliance, and re-running the integration steps and was able to get it to work.

I am facing the same issue while running the audit cookbook. I am using the latest version of compliance, chef server and inspec. Please help.
Logs below:
tail -f  /var/log/opscode/chef_gate/current
2016-05-16_13:21:09.99935 [GIN] 2016/05/16 - 13:21:09 | 200 |   13.777166ms | <IP_ADDRESS> |   POST    /compliance/organizations/demo/inspec
2016-05-16_13:24:11.95138 [GIN] 2016/05/16 - 13:24:11 | 200 |   27.596463ms | <IP_ADDRESS> |   GET     /orgs
2016-05-16_13:24:12.15772 [GIN] 2016/05/16 - 13:24:12 | 200 |   61.234133ms | <IP_ADDRESS> |   GET     /orgs
2016-05-16_13:24:12.27839 [GIN] 2016/05/16 - 13:24:12 | 200 |    23.54308ms | <IP_ADDRESS> |   GET     /orgs
2016-05-16_13:24:12.32930 [GIN] 2016/05/16 - 13:24:12 | 200 |   19.725617ms | <IP_ADDRESS> |   GET     /orgs
2016-05-16_13:24:12.38496 [GIN] 2016/05/16 - 13:24:12 | 200 |   20.564337ms | <IP_ADDRESS> |   GET     /orgs
2016-05-16_13:24:12.48848 [GIN] 2016/05/16 - 13:24:12 | 200 |   18.645486ms | <IP_ADDRESS> |   GET     /orgs
2016-05-16_13:24:12.56252 [GIN] 2016/05/16 - 13:24:12 | 200 |   22.251111ms | <IP_ADDRESS> |   GET     /orgs
2016-05-16_13:24:12.70535 [GIN] 2016/05/16 - 13:24:12 | 200 |   66.161231ms | <IP_ADDRESS> |   GET     /orgs
2016-05-16_13:24:12.87906 [GIN] 2016/05/16 - 13:24:12 | 200 |   20.658468ms | <IP_ADDRESS> |   GET     /orgs
2016-05-16_13:31:58.96585 [GIN] 2016/05/16 - 13:31:58 | 200 |   12.492756ms | <IP_ADDRESS> |   GET     /compliance/organizations/demo/owners/base/compliance/ssh/tar
2016-05-16_13:31:59.08582 [GIN] 2016/05/16 - 13:31:59 | 200 |   17.407865ms | <IP_ADDRESS> |   GET     /compliance/organizations/demo/owners/base/compliance/linux/tar
2016-05-16_13:31:59.23695 [GIN] 2016/05/16 - 13:31:59 | 200 |   16.617363ms | <IP_ADDRESS> |   POST    /compliance/organizations/demo/inspec

tail -f /var/log/chef-compliance/core/current
2016-05-16_13:24:12.59512 13:24:12.595 DEB => ID of user admin changed: fb3f7e81-dd53-43da-7f49-0efbd51c4942 -> 6c0dd10b-0ac8-4bc3-aa53-fd348a8734d9 (resetting)
2016-05-16_13:24:12.71378 13:24:12.713 DEB => orgs for user admin (fb3f7e81-dd53-43da-7f49-0efbd51c4942): []string{"demo"}
2016-05-16_13:24:12.72114 13:24:12.721 DEB => Authenticated user: &{PasswordHash: Login:admin Name:admin IsOrg:false Source:{String: Valid:false} UUID:{ID:fb3f7e81-dd53-43da-7f49-0efbd51c4942}}
2016-05-16_13:24:12.72137 [GIN] 2016/05/16 - 13:24:12 | 200 |  128.414153ms | <IP_ADDRESS> |   GET     /server/config
2016-05-16_13:24:12.80786 13:24:12.807 ERR => DB error: sql: no rows in result set
2016-05-16_13:24:12.80959 13:24:12.809 DEB => ID of user admin changed: fb3f7e81-dd53-43da-7f49-0efbd51c4942 -> 6c0dd10b-0ac8-4bc3-aa53-fd348a8734d9 (resetting)
2016-05-16_13:24:12.88667 13:24:12.886 DEB => orgs for user admin (fb3f7e81-dd53-43da-7f49-0efbd51c4942): []string{"demo"}
2016-05-16_13:24:12.88842 13:24:12.888 DEB => Authenticated user: &{PasswordHash: Login:admin Name:admin IsOrg:false Source:{String: Valid:false} UUID:{ID:fb3f7e81-dd53-43da-7f49-0efbd51c4942}}
2016-05-16_13:24:12.88880 13:24:12.888 ERR => DB error: sql: no rows in result set
2016-05-16_13:24:12.89010 [GIN] 2016/05/16 - 13:24:12 | 200 |   85.015616ms | <IP_ADDRESS> |   GET     /owners/adcf5c2c-cda8-483f-4262-84f7b0c1555a/keys
2016-05-16_13:31:59.01786 13:31:59.017 ERR => Authentication: %!(EXTRA *errors.errorString=missing Authorization header)
2016-05-16_13:31:59.01789 13:31:59.017 ERR => Parsing token from request:%!(EXTRA *jwt.ValidationError=No shared secret passed through the environment (CHEF_GATE_COMPLIANCE_SECRET))
2016-05-16_13:31:59.01790 [GIN] 2016/05/16 - 13:31:59 | 401 |     201.964µs | <IP_ADDRESS> |   GET     /chef/organizations/demo/owners/base/compliance/ssh/tar
2016-05-16_13:31:59.12812 13:31:59.127 ERR => Authentication: %!(EXTRA *errors.errorString=missing Authorization header)
2016-05-16_13:31:59.12815 13:31:59.127 ERR => Parsing token from request:%!(EXTRA *jwt.ValidationError=No shared secret passed through the environment (CHEF_GATE_COMPLIANCE_SECRET))
2016-05-16_13:31:59.12821 [GIN] 2016/05/16 - 13:31:59 | 401 |     295.419µs | <IP_ADDRESS> |   GET     /chef/organizations/demo/owners/base/compliance/linux/tar
2016-05-16_13:31:59.29408 13:31:59.293 ERR => Authentication: %!(EXTRA *errors.errorString=missing Authorization header)
2016-05-16_13:31:59.29410 13:31:59.293 ERR => Parsing token from request:%!(EXTRA *jwt.ValidationError=No shared secret passed through the environment (CHEF_GATE_COMPLIANCE_SECRET))
2016-05-16_13:31:59.29411 [GIN] 2016/05/16 - 13:31:59 | 401 |      371.77µs | <IP_ADDRESS> |   POST    /chef/organizations/demo/inspec

I was able to fix this by restarting the compliance core service.
chef-compliance-ctl restart core

Thanks all for the feedback. Please reopen the issue if it persists.


Parameterized pseudo-classes break selector highlighting in SCSS

Information:

Prism version: 1.29.0
Plugins: none
Environment: Browser

Description
SCSS selectors that include parenthesized pseudo-classes are not highlighted as selectors.
Note that CSS does not have this issue.
Example
Triggers the bug:
foo :foo() bar {

}

Does not trigger the bug:
foo :foo bar {

}

Workaround
This appears to fix it in my setup (simply removing () from [^@;{}()\s], but not sure whether it breaks something else (@golmote any idea why that avoids parens?):
Prism.languages.scss.selector.pattern = /(?=\S)[^@;{}()]?(?:[^@;{}\s]|\s+(?!\s)|#\{\$[-\w]+\})+(?=\s*\{(?:\}|\s|[^}][^:{}]*[:{][^}]))/;

The pattern you suggested breaks the highlighting of the following code:
@mixin prefix($property, $value, $prefixes) {
}

where prefix should be tokenized as a function.


ubuntu user's cloud-boot SSH keys are not forcibly removed on re-keying of cideploy

We need to enforce the list of SSH keys rather than just add to it, so that if we change SSH keys after the 'nova boot' that creates a node, we don't keep allowing the old one in.

This was completed some time ago now.


User Can Register

User will be able to register a new account
ID (not shown on UI), Username, email, password (other fields optional)
Password field should be 60 characters
Passwords should be hashed (plain text passwords lose points)
Email should be unique
Username should be unique
Form should have proper validations/checks for legitimate data
Email validation
Username validation (length/required)
Password validation (length minimum)
Confirm password match
System should let user know if username or email is taken and allow the user to correct the error without wiping the form

https://github.com/ReyMArias/IT202009/commit/b9ac696f83a3f4aa2588316a47fb69bdc6699d33#diff-7b0b9cab1c519df365d99d16ede96705fb6c3b58b7457103e6f49acfb8a2f378

https://github.com/ReyMArias/IT202009/pull/48


Better logging?

Currently we are dumping logs to stdout (using iostream or cstdio), which works but I think is less ideal for debugging. I have even written some tools to work around this (eg 1 and eg 2).
As such, I think we should migrate to a proper logging system, which should integrate well with Python's logging module. I have not looked into this, but spdlog seems promising.

A good logging system can indeed help a lot in debugging. I agree it's worth doing it.
Qiling Zou

From: kunhtkun @.>
Sent: Friday, June 28, 2024 3:08:08 AM
To: maccmu/macposts @.>
Cc: Subscribed @.***>
Subject: [maccmu/macposts] Better logging? (Issue #67)
Currently we are dumping logs to stdout (using iostream or cstdio), which works but I think is less ideal for debugging. I have even written some tools to work around this (eg 1https://github.com/maccmu/macposts/blob/4faf6eed72d2b299f9becc48d4320aefddcc16d4/macposts/utils.py#L19-L44 and eg 2https://github.com/pengjiz/playground/blob/main/system/expose/expose.c).
As such, I think we should migrate to a proper logging system, which should integrate well with Python's logging module. I have not looked into this, but spdlog seems promising.
—
Reply to this email directly, view it on GitHubhttps://github.com/maccmu/macposts/issues/67, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABXEA7IHUUR4QQ63QBJFBB3ZJRPJRAVCNFSM6AAAAABKAQK2QSVHI2DSMVQWIX3LMV43ASLTON2WKOZSGM3TQOJQHA4DMOA.
You are receiving this because you are subscribed to this thread.Message ID: @.***>


Clicking on checkbox with @click-handler that impacts other checkbox will not check the clicked checkbox

Vue version
3.5.11
Link to minimal reproduction
https://play.vuejs.org/#eNqVU8FOwzAM/ZUoJ5CgExpcSjcB05DgAIhxjIS61tuypUmUpGNo6r/jJOtW0DSJU20/+/nZTrf0XutkXQNNaeag0iJ3MGSSkEzkUxDBRIdLXTsSHULct4YBo8UCitVUbRhtgfVlpUoQiM24sY7R3o7gMbietnfgzaZmSALpkWb/6GWhULJkNMZb/K4QvFjt4ZH3vKBuziRWxrY7ZQhmvc4qMlsYrl0QBxutjCMlzPJaOLKNlWXu8rPz1iPEgKuNPPiEhG2kxJkaLg7RKCwls1xYaMNNNJpdXgVuoUqbku3v6TpDdVvjvhbcJqEfGUTm27/U/tNgNOvtR6MX1FlknPF5srRK4nMInLh4VWkuwLxqx5W0jKKUyMNoLoT6eg6xzmi7Yx2JLy3eL0XjzYAFswZG95jLzRzwxXh4PHmBDdp7EC9dC8w+Ab6DVaL2GmPaQy1LlN3JC2qfKn9BLucfdrxxIG07lBcaFhPyGcV/YnRi9IPcfnId6phscIufazCeExfYT26Sqyva/ABwFwqe
Steps to reproduce
Click on checkbox with text "Second".
What is expected?
That the "First" checkbox is unchecked and that the "Second" is checked.
What is actually happening?
The "First" checkbox is unchecked, but the "Second" checkbox is still unchecked.
System Info
Chrome 129.0.6668.89. Ubuntu 22.04.
Any additional comments?
It works correctly in 3.4.38. But it stopped working in 3.5.0 and is not working in 3.5.11.

Here comes another reproduction of the issue but with just one checkbox:
https://play.vuejs.org/#eNp9Uk1P8zAM/itWTiDxti8CLqVMwOAAB0DAMRIqrbcF0iRK0jE09b/jJLSrEOIUfzy2n8fOll0Yk607ZAUrPbZGVh5nAFwBlLJ6RTmLplCm88EC8J8GzzirV1i/v+oNZym8/tfqBiVlhJuHHDachURqBnBeS1G/Tyrnwecsp3EDJoagxTgzT/MTF0MDxCJUB8izIAybhaeA7RbGIPR9mRviXOajGnJcbYXxUQpujLYeGlxUnfSwTYObyld7+4MHYNF3Vu18gFFVAYtKOjzYpcbpBfwfon0y+m9Yi36lG0dkpyuh0ukupgRozyvhsp2wM7giMZnSH3v7pz+nhKenaJmPStkB867WaiGW2ZvTig4cm9MGdWuERHtvvNDKcUasUh/OKin1x22MedsNIr9v9kv8zdEHKMh4sOjQrukqY85Xdok+pa+f7nBD9pikz9JJQv+RfESnZRc4JthlpxqiPcFFtjdtOKhQy2d3vfGo3CAqEI2LiXjO6JfP/5C+o3uUHcc6rnra4ssabehJCzzKTrLDQ9Z/AZ9WAFo=
Click on "Click me" checkbox. The time is updated, but the checkbox remains unchecked no matter how many times you click on it. It works correctly in 3.4.38, but stopped working in 3.5.0.

a workaround
secondClick() {
  setTimeout(()=>{
    this.first = false;
  },0)
}


AspectRatioContainer cant rotate.

Godot version
3.5.stable
System information
ArchLinux x11
Issue description
It resets the rect_rotation to 0 when resized is emitted.
Steps to reproduce

Open minimum reproduction scene in editor.
It should look like:

Run.
Observe: (the rotation was reset)

Minimal reproduction scene
[gd_scene format=2]

[node name="Control" type="CenterContainer"]
anchor_right = 1.0
anchor_bottom = 1.0

[node name="AspectRatioContainer" type="AspectRatioContainer" parent="."]
margin_left = 461.0
margin_top = 150.0
margin_right = 961.0
margin_bottom = 650.0
rect_min_size = Vector2( 500, 500 )
rect_rotation = 180.0

[node name="ColorRect" type="ColorRect" parent="AspectRatioContainer"]
margin_right = 500.0
margin_bottom = 500.0
color = Color( 0.623529, 0.25098, 0.25098, 1 )

Duplicate of https://github.com/godotengine/godot/issues/59306. Your AspectRatioContainer is child of a CenterContainer, so it cannot be rotated or scaled.

Ah, so i have to rotate the centercontainer? I see, that makes sense.
My bad.


Systemvm agent state isn't up

ISSUE TYPE

Other

COMPONENT NAME

systemvm agent state isn't up

CLOUDSTACK VERSION

4.16

CONFIGURATION

OS / ENVIRONMENT
 rhel 8.5/ vmware
SUMMARY

STEPS TO REPRODUCE

EXPECTED RESULTS

ACTUAL RESULTS

When i downgrade from CS4.18 to CS <IP_ADDRESS> And, systemvm and console vm agent isn't up.

![System VMs - CloudStack -](https://github.com/apache/cloudstack/assets/134905472/0fd8f647-3657-4c50-8f9a-96

9e13173080)

@HtainL , did you downgrade the DB and the packages and check if the old SVM template is still on the storage?

issued was closed.

delete systemvm and console vm
Then, systemvm auto create and agent was up


feature: Automatically reconnect the websocket connection on close

Quite simple, just recreate the websocket and reinitialize it whenever it closes. Unsure if this will have any janky side-effects, but seems to work okay.
Closes #165.

Shouldn't this need some sort of delay or debounce? Wouldn't it start spamming requests?

I agree with rymiel, a set timeout or even better, exceptional backoff

can use https://www.npmjs.com/package/exponential-backoff


Drag and drop lets me move things that aren't allowed at destination in sandbox

Not clear if this is still an issue, closing.


Staff Member

You must be a staff member to use this webpanel! If you believe this is a mistake, contact a developer.
How can i setup thes i am a stuff member where i can make this?

Per https://github.com/ExpDev07/legacy-rp-admin-v3/blob/master/app/Player.php#L82-L90, they need to have a "staff" property (column in db), and it needs to be set to something else than null, 0, or false. For example, true, 1, or a staff ID such as "ADMIN-1". If not, they will be caught by this middleware: https://github.com/ExpDev07/legacy-rp-admin-v3/blob/master/app/Http/Middleware/StaffMiddleware.php, hence your error.
Originally posted by @ExpDev07 in https://github.com/ExpDev07/legacy-rp-admin-v3/issues/14#issuecomment-612382494


Tweaking display of d1 execute (for large files in particular)

Takes some lines out when the commands fit in a single batch, and gives the user some context about where each batch starts if there are multiple, e.g.

also mind adding a changeset?


Add ability to merge serveral DQM or BQM objects

It would be useful to merge several BQM/DQMs.
At the moment one can do
bqm.update(other_bqm)

to merge two BQM objects.
We should add a DQM.update as well.
Further, it would be useful to combine many DQM/BQM together at relative weights. See https://github.com/dwavesystems/dimod/pull/784#issuecomment-769358918
One way to accomplish this would be a merge function, as suggested in https://github.com/dwavesystems/dimod/pull/784#issuecomment-769358918
Another would be to add a weight parameter to the BQM.update() and DQM.update() methods. Likely the function would end up calling the methods, but rolling them together would be nice.

I have been thinking about this. I believe that the operations (+, -, *, pow(), sum()) should always return a new object.
For example:
bqm + bqm + bqm
can be unambiguous, if bqm changes in the first operation. For example, if the bqm only has a bqm.offset = 1, the expression above can result in bqm.offset being 4 instead of 3.

Yes, of course. + should always make a new one, += modifies an existing. Did I imply otherwise?

nope. I had the wrong starting point in my head. To save space, one might consider modifying the largest BQM rather than creating a new one.

Makes sense, I think merge would look something like
def merge(bqms):
    merged_bqm = bqms[0].copy()
    for bqm in bqms[1:]:
        merged_bqm += bqm
    return merged_bqm

Obviously with input checking and avoiding the copy on list slice.

In 0.10.x there are two BQM objects, AdjVectorBQM and AdjDictBQM. right? Should all methods add to both objects as well as DQM?
All in one PR or multiple PR?

Unless it's urgent, I would not make any PRs on this. There are some fundamental decisions about structure and API that need to be worked out. In the case that we need performant merging urgently, I'd like to address https://github.com/dwavesystems/dimod/issues/757. It's not a hard change to make, but given the current implementation work, I should do it so we're not doing redundant work.


Add a new onedata_failsafe option

So the datahub does not fail when starting

Summary

Avoid failing whenever datahub is not available.

Related issue : #75

@enolfc  if i understood correctly  this change, in case we return an empty token instead of throwing an exception, the oneclient mount will fail on the sidecar container but this won't prevent the notebook container to start , correct?

yes, that's the initial idea. The sidecar should not even be created as the token will not be there

ok thanks i see it in the code now where the creation of the sidecar is skipped, i guess we can go for it and think about the warning to the user later


Fixed incorrect information in README

Current dependencies on/for this PR:

main

PR #158

PR #162

PR #165   👈

PR #166

This comment was auto-generated by Graphite.

Graphite Merge Job
Current status: ⏳ Queued to merge
This pull request is currently queued to be merged as part of a stack.
This comment was auto-generated by Graphite.

Job Reference: 3kyLcwdoqbYYTVlDETi7


Revamped admin module #675

The only thing that I've been unable to fix is that I'm now seeing the clause-truncation-text on the summary section, always; even if there are no clauses and a lot of paragraphs have been loaded to the law.
@jfresco I'm not quite clear on how to address this and I'm kind of burnt here. @slifszyc please have a look at this; you'll probably be able to sort it out.


execution in seconds

Would it be possible to circumvent this scheduling method where it allows only at least every minute and is able to adjust to run for example every 10 seconds?

@gamadoleo I've already replied to your question in #61

ok

thanks a lot, for the return, get done as recommended, now min arises a doubt imagine that I have several tasks schedules, so realize the task that is at the end of the queue is executed only when all the previous ones have already been executed, is there any way force them all to start at the same instant, without depending on the completion of the previous ones?

to avoid this issue you might use a different approach, for example scheduling the scheduler 4 times in the same file.
Example: you have your scheduler script with all the jobs that need to be executed (foreground and background jobs, it doesn't matter). Now, because some of yours scheduler executions might take more than 15s to execute, there could be a case of job overlapping.
So, instead of running the scheduler 4 times on that file, set it up for a singular execution.
Then create a "master scheduler" that runs 4 times and executes in the background your scheduler every 15s.
eg. scheduler.php
#....
$scheduler = new Scheduler();

// These are the scripts that need to be executed every 15s
$scheduler->php('my_script.php');
$scheduler->php('my_other_script.php');
$scheduler->php('some_other_script.php');

$scheduler->run();

Now create the master_scheduler.php
#....
$scheduler = new Scheduler();

// This is the script that needs to be executed every 15s
$scheduler->php('scheduler.php');

sleep(15);
$scheduler->resetRun()->run();

sleep(15);
$scheduler->resetRun()->run();

sleep(15);
$scheduler->resetRun()->run();

Because scheduler.php can run in the background, there will be minimal or no delay at all between the execution. So you are sure that all of your jobs will run at the same time every 15s.
Hope that helps

Ok, thank you very much, I analyzed the library here, the thing is that I used the -> then () method, and this makes the script to run in the foreground, and when modifying via parameter to force in the background, return script, but okay, I'll review my need.


745 update grabdish terraform

Variable-ising OKE version in both locations:
grabdish/terraform and infra/k8s/oke/terraform

Why two locations? (grabdish/terraform and infra/k8s/oke/terraform)?


refactor: remove minvals check for uints

Remove minvals check for uints
Keep min=0 in the schema and remove lint:ignore rule from the generator
Closes https://github.com/elastic/apm-data/issues/131

The original idea for this fix was to infer a minimum value for the generated JSON schema.
https://github.com/elastic/apm-data/pull/123#discussion_r1274969475

With the check for types.IsUnsigned, shouldn't we bring back minVal=0 for jsonschema validation? (that's what I meant in my comment earlier).

@dmathieu are you asking why there's no diff on the generated JSON Schema? That's because it already had the minimum value property, and still does: https://github.com/elastic/apm-data/blob/3d5c2a73763d32b36efcbb048c666ce208fd2df5/input/elasticapm/docs/spec/v2/metricset.json#L91


Tuya-lan-find gives error when attempting to launch

I've run homebridge successfully for some months now, and recently installed the homebridge-tuya-lan module in order to control some Feit color lightbulbs that are not homekit compatible.  I modified config.js of homebridge to include the tuya platform, but added no devices to it, since I don't yet have the id and key of the feit bulbs.  Homebridge continues to launch successful except to complain of there being no configured devices for tuya.  When I attempt to run tuya-lan-find, it give the following error:
/usr/local/lib/node_modules/homebridge-tuya-lan/bin/cli.js:175
let {address, port} = proxy.httpServer.address();
^
TypeError: Cannot read property 'address' of undefined
at proxy.listen (/usr/local/lib/node_modules/homebridge-tuya-lan/bin/cli.js:175:44)
at /usr/local/lib/node_modules/homebridge-tuya-lan/node_modules/http-mitm-proxy/lib/proxy.js:62:14
at /usr/local/lib/node_modules/homebridge-tuya-lan/node_modules/http-mitm-proxy/lib/ca.js:130:14
at /usr/local/lib/node_modules/homebridge-tuya-lan/node_modules/http-mitm-proxy/node_modules/async/dist/async.js:3888:9
at /usr/local/lib/node_modules/homebridge-tuya-lan/node_modules/http-mitm-proxy/node_modules/async/dist/async.js:473:16
at iterateeCallback (/usr/local/lib/node_modules/homebridge-tuya-lan/node_modules/http-mitm-proxy/node_modules/async/dist/async.js:988:17)
at /usr/local/lib/node_modules/homebridge-tuya-lan/node_modules/http-mitm-proxy/node_modules/async/dist/async.js:969:16
at /usr/local/lib/node_modules/homebridge-tuya-lan/node_modules/http-mitm-proxy/node_modules/async/dist/async.js:3885:13
at /usr/local/lib/node_modules/homebridge-tuya-lan/node_modules/mkdirp/index.js:47:53
at FSReqCallback.oncomplete (fs.js:161:21)
I'm running homebridge on Mac OS 10.15.1 on a 16" MacBook Pro.
I ran homebridge in debug mode and saw nothing pop up associated with tuya-lan-find in the console logs.

I found it necessary to launch tuya-lan-find as root in order for it to start the proxy server.


GHA enhancement automate go test

instead of manual check following up on https://github.com/opendatahub-io/model-registry/pull/18#issue-1908984838

Was resolved as part of https://github.com/opendatahub-io/model-registry/pull/38#event-10566721852


Revert "Optimize usage of test-runner (#46)"

Reverts SpoonLabs/flacoco#46 as we should merge #45 first.

The builds will fail because 2.3.1-SNAPSHOT already has the changes. No worries, as we will merge #45 and #46 right after.

@martinezmatias ready to do this operation?


Generalize CatchingCallback function

Use variadic template and perfect forwarding so that this is a more general exception catcher (in particular, for use in server-side handlers that are all of different flavors)

****************************************************************

libgrpc.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

****************************************************************

libgrpc++.so

     VM SIZE                                                            FILE SIZE
 ++++++++++++++ GROWING                                              ++++++++++++++
  +0.5%    +116 src/cpp/client/generic_stub.cc                          +116  +0.5%
       +13%     +87 grpc::internal::CallbackWithStatusTag::StaticRun         +87   +13%
      +0.8%     +29 grpc::GenericStub::experimental_type::UnaryCall          +29  +0.8%

 -+-+-+-+-+-+-+ MIXED                                                +-+-+-+-+-+-+-
  -0.0%      -4 [None]                                                 +1004  +0.0%

  +0.0%    +112 TOTAL                                                +1.09Ki  +0.0%

[trickle] No significant performance differences

Objective-C binary sizes
*****************STATIC******************
  New size                      Old size
 1,997,274      Total (=)      1,997,274

 No significant differences in binary sizes

***************FRAMEWORKS****************
  New size                      Old size
11,021,694      Total (<)     11,021,697

 No significant differences in binary sizes

Corrupt JSON data (indicates timeout or crash):
    bm_call_create.BM_IsolatedFilter_ClientChannelFilter_NoOp_.counters.new: 10
    bm_call_create.BM_IsolatedFilter_ClientChannelFilter_NoOp_.counters.old: 10

[microbenchmarks] No significant performance differences


Fixes significant numbers error when creating BigNumber from block_time

Pull Request Test Coverage Report for Build 2142

0 of 0   changed or added relevant lines in 0 files are covered.
27 unchanged lines in 6 files lost coverage.
Overall coverage decreased (-2.4%) to 73.524%

Files with Coverage Reduction
New Missed Lines
%

src/TxPool/TxPoolProcessor.ts
1
86.11%

src/Scanner/WatchableBucket.ts
1
87.1%

src/TxPool/TxPool.ts
2
78.85%

src/Util.ts
3
75.21%

src/TimeNode.ts
3
95.16%

src/WsReconnect/index.ts
17
31.34%

Totals

Change from base Build 2140:
-2.4%

Covered Lines:
860

Relevant Lines:
1112

💛  - Coveralls

Pull Request Test Coverage Report for Build 2142

0 of 0   changed or added relevant lines in 0 files are covered.
27 unchanged lines in 6 files lost coverage.
Overall coverage decreased (-2.4%) to 73.524%

Files with Coverage Reduction
New Missed Lines
%

src/TxPool/TxPoolProcessor.ts
1
86.11%

src/Scanner/WatchableBucket.ts
1
87.1%

src/TxPool/TxPool.ts
2
78.85%

src/Util.ts
3
75.21%

src/TimeNode.ts
3
95.16%

src/WsReconnect/index.ts
17
31.34%

Totals

Change from base Build 2140:
-2.4%

Covered Lines:
860

Relevant Lines:
1112

💛  - Coveralls


Function parameters now support default assignments

This implementation has some limitations:

We currently can't use super and arguments as default args since these ops have context restrictions and we won't always be able to emit them into the outer scope. One way to solve this could be to use LoadFromScope operations.
Now that we have default args, should we ensure that inputTypes is in sync with the default arg types? Not sure if that's a good idea since the default args are generated randomly and narrowing the type from .anything doesn't make a lot of sense. Happy to hear arguments (no pun intended!) both for an against this.

@saelo this PR is ready for review. Please see the note on limitations and let me know what you think.

This implementation has some limitations:

We currently can't use super and arguments as default args since these ops have context restrictions and we won't always be able to emit them into the outer scope. One way to solve this could be to use LoadFromScope operations.
Now that we have default args, should we ensure that inputTypes is in sync with the default arg types? Not sure if that's a good idea since the default args are generated randomly and narrowing the type from .anything doesn't make a lot of sense. Happy to hear arguments (no pun intended!) both for an against this.

So for 1. I think it's fine to ignore it. I'm also not sure if this won't fix itself: of super and arguments have special context requirements (in class and in function), and we decide for approach 1, then they shouldn't be available before the function. Or is the problem that they'll be inlined, and then that causes syntax errors? In either case, I think it's fine to ignore that...
For 2. I think it would make sense to try and find matching (i.e. correct type) default values, at least in .conservative mode. Maybe this'll be fairly easy though if we have all the information in the FunctionSignature (i.e. the information about the expected type and whether there's a default value)

Maybe there are other options yet?

I don't think there's an easy way to handle call-time-invocation without using some form of inlining. There's a potentially simpler approach using inlining that we could consider. How about we add a property to Variable such as isInlined to help the lifter determine which outputs should be cached and which outputs should be emitted immediately to the script buffer. For example consider the following program:
let v0 = CreateObject...
BeginFunctionDefinition <- v1 -> v0
....
EndFunctionDefinition

At the time of code gen we could set the isInlined flag on the output of the CreateObject operation i.e v0. At the time of lifting, if we determine that the output from the operation has the isInlined property set then we generate an expression for v0 and store this in a 'expression cache' rather than emitting it to the script buffer.
Now when we get to parsing default function parameters, we first look up the inline cache for an expression that matches the default assignment variable and if that lookup fails then we simply lift the variable identifier. In this way we move the inlining property from the lifter to the output variables. The FuzzIL would essentially stay the same and if we wanted to we can add additional analysers to track these inline variables if we wanted to (I currently can't think of a reason why that would be useful.) Wdyt?

Now if we decide for approach 1 (I think I'm leaning towards that), and we anyway refactor FunctionSignature, then I think I'd be in favor of moving the information about which parameters have default values into the FunctionSignature (so we'd have a Parameter type .paramWithDefault or so). This will again enable us to support default values in every type of function without any further changes.

This makes sense but we would still need to update the various function operations (regular, objects, classes) to have the numInputs match the number of default parameter assignments. I don't think that's a big deal but something to consider.

Now that we have improved FunctionSignatures, do we want to use them here to express whether there are default arguments? I could imagine that to work pretty nicely, since default arguments should be supported in all the different function types we have

I'm closing some seemingly stale PRs, but please reopen if you'd still like to merge this. Thanks!


Updated CHANGELOG and pubspec.yalm

Also I think you need to branch off the latest singerdmx/flutter-quill commit rather than just using your previous branch from #1210

I agree but I honestly don't have time to deal with it now. Please feel free to do it correctly.

Nevermind looks like this has already been done in https://github.com/singerdmx/flutter-quill/commit/0a3fe3f63c4636c68de1e44523eae3b9de787dcb
This PR can be closed


SwiftUI preview crashed

The preview produced an crash, the ips file is attached
//
//  CustomKeyboardView.swift
//  MyKeyboardExtension
//

import KeyboardKit
import SwiftUI

/**
 This view adds a `SystemKeyboard` with some more views to a
 `VStack`, then configures the keyboard slightly.

 The system keyboard will then adapt its appearance based on
 the ``DemoKeyboardAppearance``, its input keys based on the
 ``DemoInputSetProvider`` and its full keyboard layout based
 on the ``DemoLayoutProvider``.
 */
struct DemoKeyboardView: View {

    unowned var controller: KeyboardInputViewController

    @State private var isExpanded = false
    @State private var clipboardText: String = ""

    @EnvironmentObject
    private var keyboardContext: KeyboardContext

    var body: some View {
        VStack(spacing: 0) {
            ToolbarView(
                isExpanded: isExpanded,
                expandAction: toggleExpand,
                pasteAction: pasteButtonTapped,
                translateAction: translateButtonTapped,
                clearAction: clearButtonTapped,
                clipboardText: clipboardText
            )

            if isExpanded {
                // 展开状态的界面
                ExpandedView().frame(height: 214)
            } else {
                // 收起状态的界面
                SystemKeyboard(
                    controller: controller,
                    autocompleteToolbar: .none
                )
            }
        }
        .onAppear {
            pasteButtonTapped()
        }
    }

    func toggleExpand() {
        withAnimation {
            isExpanded.toggle()
        }
    }

    func pasteButtonTapped() {
        // 处理粘贴按钮的动作
        if let pasteboardString = UIPasteboard.general.string {
            clipboardText = pasteboardString
            isExpanded.toggle()
        } else {
            clipboardText = ""
        }
    }

    func translateButtonTapped() {
        // 处理翻译按钮的动作
    }

    func clearButtonTapped () {
        // 处理清除标签按钮的动作
        clipboardText = ""
    }
}

struct DemoKeyboardView_Previews: PreviewProvider {
    static var previews: some View {
        DemoKeyboardView(controller: .preview)
            .environmentObject(KeyboardContext.preview)
    }
}

MyAIKeyboard-2023-05-31-212349.ips.zip

Hi @wpcfan
I can't see any information in the ips file that helps me understand what goes wrong.
What happens if you try to preview a plain SystemKeyboard view instead of the demo one?

issue is gone, dont know why


fix(table): Add an isKeyboardNavigationDisabled prop to disable the navigation

Closes #3681
📝 Description

PR adds isKeyboardNavigationDisabled prop to disable navigation on keypress

⛳ Current behavior (updates)

Currently, whenever any arrow-key keypress is triggered it navigates the focus to other cell/row.
This maybe an issue when the table cell contains a component which requires this keys for specific purpose.
Example for above scenario could be: table cell contains input component, it might need arrow keys for editing. But it is not possible because whenever the keypress triggers navigation

https://github.com/user-attachments/assets/61ae353d-cdca-4cbf-b12d-1146da371704
🚀 New behavior

The PR adds an isKeyboardNavigationDisabled prop to disable the navigation through keyboard.

https://github.com/user-attachments/assets/c05c084a-8caf-4959-aee8-102818220a0a
💣 Is this a breaking change (Yes/No): No
Additional info

updated the docs

Summary by CodeRabbit

New Features

Introduced isKeyboardNavigationDisabled prop for the Table component, allowing users to disable keyboard navigation when interacting with components that require arrow key inputs.

Documentation

Updated Table component documentation to include details about the new isKeyboardNavigationDisabled prop.

Tests

Added a test case to verify the functionality of the isKeyboardNavigationDisabled prop, ensuring keyboard navigation is disabled when the prop is set to true.

I think a better solution is to automatically disable keyboard navigation temporarily when the focus is on the input, so that can move the cursor with the keyboard and use the Tab key to navigate to other elements of the table after leaving the input.

Thanks for the suggestion @AnYiEE. But I do not think it would be a great idea to write in a logic that checks if component is input component then stop the keyboard navigation.
One work-around which I thought could be helpful is rather than adding a prop isKeyboardNavigationDisabled to the table, we can add this prop to any of the cell. If any cell with isKeyboardNavigationDisabled as true, keyboard navigation will be stopped when then cell is in focus.
any thoughts here @wingkwong, should we go forward with adding the prop to the Table or it would be helpful to add the functionality to the TableCell instead.

@macci001 Is it not merge yet? I need this option :(

@wingkwong can I please get in some review here?

Reflecting on your comment @ryo-manba
I can think of following design for the edit mode:

In any of the cases, one when the cell has focusable children and other when cell do not have focusable children, always entire cell is focused. That is, focusMode set to cell instead of child.
Whenever there is Enter keypress on a focused cell:

If cell does have some focusable children:

Set the focus on the first/last focusable children (based on RTL)
Add the keyboard navigation on shift + leftarrowkey and shift + rightarrowkey for navigating to prev/next focusable children of the cell.

If cell does not have any focusable children -> do nothing i.e. edit mode is not relevant in this case.

Esc/Tab keypress to exit the edit mode.

Note 1: For navigation between focusable children of the cell, getFocusableTreeWalker will be used.
Note 2: For now, the useTableCell internally uses useGridCell's default value for focusMode i.e.  child. This means, that  whenever the cell will be in focus, the focus will shift to the focusableChild if it exist, else entire cell would be in focus. In order  to implement the edit mode, we would need the react-aria team to add a prop by which we can set the focusMode to cell.

@macci001
Thank you for your detailed insights. I'll discuss it with the team and see how we can proceed.

Hey @macci001 please fix the conflicts


Action stopped working -> cannot read properties of undefined.

Hi,
I was using this action for >3 months now, and it suddenly stopped working on 2nd March with the following error stack trace:

There were no labels changed, the actions haven't been touched either.
Any ideas/suggestions?
For now, I have disabled the workflow manually.

You can for now pin to v1.0.0, I'll release a patch ASAP.

It's fixed now in v1. Could you confirm it?

I did the below, but keep getting the same erorr. The stack trace tells me it's still using v1
...
    runs-on: ubuntu-latest
    steps:
      - uses<EMAIL_ADDRESS>...

Sorry for the inconvenience. Should be fixed now with:
...
    runs-on: ubuntu-latest
    steps:
      - uses: mondeja/remove-labels-gh-action@v1
...

Yup, can confirm that is rolling now. Nice one! Thanks for the quick response! 🥇


Zoom image grid to fit images

Adds logic that will automatically update the zoom slider so all images will be visible. Updates the image grid to have a larger margin to better display images that are close to the edge.
Fixes #31

Seems to work great. One thing I noticed is that if you don't have images (so only points), it will still adjust the plot size based on the image scaling slider. I'm not sure how much that matters, but I was curious what would happen. It does factor in the points to change the dimensions of the plot.

Seems to work great. One thing I noticed is that if you don't have images (so only points), it will still adjust the plot size based on the image scaling slider. I'm not sure how much that matters, but I was curious what would happen. It does factor in the points to change the dimensions of the plot.

The logic here just looks at the point location in calculating the amount to scale. The images are just rendered relative to each point.


[$1000] Composer is focused when creating a workspace

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

Action Performed:

Click on 'Profile' icon
Click on 'Workspace' link
Click on 'New workspace' button

Expected Result:
Composer shouldn't be focused
Actual Result:
Composer is focused
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

Version Number: <IP_ADDRESS>
Reproducible in staging?: y
Reproducible in production?: n
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/43996225/dddb6bc8-3b5d-4fcd-99cf-359640fdd6e9
https://github.com/Expensify/App/assets/43996225/e01ae64c-93e0-4a71-bf5a-e2cc6ff2d688
Expensify/Expensify Issue URL:
Issue reported by: @natnael-guchima
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1684825988204159
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~010bb443b5ade008b1
Upwork Job ID:<PHONE_NUMBER>599945728
Last Price Increase: 2023-06-01

:wave: Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open StagingDeployCash deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

Identify the pull request that introduced this issue and revert it.
Find someone who can quickly fix the issue.
Fix the issue yourself.

Confirmed I can reproduce on staging but not prod. @danieldoglas do you agree this should be a deploy blocker?

I don't think this is a deploy blocker. It's a bug, but it won't break the app/experience if we deploy it to production. But we need to find the offending PR

I think this is the PR https://github.com/Expensify/App/pull/19224

I am guessing this might be the offending PR https://github.com/Expensify/App/pull/19224

Thanks! PR is in review.

Adding an additional BZ assignee as I'm OOO next week (until June 5th). PR for this one is up, but there is some discussion in the PR about how we should proceed. Next steps here are to just make sure we drive the discussion in the PR to resolution.

Adding an additional BZ assignee as I'm OOO next week (until June 5th). PR for this one is up, but there is some discussion in the PR about how we should proceed. Next steps here are to just make sure we drive the discussion in the PR to resolution.

as discussed in https://github.com/Expensify/App/pull/19492#issuecomment-1569325157, assigning @Santhosh-Sellavel as the C+ for this issue. This was not a regression, but actually something that happened independently of the changes in the PR I tagged above. The changes in the PR just made the issue clear.
Adding this as external.

@abekkala I'm back from OOO, so removing your assignment!

This is a dupe of https://github.com/Expensify/App/issues/18182 and can be closed.

Yep, looks like a dupe to me. @danieldoglas cool to close this too?

oh wow, yes. That one is older. I think it's the same root cause. Let's close this one.


NPM Start Error -  Could not find module "@parcel/transformer-sass" satisfying 2.8.0.

When I try to start the project, this is what I get.

In the package.json, it originally had it as like 2.0.1 or something like that. I tried changing it to my current version of @parcel/transformer-sass, and 2.8.0 because that is the version the error is talking about, but it isn't working. Any Ideas?

did you figure it out?

Hi @Viraj-Bagga @kailew
Are you still getting the mentioned issue?
Please do a copy of the following package.json (current from the master branch)
{
  "name": "simplefolio",
  "version": "1.0.1",
  "private": "true",
  "description": "A clean, beautiful and responsive portfolio template for Developers!",
  "source": "src/index.html",
  "scripts": {
    "start": "parcel",
    "build": "parcel build"
  },
  "repository": {
    "type": "git",
    "url": "git+https://github.com/cobiwave/simplefolio"
  },
  "keywords": [],
  "author": "Jacobo Martinez",
  "license": "ISC",
  "bugs": {
    "url": "https://github.com/cobiwave/simplefolio/issues"
  },
  "homepage": "https://github.com/cobiwave/simplefolio#readme",
  "devDependencies": {
    "@parcel/transformer-sass": "^2.8.2",
    "parcel": "^2.8.2",
    "prettier": "^2.8.1"
  },
  "dependencies": {
    "@popperjs/core": "^2.11.6",
    "bootstrap": "^5.2.3",
    "jquery": "^3.6.3",
    "popper.js": "^1.16.1",
    "vanilla-tilt": "^1.8.0"
  }
}

after that, please use the required node version: 16.14.2 and delete the node_modules folder.
Finally: npm run install && npm run start

After using the above package.json file, The problem is still not solved.

All good I figured it out. I had not added the hyperlink

I had same issue, after installing parcel it got resolved.
npm install parcel --save-dev

I had same issue, after installing parcel it got resolved. npm install parcel --save-dev

@cobiwave this one solved the issue.

I had to update both parcel and parcel/transformer-sass to 2.9.3 and then it worked

npm i<EMAIL_ADDRESS>that line should fix it


Load configuration from file

It would be handy to provide goa with a mechanism to load configuration from file.

goa.yml could look like this
output_dir:
skip_dirs:
  - .git
logger:
  level: DEBUG
alias:
  build: go build
  run: go run
  test: go test

This file could be generated by just running goa init . An a goa.yaml with default values would be created

feature/v0.0.2

Done in branch feature/v0.0.2


Modular Refactor

I can move all the events in your main.js file into a folder of their own.
e.g. ready.js and message.js could be in a folder called 'Events'
Let me know and I'll get started when I have time.

Sure, go for it @valkyrienyanko !

Done. See #8


Agent doesn't restart on journald failure

Output of the info page (if this is a bug)
Getting the status from the agent.

==============
Agent (v6.0.3)
==============

  Status date: 2018-04-04 23:15:12.440773 UTC
  Pid: 920
  Python Version: 2.7.12
  Logs:
  Check Runners: 1
  Log Level: info

  Paths
  =====
    Config File: /etc/datadog-agent/datadog.yaml
    conf.d: /etc/datadog-agent/conf.d
    checks.d: /etc/datadog-agent/checks.d

  Clocks
  ======
    NTP offset: -0.000200632 s
    System UTC time: 2018-04-04 23:15:12.440773 UTC

  Host Info
  =========
    bootTime: 2018-02-17 00:06:22.000000 UTC
    kernelVersion: 4.13.0-1006-gcp
    os: linux
    platform: ubuntu
    platformFamily: debian
    platformVersion: 16.04
    procs: 249
    uptime: 3.872051e+06

  Hostnames
  =========
    host_aliases: [internal-v6mx.findmine-153506]
    hostname: internal-v6mx.c.findmine-153506.internal
    socket-fqdn: internal-v6mx.c.findmine-153506.internal.
    socket-hostname: internal-v6mx

=========
Collector
=========

  Running Checks
  ==============
    cpu
    ---
      Total Runs: 12348
      Metrics: 6, Total Metrics: 74082
      Events: 0, Total Events: 0
      Service Checks: 0, Total Service Checks: 0

    disk
    ----
      Total Runs: 12348
      Metrics: 66, Total Metrics: over 100K
      Events: 0, Total Events: 0
      Service Checks: 0, Total Service Checks: 0

    file_handle
    -----------
      Total Runs: 12348
      Metrics: 1, Total Metrics: 12348
      Events: 0, Total Events: 0
      Service Checks: 0, Total Service Checks: 0

    http_check
    ----------
      Total Runs: 12348
      Metrics: 3, Total Metrics: 37042
      Events: 0, Total Events: 0
      Service Checks: 1, Total Service Checks: 12348

    http_check
    ----------
      Total Runs: 12348
      Metrics: 3, Total Metrics: 37044
      Events: 0, Total Events: 0
      Service Checks: 1, Total Service Checks: 12348

    io
    --
      Total Runs: 12348
      Metrics: 26, Total Metrics: over 100K
      Events: 0, Total Events: 0
      Service Checks: 0, Total Service Checks: 0

    load
    ----
      Total Runs: 12348
      Metrics: 6, Total Metrics: 74088
      Events: 0, Total Events: 0
      Service Checks: 0, Total Service Checks: 0

    memory
    ------
      Total Runs: 12348
      Metrics: 14, Total Metrics: over 100K
      Events: 0, Total Events: 0
      Service Checks: 0, Total Service Checks: 0

    network
    -------
      Total Runs: 12348
      Metrics: 20, Total Metrics: over 100K
      Events: 0, Total Events: 0
      Service Checks: 0, Total Service Checks: 0

    ntp
    ---
      Total Runs: 12348
      Metrics: 1, Total Metrics: 12085
      Events: 0, Total Events: 0
      Service Checks: 1, Total Service Checks: 12348

    process
    -------
      Total Runs: 12348
      Metrics: 16, Total Metrics: over 100K
      Events: 0, Total Events: 0
      Service Checks: 1, Total Service Checks: 12348

    process
    -------
      Total Runs: 12348
      Metrics: 16, Total Metrics: over 100K
      Events: 0, Total Events: 0
      Service Checks: 1, Total Service Checks: 12348

    uptime
    ------
      Total Runs: 12348
      Metrics: 1, Total Metrics: 12348
      Events: 0, Total Events: 0
      Service Checks: 0, Total Service Checks: 0

========
JMXFetch
========

  Initialized checks
  ==================
    no checks

  Failed checks
  =============
    no checks

=========
Forwarder
=========

  CheckRunsV1: 12349
  IntakeV1: 941
  RetryQueueSize: 0
  Success: 25639
  TimeseriesV1: 12349

  API Keys status
  ===============
    https://6-0-3-app.agent.datadoghq.com,*************************7e41c: API Key valid

==========
Logs Agent
==========

  Logs Agent is not running

=========
DogStatsD
=========

  Checks Metric Sample: 2.438814e+06
  Event: 1
  Events Flushed: 1
  Number Of Flushes: 12349
  Series Flushed: 1.987483e+06
  Service Check: 222264
  Service Checks Flushed: 234595
  Dogstatsd Metric Sample: 120461

Describe what happened:
The Datadog agent unit goes into an inactive state and does not restart automatically. I believe the root cause is a journald crash (when the system becomes overloaded it kills journald) which in turn kills log pipes for certain processes (included datadog-agent) and the agent doesn't recover.
Describe what you expected:
The agent restarts are journald crashes.
Steps to reproduce the issue:

Stop systemd-journald (sudo systemctl stop systemd-journald).
After about 10 seconds observe that datadog-agent goes to inactive and doesn't restart.

Additional environment details (Operating System, Cloud provider, etc):
Running on Ubuntu 16.04 in Google Compute Engine. systemd version 229-4ubuntu21.1. It sounds like it could be a systemd issue and related to https://bugs.freedesktop.org/show_bug.cgi?id=84923. But I'm not quite sure...
Perhaps the agent should be catching and handling SIGPIPE? More information about this at https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html#Stream logging.
The status of the unit before failure:
andy@internal-v6mx:~$ sudo systemctl status datadog-agent
● datadog-agent.service - "Datadog Agent"
   Loaded: loaded (/lib/systemd/system/datadog-agent.service; enabled; vendor preset: enabled)
   Active: active (running) since Wed 2018-04-04 23:23:33 UTC; 1min 0s ago
 Main PID: 5711 (agent)
    Tasks: 16
   Memory: 39.1M
      CPU: 885ms
   CGroup: /system.slice/datadog-agent.service
           └─5711 /opt/datadog-agent/bin/agent/agent start -p /opt/datadog-agent/run/agent.pid

Apr 04 23:24:19 internal-v6mx agent[5711]: 2018-04-04 23:24:19 UTC | INFO | (runner.go:246 in work) | Running check load
Apr 04 23:24:19 internal-v6mx agent[5711]: 2018-04-04 23:24:19 UTC | INFO | (runner.go:302 in work) | Done running check load
Apr 04 23:24:19 internal-v6mx agent[5711]: 2018-04-04 23:24:19 UTC | INFO | (runner.go:246 in work) | Running check memory
Apr 04 23:24:19 internal-v6mx agent[5711]: 2018-04-04 23:24:19 UTC | INFO | (runner.go:302 in work) | Done running check memory
Apr 04 23:24:19 internal-v6mx agent[5711]: 2018-04-04 23:24:19 UTC | INFO | (runner.go:246 in work) | Running check network
Apr 04 23:24:19 internal-v6mx agent[5711]: 2018-04-04 23:24:19 UTC | INFO | (runner.go:302 in work) | Done running check network
Apr 04 23:24:19 internal-v6mx agent[5711]: 2018-04-04 23:24:19 UTC | INFO | (runner.go:246 in work) | Running check ntp
Apr 04 23:24:19 internal-v6mx agent[5711]: 2018-04-04 23:24:19 UTC | INFO | (runner.go:302 in work) | Done running check ntp
Apr 04 23:24:19 internal-v6mx agent[5711]: 2018-04-04 23:24:19 UTC | INFO | (runner.go:246 in work) | Running check uptime
Apr 04 23:24:19 internal-v6mx agent[5711]: 2018-04-04 23:24:19 UTC | INFO | (runner.go:302 in work) | Done running check uptime

And after failure:
andy@internal-v6mx:~$ sudo systemctl status datadog-agent
● datadog-agent.service - "Datadog Agent"
   Loaded: loaded (/lib/systemd/system/datadog-agent.service; enabled; vendor preset: enabled)
   Active: inactive (dead) since Wed 2018-04-04 23:24:34 UTC; 4s ago
  Process: 5711 ExecStart=/opt/datadog-agent/bin/agent/agent start -p /opt/datadog-agent/run/agent.pid (code=killed, signal=PIPE)
 Main PID: 5711 (code=killed, signal=PIPE)

Apr 04 23:24:19 internal-v6mx agent[5711]: 2018-04-04 23:24:19 UTC | INFO | (runner.go:246 in work) | Running check load
Apr 04 23:24:19 internal-v6mx agent[5711]: 2018-04-04 23:24:19 UTC | INFO | (runner.go:302 in work) | Done running check load
Apr 04 23:24:19 internal-v6mx agent[5711]: 2018-04-04 23:24:19 UTC | INFO | (runner.go:246 in work) | Running check memory
Apr 04 23:24:19 internal-v6mx agent[5711]: 2018-04-04 23:24:19 UTC | INFO | (runner.go:302 in work) | Done running check memory
Apr 04 23:24:19 internal-v6mx agent[5711]: 2018-04-04 23:24:19 UTC | INFO | (runner.go:246 in work) | Running check network
Apr 04 23:24:19 internal-v6mx agent[5711]: 2018-04-04 23:24:19 UTC | INFO | (runner.go:302 in work) | Done running check network
Apr 04 23:24:19 internal-v6mx agent[5711]: 2018-04-04 23:24:19 UTC | INFO | (runner.go:246 in work) | Running check ntp
Apr 04 23:24:19 internal-v6mx agent[5711]: 2018-04-04 23:24:19 UTC | INFO | (runner.go:302 in work) | Done running check ntp
Apr 04 23:24:19 internal-v6mx agent[5711]: 2018-04-04 23:24:19 UTC | INFO | (runner.go:246 in work) | Running check uptime
Apr 04 23:24:19 internal-v6mx agent[5711]: 2018-04-04 23:24:19 UTC | INFO | (runner.go:302 in work) | Done running check uptime

@andyshinn thank you for letting us know about this. We'll take a look at what may be done on the agent side to better deal with this. Thank you for providing some resources as well 🍰


Select's chevron/arrow not working on minified version

The <select> tag is not displaying the arrow down on the minified version, probably the minifier replaced the svg+xml to svg xml.

Nice catch, you're spot on. I'm trying a different CSS minifier and open to suggestions for everybody's favorite one.


Simplify document type resolution

Context
In the contentlayer/source-files plugin there are currently two mechanisms to tell Contentlayer how map a given document (e.g. a .md file) to one of many document definitions (e.g. a BlogPost, Page, ...). The two mechanisms are:

Explicitly via the filePathPattern option provided for defineDocumentType
Implicitly by looking up a "type" field in a given document (configurable via fieldOptions.typeFieldName)

Problem
I'm seeing two problems with the current design:
A: Technical problems/limitations
When using mechanism (1) there can be situations where the provided filePathPattern can overlap between document definitions and there currently is no way to explicitly configure the "precedence" document matching behaviour of Contentlayer.
B: Hard to understand / learn
Additionally to the technical problems (A) having two different ways to do the same thing (especially when they overlap) makes things much harder to understand - especially for new Contentlayer users who e.g. might ask themselves "which approach should I use?" or "which approach is better?".
I think that providing less ways to do the same thing is the right approach in most cases as it reduces cognitive overload.
Additionally there's also the complexity resulting of the possibility of combining both mechanisms (1) + (2).
Solution
As an alternative to the current mechanisms (1) + (2) I'm proposing a single unified approach to let users specify how to map document files to document type definitions by simply implementing a resolveDocumentType function as a property in makeSource like the following:
As replacement for mechanism (1)
Assuming a content file structure like:
.
├── about.md
├── index.md
└── posts
    ├── post-1.md
    ├── post-2.md
    └── post-3.md

const Post = defineDocumentType(() => ({
  name: 'Post',
  fields: {
    // ...
  }
}))

const Page = defineDocumentType(() => ({
  name: 'Page',
  fields: {
    // ...
  }
}))

export default makeSource({
  contentDirPath: 'posts',
  documentTypes: [Post, Page],
  resolveDocumentType: (frontmatter, raw) => raw.sourceFilePath.startsWith('posts/') ? 'Post' : 'Page'
})

As replacement for mechanism (2)
Assuming each document as a frontmatter field called type
const Post = defineDocumentType(() => ({
  name: 'Post',
  fields: {
    // ...
  }
}))

const Page = defineDocumentType(() => ({
  name: 'Page',
  fields: {
    // ...
  }
}))

export default makeSource({
  contentDirPath: 'posts',
  documentTypes: [Post, Page],
  resolveDocumentType: (frontmatter, raw) => frontmatter.type
})

Feedback wanted
We'd love to hear your feedback on the proposed API change. 🙏

Copying from the discord chat:
Here's an idea that combines the above with https://github.com/contentlayerdev/contentlayer/issues/84
const ctfl = makeSource({ type: 'contentful', accessToken: /* ... */ })
const local = makeSource({ type: 'local', path: /* ... */ })

const Page = defineDocumentType(() => ({
  name: 'Page',
  source: ctfl,
  ...
}))
const Post = defineDocumentType(() => ({
  name: 'Post',
  source: local,
  contentType: 'mdx',
  resolveDocument: (frontmatter, path) => frontmatter.type,
  mdx: {remarkPlugins:[], rehypePlugins: []}
  ...
}))

export {Page, Post}

The idea is to have a clearer separation of the source from the transformation pipeline (defineDocuementType). resolveDocument would in this case be only specific only to md/mdx files.
The part that I still don't really like is that resolveDocument in defineDocumentType still takes a path. I think it's more natural for filePathPattern to exist in the makeSource section and maybe defineDocumentType can take a resolveType property?


Describe FE-BE interface depth requirements

https://github.com/black-parrot/black-parrot/blob/8a394000d4e17078ed08ea2da626f9d5e926eb60/bp_common/src/include/bp_common_aviary_pkg.vh#L43

  ,fe_queue_fifo_els: 8
  ,fe_cmd_fifo_els  : 4

I would assume that fe_cmd_fifo only needs to be 1 or 2 elements?

No actually. This caused a very subtle bug a ways back. We have two entry points for writing in the fe_cmd queue. We can write at EX1 for attaboy/pc_redirect, or we can write at EX3 for traps.  Then, we may have back to back writes, along with a latent attaboy inside the queue. Because we cannot stall, we must allocate enough entries so that the queue will always be ready by the time a trap rolls around.
We should both comment and assert that’s its true.
Aside: I think sending attaboys at EX3 would solve this and allow us a 2 entry fe_cmd fifo. And we may want to do it anyway for security / predictor accuracy reasons

Agree with asserting and commenting this info.  Attaboys: with some benchmarks we will be able to see if there are any performance implications!
M

Formalized and fixed with #772


feat(kafkatopic): creation simplification

About this change—what it does
we already have retry logic in the client no need for the retry logic in the TF and fixes acceptance tests

Tests are still failing, lets catch up to discuss this issue.


Add synergistic score of compounds

Li S, Zhang Bo, Zhang NB. 2011. Network target for screening synergistic drug
combinations with application to traditional Chinese medicine. BMC
Systems Biology. 5(1).1-13.

Superceded by #186


[WIP] Revamp implementation and add arithmetic operations support for byte type

Purpose
This PR modifies the Ballerina byte type implementation. With this PR, byte type has been moved from int registry to long registry and treated as same as int type. This PR also adds arithmetic operations support for byte type. The existing bitwise operations have been modified and missing operations are added with this PR.
Arithmatic operations such as +, -, *, /, % are now supported between byte, byte and byte, int.
This PR Fixes,

https://github.com/ballerina-platform/ballerina-lang/issues/13821
https://github.com/ballerina-platform/ballerina-lang/issues/13865

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@1a574a8). Click here to learn what that means.
The diff coverage is 77.39%.

@@            Coverage Diff            @@
##             master   #14209   +/-   ##
=========================================
  Coverage          ?   64.77%
  Complexity        ?      426
=========================================
  Files             ?     2177
  Lines             ?    96047
  Branches          ?    12825
=========================================
  Hits              ?    62216
  Misses            ?    28816
  Partials          ?     5015

Impacted Files
Coverage Δ
Complexity Δ

...ava/org/ballerinalang/model/values/BValueType.java
80% <ø> (ø)
0 <0> (?)

...ava/org/ballerinalang/bre/emitter/BalxEmitter.java
0% <ø> (ø)
0 <0> (?)

.../org/wso2/ballerinalang/programfile/Mnemonics.java
0% <ø> (ø)
0 <0> (?)

...a/org/ballerinalang/util/codegen/DefaultValue.java
85.71% <ø> (ø)
0 <0> (?)

...alang/compiler/semantics/analyzer/TypeChecker.java
86.23% <ø> (ø)
0 <0> (?)

...2/ballerinalang/programfile/PackageInfoWriter.java
90.83% <ø> (ø)
0 <0> (?)

...java/org/ballerinalang/util/codegen/Mnemonics.java
0% <ø> (ø)
0 <0> (?)

...g/wso2/ballerinalang/programfile/DefaultValue.java
100% <ø> (ø)
0 <0> (?)

...n/java/org/ballerinalang/model/util/ListUtils.java
76.31% <0%> (ø)
0 <0> (?)

...a/org/ballerinalang/util/program/BLangVMUtils.java
21.66% <0%> (ø)
0 <0> (?)

... and 25 more

Continue to review full report at Codecov.

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


Create composite prober

Fixes #3176

Proposed Changes

Update the Prober interface to take in a slice of Addressables instead of a single Addressable so that a composite prober still conforms to the interface.
Create a composite prober that will iterate through all addresses provided and probe all addresses according to their scheme.
Create tests for the composite prober to ensure it uses the correct prober for the correct scheme

/hold until this is refactored to use duckv1.AddressableStatus in the Address field

/unhold

/test channel-integration-tests-ssl


Changed behaviour of Exit button while channel scanning mode.

Hi
I noticed that the behavior of Exit button has changed while it is in channels scanning mode.
Before - while radio was scanning channels - pressing Exit button once just stopped the scanning and that's all it did.
Now - Exit button has something like two modes in two cases:

When memory scanning is running but the screen is still backlit - pressing Exit stops the scan.
When memory scanning is running but the screen backlight timeout has already turned off the light - pressing Exit once only switches back on the backlight without stopping the scan and then only after second press of Exit it stops the scan.

Is it a expected feature? I may be wrong but I think it wasn't like this before.
Not a big deal but I just wanted to make sure.
Thanks

Hello,
It was like this before. You can check with an older v2 version :)
Armel.


Fix regression in 30fa296: Missing badgeRightOffset.

This change fixes a regression introduced in 30fa296, which had the pre-iOS 7 code path for setting badgeRightOffset.

Thank you for this!


Just a merge from "upstream" 0.8.11 release (as is)

3.4 was dropped entirely, 3.5 is still failing.  subsequent PR would come to bring py34 back although leading to more failures than 3.5, but imho worth addressing

actually there were good amount of activity upstream, so I will just merge recent ones as well and push directly.  may be project will just revive in original location/under original authorship/maintenance ;)


Bigtable latency spikes every hour due to grpc reconnects

Is it possible to implement something similar to the ChannelPrimer in the Bigtable Java client to mitigate hourly spikes in latency due to underlying grpc connection shutdowns & reconnects
Java client reference: https://github.com/googleapis/java-bigtable/pull/115
Related Github issue for Java client: https://github.com/googleapis/java-bigtable-hbase/issues/1463

@coryan you seem like the most likely person to have insight on this, if not assign it back and i'll dig into it.

A change similar to googleapis/java-bigtable#115 seems possible, but requires a number of changes:

The Bigtable classes do not have a set of background threads and/or completion queues with them, we would need to add such background threads to Table, TableAdmin, etc.

Then we would need to use something like this grpc::ChannelInterface::NotifyOnStateChange, to query the state of each channel and get notified when it changes:

https://grpc.github.io/grpc/cpp/classgrpc_1_1_channel_interface.html#a2acd32839ec4e5e92fe4b796a913623f
Note that we should avoid calling GetCurrentState(true) as that might block.

Alternatively, we could simply make a "ping" call, but there is no equivalent to SELECT 1; in Bigtable-land, that would require some thinking...

So, this is a valid feature request, I will put it in the backlog, no promises on when it will be done.


Small maintenance

I am sorry but I don't want to expose heap size limit as a Cmake option. That code is useful only during development of the library and I don't think it anyone using the library would want to enable it.
The removal of that outdated code about CSV recording looks good though.

Thank you for this contribution.