using editing form reorders fields after the changes are saved.  breaks later sorting query

Expected Behavior
I have tasks that look like the following:

[ ] 13:00 #tasks some meeting .....

when i open with the tasks form the #tasks isn't visible but after a change to description and save I get this:

[ ] #tasks 13:00 changed meeting description

I use sort on description to get my timed items displayed in order.  sort of a replacement for the out of date daily planner.  I would have expected the #tasks not to be first.
A solution would be to have an option to put the #tasks tag at the end of the description.
Current behaviour
the #tasks tag is always placed at the start
Steps to reproduce
see above,  just edit the sdescription
Which Operating Systems are you using?

[ ] Android
[ ] iPhone/iPad
[ ] Linux
[ ] macOS
[X] Windows

Obsidian Version
0.15.9
Tasks Plugin Version
1.11.1
Checks

[X] I have tried it with all other plugins disabled and the error still occurs

This sounds very familiar, I'm pretty sure we've had requests for this kind of thing already - putting the global filter at the end.
@pcause Please could you search for duplicate discussions and issues, and if one exists, upvote it and close this one?
But one thing I don't understand: Do you have a global filter #task? I thought that the global filter prefix did not contribute to the sort order? So maybe there is a different fundamental cause?
Is the crux of the problem that the global filter is being included in the sort order, when it should be ignored???
I mean, it sounds like you are unhappy with the sort order, but are proposing a solution which is unrelated to the sort order?
What have I misunderstood? 😄
@AnnaKornfeldSimpson Even though this sounds like a feature request - which should go in Discussions - I suggest not doing anything with it until we understand what the best solution is, and whether it is really

a duplicate
a new feature request (unlikely)
or an alternative solution (fixing the sort order) to previous requests for the same feature!

(My head hurts!! 🤯)

@pcause Please could you also show us a screenshot of your Tasks settings?
I am wondering if it is some combination of these settings:

I wonder whether you have 'Global task filter' enabled, but 'Remove global filter from description' disabled?
That's the only reason I can think that the #task tag might be being taken in to account in the sort order.
In which case, a workaround requiring no code changes would be to turn on 'Remove global filter from description'.

@pcause cancel this:

This sounds very familiar, I'm pretty sure we've had requests for this kind of thing already - putting the global filter at the end.

Yes, it is a duplicate of #147 - which links to other requests as well.
So I'm converting this to a Discussion/Q&A - to get to the bottom of what is going on with your setup.


AssertionError in testMultipleJobsReadSameCacheHitGlobalFile

http://jenkins.cgcloud.info/job/toil-pull-requests/1410/

It just occurred to me that toil-jenkins-slave slaves are shared by toil-scripts and toil. It is possible that toil-scripts pollutes the slave.

To the order of 70G? I find that a little hard to believe

This is caused by running on a slave were for some reason ephemeral wasn't mounted. I'm leaving this open because I don't know why ephemeral is only mounted sometimes. The AMI has a suitable block device mapping. The useEphemeralDevices for the slave was set to false in config.xml. I changed that to true for all slaves. We'll have to keep an eye out for it.
See also https://github.com/BD2KGenomics/cgcloud/issues/184

We should also talk about detecting lack of temporary space in jenkins.sh, the Makefile, or in a special unit test.

Wow! How did you find this?! Awesome. Can we have a line in jenkins.sh that checks for (say) 20G of space on ephemeral before starting any tests?

Yes, we should.


licensor: "Fix" integration test for 2021

Motivation for this change
The license_and_name test depends on the year, thus failing and causing the build to fail.
Things done

Use unstable-2021-02-03 instead of 2.1.0 + patches

Use the patch from https://github.com/raftario/licensor/pull/28 that "fixes" the license_and_name test by bumping the year from 2020 to 2021, until the test implementation can be properly addressed
Security Updates
This also includes a security update from https://github.com/raftario/licensor/pull/8
Instead of adding 2 more patches (one for the test fix, one for the security update), using the latest commit from master seems to make the most sense for now

This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
If you have any questions or problems please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 111776 run on x86_64-darwin 1

1 package built:

licensor


Great project. Look forward to the day when it's available

Thanks!
Right now I'm focused on finishing testing existing code and planning the rest of the code. I don't know how far it is from completion since I'm still planning the rest of it, but it's making good progress.
Recently I finished writing all the metadata parsers (metadata, toc, manifest, spine, etc), though I'm still planning on how it should be accessed


New Tab Button Crashes the App, Download Progress stuck at 0% and Many More......

So upon testing, I noticed these bug.

When clicking the New Tab button, it crashes the app.
Bookmarks and History Doesn't Work. Download Option Doesn't show Downloaded files.
Files Download but Progress is stuck at 0%. Canceling causes Crash.

System Used for Testing: Arch Linux

I'm   apologize for this issue . The issues you’ve encountered are due to certain features not being properly implemented. I’m actively working on resolving them and ensuring the app functions as expected.
Thank you for your efforts in testing and reporting these bugs—it’s invaluable in improving the app. I’ll keep you updated on the progress and share a fix as soon as it’s ready.
Your patience and support mean a lot!

This issues is solved. please check our latest version


Can't access attached local hard disks

Preflight Checklist

[X] I have installed the latest version of Storage Explorer.
[X] I have checked existing resources, including the troubleshooting guide and the release notes.
[X] I have searched for similar issues.

Storage Explorer Version
1.20.0
Regression From
No response
Architecture
x64
Storage Explorer Build Number
20210625.5
Platform
Linux
OS Version
Ubuntu 20.04
Bug Description
Trying to access a local hard drive results in "Error opening directory '': Permission denied". The directory is on an extra internal hard disk, has all the correct permissions set and is readily accessible through any other means: from any file manager or from the shell.
Steps to Reproduce

Launch Storage Explorer
Expand Blob containers node
Select a container
Click 'Upload' button
Navigate to a HD device mounted in /media or to any symlinked directory located on such device

Actual Experience
Storage explorer reports an error with "Permission denied" message (see screenshot).

Expected Experience
The directory should be traversed without any trouble.
Additional Context
The Storage Explorer is installed from snapstore

Maybe a duplicate of https://github.com/microsoft/AzureStorageExplorer/issues/4093. Unfortunately the exact cause is still an unknown to us except that we already noticed that our snap is restricted to access external drives. We will see if there is anything we can configure for our snap to remove the restriction.

Thanks for the reply, @JasonYeMSFT.
Yes, it does sound similar. Especially what you write in your comment from 24th of March
I am able to see the symlink as a directory in the Storage Explorer's File Upload dialogue, but trying to navigate to it results in "Permission denied" message. All other ways of navigating to these directories work without any problems. Even if I try navigating there with Chromium -- another application installed from Snapstore -- it shows everything correctly. The problem occurs only in Storage Explorer.
I will try the .tar.gz build when I have time and I'll get back here with the results.

@VictorSago You may need to connect the removable-media interface, which doesn't automatically connect when you install Storage Explorer. According to the Snapcraft documentation, this interface is what you need to access removable media, like your external hard drive. Storage Explorer already includes the removable-media plug, so you should be able to connect it by running:
snap connect storage-explorer:removable-media :removable-media

Give that a try and let us know if that solves your problem.

Haven't received a response from the author yet, so I'm going to close this issue.
@VictorSago If you are still experiencing this issue, please reply or open a new issue.

@VictorSago You may need to connect the removable-media interface, which doesn't automatically connect when you install Storage Explorer. According to the Snapcraft documentation, this interface is what you need to access removable media, like your external hard drive. Storage Explorer already includes the removable-media plug, so you should be able to connect it by running:
snap connect storage-explorer:removable-media :removable-media

Give that a try and let us know if that solves your problem.

@craxal  I had the same problem, tried your solution, it works now. Thanks.

@VictorSago You may need to connect the removable-media interface, which doesn't automatically connect when you install Storage Explorer. According to the Snapcraft documentation, this interface is what you need to access removable media, like your external hard drive. Storage Explorer already includes the removable-media plug, so you should be able to connect it by running:
snap connect storage-explorer:removable-media :removable-media

Give that a try and let us know if that solves your problem.

Just to add data points, I was experiencing the same issue, ran the command above, and issue resolved without even having to restart Storage Explorer. Thanks :-)


Adding TSUP as the bundler tool

Tied to #41. Totally optional as we discussed in discord, but feel free to play around with the setup.
It looks like you might dev on a windows computer, would love to know if the updated build and dev commands work for you.

Looks cool! Have you tested it locally to make sure everything works?

Does work on my end on WSL. Can anyone try this on powershell?

works on powershell, #41 can e closed now 👍🏼


有没有好的方案，把URLSessionDataDelegate更多的协议实现暴露出来

https://github.com/onevcat/Kingfisher/issues/1619
尝试一种方案。把URLSessionDataDelegate的其他协议方法，转发给业务方定制化处理

我可能更倾向于把 SessionDelegate 写成 open 然后通过 subclass 的方式来实现自定义逻辑。
当然，这个 PR 里的实现也是一种办法。我考虑一下哪种会更好。

Nice!

It seems that these changes cause an error while loading.
2021-03-09 11:51:23.423663+0900 Kingfisher-Demo[44705:9436274] 44705: CFNetwork internal error (0xc01a:/Library/Caches/com.apple.xbs/Sources/CFNetwork_Sim/CFNetwork-1220.1/Loading/Connection/Loader Side/URLConnectionLoader.cpp:266)

I am not sure what is happening now, but reverting these changes can solve the issue. I am going to revert it and tag a patch version. I will also keep digging to see what is the problem/


Cannot import standard ES6 modules from npm

What
At the moment if you try to import using our documentation using a standard ES6 bundler such as Rollup it will fail.
This is because we ship our bundles as UMD, which is great for browser and CommonJs support but not ES6 Modules (better for build pipelines).
This means our current guidance around rollup is misleading and only works when compiling from source.
We could consider adding more real world examples that import the package directly to ensure what we recommend is tested.
I'm not sure if we should be publishing these as .mjs files, which seems to be what Node.js is going towards.

Webpack example: https://github.com/alphagov/govuk-frontend/tree/master/examples/webpack
Rollup advice on modules https://github.com/rollup/rollup/wiki/pkg.module
Microbundle https://github.com/developit/microbundle

Why
Some users rely on getting modules directly from /src, which we don't recommend and don't want to encourage. Many of these users say they're running outdated versions. We should make it easier for them to import as standard ES6 modules.
Done when

[x] Test including modules directly from /src
[x] Research into type: module in the package.json
[x] Test in some dummy apps/services
[x] Automated testing
[ ] Implement decided approach
[x] Do a pre-release and share with the community to make sure this solves the problems (try and reach out to those we know are going directly to /src)
[ ] Documentation
[ ] Raised a PR for using this in the Design System

Do you lose tree shaking by using 'rollup-plugin-commonjs'/UMD? I'm having to useimport Button from 'govuk-frontend/components/button/button'; rather than import { Button } from 'govuk-frontend' to only get the code I want.

