tf.gather with int32 indices yields wrong result on gpu

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow):
yes
OS Platform and Distribution (e.g., Linux Ubuntu 16.04):
$ cat /etc/issue
Ubuntu 16.04.2 LTS
TensorFlow installed from (source or binary):
Source head
TensorFlow version (use command below):
1.3
Python version:
3.6
Bazel version (if compiling from source):
bazel release 0.4.5
CUDA/cuDNN version:
8.0, 7.0
GPU model and memory:
GeForce GTX 980
Exact command to reproduce:

import tensorflow as tf

def bug():
  params = tf.convert_to_tensor([0., 1., 2., 3., 4., 5., 6., 7.], dtype=tf.float32)
  indices_32 = tf.convert_to_tensor([2, 0, 2, 4], dtype=tf.int32)
  indices_64 = tf.convert_to_tensor([2, 0, 2, 4], dtype=tf.int64)
  test_op_32 = tf.gather(params, indices_32)
  test_op_64 = tf.gather(params, indices_64)
  with tf.Session() as sess:
      res = sess.run([test_op_32, test_op_64])
  print('test_op_32', res[0], 'test_op_64', res[1])

bug()
with tf.device('/cpu:0'):
  bug()
bug()

Describe the problem
When using int32 indices for tf.gather on GPU, wrong (random) numbers are returned.
See code above. It does not occur if using int64 or running on CPU.
Output
2017-09-08 15:54:08.775830: I tensorflow/core/common_runtime/gpu/gpu_device.cc:965] Found device 0 with properties:
name: GeForce GTX 980 major: 5 minor: 2 memoryClockRate(GHz): 1.2785
pciBusID: 0000:04:00.0
totalMemory: 3.94GiB freeMemory: 158.62MiB
2017-09-08 15:54:08.775862: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1055] Creating TensorFlow device (/device:GPU:0) -> (device: 0, name: GeForce GTX 980, pci bus id: 0000:04:00.0, compute capability: 5.2)
test_op_32 [ 0.  0.  0.  0.] test_op_64 [ 2.  0.  2.  4.]
2017-09-08 15:54:08.792745: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1055] Creating TensorFlow device (/device:GPU:0) -> (device: 0, name: GeForce GTX 980, pci bus id: 0000:04:00.0, compute capability: 5.2)
test_op_32 [ 2.  0.  2.  4.] test_op_64 [ 2.  0.  2.  4.]
2017-09-08 15:54:08.800545: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1055] Creating TensorFlow device (/device:GPU:0) -> (device: 0, name: GeForce GTX 980, pci bus id: 0000:04:00.0, compute capability: 5.2)
test_op_32 [ 3.  0.  0.  0.] test_op_64 [ 2.  0.  2.  4.]

Could you try on github head? I can't seem to be able to repro. Can you also try on a prebuilt pip package?

I cant reproduce this on pip 1.3

It might be related to the address the array is stored in:
2017-09-10 16:16:52.557622: I tensorflow/core/common_runtime/gpu/gpu_device.cc:965] Found device 0 with properties:
name: GeForce GTX 980 major: 5 minor: 2 memoryClockRate(GHz): 1.2785
pciBusID: 0000:04:00.0
totalMemory: 3.94GiB freeMemory: 158.62MiB
2017-09-10 16:16:52.557653: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1055] Creating TensorFlow device (/device:GPU:0) -> (device: 0, name: GeForce GTX 980, pci bus id: 0000:04:00.0, compute capability: 5.2)
test_op_32 [ 0.  0.  0.  0.] test_op_64 [ 2.  0.  2.  4.]
2017-09-10 16:16:52.573418: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1055] Creating TensorFlow device (/device:GPU:0) -> (device: 0, name: GeForce GTX 980, pci bus id: 0000:04:00.0, compute capability: 5.2)
test_op_32 [ 2.  0.  2.  4.] test_op_64 [ 2.  0.  2.  4.]
2017-09-10 16:16:52.580016: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1055] Creating TensorFlow device (/device:GPU:0) -> (device: 0, name: GeForce GTX 980, pci bus id: 0000:04:00.0, compute capability: 5.2)
test_op_32 [ 3.  0.  0.  0.] test_op_64 [ 2.  0.  2.  4.]

2017-09-10 16:17:17.984597: I tensorflow/core/common_runtime/gpu/gpu_device.cc:965] Found device 0 with properties:
name: GeForce GTX 980 major: 5 minor: 2 memoryClockRate(GHz): 1.2785
pciBusID: 0000:04:00.0
totalMemory: 3.94GiB freeMemory: 3.87GiB
2017-09-10 16:17:17.984626: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1055] Creating TensorFlow device (/device:GPU:0) -> (device: 0, name: GeForce GTX 980, pci bus id: 0000:04:00.0, compute capability: 5.2)
test_op_32 [ 2.  0.  2.  4.] test_op_64 [ 2.  0.  2.  4.]
2017-09-10 16:17:18.160432: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1055] Creating TensorFlow device (/device:GPU:0) -> (device: 0, name: GeForce GTX 980, pci bus id: 0000:04:00.0, compute capability: 5.2)
test_op_32 [ 2.  0.  2.  4.] test_op_64 [ 2.  0.  2.  4.]
2017-09-10 16:17:18.167003: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1055] Creating TensorFlow device (/device:GPU:0) -> (device: 0, name: GeForce GTX 980, pci bus id: 0000:04:00.0, compute capability: 5.2)
test_op_32 [ 2.  0.  2.  4.] test_op_64 [ 2.  0.  2.  4.]

Notice that the bug appears when there is hardly any free memory while it doesn't when all memory is free. Possibly an int32 overflow somewhere?

@jheymann85 that's interesting, thank you for pointing that out.
@rmlarsen I'll take a look later, but if you get to this faster, that would be nice.

More details for reproduction:
I run tensorflow 32ffc5a81eee8c39bbe71536212a773b1ffd4eb2. But the related tensorflow code does not seem to have changed very recently.
We only have access to cards with limited amount of memory (i.e. totalMemory: 5.94GiB). I have to consume a lot of memory in a different tensorflow session, to make this bug appear.
To be more precise: It works, when there is not enough allocated, compare freeMemory:
name: GeForce GTX 980 major: 5 minor: 2 memoryClockRate(GHz): 1.2785
pciBusID: 0000:04:00.0
totalMemory: 3.94GiB freeMemory: 226.75MiB
...
test_op_32 [ 2.  0.  2.  4.] test_op_64 [ 2.  0.  2.  4.]

If I now allocate more (i.e. start yet another session):
name: GeForce GTX 980 major: 5 minor: 2 memoryClockRate(GHz): 1.2785
pciBusID: 0000:04:00.0
totalMemory: 3.94GiB freeMemory: 149.75MiB
...
test_op_32 [ -1.27668094e+38   2.91721193e-39   1.10202595e-38   3.42339542e+17] test_op_64 [ 2.  0.  2.  4.]

Sorry I didn't get around that, if you have a program that exhibits that behavior by allocating a lot of memory then performing the operation? That way I can try to repro and debug. Thank you!

One way to reproduce is to open some other Tensorflow sessions on the same host. I.e.:
tf_sess.py:
import tensorflow as tf
import time
s = tf.Session()
time.sleep(30)

and then execute
python tf_sess.py &
python tf_sess.py &
python example.py

yields
2017-09-20 08:01:36.029417: I tensorflow/core/common_runtime/gpu/gpu_device.cc:965] Found device 0 with properties:
name: GeForce GTX 980 major: 5 minor: 2 memoryClockRate(GHz): 1.2785
pciBusID: 0000:04:00.0
totalMemory: 3.94GiB freeMemory: 149.75MiB
2017-09-20 08:01:36.029446: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1055] Creating TensorFlow device (/device:GPU:0) -> (device: 0, name: GeForce GTX 980, pci bus id: 0000:04:00.0, compute capability: 5.2)
test_op_32 [ -6.38132574e+37   2.93414410e-38   2.77472790e-38   4.32417032e+17] test_op_64 [ 2.  0.  2.  4.]
2017-09-20 08:01:36.044647: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1055] Creating TensorFlow device (/device:GPU:0) -> (device: 0, name: GeForce GTX 980, pci bus id: 0000:04:00.0, compute capability: 5.2)
test_op_32 [ 2.  0.  2.  4.] test_op_64 [ 2.  0.  2.  4.]
2017-09-20 08:01:36.050076: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1055] Creating TensorFlow device (/device:GPU:0) -> (device: 0, name: GeForce GTX 980, pci bus id: 0000:04:00.0, compute capability: 5.2)
test_op_32 [  1.42191624e-13   2.90286264e-39              nan   4.26825146e-22] test_op_64 [ 2.  0.  2.  4.]

The number of open sessions necessary to reproduce may vary depending on the amount of memory they consume. For me two worked, but one was not sufficient.

@jheymann85, I can reproduce this issue on TensorFlow 1.3 but not TensorFlow 1.4, so I am going to assume it's fixed (although I'm curious what the issue was). Please reopen if you discover the issue still exists in some form.

Has anyone had issues with this since? I'm having results reproducibility issues using tf.gather with TF2.2-stable. I have set all seeds and turned TF_DETERMINISTIC_OPS=1


VSTS organization URL helper samples

Samples showing how to properly construct a URL to a VSTS organization (formerly called "account") using either its name (e.g. "Fabrikam") or its GUID identifier.
Example of how to use the new helper:
public async Task DoSomething()
{
    Uri orgUrl = OrganizationUrlHelpers
        .GetConnectionUrl("myOrgName");  // typically resolves to https://myorgname.visualstudio.com

    VssConnection orgConnection = new VssConnection(orgUrl, credentials);

    BuildHttpClient buildClient = orgConnection.GetClient<BuildHttpClient>();
}

If you have a moment to retarget this at main, I'd still merge it.


Explicitly defining ingress on Sidecar results brief service impact

Bug description
Whilst working around https://github.com/istio/istio/issues/17465, we're having to explicitly define ingress on our sidecar.  In the vast majority of circumstances, this changes nothing about the inbound listeners; for example we added:
    ingress:
    - defaultEndpoint: <IP_ADDRESS>:8080
      port:
        name: http-app
        number: 8080
        protocol: HTTP
    - defaultEndpoint: <IP_ADDRESS>:8081
      port:
        name: http-admin
        number: 8081
        protocol: HTTP

To this service/endpoint:
❯ kubectl get ep
NAME    ENDPOINTS                                                             AGE
admin   <IP_ADDRESS>:8081,<IP_ADDRESS>:8081,<IP_ADDRESS>:8081 + 12 more...   560d
app     <IP_ADDRESS>:8080,<IP_ADDRESS>:8080,<IP_ADDRESS>:8080 + 12 more...   2y28d

Which is basically, identical in terms of configuration.  However the service is under load and when the ingress was applied to Sidecar we had a large spike in 503NR errors from reporter=source:

[ ] Docs
[ ] Installation
[x] Networking
[x] Performance and Scalability
[ ] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[x] User Experience
[ ] Developer Infrastructure
Expected behavior
Should be able to add listeners to the Sidecar which match existing listeners without service impact.
Steps to reproduce the bug
Have an existing Sidecar resource with no ingress, and then add ingress matching an existing listener generated from the pod ports.
Version (include the output of istioctl version --remote and kubectl version --short and helm version if you used Helm)
1.5

Will need to look more into the details but this is probably related to https://github.com/istio/istio/issues/26861

