SDCARD Write/Read

@aiden-ct  Thank you for commit to WriteBlock().
I tested at that time but I gave up to develop SDCARD Fat fs.
I trying to develop it again.
I tried to write and read blocks, from 0 to the end.
I used to SDCARD of Sandisk microSD HC1 class 4, 4GB capacity.
But I got too many errors to write and read till the end. The SPI clock was 250KHz, 2MHz, 20MHz.
When I got errors, I try to do SD_Close(), SPIMaster_Close() and SPIMaster_Open(), SD_Open() to retry to failed block. Well, it works.
But, I wonder is it right or not.
Is it possible to clearly(I mean without error)write and read all blocks?
And, if you can tell me the details of the SDCARD you tested.

@taylor-an - let me know how you get on and if my patch fixes things for you.

@taylor-an - let me know how you get on and if my patch fixes things for you.

@aiden-ct Thank you.
It works very well. I can't see any errors.

@aiden-ct Thank you.
It works very well. I can't see any errors.

Great. Thanks for the bug report.

Great. Thanks for the bug report.


Add MP3 music to Exists Jcodec MP4 in android

Hi, before everything, thanks for this pure library.
i simply created MP4 video by jcodec with simple code on android:
String image = Environment.getExternalStorageDirectory() + "/test.jpg";

File video = new File (Environment.getExternalStorageDirectory(), "output.mp4");

AndroidSequenceEncoder sequenceEncoder =
     AndroidSequenceEncoder.createSequenceEncoder(video, 2);

Bitmap bitmap = BitmapFactory.decodeFile(image);

for (int i=0; i<100; i++) {
    sequenceEncoder.encodeImage(bitmap);
}

sequenceEncoder.finish();

//ouput is 50sec mp4 video without sound

so my video is 50sec without sound. i want add mp3 music to this mp4 video in android. what is best solution? (ffmpeg javacv  is complex native libs and hard to use) (mp4parser is not support mp3)
we can merge mp4 and m4a(AAC) by android mediamuxer. but i can not convert mp3 to aac :|
thanks for help.

Hi, depending on your specific need this may or may not be supported in JCodec.
Which of the cases below describes your situation:

You have an AAC sound and want to add it to the movie.
You have a MP3 sound and want to add it to the movie.
You have an uncompressed sound and want to convert it to MP3 and add it to the movie.
You have an uncompressed sound and want to convert it to AAC and add it to the movie.
You have a MP3 sound and want to convert it to AAC and add it to the movie.

Please let me know.

@svitvitskiy  I Have a MP3 sound and i want add it to the movie (MP4 video that created by jcodec).

Just created 3 enhancement requests (issue #246, #247 and #248).
After they are all done you should be able to specify the background sound file in the sequence encoder. I'll post the status here.

@svitvitskiy Ok, I will check. thanks

How could I do about Add MP3 music to Exists Jcodec MP4 in android!

@lvxiaolongde, you'll need to wait for feature #246 to be able to do that.

@svitvitskiy yourself can you add this feature(add mp3 to mp4 or convert mp3 to aac{m4a}) to this library? is very fun if install ffmpeg only only for add mp3 :| ffmpeg is large and complex lib to use :| and size of apk android app after suer ffmpeg : 20mb :| but by jecodec without change size apk : 4mb

@svitvitskiy any update on this


Assume schema interpreter

Diff:
https://github.com/egraphs-good/eggcc/compare/oflatt-assume-sugar..oflatt-assume-interpreter

trying again on this PR due to git history issues


No option to automatically terminate previous task when a new instance of the same task is started

VSCode Version:  1.14.2
OS Version: Windows 10 Creators Update

This is just a suggestion.
Almost all IDEs allow us to set a 'Single Instance Only' option, When this option is true, And you try to run a task that is already running, It'll kill the running task and then restart it.
VS Code gives an error stating that the task is already running, go to F1->Terminate Task to terminate the task.
This gets really annoying on some machines where to access Function keys, You also need to hold down a separate  "Fn" key.
My suggestion is to let people specify a SingleInstanceOnly option in tasks.json, If this option is true, then instead of giving an error to user, It should kill the existing task and restart it.
And if this option is false, Then just do what it does currently.
Default value should be false, So, Only the people who really need this option can set it and others will see the usual behavior
And, I'd like to work on this, if that's okay.
Regards
Ishan

@ishanjain28 the request makes sense and PRs are always welcome.

@dbaeumer So, I'll start working on it.

Hi, @dbaeumer, Submitted a PR to add this feature here

It seems like this should be three options:

Prompt (current behavior)
Restart
Use existing

Hi! I'd be glad to continue working on this from where we left off with this PR. Let me know if there's anything else I should know.

I think this comment has the most useful and up to date information. To make review easier and faster, I recommend making two PRs, one for instanceLimit and one for instancePolicy and finishing one before starting the next (assuming you wanted to implement both).

Note: people subscribed to this issue may want to follow #90125 (for instancePolicy) instead now, which is the second part required for the behavior originally described here to work. With the instanceLimit that has been added, there is still a prompt.


Header casing

The headers can be either Uppercased o lowercased, based on how they have been written. I think we should lowercase every key by default, to avoid confusion.
test('headers casing', (t) => {
  t.plan(4)

  const server = createServer((req, res) => {
    res.writeHead(200, {
      'content-type': 'text/plain',
      Foo: 'Bar'
    })
    res.end('hello')
  })
  t.tearDown(server.close.bind(server))

  server.listen(0, () => {
    const client = new Client(`http://localhost:${server.address().port}`)
    t.tearDown(client.close.bind(client))

    client.request({ path: '/', method: 'GET' }, (err, { statusCode, headers, body }) => {
      t.error(err)
      t.strictEqual(headers['content-type'], 'text/plain')
      t.strictEqual(headers.foo, 'Bar') // This fails
      const bufs = []
      body.on('data', (buf) => {
        bufs.push(buf)
      })
      body.on('end', () => {
        t.strictEqual('hello', Buffer.concat(bufs).toString('utf8'))
      })
    })
  })
})

This has performance implications and HTTP header handling should be case insensitive. I would prefer we don't touch them.

Should this be an option?

I agree that this might cause some performance slowdown, but if we don't lowercase all headers by default (in the response), then all of our users will need to log the headers before writing their code because they can't know in advance the casing of the headers.
Finally, I think we should behave in the same way as Node.js core, as I believe that keeping the code as-is, will bite us in the future.

In fact, I've noticed this behavior because I was trying to port the current test in the Elasticsearch client to use undici, and every header check started failing.

So an option which is enabled by default?

An option enabled by default could work, but I don't think anyone will ever change this, because it might save you a few milliseconds (did we measure how many?), but it adds a lot of complexity afterward, as you don't really know the casing of the headers.

In Fastify we are lowercasing everything by default, and I don't think it causes a degradation in performances that justifies the complexity of supporting different solutions: https://github.com/fastify/fastify/blob/8b8485ac5ff56d1ead387f6dd76384f996a2cf8e/lib/reply.js#L162-L210

I did some benchmarks:
With key.toLowerCase():
~/Development/undici  master ✗                                                        4h17m ⚑  ⍉
▶ node benchmarks/index.js
http - keepalive - pipe x 8,719 ops/sec ±7.94% (71 runs sampled)
undici - request - pipe x 11,290 ops/sec ±12.67% (73 runs sampled)
undici - pipeline - pipe x 9,305 ops/sec ±4.41% (75 runs sampled)
undici - stream - pipe x 12,794 ops/sec ±3.98% (76 runs sampled)

~/Development/undici  master ✗                                                         4h18m ⚑
▶ node benchmarks/index.js
http - keepalive - pipe x 9,167 ops/sec ±4.51% (72 runs sampled)
undici - request - pipe x 11,624 ops/sec ±6.34% (71 runs sampled)
undici - pipeline - pipe x 9,289 ops/sec ±10.42% (76 runs sampled)
undici - stream - pipe x 12,814 ops/sec ±4.25% (75 runs sampled)

Without key.toLowerCase():
~/Development/undici  master ✗                                                         4h18m ⚑
▶ node benchmarks/index.js
http - keepalive - pipe x 9,504 ops/sec ±4.29% (73 runs sampled)
undici - request - pipe x 11,948 ops/sec ±4.65% (71 runs sampled)
undici - pipeline - pipe x 9,391 ops/sec ±6.52% (75 runs sampled)
undici - stream - pipe x 13,161 ops/sec ±3.71% (80 runs sampled)

~/Development/undici  master ✗                                                         4h19m ⚑
▶ node benchmarks/index.js
http - keepalive - pipe x 9,254 ops/sec ±4.39% (74 runs sampled)
undici - request - pipe x 10,315 ops/sec ±13.93% (68 runs sampled)
undici - pipeline - pipe x 8,941 ops/sec ±7.72% (71 runs sampled)
undici - stream - pipe x 12,642 ops/sec ±4.01% (74 runs sampled)

The server code:
const { createServer } = require('http')

createServer((req, res) => {
  res.writeHead(200, {
    'content-type': 'text/plain',
    'X-Foo': 'Bar'
  })
  res.end('hello world')
}).listen(3000)

I don't see a sensible difference :)


How I can close all subgrids to display another subgrid i version 1.4.2

hello
I am making a grid with subgrid
my question is
How I can close all subgrids to display another subgrid i version 1.4.2?
regards

Please post your questions to w2ui.com comments section or stackoverflow. The issue section is only for bugs.


Please make com.gradle.plugin-publish open source

Expected Behavior
The plugin publishing plugin should be open sourced since it is used by many gradle plugins to publish to a repository.
Current Behavior
The plugin currently is in an internal repository.
Context
I am trying to come up with a solution to package java programs that use gradle as their build system in Gentoo Linux. As most users build everything from source, using the internal plugin cannot be avoided which might become an issue for users who want their whole system to be built from source and not have any proprietary/internal code.

Please do not close this issue as stale. Everyone should agree that it makes more sense if it becomes open source.

The sources are published in JARS on the Gradle Plugin Portal, although they are not convenient to access and it would be much easier if they were shared on GitHub
https://plugins.gradle.org/m2/com/gradle/publish/plugin-publish-plugin/1.2.0/
It's also not clear what the license is. The JAR itself contains an Apache License 2.0, but the sources JAR does not contain a license. There's no license information in the POM either.


Improve recipe path readability on recipes list

Is your enhancement related to a problem? Please describe
Following discussion on https://github.com/containers/podman-desktop-extension-ai-lab/pull/1199
The current path uses text-ellipsis to hide the overflow.

Describe the solution you'd like
Auto horizontal scroller on hover
https://github.com/containers/podman-desktop-extension-ai-lab/assets/42176370/ee2c9867-ce3e-47c1-bf74-62430b62e3b6
branch ref https://github.com/axel7083/ai-studio/tree/feature/hover-scroller-component
Tooltip
Tooltip is a bit complicated, as the path is a bit long, so in a lot of cases the tip is partially hidden, and we could try enforcing the position, but depending on the position of the grid, we are facing different overflow problem.
Copy cursor
In addition of the path, user will probably want to copy it, we might replace the default cursor by a copy icon, and allow on click to add it to the clipboard.
Describe alternatives you've considered
No response
Additional context
No response

Closing in favor of https://github.com/containers/podman-desktop-extension-ai-lab/issues/1980


When messing around with Import / Watched Folders filelocation is not updated

3.7 beta
During my curent issue (Files from Drop Folder are not moved to Drop destination) I started playing around with th settings a little bit. Before I hade
Anime\ as to be watched for new files, Anime\Drop as Drop Source and Anime_2016 as drop Destination. As I read that "watch for new Files" option will leave them in the Folder and the drop folder was as it's a subfolder of Anime also watched - maybe taht's teh reason (even if it worked for years now). OK - I have changed the path to Anime\Year_2015, Aniem\Year_2016 and so on, moved the files and rerun the import (expecting that the Fiel path will be correceted - as it was in the past - but - no. The files are shown with an exclamation mark with the old paths (only a small number are showing the corect one) and - when checking at the Files Tab in JMM Desktop (Collection - Series - Files) the correct path is shown?! And I can open the folder from that view without problems.
When running the Importer it only shows entries like that:
[2016-11-15 18:40:39:539] Info|BackgroundWorker.OnDoWork => MainWindow.workerImport_DoWork => Importer.RunImport_NewFiles Processing File 3272/22161 --- \\<IP_ADDRESS>\Anime\Year\_2013\Strike the Blood\[HorribleSubs] Strike the Blood - 18 [720p].nfo [2016-11-15 18:40:39:539] Info|BackgroundWorker.OnDoWork => MainWindow.workerImport_DoWork => Importer.RunImport_NewFiles Processing File 3273/22161 --- \\<IP_ADDRESS>\Anime\Year\_2013\Strike the Blood\[HorribleSubs] Strike the Blood - 19 [720p].nfo [2016-11-15 18:40:39:539] Info|BackgroundWorker.OnDoWork => MainWindow.workerImport_DoWork => Importer.RunImport_NewFiles Processing File 3274/22161 --- \\<IP_ADDRESS>\Anime\Year\_2013\Strike the Blood\[HorribleSubs] Strike the Blood - 20 [720p].nfo [2016-11-15 18:40:39:555] Info|BackgroundWorker.OnDoWork => MainWindow.workerImport_DoWork => Importer.RunImport_NewFiles Processing File 3275/22161 --- \\<IP_ADDRESS>\Anime\Year\_2013\Strike the Blood\[HorribleSubs] Strike the Blood - 21 [720p].nfo

Try running Remove Missing Files and Run Import.

I did ... same result.
Am 27.11.2016 00:38 schrieb "ElementalCrisis"<EMAIL_ADDRESS>
Try running Remove Missing Files and Run Import.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/japanesemediamanager/ShokoServer/issues/513#issuecomment-263092597,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AV3yjBAfXe6x3GUsbqSVVSAaZ8oVBltEks5rCMLpgaJpZM4KzAPC
.

Hmm, are the local paths correct? If Server is on another computer they should reflect the path from your computer to the computer Server is on.

Yes They are. I am Running now a  complete new import (again) to see if it
will work ...
Am 27.11.2016 00:44 schrieb "ElementalCrisis"<EMAIL_ADDRESS>
Hmm, are the local paths correct? If Server is on another computer they
should reflect the path from your computer to the computer Server is on.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/japanesemediamanager/ShokoServer/issues/513#issuecomment-263092786,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AV3yjJEUeNURQdHMHky5fQS60Vi904Lhks5rCMRBgaJpZM4KzAPC
.

It is no configuration issue for Sure.
Am 27.11.2016 12:44 Vorm. schrieb "ElementalCrisis" <
<EMAIL_ADDRESS>
Hmm, are the local paths correct? If Server is on another computer they
should reflect the path from your computer to the computer Server is on.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/japanesemediamanager/ShokoServer/issues/513#issuecomment-263092786,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AV3yjJEUeNURQdHMHky5fQS60Vi904Lhks5rCMRBgaJpZM4KzAPC
.

Any ideas @maxpiva?

I really don't know, can anyone explain me where is the bug? Is the path \<IP_ADDRESS>\Anime\Year_2013
Correct, Belonging to one of the import folder.
For sure, if you play with the import folders, and there is hash to be made in the queue, some problems may arise, since the command takes the entire filename, if you rename your import folder, the path in the command will be no longer valid.

This should be fixed now with the recent changes.

I added some files, then renamed folder and changed import folder path, then pressed run import, no new files were found. So looks like its fixed.


BUG: Loader header are null if the loader uses defer

Test case for #5345

Thanks! Brought these over into #5627


Integrate concepts tool into STG plugin

[ ] Add Concepts menu in STG plugin.
[ ] Implement importing of concepts from a .hs file.
[ ] Implement authoring of smaller test concepts in dialog for translation to STG.
[ ] Add helpful error messages in case of GHC not being installed/concepts being wrong/concepts not installed.

Just to clarify, do we go for a dedicated Concepts menu or would it be sufficient to have it as one of the importers from .hs file (similar to import from .g and .sg files)?

Personally I would prefer a Concepts menu, for both importing from a .hs file, and writing small concepts in a dialog for quick tests in the STG plugin.
I was also aiming to set it as an importer for the File > Import menu.
Is this OK?
If you would prefer, we could put this in the Conversion menu which already exists in the STG plugin as that is effectively what we're doing. This would save menu bar space.

I think this should be implemented as an import plugin (for Import menu).  Having it in under Concepts menu may also make sense, especially if there is more than one menu item related to concepts. We can experiment with the menus/submenus later.

I can do that.
Can I put this within the STGplugin, or would it be best having a separate ConceptsPlugin?

I would put the importer in org.workcraft.plugin.stg.interop, similar to DotGImporter class and create a package org.workcraft.plugin.stg.concepts for all the parsing and backend calling stuff.


Windows 2019 virtual environment image fail on python installation

Describe the bug
Python installation fails on a windows 2019 virtual environments. The windows 2019 image was working january 27. Seems to be from the change of toolcache_registry to github_feed_token on this PR : https://github.com/actions/virtual-environments/commit/0967620111f1f4543c47b02017685ee587daeeda
Area for Triage:
Python
Question, Bug, or Feature?:

Virtual environments affected

[ ] macOS 10.15
[ ] Ubuntu 16.04 LTS
[ ] Ubuntu 18.04 LTS
[ ] Windows Server 2016 R2
[X] Windows Server 2019

Expected behavior
Python installation works
Actual behavior
Python installation fails
Logs :
2020-02-03T16:59:32.0089629Z     vhd: Installing npm<EMAIL_ADDRESS>from https://npm.pkg.github.com/ 2020-02-03T16:59:32.0095021Z ==> vhd: NPMFeed-AuthSetup : Cannot bind argument to parameter 'AccessToken' because it is an empty string. 2020-02-03T16:59:32.0100184Z ==> vhd: At C:\Windows\Temp\script-5e383898-a578-b289-d3e3-f070c5bcd08a.ps1:63 char:32 2020-02-03T16:59:32.0105492Z ==> vhd: + NPMFeed-AuthSetup -AccessToken $AccessToken -FeedPrefix $FeedPrefix 2020-02-03T16:59:32.0110215Z ==> vhd: +                                ~~~~~~~~~~~~ 2020-02-03T16:59:32.0116483Z ==> vhd:     + CategoryInfo          : InvalidData: (:) [NPMFeed-AuthSetup], ParameterBindingValidationException 2020-02-03T16:59:32.0120793Z ==> vhd:     + FullyQualifiedErrorId : ParameterArgumentValidationErrorEmptyStringNotAllowed,NPMFeed-AuthSetup 2020-02-03T16:59:32.0123377Z ==> vhd: 2020-02-03T16:59:32.5909810Z     vhd<EMAIL_ADDRESS>installation failure;  Error: 1 2020-02-03T16:59:32.5914379Z ==> vhd: npm ERR! code E401 2020-02-03T16:59:32.5921449Z ==> vhd: npm ERR! Unable to authenticate, need: Basic realm="GitHub Package Registry" 2020-02-03T16:59:32.5924677Z ==> vhd: 2020-02-03T16:59:32.5930783Z ==> vhd: npm ERR!      C:\npm\cache\_logs\2020-02-03T16_59_32_519Z-debug.log

Hi @jprioux160
You need to specify your GitHub token to be able to download these packages during image generation:
https://github.com/orgs/actions/packages

Oh right! Thank you for your quick reply !


Minimal Android version?

Hi,
I can't get your plugin working on android. The app crash on start. I don't know how to go on with the problem. I have placed the google-services.json in the app Folder and it is also in the platform/android folder. But it is not located in the built APK file. Is this wrong? I am working with android API level 21, is it a problem?
Please help me. Thank you very much.
Moritz

KitKat didnt work, now using Api 24 and fine.

On android logcat should give you more information on what is causing the crash.
Anything in there?


toBePointGeometry

Description
This is a building block matcher. Geometries are the basis of all objects, and we need a way to reliably test that they have been formatted appropriately.
This matcher focuses only on "Point". All coordinates must be valid coordinates per the WGS-84 standard. Any non-conforming values should fail. However, the "coordinates" property MAY have an empty array ([ ]) as a valid value.

A Geometry object represents points, curves, and surfaces in coordinate space.  Every Geometry object is a GeoJSON object no matter where it occurs in a GeoJSON text.

The value of a Geometry object's "type" member MUST be one of the seven geometry types (per Section 1.4: "Point", "MultiPoint", "LineString", "MultiLineString", "Polygon", "MultiPolygon", and "GeometryCollection").
A GeoJSON Geometry object of any type other than "GeometryCollection" has a member with the name "coordinates". The value of the "coordinates" member is an array.  The structure of the elements in this array is determined by the type of geometry.  GeoJSON processors MAY interpret Geometry objects with empty "coordinates" arrays as null objects.

~https://datatracker.ietf.org/doc/html/rfc7946#section-3.1

For type "Point", the "coordinates" member is a single position.
https://datatracker.ietf.org/doc/html/rfc7946#section-3.1.2

The geometry object should have a "type" and a "coordinates" property. It is prohibited from having a "geometry", "properties", or "features" property.

Implementations MUST NOT change the semantics of GeoJSON members and types.
The GeoJSON "coordinates" and "geometries" members define Geometry objects.  FeatureCollection and Feature objects, respectively, MUST NOT contain a "coordinates" or "geometries" member.
The GeoJSON "geometry" and "properties" members define a Feature object.  FeatureCollection and Geometry objects, respectively, MUST NOT contain a "geometry" or "properties" member.
The GeoJSON "features" member defines a FeatureCollection object. Feature and Geometry objects, respectively, MUST NOT contain a "features" member.
https://datatracker.ietf.org/doc/html/rfc7946#section-7.1

Although illogical, it is NOT PROHIBITED from having a "geometries" property, although if present it would be considered a foreign member.
Other foreign members ARE allowed (see https://datatracker.ietf.org/doc/html/rfc7946#section-6.1). None of these foreign members should get checked for validity of any type; they may contain anything that is valid JSON.
See GeoJSON Spec: What does it mean to extend GeoJSON without using a foreign member? for further clarification.
Valid GeoJSON Point Geometry Examples
A two dimensional of point:
{
    "type": "Point",
    "coordinates": [100.0, 0.0]
}

A three dimensional of point:
{
    "type": "Point",
    "coordinates": [100.0, 0.0, 2000]
}

An empty coordinate
{
    "type": "Point",
    "coordinates": [ ]
}

Contained as an object within a geometries array on a GeometryCollection:
{
    "type": "GeometryCollection",
    "geometries": [{
        "type": "Point",
        "coordinates": [100.0, 0.0]
    }, {
        "type": "LineString",
        "coordinates": [
            [101.0, 0.0],
            [102.0, 1.0]
        ]
    }]
}

In each case, the matcher should only get passed the object in its entirety, not the individual components, and not as part of another collection object.
Example Matcher Usage
const point1 = {
    type: "Point",
    coordinates: [100.0, 0.0]
}
const point2 = {
    type: "Point",
    coordinates: [100.0, 0.0, 2000]
}
const point3 = {
    type: "LineString",
    coordinates: [
        [101.0, 0.0],
        [102.0, 1.0]
    ]
}

expect(point1).toBePointGeometry()
expect(point2).toBePointGeometry()

expect(point3).not.toBePointGeometry()
expect([22, -34.549, 22]).not.toBePointGeometry()
expect({coordinates: [100.0, 0.0]}).not.toBePointGeometry()

Passing Tests
This matcher does not test coordinate validity. Either two or three digit coordinates are allowed.
Values in Range

2D Point

const testPoint = {
    type: "Point",
    coordinates: [25, 10.2]
}

3D Point

const testPoint = {
    type: "Point",
    coordinates: [-100.0, -15.0, 2000]
}

Empty Coordinate

const testPoint = {
    type: "Point",
    coordinates: [ ]
}

Foreign Properties Allowed

ID (String and number input: Test 1, 1

const testPoint = {
    type: "Point",
    id: <input>,
    coordinates: [25, 90]
}

Non alphanumeric ID
ID Normally needs to be a letter or number, but because it is a foreign member on a geometry object, the GeoJSON standard takes no consideration about it.

const testPoint1 = {
    type: "Point",
    id: null,
    coordinates: [25, 90]
}

Geometries

const testPoint2 = {
    type: "Point",
    geometries: testPoint1,
    coordinates: [-100.0, -15.0, 2000]
}

Multiple

const testPoint3 = {
    type: "Point",
    someRandomProp: true,
    geometries: testPoint2,
    coordinates: [180, 10.2, -125]
}

Failing Tests
Geometry Input Not an Object
Any of the following inputs to the matcher should fail:

undefined
null
Booleans: true, false
Numbers: 200, -200, Infinity, -Infinity, NaN
Arrays: [{ coordinates: [0, 0] }]
Strings: '', 'Random Geometry', '[0, 0]', '[[0, 0], [0, 0]]'
Stringified JSON:JSON.stringify({
    type: "Point",
    coordinates: [25, 90]
})

Invalid Coordinates

Each of the values from "Geometry Input Not an Object":

const testPoint = {
    type: "Point",
    coordinates: <input>
}

Coordinates Out of Range
This only tests a handful of invalid coordinates to verify behavior. Detailed coordinate validation occurs in isValidCoordinate
Input: [181, 91],  [181, -91],  [-181, 91, 0],  [-181, -91, 200], [0, 0, 0, 0]
const testPoint = {
    type: "Point",
    coordinates: <input>
}

Type Value Incorrect
Input:

Each of the values from "Geometry Input Not an Object", plus
'MultiPoint', 'LineString', 'MultiLineString', 'Polygon', 'MultiPolygon', and 'GeometryCollection', or
'POINT', 'point'

const testPoint = {
    type: <input>,
    coordinates: [0, 0]
}

Contains Prohibited Properties
Geometry
const testPoint = {
    type: "Point",
    coordinates: [0, 0],
    geometry: {
        type: "Point",
        coordinates: [102.0, 0.5]
    }
}

Properties
const testPoint = {
    type: "Point",
    coordinates: [0, 0],
    properties: {
        prop1: true
    }
}

Features
const testPoint = {
    type: "Point",
    coordinates: [0, 0],
    features: [{
        type: "Feature",
        geometry: {
            type: "Point",
            coordinates: [102.0, 0.5]
            },
        properties: {
           prop0: "value0"
        }
    }]
}

Missing Required Properties

No Type

const testPoint = {
    coordinates: [0, 0]
}

No Coordinates

const testPoint = {
    type: "Point"
}

:tada: This issue has been resolved in version 1.0.0-beta.6 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

Reopening to add coverage to validate optional bounding boxes.

:tada: This issue has been resolved in version 1.0.0-beta.14 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Install using HACS, no configuration available

Hi
I managed to add vallox2mqtt latest release to Home Assistant 2021.12.9 but it doesn't add entities and I'm not able to change configuration settings. I guess I'm doing something wrong, but I don't know what. I must add, ESP32 is already running but not connected to my ventilation unit. I first wanted to check communication channels because I switched to ESP32 and want to use Serial2 instead of the default serial port.
Any help would be very much appreciated.

Have you done it like this:
– HACS -> add custom repository -> https://github.com/kotope/valloxesp.git
– Install vallox2mqtt
– go to configuration -> devices -> integrations -> + add integration
– search for vallox2mqtt and click ok
–> configuration flow should start at this point

I thought I had done this but couldn't find the vallox2mqtt integration. Did it again yesterday, and it's up and running now.
Thanks again!


Can I make a wallet on my own device

How to make a wallet

hey,  my old sport, if you want to use source code to build the wallet. please refer the order:

download source code and import you Android Studio.
build the project.

How can i do it?pelease

please read project build.md


RenderingServer.create_local_rendering_device() memory leaks

Godot version
v4.0.beta10.official
System information
Debian GNU/Linux 11 (bullseye), Intel Core i3-8130U CPU, Mesa Intel UHD Graphics 620 (KBL GT2)
Issue description
Memory leaks occur while using RenderingServer.create_local_rendering_device(). Moreover, the engine crashes after creating many local rendering devices (even if this is done in a scoped environment, see below). If rendering_device.free() is called, the following warning appears: drivers/vulkan/rendering_device_vulkan.cpp:8957 - 1 RID of type "<...>" was leaked., where <...> is any object, created with local rendering device (Shader, Texture, ...).
Steps to reproduce
The following code reproduces the bug:
extends Node

func _ready() -> void:
    for step in range(199):  # 199 times are enogh to crash the engine on my system.
        create_lrd()
        print(step)

func create_lrd() -> void:
    var rd := RenderingServer.create_local_rendering_device()

    # If something is done with rd here, it remains in memory even upon
    # return from this function.

    #rd.free() # No memory leaks occur, but Vulkan warnings are printed.
    # this line also fixes crashes.

Minimal reproduction project
RDMemoryLeak.zip

Creating that many local rendering devices will use up all of your video memory (per the vulkan spec), resulting in a crash. The limit I can go on my machine is ~100. You have to call RenderingDevice.free_rid(RID) for any resources created with the rendering device manually, else they will be leaked when the RenderingDevice is freed.
I've written a small function in one of my projects to get the total memory usage for all created rendering devices to prevent too many RDs from causing a crash. Maybe having this functionality built in and documented would solve some headaches for people trying to use RenderingDevice before it gets documented.

Calling RenderingServer.free_rid(rd) will help maybe?

Calling RenderingServer.free_rid(rd) to free the local device will help maybe?

Calling RenderingServer.free_rid(rd) to free the local device will help maybe?

Yes, it helps, but it is still confusing that it is not done automatically. At least this should be reflected in the docs.


[Bug]:

What happened?
I am attempting to get download URL's for MacOS and not windows and the different arches (as in ARM and Intel). Is it possible? If so what's the most efficient way of doing so? I do see the MacOS entries in Evergreen.json on PSGallery forexample.
I thought maybe these commandlets would help, but I am not able to invoke any of the Get-* commandlets:
PS C:\Users\jztfl> Get-AdobeBrackets
Get-AdobeBrackets : The term 'Get-AdobeBrackets' is not recognized as the name of a cmdlet, function, script file, or o
perable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try aga
in.
At line:1 char:1

Get-AdobeBrackets

  + CategoryInfo          : ObjectNotFound: (Get-AdobeBrackets:String) [], CommandNotFoundException
  + FullyQualifiedErrorId : CommandNotFoundException

PS C:\Users\jztfl> Get-CitrixWorkspaceApp
Get-CitrixWorkspaceApp : The term 'Get-CitrixWorkspaceApp' is not recognized as the name of a cmdlet, function, script
file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct a
nd try again.
At line:1 char:1

Get-CitrixWorkspaceApp

  + CategoryInfo          : ObjectNotFound: (Get-CitrixWorkspaceApp:String) [], CommandNotFoundException
  + FullyQualifiedErrorId : CommandNotFoundException

PS C:\Users\jztfl> Get-AdobeAcrobatReaderDC
Get-AdobeAcrobatReaderDC : The term 'Get-AdobeAcrobatReaderDC' is not recognized as the name of a cmdlet, function, scr
ipt file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is corre
ct and try again.
At line:1 char:1

Get-AdobeAcrobatReaderDC

  + CategoryInfo          : ObjectNotFound: (Get-AdobeAcrobatReaderDC:String) [], CommandNotFoundException
  + FullyQualifiedErrorId : CommandNotFoundException

  Any other commandlets work fine. Is this something that is no longer possible?

Version
2309.840
What PowerShell edition/s are you running Evergreen on?
Windows PowerShell
Which operating system/s are you running Evergreen on?
Windows 10+
Have you reviewed the documentation?

[X] Troubleshooting at: https://stealthpuppy.com/evergreen/troubleshoot/
[X] Known issues at: https://stealthpuppy.com/evergreen/issues/

Verbose output
PS C:\Users\jztfl> Get-EvergreenApp AdobeAcrobatReaderDC

Version      : 23.006.20360
Language     : Spanish
Architecture : x86
Name         : Reader 2023.006.20360 Spanish for Windows
URI          : https://ardownload2.adobe.com/pub/adobe/reader/win/AcrobatDC/2300620360/AcroRdrDC2300620360_es_ES.exe

Version      : 23.006.20360
Language     : French
Architecture : x86
Name         : Reader 2023.006.20360 French for Windows
URI          : https://ardownload2.adobe.com/pub/adobe/reader/win/AcrobatDC/2300620360/AcroRdrDC2300620360_fr_FR.exe

Any ideas here on how to leverage evergreen for macos applications?

Evergreen hasn't been written to support macOS; however, the approaches used in many of the application functions can be modified to return the macOS installers, but this would require changing quite a bit of the code. You can fork the project and make changes


Elixir nixpack shouldn't run migrations in build step

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the bug
The default elixir buildpack tries to run migrations during the docker build. I might be missing some common use case, but I can't imagine wanting to run migrations during the image building. I checked a few other languages, and they don't seem to have similar behavior.
To reproduce
Create a new phoenix app (assuming elixir and phoenix are installed):
mix phx.new hello
cd hello
nixpacks build ./

# output
 => ERROR [12/14] RUN  mix ecto.migrate                                                                                0.5s
------
 > [12/14] RUN  mix ecto.migrate:
0.211 warning: the VM is running with native name encoding of latin1 which may cause Elixir to malfunction as it expects utf8. Please ensure your locale is set to UTF-8 (which can be verified by running "locale" in your shell)
0.473 ** (RuntimeError) environment variable DATABASE_URL is missing.
0.473 For example: ecto://USER:PASS@HOST/DATABASE
0.473
0.473     /app/config/runtime.exs:26: (file)
0.473     (stdlib <IP_ADDRESS>) erl_eval.erl:748: :erl_eval.do_apply/7
0.473     (stdlib <IP_ADDRESS>) erl_eval.erl:492: :erl_eval.expr/6
0.473     (stdlib <IP_ADDRESS>) erl_eval.erl:136: :erl_eval.exprs/6
0.473     (elixir 1.14.5) lib/code.ex:425: Code.validated_eval_string/3
------
Dockerfile:27
--------------------
  25 |     RUN  mix compile
  26 |     RUN  mix assets.deploy
  27 | >>> RUN  mix ecto.migrate
  28 |     RUN  mix run priv/repo/seeds.exs
  29 |
--------------------
ERROR: failed to solve: process "/bin/bash -ol pipefail -c mix ecto.migrate" did not complete successfully: exit code: 1
Error: Docker build failed

The following nixpacks.toml fixes this:
[phases.build]
cmds = ["mix compile", "mix assets.deploy"]

Expected behavior
Don't run migrations and seeds during the build step. Maybe not at all. Python ran migrations in the start step which might make sense, but I'm not sure what the best behavior is.
Environment
Mac OS Sonoma 14.4
Nixpacks v1.21.2

I run into the same issue. Migrations shouldn't be run on docker build.


Update the Gemfile.lock to fix security warnings

Handling the dependabot alert around  gem "activesupport", ">= <IP_ADDRESS>"

Need to upgrade github-pages gem to v228


no such table: Z_METADATA

Am trying to work with a Photos library on a Mac Mini M2 Pro system that was updated on Ventura 13.6.3 version of Photos.app - the photos library is physically located on a Mac Pro 2013 system running High Sierra 13.6.1 on a HFS+ case sensitive volume that was originally created on a High Sierra version of Photos.app (version 3) and then remotely mounted on the Mac Mini Ventura system and then when Photos on Ventura tried to open it, it wanted to update it so that it became a version 8 photos library. The "update" process took 2-3 hours (the Photos library is about 900GB) and there were no errors during the update process. But when Photos.app tried to then open this "updated" photos library, it gets a -1 error and won't do anything with it now. Since the photos library has now been updated by Ventura, I can no longer use it on the High Sierra system, so am now trying to deal with a rather large photos library that can't be used either on High Sierra or on Ventura.
Apparently there is a problem with new versions of Photos on macOS that don't like photo libraries located on case-sensitive volumes, even though I've been using the High Sierra Photos.app with a case sensitive volume for years and years. I've contacted Apple and tried to confirm this fact but have not been seen where this is documented on any official Apple web page - does anyone know where this is documented, or is this really just a rumor?
So I came across osxphotos and am trying it out to see what I can find out about the updated photos library, and when I try, get the following when osxphotos tries to give me info about this photos library:
### _% ./osxphotos-arm info --library ./Bob's\ Photos.photoslibrary
Loading library: ./Bob's Photos.photoslibrary
WARNING: Only tested on database versions [6000, 5001, 4025, 4016, 3301, 2622] You have database version=5002 which has not been tested
╭─────────────────────────────── Traceback (most recent call last) ────────────────────────────────╮
│ in :18                                                                                │
│                                                                                │
│ in call:1157                                                                                │
│                                                                                │
│ in main:1078                                                                                │
│                                                                                │
│ in invoke:1688                                                                                │
│                                                                                │
│ in invoke:1434                                                                                │
│                                                                                │
│ in invoke:783                                                                                │
│                                                                                │
│ in new_func:45                                                                                │
│                                                                                │
│ in new_func:33                                                                                │
│                                                                                │
│ in info:36                                                                                │
│                                                                                │
│ in init:394                                                                                │
│                                                                                │
│ in get_photos_version_from_model:107                                                             │
│                                                                                │
│ in get_model_version:88                                                                          │
╰──────────────────────────────────────────────────────────────────────────────────────────────────╯
OperationalError: no such table: Z_METADATA
[2977] Failed to execute script 'cli' due to unhandled exception!
%_
Anyone ever seen this Photos.app -1 error or know what it's really having a problem with?? I do have a TimeMachine backup of the original Photos library on the High Sierra system, so that's my fallback plan, but would really like to be able to use Photos.app on the Mac Mini system, as it's a lot faster than the High Sierra computer. Appreciate any suggestions, ideas, etc.
Here is the osxphotos version info (i tried both the arm and the x86 versions I downloaded this morning - both give the same error about missing Z_METADATA table):
% ./osxphotos-x86 --version
osxphotos, version 0.67.0
Python 3.12.0 (v3.12.0:0fb18b02c8, Oct  2 2023, 09:45:56) [Clang 13.0.0 (clang-13<IP_ADDRESS>)]
macOS 13.6.3, x86_64
% ./osxphotos-arm --version
osxphotos, version 0.67.0
Python 3.11.6 (v3.11.6:8b6ee5ba3b, Oct  2 2023, 11:18:21) [Clang 13.0.0 (clang-13<IP_ADDRESS>)]
macOS 13.6.3, arm64
%
Odd that the two different versions of the osxphotos program (I named them osxphotos-arm and osxphotos-x86) give different python version info - is that normal when using the ARM and X86 versions of the osxphotos program??
I was expecting to see a lot of info about the underlying photos library that had been updated by Photos.app on Ventura. By the way, got the same -1 error when this Mac Mini was running macOS version 13.6.1, and Apple asked me to update to the lastest 13.6.3, which I did and it made no difference.
Anyone have any idea why the missing "Z_METADATA" table happened or how to fix it or what the -1 really is all about?
Thanks very much...
-bob

It sounds like migration from the High Sierra to Ventura failed. Z_METADATA is a table that should be in the database for any Photos library from Catalina or newer. The osxphotos code found database version 5002 which indicates a Catalina+ database. It then needs to read Z_METADATA to find out which exact version of Photos created the library so it can use the correct schema. Yours is in a n "in between" state -- the migration updated the version to 5002 (High Sierra would have been most likely 3301 originally) -- but it did not create the Z_METADATA table. This is also why Photos cannot open the database.
It is probably possible to patch the osxphotos code to get around this (but who knows what other inconsistencies we'd find if the database is in a partially migrated state. You said you had a Time Machine backup of the library -- is it current? If so, I recommend copying that library to an external drive formatted with APFS (and preferably an SSD drive) then attempting to do the conversion again with the 13.6.3  machine. That is far more likely to produce a good result than attempting to work around a corrupt database.

Odd that the two different versions of the osxphotos program (I named them osxphotos-arm and osxphotos-x86) give different python version info - is that normal when using the ARM and X86 versions of the osxphotos program??

Yes. I build the images on 2 different machines that have different pythons installed. The preferred install approach is to use pipx per the instructions but the binaries are provided for those who don't want to do so.

Apparently there is a problem with new versions of Photos on macOS that don't like photo libraries located on case-sensitive volumes,...does anyone know where this is documented,

I don't know if this is documented but the Mac in general does not like case-sensitive file systems and I would avoid doing this in the future.

The reason for the case-sensitive file system is that the photos library was located on the same disk as a bunch of other stuff I use on many different systems. Like I mentioned, I've been using this case-sensitive setup on High Sierra version of Photos.app for years with absolutely no problems - and before that Sierra and Mountain Lion and Lion and even further back I think, as I've been taking digital photographs and keeping them on a Mac system since the early 2000's. This is not a bootable volume, just a place for a lot of misc stuff, from downloads collected over the years to various UNIX projects, to various media files (movies, music, etc) and many other things.
I've been a UNIX user since the 1970's, so case-sensitive filesystems are part of my "DNA" and I simply can't imagine life without them, even on my Mac systems. I understand some software will refuse to even install on case-sensitive volumes (like most/all of Adobe's programs) but for that case-insensitive stuff I use the boot disk usually or another case-insensitive disk for just those sorts of programs that need to live on case-insensitive volumes.
In my opinion, I believe that the reason Adobe claims that their software doesn't work on case-sensitive volumes is because of sloppy programming practices on their part that would be a significant effort for them to repair and they "solve" the problem by simply forbidding people to install their software on case-sensitive volumes - many years ago I've seen crash reports from various Adobe software apps (e.g. Photoshop) that I've experimented with on case-sensitive volumes, that very clearly demonstrate programs that try to do things like compare a filename on the disk named "ABC.jpg" to a variable that contains the value "abc.jpg" and on a case-insensitve file system that sort of thing can work, but on a case-sensitive file system will, of course, fail. So, rather than fix the real problem by cleaning up their code, they have perpetuated the "myth' that case-sensitive volumes are the problem, but I'm afraid I couldn't disagree more. UNIX was born with case-sensitive files being no big deal and I couldn't agree more. Perhaps a few Adobe programmers now work at Apple on Photos and they've adopted this philosophy rather than be more careful when writing software?
Given your comments, I'm a bit puzzled why the original Ventura Photos.app invocation that updated the High Sierra photos library didn't do a better job at complaining that the update process failed in a rather significant way. I will try and talk to Apple support now being aware of this important information and see what they have to suggest as to what might have happened. If I find out, will update these notes to let folks know what they have to say/suggest.
Thanks very much for your insights, as this gives me a good reason to restore the original High Sierra photos library folder from Time Machine and get it working again rather than pursue what seems to have been a faulty conversion, and then try Ventura Photos.app on a separate photo library and leave my High Sierra photo library alone and untouched by newer macOS versions and avoid this whole mess in the future - hopefully ;-)
Couldn't have asked for a better Chrismas present that this great "osxphotos" program - thanks so much for all the work, you and everyone else has done for this project, and best wishes for the holidays and the coming year. Open Source software is, without question, one of the best ideas to have been happened to everyone who uses computers. Thanks to everyone who makes this a better world because of their efforts on this project and all the others!!!
-bob

UNIX was born with case-sensitive files being no big deal and I couldn't agree more.

But macOS is not unix. It is based off BSD but has significantly diverged and Apple has made a bunch of macOS specific design choices (like defaulting to a case-insensitive file system). I really think you'll be much better off moving the library to an APFS disk and trying to convert again -- who knows what state the corrupt library is in and even if you could get it working, it would be hard to know if there was anything missing.  (Though osxphotos could be used to write a script to compare the two).
For what it's worth, when exporting from Photos, osxphotos will assume that files are case-insensitive as this is the default for most Mac users and targeting the expected use case is a better design choice that targeting an edge case. So if you had two photos that were getting exported to the same directory: IMG_123.jpg and img_1234.JPG, osxphotos will first normalize unicode then convert to lower case and compare. In this case, you'd end up with IMG_1234.jpg and img_1234 (1).JPG as the exported files even if exporting to a case-sensitive file system. Working around the case-sensitive edge case just complicates the code for very little benefit for most users. The original case will be preserved in the created file names but as they both compare to the same name when converted to lower case, one name will be incremented to deconflict with the other.

Couldn't have asked for a better Chrismas present than this great "osxphotos" program

Thanks! I hope it's useful to you!
Cheers and Merry Christmas!
Rhet

Well, I got osxphotos installed on High Sierra and Ventura so that I can dig into the innards of my Photos libraries and what a cool tool!! Thanks again for all your effort in creating and maintaining osxphotos. Definately on my list of favorites!!
-bob

@DeepYogurt  thanks for the feedback! Glad you find it useful!


feat: Support WAV files as well

fixes godot-escoria/escoria-issues#65

Looks great to me. Thanks a lot!


exorcism, chytridiales (logical-conflict)

This pull request was generated by the 'mq' tool

/trunk merge


chore: pull in changes from fork

With https://github.com/Stedi/jsonata/pull/23/commits/c266f17e1c56907090a056d8bde4a62d5aef8f6d I fixed two files that are/are not relevant to us. I'll patch them again when proposing a change to the base repo.


Fix convertPoundToKilograms Methods

There is currently a method called <convertPoundToKilograms> that lives in /lib/<convertPoundToKilograms>.js.
It is incomplete and needs to be fixed!
The method converts pounds to Kilograms where 1 pound is equal to 0.45 kilograms.
Acceptance Criteria:

Running yarn test <convertPoundToKilograms> results in tests passing.
You have written a skeleton method for someone else to work on.
You have written tests surrounding your skeleton method.
Running yarn lint does not print any errors to the console!
Optional: write one or two more tests surrounding the method you are solving to account for potential edge cases.

Please include the skeleton of a new method + an accompanying test for someone else to work on at the time of creating a pull request! A pull request will most likely be denied if it does not contain a skeleton method for someone else to work on! For more information, please read the Contributing Guide.
Thank you so much for your contribution!

ill work on this issue

There is no such method file in the directory, so do i create one?

@darthgera123 I've made a pull request. It's yet to be merged, then you'll see the file.


Allow players to return word list only

Quick fix, should be refactored later in https://github.com/production-ml/the-hat-game/issues/25

Works, e.g. last lines of running python run_game.py:
=== Team scores, summary ===
                explaining  guessing  total  response_200  response_time
HerokuOrg team          10         0   10.0           1.0       0.722293
Local Player             0        10   10.0           0.0            NaN
Game started at 2021-11-13 18:02:55.434989. Game lasted for 0 days 00:00:15.538950


Security Issue: Password in logfile

While trouble shooting another problem I've noticed that the log information of the roundcube addon is dumping the password in the clear.

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/21021833-security-issue-password-in-logfile?utm_campaign=plugin&utm_content=tracker%2F308690&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F308690&utm_medium=issues&utm_source=github).

I remember that once or twice such a debugging kludge accidentally slipped into the git archive through my hands. Inspecting my own logs I do not have the expression that  this is still the case; can you perhaps quote one of those log-lines (but of course with the password wiped out) such that it is easier for me/us to identify the bogus line in our own log-files?
Thanks,
Claus

Here you go:
Exception: {"Message":"Unable to determine network-status due to technical problems.","Code":0,"Trace":"#0 \/srv\/www\/owncloud\/htdocs\/apps\/roundcube\/lib\/RoundCubeLogin.class.php(279): OC_RoundCube_Login->sendRequest('\/roundcube\/', Array)\n#1 \/srv\/www\/owncloud\/htdocs\/apps\/roundcube\/lib\/RoundCubeApp.class.php(356): OC_RoundCube_Login->login('<username>', '<password>')\n#2 \/srv\/www\/owncloud\/htdocs\/apps\/roundcube\/lib\/RoundCubeApp.class.php(529): OC_RoundCube_App::login('owncloud.quasiw...', '', '\/roundcube\/', '<username>', '<password>')\n#3 \/srv\/www\/owncloud\/htdocs\/apps\/roundcube\/ajax\/userSettings.php(10): OC_RoundCube_App::saveUserSettings('roundcube', '<username>', '<username>', '<password>')\n#4 \/srv\/www\/owncloud\/htdocs\/lib\/private\/route\/route.php(135) : runtime-created function(1): require_once('\/srv\/www\/ownclo...')\n#5 [internal function]: __lambda_func(Array)\n#6 \/srv\/www\/owncloud\/htdocs\/lib\/private\/route\/router.php(250): call_user_func('\\x00lambda_1427', Array)\n#7 \/srv\/www\/owncloud\/htdocs\/lib\/base.php(782): OC\\Route\\Router->match('\/apps\/roundcube...')\n#8 \/srv\/www\/owncloud\/htdocs\/index.php(36): OC::handleRequest()\n#9 {main}","File":"\/srv\/www\/owncloud\/htdocs\/apps\/roundcube\/lib\/RoundCubeLogin.class.php","Line":434}

ok du u mean that the users are named "username" and the passwword in clear text are "password" right?
this i think only happened if the debbugin level are at the lowes .. let me try and i'll post feedback here

you can try if the error is now gone with latest master

is it still an issue with the latest master?

i cannot see in my log .. (and i still have the table rouncube empty)
i ask, its necesary have enabled the filesencription app of the owncloud?

I really can't say if it is still an issue because I can't produce the log entry anymore.
I don't have any file encryption enabled in owncloud.


Better Nav Implementation

Basic navigation logic is in place, but a better animation would complete the experience.  A better experience would include:

Header element shrinks fully with elements.
Element moves into expected position below the navigation toggle.

While I think this issue is in reach, I also am tired of uninstalling Ruby's Sass to access Sass, along with several other issues that makes a vanilla Github Jekyll not an ideal experience.  Expect this issue to be addressed in the next version of A Pretty Heckin' Website, which I intend to build with Hugo.

We're going to focus on this issue more in future iteration, but currently we have a faux accordion effect that removes much of the jumpiness experienced when creating this issue.
A further elaboration on this would involve wrapping each button in a div and shrinking those divs as the buttons fade.  This will be implemented in the upcoming 'A Pretty Hugoin' Website'.


Flow Activation - Flow is missing Connection exception

When the pipeline tries to activate the Flow after reassigning the ownership, I get the exception below

The connection references are owned by the service account. I created the connections in the destination environment and use the ConnectionReferences pipeline variable to hook this up with the connection reference. I also made sure that the unique name of the connection reference and the actual connection id are correct in the JSON being passed.

When the Pipeline tries to reassign the Flow to a real user and then activate it, the Pipeline fails with the error in the 1st screenshot.
When I tried to run the reassign/activate script update-connection-references.yml locally, I get the same error

If I try to activate the Flow on the portal I get the same error as well.

I read  again and I can confirm that:

Connection Reference records have been created in destination environment
Connection Reference record is owned by service account configured in the pipeline
Connections exists in the destination environment
Connection is owned by my SysAdmin account in the destination environment
Connection and Connection Reference are hooked up (manually) in the destination environment

I am not sure what I am missing.

Messaged @scottdurow and it looks like the real issue is that the Flow is using Connection rather than Connection Reference, even though it is inside the Solution. This is how the Flow looks like

I created another Flow inside the Solution and it does seem to be using Connection Reference.

So, it looks like someone created Flow outside of Solution and later added it inside. I now have to figure out how to convert Connection into Connection references for all the Flows in the solution, so that the pipeline succeeds.


Atom Failed to Find file in entire project file of Laravel

i try to find file name DB.php located on \my laravel folder\vendor\laravel\framework\src\Illuminate\Support\Facades\DB.php but atom fail to search it using CTRL + P Any idea why?

Thanks for reaching out!  I'd suggest checking if your project has a .gitignore that ignores vendor/ maybe?  Or double check your Settings > Core > Ignored Names setting as well.
If that doesn't help, feel free to post on the message board and mention me (@rsese) and we can take a look.

Because we treat our issues list as the Atom team's backlog, we close issues that are questions since they don't represent a task needing to be completed. For most questions about Atom there are a lot of options, check out:

The Atom Flight Manual
The Atom FAQ on Discuss
Discuss, the official Atom and Electron message board
Join the Atom Slack team

On Discuss and in the Atom Slack team, there are a bunch of helpful community members that should be willing to point you in the right direction.

Hi @rsese thank you for replying. yes it's contain .gitignore but in my logic that file isn't related to atom or this fuzy finder. it just file for git (app) to ignore the folder to be upload to remote repository. i have checked core setting as well and there's still in default and no vendore folder included. could you please help why i can't find file DB.php inside folder vendor among many sub2 folder inside it?

yes it's contain .gitignore but in my logic that file isn't related to atom or this fuzy finder.

Thanks for confirming - Atom will ignore files in your .gitignore by default for functionality like fuzzy finder but you can disable this in your settings at Settings > Core > Exclude VCS Ignored Paths.  If that doesn't help, please share your .gitignore.

its work thanks @rsese you the best


[WIP] Multithreaded version of simdjson for parsing regular but large JSON documents

This is a work-in-progress version of simdjson which can parse large documents in a multithreaded fashion. There is an interleave of stage 1 and stage 2. The expectation is that we should be able to boost the parsing speed of large files by ~50% while using 2 cores.
This would solve https://github.com/lemire/simdjson/issues/171
I brought it here from a fork @piotte13 did. It is not clean and not approved by Jérémie, but I wanted to start discussion around it, early.
The stage 2 has been reengineered to be more flexible. Basically, you can run stage 2 over pieces of a JSON document, not just entire JSON documents. This implies that we must be able to persist the current state, and resume where we were (e.g., in the middle of an object).
Doing so has other engineering benefits. For example, it should allow us to avoid having to pad the inputs (solving https://github.com/lemire/simdjson/issues/174). We could also allow the user to just parse the documents in small pieces.
Besides the fact that this PR is not clean, there are still unresolved performance issues. The expectation is that the more flexible stage 2 should run at the same speed. We worked hard to keep the fancy computed gotos. Sadly, the single-threaded can be far worse (-25%). For large files, this is fine because the second thread more than compensate, but for small files, we can't use the new approach without a substantial penalty.
The new stage 2 should be identical in computation cost, except for one additional comparison and conditional jump per structural element. We can expect that this comparison and condition jump should be highly predictable and, effectively free. So something else is hurting us. Unfortunately, the new code is quite different from the old code in structure, so a straight-forward comparison is not trivial.
I expect that @piotte13 might come around, clean and report. When he does, this PR will become obsolete.
Cheers!

Daniel

I am going to kill this PR, but keep the branch.


Injector can define kubernetes clusterDomain

Description
Injector use default cluster domain "svc.cluster.local" to access some service but kubelet can change the "cluster.local" value by clusterDomain.
Make Injector can get kubernetes clusterDomain configuration by environment
Issue reference
#3163
Checklist
Please make sure you've  completed the relevant tasks for this PR, out of the following list:

[x] Code compiles correctly
[x] Created/updated tests
[x] Unit tests passing
[ ] End-to-end tests passing
[ ] Extended the documentation / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]
[ ] Specification has been updated / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]
[ ] Provided sample for the feature / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]

