Add Support for Node.js 22

https://github.com/Milanzor/webpack-watched-glob-entries-plugin/blob/f4b7b42646269f5109ae5059ea701c404b264ead/package.json#L25
webpack-watched-glob-entries-plugin supports up to Node.js 21.
However, Node.js 22 becomes LTS since 2024-10-29: https://github.com/nodejs/Release
Therefore, I would be happy if this plugin supports Node.js 22.

There is a very high chance it'll run on Node 22.
I'm unavailable to do it myself this week but if you can make a PR, I can merge it and update this package.
Thanks


Do not propose updates that are not available for all crossScalaVersions

see https://github.com/plokhotnyuk/jsoniter-scala/pull/180

I don't see updates of dependencies that are not available for all crossScalaVersions anymore. Maybe this has been fixed in sbt-updates 0.4.0.


Issue: App publishing. webview_flutter

Hi, everyone,
Problem description:
In the application I am developing, it is necessary to play live videos from a YouTube playlist, this is why I must use webview, however, Google Play is rejecting the application because when pressing the android home button, the video continues with the reproduction. How can I stop it to eliminate this error?
child: WebView(
    initialUrl: "$PlaylistLink",
    javascriptMode: JavascriptMode.unrestricted,
),

Note: It is not when I press the Android back button, it is when I press the Android home button.
I hope you can help me, regards.

Duplicate of #32363


[Linux] add missing libstdc++fs library to onnxruntime_test_all target

Discovered on: Ubuntu 18.x, compilers used: GCC 7.x and GCC 8.2
Due to missing library linker is reporting std::filesystem unresolved symbols for target onnxruntime_test_all.
Adding libstdc++fs to the target's linking rules solves the issue.
Signed-off-by: Artur Wojcik<EMAIL_ADDRESS>

It does occur on Ubuntu 16.x, too. I just verified this. By adding stdlibc++fs to the target's linker rules solves the issue.

If that, why our CI build didn't catch it?

It is hard for me to say. I don't know the configuration of your CI. I am using clean installation of Ubuntu. I tried 16.x, 17.x and 18.x and all have the same issue while linking onnxruntime_test_all.

Let me reproduce the error first.
Thank you for the fixing.

Hi @apwojcik
Could you please run
grep FILESYSTEM CMakeCache.txt

In your build dir, and post the result here?
Thanks.

Ubuntu 16.04
HAS_EXPERIMENTAL_FILESYSTEM_H:INTERNAL=1
HAS_FILESYSTEM_H:INTERNAL=

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: apwojcik sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

I have updated PR with changes allowing to build using CMake 3.8 and above. For Ubuntu 17.x and 18.x now you may use distribution provided CMake. Ubunut 16.x stills need installation of more recent CMake.


Multiple Geometries in shape not supported?

Hi Dave,
Is my understanding from the shapes.py code correctly that you currently do not support the reading of multiple geometry sections defined in a single shape record?
I have come across several examples of such cases.
Geert

I ran into the same problem. I modified the code so it would:
shapes.py starting at line 151:
geometrys = self.xml.findall(f'{namespace}Section[@N="Geometry"]')
for geometry in geometrys:
if type(geometry) is Element:
# print(f"geometry({type(geometry)}):{geometry}")
self.geometry = vsdx.Geometry(xml=geometry, shape=self)
if geometry.attrib.get('IX') is not None:
self.geometry.index = geometry.attrib['IX']
else:
self.geometry.index = 0
for r in geometry.findall(f"{namespace}Row"):
row_type = r.attrib['T']
if r.attrib.get('IX') is not None:
row_type = f"{row_type}/{r.attrib['IX']}"
else:
row_type = f"{row_type}/0"
if row_type:
for e in r.findall(f"{namespace}Cell"):
cell = vsdx.Cell(xml=e, shape=self)
key = f"Geometry/{self.geometry.index}/{row_type}/{cell.name}"
self.cells[key] = cell
so if you have:

you can modify the different values as so:
shape.set_cell_value("Geometry/2/LineTo/2/Y", '1.51770027')
This will handle multiple Geometries and Rows.
For dave:
I can provide more context if ya want, but I think this can be applied to all sections, rows, and even cells with dupe names

Keep in mind this will break certain functions like line_to_x, but if you've gotten this far, just call the cell_val yourself


fix(frontend): loading status in uploading page

:tada: This PR is included in version 3.2.1-alpha.7 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.2.2 :tada:
The release is available on npm package (@latest dist-tag)
Your semantic-release bot :package::rocket:


First Birthday Post

Motivation
It's Slash's Birthday!
Have you read the Contributing Guidelines on pull requests?
Yes.
Test Plan
Local and Netlify
Related PRs
N/A

😍


Documentation typo ReactFontManager.java

