Get rid of unicode warnings

/usr/lib/python2.7/site-packages/doozerlib/cli/__main__.py:126: Warning:
Click detected the use of the unicode_literals __future__ import.  This
is heavily discouraged because it can introduce subtle bugs in your
code.  You should instead use explicit u"" literals for your unicode
strings.  For more information see
https://click.palletsprojects.com/python3/

It is controversial of the use unicode_literals. See discussions on Should I import unicode_literals?
From my opinion, if our goal is migrating to Python 3 and deprecating Python 2 eventually, then changing the signature of our functions and always using unicode is not much a problem and can probably help us discover issues earlier (since Python 2 doesn't distinguish byte and str, much code may never call encode/decode correspondingly).
Hence, I would be in favor of disabling the warning rather than following it.

@vfreex that was an attempt to solve sriov-network-operator build failures (error msg had to do with unicode) ... but Justin found out the root cause of that, therefore we can disregard this PR for now.

@thiagoalessio Alright. Anyway really appreciated your investigation.


[15.0] ISPN-16709 Static alias config

https://issues.redhat.com/browse/ISPN-16709
https://issues.redhat.com/browse/ISPN-16710
https://issues.redhat.com/browse/ISPN-14798

@karesti CI is green


Provide utilities

[ ] execute a command on a service. Must find the container
[ ] execute a command on each worker

Do we really need to execute a command on a service?


Deploy react-static as normal SPA

Hey guys,
I wonder if it's possible to deploy a react-static app as a SPA (pulling dynamic data in browser without actually building html) so I can host a "preview" app where contributors would be able to see how changes look before triggering a full website rebuild that can take quite some time depending on the website.
Don't know if that makes sense or if there is a better way to do this ?
Thanks !

Hey,
It is possible.
Have a look here: https://github.com/pauloamgomes/CockpitCMS-React-Static

Hey, thanks for your fast answer :)
This is an interesting example on how to achieve this ! However in this example the preview lives under a special page, which is something I cannot do as I have multiple page templates that are really different. I would also like to fetch my data instead of it being pushed from a postMessage event
I wonder if it would be possible to have my front end parse any url having the param preview=true and then rerender using preview data and not builtin data ? What would be great is being able to reload the getRoutes() from the browser. I see how I could test for the preview param and then trigger a manual fetch to get last data and update my page, but it would just be simpler if I could use what i've already written in my static.config...
Don't know if that makes sense ?

the answer is yes, but there are some things you wont be able to do. for example in static.config.js you have access to the full power of Node.js. however if you want to do that within the browser for your SPA you wont have this ability (unless you stick it in a serverless function or something...)
as an alternative, if you deploy thru netlify, every PR will get a deploy preview: https://www.netlify.com/blog/2016/07/20/introducing-deploy-previews-in-netlify/ that may help.

Thanks for your answer! That makes sense. I wonder if there would be a way to share route information between static.config.js and the browser ? Like having a seperate file specifying data dependencies for each route that I can then import in static.config.js for static rendering, and that I can also import directly in my dynamic preview component so I know what data to fetch for what template?

@simonunlikely So, I did something like this once but it's not a quick fix.
I had a file to contains data references and where to get them, e.g. posts come from 'api/posts' and such.
My static.config imports these and runs them during build, the usual stuff.
Now on to how I made it work, I wrap each page/template in a dynamic-data-hoc. If the hoc detects ?preview=true in the url, it will start fetching data.
To know what data I need, I look into the keys provided to the props of my template and see if any of them match data references, if so, fetch them and replace the old props with these props.
Your component then receives 'new' data instead of the static data, I did have to add a small loader to show that it was refetching the new data and such.
This way by far the 'easiest' way I could figure out how to preview pages without running your site as a separate SPA  on a preview server.

Hey @Pixelatex !
Thanks for your feedback on this. I ended up doing exactly that with a wordpress backend and it works pretty well :)
I'm closing this as it is no longer a problem for me, thanks all for your answers!


mypy plugin: init_typed=False does not work with pydantic.v1

Initial Checks

[X] I confirm that I'm using Pydantic V2

Description
I am using pydantic.v1.BaseModel  (which is in pydantic v2.. I hope I am reporting the bug at the right place).
And it looks like the init_typed=False setting of the mypy plugin does not work.
Example Code
No response
Python, Pydantic & OS Version
pydantic version: 2.6.4
        pydantic-core version: 2.16.3
          pydantic-core build: profile=release pgo=true
                 install path: /Users/alexandre.viau/git/flare/pyro/venv/lib/python3.11/site-packages/pydantic
               python version: 3.11.6 (main, Nov 28 2023, 10:03:48) [Clang 15.0.0 (clang-15<IP_ADDRESS>)]
                     platform: macOS-14.4-arm64-arm-64bit
             related packages: typing_extensions-4.10.0 mypy-1.7.0
                       commit: unknown

@dmontagu,
Could you please take a look?

Can you share your mypy config? You might need to add pydantic.v1.mypy to your list of mypy plugins instead of pydantic.mypy for v1 support.

My config was like so:
[mypy]
plugins = sqlalchemy.ext.mypy.plugin,
    pydantic.mypy

[pydantic-mypy]
init_forbid_extra = True
init_typed = True
warn_required_dynamic_aliases = True

So I confirm that I was not using pydantic.v1.mypy!.
Would it make sense to document it here? https://docs.pydantic.dev/latest/integrations/mypy/#enabling-the-plugin

@aviau,
If you add the pydantic.v1.mypy plugin, does everything work as expected? Yep, we can definitely add a note to the docs.

Yep, I confirm it works!

Now that I know that there are two mypy plugins, I think it would even make sense to have a config for v1 and a different config for v2. It would support use cases where people used init_typed=False in v1 and would like to migrate to v2 using init_typed=True, but maybe this is outside of this bug.
I am happy closing this bug with just the doc update!

@aviau,
Would you be willing to open a PR with the docs update?

@sydney-runkle Sorry I couldn't get to it before you. Thank you for your help! :)


doc: add npcheck review for March 19 review

Signed-off-by: Michael Dawson<EMAIL_ADDRESS>

I did it based on the last npcheck run that passed which is on March 19. We'll need to fix up audit for npcheck - see https://issues.redhat.com/browse/NODE-1707 for more details.


onSubscribed should allow async result

onSubscribed should allow returning a Uni if asynchronous actions need to happen during the subscription.

Fixed by #195.


How to export jsGrid Data in Excel or CSV file.

How to export jsGrid Data in Excel or CSV file.

The way I did it is to use something like alasql which allows json to excel export.   Then you need to use the data option on the jsgrid to get the json data.

@navar45000, thank you for the answer.
You can also checkout the following issue https://github.com/tabalinas/jsgrid/issues/59.
It also provides a few solutions.


Fixed a bug in utility function addPlugin (in the usePlugin)

Fixed a bug in utility function addPlugin, in the usePlugin (the plugin itself was passed to the function, instead of its name.)

Thanks for this!


How to run rkt image list or fetch as unprivileged?

In #1585, @jonboulle said:

Recent changes to rkt have allowed us to perform a large subset of rkt commands (image list, fetch, etc) as an unprivileged user.

However, when I try that it doesn't work:
inscrutable$ rkt image list
list: cannot open store: mkdir /var/lib/rkt/cas/imagelocks: permission denied
inscrutable$ sudo ls -ld /var/lib/rkt/cas
drwxrwx--- 9 root root 112 Apr  5 16:06 /var/lib/rkt/cas
inscrutable$ sudo ls -ld /var/lib/rkt/cas/imagelocks
drwxrwx--- 2 root root 4096 Apr 11 11:02 /var/lib/rkt/cas/imagelocks

This is with the official rkt-1.25.0 RPM.
With those permissions in the filesystem, I wouldn't expect it to work.  BTW I am in the rkt group, but not rkt-admin.
What am I missing?

I think you run rkt as root the first time, so the directories are not set-up with group permissions. Try to start from scratch and let the datadir be created by the rkt.conf tmpfile instead; it should come up with proper group ownership.

Yes, you're right, thanks.  We are using rktrunner, which invokes rkt run as root, so on a virgin system, the datadir is created with the wrong permissions.  (The fetch is done implicitly by rkt run.)
What I'm doing to fix this is running the following command immediately after installing the rkt package, before the first use of rktrunner (we use puppet, so this is easily automated):
 systemd-tmpfiles --create /usr/lib/tmpfiles.d/rkt.conf

So far, this seems to have fixed the problem.

Can this be closed then?

Ah yes, wasn't sure of the protocol for closing.  I can do that myself if that works best for you.
Thanks for your help.


[Docs] Add docs for mesheryctl system check command

Current State
mesheryctl system check is a command use to run system health checks for both pre and post deployment scenarios.
Desired State

Add documentation for this command in the Command Reference page and add individual page for this command.
Create a guide which walks through how a user can verify their environment readiness covering most common use-cases.

Contributor Guides and Resources

🛠 Meshery Build & Release Strategy
📚 Instructions for contributing to documentation

Meshery documentation site and source

🎨 Wireframes and designs for Meshery UI in Figma
🙋🏾🙋🏼 Questions: Layer5 Discussion Forum and Layer5 Community Slack

Can I  work on this issue? @navendu-pottekkat

Yes @ishitakeshawani
@piyushsingariya Could you share any resources on what tests are run for preflight as well as post-deployment checks?

Pre-deployment
1. docker healthchecks
2. kubernetes healthchecks
3. Kubernetes Version healthchecks
Post-deployment(also run the first 3 checks mentioned)
4. Meshery Version healthchecks
5. Meshery Adapter healthcheks

This guide should address possible reasons behind the failure of each of these checks and their possible solutions.
You can figure out the failing reasons by reading the code, some you must have faced while setting up meshery in your system, you can ask other folks to share the issues they faced while working with the respected component of which you're writing the failure reasons, rest I'll address when the PR will be up.

@ishitakeshawani You can check this above comment as well as test out the command before you write the docs.

@ishitakeshawani You can check this above comment as well as test out the command before you write the docs.

ok. I will do it.

@ishitakeshawani Are you working on this?
If not, @alphaX86 could you take this up quickly?

Let's wait for her reply within today. If she didn't work on this issue yet, I'll tie up loose ends today

@ishitakeshawani Are you working on this?
If not, @alphaX86 could you take this up quickly?

No, I am not working. I stuck with some work. Sorry, I forgot to mention this here.

Thanks for the update @ishitakeshawani

I'll tie up the issue


Small bramble nodes obstruct preview fog lights

What Happened?
It seems like shrinking bramble nodes can cause the internal geometry to get in the way of the actual light. This makes it so that the light can only be seen from specific angles. It's definitely the node geometry itself, as disabling the collider of the node causes the light to reappear.
What was supposed to happen?
The light should be viewable from most angles that see the internal fog, especially head-on
Platform
Steam
Mods
Just NH and my custom addon

Logs
No response

Can you provide an image

Nvm, anyway I can't figure out why this happens. It's totally FogLight.UpdateFogLight which does two raycasts, just not sure where that's going wrong. Gonna call this a vanilla bug and say the nodes ought to have had a better mesh (it happens to Vanilla nodes but it's less noticeable since they're so large).


Build rustc{Beta,Unstable} on Hydra?

Issue description
Right now it's still quite common to use rustUnstable.rustc for Rust development as many nice features (most notably procedural macros) are only enabled there at the moment.
Users have shown interest for binary-substitutes for rustc, and I can fully understand that you don't want to wait ~4 hours for a rustc build.
Is there a process or someone to ask if we can add these packages to the Hydra build? The builds take quite some time, so I'd rather not do it without discussing it first.

Thinking a bit more about this I don't think it's a good idea to have unstable (and even beta) in nixpkgs anyway. While beta is rarely used (as unstable features are disabled there which is the primary cause for not using stable) unstable is updated too frequently for us to keep track.
Better solutions for unstable exist (https://github.com/solson/rust-nightly-nix), so we should just get rid of beta and unstable.

good grief, please don't.

Building on nixpkgs is quickly descending into a nightmare. I thought it would be solid.

Like in your thinking, did you factor in the people that are using this at all? Like even a little?

Wow, is there any reason for being so hostile? I obviously didn't delete anything yet. I just want to start a discussion.
Keep in mind that our unstable was last updated in July. If you depend on such an old unstable version you might want to consider copying the expression for the compiler into your project.

Breaking public APIs is hostile, closing this issue with a unilateral "so we should just get rid of beta and unstable." is hostile. The whole point of nixpkgs going through hydra is binary distribution, saving Fractalide and Nixpkgs users 4~5 hours of compilation, most of the interesting features for complex projects like Fractalide are in rustUnstable. I've just contracted people to fix this very problem.

Ok, so it boils down if we should treat nixpkgs.git as a stable API. This surely isn't the right ticket to discuss this.
Also keep in mind that you can always pin your nixpkgs to a specific revision or a stable channel. These are guaranteed to have a stable api.

Look Kenny, I get that you don't have time to maintain this. I will take over the maintenance of Rust, I have financial incentives to keep this up and running and stable as possible.
There is a patch that is ready to fix this right now. Shall we say that myself and a few other people take over the maintenance of Rust on nixpkgs please?
We're doing a whole bunch right now from stripping out cargo in Fractalide to developing something called nixcrates which basically reads crates.io-index and writes nix expressions to a repo called nix-crates.io-index, thus allowing us to get rid of the cognitive dissonance that exists between cargo and nix, and allowing fractalide users to directly interact with rust programs using nix. There is a whole bunch of stuff going on and really it's becoming hard interacting with Rust on nixpkgs. It would be very helpful if you allowed us to take over please.

Feel free to submit a pull request updating beta and master and I'll merge it if it looks good. I wasn't aware of anyone relying on such an old version of rustcMaster. I'm sorry if I was mistaken.
That said, please refrain from guessing about my intentions or my personal timetable. If you have financial incentives that's fine. It still doesn't mean you can lecture me.

I'm getting ready to stabilize Fractalide at 1.0 very soon, part of the stabilization is fixing this issue. It's really not good having users say WTF I just waited 5 hours to compile Fractalide. Fractalide also has potential to being a very good source of new nix users and potentially new maintainers. Which will hopefully boost not only nixpkgs, but also hydra and nixops because all these tools are being used in Fractalide.

@the-kenny @vcunat @davidak
i've filed a bug-report but i'm not 100% sure if this is a nix related issue or rust related issue:
https://github.com/rust-lang/rust/issues/38026

I've seen this before. Please see the linked ticket for a description of
the problem and a possible fix.
Joachim Schiele<EMAIL_ADDRESS>writes:

@the-kenny @vcunat @davidak
i've filed a bug-report but i'm not 100% sure if this is a nix related issue or rust related issue:
https://github.com/rust-lang/rust/issues/38026
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/NixOS/nixpkgs/issues/18111#issuecomment-263131817

--


add a little "where am i map" in the corner, catmaid style

https://github.com/Norkart/Leaflet-MiniMap

Because of all the mods to leaflet, this is going to be a ton of work. Moving to later this year...


[AI Agent Idea] : Deep dive into History

Is your feature request related to a problem? Please describe.
A lot of time I have seen people forgetting our ancient Indian culture and the beautiful history of the past which led to amazing inventions and helped us to move forward.
Describe the solution you'd like
I want to create an AI agent to help people learn about Indian culture and history.
Describe alternatives you've considered
No, there's no alternatives as of now.
Additional context
Assign this issue to me.

Note to folks: Don't create a PR as I'm working on it


Remove Rackspace

This patch removes the Rackspace storage driver.

Codecov Report

Merging #535 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #535   +/-   ##
=======================================
  Coverage   28.52%   28.52%
=======================================
  Files          34       34
  Lines        1995     1995
=======================================
  Hits          569      569
  Misses       1365     1365
  Partials       61       61

Continue to review full report at Codecov.

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


How to set a custom value of the AceEditor Field?

I'm using the following code to make the AceEditor However its not rendering the value of the field.
$form->schema([
            Tabs::make("container")->tabs([
                Tab::make("name")->schema([
                    AceEditor::make("name")->hiddenLabel()
         ]),
     ])
]);

Below is the screenshot.

Laravel: 10x
riodwanto/filament-ace-editor: 1.0

Hi @touqeershafi
Your code is fine. Just make sure the name u define has value. u can add this formatStateUsing(fn ($state) => dd($state)) to dump value.


Extra Leeds PHR specific styles and images to a separate fork

Leeds PHR specific images that are contained under src/assets/images directory should be moved to LeedsCC fork
_leedsPHR.scss file that is contained under src/styles/themes directory should be moved to LeedsCC fork

move to LeedsCC repo?
Bogdan saying images are handled server side??
We need to ensure UI theme images are kept in client side repo, LeedsCC repo or another repo for theming images

@kbeloborodko @tony-shannon
I tried to solve this task by the method, which is described upper.
But it was impossible, because in this case Main and LeedsCC repositories will have different code.
Now these two repositories are different only by one theme constant.
If we want to remove image-files and style-files from Main, we must remove all importing of these files in React-code. In opposite case project can't be build. Because image-file or style-file for ReactJS - there are module for build.
We will have two projects with different code:

Main - without image-files and without images importing;
LeedsCC - with images and with their importing.

Now we located images at server. We don't import images - we get them by GET-request like
http://dev.ripple.foundation:8000/images/banners/allergies.jpg
In this case we can save equal code in Main and LeedsCC repositories.

@kbeloborodko  to lead and guide us on this

@tony-shannon
Hi, Tony!
We solved this problem by the follow way:

all non-core plugins and images were removed from the Core-repo;
created separate fork for LeedsCC-version;
added non-core plugins, which were necessary in Leeds;
added images to client side and inported them to React.

Changes were checked, testes and approved by Kirill.
Now this task is done.

tthanks @BogdanScherban
Can you explain what u mean by "added images to client side and inported them to React."

@tony-shannon
Sorry, I mean 'imported'.
We located images in client side and imported them as React-components (in LeedsCC-repo).
In Core-repo images are absent.

ok thanks Bogdan
what folder have u moved images to?
Thanks T

The same folder, which was earlier: /src/assets/images

ok thanks

ok to  close for now @kuvakina
Please set up a new issue for Helm PHR theme as Plugin as per discussion


Cannot verify contracts compiled with zksolc v1.3.18

🐛 Bug Report for hardaht-zksync plugins
💥 Plugin name
@matterlabs/hardhat-zksync-verify
📝 Description
Verifying contracts compiled with zksolc v1.3.18 fails.
🔄 Reproduction Steps

Set zksolc version to 1.3.18 (or in my case latest)
Compile and deploy contract
Attempt to verify with hardhat verify

🤔 Expected Behavior
Contract is verified.
😯 Current Behavior
Verification fails.
🖥 Environment
macOS, pnpm on node 20.6.1
📋 Additional Context
https://zksync2-mainnet-explorer.zksync.io/contract_verification/36653
📎 Log Output
Your verification ID is: 36653
Error in plugin @matterlabs/hardhat-zksync-verify: Backend verification error: Unknown zksolc version: v1.3.18

Seems like this issue regresses pretty much any time zksolc is updated, so the backend verification system is usually behind.
1.3.14:
https://github.com/matter-labs/hardhat-zksync/issues/427
1.3.17:
https://github.com/matter-labs/hardhat-zksync/issues/501

Yes, the issues are related. The backend system does not yet support zksolc v1.3.18 for verification.
The hotfix here is to put the version in your hardhat.config file to 1.3.17 as that's the highest supported version for now.

@kbortnik You can now verify contracts compiled with zksolc 1.3.18.
Closing the issue.


If statements don't work when put together as if else but work individually

Challenge Profile Lookup has an issue.
User Agent is: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/48.0.2564.97 Safari/537.36.
Please describe how to reproduce this issue, and include links to screenshots if possible.
My code:
//Setup
var contacts = [
    {
        "firstName": "Akira",
        "lastName": "Laine",
        "number": "0543236543",
        "likes": ["Pizza", "Coding", "Brownie Points"]
    },
    {
        "firstName": "Harry",
        "lastName": "Potter",
        "number": "0994372684",
        "likes": ["Hogwarts", "Magic", "Hagrid"]
    },
    {
        "firstName": "Sherlock",
        "lastName": "Holmes",
        "number": "0487345643",
        "likes": ["Intriguing Cases", "Violin"]
    },
    {
        "firstName": "Kristian",
        "lastName": "Vos",
        "number": "unknown",
        "likes": ["Javascript", "Gaming", "Foxes"]
    }
];

function lookUp(firstName, prop){
// Only change code below this line

for (i = 0; i < contacts.length; i++) {
  if (contacts[i].firstName === firstName && contacts[i].hasOwnProperty(prop)) {
    return contacts[i][prop];
  } else if (contacts[i].firstName !== firstName) {
    return "No such contact";
  } else if (contacts[i].prop !== prop) {
    return "No such property";
  }
}

// Only change code above
}

// Change these values to test your function
lookUp("Akira", "likes");

Each individual if statement works but they don't work together when using an if else statement.  Not sure why that is the case.

Your for loop doesn't check past the first contact object in the contacts array because your lookUp() function is returned before the loop goes to the next iteration.
For example, when looking for the contact with the firstName of "Kristian", your function checks the first contact to see if its firstName is equal to "Kristian" and then returns "No such contact" if it isn't before checking the other contacts.
If you need help on the challenges, please check out the Help Chat first as GitHub issues are mainly for reporting bugs. You'll likely get a faster response there.

Please use the help chat. Thanks!


Error when using swiftc to build a derivation

Describe the bug
I am trying to package the following repo via nix: https://github.com/biscuitehh/pam-watchid
This is my derivation definition (the patch is needed because Apple renamed the policies in macOS 15, thus I also added the darwin version hook):
{
  swift,
  fetchFromGitHub,
  stdenv,
  lib,
  darwinMinVersionHook,
}:
stdenv.mkDerivation {
  name = "pam-watchid";
  src = fetchFromGitHub {
    owner = "biscuitehh";
    repo = "pam-watchid";
    rev = "6061b86e96c766085718d4589c974184d86cf1d3";
    hash = "sha256-EJekXScC2Oay2ySb+xT1VusZ265WNh3JjezsbSBSEB4=";
  };
  buildInputs = [ (darwinMinVersionHook "15.0") ];
  nativeBuildInputs = [ swift ];
  patchPhase = ''
    runHook prePatch

    substituteInPlace watchid-pam-extension.swift \
      --replace-fail \
      'return .deviceOwnerAuthenticationWithBiometricsOrWatch' \
      'return .deviceOwnerAuthenticationWithBiometricsOrCompanion'

    runHook postPatch
  '';
  buildPhase = ''
    runHook preBuild

    swiftc watchid-pam-extension.swift \
      -o pam_watchid.so \
      -emit-library \
      -Ounchecked

    runHook postBuild
  '';
  installPhase = ''
    runHook preInstall

    mkdir -p $out/lib/pam
    cp pam_watchid.so $out/lib/pam

    runHook postInstall
  '';
  meta = with lib; {
    homepage = "https://github.com/biscuitehh/pam-watchid";
    description = "PAM plugin module that allows the Apple Watch to be used for authentication";
    license = licenses.unlicense;
    maintainers = with maintainers; [ mirkolenz ];
    platforms = platforms.darwin;
  };
}

Trying to build it leads to the following errors:
Running phase: unpackPhase
@nix { "action": "setPhase", "phase": "unpackPhase" }
unpacking source archive /nix/store/7sj5ag5mjpxijxq8vn22w5lagc5xi6c8-source
source root is source
Running phase: patchPhase
@nix { "action": "setPhase", "phase": "patchPhase" }
Running phase: configurePhase
@nix { "action": "setPhase", "phase": "configurePhase" }
no configure script, doing nothing
Running phase: buildPhase
@nix { "action": "setPhase", "phase": "buildPhase" }
error: compile command failed due to signal 8 (use -v to see invocation)
/nix/store/wgcbqi40ahn1ay6905v190x5mlv9xdq9-apple-sdk-13.3/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/LocalAuthentication.framework/Headers/LAContext.h:8:9: note: while building module 'Foundation' imported from /nix/store/wgcbqi40ahn1ay6905v190x5mlv9xdq9-apple-sdk-13.3/Platforms/M>
#import <Foundation/Foundation.h>
        ^
/nix/store/wgcbqi40ahn1ay6905v190x5mlv9xdq9-apple-sdk-13.3/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/Foundation.framework/Headers/NSURLError.h:15:9: note: while building module 'CoreServices' imported from /nix/store/wgcbqi40ahn1ay6905v190x5mlv9xdq9-apple-sdk-13.3/Platforms/MacOSX>
#import <CoreServices/CoreServices.h>
        ^
/nix/store/wgcbqi40ahn1ay6905v190x5mlv9xdq9-apple-sdk-13.3/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/CoreServices.framework/Frameworks/CarbonCore.framework/Headers/MachineExceptions.h:22:10: note: while building module '_Builtin_intrinsics' imported from /nix/store/wgcbqi40ahn1ay6>
#include <emmintrin.h>
         ^
<module-includes>:1:9: note: in file included from <module-includes>:1:
#import "immintrin.h"
        ^
/nix/store/d2jm2gdf5qmyfbqk579f7h65sbi497sr-clang-wrapper-16.0.6/resource-root/include/immintrin.h:31:10: note: in file included from /nix/store/d2jm2gdf5qmyfbqk579f7h65sbi497sr-clang-wrapper-16.0.6/resource-root/include/immintrin.h:31:
#include <emmintrin.h>
         ^
/nix/store/d2jm2gdf5qmyfbqk579f7h65sbi497sr-clang-wrapper-16.0.6/resource-root/include/emmintrin.h:43:9: error: _Float16 is not supported on this target
typedef _Float16 __v8hf __attribute__((__vector_size__(16), __aligned__(16)));
        ^
/nix/store/wgcbqi40ahn1ay6905v190x5mlv9xdq9-apple-sdk-13.3/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/LocalAuthentication.framework/Headers/LAContext.h:8:9: note: while building module 'Foundation' imported from /nix/store/wgcbqi40ahn1ay6905v190x5mlv9xdq9-apple-sdk-13.3/Platforms/M>
#import <Foundation/Foundation.h>
        ^
/nix/store/wgcbqi40ahn1ay6905v190x5mlv9xdq9-apple-sdk-13.3/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/Foundation.framework/Headers/NSURLError.h:15:9: note: while building module 'CoreServices' imported from /nix/store/wgcbqi40ahn1ay6905v190x5mlv9xdq9-apple-sdk-13.3/Platforms/MacOSX>
#import <CoreServices/CoreServices.h>
        ^
/nix/store/wgcbqi40ahn1ay6905v190x5mlv9xdq9-apple-sdk-13.3/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/CoreServices.framework/Frameworks/CarbonCore.framework/Headers/MachineExceptions.h:22:10: note: while building module '_Builtin_intrinsics' imported from /nix/store/wgcbqi40ahn1ay6>
#include <emmintrin.h>
         ^
<module-includes>:1:9: note: in file included from <module-includes>:1:
#import "immintrin.h"
        ^
/nix/store/d2jm2gdf5qmyfbqk579f7h65sbi497sr-clang-wrapper-16.0.6/resource-root/include/immintrin.h:31:10: note: in file included from /nix/store/d2jm2gdf5qmyfbqk579f7h65sbi497sr-clang-wrapper-16.0.6/resource-root/include/immintrin.h:31:
#include <emmintrin.h>
         ^
/nix/store/d2jm2gdf5qmyfbqk579f7h65sbi497sr-clang-wrapper-16.0.6/resource-root/include/emmintrin.h:44:9: error: _Float16 is not supported on this target
typedef _Float16 __m128h __attribute__((__vector_size__(16), __aligned__(16)));
        ^
/nix/store/wgcbqi40ahn1ay6905v190x5mlv9xdq9-apple-sdk-13.3/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/LocalAuthentication.framework/Headers/LAContext.h:8:9: note: while building module 'Foundation' imported from /nix/store/wgcbqi40ahn1ay6905v190x5mlv9xdq9-apple-sdk-13.3/Platforms/M>
#import <Foundation/Foundation.h>
        ^
/nix/store/wgcbqi40ahn1ay6905v190x5mlv9xdq9-apple-sdk-13.3/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/Foundation.framework/Headers/NSURLError.h:15:9: note: while building module 'CoreServices' imported from /nix/store/wgcbqi40ahn1ay6905v190x5mlv9xdq9-apple-sdk-13.3/Platforms/MacOSX>
#import <CoreServices/CoreServices.h>
        ^
/nix/store/wgcbqi40ahn1ay6905v190x5mlv9xdq9-apple-sdk-13.3/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/CoreServices.framework/Frameworks/CarbonCore.framework/Headers/MachineExceptions.h:22:10: note: while building module '_Builtin_intrinsics' imported from /nix/store/wgcbqi40ahn1ay6>
#include <emmintrin.h>
         ^
<module-includes>:1:9: note: in file included from <module-includes>:1:
#import "immintrin.h"
        ^
/nix/store/d2jm2gdf5qmyfbqk579f7h65sbi497sr-clang-wrapper-16.0.6/resource-root/include/immintrin.h:31:10: note: in file included from /nix/store/d2jm2gdf5qmyfbqk579f7h65sbi497sr-clang-wrapper-16.0.6/resource-root/include/immintrin.h:31:
#include <emmintrin.h>
         ^
/nix/store/d2jm2gdf5qmyfbqk579f7h65sbi497sr-clang-wrapper-16.0.6/resource-root/include/emmintrin.h:44:9: error: _Float16 is not supported on this target
typedef _Float16 __m128h __attribute__((__vector_size__(16), __aligned__(16)));
        ^
/nix/store/wgcbqi40ahn1ay6905v190x5mlv9xdq9-apple-sdk-13.3/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/LocalAuthentication.framework/Headers/LAContext.h:8:9: note: while building module 'Foundation' imported from /nix/store/wgcbqi40ahn1ay6905v190x5mlv9xdq9-apple-sdk-13.3/Platforms/M>
#import <Foundation/Foundation.h>
        ^
/nix/store/wgcbqi40ahn1ay6905v190x5mlv9xdq9-apple-sdk-13.3/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/Foundation.framework/Headers/NSURLError.h:15:9: note: while building module 'CoreServices' imported from /nix/store/wgcbqi40ahn1ay6905v190x5mlv9xdq9-apple-sdk-13.3/Platforms/MacOSX>
#import <CoreServices/CoreServices.h>
        ^
/nix/store/wgcbqi40ahn1ay6905v190x5mlv9xdq9-apple-sdk-13.3/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/CoreServices.framework/Frameworks/CarbonCore.framework/Headers/MachineExceptions.h:22:10: note: while building module '_Builtin_intrinsics' imported from /nix/store/wgcbqi40ahn1ay6>
#include <emmintrin.h>
         ^
<module-includes>:1:9: note: in file included from <module-includes>:1:
#import "immintrin.h"
        ^
/nix/store/d2jm2gdf5qmyfbqk579f7h65sbi497sr-clang-wrapper-16.0.6/resource-root/include/immintrin.h:31:10: note: in file included from /nix/store/d2jm2gdf5qmyfbqk579f7h65sbi497sr-clang-wrapper-16.0.6/resource-root/include/immintrin.h:31:
#include <emmintrin.h>
         ^
/nix/store/d2jm2gdf5qmyfbqk579f7h65sbi497sr-clang-wrapper-16.0.6/resource-root/include/emmintrin.h:45:9: error: _Float16 is not supported on this target
typedef _Float16 __m128h_u __attribute__((__vector_size__(16), __aligned__(1)));
        ^
/nix/store/wgcbqi40ahn1ay6905v190x5mlv9xdq9-apple-sdk-13.3/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/LocalAuthentication.framework/Headers/LAContext.h:8:9: note: while building module 'Foundation' imported from /nix/store/wgcbqi40ahn1ay6905v190x5mlv9xdq9-apple-sdk-13.3/Platforms/M>
#import <Foundation/Foundation.h>
        ^
/nix/store/wgcbqi40ahn1ay6905v190x5mlv9xdq9-apple-sdk-13.3/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/Foundation.framework/Headers/NSURLError.h:15:9: note: while building module 'CoreServices' imported from /nix/store/wgcbqi40ahn1ay6905v190x5mlv9xdq9-apple-sdk-13.3/Platforms/MacOSX>
#import <CoreServices/CoreServices.h>
        ^
/nix/store/wgcbqi40ahn1ay6905v190x5mlv9xdq9-apple-sdk-13.3/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/CoreServices.framework/Frameworks/CarbonCore.framework/Headers/MachineExceptions.h:22:10: note: while building module '_Builtin_intrinsics' imported from /nix/store/wgcbqi40ahn1ay6>
#include <emmintrin.h>
         ^
<module-includes>:1:9: note: in file included from <module-includes>:1:
#import "immintrin.h"
        ^
/nix/store/d2jm2gdf5qmyfbqk579f7h65sbi497sr-clang-wrapper-16.0.6/resource-root/include/immintrin.h:31:10: note: in file included from /nix/store/d2jm2gdf5qmyfbqk579f7h65sbi497sr-clang-wrapper-16.0.6/resource-root/include/immintrin.h:31:
#include <emmintrin.h>
         ^
/nix/store/d2jm2gdf5qmyfbqk579f7h65sbi497sr-clang-wrapper-16.0.6/resource-root/include/emmintrin.h:47:9: error: __bf16 is not supported on this target
typedef __bf16 __v8bf __attribute__((__vector_size__(16), __aligned__(16)));
        ^
Please submit a bug report (https://swift.org/contributing/#reporting-bugs) and include the crash backtrace.
Stack dump:
0.      /nix/store/d2jm2gdf5qmyfbqk579f7h65sbi497sr-clang-wrapper-16.0.6/resource-root/include/emmintrin.h:47:76: current parser token ';'
Stack dump without symbol names (ensure you have llvm-symbolizer in your PATH or set the environment var `LLVM_SYMBOLIZER_PATH` to point to it):
0  .swift-frontend-wrapped  0x0000000106d0b2bb llvm::sys::PrintStackTrace(llvm::raw_ostream&, int) + 59
1  .swift-frontend-wrapped  0x0000000106d0a1b7 llvm::sys::RunSignalHandlers() + 279
2  .swift-frontend-wrapped  0x0000000106d0b9cb SignalHandler(int) + 363
3  libsystem_platform.dylib 0x00007ff811929e9d _sigtramp + 29
4  libsystem_platform.dylib 0x00007fcc7601c310 _sigtramp +<PHONE_NUMBER>6415996048
5  .swift-frontend-wrapped  0x0000000105c0077e processTypeAttrs((anonymous namespace)::TypeProcessingState&, clang::QualType&, TypeAttrLocation, clang::ParsedAttributesView const&) + 5550
6  .swift-frontend-wrapped  0x0000000105bf8c17 GetFullTypeForDeclarator((anonymous namespace)::TypeProcessingState&, clang::QualType, clang::TypeSourceInfo*) + 22983
7  .swift-frontend-wrapped  0x0000000105beff6c clang::Sema::GetTypeForDeclarator(clang::Declarator&, clang::Scope*) + 716
8  .swift-frontend-wrapped  0x000000010558ea46 clang::Sema::HandleDeclarator(clang::Scope*, clang::Declarator&, llvm::MutableArrayRef<clang::TemplateParameterList*>) + 1190
9  .swift-frontend-wrapped  0x000000010558e53a clang::Sema::ActOnDeclarator(clang::Scope*, clang::Declarator&) + 26
10 .swift-frontend-wrapped  0x000000010512c8b4 clang::Parser::ParseDeclarationAfterDeclaratorAndAttributes(clang::Declarator&, clang::Parser::ParsedTemplateInfo const&, clang::Parser::ForRangeInit*) + 148
11 .swift-frontend-wrapped  0x000000010512a5b2 clang::Parser::ParseDeclGroup(clang::ParsingDeclSpec&, clang::DeclaratorContext, clang::SourceLocation*, clang::Parser::ForRangeInit*) + 882
12 .swift-frontend-wrapped  0x0000000105123ad6 clang::Parser::ParseSimpleDeclaration(clang::DeclaratorContext, clang::SourceLocation&, clang::ParsedAttributes&, bool, clang::Parser::ForRangeInit*, clang::SourceLocation*) + 758
13 .swift-frontend-wrapped  0x0000000105123402 clang::Parser::ParseDeclaration(clang::DeclaratorContext, clang::SourceLocation&, clang::ParsedAttributes&, clang::SourceLocation*) + 370
14 .swift-frontend-wrapped  0x00000001051e926b clang::Parser::ParseExternalDeclaration(clang::ParsedAttributes&, clang::ParsingDeclSpec*) + 203
15 .swift-frontend-wrapped  0x00000001051e7855 clang::Parser::ParseTopLevelDecl(clang::OpaquePtr<clang::DeclGroupRef>&, clang::Sema::ModuleImportState&) + 853
16 .swift-frontend-wrapped  0x000000010510dbde clang::ParseAST(clang::Sema&, bool, bool) + 798
17 .swift-frontend-wrapped  0x0000000104f159a8 clang::FrontendAction::Execute() + 104
18 .swift-frontend-wrapped  0x0000000104e8a7ac clang::CompilerInstance::ExecuteAction(clang::FrontendAction&) + 860
19 .swift-frontend-wrapped  0x0000000104e957d0 void llvm::function_ref<void ()>::callback_fn<compileModuleImpl(clang::CompilerInstance&, clang::SourceLocation, llvm::StringRef, clang::FrontendInputFile, llvm::StringRef, llvm::StringRef, llvm::function_ref<void (clang::CompilerInstance&)>, llvm::function_ref<void (cl>
20 .swift-frontend-wrapped  0x0000000106c47ab3 llvm::CrashRecoveryContext::RunSafely(llvm::function_ref<void ()>) + 227
21 .swift-frontend-wrapped  0x0000000106c47bf0 RunSafelyOnThread_Dispatch(void*) + 48
22 .swift-frontend-wrapped  0x0000000106c47d3f void* llvm::thread::ThreadProxy<std::__1::tuple<void (*)(void*), (anonymous namespace)::RunSafelyOnThreadInfo*> >(void*) + 15
23 libsystem_pthread.dylib  0x00007ff8118f5253 _pthread_start + 99
24 libsystem_pthread.dylib  0x00007ff8118f0bef thread_start + 15

Steps To Reproduce

Make sure to use the latest nixpkgs-unstable version that contains the updated apple-sdk pattern.
Save above derivation in a file called pam-watchid.nix
Run nix build --impure --expr "with import <nixpkgs> {}; callPackage overlays/package s/pam-watchid.nix {}"

Expected behavior
The derivation should build.
Notify maintainers
@emilazy
Metadata

system: "x86_64-darwin"
host os: Darwin 24.1.0, macOS 10.16
multi-user?: yes
sandbox: no
version: nix-env (Nix) 2.24.10
nixpkgs: /nix/store/rxn26bq4xm2p0x4whkp94afhy1g88cm7-source

Add a :+1: reaction to issues you find important.

Ah, I think you need swiftPackages.stdenv to build Swift code right now, for reasons. (Not sure whether those reasons will remain reasons after we make Swift good or not. Ideally I’d like them to get unreasoned because overriding stdenv is a pain.)

Thank you, that did the trick. The following builds as expected:
{
  lib,
  fetchFromGitHub,
  swift,
  swiftPackages,
}:
swiftPackages.stdenv.mkDerivation {
  name = "pam-watchid";
  src = fetchFromGitHub {
    owner = "biscuitehh";
    repo = "pam-watchid";
    rev = "6061b86e96c766085718d4589c974184d86cf1d3";
    hash = "sha256-EJekXScC2Oay2ySb+xT1VusZ265WNh3JjezsbSBSEB4=";
  };
  nativeBuildInputs = [ swift ];
  buildPhase = ''
    runHook preBuild

    swiftc watchid-pam-extension.swift \
      -o pam_watchid.so \
      -emit-library \
      -Ounchecked

    runHook postBuild
  '';
  installPhase = ''
    runHook preInstall

    mkdir -p $out/lib/pam
    cp pam_watchid.so $out/lib/pam

    runHook postInstall
  '';
  meta = with lib; {
    homepage = "https://github.com/biscuitehh/pam-watchid";
    description = "PAM plugin module that allows the Apple Watch to be used for authentication";
    license = licenses.unlicense;
    maintainers = with maintainers; [ mirkolenz ];
    platforms = platforms.darwin;
  };
}

Note that I needed to remove the patch since the new policy is not available in the default apple sdk. I tried overriding it as follows, but got basically the same error as in my original post. Is the latest apple sdk incompatible with the current swift version in nixpkgs?
{
  lib,
  fetchFromGitHub,
  swift,
  swiftPackages,
  apple-sdk_15,
}:
swiftPackages.stdenv.mkDerivation {
  name = "pam-watchid";
  src = fetchFromGitHub {
    owner = "biscuitehh";
    repo = "pam-watchid";
    rev = "6061b86e96c766085718d4589c974184d86cf1d3";
    hash = "sha256-EJekXScC2Oay2ySb+xT1VusZ265WNh3JjezsbSBSEB4=";
  };
  buildInputs = [ apple-sdk_15 ];
  nativeBuildInputs = [ swift ];
  patchPhase = ''
    runHook prePatch

    substituteInPlace watchid-pam-extension.swift \
      --replace-fail \
      'return .deviceOwnerAuthenticationWithBiometricsOrWatch' \
      'return .deviceOwnerAuthenticationWithBiometricsOrCompanion'

    runHook postPatch
  '';
  buildPhase = ''
    runHook preBuild

    swiftc watchid-pam-extension.swift \
      -o pam_watchid.so \
      -emit-library \
      -Ounchecked

    runHook postBuild
  '';
  installPhase = ''
    runHook preInstall

    mkdir -p $out/lib/pam
    cp pam_watchid.so $out/lib/pam

    runHook postInstall
  '';
  meta = with lib; {
    homepage = "https://github.com/biscuitehh/pam-watchid";
    description = "PAM plugin module that allows the Apple Watch to be used for authentication";
    license = licenses.unlicense;
    maintainers = with maintainers; [ mirkolenz ];
    platforms = platforms.darwin;
  };
}

I think that Swift has some sort of coupling to the SDK version yeah :( so we might need a newer Swift or something. Needs further investigation. Does apple-sdk_14 work?

Does apple-sdk_14 work?

Just tried it and it does not work. The error is different however, with v14 the compiler complains that it could not build the module LocalAuthentication.
Thanks again for your assistance, using the default SDK without the patch seems to work fine for now, so I'll go ahead and close the issue 😄

Yeah, I believe Swift should be giving you the macOS 13 SDK, so it’s not ancient at least.


Support CUDA11.0 on CD

Description
Enable CUDA 11.0 on CD nightly pipeline and release pipeline
Remove CUDA 9.2 and CUDA 10.0 from CD

@leezu @szha can you please review, thanks.

the base image nvidia/cuda:11.2-cudnn8-devel-ubuntu16.04 does not exist, so we probably need to try another image


Field names are lost in web client when object use MessagePack annotations

When decores the class with MessagePack annotations, i.e., [MessagePackObject] and [Key(n)], the response in Web Client arrives without field names.
Why do I have to use the annotations on the object? Because I need to transfer data to a Web Api, to then deliver the data by SignalR (I´m using WebAPIContrib.Core)
e.g.
public class Book
{
    public int Id { get; set; }
    public string Title { get; set; }
    public string Author { get; set; }
    public DateTime Date { get; set; }
    public double Price { get; set; }
}

After use annotations: [MessagePackObject] and [Key(n)] the object arrives from SignalR in another structure and without field names.
[MessagePackObject]
public class Book
{
    [Key(0)] public int Id { get; set; }
    [Key(1)] public string Title { get; set; }
    [Key(2)] public string Author { get; set; }
    [Key(3)] public DateTime Date { get; set; }
    [Key(4)] public double Price { get; set; }
}
// the web client receives:
[
  469,
  "In His Own Write",
  "John Lennon",
  "2018-10-20T07:23:02.124Z",
  223.54
]

The complete sample here:
https://github.com/harveytriana/MessgePackServerData
Any suggestions to not have to rewrite how to handle response from the client side?

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

ID: e807e138-f84c-e63e-ab37-eec0d554d3bb
Version Independent ID: 3ac41883-3bc2-30ba-a47f-462196850c12
Content: Use MessagePack Hub Protocol in SignalR for ASP.NET Core
Content Source: aspnetcore/signalr/messagepackhubprotocol.md
Product: aspnet-core
GitHub Login: @tdykstra
Microsoft Alias: tdykstra

https://github.com/neuecc/MessagePack-CSharp#object-serialization The messagepack library docs show examples of how to preserve property names. Key(#) just does position, whereas Key("string") will preserve the name.

The solution in one line, -elegant.
[MessagePackObject(keyAsPropertyName: true)]
public class Book
{
    public int Id { get; set; }
    public string Title { get; set; }
    public string Author { get; set; }
    public DateTime Date { get; set; }
    public double Price { get; set; }
}

Thanks a lot Brennan.


Gossip protocol not gossipping added DB server to RTS

Acton Version
v0.11.7
Steps to Reproduce

start db1: actondb -p 32000 -s <IP_ADDRESS>:32001
start RTS: examples/count --rts-ddb-host localhost

default replication is 3 so this will result in a non-working setup since we only have 1 server
ideally we should have code in place so RTS hangs until we see quorum, but currently that doens't happen so RTS does process some stuff

start db2: actondb -p 32002 -s <IP_ADDRESS>:32001

Expected Behavior
I expect RTS to be gossiped to from db1 that db2 has joined.
Actual Behavior
db1 and db2 gossip and agree on a view which both install but this is never communicated or never shows up in RTS.

Fixed in https://github.com/actonlang/acton/pull/968

Confirmed fix, nice! :)


Allow authenticating as a GitHub App

Add jwt and oauth_token parameters to:

abc.GitHubAPI._make_request
abc.GitHubAPI.get_item
abc.GitHubAPI.get_iter
abc.GitHubAPI.post
abc.GitHubAPI.patch
abc.GitHubAPI.put
abc.GitHubAPI.delete

Add jwt argument to sansio.create_headers
Raise ValueError if both jwt and oauth_token are passed in above methods
Update the documentation
Update the changelog

Closes https://github.com/brettcannon/gidgethub/issues/23

Ready for review now!

Seeing it written out I think I prefer the separate auth_token/jwt arguments like you have with create_headers. It eliminates the need for all the if/elif/else lines because you can just blindly pass auth_token and jwt blindly down the call stack and the name still makes it obvious what kind of authorization you're doing.
Or am I over looking something? I'm not worried about future flexibility if that's why you went with this initial design as I'm sure GitHub is going to push GraphQL more anyway so I think this might be the end of the line for major changes to their v3 API. 😄

Alright no prob :) I've changed the signature, and made oauth_token and jwt as keyword arguments to the other methods. ValueError is raised when both are passed.
I'll look forward to gidgethub v4: Add GraphQL support 😉

Just got back from vacation; I will try to review this week.
As for GraphQL support, I have some ideas on a generalized GraphQL client library for Python if you're at all curious.

😄 Thanks!!


Breaking out the parsing

I noticed the Schema execute will take in the graphql, parse it, run it, then build out the result all in one go.
https://github.com/graphql-crystal/graphql/blob/1ee630fb4b0c3982285ecc6bc43fc1df98be60d3/src/graphql/schema.cr#L79-L99
Is there already a way, or would you be open to having the parsing portion broken out in to a separate public method? I'm thinking something along the lines of:
# mutation Login($email: String!, $password: String!) {
#   login(email: $email, password: $password) {
#     email
#   }
# }
def parse(query : String) : GraphQL::Document
end

doc = schema.parse(query)

doc.operation_name #=> "Login"
doc.variables  #=> ["$email: String!", "$password: String!"]
doc.mutation? #=> true
doc.query? #=> false

Just a rough idea, but basically a way to ingest some GraphQL, and get back a usable object with what was passed in. Then from that point, the execute method could just take a document and run it.
schema.execute(doc, variables, operation_name, context)

What's the use case for this?

My experience with Lucky is limited so correct me if I'm wrong, but while you could theoretically map Lucky operations and queries to GraphQL, I don't think you'd actually want to do this.
GraphQL objects are comparable to classes, each field can resolve to a primitive property or a method and it's possible to nest them, whereas I'm assuming you're returning primitive JSON-style values in Lucky queries/operations. See this article. A simple query such as this has no equivalent in traditional REST APIs:
{
  book(id: 123) {
    author {
      books {
        title
      }
    }
}

The resolution hierarchy for this would usually look like this: Query::book -> Author::books -> Book::title; there are three classes involved rather than one.
What this library does is three things, it parses code to generate the schema/introspection data that is consumed by tools like GraphiQL, it generates resolver methods to take a query and turn it into the response, and it has a parser for the GraphQL language.
The first two aren't going to be of much use to you because they require the exact code structure laid out in the readme. You could take the parser and use it to write you own schema generator and resolver, but that's a lot of work only to end up with a constrained version of GraphQL.

Ah, I see. Thanks for the explanation! That makes things a lot more clear. It sounds like we may just have a really bad GraphQL setup with our app. None of us have ever used it before trying this new app, so it's super messy and clunky. I was hoping to find a nice pattern to clean it up and make it reusable, but I guess with how flexible GraphQL is, that's sort of the trade-off. You get more flexibility, but it's just a lot more difficult to setup 😅
I'll probably hold off on doing a Lucky integration until I can pair up with someone that knows both Lucky and GraphQL 😄 I appreciate the feedback!


Fixes for Update Modules feature

I am merging it now. If you have more feedback @vpodzime I'd be happy to address it on a follow-up PR :+1:


Problem with aNewRulesEngine

The following code gives me "Cannot resolve symbol 'RulesEngineBuilder.aNewRulesEngine' " as I have not imported org.jeasy.rules.core.RulesEngineBuilder. Any ideas why? I am using org.jeasy:easy-rules-core:3.0.0.
import org.jeasy.rules.api.RulesEngine;
import org.jeasy.rules.core.RulesEngineBuilder;

public class Main {

    public static void main(String[] args) {
        RulesEngine rulesEngine = new RulesEngineBuilder.aNewRulesEngine().build();
    }
}

Sorry, my bad. Should be RulesEngine rulesEngine = RulesEngineBuilder.aNewRulesEngine().build(); indeed.


如何复现实验结果以及替换自己的数据集呢？

@Spark-lens I have the scripts for reproducibility in the main (e0e0131) branch now.


chore: speedup docker build time

Motivation
Speedup docker builds
Description
Tweak current Docker build process to improve build speeds.
This is achieved by:

using regular node images for build layers; this remove the need to add extra tooling via apk every run
document how to use yarn offline mirror to reduce the need to download dependencies

Using regular node images comes at a higher download cost (image is bigger) but is cached. slim images do not ship with the necessary tooling.
Note that the current Docker build creates a multi-platform Docker image (arm64 and amd64). We can probably improve things further by having a dedicated Dockerfile for dev usage.
Results
Before
1st run: 5m 22s
Subsequent runs, after code change: 4m 52s
After
1st run: 3m 16s
Subsequent runs, after code change: 2m 32s

I added some experiment using a lodestar base builder image. This reduce the need to either use a big image or update via apk every build.
This image will have to be pushed to ChainSafe dockerhub beforehand.

Note that the current Docker build creates a multi-platform Docker image (arm64 and amd64). We can probably improve things further by having a dedicated Dockerfile for dev usage.

I don't think this is correct. By default docker will only create an image for the platform it's built on. To create multiarch images you need to pass --platform linux/amd64,linux/arm64 and requires an emulator like QEMU to be installed

@nflaig Yes that's what we are doing, see this. If we were not doing multi-platform build the Dockerfile could be simplified to have only a single build stage (w/o the FROM --platform).

@nflaig Yes that's what we are doing, see this. If we were not doing multi-platform build the Dockerfile could be simplified to have only a single build stage (w/o the FROM --platform).

ah you mean we could remove the middle stage in case we don't need to support arm64 images?

In a separate Dockerfile only used for local dev, yes

Doesn't appear to provide value.


[Feature Request] Connect UI to websocket

Problem description
Connection to websockets will provide more opportunities for rich visualization and quick updates. For example, authorized users may be able to view which tasks are currently running on certain nodes, and node status (online/offline) could be updated without calling the API
Desired solution

[x] connect UI to websocket.
[x] Only allow it in channels where user is authenticated to view events
[x] Update node status
[x] Show which tasks are running (vantage6/vantage6#167)

Additional tasks

[ ] Add permissions on the server to view nodes or tasks in a specific scope (collab, global)
[ ] Rewire socket design on the server so that we have one room for each collaboration, and a room for all nodes

Fixed by #84.
Note that this is not released yet (will be with v3.6) so leaving issue open for now.


Bug: unnecessary scroll

Describe the bug
There is an unnecessary scroll in the large screens on the contributor's page.

Steps to reproduce

go to the contributor page: https://insights.opensauced.pizza/user/a0m0rajab/contributions
Check the tabs area. You can see the scroll.

Suggested solution:
You can add overflow:hidden in the CSS.
Browsers
No response
Additional context (Is this in dev or production?)
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Contributing Docs

[ ] I agree to follow this project's Contribution Docs

hi @a0m0rajab , i have reproduced this , scroll is there
this class is responsible for the overflow,
.overflow-x-scroll
overflow: hidden would not be a suitable solution for this,
i think this class should be removed (.overflow-x-scroll ), and added dynamically in case there is a need for horizontal scroll if there are more tabs

Would you like to open a PR for this?
Sent from mobile device

From: hritik @.>
Sent: Sunday, July 2, 2023 7:41:36 PM
To: open-sauced/insights @.>
Cc: Abdurrahman Rajab @.>; Mention @.>
Subject: Re: [open-sauced/insights] Bug: unnecessary scroll (Issue #1325)
hi @a0m0rajabhttps://github.com/a0m0rajab , i have reproduced this , scroll is there
this class is responsible for the overflow,
.overflow-x-scroll
overflow: hidden would not be a suitable solution for this,
i think this class should be removed (.overflow-x-scroll ), and added dynamically in case there is a need for horizontal scroll if there are more tabs
[image]https://user-images.githubusercontent.com/26836794/250370592-45dd66e6-9bec-4f2e-8c1a-e02b97a82552.png
—
Reply to this email directly, view it on GitHubhttps://github.com/open-sauced/insights/issues/1325#issuecomment-1616727340, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AELNMKO74H2BLMXIJD7CLFLXOGQEBANCNFSM6AAAAAAZ2MDKVM.
You are receiving this because you were mentioned.Message ID: @.***>

Thank you for the PR.


upgrade to v6 for create room with supplied ID

Answered offline, but for posterity: just committed to mimir, and yeah let's merge all at the same time.


Missing standard includes on macOS runners

Description
I just started testing my project against the macOS runners and got a lot of missing includes from the MacOS SDKs. For example:
/Applications/Xcode_15.0.1.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX14.0.sdk/usr/include/c++/v1/cstddef:59:9: error: no member named 'nullptr_t' in the global namespace
using ::nullptr_t;
      ~~^
In file included from /Users/runner/work/volume-cartographer/volume-cartographer/build/_deps/smgl-src/smgl/src/Logging.cpp:1:
In file included from /Users/runner/work/volume-cartographer/volume-cartographer/build/_deps/smgl-src/smgl/include/smgl/Logging.hpp:3:
In file included from /Applications/Xcode_15.0.1.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX14.0.sdk/usr/include/c++/v1/ostream:168:
In file included from /Applications/Xcode_15.0.1.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX14.0.sdk/usr/include/c++/v1/__memory/shared_ptr.h:22:
In file included from /Applications/Xcode_15.0.1.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX14.0.sdk/usr/include/c++/v1/__memory/allocation_guard.h:14:
In file included from /Applications/Xcode_15.0.1.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX14.0.sdk/usr/include/c++/v1/__memory/allocator_traits.h:14:
In file included from /Applications/Xcode_15.0.1.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX14.0.sdk/usr/include/c++/v1/__memory/construct_at.h:23:
In file included from /Applications/Xcode_15.0.1.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX14.0.sdk/usr/include/c++/v1/new:96:
/Applications/Xcode_15.0.1.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX14.0.sdk/usr/include/c++/v1/cstdlib:90:5: error: <cstdlib> tried including <stdlib.h> but didn't find libc++'s <stdlib.h> header.           This usually means that your header search paths are not configured properly.           The header search paths should contain the C++ Standard Library headers before           any C Standard Library, and you are probably using compiler flags that make that           not be the case.
#   error <cstdlib> tried including <stdlib.h> but didn't find libc++'s <stdlib.h> header. \

This is very similar to an issue I had 4 years ago, so I know that this is some sort of Xcode/SDK configuration error. In this case, I solved my build problems by explicitly using the command line tools and not Xcode:
      - name: Use the Command Line Tools
        run: |
          sudo xcode-select -s /Library/Developer/CommandLineTools

I don't know if this is a regression in the macOS runner images or just a perpetual problem with Xcode, so I thought I'd at least record it here for posterity.
macos-13 job log [link]
macos-14 job log [link]
Platforms affected

[ ] Azure DevOps
[X] GitHub Actions - Standard Runners
[ ] GitHub Actions - Larger Runners

Runner images affected

[ ] Ubuntu 20.04
[ ] Ubuntu 22.04
[ ] Ubuntu 24.04
[ ] macOS 11
[ ] macOS 12
[X] macOS 13
[ ] macOS 13 Arm64
[ ] macOS 14
[X] macOS 14 Arm64
[ ] Windows Server 2019
[ ] Windows Server 2022

Image version and build link
macos-13 runner version: 2.317.0
macos-14 runner version: 2.317.0
Is it regression?
unknown
Expected behavior
Successful build.
Actual behavior
Build fails with errors pertaining to missing includes/unknown symbols from the C++ standard libraries.
Repro steps
My old test repository has a minimal example using ITK: https://github.com/csparker247/cpp-build-action

Hey @csparker247!
Thank you for bringing it to other users attention. Yes, such a problem exists. Depends on the version of XCode and the version of macOS on which it is installed, oddly enough. Unfortunately, this is behaviour that we cannot control and the only available solution is manual choose the SDK (or only some set of libraries in some cases) used on the users' side. In any case, during installation we download all available ones, including those that come with CommandLineTools. We would not like to install additional versions, since we will still never be able to provide a solution in this area that satisfies all users and it will be easier and faster to download or link them on the go.
Another example of such changes: https://github.com/actions/runner-images/issues/9976


Mention the Git Credential Manager Core (Beta) for dev.azure.com repositories?

Following the github page linked in this article to use brew to install git-credential-manager for MacOS did not work for dev.azure.com repos.
This worked- https://github.com/microsoft/Git-Credential-Manager-Core#download-and-install
Not sure if it is worth mentioning here for others.

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

ID: 6c2f260d-9321-d669-172d-01289c233263
Version Independent ID: 14e9ae18-df9d-7555-902c-3e8b4c2b2f22
Content: Connect to your Git repos using credential managers - Azure Repos
Content Source: docs/repos/git/set-up-credential-managers.md
Product: devops
Technology: devops-code-git
GitHub Login: @apawast
Microsoft Alias: sdanie

Seems reasonable.  I'll take a look.


How to use Swift version?

Hey there!
I think switching enum with guard case . for every object in json isn't the best way, am I right? Could you show me real world (production) examples of using this lib?

Hi!  Unfortunately I don't have access to any public code that uses the library, but maybe @aeidelson could sanitize and share some.
guard case sounds fine to me though - do you have a specific objection?  How else would you handle the case that the value is something you didn't expect?
If you're asking about overall structure, usually you write a series of functions from a JSON value to an Optional<SomeStruct> and compose them appropriately to decode the entire document.
Does that help?

Yea, so as a convenience we (privately) declared a number of helper getters to read fields of various expected types. For example, String is declared as:
extension sajson_swift.ValueReader {
    public var stringValue: String {
        if case .string(let v) = self {
            return v
        }
        return ""
    }

    public var string: String? {
        if case .string(let v) = self {
            return v
        }
        return nil
    }
}
...
let s = someValue.string

We haven't merged these back because many of them aren't super well thought out and are pretty specific to our situation (keeping backwards compatibility with the library we moved from). But I think it would be totally reasonable to extend similar getters in SaJSON as a convenience.

I'm happy to take that on if you want @chadaustin? And we could probably add some better documentation around how to use the API

@aeidelson If you'd like, feel free!  @own2pwn do you have any input into how you'd prefer decoder functions be written?

A while back I began on implementing a JSON Decoder that uses Swift4‘s ˋDecodableˋ protocol and internally uses Sajson. It’s not finished yet, but ultimately that’s the way to go I guess... you can check it out in my fork here: https://github.com/t089/sajson/blob/master/swift/sajsonTests/FastJSONDecoder_Tests.swift

Hey, I've implemented it like aeidelson have. But that leads to deal with optional values (because of Swift's dictionary subscript).
E.g.
let items = json.array
for item in items {
  let item = item.object // item's type is: [String: Value]
  let id = item["id"]?.stringValue // here we deal with String?
}

Using if case all fine if we talk about optionals but not for readability, IMO.
if case .array(let items) = json {
  var it = items.makeIterator()
  while let elem = it.next() {
    if case .object(let item) = elem {
      let id = item["id"].stringValue // because of overriding sajson's subscript, we get String -- that's nice
    }
  }
}

It would be very nice if one could use it swiftyJson way: like aeidelson suggestion with computed properties but one that returns optional and one that return parsed value or something default (string and stringValue).
Maybe there is a way to use ASTNode directly w/o enums?

Also, overriding sajson's subscript leads to dirty way of handling non existing keys in json: we should return malformed ASTNode or we throw preconditionFailure

Thought about it a bit: I like the idea of extending to have getters something like:
extension sajson_swift.Value {
    var string: String?
    func string(withDefault: String) -> String
    // and similar for Boolean, Arrays, etc.
}

Perhaps even getters that throw?
Anyone want to submit a PR?
I don't know anything about the new Decodable protocol, so if there's consensus around @t089's fork I'd be happy to merge that too.  :)

It‘s not in a mergeble(?!?) state yet. I’ll raise a PR once it is. Regardless,  more convenient accessors are a plus and complement the Decodable conformance nicely.

Am 04.10.2017 um 02:08 schrieb Chad Austin<EMAIL_ADDRESS>Thought about it a bit: I like the idea of extending to have getters something like:
extension sajson_swift.Value {
var string: String?
func string(withDefault: String) -> String
// and similar for Boolean, Arrays, etc.
}
Perhaps even getters that throw?
Anyone want to submit a PR?
I don't know anything about the new Decodable protocol, so if there's consensus around @t089's fork I'd be happy to merge that too. :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

@chadaustin wouldn't it be better to prefer optionals rather than throwing? If I recall correctly Apple recommends using throwing funcs when dealing with hardware or when we want to describe error in more detail.
I'm happy with idea of non-optional subscript that return default value if extract failed along with two getters for other types (optional getter and getter with default value)


Iron + Harmonic examples not responding.

Not sure what is going on but It seems that on harmonic, the examples are not working.
I've installed ros_gz_sim and gz_ros2_control from source from the iron branch as I'm on iron.
Running the example launch files for cart velocity and effort does seem to load properly without any errors and running the example binaries for the velocity and effort do publish command messages as expected but the cart model is unaffected in both cases.
In the case of the position control example, running the position example binary throws the following error:

ros2 run gz_ros2_control_demos example_position
node created
terminate called after throwing an instance of 'std::runtime_error'
what():  could not get action server
[ros2run]: Aborted

I can't find any documentation on how to debug this further. For example through what kind of interface does the controllers manipulate the joints and is it possible to see if the controllers actually receive the commands and try to do something with the commands.

As a note, I was adding the velocity controller to a model I'm working on and had the same issue there. One positive note is that the joint that I was adding the velocity controller seemed to stay in place and not drop down because of gravity after adding the velocity controller.
So something must be controlling the joint but It's just not getting new commands I suppose?

Seems that the controllers are not loaded properly in my environment for some reason.
After running the launch file, no controllers are loaded:
$ ros2 control list_hardware_interfaces
command interfaces
	slider_to_cart/effort [available] [unclaimed]
state interfaces
	slider_to_cart/effort
	slider_to_cart/position
	slider_to_cart/velocity

If I then manually load the controllers after running the launch command, then it works fine.

Just to clarify: You can run ros2 launch gz_ros2_control_demos cart_example_position.launch.py successfully? Are there any errors written in the log? What reports ros2 control list_controllers?
I tested this just now and works on iron.


SOCRATES: generate consistent spectral files

T range: 200–3000 K
Volatiles:

[H2]
[H2O]
[CO2]
[CO]
[N2]
[O2]
[(CH4?]
[(/He?)]

Both for the relevant G and M star spectra, see issue #5.
@mark-hammond @Ryan-Boukrouche  :-)

Done with the general HITRAN database, need to work on HITEMP and EXOMOL data next; this is going to be a new issue.


Maybe fix build on macos

@glguy please try this

@glguy please try this

I'll give this a shot tonight and report back what I learn. Thanks!

I haven't narrowed it down yet, but somehow the defines in zncconfig.h aren't showing up in source files that seem to include them
[  1%] Building CXX object src/CMakeFiles/znclib.dir/znc.cpp.o
/Users/emertens/Source/znc/src/znc.cpp:117:20: error: use of undeclared identifier 'VERSION_STR'
    return CString(VERSION_STR) + CString(ZNC_VERSION_EXTRA);
                   ^
/Users/emertens/Source/znc/src/znc.cpp:484:47: error: use of undeclared identifier 'VERSION_STR'
    config.AddKeyValuePair("Version", CString(VERSION_STR));
                                              ^
/Users/emertens/Source/znc/src/znc.cpp:624:46: error: use of undeclared identifier 'VERSION_STR'
    vsLines.push_back("Version = " + CString(VERSION_STR));
                                             ^
/Users/emertens/Source/znc/src/znc.cpp:1064:20: error: use of undeclared identifier 'VERSION_MAJOR'
        make_tuple(VERSION_MAJOR, VERSION_MINOR);
                   ^
/Users/emertens/Source/znc/src/znc.cpp:1064:35: error: use of undeclared identifier 'VERSION_MINOR'
        make_tuple(VERSION_MAJOR, VERSION_MINOR);
                                  ^
/Users/emertens/Source/znc/src/znc.cpp:1068:43: error: use of undeclared identifier 'VERSION_STR'
        BackupConfigOnce("pre-" + CString(VERSION_STR));
                                          ^
6 errors generated.

OK, I deleted the znc directory and started fresh. There was cruft from an old autoconf build there that was invisible to git with the default settings.
With that done a new linker error emerges
[6/32] Linking CXX shared module modules/crypt.so
FAILED: modules/crypt.so
: && /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/c++  -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX14.0.sdk -mmacosx-version-min=13.6 -bundle -Wl,-headerpad_max_install_names  -o modules/crypt.so modules/CMakeFiles/module_crypt.dir/crypt.cpp.o  -Wl,-bundle_loader,src/znc && :
ld: Undefined symbols:
  _BN_bin2bn, referenced from:
      CCryptMod::DH1080_comp(CString&, CString&) in crypt.cpp.o
  _BN_bn2bin, referenced from:
      CCryptMod::DH1080_gen() in crypt.cpp.o
      CCryptMod::DH1080_gen() in crypt.cpp.o
...

Fix to this new error seems related to #1882 so I'll try to fix/merge that first, then will get back to macos

@glguy now this PR should work, can you retest?

@glguy now this PR should work, can you retest?

 ZNC was successfully compiled.


Fix user autoincrement id

Thanks for looking at this issue!
I tried your code. Creating a new user still does not add the ID field for me.
I tested running under Linux and nginx, with the default SQLite DB.

Sorry for the delay.
I get three errors:
[Doctrine\DBAL\Exception\DriverException]
An exception occurred in driver: could not find driver
[Doctrine\DBAL\Driver\PDOException]
could not find driver
[PDOException]
could not find driver

That's the problem, the migration is not running and the change is not beign applied.
I had to set the env variables with the database type and adapter to get them to run

I am not sure what you mean. I do have the DB type set, and the driver (both like .env.example).

@izambl I apologize for being silent. I have been pulled in other directions the past few days.
Are you still looking at this?

@izambl I am sorry it took me so long to get back to this. I did merge.
Thanks again for your help. Please continue as a member of the community!


Allow multiple named parameter in single path part

This PR allows /{foo}-{bar}/{file}.{ext}

Coverage remained the same at 97.643% when pulling 3b06d37ad03f3519dbc9cc4a0f12539698bec9d8 on MugeSo:allow-multiple-named-parameters-in-single-path-part into 575d90f3694bf7385c00d4caf7e8bd61decbeb53 on kogosoftwarellc:master.

Coverage remained the same at 97.643% when pulling 3b06d37ad03f3519dbc9cc4a0f12539698bec9d8 on MugeSo:allow-multiple-named-parameters-in-single-path-part into 575d90f3694bf7385c00d4caf7e8bd61decbeb53 on kogosoftwarellc:master.

Coverage remained the same at 97.643% when pulling 3b06d37ad03f3519dbc9cc4a0f12539698bec9d8 on MugeSo:allow-multiple-named-parameters-in-single-path-part into 575d90f3694bf7385c00d4caf7e8bd61decbeb53 on kogosoftwarellc:master.

Coverage remained the same at 97.643% when pulling 3b06d37ad03f3519dbc9cc4a0f12539698bec9d8 on MugeSo:allow-multiple-named-parameters-in-single-path-part into 575d90f3694bf7385c00d4caf7e8bd61decbeb53 on kogosoftwarellc:master.

Coverage remained the same at 97.643% when pulling 4e96f599db2681ecbb4adb9f1e6a368f3ef75f54 on MugeSo:allow-multiple-named-parameters-in-single-path-part into 575d90f3694bf7385c00d4caf7e8bd61decbeb53 on kogosoftwarellc:master.

Can you also add this to the README?

I don't know which section should I write it in.

I don't know which section should I write it in.

How about in a new description under this heading.  There's currently just a bullet point underneath that.  We should probably have a sub heading titled Path Configuration above the existing bullet point.

On second thought, how about a new Path Parameters section above Operation Parameters that explains how {param} works in the filename as well as an example of multiple params in a path part.

@MugeSo any updates?

@MugeSo if you can add documentation later I'd appreciate it.  Thanks for the change!


[TF2.0] Disable XLA as default build option

Synced up with @whchung and we agreed that this is the more appropriate way to disable xla support.

@sunway513 Gentle ping


🐛 Applying biome check --apply* goes over files.include. biome.jsonc specifically

Environment information
CLI:
  Version:                      1.6.4
  Color support:                true

Platform:
  CPU Architecture:             x86_64
  OS:                           linux

Environment:
  BIOME_LOG_DIR:                unset
  NO_COLOR:                     unset
  TERM:                         "xterm"
  JS_RUNTIME_VERSION:           "v20.11.0"
  JS_RUNTIME_NAME:              "node"
  NODE_PACKAGE_MANAGER:         "pnpm/8.15.6"

Biome Configuration:
  Status:                       Loaded successfully
  Formatter disabled:           false
  Linter disabled:              false
  Organize imports disabled:    true
  VCS disabled:                 true

Workspace:
  Open Documents:               0

What happened?
With the following config biome.jsonc:
{
	"$schema": "https://biomejs.dev/schemas/1.6.4/schema.json",
	"files": {
		"ignoreUnknown": true,
		"include": ["config/**/*.ts", "source/**/*.ts", "server.ts"],
		"ignore": ["var/**/*"]
	},
    // snip

Run biome check --config-path ./ --apply-unsafe ./
biome.jsonc is formatted even if not explicitly present in include.

This is a problem because in VSCode we cannot use specific extension to format specific files so when we format biome.jsonc via editor, the output will be always different creating useless changes in git.
Expected result
I expect --apply* to work ONLY on files matching the include patterns.
In fact I see ignore in this specific case redundant because the folder is not included.
The problem seems to arise because of the required PATH in biome check [PATH] (./ in this case). Given a config AND and include, PATH seems to be redundant and unnecessary. Even confusing given that checks files that are not included (both the excluded folder and `biome.jsonc' in my case).
Probably I'm missing something that requires [PATH] to be provided.
Code of Conduct

[X] I agree to follow Biome's Code of Conduct

You don't need to specify --config-path ./ because the configuration file is in the working directory.
It is intentional that biome.json and biome.jsonc are always formatted. This was a user request.
Why do you want to ignore biome.jsonc?

You don't need to specify --config-path ./ because the configuration file is in the working directory.
Thanks, didn't know that.

It is intentional that biome.json and biome.jsonc are always formatted. This was a user request.
Why do you want to ignore biome.jsonc?
Because in VSCode json files are formatted with another extension (JSON Language Features) and cannot overridethis just for biome.jsonc leading to always have a change in git.

Anyway, I think the problem with [PATH] and include/exclude still applies.

Actually you can change default JSON formatter in VSCode and even enforce it on the repo level.
Create settings.json in .vscode folder with this content:
{
  "[json]": {
    "editor.defaultFormatter": "biomejs.biome"
  },
  "[jsonc]": {
    "editor.defaultFormatter": "biomejs.biome"
  }
}

As long as you commit this file into the repo, the only way contributors can format JSON files any other way is by explicitly choosing to, because settings in .vscode/settings.json have higher precedence over user and workspace settings.

Actually you can change default JSON formatter in VSCode and even enforce it on the repo level. Create settings.json in .vscode folder with this content:
{
  "[json]": {
    "editor.defaultFormatter": "biomejs.biome"
  },
  "[jsonc]": {
    "editor.defaultFormatter": "biomejs.biome"
  }
}

As long as you commit this file into the repo, the only way contributors can format JSON files any other way is by explicitly choosing to, because settings in .vscode/settings.json have higher precedence over user and workspace settings.

This changes the formatter for EVERY json file, not just for the biome.json(c) as I stated before.
Now I think the issue title is misleading. Should I change it with "Biome apply changes to files regardless of files.include" or something like that?

Well the title of the issue is biome CLI formatting its own config, while message I replied to is about VSCode formatting it differently by default. In fact even the OP message mentions it being about VSCode.

This is surely a strange edge case. Why can't Biome format its own file configuration?? 🤔

Because VSCode uses JSON Language Features as formatter for a language, not a specific single file. I cannot tell VSCode "use this formatter (biomejs.biome) just for biome.jsonc. With "Format on save", biome.jsonc it will be formatted by VSCode.
Then launchingbiome check --apply* the content changes creating a changeset in git. You have to remember to reformat the code via VSCode if you don't want to commit this kind of changes.
Applying the previous suggestion will going to format every JSON file in my project on save in VSCode with biome and I don't want that.
I can resolve this by putting biome.jsonc in files.ignore and it works as expected.

I can update the original post, remove the biome.jsonc part and focus on what to me is the real issue:
launching biome check --apply ./ with "include": ["config/**/*.ts", "source/**/*.ts", "server.ts"], formats OTHERS folders (like var/**/*) that are not under files.include. I do not expect to format other folders and have to curate a list of files.ignored paths because of that.
Should I update the issue?

Yes @FedericoBiccheddu, we should focus on one single issue. Also, make sure to update to the latest. Maybe your issue was fixed.


Add ability to hide comments

Adds a checkbox with label "Show comments" that appears in the upper right. It is checked by default. If unchecked, comments and code diagnostics are hidden. The state of the checkbox isn't saved when switching to other revisions - let me know if you think this is important to add.
Also did a Format Document on Review.cshtml

I like the feature but am not sure about the implementation, it doesn't inter-operate very well with existing commenting functionality, for example sometimes clicking on the element or the add button would open a commenting window and you would be able to comment without knowing if there are existed comments and sometimes comment window wouldn't even show up looking like a bug.

I like the feature but am not sure about the implementation, it doesn't inter-operate very well with existing commenting functionality, for example sometimes clicking on the element or the add button would open a commenting window and you would be able to comment without knowing if there are existed comments and sometimes comment window wouldn't even show up looking like a bug.
Non persistence across the revision switch is less of a concern and is easy to fix.

When would comment window not even show up when attempting to add a new comment (or maybe I am misinterpreting your comment)? I think it would always show up when clicking to add a new comment regardless of the state of the checkbox since it is a new element being added and the jquery selector only updates the elements that are already in the document when the checkbox is clicked.
Since it is checked by default, a user would have to intentionally uncheck it. However I can see them forgetting that they unchecked it and coming back later and adding the same comment again or something like that. I guess we could lock down adding new comments if they are currently being hidden?

When would comment window not even show up when attempting to add a new comment (or maybe I am misinterpreting your comment)?

Try hiding an existing thread and then clicking on add button for the same element. New element is added but under a hidden one.

I guess we could lock down adding new comments if they are currently being hidden?

This would require people to unhide and find the element again to add a comment.

Another idea would be to automatically toggle the comments back on when a user clicks to add a new comment. This would help prevent the duplicate comment concern.

Yeah, having some compact indication that there are comments/diagnostics but they are hidden, allow toggling them individually and having add show the existing comments would be the best option.

Try hiding an existing thread and then clicking on add button for the same element. New element is added but under a hidden one.

Sure, I thought you were saying that there were cases where a new comment couldn't be added.

having some compact indication that there are comments/diagnostics but they are hidden

Do you mean per hidden comment thread? This seems to defeat the purpose of the feature, as the intent is to show solely the API without any clutter from comments.

allow toggling them individually

This doesn't seem useful to me as we already have the ability to resolve comments. I don't see the use in hiding individual comments completely as this could lead to even more confusion, especially if we don't add the compact indication of the existence of comments on a thread by thread basis.
I do agree about showing the existing comments when attempting to add a new comment if they are currently hidden, but as for the other two features I guess we can chat more in person if you feel strongly about these.

Sure, I thought you were saying that there were cases where a new comment couldn't be added.

Yes, new comment can not be added to an existing thread.

Do you mean per hidden comment thread? This seems to defeat the purpose of the feature, as the intent is to show solely the API without any clutter from comments.

It depends on how the indication is done, I'm sure we can think of something that doesn't clutter too much.

This doesn't seem useful to me as we already have the ability to resolve comments. I don't see the use in hiding individual comments completely as this could lead to even more confusion, especially if we don't add the compact indication of the existence of comments on a thread by thread basis.

Imagine you're scrolling through APIs and want to leave a comment but would like to see existing ones first, scrolling to the top and toggling all threads on would be not very convenient.

I though about something like:

It would represent that there are existing comments, and clicking on it would show them and allow commenting.

Imagine you're scrolling through APIs and want to leave a comment but would like to see existing ones first, scrolling to the top and toggling all threads on would be not very convenient.

I guess I was imagining this as a feature that would be used only when wanting to get an overall sense of the shape of the API. I didn't really think of it as something where users would want to actually interact with the tool while things are hidden, but I guess it is reasonable that they would want to have things hidden yet still be able to see individual comments for a specific API. This opens up the whole can of worms of managing the state of whether individual comments are hidden. I assume we would want to store off this information just like we do for resolved comments? Also, do you think the checkbox still makes sense given that we want to toggle individual comments? It is still useful to toggle things all off/on quickly, but the state of it is a bit weird when somethings are shown and some are hidden. I think that is probably okay.

I though about something like:

It would represent that there are existing comments, and clicking on it would show them and allow commenting.

Yeah that looks pretty good, thanks.


Failed to build on ubuntu16.04 due to error about image_input_op_gpu.cc.o

Hi, I am building caffe2 from source, per instructions here https://caffe2.ai/docs/getting-started.html?platform=ubuntu&configuration=compile, and it has problem gpu related stuff. Here is the output:
[ 77%] Building CXX object caffe2/CMakeFiles/caffe2_gpu.dir/image/image_input_op_gpu.cc.o
In file included from /home/marxlp/anaconda3/gcc/include/c++/vector:64:0,
from /home/marxlp/anaconda3/gcc/include/c++/bits/random.h:34,
from /home/marxlp/anaconda3/gcc/include/c++/random:50,
from /home/marxlp/anaconda3/gcc/include/c++/bits/stl_algo.h:65,
from /home/marxlp/anaconda3/gcc/include/c++/algorithm:62,
from /home/marxlp/github/caffe2/caffe2/core/registry.h:24,
from /home/marxlp/github/caffe2/caffe2/core/flags.h:39,
from /home/marxlp/github/caffe2/caffe2/core/logging.h:26,
from /home/marxlp/github/caffe2/caffe2/core/common_gpu.h:41,
from /home/marxlp/github/caffe2/caffe2/image/image_input_op_gpu.cc:17:
/home/marxlp/anaconda3/gcc/include/c++/bits/stl_vector.h: In instantiation of ‘class std::vector’:
/home/marxlp/anaconda3/gcc/include/c++/bits/random.h:5299:22:   required from here
/home/marxlp/anaconda3/gcc/include/c++/bits/stl_vector.h:210:11: internal compiler error: Segmentation fault
class vector : protected _Vector_base<_Tp, _Alloc>
^
Please submit a full bug report,
with preprocessed source if appropriate.
See http://gcc.gnu.org/bugs.html for instructions.
caffe2/CMakeFiles/caffe2_gpu.dir/build.make:1055: recipe for target 'caffe2/CMakeFiles/caffe2_gpu.dir/image/image_input_op_gpu.cc.o' failed
make[3]: *** [caffe2/CMakeFiles/caffe2_gpu.dir/image/image_input_op_gpu.cc.o] Error 1
make[3]: Leaving directory '/home/marxlp/github/caffe2/build'
CMakeFiles/Makefile2:2310: recipe for target 'caffe2/CMakeFiles/caffe2_gpu.dir/all' failed
make[2]: *** [caffe2/CMakeFiles/caffe2_gpu.dir/all] Error 2
make[2]: Leaving directory '/home/marxlp/github/caffe2/build'
Makefile:138: recipe for target 'all' failed
make[1]: *** [all] Error 2
make[1]: Leaving directory '/home/marxlp/github/caffe2/build'
Makefile:4: recipe for target 'all' failed
make: *** [all] Error 2

The error looks like an internal compiler error. Not much we can do on the Caffe2 side.
What are the specs of the machine you are trying to compile on? Perhaps you're running out of memory?

@pietern ,thanks for your reply. I solved this problem by creating a new virtual environment by python3's venv while my original build was based on anaconda3, which libraries may not be compatible with caffe2.
My machine's specs: Ubuntu 16.06 x64 and GetForce 850M with 4GB memory.


Remove app icon is showing up in all apps mode in the launcher

I was testing the all apps mode in the launcher and found a bug. When you drag a app around the remove option comes up as well as the uninstall. but when an app is installed from the play store and you go to drag it around the only option that shows up is the remove option uninstall does not show up. is there any way to remove the remove option from all apps mode?
Thanks in advance!

When you install an app the launcher will directly add the shortcut intent to the desktop so it is not an app object so only remove is shown,
I will fix this remove the remove option from all apps mode? and that too.
But currently I am busying with a app competition. Damn....

All apps mode was removed for now


Allow using a custom S3 endpoint as lakeFS' block storage

In the block package of the lakeFS app, we currently allow connecting only to AWS S3. To be able to use other S3-compatible storage engines, e.g. Minio, allow specifying a custom endpoint through the lakeFS configuration.

under 'blockstore.s3' adding the following will allow connection to MinIO
yaml endpoint: http://s3.local.lakefs.io:9000 force_path_style: true


train up subpredictors in parallel using parallel map

done! pretty easy too. plenty of next optimizations to make still.


[#17] [#18] [Integration] PART 2 - As a signed-in user, I can see horizontal scrollable list of survey and pull down to refresh survey list on the Home screen

Close #17 #18

What happened 👀

Implement integrating saving surveys list as cache
Convert survey models to JSON serializable
Add unit test

Insight 📝

The total survey list will be refreshed after refreshing is executed successfully.
The app will always fetch surveys from server first, when it is failed, then loading surveys from cache

Proof Of Work 📹

Unit test passed

Android

device-2023-05-11-174214.webm

Resolved @nmint8m ✅ please kindly recheck if you have time


http:support for adding dynamic request headers to the upstream requests

PR for GH #1016
Signed-off-by: Kunal Gandhi<EMAIL_ADDRESS>

@mattklein123 @htuch do you want to take a pass on this?

Yup will do early next week.

Thank you @mattklein123 . after making the change, the circleci build is failing due the following error:
brew ls --versions coreutils >/dev/null || brew install coreutils
bash: line 1: brew: command not found
bash: line 1: brew: command not found

brew ls --versions coreutils >/dev/null || brew install coreutils returned exit code 127

Also, the Mac OSX build seems to have passed but it does not seem to get marked as a successful step on the PR
https://circleci.com/gh/turbinelabs/envoy/796


Have default config.yml load by default

Avoid multiple example config.yml in various places.
Use in tests, examples, tutorials, demos.
Expose dump function.
Related to #29 eventually?

Mostly implemented in 7260d8e342a0d480295d83cb6ceb720a5dabc290.
Although considering a more @property-like syntax and/or yaml-dump function

Making update_params and set_params behavior more explicit (as well as including a IntrahostComponent.params.yaml property to dump formatted parameters) in https://github.com/edwenger/emodlib/commit/fcf79c21886292ea35b0b59fb8ab2928ee95b518


Error in when i try to ng serve

Bug Report or Feature Request (mark with an x)
- [x] bug report -> please search issues before submitting
- [ ] feature request

Command (mark with an x)
- [ ] new
- [ ] build
- [x] serve
- [ ] test
- [ ] e2e
- [ ] generate
- [ ] add
- [ ] update
- [ ] lint
- [ ] xi18n
- [ ] run
- [ ] config
- [ ] help
- [ ] version
- [ ] doc

Versions
Angular CLI: 7.0.1
Node: 10.12.0
OS: darwin x64
Angular: 7.0.0
... cdk, common, compiler, core, material
Repro steps
npm i --save
npm install @angular/cli -g
ng serve
The log given by the failure
ERROR in ./src/assets/styles/app.scss (./node_modules/raw-loader!./node_modules/postcss-loader/lib??embedded!./node_modules/sass-loader/lib/loader.js??ref--15-3!./src/assets/styles/app.scss)
Module build failed (from ./node_modules/sass-loader/lib/loader.js):
Error: Dart Sass version 1.2.0 is incompatible with ^1.3.0.
at getRenderFuncFromSassImpl (/Users/onixortiz/Documents/GitHub/Cinco-validation/cinco-validation/node_modules/sass-loader/lib/loader.js:103:19)
at Object.sassLoader (/Users/onixortiz/Documents/GitHub/Cinco-validation/cinco-validation/node_modules/sass-loader/lib/loader.js:46:20)
ERROR in node_modules/@angular/flex-layout/extended/typings/style/style.d.ts(72,67): error TS1144: '{' or ';' expected.
node_modules/@angular/flex-layout/extended/typings/style/style.d.ts(74,5): error TS1128: Declaration or statement expected.
node_modules/@angular/flex-layout/extended/typings/style/style.d.ts(74,33): error TS1005: ';' expected.
node_modules/@angular/flex-layout/extended/typings/style/style.d.ts(74,39): error TS1109: Expression expected.
node_modules/@angular/flex-layout/extended/typings/style/style.d.ts(79,5): error TS1128: Declaration or statement expected.
node_modules/@angular/flex-layout/extended/typings/style/style.d.ts(80,1): error TS1128: Declaration or statement expected.
Desired functionality

Mention any other details that might be useful
I have uninstall and re-install node a few times
I'm the only one in my team that can't access de project.

This seems like a bug but we'll need to look at a reproduction to find and fix the problem. Can you setup a minimal repro please?
You can read here why this is needed. A good way to make a minimal repro is to create a new app via ng new repro-app and adding the minimum possible code to show the problem. Then you can push this repository to github and link it here.
This might be related to your directory structure so its really important to get an accurate repro to diagnose this.


An error occurred while packing in electron

The following message is displayed when installing ‘npm i ollama’ and then packing with electron:
• electron-builder  version=24.5.2 os=10.0.19045
• loaded configuration  file=package.json ("build" field)
• description is missed in the package.json  appPackageFile=E:\Project\Knowledge\package.json
• author is missed in the package.json  appPackageFile=E:\Project\Knowledge\package.json
• writing effective config  file=release\builder-effective-config.yaml
• executing @electron/rebuild  arch=x64 platform=windows version=25.2.0 appDir=E:\Project\Knowledge
Error: Could not find any Python installation to use
at PythonFinder.fail (E:\Project\Knowledge\node_modules\node-gyp\lib\find-python.js:330:47)
at PythonFinder.runChecks (E:\Project\Knowledge\node_modules\node-gyp\lib\find-python.js:159:21)
at PythonFinder. (E:\Project\Knowledge\node_modules\node-gyp\lib\find-python.js:228:18)
at PythonFinder.execFileCallback (E:\Project\Knowledge\node_modules\node-gyp\lib\find-python.js:294:16)
at exithandler (node:child_process:427:5)
at ChildProcess.errorhandler (node:child_process:439:5)
at ChildProcess.emit (node:events:513:28)
at ChildProcess._handle.onexit (node:internal/child_process:289:12)
at onErrorNT (node:internal/child_process:476:16)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
⨯ node-gyp failed to rebuild 'E:\Project\Knowledge\node_modules\canvas'  failedTask=build stackTrace=Error: node-gyp failed to rebuild
'E:\Project\Knowledge\node_modules\canvas'
at ChildProcess. (E:\Project\Knowledge\node_modules@electron\rebuild\src\module-type\node-gyp\node-gyp.ts:131:16)
at ChildProcess.emit (node:events:513:28)
at Process.ChildProcess._handle.onexit (node:internal/child_process:291:12)

Hi @whl1207, ollama-js uses Node, but I believe that Electron uses Node so this should work. It looks like you may need Python configured on your system to build the node-gyp dependency in this case. Does building other node packages work?

Hi @whl1207, ollama-js uses Node, but I believe that Electron uses Node so this should work. It looks like you may need Python configured on your system to build the node-gyp dependency in this case. Does building other node packages work?

Thank you for your help. electron uses nodejs. When I installed python, the packaging still prompts me to install Visual Studio, do I have to use vs studio to use ollama-js? The specific error is as follows:
`Error: Could not find any Visual Studio installation to use
at VisualStudioFinder.fail (D:\Project\Knowledge\node_modules\node-gyp\lib\find-visualstudio.js:122:47)
at D:\Project\Knowledge\node_modules\node-gyp\lib\find-visualstudio.js:75:16
at VisualStudioFinder.findVisualStudio2013 (D:\Project\Knowledge\node_modules\node-gyp\lib\find-visualstudio.js:380:14)
at D:\Project\Knowledge\node_modules\node-gyp\lib\find-visualstudio.js:71:14
at VisualStudioFinder.findVisualStudio2015 (D:\Project\Knowledge\node_modules\node-gyp\lib\find-visualstudio.js:364:14)
at D:\Project\Knowledge\node_modules\node-gyp\lib\find-visualstudio.js:67:12
at failPowershell (D:\Project\Knowledge\node_modules\node-gyp\lib\find-visualstudio.js:156:7)
at VisualStudioFinder.parseData (D:\Project\Knowledge\node_modules\node-gyp\lib\find-visualstudio.js:170:14)
at D:\Project\Knowledge\node_modules\node-gyp\lib\find-visualstudio.js:143:14
at ChildProcess.exithandler (node:child_process:414:7)
⨯ node-gyp failed to rebuild 'D:\Project\Knowledge\node_modules\canvas'  failedTask=build stackTrace=Error: node-gyp failed to rebuild 'D:\Project\Knowledge\node_modules\canvas'
at ChildProcess. (D:\Project\Knowledge\node_modules@electron\rebuild\src\module-type\node-gyp\node-gyp.ts:131:16)
at ChildProcess.emit (node:events:517:28)
at Process.ChildProcess._handle.onexit (node:internal/child_process:292:12)`

node-gyp is used to deal with native dependencies - so you are in windows, and its trying to find a compiler.
This has nothing to do with ollama-js, it has something to do with some other dependency you project has and the Electron build