@marviniter the e2e tests are failing

@marviniter the e2e tests are failing
i found the error is  "timed out waiting for the condition",the deployment pod not running

@marviniter the e2e tests are failing
i found the error is  "timed out waiting for the condition",the deployment pod not running

HI @yaron2  I run e2e tests on local dev enviromnet and kind cluster all successed, i add some log output pod resource info  find the search domain in Injector Pod is "ac31hddj4phu5ocom5smqd4hkf.cx.internal.cloudapp.net" , e2e tests run on Azure cluster?
I add the KUBE_CLUSTER_DOMAIN environment variables in charts just for e2e tesets

/ok-to-test

Do we want to update sentry here to use certificates that use the local domain or are we happy to continue having certificates use cluster.local (ref)? AFAIK cluster.local will still continue to work as the Dapr client also sets the expected TLS server name to appid.namespace.cluster.local when making a request (ref) so we could leave it but it wouldn't reflect the actual hostname of the service. I opened an issue a few weeks back about this #3131.

Do we want to update sentry here to use certificates that use the local domain or are we happy to continue having certificates use cluster.local (ref)? AFAIK cluster.local will still continue to work as the Dapr client also sets the expected TLS server name to appid.namespace.cluster.local when making a request (ref) so we could leave it but it wouldn't reflect the actual hostname of the service. I opened an issue a few weeks back about this #3131.