Description
https://github.com/facebook/react-native/blob/master/ReactAndroid/src/main/java/com/facebook/react/views/text/ReactFontManager.java#L78
  /**
   * Add additional font family, or replace the exist one in the font memory cache.
   * @param style
   * @see {@link Typeface#DEFAULT}
   * @see {@link Typeface#BOLD}
   * @see {@link Typeface#ITALIC}
   * @see {@link Typeface#BOLD_ITALIC}
   */
  public void setTypeface(String fontFamilyName, int style, Typeface typeface) {

The line with Typeface#DEFAULT should be changed to Typeface#NORMAL. Default is a typeface object, normal is the value 0 as documented in TypeFace class.
Additional Information

React Native version: Any, but if you really want a number: 0.42
Platform: Android

Should be a quick fix. Want to send a PR?

Hi there! This issue is being closed because it has been inactive for a while. Maybe the issue has been fixed in a recent release, or perhaps it is not affecting a lot of people. Either way, we're automatically closing issues after a period of inactivity. Please do not take it personally!
If you think this issue should definitely remain open, please let us know. The following information is helpful when it comes to determining if the issue should be re-opened:

Does the issue still reproduce on the latest release candidate? Post a comment with the version you tested.
If so, is there any information missing from the bug report? Post a comment with all the information required by the issue template.
Is there a pull request that addresses this issue? Post a comment with the PR number so we can follow up.

If you would like to work on a patch to fix the issue, contributions are very welcome! Read through the contribution guide, and feel free to hop into #react-native if you need help planning your contribution.


feature/RowProcessor-replaceNewlinesWithSpaces

Description
Add optional boolean flag RowProcessor.replaceNewlinesWithSpaces that controls whether or not to replace newlines with spaces in values before passing them to field processors (don't change default behavior by defaulting this to true).
Motivation
TextFieldProcessors may  wish to be aware of newlines in the input and encode them as features. Example encoded as a unit test.

Thanks. As Jack said, we probably want to revisit this as part of a larger refactor to make RowProcessor a little simpler to use, but in the meantime this seems like a fine change.


Minor grammar fixes to documentation

Possibly non-exhaustive fixes for article for words starting in a U

Thanks!

Thank you!

Cherry-picked for 4.0.4.


Typescript types not available in setup with Yarn PnP, Yarn VS Code SDK

Expected Behavior
Yarn types are available in IDE and used by Typescript for type-checking.
Current Behavior
Types are not available, IDE shows (alias) type Jimp = any. Typescript does not throw an error at Jimp.thisFunctionDoesNotExist();.

Failure Information (for bugs)
Steps to Reproduce

git clone git@github.com:marvinruder/jimp-no-types-available.git && cd jimp-no-types-available
yarn
yarn build
While #1191 is unresolved, remove ["default"] from src/index.js
yarn start
When using VS Code, hovering over import Jimp from "jimp"; shows (alias) type Jimp = any

Screenshots

Context
Context is given in marvinruder/jimp-no-types-available and was briefly mentioned in #1189.

Jimp Version: 0.22.4
Operating System: macOS 13.2 (build 22D49)
Node version: 19.6.0

Already tried yarn unplug jimp, has no effect, type Jimp is still resolved to any.
In tsconfig.json, "skipLibCheck": true appears to be required, removing it throws 27 errors: error TS2307: Cannot find module '@jimp/core' or its corresponding type declarations.

Add these lines to .yarnrc.yml should solve this problem
packageExtensions:
  jimp@*:
    dependencies:
      '@jimp/core': '*'

:rocket: Issue was released in v1.0.2 :rocket:


Users will be created even with worng password

first of all thank you so much, its very helpfull tool.
When we add the pam_script_auth file, and someone try with
user1@server   then enter worng password the server will create the user but access denied, in this way someone can create x-thousend users. its good if you can fix that. thank you
Then, the script itself. In the file /usr/share/libpam-script/pam_script_auth
#!/bin/bash
adduser $PAM_USER --disabled-password --quiet --gecos ""

Hello @hoshang82
The script is just an example and not part of module. You can modify the script in any way you like to meet your requirements.
https://github.com/kha7iq/kc-ssh-pam/issues/18


fallback lsp range format with several buffers get messed

Describe the bug and the expected behavior
fallback lsp range format modifies the wrong buffer
Conform version
v5.1, commit: ad2b5ec
Steps to Reproduce the Bug or Issue
Provide two files:
a.cc:  maybe valid cpp source is enough, formatted or not

#define A_CC

#include <iostream>
using namespace std;

int main() { cout << "Hello World!"; }

b.cc: lsp format will change the content
#define B_CC

#include <iostream>
using namespace std;

int main() {
  cout << "Hello World!";
  return 0;
}

Configuration:

clangd lsp setup for cpp
conform format with fallback to lsp for the filetype: cpp

Steps to reproduce:

nvim a.cc
apply conform format (run at least once)
load b.cc with :e b.cc in nvim
apply conform format (this will trigger the bug)

bug behavior base on the above operation:
For the conform format operation on b.cc:
the first one may finish success, the latter format will raise Error without running the format callback:
Error executing vim.schedule lua callback: /usr/share/nvim/runtime/lua/vim/lsp/util.lua:501: Invalid 'start_col': out of range
stack traceback:
	[C]: in function 'nvim_buf_set_text'
	/usr/share/nvim/runtime/lua/vim/lsp/util.lua:501: in function 'apply_text_edits'
	.../share/nvim/lazy/conform.nvim/lua/conform/lsp_format.lua:24: in function 'apply_text_edits'
	.../share/nvim/lazy/conform.nvim/lua/conform/lsp_format.lua:103: in function 'handler'
	/usr/share/nvim/runtime/lua/vim/lsp.lua:1393: in function ''
	vim/_editor.lua: in function <vim/_editor.lua:0>

Additional context
You may use the lazyNvim: dev  branch to apply the test, use key shot  for conform format operation. the format() wrapper is located in init/utils.lua:format().

I guess you are looking for conform.nvim. This is the repository of a web form validation library :)

😂ome bit of embarrassing🙈 thanks for your reminder😂


Update Remove-SPProjectWebInstanceData.md

Fill in placeholders.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

sharepoint/sharepoint-ps/sharepoint-server/Remove-SPProjectWebInstanceData.md
:white_check_mark:Succeeded
View (sharepoint-ps)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Name ?

Any idea @nclsHart  ?

Some new idea:

ReviewLab
GLower (GitLab + Tower)

And why not keeping gitlab-reviewer as a competitor.

in the end we got used to gitlab-reviewer I propose to close the issue

I'm ok :+1:.
@TomBerriot?

ping @TomBerriot

I'm okay too 👌


put prospectus on a page

addresses #38

:shipit:

coolio! edit the description of the PR to include the other issue it addresses.
:shipit:!


Set no_proxy in install-chef-suse.sh (bsc#998968)

Chef now works around a missing Ruby feature by checking no_proxy
itself and matching against it when returning if a proxy connection
is required, so drop the http_proxy workaround and set no_proxy
directly. Since the script talks to both the hostname and the IP, add
them both.

AFAIK, there was no change in our chef codebase so I'm not sure why this should work now. Can you explain why you think it works now and what changed?

Firstly, I checked the chef REST client code in Cloud 6, which has exclude functionality based on no_proxy, and secondly, I pulled up a development environment to the point where crowbar was installed, exported http_proxy to a machine on my local netwok on port 3128, ensuring any request would get connection refused, and made certain that install-suse-cloud worked.

Mmh... I tried exactly the same while I created the workaround but it didn't work for me. So I don't know if I did something wrong while testing or if something changed in the code.

Testing this on mkcloud to be sure:
mkcloud:~/manual.stevek # ./runtest.c18.stevek cleanup prepare setupadmin prepareinstcrowbar
mkcloud:~/manual.stevek # ssh crowbar.c18.cloud.suse.de

root@crowbar:~ # nc -vz <IP_ADDRESS> 3128
nc: connect to <IP_ADDRESS> port 3128 (tcp) failed: Connection refused
root@crowbar:~ # export http_proxy=http://<IP_ADDRESS>:3128/
root@crowbar:~ # echo $http_proxy
http://<IP_ADDRESS>:3128/
root@crowbar:~ # echo $no_proxy
root@crowbar:~ # install-suse-cloud
<dialogs about starting services, running chef-client and installing barclamps>
This actually fails with:
Retrieving package bridge-utils-1.5-17.56.x86_64 (1/1),  32.1 KiB ( 66.0 KiB unpacked)
Retrieving: bridge-utils-1.5-17.56.x86_64.rpm [error]
Abort, retry, ignore? [a/r/i/? shows all options] (a): a
STDERR: Download (curl) error for 'http://<IP_ADDRESS>/repos/SLES12-SP1-Pool/x86_64/bridge-utils-1.5-17.56.x86_64.rpm':
Error code: Connection failed
Error message: Failed to connect to <IP_ADDRESS> port 3128: Connection refused
However, I think that's fine since in the usual case, a configured proxy server will be able to reach the SLES repos to download an rpm file, and I think it shows the proxy server isn't being used for the myriad of knife calls and then running chef-client.

Change looks good, but can you rebase to retrigger the gating?

No other changes have merged, so a rebase is a no-op. However, I will amend HEAD to change the date and force push to do what you ask.


Pending messages cleanup

Hi,
Is it possible to have an async subscriber stop receiving new messages and clean the existing ones present in the queue (inspected by subscription.Pending)?
Thank you!

@lukaf Not really - a subscriber will continue to receive messages until it is closed, and at that point it will internally clean up any pending messages.  Could you describe your use case?

Hi @ColinSullivan1,
Thanks for the answer. Could you explain a bit what do you mean with 'until it is closed'? Does this refer to connection or subscription? And does cleaning up pending messages mean discarding them?
Basic use case would be gracefully stopping consumers, so that they stop receiving old messages but process current ones and the ones in the queue (pending).
Thank you!

@lukaf No problem!  Sorry for the confusion - I was referring to the subscription being unsubscribed, but the connection close will do the same.  NATS is at most once delivery; when there is no longer interest so the messages will be discarded.
To avoid lost messages, I suggest you look into NATS Streaming?  It will solve this problem for you.
In both NATS and NATS streaming, we have queue subscribers to distribute work.  You can find information about that [here] (http://nats.io/documentation/concepts/nats-queueing).
The NATS streaming server will send messages to the queue subscriber that has the least number of outstanding acknowledgements (the most efficient subscriber), distributing work more fairly, which looks to be in line with your goals.  When you unsubscribe, messages that have been sent to that queue subscriber have not been acknowledged (processed) will automatically be resent to other queue subscribers in the queue group.  Note, the NATS server will distribute messages to a queue subscriber randomly.
If you prefer not to use NATS streaming, we can discuss other alternatives, such as a control plane to allow subscribers to gracefully shut down...
Lowering the max_pending_size at the server will work, but is the brute force approach - a subscriber too far behind will be automatically disconnected and you will still lose messages.
Does NATS streaming sound like it will work for you?

Wow, wasn't even aware NATS streaming exists. It looks like exactly what I'm looking for.
Thank you very much!

@lukaf That's what we like to hear 👍

Absolutely, happy to help!


chore(@embark/site): remove connect() doc and add back onReady

We still had docs about EmbarkJS.Blockchain.connect() and we even had places where we said that onReady was deprecated.
So I removed the connect parts and added back or put higher the onReady

Also CI was failing for this one, but not because of these changes. Restarted the build..

@PascalPrecht updated.
As for the changes for 4.1, we can just do another PR.

Landed!


TST: isinstance(OptimizeResult.message, str) closes #13001

Tests that all isinstance(OptimizeResult.message, str). Fixes minimizer methods that don't comply.
Closes #13001

closes #13001

+1 though the messages still reads a bit cryptic.
By the way, moved the Github closing instruction to the description to make it work.

The LBFGS message is cryptic, or the commit message is cryptic?

The LBFGS messages but I guess they have been there for quite a while now.

plain assert is ok now, it doesn't get optimised away. I prefer this style.

@andyfaff Thanks for the quick response!


[Ubuntu 16.04] libGL error when trying to play the game

when I run the python3 -m gfootball.play_game , error shows that:
libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: swrast
Couldn't load GL function glBegin: No GL driver has been loaded

Also happen in python3 -m gfootball.examples.run_ppo2 --dump_full_episodes=True --render=True
But when I try another pygame example python3 -m pygame.examples.aliens , it works

This looks like the issue with OpenGL. AFAIK other pygames are not using it for rendering, therefore might be running fine.
Can you try running "glxgears" (or "glgears") program ?
(this is a standalone tool for verifying if opengl is working correctly).
Also - please mention what version of the system you have.

I am also facing the same issue. I can confirm that glxinfo, glxgears are working fine for me.

What linux version are you running ? How did you install the football environment ?
The fact that glxgears is working means, that you do have a working driver (good), but now the question is, whether the football environment is using the same one.
Let's start by comparing the ".so" libraries that glxgears and the gfootball.so depends on:
ldd /usr/bin/glxgears | grep  -i gl
ldd PATH_TO_WHERE_GFOOTBALL_WAS_INSTALLED/_gameplayfootball.so | grep  -i gl
(on my machine it is in $HOME/.local/lib/python3.6/site-packages/gfootball_engine)

Yes, you're right.
ldd /usr/bin/glxgears | grep -i gl :

libGL.so.1 => /usr/lib/nvidia-410/libGL.so.1 (0x00007f237f084000)
libnvidia-glcore.so.410.104 => /usr/lib/nvidia-410/libnvidia-glcore.so.410.104 (0x00007f237c887000)

ldd build/lib.linux-x86_64-3.5/gfootball_engine/_gameplayfootball.so | grep -i gl

libwayland-egl.so.1 => /usr/lib/x86_64-linux-gnu/libwayland-egl.so.1 (0x00007f7595d83000)

glxinfo glxgears xclock works ok but it also shows the libGL error.
libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: swrast
90167 frames in 5.2 seconds = 17355.412 FPS
...

I check my OpenGL version with glxinfo | grep OpenGL, I get that :
OpenGL vendor string: Microsoft Corporation
OpenGL renderer string: GDI Generic
OpenGL version string: 1.1.0
OpenGL extensions:

OpenGL version looks too low. I use TITAN RTX and my nvidia driver is 418.56. It seems that gpu is not used.(I am not familiar with x server. Maybe I should do something with xserver configuration ?)
Also check the ldd command：
ldd /usr/bin/glxgears | grep -i gl

libGL.so.1 => /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1 (0x00007fd898553000)
libglapi.so.0 => /usr/lib/x86_64-linux-gnu/libglapi.so.0 (0x00007fd896cbf000)
libxcb-glx.so.0 => /usr/lib/x86_64-linux-gnu/libxcb-glx.so.0 (0x00007fd896287000)

ldd ./lib/python3.6/site-packages/gfootball_engine/_gameplayfootball.so | grep -i gl

libwayland-egl.so.1 => /usr/lib/x86_64-linux-gnu/libwayland-egl.so.1 (0x00007f560ab6e000)

Linux version: Ubuntu 16.04.03 LTS

Seems that many things were not linked correctly.
Here's the example output from my machine:
ldd _gameplayfootball.so | grep -i gl
libglee.so.0d1 => /usr/lib/x86_64-linux-gnu/libglee.so.0d1 (0x00007efdd0db4000)
libGL.so.1 => /usr/lib/x86_64-linux-gnu/libGL.so.1 (0x00007efdce1e3000)
libGLU.so.1 => /usr/lib/x86_64-linux-gnu/libGLU.so.1 (0x00007efdcdf74000)
libwayland-egl.so.1 => /usr/lib/x86_64-linux-gnu/libwayland-egl.so.1 (0x00007efdcb6c6000)
libGLX.so.0 => /usr/lib/x86_64-linux-gnu/libGLX.so.0 (0x00007efdc96f6000)
libGLdispatch.so.0 => /usr/lib/x86_64-linux-gnu/libGLdispatch.so.0 (0x00007efdc9440000)
Could you do:

go to gfootball/third_party/gfootball_engine
run cmake .   (notice the dot)
Please paste the output of this command and contents of CMakeFiles/game.dir/link.txt

I had the same problem.
libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: swrast
Couldn't load GL function glBegin: No GL driver has been loaded

cmake . output:
-- The C compiler identification is GNU 5.4.0
-- The CXX compiler identification is GNU 5.4.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Found OpenGL: /usr/lib/x86_64-linux-gnu/libGL.so
-- Found SDL2_image: /usr/lib/x86_64-linux-gnu/libSDL2_image.so
-- Found SDL2_ttf: /usr/lib/x86_64-linux-gnu/libSDL2_ttf.so
-- Found SDL2_gfx: /usr/lib/x86_64-linux-gnu/libSDL2_gfx.so (found version "1.0.1")
-- Found PythonLibs: /usr/lib/x86_64-linux-gnu/libpython3.5m.so (found suitable version "3.5.2", minimum required is "3")
Using Python: 3.5.2
-- Could NOT find Boost
python3-py35 not found. Trying other names.
-- Boost version: 1.58.0
-- Found the following Boost libraries:
--   python-py35
Using python_boost: python-py35
-- Looking for pthread.h
-- Looking for pthread.h - found
-- Looking for pthread_create
-- Looking for pthread_create - not found
-- Looking for pthread_create in pthreads
-- Looking for pthread_create in pthreads - not found
-- Looking for pthread_create in pthread
-- Looking for pthread_create in pthread - found
-- Found Threads: TRUE
-- Boost version: 1.58.0
-- Found the following Boost libraries:
--   system
--   thread
--   signals
--   filesystem
--   python-py35
--   chrono
--   date_time
--   atomic
-- Found SGE: /usr/lib/x86_64-linux-gnu/libSGE.so
-- Configuring done
-- Generating done
-- Build files have been written to: /home/chenjiali/football/third_party/gfootball_engine

contents of CMakeFiles/game.dir/link.txt
/usr/bin/c++  -fPIC   -fPIC -g -O3 -no-pie -L/usr/X11/lib -lX11 -lSDL2  -shared -Wl,-soname,libgame.so -o libgame.so CMakeFiles/game.dir/src/cmake/backtrace.cpp.o CMakeFi    les/game.dir/src/cmake/helpers.cpp.o CMakeFiles/game.dir/src/misc/perlin.cpp.o CMakeFiles/game.dir/src/misc/hungarian.c.o CMakeFiles/game.dir/src/gametask.cpp.o CMakeFile    s/game.dir/src/utils.cpp.o CMakeFiles/game.dir/src/main.cpp.o CMakeFiles/game.dir/src/cmake/main.cpp.o CMakeFiles/game.dir/src/synchronizationTask.cpp.o CMakeFiles/game.d    ir/src/dbquery.cpp.o CMakeFiles/game.dir/src/gamedefines.cpp.o CMakeFiles/game.dir/ai.cpp.o CMakeFiles/game.dir/src/ai/ai_keyboard.cpp.o libgamelib.a libhidlib.a libmenul    ib.a libdatalib.a libleaguelib.a -lglee libblunted2.a -lrt -lboost_system -lboost_thread -lboost_signals -lboost_filesystem -lboost_python-py35 -lboost_chrono -lboost_dat    e_time -lboost_atomic -lpthread -lpython3.5m -lSDL2_image -lSDL2_ttf -lSDL2_gfx -lSGE -ldl -lm -lsqlite3 -lGLU -lGL

I think I know what's going on - this is due to the older version of the c++ compiler that you're using.
Could you please path the one-line change from:
https://github.com/google-research/football/pull/12
And try compiling and installing again.

After changing CMakeList.txt, I run cmake .:
Using Python: 3.5.2
-- Could NOT find Boost
python3-py35 not found. Trying other names.
-- Boost version: 1.58.0
-- Found the following Boost libraries:
--   python-py35
Using python_boost: python-py35
-- Boost version: 1.58.0
-- Found the following Boost libraries:
--   system
--   thread
--   signals
--   filesystem
--   python-py35
--   chrono
--   date_time
--   atomic
-- Configuring done
-- Generating done
-- Build files have been written to: /home/chenjiali/football/third_party/gfootball_engine

/usr/bin/c++  -fPIC   -fPIC -g -O3 -no-pie -L/usr/X11/lib -lX11 -lSDL2  -Wl,--no-as-needed -shared -Wl,-soname,libgame.so -o libgame.so CMakeFiles/game.dir/src/cmak    e/backtrace.cpp.o CMakeFiles/game.dir/src/cmake/helpers.cpp.o CMakeFiles/game.dir/src/misc/perlin.cpp.o CMakeFiles/game.dir/src/misc/hungarian.c.o CMakeFiles/game.d    ir/src/gametask.cpp.o CMakeFiles/game.dir/src/utils.cpp.o CMakeFiles/game.dir/src/main.cpp.o CMakeFiles/game.dir/src/cmake/main.cpp.o CMakeFiles/game.dir/src/synchr    onizationTask.cpp.o CMakeFiles/game.dir/src/dbquery.cpp.o CMakeFiles/game.dir/src/gamedefines.cpp.o CMakeFiles/game.dir/ai.cpp.o CMakeFiles/game.dir/src/ai/ai_keybo    ard.cpp.o libgamelib.a libhidlib.a libmenulib.a libdatalib.a libleaguelib.a -lglee libblunted2.a -lrt -lboost_system -lboost_thread -lboost_signals -lboost_filesyst    em -lboost_python-py35 -lboost_chrono -lboost_date_time -lboost_atomic -lpthread -lpython3.5m -lSDL2_image -lSDL2_ttf -lSDL2_gfx -lSGE -ldl -lm -lsqlite3 -lGLU -lGL

The error still exists

Can you check that the ldd started showing the GL libraries ?
Also - please make sure that your game is using the library that you've just compiled.
(the cmake/make will put the library locally, but gfootball will try to load it from the $HOME/.local/lib/python3.6/site-packages/gfootball_engine or similar location.

LABEL_DEBUG=verbose glxinfo
libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: swrast
X Error of failed request:  GLXBadContext
Major opcode of failed request:  149 (GLX)
Minor opcode of failed request:  6 (X_GLXIsDirect)
Serial number of failed request:  26
Current serial number in output stream:  25

ldd get a same result after running the new CMakeFile
ldd /usr/bin/glxgears | grep -i gl

libGL.so.1 => /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1 (0x00007f21815a1000)
libglapi.so.0 => /usr/lib/x86_64-linux-gnu/libglapi.so.0 (0x00007f217fd0d000)
libxcb-glx.so.0 => /usr/lib/x86_64-linux-gnu/libxcb-glx.so.0 (0x00007f217f2d5000)

ldd ~/anaconda3/envs/gfootball/lib/python3.6/site-packages/gfootball_engine/_gameplayfootball.so | grep -i gl

libwayland-egl.so.1 => /usr/lib/x86_64-linux-gnu/libwayland-egl.so.1 (0x00007efc6acc0000)

And libgame.so does not exist. I check this with find ~ -name libgame.so

@OneFiveChen  - sorry, I was not clear:

go to the directory where you've run the cmake / make
there should be a libgame.so there (assuming that make finished successfully)
verify that this libgame.so has additional ldd GL dependencies
copy this libgame.so to replace ~/anaconda3/envs/gfootball/lib/python3.6/site-packages/gfootball_engine/_gameplayfootball.so
check if the game works

On my side: I've verified that things work on Ubuntu with Nvidia's OpenGL driver. I'll also try to find a computer with similar setup that you have.

I got the same problem as @OneFiveChen:
The fact is that there is no libgame.so generated after adding the additional line to CMakeLists.txt and rerun cmake .  command.
Wondering how to fix it.

Now I've successfully generated the libgame.so with the correct dependencies, here is what I did:

uninstall the gfootball package
modify the CMakefileLists.txt as mentioned in #12
pip install -e .[tf_cpu] --process-dependency-links
This installation process would fail, while it does generate the libgame.so file with correct dependencies under third_party/gfootball_engine directory. 'pip -e' means install from the local .git repo, check the following link: https://stackoverflow.com/questions/14159482/pip-install-a-local-git-repository
reinstall the gfootball package using pip install gfootball[tf_cpu] --process-dependency-links
replace the [python-environment-path]/site-packages/gfootball_engine/_gameplayfootball.so with libgame.so

Though the whole process is a little bit beyond my comprehension, it did generates that important .so file @cyfra mentioned. And the dependencies look exactly like the correct one you post:
libglee.so.0d1 => /usr/lib/x86_64-linux-gnu/libglee.so.0d1 (0x00007f344bf0a000)
libGLU.so.1 => /usr/lib/x86_64-linux-gnu/libGLU.so.1 (0x00007f34493eb000)
libGL.so.1 => /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1 (0x00007f3449177000)
libglapi.so.0 => /usr/lib/x86_64-linux-gnu/libglapi.so.0 (0x00007f34460bc000)
libxcb-glx.so.0 => /usr/lib/x86_64-linux-gnu/libxcb-glx.so.0 (0x00007f344534a000)
libwayland-egl.so.1 => /usr/lib/x86_64-linux-gnu/libwayland-egl.so.1 (0x00007f3443348000)

The problem is that I still can't get the rendering engine running. It now gives me "Couldn't load GL function glBegin: Video subsystem has not been initialized" error.
I'm confused, and any advice would be welcomed.

Unfortunately it seems that my solution didn't work. Thanks for verifying it @WOWNICE  and @OneFiveChen.
I am still trying to reproduce it on one of my machines .

when I run"python3 -m gfootball.play_game"，the problem is that:
Wed Jun 26 15:36:39 2019 [Warning] in [OpenGLRenderer3D::CreateContext]: OpenGL version not equal to or higher than 3.2 (or not reported as such)
shader compilation error (media/shaders/simple.vert)
Wed Jun 26 15:36:39 2019 [Warning] in [::LoadGLShader]: shader compilation error (media/shaders/simple.vert)
shader compilation info: 0:1(10): error: GLSL 1.50 is not supported. Supported versions are: 1.10, 1.20, 1.30, 1.00 ES, and 3.00 ES
......................
and when I run the "glxinfo | grep OpenGL" result is:
OpenGL vendor string: VMware, Inc.
OpenGL renderer string: SVGA3D; build: RELEASE;  LLVM;
OpenGL core profile version string: 3.3 (Core Profile) Mesa 18.0.5
OpenGL core profile shading language version string: 3.30
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 3.0 Mesa 18.0.5
OpenGL shading language version string: 1.30
OpenGL context flags: (none)
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.0 Mesa 18.0.5
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00
OpenGL ES profile extensions:
so how to upgrate it?I don't konw what to to?

@Gezx  - your case is different, and fortunately we have a workaround in FAQ in README.md
MESA_GL_VERSION_OVERRIDE=3.2 MESA_GLSL_VERSION_OVERRIDE=150 python3 -m gfootball.play_game

@cyfra Thank you! It works. I am so sorry that I don't see that.

I also ran into this same issue (Ubuntu 18.04, Cuda 10, and my OpenGL was working). I tried all the things suggested here, including the one given by @WOWNICE , but still didn't work for me. I finally got it to work, so sharing it in case it helps anyone else.
I noticed that /usr/lib/x86_64-linux-gnu/libGL.so pointed to /usr/lib/x86_64-linux-gnu/libGL.so.1.0.0 (which was a broken link). So I remove the broken link and then created a new one:
sudo rm libGL.so
sudo ln -s libGL.so.1 libGL.so
Then I went back to the root football directory and ran:
pip3 install .[tf_gpu]
and it worked.
Note that I did add the line to the CMakeLists.txt from #12 (but I don't know if it would have worked without it).

@WOWNICE @OneFiveChen @avijit9 @fedorajzf - Did the solution provided by @ranahanocka work for you?  (do you also have broken library links for some reason?)

@cyfra When I have the broken library links, I cannot even install the package. I've tried to link to different OpenGL library, but it always shows me

Couldn't load GL function glBegin: No GL driver has been loaded

Does the new version deal with this problem either?

Head version of the environment supports off screen rendering which doesn't require display. Hope many rendering issues are solved there.


Problem with dynamic routes in PROD

Error
Dynamic routes fail in ditribution build. When i click a <Link> with dynamic route have the next error:

Error is in file:
./node_modules/react-static/lib/client/methods.js
Line 16: prefetchData
In case 2: routeInfo = _context4.sent; context4.sent is html code instead of an Object

Environment

react-static -v:  v5.9.7
node -v: v8.11.1
yarn --version or npm -v: v1.9.4
Operating system: Mac OS High Sierra v10.13.6
react -v: v16.0.0

Steps to Reproduce the problem
Base your steps off of any freshly installed react-static template!

yarn run build or react-static build
deploy dist folder in prod server
onClick on <Link> with dynamic route

My code:
Paths file:
import {
  Register,
} from '../components/pages/'
import StaticRoutes from 'react-static-routes'

const Paths = (
  <Switch>
    <Route exact path="/registro" component={Register} />
    <StaticRoutes />
  </Switch>

export default Paths

My Pages index:
import universal from 'react-universal-component'

const Login = universal(import('./auth/login/'))
const Register = universal(import('./auth/register/'))

export {
  Register
}

And my App.js
const App = () => (
  <Provider store={store}>
    <Router>
      <ThemeProvider theme={theme}>

          <NavBar />

{Paths}

          <Modal />

      </ThemeProvider>
    </Router>
  </Provider>
)

export default hot(module)(App)

Could you provide a link to a basic example or repo where we can replicate this problem?

I have been able to do this, it does not give the same error but it does not load the dynamic route either
https://github.com/luisfuertes/react-static-demo

@luisfuertes have you tried adding prefetch={false} to any <Links /> referencing dynamic links? I have found this prevents errors on sites where I use them

thanks for anwer. I have tried to add but it didnt work

I am also facing this issue. Can work on it but will need some help to get started

I've figured out that this is a core issue with the prefetching
architecture in v5. Aside from rewriting v5, there won't be much we can do
other than move on to v6 where we have a new architecture that fixes this.
On Mon, Oct 22, 2018 at 5:42 AM Sharat Chandra<EMAIL_ADDRESS>wrote:

I am also facing this issue. Can work on it but will need some help to get
started
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/nozzle/react-static/issues/744#issuecomment-431810821,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFUmCbyepJp6NDEKlt3D4YEj1JFSC3j2ks5una89gaJpZM4WjZLq
.

#835 Seems to work


Upload sdist to PyPI

The PyPI entry has no PyPI-hosted downloads of Diesel -- https://pypi.python.org/pypi/diesel/3.0.16
Currently it's using a download URL to an external site, but pip seems to be deprecating that.
vagrant@ubuntu:~/dev/memcacheliked$ .tox/py26/bin/pip install diesel
Downloading/unpacking diesel
  You are installing an externally hosted file. Future versions of pip will default to disallowing externally hosted files.
   Future versions of pip will default to disallowing insecure files.
  Error <urlopen error [Errno -3] Temporary failure in name resolution> while getting http://jamwt.com/diesel/diesel-3.0.16.tar.gz (from https://pypi.python.org/simple/diesel/)
...

Bonus points for uploading wheels and/or eggs.

Uploaded 3.0.24 to PyPI.

Thanks!


Cache always missing

It shows Cache miss first then says cache duplicate. Idk if I did anything wrong with my config.
2020-12-24T15:42:49.2079329Z ##[group]Run lukka/run-vcpkg@v6
2020-12-24T15:42:49.2079872Z with:
2020-12-24T15:42:49.2080397Z   vcpkgArguments: drogon nlohmann-json
2020-12-24T15:42:49.2080984Z   vcpkgTriplet: x64-linux
2020-12-24T15:42:49.2081617Z   vcpkgDirectory: /home/runner/work/CFSPP/b/vcpkg
2020-12-24T15:42:49.2082781Z   vcpkgGitCommitId: e01668e44db57a179fd5b0b668dea7c41621f689
2020-12-24T15:42:49.2083525Z   setupOnly: false
2020-12-24T15:42:49.2084541Z   vcpkgArtifactIgnoreEntries: !.git
**/*
!installed
!/vcpkg
!vcpkg.exe
!vcpkgArtifactIgnoreEntries

2020-12-24T15:42:49.2085767Z   vcpkgGitURL: https://github.com/microsoft/vcpkg.git
2020-12-24T15:42:49.2086476Z   cleanAfterBuild: true
2020-12-24T15:42:49.2087026Z   doNotUpdateVcpkg: false
2020-12-24T15:42:49.2087531Z   useShell: true
2020-12-24T15:42:49.2087962Z   doNotCache: false
2020-12-24T15:42:49.2088365Z env:
2020-12-24T15:42:49.2088752Z   BUILD_TYPE: Release
2020-12-24T15:42:49.2089418Z ##[endgroup]
2020-12-24T15:42:49.3009871Z tool: /usr/bin/git
2020-12-24T15:42:49.3012022Z Fetching the commit id at /home/runner/work/CFSPP/b/vcpkg
2020-12-24T15:42:49.3090376Z ##[group]Restore vcpkg and its artifacts from cache
2020-12-24T15:42:49.3113462Z tool: /usr/bin/git
2020-12-24T15:42:49.3114661Z Fetching the commit id at /home/runner/work/CFSPP/b/vcpkg
2020-12-24T15:42:49.3153192Z Cache's key = 'localGitId=1046141699-args=-1457923159-os=1524360844-appendedKey=42-triplet=-1490537861'.
2020-12-24T15:42:49.3155106Z Running restore-cache...
2020-12-24T15:42:49.3728586Z Cache miss.
2020-12-24T15:42:49.3730275Z ##[endgroup]
2020-12-24T15:42:49.3736375Z ⏱ elapsed: 0.064 seconds
2020-12-24T15:42:49.3740256Z ##[group]Set output env vars
2020-12-24T15:42:49.3749308Z Set the output variable 'RUNVCPKG_VCPKG_ROOT_OUT' to value: /home/runner/work/CFSPP/b/vcpkg
2020-12-24T15:42:49.3752616Z Set the environment variable 'RUNVCPKG_VCPKG_TRIPLET' to value: x64-linux
2020-12-24T15:42:49.3753882Z Set the output variable 'RUNVCPKG_VCPKG_TRIPLET_OUT' to value: x64-linux
2020-12-24T15:42:49.3755141Z ##[endgroup]
2020-12-24T15:42:49.3759701Z ⏱ elapsed: 0.001 seconds
2020-12-24T15:42:49.3786045Z tool: /usr/bin/git
2020-12-24T15:42:49.3787161Z Fetching the commit id at /home/runner/work/CFSPP/b/vcpkg
2020-12-24T15:42:49.3839284Z fatal: not a git repository (or any of the parent directories): .git
2020-12-24T15:42:49.3850420Z ##[group]Check whether vcpkg repository is up to date
2020-12-24T15:42:49.3851850Z Checking whether vcpkg's repository is updated to commit id '' ...
2020-12-24T15:42:49.3870989Z tool: /usr/bin/git
2020-12-24T15:42:49.4235922Z fatal: /home/runner/work/CFSPP/b/vcpkg: '/home/runner/work/CFSPP/b/vcpkg' is outside repository at '/home/runner/work/CFSPP/CFSPP'
2020-12-24T15:42:49.4257273Z Current commit id of vcpkg: ''.
2020-12-24T15:42:49.4257938Z Is vcpkg repository updated? No
2020-12-24T15:42:49.4258466Z ##[endgroup]
2020-12-24T15:42:49.4259132Z ⏱ elapsed: 0.040 seconds
2020-12-24T15:42:49.4259743Z ##[group]Download vcpkg source code repository
2020-12-24T15:42:49.4261048Z Cloning vcpkg in '/home/runner/work/CFSPP/b/vcpkg'...
2020-12-24T15:42:49.4308713Z tool: /usr/bin/git
2020-12-24T15:42:49.4433696Z Cloning into '.'...
2020-12-24T15:42:53.1706122Z Note: switching to 'e01668e44db57a179fd5b0b668dea7c41621f689'.
2020-12-24T15:42:53.1706870Z
2020-12-24T15:42:53.1708139Z You are in 'detached HEAD' state. You can look around, make experimental
2020-12-24T15:42:53.1709213Z changes and commit them, and you can discard any commits you make in this
2020-12-24T15:42:53.1710183Z state without impacting any branches by switching back to a branch.
2020-12-24T15:42:53.1710646Z
2020-12-24T15:42:53.1711286Z If you want to create a new branch to retain commits you create, you may
2020-12-24T15:42:53.1712820Z do so (now or later) by using -c with the switch command. Example:
2020-12-24T15:42:53.1713366Z
2020-12-24T15:42:53.1714080Z   git switch -c <new-branch-name>
2020-12-24T15:42:53.1714759Z
2020-12-24T15:42:53.1740881Z Or undo this operation with:
2020-12-24T15:42:53.1741630Z
2020-12-24T15:42:53.1742512Z   git switch -
2020-12-24T15:42:53.1743443Z
2020-12-24T15:42:53.1744682Z Turn off this advice by setting config variable advice.detachedHead to false
2020-12-24T15:42:53.1745312Z
2020-12-24T15:42:53.1745901Z HEAD is now at e01668e44 [glbinding] Improve usage information (#15082)
2020-12-24T15:42:53.1748212Z Clone vcpkg in '/home/runner/work/CFSPP/b/vcpkg'.
2020-12-24T15:42:53.1748958Z ##[endgroup]
2020-12-24T15:42:53.1749777Z ⏱ elapsed: 3.747 seconds
2020-12-24T15:42:53.1750464Z ##[group]Build vcpkg
......
2020-12-24T15:57:33.6759859Z ⏱ elapsed: 715.379 seconds
2020-12-24T15:57:33.6760770Z ##[group]Prepare vcpkg generated file for caching
2020-12-24T15:57:33.6763880Z ##[endgroup]
2020-12-24T15:57:33.6764830Z ⏱ elapsed: 0.001 seconds
2020-12-24T15:57:33.6765674Z ##[group]Cache vcpkg and its artifacts
2020-12-24T15:57:33.6789811Z tool: /usr/bin/git
2020-12-24T15:57:33.6790799Z Fetching the commit id at /home/runner/work/CFSPP/b/vcpkg
2020-12-24T15:57:33.6841615Z e01668e44db57a179fd5b0b668dea7c41621f689
2020-12-24T15:57:33.6849438Z vcpkg identified at commitId='e01668e44db57a179fd5b0b668dea7c41621f689', adding it to the cache's key.
2020-12-24T15:57:33.6852240Z Caching paths: '/home/runner/work/CFSPP/b/vcpkg,!/home/runner/work/CFSPP/b/vcpkg/packages,!/home/runner/work/CFSPP/b/vcpkg/buildtrees,!/home/runner/work/CFSPP/b/vcpkg/downloads'
2020-12-24T15:57:33.6854276Z Running save-cache...
2020-12-24T15:57:33.7973132Z ##[warning]reserveCache failed: Cache already exists. Scope: refs/heads/master, Key: submodGitId=e01668e44db57a179fd5b0b668dea7c41621f689-args=-1457923159-os=1524360844-appendedKey=42-triplet=-1490537861, Version: 181b8bcdd0e5da289ad9e13fb5396f255ebe662e241459c93a36258eb5183758
2020-12-24T15:57:33.7998962Z ##[endgroup]
2020-12-24T15:57:33.7999947Z ⏱ elapsed: 0.119 seconds
2020-12-24T15:57:33.8000671Z run-vcpkg  action execution succeeded
2020-12-24T15:57:33.8001459Z run-vcpkg action execution succeeded

My config:
name: CMake

on: [push]

env:
  # Customize the CMake build type here (Release, Debug, RelWithDebInfo, etc.)
  BUILD_TYPE: Release

jobs:
  job:
    name: ${{ matrix.os }}-build
    runs-on: ${{ matrix.os }}
    strategy:
      fail-fast: false
      matrix:
        os: [ ubuntu-20.04 ]
        include:
          - os: ubuntu-20.04
            triplet: x64-linux
            vcpkgCommitId: 'e01668e44db57a179fd5b0b668dea7c41621f689'
            vcpkgPackages: 'drogon nlohmann-json'

    steps:
    - uses: actions/checkout@v2
    - uses<EMAIL_ADDRESS>
    # Restore from cache the previously built ports. If cache-miss, download and build vcpkg (aka "bootstrap vcpkg").
    - name: Restore from cache and install vcpkg
      # Download and build vcpkg, without installing any port. If content is cached already, it is a no-op.
      uses: lukka/run-vcpkg@v6
      with:
        vcpkgArguments: '${{ matrix.vcpkgPackages }}'
        vcpkgTriplet: '${{ matrix.triplet }}'
        vcpkgDirectory: '${{ runner.workspace }}/b/vcpkg'
        vcpkgGitCommitId: '${{ matrix.vcpkgCommitId }}'

    - name: Create Build Environment
      # Some projects don't allow in-source building, so create a separate build directory
      # We'll use this as our working directory for all subsequent commands
      run: cmake -E make_directory ${{runner.workspace}}/build

    - name: Configure CMake
      # Use a bash shell so we can use the same syntax for environment variable
      # access regardless of the host operating system
      shell: bash
      working-directory: ${{runner.workspace}}/build
      # Note the current convention is to use the -S and -B options here to specify source
      # and build directories, but this is only available with CMake 3.13 and higher.
      # The CMake binaries on the Github Actions machines are (as of this writing) 3.12
      run: cmake $GITHUB_WORKSPACE -DCMAKE_BUILD_TYPE=$BUILD_TYPE -DCMAKE_TOOLCHAIN_FILE=$VCPKG_ROOT/scripts/buildsystems/vcpkg.cmake

    - name: Link Drogon Binaries
      run: sudo ln -s ${{runner.workspace}}/b/vcpkg/packages/drogon_x64-linux/tools/drogon/drogon_ctl /usr/local/bin
      shell: bash

    - name: Build
      working-directory: ${{runner.workspace}}/build
      shell: bash
      # Execute the build.  You can specify a specific target with "--target <NAME>"
      run: cmake --build . --config $BUILD_TYPE

    - name: Upload Artifact
      uses: actions/upload-artifact@v2
      with:
        name: CFSPP-release
        path: ${{runner.workspace}}/build/CFS++

@kotori2 haven't seen the complete execution output of your workflow with the debug information, but my intuition is that there is a bug in run-vcpkg when vcpkg is not used as a Git submodule. I fixed it in this branch, please try the following in your workflow, and let me know. For further investigation a link with verbose debug output is welcome!
uses: lukka/run-vcpkg@dev/fix_key_computation

Thanks for your help. The dev branch seems caching fine.
However it seems re-installing the packages when I executing CMake. (stucking at Running vcpkg install for over 10 minutes).
2020-12-25T03:40:30.1278524Z ##[group]Restore vcpkg and its artifacts from cache
2020-12-25T03:40:30.1283879Z Cache's key = 'localGitId=1046141699-args=-1457923159-os=1524360844-appendedKey=42-triplet=-1490537861'.
2020-12-25T03:40:30.1284817Z Running restore-cache...
2020-12-25T03:40:42.6751723Z Cache Size: ~118 MB (123900714 B)
......
2020-12-25T03:40:44.5837625Z The following packages are already installed:
2020-12-25T03:40:44.5838614Z     drogon[core]:x64-linux -> 1.1.0
2020-12-25T03:40:44.5839230Z     nlohmann-json[core]:x64-linux -> 3.9.1
2020-12-25T03:40:44.5839971Z Package drogon:x64-linux is already installed
2020-12-25T03:40:44.5840819Z Package nlohmann-json:x64-linux is already installed
2020-12-25T03:40:44.5841182Z
2020-12-25T03:40:44.5841521Z Total elapsed time: 4.5 us

logs_43.zip

@kotori2 thanks for the feedback! Regarding your workflow, I have few recommendations which I could not ensure they apply to your private (and not accessible) repository:
1- have you tried to follow the best practices? i.e. having vcpkg as a Git submodule, and leveraging the vcpkg.json file to express the dependencies.
2- your private repository may contain a vcpkg.json file, that is the reason vcpkg is being run at CMake configuration time.
3- You could leverage the run-cmake to reduce the complexity of the workflow.

@lukka
I think I got the reason why they are installed twice.
run-vcpkg will try to install them in vcpkg install folder first, then they will be added to cache.
However if I add vcpkg.json, the packages will be installed in build/vcpkg_installed so that they won't be cached.
I'm curious why it will behave like this if I have vcpkg.json, because it is written your best practice page.

You could leverage the run-cmake to reduce the complexity of the workflow.

Also sorry but I didn't get what does it mean here...

@kotori2
Using lukka/run-vcpkg@v6 add in your workflow a value for additionalCachedPaths as shown in the quickstart documentation.
The problem you described should be fixed, please report it back.

@kotori2
Using lukka/run-vcpkg@v6 add in your workflow a value for additionalCachedPaths as shown in the quickstart documentation.
The problem you described should be fixed, please report it back.

It works perfectly.
Thanks for your hard work.

It works perfectly.
Thanks for your hard work.


Missing endpoint: get-playlists-tracks

Thanks for this package!
It looks like the get-playlists-tracks endpoint is not implemented, unless I'm missing it.

Never mind, I was just missing it!


Sankaku not loading

Im using the latest version of grabber and when Im trying to search anything on chan.sankakucomplex.com I just get a blank page without any pictures. idol.sankakucomplex.com is working fine trough.
Here is my log:
[11:55:31.398] Loading results...
[11:55:31.399] Loading page https://chan.sankakucomplex.com/post/index?limit=20&tags=hatsune_miku&page=1
[11:55:35.522] Loading error: Connection closed
[11:55:35.522] Loading using regex failed. Retry using rss.
[11:55:35.522] Loading error: Protocol "" is unknown
[11:55:35.522] Loading using rss failed. Retry using json.
[11:55:36.128] Loading error: Connection closed
[11:55:36.128] Loading using json failed. Retry using xml.
[11:55:37.429] Loading error: Connection closed
[11:55:37.429] No valid source of the site returned result.

Hello,
Can you access chan.sankaku directly?
The "Connection closed" message looks like either something is blocking your access to the server (firewall or censorship), or you've been banned by their server software.
Another reason could have been an invalid SSL configuration on Grabber's side (according to this), making him send SSL handshakes instead of TLS ones.

Version
Enabled

TLS 1.2
✔

TLS 1.1
✔

TLS 1.0
✔

SSL 3
❌

SSL 2
❌

However, I just tested with another server with the same Cloudflare configuration, and I could load pages with no issues, so I don't think it comes from this.
Unfortunately, chan.sankaku being blocked in France, I can't reproduce this isue.

Sankaku is blocked in my country, I can access it reloading page a fev times or enabling vpn plugin in browser. Does that mean that I must run VPN to be able to load it inside grabber?

Yes, if it's blocked you either have to set some proxy in Grabber's settings or install a VPN on your computer.


Date based restriction doesn't work with command macro

From @daniels on June 19, 2017 12:27
When trying to use a time/date based restriction from a commands macro, the DateTime or Time object passed in as a parameter is converted to an Array and then splatted against the filter method, causing an ArgumentError.
The SQL-relation :requests has a :created_at column, and Requests#expired is defined:
def expired(expiration_time=default_expiration_time)
  where{ created_at < expiration_time }
end

The commands macro is used like this:
r = Class.new(ROM::Repository[:requests])  do
  commands delete: [:by_pk, :expired]
end.new(rom)

And calling the generated method:
r.delete_expired(Time.now)
#=> ArgumentError: wrong number of arguments (given 10, expected 0..1)

Copied from original issue: rom-rb/rom-repository#93

Thanks for reporting this. I'll fix it in 1.x and port it to rom-rb/rom master.

I would like to help with this one

@GustavoCaso it's all yours (:


Add Spilling Utilities

Add SpillFile, a write-once, read-once stream for a single spill file.
Add SpillFileList, a set of SpillFiles for representing the total spill of a
partition of spilled data.
Add SpillState to represent the multi-partition spilled state of an operator
like order by, group by or hash build/probe.
Add a test for SpillState that writes multiple partitions of multiple spilled
runs and reads these back checking for correct merge of the individual sorted
runs.

Thank you, Masha. I made the suggested edits.

IndexRange is used because serializatuion takes this and not SelectivityVector. The reason for this is that serialization is either very sparse (shuffle) or all rows (gather).  This works a little better than bits.

The facebook::veloox namespace prefix is needed. Velox::test and Velox::exec::test are ambiguous. A Velox::… prefix without facebook also does not work.

Updated the PR


JsonFormatter / Add JSON Serialization Support

Add support for JSON as alternative to XML.
Pro:

Smaller Resource files
Higher data frequency than XML, but still human-readable
A good excuse to create a plugin API for adding custom serialization formats to Duality

Con:

Need to create said plugin API first in order to keep additional dependencies out of the core
Probably won't add that much of value to the user, will still need to be maintained

...or maybe use YAML instead?
Also, make sure the unit tests for serialization just use any kind of formatting that is available - whether defined in a plugin or not.

Support for custom Serializers is now part of Duality, see here. Just define your own one in a Core Plugin, and it'll be a "first-class citizen" for serialization in both core and editor. This enables projects to use their own kind of serialization, as well as multiple distinct Serializers for different purposes - such as a fast binary format without metadata and versioning for non-dev releases of the game or similar.

Closing this, as it has become a non-issue now that custom serialization can be added via plugin.


Create Letters “always-prioritise-your-health”

Automatically generated by Netlify CMS

👷 Deploy Preview for effortless-brioche-210b80 processing.

Name
Link

🔨 Latest commit
c38827ba6240fc849fa86c854a3f4428268262d4

🔍 Latest deploy log
https://app.netlify.com/sites/effortless-brioche-210b80/deploys/63e5a3ea0f5b7100084a23cd


Implement String Data Structure

Develop the String data structure for Kisumu with basic methods like concatenation and length.
Tasks:

Implement the String data structure.
Add methods for concatenation, length, and substring extraction.
Write tests to validate the functionality.

noted


Add support for .clangd as configuration root

clangd 11 added new YAML configuration format through the .clangd
configuration file. coc-clangd still doesn't support it, so, adding it.

.clangd files can also reside inside sub-directories of a project, so I am not sure it would be correct for an editor to recognize it as a workspace root. OTOH, the one for compile_flags.txt definitely makes sense.

@kadircet hmm ok.. do you suggest something? Is it better be dropped?

yes i think it is better for it to be dropped. I am not a coc expert, but
if there's a way to provide language support for the .clangd file without
marking it as a workspace root, I think that behaviour can be kept. since
clangd actually provides diagnostics for .clangd files starting with
clangd-12.
On Mon, Jul 26, 2021 at 5:02 PM Francisco Lopes @.***>
wrote:

@kadircet https://github.com/kadircet hmm ok.. do you suggest
something? Is it better be dropped?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/clangd/coc-clangd/pull/305#issuecomment-886780622,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAG3EE22SQRTI7OMCBZ6TTLTZV2HZANCNFSM5A46JLRA
.

Okay. Thanks for info.


Update scalaz-core to 7.3.3

Updates org.scalaz:scalaz-core from 7.2.32 to 7.3.3.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Applied Migrations

https://raw.githubusercontent.com/scalaz/scalazfix/v0.1.2/rules/src/main/scala/scalaz/ScalazFix.scala

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scalaz", artifactId = "scalaz-core" } ]

labels: library-update, semver-minor, scalafix-migrations

Superseded by https://github.com/coursier/coursier/pull/2330.


set label for custom/script that are not running

let's assume I have this custom module
[module/custommodule]
type = custom/script
exec = sh custommodule.sh
exec-if = anycondition
label = %output%"
interval = 1

I would like an option that lets me define a label for when this script is not running, like the label-empty option of the title module does when there is no window open.
Would it be possible to add this option?
(theoretically an exec-else option would work too)

let's assume I have this custom module
[module/custommodule]
type = custom/script
exec = sh custommodule.sh
exec-if = anycondition
label = %output%"
interval = 1

I would like an option that lets me define a label for when this script is not running, like the label-empty option of the title module does when there is no window open.
Would it be possible to add this option?
(theoretically an exec-else option would work too)

Just use the echo command or any other script that prints that label.


Deploy to the vercel pages did not work!

I try to deploy to vercel but the site didn't deploy in vercel. Did anyone else facing the same issue?
I try to deploy from the button on the markdowns of the project the button dont allow me to deploy a new project too?
Error should up:
[23:11:48.030] Running build in Washington, D.C., USA (East) – iad1
[23:11:50.360] Cloning github.com/heyjumanji/jumanjiblogs (Branch: main, Commit: 617fbbf)
[23:11:50.878] Previous build cache not available
[23:11:51.625] Cloning completed: 1.264s
[23:11:51.957] Running "vercel build"
[23:11:52.375] Vercel CLI 39.2.0
[23:11:52.758] Installing dependencies...
[23:11:56.163] ➤ YN0000: ┌ Resolution step
[23:11:56.412] ➤ YN0002: │ @algolia/autocomplete-core@npm:1.9.3 doesn't provide @algolia/client-search (pbc410), requested by @algolia/autocomplete-shared
[23:11:56.413] ➤ YN0002: │ @algolia/autocomplete-core@npm:1.9.3 doesn't provide algoliasearch (p8ad5b), requested by @algolia/autocomplete-shared
[23:11:56.413] ➤ YN0002: │ @algolia/autocomplete-core@npm:1.9.3 doesn't provide search-insights (pfdb70), requested by @algolia/autocomplete-plugin-algolia-insights
[23:11:56.413] ➤ YN0002: │ @algolia/autocomplete-plugin-algolia-insights@npm:1.9.3 [e43f4] doesn't provide @algolia/client-search (pdf3b9), requested by @algolia/autocomplete-shared
[23:11:56.414] ➤ YN0002: │ @algolia/autocomplete-plugin-algolia-insights@npm:1.9.3 [e43f4] doesn't provide algoliasearch (p0f6bb), requested by @algolia/autocomplete-shared
[23:11:56.414] ➤ YN0060: │ @contentlayer2/utils@npm:0.4.1 [2490a] provides @opentelemetry/api (p22e89) with version 1.8.0, which doesn't satisfy what @opentelemetry/core requests
[23:11:56.414] ➤ YN0060: │ @contentlayer2/utils@npm:0.4.1 [2490a] provides @opentelemetry/api (pde20c) with version 1.8.0, which doesn't satisfy what @opentelemetry/resources requests
[23:11:56.414] ➤ YN0060: │ @contentlayer2/utils@npm:0.4.1 [2490a] provides @opentelemetry/api (p18e9a) with version 1.8.0, which doesn't satisfy what @opentelemetry/sdk-trace-base requests
[23:11:56.415] ➤ YN0060: │ @contentlayer2/utils@npm:0.4.1 [2490a] provides @opentelemetry/api (p31076) with version 1.8.0, which doesn't satisfy what @opentelemetry/exporter-trace-otlp-grpc and some of its descendants request
[23:11:56.415] ➤ YN0060: │ @contentlayer2/utils@npm:0.4.1 [2490a] provides @opentelemetry/exporter-trace-otlp-grpc (pbedd1) with version 0.48.0, which doesn't satisfy what @effect-ts/otel-exporter-trace-otlp-grpc requests
[23:11:56.415] ➤ YN0002: │ @docsearch/react@npm:3.6.0 [72311] doesn't provide @algolia/client-search (pc7191), requested by @algolia/autocomplete-preset-algolia
[23:11:56.415] ➤ YN0060: │ tailwind-nextjs-starter-blog@workspace:. provides react (p923c3) with version 18.2.0, which doesn't satisfy what pliny and some of its descendants request
[23:11:56.416] ➤ YN0000: │ Some peer dependencies are incorrectly met; run yarn explain peer-requirements <hash> for details, where <hash> is the six-letter p-prefixed code
[23:11:56.417] ➤ YN0000: └ Completed in 0s 254ms
[23:11:56.478] ➤ YN0000: ┌ Fetch step
[23:13:07.806] ➤ YN0066: │ typescript@patch:typescript@npm%3A5.4.3#~builtin<compat/typescript>::version=5.4.3&hash=14eedb: Cannot apply hunk #2
[23:13:07.843] ➤ YN0013: │ 34 packages were already cached, 1075 had to be fetched
[23:13:07.848] ➤ YN0000: └ Completed in 1m 12s
[23:13:07.929] ➤ YN0000: ┌ Link step
[23:13:21.382] ➤ YN0007: │ esbuild@npm:0.20.2 must be built because it never has been before or the last one failed
[23:13:21.383] ➤ YN0007: │ protobufjs@npm:7.2.6 must be built because it never has been before or the last one failed
[23:13:21.621] ➤ YN0007: │ contentlayer2@npm:0.4.4 must be built because it never has been before or the last one failed
[23:13:24.259] ➤ YN0000: └ Completed in 16s 330ms
[23:13:24.354] ➤ YN0000: Done with warnings in 1m 29s
[23:13:24.514] Detected Next.js version: 14.1.4
[23:13:24.517] Running "yarn run build"
[23:13:25.817] Attention: Next.js now collects completely anonymous telemetry regarding usage.
[23:13:25.820] This information is used to shape Next.js' roadmap and prioritize features.
[23:13:25.820] You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL:
[23:13:25.820] https://nextjs.org/telemetry
[23:13:25.821]
[23:13:25.905]    ▲ Next.js 14.1.4
[23:13:25.906]    - Environments: .env
[23:13:25.906]
[23:13:25.979]    Creating an optimized production build ...
[23:13:27.729] (node:563) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
[23:13:27.729] (Use `node --trace-deprecation ...` to show where the warning was created)
[23:13:29.244] successCallback /vercel/path0/.contentlayer
[23:13:29.269] SuccessCallbackError {
[23:13:29.269]   error: SyntaxError: Unexpected identifier 'assert'
[23:13:29.270]       at compileSourceTextModule (node:internal/modules/esm/utils:338:16)
[23:13:29.270]       at ModuleLoader.moduleStrategy (node:internal/modules/esm/translators:102:18)
[23:13:29.270]       at ModuleLoader.#translate (node:internal/modules/esm/loader:437:12)
[23:13:29.270]       at ModuleLoader.loadAndTranslate (node:internal/modules/esm/loader:484:27)
[23:13:29.270]       at ModuleJob._link (node:internal/modules/esm/module_job:115:19),
[23:13:29.270]   _tag: 'SuccessCallbackError',
[23:13:29.270]   toString: [Function (anonymous)],
[23:13:29.270]   [Symbol()]: {
[23:13:29.270]     error: SyntaxError: Unexpected identifier 'assert'
[23:13:29.270]         at compileSourceTextModule (node:internal/modules/esm/utils:338:16)
[23:13:29.270]         at ModuleLoader.moduleStrategy (node:internal/modules/esm/translators:102:18)
[23:13:29.270]         at ModuleLoader.#translate (node:internal/modules/esm/loader:437:12)
[23:13:29.270]         at ModuleLoader.loadAndTranslate (node:internal/modules/esm/loader:484:27)
[23:13:29.270]         at ModuleJob._link (node:internal/modules/esm/module_job:115:19)
[23:13:29.270]   },
[23:13:29.270]   [Symbol()]: [ 'error' ]
[23:13:29.270] }
[23:13:29.339] Error: Command "yarn run build" exited with 1
[23:13:29.769]

I found the same issue, here is my solution that works.
Replace this statement in scripts/rss.mjs:
import tagData from '../app/tag-data.json' assert { type: 'json' };

With these statements:
import fs from 'fs'
const tagData = JSON.parse(
  fs.readFileSync(new URL('../app/tag-data.json', import.meta.url), 'utf-8')
)

I think the root cause is the experimental feature in JavaScript that may not be fully supported by certain Node.js environments in Vercel.

I have replaced as you said but i got another error!
The replacement i did here:
import { writeFileSync, mkdirSync } from 'fs'
import path from 'path'
import { slug } from 'github-slugger'
import { escape } from 'pliny/utils/htmlEscaper.js'
import siteMetadata from '../data/siteMetadata.js'
import fs from 'fs'
const tagData = JSON.parse(
  fs.readFileSync(new URL('../app/tag-data.json', import.meta.url), 'utf-8')
)
import { allBlogs } from '../.contentlayer/generated/index.mjs'
import { sortPosts } from 'pliny/utils/contentlayer.js'

const generateRssItem = (config, post) => `
  <item>
    <guid>${config.siteUrl}/blog/${post.slug}</guid>
    <title>${escape(post.title)}</title>
    <link>${config.siteUrl}/blog/${post.slug}</link>
    ${post.summary && `<description>${escape(post.summary)}</description>`}
    <pubDate>${new Date(post.date).toUTCString()}</pubDate>
    <author>${config.email} (${config.author})</author>
    ${post.tags && post.tags.map((t) => `<category>${t}</category>`).join('')}
  </item>
`

const generateRss = (config, posts, page = 'feed.xml') => `
  <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
      <title>${escape(config.title)}</title>
      <link>${config.siteUrl}/blog</link>
      <description>${escape(config.description)}</description>
      <language>${config.language}</language>
      <managingEditor>${config.email} (${config.author})</managingEditor>
      <webMaster>${config.email} (${config.author})</webMaster>
      <lastBuildDate>${new Date(posts[0].date).toUTCString()}</lastBuildDate>
      <atom:link href="${config.siteUrl}/${page}" rel="self" type="application/rss+xml"/>
      ${posts.map((post) => generateRssItem(config, post)).join('')}
    </channel>
  </rss>
`

async function generateRSS(config, allBlogs, page = 'feed.xml') {
  const publishPosts = allBlogs.filter((post) => post.draft !== true)
  // RSS for blog post
  if (publishPosts.length > 0) {
    const rss = generateRss(config, sortPosts(publishPosts))
    writeFileSync(`./public/${page}`, rss)
  }

  if (publishPosts.length > 0) {
    for (const tag of Object.keys(tagData)) {
      const filteredPosts = allBlogs.filter((post) =>
        post.tags.map((t) => slug(t)).includes(tag)
      )
      const rss = generateRss(config, filteredPosts, `tags/${tag}/${page}`)
      const rssPath = path.join('public', 'tags', tag)
      mkdirSync(rssPath, { recursive: true })
      writeFileSync(path.join(rssPath, page), rss)
    }
  }
}

const rss = () => {
  generateRSS(siteMetadata, allBlogs)
  console.log('RSS feed generated...')
}
export default rss

The error i got:
[01:03:00.770] Running build in Washington, D.C., USA (East) – iad1
[01:03:00.877] Cloning github.com/heyjumanji/jumanjiblogs (Branch: main, Commit: 8567704)
[01:03:01.672] Previous build cache not available
[01:03:02.262] Cloning completed: 1.385s
[01:03:02.567] Running "vercel build"
[01:03:03.003] Vercel CLI 39.2.0
[01:03:03.387] Installing dependencies...
[01:03:04.196] ➤ YN0000: ┌ Resolution step
[01:03:04.440] ➤ YN0002: │ @algolia/autocomplete-core@npm:1.9.3 doesn't provide @algolia/client-search (pbc410), requested by @algolia/autocomplete-shared
[01:03:04.442] ➤ YN0002: │ @algolia/autocomplete-core@npm:1.9.3 doesn't provide algoliasearch (p8ad5b), requested by @algolia/autocomplete-shared
[01:03:04.443] ➤ YN0002: │ @algolia/autocomplete-core@npm:1.9.3 doesn't provide search-insights (pfdb70), requested by @algolia/autocomplete-plugin-algolia-insights
[01:03:04.443] ➤ YN0002: │ @algolia/autocomplete-plugin-algolia-insights@npm:1.9.3 [e43f4] doesn't provide @algolia/client-search (pdf3b9), requested by @algolia/autocomplete-shared
[01:03:04.443] ➤ YN0002: │ @algolia/autocomplete-plugin-algolia-insights@npm:1.9.3 [e43f4] doesn't provide algoliasearch (p0f6bb), requested by @algolia/autocomplete-shared
[01:03:04.443] ➤ YN0060: │ @contentlayer2/utils@npm:0.4.1 [2490a] provides @opentelemetry/api (p22e89) with version 1.8.0, which doesn't satisfy what @opentelemetry/core requests
[01:03:04.444] ➤ YN0060: │ @contentlayer2/utils@npm:0.4.1 [2490a] provides @opentelemetry/api (pde20c) with version 1.8.0, which doesn't satisfy what @opentelemetry/resources requests
[01:03:04.444] ➤ YN0060: │ @contentlayer2/utils@npm:0.4.1 [2490a] provides @opentelemetry/api (p18e9a) with version 1.8.0, which doesn't satisfy what @opentelemetry/sdk-trace-base requests
[01:03:04.444] ➤ YN0060: │ @contentlayer2/utils@npm:0.4.1 [2490a] provides @opentelemetry/api (p31076) with version 1.8.0, which doesn't satisfy what @opentelemetry/exporter-trace-otlp-grpc and some of its descendants request
[01:03:04.444] ➤ YN0060: │ @contentlayer2/utils@npm:0.4.1 [2490a] provides @opentelemetry/exporter-trace-otlp-grpc (pbedd1) with version 0.48.0, which doesn't satisfy what @effect-ts/otel-exporter-trace-otlp-grpc requests
[01:03:04.444] ➤ YN0002: │ @docsearch/react@npm:3.6.0 [72311] doesn't provide @algolia/client-search (pc7191), requested by @algolia/autocomplete-preset-algolia
[01:03:04.445] ➤ YN0060: │ tailwind-nextjs-starter-blog@workspace:. provides react (p923c3) with version 18.2.0, which doesn't satisfy what pliny and some of its descendants request
[01:03:04.445] ➤ YN0000: │ Some peer dependencies are incorrectly met; run yarn explain peer-requirements <hash> for details, where <hash> is the six-letter p-prefixed code
[01:03:04.445] ➤ YN0000: └ Completed in 0s 249ms
[01:03:04.506] ➤ YN0000: ┌ Fetch step
[01:04:14.671] ➤ YN0066: │ typescript@patch:typescript@npm%3A5.4.3#~builtin<compat/typescript>::version=5.4.3&hash=14eedb: Cannot apply hunk #2
[01:04:14.725] ➤ YN0013: │ 34 packages were already cached, 1075 had to be fetched
[01:04:14.729] ➤ YN0000: └ Completed in 1m 11s
[01:04:14.780] ➤ YN0000: ┌ Link step
[01:04:28.341] ➤ YN0007: │ esbuild@npm:0.20.2 must be built because it never has been before or the last one failed
[01:04:28.342] ➤ YN0007: │ protobufjs@npm:7.2.6 must be built because it never has been before or the last one failed
[01:04:28.585] ➤ YN0007: │ contentlayer2@npm:0.4.4 must be built because it never has been before or the last one failed
[01:04:30.231] ➤ YN0000: └ Completed in 15s 452ms
[01:04:30.328] ➤ YN0000: Done with warnings in 1m 27s
[01:04:30.533] Detected Next.js version: 14.1.4
[01:04:30.535] Running "next build"
[01:04:31.139] Attention: Next.js now collects completely anonymous telemetry regarding usage.
[01:04:31.139] This information is used to shape Next.js' roadmap and prioritize features.
[01:04:31.139] You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL:
[01:04:31.139] https://nextjs.org/telemetry
[01:04:31.139]
[01:04:31.230]    ▲ Next.js 14.1.4
[01:04:31.231]    - Environments: .env
[01:04:31.231]
[01:04:31.305]    Creating an optimized production build ...
[01:04:33.125] (node:532) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
[01:04:33.126] (Use `node --trace-deprecation ...` to show where the warning was created)
[01:04:34.639] successCallback /vercel/path0/.contentlayer
[01:04:34.668] SuccessCallbackError {
[01:04:34.668]   error: SyntaxError: Unexpected identifier 'assert'
[01:04:34.668]       at compileSourceTextModule (node:internal/modules/esm/utils:338:16)
[01:04:34.669]       at ModuleLoader.moduleStrategy (node:internal/modules/esm/translators:102:18)
[01:04:34.669]       at ModuleLoader.#translate (node:internal/modules/esm/loader:437:12)
[01:04:34.670]       at ModuleLoader.loadAndTranslate (node:internal/modules/esm/loader:484:27)
[01:04:34.670]       at ModuleJob._link (node:internal/modules/esm/module_job:115:19),
[01:04:34.673]   _tag: 'SuccessCallbackError',
[01:04:34.673]   toString: [Function (anonymous)],
[01:04:34.673]   [Symbol()]: {
[01:04:34.673]     error: SyntaxError: Unexpected identifier 'assert'
[01:04:34.673]         at compileSourceTextModule (node:internal/modules/esm/utils:338:16)
[01:04:34.673]         at ModuleLoader.moduleStrategy (node:internal/modules/esm/translators:102:18)
[01:04:34.673]         at ModuleLoader.#translate (node:internal/modules/esm/loader:437:12)
[01:04:34.674]         at ModuleLoader.loadAndTranslate (node:internal/modules/esm/loader:484:27)
[01:04:34.674]         at ModuleJob._link (node:internal/modules/esm/module_job:115:19)
[01:04:34.674]   },
[01:04:34.674]   [Symbol()]: [ 'error' ]
[01:04:34.674] }
[01:04:34.705] Error: Command "next build" exited with 1
[01:04:35.051]

I found the same issue, here is my solution that works.
Replace this statement in scripts/rss.mjs:
import tagData from '../app/tag-data.json' assert { type: 'json' };

With these statements:
import fs from 'fs'
const tagData = JSON.parse(
  fs.readFileSync(new URL('../app/tag-data.json', import.meta.url), 'utf-8')
)

I think the root cause is the experimental feature in JavaScript that may not be fully supported by certain Node.js environments in Vercel.

I have replaced as you said but i got another error!
The replacement i did here:
import { writeFileSync, mkdirSync } from 'fs'
import path from 'path'
import { slug } from 'github-slugger'
import { escape } from 'pliny/utils/htmlEscaper.js'
import siteMetadata from '../data/siteMetadata.js'
import fs from 'fs'
const tagData = JSON.parse(
  fs.readFileSync(new URL('../app/tag-data.json', import.meta.url), 'utf-8')
)
import { allBlogs } from '../.contentlayer/generated/index.mjs'
import { sortPosts } from 'pliny/utils/contentlayer.js'

const generateRssItem = (config, post) => `
  <item>
    <guid>${config.siteUrl}/blog/${post.slug}</guid>
    <title>${escape(post.title)}</title>
    <link>${config.siteUrl}/blog/${post.slug}</link>
    ${post.summary && `<description>${escape(post.summary)}</description>`}
    <pubDate>${new Date(post.date).toUTCString()}</pubDate>
    <author>${config.email} (${config.author})</author>
    ${post.tags && post.tags.map((t) => `<category>${t}</category>`).join('')}
  </item>
`

const generateRss = (config, posts, page = 'feed.xml') => `
  <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
      <title>${escape(config.title)}</title>
      <link>${config.siteUrl}/blog</link>
      <description>${escape(config.description)}</description>
      <language>${config.language}</language>
      <managingEditor>${config.email} (${config.author})</managingEditor>
      <webMaster>${config.email} (${config.author})</webMaster>
      <lastBuildDate>${new Date(posts[0].date).toUTCString()}</lastBuildDate>
      <atom:link href="${config.siteUrl}/${page}" rel="self" type="application/rss+xml"/>
      ${posts.map((post) => generateRssItem(config, post)).join('')}
    </channel>
  </rss>
`

async function generateRSS(config, allBlogs, page = 'feed.xml') {
  const publishPosts = allBlogs.filter((post) => post.draft !== true)
  // RSS for blog post
  if (publishPosts.length > 0) {
    const rss = generateRss(config, sortPosts(publishPosts))
    writeFileSync(`./public/${page}`, rss)
  }

  if (publishPosts.length > 0) {
    for (const tag of Object.keys(tagData)) {
      const filteredPosts = allBlogs.filter((post) =>
        post.tags.map((t) => slug(t)).includes(tag)
      )
      const rss = generateRss(config, filteredPosts, `tags/${tag}/${page}`)
      const rssPath = path.join('public', 'tags', tag)
      mkdirSync(rssPath, { recursive: true })
      writeFileSync(path.join(rssPath, page), rss)
    }
  }
}

const rss = () => {
  generateRSS(siteMetadata, allBlogs)
  console.log('RSS feed generated...')
}
export default rss

The error i got:
[01:03:00.770] Running build in Washington, D.C., USA (East) – iad1
[01:03:00.877] Cloning github.com/heyjumanji/jumanjiblogs (Branch: main, Commit: 8567704)
[01:03:01.672] Previous build cache not available
[01:03:02.262] Cloning completed: 1.385s
[01:03:02.567] Running "vercel build"
[01:03:03.003] Vercel CLI 39.2.0
[01:03:03.387] Installing dependencies...
[01:03:04.196] ➤ YN0000: ┌ Resolution step
[01:03:04.440] ➤ YN0002: │ @algolia/autocomplete-core@npm:1.9.3 doesn't provide @algolia/client-search (pbc410), requested by @algolia/autocomplete-shared
[01:03:04.442] ➤ YN0002: │ @algolia/autocomplete-core@npm:1.9.3 doesn't provide algoliasearch (p8ad5b), requested by @algolia/autocomplete-shared
[01:03:04.443] ➤ YN0002: │ @algolia/autocomplete-core@npm:1.9.3 doesn't provide search-insights (pfdb70), requested by @algolia/autocomplete-plugin-algolia-insights
[01:03:04.443] ➤ YN0002: │ @algolia/autocomplete-plugin-algolia-insights@npm:1.9.3 [e43f4] doesn't provide @algolia/client-search (pdf3b9), requested by @algolia/autocomplete-shared
[01:03:04.443] ➤ YN0002: │ @algolia/autocomplete-plugin-algolia-insights@npm:1.9.3 [e43f4] doesn't provide algoliasearch (p0f6bb), requested by @algolia/autocomplete-shared
[01:03:04.443] ➤ YN0060: │ @contentlayer2/utils@npm:0.4.1 [2490a] provides @opentelemetry/api (p22e89) with version 1.8.0, which doesn't satisfy what @opentelemetry/core requests
[01:03:04.444] ➤ YN0060: │ @contentlayer2/utils@npm:0.4.1 [2490a] provides @opentelemetry/api (pde20c) with version 1.8.0, which doesn't satisfy what @opentelemetry/resources requests
[01:03:04.444] ➤ YN0060: │ @contentlayer2/utils@npm:0.4.1 [2490a] provides @opentelemetry/api (p18e9a) with version 1.8.0, which doesn't satisfy what @opentelemetry/sdk-trace-base requests
[01:03:04.444] ➤ YN0060: │ @contentlayer2/utils@npm:0.4.1 [2490a] provides @opentelemetry/api (p31076) with version 1.8.0, which doesn't satisfy what @opentelemetry/exporter-trace-otlp-grpc and some of its descendants request
[01:03:04.444] ➤ YN0060: │ @contentlayer2/utils@npm:0.4.1 [2490a] provides @opentelemetry/exporter-trace-otlp-grpc (pbedd1) with version 0.48.0, which doesn't satisfy what @effect-ts/otel-exporter-trace-otlp-grpc requests
[01:03:04.444] ➤ YN0002: │ @docsearch/react@npm:3.6.0 [72311] doesn't provide @algolia/client-search (pc7191), requested by @algolia/autocomplete-preset-algolia
[01:03:04.445] ➤ YN0060: │ tailwind-nextjs-starter-blog@workspace:. provides react (p923c3) with version 18.2.0, which doesn't satisfy what pliny and some of its descendants request
[01:03:04.445] ➤ YN0000: │ Some peer dependencies are incorrectly met; run yarn explain peer-requirements <hash> for details, where <hash> is the six-letter p-prefixed code
[01:03:04.445] ➤ YN0000: └ Completed in 0s 249ms
[01:03:04.506] ➤ YN0000: ┌ Fetch step
[01:04:14.671] ➤ YN0066: │ typescript@patch:typescript@npm%3A5.4.3#~builtin<compat/typescript>::version=5.4.3&hash=14eedb: Cannot apply hunk #2
[01:04:14.725] ➤ YN0013: │ 34 packages were already cached, 1075 had to be fetched
[01:04:14.729] ➤ YN0000: └ Completed in 1m 11s
[01:04:14.780] ➤ YN0000: ┌ Link step
[01:04:28.341] ➤ YN0007: │ esbuild@npm:0.20.2 must be built because it never has been before or the last one failed
[01:04:28.342] ➤ YN0007: │ protobufjs@npm:7.2.6 must be built because it never has been before or the last one failed
[01:04:28.585] ➤ YN0007: │ contentlayer2@npm:0.4.4 must be built because it never has been before or the last one failed
[01:04:30.231] ➤ YN0000: └ Completed in 15s 452ms
[01:04:30.328] ➤ YN0000: Done with warnings in 1m 27s
[01:04:30.533] Detected Next.js version: 14.1.4
[01:04:30.535] Running "next build"
[01:04:31.139] Attention: Next.js now collects completely anonymous telemetry regarding usage.
[01:04:31.139] This information is used to shape Next.js' roadmap and prioritize features.
[01:04:31.139] You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL:
[01:04:31.139] https://nextjs.org/telemetry
[01:04:31.139]
[01:04:31.230]    ▲ Next.js 14.1.4
[01:04:31.231]    - Environments: .env
[01:04:31.231]
[01:04:31.305]    Creating an optimized production build ...
[01:04:33.125] (node:532) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
[01:04:33.126] (Use `node --trace-deprecation ...` to show where the warning was created)
[01:04:34.639] successCallback /vercel/path0/.contentlayer
[01:04:34.668] SuccessCallbackError {
[01:04:34.668]   error: SyntaxError: Unexpected identifier 'assert'
[01:04:34.668]       at compileSourceTextModule (node:internal/modules/esm/utils:338:16)
[01:04:34.669]       at ModuleLoader.moduleStrategy (node:internal/modules/esm/translators:102:18)
[01:04:34.669]       at ModuleLoader.#translate (node:internal/modules/esm/loader:437:12)
[01:04:34.670]       at ModuleLoader.loadAndTranslate (node:internal/modules/esm/loader:484:27)
[01:04:34.670]       at ModuleJob._link (node:internal/modules/esm/module_job:115:19),
[01:04:34.673]   _tag: 'SuccessCallbackError',
[01:04:34.673]   toString: [Function (anonymous)],
[01:04:34.673]   [Symbol()]: {
[01:04:34.673]     error: SyntaxError: Unexpected identifier 'assert'
[01:04:34.673]         at compileSourceTextModule (node:internal/modules/esm/utils:338:16)
[01:04:34.673]         at ModuleLoader.moduleStrategy (node:internal/modules/esm/translators:102:18)
[01:04:34.673]         at ModuleLoader.#translate (node:internal/modules/esm/loader:437:12)
[01:04:34.674]         at ModuleLoader.loadAndTranslate (node:internal/modules/esm/loader:484:27)
[01:04:34.674]         at ModuleJob._link (node:internal/modules/esm/module_job:115:19)
[01:04:34.674]   },
[01:04:34.674]   [Symbol()]: [ 'error' ]
[01:04:34.674] }
[01:04:34.705] Error: Command "next build" exited with 1
[01:04:35.051]

I am getting this identical error, haven't been able to find a fix. If I figure anything out I will post back here.

I found a solution that worked for me. On Vercel, go to your project settings for your page and change the Node.js version to 20.X, if that matches the version of node you have.  https://vercel.com/docs/functions/runtimes/node-js/node-js-versions

@alexsalce omg you are awesome, thank you so much! it works for me perfectly and the site back to online and working normal.
Changing the node to *20.x in vercel project settings make it fix the deployment issue.


Add dependency between nova-compute and vaultlocker

If vaultlocker fails to decrypt and mount
/var/lib/nova/instances, nova will start anyway
and may create instances with their disks on the
root filesystem's disk, which may not be encrypted.
This patch creates a dependency between the nova-compute
and vaultlocker services, so if vaultlocker fails
nova-compute will not be started.
Closes-bug: #1863358

I think this specialises vaultlocker towards nova-compute to much.
Would an alternative approach be to use overrides on the nova-compute systemd configuration to ensure that it runs after the required vaultlocker units have been started successfully?


Adds y-ticks and axes left of schedule plot

Summary
Fixes #3502
Details and comments
When plotting pulse schedules, display the y ticks scaled along the left side of plot.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


[Backport kirkstone-next] add greengrass-lite, non release version

Description
Backport of #10689 to kirkstone-next.

CMake 3.25 or higher is required.  You are running version 3.22.3


Harmonize usage docs

Make a pass for consistency such as:

primacy of Folders vs States
usage of colons and quotes
usage of bullet points
usage of backtick quoted material

capitalization

@naglepuff Would you care to do a read-through of the docs and see if any of these need adjusting?  If so, please make a PR.  If not, please close this issue.

Sure, will do.


a simple python sdk

A simple python sdk based on rest server api.
Support the following method:
start: start a job
stop: stop a job
get state: get the state of the given job

Coverage increased (+20.2%) to 73.211% when pulling b21895d911ac893e93fac0e928ab505f450c52e1 on yuqian/simple_python_sdk into b377583a5db89e80438c024fadbd46f885d6c77b on contrib.


Fix Idempotence issue for RHEL 7 forwarder install

I could really use a second pair of 👀 on this.  I was sifting through the issues on github for this module and noticed someone having a problem a RHEL 7.  While i was not able to reproduce their issue specifically ( i assume it's fixed ) i did notice the idempotence test for the forwarder is failing when run under beaker.  I know pretty much nothing about se_linux on RHEL 7 but what i do know is the following attribute on the file resource solves the forwarder idempotence test.  Could anyone verify this fix is indeed valid?
FYI.  Here is the failing beaker test without this change.
First Run
  Info: Loading facts
  Info: Loading facts
  Warning: /etc/puppetlabs/puppet/hiera.yaml: Use of 'hiera.yaml' version 3 is deprecated. It should be converted to version 5
     (in /etc/puppetlabs/puppet/hiera.yaml)
  Notice: Compiled catalog for rhel-74-x64.attlocal.net in environment production in 0.46 seconds
  Info: Applying configuration version '1507523793'
  Notice: /Stage[main]/Archive::Staging/File[/opt/staging]/ensure: created
  Notice: /Stage[main]/Splunk::Forwarder/Archive[/opt/staging/splunk/splunkforwarder-7.0.0-c8a78efdd40f-linux-2.6-x86_64.rpm]/ensure: download archive from https://download.splunk.com/products/universalforwarder/releases/7.0.0/linux/splunkforwarder-7.0.0-c8a78efdd40f-linux-2.6-x86_64.rpm to /opt/staging/splunk/splunkforwarder-7.0.0-c8a78efdd40f-linux-2.6-x86_64.rpm  with cleanup
  Notice: /Stage[main]/Splunk::Forwarder/Package[splunkforwarder]/ensure: created
  Notice: /Stage[main]/Splunk::Forwarder/Splunkforwarder_input[default_host]/ensure: created
  Info: /Stage[main]/Splunk::Forwarder/Splunkforwarder_input[default_host]: Scheduling refresh of Service[splunk]
  Notice: /Stage[main]/Splunk::Forwarder/Splunkforwarder_output[tcpout_defaultgroup]/ensure: created
  Info: /Stage[main]/Splunk::Forwarder/Splunkforwarder_output[tcpout_defaultgroup]: Scheduling refresh of Service[splunk]
  Notice: /Stage[main]/Splunk::Forwarder/Splunkforwarder_output[defaultgroup_server]/ensure: created
  Info: /Stage[main]/Splunk::Forwarder/Splunkforwarder_output[defaultgroup_server]: Scheduling refresh of Service[splunk]
  Notice: /Stage[main]/Splunk::Forwarder/Splunkforwarder_web[forwarder_splunkd_port]/ensure: created
  Info: /Stage[main]/Splunk::Forwarder/Splunkforwarder_web[forwarder_splunkd_port]: Scheduling refresh of Service[splunk]
  Notice: /Stage[main]/Splunk::Forwarder/File[/opt/splunkforwarder/etc/system/local/deploymentclient.conf]/ensure: created
  Notice: /Stage[main]/Splunk::Forwarder/File[/opt/splunkforwarder/etc/system/local/inputs.conf]/mode: mode changed '0644' to '0600'
  Notice: /Stage[main]/Splunk::Forwarder/File[/opt/splunkforwarder/etc/system/local/inputs.conf]/seluser: seluser changed 'unconfined_u' to 'system_u'
  Notice: /Stage[main]/Splunk::Forwarder/File[/opt/splunkforwarder/etc/system/local/outputs.conf]/mode: mode changed '0644' to '0600'
  Notice: /Stage[main]/Splunk::Forwarder/File[/opt/splunkforwarder/etc/system/local/outputs.conf]/seluser: seluser changed 'unconfined_u' to 'system_u'
  Notice: /Stage[main]/Splunk::Forwarder/File[/opt/splunkforwarder/etc/system/local/web.conf]/mode: mode changed '0644' to '0600'
  Notice: /Stage[main]/Splunk::Forwarder/File[/opt/splunkforwarder/etc/system/local/web.conf]/seluser: seluser changed 'unconfined_u' to 'system_u'
  Notice: /Stage[main]/Splunk::Forwarder/File[/opt/splunkforwarder/etc/system/local/limits.conf]/ensure: created
  Notice: /Stage[main]/Splunk::Forwarder/File[/opt/splunkforwarder/etc/system/local/server.conf]/ensure: created
  Notice: /Stage[main]/Splunk::Platform::Posix/Exec[license_splunkforwarder]/returns: executed successfully
  Notice: /Stage[main]/Splunk::Platform::Posix/Exec[enable_splunkforwarder]/returns: executed successfully
  Info: /Stage[main]/Splunk::Platform::Posix/Exec[enable_splunkforwarder]: Scheduling refresh of Service[splunk]
  Notice: /Stage[main]/Splunk::Virtual/Service[splunk]/ensure: ensure changed 'stopped' to 'running'
  Info: /Stage[main]/Splunk::Virtual/Service[splunk]: Unscheduling refresh on Service[splunk]
  Info: Creating state file /opt/puppetlabs/puppet/cache/state/state.yaml
  Notice: Applied catalog in 10.79 seconds

Second run
  Info: Loading facts
  Info: Loading facts
  Warning: /etc/puppetlabs/puppet/hiera.yaml: Use of 'hiera.yaml' version 3 is deprecated. It should be converted to version 5
     (in /etc/puppetlabs/puppet/hiera.yaml)
  Notice: Compiled catalog for rhel-74-x64.attlocal.net in environment production in 0.44 seconds
  Info: Applying configuration version '1507523806'
  Notice: /Stage[main]/Splunk::Forwarder/File[/opt/splunkforwarder/etc/system/local/server.conf]/seluser: seluser changed 'unconfined_u' to 'system_u'
  Notice: Applied catalog in 0.17 seconds

mh I've no idea. @vinzent @oranenj can you help us out here?

Hard to tell what's going on without actually testing the module myself, but my initial guess is that something changes the SELinux policy while puppet is running (eg. one of the packages it installs) so that on the next run, the file contexts for that particular path are different than on the first run and puppet corrects them.
To see which is "correct", run restorecon on that path. If it changes from unconfined_u to system_u, then that's what the policy declares and the puppet code should probably default to that too.

I'm also not sure, but what @oranenj says makes sense (if the settings are coming from the package rather than from Puppet, you could also try looking at the rpm's scripts).

I'll give this a shot.


New payment processor

Please add new payment processors like Paddle or Paypal so that the payments could be more configurable.
Thnaks!

I have no plans to add additional payment providers but feel free to fork and add it to your own app.


Discussion: Alternative Approach to Handling Mutation Errors

Hi strawberry-django team,
First, I just want to say how much I appreciate the work you’re doing! I’ve been following the development of Strawberry closely, and I am already using it in a number of projects.  Having just updated a couple of projects to the latest version I noticed that Strawberry is now using a generic approach to handle mutation errors, such as:
type OperationMessage {
  kind: OperationMessageKind!
  message: String!
  field: String
  code: String
}

This seems like a flexible way to handle a wide variety of errors with a minimal schema. However, since you've not yet released a 1.0 version, I wanted to start a conversation around this choice and share a different approach that I’ve found useful in production, particularly for its explicitness and flexibility. (I started using this solution before there were docs written for strawberry-django).
I use an InputError interface, which allows for specific error types like ValidationError, NotAuthenticatedError, etc.:
interface InputError {
  message: String!
}

type ValidationError implements InputError {
  message: String!
  fields: [FieldError!]!
}

type FieldError {
  field: String!
  messages: [String!]!
}

type NotAuthenticatedError implements InputError {
  message: String!
}

type NotAuthorisedError implements InputError {
  message: String!
}

type DoesNotExistError implements InputError {
  message: String!
}

# And you can create your own specific types.
type OurCustomError implements InputError {
  message: String!
  libraryId: Int!
}

I like this approach because:

It ensures all errors have a common message field, which can be easily queried (... on InputError { message }).
It allows for more granular error types, where I can query additional specific fields (e.g., ... on ValidationError { fields { field, messages } }).
Using __typename on the frontend allows me to handle each error type with specific UI responses.
Errors are strongly typed and explicit.

I’d love to hear your thoughts on the merits of both approaches. I’m curious about the design decisions that led to the current generic error handling and whether there’s room for considering more specific error types down the road.  Or are there issues with my approach that make it unfeasible?
Looking forward to your thoughts and discussion!
Thanks again for all the hard work.

Upvote & Fund

We're using Polar.sh so you can upvote and help fund this issue.
We receive the funding once the issue is completed & confirmed by you.
Thank you in advance for helping prioritize & fund our backlog.

Hi @humphrey ,
I really like your idea! It is a lot more flexible than what we currently have
Maybe the only downside is that when writing a query that can return InputError, you need to add ... on SomeError for all possible kinds of errors in your application. Not a big deal, but something to think about.
Indeed, we haven't released 1.0 yet, so we could possibly make this breaking change. However, it is a very big change, and I'm afraid of how much it would break for people already relying on the current API, especially because it changes not only for the backend but also for the clients using the API.
@patrick91 pinging you to check your thoughts on this


Fix flakiness in testDontAllowSwitchingCompatibilityModeForClusterWit…

…hMultipleVersions

Description

Fixes the flakiness in org.opensearch.action.support.clustermanager.TransportClusterManagerNodeActionTests.testDontAllowSwitchingCompatibilityModeForClusterWithMultipleVersions.
Was using randomCompatibleVersion(random(), version1) to pick version2 which does not guarantee version2 being different from version1 leading to an assertion failure at assert version1.equals(version2) == false
Now specifically using two compatible and different OpenSearch versions for the purpose of the test

Related Issues
Resolves #13240

Check List

[ ] ~New functionality includes testing.~

[ ] ~All tests pass~

[ ] ~New functionality has been documented.~

[ ] ~New functionality has javadoc added~

[ ] ~Failing checks are inspected and point to the corresponding known issue(s) (See: Troubleshooting Failing Builds)~
[x] Commits are signed per the DCO using --signoff
[ ] ~Commit changes are listed out in CHANGELOG.md file (See: Changelog)~
[ ] ~Public documentation issue/PR created~

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

❌ Gradle check result for 8701a41: FAILURE
Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

Flaky Tests: #11979, #12197


[Bug] Folder bind mounts in docker contianer not working

Current Behavior
The /storage and the /output folders used in docker compose are bind mounts, but they are not working inside the docker contianer.
Expected Behavior
No response
Steps To Reproduce
No response
Environment

OS: DietPi
OS version: 9.0.0
CPU: ARM
Docker version: latest
Device model: Compute Module 4
Browser/OS: Microsoft Edge

Container creation
makemkv:
image: jlesage/makemkv:latest
container_name: makemkv
hostname: makemkv
restart: always
user: 0:0
environment:
- PUID=0
- PGID=0
- TZ=Europe/Rome
- DARK_MODE=true
volumes:
- ./makemkv/config:/config
- ./makemkv/input:/storage
- ./makemkv/output:/output
Container log
No Error visible in the log....

Container inspect
No response
Anything else?
No response

OK, I did change the PUID and GUID to 1000, but then I get an error.
/startapp.sh: cd: line 16: can't cd to /storage: Permission denied

The /storage folder is a bind mount to /mnt/storage and there also the permissions are correct...

Not sure where they are coming from, but PUID/PGID variables are not used by the container.  You need to use USER_ID and GROUP_ID.
You have to make sure the configured user can access /makemkv/input and other mapped folder.  See https://github.com/jlesage/docker-makemkv?tab=readme-ov-file#usergroup-ids

Good point. was just looking at what they had used to create. now looking at my setup is using USER_ID ..
But I assume they still need to map to valid OS user ids that have access to mount
Also not sure why they dint just build using your compose or instructions ?

Not sure where they are coming from, but PUID/PGID variables are not used by the container. You need to use USER_ID and GROUP_ID. You have to make sure the configured user can access /makemkv/input and other mapped folder. See https://github.com/jlesage/docker-makemkv?tab=readme-ov-file#usergroup-ids

This was it. Thanks


Buxton recipe

Buxton is a Smack-compatible key-value management system. This is a baseline recipe for it.

I fixed the issues you mentioned. At least systemd recipe has LICENSE = "GPLv2 & LGPLv2.1 & MIT" so I used equivalent format.

Looks good now. However, please squash the commits into one.

Samsung announced Tizen 3.0 Milestone 1 and mentions a Buxton2 in it, with support for Cynara. I suspect that this is a better match for a security architecture based on the Smack 3 domain model + Cynara.

Are you suggesting we wait until Buxton2 is evaluated before doing anything with this request?

Using Buxton with only smack isn't working well for Tizen 3. Buxton is much more useful with cynara.

@johnwhiteman yes, I think we need a better understanding of how Buxton would fit into the security model before merging the PR. What @Jobol said confirms my suspicion that it simply wouldn't be suitable.
Buxton2 might be, but there's very little information about it available. The source is here: https://review.tizen.org/git/?p=platform/core/system/buxton2.git;a=log;h=refs/heads/tizen - but it starts with a major code dump and doesn't have any README explaining the concepts behind it.

Can one of the admins verify this patch?

I'm closing this as a specific need for Buxton has not materialized.


Write Spec conformance tests for Checking expression

Refer to: https://ballerina.io/spec/lang/2022R1/#section_6.33

We are closing this issue because it is not being actively worked on. Let's reopen when we resume conformance test efforts.


Support armv7l (32 bit raspberry pi)

Full disclosure, I don't really know what I'm doing. 😄 I was trying to compile my Phoenix app (1.5 with Elixir 1.12.3) on Raspberry Pi 3 and was getting this error:
(RuntimeError) could not download esbuild for architecture: armv7l-unknown-linux-gnueabihf

This change made things work.

:green_heart: :blue_heart: :purple_heart: :yellow_heart: :heart: