when installing on a windows github runner, it builds itself instead of using the wheel

when attempting to install nodejs-wheel-binaries on a github windows runner, it intermittently crashes because it's trying to build it instead of using the wheel: https://github.com/DetachHead/basedpyright/actions/runs/9557152128/job/26343748025
ERRORS:
add nodejs-wheel-binaries failed:
Traceback (most recent call last):
  File
"C:\hostedtoolcache\windows\Python\3.9.13\x64\lib\concurrent\futures\thread.py"
, line 58, in run
    result = self.fn(*self.args, **self.kwargs)
  File
"D:\a\basedpyright\basedpyright\.pyprojectx\venvs\main-47f0a0df87867df1210f252a
3883e528-py3.9\lib\site-packages\pdm\installers\synchronizers.py", line 282, in
install_candidate
    self.manager.install(can)
  File
"D:\a\basedpyright\basedpyright\.pyprojectx\venvs\main-47f0a0df87867df1210f252a
3883e528-py3.9\lib\site-packages\pdm\installers\manager.py", line 33, in
install
    prepared.build(),
  File
"D:\a\basedpyright\basedpyright\.pyprojectx\venvs\main-47f0a0df87867df1210f252a
3883e528-py3.9\lib\site-packages\pdm\models\candidates.py", line 416, in build
    self._cached = Path(builder.build(build_dir,
metadata_directory=self._metadata_dir))
  File
"D:\a\basedpyright\basedpyright\.pyprojectx\venvs\main-47f0a0df87867df1210f252a
3883e528-py3.9\lib\site-packages\pdm\builders\wheel.py", line 22, in build
    filename = self._hook.build_wheel(out_dir, self.config_settings,
metadata_directory)
  File
"D:\a\basedpyright\basedpyright\.pyprojectx\venvs\main-47f0a0df87867df1210f252a
3883e528-py3.9\lib\site-packages\pyproject_hooks\_impl.py", line 256, in
build_wheel
    return self._call_hook(
  File
"D:\a\basedpyright\basedpyright\.pyprojectx\venvs\main-47f0a0df87867df1210f252a
3883e528-py3.9\lib\site-packages\pyproject_hooks\_impl.py", line 392, in
_call_hook
    self._subprocess_runner(
  File
"D:\a\basedpyright\basedpyright\.pyprojectx\venvs\main-47f0a0df87867df1210f252a
3883e528-py3.9\lib\site-packages\pdm\builders\base.py", line 259, in
subprocess_runner
    return log_subprocessor(cmd, cwd, extra_environ=env)
  File
"D:\a\basedpyright\basedpyright\.pyprojectx\venvs\main-47f0a0df87867df1210f252a
3883e528-py3.9\lib\site-packages\pdm\builders\base.py", line 106, in
log_subprocessor
    raise build_error(e) from None
pdm.exceptions.BuildError: Build backend raised error: Showing the last 10
lines of the build output:
  calling: "C:\Program Files\Microsoft Visual
Studio\2022\Enterprise\VC\\Auxiliary\Build\vcvarsall.bat" amd64
  **********************************************************************
  ** Visual Studio 2022 Developer Command Prompt v17.10.1
  ** Copyright (c) 2022 Microsoft Corporation
  **********************************************************************
  The input line is too long.
  The syntax of the command is incorrect.
C:\Program Files\Microsoft Visual
Studio\2022\Enterprise\MSBuild\Microsoft\VC\v170\Microsoft.CppCommon.targets(25
4,5): error MSB8066: Custom build for
'C:\Users\runneradmin\AppData\Local\Temp\tmphbpssuly\build\CMakeFiles\0ecaa4009
b35a5651d6eb00053767bdd\nodejs-mkdir.rule;C:\Users\runneradmin\AppData\Local\Te
mp\tmphbpssuly\build\CMakeFiles\0ecaa4009b35a5651d6eb00053767bdd\nodejs-downloa
d.rule;C:\Users\runneradmin\AppData\Local\Temp\tmphbpssuly\build\CMakeFiles\0ec
aa4009b35a5651d6eb00053767bdd\nodejs-update.rule;C:\Users\runneradmin\AppData\L
ocal\Temp\tmphbpssuly\build\CMakeFiles\0ecaa4009b35a5651d6eb00053767bdd\nodejs-
patch.rule;C:\Users\runneradmin\AppData\Local\Temp\tmphbpssuly\build\CMakeFiles
\0ecaa4009b35a5651d6eb00053767bdd\nodejs-configure.rule;C:\Users\runneradmin\Ap
pData\Local\Temp\tmphbpssuly\build\CMakeFiles\0ecaa4009b35a5651d6eb00053767bdd\
nodejs-build.rule;C:\Users\runneradmin\AppData\Local\Temp\tmphbpssuly\build\CMa
keFiles\0ecaa4009b35a5651d6eb00053767bdd\nodejs-install.rule;C:\Users\runneradm
in\AppData\Local\Temp\tmphbpssuly\build\CMakeFiles\e3ccfecb85c38cc10019a2432a9b
ae97\nodejs-complete.rule;C:\Users\runneradmin\AppData\Local\Temp\tmphbpssuly\b
uild\CMakeFiles\7bceba0f3bcbffdbccf74243fc13790b\nodejs.rule;C:\Users\runneradm
in\AppData\Local\Temp\pdm-build-8bl957n1\CMakeLists.txt' exited with code 255.
[C:\Users\runneradmin\AppData\Local\Temp\tmphbpssuly\build\nodejs.vcxproj]

*** CMake build failed

i'm not sure why this is. perhaps the windows runners use a different architecture which prevents the nodejs_wheel_binaries-20.14.0-py2.py3-none-win_amd64.whl wheel from working?

I created a temporary workflow for test and didn't get errors:
name: Test

on:
  push:

jobs:
  test:
    name: test windows wheel
    runs-on: windows-latest
    steps:
    - uses: actions/checkout@v4
    - uses: actions/setup-python@v5
      with:
        python-version: "3.x"
    - run: pip install nodejs-wheel-binaries

Run pip install nodejs-wheel-binaries

Collecting nodejs-wheel-binaries
  Downloading nodejs_wheel_binaries-20.14.0-py2.py3-none-win_amd64.whl.metadata (4.[7](https://github.com/njzjz/gist/actions/runs/9557801370/job/26345452572#step:4:7) kB)
Downloading nodejs_wheel_binaries-20.14.0-py2.py3-none-win_amd64.whl (33.[8](https://github.com/njzjz/gist/actions/runs/9557801370/job/26345452572#step:4:8) MB)
   ---------------------------------------- 33.8/33.8 MB 36.2 MB/s eta 0:00:00
Installing collected packages: nodejs-wheel-binaries
Successfully installed nodejs-wheel-binaries-20.14.0

it seems to be intermittent. maybe it needs to run a few times before it happens?

Maybe it is a bug from pdm?

looks like you're right. on a test project i tried installing it 10 times and it worked 10/10 times when using pip directly, but only 5/10 times when using pdm. i'll close this and raise it on pdm instead.

ok it turns out that some runners use a 32 bit version of python and others have a 64 bit version. using the setup-python action fixes it:
- uses: actions/setup-python@v5
  with:
      python-version: '3.12'


Make galaxy workflow on usegalaxy.eu which runs until msfinder for library filtering for internal libraries

This workflow should be built for the "large" in-house libraries, therefore should include the steps to add Charge, Ionmode and Adduct as hard coded values and then to derive precursor_mz using matchms. We can start developing this using a single chunk from our dataset.
For the last step, the peak overwriting tool in RECETOX/galaxytools#485 is needed.

[ ] MSMetaEnhancer: collect InChi using pubchem
[ ] MSMetaEnhancer: collect Isomeric_smiles from IDSM
[x] matchms filtering: filter invalid smiles and inchi
[x] rem_complex + matchms subsetting: remove complexes
[x] matchms remove key: remove existing adduct, charge and ionmode keys
[x] matchms add key: add charge, ionmode, adduct
[x] matchms filtering: derive precursor
[x] matchms convert: convert to riken
[x] recetox-msfinder: run msfinder with 0.5Da tolerance for MS1 and MS2 and inclusing all element checks as well as extended range
[ ] handle errors -> remove smiles which are not accepted -> rerun msfinder (optional, not sure if possible)
[x] RECETOX/galaxytools#485: run high-res annotation

After all the steps are included in the workflow, the workflow should be downloaded and deposited here on this repo.
The workflow file can then also be deposited on Zenodo.

This is waiting for https://help.galaxyproject.org/t/msmetaenhancer-cant-reach-services-if-running-on-usegalaxy-eu/11821

Closed with https://github.com/RECETOX/workflow-testing/pull/32


Add support for Mac OS

The current implementation works on Windows and Linux, need to add support for Mac OS

Could you assign that for me, but before I to start what exactly doesn't work for Mac OS?

Hi there,
I have addressed this issue in my pull request #10, where I implemented support for macOS systems. Can you by chance assign me for this issue?

@nsankethreddy could you assign that for me? , but before I to start what exactly doesn't work for Mac OS?

Hey, issue was already addressed by @energiesparlampe thank you for your interest

Thank you @energiesparlampe


Unrecognized command-line options error when building for android

I am trying to build Openh264 for android on wsl ubuntu.
With the command make OS=android NDKROOT=/root/Android/Sdk/ndk/26.0.10792818 TARGET=34 I get the output
/root/Android/Sdk/ndk/26.0.10792818/build/core/add-application.mk:177: *** Android NDK: APP_STL stlport_shared is no longer supported. Please switch to either c++_static or c++_shared. See https://developer.android.com/ndk/guides/cpp-support.html for more information.    .  Stop. /root/Android/Sdk/ndk/26.0.10792818/build/core/add-application.mk:177: *** Android NDK: APP_STL stlport_shared is no longer supported. Please switch to either c++_static or c++_shared. See https://developer.android.com/ndk/guides/cpp-support.html for more information.    .  Stop. /root/Android/Sdk/ndk/26.0.10792818/build/core/add-application.mk:177: *** Android NDK: APP_STL stlport_shared is no longer supported. Please switch to either c++_static or c++_shared. See https://developer.android.com/ndk/guides/cpp-support.html for more information.    .  Stop. /root/Android/Sdk/ndk/26.0.10792818/build/core/add-application.mk:177: *** Android NDK: APP_STL stlport_shared is no longer supported. Please switch to either c++_static or c++_shared. See https://developer.android.com/ndk/guides/cpp-support.html for more information.    .  Stop. gcc -O3 -DNDEBUG -DHAVE_NEON -march=armv7-a -mfloat-abi=softfp -mfpu=vfpv3-d16 -DANDROID_NDK -fpic --sysroot=/root/Android/Sdk/ndk/26.0.10792818/platforms/android-12/arch-arm -MMD -MP -fstack-protector-all -isystem /root/Android/Sdk/ndk/26.0.10792818/sysroot/usr/include -isystem /root/Android/Sdk/ndk/26.0.10792818/sysroot/usr/include/ -D__ANDROID_API__=12 -DGENERATED_VERSION_HEADER -I./codec/api/wels -I./codec/common/inc -Icodec/common/inc -Dandroid_getCpuIdArm=wels_getCpuIdArm -Dandroid_setCpuArm=wels_setCpuArm -Dandroid_getCpuCount=wels_getCpuCount -Dandroid_getCpuFamily=wels_getCpuFamily -Dandroid_getCpuFeatures=wels_getCpuFeatures -Dandroid_setCpu=wels_setCpu  -I/root/Android/Sdk/ndk/26.0.10792818/sources/android/cpufeatures -c -o codec/common/src/cpu-features.o /root/Android/Sdk/ndk/26.0.10792818/sources/android/cpufeatures/cpu-features.c gcc: error: unrecognized command-line option ‘-mfloat-abi=softfp’ gcc: error: unrecognized command-line option ‘-mfpu=vfpv3-d16’ make: *** [build/platform-android.mk:138: codec/common/src/cpu-features.o] Error 1
So the error is
gcc: error: unrecognized command-line option ‘-mfloat-abi=softfp’
gcc: error: unrecognized command-line option ‘-mfpu=vfpv3-d16’
I have the newest versions of Android Studio with SDK and NDK as I just installed them. Same with NASM and OpenH264 itself.
Is there a solution for this?

please try this command:
make OS=android TRAGET=android-xx NDKROOT=your/ndk/path NDK_TOOLCHAIN_VERSION=clang

请尝试此命令： make OS=android TRAGET=android-xx NDKROOT=your/ndk/path NDK_TOOLCHAIN_VERSION=clang

when i try to: make OS=android TRAGET=android-xx NDKROOT=your/ndk/path NDK_TOOLCHAIN_VERSION=clang
It shows an error message：
/home/lhs/pjsip/pjsip-install/android-ndk-r22b/sources/android/cpufeatures/cpu-features.h:31:10: fatal error: 'sys/cdefs.h' file not found
#include <sys/cdefs.h>
^~~~~~~~~~~~~
1 error generated.
make: *** [build/platform-android.mk:138: codec/common/src/cpu-features.o] Error 1

Maybe you didn't pull the latest version of the code?

请尝试此命令： make OS=android TRAGET=android-xx NDKROOT=your/ndk/path NDK_TOOLCHAIN_VERSION=clang

when i try to: make OS=android TRAGET=android-xx NDKROOT=your/ndk/path NDK_TOOLCHAIN_VERSION=clang It shows an error message： /home/lhs/pjsip/pjsip-install/android-ndk-r22b/sources/android/cpufeatures/cpu-features.h:31:10: fatal error: 'sys/cdefs.h' file not found #include <sys/cdefs.h> ^~~~~~~~~~~~~ 1 error generated. make: *** [build/platform-android.mk:138: codec/common/src/cpu-features.o] Error 1

Maybe you didn't pull the latest version of the code?


AutomationHAT contribution

I'm working on an implementation for the AutomationHAT (https://github.com/shortbloke/node-red-nodes/tree/automationhat). I've initially started this as a fork. However I can see that you have a link out to 3rd party nodes contributions. From this can I assume that you'd not want to accept a PR to add this support into your main package and instead I should follow the example of: https://github.com/cyberflohr/node-red-contrib-rainbow-hat
Thanks Martin

You assume correctly- as much as I'd love to accept a PR and take this under our wing, right now I just don't know enough about NodeJS and Node-RED for it to be worth doing so.

Thanks, good to know. I'll restructure my project with a view to being a 3rd party node contribution.

@Gadgetoid I've created the Automation HAT implementation and raised a PR #4 to request an update to the readme to link out to this 3rd party implementation. The package is also published via npm.

PR Approved. Closing


React DnD tutorial is hard to follow

React DnD tutorial (chessboard example)
I'm new to React (completed a few tutorials).
And it's still not clear for me what we are doing in 'Game' component. And how it links with index.js. Moreover, when I completed the tutorial, I saw that the knight couldn't move to anywhere (we could drag him, but after drop the app crashes: "Cannot have two HTML5 backends at the same time"). So I went to compare my code with example, but it has another code with different files in typescript! Okay, I rewrote my code according to the example and of course, change ReactDOM.render so as to it renders 'ChessboardTutorialApp'.
And all I get is just a square 500x500 and nothing else.
Probable solution
It's necessary to add explanation to how interacts 'Game' with 'index' and other components (moreover this tutorial (http://react-dnd.github.io/react-dnd/docs/tutorial) partially written for beginners:

If you're new to React and know a thing or two about it, but yet have to gain some experience building components, this tutorial can also serve as an introduction to the React mode of thinking and the React workflow.

And It would be nice to re-write the tutorial with typescript code in order to at least compare it with working version of the app.
My project with chessboard from documentation-examples
https://github.com/TimmyGOGO/react_dnd_tutorial

In order to run this example with Chessboard, you need to add to Board.tsx file next lines:
import HTML5Backend from 'react-dnd-html5-backend';  import BoardSquare from './BoardSquare';  ...  export default DragDropContext(HTML5Backend)(Board);

Move the provider to index.js and wrap your root component with it. It seems that as the tutorial is written every time the Board component re-renders it provides a new context with a new back end.

@rdurel423 This does not fix the issue. I am still receiving the same "Cannot have two HTML5 backends at the same time" error.
Full index.js file after moving provider:
import React from 'react'
import ReactDOM from 'react-dom'
import Board from './Board'
import { observe } from './Game'
import { DragDropContextProvider } from 'react-dnd'
import HTML5Backend from 'react-dnd-html5-backend'

const root = document.getElementById('root')

observe(knightPosition =>
   ReactDOM.render(<DragDropContextProvider backend={HTML5Backend}><Board knightPosition={knightPosition} /></DragDropContextProvider>, root),
)

+1 that it is hard to follow.
Nobody needs to have to read through a bunch of experimental code to see how a chessboard would be implemented when you could just show a working implementation of how the code works and let people modify it to suit their own needs.
I made it work for me after struggling with it for about 1.5 hours.
Furthermore, the toggle button for "hooks" and "decorators" seems broken....  clicking on either changes nothing at all.
While it seems to be a good library, the documentation is horrible.

... and this "stale" bot needs an algorithm update.
Just because nobody addressed the bad documentation does not mean that the issue should be closed.


[FLINK-12219][runtime] Yarn application can't stop when flink job failed in per-job yarn cluste mode

What is the purpose of the change
In our flink(1.6.3) product env, I often encounter a scene that yarn application can't stop when flink job failed in per-job yarn cluste mode.
When a flink job fail, system will write an archive file to a FileSystem through MiniDispatcher#archiveExecutionGraph method, then notify YarnJobClusterEntrypoint to shutDown. But, if MiniDispatcher#archiveExecutionGraph throw exceptions during execution, it affect the following calls.
So I open FLINK-12247 to solve NEP bug when system write archive to FileSystem. But We still need to consider other exceptions, so we should catch Exception / Throwable not just IOExcetion.
for more detail, please see FLINK-12219-JIRA.
Brief change log
JsonResponseHistoryServerArchivist#archiveExecutionGraph change Exception to IOException.
Verifying this change
This change is already covered by existing tests, such as TestingDispatcher.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (yes)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (no)
If yes, how is the feature documented? (not applicable)

@tillrohrmann, thanks for review. Let me think how to provide a right test case.

@tillrohrmann, I add a junit case MiniDispatcherTest#testTerminationAfterJobCompletionWithExceptionHistoryServerArchivist. At this case, miniDispatcher was in detached mode( like to per-job on yarn) and we will see JobTerminationFuture will nerver terminate until timeout.

hi @tillrohrmann, a minimal reproducible flink program can simulate this bug quickly.
ENV

flink-1.6.3 or up version
run job on yarn cluster in detached mode.
restart strategy

restart-strategy: fixed-delay
restart-strategy.fixed-delay.attempts: 20
restart-strategy.fixed-delay.delay: 2 s

Flink Job
public static void main(String[] args) throws Exception {

    StreamExecutionEnvironment env = StreamExecutionEnvironment.getExecutionEnvironment();

    DataStream<String> text = env.addSource(new SourceFunction<String>() {
        @Override
        public void run(SourceContext<String> ctx) throws Exception {
            while (true) {
                ctx.collect("aaaa");
                Thread.sleep(100);
            }
        }

        @Override
        public void cancel() {

        }
    });

    text.addSink(new SinkFunction<String>() {
        @Override
        public void invoke(String value, Context context) throws Exception {
            System.out.println(1 / 0);
        }
    });

    env.execute();

}

The HistoryServerArchivist is not supposed to throw any exceptions. If it does, then it is clearly a programming fault. I don't understand which case you try to solve here. What is the original exception you are seeing why you think that an IOException is not good enough.

hi, @tillrohrmann
First, the original exception is NEP which as FLINK-12247 described. When the number of retries more than MAX_ATTEMPTS_HISTORY_SIZE, it'll throw NEP. it'll cause yarn application hang.
Second, the FsJobArchivist#archiveJob method not only throw IOException but also throw Exception. Include at least the above exception currently.
So I used ExceptionHistoryServerArchivist to simulate other unknown exceptions which may be happen.

@tillrohrmann, here is original NPE stacktrace.
java.lang.NullPointerException
   at org.apache.flink.runtime.rest.handler.util.MutableIOMetrics.addIOMetrics(MutableIOMetrics.java:88)
   at org.apache.flink.runtime.rest.handler.job.SubtaskExecutionAttemptDetailsHandler.createDetailsInfo(SubtaskExecutionAttemptDetailsHandler.java:140)
   at org.apache.flink.runtime.rest.handler.job.SubtaskExecutionAttemptDetailsHandler.archiveJsonWithPath(SubtaskExecutionAttemptDetailsHandler.java:120)
   at org.apache.flink.runtime.webmonitor.WebMonitorEndpoint.archiveJsonWithPath(WebMonitorEndpoint.java:780)
   at org.apache.flink.runtime.dispatcher.JsonResponseHistoryServerArchivist.archiveExecutionGraph(JsonResponseHistoryServerArchivist.java:57)
   at org.apache.flink.runtime.dispatcher.Dispatcher.archiveExecutionGraph(Dispatcher.java:758)
   at org.apache.flink.runtime.dispatcher.Dispatcher.jobReachedGloballyTerminalState(Dispatcher.java:730)
   at org.apache.flink.runtime.dispatcher.MiniDispatcher.jobReachedGloballyTerminalState(MiniDispatcher.java:138)
   at org.apache.flink.runtime.dispatcher.Dispatcher.lambda$startJobManagerRunner$6(Dispatcher.java:341)
   at java.util.concurrent.CompletableFuture.uniWhenComplete(CompletableFuture.java:760)
   at java.util.concurrent.CompletableFuture$UniWhenComplete.tryFire(CompletableFuture.java:736)
   at java.util.concurrent.CompletableFuture$Completion.run(CompletableFuture.java:442)
   at org.apache.flink.runtime.rpc.akka.AkkaRpcActor.handleRunAsync(AkkaRpcActor.java:332)
   at org.apache.flink.runtime.rpc.akka.AkkaRpcActor.handleRpcMessage(AkkaRpcActor.java:158)
   at org.apache.flink.runtime.rpc.akka.FencedAkkaRpcActor.handleRpcMessage(FencedAkkaRpcActor.java:70)
   at org.apache.flink.runtime.rpc.akka.AkkaRpcActor.onReceive(AkkaRpcActor.java:142)
   at org.apache.flink.runtime.rpc.akka.FencedAkkaRpcActor.onReceive(FencedAkkaRpcActor.java:40)
   at akka.actor.UntypedActor$$anonfun$receive$1.applyOrElse(UntypedActor.scala:165)
   at akka.actor.Actor$class.aroundReceive(Actor.scala:502)
   at akka.actor.UntypedActor.aroundReceive(UntypedActor.scala:95)
   at akka.actor.ActorCell.receiveMessage(ActorCell.scala:526)
   at akka.actor.ActorCell.invoke(ActorCell.scala:495)
   at akka.dispatch.Mailbox.processMailbox(Mailbox.scala:257)
   at akka.dispatch.Mailbox.run(Mailbox.scala:224)
   at akka.dispatch.Mailbox.exec(Mailbox.scala:234)
   at scala.concurrent.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260)
   at scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1339)
   at scala.concurrent.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979)
   at scala.concurrent.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107)

The HistoryServerArchivist is not supposed to throw any exceptions. If it does, then it is clearly a programming fault. I don't understand which case you try to solve here. What is the original exception you are seeing why you think that an IOException is not good enough.

you're right, may be it's a clearly a programming falut. but once an exception occurs, it will cause the yarn application hang. Because this affects the execution of the method ClusterEntrypoint#shutDownAsync which will notify yarn resourcemanager to stop applicaiton.

@tillrohrmann, BTW, if you want to get the NPE stacktrace, you need to use log4j and change IOException to Exception. than use command yarn logs -applicationId xxx.
@Override
public CompletableFuture<Acknowledge> archiveExecutionGraph(AccessExecutionGraph executionGraph) {
   try {
      FsJobArchivist.archiveJob(archivePath, executionGraph.getJobID(), jsonArchivist.archiveJsonWithPath(executionGraph));
      return CompletableFuture.completedFuture(Acknowledge.get());
   } catch (Exception e) {
      LOG.error("archive exception",e);
      return FutureUtils.completedExceptionally(e);
   }
}

@tillrohrmann, I have a new idea to fix the bug. The most essential reason is when the Dispatcher#jobReachedGloballyTerminalState method throw exception witch we don't catched. it affect jobterminal callback. we can catch exception and move callback to finally code block.
Current code
MiniDispatcher#jobReachedGloballyTerminalState
protected void jobReachedGloballyTerminalState(ArchivedExecutionGraph archivedExecutionGraph) {

    super.jobReachedGloballyTerminalState(archivedExecutionGraph);

    if (executionMode == ClusterEntrypoint.ExecutionMode.DETACHED) {
        // shut down since we don't have to wait for the execution result retrieval
        jobTerminationFuture.complete(ApplicationStatus.fromJobStatus(archivedExecutionGraph.getState()));
    }
}

Change to new code
protected void jobReachedGloballyTerminalState(ArchivedExecutionGraph archivedExecutionGraph) {

    try {
        super.jobReachedGloballyTerminalState(archivedExecutionGraph);
    } catch (Exception e) {
        log.error("jobReachedGloballyTerminalState exception", e);
    } finally {
        if (executionMode == ClusterEntrypoint.ExecutionMode.DETACHED) {
            // shut down since we don't have to wait for the execution result retrieval
            jobTerminationFuture.complete(ApplicationStatus.fromJobStatus(archivedExecutionGraph.getState()));
        }
    }
}

Hi @lamber-ken, I think the inner Exception is not a problem because it is actually only a IOException. Thus, the archiveJob method can only throw an IOException.
The NPE is clearly a Flink bug and as such we should rather fix the bug than guard against it. What we could do, though, is to run jobTerminationFuture.complete(ApplicationStatus.fromJobStatus(archivedExecutionGraph.getState())); in a finally block. But we should not catch the exception there. Per contract jobReachedGloballyTerminalState should not throw any exception. If it does, then it violates the contract and Flink gives no guarantees how it behaves afterwards.

Hi @lamber-ken, I think the inner Exception is not a problem because it is actually only a IOException. Thus, the archiveJob method can only throw an IOException.
The NPE is clearly a Flink bug and as such we should rather fix the bug than guard against it. What we could do, though, is to run jobTerminationFuture.complete(ApplicationStatus.fromJobStatus(archivedExecutionGraph.getState())); in a finally block. But we should not catch the exception there. Per contract jobReachedGloballyTerminalState should not throw any exception. If it does, then it violates the contract and Flink gives no guarantees how it behaves afterwards.

Hi, @tillrohrmann, you are right!

Thanks for your review and suggestion @tillrohrmann. I had update the patch, can you take some time to check?

I don't think that this solves the problem @lamber-ken. Please provide a test case which verifies it.

I don't think that this solves the problem @lamber-ken. Please provide a test case which verifies it.

done.

Thanks for updating the PR @lamber-ken. I actually think that we cannot guard against all possible unchecked exceptions in Flink. If such an exception occurs, then this is clearly an indicator that there is a bug in Flink. If there is a bug in Flink, then we don't give guarantees on the its behaviour. Thus, I think we don't need to add this finally block. The problem should have been solved by fixing #8250. Hence, I will close this PR and the corresponding JIRA issue. Please re-open if you strongly object.

Thanks for your comment @tillrohrmann, as another issue FLINK-12183 says, it's hard to find that because here it only catches IOException, and we can't get any stacktrace information from the log file (because there's no place to record the exception log). If some uncatched exception happens in the futher, it'll cause yarn application can't stop again even if the task has failed. BTW, I have no right to re-open this issue again.
Best.

FLINK-12183 is the same issue as FLINK-12247. If the problem is debuggability, then we should think about adding a UncaughtExceptionHandler to log these exceptions. This should be the proper fix for this problem, because it can potentially also happen in other places. If you want to re-open the issue, then please ping me or open a new issue.

hi @tillrohrmann, yes, at least we need to record the exception record, so I log the exception and re-throw it again.
protected void jobReachedGloballyTerminalState(ArchivedExecutionGraph archivedExecutionGraph) {

    try {
        super.jobReachedGloballyTerminalState(archivedExecutionGraph);
    } catch (Exception e) {
        log.error("jobReachedGloballyTerminalState exception", e);
        throw e;
    } finally {
        if (executionMode == ClusterEntrypoint.ExecutionMode.DETACHED) {
            // shut down since we don't have to wait for the execution result retrieval
            jobTerminationFuture.complete(ApplicationStatus.fromJobStatus(archivedExecutionGraph.getState()));
        }
    }
}

@tillrohrmann, no button to click to re-open, just a Comment button.

The super.jobReachedGloballyTerminalState(archivedExecutionGraph); method need to call WebMonitorEndpoint#archiveJsonWithPath to acquire archive jsons, in that method, will call many archivingHandlers. We can't guarantee that there is no problem in these handles in the futher. Although it's may be a minor bug for these handlers, but this will cause the yarn application can't stop.
For the user, when open the flink-ui page, we only see the fink-job fail, but it is not clear why the yarn-application does not stop in per-job detached mode.
protected void jobReachedGloballyTerminalState(ArchivedExecutionGraph archivedExecutionGraph) {

    super.jobReachedGloballyTerminalState(archivedExecutionGraph);

    if (executionMode == ClusterEntrypoint.ExecutionMode.DETACHED) {
        // shut down since we don't have to wait for the execution result retrieval
        jobTerminationFuture.complete(ApplicationStatus.fromJobStatus(archivedExecutionGraph.getState()));
    }
}

As I've said before, the archiving handlers belong to Flink and if they are broken, then the system does not give any guarantees. If they were user provided, then I would agree that Flink should not fail in case of exceptions because they are not under its control.
The problem is that we don't see this exception. The reason seems to be that we execute the jobReachedGloballyTerminalState in a whenCompleteAsync callback which returns a future containing the exception. Since we don't check this future, we will never see it. That's also why the UncaughtExceptionHandler is never called.
I would suggest to add a utility FutureUtils#assertNoException which checks returned futures for normal completion. Please take a look at this commit https://github.com/tillrohrmann/flink/commit/524ead44f68ff02d52e8ff561c9e235e5b353123 and let me know whether you would accept this as a fix for the problem.

Your solution is fantastic @tillrohrmann!
I known the reason，but I'm sorry that I didn't describe it well. FutureUtils#assertNoException is a good tool so solve this problem.
My point is when flink job failed on yarn in detach mode，the yarn application should failed too.

but, another problem is I can't re-open this issue again

It is true that Yarn could try to restart the cluster depending on the configuration. Flink would then try to re-execute the job again since it is part of the Yarn application (no problem with the submitted job graph store). Depending on whether the Flink bug is transient or not the failure would happen again until all restarts are depleted or eventually the job will succeed (potentially with producing duplicate results).
Given that this is caused by a bug in Flink, I think it is ok to say that we don't give hard guarantees in this case. The important bit is that we report the problem.
I would open a PR based on my commit to add this utility.

ok，I agree with you

I opened a issuse before, it describe a scene that containts two steps.
first，the flink job failed and the yarn application don't stop.
second，the yarn resourcemanager restarted for some reason, it will attempt to restart all applications. the job in the first step also restarted, but no jobs recover because the zk meta was removed by first step. it'll failed. but the finalState status is UNDEFIEND.
these two issues are associated，if you have time，help me review it, thanks.

FYI @lamber-ken I've opened the PR with the utility #8334

hi，@tillrohrmann，what I need to do next? need I update this pr when #8334 merged?

No, this PR has been closed and should no longer be relevant, right?

right, but when and how to fix this issue when #8334 merged? need to open a new pr?

which issue do you wanna fix? That the Yarn application can't stop? I think this one should be fixed with #8250.

hi, @tillrohrmann, what this commit tillrohrmann@524ead4 mean?
If you insist that it has been resolved with #8250, I don't agree with you very much, but I can only obey you.
As another issue FLINK-12183 says, it's hard to find that because here it only catches IOException, and we can't get any stacktrace information from the log file (because there's no place to record the exception log). If some uncatched exception happens in the futher, it'll cause yarn application can't stop again even if the task has failed.
Best.

hi, @tillrohrmann, I think your fix is fantastic tillrohrmann@524ead4.
like the FLINK-12247, We used flink from 1.2.1 to 1.6.3 and we have been puzzled by this problem for a long time. Because it‘s needs the count of flink job failed attempt up to the max attempt history size, and no error log information that we can find the reason why the flink job failed but the yarn application don't stop in detach mode.
May be other users had met the same bug, but they did not mention it or fix it. So I think it's better to log the error information and stop the application like your solution tillrohrmann@524ead4.
If don't do that, any unexpected exception happens, the yarn application will can not stop again. It will need users to find out the reason, it's hard to users.
Best.

hi, @tillrohrmann,
Sorry, it's ok, I just think you just add a future tool just now. you had fix the issue #8334 too.
Best.

The commit message and the PR title were a bit misleading. I've updated them.

ok


Replace usages of abandoned Interop\Container\ContainerInterface

Feature Request

Q
A

New Feature
yes

RFC
no

BC Break
no

Summary
Interop\Container\ContainerInterface has been abandoned and composer install suggests moving to psr/container instead.
Package container-interop/container-interop is abandoned, you should avoid using it. Use psr/container instead.
This should not cause a BC break, as Interop\ContainerInterface simply extends Psr\ContainerInterface.

This might not actually be possible yet depending on Laminas\ServiceManager updates

https://github.com/laminas/laminas-servicemanager/issues/18#issuecomment-879182790


request: Initialize from anything on instantiation.

As a user I want the ability to instantiate and initialize a DrupalJsonApiParams object using a String, Object, or an existing DrupalJsonApiParams object, without the need to call a specific method.
Currently I have a mergeQuery method that will take a query String, Object or DrupalJsonApiParams object, and ensure I get a DrupalJsonApiParams object back, but it's a little clunky:
  mergeQuery(query) {
    if (!(query instanceof DrupalJsonApiParams)) {
      if (query) {
        query = typeof query === 'string'
          ? new DrupalJsonApiParams().initializeWithQueryString(query)
          : new DrupalJsonApiParams().initializeWithQueryObject(query)
      } else {
        query = new DrupalJsonApiParams()
      }
    }
    return query
  }

That allows me to do something like:
this.mergeQuery(query).addFields(...)

It would be preferable if I could do something like:
query = new DrupalJsonApiParams(query).addFields(...)

query = new DrupalJsonApiParams(query).addFields(...)

@Decipher  I would like to know a little more context about this usage. When doesn't a developer have the knowledge about the type of query.
So the following is the usage AS IS,
// when query is DrupalJsonApiParams object.
query = query.addFields(...);

// when query is string
query = new DrupalJsonApiParams().initializeWithQueryString(query).addFields(...);

// when query is data object.
query = new DrupalJsonApiParams().initializeWithQueryObject(query).addFields(...);

// when query is undefined/false/null
query = new DrupalJsonApiParams().addFields(...);

And following is what is TO BE,
query = new DrupalJsonApiParams(query).addFields(...);

Technically it looks like this has to be handled outside DrupalJsonApiParams Class, so we can also handle the condition when query is Falsy.
Maybe it can be a standalone method outside the class itself which is available for import. Like a pinch of Syntactic Salt.

The use case mostly comes about because the Druxt modules allow for the query parameter to be either:

A querystring
A queryobject
A DrupalJsonApiParams object

The reason something is needed is that I often need for the module to be able to alter queries, to add explicitly required fields or filters.
Currently I have the following implementation in the DruxtStore:
https://github.com/druxt/druxt.js/blob/develop/src/stores/druxt.js#L6-L16

Update:
I tried to implement this in Typescript and it is not letting me do that. Such a bummer. Will give it a go again after consulting some Typescript Gurus.

Solved in a slightly different manner. Guess it should work... at least tests says so :)


cmd/internal/goobj: untested code

In CL 20489, @crawshaw observed that he was able to change the cmd/internal/obj's objfile writing code and cmd/link/internal/ld's objfile reading code, but no tests failed to indicate that cmd/internal/goobj should be updated too.
cmd/internal/goobj used to be used by cmd/newlink, but that was deleted in CL 20380 (fb880b8).
It's also still used in cmd/internal/objfile/goobj.go, but that file isn't otherwise used either.
I imagine that because of #14386, we might as well just remove the dead code.
/cc @rsc

There's a lot of other linker-related overlap, some of which is only now becoming clear to me.
For example, cmd/internal/obj.LSym and cmd/link/internal/ld.LSym. I believe if obj.LSym had an Extra interface{} field that cmd/link could use, then we could replace most of ld.LSym. Given I did some recent cleanup of ld.LSym, I'll attempt to do the same to obj.LSym and see how close I can get to merging those types.

The code in goobj is meant to be able to be used by cmd/objdump to enable
objdump of .o files. I think that never made it into objdump, but it still
should, so please don't delete the code. I guess if I hadn't deleted
cmd/newlink there would be a test. :-(
The new format is just about replacing the ar framing with zip framing. The
goobj-parsed part current called a .o file will still exist, just inside
the zip archive.
On Fri, Mar 11, 2016 at 4:22 PM Matthew Dempsky<EMAIL_ADDRESS>wrote:

In CL 20489, @crawshaw https://github.com/crawshaw observed that he was
able to change the cmd/internal/obj's objfile writing code and
cmd/link/internal/ld's objfile reading code, but no tests failed to
indicate that cmd/internal/goobj should be updated too.
cmd/internal/goobj used to be used by cmd/newlink, but that was deleted in
CL 20380 (fb880b8
https://github.com/golang/go/commit/fb880b8a03f33b6a1809d76e7673717875c74606
).
It's also still used in cmd/internal/objfile/goobj.go, but that file isn't
otherwise used either.
I imagine that because of #14386
https://github.com/golang/go/issues/14386, we might as well just remove
the dead code.
/cc @rsc https://github.com/rsc
—
Reply to this email directly or view it on GitHub
https://github.com/golang/go/issues/14782.

In that case I think we should plan on eventually deleting the objfile reading code cmd/link/internal/ld/objfile.go, and using goobj instead in cmd/link.

Please do NOT merge cmd/internal/obj and cmd/internal/ld. The first is
about writing object files and the second is about reading them. The
point of splitting the code was so that they could diverge reasonably, so
that the reading-specific parts could be dropped from one and the
writing-specific parts dropped from the other. They can both get cleaner
that way. I would like to get back to the point where cmd/link does not
import cmd/internal/obj at all. It didn't used to, but there was some
well-intentioned and reasonable cleanup that undid that separation this a
while back in order to avoid some duplicated constant definitions. It would
be good to split those constants out into a separate shared package
(cmd/internal/objfile maybe) and then add a test to go/build that cmd/link
cannot depend on cmd/internal/obj.
On Fri, Mar 11, 2016 at 4:26 PM David Crawshaw<EMAIL_ADDRESS>wrote:

There's a lot of other linker-related overlap, some of which is only now
becoming clear to me.
For example, cmd/internal/obj.LSym and cmd/link/internal/ld.LSym. I
believe if obj.LSym had an Extra interface{} field that cmd/link could
use, then we could replace most of ld.LSym. Given I did some recent cleanup
of ld.LSym, I'll attempt to do the same to obj.LSym and see how close I can
get to merging those types.
—
Reply to this email directly or view it on GitHub
https://github.com/golang/go/issues/14782#issuecomment-195561179.

+1 on moving the shared constants and file format documentation into a separate package that both cmd/internal/obj and cmd/link can use.
Also, apparently I'm mistaken.  The cmd/internal/goobj code is linked into nm, objdump, etc.  It looks like it should be at least manually testable by running "go tool nm" on a compiled Go .o file.  We just don't seem to have tests for that functionality though.

I think I was still a bit confused when I wrote that. What I'm interested in is merging the two pieces of objfile reading code we have: cmd/internal/goobj/read.go and cmd/link/internal/ld/objfile.go.
That would mean some kind of type sharing between cmd/internal/goobj.Sym and cmd/link/internal/ld.LSym.
It looks like ld.LSym could have goobj.Sym as a field inside it, and use the goobj reading code.

I looked at that a bit a few months back. The problem I ran into is that ld.Reloc has several more fields than goobj.Reloc but goobj.Sym has a slice of goobj.Relocs... I guess it's not that many really, so they could be added, but Xadd/Xsym don't really "belong" in goobj. The other thing is that goobj's struct have SymID's everywhere where ld has *LSyms, which IIRC ends up conflicting with the idea of using a symbol table in object files.

I think we can consider this fixed by CL 42971, which adds a test that exercises the code (and which was written in response to a surprise goobj failure). Feel free to reopen if you disagree.


added footer to about page and home page

I pulled main into your branch and then resolve the merge conflict. It looks like it is good to merge. LGTM!


Variety of fixes, making actually work again

It's a big patch, but restores usability.

Fixes bug with api's being changed (e.g. deleting required archiving first)
Adds --wipeAll command (so when developing, you can wipe all changes and then start from a fresh slate)
Adds multithreading with dynamic timeout detection, for very big speed increase. Initial run from the repo ran overnight (12+ hours, final testing took 1~ hour.
Fixes issue #14. Previously, all projects would belong to the "first" client.

Support for null client entries, null project entries, and 😱 nullclient-nullproject entries.
Code is kept in same formatting as before

This has been tested on my own workspace. Most entries made it across and the majority are categorized into the correct project/client.

The other pull request has this as a base so i'm closing this one.


google app engine issue

I deployed my server at the google app engine.
When I deploy my server which is using google-cloud/datastore, google-cloud/connect-datastore module as the session storage, there are infinitely many session data appears repeatedly even though I didn't connect to the website.
Anyone has the same problem? And anyone can handle this?

I solved the problem. It was an App engine internal API issue.


Stefans tweaks to #309

Tweaks to show on #309
Changes
How I tested this
Notes
Checklist

[ ] PR has an informative and human-readable title (this will be pulled into the release notes)
[ ] Changes are limited to a single goal (no scope creep)
[ ] Code passed the pre-commit check & code is left cleaner/nicer than when first encountered.
[ ] Any change in functionality is tested
[ ] New functions are documented (with a description, list of inputs, and expected output)
[ ] Placeholder code is flagged / future TODOs are captured in comments
[ ] Project documentation has been updated if adding/changing functionality.

Closing as it's served its purpose.


Gear cannot run if no inputs in manifest

When running a gear that takes no inputs, the follow error occurs when trying to start the job:
A validation error has occurred. Please review any errors above and resubmit the form.
Below is the manifest of the gear that was causing this error.
{
  "label": "Session Archive",
  "name": "session-archive",
  "version": "0.0.1rc1",
  "description": "This gear uses the Flywheel Python SDK to locate all files within a given session (indicated by session ID given in the config file) on a user's Flywheel Instance. All files within the session are outputted as a single zip archive.",
  "inputs": {},
  "config": {
    "session_id": {
      "default": "",
      "type": "string",
      "description": "ID number of the session."
    },
    "api_key": {
      "default": "",
      "type": "string",
      "description": "The API key of the user."
    }
  },
  "author": "Jennifer Reiter",
  "maintainer": "Jennifer Reiter",
  "custom": {
    "docker-image": "flywheel/session-archive:v0.0.1",
    "gear-builder": {
        "image": "flywheel/session-archive"
        }
  },
  "license": "Other",
  "url": "",
  "source": "https://github.com/flywheel-apps/session-archive"
}

Will be closed by #938.

Resolved by #938


Popup: Add links to external mapping sites for that location

A query to Geohack will provide URLs for Google, Bing, OpenStreetMap,  and dozens of other map websites.
There is a Firefox extension that will open Geo URLs in Geohack or other sited. GeoURL support is already built into smartphones, so the extension is only needed on desktops, laptops, etc.

We currently have Google, Geohack, and GeoURI links.


HELP

Why relation_types=input_reader.relation_type_count - 1 ？ Why need  - 1？Instead of relation_types=input_reader.relation_type_count！

I have the same question. Any reply @markus-eberts, please?


Remove paket 🔥

Reduce dependency issues:
Expected nuspec information for ARCtrl package
<!-- ARCtrl -->
<?xml version="1.0" encoding="utf-8"?>
<package xmlns="http://schemas.microsoft.com/packaging/2013/05/nuspec.xsd">
  <metadata>
    <id>ARCtrl</id>
    <version>1.0.0-beta.2</version>
    <authors>nfdi4plants, Lukas Weil, Kevin Frey, Kevin Schneider, Oliver Maus</authors>
    <license type="expression">MIT</license>
    <licenseUrl>https://licenses.nuget.org/MIT</licenseUrl>
    <icon>logo.png</icon>
    <projectUrl>https://github.com/nfdi4plants/ARCtrl</projectUrl>
    <description>Library for management of Annotated Research Contexts (ARCs) using an in-memory representation and runtimer agnostic contract systems.</description>
    <releaseNotes>Additions:
Complete overhaul of the API.
Shifted focus from only ISA to include full ARC.
Included Fable compilation to Javascript as first citizen design principles.
No direct filesystem access but contract based IO, which allows language agnostic IO.</releaseNotes>
    <tags>ARC F# FSharp dotnet .Net bioinformatics biology fable-library datascience dataplant nfdi metadata</tags>
    <repository type="git" url="https://github.com/nfdi4plants/ARCtrl" />
    <dependencies>
      <group targetFramework=".NETStandard2.0">
        <dependency id="ARCtrl.Contract" version="1.0.0-beta.2" exclude="Build,Analyzers" />
        <dependency id="ARCtrl.CWL" version="1.0.0-beta.2" exclude="Build,Analyzers" />
        <dependency id="ARCtrl.FileSystem" version="1.0.0-beta.2" exclude="Build,Analyzers" />
        <dependency id="ARCtrl.ISA.Json" version="1.0.0-beta.2" exclude="Build,Analyzers" />
        <dependency id="ARCtrl.ISA.Spreadsheet" version="1.0.0-beta.2" exclude="Build,Analyzers" />
        <dependency id="ARCtrl.ISA" version="1.0.0-beta.2" exclude="Build,Analyzers" />
        <dependency id="FSharp.Core" version="6.0.7" exclude="Build,Analyzers" />
        <dependency id="Fable.Fetch" version="2.6.0" exclude="Build,Analyzers" />
        <dependency id="Fable.SimpleHttp" version="3.5.0" exclude="Build,Analyzers" />
      </group>
    </dependencies>
  </metadata>
</package>

<!-- ISA.Spreadsheet -->
<?xml version="1.0" encoding="utf-8"?>
<package xmlns="http://schemas.microsoft.com/packaging/2013/05/nuspec.xsd">
  <metadata>
    <id>ARCtrl.ISA.Spreadsheet</id>
    <version>1.0.0-beta.2</version>
    <authors>nfdi4plants, Lukas Weil</authors>
    <license type="expression">MIT</license>
    <licenseUrl>https://licenses.nuget.org/MIT</licenseUrl>
    <icon>logo.png</icon>
    <projectUrl>https://github.com/nfdi4plants/ARCtrl/tree/main/src/ISA</projectUrl>
    <description>ARC and ISA xlsx compliant parser for experimental metadata toolkit in F#. This project is meant as an easy means to open, manipulate and save ISA (Investigation,Study,Assay) metadata files in isa-xlsx format.</description>
    <releaseNotes>Additions:
Complete overhaul of the API.
Shifted focus from only ISA to include full ARC.
Included Fable compilation to Javascript as first citizen design principles.
No direct filesystem access but contract based IO, which allows language agnostic IO.</releaseNotes>
    <tags>ARC F# FSharp dotnet .Net bioinformatics biology fable-library datascience dataplant nfdi metadata investigation study assay ISA Spreadsheet xlsx excel</tags>
    <repository type="git" url="https://github.com/nfdi4plants/ARCtrl" />
    <dependencies>
      <group targetFramework=".NETStandard2.0">
        <dependency id="ARCtrl.FileSystem" version="1.0.0-beta.2" exclude="Build,Analyzers" />
        <dependency id="ARCtrl.ISA" version="1.0.0-beta.2" exclude="Build,Analyzers" />
        <dependency id="FSharp.Core" version="6.0.7" exclude="Build,Analyzers" />
        <dependency id="FsSpreadsheet" version="5.0.1" exclude="Build,Analyzers" />
      </group>
    </dependencies>
  </metadata>
</package>

Dependencies are softer and should work out more fluently.

REMOVE PAKET
...
and also some other minor 60 files 😅


bird: > v1.6.5 update

Calico: v3.5.0
We are currently working on cross-cluster configuration between two clusters both running calico. Our pod communication is working and we are happy with the setup.
To enable Kubernetes Service <-> Service communication we need calico nodes bgp agents (bird) to set LLGR (2 minutes). More information can be found here: https://vincent.bernat.ch/en/blog/2018-bgp-llgr
Currently the routing node takes 2 minutes to update, due to GR setting. This means Service requests fail for 2 minutes. Setting llgr = 2m and setting gr = 0m, should preserve the guards against flapping, but also enable quick failover for single routing nodes.
Slack thread discussing this: https://calicousers.slack.com/archives/C0BCA117T/p1551353214002600
Thank you.

Sorry for the delay - this sounds like something that would be good to do.
We'll need to merge in the latest BIRD with our changes and do some rigorous testing of it as a first step.

@george-angel FYI, I'm working now on updating our BIRD fork to upstream v1.6.7.  (https://github.com/projectcalico/node/pull/314)
Please can I check with you: once that is in place, are you also asking/suggesting that calico-node by default emits specific LLGR and GR settings for all of its BGP peering configs?  Or do you already have some workflow of your own for overriding our BIRD config, and so you only need the upgraded BIRD code?

@neiljerram great news.
We do not have any workflow yet. But when we started working on this, we thought we could conceivably overwrite the config with the values I mentioned. We then realised our config had no effect since the version was too old and didn't support the settings.
So if you chose to include those by default - great, less custom code on our side. If not, we would have an init-container of some sort to load the config.

We found an alternative in exposing Service objects cross-cluster: https://github.com/utilitywarehouse/kube-service-mirror so no longer need this.
Closing. Thank you all.

We found an alternative in exposing Service objects cross-cluster: https://github.com/utilitywarehouse/kube-service-mirror so no longer need this.
Closing. Thank you all.

@george-angel , That's exactly where i started with. But, found that pod-to-pod communication is the prerequisite as mentioned here.


Adjust translation system

Implement the directory structure for different language files (do not use big one file, with every string).
Details: #53 and Application. Translations page at wiki.

Please, let me know, if you are done with developing translation system, so I can update our Wiki page:

Add correct paths to translation files in repo
Correct or update translation examples

Thank you!

Examples will be okay, I'll adjust paths in a minute.


Test suite is broken

With latest master it's currently impossible to run the test suite.
Fails with:
phpunit --configuration tests/phpunit.xml
Hoa main file (Core.php) must be included once.

Problem only appears when using phpunit, that is installed globally via composer global require "phpunit/phpunit=4.7.*"[1].
Running bin/phpunit --configuration tests/phpunit.xml works fine.
Once "hoa/bench"       : "~<IP_ADDRESS>" is removed from require-dev in composer.json the phpunit version installed via composer global also works fine.

This is actually an issue for @Hywan
I would like to keep the ability for people to just run phpunit as a globally installed binary, unfortunately this is now broken if Hoa\Core is installed both globally and within the project. Both the phpunit and composer projects themselves had issues like this, but for each of them it was important enough to fix this problem.
The question is: is it important for Hoa to fix this as well? Alternatively, is Hoa\Core really needed as a dependency?
I can see that @Hywan does not consider this a bug though. If he doesn't, I think we should just remove hoa/bench from our composer.json. There's going to be a very small amount of people that will use it anyway (probably just me), so it's worth fixing.
But there's a workaround for @DominikTo , you can just run bin/phpunit.

Composer introduces (natural) conflicts when we have stuff installed globally and locally. I have troubles with other projects, not only with Hoa. I am thinking of dropping the files property of the composer.json file of Hoa\Core though, because people encounter errors with this. Hoa is not responsible, but this does not fit to some workflow (even if it fits perfectly to 99.5% of other workflows…).
I consider running phpunit globally as an error. You must run bin/phpunit because it's a dependency. You will meet equivalent errors with C or Python shared libraries for instance. Always use local distributions and binaries, that's the rule.
Also, I don't care if we drop Hoa\Bench. I wasn't even aware that sabre/vobject were using it :yum:!

It definitely makes sense, and I know Hoa is not the only project that has/had problems with this.
For me it's important that we don't have to change how people work with this. So the real question for me, are you willing to make this change, or should we remove the dependency.
I won't remove the code that uses Hoa\Bench though, but I'm ok with forcing myself to manually add the dependency whenever I need it. We used Hoa\Bench in the past for benchmarking, but I only very recently added it to require-dev, which is when this error started appearing.

Consider I will work on it as soon as possible :-).

Please open an issue on Hoa\Core too (thanks :-)).

Awesome to hear =) Will do this a bit later this afternoon.

Reported upstream.

It looks like this has been fixed!

I was mistaken. This is still an issue. I'm going to move Hoa/Bench from require-dev to suggests.


Merge milestones/M162 to releases/shipped

Release notes:

Fixes an issue where File Explorer does not refresh after running gvfs sparse
Allows hooks to be configured in local git config files
Fixes an issue where gvfs sparse warns about dirty files inside the sparse set
Fixes an issue where gvfs sparse warns about dirty files that are inside non-recursive entries in the sparse set
Various other bug fixes and performance improvements

/azp run GitHub VFSForGit Large Repo Build

/azp run GitHub VFSForGit Large Repo Perf Tests

@jrbriggs the results of "GitHub VFSForGit Large Repo Perf Tests" look roughly the same as the last run on releases/shipped.


CCC

Hello,
I am working on dubins path, and your code works great!!!.
I wonder if your code includes CCC configuration? For any set of initial and final points, I could get only CSC configuration. If the code does include CCC configuration, please suggest some set of initial and final conditions, which results in this.
Thanks

Yes, CCC configurations are produced by the code. Typically this occurs when a pair of configurations are very close together.
q_0 = (0,0,0) and q_1 = (0,0,pi) should produce the results you're looking for

Hello Andrew,
Thanks for the reply,
I could produce required results, by your suggestion.
With Regards
Avinash S
On Tue, Jul 7, 2015 at 6:16 AM, Andrew Walker<EMAIL_ADDRESS>wrote:

Yes, CCC configurations are produced by the code. Typically this occurs
when a pair of configurations are very close together.
q_0 = (0,0,0) and q_1 = (0,0,pi) should produce the results you're looking
for
—
Reply to this email directly or view it on GitHub
https://github.com/AndrewWalker/Dubins-Curves/issues/4#issuecomment-119068559
.


PickerDialog not working in a Fragment

Calling goWithDialog in a Fragment will cause a crash.
I must miss something in the onAttach of MusicPickerDialog.

Fixed in the commit 2287121.


WIP : Proc tree

procedural trees using :

procedural_mesh/procedural_material from @VinhTruongAmbient
TreeMesh, my proposition of procedural pseudo-random tree generation Class

disclamer : transitional code, awaiting for the dependency system to land :)

Hey there!
Hope you're doing well. We're gearing up for our next update and while we won't be able to get this in for this update, we'd love to see it as part of the next one! Would you be able to try converting it to a package? Check out guest/rust/packages/std 🙂


Add column filter component

Created column filter component.
2 different options to handle date with time:

Display both date & time in same text field.
Display date & time separate.

Turned the menu component's background into a mixin.
Labeled inline inputs only get padding-right set if a status is present.
.iui-input-combo .iui-overlay should be removed from this & added into /inputs/ eventually, but wanted to keep the scope as contained as possible. Classes are setup as to not introduce breaking change when this eventually happens.

@bentleyvk The tests on the column filters are giving results I didn't expect.  I tried to leave a comment directly on this image, but I couldn't find the option in GitHub.
I applied 16px padding to the <section> so that we could capture the drop shadow effect.  I'm not sure why, but the right side seems to get cutoff. I approved the tests as is because I can confirm that the results are still correct, but thought I would ask if you know of a solution?

Looks ok in current state.
The only thing we need to think about is how to handle date input in react. We are not using <input type='date'> which handles a lot of things for us.

I think we really can't use it because if I am not mistaken it will open native date picker in modern browsers. In other project I was using date-fns to parse and validate the date string that was written by hand.

@FlyersPh9 Is this toggle really supposed to be on the left? I just look at it and cannot get used to..

What if we put it aligned all together?


About function update_opt_from_json

The function [update_opt_from_json] is to exclude some parameters that need to be manually updated, and then used to update other parameters with the same name as the command line parameters but different from the default value of the command line。right?
What does this line of code do?
https://github.com/ramdrop/stun/blob/0414dec2715d69d83b8a87b5d612a2b6a9fe54af/options.py#L69

You are right.
If the act.const attribute is a boolean value, it means that the corresponding argument is a boolean flag (i.e., a flag that takes no argument), and the expression type(act.const) == type(True) will evaluate to True. In this case, the code is checking whether the value of the stored flag matches the default value of the argument. If it does, the corresponding flag is added to the to_del list, because boolean flags do not accept arguments. If it doesn't, the value of the flag in stored_flags is set to an empty string.


driver = WhatsAPIDriverAsync() never loads whatsapp web page

When I instanciate WhatsAPIDriverAsync() the chrome/firefox opens but it never goes to the whatsappweb page. It keeps on a blank page. Is anyone aware of this? I didn't see any issue about it.

Found the issue:
on chatbot.dependencies.WebWhatsappWrapper.webwhatsapi.async_driver you have to set the __init__ autoconnect parameter = True


Possible problem with gcc-6 docker image

The gcc-6 build has been failing due, with an error message indicating that it is out of space (see #215)
Looking at the docker images, the gcc-6 image is close to 4GB while the other compilers are closer to 1GB. See: https://hub.docker.com/r/axom/tpls/tags
It looks like the gcc-6 docker image might be using the gfortran-7.
https://github.com/LLNL/axom/blob/38f974aaecb7ffcb2889781d31846504b01c53c2/scripts/docker/dockerfile_gcc-6#L1-L6
To resolve this, we might need to fix and rebuild the axom/tpl/gcc-6 image against gfortran-6.

In the short term, I'd recommend disabling the gcc-6 CI plan.

@davidbeckingsale, @keithhealy  -- Is there any reason that the docker axom/compiler images for gcc do not all contain gfortran ?
It looks like gcc-5 does -- https://github.com/LLNL/axom-docker/blob/master/gcc-5/Dockerfile
But the others do not.

This was disabled a while ago.


feat: add more example self-podmonitorings

The gmp-operator exposes Prometheus metrics that can be helpful to debug issues with managed-collection. This is also the case with the managed alertmanager.
We have examples of how to scrape metrics from other components, but not the operator or the alertmanager.
So here we provide examples to supplement the self-monitoring exporter documented in
https://cloud.google.com/stackdriver/docs/managed-prometheus/exporters/prometheus?hl=en.
Partly addresses #793.

Fixes https://github.com/GoogleCloudPlatform/prometheus-engine/issues/1123


Add Nitesh232

Related issue

What changes does this PR do?
Screenshots (If any)
Questions

Thankyou @aparna2071 @bkpecho  @E-fais


Can change the hub-nva.json setting to keep connect via jb-vm1?

After run the following command:
azbb -s <subscription_id> -g hub-nva-rg -l  -p hub-nva.json --deploy
Can't connect to hubjb-vm1, s1jb-vm1 and s1jb-vm2 via jb-vm1.
Can change the hub-nva.json setting to keep connect via jb-vm1? thanks.

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

ID: 104eba32-c77e-b013-e161-ff616d16a0f7
Version Independent ID: 3bc27d0a-ef32-f5f6-4c85-fe8e2e45155e
Content: Implementing a hub-spoke network topology in Azure
Content Source: docs/reference-architectures/hybrid-networking/hub-spoke.md
Service: guidance
GitHub Login: @telmosampaio
Microsoft Alias: pnp

Do you know if you could connect to these VMs before running that step (hub-nva.json)?

Update: Looks like this is a bug in the deployment. We're following up.

I'm not sure if this is correct or not, but it seems that the default UDR in hub-gateway-rt broke my site-to-site VPN connections when the RT was applied to the hub-vnet's gateway subnet.  When testing, I removed the default route from this table (<IP_ADDRESS>) and replaced it with two more specific routes (<IP_ADDRESS>/16 aka spoke1) and (<IP_ADDRESS>/16 aka spoke2) and then, the VPN functioned and ping between networks worked.

Thanks for reporting this issue. This should be fixed by mspnp/reference-architectures#185


i18n(ko-KR): update tutorial/6-islands/4.mdx

Description (required)

update tutorial/6-islands/4.mdx
#10347

Related issues & labels (optional)

Closes #
Suggested label:

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

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

Tracked Files

File
Note

ko/tutorial/6-islands/4.mdx
Localization changed, will be marked as complete.

Warnings reference

Icon
Description

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


Edits to User Guide

Edited Quick Start section.
Added mockup of UI.
Added Delete Group feature.
Added Delete Group feature to table.

Codecov Report

Merging #27 (90700d7) into master (c511490) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #27   +/-   ##
=========================================
  Coverage     72.15%   72.15%
  Complexity      399      399
=========================================
  Files            70       70
  Lines          1232     1232
  Branches        125      125
=========================================
  Hits            889      889
  Misses          311      311
  Partials         32       32

Continue to review full report at Codecov.

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


UITableView in DetailView

A Reopen of case #31
Hi, I've tried to implement a UITableView inside the DetailView but as mention in #31 the scroll acts up and it doesn't function the way it should.
I tried disabling the scroll on the table view and yes that does make the scroll work properly but then when I scroll to the bottom it's cutting off the tableview as in it's not resizing to the height of the tableview.
I want to achieve something like:

This is what the result is:

The table view should show all the way until Row:2 Section:5 but it is cut off.
Any help would be much appreciated. Thanks in advanced.

Did you managed to solve this ?
If not could you share an example project ?

I asked a very similar question and gave you a sample project. Could you please have a look at it.

@mteera I can't find it. Could you please link it ?
@zacadams01 Did you have the same issue even with the 1.3.3 version ?

@PaoloCuscela  did you look at https://github.com/PaoloCuscela/Cards/issues/41 ?

Sorry I thought I responded to this case. I solved my problem, probably not in the most efficient or best way. But it works and it works for me. Hopefully with this a proper fix can come about.
Firstly I set an outlet for the fixed height constraint for the tableView on the CardViewController (The view controller shown when the card is open)
Secondly I made this function that gets the content size of the tableview (All heights of cells, headers, footers added up) then set the tableView height constraint to equal the content size, all within the CardViewController. I only call this once the table view has been reloaded and all data loaded:
 func resetViewAndPost() {

    if UIScreen.main.nativeBounds.height == 2436 { //only checking for portrait bounds
        // IS IPHONE X add extra bounds for bottom
        self.tableViewHeightConstraint.constant = self.tableView.contentSize.height+30
    } else {
        self.tableViewHeightConstraint.constant = self.tableView.contentSize.height
    }

    // Set the views height to the content size of the table view
    self.view.frame.size.height = self.tableView.contentSize.height

    self.viewDidLayoutSubviews()
    self.tableView.layoutIfNeeded()
    self.tableView.updateConstraints()

    // Post a flag
    NotificationCenter.default.post(name: NSNotification.Name(rawValue: "resetDetailView"), object: nil)
}

Add Notification Receiver in the viewDidLoad of DetailViewController in the Cards files
NotificationCenter.default.addObserver(self, selector: #selector(self.resetDetailViewHeight(notification:)), name: NSNotification.Name(rawValue: "resetDetailView"), object: nil) //Requires Reset Of View
Then I add this function to the DetailViewController that is called when Post message is received which resets the frame to the new height of the CardViewController
 @objc func resetDetailViewHeight(notification: NSNotification) {
    if let detail = detailView {

        detail.alpha = 1
        if UIScreen.main.nativeBounds.height == 2436 {
            // IS IPHONE X add extra bounds
            detail.frame = CGRect(x: 0,
                              y: card.backgroundIV.bounds.maxY,
                              width: scrollView.frame.width,
                              height: detail.frame.height+30)
        } else {
            detail.frame = CGRect(x: 0,
                                  y: card.backgroundIV.bounds.maxY,
                                  width: scrollView.frame.width,
                                  height: detail.frame.height)
        }

        scrollView.contentSize = CGSize(width: scrollView.bounds.width, height: detail.frame.maxY)

    }
}

So now once you have finished getting your data and reloading the tableview you call resetViewAndPost() and it will set the constraints and reset the card view bounds.
I hope this makes sense, I would make an example project but I really don't have that much time with Work, Study on the Side Stuff. But I'll try and make one if these instructions aren't that clear :)
This doesn't enable the tableview to be seen from the inital card before it is presented.

@PaoloCuscela I had this problem on what ever version was the latest when I made this ticket. I'm not sure if it is still a problem in any newer versions, if there has been, but this method hasn't let me down.

I also disabled the scrollView on the tableView in CardViewController
self.tableView.isScrollEnabled = false

I managed to solve this by changing in DetailViewController -> viewDidLoad()
if let detail = detailView {

            scrollView.addSubview(detail)
            detail.alpha = 0
            detail.autoresizingMask = .flexibleHeight //previously .flexibleWidth
        }

Can you do some testing and see if this solves your issues ?

Sorry you'll have to explain a bit clearer than that. What do I do inside DetailViewController?

Actually it's work better with this:
detail.autoresizingMask = [.flexibleBottomMargin, .flexibleHeight]
Tested in UICollectionView and works!

I got the same issue,
first of all you need to make your tableView unscrollable
self.tableView.isScrollEnabled = false
second you need to determine the content height of your tableView, I declared a variable called tableViewHeight to get this value
`var tableViewHeight: CGFloat {
tableView.layoutIfNeeded()
    return tableView.contentSize.height
}`

After that you need to set of height of the entire view to the height of your tableview after reloading data.
self.view.frame.size.height = self.tableViewHeight


Addition of University - Seoul National University of Science and Technology

Hello JetBrains,
I am requesting to add my university.
Please accept my request!
Thank you!

@yahyo7 I am sorry, the domain jnu.ac.kr is removed from our trusted domains list because it was abused in the past. If you are the student of this school, please enroll to GitHub Student Developer Program. Then apply for JetBrains educational subscription with your GitHub account (GitHub tab at https://www.jetbrains.com/shop/eform/students).

What about seoultech.ac.kr(Seoul National University of Science and Technology)?


Make the lightmap size hint property appear as read-only in the editor

Lightmap Size Hint is set on import or when modifying a PrimitiveMesh's size, so manual changes to it are often lost.
However, being able to see it for debugging purposes is useful, so it's visible as a read-only property. This does not impact your ability to set lightmap_size_hint from a script (for procedural generation).
See discussion starting from https://github.com/godotengine/godot/pull/75164#issuecomment-1478876239.
Preview

I've improved documentation for the Mesh.lightmap_size_hint property.

Since #75164 the user has more control over an individual mesh instance's lightmap size. I think setting the hint to read-only makes more sense now

Although the lightmap size multiplier is nice, there are still use-cases for manually defining the lightmap size of an object in real units (pixels in this case)
https://github.com/godotengine/godot-proposals/issues/11383
I wrote up the above proposal earlier this week specifically because I was running into the the issue of lightmap size hints being reset.
BUT we still need a way to generate better sane defaults for the lightmap hint on imported scenes based on mesh size. Currently large meshes that are impractical to run through Godot's UV2 generation are assigned stupidly small lightmap size hints that mean now you'd be turning the lightmap size scale not to 2x or even 4x but probably on the order of 32x to 64x in many cases.
Basically my point is: although the lightmap size hint SHOULDN'T need to be edited manually, and will often be reset, for me specifically it's the only way I've used successfully so far to get the result I need (actual decent texel resolution for large chunks of a landscape that have UV2s authored externally)
If we could get lightmap size hints to be set automatically based on the size of imported meshes that aren't run through the godot UV generation, that would be ideal. At that point I'd be 100% on board with this change.


Meta key is not working on macOS.

I found this solution for iTerm2 and default terminal app.
And some discussions on here #62 #93
But I can't figure out how to make it works on Alacritty.
Defending on #93, it seems I need to add every key combination to config file, that's fine but I want more like iTerm2 or terminal way.
I want to know how Meta key works on Alacritty too.
Thanks in advance.

This seems like the same issue as #62. Is this somehow different?

Sorry for my bad, no difference.
I should comment existing issue rather than create an issue next time.
Could you tell me how is work about this issue going on?

I don't think anyone is working on it at the moment; a common work-around is to add keybindings as you've mentioned.


fast float: compiler warning about misleading indentation

../git/submodules/Little-CMS/plugins/fast_float/src/fast_8_tethra.c: In function ‘PerformanceEval8’:
../git/submodules/Little-CMS/plugins/fast_float/src/fast_8_tethra.c:234:57: warning: this ‘else’ clause does not guard... [-Wmisleading-indentation]
  234 |                                                         else
      |                                                         ^~~~
../git/submodules/Little-CMS/plugins/fast_float/src/fast_8_tethra.c:246:64: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘else’
  246 |                                                                Rest = c1 * rx + c2 * ry + c3 * rz + 0x8001;
      |                                                                ^~~~

(This bothers me mostly because I needed a static build.)

Should be fixed by ca207ee4dd4ec490e8a42431784278917ea93ea7

Thanks.


Gugu72: Watch goivvy.com

Gugu72 requests the watch of the watch_keyword goivvy\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

Approved by cigien in Charcoal HQ


Corrections to ubuntu install docs, based on attempting to install on Wily

Proposed changes

Added - to apt-key command so it should use stdin
Changed apt repo layout in add-apt-repository command

The apt repo layout seems wrong, it only worked after the proposed change.
Also apt-key seems to need - to look at stdin; otherwise I got gpg: can't open ': No such file or directory`
Unreleased project version (optional)

Related issues (optional)

I tested the instructions on Ubuntu Xenial and it worked with and without the -, so I'll allow the  change. However, Wily is not supported for Docker 1.13.
I rebased your patch and added the change to the Debian instructions as well, to be consistent. I'll merge after the tests complete. Thanks for your contribution.


Release updated compiled build with support for Python 3.11

With the release of Python 3.11:
https://docs.python.org/3/whatsnew/3.11.html
Oso requires a new compiled release to support this version of Python:
❯ python --version
Python 3.11.0
❯ python -m pip install oso
ERROR: Could not find a version that satisfies the requirement oso (from versions: none)
ERROR: No matching distribution found for oso

Apologies if this isn't actually stemming from oso itself, just noticed it with compiled code such as Oso, so wanted to report it for awareness, if nothing else.

https://github.com/osohq/oso/releases/tag/v0.26.4 released
Thanks for your help guys and gals (and for the +1 votes to those who were watching this!)


Fix for compiling error

# command-line-arguments
./namenode_exporter.go:243:15: e.pnGcCount.Set undefined (type prometheus.Counter has no field or method Set)
./namenode_exporter.go:244:14: e.pnGcTime.Set undefined (type prometheus.Counter has no field or method Set)
./namenode_exporter.go:247:16: e.cmsGcCount.Set undefined (type prometheus.Counter has no field or method Set)
./namenode_exporter.go:248:15: e.cmsGcTime.Set undefined (type prometheus.Counter has no field or method Set)

and
# command-line-arguments
./namenode_exporter.go:243:16: e.cmsGcCount.Set undefined (type prometheus.Counter has no field or method Set)
./namenode_exporter.go:244:15: e.cmsGcTime.Set undefined (type prometheus.Counter has no field or method Set)

fixed in https://github.com/wyukawa/hadoop_exporter/pull/8


Podspecs are breaking with nightly build version in package.json

When using a nightly, the pods fail to build. The podspecs look for the version in package.json. Package.json in master uses "100.00" as version, but the nightlies use a version that the podspecs can't recognize.
Podspec sample
if version == '1000.0.0'
  # This is an unpublished version, use the latest commit hash of the react-native repo, which we’re presumably in.
  source[:commit] = `git rev-parse HEAD`.strip
else
  source[:tag] = "v#{version}"
end

Should be
if version == '1000.0.0' || version.include? "0.0.0-"
  # This is an unpublished version, use the latest commit hash of the react-native repo, which we’re presumably in.
  source[:commit] = `git rev-parse HEAD`.strip
else
  source[:tag] = "v#{version}"
end

React Native version:
System:
    OS: macOS 10.15.5
    CPU: (12) x64 Intel(R) Core(TM) i7-8850H CPU @ 2.60GHz
    Memory: 2.14 GB / 16.00 GB
    Shell: 3.2.57 - /bin/bash
  Binaries:
    Node: 14.2.0 - /usr/local/bin/node
    Yarn: 1.22.4 - /usr/local/bin/yarn
    npm: 6.14.4 - /usr/local/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  Managers:
    CocoaPods: 1.9.3 - /usr/local/bin/pod
  SDKs:
    iOS SDK:
      Platforms: iOS 13.5, DriverKit 19.0, macOS 10.15, tvOS 13.4, watchOS 6.2
    Android SDK:
      API Levels: 28, 29
      Build Tools: 26.0.3, 27.0.3, 28.0.3, 29.0.2, 29.0.3, 30.0.0
      System Images: android-25 | Google APIs ARM 64 v8a, android-28 | Google Play Intel x86 Atom, android-R | Google Play Intel x86 Atom
      Android NDK: Not Found
  IDEs:
    Android Studio: 4.0 AI-193.69<IP_ADDRESS>14223
    Xcode: 11.5/11E608c - /usr/bin/xcodebuild
  Languages:
    Java: 1.8.0_192 - /Users/patrickmcwilliams/.jenv/shims/javac
    Python: 2.7.16 - /usr/bin/python
  npmPackages:
    @react-native-community/cli: Not Found
    react: 16.13.1 => 16.13.1
    react-native: 0.0.0-c3ab2a254 => 0.63.2
    react-native-macos: Not Found
  npmGlobalPackages:
    *react-native*: Not Found

Steps To Reproduce

Include a nightly as the react-native package in your project
run npx pod-install

Expected Results
Pods should be properly. Instead it throws errors.
Errors
>npx pod-install
npx: installed 1 in 1.499s
Scanning for pods...
1.9.3
> pod install
Adding a custom script phase for Pod RNFBApp: [RNFB] Core Configuration
Auto-linking React Native modules for target `moishemobile`: RNCMaskedView, RNCPushNotificationIOS, RNDeviceInfo, RNFBAnalytics, RNFBApp, RNGestureHandler, RNImageCropPicker, RNReanimated, RNSVG, RNScreens, RNVectorIcons, ReactNativeFabric, react-native-safe-area-context, react-native-version-check, react-native-version-number, react-native-webview, and react-native-zendesk-support
Analyzing dependencies
Fetching podspec for `DoubleConversion` from `../node_modules/react-native/third-party-podspecs/DoubleConversion.podspec`
[!] The `FBLazyVector` pod failed to validate due to 1 error:
    - ERROR | version: The version of the spec should be higher than 0.

Aborting run
An unexpected error was encountered. Please report it as a bug:
Error
    at CocoaPodsPackageManager._installAsync (/Users/patrickmcwilliams/.npm/_npx/94893/lib/node_modules/pod-install/build/index.js:2:85721)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    at async CocoaPodsPackageManager.installAsync (/Users/patrickmcwilliams/.npm/_npx/94893/lib/node_modules/pod-install/build/index.js:2:85121)
    at async runAsync (/Users/patrickmcwilliams/.npm/_npx/94893/lib/node_modules/pod-install/build/index.js:2:12925)
    at async /Users/patrickmcwilliams/.npm/_npx/94893/lib/node_modules/pod-install/build/index.js:2:13011

@tom-un and I just realized this the other day. We concluded the version used should change, rather than updating CocoaPods to support v0.0.0, but I don’t recall where we left the discussion wrt what to use as the version.

@alloy for what its worth when i changed the version to something like
0.63.2-c3ab2a254-NIGHTLY
It still worked

The react-native-macos nightly builds are broken in exactly the same way (still).
In the react-native-macos builds, the Azure DevOps publish yaml script for canary builds invokes:
          script: node scripts/bump-oss-version.js --nightly`

(https://github.com/microsoft/react-native-macos/blob/master/.ado/publish.yml#L64)
and the that script renames the version to
  version = `0.0.0-${currentCommit.slice(0, 9)}`;

(https://github.com/microsoft/react-native-macos/blob/master/scripts/bump-oss-version.js#L43)
Is there a reason the nightly builds in both react-native and the out-of-tree platforms just be 1000.0.0-HASH ?

@acoates-ms Had done this work, but it didn’t appear to be for any specific reason, so let’s just standardize on 1000 to mean master and builds from master?

Yeah, The 0.0.0-commitid format was chosen purely to align with the version scheme used by react.  If it's not compatible with react-native, then we should use a different format.
We use 1000.0.0-canary.xxx for react-native-windows.

I’ll do this work 👍

(I’ll be doing this work firs on our macOS fork, as it will be easier for me to test changes.)

As discussed here, I’ll be looking at update CocoaPods instead.

PR created https://github.com/CocoaPods/Core/pull/657

Just gonna resurrect this OLD issue to see what's going on with it (so: non-RN maintainers who are following this issue still: sorry for the notification). I'm still getting this issue with plain react-native and the same error as the original message.
I'm running the latest pod binary but it still happens so I'm wondering if there's another underlying issue. Please let me know if there's any way I can help. Thanks!


Proposal: command dtm show config with no flag to print main config sample

Description
We can now use the command dtm show config --plugin=A-PLUGIN-NAME print a sample config with one plugin/tool. But how to write the main config file: config.yaml?
Design

dtm show config print the text like below:

# config.yaml sample:
varFile: variables.yaml
toolFile: tools.yaml
state:
  backend: local
  options:
    stateFile: devstream.state

# tools.yaml sample:
tools:
- name: github-repo-scaffolding-golang
  instanceID: default
  options:
    owner: [[ githubUsername ]]
    org: ""
    repo: [[ repoName ]]

# variables.yaml sample:
githubUsername: daniel-hutao
repo: go-webapp-demo

@IronCore864 Are there some suggestions?

I'd like to try.


[SPARK-47849][PYTHON][CONNECT] Change release script to release pyspark-connect

What changes were proposed in this pull request?
This PR proposes to change release script to publish pyspark-connect.
Why are the changes needed?
See the SPIP https://issues.apache.org/jira/browse/SPARK-47540.
Does this PR introduce any user-facing change?
Yes, it releases pyspark-connect package into PyPI.
How was this patch tested?
Did the basic test for individual commands. It will be tested during actual release process (and I will cowork together with 4.0 release manager).
Was this patch authored or co-authored using generative AI tooling?
No.

CI doesn't verify this. Merged to master.


WAT

https://github.com/gogits/gogs/blob/35c83f60266fb2178ae69db4b578dad333b6b2ea/modules/ssh/ssh.go#L59

Looks more like a problem in accidentally leaving in test code than anything else.

Hmm... what does WAT mean?

@Unknwon it's an English colloquialism for "what is happening?" or "why is this there?" It's usually used in exasperation or surprise due to something dramatically surprising. It's a derivative of the word "what" or the single phrase "what?"
The reason why the issue reporter posted this is because he wanted to either draw attention to the absolute path at the line referenced, or ask why there's an absolute path to a programmer's PC in there too.

@nicatronTg thanks for the explanation!
The file @overnine points to is completely not used in Gogs, but a prototype of builtin SSH server of Gogs. So don't worry about it :blush:

@Unknwon of course :)
Keep it up! Gogs is quite nifty

http://i0.kym-cdn.com/photos/images/newsfeed/000/173/576/Wat8.jpg?1315930535

It's probably a good idea not to leave prototype code in the master branch.

@bashrc you're right, so we then made a ssh branch.

I'm closing it with the release, feel free to reopen it if you want to continue discussion. :smiley:


OCA for credentials from SIT environment do not have the "non production" watermark

It might be just a simple update to the OCA Bundle for SIT environment
review all Person Credential bundle that are non-production (DEV/SIT/Showcase)

Fixed, confirmed in 1.0.17 1740.


Sunstone: template wizard wipes SCHED_RANK attribute

Description
SCHED_RANK containing expression such as "FREE_CPU * 100 - TEMPERATURE" (this example comes from official documentation) is wiped after template update.
To Reproduce
Steps to reproduce the behavior.

Create a new template
Click update
Click on "Scheduling" tab then on "Policy" tab
Fill "Host Rank" field with "FREE_CPU * 100 - TEMPERATURE"
Click update to save the template
The SCHED_RANK attribute is present in the template
Click update to launch the wizard
"Host Rank" field is now empty
Click update to save the template
The SCHED_RANK attribute is lost

Expected behavior
The SCHED_RANK attribute is preserved after template updates.
Details

Affected Component: Sunstone

Hypervisor: KVM

Version: 5.8.5

Additional context
We've just upgraded from 5.2 to 5.8.5 ans we are loosing all our placements rules!
Thanks for your help,
Laurent

Progress Status

[x] Branch created
[x] Code committed to development branch
[ ] Testing - QA
[ ] Documentation
[ ] Release notes - resolved issues, compatibility, known issues
[ ] Code committed to upstream release/hotfix branches
[ ] Documentation committed to upstream release/hotfix branches

@tinova PR to approve
-One: https://github.com/OpenNebula/one/pull/3843
-Docs: https://github.com/OpenNebula/docs/pull/801

Needs testing

Hi,
Thanks for the fix. I've justed the patch on 5.8.5. It solves half the problem.

The SCHED_RANK attribute remains untouched in the template: OK
The "Host Rank" field in the wizard remains blank while editing the template: NOK

@tinova PR to approve:
-One: https://github.com/OpenNebula/one/pull/3879

I've just tested it on 5.8.5 and everything is fine now.
Many thanks @jloboescalona2 and @tinova!


contrib/backporting: remove requires-janitor-review label

The backport PRs shouldn't add the label requires-janitor-review since
the review is automatically requested by the CODEOWNERS file.
Signed-off-by: André Martins<EMAIL_ADDRESS>

Coverage decreased (-0.003%) to 37.0% when pulling 63c731def489ea24dbecb04a1e9dcc091c543f02 on pr/remove-requires-janitor-review-label into ed6583047c1f8a47f0a2d57188e9341bf71a2df6 on master.

Do we need to backport this?


c/driver/postgresql: Logging appears downstream

When running the pandas test suite with ADBC drivers users currently see this output:
pandas/tests/io/test_sql.py .........NOTICE:  table "test_frame" does not exist, skipping
.........FNOTICE:  table "test_frame" does not exist, skipping
x.........NOTICE:  table "test_frame" does not exist, skipping
..........NOTICE:  table "test_frame" does not exist, skipping
..........NOTICE:  table "test_frame" does not exist, skipping
..........NOTICE:  table "test_frame" does not exist, skipping
..........NOTICE:  table "test_frame" does not exist, skipping
..........NOTICE:  table "test_frame" does not exist, skipping
...................xNOTICE:  table "test_frame" does not exist, skipping
x........WARNING:  there is no transaction in progress
..........WARNING:  there is no transaction in progress
.....................NOTICE:  table "test_frame" does not exist, skipping
.........xNOTICE:  table "test_frame" does not exist, skipping
x...............xNOTICE:  table "test_frame" does not exist, skipping
x.....................................................................................................................................................................ss..............x...................................................................x..................................................................F.............................................................................

Would be nice if those didn't appear downstream

We need to add a notice handler to libpq

I'm just going to suppress it for now (perhaps with an env var to allow it through), with the idea that somewhere between #735 and #924 we'll expose it in the actual driver logs


Add an example for filtering the opposite of "in".  Instead of a value found "in" or belonging "to" a collection, return rows where the value is "not found in" or "does not belong to" a collection.

[Enter feedback here]

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

ID: 9b784f58-59eb-fb06-da8f-4747f6900db3
Version Independent ID: 9b784f58-59eb-fb06-da8f-4747f6900db3
Content: Filter, Search, and LookUp functions in Power Apps (contains video) - Power Platform
Content Source: power-platform/power-fx/reference/function-filter-lookup.md
Service: power-platform
Sub-service: power-fx
GitHub Login: @gregli-msft
Microsoft Alias: gregli

Thanks for your comment, @sovando. This issue has been assigned to the doc author for review.


Stop enforcing Certificate Transparency verification

Chromium started enforcing some Certificate Transparency policies by default
in M53, and refuses to load certain websites when the CT verification fails
while establishing the TLS connection; this affected Crosswalk because we
were using the default CT verifier and policy enforcer, but we did not add
any of the logs approved by the Chromium project (see
net/cert/ct_known_logs_static-inc.h).
Instead of doing so, stop requiring websites to pass Chromium's Certificate
Transparency checks altogether after getting some clarification from
upstream. The biggest impediment to us following Chromium's policy is that
Crosswalk's release cycle would need to match Chromium's very closely to
avoid two risks:

Chromium approves new CT logs, they start being used in new certificates,
Crosswalk does not recognize the new logs and refuses to load a website
with a valid certificate.
Chromium disqualifies a CT log, while Crosswalk does not and can end up
trusting a certificate that Chromium no longer trusts.

Additionally, the aforementioned list of built-in logs that Chromium uses
stops being recognized 70 days after the build date, which can lead our
users to a false sense of security if they do not update their own apps with
a more recent Crosswalk (which we might not even have released yet).
See the discussion in http://crbug.com/669978 for more information.
BUG=XWALK-7398

@xzhan96 @fujunwei @lincsoon @darktears
This achieves the same thing as #3962 in a different way and with a much better explanation.

@xzhan96 @fujunwei @lincsoon @darktears: ping again

nice, I had seen the discussion in http://crbug.com/669978.
LGTM for this patch.


docs(web-app-boilerplate.md):update content

Improve WebApp Boilerplate Page #189
#189
Steps to test

Run project locally

CheckList

[ ] Follow proper Markdown format
[ ] The content is adequate
[ ] The content is available in both english and spanish
[ ] I Ran a spell check

I think we need to work on this in a different issue , the content is nowwhat we intended to include in the documentation page

I think we need to work on this in a different issue , the content is nowwhat we intended to include in the documentation page


SPA mode unsaved changes

Adds unsaved changes functionality to SPA mode using Livewire's new cancellable navigate feature.
This PR is fully working with no errors. It was necessary to add if (typeof @this !== 'undefined') checks to prevent component not found errors in SPA mode due to wire:navigate's lifecycle.
I've tested this in both SPA mode and non-SPA mode with internal links, external links and navigating away with open modals. Everything I checked works.

@tonypartridge Yeah definitely. This depends on min 3.4.10.

Right now, it changes the warning message in the SPA mode. But non-spa mode still has the old one. I think we should use the same message in both.

@taliptako That isn't possible AFAIK. Every browser uses different language for their beforeUnload alert (and it can't be changed). Eg. this is what they look like in Chrome and Firefox:

Unsaved changes alerts in SPAs use custom events, which means they have to use custom alerts instead of the browser's beforeUnload alert. It's the same with any JS framework- see Vue Router's navigation guard docs for example: https://router.vuejs.org/guide/advanced/navigation-guards.html.

It's the same with wire:navigate.
So there's no way to match the browser's beforeUnload alert exactly. If you try and match the language of Chrome's, it won't match Firefox's. And so on... Feel free to make a PR if you think the SPA alert language can be improved, but I think the current alert is quite simple and clear.

Is there a way to perform action other actions like say the user is navigating away and didn't submit the form I want to capture, that and store it that he cancelled that action


Add ETA to dashboard

The new dashboard has a completion bar. It would be handy to have an ETA and perhaps a percentage too.

Those aren't completion bars -- it's responses bucketed by HTTP response code (1xx, 2xx, 3xx, 4xx, 5xx, and the zero-code used to indicate things like network failures).
This is similar to #229 otherwise, which I've put on the "I don't think we'll get to this" because we don't really have the data to provide a useful estimate.


Replace unsupported docker-py with current docker module.

As noted at https://github.com/ansible/ansible/issues/42162 and elsewhere, docker-py is no longer maintained, and ansible now requires the use of it's replacement, the PyPI module named simply docker. Since these conflict, docker-py must be explicitly removed first.
Without this change, the playbook will not run under Ansible 2.6+.

Many thanks!


Hard fail

Hi,
I have purchase fresh domain and server .
but when i send mails it hard fails and show this error:

Our system has detected that this message is 550-5.7.1 likely suspicious due to the very low reputation of the sending 550-5.7.1 domain

Please give me solution.
Thanks in advance.

If you have only recently started sending emails from that IP address then it might be a while before the internet trusts you.
Please also read https://github.com/atech/postal/issues/477 and https://github.com/atech/postal/issues/367

It has to do with the reputation of your IP, even if your emails are legit, but if you start sending large amounts of emails, Gmail will block those emails.
You can prevent this by doing an IP warm up (Google search Sendgrid IP warm up)
Monitor the reputation of your domain/IP with Google Postmaster.


Support Retina Images

You can read a bit more about it here: https://www.sitepoint.com/support-retina-displays/
I provided provided retina sized assets that all end in @2x so the JS method may be the easiest if you are up for it.
Let me know if you have any questions.

After thinking on this, let's swap all of the non-photo assets with SVG versions
folder here: https://drive.google.com/drive/folders/0B5DWXoUiIyAJd21EX3pyLUFhbzQ?usp=sharing
For the photos, you can replace all of the images with their @2x versions I supplied. I checked them and the file size isn't too heavy.

Photos do not appear in higher quality on iPhone or iPad.
How we can help you graphics look good (SVG)
Our Process graphics still appear as lower res jpgs, please change those to SVG as well.


error in demo 102, bwipjs

Hi @oblomov-dev
just after pressing Show Barcode
getting:

and

ah yes, this demo is still under construction, will fix this in the upcoming days. thanks for the hint.

made some updates, it works now on my side

not working on my end
getting an error here

here, on the marked line

ah i see, added again a fix. you can try again.

still error on the same line

oh forgot to update the main repo, you can try again

works !