String parameters with format 'date' get no Format in the QueryAttribute

Describe the bug
When generating a client for an OpenApi (swagger version 2.0) with url (query) parameters of type string with a format of 'date' are generated as a regular DateTimeOffset without a 'Date' format.
Support Key: mmt1dt0
OpenAPI Specifications
(not the full specs, but this is the gist of it)
{
  "swagger": "2.0",
  "info": {
    "title": "XX",
    "version": "0.0.0"
  },
  "host": "x.io",
  "basePath": "/",
  "schemes": [
    "https"
  ],
  "paths": {
    "/t/dummy/{employee_id}": {
      "get": {
        "summary": "X",
        "description": "X",
        "operationId": "dummy",
        "parameters": [
          {
            "name": "employee_id",
            "in": "path",
            "description": "the specific employee",
            "required": true,
            "format": "int64",
            "type": "integer"
          },
          {
            "name": "valid_from",
            "in": "query",
            "description": "the start of the period",
            "required": true,
            "format": "date",
            "type": "string"
          },
          {
            "name": "valid_to",
            "in": "query",
            "description": "the end of the period",
            "required": true,
            "format": "date",
            "type": "string"
          }
        ],
        "responses": {
          "200": {
            "description": "No response was specified",
            "schema": {
              "$ref": "#/definitions/DummyList"
            }
          }
        },
        "produces": [
          "application/json",
          "application/xml"
        ]
      }
    },
  }
},

Additional context
Resulting code is:
        /// <summary>
        /// X
        /// </summary>
        [Get("/t/dummy/{employee_id}")]
        Task<DummyList> Dummy(long employee_id, [Query(CollectionFormat.Multi)] System.DateTimeOffset valid_from, [Query(CollectionFormat.Multi)] System.DateTimeOffset valid_to);

When executing, this results in errors.
Expected code:
        /// <summary>
        /// X
        /// </summary>
        [Get("/t/dummy/{employee_id}")]
        Task<DummyList> Dummy(long employee_id, [Query(CollectionFormat.Multi, Format = "yyyy-MM-dd")] System.DateTimeOffset valid_from, [Query(CollectionFormat.Multi, Format = "yyyy-MM-dd")] System.DateTimeOffset valid_to);

The same may be true for other date / time related formats, like 'time'. The same may also be true for entity classes where properties are generated as regular 'DateTimeOffset'.
Ideally, for 'time' and 'date', both the arguments of functions and the properties of entity classes would result in 'TimeOnly' and 'DateOnly', respectively, but I'm not sure if those are fully supported in Refit? I think they are for properties, not sure about function arguments.
Edit: apparently 'time' was no format in OpenApi (Swagger) v2, but 'date' apparently is.

@brease-colin thanks for taking the time to report this. I was not aware that you could do this with Refit. It looks simple enough and I will try to implement it as soon as possible

@all-contributors please add @brease-colin for bugs

Thanks for the quick response (and the library in general)!
I looked into the 'time' format some more. The strange thing is that even though it's not listed as an official data type in the Swagger 2.0 and OpenApi 3.0 specs as far as I can tell, it's still converted to a TimeSpan property type currently, at least on the entity model side.
Also, on the models side, a string format of 'date' results in a DateTimeOffset as well, but with a DateFormatConverter, so it already seems to manage that well. So it may just be the function arguments side where things can be improved.

The information I can find about the specs on the OpenAPI web site and also referenced for example here mention that an API with type string and format date expects a date string in the format yyyy-MM-dd. This is different from the expected input for the date-time type. According to the spec, those are actually two different things.

The internet date/time standard used by OpenAPI is defined in RFC 3339, section 5.6 (effectively ISO 8601) and examples are provided in section 5.8. So for date values should look like "2018-03-20" and for date-time, "2018-03-20T09:12:28Z". As such, when using date or date-time, the pattern should be omitted.
If you need to support dates/times formatted in a way that differs to RFC 3339, you are not allowed to specify your parameter as format: date or format: date-time. Instead, you should specify type: string with an appropriate pattern and remove format.
Finally, note that a pattern of "YYYY-MM-DD" is invalid according to the specification: pattern must be a regular expression, not a placeholder or format string.

I do not have much experience with different OpenAPI server software, so I don't know how it's handled in general when a string in the wrong format (i.e. a full DateTime string for a date format) is supplied, but an API that we're building a client for does not respond well when they're supplied with the default date format that is generated by a DateTimeOffset. In our case, we actually have to change the code for our client code to work.
I could understand you may be reluctant to change the default behavior, because for some, this may be a breaking change, but it's a change that would bring it in line with the specs.
Personally I would not let the users actually pick a format. If you'd decide to support this and also make it optional, I would expect an argument like useIsoDateTimeFormats (or perhaps a separate setting for date and date-time, but one may assume that if one of them is built according to the spec, the other would be as well).

The information I can find about the specs on the OpenAPI web site and also referenced for example here mention that an API with type string and format date expects a date string in the format yyyy-MM-dd. This is different from the expected input for the date-time type. According to the spec, those are actually two different things.

The internet date/time standard used by OpenAPI is defined in RFC 3339, section 5.6 (effectively ISO 8601) and examples are provided in section 5.8. So for date values should look like "2018-03-20" and for date-time, "2018-03-20T09:12:28Z". As such, when using date or date-time, the pattern should be omitted.
If you need to support dates/times formatted in a way that differs to RFC 3339, you are not allowed to specify your parameter as format: date or format: date-time. Instead, you should specify type: string with an appropriate pattern and remove format.
Finally, note that a pattern of "YYYY-MM-DD" is invalid according to the specification: pattern must be a regular expression, not a placeholder or format string.

I do not have much experience with different OpenAPI server software, so I don't know how it's handled in general when a string in the wrong format (i.e. a full DateTime string for a date format) is supplied, but an API that we're building a client for does not respond well when they're supplied with the default date format that is generated by a DateTimeOffset. In our case, we actually have to change the code for our client code to work.
I could understand you may be reluctant to change the default behavior, because for some, this may be a breaking change, but it's a change that would bring it in line with the specs.
Personally I would not let the users actually pick a format. If you'd decide to support this and also make it optional, I would expect an argument like useIsoDateTimeFormats (or perhaps a separate setting for date and date-time, but one may assume that if one of them is built according to the spec, the other would be as well).

@brease-colin Thanks for looking into the details of this
It's true that it might be a breaking change for some, but since multiple versions of the tool are available from nuget.org, I'm that afraid of introducing breaking changes.
I like the idea of bringing this in line with the OpenAPI specification so I will implement this starting with introducing the --useIsoDateTimeFormats CLI tool argument

Does this work for you @brease-colin
USAGE:
    refitter [URL or input file] [OPTIONS]

EXAMPLES:
    refitter ./openapi.json
    refitter https://petstore3.swagger.io/api/v3/openapi.yaml
    refitter ./openapi.json --namespace "Your.Namespace.Of.Choice.GeneratedCode" --output ./GeneratedCode.cs
    refitter ./openapi.json --namespace "Your.Namespace.Of.Choice.GeneratedCode" --internal
    refitter ./openapi.json --output ./IGeneratedCode.cs --interface-only
    refitter ./openapi.json --use-api-response
    refitter ./openapi.json --cancellation-tokens
    refitter ./openapi.json --no-operation-headers
    refitter ./openapi.json --use-iso-date-format

ARGUMENTS:
    [URL or input file]    URL or file path to OpenAPI Specification file

OPTIONS:
                                      DEFAULT
    -h, --help                                         Prints help information
    -n, --namespace                   GeneratedCode    Default namespace to use for generated types
    -o, --output                      Output.cs        Path to Output file
        --no-auto-generated-header                     Don't add <auto-generated> header to output file
        --interface-only                               Don't generate contract types
        --use-api-response                             Return Task<IApiResponse<T>> instead of Task<T>
        --internal                                     Set the accessibility of the generated types to 'internal'
        --cancellation-tokens                          Use cancellation tokens
        --no-operation-headers                         Don't generate operation headers
        --no-logging                                   Don't log errors or collect telemetry
        --use-iso-date-format                          Explicitly format date query string parameters in ISO 8601
                                                       standard date format using delimiters (2023-06-15)

The following example OpenAPI spec:
{
  "swagger": "2.0",
  "info": {
    "title": "XX",
    "version": "0.0.0"
  },
  "host": "x.io",
  "basePath": "/",
  "schemes": [
    "https"
  ],
  "paths": {
    "/t/dummy/{employee_id}": {
      "get": {
        "summary": "X",
        "description": "X",
        "operationId": "dummy",
        "parameters": [
          {
            "name": "employee_id",
            "in": "path",
            "description": "the specific employee",
            "required": true,
            "format": "int64",
            "type": "integer"
          },
          {
            "name": "valid_from",
            "in": "query",
            "description": "the start of the period",
            "required": true,
            "format": "date",
            "type": "string"
          },
          {
            "name": "valid_to",
            "in": "query",
            "description": "the end of the period",
            "required": true,
            "format": "date",
            "type": "string"
          }
        ],
        "responses": {
          "200": {
            "description": "No response was specified",
            "schema": {
              "$ref": "#/definitions/DummyList"
            }
          }
        },
        "produces": [
          "application/json",
          "application/xml"
        ]
      }
    },
  }
}

generates the following code when using the --use-iso-date-format CLI tool argument
public interface IXX
{
    /// <summary>
    /// X
    /// </summary>
    [Get("/t/dummy/{employee_id}")]
    Task Dummy(long employee_id, [Query(Format = "yyyy-MM-dd")] System.DateTimeOffset valid_from, [Query(Format = "yyyy-MM-dd")] System.DateTimeOffset valid_to, [Query] System.TimeSpan test_time);
}

I assume the test_time parameter will not appear out of nowhere (as it's not in the spec you mention), but other than that, looks great!

Copy/paste error there 😂

This is now release to nuget.org as v0.6.0


Node1 LAN to Node2 LAN connectivity problem,  Tunnel is  active

I have 3 servers
Node0 is the Nebula Lighthouse server on Hetzner Cloud in Germany
Node1 is a KVM Ubuntu VM here at my home.
Node2 is a KVM Ubuntu VM here at my home.
Both Node1 and Node2 are on the same <IP_ADDRESS> subnet.
Both Node1 and Node2 have LXD Containers on them behind a 10.x.x.1/24 DNSMASQ bridge
The Nebula Configs for each Node0, Node1 and Node2 are attached.
I created the Certs for Node1 and Node2 and specified for each the Subnet of the LXD containers (see configs).
Starting Nebula on all three nodes and Node1 and Node2 connect to Node0 (Lighthouse)
Node1 can ping the nebula1 tunnel interface IP of Node2  and Node0 (lighthouse)
Node2 can ping the nebula1 tunnel interface IP of Node1  and Node0 (lighthouse)
Node 0 can ping both Node1 and Node2 nebula1 interface IP address
Node0 pings

node0:~$ ping <IP_ADDRESS>
PING <IP_ADDRESS> (<IP_ADDRESS>) 56(84) bytes of data.
64 bytes from <IP_ADDRESS>: icmp_seq=1 ttl=64 time=140 ms
64 bytes from <IP_ADDRESS>: icmp_seq=2 ttl=64 time=134 ms

node0:~$ ping <IP_ADDRESS>
PING <IP_ADDRESS> (<IP_ADDRESS>) 56(84) bytes of data.
64 bytes from <IP_ADDRESS>: icmp_seq=1 ttl=64 time=138 ms
64 bytes from <IP_ADDRESS>: icmp_seq=2 ttl=64 time=140 ms

Problem:

Node1 can not ping the LXD <IP_ADDRESS> Bridge on Node2 or any of the LXD containers behind that bridge (re say (<IP_ADDRESS>)
Node2 can not ping the LXD <IP_ADDRESS> Bridge on Node1 or any of the LXD containers behind that bridge (re say <IP_ADDRESS>)

So with Nebula there is reachablity to every node from every other node but only to the Tunnel End Point (TEP) on the other end... not beyond to the other-side's LAN
Port 4242 is open everywhere or the Tunnels and Tunnel interface would not come up.
I'm looking for a reason for this or what I might be missing.   I did try implementing some iptables
statements on each node to forward traffic to/from the nebula1 TUN interface to/from LAN but unless I did those wrong... it made no difference.
NODE0 IPTABLES

node0:~$ sudo iptables -S
-P INPUT ACCEPT
-P FORWARD ACCEPT
-P OUTPUT ACCEPT
-A INPUT -i t1-br -p tcp -m tcp --dport 53 -m comment --comment "generated for LXD network t1-br" -j ACCEPT
-A INPUT -i t1-br -p udp -m udp --dport 53 -m comment --comment "generated for LXD network t1-br" -j ACCEPT
-A INPUT -i t1-br -p udp -m udp --dport 67 -m comment --comment "generated for LXD network t1-br" -j ACCEPT
-A FORWARD -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
-A FORWARD -s <IP_ADDRESS>/24 -d <IP_ADDRESS>/24 -i nebula1 -o t1-br -m conntrack --ctstate NEW -j ACCEPT
-A FORWARD -o t1-br -m comment --comment "generated for LXD network t1-br" -j ACCEPT
-A FORWARD -i t1-br -m comment --comment "generated for LXD network t1-br" -j ACCEPT
-A OUTPUT -o t1-br -p tcp -m tcp --sport 53 -m comment --comment "generated for LXD network t1-br" -j ACCEPT
-A OUTPUT -o t1-br -p udp -m udp --sport 53 -m comment --comment "generated for LXD network t1-br" -j ACCEPT
-A OUTPUT -o t1-br -p udp -m udp --sport 67 -m comment --comment "generated for LXD network t1-br" -j ACCEPT

NODE1 IPTABLES

node1:~$ sudo iptables -S
-P INPUT ACCEPT
-P FORWARD ACCEPT
-P OUTPUT ACCEPT
-A INPUT -i t1-br -p tcp -m tcp --dport 53 -m comment --comment "generated for LXD network t1-br" -j ACCEPT
-A INPUT -i t1-br -p udp -m udp --dport 53 -m comment --comment "generated for LXD network t1-br" -j ACCEPT
-A INPUT -i t1-br -p udp -m udp --dport 67 -m comment --comment "generated for LXD network t1-br" -j ACCEPT
-A FORWARD -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
-A FORWARD -s <IP_ADDRESS>/24 -d <IP_ADDRESS>/24 -i nebula1 -o t1-br -m conntrack --ctstate NEW -j ACCEPT
-A FORWARD -o t1-br -m comment --comment "generated for LXD network t1-br" -j ACCEPT
-A FORWARD -i t1-br -m comment --comment "generated for LXD network t1-br" -j ACCEPT
-A OUTPUT -o t1-br -p tcp -m tcp --sport 53 -m comment --comment "generated for LXD network t1-br" -j ACCEPT
-A OUTPUT -o t1-br -p udp -m udp --sport 53 -m comment --comment "generated for LXD network t1-br" -j ACCEPT
-A OUTPUT -o t1-br -p udp -m udp --sport 67 -m comment --comment "generated for LXD network t1-br" -j ACCEPT

NODE2 IPTABLES

node2:~$ sudo iptables -S
-P INPUT ACCEPT
-P FORWARD ACCEPT
-P OUTPUT ACCEPT
-A INPUT -i t1-br -p tcp -m tcp --dport 53 -m comment --comment "generated for LXD network t1-br" -j ACCEPT
-A INPUT -i t1-br -p udp -m udp --dport 53 -m comment --comment "generated for LXD network t1-br" -j ACCEPT
-A INPUT -i t1-br -p udp -m udp --dport 67 -m comment --comment "generated for LXD network t1-br" -j ACCEPT
-A FORWARD -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
-A FORWARD -s <IP_ADDRESS>/24 -d <IP_ADDRESS>/24 -i tun0 -o t1-br -m conntrack --ctstate NEW -j ACCEPT
-A FORWARD -o t1-br -m comment --comment "generated for LXD network t1-br" -j ACCEPT
-A FORWARD -i t1-br -m comment --comment "generated for LXD network t1-br" -j ACCEPT
-A OUTPUT -o t1-br -p tcp -m tcp --sport 53 -m comment --comment "generated for LXD network t1-br" -j ACCEPT
-A OUTPUT -o t1-br -p udp -m udp --sport 53 -m comment --comment "generated for LXD network t1-br" -j ACCEPT
-A OUTPUT -o t1-br -p udp -m udp --sport 67 -m comment --comment "generated for LXD network t1-br" -j ACCEPT

I am suspecting the routing problem has to do with use of the 2 KVM VMs as Nodes but in today's world where Containers are everywhere ... that would seem to be a common encounter for Nebula.
node0-config.yml.txt
node1-config.yml.txt
node2-config.yml.txt

I haven't used routes on Nebula, and I'm not that familiar with LXD, so perhaps I'm shooting in the dark here, but have you confirmed that IPv4 forwarding is enabled in the kernel and that the expected IP routes are configured on the nodes (I assume Nebula does this upon tunnel establishment but as I've said I've never tried this myself).

Thanks
Yes I had made sure that it was... executed the following on all nodes.
$ sudo sysctl -w net.ipv4.ip_foward=1
On Wed, Jan 8, 2020 at 6:15 PM Martin Gignac<EMAIL_ADDRESS>wrote:

I haven't used routes on Nebula, and I'm not that familiar with LXD, so
perhaps I'm shooting in the dark here, but have you confirmed that IPv4
forwarding is enabled in the kernel and that the expected IP routes are
configured on the nodes (I assume Nebula does this upon tunnel
establishment but as I've said I've never tried this myself).
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/slackhq/nebula/issues/154?email_source=notifications&email_token=AAM23J6PF2HQN7Y7EXHK4JDQ4ZNBDA5CNFSM4KEPEWJKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIOKVJA#issuecomment-572304036,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAM23J7ZTSO3RAIRX6BACYTQ4ZNBDANCNFSM4KEPEWJA
.

OK then. Well, I guess short of running tcpdump on the interfaces to try to figure out where packets get swallowed up I'm out of ideas!

thats ok... thanks for trying though!

Nebula checks every packet to ensure the IP of packet match certificate.
https://github.com/slackhq/nebula/blob/master/firewall.go#L363


Add Posthog Template

Goal
PostHog is an analytics template that offers powerful product analytics for web and mobile applications.
Payout
$200
Expectation
Develop the PostHog template with seamless integration for web and mobile tracking. It should support advanced analytics, event tracking, and user journey analysis. Consider incorporating cohort analysis and user segmentation features. Detailed documentation will guide users in utilizing PostHog's analytical capabilities to gain insights into their products.

there is already a Posthog template: https://railway.app/template/16rDub

It doesnt work...


Symlinks to themes not working

Hi there
I recently tried symlink-ing to some themes located in the local 'data' directory, from the wp-content/themes directory, however these themes are not showing from within the WP admin.
I'm wondering if I need to configure the Apache service from within the container to following symlinks?
I'm not sure where the Apache host configs are located within the coreos box. Could someone point me in the right direction so that I can troubleshoot?
I created the symlinks for each of the themes I wish to develop like so:

cd into 'data' directory: cd data
cp -R themes directory in the current 'data' directory (named wordpressthemes): cp -R ../pathtothemedirectory wp-content/themes
cd into themes directory: cd wp-content/themes
create symlink for each theme: ln -s ../../wordpressthemes/themename themename

Files and folders directly in the local 'data' directory besides the folder for running container will not be mounted. They are synced with CoreOS but will NOT be mounted by Docker container. Only files in each container folder (usually same as container name) will be mounted.
The following step will work:
1. Run a new container named 'myproject'
core@wocker ~ $ wocker run --name myproject

2. Copy your 'wordpressthemes' into 'myproject' in your local machine
$ cd data
$ cp -R /PATHTO/wordpressthemes myproject

3. cd into themes directory
cd myproject/wp-content/themes

4. Create symlink for each theme
ln -s ../../wordpressthemes/themename themename

However, I can't see any advantage in this style.


The repository 'https://packages.microsoft.com/repos/azure-cli bookworm Release' does not have a Release file

Describe the bug
Getting below error while running commands
The repository 'https://packages.microsoft.com/repos/azure-cli bookworm Release' does not have a Release file
Command: RUN apt-get update --yes
&& apt-get install --yes
azure-cli
dotnet-runtime-2.1
&& rm -rf /var/lib/apt/lists/*
Related command
RUN apt-get update --yes
&& apt-get install --yes
azure-cli
dotnet-runtime-2.1
&& rm -rf /var/lib/apt/lists/*
Errors
The repository 'https://packages.microsoft.com/repos/azure-cli bookworm Release' does not have a Release file
Issue script & Debug output
The repository 'https://packages.microsoft.com/repos/azure-cli bookworm Release' does not have a Release file
Expected behavior
It should run as expected
Environment Summary
NA
Additional context
No response

Thank you for opening this issue, we will look into it.

Debian bookworm is not supported yet. Tracked by https://github.com/Azure/azure-cli/issues/25750.

The bookworm package is built but it's not released yet.
Close this as tracked by #25750.


Japanese translation of Advanced Bonfires

[ ] Validate US Telephone Numbers
[ ] Symmetric Difference
[ ] Exact Change
[ ] Inventory Update
[ ] No repeats please
[ ] Friendly Date Ranges
[ ] Make a Person
[ ] Map the Debris
[ ] Pairwise

Closing in favor of https://github.com/FreeCodeCamp/TranslationExpansion/issues/57


Delete Circle CI's installation of an older go.

Was causing problems when you go get gomobile in Circle CI.
@keybase/react-hackers

:+1:


Undefined symbols for architecture arm64 Mac M1

Bug Description
When compiling the "Using Python from Rust" example in the documentation
use pyo3::prelude::*;
use pyo3::types::IntoPyDict;

fn main() -> PyResult<()> {
    Python::with_gil(|py| {
        let sys = py.import("sys")?;
        let version: String = sys.getattr("version")?.extract()?;

        let locals = [("os", py.import("os")?)].into_py_dict(py);
        let code = "os.getenv('USER') or os.getenv('USERNAME') or 'Unknown'";
        let user: String = py.eval(code, None, Some(&locals))?.extract()?;

        println!("Hello {}, I'm Python {}", user, version);
        Ok(())
    })
}

the linker raises many warnings looking like
ld: warning: object file (/Users/harrylees/.pyenv/versions/3.10.1/lib/libpython3.10.a(accu.o)) was built for newer macOS version (12.1) than being linked (11.3)
before finally failing with the error Undefined symbols for architecture arm64
I'm quite new to Rust and PyO3, I have been able to compile code using Rust in Python using maturin but I haven't had any luck compiling the examples for using Python in Rust.
Steps to Reproduce

cargo new, add pyo3 to Cargo.toml as outlined in the README example.
copy paste the example from the README into src/main.rs
cargo run

Backtrace
...
ld: warning: object file (/Users/harrylees/.pyenv/versions/3.10.1/lib/libpython3.10.a(parser.o)) was built for newer macOS version (12.1) than being linked (11.3)
          ld: warning: object file (/Users/harrylees/.pyenv/versions/3.10.1/lib/libpython3.10.a(accu.o)) was built for newer macOS version (12.1) than being linked (11.3)
          Undefined symbols for architecture arm64:
            "_libintl_bind_textdomain_codeset", referenced from:
                __locale_bind_textdomain_codeset in libpython3.10.a(_localemodule.o)
            "_libintl_bindtextdomain", referenced from:
                __locale_bindtextdomain in libpython3.10.a(_localemodule.o)
            "_libintl_textdomain", referenced from:
                __locale_textdomain in libpython3.10.a(_localemodule.o)
            "_libintl_dcgettext", referenced from:
                __locale_dcgettext in libpython3.10.a(_localemodule.o)
            "_libintl_setlocale", referenced from:
                __locale_setlocale in libpython3.10.a(_localemodule.o)
                __locale_localeconv in libpython3.10.a(_localemodule.o)
            "_libintl_dgettext", referenced from:
                __locale_dgettext in libpython3.10.a(_localemodule.o)
            "_libintl_gettext", referenced from:
                __locale_gettext in libpython3.10.a(_localemodule.o)
          ld: symbol(s) not found for architecture arm64
          clang: error: linker command failed with exit code 1 (use -v to see invocation)

Your operating system and version
M1 Macbook Air macOS Monterey 12.2
Your Python version (python --version)
Python 3.10.1
Your Rust version (rustc --version)
rustc 1.58.1 (db9d1b20b 2022-01-20)
Your PyO3 version
0.15.1
How did you install python? Did you use a virtualenv?
pyenv
Additional Info
No response

Did you use --enable-shared when installing Python with pyenv?


Update Microsoft Teams Powershell documentation

Since the Skype for Business Powershell module functionality has been moved to the Microsoft Teams Powershell module, please update the documentation for this command.

@SebastianPiendl Please indicate which document you are referring to and which command you are mentioning here. Thanks

Hello @SebastianPiendl
Recently I edited the article to add a reference to the parameter from this cmdlet that works for teams, please see under "-EnablePrivacyMode" in the article.
Thanks

@get-itips Thank you very much for the contribution and sharing this explanation. @SebastianPiendl Hope this comment is helpful for you. If you see a documentation update is required, please feel free to open an issue for the same. We proceed here to close it. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


English errors

I found issues in your english, fix the plurals and add articles.
Much lean, Usbo.

"Much lean", "English errors", "I found issues"
Lmao


Revert "Refactor: project structure"

Reverts tokitouq/MangaAPI#71

Dont need this Rever PR anymore since vercel config is completed
Closing*


Problems building for Windows x64 using Visual Studio 17.11.0

Trying to build Swift for windows for the first time. 30+ years as Windows developer, brand new to Swift.
I'm using the commands:
repo sync
S:\SourceCache\swift\utils\build.cmd -WindowsSDKs x64 -DebugInfo -SkipPackaging -EnableCaching
No problems till I get to building the basic module. Looks to me that Clang can't parse something from the complex header file but I can't figure out what or why.
Output follows. Any help in at least understanding what might be going wrong would be great. Am wanting to contribute to Swift on Windows, but obviously need to be able to build first.
Let me know if there's other info that I can provide to help diagnose what I must be doing wrong.
Thanks
[3932/6491] Building swift module Basic

FAILED: tools/swift/SwiftCompilerSources/Basic.o S:/b/5/tools/swift/SwiftCompilerSources/Basic.o

C:\Windows\system32\cmd.exe /C "cd /D S:\SourceCache\swift\SwiftCompilerSources && S:\b\toolchains\swift-5.10.1-RELEASE-windows10\LocalApp\Programs\Swift\Toolchains\5.10.1+Asserts\usr\bin\swiftc.exe -c -o S:/b/5/tools/swift/SwiftCompilerSources/Basic.o -sdk S:/b/toolchains/swift-5.10.1-RELEASE-windows10/LocalApp/Programs/Swift/Platforms/5.10.1/Windows.platform/Developer/SDKs/Windows.sdk -target x86_64-unknown-windows-msvc -module-name Basic -emit-module -emit-module-path S:/b/5/tools/swift/SwiftCompilerSources/Basic.swiftmodule -parse-as-library S:/SourceCache/swift/SwiftCompilerSources/Sources/Basic/SourceLoc.swift S:/SourceCache/swift/SwiftCompilerSources/Sources/Basic/StringParser.swift S:/SourceCache/swift/SwiftCompilerSources/Sources/Basic/Utils.swift -wmo -color-diagnostics -Xfrontend -validate-tbd-against-ir=none -Xfrontend -disable-target-os-checking -Xcc -std=c++17 -Xcc -DCOMPILED_WITH_SWIFT -Xcc -DSWIFT_TARGET -Xcc -UIBOutlet -Xcc -UIBAction -Xcc -UIBInspectable -cxx-interoperability-mode=default -O -cross-module-optimization -Xcc -UNDEBUG -Xcc -DPURE_BRIDGING_MODE -Xfrontend -disable-legacy-type-info -static -Xllvm -sil-disable-pass=loadable-address -Xcc -D_ALLOW_COMPILER_AND_STL_VERSION_MISMATCH -Xcc -I -Xcc S:/SourceCache/llvm-project/llvm/include -Xcc -I -Xcc S:/b/5/include -Xcc -I -Xcc S:/SourceCache/llvm-project/llvm/../clang/include -Xcc -I -Xcc S:/b/5/tools/clang/include -Xcc -I -Xcc S:/SourceCache/swift/include -Xcc -I -Xcc S:/b/5/tools/swift/SwiftCompilerSources/../include -I S:/b/5/tools/swift/SwiftCompilerSources"
<module-includes>:1:10: note: in file included from <module-includes>:1:

#include "ccomplex"

         ^

C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.41.34120\include/ccomplex:11:10: note: in file included from C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.41.34120\include/ccomplex:11:

#include <complex>

         ^

C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.41.34120\include\complex:13:10: note: in file included from C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.41.34120\include\complex:13:

#include <sstream>

         ^

C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.41.34120\include\sstream:10:10: note: in file included from C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.41.34120\include\sstream:10:

#include <istream>

         ^

C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.41.34120\include\istream:10:10: note: in file included from C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.41.34120\include\istream:10:

#include <ostream>

         ^

C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.41.34120\include\ostream:10:10: note: in file included from C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.41.34120\include\ostream:10:

#include <ios>

         ^

C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.41.34120\include\ios:10:10: note: in file included from C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.41.34120\include\ios:10:

#include <xlocnum>

         ^

C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.41.34120\include\xlocnum:15:10: note: in file included from C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.41.34120\include\xlocnum:15:

#include <iterator>

         ^

C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.41.34120\include\iterator:11:10: note: in file included from C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.41.34120\include\iterator:11:

#include <xutility>

         ^

C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.41.34120\include\xutility:11:10: note: in file included from C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.41.34120\include\xutility:11:

#include <__msvc_iter_core.hpp>

         ^

C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.41.34120\include\__msvc_iter_core.hpp:10:10: note: in file included from C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.41.34120\include\__msvc_iter_core.hpp:10:

#include <utility>

         ^

C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.41.34120\include\utility:11:10: note: in file included from C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.41.34120\include\utility:11:

#include <type_traits>

         ^

C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.41.34120\include\type_traits:131:5: error: static assertion failed: Calling declval is ill-formed, see N4950 [declval]/2.

    static_assert(false, "Calling declval is ill-formed, see N4950 [declval]/2.");

    ^

<module-includes>:1:10: note: in file included from <module-includes>:1:

#include "ccomplex"

         ^

C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.41.34120\include/ccomplex:11:10: note: in file included from C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.41.34120\include/ccomplex:11:

#include <complex>

         ^

C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.41.34120\include\complex:13:10: note: in file included from C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.41.34120\include\complex:13:

#include <sstream>

         ^

C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.41.34120\include\sstream:10:10: note: in file included from C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.41.34120\include\sstream:10:

#include <istream>

         ^

C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.41.34120\include\istream:10:10: note: in file included from C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.41.34120\include\istream:10:

#include <ostream>

         ^

C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.41.34120\include\ostream:10:10: note: in file included from C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.41.34120\include\ostream:10:

#include <ios>

         ^

C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.41.34120\include\ios:10:10: note: in file included from C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.41.34120\include\ios:10:

#include <xlocnum>

         ^

C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.41.34120\include\xlocnum:16:10: note: in file included from C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.41.34120\include\xlocnum:16:

#include <streambuf>

         ^

C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.41.34120\include\streambuf:10:10: note: in file included from C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.41.34120\include\streambuf:10:

#include <xiosbase>

         ^

C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.41.34120\include\xiosbase:11:10: note: in file included from C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.41.34120\include\xiosbase:11:

#include <system_error>

         ^

C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.41.34120\include\system_error:13:10: note: in file included from C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.41.34120\include\system_error:13:

#include <stdexcept>

         ^

C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.41.34120\include\stdexcept:11:10: note: in file included from C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.41.34120\include\stdexcept:11:

#include <xstring>

         ^

C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.41.34120\include\xstring:16:10: note: in file included from C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.41.34120\include\xstring:16:

#include <xpolymorphic_allocator.h>

         ^

C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.41.34120\include\xpolymorphic_allocator.h:10:10: note: in file included from C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.41.34120\include\xpolymorphic_allocator.h:10:

#include <tuple>

         ^

C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.41.34120\include\tuple:957:9: error: static assertion failed: get<T>(tuple<Types...>&) requires T to occur exactly once in Types. (N4971 [tuple.elem]/5)

        static_assert(false, "get<T>(tuple<Types...>&) "

        ^

<module-includes>:1:10: note: in file included from <module-includes>:1:

#include "ccomplex"

         ^

C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.41.34120\include/ccomplex:11:10: note: in file included from C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.41.34120\include/ccomplex:11:

#include <complex>

         ^

C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.41.34120\include\complex:13:10: note: in file included from C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.41.34120\include\complex:13:

#include <sstream>

         ^

C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.41.34120\include\sstream:10:10: note: in file included from C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.41.34120\include\sstream:10:

#include <istream>

         ^

C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.41.34120\include\istream:10:10: note: in file included from C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.41.34120\include\istream:10:

#include <ostream>

         ^

C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.41.34120\include\ostream:10:10: note: in file included from C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.41.34120\include\ostream:10:

#include <ios>

         ^

C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.41.34120\include\ios:10:10: note: in file included from C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.41.34120\include\ios:10:

#include <xlocnum>

         ^

C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.41.34120\include\xlocnum:16:10: note: in file included from C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.41.34120\include\xlocnum:16:

#include <streambuf>

         ^

C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.41.34120\include\streambuf:10:10: note: in file included from C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.41.34120\include\streambuf:10:

#include <xiosbase>

         ^

C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.41.34120\include\xiosbase:11:10: note: in file included from C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.41.34120\include\xiosbase:11:

#include <system_error>

         ^

C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.41.34120\include\system_error:13:10: note: in file included from C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.41.34120\include\system_error:13:

#include <stdexcept>

         ^

C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.41.34120\include\stdexcept:11:10: note: in file included from C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.41.34120\include\stdexcept:11:

#include <xstring>

         ^

C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.41.34120\include\xstring:16:10: note: in file included from C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.41.34120\include\xstring:16:

#include <xpolymorphic_allocator.h>

         ^

C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.41.34120\include\xpolymorphic_allocator.h:10:10: note: in file included from C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.41.34120\include\xpolymorphic_allocator.h:10:

#include <tuple>

         ^

C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.41.34120\include\tuple:969:9: error: static assertion failed: get<T>(const tuple<Types...>&) requires T to occur exactly once in Types. (N4971 [tuple.elem]/5)

        static_assert(false, "get<T>(const tuple<Types...>&) "

It seems that the error message that you are trying to search for might be one of:
C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.41.34120\include\type_traits:131:5: error: static assertion failed: Calling declval is ill-formed, see N4950 [declval]/2.
    static_assert(false, "Calling declval is ill-formed, see N4950 [declval]/2.");
    ^

C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.41.34120\include\tuple:957:9: error: static assertion failed: get<T>(tuple<Types...>&) requires T to occur exactly once in Types. (N4971 [tuple.elem]/5)
        static_assert(false, "get<T>(tuple<Types...>&) "
        ^

C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.41.34120\include\tuple:969:9: error: static assertion failed: get<T>(const tuple<Types...>&) requires T to occur exactly once in Types. (N4971 [tuple.elem]/5)
        static_assert(false, "get<T>(const tuple<Types...>&) "

I think that was recently introduced in 17.11.0. A temporary workaround might be to use 17.10.0 (though we will need to figure out what is going on here).

I think that this might be a bug in the older clang that we use for bootstrapping. It seems to work with the newer compiler. However, that uncovers another bug in build.ps1 :(

Thanks for the quick responses.  I’ll get back to this next weekend  and see if I get further. Is there a way to use the Clang standard library headers when compiling and bypass those provided by Visual C++, or  will that open up a different kettle of fish.
From: Saleem Abdulrasool @.>
Sent: Sunday, August 18, 2024 7:56 PM
To: compnerd/swift-build @.>
Cc: glenrgordon @.>; Author @.>
Subject: Re: [compnerd/swift-build] Problems building for Windows x64 using Visual Studio 17.11.0 (Issue #808)
I think that this might be a bug in the older clang that we use for bootstrapping. It seems to work with the newer compiler. However, that uncovers another bug in build.ps1 :(
—
Reply to this email directly, view it on GitHub https://github.com/compnerd/swift-build/issues/808#issuecomment-2295481125 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AEMY6EPWPG6BZRO6YKEADPLZSE7DZAVCNFSM6AAAAABMWZADA6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJVGQ4DCMJSGU .
You are receiving this because you authored the thread.  https://github.com/notifications/beacon/AEMY6EK4GJGMUSWGIXPRSBLZSE7DZA5CNFSM6AAAAABMWZADA6WGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTUI2JBSK.gif Message ID: @.*** @.***> >

No, not currently; we build the compiler against the windows system libraries and compilers. The problem is that the SwiftCompilerSources is Swift code which falls back to the integrated clang.

Could it help if a 6.0 toolchain like this is used as the pinned (bootstrap) toolchain?

@hjyamauchi we cannot pin the toolchain to 6.0 as the 5.10 toolchain is the agreed upon bootstrap toolchain for the project.

@compnerd Would it make sense to need to pin the VS version like the Swiftlang CIs then?

Well, I'd rather not pin the VS version for main - that needs to be fixed.

fix (pending deployment): https://github.com/swiftlang/llvm-project/pull/9153


Get-OSBuild function is broken. 20H2 is interpreted as a function

Line 965: $OSVersion = 20H2

Added single quotation mark around '20H2' and script is again working.

ApplyDriverPackage.log did not log this error. Had to add some additional error handling.
Write-CMLogEntry -Value "[ApplyDriverPackage]: Dumping last error $Error[0].Exception.Message" -Severity 3

Unfortunately I did not write down the error message that was thrown by $Error[0].Exception.Message.
This can be recreated by running -DriverUpdate -Endpoint "SiteServer" on 20H2 client.

I just ran into the same problem,
thanks for figuring out this!

Fixed in 4.1.2


names/auctions/active?sort=max_bid: Improper sorting

https://aeternal.io/middleware/names/auctions/active?sort=max_bid
[
   {"name":"uiyufw.aet","expiration":32441,"max_bid":"53994045000000004096","winning_bidder":"ak_2e11dB5tGLGokr9z2VaS5tQ4w9bLmw1SQ5Enb3s61ycS1psRg3"},
   {"name":"hjsgcks.aet","expiration":32677,"max_bid":"38630125681875001344","winning_bidder":"ak_DaMGbdj8R45k6aXB8s2QHbVNacscjQvqBCruELQs7izwHX3VX"},
   {"name":"spwesu.aet","expiration":32698,"max_bid":"53994045000000004096","winning_bidder":"ak_bhz7gBWx5vWF6GHwtR6triD1jPxh82UZ6nabkLM1WPZEHpDiN"},
   {"name":"tnznmyh.aet","expiration":32822,"max_bid":"35038662750000001024","winning_bidder":"ak_2a92SdSwUKrBg6tzbsGWPEP1hcxhFgCwBSgR59DvjhiHv4C87x"},
   {"name":"fkvpu.aet","expiration":32834,"max_bid":"91732410000000008192","winning_bidder":"ak_davFvHitLmxR8rBg7mbWXM1UzoPiP9ZnW8UqTK7Gs3h2zEdbd"},
   {"name":"vt.aet","expiration":39013,"max_bid":"352457800000000000000","winning_bidder":"ak_Y3cxakNYYRuxxJAZL1EcWDickXwNUuRLZidbsS6fhDCWnNY1"},
   {"name":"qh.aet","expiration":39089,"max_bid":"352457800000000000000","winning_bidder":"ak_ZWm18Zv5vkgUkedQwUwak1DV8z6PrJ7z1TFKwqpUcsGuqT6Mq"},
   {"name":"zfex.aet","expiration":39093,"max_bid":"208850508599718150144","winning_bidder":"ak_6TUVkQ3vfHy8ENM8yhi9Fwq4WSX5xsb118J4HHg6qkiXRq5TG"},
   {"name":"lr.aet","expiration":47308,"max_bid":"352457800000000000000","winning_bidder":"ak_pvRzXk2RR9m4Buatx2Zf6KxqX6iFsztrE1h1MKa6tY5gtW1MD"},
   {"name":"eqem.aet","expiration":47477,"max_bid":"180412921800857911296","winning_bidder":"ak_zsUdWTvfFwkeD6hq11GzW6k3WjvSV9fF3YpcRvMY9foRwciLA"},
   {"name":"t.aet","expiration":47596,"max_bid":"727848953112094048256","winning_bidder":"ak_26WrdkTaLtPMRpFpqr92qDRGqCT1vx9H3ApyoLdfgtE46p92y4"},
   {"name":"wfc.aet","expiration":47615,"max_bid":"217830900000000000000","winning_bidder":"ak_2AZFiAubaBZtCThqxEHJxTgk2YkyXastc5fXiXxLNmek6c5Hnn"}
]

It looks like it firstly ordered by the length of max_bid field, and then ordered by expiration field. It is expected to have it ordered by max_bid field as numbers.

https://testnet.aeternal.io/middleware/names/auctions/active?sort=max_bid


Business Central API v1.0 PATCH picture BadRequest_InvalidToken

Describe the bug
According the Microsoft Docs, we should be able to update an item picture trough the default API: Update picture
Unfortunately an error is thrown
Could not validate the client concurrency token required by the service. Please provide a valid token in the client request.  CorrelationId:  8dbb4ed0-73d4-45c6-b5b1-efa0e9512563.
To Reproduce
Steps and to reproduce the behavior:

Create a API GET Request on the photographed Item: GET businesscentralPrefix/companies({id})/items({id})

Use ID to retrieve picture url: GET businesscentralPrefix/companies({companyId})/items({itemId})/picture

Use<EMAIL_ADDRESS>to update or create a picture for this item: PATCH businesscentralPrefix/companies({companyId})/items({itemId})/picture({pictureId})/content

Error in response : Could not validate the client concurrency token required by the service. Please provide a valid token in the client request.  CorrelationId:  8dbb4ed0-73d4-45c6-b5b1-efa0e9512563.

Expected behavior
An update or creation of an item picture.
5. Versions:

API Version: v1.0
Business Central: 14.0.36457

Hi! Please take a minute to read the guidelines for this repository https://github.com/microsoft/AL and our collection of frequently asked questions https://github.com/Microsoft/AL/wiki/frequently-Asked-Questions .
As this repository is only for issues related to the AL compiler in latest developer preview environment for Dynamics 365 Business Central. We suggest that you open a support case or file a bug in Collaborate, to ensure that all Business Central users benefit from your catch as soon as possible.
To open a support case, you can:

Open a support request to CSS through the PartnerSource portal
Contact your Service Account Manager (SAM) in your local subsidiary to understand what is included in your contract as of support incident and PAH (Partner Advisory Hours). Your SAM might also direct you "step by step" how to open a support request or how to get credentials, if this is the first time for you or your company

If you file the bug in Collaborate, remember to include steps to reproduce the issue, and the Business Central build number and country version you're using.


Package zed editor

Description of changes
This PR packages the zed editor, https://github.com/zed-industries/zed/.

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[X] Fits CONTRIBUTING.md.

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

zed has already been packaged as of #284010

Interestingly, it turns out that the zed editor has already been packaged (and more elaborately than my attempt by the looks of it) in the by-name directory. (this seems like a 'new' thing - I had expected to find it in 'all-packages.nix', but I'm at least one or more years out of date contributing to nixpkgs)
I only discovered that when the Check pkgs/by-name / check (pull_request_target) CI check failed - if I knew I wouldn't have attempted it myself ;-)
I suppose I simply had only checked with nixpkgs from the nixos-unstable channel rather than the git master branch.
As such I'll close this PR, since it's superfluous.


Bugfix for CurlCurl integrator without a coefficient [curlcurl-nocoef-fix]

Uncovered this problem with one of Mark's unittests.

Merged into next for testing


Ubuntu Touch

I really really wanna have this app for my BQ 5HD phone, guess the Meizu guys wanna have it aswell :)
Is it possible?

Sorry, this is not something I'm interested in doing.

If messenger.com doesn't work on your phone, it won't work if I create an app either (or I'd have to find some fixes, i.e. hacks).
Are you running Flyme OS? Isn't that based on Android? If it is, I doubt that Android apps don't work on it. Try to install Facebook's mobile messenger from the app store.

Okidoki, no im Using an updated Ubuntu Touch, got the BQ Ubuntu edition

Closing


OpenBoson?

There are many reasons why one might want to study the physics of bosonic systems. Such is not the focus of OpenFermion but some limited functionalities for simulating bosons, or systems of interacting bosons and fermions, should be possible to incorporate. For instance, one might want to simulate models of molecules interacting with light which involve electrons and photons. There are also many reasons why one might wish to study systems with electron-phonon coupling, etc. Coupling fermionic systems to a harmonic bath is also common in the context of open quantum systems. If this is a direction which interests anyone, we should discuss implementation ideas here.
One thought is to first make a BosonOperator class. This would be much less onerous if (https://github.com/quantumlib/OpenFermion/issues/43) is first closed, since then one can create the BosonOperator through inheritance. If one restricts the number of bosons which may occupy a single mode then it is also straightforward to provide transforms which map the bosonic operators to QubitOperators. In order to study models of fermion-boson coupling one would need a class that can represent mixed operators. That too will require some thought and discussion. An excellent solution is not immediately obvious.

This paper seems like it should be of interest for this issue: https://arxiv.org/abs/1802.07347

This was closed in #352


UXUI-265 - Creating a new Alert element

What does this PR do? (please provide any background)

This creates an alert which is used to display helpful or factual information usually used as a prompt.

What tests does this PR have?

Tests to check the size, title and purpose have been written in _tests

How can be this tested?

You can run npm test and it will run through all tests for the ui-toolkit

Screenshots / Screencast

What gif best describes how you feel about this work?

Developer Definition of Done/Quality Checklist (for PR author to complete BEFORE code review):

[x] I have checked the contributing document and I'm happy for this to be reviewed.

Software Engineer or Developer review:

[x] I’ve witnessed the work behaving as expected (this could be on the authors machine or screencast).
[x] I’ve checked for coding anti-patterns.
[x] I’ve checked for appropriate test coverage.
[x] I’ve run all the tests locally and they pass.

Software Engineer or project guru review:

[x] I’ve witnessed the work behaving as expected (this could be on the authors machine or screencast).
[x] I’ve checked for coding anti-patterns.
[x] I’ve checked for appropriate test coverage.
[x] I’ve run all the tests locally and they pass.

taking dev

taking other review slot

works for me :+1:

looks good :+1:


Cooperation with graphql-faker

type-graphql is great
Is your feature request related to a problem? Please describe.
Cooperation with graphql-faker
https://github.com/APIs-guru/graphql-faker
Describe the solution you'd like
I want you to add fakerOption
Describe alternatives you've considered
...
Additional context
@ObjectType()
class Recipe {
  @Field({
    fakerOption: {
        fake: {},
        examples: {}
      }
  })
  title: string;
}

↓ generate
type Recipe {
  title: String @fake(type: ...)
}

generate (...) @fake(type: ...)

It's not possible due to #77.
All we can do is to create a @Faker(...) decorator that will accept the options and use faker.js under the hood to return fake data from the resolvers.

Response Thank you

The only problem is that you have to read the type info from

It may be possible with NestP's UsePipes
https://docs.nestjs.com/pipes
import { Query, Resolver, Args } from '@nestjs/graphql';
import { UsePipes } from '@nestjs/common';

@Resolver()
class RecipeResolver {
  private recipesCollection: Recipe[] = [];

  @UsePipes(FakerPipe(Recipe)) // <- ★
  @Query(returns => [Recipe])
  async recipes() {
    return await this.recipesCollection;
  }
}

It may be possible with Nestjs UsePipes

With TypeGraphQL middlewares too:
https://typegraphql.ml/docs/middlewares.html
But the problem is with reading/parsing the GraphQLResolveInfo which is not convenient, but doable 😉

I missed it. I'm sorry 😹

The only problem is that you have to read the type info from

If you think carefully
I think partial Faker is strange
@ObjectType()
class Recipe {
  @Field({
    fakerOption: {
        fake: {},
        examples: {}
      }
  })
  title: string;
}

Is it better to use function units?
@Resolver()
export class RecipeResolver {
  @UseFakerMiddleware([Recipe]) // <- ★
  @Query(returns => [Recipe])
  async recipes() {
    return await this.recipesCollection;
  }
}

We can support different faker modes - global (catch every null/error in resolver and replace with fake data), per type (fake all recipe fields), per query (fake the response object) and per field (fake the title and description fields).


Cache & re-use Klippa results

Resolve https://github.com/opencollective/opencollective/issues/6601
Part of https://github.com/opencollective/opencollective/issues/6865
I had to update S3 to the lastest SDK since one of the features I needed to use (ChecksumAlgorithm) was not working otherwise. I took the opportunity to run the trash scripts; they're working as expected.

Although I wasn't able to test it locally, the code is looking good. Kudos for updating the S3 lib.

Thanks for the prompt review!


[Backport 2.x] Remote Translog Trimming based on remote segment upload and cleanin…

…g older tlog files  (#5662) (#5793)

RemoteFSTranslog Trimming and GC Logic

Signed-off-by: Gaurav Bafna<EMAIL_ADDRESS>
Description
[Describe what this change achieves]
Issues Resolved
[List any issues this PR will resolve]
Check List

[ ] New functionality includes testing.

[ ] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[ ] Commits are signed per the DCO using --signoff
[ ] Commit changes are listed out in CHANGELOG.md file (See: Changelog)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Looks like the changes were merged in with #5792
Please re-open the PR if needed.


[WIP] Use mio instead of tiny-http

cc #27

What's the status on this work? It could be good to combine this with #154 as a new major version (realistically for a major version bump I'd drop rustc-serialize entirely).

The code here is working, but it's not tested.
I was more or less hoping that Rust would support generators soon-ish (not async, just coroutines for parsing), but it looks like we're still far away from them.

What would the process be to get this PR and the Serde PR implemented? These two PRs would be a great boost for the project though I'm sure other concerns come in to play here.

Well the Serde update is ready for review. It has obvious backwards compat issues so there is a question there.

So the problem with this PR right now is that it breaks websockets.
Websockets is a bit tricky because it's touching the topic of asynchronous I/O in Rust.
Other than that, I think there are some minor problems such as HTTP error codes not being returned in some situations (eg. request line too long), and performances could be improved.

The performance gains from this PR are really impressive! Running the hello-world example goes from 19k req/s to 83k req/s (with wrk -t4 -c100 -d10s)
I did notice two issues though:

If a handler panics, the connection hangs. Once the client kills the connection, the cpu usage explodes for all server threads.
Performance is great for the first wrk -t4 -c100 -d10s run, but each subsequent run gets worse and worse. (req/s) 83k -> 41k -> 35k -> 32k -> 27k -> 23k -> 22k -> 19k .... eventually down to zero. The server needs to be restarted to reset performance.

Thanks for the investigation! That's unfortunate.


'cstdio'file not found

Is this a bug report?
Yes
Have you read the Contributing Guidelines?
Yes
Environment:
OS: macOS High Sierra 10.13
Node: 9.3.0
Yarn: 1.3.2
npm: 5.6.0
Watchman: 4.9.0
Xcode: Xcode 9.1 Build version 9C40b
react: 16.0.0 => 16.0.0
react-native: 0.50.3 => 0.50.3
Steps to Reproduce
i integration ReactNative with Existing Apps. Have followed the instructions from here:http://facebook.github.io/react-native/docs/integration-with-existing-apps.html but i get an error,
In file included from/Users/litianpeng/Desktop/aaa/ios/baselib/BaseLib/BaseLibPrefixHeader.pch:22: In file included from ../baselib/BaseLib/BaseLibHeader.h:95: In file included from /Users/litianpeng/Desktop/aaa/ios/baselib/BaseLib/thirdParty/DES/des.h:1: ../Pods/Folly/folly/portability/stdio.h:19:10: fatal error: 'cstdio' file not found.
my project has a submodule->baselib, if i remove the submodule, not the error, but i can't remove it, i can't found any answer.
Expected Behavior
run normal
Actual Behavior
build failed
Reproducible Demo
nothing to Demo

my error, very sorry


About preprocess logic or code for raw dataset

Hi Xueyi!
Thanks for the great work! Would you mind share the code or logic for preprocessing the raw datasets? Now only the processed data i savailable in the project and it's hard to figure out what clip_clean['f1']-clip_clean['f13'] (line 262 in data_loaders/humanml/data/dataset_ours_single_seq.py) means from preprocessed data.
Looking forward to your reply,
Best,
Feiyu

Hi Feiyu,
Sorry for the late response. I've been overwhelmed with final projects and exams recently. The data preprocessing for GRAB is mainly adapted from that used in TOCH. I vaguely remember making some small changes to this script before, but I can't quite recall the specifics. Additionally, I'm unable to quickly locate the preprocessing code I used at the time, as it might be hidden in the part of my code that I haven't organized yet. The preprocessing code for other datasets is also not organized yet. The process is a little bit complicated, and I'm afraid it's difficult to describe clearly in words. After my final term, I will allocate some time to work on this. I kindly ask for your continued patience. Thank you!
Best,
Xueyi


[wip] More pandas

Codecov Report

Merging #200 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #200      +/-   ##
==========================================
+ Coverage   97.33%   97.33%   +<.01%
==========================================
  Files          41       41
  Lines        2513     2516       +3
  Branches      477      478       +1
==========================================
+ Hits         2446     2449       +3
  Misses         35       35
  Partials       32       32

Impacted Files
Coverage Δ

eli5/_feature_importances.py
100% <ø> (ø)
:arrow_up:

eli5/xgboost.py
99.3% <100%> (ø)
:arrow_up:

eli5/sklearn/utils.py
89.55% <100%> (+0.15%)
:arrow_up:


Request: non admin user should be able to open public projects

Hi all,
meanwhile we have a lot of users working with this great tool.
But most of their projects require several members. So a public one is needed.
I would be very helpful if they could create their one public projects.
I hope this is feasible.
Kind regards
muehli

Already requested ;) #521

It's now possible in master branch, there is a new group "project admins" for that.


Refactor

[x] refactor components and structure
[x] cheange gallery
[x] add popup for youtube

Good job!
@aksr666 is a genius


layer-add-surfaces: follow the surface changing during running this a…

…pplication
In most cases, after adding a surface to a layer, even if the size of the surface changes, it does not follow.
While this application is running, always get the configured event to follow the surface changings.
Signed-off-by: Kenji Hosokawa<EMAIL_ADDRESS>

looks good, the implementation is working


fix win loading

replace win path delimiter to linux-like for meta config laoder

Can you provide the error this fails with if this is not done?
Because, this may just be a patch fix. It might be better to use File.separator elsewhere.


[Bug]: Img2Img/Dream leads to unexpected cropping

What happened?
When using Dream or Img2Img, anything not inside the cursor window that is within the layer you're working on gets removed from the canvas. Images on the canvas on another layer than the current one stay in place, however.
This seems to be newish behavior, but it has been awhile since I last used OpenOutpaint. U have replicated this result in both Chrome and Edge. No apparent error messages are visible in the console.
Steps to reproduce the problem

Go to OpenOutpaint
Dream a new image
Move the cursor and dream or Img2Img overlapping the first image.
Accept one of the possible images, and anything outside the placement of the second cursor disappears from the canvas.

What should have happened?
Images outside the cursor on the canvas should not be disappearing.
Commit where the problem happens
https://github.com/zero01101/openOutpaint-webUI-extension@a4a0200f
What platforms do you use to access openOutpaint?
Windows
What browsers do you use to access the UI ?
Google Chrome, Microsoft Edge
Browser Extensions/Addons
None active (using Incognito mode to disable all extensions)
AUTOMATIC1111 webUI Commandline Arguments
--api --xformers --no-half-vae --opt-channelslast
Additional information
No response

disclaimer: apologies for the extended delay, my brain is terrible and you shouldn't expect much from me
yeah, confirming chromium-based browsers have a miserable new disaster with the layering implementation and that i'm not smart enough to have it figured out yet :/

Got the same problem on chrome.
A  somewhat easy workaround is to click one of the previous steps in the history palette then click the last one again. Depending on your steps, you have to go farther back or not :)
Usually choosing a clear canvas or stamp does the trick. When you click on the last step it refreshes everything.
I still love this extension, I have a hard time picturing my SD workflow without it...

seems chromium upstream is really seeming to be the culprit here; if anyone still affected could confirm the findings in https://github.com/zero01101/openOutpaint/issues/268#issuecomment-1848414152 that'd be awesome :)


Breakpoints should render snippet of code line

Similar to how we show snippets in find references we should also show references in breakpoints pane. code snippet         filename : line number alligned to the right
Code snippet should be shown using a mono space font

@isidorn I'm questioning the usefulness of this. In many cases the code of the breakpoint line is not very interesting and does not identify the breakpoint. I would rather show the enclosing function.

@weinand after discussion in the standup I have decided not to show the code snippet. We can leave this open as a feature request and we can see if it generates some interest from users

Closing because we are not planning to implement this within the next 12 months.


add DowncastIntoError::into_inner

This PR adds DowncastIntoError::into_inner, as a way to get the Bound value back if the downcast fails.
The name into_inner was chosen to match std, which has several examples of this e.g. std::sync::PosionError, std::io::WriterPanicked.
Should solve the case in https://github.com/PyO3/pyo3/pull/3820#discussion_r1485697412

🙏 thanks for the quick approval!


test: Add web integration_test

fix #10

https://github.com/koji-1009/flutter_secure_storage/issues/50


CClient: identify good abstraction for arrays

you need to allocate the actual array first before putting it into a struct for consumption by cclient. This is not very nice...

It is implemented in PR https://github.com/iotaledger/entangled/pull/169
Cclient uses utarray macro and char_buffer to allocate the real size as needed.

Closed by #169


TN-1125 followup fix FF scrolling fix

https://jira.movember.com/browse/TN-1125
FF scrolling fix - removing webkit scrollbar css changes

@mcjustin for aesthetics, added this sprint to not show scrolling bar - but should have tested out in all browsers before implementing it.


Issue 531

What this PR does / why we need it:
Fix issue mentioned in the issue 531
Which issue(s) this PR fixes:
Fixes #531
Quality checks

[x] My content adheres to the style guidelines
[x] I ran make test or make e2e-test and it was successful

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Thank you @ybezsonov I will review this


Add typing hinting to functions

Instead of this
def same_suit(self, other_card):
    # code here

Do this
def same_suit(self, other: Card) -> bool:
    # code here

Can't add Card as a hint, in the class that it's being defined in :cry:

Fixed in #27


Time-zones should not impact DateTime (critical)

It works differently on different local time-zones set in the Date/Time settings of OS.
I tested UTC+3 and UTC+1 settings.
Steps To Reproduce
https://deck.net/7c3bd36d71b3a3b54a89f3b72110c78b
public class Program
{
    public static void Main()
    {
	var time = new DateTime(2018, 11, 04, 0, 0, 0, 0, DateTimeKind.Utc);

        time = time.AddDays(-1 * 7.0);

        Console.WriteLine(time.Kind.ToString());

        Console.WriteLine(time.ToString("u"));
    }
}

Expected Result
UTC+3:
Utc
2018-10-28 00:00:00Z

UTC+1:
Utc
2018-10-28 00:00:00Z

Actual Result
UTC+3:
Utc
2018-10-28 00:00:00Z

UTC+1:
Utc
2018-10-27 23:00:00Z

For me it is most critical issue ever reported here.

Also it is strange that we getting the following results:
(DateTime.Now - DateTime.UtcNow).ToString();
// UTC+1: 00:59:59.9990000
// UTC+3: 02:59:59.9990000
Correct result should be: "03:00:00"

The 1-millisecond difference is likely because it's taking >0.5 milliseconds to create the second DateTime object.

The 1-millisecond difference is likely because it's taking >0.5 milliseconds to create the second DateTime object.

Yes it could be.. sounds reasonable.

@geoffreymcgill Any update on this?
My application very depends on calendar and DateTime logic.
So for now it is stuffed by workarounds for this issue.

No reply more than 2 months?

I believe we have this issue fixed. You can test your original Deck.NET sample in our dev instance:
https://dev.deck.net/7c3bd36d71b3a3b54a89f3b72110c78b
We still have a lot more testing to do, but if everything goes well, this fix will be included in the upcoming Bridge 17.8.0 release.

This scenario has been fixed. After another review and final testing, the fix will be included in the upcoming Bridge 17.8.0 release.
You can confirm with the following dev.deck.net sample:
https://dev.deck.net/7c3bd36d71b3a3b54a89f3b72110c78b

A full test over all time zones have been undegone and all looks good, so the fix for this will be available next Bridge release!


Error reporting returns wrong module name in error

Using @google-cloud/error-reporting, and I get this error:
ERROR:@google/cloud-errors: Unable to find credential information on instance. This library will be unable to communicate with the Stackdriver API to save errors.

Really confused me for a second until I realized that we left a hard coded string in the error reporting module :)
cc @ofrobots

Fix here: https://github.com/GoogleCloudPlatform/google-cloud-node/pull/2391


New Sheet - Fifth Season

The Green Ronin-official Roll20 character sheet for Fifth Season RPG

Submission Checklist
Required

[x] The pull request title clearly contains the name of the sheet I am editing.
[x] The pull request title clearly states the type of change I am submitting (New Sheet/New Feature/Bugfix/etc.).
[x] The pull request makes changes to files in only one sub-folder.
[ ] The pull request does not contain changes to any json files in the translations folder (translation.json is permitted)
(I copied over the translations folder from the AGE System sheet this is branched from to keep any existing translations)

New Sheet Details

The name of this game is: Fifth Season RPG

The publisher of this game is: Green Ronin

The name of this game system/family is: AGE System

[x] I have followed the Character Sheets Standards when building this sheet.

[x] This sheet has been made on behalf of, or by, the game's publisher.
[ ] This game is not a traditionally published game, but a copy of the game rules can be purchased/downloaded/found at: <   >
[ ] This sheet is for an unofficial fan game, modification to an existing game, or a homebrew system.

Changes / Description

The Green Ronin-official Roll20 character sheet for Fifth Season RPG

Character Sheet Info Roll20 Internal Use only.


Atlas size arbitrarily set to 9?

Is there a reason why atlas size is hardcoded to be 9?

I assume you're talking about

I was confused by the atlas type in AtlasSprite3dComponent. Are the mesh's cached per texture in the texture atlas? They seem to index on the texture width/height (but different textures in the same atlas can have the same width/height etc.)

If the intention is to create a unique key (which is why I assume MESH_CACHE_GRANULARITY is a float) wouldn't it be better to key on [f32; 9]?

We initially retrieve a mesh from a mesh-key (one of the int arrays) by looking it up here
https://github.com/FraserLee/bevy_sprite3d/blob/main/src/lib.rs#L433C17-L433C89
and later an update system swaps it out if we see the index has changed here
https://github.com/FraserLee/bevy_sprite3d/blob/main/src/lib.rs#L77
For any one combo of mesh size, pivot, and UVs, we have only one mesh (cached and reused). A texture atlas currently uses different UVs to represent each sub-texture - hence the array of mesh keys. There might be an optimization to be made here by swapping to a single mesh without UVs - setting UVs via some other data passed into the shader - then we lose out on being able to use bevy's default shaders. Might be worth looking into at some point, but I haven't personally seen performance even close to bottlenecked by the current system.
Does that about answer your question?

Answers my question - thank you!


2.0 wip Fixes for issue  #1345

It's my first pull request, i'm sorry for any mistake.
This fixes issue  #1345 adding a 36px line-height to .modal-header h3

Closed #1345, and will close this one. We don't want to increase line-height here, but rather the padding, so I've made that change and pushed it.
And you did everything right with your pull request, save for recompiling the LESS files (by running make in Terminal). Either way, thanks for pointing this!


This issue has been opened to transfer labels to another GitHub repo

This issue was moved to ArcGIS/military-tools-dotnet-single-add-in#4


Missing CA cert after restart

First of all, I want to say that this tool looks very useful! However, I was wondering how the CA certs are stored? I am encountering the problem that when I restart the NodeJS application, my redirects no longer work because the certificate chain is incomplete. I have the same issue when I use the Docker container.
This is what I get after restarting the application and fetch the certificate with OpenSSL:
openssl s_client -showcerts -servername domain.tld --connect domain.tld:443 </dev/null
CONNECTED(00000003)
depth=0 CN = domain.tld
verify error:num=20:unable to get local issuer certificate
verify return:1
depth=0 CN = domain.tld
verify error:num=21:unable to verify the first certificate
verify return:1
depth=0 CN = domain.tld
verify return:1

All ca certs are stored in sqlite database.
const dbFile = path.join(__dirname, '../.certs/db.sqlite');
When restarted, it should resume serving HTTPS with these certificates, so I'm not entirely sure why it happened to you.

Thanks for your reply!
These certificates are indeed also served after a restart. However, when I convert the BLOB data from the database to text, I only see the private key and cert (before and after a restart). The CA/intermediate cert is not included, which causes it to fail for me.

Oh, sorry. I think I misread the whole topic. Let's start again.
No, we don't intermediate cert. I wasn't though I need to save CA cert until recently.
https://github.com/willnode/forward-domain/blob/cc804729effb7ad28eb1a4432466e937ec3f78a9/src/db.js#L149-L162
The cert here contains the certificate and the CA. To save storage I do conversion to DER/binary format, but I only save the x509.raw here. The CA file you're looking for is in x509.ca, it doesn't get saved here.

I'm not entirely understand why a CA is needed I think it definitely breaks "chain of trust". Does it will break some browsers?

Yes, current behavior only store CA in memory. This is a bug since I moved the storage to sqlite around three months ago. Luckily I don't restart the service over the time.
I'll refactor current db to store CA.


Installation Instructions [Linux Debian]

I wanted to run some of my own tests on the eye reasoner on my machine.
I was trying to run the ./install.sh script - but haven't got the swipl command installed. Is there a recommended place to install this from since it doesn't appear to be available from the apt package manager.
System Details:
PRETTY_NAME="Debian GNU/Linux 11 (bullseye)"
NAME="Debian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"

I'm happy to PR a set of Linux installation instructions once I am able to get this working on my machine.

You could install swipl as per https://www.swi-prolog.org/build/PPA.html
Another way to run eye locally is via https://hub.docker.com/r/bdevloed/eye/


ISO 639-2 language code

To prevent translation conflicts, it is recommended to use ISO 639-2 language codes. For example, words such as 'no' and 'or' may have different translations in different languages.

Thank you very much for your advice, I will take it into consideration


Extension install scripts fail with empty variables

The sudo -u ec2-user -i EOF pattern used in the install-lab-extension sample fails because the main shell resolves the variable $EXTENSION_NAME (to blank) before it's passed to the subshell in the script.
As noted here, we need to escape $ when using this pattern.
I have a PR ready to fix this for both the install-lab-extension and install-nb-extension samples - will submit after recording the issue.
...but I think this might affect other samples too?

I just did a quick check and think this will also affect:

install-conda-package-all-environments
install-conda-package-single-environment
install-pip-package-all-environments
install-pip-package-single-environment
install-server-extension
persistent-conda-ebs
set-git-config

Hi athewsey,
Thanks for submitting this issue.  Indeed, it would appear that we need to quote the "heredoc delimiter" with quotes in order to disable variable expansion entirely inside of the heredoc.  Escaping $ with $ would also work as well (no strong preference to either).
Feel free to submit a PR for the others, otherwise we will fix this as soon as possible.

I agree that, for the majority of our scripts that don't take any params from the parent shell, quoting the heredoc delimiter is more readable/less overhead than escaping each use of a variable :-)
Will raise a PR imminently to have a crack at the rest and revert the extension installation ones to quoted delimiter

Awesome, thank you very much!


Dynamic mask and trace chunk size and dataType

Yeah, after noticing that usability issue, we've been doing the same on the matnwb side modeled after h5py's approach to guessing chunk size. It looks like our approaches are similar. It would not be a problem to keep your implementation if you prefer it to matnwb's

Sounds good, I'll wait until that is merged to see about incorporating it here.

Changed so that it now saves as /processing/ophys/ImageSegmentation/PlaneSegmentation1, etc. as this appears to most closely track the NWB schema (https://nwb-schema.readthedocs.io/en/latest/format.html#planesegmentation). We'll leave the cell-extraction method in the description for now until algorithm field is added to the NWB standard.

You can technically name the PlaneSegmentation whatever you want, but I
think PlaneSegmentation1, etc. is a good idea.
On Sun, Apr 5, 2020 at 6:18 PM Biafra Ahanonu<EMAIL_ADDRESS>wrote:

Changed so that it now saves as
/processing/ophys/ImageSegmentation/PlaneSegmentation1, etc. as this
appears to most closely track the NWB schema (
https://nwb-schema.readthedocs.io/en/latest/format.html#planesegmentation).
We'll leave the cell-extraction method in the description for now until
algorithm field is added to the NWB standard.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/schnitzer-lab/nwb_schnitzer_lab/pull/6#issuecomment-609493829,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAGOEERJ6NFM7KUESAF7YELRLD7TFANCNFSM4L4RRROQ
.

--
Ben Dichter, PhD
Data Science Consultant


Feature / Support Request - Slideshow

This issue is a kind of both:

Feature request
Question / support request

Description
Is there any possibility or example to implement a Slideshow with this package? I have tried this with a controlled component, but when I set the isZoomed property to false on one image and to true on another image, the open and close animations come into play, doesn't look very nice.
So my Question: Is there any way to open an Image Slider/Colorbox with this beautiful effect?

Thanks for the fast answer!
I am struggling to get this to work in e.g. jsfiddle, how can I add react-medium-image-zoom inside the fiddle?
But nonetheless, here is my Code. I have added some buttons for closing the slideshow and a unfinished (does not watch out for last image) next button to test the behavior:
import React, { Component } from 'react';

// 3rd Party
import ImageZoom from 'react-medium-image-zoom';

class ImageGallery extends Component {
  state = {
    allowZoom: true,
    countdown: 0.5,
    imageStates: this.props.images.map(() => false),
    showControls: false
  };

  handleUnzoom = () => {
    this.setState({
      allowZoom: false,
      imageStates: this.props.images.map(() => false),
      showControls: false
    });

    setTimeout(
      () => this.setState({ allowZoom: true }),
      this.state.countdown * 1000
    )
  };

  handleZoom = index => {
    if (this.state.allowZoom) {
      const imageStates = this.state.imageStates;

      imageStates[index] = true;

      this.setState({
        allowZoom: false,
        imageStates,
        showControls: true
      });
    }
  };

  handleNext = () => {
    const imageStates = this.state.imageStates,
      nextImageIndex = imageStates.findIndex(image => image === true) +1;

    this.setState({ imageStates: this.props.images.map((e, index) => index === nextImageIndex), });
  };

  // @todo implement throttle
  scrollHandler = () => {
    this.handleUnzoom();
  };

  componentDidMount() {
    window.addEventListener('scroll', this.scrollHandler);
  }

  componentWillUnmount() {
    window.removeEventListener('scroll', this.scrollHandler);
  }

  render() {
    return ([

        {this.props.images.map((item, index) =>

 this.handleZoom(index)} className="gallery-item">
            <ImageZoom
              image={{
                src: item.small,
                className: 'img',
              }}
              shouldReplaceImage={false}
              shouldRespectMaxDimension={true}
              zoomImage={{ src: item.big }}
              isZoomed={this.state.imageStates[index]}
              onUnzoom={() => this.handleUnzoom()}
            />

        )}

,

        {this.state.showControls &&

 this.handleUnzoom()}>close

 this.handleNext()}>next

prev

        }

    ]);
  }
}

export default ImageGallery;

Mounting Point:
ReactDOM.render(
        <ImageGallery images={[
           {"small": "https://via.placeholder.com/150", "big": "https://via.placeholder.com/500"},
           {"small": "https://via.placeholder.com/150", "big": "https://via.placeholder.com/500"},
           {"small": "https://via.placeholder.com/150", "big": "https://via.placeholder.com/500"}
        ]} />,
        document.querySelector('#app')
      );

CSS:
#imageZoomControls--close{
  position: fixed;
  z-index: 1050;
  top: 50px;
  left: 50%;
  color: black;
}

#imageZoomControls--next{
  position: fixed;
  z-index: 1050;
  top: 50%;
  right: 50px;
  color: black;
}

@rpearce It would be very nice if I could solve this issue by the end of the year. But nobody's life depends on it ;)

@Daveiano got it. It's on my to-do list, along with completely refactoring this entire project :)

@rpearce Oh well :D
I will also try to look at this again when I got some time. Thank you very much for taking the time!

@Daveiano Update: after Xmas! Sorry for the wait!

Don't stress yourself, merry Xmas!

@Daveiano could you describe what sort of slideshow you're trying to do, exactly? Is it like a normal one that sits on the page and cycles through them? What is supposed to be happening? Is it supposed to be like a Bootstrap slider but with this image zoom effect? The example provided, after looking over the code and trying it out, isn't quite clear to me.

Here is webpage I am working on (work in progress, it's not in production), there is the exact code I posted in action.
http://www.fuer-angie.net/der-haselhof
If you click on the first image (with the horses) and the on "next", the next image (the dog) shows up and disappears. What I am doing if you press on next, I remove the isZoomed state from the horse image and add it to the dog image.
What I want is a Colorbox (sorry I said slideshow), for example like http://simplelightbox.com/, but with the opeeing animation of this project.
I hope it is more clear now what I want?

I managed to get this to work:
My problem was the onUnzoom function which was triggered when the isZoomed state changed on the images. i have removed the part onUnzoom={() => this.handleUnzoom()} from my <ImageZoom /> Components.
You can see a working version under the link I shared in the previous post.

Ah! That's great news. In the next version I'm working on, I'll consider including an option to disable the animation (may make the slideshow work better).

This would be a great addition! But just when changing the image, not on opening.
And thank you for your support!

Any updates on this? I also implemented something similar to Daveiano. It would be good to disable the animation!

@javialeung Honestly, I haven't put much thought into it. I think I know how to make this happen, so I'll reopen this while I think about it!

Thanks for the update! I appreciate the support for this.
The slideshow I have works great with the image zoom it's just the animation when changing images is causing a not so great user experience.

@javialeung what I'm going to look at this weekend is seeing if we can provide an animation config flag (some people might not want the animation for accessibility reasons sometimes) that will set the transition-duration to 0 or remove the transition-duration property entirely.

@Daveiano @javialeung Looks like I already did this! As you can see in the readme's API section, you can pass a transitionDuration, which will disable the transition.
You can pair this with the controlled component and listen to the document for arrow keys in order to make this happen.
As a bonus, I created an example in the Storybook examples for you! https://rpearce.github.io/react-medium-image-zoom/?path=/story/react-medium-image-zoom--image-gallery-slideshow-style-images

@rpearce Thank you very much for response!
I will look into this in the next few days and give feedback! Thanks a lot.


The Living Bible

It may be a copyright issue but is it possible make a JWPUB version of The Living Bible? Thank you

Hi @cienypico
Thank you for your enquiry.
First, I believe this version is still under copyright.
Second, it's a very imprecise paraphrase and would not contribute to a better knowledge or deeper understanding of the Scriptures.


Allow passing in appId to facebook components

@chrislopresto @lukemelia thoughts on this pattern?
Question:
If there are several facebook components in an app and only some of them are passed an appId, the ones that aren't will use the default appId from env, metatag, or global. Do we want load to return a new promise if the appId changes between components calling load()? (ie: as implemented in this PR with currentIdIsUpdated)

Actually talked about this with @seamus-oconnor , probably not a good idea


Compile issues

All of the syntax,
      return (
           Show Deleted Files           <input             type="checkbox"             id="chkShowDeleted"             defaultChecked={this.props.options.showDeletedFiles ? "checked" : ""} />
       );
for example gives javascript compile errors about Uncaught SyntaxError: Unexpected token < using Google Chrome Browser but used others as well with same issue.

@pbllms The README.md should probably be updated but you need to either include the JSX in-browser transformer (take a look at JSXTransformer-0.12.2.js in the example index.html file) or run the JavaScript source through the JSX preprocessor before using it.

@CtrlC-Root just gave you write access in case you get bored and want to tinker

Yes, we saw that but are using HTTPS and it causes issues with mixed content so we use this location instead,
https://cdnjs.cloudflare.com/ajax/libs/react/0.12.2/JSXTransformer.js
And we still get the same issues including it and react.js before s3commander.js

@electroniceagle Thanks. It looks like I'm going to be using s3commander at my current job so I'll probably be opening pull requests for new features here and there.
@pbllms I just checked out the contents of the master branch, made it available through S3 static hosting, and loaded the index.html file. It seems to work out of the box for me in Google Chrome. I must be missing something about your situation because it should be working.

@pbllms I'm going to close this issue. If you're still experiencing a problem feel free to comment here or open another issue.


utc problem!

This project seems to use cron, consider using chrono::Local instead of chrono::Utc, maybe it's works better.

Please check version 0.10.0 and the builder API, if it works better for you?


SSR Data are loaded only after refresh (SSR BUG related with useAsyncData - so every composable)

Environment

Operating System: Darwin
Node Version:     v18.13.0
Nuxt Version:     3.1.1
Nitro Version:    2.1.1
Package Manager<EMAIL_ADDRESS>Builder:          vite
User Config:      debug, ssr, css, build, vite, modules, runtimeConfig
Runtime Modules:  ()
Build Modules:    -

Describe the bug
Fetching data from Apollo server works only after refresh.
On Page loading, the setup function doesn't fire the request to the Apollo server, but it waits until a refresh is performed.
The request then appear in the console network, and everything works fine (on page loading the request/fetch doesn't exist).
This happens only when the ssr option is set to true in nuxt.config (by default it is set to true). The behavior changes, and the fetch is performed also on page load when the ssr option is set to false (clearly).
Expected behaviour
I would expect that the first time I load a page, the request is normally performed to the apollo server, in this way I can populate the page with the data.
Reproduction
Someone in December opened an issue and tagged it as BUG, unfortunately the issue was closed just before the end of the year without a real resolution. For reference the following is the link to the issue:
https://github.com/nuxt-modules/apollo/issues/452#issue-1451729190
Additional context
I tried to investigate a bit the issue, and I noticed that under the hood, the module uses the useAsyncData (form the nuxt composable). This is amazing but it's worth probably point out that (the yellow alert in particular):

Maybe the problem is just here??
Logs
No response

The way in which I "hacked" this is issue is the following:
<script setup>
  const query = gql`
    query getCategories {
      categories {
        data {
          id
          attributes {
            name
          }
        }
      }
    }
  `
const { data, refresh } = await useAsyncQuery(query)
if (!data.value) {
    refresh()
  }
</script>

So I am conditionally refreshing the data if they are indeed null. This trick allow me to perform the SSR :)
Maybe it's worth allowing an automatic refresh option when data are null and contemporarily we are using SSR.

@Dinuz can you share apollo config in nuxt.config.ts and @nuxtjs/apollo version?
i used
node v18.12.1
@nuxtjs/apollo": "5.0.0-alpha.5 "
nuxt": "^3.1.1"
nuxt3": "3.1.2-rc.0-27922414.cb0860b"
export const getUsersQuery = gql`
  query users(
    $limit: Float
    $orderBy: [UserOrderByInput!]
    $page: Float
    $where: UserWhereInput
  ) {
    users(limit: $limit, orderBy: $orderBy, page: $page, where: $where) {
      pageInfo {
        page
        limit
        currentPage
        totalCount
      }
      docs {
        id
        firstName
        lastName
        email
        username
        roles
        avatar
        status
      }
    }
  }
`

/**
 * query data my user
 * if @data null return login
 */
const variables = {
  limit: 10,

  page: 1,
}

const { data } = await useAsyncQuery(getUsersQuery, variables)
if (!data.value) {
  navigateTo('/user')
}
const users = JSON.parse(JSON.stringify(data.value)).users

mine still return normal.

@devhoangkien sure (what do you mean still return normal??),
node version 18.13.0
"@nuxtjs/apollo": "^5.0.0-alpha.5"
"nuxt": "^3.1.1"
my nuxt.config is super basic:
export default defineNuxtConfig({
  debug: true,
  ssr: true,
  modules: ['@nuxtjs/apollo',],
  apollo: {
    clients: {
      default: {
        httpEndpoint: 'http://localhost:1337/graphql',
      },
    },
  },
})

I was having the exact same issues here but ensuring I was on beta-5 of nuxt apollo and nuxt 3.1.2 and everything began working as expected.

Context
I use a Laravel Lighthouse backend and this only occurs to me when auth is required.

My nuxt.config.ts
// https://nuxt.com/docs/api/configuration/nuxt-config
export default defineNuxtConfig({
  modules: ["@nuxtjs/apollo"],
  apollo: {
    clients: {
      default: {
        httpEndpoint: "http://myapp.test/graphql"
      }
    },
  },
});

Behavior
If I protect the query (requiring auth)
It does not load on initial load (like after refresh). Only when I manually press a button to request the data when the page has been loaded.
If I remove the protection from the query (no auth required anymore)
Everything works as intended. It does work on initial load and after refresh.

Visual example of behavior

Removing the guard makes it work for ssr, but leaves the query unprotected.

It appears when the server is making the request it does so without auth. But I'd like to be able to protect my queries and have them loaded on initial load when authenticated.
Other

I noticed useLazyAsyncQuery documentation shows useAsyncQuery instead of useLazyAsyncQuery in the example.
Using useQuery throws a 500 with message "Unauthenticated" which I assume is intended behavior if unauthenticated, but in this case I am authenticated.

I have a similar issue as @timyourivh, but in my case it works on refresh(SSR) and not on the client side. I am using the apollo:auth hook inside plugins/apollo.ts like so:
export default defineNuxtPlugin((nuxtApp) => {
    const { value } = useCookie("session_token");
    nuxtApp.hook("apollo:auth", ({ client, token }) => {
        token.value = `Bearer ${value}`;
    });
});

This works fine for SSR requests (like on refresh), but returns Bearer undefined for client side requests, like navigating between routes.
How can I get the cookie to work for client side requests? Any ideas?


Fix button ui when disabled

Summary
In the login flow, the styles for the buttons in disable mode were missing..
Ticket Link
N/A
Release Note
NONE

going to merge this


Quickfix to add package to pubspec.yaml.

If I write import "package:foo/foo.dart";, and there is no foo package in my package configuration, could we have a quick-fix to add it to the pubspec.yaml file (and run pub get).
(Make it a dev_dependency if the file is not in lib/.)
Is that possible, or must quick-fixes be in the same file?
An alternative would be a pub command like pub depend foo which adds a foo dependency to the pubspec.yaml file, but that requires the user to leave the editor.

Quick fixes are allowed to modify files other than the one in which they are invoked. You can see this, for example, by referencing, in a part file, an identifier that is not yet imported and selecting the fix to add an import. The import is correctly placed in the library file.
The harder question, in my mind, is what text to add. More specifically, which version constraint to use.
Quick fixes work by sending back a description (the menu item) and the edits to apply to implement the fix. That means that we have a limited amount of time in which to compose the edits before it impacts the UX.
My concerns are that

we likely won't be able to communicate with pub.dev to get a list of available version within that timeframe, and
even if we could we won't be able to know which versions are compatible with the version constraints on other packages within that timeframe.

I love this idea, but I'm not immediately seeing a way to implement it.

You could use any. Then Pub would probably pick the newest version compatible with all the other constraints. Users can change that if they need a specific version.
It does sound like pub is the right place to solve the problem more deepply. They can find the newest version of the package that is compatible with either the versions in pubspec.lock or find a new solution for everyone.

Yes, pub could solve the problem more deeply. But it might be more convenient to have a quick fix to add the any version and then have pub tell you when the lower bound of a package's constraints can't be used (because of the other dependencies) and hence could be tightened.


i18n(ko-KR): update configuration-reference.mdx

Description (required)

update configuration-reference.mdx
#9081
#9094

Related issues & labels (optional)

Closes #
Suggested label:

Lunaria Status Overview
🌕 This pull request will trigger status changes.

Learn more
By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.
You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

Locale
File
Note

ko
reference/configuration-reference.mdx
Localization changed, will be marked as complete.

Warnings reference

Icon
Description

🔄
The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.