Proposal: Language classification should be configurable via plugin

Is your request related to a specific problem you're having?
Yes, auto-detect will guess very wildly when it only matches a small number of rules.
The solution you'd prefer / feature you'd like to see added...
IE, a relevancy score of less than 5 perhaps should not be considered at all, resulting in rendering as plaintext rather than essentially making a "wild guess" and rendering incorrectly/poorly.
Any alternative solutions you considered...
This threshold could be configurable, though I'm not convinced it needs to be.  This could also be implemented by making our "classifier" a plugin (and is likely a far more flexible solution).  IE, autoDetect would only do the "raw" scoring and then pass the results to a "classify" plugin that would make final determinations regarding winners, losers...  Currently the API only returns the highest match and second_best. So the classifier would (for compatibility) need to follow that API, although there would be nothing from stopping the classifier from adding extra meta-data that could be used by custom implementations.
The benefit of just supporting the existing API would be that highlightBlock() and initHighlightingOnLoad() would continue to "just work" with 0 required changes, other than registering your API.
Secondary benefits on a plugin based approach
Instead of just "don't highlight after wild guesses" (as a feature) it becomes very easy to "improve" the language detection GREATLY based on additional context you have available that the highlighter does not... IE, classification based on filename, StackOverflow post tags, lunar cycle, etc...
Additional context...
https://meta.stackexchange.com/questions/354793/improving-syntax-highlighting-language-auto-detection/355496#355496

This needs to be thought about carefully with regard to the existing hooks before:highlightBlock  and after:highlightBlock since it's probably already possible to build this on top of those, but it seems this should also be possible at the raw highlightAuto layer, if someone is running on the server outside of a browser environment.

Our default (or low-level) classifier should also finally resolve this long-standing "equal weight" issue between a base language and another language that includes it... IE that "xml", "handlebars", "php_template", etc. should not all score the same just because they are obviously HTML...  If there is no clear Handlebars or PHP code present then obviously XML (HTML) is the correct language to choose.
https://github.com/highlightjs/highlight.js/issues/2275

@allejo @egor-rogov  Added initial implementation thoughts to the top of issue.


Add home route

Add the home route that checks if the user has access to the route by checking if the tokens match.

Added code for home route, need to go back in and get it to work properly


lxd/apparmor/forkproxy: Fix running on i386

Signed-off-by: Stéphane Graber<EMAIL_ADDRESS>

This should fix i386 which will then let us confirm the other fix worked properly.

Testsuite passed


[Bug] Page load timeout / Error displaying this website

Reporting a bug?
When I create a new basic project and open it in the browser after yarn build & yarn serve, the page loads endless and crashes.
I tried in Docker and some other Versions too so I only want to know if someone has the same Problem?
Environment

  System:
    OS: macOS 11.2.1
    CPU: (8) x64 Intel(R) Core(TM) i5-1038NG7 CPU @ 2.00GHz
    Memory: 3.01 GB / 32.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 15.5.1 - /usr/local/bin/node
    Yarn: 1.22.10 - /usr/local/bin/yarn
    npm: 7.3.0 - /usr/local/bin/npm
  Browsers:
    Chrome: 88.0.4324.182
    Safari: 14.0.3
  npmPackages:
    react: ^16.14.0 => 16.14.0
    react-dom: ^16.14.0 => 16.14.0
    react-hot-loader: ^4.13.0 => 4.13.0
    react-static: ^7.5.0 => 7.5.1
    react-static-plugin-reach-router: ^7.5.0 => 7.5.1
    react-static-plugin-sitemap: ^7.5.0 => 7.5.1
    react-static-plugin-source-filesystem: ^7.5.0 => 7.5.1

Steps to Reproduce the problem
user@MacBook-Pro Projects % react-static create

? What should we name this project? my-static-site
? Select a template below... basic
Creating new react-static project...

Using React Static template: basic
Installing dependencies with: Yarn...
warning react-static > webpack-dev-server ><EMAIL_ADDRESS>Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
warning react-static > socket.io ><EMAIL_ADDRESS>Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
warning react-static > webpack-dev-server > chokidar ><EMAIL_ADDRESS>fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
warning react-static > socket.io > socket.io-parser ><EMAIL_ADDRESS>Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
warning react-static > socket.io > engine.io ><EMAIL_ADDRESS>Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
warning react-static > swimmer > babel-runtime ><EMAIL_ADDRESS>core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
warning react-static > webpack > watchpack > watchpack-chokidar2 ><EMAIL_ADDRESS>Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
warning react-static > webpack-dev-server > chokidar > braces > snapdragon > source-map-resolve ><EMAIL_ADDRESS>https://github.com/lydell/resolve-url#deprecated
warning react-static > webpack-dev-server > chokidar > braces > snapdragon > source-map-resolve ><EMAIL_ADDRESS>Please see https://github.com/lydell/urix#deprecated
warning<EMAIL_ADDRESS>babel-eslint is now @babel/eslint-parser. This package will no longer receive updates.
warning eslint-config-react-tools ><EMAIL_ADDRESS>babel-eslint is now @babel/eslint-parser. This package will no longer receive updates.
warning " ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>warning " ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>
[✓] Project "my-static-site" created (38s)

  To get started:

    cd "my-static-site"

    yarn start - Start the development server
    yarn build - Build for production
    yarn serve - Test a production build locally

user@MacBook-Pro my-static-site  % yarn build && yarn serve
yarn run v1.22.10
$ react-static build
Bundling application for Production...

Cleaning dist...
[✓] Dist cleaned
Cleaning artifacts...
[✓] Artifacts cleaned
Building Routes...
Importing routes from directory...
{ has404: true }
[✓] Routes Built (0.2s)
Building Templates...
[✓] Templates Built
Copying public directory...
[✓] Public directory copied
Bundling App...
[✓] App Bundled (10s)
Fetching Site Data...
[✓] Site Data Downloaded
Fetching Route Data...
[========================================================================================================] 104/104 100% 26000/s 0.0s
[✓] Route Data Downloaded
Exporting HTML across 8 threads...
[========================================================================================================] 104/104 100% 2000/s 0.0s
[✓] HTML Exported (4.3s)
Generating sitemap.xml...
[✓] sitemap.xml generated

Your app is now exported! Here's what we suggest doing next:

- Upload your 'dist' directory to your favorite static host! We recommend using Netlify:
  - npx netlify-cli deploy
- Analyze your app's webpack bundles
  - react-static bundle --analyze

✨  Done in 18.67s.
yarn run v1.22.10
$ serve dist -p 3000

   ┌───────────────────────────────────────────────┐
   │                                               │
   │   Serving!                                    │
   │                                               │
   │   - Local:            http://localhost:3000   │
   │   - On Your Network:  http://<IP_ADDRESS>:3000    │
   │                                               │
   │   Copied local address to clipboard!          │
   │                                               │
   └───────────────────────────────────────────────┘

Expected Behavior
Site load correctly

Thanks for reporting. It's the same issue as https://github.com/react-static/react-static/issues/1564

It was fixed and released!


use poolboy?

pool supervisor's init:
PoolArgs = [{name, {local, ?POOLNAME}}, {worker_module, mc_worker}] ++ SizeArgs,
PoolSpecs = [poolboy:child_spec(Name, PoolArgs, WorkerArgs)],
{ok, {{one_for_one, 10, 10}, PoolSpecs}}.

where size args are
[
    {size, 200},
    {max_overflow, 200}
],

and workers args are
[
    {host, "localhost"},
    {port, 27017},
    {database, <<"test">>},
    {login, <<"test_user">>},
    {password, <<"test">>},
    {w_mode, safe},
    {r_mode, slave_ok}
 ]

I think you apply poolboy in mongodb-erlang. you mean I apply poolboy in my app, right?  If disconnected  with mogodb server, how I reconnect?

No, mongodb is only the driver. How you want to pool it is your business.
I do not think mantaining pool in mongo is good idea, when there is special pool projects. It is better to give mongo users opportunity to select.
If connection to database is lost - mc_worker shoud exit with tcp_closed or other error (if got tcp error).
You can use your poolboy supervisor to restart them.

https://github.com/alexbank/mongodberl/tree/master/src

I think it is unnecessary. First - mongo dep is old, second - no poolboy dep, but you use it. And third - you create extra unneeded process mongodberl_worker. You could specify mc_worker to poolboy and create ordinary erlang module to call from poolboy with you requirements (like get_secret).
Though Erlang processes is light - try not to overuse it.

mongo dep is based your mongodb-erlang project. you mean I changes your mongodb-erlang source for my proj?

I mean, that I advice you to use comtihon/mongodb-erlang as it is supposed to be most up-to-date and if you have some changes - you are welcome for pool requests.
(and also put attention on two more advices).


[stable/influxdb] add ability to enable flux service

What this PR does / why we need it:
Just creates an option to enable the flux service
Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[X] DCO signed
[X] Chart Version bumped
[ ] Variables are documented in the README.md
[X] Title of the PR starts with chart name (e.g. [stable/chart])
@jackzampolin @aisuko

/ok-to-test

/assign

Thanks for your PR.


Making play-jongo compatible with Play framework 2.5.3+

Please don't remove stuff from gitignore which might be useful to others. The build.sbt version should also not be changed by a PR. The other changes for Play 2.5.x support should go into a single commit AFAICS.


Add skos:related links

Fixes #105

