Autorun not working on Windows 10 with Epic

Describe the bug/error
The /autorun and /edo tags do not appear to function, no product is found and the launcher fails. When they are left off, the minimal launcher will list the products and a selection of "1" will run ED:Odyssey. /autoquit appears to function properly
Debug log
I have added some slightly sanitized debug logs below.
Debug logging is placed in the standard log location for your operating system:

Windows - %LOCALAPPDATA%\min-ed-launcher\min-ed-launcher.log

----------
2024-10-10 09:57:27.297 -06:00 [INF] Elite Dangerous: Minimal Launcher - v0.11.1+d7e3e01c
2024-10-10 09:57:27.471 -06:00 [DBG]
    Args: [|"/Epic"; "-AUTH_LOGIN=unused";
  "-AUTH_PASSWORD=add...b80[32]"; "-AUTH_TYPE=exchangecode";
  "-epicapp=9c2...593[32]"; "-epicenv=Prod"; "-EpicPortal";
  "/autorun"; "/edo"; "-epicusername=xxx";
  "-epicuserid=520...9f2[32]"; "-epiclocale=en";
  "-epicsandboxid=3db...ac1[32]"|]
    OS: Win64
    Env:

2024-10-10 09:57:27.480 -06:00 [DBG] Reading settings from 'C:\Users\Bill\AppData\Local\min-ed-launcher\settings.json'
2024-10-10 09:57:27.715 -06:00 [DBG] Settings: { Platform = Epic { ExchangeCode = "add...b80[32]"
                    Type = "exchangecode"
                    AppId = "9c2...593[32]" }
  DisplayMode = Pancake
  AutoRun = true
  QuitMode = WaitForInput
  WatchForCrashes = false
  ProductWhitelist = seq ["edo"]
  ForceLocal = true
  CompatTool = None
  CbLauncherDir = "F:\EpicGames\EliteDangerous\"
  PreferredLanguage = None
  ApiUri = https://api.zaonce.net/
  Restart = None
  AutoUpdate = true
  CheckForLauncherUpdates = true
  MaxConcurrentDownloads = 4
  ForceUpdate = set []
  Processes = []
  ShutdownProcesses = []
  FilterOverrides = seq []
  AdditionalProducts = []
  DryRun = false
  ShutdownTimeout = 00:00:10
  CacheDir = "C:\Users\Bill\AppData\Local\min-ed-launcher\cache"
  GameStartDelay = 00:00:00
  ShutdownDelay = 00:00:00 }
2024-10-10 09:57:27.730 -06:00 [INF] Elite Runtime
    Platform: Epic
    CobraBay Version: 1.7.6972.1
    Products Dir: F:\EpicGames\EliteDangerous\Products
2024-10-10 09:57:27.746 -06:00 [DBG] Getting machine id
2024-10-10 09:57:27.762 -06:00 [INF] Logging in
2024-10-10 09:57:27.764 -06:00 [DBG] Getting remote time
2024-10-10 09:57:28.554 -06:00 [DBG] Requesting epic token
  Method: POST
  Uri: https://api.epicgames.dev/epic/oauth/v1/token
  Content: [
    grant_type=exchange_code
    exchange_code=add...b80[32]
    deployment_id=73d...6f3[32]
    scope=basic_profile friends_list presence
  ]
  Headers: {
    Authorization: Basic eHl...2NA[102]==
    Content-Type: application/x-www-form-urlencoded; charset=utf-8
  }

2024-10-10 09:57:28.846 -06:00 [DBG] Requesting epic token success
2024-10-10 09:57:28.860 -06:00 [DBG] Authenticating via Epic
2024-10-10 09:57:29.367 -06:00 [DBG] Successfully authenticated
2024-10-10 09:57:29.367 -06:00 [INF] Logged in via Epic as: xxx
2024-10-10 09:57:29.368 -06:00 [DBG] Getting authorized products
2024-10-10 09:57:29.606 -06:00 [DBG] Purchases Response:
{"purchases":[{"colour":"#f07b05","filter":"ed","directory":"elite-dangerous-64","serverargs":"","gameargs":"SeasonOne","sortkey":"06","product_name":"Legacy Elite Dangerous","imageset":{"box":"http://hosting.zaonce.net/launcher_new/images/box_ed.jpg","hero":"http://hosting.zaonce.net/launcher_new/images/Elite_Dangerous_LauncherHero.png","logo":"http://hosting.zaonce.net/launcher_new/logos/ED_Refresh_Logo_Full_White.png"},"ratings":{"esrb":"teen","pegi":"7"},"game_api":"https://api3x.orerve.net","game_branch":38,"patch_notes_game_code":13,"no_details":false,"product_sku":"FORC-FDEV-D-1010","template":"http://hosting.zaonce.net/launcher/elite/en.html"},{"colour":"#f07b05","filter":"eda","directory":"elite-dangerous-64","serverargs":"","gameargs":"CQCArena","sortkey":"20","product_name":"Elite Dangerous: Arena","imageset":{"box":"http://hosting.zaonce.net/launcher_new/images/box_arena.jpg","hero":"http://hosting.zaonce.net/launcher_new/images/Elite_Dangerous_Arena_LauncherHero.png","logo":"http://hosting.zaonce.net/launcher_new/logos/ED_Refresh_Logo_Full_White.png"},"ratings":{"esrb":"teen","pegi":"7"},"game_api":"https://api3x.orerve.net","game_branch":38,"patch_notes_game_code":13,"no_details":true,"product_sku":"FORC-FDEV-D-1012","template":"http://hosting.zaonce.net/launcher/elite-dangerous-arena/en.html"},{"colour":"#f07b05","filter":"ed","directory":"COMBAT_TUTORIAL_DEMO","serverargs":"","gameargs":"","sortkey":"30","product_name":"Single Player Combat Training","imageset":{"box":"http://hosting.zaonce.net/launcher_new/images/box_ed.jpg","hero":"http://hosting.zaonce.net/launcher_new/images/Elite_Dangerous_LauncherHero.png","logo":"http://hosting.zaonce.net/launcher_new/logos/ED_Refresh_Logo_Full_White.png"},"ratings":{"esrb":"teen","pegi":"7"},"game_api":"https://api3x.orerve.net","game_branch":38,"patch_notes_game_code":13,"no_details":true,"product_sku":"COMBAT_TUTORIAL_DEMO","template":"http://hosting.zaonce.net/launcher/elite/en.html"},{"colour":"#0a8bd6","filter":"edh","directory":"elite-dangerous-64","serverargs":"","gameargs":"","sortkey":"05","product_name":"Legacy Horizons","imageset":{"box":"http://hosting.zaonce.net/launcher_new/images/box_edh.png","hero":"http://hosting.zaonce.net/launcher_new/images/Elite_Dangerous_Horizons_LauncherHero.png","logo":"http://hosting.zaonce.net/launcher_new/logos/ED_Refresh_Logo_Full_White.png"},"ratings":{"esrb":"teen","pegi":"7"},"game_api":"https://api3x.orerve.net","game_branch":38,"patch_notes_game_code":13,"no_details":false,"product_sku":"FORC-FDEV-D-1013","template":"http://hosting.zaonce.net/launcher/elite-dangerous-horizons-38/en.html"},{"colour":"#f07b05","filter":"ed","directory":"elite-dangerous-odyssey-64","serverargs":"","gameargs":"SeasonTwo","sortkey":"04","product_name":"Elite Dangerous: Horizons","imageset":{"box":"http://hosting.zaonce.net/launcher_new/images/box_edh.png","hero":"http://hosting.zaonce.net/launcher_new/images/Elite_Dangerous_Horizons_LauncherHero.png","logo":"http://hosting.zaonce.net/launcher_new/logos/ED_Rebrand_Logo_Full_White.png"},"ratings":{"esrb":"teen","pegi":"7"},"game_api":"https://api.orerve.net","game_branch":40,"patch_notes_game_code":943,"no_details":false,"product_sku":"FORC-FDEV-DO-38-IN-40","template":"http://hosting.zaonce.net/launcher/elite-dangerous-horizons/en.html"},{"colour":"#0a8bd6","filter":"edh","directory":"elite-dangerous-odyssey-64","serverargs":"","gameargs":"","sortkey":"00","product_name":"Elite Dangerous: Odyssey","imageset":{"box":"http://hosting.zaonce.net/launcher_new/images/box_art_edo_rebrand.png","hero":"http://hosting.zaonce.net/launcher_new/images/Elite_Dangerous_Odyssey_LauncherHero.png","logo":"http://hosting.zaonce.net/launcher_new/logos/ED_Rebrand_Logo_Full_White.png"},"ratings":{"esrb":"teen","pegi":"16"},"game_api":"https://api.orerve.net","game_branch":40,"patch_notes_game_code":943,"no_details":false,"product_sku":"FORC-FDEV-DO-1000","template":"http://hosting.zaonce.net/launcher/odyssey/en.html"}]}
2024-10-10 09:57:29.620 -06:00 [DBG] Authorized Products: Elite Dangerous: Odyssey,Elite Dangerous: Horizons,Legacy Horizons,Legacy Elite Dangerous,Elite Dangerous: Arena,Single Player Combat Training
2024-10-10 09:57:29.620 -06:00 [INF] Checking for updates
2024-10-10 09:57:30.079 -06:00 [DBG] Launcher is latest release 0.11.1
2024-10-10 09:57:30.085 -06:00 [DBG] Unable to find product's version info at 'F:\EpicGames\EliteDangerous\Products\COMBAT_TUTORIAL_DEMO\VersionInfo.txt'
2024-10-10 09:57:31.191 -06:00 [INF] Available Products:
	Elite Dangerous: Odyssey      FORC-FDEV-DO-1000     Up to Date
	Elite Dangerous: Horizons     FORC-FDEV-DO-38-IN-40 Up to Date
	Legacy Horizons               FORC-FDEV-D-1013      Up to Date
	Legacy Elite Dangerous        FORC-FDEV-D-1010      Up to Date
	Elite Dangerous: Arena        FORC-FDEV-D-1012      Up to Date
	Single Player Combat Training COMBAT_TUTORIAL_DEMO  Not Installed
2024-10-10 09:57:31.223 -06:00 [ERR] No selected project

Leaving off the /autorun provides the option to select which product to run which does run the product successfully. I would just like to know which launch options will run ED:Odyssey successfully.

Looks like your filter overrides are empty which leads me to believe your settings file is missing some entries. You'll want to ensure your filterOverrides looks like the following:
"filterOverrides": [
  { "sku": "FORC-FDEV-DO-1000", "filter": "edo" },
  { "sku": "FORC-FDEV-DO-38-IN-40", "filter": "edh4" }
],

Did you perhaps run min-ed-launcher before v0.5.1 was released? Before that, the settings file didn't include that entry when it was auto-generated on first-run.

Looks like your filter overrides are empty which leads me to believe your settings file is missing some entries. You'll want to ensure your filterOverrides looks like the following:
"filterOverrides": [
  { "sku": "FORC-FDEV-DO-1000", "filter": "edo" },
  { "sku": "FORC-FDEV-DO-38-IN-40", "filter": "edh4" }
],

