Lose generic when spreading T | undefined where T is a generic object type

🔎 Search Terms
spread, union
🕗 Version & Regression Information
There are 2 problems. The first was changed between versions 4.0.5 and 4.1.5, and the second exists in every version of TS I tried in the Playground.
⏯ Playground Link
https://www.typescriptlang.org/play/?#code/GYVwdgxgLglg9mABMOcA8AVRBTAHlbMAEwGdE4AjAK22gD4AKKALkSwB9FwjtgYxsRAJSIA3gChEiAE7YoIaUlGIAdGqgAaZKlYAWAEyIAvgG5xR8eNCRYCRBQCG0zDnyFS5arSiMWbRJzcvPyCIhJSsvKKYqrqxmZGQA
💻 Code
// spread and add a property
function foo<T extends object>(t: T | undefined) {
  return { ...t, foo: 42 };
}

// just spread
function bar<T extends object>(t: T | undefined) {
  return { ...t };
}

🙁 Actual behavior

The result type of foo is { foo: number }.
The result type of bar is {}.

🙂 Expected behavior

The result type of foo is(T & { foo: number }) | { foo: number }.
The result type of bar is T.

Additional information about the issue
I'm not sure if this is same with #58617. But as there are some previous versions of TS work as I expected, I tend to treat it as a different issue and a bug.

I don't think there is a bug here. Spreading an undefined value creates no properties, so { ...t } produces {} when t is undefined. Thus, the result is T | {}, which reduces to just {} by subtype reduction.

I'm confused a little on the situation of foo. I think it is also because of subtype reduction which the type of { ...t, foo: number } is { foo: number }. But as we see it was (T & { foo: number }) | { foo: number } in some old versions of TS, did there happen some "breaking changes" on subtype reduction?


Write out manifest.json file when the RPC server is HUP'd

Describe the feature
Use case: view the documentation site rendered from the state in the rpc server. Desired flow:

edit some model sql, documentation, tests, etc
HUP the server
reload the index.html file from the target/ dir and see the new docs

Challenges:

serializing the manifest can be quite slow. Is this an unavoidable cost, or is there something we can do to support this feature without adding a significant delay to server HUP time?
this should work well with partial parsing
starting or HUP'ing the server does not actually invoke a compile -- in order to achieve the flow stated above, we would in fact need to invoke a whole dbt compile!

Tagging @beckjake to confirm these challenges above in case I got anything wrong.
Describe alternatives you've considered
I think that the use case described above is absolutely something we should work to support in the future, but it might require us to make server reloading work meaningfully differently. A shorter path to supporting this type of use case could just be to make dbt invocations (like dbt compile, dbt run) write out the manifest (and other artifacts) at the end of the run. This is already supported for dbt docs generate.
Who will this benefit
This will allow us to support docs viewing in the dbt Cloud IDE, as well as a similar flow for anyone else hosting the RPC server in a dev environment.

serializing the manifest can be quite slow. Is this an unavoidable cost, or is there something we can do to support this feature without adding a significant delay to server HUP time?

On reload, the manifest is built in a background thread. We could just serialize it there too. I'm not sure what we'd do to make serializing not slow - I guess we could replace our current json.dumps with something faster: orjson looks like it's the current state of the art. I think a lot of the time and effort is spent on jinja-rendering (required) and converting data into json (obviously required...). We could write less data to the manifest file, or present an alternative manifest-slim.json, etc. We could even just try calling the to_dict method with the flag that tells it to skip serializing None values!

starting or HUP'ing the server does not actually invoke a compile -- in order to achieve the flow stated above, we would in fact need to invoke a whole dbt compile!

If you want the compiled SQL: Yeah.
If you don't care, we could serialize the parsed manifest before compiling (that's what dbt compile does).