To confirm it is the same issue, does the NR happen after ~ 30 minutes from when the pod boots (or whatever your connection timeout for values.pilot.keepaliveMaxServerConnectionAge is?)
This is exactly the symptom we saw & fixed with a patch like 26861. It is fixed after that patch (but telemetryv2 doesn't work).

I strongly suspect this is a variant of https://github.com/istio/istio/issues/26861 which will be fixed by the same patch. need to verify though. Unfortunately due to the telemetry dependencies it will be extremely challenging to backport as is

I did some initial testing and reproduced the original issue and failed to reproduce it in 1.8


Add paravirtual mode support, nodeSelector, deployment Strategy for different versions of CPI.

What this PR does / why we need it

This PR
[x] enables support of para-virtual mode for older versions of CPI, to support 1.21 and 1.22 TKr.
[x] adds node selector and update strategy for 1.21.3, 1.22.6, 1.23.0 CPI package, with additional unit tests
Which issue(s) this PR fixes

Fixes: #
Describe testing done for PR

CPI package unit test
Special notes for your reviewer

/lgtm
@shyaamsn please take a look

/lgtm
/approve


Check for outdated tools

It would be great if this tool could check tools for outdated versions (local and global)

I think this would be really useful addition! For now there is a separate tool that does this: https://www.nuget.org/packages/dotnet-tools-outdated/

That is really cool. I hadn't seen that before. Hopefully we can leverage the work @rychlym has already done. I've raised an issue to start that conversation.

I found this thread today hoping for a way to check for outdated local tools. I looked at the dotnet-tools-outdated tool mentioned by slang25, but it still only supports global tools. I also read through the collaboration issue raised by coderpatros.
I raised an issue to request local tools support if/when the author has time for it since I can't find any way to do it with the CLI tools I've seen so far.


ValueError: Warning: could not perform deep copy of <class 'fpsim.sim.Sim'>: cannot pickle 'dict_values' object

Copy error raises from sc.dcp() when running a Multisim. Example:
https://github.com/fpsim/fpsim/blob/rc2.0-tuts-community-day/docs/tutorials/T3_interventions.ipynb

Multisim with RandomChoice works, but it doesn't with SimpleChoice


TranslateApiException

TranslateApiException: The Azure Market Place Translator Subscription associated with the request credentials has zero balance. : ID=5043.V2_Json.Translate.1E249B13

+1


ESP32 support does not work

I tried to compile the MCP4911_test-example but get the error-message
exit status 1
'selectVSPI' was not declared in this scope
I guess this is due to this if-define-condition that does not evaluate to true
/ ESP32 specific
#if defined(ESP32)
void     selectHSPI() { _useHSPI = true;  };
void     selectVSPI() { _useHSPI = false; };
bool     usesHSPI()   { return _useHSPI;  };
bool     usesVSPI()   { return !_useHSPI; };
// to overrule ESP32 default hw pins...
void     setGPIOpins(uint8_t clk, uint8_t miso, uint8_t mosi, uint8_t select);
#endif
sighh!
just another one of those libraries that are shared "as is".
So I'm gonna try this MCP4922-library
https://github.com/michd/Arduino-MCP492X
let's see if I can successfully compile with this library

Hi,
this version / functionality is merged today - see #5 - after some days of testing.
I compiled it with the IDE 1.8.13 and board: ESP dev Module  and the ESP32 Wrover module
Can you tell me what board you used?

https://github.com/michd/Arduino-MCP492X
A quick look at the code shows it does not support VSPI  / HSPI / ESP32

TODO: need to write a VSPI example

@StefanL38

Added an example to the master branch HOW to select VSPI for an ESP32.
https://github.com/RobTillaart/MCP_DAC/tree/master/examples/MCP4921_VSPI
If your board is not an ESP32, VSPI is not supported yet,

Added a few lines in the readme.md file to make the order of commands to use VSPI more explicit.

Hello Rob,
thank you for answering so quick.
I made some progress. The error of not compiling was caused by my call of selectVSPI()
just "selectVSPI()"
without a
MCP.selectVSPI();
now the MCP4911_test-code does compile but I don't see any signal change on any pin of my ESP32
it is a JOY-IT ESP32 DEV-module
I will test your example for the ESP32.
I will report if I have succcess or what questions I still have....
best regards Stefan

Yes I do have questions:
your example uses
 MCP.setGPIOpins(20,21,22,10);   // needs to be called after begin()
But it is completely unclear to me which ESP32-IO-pin number must be connected to what on the MCP4922
best regards Stefan

it is a JOY-IT ESP32 DEV-module

It is not in my list of boards, which one  do you use to compile?

ESP32 Dev module. Never had any issue with this board selection
I'm using this pinout picture

Your call to
 //              clk, miso, mosi, select   MCP.setGPIOpins(20,21,22,10);   // needs to be called after begin()
makes no sense with this pinout GPIO20 is not in there
best regards Stefan

MCP.setGPIOpins(20, 21, 22, 10);

The order of the parameters

CLOCK,
MISO (not used),
MOSI,
SELECT

The numbers I used are just random chosen (your setup might use other ones).
If you remove this line MCP.setGPIOpins(20, 21, 22, 10);  the VSPI default pins will be used
See table https://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-reference/peripherals/spi_master.html#gpio-matrix-and-io-mux

makes no sense with this pinout GPIO20 is not in there

correct, GPIO10 is also not in the picture, so you must adjust the sketch to the pins you use.

I have a big request can you post an example where real accessible IO-pins are used (not the ones connected to the flash)
and add some kind of documentation which ESP32-IO-pin must be connected to what IO-pin of the MCP4922
The abbreviations all differ and that is the reason why it is unclear to me

best regards Stefan

MCP4922
ESP32  VSPI

CS
SELECT = 15

SCK
SCLK   = 14

SDI
MOSI   = 13

Hi Rob,
thank you very much. I will re-wire my setup and test...

You're welcome, with a bit of luck and persistence it will work :)
The example has been updated to a sort of minimum which uses the default pins of VSPI.

Note: I am developing a minor update in the develop branch.
should not interfere with your issue except that I might be offline ...

I have added this code to loop() because I wanted to measure the voltage of the DAC.
void loop() {   MCP.fastWriteA(1024);   MCP.fastWriteB(1024);   //Serial.println("MCP.fastWriteA(1024)");   //delay(3000);   MCP.fastWriteA(2048);   MCP.fastWriteB(2048);   //Serial.println("MCP.fastWriteA(2048)");   //delay(3000); }
But it always shows 0,00V on my digital multimeter
I commented out the serial print and delays to have a continious stream of command send to the MCP4922
because I want to check if there are any signals on the IO-pins.
If I'm probing the Chip-selectpin
 MCP.begin(15);
I see a 400-500 nanoseconds long high-pulse that repeats every 10 microseconds
I have no experience with SPI at all but this looks strange to me.
The datasheet of the MCP4902/4912/4922 says
3.2 Chip Select (CS)
CS is the Chip Select input, which requires an
active low signal to enable serial clock and data functions.
If I connect the second channel of my 100 MHz digital storage-oscilloscope to MOSI (GPIO13) or clock  (GPIO 14)
I see no pulses at all!?!?!???
So I checked all IO-pins with my DSO but I did not see any signal on any IO-pin.
Next thing I checked was:  if the IO-pins work at all. So I uploaded a small democode that does PWM on the IO-pins
`int freq = 5000;
int ledChannel = 0;
int resolution = 8;
const byte IO_Pin = 13;
void setup() {
ledcSetup(ledChannel, freq, resolution);
ledcAttachPin(IO_Pin, ledChannel);
}
void loop() {
for (int dutyCycle = 0; dutyCycle <= 255; dutyCycle++) {
ledcWrite(ledChannel, dutyCycle);
delay(7);
}
for (int dutyCycle = 255; dutyCycle >= 0; dutyCycle--) {
ledcWrite(ledChannel, dutyCycle);
delay(7);
}
}`
My DSO clearly showed PWM based on ledc works. The duty-cycle goes up and down like it should
Did you do a real hardware-test with your library?
I mean connecting a real MCP4921/MCP4922 to an ESP32
connecting all the wires including SHDN, VrefA, VrefB and really measured with a DMM or DSO if the right voltage
is really created on the VoutA / VOutB-pins of the MCP49x"?
best regards Stefan

(put better tags around the code in your post)

Did you do a real hardware-test with your library?
No, as you can read in issue #5 I did not connect any MCP to my ESP32 as I have no MCP available, however Hank did the testing and he had it working in the end. Not immediately, it took some iterations.

Coming week - I hope Wednesday - I will have and time and the hardware needed - so it is definitely on my list to verify it is working by myself.
Previous versions of the library were tested with UNO and an ESP32 (used the HSPI if I recall correctly)
Do you have pull up resistors on the MOSI and CLOCK line?
As the library is default set to 16MHz this could be a problem.  try setting the MCP.setSpeed(1000000);

I think the pin table got switched  VSPI - HSPI columns , sorry

MCP4922
ESP32  VSPI
ESP32  HSPI

CS
SELECT = 5
SELECT = 15

SCK
SCLK   = 18
SCLK   = 14

SDI
MOSI   = 23
MOSI   = 13

I measured and when selecting VSPI - and setSPIspeed(1000000) - I got a clock on pin 18

merged the 0.1.3 preparations in master

added increment(channel)
added decrement(channel)
updated readme.md to reflect correct SPI pins
updated VSPI example with some comments.

TEST 1
no MCP connected,
when selectVSPI()  I get MOSI signals on pin 23, and CLOCK on pin 18
When selectHSPI() I get MOSI signals on pin 13 and CLOCK on pin 14
so SPI peripheral selection works and data is send

merged the 0.1.4 in master

fix setGPIOpins() to overrule default HSPI / VSPI pins

Did you do a real hardware-test with your library?
I mean connecting a real MCP4921/MCP4922 to an ESP32
connecting all the wires including SHDN, VrefA, VrefB and really measured with a DMM or DSO if the right voltage
is really created on the VoutA / VOutB-pins of the MCP49x"?

ESP32 via VSPI to MCP4922
external power of 5V
Sinus 1000 Hz
MCP4921_wave_generator.ino with these lines added to use the VSPI
  MCP.selectVSPI();     // needs to be called before begin()
                        // uses default HSPI SCLK=14, MISO=12, MOSI=13, SELECT=15
                        // uses default VSPI SCLK=18, MISO=19, MOSI=23, SELECT=5
  MCP.begin(15);        // 5 for VSPI and 15 for HSPI

works

@HankLloydRight

edit: I'm working on a 6 channel DAC:

You might add a LED to the CS lines to see activity ?

Yup! Already in the next layout, this was just a V0 test board.

Yup! Already in the next layout, this was just a V0 test board.

It occurred to me though, at 30kHz, wouldn't the CS line LEDs just seem to be "on" all the time?

Yup! Already in the next layout, this was just a V0 test board.

It occurred to me though, at 30kHz, wouldn't the CS line LEDs just seem to be "on" all the time?

Yes and that is exactly what you want to see. It informs you that all 3 your channels (x2) get their data in a very high pace.
I always add several LEDs. That allows my customers to send a picture of the board so I have a first order "diagnostics" what works and what not. A LED for 3.3, 5 and/or 12V etc is useful to diagnose a broken power supply or fuse "poofed".

I have LEDs on the 3.3v  output of the voltage regulator as well as LEDS on the +5v and -5V output of the bipolar power supply  (not in the photo above).  BTW, how do I tap the CS lines with an LED without affecting the signal? I also have RGB analog output (0-5v) which I'd like to add an LED, but again, don't want to affect the signal.  Thanks.
(I only barely know what I'm doing, I'm not a trained EE :) )

An LED will not take much current.
Assume you have 5V supply
Assume Led may take 10mA at max
Assume led needs 2V
formula: R = (voltage supply - voltage LED) / (desired led current)
R = (5 - 2) / 0.01 = 300 ohm
If you want less luminosity you take 600 ohm (~50%) - or a standard value of 470 ohm (~60%).
For diagnostics 60% is often bright enough. Note the leds are already dims as they are not 100% on.
More detailed see e.g. https://www.circuitspecialists.com/blog/how-to-determine-resistor-value-for-led-lighting/

Awesome, thank you!

@StefanL38
Did you manage to get it working?

@StefanL38
If the issue persists feel free to reopen the issue.


Question about bitrate and framerate

Hi.
I am a little confused with the parameters for encoder.
SEncParamExt has this:
oSEncParamExt.fMaxFrameRate
and this;
oSEncParamExt.iTargetBitrate
Whats confuse me is that if i set fMaxFrameRate to be 30 for example then this alone can determine the Bitrate.
Then why there is an option to set the iTargetBitrate then?
Same question here:
oSEncParamExt.sSpatialLayers[0].fFrameRate = 30.0f;
oSEncParamExt.sSpatialLayers[0].iSpatialBitrate = 1500000;
and why there is an option to choose bitrate & FrameRate for input and for output.
Hope someone can make me understand this.
Thanks.

@jim12345 I believe there is no way to have both constant bitrate and framerate. To do that the encoder should be able to automatically lower encoding quality.
Right now if we set the SEncParamExt.bEnableFrameSkip to false there is a warning that tells us that Rate Control is disabled without skipping frames.
Automatically lowering encoding quality rather than framerate would be nice.


Invisible note that plays no animation.

Describe your problem here.
Since my last request, I've just learned that for the custom event "Set Cam Zoom" to work, a note needs to be hit by the player or the opponent. So, I just wanted to know if I could have a lua script to make an invisible note that doesn't play any animations. Thanks !
Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
No

dont use invisible notes use
function onCreatePost(elapsed)
setProperty('camGame.zoom', 5)
doTweenZoom('begin', 'camGame', '6', 3, 'quadOut')
setProperty('camHUD.zoom', 5)
doTweenZoom('begin', 'camHUD', '6', 3, 'quadOut')
end
camGame can be replaced with
camHUD
or
camOther
camGame zooms in the game
camHUD zooms in the UI
camOther is the pause menu lol
use camGame and camHUD like i put above so you can have a similar feel
number 6 is the zoom
number 3 is the zoom out or in time
number 5 is starting song zoom
i recommend just making the 6 and 5 the same if you want but this is an easy way to do that instead


implementation of global setup/teardown; closes #4308

This PR adds mochaGlobalSetup and mochaGlobalTeardown fixtures, loaded like mochaHooks via --require.  the function(s) defined here are guaranteed to run once and only once, in serial, parallel, serial-watch or parallel-watch modes. this should be the preferred way of running global setup/teardown code, and I'll need to update the docs accordingly.  the setup and teardown functions will share a single context object, and will only run in the main process.
more:

adds a generic "plugin loader" which handles root hooks, global setup/teardown, future.  these "plugin definitions" (of which there are three: root hooks, global setup, and global teardown) adhere to a rough "interface" at this point, but are not entirely self-contained--functionality is still tightly coupled to the Mocha class, which needs instance methods to support each.  I'm choosing to defer any decisions on this design for now
renamed validatePlugin to validateLegacyPlugin. reporters/interfaces could/should eventually be refactored to use the same system.  this would make it less awkward to define a custom reporter, for instance.
soft-deprecates errors.createPluginError; directs consumers to use errors.createLegacyPluginError instead

What I mean by "reporters and interfaces should use this plugin system" above is that it's currently awkward to implement a third-party reporter or interface.  You have to essentially set properties on Mocha.interfaces or Mocha.reporters.  This new system could detect the presence of a reporter/interface in a --require'd file via named exports and do the plumbing for you.  We'd also have a chance, if e.g., --require my-reporter was used, to enable the reporter automatically if no other --reporter was given (and this would need to be limited to a single reporter, since we don't have multiple reporter support).