Did you perhaps run min-ed-launcher before v0.5.1 was released? Before that, the settings file didn't include that entry when it was auto-generated on first-run.

You are exactly right, I had previously used min-ed-launcher a few years ago and just updated the new files but the settings file had previously been generated. I just added the lines you provided and it works great! Thank you for the quick response!!


Use logging library instead of print statement

In order to be able to work more flexibly with the output, it would be nicer to use the logging framework.

:-)

Neues Release! https://pypi.python.org/pypi/django-http-fallback-storage


TestCheckCache and TestIngressCheckCache are flaky

These tests failed in the latest daily tests.
https://k8s-gubernator.appspot.com/build/istio-prow/pull/istio-releases_daily-release/506/daily-e2e-rbac-auth/445
They passed yesterday (https://k8s-testgrid.appspot.com/istio#daily-e2e-rbac-auth) and currently in postsubmit (https://k8s-testgrid.appspot.com/istio#e2e-suite-rbac-auth).

FTR, They are flaky in CircleCI as well

Test failure reason is weird: mixer_test.go:272: Unable to retrieve valid cached hit number: check call metric is invalid: remote check call 41 is more than total check call 40 It is easy to de-flake the test, but not sure why these erroneous metric numbers are generated.


Visual Studio Compile on Save not immediately wiring up after rename

The Compile on Save functionality in Visual Studio 2013 when initially converting a file to TypeScript from JavaScript is buggy.  This may result in a negative first impression of TypeScript.
Repro:

Brand new Windows 8.1 fully patched with VS 2013 Community Edition (Update 4). No extensions or other software installed.
Start a new C# ASP.NET Web Application
Select the "Empty" template, uncheck "Host in the cloud".
Right-click Add JavaScript file.  Call it test.js.
Enter some simple code such as:

var x = 1;
x = x + 10;
console.log(x);

Save it.
Right-click rename file to test.ts.  Answer yes to "change extension" warning, No to "Seach NuGet?" question.
Save the file.  Expected: Since there are no errors and "compile on save" is enabled, Visual Studio should compile the TypeScript file and generate a source map.  Actual: The file is not compiled and no source maps are generated.
Make a trivial change to the file (add space or change numbers that are being added).  Try saving again.  Result: Still no compile.
Close the TypeScript file and open it again.
Click save without making any changes.  Result: Still no compile.
Make a trivial change and save it.  Result: Still no compile.
Right-click "Unload project", then Right-click "Reload project".
Make another trivial change and save it.  Result: TypeScript file compiles as expected.
Right-click Add JavaScript file.  Call it test2.js.
Put in some simple code such as:

var y = 9;

Right-click rename file to test2.ts.
Save test2.ts.  Result: test2.js and test2.map.js are not emitted.
Make a trivial change to test.ts (the original file) and save it.  Result: test.js and test.js.map are emitted as expected, so only test2 is broken.

This also occurs if TypeScript 1.4 has been installed from the Visual Studio Gallery.

I suspect renaming a .js to .ts does not trigger the same auto configuration of the project for TypeScript  as Add New Item -> TypeScript file.

Yes, I wouldn't be surprised if this and #1759 had a similar root cause.  Thanks for looking into this, Dan.

@nycdotnet this should be fixed in VS 2015. We have rewrote most of the compile-on-save implementation for this release to handle this class of issues. Porting the fix back to VS2013 would not be farly expensive. Closing this as won't fix; please reopen if you see issues on VS2015.

Did you mean would be fairly expensive or would not be?  As of now, do you intend to backport into VS 2013 update 5?  If I update my TypeScript course, I can include that info.
Thanks all - I look forward to trying it in VS 2015 when it RTMs in a few weeks.  :-)
-Steve O

Back porting the fixes to VS2013 would be expensive; we had to do some architectural changes to make sure this class of issues are addressed. So no change coming in Update5 for this issue in VS2013.

Thanks so much.  I can't wait for 1.5 official, not to mention VS 2015 RTM.


Status.TaskSpec should reset after params substitution

Feature request

The Taskrun.Status.taskSpec will be set as Taskrun.Spec when reconcile, seems for auditing.
I think it should be reset after the Params substitution, for auditing, with the real parameters will be more helpful.
current behavior
status:
  taskSpec:
    params:
    - name: arg
      type: string
    steps:
    - image: alpine
      name: do-something
      resources: {}
      script: |
        echo "$(params.arg)" | grep "prefix:suffix"

Expect behavior:
status:
  taskSpec:
    params:
    - name: arg
      type: string
    steps:
    - image: alpine
      name: do-something
      resources: {}
      script: |
        echo "prefix:suffix" | grep "prefix:suffix"

Use case
Beside auditing, there is another use case, maybe not common:
I try to get a unique hash code based on character of a taskrun,  that's could help cache the output of the taskrun and reuse(ignore) when a exactly same taskrun is invoked.
Spec is not enough, Params should be consider too. So if we set Status.TaskSpec after parameters substitution,  i can calculate hash code base on it.
Maybe it's not a common case, but at least it will help on auditing.

@vdemeester @ImJasonH @bobcatfish
any comments?

I think when I'm interested in auditing I actually expect to see what the original task spec was, verbatim. That means not having any modifications made from the original spec, like having placeholder strings replaced. I'm curious what others expect the behavior to be here.

I think when I'm interested in auditing I actually expect to see what the original task spec was, verbatim. That means not having any modifications made from the original spec, like having placeholder strings replaced. I'm curious what others expect the behavior to be here.

I would expect the same as @ImJasonH there.

Fine, so if I want to calculate a unique hash code for a taskrun, what character do you suggest?
BTW, a  original task spec without params replaced, user can get these information direct from spec.
@vdemeester @ImJasonH

I'd say it depends a lot on what you're trying to accomplish. Could you just use the .metadata.uid? Or are you comparing for equality, minus param(/result) values, to deduplicate?

@ImJasonH
I think .metadata.uid not works. my purpose is to make a certain "taskrun" could be reuse, so I need calculate a unique Hash Code based on something.  So when another taskrun which has exactly some character and it will have same Hash Code, then i know the taskrun could be replace with previously one.


[FEATURE] make optimization API simpler

Describe the bug
To be used like this example from a pr from llvm: https://github.com/llvm/llvm-project/pull/114612

Should be mostly done


feat: add variables key_usage and customer_master_key_spec

what

Added optional variables key_usage and customer_master_key_spec
Updated GitHub configs

why

To be able to use the created KMS key with DNSSEC in Route53. The defaults remain unchanged.

references

https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/kms_key#key_usage
https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/kms_key#customer_master_key_spec

/test all

/test all


Field search with star: true not working as expected

The following call does not work as expected:
Person.search("@name john @town new", star: true)

results in:
@name *john* @*town* *new*

I would expect
@name *john* @town *new*

Thanks for pointing this out - just fixed it in 1d997f5fc1678ae4603d83990fa1aed8d6ae8af9.

Thank you very much for the quick fix and for maintaining this great library!


Getting error Exception: Call to Node module failed with error: reflect-metadata shim is required when using class decorators

Just cloned to desktop and loaded the solution into VS 2015. My OS is Win10.
Packages restored properly. Solution builds nicely.
But after I try to launch the application, the browser shows this error: "Exception: Call to Node module failed with error: reflect-metadata shim is required when using class decorators".
Any idea?

