Adjustments for theming changes in AngularJS Material 1.2.0

Based on https://github.com/angular/material/pull/11376 (and likely some other PRs), there may need to be some adjustments to this library for it to keep working with AngularJS Material 1.2.0. This issue is to keep track of any of those issues and remember to put out a new release of this library when (or soon after) AngularJS Material 1.2.0 is released.

[16:27:57]: Retrieved versions from AngularJS Material docs (12x)
[16:27:59]: Successfully built 1.2.1.
[16:28:01]: Successfully built 1.1.26.
[16:28:02]: Successfully built 1.1.25.
[16:28:04]: Successfully built 1.2.0.
[16:28:06]: Successfully built 1.2.0-rc.2.
[16:28:08]: Successfully built 1.2.0-rc.1.
[16:28:09]: Successfully built 1.1.24.
[16:28:09]: Using AngularJS Material version from cache.
[16:28:10]: Successfully built 1.1.23.
[16:28:10]: Using AngularJS Material version from cache.
[16:28:10]: Successfully built 1.1.22.
[16:28:10]: Using AngularJS Material version from cache.
[16:28:10]: Successfully built 1.1.22-rc.0.
[16:28:10]: Using AngularJS Material version from cache.
[16:28:10]: Successfully built 1.1.21.
[16:28:10]: Using AngularJS Material version from cache.
[16:28:10]: Successfully built 1.1.20.
[16:28:10]: Successfully tested the tool against all supported versions.

The 1.2.x releases seem to be working with this tool so far (at least according to the tests).

As mentioned in https://github.com/angular/material-tools/issues/44#issuecomment-719045563, 1.1.23 changed a couple .scss files to be Sass partials. That issue is fixed and now the minimum version supported in 1.1.23.
However, there is another exception listed in that comment that needs to be investigated. It may related to the 1.2.x changes.

722f08e797ef8b6b5d08005565729673dc460767 fixed an issue with the original code, so it wasn't due to 1.2.0.
I think that we're clear of 1.2.0 issues at this point with 1.0.0-rc.3. If some user testing on that goes well, we'll cut 1.0.0 and close this issue.

Verified in https://github.com/angular/material-tools/issues/44#issuecomment-720899390 that the latest RC works with a real app using AngularJS Material 1.2.x.


Feature request: Forcing order of in text citations

At present, multiple BibTex keys within a Markdown document are rendered alphabetically.
For instance,
[@sloman_two_2002; @sloman_empirical_1996; @darlow_two_2010].
is rendered as

(Darlow & Sloman, 2010; Sloman, 1996, 2002).

However, there are cases when it's desirable to override this, for example, it would be preferable to be able to enter
Sloman's [-@sloman_empirical_1996; -@sloman_two_2002; @darlow_two_2010] dual process theory
and render it as

Sloman's (1996; 2002; Darlow & Sloman, 2010) dual process theory

At present, because Darlow comes before Sloman alphabetically, this renders instead as

Sloman's (Darlow & Sloman, 2010; 1996; 2002) dual process theory

An obvious workaround is to enter the citation manually, taking advantage of the fact that numbers come before letters "alphabetically", and use nocite fields
Sloman's [1996; 2002; @darlow_two_2010] dual process theory

---
nocite: @sloman_empirical_1996, @sloman_two_2002
...

...but it might be possible to implement an override in pandoc directly?

@nickbart, do you know if this is determined by the CSL style and configurable there?

There's an old, but possibly related discussion on the Zotero forum here.

Also, digging around this a little, I've found the relevant part of the CSL specification.
Specifically, most styles, including APA.csl,
have a section as follows, specifying to sort citations by author,
and then by date
<sort>
    <key macro="author" names-min="3" names-use-first="3"/>
    <key variable="issued" sort="descending"/>
</sort>

The key question, which is beyond my knowledge of Pandoc, Haskell, or CSL, is if there's a way to override this for a specific section of the text, as changing this globally would be clearly undesirable.

+++ Eoin Travers [Jan 13 15 09:01 ]:

The key question, which is beyond my knowledge of Pandoc, Haskell, or
CSL, is if there's a way to override this for a specific section of the
text, as changing this globally would be clearly undesirable.

No, not currently.  Since you're going for an author-in-text
citation, have you tried this format?
@citemefirst [pp. 37; @citemenext, p. 40]

I think that would force @citemefirst to be first,
and outside the parens.

Correct. Thanks. I hadn't realized that Pandoc was this intelligent with regards to square brackets, etc.
@sloman_empirical_1996 [-@sloman_two_2002; @darlow_two_2010] theory

Sloman (1996, 2002; Darlow & Sloman, 2010) theory

This doesn't solve the problem I had wished to avoid by forcing citations to display in order though, but which probably lies outside of this feature request - handling of possessive apostrophes:
Sloman's [-@sloman_empirical_1996] [-@sloman_two_2002; @darlow_two_2010] theory

Sloman's (1996) (Darlow & Sloman, 2010; 2002) theory

For the time being, I'll stick to my original solution, using the nocite feature.

So this seems to be mostly solved already. Just to confirm, as far as I know, there is no way of overriding the sort instructions given in <citation ...><sort>...</sort>... ... ...</citation> for a specific section of the text. Some popular styles like chicago-author-date.csl or chicago-fullnote-bibliography.csl do not use any sorting for in-text citations, in line with what the Chicago Manual says in “15.29 Multiple text references”:

Two or more references in a single parenthetical citation are separated by semicolons. The order in which they are given may depend on what is being cited, and in what order, or it may reflect the relative importance of the items cited. If neither criterion applies, alphabetical or chronological order may be appropriate. Unless the order is prescribed by a particular journal style, the decision is the author’s.

So if you want this kind of flexibilty, I'd say, just get rid of the <sort>...</sort> element inside <citation>.

Yup, losing the \<sort>...\</sort> tags seems to be the only way preserve the order.
As an exercise/distraction from writing, I put together a python script to manually sort citations, except for those containing a <!--NOSORT--> comment, mimicing to a certain level of precision the behaviour of apa.csl, but allowing an override.
https://gist.github.com/EoinTravers/33dfcd76714405a4e9c1
This might be of interest to anyone coming across this issue - unfortunately, I have 0 Haskall skills, so I can't offer to try to implement anything similar within Pandoc.

Probably worth implementing it as a pandoc filter, see jgm/pandocfilters for relevant stuff (and my own pandoc-filters repo for more examples)

Closing this, as it seems resolved.


Mention the need for classical register name in SamplerV2

URL, if applicable

[x] https://docs.quantum.ibm.com/api/migration-guides/v2-primitives#steps-to-migrate-to-sampler-v2

[x] https://docs.quantum.ibm.com/run/primitives-get-started#4-invoke-the-sampler-and-get-results

Describe the new content you are requesting.
The output of SamplerV2 is grouped by the names of the classical registers in the input circuit. The default is meas if measure_all() is used, but it's c if measure() is used. This has caused some confusion with the users. #1088 has this note

We should add this so the general SamplerV2 docs as well.
If this new content request is accepted, do you want to write the content?
I can help the team by providing enough information to write the material

These topics all have the note added:

migration-guides/qiskit-runtime-examples
migration-guides/qiskit-runtime-use-case
migration-guides/v2-primitives (2 locations)
run/primitives-examples
run/primitives

These changes will all be part of https://github.com/Qiskit/documentation/pull/1088 and will go live on Monday


Removing 3 extra references to jquery

You were loading the same version of jQuery 4 times. I removed 3 of the references to reduce unneeded browser requests and thus making your site load faster :).

Thanks, Adizam. It was in the html5 boilerplate


CLOUDSTACK-9230: Remove unnecessary return statement from cloudStack.js

Removed the unnecessary return statement.
The statement is never reached.

LGTM, this return statement is immediately following another return statement and is thus unreachable.

LGTM, makes sense. Checked syntax and that is also still OK.


joint_state_broadcaster build failed

It's similar to this issue, except c++-8 replaced with c++7 here. I hope this info will be helpfull for debugging.
commits, that works for me:
fake_joint             - a96af50 (HEAD -> foxy, origin/foxy) Fix the spin rate (#3)
geo shapes             - ebfc30d (HEAD -> ros2) [fix] cmake install command (#164)
moveit2                - ea62dbc6d (HEAD -> main, origin/main, origin/HEAD) MTC compatibility fixes (#323)
moveit_msgs            - 51c9a51 (HEAD -> ros2, tag: 2.0.0) 2.0.0
moveit_resources       - e512345 (HEAD -> ros2, tag: 2.0.0) 2.0.0
ros2_control           - 2c3aad1 (HEAD) New version of component parser (#127)
ros2_controllers       - 8587e07 (HEAD) [Ready] Port over interpolation formulae, abort if goals tolerance violated (#62)
srdfdom                - f77799c (HEAD -> ros2, tag: 2.0.0) 2.0.0
warehouse_ros          - d5bd4cc (HEAD -> ros2, tag: 2.0.0) 2.0.0
warehouse_ros_mongo    - 3a69993 (HEAD -> ros2, tag: 2.0.0) 2.0.0

last commits (that fails to build):
geo_shapes             - da52ff8 (HEAD -> ros2, tag: 2.0.2, origin/ros2) 2.0.2
moveit2                - c029942db (HEAD -> main, origin/main, origin/HEAD) Temporarily disable flaky OMPL test (#495)
moveit_msgs            - 53b8ddf (HEAD -> ros2, tag: 2.0.1, origin/ros2) 2.0.1
moveit_resources       - 8d245f8 (HEAD -> ros2, origin/ros2) Add Galactic CI (#80)
ros2_control           - e980718 (HEAD -> master, origin/master, origin/HEAD) Remove forgoten debug output (#439)
ros2_controllers       - df5a5fa (HEAD -> master, origin/master, origin/HEAD) Fix rolling build (#200)
srdfdom                - ed8e5ed (HEAD -> ros2, origin/ros2) Add Galactic CI (#87)
warehouse_ros          - ec9fb64 (HEAD -> ros2, origin/ros2) Fix building on windows (#73)
warehouse_ros_mongo    - 0d0efa5 (HEAD -> ros2, origin/ros2) Add rolling CI (#56)

Used build instructions:
source /opt/ros/foxy/setup.bash && \
mkdir -p moveit2_ws/src && \
cd moveit2_ws/src && \
wget https://raw.githubusercontent.com/ros-planning/moveit2/main/moveit2.repos && \
vcs import < moveit2.repos && \
rosdep update && \
rosdep install -r --from-paths . --ignore-src --rosdistro foxy -y && \
cd .. && \
colcon build --cmake-args -DCMAKE_BUILD_TYPE=Release

Result:
Starting >>> controller_manager_msgs
Starting >>> ros2_control_test_assets
Starting >>> moveit_resources_fanuc_description
Starting >>> moveit_resources_panda_description
Starting >>> moveit_resources_pr2_description
Starting >>> warehouse_ros
Starting >>> geometric_shapes
Starting >>> moveit_msgs
Finished <<< ros2_control_test_assets [0.55s]
Finished <<< moveit_resources_panda_description [0.55s]
Finished <<< moveit_resources_fanuc_description [0.58s]
Starting >>> hardware_interface
Starting >>> moveit_resources_fanuc_moveit_config
Starting >>> moveit_resources_panda_moveit_config
Finished <<< moveit_resources_pr2_description [0.63s]
Starting >>> srdfdom
Finished <<< warehouse_ros [0.65s]
Starting >>> warehouse_ros_mongo
Finished <<< geometric_shapes [0.99s]
Finished <<< moveit_resources_fanuc_moveit_config [0.61s]
Finished <<< moveit_resources_panda_moveit_config [0.61s]
Starting >>> moveit_resources
Finished <<< hardware_interface [0.69s]
Finished <<< srdfdom [0.64s]
Starting >>> controller_interface
Starting >>> transmission_interface
Finished <<< controller_manager_msgs [1.37s]
Finished <<< warehouse_ros_mongo [0.68s]
Finished <<< moveit_resources [0.27s]
Finished <<< transmission_interface [0.29s]
Finished <<< controller_interface [0.32s]
Starting >>> controller_manager
Finished <<< controller_manager [0.36s]
Starting >>> forward_command_controller
Starting >>> joint_state_broadcaster
Starting >>> diff_drive_controller
Starting >>> joint_trajectory_controller
Starting >>> ros2controlcli
Starting >>> gripper_controllers
Finished <<< forward_command_controller [0.80s]
Starting >>> effort_controllers
Starting >>> position_controllers
Finished <<< diff_drive_controller [0.88s]
Starting >>> velocity_controllers
Finished <<< joint_trajectory_controller [1.49s]
Finished <<< gripper_controllers [1.59s]
Finished <<< ros2controlcli [1.61s]
Starting >>> ros2_control
Finished <<< ros2_control [0.04s]
Finished <<< moveit_msgs [5.72s]
--- stderr: joint_state_broadcaster
In file included from /usr/include/x86_64-linux-gnu/c++/7/bits/c++allocator.h:33:0,
                 from /usr/include/c++/7/bits/allocator.h:46,
                 from /usr/include/c++/7/string:41,
                 from /usr/include/c++/7/stdexcept:39,
                 from /usr/include/c++/7/array:39,
                 from /usr/include/c++/7/tuple:39,
                 from /usr/include/c++/7/functional:54,
                 from /home/dalek/development/deps/moveit_ws/src/ros2_controllers/joint_state_broadcaster/test/test_joint_state_broadcaster.cpp:17:
/usr/include/c++/7/ext/new_allocator.h: In instantiation of ‘class __gnu_cxx::new_allocator<const char* const>’:
/usr/include/c++/7/bits/allocator.h:108:11:   required from ‘class std::allocator<const char* const>’
/usr/include/c++/7/bits/stl_vector.h:81:14:   required from ‘struct std::_Vector_base<const char* const, std::allocator<const char* const> >::_Vector_impl’
/usr/include/c++/7/bits/stl_vector.h:166:20:   required from ‘struct std::_Vector_base<const char* const, std::allocator<const char* const> >’
/usr/include/c++/7/bits/stl_vector.h:216:11:   required from ‘class std::vector<const char* const, std::allocator<const char* const> >’
/opt/ros/foxy/src/gmock_vendor/include/gmock/gmock-matchers.h:3168:26:   required from ‘class testing::internal::ElementsAreArrayMatcher<const char* const>’
/home/dalek/development/deps/moveit_ws/src/ros2_controllers/joint_state_broadcaster/test/test_joint_state_broadcaster.cpp:278:5:   required from here
/usr/include/c++/7/ext/new_allocator.h:93:7: error: ‘const _Tp* __gnu_cxx::new_allocator<_Tp>::address(__gnu_cxx::new_allocator<_Tp>::const_reference) const [with _Tp = const char* const; __gnu_cxx::new_allocator<_Tp>::const_pointer = const char* const*; __gnu_cxx::new_allocator<_Tp>::const_reference = const char* const&]’ cannot be overloaded
       address(const_reference __x) const _GLIBCXX_NOEXCEPT
       ^~~~~~~
/usr/include/c++/7/ext/new_allocator.h:89:7: error: with ‘_Tp* __gnu_cxx::new_allocator<_Tp>::address(__gnu_cxx::new_allocator<_Tp>::reference) const [with _Tp = const char* const; __gnu_cxx::new_allocator<_Tp>::pointer = const char* const*; __gnu_cxx::new_allocator<_Tp>::reference = const char* const&]’
       address(reference __x) const _GLIBCXX_NOEXCEPT
       ^~~~~~~
In file included from /opt/ros/foxy/src/gmock_vendor/include/gmock/gmock-spec-builders.h:73:0,
                 from /opt/ros/foxy/src/gmock_vendor/include/gmock/gmock-generated-function-mockers.h:46,
                 from /opt/ros/foxy/src/gmock_vendor/include/gmock/gmock-function-mocker.h:4,
                 from /opt/ros/foxy/src/gmock_vendor/include/gmock/gmock.h:61,
                 from /home/dalek/development/deps/moveit_ws/src/ros2_controllers/joint_state_broadcaster/test/test_joint_state_broadcaster.cpp:23:
/opt/ros/foxy/src/gmock_vendor/include/gmock/gmock-matchers.h: In instantiation of ‘testing::internal::ElementsAreArrayMatcher<T> testing::ElementsAreArray(std::initializer_list<_Tp>) [with T = const char* const]’:
/home/dalek/development/deps/moveit_ws/src/ros2_controllers/joint_state_broadcaster/test/test_joint_state_broadcaster.cpp:278:5:   required from here
/opt/ros/foxy/src/gmock_vendor/include/gmock/gmock-matchers.h:3555:47: error: could not convert ‘testing::ElementsAreArray(Iter, Iter) [with Iter = const char* const*; typename std::iterator_traits<_Iterator>::value_type = const char*](xs.std::initializer_list<const char* const>::end())’ from ‘testing::internal::ElementsAreArrayMatcher<const char*>’ to ‘testing::internal::ElementsAreArrayMatcher<const char* const>’
   return ElementsAreArray(xs.begin(), xs.end());
                                               ^
In file included from /usr/include/x86_64-linux-gnu/c++/7/bits/c++allocator.h:33:0,
                 from /usr/include/c++/7/bits/allocator.h:46,
                 from /usr/include/c++/7/string:41,
                 from /usr/include/c++/7/stdexcept:39,
                 from /usr/include/c++/7/array:39,
                 from /usr/include/c++/7/tuple:39,
                 from /usr/include/c++/7/functional:54,
                 from /home/dalek/development/deps/moveit_ws/src/ros2_controllers/joint_state_broadcaster/test/test_joint_state_broadcaster.cpp:17:
/usr/include/c++/7/ext/new_allocator.h: In instantiation of ‘void __gnu_cxx::new_allocator<_Tp>::deallocate(__gnu_cxx::new_allocator<_Tp>::pointer, __gnu_cxx::new_allocator<_Tp>::size_type) [with _Tp = const char* const; __gnu_cxx::new_allocator<_Tp>::pointer = const char* const*; __gnu_cxx::new_allocator<_Tp>::size_type = long unsigned int]’:
/usr/include/c++/7/bits/alloc_traits.h:462:9:   required from ‘static void std::allocator_traits<std::allocator<_CharT> >::deallocate(std::allocator_traits<std::allocator<_CharT> >::allocator_type&, std::allocator_traits<std::allocator<_CharT> >::pointer, std::allocator_traits<std::allocator<_CharT> >::size_type) [with _Tp = const char* const; std::allocator_traits<std::allocator<_CharT> >::allocator_type = std::allocator<const char* const>; std::allocator_traits<std::allocator<_CharT> >::pointer = const char* const*; std::allocator_traits<std::allocator<_CharT> >::size_type = long unsigned int]’
/usr/include/c++/7/bits/stl_vector.h:180:19:   required from ‘void std::_Vector_base<_Tp, _Alloc>::_M_deallocate(std::_Vector_base<_Tp, _Alloc>::pointer, std::size_t) [with _Tp = const char* const; _Alloc = std::allocator<const char* const>; std::_Vector_base<_Tp, _Alloc>::pointer = const char* const*; std::size_t = long unsigned int]’
/usr/include/c++/7/bits/stl_vector.h:162:22:   required from ‘std::_Vector_base<_Tp, _Alloc>::~_Vector_base() [with _Tp = const char* const; _Alloc = std::allocator<const char* const>]’
/usr/include/c++/7/bits/stl_vector.h:435:33:   required from ‘std::vector<_Tp, _Alloc>::~vector() [with _Tp = const char* const; _Alloc = std::allocator<const char* const>]’
/opt/ros/foxy/src/gmock_vendor/include/gmock/gmock-matchers.h:3152:7:   required from here
/usr/include/c++/7/ext/new_allocator.h:125:19: error: invalid conversion from ‘const void*’ to ‘void*’ [-fpermissive]
  ::operator delete(__p);
  ~~~~~~~~~~~~~~~~~^~~~~
In file included from /usr/include/c++/7/functional:53:0,
                 from /home/dalek/development/deps/moveit_ws/src/ros2_controllers/joint_state_broadcaster/test/test_joint_state_broadcaster.cpp:17:
/usr/include/c++/7/new:124:6: note:   initializing argument 1 of ‘void operator delete(void*)’
 void operator delete(void*) _GLIBCXX_USE_NOEXCEPT
      ^~~~~~~~
In file included from /usr/include/c++/7/memory:64:0,
                 from /home/dalek/development/deps/moveit_ws/src/ros2_controllers/joint_state_broadcaster/test/test_joint_state_broadcaster.cpp:18:
/usr/include/c++/7/bits/stl_construct.h: In instantiation of ‘void std::_Construct(_T1*, _Args&& ...) [with _T1 = const char* const; _Args = {const char* const&}]’:
/usr/include/c++/7/bits/stl_uninitialized.h:83:18:   required from ‘static _ForwardIterator std::__uninitialized_copy<_TrivialValueTypes>::__uninit_copy(_InputIterator, _InputIterator, _ForwardIterator) [with _InputIterator = __gnu_cxx::__normal_iterator<const char* const*, std::vector<const char* const, std::allocator<const char* const> > >; _ForwardIterator = const char* const*; bool _TrivialValueTypes = false]’
/usr/include/c++/7/bits/stl_uninitialized.h:134:15:   required from ‘_ForwardIterator std::uninitialized_copy(_InputIterator, _InputIterator, _ForwardIterator) [with _InputIterator = __gnu_cxx::__normal_iterator<const char* const*, std::vector<const char* const, std::allocator<const char* const> > >; _ForwardIterator = const char* const*]’
/usr/include/c++/7/bits/stl_uninitialized.h:289:37:   required from ‘_ForwardIterator std::__uninitialized_copy_a(_InputIterator, _InputIterator, _ForwardIterator, std::allocator<_Tp>&) [with _InputIterator = __gnu_cxx::__normal_iterator<const char* const*, std::vector<const char* const, std::allocator<const char* const> > >; _ForwardIterator = const char* const*; _Tp = const char* const]’
/usr/include/c++/7/bits/stl_vector.h:331:31:   required from ‘std::vector<_Tp, _Alloc>::vector(const std::vector<_Tp, _Alloc>&) [with _Tp = const char* const; _Alloc = std::allocator<const char* const>]’
/opt/ros/foxy/src/gmock_vendor/include/gmock/gmock-matchers.h:3152:7:   required from here
/usr/include/c++/7/bits/stl_construct.h:75:13: error: invalid static_cast from type ‘const char* const*’ to type ‘void*’
     { ::new(static_cast<void*>(__p)) _T1(std::forward<_Args>(__args)...); }
             ^~~~~~~~~~~~~~~~~~~~~~~
make[2]: *** [CMakeFiles/test_joint_state_broadcaster.dir/build.make:82: CMakeFiles/test_joint_state_broadcaster.dir/test/test_joint_state_broadcaster.cpp.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:255: CMakeFiles/test_joint_state_broadcaster.dir/all] Error 2
make: *** [Makefile:160: all] Error 2
---
Failed   <<< joint_state_broadcaster [11.3s, exited with code 2]
Aborted  <<< effort_controllers [12.6s]
Aborted  <<< position_controllers [24.0s]
Aborted  <<< velocity_controllers [26.3s]

Summary: 23 packages finished [29.7s]
  1 package failed: joint_state_broadcaster
  3 packages aborted: effort_controllers position_controllers velocity_controllers
  1 package had stderr output: joint_state_broadcaster
  2 packages not processed

The package builds fine on our various CI builds and the ros build farm. The problem is likely your setup. I suggest installing binaries for foxy,saves you a lot of time.

There is only source build instructions for moveit2, where are the binaries?
I used g++ 7.5 and cmake 3.19.2 for building.

I believe I have the default installation
$ g++ --version
g++ (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0

and
$ cmake --version
cmake version 3.16.3

for binaries follow the ROS2 Foxy guide:
https://index.ros.org/doc/ros2/Installation/Foxy/Linux-Install-Binary

Problem was gcc, g++ version, all works good with 9.3.0


And the documentation is WHERE?

There is no WIKI available at the link. OK I have successfully installed the plugin but there is absolutely no description of how to work with it. I tried several websocket clients and they get disconnected by server or not connecting at all. Please provide docs, thank you!

Use the V1.0.0_rc-1. It's a match more polished version.
The plugin is in a client configuration , so you need to use a server that accept any connexion request at the used port. When connected , the plugin will start sending the last received message..
Check the readme.md, it was updated to include match more informations.
Please let me know if you still have a problem after that.


Add support for posix_spawn_file_actions_addchdir_np on available Linux platforms

This adds support for workingDirectory APIs for TSCBasic.Process on Linux if the system where the library is compiled with has libc6 >= 2.29. Uses the __GLIBC_PREREQ(2, 29) as per @jakepetroules 's suggestion on #69
Because there are no compile time checks for this version on Swift, I had to add runtime support for the failure mode where the posix_spawn_file_actions_addchdir_np is not available.

@swift-ci test

Tested this using Docker on Ubuntu 20.04 where 2.31 is the default and on Ubuntu 18.04 where the max available version is 2.27 (which doesn't have this API)

@swift-ci test

@swift-ci test


Add styled scoreboard below arena

Added styled scoreboard below the game arena
Team's color corresponds to score
Closes #28

looks really good. I'm going to go ahead and merge


Upload results to file service and update results file with id and status

Signed-off-by: Richard Marston<EMAIL_ADDRESS>

This closes #6 and #7


chore(main): release 1.8.2

:robot: I have created a release beep boop
1.8.2 (2024-07-02)
Code Refactoring

improve constructor and start methode of servermanager with no parameter (3c81d5c)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/Andesite-Lab/Core/releases/tag/v1.8.2 :sunflower:


Release Google.Cloud.Filestore.V1 version 2.6.0

Changes in this release:
New features

Add IServiceCollection extension methods for client registration where an IServiceProvider is required. (commit 022fab2)

Created release for Google.Cloud.Filestore.V1-2.6.0


Add to DRF's Third Party Resources

Great work on this, would love to see a PR adding this to http://www.django-rest-framework.org/topics/third-party-resources/#other-resources

Thanks, will do!

https://github.com/tomchristie/django-rest-framework/pull/2963
merged


Add govulncheck to Go Tests workflow

Adds a govulncheck step to the Go Tests workflow to add an extra check against known vulnerabilities.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

Waiting on the workflow to run on my local branch to make sure it's happy, do not merge yet

Example Output on my fork:
Run go install golang.org/x/vuln/cmd/govulncheck@latest
go: downloading golang.org/x/vuln v1.0.1
go: downloading golang.org/x/mod v0.12.0
go: downloading golang.org/x/tools v0.12.1-0.20230815132531-74c255bcf84[6](https://github.com/jrmccluskey/beam/actions/runs/6027684665/job/16353404191#step:10:7)
Scanning your code and [7](https://github.com/jrmccluskey/beam/actions/runs/6027684665/job/16353404191#step:10:8)[8](https://github.com/jrmccluskey/beam/actions/runs/6027684665/job/16353404191#step:10:9)3 packages across 85 dependent modules for known vulnerabilities...

No vulnerabilities found.

Share feedback at https://go.dev/s/govulncheck-feedback.

R: @lostluck


Scanner area when setting scaleY parameter

When we set the scaleY parameter, real scanned area zone seems to be translated under the viewFinder rectangle. This make the scanner difficult to use.

@jeremybviseo you could try and use branch version-2 which is a rewrite to not use dm77/barcodescanner anymore as with a project of mine there was an error in a part of the library which I could not fix easily. In this implementation the whole area is used to detect codes. To use it you can include the following in your package.json:
"react-native-barcodescanner": "git+https://github.com/ideacreation/react-native-barcodescanner/#version-2",

hope that helps.

@jeremybviseo I have merged the version-2 branch into master and fixed import statement problems and a black screen after reloading the js. The version is published to npm. It would be awesome if you could close this issue when no problems remain.


Score audio file

Hello, thank for your sharing this repo
How can I pass an audio file. The output is the score of the audio file: accuracy, completeness, fluency, prosodic and total
Thank you!

II have the same issue. Have you resolved it?

Thank you for the question!
We used the same dataset as the baseline model, GOPT. Please download and configure the data in the same way as this repository: https://github.com/YuanGongND/gopt/tree/master/data.
To use your audio dataset other than the speechocean762, generate the Godness of Pronunciation (GOP) features first and then convert the features to sequences for model input, as described in the aforementioned repository.

Thank you!


Change Resource Bundle from class to ResourceBundle property file

Example on how to do this https://docs.oracle.com/javase/tutorial/i18n/resbundle/examples/PropertiesDemo.java

https://docs.oracle.com/javase/tutorial/i18n/


ci: Upload coverage report

This will attach a code coverage report to PRs and to nightly tests,
both specifically from Chrome on Linux.  Reports will be attached to
workflow runs whether or not the tests pass.

This needs more work.  I'm testing the workflow change on the PR, though, so I'm going to leave it active while I make changes.

This is working now!  PTAL.

Ping!  Please take a look.  I'd love to start collecting coverage data for our project health metrics.


could we support to start two dbeaver on the same server?

Hi Expert,
could you help to answer two questions? very appreciated.

could we support to start two dbeavers on the same server?
I try to start two dbeavers on my mac book, below error is reported. " Can not lock the same workspace".
Can we specify the workspace when we start the dbeaver like we start the eclipse.

why do we have two connection when we connect to posgres?

Please check the code below , one for main context ,one for metacontext
void checkInstanceConnection(@NotNull DBRProgressMonitor monitor, boolean cacheMetadata) throws DBException {
    if (!isSharedDatabase() && executionContext == null) {
        initializeMainContext(monitor);
        initializeMetaContext(monitor);
        if (cacheMetadata)
            cacheDataTypes(monitor, true);
    }
}

For the first question , i tried two ways on my mc book
add the below params in the dbeaver.init, it can not work
-data /Users/niubaoke/Library/DBeaverData/workspace1
but it can work with command line params
./dbeaver -data "/Users/niubaoke/Library/DBeaverData/workspace1"

That symbol has nothing to do with different new line between platforms. like I said, that symbol is used on windows, linux, and macos when viewing the compact form (as a table column).
You can double click on that line to show the actual query properly.
I'm guessing that's because the table doesn't support multi line for fields. But if you feel that's a problem, open a bug report for it. don't reuse the same issue. This one is tracking your suggestion for multiple workspaces.

I think we should add an option to choose the workspace as Eclipse does.

@janiu-001 To answer your question about adding required workspace in dbeaver.ini you need to add this argument at the beginning of the file and also include newline after -data so it looks kind of like this
-data
/Users/niubaoke/Library/DBeaverData/workspace1
-startup
plugins/org.eclipse.equinox.launcher_1.6.300.v20210813-1054.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.win32.win32.x86_64_1.2.300.v20210828-0802
-vmargs
-XX:+IgnoreUnrecognizedVMOptions
--add-modules=ALL-SYSTEM
-Dosgi.requiredJavaVersion=11
-Xms128m
-Xmx2048m

Also workspace could be changed in the main menu File->Switch workspace
Does this issue still actual for the latest DBeaver version?

It's been a while since no update here. If the issue is still actual please let me know and provide additional information.


metering not reporting non openshift namespaces

report is generated only for ocp namespaces like
default, openshift-console, openshift-metering, openshift-sdn, openshift-web-console  but not for custom namespaces that i have created.   how do i tell metering to monitor all namespaces?

@debianmaster Where you able to get this working? The other thing it could be is that you don't have anything scheduled/running in non openshift namespaces, but that would be difficult I feel since openshift does run the registry and router in the default namespace.

i tested again and this does not work,  metering only reports openshift specific namespaces
prometheus shows them all


Bump included cypress image to match NPM version

NB: The NPM package is actually on v9.7.0, but ≥9.5.4 upgrades Chrome to v100 and does not run in GitHub Actions (perhaps due to memory problems?)
#patch

Codecov Report

Merging #50 (c2dcb36) into main (00460fb) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #50   +/-   ##
=======================================
  Coverage   79.60%   79.60%
=======================================
  Files          21       21
  Lines         461      461
=======================================
  Hits          367      367
  Misses         60       60
  Partials       34       34

Continue to review full report at Codecov.

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


Security: Switch to audited secp256k1 implementation

https://github.com/paulmillr/noble-curves provide audited, fast, tree-shakeable, esm-compatible secp256k1 implementation.
Your current implementation seems to be using elliptic? Which is not actively maintained.
If you want users to use safe, audited code, then switch is the way.

I would second @paulmillr 's comments.
Block / TBD is in need of a maintained and audited ECIES library and would welcome the opportunity to collaborate on updating this package to use @noble/curves.

@frankhinek I updated to use @noble/curves.
@paulmillr Since I didn't find any util function for converting compressed/uncompressed format, I had to use a trick like
    this.uncompressed = Buffer.from(secp256k1.getSharedSecret(ONE, buffer, false));
    this.compressed = Buffer.from(secp256k1.getSharedSecret(ONE, buffer, true));

const uncomp = secp256k1.getSharedSecret(ONE, buffer, false);
const comp = secp256k1.Point.fromHex(unc).toRawBytes(true);


ButtonRectangle espresso click action

ButtonRectangle doesn't get clicked when using espresso.
onView(withId(R.id.enterBtn)).perform(click());

Here's what happens

It stays like that, and test times out

Yes, I have noticed the same issue. Is there a workaround or a fix in the horizon?
I really hope testing is taken much more seriously, as far as I am concerned, this is a showstopper, it's pretty but broken.

It's not perfect, but I've been calling the onClick function directly (specified in my layout xml) instead of via the button.
e.g. for the following (simplified) xml:
<ButtonRectangle
            android:id="@+id/register"
            android:layout_width="fill_parent"
            android:layout_height="wrap_content"
            android:onClick="signupWithEmail">

I'll just do the following in my test:
mainActivity.getActivity().signupWithEmail(null);
instead of the usual:
onView(withId(R.id.register)).perform(click());

Hi @jaydeep17, @andrewcross and @appmath,
I have managed to create a workaround for this library to disable button ripple effect when the app is under test.
My workaround requires that a indicator class named 'TestingIndicator', be created within the 'src/androidTest' folder whose classes are only loaded when app is being tested. This class must have package name the same as that of the app under test.
When a button (extends CustomView) is instantiated, we check for presence of 'TestingIndicator' using Class.forName method. If it exists, set variable to define app is under test and from that variable, disable ripple effect.
See commit here to my fork:
https://github.com/wilson208/MaterialDesignLibrary/commit/2450808b99e51413404d4b62dcb27b0b0bbbccb2
I am looking for your guys opinions as to whether this is a viable solution to create a pull request, I know its a little hacky but cant think of another way to do this at the moment.
Wilson.

Any update with this? considering changing buttons over this issue.


Updated check for button visibility instead of window width.

PR for check on button visibility instead of width.
Allows user the ability to change the width at which the widget changes.

Thanks again for this and the other PR @ZenHarbinger

No problem!


the "-enc" string in powershell commands is being flagged by a/v as bad.

This may explain why "some stuff doesn't work", as it's likely a/v is killing the command behind the scenes.
Recommend changing it to "-EncodedCommand", that seems to fix it.

At this point, we don't want to get into a race with every AV engine that's out there. If you want to change the launching parameters yourself, you can do so in helpers.py.


Fix CI errors for MFAZones pull requests

Make PR CI checks green. for example: https://github.com/pondersource/mfazones/pull/10

All checks are green now for these PRs:

https://github.com/pondersource/mfazones/pull/10
https://github.com/pondersource/mfazones/pull/11


Downloading from nrk.no broken

youtube-dl https://tv.nrk.no/serie/vera/KOIF28002115/sesong-6/episode-1
[NRKTV] KOIF28002115: Downloading webpage
[NRKTV] KOIF28002115: Downloading f4m manifest
[NRKTV] KOIF28002115: Downloading m3u8 information
WARNING: Your copy of avconv is outdated and unable to properly mux separate video and audio files, youtube-dl will download single file media. Update avconv to version 10-0 or newer to fix this.
[download] Destination: Vera-KOIF28002115.mp4
WARNING: Your copy of avconv is outdated, update avconv to version 10-0 or newer if you encounter any errors.
avconv version 0.8.17-6:0.8.17-2, Copyright (c) 2000-2014 the Libav developers
built on Mar  2 2016 22:53:14 with gcc 4.7.2
Unrecognized option 'headers'
Failed to set value 'Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip, deflate
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,/;q=0.8
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0) Gecko/20150101 Firefox/44.0 (Chrome)
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Cookie: alid=7xTJhe3wFC5ayFXFG0IurQ==
' for option 'headers'
ERROR: ffmpeg exited with code 1

WARNING: Your copy of avconv is outdated, update avconv to version 10-0 or newer if you encounter any errors.


automation, Align sig-operator in automation scripts

Align sig-operator as the other sigs in
automation/test.sh script.
This way it can set TARGET as
k8s-1.x-sig-operator.
Signed-off-by: Or Shoval<EMAIL_ADDRESS>None

/lgtm

@fgimenez can you take a look on this one please ?
prerequisites of https://github.com/kubevirt/project-infra/pull/1547

/retest

/approve
/hold
Waiting for another reviewer

Lets remove the hold ? Federico reviewed
thanks

/retest
/unhold


Plans to generate a GFA?

Hi,
Do you have any plans to produce a GFA output instead of a Fasta? it would be a natural way to represent the full graph with adjacency information betw unitigs
Thanks

Hello all, is this solved? Also want to do dome downstream analysis but I learned that GFA format is widely used for this purpose. Thanks! Jianshu

Hi, now GGCAT supports the output of uncolored graphs to gfa format, using the flag --gfa

Hi how about colored， no gfa support right？
Thanks，
Jianshu

It would be extremely valuable to have gfa support in color mode and we can then easily compare with other c-DBG tools.
Best,
Jianshu


about trainning

hello, I wonder how to train your model and evaluate, looking forward to your reply.

Currently, we don't plan to release the training code, but may upload the that someday. The training code of ISVI is quite similar to FGT, you can modify the training code from FGT to train ISVI.
As for evaluation, as the paper indicates, we adopt PSNR, SSIM and LPIPS as the objective metrics. We utilize the corresponding functions from scikit-image to measure PSNR and SSIM, and the official repository to measure LPIPS.


BaseNDArray.detach() can cause invalid shape information

Reproduce using:
https://github.com/deeplearning4j/deeplearning4j/blob/6335b5e933f13d2bdb5c1f7e5896c45eb96839d7/deeplearning4j-core/src/test/java/org/deeplearning4j/nn/graph/graphnodes/TestGraphNodes.java#L542
Due to detach here:
https://github.com/deeplearning4j/deeplearning4j/blob/268a87e093ca81510fb95ab8bd08fe0a1ec34642/deeplearning4j-nn/src/main/java/org/deeplearning4j/nn/graph/ComputationGraph.java#L1808
Before detach:

After detach:

Full stack trace:
java.lang.IndexOutOfBoundsException: 160

	at org.bytedeco.javacpp.indexer.Indexer.checkIndex(Indexer.java:90)
	at org.bytedeco.javacpp.indexer.DoubleRawIndexer.get(DoubleRawIndexer.java:59)
	at org.nd4j.linalg.api.buffer.BaseDataBuffer.getDouble(BaseDataBuffer.java:959)
	at org.nd4j.linalg.api.shape.Shape.getDouble(Shape.java:435)
	at org.nd4j.linalg.api.ndarray.BaseNDArray.getDouble(BaseNDArray.java:1756)
	at org.nd4j.linalg.api.ndarray.BaseNDArray.getDouble(BaseNDArray.java:3770)
	at org.nd4j.linalg.string.NDArrayStrings.format(NDArrayStrings.java:114)
	at org.nd4j.linalg.string.NDArrayStrings.format(NDArrayStrings.java:128)
	at org.nd4j.linalg.string.NDArrayStrings.format(NDArrayStrings.java:96)
	at org.nd4j.linalg.string.NDArrayStrings.format(NDArrayStrings.java:92)
	at org.nd4j.linalg.api.ndarray.BaseNDArray.toString(BaseNDArray.java:4980)
	at org.deeplearning4j.nn.graph.graphnodes.TestGraphNodes.testLastTimeStepWithTransfer(TestGraphNodes.java:589)

I believe this started after the following PR was merged (but not 100% sure). It was about that time, however.
https://github.com/deeplearning4j/nd4j/pull/2600

Hypothetically fixed. Please confirm.

Confirmed fixed


Accounts with a username that starts with a number are buggy

Contact Details
No response
What happened?
When you create an account and pick a username starting with a number, you can never see your profile, and some other functionallities are buggy.

What browsers are you seeing the problem on?
No response
Relevant log output
No response
Are you interested in contributing?

[X] I'd like to work on this issue

Code of Conduct

[X] I have used the search function to check if an issue already exists
[X] I agree to follow this project's Code of Conduct

I've made a pull request here: #799

@holopin-bot @youssefjaziri456 bug-hunter


Fabric-client and fabric-ca-client are not correctly installed!

Context

when i git clone the caliper and cd caliper, then i

When i try to show my fabric-client and fabric-ca-client, i see this

I know that there must be something wrong with my fabric-client and fabric-ca-client, but i don't know how to fix it. Is there anyone who has some ideas, thanks in advance!
Expected Behavior

Fabric-client and fabric-ca-client are correctly installed and i can run the example by node main.js
Actual Behavior

fabric-client and fabric-ca-client are  not correctly installed and i cannot run the example by node main.js
Possible Fix

Maybe reinstalling the fabric-client and fabric-ca-client helps
Existing issues

GitHub Issues

@aklenik

The node main.js ... approach has been gone a long time ago. Now Caliper offers a CLI to start your tests, either when installed through npm/docker or using the source code directly.
Check out the docs for the various ways to install/bootstrap Caliper: https://hyperledger.github.io/caliper/vLatest/installing-caliper/

Ok and thanks a lot! @

Ok and thanks a lot!


[ISSUE #8765] fix low performance of delay message when enable rocksdb consume queue

Which Issue(s) This PR Fixes

Fixes #8765
Brief Description

How Did You Test This Change?

Codecov Report
Attention: Patch coverage is 52.50000% with 19 lines in your changes missing coverage. Please review.

Project coverage is 47.35%. Comparing base (daf3d1a) to head (20faf8e).

Files with missing lines
Patch %
Lines

...ache/rocketmq/store/queue/RocksDBConsumeQueue.java
52.50%
13 Missing and 6 partials :warning:

Additional details and impacted files
@@              Coverage Diff              @@
##             develop    #8766      +/-   ##
=============================================
- Coverage      47.51%   47.35%   -0.17%
+ Complexity     11591    11548      -43
=============================================
  Files           1282     1282
  Lines          89848    89884      +36
  Branches       11557    11565       +8
=============================================
- Hits           42692    42565     -127
- Misses         41931    42062     +131
- Partials        5225     5257      +32

Flag
Coverage Δ

47.35% <52.50%> (-0.17%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

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

@yuz10 Is there profiling metrics verifying that prefetch actually improves perf?

@yuz10 Is there profiling metrics verifying that prefetch actually improves perf?

The performance loss is not related to prefetching. The schedule message deliver speed is 160/s because every time the iterator only returns 16 messages, and the deliver thread will sleep 100ms

@lizhanhui I found no difference between batch and single get key from rocksdb. I will remove prefetch code.
Batch:
QueryCQ iter 10489877 cost 20527
QueryCQ iter 10489877 cost 19496
QueryCQ iter 10489877 cost 19395
Single:
QueryCQ iter 10489877 cost 20313
QueryCQ iter 10489877 cost 19196
QueryCQ iter 10489877 cost 18945

@yuz10 Got your update and review it tomorrow.

The performance loss is not related to prefetching. The schedule message deliver speed is 160/s because every time the iterator only returns 16 messages, and the deliver thread will sleep 100ms after iterate finish. See org.apache.rocketmq.broker.schedule.ScheduleMessageService.DeliverDelayedMessageTimerTask#executeOnTimeUp

The original implementation uses one-shot(at most 16 results) multi-get to simulate iterator; The outcome iterator fails to return all results, thus, does not fit well for the mentioned use case;
You change is to use lazy single get to iterate; and use potential pre-fetch to accelerate;
A third option is to directly wrap RocksIterator with prefix;

It would be best to make further comparisons in terms of performance(why multi-get at present), code maintenance, ...
After all pros and cons are clarified, we may finalize this pull request.
Another issue is option 2, aka, this pull request, changes original behavior. We need to verify the change does not impact semantics of upper layer code bases.

The original implementation uses one-shot(at most 16 results) multi-get to simulate iterator; The outcome iterator fails to return all results, thus, does not fit well for the mentioned use case;
You change is to use lazy single get to iterate; and use potential pre-fetch to accelerate;
A third option is to directly wrap RocksIterator with prefix;

It would be best to make further comparisons in terms of performance(why multi-get at present), code maintenance, ... After all pros and cons are clarified, we may finalize this pull request.
Another issue is option 2, aka, this pull request, changes original behavior. We need to verify the change does not impact semantics of upper layer code bases.

I did not compare the performance of RocksIterator with current solution, It can be optimized later, the current solution just deals with the issue of delay message. Another solustion is not to sleep 100ms after each iteration.
As for the behavior, the default ConsumeQueue only iters one file, the RocksDBConsumeQueue only iters at most 16 items. so I think the behavior is not defined about how many items the iteration returns. and will not impact upper layer code.

@lizhanhui I found no difference between batch and single get key from rocksdb. I will remove prefetch code. Batch: QueryCQ iter 10489877 cost 20527 QueryCQ iter 10489877 cost 19496 QueryCQ iter 10489877 cost 19395
Single: QueryCQ iter 10489877 cost 20313 QueryCQ iter 10489877 cost 19196 QueryCQ iter 10489877 cost 18945

Take a look at this blog, MultiGet has quite a few optimizations available, we shall have two options to investigate:
1, Simulated manual iterator with multi-get in the background, to prefetch accordingly;
2, Use RocksDB embedded Iterator;
https://rocksdb.org/blog/2022/10/07/asynchronous-io-in-rocksdb.html


Update Carbon icons to latest version of ocs icons

Routine update/rebase with latest icons from https://github.com/cerner/one-cerner-style-icons.

This is a good opportunity to combine this when updating icons for https://github.com/cerner/carbon-graphs/issues/29#issuecomment-513288557

:tada: This issue has been resolved in version 1.7.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


won't work on Jupyter lab

I seem to be having some problems to run it. It won't render the buttons on the options. This might be related to me using Jupyter lab instead of regular notebooks.
I'm running:
Jupiter lab 4.4.0
Python 3.7.3

I just checked and it works on regular Jupyter notebooks. Just not Jupyter lab. Anyone knows why this might be the case?

This stackoverflow solution might help for some, since pigeon is using ipywidgets under the hood: https://stackoverflow.com/a/49613135/7644323


gcc: 7.3 -> 7.4

https://gcc.gnu.org/gcc-7/changes.html
Motivation for this change
Things done

I'm still testing this for various configurations, so far so good :).

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Hmm, internal compiler error when building LLVM 7?
:(

Any updates?  I merged this with a staging commit (ee77dd61e3b0) and llvm+clang 7 built fine for me (x86_64 NixOS).

Any updates? I merged this with a staging commit (ee77dd6) and llvm+clang 7 built fine for me (x86_64 NixOS).

Interesting! I tried this myself, and it worked for me as well (rebased onto recent staging, same idea).
Let's revisit this, will update with rebased version in a few-- first for sake of sanity and curiosity investigating the issue a bit :).

Nevermind, tagging it for my own curiosity-- reopening with updated version.


interesting work

Hi, when could you release the codes?

Now, the codes are available. Thanks for your interest to our work!


Correct documentation for affinity_host example.

Update documentation to have a working example along with make it a bit more descriptive.
issue #185

Really appreciate your help in making the documentation correct!


Admin portal - Projector view showing current game state of specified game

We may want to make this a "view only" client rather than admin.  For all intensive purposes we could manually navigate there, say /projector/game/:roomCode and leave that up in a browser on the projector.  Theoretically we could stage multiple screens this way, not that we want to for this. Basically I like decoupling this view from admin UI since it's read only and I don't want users to watch admin as they click next, etc. and this way there won't be any admin URLs displayed to users (while we're insecure)


Update README.md

add logo to readme

@Apache9 PTAL

I think it is better to put it on the top?

yep, that make sense.

And don't forget the organization logo :)

@spinlock  PTAL


Image low quality -> unreadeable

Hi,
The image is unreadeable in chrome, edge, firefox. Even when opened in new tab.
Valentijn

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

ID: 23b6318a-1d43-e98e-649a-33188c844506
Version Independent ID: 3dc31b3e-d3ce-8937-d068-b1e460df4569
Content: B2B collaboration user claims mapping in Azure Active Directory
Content Source: articles/active-directory/active-directory-b2b-claims-mapping.md
Service: active-directory
GitHub Login: @twooley
Microsoft Alias: twooley

@valentijnscholten Hello. Thanks for reporting this issue and helping to improve the docs. I have updated the article with a new screenshot (and made some other minor updates).

#please-close

@valentijnscholten We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.


Windows: Snake keypresses not working

Not 100% sure, maybe this is related to a race condition of some sort? I get it to happen on Linux but 1% of the time?

Windows is busted. Text effects don't seem to work, ANSI codes may not be supported, and arrow keys are totally busted.
For now, we always use the Virtual Terminal for windows as a workaround, but it would be nice to fix this in the future.

Note: When re-enabling, remember to include the jansi jar in the build.gradle.kts file:
//runtimeOnly(files("libs/jansi-1.18.jar")) // Required for windows support


Save initial condition (for movie)

Fixes #41
For this PR, I will need a real review! :-)

As @ashwinvis mentioned, because we are using chpt_ifrst after call frame_end, we need to include 'CHKPOINTD'. Another possibility would be
if (istep .eq. 0 .and. (chpt_ifrst == 0) ) then
      ! first timestep which is not restarted
         call outpost(vx, vy, vz, pr, t, '   ')  ! write initial condition
      ! finalise framework
else if (istep.eq.nsteps.or.lastep.eq.1) then
         call frame_end
endif


Add HTTPS support

Great, thanks!

Published as 1.2.0

Thank you so much for the quick turn-around.


[Bug]: Error in shopify dev

Please confirm that you have:

[X] Searched existing issues to see if your issue is a duplicate. (If you’ve found a duplicate issue, feel free to add additional information in a comment on it.)
[X] Reproduced the issue in the latest CLI version.

In which of these areas are you experiencing a problem?
Other
Expected behavior
If you enter shopify theme dev --store https://test.myshopify.com/.
│ │ │
Preview the theme
│ - http://<IP_ADDRESS>:9292 │

Next Steps
Customize your theme in the theme editor
Share the theme preview
│ (https://test.myshopify.com/?preview_theme_id=0000)

 Sync theme #〇〇〇〇〇〇 to test.myshopify.com

is now complete.
Actual behavior
Because the following was displayed,
shopify theme dev --store https://test.myshopify.com/

✗ An unexpected error occurred.
        To submit an issue include the stack trace.
        To print the stack trace, add the environment variable SHOPIFY_CLI_STACKTRACE=1.

I just entered this one.
export SHOPIFY_CLI_STACKTRACE=1
shopify theme dev --store https://test.myshopify.com/

I get the following and shopify theme dev is not working properly.
<internal:dir>:411:in `glob': Operation timed out - /Users/test/Desktop/test-content/T/TT/materials/tagDI.rtfd (Errno::ETIMEDOUT)
        from /usr/local/Cellar/shopify-cli/3.60.1/libexec/lib/node_modules/@shopify/cli/dist/assets/cli-ruby/lib/shopify_cli/theme/root.rb:29:in `glob'
        from /usr/local/Cellar/shopify-cli/3.60.1/libexec/lib/node_modules/@shopify/cli/dist/assets/cli-ruby/lib/shopify_cli/theme/root.rb:29:in `glob'
        from /usr/local/Cellar/shopify-cli/3.60.1/libexec/lib/node_modules/@shopify/cli/dist/assets/cli-ruby/lib/shopify_cli/theme/theme.rb:24:in `theme_files'
        from /usr/local/Cellar/shopify-cli/3.60.1/libexec/lib/node_modules/@shopify/cli/dist/assets/cli-ruby/lib/shopify_cli/theme/syncer/uploader.rb:63:in `delete_files!'
        from /usr/local/Cellar/shopify-cli/3.60.1/libexec/lib/node_modules/@shopify/cli/dist/assets/cli-ruby/lib/shopify_cli/theme/syncer/uploader.rb:50:in `upload!'
        from /usr/local/Cellar/shopify-cli/3.60.1/libexec/lib/node_modules/@shopify/cli/dist/assets/cli-ruby/lib/shopify_cli/theme/syncer.rb:171:in `upload_theme!'
        from /usr/local/Cellar/shopify-cli/3.60.1/libexec/lib/node_modules/@shopify/cli/dist/assets/cli-ruby/lib/project_types/theme/ui/sync_progress_bar.rb:11:in `public_send'
        from /usr/local/Cellar/shopify-cli/3.60.1/libexec/lib/node_modules/@shopify/cli/dist/assets/cli-ruby/lib/project_types/theme/ui/sync_progress_bar.rb:11:in `block in progress'
        from /usr/local/Cellar/shopify-cli/3.60.1/libexec/lib/node_modules/@shopify/cli/dist/assets/cli-ruby/vendor/deps/cli-ui/lib/cli/ui/progress.rb:34:in `progress'
        from /usr/local/Cellar/shopify-cli/3.60.1/libexec/lib/node_modules/@shopify/cli/dist/assets/cli-ruby/lib/project_types/theme/ui/sync_progress_bar.rb:10:in `progress'
        from /usr/local/Cellar/shopify-cli/3.60.1/libexec/lib/node_modules/@shopify/cli/dist/assets/cli-ruby/lib/project_types/theme/commands/serve.rb:53:in `block in call'
        from /usr/local/Cellar/shopify-cli/3.60.1/libexec/lib/node_modules/@shopify/cli/dist/assets/cli-ruby/lib/shopify_cli/theme/dev_server.rb:189:in `sync_theme'
        from /usr/local/Cellar/shopify-cli/3.60.1/libexec/lib/node_modules/@shopify/cli/dist/assets/cli-ruby/lib/shopify_cli/theme/dev_server.rb:118:in `start'
        from /usr/local/Cellar/shopify-cli/3.60.1/libexec/lib/node_modules/@shopify/cli/dist/assets/cli-ruby/lib/shopify_cli/theme/dev_server.rb:72:in `start'
        from /usr/local/Cellar/shopify-cli/3.60.1/libexec/lib/node_modules/@shopify/cli/dist/assets/cli-ruby/lib/project_types/theme/commands/serve.rb:52:in `call'
        from /usr/local/Cellar/shopify-cli/3.60.1/libexec/lib/node_modules/@shopify/cli/dist/assets/cli-ruby/lib/shopify_cli/command/sub_command.rb:15:in `call'
        from /usr/local/Cellar/shopify-cli/3.60.1/libexec/lib/node_modules/@shopify/cli/dist/assets/cli-ruby/lib/shopify_cli/command.rb:26:in `call'
        from /usr/local/Cellar/shopify-cli/3.60.1/libexec/lib/node_modules/@shopify/cli/dist/assets/cli-ruby/lib/shopify_cli/core/executor.rb:17:in `block (2 levels) in call'
        from /usr/local/Cellar/shopify-cli/3.60.1/libexec/lib/node_modules/@shopify/cli/dist/assets/cli-ruby/vendor/deps/cli-kit/lib/cli/kit/executor.rb:37:in `block (2 levels) in with_logging'
        from /usr/local/Cellar/shopify-cli/3.60.1/libexec/lib/node_modules/@shopify/cli/dist/assets/cli-ruby/vendor/deps/cli-ui/lib/cli/ui/stdout_router.rb:169:in `with_id'
        from /usr/local/Cellar/shopify-cli/3.60.1/libexec/lib/node_modules/@shopify/cli/dist/assets/cli-ruby/vendor/deps/cli-kit/lib/cli/kit/executor.rb:36:in `block in with_logging'
        from /usr/local/Cellar/shopify-cli/3.60.1/libexec/lib/node_modules/@shopify/cli/dist/assets/cli-ruby/vendor/deps/cli-ui/lib/cli/ui.rb:177:in `log_output_to'
        from /usr/local/Cellar/shopify-cli/3.60.1/libexec/lib/node_modules/@shopify/cli/dist/assets/cli-ruby/vendor/deps/cli-kit/lib/cli/kit/executor.rb:35:in `with_logging'
        from /usr/local/Cellar/shopify-cli/3.60.1/libexec/lib/node_modules/@shopify/cli/dist/assets/cli-ruby/lib/shopify_cli/core/executor.rb:16:in `block in call'
        from /usr/local/Cellar/shopify-cli/3.60.1/libexec/lib/node_modules/@shopify/cli/dist/assets/cli-ruby/vendor/deps/cli-kit/lib/cli/kit/executor.rb:45:in `block (2 levels) in with_traps'
        from /usr/local/Cellar/shopify-cli/3.60.1/libexec/lib/node_modules/@shopify/cli/dist/assets/cli-ruby/vendor/deps/cli-kit/lib/cli/kit/executor.rb:55:in `twrap'
        from /usr/local/Cellar/shopify-cli/3.60.1/libexec/lib/node_modules/@shopify/cli/dist/assets/cli-ruby/vendor/deps/cli-kit/lib/cli/kit/executor.rb:44:in `block in with_traps'
        from /usr/local/Cellar/shopify-cli/3.60.1/libexec/lib/node_modules/@shopify/cli/dist/assets/cli-ruby/vendor/deps/cli-kit/lib/cli/kit/executor.rb:55:in `twrap'
        from /usr/local/Cellar/shopify-cli/3.60.1/libexec/lib/node_modules/@shopify/cli/dist/assets/cli-ruby/vendor/deps/cli-kit/lib/cli/kit/executor.rb:43:in `with_traps'
        from /usr/local/Cellar/shopify-cli/3.60.1/libexec/lib/node_modules/@shopify/cli/dist/assets/cli-ruby/lib/shopify_cli/core/executor.rb:15:in `call'
        from /usr/local/Cellar/shopify-cli/3.60.1/libexec/lib/node_modules/@shopify/cli/dist/assets/cli-ruby/lib/shopify_cli/core/entry_point.rb:17:in `block in call'
        from /usr/local/Cellar/shopify-cli/3.60.1/libexec/lib/node_modules/@shopify/cli/dist/assets/cli-ruby/lib/shopify_cli/core/monorail.rb:26:in `log'
        from /usr/local/Cellar/shopify-cli/3.60.1/libexec/lib/node_modules/@shopify/cli/dist/assets/cli-ruby/lib/shopify_cli/core/entry_point.rb:16:in `call'
        from /usr/local/Cellar/shopify-cli/3.60.1/libexec/lib/node_modules/@shopify/cli/dist/assets/cli-ruby/bin/shopify:57:in `block (2 levels) in <main>'
        from /usr/local/Cellar/shopify-cli/3.60.1/libexec/lib/node_modules/@shopify/cli/dist/assets/cli-ruby/vendor/deps/cli-kit/lib/cli/kit/error_handler.rb:75:in `handle_abort'
        from /usr/local/Cellar/shopify-cli/3.60.1/libexec/lib/node_modules/@shopify/cli/dist/assets/cli-ruby/vendor/deps/cli-kit/lib/cli/kit/error_handler.rb:21:in `call'
        from /usr/local/Cellar/shopify-cli/3.60.1/libexec/lib/node_modules/@shopify/cli/dist/assets/cli-ruby/bin/shopify:56:in `block in <main>'
        from /usr/local/Cellar/shopify-cli/3.60.1/libexec/lib/node_modules/@shopify/cli/dist/assets/cli-ruby/bin/shopify:66:in `<main>'

Verbose output
test@MacBook-Pro ~ % shopify theme dev --store https://test.myshopify.com --verbose

2024-05-30T16:19:10.991Z: Running command theme dev
2024-05-30T16:19:11.037Z: Ensuring that the user is authenticated with the Theme API with the following scopes:
[]

2024-05-30T16:19:11.037Z: Ensuring that the user is authenticated with the Admin API with the following scopes for the store test.myshopify.com:
[]

2024-05-30T16:19:11.039Z: Getting session store...
2024-05-30T16:19:11.043Z: Validating existing session against the scopes:
[
  "openid",
  "https://api.shopify.com/auth/shop.admin.graphql",
  "https://api.shopify.com/auth/shop.admin.themes",
  "https://api.shopify.com/auth/partners.collaborator-relationships.readonly",
  "https://api.shopify.com/auth/shop.storefront-renderer.devtools",
  "https://api.shopify.com/auth/partners.app.cli.access",
  "https://api.shopify.com/auth/destinations.readonly"
]
For applications:
{
  "adminApi": {
    "scopes": [],
    "storeFqdn": "test.myshopify.com"
  }
}

2024-05-30T16:19:11.044Z: Sending Identity Introspection request to URL: https://accounts.shopify.com/oauth/introspection
2024-05-30T16:19:11.044Z: Sending POST request to URL https://accounts.shopify.com/oauth/introspection
With request headers:
 - User-Agent: Shopify CLI; v=3.60.1
 - Keep-Alive: timeout=30
 - Sec-CH-UA-PLATFORM: darwin
 - Content-Type: application/json

2024-05-30T16:19:11.389Z: Request to https://accounts.shopify.com/oauth/introspection completed in 316 ms
With response headers:
 - cache-control: no-cache, no-store, private, must-revalidate, max-age=0
 - content-type: application/json; charset=utf-8
 - etag: W/"88a2a7ce1a61252d2563a3314c0d10a1"
 - x-request-id: d015a0cc-de68-4a7e-a2f6-8677e656aa19-1717085951

2024-05-30T16:19:11.395Z: The identity token is valid: true
2024-05-30T16:19:11.395Z:
The validation of the token for application/identity completed with the following results:
- It's expired: false
- It's invalid in identity: false

2024-05-30T16:19:11.396Z: The current session is valid but needs refresh. Refreshing...
2024-05-30T16:19:11.397Z: Sending POST request to URL https://accounts.shopify.com/oauth/token?grant_type=refresh_token&access_token=atkn_CjQIjr3isgYQrvXisgZSJggBEhDGUGZlYehCeLdQ6W5KUQ3QGhC-pz-E_KhKI7ICJVgRIytIEkCj7m8_dCuAiKi4Put-eQAGoyqFRF9ZkgCWXHBsRi0qzC-GWEhx67-MaSuk_JJsEqR9gPgAeb8xZpX0sRtf0MsM&refresh_token=atkn_CiEIjr3isgYQjteAtAaiARIKEL6nP4T8qEojsgIlWBEjK0gSQJ9xWt2rMWvxwCgCsRdEjvPFdhh5JT3rE4B_yqivO1BXs3cwPrYrAvG-CSKp0FQinIqRJsSAK2X8hoRvDTNQrQk&client_id=fbdb2649-e327-4907-8f67-908d24cfd7e3
With request headers:
 - User-Agent: Shopify CLI; v=3.60.1
 - Keep-Alive: timeout=30
 - Sec-CH-UA-PLATFORM: darwin
 - Content-Type: application/json

2024-05-30T16:19:12.035Z: Request to https://accounts.shopify.com/oauth/token?grant_type=refresh_token&access_token=atkn_CjQIjr3isgYQrvXisgZSJggBEhDGUGZlYehCeLdQ6W5KUQ3QGhC-pz-E_KhKI7ICJVgRIytIEkCj7m8_dCuAiKi4Put-eQAGoyqFRF9ZkgCWXHBsRi0qzC-GWEhx67-MaSuk_JJsEqR9gPgAeb8xZpX0sRtf0MsM&refresh_token=atkn_CiEIjr3isgYQjteAtAaiARIKEL6nP4T8qEojsgIlWBEjK0gSQJ9xWt2rMWvxwCgCsRdEjvPFdhh5JT3rE4B_yqivO1BXs3cwPrYrAvG-CSKp0FQinIqRJsSAK2X8hoRvDTNQrQk&client_id=fbdb2649-e327-4907-8f67-908d24cfd7e3 completed in 637 ms
With response headers:
 - cache-control: no-cache, no-store, private, must-revalidate, max-age=0
 - content-type: application/json; charset=utf-8
 - etag: W/"320a7d18d379353156c7533b3111a50b"
 - x-request-id: ace8f3ee-61f9-4496-99d2-473be5e71df4-1717085951

2024-05-30T16:19:12.040Z: Sending POST request to URL https://accounts.shopify.com/oauth/token?grant_type=urn%3Aietf%3Aparams%3Aoauth%3Agrant-type%3Atoken-exchange&requested_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&subject_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&client_id=fbdb2649-e327-4907-8f67-908d24cfd7e3&audience=271e16d403dfa18082ffb3d197bd2b5f4479c3fc32736d69296829cbb28d41a6&scope=https%3A%2F%2Fapi.shopify.com%2Fauth%2Fpartners.app.cli.access&subject_token=****
With request headers:
 - User-Agent: Shopify CLI; v=3.60.1
 - Keep-Alive: timeout=30
 - Sec-CH-UA-PLATFORM: darwin
 - Content-Type: application/json

2024-05-30T16:19:12.040Z: Sending POST request to URL https://accounts.shopify.com/oauth/token?grant_type=urn%3Aietf%3Aparams%3Aoauth%3Agrant-type%3Atoken-exchange&requested_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&subject_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&client_id=fbdb2649-e327-4907-8f67-908d24cfd7e3&audience=ee139b3d-5861-4d45-b387-1bc3ada7811c&scope=https%3A%2F%2Fapi.shopify.com%2Fauth%2Fshop.storefront-renderer.devtools&subject_token=****
With request headers:
 - User-Agent: Shopify CLI; v=3.60.1
 - Keep-Alive: timeout=30
 - Sec-CH-UA-PLATFORM: darwin
 - Content-Type: application/json

2024-05-30T16:19:12.041Z: Sending POST request to URL https://accounts.shopify.com/oauth/token?grant_type=urn%3Aietf%3Aparams%3Aoauth%3Agrant-type%3Atoken-exchange&requested_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&subject_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&client_id=fbdb2649-e327-4907-8f67-908d24cfd7e3&audience=32ff8ee5-82b8-4d93-9f8a-c6997cefb7dc&scope=https%3A%2F%2Fapi.shopify.com%2Fauth%2Fdestinations.readonly&subject_token=****
With request headers:
 - User-Agent: Shopify CLI; v=3.60.1
 - Keep-Alive: timeout=30
 - Sec-CH-UA-PLATFORM: darwin
 - Content-Type: application/json

2024-05-30T16:19:12.041Z: Sending POST request to URL https://accounts.shopify.com/oauth/token?grant_type=urn%3Aietf%3Aparams%3Aoauth%3Agrant-type%3Atoken-exchange&requested_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&subject_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&client_id=fbdb2649-e327-4907-8f67-908d24cfd7e3&audience=7ee65a63608843c577db8b23c4d7316ea0a01bd2f7594f8a9c06ea668c1b775c&scope=https%3A%2F%2Fapi.shopify.com%2Fauth%2Fshop.admin.graphql+https%3A%2F%2Fapi.shopify.com%2Fauth%2Fshop.admin.themes+https%3A%2F%2Fapi.shopify.com%2Fauth%2Fpartners.collaborator-relationships.readonly&subject_token=****&destination=https%3A%2F%2Ftest.myshopify.com%2Fadmin
With request headers:
 - User-Agent: Shopify CLI; v=3.60.1
 - Keep-Alive: timeout=30
 - Sec-CH-UA-PLATFORM: darwin
 - Content-Type: application/json

2024-05-30T16:19:12.361Z: Request to https://accounts.shopify.com/oauth/token?grant_type=urn%3Aietf%3Aparams%3Aoauth%3Agrant-type%3Atoken-exchange&requested_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&subject_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&client_id=fbdb2649-e327-4907-8f67-908d24cfd7e3&audience=271e16d403dfa18082ffb3d197bd2b5f4479c3fc32736d69296829cbb28d41a6&scope=https%3A%2F%2Fapi.shopify.com%2Fauth%2Fpartners.app.cli.access&subject_token=**** completed in 314 ms
With response headers:
 - cache-control: no-cache, no-store, private, must-revalidate, max-age=0
 - content-type: application/json; charset=utf-8
 - etag: W/"09f704e5f95eff00421da480dd712e29"
 - x-request-id: 59e271c1-0eeb-4d73-ad14-1d99a4f96cb0-1717085952

2024-05-30T16:19:12.376Z: Request to https://accounts.shopify.com/oauth/token?grant_type=urn%3Aietf%3Aparams%3Aoauth%3Agrant-type%3Atoken-exchange&requested_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&subject_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&client_id=fbdb2649-e327-4907-8f67-908d24cfd7e3&audience=ee139b3d-5861-4d45-b387-1bc3ada7811c&scope=https%3A%2F%2Fapi.shopify.com%2Fauth%2Fshop.storefront-renderer.devtools&subject_token=**** completed in 327 ms
With response headers:
 - cache-control: no-cache, no-store, private, must-revalidate, max-age=0
 - content-type: application/json; charset=utf-8
 - etag: W/"4cda8b7ca709f1d0e6ef16b5c2ed8b23"
 - x-request-id: 70721d40-0d30-468b-9f36-589136e9f107-1717085952

2024-05-30T16:19:12.380Z: Request to https://accounts.shopify.com/oauth/token?grant_type=urn%3Aietf%3Aparams%3Aoauth%3Agrant-type%3Atoken-exchange&requested_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&subject_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&client_id=fbdb2649-e327-4907-8f67-908d24cfd7e3&audience=7ee65a63608843c577db8b23c4d7316ea0a01bd2f7594f8a9c06ea668c1b775c&scope=https%3A%2F%2Fapi.shopify.com%2Fauth%2Fshop.admin.graphql+https%3A%2F%2Fapi.shopify.com%2Fauth%2Fshop.admin.themes+https%3A%2F%2Fapi.shopify.com%2Fauth%2Fpartners.collaborator-relationships.readonly&subject_token=****&destination=https%3A%2F%2Ftest.myshopify.com%2Fadmin completed in 325 ms
With response headers:
 - cache-control: no-cache, no-store, private, must-revalidate, max-age=0
 - content-type: application/json; charset=utf-8
 - etag: W/"0b2e746f3c5fbf609cbf10e8b808cd09"
 - x-request-id: 2956d258-d84f-4482-847a-5614879bf26d-1717085952

2024-05-30T16:19:12.388Z: Request to https://accounts.shopify.com/oauth/token?grant_type=urn%3Aietf%3Aparams%3Aoauth%3Agrant-type%3Atoken-exchange&requested_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&subject_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&client_id=fbdb2649-e327-4907-8f67-908d24cfd7e3&audience=32ff8ee5-82b8-4d93-9f8a-c6997cefb7dc&scope=https%3A%2F%2Fapi.shopify.com%2Fauth%2Fdestinations.readonly&subject_token=**** completed in 335 ms
With response headers:
 - cache-control: no-cache, no-store, private, must-revalidate, max-age=0
 - content-type: application/json; charset=utf-8
 - etag: W/"846e3d2c5d66d36db12dc60637b39620"
 - x-request-id: b9f0b80a-2c9f-4b70-b3a8-217236b9d3cf-1717085952

2024-05-30T16:19:12.394Z: Setting session store...
2024-05-30T16:19:12.409Z: Ensuring that the user is authenticated with the Storefront API with the following scopes:
[]

2024-05-30T16:19:12.410Z: Getting session store...
2024-05-30T16:19:12.411Z: Validating existing session against the scopes:
[
  "openid",
  "https://api.shopify.com/auth/shop.admin.graphql",
  "https://api.shopify.com/auth/shop.admin.themes",
  "https://api.shopify.com/auth/partners.collaborator-relationships.readonly",
  "https://api.shopify.com/auth/shop.storefront-renderer.devtools",
  "https://api.shopify.com/auth/partners.app.cli.access",
  "https://api.shopify.com/auth/destinations.readonly"
]
For applications:
{
  "storefrontRendererApi": {
    "scopes": []
  }
}

2024-05-30T16:19:12.411Z: Sending Identity Introspection request to URL: https://accounts.shopify.com/oauth/introspection
2024-05-30T16:19:12.411Z: Sending POST request to URL https://accounts.shopify.com/oauth/introspection
With request headers:
 - User-Agent: Shopify CLI; v=3.60.1
 - Keep-Alive: timeout=30
 - Sec-CH-UA-PLATFORM: darwin
 - Content-Type: application/json

2024-05-30T16:19:12.691Z: Request to https://accounts.shopify.com/oauth/introspection completed in 277 ms
With response headers:
 - cache-control: no-cache, no-store, private, must-revalidate, max-age=0
 - content-type: application/json; charset=utf-8
 - etag: W/"fbdb26999f4579b665efd79afea39167"
 - x-request-id: 6c4baff3-11b4-4cab-9e3c-481e9c59b24e-1717085952

2024-05-30T16:19:12.692Z: The identity token is valid: true
2024-05-30T16:19:12.693Z:
The validation of the token for application/identity completed with the following results:
- It's expired: false
- It's invalid in identity: false

2024-05-30T16:19:12.710Z:
Running system process:
  · Command: /usr/local/opt/ruby/bin/ruby -v
  · Working directory: /Users/test

2024-05-30T16:19:12.760Z:
Running system process:
  · Command: /usr/local/opt/ruby/bin/bundle -v
  · Working directory: /Users/test

2024-05-30T16:19:13.140Z: Reading the content of file at<EMAIL_ADDRESS>2024-05-30T16:19:13.142Z:
Running system process:
  · Command: /usr/local/opt/ruby/bin/bundle install
  · Working directory: /usr/local/Cellar/shopify-cli/3.60.1/libexec/lib/node_modules/@shopify/cli/dist/assets/cli-ruby

2024-05-30T16:19:14.088Z:
Running system process:
  · Command: /usr/local/opt/ruby/bin/bundle exec /usr/local/opt/ruby/bin/ruby /usr/local/Cellar/shopify-cli/3.60.1/libexec/lib/node_modules/@shopify/cli/dist/assets/cli-ruby/bin/shopify theme token --admin atkn_Cp8DCIDO4rIGEKCG47IGYpADCAESEJ35AYeFs0NprzOhr_RJ8K8aqAFodHRwczovL2FwaS5zaG9waWZ5LmNvbS9hdXRoL3BhcnRuZXJzLmNvbGxhYm9yYXRvci1yZWxhdGlvbnNoaXBzLnJlYWRvbmx5IGh0dHBzOi8vYXBpLnNob3BpZnkuY29tL2F1dGgvc2hvcC5hZG1pbi5ncmFwaHFsIGh0dHBzOi8vYXBpLnNob3BpZnkuY29tL2F1dGgvc2hvcC5hZG1pbi50aGVtZXMgDSinUzIQ1RUExM8uQNaQ9DJ88sHSfDokM2QxNWRmODktZjVkNy00M2IwLWEzMTktYTkzZWM2MjNhMTJiQgdBY2NvdW50ShB87lKVZ-xIsZTyBoMATLZDUlN7InN1YiI6ImZiZGIyNjQ5LWUzMjctNDkwNy04ZjY3LTkwOGQyNGNmZDdlMyIsImlzcyI6Imh0dHBzOi8vYWNjb3VudHMuc2hvcGlmeS5jb20ifWIQV4EplqcwSwu4WYE0jmAEC2oQSBTaWp2CRnmOLsjv9NXkvRJActWq7bknjRcE0uRKij-dBczxJ0e2apevg5WnUdSKqiyBKx7-hChomgVGnfUQww4C-eGCynj98Rtt7xV-LKSxAQ --sfr atkn_CqMCCIDO4rIGEKCG47IGYpQCCAESELYv5B99JUzwgz8yrdh-S0kaPmh0dHBzOi8vYXBpLnNob3BpZnkuY29tL2F1dGgvc2hvcC5zdG9yZWZyb250LXJlbmRlcmVyLmRldnRvb2xzINhSKKdTOiQzZDE1ZGY4OS1mNWQ3LTQzYjAtYTMxOS1hOTNlYzYyM2ExMmJCB0FjY291bnRKEHzuUpVn7EixlPIGgwBMtkNSU3sic3ViIjoiZmJkYjI2NDktZTMyNy00OTA3LThmNjctOTA4ZDI0Y2ZkN2UzIiwiaXNzIjoiaHR0cHM6Ly9hY2NvdW50cy5zaG9waWZ5LmNvbSJ9YhBXgSmWpzBLC7hZgTSOYAQLahBIFNpanYJGeY4uyO_01eS9EkC5If-aYbEe0rEwj2ZhwJS4zCQSDJeYPU7zU4g6p18H3FZ3NH2wepWa43ySMhApFOl-y4-vi1Cgyb8Ou2FkY6AD
  · Working directory: /Users/test

2024-05-30T16:19:15.548Z: Getting development theme...
2024-05-30T16:19:15.967Z: Request to https://test.myshopify.com/admin/api/unstable/themes/142028308706.json?fields=id%2Cname%2Crole%2Cprocessing completed in 414 ms
With response headers:
 - content-type: application/json; charset=utf-8
 - x-request-id: 35fc3ba8-1c81-45a2-b4cf-142d56bb942e-1717085955

╭─ success ──────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│                                                                                │
│  Preview your theme                                                                                │
│    • http://<IP_ADDRESS>:9292                                                                                │
│                                                                                │
│  Next steps                                                                                │
│    • Customize your theme at the theme editor                                                                      │
│    • Share your theme preview (https://test.myshopify.com/?preview_theme_id=142028308706)                     │
│                                                                                │
╰────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯

2024-05-30T16:19:16.056Z:
Running system process:
  · Command: /usr/local/opt/ruby/bin/ruby -v
  · Working directory: /Users/test

2024-05-30T16:19:16.077Z:
Running system process:
  · Command: /usr/local/opt/ruby/bin/bundle -v
  · Working directory: /Users/test

2024-05-30T16:19:16.508Z: Reading the content of file at<EMAIL_ADDRESS>2024-05-30T16:19:16.512Z:
Running system process:
  · Command: /usr/local/opt/ruby/bin/bundle install
  · Working directory: /usr/local/Cellar/shopify-cli/3.60.1/libexec/lib/node_modules/@shopify/cli/dist/assets/cli-ruby

2024-05-30T16:19:17.464Z:
Running system process:
  · Command: /usr/local/opt/ruby/bin/bundle exec /usr/local/opt/ruby/bin/ruby /usr/local/Cellar/shopify-cli/3.60.1/libexec/lib/node_modules/@shopify/cli/dist/assets/cli-ruby/bin/shopify theme serve /Users/test --live-reload hot-reload --theme<PHONE_NUMBER>06 --overwrite-json undefined
  · Working directory: /Users/test

DEBUG GET https://test.myshopify.com/admin/api/unstable/themes.json with request_id: bba3e18d-76e2-4991-9095-fc67c9c29cd0-1717085959
* Syncing theme #142028308706 on test.myshopify.com
DEBUG GET https://test.myshopify.com/admin/api/unstable/themes/142028308706/assets.json with request_id: 0610feab-7d6e-4844-8ad3-f90ad737e44e-1717085959
                                                                                0%
✗ An unexpected error occurred.
        To submit an issue include the stack trace.
        To print the stack trace, add the environment variable SHOPIFY_CLI_STACKTRACE=1.

Reproduction steps
1.shopify theme dev --store https://test.myshopify.com/
2.SHOPIFY_CLI_STACKTRACE=1
3.shopify theme dev --store https://test.myshopify.com/
Operating System
Mac OS
Shopify CLI version (check your project's package.json if you're not sure)
3.60.1
Shell
No response
Node version (run node -v if you're not sure)
v22.2.0
What language and version are you using in your application?
No response

Any updates here? I'm having the exact same issue as above


Priority Error

Hi there,
I am getting the following error:

{ [PriorityInvalidError: priority is invalid] name: 'PriorityInvalidError', message: 'priority is invalid' }

I think is because some of my .md files have set the priority field and the value goes up to 10000 and so on.
How can I prevent mapsite to use those values as a sitemap's priority?
I defined the priority

	.use(sitemap({
			'hostname':'http://www.example.com',
			'priority': '0.5'
		}))

But I am still getting the same error.
Thanks

Hi,
Yeah, the error makes sense, since valid values for priority are from 0.0 to 1.0. Also, the values in the front-matter always override the options passed to the plugin, which is why the value from your .md files is used.
You could exclude the .md files with the pattern option, or remove the values from the frontmatter before mapsite processes them. What I would recommend however, is to just only use the priority field for values that are meant for mapsite, and move the values that you're now putting in priority elsewhere. That would be the simplest solution imo.

Hope that helps. Feel free to let me know if you have any other questions!

Ismay,
Thank you for the quick reply.
I cannot change the tag priority in my .md files that will take a way too long.
I tried to use pattern to prevent mapping the .md files, I did:
'pattern': '**/*.html'
And still I am getting the same error. Also I was wondering even If I make it work and I don't map the .md files then I won't get them in the sitemap right? So that's a problem.
Any thought?
Thanks

I tried to use pattern to prevent mapping the .md files, I did: 'pattern': '**/*.html'

That should work (it's also the default, so you shouldn't even have to pass it). You're probably converting the markdown before running mapsite (which means all .md will be converted to .html, and thus will match the pattern).

Also I was wondering even If I make it work and I don't map the .md files then I won't get them in the sitemap right? So that's a problem.

That's right, they'll be ignored.
Unfortunately I can't change it matching on the priority field. Which is the main cause of your problem here. If you don't want to change your use of the priority field, your only option is to remove the field before mapsite gets to it.
// define local plugin
function removePriority(){
  return function(files){
    for (var file in files) {
      if (files[file].priority) delete files[file].priority;
    }
  };
}

// remove priority after you're done with it
Metalsmith(__dirname)
  // other plugins
  .use(removePriority())
  .use(mapsite())
  // other plugins
  .build(function(err) {
    if (err) throw err;
    console.log('Build finished!');
  });


Add some sort of web analytics

Plausible is a "lightweight and open-source website analytics tool. No cookies and fully compliant with GDPR, CCPA and PECR. Made and hosted in the EU", perhaps we can use that to get some insights in how the website gets uesd?
Example on a real cloud hosted version.

Is there something like this on WM Cloud maybe?

Alternatively, check if we can piggyback on a chapter's Matomo instance.

Alternatively, check if we can piggyback on a chapter's Matomo instance.

Yes, that would be easier for maintenance. Is there anyone willing providing hosting and login details to their instance?
One bonus of Plausible is that you can have it publicly viewable, I have no clue if that is possible in Matomo, but it is also not a dealbreaker.

Apparently Wikimedia has Matomo. But I guess this is hinging on #33.

WMDE and WMSE also got Matomo instances.

Application to WMSE has been submitted: https://se.wikimedia.org/wiki/Stöd_till_gemenskapen/Projektstöd/Tillgång_till_analysverktyg_för_Wikidatadrivet_projekt

Implemented in c1880394643c1b5376f3d6ebe8c7736d870e542d. Note that it lacks subresource integrity checks because upstream lacks CORS.


Seeing lots of new noise in git push to builder

[kent@mbp example-go]$ git push deis master
Warning: Permanently added '[deis.krancour.deis.ninja]:2222,[<IP_ADDRESS>]:2222' (RSA) to the list of known hosts.
Counting objects: 75, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (48/48), done.
Writing objects: 100% (75/75), 18.28 KiB | 0 bytes/s, done.
Total 75 (delta 30), reused 58 (delta 22)
Running in debug mode
Running git hook
read [0000000000000000000000000000000000000000,5450cbcdaaf9afe6fadd219c94ac9c449bd62413,refs/heads/master]
Workflow request /v2/hooks/push (body elided)
Workflow request POST /v2/hooks/config
{"receive_user":"kent","receive_repo":"deluxe-hardtack"}
got the following config back for app deluxe-hardtack: {Owner:kent App:deluxe-hardtack Values:map[] Memory:map[] CPU:map[] Tags:map[] UUID:0163d2b9-b0c6-4001-a020-eabae0fbb589 Created:2016-02-04 20:55:18 +0000 UTC Updated:2016-02-04 20:55:18 +0000 UTC}
running [git archive --format=tar.gz --output=deluxe-hardtack.tar.gz 5450cbcd] in directory /home/git/deluxe-hardtack.git
running [tar -xzf deluxe-hardtack.tar.gz -C /home/git/deluxe-hardtack.git/build/tmp366031923/] in directory /home/git/deluxe-hardtack.git
create bucket error: BucketAlreadyExists: The requested bucket name is not available.
remote: status code: 409, request id: JRAKQXCZXYUSZHC0
Uploading tar to http://<IP_ADDRESS>:9000/git/home/deluxe-hardtack:git-5450cbcd/tar
-----> Starting build... but first, coffee!
Starting pod slugbuild-deluxe-hardtack-5450cbcd-31a2b4b8
Pod spec: {
  "metadata": {
    "name": "slugbuild-deluxe-hardtack-5450cbcd-31a2b4b8",
    "namespace": "deis",
    "creationTimestamp": null,
    "labels": {
      "heritage": "deis",
      "version": "2.0.0-beta"
    }
  },
  "spec": {
    "volumes": [
      {
        "name": "minio-user",
        "secret": {
          "secretName": "minio-user"
        }
      }
    ],
    "containers": [
      {
        "name": "deis-slugbuilder",
        "image": "quay.io/deisci/slugbuilder:v2-beta",
        "env": [
          {
            "name": "DEBUG",
            "value": "1"
          },
          {
            "name": "TAR_URL",
            "value": "http://<IP_ADDRESS>:9000/git/home/deluxe-hardtack:git-5450cbcd/tar"
          },
          {
            "name": "put_url",
            "value": "http://<IP_ADDRESS>:9000/git/home/deluxe-hardtack:git-5450cbcd/push"
          }
        ],
        "resources": {},
        "volumeMounts": [
          {
            "name": "minio-user",
            "readOnly": true,
            "mountPath": "/var/run/secrets/object/store"
          }
        ],
        "imagePullPolicy": "Always"
      }
    ],
    "restartPolicy": "Never",
    "serviceAccountName": ""
  },
  "status": {}
}

@krancour this noise is intentional and the result of running builder with DEBUG=true in the environment. I've added it in the deis-dev chart, but not the official.

Ah.  Well that explains that!  Carry on!


Linking a page in a CTA

Hey all,
I'm trying to link a type "page" in a Call To Action.
I can select the page I want to link, but when I try to go to the page that shows the CTA I get an error:
No linkable model could be found for 'App\Models\Page' in morph map. of record 2
Any idea what is going on here?
Thanks.

Did you add the Page model to the morph map?  See https://laravel-news.com/enforcing-morph-maps-in-laravel
The package requires the use of a morph map.

@Sindoweb Try to add a breakpoint in CallToActionData on line 46 where the LinkableModelNotFoundException is created and check what the $callToActionBlockData array contains. It means that Relation::getMorphedModel($linkableType); returns something strange.

@Sindoweb Could it be that this is old data from before you added the morph map? If the morph map is set, the cta_model variable should be page.
Can you delete the CTA and re-create it?

@Sindoweb It's a bit hard to debug like this. Can you make an example repo or can I access the code?

@Sindoweb Great to hear you fixed it.


async is a reserved keyword in python

There was an async parameter in train_imagenet.py, but it was deprecated now

Preserving or removing the async papameter does not affect running of the code.


Modules executed exactly once.

A minimal example is available here. Steps to reproduce:
git clone https://gist.github.com/3b167a609877c32d1213.git example
cd example
npm i
npm start

This is fine most of the time, but I've been writing tape tests for a client-side application, browserifying them, and finding that some modules are impossible to clean up due to side-effects that are executed on require. These modules aren't written well, but I don't really have a lot of choice in that matter.
I think this is a bug, because it dramatically differs from how node handles requires.
For our use case, each module should be executed each time it is required, as happens in node.

Oops! browserify and node match! Closing the issue.