Search functionality not working

MacOS High Sierra, 10.13.6
Chrome: Version 68.0.3440.106 (Official Build) (64-bit)
Type a search phrase in to the search bar (top right of screen) and hit enter:  Nothing happens.
I had a look in the console for any errors, could not see anything.

I get a 404 error for asset: https://cdn.jsdelivr.net/docsearch.js/1/dist/cdn/docsearch.min.js.map

+1 search is broken on 0.57 version of the site

Definitely still working in 0.56 version on the site so it's gotta be something that was introduced inbetween.

Seemingly fixed by magic or #560 can be closed.

working again 👍


Fix a few flaky aws tests

This (hopefully) handles the EC2 400 errors on instance creation, and another rare error when creating a leader. Both are related to consistency issues with EC2: the results of instance creation aren't immediately propagated to all the servers that handle our requests.
There are still a few flaky AWS tests remaining, because the t2.small instances used in some of the tests have only a few MB of headroom to be able to run the jobs we issue. We are somehow using nearly a GB (and sometimes more) of RAM as overhead on worker nodes.

@jessebrennan I think that looks super cool! I like how clean the decorator approach is.
One thing I just thought of though, is that we might have to be careful that all functions wrapped in a decorator are idempotent. The _addTags method, for example, may not be. If we are adding 3 tags and hit a retriable exception on the 3rd, then we would try to add all 3 tags over again--which might raise some other error from AWS complaining that we already added it. (Or maybe they don't care about "creating" the same tag twice--in which case it doesn't really matter.)
I'd be cool with going with your retry changes in a new PR and closing this one, as long as the changes from 1aa662f are still included somehow.

@joelarmstrong I rebased off of your branch. Feel free to close this, but I'll ping you for a final review.
Good point about idempotentcy. I wonder if it would be worth breaking some of those larger functions into smaller, idempotent ones and then wrapping those.

Yeah I think that's the safest possible approach: methods that do only 1 request which are wrapped in your decorator, then composed into larger, more useful functions. Thanks!


print_hip_info working with CUDA

bazel build //...

is now failing for me. Is it supposed to?
ERROR: /home/oliver/repos/oliverlee/gpu-deflate/BUILD.bazel:14:13: Compiling bazel-out/k8-fastbuild/bin/hip_info.cpp.cu failed: (Exit 1): nvcc failed: error executing command (from target //:hip_info_cuda) /usr/local/cuda/bin/nvcc -x cu -Xcompiler -fPIC -ccbin external/gcc_12_2_toolchain/tool_wrappers/x86-64/2022.08-1_bleeding/x86-64-linux-gnu-2022.08-1_bleeding-gcc -I . -I bazel-out/k8-fastbuild/bin -I ... (remaining 31 arguments skipped)

Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
In file included from /usr/local/cuda/bin/../targets/x86_64-linux/include/cuda_runtime.h:83,
                 from <command-line>:
/usr/local/cuda/bin/../targets/x86_64-linux/include/crt/host_config.h:139:2: error: #error -- unsupported GNU version! gcc versions later than 10 are not supported! The nvcc flag '-allow-unsupported-compiler' can be used to override this version check; however, using an unsupported host compiler may cause compilation failure or incorrect run time execution. Use at your own risk.
  139 | #error -- unsupported GNU version! gcc versions later than 10 are not supported! The nvcc flag '-allow-unsupported-compiler' can be used to override this version check; however, using an unsupported host compiler may cause compilation failure or incorrect run time execution. Use at your own risk.
      |  ^~~~~

Disabled CUDA by default. We can debug it more on your system later if needed.


Check energy conservation when there are sources or sinks

Check that the atmos model conserves energy when there are sources or sinks, such as radiation, surface fluxes, and precipitation.
cc @LenkaNovak

superseded by #2568


Loading the model

Hi, may I ask how can I load your pretrained .model file into Keras properly? I use tensorflow 1.13.1, Keras 2.2.4, and it seems there is a problem loading the model.
I would be very grateful if you can take a look of my problem or tell me your solution!

Thanks for your reply! I don't think network architecture could be the problem, as I simply import keras and use keras.model.load_model() function, there appears the same error.

Thanks for your reply! I don't think network architecture could be the problem, as I simply import keras and use keras.model.load_model() function, there appears the same error.

Could you just remove the decode part? Don't think you need the decode when it's a str.

Yes, and I find a solution by reinstalling another version of h5py package, but when I run play.py another problem happened, as shown in the image. I have looked up for this issue, most answers revolves around the older version of keras should use lr rather than learning_rate as the parameter, however, I have checked the original code, sendex did pass lr as the parameter. And when I run train.py, there is no error, but the trained seems to stuck at waiting state. I am a little confused.

Maybe ChatGPT could help

Yeah maybe, thanks for the tip!


[ERROR] Could not resolve "fast-xml-parser"

To reproduce
npx create-next-app@latest

cd my-app
npx create-sst@latest

npm install
npx sst deploy

Note: In all the cases used the defaults
And the error that happens:
✘ [ERROR] Could not resolve "fast-xml-parser"

    ../../../Users/ignacio/.npm/_npx/6fd3fdda1aa7f7f3/node_modules/@aws-sdk/core/dist-cjs/index.js:372:37:
      372 │ var import_fast_xml_parser = require("fast-xml-parser");
          ╵                                      ~~~~~~~~~~~~~~~~~

  You can mark the path "fast-xml-parser" as external to exclude it from the bundle, which will
  remove this error. You can also surround this "require" call with a try/catch block to handle this
  failure at run-time instead of bundle-time.

/Users/ignacio/.npm/_npx/6fd3fdda1aa7f7f3/node_modules/esbuild/lib/main.js:1649
  let error = new Error(text);
              ^

Error: Build failed with 1 error:
../../../Users/ignacio/.npm/_npx/6fd3fdda1aa7f7f3/node_modules/@aws-sdk/core/dist-cjs/index.js:372:37: ERROR: Could not resolve "fast-xml-parser"
    at failureErrorWithLog (/Users/ignacio/.npm/_npx/6fd3fdda1aa7f7f3/node_modules/esbuild/lib/main.js:1649:15)
    at /Users/ignacio/.npm/_npx/6fd3fdda1aa7f7f3/node_modules/esbuild/lib/main.js:1058:25
    at runOnEndCallbacks (/Users/ignacio/.npm/_npx/6fd3fdda1aa7f7f3/node_modules/esbuild/lib/main.js:1484:45)
    at buildResponseToResult (/Users/ignacio/.npm/_npx/6fd3fdda1aa7f7f3/node_modules/esbuild/lib/main.js:1056:7)
    at /Users/ignacio/.npm/_npx/6fd3fdda1aa7f7f3/node_modules/esbuild/lib/main.js:1085:16
    at responseCallbacks.<computed> (/Users/ignacio/.npm/_npx/6fd3fdda1aa7f7f3/node_modules/esbuild/lib/main.js:703:9)
    at handleIncomingPacket (/Users/ignacio/.npm/_npx/6fd3fdda1aa7f7f3/node_modules/esbuild/lib/main.js:762:9)
    at Socket.readFromStdout (/Users/ignacio/.npm/_npx/6fd3fdda1aa7f7f3/node_modules/esbuild/lib/main.js:679:7)
    at Socket.emit (node:events:517:28)
    at addChunk (node:internal/streams/readable:368:12) {
  errors: [Getter/Setter],
  warnings: [Getter/Setter]
}

Node.js v18.19.0

Error: There was a problem building the "site" site.

Workaround on aws-sdk-js-v3
I also tried to apply this: https://github.com/aws/aws-sdk-js-v3/issues/5866#issuecomment-1984882353 without success.
npm add @aws-sdk/client-s3
npx sst deploy

Same error again.
Workaround directly adding fast-xml-parser
I also tried to directly add fast-xml-parser
npm add fast-xml-parser
npx sst deploy

Same error again.

Discord link: https://discord.com/channels/983865673656705025/1145967640595148803/1215594523997118545

If using npm
rm -rf node_modules package-lock.json
npm install
If using yarn
yarn cache clean
rm -rf node_modules yarn.lock
yarn install
Can you please remove caches and node_modules, .sst , .next everything and try again

Thanks @rokasta12, I tried that, I think the final solution was npm cache clean --force(there was something cached in my npm user cache - more details in the discord)


Many new cards available for support thanks to our GPU survey.

Thanks to the wonderful community for submitting their PCI IDs and card names in the Discord server. I have added all that people want so far.

Please only use unix line endings for code. This makes it much easier to review. dos2unix will convert it back to unix line endings.
For example the diff for 2fe296a is huge.

@DualCoder You can make this happen automatically (99% of the time) with a .gitattributes file and normalizing all line endings in the repo.
I can PR that if it's wanted along with an EditorConfig. :)

@jonpas Please do.

#18 but this branch will still have to be updated, as .gitattributes only works for new commits / changed lines (if I remember correctly).

I'm on windows, so no Unix line endings for me :(

I added M10, M60, and V100 support, so I think this PR is completed. Let me know if there is anything else you need before merging :)

Changed CRLF to LF, sorry about the difference looking huge.


Can we use it for chatter posts?

Hi,
I'm trying to fixture our if we are able to use this package for chatter uploads.
do you have any information about this?
Thank you!

There's a raw request for GET and POST in the Salesforce.php file that you can use for anything not covered by the current api. I don't have any plans to add it at this time.
You could do something like this:  $me = Salesforce::rawGetRequest('chatter/users/me');  This should send a GET request to https://instance.salesforce.com/services/data/v36.0/chatter/users/me


Add support to Nukkit 2.0's LevelDB format

Is your feature request related to a problem? Please describe.
Nukkit 2.0 now targets the LevelDB format and Anvil is getting deprecated.
Describe the solution you'd like
Have an option to convert directly to a LevelDB format which Nukkit 2.0 can handle, so no more conversions are needed.
Describe alternatives you've considered
Create a new repository like the Region Manipulator which does the same thing but with LevelDB using pure Java if possible.

Would you add Pocketmin Support? yet, the converter work also for it?


Unmounting 'Masonry' component throws type error 'Cannot read properties of null (reading 'clientWidth')'

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯

I implemented one page that contains a responsive masonry component and moved to another page.
Then, I faced this error in the browser console.
Masonry.js:208
Uncaught TypeError: Cannot read properties of null (reading 'clientWidth') at ResizeObserver.handleResize (Masonry.js:208)

Expected Behavior 🤔

It should move to other pages without printing console error.
Steps to Reproduce 🕹

Steps:

Link to https://6gw4k.csb.app/
Click 'Page 2' link
Click 'Page 1' link
Showing 'Type Error'

Context 🔦

Your Environment 🌎

`npx @mui/envinfo`
  Don't forget to mention which browser you used.
  Output from `npx @mui/envinfo` goes here.

 System:
OS: Windows 10 10.0.22000

Binaries:
Node: 14.15.3 - C:\Program Files\nodejs\node.EXE
Yarn: Not Found
npm: 6.14.9 - C:\Program Files\nodejs\npm.CMD

Browsers:
Chrome: Not Found
Edge: Spartan (44.22000.120.0), Chromium (95.0.1020.40)

npmPackages:
@emotion/react: ^11.5.0 => 11.5.0
@emotion/styled: ^11.3.0 => 11.3.0
@mui/core:  5.0.0-alpha.53
@mui/icons-material: ^5.0.5 => 5.0.5
@mui/lab: ^5.0.0-alpha.53 => 5.0.0-alpha.53
@mui/material: ^5.0.6 => 5.0.6
@mui/private-theming:  5.0.1
@mui/styled-engine:  5.0.2
@mui/system:  5.0.6
@mui/types:  7.0.0
@mui/utils:  5.0.1
@types/react: ^16.14.20 => 16.14.20
react: ^17.0.2 => 17.0.2
react-dom: ^17.0.2 => 17.0.2
typescript: ^4.1.6 => 4.4.4