rebasing onto branch boneskull/rollup-umd

To support watch mode effectively, I need to rip this impl out of Runner and put it into Mocha.

Coverage increased (+0.07%) to 93.999% when pulling 20dd2785b5ebc2b5f8bd082a3d91e8442f633ff2 on boneskull/issue/4308-global-setup-teardown into 2d32246de032185297f5b4afd1136b850fefe065 on master.

hey, green build finally.
looks like it needs some more tests though.

Started having a read, plugins look good.
So we are following the same approach as Jest + not allowing state or resources to be available for tests? So is intended for things like start/stop of a server or db, but will need root suite hook to create connection instance to use in tests. It is fine I just wanted to be clear.
I was thrown by the "fixture" term, as we use it elsewhere in the repo and then we follow the common JS ecosystem meaning.
I understand the difficulty though as:

Plugins could/might be for more than just hooks so they arent synonymous
"globalSetup" is not a hook
Its useful to have "globalSetup plugin" + "globalTeardown plugin" coupled semantically as they are in code

So im not sure what to suggest, seems useful to have this new category, but could get confusing.

Thanks @craigtaub. Yeah there's really no reasonable way to share a file, db handle, socket etc across spawned worker processes. Each worker process would have its own handle, and this would be suitable for root hook plugins instead of these globals.
You can share state between global setup and teardown, but the suites, hooks, and tests themselves can not access that state.
"Fixture", I think, is not inappropriate (see wiki). we're using it to mean roughly the same thing in our test "fixture" files--it's some environment or a context we test in.

@craigtaub Can you take a look, specifically, at the changes to the "run cycle overview" in docs/index.md? It was out-of-date with respect to parallel mode, root hooks, and this PR (and I felt like it needed further expansion)

I'm referencing version 9 in the docs here, but now I can't remember why.  I thought I was breaking something, but maybe I'm not.  Need to double-check.

Nice, "run cycle overview" is much improved

this has gotten too unwieldy and I'm going to try to break it up

I am not going to attempt to break this up, because that's a pain in the ass.  suffice to say there are things in here that could technically be in separate PRs.  I am sorry.

I'm going to assume we're OK with moving deprecate() and warn() into lib/errors from lib/utils.  It is not ideal, but it is problematic to attempt to bundle a cyclic dependency, as utils needed errors and vice-versa.

when AppVeyor passes I'm going to merge this, finally.

I have some ideas around documenting this further, but I can do it in a subsequent PR.

FYI as feedback to help you calibrate semver choices for the future, this was a breaking change for reasons summarized here, and should've gone out in 9.0.0.
Thanks for all your work on this project!


RubyInstaller2 doesn't work with AppVeyor CI environment

AppVeyor is a Windows CI service.
It is working PowerShell based environment.
I've got the following result:
c:/ruby24/bin/ruby extconf.rb
c:/ruby24/lib/ruby/site_ruby/ruby_installer/dll_directory.rb:75:in `add_dll_directory_winapi': AddDllDirectory failed (RubyInstaller::DllDirectory::WinApiError)
	from c:/ruby24/lib/ruby/site_ruby/ruby_installer/dll_directory.rb:46:in `initialize'
	from c:/ruby24/lib/ruby/site_ruby/ruby_installer/msys2_installation.rb:63:in `new'
	from c:/ruby24/lib/ruby/site_ruby/ruby_installer/msys2_installation.rb:63:in `enable_dll_search_paths'
	from c:/ruby24/lib/ruby/site_ruby/ruby_installer.rb:26:in `enable_dll_search_paths'
	from c:/ruby24/lib/ruby/2.4.0/rubygems/defaults/operating_system.rb:7:in `<top (required)>'
	from c:/ruby24/lib/ruby/2.4.0/rubygems.rb:1345:in `require'
	from c:/ruby24/lib/ruby/2.4.0/rubygems.rb:1345:in `<top (required)>'
	from <internal:gem_prelude>:4:in `require'
	from <internal:gem_prelude>:4:in `<internal:gem_prelude>'
rake aborted!

https://ci.appveyor.com/project/cosmo0920/win32-api/build/47/job/ep9h2sw4g17ivb3g#L477

This error is raised if the mingw directory does not exist. It should be c:/msys64/mingw32/bin on appveyor. It is probably caused by %devkit64%\devkitvars.bat , which sets RI_DEVKIT and due to the fact that RI2 considers RI_DEVKIT as the root MSYS2 path .
I think it is better to ignore a previous setting of RI_DEVKIT. There is no need for it. And the error message should contain the failed path.
Can you please try to delete the environment variable set RI_DEVKIT= before the RI2-part on appveyor?

I want to use DevKit1 based Rubies and RI2 Rubies in the same rake task to create universal gem.
Can we use them there?

A predefined RI_DEVKIT does no longer break MSYS detection in RI2.
The use of MSYS1 and MSYS2 in one shell is difficult, because both toolsets contain the same commands in very different versions. You probably have to use either subshells with distinct MSYS1/2 activation or need to switch to MSYS2 for all ruby versions. In case of rake-compiler-dock I choosed the latter way.

Before the next release to github , you can either set RI_DEVKIT= in front of the RI2-part on appveyor or download the latest artifacts from appveyor .

Thanks for explaining the root cause this problem.
I'd acheived to get success building MSYS1 and MSYS2 mixed gem with this commit: https://github.com/cosmo0920/win32-api/commit/b06f5c00fe79b4358c46a7c3f2b0666ca28d05b1
But I feel that this is not straightforward solution.

If the running Ruby interpreter is RI2, then you could use:
  ENV.delete('RI_DEVKIT')
  require "ruby_installer"
  RubyInstaller.enable_msys_apps

But this is bundled with the RubyInstaller2 and so far not available as a separate gem, so that other Ruby versions will fail to require 'ruby_installer' . So if your work-around works for you, then keep it.

I think this issue is solved now.


There should not be an exception if the admin is trying to add a new variant for the configurable product

Bagisto Version: Master
Steps To reproduce--
1. Log in as an admin.
2. Click on products inside the catalog section
3. Edit any configurable product
4. Add a new variant for the product and click on the Save button
Expected result: There should  not be an exception if the admin is trying to add a new variant for the configurable product
Actual result: There is an exception if the admin is trying to add a new variant for the configurable product by editing the configurable. Please find the screenshot Here

@jitendra-webkul
Now, this issue is fixed. And I have attached a screenshot Here, for future reference.


Improved device compilation.

It appears that the compiler is not optimizing some if(false) resulting in 3 kernels (for all kernels) being compiled instead of just 1. This PR wraps the execution policies to avoid this compilation pitfall.
Using make clean; time make pcuda CUDA_ARCH=sm_70 MFEM_USE_BENCHMARK=YES MFEM_USE_CEED=YES -j32 on Lassen:
From:
real	3m5.816s
user	49m39.718s
sys	1m48.213s

To:
real	1m53.853s
user	41m45.493s
sys	1m50.766s

PR
Author
Editor
Reviewers
Assignment
Approval
Merge

#2612
@YohannDudouit
@tzanio
@artv3 + @camierjs + @jandrej
10/16/21
⌛due 10/30/21
⌛due 11/06/21

This PR is now under review (see the table in the PR description). To help with the review process, please do not force push to the branch.

@jandrej I think there is a misunderstanding:
      if (DIM == 1) { return CuWrap1D(N, d_body); }
      if (DIM == 2) { return CuWrap2D(N, d_body, X, Y, Z); }
      if (DIM == 3) { return CuWrap3D(N, d_body, X, Y, Z, G); }

generates 3 GPU kernels, you can see it using the compilation option -Xptxas -v for instance.


pull request for e2e test at 01/01/2017 00:15:09

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

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


Dependabot opens PRs in Hugo forks.

Not sure how this can be fixed but the recent addition of dependabot.yml seems to activate it in Hugo forks.
See the flood of PRs in my fork over here:
https://github.com/onedrawingperday/hugo/pulls
Also there is an open issue about this behavior in the dependabot repo:
https://github.com/dependabot/dependabot-core/issues/2198

Quick and dirty fix: comment @dependabot ignore this dependency on each of the PRs. Quicker and dirtier fix: Block @dependabot from your fork.

Thanks @davidsneighbour will try blocking Dependabot.
Also I will leave this issue open for now. Maybe there will be a fix at some point.

Blocking Dependabot does not work.
Currently they are asking users to delete old forks and then re-create them so the they are upfraded to v2 of dependabot that does not come with this issue! See this: comment
Lots of the 5.3K forks of Hugo were created before v2 of dependabot. Some these have Pull Requests history that users may not want to discard.
I left a comment at the dependabot repo over here but I don't expect a fix anytime soon.


Very slow startup (20-30 seconds)

Issue Type: Performance Issue
Everytime when i want to start VS Code, it takes 20-30 seconds to open. I just remember, i changed a number in the settings to something like<PHONE_NUMBER>99 to load something, but I really can't remember what that was.
Thanks for your help.
VS Code version: Code 1.43.1 (fe22a9645b44368865c0ba92e2fb881ff1afce94, 2020-03-18T07:01:20.184Z)
OS version: Windows_NT x64 10.0.18362

System Info

Item
Value

CPUs
AMD Ryzen 5 2600 Six-Core Processor             (12 x 3400)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_off_okwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
15.96GB (9.51GB free)

Process Argv
C:\Users\daryl\Desktop\AltVServer

Screen Reader
no

VM
0%

Process Info
CPU %	Mem MB	   PID	Process
    0	    77	 14640	code main
    0	    70	 25660	   shared-process
    0	    14	 33936	   electron-crash-reporter
    0	   188	 34292	   window (AltVServer - Visual Studio Code)
    0	    63	 20752	     C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe
    0	     6	 35200	     console-window-host (Windows internal process)
    0	    11	 36208	     watcherService
    0	    11	   564	       console-window-host (Windows internal process)
    0	    80	 36872	     extensionHost
    0	   280	 31436	       electron_node tsserver.js
    0	    46	 35940	         electron_node typingsInstaller.js typesMap.js
    0	    51	 31824	       electron_node tsserver.js
    0	    68	 36824	   window (Issue Reporter)
    0	    25	 37112	   utility
    0	   129	 37208	   gpu-process

Workspace Info
|  Window (AltVServer - Visual Studio Code)
|    Folder (AltVServer): 569 files
|      File types: ymap(63) ydr(62) js(52) ytd(41) ts(34) dmp(32) ydd(26)
|                  cfg(24) mjs(22) ttf(20)
|      Conf files: package.json(1);

Extensions (5)

Extension
Author (truncated)
Version

bracket-pair-colorizer
Coe
1.0.61

prettier-vscode
esb
3.20.0

discord-vscode
icr
3.13.0

discord
Kua
0.0.6

atlv-complete
stu
0.1.3

(2 theme extensions excluded)

Did you try opening your settings in JSON format (settings json file) and searching the file?

To find out if the slow startup is related the settings or any other state, run VSCode with a different user-data-dir: code --user-data-dir c:\\test-user-dir and see if that makes any difference
If that doesn't help, please see https://github.com/microsoft/vscode/wiki/Performance-Issues#visual-studio-code-starts-up-slowly for instructions on how to diagnose the slow startup.

Did you try opening your settings in JSON format (settings json file) and searching the file?

No i didnt how can i do that?

To find out if the slow startup is related the settings or any other state, run VSCode with a different user-data-dir: code --user-data-dir c:\\test-user-dir and see if that makes any difference
If that doesn't help, please see https://github.com/microsoft/vscode/wiki/Performance-Issues#visual-studio-code-starts-up-slowly for instructions on how to diagnose the slow startup.

Where do i have to write code --user-data-dir c:\test-user-dir
In the terminal?

Yes, close all VSCode windows, open a command prompt and start VSCode with
code --user-data-dir c:\test-user-dir

Yes, close all VSCode windows, open a command prompt and start VSCode with
code --user-data-dir c:\test-user-dir

Okay do i have to do test-user-dir or does it not matter in which folder i do that?

:warning: We have copied additional data to your clipboard. Make sure to paste here. :warning:
:warning: Make sure to attach these files from your home-directory: :warning:
-prof-1cb7.extHost.cpuprofile.txt
-prof-1cb7.main.cpuprofile.txt
-prof-1cb7.renderer.cpuprofile.txt

That should help you.
Performance Marks

What
Duration
Process
Info

start => app.isReady
50
[main]
initial startup: true

nls:start => nls:end
1
[main]
initial startup: true

require(main.bundle.js)
60
[main]
initial startup: true

app.isReady => window.loadUrl()
142
[main]
initial startup: true

window.loadUrl() => begin to require(workbench.desktop.main.js)
11048
[main->renderer]
NewWindow

require(workbench.desktop.main.js)
521
[renderer]
cached data: YES, node_modules took 130ms

require & init workspace storage
33
[renderer]
-

init workspace service
36
[renderer]
-

register extensions & spawn extension host
4344
[renderer]
-

restore viewlet
58
[renderer]
workbench.view.explorer

restore panel
0
[renderer]
-

restore editors
4301
[renderer]
1: workbench.editors.files.fileEditorInput

overall workbench load
4483
[renderer]
-

workbench ready
16305
[main->renderer]
-

extensions registered
16474
[renderer]
-


fix parameter "wi"

[fix parameter "wi"]
TokenWaitInfo wi = new TokenWaitInfo();
wi.Handle = ThreadPool.RegisterWaitForSingleObject(
...................................................................................................
if (!timedOut)
{
TokenWaitInfo wi1 = (TokenWaitInfo)state;
if (wi1.Handle != null)
{
wi1.Handle.Unregister(null);
}
}
...................................................................................................
,wi,
(uint)CalculateThreadSleep(accessToken).TotalMilliseconds,
)

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

ID: 80e62a9d-06d0-ebc3-2c99-ce459388182a
Version Independent ID: 07d8b090-b18c-842d-ba1e-0f2b2a127ad3
Content: Using CSOM for .NET Standard instead of CSOM for .NET Framework
Content Source: docs/sp-add-ins/using-csom-for-dotnet-standard.md
Product: sharepoint
GitHub Login: @spdevdocs
Microsoft Alias: spdevdocs

Can you please provide more context around your submission? What's wrong with the existing, what are you changing, etc. Providing updated code with zero context isn't clear...

I run the code from link: https://docs.microsoft.com/en-us/sharepoint/dev/sp-add-ins/using-csom-for-dotnet-standard
see that:

variable "wi" was declared firstly at line:               "TokenWaitInfo wi = new TokenWaitInfo();"
and variable "wi" was declared secondly at line:   "TokenWaitInfo wi = (TokenWaitInfo)state;"
please update for build/running with visual studio 2019.

Oh... so you're saying the code in the doc is incorrect because it overwrites an existing variable? OK... that makes sense.
It helps to explain WHY something is wrong and WHAT you're fixing rather than just submitting code saying "fixes X" :)


⚠ Bofrost.fr has degraded performance

In 50d24d2, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 852 ms

Resolved: Bofrost.fr performance has improved in 0c70aa8.


When logdir=path is not in config file code does not run

When logdir=path is commented out in the config file the follow error is raised and the code does not run.
ValueError: Live feed has no sensor data keys. Can't setup plotting. Try fiddling with the `-wait` parameter.
The config file is shown below.
[sensor.prox]
dtype=int, float
port=COM3
label=Proximity
value_index=2

[port.COM3]
port_baud=115200
port_timeout=0.3
encoding=ASCII
# port_delimeter=\s

[global]
wait=10
buffertime=5
logdir=C:\Users\TNiederhauser\OneDrive - NewVista Property Holdings, LLC\ProxData\test\

I fixed a different issue (making the -wait parameter be an explicit wait time, before which no plotting is done) and it appears to have fixed this issue.


Fixed the Configure method contents

Previously there was no call to app.UseIdentityServer which is necessary to make the example actually work (.well-known endpoint)

Hi @MartinZikmund, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, DNFBOT;


Crash with typed array of objects

Godot version
4.1 beta 2
System information
Godot v4.1.beta2 - Windows 10.0.19045 - Vulkan (Forward+) - dedicated AMD Radeon RX 5700 (Advanced Micro Devices, Inc.; 31.0.14057.5006) - AMD Ryzen 5 2600 Six-Core Processor (12 Threads)
Issue description
I have just changed a filename and the class name associated. Following that Godot crashed (not the first time 4.1 beta 2 crashed on a save actually). However, this time I was not able to load the project again. Godot crashes at load.  There has also been many successful file saves without any issue.
I tried loading the project back in 4.0.3 (there's no vital component that are dependent on downgrade and upgrade so far in the project afaik) and it works perfectly and the classes are functional and working.
Steps to reproduce
I unfortunately don't even have the slightest idea what triggered the bug. It might very well be a documented bug but since I'm basically left with no clue all I can do is link my project and a screen of the log at crash :

I did confirm by running in the Command Prompt that no further bugs were reported. I can try uploading a log but I can't seem to be able to redirect Godot's output to a log file during the project load. No log file is generated in the project's normal log folder either (all are dated hours before from now)
Minimal reproduction project
FlickGame_repro.zip

I can reproduce the crash with the MRP. Errors and GDB backtrace:
WARNING: res://addons/proton_scatter/demos/assets/materials/m_bush.tres:4 - ext_resource, invalid UID: uid://b2a6ylo2enm4g - using text path instead: res://addons/proton_scatter/demos/assets/textures/t_bush.png
     at: load (./scene/resources/resource_format_text.cpp:447)
ERROR: Attempted to push_back an object into a TypedArray, that does not inherit from 'GDScript'.
   at: validate_object (./core/variant/container_type_validate.h:139)
ERROR: Condition "!_p->typed.validate(value, "push_back")" is true.
   at: push_back (./core/variant/array.cpp:269)
ERROR: FATAL: Index p_index = 253 is out of bounds (((Vector<T> *)(this))->_cowdata.size() = 252).
   at: operator[] (./core/templates/vector.h:52)

Thread 1 "godot-git" received signal SIGILL, Illegal instruction.
0x000000000570b4e3 in VectorWriteProxy<Variant>::operator[] (this=0x1fed9fd8, p_index=253) at ./core/templates/vector.h:52
52                      CRASH_BAD_INDEX(p_index, ((Vector<T> *)(this))->_cowdata.size());

(gdb) bt
#0  0x000000000570b4e3 in VectorWriteProxy<Variant>::operator[] (this=0x1fed9fd8, p_index=253) at ./core/templates/vector.h:52
#1  0x000000000a28c9d8 in Array::operator[] (this=0x7fffffffb160, p_idx=253) at ./core/variant/array.cpp:89
#2  0x000000000a28ecb4 in Array::set (this=0x7fffffffb160, p_idx=253, p_value=...) at ./core/variant/array.cpp:415
#3  0x0000000008ec408d in SceneState::instantiate (this=0x1e02d020, p_edit_state=SceneState::GEN_EDIT_STATE_INSTANCE) at ./scene/resources/packed_scene.cpp:483
#4  0x0000000008ed0142 in PackedScene::instantiate (this=0x1ab9f920, p_edit_state=PackedScene::GEN_EDIT_STATE_INSTANCE) at ./scene/resources/packed_scene.cpp:1932
#5  0x0000000008ec1cf8 in SceneState::instantiate (this=0x1cb5ac80, p_edit_state=SceneState::GEN_EDIT_STATE_MAIN) at ./scene/resources/packed_scene.cpp:172
#6  0x0000000008ed0142 in PackedScene::instantiate (this=0x213594e0, p_edit_state=PackedScene::GEN_EDIT_STATE_MAIN) at ./scene/resources/packed_scene.cpp:1932
#7  0x0000000007485759 in EditorNode::load_scene (this=0xe0370a0, p_scene=..., p_ignore_broken_deps=false, p_set_inherited=false, p_clear_errors=true, p_force_open_imported=false, p_silent_change_tab=false)
    at ./editor/editor_node.cpp:3721
#8  0x000000000746b78a in EditorNode::_sources_changed (this=0xe0370a0, p_exist=false) at ./editor/editor_node.cpp:1062
#9  0x00000000076c3a24 in call_with_variant_args_helper<EditorNode, bool, 0ul> (p_instance=0xe0370a0, p_method=(void (EditorNode::*)(EditorNode * const, bool)) 0x746b642 <EditorNode::_sources_changed(bool)>,
    p_args=0x7fffffffcaf0, r_error=...) at ./core/variant/binder_common.h:303
#10 0x00000000076b3470 in call_with_variant_args<EditorNode, bool> (p_instance=0xe0370a0, p_method=(void (EditorNode::*)(EditorNode * const, bool)) 0x746b642 <EditorNode::_sources_changed(bool)>, p_args=0x7fffffffcaf0,
    p_argcount=1, r_error=...) at ./core/variant/binder_common.h:417
#11 0x000000000769eeb0 in CallableCustomMethodPointer<EditorNode, bool>::call (this=0x1c9740c0, p_arguments=0x7fffffffcaf0, p_argcount=1, r_return_value=..., r_call_error=...) at ./core/object/callable_method_pointer.h:104
#12 0x000000000a291317 in Callable::callp (this=0x210701b0, p_arguments=0x7fffffffcaf0, p_argcount=1, r_return_value=..., r_call_error=...) at ./core/variant/callable.cpp:50
#13 0x000000000a5a6e83 in Object::emit_signalp (this=0xe0dc0a0, p_name=..., p_args=0x7fffffffcaf0, p_argcount=1) at ./core/object/object.cpp:1068
#14 0x000000000834dc5d in Node::emit_signalp (this=0xe0dc0a0, p_name=..., p_args=0x7fffffffcaf0, p_argcount=1) at ./scene/main/node.cpp:3570
#15 0x000000000683de90 in Object::emit_signal<bool> (this=0xe0dc0a0, p_name=...) at ./core/object/object.h:881
#16 0x000000000729482b in EditorFileSystem::_notification (this=0xe0dc0a0, p_what=17) at ./editor/editor_file_system.cpp:1284
#17 0x0000000007341754 in EditorFileSystem::_notificationv (this=0xe0dc0a0, p_notification=17, p_reversed=false) at ./editor/editor_file_system.h:146
#18 0x000000000a5a50e1 in Object::notification (this=0xe0dc0a0, p_notification=17, p_reversed=false) at ./core/object/object.cpp:796
#19 0x0000000008353d07 in SceneTree::_process_group (this=0xe019fd0, p_group=0xe01a220, p_physics=false) at ./scene/main/scene_tree.cpp:947
#20 0x00000000083542c3 in SceneTree::_process (this=0xe019fd0, p_physics=false) at ./scene/main/scene_tree.cpp:1027
#21 0x0000000008351f72 in SceneTree::process (this=0xe019fd0, p_time=0.13333333333333286) at ./scene/main/scene_tree.cpp:504
#22 0x00000000056f6800 in Main::iteration () at main/main.cpp:3425
#23 0x0000000005670cda in OS_LinuxBSD::run (this=0x7fffffffcff0) at platform/linuxbsd/os_linuxbsd.cpp:912
#24 0x0000000005667f80 in main (argc=2, argv=0x7fffffffd5d8) at platform/linuxbsd/godot_linuxbsd.cpp:74

And it also seems to not be platform dependent, based on your backtrace I assume you're running Godot in Linux ?
Using the renamed title I was able to just remove the script (ProgrammableRBComponent) using a typed array from the RigidBody it was attached to by using 4.0.3. This resulted in the project being loadable again in 4.1 beta 2. I won't need that for a few but I assume me renaming and reorganizing some of the things may have messed with the resource IDs of the script related to the array type ?
In all case thanks for the reactivity, the backtrace and title helped me get the project runnable in 4.1 beta 2 again.

The crash is fixed by #77735. For the other error all I could say is that it is caused by the parser error which resulted in a null script. Unfortunatly I'm not too familiar with GDScript loading so I can't tell much more what is happening here.

The null script makes sense as these were scripts I was actively working on. I was expecting to have to reaffect the nodes to their variables at some point. Glad this could be fixed.

I debug this using latest godot and reproduce the crash.
Here is the backtrace
__GI_raise 0x00007ffff7c6300b
__GI_abort 0x00007ffff7c42859
handle_crash crash_handler_linuxbsd.cpp:141
<signal handler called> 0x00007ffff7c63090
VectorWriteProxy::operator[] vector.h:52
Array::operator[] array.cpp:89
Array::set array.cpp:415
SceneState::instantiate packed_scene.cpp:483
PackedScene::instantiate packed_scene.cpp:1932
SceneState::instantiate packed_scene.cpp:172
PackedScene::instantiate packed_scene.cpp:1932
EditorNode::load_scene editor_node.cpp:3721
EditorNode::_load_open_scenes_from_config editor_node.cpp:5333
EditorNode::_load_editor_layout editor_node.cpp:4974
EditorNode::_sources_changed editor_node.cpp:1058
call_with_variant_args_helper<…> binder_common.h:303
call_with_variant_args<…> binder_common.h:417
CallableCustomMethodPointer::call callable_method_pointer.h:104
Callable::callp callable.cpp:50
Object::emit_signalp object.cpp:1068
Node::emit_signalp node.cpp:3570
Object::emit_signal<…> object.h:881
EditorFileSystem::_notification editor_file_system.cpp:1284
EditorFileSystem::_notificationv editor_file_system.h:146
Object::notification object.cpp:796
SceneTree::_process_group scene_tree.cpp:939
SceneTree::_process scene_tree.cpp:1019
SceneTree::process scene_tree.cpp:504
Main::iteration main.cpp:3420
OS_LinuxBSD::run os_linuxbsd.cpp:912
main godot_linuxbsd.cpp:74
__libc_start_main 0x00007ffff7c44083
_start 0x0000555557fea27e

Here is my analyze
And I find the code from godot/scene/resources/packed_scene.cpp if array.size() >= index
		if (string_property.contains("/indices/")) {
			// For properties with "/indices/", the replacement takes place inside an Array.
			const String base_property = string_property.get_slice("/", 0);
			const int index = string_property.get_slice("/", 2).to_int();

			bool valid;
			Array array = dnp.base->get(base_property, &valid);
			ERR_CONTINUE(!valid);

                        // ---> This code looks wrong, the if condition changes to index >= array.size() look more reasonable
			if (array.size() >= index) {
				array.push_back(other);
			} else {
				array.set(index, other);
			}

			dnp.base->set(base_property, array);
		}

Before the index < 253, it is always same with array.size(), so the crash location is the index = 253