/cc @yaron2  Thoughts on this?

Do we want to update sentry here to use certificates that use the local domain or are we happy to continue having certificates use cluster.local (ref)? AFAIK cluster.local will still continue to work as the Dapr client also sets the expected TLS server name to appid.namespace.cluster.local when making a request (ref) so we could leave it but it wouldn't reflect the actual hostname of the service. I opened an issue a few weeks back about this #3131.

/cc @yaron2 Thoughts on this?

Yes, we'd like to change that. This can be done in a separate PR.
@artursouza are we good to merge this?

@marviniter we recently pushed some new linter changes, and the build is now failing. can you fix those? we can merge then.

@marviniter we recently pushed some new linter changes, and the build is now failing. can you fix those? we can merge then.

Hi @yaron2 , i have fixed it!

/ok-to-test

@marviniter thanks a lot for this contribution. can you please follow up with a docs PR that explains how to setup this configuration?

@marviniter thanks a lot for this contribution. can you please follow up with a docs PR that explains how to setup this configuration?

OK，i will finish relate doc pr later！


Remove typings for @storybook/react

Issue: #1166

[x] Hold off merging until https://www.npmjs.com/package/@types/storybook__react is available.
[x] Update docs

Thanks @joscha !

Docs updated in 5013dda - let's see how we go with this change and then we can update all the other packages.