can we try out orjson (specifically https://github.com/ijl/orjson#dataclass), and see how it performs for manifest serialization before we make any big decisions here?
@beckjake if i remember correctly, the last time we tried to do this, it was specifically json serialization that was slow, and why we decided to use pickles for partial parsing. do you still have any JSON vs. pickle benchmark data we can look at?
if it works as advertised (40-50x speedup on dataclasses) then it seems like it could get us very far.

Well, it says it's 40-50x faster than other json libraries that serialize dataclasses, who knows what those or or what they're up to. I'm not sure it supports all the stuff we use hologram for.
I don't have any benchmark data, I didn't save it. I'm pretty sure it was the json part is what was slow, though of course if you pickle you also get to bypass the hologram to_dict stuff, which is extra bonus. If memory serves, it was not even close for large-ish manifests. I think parse results will be comparable to manifests - the differences are pretty minor, really: parse results are just sort of proto-manifests.

Let's make this an RPC method that returns the manifest from memory. TODO:

Figure out what we do about catalog and run_results (@drewbanin) cc @cmcarthur

The manifest that the RPC server has in memory is a manifest of parsed nodes, not compiled - we want the compiled form, right?

Yep - we're going to want the compiled manifest for sure. It's ok if this is slow at first, I bet there will be compelling ways for us to make it faster in the future. For the moment, we should just make the functionality available and then proceed from there.


<EMAIL_ADDRESS>builder breaks routing with now dev

I am unable to navigate to dynamic routes via full page refresh. Also static assets 404. Downgrading to<EMAIL_ADDRESS>fixes things for me. I am using a monorepo setup. All code is open source here: https://github.com/iamandyk/fitfam. Here is my now.json
{
  "version": 2,
  "name": "FitFam",
  "alias": "fitfam.me",
  "env": {
    "API_URL": "@fitfam-api-url",
    "GRAPHQL_API_URL": "@fitfam-graphql-api-url",
    "MYSQL_URL": "@fitfam-mysql-url",
    "FACEBOOK_APP_ID": "@fitfam-facebook-app-id",
    "FACEBOOK_APP_SECRET": "@fitfam-facebook-app-secret",
    "JWT_SECRET": "@fitfam-jwt-secret"
  },
  "build": {
    "env": {
      "MYSQL_URL": "@fitfam-mysql-url",
      "API_URL": "@fitfam-api-url",
      "GRAPHQL_API_URL": "@fitfam-graphql-api-url"
    }
  },
  "builds": [
    {
      "src": "api/routes/*.ts",
      "use": "@now/node"
    },
    {
      "src": "api/src/index.ts",
      "use": "@now/node",
      "config": {
        "maxLambdaSize": "25mb"
      }
    },

    { "src": "www/package.json", "use": "<EMAIL_ADDRESS>}
  ],
  "routes": [
    {
      "src": "/api/facebook-auth",
      "dest": "/api/routes/facebook-auth.ts"
    },
    {
      "src": "/api/(.*)",
      "dest": "/api/src/index.ts"
    },
    { "src": "/(.*)", "dest": "/www/$1", "continue": true }
  ]
}

The same happend to me, and I'm not using

Ditto.

Also having problems with 2.3.2 . With now dev routing seems broken, e.g. assets from the /public folder can't be found.

I have the same problems too.
Regardless whether or not a project has configurations for Next.js and Now, dynamic routing seems be broken.
For example, I put files like the following firstly.
/sample
  - /pages
    - /users
      - [id].jsx
    - index.jsx
  - package-lock.json
  - package.json

When I go to pages using dynamic routing such as /users/123 , the pages raise errors like the following.

If I go to these pages by only History API (e.g. <Link /> and Router.push() ), it's successful to render them. Also I can access pages not using dynamic routing such as / (or `/index).

Same here. Downgrading to<EMAIL_ADDRESS>"fixed" my application, as @iamandyk mentioned. Something related with dynamic routes, for sure.

Same story. public folder throws FILE_NOT_FOUND as well as dynamic routes. Please, fix.

Same for me. Note that you need to set<EMAIL_ADDRESS>via the builds section of now.json (eg "builds": [{ "src": "package.json", "use": "<EMAIL_ADDRESS>}],) and not via NPM/Yarn.

Same issue. Downgrading to<EMAIL_ADDRESS>fixed the issue for me.

Same issue here; Downgrading to<EMAIL_ADDRESS>also fix it for me.

Same issue with Now v17.1.1, @timswalling's solution fixed the issue for now...

same here with now 17.1.1

I just confirmed it works fine in v18.0.0 🎉

Closing this at it has been resolved from 18.0.0 onwards.


support junit 4

Move the code of the extension to a public class so the user can use it anywhere in any JUnit version.


E_NOTICE: MemcachePool::cas(): Server <IP_ADDRESS> (tcp 11223, udp 0) failed with: NOT_FOUND  (0)

Hello,
I encounter this notice everytime when I am using getAdp on a non-existing key.
Env details:
"leaseweb/memcache-bundle": "2.1.11"
PHP 5.5.30
memcache: 3.0.8
Thanks!

Add a "@" before the parent::cas command on line 115 in LoggingMemcache.php:
https://github.com/LeaseWeb/LswMemcacheBundle/blob/master/Cache/LoggingMemcache.php#L115

Thanks, but this is not what I was expected. :) So, there is not other solution for this issue?
With or without errors suppression, If found out that it is translated into a lot of sets to memcache, even if the key exists.
Could be something related to php-ext version?


Fix object serialization

Prevent inject from returning nil
https://github.com/remiprev/her/issues/401

Another option to help avoid an incorrect return type (while allowing the use of next) is to use Enumerable#each_with_object.  It might have a slight side benefit of making it a little harder for this to break in the future.  Speaking of which, I'd love to see a spec for this too.  From the contribution guide:

Add examples that describe it (in the spec directory). Only refactoring and documentation changes require no new tests. If you are adding functionality or fixing a bug, we need examples!

I'm not entirely sure how to build a spec for This scenario. Also it might even be overkill considering it's a bad usage of inject.
Regarding the each with object, I agree it might be a better solution to the inject in this case.

hi @avdmatamoros @mtwentyman @cimtico I've just got commit access on this repo and plan to get back on track with maintenance over time - will be in touch soon!


TN-351 formatted coredata.py, crossdomain.py, demographics.py, fhir.py

Hello @John0Randolph! Thanks for submitting the PR.

In the file portal/views/coredata.py, following are the PEP8 issues :

Line 215:19: E128 continuation line under-indented for visual indent

In the file portal/views/fhir.py, following are the PEP8 issues :

Line 32:80: E501 line too long (80 > 79 characters)
Line 33:80: E501 line too long (80 > 79 characters)


404 when trying to get the token icon for Ether.

get https://lunaria.dark.florist/js/components/Icon/Tokens/Ether.js net::ERR_ABORTED 404

// in ts/components/Icon/Tokens/index.tsx
const module = await import(path)

Separately, why are these images being imported dynamically via JS rather than just being referenced as .svgs?  Seems like you could just have the component be <img src={path}/> and store them on disk as SVGs.  Same question for everything in Icon folder it appears.

There's a quick fix at the moment for the missing icon (invalid path) #101. Keeping this issue open since SVG handling would require #92 to complete first

#115 image paths are now applied in new UI


Captcha  solver

Bro pls add captcha solver in it

Working on it

Bro pls add captcha solver in it
—
Reply to this email directly, view it on GitHub
https://github.com/MehulKhanna/PokeGrinder/issues/24, or unsubscribe
https://github.com/notifications/unsubscribe-auth/BCRN65XT3VEKMLH5EPO3I4LYKMNDJAVCNFSM6AAAAABA5FJSOGVHI2DSMVQWIX3LMV43ASLTON2WKOZSGA2TAOJXGU4TINA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Working on it
…
Bro pls add captcha solver in it — Reply to this email directly, view it on GitHub <#24>, or unsubscribe https://github.com/notifications/unsubscribe-auth/BCRN65XT3VEKMLH5EPO3I4LYKMNDJAVCNFSM6AAAAABA5FJSOGVHI2DSMVQWIX3LMV43ASLTON2WKOZSGA2TAOJXGU4TINA . You are receiving this because you are subscribed to this thread.Message ID: @.***>

ETA?

Working on it
…
Bro pls add captcha solver in it — Reply to this email directly, view it on GitHub <#24>, or unsubscribe https://github.com/notifications/unsubscribe-auth/BCRN65XT3VEKMLH5EPO3I4LYKMNDJAVCNFSM6AAAAABA5FJSOGVHI2DSMVQWIX3LMV43ASLTON2WKOZSGA2TAOJXGU4TINA . You are receiving this because you are subscribed to this thread.Message ID: @.***>

ETA?

Idk bro, maybe same last year MehulKhanna drop it
Working on it

… <#m_7208229603353838911_>
Bro pls add captcha solver in it — Reply to this email directly, view it
on GitHub <#24 https://github.com/MehulKhanna/PokeGrinder/issues/24>,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BCRN65XT3VEKMLH5EPO3I4LYKMNDJAVCNFSM6AAAAABA5FJSOGVHI2DSMVQWIX3LMV43ASLTON2WKOZSGA2TAOJXGU4TINA
. You are receiving this because you are subscribed to this thread.Message
ID: @.***>
ETA?
—
Reply to this email directly, view it on GitHub
https://github.com/MehulKhanna/PokeGrinder/issues/24#issuecomment-1865436756,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BCRN65SRK3HV6TNHJ3YCG6DYKOW3DAVCNFSM6AAAAABA5FJSOGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNRVGQZTMNZVGY
.
You are receiving this because you commented.Message ID:
@.***>

Bro pls add captcha solver in it

done almost

Bro pls add captcha solver in it

done almost

Oh nice waiting for the release


Some fixes to snapshot uploading

Two fixes to support uploading a snapshot:

responses for putting a block and completing a snapshot should be 201 and 202 respectively rather than 200; HTTP 201 and 202 are expected by the .NET AWS API for the respective operations.

If the body cannot be utf-8 decoded, try base64.

Hi @jdtsillas, thanks for the PR!
What is the reasoning behind the base64-change?
Also, it would be good to have tests for these changes, ideally by extending the existing DotNet tests:
https://github.com/getmoto/moto/tree/master/other_langs/tests_dotnet/ExampleTestProject
The tests are executed like so:
https://github.com/getmoto/moto/blob/master/.github/workflows/tests_sdk_dotnet.yml


from imgaug import augmenters as iaa

--------------------------------------------------------------------------
ImportError                               Traceback (most recent call last)
<ipython-input-2-f2c5951829dd> in <module>()
      4 import numpy as np
      5 import imgaug
----> 6 from imgaug.augmentables.segmaps import SegmentationMapsOnImage

ImportError: cannot import name 'SegmentationMapsOnImage' from 'imgaug.augmentables.segmaps' (/usr/local/lib/python3.7/dist-packages/imgaug/augmentables/segmaps.py)

---------------------------------------------------------------------------
NOTE: If your import is failing due to a missing package, you can
manually install dependencies using either !pip or !apt.

To view examples of installing some common dependencies, click the
"Open Examples" button below.

I have been doing this on google colab pro, but it does not work.


F5 is broken for a console application

Create a console application, restore and F5:

Is this related to the startup project work or launch profiles?
@basoundr @BillHiebert

I was able to get it a few times but now I am not able to get it. On F5, the application seems to be starting and completes without doing anything.
The Debug window says this:
The program '[4256] dotnet.exe' has exited with code -2147450749 (0x80008083).
The program '[4256] dotnet.exe: Program Trace' has exited with code 0 (0x0).

Relevant? http://stackoverflow.com/questions/38175242/the-program-13492-dotnet-exe-has-exited-with-code-2147450749

There are also a couple of issues in aspnet/tooling: https://github.com/aspnet/Tooling/issues/646 and https://github.com/aspnet/Tooling/issues/538. Maybe this has something to do with the version of the cli that ships with VS?


updated json dump helper to handle CommissionableNode structure

TypeError: Type is not JSON serializable: CommissionableNode
python3 --version Python 3.10.12
Suspected Reason:
json dumps handler cannot handle CommissionableNode structure
Steps to reproduce:

flash latest esp32 lighting-app example to ESP32 dev kit

commission esp32 lighting-app example using chip-tool
./chip-tool pairing ble-wifi 0x1 MYSSID MYPASS 20202021 3840

Once commissioning is successful as node 1, open a commissioning window:
./chip-tool pairing open-commissioning-window 1 1 300 1000 2365

run a discover from the python-matter-server
{"message_id": "1","command": "discover"}

python-matter-server log shows:
023-12-04 12:00:57 dell matter_server.server.client_handler[2017833] DEBUG [140135655073504] Received CommandMessage(message_id='1', command='discover', args=None)
2023-12-04 12:00:57 dell matter_server.server.client_handler[2017833] DEBUG [140135655073504] Handling command discover
2023-12-04 12:00:57 dell chip.DL[2017833] INFO Avahi browse: cache new
2023-12-04 12:00:57 dell chip.DL[2017833] INFO Avahi browse: cache new
2023-12-04 12:00:57 dell chip.DL[2017833] INFO Avahi browse: cache exhausted
2023-12-04 12:00:58 dell chip.DL[2017833] INFO Avahi browse: all for now
2023-12-04 12:00:58 dell chip.DL[2017833] INFO Avahi resolve found
2023-12-04 12:00:58 dell chip.DIS[2017833] DEBUG Discovered node:
2023-12-04 12:00:58 dell chip.DIS[2017833] DEBUG        Hostname: 58BF2593B9A8
2023-12-04 12:00:58 dell chip.DIS[2017833] DEBUG        IP Address #1: <IP_ADDRESS>
2023-12-04 12:00:58 dell chip.DIS[2017833] DEBUG        Port: 5540
2023-12-04 12:00:58 dell chip.DIS[2017833] DEBUG        Mrp Interval idle: not present
2023-12-04 12:00:58 dell chip.DIS[2017833] DEBUG        Mrp Interval active: not present
2023-12-04 12:00:58 dell chip.DIS[2017833] DEBUG        TCP Supported: 1
2023-12-04 12:00:58 dell chip.DIS[2017833] DEBUG        Vendor ID: 65521
2023-12-04 12:00:58 dell chip.DIS[2017833] DEBUG        Product ID: 32768
2023-12-04 12:00:58 dell chip.DIS[2017833] DEBUG        Long Discriminator: 2365
2023-12-04 12:00:58 dell chip.DIS[2017833] DEBUG        Pairing Hint: 36
2023-12-04 12:00:58 dell chip.DIS[2017833] DEBUG        Instance Name: 35D42B385A32DC31
2023-12-04 12:00:58 dell chip.DIS[2017833] DEBUG        Commissioning Mode: 2
2023-12-04 12:00:58 dell chip.CTL[2017833] ERROR Unknown filter type; all matches will fail
2023-12-04 12:00:58 dell chip.DL[2017833] INFO Avahi resolve found
2023-12-04 12:00:58 dell chip.DIS[2017833] DEBUG Discovered node:
2023-12-04 12:00:58 dell chip.DIS[2017833] DEBUG        Hostname: 58BF2593B9A8
2023-12-04 12:00:58 dell chip.DIS[2017833] DEBUG        IP Address #1: <IP_ADDRESS>
2023-12-04 12:00:58 dell chip.DIS[2017833] DEBUG        Port: 5540
2023-12-04 12:00:58 dell chip.DIS[2017833] DEBUG        Mrp Interval idle: not present
2023-12-04 12:00:58 dell chip.DIS[2017833] DEBUG        Mrp Interval active: not present
2023-12-04 12:00:58 dell chip.DIS[2017833] DEBUG        TCP Supported: 1
2023-12-04 12:00:58 dell chip.DIS[2017833] DEBUG        Vendor ID: 65521
2023-12-04 12:00:58 dell chip.DIS[2017833] DEBUG        Product ID: 32768
2023-12-04 12:00:58 dell chip.DIS[2017833] DEBUG        Long Discriminator: 2365
2023-12-04 12:00:58 dell chip.DIS[2017833] DEBUG        Pairing Hint: 36
2023-12-04 12:00:58 dell chip.DIS[2017833] DEBUG        Instance Name: 35D42B385A32DC31
2023-12-04 12:00:58 dell chip.DIS[2017833] DEBUG        Commissioning Mode: 2
2023-12-04 12:00:58 dell chip.CTL[2017833] ERROR Unknown filter type; all matches will fail
2023-12-04 12:00:59 dell chip.DL[2017833] INFO Avahi browse: cache new
2023-12-04 12:00:59 dell chip.DL[2017833] INFO Avahi browse: cache new
2023-12-04 12:00:59 dell chip.DL[2017833] INFO Avahi browse: cache exhausted
2023-12-04 12:01:00 dell chip.DL[2017833] INFO Avahi browse: all for now
2023-12-04 12:01:00 dell chip.DL[2017833] INFO Avahi resolve found
2023-12-04 12:01:00 dell chip.DIS[2017833] DEBUG Discovered node:
2023-12-04 12:01:00 dell chip.DIS[2017833] DEBUG        Hostname: 58BF2593B9A8
2023-12-04 12:01:00 dell chip.DIS[2017833] DEBUG        IP Address #1: <IP_ADDRESS>
2023-12-04 12:01:00 dell chip.DIS[2017833] DEBUG        Port: 5540
2023-12-04 12:01:00 dell chip.DIS[2017833] DEBUG        Mrp Interval idle: not present
2023-12-04 12:01:00 dell chip.DIS[2017833] DEBUG        Mrp Interval active: not present
2023-12-04 12:01:00 dell chip.DIS[2017833] DEBUG        TCP Supported: 1
2023-12-04 12:01:00 dell chip.DIS[2017833] DEBUG        Vendor ID: 65521
2023-12-04 12:01:00 dell chip.DIS[2017833] DEBUG        Product ID: 32768
2023-12-04 12:01:00 dell chip.DIS[2017833] DEBUG        Long Discriminator: 2365
2023-12-04 12:01:00 dell chip.DIS[2017833] DEBUG        Pairing Hint: 36
2023-12-04 12:01:00 dell chip.DIS[2017833] DEBUG        Instance Name: 35D42B385A32DC31
2023-12-04 12:01:00 dell chip.DIS[2017833] DEBUG        Commissioning Mode: 2
2023-12-04 12:01:00 dell chip.CTL[2017833] ERROR Unknown filter type; all matches will fail
2023-12-04 12:01:00 dell chip.DL[2017833] INFO Avahi resolve found
2023-12-04 12:01:00 dell chip.DIS[2017833] DEBUG Discovered node:
2023-12-04 12:01:00 dell chip.DIS[2017833] DEBUG        Hostname: 58BF2593B9A8
2023-12-04 12:01:00 dell chip.DIS[2017833] DEBUG        IP Address #1: <IP_ADDRESS>
2023-12-04 12:01:00 dell chip.DIS[2017833] DEBUG        Port: 5540
2023-12-04 12:01:00 dell chip.DIS[2017833] DEBUG        Mrp Interval idle: not present
2023-12-04 12:01:00 dell chip.DIS[2017833] DEBUG        Mrp Interval active: not present
2023-12-04 12:01:00 dell chip.DIS[2017833] DEBUG        TCP Supported: 1
2023-12-04 12:01:00 dell chip.DIS[2017833] DEBUG        Vendor ID: 65521
2023-12-04 12:01:00 dell chip.DIS[2017833] DEBUG        Product ID: 32768
2023-12-04 12:01:00 dell chip.DIS[2017833] DEBUG        Long Discriminator: 2365
2023-12-04 12:01:00 dell chip.DIS[2017833] DEBUG        Pairing Hint: 36
2023-12-04 12:01:00 dell chip.DIS[2017833] DEBUG        Instance Name: 35D42B385A32DC31
2023-12-04 12:01:00 dell chip.DIS[2017833] DEBUG        Commissioning Mode: 2
2023-12-04 12:01:00 dell chip.CTL[2017833] ERROR Unknown filter type; all matches will fail
2023-12-04 12:01:00 dell chip.DL[2017833] INFO Avahi resolve found
2023-12-04 12:01:00 dell chip.DIS[2017833] DEBUG Discovered node:
2023-12-04 12:01:00 dell chip.DIS[2017833] DEBUG        Hostname: 58BF2593B9A8
2023-12-04 12:01:00 dell chip.DIS[2017833] DEBUG        IP Address #1: <IP_ADDRESS>
2023-12-04 12:01:00 dell chip.DIS[2017833] DEBUG        Port: 5540
2023-12-04 12:01:00 dell chip.DIS[2017833] DEBUG        Mrp Interval idle: not present
2023-12-04 12:01:00 dell chip.DIS[2017833] DEBUG        Mrp Interval active: not present
2023-12-04 12:01:00 dell chip.DIS[2017833] DEBUG        TCP Supported: 1
2023-12-04 12:01:00 dell chip.DIS[2017833] DEBUG        Vendor ID: 65521
2023-12-04 12:01:00 dell chip.DIS[2017833] DEBUG        Product ID: 32768
2023-12-04 12:01:00 dell chip.DIS[2017833] DEBUG        Long Discriminator: 2365
2023-12-04 12:01:00 dell chip.DIS[2017833] DEBUG        Pairing Hint: 36
2023-12-04 12:01:00 dell chip.DIS[2017833] DEBUG        Instance Name: 35D42B385A32DC31
2023-12-04 12:01:00 dell chip.DIS[2017833] DEBUG        Commissioning Mode: 2
2023-12-04 12:01:00 dell chip.CTL[2017833] ERROR Unknown filter type; all matches will fail
2023-12-04 12:01:00 dell chip.DL[2017833] INFO Avahi resolve found
2023-12-04 12:01:00 dell chip.DIS[2017833] DEBUG Discovered node:
2023-12-04 12:01:00 dell chip.DIS[2017833] DEBUG        Hostname: 58BF2593B9A8
2023-12-04 12:01:00 dell chip.DIS[2017833] DEBUG        IP Address #1: <IP_ADDRESS>
2023-12-04 12:01:00 dell chip.DIS[2017833] DEBUG        Port: 5540
2023-12-04 12:01:00 dell chip.DIS[2017833] DEBUG        Mrp Interval idle: not present
2023-12-04 12:01:00 dell chip.DIS[2017833] DEBUG        Mrp Interval active: not present
2023-12-04 12:01:00 dell chip.DIS[2017833] DEBUG        TCP Supported: 1
2023-12-04 12:01:00 dell chip.DIS[2017833] DEBUG        Vendor ID: 65521
2023-12-04 12:01:00 dell chip.DIS[2017833] DEBUG        Product ID: 32768
2023-12-04 12:01:00 dell chip.DIS[2017833] DEBUG        Long Discriminator: 2365
2023-12-04 12:01:00 dell chip.DIS[2017833] DEBUG        Pairing Hint: 36
2023-12-04 12:01:00 dell chip.DIS[2017833] DEBUG        Instance Name: 35D42B385A32DC31
2023-12-04 12:01:00 dell chip.DIS[2017833] DEBUG        Commissioning Mode: 2
2023-12-04 12:01:00 dell chip.CTL[2017833] ERROR Unknown filter type; all matches will fail
2023-12-04 12:01:02 dell chip.DIS[2017833] INFO Commissionable Node 0
2023-12-04 12:01:02 dell matter_server.server.client_handler[2017833] ERROR [140135655073504] Error handling message: CommandMessage(message_id='1', command='discover', args=None)
TypeError

The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/home/ivob/Projects/python-matter-server/matter_server/server/client_handler.py", line 189, in _run_handler
self._send_message(SuccessResultMessage(msg.message_id, result))
File "/home/ivob/Projects/python-matter-server/matter_server/server/client_handler.py", line 221, in _send_message
_message = json_dumps(message)
File "/home/ivob/Projects/python-matter-server/matter_server/common/helpers/json.py", line 40, in json_dumps
return orjson.dumps(
TypeError: Type is not JSON serializable: CommissionableNode

I don't like this approach. I think we should just make sure that either CommissionableNode is serializable or convert it to our own object within the discover method.
The to/from json helpers should be for generic types only that are common within the matter stack.

Hi. That's a fair comment. It would be better to handle the serialisation elsewhere.
I can make a change to this PR. Could you give me a little guidance on how I could make CommissionableNode serializable or convert it to  object within the discover method.? I am learning so if you can have a little patience with my lack of knowledge of this library I will be able to help out with other changes.

This is actually a bit of messy in the sdk... CommissionableNode inherits from discovery.CommissionableNode (which is a dataclass) but with some non-serializable fields and methods. In my opinion this mixing of dataclasses and custom classes is just a bad code pattern.
Long term goal we should fix these issues upstream but the list is already getting long of stuff we found and want to fix at some point.
I think the only short-term fix for now is initializing a discovery.CommissionableNode from the data received.

Hi @marcelveldt ,
I see what you mean. I tried various different approaches but it seems no matter what I do the JSON library cant serialize the CommissionableNode object. I dont really know why some SDK object serialize no problem and others throw this type of error.
I wasnt exact sure what you meant by initializing a discovery.CommissionableNode from the data received. When I tried this approach the json serialization still failed. So I went a little further with this approach and created a new dataclass for CommissionableNodeData in models.py
@dataclass
class CommissionableNodeData:
    """Message sent by the server when a client runs does a discover CommissionableNodes."""

    instanceName: str
    hostName: str
    port: int
    longDiscriminator: int
    vendorId: int
    productId: int
    commissioningMode: int
    deviceType: int
    deviceName: str
    pairingInstruction: str
    pairingHint: int
    mrpRetryIntervalIdle: int
    mrpRetryIntervalActive: int
    supportsTcp: bool
    addresses: list[dict]
    rotatingId: int

and then, back in device_controller.py, I initialized a new instance of this dataclass from the data returned from the sdk.
    @api_command(APICommand.DISCOVER)
    async def discover_commissionable_nodes(
        self,
    ) -> CommissionableNodeData | list[CommissionableNodeData] | None:
        """Discover Commissionable Nodes (discovered on BLE or mDNS)."""
        if self.chip_controller is None:
            raise RuntimeError("Device Controller not initialized.")

        result = await self._call_sdk(
            self.chip_controller.DiscoverCommissionableNodes,
        )

        commissionable_nodes = [CommissionableNodeData(
                instanceName = node.instanceName,
                hostName = node.hostName,
                port = node.port,
                longDiscriminator = node.longDiscriminator,
                vendorId = node.vendorId,
                productId = node.productId,
                commissioningMode = node.commissioningMode,
                deviceType = node.deviceType,
                deviceName = node.deviceName,
                pairingInstruction = node.pairingInstruction,
                pairingHint = node.pairingHint,
                mrpRetryIntervalIdle = node.mrpRetryIntervalIdle,
                mrpRetryIntervalActive = node.mrpRetryIntervalActive,
                supportsTcp = node.supportsTcp,
                addresses = node.addresses,
                rotatingId = node.rotatingId,
            ) for node in result]

        return commissionable_nodes

Its still not a great solution as we would need to update the dataclass if the SDK changes the fields returned in the chip_controller.DiscoverCommissionableNodes function.
Anyways I am happy to make a change to this PR with the above. Or if you can suggest a more elegant approach please let me know and I will try that.

Hi @marcelveldt ,
I see what you mean. I tried various different approaches but it seems no matter what I do the JSON library cant serialize the CommissionableNode object. I dont really know why some SDK object serialize no problem and others throw this type of error.
I wasnt exact sure what you meant by initializing a discovery.CommissionableNode from the data received. When I tried casting the results to the  discovery.CommissionableNode dataclass but the JSON serialization failed again. In the end I went ahead a hard-coded the initialization of each of the fields in the dataclass.
    @api_command(APICommand.DISCOVER)
    async def discover_commissionable_nodes(
        self,
    ) -> CommissionableNode | list[CommissionableNode] | None:
        """Discover Commissionable Nodes (discovered on BLE or mDNS)."""
        if self.chip_controller is None:
            raise RuntimeError("Device Controller not initialized.")

        result = await self._call_sdk(
            self.chip_controller.DiscoverCommissionableNodes,
        )

        commissionable_nodes = [CommissionableNode(
                instanceName = node.instanceName,
                hostName = node.hostName,
                port = node.port,
                longDiscriminator = node.longDiscriminator,
                vendorId = node.vendorId,
                productId = node.productId,
                commissioningMode = node.commissioningMode,
                deviceType = node.deviceType,
                deviceName = node.deviceName,
                pairingInstruction = node.pairingInstruction,
                pairingHint = node.pairingHint,
                mrpRetryIntervalIdle = node.mrpRetryIntervalIdle,
                mrpRetryIntervalActive = node.mrpRetryIntervalActive,
                supportsTcp = node.supportsTcp,
                addresses = node.addresses,
                rotatingId = node.rotatingId,
            ) for node in result]

        return commissionable_nodes```

Its still not a great solution as we would need to update the dataclass if the SDK changes the fields returned in the chip_controller.DiscoverCommissionableNodes function.

Anyways I am happy to make a change to this PR with the above. Or if you can suggest a more elegant approach please let me know and I will try that.

p.s. when I took out this import:
from chip.ChipDeviceCtrl import CommissionableNode

I started getting errors about certificate authorities so I left that line in and put this one under it:
from chip.discovery import CommissionableNode

#490 has been merged with a fix for this one.
Thanks anyways for the efforts @oidebrett !

Thanks for letting me know. Sorry for not getting onto this before now. Was on leave. Good to hear it's fixed and I like your solution. If there's something else I can help with let me know.


Latest release (v0.2.3) is crashing when http or grpc add is provided in configuration

Removing these two configs (OPENFGA_HTTP_ADDR and OPENFGA_GRPC_ADDR) allows the service to start.
The configuration is passed through docker compose, like so:
services:
  openfga:
    image: openfga/openfga
    # ...
    environment:
      OPENFGA_HTTP_ADDR: ":${OPENFGA_HTTP_PORT}"
      OPENFGA_GRPC_ADDR: ":${OPENFGA_GRPC_PORT}"

Note: This used to work on v0.2.2
More info

Run through: official docker image & docker-compose
OpenFGA version: v0.2.3

Logs
{"level":"info","ts":1665181651.7706127,"caller":"logger/logger.go:48","msg":"using 'postgres' storage engine","build.version":"v0.2.3","build.commit":"07a7a1a7eaa4d04f2c9e7efed40072ae2f3560b4"}
{"level":"warn","ts":1665181651.7706547,"caller":"logger/logger.go:52","msg":"grpc TLS is disabled, serving connections using insecure plaintext","build.version":"v0.2.3","build.commit":"07a7a1a7eaa4d04f2c9e7efed40072ae2f3560b4"}
{"level":"warn","ts":1665181651.7706614,"caller":"logger/logger.go:52","msg":"HTTP TLS is disabled, serving connections using insecure plaintext","build.version":"v0.2.3","build.commit":"07a7a1a7eaa4d04f2c9e7efed40072ae2f3560b4"}
{"level":"warn","ts":1665181651.7706642,"caller":"logger/logger.go:52","msg":"authentication is disabled","build.version":"v0.2.3","build.commit":"07a7a1a7eaa4d04f2c9e7efed40072ae2f3560b4"}
{"level":"fatal","ts":1665181651.7706723,"caller":"logger/logger.go:64","msg":"failed to initialize openfga server","build.version":"v0.2.3","build.commit":"07a7a1a7eaa4d04f2c9e7efed40072ae2f3560b4","error":"failed to parse the 'grpc.addr' config: no IP","stacktrace":"github.com/openfga/openfga/pkg/logger.(*ZapLogger).Fatal\n\t/home/runner/work/openfga/openfga/pkg/logger/logger.go:64\ngithub.com/openfga/openfga/pkg/cmd.run\n\t/home/runner/work/openfga/openfga/pkg/cmd/run.go:55\ngithub.com/spf13/cobra.(*Command).execute\n\t/home/runner/go/pkg/mod/github.com/spf13/cobra@v1.5.0/command.go:876\ngithub.com/spf13/cobra.(*Command).ExecuteC\n\t/home/runner/go/pkg/mod/github.com/spf13/cobra@v1.5.0/command.go:990\ngithub.com/spf13/cobra.(*Command).Execute\n\t/home/runner/go/pkg/mod/github.com/spf13/cobra@v1.5.0/command.go:918\nmain.main\n\t/home/runner/work/openfga/openfga/cmd/openfga/openfga.go:18\nruntime.main\n\t/opt/hostedtoolcache/go/1.18.6/x64/src/runtime/proc.go:250"}

Reported by @ghstahl

@ghstahl this should be fixed now on the main branch. Our next release will include it.


ruffle: nightly-2024-09-12 -> nightly-2024-11-07

This update contains various AVM2 and text improvements, among other things. A couple of the cargoLock.outputHashes entries are removed. Presumably, Ruffle is inching closer and closer to its first stable release, but there are no updates on where that is yet.
Full changelog: https://github.com/ruffle-rs/ruffle/compare/nightly-2024-09-12...nightly-2024-11-07
Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Not a regression https://hydra.nixos.org/build/276796207


Suppress the warning if verify=False

Setting verify to False differs from verify=None in being explicitly set,
and therefore the warning being undesirable.
See this for the a proposed alternative that involves importing
implementation details of Requests onto the application:
https://github.com/kennethreitz/requests/issues/2214#issuecomment-72941896
This fix avoids deep imports and pulling the knowledge of internals of
Requests into the application.
Fixes #2214

Some notes:

urllib3 is a separate project that we vendor in its entirety. This PR affects it, and so requires a separate change in that library.
'Explicit' is dependent on who you are. This is 'explicit' to the person who calls requests, but not to the person above them, if any. The warning is not just for the person writing against requests, but for anyone who uses an application that uses requests.

I'm -1 on this change.

CERT_EXPLICITLY_NONE means nothing and doesn't add much value here. Given that this is mostly in urllib3 and would rely on acceptance there, I'm closing this until progress has been made there.

Sorry, but the closing statement is false. CERT_EXPLICITLY_NONE means CERT_NONE set explicitly, and its value is making the distinction between such case and CERT_NONE set explicitly, purely by the lack of certificates.

@zaitcev The closing statement was: "Given that this is mostly in urllib3 and would rely on acceptance there, I'm closing this until progress has been made there."

@zaitcev CERT_NONE, CERT_REQUIRED and CERT_OPTIONAL are all defined on the ssl module and have a real meaning in the context of performing validation. CERT_EXPLICITLY_NONE means absolutely nothing in the same context.


Question: if bind_uri is deprecated, how remotelly access docker instance

Hi, I would like to run kitchen tests on remote docker. For this purpose I use vagrant to deploy docker instance using your cookbook.
However to use it, then I need to access it remotely (and for sure securely). So I agree using exposed port 4242 through bind_uri is not secure and  deprecated, but what are the other alternatives?
Do we have cookboos that expose the docker.sock over https?
Does Kitchen-CI have an option to tunnel remote unix:/var/run/docker.sock socket to kitchen host?
Thanks in advance.

Closing issue due to inactivity. Please open a new issue if this is still relevant. Thanks!


I would like to learn more about your program so I would like to ask you a few questions.

Hello, first of all thank you very much for sharing, this is very helpful for me. I would like to learn more about your program so I would like to ask you a few questions. First of all, what is the physical method you used and do you have any references for your thermodynamic model. I would like to have a clearer understanding.

Hello, sorry for the delay, just read the message.
I will recommend the book by Basu Biomass pyrolysis, gasification. combustion and torrefaction. Also, check my papers on Scopus. Olagoke Oladokun

Thank you very much for the recommended book and paper. You have done an excellent job of studying the gasification process. The stoichiometric models you used to simulate the gasification process by your own programming treat the gas as an ideal gas because the pressure of the gasification process you simulated is low. For example, in this article:Sensitivity analysis of Biohydrogen Production from Imperata cylindrica Using Stoichiometric Equilibrium Model. But the gasification process at high pressures requires treating the gas as a real gas and using the real gas equation of state such as the PR or SRK equation to calculate the fugacity. For example, in this article:Two-stage equilibrium model for a coal gasifier to predict the accurate carbon conversion in hydrogen production.Have you programmed your own simulation of gasification at high pressures. I would be grateful if you could share the program with me so that I can learn it.
------------------ 原始邮件 ------------------
发件人:                                                                                "goke-ai/gasific"                                                                                @.>;
发送时间: 2021年12月2日(星期四) 上午6:20
@.>;
<EMAIL_ADDRESS>主题: Re: [goke-ai/gasific]  I would like to learn more about your program so I would like to ask you a few questions.  (Issue #1)
Hello, sorry for the delay, just read the message.
I will recommend the book by Basu Biomass pyrolysis, gasification. combustion and torrefaction. Also, check my papers on Scopus. Olagoke Oladokun
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.


deal with dso_pandocfilter

Description of feature
dso provides a second CLI: dso_pandocfilter that is mostly intended to be used internally for the watermarking.
This command should obviously also match the specified dso version.
Ideally, we can get rid of that command altogether, possibly by using something like python -m dso.pandocfilter and python is the absolute path to the binary that's currently used to execute dso.

done in v0.10


Working dataProvider as object

Works in conjunction with
https://github.com/dpla/sparkindexer/pull/55

I added the ability to facet on dataProvider.name and dataProvider.@id for consistency with the provider facet.  I tested it locally.


choose a folder name other than html under /var/www/ for where site code resides

Is there an existing issue for this?

[X] I have searched the existing issues

Is your feature request related to a problem?
Problem as described here:
https://stackoverflow.com/questions/76603421/how-to-change-ddev-php-container-docroot-path-from-var-www-html

I need to change the docroot path that ddev sets up in the php container because I have some code that has already had an html folder in its source and bespoke include path determination is not working.
The code looks for the first occurrence of html to set a path to include files at another location. But because both the code and ddev php container have html, there are 2 occurrences of html in the path and the code now forms the path incorrectly. It's legacy code and the routine is done many times in the code so I'd rather not change each file to avoid larger pull request diffs.

I tried @rfay's suggestion on that link:

created a docker-compose.mounts.yaml directly under .ddev.
contents:

services:
  web:
    volumes:
    - ../:/var/www/docroot

deleted my project
ddev config
ddev said that the folder wasn't created (which is what I'd expect) but that it would create it
ddev start
ddev ssh and observed folder /var/www/docroot exists
But on visiting the site I get "Forbidden".

Describe your solution
Not known.
Describe alternatives
change the code but there are a lot of instances of the reliance on html and this would affect our live code as well.
Additional context
No response

In general we don't try to add enhancements to support one project's misbehaving old code :)


Fix typo: "sand-serif" to "sans-serif"

Another one^^

Wait don't merge... I committed from github and you've merged my previous PR in the meantime... meaning I committed an older version, effectively reversing the previous fix ><"

My bad, it's fixed.


TFRS-2145- Added BC Attorney Address on Organization Details page

Looks great, thank you for creating the builder method.


Fix valueForKey:/valueForKeyPath: returns incorrect results for List properties

Fixes https://github.com/realm/realm-cocoa/issues/4251
Modified to create different accessors for each element in the List.
CC @tgoyne @bdash @jpsim

I forgot to report back that I couldn't get the fix while preserving the optimization. Actually, the current code on master works as-is on macOS in Debug mode, but not in release mode and never on iOS IIRC.

Creating a new accessor object for each value is needed if and only if the property we're getting the value of has a non-nil swiftIvar. This is because for those properties valueForKey: simply returns  an object with a reference to the parent object, while valueForKey: on other properties returns a new object which contains the value directly.
I'd be inclined to split these two cases into different loops (like how the self case is already a different loop). Note that in the accessor-reuse version calling RLMInitializeSwiftAccessorGenerics() is unnecessary, as the point of it is to initialize the properties which accessor reuse doesn't work for.

@tgoyne Thanks. I've updated this PR to split into two loops for Swift generic properties and for other properties. RealmOptional<T> properties seem to be able to use reused version. In that case, calling RLMInitializeSwiftAccessorGenerics() seems necessary. If it doesn't call it, valueForKey: for RealmOptional<T> properties returns nil.

Also, ideally there'd be tests for all sub-property types, not just Int.

This is failing on Xcode 8. I'm installing it locally to debug. I think I can carry this the last mile. Thanks @kishikawakatsumi!


Error: "[WARNING] Ignoring an unsupported file of type 0020000"

System Info:

Windows 10 Build 1903 (everything is up to date)
LxRunOffline v3.40 (installed via chocolatey)

Command that I ran:
LxRunOffline i -n ubuntu1604main -d "C:\ubuntu1604main" -f "C:\Users\HARRY\Downloads\Compressed\16.04.2-server-cloudimg-amd64-root.tar.gz" -s

Error log:
[WARNING] Ignoring an unsupported file "dev/midi01" of type 0020000.
[WARNING] Ignoring an unsupported file "dev/null" of type 0020000.
[WARNING] Ignoring an unsupported file "dev/tty7" of type 0020000.
[WARNING] Ignoring an unsupported file "dev/tty0" of type 0020000.
[WARNING] Ignoring an unsupported file "dev/loop3" of type 0060000.
[WARNING] Ignoring an unsupported file "dev/mixer" of type 0020000.
[WARNING] Ignoring an unsupported file "dev/rmidi3" of type 0020000.
[WARNING] Ignoring an unsupported file "dev/audioctl" of type 0020000.
[WARNING] Ignoring an unsupported file "dev/ram2" of type 0060000.
[WARNING] Ignoring an unsupported file "dev/tty6" of type 0020000.
[WARNING] Ignoring an unsupported file "dev/rmidi0" of type 0020000.
[WARNING] Ignoring an unsupported file "dev/loop6" of type 0060000.
[WARNING] Ignoring an unsupported file "dev/midi03" of type 0020000.
[WARNING] Ignoring an unsupported file "dev/ram6" of type 0060000.
[WARNING] Ignoring an unsupported file "dev/tty5" of type 0020000.
[WARNING] Ignoring an unsupported file "dev/midi2" of type 0020000.
[WARNING] Ignoring an unsupported file "dev/loop4" of type 0060000.
[WARNING] Ignoring an unsupported file "dev/agpgart" of type 0020000.
[WARNING] Ignoring an unsupported file "dev/random" of type 0020000.
[WARNING] Ignoring an unsupported file "dev/mpu401stat" of type 0020000.
[WARNING] Ignoring an unsupported file "dev/dsp" of type 0020000.
[WARNING] Ignoring an unsupported file "dev/kmem" of type 0020000.
[WARNING] Ignoring an unsupported file "dev/midi0" of type 0020000.
[WARNING] Ignoring an unsupported file "dev/loop1" of type 0060000.
[WARNING] Ignoring an unsupported file "dev/loop2" of type 0060000.
[WARNING] Ignoring an unsupported file "dev/ram5" of type 0060000.
[WARNING] Ignoring an unsupported file "dev/port" of type 0020000.
[WARNING] Ignoring an unsupported file "dev/mapper/control" of type 0020000.
[WARNING] Ignoring an unsupported file "dev/audio3" of type 0020000.
[WARNING] Ignoring an unsupported file "dev/ram14" of type 0060000.
[WARNING] Ignoring an unsupported file "dev/audio2" of type 0020000.
[WARNING] Ignoring an unsupported file "dev/ram0" of type 0060000.
[WARNING] Ignoring an unsupported file "dev/audio1" of type 0020000.
[WARNING] Ignoring an unsupported file "dev/sequencer" of type 0020000.
[WARNING] Ignoring an unsupported file "dev/dsp2" of type 0020000.
[WARNING] Ignoring an unsupported file "dev/tty4" of type 0020000.
[WARNING] Ignoring an unsupported file "dev/loop0" of type 0060000.
[WARNING] Ignoring an unsupported file "dev/tty9" of type 0020000.
[WARNING] Ignoring an unsupported file "dev/smpte1" of type 0020000.
[WARNING] Ignoring an unsupported file "dev/rmidi2" of type 0020000.
[WARNING] Ignoring an unsupported file "dev/tty" of type 0020000.
[WARNING] Ignoring an unsupported file "dev/ram8" of type 0060000.
[WARNING] Ignoring an unsupported file "dev/mixer1" of type 0020000.
[WARNING] Ignoring an unsupported file "dev/loop7" of type 0060000.
[WARNING] Ignoring an unsupported file "dev/midi1" of type 0020000.
[WARNING] Ignoring an unsupported file "dev/tty2" of type 0020000.
[WARNING] Ignoring an unsupported file "dev/tty8" of type 0020000.
[WARNING] Ignoring an unsupported file "dev/urandom" of type 0020000.
[WARNING] Ignoring an unsupported file "dev/ram11" of type 0060000.
[WARNING] Ignoring an unsupported file "dev/tty1" of type 0020000.
[WARNING] Ignoring an unsupported file "dev/rmidi1" of type 0020000.
[WARNING] Ignoring an unsupported file "dev/audio" of type 0020000.
[WARNING] Ignoring an unsupported file "dev/ram12" of type 0060000.
[WARNING] Ignoring an unsupported file "dev/mpu401data" of type 0020000.
[WARNING] Ignoring an unsupported file "dev/console" of type 0020000.
[WARNING] Ignoring an unsupported file "dev/mixer3" of type 0020000.
[WARNING] Ignoring an unsupported file "dev/smpte3" of type 0020000.
[WARNING] Ignoring an unsupported file "dev/ram3" of type 0060000.
[WARNING] Ignoring an unsupported file "dev/midi3" of type 0020000.
[WARNING] Ignoring an unsupported file "dev/ram13" of type 0060000.
[WARNING] Ignoring an unsupported file "dev/dsp3" of type 0020000.
[WARNING] Ignoring an unsupported file "dev/smpte2" of type 0020000.
[WARNING] Ignoring an unsupported file "dev/ram4" of type 0060000.
[WARNING] Ignoring an unsupported file "dev/mixer2" of type 0020000.
[WARNING] Ignoring an unsupported file "dev/ram1" of type 0060000.
[WARNING] Ignoring an unsupported file "dev/full" of type 0020000.
[WARNING] Ignoring an unsupported file "dev/ram7" of type 0060000.
[WARNING] Ignoring an unsupported file "dev/midi02" of type 0020000.
[WARNING] Ignoring an unsupported file "dev/mem" of type 0020000.
[WARNING] Ignoring an unsupported file "dev/sndstat" of type 0020000.
[WARNING] Ignoring an unsupported file "dev/midi00" of type 0020000.
[WARNING] Ignoring an unsupported file "dev/ram10" of type 0060000.
[WARNING] Ignoring an unsupported file "dev/smpte0" of type 0020000.
[WARNING] Ignoring an unsupported file "dev/tty3" of type 0020000.
[WARNING] Ignoring an unsupported file "dev/loop5" of type 0060000.
[WARNING] Ignoring an unsupported file "dev/ram15" of type 0060000.
[WARNING] Ignoring an unsupported file "dev/ram16" of type 0060000.
[WARNING] Ignoring an unsupported file "dev/zero" of type 0020000.
[WARNING] Ignoring an unsupported file "dev/ram9" of type 0060000.
[WARNING] Ignoring an unsupported file "dev/dsp1" of type 0020000.
[WARNING] Love this tool? Would you like to make a donation: https://github.com/DDoSolitary/LxRunOffline/blob/master/README.md#donation

It's not an error. The program has successfully run to completion. All of these output are warnings because the tar archive contains some device files that can't be properly extracted. There is no need to worry because necessary device files will be automatically created when you run the installed distro.

Ah. That's very good to hear. I was wondering the same. Even though I got a lot of warning, everything is working perfectly fine. Closing the ticket and thank you for quick reply. 😘

Is this true for all device files?
I moved Ubuntu 20.04 on Server 2019, v 1809 to another folder with 'LxRunOffline m'.
This error was given for /dev/console, /dev/full, /dev/mapper/control and /dev/ptmx, and none of these exist after the move.
I tried to hack a partial fix by creating a symlink /dev/console to /dev/tty, but that disappeared after a reboot.
There were some other devices giving the error too, including /dev/null and /dev/tty, but those came back as you said.

The device files alone are useless. On a real Linux system, these files are not stored on a disk but directly provided by the kernel. If you don't see these files in WSL, it's simply because WSL doesn't support them.

@lucvdv The device files alone are useless. On a real Linux system, these files are not stored on a disk but directly provided by the kernel. If you don't see these files in WSL, it's simply because WSL doesn't support them.

Yes, that's what I thought too, but then I was wondering why the files are present in a disk image.
Are you accessing them through WSL when you are copying, so I shouldn't regard the system as stopped?
Besides that, I found a WSL issue from 2018 about the missing /dev/full that was acknowledged as something they were already working on, so I thought that would have been fixed by now.

@lucvdv

Yes, that's what I thought too, but then I was wondering why the files are present in a disk image.

I don't know. These images are provided by distro maintainers rather than me.

so I thought that would have been fixed by now.

No, it's not fixed. However, you can use WSL2, which doesn't have this bug at all because it uses a real Linux kernel.

However, you can use WSL2
Thanks for taking the time to explain things.
WSL2 is (still, for the moment) not an option for another reason, I still need VMWare Workstation, and that's mutually exclusive with everything powered by HyperV.

@lucvdv

Yes, that's what I thought too, but then I was wondering why the files are present in a disk image.

I don't know. These images are provided by distro maintainers rather than me.

so I thought that would have been fixed by now.

No, it's not fixed. However, you can use WSL2, which doesn't have this bug at all because it uses a real Linux kernel.


When last to play, the bot announces the round before confirming your play

I was the last person to enter my play in a round, and the "Thanks. So this is your play for #channel" message came after the bot listed all the plays in the channel ("All plays are in. No more changes!").
This is a bit weird: ideally it would inform the user that their play was registered before listing the plays, not the other way around. Maybe it should even delay the final listing for a few seconds to allow the final player to quickly change their mind (something that all the other players are able to do).

It actually does send a message to the user before sending messages to the channel, but the message send queue is biased to send out channel messages first to reduce message delays that multiple people see.
Immediately ending the round on the last user's play is a separate thing.
It will be easier to fix the second thing than the first.
As you say, having a delay between the last person making their play and the round ending could be done. How much of a delay do you think is appropriate?

30-60 seconds perhaps?

It would seem reasonable to extend the turn clock out by 60 seconds after the last person has made their play, regardless…


ImzML recalibration

[x] Copy across current recalibration & alignment code
[x] Either try to improve & package MSIWarp for integration, or copy across the necessary parts
[ ] Save recal stats, sum spectrum, TIC image to DB as Diagnostic blobs
[ ] Add feature-flagged UI

This has been shelved as we found it didn't provide a compelling argument for adoption in its current state. (~15% of good-quality and ~100% of bad-quality datasets got worse results, overall improvement usually less than Raphaël La Rocca's implementation). We decided that it should be re-evaluated with METASPACE ML FDR (#797) once that's available, as the inclusion of mass error in the MSM score is likely to provide a clearer advantage.
My notes, if/when this gets picked up again:

The most important outstanding shortcoming is explainability. The end-to-end diagnostics in evaluation.py need to be re-tooled to plot mass errors (& stddevs) on a ppm scale, and track peaks through the pipeline by peak index instead of m/z so that a reliable before & after view can be shown.
Unanswered question: Is it possible to detect and abort if recalibration seems to worsen the results?
There's a bug that causes excessive memory usage somewhere - seems to be late in the pipeline, possibly while writing the ImzML file.
Several as-yet undocumented ideas for how to further improve the algorithm:

Find recalibration targets based on distinct spectra instead of sum spectra. The spectrum summation step is the most likely culprit for why many known peaks didn't work at all for recalibration in the spotting datasets.
Likely reason for underperformance compared to Raphaël's algorithm: that algorithm pre-filters outliers, so RANSAC has less work to do.


SubViewportContainer devouring click events

Tested versions

Godot v4.3.rc1

System information
Godot v4.3.rc1 - Windows 10.0.22631 - GLES3 (Compatibility) - NVIDIA GeForce RTX 2080 Ti (NVIDIA; <IP_ADDRESS>33) - 12th Gen Intel(R) Core(TM) i5-12400F (12 Threads)
Issue description
When the subviewports in the SubViewportContainer do not handle input events, I hope the input events can continue to propagate to other nodes in the node tree.
The current version of SubViewportContainer will consume all input events within the region
Steps to reproduce

When you click on the left half of button2, button2 cannot accept click events because the input event are consumed by SubViewportContainer1.
When you click on the right half of button2, the button can be clicked because this area is not within the range of SubViewportContainer1.
https://github.com/user-attachments/assets/b622a23c-3eff-4b49-8b23-036b12de9cd0
Minimal reproduction project (MRP)
subviewportcontainer.zip

Sounds like:

https://github.com/godotengine/godot/issues/93272

Thank you for your help, it is indeed because of this issue #93272
If the current behavior is expected, what can I do to achieve my goal? I hope that when events are not processed inside the SubViewportContainer, they will continue to pass through the node tree

Closing as a duplicate of that issue, see there for more details, specifically https://github.com/godotengine/godot/issues/55432


DeleteResource cannot be assigned using the  sigs.k8s.io/controller-runtime/pkg/client library. I think it should be changed to a pointer.

DeleteResource cannot be assigned using the  sigs.k8s.io/controller-runtime/pkg/client library. I think it should be changed to a pointer.

DeleteResource default is true,  When I want to change this value to false with golang, Does not take effect


Add some badges to the readme file

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
537

Relevant Lines:
611

💛  - Coveralls


DEV: Send message - Console error on create new chat

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Click on FAB icon and select send message option
Enter email with whom you don't have chat history
Click on that user

Expected Result:
It should not show any console error
Actual Result:
Console error appears (Cannot set properties of undefined (setting 'preferredSkinTone'))
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

Version Number: Dev v1.3.74-3
Reproducible in staging?: n
Reproducible in production?: n
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/93399543/a688b5e9-6b61-4ac8-b53f-1f30155973b9
https://github.com/Expensify/App/assets/93399543/5aa0bd0a-a62f-4592-996f-0afd386d6f8f
Expensify/Expensify Issue URL:
Issue reported by: @gadhiyamanan
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1695877161884539
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~012734407620ba58bb
Upwork Job ID:<PHONE_NUMBER>372219392
Last Price Increase: 2023-09-28

I can't reproduce this. is there any extra step?

https://github.com/Expensify/App/assets/57125237/af4b2e48-6e60-4957-9622-8d4e4f423414
Follow the steps to reproduce issue, but couldn't see the console error

this PR will solve this issue its awaiting a review.

Not reproducible anymore.


Bootstrap VM doesn't come up in OpenShift 4.2 vSphere Installation

Hi guys
I want to install okd 4.2 on vsphere 6.7 with OpenShift 4.2 vSphere Install Quickstart documentation. But bootstrap VM doesn't come up.
What is the reason?
Is there full and step by step installation document?
Thank you for your help

There is no OKD 4.2, which release payload and installer are you using?

There is no OKD 4.2, which release payload and installer are you using?

Thank you for reply.
I used OpenShift 4.2 vSphere Install Quickstart and openshift client and installation files

That is OCP 4.2, not okd 4.2. See https://docs.openshift.com/container-platform/4.2/support/getting-support.html


First draft working environments section

This turned out way to long, I think. Please provide feedback on (1) topics and content, (2) the level of detail, and (3) overall style. In the meantime, I will probably work on the documentation section. ;-)

CI fails because of https://github.com/tectonic-typesetting/tectonic/issues/38 (which means tectonic won't support minted).
We should move away from tectonic, then.

CI fails because of tectonic-typesetting/tectonic#38 (which means tectonic won't support minted).
We should move away from tectonic, then.

Thanks for looking this up... we should "reject" those last two commits then.

a4980ab fixes CI (but uses a relatively big docker image).

To simplify restructuring, we'll merge this for now. The suggestions by Martin will be implemented at a later point.


[Tabular][FastAI] Upgrade fastai v1 -> fastai2

Description of changes:
Re-write of NeuralNetFastAI from fast.ai v1 to v2
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Job PR-977-2 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-977/2/index.html

Looks good to me. You'll first run benchmark to check for accuracy/efficiency/memory degradation before merging?

Yes, this needs to be done before the merge.

Job PR-977-3 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-977/3/index.html

Job PR-977-5 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-977/5/index.html

Job PR-977-9 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-977/9/index.html

@gradientsky Any updates on benchmarking/merging this?
Taesup is hoping to adapt the fastAI net for our quantile-regression task, since his existing NN-quantile code is also in pytorch.

re benchmarking, I'm still waiting for automlbenchmark to merge my PR to enable our team to easily benchmark AG: https://github.com/openml/automlbenchmark/pull/237

Job PR-977-11 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-977/11/index.html

Job PR-977-12 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-977/12/index.html

Job PR-977-13 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-977/13/index.html

Job PR-977-15 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-977/15/index.html

Job PR-977-16 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-977/16/index.html


Handle void object case

This adds void to the list of { prefix tokens that imply block statement braces.
Fixes https://github.com/guybedford/cjs-module-lexer/issues/22.
Again, these are academic edge cases, and don't affect real world code.

Sorry, I think I wasn't clear in the issue :sweat_smile:
The bug is the other way around: the regexp isn't correctly handled in the case without void.
I think that the problem is that a { at the beginning of the file is not handled like other blocks (i.e. if I prefix it with if (foo) it works)

Ah thanks for clarifying. If it's specifically to do with the start of the source it sounds like it might be a start check? Do you have an approach in mind here?


Contacts Delegation

Hi Nate,
It appears that Google changed the way contacts work, they now need to be delegated separately in a similar manner to Mailboxes.  I have several shared mailboxes and would like to enable the Users to have a central contacts list for each of them.
Describe the solution you'd like
Implement Add-GSContactsDelegate / Remove-GSContactsDelegate etc
Your module is putting in good work for me thanks for the effort.
Cheers,
Neil

Hey Neil @n-searle - Checking it out once I have a moment, thanks for sending over the great idea!

Hey @n-searle - While it's definitely doable through the UI, I'm not finding any information yet on doing this via API specifically. Have you seen any documentation around the API's for this, by chance?

Neither the soon-to-be-deprecated Contacts API nor the newer People API appear to support Contact Delegation.

Hey,
No I hadn't seen anything, I was hoping I you would be able to magic it up :)
I'll keep my eye out and if I see anything I'll let you know.
Cheers for checking it out.


WIP: Configure Travis to release on tags

Note: this is WIP because it does not have a valid token for RubyGems.
The idea here is that if we can configure TravisCI to release this gem, then the friction of releasing new versions is reduced and our lives are made easier. I followed the guide here:
https://docs.travis-ci.com/user/deployment/rubygems/
And even pasted in my API key but then replaced it with what you see here in order to avoid pwning myself. 😝
So, before merging this I either need to be added to RubyGems so that my token will work, or we'd need @atwam to get his token encrypted and added here. Either would work although I'd be happy to be added so that I could help admin the gem too.

Woot, thank you so much!! 🙌


ERR_STREAM_DESTROYED when trying to run command idris.addClause

System

(Click to expand)
$ uname -a
Linux a 5.10.25_1 #1 SMP<PHONE_NUMBER> x86_64 GNU/Linux
$ code-oss --version
Warning: 'app' is not in the list of known options, but still passed to Electron/Chromium.
1.54.3
Unknown commit
x64
$ code-oss --list-extensions --show-versions | rg idris
Warning: 'app' is not in the list of known options, but still passed to Electron/Chromium.
<EMAIL_ADDRESS>$ idris2 --version
Idris 2, version 0.3.0
$ which idris2
/home/a/.idris2/bin/idris2
$ cat "/home/a/.config/Code - OSS/User/settings.json" | rg idris
	"idris.idrisPath": "/home/a/.idris2/bin/idris2",
	"idris.idris2Mode": true,

Reproduction

(Click to expand)

In a terminal, run:

mkdir -p ~/tmp
printf 'foo : Bool -> Bool' > ~/tmp/Main.idr
code-oss ~/tmp/Main.idr

In the editor, navigate cursor to foo.
Input Ctrl-e.
Input >idris.addClause.

Expected behaviour

(Click to expand)

Buffer now contains something similar to:

foo : Bool -> Bool
foo x = ?foo_rhs

Log (Extension Host) has no errors related to this extension.

Actual behaviour

(Click to expand)

Buffer still only contains:

foo : Bool -> Bool

Log (Extension Host) contains:

[2021-03-21 20:54:03.174] [exthost] [error] Error [ERR_STREAM_DESTROYED]: Cannot call write after a stream was destroyed
	at doWrite (_stream_writable.js:431:19)
	at writeOrBuffer (_stream_writable.js:419:5)
	at Socket.Writable.write (_stream_writable.js:309:11)
	at /home/a/.vscode-oss/extensions/meraymond.idris-vscode-0.0.8/node_modules/idris-ide-client/build/client.js:71:24
	at new Promise (<anonymous>)
	at IdrisClient.makeReq (/home/a/.vscode-oss/extensions/meraymond.idris-vscode-0.0.8/node_modules/idris-ide-client/build/client.js:69:16)
	at IdrisClient.loadFile (/home/a/.vscode-oss/extensions/meraymond.idris-vscode-0.0.8/node_modules/idris-ide-client/build/client.js:229:21)
	at /home/a/.vscode-oss/extensions/meraymond.idris-vscode-0.0.8/out/commands.js:279:36
	at Generator.next (<anonymous>)
	at /home/a/.vscode-oss/extensions/meraymond.idris-vscode-0.0.8/out/commands.js:8:71
	at new Promise (<anonymous>)
	at __awaiter (/home/a/.vscode-oss/extensions/meraymond.idris-vscode-0.0.8/out/commands.js:4:12)
	at Object.exports.loadFile (/home/a/.vscode-oss/extensions/meraymond.idris-vscode-0.0.8/out/commands.js:275:42)
	at /home/a/.vscode-oss/extensions/meraymond.idris-vscode-0.0.8/out/commands.js:55:25
	at Generator.next (<anonymous>)
	at fulfilled (/home/a/.vscode-oss/extensions/meraymond.idris-vscode-0.0.8/out/commands.js:5:58)
	at processTicksAndRejections (internal/process/task_queues.js:94:5) idris.addClause

Miscellaneous

(Click to expand)

The :ac Idris 2 command seems to work fine:

$ idris2 --client ':ac 1 foo' ~/tmp/Main.idr
foo x = ?foo_rhs

Thank you for the very detailed bug report :+1:
It looks like the idris2 process has either crashed, or not started correctly. I don't see anything wrong in your config though. I haven't been able to replicate this. I'm on an older version of vscodium, tomorrow I'll try with 1.54.3 — maybe something's changed.
When you start the extension are there any error popups? I'm assuming none of the other commands work either?

When you start the extension are there any error popups?

I'm not sure what you mean by "start the extension". I thought that it's automatically started when the editor starts, as long as it's enabled, or have I maybe been missing a step to activate it? In any case, no error popups appear when I start the editor.

I'm assuming none of the other commands work either?

Aside from idris.addClause, the only other command I've tried is idris.caseSplit when the cursor is on the x in the following buffer contents:
foo : Bool -> Bool
foo x = ?foo_rhs

which also doesn't work and results in the following error in Log (Extension Host):
[2021-03-22 23:54:19.693] [exthost] [error] Error [ERR_STREAM_DESTROYED]: Cannot call write after a stream was destroyed
	at doWrite (_stream_writable.js:431:19)
	at writeOrBuffer (_stream_writable.js:419:5)
	at Socket.Writable.write (_stream_writable.js:309:11)
	at /home/a/.vscode-oss/extensions/meraymond.idris-vscode-0.0.8/node_modules/idris-ide-client/build/client.js:71:24
	at new Promise (<anonymous>)
	at IdrisClient.makeReq (/home/a/.vscode-oss/extensions/meraymond.idris-vscode-0.0.8/node_modules/idris-ide-client/build/client.js:69:16)
	at IdrisClient.loadFile (/home/a/.vscode-oss/extensions/meraymond.idris-vscode-0.0.8/node_modules/idris-ide-client/build/client.js:229:21)
	at /home/a/.vscode-oss/extensions/meraymond.idris-vscode-0.0.8/out/commands.js:279:36
	at Generator.next (<anonymous>)
	at /home/a/.vscode-oss/extensions/meraymond.idris-vscode-0.0.8/out/commands.js:8:71
	at new Promise (<anonymous>)
	at __awaiter (/home/a/.vscode-oss/extensions/meraymond.idris-vscode-0.0.8/out/commands.js:4:12)
	at Object.exports.loadFile (/home/a/.vscode-oss/extensions/meraymond.idris-vscode-0.0.8/out/commands.js:275:42)
	at /home/a/.vscode-oss/extensions/meraymond.idris-vscode-0.0.8/out/commands.js:55:25
	at Generator.next (<anonymous>)
	at fulfilled (/home/a/.vscode-oss/extensions/meraymond.idris-vscode-0.0.8/out/commands.js:5:58)
	at runMicrotasks (<anonymous>)
	at processTicksAndRejections (internal/process/task_queues.js:94:5) idris.caseSplit

Should I test the other commands as well?
Not sure if this is pertinent, but in my system (Bedrock Linux) I think the Code editor uses glibc but Idris 2 uses musl. That said, Idris 2 seems to run fine in the editor's built-in terminal. Maybe I should try to rebuild the Idris 2 binary using glibc?

Not sure if this is pertinent, but in my system (Bedrock Linux) I think the Code editor uses glibc whereas Idris 2 might be using musl (IIRC the Chez Scheme I bootstrapped it from was built with musl):

That's really interesting, and I have no idea why that would cause a problem but I can completely believe that it did. I'm curious, so I may try to reproduce that sometime.

Error: Illegal value for line

I think this one is going to be a bit easier. My guess is that you're on the last line of the editor, and you don't have VSCodium set to insert a final new line on save ("files.insertFinalNewline": true). Can you confirm that?
The extension is trying to insert the new clause on a line that doesn't exist, and apparently it won't automatically extend the document. I've never run into this, because the extension saves before running commands, and mine is set to insert a final newline, so it's never tried to insert into a non-existent next line.

Can you confirm that?

Yes, that was the case. I've since added that entry and added a new line to the buffer contents. After doing that, the commands I've tried have worked as expected. Thanks for help troubleshooting this!

I've pushed a fix for the insert bug, and it's in the latest version that I just released.

but the extension will only work when I am using Chez Scheme built with the same libc as the editor.

Is your Idris2 binary dynamically linked?

Thanks, the fix seems to work well.

Is your Idris2 binary dynamically linked?

I don't actually seem to have an Idris 2 binary, but a script instead:
$ ldd `which idris2`
ldd: /home/a/.idris2/bin/idris2: Not a valid dynamic program
$ cat `which idris2`
#!/bin/sh

case `uname -s` in
    OpenBSD|FreeBSD|NetBSD)
        DIR="`grealpath $0`"
        ;;

    *)
        DIR="`realpath $0`"
        ;;
esac

export LD_LIBRARY_PATH="`dirname "$DIR"`/"idris2_app":$LD_LIBRARY_PATH"
"`dirname "$DIR"`"/"idris2_app/idris2.so" "$@"
$ ldd `dirname $(which idris2)`/idris2_app/idris2.so
ldd: /home/a/.idris2/bin/idris2_app/idris2.so: Not a valid dynamic program

Is your setup not like that?

No, I'm compiling it using Nix and I end up with a static binary.


Is it possible to drag and drop rows across multiple tables?

Hello,
I wanted to know if it is possible to drag rows across multiple tables and the data is maintained across them. Basically what I want to do is the ability to manually sort table rows across multiple stacked tables.
Basically the same functionality as what https://jqueryui.com/sortable/#connect-lists Jquery Sortable using connect list does.
If this feature is possible, then I'll be using this for sure. Fingers crossed.

I haven't tested it in a scenario like this. It would be a very good example to add to the component (PR welcome). It is possible you may need to rewrite some of the dragging related logic, but most of the code should just work I think.


updated garmin-basecamp (4.6.3)

Thank you for the contribution. It was merged directly as 198258285e272b93b561d9d98a59c034b7fe9faf to keep commit history cleaner. Your contribution is still credited to you.


Auto-Load Namespaces.

I find myself loading a few namespaces always. Is there a way to specify(maybe through scripting) a list of namespaces to auto load.

I'm using a simple script to achieve this.
using UnityEngine;
using uREPL;

public class ReplPreload : MonoBehaviour
{
    public string[] Commands;

    void Start()
    {
        foreach (var command in Commands)
        {
            Evaluator.Evaluate(command);
        }
    }
}

Sorry for my late work..., but I've added Pre-Load Command text area to uREPL.Main component from v0.6.0. The code written here is run just after starting scene like @Kabie wrote above.
https://github.com/hecomi/uREPL/releases/tag/v0.6.0
Please write here namespaces which you want to use like below:
using UnityEngine.UI;
using UnityEngine.XR;


Improved translation quality for Simplified Chinese

Pull Request Checklist

[x] Description: Briefly describe the changes in this pull request.
[ ] Changelog: Ensure a changelog entry following the format of Keep a Changelog is added at the bottom of the PR description.
[ ] Documentation: Have you updated relevant documentation?
[ ] Dependencies: Are there any new dependencies? Have you updated the dependency versions in the documentation?

Description
Improved translation quality for Simplified Chinese

Changelog Entry
Improved and added some simplified Chinese translations
Added
None
Fixed
None
Changed
src/lib/i18n/locales/zh-CN/translation.json
Removed
None

Thanks!


Update deps

Coverage remained the same at 98.561% when pulling 3d6a049a64cee5a123f5991afefb2df69ce1b9af on update-deps-2 into 4c67284b306113f47deffa31c266105f934e3204 on master.


Use something other than Antlr

It has been suggested that the dependency on Antlr is off-putting due to the possible Java/IKVM dependency (note that the NuGet package doesn't have a Java/IKVM dependency, just the development project has that dependency).  I don't have plans on switching currently, though if there is enough interest in doing so that is certainly an option.
Possible replacements:

https://github.com/sprache/Sprache

Hi Joe,
I was tempted to go with ANTLR with our version of this but I just don't think it was a good fit. The JS reference version of GraphQL will continually get updated with any fixes so I went the route of porting their parser. My thinking was it would be easier for people to read that and translate it into C# fixes in a parser so we've have more eyes on it.
You've done such a great amount of work on this I'm happy to bring my code to the table and add it to this project and put our heads together as you said on twitter ;)
I'll create a fork and see about getting my stuff added. Not got too much but the parser is about 40% done I think. If I focus on that bit we could swap it out for Antlr once its up and running assuming you are happy with it.
Cheers
Pete

Hey Pete, thanks for offering to help!
My thinking with going with ANTLR was so that I could get something working fairly quickly, and overall I think they do a good job at solving the lexer/parser problem.
I think going with a custom solution would be fine, though from experience that can be hard to get right.  As you said though, that could possibly elicit more help if it is all in .NET.
I'll add in some hooks to make it easier to swap out the Document builder.  That way you can run the existing tests to see if its working.

Added some interfaces to make it easier to replace existing classes.
Implement IDocumentBuilder which takes in the query data and returns a Document.
public interface IDocumentBuilder
{
    Document Build(string data);
}

public class MyCustomBuilder : IDocumentBuilder
{
    ...
}

You can then replace the builder in the Tests by making this change:
public class StarWarsBasicQueryTests
    : QueryTestBase<StarWarsSchema, MyCustomBuilder>
{
    ...
}

How about Facebook's C++ parser?  https://github.com/graphql/libgraphqlparser

It seems like using the C++ implementation would be mean a lot less work in the future.

For parser generator I'd take a look at Jetbrains' Nitra.

I ported facebook's javascript version to c#.  Any interest in including it?

Wow ;-) can you share a link? :dancer:

Worth a look for sure.

Here it is: https://github.com/zhech2/graphql-dotnet/commit/4f0c720569fe76f9c7175f269775819b113d9ebf.
It could still use work but at least you can review it.  So far, I've only written enough to get all tests passing.  Some of the code to convert from the parser's ASTs to the current format is not implemented.  This is because the current tests were not calling any of the methods and I didn't want to implement them until I write tests.
If this method were used, I was thinking that the original JS source could be saved or referenced in some manner, so that it could be compared against.  This would allow for updating the C# when the JS source is updated.

@zhech2 you could potentially use Paket's Github dependencies feature to reference the specific parser.js file in that repo at a point in time.  Then, any updates to that would show as an updateable dependency when 'paket update' is run.

Closed with the merging of #127


Unity + XCode + Flurry issue

Hi! I added your Flurry plugin in my Unity 4.6 project. It works fine on Android!
But on iOS IL2CPP, I got a compiler error on xcode 6.3.2.

Security.framework has been added properly.

Undefined symbols for architecture arm64:
"_mLogEvent", referenced from:
_FlurryAgent_mLogEvent_m475 in Bulk_Assembly-CSharp-firstpass_0.o
(maybe you meant: _FlurryAgent_mLogEvent_m475_MethodInfo, _FlurryAgent_mLogEvent_m475 )
"_mStopSession", referenced from:
_FlurryAgent_mStopSession_m476 in Bulk_Assembly-CSharp-firstpass_0.o
(maybe you meant: _FlurryAgent_mStopSession_m476, _FlurryAgent_mStopSession_m476_MethodInfo )
"_mStartSession", referenced from:
_FlurryAgent_mStartSession_m474 in Bulk_Assembly-CSharp-firstpass_0.o
(maybe you meant: _FlurryAgent_mStartSession_m474, _FlurryAgent_mStartSession_m474_MethodInfo )
ld: symbol(s) not found for architecture arm64
Can you help me? Thanks

I tried to rebuid using Mono + ARM7 architecture and I still have the same issue:
Ld /Users//Library/Developer/Xcode/DerivedData/Unity-iPhone-ddvcmtmcartznbfgcilptvxevqht/Build/Products/developer.app/developer normal armv7
cd /Users//Desktop/****/build
export IPHONEOS_DEPLOYMENT_TARGET=7.1
Undefined symbols for architecture armv7:
"_mStopSession", referenced from:
RegisterMonoModules() in RegisterMonoModules.o
"_mStartSession", referenced from:
RegisterMonoModules() in RegisterMonoModules.o
"_mLogEvent", referenced from:
RegisterMonoModules() in RegisterMonoModules.o
ld: symbol(s) not found for architecture armv7
clang: error: linker command failed with exit code 1 (use -v to see invocation)


Text field length validation work with international characters and emoji

Description
I started with this (great!) project, and created a simple country collection, that included a Flag emoji, and set maxLength: 1.  It failed :(

The solution to this is to not use the default string.length but instead: https://gomakethings.com/emoji-are-still-weird-but-modern-browser-methods-help/
I've added this to the validation code, along with additional tests.
To have the Intl function work I also had to upgrade typescript and the target, so if you want me to take another path with this just let me know!  For example,
I have added this dependency instead: https://github.com/flmnt/graphemer

[X] I have read and understand the CONTRIBUTING.md document in this repository

Type of change

[X] Bug fix (non-breaking change which fixes an issue)

Checklist:

[X] I have added tests that prove my fix is effective or that my feature works
[X] Existing test suite passes locally with my changes
[X] I have made corresponding changes to the documentation

I love the integration tests you added for min/max length. I'm a bit cautious that this is something we should handle though.
I reviewed the flmnt/graphemer package. It isn't a huge, but the main class is a 10k line class and that may be a bit too heavy of overhead for something to handle what seems like a very edge case.
https://github.com/flmnt/graphemer/blob/master/src/Graphemer.ts
We will discuss and decide, but this feels like something you need to handle in a custom validation on the fields that need it, within your own project or as a plugin instead of the core of Payload.
If we do decide to go forward with this, I'd definitly move the length setting inside an if block that only does this extra work if minLength or maxLength are being used. Here is where you're setting setting the length, which may not be used depending on the field config: https://github.com/payloadcms/payload/pull/1061/files#diff-e8686d63ee7a57e9238921baf4b95b80322b8df7d080f96d305fad65940678f8R31

Thanks for reviewing!  That is only the definition of the length function (perhaps it needs a clearer name?) - it doesn't get called unless there is a maxLength or minLength.
Of course no problem at all if you want to keep the core clean, and I can move it into a plugin. However, I would say that if you are building a CMS that you want to be used internationally in a professional context you do need to eventually consider these edge cases, and these days people put emoji in text fields more often than you think 😄

Hey @cliftonc — I agree with everything you're saying and we definitely need to figure out a way to get validation to more accurately reflect international characters and emojis.
We are up for that. The only thing here that I would like to see us get around is importing the new dependency graphemer. Because validation functions are used in the browser, this package's filesize directly contributes to the JS needed to download from the admin UI, and we are pretty strict about trying to keep that bundle as small as possible. Not to mention just in general we want to keep our dependencies to a minimum as Payload gets bigger. Do you have any other ideas regarding how to better validate text length (emoji-friendly) outside of using that package? Everything else looks great!

For some reason my brain skipped fact the validation was client side.
The easier path is to just use the browser Intl functions, which I did initially (if you look at the commit history) - but to get the tests to pass you have to upgrade typescript + bump the target - neither of which felt appropriate at the time.
Why don't you close this now as you guys likely have a lot to work on that is more important, and I will throw this into a plugin so folks that want it can opt in.
Thanks!

@cliftonc yeah, depending on how aggressively we have to bump the target, and what that means for non-evergreen browsers could influence our answer here. But honestly it is not a top concern of Payload to support older browsers. I would personally much rather advocate for making quicker use of newer browser features especially with the rise of evergreen browsers.
I'm not opposed to bumping TS and upping the target. I would hate to close this too. I think it's a valid PR. Maybe we can revisit this as a team at some point soon. Maybe there's a better package that we could use with a smaller filesize.

Who knew getting the correct character count would be so difficult?
I went down a lot of different paths only to hit dead ends with every option.

Use Intl.Segmenter like you have in f1e54b48e7f803cbd2583b3b05e701c8c89874fd: Not supported in Firefox.
Use Intl.Segmenter with a polyfill: no small polyfill package that I could find.
Use graphemer: I am particular concerned with this https://github.com/flmnt/graphemer/issues/7. I haven't benchmarked this, but I suspect long strings would have performance impacts.
Find a pure JS solution using regexs or other string functions: everything I see on StackOverflow seems to limited.
Find a different package: I can't find one that I would want to include due to size, lack of maintenance or other concerns.

I think we need to let this one pass for now and revisit again in the future—maybe Firefox will support the Segmenter API some day.
Thanks for the PR, I learned a lot on this topic!

I made a Unicode library that is much smaller and faster than graphemer. Check it out: https://github.com/cometkim/unicode-segmenter?tab=readme-ov-file#unicode-segmentergrapheme-vs
It ensures compliance with the latest Unicode data by performing tests and fuzzing against the Intl.Segmenter API.


Geowave 385

Coverage increased (+0.01%) to 62.61% when pulling 13409f6e8dfe286681882608f13fe7549da89bca on GEOWAVE-385 into 3785f058c65ac4a11035dc9673564212b53341df on master.

Coverage increased (+0.01%) to 62.61% when pulling 13409f6e8dfe286681882608f13fe7549da89bca on GEOWAVE-385 into 3785f058c65ac4a11035dc9673564212b53341df on master.

FYI.  Walked through this with Rich.  Had an extra 'compensation' logic for adapting different versions of feature data adapter stored images.  Took the adaptive component out by left the version byte in there for future use.
Just to recap:
CRS:84 does not have an SRID...so it fails in several unit tests.
urn:x-ogc:def:crs:EPSG:4326 forces long/lat, as does the current method of passing 'true' to the CRS.decode method with code=EPSG:4326.
EPSG:4326, in itself, cannot force lat/long.  It all depends on the authority within the system.  For us our purposes, this is ok.

Coverage increased (+0.03%) to 62.62% when pulling 5f5440ce01664dbf31aa3ed9d149adc5725babb0 on GEOWAVE-385 into 9745bb445ec5b31db6aaf54d4aa8ae3cb75d61e6 on master.


Can we test Quickstart Guide with minikube?

Hi
Recently I follow the Quickstart Guide with minikube.
I have finished Deploy the the operator. Everything looks fine.
NAMESPACE                        NAME                                              READY   STATUS    RESTARTS   AGE
confidential-containers-system   cc-operator-controller-manager-5df7584679-c5ttt   2/2     Running   0          79s

Then I try to Create the custom resource. I changed the ccruntime.yaml with the following:
ccNodeSelector:
    matchLabels:
             node-role.kubernetes.io/control-plane: ""
            # node-role.kubernetes.io/worker: ""

I did not get the corresponding pods running. Is there anything wrong?
NAMESPACE                        NAME                                              READY   STATUS    RESTARTS   AGE
confidential-containers-system   cc-operator-controller-manager-5df7584679-c5ttt   2/2     Running   0          79s

maybe because does not support kvm2 driver


Changed API for safe settings

Hello,
Mistral's API param safe_mode is changed. The new name is safe_prompt.
In your file chat.go simply rename the key name of requestData maps in MistralClient methods Chat and ChatStream, from safe_mode to safe_prompt.
Ciao

Thanks for this! Fixing now. I'm pushing on them to give me this info ahead of time so the client doesn't break

Completed

@gimaldi fixed in v0.1.3

I confirm that the problem is solved.
Thanks for your efforts.


minor release.yaml simplifcation

simplifies workflow logic by making the environment conditional
a test run that passes through
a test run that's waiting for approval

looks like it works, yeah (tested it on my fork)


JsonTagParser, EntityModels, Particles

The wiki page on particles might be helpful for contributer, commenters and reviewers.

Overall question: why are the particle names going to be different from their names that are used when creating them? Wouldn't it be easier to understand if they matched the /particle names?

Thinking of merging this and applying some changes myself. Any objections? :heart:

Nah, you're pretty much the POMF Architect now.


renamed LightningLoggerBase to Logger

fixes https://github.com/Lightning-AI/lightning-bolts/issues/983
Relevant issue in pytorch-lightning:
https://github.com/Lightning-AI/lightning/issues/11971
What does this PR do?
Renames LightningLoggerBase to Logger since this has been changed in PyTorch lightning package 1 year ago.
Fixes # (issue)
https://github.com/Lightning-AI/lightning-bolts/issues/983

duplicate of https://github.com/Lightning-AI/lightning-bolts/pull/973


feat: add padding to the vsi name

Description
Issue: https://github.ibm.com/GoldenEye/issues/issues/5815
Release required?

[ ] No release
[ ] Patch release (x.x.X)
[ ] Minor release (x.X.x)
[ ] Major release (X.x.x)

Release notes content

Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
/run pipeline

Checklist for reviewers

[ ] If relevant, a test for the change is included or updated with this PR.
[ ] If relevant, documentation for the change is included or updated with this PR.

Merge actions for mergers

When merging, use a relevant conventional commit message that is based on the PR contents and any release notes provided by the PR author. The commit message determines whether a new version of the module is needed, and if so, which semver increment to use (major, minor, or patch).
Merge by using "Squash and merge".

/run pipeline

/run pipeline

@ocofaigh , The name change is causing the terraform to destroy and recreate the vsi and the block volumes. While rename without destroy is possible from UI, cli or API https://cloud.ibm.com/docs/vpc?topic=vpc-managing-virtual-server-instances&interface=ui#rename-virtual-server-instances-ui . Any idea on how we manage this situation?

@Aashiq-J Can you check if its possible to rename using the api? If that works, we need to check provider code to see why it is trying to destroy and recreate. If it doesn't work with api, then we need to reach our to VPC VSI team to see what they recommend for renaming using automation

@Aashiq-J I wonder if there is something going on between the storage and the VSI. The VSI probably need recreating because the storage is recreated. If you run this locally, can you see what forces a new resource in the output?
Alternatively can we rename the storage (without updating the VSI)? Or can we rename the VSI without renaming the storage (which is the one step that the documentation says you can do in the UI)?
https://cloud.ibm.com/docs/vpc?topic=vpc-instance-storage-provisioning&interface=ui does not mention renaming, but https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/is_volume does not list a name change as forces new.
https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/is_volume boot_volume.volume_id is forces new, so this might trigger the VSI recreate IF there is a volume recreate (I am not sure if the module uses the volumes for boot volumes).

@ocofaigh , @shemau
I was able to change the name of the vsi and block storage using API and the UI.
curl -X PATCH "https://us-south.iaas.cloud.ibm.com/v1/instances/0717_b89cfc4e-ddd7-4618-b95d-90b08b0ac0de?version=2021-06-29&generation=2" -H "Authorization: $iam_token" -d '{"name": "my-instance"}'

curl -X PATCH "https://us-south.iaas.cloud.ibm.com/v1/volumes/r006-4f29babb-bf77-4414-9035-f0cdb231c546?version=2022-04-22&generation=2" -H "Authorization: $iam_token" -d '{
      "name": "my-volume-4-update"
    }'

There was no other effect on the VSI and the block storage attached to the VSI other than the updated name. In our case the ID remains the same, only the name of the VSI and storage changes.

@Aashiq-J ok thats good - so can we create a very basic example (using the ibm provider directly) where we can easily reproduce the rename causing destroy / recreate? Then we can create a provider issue for that.

terraform plan from this branch AFTER creating on main branch:
# module.slz_vsi.ibm_is_instance.vsi["slz-vsi-001"] will be created
  + resource "ibm_is_instance" "vsi" {
      + access_tags                       = (known after apply)
      + availability_policy_host_failure  = (known after apply)
      + bandwidth                         = (known after apply)
      + crn                               = (known after apply)
      + default_trusted_profile_auto_link = (known after apply)
      + disks                             = (known after apply)
      + force_action                      = false

So actually it is getting destroyed and recreated because the name in the map changes. This has nothing to do with the provider. Terraform sees it as a new different map entries.
This adds a whole new dimension. The point of the PR appears to be that the resources created have different names. Therefor can we keep the internal names module.slz_vsi.ibm_is_instance.vsi["slz-vsi-1"] as a reference to vsi.name: "slz-vsi-001"? Or is that just even more confusing?

@shemau Thanks for your input, keeping the map keys the same solved our issue. Now its updating the name of the instances and volumes without recreating.

/run pipeline

Looks good folks, nice work. @Aashiq-J please update the release notes section of the PR description and ensure we include info about the expected (non disruptive) rename

/run pipeline

@shemau Since Aashiq is out, would you be able to create the release notes for this update please? And I can look after getting them into a release

As expected, the upgrade test is failing with these identified updates:
Messages:   	Resource(s) identified to be updated Name: vsi Address: module.slz_vsi.module.fscloud_vsi.ibm_is_instance.vsi["slz-vsi-upg-mpqhal-1"] Actions: [update]
        	            	DIFF:
        	            	Before: {"name":"slz-vsi-upg-mpqhal-1"}
        	            	After: {"name":"slz-vsi-upg-mpqhal-001"}

Messages:   	Resource(s) identified to be updated Name: vsi Address: module.slz_vsi.module.fscloud_vsi.ibm_is_instance.vsi["slz-vsi-upg-mpqhal-2"] Actions: [update]
        	            	DIFF:
        	            	Before: {"name":"slz-vsi-upg-mpqhal-2"}
        	            	After: {"name":"slz-vsi-upg-mpqhal-002"}

Messages:   	Resource(s) identified to be updated Name: vsi Address: module.slz_vsi.module.fscloud_vsi.ibm_is_instance.vsi["slz-vsi-upg-mpqhal-3"] Actions: [update]
        	            	DIFF:
        	            	Before: {"name":"slz-vsi-upg-mpqhal-3"}
        	            	After: {"name":"slz-vsi-upg-mpqhal-003"}

Messages:   	Resource(s) identified to be updated Name: volume Address: module.slz_vsi.module.fscloud_vsi.ibm_is_volume.volume["slz-vsi-upg-mpqhal-3-slz-vsi-upg-mpqhal"] Actions: [update]
        	            	DIFF:
        	            	Before: {"name":"slz-vsi-upg-mpqhal-3-slz-vsi-upg-mpqhal"}
        	            	After: {"name":"slz-vsi-upg-mpqhal-003-slz-vsi-upg-mpqhal"}

Messages:   	Resource(s) identified to be updated Name: volume Address: module.slz_vsi.module.fscloud_vsi.ibm_is_volume.volume["slz-vsi-upg-mpqhal-1-slz-vsi-upg-mpqhal"] Actions: [update]
        	            	DIFF:
        	            	Before: {"name":"slz-vsi-upg-mpqhal-1-slz-vsi-upg-mpqhal"}
        	            	After: {"name":"slz-vsi-upg-mpqhal-001-slz-vsi-upg-mpqhal"}

Messages:   	Resource(s) identified to be updated Name: volume Address: module.slz_vsi.module.fscloud_vsi.ibm_is_volume.volume["slz-vsi-upg-mpqhal-2-slz-vsi-upg-mpqhal"] Actions: [update]
        	            	DIFF:
        	            	Before: {"name":"slz-vsi-upg-mpqhal-2-slz-vsi-upg-mpqhal"}
        	            	After: {"name":"slz-vsi-upg-mpqhal-002-slz-vsi-upg-mpqhal"}

As these are all expected, and non-disruptive, I will skip upgrade test.

/run pipeline

:tada: This PR is included in version 2.7.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket: