Feature request : pulse on dots.

Hi,
Sometimes, I do not want to cut a shape, but just make a pulse without moving the head (e.g. if I want to make the smallest possible hole in a sheet of black paper to make a pinhole camera). I currently do it manually by

puting a segment starting where I want to make each hole in the dxf
selecting the segment
moving the head to top/left of the segment
sending a short pusle

Would it be hard to automate this in MeerK40t using DXF Points and adding a "pulse duration for dots" parameter for each color (in addition to speed and PPI that would still be used for non-dots) ?
I attache a .dxf file with points (renamed in .dxf.txt because github won't accept .dxf).
Best Regards.
points.dxf.txt

In the console there's a command called pulse. It's not a mode but you can do pulse 100 to fire your laser in one spot for 100 ms without moving. You can also do bind space +laser in console and then you can move your laser around with the WASD keys and hit space to fire the laser in one spot. It would be bound by default but letting cats burn down your house is a bad idea.  You could also bind a key to do pulse 100 or whatever value fits your need.
It is possible to code this up if I had a series of points, though there's nothing in there currently since this would be a different sort of operation. It's not strictly enough to add in a pulse duration for dots though there is one of those in navigator to let you fire pulses from there. Since you can only do this pulse duration trick in default/rapid mode and most of the other operations run in the sort of compact/program mode.
There's also not strictly a dots structure in svg, and those are the geometry data structures I'm currently using. I'm not sure how often this would get used and it might be more reasonable to do this as a sort of one-off buried function. That or just as a separate operation type.

I've got the first step. DXF Point objects show up now. The issue is they are closed moves. Path('M0,0z') it's a technically valid path and is just a point. I do not know how you could move it since it's 0x0 in size. If you try to laser these it will actually go there in an engrave or whatever. But, it's 0 pixels long, and consequently doesn't do anything. It goes there and then goes to the next point. There's nothing to dwell at that point... at least not yet.

And I added the rest of the dots stuff.
You'll need the latest pull of 0.7.0, but if you type dots -s <time-in-ms> in console it will make a dot operation. This will exclusively classify dots, which are literally 0 length position objects. These will dwell for the set amount of time.

Also, rather than do all this you could have done very tiny rectangles, and set a passes value to adjust for time. I think this is what the one person who requested this before ended up doing, though that might mess with your workflow.
--
I gave dots an icon, and classification scheme, and some coverage for how they should work. But, I kept them mostly hidden. They don't need much in the way of typical operation setting, so I just sort of blanked that out. They are normal operations so they will get saved like normal operations. And anything that is a dot will classify in them (unless it qualified for another classification first, eg red and red cut is above them).
You could safely leave dots in your operations, they can only classify a dot. If you put something not a dot in there. It will go to the first point and dwell their for the allotted time.

I managed to patch in the correction for moving the Dot Operation objects and having it still work.
https://www.youtube.com/watch?v=gu5YoVJGlj8

This exists in the latest versions.


Fix node pattern tutorial ... matcher section

... actually matches zero or more elements, not "one or more":
> pattern = NodePattern.new('(send nil? :sum $...)')
> pattern.match(RuboCop::ProcessedSource.new('sum(1,2,3,n)', 2.5).ast)
=> [s(:int, 1), s(:int, 2), s(:int, 3), s(:send, nil, :n)]
> pattern.match(RuboCop::ProcessedSource.new('sum()', 2.5).ast)
=> []

Before submitting the PR make sure the following are checked:

[x] Wrote good commit messages.
[-] Commit message starts with [Fix #issue-number] (if the related issue exists).
[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[-] Added tests.
[-] Added an entry to the Changelog if the new code introduces user-observable changes. See changelog entry format.
[x] The PR relates to only one subject with a clear title
and description in grammatically correct, complete sentences.
[x] Run bundle exec rake default. It executes all tests and RuboCop for itself, and generates the documentation.

Good catch! 🙇


Add an API for extensions to resolve variables in configurations

I would like to have a way for extensions to resolve strings containing variables like ${workspaceFolder}, similarly to how this is done for tasks and other configuration.
I am trying to write an extension that hooks into a script which may be named differently in different projects. I will search for the script in a default location, but I've added a setting to allow a workspace to override the location as needed.
My code looks something like this:
// package.json
...
"contributes": {
  "configuration": {
    "type": "object",
    "title": "My Extension",
    "properties": {
      "myext.entryPoint": {
        "type": "string",
        "default": ""
      }
    }
  }

import * as vscode from 'vscode';
import * as path from 'path';

function getEntryPoint() {
    const config = vscode.workspace.getConfiguration('myext');
    const entryPoint = config.get<string>('entryPoint');

    if (entryPoint) {
        return entryPoint;
    } else {
        // If the setting doesn't override the entry point,
        // assume it is in the workspace folder with a default name.
        return path.join(vscode.workspace.rootPath, 'the_script.py');
    }
}

If I then create a workspace with these settings...
// .vscode/settings.json
{
  "myext.entryPoint": "${workspaceFolder}/a_different_script.py"
}

...I see that config.get('entryPoint') returns exactly that string without resolving ${workspaceFolder}, so I need to somehow resolve that variable. I have enough information to do a search and replace and resolve it on my own, but it would be much more convenient if I had some way to ask VS Code to resolve it, either by giving some form of access to variableResolver.ts or having WorkspaceConfiguration resolve the variables when I get them.

fyi @weinand @alexr00

I think a fundamental problem is: why are we interpolating variables in "task.json" and "launch.json" but not in "settings.json".
Placing the substitution burden on clients that read configurations is IMO the wrong approach because it gives the impression that variables are supported in settings everywhere (which is not the case).
/cc @bpasero

I do think we need to be careful with variables in settings. I've had a request for allowing input variables in settings, which I don't think makes sense (when should a setting that requires input be resolved??) .

Related https://github.com/Microsoft/vscode/issues/2809

I also think it would be nice if variable interpolation was supported in settings.json, but I can see how the questions of when some of them should be resolved would be an issue. Maybe more limited support for settings.json, such as ${workspaceFolder} which should be constant.

we're having a very similar issue to this:
our debugger extension is going to parse a configuration and propagate the debug requests to language-specific debugger extensions (vscode-python, vscode-cpptools).
for example, for the following configuration
{
    "name": "debug",
    "type": "newtype",
    "request": "launch",
    "target": "${file}"
},

the target ${file} points to an XML file that contains the actual launch requests. We need to actually parse that file and generate debug requests to the other debuggers.
Since we need access to vscode.debug.startDebugging(), this needs to take place inside vscode.DebugConfigurationProvider.resolveDebugConfiguration() (not the debug adapter). For this reason, we need an API to resolve VS Code variables manually (inside the extension's context).

@kejxu please file a new issue for your request as your use case is sufficiently different from resolving variables in settings.

@kejxu please file a new issue for your request as your use case is sufficiently different from resolving variables in settings.

thanks for the pointer! created https://github.com/microsoft/vscode/issues/79518

/duplicate of https://github.com/microsoft/vscode/issues/46471


bug in np.full / lax.full for DeviceArray wrapped scalars

If you pass in a jax-wrapped scalar as the fill-constant value to np.fill, it breaks, e.g.:
np.full((1,1), np.array([1])[0])

this hits the condition in lax.full:
 elif isinstance(fill_value, xla.DeviceValue):
    return FilledConstant(convert_element_type(fill_value, dtype), shape)

no matter what dtype is, the convert_element_type result is still a DeviceArray, then
this line in lax.FillConstant:
class FilledConstant(xla.DeviceConstant):
  __slots__ = ["fill_value"]

  def __init__(self, fill_value, shape):
    assert type(fill_value) is onp.ndarray

wants the fill value to be an onp ndarray instead.
I'm not too certain about the type logic here to make a PR confidently.

Thanks for catching this! We just needed an onp.asarray there to turn the DeviceValue back into a regular ndarray. (We might instead be able to allow FilledConstants to have DeviceValues inside, but this seems like the simpler option.)


problem with UART baudrate

Hi
After flash for bouth line logging and at, baudrate transmite is 76800.  Not like in esp32_instruction

The default baud rate of AT command is 115200

AT+UART_DEF? returned
+UART_DEF:115200,8,1,0,1
AT+UART_CUR? returned
+UART_CUR:115201,8,1,0,1
AT+UART_CUR=115200,8,1,0,1 returned
OK
Again
AT+UART_CUR? returned
+UART_CUR:115201,8,1,0,1
But still baudrate transmit is 76800. May i doing something wrong or this is some bug?
What should i do to change baudrate transmit?
I tried both firmware 1.1.2 from https://www.espressif.com/en/support/download/at with the same results. I've got sparkfun esp32 thing module. I tried also on my custom board with esp32

hi yea my fault. i've got 26MHz on board. When i compiled it with changed parameters in make menuconfig. Everything works ok. It was litle confused because every thing looks ok only uart works on this baud.


JSONDecodeError

First the tool was working fine and after some time it is showing the issue tried remove and installing again but the problem is same.

Hello!
Thanks for reaching out to me.
Apologies for any inconvenience caused.
Due to very high resource consumption that API goes to sleep sometimes to ensure my bills don't go off the charts haha.
It must be working alright now.
Thanks for your understanding!
Lmk if you have any other issues.


Contest start time is wrong (possibly because of timezone).

The contest start time is 7:00 PM IST

Issue is still there, might be fixed by https://github.com/nobleknightt/contestsdb/commit/3186cc2065e63a2db0a542657473111e0ab7c463


[1.10.2-<IP_ADDRESS>2] Energy upgrade has no effect on electrolytic separator

Mekanism version: <IP_ADDRESS>2
Forge <IP_ADDRESS>7
Electrolytic separator (processing water) is using 400 J/t running without any upgrades.
Inserting any amount of energy upgrades does not change the reported energy usage in the GUI.  After inserting 8 upgrades, it still reports using 400J/t.
Not happening in any other machines or factories I've tried.  Speed upgrades work normally in the separator.

Intended.

Then the tool-tip in the upgrade window on the separator should not indicate energy upgrades are supported, and the machine should not accept them.

The Energy Upgrade still boosts energy capacity.

Why not split the energy upgrade into speed and capacity upgrades? That will stop this and add an additional mechanic.  :)

Does anyone really use the increased energy storage feature of Energy Upgrades?  That feature could be cut and I don't think many people would notice.
Why do mods increase power buffers anyway?  If its something about increased power usage, then why isn't that feature on the Speed Upgrades or a separate upgrade instead?

I think that it makes perfect sense the way it is. Capacity and efficiency seem to both be needed numerically if you max out on speed upgrades.
My main complant is the discoverability of the separator being an exception to half the effect of the energy upgrade.
An update on the wiki would help, and some way to discover it in the ui in game would be really nice, maybe a little more text when the energy upgrade is selected.


cmake: patch namelink regression

Motivation for this change
see:

https://github.com/NixOS/nixpkgs/issues/106329
https://github.com/awslabs/aws-c-common/issues/734

Things done

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

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

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

@GrahamcOfBorg build nix

Also fixes gdcm and itk (which vendors gdcm) which were affected similarly to #106329.

it was hinted that 3.19.2 may be released soon, but that doesn't seem to be the case. Merging


[BUG]The response time of the cluster is extremely long after upgrading to ubuntu 22.04

Rancher Server Setup

Rancher version: 2.6.4
Installation option (Docker install/Helm Chart): RKE1

If Helm Chart, Kubernetes Cluster and version (RKE1, RKE2, k3s, EKS, etc):

Proxy/Cert Details: none

Information about the Cluster

Kubernetes version: v1.21.6
Cluster Type (Local/Downstream): Downstream (vSphere)

If downstream, what type of cluster? (Custom/Imported or specify provider for Hosted/Infrastructure Provider):

Describe the bug
Yesterday I updated nodes from ubuntu 20.04 > 22.04.
I had network problems and I got a solution from HERE.
But the whole cluster is extremely slow.
I get a response from kubectl get nodes command in 1 minute or more.
The servers have enough free memory, CPU resources and disk space.
To Reproduce

Result
Expected Result

Screenshots

Additional context

I upgraded kubernetes version also and that seems to be fixed it. Sorry for noise.


cvxopt issues on El Capitan

Just wanted to document a problem that cvxopt seems to have with Macs running El Capitan. On running one of the tests, test_bootstrap (__main__.TestDriversMethods), I get:
ImportError: dlopen(~/anaconda/envs/py27/lib/python2.7/site-packages/cvxopt/lapack.so, 2): Symbol not found: _dgesv_
  Referenced from: ~/anaconda/envs/py27/lib/python2.7/site-packages/cvxopt/lapack.so
  Expected in: /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBLAS.dylib

The issue cvxopt/cvxopt#45 documents what I think is the same problem, and it may be due to my use of anaconda. I'll try some fixes and see if I come up with a way to get it working.

It appears that the issue was that I had installed cvxopt via conda install cvxopt instead of pip install cvxopt. Once I install with pip, all the ImportErrors disappear. This should be mentioned in the documentation somewhere (especially since @kmrudin seems to have experienced similar issues with Enthought Canopy).

Is there some way to include these kinds of subtleties in the dependencies? As of devlop/c34ba68a590e5ad8d1adf7cf7ca840e246770c77, requirements.txt doesn't list cvxopt as a dependency.

cvxopt is a dependency of cvxpy, which is an optional dependency for pyGSTi (it's only used to compute the diamond-norm I believe), which I think is why it's not in requirements.txt. As far as including the subtlety of using pip versus conda, I don't know of a way. If it installs via setup.py, I believe any dependencies listed in there are installed using pip.

Just for reference:
Documentation for cvxpy indicates that mixing pip and conda installs can cause errors (especially if pip install --upgrade is used when the package was originally installed with conda).
In #6, the conda-installed version of cvxopt was preventing computing the diamond norm. Specifically, the version 1.8.1 py_35 needed to be updated to 1.8.1  py35_blas_openblas_203  [blas_openblas]  conda-forge or downgraded to 1.7.1 py_35. For me, the pip version worked as well.


Tuya zigbee lcd temperature/humidity sensor not working

Hi,
I am tryimg to install a tuya zigbee lcd temperature sensor. But it does add as a unknown device.

Any help welcome
Kinds regards,
Dennis

Added to next update.


URL Cleanup

This commit updates URLs to prefer the https protocol. Redirects are not followed to avoid accidentally expanding intentionally shortened URLs (i.e. if using a URL shortener).
Fixed URLs
Fixed But Review Recommended
These URLs were fixed, but the https status was not OK. However, the https status was the same as the http request or http redirected to an https URL, so they were migrated. Your review is recommended.

[ ] http://a.host (UnknownHostException) with 1 occurrences migrated to:
https://a.host (https result UnknownHostException).
[ ] http://c.host (UnknownHostException) with 1 occurrences migrated to:
https://c.host (https result UnknownHostException).
[ ] http://compose.docker.io/ (UnknownHostException) with 1 occurrences migrated to:
https://compose.docker.io/ (https result UnknownHostException).
[ ] http://d.host (UnknownHostException) with 1 occurrences migrated to:
https://d.host (https result UnknownHostException).
[ ] http://f.host (UnknownHostException) with 1 occurrences migrated to:
https://f.host (https result UnknownHostException).
[ ] http://g.host (UnknownHostException) with 1 occurrences migrated to:
https://g.host (https result UnknownHostException).
[ ] http://h.host (UnknownHostException) with 1 occurrences migrated to:
https://h.host (https result UnknownHostException).
[ ] http://www.puppycrawl.com/dtds/suppressions_1_1.dtd (404) with 1 occurrences migrated to:
https://www.puppycrawl.com/dtds/suppressions_1_1.dtd (https result 404).

Fixed Success
These URLs were switched to an https URL with a 2xx status. While the status was successful, your review is still recommended.

[ ] http://12factor.net/ with 2 occurrences migrated to:
https://12factor.net/ (https result 200).
[ ] http://cloud.spring.io/spring-cloud-consul/ with 1 occurrences migrated to:
https://cloud.spring.io/spring-cloud-consul/ (https result 200).
[ ] http://cloud.spring.io/spring-cloud-netflix/ with 1 occurrences migrated to:
https://cloud.spring.io/spring-cloud-netflix/ (https result 200).
[ ] http://cloud.spring.io/spring-cloud-zookeeper/ with 1 occurrences migrated to:
https://cloud.spring.io/spring-cloud-zookeeper/ (https result 200).
[ ] http://example.com with 1 occurrences migrated to:
https://example.com (https result 200).
[ ] http://martinfowler.com/bliki/CircuitBreaker.html with 1 occurrences migrated to:
https://martinfowler.com/bliki/CircuitBreaker.html (https result 200).
[ ] http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html with 2 occurrences migrated to:
https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html (https result 200).
[ ] http://www.oracle.com/technetwork/java/javase/downloads/jce-6-download-429243.html with 2 occurrences migrated to:
https://www.oracle.com/technetwork/java/javase/downloads/jce-6-download-429243.html (https result 200).
[ ] http://www.oracle.com/technetwork/java/javase/downloads/jce-7-download-432124.html with 2 occurrences migrated to:
https://www.oracle.com/technetwork/java/javase/downloads/jce-7-download-432124.html (https result 200).
[ ] http://www.oracle.com/technetwork/java/javase/downloads/jce8-download-2133166.html with 2 occurrences migrated to:
https://www.oracle.com/technetwork/java/javase/downloads/jce8-download-2133166.html (https result 200).
[ ] http://pivotal.io/platform-as-a-service/migrating-to-cloud-native-application-architectures-ebook with 2 occurrences migrated to:
https://pivotal.io/platform-as-a-service/migrating-to-cloud-native-application-architectures-ebook (https result 301).
[ ] http://plugins.jetbrains.com/plugin/6546 with 2 occurrences migrated to:
https://plugins.jetbrains.com/plugin/6546 (https result 301).
[ ] http://projects.spring.io/spring-boot with 2 occurrences migrated to:
https://projects.spring.io/spring-boot (https result 301).
[ ] http://eclipse.org with 1 occurrences migrated to:
https://eclipse.org (https result 302).
[ ] http://eclipse.org/m2e/ with 2 occurrences migrated to:
https://eclipse.org/m2e/ (https result 302).
[ ] http://www.springsource.com/developer/sts with 1 occurrences migrated to:
https://www.springsource.com/developer/sts (https result 302).

Ignored
These URLs were intentionally ignored.

http:///foobar with 1 occurrences
http://default with 1 occurrences
http://foo with 7 occurrences
http://foo_underscore with 1 occurrences
http://foobar with 1 occurrences
http://host1:8080 with 2 occurrences
http://listener with 1 occurrences
http://localhost with 4 occurrences
http://localhost:8888 with 1 occurrences
http://myservice/path/to/service with 1 occurrences
http://noRetry with 1 occurrences
http://s1-1:8080 with 5 occurrences
http://stores with 1 occurrences
http://stores/stores with 3 occurrences
http://testservice with 1 occurrences

Closed with some polish via 700a11a4ec09645c1a44bb5eeec80a4519506837


Definition Request: cookie-session

Please add definitions for: https://github.com/expressjs/cookie-session

#4656

@horiuchi , yes,  I DIY this definitions.


Add the osleague.tools exporter plugin

This plugin allows users to export their completed leagues tasks both in CSV format, and a format compatible with https://www.osleague.tools which is a very handy website to track progression!

I talked with the developers over at osleague.tools and there's another plugin in development with better integration with the website. So I'm closing my PR in favur of that upcoming one.


Feature/auth0 setup implementation

Description
Started the implementation of auth0
Created application with auth0 in auth0.
Installed auth0/auth0-react
Created a env.sample file with the needed domain and client for auth0
added the files into the env.
In index.js imported authProvider then got the domain and client from enviroment.
Wrapped the application with auth0Provider.
Video Link
Loom Video
Trello Link
Auth0: Starting of implementation thats includes creating a single page application in auth0, installing auth0, adding env files, and wrapping the application with auth0provider
Type of change
Please delete options that are not relevant.

[x] Installed auth0/auth0-react
[x] added env.sample file
[x] wrapped the application with auth0Provider

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have removed unnecessary comments/console logs from my code
[x] My changes generate no new warnings
[x] I have checked my code and corrected any misspellings
[x] No duplicate code left within changed files
[x] Size of pull request kept to a minimum
[x] Pull request description clearly describes changes made & motivations for said changes

Good job aligning the environment variables and bringing things up through the index.js file. Nice.


Support Lambda@Edge functions

Lambda@Edge functions do not allow Environment Variables. This change
skips creation of the SERVERLESS_ALIAS env var for any functions listed
as Lambda@Edge functions in cfg below.
I'm certainly open to other implementation approaches, but it'd be great
to be able to use this plugin in combination with Lambda@Edge. If you agree to the PR, I'll add README updates as well.
custom:
  lambdaEdgeFunctions:
    - platform-spa-origin-request-lambda-edge

Coverage increased (+0.1%) to 74.419% when pulling 23c4e2e74fb782328859eb0e29e20bdb668799fa on sonofbjorn:feature/support-lambda-edge into e0215d2694b743567e58a48746129b33af13cc01 on HyperBrain:master.

Hi @sonofbjorn ,
thank you for the PR. I agree that edge functions should be supported and highly appreciate a solution.
I've read the AWS documentation and I assume that we do not need a separate custom array to declare the edge functions separately.
According to http://docs.aws.amazon.com/lambda/latest/dg/API_CreateFunction.html#SSS-CreateFunction-request-Runtime we should be able to distinguish any edge function by it's Runtime value. If it is an edge function the runtime should be set to nodejs4.3-edge. So the best solution imo should be to check for
if (resource.Type === 'AWS::Lambda::Function' && _.endsWith(resource.Runtime, '-edge')) { ... }

Checking for the -edge suffix should be more future proof than just checking for the exact available values.
What do you think and could you try if that works?

Absolutely, I'll give it a try today. Agree that this approach is much cleaner. Thanks for the quick response!

Nice job on adding this capability.
One potential issue I found, though it could be a typo in the AWS docs, it looks like the edge functions do support node 6.10. Here is the AWS docs for their tutorial and they say to specifically use node 6.10.
Maybe the API doc hasn't been fully updated yet, worth a shot to see if it supports nodejs6.10-edge as well.

@mikelax Good catch. @sonofbjorn , could you do an experiment with nodejs6.10-edge too, to confirm that it is supported by AWS?

@HyperBrain I've done a bit of testing... Here's what I've found.
I was able to create a lambda with the nodejs4.3-edge runtime, but it appears this runtime is deprecated (the error below appears in the Lambda console and NO RUNTIME is selected).

The Edge Node.js 4.3 runtime is no longer supported. We recommend you migrate your functions that use Edge Node.js 4.3 to a newer runtime as soon as possible.

When attempting to create a lambda with the nodejs6.10-edge runtime, I receive the following error during deploy (note that nodejs-4.3-edge doesn't appear in this list either, though it passes validation).

1 validation error detected: Value 'nodejs6.10-edge' at 'runtime' failed to satisfy constraint: Member must satisfy enum value set: [java8, nodejs, nodejs4.3, nodejs6.10, python2.7, python3.6, dotnetcore1.0]

As @mikelax points out from the AWS docs, they clearly state to select node 6.10 runtime when creating a Lambda@Edge function. I suspect that when these functions are replicated to the edge locations, they're using nodejs6.10-edge, but it doesn't appear possible to select that option when creating them.
At this point, I don't see a great way to distinguish a Lambda@Edge function from a standard Lambda, outside of additional configuration.

I also dug a bit to find any information. It seems that there is currently no working CloudFormation support for Lambda@Edge. See: https://forums.aws.amazon.com/thread.jspa?threadID=262327
The plugin as workaround looks also quite fragile to me as it circumvents CF and leaves things out-of-control. Before taking any decision here we should try to get a clear statement, if or if not, it is supported by CloudFormation. I'm sure that CloudFormation (and maybe Serverless) must handle edge lambdas differently. Do edge lambdas work in Serverless without the alias plugin?
Regarding the validation error: Serverless uses the CloudFormation REST API call validateTemplate() to validate the generated CloudFormation template. It seems that this validation call fails here. To be sure we should check the Serverless code if there is some additional check for the runtime that might lead to a failure-

Agreed on all counts. Serverless does not support Lambda@Edge (L@E) out of the box currently, nor does CloudFormation. There have been a couple of issues raised regarding CF support for L@E, but I haven't seen any response from AWS on the topic. At this point, I'm leaning toward addressing this issue with a L@E plugin instead. You can decline this PR.
Just for reference, there's already an existing plugin, but it assumes the L@E function is in the same CloudFormation stack as the linked CloudFront distribution. In my use case the L@E function is standalone and can be triggered by many CloudFront distributions. Thanks you for the time and thoughtful response, and great work on this plugin!

Closed as discussed


ARROW-3059: [C++] Remove namespace arrow::test

Depends on PR https://github.com/apache/parquet-cpp/pull/487

Codecov Report

Merging #2436 into master will increase coverage by 17.71%.
The diff coverage is 97.64%.

@@             Coverage Diff             @@
##           master    #2436       +/-   ##
===========================================
+ Coverage   69.01%   86.73%   +17.71%
===========================================
  Files          61      239      +178
  Lines        3234    42607    +39373
===========================================
+ Hits         2232    36954    +34722
- Misses        928     5653     +4725
+ Partials       74        0       -74

Impacted Files
Coverage Δ

cpp/src/arrow/memory_pool-test.h
100% <ø> (ø)

cpp/src/arrow/io/io-hdfs-test.cc
17.44% <0%> (ø)

cpp/src/arrow/test-common.h
100% <100%> (ø)

cpp/src/arrow/util/compression-test.cc
100% <100%> (ø)

cpp/src/arrow/ipc/ipc-read-write-test.cc
99.04% <100%> (ø)

cpp/src/arrow/test-util.h
74.8% <100%> (ø)

cpp/src/arrow/util/lazy-test.cc
100% <100%> (ø)

cpp/src/arrow/memory_pool-test.cc
100% <100%> (ø)

cpp/src/arrow/compute/compute-test.cc
99.54% <100%> (ø)

cpp/src/arrow/array-test.cc
100% <100%> (ø)

... and 307 more

Continue to review full report at Codecov.

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

Arrow's CI does not build the Parquet unit tests, which I presume are the only things affected by this

Ah, I see, thanks.


Block->API: Mind The Annotation ID

This is probably not something we'll have problem with, but I just noticed it while reading some code.
During Block-to-API conversion, when we produce the annotation ID to choose which annotation layer we're modifying, seems like we only take into account the url attribute. Meaning that other annotations like code blocks and colors and what not would be mapped only taking type into account, which may or may not produce unexpected result.
So, creating this issue to keep track of this in the future.

Is this issue still happening?

Our annotation code has since been re-written


Not all available AWS regions work

I can configure bees up in the following regions:
us-east-1
us-west-1
us-west-2
eu-west-1
ap-southeast-2
ap-southeast-1
ap-northeast-1
sa-east-1
But for the following regions:
us-east-2
ca-central-1
eu-central-1
eu-west-2
ap-northeast-2
ap-south-1
I get this error each time:
Connecting to the hive. Traceback (most recent call last):   File "/usr/local/bin/bees", line 6, in <module>     main.main()   File "/usr/local/lib/python2.7/site-packages/beeswithmachineguns/main.py", line 270, in main     parse_options()   File "/usr/local/lib/python2.7/site-packages/beeswithmachineguns/main.py", line 210, in parse_options     bees.up(options.servers, options.group, options.zone, options.instance, options.type, options.login, options.key, options.subnet, options.bid)   File "/usr/local/lib/python2.7/site-packages/beeswithmachineguns/bees.py", line 176, in up     raise Exception("Invalid zone specified? Unable to connect to region using zone name") Exception: Invalid zone specified? Unable to connect to region using zone name
Any ideas?

The version of boto probably needs to be updated in order to be aware of the latest region names. How did you install bees? Did you pull it from master or did you install it through pip?

I just ran pip install https://github.com/newsapps/beeswithmachineguns/archive/master.zip, so I will try updating the boto version and try again.

@paulmarsicovetere  any update?

Hi,
Same here, eu-west-3 doesn't work. Fresh install.


Elo Score Calculation & Surrounding Controller Logic

#16
Merge conflicts should be limited to the tests created.

Yep- that was me- whoops!
Woop woop 🙌 nice work, will review after yoga 🧘♂

Yep- that was me- whoops!
Woop woop 🙌 nice work, will review after yoga 🧘♂

Hahah all good! Realised after I committed them that'd you'd made a few of the same ones 30mins prior facepalm

Fixes #16


Remove obsolete mock dependency

Remove the dependency on mock package, as the test suite uses only the builtin unittest.mock module.
Checklist:

[ ] Add tests that demonstrate the correct behavior of the change. Tests should fail without the change.
[ ] Add or update relevant docs, in the docs folder and in code.
[ ] Add an entry in CHANGES.rst summarizing the change and linking to the issue.
[ ] Add .. versionchanged:: entries in any relevant code docs.
[ ] Run pre-commit hooks and fix any issues.
[x] Run pytest and tox, no tests failed.

The CI failures don't seem related to my change.

Thanks

Thanks!


TypeError: create_curvilinear_collision_checker(): incompatible function arguments.

I am running "compute_reachable_set.py", but I got the following errors:
TypeError: create_curvilinear_collision_checker(): incompatible function arguments. The following argument types are supported:
1. (arg0: List[List[numpy.ndarray[numpy.float64[2, 1]]]], arg1: Dict[int, List[List[numpy.ndarray[numpy.float64[2, 1]]]]], arg2: geometry::CurvilinearCoordinateSystem, arg3: float, arg4: int, arg5: bool, arg6: bool) -> collision::CollisionChecker
It seems that the function "create_curvilinear_collision_checker()" got the wrong function arguments. But I do not know how to fix this.

Hey, which numpy version are you using? It is a known problem that the package only works with numpy<2.0.

I have numpy == 1.26.4. I guess it is not caused by the numpy version.
I use the combination of following packages, this problem has gone as well, like the last issue. Therefore, the problem might come from the mismatch between the following packages. Now, all codes are running correctly with the following combination:
commonroad-drivability-checker 2023.1
commonroad-io                  2024.2
commonroad-reach               2024.1.2
commonroad-route-planner       2024.2.0
By the way, first build "commonroad-drivability-checker", then build "commonroad-reachable-set", last just "pip install commonroad-route-planner==2024.2.0".
Finally, all works! Thanks for you help!


Providing an updated changelog

I have no idea what changed between versions in the last 6 months.
The commits in github doesn't seems to be much helpful, and https://github.com/jonan/ForkHub/blob/master/CHANGELOG.md didn't change for quite a while.
So, an updated file, or the correct section in the Play Store should be filled.

ForkHub is only 4 months old, and I haven't created an official release yet because I intended to merge my changes back to the official app. That's why all the changes are marked as unreleased in the CHANGELOG.
Unfortunately merging changes back doesn't seem to be possible, so I plan on creating the first official release of ForkHub this week. After that, all the releases will be tagged and the changelog will be more precise.

Great !
I wasn't aware of how old ForkHub was.
And seeing changes as unreleased while there were releases on the Play Store was weird.
Now I understand :)


Rsync fails with mkstemp permission denied when using sudo to become another user

Deployer version: 7.3.1
Deployment OS: Debian Bookworm

config:
  become: "user"

hosts:
  example.com:
    deploy_path: ~
    remote_user: "deployer"

tasks:
  upload:
    - upload:
        src: "cachetool.phar"
       dest: "{{deploy_path}}"

Cache tool can be downloaded via:
curl -sLO https://github.com/gordalina/cachetool/releases/latest/download/cachetool.phar

On the server side, there is a user within a group deployment.
Home directories are only writable by the user itself, so neither deployer can write to user nor user can write to deployer home directory.
The deployer user is in the deployment group as well.
The sudoers has:
deployer ALL=(%deployment) NOPASSWD: ALL

[example.com] run rsync '-azP' '-e' 'ssh '\''-o'\'' '\''StrictHostKeyChecking=no'\'' '\''-A'\''' '--rsync-path' 'sudo -H -u user rsync' 'tools/cachetool.phar' 'deployer@example.com:~'
[example.com] err rsync: [receiver] mkstemp "/home/deployer/.cachetool.phar.J81Ii0" failed: Permission denied (13)

Looks to me as if rsync has already executed sudo and became user but somehow wants to create an upload temp file in deployer home directory.

I guess its trying to create that tmp file in deployer home as it connects with deployer@example.com:~, looks like it has to be an absolute path to the user home directory instead - but not sure what would be the best way to actually determine that 🤔


Q&A Topics

continuing on from #10 - each of the topics relates to a directory in QnA part of the repo (just like the original SupplyChain questions came from the SupplyChain directory). So SBOM, OpenC2, etc are directory names that are peers to SupplyChain. If the user selects OpenC2, then an OpenC2 question if popped up just like Supply Chain question was popped up. For this story, answering correctly just returns you to unpaused game.

I believe this is implemented already in 0.3.6


fixes loading speed issue by moving config reads away from View composer ...

… and into the Livewire component
Fixes #238
As reported in the above issue, there is a speed issue when using View::composer.
I haven't found the root cause of it and why this call is so slow, but by moving the configuration checks away from View::composer and into the Modal livewire component, the problem is resolved.

hey @PhiloNL, let me know if this has a chance of making it into the main branch :)

Thanks @arukompas 🙌

@arukompas, one question: Have you tested if this works if the values are false? The view currently checks if the variables are set, so I think it will try to get the file contents of null because the variables are defined at all times. Would you mind checking this? 😄

hey @PhiloNL , thanks for accepting this! 🎉
As per Laravel docs, the @isset helper also checks whether it’s null:

@arukompas perfect; thanks for confirming 🙌  tagging a new release.


[GSSOC'23] Documentation for create_repo.py file

I'd like to write the documentation for the create_repo.py file. @sahil-sagwekar2652 , please assign this issue to me under GSSOC'23.

Hi I do like to contribute. Assign me this issue under label GSSoC23.

Hey there @SwastikGorai . Could you elaborate a bit more about what changes you are proposing?

I'll write the docs for the code. Like, what exactly the lines do and why are those needed.


Error while creating parameter file

Does this occur consistently?
Repro steps:

Action: azurerm-vscode-tools.selectParameterFile
Error type: Error
Error Message: "f:\vsc\azuredeploy.json" does not appear to be an Azure Resource Manager deployment template file.
Version: 0.11.0
OS: win32
OS Release: 10.0.19041
Product: Visual Studio Code
Product Version: 1.47.0
Language: en

Call Stack
Object.<anonymous> extension.bundle.js:3:349982
fulfilled extension.bundle.js:3:347122

Been trying to find out how to reproduce this bug (see #838).  Are these the steps you took?

create new file
save as .json file (while the file is still empty)
Use "arm!" snippet or copy a template from elsewhere
Before saving the file, attempt to select/create a parameter file

Thanks!

This should be fixed in the next release.


Update handwriting_recognition.py

Added missing e in provides.

I've fixed the other two files as well now 🙂

Thanks! Before we can merge the PR, you'll need to sign the CLA as well: https://cla.developers.google.com/clas

CLA is signed


docs: split building and deploying doc

Checklist

[x] commit message follows commit guidelines.
[x] website builds and runs in production - for information on how to test locally go here.

Description
Split up the "building and deploying" doc into " building", "deploying" and "appsody operator" docs. I tried to keep the content largely the same in this PR. Future PRs will be made to improve the actual content.
For easier reviewing:

[ ] "Building" doc is taken from the original "building and deploying" doc. I only added the first 2 paragraphs and the last line
[ ] "Deploying" doc is the original "building and deploying" doc with the "building" and "appsody operator" sections removed from it. I only made changes to the # Getting ready to deploy your Appsody project section, and the last sentence in the ### Deployment via the Appsody Operator section
[ ] "Appsody Operator" doc is directly taken from the original "building and deploying" doc with no additional changes

Related Issues
Related to https://github.com/appsody/website/issues/359

You'll need to add redirects, changes to the sidebar yaml and any direct website refs also need updating...

I have added one redirect which is the main one. I think we can add redirects for anchor links that we are aware have been used externally. However, we will probably have to accept some breakages as we can't redirect every anchor header. I've also updated the sidebar yaml and any  direct website link references

Sandy, I dreamt about the docs last night (sad I know!). Is there a link from the deploying doc to the operator docs as I didn't notice one yesterday? There should be something to show users that there is more information in Reference otherwise we can't expect users to find it.

@helenmasters haha sorry to hear about that. There is a link to the operator doc at the end of the ### Deployment via the Appsody Operator section


Only depend on requests[security] and ordereddict for Python 2.6

Fixes #2055

Can you verify that we don’t just randomly import ordereddict anywhere? I have no idea why this is a thing to be completely honest. Maybe pathlib related. We don’t support 2.6 so we can axe anything related to it.
requests[security] is a bit more nuanced. Without it resolution can be much slower and I believe it was added specifically to handle certificate issues on 2.6/2.7 but I’ll have to go back and double check

(Sorry I’m on mobile or I’d look now)

I dug into this and it seems like we can axe this as you point out


Proposal: Windows-friendly build scripts

Quick summary (as I have the tendency of writing walls of text): I'm having troubles running this repo's setup and tests in Windows. I also have a Mac that I can test so I'm willing to make pull requests to fix any issues that come up.
I'm creating this issue to show an example of what some the issues are and what the changes would look like... and also because I read the contributing guide which told me to:

Open a GitHub issue before doing significant amount of work.

.scripts/npm-x-for-all-packages.sh
I cloned this repo and ran npm run setup which ended with this result:
> @ internal-install-all C:\Development\forks\cyclejs
> .scripts/npm-x-for-all-packages.sh install

'.scripts' is not recognized as an internal or external command,
operable program or batch file

I'm using bash emulation on windows (using cmder) so I attempted to run the script with sh .scripts/npm-x-for-all-packages.sh install.
This actually ran, but failed in a different way (and even if it had of worked it still wouldn't have worked on regular windows command prompt).
This is what I got:

So this led me to create a node equivalent version of the npm-x-for-all-packages.sh, here's a link -> npm-x-for-all-packages.js
Then I modified the package.json:
"internal-install-all": "node .scripts/npm-x-for-all-packages.js install",

This works for me in windows command prompt, git-bash and also mac terminal.
So with that out of the way I attempted to:
node .scripts/npm-x-for-all-packages.js run test

This works fine on mac, but fails on windows.
Which led me to...
cyclejs/base/package.json
I decided to try and get all the scripts in base working and ran into a couple of issues:

"prelib" script

"prelib": "rm -rf lib/ && mkdir -p lib/",

This can be fixed using rimraf and mkdirp, so I added these packages to the root package.json's devDependencies so that they can be used across the other packages.
 "prelib": "../node_modules/.bin/rimraf lib/ && ../node_modules/.bin/mkdirp lib/",

Which led me to another windows issue:
><EMAIL_ADDRESS>prelib C:\Development\forks\cyclejs\base
> ../node_modules/.bin/rimraf lib/ && ../node_modules/.bin/mkdirp lib/

'..' is not recognized as an internal or external command,

This is an issue with npm scripts and windows:
https://github.com/npm/npm/issues/13789
However if you change the script to this:
  "prelib": "node ../node_modules/rimraf/bin.js lib/ && node ../node_modules/mkdirp/bin/cmd.js lib/",

It will work correctly on command prompt, gitbash, and mac terminal.
So I went and updated the rest of the scripts in the base package.json.
Which looks like this:
  "scripts": {
    "lint": "node ../node_modules/tslint/bin/tslint -c ../tslint.json src/**/*.ts",
    "prelib": "node ../node_modules/rimraf/bin.js lib/ && node ../node_modules/mkdirp/bin/cmd.js lib/",
    "lib": "node ../node_modules/typescript/bin/tsc",
    "premocha": "npm run lib",
    "mocha": "node ../node_modules/mocha/bin/mocha --compilers js:babel-register test",
    "test": "npm run lint && npm run mocha",
    "test-ci": "npm run test",
    "prebrowserify": "npm run lib",
    "browserify": "node ../node_modules/browserify/bin/cmd.js lib/index.js -t babelify --standalone CycleBase -o dist/cycle-base.js",
    "uglify": "node ../node_modules/uglify-js/bin/uglifyjs dist/cycle-base.js -o dist/cycle-base.min.js",
    "predist": "node ../node_modules/rimraf/bin.js dist/ && node ../node_modules/mkdirp/bin/cmd.js dist/",
    "dist": "npm run browserify && npm run uglify",
    "readme": ":",
    "changelog": "node ../.scripts/update-changelogs.js ${PWD##*/}",
    "preversion": "npm test",
    "version": "npm run dist && npm run readme && npm run changelog",
    "postversion": "git add -A && git commit -m \"release(${PWD##*/}): v$(cat package.json | ../node_modules/.bin/jase version)\" && git push origin master && npm publish",
    "release-patch": "false",
    "release-minor": "npm --no-git-tag-version version minor",
    "release-major": "npm --no-git-tag-version version major"
  },

So basically if these kind of changes seem alright to make, I'd be happy to go through all the packages one-by-one and get them all working on windows.
Note that I'm still pretty new to github etc so I'm not sure what the best way would be to orchestrate all the changes: many small pull requests or fewer larger ones? so any advice there would be appreciated.

This problem had been already raised.
But the problem is in NPM. I just have made a PR to Yarn to fix this.
As workaround you may fix your fork of NPM/Yarn or I even just fix it manually in npm installation (as long as I don't install npm often it is ok)
For yarn I hope it will be fixed, maybe then in NPM. Someday, somehow =)

Hi, thank you for taking your time to send us this issue. I'm sorry but our bash scripts are serving us very well, and it's not worth the time trying to support Windows. See this issue https://github.com/cyclejs/cyclejs/issues/384
I recommend installing Ubuntu in a virtual machine. It's free.

Thats fair enough thanks, I understand not wanting to mess with around with the bash scripts - especially since you're not likely to be building or managing the overall repo on a windows machine anyway.
In that case I agree that the internal-install-all stuff and so on is not so important and its not a big deal to just manually npm install in the relevant folders that you care about.
However build scripts out of the way, it would still be beneficial to be able to run and test the packages locally on windows.
Assuming we just wait for the relative path bugs that @whitecolor mentioned to be fixed in npm / yarn, that leaves a couple of simple changes that could be made to get the tests working on windows:

Replacing mkdir -p with mkdirp and rm -rf with rimraf in scripts like "prelib" would fix that issue.
Adding some notes to CONTRIBUTING.md to make a note of the issues with windows eg:

not officially supported but if you want to run the tests then here is how you might go about it...

npm install manually
run at least version of npm / yarn (that has hopefully been fixed)
alternatively run in a VM, bash for windows etc....

OR alternatively...
Could take it a step further (and I mentioned it in my previous message), it is possible to modify package.json scripts to work around the npm/yarn relative path bug in the meantime by running them with node directly.
That would get the tests etc working in the meantime, then when npm / yarn is fixed the change can be reverted and simply leave a note for contributors saying: 'run at least this version of npm/yarn for it to work on windows'.
    "lint": "node ../node_modules/tslint/bin/tslint -c ../tslint.json src/**/*.ts",
    "prelib": "node ../node_modules/rimraf/bin.js lib/ && node ../node_modules/mkdirp/bin/cmd.js lib/",
    "lib": "node ../node_modules/typescript/bin/tsc",
    "premocha": "npm run lib",
    "mocha": "node ../node_modules/mocha/bin/mocha --compilers js:babel-register test",
    "test": "npm run lint && npm run mocha",
    "test-ci": "npm run test",
    "prebrowserify": "npm run lib",
    "browserify": "node ../node_modules/browserify/bin/cmd.js lib/index.js -t babelify --standalone CycleBase -o dist/cycle-base.js",
    "uglify": "node ../node_modules/uglify-js/bin/uglifyjs dist/cycle-base.js -o dist/cycle-base.min.js",
    "predist": "node ../node_modules/rimraf/bin.js dist/ && node ../node_modules/mkdirp/bin/cmd.js dist/",
    "dist": "npm run browserify && npm run uglify",

I'd be happy to make submit pull requests for changes myself but again it's up to you whether you view this as a worthwhile effort, so if you are still not keen just let me know and I'll leave it be.
Cheers


Service doesn't have a com.docker.compose.service tag

I've been trying to find the solution to this issue for 3 hours now and I can't seem to make it work. The example works fine, but when I try to host my own setup, it composes fine with the docker ecs compose up, but then when I try to access its ip address using docker ecs compose psit gives this message:
service arn:aws:ecs:us-east-1:885192933549:service/server-BackendService-1RGWIKLFI55RB doesn't have a com.docker.compose.service tag

This is my docker-compose.yml:
version: '3.8'
services:
  frontend:
    restart: always
    x-aws-pull_credentials: arn:aws:secretsmanager:us-east-1:{pretend-this-is-my-id}:secret:myname-randomnumbers
    image: fracturx/oceanic:frontend
    ports:
      - '80:80'
    depends_on:
      - backend
  backend:
    restart: always
    x-aws-pull_credentials: same as one in frontend
    image: fracturx/oceanic:backend
    ports:
      - '8000:8000'

The frontend service's image is a react build made with node 14.5.0 alpine and served using nginx:alpine base image.
Dockerfile (for frontend):
FROM node:14.5.0-alpine as build
WORKDIR /app
COPY package*.json ./
RUN npm install
COPY src ./src
COPY public ./public
RUN npm run build

FROM nginx:alpine
COPY --from=build /app/build/ /usr/share/nginx/html
COPY web/nginx.conf /etc/nginx/conf.d/default.conf

Backend service's image is express api
Dockerfile (for backend):
FROM node:14.5.0-alpine
WORKDIR /server
COPY package*.json ./
RUN npm install
COPY . ./
EXPOSE 8000
CMD ["npm", "start"]

I have made sure to tag and push the latest builds to my private docker hub repo and using the default context and composing locally on my machine works fine.

Thanks for reporting this, I'll look into this later this week.

in the meantime, please can you confirm you opted-in for the "new ARN and ID format" on AWS account settings? This is a requirement so we can tag services - should have been detected when creating services, probably buggy.

i did not have that enabled while i was experiencing that issue, testing with it on now.

alright it works fine, but how would i configure the backend to be on a private subnet?

This should now be detected as you create context with https://github.com/docker/ecs-plugin/blob/master/pkg/amazon/sdk/sdk.go#L59
I'm surprised CloudFormation stack deployment doesn't fail as we request creation of a service with tags but the latter are not supported, need to double check


Can default_text have option to be a function? And then pass the filename as a parameter we can use?

This plugin is amazing... just what I needed!
One thing I find myself wanting is to create default_text dynamically via a function. Is this something you would consider? allowing to define as a function and then providing function parameters of the filename and also would be nice if could provide the type of gitpad (project, branch, daily note, or current file) so that we can do some conditional logic based on the type of gitpad. Thoughts?

@GitMurf Thanks! Glad you liked this plugin
That sounds like a nice idea. Maybe we could just use the opts for similar to what we did for the title where you can just pass the title parameter when toggling notes
Maybe something like:
local date_filename = 'daily-' .. os.date('%Y-%m-%d.md')
require('gitpad').toggle_gitpad { filename = date_filename, on_attach = function() end, default_text = function() end, title = 'Daily Notes }


Build script lacks success confirmation for win10 host

Operating System Version: MacOS 10.13.6
Provider (VirtualBox/VMWare): VMWare Desktop
Vagrant Version: 2.1.2
Packer Version: 1.2.5
Is the issue reproducible or intermittent? Reproducible
Description of the issue:
Build script does not return 'Good news! win10 was built successfully', even though the build process has seemingly completed successfully.
Attempting to bring up the logger host using Vagrant
Good news! logger was built successfully!
Attempting to bring up the dc host using Vagrant
Good news! dc was built successfully!
Attempting to bring up the wef host using Vagrant
Good news! wef was built successfully!
Attempting to bring up the win10 host using Vagrant
Something went wrong while attempting to build the win10 box.
Attempting to reload and reprovision the host...
[returns to terminal]

After the reload/reprovision, did the build complete successfully? A vagrant build log for Win10 would be super helpful here. It's possible something went wrong or didn't complete, thus aborting the build and explaining the lack of a successful build message. I'll try to reproduce this.


explore options for dealing with non-secret input values

Currently, all resources in the input stack are created with placeholder values and the deployer tool populates them with the actual values.
This is useful as a way of identifying whether a stack has been updated, but the naive update behavior with this model would result in the input values being reset. This is probably not what we want.
One option would be to read the values before updating the inputs stack and re-overwriting them afterwards.
This creates the potential issue of what happens if something tries to read those values during this gap.
I'm also not sure how Secrets Manager will react to an update: will it attempt to decrypt the value to check it against the provided value to know if this is an update or will it simply override always? Or something else?
Another option would be to add the non-secret values as parameters to the inputs stack. This would make stack updates simpler, but would require stack updates if we want to change the non-secret values in a sane way. It also does not address the issue of secret values.

Closing down project: #52


Provide a from_json overload for std::map

This overload is chosen only when BasicJsonType::string_t
is not constructible from std::map::key_type.
Currently, converting a map to json treats it as an array of pairs.
fixes #1079

Pull request checklist
Read the Contribution Guidelines for detailed information.

[x]  Changes are described in the pull request, or an existing issue is referenced.
[x]  The test suite compiles and runs without error.
[x]  Code coverage is 100%. Test cases can be added by editing the test suite.
[x]  The source code is amalgamated; that is, after making changes to the sources in the include/nlohmann directory, run make amalgamate to create the single-header file single_include/nlohmann/json.hpp. The whole process is described here.

@nlohmann Since we don't check extra values in the array when converting to std::pair, I'm doing the same thing.
(i.e. [1,2,3,4] -> std::pair {1, 2})
I'm wondering if we should check if the insertion in the map was successful, seems like a good idea. I don't know which exception to throw however. What's your opinion on it?

Coverage decreased (-0.03%) to 99.971% when pulling 6b6e73d2ec2cddd039e3671999824fbe247165b2 on theodelrieu:feature/map_conversion into 567fe9b7a04af568f0b6e45c0e3c1ee233f4f981 on nlohmann:develop.

Sorry, I haven't found the time to look into this earlier.

I think the behavior is OK as you're right: it is consistent to the std::pair treatment. Adding an exception for std::map would also require adding one for std::pair which would mean a breaking change in terms of semantic versioning, right?

Nothing is breaking, unless I missed something.
The std::pair overload is already there, and does not need to be changed. The issue with std::map is that its value_type is std::pair<**const** Key, Value>, so using the default std::pair overload does not work.
The only way that I know of constructor this peculiar value_type is to use std::map constructors/functions, so this special treatment is done inside the std::map overload.
Also, one can already serialize a std::map<int, int> to json, the other way around does not work though.

With "breaking" I meant the API behavior in case of superfluous list entries. As we do not throw for pairs if we convert from a 3-element list, we should not throw for maps for symmetry reasons. But adding an exception to the pairs would be a breaking change.

Oh you're right, I've added a test case for this, I kept the existing behavior (i.e. discarding extra values from arrays)

Just for my understanding: Assume I have MyType and provided a to_json function. Then std::map<int, MyType> will be serialized to a list of pairs, and std::map<std::string, MyType> will be serialized to an object.
Assume I have AnotherType that can be converted to a std::string, e.g. by operator std::string(). Will a std::map<AnotherType, MyType be serialized to an object?

Indeed, it will be serialized to an object.
The condition is: if string_t is constructible from Key, then it will be serialized to an object.

Thanks a lot!


fcvt.bf16.s encoding collides with fround.h from zfa

The Zfa extension describes fround.h as "encoded like FCVT.H.S, but with rs2=4". This collides with the proposed fcvt.bf16.s encoding which also uses 4 in the rs2 position:
field bits<32> Inst = { 0, 1, 0, 0, 0, 1, 0, 0, 0, 1, 0, 0, rs1{4}, rs1{3}, rs1{2}, rs1{1}, rs1{0}, frm{2}, frm{1}, frm{0}, rd{4}, rd{3}, rd{2}, rd{1}, rd{0}, 1, 0, 1, 0, 0, 1, 1 };

Just a ping on this.

Thanks for pointing this out Alex. I'm looking into a new encoding for fcvt.bf16.s.

@kdockser Could I ask you to roll a new release artifact with this change and a new version number?  Having a cite-able PDF with a distinct version will make it easier to do change tracking for downstream projects.  In particular, this should unblock us landing experimental support in LLVM.

Reopened until the change is pushed (which will be soon).

I see the change is pushed now (thanks!), but a new PDF build and an incremented spec version number would be much appreciated. I could commit the experimental support for bfloat16 with reference to the current commit id, but it's not ideal that people wanting to review the implementation can't easily access a PDF.

The spec number is now incremented (thanks!) - would it be possible to get a new PDF release?

A new PDF has been released. This includes that changes suggested by the AR Committee.

@kdockser I'm not seeing the new PDF? The last tagged release is https://github.com/riscv/riscv-bfloat16/releases/tag/20230322 (March 22nd)

@kdockser I'm not seeing the new PDF? The last tagged release is https://github.com/riscv/riscv-bfloat16/releases/tag/20230322 (March 22nd)

Another ping, as the PDF still doesn't seem to be posted. Many thanks.


Update quick start

Part of #169 . You may see here for preview.

Codecov Report

Merging #232 (553d015) into master (cb6cbb4) will decrease coverage by 1.22%.
The diff coverage is 1.28%.

@@             Coverage Diff              @@
##             master     #232      +/-   ##
============================================
- Coverage     78.74%   77.52%   -1.23%
  Complexity     1149     1149
============================================
  Files           139      139
  Lines          3289     3341      +52
  Branches        377      373       -4
============================================
  Hits           2590     2590
- Misses          604      656      +52
  Partials         95       95

Impacted Files
Coverage Δ

...22s1_cs2103t_w16_2/btbb/commons/core/Messages.java
0.00% <ø> (ø)

...2103t_w16_2/btbb/logic/parser/util/ParserUtil.java
95.04% <ø> (ø)

..._cs2103t_w16_2/btbb/model/util/SampleDataUtil.java
0.00% <0.00%> (ø)

...ava/ay2122s1_cs2103t_w16_2/btbb/ui/MainWindow.java
0.00% <0.00%> (ø)

..._w16_2/btbb/logic/descriptors/OrderDescriptor.java
85.71% <100.00%> (ø)

Continue to review full report at Codecov.

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


Not readily reflected.

Issue Type: Bug
Selecting browse -> repository from here is not immediately reflected in the workspace.
When I close the workspace and reopen it, it is reflected.
This was not a problem in previous versions.

I will summarize the procedure.

Please see attached documents.
Fault phenomenon.pdf

@h-shino, thank you very much for the document and apologies for not getting back to you on this until now. I have looked at the document and based on the provided screenshots, it looks like the problem that you are experiencing is related to a feature that is contributed by the GitLens extension. I would recommend that you file this issue in the extension's repository. Thank you!


Document that Mac bindings can only be built on a Mac

Would be great to document that Mac bindings can only be built on a Mac, and that Pair to Mac will not work.
Better if it could be documented which built files from the Mac need to be moved back over to Windows, and how to incorporate them into the solution.

Okay the Firebase example doesn't build on a Mac either because it can't resolve the Firebase package dependencies. I'm not familiar with XCode but the docs don't seem to have steps I missed.

Hi, @BioTurboNick - thanks for using Maui.NativeLibraryInterop and reporting this issue. If you are still experiencing this, could you please share more information about the error you're seeing and attach a binlog so we can take a closer look? Thank you :)

Well, the original issue doesn't really need more information - the Getting Started documentation (https://learn.microsoft.com/en-us/dotnet/communitytoolkit/maui/native-library-interop/get-started) weirdly doesn't discuss development of the interop on a Windows machine.
I'll file a new issue to discuss the follow-up comment if that's still an issue, that was me venting.

@BioTurboNick gotcha, thanks for clarifying. In order to implement Mac/iOS bindings, you will need to use a Mac machine with Xcode installed. Will note to make sure this is clarified in the docs!


Fix and enable checker_test.go.

What this PR does / why we need it:
The checker_test.go was not enabled, since it wasn't added to the bazel build file.
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
Special notes for your reviewer:
Release note:

NONE

/lgtm


[Issue 9418][docs] Add how to define Pulsar resources names when using K8S runtime

Fixes #9418
Motivation
There is disconnection of Pulsar name verification and Kubernetes name verification, we need to tell users how to define Pulsar resources names when running functions and connectors in K8S.
Modifications

Add the above content.
Remove some unnecessary links.

Related to https://github.com/apache/pulsar/issues/9360


[Hummingbird Current] More fixes for the titles

Fixes the serialization of each title, prioritizing the users preference, then canonical.

Looks solid :+1:


maybe the basecamp project urls used to have a trailing slash? fixes #15...

simple fix?

We are actually moving away from adding scripts to repository in favor of separate npm packages per scripts. We have already stopped accepting new scripts, and will stop accepting pull requests on this repository after hubot 3.0.
See #1113 for details. If you are interested in maintaining this longer term, check npm in case someone already made a package for it, and if not, check out https://hubot.github.com/docs/scripting/ for creating a package of your own.


SAA-342: Check for duplicate activity

Codecov Report
Base: 69.88% // Head: 69.92% // Increases project coverage by +0.04% :tada:

Coverage data is based on head (7f95818) compared to base (eaaba3d).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files
@@             Coverage Diff              @@
##               main     #174      +/-   ##
============================================
+ Coverage     69.88%   69.92%   +0.04%
- Complexity      709      712       +3
============================================
  Files           143      143
  Lines          3377     3382       +5
  Branches        125      126       +1
============================================
+ Hits           2360     2365       +5
  Misses          941      941
  Partials         76       76

Impacted Files
Coverage Δ

...activitiesmanagementapi/service/ActivityService.kt
87.71% <100.00%> (+1.18%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


[部署错误] vercel 部署失败, TypeError: Cannot read properties of undefined (reading '0')

描述遇到的问题
vercel 部署失败
之前一直是可以正常部署的，最近迁移了旧博客的文章，改了 next 主题的 footer，再部署就会报错了
相应配置
Fork 项目：https://github.com/wanghaoxi3000/NotionNext
notion_page_id：ae3c8c9fd2e7490cb2980f96e33fe57e
网站地址：https://darkreunion.tech/
截图

/vercel/path0/.next/server/chunks/635.js:6583
--
17:45:24.762 | const defaultCollectionViewId = viewIds[0];
17:45:24.762 | ^
17:45:24.762 |
17:45:24.762 | TypeError: Cannot read properties of undefined (reading '0')
17:45:24.762 | at CollectionViewBlock (/vercel/path0/.next/server/chunks/635.js:6583:42)
17:45:24.762 | at Fb (/vercel/path0/node_modules/react-dom/cjs/react-dom-server-legacy.node.production.min.js:65:44)
17:45:24.762 | at Ib (/vercel/path0/node_modules/react-dom/cjs/react-dom-server-legacy.node.production.min.js:67:254)
17:45:24.762 | at W (/vercel/path0/node_modules/react-dom/cjs/react-dom-server-legacy.node.production.min.js:73:89)
17:45:24.762 | at Ib (/vercel/path0/node_modules/react-dom/cjs/react-dom-server-legacy.node.production.min.js:71:304)
17:45:24.762 | at W (/vercel/path0/node_modules/react-dom/cjs/react-dom-server-legacy.node.production.min.js:73:89)
17:45:24.762 | at Ib (/vercel/path0/node_modules/react-dom/cjs/react-dom-server-legacy.node.production.min.js:67:482)
17:45:24.762 | at W (/vercel/path0/node_modules/react-dom/cjs/react-dom-server-legacy.node.production.min.js:73:89)
17:45:24.763 | at Ib (/vercel/path0/node_modules/react-dom/cjs/react-dom-server-legacy.node.production.min.js:67:482)
17:45:24.763 | at W (/vercel/path0/node_modules/react-dom/cjs/react-dom-server-legacy.node.production.min.js:73:89)
17:45:24.763 |
17:45:24.763 | Node.js v18.16.1
17:45:24.767 | [响应成功]: from:slug-props-article/life-stream-2305-W1
17:45:24.767 | [API耗时] 141ms
17:45:24.806 | Static worker unexpectedly exited with code: 1 and signal: null

17:45:38.477 | TypeError: Cannot read properties of undefined (reading '0')
17:45:38.477 | at CollectionViewBlock (/vercel/path0/.next/server/chunks/635.js:6583:42)
17:45:38.477 | at Wc (/vercel/path0/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:68:44)
17:45:38.477 | at Zc (/vercel/path0/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:70:253)
17:45:38.477 | at Z (/vercel/path0/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:76:89)
17:45:38.477 | at Zc (/vercel/path0/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:74:209)
17:45:38.477 | at Z (/vercel/path0/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:76:89)
17:45:38.477 | at Zc (/vercel/path0/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:70:481)
17:45:38.477 | at Z (/vercel/path0/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:76:89)
17:45:38.477 | at Zc (/vercel/path0/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:70:481)
17:45:38.477 | at Z (/vercel/path0/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:76:89)
17:45:38.478 |
17:45:38.478 | Error occurred prerendering page "/article%2Fgolang-gc". Read more: https://nextjs.org/docs/messages/prerender-error
17:45:38.478 | TypeError: Cannot read properties of undefined (reading '0')
17:45:38.478 | at CollectionViewBlock (/vercel/path0/.next/server/chunks/635.js:6583:42)
17:45:38.478 | at Wc (/vercel/path0/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:68:44)
17:45:38.478 | at Zc (/vercel/path0/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:70:253)
17:45:38.478 | at Z (/vercel/path0/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:76:89)
17:45:38.478 | at Zc (/vercel/path0/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:74:209)
17:45:38.478 | at Z (/vercel/path0/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:76:89)
17:45:38.478 | at Zc (/vercel/path0/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:70:481)
17:45:38.478 | at Z (/vercel/path0/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:76:89)
17:45:38.478 | at Zc (/vercel/path0/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:70:481)
17:45:38.478 | at Z (/vercel/path0/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:76:89)

17:47:35.710 | Static worker unexpectedly exited with code: null and signal: SIGTERM
17:47:35.712 | Static worker unexpectedly exited with code: null and signal: SIGTERM
17:47:35.713 | Static worker unexpectedly exited with code: null and signal: SIGTERM
17:47:35.714 | warn  - Restarted static page generation for /article%2Fgolang-scheduler because it took more than 60 seconds
17:47:35.714 | warn  - See more info here https://nextjs.org/docs/messages/static-page-generation-timeout
17:47:35.714 | warn  - Restarted static page generation for /article%2Fuse-gin-and-websocket-to-play-rtsp-video because it took more than 60 seconds
17:47:35.714 | warn  - Restarted static page generation for /article%2Fdeploy-kubernetes-on-ubuntu18 because it took more than 60 seconds
17:47:35.714 | warn  - Restarted static page generation for /article%2Fseckill-backend-system-base-on-go-micro because it took more than 60 seconds
17:47:35.714 | warn  - Restarted static page generation for /article%2Ffirst-exploration-of-mirco-service because it took more than 60 seconds
17:47:35.714 | warn  - Restarted static page generation for /article%2Fuse-ci-system-to-free-time because it took more than 60 seconds
17:47:35.714 | warn  - Restarted static page generation for /article%2Fgo-base-knowledge because it took more than 60 seconds
17:47:35.715 | warn  - Restarted static page generation for /article%2Fversatility-uwsgi-config because it took more than 60 seconds
17:47:35.715 | warn  - Restarted static page generation for /article%2Fmanage-hexo-theme-with-git-submodules because it took more than 60 seconds
17:47:35.715 | warn  - Restarted static page generation for /article%2Falgorithm-with-leetcode because it took more than 60 seconds
17:47:35.715 | warn  - Restarted static page generation for /article%2Fpython-build-in-function because it took more than 60 seconds
17:47:35.716 | warn  - Restarted static page generation for /article%2Fsometimes-useful-mysql-skill because it took more than 60 seconds
17:47:35.717 | warn  - Restarted static page generation for /article%2Fsometimes-useful-git-skill because it took more than 60 seconds
17:47:35.717 | warn  - Restarted static page generation for /article%2Fpandas-basic-usage because it took more than 60 seconds
17:47:35.717 | warn  - Restarted static page generation for /article%2Fnumpy-basic-usage because it took more than 60 seconds
17:47:35.717 | warn  - Restarted static page generation for /article%2Fmysql-config-adjust because it took more than 60 seconds
17:47:35.717 | warn  - Restarted static page generation for /article%2Frunning-crontab-in-docker because it took more than 60 seconds
17:47:35.717 | warn  - Restarted static page generation for /article%2Fdjango-hides-the-primary-key-id-in-the-database-with-hash because it took more than 60 seconds
17:47:35.717 | warn  - Restarted static page generation for /article%2Fvirtualenvwrapper-of-the-python-module because it took more than 60 seconds
17:47:35.717 | warn  - Restarted static page generation for /article%2Flinux-common-commands because it took more than 60 seconds
17:47:35.717 | warn  - Restarted static page generation for /article%2Fshell-edit-the-crontab-task because it took more than 60 seconds
17:47:35.718 | warn  - Restarted static page generation for /article%2Fcpp11-new-knowledge-point because it took more than 60 seconds
17:47:35.718 | warn  - Restarted static page generation for /article%2Fnotes-on-the-design-pattern-of-big-talk because it took more than 60 seconds
17:47:35.718 | warn  - Restarted static page generation for /article%2Fes6-scope-and-deconstruction-assignment because it took more than 60 seconds
17:47:35.718 | warn  - Restarted static page generation for /article%2Fthe-class-object-of-the-thinking-mapping-java because it took more than 60 seconds
17:47:35.718 | warn  - Restarted static page generation for /article%2Fjava-io-learning-point-guide because it took more than 60 seconds
17:47:35.718 | warn  - Restarted static page generation for /article%2Fjavascript-function because it took more than 60 seconds
17:47:35.718 | warn  - Restarted static page generation for /article%2Fthe-basic-concept-of-javascript-closure because it took more than 60 seconds
17:47:35.718 | warn  - Restarted static page generation for /article%2Fjavascript-type-comparison because it took more than 60 seconds
17:47:35.718 | warn  - Restarted static page generation for /article%2Fcollections-of-the-python-module because it took more than 60 seconds
17:47:35.718 | warn  - Restarted static page generation for /article%2Fpython-advanced-decorator because it took more than 60 seconds
17:47:35.718 | warn  - Restarted static page generation for /article%2Fpython-advanced-iterator-and-generator because it took more than 60 seconds
17:47:35.718 | warn  - Restarted static page generation for /article%2Fbrief-explanation-of-event-driven-(python-implementation) because it took more than 60 seconds
17:47:35.718 | warn  - Restarted static page generation for /article%2Fthe-configuration-program-becomes-a-linux-service because it took more than 60 seconds
17:47:35.719 | warn  - Restarted static page generation for /article%2Fdjango-modelform-modifies-the-default-control-properties because it took more than 60 seconds
17:47:35.719 | warn  - Restarted static page generation for /article%2Fdesign-pattern-of-django because it took more than 60 seconds
17:47:35.719 | warn  - Restarted static page generation for /article%2Fsummary-of-shell-writing because it took more than 60 seconds
17:47:35.719 | warn  - Restarted static page generation for /article%2Fmysql-will-surely-know-notes because it took more than 60 seconds
17:47:35.719 | warn  - Restarted static page generation for /article%2Fandroid-activity-lifecycle because it took more than 60 seconds
17:47:35.719 | warn  - Restarted static page generation for /article%2Fpython-small-knowledge-point because it took more than 60 seconds
17:47:35.719 | warn  - Restarted static page generation for /article%2Fpython-tarfile-module-unzip-invalid-mode-('wb')-or-filename because it took more than 60 seconds
17:47:35.719 | warn  - Restarted static page generation for /article%2Fmakefile-common-knowledge-points because it took more than 60 seconds
17:47:35.719 | warn  - Restarted static page generation for /article%2Fpy2exe-conversion-parameters because it took more than 60 seconds
17:47:35.719 | warn  - Restarted static page generation for /article%2Flinux-driven-development-basic-knowledge because it took more than 60 seconds
17:47:35.719 | warn  - Restarted static page generation for /article%2Fvi-skills because it took more than 60 seconds
17:47:35.719 | warn  - Restarted static page generation for /message because it took more than 60 seconds
17:47:35.719 | warn  - Restarted static page generation for /links because it took more than 60 seconds
17:47:35.719 | warn  - Restarted static page generation for /%23 because it took more than 60 seconds
Expand 7 Lines
17:48:36.320 | Static worker unexpectedly exited with code: null and signal: SIGTERM
17:48:36.321 | warn  - Restarted static page generation for /article%2Fgolang-scheduler because it took more than 60 seconds
17:48:36.321 | warn  - Restarted static page generation for /article%2Fuse-gin-and-websocket-to-play-rtsp-video because it took more than 60 seconds
17:48:36.321 | warn  - Restarted static page generation for /article%2Fdeploy-kubernetes-on-ubuntu18 because it took more than 60 seconds
17:48:36.321 | warn  - Restarted static page generation for /article%2Fseckill-backend-system-base-on-go-micro because it took more than 60 seconds
17:48:36.321 | warn  - Restarted static page generation for /article%2Ffirst-exploration-of-mirco-service because it took more than 60 seconds
17:48:36.321 | warn  - Restarted static page generation for /article%2Fuse-ci-system-to-free-time because it took more than 60 seconds
17:48:36.321 | warn  - Restarted static page generation for /article%2Fgo-base-knowledge because it took more than 60 seconds
17:48:36.321 | warn  - Restarted static page generation for /article%2Fversatility-uwsgi-config because it took more than 60 seconds
17:48:36.321 | warn  - Restarted static page generation for /article%2Fmanage-hexo-theme-with-git-submodules because it took more than 60 seconds
17:48:36.321 | warn  - Restarted static page generation for /article%2Falgorithm-with-leetcode because it took more than 60 seconds
17:48:36.321 | warn  - Restarted static page generation for /article%2Fpython-build-in-function because it took more than 60 seconds
17:48:36.322 | warn  - Restarted static page generation for /article%2Fsometimes-useful-mysql-skill because it took more than 60 seconds
17:48:36.322 | warn  - Restarted static page generation for /article%2Fsometimes-useful-git-skill because it took more than 60 seconds
17:48:36.322 | warn  - Restarted static page generation for /article%2Fpandas-basic-usage because it took more than 60 seconds
17:48:36.322 | warn  - Restarted static page generation for /article%2Fnumpy-basic-usage because it took more than 60 seconds
17:48:36.322 | warn  - Restarted static page generation for /article%2Fmysql-config-adjust because it took more than 60 seconds
17:48:36.322 | warn  - Restarted static page generation for /article%2Frunning-crontab-in-docker because it took more than 60 seconds
17:48:36.322 | warn  - Restarted static page generation for /article%2Fdjango-hides-the-primary-key-id-in-the-database-with-hash because it took more than 60 seconds
17:48:36.322 | warn  - Restarted static page generation for /article%2Fvirtualenvwrapper-of-the-python-module because it took more than 60 seconds
17:48:36.322 | warn  - Restarted static page generation for /article%2Flinux-common-commands because it took more than 60 seconds
17:48:36.322 | warn  - Restarted static page generation for /article%2Fshell-edit-the-crontab-task because it took more than 60 seconds
17:48:36.322 | warn  - Restarted static page generation for /article%2Fcpp11-new-knowledge-point because it took more than 60 seconds
17:48:36.322 | warn  - Restarted static page generation for /article%2Fnotes-on-the-design-pattern-of-big-talk because it took more than 60 seconds
17:48:36.322 | warn  - Restarted static page generation for /article%2Fes6-scope-and-deconstruction-assignment because it took more than 60 seconds
17:48:36.322 | warn  - Restarted static page generation for /article%2Fthe-class-object-of-the-thinking-mapping-java because it took more than 60 seconds
17:48:36.322 | warn  - Restarted static page generation for /article%2Fjava-io-learning-point-guide because it took more than 60 seconds
17:48:36.323 | warn  - Restarted static page generation for /article%2Fjavascript-function because it took more than 60 seconds
17:48:36.323 | warn  - Restarted static page generation for /article%2Fthe-basic-concept-of-javascript-closure because it took more than 60 seconds
17:48:36.323 | warn  - Restarted static page generation for /article%2Fjavascript-type-comparison because it took more than 60 seconds
17:48:36.323 | warn  - Restarted static page generation for /article%2Fcollections-of-the-python-module because it took more than 60 seconds
17:48:36.323 | warn  - Restarted static page generation for /article%2Fpython-advanced-decorator because it took more than 60 seconds
17:48:36.323 | warn  - Restarted static page generation for /article%2Fpython-advanced-iterator-and-generator because it took more than 60 seconds
17:48:36.323 | warn  - Restarted static page generation for /article%2Fbrief-explanation-of-event-driven-(python-implementation) because it took more than 60 seconds
17:48:36.323 | warn  - Restarted static page generation for /article%2Fthe-configuration-program-becomes-a-linux-service because it took more than 60 seconds
17:48:36.323 | warn  - Restarted static page generation for /article%2Fdjango-modelform-modifies-the-default-control-properties because it took more than 60 seconds
17:48:36.323 | warn  - Restarted static page generation for /article%2Fdesign-pattern-of-django because it took more than 60 seconds
17:48:36.323 | warn  - Restarted static page generation for /article%2Fsummary-of-shell-writing because it took more than 60 seconds
17:48:36.323 | warn  - Restarted static page generation for /article%2Fmysql-will-surely-know-notes because it took more than 60 seconds
17:48:36.323 | warn  - Restarted static page generation for /article%2Fandroid-activity-lifecycle because it took more than 60 seconds
17:48:36.323 | warn  - Restarted static page generation for /article%2Fpython-small-knowledge-point because it took more than 60 seconds
17:48:36.323 | warn  - Restarted static page generation for /article%2Fpython-tarfile-module-unzip-invalid-mode-('wb')-or-filename because it took more than 60 seconds
17:48:36.323 | warn  - Restarted static page generation for /article%2Fmakefile-common-knowledge-points because it took more than 60 seconds
17:48:36.323 | warn  - Restarted static page generation for /article%2Fpy2exe-conversion-parameters because it took more than 60 seconds
17:48:36.324 | warn  - Restarted static page generation for /article%2Flinux-driven-development-basic-knowledge because it took more than 60 seconds
17:48:36.324 | warn  - Restarted static page generation for /article%2Fvi-skills because it took more than 60 seconds
17:48:36.324 | warn  - Restarted static page generation for /message because it took more than 60 seconds
17:48:36.324 | warn  - Restarted static page generation for /links because it took more than 60 seconds
17:48:36.324 | warn  - Restarted static page generation for /%23 because it took more than 60 seconds
17:48:36.908 | [请求API] from:slug-props-article/golang-scheduler id:ae3c8c9fd2e7490cb2980f96e33fe57e
17:48:37.693 | [响应成功]: from:slug-props-article/golang-scheduler
17:48:37.693 | [API耗时] 786ms
17:48:37.738 | [请求API] from:data-notice id:129c8c93-bc35-4223-99da-1b04a34407b3
17:48:37.853 | [响应成功]: from:data-notice
17:48:37.853 | [API耗时] 115ms
17:48:37.864 | [请求API] from:slug-props-article/golang-scheduler id:0498bc63-4538-4d18-94f2-6edf9b92f43f
17:49:36.931 | Static worker unexpectedly exited with code: null and signal: SIGTERM
17:49:36.934 |
17:49:36.935 | > Build error occurred
17:49:36.936 | Error: Static page generation for /article%2Fgolang-scheduler is still timing out after 3 attempts. See more info here https://nextjs.org/docs/messages/static-page-generation-timeout
17:49:36.936 | at onRestart (/vercel/path0/node_modules/next/dist/build/index.js:647:35)
17:49:36.936 | at Worker.exportPage (/vercel/path0/node_modules/next/dist/lib/worker.js:88:40)
17:49:36.937 | at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
17:49:36.937 | at async /vercel/path0/node_modules/next/dist/export/index.js:502:32
17:49:36.937 | at async Span.traceAsyncFn (/vercel/path0/node_modules/next/dist/trace/trace.js:97:20)
17:49:36.937 | at async Promise.all (index 61)
17:49:36.937 | at async /vercel/path0/node_modules/next/dist/export/index.js:497:9
17:49:36.937 | at async Span.traceAsyncFn (/vercel/path0/node_modules/next/dist/trace/trace.js:97:20)
17:49:36.937 | at async /vercel/path0/node_modules/next/dist/build/index.js:1440:21
17:49:36.937 | at async Span.traceAsyncFn (/vercel/path0/node_modules/next/dist/trace/trace.js:97:20)
17:49:36.974 | error Command failed with exit code 1.
17:49:36.974 | info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
17:49:36.996 | Error: Command "yarn run build" exited with 1

环境

版本 v3.16.4

最近迁移了旧博客的文章
这里做了什么操作，看错误日志是，获取notion-api数据异常

@tangly1024 原来旧博客是 markdown 写的，就是把这些内容粘贴到了 notion 中，这个过程持续了几天，每天移过来一部分，4天前部署了一次是可以的。
另外删除了 type 为 menu 类型的菜单，暂时不会用到二级菜单功能，调整了数据表列的顺序不知道有没有影响，有尝试改回和模板一致还是无法部署。

@tangly1024 我在本地使用 yarn build 来构建测试了下，发现似乎是  https://www.notion.so/Golang-GC-e7a5493ca981423caef4931f010cbe1a 这篇文章导致了 TypeError: Cannot read properties of undefined (reading '0') 的问题，
把这篇文章改为 Draft 状态，即可正常构建了。
在构建完成后，重新设置为 Published 状态，文章标题和摘要可以在目录中显示，但是一点击进去就会出错变为空白页，vercel 的日志中可以查看到同样出现了 TypeError: Cannot read properties of undefined (reading '0') 的错误。
这篇文章我反复检查了几次，该有的属性都有，看起来和其他正常的文章没有什么不同... 不清楚出现此问题的原因了。
另外发现 404 页面显示 页面无法加载，即将返回首页，但实际并不会自动跳转到首页，比如我搭建的这个:  https://darkreunion.tech/404

升级到4.0.8 版本，404 页面可以正常跳转了，出错的页面手动重新复制了下，也可以正常构建了


build.julialang.org should actually exist

cc @stefankarpinski, along with cache.julialang.org, ref https://github.com/JuliaLang/WinRPM.jl/issues/57#issuecomment-150830473

huzzah, it exists now, but has to use http://build.julialang.org:8010 - how do we get rid of the need for the :8010 ?

Done and done.  Now available not only over port 80, but over HTTPS.

yay, thanks! now if only I knew how to solve (or even locally reproduce) https://github.com/JuliaLang/julia/issues/9572 or https://github.com/JuliaLang/julia/issues/13719 which are afflicting the osx and centos buildbots

Agreed.  I have no idea why those things are happening.  Hopefully someone with enough time on their hands and the ability to track it down will get tired of not having nightlies and will fix it.  Alternatively, if someone wants to fix it but can't reproduce locally, I can grant temporary buildbot SSH access.


🚨[Urgent Bug] — Please fix the issue that the latest stable version of VSCode (1.91.0 stable) cannot be launched on macOS (11.7.10) as soon as possible

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version: 1.91.0
OS Version: macOS Big Sur - 版本：11.7.10 (20G1427)

Steps to Reproduce:

最新版本的 VSCode 在该 macOS 系统系统下无法启动；
但是 VSCode-Insides 1.92.0 可以正常启动；

这是正常工作下的 VSCode
版本: 1.90.0
提交: 89de5a8d4d6205e5b11647eb6a74844ca23d2573
日期: 2024-06-04T19:34:44.157Z
Electron: 29.4.0
ElectronBuildId: 9593362
Chromium: 122.0.6261.156
Node.js: 20.9.0
V8: 12.2.281.27-electron.0
OS: Darwin x64 20.6.0

以及
Version: 1.92.0-insider
Commit: 82104a3a6cf8713b81e5bbd97960dbf5c82a816a
Date: 2024-07-05T00:00:00.000Z (1 day ago)
Electron: 29.4.0
ElectronBuildId: 9728852
Chromium: 122.0.6261.156
Node.js: 20.9.0
V8: 12.2.281.27-electron.0
OS: Darwin x64 20.6.0

请尽快修复 1.91.0 稳定版无法在该系统下无法启动的问题；

see the pinned issue https://github.com/microsoft/vscode/issues/219893

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.
Happy Coding!


First draft of theme support

Still missing:

[ ] make a theme using that: https://github.com/Keats/gutenberg-hyde
[ ] if needed for the line above, make a dummy server command to easily develop themes that will create a dummy site and then serve it while live-reloading html/css
[ ] docs

In the future when there are more themes, also investigate a theme command eventually that would list available themes and install them (via git clone I guess)


Modify interface for extension

What changes are proposed in this pull request?
Modify interface for extension
Why are the changes needed?
Modify interface for extension

alluxio-bot, merge this please


Implement a better shuffle

Coverage increased (+0.2%) to 84.439% when pulling d1ebc1e917a0eba44f64bc4f1ba4ee3d3e6339b3 on akalin/better-shuffle into 0c8b960f9a0d60e5f4e6c43b8169553692aa21b9 on master.

Coverage increased (+0.2%) to 84.439% when pulling d1ebc1e917a0eba44f64bc4f1ba4ee3d3e6339b3 on akalin/better-shuffle into 0c8b960f9a0d60e5f4e6c43b8169553692aa21b9 on master.

Okay, addressed all comments! PTAL


Maximum call stack size exceeded

Hi @andismith,
I try to resize a few hundreds  images (jpg, png) :smile:
It perfectly works the first time i run the task grunt responsive_images:server.
Nevertheless, when i run the task for a second time, the error  Warning: Maximum call stack size exceeded occurs – when newFilesOnly is running.
This is the output:

Here is the grunt task:
responsive_images: {
      options: {
        quality: 80,
        sizes: [{
          name: 'xsmall',
          aspectRatio:false,
          upscale: true,
          width: 140
        },{
          name: 'small',
          upscale: true,
          width: 360
        },{
          name: 'medium',
          upscale: true,
          width: 640
        },{
          name: 'large',
          upscale: true,
          width: 1024
        }]
      },
      server: {
        files: [{
          expand: true,
          cwd: '<%= yeoman.app %>',
          src: ['img/sources/**/*.{jpg,jpeg,png}'],
          custom_dest: '<%= yeoman.app %>/img/{%= name %}'
        }]
      }
    },

and here is how i register the task
  grunt.registerTask('serve', function (target) {
    if (target === 'dist') {
      return grunt.task.run(['build', 'connect:dist:keepalive']);
    }

    grunt.task.run([
      'clean:server',
      'responsive_images:server',
      'newer:imagemin:server',
      'concurrent:server',
      'autoprefixer:server',
      'connect:livereload',
      'watch'
    ]);
  });

OS: windows 8.1
node: 0.10.26
grunt: 0.4.5
Responsive Images 0.1.6

Any help much appreciate.

PS: 'newFilesOnly' tries to check if 2561 files already exist on the disk. It's huge, isn't it ?

Fix this issue by scheduling the "immediate" execution of callback after I/O events callbacks and before setTimeoutand setInterval – Read more here :octocat: : https://github.com/andismith/grunt-responsive-images/pull/87


Fix Ansible version_compare change in behaviour

Non-standard strings (e.g. CI job names) can no longer be compared against versions. Since this usually indicates a CI build unconditionanally upgrade.
Also fixes a deprecation warning:
[DEPRECATION WARNING]: Using tests as filters is deprecated. Instead of using
result|version_compare use result is version_compare. This feature will be
removed in version 2.9. Deprecation warnings can be disabled by setting
deprecation_warnings=False in ansible.cfg.

To try and understand the various combinations of versions/variables before and after this PR, I tried to summarize various scenarios using an installed OMERO 5.5.0 server in the following table.

omero_server_release
installed version
omero_server_upgrade
Behavior (without PR)
Behavior (proposed)

latest
5.5.0
true
upgrade
upgrade

latest
5.5.0
false
no upgrade
no upgrade

present
5.5.0
true
no upgrade
no upgrade

present
5.5.0
false
no upgrade
no upgrade

5.5.1
5.5.0
true
upgrade
upgrade

5.5.1
5.5.0
false
no upgrade
no upgrade

OMERO-build
5.5.0
true
no upgrade
upgrade

OMERO-build
5.5.0
false
no upgrade
no upgrade

Is this representation correctly capturing the current behavior and the proposed change? If so, I agree we need some mechanism to force an upgrade using a given QA/CI build.
The primary question for me is whether we want to keep handling this scenario via the omero_server_release variable especially as no comparison with the current version is involved in the upgrade decision. One idea would be a separate development variable e.g. omero_server_build that could override omero_server_release. If the scenario of forcing a server upgrade using a standard version (e.g. 5.5.1 -> 5.5.0) is also in scope, an alternative would be to extend the upgrade semantics to include some force option.

I think (though I'm not sure) there should be no change in behaviour. Previously comparing "non-numeric-string" < 5.5.1 was allowed though always returned the same value, now it's not, so this should be a bug fix.
If it is a change in behaviour then I think it's acceptable since these parameters aren't documented and it's for dev use.
I agree it would be nice to have a proper way of handling specifying versions (both release and dev versions) but there's a very old trello card and it's unlikely to be resolved anytime soon 😀.

Previously comparing "non-numeric-string" < 5.5.1 was allowed though always returned the same value, now it's not, so this should be a bug fix.

Ah I missed this from my representation above. Is it related an upstream Ansible change? Which versions should be tested with/without this PR?

It's an upstream Ansible change. I don't know which version though. I think as long as as the release/production deployment is unchanged we can have some leeway on development or hidden parameters.

Thanks for the sleuthing!