Thanks so much @joscha . Going to test it out and then merge. Super excited about this!

@joscha worked like a charm. fabulous! 🌈 🦄 🌟

@joscha worked like a charm. fabulous! 🌈 🦄 🌟

awesome, I'll be doing the other packages then as follow-ups.

@joscha @ndelangen @tmeasday I'd like to revert this change for now. It's a breaking change, so technically it would bump this release to 4.0.0 under semver, and I think we want to batch up breaking changes so that we aren't doing major releases all the time.

does this make sense to you guys?
(OR do you want to ditch semver and just release this is as 3.0.2, which is what it feels like?)
@joscha if we backed out this change, is it still possible for users to force typescript to use your DefinitelyTyped typings instead of these?

Thanks and sorry for the confusion!

does this make sense to you guys?

makes sense, yes.

(OR do you want to ditch semver and just release this is as 3.0.2, which is what it feels like?)

hmm, not sure how annoyed I would be if I had to run one little yarn add @types/node @types/storybook__react after upgrading, I personally would probably be okay with it, but it is not a no-brainer update as a patch should be, so maybe 4.0 sounds right?

@joscha if we backed out this change, is it still possible for users to force typescript to use your DefinitelyTyped typings instead of these?

I don't think so, the typings definition in package.json takes precedence iirc, so it would shadow anything from @types/.... We'd need to keep the typings in definitelytyped updated alongside the ones in this repo for the time being and then remove the typings from this repo with the 4.0.0 release. Quite tedious and potentially confusing, but an easier upgrade path for users I suppose.
I haven't tried, but what if @types/storybook__react is made a dependency of @storybook/react for now and we reference the<EMAIL_ADDRESS>from the typings key in package.json - does that work? Because then that would be a seamless upgrade until in 4.0.0 we can remove the absolute dependency as a breaking change. The only penalty to pay in the meantime is the weight of the additional package for users that don't use TS, but they currently pay a similar penalty with the additional type definition anyway.

