MythTV: 31.0 -> 32.0

MythTV
current version 31.0
desired version 32.0
Note to maintainer
@https://github.com/titanous
I tried installing Mythtv 31.0 in the latest version of NixOS and the following error appeared.
collect2: error: ld returned 1 exit status
> make[2]: *** [Makefile:205: mythavtest] Error 1
> make[2]: Leaving directory '/build/source/mythtv/programs/mythavtest'
> make[1]: *** [Makefile:67: sub-mythavtest-make_first] Error 2
> make[1]: Leaving directory '/build/source/mythtv/programs'
> make: *** [Makefile:66: programs] Error 2
For full logs, run 'nix log /nix/store/i7hayl96078skrs46yksjqxjsh31cmfv-mythtv-31.0.drv'.
Reading the log displayed   error: experimental Nix feature 'nix-command' is disabled; use '--extra-experimental-features nix-command' to override

I am currently building MythTV 32.0 (sha256 = "0i4fs3rbk1jggh62wflpa2l03na9i1ihpz2vsdic9vfahqqjxff1") with two patches. The first is called disable-os-detection.patch:
diff -Naur a/configure b/configure
--- a/configure	2022-04-20 16:54:16.201216465 -0400
+++ b/configure	2022-04-22 14:39:29.998895626 -0400
@@ -5894,9 +5894,9 @@
     die "ERROR: cannot find soundtouch 1.8.0 or later."
 fi

-if [ $target_os = "linux" ] ; then
-    . /etc/os-release
-fi
+#if [ $target_os = "linux" ] ; then
+#    . /etc/os-release
+#fi

 # libudfread
 if enabled system_libudfread ; then

The second patch is called fix-qmake-var-syntax.patch.  I patched it up upstream, and it looks like my patch has been merged. Here is that patch:
diff -Naur b/configure c/configure
--- b/configure	2022-04-22 14:39:29.998895626 -0400
+++ c/configure	2022-04-22 14:38:36.688266601 -0400
@@ -6296,7 +6296,7 @@

 # add some linker flags
 check_ldflags -Wl,--warn-common
-check_ldflags '-Wl,-rpath-link,\${SRC_PATH_BARE}/external/FFmpeg/libpostproc:\${SRC_PATH_BARE}/external/FFmpeg/libswresample:\${SRC_PATH_BARE}/external/FFmpeg/libswscale:\${SRC_PATH_BARE}/external/FFmpeg/libavfilter:\${SRC_PATH_BARE}/external/FFmpeg/libavdevice:\${SRC_PATH_BARE}/external/FFmpeg/libavformat:\${SRC_PATH_BARE}/external/FFmpeg/libavcodec:\${SRC_PATH_BARE}/external/FFmpeg/libavutil:\${SRC_PATH_BARE}/external/FFmpeg/libavresample'
+check_ldflags '-Wl,-rpath-link,\$\${SRC_PATH_BARE}/external/FFmpeg/libpostproc:\$\${SRC_PATH_BARE}/external/FFmpeg/libswresample:\$\${SRC_PATH_BARE}/external/FFmpeg/libswscale:\$\${SRC_PATH_BARE}/external/FFmpeg/libavfilter:\$\${SRC_PATH_BARE}/external/FFmpeg/libavdevice:\$\${SRC_PATH_BARE}/external/FFmpeg/libavformat:\$\${SRC_PATH_BARE}/external/FFmpeg/libavcodec:\$\${SRC_PATH_BARE}/external/FFmpeg/libavutil:\$\${SRC_PATH_BARE}/external/FFmpeg/libavresample'
 enabled rpath && add_ldexeflags -Wl,-rpath,$libdir
 enabled rpath && add_ldlibflags -Wl,-rpath,$libdir
 test_ldflags -Wl,-Bsymbolic && append SHFLAGS -Wl,-Bsymbolic

My current default.nix derivation is like this:
  version = "32.0";

  src = fetchFromGitHub {
    owner = "MythTV";
    repo = "mythtv";
    rev = "v${version}";
    sha256 = "0i4fs3rbk1jggh62wflpa2l03na9i1ihpz2vsdic9vfahqqjxff1";
  };

  patches = [
    # Disables OS detection in configure script
    ./disable-os-detection.patch
    ./fix-qmake-var-syntax.patch
  ];

Sorry that was back in April and I didn't propagate my changes to NixOS yet!

@zero-one01 it looks like your branch and mine are basically the same except for the fix-qmake-var-syntax.patch.  I don't know if it is better to add my patch, or for you to move to a version of MythTV after the pull mentioned above.

@kleytr6s, I didn't paste my whole default.nix, there are also new deps (soundtouch, libzip) which you can see in the branch by @zero-one01

I added the fix-qmake-var-syntax patch on top of @zero-one01 's  branch here. I haven't tried building it yet since my machine is already building my original version of the derivation in the background (due to NixOS upgrade), and it takes hours. That is actually what prompted me to notice this issue :).

@acarrico I'll try if my issue is gone with your patch now (I also need lots of time for one build).
Going forward I think it's best to use the release version of MythTV 32 and your patch for bumping the version in NixOS.
I'll however try the other route with the MythTV version after the merge of your fix as I want to set up a combination of official and my own packages anyway.

I'm happy to confirm that both routes work. for the one with the updated MythTV version I took the commit of the pull request @acarrico mentioned.
@acarrico would you be so kind and open a pull request for the version bump ?


Fix: zi ensure single trigger mode is always set

Fixes garbage data on ZI
@WilliamHPNielsen @jana-d fixes what we spent most of friday debugging

Need to remember to fix scopemode as hacked in https://github.com/qdev-dk/Qcodes/pull/11

We should probably try to only use one scope instance and then call
unbind and finish in the end. That seems to be what the ZI gui does. Verify this from the gui log file.


Vector tiles

Thank you so much for this!
Sorry for being so ignorant: This is probably not the right forum for making feature request, but the final piece of the jigsaw which would make this package perfect in my opinion is inclusion of a vector tile example layer.

https://rawgit.com/allenhwkim/react-openlayers/master/app/index.html#/layers/vector

https://openmaptiles.org/docs/website/openlayers/

Do you want the example comPlate?

A complete working example of vector tiles would make an awesome addition.  Vector tiles are really becoming incredibly popular these days and so far nobody else has been able to show how to integrate vector tiles in a React app.  Thanks for the amazing work you have done.

Here I added the VectorTile example which is presented from openlayers.org
http://openlayers.org/en/latest/examples/mapbox-vector-tiles.html
https://rawgit.com/allenhwkim/react-openlayers/master/app/index.html#/layers/vector-tile
I tried to use this, but it did not quite follow OpenLayer conventions, IMO
https://openmaptiles.org/docs/website/openlayers/
You may play around little bit and LMK if I need to improve any.

VectorTile has been implemented.


In imagemodel mutations split business logic to services

Split logic like it's already done in user mutations

Done in ~1 hour


Improve example applications

The examples ought to be more consistent with each other, and well
documented.

Fix, simplify and document the Gin example
Fix, simplify and document the net/http example
Fix, simplify and document the Negroni example
Fix, simplify and document the Revel example
Fix, simplify and document the goroutine use case
Add a Martini example

The interrupt issue is resolved on the target branch already 🎉


Instance function call style & extension user-defined functions

Is your feature request related to a problem? Please describe.
Writing a long chain of Bicep functions is much harder to do, compared to C#. For example:
var x = map(items(mapValues(groupBy(filter(o, item => item.deploy), item => item.id, item => item.roles), item => reduce(item, [], (cur, next) => union(cur, next)))), item => {
  id: item.key
  roles: item.value
  })

Describe the solution you'd like
Call all object/array functions like instance/extension functions, and also allow defining UD extension functions.
The above could be rewritten as:
o
  .filter(item => item.deploy)
  .groupBy(item => item.id, item => item.roles)
  .mapValues(item => item.reduce((cur, next) => cur.union(next), []))
  .map(item => {
    id: item.key
    roles: item.value
  })

It's much easier to read and write. Additionally, completion would offer the available functions for each type, simplifying discovery.
For UDFs:
func sayHelloString(this name string) string => 'Hi ${name}!'

Usage:
var s = 'Bicep';
var h = s.sayHelloString();

Closing as dup of #4435. Would love to get to this as it makes the code a lot easier to work with overall!


Error: Expected buffer for OUT transfer (based on bmRequestType) when executing clearHalt.

Bug Description:
It seems like there's a problem with WebUSB API's clearHalt implementation. Executing clearHalt throws an error:
Expected buffer for OUT transfer (based on bmRequestType)

From what I understand, the error originates at:
https://github.com/node-usb/node-usb/blob/e9d33d81c495e33875b0dd85942af6335d85a27c/tsc/usb/device.ts#L137-L139
Which is called by:
https://github.com/node-usb/node-usb/blob/e9d33d81c495e33875b0dd85942af6335d85a27c/tsc/webusb/webusb-device.ts#L261
In this line, the value 0 is passed as data_or_length, but since it's an OUT request, controlTransfer expects a buffer and fails.

Steps to Reproduce:

Execute clearHalt on a stalled endpoint of a WebUSB-API USB device.

Additional Information

Operating System: Ubuntu 22.04
Runtime (node -v or electron -v): Electron 13.6.9
Node USB Version (npm ls usb): 2.4.3 (however it seems like it might still be present in the newest version)

Yeah, I can see the issue.
Some possible ways to resolve this and keep the code clean:

create a new transfer object in clearHalt and leave the device controlTransfer as is - duplicates code
remove the length or buffer size check in device controlTransfer - loses a guard
extend the data_or_length union type to also accept false to skip the checks

Thoughts or other suggestions?
cc @mildsunrise

@thegecko Why not create a new empty buffer in clearHalt, and pass that to controlTransfer?

@thegecko Why not create a new empty buffer in clearHalt, and pass that to controlTransfer?

I think that would only help with OUT endpoints. AFAICT the problem also exists for IN endpoints, too.

@thegecko Do you mean when using clearHalt on IN endpoints?
From what I understand, clearHalt is always an OUT control transfer. The actual endpoint is passed in wIndex. Feel free to correct me on that if I'm wrong please.

From what I understand, clearHalt is always an OUT control transfer. The actual endpoint is passed in wIndex. Feel free to correct me on that if I'm wrong please.

In this case your suggestion should work!

How does #636 look?

@thegecko I think that it might fail because of what I mentioned above.
It doesn't matter if the endpoint you're running clearHalt on is an IN or OUT endpoint, clearHalt itself still goes through as an OUT control transfer.
The bug I'm reporting originated in this code:
https://github.com/asivery/node-mass-storage/blob/master/src/usb-mass-storage.ts#L158-L162
It's running clearHalt() on an IN endpoint, but the error was still 'Expected buffer for OUT transfer (based on bmRequestType)'

Oh I see, I was assuming clearHalt gets called on the endpojnt being cleared, but it's actually on LIBUSB_RECIPIENT_ENDPOINT
PR updated accordingly.

@thegecko Looks good!


Add Travis support

It is a good step to the project if we start to run tests in a CI tool like Travis.

Closed via 167f7a969d1c2aa86f97c1b4ac9c13c8e41238f5


Which Java APIs are supported?

I have tried to read the documentation, but I do not understand which Java APIs I can and cannot use.
For example, I understood that Java FX and Swing are not supported, but I can create my web application graphics using org.teavm.jso.dom.html.HTMLButtonElement, org.teavm.jso.dom.html.HTMLDocument, and org.teavm.jso.dom.html.HTMLElement.
However, I could not find the relevant Javadocs.
In practice, I have to play with HTML elements and CSS styles for the graphical part, while Java is mainly useful for the client business logic. Please correct me if I am wrong.
Having said that, how do I know which standard Java classes to use?

The link to set of supported classes from Java standard library (https://teavm.org/jcl-report/recent/jcl.html) is mentioned here: https://teavm.org/docs/runtime/java-classes.html
As for JSO, I publish both Javadocs and sources to Maven Central, which is requirement by Maven Central. By default, IDEA picks these and shows autocompletions, etc. But if for some reason you want them as separate jars, you can search on Maven Central for TeaVM artifacts of some certain version and download Javadocs. For example, for version 0.10.1, which is as for now is the latest, you can find them here: https://repo1.maven.org/maven2/org/teavm/teavm-jso-apis/0.10.1/

Please correct me if I am wrong.

In the practical cases, the gap between Java and JavaScript is not fully transparent, so you can have some issues here. So it depends. Personally, I write everything in Java, because I use TeaVM primarily to compile single app both to Android, iOS (Graal Native Image) and web, sharing 99.9% of code between platforms.

Personally, I write everything in Java
So how do you build the GUI? Do you use the classes in the org.teavm.jso.dom.html package or do you use other classes?

I use TeaVM primarily to compile single app both to Android, iOS (Graal Native Image) and web
Could you share some more information on this point? How do you do it?

So how do you build the GUI? Do you use the classes in the org.teavm.jso.dom.html package or do you use other classes?

I render everything using OpenGL, so it's either WebGL on the web, EGL on Android and MetalANGLE on iOS. Every OpenGL call is made though some platform-independant interface which has implementation over WebGL and EGL. Entire GUI is rendered by home-grown UI framework.

There's a lot of choice. Of course, you can try to proceed with some JS framework (like React) to build UI and try to use TeaVM only to expose business logic. However, you should remember, that directly calling Java from JS and back is not possible, so you end up with wrappers and annotations. If interaction layer between Java and JS is limited, then it would be a working solution.
Another way is to do everything from Java. If you are ok to deal with raw DOM or you are ready to invent your own Java framework, then this would be a working solution. You can also try to find something, may be someone already created and published any Java framework for front-end development. For example, you can take a looks at following:

https://github.com/fb71/areca
https://github.com/reportmill/SnapTea
https://github.com/konsoletyper/teavm-flavour (this is an Angular-like framework that I used to maintain, but then abandoned, you can try to revive it for your own needs)

Otherwise, TeaVM is not for you. Despite I'd like to develop TeaVM ecosystem, I simply have no resources for it, so what I can do is to maintain compiler and to hope that someday someone implements a popular web framework on top of TeaVM.

I managed to create a nice and fully functional web application with TeaVM. Compiling from Java to JavaScript works great! For the graphics I manipulated the DOM directly from Java.
It is not clear to me what the WebAssembly compilation and especially the C compilation are for. Could you please give me an explanation?

It is not clear to me what the WebAssembly compiling and especially the C compiling are for. Could you please give me an explanation?

It means literally: compile Java bytecode to WebAssembly and C. As for C I need some explanation. It can be used as a ultra-lightweight subset of GraalVM Native Image. The goal is to support platforms where it's hard to get into with LLVM. One may say that LLVM is supported everywhere, but it's not. It was for one project that we wanted to launch as WinRT/UWP application, and nobody could either patch OpenJDK to run as a WinRT app or to make RoboVM run under WinRT (and GraalVM Native Image was too fresh and unstable then). It turned out that for me it was easier to create C BE for TeaVM (especially, when there was WebAssembly BE that already implemented 99% of runtime magic, including GC) rather that for guys who tried alternative approaches. We managed to successfully compile our app (500KLOC of Java code) as a UWP app, but then the project was cancelled due to non-technical reasons. But C backend for TeaVM is still there and usable, because there was just no reason to drop it. This example, in addition to JS and WebAssembly can also target Linux (GTK)

Thank you for your explanation. 500KLOC of Java code... wow!


Basic example issue: Cannot write to a WebSocket in the CLOSING state

I'm running the basic example from here: https://websockets.readthedocs.io/en/stable/intro.html
When I run the client program, about 30% of the time I get an error (after successfully printing the greeting from the server):
> Brian
< Hello Brian!
Traceback (most recent call last):
  File "test_websockets_client.py", line 12, in <module>
    asyncio.get_event_loop().run_until_complete(hello())
  File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/asyncio/base_events.py", line 467, in run_until_complete
    return future.result()
  File "test_websockets_client.py", line 10, in hello
    print('< {}'.format(greeting))
  File "/Users/brianwong/evex-python2/websockets/client.py", line 390, in __aexit__
    yield from self.ws_client.close()
  File "/Users/brianwong/evex-python2/websockets/protocol.py", line 370, in close
    self.timeout, loop=self.loop)
  File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/asyncio/tasks.py", line 358, in wait_for
    return fut.result()
  File "/Users/brianwong/evex-python2/websockets/protocol.py", line 642, in write_frame
    "in the {} state".format(self.state.name))
websockets.exceptions.InvalidState: Cannot write to a WebSocket in the CLOSING state

All help very much appreciated!

Reply is a little late, but better now than never.
The code breaks on the await command:
 await websocket.send(greeting)     print("> {}".format(greeting))
Which Python version do you use to start the program? It looks like it is a python2 version. Is the server running at the same time?

@feridM it says python3.6 in the directories mentioned
It doesn't break on await send, that has already finished (the context manager is exiting)
The error message shows that the connection state is CLOSING
write_frame(OP_CLOSE, data) is the only thing setting CLOSING as the state
write_frame complains that state is already CLOSING
Therefore, the problem is that write_frame(OP_CLOSE, data) gets called twice, or that it doesn't handle getting called twice