Seems it happens because of same reason in #29362
When the component is unmounted, it lost its reference?

Seems it happens because of same reason in #29362
When the component is unmounted, it lost its reference?

Yes, it seems so. I added extra checks to prevent such issue. Check out https://github.com/mui-org/material-ui/pull/29452 :)


Configure error link tests are not allowed after AC_NO_EXECUTABLES

Moving to OpenThread master, we are seeing build failures triggered during configure:
checking for stdint.h... (cached) yes
checking for string.h... (cached) yes
checking for strlcpy... (cached) no
checking for strlcat... (cached) no
checking for strnlen... configure: error: link tests are not allowed after AC_NO_EXECUTABLES
make[4]: *** [config.status] Error 1
make[3]: *** [build] Error 2
make[2]: *** [tps/openthread/Makefile] Error 2

This seems to happen after the changes in this commit https://github.com/openthread/openthread/commit/d65418c12fbf820dd1ade22087541bff691a8f96.
@darconeous, @DuaneEllis-TI , any ideas?

Why is this not being caught by travis checks?
What target CPU are you using here?  What compiler version?
can you provide a more complete config.log to examine?

Also - does this help resolve the issue: https://github.com/openthread/openthread/pull/1677

Compiler is : arm-none-eabi-gcc (v.4,9).
gcc version 4.9.3 20141119 (release) [ARM/embedded-4_9-branch revision 218278] (GNU Tools for ARM Embedded Process

Let me check with https://github.com/openthread/openthread/pull/1677....

I still see this with the https://github.com/openthread/openthread/pull/1677 changes included.

so - i just pulled head, and using (the same compiler as you)
arm-none-eabi-gcc (GNU Tools for ARM Embedded Processors) 4.9.3 20141119 (release) [ARM/embedded-4_9-branch revision 218278]
Copyright (C) 2014 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

./bootstrap
make -f examples/Makefile-cc2538

Works just fine.
What else can you tell me?

This isn't an OpenThread bug. We can close this issue and discuss internally.

Thanks RQ . Also thanks @DuaneEllis-TI for your quick help with this.
Seems like it's related to an internal makefile  issue that we need to figure out.
Closing this issue.

See https://github.com/openthread/openthread/commit/812cc838ebe8bec59831273d5e296f32ade0ffa4#commitcomment-21953634


fix: Update models.py

display_GMT_offset=getattr(
        settings, "TENANT_TIMEZONE_DISPLAY_GMT_OFFSET", False
    ),

TypeError: init() got an unexpected keyword argument 'display_GMT_offset'
Django throws this error when I am using the package but when I remove the field it works fine. I wonder what's the matter. Do you think you can help me here. Thank you

Fixed in #30


Rviz crashes when started with specific tf but not others

I'm playing back a bag with a occupancy_grid, pointclouds, and a tf system. If the fixed frame is set to a specific (which happens to be the root of the tf tree) rviz will crash the moment bag playback starts. If the fixed frame is set to any other frame in the bag the playback will work correctly. After the first set of messages are displayed you can set the fixed frame to any other frame and rviz is fine. It doesn't matter how far into the bag I start playback the same thing happens. I've only included the gdb backtrace but I can include everything rviz prints on startup (its a lot of text) if desired.
**GDB Backtrace**
[ INFO] [1440030397.386498288,<PHONE_NUMBER>.921057766] [/playback_rviz]: Font Arial using texture size 512x512
[ INFO] [1440030397.388154812,<PHONE_NUMBER>.921564215] [/playback_rviz]: Info: Freetype returned null for character 160 in font Arial
[ INFO] [1440030397.388429254,<PHONE_NUMBER>.921564215] [/playback_rviz]: Texture: ArialTexture: Loading 1 faces(PF_BYTE_LA,512x512x1) with 0 generated mipmaps from Image. Internal format is PF_BYTE_LA,512x512x1.
[ INFO] [1440030400.943647025,<PHONE_NUMBER>.276780689] [/playback_rviz]: Texture: MapTexture0: Loading 1 faces(PF_L8,3072x3072x1) with 0 generated mipmaps from Image. Internal format is PF_L8,3072x3072x1.

Program received signal SIGSEGV, Segmentation fault.
0x0000000000000000 in ?? ()
(gdb)
(gdb) backtrace
#0  0x0000000000000000 in ?? ()
#1  0x00007ffff7affd01 in rviz::Property::Property(QString const&, QVariant, QString const&, rviz::Property*, char const*, QObject*) ()
   from /opt/ros/indigo/lib/librviz.so
#2  0x00007fff953edeae in rviz::TFDisplay::updateFrame(rviz::FrameInfo*) ()
   from /opt/ros/indigo/lib/libdefault_plugin.so
#3  0x00007fff953ef4d7 in rviz::TFDisplay::updateFrames() ()
   from /opt/ros/indigo/lib/libdefault_plugin.so
#4  0x00007fff953ef756 in rviz::TFDisplay::update(float, float) ()
   from /opt/ros/indigo/lib/libdefault_plugin.so
#5  0x00007ffff7aa7692 in rviz::DisplayGroup::update(float, float) ()
   from /opt/ros/indigo/lib/librviz.so
#6  0x00007ffff7b48bbe in rviz::VisualizationManager::onUpdate() ()
   from /opt/ros/indigo/lib/librviz.so
#7  0x00007ffff2e2387a in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#8  0x00007ffff2e27a31 in QObject::event(QEvent*) ()
   from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#9  0x00007ffff6edce2c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
    () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#10 0x00007ffff6ee34a0 in QApplication::notify(QObject*, QEvent*) ()
   from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#11 0x00007ffff2e0f4dd in QCoreApplication::notifyInternal(QObject*, QEvent*)
---Type <return> to continue, or q <return> to quit---
    () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#12 0x00007ffff2e3f323 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#13 0x00007ffff2e3c629 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#14 0x00007ffff1782e04 in g_main_context_dispatch ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#15 0x00007ffff1783048 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#16 0x00007ffff17830ec in g_main_context_iteration ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#17 0x00007ffff2e3c7a1 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#18 0x00007ffff6f7ebe6 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#19 0x00007ffff2e0e0af in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#20 0x00007ffff2e0e3a5 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#21 0x00007ffff2e13b79 in QCoreApplication::exec() ()
   from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#22 0x0000000000400bc7 in main ()

@CaffeineSqurr is possible for you to share a bag file with just the /tf data that causes the problem?

Here's the bag with only the tf messages
https://www.dropbox.com/s/zcfkn6afvkjgehk/tf_only.bag?dl=0

Thanks @CaffeineSqurr, I'll have a look at it as soon as I'm able. If you find out more or find a solution please let us know.

This bug, along with the related ones #808 #616 (and the tf saving issue #834), I spent a bit of
time to try and look into the issue.
First, the debug trace goes as follow:
#0  0x00007ffff2f60940 in QVectorData::shared_null () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#1  0x00007ffff7a5c322 in rviz::Property::Property (this=0x114fa70, name=..., default_value=..., description=...,
    parent=0x11ff4d0, changed_slot=0x0, receiver=0x0)
    at /home/arnaud/src/ext/catkin_ws/src/rviz/src/rviz/properties/property.cpp:72
#2  0x00007fffa1ac3ec2 in rviz::TFDisplay::updateFrame (this=0x92fc40, frame=0x11954d0)
    at /home/arnaud/src/ext/catkin_ws/src/rviz/src/rviz/default_plugin/tf_display.cpp:580
#3  0x00007fffa1ac1d58 in rviz::TFDisplay::updateFrames (this=0x92fc40)
    at /home/arnaud/src/ext/catkin_ws/src/rviz/src/rviz/default_plugin/tf_display.cpp:372
#4  0x00007fffa1ac1b8b in rviz::TFDisplay::update (this=0x92fc40, wall_dt=0.0298139174, ros_dt=0.0298169907)
    at /home/arnaud/src/ext/catkin_ws/src/rviz/src/rviz/default_plugin/tf_display.cpp:327
#5  0x00007ffff79cf064 in rviz::DisplayGroup::update (this=0x7be3e0, wall_dt=0.0298139174, ros_dt=0.0298169907)
    at /home/arnaud/src/ext/catkin_ws/src/rviz/src/rviz/display_group.cpp:234
#6  0x00007ffff7acea91 in rviz::VisualizationManager::onUpdate (this=0x7e6a10)
    at /home/arnaud/src/ext/catkin_ws/src/rviz/src/rviz/visualization_manager.cpp:320
#7  0x00007ffff7af1391 in rviz::VisualizationManager::qt_static_metacall (_o=0x7e6a10,
    _c=QMetaObject::InvokeMetaMethod, _id=3, _a=0x7fffffffcef0)
    at /home/arnaud/src/ext/catkin_ws/build/rviz/src/rviz/moc_visualization_manager.cxx:64
#8  0x00007ffff2c0e87a in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) ()
   from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#9  0x00007ffff2c12a31 in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#10 0x00007ffff6ca2e2c in QApplicationPrivate::notify_helper(QObject*, QEvent*) ()
   from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#11 0x00007ffff6ca94a0 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#12 0x00007ffff2bfa4dd in QCoreApplication::notifyInternal(QObject*, QEvent*) ()
   from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#13 0x00007ffff2c2a323 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#14 0x00007ffff2c27629 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#15 0x00007ffff156de04 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#16 0x00007ffff156e048 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#17 0x00007ffff156e0ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#18 0x00007ffff2c277a1 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
   from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#19 0x00007ffff6d44be6 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#20 0x00007ffff2bf90af in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
   from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#21 0x00007ffff2bf93a5 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) ()
   from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#22 0x00007ffff2bfeb79 in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#23 0x0000000000401080 in main (argc=3, argv=0x7fffffffd6b8)
    at /home/arnaud/src/ext/catkin_ws/src/rviz/src/rviz/main.cpp:41

Which corresponds to the following call in tf_display.cpp:580
 // Delete the old tree property.
delete frame->tree_property_;
frame->tree_property_ = NULL;

// If the parent has a tree property, make a new tree property for this frame.
 if( parent->tree_property_ )
{
frame->tree_property_ = new Property( QString::fromStdString( frame->name_ ), QVariant(), "", parent->tree_property_ );
}

By doing a bit more gdb magic, we notice that the parent object has an adress, but that none of it's functions or attributes are accessible:
(gdb) frame 1
#1  0x00007ffff7a5c322 in rviz::Property::Property (this=0x114fa70, name=..., default_value=..., description=...,
    parent=0x11ff4d0, changed_slot=0x0, receiver=0x0)
    at /home/arnaud/src/ext/catkin_ws/src/rviz/src/rviz/properties/property.cpp:72
72	    parent->addChild( this );
(gdb) print parent
$1 = (rviz::Property *) 0x11ff4d0
(gdb) print parent->getName()

Program received signal SIGSEGV, Segmentation fault.
0x000000000120b950 in ?? ()
The program being debugged was signaled while in a function called from GDB.
GDB remains in the frame where the signal was received.
To change this behavior use "set unwindonsignal on".
Evaluation of the expression containing the function
(at 0x0x120b950) will be abandoned.
When the function is done executing, GDB will silently stop.

Okay, so, we've got some corrupted memory somewhere. I really am not surprised, considering how this property_tree_ is handled. It is destroyed/recreated here and there, in function either called by periodic timer update, or by manually using the reset button and so on...
Any particular reason for deleting and recreating this object all the time?
One quick testing hack "resolves" the issue. Commenting line 574
 // Delete the old tree property.
// delete frame->tree_property_;
frame->tree_property_ = NULL;

// If the parent has a tree property, make a new tree property for this frame.
if( parent->tree_property_ )
{
    frame->tree_property_ = new Property( QString::fromStdString( frame->name_ ), QVariant(), "", parent->tree_property_ );
}

However, this most likely creates a memory leak.
My guess is that the problem originates from race conditions between threads deleting the tree_property_ while others are trying to use it, thus causing random bugs.
Now, I don't really have the time to figure out how to solve this properly, it would be nice if someone more familiar with rviz could look into it.

@hershwg Why is the property tree deleted and then recreated, instead of just being updated?
The easiest way to fix this would be to never delete it in the first place, but update its elements wouldn't it?

Please comment if https://github.com/ros-visualization/rviz/pull/926 doesn't solve the issue for you.


Upgrade to 5.00

Solution

Upgrade to 5.00

PR Status

[ ] Code finished.
[ ] Tested with Package_check.
[ ] Fix or enhancement tested.
[ ] Upgrade from last version tested.
[ ] Can be reviewed and tested.

!testme

!testme


Add a New Button

Fixes Issue
Closes #1267

Changes proposed

Added a new animated button, created using HTML & CSS.
Screenshots

Checklist

[x] You've linked this PR to the correct issue.
[x] You have checked that the code is working correctly.
[x] You ⭐ the repository!

Note to reviewers

This PR is part of GSSoC'23.

Hey @Spyware007 & @TANYA-CHAN, please add the appropriate labels to this PR since it's a part of GSSoC'23.

Hey @Spyware007 & @TANYA-CHAN, can you please add the labels for GSSoC'23?


Inline youtube videos not showing up.

Hi Brian,
Your recent work was greatly appreciated - you can see the hosanas in this mornings threads.
However, one bug has cropped up involving embedded youtube videos.  An example may be found here:
https://reason.com/blog/2015/09/21/alexis-tsipras-stepped-down-as-greek-pri#comment_5603046
I don't have a quick fix to recommend.  Can you take a stab at it? :)

Should be fixed in version 2.3.6 (80887b2905a26abce709e7a2891499736997bed3).

Works like a charm!!!  Thanks!


ClippedPPO does not log loss, value/policy loss, kl divergence

ClippedPPO does not log a number of relevant parameters in the CSV file inside the experiments directory. These include loss, value loss, kl divergence, policy loss. It becomes difficult to debug the training runs without these parameters.
The corresponding columns are empty in the file and the visualization does not show these parameters for graphing.

Hi @bbalaji-ucsd ,
This was indeed a bug. Fixed with 72ea9333846e39e508eaff73b1d96d144d020532.
Thanks for catching this.


Add a NodeFail action

Signed-off-by: Patrick Uiterwijk<EMAIL_ADDRESS>

Could you please add docs? https://github.com/CentOS/python-cicoclient/blob/master/docs/cli_usage.rst

@dmsimard Added them.

@puiterwijk ping ?

@dmsimard well, I basically copied the docs from the "done" one, since I am unable to test this code anywhere with the lack of a duffy setup I can test it against:

I can't test it on CentOS CI, since I can't install software on the CentOS CI slaves.
I can't test it locally by lack of Duffy sources to setup a local instance.

If this is blocking the PR, feel free to just close it out.


How to structure log without error - No parameter named "x"

I use the default python logger and provide structured parameters so that I can filter/search nicely in my logging system.
However pylance reports problems that each of the parameters do not exist
log.info('hello {name}',  name='Mark')

Error shown:
No parameter named "name"  (Pylance reportGeneralTypeIssues)
Is there a way to avoid this without turning general type issues off?

The issue title and "error shown" don't align with the code sample; I'm assuming that the issue is that named parameter?
Assuming log is a logging.Logger, the stubs upstream in typeshed don't seem to indicate that they support arbitrary kwargs: https://github.com/python/typeshed/blob/master/stdlib/logging/init.pyi
Both LoggerAdapter and the top-level info function do have a kwargs, perhaps it was an oversight? The docs on python.org state that kwargs are supported.

The PR that changed it is https://github.com/python/typeshed/pull/5862, which claims that Logger doesn't support arbitrary keyword args, only the adapter.

Sorry, updated error to match code sample.  Arbitrary keywords currently work, i'm using a seqlog  logger which relies on them
https://seqlog.readthedocs.io/en/latest/usage.html#overriding-the-root-logger
Is this a scenario they missed in that PR?

If I'm reading this correctly, this library patches the stdlib logger to add format string / kwargs support after the fact. That's an unfortunate bit of dynamic behavior; we assume that Logger is unmodified and its API matches the API declared in typeshed. I am a bit surprised this doesn't break other uses of the logger, given this changes the meaning of the strings.
It'd be more reasonable if this library instead gave a specific SeqLogger class or something to distinguish the APIs, not monkeypatch the standard library to behave differently...

OK, thanks for the information.


Developer guide

Could do with a section on building locally and contributing. Sure I am doing something wrong but after running:
go get
go install
go build
docker build .
docker run xxxxx

I get:
docker: Error response from daemon: Container command '/opt/keycloak-proxy' not found or does not exist..

Added a Building section in the readme ... essentially, go and make is enough or make docker-build


chore(dependencies): update bson dep vers

[x] - npm test succeeds
[x] - Code coverage does not decrease (if any source code was changed)

Current coverage is 75.22% (diff: 100%)

Merging #19 into master will not change coverage

@@             master        #19   diff @@
==========================================
  Files             2          2
  Lines           335        335
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits            252        252
  Misses           83         83
  Partials          0          0

Powered by Codecov. Last update dd43e87...58eb0a4


customize completion menu with native CompletionItemKind instead of lspkind-nvim

With nvim-compe I could customize the completion-menu-icons by simply defining the lsp-native CompletionItemKind:
require('vim.lsp.protocol').CompletionItemKind = {
    '', -- Text
    '', -- Method
    '', -- Function
    '', -- Constructor
    '', -- Field
    '', -- Variable
    '', -- Class
    'ﰮ', -- Interface
    '', -- Module
    '', -- Property
    '', -- Unit
    '', -- Value
    '了', -- Enum
    '', -- Keyword
    '﬌', -- Snippet
    '', -- Color
    '', -- File
    '', -- Reference
    '', -- Folder
    '', -- EnumMember
    '', -- Constant
    '', -- Struct
    '', -- Event
    'ﬦ', -- Operator
    '', -- TypeParameter
}

nvim-cmp doesn't recognize it and your README suggests to use lspkind-nvim which itself uses CompletionItemKind in the background. Is it possible to define completion-menu by myself with CompletionItemKind without lspkind-nvim?

Also calling it completion-kind would be probably more correct than completion-menu.

I think it would be better if nvim-cmp would simply check for require('vim.lsp.protocol').CompletionItemKind internally by itself. This is the official way to customize it and the only thing lspkind-nvim does is to set require('vim.lsp.protocol').CompletionItemKind anyway. Making lspkind-nvim a dependency is really not necessary.

Putting
for index, value in ipairs(vim.lsp.protocol.CompletionItemKind) do
  cmp.lsp.CompletionItemKind[index] = value
end

into my nvim-cmp configuration does the job nicely for me ...

Thanks. I think this should be the default. The use user should set it manually.

No... I think the changing defined value to customize is bad idea.
You should return your favorite kind icon via formatting.format instead of modify cmp.lsp.CompletionItemKind

No... I think the changing defined value to customize is bad idea.
You should return your favorite kind icon via formatting.format instead of modify cmp.lsp.CompletionItemKind

Hmm I'm afraid I don't understand ...
I could not find any help to formatting.format. Could you elaborate a bit more please?

@wimstefan There's an example here: https://github.com/hrsh7th/nvim-cmp#formattingformat-type-funentry-cmpentry-vim_item-vimcompleteditem-vimcompleteditem

@wimstefan There's an example here: https://github.com/hrsh7th/nvim-cmp#formattingformat-type-funentry-cmpentry-vim_item-vimcompleteditem-vimcompleteditem

Thanks a lot @ikalnytskyi  🙏
Unfortunately my skills are too lousy that I could get that working :/

@wimstefan You can take a peek at my configuration:
https://github.com/ikalnytskyi/dotfiles/blob/76e8528b9239a045075130f7c3c6437b19f6870f/nvim/.config/nvim/init.lua#L52-L78
https://github.com/ikalnytskyi/dotfiles/blob/76e8528b9239a045075130f7c3c6437b19f6870f/nvim/.config/nvim/init.lua#L254-L259

@ikalnytskyi this might work but I have two objections with this solution.

Isn't vim.lsp.protocol.CompletionItemKind already builtin into neovim-lsp or do I get it wrong? If so than why shouldn't it be used by default by nvim-cmp instead of creating a custom solution for it. nvim-compe recognizes vim.lsp.protocol.CompletionItemKind without any complicated interventions.
I find your solution too complicated to be honest and not intuitive at all. It should be as easy as setting a few variables. Just as it worked with vim.lsp.protocol.CompletionItemKind in nvim-compe.

I say again. the changing vim.lsp.protocol.CompletionItemKind is bad idea.
If some plugin checks vim.lsp.protocol.CompletionItemKind[item.kind] == 'Snippet', this will break with this customization.

Here's an example with codicons.nvim:
`
local codicons = require "codicons"
local codiconsCIK = require("codicons.extensions.completion_item_kind").symbols
...
formatting = {
format = function(_, vim_item)
vim_item.kind = codicons.get(codiconsCIK[vim_item.kind].icon)
return vim_item
end,
},
`

@hrsh7th I did not realise implications setting vim.lsp.protocol.CompletionItemKind up has. I was then interested to see what lspkind does and it seems like it also modifies it https://github.com/onsails/lspkind-nvim/blob/9cc326504e566f467407bae2669a98963c5404d2/lua/lspkind/init.lua#L100.
Perhaps it should be removed from README if it is such a bad idea and replaced with some safer way?

To be honest I still don't really understand why it's a bad thing to set CompletionItemKind. Maybe I just don't get what it purpose is if not defining completion-kind-icons but I trust @hrsh7th if he says so. I always assumed it to be correct because lspkind-nvim sets it internally and nvim-cmp recommends lspkind. Also nvim-compe seems to use CompletionItemKind for the icons. @hrsh7th you can close this issue if you want.

At least, In nvim-cmp, I prefer all menu customixation realises by formatting.format. It's explicit way and super flexisible.
For example, you can change icon per source.

Anyway, Thank you for raising a question. It was a good point to me.

Just wanted to share my final solution without using any plugins:
formatting = {
  format = function(entry, vim_item)
    vim_item.menu = ({
      nvim_lsp = '',
      buffer   = '',
    })[entry.source.name]
    vim_item.kind = ({
      Text          = '',
      Method        = '',
      Function      = '',
      Constructor   = '',
      Field         = '',
      Variable      = '',
      Class         = '',
      Interface     = 'ﰮ',
      Module        = '',
      Property      = '',
      Unit          = '',
      Value         = '',
      Enum          = '',
      Keyword       = '',
      Snippet       = '﬌',
      Color         = '',
      File          = '',
      Reference     = '',
      Folder        = '',
      EnumMember    = '',
      Constant      = '',
      Struct        = '',
      Event         = '',
      Operator      = 'ﬦ',
      TypeParameter = '',
    })[vim_item.kind]
    return vim_item
  end
},


Clean some tests

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

Project coverage is 100.00%. Comparing base (0b93d37) to head (72c3232).
Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #362   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files          100       100
  Lines         3164      3164
  Branches       267       267
=========================================
  Hits          3164      3164

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


Unable to use some git commands from atom or sub-packages.

git-pull, merge so far don't work from within packages in atom.
To fix this I did the following (OSX):

cd /Applications/Atom.app/Contents/MacOS/
mv Atom Atom-bin
vi Atom
paste:

#!/bin/sh
${0}-bin

save
chmod +x Atom

When I start Atom it can now use git commands like no ones business but updating fails.
Here is the error I get when using git-pull:
/Library/Developer/CommandLineTools/usr/libexec/git-core/git-pull: line 11: git-sh-setup: No such file or directory

I am using Yosemite at this point DP6. I had this issue on DP5 and PB1 as well.
Another way to fix it is to manually modify a few git-core files and hardcode a few file locations.
Please let me know if there's any more info I can provide. Thanks!

No reports on this for some time please let us know if this is still an issue.


BUG Using browser-sdk with NextJS 12

Error: Failed to fetch update manifest Internal Server Error
    at http://localhost:3000/_next/static/chunks/fallback/webpack.js?ts=1686740013295:1176:37
ReferenceError: exports is not defined in ES module scope
This file is being treated as an ES module because it has a '.js' file extension and<EMAIL_ADDRESS>contains "type": "module". To treat it as a CommonJS script, rename it to use the '.cjs' file extension.

Hello! Failed to use library (2.0.0-alpha9 version)  with NextJS. Seems like it can be fixed by removing "type": "module" from package.json.
Please assist how to overcome this issue to use with NextJS 12.0?

Hi there 👋 We will try to replicate this issue and get back to you shortly with instructions on how to proceed. Might be that we have misconfigured our package, which might require us to provide a new version for you to test.

@havardholvik thank you for really fast reply :) yeap, I would be happy if you will be able to replicate the issue and release new version! if I can help somehow – pls tag me here, will try to do my best!)

@havardholvik  Hello!
Do you have an idea when this release will be available for end users?
Trying to plan our product development tasks.
Or maybe any idea how I can fix it on my own? I tried to rename all .js files into .cjs in https://github.com/puhoshville/browser-sdk/tree/development
But after installing it using yarn add https://github.com/puhoshville/browser-sdk.git#development I'm getting error like:
Error [ERR_MODULE_NOT_FOUND]: Cannot find package<EMAIL_ADDRESS>
(both for windows and mac)

Same probkem for me.

Cant start it running with any react thourh any technologies

any example with fresh packet and react possible?

Same probkem for me.  Cant start it running with any react thourh any technologies
any example with fresh packet and react possible?

@DTX-92; I dont think this is the same issue, as from your stack trace you seem to be using our ESM build.
Looking closer at your error, it seems this might be related to using our SDK server-side, as is the default mode for Next. Have you looked at https://nextjs.org/docs/pages/building-your-application/optimizing/lazy-loading#with-no-ssr to configure your custom video component to only render client side?

Using the most recent next version, I dont see this issue. However, I am able to reproduce your issues now @puhoshville , when creating a vanilla app using npx create-next-app@12.
So it seems we might have some inconsistencies in our package.json, mainly having type: "module" and a main field pointing to our CJS build. However, we also have a module field pointing to our ESM build, which seems to be respected by the bundlers I have used up until this point.
One quick fix we can do is to update the CJS filename from .cjs.js -> .cjs and leave the type field as is. According to https://nodejs.org/docs/latest-v13.x/api/esm.html#esm_package_json_type_field, any compiler should treat .cjs as a common-js module regardless of the value in the type field.
Will let you know when we have issued a new version 👍

@puhoshville : We have now released 2.0.0-alpha10. I've tested that with your version of Next and things seem to be working fine now out of the box. Let me know if this solves the issue for you.
Keep in mind though that you need to ensure any component which makes use of the SDK is rendered client side, as we are using apis only available in the browser.


OSX .app bundle generated in release/ and .dmg has timestamp of assets/osx/Alacritty.app dir

When building a new release of Alacritty, the .app bundle has the modification timestamp of the assets folder in git (assets/osx/Alacritty.app) rather than the time of the build.
i.e., from a brand new checkout make dmg you end up with:
$ ls -ld /Volumes/Alacritty/Alacritty.app /Volumes/Alacritty/Alacritty.app/Contents/MacOS/alacritty
drwxr-xr-x  3 user  staff      102 12 Mar  2018 /Volumes/Alacritty/Alacritty.app/
-rwxr-xr-x  1 user  staff  6632008 29 Oct 16:51 /Volumes/Alacritty/Alacritty.app/Contents/MacOS/alacritty

Ideally the .app bundle timestamp would match the build timestamp.

That's because it's the last modification timestamp of the directory.
I'm not quite sure here what the desired behavior would accomplish.

@chrisduerr yes I understand, but an .app bundle on OSX is visually a single item. When opening up the dmg and copying to /Applications it is unusual for the .app to appear to be six months old for a release that was only released and built a few days ago.

If it's displayed incorrectly in macOS, that seems like an OSX issue.
However you could always just touch -m file to update the date if that is important to you.

@chrisduerr no? it's the alacritty Makefile that preserves the timestamps when copying the template dir
https://github.com/jwilm/alacritty/blob/master/Makefile#L35

You could still update the timestamp by using touch -m file after it has been moved. Alternatively it's also possible to exclude the timestamp from the -p option of cp.

Yep, these are the things I currently do on each build. This GH issue is to suggest making that the behaviour of the Makefile so builds are correct out of the box.

Feel free to open a PR to introduce this change.


Externally-provided socket ownership in the context of systemd socket activation

First, I would like to tell you that I understand that the described mode of operation may be out of scope of this specific project and should not be improved on here, with current API it could be solved externally, Yet, I still believe that you should know that there might be an oversight.
Currently, the KestrelServerOptions.ListenHandle and the underlying libuv-based socket handling code assumes ownership of the passed handle (via uv_tcp_open/uv_pipe_open), destroying the underlying descriptor when it's being closed. This leads to handle being unusable after listen socket is closed when server is shut down.
Normally, this is not a problem (although it probably should be explicitly mentioned in the documentation comments), but consider the the following scenario. For my project (not yet on Github), I would like to implement support for graceful server reload without the process restart along the lines of:
public static void Main(string[] args)
{
    while (true)
    {
        using (var host = BuildWebHost())
        {
            host.Run();
        }
    }
}

The specific implementation of BuildWebHost is irrelevant, it uses WebHostBuilder, configuring systemd activation with UseSystemd.
This allows to declare systemd service like this (non-crucial parts omitted):
some-server.service
[Unit]
Requires=some-server.socket

[Service]
ExecStart=/usr/bin/dotnet /opt/some-server/some-server.dll
ExecReload=/bin/kill -INT $MAINPID
NonBlocking=true

some-server.socket
[Unit]
PartOf=some-server.service

[Socket]
ListenStream=<IP_ADDRESS>:5555
NoDelay=true

Since ASP.NET Core installs proper signal handlers, SIGINT can be used to reload the server without a process restart, while SIGTERM will terminate the process altogether, and it works perfectly, but... since systemd provides socket handle (KesterlServerOptionsSystemdExtensions.SdListenFdsStart) via forking, the first Kestrel shutdown closes the passed descriptor and it can no longer can be used for subsequent Kestrel instances hosted in the same processe.
I again stress that this might be a less-than-usual case, and not worth your attention, but I still believe you should know of this.
So, was ListenHandle designed to destroy the passed descriptor on Kestrel instance shutdown, or is it an unintended consequence? Do you consider this a potential problem, and interested in improving ListenHandle itself, or systemd-activated scenario, by handling this in UseSystemd? Maybe consider splitting systemd integration in a separate project?
The only practical solution for this from a technical standpoint is duplication of provided file descriptor (either in Listener or in UseSystemd, though I believe that the latter being a configuration-related piece of code should not invoke syscalls). Unfortunately, this will require importing two native methods from the RT -- int dup(int oldfd) and int close(int fd) (the latter only required to handle error cases to prevent descriptor leaks), maybe the fcntl + F_DUPFDCLOEXEC should be used, but since Kestrel host is unlikely to spawn additional processes, we might as well skip on it. This looks quite easy to implement for Linux, I even hacked together a quick fix and it works, but its design and additional native dependencies don't really look good. To make things worse, the Windows version would need another pair of native calls (DuplicateHandle and CloseHandle respectively).
Thank you for reading this wall of text and considering the potential paths for improvement.
P.S. As a matter of a fact, there were other "victims" of this libuv mode of operation, see https://github.com/libuv/libuv/issues/510 and https://github.com/libuv/libuv/issues/390 (I wonder how Kelly solved it in haywire).

Very interesting. I had not considered reusing the listen handle.
It wouldn't be unheard of to add some non-libuv native calls given a compelling reason as long as it's well tested. We've had to make an OS-specific native call before to facilitate duplicating an accepted socket efficiently. This idea actually came from @saghul's comment in the libuv/libuv#390 issue you mentioned.
My knowledge of using systemd socket activation is pretty much limited to writing that original docker-based test, so I have a few questions about it.
First of all, after the listen handle is closed by Kestrel during shutdown, won't systemd create a new listen handle for the specified TCP and/or Unix domain socket and relaunch the specified service once a new connection is attempted? If so, why does it matter that the listen socket is momentarily closed? If not, why doesn't it work this way?
Secondly, even if Kestrel left the original listen handle open by duping it first, wouldn't it still have to close all the active accepted sockets when it shuts down? Does leaving the original listen handle open prevent connection refused error somehow?

At first, let me note that there is no problem with socket activation and server restarts (for example via systemctl restart), it's the reload (in-process disposal of Kestrel instance and re-creation of a new one) that is the problem -- this is why I believe it's a nonstandard scenario.
Now to the questions.
The activated process can't close the actual socket that is being listened (and that is why I like systemd, don't have to write master process myself), because it's a duplicate of a systemd one (systemd creates socket, then forks and execs the target service, cloning the socket to use a specific descriptor). But, the activated process can close it's own copy of the socket, preventing it's reuse inside the process itself.
And no, I don't think that original socket needs extra handling except duplication itself. Until the service process is dead, it's just an extra descriptor that can be used to start Kestrel instances, and when process dies, it automatically gets destroyed by the OS (since it's a clone of the original systemd socket, the original socket still lives in systemd).

@onyxmaster If I'm understanding your scenario correctly, I think it's probably niche enough to leave it to the app developer to dup the socket themselves even though it's not that easy.
If it was as simple as not calling uv_close on the listen socket when it was passed in via ListenHandle, I would probably be willing to do that, but AFAIK there is no other way to unregister the uv_listen callback.
We could keep the callback registered and just stop calling uv_accept when Kestrel shuts down, but I don't know for sure that a new Kestrel instance would be able to configure a second uv_listen callback. I'm not even sure that's worth testing, because it feels very hacky.

@halter73 well, I thought along the same lines. I'm planning to do additional systemd integration using native calls anyways (to take advantage of structured logging via journald). Still it's good we had this conversation, might be useful for future reference. Thank you for considering the options.


[CODEOWNERS]  Adding Metrics Advisor

Summary
The focus of these changes is to add an entry for the Cognitive Metrics Advisor libraries.
Last Upstream Rebase
Wednesday, October 1, 3:38pm (EDT)

/check-enforcer override


Base phpunit classes should be extracted to yii2-phpunit package

What steps will reproduce the problem?
We have a compatibility layer for phpunit: https://github.com/yiisoft/yii2/blob/master/tests/compatibility.php
This code was copied between many (all?) of yii2 official extensions. But this code relies on assumption, that phpunit 4 does not have PHPUnit\Framework\TestCase class. This was changed in phpunit 4.8.35: https://github.com/sebastianbergmann/phpunit/commit/a55235c033c2dc18db631cc6b804844f6d37615a
So now some tests does not work on phpunit 4.8.35 or 4.8.36 and you need to fix it in every extension. Obviously this is a monkey job and nobody wants to do it. So we have some lazy/temporary workarounds:

Lock phpunit to 4.8.34: https://github.com/yiisoft/yii2/commit/758f01934f180b4a4a47d36e1be103b1f979d76b#diff-b5d0ee8c97c7abd7e3fa29b9a27d1780L84
Just disable tests on PHP 5.4, which requires phpunit 4: https://github.com/yiisoft/yii2-httpclient/commit/e61daa63eca37f21daca1f9f79888ffa3ba5836d

What is the expected result?
DRY. There should be one package with phpunit-related classes. All potential improvements or fixes should be done there, not in each package separately.

Agree. https://github.com/yiisoft/yii2-phpunit

Not going to do it for 2.0.


[Medium] Issues with several webpages

3.1.125

bug occurs when LocatorsList was opened once and then hidden. no matter, by clear all or moving to page objects list

JDN v 3.1.125
Back-end v 2022-02-12-11.36.19
Chrome
done


cluster shutdown script

This should be simple, looks like we can just use the same ec2 module in Ansible, and set state=absent.
http://docs.ansible.com/ansible/latest/ec2_module.html
Before experimenting with this, let's make sure we've got termination protection on the important instances (namely osp-www), since a mistake here could take the public site offline.

Needs to cean up ebs volumes because it causes probem, see this log below:
fatal: [localhost]: FAILED! => {"changed": false, "failed": true, "msg": "wait for instances running timeout on Sat Dec 23 13:21:00 2017"}

...

Add Comment Collapse  This snippet was truncated for display: see it in full.

pete [12:24 PM]
@lily can you take a look at this when you're back online? happens consistently
have a good holiday until then
(guess that goes for EC2 as well!)
lily
[12:24 PM]
@pete this is bizarre nothing changed in scriptland since it was working hrm
I wonder if amazon is having troubles
„wait for instances running timeout on Sat Dec 23 13:21:00 2017"}”
Googled on phone: https://groups.google.com/forum/m/#!topic/ansible-project/QMmd53UalDU
pete [4:09 PM]
hmm, seems likely @lily https://console.aws.amazon.com/ec2/v2/home?region=us-east-1#Volumes:sort=desc:createTime
i thought i tell amazon to destroy ebs volumes when i terminate, but maybe that's just the root, or not happening for some reason
#90 shutdown script would be real helpful here
cleans them up
yup, that ws the problem

Actually cleaning up EBS problem isn't what I'd want in a shutdown script, I want:
https://stackoverflow.com/questions/45247521/how-to-set-delete-on-termination-for-boot-volume-in-ec2-volume-using-ansible

Regarding cleaning up EBS volumes: https://github.com/opensyllabus/osp-pipeline/commit/0b263be6b2460ff83c9962b82cc1c3898fc08ca6 (solved; no need to include cleaning of EBS volumes in script)

Okay I can do this pretty easily I just need to require awscli as a depend and use terminate-instances
http://docs.aws.amazon.com/cli/latest/reference/ec2/terminate-instances.html

Resolved in https://github.com/opensyllabus/osp-pipeline/releases/tag/v0.10.1


CUDA-Q

How can tequila implement support for CUDA-Q?
NVIDIA/cuda-quantum; CUDA-Q:

src: https://github.com/NVIDIA/cuda-quantum
docs: https://nvidia.github.io/cuda-quantum/latest/
docs: https://nvidia.github.io/cuda-quantum/latest/using/examples/introduction.html
docs: https://nvidia.github.io/cuda-quantum/latest/using/basics/kernel_intro.html :

What’s the difference between a quantum kernel and a quantum circuit?
Every quantum circuit is a kernel, but not every quantum kernel is a circuit.

docs: https://nvidia.github.io/cuda-quantum/latest/using/python.html
pypi: https://pypi.org/project/cudaq/

NVIDIA/cuda-q-academic: https://github.com/NVIDIA/cuda-q-academic :

https://github.com/NVIDIA/cuda-q-academic/blob/main/quick-start-to-quantum/01_quick_start_to_quantum.ipynb

Sources that may be useful:

https://github.com/tequilahub/tequila/tree/master/src/tequila/simulators/ simulator_cudaq.py ?

docs: https://nvidia.github.io/cuda-quantum/latest/api/default_ops.html

https://github.com/tequilahub/tequila/tree/master/src/tequila/ml

docs: https://nvidia.github.io/cuda-quantum/latest/using/integration/cuda_gpu.html

https://github.com/tequilahub/tequila/tree/master/src/tequila/optimizers

docs: https://nvidia.github.io/cuda-quantum/latest/examples/python/optimizers_gradients.html
docs: https://nvidia.github.io/cuda-quantum/latest/api/languages/python_api.html#optimizers

Hi,
the Cudaq support is currently being developed.
We hope it will be ready soon, but it will potentially still take a little time. Should be there at some point in December. I flag it here once online.
But if you want to try it yourself, you need to create a new backend in src/tequila/simulators derived from simulator_base.py. I would just check out how the qulacs backend is integrated.


LINK : fatal error LNK1181: cannot open input file 'Debug.lib'

I am trying to build the library, after having configured it using CMake. This is an incremental build log:
Build started...
1>------ Build started: Project: h5noop, Configuration: Debug x64 ------
2>------ Build started: Project: h5bzip2, Configuration: Debug x64 ------
3>------ Build started: Project: h5deflate, Configuration: Debug x64 ------
4>------ Build started: Project: h5fletcher32, Configuration: Debug x64 ------
5>------ Build started: Project: h5misc, Configuration: Debug x64 ------
6>------ Build started: Project: h5noop1, Configuration: Debug x64 ------
7>------ Build started: Project: h5shuffle, Configuration: Debug x64 ------
8>------ Build started: Project: h5unknown, Configuration: Debug x64 ------
9>------ Build started: Project: nczmisc, Configuration: Debug x64 ------
10>------ Skipped Build: Project: .distcheck, Configuration: Debug x64 ------
10>Project not selected to build for this solution configuration
11>------ Skipped Build: Project: .distdir, Configuration: Debug x64 ------
11>Project not selected to build for this solution configuration
12>------ Build started: Project: netcdf, Configuration: Debug x64 ------
13>------ Skipped Build: Project: Continuous, Configuration: Debug x64 ------
13>Project not selected to build for this solution configuration
14>------ Skipped Build: Project: Experimental, Configuration: Debug x64 ------
14>Project not selected to build for this solution configuration
15>------ Skipped Build: Project: NightlyMemoryCheck, Configuration: Debug x64 ------
15>Project not selected to build for this solution configuration
16>------ Skipped Build: Project: RUN_TESTS, Configuration: Debug x64 ------
16>Project not selected to build for this solution configuration
17>------ Skipped Build: Project: dist, Configuration: Debug x64 ------
17>Project not selected to build for this solution configuration
18>------ Skipped Build: Project: makeparser, Configuration: Debug x64 ------
18>Project not selected to build for this solution configuration
19>------ Skipped Build: Project: uninstall, Configuration: Debug x64 ------
19>Project not selected to build for this solution configuration
20>------ Skipped Build: Project: Nightly, Configuration: Debug x64 ------
20>Project not selected to build for this solution configuration
21>------ Skipped Build: Project: distcheck, Configuration: Debug x64 ------
21>Project not selected to build for this solution configuration
4>LINK : fatal error LNK1181: cannot open input file 'Debug.lib'
5>LINK : fatal error LNK1181: cannot open input file 'Debug.lib'
3>LINK : fatal error LNK1181: cannot open input file 'Debug.lib'
3>Done building project "h5deflate.vcxproj" -- FAILED.
1>LINK : fatal error LNK1181: cannot open input file 'Debug.lib'
1>Done building project "h5noop.vcxproj" -- FAILED.
8>LINK : fatal error LNK1181: cannot open input file 'Debug.lib'
8>Done building project "h5unknown.vcxproj" -- FAILED.
4>Done building project "h5fletcher32.vcxproj" -- FAILED.
5>Done building project "h5misc.vcxproj" -- FAILED.
2>LINK : fatal error LNK1181: cannot open input file 'Debug.lib'
2>Done building project "h5bzip2.vcxproj" -- FAILED.
9>LINK : fatal error LNK1181: cannot open input file 'Debug.lib'
9>Done building project "nczmisc.vcxproj" -- FAILED.
7>LINK : fatal error LNK1181: cannot open input file 'Debug.lib'
7>Done building project "h5shuffle.vcxproj" -- FAILED.
6>LINK : fatal error LNK1181: cannot open input file 'Debug.lib'
6>Done building project "h5noop1.vcxproj" -- FAILED.
12>LINK : fatal error LNK1104: cannot open file 'Debug.lib'
12>Done building project "netcdf.vcxproj" -- FAILED.
22>------ Build started: Project: ut_json, Configuration: Debug x64 ------
23>------ Build started: Project: ut_map, Configuration: Debug x64 ------
24>------ Build started: Project: C_tests_format, Configuration: Debug x64 ------
25>------ Build started: Project: C_tests_pres_temp_4D_rd, Configuration: Debug x64 ------
26>------ Build started: Project: C_tests_pres_temp_4D_wr, Configuration: Debug x64 ------
27>------ Build started: Project: C_tests_sfc_pres_temp_rd, Configuration: Debug x64 ------
28>------ Build started: Project: C_tests_sfc_pres_temp_wr, Configuration: Debug x64 ------
29>------ Build started: Project: C_tests_simple_xy_rd, Configuration: Debug x64 ------
30>------ Build started: Project: C_tests_simple_xy_wr, Configuration: Debug x64 ------
31>------ Build started: Project: ut_mapapi, Configuration: Debug x64 ------
32>------ Build started: Project: ut_projections, Configuration: Debug x64 ------
33>------ Build started: Project: zhex, Configuration: Debug x64 ------
34>------ Build started: Project: nc_test_tst_inq_type, Configuration: Debug x64 ------
35>------ Build started: Project: zisjson, Configuration: Debug x64 ------
36>------ Build started: Project: zmapio, Configuration: Debug x64 ------
37>------ Build started: Project: zs3parse, Configuration: Debug x64 ------
27>LINK : fatal error LNK1104: cannot open file 'Debug.lib'
27>Done building project "C_tests_sfc_pres_temp_rd.vcxproj" -- FAILED.
30>LINK : fatal error LNK1104: cannot open file 'Debug.lib'
30>Done building project "C_tests_simple_xy_wr.vcxproj" -- FAILED.
24>LINK : fatal error LNK1104: cannot open file 'Debug.lib'
24>Done building project "C_tests_format.vcxproj" -- FAILED.
25>LINK : fatal error LNK1104: cannot open file 'Debug.lib'
25>Done building project "C_tests_pres_temp_4D_rd.vcxproj" -- FAILED.
26>LINK : fatal error LNK1104: cannot open file 'Debug.lib'
26>Done building project "C_tests_pres_temp_4D_wr.vcxproj" -- FAILED.
22>LINK : fatal error LNK1104: cannot open file '..\liblib\Debug\netcdf.lib'
22>Done building project "ut_json.vcxproj" -- FAILED.
38>------ Build started: Project: bom, Configuration: Debug x64 ------
39>------ Build started: Project: nc_test, Configuration: Debug x64 ------
40>------ Build started: Project: nc_test_t_nc, Configuration: Debug x64 ------
41>------ Build started: Project: nc_test_tst_atts3, Configuration: Debug x64 ------
42>------ Build started: Project: nc_test_tst_def_var_fill, Configuration: Debug x64 ------
31>LINK : fatal error LNK1104: cannot open file '..\liblib\Debug\netcdf.lib'
31>Done building project "ut_mapapi.vcxproj" -- FAILED.
32>LINK : fatal error LNK1104: cannot open file '..\liblib\Debug\netcdf.lib'
32>Done building project "ut_projections.vcxproj" -- FAILED.
34>LINK : fatal error LNK1104: cannot open file 'Debug.lib'
34>Done building project "nc_test_tst_inq_type.vcxproj" -- FAILED.
33>LINK : fatal error LNK1104: cannot open file '..\liblib\Debug\netcdf.lib'
33>Done building project "zhex.vcxproj" -- FAILED.
28>LINK : fatal error LNK1104: cannot open file 'Debug.lib'
28>Done building project "C_tests_sfc_pres_temp_wr.vcxproj" -- FAILED.
23>LINK : fatal error LNK1104: cannot open file '..\liblib\Debug\netcdf.lib'
23>Done building project "ut_map.vcxproj" -- FAILED.
36>LINK : fatal error LNK1104: cannot open file '..\liblib\Debug\netcdf.lib'
36>Done building project "zmapio.vcxproj" -- FAILED.
43>------ Build started: Project: nc_test_tst_default_format, Configuration: Debug x64 ------
44>------ Build started: Project: nc_test_tst_err_enddef, Configuration: Debug x64 ------
45>------ Build started: Project: nc_test_tst_formats, Configuration: Debug x64 ------
46>------ Build started: Project: nc_test_tst_global_fillval, Configuration: Debug x64 ------
47>------ Build started: Project: nc_test_tst_max_var_dims, Configuration: Debug x64 ------
48>------ Build started: Project: nc_test_tst_meta, Configuration: Debug x64 ------
49>------ Build started: Project: nc_test_tst_misc, Configuration: Debug x64 ------
29>LINK : fatal error LNK1104: cannot open file 'Debug.lib'
29>Done building project "C_tests_simple_xy_rd.vcxproj" -- FAILED.
50>------ Build started: Project: nc_test_tst_names, Configuration: Debug x64 ------
51>------ Build started: Project: nc_test_tst_nofill, Configuration: Debug x64 ------
38>LINK : fatal error LNK1104: cannot open file '..\liblib\Debug\netcdf.lib'
38>Done building project "bom.vcxproj" -- FAILED.
35>LINK : fatal error LNK1104: cannot open file '..\liblib\Debug\netcdf.lib'
42>LINK : fatal error LNK1104: cannot open file 'Debug.lib'
42>Done building project "nc_test_tst_def_var_fill.vcxproj" -- FAILED.
52>------ Build started: Project: nc_test_tst_nofill2, Configuration: Debug x64 ------
35>Done building project "zisjson.vcxproj" -- FAILED.
53>------ Build started: Project: nc_test_tst_nofill3, Configuration: Debug x64 ------
40>LINK : fatal error LNK1104: cannot open file 'Debug.lib'
40>Done building project "nc_test_t_nc.vcxproj" -- FAILED.
39>LINK : fatal error LNK1104: cannot open file '..\liblib\Debug\netcdf.lib'
39>Done building project "nc_test.vcxproj" -- FAILED.
41>LINK : fatal error LNK1104: cannot open file 'Debug.lib'
41>Done building project "nc_test_tst_atts3.vcxproj" -- FAILED.
54>------ Build started: Project: nc_test_tst_norm, Configuration: Debug x64 ------
55>------ Build started: Project: nc_test_tst_small, Configuration: Debug x64 ------
56>------ Build started: Project: nc_test_tst_utf8_phrases, Configuration: Debug x64 ------
37>LINK : fatal error LNK1104: cannot open file '..\liblib\Debug\netcdf.lib'
37>Done building project "zs3parse.vcxproj" -- FAILED.
57>------ Build started: Project: nccopy, Configuration: Debug x64 ------
44>LINK : fatal error LNK1104: cannot open file 'Debug.lib'
44>Done building project "nc_test_tst_err_enddef.vcxproj" -- FAILED.
46>LINK : fatal error LNK1104: cannot open file 'Debug.lib'
46>Done building project "nc_test_tst_global_fillval.vcxproj" -- FAILED.
58>------ Build started: Project: ncdump, Configuration: Debug x64 ------
50>LINK : fatal error LNK1104: cannot open file 'Debug.lib'
50>Done building project "nc_test_tst_names.vcxproj" -- FAILED.
49>LINK : fatal error LNK1104: cannot open file 'Debug.lib'
49>Done building project "nc_test_tst_misc.vcxproj" -- FAILED.
59>------ Build started: Project: tst_zchunks, Configuration: Debug x64 ------
60>------ Build started: Project: ncfilteravail, Configuration: Debug x64 ------
48>LINK : fatal error LNK1104: cannot open file 'Debug.lib'
48>Done building project "nc_test_tst_meta.vcxproj" -- FAILED.
47>LINK : fatal error LNK1104: cannot open file 'Debug.lib'
47>Done building project "nc_test_tst_max_var_dims.vcxproj" -- FAILED.
43>LINK : fatal error LNK1104: cannot open file 'Debug.lib'
43>Done building project "nc_test_tst_default_format.vcxproj" -- FAILED.
45>LINK : fatal error LNK1104: cannot open file 'Debug.lib'
45>Done building project "nc_test_tst_formats.vcxproj" -- FAILED.
61>------ Build started: Project: ncgen, Configuration: Debug x64 ------
62>------ Build started: Project: ncgen3, Configuration: Debug x64 ------
63>------ Build started: Project: ncpathcvt, Configuration: Debug x64 ------
52>LINK : fatal error LNK1104: cannot open file 'Debug.lib'
52>Done building project "nc_test_tst_nofill2.vcxproj" -- FAILED.
64>------ Build started: Project: nctest, Configuration: Debug x64 ------
65>------ Build started: Project: nctrunc, Configuration: Debug x64 ------
66>------ Build started: Project: ncvalidator, Configuration: Debug x64 ------
67>------ Build started: Project: nczhdf5filters, Configuration: Debug x64 ------
53>LINK : fatal error LNK1104: cannot open file 'Debug.lib'
54>LINK : fatal error LNK1104: cannot open file 'Debug.lib'
53>Done building project "nc_test_tst_nofill3.vcxproj" -- FAILED.
54>Done building project "nc_test_tst_norm.vcxproj" -- FAILED.
68>------ Build started: Project: nczstdfilters, Configuration: Debug x64 ------
69>------ Build started: Project: ncdumpchunks, Configuration: Debug x64 ------
57>LINK : fatal error LNK1104: cannot open file '..\liblib\Debug\netcdf.lib'
57>Done building project "nccopy.vcxproj" -- FAILED.
58>LINK : fatal error LNK1104: cannot open file '..\liblib\Debug\netcdf.lib'
58>Done building project "ncdump.vcxproj" -- FAILED.
55>LINK : fatal error LNK1104: cannot open file 'Debug.lib'
55>Done building project "nc_test_tst_small.vcxproj" -- FAILED.
60>LINK : fatal error LNK1104: cannot open file '..\liblib\Debug\netcdf.lib'
60>Done building project "ncfilteravail.vcxproj" -- FAILED.
63>LINK : fatal error LNK1104: cannot open file '..\liblib\Debug\netcdf.lib'
63>Done building project "ncpathcvt.vcxproj" -- FAILED.
70>------ Build started: Project: ocprint, Configuration: Debug x64 ------
71>------ Build started: Project: rewrite-scalar, Configuration: Debug x64 ------
72>------ Build started: Project: s3util, Configuration: Debug x64 ------
73>------ Build started: Project: test_filter_avail, Configuration: Debug x64 ------
74>------ Build started: Project: test_quantize, Configuration: Debug x64 ------
75>------ Build started: Project: testfilter, Configuration: Debug x64 ------
65>LINK : fatal error LNK1104: cannot open file '..\liblib\Debug\netcdf.lib'
65>Done building project "nctrunc.vcxproj" -- FAILED.
66>LINK : fatal error LNK1104: cannot open file '..\liblib\Debug\netcdf.lib'
66>Done building project "ncvalidator.vcxproj" -- FAILED.
67>LINK : fatal error LNK1181: cannot open input file 'Debug.lib'
67>Done building project "nczhdf5filters.vcxproj" -- FAILED.
62>LINK : fatal error LNK1104: cannot open file '..\liblib\Debug\netcdf.lib'
62>Done building project "ncgen3.vcxproj" -- FAILED.
64>LINK : fatal error LNK1104: cannot open file '..\liblib\Debug\netcdf.lib'
64>Done building project "nctest.vcxproj" -- FAILED.
61>LINK : fatal error LNK1104: cannot open file '..\liblib\Debug\netcdf.lib'
61>Done building project "ncgen.vcxproj" -- FAILED.
76>------ Build started: Project: testfilter_misc, Configuration: Debug x64 ------
77>------ Build started: Project: testfilter_multi, Configuration: Debug x64 ------
78>------ Build started: Project: testfilter_order, Configuration: Debug x64 ------
79>------ Build started: Project: testfilter_repeat, Configuration: Debug x64 ------
80>------ Build started: Project: tst_chunkcases, Configuration: Debug x64 ------
81>------ Build started: Project: tst_dimsizes, Configuration: Debug x64 ------
51>LINK : fatal error LNK1104: cannot open file 'Debug.lib'
51>Done building project "nc_test_tst_nofill.vcxproj" -- FAILED.
68>LINK : fatal error LNK1181: cannot open input file 'Debug.lib'
68>Done building project "nczstdfilters.vcxproj" -- FAILED.
82>------ Build started: Project: tst_diskless, Configuration: Debug x64 ------
83>------ Build started: Project: tst_diskless3, Configuration: Debug x64 ------
69>LINK : fatal error LNK1104: cannot open file '..\liblib\Debug\netcdf.lib'
69>Done building project "ncdumpchunks.vcxproj" -- FAILED.
84>------ Build started: Project: tst_diskless4, Configuration: Debug x64 ------
85>------ Build started: Project: tst_diskless5, Configuration: Debug x64 ------
70>LINK : fatal error LNK1104: cannot open file '..\liblib\Debug\netcdf.lib'
70>Done building project "ocprint.vcxproj" -- FAILED.
75>LINK : fatal error LNK1104: cannot open file '..\liblib\Debug\netcdf.lib'
75>Done building project "testfilter.vcxproj" -- FAILED.
71>LINK : fatal error LNK1104: cannot open file '..\liblib\Debug\netcdf.lib'
71>Done building project "rewrite-scalar.vcxproj" -- FAILED.
86>------ Build started: Project: tst_fillbug, Configuration: Debug x64 ------
87>------ Build started: Project: tst_fillonlyz, Configuration: Debug x64 ------
78>LINK : fatal error LNK1104: cannot open file '..\liblib\Debug\netcdf.lib'
78>Done building project "testfilter_order.vcxproj" -- FAILED.
77>LINK : fatal error LNK1104: cannot open file '..\liblib\Debug\netcdf.lib'
77>Done building project "testfilter_multi.vcxproj" -- FAILED.
73>LINK : fatal error LNK1104: cannot open file '..\liblib\Debug\netcdf.lib'
73>Done building project "test_filter_avail.vcxproj" -- FAILED.
72>LINK : fatal error LNK1104: cannot open file '..\liblib\Debug\netcdf.lib'
72>Done building project "s3util.vcxproj" -- FAILED.
74>LINK : fatal error LNK1104: cannot open file '..\liblib\Debug\netcdf.lib'
74>Done building project "test_quantize.vcxproj" -- FAILED.
80>LINK : fatal error LNK1104: cannot open file '..\liblib\Debug\netcdf.lib'
80>Done building project "tst_chunkcases.vcxproj" -- FAILED.
88>------ Build started: Project: tst_inmemory, Configuration: Debug x64 ------
81>LINK : fatal error LNK1104: cannot open file '..\liblib\Debug\netcdf.lib'
81>Done building project "tst_dimsizes.vcxproj" -- FAILED.
89>------ Build started: Project: tst_nczfilter, Configuration: Debug x64 ------
90>------ Build started: Project: tst_open_mem, Configuration: Debug x64 ------
91>------ Build started: Project: tst_rename, Configuration: Debug x64 ------
92>------ Build started: Project: tst_utf8, Configuration: Debug x64 ------
93>------ Build started: Project: tst_zchunks2, Configuration: Debug x64 ------
94>------ Build started: Project: tst_zchunks3, Configuration: Debug x64 ------
95>------ Build started: Project: ut_chunking, Configuration: Debug x64 ------
82>LINK : fatal error LNK1104: cannot open file '..\liblib\Debug\netcdf.lib'
82>Done building project "tst_diskless.vcxproj" -- FAILED.
84>LINK : fatal error LNK1104: cannot open file '..\liblib\Debug\netcdf.lib'
84>Done building project "tst_diskless4.vcxproj" -- FAILED.
85>LINK : fatal error LNK1104: cannot open file '..\liblib\Debug\netcdf.lib'
85>Done building project "tst_diskless5.vcxproj" -- FAILED.
79>LINK : fatal error LNK1104: cannot open file '..\liblib\Debug\netcdf.lib'
79>Done building project "testfilter_repeat.vcxproj" -- FAILED.
76>LINK : fatal error LNK1104: cannot open file '..\liblib\Debug\netcdf.lib'
76>Done building project "testfilter_misc.vcxproj" -- FAILED.
87>LINK : fatal error LNK1104: cannot open file '..\liblib\Debug\netcdf.lib'
86>LINK : fatal error LNK1104: cannot open file '..\liblib\Debug\netcdf.lib'
87>Done building project "tst_fillonlyz.vcxproj" -- FAILED.
86>Done building project "tst_fillbug.vcxproj" -- FAILED.
89>LINK : fatal error LNK1104: cannot open file '..\liblib\Debug\netcdf.lib'
88>LINK : fatal error LNK1104: cannot open file '..\liblib\Debug\netcdf.lib'
89>Done building project "tst_nczfilter.vcxproj" -- FAILED.
94>LINK : fatal error LNK1104: cannot open file '..\liblib\Debug\netcdf.lib'
93>LINK : fatal error LNK1104: cannot open file '..\liblib\Debug\netcdf.lib'
88>Done building project "tst_inmemory.vcxproj" -- FAILED.
94>Done building project "tst_zchunks3.vcxproj" -- FAILED.
93>Done building project "tst_zchunks2.vcxproj" -- FAILED.
92>LINK : fatal error LNK1104: cannot open file '..\liblib\Debug\netcdf.lib'
92>Done building project "tst_utf8.vcxproj" -- FAILED.
95>LINK : fatal error LNK1104: cannot open file '..\liblib\Debug\netcdf.lib'
95>Done building project "ut_chunking.vcxproj" -- FAILED.
91>LINK : fatal error LNK1104: cannot open file '..\liblib\Debug\netcdf.lib'
91>Done building project "tst_rename.vcxproj" -- FAILED.
90>LINK : fatal error LNK1104: cannot open file '..\liblib\Debug\netcdf.lib'
90>Done building project "tst_open_mem.vcxproj" -- FAILED.
96>------ Skipped Build: Project: INSTALL, Configuration: Debug x64 ------
96>Project not selected to build for this solution configuration
97>------ Skipped Build: Project: PACKAGE, Configuration: Debug x64 ------
97>Project not selected to build for this solution configuration
========== Build: 0 succeeded, 84 failed, 7 up-to-date, 13 skipped ==========

I took a look at https://github.com/Unidata/netcdf-c/blob/main/plugins/CMakeLists.txt, and I can't figure out where requirement for Debug.lib comes from.
My CMake settings are attached: CMakeCache.txt
This happens with both v4.9.0 and main (5ebc855ed665c0d13dd86e937043fb07031cb827). Win10 x64, version 21H2 (build 19044.1865). Visual Studio 2019, v16.11.17.
RelWithDebInfo configuration also wants Debug.lib.

What happens if you try building with Release configuration? It's not immediately obvious to me why this is happening, either, and I'm curious if it goes away if you build without debug info.

It wanted Debug.lib in Release mode too.
But I figured out where this comes from. In the CMake setting ZLIB_LIBRARY I initially typed Debug;C:/Misc/zlib-ng-19/Debug/zlibstaticd.lib;Optimized;C:/Misc/zlib-ng-19/RelWithDebInfo/zlibstatic.lib. It turns out case matters: this put both Debug.lib and Optimized.lib on the link line. Changing it to debug;C:/Misc/zlib-ng-19/Debug/zlibstaticd.lib;optimized;C:/Misc/zlib-ng-19/RelWithDebInfo/zlibstatic.lib resolves this problem.

Thank you; that is a great data point that could crop up again in the future.  Thanks for sharing the solution you discovered!


Implement query to assess lazy-loaded LCP image fix opportunity

Fixes #8
Inspired by https://discuss.httparchive.org/t/lazy-loaded-lcp-images-by-wordpress-version/2455/2, this query allows to assess the opportunity of fixing the remaining problems where WordPress sites lazy-load their LCP image.
The query includes the opportunity relative to the number of WordPress sites that actually have an LCP image, but also relative to the total number of WordPress sites. For reference, the query also shows the number of sites on a WordPress version greater than or equal to 5.5, since that is when lazy-loading was introduced in WordPress core.
Query results

Row
client
with_lazyloaded_lcp_image
with_lcp_image
total_wp_sites
pct_lcp_image_opportunity
pct_total_opportunity
wp_gte_55

1
desktop
321428
1503774
3502837
0.21374754451134279
0.091762191617822925
3164718

2
mobile
434920
2092115
5465547
0.20788532179158412
0.079574834870142
4857803

Based on October 2022 dataset

@felixarntz The query is more significant than 1 TB of data processing, so I haven't run it, but it looks good. Thank you!


Added adminapi generic route

:+1:

@ronaldbaltus I can't merge this, but I can publish it.  :)

@RWOverdijk That would be great! Than I am able to update the NPM package myself :)


