[Fix] Fixed the inputs to the ManagerAgent

End-user friendly description of the problem this fixes or functionality that this introduces

[ ] Include this change in the Release Notes. If checked, you must provide an end-user friendly description for your change below

Give a summary of what the PR does, explaining any non-trivial design decisions
This PR addresses an issue in the openhands/agenthub/micro/manager/prompt.md file. The main change involves updating the placeholder for the task input from {{ latest_user_message }} to {{ state.inputs.task }}. This change ensures that the task delegated to the agent is correctly sourced from the state variable as specified in agent.yaml

Link of any specific issues this addresses
Issue #4426

I think the issue here is that ManagerAgent can be run directly, not as a delegate, and it needs a MessageAction for its 'task'. The test is failing because of this.
The linked issue is about trying to run it as delegate itself. The way we handle this elsewhere is that we figure out the appropriate goal according to whether it has a task from a MessageAction (via state.get_current_user_intent) or from inputs['task'], e.g. like this.

The linked issue is about trying to run it as delegate itself. The way we handle this elsewhere is that we figure out the appropriate goal according to whether it has a task from a MessageAction (via state.get_current_user_intent) or from inputs['task'], e.g. like this. Maybe that's what we need?

Agreed, let me refactor it


[e2e]: generic workflow_dispatch branch1 default slsa3

Repo: https://github.com/slsa-framework/example-package/tree/branch1
Run: https://github.com/slsa-framework/example-package/actions/runs/7859258263
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.generic.workflow_dispatch.branch1.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.generic.workflow_dispatch.branch1.default.slsa3.yml
Trigger: workflow_dispatch
Branch: branch1
Date: Sun Feb 11 03:10:45 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/branch1
Run: https://github.com/slsa-framework/example-package/actions/runs/7866768213
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.generic.workflow_dispatch.branch1.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.generic.workflow_dispatch.branch1.default.slsa3.yml
Trigger: workflow_dispatch
Branch: branch1
Date: Mon Feb 12 03:10:28 UTC 2024
Tests are passing now. Closing this issue.


Render NotFoundContent via route if routeBasePath is /

Pre-flight checklist