Sorry for the confusion @joscha . See my updated comment above. 😵


Support FREME API version 0.6

Started to work on this since the endpoint changed and the filter agent was not working any more for version 0.5. Since I don't know what I'm doing :) it would be nice if you could review this @dsander. If it seems ok to you, you could continue working in this PR until we have all agents updated to version 0.6.

Nice, I will have a look at it later today. Do we have a changelog for the API changes or do we need to compare the new docs with the configuration we have in the agents?

@davidwabnitz Are you ok with me squashing the commits into one? What would make the cherry-picking in the feature branch and the agent gem easier.

@dsander sure - especially with the fixes now being in.


docs: Make config version 2.

Remove unsupported config values.
Fixes #14.
Signed-off-by: Tim 'mithro' Ansell<EMAIL_ADDRESS>

@mohanad0mohamed - This pull request fixes the config file that you added in https://github.com/google/open-source-pdks/pull/20 to actually work correctly. See the documentation at https://docs.readthedocs.io/en/stable/config-file/v2.html

@mohanad0mohamed The doc build doesn't seem to build the documentation correctly?

@atorkmabrains The build won't be successful until all warnings are fixed.
I have made pull requests for this issue #18 to fix these warnings.


bootstrap may leave unexpected region data in storage.

When bootstrap cluster, we 1) build the first region, save it, 2) send bootstrap request to PD. If server panics after step 1, invalid region data will be left. Refer https://github.com/pingcap/tikv/blob/master/src/server/node.rs#L124

Maybe we can:

prepare the first region in RocksDB
Bootstrap the first region in PD
commit the first region in RocksDB


cannot query on an emmbedded-list (long) with the operator 'between x and y'

OrientDB Version: 2.2.17
Java Version: java 8 update 131
OS: Windows 10
I cannot query on an emmbedded-list (long) with the operator 'between x and y' and not with '>=x and <=y' (>= alone - works, <= alone - works) - the index is notUnique.
Expected behavior
if a record contains the value [2,3,4] in an 'emmbedded-list (long)' field called 'prop', I should get this record when perform a query serach with the condition like: 'prop between 1 and 4', 'prop between 2 and 3'
Actual behavior
an exception is thrown in orient server:

Error on using index EN70.EP70_4 in query 'SELECT * FROM EN70 WHERE (EP70_4 BETWEEN 1 AND 3 )'. Probably you need to rebuild indexes. Now executing query using cluster scan java.lang.ClassCastException: java.util.ArrayList cannot be cast to java.lang.Long at com.orientechnologies.common.serialization.types.OLongSerializer.preprocess(OLongSerializer.java:36) at...

Steps to reproduce

