SQLITE_PROTOCOL: locking protocol

⚠ Please verify that this bug has NOT been raised before.

[X] I checked and didn't find similar issue

🛡 Security Policy

[X] I agree to have read this project Security Policy

📝 Describe your problem
Am deploying uptime-kuma on a kubernetes cluster. Am using a persistent volume with a deployment of uptime kuma. Here is the deployment file and pvc:
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: uptime-kuma
  namespace: monitoring
spec:
  replicas: 1
  selector:
    matchLabels:
      app: uptime-kuma
  strategy:
    type: Recreate
  template:
    metadata:
      labels:
        app: uptime-kuma
    spec:
      containers:
      - name: uptime-kuma
        image: louislam/uptime-kuma:1
        env:
        - name: UPTIME_KUMA_PORT
          value: "3001"
        imagePullPolicy: Always
        ports:
        - containerPort: 3001
          protocol: TCP
        volumeMounts:
        - mountPath: /app/data
          name: storage
        securityContext:
          allowPrivilegeEscalation: false
        resources:
          limits:
            memory: "512Mi"
            cpu: "1.0"
          requests:
            memory: "256Mi"
            cpu: "0.1"
      volumes:
      - name: storage
        persistentVolumeClaim:
          claimName: uptime-kuma
---
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: uptimekuma
  namespace: monitoring
spec:
  accessModes:
  - "ReadWriteOnce"
  resources:
    requests:
      storage: 1Gi
  storageClassName: managed-nfs-storage
---

Here is the output of the logs for the pod that spun up:
==> Performing startup jobs and maintenance tasks
==> Starting application with user 0 group 0
Welcome to Uptime Kuma
Node Env: production
Importing Node libraries
Importing 3rd-party libraries
Importing this project modules
Prepare Notification Providers
Version: 1.11.3
Creating express and socket.io instance
Server Type: HTTP
Data Dir: ./data/
Copying Database
Connecting to the Database
SQLite config:
[ { journal_mode: 'wal' } ]
[ { cache_size: -12000 } ]
SQLite Version: 3.36.0
Connected
Trace: [Error: SELECT value FROM setting WHERE key = 'database_version'  limit 1 - SQLITE_PROTOCOL: locking protocol] {
errno: 15,
code: 'SQLITE_PROTOCOL'
}
at process. (/app/server/server.js:1542:13)
at process.emit (events.js:400:28)
at processPromiseRejections (internal/process/promises.js:245:33)
at processTicksAndRejections (internal/process/task_queues.js:96:32)
If you keep encountering errors, please report to https://github.com/louislam/uptime-kuma/issues
When deployment is done without specifying a persistent volume, uptime-kuma works. Was adding a pvc to persist data for when the pod dies or is restarted. Kindly advise.
🐻 Uptime-Kuma Version
1.11.3
💻 Operating System and Arch
Ubuntu 16.04.7 LTS
🌐 Browser
Microsoft Edge Version 97.0.1072.55 (Official build) (64-bit)
🐋 Docker Version
20.10.7
🟩 NodeJS Version
No response

Looks like you are putting your storage on NFS, which is not supported by SQLite.

Thank you for this. Let me switch

Btw, how did you come up with those resource limits and requests values?

Hey folks. @jananathbanuka @beliot-atos @chakflying I'm using version 1.23.11. I've deployed the application as a docker container on AWS ECS. I used AWS EFS as an external storage. Is EFS not compatible with sqlite? Thanks for your comments

https://sqlite.org/forum/forumpost/8e84712c9d
That might work or might not work. Unclear, as it is still NFS (though v4 which does not guarantee you to corrupt your disks as v3 does).
=> Plan with the occasional db-corruption issue and take regular backups.
=> Plan with a strongly reduced performance ceiling (running a DB on a network file system is not a good idea)
Tl;DR: Just use a local file system as we suggest in our installation guide.

Thanks for your comments @CommanderStorm.
The issue with using a local file system is that if the container dies and a new one is created, the data in the SQLite file that is on the unhealthy container will be lost because a new SQLite file will be created in the new container, right?

That might depend on your cloud provider, but if you use a normal provider your local filesystem is persistent.
AWS ECS does not seem to support local, persistent disks. I would not want to be running anything with lower-latency storage requirements (such as a database) on such a system.
You might want to consider either AWS EC2 or running your container on a cheap VPS (away from the rest of your infrastructure) like netcup


Built-in validator formData parsing

What version of Hono are you using?
4.46
What runtime/platform is your app running on?
Nodejs
What steps can reproduce the bug?
Is there a reason at this you use arrayBuffer to construct formData record?
https://github.com/honojs/hono/blob/d21f8eb27aa43da9cd9d5b6f666692c4e92a0344/src/validator/validator.ts#L92
Hono has a built-in for that already c.req.parseBody()
This causes a bug if there's middleware which uses .parseBody() before validator - this populates c.req.bodyCache.parsedBody AND c.req.bodyCache.formData.
And since your validator tries to check the cache for formData(not parsedBody) - it gets a hit which contains FormData, not a Record.
It seems this issue would be mitigated if either hono used c.req.bodyCache.parsedBody with a fallback to arrayBuffer or would just use parseBody() directly since it already checks the cache.
So is there some reason for the current behavior? Apologies that the issue isn't properly filled in but I hope my explanation is clear enough.
What is the expected behavior?
No response
What do you see instead?
No response
Additional information
No response

Hi @HugeLetters

This causes a bug if there's middleware which uses .parseBody() before validator - this populates c.req.bodyCache.parsedBody AND c.req.bodyCache.formData.

Can you provide the concrete steps to reproduce that bug first?

@yusukebe hi, here's small demo
https://github.com/HugeLetters/formdata-hono-demo
Just run a dev script and it should provide logs which showcase the bug.

@HugeLetters Thanks! I'll check it later.

@HugeLetters Sorry for the late reply.
I'm investigating it now. I've created a minimal code to reproduce it:
import { validator } from 'hono/validator'

const app = new Hono().post(
  '/',
  async (c, next) => {
    await c.req.parseBody()
    await next()
  },
  validator('form', (value) => {
    console.log('validator - value:', value)
    assert(!(value instanceof FormData), 'Value has to be a Record, not FormData')
    return value
  }),
  (c) => {
    return c.text('Hello Hono!')
  }
)

const form = new FormData()
form.append('foo', 'bar')

await app.request('/', {
  method: 'POST',
  body: form
})


New installer

The current installer works fine but is a bit clunky, unclear, and outdated in some ways.
A replacement with improved UX and not reliant on jQuery (#907) should be implemented.

I started looking at an overhaul to the installer after #1583 out of my own interest, so this is convenient timing. I will go ahead and continue working on it and post updates here.

I see it got bumped a bit further down the roadmap, but I think a better installer would be great for v1.0.0.

I kicked it down the roadmap a little bit simply because it would be good to get a stable 1.0 out as soon as possible rather than in the unforeseeable future and the current installer is fit for purpose while there are a lot of other things that really aren't and therefore take priority.
Having said that, of course if there is a new shiny better option on the table for 1.0 or before then that is even better. :)

Will be closed by #1698


.env sample is wrong

https://github.com/stripe-samples/oxxo-payment/blob/fdc5cc9db00568a31ea251e6e0275df010264aad/.env.example#L7
This should be ../client as there is no web directory anymore

https://github.com/stripe-samples/oxxo-payment/blob/fdc5cc9db00568a31ea251e6e0275df010264aad/.env.example#L7
This should be ../client as there is no web directory anymore

If you cloned the project the env.example should be located under the server language you chose but web doesn't exist and the correct value will be:
STATIC_DIR=../../client/

Fixed. Thanks, both!


Limit number of spawned coroutine sockets

Phone gets nice and toasty if we just let it fly with unlimited coroutine's
Trade off a coroutine limit with performance, allow limiting max parallel sockets to 8, 16, 30, 60, 100

Limit creation amount by evaling a coroutine's dispatcher upon session creation, instead of using Dispatcher IO by default.
Provide an unlimited option which will use IO though


Better collision geometry

I think I noted that the collision geometry is just a mesh-collider of the output CSG, which is a bad approach in my opinion. Instead, we could use the shape of each brush to generate collision geometry. Use box-colliders for 6-faced brushes and convex-mesh-colliders for non-6-faced brushes, or maybe even make it a option.
Subtraction brushes would be a problem, but we could just use non-convex-mesh-colliders (aka the method that is being used now) for these particular brushes (could make it an user option).

SabreCSG used to have colliders per-brush. You can still find remnants of it in the source code (that currently removes colliders on brushes as part of an upgrade process for old levels made with previous versions of SabreCSG). Perhaps @sabresaurus can shed some light on why this was done.
PhysX (the physics engine Unity uses) can pre-process and optimize a static "polygon soup" (the collision mesh) to then do collision checks very quickly at play. There are several early-outs, assumptions and shortcuts you can take. One example is a quick dot product on an imaginary plane that cuts through the center of the level to determine whether the object is completely on the left or right side of the polygon soup; already you can skip 50% of the polygons. It can also create an octree in advance that will quickly tell what level polygons exist in the bounding box of the collider to then only check a handful of polygons. But regardless of the algorithms implemented;- It all comes with the condition that this mesh must NOT be moved. It's the reason why you can only have convex rigidbody colliders (older PhysX versions used to internally create convex colliders out of the polygon soup but this has since been discontinued as it may have (supposedly) resorted to creating a convex collider for every polygon).
The convex collider provides several assumptions and early-outs that make it optimal for very fast boundary checks. Every polygon has a unique normal and a quick dot product on every polygon can tell you whether something is inside of it. It's essentially a more advanced version of the bounding box.
Having too many convex colliders will increase the component count in Unity and consume additional resources which may eventually slow down all collision checks. Some real-world levels in SabreCSG can easily have over 3000 brushes or more. We'd have to generate over 3000 convex colliders. This will also inevitably slow down scene loading times and the overal performance of SabreCSG. Once #103 is fixed we will have very optimized geometry that can be passed on to PhysX dealing with any potential concerns.
Please correct me if I am wrong.