Yeah I believe that's the only way currently to achieve what you'd get for free with tree shaking.

A possible way to test tree shaking: https://twitter.com/Rich_Harris/status/1031220091940204546?s=17

https://philipwalton.com/articles/deploying-es2015-code-in-production-today/

http://exploringjs.com/es6/ch_modules.html

In our project we use very few govuk-frontend js modules: Button, Radios, Checkboxes, ErrorSummary, that's about it. So to save on the bundle size I made a custom all.js file that only imports the components I need. The other reason we do this is that we have some custom components which use the same polyfills (and one that reuses Button) which can also be added to the same all.js file. The tree shaking will avoid bundling the same polyfills or components twice, resulting in a single small js bundle.
Unforuntatley the only way to achieve this is to add this Github repo as a npm depency, as the unbundled source is not included in the npm package and using the individually bundled components does not take advantage of tree shaking, bloating out the total bundle size.
This also presents us with some problems:

The version of the Github repo is not always accurately reported by the 'out of date' check in our CI pipeline so it's always yellow with a warning
The Github repo package.json requires specifically node version 12 preventing us from updating to current LTS version 14 (the npm install fails)
govuk-frontend is already a subdepency of a DWP package meaing we're effectively installing everything twice, with the nunjucks macros being the loaded from the subdepency but the client side js bundled from the source repo. Keeping these versions the same is a faff
This is clearly a messy hack

So in an ideal world the unbundled component js would be included in the govuk-frontend npm package in a way in which it could be imported as an ES6 module. This could also allow serving the ES6 modules directly over HTTP2 in the future, falling back to the bundle.
I'd be happy to help on the implementation of this if an approach could be agreed.
Thanks!

direction most packages are moving to is to specify type: module in package.json
Sindre Sorhus’s FAQ. for more details

I did some testing last year to verify that directly including the ES6 modules from /src in the GOV.UK Frontend npm package would work with bundler imports. I imported the component JavaScript using Parcel and Webpack from the npm package and didn't encounter any problems.
I also saw that there was about a ~20% reduction in the size of the resulting JavaScript file, although this is a bit arbitrary since I only tested the import of two components (the accordion and the character count). I also had a bit of a dig through what the removed JS consisted of and agreed with @andymantell's assessment that it seems to be mainly made up of the duplicated polyfills.
I haven't assessed the type: module solution so we should do that as well before deciding on next steps.

I had a quick look at using "type": "module", but didn't get far.

The type defaults to commonjs, though the guidance is to explicitly set this in the package.json, in case defaults change in the future. We could do this in any case.
This is a hard switch. It will break for anybody using a require to grab govuk-frontend. This happens even if we don't change anything about the compiled files (ie: they're all still UMD).
Seems like this is for a package that wants to completely switch over to ESM.
I had some success hackily generating two sets of files via gulp rollup using the es and umd formats, though I didn't get as far as treeshaking the polyfills. In this case we could set "type": "module" for the appropriate files.

I've got a WIP branch with some hacky non-functional bare bones approaches that I was going to run by the team.
https://github.com/alphagov/govuk-frontend/tree/bk-create-esm-files-in-package

Use rollup to bundle ESM files

Doesn't really work - we're rolling up file by file, so all the polyfill duplication still happens, and you lose the opportunity for other services to roll their own bundling.

Copy the JS source files  as .mjs into the same locations as the generated UMD files

Big questions here are how to correctly target the .mjs files and not the UMD files (all.mjs would probably need a slight refactor?), and which files need to be kept as is.

Copy all source files to a separate folder - something like govuk-esm

The published package becomes a lot larger and there's presumably going to be a lot of namespacing issues. Could the JS files only be separated into another folder with an entry point file?

ESM Write-Up
I picked this work up last week and carried on where @domoscargin left off - looking into the 3 options detailed in the comment above in more detail to see which is most feasible.
Option 1: using rollup
I’ve almost immediately discarded this option because of the downsides written up by @domoscargin.
Option 2: copying src files into /package alongside UMD
It seems difficult to get this working properly (i.e: separating out .mjs and .js and making sure you’re only importing either ESM or UMD). I changed the package/package.json to give 2 entry points for UMD or ESM, e.g:
  "name": "govuk-frontend",
  "description": "GOV.UK Frontend contains the code you need to start building a user interface for government platforms and services.",
  "version": "4.0.1",
  "main": "govuk/all.js",
  "module": "govuk/all.mjs",
   …

However, even though the initial entry point works correctly, the JavaScript that all.mjs imports seems to still target .js (UMD) files and there’s no way of telling it to import .mjs instead.
I didn’t dig into setting ”type”: “module” in the package/package.json which might change that default behaviour - I'm not sure. That might become a breaking change, where ESM becomes the default, which I think we want to avoid.
Option 3: copying src files into a new folder for ESM
This is the option which I’ve tested the most as it seems the most feasible option.
➡ See WIP govuk-frontend branch
I’ve added a new copysrc task which copies the JavaScript files in src, renames them to have the .mjs file extension and saves them into a new package/govuk-esm folder.
Note: This only copies JavaScript into the package/govuk-esm folder. The package/govuk-esm folder is not a complete copy of what’s currently in package/govuk. I think our JavaScript is separate enough from our sass, nunjucks etc that we can pull it out into a separate folder like this, but happy to be corrected on that.
➡ See WIP govuk-design-system branch
I tested this by editing the govuk-frontend.js in the Design System repo and replacing it with:
import { initAll } from ‘govuk-frontend’
initAll()

The only thing which needed adjusting to get this to work were the imports of our common helpers.
Next steps
Things I was hoping to do, but unfortunately didn’t get enough time before annual leave:

Test this WIP solution with more services/apps/examples other than just the design system
Figure out the interaction with bundlers and if this works
Figure out what additional documentation/changes to existing documentation we might need
Share with other developers and get opinions on if this is the right direction to be heading in

@vanitabarrett if I were to try and pull this into govuk-react-jsx, do I just need to reference the /package folder? That's exactly the contents of the package once it's published to npm?

@andymantell you should be able to do that using npm link from the package folder, yep.
If it's helpful, we could also publish a pre-release branch you can use without needing to clone govuk-frontend locally, or if you need to push a branch of govuk-react-jsx anywhere else.

@36degrees Good shout on nodeListForEach - I'd noted down our decision, but forgotten to update that branch. Should be updated now in this commit.
For the other point, importing from govuk-frontend is how I'd expect someone to import. We're not defining anything new called 'govuk-frontend-esm'. Instead, the fact that we're using an import statement should be enough for the govuk-frontend package.json to "point us" to the govuk-esm directory because we've made these changes to the package/package.json file.
Does that make sense?

Summary of changes
We're proposing to add a new govuk-esm directory to the shipped govuk-frontend package. This new folder will only contain ES Module javascript files (published as .mjs files), including component javascript and polyfills.
In order to support both the UMD we currently ship, and these new ESM files, we will add the following to our package/package.json file:
...
 "module": "govuk-esm/all.mjs",
  "exports": {
    "import": "./govuk-esm/all.mjs"
  },
  "sideEffects": [
    "govuk-esm/vendor/**"
  ]
...

Setting the module and exports to point to the govuk-esm folder allows a user to simply write (for example) import { Accordion } from 'govuk-frontend' without having to know that the ES Modules are stored in a separate directory - the package.json will handle the entry point depending on how govuk-frontend is being included in a project. This also means the change is backwards compatible - existing users relying on the UMD files won't need to make any changes.
Because of the way we include polyfills in our JavaScript, we also need to set sideEffects: ["govuk-esm/vendor/**"]. When we import polyfills, we rely on them being there without having to 'call' them, which means our code has "side effects". Without setting this property in the package.json, a bundler would exclude the polyfills because it thinks they aren't being used.
You can preview all the proposed changes here

Hey! Thanks so much for this work, once released this should allow me install the govuk-frontend module properly again rather than include a tagged point in the repo to get the original source. I'm gonna make a branch on our frontend project to test it out and see if these changes will fit neatly into my build.
Thanks

Hi,
So I seem to have an issue where I can't import any files directly from their file paths while exports is set in the package.json:
  "exports": {
    "import": "./govuk-esm/all.mjs"
  },

This seems to restrict the node-resolve plugin of rollup from importing anything other than that file. If I remove the exports from the package.json it works fine.
For context this is what I'm trying to do in a custom all.js (import the GOVUK components I wish to init, along with an HMRC component and some that are custom to the service):
import { nodeListForEach } from 'govuk-frontend/govuk-esm/common.mjs';
import { Button, Checkboxes, ErrorSummary, Radios, SkipLink } from 'govuk-frontend';
import TimeoutDialog from 'hmrc-frontend/hmrc/components/timeout-dialog/timeout-dialog';
import PrintButton from './js/print-button';
import SaveLink from './js/save-link';
import TimeoutButton from './js/timeout-button';
import CookieBanner from './js/cookie-banner';

Rollup cannot resolve common.mjs, or any of the polyfills which I am importing in the custom modules (eg cookie-banner) as they do not appear in the package.json exports block (I assume).
I'm working on a branch of an internal project, but I'll set up a small public repo with an example if it helps.
Thanks

I've setup a small repo with an example project, it won't build, but if you go into the node_modules folder and delete the exports property from the govuk-frontend package.json it will build fine. Of course there's probably a way to work around this, but I dunno what it is yet. A solution vaugely formed in my mind but then I immediately forgot what it was, maybe it'll come back to me tomorrow. Thanks again.

Hey @gunjam, thanks for investigating, and taking the time to set up a nice example.
This is intended behaviour - importing from common and our polyfills wasn't something we intentionally provided, and we wouldn't encourage importing from our source code folders.
In fact, as part of our work to update our browser support and fix up some of our JavaScript, we'll likely be proposing some changes to polyfills, which would affect your project. We'll put out a more detailed proposal of our changes for feedback soon.

Oh I see! Since I was @d in this thread I assumed it was related to my previous comment.

Hi @gunjam - you may be interested in this proposal, as it will affect polyfills: https://github.com/alphagov/govuk-frontend/discussions/2607


🔧 [Refactor] Multicreation - instead of EMail! have not confirmed

🔧 Refactor ticket

Multicreation - instead of EMail! have not confirmed or any similar text describing the actual thing that is the problem.
Filter them out in the backend, no need to present them in this dialog

I can't find where this is done!


Example: Docker on AWS

Add missing information to README:

Specify minimum requirements (CPUs, RAM, storage) to run it on Amazon's EC2 instances
Take care of special requirements (reformatting any volumes? mount stuff?)

Co-assigning myself (why can't I assign 2 people? Pff).

Ultimate goal for README:

step-by-step guide

@pbelmann Are there any more steps we need to describe, to guide people how to run in on an EC2 instance? We should at least state memory and storage requirements, and possibly even provide a detailed walkthrough.

max HDD 82.55448 GB
max MEM 134.3495 GB
I try build a plot out of my log data for memory consumption.
I will provide a PR for the guide.

Perfect, thanks! :+1:

The mem value was retrieved by using cAdvisor.
CAdvisor returns a value that is composed of cached disk space as well as used space.
This is correct but can lead to a misunderstanding as stated in this issue: https://github.com/docker/docker/issues/10824
The value (used space - cache) for this pipeline is: 88.95996 GB .


Add a way to extend server middlewares + access server context from modules

What is the motivation for adding / enhancing this feature?

Currently, there is no way to access server context from modules - either add Express middlewares.
The Vue.prototype.$ssrRequestContext is a pretty powerful tool:
    const context = {
      url: req.url,
      output: {
        prepend: (context) => { return '' }, // these functions can be replaced in the Vue components to append or prepend some content AFTER all other things are rendered. So in this function You may call: output.prepend() { return context.renderStyles() } to attach styles
        append: (context) => { return '' },
        appendHead: (context) => { return '' },
        template: 'default',
        cacheTags: null
      },
      server: {
        app: app,
        response: res,
        request: req
      },
      meta: null,
      vs: {
        config: config,
        storeCode: req.header('x-vs-store-code') ? req.header('x-vs-store-code') : process.env.STORE_CODE
      }
    }

The server section is all ExpressJS. So you can easily add middlewares to context.server.app or add response headers to context.server.response.
Would be great to have some access to this object from inside modules. Of course accessing it makes only sense when isServer is true.

some news about this ?

I've assigned this one to both of you @filrak and  @andrzejewsky as it's related to new modules architecture merged in two weeks ago
The goal is to have the ability to add the express.js middlewares - BUT with support to ES6 and ll the vuex modules :)
It shouldn't be so hard as the context.server..app is just the express.js app and it's passed from core/server to the vue.js app

I'll talk to @andrzejewsky about this. It's actually a part of new modules API rfc https://github.com/DivanteLtd/vue-storefront/issues/3144#issue-460588876

@AGPDev on it ;)

Temporarily done with https://github.com/DivanteLtd/vue-storefront/pull/3518 - can be extended in the future


pin Connection

Fixes #45.

Note this requires Rust 1.39.

Nightly builds are failing due to errors like
error: `extern` fn uses type `Config`, which is not FFI-safe

   --> src/ffi.rs:81:50

    |

81  | pub extern fn quiche_config_new(version: u32) -> *mut Config {

    |                                                  ^^^^^^^^^^^ not FFI-safe

    |

    = note: `-D improper-ctypes` implied by `-D warnings`

    = help: consider adding a `#[repr(C)]` or `#[repr(transparent)]` attribute to this struct

    = note: this struct has unspecified layout

note: type defined here

   --> src/lib.rs:372:1

Looks like it's just the newer rust nightly, as master also fails :/

https://github.com/cloudflare/quiche/pull/251 should "fix" it.

Added some more context to the commit message.


Print Filename and number

Currently logger is not outputing filename and number. It looks like it is limitation.
log.SetOutput(&lumberjack.Logger{
Filename:   "/tmp/sample.log",
MaxSize:    500, // megabytes
MaxBackups: 3,
MaxAge:     28,   // days
Compress:   true, // disabled by default
})
output:
2020/09/23 13:35:12 main started
2020/09/23 13:35:12 webserver2 started

The lumberjack logger doesn't control what data it writes out. That's up to the logger.  Think of lumberjack as just a wrapper for a file.  In this case, it's the log.Logger that would need to output file and line numbers.

Try this out and see if it works.
Outside of main, declare your log variable.
var errLog *log.Logger
Inside main:
e, err := os.OpenFile("./foo.log", os.O_WRONLY|os.O_CREATE|os.O_APPEND, 0666)
if err != nil {
    fmt.Printf("error opening file: %v", err)
    os.Exit(1)
}
errLog = log.New(e, "", log.Ldate|log.Ltime)
errLog.SetOutput(&lumberjack.Logger{
    Filename:   "./foo.log",
    MaxSize:    1,  // megabytes after which new file is created
    MaxBackups: 3,  // number of backups
    MaxAge:     28, //days
})

if you do
errLog.Print("Print something.")


Breaking up spec/TCK to remove circular dependencies

A long standing issue is that we references to downstream specifications like Servlet, Transactions, etc. A summary of the issues can be found in the following Jakarta EE 11 issue:
https://dev.azure.com/jakarta-ee-azdo/jakarta-ee-azdo/_workitems/edit/98
The most correct thing is to break up the specification and TCKs into separate repos that layer the dependencies. This is something that is being done for MP-JWT to allow separation on the Jakarta dependencies.
The simplest thing todo is simply separate the TCK into finer grain artifacts that also layer the dependencies.
The only problem with this is that ideally a TCK that describes requirements for CDI/Servlet integration would be released as part of the Serlvet specification ballot.

I would like to point out one thing: in CDI, the spec and the TCK are already broken apart. The CDI spec depends only on projects that are "below" CDI (Jakarta Annotations, Jakarta Interceptors, Jakarta Dependency Injection, Jakarta Expression Language).
Further, the CDI TCK is also broken apart: there are some supplementary modules, the CDI Lang Model TCK (which is not interesting here), and 2 main TCK modules:

impl, which contains tests for Core CDI and CDI SE and only depends on projects that are "below" CDI,
web, which contains tests for CDI EE and depends also on projects that are "above" CDI.

So technically, we could release CDI early and CDI TCK late. That probably breaks some rules, so another option, probably a path of least resistance, is to break out the web module into something like cdi-tck-ee. Then, CDI and CDI TCK would be released early, and CDI TCK EE would be released late. Would something like that work?
I generally agree that if CDI is truly a corner stone of Jakarta EE, then it should be the projects "above" CDI who specify how they integrate with CDI, but historically, there hasn't been a lot of enthusiasm for doing that.

Scott's proposal

Take the current CDI spec and break it up into

"integration spec" this is where behaviors relative to other
Jakarta EE specs, downstream dependencies, are specified. It is
an integration spec because it is a spec that covers the
integration between CDI and everything else.

"CDI implementation spec" the rest of the spec after the
integrations have been taken out.

TCK

the integration spec will have its own TCK.

CDI implementation spec will have its own TCK.

There will be no shared tests between these two TCKs.

Jakarta EE Core profile will only reference "CDI implementation spec".

Jakarta EE Web and Platform will reference "integration spec" and
"CDI implementation spec".

What about the POMs for the TCKs?
Consider these.

web/pom.xml
We plan to pull the web/pom.xml out of the CDI TCK distribution
and put it into a new artifact associated with the "integration
spec".

impl/pom.xml

lang-model/pom.xml
These will be in the TCK for "CDI implementation spec".

What about the waves?
"integration spec" will be in wave 7
"CDI implementation spec" will be in wave 3

So technically, we could release CDI early and CDI TCK late. That probably breaks some rules, so another option, probably a path of least resistance, is to break out the web module into something like cdi-tck-ee. Then, CDI and CDI TCK would be released early, and CDI TCK EE would be released late. Would something like that work?

Yes, this breaks the current IP flow of the Jakarta specification process where the voting happens on the spec and TCK. As you point out, it really should not take much work to simply break the CDI spec into a base and integration spec with attendant TCKs that would produce two clear spec/TCK bundles that follow the specification process rules.

I see. Given that I'm skeptical about other specs adopting the CDI integration concerns, I think moving the CDI EE spec out CDI itself into another specification called "CDI EE" would be easiest. On the TCK front, that basically amounts to moving the web module into a TCK of the new spec.
Why would I call it "CDI EE"? Because that's how it called today. The less changes, the better :-)

It won't be outside of the CDI project, it will simply be another specification like dependency injection managed by the CDI specification project. A CDI EE + current web submodule of existing TCK would be the contents as you are saying.

Hello @starksm64 and @Ladicek. Based on this comment:

Why would I call it "CDI EE"? Because that's how it called today. The less changes, the better :-)

Can you please confirm:

What I called "CDI integration spec" will be called "Jakarta Contexts and Dependency Injection Enterprise Edition (Jakarta CDI EE)".
What I called "CDI implementation spec" will be called "Jakarta  Contexts and Dependency Injection Enterprise Edition (Jakarta CDI)".

I highlighted the Platform level component spec integration tests in the current CDI TCK Web Impl above and list them here again for clarification:

Jakarta Messaging
Jakarta Connectors

Another solution is to move the CDI EE part to either web profile or platform spec and then put the tcks in the respective repo and CDI team owns the tests. In this way, there won't be individual -ee specs, which might double the spec sizes for no apparent content addition. It will be nicer to have the umbrella spec contains the spec interactions.

A little confused about the CDI EE, why not move the CDI and spec integration to the certain spec.

For example, Original CDI Servlet support in CDI 4.0, move it to Servlet, add a CDI support section in Servlet spec. If possible provide a new module under servlet for CDI- jakarta.servlet.cdi.
Faces, Jaxrs can split the Injection Provider SPI and implementation, and provide default implementation by CDI, in Jakarta EE environment, the injection is enabled by CDI,  in Spring etc,(no CDI implementation in the classpath), it can be provided by Spring.
For those specs integrated CDI tightly, CDI is part of the deps.

Thus we only have a CDI spec, can run pure Java or Jakarta EE Container, can be a direct dep for other specs(or its CDI module).

Feel free to ask the Servlet spec if they want to own the CDI integration concerns :-)
Hint: they already indicated in the past that they don't, see e.g. https://github.com/jakartaee/servlet/issues/116 or https://issues.redhat.com/browse/CDI-492

@arjan tijms @.***> is going to ask on the servlet dev
list. The issue in the past has been that the servlet core team was not
interested in CDI integration, and so this really is an EE platform
integration issue that should be done in a separate spec to avoid
dependency issues. For now this is happening in CDI EE. In the future it
could be a Web Profile integration spec.
On Wed, Oct 25, 2023 at 1:38 AM Ladislav Thon @.***>
wrote:

Feel free to ask the Servlet spec if they want to own the CDI integration
concerns :-)
Hint: they already indicated in the past that they don't, see e.g.
jakartaee/servlet#116 https://github.com/jakartaee/servlet/issues/116
or https://issues.redhat.com/browse/CDI-492
—
Reply to this email directly, view it on GitHub
https://github.com/jakartaee/cdi/issues/687#issuecomment-1778688935, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AACRDMTL2GNWU742RKYLHM3YBC6XZAVCNFSM6AAAAAA2QFMNNGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONZYGY4DQOJTGU
.
You are receiving this because you were mentioned.Message ID:
@.***>

So the restructuring review ballot to move the integration contents into a new CDI EE spec failed the spec committee ballot due to question about whether this was a general approach all specs should take. What has been decided as the approach for EE 11 is to have integration requirements move into the corresponding platform spec or profile. A new restructuring review ballot for this change will kick off this week.

I would frankly prefer CDI EE over putting things into the platform spec, because of clear ownership. But I won't lose sleep over it :-)

I have incorporated the latest on this matter into the EE 11 release plan. I seek your review at https://github.com/jakartaee/platform/pull/808 @Ladicek @starksm64 .

The bulk of the work on the CDI component spec project side is done with:
https://github.com/jakartaee/cdi/pull/755
https://github.com/jakartaee/cdi-tck/pull/532
There will still be work needed to complete the integration of the CDI EE requirements into the platform as part of this PR:
https://github.com/jakartaee/platform/pull/838


Add SyslogIdentifier for systemd service

So the service output can be properly identified in syslog

There was an spec error in my environment, not related to my change as it seems...

@lazyfrosch thanks for the addition, nice idea. I've fixed up the issue with the tests in Travis in master but I've run this locally. It needed one minor change to the tests and all looks good. Cheers


fix: debug build

This was failing with e.g.
ecc_lookup_relation.cpp:(.text.startup[_ZN7plookup10fixed_base5table34fixed_base_table_offset_generatorsE]+0x39): undefined reference to `barretenberg::group_elements::affine_element<barretenberg::field<barretenberg::Bn254FrParams>, barretenberg::field<barretenberg::Bn254FqParams>, grumpkin::GrumpkinG1Params> plookup::fixed_base::table::generate_generator_offset<128ul>(barretenberg::group_elements::affine_element<barretenberg::field<barretenberg::Bn254FrParams>, barretenberg::field<barretenberg::Bn254FqParams>, grumpkin::GrumpkinG1Params> const&)'

I'm not entirely sure why - but static arrays should be initialized in compilation units anyway.

Benchmark results
No metrics with a significant change found.

Detailed results
All benchmarks are run on txs on the Benchmarking contract on the repository. Each tx consists of a batch call  to create_note and increment_balance, which guarantees that each tx has a private call, a nested private call, a public call, and a nested public call, as well as an emitted private note, an unencrypted log, and public storage read and write.
This benchmark source data is available in JSON format on S3 here.
Values are compared against data from master at commit ec2b805e and shown if the difference exceeds 1%.
L2 block published to L1
Each column represents the number of txs on an L2 block published to L1.

Metric
8 txs
32 txs
128 txs

l1_rollup_calldata_size_in_bytes
45,444
179,588
716,132

l1_rollup_calldata_gas
222,996
867,800
3,449,924

l1_rollup_execution_gas
842,083
3,594,908
22,205,293

l2_block_processing_time_in_ms
2,016
7,625
29,798 (-2%)

note_successful_decrypting_time_in_ms
294
871 (-1%)
3,183 (-2%)

note_trial_decrypting_time_in_ms
95.3 (-2%)
81.4 (-7%)
132 (-1%)

l2_block_building_time_in_ms
13,343
52,438 (-1%)
210,094

l2_block_rollup_simulation_time_in_ms
11,986
47,110 (-1%)
189,000

l2_block_public_tx_process_time_in_ms
1,314 (-1%)
5,199
20,598

L2 chain processing
Each column represents the number of blocks on the L2 chain where each block has 16 txs.

Metric
5 blocks
10 blocks

node_history_sync_time_in_ms
22,409 (+2%)
43,034 (+2%)

note_history_successful_decrypting_time_in_ms
2,099 (+4%)
4,104 (+5%)

note_history_trial_decrypting_time_in_ms
122 (+1%)
148 (+4%)

node_database_size_in_bytes
1,631,005
1,099,282

pxe_database_size_in_bytes
29,748
59,307

Circuits stats
Stats on running time and I/O sizes collected for every circuit run across all benchmarks.

Circuit
circuit_simulation_time_in_ms
circuit_input_size_in_bytes
circuit_output_size_in_bytes

private-kernel-init
762
61,697
18,905

private-kernel-ordering
125
24,297
8,153

base-rollup
1,768
656,311
814

root-rollup
173 (+2%)
4,072
1,097

private-kernel-inner
786
81,568
18,905

public-kernel-private-input
41.3 (+1%)
41,519
18,841

public-kernel-non-first-iteration
26.0 (+1%)
41,497
18,841

merge-rollup
15.2
2,592
873

Miscellaneous
Transaction sizes based on how many contracts are deployed in the tx.

Metric
0 deployed contracts
1 deployed contracts

tx_size_in_bytes
8,787
27,547


Undefined index

Issue description:
Hey @aristath,
I'm getting the following error using 3.0.10 and also with the latest dev branch having debug mode activated:

Version used:
latest dev & 3.0.10
Using theme_mods or options?
Code to reproduce the issue (config + field(s))

can you post the code of your field please?

I guess this is not triggered by a specific field but I may be wrong.

PS: this just shows up for like a second, then the customizer is loaded properly.

This is weird...
I can't replicate it.
I make sure there's a language defined in https://github.com/aristath/kirki/blob/3.0.10/field/class-kirki-field-code.php#L39-L43 which runs before the Kirki_Control_Code class. So this should not be happening...
However I just pushed a commit that adds an extra fix there for sanity's sake.
It should be ok now in the dev branch 👍

Confiremd. Works with the latest dev branch :) Thanks!


fix: Teleport - checking funds visual bug

PR Type

[x] Bugfix
[ ] Feature
[ ] Refactoring

Context

[x] Closes #9193

Needs QA check

@kodadot/qa-guild please review

@prury  also check the main buttin text

Did your issue had any of the "$" label on it?

[x] Fill up your DOT address: Payout

Screenshot 📸

[x] My fix has changed something on UI;

https://github.com/kodadot/nft-gallery/assets/44554284/16afb271-5a96-4348-bee7-b53dae5287a0

😍 Perfect, I’ve sent the payout
💵 $20 @ 6.64 USD/DOT ~ 3.012 $DOT
🧗 16faLfsywwNATaEfbH2ah75dn6ZmctQWpMS5G4KFhbmj5hnD
🔗 0x9c4f0f866b5f9c6fefad4bcd9df8019ad3f90c5c58bcd11882ce51bef7bd86b4
🪅 Let’s grab another issue and get rewarded!
🪄 github.com/kodadot/nft-gallery/issues


inference_detector error

When I use inference_detector to try PETR, tensor shape error is caused like this:
RuntimeError: Expected 4-dimensional input for 4-dimensional weight [64, 3, 7, 7], but got 3-dimensional input of size [3, 800, 1067] instead
How to fix this?

Here, data['img'] is not cast to DataContainer.
https://github.com/hikvision-research/opera/blob/33ec0771f2040dabc98512550a17475cffec85c2/opera/apis/inference.py#L196

I investigated this problem.
This is caused by replace_ImageToTensor in mmdetection.
replace_ImageToTensor doesn't deal with mmdet.ImageToTensor.
https://github.com/hikvision-research/opera/blob/33ec0771f2040dabc98512550a17475cffec85c2/opera/apis/inference.py#L180

Thanks for your suggestion. We have fixed this issue and you can use inference_detector to try PETR now.


Update pygithub to v1.43.1

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


PHVideoCaptureBridge: Submit frames on WebRTC thread

Thread affinity checks were introduced in:
https://chromium.googlesource.com/external/webrtc/+/e07710cc91b3dccd7fea7df3d99c304f419babda
so we can no longer submit frames from the AVFoundation thread.
In debug builds, it will result in an assertion. It’s a shame we have to fling things between threads, since AVFoundation already does all the queueing for us, but such is life.
This fix was essentially lifted from:
talk/app/webrtc/objc/avfoundationvideocapturer.mm

@ikonst Thanks very much for this fix! It is definitely a shame to have to bounce incoming frames over to the capturer's WebRTC thread, but it sounds like you are correct. This is what I get for not testing against a debug build for r8444.
Assigning myself as the reviewer.

@ikonst I reviewed the fix, and everything appears to be in order. Initially, I was concerned about thread safety with the capturer's temporary conversion buffer, but then realized that rtc::Thread's Invoke method is synchronous.
Ideally, once WebRTC supports passing wrapped CVPixelBufferRefs to the downstream components it would be as simple as retaining the buffer and asynchronously notifying the capturer thread rather than blocking here.


Automatically start the debug session when test or debug is pressed

After the debug or test session is started, dlv requires that you all continue to start to session.  I find it pretty useful to automatically trigger the continue operation (we go from two button clicks two one per each test / debug cycle).

Good feedback on that as well! I have updated my PR with your changes (minus a rogue semicolon).  Been playing around with this change and it's great.


adds drawings

I'm gonna just merge these. I don't have the brain space right now to work on a proper pr.


fix: no longer prompt for values provided in args

Pull Request Test Coverage Report for Build 648847455

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 648844746:
0.0%

Covered Lines:
1

Relevant Lines:
1

💛  - Coveralls


DeprecationWarning: The punycode module is deprecated

I am trying to run the code in starter tutorial:
The code is in a file called IndexService.ts, and kb.txt is in the same directory of this file.
import fs from "fs/promises";
import { Document, VectorStoreIndex } from "llamaindex";
async function main() {
// Load essay from abramov.txt in Node
const essay = await fs.readFile(
"kb.txt",
"utf-8",
);
// Create Document object with essay
const document = new Document({ text: essay });
// Split text and create embeddings. Store them in a VectorStoreIndex
const index = await VectorStoreIndex.fromDocuments([document]);
// Query the index
const queryEngine = index.asQueryEngine();
const response = await queryEngine.query(
"What are the payment plans for AI Business Coach?",
);
// Output response
console.log(response.toString());
}
main().catch(console.error);
when running "npx ts-node IndexService.ts", it gave me the error "(node:37856) [DEP0040] DeprecationWarning: The punycode module is deprecated. Please use a userland alternative instead.
(Use node --trace-deprecation ... to show where the warning was created)"
How do I fix it? Thank you!

Which version of Node are you on?

Which version of Node are you on?

npm -v
10.2.4
node -v
v21.2.0
What do you suggest?

Can you try Node 20 and see if it fixes it? We generally test against LTS
versions but I’ll also take a look if I can reproduce it on Node 21 on my
end.
On Wed, Nov 22, 2023 at 8:10 PM minnahu23 @.***> wrote:

Which version of Node are you on?
npm -v
10.2.4
node -v
v21.2.0
What do you suggest?
—
Reply to this email directly, view it on GitHub
https://github.com/run-llama/LlamaIndexTS/issues/222#issuecomment-1823799645,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJHHYVPIYIDOXD2QPIOM2TYF3EDNAVCNFSM6AAAAAA7VKRCY2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMRTG44TSNRUGU
.
You are receiving this because you commented.Message ID:
@.***>

Can you try Node 20 and see if it fixes it? We generally test against LTS versions but I’ll also take a look if I can reproduce it on Node 21 on my end.
…
On Wed, Nov 22, 2023 at 8:10 PM minnahu23 @.> wrote: Which version of Node are you on? npm -v 10.2.4 node -v v21.2.0 What do you suggest? — Reply to this email directly, view it on GitHub <#222 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAJHHYVPIYIDOXD2QPIOM2TYF3EDNAVCNFSM6AAAAAA7VKRCY2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMRTG44TSNRUGU . You are receiving this because you commented.Message ID: @.>

Yes, I downgraded to node 20, and also followed the guide on https://github.com/run-llama/LlamaIndexTS, it worked this time.


Support resource requests/limits on checkout and agent containers

agent-stack-k8s allows us to set the resource requests/limits (e.g. cpu and memory) for the controller that launches pods, but does not provide a way to specify those requests/limits for the Buildkite agent pods it launches. Implicitly, you can provide resources for pods launched by the podSpec specified in a step, but not for the pods that the controller launches for checking out the Git repo or for monitoring the pods it launched.
This is especially needed if we are running the commands directly in the agent container (e.g. with no podSpec, just using a regular command step), where our commands could run some more cpu/memory intensive operations (in combination with our own custom agent containers with our own libraries installed). Proper requests/limits will allow us to combine agent-stack-k8s with an autoscaler like Karpenter to dynamically size our Buildkite compute appropriately.
Even better would be supporting different container-level resource limits/requests depending on if the agent is running the command block directly versus just using a podSpec and launching separate containers (where we can provide our own requests/limits). Even better on top of that would be having a concept of default requests/limits for containers specified in a podSpec.

Hi @mbarrien, thanks for raising this. We've planned to add something to set these.
Do you have opinions or a suggestion for how the syntax might look? e.g.
steps:
  - plugins:
      - kubernetes:
          podSpec:
            containers:
              - image: blah/alpine
                command: ["echo", "hello!"]
                resources:
                  requests:
                    cpu: 100m
                    memory: 100Mi
          defaultResources:
            requests:
              cpu: 1000m
              memory: 1Gi

Ideally, I'd have something that can be done at the time I provision the helm chart, rather than having to weave this default resources all throughout every single Kubernetes workflow step. This feels like something that should be handled by an infra/platform team rather than something our application engineers would have to write themselves. This would mirror our current workflow of provisioning those things from the deprecated buildkite agent chart from https://github.com/buildkite/charts
Similarly, I was about to write an issue asking for gitEnvFrom to be something that can be defaulted at Helm install time, for similar reasons.

That's a good point, we'll look into it. If you feel motivated, we'll accept a PR adding a value for default resources to the Helm chart for the controller to use when creating new pods.

This also said, maybe having support for BOTH the Helm chart, and the defaultResources (or defaults: {resources: ...}}) would be useful, in case we do want to override the underlying default values provisioned in Helm for specific steps.
Would be open to implementing the PR, but cannot commit to it right now given other work.

Hey y'all; I stumbled on this issue while looking for something else and I just wanted to throw a potential solution on here really quick.
Kubernetes already allows for settings defaults for containers and pods inside of a namespace, it could absolutely be added to the helm chart but even without it this can be accomplished super easily
https://kubernetes.io/docs/tasks/administer-cluster/manage-resources/
apiVersion: v1
kind: LimitRange
metadata:
  name: resource-ranges
spec:
  limits:
    - default:
        memory: 1000Mi
        cpu: 1000m
      defaultRequest:
        memory: 600Mi
        cpu: 500m
      max:
        memory: 6000Mi
        cpu: 4000m
      type: Container

kubectl -n <buildkite namespace> apply -f <path to the above yaml>

Hi all, the pull request https://github.com/buildkite/agent-stack-k8s/pull/262 will allow you to customize any containers


Allowing investigation doc to be updated on incident data change.

Allows the investigation document to be updated whenever various incident attributes change.

I'm going to close this for now as it's stale. Going to see if there are better approaches for keeping dispatch/google-docs in sync.

If this feature gets interesting again, just wanted to add a shout-out for using Google Spreadsheets (if we stick with GSuite). Adds the ability to address and modify specific fields, and we could make it look more or less like the investigation doc does today. Seems like Google Docs isn't gonna add this.


Multimethods for the Linear Algebra module

I've picked up where @prasunanand left off in https://github.com/Quansight-Labs/unumpy/pull/48 by adding additional multimethods + tests for the Linear Algebra module (linalg). These include:

linalg.multi_dot
linalg.matrix_power
linalg.solve
linalg.tensorsolve
linalg.lstsq
linalg.inv
linalg.pinv
linalg.tensorinv

Note: Adding some default implementations may be relevant here.

I'd add defaults to those that are simple to do here. For the more complicated ones, leave them out.

I'll keep adding more.

A note: Correctness is better than completeness here. If a kwarg isn't supported, raise a BackendNotImplementedError.

The default implementation for norm was removed and it will be used in a future PR for adding tests that compare its results to NumPy's norm. This is intended as a testbed for creating robust defaults by testing them on corner cases. I'll open an issue for this.


chore(deps): upgrade dev dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-dev-dependencies-2.x" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 1826

Questions ?
Please refer to the Backport tool documentation


Ubuntu 16.04 installation woes

I don't have much experience with Ruby, any pointers would be helpful. I can see how dryrun can be extremely helpful, I just need to get it up and running. Thank you for your wonderful contribution. I have already installed alfi, international and lasertag.
I'm trying to install dryrun on my Ubuntu PC but I couldn't.
When I do a sudo gem install dryrun
I get this,
Building native extensions.  This could take a while...
ERROR:  Error installing dryrun:
    ERROR: Failed to build gem native extension.

    current directory: /var/lib/gems/2.3.0/gems/rjb-1.5.4/ext
/usr/bin/ruby2.3 -r ./siteconf20160523-23370-6ujxs4.rb extconf.rb
*** extconf.rb failed ***
Could not create Makefile due to some reason, probably lack of necessary
libraries and/or headers.  Check the mkmf.log file for more details.  You may
need configuration options.

Provided configuration options:
    --with-opt-dir
    --without-opt-dir
    --with-opt-include
    --without-opt-include=${opt-dir}/include
    --with-opt-lib
    --without-opt-lib=${opt-dir}/lib
    --with-make-prog
    --without-make-prog
    --srcdir=.
    --curdir
    --ruby=/usr/bin/$(RUBY_BASE_NAME)2.3
extconf.rb:53:in `<main>': JAVA_HOME is not set. (RuntimeError)