Arrange changelogs

Proposed Release Notes

Arranged changelogs for monorepo and sub-repos.

Links

https://github.com/newrelic/newrelic-node-log-extensions/pull/7

Details
This PR modifies the top-level changelog and adds two other changelogs, one for each of the log enrichers. This allows us to track monorepo-level changes, such as new workflows, separately from changes to specific sub-packages, such as bugfixes or new features. Here I build upon the work of @bizob2828 in https://github.com/newrelic/newrelic-node-log-extensions/pull/7

However, I don't see any value in one at the root as there isn't any code that ships.

Fair enough! I wasn't sure if we'd want something there to track changes to the monorepo. I can update this PR and push it back.


level.open() is not a function

When wrapping my leveldb in sublevel I can no longer reopen the database. Am I missing something?

Okay fixed it by just closing and recreating the database. But maybe this is an opportunity to document that one doesn't get a leveldb with just something added to it. There are actual API differences like open() not being present and the promise feature beeing broken because callbacks are added even when none are provided.

the promise feature beeing broken because callbacks are added even when none are provided

Are you referring to the promise support in recent level(up)? Because level-sublevel follows the old levelup API.
You might want to look at subleveldown as an alternative to level-sublevel.

@vweevers actually yes. I didn't notice that this library isn't compatible with recent versions of level(up)(-rocksdb). Thinks for the hint to subleveldown.


Set server image entrypoint to yarn

Overview
Updates the Docker ENTRYPOINT for the server image to yarn, allowing us to start the container in production with the command run start:prod. We no longer need to override the entrypoint in the Fargate task definition.
Notes
This was mentioned in #142 when overriding the entrypoint to run yarn instead of the parent image node entrypoint.
Testing Instructions

Confirm that the Jenkins build passes.
Run scripts/update locally and confirm that all updates succeed.
Run scripts/test locally and confirm that all tests run and continue to pass.
Run scripts/server locally and confirm that all application containers come up, that the application is running in development mode, and that the application is available at http://localhost:3005.
Confirm that the staging site at https://staging.districtbuilder.azavea.com is up and accessible.

Closes #148

Ugh, whoops, fixed that in the most recent commit.


Dev Version

Describe the bug
My point is that the version with the Airplane and Pufferfish patch port is not stable and should not be used. This is my review of it. I tested this immediately on the primary server 6g6s.org and noticed the appearance of frequent server crashes
To Reproduce
Crash - https://hastebin.app/62b87f2dd5c6ab001c626995
Crash2 - https://hastebin.app/62b87f60d5c6ab001c626996
Stable happened 3-4 times a day, but after I returned the version from the releases, it did not happen anymore
Plugins

Version
Build Dev with the latest changes

/timings on causes huge lags, which is not the case in the normal version


Django Import Exports fails for MongoDB

import-export is working for Mysql but fails for MongoDb.
Does this package supports Mongo?
or is there any additional requirement?
The error is same as in issue:
https://github.com/django-import-export/django-import-export/issues/811

It's not supported - only Mysql, Postgres and sqlite are covered in the tests.
You could search the past issues (if not already) to see if anyone has been successful in integrating with other dbs.  Maybe this a good starting point?

Thank You @matthewhegarty . I will sure check it.


Fix the output directory

According to the documentation of the recent version of sbt, the output directory should be a subdirectory of the sourceManaged in Compile, and not be the sourceManaged in Compile itself.
For multiple projects, sbt-idea excludes the directory from the list of source directories without conforming to this.
References:
http://www.scala-sbt.org/0.13.1/docs/Howto/generatefiles.html
https://github.com/mpeltonen/sbt-idea/issues/209
https://github.com/sbt/sbt-scalabuff/pull/6

Implemented here: https://github.com/sbt/sbt-fmpp/commit/49efb76d4ab9fb76560ff909a79a533d3879b7e0#diff-edb75f36c67c796ff2a0fc30437c4b4f53ba507d030c7d0a74a97c2054258b69R67


Add explicit partition numbers

Currently, partition numbers are inferred by their position in the partitions array in the plugin config. This means that you must add all partitions up to and including the partition you want to control via HomeKit.
It would be helpful if we could add an optional number field to the partition object to allow configuration like this:

"partitions": [
                {
                    "name": "3rd Floor",
                    "number": 4
                }
            ],

Instead of:

"partitions": [
                {
                    "name": "Common"
                },
                {
                    "name": "1st Floor"
                },
                {
                    "name": "2nd Floor"
                },
                {
                    "name": "3rd Floor"
                }
            ],

In the above example, I only want HomeKit control of the 3rd floor partition. Currently, I'm forced to also add the Common, 1st Floor, and 2nd Floor partitions to HomeKit in order to add the 3rd Floor partition. This adds clutter to HomeKit with unneeded accessories. It also means that the home-wide security system status requires all partitions to be armed in order to show as armed, for example.

Hi,
I don't have a multiple partition configuration, so I have no way of testing the final outcome. I added new optional field called "partitionNumber". Please confirm it is working before I add the options in the official build and UI configuration file.  Just replace index.js with the  posted version in GitHub.
Example
"partitions": [
{
"name": "3rd Floor",
"partitionNumber": 4
}
],