Looks like I got my invariants wrong at some point :-(
async is hard, folks.

I'm not managing to reproduce this problem :-/
@brianblakewong Could you try adding this at the beginning of the client.py and server.py scripts, reproduce the error, and paste the output here?
import logging
logging.basicConfig(level=logging.DEBUG)

Thanks!

To clarify my earlier comment about invariants: websockets is supposed to write a CLOSE frame only after checking that the connection state is OPEN and changing it to CLOSING, without yielding in the meantime. write_frame contains an assertion to enforce this.
The issue here is that write_frame runs after the state has changed to CLOSING. Based on the stack trace, I believe we're talking about this call to write_frame:
https://github.com/aaugustin/websockets/blob/9b0929582874cab3b3d18e283a841c43fd198eaf/websockets/protocol.py#L377-L390
Reading the implementation of wait_for in Python 3.6, I don't see how it could yield to the event loop before executing its first argument. I'm not seeing what else could explain the problem we're seeing.
Could you try applying this change and see it if makes the problem go away? That would help narrowing down the cause.
diff --git a/websockets/protocol.py b/websockets/protocol.py
index 541aa75..d6bcd01 100644
--- a/websockets/protocol.py
+++ b/websockets/protocol.py
@@ -378,16 +378,7 @@ class WebSocketCommonProtocol(asyncio.StreamReaderProtocol):
             # 7.1.2. Start the WebSocket Closing Handshake
             # 7.1.3. The WebSocket Closing Handshake is Started
             frame_data = serialize_close(code, reason)
-            try:
-                yield from asyncio.wait_for(
-                    self.write_frame(OP_CLOSE, frame_data),
-                    self.timeout, loop=self.loop)
-            except asyncio.TimeoutError:
-                # If the close frame cannot be sent because the send buffers
-                # are full, the closing handshake won't complete anyway.
-                # Cancel the data transfer task to shut down faster.
-                # Cancelling a task is idempotent.
-                self.transfer_data_task.cancel()
+            yield from self.write_frame(OP_CLOSE, frame_data)

         # If no close frame is received within the timeout, wait_for() cancels
         # the data transfer task and raises TimeoutError. Then transfer_data()

Doesn't matter if it protects from interference from others, it is the interference
..right? It's the other call to write_frame(OP_CLOSE) that has yielded while in closing state (which presumably comes receiving CLOSE from the server)
(also, should it really be blocking?)
I had the same issue. Once, the first time I ran the example. Couldn't and can't reproduce.
I barely know what I'm saying here. I don't know websockets or asyncio. Just sharing what I do see for whatever that is worth.

@aaugustin I can repro this issue almost 100% of the time when I alter the client code to run 10 tasks on the event loop sending a name to the server.
Applying your diff fixes the issue.

Thank you very much Anthony, I can reproduce the error with that script.

Fun fact: activating DEBUG logs to diagnose the issue makes it go away...
However, with a few print statements, I see the following scenario:

hello exits the async with websockets.connect block, which calls close
close enters yield from asyncio.wait_for(self.write_frame(OP_CLOSE, frame_data), ...) and yields control to the event loop before calling write_frame (which I didn't expect)
transfer_data_task, which is executing read_data_frame, receives a close frame from the server, calls yield from self.write_frame(OP_CLOSE, frame.data), which completes successfully
the task started by asyncio.wait_for at step 2 resumes executing; at this point the state has changed to CLOSING; this results in the exception reported here.

So the issue is that close yields control to the event loope between if self.state is State.OPEN and self.write_frame(OP_CLOSE, frame_data), making it possible for two coroutins to enter self.write_frame(OP_CLOSE, frame_data) simultaneously.

I confirmed manually that the error no longer happens with Anthony's script with the changes in that PR.


Option for auto/max ranging

For power submissions, we first perform a ranging run to determine the maximum current range, and then a test run with exactly the same parameters with the power meter set to that range.
For v1.0, we performed the ranging run under the Auto settings. It worked well across all kinds of system from Edge to Datacenter. For v1.1, we initially switched to perform ranging under the Max range (e.g. 20 A), but had to roll that back because it caused issues for low power systems.
For v2.0, we would like to have an option for the ranging mode, defaulting to Auto.

@psyhtest Is there any advantage of using the Max mode as compared to the auto mode for ranging? Just trying to understand the reason for changing to Max mode from Auto mode.


Merge release/3.x branch to master

This PR is a part of the Release. I follow the instruction step 3. This PR marge release 3.x branch to master.  This is a part of 3.0.15277 release process.
Since there was 3 commit ahead master on the release/3.x branch. However, these change is already reside on the master.
Only the difference between master and release/3.x is adding release/3.x branch as Ci trigger.
I'm not sure if it is needed for master branch or not.
The original HotFix and Cherry Pick was, the Functions Host version (it will be updated this time) and Extension Bundle
version. It was done by @divyagandhii .
PR information

[x] The title of the PR is clear and informative.
[ ] There are a small number of commits, each of which has an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
[ ] If applicable, the PR references the bug/issue that it fixes in the description.
[ ] New Unit tests were added for the changes made and CI is passing.

Add @pragnagopa  for tracking progress

Add @pragnagopa  for tracking progress

@divyagandhii
For the release/2.x branch, I rebased it with master and nothing different with master.
So that We don't need release/2.x merge this time.

@divyagandhii
For the release/2.x branch, I rebased it with master and nothing different with master.
So that We don't need release/2.x merge this time.


[BUG] Previous ECM is gone when scramble other service.

Bug description:
[BUG] Previous ECM is gone when scramble other service.

How to reproduce:

Scramble one service with fixed CW
Insert ECM for the service using inject plugin
Scrambler another different service from the same TS file
Then the ECM for the first scrambled service is gone in the final TS file.

I use the following script to perform the above actions:
tsp -v -I file tnt-uhf25-506MHz-2019-01-22.ts -P scrambler 513 --dvb-csa2 --cw-file cw-dvb-csa2.txt -O file tnt1.ts.scr

tsanalyze --pid-list  tnt1.ts.scr
0 1 16 17 18 20 21 110 120 130 131 132 140 141 170 310 320 330 340 410 420 430 440 470 510 520 530 531 540 541 570 610 620 630 631 632 640 641<PHONE_NUMBER>

tsp -I file tnt1.ts.scr  -P inject --binary tools/ecm_sec_csa2.bin --pid 790 --inter-packet 10 --stuffing -P pmt --add-ca-descriptor 57069/790 --service 513 -O file tnt1.ts.scr.ecm

tsanalyze --pid-list tnt1.ts.scr.ecm
0 1 16 17 18 20 21 110 120 130 131 132 140 141 170 310 320 330 340 410 420 430 440 470 510 520 530 531 540 541 570 610 620 630 631 632 640 641 670<PHONE_NUMBER>

tsp -v -I file tnt1.ts.scr.ecm   -P scrambler 515 --dvb-csa2 --cw-file cw-dvb-csa2.txt  -O file tnt1.ts.scr.ecm.scr
tsanalyze --pid-list tnt1.ts.scr.ecm.scr
0 1 16 17 18 20 21 110 120 130 131 132 140 141 170 310 320 330 340 410 420 430 440 470 510 520 530 531 540 541 570 610 620 630 631 632 640 641<PHONE_NUMBER>

For output of tsanalyze in last step, the ECM with PID 790 get lost from the last TS file.
I am not sure if I miss something.  I don't why the original ECM get removed.
Looking forward to your reply! Thanks

Expected behavior:

Errors and logs:

[be sure to surround verbatim log lines with "~~~" lines]

Environment:

OS:
OS version:
TSDuck full version:
Installation type:

Additional information:

Hi @sichunqin
This is the classical problem of the lack of free space (stuffing) when trying to insert something, here the ECM.
Because of the file name, I assume here that the input stream you use for your tests was downloaded from the TSDuck stream repository, in the French terrestrial section.
First point: If you analyze that stream, you will see that there is no stuffing at all.
Note: All broadcast streams have some stuffing because the TS bitrate is fixed by the modulation parameters and the sum of all ES is never exactly that precise bitrate. However, the DVB-T tuner I used for capturing that stream has the very bad idea of dropping all null packets. It can make sense to watch TV on the computer. But it is very inconvenient for analysis. Anyway, the result is a TS file without any stuffing, no PID 8191 at all.
The second point to understand is how the scrambler plugin works when specifying a service (i.e. not a list of PID's on the command line). Scrambling a service means that no packet from that service shall remain in the clear. However, the precise list of PID's of the service is unknown until we get a PAT and then the PMT of the service to scramble. To avoid letting in the clear potential packets from the service to scramble, the scrambler plugin nullifies all TS packets before the PMT of the service. As a result, all packets at the beginning of the file are null packets (except global PID's such as PAT, CAT, etc. which cannot be part of the service to scramble).
Knowing these two points, what happens is the following scenario:

File tnt-uhf25-506MHz-2019-01-22.ts contains no stuffing at all. If you had tried tsanalyze --pid-list on it, you would have seen that PID 8191 was not present.
After scrambling service 513, most packets at the beginning of tnt1.ts.scr are null packets. If you analyze this file, you will see that the first packet which is not null or a global PID is precisely the 513 PMT. This is the point where the scrambler plugin exactly knows what to scramble and what to pass. So, tnt1.ts.scr now has some stuffing, some free space, but only at the beginning of the file, before the first 513 PMT.
In file tnt1.ts.scr.ecm, the ECM were inserted where there is some free space, meaning only at the beginning of the file. If you analyze the file, you will see that the ECM PID disappears after the first 513 PMT. Because there was no free space after that PMT. By the way, this also means that the ECM PID is unusable by receivers since the ECM PID disappears at the exact point where it becomes known as an ECM PID.
During scrambling of the second service, the same initial nullification method applies. All packets before the PMT of service 515 are nullified. However, because the first scrambling operation erased everything, including the 515 PMT, before the 513 PMT, the first 515 PMT is now after the first 513 PMT. This means that the nullification process erases all ECM in PID 790 (because they are all before the 513 PMT).

Therefore, PID 790 was completely erased from file tnt1.ts.scr.ecm.scr.
Rule of thumb: When you insert something in a stream, ALWAYS make sure that you have enough free space (stuffing) in that stream.
To avoid this, make sure to have some free space in the initial input file, for instance using option --add-input-stuffing in the first tsp command.
For more details, please carefully read the documentation of tsp in the TSDuck user's guide.

@lelegard Thanks a lot for your great explanation! It really help!


imageUrl and imageBase64 (thumb) in json format

Hi,
How to get imageUrl and imageBase64 (thumb) in json format ?
I see it exist in xml, but not in json, any reason ?
Best
Roman

hello i will try to put the code for the imageUrl here when i have it slected cuz like its somewhere in my code but it does work in Json
also if you run your project on a remote cloud host plz let me know how you did it cuz i cant get it to run on a live remote cloud ubuntu server
Lisa


FIX(dashboard): Fixes #167: AAM uses node type equals IAAS or equals PAAS

If the user selects IaaS or PaaS for a module, the matchmaker is not passing any suitable offering to the optimizer. This PR fixes this ( #167 )
@adriannieto : Could you review this?

Looks good to merge, as we got no feedback on #167 about the naming issue we can discuss this during the Integration Meeting.

Merging. Closes #167
@adriannieto : That naming issue has nothing to do with neither this PR nor the issue.


python module fatal install error

I can't install fatal when trying to run the source
ERROR: Could not find a version that satisfies the requirement fatal (from versions: none)
ERROR: No matching distribution found for fatal

This has been addressed. Please download the latest version of UVR.
Link:
https://github.com/Anjok07/ultimatevocalremovergui#installation


Query/network processing begins too soon and gets unwanted intermediate results.

PCViz query/network processing begins too early - as user adds gene symbols.
This no good. Often, this is actually waste of resources and user's patience.
For example, I am going to use three gene names, and want to add them one by one (perhaps, I'd like to double-check the third gene symbol and need some time, or got distracted, etc...).
I do NOT want to see (and wait for) the network after I typed in the first or second gene name; this is wasting of time and resources. I only want to see the network after all the three genes added.
So, there either should be a button to press, or a reasonable interval (e.g., 10 sec) of user inactivity (in the input field), or loss of focus before the request is sent to the servers and network starts to build.
Attn.: @armish @onursumer

Igor, we do have a timeout of 5 seconds; but, if feels too short, happy to bump it to ~10 seconds. I don't like the idea of having a submit button as it clutters the supposedly minimal UI, but also don't have any strong opinions against having it there as long as we tweak the design to accommodate that.
This is one of those we-need-to-survey-users-to-find-the-right-settings features.

Increasing the delay (see the changeset) did not work; need to fix somewhere else... We probably want a push button there to submit a new user query. But if the URL (HTTP GET request) contains a list of IDs, such as /pcviz/#neighborhood/MDM2, then it should run the query and start building a network right away.

Igor, this is my bad. Apparently I pointed the wrong the timeout event to you. The correct timer is this one: https://github.com/PathwayCommons/pcviz/blob/master/src/main/webapp/js/components/pcviz.home.js#L48 (in pcviz.home.js, see the waitTime variable). Bumping this further up should do the trick.


Scroll bar not visible

It seems like it's impossible to show a scroll bar when using the library. Can you confirm?

Just tested our sample now by setting:
<android.support.v7.widget.RecyclerView
        android:id="@+id/recyclerview"
        android:layout_width="match_parent"
        android:layout_height="match_parent"
        android:scrollbars="vertical"/>

and could see the scrollbars, this library shouldn't affect anything with the RecyclerView display (all it does is abstract the idea of parents and children at the adapter level).
Good luck!

Yeah, I thought it was rather weird that the library would have any effect on this. I've already tried using the android:scrollbars="vertical" attribute, but to no luck. Oh well, thanks for responding!

If you can get an example recreating the issue I wouldn't mind taking a peek, who knows maybe it is something wrong with the lib strangely. Maybe it's a device issue, does it also not show on the emulator? And just to be clear I'm only seeing the scrollbar when the user scrolls, by default they hide when it is stable.


Infinite recursion loop

Hi all! First off, thank you for maintaining dag-cbor. It's great!
I came across an encoded DAG-CBOR object that makes dag-cbor recurse infinitely, or at least deeper than Python's default max recursion depth. Here it is, base64-encoded: bad.b64.txt
Here's the stack trace snippet:
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/Users/ryan/src/bridgy-fed/local/lib/python3.11/site-packages/dag_cbor/decoding/__init__.py", line 127, in decode
    data, _ = _decode_item(stream, options)
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/ryan/src/bridgy-fed/local/lib/python3.11/site-packages/dag_cbor/decoding/__init__.py", line 149, in _decode_item
    value, num_bytes_further_read = _decoders[major_type](stream, arg, options)
                                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/ryan/src/bridgy-fed/local/lib/python3.11/site-packages/dag_cbor/decoding/__init__.py", line 272, in _decode_dict
    v, _ = _decode_item(stream, options)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/ryan/src/bridgy-fed/local/lib/python3.11/site-packages/dag_cbor/decoding/__init__.py", line 149, in _decode_item
    value, num_bytes_further_read = _decoders[major_type](stream, arg, options)
                                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/ryan/src/bridgy-fed/local/lib/python3.11/site-packages/dag_cbor/decoding/__init__.py", line 231, in _decode_list
    item, _ = _decode_item(stream, options)
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/ryan/src/bridgy-fed/local/lib/python3.11/site-packages/dag_cbor/decoding/__init__.py", line 149, in _decode_item
    value, num_bytes_further_read = _decoders[major_type](stream, arg, options)
                                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/ryan/src/bridgy-fed/local/lib/python3.11/site-packages/dag_cbor/decoding/__init__.py", line 231, in _decode_list
    item, _ = _decode_item(stream, options)
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
...

You're not the only ones, whatever JS lib @ericvolp12 is using on atproto.tools has the same problem 😆: https://atproto.tools/records?did=did%3Aplc%3A4agp2hcrps6ou4vjv7uux7dm
Thanks in advance!

It's a recursion depth issue: the current implementation of encoding and decoding in this library is recursive: objects with hundreds of levels of nesting, like the object you linked, exhaust the available recursion depth (which is 1000) in my machine.
Fixing this will require a non-recursive re-design of the library: it was not an issue for us until now, but I guess we'll get it done at some point in the near future :)

Thanks! Totally makes sense. Not a high priority on our end, looks like this object was specifically crafted to push the boundaries, not representative of the kinds of objects we usually see.


Updated Norwegian translation

🤖 Generated by Copilot at b2e8ef0
This pull request improves the Norwegian localization of Ghost by updating, translating, and adding missing strings for various core features and components, such as ghost.json, comments.json, portal.json, and signup-form.json. This will enhance the user experience and accessibility of Ghost for Norwegian speakers.

Hey @fyksen - we've just merged a bunch of Norwegian translations here: https://github.com/TryGhost/Ghost/pull/18744, so this PR conflicts. Please open a new PR if you'd like to make some alterations 🙂


about view one instance app  logs real time

marathon-python have view one instance app  logs real time？OR mesos-api？thanks

Neither APIs have such functionality alone. You will have to combine the two.

OK，thank you


We should not attempt to resolve Move events struct in the Gateway

When we are constructing transaction effect response, we also try to resolve the Move struct of all the events in the effects, from here: https://github.com/MystenLabs/sui/blob/main/crates/sui-core/src/gateway_state.rs#L1048
This is not going to work.
The gateway is not guaranteed to contain the package/module that defined the event struct, and it may fail to obtain the Move struct for every event.
We are also probably over-complicate things here: does the transaction caller really need to see the Move fields of every event in the effects? If they need to do so, they should resolve it on the client by querying the fullnode, not on the gateway.

The gateway is not guaranteed to contain the package/module that defined the event struct ...

When we create a move call transaction in gateway (create_move_call_transaction_kind), we assume the gateway knows about the package/module of the move function and we use the package object to resolve the move call args resolve_move_function_args. My thought is if the gateway can create the move call transaction, it should have the package object to resolve the event object as well? Or is this a wrong assumption...?

The gateway only assures to know the package it's calling. But if the event struct is not defined in this package, but in a dependent package, there is no guarantee that the gateway will have it.


Broken matplotlib demos

Errors can be seen here:
https://aeturrell.github.io/coding-for-economists/vis-intro.html#categorical-data

IndexError: index 0 is out of bounds for axis 0 with size 0

Many thanks for flagging this!


[FR] Add option to exclude a specific zone from more general stub- or forward-zone declarations

Current behavior
Currently you can define forward-zones (or stub-zones, but the difference shouldn't be relevant for my example) as follows:
forward-zone:
  name: example.com
  forward-host: ns1.example.com

Now let's say, there's a subdomain foo.example.com that you don't want to to forward to ns1.example.com but instead you want queries for that domain to be resolved recursively by looking up the corresponding NS records and asking those name servers. Currently there is no way to achieve this. You could override the behavior for foo.example.com with another forward- or stub-zone but there is no way to revert the behavior back to recursive queries.
Describe the desired feature
I imagine this could be solved by introducing a new zone declaration recursive-zone, that could be used as follows:
recursive-zone:
  name: foo.example.com

If this zone is configured together with the forward-zone declared above, it would result in queries for bar.example.com to be forwarded to ns1.example.com while a request for blub.foo.example.com would result in a regular recursive lookup.
There's a similar feature in bind, where you can undo the effect of a more general forward zone like this
zone "example.com" {
  type forward;
  forwarders { ns1.weltraumschlangen.de; };
};

zone "foo.example.com" {
  type forward;
  forward {};
};

The corresponding documentation for this reads as follows:

If no forwarders statement is present, or an empty list for forwarders is given, then no forwarding is done for the domain, canceling the effects of any forwarders in the options statement.

Implementing this in a similar way to how bind does it seems reasonable to me.
Potential use-case
This type of configuration seems mostly useful, when your ISP provides a recursive resolver for you, that you can forward your regular queries to. In those cases I would specify the ISP's name recursive resolvers like this:
forward-zone:
  name: .
  forward-addr: <The ISP's name server>

But in the past I've come upon multiple reasons to circumvent this general forwarding for specific domains. One example is the domain spamhaus.org, which applies rate limiting per client, which means the shared ISP's resolver might be over the rate limit, while querying from your own resolver would succeed.
Another example would be that some forwarders might do strange manipulations on certain domains.


feat(koa): Skip update HTTP's span name and update RpcMetadata's route instead

Which problem is this PR solving?
Each framework has a different approach to updating Span's name and HTTP_ROUTE attribute. We want to delegate this to instrumentation-http for consistent's name and attribute
This PR fixes the above issue for koa when integrate with @koa/router as koa are not support routing natively.

This will partially fix issue #1381

Short description of the changes

Skip modifying HTTP's Span name directly in instrumentation-koa code
Update route property of RpcMetadata

can we merge this or add pkg:instrumentation-koa label so we can test tav for this?

This one is ready to merge, but the build seems to have an issue

lerna ERR! lifecycle "prepare" errored in "@opentelemetry/instrumentation-koa", exiting 1

Can you please take a look?

My bad, forgot to remove unused import.


interface sketch

Changing this up:

start
stop
line

Slices a line between a start and stop point

done


Added implementation files folder (src), added figures.dart file wher…

…e export all figures

Not approved


ESP is not responding when I ping

I did all the steps but the device is not responding.
Pinging <IP_ADDRESS> with 32 bytes of data:
Reply from <IP_ADDRESS>: Destination host unreachable.
Reply from <IP_ADDRESS>: Destination host unreachable.
Reply from <IP_ADDRESS>: Destination host unreachable.
Reply from <IP_ADDRESS>: Destination host unreachable.
Ping statistics for <IP_ADDRESS>:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

also the is esp is doing this after it's done installing sketch
esptool.py v2.8
Serial port COM3
Connecting....
Chip is ESP8266EX
Features: WiFi
Crystal is 26MHz
MAC: a4:cf:12:dd:5d:42
Uploading stub...
Running stub...
Stub running...
Changing baud rate to 460800
Changed.
Configuring flash size...
Auto-detected Flash size: 4MB
Compressed 320400 bytes to 231688...
Writing at 0x00000000... (6 %)
Writing at 0x00004000... (13 %)
Writing at 0x00008000... (20 %)
Writing at 0x0000c000... (26 %)
Writing at 0x00010000... (33 %)
Writing at 0x00014000... (40 %)
Writing at 0x00018000... (46 %)
Writing at 0x0001c000... (53 %)
Writing at 0x00020000... (60 %)
Writing at 0x00024000... (66 %)
Writing at 0x00028000... (73 %)
Writing at 0x0002c000... (80 %)
Writing at 0x00030000... (86 %)
Writing at 0x00034000... (93 %)
Writing at 0x00038000... (100 %)
Wrote 320400 bytes (231688 compressed) at 0x00000000 in 5.7 seconds (effective 448.1 kbit/s)...
Hash of data verified.
Leaving...
Hard resetting via RTS pin...


Horizontal scrollbar on long warning is not moving

On a node with a long warning, open the warning visualization and try to scroll to the right/left. The scrollbar stays in the same place and only the cursor moves. I am uncertain whether this is on purpose or not, but it feels weird.
Screencast from 2023-06-08 18-08-08.webm

It's of course not on purpose :)

After merging #6981 it's not reproducible.


Clicking on the Windows notification for "an update to PowerToys is available" does nothing

Microsoft PowerToys version
0.74.0
Installation method
Other (please specify in "Steps to Reproduce")
Running as admin
No
Area(s) with issue?
General
Steps to reproduce
Wait for the notification to appear, then click it.
✔ Expected Behavior
The app to open.
❌ Actual Behavior
Nothing happens.
Other Software
No response

Here's a video of the observed bug
https://github.com/microsoft/PowerToys/assets/444722/8703c426-2bc1-4031-8cb2-d7a00eff5401

I'm seeing the same thing on my Windows 11 system. Is there any logs or anything that I can dig up to provide more context? Or this is reproducible on all Win11 machines?


Remove Alertmanager API v1

Alertmanager API v2 is available since v0.16.0 and it's probably fair to say that it's (at least) feature-equivalent to the API v1 since v0.19.0. At the time when v0.16.0 was released, the CHANGELOG stated that v1 would be removed in v0.18.0. Obviously it hasn't happened yet and this issue is to discuss if/when it should happen.
cc @roidelapluie @beorn7
xref https://github.com/prometheus/prometheus/issues/8398

Good to know that the API v1 removal had been announced long ago.
Yes, it would be great to retire v1 as soon as reasonably possible. It's existence caused us a lot of headache when adding new features.

Good to know that the API v1 removal had been announced long ago.
Yes, it would be great to retire v1 as soon as reasonably possible. It's existence caused us a lot of headache when adding new features.

Also, let's remember to remove any json tags and json marshalling code that are not needed anymore after the removal (if that applies to any).

Also, let's remember to remove any json tags and json marshalling code that are not needed anymore after the removal (if that applies to any).

I'll be happy to take care of this.

Great. Just note that we should coordinate this with https://github.com/prometheus/prometheus/issues/8398 , i.e. ideally we only remove the v1 API once Prometheus defaults to the v2 API to avoid friction.

Consensus was reached during the Alertmanger Working Group that we'll proceed with this but keep the api/v1/alerts endpoint as a redirect to the api/v2/alerts endpoint.


remove deprecated method call from_ir

@benhoff
Hi, thanks for PR.
Do you happen to know what is the first OpenVINO version which support this API? Probably we should update README.md file with it.

https://github.com/opencv/dldt/blame/ba6e22b1b5ee4cbefcc30e8d9493cddb0bb3dfdf/inference-engine/ie_bridges/python/src/openvino/inference_engine/ie_api.pyx#L485

Looks like R5 from 2018

@benhoff
Ok, thanks.

@benhoff , thanks for the contribution. Please give us some time to check the patch. Even it is obvious I would prefer to send some time to test it. I will merge it this week for sure.


Update YouVersion Bible Suggest extension to latest (v3.5.0)

Description
Resolves #12963
Screencast
#2951
Checklist

[X] I read the extension guidelines
[X] I read the documentation about publishing
[X] I ran npm run build and tested this distribution build in Raycast
[X] I checked that files in the assets folder are used by the extension itself
[X] I checked that assets used by the README are placed outside of the metadata folder

@pernielsentikaer The bulk of the changes are in the update to my youversion-suggest dependency (seen in the package.json). The changes in that dependency consist of strictly the new language support requested by https://github.com/raycast/extensions/issues/12963.


TSM1 reader accessor struct: ensure 64bit alignment

use pointers to allocated uin64 values instead field values
fixes "panic: unaligned 64-bit atomic operation" with Golang v1.20

If compiling with go 1.20, influxd crashed after some time:
panic: unaligned 64-bit atomic operation

goroutine 23 [running]:
runtime/internal/atomic.panicUnaligned()
    /usr/lib/go-1.20/src/runtime/internal/atomic/unaligned.go:8 +0x24
runtime/internal/atomic.Xadd64(0x30bad54, 0x1)
    /usr/lib/go-1.20/src/runtime/internal/atomic/atomic_arm.s:258 +0x14
github.com/influxdata/influxdb/tsdb/engine/tsm1.(*accessor).incAccess(...)
    /go/github.com/simonvetter/influxdb/tsdb/engine/tsm1/reader.go:1497

This error didn't occur with golang 1.16.
Golang 1.19 brought own atomic.Uint64 types ensuring correct alignment, but this would break compiling using older go releases. Hence this fix via pointers.
Notes regarding alignment for atomic functions:
https://pkg.go.dev/sync/atomic#pkg-notes


Update environment.yml

Short description of the changes:

Long description of the changes:

Check list for the pull request

[ ] I have read the [CONTRIBUTING]
[ ] I have read the [CODE_OF_CONDUCT]
[ ] I have added tests for my changes
[ ] I have updated the documentation accordingly

Check list for the reviewer

[ ] I have read the [CONTRIBUTING]
[ ] I have verified the proposed changes
[ ] best software practices

[ ] all internal functions have an underbar, as is python standard
[ ] clearly named variables (better to be verbose in variable names)
[ ] code comments explaining the intent of code blocks

[ ] All the tests are passing
[ ] The documentation is up to date
[ ] code comments added when explaining intent

Manual test for the reviewer

References

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 76.26%. Comparing base (8c5e8ed) to head (1fcd77c).

Additional details and impacted files
@@           Coverage Diff           @@
##             next     #160   +/-   ##
=======================================
  Coverage   76.26%   76.26%
=======================================
  Files          23       23
  Lines        1403     1403
=======================================
  Hits         1070     1070
  Misses        333      333

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Performance audit

Three queries that need to be improved:

SELECT COUNT(*) FROM visits where animal_id = 4;
Before optimization:

After optimization:

SELECT * FROM visits where vet_id = 2;
Before optimization

After optimization

SELECT * FROM owners where email =<EMAIL_ADDRESS>Before optimization

After optimization

Thank you @binhussen for taking your time to review our PR 😀


The operation couldn’t be completed. (OSStatus error -10814.)

If you are filing a bug report, please include information for the topics below. Also, please make sure to only report one bug/feature request/question per issue.
Description
I am getting The operation couldn’t be completed. (OSStatus error -10814.) upon trying to login. I suspect the setup around URI is wrong. It fails with web browser and iOS app.
Versions
iOS SDK version: 0.1.6
Spotify app version (if native SSO flow is involved): <IP_ADDRESS>2
Severity
Trivial
Steps to Reproduce

Add URI to Spotify dev dashboard myappmedia:// and myappmedia://callback
Setup the URI Types in Xcode project with URL Schemes: myappmedia
Add the following code to AppDelegate.swift:

func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?) -> Bool {
        SpotifyLogin.shared.configure(clientID: "aaa123", clientSecret: "bbb123", redirectURL: URL(string: "myappmedia://callback")! )
        return true
    }

, where "aaa123" and "bbb123" are real clientID and clientSecret respectively.

Build and run, try to sign in with Facebook login
Web page with the scope of permissions is presented
Press AGREE

Actual behaviour
Get The operation couldn’t be completed. (OSStatus error -10814.) error after pressing Sign In button, and them after pressing AGREE nothing happens.
Expected behaviour
Successful sign in
Logs
2020-07-21 23:11:59.790846-0700 MyApp-iOS[70870:5832280] -canOpenURL: failed for URL: "spotify-action://authorize?utm_campaign=spotifylogin&show_dialog=true&nosignup=true&utm_medium=spotifylogin&scope=playlist-read-private%20playlist-read-collaborative%20playlist-modify-public%20playlist-modify-private&redirect_uri=myappmedia%3A%2F%2Fcallback&response_type=code&client_id= aaa123&nolinks=true&utm_source=spotify-sdk" - error: "The operation couldn’t be completed. (OSStatus error -10814.)"

Please try to add the key LSApplicationQueriesSchemes to your info.plist with following values: spotify, spotify-action, myappmedia.

I am experiencing the same issue. Would appreciate any advice on how to fix this.

I am experiencing the same issue. Would appreciate any advice on how to fix this.


luarocks install luarocks fails on windows using vs 2013

Hi,
When i try updating luarocks installation, it fails with a weird error from nmake:
c:\Prog\mypackage\2.2>luarocks.bat install luarocks
Installing https://luarocks.org/luarocks-2.2.2-1.src.rock...
Using https://luarocks.org/luarocks-2.2.2-1.src.rock... switching to 'build' mode
Warning: variable CFLAGS was not passed in build_variables

Microsoft (R) Program Maintenance Utility Version 11.00.60610.1
Copyright (C) Microsoft Corporation. Tous droits réservés.

Makefile.setup.inc(2) : fatal error U1036: erreur de syntaxe : noms trop nombreux à gauche de '='
Stop.

Error: Build error: Failed installing.

Could somebody help me understanding what is the problem ?

LuaRocks cannot update itself on Windows. You have to download and install the new version on top of the old one.


Undefined method say_status for Builder

I am trying to port some extensions for MMv4. They often call builder.say_status on a after_build hook, which is no longer defined.
I see that in e.g. gzip extension, builder.say_status has been replaced by builder.trigger.
Should I do the same (no caveats)?
Thank you!

The change is basically this. after_build used to return an instance of the Thor class which was building the site. Now, it returns an instance of Middleman::Builder which allows us to build sites directly in Ruby, without Thor. We still use Thor, but we've moved a lot of the diffing and file creation logic into Middleman.
There are two options now:

builder.thor.say_status: The Thor object is available as builder.thor, but it may not always be available. But it probably will for now, on normal middleman build commands.

builder.trigger :your_extension, "Your Message": Basically, trigger emits an event that other parts of the build process can listen to. If the build is running through the command line, it will output unknown event types as messages to the console. This is the best approach

Would love to figure out a good way to communicate this change to extension authors. Maybe a separate "Upgrading Extensions to v4" article on the site.


Unexpected error #12

2022-04-27T17:00:43.189029+00:00 app[worker.1]: [5] Retrying "upload.SaveBigFilePart" due to Telegram says: [500 RPC_CALL_FAIL] - Telegram is having internal problems. Please try again later (caused by "upload.SaveBigFilePart")
[…]
2022-04-27T17:01:23.936566+00:00 app[worker.1]: Telegram says: [500 RPC_CALL_FAIL] - Telegram is having internal problems. Please try again later (caused by "upload.SaveBigFilePart")

Just Telegram servers that were offline for 1min


Added resources for programming

Added Harvard CS50 course playlist
This is the most popular and recommended course for any Computer Science student who is just starting to code.

By submitting this pull request I confirm I've read and complied with the below requirements.
Failure to properly do so will just result in the pull request being closed and everyone's time wasted.

[ ] I have read the Contribution guidelines and made sure my pull request follows it, specifically the part about promotions and markdown format.
[ ] Any resources I am adding in this PR have been used by me and I can personally vouch for their quality.
[ ] This pull request has a descriptive title. For example, Add [Resource Name] or Add [Topic Name], not Added new entries or update.
[ ] I have double checked that I have only updated the minimum files that are required by this PR.

@PragatiVerma18 Really sorry for so many commits, but I've done the required changes. Kindly review


Accessing Sinatra settings object from within a Job

Forgive me if this is obvious; I'm new to Sinatra and Ruby in general. How, if at all, can I access the Sinatra settings object from within a Job? I wanted to have some config settings stored in YAML files, so I added a method to config.ru to read them in and add them to settings. From within config.ru, I can access them (e.g. settings.bamboo[:bamboo_host] but from within a Job file I get a NoMethodError when trying to access settings.bamboo. When I try to access settings.auth_token or settings.defaut_dashboard from my Job, it returns nil.
Here's what I'm doing to read in the config files (from within the configure block in config.ru).
Dir.glob('config/*.yml').each do |f|
  config_name = File.basename(f, '.*')
  raw_config = File.read(f)
  config = YAML.load(raw_config).symbolize_keys
  set config_name.to_sym, Proc.new { config }
end

Instead of renaming you can use @sjernigans code at the end of configre do and before add
ENV["JOB_PATH"] = 'dashing can you wait a sec before you load the jobs?'

at the top of your file


Issue building with VS 2015

VsBuildV1 started failing today when targeting Visual Studio 2015.  We are getting this warning in the logs:
##[warning]Please enter one of the versions 15.0, 16.0, 17.0
##[warning]Visual Studio version '14.0' not found. Falling back to version '16.0'.
Visual Studio 2015 is installed on our build agent.  This started happening on September 17, 2021.
This powershell was modified recently and appears to have remove any version below 15 from the tests:
azure-pipelines-tasks/Tasks/VSBuildV1/Tests/Get-VSPath-Use-VsWhere.ps1

@dorlandode This is a known issue, it should be fixed by VSBuildV1 with version 1.192.3. Deployment of this task version should be completed today.
As a temporary workaround, you can pin the previous task version in your YAML file like this:
- task<EMAIL_ADDRESS>

@dorlandode Deployment of VSBuildV1 of version 1.192.3 completed. Could you please recheck and confirm if everything is working for you now?

@dorlandode Let me close this item since the fixed task version has been deployed. Please let me know if the issue is still actual for you.


Add Why BIOS section

Can you please use a standard commit message like,
feat: add new whybios section
After that, you can make a new PR. Thank you


[release-2.6] Set cgo flag on PROMU to build dynamically linked binary

/retest

/override ci/prow/test
Overriding the test job to unblock the PR. The test is failing due to a webhook configuration in the test base. We will need more time to investigate this failure.


Added NSObject category to handle NSNull and EXTNil

Suppose we have this code:
NSArray<UIViewController *> *horizontalViewControllers = @[
    self.trendsViewController ?: [NSNull null],
    self.trendGroupsViewController,
    self.searchViewController,
    self.bookmarksViewController ?: [NSNull null],
];

we need to return VC or nil by its index, like this:
UIViewController *controller = horizontalViewControllers[index];
if (controller != (id)[NSNull null]) {
    return controller;
}
return nil;

But I wanna be able to just do this:
return [horizontalViewControllers[index] selfOrNil];

@jspahrsummers this is tiniest feature for your lib. Can you looks at it soon? :)

Wow! Wow! Wow! I've just found amazing solution on EXTNil. I'll send you new PR in a few minutes!

Sorry, but I like to avoid adding NSObject categories in this project (as much as possible), as they pollute the class for all consumers—including other libraries.


Update opam

Update paths to mirage user, package name
Fix remove (ocaml/opam-repository#3921)

mirage-www/TROVE also needs an update

On 14 Apr 2015, at 09:28, Magnus Skjegstad<EMAIL_ADDRESS>wrote:
Merged #3 https://github.com/mirage/mirage-bootvar-xen/pull/3.
—
Reply to this email directly or view it on GitHub https://github.com/mirage/mirage-bootvar-xen/pull/3#event-280599425.


fix(ground_segmentation): missing classified points bug

Description
This fixed the bug that some points cloud closed to vehicle were not classified as GROUND or NON_GROUND points.
Related links
TIER IV INTERNAL LINK
Tests performed

Not applicable.
Effects on system behavior

Not applicable.
Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[ ] I've confirmed the contribution guidelines.
[ ] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

@badai-nguyen
I checked with sample rosbag, it appears that many false positives were detected after this PR.
before
after

I need to evaluate on different products or reconsider the solution for this issue so I will close this PR.


Guidance on updating owned entities

After upgrading to EF Core 3.0, I can't update properties on an owned entity.
Steps to reproduce
Start with this sample app that uses EF Core 2.2.6:
<Project Sdk="Microsoft.NET.Sdk">

  <PropertyGroup>
    <OutputType>Exe</OutputType>
    <TargetFramework>netcoreapp3.0</TargetFramework>
  </PropertyGroup>

  <ItemGroup>
    <PackageReference Include="Microsoft.EntityFrameworkCore.SqlServer" Version="2.2.6" />
  </ItemGroup>

</Project>

using Microsoft.EntityFrameworkCore;
using System;
using System.Linq;

namespace ConsoleApp3
{
    public sealed class Entity
    {
        public int Id { get; set; }
        public UserAction Created { get; private set; } = new UserAction();
        public UserAction Updated { get; private set; } = new UserAction();
    }

    [Owned]
    public sealed class UserAction
    {
        public DateTime? TimeUtc { get; set; }
        public int? UserId { get; set; }
        public string UserEmail { get; set; }
    }

    public sealed class ApplicationDbContext : DbContext
    {
        protected override void OnConfiguring(DbContextOptionsBuilder optionsBuilder)
        {
            base.OnConfiguring(optionsBuilder);
            optionsBuilder.UseSqlServer("Server=(localdb)\\mssqllocaldb;Database=aspnet-WebApplication-6E483A89-BEE6-4A76-96CC-CEB276E5E112;Trusted_Connection=True;MultipleActiveResultSets=true");
        }

        public DbSet<Entity> Entities { get; set; }
    }

    public static class Program
    {
        public static void Main()
        {
            using (var context = new ApplicationDbContext())
            {
                context.Database.EnsureDeleted();
                context.Database.EnsureCreated();

                context.Entities.Add(new Entity { Created = { TimeUtc = DateTime.UtcNow } });
                context.SaveChanges();
            }

            using (var context = new ApplicationDbContext())
            {
                var entity = context.Entities.First();
                entity.Updated.TimeUtc = DateTime.UtcNow;
                context.Entities.Update(entity);
                context.SaveChanges();
            }
        }
    }
}

I always initialize UserAction properties in the class itself to make sure they're never null, even right after creating the entity.
After running this, as expected, Updated_TimeUtc will be set in the table row. But if I change the Microsoft.EntityFrameworkCore.SqlServer package version to 3.0.0 and run this again, Updated_TimeUtc will always be null. The call to SaveChanges doesn't execute any SQL. This bug is also present in 3.1.0-preview2.19525.5.
I can't find any workaround other than manually executing some SQL to update the row. I tried calling context.Update(entity.Updated) or setting context.Entry(entity.Updated).State = EntityState.Modified but they throw exceptions.
Further technical details
EF Core version: 3.0.0
Database provider: Microsoft.EntityFrameworkCore.SqlServer
Target framework: .NET Core 3.0
Operating system: Windows 10 Version 1903
IDE: Visual Studio 16.4.0 Preview 2.0

@AndriySvyryd @ajcvickers  Thanks for the info. I agree it seems like bad behavior that EF Core would silently replace an existing instance that the property was initialized to (although it seems even worse that it would silently ignore the property without throwing an exception).
Looking back, I can see how it wasn't the best idea to always initialize the property as opposed to letting EF Core do the work and to interfere with it like that. The problem I was trying to solve was to make sure that the properties are always initialized and prevent someone from accidentally forgetting to do so. When querying the owner entity from the database, this wasn't a problem because EF Core automatically included these (since they are owned entities), but I also wanted to make sure they were always initialized whenever I created a new owner entity.
I think the best solution would be if we could remove the setter of these properties altogether (an existing owned entity shouldn't ever be replaced with another instance after all) and put them in the constructor. That way, anyone creating the entity would have to provide the owned entities and so would EF Core. This shouldn't be a big problem since EF Core automatically includes them already, should it? Just inject them in the constructor.

I think the best solution would be if we could remove the setter of these properties altogether (an existing owned entity shouldn't ever be replaced with another instance after all - in fact I might easily do the wrong thing and set it to an owned entity of another owner and get an exception) and put them in the constructor.

@Neme12 That is tracked by https://github.com/aspnet/EntityFrameworkCore/issues/12078

@AndriySvyryd What about throwing an exception then if the navigation property isn't null?

@Neme12 We are considering doing that in https://github.com/aspnet/EntityFrameworkCore/issues/18007#issuecomment-541359058


Code samples Wrongly coloured

[Enter feedback here]
Please when you can adjust the colors for some lines of the code examples.
some comments and lines of code are wrongly coloured and make the code sample look like a little bit messy.
Example1:
// Modifying the caption of the field 'Address 2' -->This line should be green but it is not.
modify("Address 2") -->
Example2:
Error('Feet too small');--> 'Feet too small' should be dark red.
Thank you a lot for your documentation and have a nice day!.
Kind regards,

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

ID: cdda7e30-30d9-ac83-abf7-267a7f634c6d
Version Independent ID: 5bf5ce87-f59a-d2ae-10b3-05eda02406b5
Content: Page Extension Object - Business Central
Content Source: dev-itpro/developer/devenv-page-ext-object.md
Service: dynamics365-business-central
GitHub Login: @SusanneWindfeldPedersen
Microsoft Alias: solsen

Thanks for the feedback! We've fixed the article, so that the color-coding is correct. The update will be published soon.


Refactor the agent

This PR broadly refactors the agent to:

use kube Controller construct
take advantage of Server Side Apply
prepare for resource split and CDI+DRA
don't put everything under a util directory
use closer to kube upstream kube client
update proto definitions for device plugins
use kubelet pod resources monitoring interface rather than CRI to do slot reconciliation
Use CRD definition in Rust code to generate yaml file

While a strict refactor would not change anything user-facing, in order to facilitate some elements, the capacity is added to the Instance object, as well as the CDI fully qualified device name.
This Still WIP for now, as most of the unit tests were not ported to new architecture.
What this PR does / why we need it:
Special notes for your reviewer:
Sorry for the huge PR
If applicable:

[ ] this PR has an associated PR with documentation in akri-docs
[ ] this PR contains unit tests
[ ] added code adheres to standard Rust formatting (cargo fmt)
[ ] code builds properly (cargo build)
[ ] code is free of common mistakes (cargo clippy)
[ ] all Akri tests succeed (cargo test)
[ ] inline documentation builds (cargo doc)
[ ] all commits pass the DCO bot check by being signed off -- see the failing DCO check for instructions on how to retroactively sign commits

assuming that there are instances of files that are just existing code that has been moved (but otherwise functionally unchanged), it would be helpful if you could point those out so we don't waste time reviewing them :)

assuming that there are instances of files that are just existing code that has been moved (but otherwise functionally unchanged), it would be helpful if you could point those out so we don't waste time reviewing them :)

Some parts of files are code that just got moved, but most of it required rework (hence the fact I couldn't just copy/paste the unit tests)

/version minor


Add contributing.md

An adaptation of https://github.com/bbatsov/rubocop/blob/master/CONTRIBUTING.md should be added to make sure PRs conform to certain guidelines.

Closed by https://github.com/kittoframework/kitto/commit/0d690330dfb1d4fc4c03f007dddfbaaaeead1efa


Fix various typos in .cc and .md files

Fix various typos.

Test failures:
https://github.com/grpc/grpc/issues/17335

Thanks for the contribution!


fix code format (exclude pfto)

Changed pysen black and isort to enable.

sorry, can we solve the conflictS? I will run CI and merge after that!

Conflicts resolved. Please review again!

/test


Cannot verify an email

Describe the bug
I've added a new address<EMAIL_ADDRESS>and the mail with verification link doesn't come.
Expected behavior
Mail must arrive.
To Reproduce
Maybe send some test mail to this address from the mailserver that handles verification mails?
My Platform
I believe this may be because aikipooh.name is IPv6 only.
Additional context

Yes, the email to that domain has permanently bounced:

553 5.1.2 Unknown mail server. Could not find a mail server for aikipooh.name

We're sending email from Amazon SES which I imagine can handle most configurations of mail servers.
You might want to make sure your DNS is properly configured? 			IN	MX

;; ANSWER SECTION:
aikipooh.name.		1799	IN	MX	10 aikipooh.name.

;; Query time: 282 msec
;; SERVER: <IP_ADDRESS>#53(<IP_ADDRESS>)
;; WHEN: Sat Aug 04 08:05:28 CDT 2018
;; MSG SIZE  rcvd: 58

(Specifically I think the answer should resolve to an IP and not the same name)

Oh, amazon is retarded too:(
So there are no options for me to use IPv6, you won't migrate from SES so I understand?

@aikipooh we don't plan to migrate off of SES in this case, is IPv4 not an option for MX on your domain at all? Additionally please try to keep your comments within our Code of Conduct.

@ewdurbin Speaking about IPv4, it's not '80s, it's almost an end of a first quarter of 21 century out there.
What about the code of conduct?  They're not the only one at that, github cannot send to IPv6 too.

I am also unable to verify my email address so I am not able to upload my package


installing typescript is important :)

For the typescript to run properly, he need the package typescript ! The npm i command doesn't install it by default

Sorry, mine didn't install, but it should do so automatically. Don't merge this !

I'm a year late to this party but having just tried to install this recently myself I can confirm that it didn't automatically install for me either and I was pulling my hair out for a while wondering why attempting to build was inexplicitely failing

@Tomshiii I resolved this issue with https://github.com/sebinside/PremiereRemote/commit/8c8dcda75d3bd6e0d9d551f35b8bd0edba20a528. Now, typescript should be available to the build by simply calling npm i.


Fix issue 15941 -- rbtree no longer supports classes

Simple -- if type doesn't support formatting the range, then don't define toString. This means it defaults to Object.toString in those cases, but this isn't really a problem.
There are likely better ways to do this, but this fixes the regression now.
Need to see how docs get generated to find out if I did that part right.

ping @MartinNowak, can we get this in 2.071.1?

Interesting difference between ddox and ddoc here. I left the docs outside static if, and it seems to be fine for ddoc, but ddox has removed the toString documentation. ping @s-ludwig

I changed the docs so hopefully they work with ddox.

hopefully they work with ddox

Nope, still didn't help. Not sure what to do...

This is an issue related to DMD's JSON outuput. Related issue: https://github.com/rejectedsoftware/ddox/issues/86
I think at some point we'll switch to the libdparse backend for generating the documentation, though, in which case this will be fixed.

@s-ludwig OK, thanks for letting me know. I will undo that version(StdDdoc) machinery, if it's technically unnecessary.

Fixed up the docs.

I find it a little funny that my first contribution to Phobos lead to a serious regression.
LGTM

@JackStouffer not your fault: 1) I find it funnier that we had no test of classes as an element type, 2) the Object default functions need to go.


What can I do with "too many errors" ?

@guregu hi!  ~
could you help me resolve this? just trying go build for stream but getting stopped at these errors. haven't encountered this before. also just updated go version; if that matters.   Windows 11.
(sorry for posting here , but idk how else to contact you 😅 )

Hello, no worries. Hmm, seems to be related to this https://github.com/bytecodealliance/wasmtime-go/issues/192#issuecomment-1734252302 (tl;dr: upgrading Go breaks the Windows wasmtime-go build?)
Easiest way to get around it would be using WSL and building it in Ubuntu etc. Just tried it and I'm getting weird errors on regular Windows but WSL works.

I might just switch this library to wazero which is written in Go and avoids the library dependencies that wasmtime has. It will be a little slower but a lot easier to build 🤔. For Stream the speed won't be issue because all (iirc) of the work happens during startup.

cool, thanks for the info. yeah on mac i didn't have this issue with newest go version.
good to know at least it was not some messup on my side~
probs no one on our side needs a windows fix for development atm anyway; feel free to close this i guess but pls do let us know if you update things ~

The latest releases upgraded the wasmtime version so it (might) work better in Windows now. It fixes some other stuff too so might be a good idea to upgrade

hi again @guregu  🫡  i'm having the same issue nowadays..  i have a special case where we require  to use windows for sth and streamapi fails to build on it.
i have tried the following go versions:
1.22.~
1.21.0
1.21.12

is there something else i can/should try..?
thanks in advance

With the wazero switch this shouldn't happen anymore!


fix: Removed helper method from Scaffold

This PR fixes https://github.com/flutter/flutter/issues/99712 by replacing a helper method with an actual widget inside the build method
If you had to change anything in the [flutter/tests] repo, include a link to the migration guide as per the [breaking change policy].
Pre-launch Checklist

[x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs.
[x] I read the [Tree Hygiene] wiki page, which explains my responsibilities.
[x] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement].
[x] I signed the [CLA].
[x] I listed at least one issue that this PR fixes in the description above.
[ ] I updated/added relevant documentation (doc comments with ///).
[ ] I added new tests to check the change I am making, or this PR is [test-exempt].
[x] All existing and new tests are passing.

@albertodev01 LGTM could you request a text-exemption from @Hixie on Discord. Thank you!

test-exempt: code refactor with no semantic change

Hey @albertodev01 it looks like this needs to be rebased rather than merged.


target=_blank doesn't work

I can't seem to handle/see/route target=_blank routes, they never seem to even reach TurboSession.shouldOverrideUrlLoading, I have logging on and never see any logs fired from those links.
We are using Turbolinks 5 on the web still and Turbo on Android, this is working fine with Turbolinks on Android, and does work with iOS using the new Turbo library interacting with Ruby Version 5. Wondering if it's a regression between New Android and Legacy Web?
If you need more insight to the website hopefully @cmartyn or @joemasilotti  can answer any questions.

@chrisjenx I'm curious, is the target=blank link part of an <iframe> or some other embedded content on the page? I'm aware of an issue with <iframe> links, which I'll open a PR and fix.
Ordinary target=_blank links should work, though, just like in the demo app: https://github.com/hotwired/turbo-native-demo/blob/main/views/index.ejs#L46-L49

Oh I don't think so, but I do know I had to add settings.setSupportMultipleWindows(true) to enable opening files on the older version, so that should hopefully fix it here too.

Oh nevermind, I have that turned on already...

Interesting, if settings.setSupportMultipleWindows(true) is enabled, you also need to handle WebChromeClient.onCreateWindow(), so maybe that's the issue?
I'll merge #145 over and ship a new beta and you can try it out. If that doesn't solve the issue you're running into, I'll need more specific steps to reproduce.

7.0.0-beta06 is now available.

Not sure if it was in an iframe or not, but yes that fixed it :partying_face:


Make ContainerExceptionInterface extend Throwable where it is available

I've run into some static analysis issues because the ContainerExceptionInterface provides no guarantee that it's actually throwable (or catchable more specifically).
I understand making it extend Throwable would break BC, so I think this would be the ideal middle ground, providing the benefit of stricter typing only where it's available.

👍 I've faced the same problem.
Is it a BC break to extend Throwable?

Current minimum compatibility constraint is
"require": {
    "php": ">=5.3.0"
}

Throwable is only available from 7.0 upwards.

OK I see, tagging a release that targets 7.0 wouldn't really be a BC break though since Composer will not install the new release unless you run PHP 7.

Agreed, and I'm not aware of the FIG's BC policy, but to me it's seems unnecessary to limit BC to PHP 7+ going forward, while with this solution, we can still maintain compatibility with 5.3+.
Although I also don't see many changes/upgrades coming to this package in the future, since I guess it does what it's supposed to ;-)
If it's preferred to just extend Throwable without the existence check for the interface, I'm happy to change it.

You're right, this solution works fine!
I'm :+1: with both solution. Does anyone know what is needed to merge this?

Unfortunately we do not have any kind of process defined for this kind of stuff. In any case, the editor(s) of this PSR (which are you @mnapoli along with @moufmouf) have the final say on this.

@mnapoli @moufmouf Could you please take another look at this and if it's acceptable, get it merged and released? Would be much appreciated.

@mnapoli @moufmouf @Jean85 Gentle reminder that this PR is still here and open 😉 Any chance we can get this merged and released?

We've been discussing this kind of issues a lot lately, and we've condensed our proposed solution to updating PSR interfaces in a blog post. Please read it and provide your feedback!
https://www.php-fig.org/blog/2019/10/upgrading-psr-interfaces/

@Jean85 I've read the post and it makes total sense, I've filled in the feedback form.
At the same time, to be honest, I don't think it really applies to this PR, as this has specifically been created to not be a BC break, therefore I'd still love to just get this merged and released as 1.0.1

Hey, I'm in the process of adapting more PSR interfaces in Nextcloud and I came across this missing base class as I added the psr/conatiner package. Would it be possible to include this change with the v2.0 release together with https://github.com/php-fig/container/pull/28?

This could made even 1.1, and with no if shenanigans too!
ping @weierophinney

@Jean85 Would this require an errata vote?

I hope not ^^

@weierophinney IMHO it could be bundled up with everything else in the 1.1-2.0 evolution vote. As far as I'm concerned, this interface only enforces at the code level what the spec requires.

@Jean85 This patch actually duplicates work already in #20, which does target 1.1, and doesn't require a conditional as it requires PHP 7.2. As such, I'm closing it.

@Jean85 This patch actually duplicates work already in #20, which does target 1.1, and doesn't require a conditional as it requires PHP 7.2. As such, I'm closing it.


Can not get online access token

Overview
I am using @shopify/koa-shopify-auth and need to implement online access mode authorization flow, I set accessMode to online but still get offline access token which does not contain associated_user data described in Shopify docs
shopifyAuth({
  apiKey: SHOPIFY_API_KEY,
  secret: SHOPIFY_API_SECRET,
  scopes: ['write_products'],
  accessMode: 'online',
  afterAuth(ctx) {
    const {shop, accessToken} = ctx.session;

    console.log('We did it!', accessToken);

    return ctx.redirect('/');
  },
}),

Please, correct me If I am doing something wrong.
Consuming repo

I have debugged through @shopify/koa-shopify-auth and Shopify returns online accessToken with associated_user and associated_user_scope but @shopify/koa-shopify-auth does not include it in session.


feat : define pre-tight and tight measures

Define tight measures (by first defining separable and pre-tight measures).
Define some api for all three concepts
Prove Ulam's tightness theorem and a strengthened version of this.

I’m struggling to prove ‘of_isSeparable_on_metric’, which should easily follow from the definition is IsSeparable and the result above it by passing to sub spaces and back, but it does not

The linter is not happy...

The linter is not happy...

Thanks, I fixed it now! I forgot to run #lint again after incorporating the points from the previous review.

#12519 also defines a notion of separability of measures, SeparableMeasureSpace. I believe that my definition should agree with that definition on suitable spaces, but that the definition therein is probably the more general. As I'm defining very little API for IsSeparable in my file, I do not think this will bite the reviewing process: once we establish that the definition in #12519 generalizes IsSeparable, we can rewrite my special case as a lemma and adapt the other results by a simple rw.


New version which include fixes on crash, doesn't compatible with Xcode 9.2

Steps to reproduce
Install the pusher in Xcode 9.2
Expected behavior
Since this library use CryptoSwift and it's used the latest one which supposed to used at Xcode 9.3 Swift 4.1, we got many error
Any improvements you suggest
We need the fixes which include crash fixes on latest version to support Xcode 9.2 Swift 4 as well.
...

Is there a reason that you can't use Xcode 9.3? Ideally we'd only support the latest Xcode release with the latest version of the library so if you could suggest why you can't use 9.3 that would be great.

We can't use because it will effect other developers who are working on this project and we need other developer to update to High Sierra in order to use Xcode 9.3. I still have no reason why CryptoSwift library was updated to latest version? is there any reason?

It was updated because most people are using Swift 4.1 and Xcode 9.3 now and without updating it there were warnings (and potentially errors - I can't remember exactly) being shown.
Note that there weren't really any "fixes" per se in the latest release. There was some new behaviour added that hopes to detect disconnections better, but the disconnections that it wasn't detecting in 5.1.1 were largely edge cases, the vast majority of which (if not all) could be remedied by explicitly calling disconnect when the app enters the background (and then calling connect again when the app is in the foreground).

I'll release a 5.2.0 version that backports the new functionality added in 6.0.0.
Are you seeing errors when using 5.1.1?

Please can you see if the branch backport-6.0.0-fixes builds and works for you before I cut a 5.2.0 release?
https://github.com/pusher/pusher-websocket-swift/tree/backport-6.0.0-fixes
Thanks

Seen as there has been no activity on this, it seems fair that the latest version of a framework targets the latest Xcode.

Closing because this issue is no longer relevant.


WIP chart testing workflow

Hey, I just made a Pull Request!

:heavy_check_mark: Checklist

[ ] All tests are passing yarn test
[ ] Screenshots attached (for UI changes)
[ ] Relevant documentation updated
[ ] Prettier run on changed files
[ ] Tests added for new functionality
[ ] Regression tests added for bug fixes

wrong repo


Issue #2169 - Added missing spellcheck for all form text and textarea…

… fields except for fields:
abbreviation
code
name
firstname
surname
Fixes #2169 .

looks good to me. Thanks @johnpinto1!


railway link improvements

Fixes #550
This allows you to specify a project name now. It also handles many more edge cases.

Line 220 has nothing to do with get_project...


Fix openapi yaml exposure

under the url .../api/openapi.yaml it is missing the paths data

the way it should be:

the way it currently is:

We should consider migrating to Redoc.
After extracting the openapi.json from the HTML code at /api-docs I was able to create docs from that file:
npx @redocly/cli build-docs openapi.json

https://redocly.com/docs/redoc/deployment/react/


[Extra Metadata Loader] Re-add the option to use logo's from personal drives.

Extra Metadata Loader
Just re-add the option to use logos from your harddrive rather than from online sources.

Done.


Grayscale & resize PNGs

We need to figure out which resolution we'd like to standardize on, but once we do, all the PNGs generated from #1 need to get grayscaled and sized to that resolution.

Well, the documentation here says the default setting is 150dpi. I didn't specify a resolution when running pdftoppm for #1 , so the 150dpi version of this dataset is 1.9G uncompressed.

The smallest image is 502x502 pixels while the largest is 12157x3336.
The documents don't have to be visually appealing for analysis, so I think we're fine to resize them to 500x500 or lower. Not sure what the best-practices are here.

If we were doing image classification only, then 500x500 would be great.  But for this exercise, I think we should maintain close to a realistic resolution and aspect ratio.
We could kick out documents that don't adhere to the common portrait orientation and 8"x11" size.  On the other hand, non-English documents in the corpus means we will have non-Letter sized documents.  We could try rotating/resizing to a common page size instead of rejecting landscape or A4 sizes, etc.
We may have to settle on 200-300 DPI for this first release of the dataset, just to keep the storage/bandwidth requirements reasonable.  We can consider releasing additional higher-res datasets later if we run out of time to get it done in this round.

With the current 150dpi images, we're looking at 1275x1650 resolution for an 8.5"x11" Letter sheet. There are 2048 images smaller than this in at least one dimension, leaving a little over 4000 left that could be scaled down to that.
We could export 200-300dpi images from the PDFs and then scale them down to that size.

If a manual review of those smaller pages indicates that we should save many or most of those shorter dimensions, then we could lower our threshold and pad those images on the dimensions that fall short.
For images that are slightly larger, we could probably shrink those within some reasonable tolerance (maybe like up to 20% shrinkage is OK).

We're staying on 150dpi for this run. Grayscaling and resizing/fitting code is in the build directory of the repo.


Mobile horizontal padding discrepancy

Description

Banners have less horizontal padding than the site contents on mobile. We should adjust one to match the other, or find a normalized value between the two.
Might want to consider maximizing our use of horizontal space and making the padding a bit smaller?
Reproduction

Visit https://openverse.org in a private/incognito mode on a mobile device.

Screenshots

Personally, I think I like a horizontal padding of 3 (using our scale) on mobile:

I don't think the banner should match the spacings of search result page layout. This element, similar to the global player, was thought to match the screen area. Therefore, it will look different in the homepage, the search result, and in the future, the single result in modal.
This situation does not impact the search experience significantly to be tagged as priority medium, compared to #547 that has been resting there for months and involved a layout improvement of the image result page.

Agreed, it should be low. If you think the banner spacing looks good across device sizes please close this issue 👍


Changed template to prevent unwanted issue linking

I noticed with the template that using a hashtag with numbers is not a good idea.
Currently, it would link all new issues to
https://github.com/Azure/arm-template-whatif/issues/1
and
https://github.com/Azure/arm-template-whatif/issues/2

Thanks for pointing that out. It actually doesn't make sense to use numbers at all. At one point it was a numbered list of items, but I got rid of that. So I changed it accordingly.


Refactoring chart test to use in memory list

Coverage remained the same at 80.943% when pulling 054ce6c419dfdcad1d6395f7798b53dcc0265c00 on AlexeyTurlapov:master into ea22e26fa0f59a0b4a07d8374b737709b4fc0aff on unosquare:master.


SUBMARINE-706. [web] Refactor workbench experiment page

What is this PR for?
The original functionality can still work fine now. I refactored the code and made these major changes:

Split complex components into smaller ones. In that way, it becomes easier to maintain the code. Furthermore, different pages can use the same components easily and do not need to re-write code.
Replace dirty trick with a more elegant method. For example, this bug can be fixed by a shared service between parent and child component rather than checking reload manually.

What type of PR is it?
[Refactoring]
What is the Jira issue?
https://issues.apache.org/jira/browse/SUBMARINE-706
How should this be tested?
Questions:

Does the licenses files need update? No
Is there breaking changes for older versions? No
Does this needs documentation? No

@pingsutw @kevin85421 Help me review this PR. Thanks!

@pingsutw @kevin85421 Help me review this PR. Thanks!

@ByronHsu  Do we need a doc for developers to follow this pattern?

@ByronHsu  Do we need a doc for developers to follow this pattern?

@ByronHsu Do we need a doc for developers to follow this pattern?

The philosophy behind this pattern is just what Angular emphasizes: split different functionality into separate components. I think that other developers can just reference the code of the experiment page so we do not need a specific doc.

@ByronHsu Do we need a doc for developers to follow this pattern?

The philosophy behind this pattern is just what Angular emphasizes: split different functionality into separate components. I think that other developers can just reference the code of the experiment page so we do not need a specific doc.


Frontend: Fix #97, change default python interpreter URL to http://terrarium:8080

Description: The previous default python interpreter URL http://localhost:8080 didn't work with docker compose on Mac. Changing to terrarium (name of the Docker container running Python interpreter API endpoint) fixed the frontend.
Issue: #97
Dependencies: N/A

[x] Add tests and docs: Updated README
[] Lint and test: Run make lint and make run-tests. Need to run CI, these didn't work locally for me.

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

Merging to avoid the need to update the branch again!


Does the getIdleConnections() method under HikariPoolMXBean class brings the idle connections that are still valid connections?

Environment
HikariCP version: 3.2.0
JDK version     : 1.8.0_102
Database        : AS400
Driver version  : jt400-jdk8 v9.8

I am trying to switch the datasources from a primary AS400 to a secondary AS400 in case the primary AS400 is not online. To do this I am looking at the idle connections in the pool. Idle connections are still valid connections to the DB, correct?

@amitbhanot The idle count available through the MXBean may include connections that are not valid.  Connections are tested upon borrow, and therefore connections "sitting" in the pool may or may not be valid.
If, however, you have an idleTImeout configured, and a minimumIdle setting that is less than maximumPoolSize , you can be reasonable sure that the connections are alive.
If you are trying to detect that the primary AS400 has gone down, I suggest looking primarily at the total pool size.  When a database fails, the pool will quickly exhaust all of the connections.  When a new connection is requested, one will be selected, then tested, and upon failing, evicted from the pool -- and the process repeated very quickly for the remaining connections in the pool.

@brettwooldridge That is in fact what I am doing. I am querying the DB which uses an available invalid connection from the pool. Since the connection is invalid, the query fails and I switch it to the secondary AS400 datasource. Thank you for that explanation.


Fix copy(::Transducer, ::Table) etc.

Type parameters must be dropped off to call a proper constructor.
xfail: https://travis-ci.com/tkf/Transducers.jl/builds/141126703

Codecov Report

Merging #104 into master will increase coverage by 0.12%.
The diff coverage is 60%.

@@            Coverage Diff             @@
##           master     #104      +/-   ##
==========================================
+ Coverage   88.88%   89.01%   +0.12%
==========================================
  Files          17       17
  Lines        1107     1074      -33
==========================================
- Hits          984      956      -28
+ Misses        123      118       -5

Impacted Files
Coverage Δ

src/basics.jl
25% <0%> (-5%)
:arrow_down:

src/processes.jl
90.78% <100%> (-0.71%)
:arrow_down:

src/dreduce.jl
100% <100%> (+5%)
:arrow_up:

src/reduce.jl
100% <100%> (+4.91%)
:arrow_up:

src/core.jl
72.18% <0%> (-2.33%)
:arrow_down:

src/show.jl
94.87% <0%> (-0.05%)
:arrow_down:

src/library.jl
93.5% <0%> (-0.02%)
:arrow_down:

... and 2 more

Continue to review full report at Codecov.

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


Align vue-treeselect with a label

Hello.
I am trying to align vue-treeselect side-by-side with other elements however I am probably missing something. The only way I've been able to this to work was specifying a custom max-width property, so the rest of the elements on its side would not get overlapped.
The issue can be seen in the following snippet, as I am trying to align two elements (a simple span and a vue-treeselect):
https://codesandbox.io/s/8z0wzpxmxj
Any idea?

Hi @IvoPereira. I'm sorry but not seeing any issue or maybe not getting the point. Can you explain more or improve your demo? I don't know how you want the elements to be aligned.

@riophae I want the elements to be side-by-side.
Let me know if this helps to understand the issue:
https://codesandbox.io/s/8z0wzpxmxj

I see. You should use table-cell instead of inline-block:
https://codesandbox.io/s/mzv9npov48


Bring supported object list up to date

Set closed issues with object de/serialisers to Yes, update PDTS to remaining todo.

I was thinking about this update, too. thanks.
I thought about adding a column with the reference to the merge that introduced the object type (or relevant issues discussing it) instead of removing it. This way you can find for example who "invented" it easily.

Hmm, I see this as more effort than the value it adds. Just pop an object type into the GitHub search box and you get much more useful and relevant info.

The list is part of user docs. Agree, let's keep it simple.


ArcGIS Online Geometry service causing error

When the app is configured to use the ArcGIS Online geometry service (which it is by default), the user will occasionally encounter a message "The searched area is outside the area of interest and will not be analyzed."
This message should only display if the searched area is outside of the default extent of the webmap.  However, we are now seeing it with areas searched within the default extent of the webmap.
Steps to repro:

Using http://tryitlive.arcgis.com/SiteSelector/ as an example, enter a search address for a location in Maryland and use the buffer slider to define the buffer distance.
Increase the buffer distance on the buffer slider to search again.  You will see a message: “The searched area is outside the area of interest and will not be analyzed.”

When the application is configured to use the Geometry Service running on ArcGIS Server rather than ArcGIS Online’s geometry service, we do not see this issue.
An incident has been logged with Technical Support.

The application's config.js and proxy.config should be updated to switch the Geometry Service from http://tasks.arcgisonline.com/ArcGIS/rest/services/Geometry/GeometryServer to

either https://utility.arcgisonline.com/arcgis/rest/services/Geometry/GeometryServer/
or a geometry service running on a local ArcGIS Server

Addressed in commit https://github.com/Esri/site-selector/commit/4bf4b1f2a5e253684ac619e4d129b659217ae24b