extconf failed, exit code 1

Gem files will remain installed in /var/lib/gems/2.3.0/gems/rjb-1.5.4 for inspection.
Results logged to /var/lib/gems/2.3.0/extensions/x86_64-linux/2.3.0/rjb-1.5.4/gem_make.out

I took a look at the logged results and then I found the following information,
current directory: /var/lib/gems/2.3.0/gems/rjb-1.5.4/ext
/usr/bin/ruby2.3 -r ./siteconf20160523-23370-6ujxs4.rb extconf.rb
*** extconf.rb failed ***
Could not create Makefile due to some reason, probably lack of necessary
libraries and/or headers.  Check the mkmf.log file for more details.  You may
need configuration options.

Provided configuration options:
    --with-opt-dir
    --without-opt-dir
    --with-opt-include
    --without-opt-include=${opt-dir}/include
    --with-opt-lib
    --without-opt-lib=${opt-dir}/lib
    --with-make-prog
    --without-make-prog
    --srcdir=.
    --curdir
    --ruby=/usr/bin/$(RUBY_BASE_NAME)2.3
extconf.rb:53:in `<main>': JAVA_HOME is not set. (RuntimeError)

extconf failed, exit code 1

The error says JAVA_HOME is not set, but when I echo the path, it works.
echo $JAVA_HOME returns /usr/lib/jvm/java-8-oracle
My ruby version is ruby 2.3.0p0 (2015-12-25) [x86_64-linux-gnu]
Let me know if you need more information. Thanks again.

Hey man! Thanks a lot for your compliments 👍
Glad to hear that my libs are being useful.

Are you sure that that's really your home path? look at mine:
$ echo $JAVA_HOME
/Library/Java/JavaVirtualMachines/jdk1.8.0_72.jdk/Contents/Home

Take a look at this: https://github.com/arton/rjb/issues/40

@cesarferreira I managed to install rjb on Ubuntu by following this answer on SO. Should we keep this open until the rjb issue is resolved? Someone could find it useful.

I agree with you @ragunathjawahar, thanks 👍

This is a good answer that works for me stackoverflow
The answer is
In the console just type these (remember to change to your current location)
export ANDROID_HOME=$HOME/Android/Sdk

I have faced the same issue and this answer fix it for me
stackoverflow
The answer is
This is because JAVA_HOME is getting reset in the sudo mode. To fix it, open your /etc/sudoers file add the following line and save it.
Defaults   env_keep += "JAVA_HOME"
now reopen the terminal and install the gem


Link for Discord server

Added a link to the KnoxDevs Discord server.

This request will resolve #27.

🦗

The invite link to the KnoxDevs Discord has been changed to https://discord.gg/TMNSt3KuUS. This Pull Request needs to be updated with the new Discord link.


mimeo: 2017.6.6 -> 2018.11

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/mimeo/versions.
meta.description for mimeo is: '"Open files by MIME-type or file name using regular expressions"'.

Checks done (click to expand)

built on NixOS
/nix/store/6422ad52kv317v4xypshgafkl9ygk5w3-mimeo-2018.11/bin/.mimeo-wrapped passed the binary check.
/nix/store/6422ad52kv317v4xypshgafkl9ygk5w3-mimeo-2018.11/bin/mimeo passed the binary check.
2 of 2 passed binary check by having a zero exit code.
0 of 2 passed binary check by having the new version present in output.
found 2018.11 with grep in /nix/store/6422ad52kv317v4xypshgafkl9ygk5w3-mimeo-2018.11
directory tree listing: https://gist.github.com/27bf530a16b0dafe1eb085f45c169ee5
du listing: https://gist.github.com/6beb10b1578864a6cf08f8ea50d831f8

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)
1 package rebuild(s)
1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)
First fifty rebuilds by attrpath
mimeo

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/6422ad52kv317v4xypshgafkl9ygk5w3-mimeo-2018.11 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
Or, build yourself:
nix-build -A mimeo https://github.com/r-ryantm/nixpkgs/archive/1b35c07bd04eaaaf2c59f5063fb5fe2d4391327d.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/6422ad52kv317v4xypshgafkl9ygk5w3-mimeo-2018.11
ls -la /nix/store/6422ad52kv317v4xypshgafkl9ygk5w3-mimeo-2018.11/bin

cc @rycee for testing.

Rebased to master in 9d4cc31a169be4ad112b32702299276dbbdbfa86.


Dart

There was some Dart integration posted about on Reddit a few days ago

https://github.com/mqnfred/dustr


idea: add toppy, use min p

Toppy's a great 7B model - the best, in my opinion, and many others have also loved it for RP.
Aside from that, Min P is a sampler implemented in every open source LLM backend. (except transformers)

You can install the model yourself by putting it in the models/LLM folder and creating your own model config. Last time I checked, Min P hasn't been implemented to the main koboldcpp release package yet. Let me know if that has changed.

You can install the model yourself by putting it in the models/LLM folder and creating your own model config. Last time I checked, Min P hasn't been implemented to the main koboldcpp release package yet. Let me know if that has changed.

..when did you last check? they added min p on november 4

also, i meant adding a config for toppy, as its the most used and most praised 7B iirc based on mistral for rp


Release taskcat [0.9.3]

5e94239 Bump Version - Creating a new minor version
1729fe1 Simplify travis logic based on tags
1ffc257 Bump Version - Creating a new minor version
0114603 Updating Travis regex; closes #370
8e608e2 additional tests
b6be515 remove pyfiglet dependency
8e49abb Bump Version - Creating a new minor version
aca9c22 Adding skip_cleanup
f2cc0d4 Fixing if-statement in travis config
f840e02 add flag to keep only failed stacks
849a17f support legacy global overrides from ~/.aws/taskcat_global_override.json
5059c89 allow undefined parameters section in test. Fixes #355
46c73a1 Updating TravisCI Config to reflect build pipeline desired state
d6d3572 Add support for floating point parameters
473e5fa additional tests for Config
2df524d additional tests for Boto3Cache

Codecov Report

Merging #374 into master will decrease coverage by 0.03%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #374      +/-   ##
==========================================
- Coverage   72.55%   72.51%   -0.04%
==========================================
  Files          30       30
  Lines        2700     2700
  Branches      460      460
==========================================
- Hits         1959     1958       -1
  Misses        646      646
- Partials       95       96       +1

Impacted Files
Coverage Δ

taskcat/_lambda_build.py
85.24% <0%> (-1.64%)
:arrow_down:

Continue to review full report at Codecov.

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

/do-e2e-tests


[graphicsmagick] fix Magick++.h header location.

This pull request is to correct a header location for graphicsmagick. The issue was discovered when I enabled the Navigation 2 stack on Windows. The Magick++.h is expected to be placed one level up in the folder layout. Here is a example of the header layout in Ubuntu package: https://packages.ubuntu.com/bionic/amd64/libgraphicsmagick++1-dev/filelist.

This is ready for review and merge. Thanks!

@seanyen, thanks for the PR!
Could you also update the version to '1.3.35-1' in CONTROL file?

@PhoebeHui Done!

Thanks for the PR!


an expanded watch variable collapses when changing

I'm guessing the reference changes, the scene explorer window collapses it as it changes.
Scenario - was looking at ToolController, NetTool, NetToolControlPoints (there's 3 of them).  Expanded them, and then started building a curve road (3 control points).  Set down the first control point, then as the mouse is moved, the second watched NetControlPoint collapses, so I can't see it's contents.
You can move the mouse over to re-click the expand button, but that mouse movement is constantly changing the 2nd control point :)
Anyhow, keeping it open when the object it points to changes would help.
Plus most awesome mod!  Spending more time with it than the game right now.

Hm, good point.

Ok, this took a bit longer than expected but I have made some big design changes and made this work + fixed some related issues. Commit is here.


eval/evalsha support

get_key_from_command fun doesnt support eval or evalsha redis commands.
Example:

eredis_cluster:get_key_from_command([<<"eval">>, <<"local temp = 1 return temp">>, 1, <<"key">>,<<"value">>]).
"local temp = 1 return temp"
(should return <<"key">>)

Hello paramahamsa, thanks for filing this issue, I will fix it in the next release.

Hello paramahamsa, this issue has been fixed in the version 0.4.1

Great, thank You!
2016-01-11 9:40 GMT+02:00 Adrien Moreau<EMAIL_ADDRESS>
Hello paramahamsa, this issue has been fixed in the version 0.4.1
—
Reply to this email directly or view it on GitHub
https://github.com/adrienmo/eredis_cluster/issues/3#issuecomment-170453844
.


Receiving "Error: Can't walk dependency graph: ENOENT: no such file or directory" when run the test

Current behavior
I am trying to use a cucumber preprocessor with cypress. and I have created a .feature file and a step-definition file. When I run the .feature file I am getting  Error: Can't walk dependency graph: ENOENT: no such file or directory, lstat 'C:\Users\admin\LegrandRX_Cucumber\process'     required by C:\Users\admin\LegrandRX_Cucumber\node_modules\cypress-cucumber-preprocessor\lib\getStepDefinitionsPaths.js
Test code to reproduce
I have added this in my cypress/support/index.js

Here is my cypress.json file.
{
  "reporter": "cypress-mochawesome-reporter",
  "reporterOptions": {
    "reportDir": "cypress/Reports",
    "charts": true,
    "overwrite": false,
    "html": false,
    "json": true,
    "reportPageTitle": "Legrande Cypress",
    "reportFilename": "Legrande Cypress Test Report",
    "embeddedScreenshots": true,
    "inlineAssets": true
  },
  "defaultCommandTimeout": 30000,
  "retries": {
    "runMode": 1,
    "openMode": 1
  },
  "video": false,
  "scrollBehavior": "nearest",
  "testFiles": "**/*.{feature,features}",
  "chromeWebSecurity": false
}

And here is my package.json file.

and here is my .feature file. definition file and folder structure.
I am getting same error for different folder structure.

And

Versions

Cypress version: 9.5.0
Preprocessor version: 4.0.1, 4.3.1
Node version: 16.13.1

I'm not able to reproduce your issue, you're going to have to provide a minimal example that illustrate it and that I can clone.

Hi, @badeball Please close https://github.com/KrupalVaghasiya/Cypress_BDD this repo and run it into your machine. so you will get a better idea.

So, the preprocessor code shown below, goes into cypress/plugins/index.js and not cypress/support/index.js, as per documentation.
const cucumber = require('cypress-cucumber-preprocessor').default

module.exports = (on, config) => {
  on('file:preprocessor', cucumber())
}

@badeball My code is in cypress/plugins/index.js not cypress/support/index.js. sorry, it was my mistake.

You're still doing something wrong and something that's not according to the documentation. Update your repository with your changes and let me see.


Vulnerability roundup 87: ubridge-0.9.18: 1 advisory [5.5]

search, files

[ ] CVE-2020-14976 CVSSv3=5.5 (nixos-unstable)

Scanned versions: nixos-unstable: b3251e04ee4. May contain false positives.
Cc @primeos

Oh, I forgot to close this. The fix is already in 0.9.18 so the CVE references the wrong version. It also wouldn't affect us anyway as we don't set the SUID bit.


Attribute for documentation -help| --help| /help

Hello,
How about that?
[HelpArgs("Documentation....")]
public class ExampleClass
{
    [Required]
    [HelpArgs("StringValue description...")]
    public string StringValue;
    .
    .
    .

Bye.

I need to think this through :+1:  I do agree there is lack of documentation attributes


No API key setting available ( in Intellij IDEA) after upgrading to the version 1.3.2

Hi,
I upgraded the plugin to version 1.3.2, but after the upgrade, it stopped working.
There are two issues:

In Settings -> Tools: There is no CodeGPT field anymore!
When trying to config the API settings by clicking on the link suggested by the plugin in the chat windows, I get the following error:

The Stack trace:
java.lang.AssertionError: Cannot find configurable for specified predicate 	at com.intellij.ide.actions.ShowSettingsUtilImpl.showSettingsDialog(ShowSettingsUtilImpl.java:128) 	at com.intellij.ide.actions.ShowSettingsUtilImpl.showSettingsDialog(ShowSettingsUtilImpl.java:107) 	at com.intellij.ide.actions.ShowSettingsUtilImpl.showSettingsDialog(ShowSettingsUtilImpl.java:99) 	at ee.carlrobert.chatgpt.ide.toolwindow.ToolWindowService$1.mouseClicked(ToolWindowService.java:161) 	at java.desktop/java.awt.Component.processMouseEvent(Component.java:6651) 	at java.desktop/javax.swing.JComponent.processMouseEvent(JComponent.java:3392) 	at java.desktop/java.awt.Component.processEvent(Component.java:6413) 	at java.desktop/java.awt.Container.processEvent(Container.java:2266) 	at java.desktop/java.awt.Component.dispatchEventImpl(Component.java:5022) 	at java.desktop/java.awt.Container.dispatchEventImpl(Container.java:2324) 	at java.desktop/java.awt.Component.dispatchEvent(Component.java:4854) 	at java.desktop/java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4948) 	at java.desktop/java.awt.LightweightDispatcher.processMouseEvent(Container.java:4584) 	at java.desktop/java.awt.LightweightDispatcher.dispatchEvent(Container.java:4516) 	at java.desktop/java.awt.Container.dispatchEventImpl(Container.java:2310) 	at java.desktop/java.awt.Window.dispatchEventImpl(Window.java:2802) 	at java.desktop/java.awt.Component.dispatchEvent(Component.java:4854) 	at java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:781) 	at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:730) 	at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:724) 	at java.base/java.security.AccessController.doPrivileged(AccessController.java:399) 	at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:86) 	at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:97) 	at java.desktop/java.awt.EventQueue$5.run(EventQueue.java:754) 	at java.desktop/java.awt.EventQueue$5.run(EventQueue.java:752) 	at java.base/java.security.AccessController.doPrivileged(AccessController.java:399) 	at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:86) 	at java.desktop/java.awt.EventQueue.dispatchEvent(EventQueue.java:751) 	at com.intellij.ide.IdeEventQueue.defaultDispatchEvent(IdeEventQueue.java:909) 	at com.intellij.ide.IdeEventQueue.dispatchMouseEvent(IdeEventQueue.java:831) 	at com.intellij.ide.IdeEventQueue._dispatchEvent(IdeEventQueue.java:753) 	at com.intellij.ide.IdeEventQueue.lambda$dispatchEvent$5(IdeEventQueue.java:437) 	at com.intellij.openapi.progress.impl.CoreProgressManager.computePrioritized(CoreProgressManager.java:787) 	at com.intellij.ide.IdeEventQueue.lambda$dispatchEvent$6(IdeEventQueue.java:436) 	at com.intellij.openapi.application.TransactionGuardImpl.performActivity(TransactionGuardImpl.java:113) 	at com.intellij.ide.IdeEventQueue.performActivity(IdeEventQueue.java:615) 	at com.intellij.ide.IdeEventQueue.lambda$dispatchEvent$7(IdeEventQueue.java:434) 	at com.intellij.openapi.application.impl.ApplicationImpl.runIntendedWriteActionOnCurrentThread(ApplicationImpl.java:838) 	at com.intellij.ide.IdeEventQueue.dispatchEvent(IdeEventQueue.java:480) 	at java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:207) 	at java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:128) 	at java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:117) 	at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:113) 	at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:105) 	at java.desktop/java.awt.EventDispatchThread.run(EventDispatchThread.java:92)
Would you please let me know what should I do?

Hi @vahidR
Seems to be the same issue as mentioned here.
Could you follow the steps that Mustafa did?
Best regards

Amazing...
I also searched for the CodeGPT in the settings, and another plugin showed up (for me it was Mario Progress Bar).
I deactivated that, restarted the IDE, and voila, everything started to work.
PS. After activating that plugin, the CodeGPT setting vanished again for me. There should be some sort of collision in the settings for these two, IMHO.
Thanks again for your help and keep up the good work :)

Ohh, the SettingsConfigurable id is colliding with the other existing plugins settings(most likely with the ones who used Settings Example as a starter project).
I will change the id to be more unique, thank you!


Slowness on larger files

Type: Bug
Using extension Bisect, I have identified IntelliCode API Usage Examples to be causing slowness issues, primarily in TypeScript files, especially in larger ones.
IntelliSense would take a long time to load after changes
Prettier would take a long time to format
Saving was noticably delayed until all extensions finished
If using Vim extension, editing would be noticeably delayed
Extension version: 0.2.0
VS Code version: Code 1.70.0 (Universal) (da76f93349a72022ca4670c1b84860304616aaa2, 2022-08-04T04:38:55.829Z)
OS version: Darwin x64 21.5.0
Modes:

System Info

Item
Value

CPUs
Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz (16 x 2400)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledwebgl: enabledwebgl2: enabled

Load (avg)
6, 5, 4

Memory (System)
32.00GB (1.66GB free)

Process Argv
--crash-reporter-id ca0dbd96-d70c-4e7a-a40a-0bdf63e6c6be

Screen Reader
no

VM
0%

A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vstes627:30244334
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263cf:30335440
vscoreces:30445986
pythondataviewer:30285071
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30542924
vsaa593cf:30376535
pythonvs932:30410667
wslgetstarted:30449410
cppdebug:30492333
pylanb8912cf:30529770
vsclangdc:30486549
c4g48928:30535728
hb751961:30543456
dsvsc012cf:30540253

Hi @domjancik, thanks a lot for the feedback!
I'm happy to inform you that we have just published a new version with many improvements targeting performance on ts/js large projects.
I will close this issue for now but please feel free to re-open if you still experience performance issues.


Psbex 122

Proxy the legend graphic request if appropriate and add version to call

Oops. I guess I shouldn't be reviewing changes on this repo.


Enhance planner plan get with rosterId

Closes #4401

And another one from @MathijsVerbeeck 😮. You are AWESOME 🤩. We will review it ASAP

I just recognized we are in the release freeze. Will merge the changes next week.

Manually merged.
Thank you


Revert "Disable test which cannot handle two clusters"

Reverts vespa-engine/sample-apps#262
@mpolden

👍


Problem Parsing Complex if-statements

I found Issue #53 , but it did not answer my question. I looked in the documentation, but did not see a solution there either for this type of if-statement.
My issue is that I have "complex" if-statements such as this:
<<if (($var1 > 5 and $var2 < 300) or ($var1 < 6 and $var2 >= 200 and $var2 < 300)) and ($var3 is false and $var4 >= 3 and $var5 < 100)>>[[next node|nextNode]]<>
and the parser seems to get suck on this line in this node when adding the statements to the _statements list and I'm not sure why. I've looked at the parsed text and it parses the whole node just fine from what I can see. This is the first "complex" if-statement I have in my story, and if I change it to an if-statement with no parenthesis, it moves past this node just fine.
I do need if-statements like this, but if there is some other way I should write them, please let me know.

Looking into it!

Thank you for looking into this!
I do have one more question about "weird" if-statement conditions if anyone happens to know:
I would love to be able to use modular (%) as part of an if-statement. Ex: if $var % 3 is 0. However, it seems that modular is not supported.
I could get around this with division, but only if division returns a double/float and not an integer. Does $var / 3 when $var = 4 return an integer (1) or a double/float (1.3333)?
My "last resort" will be to write a function to perform mod for me, but I wanted to try using the built-in tools first.
Thanks!

I'm probably not going to add syntax or features that let you define arbitrary new operators, because Yarn's focus is dialogue and not all-purpose programming, but modulus is a common enough operator that I think it should be included in the core language. I'll add a new issue for it.

Added issue #73 to track this. Please continue any discussion about this in that issue, please! 👍

Modulo operator added in #77. To diagnose your initial issue we'll just need to attempt to reproduce the error on our end. Working on it! We'll let you know how it goes :)

There hasn’t been any activity on this in a while and I believe it is fixed in the 1.1 beta so I am closing this issue.
If the issue reappears please open a new issue.


Add mne-lsl to construct

Adding mne-lsl to the installers.
Should we keep mne-realtime, people mentioned it was not working with the latest version of MNE anyway?

What's the difference between realtime and LSL? Can MNE-LSL replace MNE-realtime for LSL users?

What's the difference between realtime and LSL?

MNE-LSL is a rewrite of much of MNE-Realtime functionality, but built on top of LSL from the start (MNE-Realtime was built around FieldTripBuffer, with limited LSL support added later).

Can MNE-LSL replace MNE-realtime for LSL users?

yes, that is the intent.

It's still a WIP on which I work on when I have the time, but it is functional and already simplifies a lot the interaction with an LSL stream.

Thanks @drammock and @mscheltienne!
I just saw that you were planning to deprecate the MNE-Realtime package anyway, so from my end I have no objections to removing it and adding MNE-LSL to the installer.

mne-realtime should in principle continue to work. Let's keep it for a release or two


Move to doubles for world positions?

Might be a good idea. Making this issue for discussion.

The reasons to use floats are:

If an existing library requires it
If you're doing a lot of GPU calculations with the number
If you need the memory

So I'd say we're 0/3, and there's no reason not to switch

World positions are already floats. The point of the discussion was to move from single precision floats to double precision ones to prevent accuracy loss.

By floats, I meant singles. I forget if C# actually has "single" as an alias for the type.

Oh I misread your comment and didn't notice the not.
Nevermind.

Some things i found during research
Doubles are slower on every platform you'll care about writing games, take twice the memory bandwidth, and have fewer specialized CPU instructions available.

Single-precision floats remain the standard for hardware graphics interfaces, both on the C/C++ side and inside shaders

You'll probably need a double vector at some point, but it should be used when needed, not by default

World coordinates are currently of the type SFML.System.Vector2f.
If we're moving away from SFML that'll have to change anyways - if we're going to switch to double-precision floats that would be the time to do it.

But personally though, you just don't need the precision for doubles and floats are supported with more operations within the GPU.

Alright.


[Bug] How to adjust the yarn queue used by the task

Search before asking

[X] I searched the issues and found no similar issues.

Linkis Component
linkis-commons
What happened + What you expected to happen
怎么调整任务使用的yarn队列?错误信息: 执行sql任务时报1.获取Yarn队列信息异常 或者 用户XX不能提交到队列
How to adjust the yarn queue used by the task? Error message: 1. The Yarn queue information obtained is abnormal or the user XX cannot be submitted to the queue when executing the sql task
Relevent platform
·
Reproduction script
·
Anything else
这个问题来自Linkis社区的QA文档
This question comes from the QA documentation of the Linkis community
QA Doc Link：https://docs.qq.com/doc/DSGZhdnpMV3lTUUxq
Are you willing to submit a PR?

[ ] Yes I am willing to submit a PR!

在前端—管理台—设置—通用设置—Yarn队列 配置登录用户有权限的队列
In the front-end—Administrator—Settings—General Settings—Yarn Queues Configure the queues that the logged-in user has permission to


Alt headless select implementation

What is it?

[x] Feature / enhancement
[ ] Bug
[ ] Docs / tests

Description
This is an alternate implementation for headless Select with a demo which includes some minimal styling.
This implementation largely draws from Radix UI's usage model as well as Open UI's selectmenu prototype.
Screenshots/Demo
Demo is added to /headless/select/ path, viewable after running npx nx start website.
Checklist:

[x] My code follows the developer guidelines of this project
[x] I have performed a self-review of my own code
[x] I have made corresponding changes to the documentation
[ ] Added new tests to cover the fix / functionality

I have read the CLA Document and I hereby sign the CLA

thanks @shiroinegai !
Can I merge this PR? or do you still work on it?
(BTW, there are a couple of conflicts to resolve before it can be merged)

I'm still actively working on it (right now, actually!). Is this implementation going to replace the existing Select? If so, I'll be renaming the export and put it into the new documentation page.

Hey @shairez , I think I have resolved the conflicts and this current commit is in the exact same state as you saw from yesterday's meeting. I'm still trying to implement the rest of the necessary behaviour but you can merge this PR for now.

great work @shiroinegai 👏
can you add the docs example in the daisy folder -> qwik-ui/packages/website/src/routes/docs/daisy/... please?

Will do!


Indirect development in animals

Description
This includes a few changes to do with animals that undergo indirect developmental, proceeding through a metamorphic process where their functional group changes, such as from caterpillar to butterfly.
Included:
Animal traits for: development type (direct vs indirect), development status (adult vs larval), and the functional group that is produced by the current functional group through either birth or metamorphosis. This also adds a non-reproductive reproductive type for larval functional groups.
The main methods included are metamorphose and metamorphose_community, creating the change and processing the change over the entire community, respectively.
Fixes # (issue)
Type of change

[x] New feature (non-breaking change which adds functionality)
[ ] Optimization (back-end change that speeds up the code)
[ ] Bug fix (non-breaking change which fixes an issue)

Key checklist

[x] Make sure you've run the pre-commit checks: $ pre-commit run -a
[x] All tests pass: $ poetry run pytest

Further checks

[x] Code is commented, particularly in hard-to-understand areas
[x] Tests added that prove fix is effective or that feature works

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 94.66%. Comparing base (efd0b7f) to head (653c175).

Additional details and impacted files
@@             Coverage Diff             @@
##           develop     #450      +/-   ##
===========================================
+ Coverage    94.61%   94.66%   +0.05%
===========================================
  Files           70       70
  Lines         3750     3786      +36
===========================================
+ Hits          3548     3584      +36
  Misses         202      202

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Should the package be set per policy?

Currently, all the policies live in the package main as that's what the OPA examples tell you. But if you look at "real world" examples in gatekeeper, they are all in their own packages. I presume this is so multiple policies don't fire for one constraint - not 100% sure.
If we did update the packages to be unique per policy, it would make the testing easier as their would be no cross-firing of rules, i.e.: 1 rule fires against its own test data, vs currently, all rules fire against 1 set of test data.

FYI: Downstream tests can use conftest test --all-namespaces if they want all policies to exec.

can also do --namespace "namespace.a" --namespace "namespace.b"

Applied via PR: https://github.com/redhat-cop/rego-policies/pull/69


Enable number insight async requests

Removed the non-supported changes

Coverage decreased (-0.3%) to 99.735% when pulling 14224a049b4d97dd33499a4353612832393d0284 on superdiana:master into 9248fb40e15ed8107a9b506e669c033e1adf9ccf on Nexmo:master.

Can we rebase out the earlier commits?


Re-release addon on Splunkbase

We'd like to release this app on Splunkbase as a direct download rather than as an "externally hosted" app.  Splunk doesn't allow us to just convert an existing app between these types, therefore we need to upload a new app.
Additionally, Splunk now frowns upon reusing an existing sourcetype name that ships with Splunk enterprise, see #10.  So we have to change the sourcetype postfix_syslog to something new.   At the moment, I'm assuming that we also have to update the app id (folder name) to something new as well.
We would move the existing "master" branch to a new branch representing the "NEW" version of the app, the existing branch would be kept for some time for anyone still on the older version.  Each branch would have some clear instructions in the README explaining the situation (and linking to the other), and there would be some "upgrade" notes on how to migrate from the legacy version to the updated and Splunkbase-available version.
Here's what I'm thinking in terms of renaming stuff.    Please provide feedback with any recommendations or gotchas.

Name
Current value
New app (SplunkBase)
Old app (git-only)

App id
TA-postifx
TA-postfix2 *
TA-postfix

App version
0.8.x
2.x.x *
0.8.

Splunkbase id
3347
TBD *
3347

Label
Postfix Add-on for Splunk
Postfix Add-on for Splunk
Postfix Add-on for Splunk (Legacy) *

Sourcetype
postfix_syslog
mail:postfix *
postfix_syslog

Git branch
master
main *
legacy *

Where * indicates a change.

I got some internal feedback / approval on this.  I'll give this to the end of the week to see if there's any feedback/concern from anyone else who's contributed/commented on this project:  @j-chia, @barrettnet, @Guitaraholic, @atremar, @rdelmotte

Got a recommendation for using the name TA-postfix-for-splunk and postfix:syslog from alacercogitatus on Splunk's user slack. (This follows the vendor:tech:format sourcetype convention better, but I was concerned that it may cause some confusion because it's so similar, but looking for thoughts on the topic.)

Update:  Splunkbase was able to convert the app type from external to splunkbase-hosted, so that problem has been solved.   Not it's just a matter of getting some time to tackle this.


Update smoke tested plugin versions

Reviewing cheatsheet
Before merging the PR, comments starting with

❌ ❓must be fixed
🤔 💅 should be fixed
💭 may be fixed
🎉 celebrate happy things

The merge queue build has failed. Click here to see all failures.

@bot-gradle test AST

I've triggered the following builds for you. Click here to see all build failures.

All Smoke Tests for Pull Request Feedback (Trigger) (Pull Request Feedback)

@bot-gradle test AST

I've triggered the following builds for you. Click here to see all build failures.

All Smoke Tests for Pull Request Feedback (Trigger) (Pull Request Feedback)

@bot-gradle test AST

I've triggered the following builds for you. Click here to see all build failures.

All Smoke Tests for Pull Request Feedback (Trigger) (Pull Request Feedback)

@bot-gradle test AST

I've triggered the following builds for you. Click here to see all build failures.

All Smoke Tests for Pull Request Feedback (Trigger) (Pull Request Feedback)

@bot-gradle test AST

I've triggered the following builds for you. Click here to see all build failures.

All Smoke Tests for Pull Request Feedback (Trigger) (Pull Request Feedback)

@bot-gradle test AST

I've triggered the following builds for you. Click here to see all build failures.

All Smoke Tests for Pull Request Feedback (Trigger) (Pull Request Feedback)

@bot-gradle test AST

I've triggered the following builds for you. Click here to see all build failures.

All Smoke Tests for Pull Request Feedback (Trigger) (Pull Request Feedback)


Listen on local interface only

#124350
@alexr00 Seeing that you are OOF, I might merge this to give it some test exposure before endgame.
@alexdima I think you have worked with @alexr00 in this area, can you think of a case where listening on other interfaces than the local one is needed? If there is one, we might need a setting to be safe by default.

Let's merge optimistically


Bonsai ML

[x] Decide on repositories
[x] Review Python package
[ ] Discuss other integration packages (R, MATLAB)
[ ] Brainstorm approach to ML.NET integration

Closing since we are moving away from meta-issues to do overall tracking of projects. We might still want to migrate the remaining points to their own discussions or feature request issues at a later point.


List PRs

Ability to list pull requests via the bot. Should provide ways of listing:

[ ] all PRs
[ ] all open PRs
[ ] recently opened PRs
[ ] recently updated PRs
[ ] recently closed PRs

Due to the way the GitHub APIs work, this is already handled by the code that was written for issue #2.  All that was needed was to better support the display of PRs, a first cut of which happened in rev 1112748e34a84e91912f0b302ebd891a986a8ced.


[Android] Action.Execute support

Related Issue
Fixes #5506
Description

Re-SWIG shared model changes
Revert erroneous ParseUtil::GetValueAsString refactor, add clarifying comment
Action.Execute submit handling

Sample Card
v1.4/Elements/Action.Execute.json

Microsoft Reviewers: Open in CodeFlow

Added sample screenshot


DatePicker Alpine error when using getFormStatePath

Package
filament/forms
Package Version
2.9.7
Laravel Version
8.75
Livewire Version
2.9
PHP Version
8.1
Bug description
DatePicker Alpine error when using getFormStatePath to store all form data in one variable as per documentation.
https://user-images.githubusercontent.com/43570309/150423056-4d7bf47a-4e01-435e-81a9-c8b8ba4fe3f6.mp4
Steps to reproduce
No response
Relevant log output
No response

You need to call $this->form->fill() or $this->form->fill([your data]) in every single form, usually from the mount() method. It's in the Getting Started docs of the table builder.


liftOperator

Closes https://github.com/gcanti/fp-ts-rxjs/issues/39 (allows OperatorFunctions e.g. filter to be used on ObservableEither, ObservableThese, ReaderObservableEither and StateReaderObservableEither)
Version of https://github.com/gcanti/fp-ts-rxjs/pull/42, branched from 0.6.12
[Edit: added ObservableThese]

Alas! Ok I'll release this as a separate package. Any feedback? If not, no worries

Alas! Ok I'll release this as a separate package. Any feedback? If not, no worries

@anthonyjoeseph ah I'm sorry...this PR was closed automatically when I released v0.6.12 I guess.

Any feedback?

I need some time, I'm working on fp-ts v2.10 at the moment, sorry.

@anthonyjoeseph ah I'm sorry...this PR was closed automatically when I released v0.6.12 I guess.

Any feedback?

I need some time, I'm working on fp-ts v2.10 at the moment, sorry.

No worries! I'll open a new PR against master. Good luck with fp-ts, I'm a big fan!

No worries! I'll open a new PR against master. Good luck with fp-ts, I'm a big fan!

I'll open a new PR against master

ok, feel free to release your own package though

I'll open a new PR against master

ok, feel free to release your own package though


Running Windows having this type of error

D:\Portfolio\Project\auto_localization_maker\windows\flutter\generated_plugin_registrant.cc(13,3): error C3861: 'nb_utils_pluginRegisterWithRegistrar': identifier not found [D:\Portfolio\Project\auto_localization_maker\build\windows\runner\auto_localization_maker.vcxproj]
Exception: Build process failed.

You can use my fork for now.
Replace nb_utils definition with this on your pubspec.yaml.
dependencies:
    nb_utils:
        git:
            url: git://github.com/rockyprabowo/nb_utils.git
            ref: 1e936ea56f263ce1c93da64fe6ba7aba7a76fe4a

Thank you @rockyprabowo for working on this issue. I have merged and closed this issue.


Table tools not showing correctly

Hi and sorry for my english
I'm using the 3 buttons of tabletools copy/print/save but this not showing correctly...

It is not aligned to the right
Also on these 3 buttons, translations doesn't work

Maybe this page helps you.


baseline: add type judgement for keys of baseline

if the keys is not string, such as "tuple", then
it can not use method "startswith".
Signed-off-by: Wang Zhanjun<EMAIL_ADDRESS>

In what case does a context include a non-string type?

In what case does a context include a non-string type?

Ah yes, transcode tests.

Ugh, I guess I can't add commit to PR and squash from GitHub.
Need this fix ASAP so full test runs don't break today.  I merged a slightly modified commit as  b6902e37e4d0ee3768150ba5ebb68d83d727ee45.
Thanks for spotting this issue quickly.

Ok, thanks


Add driver station warning if named command is not known

My kids had a capitalization problem with a named command and didn't know why their thing wasn't getting scheduled. By at least logging a warning, there is some insight to what is going wrong.
Alternatively, you can hard fail with an exception. I think it is bad that there can be a discrepancy that silently fails between what you see in the gui and what gets run on the robot.

I think reporting a warning or error makes sense over throwing since it allows for easily disabling certain markers for testing just by commenting out the lines that register them, without having to delete them from the path.
Can you add the same warning for python as well. Relevant line is here. You'd need to add reportWarning to the import here


Properly Handle Exceptions With Routes

Sometimes I accidentally save a file with syntax errors. Light should account for this and gracefully handle this (potentially with some message in the logs).

Double checked and light already handles this

Experienced this again

:tada: This issue has been resolved in version 1.2.11 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Question about the google.places.text_search

Hi,
I was using your library to query the google places api and I found out that I get the error OVER_QUERY_LIMIT. I've read that this is due to the limit google puts to the user queries to its API (2,500 free requests per day or 50 requests per second) That's why I'd like to know if there is any way of limiting the number of results from the query, so I don't exceed that limit.
Thanks,
Felix.

Hey Felix,
This would be beyond the remit of this library. Different users could have different limits, depending on what they've (or not) paid for, or even where else they may be using their quota.
It would be best managed by your own application logic and probably a database.


Idea: Add a feature/tab to display the last played sets for a given player

If the tournament data is extracted from Smash.gg or Challonge, display previous played sets and scores in the tournament in the app and save them to a file for stream display (Akin to what was done at Heatwave: https://twitter.com/CH_Bonanza/status/1459985041421856768)
My contribution to #eSports broadcasting. This, I believe, is the first graphic of its kind, showing an individual player's run through the bracket. Hope to use this at more tournaments #RivalsofAether #heatwave pic.twitter.com/MYeP4WzER0— Taylor Broad @ Ascension (@CH_Bonanza) November 14, 2021
This feature could in theory extend to display set counts between two players as given by different data sources like a subset of Challonge/Smash.gg tournaments or Smash.gg general stats
(Obviously this is a low priority feature ^^)

After doing some testing for #102 with the API to get certain bits of data for Smash.gg, this might very well be feasible with a modified version of the recent sets query to only be 1 player and show the last 3 sets the player has done at the event, and simply turn that into an overlay

Available as a stable release