That works for my needs. 👍
One thing I've noticed though is that Homebridge is not receiving the partition status change update in response to a request to arm/disarm from within HomeKit.  I'm guessing it might have something to do with my multi-partition setup (I've got a vista FB128 panel with 5 of the 8 total partitions configured). I haven't been able to pinpoint the exact cause just yet though. I'm going to file a separate issue to track that.
Thanks for your quick response!

Hi,
Looked over the code again,  its seem their a few spots that also need to modify based on adding this option.  I will post once those changes are made and you can test.  I believe all the changes will be contained in the index.js.

Awesome. Thanks a lot!

Hi,
Posted an updated index.js which should correct the partition update.

I'm seeing the following error message:
TypeError: Cannot read property 'processingAlarm' of undefined
    at EnvisalinkPlatform.systemUpdate (/usr/local/lib/node_modules/homebridge-envisalink-ademco/index.js:191:24)
    at EnvisaLink.emit (events.js:400:28)
    at updateKeypad (/usr/local/lib/node_modules/homebridge-envisalink-ademco/envisalink.js:478:15)
    at Socket.<anonymous> (/usr/local/lib/node_modules/homebridge-envisalink-ademco/envisalink.js:137:23)
    at Socket.emit (events.js:400:28)
    at addChunk (internal/streams/readable.js:293:12)
    at readableAddChunk (internal/streams/readable.js:267:9)
    at Socket.Readable.push (internal/streams/readable.js:206:10)
    at TCP.onStreamRead (internal/stream_base_commons.js:188:23)

Hi,
Posted another index.js with enhance error trapping.  I believe what occurred is the plug-in got an update from a non registered partition (which will happened since we can skip partitions now) and wasn't able to process the data. I fix the code so it check to assure that it is a register partition before it process the updates and simply ignore the rest.
I have also made few other changes, since you indicated your using 128 panel, which this plug-in wasn't original written to support, base on the document there are some minor items how to send bypass commands.
To active the new section of code change the deviceType field in Configuration file
"deviceType": "128FBP",
The new config.schema.json has also been posted to manage the partition and devices type using the UI.

Thanks for that. I installed and tested it. It looks like the partition updates are working following commands, so that's great. There might be something else going on though since shortly after disarming my partition HomeKit reports the security system as being armed￼ again.

Hmm...

Does Homekit clear arm state and few sec late go back to arm and later disarm again? If this is the case the command timeout value (commandTimeOut) is too short. The log file should also give warning that this occured.
Are any of the other partition armed?

It displays the arm state shortly after arming/disarming. This is an improvement over what it used to do, which was just sit there saying "arming..." or "disarming...". Shortly after, the status changes.

I believe it switches to reporting the armed state of partition 1, in my case, our common area. Perhaps it is reading the state from the virtual keypad updates?

Hi,

I posted another Index.js tonight, its cleanup and optimization coding so don't believe it will correct the issue. But at least we will be running the same code base.
The best course of action is turn on debug in Homebridge (under Homebridge setting in UI)  and provide the output when you arm and disarm. In debug it will provide the raw output from Envisakit module and updates. With raw output hopefully will be able determine why you are getting another update.  Please indicate which partition you want to be monitoring in Homekit.

Hey there, sorry for the late reply. I did some troubleshooting and discovered that the Envisalink.partitions property is what is causing my alarm system status in HomeKit (which should only be the 3rd partition) to show the status of the common (1st) partition.

Hi,
Looking over the section of logging, it wasn't what was there -- but absence of log data. It seem there is a hold over attribute when I initial created this module that was never removed from the core engine. It could be root of these issues with update since that attribute was the definition for the number of partitions and default to 1 and suppress some other non primary update from the Envisalink device.  I have removed the attribute from the core engine. Here are the step to update. This time you will need replace Envisalink.js and index.js file with one I have posted. You should now see more events being generated with debug.
Do following test and provide the output (if they fail)

From keypad arm any partition other than the one being monitored. (Nothing should happened to monitored partition).
Disarm from the keypad any partition other than the one being monitored.  (Nothing should happened to monitored partition).
From keypad arm the one being monitored. (Monitored partition should change).
From Keypad disarm the one being monitored. (Monitored partition should change).
From Homekit Arm and Disarm (Monitored partition should change).

I am also making assumption that Envisalink module is already configure to access all partition.
Please note, was working few new features so we may see battery status now and other detail in HomeKit. Still testing those...so they can be ignored rights.


remote debugger

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

VS Code Version: 1.72.2
OS Version: amazon linux

Steps to Reproduce:

create npm with typescript on remote system
start the application with a break point. the Program doesn't halt at the breakpoint

Please give just more details about exactly what you are doing, include the log
/jsDebugLogs

/jsDebugLogs

I guess the bot is asleep, I'll post the steps manually
Please collect trace logs using the following instructions:

If you're able to, add "trace": true to your launch.json and reproduce the issue. The location of the log file on your disk will be written to the Debug Console. Share that with us.
⚠ This log file will not contain source code, but will contain file paths. You can drop it into https://microsoft.github.io/vscode-pwa-analyzer/index.html to see what it contains. If you'd rather not share the log publicly, you can email it to<EMAIL_ADDRESS>

I think the issue was with my configuration file, sorry for the bother.


Release of a world map

I recently got a dedicated server aimed at producing a world map. I still encounter some issues with the geometries of some relations in planet.osm.pbf, hence the small fixes here and there and the increase in the number of releases.
The preliminary results are very encouraging. A planet database import take about 24hours and the time taken to index the data is about the same. More details will be posted here soon.

Better late than never, here is the url of the demo. https://demo.baremaps.com/
I still have a couple of problems at low zoom levels (the vector tiles are too big), but overall it looks great.


Model-level notifications

What are you changing in this pull request and why?
Beta docs for model-level notifications

[x] New page
[x] Update sidebar so new page is below Job notifications page

Checklist

[x] I have reviewed the Content style guide so my content adheres to these guidelines.
[x] The topic I'm writing about is for specific dbt version(s) and I have versioned it according to the version a whole page and/or version a block of content guidelines.
[ ] Needs PM review

ADDING PAGE (if so, uncomment):

[x] Add/remove page in website/sidebars.js
[x] Provide a unique filename for new pages

At a high level, depending on the UI settings, users can choose to be notified on -
For models: fail/success
For tests on models: fail/success/warn
The UI setting applies for both models and tests, we don't differentiate them in the backend. When users receive an email, the email will say whether it is for a model/test.


[: =: unary operator expected when disconnected from internet

Alas, once again I feel the burn of making an over complicated bash script, so now I get to over-complicate it more.
When attempting to grab weather while offline, this error is thrown:
/usr/bin/confetch: line 176: [: =: unary operator expected

/usr/bin/confetch: line 225: [: =: unary operator expected
Here's the weather in  (As of 1 hour ago):

Uhh, so my proposed solution: lines 176 and 225 don't run the online function, so they run regardless if its online or not. So, put down a check that executes the script if its online. This is an easy fix, the code's already in the file, it just needs some copy pasting and indenting.

Fixed in main branch with Revision 8-1.


⚠ Bofrost.es has degraded performance

In ec95f78, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1353 ms

Resolved: Bofrost.es performance has improved in d9a541e after 6 minutes.


hooks for temporary tables in the catalog

Is your feature request related to a problem or challenge?
While trying to return an explicit error to clarify the semantics of temporary tables in #12363, it was suggested that it might be a good idea to semantically distinguish temporary tables in the catalog, while strictly speaking this behaviour is/already exists in that DF's tables support this behaviour.
Describe the solution you'd like
I would like to clearly define the semantics of a temporary table in the catalog.
Describe alternatives you've considered
No response
Additional context
No response

How about adding a flag on the appropriate DdlStatement
https://docs.rs/datafusion/latest/datafusion/logical_expr/enum.DdlStatement.html
So for example, that would mean adding a temporary flag to structures like CreateMemoryTable, CreateExternalTable, etc
https://docs.rs/datafusion/latest/datafusion/logical_expr/struct.CreateMemoryTable.html
If we wanted we could plumb that information into the memory catalog implementation that comes with DataFusion or we could potentially simply error if it appears (and let users of DataFusion define the semantics)

take


Contact Info - Updated labels and styling

Issue #: /bcgov/entity#10613
Description of changes:

Added label prop to override the contact information descriptor
updated stories

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the business-filings-ui license (Apache 2.0).

LGTM. Proceed when you're happy with your changes.
PS unit tests?

Updated!


Complex Text Layouts: Label's Percent Visible property does not follow RTL text orientation

Godot version
4.0.dev
System information
Linux Manjaro, i7-8550U, Vulkan
Issue description
in arabic Percent Visible should delete from left to right:
Steps to reproduce

Minimal reproduction project
No response

Fixed by https://github.com/godotengine/godot/pull/52860


BugFix - fix build_local_test_elfs.sh not copying app-ethereum

fix build_local_test_elfs.sh to copy app-ethereum.elf into plugin's tests/elfs/

Thank your for pointing this bug out. We've also encountered it, alongside with another one (the plugin-tools environment which is advised on our developer portal ).
They are addressed in this PR.

Closing as equivalent fix was merged here. Thanks again for the bump!


wasm web-sys support

Hi, and thanks for this useful library!
What would make it even more useful to me is if worked on the web (wasm32-unknown-unknown), probably using window.performance.memory.usedJSHeapSize.

Blocked on https://github.com/rustwasm/wasm-bindgen/issues/3159

WASM support also sounds useful to me, so feel free to shoot a PR when that gets unblocked!
(sorry for the late response I've been busy with college)

This is now unblocked:
https://docs.rs/web-sys/latest/web_sys/struct.Performance.html#method.measure_user_agent_specific_memory
Note that it is chrome-only, and behind the web_sys_unstable_apis feature flag.
Anways, I don't have time to work on this right now, but I'm leaving this here for someone else, or for future me :)

I'm slightly hesitant to include this API in memory-stats right now, since it is both unstable and vendor-specific; that being said at least #8 should unblock building on WASM right now


Topic list: Fix wrong markup output of nested lists

My correct view.php output (inspect element)

a

    b

b-1

b-2

            BB

BB1

BB2

c

** I dont know if the parent li should be clickable (in the code is clickable)

Benefits: :)

Correct/valid nested lists markup
"has-children" - Add "ccm-block-topic-list-topic-parent" (If you want to add css class to the "parent" li item)
Add ccm-block-topic-nested-list-list (If you want to add css class to the nested ul list. A lot of times you need this for accordions and nested dropdowns list).
Human readable separation of the "regular li" and "parent li and nested ul" items. Like this its easy to change the markup for some boostrap/foundaion/other libary...accordions and dropdown markup (add/change classes, remove href, change the href to "#" and so on).

The core view.php wrong output (Not valid and not in the correct topic structure).
a
b
b-1
b-2
BB
BB1
BB2

                c

I think we need a few more eyes on this to verify it. Plus the whitespacing is pretty off, so if that could be corrected that would be helpful.

You right about of the white space (some of that is because this "copy and paste" to this editor).
I add one more "clever version" (i dont want to create "new" issue). This is very similar to the first version only with multi D array instead of "hardcore" classes.
In this example i use this "multi D arrays" -
http://codepen.io/siton/full/PzGpOP/
I think its nice concept because the "topic-list" its little "hard" to change block (Not like "feature block" for example and other blocks).

This pull request needs to be rebased and reopened because we did some history rewriting, if you need help with this head into #dev in our slack channel
#4814


Add template docstrings for functions and methods

From<EMAIL_ADDRESS>on 2015-02-16T11:46:01Z
I would love if spyder could help docstring-ing a module by passing through the code and suggesting template
before:
=======
def f(x,y):
z=x&y
return(z)
after:
======
def f(x,y = 2):
# TODO: f takes x and y and return z
# parameters
# ----------
# x - TODO: describe what x is
# y - TOOD: describe what y is (default value 2)
There is a package that does it but it would be nice if this is embedded in Spyder GUI https://github.com/dadadel/pyment
Original issue: http://code.google.com/p/spyderlib/issues/detail?id=2177

From ccordoba12 on 2015-02-16T11:36:14Z
Good idea. But someone would need to step up and implement it :-)
Summary: Add template docstrings for functions and methods  <span class="oldvalue"> (was: feature request: docstrings automation) </span>
Status: HelpNeeded
Labels: -Type-Defect Type-Enh Cat-Editor

this sound like something for a plugin :)

There is a similar functionality/plugin in PyCharm - worth to check before implementation in Spyder. Btw, as a further development, there should be a check for consistency (at least between number of parameters)

@rlaverde if you want to work on something, this could be a good idea :-)