I have a vertex called: EN70 with a property: EP70_4 from type 'embedded list = LONG'.
I added a record to this vertex with the value of [2,3,4] in this 'EP70_4' property.
The index on this property: Not_Unique (sbtree). [must support range queries]
SELECT * FROM EN70 WHERE (EP70_4 >= 1) is working and returns my record.
SELECT * FROM EN70 WHERE (EP70_4 <= 3) is working and returns my record.
The operator "Between" is not woking and throw exception: SELECT * FROM EN70 WHERE (EP70_4 BETWEEN 1 AND 3 )
I tried to simulate a "between" operator: SELECT * FROM EN70 WHERE ((EP70_4 >= 1) AND (EP70_4 <= 3)) IS NOT WORKING but it is not working.

both sections 6 and 7 throws an exception:
Error on using index EN70.EP70_4 in query 'SELECT * FROM EN70 WHERE (EP70_4 BETWEEN 1 AND 3 )'. Probably you need to rebuild indexes. Now executing query using cluster scan java.lang.ClassCastException: java.util.ArrayList cannot be cast to java.lang.Long at com.orientechnologies.common.serialization.types.OLongSerializer.preprocess(OLongSerializer.java:36) at...
See also:
http://stackoverflow.com/questions/43602699/using-beteen-operator-on-a-long-embedded-list-property-declared-in-orientdb-2

Hi @T55134
I'm working to a fix for this, it will be in the branch in a few hours.
Anyway, IMHO this behavior is intrinsically incorrect. The comparison of a list with a long should always evaluate to false, we should define a specific syntax to query elements inside a list.
Thanks
Luigi

Luigi,
May I ask why do you thing it is wrong to perform a comparison on a list??
Let's say I have a vertex for a person with an embedded list for his addresses - if I search for address 'xxx' it looks like this: "WHERE address = 'xxx' " I get this person and it is ok that only one item within the list is a match. (It works fine now, no need change it)
Another example is regarding ranges ('between') - a field is emmbedded list of DATE - Let's say that person vertex has a field like this that contains the dates that this person was using his creditcard. so when I search for "...WHERE ccardUses between '2017-01-01 00:00:00' and '2017-12-31 23:59:59'  " I expect to get this person as a result even ONE of the dates match the condition.
In short - =, >=, <= is working just fine on embedded list but when you combine more than one condition you get an exception and no results:

between,
'>= and <=',
in
etc.

I think that the core of this issue is exactly like this one:
http://stackoverflow.com/questions/41207737/a-valid-query-syntax-for-orientdb-returns-no-results-without-errors
And there is maybe a different settings I need for the index - I will be happy to know what...
Thanks
Tami

Hi @T55134
The use case makes a lot of sense, what puzzles me more is the SQL syntax. I'll try to explain what I mean:
SELECT FROM V where foo = 10

if foo is a number, then the query is straight forward
If foo is a list, like [10, 20, 30] then it becomes more complex: maybe you want to obtain the records where at least one element matches the condition, maybe you want only the record where ALL the elements in the collection match the condition.
The right syntax for the first case would be
SELECT FROM V where foo CONTAINS 10

the = syntax should succeed only when you pass a list, eg.
SELECT FROM V where foo = [10, 20, 30]

The same can be applied to <, <=, >, >= and so on. IMHO the syntax should be as explicit as you can read it, ie. 10 is greater than 5, but 10 is not greater than [5, 6, 7], and it's not even greater than [5, 10, 15]. This is why I think we should have another operator for this, something like (and I think it actually works)
SELECT FROM V where min(foo) >= 10

Even worse, the syntax you are using works fine if you have an index defined, but it works only because of an internal detail: OrientDB indexes defined on an collection attribute create an index entry for each element in the list. If you try to drop the index, you'll see that your query does not work anymore. IMHO this is not correct, an index should be an optimization, not a way to force a behavior.
I hope my point of view is clearer now
Thanks
Luigi

OK, let me see if I got you:
SELECT FROM V where foo IN [1,2,3]
is working now whether 'foo' is a single number or an embedded-list-long (on a list - it return true wether even ONE of the values if 'foo' exists inside the [1,2,3] parmeter list).
According to what you wrote I should change it when 'foo' is an embedded-list' to:
SELECT FROM V where foo CONTAINS 1 OR SELECT FROM V where foo CONTAINS 2 OR SELECT FROM V where foo CONTAINS 3
Is that so? Sould I change it to this long way?


Incoming/Outgoing section fails for long branch name

Type: Bug

Open Source Control with Incoming/Outgoing section enabled with branch that has long name - in my case 91 characters
Git output shows message [info] fatal: failed to stat 'refs/heads/feature/ followed by local and remote branch names and finished with : Filename too long
Incoming/Outgoing section does not show in Source Control

For branch with 74 character name, Incoming/Outgoing section is correctly displayed.
VS Code version: Code 1.85.0 (af28b32d7e553898b2a91af498b1fb666fdebe0c, 2023-12-06T20:48:09.019Z)
OS version: Windows_NT x64 10.0.22621
Modes:
Extensions (4)

Extension
Author (truncated)
Version

gitlens
eam
14.5.2

zopeneditor
IBM
1.0.3

vscode-language-pack-pl
MS-
1.85.2023120618

vscode-extension-for-zowe
Zow
2.12.2

Same issue here. My branch name is only 56 characters. It does use one level of nesting though (ie - mysprint/myfeature...)
Same git log.
Doesn't show changes under the Source Control tab and sometimes doesn't show all the buttons like the refresh button and commit check mark button.
Version: 1.85.1 (user setup)
Windows

This issue has been fixed in the latest VS Code Insiders release.

Looks verified 👍


[api-docs] Document OAuth2 guilds.members.read (#4204)

A new commit was made into the api-docs repo.
https://github.com/discord/discord-api-docs/commit/51227cb2d5e07818ebe0ddd39fda591f8d873104
This is a bot created issue.

discord just document its, well, docs.
Do we need to document anything?


python3Packages.jax: 0.3.4 -> 0.3.4

Motivation for this change
Upgrades python3Packages.jax from 0.3.4 to 0.3.4
This PR was automatically generated by nixpkgs-upkeep.

CI workflow that created this PR.
Internal tag: 671a0168661db50cc24c2b7c45654d1a.

Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[x] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

This is a bug. It thinks there's a new version bc there was a git diff, but the hashes are just in a different format. I'll work on a fix.

This is resolved in https://github.com/samuela/nixpkgs-upkeep/commit/864b5446fa1fbe76b5b9b20035a133d2f6feb547.


<table ?

How can I write table. got many data to send.

Hi,
I just wrote a component for that, waiting to be approved and merged ;)
https://github.com/mjmlio/mjml/pull/101

Hey @codeskyblue, could you explain us a bit better what you're trying to achieve?
So far, regular HTML tables can be included by wrapping it up in an mj-raw tag. From here, it should properly render.
Otherwise, yes as @swibge said, we started to implement such component, which is under review through PR #101. Feel free to have a look, share feedback and maybe contribute to it ;)?
Anyway, thanks for your interest in MJML.
Cheers

mj-table is part of 1.3 release :+1:

:+1:


Switch from MSON-AST to Data Struct Refract

This removes all references to the MSON-AST and replaces the example with refracted objects.

This need to wait until the above linked discussion is finalized.

@danielgtaylor @pksunkara can this be resolved with https://github.com/refractproject/rfcs/pull/10 merged?

Yup. We need to update this PR.

Ping @danielgtaylor

I'll get this updated ASAP and push it up for review. Thanks.

I believe I have addressed all the feedback and think that the document is now correct, but my confidence level isn't super high so please double check. I'm starting to think that maybe we want to have a source API Blueprint document / example in this repo and generate the output so we can be sure that:

The output is accurate based on the tool people will use.
The output matches what we expect.

Maybe it's all moot though with the refract changes. Thoughts?

Reviewed. Can you also look into the following things?

[ ] Update version
[ ] Remove raw and html from media types

@pksunkara I believe I've addressed all feedback. I wrote a quick sample document, ran it through drafter and used similar JSON here. Let me know if there's a better way to write any of it, thanks!

This PR is currently waiting on feedback from @zdne regarding the removal of raw and html from media types. If we do decide to remove them, then they need to removed from Parse Result.md too.

Also, parse result spec version should be changed to 2.2 and AST versions in the examples of that file should be updated.

@pksunkara @danielgtaylor I am up for removing raw (et al) as long as the implementation will stay backward compatible (e.g. it will still work with the Accept: application/vnd.apiblueprint.ast.raw+json header). Does this clarify?

A few minor things left.

@pksunkara should be ready to go!

Just a small minor thing still left.

Review passed. Waiting for drafter release to merge this PR.

Please tag and release


zenity errors from AppImage

Etcher version: 1.0.0-beta14
Operating system and architecture: PLD Linux x86_64

AppImage launcher spills some notices to terminal. otherwise it launches fine, but likely some zenity message i failed to see
[~/Downloads] ➔ ./Etcher-linux-x64.AppImage
/tmp/.mount_lynvJD/usr/bin/etcher.wrapper

(zenity:17783): Gtk-WARNING **: Could not find the icon 'dialog-question-ltr'. The 'hicolor' theme
was not found either, perhaps you need to install it.
You can get a copy from:
	http://icon-theme.freedesktop.org/releases

(zenity:17783): Gtk-WARNING **: Could not load a pixbuf from /org/gtk/libgtk/icons/48x48/status/image-missing.png.
This may indicate that pixbuf loaders or the mime database could not be found.
**
Gtk:ERROR:gtkiconhelper.c:493:ensure_surface_for_gicon: assertion failed: (destination)
./bin//etcher.wrapper: line 68: 17783 Aborted                 (core dumped) LD_LIBRARY_PATH="" zenity --question --title="$TITLE" --text="$TEXT"

