Broken lexical variables in eval

At latest master (https://github.com/mruby/mruby/commit/72581696d35e8da79a3a9d606294602c83abdf9f), the following code says nothing (i.e. proc returns nil) but of cause I expected FOO.
puts eval(<<'EOS').call
foo = 'FOO'
proc { foo }
EOS

What's more interesting is,
def do_eval(code)
  eval(code)
end

puts do_eval(<<'EOS').call
foo = 'FOO'
proc { foo }
EOS

says the following, eval-ed code itself!
foo = 'FOO'
proc { foo }

After some investigations, I found https://github.com/mruby/mruby/pull/4012 is the cause of this issue. By setting ci->env is set to proc's env which encloses the eval-caller's context, inner closure refers that env too (https://github.com/mruby/mruby/blob/master/src/proc.c#L69). But that env->stack should point proc caller's stack which is placed at the next of actual one.
@take-cheeze Could you explain the detail of that PR? I cannot see https://<IP_ADDRESS>.static.iijgio.jp/jenkins/view/0-master-mrbgem/job/master-mruby-aws-sigv4/58/console now.

@i110 The behavior you expect seems more correct.
Since https://github.com/mruby/mruby/pull/3991 is merged #4012 can be reverted.
I'll check aws-sigv4 after reverted.

@take-cheeze Thank you. I filed https://github.com/mruby/mruby/pull/4039. BTW just for reference, could you give, me brief explanations of why you added these code, when you have a time?

@i110 there was some memory access error and seems there is another happening.
will investigate later.


(GH-107) Update package with new install path

Package Verifier install folder is now a shorter name to minimise issues with long paths.

@pauby your changes have been merged, thanks for your contribution 👍


Calling Event Dispatcher

I tried this:
self.uobject.MyEventDispatcher.call()
Apparently a string is needed. Not sure how to handle this.
Can you help?

Hi, use self.uobject.dispatch('MyEventDispatcher') i am working in a more python way, btw


Add adversary actor sheet

We need to add a character sheet for adversaries

Functionally complete, added new issue for styling #47


Disappeared images in GAN notes

Hi there!
Thanks for your great notes about the difficulty of training GANs. I see that some of the images in your notes are missing. I think the images are from the examples of changing a dimension in the latent z space. Can you please fix it when you have time?
Thanks

Thanks for the heads up 👍


Variables in keys are not supported

Bicep version
Bicep CLI version 0.2.328
Describe the bug
To assign a User Managed Identity to Azure Resource it is required to set an identity id as key for object userAssignedIdentities
unfortunately it is not possible to use bicep for this purpose
{
    "apiVersion": "2016-08-01",
    "type": "Microsoft.Web/sites",
    "name": "[variables('appName')]",
    "location": "[resourceGroup().location]",
    "identity": {
        "type": "UserAssigned",
        "userAssignedIdentities": {
            **"[resourceId('Microsoft.ManagedIdentity/userAssignedIdentities', variables('identityName'))]"**: {}
        }
    }
}

To Reproduce

create bicep with variable that stores id and use this variable as a key

var sysId = 'someId'

resource Function 'Microsoft.Web/sites@2020-09-01' = {
  name: 'name'
  location: 'euwest'
  identity: {
    type: 'UserAssigned'
    userAssignedIdentities: {
      sysId: {
      }
    }
  }
}

compile bicep

{
  "type": "Microsoft.Web/sites",
  "apiVersion": "2020-09-01",
  "name": "name",
  "location": "euwest",
  "identity": {
    "type": "UserAssigned",
    "userAssignedIdentities": {
      **"SysId"**: {}
    }
  }
}

it is clear to see that key is inserted as is.
Additional context
none

You need to embed the key name inside of a string and use interpolation like so:
var sysId = 'someId'

resource Function 'Microsoft.Web/sites@2020-09-01' = {
  name: 'name'
  location: 'euwest'
  identity: {
    type: 'UserAssigned'
    userAssignedIdentities: {
      '${sysId}': {}
    }
  }
}


Summary of the license?

I've never heard of it and don't feel like reading a ton of legal jargon. Is the lib free to use or what? If it is, MIT it like every single other modern lib out there?

Yes, it is an open source license, you can use it for free.


get exception when Push to Remote

Hi every time i tried to "Push to Remote" always get this exception. im using auto git. When im using "Open Shell" use git commit then git push, it works just fine.
`See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.
at PassWinmenu.ExternalPrograms.Git.CommitFile(String filePath)
at PassWinmenu.Windows.DialogCreator.AddPassword()
at PassWinmenu.WinApi.Notifications.<>c__DisplayClass11_0.b__1(Object sender, EventArgs args)
at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ToolStrip.WndProc(Message& m)
at System.Windows.Forms.ToolStripDropDown.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
`

I do have the same issue, I tried to modify config for git native but no changes

Thanks for your report, and my apologies for responding so late.
I haven't been able to discover the underlying cause yet, but I created a new build which should at least prevent the application from crashing if the same condition occurs. Instead, it will report an error in this case.
You can download the new version here: https://ci.appveyor.com/api/buildjobs/rar2agcxh6jc8y1v/artifacts/pass-winmenu%2Fbin%2FRelease%2Fpass-winmenu.exe
Could you please test it again with this build? If you get an error again, please report the error message and the logs (right click the notification area icon -> More actions -> View logs). Thanks!

Thanks for your report, and my apologies for responding so late.
I haven't been able to discover the underlying cause yet, but I created a new build which should at least prevent the application from crashing if the same condition occurs. Instead, it will report an error in this case.
You can download the new version here: https://ci.appveyor.com/api/buildjobs/rar2agcxh6jc8y1v/artifacts/pass-winmenu%2Fbin%2FRelease%2Fpass-winmenu.exe
Could you please test it again with this build? If you get an error again, please report the error message and the logs (right click the notification area icon -> More actions -> View logs). Thanks!

i just tried it... its worked. thanks!

i just tried it... its worked. thanks!

#73

I've just published v1.11.1, which fixes this issue.
I'll close the issue now, but if the problem persists, feel free to open a new issue, or to reopen this one.


Implement endpoints to delete course creation requests

Subtask to set up the backend endpoints for the user story defined at https://github.com/JamesPartsafas/ConcordiaCurriculumManager/issues/7
Create endpoint so users can delete create course requests
[Story Points: 2]
[Priority: High]
[Risk: Medium]

demo


All samplers are deprecated

Reading the<EMAIL_ADDRESS>docs, to customize the sampler option we should use:

const { ParentBasedSampler } = require('@opentelemetry/core')
const { AlwaysOnSampler } = require('@opentelemetry/core')
const { AlwaysOffSampler } = require('@opentelemetry/core')

but all these classes are deprecated
https://github.com/open-telemetry/opentelemetry-js/blob/40ee3825a420feeb682dfb8a546dc8106c420819/packages/opentelemetry-core/src/trace/sampler/ParentBasedSampler.ts#L32
What should I use?
Thks

This is a case of bad documentation. You should use the samplers in sdk-trace-base.

Thank you for reporting this! Updated the document of the sdk-trace-base at https://github.com/open-telemetry/opentelemetry-js/pull/3319.


Optimising high dispatch and db query counts in broad model

Checklist

[X] I have looked into the README and have not found a suitable solution or answer.
[X] I have looked into the documentation and have not found a suitable solution or answer.
[X] I have searched the issues and have not found a suitable solution or answer.
[X] I have upgraded to the latest version of OpenFGA and the issue still persists.
[X] I have searched the OpenFGA Community and have not found a suitable solution or answer.
[X] I agree to the terms within the OpenFGA Code of Conduct.

Description
We are experiencing high latency and failing Check queries in production using the auth model below. The problem seems to stem from a particular set of users who have relations with multiple tenants and projects. When a check is performed with one of these users as the object, we are seeing dispatch counts in the hundreds and db query counts over a 100.
This is causing queries to timeout and putting undue pressure on the db.
Is there anything we could do to make the model perform better while still maintaining the same intent of the model. For example we tried to substitute owner_tenant and owner_project with [tenant#can_view_users, project#can_view_users], but this made the performance even worse.
Another option I am aware of is decreasing the OPENFGA_RESOLVE_NODE_BREADTH_LIMIT, but I'm afraid that will lead to an unacceptable number of false negatives.
Any ideas would be appreciated?
Expectation
I'd expect to be able check relations in a timely manner even for objects that have many relations.
Reproduction

Use the model below.
Create a user[0] with many owner_tenant and owner_project relations
Create another user[1] with one shared tenant
Check user[1] can_view user[0]
Observe high dispatch and db query counts

Store data
model
  schema 1.1

type project
  relations
    define admin: [user] or owner
    define can_view: viewer
    define can_view_users: viewer
    define editor: [user] or admin
    define member: [user] or viewer
    define owner: [user] or super_admin from owner_tenant
    define owner_tenant: [tenant]
    define revoked: [user] or revoked from owner_tenant
    define viewer: [user] or editor

type tenant
  relations
    define admin: [user] or super_admin
    define can_view: (member or external_member) but not revoked
    define can_view_users: member but not revoked
    define editor: [user] or admin
    define external_member: [user]
    define member: [user] or editor
    define revoked: [user]
    define super_admin: [user]

type user
  relations
    define can_edit: owner
    define can_list_memberships: owner
    define can_view: owner or can_view_users from owner_tenant or can_view_users from owner_project
    define owner: [user]
    define owner_project: [project]
    define owner_tenant: [tenant]

OpenFGA version
1.5.3
How are you running OpenFGA?
In Kubernetes
What datastore are you using?
Postgres
OpenFGA Flags
OPENFGA_CHECK_QUERY_CACHE_ENABLED, OPENFGA_CHECK_QUERY_CACHE_TTL=30s, OPENFGA_DATASTORE_MAX_OPEN_CONNS=500, OPENFGA_MAX_CONCURRENT_READS_FOR_CHECK=4000000, OPENFGA_MAX_CONCURRENT_READS_FOR_LIST_OBJECTS=4000000
Logs
{
	"content": {
		"timestamp": "2024-05-07T09:05:15.952Z",
		"service": "openfga",
		"message": "grpc_req_complete",
		"attributes": {
			"store_id": "01HAM89A85W7HT9MS4KTBN4NPT",
			"raw_request": {
				"store_id": "01HAM89A85W7HT9MS4KTBN4NPT",
				"trace": false,
				"tuple_key": {
					"user": "user:c03fbcc5-5fd8-4711-9be6-33ae29384606",
					"relation": "can_view",
					"object": "user:2d65e2c0-5a9a-47b6-bb8c-236d76f50fdb"
				},
				"authorization_model_id": "01HQ8AZT8BPM228F1E0F5258Y2"
			},
			"level": "info",
			"grpc_service": "openfga.v1.OpenFGAService",
			"datastore_query_count": 515,
			"grpc_code": 0,
			"grpc_method": "Check",
			"grpc_type": "unary",
			"build": {
				"commit": "ebf39989ec19c8c3d8a7646e308bcffca5748874",
				"version": "v1.5.3"
			},
			"peer": {
				"address": "<IP_ADDRESS>:37840"
			},
			"dispatch_count": 658,
			"timestamp_milli": "1715072715952",
			"raw_response": {
				"allowed": false,
				"resolution": ""
			},
			"request_id": "629dbfe5-17af-4be2-a9cd-5004be4947eb",
			"user_agent": "openfga-sdk js/0.3.5",
			"timestamp":<PHONE_NUMBER>.9523919,
			"authorization_model_id": "01HQ8AZT8BPM228F1E0F5258Y2"
		}
	}
}

Hi @KlausVii, sorry for the delay!

Is there anything we could do to make the model perform better

If your model had relations with overlapping definitions, such as
define c: a or b
define d: a or b

Then we could introduce define intermediate: a or b and then define c: intermediate, define d: intermediate to improve cache hit ratio. However, your model looks very optimized in this front already, so not much we can do here.

Another option I am aware of is decreasing the OPENFGA_RESOLVE_NODE_BREADTH_LIMIT, but I'm afraid that will lead to an unacceptable number of false negatives.

This should not be the case - that flag is meant to increase the degree of concurrency that queries can have. It doesn't change the final outcome.

A few things you can try:

OPENFGA_DATASTORE_METRICS_ENABLED set to true, and then monitor your connection pool. If your open conns are regularly reaching max open conns, try increasing OPENFGA_DATASTORE_MAX_OPEN_CONNS. But only do this if your database allows it.
The default for OPENFGA_REQUEST_TIMEOUT is 3s, you can try increasing it. This is not ideal as latency will increase, but you should experience less errors.

In the short term we are planning to work on some performance improvements that could help your use case, (e.g. https://github.com/openfga/openfga/issues/1012)

Hmm, we've done some hacks to bypass openfga for the problematic checks for now. Increasing the timeout was not an acceptable solution for us. The max conns is already quite high and the query was negatively affecting other checks.
When are you planning on implementing this https://github.com/orgs/openfga/projects/1?pane=issue&itemId=5756062 ?
Would that help?

@KlausVii if you have some sample tuples to share that would be great. That being said, in the meantime, the problem here stems from bi-directional relationships between user and tenant. That is user[0] --> tenant --> user[1...N]. Since OpenFGA is a directed graph, modeling that bi-directional query pattern causes high fan-out with respect to the user[1...N] --> tenant --> user[0] (reverse query) pattern.
Starting with user[0] you have to expand all of the owner_tenant and owner_project relationships for that subject, and for each one of them (could be hundreds or thousands it sounds like) you have to check if user[1] is related through the can_view_users relationship. FGA Indexes will definitely help with this pattern as the lookup for user[1] for each of the tenants and projects will reduce from O(N) lookup to O(1) 👍
Shoot those tuples over though and we can see if there are some other options in the meantime. Thanks for the report!

Heres a sample store export with an example of a very expensive can_view check.
slow-store.txt (its actually yaml, but gh doesn't allow uploading those)
To reproduce:

import store
open playground
follow logs
run assertions
observe logs and see that the last can_view leads to excessive dispatches and db queries like this

{
  "grpc_method": "Check",
  "tuple_key": {
    "user": "user:f3659913-cde0-4aeb-b23f-dffb3176662b",
    "relation": "can_view",
    "object": "user:05d2c261-cec3-43d7-9b26-ef07b083f3ee"
  },
  "raw_response": {
    "allowed": false,
    "resolution": ""
  },
  "datastore_query_count": 829,
  "dispatch_count": 852
}

This is the worst case, where no relation to view exists, but even the more common successful one like this can lead to many db queries:
{
  "tuple_key": {
    "user": "user:0904c37c-a06b-41dc-8c29-5d66540137e9",
    "relation": "can_view",
    "object": "user:05d2c261-cec3-43d7-9b26-ef07b083f3ee"
  },
  "raw_response": {
    "allowed": true,
    "resolution": ""
  },
  "datastore_query_count": 71,
  "dispatch_count": 702
}

Also is there indication to when the indexing will be implemented?

@KlausVii FYI we're working on an improvement for your use case here: https://github.com/openfga/openfga/pull/1735. It's not finalized yet, but keep an eye on it because once we merge to main I'd love it if you could try it out :)

Hey, just upgraded from 1.5.3 to 1.5.8. The performance has gotten better, especially for request that return allowed. However a large number disallowed checks still cause openfga to start timing out and struggling.

Hi @KlausVii! Thank you for the feedback.

However a large number disallowed checks still cause openfga to start timing out and struggling.
Have you noticed an improvement over 1.5.3 or still the same level when it comes to disallowed checks? We're still working on more enhancements related to optimizing the check code and we believe there's still several tricks up our sleeve to improve performance there, but continuous feedback helps, so thanks!

Side-note: Please note that we have a critical security issue in v1.5.7 and v1.5.8 and it's better to avoid upgrading your production workload until v1.5.9 is out - https://github.com/openfga/openfga/security/advisories/GHSA-3f6g-m4hr-59h8

It looks like the dispatch_count has been reduced, but the datastore_query_count remains high. Examples for the same query:
1.5.3:
"datastore_query_count": 488, "dispatch_count": 486

1.5.8
"datastore_query_count": 488, "dispatch_count": 97,

I would have thought datastore queries would be capped by dispatch, but i guess my understanding of these metrics is not crystal.

@rhamzeh PS: thanks for the security alert. Might be an idea to include such notices on the release notes, so people know to avoid the release.


Using polygons or paths in the annotators

We can specify an annotator like this:
sample_poly=dict(
    Longitude = [-10114986, -10123906, -10130333, -10121522, -10129889, -10122959],
    Latitude  = [  3806790,   3812413,   3807530,   3805407,   3798394,   3796693])

gvdata = gv.Polygons(data=[sample_poly], crs=ccrs.GOOGLE_MERCATOR)

annotator = PolyAnnotator(polys=gvdata)
annotator.panel()

This will produce a panel with the map on the left and tabs on the right for the polygon table and the vertex table. The vertex table is the listing of the lat/longs for all the vertices on the polygon. This works as it should.
Now, with the annotators we can easily switch this to paths using
gvdata = gv.Path(data=[sample_poly], crs=ccrs.GOOGLE_MERCATOR)
which will properly display paths on the map. However, the vertex table will not populate when a path is selected.
In order to get the table to populate properly, one must use:
annotator = PolyAnnotator(path_type=hv.Path, polys=gvdata) to explicitly specify the path_type.
It's quite confusing that path_type is not required for proper map visualization but IS required for table visualization.

I can't reproduce this anymore, please reopen if you can @kcpevey.


[stdlib] Refactor LoggingWrapper test utility with conditional conformance

This code greatly benefits from conditional conformance, by re-using the same logging shims when going down the hierarchy. Hopefully this will make it easier to maintain, as adding customization points is otherwise quite a pain (and we haven't been adding them as we go... oops)

@swift-ci please test


fix: Stop the scrollbar in the Change Dataset modal from scrolling down to the pagination component

SUMMARY
Different from the ask in the related issue #15935, this PR does not stop the scrollbar from going over the sticky header. In order to stop the scrollbar from appearing over the sticky header, a complete refactor of the TableCollection component would be required. In fact, that behaviour is standard in the HTML tables. A deviation from the standard HTML table would be required.
One example where the scrollbar isn't appearing over the header would be the "Table" chart. That comes with a full custom implementation of the table indeed.
This PR will at least solve the most perceivable issue with the scrollbar going all the way to the bottom.
BEFORE

AFTER
https://user-images.githubusercontent.com/60598000/129215292-6d07c6b7-f6d9-4c74-8133-90c45ac59a7f.mp4
TESTING INSTRUCTIONS

Open Explore
Click on "Change dataset"
Observe the table and scroll
Make sure the scrollbar does not appear down to the pagination

ADDITIONAL INFORMATION

[x] Has associated issue: #15935
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

/testenv up

I have noticed a cosmetic issue that is also affecting main. With no pagination, there is a big blank space at the bottom. I will file a separate issue for this problem and solve it in a separate PR as it is not related to the scrollbar.
https://user-images.githubusercontent.com/60598000/129256458-4a582b35-11d2-42a0-afb0-c3911b5957d8.mp4


docs(plugin-dev) new 0.11.0 cache invalidation mechanism

@hishamhm Thanks! All updated, including the plugins ordering table!


Relocating experimental and deprecated tests

Three non-SSA test files are NOT located in the experimental/deprecated directories,
but their associated detections are located there.  Moving those test files to the
experimental/deprecated directories.
PR Template for new Detections
For Authors:

[ ] Make sure that CI/CD detection-testing and build-and-validate jobs passed ✔.

For Reviewers:

[ ] Verify CI/CD jobs have passed without errors.
[ ] Validate SPL logic.
[ ] Validate tags, description, and how to implement.
[ ] Validate name matches <platform>_<mitre att&ck technique>_<short description>
[ ] Verify references match analytic.
[ ] Is there an Atomic Test?

Resolving merge conflicts is harder than closing and reopening this PR due to a number of factors. Closing and will open a new PR


⚠ Fortnite has degraded performance

In 42c09ad, Fortnite (https://fortnite.com) experienced degraded performance:

HTTP code: 200
Response time: 1536 ms

Resolved: Fortnite performance has improved in 8b48218.


New check: detect change of ownership

Return true if there was a chance, false otherwise.

https://api.github.com/repos/googleprojectzero/fuzzilli
it is easy to get current owner, but hard to check which was the last one.

 "owner": {
    "login": "googleprojectzero",

I'm interested in taking this one on. Before I start, I'd like to discuss how to go about doing this.
I don't see anything on Github's API that would allow us to query for a repo's past owners. I think we'll need to store this data ourselves and have scorecard query for it. We could record the owners for the repos we track as part of the cron process and store it in GCS bucket. Then when scorecard runs, it could download the file(s) it needs from the bucket. Maybe not at first, but we will want to shard the data across files within the bucket so that scorecard can download a reasonable size chunk if it's only checking one repo.
If the repo being checked is not present in the saved data, we'd have to give an inconclusive result.
Feedback on this approach?

I'm interested in taking this one on. Before I start, I'd like to discuss how to go about doing this.
I don't see anything on Github's API that would allow us to query for a repo's past owners. I think we'll need to store this data ourselves and have scorecard query for it. We could record the owners for the repos we track as part of the cron process and store it in GCS bucket. Then when scorecard runs, it could download the file(s) it needs from the bucket. Maybe not at first, but we will want to shard the data across files within the bucket so that scorecard can download a reasonable size chunk if it's only checking one repo.
If the repo being checked is not present in the saved data, we'd have to give an inconclusive result.
Feedback on this approach?

This is a good approach. But we are in the process of designing sharding and coming up with long-term plans to scale.  I would recommend that we wait until then.
Thanks for picking up the issue and all your contributions @chrismcgehee!

Just to clarify, are you saying I can start working on this issue now, but I should not worry about sharding at this time?

Just to clarify, are you saying I can start working on this issue now, but I should not worry about sharding at this time?

Not worry about right now. There are several other to pick from list - https://github.com/ossf/scorecard/issues?q=is%3Aissue+is%3Aopen+"New+check" or https://github.com/ossf/scorecard/milestone/1
but whichever you pick, leave a comment in bug to avoid duplication/conflict. thanks @chrismcgehee for your contributions!

This feature does not align with the current project focus. If there is no feedback in the next 7 days to the contrary, then this issue will be closed.


fix: fix types for cloudflare:queue args

🔗 Linked issue

❓ Type of change

[ ] 📖 Documentation (updates to the documentation, readme, or JSdoc annotations)
[x] 🐞 Bug fix (a non-breaking change that fixes an issue)
[ ] 👌 Enhancement (improving an existing functionality like performance)
[ ] ✨ New feature (a non-breaking change that adds functionality)
[ ] 🧹 Chore (updates to the build process or auxiliary tools and libraries)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description
The queue event(MessageBatch) is wrong types.
What was originally supposed to be MessageBatch, I looked it up today and found that it was written as CloudflareEmailContext.
I just fixed it.

📝 Checklist

[x] I have linked an issue or discussion.
[ ] I have updated the documentation accordingly.

https://github.com/unjs/nitro/issues/2587#issuecomment-2240766921

additional fix: types for cloudflare:queue args
CloudflareEmailContext.raw to ReadableStream from ReadableStream

I have something additional to ask.
Testing with Nuxt nightly. The error occurs during the build process.
 ERROR  Cannot resolve "cloudflare:email" from "/Users/jioo0224/Desktop/nodejs/sh0rt-kr-email-worker/node_modules/cloudflare-email-kit/dist/index.js" and externals are not allowed!                                                 10:49:18 AM

  at Object.resolveId (node_modules/nitro/dist/rollup/index.mjs:1570:17)
  at async PluginDriver.hookFirstAndGetPlugin (node_modules/rollup/dist/es/shared/node-entry.js:19708:28)
  at async resolveId (node_modules/rollup/dist/es/shared/node-entry.js:18389:26)
  at async ModuleLoader.resolveId (node_modules/rollup/dist/es/shared/node-entry.js:18792:15)
  at async Object.resolveId (node_modules/@rollup/plugin-commonjs/dist/es/index.js:590:10)
  at async PluginDriver.hookFirstAndGetPlugin (node_modules/rollup/dist/es/shared/node-entry.js:19708:28)
  at async resolveId (node_modules/rollup/dist/es/shared/node-entry.js:18389:26)
  at async ModuleLoader.resolveId (node_modules/rollup/dist/es/shared/node-entry.js:18792:15)
  at async ModuleLoader.resolveDynamicImport (node_modules/rollup/dist/es/shared/node-entry.js:19196:82)
  at async node_modules/rollup/dist/es/shared/node-entry.js:19083:32

I would like to ask whether this is also a problem with Nitro and, if so, where I should fix it.

I don't know think so.
Maybe this rule or "cloudflare-email-kit" plugin is fault.
Before, "cloudflare-email-kit" module's dependency is all of "browser" dependencies. So, I think that rules is problem...

Thanks for PR. Fixed via https://github.com/unjs/nitro/pull/2711


Fix the issue of no space in CI

This PR is

to introduce two conditions variables checkout_polyfill and checkout_samples, those webnn-polyfill(608M), webnn-samples(700M) and test-data(1.2G) dependencies repos would be checkout by default
to enable checkout onnxruntime(858M) dependency repo by default

Following table shows the checkout status in CI:

CI \ Repo
webnn-polyfill (608M) + test-data(1.2G)
webnn-samples(700M) + test-data(1.2G)
onnxruntime (858M)

CI for null backend
NO
NO
NO

CI for DML/OpenVINO/oneDNN native backends
YES(1)
NO
NO

CI for WebNN-native Binding for node.js
YES
NO
NO

CI for MLAS backend (TODO)
YES(1)
NO
YES

Note:
(1) Actually in CI for native backends, only test-data repo is required to checkout for testing End2End tests(model tests).
@fujunwei @huningxin PTAL, thanks.

Merge it, thanks.


Can i add custom label into node?

@eisman Thanks for the neo4jd3 you make, very helpful for me, but can i add label for each node?
thanks...

Hi @laxen00  I'm really new to the web and I'm trying to replicate this present visualization on my GitHub pages.I have forked and change the GitHub page settings. But it just keeps displaying nothing more than the README.md. I don't understand where I'm going wrong. Could you please tell me how?
Thanks in advance :)

I need this as well @laxen00 how did you solve the problem?


Error handling

Hi quick question. In a very specific env I keep getting exit status 1 and I have no idea how to go about troubleshooting this.
For context:
docker image with alpine linux on my arch linux development machine works fine
same docker image on a digital ocean vps returns exit status one from ffmpeg

it's true problem that ffmpeg-go do not print enough error detail for troubleshooting. I will do some work to optimize that. For now, you can just use method GetArgs() which print all args generated for command ffmpeg, and run command ffmpeg manually with these args, do this will get you more information about the failure.

Right I see, thanks!

In this pr: https://github.com/u2takey/ffmpeg-go/pull/12, an option: ErrorToStdOut, WithErrorOutput and  is imported, with which error output from FFmpeg will be ouputed to stdout or a writer


Layer Visibility Conditions

I'm sorry, this in not a bug report, but a question. (Couldn't find a place to send my question)
When I'm trying to set up a new conditional layer, it encourages me to use Layer Visibility Conditions. I can guess what it does from its name, but where are these conditions tweaked, I can't find. Can someone help?
Thank you and again, sorry.

Have a look at the guide https://aurora-rgb.github.io/Docs/advanced-topics/overrides-system/

Thanks


i18n(ko-KR): update tutorial/

Description (required)

update tutorial/
#9240
#10209
#10223

Related issues & labels (optional)

Closes #
Suggested label:

Lunaria Status Overview
🌕 This pull request will trigger status changes.

Learn more
By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.
You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

File
Note

ko/tutorial/0-introduction/1.mdx
Localization changed, will be marked as complete.

ko/tutorial/0-introduction/index.mdx
Localization changed, will be marked as complete.

ko/tutorial/1-setup/2.mdx
Localization changed, will be marked as complete.

ko/tutorial/1-setup/5.mdx
Localization changed, will be marked as complete.

ko/tutorial/1-setup/index.mdx
Localization changed, will be marked as complete.

ko/tutorial/3-components/4.mdx
Localization changed, will be marked as complete.

ko/tutorial/5-astro-api/1.mdx
Localization changed, will be marked as complete.

ko/tutorial/5-astro-api/2.mdx
Localization changed, will be marked as complete.

ko/tutorial/5-astro-api/3.mdx
Localization changed, will be marked as complete.

ko/tutorial/5-astro-api/index.mdx
Localization changed, will be marked as complete.

ko/tutorial/6-islands/2.mdx
Localization changed, will be marked as complete.

ko/tutorial/6-islands/3.mdx
Localization changed, will be marked as complete.

ko/tutorial/6-islands/4.mdx
Localization added, will be marked as complete.

Warnings reference

Icon
Description

🔄
The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.

The changes in this PR are included in #10258. I will close this PR when #10258 is merged.


Add tests for VOC(Segmentation|Detection) and fix existing bugs

This adds tests for VOCSegmentation and VOCDetection. Additionally, this fixes two existing bugs:

When using year="2007-test" we currently allow all image_splits
https://github.com/pytorch/vision/blob/22c548b0ec02de3ccd606ba227f4c03eb54f98f9/torchvision/datasets/voc.py#L91-L93
https://github.com/pytorch/vision/blob/22c548b0ec02de3ccd606ba227f4c03eb54f98f9/torchvision/datasets/voc.py#L174-L176
The downloaded archive only contains the test split. Thus, using year="2017-test" with any other image_set="test" only works if the archive for year="2007" was extracted before.
I've deprecated the year="2007-test", image_set="test" combination in favor of year="2007", image_set="test" which is more clear.

We currently force UNIX paths
https://github.com/pytorch/vision/blob/22c548b0ec02de3ccd606ba227f4c03eb54f98f9/torchvision/datasets/voc.py#L107
https://github.com/pytorch/vision/blob/22c548b0ec02de3ccd606ba227f4c03eb54f98f9/torchvision/datasets/voc.py#L191

Both classes are mostly the same so I've opted to create a common base class which handles the download and preparation. Merely the access is now handled individually.

There are conflicts now, can you address those?


keep consistence of name TASK-ID

Keep language TASK-ID consistence of container list with task list.
Signed-off-by: xiekeyang<EMAIL_ADDRESS>

Sorry it is really for container id.

Codecov Report

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

@@           Coverage Diff           @@
##           master    #1089   +/-   ##
=======================================
  Coverage   54.51%   54.51%
=======================================
  Files          16       16
  Lines        1229     1229
=======================================
  Hits          670      670
  Misses        386      386
  Partials      173      173

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 cd7bbf2...3d45f85. Read the comment docs.


start a login shell at login

fixes #35
unsure how to test or apply, see #36

closing this myself due to inactivity, though it may still be useful to others


Sampling and reweighting scripts are working with SMILES string using the openff-toolkit

Description
We have previously relied on the CHARMM topology/parameter files to set up a system for sampling and reweighting, this is changed in the scripts that we provide as part of this package. This change will make it easier for other scientists to use this package since only the SMILES string needs to be specified.
Todos

[x] System generation and parametrization with openff-toolkit

Status

[ ] Ready to go

Codecov Report

Merging #72 (e03c015) into main (1173246) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head e03c015 differs from pull request most recent head 30cc518. Consider uploading reports for the commit 30cc518 to get more accurate results

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files


statedb: Add REST API for statedb queries

This implements support for remotely querying the contents of StateDB tables over the REST API. It is implemented in terms of raw queries, e.g. the table, index names and the key []byte is transferred to the server which then performs the query against the given table and index. This allows reuse of the Index[Obj, Key] types and thus provides the same experience as server side:
    table := statedb.NewRemoteTable[*tables.Device](client, "devices")

    // Query devices by revision, least recently changed objects first.
    iter, err := table.LowerBound(ctx, statedb.ByRevision[*tables.Device](0))
    for device, revision, ok := iter.Next(); ok; device, revision, ok = iter.Next { ... }

    // Find devices by name: all devices that start with "e" (or higher):
    iter, err = table.LowerBound(ctx, tables.DeviceNameIndex("e"))

    // Exact matches:
    iter, err = table.Get(ctx, tables.DeviceNameIndex("eth0"))
    if device, revision, ok := iter.Next(); ok { ... }

On top of this API a generic utility is implemented in cilium-dbg/cmd/statedb.go to allow adding the ability to pretty-print the contents of any table whose object implements 'statedb.TabWritable':
	// "cilium-dbg statedb devices"
	statedbTableCommand[*tables.Device]("devices")

Example output:
  root@kind-worker:/home/cilium# cilium statedb devices
  Name              Index   Selected   Type     MTU     HWAddr              Flags                    Addresses
  lxc4446c55b3291   8       false      veth     1500    46:b9:9b:85:c2:e2   up|broadcast|multicast   fe80::44b9:9bff:fe85:c2e2
  lo                1       false      device   65536                       up|loopback              <IP_ADDRESS>, ::1
  lxc_health        71      false      veth     1500    06:d8:63:ff:20:3b   up|broadcast|multicast   fe80::4d8:63ff:feff:203b
  cilium_host       3       false      veth     1500    66:e0:0e:19:a6:9f   up|broadcast|multicast   <IP_ADDRESS>

Since go-swagger does not provide an easy way to implement proper streaming APIs this does not add support for delete events (DeleteTracker). Implementing this is more involved and would require registering a DeleteTracker and keeping it alive with some sort of keepalive mechanism.
cilium-dbg: Add statedb query support and commands to inspect statedb tables devices, routes and l2-announce.

/test

I was planning to originally build this on top of https://github.com/cilium/cilium/pull/28729 with gRPC so there'd be proper streaming RPC goodness. I decided in the end to split this off from that since we need to have proper discussions on if/how/when to introduce competition to go-swagger/openapi and how we'd migrate.

/test

/test

/test

/test


custom dp-input cannot press enter and select date

Hi.
I'm trying to make it so when user types and press enter, the date is selected. But nothing happens.
My code
<vue-date-picker
        v-model="selectedDate"
        ref="datepicker"
        :enable-time-picker="false"
        auto-apply
        text-input
        :disabled="props.disabled"
        hide-input-icon
        :format="formatDateForPreview"
        calendar-cell-class-name="dp-custom-cell"
        @update:model-value="handleUpdate"
        @cleared="clearDatepicker"
      >
        <template #dp-input="{ value, onEnter }">
          <input
              type="text"
              :value="value"
              placeholder="Add inspection date"
              class="dp-custom-input"
              @keydown.enter="onEnter"
          />
        </template>
</vue-date-picker>

Do I need to add something more then just @keydown.enter="onEnter"?

Did you find something to fix this? I would love to use custom input fields instead of the current one.


Egobundle: Scale circles

Right now the circles in the egobundle all have the same size. Alternatively we could

scale circle size according to number of nodes
scale circle size according to number of shared nodes. This would ensure that the nodes in the shared node portion would be equally spaced in all 3 circles and the connecting bands would have a constant width
Omit the circle shape and create a shape where we can have different radii for shared and unique nodes

Implement switch between only shared and all nodes


False positive on FC021

I'm getting a warning for FC021 on a block like the following:
  some_fancy_lwrp new_resource.name do
    source_dir source_dir
    flags new_resource.flags
    not_if { ::File.exists?("#{new_resource.some_dir}/#{new_resource.name}")}
  end

According to the definition I read, this shouldn't happen, as the name isn't fixed.

I ran into this same issue. It seems to be triggering the warning if the name of the resource is either only a string or only a variable which does lead to a work around.
some_fancy_lwrp "something #{new_resource.name}" do
  source_dir source_dir
  flags new_resource.flags
  not_if { ::File.exists?("#{new_resource.some_dir}/#{new_resource.name}")}
end

Although this is a work around it makes some of the resources a lot messier.


File based dev registry

What this PR solves / how to test
Fixes #[insert GH or internal issue number(s)].
Author has addressed the following

Tests

[ ] TODO (before merge)
[ ] Included
[ ] Not necessary because:

Changeset (Changeset guidelines)

[ ] TODO (before merge)
[ ] Included
[ ] Not necessary because:

Public documentation

[ ] TODO (before merge)
[ ] Cloudflare docs PR(s): https://github.com/cloudflare/cloudflare-docs/pull/...
[ ] Not necessary because:

Add file heartbeat to detect crashed workers
Add Wrangler version to files to detect back compat
Add cleanup mechanism when Wrangler tries to fetch a worker that no longer exists


Experimental features

Added a lot of EWC related features and conducted hyperparameter searches

My bad, accidentally selected wrong base to merge to


IOS - FirestackReceiveNotification is not a supported event type

On IOS I get the following error using cloud messages.
The build is fine and the app is running, just the red screen comes up.
Running on emulator or device.
FirestackReceiveNotification is not a supported event type for FirestackCloudMessaging.
Supported events are: messaging_event, messaging_error, messaging_token_refresh, ……

Code I use
FirebaseStack.cloudMessaging.listenForReceiveNotification((msg) =>{
        console.log(msg.data);
        console.log(msg.notification);
    });

FirebaseStack.cloudMessaging.subscribeToTopic("film").then(function (topic) {
        console.log('Subscribed:'+topic);
    }).catch(function(err){
        console.error(err);
    });

I'll look into this

I have exactly the same error.

@auser hey, any progress on this?

This call works without error
FirebaseStack.cloudMessaging.subscribeToTopic("film").then(function (topic) {
        // whatever
    }).catch(function(err){
        console.error(err);
    });

Those below one doesn't
FirebaseStack.cloudMessaging.listenForReceiveNotification((msg) =>{
    console.log(msg.data);
    console.log(msg.notification);
});

FirebaseStack.cloudMessaging.listenForTokenRefresh(function (token) {
        _this.updateDeviceToken(token)

        .then(function(response) {
            resolve(response)
        })
        .catch(function(fire){
            reject(fire)
        })

    });

In case that helps :-)

i am seeing the same error. for me the crash occurs on iOS for this method/callback: firestack.cloudMessaging.listenForReceiveNotification((msg) => ....
on Droid is ok
has there been any progress in resolving ?

@ajonno
I use for now https://github.com/evollu/react-native-fcm/issues/177 (only for the cloudMessages) and hope that they may merge, but it doesn't look like it so far, I guess.
Anyway, just in case you need a solution right now.
Otherwise waiting until this is implemented.


We need to document required functionality for v1

The first version should provide the following functionality:
Map with OSM underlay

Full screen map with top bar (as per wireframe above) (see #20 )
Sites should be rendered as geojson using leaflet point clustering (how will this scale to ~1000 of points?) (see #21)
Clicking on a site should reveal the item info and its contextual info

Point creation

Click 'add site to map'
On clicking 'add site to map', the user should be prompted to log in using oauth if they are not already logged in (see #22)
Return user to same position on the map with marker cross hairs activated
User locates the site by dragging the map and toggling the satelite image and map view (need a ticket)
Clicking the site on the map activates the red marker and the small pop-up window as per http://users.inasafe.org/
User completes form
Lat long auto-populated
Click the 'more..' link in the small form opens the slider window on the right with data loaded

Place the cursor in the next empty field
Move the map and the site position so that it is horizontal with the first field
After the site is accepted, it should turn into a blue marker as per image below and the new site modal should be removed

About
There should be a simple about box - @markherringer to provide markup


New release of ember-autoresize

When are you going to release 1.15.5 - the fix for ember-cli-fastboot is well needed?

Thanks for the poke! I just released it :)


Nested wilcards with $$ syntax is broken

Describe the bug
Nested wildcards seems broken when combined with {2$$__some-wildcard__} syntax.
To Reproduce
animal.txt contains a list of animals
color.txt contains a list of colors
custom.txt contains
__animal__
__color__

If you try
{2$$__custom__} then it erroneously ends up resolving to __animal__,__color__ for instance instead of fully recursively resolving to
"cat,red" as it used to behave.
When I try __custom__ by itself without $$ syntax, it does fully recursively resolve to "cat" for example as expected.
Also mention which checkboxes have been set: None
Are you using a local install or a colab?
local install
Expected behaviour
A clear and concise description of what you expected to happen.
{2$$__custom__} should fully resolve to "cat,pink" for instance instead of __animal__,__color__
Additional context
Add any other context about the problem here.
This worked while i was on the 10c9006c Jan 27 commit, and broke when I updated today to 59f44e935 commit.

I am also getting this, really annoying with how much I use this for colors

Could you please confirm your version of the dynamicprompts library? You can find it on the Need Help? Accordion.

"You are using version 2.10.0 of the WebUI extension, and the underlying dynamicprompts library is version 0.21.0. "

same

I've submitted a pull request (https://github.com/adieyal/dynamicprompts/pull/69), once it's approved then it will be publish.

sweet, thanks.

still getting that problem on my end


Fix harness getDirectores implementation to not include directory as prefix

Fixes https://github.com/Microsoft/TypeScript/pull/21100#issuecomment-362913096
We already had fourslash tests for getting directories in path completions. But, the harness implementation of getDirectories differed from the original one, as it returned directories with the prefix present.
Now directory completions with paths should for real in addition to in fourslash tests. (See the linked comment for repro instructions.)

I am completely replacing the implementation of getDirectories in https://github.com/Microsoft/TypeScript/pull/20763, so we'll need to coordinate this change.

I went with standardizing returning "foo" instead of "/directory/path/foo" because all getDirectories implementations but the one in harnessLanguageService seemed to be doing that already. So long as your PR also keeps that behavior in all getDirectories implementations I don't think there will be any conflict.


HADOOP-18576. hadoop common javadocs

Description of PR
changes imports to stop javadoc complaining
How was this patch tested?
For code changes:

[ ] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'HADOOP-17799. Your PR title ...')?
[ ] Object storage: have the integration tests been executed and the endpoint declared according to the connector-specific documentation?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE, LICENSE-binary, NOTICE-binary files?

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 42s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+0 :ok:
detsecrets
0m  1s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
38m 33s

trunk passed

+1 :green_heart:
compile
22m 54s

trunk passed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04

+1 :green_heart:
compile
20m 25s

trunk passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
checkstyle
1m 12s

trunk passed

+1 :green_heart:
mvnsite
1m 39s

trunk passed

-1 :x:
javadoc
1m 15s
/branch-javadoc-hadoop-common-project_hadoop-common-jdkUbuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04.txt
hadoop-common in trunk failed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04.

+1 :green_heart:
javadoc
0m 51s

trunk passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
spotbugs
2m 41s

trunk passed

+1 :green_heart:
shadedclient
22m 15s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 59s

the patch passed

+1 :green_heart:
compile
22m 22s

the patch passed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04

+1 :green_heart:
javac
22m 22s

the patch passed

+1 :green_heart:
compile
20m 21s

the patch passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
javac
20m 21s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
1m  7s
/results-checkstyle-hadoop-common-project_hadoop-common.txt
hadoop-common-project/hadoop-common: The patch generated 2 new + 21 unchanged - 0 fixed = 23 total (was 21)

+1 :green_heart:
mvnsite
1m 40s

the patch passed

-1 :x:
javadoc
1m  5s
/patch-javadoc-hadoop-common-project_hadoop-common-jdkUbuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04.txt
hadoop-common in the patch failed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04.

+1 :green_heart:
javadoc
0m 50s

the patch passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
spotbugs
2m 40s

the patch passed

+1 :green_heart:
shadedclient
22m 21s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
18m 19s

hadoop-common in the patch passed.

+1 :green_heart:
asflicense
1m  2s

The patch does not generate ASF License warnings.

205m 45s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5226/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/5226

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux 63b9842fb64d 4.15.0-200-generic #211-Ubuntu SMP Thu Nov 24 18:16:04 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 74892e24dfd86442e51a5cb37d24f33e6b540bf4

Default Java
Private Build-1.8.0_352-8u352-ga-1~20.04-b08

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_352-8u352-ga-1~20.04-b08

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5226/1/testReport/

Max. process+thread count
1259 (vs. ulimit of 5500)

modules
C: hadoop-common-project/hadoop-common U: hadoop-common-project/hadoop-common

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5226/1/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 52s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+0 :ok:
detsecrets
0m  1s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
39m 10s

trunk passed

+1 :green_heart:
compile
23m 10s

trunk passed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04

+1 :green_heart:
compile
20m 21s

trunk passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
checkstyle
1m 13s

trunk passed

+1 :green_heart:
mvnsite
1m 41s

trunk passed

-1 :x:
javadoc
1m 16s
/branch-javadoc-hadoop-common-project_hadoop-common-jdkUbuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04.txt
hadoop-common in trunk failed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04.

+1 :green_heart:
javadoc
0m 51s

trunk passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
spotbugs
2m 40s

trunk passed

+1 :green_heart:
shadedclient
22m 26s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
1m  0s

the patch passed

+1 :green_heart:
compile
22m 14s

the patch passed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04

+1 :green_heart:
javac
22m 14s

the patch passed

+1 :green_heart:
compile
20m 25s

the patch passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
javac
20m 25s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
1m  6s
/results-checkstyle-hadoop-common-project_hadoop-common.txt
hadoop-common-project/hadoop-common: The patch generated 2 new + 21 unchanged - 0 fixed = 23 total (was 21)

+1 :green_heart:
mvnsite
1m 41s

the patch passed

-1 :x:
javadoc
1m  4s
/patch-javadoc-hadoop-common-project_hadoop-common-jdkUbuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04.txt
hadoop-common in the patch failed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04.

+1 :green_heart:
javadoc
0m 48s

the patch passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
spotbugs
2m 41s

the patch passed

+1 :green_heart:
shadedclient
22m 14s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
18m 13s

hadoop-common in the patch passed.

+1 :green_heart:
asflicense
1m  1s

The patch does not generate ASF License warnings.

206m 48s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5226/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/5226

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux cafea693e91b 4.15.0-200-generic #211-Ubuntu SMP Thu Nov 24 18:16:04 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 00258139e79406e9234c5ba96cc7faa90b59b38a

Default Java
Private Build-1.8.0_352-8u352-ga-1~20.04-b08

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_352-8u352-ga-1~20.04-b08

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5226/2/testReport/

Max. process+thread count
1259 (vs. ulimit of 5500)

modules
C: hadoop-common-project/hadoop-common U: hadoop-common-project/hadoop-common

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5226/2/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

thanks i will try that in a a different pr; close this one.
note that we are doing java11 javadocs twice, not java8 any more. have we stopped java8 builds?
as i was going to raise that topic soon "can we stop java8 work?".

note that we are doing java11 javadocs twice, not java8 any more. have we stopped java8 builds?

java-11 javadoc is twice because once it is run on trunk without patch, the second run with your patch applied.
Same goes with Java-8, it is passing in the last result

This is the patch result on JDK-8
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5226/2/artifact/out/patch-javadoc-hadoop-common-project_hadoop-common-jdkPrivateBuild-1.8.0_352-8u352-ga-1~20.04-b08.txt
Can check all the results here:
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5226/2/artifact/out/
just search javadoc

we need to stop with the java8 releases


Too many subrequests.

Hi,
on a blockchain, I'm trying to get the information that the transaction has been approved.
const confirmation = await connection.confirmTransaction({
        signature,
        blockhash,
        lastValidBlockHeight,
    },
    "finalized"
);

The confirmTransaction function assigns multiple get requests in the background to verify whether the transaction has been confirmed or not.
in this case "error: Too many sub-requests. Thus, employees can submit up to 50 sub-requests per request."
the error returns. I don't get errors when I do the same with Expressjs.
What am I doing wrong?

Hi @tolgaand !
Which platform do you run on? I think it's not Hono matter but the platform matter.

Hi @yusukebe , thanks for your comment.
For two days I thought it wasn't about hono.
But then I realized that when I try with frontend(next) and backend(express), there is no problem.
The code of the confirmTransaction function is here

@tolgaand
I've investigated. If you are running on Cloudflare Workers, then you can only make up to 50 external fetch sub-requests in the free plan.
https://developers.cloudflare.com/workers/platform/limits/
Maybe this is the issue.

@yusukebe thanks for your comment.
The '@honojs/node-server' library worked.
One last question; where can I deploy my project using this library?

The @honojs/node-server library worked.

Good!

One last question; where can I deploy my project using this library?

You can deploy it anywhere Node.js works. Version 16.x or 18.x would be good. If you like "serverless", maybe it will work on AWS lambda or Google Cloud Functions. Or you can make it runs on VPS or containers...

Hi, thank you for creating Hono,
do you have any example of how to use "@honojs/node-server" with AWS lambda (serverless)?

Hi @KailasMahavarkar !

do you have any example of how to use "@honojs/node-server" with AWS lambda (serverless)?

Not yet. I have never heard about Hono running on AWS. Let me know if you get it to work :)


valid Corefile sytax is wrongly parsed

A Corefile with:
dnssex.nl:1053 {
       file dnssex.nl.signed
}

Is wrongly parsed

Hadn't recompiled, works OK.


Slash command not registering

Summary
Slash command not registering
Reproduction Steps
The "Slash command example" on the project readme is not working for me. I'm replicating the code exactly, and disnake is giving SyncWarning: Failed to overwrite commands in <Guild id=[id]> due to 403 Forbidden (error code: 50001): Missing Access and warnings.warn(. The bot was invited to the server with all permissions.
Minimal Reproducible Code
import disnake
from disnake.ext import commands

token = 'TOKEN'
guild = GUILD_ID

def main():
  bot = commands.InteractionBot(test_guilds=[guild])

  @bot.slash_command()
  async def ping(inter):
    await inter.response.send_message()

  bot.run(token)

if __name__ == `__main__`:
  main()

Expected Results
The ping command to show up on the server.
Actual Results
The warning message given above.
Intents
Default
System Information

Python v3.10.4-final
disnake v2.5.1-final

disnake pkg_resources: v2.5.1

aiohttp v3.7.4.post0
system info: Linux 5.17.5-arch1-1 #1 SMP PREEMPT Wed, 27 Apr 2022 20:56:11 +0000

Checklist

[X] I have searched the open issues for duplicates.
[X] I have shown the entire traceback, if possible.
[X] I have removed my token from display, if visible.

Additional Context
No response

Make sure you invite your bot with the applications.commands OAuth scope enabled.
To do so, visit https://discord.com/developers/applications, click on your bot, navigate to OAuth -> URL Generator, and make suer applications.commands is ticked. Then copy the link that appears, and use that to reinvite your bot. Without this OAuth scope, the bot is not authorized to use slash commands regardless of its permissions.

Given no activity for over a week, and a response above which is the solution, I will be closing this issue.


Disallow runs of special characters in project names

It should not be allowed to upload a project named something like foo--bar. It creates hard to read project names.

Here's a SQL query that will return a list of projects that currently use a run of special characters:
SELECT *
FROM (
    SELECT name,
           regexp_replace(name, '[_.]', '-', 'g') as dname,
           regexp_replace(name, '[-_.]+', '-', 'g') as rname
    FROM packages
) as s
WHERE dname != rname;

There are currently 13, we should reach out to them and see if they'd mind dropping any runs of special characters so we can enforce this easily in the database. There shouldn't be any issues with collisions or such since the normalization already eliminates runs of special characters.

We discussed this idea in the Warehouse meeting today -- I presume that the change would be just for readability?
I'm marking it blocked since implementing it would require PEPs to be modified. And since this is a new change that doesn't get us closer to replacing legacy PyPI I've added it to a far future milestone.

In practice this isn't happening much because builders, build backends and uploaders are all providing some degree of normalization throughout the process prior to PyPI getting the upload, but it's still technically possible.
Before implementing this we probably need to update the Core Metadata specification at https://packaging.python.org/en/latest/specifications/core-metadata/#name with the new rule.


Redesign ItemDetails

This is an issue for discussion. The current ItemDetails component has same drawbacks. In particular the layout  arose from current Cocoda layout and has some drawbacks (or unavoidable compromises):

browsing is not as nice as with ConceptTree because the height of tabs changes so the list of narrower concepts jumps up and down
Content of tabs is hard-coded
Only one tab is shown at a time

There will likely be more and/or other tabs in the future, e.g. to show coordinate at a map. Tabs can already be configured with slot tabs. We may also put hierarchy (ancestors & browader, narrower) into a tab instead of always showing it. We may make it configurable which tabs to always show on bottom, at top, or as tab. If there is vertical space, we could also show some content left (e.g. hierarchy) and some right (e.g. tabs)... We could also  split ItemDetails into sub-components (e.g. LicenseInfo can be a component of its own) so it can easier be rearranged.
I started by moving the item label to the top of the component, but this still can be discussed.

Vue 3's Teleport might be helpful for this.
In any case, the requirements should be clearly defined before we start redesigning ItemDetails. There were a lot of different ideas in your post which need to be organized and properly elaborated.

We decided to not create a complex component with many configuration but chose one opinionated layout. Still some questions:

Can we get rid of beforeName? It is used in Cocoda to show the "clear concept" button.  How about button all buttons to the right, so we only need one slot?
Rename slot tabs to additionalTabs (otherwise I'd expect it to override all tabs)
Move display of license into a component of its own (LicenseInfo?)
Move tabs into a component ItemDetailTabs so they can better be reused for side-by-side layout of hierarchy and concept details
Think again why the component is named ItemDetails instead of ConceptDetails (I think there was a reason?)

Can we get rid of beforeName? It is used in Cocoda to show the "clear concept" button.  How about button all buttons to the right, so we only need one slot?

I just noticed that in Cocoda, the "favorite star" is sometimes before and sometimes after the name. I actually like how it looks before the name, so I would vouch to keep the beforeName slot and (in Cocoda) put the favorite star there instead of after the name.

Rename slot tabs to additionalTabs (otherwise I'd expect it to override all tabs)

Fair enough.

Move display of license into a component of its own (LicenseInfo?)

Sure. I guess sometimes it's necessary to show the license separately, like after ItemName or something, so it makes sense. We could also allow to add more license badges via that component (in addition to the built-in ones).

Move tabs into a component ItemDetailTabs so they can better be reused for side-by-side layout of hierarchy and concept details

I'm fine with that.

Think again why the component is named ItemDetails instead of ConceptDetails (I think there was a reason?)

Because we want to use it not only for concepts, but also for concept schemes. It would make sense to add an example for that.

I made several changes and I'm going to close this issue now to release 0.2.0. For any further adjustments, please create separate issues.


Add basic rh.here test blocked by call working.

self explanatory

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

Current dependencies on/for this PR:

main

PR #390

PR #391   👈

This stack of pull requests is managed by Graphite.


Theme footer shows "powered by Worona"

child of https://github.com/wp-pwa/saturn-theme/issues/48

@Poliuk could you please give us a bigger (or SVG) image for Sirv?

@luisherranz @orballo Here you have a SVG version: https://drive.google.com/open?id=1sGUJDggwZxQ5mg8yo718s8Zfvmv1FwOR
Let me know if it works :)

@Poliuk perfect, thanks :)

@orballo sure! Can you define "big"? Haha give me exact dimensions!

@Poliuk Don't know, maybe 600px width? We should be able to crop it for different screen densities. The current logo is 100px width and I think the biggest we use is x3 or 300px. With 600px we should be good.

You don't need to use png, you can convert text to vectors before exporting the svg.

@orballo can you try with this one? It's an svg without font. https://drive.google.com/open?id=1WEyh8j4Mwx_osCN2bvSUZ_Nd12NdQ1Kz

:tada: This issue has been resolved in version 0.7.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 1.6.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Bump Alpine OS version to 3.19

Currently image is using Alpine OS v.3.18.
New 3.19 version was released, can you upgrade to use that?
This is required to allow some downstream ha-addons to support new hardware.

This is just about what Alpine version the builder is using.
If you build an add-on, you are using the Docker base image. 3.19 is available, see https://github.com/home-assistant/docker-base/.


Add support for Yale YRL256 lock

Description:
Yale locks require the device state and alarm type workarounds.  Yale recently released a new line of locks, and it seems my Yale YRL256 also requires this workaround.
Checklist:

[x] The code change is tested and works locally.
[x] Local tests pass with tox. Your PR cannot be merged unless tests pass
[x] There is no commented out code in this PR.
[x] I have followed the development checklist

Hi @ctso,
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!


Footer Section Design Improvement

Is your feature request related to a problem? Please describe.
No. It's an enhancement in the existing design of the footer.
Describe the solution you'd like
I would like to change the color, background, border, link styling and other design properties of the footer to make it look even better.
Describe alternatives you've considered
Changes in the existing footer's design code.
Additional context
N/A

#26 already exist for this, please propose your changes there


Fix a bug introduced by 9b803ee. See #193 and #194.

I somehow missed the pretty.sml file.

good catch!
This is one of those areas where I wish SML had a special lexical syntax for constructors (as in Haskell), so that they could not be confused with pattern variables.


Added note about where the transcription is stored to cloud-recording.md

Closes https://github.com/MicrosoftDocs/OfficeDocs-SkypeForBusiness/issues/5661.

@tonysmit PR has been copyedited and is ready for final review, could you please check and merge? Thanks!


SOLR-13748: Add support for mm parameter to bool query parser

https://issues.apache.org/jira/browse/SOLR-13748

Description
Added support for mm parameter to {!bool} query parser
Tests
Added test suite for BoolQParserPlugin
Checklist
Please review the following and check all that apply:

[x] I have reviewed the guidelines for How to Contribute and my code conforms to the standards described there to the best of my ability.
[x] I have created a Jira issue and added the issue ID to my pull request title.
[x] I have given Solr maintainers access to contribute to my PR branch. (optional but recommended)
[x] I have developed this patch against the main branch.
[x] I have run ./gradlew check.
[x] I have added tests for my changes.
[x] I have added documentation for the Reference Guide

Since the similar parameter for DisMax/eDisMax query parsers is also named mm, perhaps it makes sense to keep the naming consistent?

Thanks for the review @HoustonPutman, feel free to merge this whenever you have time.

Thanks @AndreyBozhko I'll check it next week


React Native 0.26

Why:

Latest React Native no longer users React and Component from
react-native package.

This change addresses the need by:

Pull React and Component from react package.
PropTypes had to be prefixed with React. (not sure why but that was the error I was given)

Thanks for the PR! I will have a look at it over the weekend.

Thanks again for contributing! I applied some small changes to your PR and merged them in to master.


Enable TLS for APIEdge instances

When TLS is enabled for an edge instance, we need to set the tlsEnabled bool variable to make sure that the HTTPS URISchema is applied.
Jira: OSPRH-6720

/hold beta freeze


Team formation

What
We'll need to fill the following core roles + shadows to get the ball rolling. The current list of role responsibilities is just a suggestion based on the last meeting.  Each team will decide on sub-team roles and responsibilities (ie - marketing lead will determine if a writer is needed) based on the direction of the event.
This is our first event, so all Lead roles are open for self-nomination and will be decided in the next public meeting. Shadows for the roles do not need to have event experience but should be ok with taking a Lead role within the next 12 months of events.
How
The Guide from the Kubernetes Community Days website:
https://kubernetescommunitydays.org/organizing/
The checklist:
Kubernetes Community Days Conference Action Items and Assignments

Roles
Event coordination

Project management
CNCF interactions
SIG-Contribex interactions
Sponsorship (if applies)

Content

Define event tracks and schedule
Talk introduction / moderation
Call for proposals ingestion / Speakers

Marketing

Website
Social media / Community management
Call for proposals form
Swag (if applies)

Multimedia

Bevy platform setup
Recordings edit / publication
Technical support

Team

Role
Lead
Shadow
Notes

Event coordination
@raelga  @agonzalezro

Content
@angelbarrera92
@agonzalezro

Marketing

@raelga

Multimedia

@angelbarrera92

Ciao @raelga,
If I may propose myself to a couple of roles, I can be "lead" at Content and "shadow" on Multimedia.
Thanks!

Hi! Shadow on Content & happy to shadow in any other if needed. I could lead event coordination but I don't fully know how deep is the work needed there (maybe we would need more than one lead on that one?).

@agonzalezro is just a proposal to discuss over the next meeting tomorrow and formalice the teams. Some roles, like the event coordination or content are quite more demanding than others, so have a lot of sense to split them smaller roles and have a lead/owner for each one.
I'm going to apply as lead for event coordination and shadow for the marketing team.

Hello! As discused with @raelga I don't have enough time to take a leading role as I'm part of the organization of HackUPC, an online hackathon that will take place on mid may, but I can shadow both Marketing and Multimedia :)

I can lead multimedia and shadow content and/or event coordination.

I will add myself as Marketing lead, as there are no more candidates at this point :p

Add me to Content Shadow


CA counties: Santa Barbara, Ventura, Merced

Ventura works great, getting 0 for Santa Barbara and Merced though

Santa Barbara is working until 2020-3-26, then it gets 0 for everything

Merced seems to get 0 for every day
yarn timeseries -l "Merced County, CA, USA" -d 2020-3-17


Inconsisten Behavior between ngx-datatable-column and [columns] definition

I'm submitting a ...  (check one with "x")
[ x] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request => Please do not submit support request here, post on Stackoverflow or Gitter

Current behavior

If using ngx-datatable-column as column definition, the table doesn't redraw when there is a change in Datatable.columns array. This doesn't happen when column definition is specified in .ts file using [columns]='columns' syntax. This bug was introduced in 10.0.4. It is good in 10.0.3
Expected behavior
Column definition using ngx-datatable-column should behave the same with [columns]='columns'.

Reproduction of the problem

https://plnkr.co/edit/WtLJ6HK39XF9MZIJFGO4?p=preview
Click Hide 1st Column button. The first column of the first table is hidden but not in the second. Resize the browser window (unmaximize it - maximize it again) to force redraw the second table, then the first column is hidden.
What is the motivation / use case for changing the behavior?

Please tell us about your environment:

Table version: 10.0.4 and 10.0.5

Angular version: 4.3.3

Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]

Language: [all | TypeScript X.X | ES6/7 | ES5]

I edited the plunkr to work with 10.2.0. The problem is still happening.

I managed to solve this problem. The columns change should always happens in a variable that assigned to DatatableComponent.columns.
In the plunkr above, check app.ts line 34 and 67


golang

had a look... your just calls the per OS installer and then doing a exec.
I wrote the same thing in golang calling the CF golang binary.
also runs in GitHub CI, but also any other place I need it.

Can you expand on what you'd like to see changed / updated? It's a bit unclear at the moment.

In general, GitHub actions are written in JavaScript or deployed in a docker container. In the case of this action, JavaScript was easier, as we are just running a few commands and do not need any extra tools built into a docker container. The actions/toolkit is pretty useful and abstracts a lot of stuff away too.


Generated export code is incorrect

The following export statement is not properly transformed:
export {A, B} from './foo'

It produces:
exports.A = _interopRequire(require("./foo"));
exports.B = _interopRequire(require("./foo"));

Instead of:
var _ref = require("./foo");
exports.A = _ref.A;
exports.B = _ref.B;

Tested using<EMAIL_ADDRESS>

It's correct. It's essential for module interopability. See #95, #224 and #225 for prior discussion. Unless you're referring to the duplicate requires in which case it's another issue and it's not really incorrect.

According to harmony specifications export {A} from './foo' should export A from ./foo.
The generated code fails to export A.
export {A, B} from './foo'`

Expect ExportBindings:

[[ExportName]]
[[ModuleRequest]]
[[ImportName]]

A
./foo
A

B
./foo
B

Am I wrong?

My apologies, I misread your original issue. This certainly shouldn't be expected behaviour, I'll investigate shortly.

It is a regression<EMAIL_ADDRESS>produces:
exports.A = require("./foo").A;
exports.B = require("./foo").B;

Really sorry about that. Fixed as of 2.6.3

:+1:


Webhook fails to parse setup intent events

Hello, it seems that whenever I receive a webhook involving setup intents, async stripe fails to parse them. The endpoints where I receive this parsing error is:

setup_intent.created
setup_intent.succeeded

This is the error that is thrown.
BadParse("Error(\"unknown variant `setup_intent`, expected one of `account`, `application_fee`, `fee_refund`, `balance`, `bank_account`, `card`, `charge`, `customer`, `dispute`, `checkout.session`, `file`, `invoice`, `invoiceitem`, `order`, `order_return`, `payment_method`, `payment_intent`, `payout`, `plan`, `product`, `refund`, `review`, `sku`, `subscription`, `transfer`\", line: 9, column: 30)")

Currently running straight off of the github (I believe this commit):
async-stripe = { git = "https://github.com/arlyon/async-stripe", default-features = true, features = ["runtime-tokio-hyper-rustls"] }

Hi! I think the issue is that the appropriate variant is not available in the EventObject enum.
https://github.com/arlyon/async-stripe/blob/master/src/resources/webhook_events.rs#L211-L240
If you'd like to get this working you can the repo, add a variant for setup_intent in the file, and test it. When you're happy submit a PR and I'll get it merged.
thanks for the report!


[Firebase] Improve gamification

Rather than solely providing a leaderboard position in the progress notification mechanism (and in the leaderboard intent) we could introduce achievements & badges to show off their movie knowledge & get them more interested in continuing to use vote goat..

If we solve https://github.com/gla-ial/Vote-Goat-Backend/issues/6 for this WIP JS then we could establish a 'proof of work' for external rewards - a fine line between gamification & monetization though..

If we solve #6 for this WIP JS then we could establish a 'proof of work' for external rewards - a fine line between gamification & monetization though..

Implementing such a proof of work could breach the Google Assistant terms of service, so it's not suitable for production use.


Feat(eos_cli_config_gen): Add graceful-restart support for router_bgp

Change Summary
Adde graceful-restart and graceful-restart-helper support at top BGP level

Missing device documentation template updates
Need to verify on the issue if it should be implemented at other levels

Related Issue(s)
Fixes #2265
Component(s) name
arista.avd.eos_cli_config_gen
Proposed changes
Adding the following keys to the router_bgp schema:
  graceful_restart:
    enabled: < true | false >
    restart_time: < 1-3600 >
    stalepath_time: < 1-3600 >
  graceful_restart_helper:
    enabled: < true | false >
    restart_time: < 1-100000000>
    long_lived: < true | false >

Based on the following output (only including top level options in the fist commit for this PR):
DC1-LEAF1A(config-router-bgp)#show cli commands | grep graceful
[no|default] graceful-restart
[no|default] graceful-restart ( restart-time | stalepath-time ) SECONDS
[no|default] graceful-restart-helper [ ( restart-time RESTART_TIME ) ] [ long-lived ]
[no|default] neighbor ( GROUP | IP_PEER | IP6_PEER | IP6_LL_PEER ) graceful-restart [ disabled ]
[no|default] neighbor ( GROUP | IP_PEER | IP6_PEER | IP6_LL_PEER ) graceful-restart-helper [ ( restart-time RESTART_TIME ) ] [ long-lived ] [ disabled ]

How to test
Adding molecule tests
NOTE: for now the test does not cover every single cases as only one host is being used.
Checklist
Repository Checklist

[x] My code has been rebased from devel before I start
[x] I have read the CONTRIBUTING document.
[x] My change requires a change to the documentation and documentation have been updated accordingly.
[x] I have updated molecule CI testing accordingly. (check the box if not applicable)

@ryanmerolle - first stab at implementing it - can you please have a look and answer a few questions:
1/ does your issue also need the same behavior at the neighbor / peer-group level?
2/ in what way would you see the settings being documented in the device documentation - is it sufficient to do as it was done before when leveraging bgp_defaults?

Please don't merge until we get feedback from @ryanmerolle!


Prefix headers are moved to common file

In #254 PR, decided to move prefix http to common file. They are moved to network.

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

Needs approval from an approver in each of these files:

OWNERS

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

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

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

fix the test/linter failures?
/ok-to-test

Yes normally I do that but I don't know why this time I jumped to build state. I thought there wont be a problem. I shouldn't have rushed. that is a lesson to me :).


Can't reproduce results on Franka Cube Stack

Hi, thank you for open sourcing PQL! I am trying to reproduce the results on one GPU (4090) and am finding that the algorithm eval return doesn't go past the 400 ish mark
I ran the following command to test PQL (not PQL-D)
python scripts/train_pql.py task=FrankaCubeStack algo.num_gpus=1 algo.p_learner_gpu=0 algo.v_learner_gpu=0

I am using ca7a4fb762f9581e39cc2aab644f18a83d6ab0ba as the IsaacGymEnvs git commit and am using the Isaac Gym 4 release, as well as the latest git commit of the pql repo. I don't think this should be a reward scale issue since I modified the code to print the success rate of successfully stacking the cube and it is mostly close to 0.
Any idea?

I ran a second seed which is now doing slightly better, although comparing sample efficiency with the original paper it seems to still be behind. At 120M steps it is around 600 reward but paper shows 700.

I also tried running PPO just now but it seems to fail completely using
python scripts/train_baselines.py algo=ppo_algo task=FrankaCubeStack isaac_param=True

Is there anything else I might need to add to test the baselines?


Feat: Sign in with google Button

What feature?
There should be an sign in with google button so that users can visit this website easily without manually signing up in the website.
Add screenshots

Record

[X] I agree to follow this project's Code of Conduct
[X] I want to work on this issue

Yeah idea is good. You can use the google OAuth2.0 given by Appwrite. Assigned to you


[Bug] Using wrong font messes up font alignment

MS UI Gothic did it, changing to FOT-大江戸勘亭流 Std E fixed this

This might be more of a font issue, but please do look in to it and see if it's wontfix or fix

Not a bug itself but mainly font dependant (the FOT-ooedo kanteiryuu font having a different upper padding than the MS UI Gothic one, will see if I can put a better default font but og tjap3 normaly already included an option to change the text margin


[Bug]: Middleware rewrites cause TypeError: Invalid URL when pointing to a directory in public

Summary
With a middleware like this:
export default async (request) => new MiddlewareRequest(request).rewrite('/foo');

If there's a folder /foo in public, edge functions throw an error like this:
Oct 13, 08:10:08 PM: error  [next_src_middleware] TypeError: Invalid URL: '/foo/'
    at getSerialization (ext:deno_url/00_url.js:89:11)
    at new URL (ext:deno_url/00_url.js:380:27)
    at parseURL (file:///root/.netlify/edge-functions/next_src_middleware/bundle.js:2706:12)
    at new NextURL (file:///root/.netlify/edge-functions/next_src_middleware/bundle.js:2720:18)
    at adapter (file:///root/.netlify/edge-functions/next_src_middleware/bundle.js:1599:29)
    at eventLoopTick (ext:core/01_core.js:183:11)
    at async handler (file:///root/.netlify/edge-functions/next_src_middleware/index.ts:50:20)
    at async FunctionChain.runFunction (file:///root/src/bootstrap/function_chain.ts:396:22)
    at async FunctionChain.run (file:///root/src/bootstrap/function_chain.ts:316:20)
    at async handleRequest (file:///root/src/bootstrap/handler.ts:80:22)

A link to a reproduction repository
https://github.com/cprussin/netlify-issue-repro
Expected Result
Render the file /public/foo/index.html if it exists, and 404 if it does not.
Actual Result
500 with the message Invalid URL: '/foo/' and the edge function log:
Oct 13, 08:10:08 PM: error  [next_src_middleware] TypeError: Invalid URL: '/foo/'
    at getSerialization (ext:deno_url/00_url.js:89:11)
    at new URL (ext:deno_url/00_url.js:380:27)
    at parseURL (file:///root/.netlify/edge-functions/next_src_middleware/bundle.js:2706:12)
    at new NextURL (file:///root/.netlify/edge-functions/next_src_middleware/bundle.js:2720:18)
    at adapter (file:///root/.netlify/edge-functions/next_src_middleware/bundle.js:1599:29)
    at eventLoopTick (ext:core/01_core.js:183:11)
    at async handler (file:///root/.netlify/edge-functions/next_src_middleware/index.ts:50:20)
    at async FunctionChain.runFunction (file:///root/src/bootstrap/function_chain.ts:396:22)
    at async FunctionChain.run (file:///root/src/bootstrap/function_chain.ts:316:20)
    at async handleRequest (file:///root/src/bootstrap/handler.ts:80:22)

Steps to reproduce

Deploy repo
Navigate to site

Next Runtime version
4.40.2
Is your issue related to the app directory?

[X] Yes, I am using the app directory

More information about your build

[ ] I am building using the CLI
[ ] I am building using file-based configuration (netlify.toml)

What OS are you using?
None
Your netlify.toml file
No response
Your public/_redirects file
No response
Your next.config.js file

`next.config.js`
module.exports = {
  reactStrictMode: true
};

Builds logs (or link to your logs)

Build logs
8:09:05 PM: build-image version: 2a79f2b6b97edab3f858983ec4cea00280a2836a (focal)
8:09:05 PM: buildbot version: c7db8131ac2d97256c1f537cc5bbdf08464b8daa
8:09:05 PM: Fetching cached dependencies
8:09:05 PM: Starting to download cache of 274.0MB
8:09:06 PM: Finished downloading cache in 743ms
8:09:06 PM: Starting to extract cache
8:09:08 PM: Finished extracting cache in 2.036s
8:09:08 PM: Finished fetching cache in 2.849s
8:09:08 PM: Starting to prepare the repo for build
8:09:08 PM: Preparing Git Reference refs/heads/main
8:09:10 PM: Starting to install dependencies
8:09:10 PM: Python version set to 3.8
8:09:10 PM: Attempting Ruby version 2.7.2, read from environment
8:09:11 PM: Using Ruby version 2.7.2
8:09:11 PM: Started restoring cached go cache
8:09:11 PM: Finished restoring cached go cache
8:09:11 PM: go version go1.19.13 linux/amd64
8:09:11 PM: Using PHP version 8.0
8:09:12 PM: Started restoring cached Node.js version
8:09:13 PM: Finished restoring cached Node.js version
8:09:14 PM: v18.18.2 is already installed.
8:09:14 PM: Now using node v18.18.2 (npm v9.8.1)
8:09:14 PM: Enabling Node.js Corepack
8:09:14 PM: Started restoring cached build plugins
8:09:14 PM: Finished restoring cached build plugins
8:09:14 PM: Started restoring cached corepack dependencies
8:09:14 PM: Finished restoring cached corepack dependencies
8:09:14 PM: No pnpm workspaces detected
8:09:14 PM: Started restoring cached node modules
8:09:14 PM: Finished restoring cached node modules
8:09:14 PM: Installing npm packages using pnpm version 8.7.6
8:09:15 PM: Lockfile is up to date, resolution step is skipped
8:09:15 PM: Already up to date
8:09:15 PM: Done in 421ms
8:09:15 PM: npm packages installed using pnpm
8:09:15 PM: Install dependencies script success
8:09:15 PM: Starting build script
8:09:16 PM: Detected 1 framework(s)
8:09:16 PM: "next" at version "13.5.4"
8:09:16 PM: Section completed: initializing
8:09:18 PM:
8:09:18 PM: Netlify Build
8:09:18 PM: ────────────────────────────────────────────────────────────────
8:09:18 PM:
8:09:18 PM: ❯ Version
8:09:18 PM:   @netlify/build 29.22.5
8:09:18 PM:
8:09:18 PM: ❯ Flags
8:09:18 PM:   baseRelDir: true
8:09:18 PM:   buildId: 652a065085dce700083fb0d8
8:09:18 PM:   deployId: 652a065085dce700083fb0da
8:09:18 PM:
8:09:18 PM: ❯ Current directory
8:09:18 PM:   /opt/build/repo
8:09:18 PM:
8:09:18 PM: ❯ Config file
8:09:18 PM:   No config file was defined: using default values.
8:09:18 PM:
8:09:18 PM: ❯ Context
8:09:18 PM:   production
8:09:18 PM:
8:09:18 PM: ❯ Using Next.js Runtime - v4.40.2
8:09:19 PM:
8:09:19 PM: @netlify/plugin-nextjs (onPreBuild event)
8:09:19 PM: ────────────────────────────────────────────────────────────────
8:09:19 PM:
8:09:19 PM: Next.js cache restored.
8:09:19 PM: Netlify configuration property "build.environment.NEXT_PRIVATE_TARGET" value changed.
8:09:19 PM:
8:09:19 PM: (@netlify/plugin-nextjs onPreBuild completed in 126ms)
8:09:19 PM:
8:09:19 PM: Build command from Netlify app
8:09:19 PM: ────────────────────────────────────────────────────────────────
8:09:19 PM:
8:09:19 PM: $ pnpm run build
8:09:19 PM: ><EMAIL_ADDRESS>build /opt/build/repo
8:09:19 PM: > next build
8:09:20 PM:    Creating an optimized production build ...
8:09:21 PM:  ✓ Compiled successfully
8:09:21 PM:    Linting and checking validity of types ...
8:09:21 PM:    Collecting page data ...
8:09:22 PM:    Generating static pages (0/4) ...
8:09:23 PM:    Generating static pages (1/4)
8:09:23 PM:    Generating static pages (2/4)
8:09:23 PM:    Generating static pages (3/4)
8:09:23 PM:  ✓ Generating static pages (4/4)
8:09:25 PM:    Finalizing page optimization ...
8:09:25 PM:    Collecting build traces ...
8:09:26 PM: Route (app)                              Size     First Load JS
8:09:26 PM: ┌ ○ /                                    140 B          80.5 kB
8:09:26 PM: └ ○ /_not-found                          883 B          81.2 kB
8:09:26 PM: + First Load JS shared by all            80.3 kB
8:09:26 PM:   ├ chunks/95-667055ea6e31680b.js        27.5 kB
8:09:26 PM:   ├ chunks/b97a3a71-357a375a396d8622.js  51 kB
8:09:26 PM:   ├ chunks/main-app-968e29e1596532ac.js  229 B
8:09:26 PM:   └ chunks/webpack-bf1a64d1eafd2816.js   1.66 kB
8:09:26 PM: ƒ Middleware                             27.9 kB
8:09:26 PM: ○  (Static)  automatically rendered as static HTML (uses no initial props)
8:09:26 PM:
8:09:26 PM: (build.command completed in 6.6s)
8:09:26 PM:
8:09:26 PM: @netlify/plugin-nextjs (onBuild event)
8:09:26 PM: ────────────────────────────────────────────────────────────────
8:09:26 PM:
8:09:26 PM: Moving static page files to serve from CDN...
8:09:26 PM: Moved 6 files
8:09:26 PM: You are not using Netlify Edge Functions for image format detection. Set env var "NEXT_FORCE_EDGE_IMAGES=true" to enable.
8:09:26 PM: ✨ Deploying middleware and functions to Netlify Edge Functions ✨
8:09:26 PM: Netlify configuration property "redirects" value changed to [
8:09:26 PM:   { from: "/_next/static/*", to: "/static/:splat", status: 200 },
8:09:26 PM:   {
8:09:26 PM:     from: "/_next/image*",
8:09:26 PM:     query: { url: ":url", w: ":width", q: ":quality" },
8:09:26 PM:     to: "/_ipx/w_:width,q_:quality/:url",
8:09:26 PM:     status: 301
8:09:26 PM:   },
8:09:26 PM:   { from: "/_ipx/*", to: "/.netlify/builders/_ipx", status: 200 },
8:09:26 PM:   {
8:09:26 PM:     from: "/api/*",
8:09:26 PM:     to: "/.netlify/functions/___netlify-handler",
8:09:26 PM:     status: 200
8:09:26 PM:   },
8:09:26 PM:   {
8:09:26 PM:     from: "/foo/index.html",
8:09:26 PM:     to: "/foo/index.html",
8:09:26 PM:     conditions: { Cookie: [Array] },
8:09:26 PM:     status: 200
8:09:26 PM:   },
8:09:26 PM:   {
8:09:26 PM:     from: "/*",
8:09:26 PM:     to: "/.netlify/functions/___netlify-handler",
8:09:26 PM:     status: 200,
8:09:26 PM:     conditions: { Cookie: [Array] },
8:09:26 PM:     force: true
8:09:26 PM:   },
8:09:26 PM:   {
8:09:26 PM:     from: "/_next/data/tep2MhD4Z2WLvbHajTyX-/_not-found.json",
8:09:26 PM:     to: "/.netlify/functions/___netlify-handler",
8:09:26 PM:     status: 200,
8:09:26 PM:     force: false
8:09:26 PM:   },
8:09:26 PM:   {
8:09:26 PM:     from: "/_not-found",
8:09:26 PM:     to: "/.netlify/functions/___netlify-handler",
8:09:26 PM:     status: 200,
8:09:26 PM:     force: false
8:09:26 PM:   },
8:09:26 PM:   {
8:09:26 PM:     from: "/*",
8:09:26 PM:     to: "/.netlify/functions/___netlify-handler",
8:09:26 PM:     status: 200
8:09:26 PM:   }
8:09:26 PM: ].
8:09:26 PM:
8:09:26 PM: (@netlify/plugin-nextjs onBuild completed in 121ms)
8:09:26 PM:
8:09:26 PM: Functions bundling
8:09:26 PM: ────────────────────────────────────────────────────────────────
8:09:26 PM:
8:09:26 PM: Packaging Functions from .netlify/functions-internal directory:
8:09:26 PM:  - ___netlify-handler/___netlify-handler.js
8:09:26 PM:  - ___netlify-odb-handler/___netlify-odb-handler.js
8:09:26 PM:  - _ipx/_ipx.js
8:09:26 PM:
8:09:57 PM:
8:09:57 PM: (Functions bundling completed in 31.1s)
8:09:57 PM:
8:09:57 PM: Edge Functions bundling
8:09:57 PM: ────────────────────────────────────────────────────────────────
8:09:57 PM:
8:09:57 PM: Packaging Edge Functions from .netlify/edge-functions directory:
8:09:57 PM:  - next_src_middleware
8:09:57 PM:  - rsc-data
8:09:58 PM:
8:09:58 PM: (Edge Functions bundling completed in 1.3s)
8:09:58 PM:
8:09:58 PM: @netlify/plugin-nextjs (onPostBuild event)
8:09:58 PM: ────────────────────────────────────────────────────────────────
8:09:58 PM:
8:09:58 PM: Next.js cache saved.
8:09:58 PM:
8:09:58 PM: (@netlify/plugin-nextjs onPostBuild completed in 92ms)
8:09:58 PM:
8:09:58 PM: Deploy site
8:09:58 PM: ────────────────────────────────────────────────────────────────
8:09:58 PM:
8:09:58 PM: Starting to deploy site from ".next"
8:09:58 PM: Calculating files to upload
8:09:59 PM: 8 new files to upload
8:09:59 PM: 2 new functions to upload
8:10:07 PM: Post processing - redirect rules
8:10:07 PM: Post processing done
8:10:07 PM: Section completed: postprocessing
8:10:07 PM: Starting post processing
8:10:07 PM: Skipping HTML post processing
8:10:07 PM: Post processing - header rules
8:10:07 PM: Site is live ✨
8:10:07 PM: Section completed: deploying
8:10:07 PM: Site deploy was successfully initiated
8:10:07 PM:
8:10:07 PM: (Deploy site completed in 8.2s)
8:10:07 PM:
8:10:07 PM: Netlify Build Complete
8:10:07 PM: ────────────────────────────────────────────────────────────────
8:10:07 PM:
8:10:07 PM: (Netlify Build completed in 49s)
8:10:07 PM: Caching artifacts
8:10:07 PM: Started saving node modules
8:10:07 PM: Finished saving node modules
8:10:07 PM: Started saving build plugins
8:10:07 PM: Finished saving build plugins
8:10:07 PM: Started saving corepack cache
8:10:07 PM: Finished saving corepack cache
8:10:07 PM: Started saving pip cache
8:10:07 PM: Finished saving pip cache
8:10:07 PM: Started saving emacs cask dependencies
8:10:07 PM: Finished saving emacs cask dependencies
8:10:07 PM: Started saving maven dependencies
8:10:07 PM: Finished saving maven dependencies
8:10:07 PM: Started saving boot dependencies
8:10:07 PM: Finished saving boot dependencies
8:10:07 PM: Started saving rust rustup cache
8:10:07 PM: Finished saving rust rustup cache
8:10:07 PM: Started saving go dependencies
8:10:07 PM: Finished saving go dependencies
8:10:07 PM: Build script success
8:10:07 PM: Section completed: building
8:10:08 PM: Uploading Cache of size 273.9MB
8:10:11 PM: Section completed: cleanup
8:10:11 PM: Finished processing build request in 1m5.883s

Function logs

Function logs
Oct 13, 08:10:08 PM: error  [next_src_middleware] TypeError: Invalid URL: '/foo/'
    at getSerialization (ext:deno_url/00_url.js:89:11)
    at new URL (ext:deno_url/00_url.js:380:27)
    at parseURL (file:///root/.netlify/edge-functions/next_src_middleware/bundle.js:2706:12)
    at new NextURL (file:///root/.netlify/edge-functions/next_src_middleware/bundle.js:2720:18)
    at adapter (file:///root/.netlify/edge-functions/next_src_middleware/bundle.js:1599:29)
    at eventLoopTick (ext:core/01_core.js:183:11)
    at async handler (file:///root/.netlify/edge-functions/next_src_middleware/index.ts:50:20)
    at async FunctionChain.runFunction (file:///root/src/bootstrap/function_chain.ts:396:22)
    at async FunctionChain.run (file:///root/src/bootstrap/function_chain.ts:316:20)
    at async handleRequest (file:///root/src/bootstrap/handler.ts:80:22)

.next JSON files
No response

Netlify-only internal link to conversation with customer on this topic

See comment here on the related issue #2332, the same comment applies to this ticket as well.

Hi @cprussin
The team at Netlify have now released the new v5 Next.js runtime which has support for both pages and app router, on-demand and time-based revalidation, automatic fine-grained cache control, and automatic image optimization using Netlify's image CDN.
You can find the documentation and additional information on the new runtime here: Next.js on Netlify
The v4 runtime is now in the maintenance support phase with no new features being added. Occasional bug fixes and security patches will be applied when needed.
Thanks!