So it sounds like you have an older version of Node & NPM installed (npm 2 or lower).
Can you install the latest Node 7.* (https://nodejs.org/en/) ?
That should make it go away :1st_place_medal:
Let me know!

Thanks Mark, You are correct.


Tabular: Added support for advanced stacker model interactions

Issue #, if available:
Description of changes:
Major Changes:

Expanded stacker functionality to work outside of level-alignment

This means that a stacker model at L3 can now take models at L0, L1, and L2 as input.
Previously they could only take models at L2 as input.

Upcoming PR will build upon this functionality to enable _FULL ensembles, resulting in 10-200x inference speedup with minimal accuracy loss for bag enabled ensembles.
Enables functionality to swap model pred_proba inputs on an already fitted stacker model. (Tradeoff between bagged stacker and _FULL stacker on-the-fly for accuracy/inference speed.)

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Job PR-403-1 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-403/1/index.html

Seems like the plan going forward is to keep the model names as: "_STACKER_lX" where X is the stacker "level" (determined by which round of stacking this model was trained in)?
If arbitrary DAGs are supported (and eventually actually used), then the documentation will  probably need to clarify what "level" means precisely to avoid user confusion.
If renaming eventually comes under consideration, I still think we might reconsider dropping the "STACKER*" suffix from the base models to more clearly distinguish them, as well as more clearly distinguishing between bagged vs not-bagged models (could be a separate suffix).

Ran this change on automlbenchmark, we match or outperform previous version, with no errors, so I have confirmed stability. We don't experience visible slowdown in inference time on automlbenchmark.
I don't intend to utilize the complex DAG functionality immediately, its implementation was a pre-requisite for _FULL ensembles due to intricacies in the code structure rather than _FULL ensembles actually utilizing complex DAG functionality. The most likely place it will be used is for weighted ensembles that can weight models at different stack levels.
Once this is the case, I will add to the documentation as you say. I also agree that we should make a tutorial notebook on these features. I think this can wait until after _FULL functionality and user-facing .info() are added. I also wanted to add a draw option to visualize the graph, but networkx makes weird drawings that are near impossible to make sense of. If we can figure out how to draw the graph nicely, I think that would be extremely helpful in the notebook to visualize the stackers and how they work.


Create bind for SignalR Java Client 5.0.6

In order to mitigate issues like:
https://github.com/xamarin/XamarinComponents/issues/1176
please add Xamarin prefix to:

nuget packageid
assemblyname
namespaces (including Metadata)

@moljac  I think it's done with https://github.com/xamarin/XamarinComponents/pull/1196/commits/cd99608dc25e4be042c79f0aebf29e11b34bbf95


Clean up and modernize Gradle scripts

Task to build is now just build instead of createReleaseJar
Each platform produces a runnable jar, and the parent merges them into a "universal" jar
Final jars end up in the root project build/distributions directory

Good idea, note that creating a runnable jar per platform requires including common though, so merging the runnable jars into a final jar might not be the most practical way.

This is really great. Thanks so much. Tested Wildlands on Paper 1.17.1 with the Build task and the universal and platform-specific jars; all loads fine.


waypoint 13 of jQuery

Challenge http://freecodecamp.com/challenges/waypoint-target-the-parent-of-an-element-using-jquery has an issue. Please describe how to reproduce it, and include links to screenshots if possible.
left-well element is red but still says not correct

@x34passenger thanks for posting this issue!
Please, provide your code and screenshot, thanks you.

Please review the Guidelines for Contributing, thank you!.

@x34passenger do you have ?
$("#target1").parent().css("background-color", "red")

or
("#left-well").parent().css("background-color", "red")

because from your description I believe you have the second which target the div element arond the left well and not the left well itself like the instructions say


Add tan, arcsin, arccos, arctan to ChainerX

With reference to #6423
Changelog:

Added tan, arcsin, arccos, arctan to ChainerX routines.
Added Python tests.
Updated docs

Jenkins, test this please.

Jenkins, test this please.

Jenkins CI test (for commit 1f68407e9445a8442ed5c4f76f55fdf66c6d9e42, target branch master) failed with status FAILURE.
(For contributors, please wait until the reviewer confirms the details of the error.)

The test failures seem unrelated to this PR. LGTM! Thank you very much!

Jenkins CI test (for commit 1f68407e9445a8442ed5c4f76f55fdf66c6d9e42, target branch master) failed with status FAILURE.
(For contributors, please wait until the reviewer confirms the details of the error.)


Added conversion script for pickle -> json detections

The new script is located in data_management/databases/classification/convert_pickle_to_detection_json.py

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: Marcel-Simon sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.


⚠ Bofrost.at has degraded performance

In bc08e4c, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 2380 ms

Resolved: Bofrost.at performance has improved in bf4a814 after 6 minutes.


Create special comment that adds tag/project/context to all tasks after it

1⃣ & 2⃣ tasks will have the #html tag
## #html
1⃣ first task
2⃣ second task
# Any comment stops it
3⃣ third task

Currently only works with tags (no project, context support yet).

No more work planned on this feature for now.


Support env vars like FLANNEL_ETCD_ENDPOINTS

Im missing the ability to set -etcd-endpoints -etcd-cafile -etcd-certfile and -etcd-keyfile via Environment variables (systemd drop in) like fleet and etcd

@psi-4ward you should be able to set FLANNELD_ETCD_ENDPOINTS, FLANNELD_ETCD_CAFILE and FLANNELD_ETCD_KEYFILE env vars. If you're using CoreOS and cloud-config, you should be able to set them in coreos.flannel section: https://coreos.com/docs/cluster-management/setup/cloudinit-cloud-config/#configuration-parameters
Let me know if it doesn't work for you.

Nice! But theres one more question.
The ca, cert and key files resists in a directory on the host. As far as i can see flannel gets started using the quay.io/coreos/flannel container. Cant imagine how the container can access the files? Currently i inject the folder as volume but i dont see a way how the coreos builtin flannel service can do that using the systemd drop in.

@psi-4ward you're right! This is a big oversight on our end. We will address that but for now you can work around it by copying those files (e.g. in ExecStartPre via dropin) into /run/flannel since that gets pulled into container.

Fixed in https://github.com/coreos/coreos-overlay/pull/1126


Added version checks in server and agents

Signed-off-by: Soumya Ghosh Dastidar<EMAIL_ADDRESS>
Proposed changes
This PR adds the version data in the db and version checks in the server and agent. This PR will form the basis for the upgrade mechanism in the following versions.
Changes:

New collection to store the version details for the control plane components
VERSION env variable in server and agent
If server version doesn't match the db version server will not startup
All requests from the agents are now also checked for version compatibility, if agent is in different version request is denied by the server.

Types of changes
What types of changes does your code introduce to Litmus? Put an x in the boxes that apply

[x] New feature (non-breaking change which adds functionality)
[ ] Bugfix (non-breaking change which fixes an issue)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation Update (if none of the other choices applies)

Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[x] I have read the CONTRIBUTING doc
[x] I have signed the commit for DCO to be passed.
[x] Lint and unit tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works (if appropriate)
[ ] I have added necessary documentation (if appropriate)

@rajdas98 @Jonsy13 does the manifest in docs directory also require this change ? cc: @gdsoumya

Yes @gdsoumya Can you pls add this env change in manifests in docs directory too.

Yes @gdsoumya Can you pls add this env change in manifests in docs directory too.

Updated


ValidationError body field required

An error occurred when upgrading from version <IP_ADDRESS> to <IP_ADDRESS>.
ValidationError(model='my_handler', errors=[{'loc': ('body',), 'msg': 'field required', 'type': 'value_error.missing'}])
The error appears only with additional arguments in the handler function:
class Message(BaseModel):
    data: str

async def my_handler(body: Message, logger: Logger, settings: Settings = Context()):
    ...

And it does not occur if additional arguments are removed:
class Message(BaseModel):
    data: str

async def my_handler(body: Message):
    ...

The data type of the body does not affect the error, only the additional arguments of the function affect.
When rolling back to <IP_ADDRESS>, the error stops reproducing.
I couldn't figure out what the problem was, since I'm not very immersed in the source code of the project. Thank you in advance for the answer.

@shlyamster thanks for using Propan and for your feedback! This bug was in fast-depends==2.0.2 version. So, you can use propan==<IP_ADDRESS> or the last <IP_ADDRESS> with updated fast-depends


NathanTech.LunaForReddit version 1.3.11

[ ] Have you signed the Contributor License Agreement?
[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] This PR only modifies one (1) manifest
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.4 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: codeflow:open?pullrequest=https://github.com/microsoft/winget-pkgs/pull/109917&drop=dogfoodAlpha

Automatic Validation ended with:

Despite the installer switches, this package still asks to confirm:


Runner::send_message should support polymorphic form

Is your feature request related to a problem? Please describe.
LocalRunner is invaluable for test development and debugging BUT extra message sending code is needed - e.g. from the custom_messages.py⇗ example, viz:
'As Is' (does not work for LocalRunner):
38    for i, worker in enumerate(environment.runner.clients):
            ...snip...
47        environment.runner.send_message("test_users", data, worker)

'Go To' (now supports LocalRunner BUT has become inelegant):
      clients = environment.runner.clients if isinstance(environment.runner, MasterRunner) else [environment.runner]
      for i, worker in enumerate(clients):
          ...snip...
          environment.runner.send_message("test_users", data, worker) if isinstance(environment.runner, MasterRunner) \
              else environment.runner.send_message("test_users", data)

Describe the solution you'd like

Change signature of LocalRunner::send_message(...) - to support polymorphic call on LocalRunner or MasterRunner:
    As Is: LocalRunner::send_message(self, msg_type, data=None)
    Go To: LocalRunner::send_message(self, msg_type, data=None, client_id=None)

This helps when simulating master-to-worker messages as LocalRunner::send_message(self, msg_type, data=None) currently only takes three arguments - not the usual four of MasterRunner::send_message(self, msg_type, data=None, client_id=None) and the above non-breaking change simplifies test code significantly.

NB: No change is proposed to WorkerRunner::send_message(self, msg_type, data=None) as polymorphic calling is already possible between LocalRunner (as Worker) and WorkerRunner and not broken by additional of fourth optional arg.

Define LocalRunner::clients as containing a single element of its own instance of LocalRunner thus facilitating polymorphically enumerating clients on LocalRunner or MasterRunner - a non-breaking change that simplifies test code significantly and simplifies examples.

(optional: unsure if this is needed) Define LocalRunner::client_id as its own 'client_id' (could just be str(self)?) that is normally allocated to a remote WorkerRunner and thus allow the new LocalRunner::send_message(self, msg_type, data=None, client_id=None) above to validate that the client_id is that of the LocalRunner.

Describe alternatives you've considered
Adding a lot more code that bloats tests to support debug as LocalRunner - an invaluable capability for demo, spikes, and for mentoring new developers - that could be simpler and hopefully clearer with the above proposed changes.  I wanted to check that there was appetite for this before submitting a PR proposal.
Additional context
Thanks again to all the contributors for such an elegant and useful tool in locust and its various addons and plugins - and specifically for supporting message passing in LocalRunner thus enabling simple debugging of 'distributed' scenarios - traditionally tricky and time-consuming to debug.

@nathan-beam What do you think?

@huesie your suggestions make sense. Maybe try making a PR yourself?


Add contact's work and quarantine address

Closing as https://github.com/AY2122S1-CS2103-W14-2/tp/pull/59 has been merged.


A simple, per-file metadata CRUD API

Fixes issue #:
#1048
Description of the changes being introduced by the pull request:
A simple, per-file metadata CRUD API that should make it easy to do the most common operations, without resorting to reading and writing the entire repository all at once.
Please verify and check that the pull request fulfills the following
requirements:

[ ] The code follows the Code Style Guidelines
[ ] Tests have been added for the bug fix or new feature
[ ] Docs have been added for the bug fix or new feature

Cc @joshuagl @sechkova @MVrachev @lukpueh @woodruffw

There is so much incomplete with this draft PR, but I hope it gives the right idea. Please let me know if you vehemently disagree with the approach here!
Cc @joshuagl @sechkova and @MVrachev who have agreed to help write and polish the code

Hi Joshua,

Observation: typing support requires Python 3.5+ or the typing package and f-string support requires Python 3.6.
This needn't block the initial implementation, but assuming we continue to flesh out this low-level API and use it in the refactor it might be exposed to the client, where we want to continue to support Python 2.7 and thus we can't use f-strings and may not want to add an additional dependency on typing.

Agreed. I left the typing in there as to help communicate intent between different developers 🙂 So you can think of it as scaffolding we can remove before hitting production...

Add bump_role() API somewhere?

Aha, it's not clear, sorry, but it's supposed to be a part of Metadata.sign(). Let me know whether this is a good idea or not...
How should we divide-and-conquer going forward?

Observation: typing support requires Python 3.5+ or the typing package and f-string support requires Python 3.6.
This needn't block the initial implementation, but assuming we continue to flesh out this low-level API and use it in the refactor it might be exposed to the client, where we want to continue to support Python 2.7 and thus we can't use f-strings and may not want to add an additional dependency on typing.

Agreed. I left the typing in there as to help communicate intent between different developers 🙂 So you can think of it as scaffolding we can remove before hitting production...

I assumed it was something like that, but thought it worth explicitly noting.

Add bump_role() API somewhere?

Aha, it's not clear, sorry, but it's supposed to be a part of Metadata.sign(). Let me know whether this is a good idea or not...

Ah, understood! We'll need a way to set/pass a delta by which to increase the expiration, which doesn't feel like it fits naturally into the method signature of sign() and is even less clean in the method signature of write_to_json(), from which sign() is called.
I thought a delta by which to bump the expiration could become a property of the Metadata object (i.e. PEP 458 recommends specific expiry deltas per role and this would map nicely) however the delta isn't a part of the metadata itself and therefore couldn't be loaded into the object by reading the on-disk representation and so this wouldn't work.
As this is defined as a low-level (or granular?) API, perhaps we should just be explicit and have functions for incrementing version number and increasing expiration. We can build convenience API around these in future as we flesh this out?

How should we divide-and-conquer going forward?

The to-do list I sketched above has many of the items broken down by module, perhaps you could tackle keys while we work on metadata?
Then we can hammer out typing, docstrings, tests, coding style and assertions as a follow-on task?

I've got some WIP changes https://github.com/joshuagl/tuf/commits/joshuagl/simple-update-api and have updated the to do list to indicate what I have done.
Note: I'm using a helper from #1031 – I don't think that should be a problem, but let me know

all of the code I've written so far assumes that the sequence of events is:
metadata = metadata.Metadata()
metadata.read_from_json('/path/to/metadata.json')

and therefore self.signatures and self.signed exist and are meaningful. That means we can't currently instantiate an object, populate it with code and write it to disk. We can only load and modify. That seems undesirable?
Should we smooth out the interaction model so that signatures and signed are only ever accessed as a property, like signable?
Additionally, should we make read_from_json() a class method that can be used to create an instance of an object by loading a file?
snapshot = Snapshot.read_from_json('/path/to/snapshot.json')

Should we smooth out the interaction model so that signatures and signed are only ever accessed as a property, like signable?

Yes, we should. Also, signatures and signed should be objects under signable, no?

Additionally, should we make read_from_json() a class method that can be used to create an instance of an object by loading a file?

💯

Should we smooth out the interaction model so that signatures and signed are only ever accessed as a property, like signable?

Yes, we should. Also, signatures and signed should be objects under signable, no?

I haven't implemented this suggestion yet as I was worried about the complexity increase of nested classes. I'd be curious to hear/read what everyone thinks of the current implementation.

I haven't implemented this suggestion yet as I was worried about the complexity increase of nested classes. I'd be curious to hear/read what everyone thinks of the current implementation.

This is simply looking fabulous, thanks very much, Joshua! 💯
I have a minor quibble about how we should make as many thing as possible private variables of the objects, but I started that, so it's on me, and it's also easy to fix 🙂

I haven't implemented this suggestion yet as I was worried about the complexity increase of nested classes. I'd be curious to hear/read what everyone thinks of the current implementation.

This is simply looking fabulous, thanks very much, Joshua! 💯

You're very kind, thanks!

I have a minor quibble about how we should make as many thing as possible private variables of the objects, but I started that, so it's on me, and it's also easy to fix 🙂

Completely agreed. I've added it to the list of things to address in https://github.com/theupdateframework/tuf/pull/1060#pullrequestreview-439026780

@joshuagl I think we're largely done, no? Should we get @woodruffw to start alpha-testing? 🧪

@joshuagl I think we're largely done, no? Should we get @woodruffw to start alpha-testing? 🧪

I'd certainly appreciate some user feedback on this API from @woodruffw !
The to do list before we can remove the draft flag from this PR is:

Figure out if/how to handle consistent snapshots

maybe this would be at the write_to_json() level? If consistent_snapshot is true we could massage the passed filename into the expected format for a consistent snapshot? Is that too magical? Should consistent snapshot handling be done at a higher level?

raise sslib.FormatError or ValueError instead of AssertionErrors (for input validation)
Add docstrings
Finish unit tests, ensure good (90%+?) coverage

The interface for metadata currently has two very similar properties:

Metadata.expiration can be used to set/get the expiration datetime object
Metadata.expires can be used to get the string representation of the expiration datetime object that we will write to the metadata

The names are a bit too similar for my taste, some thoughts:

should we make the expires property more explicitly named: expiration_string, or similar?
should we make expires an internal helper – will users of the public API ever need the string representation?
if so, should we add a setter for expires so that users can set the expiration datetime from an iso8601 string representation?

maybe this would be at the write_to_json() level? If consistent_snapshot is true we could massage the passed filename into the expected format for a consistent snapshot? Is that too magical? Should consistent snapshot handling be done at a higher level?

I think maybe we should pass a directory instead of filename to write_to_json() and if the consistent_snapshot flag is set, we can write an additional file in there. WDYT?

if so, should we add a setter for expires so that users can set the expiration datetime from an iso8601 string representation?

I like this option the best, but we should provide a more friendly interface that takes a relativedelta as an input instead of a datetime

maybe this would be at the write_to_json() level? If consistent_snapshot is true we could massage the passed filename into the expected format for a consistent snapshot? Is that too magical? Should consistent snapshot handling be done at a higher level?

I think maybe we should pass a directory instead of filename to write_to_json() and if the consistent_snapshot flag is set, we can write an additional file in there. WDYT?

That seems like a sound proposal to me.

We also need a similar interface for writing consistent targets...

Should we be handing consistent targets at this low-level API? At least in Warehouse we will be using existing fileinfo and not interacting with the targets directly, should we assume that a higher-level interface does the right thing with consistent targets?

if so, should we add a setter for expires so that users can set the expiration datetime from an iso8601 string representation?

I like this option the best, but we should provide a more friendly interface that takes a relativedelta as an input instead of a datetime

Just to be clear, are you advocating for public properties for setting/getting expiration as a datetime and an iso8602 string?
I made some assumptions that this low-level API might eventually end up as part of the client code and so explicitly opted to drop dateutil in favour of the standard library (https://github.com/theupdateframework/tuf/pull/1060/commits/54e1f9c03b09bdf05fd0a3cd3e4db35c6480c5a7) to reduce the number of dependencies that i.e. Pip will have to vendor (see #1065).
However, I did add a test and dateutil.relativedelta seems to behave as expected, see https://github.com/theupdateframework/tuf/pull/1060/commits/42372872d2a7f83bc4abad34d3f52a1d606fd786.

raise sslib.FormatError or ValueError instead of AssertionErrors (for input validation)

I lean towards consistently using TypeError and ValueError for bad arguments, since this is what they seem to be meant for.
The only advantage I can see of using a custom sslib's FormatError is that our own or user code can easily distinguish our Value/TypeErrors from those of other code. But I don't think that is necessary. Ideally, we validate arguments at the user boundary, so the user should know that we raised the errors, and all errors from further down the stack are our responsibility anyway, even if we didn't raise them. What do others think?
On a very related side-note, if we move away from our custom FormatError we also need to re-consider our usage of check_match, which anyways would be a good idea for the various reasons outlined in https://github.com/secure-systems-lab/securesystemslib/issues/183. :)

Add docstrings

I volunteer.

Regarding expiration:
IMO the class should have an expires attribute to align with the json metadata representation. The data type of that attribute could then either be a string in the required iso8602 format to fully align with the json metadata representation,  or a datetime object for easier further use. At any rate, we should have additional convenience methods with mnemonic names to set/get the date in the desired format.
FWIW in in-toto I keep the expires attribute as iso8602 string and provide a set_relative_expiration convenience method.

Should consistent snapshot handling be done at a higher level?

I think maybe we should pass a directory instead of filename to write_to_json() and if the consistent_snapshot flag is set, we can write an additional file in there. WDYT?

I like both your ideas. Can we keep write_to_json as is, and add a wrapper that does what Trishank says? E.g....
def write(self, metadata_dir, storage_backend=None):
    self.write_to_json(
        os.path.join(metadata_dir, self._name + ".json")

    if self._type == ROOT or self._consistent_snapshot:
        self.write_to_json(
                os.path.join(metadata_dir, self._version + "." + self._name  + ".json")

Thanks for getting back to me about my review comments, @trishankatdatadog, and generally thanks a lot for the hard work,  everyone!

Thanks for getting back to me about my review comments, @trishankatdatadog, and generally thanks a lot for the hard work, everyone!

Thanks, and where should we go from here? 🙂 Specifically, what can I help with?

Add docstrings

I volunteer.

So I haven't yet had a chance to write the docstrings... 😬
But following some discussions with @joshuagl I shuffled the metadata model class architecture quite a bit.  My intention was to make it even simpler and above all to make the classes match the metadata format specification more closely. An overview of the changes + rationale can be found in the commit message of 3e249f5bdd9e600475a05eab3587c5388eeedc3a.

Here is a summary of my thoughts about signing, signature verification and key handling in regards to this API.
Keys
Neither signing keys nor verification keys should be attributes of the role, i.e. Metadata.signed instance, they are meant to sign or verify. Instead and in order to align with the role model of the specification, they should be attributes of the delegating (this includes root) role. Same goes for the signature threshold.
Here are two suggestions how to design the signing (or verification) interface.
delegating_role.sign(delegated_role) # delegating role signs the delegated role
# or
delegated_role.sign(keys) # delegated role signs itself with keys, e.g. from delegating_role, or a detached keyring

Caveat:

Although signing keys conceptually belong to the delegating role (as in "delegating role signs for delegated role"), they must never be part of the corresponding role metadata.
This API might be used to sign delegated role metadata without having (or requiring) full knowledge of the delegating role (only the delegating role's keys are needed).

Sign
This PR currently proposes a sophisticated way of updating signatures by keyids. Although this seems convenient, I am not sure if there is actually a use case. In order to keep the interface minimal, I suggest to implement a sign function that just appends the signature, and leave it up to the caller if they want to first remove all or a few signatures from the list.
For comparison, here is how we do this in in-toto.
Verify
I think it would be good two provide two functions, one that only verifies if the signature(s) on the object are valid, and another one that checks if enough validly verified signature are available to meet a threshold.
In-toto has the former as method on the metadata class and the latter as part of the full in-toto final product verification routine.

Although signing keys conceptually belong to the delegating role (as in "delegating role signs for delegated role"), they must never be part of the corresponding role metadata.

I'm actually not so sure about this. A signing key probably does not need to belong to the delegating role, it could come from anywhere. So I suggest we have the caller decide where to get it from, and just pass it to the signing function as argument.
And we should provide the same workflow for the simple signature verification function, i.e. passing an unaffiliated key to just verify a signature. Even if, in the course of the client verification, the key (and threshold) are taken from the delegating role.

Here is a summary of my thoughts about signing, signature verification and key handling in regards to this API.

Agree with your thoughts. We could write some convenience functions later to make finding and associating the right Keys with the right Metadata, but we don't need them for now.

I was just writing a similar comment to @trishankatdatadog's. Really enjoying seeing this API evolve as a collaborative effort, thanks all!

I was just writing a similar comment to @trishankatdatadog's. Really enjoying seeing this API evolve as a collaborative effort, thanks all!

Likewise 🙂 Hoping to push soon that new type of Key I talked about yesterday... 🤞

Good news everyone: with 9285727ec50d1bb746c980525efc03d647f9925f, we finally have a Vault-TUF integration, where metadata can be signed and verified using ECDSA/Ed25519/RSA keys kept entirely in Hashicorp Vault 🚀
It is a decent start, but there are a few important TODOs left, notably:

[ ] Test that py-TUF can parse public keys produced by this integration
[ ] Test that py-TUF can verify signature produced by this integration
[ ] Allow passing in a prehashed input instead of the whole input

Before we finalize, I also think we should consider the notion of unbounded vs bounded keys.

The Vault integration sounds very interesting, great work @trishankatdatadog. 💯
I wonder whether a key management interface would be better suited to being integrated at the securesystemslib level, rather than TUF?
Even if TUF is the more appropriate home, I think it would be better to keep this PR focused on introducing the CRUD API. With any extra functionality built on top of that introduced in future PR's. What do you think?
On the CRUD API; @woodruffw did you have chance to review the proposed API and see how well it suits your needs for Warehouse integration?

Even if TUF is the more appropriate home, I think it would be better to keep this PR focused on introducing the CRUD API. With any extra functionality built on top of that introduced in future PR's. What do you think?

No problemo. I will let @lukpueh, @woodruffw, and yourself decide.

AFAICT initially this API was created having in mind easily updating a single targets metadata but if we consider it as a base of a tuf rework we need an implementation of a Root(Signed) class too.

The core feature of this PR, the metadata API, has landed in #1112. That leaves the Vault functionality of this PR.
I think securesystemslib would be a good home for it, but either way. Should we close this PR and open an Issue in sslib or here to request the Vault feature with a link to this PR for a reference implementation?

The core feature of this PR, the metadata API, has landed in #1112. That leaves the Vault functionality of this PR to resolve.
I think securesystemslib would be a good home for it, but either way. Should we close this PR and open an Issue in sslib or here to request the Vault feature with a link to this PR for a reference implementation?

Yes, please, we should upstream the Hashicorp Vault functionality against securesystemslib

Closing this PR as the metadata API landed in #1112.
Cross-linking to a securesystemslib Issue requesting an enhancement to support Hashicorp Vault: secure-systems-lab/securesystemslib#307


fix: steer_offset_for_command

fix steer offset for command
related to https://github.com/tier4/pacmod_interface/pull/23/files

Thank you. we will test this next week with real vehicle.


Context graph

I was wondering if there is any plan on adding context graph to k2/Icefall (something similar to :https://wenet.org.cn/wenet/context.html )
cc @csukuangfj

Yes, it is one of our plans and we‘ve made initial progress on this.

@marcoyang1998 Thanks ! Do you need a hand ? I started working also on it

@ezerhouni
could you have a look at https://github.com/k2-fsa/icefall/pull/645 and help propagate the changes to other folders in librispeech?

@csukuangfj Let me have a look. I can start doing the propagation tomorrow.
In the coming days I will open a PR for context graph, and if you have time to have a look it would be great

@csukuangfj Let me have a look. I can start doing the propagation tomorrow.
In the coming days I will open a PR for context graph, and if you have time to have a look it would be great

Sure, thanks!

@csukuangfj Also, in the last implementation modified_beam_search_ngram_rescoring, I might have found an error


Change the website to Nextra

The website is online. https://sotopia-lab.github.io/awesome-social-agents/


Question about getting the byte array

After calling imgcodecs::imencode I usually call the to_vec function from the resulting VectorOfuchar object.
Is there a better/faster way to get the array of bytes ([u8]) instead of transforming it into a vec?

Ugh, there is actually a to_slice method which does exactly that, but it's not marked as public by mistake. I'll push the new version with the fix soon.

It's available in version 0.23.0


Access request for srbala

Access level:

[x] Non-privileged
[ ] jenkins user
[ ] root/Administrative
[ ] other (Please specify):

System for which access is needed:
x86_64, aarm64, ppc64le, s390x
Please explain why you need this access including whether it is a temporary or permanent request:
Working on a PR fix for slim package, which affects multiple systems. https://github.com/AdoptOpenJDK/openjdk-docker/issues/339 team member recommented to access for my unit testing

(@sxa is on leave for a bit, so I'm picking this up).
test-packet-ubuntu1604-x64-1 : <IP_ADDRESS>
build-alibaba-ubuntu1804-armv8-1 : <IP_ADDRESS>
build-osuosl-centos74-ppc64le-1 : <IP_ADDRESS>
build-marist-rhel77-s390x-1 : <IP_ADDRESS>
Will these machines suffice? They all have docker installed and a fair bit of space free. If you send me your public ssh key I can create a user for you on each machine :-)

https://raw.githubusercontent.com/srbala/srbala/master/keys/srbala.pub

srbala@<IP_Address> should work now. I assume this is a temporary request, so I'll keep the issue open until you're finished.

@Willsparker Thank you. I have one PR Open waiting on review. Planning to make another one soon,  you can close afer it.

@srbala Have your PRs been reviewed / merged yet? :-)

@Willsparker one waiting to be reviewed, working on another PR

ping @srbala - is the access still required? If still awaiting other PRs can you link to them here please so we can track?

My access can be removed.
I have another PR for review, its for only X86 https://github.com/AdoptOpenJDK/openjdk-docker/pull/592

Thanks for the confirmation :-)


Fix test failure issue

Fixed some tests failures to make sure all tests under /Engine and /Rules are passed.

Also updated ReadMe info

Looks good to me.

Sign-off from me

Thanks!


Theme ignores "menu" override

I have a folder with a menu string override enabled, but the theme still shows the title instead (in this case, just "About me").

I've looked into it, and I saw that the "menu" override is a specific page header that has to be manually supported by the theme (a lot of page headers aren't automatically supported by themes btw). In my case, the reason why this override is being ignored is because I am directly calling page.title instead of page.menu from my navigation partial. I'll see to it that it is supported later. :)

I've added support for page.menu in the latest release. Let me know if it works for you @Lukaszeq.


[Feature Request} Number of alerts shown in IDS

I would like to see a way of saving the number of shown alerts in IDS to more than 7. When you select a higher number from the drop down, a page refresh always goes back to 7. I want to keep it, lets say, at 100.
There should be a way to make that choice permanent.

+1
Would be very helpful for me too. I prefer around 50 myself.


current published version relies on non-existent cloudydom/src/env path in newer versions of cloudydom

might be nice to do another publish to npm soon, since the published version is dependent on<EMAIL_ADDRESS> for me this resolves to<EMAIL_ADDRESS>which no longer contains the file cloudydom/src/env.  It has been moved to cloudydom/src/shadydom, I believe.
https://github.com/skatejs/web-components/blob/v5.2.1/src/index.js#L39

well actually right now we have * version added in this commit https://github.com/skatejs/web-components/commit/b9532dc312dad278403e35d31e71d297066ae75d#diff-b9cfc7f2cdf78a7f4b91a753d10865a2R38 I'm new to NWB, so I'm not sure if that is some requirement or best practice.
I would suggest to use exact versions as we are importing from internal structure which can easily change without major version change. What do you think @treshugart ?

This was republished under @skatejs/web-components which reset the version numbers because semantic-release (didn't know until now) determines version numbers based on the package name, not the tags.
If you install @skatejs/web-components you should be fine.


NOTICE: I will no longer deal with Issues

Can you please give ownership of the repo for someone else to maintain :)

Can you please give ownership of the repo for someone else to maintain :)

Yes, I transferred it to you.

Thanks.


CORE: Create Post Mapping for Trips page after the user has added recipes to that specific trip

Information from chatGPT.
@Controller
public class TripController {

    @Autowired
    private TripService tripService; // Assuming you have a service for managing trips

    @PostMapping("/createTrip")
    public String createTrip(@ModelAttribute TripForm tripForm, Model model) {
        // Here, TripForm is a POJO representing the form data for creating a trip
        // You would define this class with fields corresponding to trip details and selected recipes

        // Extract trip details from the tripForm object
        String tripName = tripForm.getTripName();
        int numberOfDays = tripForm.getNumberOfDays();
        float poundsPerPersonPerDay = tripForm.getPoundsPerPersonPerDay();

        // Extract the list of selected recipe IDs from the tripForm object
        List<Long> selectedRecipeIds = tripForm.getSelectedRecipeIds();

        // Create the trip entity and save it to the database
        Trip trip = new Trip();
        trip.setTripName(tripName);
        trip.setNumberOfDays(numberOfDays);
        trip.setPoundsPerPersonPerDay(poundsPerPersonPerDay);
        // Set any other trip details as needed
        tripService.saveTrip(trip);

        // Associate the selected recipes with the trip by creating TripRecipes entities
        for (Long recipeId : selectedRecipeIds) {
            Recipe recipe = recipeService.getRecipeById(recipeId); // Assuming you have a method to fetch recipes by ID
            if (recipe != null) {
                TripRecipe tripRecipe = new TripRecipe();
                tripRecipe.setTrip(trip);
                tripRecipe.setRecipe(recipe);
                tripService.saveTripRecipe(tripRecipe); // Assuming you have a method to save TripRecipes
            }
        }

        // Redirect to a confirmation page or another appropriate URL
        return "redirect:/tripCreated";
    }
}

In this example:
The TripForm class represents the form data submitted by the user for creating a trip. You would define this class with fields for trip details (e.g., tripName, numberOfDays, poundsPerPersonPerDay) and a list of selected recipe IDs (selectedRecipeIds).
Inside the createTrip method, you extract the trip details and the list of selected recipe IDs from the tripForm object.
You then create a new Trip entity and save it to the database using your TripService.
For each selected recipe ID, you fetch the corresponding Recipe entity from the database (assuming you have a method for that), create a TripRecipe entity to associate the recipe with the trip, and save it to the database.
Finally, you redirect the user to a confirmation page or another appropriate URL after successfully creating the trip.

Done


ansible-playbook -i inventory main.yml returning namespace error

Hi Jeff,
I am not knowledgeable enough with ansible to understand why this is breaking. I tried going to the file it is complaining about to see if I could figure out the issue with no luck. I am guessing it is some kind of domain type issue or an issue with my path. Just for clarification, I am running this on Windows 10 Pro using Ubuntu in the Windows Subsystem for Linux so that is why it is under /mnt/d. Any help? Here is the error:
ERROR! no action detected in task. This often indicates a misspelled module name, or incorrect module path.
The error appears to have been in '/mnt/d/pi/ansible/raspberry-pi-dramble-master/roles/geerlingguy.k8s_manifests/tasks/main.yml': line 14, column 3, but may
be elsewhere in the file depending on the exact syntax problem.
The offending line appears to be:

name: Ensure namespace exists.
^ here

Ahh, it is just syntactical. I noticed that this piece in the file is immediately following some [] brackets:

name: Ensure at least one manifest is in the list.
fail:
msg: "Please supply one or more k8s_manifests to apply."
when: k8s_manifests == []

name: Ensure a namespace is set.
fail:
msg: "The k8s_resource_namespace variable is not set."
when:

k8s_manage_namespace
k8s_resource_namespace == ''

anible-playbook --version for reference:
ansible-playbook 2.5.1
  config file = /mnt/d/pi/ansible/raspberry-pi-dramble-master/ansible.cfg
  configured module search path = [u'/home/astrochimp/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/lib/python2.7/dist-packages/ansible
  executable location = /usr/bin/ansible-playbook
  python version = 2.7.15rc1 (default, Nov 12 2018, 14:31:15) [GCC 7.3.0]

Uninstalled and reinstalled ansible and it seems to have fixed the issue.


Creating API models - is not authorized to perform: apigateway:GET

Before creating a new issue, please confirm:

[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.

Which UI component?
Liveness
Gradle script dependencies
I'm working with AMPLIFY-UI-ANDROID/samples/liveness and following the setup guide ->
// amplify-ui-android/samples/liveness/README.md
To the above, I do not understand well what would be needed within my permissions or if I need to make another change from the aws console., I hope for your comments.
Environment information
Welcome to Gradle 8.2.1!
Here are the highlights of this release:

Kotlin DSL: new reference documentation, assignment syntax by default
Kotlin DSL is now the default with Gradle init
Improved suggestions to resolve errors in console output
Reduced sync memory consumption

For more details see https://docs.gradle.org/8.2.1/release-notes.html

Gradle 8.2.1
Build time:   2023-07-10 12:12:35 UTC
Revision:     a38ec64d3c4612da9083cc506a1ccb212afeecaa
Kotlin:       1.8.20
Groovy:       3.0.17
Ant:          Apache Ant(TM) version 1.10.13 compiled on January 4 2023
JVM:          1.8.0_311 (Oracle Corporation 25.311-b11)
OS:           Mac OS X 10.16 x86_64
Please include any relevant guides or documentation you're referencing
https://github.com/aws-amplify/amplify-ui-android/blob/main/samples/liveness/README.md
Describe the bug
The following screenshot shows the error:

But within my AWS console, I've added permissions to authorize my user. I'll attach a screenshot ->

Reproduction steps (if applicable)
where I'm encountering an issue within the step:
Provision Backend API -> 3. Once finished, run amplify push to publish your changes.
next -> amplify push -> error!!

Code Snippet
// Put your code below this line.

Log output
// Put your logs below this line

amplifyconfiguration.json
{
"UserAgent": "aws-amplify-cli/2.0",
"Version": "1.0",
"auth": {
"plugins": {
"awsCognitoAuthPlugin": {
"UserAgent": "aws-amplify-cli/0.1.0",
"Version": "0.1.0",
"IdentityManager": {
"Default": {}
},
"CredentialsProvider": {
"CognitoIdentity": {
"Default": {
"PoolId": "us-east-1:9923229d-e322-4d23-bbf8-b22c8ed3a2c7",
"Region": "us-east-1"
}
}
},
"CognitoUserPool": {
"Default": {
"PoolId": "us-east-1_k4H5NZqDH",
"AppClientId": "5nhoomrfgc2visru2stud45bct",
"Region": "us-east-1"
}
},
"Auth": {
"Default": {
"OAuth": {
"WebDomain": "liveness70a2b540-70a2b540-dev.auth.us-east-1.amazoncognito.com",
"AppClientId": "5nhoomrfgc2visru2stud45bct",
"SignInRedirectURI": "myapp://callback/",
"SignOutRedirectURI": "myapp://signout/",
"Scopes": [
"phone",
"email",
"openid",
"profile",
"aws.cognito.signin.user.admin"
]
},
"authenticationFlowType": "USER_SRP_AUTH",
"socialProviders": [],
"usernameAttributes": [],
"signupAttributes": [
"EMAIL"
],
"passwordProtectionSettings": {
"passwordPolicyMinLength": 8,
"passwordPolicyCharacters": []
},
"mfaConfiguration": "OFF",
"mfaTypes": [
"SMS"
],
"verificationMechanisms": [
"EMAIL"
]
}
}
}
}
}
}
Additional information and screenshots
AMPLIFY VERSION :
12.11.1
DEVICE:
macOS - version 12.7.4

Although this was encountered while setting up the Liveness sample, this error occurs when executing amplify push with the CLI and is not related to the UI component itself.
Transferring to the CLI repo for triage.

Hey @RAISERALEX21, from the error message it appears this occurring on a IAM permission boundary set on the user the Amplify CLI is utilizing. Refer to this post providing additional information. I would suggest checking the boundary permissions and enable apigateway:GET to mitigate this behavior.

I've been trying to enable the permission as shown in the images... but so far, I haven't been successful, and I don't really have much experience with AWS IAM. Could you specify the steps I would need to follow to enable it?
I share my console settings in IAM.. ->

@RAISERALEX21 The permission boundary is a additional layer of security in IAM, the allow permission need to exist on both.
Refer to documentation on permission boundary.
The permissions boundary should be below the permissions policies section where you can add the necessary permmissions.

@RAISERALEX21 Glad to hear I was able to assist you. Do reach out if you are experiencing any issue. Closing the issue.


Split training images into training and test sets

The EBimage feature data has already been split into training and test sets. The additional splitting of the training set was performed so that we can evaluate model performance on a test set without evaluating performance on the final validation set.
In this issue, one should identify a solution to split the training image data into a training and testing set using the exact same splits as the EBImage data
EBImage data: https://github.com/cytodata/single-cell-classifier/tree/master/2.process-data/data

That means we are gone split the data in to 4 parts? The training and testing of 2.process_data + test data @fheigwer has hosted and now an other one?

Three parts:

Training
Testing
Validation

We have enough data to do this. We need to split the same samples in the raw image data.

Where does the data of http://<IP_ADDRESS>/scoringapp/ fit in to that? Because the data we download is already just a part of the full data set.

Good point - not really a "true" validation set then. Do we know of similar data that was collected in a different experiment? If so, then we don't need to split training

I would use the test-set what @fheigwer keep secret as a real test set. We only use it at the end to find out what works.
The test set of 2.process_data we can use to compare different model to each other (so the validation set). This one has the downside of leaked features because they are not split on well basis but cell basis, so one well can have training and validation data.
If a model needs to be trained we use the training set.
I don't think the leaked features problem can be solved. If we look at the number of wells we have to little to make a good split.
We have also leaked features because we try to reproduce the results from the hackaton. Only to models what works well on the test data we are using here. But I will ignore that for now
My proposal:

Training with training data
Compare the models with validation (test of 2.process_data)
after the best model is found train it with all data.
test it with @fheigwer secret data (this we only do once at the end)

I agree with this plan 👍

@gwaygenomics can I close this issue?

The task in this issue is not complete. The issue is to split images into the same training and test sets splits as the ebimage features. Does this make sense? Kinda separate from the plan you outlined above


BindingTransport does not allow transport.Converter to be used

Spoken to @slinkydeveloper on Slack about this. It turns out that migrating transports to use the new bindings API isn't compatible yet since there's no way to assign a transport.Converter to the binding.BindingTransport struct
Changes that need making:

Add a Converter transport.Converter field to the binding.BindingTransport struct
Update the SetConverter and HasConverter functions
Inside BindingTransport.handle(), use the encoding returned from ToEvent and if it's "EncodingUnknown" then use the Converter (if it's set)

Is this one still valid @n3wscott ?

No this isn't valid anymore, I'll close


Enable only authorised access to Selenoid

Hey 👋
I just installed Selenoid on DigitalOcean from its marketplace. Everything works fine but I couldn't find the way how to add any authentication to Selenoid service.
Now everyone who knows the IP address of my deployed droplet can access Selenoid but I want to have at least simple http auth to restrict access. I couldn't find anything regard this question in documentation. Anyone can help?

@ohld http://aerokube.com/selenoid-ui/latest/#_restricting_access

@vania-pooh Thanks for the links. But it is soo strange that Selenoid doesn't have any build-it authentication. Someone can sniff :4444 ports across all IPv4 addresses and find out some unhidden Selenoids.
Will this feature be implemented soon? Is it in Selenoid roadmap? I believe this is an important security issue.

@ohld no, this is not in our roadmap. We try to not overcomplicate things. If you need authentication - you can e.g. install Nginx in reverse proxy mode with basic authentication enabled.

Isn't it a security issue?

@ohld no, using Nginx ahead of application server is a common practice.


[Feature] Recover from abrupt node shutdown during SST

Is your feature request related to a problem? Please describe.
When one of the nodes with galera server is restarted abruptly during SST, pod may enter crashLoopBack due to stale  sst_in_progress/wsrep_sst.pid files.
WSREP_SST: [INFO] Stale sst_in_progress file: /var/lib/mysql/sst_in_progress (20240301 10:25:49.732)
WSREP_SST: [INFO] previous SST is not completed, waiting for it to exit (20240301 10:25:49.822)
2024-03-01 10:25:50 0 [Note] WSREP: (11659a97-92de, 'tcp://<IP_ADDRESS>:4567') turning message relay requesting off
WSREP_SST: [INFO] previous SST is not completed, waiting for it to exit (20240301 10:25:50.840)
WSREP_SST: [INFO] previous SST is not completed, waiting for it to exit (20240301 10:25:51.858)
WSREP_SST: [INFO] previous SST is not completed, waiting for it to exit (20240301 10:25:52.874)
WSREP_SST: [INFO] previous SST is not completed, waiting for it to exit (20240301 10:25:53.890)
WSREP_SST: [INFO] previous SST is not completed, waiting for it to exit (20240301 10:25:54.909)
WSREP_SST: [INFO] previous SST is not completed, waiting for it to exit (20240301 10:25:55.927)
WSREP_SST: [INFO] previous SST is not completed, waiting for it to exit (20240301 10:25:56.943)
WSREP_SST: [INFO] previous SST is not completed, waiting for it to exit (20240301 10:25:57.962)
WSREP_SST: [INFO] previous SST is not completed, waiting for it to exit (20240301 10:25:58.980)
WSREP_SST: [ERROR] previous SST script still running. (20240301 10:25:58.987)
2024-03-01 10:25:58 0 [ERROR] WSREP: Failed to read 'ready <addr>' from: wsrep_sst_mariabackup --role 'joiner' --address '<IP_ADDRESS>' --datadir '/var/lib/mysql/' --parent 1 --progress 0

From my understanding currently MariaDB Operator will not trigger recovery procedure if number of cluster member is higher than MinClusterSize of total number of replicas.
However, I think operator should also have mechanism to try to recover from above described unrecoverable state, because state with one or more servers in failed status results in:

makes it more likely to trigger full recovery procedure when another pod will enter error state
decreased read cluster performance

Describe the solution you'd like
Operator detects unrecoverable (i.e. pod restart triggered by liveness probe is not enough) state and recovers failed pod(s).
Describe alternatives you've considered
Operator waits for more pods to fail and then triggers recovery procedure.
Environment details:

Kubernetes version: 1.28.0
Kubernetes distribution: KIND
mariadb-operator version: 0.26.0
Install method: helm
Install flavor: custom

Additional context
Issue can be reproduced for tests with
k exec <pod> -- sh -c 'echo 1 > /var/lib/mysql/wsrep_sst.pid'
k delete po <pod>

Hey @djakobczak1 ! Thanks for suggesting this feature.
I think we could improve the management of  pending SSTs in the following ways:
Prevention
We could check whether the /var/lib/mysql/sst_in_progress is present in the agent side and return a 200 OK in the liveness probe. This way the Pod won't be restarted by Kubernetes when a SST is pending, potentially helping with the SST completion.
Detection
Expose an HTTP endpoint in the agent that would return a 200 OK when /var/lib/mysql/sst_in_progress is present. This way we can precisely know from the operator side if an SST is pending in every Pod.
Recovery
We could attempt to recovery the Pods with a pending SST in the following situation:

wsrep_cluster_size is greater than or equal than the MinClusterSize:
wsrep_cluster_size is less than the total number of expected Pods

To determine when a pending SST is in a unrecoverable state, we could introduce the following field:
spec:
  galera:
    recovery:
       podSSTTimeout: 3m

The operator will calling the new agent endpoint to determine whether an SST is in progress and it will track its duration in a status field:
status:
   pendingSSTStatus:
       - pod: mariadb-galera-1
         startTime: "2024-03-11T15:15:47Z"

When an SST reaches the timeout in certain Pod, the operator will:

Delete the /var/lib/mysql/sst_in_progress file in that Pod by calling another agent endpoint
Restart the Pod
Emit an Event and log it in info level to provide the user visibility for troubleshooting the issue on their end.

What do you think?

@djakobczak1 we are planning to implement this in the current release. Your input about https://github.com/mariadb-operator/mariadb-operator/issues/425#issuecomment-1988863427 would be helpful!

This is happening to me on one of my clusters.  Galera isn't triggering a recovery.  How can I manually recover from this until this feature is implemented?

@comminutus Manually deleting /var/lib/mysql/sst_in_progress in the Pod that is stucked performing the SST

@mmontes11 I tried that but when the pod restarts it comes back.


Sheik Zayed Road Dubai fix

As you know the Dubai road day says: Traveling above the  Sheik Zayed Road Dubai
But the night video just says:  Sheik Zayed Road

I looked in the community Json but I didn't want to mess anything up:)

Also @glouel You can do that with all the other ones that work that way:)

(please see my reply here too : https://github.com/JohnCoates/Aerial/issues/602#issuecomment-434273341)
So yep, Aerial does by default :

show community descriptions
show apple descriptions
show the video name

In that case there's neither a community description nor a Apple description (there are very few of these AFAIR). I'll add one for this one thanks.


Support i18n

What
We have plenty of hard coded user facing strings in English.

Article that seems to make it easy found by @n13: https://medium.com/flutter-community/i18n-extension-flutter-b966f4c65df9

I have implemented i18n already, just need to finish the remaining views.


Removed sm_database and the portable_binary_archive from the sm_boost…

… to reduce maintenance load
The former depends on the latter, which is not compatible with recent boost. If somebody needs to revive it, please also fix the compatibility or copy again from : https://github.com/boostorg/serialization/tree/develop/example

Any early objections?


Travis ci

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: baiyubin:x: mars.llmars.ll seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.

Changes Unknown when pulling 982d5c99b1d09c3601ca214c945bef554ee10376 on travis-ci into ** on master**.

Changes Unknown when pulling 982d5c99b1d09c3601ca214c945bef554ee10376 on travis-ci into ** on master**.


Use correct image replacement to use gosci for flux-app-v2 images

@uvegla whilst we're looking at this, the alpine/socat image which is patched into source-controller is also being pulled from dockerhub


Observer blocks not rotating

When i export a schema of a system of redstone and i paste it on new map, the observers blocks don't rotate
Any ideas ?

Okay this is  bug with mapping of observers I'm guessing that they need to be updated can you give some more info such as what version was the schematic created in and what version of MC did you paste the schematic into?

I use the last version of Mcedit u : <IP_ADDRESS>.
The version of my MC is 1.12.2 ; maps too


Incompatibilty cordova-plugin-googlemaps - phonegap-plugin-push

When i use "cordova-plugin-googlemaps" and "phonegap-plugin-push" plugins and i tried to open a project on android studio:
ERROR: In project 'app' a resolved Google Play services library dependency depends on another at an exact version (e.g. "[15.0.
1]", but isn't being resolved to that version. Behavior exhibited by the library will be unknown.

Dependency failing: com.google.android.gms:play-services-stats:15.0.1 -> com.google.android.gms:play-services-basement@[
15.0.1], but play-services-basement version was 16.0.1.

The following dependencies are project dependencies that are direct or have transitive dependencies that lead to the art
ifact with the issue.
-- Project 'app' depends onto com.google.firebase:firebase-messaging@{strictly 17.0.0}
-- Project 'app' depends onto com.google.android.gms:play-services-places-placereport@{strictly 16.0.0}
-- Project 'app' depends onto com.google.android.gms:play-services-location@{strictly 16.0.0}
-- Project 'app' depends onto com.google.android.gms:play-services-tasks@{strictly 16.0.1}
-- Project 'app' depends onto com.google.android.gms:play-services-basement@{strictly 16.0.1}
-- Project 'app' depends onto com.google.android.gms:play-services-base@{strictly 16.0.1}
-- Project 'app' depends onto com.google.firebase:firebase-iid@{strictly 16.0.0}
-- Project 'app' depends onto<EMAIL_ADDRESS>-- Project 'app' depends onto com.google.android.gms:play-services-maps@{strictly 16.0.0}
-- Project 'app' depends onto<EMAIL_ADDRESS>-- Project 'app' depends onto<EMAIL_ADDRESS>-- Project 'app' depends onto com.google.android.gms:play-services-stats@{strictly 15.0.1}
-- Project 'app' depends onto com.google.firebase:firebase-measurement-connector@{strictly 16.0.0}
-- Project 'app' depends onto com.google.firebase:firebase-common@{strictly 16.0.0}
-- Project 'app' depends onto com.google.firebase:firebase-iid-interop@{strictly 16.0.0}

For extended debugging info execute Gradle from the command line with ./gradlew --info :app:assembleDebug to see the dep
endency paths to the artifact. This error message came from the google-services Gradle plugin, report issues at https://
github.com/google/play-services-plugins and disable by adding "googleServices { disableVersionCheck = false }" to your build.gradle file.

I read a lot of documentation on internet, and i understand that the problem is because the plugins uses different versions, but i dont know how can i fix it.
Thanks for all.

You can specify the version of the Google Play Services for this plugin using <preference name="GOOGLE_MAPS_PLAY_SERVICES_VERSION" value="16.1.0" /> in config.xml file

I tried with your recomendation:

In your documentation you told about 16.0.1 (https://github.com/mapsplugin/cordova-plugin-googlemaps) and then I changed to:

And the error is:
ERROR: Failed to resolve: com.google.android.gms:play-services-maps:16.0.1
Show in Project Structure dialog
Affected Modules: app
ERROR: Failed to resolve: com.google.android.gms:play-services-location:16.0.1
Show in Project Structure dialog
Affected Modules: app
At the end, i test with:

And Android studio dont show errors, but i dont know if the app will be ok
What do you think?

What version do you use of this plugin ?
(Please provide enough information in advance)

Sorry. I use the las versions of all plugins.
I uploaded the project files to:
https://github.com/u01ser/test-pushandmap
The only way for everything works that i found is:

I dont know if this is the best way for your plugin.
Thanks for all!

15.0.1 is OK, if you don't use Panorama class.

I don't know other developer's plugin details, but I was able to build with:
FCM_VERSION = 20.2.1 and GOOGLE_MAPS_PLAY_SERVICES_VERSION = 16.0.0

More further, please ask to the phonegap-plugin-push developer, not me.

I don't know other developer's plugin details, but I was able to build with:
FCM_VERSION = 20.2.1 and GOOGLE_MAPS_PLAY_SERVICES_VERSION = 16.0.0

Not work for me.
I put in the config.xml "" and "". And in the package.json i have "FCM_VERSION": "20.2.1" but it doesn't work for me.
Can you tell me how do you make it work?

More further, please ask to the phonegap-plugin-push developer, not me.

You are absolutely right, and I appreciate your answers a lot. I think you are a good developer and good person.  I didn't know the problem was on the other plugin.
Thanks for all!

Sorry, this is not free helping service, and I'm so busy person. Please do your best.

I have the same problem and was just able to build using this:
https://github.com/phonegap/phonegap-plugin-push/issues/2902
Try it and let me know. I haven't found any bugs or downsides yet. Will report if I find any!


Update README.md with project description

Dependent on #6

the project title
a short summary of the project (view from 10,000 feet)
how to run your data analysis
a list of the dependencies needed to run your analysis

=> this document should live in the root of your public GitHub.com repo.

https://github.com/miniatureseal/dsci-310-group-10-GCC/pull/27

Added description how to run the analysis file: #39
With that this issue is done!


Bulk run giving TypeError after unencoded_variants test added

I was trying to test out some new gflang data sets and after the unencoded-variants was added the bulk run errors out with the following error:
Traceback (most recent call last):
  File "/home/neilspatel/Shaperglot/shaperglot-env/bulk-sg-run.py", line 133, in <module>
    main()
  File "/home/neilspatel/Shaperglot/shaperglot-env/bulk-sg-run.py", line 123, in main
    summarize(tag, fontname, this_tag_results)
  File "/home/neilspatel/Shaperglot/shaperglot-env/bulk-sg-run.py", line 69, in summarize
    for code, failure in results:
TypeError: cannot unpack non-iterable Message object

I have been chasing my tail trying to understand why this would happen. I am not sure if I am missing something obvious. What is odd is that this is occurring even if I am not using the new check.  This should be only running the default no_orphaned_marks and orthographies checks so I don't understand how adding the new check would cause this since nothing else was changed.

My fault, I changed the Message interface and so things using shaperglot will break if they're not updated. We should probably put the "bulk-sg-run" script into this repo while the shaperglot API is in flux, so that it can be updated too.


Confusion regarding conflicting information in model card of "mosaic-bert" on Hugging Face

I have been referring to the model card of "mosaic-bert" on Hugging Face, and I noticed some conflicting information that has left me confused. In the model card, it is mentioned that the vocabulary size was increased to a multiple of 8 and 64 (from 30,522 to 30,528 tokens). This suggests that either a new vocabulary was fitted or additional tokens were added to the standard bert-base tokenizer.
However, later in the model card, it states that "The tokenizer for this model is simply the Hugging Face bert-base-uncased tokenizer" with the original 30,522 tokens. This inconsistency has created confusion for me, as it seems contradictory to the previous statement regarding the increased vocabulary size.
Additionally, the respective blog mentions that one can use their own custom vocabulary and tokenizer for a specific domain. I am intrigued by this possibility but unsure of how it can be accomplished. I would appreciate further clarification on how to employ a custom vocabulary and tokenizer with the "mosaic-bert" model.
Thank you for your attention to this matter. I look forward to your response and clarification regarding these issues.

The tokenizer is unchanged, but the model's word embedding layer is expanded for hardware efficiency. This means that there are a few unused tokens that are never seen during training.
To employ a new tokenizer, you would need to (1) create that tokenizer (2) train a new model using data processed by that tokenizer. We don't have a guide for (1), but i recommend looking through huggingface's materials on the subject (https://huggingface.co/learn/nlp-course/chapter6/2?fw=pt#training-a-new-tokenizer could be a good starting point). For (2), once you have your new tokenizer, you can basically just plug it into the existing code/yamls.

Perfect, thank you very much!


Keptn 0.11.x Tutorials Update + Quickstart guide + New Learning path

This pull request is a bulk update that produces a new version with the following goals

[x] Update the Keptn Tutorials for the 0.11.x release which was missing before
[x] Make 0.11.x the tutorial displayed by default. Was 0.9.x before
[x] Link the Tutorials site to the public quickstart Guide on the Keptn website
[x] Introduce a new learning path when tutorials start from quickstarts: Local or a Public Demo. Only after that a full tour is offered

This is a temporary implementation for the Quickstart tutorial, later a new one  will be introduced along with Antora
Screenshots
Default landing:

Quickstart landing:

Quickstart tutorial:

Depends on

https://github.com/keptn/keptn.github.io/pull/983
https://github.com/keptn/examples/pull/215
https://github.com/keptn/keptn.github.io/pull/988

I will merge it and address issues incrementally. Thanks @johannes-b !


Finish the Training Documentation - Processing Team

Description:
During Business Coord April 19, we developed draft documentation for training with the Processing Team's train-the-trainers. The DOD below covers remaining tasks needed to complete this documentation
DOD

[ ] Review
[ ] Complete Extension section
[ ] Complete any other fields needed (ie: Assignments)
[ ] Beautify

cc: @lmullane @JHarrietha-AOT

Closing - training is complete for this


bump analytics-commons version

$subject

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/3150739042

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/3150739042
Status: success


Paste is not working on some applications

JetBrains Pycharm IDE does not accept pasted elements.
When trying to paste something from Clippy, the text is not pasted in the editor of the IDE nor in any text dialog.
Environment: macOS Monterey.
Application: PyCharm Professional 2021.3.1

I see the same thing in another application in the JetBrains family (IntelliJ).

I just tried pasting in IntelliJ IDEA 2021.2.3 (Community Edition) and it worked without problems. Could you provide more details about the Maccy version, the output of running defaults read org.p0deje.Maccy in the Terminal.app and the video of the problem.

Thanks, I just tried again and it worked.... very strange. I'm on IntelliJ IDEA 2021.2.3 (Ultimate Edition)
I have re-started Maccy since having this problem. With it now working this is the output from defaults:
{
    "KeyboardShortcuts_popup" = "{\\"carbonModifiers\\":768,\\"carbonKeyCode\\":8}";
    NSNavPanelExpandedSizeForOpenMode = "{800, 448}";
    "NSWindow Frame NSNavPanelAutosaveName" = "880 725 800 448 0 0 2560 1415 ";
    "NSWindow Frame SUStatusFrame" = "1080 961 400 134 0 0 2560 1415 ";
    "NSWindow Frame com.sindresorhus.Preferences.FrameAutosaveName" = "999 377 562 713 0 0 2560 1415 ";
    SUEnableAutomaticChecks = 1;
    SUHasLaunchedBefore = 1;
    SULastCheckTime = "2022-01-05 09:28:12 +0000";
    enabledPasteboardTypes =     (
        "public.tiff",
        "public.file-url",
        "public.png",
        "public.utf8-plain-text"
    );
    history = {length = 42, bytes = 0x62706c69 73743030 a0080000 00000000 ... 00000000 00000009 };
    ignoredApps =     (
        "com.apple.keychainaccess"
    );
    ignoredPasteboardTypes =     (
        "net.antelle.keeweb",
        "de.petermaurer.TransientPasteboardType",
        "com.typeit4me.clipping",
        "Pasteboard generator type",
        "com.agilebits.onepassword"
    );
    migrations =     {
        "2020-02-22-history-item-add-copied-at" = 1;
        "2020-02-22-history-item-add-number-of-copies" = 1;
        "2020-04-18-switch-storage-to-core-data" = 1;
        "2020-04-25-allow-custom-ignored-types" = 1;
        "2020-06-19-use-keyboardshortcuts" = 1;
        "2020-09-01-ignore-keeweb" = 1;
        "2021-02-20-allow-to-customize-supported-types" = 1;
        "2021-06-28-add-title-to-history-item" = 1;
        "2021-10-16-remove-dynamic-pasteboard-types" = 1;
    };
}```

If I can manage to break it again I'll update the ticket.

I am also able to paste texts now in PyCharm. Although I tried to restart the application and the machine previously and was not successful to paste, now it is working fine.
Will provide more info if the issue appeared again.
Thank you

Mystery! I'll close the issue for now, please re-open if it happens again with more details.


Can I hide the "0 backlinks / 0 words / 0 characters" status bar in the gallery view only?

It's present in graph view (!) which makes me think there's no easy way to hide it, or it'd be hidden there.


New option for a tile format with application names under program

I'd love to see this Feature. But I think for width=1 it makes more sense to put the name on the right side of the logo.
Maybe the user can choos between list style and logo style like on windows explorer.


Feature request: Search/Filter bar in the multi-select Select form component

Would love to have the option to easily add a Search/Filter bar at the top of the multi-select dropdown boxes.

The above screenshot is using Bootstrap's Multi-Select plugin.  So I am looking for that same functionality from Materialize.  Here is a live example of how it works: https://www.jquery-az.com/boots/demo.php?ex=63.0_9
Thanks!

I'm not sure if Google Material Design specifies something like this.
https://material.io/components/text-fields
I think it is the Autocomplete component but with different options / entries.
https://materializecss.com/autocomplete.html

Yeah, I looked at Autocomplete and the existing Select "multi" function.  There is nothing currently that fully meets my needs.  The existing Select "multi" is very close...it just needs the filter bar.  And as you type in the bar, the list shrinks to only what matches.  If that could be added, that would perfect!

I'm not familiar with materialcss code, but there is a thread talking about this topic and gave temp  solution before. Hope it helps and can integrate into new features in the future ：D
https://github.com/Dogfalo/materialize/issues/3096#issuecomment-621497307

Hi, I added some features to the script, linked above:

nicer handling of optgroups -> hide if no child matches search pattern, show optgroup if it has at least 1 visible child
handle keyboard navigation

handle ArrowUp + ArrowDown focus selection
grab focus when open event was triggered by keyboard

supports multi select

You can find a demo here https://jsfiddle.net/cherrg/vgn3Law4/
The code could be found here: https://github.com/Dogfalo/materialize/issues/3096#issuecomment-778513315
Sorry for the duplicate with the referenced issue, but here are some maintainers :) may this feature finds its way into the code.
If you find some bugs or possible improvements (or suggestions) to the behavior of this script, please comment.
(May I will build an update for materializecss and create an PR after some time.)

Thank you, this looks good =)

May I will build an update for materializecss and create an PR after some time

That would be awesome 👍

@LoganTann I would say this is out of scope of the Google Material spec so this should be some separate package.
I would vote to close this issue. What do you think @materializecss/members

@computerwiz12890 sure, but otherwise we would end in feature creep, adding more and more features to materialize which introduce new problems, need more tests and so on.
Generally we should check what the other members think about this, that's why I've mentioned the members of the org.
If there is a PR that can be reviewed (even if it is unfinished or a draft) that would be helpful because getting feedback as early as possible is very important.
At the moment v1 and the v1.1 release are meant to fix bugs. New features will be introduced in v2, which will be the new default branch after the v1.1 release.

In my opinion, adding a basic search feature as option is a good idea. For the more advanced ones, we can separate that in another package.
The material based framework Vuetify features this, but in a separate component called "autocomplete".


Would this work for ios11?

HI, I am working on some development for ios11. Would Caffe2-iOS work on that platform?

@gsrujana Haven't fully tested on iOS 11 yet but whenever the official release is public I will test it out and update in the readme.

Looks still working.

validated and therefore close


DOIs for references

My understanding of the review instructions for the JuliaCon proceedings is that your references bib file should contain DOI identifiers, e.g. for the Julia paper by Bezanson et al.

Adding the DOIs to the .bib file is enough.


Automatically choose --from_safetensors when appropriate

If you forget to set --from_safetensors True when downloading models, you get:
ValueError: Expected 'checkpoints/google/gemma-2b' to contain .bin files

We assume that users perfectly follow the download tutorial guides where --from_safetensors True for some commands. But intuitively, I feel like the download scripts could probably choose this automatically. Some need it, some don't.

Yeah, I think we originally added it for mistral and only few others need it (like Gemma).
I wonder if we should make --safetensors true the new default for the new user experience. It's actually safer :). And if a safetensor format is not available, we throw a warning and say "download the model with --safetensors false`. What do you think?

There should be a way to check are there any files in the repo with .safetensors extension.

This looks reasonable to me. We already import from huggingface_hub so that wouldn't add an additional dependency


DWARF: Fix a bug in array size computation

Summary:
r346165 introduced a bug, where we would fail to parse the size of an
array if that size happened to match an existing die offset.
The logic was:
if (DWARFDIE count = die.GetReferencedDie(DW_AT_count))
num_elements = compute_vla_size(count);
else
num_elements = die.GetUsigned(DW_AT_count); // a fixed-size array
The problem with this logic was that GetReferencedDie did not take the
form class of the attribute into account, and would happily return a die
reference for any form, if its value happened to match some die.
As this behavior is inconsistent with how llvm's DWARFFormValue class
operates, I chose to fix the problem by making our version of this class
match the llvm behavior. For this to work, I had to add an explicit form
class check to the .apple_XXX tables parsing code, because they do
(incorrectly?) use data forms as die references.
Reviewers: aprantl, clayborg
Subscribers: JDevlieghere, lldb-commits
Differential Revision: https://reviews.llvm.org/D55991
git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@350086 91177308-0d34-0410-b5e6-96231b3b80d8
(cherry picked from commit 1aead698a042d234b9213bdaf9e91b848fcda219)

@swift-ci test and merge


build: remove use of set-output

:tada: This PR is included in version 1.3.0 :tada:
The release is available on:

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


move from "docker" to "container" to prepare for podman support

Context
Palm relies on containerization. Presently that has been 100% via Docker, but we'd like to expand the ecosystem to a fully OSS offering.
Is your feature request related to a problem? Please describe.
Docker is not OSS and there are limitations, and the learning curve for a thing like podman is not steep but does exist.
We want to make the switch painless for our users, and we can start by abstracting "Docker" command aliases in palm to "container" commands. then under the hood we can run in the container engine of the user's choice.
Describe the solution you'd like
run_in_docker becomes run_in_container. Then under the hood we pipe the work to Docker, OR have the ability to use podman instead.
Describe alternatives you've considered
Stick with pure Docker support. Meh.
Additional context
This can start by abstraction and then balancing 100% of requests to a Docker mechanics class for now. That way we can roll podman as seperate work.
Is there an existing feature request for this?

[x]  I have searched the existing issues

We should alias all these with a deprecation warning, not remove them completely.

Podman seems like a really strong option and feels like the right pick for our team. But we should keep in mind that there are alternative options that other teams may go with. I've seen some traction around using minikube as a replacement for docker desktop. Ideally, the final state of this implementation would include an abstraction that allows us to support different containerization tools, potentially via plugins or configuration.


[Analyzer] Fix for group_bys with no aggregations

Currently Analyzer fails for the configs that has no aggregations defined.
This fix should take care of it by making sure the GroupBy doesn't raise
a NullPointerException for the group_bys with no aggregations.
Tested and verified that it works against the configs with no group_bys.

issue has been fixed in main branch. closing this.


Add log readers

Based on the work op @qubixes in simulations project.
Log readers output Logger objects.
@qubixes Shall we rename Logger into ALLog. Logger is also used in the default lib logging I think.

@qubixes Can you review this one?