In earlier versions of SabreCSG editor selection of brushes was implemented by raycasting against mesh colliders with meshes matching the preview mesh on the brush mesh renderer. Later on I implemented ray-brush intersection for another feature (I don't recall which, perhaps it was the Clip tool), so it seemed a good idea to replace the collision components which internal intersection tests. SabreCSG automatically cleans up collision geometry on brushes from old levels as a result.
A common approach is to have two CSG models - one for rendering, one for collision, that way you can simplify your collision geometry. You can also toggle rendering/collision per brush in SabreCSG which is useful if you are doing visual detailing but don't want to contribute towards collision complexity.
I'm not sure I'd agree that mesh colliders from the output polygon soup are inherently bad, for many use cases they work and are efficient. However I take your point that it's a shame when building additively that SabreCSG can't generate box/convex mesh colliders. In fact I've already written an optional extension to do this - SabreCSG Extensions (Brush to Collider), this could be rolled into SabreCSG as an option with support added for convex mesh colliders when brushes aren't cuboid. SabreCSG has been used in production environments in the past with this approach to allow efficient primitive collision geometry to be generated (and I observed it to be more efficient than mesh colliders).


Add enum names via x-enumNames parameter

In some of my projects I have to describe an openAPI interface with enum with values like "01", "02", etc. Those are codes for specific business cases. I would like to operate in my code with enum values like ClientType.BASIC instead of ClientType._01 or use string values for such cases. As I found out there are some openAPI generators that uses extensions like x-enumNames for such cases (see this stackowerflow thread for more info).
So I propose following logic:
For enum schema like:
NamedEnum:
  type: string
  enum:
    - "1"
    - "2"
    - "3"
  x-enumNames:
    - "ONE"
    - "TWO"
    - "THREE"

generate following java code:
public enum NamedEnum {
    ONE("1"),
    TWO("2"),
    THREE("3");

    // ... some code ommited...
}

I see the issue.

I dislike to use

I see the issue..
using x-tension keywords like this is a bit against the philosophy of openapi-processor.
I would like to keep tooling specific stuff out of the OpenAPI description. Let's assume we have multiple consumers of the api. Each consumer may use another programming languages and different tooling.  Now we would have to add the x-enumNames equivalent of each tooling to the OpenAPI... Things get more difficult when we don't have control over the OpenAPI description. We would have to add some pre-processing to add the enum names to the api.
Maybe this is a bit academic. ;-) In most cases this may not be an issue.
The oneOf enum construction from stackoverflow is interesting. I guess I have see this before but I wonder if anyone is really using it.
I can also imagine to "hide" the x-tension keyword behind a "use at your own risk" option. So I can say here is a solution but it has its drawbacks.
The typical openapi-processor way would be to create some kind of mapping. That would be possible, but I fear this may be cumbersome to work with. Not sure. Probably depends on how many enums I need to map and how often I have to change them.

here is the Spring converter (kotlin)
package io.openapiprocessor.samples

import org.springframework.core.convert.converter.Converter

class NamedEnumConverter: Converter<String, NamedEnum> {

    override fun convert(source: String): NamedEnum {
        return NamedEnum.fromValue(source)
    }
}

and the code to enable it
package io.openapiprocessor.samples

import org.springframework.context.annotation.Configuration
import org.springframework.format.FormatterRegistry
import org.springframework.web.servlet.config.annotation.WebMvcConfigurer

@Configuration
open class WebConfig : WebMvcConfigurer {
    override fun addFormatters(registry: FormatterRegistry) {
        registry.addConverter(NamedEnumConverter())
    }
}

summarized in an article https://openapiprocessor.io/oap/home/articles/mapping/custom-enum-mapping.html :-)


Removal of stale branches?

We currently have two stale branches:

better-tasks, last modified: 2011
web-deployment, last modified: 2011

I do not know the state of them and I suspect that it would be tremendous amount of work to merge them into master since they are so far behind.
@synhershko Should we remove them?

IIRC better-tasks has some good ideas. web-deployment we can remove.

OK :+1:


New

Jenkins

@g82005 Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.

@g82005 Thank you for signing the Contributor License Agreement!


Error when using import_netcdf_pysteps in case of no rain.

Dear developers,
I'm currently trying to deal with no-rain cases when using pySTEPS (blendig).
As you might be aware, there are some issues when running pySTEPS when the radar-images contain no precipitations (see also issue #282).
As a temporary fix, I use in this 'no-rain case' only the NWP forecasts (basically no pySTEPS run).
But I do export the results to a netCDF file using the pysteps exporter.
In this no-rain case, also the NWP forecast does not contain any rain, so basically what is in the netCDF file is a timeseries of zeros
When I try to open this netCDF file using import_netcdf_pysteps I get the following error:
import_netcdf_pysteps("./blended_nowcast_20220811141000.nc")
There was an error processing the file zero-size array to reduction operation fmin which has no identity
---------------------------------------------------------------------------
AttributeError                            Traceback (most recent call last)
Input In [41], in <cell line: 1>()
----> 1 a,b = import_netcdf_pysteps("./blended_nowcast_20220811141000.nc")

File /space/hpc-home/michielv/pylibs/pysteps/pysteps/decorators.py:91, in postprocess_import.<locals>._postprocess_import.<locals>._import_with_postprocessing(*args, **kwargs)
     88         mask = ~np.isfinite(precip)
     89         precip[mask] = _fillna
---> 91 return (precip.astype(_dtype),) + tuple(other_args)

AttributeError: 'NoneType' object has no attribute 'astype'

I have traced to error back to this line in the definition of import_netcdf_pysteps:
metadata["threshold"] = np.nanmin(precip[precip > np.nanmin(precip)])

Which gives an error when precip[precip > np.nanmin(precip)] is an empty array in case all values are equal (zero in this case).
But this error is catched and a None is returned to the decorator which in turn gives an error.
This can probably be fixed easily with something like:
if np.nanmin(precip) == np.nanmax(precip):
  metadata["threshold"] = np.nanmin(precip)
else:
  np.nanmin(precip[precip > np.nanmin(precip)])

All the best,
Michiel

Hello @mpvginde and thanks for reporting this issue!
Unfortunately I've been lagging behind on #282 and hopefully this new issue will finally give the push to look into it...
Maybe also @pulkkins can help out on this? Anyway, I'll first see if we can reproduce the error in our test suite, will keep you posted!


moment.utc drops time part when used as mongoose default

Describe the bug
When we create a date field and default it to moment.utc, when it gets populated the date part of the timestamp is correct, but the time part gets lost and defaulted to midnight.
To Reproduce
Steps to reproduce the behavior:
Run the attached script.
const mongoose = require('mongoose');
const moment = require('moment');

main().catch(err => console.log(err)).then();

async function main() {
  await mongoose.connect('mongodb://localhost:27017/test');

  const kittySchema = new mongoose.Schema({
    birthday: {default: moment.utc, type: Date}
  });

  const Kitten = mongoose.model('Kitten', kittySchema);

  const cat = new Kitten({});
  console.log(cat);
 }

Expected behavior
Timestamp to be set to now with hour, minute and second correctly displayed (not zero).
Got this:
Erikas-Macbook:BUG erikaarnocki$ ts-node bug.ts
{
  _id: new ObjectId("61e5471c712520a0f39ebbef"),
  birthday: 2022-01-17T00:00:00.000Z
}

Expected:
Erikas-Macbook:BUG erikaarnocki$ ts-node bug.ts
{
  _id: new ObjectId("61e5471c712520a0f39ebbef"),
  birthday: 2022-01-17T10:39:40.000Z
}

Desktop:

ts-node v8.10.2

Moment-specific environment

The time zone setting of the machine the code is running on

Erikas-Macbook:BUG erikaarnocki$ locale
LANG="en_GB.UTF-8"
LC_COLLATE="en_GB.UTF-8"
LC_CTYPE="en_GB.UTF-8"
LC_MESSAGES="en_GB.UTF-8"
LC_MONETARY="en_GB.UTF-8"
LC_NUMERIC="en_GB.UTF-8"
LC_TIME="en_GB.UTF-8"
LC_ALL=

The time and date at which the code was run
Mon 17 Jan 2022 10:32:37 GMT
Other libraries in use (TypeScript, Immutable.js, etc)

{
  "devDependencies": {
    "@types/node": "^17.0.9",
    "cypress-wait-until": "^1.7.1"
  },
  "dependencies": {
    "moment": "^2.29.1",
    "mongoose": "^6.1.6",
    "typescript": "^4.5.4"
  }
}

Please run the following code in your environment and include the output:
console.log((new Date()).toString())
console.log((new Date()).toLocaleString())
console.log((new Date()).getTimezoneOffset())
console.log(navigator.userAgent)
console.log(moment.version)

Erikas-Macbook:BUG erikaarnocki$ ts-node
> console.log((new Date()).toString())
Mon Jan 17 2022 10:33:56 GMT+0000 (Greenwich Mean Time)
undefined
> console.log((new Date()).toLocaleString())
17/01/2022, 10:33:56
undefined
> console.log((new Date()).getTimezoneOffset())
0
undefined
> console.log(navigator.userAgent)
/Users/erikaarnocki/BUG/[eval].ts:1
console.log(navigator.userAgent);
            ^

Uncaught ReferenceError: navigator is not defined
    at /Users/erikaarnocki/BUG/[eval].ts:1:13
    at Script.runInThisContext (vm.js:133:18)
    at exec (/usr/local/lib/node_modules/ts-node/src/bin.ts:347:17)
    at /usr/local/lib/node_modules/ts-node/src/bin.ts:337:27
    at Array.reduce (<anonymous>)
    at _eval (/usr/local/lib/node_modules/ts-node/src/bin.ts:336:18)
    at REPLServer.replEval (/usr/local/lib/node_modules/ts-node/src/bin.ts:387:16)
    at bound (domain.js:413:15)
    at REPLServer.runBound [as eval] (domain.js:424:12)
    at REPLServer.onLine (repl.js:817:10)

Opened ticket to mongoose as well.
https://github.com/Automattic/mongoose/issues/11233

Whenever You use a temporal component in Your tests (like the "current date/time", which moment.utc()-method internally uses) ... You should be prepared to mock the native Date-implementation of JavaScript to return the expected Date/Time whenever called in Your tests. Otherwise Your tests will fail tomorrow, a minute from now, etc.
This is not an issue with Moment and it is not an issue with mongoose. You just need a bit of prerun setup on Your test ;)