Deployed to test (with resolving a conflict from https://github.com/skohub-io/skohub-vocabs/pull/102).

I am losing overview over what's going on. It seems to me that we can close this PR as the changes are also part of #117 and it makes sense to review all of these together, right?

I am losing overview over what's going on. It seems to me that we can close this PR as the changes are also part of #117 and it makes sense to review all of these together, right?

Closing this one and will continue review at #117 .

Closing this one and will continue review at #117 .


Can not run New-AddAppGroup as no HostPoolName exists

Hi,
I have followed the previous documentation located here:  https://docs.microsoft.com/en-in/azure/virtual-desktop/create-host-pools-azure-marketplace
Made a note of my HostpoolName which is "CL-Hostpool"
But when trying to following the steps here: https://docs.microsoft.com/en-in/azure/virtual-desktop/manage-app-groups
And running "New-RdsAppGroup adamwilkinsonstreetsheaver CL-Hostpool TestAppGroup -ResourceType "RemoteApp"
This error is returned:
New-RdsAppGroup : HostPoolName: 'CL-Hostpool' does not exist. Please use powershell command: New-RdsHostPool
ActivityId: 4837ba0f-03a6-4547-8d3a-87c356e78abd
Powershell commands to diagnose the failure:
Get-RdsDiagnosticActivities -ActivityId 4837ba0f-03a6-4547-8d3a-87c356e78abd
At line:1 char:1

New-RdsAppGroup xxxxxxxx CL-Hostpool TestAppGroup - ...

  + CategoryInfo          : FromStdErr: (Microsoft.RDInf....NewRdsAppGroup:NewRdsAppGroup) [New-RdsAppGroup], RdsPowerShellException
  + FullyQualifiedErrorId : HostPoolNotFound,Microsoft.RDInfra.RDPowershell.AppGroup.NewRdsAppGroup

When i run :
Get-RdsHostPool -TenantName "xxxxx"
No hostpool is there, but it should have been created in step 3 when i completed the wizard. I have checked and the VM has been created..
Not sure why the hostpool is not getting created?
Thanks
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: c05d017a-8ce4-d3c2-333c-9f1decbc8e6c
Version Independent ID: 7f2287e0-71d2-05ef-335b-45bb4cd6cfe3
Content: Manage app groups for Windows Virtual Desktop Preview  - Azure
Content Source: articles/virtual-desktop/manage-app-groups.md
Service: virtual-desktop
GitHub Login: @Heidilohr
Microsoft Alias: helohr

@AdamWorkAccount Thanks for the comment! We will investigate on this issue and get back to you soon.

@AdamWorkAccount  I am not sure what could be the reason behing host pool not getting created.
Can you please try creating the host pool using PowerShell as described in this doc and share the results:
https://docs.microsoft.com/en-in/azure/virtual-desktop/create-host-pools-powershell

@Karishma-Tiwari-MSFT
Thanks for your help i ran the Powershell commands below but when trying to connect to the session desktop i am now getting this message:
Oops, we couldn't connect to "Session Desktop"
We couldn't connect to the gateway because of an error. If this keeps happening, ask your admin or tech support for help.
Have tried rebooting the VM but made no difference.
These are the commands i ran:
New-RdsHostPool -TenantName xxxxx -Name xxxHosstpool
New-RdsRegistrationInfo -TenantName xxxxxx -HostPoolName xxxHosstpool -ExpirationHours 1 | Select-Object -ExpandProperty Token > C:\temp\WVD\regtoken.txt
Add-RdsAppGroupUser -TenantName xxxxxx -HostPoolName xxHosstpool -AppGroupName "Desktop Application Group" -UserPrincipalName<EMAIL_ADDRESS>Any ideas please?

@AdamWorkAccount : Can you try running the troubleshooting steps here: https://docs.microsoft.com/azure/virtual-desktop/diagnostics-role-service ? Also, as described in the article, please run with the "-Detailed" parameter so that you can expand the Errors part of the object.

@ChristianMontoya
When running:
Get-RdsDiagnosticActivities -TenantName adamwilkinsnstreetsheaver -Detailed
I get
Get-RdsDiagnosticActivities : User is not authorized to query the management service.
ActivityId: ab34fa0d-1581-4fc5-88fe-68b20886526d
Powershell commands to diagnose the failure:
Get-RdsDiagnosticActivities -ActivityId ab34fa0d-1581-4fc5-88fe-68b20886526d
At line:1 char:1

Get-RdsDiagnosticActivities -TenantName adamwilkinsnstreetsheaver -De ...

  + CategoryInfo          : FromStdErr: (Microsoft.RDInf...osticActivities:GetRdsDiagnosticActivities) [Get-RdsDiagnosticActivities],
  RdsPowerShellException
  + FullyQualifiedErrorId : UnauthorizedAccess,Microsoft.RDInfra.RDPowershell.Diagnostics.GetRdsDiagnosticActivitie

The user is a global admin in Azure and a tenant creator in the enterprise apps for windows virtual desktops.
Powershell prompt is being run as admin

@AdamWorkAccount "User is not authorized to query the management service" indicates that your user doesn't have appropriate access to the tenant you provided. Otherwise, results should occur. Can you confirm you've run "Add-RdsAccount" and can run "Get-RdsTenant" which should result the tenant you want to have access to?

@AdamWorkAccount Any update? Please provide the details asked in the above comment, so that we can help you better.

@AdamWorkAccount Any update?

@AdamWorkAccount "User is not authorized to query the management service" indicates that your user doesn't have appropriate access to the tenant you provided. Otherwise, results should occur. Can you confirm you've run "Add-RdsAccount" and can run "Get-RdsTenant" which should result the tenant you want to have access to?

Yes i have 100% run those commands and the user i ran with is both a global admin and a TenantCreator
The result returned by  "Get-RdsTenant" is the tenant i have full access to

@AdamWorkAccount Any update?

Yes please see above.
Sorry for delay have been on leave.

@AdamWorkAccount : You mention that the host pool was not created. Are you able to create a host pool with this set of credentials (New-RdsHostPool)?

@AdamWorkAccount : You mention that the host pool was not created. Are you able to create a host pool with this set of credentials (New-RdsHostPool)?

Yes this host pool was created successfully but only after running the power shell commands manually and not via the wizard.  When i run Get-RdsHostPool the below is returned
TenantName        : adamwilkinsonstreetsheaver
TenantGroupName   : Default Tenant Group
HostPoolName      : AdamHosstpool
FriendlyName      :
Description       :
Persistent        : False
CustomRdpProperty :
MaxSessionLimit   : 999999
LoadBalancerType  : BreadthFirst
ValidationEnv     : False
Ring              :

@AdamWorkAccount : Can you continue down the manual path right now from this article: https://docs.microsoft.com/en-us/azure/virtual-desktop/create-host-pools-powershell .
However, if you would like to try again, the Azure Marketplace offfering is up and running: https://docs.microsoft.com/en-us/azure/virtual-desktop/create-host-pools-azure-marketplace .

@AdamWorkAccount Is there any update?

@AdamWorkAccount : Can you continue down the manual path right now from this article: https://docs.microsoft.com/en-us/azure/virtual-desktop/create-host-pools-powershell .
However, if you would like to try again, the Azure Marketplace offfering is up and running: https://docs.microsoft.com/en-us/azure/virtual-desktop/create-host-pools-azure-marketplace .

Already done both of these as stated above.

@AdamWorkAccount : Can you run the following
Get-RdsSessionHost -TenantName <tenantname> -HostPoolName <hostpoolname>
You should then try using the web client as an end-user: https://docs.microsoft.com/en-us/azure/virtual-desktop/connect-web . If you see resources and try connecting, but then get an error, we have the some troubleshooting articles to help narrow down the issue: https://docs.microsoft.com/en-us/azure/virtual-desktop/troubleshoot-set-up-overview .

@AdamWorkAccount Did that help?

@AdamWorkAccount We will now close this issue. If there are further questions regarding this matter, please tag me in a comment. I will reopen it and we will gladly continue the discussion.


Update SetupNNIDeveloperEnvironment.md

add a few details

please update this file based on https://github.com/Microsoft/nni/wiki/How-To-Contribute


Merge android code of v0.9.4

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.9 out of 10 committers have signed the CLA.:white_check_mark: YorkShen:white_check_mark: sospartan:white_check_mark: zshshr:white_check_mark: atomtong:white_check_mark: xkli:white_check_mark: misakuo:white_check_mark: gurisxie:white_check_mark: Rowandjj:white_check_mark: jinzhaoyu:x: chuyichuyi 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.


nvalid response body at: https://api.coinmarketcap.com//v1/ticker?limit=10 reason: incorrect header check

I found that using this wrapper in cordova generates this error:
nvalid response body at: https://api.coinmarketcap.com//v1/ticker?limit=10 reason: incorrect header check
I was able to fix it by adding:
compress: false
to this line:
  return fetch(${url}${query ? ?${qs.stringify(query)} : ''},{compress: false} ).then(...

fetch is now configurable via the constructor since v2.1.0


Make sure all of our tests are debug-able from a CI standpoint

@davidfowl recently mentioned that we should make sure that for all of the tests we have running in CI, we should make sure that enough assets and logs are collected as part of the run such that if they were to fail, we would have as much information as possible to be able to understand what might be wrong and to try to fix it. Now that we are working on adding a lot of infrastructure to be able to write new tests, it would be really good to keep this in mind.
In terms of this issue, as a goal it would be good to make a pass through all of the tests we currently run and validate that we have checks in place to collect logs, dumps, and other relevant assets that might help in the situation where they would fail.

[x] Get resource logs in test output (https://github.com/dotnet/aspire/pull/5193)

Closing this as we now have logs, blame dumps etc being generated, and collected. If there are more tasks to be done for this then we can open new issues with specific asks.


Request for better conditional class syntax

Feature request...
Angular has [class:foo]="bar"
Svelte has class:foo={bar}
Solid isn't too far behind, with: classList={{ active: state.active, editing: state.currentId === row.id }}
Mitosis has a CSS-in-JS construct, but conditional classes are currently just the basic JSX roughness, for example this bit from the TODO example. This syntax scales poorly to a longer list with multiple conditional classes.
class={`${props.todo.completed ? 'completed' : ''}

How about a better conditional class syntax? Ideally minimalist like Angular or Svelte, but even a Solid-like mechanism is the box would be great.

for JSX they usually want you to import classnames that does this
https://www.npmjs.com/package/classnames

Yeah, this suggestion effectively entails implementing what the classnames package does into Mitosis. I think, for now, folks who like those ergonomics can import classnames manually and use it, and we can explore baking it in the future once the fundamentals of the Mitosis core are more stable.


Repo Title Change

Please change your repository's title to Isuri-simple-chat just to have a uniform style.
This is just a sample issue to demonstrate how we're going to collaborate on Git.

And please close this issue whenever you addressed the requested changes :)


ShowMore and dismiss buttons problem in BitMessageBar

In BitMessageBar component when Truncated and OnDismiss properties both got value then the related buttons get so close to each other and makes mobile user to click on show more button

Current State
Expected State

@maryamhdr
plz investigate this issue 😊

@maryamhdr plz investigate this issue 😊

This issue is valid 👍🏻


Upgrade: Cloudstack Management Upgrade

ISSUE TYPE
Cann't Upgrade Cloudstak
VERSION
From Cloudstack version <IP_ADDRESS> To <IP_ADDRESS>
HYPERVISOR
CentOS 7.9 KVM
REPO
[apache-cloudstack]
name=Apache CloudStack
baseurl=http://download.cloudstack.org/centos/$releasever/4.19/
enabled=1
gpgcheck=0
UPGRADE OUTPUT
yum upgrade cloudstack-management
Loaded plugins: fastestmirror, langpacks
Loading mirror speeds from cached hostfile

epel: d2lzkl7pfhq30w.cloudfront.net
No packages marked for update

@Wei Zhou
I've changed baseurl to https://download.cloudstack.org/centos7/4.19/ but it was the same issue that I could see.
This repo doesn't have <IP_ADDRESS> version.


dagger do should check for a valid plan

Problem
Currently, dagger do (and its 0.1 predecessor dagger up) does not check that a plan is valid before running it. It delegates this task to the CUE loader, which in turn requires the developer to explicitly apply a top-level definition, like so:
import (
  "dagger.io/dagger"
)

dagger.#Plan & {
  // Plan configuration goes here
  ...
}

This is valid CUE, and we should support it. But it does not solve several problems caused by the absence of an explicit validity check:

Developers can shoot themselves in the foot by declaring fields outside the dagger.#Plan definition. For example:

dagger.#Plan & {
  ...
}
// Typo in a field name. Will not be caught.
clients: { ... }
// Still using a deprecated field name. Will not be caught.
inputs: { ... }

This is normal CUE behavior, but may not be immediately obvious to all developers.

If a plan spans multiple files, the top-level incantation must be repeated in each file. This is verbose (which makes DX incrementally worse) and also increases risks of mistakes.

It closes the door to denying top-level configuration fields. We're not yet certain which pattern is best: allow unrelated top-level fields to co-exist with the plan? Or forbid it? In doubt, we should go for the most reversible choice, which is to deny it (we can always allow it later with no breakage, but the opposite is not true). This would be a side effect of checking for valid plans.

Solution
Modify dagger do to explicitly check for a valid plan by unifying it against dagger.#Plan.

Any takers @dagger/maintainers ? This one is time sensitive, since it makes schema enforcement more strict (no top-level fields allowed if they're not part of the plan definition). Once merged, we have more options.

@shykes: I had a good chat with @aluzzardi about this.
First, I know how to accomplish this. It's pretty straightforward (finally figured it out):
// This loads the #Plan schema as a cue.Value
daggerInstances := cueload.Instances([]string{pkg.DaggerPackage}, &cueload.Config{Dir: src})
daggerInst := daggerInstances[0]

daggerValue := c.Context.BuildInstance(daggerInst)
planSchema := daggerValue.LookupPath(cue.MakePath(cue.Def("#Plan")))

// This is the user's CUE config
v, err := c.Context.BuildInstances(instances)

// Now we Unify the user's CUE config against the #Plan schema:
val := v[0]
val = val.Unify(planSchema)

As an aside, the way to accomplish a similar loading of a package via the CUE cli is: cue eval dagger.io/dagger

Now for a few questions about the intent and potential side effects of various implementations...
Different behavior: dagger vs cue eval
One concern that @aluzzardi and I have is that enforcement of the dagger.#Plan schema on the root cue.Value within dagger will mean that unless our users use this form:
dagger.#Plan & {
  // Plan configuration goes here
  ...
}

the output of cue def/cue eval won't behave like dagger does, cutting off a potential debug utility.
Backwards incompatible change/degradation of DX
Another concern we have is that enforcing dagger.#Plan will mean that patterns like this one (#PythonBuild) in Building docker container images (one of our Core Concepts docs), will no longer work, because we can't add new fields -- including definitions --  to dagger.#Plan. Related, it prevents dagger users from have any non-dagger CUE within their plan (excepting subfields of actions, because of the open definition of actions).
I've also seen this pattern in some code from @lyzhang1999 (so this change would break their plans).
I can see how this might be seen as a benefit as it forces users to create "external" packages (either in cue.mod/usr or as sub-packages in the root module) for patterns they are trying to create. But it also reduces the ability for users to incrementally move toward that, if they want.
Other possible solutions

We could warn on fields that are close to (Levenshtein distance or other similarity function) fields in dagger.#Plan, to reduce the likelihood of mistyped field names (including old deprecated field names like inputs)
We could have dagger project init create a nice scaffold hello world example (perhaps with --scaffold) that provides the dagger.#Plan & { ... } form out of the box.

Conclusions and next steps
All in all, I'm not sure how to balance the various DX concerns here. I understand the desire to reduce the types of errors and mistakes that you've outlined, but I'm also seeing the potential for other sorts of errors and DX degradation (including a pattern we've described in our docs) from occurring by implementing this solution.
All in all, after reviewing this, I think we've already past the point of being able to enforce this without user impact, so we should probably tread more carefully. And it has me wondering if we should find other ways to reduce the possibility of user error via misspelled fields (or the use of deprecated fields).

First, I know how to accomplish this. It's pretty straightforward (finally figured it out):

Great news!

Different behavior: dagger vs cue eval

One concern that @aluzzardi and I have is that enforcement of the dagger.#Plan schema on the root cue.Value within dagger will mean that unless our users use this form:
[...]
the output of cue def/cue eval won't behave like dagger does, cutting off a potential debug utility.

That's true but 1) long term there's a path to solving this problem cleanly, and 2) in the short term, it doesn't seem to be a big issue.

Long term path: there really ought to be a way to unify the root value with a definition, from the command line. Even separately from Dagger, I have felt the need for this feature, and been frustrated that it didn't exist. For example, to quickly vet a configuration against a particular schema, without having to explicitly edit that configuration. Something like cue --unify-root. We can contribute this feature upstream. And as a step towards contributing it upstream, we can add it to our dagger cue wrapper command (which we need to ship sooner rather than later).

Short term: it doesn't seem to be a pressing issue short term. I haven't felt the need to use cue eval for debugging in a while, except for very basic things like checking the value of a field. I'm not saying there is zero need for it, but it seems pretty low so far.

All in all, there is potentially a slight DX degradation, but there's a path to fixing it, and the DX gain - reducing confusion for all beginner - is much larger. So I think it's a good tradeoff.

Backwards incompatible change/degradation of DX
Another concern we have is that enforcing dagger.#Plan will mean that patterns like this one (#PythonBuild) in Building docker container images (one of our Core Concepts docs), will no longer work, because we can't add new fields -- including definitions -- to dagger.#Plan.

Two different things here:

Top-level definitions like #PythonBuild will continue to work, because closedness does not apply to them
Top-level hidden fields will also continue to work, for the same reason
Top-level regular fields will break. The sooner we merge this change, the less developers will be affected by this. Note that there is an easy fix, which is to change top-level fields to hidden fields.

Related, it prevents dagger users from have any non-dagger CUE within their plan (excepting subfields of actions, because of the open definition of actions).
I've also seen this pattern in some code from @lyzhang1999 (so this change would break their plans).
I can see how this might be seen as a benefit as it forces users to create "external" packages (either in cue.mod/usr or as sub-packages in the root module) for patterns they are trying to create. But it also reduces the ability for users to incrementally move toward that, if they want.

Yes, that's correct. This pattern of embedding a Dagger plan within an existing configuration, deserves further discussion. I don't feel like we know enough about usage patterns to lock ourselves in a direction. Until we do: "no is temporary, yes is forever". With this course of action we keep both options open.

Other possible solutions

We could warn on fields that are close to (Levenshtein distance or other similarity function) fields in dagger.#Plan, to reduce the likelihood of mistyped field names (including old deprecated field names like inputs)
We could have dagger project init create a nice scaffold hello world example (perhaps with --scaffold) that provides the dagger.#Plan & { ... } form out of the box.

I still like the original option better :)

Conclusions and next steps
All in all, I'm not sure how to balance the various DX concerns here. I understand the desire to reduce the types of errors and mistakes that you've outlined, but I'm also seeing the potential for other sorts of errors and DX degradation (including a pattern we've described in our docs) from occurring by implementing this solution.
All in all, after reviewing this, I think we've already past the point of being able to enforce this without user impact, so we should probably tread more carefully. And it has me wondering if we should find other ways to reduce the possibility of user error via misspelled fields (or the use of deprecated fields).

Thanks for the input. A few corrections (also mentioned above):

The pattern in the docs will not break
Some user configurations will break but not a lot, and the fix is easy
Learning curve will be improved which is a major pain point right now based on user feedback
The longer we wait, the more painful this change will be

@shykes Unfortunately, this is not true:

Top-level definitions like #PythonBuild will continue to work, because closedness does not apply to them. Top-level hidden fields will also continue to work, for the same reason

As discussed here and here, new definitions are not allowed to be added to already closed structs. I also have code that demonstrates this. The only way to add fields is by using hidden fields (or definitions).
Given the reversibility of this decision, I feel fairly good about doing it, with the caveats I listed.
If you're ok with the fact that no new fields or definitions of any kind  can be added to a CUE file that is a dagger.#Plan, I can probably finish this up tomorrow.

That surprises me, I tried it with cue and it seems to work?
$ cue eval - <<-EOF
> #Plan: {
>   hello: string
> }
>
> #Plan & {
>  #foo: "bar"
> }
> EOF
#Plan: {
    hello: string
}
#foo:  "bar"
hello: string

Is my version of CUE too old? It's dev version, commit<PHONE_NUMBER>cd0a63fd33691928665c60c3411361 .

I just tried again with the latest cue master (commit a03817fce72e220155022bf4fa9b2f68e35aa6b5) and it works. What am I missing?

I can dig into this more tomorrow, I know it's not working in the version of cue we're currently importing into dagger (which @aluzzardi and I have discussed upgrading).
There was a partial revert of that change, I believe. So... maybe it's still in our version of cue, but not in latest master.

The first version I tried<PHONE_NUMBER>cd0a63fd33691928665c60c3411361) was from July 2021. Fun fact: I was still pulling from the old CUE repo controlled by Google...


Broken behavior of item meta data access with MSBuild 15.3.409.57025

I get the following build error with the latest MSBuild version:

C:\Development\ws\Main\Environment\Targets\TomSun.Targets.SmartInclude.targets(11,7): error MSB4184: The expression "[S
ystem.IO.File]::ReadAllText(%(FullPath))" cannot be evaluated. Could not find file 'C:\Development\ws\Main\Environment
Builds%(FullPath)'. [C:\Development\ws\Main\Environment\Builds\BuildAndPlugins.csproj]

The itemgroup that contains the code which leads to the error:
  <ItemGroup>
    <SmartIncludeContent Include="@(SmartInclude)">
      <Content>$([System.IO.File]::ReadAllText(%(FullPath)))</Content>
      <IncludeType>$([System.String]::new(%(Content)).Split('|').GetValue(0))</IncludeType>
      <DirectoryPart>$([System.String]::new(%(Content)).Split('|').GetValue(1))</DirectoryPart>
      <FilePart>$([System.String]::new(%(Content)).Split('|').GetValue(2))</FilePart>
      <DirectoryRelative>$([System.IO.Path]::Combine($(MSBuildProjectDirectory),%(DirectoryPart)))</DirectoryRelative>
      <DirectoryAbsolute>$([System.IO.Path]::GetFullPath(%(DirectoryRelative)))</DirectoryAbsolute>
      <Files>$([System.IO.Directory]::GetFiles(%(DirectoryAbsolute),%(FilePart),SearchOption.AllDirectories))</Files>
      <OriginalRelativeDir>%(RelativeDir)</OriginalRelativeDir>
      <LinkRequired>$([System.String]::new(%(Content)).Contains('..\'))</LinkRequired>
      <Link Condition="%(LinkRequired)">%(OriginalRelativeDir)%(FileName)%(Extension)</Link>
  </SmartIncludeContent>
    <SmartIncludeFiles Include="@(SmartIncludeContent -> Metadata('Files'))">

    </SmartIncludeFiles>

  </ItemGroup>

The itemgroup is defined directly under the project node, not within a target. It seems that accessing/evaluating item meta data within the itemgroup itself doesn't work anymore or the processing order of property functions and item meta data evaluation changed. I didn't have such issues with the previous MSBuild versions (<= MSBuild of VS2017Update2). Is that a known bug? Is that an intended behavior change? (Don't hope so)
Unfortunately that bug breaks my build at many places. Thats just one example where it hits me.
Is there a way to get back the old MSBuild behavior when you have already installed VS2017 Update 3?
Oh I just recognized that it also prevents me from opening the projects in Visual Studio. Which means i can't do anything anymore with Update 3 installed. I really need help on this.
Update:
It seems that the issue had been found here #1932 and the guys dealing with it thought it is fixed, but from my point of view it is not fixed.
Update2:
I played a bit around, here is another example. There seem to be different behaviors between the property functions (e.g. string::new and MSBuild::Add):

  <SmartProjectReference Include="@(SmartProjectReferenceWorkaround2)">
      <Ok1>$([System.String]::new('%(HelpIndex)'))</Ok1>
      <Ok2>$([System.String]::new('%(StartSearchPatternLength)'))</Ok2>
      <Ok3>$([MSBuild]::Add(1,2 ))</Ok3>
      <Fails>$([MSBuild]::Add(%(HelpIndex),%(StartSearchPatternLength) ))</Fails>
     </SmartProjectReference>

Ok1-3 do what you would expect. They evaluate and calculate fine.
Ok1 and Ok2 were the cases been fixed with #1932
However, the add call for the MetaValue 'Fails' leads to the following build error:

Invalid static method invocation syntax: "[MSBuild]::Add(%(HelpIndex),%(StartSearchPatternLength) )". Method '[MSBuild]::Add' not found. Static method invocation should be of the form: $([FullTypeName]::Method()), e.g. $([System.IO.Path]::Combine(a, b)).

Update3:
I could reduce the issue down to such a simple, strange difference between two property functions:
 <SimpleSample>
      <Value>5</Value>
      <Ok>$([System.String]::new('%(Value)'))</Ok>
      <BuildFailure>$([System.Int32]::Parse('%(Value)'))</BuildFailure>
    </SimpleSample>

Anyone here? That issue breaks the build of existing projects and I didn't find a way to go back to VS2017 Update 2. I would really appreciate any feedback.
Here is a project where I broke down the issue to its core.  That project can be opened and build in MSBuild/VS Versions < 2017.3
PropertyFunctionsInItemGroupBug.zip

@KirillOsenkov can you please have a look on the issue. It is very important for me to know whether and when it will be fixed. It's very easy to reproduce it. In all versions of Visual Studio up to VS2017 Update 2 the samples (e.g. see update 3) worked. With VS2017 Update 3 using property functions within item meta data breaks the build in most of the cases.

@cdmihai @AndyGerlicher

Another instance is $([MSBuild]::GetRegistryValue(%(Identity), ``))

Why this fails: at operation construction time, the metadata has properties expanded to search for potential item references hidden behind properties. This also expands property functions. If metadata references other metadata, it does not get expanded, thus sending the metadata reference expression to the property function.
Why do some property functions referencing metadata still work? By luck

$([System.String]::new('%(M)')) works because there is special casing for constructors. It then binds to String::new(byte[]) and evaluates to "%(M)"
$([System.Environment]::GetEnvironmentVariable('%(M)')) works because it returns null

Hi, can anyone tell me when this issue will be fixed? It breaks my build since August now.

@cdmihai  I'm running into the same issue. Is there any update on this?

Is this a regression? If yes, what's the lastest version of MSBuild that didn't have this bug?

@knocte I think in visual studio 2017 update 2 it was still fine. I don't know the msbuild version that it used


E492: Not an editor command: Outline

I have installed on macOS laptop:
NVIM v0.8.3
LuaJIT 2.1.0-beta3

with CoC. You can see below from my :PlugStatus that neovim can detect the outline.vim plug-in:

But when I invoke :Outline I observer the E492: Not an editor command: Outline error.
Please advise on how best to resolve 🙂 (there's probably some configuration step I'm missing)

Hi! You need to call the setup function somewhere in your config.
https://github.com/hedyhli/outline.nvim?tab=readme-ov-file#setup
Please reopen if you're still encountering the issue.


Capstone project peer to peer code review

Hello @khitermedachraf  I can see you did an Amazing Job 👌.

Professional ReadMe presentation, However, I would like to recommend you to check on the live preview of your project in your ReadMe as it is not being redirected to the Web page.
Keep Coding

Okay, thank you so much, Brother @GOlivierNation.
I am working on it to add the GitHub Pages.


ESLint should be peerDependencies

Move ESLint from dependencies to peerDependencies.
It is a breaking change.

I wanted to suggest that do ;-) Should I send a PR for that?

@sapegin Yay! welcome to pull request.


p-values of correlation measures are not FDR-corrected

ideally the false discovery rate should be an argument provided to the method

we wrapped statsmodels multitests (fdr) here. feel free to copy if relevant as esmtools isnt really maintained anymore


Utilize caching Regex calls

new Regex() doesn't cache the build, but Regex.Match() does
\d matches much more than [0-9]

I don't mind this PR, but so many critical sections are changed (like machine listing) and I feel like "if it aint broke don't fix it".
Even your link for the \d page is broken.

The link not working is Microsoft's issue, just search for "Decimal digit character: \d" on that page to get to where I attempted to link.

\d matches any decimal digit. It is equivalent to the \p{Nd} regular expression pattern, which includes the standard decimal digits 0-9 as well as the decimal digits of a number of other character sets.

Test results:
The two failing tests fail on my machine on master as well.

@FanDjango  your views?

Ok, I did some research, and...
Concerning the \d->[0-9] change
\d is true for all representations of numbers. Depending on code page such can be:

It is recommended to use [0-9].
In the case of FluentFTP, it makes no big difference, but it doesn't hurt either. I had actually coded [0-9] in my recent PR, but changed that to \d when I saw that that was ubiquitous elsewhere in FluentFTP.
Concerning chaching enabled regex patterns
None (Ok, maybe one) of the places are in hot code paths where the caching of regex search patterns would be sensitive to performance issues. That's what I would look at. But the changes, as long as they are semantically correct, are worth doing.
The problem remains: Are they correct? If something fails due to this, we'll just need to fix it. Shucks, I made so many changes in the past months - I am standing by anyway to catch any bloopers I might have caused.

Concerning failed tests
The failed parser test is a unix file list that contains a date reference that the test code thinks is 2023 and not 2024. It needs a fix or removal of the offending directory entry.
The other failure is in the custom tests. If they are not configured as per the users site, (it)(they) fail.

I fixed the tests and am commiting that to master right now.

.NET 5+ AutoConnect was not reacting detecting a timeout properly
Unix directory listing parse tester was expecting wrong date

Tests (using current master) should now look like this (if custom tests are not configured):

But I don't think you need to re-run your test re. this PR.

Merged because regex change is minor and hopefully does not cause an issues.

Thanks for your contribution.


Update documentation

The current documentation is very out of date. It should be updated to document the latest features. Also, some breaking changes causes the examples to no longer work correctly.

I have updated almost all documentation. The only things that still need to be done are:

Add examples to WITH clause documentation;
Add examples to WHERE clause documentation.

I have updated almost all documentation. The only things that still need to be done are:

Add examples to WITH clause documentation;
Add examples to WHERE clause documentation.

I am testing the where example

require_once './vendor/autoload.php'; // Use require_once to include the autoload file

use function WikibaseSolutions\CypherDSL\node;
use function WikibaseSolutions\CypherDSL\query;

$n = node('Person');
$query = query()
    ->match($n)
    ->where($n->property('name')->equals('Peter'))
    ->returning($n)
    ->build();

print $query;

I have this error:
Fatal error: Class WikibaseSolutions\CypherDSL\Expressions\Operators\Equality contains 3 abstract methods and must therefore be declared abstract or implement the remaining methods (WikibaseSolutions\CypherDSL\Patterns\Pattern::hasVariableSet, WikibaseSolutions\CypherDSL\Patterns\Pattern::withVariable, WikibaseSolutions\CypherDSL\Patterns\Pattern::getVariable) in D:\xampp\htdocs\neo4j\vendor\wikibase-solutions\php-cypher-dsl\src\Expressions\Operators\Equality.php on line 17

Is there any update on this matter? It's already 2024!

Is there any update on this matter? It's already 2024!

This issue is already closed. If you notice something wrong/out-of-date in the documentation, please open a new issue for it. Thanks!


TippingBase: add additional storage data

TippingBase does not contain the data listed in https://linear.app/hnt-labs/issue/TOWNS-14596/tipping-smart-contract, or am I missing something?

TippingBase does not contain the data listed in https://linear.app/hnt-labs/issue/TOWNS-14596/tipping-smart-contract, or am I missing something?

why do we need all these mappings?


feat(emoji-picker, datepicker): revert style migration from dialtone8

Description
Reverted styles from dialtone8 of emoji-picker and datepicker componets.

working on linter fixes

linter fixed

Merging this cuz alex needs it for demo tomorrow.


Discard PooledByteBuf on demand

Expected behavior
Add a method PooledByteBuf.discard(). This method will discard the object instead pooling it again.
Scenario: When a DirectByteBuf or HeapByteBuf is too large, the application can release memory. This is a complementary method to PooledByteBuf.release()
Actual behavior
Pool all objects only limited by Recycler.maxCapacity
Steps to reproduce

Out Product processes MySQL protocol, using Netty as the tcp message handler. The size of the response from MySQL server is from bytes to hundreds kilobytes. The capacity of all the pooling PooledDirectByteBuf objects will increasing larger and larger. finally the java process consumed >20G direct memry and crashed every 1 ~ 2 weeks.

After we set io.netty.recycler.maxCapacity.default to 0 according to Netty documents. the problem resolved. The usage of memory is absolutely stable.

But there is bottleneck on peaktime without pooling. The bottleneck is on direct memory allocation and deallocation as we check the jvm stracktrace.

Minimal yet complete reproducer code (or URL to code)
N/A
Netty version
4.1.2.Final
JVM version (e.g. java -version)
java version "1.8.0_45"
Java(TM) SE Runtime Environment (build 1.8.0_45-b14)
Java HotSpot(TM) 64-Bit Server VM (build 25.45-b02, mixed mode)
OS version (e.g. uname -a)
Linux 3.10.0-229.el7.x86_64 #1 SMP Fri Mar 6 11:36:42 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

Can you try Netty 4.1.6.Final and see if you can reproduce?
Also have you tried using a smaller default value (it is per thread).

Looks this parameter,  io.netty.threadLocalDirectBufferSize, is to limit the max size of pooling ByteBuf. this is exactly what this issue proposed. We will try to set this parameter and verify. Thanks @Scottmitch .


Suggested GITHUB_TOKEN permissions in docs not sufficent to run on (at least) private repo's

It seems that the default permissions given as example in the docs or on the default template when you add the action to your repo are not sufficient on at least private repo's. I have not tested it on a public one.
It seems the default read-only permissions on workflow level has no influence anymore if job specific permissions are set.
I had to add the following to allow the action to run at all without erroring out:
      # To allow GraphQL ListCommits to work
      issues: read
      pull-requests: read

Without these extra permissions it fails very fast with the following error:
Error: RunScorecard: internal error: ListCommits:error during graphqlHandler.setup: internal error: githubv4.Query: Resource not accessible by integration
2023/08/17 09:37:40 error during command execution: RunScorecard: internal error: ListCommits:error during graphqlHandler.setup: internal error: githubv4.Query: Resource not accessible by integration

Also I noticed that without the permission
      # To detect SAST tools
      checks: read

The rule with ruleid SASTID is not working, it auto closes this security issue if I remove this permission.
Full workflow that works for us using the default GITHUB_TOKEN (no checks on branch protection or webhooks since that would require a PAT).
# This workflow uses actions that are not certified by GitHub. They are provided
# by a third-party and are governed by separate terms of service, privacy
# policy, and support documentation.

name: Scorecard supply-chain security
on:
  # For Branch-Protection check. Only the default branch is supported. See
  # https://github.com/ossf/scorecard/blob/main/docs/checks.md#branch-protection
  branch_protection_rule:
  # To guarantee Maintained check is occasionally updated. See
  # https://github.com/ossf/scorecard/blob/main/docs/checks.md#maintained
  schedule:
    - cron: '40 13 * * 1'
  push:
    branches: [ "develop" ]

# Declare default permissions as read only.
permissions: read-all

jobs:
  analysis:
    name: Scorecard analysis
    runs-on: ubuntu-latest
    permissions:
      # Needed to upload the results to code-scanning dashboard.
      security-events: write
      # Needed to publish results and get a badge (see publish_results below).
      id-token: write
      # Uncomment the permissions below if installing in a private repository.
      contents: read
      actions: read
      # To allow GraphQL ListCommits to work
      issues: read
      pull-requests: read
      # To detect SAST tools
      checks: read

    steps:
      - name: "Checkout code"
        uses: actions/checkout@c85c95e3d7251135ab7dc9ce3241c5835cc595a9 # v3.5.3
        with:
          persist-credentials: false

      - name: "Run analysis"
        uses: ossf/scorecard-action@08b4669551908b1024bb425080c797723083c031 # v2.2.0
        with:
          results_file: results.sarif
          results_format: sarif
          # (Optional) "write" PAT token. Uncomment the `repo_token` line below if:
          # - you want to enable the Branch-Protection check on a *public* repository, or
          # - you are installing Scorecard on a *private* repository
          # To create the PAT, follow the steps in https://github.com/ossf/scorecard-action#authentication-with-pat.
          # repo_token: ${{ secrets.SCORECARD_TOKEN }}

          # Public repositories:
          #   - Publish results to OpenSSF REST API for easy access by consumers
          #   - Allows the repository to include the Scorecard badge.
          #   - See https://github.com/ossf/scorecard-action#publishing-results.
          # For private repositories:
          #   - `publish_results` will always be set to `false`, regardless
          #     of the value entered here.
          publish_results: false

      # Upload the results as artifacts (optional). Commenting out will disable uploads of run results in SARIF
      # format to the repository Actions tab.
      - name: "Upload artifact"
        uses: actions/upload-artifact@0b7f8abb1508181956e8e162db84b466c27e18ce # v3.1.2
        with:
          name: SARIF file
          path: results.sarif
          retention-days: 5

      # Upload the results to GitHub's code scanning dashboard.
      - name: "Upload to code-scanning"
        uses: github/codeql-action/upload-sarif@a09933a12a80f87b87005513f0abb1494c27a716 # v2.21.4
        with:
          sarif_file: results.sarif

This permission example helped me lot to configure Scorecard in our GHES instance with a private repo. Should be definitely part of the documentation!!!

If someone is using a PAT and is getting the corresponding with the default config on a private repo:
Error: RunScorecard: internal error: ListCommits:error during graphqlHandler.setup: internal error: githubv4.Query: Resource not accessible by personal access token

I had to grant the following extra permissions to my fine grained PAT:

Contents: Read-only
Issues: Read-only
Pull Requests: Read-only

All three seem to be necessary.


KAFKA-2442: Fixing transiently failing test

Made the following changes:

Made the quotas very small. (100 and 10 bytes/sec for producer and consumer respectively)
For the producer, I'm asserting the throttle_time with a timed loop using waitUntilTrue
For the consumer, I'm simply calling a timed poll in a loop until the server side throttle time metric returns true

@auradkar : I had a look. One way to trigger the original test to fail consistently is to set the logging to TRACE in test.resources.log4j.properties. The new test passes, however the code is out of date with the recent trunk at this point. Could you resolve the conflicts if you get a chance?

@auradkar Could you address @jjkoshy comments and rebase?

@jjkoshy @lindong28 Is this JIRA still valid?

@guozhangwang I was not aware of this ticket. Not sure if it is still an issue. I would prefer to just close this ticket if there is no ongoing complaint of this issue.

@lindong28 cool thanks.


Workload CVEs: Tooltip polish

adding tooltips to table headers and severity count labels

hmm if the headers are never truncated, we probably can remove the excess tooltip props from headers since they would never show up. i'll modify the PR


Pack Dictionary

Can you please provide me with an example how to pack a Dictionary<String, AnyObject> to msg-pack?

        let dic:[String:String] = [
            "phone": "123",
            "code": "090"
        ]

        var mpDic = [MessagePackValue:MessagePackValue]()

        for (key,value) in dic
        {
            mpDic[MessagePackValue(key)] = MessagePackValue(value)
        }

        let packed = MessagePackValue(mpDic)

        print(packed)

Thank you very much for your reply. What if the dictionary is String: AnyObject]?

@n3trino In that case, you need to figure out what time of object each value is so you can convert it to the correct MessagePackValue case.

Although question was vague, it was answered. Closing until further discussion is needed.


Update Error GITHUB page bcdedit.md

In line number 102, the example reference article, showing 404 on the Github page. kindly update the correct links.

@bdwapp : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Hi @bdwapp, Thanks for finding this 404 link and the new link to replact it. Please remove the old link reference and add the new one as follows: For examples of how to use BCDEdit, see BCDEdit WindowsCMD.
Then we can complete this PR. Thanks!


Write a Blog Post: Using Goose with OpenAI 🦢

Write a Blog Post: Using Goose with OpenAI 🦢
Goose is your on-machine developer agent, automating engineering tasks seamlessly within your IDE or terminal. Guided by you, it can intelligently assess your project's needs, generate code modifications, and implement changes on its own.
Learn more about Goose in our documentation.
Once your content is merged, it will be featured on our Community Content site!
Example clips
https://github.com/user-attachments/assets/0217fc29-3b0b-4ab5-8a60-2dc53eb2b293
https://github.com/user-attachments/assets/5497112f-7ebb-4e73-9611-191be6d1934f
🚀 Goal
Write a blog post explaining how to effectively use OpenAI as a provider with Goose. Help others understand how to configure OpenAI, select models, and make the most of this integration.
🤝 How You Can Contribute
Write about things like:

Setting up OpenAI with Goose
Configuring your API key
Choosing the right models
Best practices and tips
Performance optimization
Cost management strategies
Real-world examples
Creative use cases

🔑 Tasks and Acceptance Criteria

[ ] Write a blog post about using OpenAI with Goose
[ ] Host your blog post on your preferred platform (dev.to, Medium, personal blog, etc.)
[ ] Add your content to the content/content.json file
[ ] Create a pull request with your changes

Your contribution in content.json must include:
{
    "type": "blog",
    "thumbnail": "./img/your-thumbnail.png",
    "title": "Your Blog Post Title",
    "link": "https://linktoyourblog.com",
    "contributor": "Your Name"
}

🌟 Resources

Goose Documentation
Goose repo
Provider Documentation
How to use toolkits
How to create toolkits

Full episodes on Goose to understand more

Getting Started

Comment ".take" on this issue to get assigned
Fork the repository and create a new branch
Write your blog post
Submit a PR with your content.json addition
Wait for review and address any feedback

Questions?
If you have any questions or need clarification, please comment on this issue!
Happy writing! 🦢

@blackgirlbytes give me this also!

.take

hmm @Marvellous111 is it okay if I give this to @aliveevie since he requested to get this prior to you?

Review my PR @blackgirlbytes


added date-picker.py example

Example application generates random data when using DatePickerSingle and then filters the data with DatePickerRange.
Created during PYCON sprints with @Coding-with-Adam

Hi @manolosolalinde
Thanks again for this app, it will make a nice addition to the Dash Example Index.  I'm going to assume you do not have any issues with the suggested changes, so I'll go ahead and apply them.
We plan to deploy next week.  If you have any questions or would like any other changes after this PR is merged, please feel free to open an issue as we can make changes at any time.


Another one with Battery discharge

Hi,
I've been having the issue with the battery being empty after around 2 weeks. Ive see the other threads regarding this issue however in my case the "Run as appication" flag was never set.

I just have updated to the latest version.

What I can see in the MQTT Log that there are messages every 3 seconds on nuki/presence/devices. Is this normal?
Any help is much appreciated!

In the supplied info nrRetry: is empty.
This translates to the Number of retries if command failed in Advanced Nuki Configuration page.
This might cause a loop?
Please check that Number of retries if command failed is set to a positive integer (3 is default)

Thanks a lot for answering! @technyon I enabled MQTT logging but I cannot see anything here for the last 5 minutes

@iranl thanks a lot, I changed the setting. Will see if itmakes a difference!

@technyon have you seen my remark before:
"What I can see in the MQTT Log that there are messages every 3 seconds on nuki/presence/devices."

Is this normal?

Yes. Presence detection updates these values every few seconds. Presence detection works independently from the lock/opener (its a function of Nuki Hub, not the Nuki device) and does not cause battery drain on the Nuki device.

Hi, after changing the setting the discharge of 2% a day seems still to be the case.
The lock is fully locked and unlocked 2 times a day and the latch is opened maybe 5 times a day.
Do you have a suggestion how I can diagnose this further?

@spaggi If you don't see continuous messages coming in, that's how it should be. If there's constant querying of the lock (which drains the battery), each query will generate log messages. Keep observing the messages though, and best case keep a history of messages for a day or so.
Are you sure this is related to Nuki Hub? You could easily check by unplugging your ESP for some time and observe the battery.

I will go on vacation soon so this will be a good time to monitor potential drain. Ill check the messages too. Thank you! For now I will close this as there might be nothing wrong


Link not working in player

Hello,
I tried the script and it is working only when paste the link on the browser :
https://pro.segavid.com/drive.php?id=ef10f175bdf79da9702d452fbd1b63ebb6648072e7404a987bf1db9ca04b572d&stream=1080p
But when use the on any player on websites such :
https://pro.segavid.com/stream/?link=https://pro.segavid.com/drive.php?id=ef10f175bdf79da9702d452fbd1b63ebb6648072e7404a987bf1db9ca04b572d&stream=1080p
not working
But our stream link not working. Any Seggestion ?
Thanks

Currently, I did stop develop this script


Fix bert training

We don't need to use the upstream PyTorch decomposition for the op aten.embedding_dense_backward, since now we have the lowering for the same in Torch-MLIR (https://github.com/llvm/torch-mlir/pull/2255).

@vivekkhandelwal1 I don't feel this is the right approach. Why aren't we using the upstream decomposition?

@vivekkhandelwal1 I don't feel this is the right approach. Why aren't we using the upstream decomposition?

Hi @pashu123, I don't see any specific reason for using only the upstream PyTorch decomposition. There are n number of instances where we have a decomposition in the PyTorch (https://github.com/pytorch/pytorch/blob/main/torch/_decomp/decompositions.py) but we are still not using that instead we have added a lowering for the op in Torch-MLIR. Few such examples are aten.tanh_backward, aten.upsample_nearest2d.vec, aten.silu, aten.nll_loss_backward op.
IIRC @powderluv once mentioned that ideally we should not rely on the upstream decompositions instead should add the lowering in Torch-MLIR. One rationale is that using the upstream decomposition is very much change-sensitive. A small change in the upstream decomposition can lead to multiple failures in the Torch-MLIR compilation. On the other hand, if we have that in Torch-MLIR itself we can avoid these issues and have more stability during the compilation. Also, using or adding a decomposition in the upstream PyTorch was just a workaround to get the op supported faster, otherwise, every op simple/complex can have a decomposition in PyTorch(many of which are already there).
And if we talk about this specific op, aten.embedding_dense_backward, then after this change in the PyTorch pytorch/pytorch@66e3989, it started throwing out this error:  That's why I added the lowering directly in Torch-MLIR instead of relying upon the upstream decompositions, which fixed the issue.
I would be happy to hear your thoughts and correct myself if I have been wrong somewhere.

The number one reason to rely on upstream Pytorch decomposition is because of the testing infra that it provides - I was having a hard time debugging the aten.var_mean validation issue when using the torch-mlir decomposition.
Secondly, writing the decomposition in Pytorch is not torch-mlir's problem and is Pytorch problem too when it comes to testing (which is a much bigger community). Also, writing and fixing decomposition in Pytorch is way simpler.
Also, writing the same decomposition again rather than reusing gives a sense of repeatability which should be taken care of from a software development perspective. AFAIK, in the early days @powderluv must have mentioned having in-house when the make_fx thing was experimental but now since it's mostly stable we should be leveraging that.
My concern is only regarding repeatability and fixing the root cause.

Lets try to land the PR in upstream PyTorch and meanwhile we can unblock ourselves locally.

This PR is not required anymore. Fixed by https://github.com/pytorch/pytorch/commit/12ca224662a630e55a8f6f1f8c5e187d2456051d.


Syn test suite fails in IE11

I'm getting this error...

'key' is undefined
Source: 500

... in test "synthetic/key:ctrl practical test", while using IE 11:

IE version: 11.1715.14393.0
Update version: 11.0.46

This issue was resolved. A previous failing test caused fallout for subsequent tests. This is a prime example of why the test suite should use iframes or popouts to isolate test elements rather than generating them in the Qunit page


not working :(

I installed opencc via homebrew on my mac M1, but this alfred workflow is not working. It's not showing me any converting options, even if I click "enter"

First. which version do you use?

Release v1.1.0 · cage1016/alfred-opencc for Alfred v5
Release v0.3.0 · cage1016/alfred-opencc for Alfred v4

Please provide log message to let me detect what is going on.


Single-channel use issue

Hi,
I'm trying to use use LMMM with one single channel to see how much it contributed to inspected kpi (I'd like to know how much of extra kpi was generated thanks to that channel). However when I follow simple_end_to_end_demo and just set number of channels to 1 when generating test data, I get TypeError: 'AxesSubplot' object is not iterable when calling plot.plot_media_channel_posteriors(media_mix_model=mmm).
Is it possible to use LMMM for single channel at all? If so, is there some special adjustment needed for it to be run?
Thanks

Full stacktrace:
[<ipython-input-52-4b8328576e48>](https://localhost:8080/#) in <cell line: 1>()
----> 1 plot.plot_media_channel_posteriors(media_mix_model=mmm)

[/usr/local/lib/python3.10/dist-packages/lightweight_mmm/plot.py](https://localhost:8080/#) in plot_media_channel_posteriors(media_mix_model, channel_names, quantiles, fig_size)
    806   fig, axes = plt.subplots(
    807       nrows=n_media_channels, ncols=n_geos, figsize=fig_size)
--> 808   for channel_i, channel_axis in enumerate(axes):
    809     if isinstance(channel_axis, np.ndarray):
    810       for geo_i, geo_axis in enumerate(channel_axis):

TypeError: 'AxesSubplot' object is not iterable

To complement info, when I run mmm.get_posterior_metrics it fails with
ValueError: Einstein sum subscript 'sc' does not contain the correct number of indices for operand 1.

Yeah I could see this being a usecase that was just never considered, typically MMM's are run to determine budget split between different ad channels. If I were you I would literally just add a fake additional media channel equivalent to random noise, that should just be attributed zero credit, as it'll have no relationship with the target. Then give it a low media prior 1e-6 etc. Not the cleanest, but probably faster than trying to debug lightweightmmm compatible with single channel problems.

Alright, I see, thanks 👍
I've tried adding a fake media channel with zero values and it crashed as scaler produced NaNs. I'm new to MMM so I have to say I'm not sure how to set up fake channel as you suggested. Could you provide me an example of such setting or a link to existing code that I could explore?

Oh literally, do exactly that, but pass in all ones, or random noise.
np.random.normal(size=(n, 1)) or np.ones(size=(n, 1))
Any constant or completely random variable will have no relationship with the target, and therefore be attributed no credit.

I'll give it a shot, thanks 👍

@michal-sankot
# Let's pretend you have 2 years of data + 13 weeks for the test set
data_size = 104 + 13
SEED = 0

######################################
# This is that data you should have,
# a KPI (data_size,), and a single media channel (data_size,1), and a single cost
##############################################################
media_channels = ['Media 1']
media_data = np.random.normal(10, 2, size=(data_size, 1)).clip(0.0)
target = (2 * media_data).reshape(-1) + np.random.normal(2, 0.5)
costs = np.array([100])

#################################################################
# Add your fake media channel, that has no relationship to target
# Random noise
###############################################################
media_channels += ['Fake Channel']
media_data = np.concatenate(
    [media_data, np.random.normal(10, 2, (data_size,1))],
    axis=1
)
# All cost priors must be non-zero, so we add 1e-6, for fake channel that should have no relation
costs = np.append(costs, 1e-6)

# Split your data
split_point = data_size - 13
# Media data
media_data_train = media_data[:split_point, ...]
media_data_test = media_data[split_point:, ...]

# Target
target_train = target[:split_point]

# Scaling
media_scaler = preprocessing.CustomScaler(divide_operation=jnp.mean)
target_scaler = preprocessing.CustomScaler(divide_operation=jnp.mean)

####################################################
# As you only have one channel of sig, the prior becomes 0.15.
# The mean scaling of target, makes mean target = 1
# CHANGE 0.15 to whatever prior belief you have for your single channels contribution
######################################################
cost_scaler = preprocessing.CustomScaler(divide_operation=jnp.mean, multiply_by=0.15)

media_data_train = media_scaler.fit_transform(media_data_train)
target_train = target_scaler.fit_transform(target_train)
costs = cost_scaler.fit_transform(costs)

extra_features = None
mmm = lightweight_mmm.lightweight_mmm.LightweightMMM(model_name="adstock")
mmm.fit(
    media=media_data_train,
    media_names = media_channels,
    media_prior=costs,
    target=target_train,
    extra_features=None,
    number_warmup=100,
    number_samples=100,
    seed=SEED)

plot.plot_media_channel_posteriors(media_mix_model=mmm, channel_names=media_channels)

Awesome, thanks 👍

Hmm, It does set fake channel contribution to none. However it considers baseline contribution to be extremely low. That doesn't look right.
plot.plot_media_baseline_contribution_area_plot(media_mix_model=mmm,
                                                target_scaler=target_scaler,
                                                channel_names=media_channels,
                                                fig_size=(20,5))

This is with your data? Or the fake data I supplied in the example?

If it's with the fake data this is what we'd expect to see. Baseline here is literally from the artificial noise I added. The y-target is almost a perfect function of 2 x media_channel_1 with some noise thrown in, with media_channel_1 being random noise centered on 10.

Aha, I see. It's with fake data. Sorry I'm missing those things that may be obvious to people familiar with MMM.

One more question about this block:
####################################################
# As you only have one channel of sig, the prior becomes 0.15.
# The mean scaling of target, makes mean target = 1
# CHANGE 0.15 to whatever prior belief you have for your single channels contribution
######################################################
cost_scaler = preprocessing.CustomScaler(divide_operation=jnp.mean, multiply_by=0.15)

Can I interpret this multiplication factor multiply_by as percentual expression of how much I expect tested channel to influence target kpi? e.g. if i set it to 0.15 I'm saying that I expect target kpi to increase by about 15% as an impact of this channel. Or is that an oversimplification?
I tried to find an answer in Discussions though I didn't find it there. Thanks.

You're pretty much in the ballpark. The target is 1-mean scaled, so average 1, the media data is 1-mean scaled, also average 1. The adstock transform is largely scale preserving. I'm ignoring the saturation function for simplicity (and for at least the exponent saturation models, they have a prior belief of no saturation). So as target = Beta x Saturated(Adstocked(X)) + ... where Beta has the 0.15 prior, I think it's right to say when the saturated, adstocked media X = 1, it as a prior belief drives 15 % of the mean value of the target we have seen historically. So, as again adstock is largely scale preserving and we're ignoring saturation, the mean value of X channel drives ~15% of the mean value of the target.
So it's not exactly that the target KPI increases by 15% as an impact of this channel, it's that when the channel = 1 (mean value), it causes (0.15 x mean target value) of the target KPI. It's average value, drives 15% of the average target we have seen historically.
Now,  the Beta Coefficient has a HalfNormal prior distribution, which is a weakly informative prior distribution, so you don't need to be exactly right in this chosen number.

Great, thanks for this detailed insight 👍


cache.cleanUp() - An understanding

This is not an issue I created but wanna know more about the use of cache.cleanUp() in what I am using cache as Map<UUID, JwtToken>.
The desired output is I wanna use cache.cleanUp() inside a setInterval of few minutes and it would clean up each entry from the cache map on the basis of the expiry time of each individual token.
From what I see, .expireAfterTime() is on cache level and not individual entry then how would ".cleanUp()" actually cleans up each entry from cache on the basis of token expiry?

As you say cleanUp() is a maintenance method, it doesn't actually control expiration, but will check for expired items when run. Transitory will run cleanUp() on its own during normal use, but using it with a setInterval is useful for certain cases where you need to garbage collect more often.
To control expiration of individual items you can use a function with expireAfterWrite to set a custom expiration time based on the value. Something like this could work if your value contains a Date in a property validUntil:
const cache = newCache()
  .expireAfterWrite((key, value) => value.validUntil.getTime() - Date.now())
  .build();

Or with ExpirationCache directly:
const cache = new ExpirationCache({
  maxWriteAge: (key, value) => value.validUntil.getTime() - Date.now()

 parent: parentCacheHere
});


[MXNET-372] [Copy of PR-10760] Add build flag for USE_F16C in CMake and clarify flag in make

Description
Copy of https://github.com/apache/incubator-mxnet/pull/10760 for v1.2
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[ ] The PR title starts with [MXNET-$JIRA_ID], where $JIRA_ID refers to the relevant JIRA issue created (except PRs with tiny changes)
[ ] Changes are complete (i.e. I finished coding on this PR)
[ ] All changes have test coverage:
Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
[ ] Code is well-documented:
For user-facing API changes, API doc string has been updated.
For new C++ functions in header files, their functionalities and arguments are documented.
For new examples, README.md is added to explain the what the example does, the source of the dataset, expected performance on test set and reference to the original paper if applicable
Check the API doc at http://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
[ ] To the my best knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Changes

[ ] Feature1, tests, (and when applicable, API doc)
[ ] Feature2, tests, (and when applicable, API doc)

Comments

If this change is a backward incompatible change, why must this change be made.
Interesting edge cases to note here

Instead of keeping two copies at the same time, could you finish the other PR first, and then create a cherry-pick PR once that PR is merged?

@szha the reason we did this is to save time by doing parallel builds on Release branch and master.  To make git history more clear we can put the link to the other PR in the title.

@szha That makes sense yes. We just wanted to save time with this PR and PR10777 to try cutting the rc2 tonight.

OK. I will stay out of your way then :)


fix(docs): reserve the first remove text run

close https://github.com/dream-num/univer-pro/issues/2044

Pull Request Checklist

[x] Related tickets or issues have been linked in the PR description (or missing issue).
[x] Naming convention is followed (do please check it especially when you created new plugins, commands and resources).
[x] Unit tests have been added for the changes (if applicable).
[x] Breaking changes have been documented (or no breaking changes introduced in this PR).

页眉页脚内设置字号后删除内容再次输入，字号未重置
操作步骤：
1、在页眉页脚输入内容
2、选中步骤一的内容设置字号
3、删除所有的内容点击正文
4、在页眉页脚输入内容
2024_8_28 21_04_58 video.webm


i will love to do copywriting for you

I love your application and would want to contribute to it, I'm not a developer but I am good at copywriting. I would love to make a copywrite for your Readme and make a pull request for you to merge. Your response would be highly appreciated. Also I would like to request if we could communicate either here or via email, so I don't have to create issues. Thank you.

Jockey already has a decent amount of copy both on GitHub and Google Play, so I'm not sure exactly what you have in mind here. That being said, anyone can open a PR without permission, so feel free to revise or expand on whatever you want and we can discuss the changes when you're ready to merge.
If you have any specific questions about this, feel free to post them in this issue or use the email address on my profile.

i am thinking about creating a Frequently asked question and an about us especially to address quick issues users get with the app

Having an FAQ could be nice, but I think an "About Us" document is unnecessary (and a bit inaccurate as there's only one dev). I'm gonna close this issue, but feel free to shoot me an email if you have any follow-up questions here.


CSS, LESS, or Sass - creating dark right frame content page with ease

Mmmmm. I love this theme! Thanks for making Virtualmin bearable to use in 2015. ;)
Do you have any of the stylesheets in LESS or Sass? Since this is built on Bootstrap, I would like to restyle the theme to something dark, which is rather easy if you've built the theme from Bootstrap LESS. There's too much white for my eyes... I can do this step by step, per class and such, but I do prefer working from LESS.
Or do you have a dark theme in the plans?

 I'm fully agree with having SASS but at the moment it would required a lot of work. Maybe one day in the future.
Do you know that in theme settings you can make it darker and choose other colors? It's not dark enough and you wanted it to be darker?

LESS also works nice. Bootstrap is originally LESS, not working from those files? Didn't see any in the github project...
http://bootswatch.com/darkly/
Although not this style, but that kind of dark. I didn't find any settings that make the whole theme dark (dark background, bright text). I can still restyle only those elements of Virtualmin I use, but rather time consuming compared to LESS when the theme is already based on Bootstrap.
How do you add all your custom CSS to the theme?

There is authentic.css in the repo, take a look. It's not done that nicely as LESS or SASS. I will think of creating dark right frame panel. It's not easy and will take some work. Good idea thought! Thanks! I have added to my future todos.

Is 'package.min.css' pure and original bootstrap.css?

Yes. https://github.com/qooob/authentic-theme/blob/master/unauthenticated/css/authentic.css

Have a look at the patch above.
Dark theme for the right content page finally here. :wink:
I hope you will like it! Give it a try by updating from GitHub.


Outdated Tutorial Page

Please make sure that this is a Bug or a Feature Request and provide all applicable information asked by the template.
If your issue is an implementation question, please ask your question on StackOverflow or on the Keras Slack channel instead of opening a GitHub issue.
System information

Have I written custom code (as opposed to using example directory):  unrelated
OS Platform and Distribution (e.g., Linux Ubuntu 16.04):  unrelated
TensorFlow backend (yes / no):
TensorFlow version:  unrelated
Keras version:  unrelated
Python version:  unrelated
CUDA/cuDNN version:  unrelated
GPU model and memory:  unrelated

Describe the current behavior
Started from the "Convolutional autoencoder" section, tutorial on the page https://blog.keras.io/building-autoencoders-in-keras.html has some mistake about plt usage. The code is shown below.
Describe the expected behavior
The usage of plt should be correct considering many learners might get frustrated when they imitated the code and got some unexpected errors.
Code to reproduce the issue
Provide a reproducible test case that is the bare minimum necessary to generate the problem.
decoded_imgs = autoencoder.predict(x_test)

n = 10
plt.figure(figsize=(20, 4))
for i in range(n):
    # display original
    ax = plt.subplot(2, n, i)
    plt.imshow(x_test[i].reshape(28, 28))
    plt.gray()
    ax.get_xaxis().set_visible(False)
    ax.get_yaxis().set_visible(False)

    # display reconstruction
    ax = plt.subplot(2, n, i + n)
    plt.imshow(decoded_imgs[i].reshape(28, 28))
    plt.gray()
    ax.get_xaxis().set_visible(False)
    ax.get_yaxis().set_visible(False)
plt.show()

Focus on this code
plt.subplot(2, n, i)

Unless i is started from 1, this expression is not correct.
Other info / logs
Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached.
unrelated

@Banyc,
The code of the Keras Tutorial has been modified from
plt.subplot(2, n, i) to plt.subplot(2, n, i + 1)
and the code now could be executed without any error. Please find the Gist of the working code. Thanks!


How to change textColor or TextView

I have integrated MessageViewController for Chat in my application. I am facing 2 issues right now:

I am not able to change textcolor of the textview. I have dark and normal mode and I need to change the textColor based on mode I select.
When I start typing into the textview, the tableview in which I am currently displaying the chat messages, scrolls up a little.

Please reply me ASAP as we need to go in production and I have already move here from SlackTextViewController.


More gracefully handle an exception raised during playback

Currently if a song fails midway through playback, we'll just log an exception and carry on to the next song.
https://github.com/anoadragon453/busty/blob/012b6d257e722e6487ad727a25208b8772a3eb02/main.py#L556-L558
I think we could handle this in a slightly better way. Namely:

Try replaying the song (though be careful of falling into an infinite loop).
Send a message in the room that playback failed, rather than having no feedback on Discord. Otherwise everyone but the author will just think that the song simply ended abruptly.

If there's a failure partway through I'm more inclined to believe it's an issue with the file than with some external factor which could be fixed by restarting playback. Sending a message in the room sounds like a good idea.


Compiler pedantry: unnecessary semi-colons

If running g++ in -pedantic mode, there are warnings about unnecessary semi-colons terminating the static function definitions and namespace declarations in space_ip.h and space_l2.h.

Also, the following variable is unused: https://github.com/nmslib/hnsw/blob/dbac49b2a6d3ed9a4d22e1b5ea0903106b2c2855/hnswlib/space_ip.h#L174


DISTX-693 In DE HA Template dfs_replication should be reduced to 2

See detailed description in the commit message.

HDFS Replication reduced to 2.


MSID: 96566 Version: 1 DOI: 10.1101/2<IP_ADDRESS>0392

MSID: 96566
Version: 1
Preprint DOI: https://doi.org/10.1101/2<IP_ADDRESS>0392
Step 1. Awaiting reviews
Editorial to post reviews via hypothesis
Useful links:

DocMap: https://data-hub-api.elifesciences.org/enhanced-preprints/docmaps/v2/by-publisher/elife/get-by-manuscript-id?manuscript_id=96566
New model tracking: https://docs.google.com/spreadsheets/d/1_fHaoOy7hjyocptKtVJRijeNpUY4hBS7Ck_aVmx6ZJk/
Reviews on sciety: https://sciety.org/articles/activity/10.1101/2<IP_ADDRESS>0392

For trouble shooting (e.g. no Docmaps available):

DocMap issue addressing: https://miro.com/app/board/uXjVNCwK6EI=/
Explore DataHub DocMaps API: https://lookerstudio.google.com/reporting/4c2f0368-babb-4beb-b5b3-497e7e7b0f08/page/ejphD
Unmatched submissions and preprints: https://lookerstudio.google.com/u/0/reporting/9f86204f-3bf7-477c-9b18-5c5ef141bf69/page/p_gxi57ha93c
Unmatched manuscripts spreadsheet: https://docs.google.com/spreadsheets/d/15QcK8w-ssB7109RQEDtFpJPZ0J5HTGxoHa_2TtpMBbg/edit#gid=1336081641

Step 2. Preview reviewed preprint
Production QC content ahead of publication
Instructions:

QC preview: https://prod--epp.elifesciences.org/previews/96566v1
Update ticket with any problems (add blocked label)
When QC OK, add QC OK label to ticket and add publication date and time to https://docs.google.com/spreadsheets/d/1amAlKvdLcaDp5W8Z8g77NmkwbMF5n_u89ArSqPMO8jg
Move card to next column
(At end of the day post link in #enhanced-preprint and ask for PDF to be generated)

Useful links:

Preprint DOI :  https://doi.org/10.1101/2<IP_ADDRESS>0392
Confirm reviews returned by EPP: https://prod--epp.elifesciences.org/api/reviewed-preprints/96566/v1/reviews
To update the MECA path in the docmap: https://docs.google.com/spreadsheets/d/1mctCQuNFBjSn97Lihy7_vBO6z7-N-oqyLv4clyi6zHg

Step 3: Awaiting search reindex
This step adds the reviewed preprint to the homepage: https://elifesciences.org
The search reindex is triggered once an hour. We need the reviewed preprint to be indexed as the search application serves the journal homepage.
Useful links:

Jenkins pipeline to reindex search can be triggered sooner or monitored here: https://alfred.elifesciences.org/job/process/job/process-reindex-reviewed-preprints/

Step 4: Published! PDF requested
Waiting for PDF to be generated
Useful links:

PDF tracking: https://docs.google.com/spreadsheets/d/106_XeDjmuBae7gexOTNzg60lapeqjl2aRn9DzupGyS8/

Step 5: Introduce PDF to data folder and git repo
Upload PDF to relevent folder in git repo https://github.com/elifesciences/enhanced-preprints-data/
Step 6: Done!

[ ] Kettle is on!

warn: [mixed-citation-other-publication-flag] mixed-citation in reference (id=c22) has a publication-type='other'. Is that correct?
warn: [mixed-citation-other-publication-flag] mixed-citation in reference (id=c27) has a publication-type='other'. Is that correct?
warn: [mixed-citation-other-publication-flag] mixed-citation in reference (id=c31) has a publication-type='other'. Is that correct?
warn: [mixed-citation-other-publication-flag] mixed-citation in reference (id=c33) has a publication-type='other'. Is that correct?
warn: [mixed-citation-other-publication-flag] mixed-citation in reference (id=c37) has a publication-type='other'. Is that correct?
warn: [mixed-citation-other-publication-flag] mixed-citation in reference (id=c43) has a publication-type='other'. Is that correct?

Hi @rkcook312 yes please: adjusted!


Using test bundle in integration test

#151 - using test bundle for RPM integration tests, added CI workflow for this test

This pull request #153 is assigned to @vatavuk/z, here is why; the budget is 15 minutes, see §4; please, read §27 and when you decide to accept the changes, inform @g4s8/z (the architect) right in this ticket; if you decide that this PR should not be accepted ever, also inform the architect; this blog post will help you understand what is expected from a code reviewer; there will be a monetary reward for this job

@sereshqua/z please review this job completed by @vatavuk/z, as in §30; the job will be fully closed and all payments will be made when the quality review is completed

Job was finished in 17 hours, bonus for fast delivery is possible (see §36)

@0crat quality bad

Quality is low, no payment, see §31


Change GroupIntoBatches to group for real

Please add a meaningful description for your change here

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

R: @davidcavazos - Do you know how I need to update groupintobatches_test if I am changing GroupIntoBatches transform. I updated the expected output but I am not sure if this is correct or not.

Run Python2_PVR_Flink PreCommit

Also, please add a JIRA :)

Thank you @udim. Addressed your comments. I will merge after tests pass.


Making predictions in intrinsic coregionalization model

I am writing a simple example for a GP with instrinsic coregionalization kernel for two tasks. I understand that the model calculates the posterior mean and variance for each task separately according to the way that they are indexed in variable X when the model fitting happens.  For example my tasks are indexed 0 and 1 so when calling  m.predict( np.array([[3, 0]]) ) it should return the posterior mean and variance of task 0 at input 3. However as you can see in the following code it returns a posterior mean and variance even when I put there an index that is not asssociated to any task (i.e., "-1" and "-2"). Where do those posterior means and variances come from?
import GPy
import numpy as np
import matplotlib.pyplot as plt

X = np.array([[ 1,  0], [ 2,  0], [ 3,  0], [ 4,  0], [ 1,  1], [ 2,  1], [ 3,  1], [ 4,  1]])

Y = np.array([[-0.23632664], [0.67736248], [-1.71536046], [2.01622779],
              [3.51775273], [-2.78539508], [2.19422611], [1.13307012]])

kernel = GPy.kern.RBF(input_dim=1, variance=1, lengthscale=1)

kernel_IC = kernel**GPy.kern.Coregionalize(input_dim=1, output_dim=2, rank=1)

m = GPy.models.GPRegression(X, Y, kernel_IC, normalizer=True)

m.Gaussian_noise.constrain_fixed(1)

# These are the posterior predictions for each task according to the provided input
mu_task_1, var_task_1 = m.predict(np.array([[ i,  0] for i in np.linspace(1, 4, 20) ]) )

mu_task_2, var_task_2 = m.predict(np.array([[ i,  1] for i in np.linspace(1, 4, 20) ]) )

# What is happening here, to which task do the posteriors mu and var belong?
mu_task_unknown_1, var_task_unknown_1 = m.predict(np.array([[ i,  -1] for i in np.linspace(1, 4, 20) ]) )
mu_task_unknown_2, var_task_unknown_2 = m.predict(np.array([[ i,  -2] for i in np.linspace(1, 4, 20) ]) )

plt.plot(np.linspace(1, 4, 20), mu_task_1, label='mu task 1', c='r')

plt.plot(np.linspace(1, 4, 20), mu_task_2, label='mu task 2', c='b')

plt.plot(np.linspace(1, 4, 20), mu_task_unknown_1, label='mu task ?1', c='y')
plt.plot(np.linspace(1, 4, 20), mu_task_unknown_2, label='mu task ?2', c='orange')

plt.legend()

sorry can't dive in that deep atm but combining a vanilla GPy.models.GPRegression with a Coregionalize kernel seems suspicous to me, when there exists a GPy.models.GPCoregionalizedRegression version as shown in GPy/examples/cpregionalization_toy.py.


Add supports for CAP

Please answer these questions before submitting pull request

Why submit this pull request?
[ ] Bug fix
[ ] New feature provided
[x] Improve performance

New feature or improvement

Supports CAP diagnostics feature.
Remove unwanted package references.

:+1: :100:


 From a given
entrypoint, AWS clients are now created exactly once and shared amongst all
components.

Enables all the create and destroy commands to accept preallocated client
instances from the caller.
Lifts all client creation up to the nearest entrypoint of each usage context
and injects them downwards from there.
Consolidates all session and config creation into a single utilty package.
Sets some new defaults for the SDK's built-in retry logic.

Further work should be done to tweak the SDK's built-in retry facilities, and
that can now be done centrally to start with and individual services can be
further tweaked as issues are identified.

/test e2e-aws

/test e2e-aws

/test e2e-aws

/test e2e-aws


Readme docs

@KevinMTO
Nice. First time that all Python tests are running through and proper coverage data is reported.
Let's try to keep it that way and slowly work towards turning all the other checks green and increasing the test coverage.


trackma: init at 0.8.4

Description of changes
https://github.com/z411/trackma

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

Same as PR #176331, this was largely based on the flake pieces of @hlissner (https://github.com/hlissner/dotfiles/blob/master/packages/trackma.nix) and @danielphan2003 (https://github.com/danielphan2003/flk/blob/main/pkgs/applications/video/trackma/default.nix).

Note that trackma-qt doesn't show anime cover image, and trackma-qt4 is broken.

Note that trackma-qt doesn't show anime cover image, and trackma-qt4 is broken.

Yeah... I'm really having trouble packaging QT stuff (had a similar problem with https://github.com/NixOS/nixpkgs/pull/176331#discussion_r890616151). Should we not expose trackma-qt on all-packages.nix for now?

Yeah... I'm really having trouble packaging QT stuff (had a similar problem with #176331 (comment)). Should we not expose trackma-qt on all-packages.nix for now?

Sure thing. I'm using the latest rev and QT is still buggy.

Result of nixpkgs-review pr 179715 run on x86_64-linux 1

3 packages built:

trackma
trackma-curses
trackma-gtk

@danielphan2003 I removed trackma-qt for now... Once this PR gets merged I'm gonna do another one for adl so we complete the trinity.

Result of nixpkgs-review pr 179715 run on x86_64-linux 1

3 packages built:

trackma
trackma-curses
trackma-gtk

Note that trackma-qt doesn't show anime cover image

I'm really having trouble packaging QT stuff

Packaging trackma for myself for a pretty long time and have no issues with Qt UI... are you intrigued?

Well, still don't know how to easily and optimally share NixOS packages, so gist: https://gist.github.com/toyo-chi/d89e804c1e3e27341b2ccea835c017c8
Maybe not so pretty, but works for me!

Just manually wrapping in preFixup. Maybe not so pretty, but works for me!

Hey @toyo-chi, sorry for taking that long to reply. Indeed, wrapping it in preFixup seems to solve the problem. I'm gonna push another PR fixing it soon. Thanks!
P.S. Feel free to add yourself as a maintainer to this package too. :wink:

I'm gonna push another PR fixing it soon. Thanks!

And please do not forget to enable submodules, otherwise anime-relations module will not be fetched. And also please include icon and desktop files too.

P.S. Feel free to add yourself as a maintainer to this package too.

I-i'm not ready for this, senpai!


[fix] possibility selecting disabled member

Coverage increased (+0.04%) to 83.59% when pulling 5ae49acbbc0839a2f7d17e85091d29a676aacac1 on sunny4381:fix/possibility-selecting-disabled-member into 4b6f362ab3f720442c2028108faf3fe7583433af on shirasagi:master.

Coverage increased (+0.04%) to 83.59% when pulling 1efb05cf553a35bd1076795699b3f470964871b6 on sunny4381:fix/possibility-selecting-disabled-member into 4b6f362ab3f720442c2028108faf3fe7583433af on shirasagi:master.


[CLOSED] Add DWP to the list of publishing departments for the ESI Funds finder

 Issue by issyl0
Wednesday 28 October 2015 at 14:43 GMT
Originally opened as https://github.com/alphagov/specialist-publisher/pull/593

Trello: https://trello.com/c/Gwnujz5D/175-add-dwp-to-european-structural-and-investment-fund-esif-finder.

issyl0 included the following code: https://github.com/alphagov/specialist-publisher/pull/593/commits

 Comment by issyl0
Wednesday 28 October 2015 at 14:45 GMT

TIL that GitHub now has an "Update branch" button on the PR when a branch is out of date with master, which inserts a merge commit. :disappointed:
EDIT: Rebased to update it with master but get rid of the merge commit.


Using Material with PolygonOutlineGeometry

In order to modify the color of polygon outlines, you can use the approach in the sandcastle which uses PerInstanceColorAppearance and then use:
var geometryAtts = primitive.getGeometryInstanceAttributes(geometry.id);
geometryAtts.color = ColorGeometryInstanceAttribute.toValue(fillColor);

The problem is that this needs Primitive#update() to be called before use, which I cannot guarantee. Using Material works fine for PolygonGeometry and you modify the color by setting it on appearance.material.uniforms.color. The same does not work for PolygonOutlineGeometry and I'm not sure why. Here is my construction code:
var outlineGeometry = new GeometryInstance({
  geometry: new PolygonOutlineGeometry({
    polygonHierarchy: polygonHierarchy,
    height: elevation,
    extrudedHeight: elevation + height,
    vertexFormat: VertexFormat.POSITION_AND_ST
  })
});

var outlineAppearance = new EllipsoidSurfaceAppearance({
  material: new Material({
    fabric: {
      type: 'Color',
      uniforms: {
        color: borderColor
      }
    },
    translucent: false
  })
});

var outlinePrimitive = new Primitive({
  geometryInstances: outlineGeometry,
  appearance: outlineAppearance
});

I get the following error:

DeveloperError: Appearance/Geometry mismatch.  The appearance requires vertex shader attribute input 'st', which was not computed as part of the Geometry.  Use the appearance's vertexFormat property when constructing the geometry.

I am setting the correct VertexFormat, so I'm not sure why it's failing.

Duplicate with #2174.  @aramk please reopen if there is another issue.