[#1260] Connection status information

QA Instructions:

Start scoping the process.
Inspect the scoped process

scope inspect <SCOPED_PROCESS_PID>

Example interface section:
   "interfaces": [
      {
         "name": "log",
         "connected": true,
         "config": "file:///tmp/scope.log"
      },
      {
         "name": "cribl",
         "connected": false,
         "config": "edge",
         "attempts": 4
      }
   ]

The output should reflect the used configuration and the current status of the connection.
Please use different configurations to verify that all cases are covered.
Ref: #1260

For testing, I ran each of the scenarios (#1 through #3) from https://github.com/criblio/appscope/issues/1260 twice.
The first time I enabled payloads by setting SCOPE_PAYLOAD_ENABLE=true.  The second time I enabled payloads by adding a protocol definition with payload: true.
All tests passed.

I've re-reviewed this PR after the last ("Fix memory leak in ctlDestroy") commit.  As a comment: I've diligently been reviewing @michalbiesek's changes in this PR, and he's been doing the same level of review for my commits.  Merging now.


Azure Core for Java (October 2021)

This contains all issues we plan to resolve by the end of the October 2021 release cycle. Additionally, this contains stretch goal issues which may be resolved in the release cycle.
Partner Requests
Reliability
Performance Enhancements
Supportability
Stretch Goals

Closing as October release has been completed.


save locally and call api /sessionleave instead of using firebase database

The puzzle 9-e42e0be6 from #9 has to be resolved:
https://github.com/ammaratef45/Attendance/blob/6458784661c60ff240bc92347d7306a070af4ac8/attendance/lib/AttendanceDatailsPage/attendance_details_page_viewmodel.dart#L61-L61
The puzzle was created by Ammar Atef on 16-Apr-19.
If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.

@ammaratef45/z please, pay attention to this issue

The job #51 assigned to @ammaratef45/z, here is why; the budget is 30 minutes, see §4; please, read §8 and §9; if the task is not clear, read this and this; there will be no monetary reward for this job

Manual assignment of issues is discouraged, see §19: -5 point(s) just awarded to @ammaratef45/z

@ammaratef45/z this job was assigned to you 5days ago. It will be taken away from you soon, unless you close it, see §8. Read this and this, please.

@ammaratef45/z please, pay attention to this issue

GitHub issue is still open, won't close

@0crat wait

@0crat wait (here)

@ammaratef45 The impediment for #51 was registered successfully by @ammaratef45/z

The puzzle 9-e42e0be6 has disappeared from the source code, that's why I closed this issue.

@0pdd 3 puzzles #59, #60, #61 are still not solved.

The job #51 is now out of scope

Order was finished: +30 point(s) just awarded to @ammaratef45/z

@0pdd 2 puzzles #105, #98 are still not solved; solved: #59, #60, #61.


Establishing order on the EditorConfig front

Currently the repository deviates from EditorConfig settings. (checked with eclint)
Would you welcome global 4-space indenting?
🍇 Much better readability 🍇

I'm new to the Go ecosystem.

Again, in Golang, Use spaces only if you must. Tabs for indentation is the official recommendation.

They want the typewriter back 🙃


Modify permissions from 644 to 755

Git can track executable (0755) and non-executable (0644) file modes. This changes possible shell scripts and files, that could be executed on the command line, to be tracked as executables in Git.
Related to #211

@petk
Thanks for the patch!


Work around subprocess.call() issue on Windows

On POSIX-like systems, calling subprocess.call() with both shell=True and executable='...' has the following behavior:

If shell=True, on POSIX the executable argument specifies a replacement shell for the default /bin/sh.

(via https://docs.python.org/3/library/subprocess.html?highlight=subprocess#popen-constructor)
This seems to have a similar behavior on Windows, but this is problematic when a POSIX shell is substituted for cmd.exe. This is because when shell=True, the shell is invoked with a '/c' argument, which is the correct argument for cmd.exe but not for Bash, which expects a '-c' argument instead. See here: https://github.com/python/cpython/blob/1def7754b7a41fe57efafaf5eff24cfa15353444/Lib/subprocess.py#L1407
This is problematic when combined with Dotbot's behavior, where the executable argument is set based on $SHELL. For example, when running in Git Bash, the $SHELL environment variable is set to Bash, so any commands run by Dotbot will fail (because it'll invoke Bash with a '/c' argument).
This behavior of setting the executable argument based on $SHELL was introduced in 7593d8c13479b382357be065c7bf51562a130660. This is the desired behavior. See discussion in https://github.com/anishathalye/dotbot/issues/97 and https://github.com/anishathalye/dotbot/pull/100.
Unfortunately, this doesn't work quite right on Windows. This patch works around the issue by avoiding setting the executable argument when the platform is Windows, which is tested using platform.system() == 'Windows'. This means that shell commands executed by Dotbot on this platform will always be run using cmd.exe. Invocations of single programs or simple commands will probably work just fine in cmd.exe. If Bash-like behavior is desired, the user will have to write their command as bash -c '...'.
This shouldn't have any implications for backwards-compatibility, because setting the executable argument on Windows didn't do the right thing anyways. Previous workarounds that users had should continue to work with the new code.
When using Python from CYGWIN, platform.system() returns something like 'CYGWIN_NT-...', so it won't be detected with the check, but this is the correct behavior, because CYGWIN Python's subprocess.call() has the POSIX-like behavior.
This patch also refactors the code to factor out the subprocess.call(), which was being called in both link.py and shell.py, so the workaround can be applied in a single place.
See the following issues/pull requests for a discussion of this bug:

https://github.com/anishathalye/dotbot/issues/170
https://github.com/anishathalye/dotbot/pull/177
https://github.com/anishathalye/dotbot/issues/219

An issue has also been raised in Python's issue tracker:

https://bugs.python.org/issue40467

Thanks to @shivapoudel for originally reporting the issue, @SuJiKiNen for debugging it and submitting a pull request, and @mohkale for suggesting factoring out the code so that other plugins could use it.

I think omitting the executable arg on Windows is a decent workaround to the problem. I'm not really sure if there's a better fix for this (maybe the Python developers will have some ideas in https://bugs.python.org/issue40467).
Some commands will probably work without an extra bash -c "....", and if Bash behavior is desired, that doesn't seem too bad to include in the install.conf.yaml.

@anishathalye I got some time today and go through this PR for test and it patches the bug.

Thanks!
I will wait a bit longer in case anyone else has feedback, and then I'll merge.


Zero-shot inference with t-few does not produce the scores and inferences

Hi @stefanhgm,
I am able to run the t-few code to infer all the datasets with any number of shots except 0 shot. Following your instruction, I changed the num_shot to 0 in the .sh file to run the pl_train.py but the output experiment folder does not contain the supposed dev_scores.json and the inferences. It works for the other shots, the issue only happens for zero-shot. I've attached the terminal output when the code is run for your reference.

Hello @hansfarrell,
I am very sorry for coming back to you so late. Still it is a bit difficult your problem with these information. I checked the zero-shot case again and here is my minimal bin/few-shot-pretrained-100k.sh file for income and t03b working for me:
#!/bin/bash
allow_skip_exp=True
eval_before_training=True
balanced_ibc=True

train_batch_size=4
grad_accum_factor=1

lr=0.003
re='^[0-9]+$'

cuda_device=0

# Set adaptively
num_steps=0
eval_epoch_interval=0

for model in 't03b' # 't03b'
do
  # For zero-shot set to '0', for all to 'all'
  for num_shot in 0
  do
    # Datasets: car, income, heart, diabetes, jungle, bank, blood, calhousing, creditg, jungle
    for dataset in income
    do
      # Zero-shot
      eval_before_training=True
      num_steps=0
      # Few-shot
      # [...]

      for seed in 42
      do
      # Print the command to run
      # [...]
      # Run the command
        CUDA_VISIBLE_DEVICES=${cuda_device} CONFIG_PATH=/root/t-few/configs HF_HOME=/root/.cache/huggingface \
        python -m src.pl_train -c ${model}.json+ia3.json+global.json -k dataset=${dataset} load_weight="pretrained_checkpoints/${model}_ia3_finish.pt" num_steps=${num_steps} num_shot=${num_shot} \
        exp_name=${model}_${dataset}_numshot${num_shot}_seed${seed}_ia3_pretrained100k few_shot_random_seed=${seed} seed=${seed} allow_skip_exp=${allow_skip_exp} eval_before_training=${eval_before_training} eval_epoch_interval=${eval_epoch_interval} \
        batch_size=${train_batch_size} grad_accum_factor=${grad_accum_factor} lr=${lr}
      done
    done
  done
done

The output looks as follows and I also get the file dev_scores.json in the directory exp_out/t03b_income_numshot0_seed42_ia3_pretrained100k/:

Validation sanity check: 100%|████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████| 611/611 [01:05<00:00,  5.97it/s]{"AUC": 0.7616058157520148, "PR": 0.4978171030717906, "micro_f1": 0.2939911966424404, "macro_f1": 0.2707494088356843, "accuracy": 0.2939911966424404, "num": 9769, "num_steps": -1, "score_gt": 0.41221203334451834, "score_cand": 0.3321806071468185}


preview not working?

Describe the bug
The preview is not displaying anything. Is there an issue with some versions of chrome? I'm using a chrome book.
Link to the Bolt URL that caused the error
https://bolt.new/~/sb1-sqef8q
Steps to reproduce
click the preview tab
Expected behavior
no preview, just a white page
Screen Recording / Screenshot
No response
Platform
Browser name = Chrome
Full version = <IP_ADDRESS>
Major version = 130
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (X11; CrOS x86_64 14541.0.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
performance.memory = {
  "totalJSHeapSize": 61077026,
  "usedJSHeapSize": 54992150,
  "jsHeapSizeLimit":<PHONE_NUMBER>
}
Username = iambutler
Chat ID = f0a66a985f3f

Additional context
No response

Appreciate the feedback! We are aware of this issue and are tracking it here.


Update virtual-machines-linux-remote-desktop.md

Made some grammatical changes.

Hi @jinmiaoms, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no contribution license agreement is required at this point. Real humans will now evaluate your PR.

TTYL, AZPRBOT;

@SuperScottz
Please review and approve or disapprove this pull request with a comment here. Thanks.

@superscottz
Please review this pull request and approve or disapprove with a comment here. Thanks.

@jinmiaoms This request has merge conflicts.  Would you please fix the merge conflict?

I have created another pull request to merge the change from this one, let's close this.
https://github.com/Azure/azure-content-pr/pull/15636
@jinmiaoms Thank you for decent feedback!


not working

Windows 10
DK2
Leapmotion
installed prerequsits not sure if i had to install when steam vr was not running so closed steam vr and reinstalled tried installing all in order 1-4 after uninstalling just 4 that i had orignally installed. using latest orin drivers
https://youtu.be/R-lBBqB1SXc?t=221 here is a video of my trying to get it to run. its kind of frustrating

Try alpha version #3, as #4 has a known bug with spaces in the path name to the steam install directory. Currently vacationing with no access to a PC, sorry.
Von meinem iPhone gesendet

Am 01.06.2016 um 13:39 schrieb nntb<EMAIL_ADDRESS>Windows 10
DK2
Leapmotion
installed prerequsits not sure if i had to install when steam vr was not running so closed steam vr and reinstalled tried installing all in order 1-4 after uninstalling just 4 that i had orignally installed. using latest orin drivers
https://youtu.be/R-lBBqB1SXc?t=221 here is a video of my trying to get it to run. its kind of frustrating
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Same issue here, I have tried everything reinstalling steam multiple times in different locations, as well as steamvr, and have tried all 4 releases, at one point I got it to work on release #2 but then I broke it
and never was able to replicate it, when I run the script via prompt, it says it has not detected the steam directory
But anyways enjoy your vacation man dont worry about us :)

Same issue here, I have tried everything reinstalling steam multiple times in different locations, as well as steamvr, and have tried all 4 releases, at one point I got it to work on release #2 but then I broke it
and never was able to replicate it, when I run the script via prompt, it says it has not detected the steam directory
But anyways have a nice vacation man dont worry about us :)

I've tried to download the last few releases. Chrome and Adaware have both deleted/quarantined the zip and installed driver. Maybe its affecting others as well.

in my orignal post i mentioned i installed and tryed 1 - 4 in order. so i tried 1 then i tried 2 then 3 then 4 but initaly i tried 4
i did this with steam vr normal, steam vr beta, installing VIVE drivers *(eventhough i dont have a vive)
i dont have a hydra do i need hydra drivers?
its sad these drivers just dont seem to work for me at all.

when i say not working i mean ill start steam vr and there is no indication of motion controllers detected.
leap motion
firmware version is 1.7.0
software version 3.1.2+40841

In my case windows 10 had missing the "32bi Visual C++ 2015 Update 2 redistributables" . 64Bit was already there. You should check this first in apps section of win10.

Alpha 4 didn't work for me, Alpha 3 did. I'm not sure why though, there aren't spaces in my steam dirs. Just D:\Valve\Steam\ and D:\Valve\Steam\steamapps\common\SteamVR

Tried alpha 5. But still doesn't work for me - Alpha 3 is the lastest version that worked for me.

Same - vrpathreg for 4 and 5 displayed the install folder but not the
/leap/ folder inside, if that helps.
On 4 June 2016 at 20:19, Thomas<EMAIL_ADDRESS>wrote:

Tried alpha 5. But still doesn't work for me - Alpha 3 is the lastest
version that worked for me.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/cbuchner1/driver_leap/issues/2#issuecomment-223773177,
or mute the thread
https://github.com/notifications/unsubscribe/ASzdEvmjjaDLdEFe8CEL-qfel9yRQKxrks5qIc_LgaJpZM4IrgC6
.

got mine to work i had to edit the register driver cmd file
i changed %steamdir% to my dir for steam that had the folder of openvr steamvr for me it was E:\steamapps\
after running it worked. i tried running a game but the framrate is awfull. (my fault for having a gtx 670
https://www.twitch.tv/nntb/v/70363829 here you can see me trying to set it up (8 mins in i got the hands working but the game crashes as i load it) i am sure i just need a better system. but yeah got it up and running! thanks

i forgot to close my issue... sorry i am new to this.


[META] 3.0.0-pre.0

I'm sorry, I would have just gotten to these but I've been really slammed. This is just a list of what I'd like to resolve before cutting 3.0.0-pre.0.

[x] Put routes on context.router (and inject in withRouter)
[ ] Move out ContextUtils into a separate library (I've already name-squatted react-context-subscriber)
[x] Figure out if we can avoid calling createRouterObject on both https://github.com/reactjs/react-router/blob/17a362556f49f780a585f7ef6fcbe79b4311307e/modules/Router.js#L86 and https://github.com/reactjs/react-router/blob/17a362556f49f780a585f7ef6fcbe79b4311307e/modules/Router.js#L94

For the createRouterObject issue, why did we go with wrapping up location and params into router before putting it on context? As implemented, it seems pretty messy to me, particularly around the identity maintenance.
Here's the question I'm asking in my head: Do we need the location and params wrapped up into router somewhere where context isn't involved? It seems like either those values (or some form of state) is available whenever it gets passed around. So, we're moving them up higher in the composition, but with bad side-effects that make the code at that level less clear (because it's tied to effects in other parts of the code).

We were maintaining the identity of the router object anyway, and it avoids doing something a lot messier to get context.router to update in <Link>.
We don't need those to be on router where context isn't involved, but it seems like less to keep track of if we don't have some weird rule that "props.router in a router context doesn't have params and location, but only context.router does".

OK, not a huge deal then. I just see a new dep and start to pump the brakes at little bit.
Anyways, it should be fixed by #3446.
For putting route on context, we need a RouteContext don't we? (not the mixin)

routes, not route
I just want context.router and withRouter to be as symmetric as possible to route components, which all receive routes, location, and params.

Threw that into #3446 for you.

@timdorr Thanks. I'll take care of that last bit either tomorrow or Thursday. Sorry this has been taking so long.

@taion if there's anything I can do to help, happy to lend a hand 😄

I'll have some time to look at this today or tomorrow. Sorry for the delay.

Not trying to rush you, just checking if any help is needed

Can we release a prerelease before pulling that code out? It’s an implementation detail so we can do it later at an RC stage. I’m going to need that version for a workshop I’ll be running soon, so it would be great if we could get it out.

I'll cut the prerelease today either way. Sorry it's taken so long.

No problem, and thank you for all your help!

Okay, given the caveats with ContextUtils, let's leave it in here for now to make iterating on it easier. I still want to pull it out before we cut 3.0.0-final, but it's likely just going to be more effort for everyone involved if we pull it out at this point.
This seems on the surface inconsistent with how we're handling things like scroll behavior and relative links, but the difference is that this isn't actually a modular add-on but instead a core dependency.

BTW, going forward, let's merge instead of cherry-pick onto next. I know it makes the commit history sort of ugly, but actually git bisect deals with this sort of thing now, and it just makes it easier to keep the branches in sync (since you can just do git merge master from next).

Ahh, it has to be an alpha because of the alphabet. Oops.

v3.0.0-alpha.1 is out. Sorry again it was blocked for so long on me.

I think I found all the PRs for the changelog, but let me know if I missed anything: https://github.com/reactjs/react-router/commit/5832f2a254c489a0f81f9c6a54188c4247a0570c


fix: use open-rpc client-js instead of Jayson

fixes #123
fixes #96

:tada: This PR is included in version 1.7.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


INT type constraint not working with HF

argmax
    'A number: [N]'
from
    'gpt2-large'
where
    INT(N) and len(N) < 3

The above example is copied directly from the documentation except it has been modified to use gpt2-large instead of the OpenAI API and I'm using a length requirement. When I run it, I get the following error: ValueError: invalid literal for int() with base 10: '  '. Running this without the length requirement just seems to run forever.

Thanks for reporting this. This seems to be an issue with the recently introduced post processing semantics, where the value is converted to a Python int().

This should be fixed on 'main' and will be part of the next release.


Creating a docker-compose.yml file

Is your feature request related to a problem? Please describe.
Currently it is not easy to setup the API's/project on new desktop/server.
Describe the solution you'd like
Creating a docker-compose.yml file to make it easy to setup and run the application.
Additional context
Click here for a article on how to make a Docker-compose to group container and services
Official Docs
Note: Create PR to feature/backend-node

hi can you please assign to me

hi can you please assign to me

Sure

@ArpitKotecha hello should i create the file in which branch ?

@ArpitKotecha hello should i create the file in which branch ?

@Aju100 Create file in feature/backend-node branch.

thank u @ArpitKotecha

@Aju100 Any update on the issue?

Can i work on this issue..

Can i work on this issue..

@viveksahu26 yes

Thank you..@ArpitKotecha .

@ArpitKotecha  in which repository  to add Dockerfile and docker-compose.yml.

@ArpitKotecha  in which repository  to add Dockerfile and docker-compose.yml.

Make a PR to feature/backend-node branch in current repository.

Ok..

@ArpitKotecha please help me in setting up the project so that I have to only work on dockerfile and docker- compose file.. I am beginner , guide me and I will do it..


Slanted Menu CSS Animation

Describe the project you want to add with tech stack
I would like add a CSS Animation about a Slanted Menu Design.
Expected behavior

Interactive
Responsive
Eye-Catchy

Screenshots (optional)

Additional context (optional )

@MohitGupta121 @TusharKesarwani sir kindly assign this issue


Added "socketplane agent restart" (issue - enhancement #82)

Related to #82
Adds a restart to the socketplane agent command...
e.g.,
socketplane agent restart
Signed-off-by: John Willis<EMAIL_ADDRESS>

Dang... will fix

Third time's a charm.. #90 should have it right...


pull request for e2e test at 01/01/2017 06:26:08

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

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


Show tag name when detached status if possible

Moved from: #3
I cleaned the commits so the pr was closed automatically.


Why is it different from the implementation in the paper 'Weakly Supervised Approach for Joint Object and Lane Marking Detection'

Why is it different from the implementation in the paper 'Weakly Supervised Approach for Joint Object and Lane Marking Detection'？

Thank you for your comment. The codes in this repository go back to 2 years before the paper that you just mentioned :)

Thank you for your reply. May I ask where the code for this paper is?:)

芥末
@.***

------------------ 原始邮件 ------------------
发件人: "Soroosh Tayebi @.>;
发送时间: 2023年7月24日(星期一) 晚上7:24
收件人: @.>;
抄送: @.>; @.>;
主题: Re: [tayebiarasteh/lane-detection] Why is it different from the implementation in the paper 'Weakly Supervised Approach for Joint Object and Lane Marking Detection' (Issue #1)
Thank you for your comment. The codes in this repository go back to 2 years before the paper that you just mentioned :)
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>


docs: Update CLI options

Follow changes in #31 and #85

Thank you! Could you add a changeset per the comment above, since the README of the published package is what shows on npmjs.com?

Added the changeset and squashed commit again!
This is my first experience for using changeset. I didn't know the toolset.
Could you check again? 🙏

Thank you!
And thank you for this project. This helped me a lot in understanding how to test package behavior in octokit/graphql-schema#925 🙏
Initially, I was fighting with npm link.


It would be nice to describe the return value of SaveChanges()

[Enter feedback here]

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

ID: 635ce96a-7f29-7fcb-b007-4685cef0499b
Version Independent ID: 6999fa37-7550-6bc6-678f-1a4fb33d2101
Content: DbContext.SaveChanges Method (Microsoft.EntityFrameworkCore)
Content Source: dotnet/xml/Microsoft.EntityFrameworkCore/DbContext.xml
Product: entity-framework-core
GitHub Login: @dotnet-bot
Microsoft Alias: divega

It is already there:
<returns>
                The number of state entries written to the database.
            </returns>

The issue turns out to be in docs rendering/generation tool (there are probably 2-3 different bugs. They are being tracked internally.
Work-around is to remove indentation in the EcmaXML. This issue happens for every returns in XML doc which uses multiple lines. I will do it alongwith #2748 after 5.0 API docs are also added to the repo.

See https://github.com/dotnet/EntityFramework.ApiDocs/pull/82

Turns out issue with returns was a legacy issue which was already fixed. We never live site using fixed code. Docs team did force rebuild on live branch. Now all returns are correctly rendered.


8 errors while debugging new react native app Execution failed for task ':app:compileDebugJavaWithJavac'. - React Native

8 errors :app:compileDebugJavaWithJavac FAILED
What went wrong: Execution failed for task ':app:compileDebugJavaWithJavac'.
Compilation failed; see the compiler error output for details.
But old apps are running on my machine, win 8.1 (64) Bit
:app:compileDebugJavaWithJavac - is not incremental (e.g. outputs have changed, no previous execution, etc.). F:\React2\appwn\android\app\src\main\java\com\appwn\MainApplication.java:5: error: cannot find symbol import com.facebook.react.ReactApplication; ^ symbol: class ReactApplication location: package com.facebook.react F:\React2\appwn\android\app\src\main\java\com\appwn\MainApplication.java:6: error: cannot find symbol import com.facebook.react.ReactNativeHost; ^ symbol: class ReactNativeHost location: package com.facebook.react F:\React2\appwn\android\app\src\main\java\com\appwn\MainApplication.java:14: error: cannot find symbol public class MainApplication extends Application implements ReactApplication { ^ symbol: class ReactApplication F:\React2\appwn\android\app\src\main\java\com\appwn\MainApplication.java:16: error: cannot find symbol private final ReactNativeHost mReactNativeHost = new ReactNativeHost(this) { ^ symbol: class ReactNativeHost location: class MainApplication F:\React2\appwn\android\app\src\main\java\com\appwn\MainApplication.java:36: error: cannot find symbol public ReactNativeHost getReactNativeHost() { ^ symbol: class ReactNativeHost location: class MainApplication F:\React2\appwn\android\app\src\main\java\com\appwn\MainActivity.java:5: error: MainActivity is not abstract and does not override abstract method getPackages() in ReactActivity public class MainActivity extends ReactActivity { ^ F:\React2\appwn\android\app\src\main\java\com\appwn\MainApplication.java:16: error: cannot find symbol private final ReactNativeHost mReactNativeHost = new ReactNativeHost(this) { ^ symbol: class ReactNativeHost location: class MainApplication F:\React2\appwn\android\app\src\main\java\com\appwn\MainApplication.java:35: error: method does not override or implement a method from a supertype @Override ^ 8 errors :app:compileDebugJavaWithJavac FAILED
FAILURE: Build failed with an exception.
What went wrong: Execution failed for task ':app:compileDebugJavaWithJavac'.
Compilation failed; see the compiler error output for details.
Try: Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.
BUILD FAILED

Execution failed for task ':app:compileDebugJavaWithJavac'


Api key required

Describe the bug
Not really a bug, I just need help. When the start function is executed, a toast notify that an api key is required and to check the log. The log states that it's impossible to connect to the service. I suppose it needs google speech recognition api key. If so, once I obtain the key, how do i use it?
Smartphone (please complete the following information):

Device: [Honor 9]
OS: [Android 9]

The plugin doesn't require an API key, the speech recognition is supposed to be provided by the OS.
Most devices will rely on installed google apps for the speech recognition, but for Chinese vendors that don't include google apps, you might need additional setup. I can't find any information about what might be required for honor devices, try opening stock honor apps that might have speech recognition enabled and see if it popups something.


motion masks - do they auto refresh

I have made a right click context menu to convert and upload motion masks.....
Assuming the filename is the same as that defined in the configs/menu; do i need to tell RPCWI to update the mask?
Reboot?
stop/start motiondetection?
Or will it automatically use the new file without me doing anyhting?

The motion mask file is loaded and activated whenever the camera set up is 'started'.
This happens when the overall software is first started and when particular commands are used which require fundamental changes to the set up.
These include the following commands px, qp, pv, bi, ru, md, rs, vp, cn. (See command summary on schedule page).
In summary just loading a new file or changing the file name will not trigger it to be used, but starting motion detection will cause it to be refreshed.

The motion mask file is loaded and activated whenever the camera set up is 'started'.
This happens when the overall software is first started and when particular commands are used which require fundamental changes to the set up.
These include the following commands px, qp, pv, bi, ru, md, rs, vp, cn. (See command summary on schedule page).
In summary just loading a new file or changing the file name will not trigger it to be used, but starting motion detection will cause it to be refreshed.

I must be doing something wrong:
In light of what you said above it would be useful to toggle the md off and then back on again to refresh the mask image. Iv'e tried a few variants like these, but I'm getting no output from FIFO, and no reaction from the browser interface button (after i refresh it)
What's wrong with my syntax/permissions?
printf "%s\n" "md 0" >/var/www/html/FIFO1
printf "%s\n" "md 1" >/var/www/html/FIFO1

printf "%s\n" "md=0" >/var/www/html/FIFO1
printf "%s\n" "md=1" >/var/www/html/FIFO1

echo "md 0" >/var/www/html/FIFO1
echo "md 1" >/var/www/html/FIFO1

echo "md=0" >/var/www/html/FIFO1
echo "md=1" >/var/www/html/FIFO1

I'll be doing this via ssh as part of the mask upload script.

I must be doing something wrong:
In light of what you said above it would be useful to toggle the md off and then back on again to refresh the mask image. Iv'e tried a few variants like these, but I'm getting no output from FIFO, and no reaction from the browser interface button (after i refresh it)
What's wrong with my syntax/permissions?
printf "%s\n" "md 0" >/var/www/html/FIFO1
printf "%s\n" "md 1" >/var/www/html/FIFO1

printf "%s\n" "md=0" >/var/www/html/FIFO1
printf "%s\n" "md=1" >/var/www/html/FIFO1

echo "md 0" >/var/www/html/FIFO1
echo "md 1" >/var/www/html/FIFO1

echo "md=0" >/var/www/html/FIFO1
echo "md=1" >/var/www/html/FIFO1

I'll be doing this via ssh as part of the mask upload script.

The main command pipe is FIFO. One can also use FIFO11 -FIFO19 if required to avoid multiple applications trying to write to the same pipe.
FIFO1 is not a command pipe it is used to provide communication between the raspimjpeg and the scheduler to pass motion detection events.
See wiki under pipe and motion detect for details.
Commands being processed correctly will put stuff into the scheduler log file.
Note that I will may add the camera restart sequence to the mf command so that a change in the mask filename would trigger a reload. However, this would not effect uploading a new mask file with the same name. That would still need something like the motion detect off / on sequence.

The main command pipe is FIFO. One can also use FIFO11 -FIFO19 if required to avoid multiple applications trying to write to the same pipe.
FIFO1 is not a command pipe it is used to provide communication between the raspimjpeg and the scheduler to pass motion detection events.
See wiki under pipe and motion detect for details.
Commands being processed correctly will put stuff into the scheduler log file.
Note that I will may add the camera restart sequence to the mf command so that a change in the mask filename would trigger a reload. However, this would not effect uploading a new mask file with the same name. That would still need something like the motion detect off / on sequence.

FIFO1 is not a command pipe

Oh....I guess this threw me:

...It still does.
But blind obedience works, so thats good enough for me.
ssh pizerocam3 "echo md=0  >/var/www/html/FIFO;echo md=1  >/var/www/html/FIFO"

FYI:
I don't think that relying on filename changes to trigger mask updates will always be useful.
The GUI 'OK' button press would seem to be best suited to triggering an update.

FIFO1 is not a command pipe

Oh....I guess this threw me:

...It still does.
But blind obedience works, so thats good enough for me.
ssh pizerocam3 "echo md=0  >/var/www/html/FIFO;echo md=1  >/var/www/html/FIFO"

FYI:
I don't think that relying on filename changes to trigger mask updates will always be useful.
The GUI 'OK' button press would seem to be best suited to triggering an update.


[minor] add AUS NSW

Have to read an RSS feed, get the latest one, and then go parse a table.

Closed in favour of https://github.com/lazd/coronadatascraper/pull/274


Feedback for: docker-for-windows/index.md

File: docker-for-windows/index.md
hi,
i alwaya get this error

@wysiharig Thank you for your feedback. However, it looks like your issue is not
about Docker documentation, but that you may be having trouble with
Docker itself. Please file a Docker support ticket or check out
https://forums.docker.com/ to see if you can find a solution.
If this really is a documentation issue and I have misunderstood,
please reopen it with more information


Update cosmos to version 0.2.0-SNAPSHOT-93-refs_heads_master-c6e5c87ba2

@BenWhitehead Needs a rebase on master.

Thanks @cmaloney!


Native macOS notifications (i.e., push notifications to notification centre)

Feature Description
Native macOS notifications (i.e., push notifications to notification centre)
Motivation and Context
Enhancement
Extend the Franz notification system to integrate natively with macOS's notification centre and make the notification's actions customisable with which service they integrate.
Examples

Gmail might have Archive & Delete;
Skype/Telegram/Messenger might have dynamic context based on whether there's an incoming call or you've received a message, e.g.,

Reply/Mark as Read, Answer/Ignore.

Justification

Badge icon counts are insufficient to provide notification context and aren't even a feature for those who auto hide their dock (or use a 3rd party dock replacement).
Audible notifications are typically not the preferred option (based on anecdotal community evidence), where most people prefer visual, rather than audible, alerts.
You can't determine which service sent you the notification nor tell what order/time/date it was received.

Summary
Without a more prosperous notification system, Franz needs a permanent place on your desktop where it's always visible, and even then, you may not notice a new alert come in.
Side Note
I contributed to an annual subscription today before realising the limitation. I don't have any regrets about my contribution since I can see Franz is actively developed and I hope those funds go some way to seeing macOS notifications sooner rather than later!

I'm trying Franz as a replacement to Wavebox. I thought this was a feature after reading:

Franz will notify you about incoming messages directly in your Operating System.

Spent a while setting up the notifications thinking it was something I did not set up correctly until I found this issue.
Is this being considered on the Roadmap? In my case is a dealbreaker since I need instant feedback when receiving email and calendar events.


Updated to use latest Docker v1.11.0 and Volume API

This commit updates the volume API implementation to leverage
the Docker v1.11.0. There was an addition of Get() and List()
methods in prior v1.10. The Get() method now replaces the
call that implicitly created volumes. The Create() method
was used for Path() and other methods prior because there
was no Get() method that returned a volume object.

root@mesos-master:/home/vagrant# ./dvdcli --volumedriver=rexray --volumename=test45 mount --explicitcreate=true
ERRO[0000] VolumeDriver.Get: {"Error":"No volumes returned"}
  volumeName=test45
root@mesos-master:/home/vagrant# ./dvdcli --volumedriver=rexray --volumename=test45 mount --explicitcreate=false
INFO[0012] /var/lib/rexray/volumes/test45/data
/var/lib/rexray/volumes/test45/data

Coverage decreased (-2.6%) to 32.99% when pulling 88634462efe077f3054cb928de260db92d002619 on clintonskitson:feature/update_docker_v1.11.0_volumes into 3c3dcbe1490c2c4a150555978f2b4915dafaddf2 on emccode:master.

The default behavior is the same as behavior, except there is no longer a create volume called in any case for Unmount() or Path(), a Get() is done instead to verify the volume exists or not. @cantbewong Can you verify that the mesos-module-dvdi will not be adversely affected if we error on missing volumes for Unmount() and Path() now?
The Mount() method now inherently is implict as before. But there is a specific flag to set it as explicit by --explicitcreate=true.

@clintonskitson when do you plan have this released? Can you please cut a branch and create a new release for it? Thanks.

@jay-lau Have you had a chance to test and verify?

Coverage decreased (-3.2%) to 32.99% when pulling e9dbe2863306781ecdf98c5e6396d50eed115797 on clintonskitson:feature/update_docker_v1.11.0_volumes into 6d7cdf1afb5eb8236063944bb261d2ee8002e237 on emccode:master.

Coverage decreased (-3.2%) to 32.99% when pulling fe004466f1716bc9597da7c2a22c3729e041e924 on clintonskitson:feature/update_docker_v1.11.0_volumes into 6d7cdf1afb5eb8236063944bb261d2ee8002e237 on emccode:master.

Coverage decreased (-3.2%) to 32.99% when pulling fe004466f1716bc9597da7c2a22c3729e041e924 on clintonskitson:feature/update_docker_v1.11.0_volumes into 6d7cdf1afb5eb8236063944bb261d2ee8002e237 on emccode:master.

Coverage decreased (-3.2%) to 32.99% when pulling 9b4cdfa8522bd285928be80e991b8236540efa0a on clintonskitson:feature/update_docker_v1.11.0_volumes into 6d7cdf1afb5eb8236063944bb261d2ee8002e237 on emccode:master.

curl -sSL https://dl.bintray.com/emccode/dvdcli/install | sh -s stable

root@mesos-master:/home/vagrant# dvdcli --volumedriver=docker --volumename=test111124 mount --explicitcreate=true
ERRO[0000] VolumeDriver.Get: {"Error":"No volumes returned"}
  volumeName=test111124
root@mesos-master:/home/vagrant# dvdcli --volumedriver=docker --volumename=test111123 mount --explicitcreate=false
INFO[0000] /var/lib/rexray/volumes/test111123/data
/var/lib/rexray/volumes/test111123/data

@clintonskitson when do you want to have a stable version of 0.2.0? I saw that current version is 0.2.0-rc1
root@mesos002:~/src/mesos/m2/mesos/build# dvdcli version
Binary: /usr/bin/dvdcli
SemVer: 0.2.0-rc1
OsArch: Linux-x86_64
Branch: v0.2.0-rc1
Commit: a789d3ddde4fa9ce3201e3f7bd5ca0cec10a9132
Formed: Tue, 19 Apr 2016 03:55:17 CST

Planning on it today.
On Wednesday, April 20, 2016, Guangya Liu<EMAIL_ADDRESS>wrote:

@clintonskitson https://github.com/clintonskitson when do you want to
have a stable version of 0.2.0? I saw that current version is 0.2.0-rc1
root@mesos002:~/src/mesos/m2/mesos/build# dvdcli version
Binary: /usr/bin/dvdcli
SemVer: 0.2.0-rc1
OsArch: Linux-x86_64
Branch: v0.2.0-rc1
Commit: a789d3ddde4fa9ce3201e3f7bd5ca0cec10a9132
Formed: Tue, 19 Apr 2016 03:55:17 CST
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/emccode/dvdcli/pull/20#issuecomment-212325389

@jay-lau https://github.com/emccode/dvdcli/releases/tag/v0.2.0

Cool! Thanks @clintonskitson


interesting this topic

coming to learning rust, the cli app is good start, thanks for your sharing.

Thanks 😄 It'll be slow progress, but once it's at a releasable state I'll make a blog post and send to the forums and subreddits as well!


cumulative leap second to 2025

The cumulative leap second in the gps.py script can be extended to 2025. No leap second was added in 2024.

Fixed in 1.2.1, thank you!
pip install --upgrade tempoo


fix(transformer/arrow-functions): _this = this should be inserted after super call expression

related: #7792
This PR doesn't contain fixing the async arrow function in super(), which is difficult for our architecture. I just found that esbuild's implementation is quite simpler! https://esbuild.github.io/try/#dAAwLjI0LjAALS10YXJnZXQ9ZXMyMDE2AGNsYXNzIEMgZXh0ZW5kcyBTIHsKICBjb25zdHJ1Y3RvcigpIHsKICAgIHN1cGVyKGFzeW5jICgpID0+IHRoaXMpOwogICAgYXN5bmMoKSA9PiB7fQogIH0KfQ

#8024  👈 (View in Graphite)
main

How to use the Graphite Merge Queue
Add either label to this PR to merge it via the merge queue:

0-merge - adds this PR to the back of the merge queue
hotfix - for urgent hot fixes, skip the queue and merge this PR next

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

@overlookmotel Can you take a look at this PR, I am not sure this is a good. I really want to change everything according to esbuild's implementation

Concerning ESBuild's version:
Yes it's simpler to implement, but I think less performant at runtime than Babel's version. In Babel's version, there's only 1 call to asyncToGenerator when the async function is defined. But in ESBuild's version, __async gets called and constructs a new generator function every time you call the async function.
I don't know for sure, but that sounds more expensive (more garbage collection).
I think we could do our own version which is better than both! Maybe something like this:
Input:
class C extends S {
  constructor() {
    super();
    let f = async () => this;
  }
}

Output:
class C extends S {
  constructor() {
    var _getThis = () => this;
    super();
    let f = oxcHelpers.asyncToGenerator(function*() { return this; }, _getThis, "f");
  }
}

(the last param takes care of naming the function correctly, instead of Babel's extra function wrappers)
But... I suggest we follow Babel for now, make our implementation correct, and look at optimizing output later. There's many places we can improve on Babel in lots of transforms.

PS: I've made a small improvement to the super()-replacer visitor in #8028.

That's a trade-off for us considering the different implementations. When I am a developer for the transformer, I prefer a
way easy to implement save my hair!

To clarify, so in this case, you prefer to double-visited? I have no strong opinion about this. Just think of this way is easier to implement, but cannot solve super(async () => {}).

I think double-visit is the best way, yes.
I think it'll be able to handle the super(async () => this) case too.
We could later try and optimize it for common case where super() is a top level statement, by storing the Address of super() during traversal, and then you know exactly where to insert _this = this without another visit.
But:

I'm not actually sure if that'll be a perf gain or not, because you have to do a lot more checking for "is this node super()?", when most of the time the answer is "no". And when the class constructor doesn't contain an async arrow function (most won't), then that's wasted work.
That won't handle all the edge cases anyway.
Make it correct first, then optimize.