audio watermarking question

I gonna implement program that embed and hide 12 digits decimal number
into .wav file audio signal and its dont affect to file sound human
hear, then after while I want extract same 12 digits decimal number
from those files. I know somethings about NAudio .net , Fast Fourier
Transform.
I have below algorithm idea but I cant implement it. Through Using Fourier Transform, I change main .wav file to frequency domain then make a signal in frequency domain form 12 digits number in less than 20 hz ( because its not hear by human ) and then merge two
signal to one signal in frequency domain and finally operate Inverse
Fourier Transform to back to time domain. in other hand I should
process some file and extract numbers

NAudio can write any samples you like to a file, but I'm afraid you'll need to implement your own algorithm for something like this as its very bespoke


define $NODE_PATH to improve the require relative paths

https://lostechies.com/derickbailey/2014/02/20/how-i-work-around-the-require-problem-in-nodejs/

$NODE_PATH is apparently an anti-pattern

https://github.com/tleunen/babel-plugin-module-alias might be a reasonable option


Throw IllegalStateExceptions after closing.

java.io throws IOExceptions. Okio throws IllegalStateExceptions.

Assuming that the FileObjectQueue version will still throw an IOException for this, should the memory version continue to do the same?

This PR changes the behavior of both ObjectQueues, so it is consistent.

Ah oops, didn't ready carefully enough on mobile. LGTM!

No test changes? yikes!


trivial bootstrap/bootstrap.go code style fixes

A bit of meditative tidying for bootstrap/bootstrap.go:

explain the RedactLengthMin const in a code comment
early return instead of indent, when it makes sense
prefer if initialisation statement, when it makes sense

Best viewed with whitespace changes ignored (&w=1)