[x] I have read the Contributing Guidelines on pull requests.
[ ] If this is a code change: I have written unit tests and/or added dogfooding pages to fully verify the new behavior.
[ ] If this is a new API or substantial change: the PR has an accompanying issue (closes #0000) and the maintainers have approved on my working plan.

Motivation

Fixes https://github.com/facebook/docusaurus/issues/9688
The behavior was semi-inspired by option 1 to https://github.com/facebook/docusaurus/issues/9688#issuecomment-1878522911
Test Plan

(Let me know what else needs to happen)
On the repo which reproduces https://github.com/facebook/docusaurus/issues/9688, I made this change (e.g. leveraged my fork) and was successfully able to get a 404 on any /<whatever> page, while still getting the content on the correct docs subroutes.
Test links

Deploy preview: https://deploy-preview-_____--docusaurus-2.netlify.app/
Related issues/PRs

Oh, and if y'all want I can (temporarily) change the website to use / as the routeBasePath as a demonstration :+1:

I just realized that this stomps on if there are other plugins involved (like a blog).
Will move back to draft.


Fixed Accessibility in Home SPA

Closes/Fixes/Resolves

Explain the feature/fix

Does this PR introduce a breaking change

Screenshots

View Screenshots

Ready-for-merge Checklist

[ ] Expected files: all files in this pull request are related to one feature request or issue (no stragglers)?
[ ] Does the change have appropriate unit tests?
[ ] Did tests pass?
[ ] Did you update or add any necessary documentation (README.md, WHY.md, etc.)?
[ ] Was this feature demoed and the design review approved?

Kindly specify the names of env u want to specify in the given format [dev,stage,qa]

["dev","qa","test"]

The third-party API responded with: undefined


Change from 6 to 4 files

Issue entered on main app, baytrendsmap.
https://github.com/tetratech/baytrendsmap/issues/65

Combine Full period and 1999 files into long term.

v<IP_ADDRESS>36
https://github.com/tetratech/baytrendsmap/commit/ec757e9e15e1631715ca0c741ade8e2d518bd548


How to set animation?

Hi
How to set animation to show and hide of Dialog?

https://www.google.com/search?q=dialog+animations+android

i need to set animation to  MaterialDialog,not the android sdk dialog.
for example add ".setAnimation(...)"
to this builder.
new MaterialDialog.Builder(this)
.title(R.string.title)
.content(R.string.content)
.positiveText(R.string.agree)
.negativeText(R.string.disagree)
.show();

MaterialDialog is an android.app.Dialog.

You'll have to build the dialog before showing it.


try/except masks connection exception reducing debugability

This significantly reduces debugability of permissions issues and other connection problems, I don't see a clear reason not to simply remove the try/except and let it bubble up
https://github.com/QphoX/CryoSwitchController/blob/57df8ab8f1d6efd05bae9381cf0e5492d2039cf1/libphox.py#L82

I would also recommend looking at pythons builtin logging framework instead of the sprinkled in debug prints for better user experience and debuggability


Adding secret manager + ec2_key_pair to main.yaml

Reason to bump docker-compose to sudo;
There were some issues with creating a folder for the data when HeyEmoji was bootstrapped. This seemed like the most straight forward solution.
During testing I did end up using ubuntu user folders (in the $HOME directory) so this could be realistically be removed..

Ran git merge main and it said "everything is up to date" so instead of messing around to much with this I created a new branch with a clean PR


Allow HTTPS to be enforced via environment variable

Summary
Implement the HTTPS Enforcement configuration settings for Web Servers RFC0004.
Proposal
When the BP_WEB_SERVER_FORCE_HTTPS environment variable is set to true, the buildpack will generate configuration in the httpd.conf file that forces http requests to be redirected to https endpoints. Check out https://cwiki.apache.org/confluence/display/httpd/redirectssl for details on how to configure this in httpd.conf.
Outcome
Given an application with no httpd.conf file, when we run pack build myapp --buildpack paketo-buildpacks/httpd --env BP_WEB_SERVER=httpd --env BP_WEB_SERVER_FORCE_HTTPS=true, then we should see the application can be built and that the static files are served by HTTPD with http requests being redirected to https.

https://httpd.apache.org/docs/2.4/bind.html

Scratch the above comment. Use this directive instead https://cwiki.apache.org/confluence/display/HTTPD/RewriteHTTPToHTTPS


Can't call open_mfdataset without creating chunked dask arrays

What happened?
Passing chunks=None to xr.open_dataset/open_mfdataset is supposed to avoid using dask at all, returning lazily-indexed numpy arrays even if dask is installed. However chunks=None doesn't currently work for xr.open_mfdataset as it gets silently coerced internally to chunks={}, which creates dask chunks aligned with the on-disk files.
Offending line of code:
https://github.com/pydata/xarray/blob/12123be8608f3a90c6a6d8a1cdc4845126492364/xarray/backends/api.py#L1040
What did you expect to happen?
Passing chunks=None to open_mfdataset should return lazily-indexed numpy arrays, like open_dataset does.
Minimal Complete Verifiable Example
ds = xr.tutorial.open_dataset("air_temperature")

ds1 = ds.isel(time=slice(None, 1000))
ds2 = ds.isel(time=slice(1000, None))

ds1.to_netcdf('air1.nc')
ds2.to_netcdf('air2.nc')

combined = xr.open_mfdataset(['air1.nc', 'air2.nc'], chunks=None)

print(type(combined['air'].data))

MVCE confirmation

[X] Minimal example — the example is as focused as reasonably possible to demonstrate the underlying issue in xarray.
[X] Complete example — the example is self-contained, including all data and the text of any traceback.
[X] Verifiable example — the example copy & pastes into an IPython prompt or Binder notebook, returning the result.
[X] New issue — a search of GitHub Issues suggests this is not a duplicate.
[X] Recent environment — the issue occurs with the latest version of xarray and its dependencies.

Relevant log output
dask.array.core.Array

Anything else we need to know?
As the default is None, changing this without changing the default would be a breaking change. But the current behaviour is also not intended.
Environment
main

Passing chunks=None to open_mfdataset should return lazily-indexed numpy arrays, like open_dataset does.

Can't do this without virtual concat machinery (https://github.com/pydata/xarray/issues/4628) which someone decided to implement elsewhere 🙄 ;)
We should change the default to chunks={} in anticipation though.

Can't do this without virtual concat machinery (https://github.com/pydata/xarray/issues/4628) which someone decided to implement elsewhere 🙄 ;)

😅
It's still broken at the moment though - I had a (ridiculous) case where I don't care that concat will load everything in memory, I just want to completely avoid creating dask.array objects, and right now there is no possible input option to open_mfdataset to do that.

We could change the default to chunks={} in anticipation though.

That's probably more useful, as well as actually being consistent.

See #5704 for changing chunks={} and more discussion.


Add repo docs

These are a few of the docs Taylor and I use in our projects. Could possibly be helpful. @kellychurchill please review and let me know if 👍  or 👎

I also wanted to ask before adding a License here.

For License for this project specifically, I think we can take the lead from what other starter projects have done https://www.gatsbyjs.org/docs/gatsby-starters/

@kellychurchill The default one has an MIT license. I have added to this PR. If it's cool with you I will merge.


The condition of convergence needs to be revised for async algorithms.

The current way to determine convergence is to see if one state's update is below some threshold. The async algorithm may have the magnitude of one state's update being below the threshold while the convergence is still not achieved -- other states' values may still be changed.
We need to change this condition for async algorithms. For example, we can say there is a convergence when the updates to all states in the previous sweep are below the threshold.

You're right. A similar alternative is to check for convergence over a window of N (potentially equal to |S|) updates.

How do we feel about the approach in our evaluation experiment program?
For sync algorithm, it checks if the mean-absolute update to the values across all states is less than a tolerance.
For async, it performs this check over the last |S| updates.

The current approach looks good. Perhaps later we might modify the search control procedure in the async case to pick states arbitrarily (based on the discussion in #16). Then we might average the the last N updates, where N is a large number.
Hmm, I guess N could still be equal to |S|.
Thoughts?

@abhisheknaik96 Since Rich hates convergence checks in general, I think this will never be part of the code that is holding us up. When we start doing async updates in a random order we can relax this condition to ensure we are not stopping too early.
Closing for now.


"Loading, please wait..."

Why after I login, it always shows "Loading, please wait..."
At the beginning I thought I was blocked. But after you guys working so hard and released an update, I found same problem doesn't go away...

Firewall, proxy, blocked IP range, etc.

@Mirx Why am I blocked? And what should I to free myself? Change a new account?
I am just a normal pokemon player. These stuff are too complicated to me... but sounds interesting.

What login type are you using for your map account? Google or PTC. The added some security steps in there, which you might first need to perform before your account will be operational.
https://github.com/mchristopher/PokemonGo-DesktopMap/issues/753#issuecomment-238297269

@Mirx Google account is what I am using. And it is also my secondary pokemon go account. It doesn't matter to if it is softbanned.

@Mirx I tried on another macbook. And it is working well. So it was not the problem with account, but with my computer... Don't understand what is wrong with my macbook???

Same problem here. I started from the terminal and there I get an error about the config


Error: Undefined property $columns on hasManyThrough relationship

There seems to be an issue when working with hasManyThrough relationships. This is my query:
$campaigns = User::find($user_id)->campaignDetails()->select(['user_campaigns.user_id','campaign_details.campaign_id as as','campaign_name','campaign_status']);
        return Datatables::of($campaigns)->make(true);

public function campaignDetails()
    {
        return $this->hasManyThrough('App\CampaignDetail','App\UserCampaign','user_id','campaign_id');
    }

This is the code that seems to be causing the problem. Line 298 in Datatables\Datatables.php:
$this->columns = $this->query_type == 'eloquent' ? $this->query->getQuery()->columns : $this->query->columns;
But it seems that Eloquent is not returning you the columns and that's why I'm guessing it's failing? Any workaround?

Hi, haven't tried the package via HasMany and the likes but will surely check this out on my free time.
In the meantime, the workaround you can do is by using a join statement manually like below: Just adjust it according to your tables definition.
$campaigns = Campaigns::join('user_campaigns','user_campaigns.campaign_id','=','campaigns.id')
	->join('campaign_details','campaign_details.id','=','user_campaigns.details_id')
	->select([
		'user_campaigns.user_id',
		'campaign_details.campaign_id as as',
		'campaign_name',
		'campaign_status'
	])
	->where('campaigns.user_id', $user_id);

return Datatables::of($campaigns)->make(true);

Thanks, will try it. Also noticed that there are two aggregate count
queries running instead of one for all types of queries.
On 20 Apr 2015 08:57, "Arjay Angeles"<EMAIL_ADDRESS>wrote:

Hi, haven't tried the package via HasMany and the likes but will surely
check this out on my free time.
In the meantime, the workaround you can do is by using a join statement
manually like below: Just adjust it according to your tables definition.
$campaigns = Campaigns::join('user_campaigns','user_campaigns.campaign_id','=','campaigns.id')    ->join('campaign_details','campaign_details.id','=','user_campaigns.details_id')    ->select([        'user_campaigns.user_id',        'campaign_details.campaign_id as as',        'campaign_name',        'campaign_status'    ])    ->where('campaigns.user_id', $user_id);return Datatables::of($campaigns)->make(true);
—
Reply to this email directly or view it on GitHub
https://github.com/yajra/laravel-datatables-oracle/issues/28#issuecomment-94347223
.

Yes, two count query is required. 1 for the total records and 1 for the total filtered records.

Should be fixed on v4.3.0. Kindly checkout and test. Thanks!

Yes works, thank you!


arch/: Trivial typos, mostly "their is" to "there is"

Summary
Trivial typos, mostly "their is" to "there is"
Impact
N/A
Testing
N/A

LGTM


Merge master into feature/monobehaviour-support-sharede

Contributions: We are not currently taking public contributions - see our contributions policy. However, we are accepting issues and we do want your feedback.

will be redone


Single user changes

Update env var names
Conditionally render the keycloak provider wrapper based on an env var.
Updated the PR to follow the forklift env var approach for supporting encrypted env vars in production loaded at runtime & loading development mode env vars at build time.
Pending operator changes: https://github.com/konveyor/tackle2-ui/issues/63

Depends upon https://github.com/konveyor/tackle2-operator/pull/43

Adds cookie handling for unauthenticated direct hub api requests. Fixes 401 errors for reports when auth turned on

@ibolton336, In the description don't you mean this PR depends upon https://github.com/konveyor/tackle2-operator/pull/45 instead ?

@ibolton336, In the description don't you mean this PR depends upon konveyor/tackle2-operator#45 instead ?

Yeah

@ibolton336, In the description don't you mean this PR depends upon konveyor/tackle2-operator#45 instead ?

Yeah - Although I think we decided to go ahead and merge the UI PR since it won't really break anything without the env var in place.

@gildub


Add Alibaba RRSA auth support

Added support of RRSA Alibaba authentication.
Changed to the client creation to use the new open API (new recommended GO SDK)
Created a REST API wrapper around the GO SDK, the GO SDK is currently broken for all KMS operations and there isn't an ETA for a fix
Fixes #1767

@maximrub i tried to create a test environment for RRSA to test this PR. Turns out that Aliyun KMS Secrets Manager has been deprecated/removed for new users. 1: launching a dedicated KMS is incredibly expensive ($1.8k per month) :exploding_head: and 2: the secret management functionality has been removed :exploding_head::exploding_head:.
I appreciate your work, but i'm not sure if it is worth it to put more effort into this due to it being deprecated and hard/impossible to test. WDYT? Are your running on Aliyun/KMS and need this feature?

Hi @maximrub! we discussed this PR in our latest community meeting, and we believe we will follow the same path as alibaba to deprecate this provider. Alibaba Cloud will be deprecated from 0.8.0, and removed in 1.0.0. It should still be possible to use it with a webhook provider under a API Wrapper, as long as that API wrapper is running available in your cluster.
Do you believe it still makes sense to add your contribution here?

Hi @moolen, @gusfcarvalho

Thanks @maximrub that's good to know :pray: I agree, then it makes no sense to deprecated it. I opened a support ticket for that service :+1:

Meh, support is not willing to give me access to it :disappointed:

@moolen what did you wrote them? they just enabled it for one of my accounts without a problem

I explained them the situation with the deprecation and asked if they can re-enable Secrets Manager it for me. They sad: it has been deprecated, please purchase a dedicated KMS for $1.8k🫠
They've also asked for a root account id :raised_eyebrow:  - so i guess if you've used it previously then you'll get it otherwise nope :disappointed:

I explained them the situation with the deprecation and asked if they can re-enable Secrets Manager it for me. They sad: it has been deprecated, please purchase a dedicated KMS for $1.8k🫠 They've also asked for a root account id 🤨 - so i guess if you've used it previously then you'll get it otherwise nope 😞

no, I think you fell on a support guy that doesn't know it's in the process of coming back and that they should whitelist it in the meanwhile

Hi @moolen I aligned the code with main and replied about the breaking change

@maximrub Sorry for ping, are you still working on this?

Hello @mozillazg
yes, I'll push the changes in a few days
thank you

@moolen @mozillazg the cr fixes are pushed

Hey @maximrub thanks for the update and sorry for the late reply. I wasn't able to get the infra going to do proper end to end tests, i'll need a couple of more days for the review.

Hey @maximrub thanks for the update and sorry for the late reply. I wasn't able to get the infra going to do proper end to end tests, i'll need a couple of more days for the review.

great, I just pushed a fix to the new lint errors validation (minor things as renaming vars and spaces)


Fix homepage

Patching is removed in EAP8.
It is replaced with Update Manager. Tracked by EAP7-1917
Local run
  TESTS: Homepage
    ✓ Should display About info (9373ms)
    ✓ Should load Deployments page
    ✓ Should load Configuration page
    ✓ Should load Runtime page
Stopping container for test test_homepage
    ✓ Should load Access Control page

  5 passing (14s)

[mochawesome] Report JSON saved to /home/mchoma/git-repo/berg/packages/testsuite/results/cypress/e2e/test-homepage_pass.json

  (Results)

  ┌────────────────────────────────────────────────────────────────────────────────────────────────┐
  │ Tests:        5                                                                                │
  │ Passing:      5                                                                                │
  │ Failing:      0                                                                                │
  │ Pending:      0                                                                                │
  │ Skipped:      0                                                                                │
  │ Screenshots:  0                                                                                │
  │ Video:        true                                                                             │
  │ Duration:     13 seconds                                                                       │
  │ Spec Ran:     test-homepage.cy.ts                                                              │
  └────────────────────────────────────────────────────────────────────────────────────────────────┘

====================================================================================================

  (Run Finished)

       Spec                                              Tests  Passing  Failing  Pending  Skipped
  ┌────────────────────────────────────────────────────────────────────────────────────────────────┐
  │ ✔  test-homepage.cy.ts                      00:13        5        5        -        -        - │
  └────────────────────────────────────────────────────────────────────────────────────────────────┘
    ✔  All specs passed!                        00:13        5        5        -        -        -

@mchoma This PR can be probably closed as the fix has been prepared in #30.

This PR can be probably closed as the fix has been prepared in #30.

When #30 will be merged I will close this. I am not sure when #30 is planned to be merged. This can go in immediately as it fix the test.


How to let the user cancel loading the model and stop it from fetching params

Hello quick question! I was wondering, after you create the engine (in the step below) and the cache starts getting populated, how do you code a cancel button for a user to cancel downloading the model/quit the task. Is there a method that can be called? In this example to stop the response llm.abort(); but I would like to understand what abort() is being called on and how can I get there from the simple implementation found below.
const engine = await CreateMLCEngine(
selectedModel,
{ initProgressCallback: initProgressCallback }, // engineConfig
);
Thank you!
@customautosys

May relate to this https://github.com/mlc-ai/web-llm/issues/484

#484 is talking about avoiding loading multiple models concurrently, but not about an API for cancelling like abort(). I will add this to our tracking list and have a look of whether we can provide this easily.

Thank you so much for looking into it! Do drop me a ping when an API like this has been created. Really appreciate the work you guys are doing <3


[Question] Is it working after (30/4/2019)

Is this cheat updated? working after the latest csgo update?

https://github.com/EternityX/DEADCELL-CSGO/tree/update
The  update branch is being updated currently, not entirely sure if it's working or not. Since it's open source, you could update it yourself. Everything needed to update is in unknowncheats.me

Update branch is not completely up-to-date yet.

Main branch should be fully updated now. Let me know if you have any issues.
eb23d7a80663961aeae7f1fe5d485df9c6187834


window is not defined. latest update breaks nuxt SSR

Hi. Thanks so much for the update . Awesome work. unfortunately it seems that it breaks the entire nuxt build due to "window is not defined" when doing the import
<script setup>
import { dragAndDrop } from "@formkit/drag-and-drop/vue";
import {
  parents,
  parentValues,
  dragValues,
  setParentValues,
  handleDragoverParent,
  handleEnd,
} from "@formkit/drag-and-drop";

at  (node_modules/@formkit/src/index.ts:47:28)
export const touchDevice = window && "ontouchstart" in window;
This breaks the build . please please please fix . This worked before the latest update
maybe something like this to fix it
if(typeof window !== 'undefined')

@agotfredsen82 hmmm, I dev'd in Nuxt ssr and never ran into this. I will take a look. Apologies!

Same on React, window is not defined

@agotfredsen82 @bfourgeaud This should be resolved at v0.2.1. Let me know if you're still having any issues.

I just tested out v0.2.1 and I still have this issue.
This is my code :
// draggable.tsx

import { ComponentProps, ReactNode, useEffect, useTransition } from "react"
import { useDragAndDrop } from "@formkit/drag-and-drop/react"
import {
  animations,
  handleEnd as coreHandleEnd,
  DragState,
  SynthDragState,
} from "@formkit/drag-and-drop"
import { cn } from "@/lib/utils"

type Props<T> = {
  onChange?: (data: T[]) => Promise<void> | void
  items: T[]
  children: (item: T) => ReactNode
  dragHandle?: string
  checkSame?: (curr: T[], changed: T[]) => boolean
} & Omit<ComponentProps<"div">, "children" | "onChange">

const compareArrays = <_, T>(a: T[], b: T[]) =>
  a.length === b.length && a.every((element, index) => element === b[index])

export const Draggable = <_, T>({
  onChange,
  items,
  children,
  dragHandle,
  checkSame = compareArrays,
  ...props
}: Props<T>) => {
  const [pending, startTransition] = useTransition()

  const onDragEnd = async (data: DragState<T> | SynthDragState<T>) => {
    const parent = data.currentParent.el
    const newData = data.currentParent.data.getValues(parent)
    const isSame = checkSame(items, newData)

    !isSame && startTransition(async () => await onChange?.(newData))
    coreHandleEnd(data)
  }

  const [parent, listItems, setValues, updateConfig] = useDragAndDrop<
    HTMLDivElement,
    T
  >(items, {
    dragHandle,
    plugins: [animations()],
    handleEnd: onDragEnd,
    longPress: true,
    longPressClass: "shadow-xl peer:opacity-50",
    draggingClass: "opacity-50 bg-muted border border-blue-500",
    dropZoneClass: "bg-muted border-dashed relative",
    //nativeDrag: true,
  })

  useEffect(() => {
    setValues(items)
  }, [items, setValues])

  return (
    <div
      ref={parent}
      className={cn(props.className, {
        "opacity-50 animate-pulse pointer-events-none": pending,
      })}
      tabIndex={-1}
      {...props}
    >
      {listItems.map(children)}
    </div>
  )
}

Hmmm, okay. I will take another look at this

@agotfredsen82 @bfourgeaud Are either of you able to create a reproduction of this? I'm having a tough time reproducing myself.

@bfourgeaud Awesome! Thank you for your patience with all of this. I'll close this now.


🐛  Pydantic bug

depends on https://github.com/caikit/caikit/pull/327
fixes #323
This adds enum and list support to the rest server, so that it can return data models with enums or lists!

Issue: In py38,
for field_type
typing_extensions.Annotated[caikit.interfaces.nlp.data_model.text_generation.GeneratedToken, 1]

I get:
get_origin(field_type)
<class 'caikit.interfaces.nlp.data_model.text_generation.GeneratedToken'>

ah thanks @prashantgupta24 , that is mildly gross but definitely required 👍


doesn't work when 'to' is a part of string to translate

You can use ""  or '' to work around this issue.
Since to is also the keyword for the destination language it may not be that easy to figure out if it's that or a word in the text.


V-model not empty after reset

I've seen the related issue but i doesn't appears to work  :
datepicker(placeholder="Select date", v-model="date_mod", language="fr", monday-first=true, v-on:selected='addFilter', clear-button=true)
date_mod doesn't change to an empty string or to null

try add v-on:cleared='date_mod=null'

Fixed in https://github.com/charliekassel/vuejs-datepicker/commit/3d0b3f3aaa0ccdd59ff7a3692e7a766b76f4cff8
Available from v0.7.8


Small changes.

Awesome, thanks so much. :smile:

Np. Let me know if there's anything else that needs clarification/simplification.


%referral and rwhois urls are not handled by getServer()

The whois server at rwhois.shawcable.net:4321 returns a referral response for ip <IP_ADDRESS> that looks like this:
%rwhois V-1.5:003fff:00 rs1so.cg.shawcable.net (by Network Solutions, Inc. V-<IP_ADDRESS>)
%referral rwhois://root.rwhois.net:4321/auth-area=.
%ok

There are a couple of issues here:

The %referral syntax isn't handled by getServer()

The server/port extraction code in getServer() assumes everything after the scheme is a server[:port], so we end up with port having the non-numeric url path attached.

PR fixing these issues to follow. Thanks!

Hello @gavincarr
Thanks for your works.

If you think this repository is helpful, please share it with friends, thanks.


Optimize usePrevious

Following this YT video: https://www.youtube.com/watch?v=B-Xb_8n5wRg the usePrevious hook probably should not use useRef but instead something closer to that implementation: https://github.com/uidotdev/usehooks/blob/90fbbb4cc085e74e50c36a62a5759a40c62bb98e/index.js#L1017-L1027
Other libraries discuss this too as you can see here: https://github.com/streamich/react-use/issues/2605

Thank you very much for pointing this out. This is an interesting question, and I quickly watched the video and it seems to be related to the concurrent mode of react18. I know about concurrent mode, but I am not very familiar with this mode.

It's late at night in my timezone right now, you can submit a PR or I'll change it tomorrow.

By the way, I also have an interesting example of concurrent mode here: https://reactarium.vercel.app/#eNrFVltv2zYU/iusitYKZsmqW2eBZgfrsgAtsO1h7Z6iPtASJbGhSIGkfKnh/75DUpSlZBv2ViEX8dz4ne8cHuoUNJjyWKtDkJ4CjhsSpBfRPGCYVx2ujFQfW6JySVsN8h1mnRHSphVSoxPKJcGa/CmERmdUStGgLABRrqNCNIucUcJ1FvyU8d7jfdt6s3gBC6vLeC640kiaMJtRzLAQeddAiLgi+p4R8/rL8WMRwiagzoIrhBX68Pn333rlFUQzmlgSXhAZrs1+i1sjDs7zAFZPcvaS/53yzMKOc6VmQ1In1ClyX5Yk13Pz+kkD/jlSGkv9WWKuqKaCe4Jmlp+ZzZsRjchBE8kxs16QPpAqOg6yFCXoDGbGiFGlCSdSpQjz48MXsHv4YkOUHc9t+IKqFuu8DiE6rFMIZBKxDuh8hU4ZR4iWqNfHRok2mw2aUQ6UG/pmvRX6L1ATVdyL0Q/ojQWLIE3CFPGBdC3FHt1LKWQ4+4s/crHnyCGYmbKAvfkz5BeXQt5jyCIs+RXa3KKSh1fGEMxGyapuayq0JWCWotBa7gQt+gSGcIanOI6H9RziGd4QkkR3kveuPdix2wgRZZAhAHJ40AvgDMA58M+QmVboGfoVawzxbXDX4Q/QE7Y1iLb0mTr6hgknxLrwQ1+FE5wuWI15wcgd/KtMiZyFj/xP0bxjxwf6wO9C5Tig9+hpGrm4vOfQf86mt7CZeTYAxUfTFnB4xsiHFvWtOWo9aFHjPUerxLxknBzs4SpIiTum0UAwHL+npNZi7ziFlwmlJYZWnMAMXVrrgu5QzrBSf8Ag2GRmEGTBrVOCettpLQCEWyIk+B2j+ePmNKmDe56c82mpBiOHLnxhwHpy3WMTHxb2OJhnAAOHSFQVIyZdaEk9gFw4lIPhycRGr1/7JK3RKAysPjGxvxMwtjgEgsn4fZXry+Kqz3u9gMpY6fNDPwnke8BMRxgqUPWWSBgeDeY5iUESOlr3NQXqwmdKFFm3NVomyTD2FgtUCJDrmvJqGE6uzWyDu+aaHvBxe63rt7d3flKerIsfkef1ApQmKX8VwSXy5CoykslV5AT+DkrtDWmxltALUYkbyo4psmcNTsARRlYTdXSO3u8IpyD6QNiOaJpjEEmKGRhBn0aKSFpa3NGebB8phDLxVAPxTerm0tBgTrEihbNrxLdIqMMzw0rio8oxc3PBaveEVrVO0bsksUJGOYnqXvgmXllhLpgAjmS1DZerFfK/C3Tz4ytHqYYRFrmL3O4kWk0b+o0wUtEtZVQfL2YK5BEuvnbKbJEkry5o1JHrmigKVyeHzvFd9fLCZYMP0Z4WugbX5U3SHqxzi4vC7ruECWUlDZYVhesmQbjT4rI58FSBOIeuJNLH34rieJl6DEOZSkZc6IZyv+Hbpd/PCAeSkmRXT/d0mBjOSUShypDNsN9A5svEMm73jwssH/2YdNqyNDW3WsBnZ4czGFJN4mvSQImWfcaTLqO8hkroEbNAOmAd2/rSr/rS551UZu9W0AHsVkgoKTi2B6QEowXSZni2GGrtojuLSOKCdpDoTc+QNbMzNvUmNjWAvVypgXibWFqLHXyW2PTGtkDD9bvr/MJEb17Cl6aaT5fRjiq6helho4hOm0aGtgbcpgFGZ8cYmyZ1e/gz7j4Powa38Vcl+OisP9VMznwv8Yfebp71LioLYK64YdV/aRtJFtRatypdLIhqYlUvrObnNzfxMk6yAPIaOUw+zf/N1xgN/v0khJ/gfP4byaoOZw==

https://reactarium.vercel.app/#eNqVVtuO2zYQ/RVCQWAZtS52481C9RpNgwAJ0PShF/ShCgpaGknMUqRAUl47rv+9Q1KS7Q1aIA+7os6cuc9QPgUtZSI2+hBkp0DQFoLsAi0CTkXd09qi5tiBLhTrDOJ7ynsLsraTypATUSBKUORMKiVbkgcKaGGiUrZ58EMuBtqbrhvlcYIvTpaLQgptiJLSkAcSlrLoWxAmrsG842CPPx0/lCHaREYezAnV5P3vH38ehHO04b2HG+sg2S4s0cLBeREg9Cy9EfmG7HoNvxlqYGFPv0Llnu+qCgozpjxzGc+mXGcuw7jQGrFcVL0oDJPC1iCck1MuCPF5/1XIXpgF0WDe2tMnLMLoL0znF2KnYM9kr70co9iIvt1h0f8houd8G9r/Nu3J8t8LUklVwB9dicauDQ+q2zBaWg2rM2UUYnwPWx+iNyU5xFzW4cyFOlsgiE8XGpnCioteYR9sD53YBXJeDPl9Qvb/eLkKM/xITRMrKnB4wrlz8pWVm6DGADCu8eholqjA9EqQ0HvZbP0TT81y+x44l+RPqXi5SfB9kpVsTwpOtf4FB+ZhVlBVziYpyne9MdhJKd5yVjw+nHwmY//C0FfHYu5EviPL+Xnrz0yTkzudN4m3c225205NtsTnpUWd7hJmgnEOb5vEHTDts80bDm4ES6hoz93aXXYBB/LZLljkZhc8MC5B5hbT9amSwkQVbRk/ZuSDMKBwbI/aQBv1bEHe7EEwhLCwezCsoAgpRjmSqNCRBsUqNxXRE+weGZqy9nSL9hsm6oxQYZDOqIbS81r5JZL68BWxVvSoC8rB0Zz0CVjdmIy8SlMHciYgagZwGa+HveBSZUTVu3C1XpPxLyH3r1/6zTFwMJG/Tpwn2RnWsi/AoWY7xpk5Xmga8YiWn3ttXaTpy0s0+ihMA5rpjAgpbJiuMS8utWzpIXpipWlQdXWfdgen3NGydH5XClqHtFTVTGQkJbQ38uIc61QjXOBYgBrt72R59OZLpjtOsU0VB2+6ZWJ0+P1q9GfBqUhpum9uffqYOC0gYthlzGbyNxXzReoq7vzHJVWP4+XmpVVle+6kGJ/fHEeYUk3jO2ixRash45spY6LBTvjLxFcWi46xXnPH1q+H1uO2aOu7k2wKdicVthQVuwPBq4OVxOAVoztq9+qKESlash4TvR8q5GjMXt3ZSHGpYdirtZ4K7xLLGrnH+9ild83FMty9uisulRjoFX7q9OL2NdozzXYcvBXZGzvIONYYtx2Aq92xZDuk3oc1bXfcf36ilnbxZy3F1a4/l9zs/ICMS++c54OKzoNsvKiHL7tF8qAxptNZkoBuY90kTvLj8nWMpckDzOtKwf8U+C8lK50U3Y3vChWcz/8CMW7oyw== No. I was mistaken, it has nothing to do with concurrent mode and behaves the same in react 17.

Interesting

So the traditional usePrevious hook worked because while useRef was updated, React didn't re-render - it just appeared to work correctly since the ref update wasn't triggering a new render cycle. I found this implementation quite elegant too. It demonstrates that you can achieve the same result without setState by using useRef<EMAIL_ADDRESS>
While this looks nice I think it violates the rule outlined in the pitfall section too:

https://react.dev/reference/react/useRef

btw. alibaba has the same discussion 😂: https://github.com/alibaba/hooks/issues/2162

You're right. I'll migrate to a pattern that doesn't rely on refs👍👍👍.

It's allowed to write ref.current conditionally: https://react.dev/reference/react/useRef#avoiding-recreating-the-ref-contents

Yes. This is typically performancfe improve method. Often used with Intersetion Observer initialization or other thing

I'm thinking about the implementation of useLatest - it writes to the ref during render. However, it seems difficult to simply migrate this operation to useEffect instead?: https://stackoverflow.com/questions/68512910/concurrent-safe-version-of-uselatest-in-react

https://github.com/facebook/react/issues/16956#issuecomment-536636418 also a good case. I decide to migrate to useLayoutEffect.

So how would your other solution look like?

just wrap with   useIsomorphicLayoutEffect。
export const useLatest: UseLatest = <T>(value: T): MutableRefObject<T> => {
  const ref = useRef(value)
  useIsomorphicLayoutEffect(() => {
    ref.current = value
  }, [value])
  return ref
}

https://github.com/facebook/react/issues/16956#issuecomment-543068780 As long as you don't pass the value to child components and use it in the child component's useLayoutEffect, there won't be any issues. I believe the chances of encountering this scenario are quite rare, and it's more acceptable compared to potential concurrent mode issues.


Add caching method for Eloquent models.

This method provides a convenient and clean way to cache model collections to prevent n + 1 querying.
Example:
$products = getThirdPartyData();

for ($i = 0; $i < count($products); $i++) {
    $categoryId = Category::cache()
                          ->where('name', $products[$i]['category'])
                          ->first()
                          ->id;

    Product::create([
        'name' => $products[$i]['name'],
        'category_id' => $categoryId
    ]);
}

Some more examples
// This loop will call query only once.
for ($i = 0; $i < 100; $i++) {
    $categories = Category::cache();
}

// This will reset the cache because the columns have changed.
$categories = Category::cache(['name', 'description']);

// This will NOT reset the cache because the columns are the same as the previous one.
$categories = Category::cache(['name', 'description']);

// This will reset the cache.
$categories = Category::cache(['name', 'description'], $reset = true);

// This will reset the cache because the columns have changed.
$categories = Category::cache(['email', 'description', 'data']);

This PR currently involves 250+ commits and 132 files changes... This sounds like an unintentional merge somewhere. Could someone confirm that this is actually the correct amount of changes?

No plans to add this to the core at this time.


AMBARI-23909. Cannot install PERF stack on centos7

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/2386/
Test PASSed.


Update docker_registry2

Fixes specs that break after 1.15
Bump to 1.17 to allow pagination on registry.access.redhat.com based images

Could you provide a little bit of context on the update, it looks like the minor update contained some breaking changes? Thanks!

Yes.
Prior art in PR #7289
I added a fix to docker_registry2 which will come with the next tag. The tag is not yet created, hence I started updating to the current latest tag to adjust to the changes in docker_registry2, so pulling in the next update is hopefully a quick thing.

Tag 1.17 has been pushed in the meantime, so I added updating to 1.17 in this PR.

Not sure the docker smoke test is related, can you have a look @jurre?

@NautiluX yeah that does look related, seems like dockerhub is requiring us to auth for these requests now? Let me re-run them to make sure it wasn't just a hiccup

right so these requests:
  proxy | 2023/07/18 14:58:43 [016] GET [https://registry.hub.docker.com:443/v2/library/ubuntu/manifests/latest](https://registry.hub.docker.com/v2/library/ubuntu/manifests/latest)
  proxy | 2023/07/18 14:58:44 [016] 401 [https://registry.hub.docker.com:443/v2/library/ubuntu/manifests/latest](https://registry.hub.docker.com/v2/library/ubuntu/manifests/latest)

used to be HEAD requests before 1.15, that could explain the difference.
There are some authorized requests to /list, probably we can do the same with GET.

I tried reproducing the behaviour with a minimal example, doing the same calls that dependabot would do:
require "docker_registry2"

client = DockerRegistry2.connect(
            "https://registry.hub.docker.com:443",
            user: nil,
            password: nil,
            read_timeout: 10,
            http_options: { proxy: "https://localhost:8080",verify_ssl: false }

          )
client.tags("library/ubuntu", auto_paginate: true).fetch("tags").each do |t|
    print t
end
print client.digest("library/ubuntu", "latest")

Interjected the requests with a proxy and got similar requests than the smoketest:
[13:32:03.281] HTTP(S) proxy listening at *:8080.
<IP_ADDRESS>:51575: GET https://registry.hub.docker.com/v2/library/ubuntu/tags/list
 << 401 Unauthorized 157b
<IP_ADDRESS>:51577: GET https://auth.docker.io/token?service=registry.docker.io&scope=repository%3Alibrary%2Fubuntu%3Apull&account
<IP_ADDRESS>:51579: GET https://registry.hub.docker.com/v2/library/ubuntu/tags/list
 << 200 OK 9.6k
<IP_ADDRESS>:51581: GET https://registry.hub.docker.com/v2/library/ubuntu/manifests/latest
 << 401 Unauthorized 157b
<IP_ADDRESS>:51583: GET https://auth.docker.io/token?service=registry.docker.io&scope=repository%3Alibrary%2Fubuntu%3Apull&account
 << 200 OK 4.3k
<IP_ADDRESS>:51585: GET https://registry.hub.docker.com/v2/library/ubuntu/manifests/latest
 << 200 OK 1.1k

However, the second GET got a 200 as response, not a 401 as in the smoketest.

managed to get the test running locally, it's succeeding as well. Not sure what's still different to the environment where they run in the GitHub action.
  proxy | 2023/07/19 13:46:41 [010] GET https://registry.hub.docker.com:443/v2/library/ubuntu/tags/list
  proxy | 2023/07/19 13:46:41 [010] 401 https://registry.hub.docker.com:443/v2/library/ubuntu/tags/list
  proxy | 2023/07/19 13:46:41 [012] GET https://auth.docker.io:443/token?service=registry.docker.io&scope=repository%3Alibrary%2Fubuntu%3Apull&account
  proxy | 2023/07/19 13:46:41 [012] 200 https://auth.docker.io:443/token?service=registry.docker.io&scope=repository%3Alibrary%2Fubuntu%3Apull&account
  proxy | 2023/07/19 13:46:41 [014] GET https://registry.hub.docker.com:443/v2/library/ubuntu/tags/list
  proxy | 2023/07/19 13:46:42 [014] 200 https://registry.hub.docker.com:443/v2/library/ubuntu/tags/list
  proxy | 2023/07/19 13:46:42 [016] GET https://registry.hub.docker.com:443/v2/library/ubuntu/manifests/latest
  proxy | 2023/07/19 13:46:42 [016] 401 https://registry.hub.docker.com:443/v2/library/ubuntu/manifests/latest
  proxy | 2023/07/19 13:46:42 [018] GET https://auth.docker.io:443/token?service=registry.docker.io&scope=repository%3Alibrary%2Fubuntu%3Apull&account
  proxy | 2023/07/19 13:46:42 [018] 200 https://auth.docker.io:443/token?service=registry.docker.io&scope=repository%3Alibrary%2Fubuntu%3Apull&account
  proxy | 2023/07/19 13:46:42 [020] GET https://registry.hub.docker.com:443/v2/library/ubuntu/manifests/latest
  proxy | 2023/07/19 13:46:42 [020] 200 https://registry.hub.docker.com:443/v2/library/ubuntu/manifests/latest
  proxy | 2023/07/19 13:46:42 [022] GET https://registry.hub.docker.com:443/v2/library/ubuntu/manifests/23.10
  proxy | 2023/07/19 13:46:42 [022] 401 https://registry.hub.docker.com:443/v2/library/ubuntu/manifests/23.10
  proxy | 2023/07/19 13:46:42 [024] GET https://auth.docker.io:443/token?service=registry.docker.io&scope=repository%3Alibrary%2Fubuntu%3Apull&account
  proxy | 2023/07/19 13:46:42 [024] 200 https://auth.docker.io:443/token?service=registry.docker.io&scope=repository%3Alibrary%2Fubuntu%3Apull&account
  proxy | 2023/07/19 13:46:42 [026] GET https://registry.hub.docker.com:443/v2/library/ubuntu/manifests/23.10
  proxy | 2023/07/19 13:46:42 [026] 200 https://registry.hub.docker.com:443/v2/library/ubuntu/manifests/23.10
  proxy | 2023/07/19 13:46:42 [028] GET https://registry.hub.docker.com:443/v2/library/ubuntu/manifests/23.04
  proxy | 2023/07/19 13:46:42 [028] 401 https://registry.hub.docker.com:443/v2/library/ubuntu/manifests/23.04
  proxy | 2023/07/19 13:46:42 [030] GET https://auth.docker.io:443/token?service=registry.docker.io&scope=repository%3Alibrary%2Fubuntu%3Apull&account
  proxy | 2023/07/19 13:46:42 [030] 200 https://auth.docker.io:443/token?service=registry.docker.io&scope=repository%3Alibrary%2Fubuntu%3Apull&account
  proxy | 2023/07/19 13:46:42 [032] GET https://registry.hub.docker.com:443/v2/library/ubuntu/manifests/23.04
  proxy | 2023/07/19 13:46:42 [032] 200 https://registry.hub.docker.com:443/v2/library/ubuntu/manifests/23.04
  proxy | 2023/07/19 13:46:42 [034] GET https://registry.hub.docker.com:443/v2/library/ubuntu/manifests/22.10
  proxy | 2023/07/19 13:46:42 [034] 401 https://registry.hub.docker.com:443/v2/library/ubuntu/manifests/22.10
  proxy | 2023/07/19 13:46:43 [036] GET https://auth.docker.io:443/token?service=registry.docker.io&scope=repository%3Alibrary%2Fubuntu%3Apull&account
  proxy | 2023/07/19 13:46:43 [036] 200 https://auth.docker.io:443/token?service=registry.docker.io&scope=repository%3Alibrary%2Fubuntu%3Apull&account
  proxy | 2023/07/19 13:46:43 [038] GET https://registry.hub.docker.com:443/v2/library/ubuntu/manifests/22.10
  proxy | 2023/07/19 13:46:43 [038] 200 https://registry.hub.docker.com:443/v2/library/ubuntu/manifests/22.10
  proxy | 2023/07/19 13:46:43 [040] GET https://registry.hub.docker.com:443/v2/library/ubuntu/manifests/22.04
  proxy | 2023/07/19 13:46:43 [040] 401 https://registry.hub.docker.com:443/v2/library/ubuntu/manifests/22.04
  proxy | 2023/07/19 13:46:43 [042] GET https://auth.docker.io:443/token?service=registry.docker.io&scope=repository%3Alibrary%2Fubuntu%3Apull&account
  proxy | 2023/07/19 13:46:43 [042] 200 https://auth.docker.io:443/token?service=registry.docker.io&scope=repository%3Alibrary%2Fubuntu%3Apull&account
  proxy | 2023/07/19 13:46:43 [044] GET https://registry.hub.docker.com:443/v2/library/ubuntu/manifests/22.04
  proxy | 2023/07/19 13:46:43 [044] 200 https://registry.hub.docker.com:443/v2/library/ubuntu/manifests/22.04

@jurre I think I found the problem. When I download the cache and run against it, the test run fails for me locally as well. Looking at the test output in the github action, it says:
proxy | 2023/07/18 14:58:44 7/9 calls cached (77%)

My understanding is, for some reason, it uses cached HTTP responses for the GET calls and in the cache there is the 401 response.
Any idea how to fix that? Is there a way to disable or clear that cache?

@jurre I verified the docker e2e test works without cache locally, so the PR should be ready to get merged from my perspective. I had to update the digest querying so it behaves as it did with docker_registry2 <1.15.

Thanks for this fix @NautiluX 🙇 I'll try to get the change out in a bit

Unfortunately, it seems that with these changes we're now seeing a lot of rate limiting errors, I'm going to revert so we can dig into it more

Trying to reintroduce the old functionality in docker_registry2 lib: https://github.com/deitch/docker_registry2/pull/95

Commenting to add that depending on this new method goes against the spec. See https://github.com/deitch/docker_registry2/issues/98

If Rate-limiting is a concern, I think that we should do instead is to retry rather than to depend on this

I created https://github.com/dependabot/dependabot-core/issues/8010 to open this for discussion


Track gets stuck when the plugin skips the very start of a video

Whenever I play something with a music-offtopic segment at the very start of a music video, the track gets stuck, without it, the track doesn't get stuck and plays from the start

do you have an example track which breaks?
does it only happen for this type of segment or all if they are at the start

I did some testing and it seems more like a lavalink error, if the player seeks 30 seconds or more right after playing the song gets stuck, and a lot of music videos have intros that are more than 30 seconds long for example smack that by akon

interesting
I'll investigate within the next days

This was probably caused by yt seeking problems in lavaplayer
They recently have been resolved in 1.3.99 I believe.
If the issue still occurs feel free to reopen the issue.


scrollTo() does not work

Following code does fire the event, but always logs "0".
Latest Chrome browser, Windows 7.
`Hey,
$$('.page-content').on('scroll', function(e) {
        console.info($$('.page-content').scrollTop());
    });

PS: $$('.page-content').scrollTop(100) works fine!

When do you call this code?
Also, can you create a fiddle please so it's easier to debug? Thanks :-) http://www.jsfiddle.net

@scriptPilot this is because you may have more than one ".page-content" in the DOM. Make you selector more specific like $$('.page[data-page="some-page"] .page-content').on('scroll', ...

Thank you, that works fine!


Modality specific JSON files

For iEEG and EEG, the JSON file is not required (we tried using the latest validator). However, they seem to be required for motion capture. CC @dungscout96
Is that by design?

EEG has REQUIRED metadata, as does iEEG. So the absence of JSON sidecar files should be an error.

We tried removing _eeg.json and _ieeg.json from test datasets and the current validator (v.1.14.5) didn't complain about it.

Do you have an example dataset for reproducing?


Make json output to follow common pattern LEVEL: details

Please sign your commits following these rules:
https://github.com/moby/moby/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "patch-1.4-json-inconsistency" git@github.com:mckjamhed/docker-bench-security.git somewhere
$ cd somewhere
$ git commit --amend -s --no-edit
$ git push -f

Amending updates the existing PR. You DO NOT need to open a new one.

Hi and thanks @mckjamhed, could you please rebase this and I'll check and test this PR.

Closing due to merged #314


Add cpu count to rhs table

Also fix cpu percentage formatting to be more readable.

@brian-brazil @juliusv


panel Drag

is it possible panel drag within window ???

You need to "Unpin" panel from DOM and then you can drag anywhere you want.

i mean to say  CONSTRAIN TO WINDOW and CONSTRAIN TO PARENT element

I suggested something similar to this. But you need to modify the lobipanel.js
See >>> #12

This issue is fixed.
Added constrain property.


Update dependencies

Signed-off-by: David A. Wheeler<EMAIL_ADDRESS>

The mysterious bundler loading problem has returned!
/home/ubuntu/.rvm/gems/ruby-2.3.0@global/bin/bundle:22:in `load': cannot load such file --<EMAIL_ADDRESS>(LoadError)
	from /home/ubuntu/.rvm/gems/ruby-2.3.0@global/bin/bundle:22:in `<main>'
rake aborted!
Command failed with status (1): [      if ping -q -c 1 google.com > /dev/nu...]
/home/ubuntu/cii-best-practices-badge/lib/tasks/default.rake:68:in `block (2 levels) in <top (required)>'
/home/ubuntu/cii-best-practices-badge/lib/tasks/default.rake:67:in `block in <top (required)>'
Tasks: TOP => ci => bundle_audit
(See full trace by running task with --trace)

bundle exec rake ci returned exit code 1

Just a rebuild fixed it. For some reason, the ping test fails with status 1 sometimes. It makes me think that the bash if statement isn't working the way we expect, but I can't see what's wrong with it.
If it keeps recurring, we may want to disable bundle_audit from the ci task until we find a fix.
One alternative would be to move the test from bash to Ruby.

Odd. We could perhaps attempt to retry to see if the problem is temporary.


dts: gen_defines.py: Add helper for outputting {} initializers

The
"{" + ", ".join(...) + "}"

pattern is in a bunch of places now. Add an out_dev_init() helper for
it, with the same parameters as out_dev().
Also makes "{" vs. "{ " consistent, picking the first one.

Rebased out of https://github.com/zephyrproject-rtos/zephyr/pull/21393 and cleaned up a bit.


Add new codes list!

Merged in v1.3 beta, after some testing I will release a normal version. Thank you for the help!


failing test xt/examples-compilation.t doc/Type/Str.pod6

From
perl6 xt/examples-compilation.t doc/Type/Str.pod6

# $string.substr-rw(2, 0) = "-Zorro-"; # insert new characters BEFORE the character at index 2
# $string.say;                         # OUTPUT: «az-Zorro-c␤»
# Variable '$string' is not declared. Did you mean 'Stringy'?
not ok 72 - doc/Type/Str.pod6 chunk 72 compiles

Added in 35e69981b2df84e1151ad2f4117bb27df6534ba2 by @tbrowder

This was fixed by 4c0eb45


PI-955: pass {} isntead of [] or empty string for empty JSON object i…

Another attempt at fixing #48

We used to not use the PSR logger.  We toggled $logger->debug() by whether config:debug === true.  However in PSR loggers you set it some other way.  I was commenting saying that passing an empty JSON object is purely to satisfy magentos class generation logic.


[Project] Update project.json content to msbuild projects

This is a meta-issue for the Update from project.json based projects to csproj based projects project.
Subtasks will be defined as this project is planned in full.
Comment below to suggest new content, or updates to existing content.

Project is close to being done.

I added the up-for-grabs label to this project. The work that remains is to migrate several small projects that were originally created using project.json style projects. The dotnet migrate command will likely work on all of them.  See the 'Notes' column in the linked project for more information.


Add 'buy me a coffee' link to Readme

Recently I've created an account for 'buying me a coffee' to sponsor this project. There are nice badges for this, Readme should be updated ...

added a 'sponsor' section in the Readme.


How reference views path?

Hi.
How reference views path in route?
If my view is named "bar" and is in Modules/Foo/Views, the code doesn't works
Route::get('example', function () {
return view('foo.bar');
});

You have to use the double colon notation.
Did you use the generator? If so, in the Controller is a working example. If not, try php artisan make:module foo.
For reference
return view("Foo::bar");


Support non Windows OSes in MediaInfo.Native nuget package

I have added support for .Net Standard 1.3 to MediaInfo.DotNetWrapper. The current implementation requires end users to install mediainfo lib manually as MediaInfo.Native is windows only.
Any chance you guys can update the nuget package to support unix and macos RIDs?
Happy to help where I can.

We don't provide (yet) a nuget package if I remember correctly. About which nuget package do you speak?
We would be happy to get help (Pull Request?) for an official (we would "push" it from an official MediaArea/MediaInfo account) nuget package compatible with any platform (we have 0 knowledge about nuget currently :( ).

Thank you for the prompt response.
I just followed the project site link in nuget. I'll contact the nuget author instead.

Would be nice to have an official package.
Let me try work with the current nuget author and see if I can create a PR against the official repo.

It would be my honor.

Great!
Do you have your MediaInfo.Native nuget project in github? We can use that as a starting point. I started with @StefH MediaInfo.DotNetWrapper project because it used the latest VS 2017 project files. I think @StefH fork was to support .Net 3.5.
Goals:

Cross platform support for MediaInfo.Native. Users dont have to manually install mediainfolib
Target .Net 3.5
Target .Net 4
Target .Net Standard >= 1.3
Refactor code

Thoughts?

@JeromeMartinez
We'll need 6+ nuget packages to support a cross platform runtime. If the linux binaries are compatible with all distros (very unlikely), we can get away with one nuget package for linux. Otherwise we would need multiple Linux compilations.

MediaInfo - C# wrapper - references runtime.native.MediaInfo
runtime.native.MediaInfo - references below nuget packages
runtime.native.MediaInfo-windows-x64 - built using windows x64 (docker on windows?)
runtime.native.MediaInfo-windows-x86 - built using windows x86 (docker on windows?)
runtime.native.MediaInfo-linuxrid - built on linux distro using docker
runtime.native.MediaInfo-macos - built on MacOS

For new releases you would have to rebuild on every platform. Linux and windows can easily be automated using docker. MacOS can be automated using MacInCloud or a similar service.
Is this something you are willing to take on per new release?

All necessary files in my fork MediaInfoLib repository in SSL_WithoutCheck branch. One NUGET package may include various libraries for several OS: Linux (x86, x64), MacOS, Windows (x86, x64), Android, iOS
I have also C# wrapper MP-MediaInfo

If the linux binaries are compatible with all distros (very unlikely)

We build AppImage version of the Linux binaries, in addition to using the "standard" method for each distro; not sure that the binary in it is "compatible with all distros", but it may be not so far. If you know how to improve our deliveries about that, or if you need a specific build, let me know.
That said, as Linux distros have their own package manager, I would suggest to let Linux nuget version using the installed libmediainfo, and/or giving the choice. Only a suggestion, I don't know enough nuget and user habits, I would rely on your hints.

For new releases you would have to rebuild on every platform.

We have our build system for release, my wish is to be use it when we do our automated release, so the nuget is updated at the same time as other deliveries, and you don't have to manage anymore releases.
Our build system already have Linux, Windows and Mac.
On GitHub we have Windows/Linux/Mac tests, having unit tests would be great so we are sure we break nothing when we update MediaInfo library.

Is this something you are willing to take on per new release?

I wish to deliver in an automated manner (or the most automated) the nuget packages when we deliver the new version, and the release manager does the manual actions needed when we announce the release.
Note that it means that we would "control" the nuget account (we wish to sign DLL with our certificate), obviously without hiding your name (this is not the goal, we want to give credit to anyone working on MediaInfo e.g. see license text, it is "owned" by MediaArea but names of code contributors are on the same page), instead of your own account, is it something acceptable for you? (I just created a MediaArea nuget account).

linuxrid

Why "rid"?

I am completely noob about nuget, I guess I need to let you both discuss about the best approach for having something nuget users love.

All necessary files in my fork MediaInfoLib repository in SSL_WithoutCheck branch

I see some additional patches (e.g. not sure the "compilation fixes" patch is still useful), some files are completely changes (line return issue?), but it looks like it is not complex when it is known how to do it.
Some of the patchs (e.g. "RuntimeLibrary" changes) are done on our side during the build (we prefer to let the default value in our code source), I wish to keep that in a separate patch if possible.
Please don't take my talk as orders, it is only suggestions to be debated in order to have the best delivery while having everyone happy with the final result.
Wondering how we could proceed.
I suggest:

we agree on the expected result (what is delivered, where it is delivered include the account name for releases, who does updates, agreement on the license...)
there is PR for debating, maybe with an "how to". I am reluctant to peek commits from the GitHub as I don't understand (yet) nuget and what users expect from it.

Your help is appreicated, I hope we can find a method for being all happy with the final result.

One NUGET package may include various libraries for several OS: Linux (x86, x64), MacOS, Windows (x86, x64), Android, iOS

@yartat You are absolutely correct. I am modeling the nuget packages using the same method microsoft uses for dotnet standard packages. Here is a good example of the OpenSsl package. I am OK with having one or one per platform. Doing one will require outputs for all platforms to be copied to a central location to build one package. Whereas doing one per platform we can package and distribute for the platform using terminal / command line natively.

That said, as Linux distros have their own package manager, I would suggest to let Linux nuget version using the installed libmediainfo, and/or giving the choice. Only a suggestion, I don't know enough nuget and user habits, I would rely on your hints.

@JeromeMartinez the current implementation MediaInfo.DotNetWrapper can use either the official releases or the package manager releases for the ditribution. We recommend using HomeBrew for MacOS. Manually installing the mediainfolib eliminates the need for the nuget runtime package. The main advantage of distributing the runtime is users aren't concerned if mediainfolib is installed or if they have the correct version. It just works.
They would just type
dotnet add package MediaInfo

And voila.

We have our build system for release, my wish is to be use it when we do our automated release, so the nuget is updated at the same time as other deliveries, and you don't have to manage anymore releases.
Our build system already have Linux, Windows and Mac.
On GitHub we have Windows/Linux/Mac tests, having unit tests would be great so we are sure we break nothing when we update MediaInfo library.

That works. Just pointing out that it's a multi-step process to build per platform. We would need to add additional steps for the nuget packages.

Note that it means that we would "control" the nuget account (we wish to sign DLL with our certificate), obviously without hiding your name (this is not the goal, we want to give credit to anyone working on MediaInfo e.g. see license text, it is "owned" by MediaArea but names of code contributors are on the same page), instead of your own account, is it something acceptable for you? (I just created a MediaArea nuget account).

I am not concerned about IP ownership. I understand that MediaPath would own the source and welcome that. It is you who will have to maintain moving forward.

Why "rid"?

That's the runtime id in case we need different binaries for distros. (e.g. ubuntu-14.04, ubuntu-16.04, redhat-7)

Doing one will require outputs for all platforms to be copied to a central location to build one package.

If it is technically doable, we could develop that.
If there is no "best" solution, we could deliver both "all in one" or "one per platform" (a bit more development of the release process, but after that it is automated in our build process, snapshots included)

The main advantage of distributing the runtime is users aren't concerned if mediainfolib is installed or if they have the correct version. It just works.

got it.
Reminder: I have a complete noob about nuget, I don't use it myself. I just wish the best for my users, including the support of what they use (any platform, any distribution method), with minimal work during a release and up to date releases everywhere (e.g. the current nuget package is not up to date, it is not part of the release build, not a criticism it is normal). It would be great if we can find a method for automating that, if everyone agrees.
A "how to" would help, so we can well automate everything in our release system.
Eager to see the result of the discussion.

@JeromeMartinez
Do you mind giving me instructions or a build that statically links libzen, libtinyxml and any other dependecies libmediainfo would have for Ubuntu 16.04?

I see the results of this discussions lead to a dotnet core compatbible nuget package MediaInfo.Core.Native pointing to this project published by user @yartat in 2021 working alongside his C# wrapper that was working perfectly with .NET6. The project was put on hold for understandable reasons here.
Updating my project to .NET8 I get this warning:

warning NETSDK1206: Found version-specific or distribution-specific runtime identifier(s): centos.7-x64, centos.8-x64, debian.10-x64, debian.11-x64, debian.9-x64, fedora.32-x64, fedora.33-x64, fedora.34-x64, opensuse.15.1-x64, opensuse-x64, osx.10.15-x64, osx.11-x64, rhel.7-x64, rhel.8-x64, ubuntu.16.04-x64, ubuntu.18.04-x64, ubuntu.20.04-x64, ubuntu.21.04-x64. Affected libraries: MediaInfo.Core.Native. In .NET 8.0 and higher, assets for version-specific and distribution-specific runtime identifiers will not be found by default. See https://aka.ms/dotnet/rid-usage for details.

The Windows build seems to still work, but not when building a Linux Docker image. I see the Microsoft Docker image upgraded to Debian12 and the latest binary available in the package is Debian11. I tried to manually copy the libmediainfo.so file from the debian.11-x64 to the linux-x64 folder but of course it's not that simple.
The RID list seems to be specified when building the nuget package and not part of the code of this project directly. Does anyone know how the nuget package was build and if it's possible to update it with the newest OS support?


Includes more comparators: gt, ge, lt, le

@jeffsetter @rdaly525

@rdaly525 the printouts are now removed

@rdaly525 also why is float.abs a binary operation? I assumed it was short for absolute value.

@dillonhuff, you are correct. That is a mistake and should be a unary


Remove maxSizeBytes property from Synapse v3 database GET and PUT

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Removing property 'maxSizeBytes' from private preview API for Synapse gen3 databases.
Changelog
Please ensure to add changelog with this PR by answering the following questions.

What's the purpose of the update?

[ ] new service onboarding
[ ] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[X] Other, please clarify : maxSizeBytes property is not applicable to gen3 sqlDatabases within Synapse, as there are no size limits that customer can configure

When you are targeting to deploy new service/feature to public regions? Please provide date, or month to public if date is not available yet. May 2021
When you expect to publish swagger? Please provide date, or month to public if date is not available yet. May 2021
If it's an update to existing version,  please select SDKs of specific language and CLIs that require refresh after swagger is published.

[X] SDK of .NET (need service team to ensure code readiness)
[X] SDK of Python
[X] SDK of Java
[X] SDK of Js
[X] SDK of Go
[X] PowerShell
[X] CLI
[X] Terraform
[ ] No, no need to refresh for updates in this PR

Contribution checklist:

[x] I commit to follow the Breaking Change Policy of "no breaking changes"
[X] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[ ] Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.

Adding new API(s)
Adding a new API version
[ ] Ensure to copy the existing version into new directory structure for first commit (including refactoring) and then push new changes including version updates in separate commits. This is required to review the changes efficiently.
Adding a new service

[x] Please ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If there are following updates in the PR, ensure to request an approval from Breaking Change Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in stable version
[ ] Removing properties in stable version
[ ] Removing API version(s) in stable version
[ ] Updating API in stable or public preview version with Breaking Change Validation errors
[ ] Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

/azp run


Heavy Spam of Console Error 'CreatureSpawnEvent' Continues

Error reported previously.
The recommendation by the dev was followed and updated to current build/release
Upon downloading the newest release the error/issue persists. The previous request was closed as solved. Assuming this requires a new issue to be opened.
Details for error log:
At this time the error spams repeatedly and does not stop. Until we stopped the server and removed plugin again. The previous error repeated several times and stopped on its own.  This means some change made has caused a new issue in the recurrence of the error.
I am providing a section of our server log containing the error.
https://pastebin.com/XYksYhb6
No in-game messages or chat also no noticed lag in-game or tps drop.
My players on all 3 of our current server networks are excited to have this plugin however the error is currently preventing it. Please review and if additional information is needed to resolve, message me here or on discord EchocallingEarth#9331
My time zone is US Eastern Standard and I will do my best to respond as quickly as possible.
EchocallingEarth
(Owner Friendlyworldserve Network©)

Please recheck your version - you're using 2.0.11. The problem was fixed between 2.0.12 and 2.0.13.

Okay testing now.
Issued a new warning:
[19:46:47] [Server thread/WARN]: [DangerousCaves] Task #49 for DangerousCaves v2.0.12-9 generated an exception
java.lang.NoSuchMethodError: org.bukkit.entity.Player.getChunk()Lorg/bukkit/Chunk;
at com.github.evillootlye.caves.caverns.CavesAging.tick(CavesAging.java:100) ~[?:?]
at java.lang.Iterable.forEach(Unknown Source) ~[?:1.8.0_241]
at com.github.evillootlye.caves.ticks.Dynamics.tick(Dynamics.java:32) ~[?:?]
at com.github.evillootlye.caves.ticks.Dynamics.lambda$new$0(Dynamics.java:20) ~[?:?]
at org.bukkit.craftbukkit.v1_15_R1.scheduler.CraftTask.run(CraftTask.java:81) ~[spigot.jar:git-Spigot-8faa8b4-7f61a25]
at org.bukkit.craftbukkit.v1_15_R1.scheduler.CraftScheduler.mainThreadHeartbeat(CraftScheduler.java:394) [spigot.jar:git-Spigot-8faa8b4-7f61a25]
at net.minecraft.server.v1_15_R1.MinecraftServer.b(MinecraftServer.java:1036) [spigot.jar:git-Spigot-8faa8b4-7f61a25]
at net.minecraft.server.v1_15_R1.DedicatedServer.b(DedicatedServer.java:406) [spigot.jar:git-Spigot-8faa8b4-7f61a25]
at net.minecraft.server.v1_15_R1.MinecraftServer.a(MinecraftServer.java:984) [spigot.jar:git-Spigot-8faa8b4-7f61a25]
at net.minecraft.server.v1_15_R1.MinecraftServer.run(MinecraftServer.java:824) [spigot.jar:git-Spigot-8faa8b4-7f61a25]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_241]

Other than the above warning so far no other issues. And the warning may possibly be fixed in 2.0.13 However as I stated above I am not finding that release.  and will test again as soon as I have the link.

Latest builds are available in "Actions" tab - you can download archive(artifact) with plugin itself and a conifg.
I don't want to update SpigotMC resource page too frequently, that's why you can't find every update there.

Thanks, I grab that and update and test again before we consider the warning anything to be concerned with.

Okay so for whatever reason it keeps looping me and I have been unsuccessful in locating the .jar for 2.0.13. If you can send me a direct link I'd be very grateful. Thanks

It's better to download latest build.

Awesome and thanks. tested and no warnings or errors. That fixed it all. Recommend updating Spigit to this version 2.0.15 That way others do not report unnecessarily. As this version is running perfectly. Later today I will provide a great review.
Second thought if you are interested look into sharing your plugin on Songoda. Just an idea.
On that note, I am closing this request. If you ever need a willing player or owner to test the plugin or additions to it message me. Thanks again fr your attention to this and quick fix.

Thank you for the report and testing. I was going to update SpigotMC page after solving this issue, so, here I go.


PR automation: follow-ups

Some things we should do:

Bump the revision as well, so that auto-bumped formulae are automatically pushed to users who brew upgrade;
Issue PRs in alphabetical order, so that we have a rough idea of how much progress the automation has made;
Look into throttling the PR automation when triggered periodically to avoid spamming the homebrew-core maintainers.

Another follow up:

Don't send a PR if it doesn't actually fix a vulnerability. This happens when version constraints don't allow upgrading the vulnerable dep, but there are other packages to be updated (example: https://github.com/Homebrew/homebrew-core/pull/122902).

Yep. Similarly, we should include which vulnerabilities we're submitting the PR for in the PR message.

[ ] re-enable automation

we disabled this because PRs started getting screwed up: they duplicated resources instead of replacing them

Automation is now re-enabled

Don't send a PR if it doesn't actually fix a vulnerability. This happens when version constraints don't allow upgrading the vulnerable dep, but there are other packages to be updated (example: cyral-gimme-db-token: bump python resources homebrew-core#122902).

Looking into this one now.

Include the list of fixed vulnerabilities in the PR message.

#35 will include this, although not in its ideal form: it'll list each distribution URL known to be vulnerable, and each one that was successfully auto-updated.

Sniping myself into doing the revision bumping today.

#44 should be the last part of this.


opt merge SimplifyDecimalV3Comparison into SimplifyComparisonPredicate

What problem does this PR solve?
Issue Number: close #xxx
Related PR: #xxx
Problem Summary:
merge SimplifyDecimalV3Comparison into SimplifyComparisonPredicate
Release note
None
Check List (For Author)

Test

[ ] Regression test
[x] Unit Test
[ ] Manual test (add detailed scripts or steps below)
[ ] No need to test or manual test. Explain why:

[ ] This is a refactor/code format and no logic has been changed.
[ ] Previous test can cover this change.
[ ] No code files have been changed.
[ ] Other reason

Behavior changed:

[x] No.
[ ] Yes.

Does this need documentation?

[x] No.
[ ] Yes.

Check List (For Reviewer who merge this PR)

[ ] Confirm the release note
[ ] Confirm test cases
[ ] Confirm document
[ ] Add branch pick label

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR.
Please clearly describe your PR:

What problem was fixed (it's best to include specific error reporting information). How it was fixed.
Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
What features were added. Why was this function added?
Which code was refactored and why was this part of the code refactored?


data: VidipGhosh

Fixes Issue

Changes proposed

Check List (Check all the applicable boxes)

[ ] My code follows the code style of this project.
[ ] My change requires changes to the documentation.
[ ] I have updated the documentation accordingly.
[ ] All new and existing tests passed.
[ ] This PR does not contain plagiarized content.
[ ] The title of my pull request is a short description of the requested changes.

Screenshots

Note to reviewers

I've made the necessary changes. Please review.


Improve the dispatcher performance when using keep alive

In dozens of jobs situation, should enable keep-alive of the dispatcher. Because the dispatcher calls a lot of requests to the job's URL.
But Transport.MaxIdleConnsPerHost is zero. So it is used http.DefaultMaxIdleConnsPerHost.
As a result, the dispatcher has been consumed all local ports.
I added new flags for controlling an idle connection (a.k.a keep-alive).
dispatch_max_conns_per_host can control the http.DefaultTransport.MaxIdleConnsPerHost.
dispatch_idle_conn_timeout can control the http.DefaultTransport.IdleConnTimeout.
I think that these flags work well for controlling an idle connection.
other problem
I believe that each queue has to have individual Transport. Because Transport caches connections.
But it is not fixed by this PR. I'm sure it's outside the scope of this patch.

have you experienced performance improvement with keep-aliving the connections in your environment?

Yes.
Here is my benchmark script.
https://gist.github.com/f110/245e64e00156edce3ed759df273e6996
When pushed per second are more than 3,000, the dispatcher has been consumed all local ports.
If the dispatcher can not grab a local port, net.Dial uses many CPU times.
Therefore We like to reuse all connections from the dispatcher.

Thank you for review and merge!
And thank you for your patience.


Breast - Tier 2

Here is the discussion about the definition of the Tier 2 metadata for the breast bionetwork.
It has been decided that for the Breast Atlas v1 HCA will use the already published atlas (Reed et al. 2024) that already has some metadata that could be considered tier 2 (in terms of being biological metadata).
We have to map with existing dcp and tier 2 fields and see which we need to create. Before we proceed with action however, we have to discuss with them cause it is possible that they will add more metadata for tier 2.

Reed et al.
match

sample_id

donor_id

BCN_donor_id

sample_type

replicate

processing_date

dissociated_cells

dissociation_minutes

X10X_library_notes

surgery_type

brca_testing

brca_status

brca_notes

tissue_condition

risk_status

donor_age

parity

parity_notes

Approximate_age_at_each_last_pregnancy

Approximate_time_since_last_pregnancy.months.

Body_mass_index

Ethnicity

Smoking_status

Alcohol_consumption_levels

Age_at_first_menstruation

Menopause_status

oral_contraceptive_pill_usage

other_hormonal_contraceptive_usage

type_of_other_hormonal_contraceptive

Hormone_replacement_therapy_usage

other_hormonal_medication

type_of_other_hormonal_medication

Previous_breast_cancer_diagnosis

previous_BC_notes

Previous_other_cancer_diagnosis


Gnar won't read the token off the config file.

I'm attempting to self-host Gnar and I've hit this error. I've put the Bot's Token inside of the config file. When I compile the bot, everything is successful. When I run the bot, it exits out with an error saying that the token is empty.
Thanks for your help.

We don't provide any help with self-hosting.


Switch to --auto-correct-all

Please see https://github.com/misogi/vscode-ruby-rubocop/issues/123, https://github.com/misogi/vscode-ruby-rubocop/issues/101.

https://github.com/rubocop-hq/rubocop/blob/master/CHANGELOG.md#0870-2020-07-06

With newer version of rubocop (0.92) and fix about the json output (see https://github.com/misogi/vscode-ruby-rubocop/issues/129), I don't have any issue (all my files have a frozen_string_literal: true and auto correct is working).
Why must we run also unsafe corrections? I feel like auto correct unsafe corrections is, well, not safe, its more of an improvement.
Why is it a requirement?
Maybe we can try to add on option in the extension settings to toggle this behaviour?

@ngouy I agree it would be better to add an option for this. This PR fixes the behaviour to before the Rubocop change, but perhaps no longer necessary.

I don't have any issue (all my files have a frozen_string_literal: true and auto correct is working).

Strange, my understanding was this cop was unsafe in terms of autocorrect (https://github.com/rubocop-hq/rubocop/pull/8529).

Maybe I didn't quite understand the issue with the frize_string_litteral thing. Is the issue that you expect it to be autocorrected when you don't have it in your file? Or is the issue that when you have it the autocorrect doesn't works for other policies?

Is the issue that you expect it to be autocorrected when you don't have it in your file?

Yes. This was the behaviour I experienced before this regression (caused by new Rubocop release).

It's a real mess in issues, so much duplicates and sometimes many different bugs in a single one issue ^^' Hard to understand it all

Could you add an option (ex: safeAutoCorrect) that toggles --auto-correct or --auto-correct-all.
https://docs.rubocop.org/rubocop/usage/auto_correct.html


unable to install

Hello, Great work to all contributors. I tried installing this on my WIN10 laptop but got this error tried installing it on a VM running fedora 37 same problem. but works fine on google collabs
ERROR: Ignored the following versions that require a different python version: 0.55.2 Requires-Python <3.5 ERROR: Could not find a version that satisfies the requirement torchvision (from salesforce-lavis) (from versions: 0.1.6, 0.1.7, 0.1.8, 0.1.9, 0.2.0, 0.2.1, 0.2.2, 0.2.2.post2, 0.2.2.post3) ERROR: No matching distribution found for torchvision
saw on #13 and tried using the requirements.txt he provided but still doesn't work.
Tried both the pip install method and the git method none worked.
Do I have to revert to python <3.5  ?

Can you try updating your pytorch version before installing torchvision?


Connection string parsing for BigQuery Simba Drivers fails.

Driver: BigQuery Simba 4.2 Driver
Connection string:  CUSTOM CONNECT TO "provider=jdbc;driver=bigquery;host=https://www.googleapis.com/bigquery/v2;port=443;ProjectId=<GCloud Project>;OAuthType=0;OAuthServiceAcctEmail=<service account email>;OAuthPvtKeyPath=/secrets/bigquery.json;"
The big query driver does not follow the jdbc://host:port/database standard and it falls through the different parsing cases we have in the code.

WON'T DO: Repository archived


Upgrade PodDisruptionBudget version

Getting warnings in the logs:
W0921 11:26:08.102693       1 warnings.go:70] policy/v1beta1 PodDisruptionBudget is deprecated in v1.21+, unavailable in v1.25+; use policy/v1 PodDisruptionBudget

So we have time but will need to support the v1beta version for a period unfortunately. What k8s version was v1 of PDB introduced?

In 1.21. So we actually have to upgrade when we're closer to 1.25. Otherwise we'd have to drop 1.21 <= support


Update to support WebAPI

WebAPI was released in CRM 8.0 (CRM 2016).  Can CrmFetchKit be made to use this instead of the SOAP endpoint if it is available?

This would be a more natural fit for the related project CrmRestKit, which uses the 2011 REST OData endpoint, which has been deprecated. This library uses the 2011 SOAP endpoint, which is still a "first class citizen" in the CRM 365 API.
http://www.powerobjects.com/2016/03/28/the-new-crm-2016-web-api-is-here/


What's Hugging Face Token

I was ask a "Hugging Face Token" when started to train, who can tell me what's this and how to find it? Thanks

https://gigazine.net/news/20220824-stable-diffusion-google-colaboratory/#1


Property shape does not exist on type ZodType

Bug description
ts-to-zod v3.0.0 generates a Zod schema that fails type verification with this error:
2339: Property 'shape' does not exist on type 'ZodType<test, ZodTypeDef, test>'.

Looking into the ZodType (exported as ZodSchema) definition it in fact doesn't have any field called shape.
Input
The input file is generated by openapi-typescript v6.2.0 but I could reproduce the issue with a type definition as simple as this:
// typescript type or interface causing the output
export interface test {
  schemas: {
    A: string | null;
    B: test['schemas']['A'][];
  };
}

Expected output
Not exactly sure ...
Actual output
// Actual Zod schemas
// Generated by ts-to-zod
import { z } from 'zod';
import { test } from './test.d';

export const testSchema: z.ZodSchema<test> = z.lazy(() =>
  z.object({
    schemas: z.object({
      A: z.string().nullable(),
      B: z.array(testSchema.shape.schemas.shape.A),
    }),
  }),
);

Versions

Typescript: v4.9.5
Zod: v3.21.4

Hi, any update ?

Btw, this issue is not relevant to me anymore since we switched from openapi-typescript + ts-to-zod to openapi-zod-client.

We're still not supporting zod v3.21.4+?

@shwaka thanks for the great explanation! I'm facing the exact same problem. Your suggestions are sound to me, but I'm also new to this repo so I also don't any idea on how to solve this.

Thanks for you investigation @shwaka
I've had a quick look at how to implement solution 1 into ts-to-zod and, there are actually 2 use cases handle by the transformRecursiveSchema function:

self-referencing types (which is the case of your example;
complex circular references (A -> B -> C -> A).

The transformRecursiveSchema is applied "blindly" on the already generated Zod statements so it is quite straightforward. In the case of your proposed solution (which seems to be the good), we would need to:

either handle circular dependency earlier on to generate the z.lazy part as part of the "main generation" 👉 this would mean revamping the whole generation process (but is an option to have a cleaner one)
or re-parse the generated zod statement and replace every occurence of the reference to schemas by a z.lazy(...) call 👉 this would basically mean re-implement the whole node browsing logic already existing for on the TS side.


Set public addresses as constants

@kseniya292, @slgraham - We can close this now that we're passing in addresses to the constructor.

@dougiebuckets @kseniya292 what's the reason to pass the addresses into the constructor?
I'm concerned that would prevent others from reading those values from the contract.

@slgraham when we deploy to Kovan and Rinkbey, we need to use the contract addresses for the testnets. Setting them in the constructor allows us to dynamically pass in the contract addresses we need to use based on where it's being deployed.
We are setting the addresses for the interfaces which are all public, so you can access them:
UniswapFactoryInterface public uniswapFactory;
UniswapExchangeInterface public daiUniswapExchange;
UniswapExchangeInterface public ocDaiExchange;
CTokenInterface public cDai;
OTokenInterface public ocDai;
 IERC20 public dai;

You can test by adding a test:
it('gets addresses', async () => {
    const address = await savedaiInstance.uniswapFactory();
    console.log(address)
  });

address returns the mainnet uniswapFactory address when running the forked mainnet ganache blockchain

@slgraham Also, we will add them to the docs, similar to Opyn: https://opyn.gitbook.io/opyn/abis-smart-contract-addresses


fix a wrong attribute name in user-guide.md

modify bodyString to stringBody
I was very confused because of bodyString.
I could find stringBody instead of bodyString in io.finch.endpoint.Bodies.

Codecov Report

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

@@           Coverage Diff           @@
##           master     #817   +/-   ##
=======================================
  Coverage   79.54%   79.54%
=======================================
  Files          46       46
  Lines         699      699
  Branches       32       32
=======================================
  Hits          556      556
  Misses        143      143

Continue to review full report at Codecov.

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

Thanks @jinuk17! Nice catch!


Iroha slowed down

We executed Create Asset using iroha-Cli and created about 2.88 million assets.
Then, the memory usage sharply increased, the operation of iroha slowed down, making it impossible to continue operation.
At this time, the memory usage seen by ps aux and free was about 90%.
Restarting iroha daemon and Docker did not change the situation, memory was used when daemon was started up, and slow down was reproduced.
If 2.88 million assets are created, is it reasonable that the system will slow down with approximately 8 GB of memory used?

The size of the block store is about 2 GB. Even if this is all put in memory, it does not reach 8 GB, so I'd like to know quickly why 8 GB of memory is used and how to avoid using memory.

Looking at Valgrind's output, most seems to be a memory reference by google:protobuf.
It may be a problem of protobuf.
I'd like to check the version of protobuf, but I do not know how. How can I check the version?
It seems to be reproduced in many environments if the protobuf in Docker is due to the old, but has anyone recreated similar events?
valgrind_memcheck_02_has_0100_account_data.log


Test Fix due to removal of jwt-auth filter: mixer/test/client/istio_authn

After jwt-auth filter was removed, several mixer tests are failing.
Options

Remove tests. Mixer itself will be removed in a release.
Fix tests by using envoy.jwt_authn.v3 filter instead.  (I hope not)

FAIL	istio.io/istio/mixer/test/client/istio_authn_origin_jwt_bound_origin
FAIL	istio.io/istio/mixer/test/client/istio_authn_origin_jwt_bound_peer
FIAL istio.io/istio/mixer/test/client/istio_authn_peer_jwt_bound_origin
FAIL istio.io/istio/mixer/test/client/istio_authn_peer_jwt_bound_peer

looks like https://github.com/istio/istio/pull/25594 fixes the problem.


💡 [FEAT] - ADD ARIA-LABELS FOR SOCIAL MEDIA ANCHOR ELEMENTS

[x] I am from GSSoC'23.
[x] I would like to be assigned this task.

Section
Description

Concise Description
aria-label attribute is used by screen readers to know about the crawler link, in this case the social images wrapped with a must want aria-label  on footer of Homepage

Solution Proposed
We want to add aria-label for a which has social links with images in order to make it accessible to screen readers

Additional Context
The purpose of this technique is to provide aria-label for a can be read by assistive technology. It provides the text label for an object, such as a images inside it. When a screen reader encounters the object, the aria-label text is read so that the user will know what it is.

Code of Conduct
By submitting this issue, you agree to follow our Code of Conduct.

[x] I follow the Contributing Guidelines of this project.
[x] I have checked the current issues for duplicate problems.
[x] I have read the readme of this repository.

Hello @anmode, you can review the PR

Hey @anmode, the label gssoc2023 is not valid and acceptable by backend.
Please update it to gssoc23 ASAP, so that we can't ran into future problems


add video compression function

 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.guoshuangcheng 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.You have signed the CLA already but the status is still pending? Let us recheck it.

draft version for video compression, it run on vehicle, it will receive video frame from dragon, and put the frame to cyber channel.
notes: you need adjust the configuration according to vehicle camera connection and configuration

already amend the code, pls review it again, thanks a lot


Always pass index to value accessors (fixes #316)

Also tries to minimise accessor call counts. This made testing easier but I assume it can't hurt performance either.

Wow - unit tests :-)


fix(ui): fix generate button loading not visible

Description

What type of PR is this? (check all applicable)

[ ] 🍕 Feature
[x] 🐛 Bug Fix
[ ] 📝 Documentation Update
[x] 🎨 Style
[ ] 🧑💻 Code Refactor
[ ] 🔥 Performance Improvements
[ ] ✅ Test
[ ] 🤖 Build
[ ] 🔁 CI
[ ] 📦 Chore (Release)
[ ] ⏩ Revert

Mobile & Desktop Screenshots/Recordings

vercel preview just approved


Use correct point-at-infinity for proofs and commitments

PR Description
I noticed that KZGProof and KZGCommitment were using the wrong point-at-infinity bytes. It was 48 zero bytes and it should have been 0xc0 followed by 47 zero bytes. See the G1_POINT_AT_INFINITY constant here:
https://github.com/ethereum/consensus-specs/blob/dev/specs/deneb/polynomial-commitments.md#constants
I've made this mistake several times myself. It's the uncompressed bytes which are all zero; the compressed bytes include the "infinity" flag. This only appears to have been used in test code, so no worries.

Additionally, the two classes were providing this value differently.

I like the static variable style, so I switched the other one to that style.

I believe BlobSidecar#toLogString should print the abbreviated commitment.

I will revert this change if this was intentional.

I fixed a minor mistake in a comment.

It said MAX_BLOBS_PER_BLOCK when it should have said MAX_BLOB_COMMITMENTS_PER_BLOCK.

Documentation

[x] I thought about documentation and added the doc-change-required label to this PR if updates are required.

Changelog

[x] I thought about adding a changelog entry, and added one if I deemed necessary.

Is there a way to get a test for it?

Yes, I think so. I will work on that.

@jtraglia it would be good to have it in spec tests. We could be not alone

Good idea. I'll look into that. To back that up, mev-boost had the same issue:

https://github.com/flashbots/mev-boost/pull/630

I chatted with a coworker and we think it would be best to remove the infinity value from the two classes. It shouldn't be necessary in clients; it should only be needed internally in the KZG library. Would it be okay for me to remove these?

Merged, thank you @jtraglia


Finalize smart damper design.

As I user, I want to know exactly what is needed to implement a smart damper solution in my home because I need to know what to purchase and how to install it.
Tasks:

[ ] Develop comprehensive list of questions for client and send them for review.
[ ] Review answers from client and ensure the damper design aligns with their responses.  Adjust design accordingly.
[ ] Repeat above two steps until full design is complete and is functional per the client's system requirements.
[ ] Send material list to client for purchase.

awaiting more information on Kyle's HVAC; all other details prepared

The design is essentially done.  We've encountered issues getting the desired dampers, but the concept/design and general materials were reviewed/approved.


runtime: Add enumerate method on Array/ArraySlice

Just putting this out there. Maybe we want to do some bigger refactor of iterators later once we have traits.
Returns an iterator ArrayIteratorIndexed with a next function that
returns a Tuple of index, item

Rather than adding this to the C++ side, can we make this functionality part of the prelude instead? Since it seems like it could be written in jakt rather than requiring C++.
Adding more to the C++ side makes it harder to merge AK back from the original Serenity one and since it's a better fit in jakt, probably the better choice.

We can, just not sure exactly where it would go?
The current prelude is basically just a list of signatures for things that exist in the runtime?

pinging @alimpfard for ideas here. Seems like we might want the prelude to be a hybrid?

:thinking: we currently don't codegen for the prelude at all, and I'm pretty sure it wouldn't even generate something that can be compiled if we did...
But it does seem sensible to keep the C++ library requirements as small as possible, so...I guess fixing that and using a hybrid prelude would be nice

Yeah, I am guessing once we have traits we would end up with wanting something like this in the prelude in the enumerate case (using the syntax from the traits PR):
trait Enumerable {
    function enumerate(this) -> Enumerator
}

struct Enumerator<T> {
    index: usize
    iterator: ArrayIterator<T>

    function next(mut this) -> (usize, T)? {
        .index++

        let item: T? = .iterator.next()
        if item.has_value() {
            let ret: (usize, T) = (.index - 1, item!)
            return Some(ret)
        } else {
            return None
        }
    }
}

type Array {
    implements(Enumerable) function enumerate(this) -> Enumerator {
        return Enumerator(
            index: 0
            iterator: .iterator()
        )
    }
}

Will close this and revisit once we have support for traits on prelude classes.


Connection refused error

Describe the bug
I'm building the app, install via vue-electron-flask Setup 1.0.1.exe and run the app. Everything is fine. Then I copy vue-electron-flask Setup 1.0.1.exe to a different computer with the same setup (also running Windows 10). After installing and running the app I get a net::ERROR_CONNECTION_REFUSED:

Any idea what happens here?

@Szhiha I would try not using wsl2 for Electron. either go native Linux on windows.

Is this related to my question?