Hi @glensc ,
The issue comes from the desktopintegration AppImage script, which attempts to show a dialog to create a link to the AppImage in your applications menu.
As a quick workaround, you can disable this AppImage feature using the following instructions: https://github.com/resin-io/etcher/blob/master/docs/USER-DOCUMENTATION.md#deactivate-desktop-shortcut-prompt-on-gnulinux
For a real fix, I suggest re-posting this in the AppImage project (https://github.com/probonopd/AppImageKit) and see what they think. If they have a fix, happy to upgrade the AppImages tooling here.

I'm closing this issue since it looks like a GTK bug (see https://bugzilla.gnome.org/show_bug.cgi?id=765649), or a GTK configuration issue. What GTK version are you running?
Please re-open if you find any insights.

gtk+2-2.24.30-1.x86_64 / gtk+3-3.20.6-1.x86_64 (not sure is gtk2 or gtk3 relevant)


Property 'fieldName' option and ORM 'namingStrategy' do not affect Embeddable for MongoDB

Describe the bug
Use MongoDB driver
Use @Property({fieldName: 'something'}) in embedded entity or choose UnderscoreNamingStrategy for ORM
In database embedded entity will have same naming as in code.
To Reproduce
Steps to reproduce the behavior:
import { Embeddable, Embedded, Entity, MikroORM, PrimaryKey, Property, UnderscoreNamingStrategy } from '@mikro-orm/core';
import { MongoDriver } from '@mikro-orm/mongodb';

@Embeddable()
class E {
  @Property()
  camelCase: string = 'c';

  @Property({fieldName: 'withALIAS'})
  withAlias: string = 'w';
}

@Entity()
class A {
  @PrimaryKey()
  _id = '1';

  @Property()
  complexName = 'n';

  @Embedded({entity: () => E, object: true})
  emBedded = new E()
}

let orm: MikroORM<MongoDriver>;

describe('GH issue 0', () => {
  beforeAll(async () => {
    orm = await MikroORM.init({
      entities: [A],
      clientUrl: 'mongodb://localhost:27017/mikro-orm-test',
      driver: MongoDriver,
      namingStrategy: UnderscoreNamingStrategy,
    });
    await orm.schema.clearDatabase();

    await orm.em.persistAndFlush(new A());
    orm.em.clear();
  });

  afterAll(async () => {
    await orm.close();
  });

  test('Ensure that embedded entity has underscore naming and fieldName is applied', async () => {
    const collection = orm.em.getDriver().getConnection().getDb().collection('a');
    expect(await collection.findOne({},{projection:{_id:0}})).toEqual({
      complex_name: 'n',
      em_bedded: {
        camel_case: 'c',
        withALIAS: 'w'
      }
    });
  });
});

Expected behavior
Renaming should propagate to the depth of embedded documents.
Versions

Dependency
Version

node
18

typescript
5

mikro-orm
5.7

your-driver
MongoDB

@B4nan I'm preparing PR but I'm not sure how object options should work.
In test tests/features/embeddables/nested-embeddables.mongo.test.ts I see that first @Embedded has object: true and it's effect propagates to nested embedded entities despite they dont have object: true option.
I expected that object option works on every level independently. It is natural: we traverse properties see Embedded and include it depending on it's object property, and then go deeper and transform nested embeddeds too.
In example  , which behavior is expected?
@Entity()
export class User {
  @PrimaryKey()
  id!: number;

  @Property()
  name!: string;

  @Embedded(() => Profile, { object: true, nullable: true })
  profile?: Profile;
}

@Embeddable()
export class Profile {
  @Property()
  username: string;

  @Embedded(() => Identity)
  identity: Identity;

  constructor(username: string, identity: Identity) {
    this.username = username;
    this.identity = identity;
  }
}

@Embeddable()
export class Identity {
  @Property()
  email: string;

  constructor(email: string) {
    this.email = email;
  }
}

becomes (because Profile includes Identity in inline mode by default)
User {
  id: '',
  name: '',
  profile: {
    username: '',
    identity_email: '',
  }
}

or (because root include was in object mode and all nested includes should be in object mode too)
User {
  id: '',
  name: '',
  profile: {
    username: '',
    identity: {
      email: '',
    }
  }
}

or (because root include was in object mode and all nested includes should be in object mode too)

It should be transitive.

This is probably a duplicate of #2165.

Oh from #2165 it looks like the problem is also in sqlite driver, example in issue uses sqlite.
And this issue is exactly in mongo driver.
In the end, both drivers do not apply prop.fieldName in embedded entities.
I'm not sure, but may it is possible to move the responsibility of renaming from drivers to core? Now I see that driver has to check meta and correctly apply it on reads and writes. Is there a reason why core cant do renaming?

Nope, that issue is about mongo, the reproduction was added by me as the same problem is with SQL drivers, but the fix will need to be handled on both ends.

IIRC its done this way so its not handled twice - the query builder already handles the conversion and is used internally too. Maybe it would be best to unify this.
FYI there is also #2361 which is kinda connected to all of this.

Closing as fixed in v6 via #4866


Set up the SEALS documentation

Describe the Task
Create a skeleton for the documentation for the GTI SEALS project. The task is to:

Set up the documentation structure in this repository
Set up webhooks with Read the Docs
Set up continuous integration to automatically update the generated documentation on Read the Docs when changes are made to various branches of the repository.

Time Estimate
1 day or less of work
Relevant Deadlines
None
Define the Metadata
Assignee

[x] Assign this Task to the appropriate person

Closed with PR #2.


Allow Raster.from_array and Raster.split_bands() to work without copying.

Right now, Raster.from_array() always returns a copy of the data that are given. This is most often the wanted behaviour, but there may be cases when this is not sought. The method should optimally have a copy attribute which defaults to True.
A case where this would be nice is with the Raster.split_bands() method (which calls Raster.from_array() and is therefore dependent on its copy-ness):
rgb = gu.Raster(datasets.get_path("landsat_RGB"))

red = rgb.split_bands(copy=False)[0]  # copy=False could be the default here.

red.data += 1  # Modify the red channel (it should also modify the rgb image)
assert np.array_equal(red.data, rgb.data[0, :, :])  # This should pass.

I believe this will be really difficult by design, because from_array creates a memory file, which need to have the data saved in itself.
This is probably a deeper level issue with rasterio...


ISSUE TYPE

Bug Report

ANSIBLE VERSION

2.12.2

COLLECTION VERSION

1.2.1

STEPS TO REPRODUCE

---
- name: Install JWS with ZIPs
  hosts: instance
  vars:
    jws_version: "{{ ews_version }}"
    jws_systemd_enabled: True
  tasks:
    - name: Import JWS role
      import_role:
        name: "{{ test_collection if test_collection is defined else 'redhat.jws'}}.jws"

EXPECTED RESULTS

Service has started. Tomcat is running.
ACTUAL RESULTS

/opt/jws-5.6/tomcat/bin/catalina.sh: line 504: /usr/lib/jvm/java/bin/java: No such file or directory\n/opt/jws-5.6/tomcat/bin/catalina.sh: line 504: /usr/lib/jvm/java/bin/java: No such file or directory

Will do asap!
I'm AFK at the moment, but normally, you should be able to set a var so that the collection is aware you have already installed a JVM it will use this one. However, we have no logic for detecting that Java is already installed. User either specify the JDK they want to use or the collection install the one by default.
@guidograzioli can you keep me honest here?

I took a look at the documentation and indeed there is no instructions to set the JDK. I have to make some test (I'm trying to write up a molecule scenario for this) to be confirmed that, but I think the expectation here is that Java is already correctly installed so that when the service starts the java command in the PATH of the server is the right one.
We may need to add a sentence like that in 3.3 part of the documentation to be clearer about it.
Regarding having the collection being able to detect and use automatically a Java installation, that could be a feature request for a later version. For this version, either the java version is provided and the collection installs the required dependency, either the JDK is installed and configured before the install role of the collection is invoked.

Had a look at the issue as well; we have code [4] to check and/or install the jdk rpm, that triggers when the jws_java_version is defined [1]; the default for it is not required and not defined, we provide it as an example in the default playbook [2].
We also have the molecule test that verifies the requested jvm is used to start jws [3].
In case the var is not defined, the java_home should default to a passed-in parameter [5] (jws.java_home in vars/default.yml) to the default jdk installation path, but we do not currently provide a variable to set it; so it falls back to the default jdk rpm installation path.
We should provide a jws_java_home variable in default/main.yml which allows to set arbitrary JDK paths (ie. is sets jws.java_home), the installation of which is owned by the user and it is to be used when jws_java_version is not defined
[1] https://github.com/ansible-middleware/jws/blob/main/roles/jws/tasks/main.yml#L58
[2] https://github.com/ansible-middleware/jws/blob/6072b83cf29a74a3579140c4a5a125a8dd09e8d6/playbooks/vars.yml#L3
[3] https://github.com/ansible-middleware/jws/blob/5d337fb3454fa0817bef409aa91f44fa7ecef372/molecule/force_install/verify.yml#L12
[4] https://github.com/ansible-middleware/jws/blob/5d337fb3454fa0817bef409aa91f44fa7ecef372/roles/jws/tasks/java_install.yml#L13
[5] https://github.com/ansible-middleware/jws/blob/main/roles/jws/templates/systemd/tomcat.conf.j2#L19

Fixed by PR208


Add back bevy_egui to LWIM 0.11

I tested minimal.rs using the egui feature just to make sure nothing broke, and it works.

Like changing the LWIM version to 0.11.1 and adding to the release notes that egui was added back?

Correct. I don't bother with the minor versions for the macro crate.


Refactor is hidden

Improves on https://github.com/dobtco/formrenderer-base/pull/150
Blocks https://github.com/dobtco/screendoor-v2/pull/4688
Previously we exposed a new method, isHidden that was a logical duplicate of the
existing isVisible method, but allowed the field collection to be passed in. It
turns out that Adam had already refactored isVisible and the ConditionChecker to
allow fields to be passed in from the outside.
Now we can get rid of isHidden, and extract the logic we want from isVisible and
use it for both isVisible and the new method FormBuilder will use, satisfiesConditions.
This is a huge improvement because now we don't have duplicated logic, and we don't have formbuilder specific logic in FormRenderer. The fact that isHidden determined that admin fields should be hidden is an example of FormBuilder specific logic (admin fields are not hidden in all contexts).

@drusepth, we forgot to make one tiny change in isHidden. Since ConditionChecker's constructor was modified in the merge, we needed to also update how isHidden initializes ConditionCheckers.
When I was looking into that, I figured that post Adam's refactor, theres actually a way cleaner way to make the formbuilder visibility checking work. I've implemented that in this PR.
Note: even if we merge this today, we can't merge the Screendoor PR (https://github.com/dobtco/screendoor-v2/pull/4688) until Screendoor is ready to point at the formrenderer repeating sections PR (as this newest change now sits on top of master, which has repeating sections).

so the priority is still to test repeating sections and point screendoor at formrenderer 2.2

I actually like this approach a lot better, it's a lot cleaner and clearer in what it does.
Whenever we're ready to merge this, it's ready to merge.


typo fixed

It appears that you have an unnecessary comma in a compound subject. Consider removing it

Thanks for your submission!
This Code of Conduct is derived from the template available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.md.  Please consider suggesting your changes to the Contributor Covenant team instead.
Thanks again for your interest in Atom!