😬 Except I forgot to flip the … > 0 here:
-	if environ != nil && environ.Length() > 0 {
+ 	if environ == nil || environ.Length() > 0 {

It should have been:
-	if environ != nil && environ.Length() > 0 {
+ 	if environ == nil || environ.Length() == 0 {

Thankfully local usage of the compiled binary and the CI test suite both picked it up 😅
The perils of meditative “trivial” changes.

Nice one @pda! I've been meaning to get a linter in there for some time.


Shaping_differs to allow >=2 items, added defs for nl_Latn and tr_Latn

I think actually we need to add a manually defined test for the change in the check (mostly the differs part), since there aren't any definitions using this notation yet. But I don't know how to define a test because I don't fully understand what's going on. Could you please contribute this?


Cannot have a table name with 'List' at the end or this line removes it from the table name

https://github.com/morris/lessql/blob/338966185fc052e7ee769360d19950cf90c0fd42/src/LessQL/Database.php#L54

Shouldn't "_list" suffix or "list" (lower-case) work? SQL is case insensitive. @rubenvincenten that could work, however think this is a very niche edge case...


format error to make it readable for docker

remove unneeded

Coverage increased (+0.06%) to 53.427% when pulling 9d976668fbb0caed8aa51237babe240344bb7688 on wy65701436:error_interceptor into 0b282039e9d12ff822715a2422c5a1edcf5470bd on vmware:master.


Improve command-line usage

Instead of having multiply entry points, we should support one executable with multiple commands (tests_selector init instead of tests_selector_init) via something like click
We might also want to invent shorter name for the executable (I'd hate if git would be instead version_control :D), but that's "naming things" -- one of the two most difficult problem in the computer science (funny that the tool itself is pretty much about the second, which is "cache invalidation")  😄

will it collide with pytest plugins way of integration? Here how it should be done (pycov example)

I think it is irrelevant now after #67, but feel free to reopen it if there is a need.


contact-us-updated

🛠 Fixes Issue

👨💻 Changes proposed

✔ Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[x] This PR does not contain plagiarized content.
[x] The title of my pull request is a short description of the requested changes.

📄 Note to reviewers
Kindly merge my pull request it is working but the only limitation is the database

📷 Screenshots

@vaishnavi2810-code Rename your file name to Contact_us

I think you made the changes


About inference speed

Hi, thanks for your brilliant work!
Now i am trying the experiment with 'R50/300queries' setting. The model converges well and works well, but the inference speed (>120ms/f, ≈8.3fps) is significantly lower than which reported in the paper (14.2fps, ≈70ms/f). It's worth noting that I also used A100 GPU, and i only counted the time spent on model processing (including post-processing, but not image I/O).
Could you please share the inference speed test script or some debugging tips? @FengLi-ust

Following the common practice, we only consider computing time. Post-processing is to handle COCO evaluation, so it is not included.

The inference speed i tested on A100 is >120ms/f, ≈8.3fps, and i also didn't conside coco-eval part. But i added the box&mask post-processing part. Do you have plan to release relevant speed test scripts in the future?

Hi, there is no script for testing speed. Whenever you do the coco inference, the detectron2 logger will output the compute time inference pure compute time and total time Total inference time. This is an example of one previous model logging:

Thx! I got a similar result with you.


Login Restriction After Office Hours. setting required.

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Login restrictions facility in ECB

Multiple logins ON/OFF💡
IP based login with multiple IP support
Timing based restrictions


Update cookie-sharing.md

Added a tip to suggest to add a dependency for the code to start working. It was not obvious and made me search through source code

Hi @zaggy, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, DNFBOT;

@zaggy  Thanks. The Tip dialog is a little too intrusive so I changed it to a comment. Thanks for your contribution.


Dependency Insight does not find substituted dependency

With Gradle 7.1.1 I got an error message
* What went wrong:
Execution failed for task ':foo:compileBarJava'.
> Could not resolve all files for configuration ':foo:barCompileClasspath'.
,   > Could not find org.bouncycastle:bctsp-jdk15on:1.46.
     Searched in the following locations:
       - https://.../org/bouncycastle/bctsp-jdk15on/1.46/bctsp-jdk15on-1.46.pom
     If the artifact you are trying to retrieve can be found in the repository but without metadata in 'Maven POM' format, you need to adjust the 'metadataSources { ... }' of the repository declaration.
     Required by:
         project :foo > project :baz > com.lowagie:itext:2.1.7.js5 > bouncycastle:bctsp-jdk14:138

I wondered where the dependency is coming from and issued
./gradlew :foo:dependencyInsight --configuration barCompileClasspath --dependency org.bouncycastle:bctsp-jdk15on

But suprisingly was answered with
No dependencies matching given input were found in configuration ':foo:barCompileClasspath'

The reason is this:
substitute module('bouncycastle:bctsp-jdk14:138') using module('org.bouncycastle:bctsp-jdk15on:1.46')

If I do
./gradlew :foo:dependencyInsight --configuration barCompileClasspath --dependency bouncycastle:bctsp-jdk14

everything is clear, but it is highly confusing that it could not find the dependency it was actually complaining about.

Does dependencyInsight work once the substitution target can be resolved?

Yes, if the substitution is successful, dependencyInsight works as expected.


Request: Promise implementation

Hello. It would be nice if this library was promised based, since it opens many possibilities and keeps it more up to date with modern standards. This would allow the library to be used with "await" expressions for example, which I think can be beneficial for the addSpam function, because for example, if someone makes 1000 emits in an instant, and the kickThreshold is 10, a lot more than 10 operations would go through before the anti spam system reaches the threshold and kicks the user, since addSpam seems to work in an asynchronous manner. If await was used, I think it could alleviate that problem by working in a synchronous manner, making it so the socket gets kicked after only 10 operations. Though I'm not 100% sure on this, you could read more about the subject and think about it perhaps. Thanks.

I agree,  this module is long due for a nice update


Look up words with spaces

This happens often in English, e.g. "high school", and does not currently work.


feat: Add facebook identity provider

This PR partially solves issue #28

@sourabhmandal plz provide a demo site and show Facebook login is working.

Closed as stale.


Ability to only play a snippet of an audio file

This is an enhancement request.
This would be to set the start and end time for an audio file to play.  So let's say I have an audio clip, and I only want to play the clip from :15 (15 second mark) to :25 (25 second mark) == 10 seconds total.  This change would add the ability to set the start and end times for that audio file for playback.
This would also cover the case of being able to only play the first 30 seconds of a clip, similar to an audio preview.
The audio controls and time rail would only show the total duration specified for the audio clip.  So if I have a start time of :15 and an end time of :25 then the controls and time rail will only show the 10 seconds span from :15 to :25.
This would be an opt-in approach and a passive change to existing functionality.  I don't mind working on this change as long as I know it's a change that would be accepted once stable.
@johndyer, thoughts?

For anyone coming to this in the future, you can already do this by using the w3 spec uri fragments:

http://www.w3.org/TR/media-frags/#fragment-query

So for the audio example on the mediaelement main page, if you wanted to only play the first 10 seconds of the audio file, your markup should be generated as follows:
<audio src="/media/AirReview-Landmarks-02-ChasingCorporate.mp3#t=0,10" type="audio/mp3">
</audio>


requirements.yml refers to an obsole role

cldr-runner/base/requirements.yml refers to an obsolete role
roles:

name: geerlingguy.postgresql
version: 2.2.0
src: https://github.com/dbeech/ansible-role-mysql
version: master

The role dbeech/ansible-role-mysql does not work with mySQL 8....only with and older 5.7 era mysql
I would suggest

src: https://github.com/clevesque/ansible-role-mysql
version: master

Agreed. I would actually like to remove this dependency completely. I think using this role is overkill for our needs.

Updated the requirements via #77


is there a gencode.composite.collapsed.rds file for hg38?

Since I'm working with hg38, I'd love to have a version of the http://mskilab.com/gTrack/hg19//gencode.composite.collapsed.rds file for hg38.
If there isn't already one available, how can I create one for myself (that has the same fields and organization as the one you make available?

Hi Peter - sorry for the late response but there is actually one available
at
http://mskilab.com/gTrack/hg38/gencode.composite.collapsed.rds
On Wed, Apr 24, 2019 at 3:35 PM Peter Waltman<EMAIL_ADDRESS>wrote:

Since I'm working with hg38, I'd love to have a version of the
http://mskilab.com/gTrack/hg19//gencode.composite.collapsed.rds file for
hg38.
If there isn't already one available, how can I create one for myself
(that has the same fields and organization as the one you make available?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/mskilab/gGnome/issues/13, or mute the thread
https://github.com/notifications/unsubscribe-auth/AC73JEMSEDM3GFHUI2K6FGLPSCZBHANCNFSM4HIHIACQ
.


Integrate all the apis to render results based on artists & songs

since there was a bug, we changed dropdown to song & video. now the user can look at top results from Spotify & YouTube easily.
when the user searches for a song, the Spotify link takes the user directly to the song whereas the YouTube link takes the user to a direct search of the corresponding song & artist name.
when the user searches for a video, the YouTube link takes the user directly to the video whereas the Spotify link takes the user to a direct search of their input in the search.
because there was too many bugs & incorrect videos being pushed to the YouTube icon, this was the best course of action.


Update README.md

I made the changes as per the issue I created on the GitHub Issue tag

Good and Quick Job @meta-human-08


Feat trusted

This PR is about of resolve #244 issue

Awesome work as always Mr. Vadim, can you take a look at my proposals?

@getjump

Awesome work as always Mr. Vadim

Thanks!

can you take a look at my proposals?

Sure! Which one? About extracting a part with CommandHandler handler creating?


Add more descriptive error message in the presence of OpenAI API timeouts

Why are these changes needed?
API timeouts can be confusing to a user. This adds a more descriptive error message when they occur and offers a suggestion to mitigate.
Related issue number

Checks

[ ] I've included any doc changes needed for https://microsoft.github.io/autogen/. See https://microsoft.github.io/autogen/docs/Contribute#documentation to build and test documentation locally.
[ ] I've added tests (if relevant) corresponding to the changes introduced in this PR.
[ ] I've made sure all auto checks have passed.

Codecov Report
Attention: 2 lines in your changes are missing coverage. Please review.

Comparison is base (e0fa6ee) 35.19% compared to head (fb367f9) 20.48%.

Files
Patch %
Lines

autogen/oai/client.py
0.00%
2 Missing :warning:

Additional details and impacted files
@@             Coverage Diff             @@
##             main    #1577       +/-   ##
===========================================
- Coverage   35.19%   20.48%   -14.71%
===========================================
  Files          44       44
  Lines        5328     5330        +2
  Branches     1236     1306       +70
===========================================
- Hits         1875     1092      -783
- Misses       3299     4102      +803
+ Partials      154      136       -18

Flag
Coverage Δ

unittests
20.46% <0.00%> (-14.73%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

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


[Fix #12542] Fix false positive for Lint/MixedRegexpCaptureTypes

Fix false positive for Lint/MixedRegexpCaptureTypes when > is included in the look-ahead matcher rubocop recognizes the matcher as a named matcher.

Before submitting the PR make sure the following are checked:

[x] The PR relates to only one subject with a clear title and description in grammatically correct, complete sentences.
[x] Wrote good commit messages.
[x] Commit message starts with [Fix #issue-number] (if the related issue exists).
[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[x] Added tests.
[x] Ran bundle exec rake default. It executes all tests and runs RuboCop on its own code.
[x] Added an entry (file) to the changelog folder named {change_type}_{change_description}.md if the new code introduces user-observable changes. See changelog entry format for details.

Nice work @marocchino !!!


The difference between this plugin and cloudwatch event

Hi,
This plugin is amazing and I absolutely like it. Thanks so much for your effort.

Previously what I did was I setup a cloudwatch event to ping the lambda every 5 minutes. Is there any other benefits I can get from changing to use this plugin instead?
Tons of thanks
CJ

The idea is the same.
However, this plugin has some advantages:

Easy configuration and good integration with the serverless framework
Option to warm up your lambdas immediately after deploying
Support concurrent lambdas warmup
Produce logs of the lambda invocations
Total control of the payload

The idea is the same.
However, this plugin has some advantages:

Easy configuration and good integration with the serverless framework
Option to warm up your lambdas immediately after deploying
Support concurrent lambdas warmup
Produce logs of the lambda invocations
Total control of the payload

Thanks for you answer. It's solved!


Greenland Addresses

http://www.nunagis.gl
<EMAIL_ADDRESS>Ministry of Finance
Section of National Planning
Box 1037
3900 Nuuk
Updated 26.02.2015

Dear Justin
Have you being answered for you question?
Otherwise, you should check our GIS platform en.nunagis.gl (which we experience some technical difficulties at this time). In this GIS platform, you choose a city/town and you activate this layer with housenumber or bulding number (B-nr) in the layer “placename + boarder” (remember to zoom in sufficiently in order to enable to housenumber layer).
If the English version of GIS platform (en.nunagis.gl) does not work, try the Danish version by entering dk.nunagis.gl > choose the town > activate the housenumber layer in the “Stednavne + grænser” – layer (remember to zoom in). Unfortunately there is no streetname yet, so you only see the housenumber (and or the entire address).
Inussiarnersumik / Med venlig hilsen
Asiaq
Ludvig Petersen
Tlf 348825

I emailed back and asked for the points. Stay tuned!

There are no  address point in the system yet. The only shapefile you may acquire, is the layer with building and building number, and those layers are not free.
May I ask why you are trying to find address points? What is the occasion?
Inussiarnersumik / Med venlig hilsen
Asiaq
Ludvig Petersen
Tlf 348825

Hi Justin
In Greenland we do only have a complete address theme (road names and house numbers) in one town; the city of Nuuk. But the road geometry, the road names, the building geometry and house numbers are not connected (georeferenced).
In general, the buildings in Greenland have a building number e.g. B-234 (not a house number as commonly known) that is only unique for each town or settlement, meaning that one building number can occur in several locations (towns and settlements). Many locations in Greenland, typically the settlements, do not have any roads, and therefore no road names. The traffic infrastructure consists of paths and trails without any names.
We have a project ongoing, that will give each building number a unique ID consisting of the location number and georeferenced to the building geometry, and georeferencing the road geometry with road names and house numbers, for those locations that have roads, road names and house numbers.
So, for the moment, we can only offer you the buildings and the building numbers for all the locations of Greenland, and for the city of Nuuk, we can also offer you buildings and house numbers.
We can deliver these information for DKK 5.000,-.
Inuulluaqqusillunga/
Venlig hilsen/
Kind regards
Jens Gottlieb
Cartographer
Head of Section
Maps & Geodata

That’s $730.09 US Dollar at today’s exchange rate.
Can you clarify with him that we'd have redistribution rights and what sort
of attribution requirements (if any), please?
On Thu, May 11, 2017 at 10:11 AM, Justin Meyers<EMAIL_ADDRESS>wrote:

Hi Justin
In Greenland we do only have a complete address theme (road names and
house numbers) in one town; the city of Nuuk. But the road geometry, the
road names, the building geometry and house numbers are not connected
(georeferenced).
In general, the buildings in Greenland have a building number e.g. B-234
(not a house number as commonly known) that is only unique for each town or
settlement, meaning that one building number can occur in several locations
(towns and settlements). Many locations in Greenland, typically the
settlements, do not have any roads, and therefore no road names. The
traffic infrastructure consists of paths and trails without any names.
We have a project ongoing, that will give each building number a unique ID
consisting of the location number and georeferenced to the building
geometry, and georeferencing the road geometry with road names and house
numbers, for those locations that have roads, road names and house numbers.
So, for the moment, we can only offer you the buildings and the building
numbers for all the locations of Greenland, and for the city of Nuuk, we
can also offer you buildings and house numbers.
We can deliver these information for DKK 5.000,-.
Inuulluaqqusillunga/
Venlig hilsen/
Kind regards
Jens Gottlieb
Cartographer
Head of Section
Maps & Geodata
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/openaddresses/openaddresses/issues/2960#issuecomment-300855386,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA0EO2IVYAAYAX6Dpj0e_Bh8jBxe47G9ks5r40E6gaJpZM4NNP3F
.

e-mailed Ludvig and Jens to check on TOU and attribution.

I just sent a follow-up email to the May 15th e-mail. Hopefully we hear from them soon.

Sent follow-up e-mail

An exciting project!
At this moment, the requested data is not available. However Greenland is running a project so Greenlandic address’ will be georeferenced and hopefully available for free. Expected conclusion of the project is during 2018.
Inussiarnersumik / Med venlig hilsen
Asiaq
Ludvig Petersen
Tlf +299 348815
My Response below:
Thanks for the information! For the current data you do have, do you know the total amount, coverage, and have any metadata? I would like to document it so when we check back in the future, we know what to expect. Is the current data available for purchase if it is not free?
Thanks!
Justin

At this monent, we cannot even provide metadata. All addresses have not being transformed to electronic data yet. We do guess that there are about 35.000 valid addresses in 17 towns and 58 communities in Greenland.
Inussiarnersumik / Med venlig hilsen
Asiaq
Ludvig Petersen
Tlf +299 348815

the price for the building geometry and the building number for all the locations of Greenland is DKK 5.000,-
You can incorporate the data into your project as long as you refer to Asiaq, Greenland Survey.
As I wrote in the mail we do only have house numbers for the city of Nuuk, but building numbers for the towns and settlements for all the locations of Greenland.
I do not have the numbers of how many addresses that exist in the dataset. The data is not in a database but in CAD files for each location.
Regards
Jens

I asked if there was a shapefile/ csv/ other geospatial format besides CAD

We can deliver in MapInfo and shape file formats.
/Jens

About $786
https://www.google.com/search?q=dkk+to+dollars&oq=DKK+to+doll&aqs=chrome.0.0j69i57j0l4.2695j0j7&sourceid=chrome&ie=UTF-8

Rad! Do they deliver via download link or DVD? (Since they are so far away download link is better.)

I just emailed Jens and asked him for the order form, and the delivery method. I'm going to be off grid for the next couple days, so my internet, email might not work the greatest. As soon as I hear back from him, I will update you. Thanks!

Justin
We do not have an order form, but you can send me your request for the exact data sets you would like to buy, and send me your contact information:
Full name, address and phone number.
Then we will put your data on our FTP server, and send you an invoice.
/Jens


chore(main): release 1.7.1

:robot: I have created a release beep boop
1.7.1 (2023-06-05)
Bug Fixes

astro: provide new typescript.tsdk initialization option (#235) (d83f31d)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/williamboman/mason-lspconfig.nvim/releases/tag/v1.7.1 :sunflower:


Refactor the current API view into a proper DRF view

From https://github.com/nexB/vulnerablecode/pull/26#discussion_r138486436

pombredanne 9 days ago Owner
I would expect the returned payload to have some "header" data (e.g. some tool version, what was the query made, number of results returned, ... And to have the list of packages returned under the packages: element

See http://www.django-rest-framework.org/api-guide/generic-views/ and http://www.django-rest-framework.org/api-guide/viewsets/

@pombredanne Regarding header data, you mean something similar to something that is added in ScanCode's JSON based results?

@kartiksibal the header data was added thanks to the PackageViewSet in the latest commits.
The API now return proper headers  count, next, previous.
No need to add more at this point until there's a need for it.
Current shape of the API data on the Packages endpoint:
{
    "count": 793,
    "next": "http://<IP_ADDRESS>:8000/api/packages/?limit=100&offset=100",
    "previous": null,
    "results": [
        {
            "name": "gcc-4.6",
            "version": "",
            "platform": "",
            "vulnerabilities": [
                {
                    "summary": "",
                    "cvss": null,
                    "references": [
                        {
                            "source": "",
                            "reference_id": "CVE-2002-2439",
                            "url": ""
                        }
                    ]
                }
            ],
            "references": []
        },
[...]


Add Child Policy Code to AWS Object Storage Optimization Policy

This just adds the additional code needed for this policy to work as a child policy.
Functionality as a regular policy is unchanged apart from the addition of a Flexera credential, since this is needed for the child policy functionality but was not present in the original policy.
The version is also bumped from 2.9 to 3.0, so even if the above is considered a "breaking change" (I imagine most customers have a Flexera credential at this point), the major version number also changed.

All of the mentioned problems have been resolved:

Version changed to 2.10
Check statement modified
Header added to first datasource that executes. I also moved this datasource to the top of the policy to avoid confusion.


How can I integrate PHP API in kaiwa source ?

Hello, @ForNeVeR @vitalyster , Can you please help me how to integrate PHP API in kaiwa source?

Kaiwa is designed to be a simple JS application that you could put under any server and it should just work. I can't see what PHP support we would need. What do you want?

I want to develop Group module using API.

Honestly I have no idea what does it mean. So, what kind of help do you require?

Okay. In short i want to integrate api. If you have any idea then please
help me how can i do it.
On Sat, Oct 13, 2018, 3:40 PM Friedrich von Never<EMAIL_ADDRESS>wrote:

Kaiwa is designed to be a simple JS application that you could put under
any server and it should just work. I can't see what PHP support we would
need. What do you want?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ForNeVeR/Kaiwa/issues/237#issuecomment-429528172, or mute
the thread
https://github.com/notifications/unsubscribe-auth/Aje4ziRzOWWR6PeKndH6ag_swpVSduAkks5ukbwSgaJpZM4XaduY
.

Well, I positively have no idea what do you mean by "integrate api". If you want to publish Kaiwa on your web server — then you just go ahead and publish it on your web server.

okay. i am facing one issue when publish kaiwa on web server.
Following error i am getting :
  The page at 'https://domainname/' was loaded over HTTPS, but attempted to connect to the insecure WebSocket endpoint 'ws://chatserverdomain/ws/'. This request has been blocked; this endpoint must be available over WSS.
and
Uncaught DOMException: Failed to construct 'WebSocket': An insecure WebSocket connection may not be initiated from a page loaded over HTTPS.

Replace ws with wss in your config.json

thanks @vitalyster , its working now.

Stacktrace could help in this case. Without the stacktrace, I can't figure what's going on.

Okay thanks @vitalyster , i got the solution.


Raycaster events not throwing accurate intersection points?

First of all Mind-Ar an amazing library, but unfortunately i ran into an issue, where i was trying to use inbuilt a-frame raycaster events to detect the point of intersection on a plane, but i am not getting accurate points, i was customising the "mindar-image-target" component as per my requirement where i can add the element dynamically as soon as the target is detected and here i am attaching my code snippets.
Requirement: -
Place a plane on the detected target and place a box on top of the plane for each click in the respective position.
Approach : -
Actually i want to implement multi-targets but here in this example it's just minimised to simplify the issue.
1)Here i am registering a new component called 'next-image-target' which is an exact replica of "mindar-image-target" from the library except updateWorldMatrix, as i want to add a 3D object dynamically based in target index, so i am updating the function as per my requirement and adding cursor & raycaster to the camera-entity if the target is found and removing them if target is lost.
2)Another component with the name "plane" which is binded to dynamically added plane in the updateWorldMatrix of 'next-image-target', which has raycaster dependency and i am listening to the "raycaster-intersected" & "raycaster-intersected-cleared" and storing the ray intersecting coordinates in the variable called "intersectPoints", added a click event to the plane so that i can place a box on the plane in the clicked position.
Issue Faced: -
Intersected coordinates were not correct and the box were placed some where in the 3D-world.
use the below image to scan

HTML

<head>
  <script<EMAIL_ADDRESS>    <script src="https://aframe.io/releases/1.2.0/aframe.min.js"></script>
    <script<EMAIL_ADDRESS>  <script src="./components.js"></script>
</head>
<body>
  <a-scene mindar-image="imageTargetSrc: https://cdn.jsdelivr.net/gh/hiukim/mind-ar-js@1.1.5/examples/image-tracking/assets/card-example/card.mind;" vr-mode-ui="enabled: false" device-orientation-permission-ui="enabled: false">
    <a-camera position="0 0 0" look-controls="enabled: false"></a-camera>
    <a-entity id="target0" next-image-target="targetIndex: 0">
    </a-entity>
  </a-scene>
</body>

components.js
let intersectPoints = new THREE.Vector3();
AFRAME.registerComponent("next-image-target", {
  dependencies: ["mindar-image-system"],
  schema: {
    targetIndex: { type: "number" },
  },

  postMatrix: null,
  init: function () {
    const arSystem = this.el.sceneEl.systems["mindar-image-system"];
    arSystem.registerAnchor(this, this.data.targetIndex);
    const root = this.el.object3D;
    root.visible = false;
    root.matrixAutoUpdate = false;
  },

  setupMarker([markerWidth, markerHeight]) {
    const position = new AFRAME.THREE.Vector3();
    const quaternion = new AFRAME.THREE.Quaternion();
    const scale = new AFRAME.THREE.Vector3();
    position.x = markerWidth / 2;
    position.y = markerWidth / 2 + (markerHeight - markerWidth) / 2;
    scale.x = markerWidth;
    scale.y = markerWidth;
    scale.z = markerWidth;
    this.postMatrix = new AFRAME.THREE.Matrix4();
    this.postMatrix.compose(position, quaternion, scale);
  },

  async updateWorldMatrix(worldMatrix) {
    const isExist = document.getElementById('plane');
    if (worldMatrix !== null && isExist===null) {
      const target = document.querySelector("#target" + this.data.targetIndex);
      let plane = document.createElement("a-plane");
      plane.setAttribute("id", "plane");
      plane.setAttribute("class", "plane");
      plane.setAttribute("width", "1");
      plane.setAttribute("height", "1");
      plane.setAttribute("color", "green");
      plane.setAttribute("plane", "raycast:true");
      target.appendChild(plane);
      const event = new Event("targetFound");
      document.dispatchEvent(event);
    } else if (worldMatrix === null && isExist != null) {
      document.getElementById(`plane`).remove();
      const event = new Event("targetLost");
      document.dispatchEvent(event);
    }
    this.el.object3D.visible = worldMatrix !== null;
    if (worldMatrix === null) {
      return;
    }
    var m = new AFRAME.THREE.Matrix4();
    m.elements = worldMatrix;
    m.multiply(this.postMatrix);
    this.el.object3D.matrix = m;
  },
});

AFRAME.registerComponent("plane", {
  dependencies: ["raycaster"],
  schema: {
    raycast: { type: "boolean" },
  },
  init: function () {
    this.el.addEventListener("raycaster-intersected", (evt) => {
      this.raycaster = evt.detail.el;
    });
    this.el.addEventListener("raycaster-intersected-cleared", (evt) => {
      this.raycaster = null;
      intersectPoints = null;
    });
    this.el.addEventListener("click", (evt) => {
      console.log(intersectPoints);
      if (intersectPoints) {
        let box = document.createElement("a-box");
        console.log(`${intersectPoints.x} ${intersectPoints.y} ${intersectPoints.z}`);
        box.setAttribute("position", `${intersectPoints.x} ${intersectPoints.y} ${intersectPoints.z}`);
        box.setAttribute("material", "color:red");
        box.setAttribute('depth','10');
        box.setAttribute('height','10');
        box.setAttribute('width','10');
       this.el.appendChild(box);
      }
    });
  },
  tick: function () {
    if (!this.raycaster) {
      return;
    }
    let intersection = this.raycaster.components.raycaster.getIntersection(this.el);
    if (!intersection) {
      return;
    }
    intersectPoints = intersection.point;
  },
});

document.addEventListener("targetFound", () => {
document.querySelector('a-camera').setAttribute('raycaster','far: 10000;objects: .plane');
document.querySelector('a-camera').setAttribute('cursor','fuse: false; rayOrigin: mouse;');
});

document.addEventListener("targetLost", () => {
  document.querySelector('a-camera').removeAttribute('raycaster')
  document.querySelector('a-camera').removeAttribute('cursor')
});

Finally another point of doubt is that the position of the model shows 0,0,0 always from the a-frame inspector,  is there any way which reveals the model placing position, as per my observation its completely handled by the world matrix, Any idea how to convert world matrix in to world coordinates.
Thanks in advance for the help.

@hiukim @Makio64 @Parikshit-Hooda  can anyone please look into this issue, any help would be appreciated.

Facing same issue with respect to raycasting. May be we are missing something. Any help will be appreciated.

fixed in v1.2.2


Error when building with soto v6.8.0

When building my project that use soto-s3-file-transfer v1.2.0 and soto v6.8.0, I get "Switch must be exhaustive" error on the following code in S3FileTransferManager
 switch threadPoolProvider {
        case .createNew:
            self.threadPool = NIOThreadPool(numberOfThreads: 2)
            self.threadPool.start()
        case .shared(let sharedPool):
            self.threadPool = sharedPool
        }

v1.3.0 should fix this


Web parser

Like the command line tool, use the web build to let users run through an arbitrary yarn script (that they paste in a text field, I guess?) right in their browser.

Have this working in gh-pages branch. Can use here: http://jayhay.me/bondage.js/


Create definition of CRD for Medulla Page

Summary

Create Definition of CRD in KubeOps for Medulla Page

Time Requirements

4 hours

Acceptance Criteria

A Medulla page should be saved to a CRD

The CRD should have a uuid property

The CRD should have a string property which stores an html like structure of components, but don't define the structure, just provide a string property

User Story

As a developer I want to save a page to Kubernetes

Closed for not following issue template.


Added information to the API descriptions, mostly based on informatio…

…n from this link: https://github.com/odota/core/wiki/JSON-Data-Dump. Some of the info is old, so I didn't fill out everything, just things I was very confident in.

do npm run lint to fix the errors.

No more help from me or my data :)  every time you take advantage you might
get error etc :)  gg divine in your dream
On Dec 30, 2017 11:01 AM, "Argn0"<EMAIL_ADDRESS>wrote:

do npm run lint to fix the errors.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/odota/core/pull/1583#issuecomment-354527839, or mute
the thread
https://github.com/notifications/unsubscribe-auth/Ag_7Q0Q1fs6ZOazt0TKtbiYVDIS0jvtRks5tFcOMgaJpZM4RPgFo
.


Delete package-lock.json

Resolves #1009

Pull Request Test Coverage Report for Build 1147

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 52.937%

Totals

Change from base Build 1111:
0.0%

Covered Lines:
3073

Relevant Lines:
5716

💛  - Coveralls

I added package-lock to the .gitignore so we don't run into this issue again.


fix: support line removal in patch tool

The patch tool now properly handles empty content between ======= and >>>>>>> UPDATED, allowing for line removal in patches.
This is done by:

Splitting patch content in multiple steps
Special handling of the case where UPDATED marker follows immediately after DIVIDER
Maintaining compatibility with existing patch formats

[!IMPORTANT]
Enhances patch tool to support line removal by handling empty content between ======= and >>>>>>> UPDATED in patch.py.

Behavior:

Supports line removal in patches by handling empty content between ======= and >>>>>>> UPDATED in patch.py.
Special case handling when UPDATED marker follows immediately after DIVIDER.

Functions:

Modifies _from_codeblock() in Patch class to split patch content in multiple steps and handle empty content cases.

This description was created by  for bc7891d7003fa157c280b58eed73d3a41bd474d0. It will automatically update as commits are pushed.

Codecov Report
Attention: Patch coverage is 80.00000% with 1 line in your changes missing coverage. Please review.

Project coverage is 72.65%. Comparing base (2ade667) to head (bc7891d).
Report is 1 commits behind head on master.

:white_check_mark: All tests successful. No failed tests found.

Files with missing lines
Patch %
Lines

gptme/tools/patch.py
80.00%
1 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #267      +/-   ##
==========================================
- Coverage   72.66%   72.65%   -0.01%
==========================================
  Files          64       64
  Lines        4298     4301       +3
==========================================
+ Hits         3123     3125       +2
- Misses       1175     1176       +1

Flag
Coverage Δ

anthropic/claude-3-haiku-20240307
71.37% <80.00%> (+0.01%)
:arrow_up:

openai/gpt-4o-mini
71.26% <80.00%> (-0.01%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

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

🚨 Try these New Features:

JS Bundle Analysis - Avoid shipping oversized bundles


opt allow to set storage_page_size for tables (#42680)

pick https://github.com/apache/doris/pull/42680

run buildall

run buildall


Can a ColumnOptions.AdditionalColumn PropertyName reference a structured object's property instead of just a scalar property?

Bug Report / Support Request Template

Please clearly describe what the SQL Sink is doing incorrectly:
I'm logging a structured object as a property of the log message.  I created
var logger = Serilog.Log.Logger
.ForContext("User", user, true)
;

Please clearly describe the expected behavior:
Creating the additional column like this.  I'm trying to reference the object's Name property:
new SqlColumn { ColumnName = "User", PropertyName = "User.Name", DataType = SqlDbType.NVarChar, DataLength = 250, AllowNull = true }
The value of this column for this property is not getting populated.  It is always null.  The property is getting structurized properly in the LogEvent column.

I have another additional column that is a simple scalar property and that column is getting populated correctly.

List the names and versions of all Serilog packages used in the project:

Serilog: 2.12.0
Serilog.Sinks.MSSqlServer:  5.7.1
(configuration, etc.)

Target framework and operating system:

[ ] .NET Core 6
[X] .NET Core 3.1
[ ] .NET Framework 4.8
[ ] .NET Framework 4.7
[ ] .NET Framework 4.6.x
OS:

Provide a simple reproduction of your Serilog configuration code:

Provide a simple reproduction of your Serilog configuration file, if any:

Provide a simple reproduction of your application code:

Hi @brianbarnett316!
Unfortunately it does not work that way with the current implementation. Only the name of the property is compared to read the value of the additional column (https://github.com/serilog-mssql/serilog-sinks-mssqlserver/blob/d5ddcd6b1a6cb7a79a5280ca8ee6b3ac6c8e0ea2/src/Serilog.Sinks.MSSqlServer/Sinks/MSSqlServer/Output/PropertiesColumnDataGenerator.cs#L29).
Probably you could use a Serilog Enricher to extract your User.Name value into a separate property and bind that to your AdditionalColumn.

Ok, thanks.  It might be worth noting this behavior in the online doc.  Thanks.

Would you give it a try and describe it as you would like to see it in the doc. I'll be happy to see your PR.


Support runtime level snapshotter for issue 6657

What is this change
This is the implementation for https://github.com/containerd/containerd/issues/6657, the following lists core ideas:

Added snapshotter option in CRI per-runtime config
For containers related operations e.g. create containers, respect the runtime.snapshotter if set, otherwise using the global  snapshotter.

[plugins."io.containerd.grpc.v1.cri".containerd.runtimes.my-runtime]
  snapshotter = "devmapper"

For pull images, given the runtime info is not passed along in the PullImageRequest, we used a configurable annotation key io.kubernetes.cri/runtimehandler to specify runtime during pull time such that the appropriate snapshotter can be used.

Pod sandbox config with annotations specifying the runtime, and image_pull will get the correct snapshotter for unpacking
{
  "metadata": {
    "name": "busybox-sandbox-devmapper",
    "namespace": "default",
    "attempt": 1,
    "uid": "hdishd83djaidwnduwk28bcsb"
  },
  "log_directory": "/tmp",
  "linux": {
  },
  "annotations": {
    "io.kubernetes.cri/runtimehandler": "my-runtime"
  }
}

Testings done

Pull images with annotations will be unpacked as devmapper

crictl pull --pod-config ./podsandbox-config-devmapper.json docker.io/library/busybox:latest

cat ./podsandbox-config-devmapper.json
{
  "metadata": {
    "name": "busybox-sandbox-devmapper",
    "namespace": "default",
    "attempt": 1,
    "uid": "hdishd83djaidwnduwk28bcsb"
  },
  "log_directory": "/tmp",
  "linux": {
  },
  "annotations": {
    "io.kubernetes.cri/runtimehandler": "my-runtime"
  }
}

create pods with my-runtime will be using devmapper snapshotter
create pods with other runtimes will be using overlayfs (default) snapshotter

@AkihiroSuda @ktock @dmcgowan @Random-Liu kindly ping to check if you have more comments? Would appreciate if I can get the action items list to get to ok-to-test ?

/ok-to-test

I'm going to take a more thorough look at this, but my main concern is that there could be cases that arise in CRI where a snapshotter is implied (or one is needed in a context where we don't have a runtime handler), and those parts may not play nicely with this.
For instance:

What happens if you have images pulled with multiple snapshotters and you try to calculate usage for those images. Will the various code paths for this have access to the snapshotter that should be used?
What if the same image is pulled twice, but with two different snapshotters? Will the correct bookkeeping happen?
Presumably Kubelet just tracks images by name, and doesn't know what snapshotter was used. So if image A is pulled by snapshotter 1, then Kubelet will just know that the image is present, and potentially schedule a pod that wants to use A with snapshotter 2.

What happens if you have images pulled with multiple snapshotters and you try to calculate usage for those images. Will the various code paths for this have access to the snapshotter that should be used?
What if the same image is pulled twice, but with two different snapshotters? Will the correct bookkeeping happen?

IMO, it is easy to handle the bookkeeping in containerd side. But the question
is the kubelet side. For different snapshots, those maybe use different storage
as volume. In current CRI-API design, the CRI just uses one storage for image
data and container writable layer. The storage path will be return by
ImageService.ImageFsInfo API.
The eviction manager relies on this FilesystemIdentifier to handle ImageGC
and evict low-priority pods in node to release disk space.
// https://github.com/kubernetes/cri-api/blob/master/pkg/apis/runtime/v1/api.proto#L1400

// FilesystemUsage provides the filesystem usage information.
message FilesystemUsage {
    // Timestamp in nanoseconds at which the information were collected. Must be > 0.
    int64 timestamp = 1;
    // The unique identifier of the filesystem.
    FilesystemIdentifier fs_id = 2;
    // UsedBytes represents the bytes used for images on the filesystem.
    // This may differ from the total bytes used on the filesystem and may not
    // equal CapacityBytes - AvailableBytes.
    UInt64Value used_bytes = 3;
    // InodesUsed represents the inodes used by the images.
    // This may not equal InodesCapacity - InodesAvailable because the underlying
    // filesystem may also be used for purposes other than storing images.
    UInt64Value inodes_used = 4;
}

message ImageFsInfoResponse {
    // Information of image filesystem(s).
    repeated FilesystemUsage image_filesystems = 1;
}

I just bring one case here. But I think it will be big change between kubelet and CRI-container :).

@kevpar these are definitely great questions, as @mikebrow and @fuweid the comprehensive picture seems to be a bigger project and should be driven by a Kep. For now if we can provide an experimental feature, that should unblock us and potentially some other use cases.

What happens if you have images pulled with multiple snapshotters and you try to calculate usage for those images. Will the various code paths for this have access to the snapshotter that should be used?
I think from CRI point of view, separate the usage into per snapshotter should be sufficient. However, it's upto kubelet to interpret the result and make decisions.

A side note, I think for many snapshotter other than overlayfs, kubelet usage accounting is already not reliable. For example for devmapper, it counts total used bytes  correctly but uses the dir of the snapshotter meta dir for total fs bytes and therefore the usage percentage is not accurate. This is probably true for many other snapshotters.
I think all these deserve a KEP for a re-think on kubelet or CRI interactions with different snapshotters.

What if the same image is pulled twice, but with two different snapshotters? Will the correct bookkeeping happen?
Reading from the code, it seems the CRI behavior is clear that it will fetch and unpack for the given snapshotter. But if kubelet decides the image already exists and do not pull again, then the unpacked (by different snapshotters) will be delayed until container creation time. This seems to be harmless, kubelet probably need to be aware of image-runtime to avoid such behavior.

Presumably Kubelet just tracks images by name, and doesn't know what snapshotter was used. So if image A is pulled by snapshotter 1, then Kubelet will just know that the image is present, and potentially schedule a pod that wants to use A with snapshotter 2.

When a pod using snapshotter2 is scheduled on the node with image unpacked with snapshotter1, containerd has the logic to identify the image in unpacked, so it will do the unpack during containerd creation time. This will make the creation slow, but should be harmless IMO (similar to pullImage without the unpack opt).

@mikebrow addressed the following comments:

suggest just make the key a const string

Done

pls mark the const as needing to be removed.. upon a KEP adding the runtime handler to the image services

Done

@fuweid totally agree that CRI is a better place for bookkeeping. I think kubelet has difficulty to get total usage for most snapshotters other than overlayfs. Seems to me ImageService.ImageFsInfo API should return the per-runtime-usage and per-runtime-total, for pod scheduling and image GC. But this requires quite some changes on the kubelet end.

@mikebrow @kevpar @AkihiroSuda friendly ping to see if there's any other comments or any other blocker for merging this PR?

@mikebrow @kevpar @AkihiroSuda friendly ping to see if there's any other comments or any other blocker for merging this PR?

comments provided thank you!

Before merge needs some level of integration testing, or at least some manual testing, to ensure/show reasonable results/responses to the image and all related runtime services with a runtime configured snapshotter, no default snapshotter, two different snapshotters (same image, different image), ...  For the parts missing we'll need an issue opened with a check list tracking the missing parts. Or we could add a checklist to #6657

Before merge needs some level of integration testing, or at least some manual testing, to ensure/show reasonable results/responses to the image, and all related runtime, services with a runtime configured snapshotter, no default snapshotter, two different snapshotters (same image, different image), ... For the parts missing we'll need an issue opened with a check list tracking the missing parts. Or we could add a checklist to #6657

@mikebrow thanks a lot for the input, I've appended the open TODO items here https://github.com/containerd/containerd/issues/6657#issuecomment-1129385189
Totally agreed on the integration test, as you suggested I've manually tested end-to-end with crictl, see the Testing Done in the PR description section. I'm planning to loop back and add CI integration tests in a separate PR, which is also tracked in the TODO list.

looking great on the manual integration (just a few more to make sure these work when two snapshotters are used :-)
on the image services... there is also:

list images
image status
remove image
image fs info
inspect image

then there are a couple related apis...:

info(status of the runtime)
stats(metrics by pod/container)

we can't squash commits on merge in this project.. can you squash your commits pls? Also something happened and you picked up extra commits from derek.. maybe a rebase/merge issue?

looking great on the manual integration (just a few more to make sure these work when two snapshotters are used :-)
on the image services... there is also:

list images
image status
remove image
image fs info
inspect image

then there are a couple related apis...:

info(status of the runtime)
stats(metrics by pod/container)

~we can't squash commits on merge in this project.. can you squash your commits pls? Also something happened and you picked up extra commits from derek.. maybe a rebase/merge issue?~

@mikebrow I've run the mentioned cases and pasted results in the PR description. The output seems to be expected. Also I have squashed all the commits. Would appreciate If you could help merging this PR, thanks for all you help!

igned-off-by: shuaichang<EMAIL_ADDRESS>
Reverted .gitignore and unset runtime.Type in UT

Signed-off-by: shuaichang<EMAIL_ADDRESS>
Changed annotation key to a const, added more logging

Signed-off-by: shuaichang<EMAIL_ADDRESS>
Adjusted logging to highlight experimental

Signed-off-by: shuaichang<EMAIL_ADDRESS>
Added comments into config doc and tweaked logs

Signed-off-by: shuaichang<EMAIL_ADDRESS>
Interating on config documentations

Signed-off-by: shuaichang<EMAIL_ADDRESS>
The commit message should be format(just use one sign-off). It is experimental feature and we know there is limited by current design. I agree to move it forward for the extensibility :)
LGTM
(And I also would like to wait for more LGTMs~)

@fuweid edited the commit message.

@AkihiroSuda @kevpar could you please also sign off the PR if it looks good to you? Appreciate your help!

As @dmcgowan suggested, I've updated the PR to use annotation name within the containerd namespace io.containerd.cri/runtime-handler https://github.com/containerd/containerd/blob/6b9307ad3d12c5ddeac8166af997b27cedf76277/pkg/cri/annotations/annotations.go#L78
@mikebrow @fuweid @kevpar @AkihiroSuda please feel free to comment if there's objection/concerns for the naming, thanks!

@shuaichang Will this feature be available in release 1.6.9?


Cannot deploy application

Hi,
I am following the guide on how to create Windows Server Containers on Azure Kubernetes Service. Link
I pulled the sample image demonstrated in the guide, tagged it and uploaded it to Azure container registry.
Upon deploying the application to Kubernetes, the pods are unable to pull the image from the container registry.
The output of the describe command for one of the pods is shown below
Name:               hello-world-56c76d8549-7248k
Namespace:          default
Priority:           0
PriorityClassName:  <none>
Node:               aksnpwin000000/<IP_ADDRESS>
Start Time:         Sat, 01 Jun 2019 19:33:21 +0530
Labels:             app=hello-world
                    pod-template-hash=56c76d8549
Annotations:        <none>
Status:             Pending
IP:                 <IP_ADDRESS>
Controlled By:      ReplicaSet/hello-world-56c76d8549
Containers:
  hello-world:
    Container ID:
    Image:          pocaspnetcoreweb.azurecr.io/pocaspnetcoreweb:v1
    Image ID:
    Port:           80/TCP
    Host Port:      0/TCP
    State:          Waiting
      Reason:       ImagePullBackOff
    Ready:          False
    Restart Count:  0
    Limits:
      cpu:     1
      memory:  800m
    Requests:
      cpu:        100m
      memory:     300m
    Environment:  <none>
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-m647n (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             False
  ContainersReady   False
  PodScheduled      True
Volumes:
  default-token-m647n:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  default-token-m647n
    Optional:    false
QoS Class:       Burstable
Node-Selectors:  beta.kubernetes.io/os=windows
Tolerations:     node.kubernetes.io/not-ready:NoExecute for 300s
                 node.kubernetes.io/unreachable:NoExecute for 300s
Events:
  Type     Reason          Age                   From                     Message
  ----     ------          ----                  ----                     -------
  Normal   Scheduled       18m                   default-scheduler        Successfully assigned default/hello-world-56c76d8549-7248k to aksnpwin000000
  Normal   SandboxChanged  17m                   kubelet, aksnpwin000000  Pod sandbox changed, it will be killed and re-created.
  Warning  Failed          17m (x3 over 17m)     kubelet, aksnpwin000000  Failed to pull image "pocaspnetcoreweb.azurecr.io/pocaspnetcoreweb:v1": [rpc error: code = Unknown desc = a Windows version 10.0.18362-based image is incompatible with a 10.0.17763 host, rpc error: code = Unknown desc = Error response from daemon: Get https://pocaspnetcoreweb.azurecr.io/v2/pocaspnetcoreweb/manifests/v1: unauthorized: authentication required]
  Normal   Pulling         16m (x4 over 17m)     kubelet, aksnpwin000000  Pulling image "pocaspnetcoreweb.azurecr.io/pocaspnetcoreweb:v1"
  Warning  Failed          2m55s (x65 over 17m)  kubelet, aksnpwin000000  Error: ImagePullBackOff

The Events section has an event with the message
Warning  Failed          17m (x3 over 17m)     kubelet, aksnpwin000000  Failed to pull image "pocaspnetcoreweb.azurecr.io/pocaspnetcoreweb:v1": [rpc error: code = Unknown desc = a Windows version 10.0.18362-based image is incompatible with a 10.0.17763 host, rpc error: code = Unknown desc = Error response from daemon: Get https://pocaspnetcoreweb.azurecr.io/v2/pocaspnetcoreweb/manifests/v1: unauthorized: authentication required]

The message seems clear enough to me since it complaints about the windows version mismatch between the container host and the node. Am I right about it? If yes, then how do I make sure that the version match.
My kubernetes deployment file(has 1-2 minor changes from the one given in the sample).
apiVersion: apps/v1
kind: Deployment
metadata:
  name: hello-world
  labels:
    app: hello-world
spec:
  replicas: 1
  template:
    metadata:
      name: hello-world
      labels:
        app: hello-world
    spec:
      nodeSelector:
        "beta.kubernetes.io/os": windows
      containers:
      - name: hello-world
        image: pocaspnetcoreweb.azurecr.io/pocaspnetcoreweb:v1
        resources:
          limits:
            cpu: 1
            memory: 800m
          requests:
            cpu: .1
            memory: 300m
        ports:
          - containerPort: 80
      imagePullSecrets:
      - name: acr-auth
  selector:
    matchLabels:
      app: hello-world
---
apiVersion: v1
kind: Service
metadata:
  name: hello-world
spec:
  type: LoadBalancer
  ports:
  - protocol: TCP
    port: 80
  selector:
    app: sample

Any help would be appreciated. Thank you!

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 6de70aec-9ebe-5655-6657-5c171de374b1
Version Independent ID: c9eb35c8-8703-511b-987b-e2a441be2e47
Content: Preview - Create a Windows Server container on an Azure Kubernetes Service (AKS) cluster
Content Source: articles/aks/windows-container-cli.md
Service: container-service
GitHub Login: @TylerMSFT
Microsoft Alias: twhitney

Thanks for the feedback! We are currently investigating and will update you shortly.

@srv-twry Can you give me the base image for pocaspnetcoreweb.azurecr.io/pocaspnetcoreweb:v1

@jakaruna-MSFT
Hi, As I mentioned already, I just pulled the mcr.microsoft.com/dotnet/framework/samples:aspnetapp image from docker hub as mentioned in the guide, tagged it with the required name and pushed it to ACR.

@srv-twry
The error is quite obvious: The kubelet has reported that it doesn't support image based on 10.0.18362 and this is equal to Windows Server 1903. Unfortunately, AKS is using 10.0.17763, this is equal to Windows Server 2019, This means AKS supports Windows Server 2019 and the OS it runs is also using Windows Server 2019.
According to  MS' Docker Hub of .NET Framework Samples the tag of mcr.microsoft.com/dotnet/framework/samples:aspnetapp is using Windows Server Core 1903 by default:

Therefore, I suggest that you should base your image on Windows Server 2019 based image:
mcr.microsoft.com/dotnet/framework/samples:aspnetapp-windowsservercore-ltsc2019
To @jakaruna-MSFT
The documentation should clarify clearly that Azure Kubernetes Service doesn't support Windows Server 1903 based image. Please update the doc page. User should be aware and informed about this kind of Docker's Windows based image default supported OS and compared with AKS latest supported OS for Windows based images.

@srv-twry - sorry for the frustration. I have just been assigned this content and will update which image to use in the topic.

@eriawan Thank you!
@TylerMSFT No worries! I was able to successfully deploy the application using mcr.microsoft.com/dotnet/framework/samples:aspnetapp-windowsservercore-ltsc2019 image.

@TylerMSFT I have assigned this issue to you.

@TylerMSFT
Could we have update in this AKS doc page on which OS is supported and also clarification that 1903 (10.0.18362) based image is not supported?

Hi,
I don't think it's true that 1903 (10.0.18362) is not supported. I think something else went wrong in @srv-twry's journey. Following the doc works fine for me.
#please-close

@TylerMSFT
Hi, what went wrong is that the nodes created in the windows node pool were running the 10.0.17763 version. Hence I should have used the sample for that version and not the 1903 version. This I was already able to figure out from the logs. My question asked in the issue description is still unanswered though, so I'll ask it again.
When a user is creating a windows node pool to be added to an existing AKS cluster, Is it possible that he/she can also specify that this node pool should contain nodes running a specific windows version?
For eg. Can I say that "hey in this node pool, create 2 nodes both of which should be running the 1903 version"?

@srv-twry

When a user is creating a windows node pool to be added to an existing AKS cluster, Is it possible that he/she can also specify that this node pool should contain nodes running a specific windows version?

No. You can't define the version of Windows server when creating a node, just as you can't define the version of Ubuntu on a Linux node.

Any updates?
We have the problem that we can't build our images on base image **-windowsservercore-ltsc2019 because it has not up to date root certs.


[6.0] Align swift sdk configuration subcommand with proposal text

Explanation: Per the proposal text:

swift sdk configure <identifier> <target-triple>, which allows users to provide additional search paths and toolsets to be used subsequently when building with a given Swift SDK. Specifically, multiple --swift-resources-path, --include-search-path, --library-search-path, and --toolset options with corresponding paths can be provided, which then will be stored as configuration for this Swift SDK. swift sdk configure <identifier> --show-configuration will print currently set paths, while swift sdk configure <identifier> --reset will reset all of those at once.

Scope: Isolated to swift sdk subcommands.
Risk: Low due to isolation and added end-to-end tests.
Testing: Added Tests/CommandsTests/SwiftSDKCommandTests.swift
Issue: N/A
Reviewer: @bnbarham

@swift-ci test


v0.19 release preparations

This became a huge rewrite with a move to wxWidgets (among other things).

Soon™

If you're eager the preview binaries are on AppVeyor. There's a few things missing but mostly it'll work as it should :)

Yay

And it works 👍

Using latest build magnet links don't open a dialog for adding torrent...

@TechAdvancedCyborg I haven't had time to implement that 100% yet, all pieces are there but the final things are missing. Thanks for bringing it to my attention!

Np, thank you so much for taking the time to make this piece of software!

@vktr Truly amazing job! Thank you!
Issue:
Tray Icon context menu 'exit' not functional
Running latest 0.19 portable build on Windows 10 version 1909.
Steps to reproduce
When clicking exit in notification area icon context menu, the app does not exit.
Preferences set to minimizing and closing to tray although changing these to default does not solve the issue.

Context menu doesn't even show up for me... :(

@vurghus-minar thanks for reporting! I'll fix it.
@TechAdvancedCyborg are you right clicking the tray icon?

It didn't work at first then it did...

Odd - let me know if you figure out how to reproduce it 🤔 Yeah, I'll fix exit. Thanks for testing!!

Yup

wxWidgets again. The phoenix rises again.

@TechAdvancedCyborg when PicoTorrent crashes, do you get the dialog telling you it crashed?

Nope

Nothing just crashes

Thanks, I'll look into it

Also, I am not on the latest build because Appveyor can't find packages on build.

Restoring NuGet package WiX.3.11.1.
WARNING: Unable to find version '0.33.0' of package 'Cake'.
WARNING: Unable to find version '3.11.1' of package 'WiX'.
Could not find Cake.exe
At C:\projects\picotorrent\build.ps1:51 char:5
+     Throw "Could not find Cake.exe"
+     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OperationStopped: (Could not find Cake.exe:String) [], RuntimeException
    + FullyQualifiedErrorId : Could not find Cake.exe

Command exited with code 1```

Thank you!

Dunno why AppVeyor couldn't find Cake, probably an intermittent error. Anyways, I can reproduce the issue so I'll make sure to push a fix for it.

@TechAdvancedCyborg The builds are working again :)

Yup I saw, thanks! 👍

v0.19 is out!

@TechAdvancedCyborg Almost :) There's a few more preparations, but quite soon!


remove YEAR from boilerplate

What type of PR is this?
kind/enhancement
What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

Codecov Report

Merging #230 (42278d2) into main (20bb459) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head 42278d2 differs from pull request most recent head d0c96a4. Consider uploading reports for the commit d0c96a4 to get more accurate results

@@           Coverage Diff           @@
##             main     #230   +/-   ##
=======================================
  Coverage   10.26%   10.26%
=======================================
  Files          39       39
  Lines        4237     4237
=======================================
  Hits          435      435
  Misses       3771     3771
  Partials       31       31

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 20bb459...d0c96a4. Read the comment docs.


Users should be redirected to /admin after login in

Steps to reproduce

Log in with valid credentials

Expected result

User is redirected to /admin

Actual result

User is redirected to the public site

#58 fixes the issue


Fixed compilation error in tests.cpp when not building with TESTS=1

Compilation fails when building without TESTS enabled, because we are not using std namespace. (You can have a look at #else part of src/tests.cpp. This can be fixed by adding
using namespace std;

So cout and endl symbols are imported properly during compilation.
This patch fixes the above error.

Hi Narasimha,
Thanks for reporting this problem! I'm happy that you're interested in this project as well :-)
Getting to the point: using namespace std is generally considered a "bad practice"
in C++. See: https://stackoverflow.com/questions/1452721/
While it's OK for very small projects (I used it in mylang until recently), the
project now seems too big for that and I spent some effort removing it from everywhere.
While doing that, I introduced the file defs.h with some using statements like:
using std::cin;
using std::cout;
using std::cerr;
using std::ostream;
using std::endl;

And, in theory, I included the file "everywhere". The idea is that only a very limited set of types and functions
in std are freely usable without the namespace prefix. The rest, require the std:: prefix especially in header
files (.h). In source files instead (.cpp, .cpp.h), it's possible to add additional using std::<something> statements
at the beginning of the file, but that's OK only if there many instances of a given type.
In conclusion, the right fix here is to just add #include "defs.h" before the first #include <iostream> in tests.cpp.
Would you like to update your pull request this way?
Thanks,
Vlad

@vvaltchev , Hi, Thanks,  I have made the necessary changes in the latest commit.
Also, another issue, the interpreter throws syntax error for samples/fib, it cannot handle multiple variable declarations in the same line. To be more specific, the syntax error is in line 5 of samples/fib

@Narasimha1997 thanks for reporting this as well. I just fixed it.
What happened: initially, mylang supported that classic syntax:
var a=1,b=2,c=3;

But later I decided that's incompatible with a new nicer feature called "array expansion",
so I dropped it and I forgot to fix the sample. The array expansion feature allows things like:
var a,b = [3, 10];
a, b += [1, 2]; # increase a by 1 and b by 2
a, b += 10; # increase both a and b by 10

Which is super-cool to me, especially in foreach loops. If you're curious, check the readme
branch, where I'm writing some documentation in the README.md file.


Add smtp output binding

Description
Add documentation on how to setup the SMTP output binding.
Issue reference
#1145

@msfussell please review


Get rid of module initialization hacks and hardcodings

No more cheating and hardcoding available modules.
Introduce ModuleInitRegistry
Make fedimint-wallet initialize its bitcoin_rpc (see https://github.com/fedimint/fedimint/pull/1202#issuecomment-1373993690 )
Inject fake BitcoinRpc in tests via other means.

The end-binary is supposed to initialize ModuleInitRegistry only, and from there
all the decoders, modules, config generation is supposed to happen.
Created #1231 #1232 to follow up with cleaning, but it is already large, so maybe we can just land.

I still need to figure out a way to allow injecting a fake BitcoinRpc into a test setup. I kind of forgot about it. Working on it.

Sounds great -- but I don't understand this stuff at all so don't feel comfortable approving

Possibly Eric and me do on top of our head, so how are we going to get another approval? :P

Possibly only Eric and me do on top of our head, so how are we going to get another approval? :P

OK, since you asked nicely 😆 (but we need to do a thursday deep dive on modularization soon!)

@elsirion @justinmoon Had to rebase due to conflict (deleted configgen)