First day of the week not consistent, displaying wrong dates

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
In calendar view, I have the first day set to 0 (Sunday). The days of the week still show up with Monday first, but the dates in the calendar grid show up as if Sunday was the first day. For December 2024 for example, it shows December 2 as Tuesday, when it is actually Monday. Additionally, when I go back into the options, the "first day of the week" option keeps getting set back to 1 after I set it to 0.
Expected behaviour
Matching dates and days!
Steps To Reproduce
Incorrect calendar shows up on a Chromium browser running on a Raspberry Pi. Shows incorrect sometimes on a Chrome browser on Windows. HA running on a Raspberry Pi.
Mode
Calendar
Card Version
10.0.0
Home Assistant Version
2024.11.1
Configuration
No response
Relevant log output
No response
Code of Conduct

[x] I agree to follow this project's Code of Conduct

I am experiencing the same issue. Looks like the firstDayOfWeek is being ignored. If I change it, the lovelace card's preview updates correctly, but the calendar within the dashboard does not update.
Before YAML/GUI update:

After YAML/GUI Update:


Write detailed documentation for backup process

Please provide information on how to backup user data of Zulip server.

Great question!  There are several pieces of data that you might want to
back up:

The postgres database.  That you can back up like any postgres database;
we have some tooling for doing that incrementally into S3 using env-wal-e
that's installed in puppet/zulip_internal/manifests/postgres_common.pp
(that's what we use for zulip.com's backups).
Any user-uploaded files.  If you're using S3 as storage for file uploads,
this is backed up in S3, but if you have instead set LOCAL_UPLOADS_DIR, any
files uploaded by users (including avatars) will be stored in that
directory and you'll want to back it up.
Your Zulip configuration including secrets from /etc/zulip/.  E.g. if you
lose the value of secret_key, all users will need to login again when you
setup a replacement server since you won't be able to verify their cookies;
if you lose avatar_salt, any user-uploaded avatars will need to be
re-uploaded (since their filenames are hashed using avatar_salt), etc.
The logs under /var/log/zulip can be handy to have backed up, but they do
get large and it's definitely lower-priority in that nothing bad happens to
users if all the logs are lost.

If anyone's up for working on it, I'd love to merge a pull request that
writes this out with a bit more detail around how to do these things (in
particular the postgres piece) in the documentation.

is this already available on the latest release of zulip?

Well the instructions above should work but they haven't been merged in anywhere.  I'd appreciate commentary on whether the above is clear; and if so I'll put it into README.prod.md
Ideally we'd make the env-wal-e piece of the configuration super easy since that's going to be the same work for basically every user...

how can I add zulip_internal/ to my current version?

@gfernandez83 the server release tarballs don't include zulip_internal/ since that's stuff which was originally just for running the Zulip site and hasn't been ported properly to be easy to install.
You can get it right now by cloning the git repo and just using that directory; sorry this is a little messy.
I guess probably making the backup situation easy should include porting the env-wal-e stuff out of zulip_internal into zulip/; I've opened a ticket on that (https://github.com/zulip/zulip/issues/293)

thanks a lot @timabbott

Fixed in a recent PR; the link is here: https://github.com/zulip/zulip/blob/master/README.prod.md#backups-for-zulip

Yeah, the docs have just moved to ReadTheDocs a few years ago; link is now https://zulip.readthedocs.io/en/latest/production/maintain-secure-upgrade.html#backups


Docsite: add Community and Contributing guides

Dear maintainers,
As a part of the Consolidating Ansible discussion platforms initiative, this PR adds the communication section template defined by the community to the README and the docsite. Similar PRs are now being raised across all the Ansible ecosystem projects.
Thank you

cc @oraNod

ready for review

@oraNod all the suggestions are committed, thanks, PTAL

@Andersson007 Thanks. I added one other nit. It also looks like there's still one suggestion to commit or resolve.

@Andersson007 Thanks. I added one other nit. It also looks like there's still one suggestion to commit or resolve.

@oraNod oh, missed it somehow, done, PTAL

Sorry @Andersson007 there was one more nit but it LGTM otherwise. Thanks.

@oraNod , committed, thanks! PTAL


World#summonParticle is inaccurate

That method is used by entities to make the client play some kind of effect. This can include spawning particle (see villagers), however it is mostly used to play sound. I would suggest something like playEffectAtEntity. This could go with naming method_5711 (the processing method) playEntityEffect, for example.

Those methods have been renamed in #590.


sudenly GRBL panel stop working, do not know why :(

I do not know what happened, may be some update of windows 7, may be I accidentally delete something, but today I run panel and it stops at this window :(

I am guessing by what I can spot on the display that this is on start up?
If you click on details I might get a location of the error. Did you by change update Grbl on the Arduino? What version of Grbl and GrblPanel are you using?


[QUESTION] Releases

Question
Hi again :)
Hope ya'll doing well..
First lemme say thanks for the efforts by recent contributors (and Lubeda of course),  EspHoMatrix has been evolved greatly!
Perhaps I misunderstood something along the way,
but the latest release is 2023.7.1.
Since then,  there are 2023.8.0 and 2023.9.0/1 branches.
Are these branches expected to be merge into main and have their own releases?
Or are we (as users) should install EHMTX per branch-basis?
Hope to have some clarifications,  to know how it's best to proceed.
Thanks again:)

Hello,
thanks.
I really don't know what's the best way to deal with this problem.  Between main and 2023.9.1 are many breaking changes, It's hard for me to make a proper documentation and some users don't even read the available documentation...
I like the features/possibilities of 2023.9.1, but I don't like the internal code structure, My plan is to clean up the internal structure and some function calls and release the result as an EspHoMaTriXv3. So everybody who is happy with the features of EspHoMaTriX or EspHoMaTriXv2 or... can stick with that version without dealing with the breaking change and without reading the messy documentation....
But I am open for suggestions, but the code clean up is mandatory before a new release.
For now, you can select the branch you like with:
external_components:
  - source:
      type: git
      url: https://github.com/lubeda/EspHoMaTriXv2
      ref: 2023.8.0

The 2023.9.1 is a work in progress, there are some details not fixed, but the 2023.9.0 will stay as it is.

Thanks for the reply Lubeda.
I fully understand the difficulties. I'm personally good on 2023.7.1, since I didn't have time to deal with the breaking changes yet (I've been watching and very exited about the new features though!).
Just wanted to know what's planned ahead.
I'd be glad to share from share my experience as a dev, if I may..
TLDR: You should treat your project like any other package - it should be maintained by versions (even with breaking changes).  As long as you don't rewrite your package from (almost) scratch or you don't massively change the API,  I don't see a reason to open a new project.
In details:
As said,  your project is actually a package.
The custom_components in ESPHome,  is like a sort-of package-manager (in each yaml independently).
Same way you (as a consumer) "lock" the packages' versions when you install them (in general,  not necessarily here) - the same you need to expect from your users.  For example,  If I install pillow in my project,  and write the code for its current API,  I should lock its current working version - so the next install won't install the latest version which may habe breaking changes.   So, same:
When users install you package,  once they finished configuring it,  they should "lock" the current version that works for them (using the ref tag which can also point to a Release version).
Each release (for example 2023.7.1) should have its correlated branch - don't delete the "old" branches.
So,  if I'm locked on version 2023.7.1 in this example,  I can switch to this branch and take a look at its relevant documentation.
The main (or latest) branch, which is the project's Default-Branch,  should be always synced to the latest (Stable) release,  so when a new user installs the package,  it will be exactly as the latest release - so they can lock it.
I expect users, especially ESPHome users (which are likely a bit more savvy than the average user), to follow to "version locking" method.  When a new version is available,  they should read the Breaking-Changes before upgrading. Otherwise they can keep their version freely.  This is relevant for all custom_components in this case,  not specifically for EHMTX.
In your case,   What I personally would do, is
Whenever the "next" release is ready (after clean-ups as you said,  etc.),  I would just release a new release.  I wouldn't open a new Project (I.e. "V3").  I would emphasize the breaking-changes (obviously), and maybe in your case I would even add the "version locking" suggestion in the readme.  Whoever wants to upgrade - is very welcome to.  Whoever doesn't - should stay in their current version (and they'll have the branch available for reference if needed).
DON'T BE AFRAID OF RELEASING BREAKING-CHANGES,  they are inevitable,  especially if new features are expected and wanted,  while you still maintain an option for the users to move/stay freely between the releases.
BTW,  if you'll release a breaking changes in the next version,  sync to main,  and a user who doesn't have a ref installs the "new" package during an ESPHome upgrade for example,  it won't let them install obviously (or things won't work).  Which will make them go here,  and either upgrade correctly using breaking-changes,  or adding ref to use their latest version that worked - if you'll add it to the docs as a reminder ;) .     Users will always be ok, in my opinion :)
This is pretty much how every public package maintainers handle their packages,  I don't see any reason why it shouldn't be like this here as well :)
But of course it's not mandatory,  you should proceed however you see fit!
Hope I was able to share my way around this subject,
I'm here for any follow-ups:)
Thanks!

One last thing,   I personally have no issue with your documentation.
Yes,  it's heavy,   but what can you do this is a well-packed package with lots of features and options.
Again,  users should find their way around,   we as devs need to do our best to help them - and our only option is with a detailed doc:)
Thanks Lubeda

I just wanted to also say thank you @lubeda , and that I agree with @ofirsnb's comments. Breaking changes are a part of progress, and having releases/versions that people can pin should be more than enough.
I'm actually looking forward to the customizable queue that I saw in the 2023.9.0 branch, so if that one is "done", I'll switch over to it.

2023.9.0 has stopped.  2023.9.1 branch has received even more work... I'm using it on 4 clocks.  👍

I also think the 2023.9.1 is the version to go for production. I don't like the internal structure of the code but the features are very useful.

Maybe it makes sense to release 2023.9.1?

@lubeda
In my opinion, we have a desynchronization of branches, in latest there are some changes, in 2024.6.pre others, even if you look at the commits, in latest, PR 229, 234, 246 are accepted, and in 2024.6.pre, PR 229, 234, 236, 237, 238, 239, 241 are accepted, but at the same time, transparency fixes are going to latest.
Maybe it's worth collecting everything in a single branch, and merging all the changes into master, and releasing release 2024.11, otherwise we'll get even more confused.
latest: https://github.com/lubeda/EspHoMaTriXv2/commits/latest/
2024.6.pre: https://github.com/lubeda/EspHoMaTriXv2/commits/2024.6.pre/
compare latests -> 2024.6.pre: https://github.com/lubeda/EspHoMaTriXv2/compare/2024.6.pre...latest
compare 1024.6.pre -> latests: https://github.com/lubeda/EspHoMaTriXv2/compare/latest...2024.6.pre

Hi All. I mirror the view of @ofirsnb - to be honest I was wondering why there hadn't been any activity in 10 months as I don't generally go hunting for new versions and monitor the main branch. I'm also seeing some glitches in this version (it's possible ESPHome has some breaking changes that impact the old branches) and found this thread before I reported anything. I'm going to work through getting to 2023.9.1 as there seems to be a lot of work put in already there. Looking forward to new features and hopefully fixing some things I've noticed (so I don't duplicate issue reporting, I'll hold off reporting any until I upgrade)

I want the customization of newer branches, but I put it off in hopes that I would only have to do "one re-write". I fear I'm even more confused now. I'll need to dedicate a day to figuring out what branch/version to use...

IMHO this the most relevant https://github.com/lubeda/EspHoMaTriXv2/tree/2024.12.1

Each esphome release is packed with suprises (breaking changes), so it is hard to stay up to date for me. Each user can decide which version of esphome he uses. So there is not one combination of esphome, ehmtx and yaml that fits all.
So ehmtx is prone to breaking on every esphome update.
My suggestion is:
Keep esphome up to date with the latest official version!
For ehmtx use the newest version tag by manually editing the ref tag in the external_componets section in your yaml.
Only change your selected ehmtx version if there are compile errors. But expect manual changes to your yaml or even your automations.


Expose TransportType to users?

I needed to write a TCP client in an armeria server and ended up using the TransportType internal class to also take advantage of CommonPools. Since we expose CommonPools, does it make sense to expose TransportType for this sort of use case? Maybe it's overkill, just want to get it out there.
    var workerGroup = CommonPools.workerGroup();
    var bootstrap = new Bootstrap();
    bootstrap.group(workerGroup);
    // NOTE(rag): This is an internal API, but should be stable. Will see about exposing it to
    // users.
    bootstrap.channel(TransportType.socketChannelType(workerGroup));
    bootstrap.option(ChannelOption.ALLOCATOR, PooledByteBufAllocator.DEFAULT);
    bootstrap.option(ChannelOption.SO_KEEPALIVE, true);
    bootstrap.handler(
        new ChannelInitializer<SocketChannel>() {
          @Override
          protected void initChannel(SocketChannel ch) {
            ch.pipeline().addLast(new Handler());
          }
        });

    channel = bootstrap.connect(target.getHost(), target.getPort()).syncUninterruptibly().channel();

Sounds OK to me. How about moving to armeria.common?

I'm also thinking of just adding methods to EventLoopGroups -> serverChanneLClass, socketChannelType and datagramChannelType. The other methods seem like they'd never have any use for users. What do you think about just adding those three methods to EventLoopGroups, which just calls into TransportType for the corresponding methods?


Horizon timeout after transaction is added to ledger

https://github.com/stellar/go/issues/305

Any updates on this? We've had to regress to depending on stellar.org's horizon instance to submit transactions. I would really like to get off of that dependency (especially since it has other fairly annoying implications for our system).
Thanks for all your awesome work!

Seems to me that this issue is not limited only to the Docker version...
Using GO Horizon built on my own VM (not from docker), I repeatedly encountered this issue occasionally, when I tried to pump over 50tps (for short duration, like 1 minute) to it.
(Can't really reproduce it, as it happens occasionally but not guaranteed.)
And this issue seems to happen more rare, when I am using a VM with better RAM & CPU assigned.
So, maybe this issue happens more often on docker, as less resource is available to the docker?

@istrau2 could you reveal how the hardware you've been using is?

This is not restricted to this docker image. We observe the same with https://github.com/satoshipay/docker-stellar-horizon and a standalone Stellar Core and Postgres (1x Core, 1x Horizon).

Not related to Docker: https://github.com/stellar/go/issues/305#issuecomment-404564549

So I believe it is highly possible this is related to docker, I would like to announce my very odd but repeatable findings.
ANNOUNCEMENT:
Debian jessy core i3 machine 8 gig ram, 5400 rpm drive 320 gig
ubuntu 18.04.1 core i7 machine (gaming mobo) 16 gig ram 256 ssd (read write not off hand)
ubuntu 18.04.1  razer blade 15 2018 (see specs for yourself)
load image first time using docker commands, 504 timeout every time.
leave docker running, restart machine (leaving docker running as is for clarification)
run same test for creating account transaction (and other subsequent transactions) success
My speculation would be some interprocess com or networking issue. Might have time to try and look into this at a later date but these are my findings for those who come across this issue. As I am one to not restart a machine unless needed, and went out of my way to verify this was not some resource issue as seen that my first machine is much lower resource than the other two I was using. To which concluded my assumption that resources had nothing to do with this. There is another issue open on the stellar go github that is easy to find if anyone wants to rely that information over there. But I can very much so say this ticket should probably still be open. As docker does seem to possibly play a role here.

I found out that restarting horizon using the supervisorctl fixed the issue.

Enter the docker container
run supervisorctl
restart horizon

I found out that restarting horizon using the supervisorctl fixed the issue.

Enter the docker container
run supervisorctl
restart horizon

That makes sense, as restarting computer probably causes this to happen in the container.

I found out that restarting horizon using the supervisorctl fixed the issue.

this does indeed magically fixes the problem in some cases. i experienced this ona test network without using code from this repo at all.


How to add border radius to dognut chart item?

How can i add rounded corners for the dognut chart sections?

Hi @CuriousProgramer
Use the new <PieChartPro> component.
It supports curved edges using the the following properties inside the objects in the data array-

isStartEdgeCurved
isEndEdgeCurved
startEdgeRadius
endEdgeRadius

See https://github.com/Abhinandan-Kushwaha/react-native-gifted-charts/issues/554#issuecomment-2018958023

import React from "react";
import { View, SafeAreaView, StyleSheet } from "react-native";
import { PieChart, PieChartPro } from "react-native-gifted-charts";
import Text from "../atoms/Text";

export const PieChartComponent = ({}: any) => {
  const data = [
    {
      name: "A",
      value: 50,
      color: "#00C777",
      isStartEdgeCurved: true,
      isEndEdgeCurved: true,
      startEdgeRadius: 4,
      endEdgeRadius: 4,
    },
    {
      name: "B",
      value: 30,
      color: "#9997EF",
      isStartEdgeCurved: true,
      isEndEdgeCurved: true,
      startEdgeRadius: 4,
      endEdgeRadius: 4,
    },
    {
      name: "C",
      value: 20,
      color: "#FF934F",
      isStartEdgeCurved: true,
      isEndEdgeCurved: true,
      startEdgeRadius: 4,
      endEdgeRadius: 4,
    },
    {
      name: "A",
      value: 50,
      color: "#95EB73",
      isStartEdgeCurved: true,
      isEndEdgeCurved: true,
      startEdgeRadius: 4,
      endEdgeRadius: 4,
    },
    {
      name: "B",
      value: 30,
      color: "#FF6363",
      isStartEdgeCurved: true,
      isEndEdgeCurved: true,
      startEdgeRadius: 4,
      endEdgeRadius: 4,
    },
    {
      name: "C",
      value: 20,
      color: "#FED97E",
      isStartEdgeCurved: true,
      isEndEdgeCurved: true,
      startEdgeRadius: 4,
      endEdgeRadius: 4,
    },
  ];
  return (
    <View className="flex-1 justify-center items-center my-6">
      <PieChartPro
        data={data}
        donut
        innerRadius={80}
        outerRadius={100}
        labelRadius={75}
        padAngle={0.02}
        animate={true}
        backgroundColor="#000"
      />
    </View>
  );
};

Hi @Abhinandan-Kushwaha , this is how it looks like with above properties. I'm looking to achieve something like this

,

Hi @CuriousProgramer
Thanks for reporting this issue. I will fix it and release an update within 1 or 2 days. Thanks for your patience.

got chart breaking behaviour as well from these options.

and?

Any solutions? Mine is still breaking


Charging Station > Edit: Amps are not displayed in Legrand Charging Station in QA named 'cptest'

Fixed in 12622ab9b454d16a42124635a51666264c4844cc


Real world app example

See https://realworld.io/

@somebee I'm gonna snag this one. I mentioned it in discord a while ago.

Here's an imba v1 example someone made a while back.
https://github.com/cartonalexandre/imba-realworld-example-app

Here's a frontend for realworld.io coded with imba 2.
If anyone would like to have a go at doing the backend, knock yourself out: https://github.com/ericvida/imba-2-realworld-example-app


Language settings

Hi, thank you so much for this project.
Is there a way to set the language to Portuguese or translate the labels in some way?

Hi @MaichiLydia,
I was looking for exactly that, and I remembered that probably the paid market sdk uses the language of the device, and that is exactly what happens.

Oh thanks @rodrigopequeno for the observation. Do you know if there is a way to set a single language despite of the device language ?

@MaichiLydia just looking deeply into the Mercado Livre SDK to confirm but I believe he doesn't have that option.

Thanks for the answers


Allow third parameter of dependence function be become negative.

Pull Request Test Coverage Report for Build 406

2 of 2 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 89.274%

Totals

Change from base Build 403:
0.0%

Covered Lines:
1057

Relevant Lines:
1184

💛  - Coveralls


Fixes #1128 - Development of next-generation TCP adaptor.

Note that this commit occludes/replaces the legacy tcp-adaptor module.
Summary of squashed commits:

Added new adaptor module and a munch of boilerplate stubs for later development. Listeners and connectors now get core connections and links set up. Preparatory refactoring
Added the new message/stream API for unicast/cut-through WIP - listener side is implemented up to message stream API WIP - Added connector-side raw-connection establishment. WIP - Added handling of no-server error case.
WIP - Simplifications to the message headers, implemented server stream Feature: user-streaming links for manual streaming in adaptors WIP - Refactored clinet/server to inbound/outbound to take advantage of symmetries WIP - implemented lifecycle of connections in both LSIDE and CSIDE. WIP - even cleaner version of full connection lifecycle - still leaks messages WIP - fixed the delivery/message leak
WIP - Added connection cleanup at router shutdown
WIP - Completed activation for raw connections - one-router transfer tested WIP - Added vFlow metrics for octets and latency
Added vFlow attribute generation.  Removed debug printf statements. Improved listener and connector deletion:  clean up connections and end the vflow record. Add test-and-set conditions for activation of core, cut-through-inbound, and cut-through-outbound Separate typedef of qd_connection_t into a new header file to eliminate unresolved cross dependencies. Minor updates in preparation for new work.
Implemented the outgoing cutthrough flow for AMQP links. WIP - incoming cut-through on AMQP side
Use a null-body to delimit the beginning of the data stream. End-to-end TCP in multi-router cases now operates.  Lots of corner cases to clean up. Fixed tcp connection close issues.  Added more trace logs. Added operStatus updates for listeners.
Moved to core_connection per tcp_connection to remove mutex issues.  Still need to convert some wakes to direct calls. Removed unimplemented and unused call: qdr_link_delete Major updates to activation and read flow.  Many tests pass. Fixed a bug with cut-through send not handling short-duration connections. Fixed issues with long streaming content.
Fixed a buffer leak for long streaming messages.  Fixed a delivery leak. Added more stats for listeners and connectors.
Added a wrapper in "threading" for posix spin-locks. Refactored activation - works much better.  Still a delivery leak to be fixed. Logging improvements
Fixed delivery leak.
WIP - Refactoring to provide protection during activation. Stabilized the single-router case.
Added delayed close for tcplite_connections
Free all resources on deletion of listeners and connectors. Close window around the raw_opened flag
Quieted the logs.  Added a pointer check before extracting error conditions. Remove use of spinlocks in the adaptor.
Recover from Q3-stall
Hold off streaming until there is a counterflow stream. Convert spinlocks to adaptive spin locks for better user-space performance. Threading/execution cleanup; logging cleanup
Added assertions for thread-types.
General suffix and comment cleanup
Added 'notify' to cutthrough notification function names.  Removed redundant calls to them.  These changes were a result of feedback from team review.
Properly clean up deliveries on error-dispositions. Use a safe pointer in message-activation context to protext against lost connections. Make connector/listener deletion thread safe.
Improved the generation of stats for management.
Merge Fixups
Updates to the tcp tests
Ported the tiered buffer allocation scheme from main. Make the normalization function public.  Use the calculated platform memory limit as the default ceiling. Minor updates. Added race-suppression for the new memory stat access. Cleaning up failures in the regression tests.

It should be noted that not all of the regression tests pass with this initial PR commit:
	 64 - system_tests_tcp_adaptor (Failed)
	 65 - system_tests_tcp_adaptor_tls (Failed)
	 66 - system_tests_http2_tls (Failed)


Compile error

Hi, when I tried to run the unit_test, it returned an error shows below. Have you ever met this problem?
I am using CUDA 10.1, PyTorch 1.3.1
Thank you!
Traceback (most recent call last):
  File "/home/zihao/Nutstore/4DCompletion/venv/lib/python3.6/site-packages/torch/utils/cpp_extension.py", line 1030, in _build_extension_module
    check=True)
  File "/usr/lib/python3.6/subprocess.py", line 438, in run
    output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['ninja', '-v']' returned non-zero exit status 1.

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "unit_test.py", line 1, in <module>
    import torch, chamfer3D.dist_chamfer_3D, fscore
  File "/home/zihao/Nutstore/4DCompletion/code/complete_pc/ChamferDistancePytorch/chamfer3D/dist_chamfer_3D.py", line 13, in <module>
    "/".join(os.path.abspath(__file__).split('/')[:-1] + ["chamfer3D.cu"]),
  File "/home/zihao/Nutstore/4DCompletion/venv/lib/python3.6/site-packages/torch/utils/cpp_extension.py", line 661, in load
    is_python_module)
  File "/home/zihao/Nutstore/4DCompletion/venv/lib/python3.6/site-packages/torch/utils/cpp_extension.py", line 830, in _jit_compile
    with_cuda=with_cuda)
  File "/home/zihao/Nutstore/4DCompletion/venv/lib/python3.6/site-packages/torch/utils/cpp_extension.py", line 883, in _write_ninja_file_and_build
    _build_extension_module(name, build_directory, verbose)
  File "/home/zihao/Nutstore/4DCompletion/venv/lib/python3.6/site-packages/torch/utils/cpp_extension.py", line 1043, in _build_extension_module
    raise RuntimeError(message)
RuntimeError: Error building extension 'chamfer_3D': [1/3] :/usr/local/cuda-10.1:/usr/local/cuda-10.1/bin/nvcc -DTORCH_EXTENSION_NAME=chamfer_3D -DTORCH_API_INCLUDE_EXTENSION_H -isystem /home/zihao/Nutstore/4DCompletion/venv/lib/python3.6/site-packages/torch/include -isystem /home/zihao/Nutstore/4DCompletion/venv/lib/python3.6/site-packages/torch/include/torch/csrc/api/include -isystem /home/zihao/Nutstore/4DCompletion/venv/lib/python3.6/site-packages/torch/include/TH -isystem /home/zihao/Nutstore/4DCompletion/venv/lib/python3.6/site-packages/torch/include/THC -isystem :/usr/local/cuda-10.1:/usr/local/cuda-10.1/include -isystem /home/zihao/Nutstore/4DCompletion/venv/include/python3.6m -D_GLIBCXX_USE_CXX11_ABI=0 -D__CUDA_NO_HALF_OPERATORS__ -D__CUDA_NO_HALF_CONVERSIONS__ -D__CUDA_NO_HALF2_OPERATORS__ --expt-relaxed-constexpr -gencode=arch=compute_61,code=sm_61 --compiler-options '-fPIC' -std=c++11 -c /home/zihao/Nutstore/4DCompletion/code/complete_pc/ChamferDistancePytorch/chamfer3D/chamfer3D.cu -o chamfer3D.cuda.o
FAILED: chamfer3D.cuda.o
:/usr/local/cuda-10.1:/usr/local/cuda-10.1/bin/nvcc -DTORCH_EXTENSION_NAME=chamfer_3D -DTORCH_API_INCLUDE_EXTENSION_H -isystem /home/zihao/Nutstore/4DCompletion/venv/lib/python3.6/site-packages/torch/include -isystem /home/zihao/Nutstore/4DCompletion/venv/lib/python3.6/site-packages/torch/include/torch/csrc/api/include -isystem /home/zihao/Nutstore/4DCompletion/venv/lib/python3.6/site-packages/torch/include/TH -isystem /home/zihao/Nutstore/4DCompletion/venv/lib/python3.6/site-packages/torch/include/THC -isystem :/usr/local/cuda-10.1:/usr/local/cuda-10.1/include -isystem /home/zihao/Nutstore/4DCompletion/venv/include/python3.6m -D_GLIBCXX_USE_CXX11_ABI=0 -D__CUDA_NO_HALF_OPERATORS__ -D__CUDA_NO_HALF_CONVERSIONS__ -D__CUDA_NO_HALF2_OPERATORS__ --expt-relaxed-constexpr -gencode=arch=compute_61,code=sm_61 --compiler-options '-fPIC' -std=c++11 -c /home/zihao/Nutstore/4DCompletion/code/complete_pc/ChamferDistancePytorch/chamfer3D/chamfer3D.cu -o chamfer3D.cuda.o
/bin/sh: 1: :/usr/local/cuda-10.1:/usr/local/cuda-10.1/bin/nvcc: not found
[2/3] c++ -MMD -MF chamfer_cuda.o.d -DTORCH_EXTENSION_NAME=chamfer_3D -DTORCH_API_INCLUDE_EXTENSION_H -isystem /home/zihao/Nutstore/4DCompletion/venv/lib/python3.6/site-packages/torch/include -isystem /home/zihao/Nutstore/4DCompletion/venv/lib/python3.6/site-packages/torch/include/torch/csrc/api/include -isystem /home/zihao/Nutstore/4DCompletion/venv/lib/python3.6/site-packages/torch/include/TH -isystem /home/zihao/Nutstore/4DCompletion/venv/lib/python3.6/site-packages/torch/include/THC -isystem :/usr/local/cuda-10.1:/usr/local/cuda-10.1/include -isystem /home/zihao/Nutstore/4DCompletion/venv/include/python3.6m -D_GLIBCXX_USE_CXX11_ABI=0 -fPIC -std=c++11 -c /home/zihao/Nutstore/4DCompletion/code/complete_pc/ChamferDistancePytorch/chamfer3D/chamfer_cuda.cpp -o chamfer_cuda.o
FAILED: chamfer_cuda.o
c++ -MMD -MF chamfer_cuda.o.d -DTORCH_EXTENSION_NAME=chamfer_3D -DTORCH_API_INCLUDE_EXTENSION_H -isystem /home/zihao/Nutstore/4DCompletion/venv/lib/python3.6/site-packages/torch/include -isystem /home/zihao/Nutstore/4DCompletion/venv/lib/python3.6/site-packages/torch/include/torch/csrc/api/include -isystem /home/zihao/Nutstore/4DCompletion/venv/lib/python3.6/site-packages/torch/include/TH -isystem /home/zihao/Nutstore/4DCompletion/venv/lib/python3.6/site-packages/torch/include/THC -isystem :/usr/local/cuda-10.1:/usr/local/cuda-10.1/include -isystem /home/zihao/Nutstore/4DCompletion/venv/include/python3.6m -D_GLIBCXX_USE_CXX11_ABI=0 -fPIC -std=c++11 -c /home/zihao/Nutstore/4DCompletion/code/complete_pc/ChamferDistancePytorch/chamfer3D/chamfer_cuda.cpp -o chamfer_cuda.o
In file included from /home/zihao/Nutstore/4DCompletion/venv/lib/python3.6/site-packages/torch/include/torch/csrc/Device.h:3:0,
                 from /home/zihao/Nutstore/4DCompletion/venv/lib/python3.6/site-packages/torch/include/torch/csrc/api/include/torch/python.h:8,
                 from /home/zihao/Nutstore/4DCompletion/venv/lib/python3.6/site-packages/torch/include/torch/extension.h:6,
                 from /home/zihao/Nutstore/4DCompletion/venv/lib/python3.6/site-packages/torch/include/torch/csrc/api/include/torch/torch.h:6,
                 from /home/zihao/Nutstore/4DCompletion/code/complete_pc/ChamferDistancePytorch/chamfer3D/chamfer_cuda.cpp:1:
/home/zihao/Nutstore/4DCompletion/venv/lib/python3.6/site-packages/torch/include/torch/csrc/python_headers.h:9:20: fatal error: Python.h: No such file or directory
compilation terminated.
ninja: build stopped: subcommand failed.

Maybe it's because I'm using a virtual environment, so some files are missing?

Dear @Salingo
Thanks for reaching out,
I never had this.
They are a few interesting threads :
https://github.com/mapillary/inplace_abn/issues/104
https://github.com/mapillary/inplace_abn/issues/106#issuecomment-475460496
https://github.com/zhanghang1989/PyTorch-Encoding/issues/162
It looks like a path problem.
This line is especially suspicious
/bin/sh: 1: :/usr/local/cuda-10.1:/usr/local/cuda-10.1/bin/nvcc: not found
Are you sure cuda 10.1 is correctly installed? (you can check in /usr/local/cuda-10.1)
Best regards,
Thibault

Hi, thanks for your reply, I have fixed the issue, indeed it is the problem with my path setting.
Thanks again!

Hi, thanks for your reply, I have fixed the issue, indeed it is the problem with my path setting.
Thanks again!

Hey! how did you set the paths, I am facing a similar problem

请问您解决这个问题了吗？我也遇到了这种情况


Manhwa

Your issue may already be reported!
Please search on the issue tracker before creating one.
Expected Behavior

Current Behavior
While reading manhwa, korean manga, the screen lags while trying to swipe to next page, and even zoom in and zoom out, whipe lagging.

Possible Solution
It could be nice if the reader was like in mangazone app, they do great job to make manhwa not lag or sudden zooms. Yet both manga and manhwa works great. Maybe some setting where we could choose manga to read with swiping and for manhwa the infinite scroll setting.

Steps to Reproduce (for bugs)

1.search manhwa
2.select any one
3.click on any page
4.try swiping to next page.
Context
 I cannot read manhwa at all. If i try swiping to nexf page or even swipe down to read it zooms out and i have to zoom in for every next page, which again just cause mofe trouble like lag and unintentional zoom in and out.

Your Environment

Version used:2.9.4 stable release
Operating System version: android

Had the Same problem..
Got rid of it my lowering my screen Resolution in display settings


Updating install instructions

Also we should give the CLI commands to add a new system_admin user (or maybe modify the db to add a 2nd user).  Logging in as the one in the config isn't practical since he's in every channel, so you cannot use that account while the load test is running.

+1 on @coreyhulen suggestion.  Will add.

@coreyhulen Changes have been made. Ready for re-review.


chore: change readme to be version specific

change readme to be version specific

Description
Since nestjs-pact is, for now, incompatible with the latest version of pact-js, the readme should help users install the correct version of this dependency
Motivation and Context
I believe this change to be necessary since running the command as documented in the README so far install pact-js v10 which leads to the following error when registering the PactProviderModule.
TypeError: Cannot read properties of undefined (reading 'logLevel')

    50 |
    51 |   beforeAll(async () => {
  > 52 |     const moduleRef = await Test.createTestingModule({
       |                       ^
    53 |       imports: [AppModule, PactProviderModule.register(options)],
    54 |     }).compile();
    55 |

    at new Verifier (../../../node_modules/@pact-foundation/src/dsl/verifier/verifier.ts:33:21)
    at InstanceWrapper.useFactory [as metatype] (../../../node_modules/nestjs-pact/dist/providers/pact-verifier.provider.js:8:23)
    at TestingInjector.instantiateClass (../../../node_modules/@nestjs/core/injector/injector.js:343:55)
    at callback (../../../node_modules/@nestjs/core/injector/injector.js:53:45)
    at TestingInjector.resolveConstructorParams (../../../node_modules/@nestjs/core/injector/injector.js:132:24)
    at TestingInjector.loadInstance (../../../node_modules/@nestjs/core/injector/injector.js:57:13)
    at TestingInjector.loadProvider (../../../node_modules/@nestjs/core/injector/injector.js:84:9)
        at async Promise.all (index 3)
    at TestingInstanceLoader.createInstancesOfProviders (../../../node_modules/@nestjs/core/injector/instance-loader.js:47:9)
    at ../../../node_modules/@nestjs/core/injector/instance-loader.js:32:13
        at async Promise.all (index 22)
    at TestingInstanceLoader.createInstances (../../../node_modules/@nestjs/core/injector/instance-loader.js:31:9)
    at TestingInstanceLoader.createInstancesOfDependencies (../../../node_modules/@nestjs/core/injector/instance-loader.js:21:9)
    at TestingInstanceLoader.createInstancesOfDependencies (../../../node_modules/@nestjs/testing/testing-instance-loader.js:14:9)
    at TestingModuleBuilder.compile (../../../node_modules/@nestjs/testing/testing-module.builder.js:47:9)
    at Object.<anonymous> (api/certifiers/pact/nestJS.contract.e2e.ts:52:23)

How Has This Been Tested?
N/A
Types of changes

[ x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x ] My change requires a change to the documentation.
[x ] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

Hey @Mazata thanks for the changes, I have incorporated in https://github.com/pact-foundation/nestjs-pact/commit/6456757cdc3a42f862639f61d5d2432205f84943


[optparse] Conflicting Option String

My Environment:
Python 2.7.10
Ubuntu 15.10
pip 8.1.0
Installed underwear via pip install underwear
Traceback:
$ python manage.py deploy
Traceback (most recent call last):
  File "manage.py", line 13, in <module>
    execute_from_command_line(sys.argv)
  File "<scrubbed>/local/lib/python2.7/site-packages/django/core/management/__init__.py", line 353, in execute_from_command_line
    utility.execute()
  File "<scrubbed>/local/lib/python2.7/site-packages/django/core/management/__init__.py", line 345, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "<scrubbed>/local/lib/python2.7/site-packages/django/core/management/base.py", line 348, in run_from_argv
    self.execute(*args, **cmd_options)
  File "<scrubbed>/local/lib/python2.7/site-packages/django/core/management/base.py", line 399, in execute
    output = self.handle(*args, **options)
  File "<scrubbed>/local/lib/python2.7/site-packages/underwear/management/commands/deploy.py", line 14, in handle
    '--extra-vars', '@%s' % './deploy/underwear.yml'])
  File "<scrubbed>/local/lib/python2.7/site-packages/underwear/run_underwear.py", line 55, in deploy
    help="set additional variables as key=value or YAML/JSON", default=[])
  File "/usr/lib/python2.7/optparse.py", line 1021, in add_option
    self._check_conflict(option)
  File "/usr/lib/python2.7/optparse.py", line 996, in _check_conflict
    option)
optparse.OptionConflictError: option -e/--extra-vars: conflicting option string(s): -e, --extra-vars

New deptree:
underwear==0.4.5
  - ansible [installed: 1.9.4]
    - paramiko [installed: 1.16.0]
      - ecdsa [required: >=0.11, installed: 0.13]
      - pycrypto [required: >=2.1, installed: 2.6.1]
    - setuptools
    - PyYAML [installed: 3.11]
    - pycrypto [required: >=2.6, installed: 2.6.1]
    - jinja2 [installed: 2.8]
      - MarkupSafe [installed: 0.23]

Error can be resolved by removing this line

All issues resolved by manually installing ansible==1.8.4

:+1:


VerticalBar time series does not render with only one datapoint

Using react-vis 1.11.7, when I render a VerticalBarSeries on a time-based x-axis and the data only has one datapoint I get the error Received NaN for the x attribute. If this is expected, cast the value to a string.
When the data has more than one datapoint everything works alright.
Example:
const chart = props => {
  const timestamp = new Date('May 23 2017').getTime();
  const ONE_DAY = 86400000;
  const data = [
    {x: timestamp, y: 1}, // when there is only one datapoint the chart errors
    // {x: timestamp + ONE_DAY, y: 1}, // when this is uncommented the chart renders normally
  ];

  return (
      <XYPlot
        height={300}
        width={350}
        xType="time"
      >
        <XAxis />
        <YAxis />
        <VerticalBarSeries
          data={data}
        />
      </XYPlot>
    );
};

Having same problem.


Fix Origin test and update kube to v1.7.6

@mrunalp @sameo @rhatdan PTAL

lint failures.

lint failures.

fixed

[retest]

[retest]

All...check your e-mail, I've got a manual run going against this PR.  Details, along with a dump of all the commands I used are in the mail.

@mrunalp manual fullresults.txt sofar...Is this expected:
TASK [Copy test policy.json file] ***********************************************************************
changed: [pr_917_f26] => {"changed": true, "checksum": "ec1503792b34e725800dab319f14358ed4321d3c", "dest": "/etc/containers/policy.json", "gid": 0, "group": "root", "md5sum": "efaa771a19dfcc83864e54ab9509a34f", "mode": "0644", "owner": "root", "secontext": "system_u:object_r:etc_t:s0", "size": 4778, "src": "/root/src/github.com/kubernetes-incubator/cri-o/test/policy.json", "state": "file", "uid": 0}
changed: [pr_917_rhel74] => {"changed": true, "checksum": "ec1503792b34e725800dab319f14358ed4321d3c", "dest": "/etc/containers/policy.json", "gid": 0, "group": "root", "md5sum": "efaa771a19dfcc83864e54ab9509a34f", "mode": "0644", "owner": "root", "secontext": "system_u:object_r:etc_t:s0", "size": 4778, "src": "/root/src/github.com/kubernetes-incubator/cri-o/test/policy.json", "state": "file", "uid": 0}

TASK [run integration tests RHEL] ***********************************************************************
skipping: [pr_917_f26] => {"changed": false, "skip_reason": "Conditional result was False", "skipped": true}
fatal: [pr_917_rhel74]: FAILED! => {"async_result": {"failed": true, "module_stderr": "Shared connection to <IP_ADDRESS> closed.\r\n", "module_stdout": "Traceback (most recent call last):\r\n  File \"/root/.ansible/tmp/ansible-tmp-1505920820.68-3449922694115/async_status.py\", line 136, in <module>\r\n    shutil.rmtree(temp_path)\r\nNameError: name 'temp_path' is not defined\r\n", "msg": "MODULE FAILURE", "rc": 0}, "changed": false, "failed": true, "msg": "async task produced unparseable results"}
...ignoring

TASK [run integration tests RHEL with xunit results] ****************************************************
skipping: [pr_917_rhel74] => {"changed": false, "skip_reason": "Conditional result was False", "skipped": true}
skipping: [pr_917_f26] => {"changed": false, "skip_reason": "Conditional result was False", "skipped": true}

TASK [run integration tests Fedora] *********************************************************************
skipping: [pr_917_rhel74] => {"changed": false, "skip_reason": "Conditional result was False", "skipped": true}
...still...running...

?

travis failures here.

Playbook failures look disk-space related...guessing it's a cloud-init problem...

Fixed now

Fixed Travis now

LGTM

okay, I think we can rebase this and start a manual run with #928 merged.

@mrunalp this is rebased now.

@cevich This is ready for a manual test run.

/test all

LGTM

:tada:

@mrunalp @runcom FYI - the manual run of this hung during the e2e test on RHEL.  I just checked and it's still hung.  Tried ssh'ing into the RHEL VM and I get no response, it seems to connect, but then hangs there w/ no output - likely what's confusing ansible.  Since this is merged, I'll kill the test, but let me know if anyone wants to inspect the RHEL VM - I'll leave it up.


Moving source files around to make it easier to consume clarity-tools as a package

@sarveshnagpal,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


Can valid_email be a replacement for rails_email_validator?

The module secure_validatable suggests using the rails_email_validator gem which seems to be unmaintained (last commit dates back to Jun 16, 2011). Is the gem valid_email a valid replacement?
Many thanks,
Mauro

I agree. I haven't tried to replace the gem yet but it is convoluted. @maurosbu if you create a PR for this I'd be glad to review it. If not, I'll add it to the list. :-)

Closing old issues, if you have more info to contribute please feel free to re-open.


feat: implement RustGenerator proof-of-concept

Description
Implements RustGenerator proof of concept with support for basic primitives, enum, structs, tuple, and union types.
Usage example
Check out examples/rust-generate-crate for a demo. You'll need to install Rust to compile the generated package.
Feature table

Feature
Status
Info

Union (polymorphic type)
✅ done

Enum (group of constants)
✅ done

Array (unordered collection)
✅ done

Tuple (ordered collection)
✅ done

Next steps

Implement To/From String methods (serde_json)
Implement To/From u8 bytes methods (serde_bytes)
Publish asyncapi-nats-rs repo for a full example of models in the wild

Related issue(s)
Fixes #509

Thank you for the thorough & thoughtful review! I blocked some time to check in revisions tomorrow (Friday) AM PDT.
:gem:  I should mention that I originally worked from master - so I really appreciate how much effort went into improving the generator development experience for next. The MetaModel refactor was excellent and made it a breeze to jump right in. Nice job y'all!

Wow, that was damn quick and you even targeted next star_struckmuscle Had a few comments and suggestions but overall looks great!
You can ignore all the CI checks, I am trying to solve them in another PR, so we merge regardless of failures.
Some extra changes which are needed:

Please add rust to the list of generators: https://github.com/asyncapi/modelina/blob/next/README.md
https://github.com/asyncapi/modelina/tree/next/docs#languages need to have rust added (I see I need to add Dart here as well)
https://github.com/asyncapi/modelina/blob/next/docs/usage.md#generate-dart-models needs a basic rust usage example or just link to existing one.

If you want to continue to be engaged and take ownership of the rust generator feel free to add yourself as code owner in this PR +1

How do y'all prefer to solve merge conflicts? Let me know if you prefer I rebase and force-push, create a merge commit from next -> branch, or merge next -> branch with --no-ff

Just rebased & fixed the last lingering code smells. Thanks again for helping me polish up this PR and for all your work on AsyncAPI. 🙇♀
Stay tuned for a Rust + NATS client generator next.✌

You can ignore the code smells, those seem to be mine 🧐
Regarding the bug, that seems like its relevant, or is it a false positive?

/rtm

@all-contributors please add @leigh-johnson for code, test, example, docs, maintenance

The team grows @magicmatatjahu @Samridhi-98 @ron-debajyoti 🎉
@leigh-johnson you should have been invited to join as collaborator 😃 Welcome to the team!
You are also illegible to join the AsyncAPI TSC (in case you didn't catch that 😄), all you have to do is add yourself to the list of TSC members here: https://github.com/asyncapi/community/blob/master/TSC_MEMBERS.json. An example of how to do it can be seen here: https://github.com/asyncapi/community/pull/430
Glad to have you onboard, and thanks for the patience with this PR 🍺


Apply restart game on menu

Pull Request Test Coverage Report for Build 130

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 89.906%

Totals

Change from base Build 129:
0.0%

Covered Lines:
271

Relevant Lines:
290

💛  - Coveralls


Collision map wrong around Giant's Foundry

This was fixed in version 1.9.3. Restart your client to fetch the update


Dev versions of MSBuild should put the version with commit ID in the logo

We get banners like
Microsoft (R) Build Engine version <IP_ADDRESS>335
Copyright (C) Microsoft Corporation. All rights reserved.

But it'd be really nice (for like 8 people) if that had the full form of the version that includes the git commit ID for easy checkout.

for like 8 people

Heh, I think many people are interested in git SHA-1 hashes these days and tend to do creative stuff (like using node.js to download the source of some project and compile it on the fly for some weird reasons..)

This doesn't quite work yet because only official builds have the assembly informational version for full framework and .NET core.  I'm going to defer this to when we are using the new SDK.


Update markup for Tabs to match vanilla example

This issue is for updating the Tabs component family to match the accessible markup detailed in: http://carbondesignsystem.com/components/tabs/code

The markup between the two seems to match now after https://github.com/IBM/carbon-components-react/pull/1040


Support Portfolio Recovery Between Live Algorithm Deployments Using QuantConnect Paper Brokerage

Expected Behavior
QuantConnect/Lean PaperBrokerage gets the current portfolio state (cashbook, positions, orders) like the other paper brokerage implementations that fetch the information from the brokerage.
Actual Behavior
When a live deployment is restarted, the portfolio information is lost.
Potential Solution
N/A
P.S.:

It would also be helpful to fetch Alpha Stream insights that have not been expired if we consider Alpha Stream restarts too.
When securities are fetched, they are added to the user-defined universe. They should be added to the universe that added them in the first place.

Reproducing the Problem
Stop and redeploy a live algorithm with open positions.
Checklist

[x] I have completely filled out this template
[x] I have confirmed that this issue exists on the current master branch
[x] I have confirmed that this is not a duplicate issue by searching issues
[x] I have provided detailed steps to reproduce the issue

See https://github.com/QuantConnect/Lean/pull/5647 & https://github.com/QuantConnect/Lean/pull/5651

This is already solved in production 👍


Update buyables with Arceuus Signet

Updated the buy command to check for favour, update buyables with the arceuus signet.
Closes #3171
Edit - Also tested the POH building of Dark Altar & Occult Altar which this now allows.

[x] I have tested all my changes thoroughly.

bump should be a relatively easy review and would be nice to have, have tested everything I could think of


[Additional Parameter Request] Codeunit 80 Sales-Post - OnAfterReturnRcptLineInsert

Hi Team,
In codeunit 90 we need possibility to have additional checks in the procedure InsertReturnReceiptLine. Standard publisher OnAfterReturnRcptLineInsert would suit us if it had additional parameter TempWhseShptHeader: Record "Warehouse Shipment Header" and TempWhseRcptHeader: Record "Warehouse Receipt Header".

local procedure OnAfterReturnRcptLineInsert(var ReturnRcptLine: Record "Return Receipt Line"; ReturnRcptHeader: Record "Return Receipt Header"; SalesLine: Record "Sales Line"; ItemShptLedEntryNo: Integer; WhseShip: Boolean; WhseReceive: Boolean; CommitIsSuppressed: Boolean; SalesCrMemoHeader: Record "Sales Cr.Memo Header"; TempWhseShptHeader: Record "Warehouse Shipment Header"; TempWhseRcptHeader: Record "Warehouse Receipt Header")

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


Setting properties before upgrade overrides Polymer's setters using the polyfill.

Please try this jsbin in safari: http://jsbin.com/zifigi/edit?html,output.  The code for x-example is available in https://gist.githubusercontent.com/blasten/861b640568f8b8268f89/raw/b6eab660b4cf6e439404e310e921f1cd5e27ae05/x-example.html

Manipulating elements before WebComponentsReady is not supported when custom elements are not implemented natively in the browser.
What's happening here is the instance property is covering up the setter/getter that Polymer installs on the element prototype. Polymer could detect this and correct the problem, but it would incur a per instance cost that we'll need to evaluate.


chore: Increase playground file limit

Signed-off-by: Charith Ellawala<EMAIL_ADDRESS>

Codecov Report

Merging #750 (1a33e39) into main (695fda3) will increase coverage by 0.20%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #750      +/-   ##
==========================================
+ Coverage   54.20%   54.41%   +0.20%
==========================================
  Files          96       96
  Lines       10128    10128
==========================================
+ Hits         5490     5511      +21
+ Misses       4169     4149      -20
+ Partials      469      468       -1

Impacted Files
Coverage Δ

internal/server/tests.go
92.54% <0.00%> (-1.18%)
:arrow_down:

internal/audit/local/badgerdb.go
62.57% <0.00%> (-0.63%)
:arrow_down:

internal/engine/engine.go
69.78% <0.00%> (+0.80%)
:arrow_up:

internal/storage/index/builder.go
83.90% <0.00%> (+5.17%)
:arrow_up:

internal/engine/trace.go
72.30% <0.00%> (+6.15%)
:arrow_up:

internal/compile/errors.go
55.55% <0.00%> (+15.87%)
:arrow_up:


Connected with Digipad 2.0 under Honda Jazz

Hi,
I used Raspberry Pi 3 A+ over Honda Jazz Digipad 2.0 and based on steps mentioned under readme file, and was able to connect it successfully. Tried calls and it works, also tried google assistant and it worked as well.
I have below query:

When Wifi is on and bluetooth is off - it doesn't connect.
When Wifi is off and bluetooth is on - it connects and then makes wifi connection active (even though it's disabled).

Isn't it should connect to wifi post boot up and then switch on the bluetooth if it's off? So basically, if either of the connection is active it should connect and made other connection on.
For location it should be enabled in all case or else it will ask for location permission over the phone and we have to enable it but this is the case for wired connection as well.
Please let me know thoughts on this.
Thanks.

This is normal Android Auto behaviour that we don't control. Android Auto only gets activated on phone when particular type of bluetooth device connects. Once bluetooth is connected, it exchanges wifi connection information automatically and connects to the wifi automatically. It bluetooth is not enabled, it cannot know that the wifi is for Android auto, or the wifi password. Since the wifi often does not have internet, users are anyway not expected to connect manually to the wifi.

Okay, this is great. I wasn't aware of this behavior. Thanks a lot for this detailed clarification.
Also, I was wondering what if head unit is having Wi-Fi support. Does it will disconnect Wi-Fi of head unit if already connected and then connect to wireless android auto Wi-Fi after connecting to Bluetooth? For Bluetooth I noticed, it disconnects head unit Bluetooth connection if already present connects to AAWireless dongle Bluetooth connection and then connects to Wi-Fi and then head unit Bluetooth connection is active again.
I haven't tried from my end but my head unit has dongle support for Wi-Fi hotspot.

For Bluetooth I noticed, it disconnects head unit Bluetooth connection if already present connects to AAWireless dongle Bluetooth connection and then connects to Wi-Fi and then head unit Bluetooth connection is active again.

This is new to me. I thought most phones can connect to multiple bluetooth at once. And it should keep the headunit bluetooth connected. Just for experimentation, you can maybe also try dongle mode and how this behaves, because it requires both bluetooth devices to be connected at once.

Also, I was wondering what if head unit is having Wi-Fi support. Does it will disconnect Wi-Fi of head unit if already connected and then connect to wireless android auto Wi-Fi after connecting to Bluetooth?

I also haven't tested this. But I believe many recent phones do have ability to connect to more than one wifi network at once. Maybe it can keep headunit wifi connected for internet and dongle for Android Auto, not sure. For the phones that don't support multiple wifi, it'll disconnect from the headunit wifi and use mobile network for internet.

For Bluetooth I noticed, it disconnects head unit Bluetooth connection if already present connects to AAWireless dongle Bluetooth connection and then connects to Wi-Fi and then head unit Bluetooth connection is active again.

This is new to me. I thought most phones can connect to multiple bluetooth at once. And it should keep the headunit bluetooth connected. Just for experimentation, you can maybe also try dongle mode and how this behaves, because it requires both bluetooth devices to be connected at once.

You are correct. I noticed carefully and then found that it connects to my headunit first followed by AAWireless dongle and then connects to Wifi and then bluetooth for AAWirelss gets diconnected. So I believe it's working as per standard.

Also, I was wondering what if head unit is having Wi-Fi support. Does it will disconnect Wi-Fi of head unit if already connected and then connect to wireless android auto Wi-Fi after connecting to Bluetooth?

I also haven't tested this. But I believe many recent phones do have ability to connect to more than one wifi network at once. Maybe it can keep headunit wifi connected for internet and dongle for Android Auto, not sure. For the phones that don't support multiple wifi, it'll disconnect from the headunit wifi and use mobile network for internet.

I tested this today and found that both wifi are connected and working simultaneously. So headunit is being tethered via my phone hotspot and AAWireless Wifi is also connected as expected. Both were able to consume data / from my phone. So this too works as expected.

One last query from my end, I believe Raspberry Pi 3 A+ has capability of 5 GHz and 2.4 GHz connections were other Pi boards zero W or zero 2W uses 2.4 GHz based on their capability. Also, I think I was connected 5 GHz connection based on my checks performed when I was connected with AA Wireless. Can you please confirm if this will always be the case that it will use the highest possible channel (2.4 GHz / 5 GHz) for WiFi connection based on boards capability?

Can you please confirm if this will always be the case that it will use the highest possible channel (2.4 GHz / 5 GHz) for WiFi connection based on boards capability?

Not automatically. But currently the RPi 3A+ and RPi 4 images are configured to use the 5GHz channel, and the other two boards are configured to use the 2.4GHz channel by default. If we add a new board, we need to configure the image correctly to use the appropriate channel as available.

This is great. Thanks a lot again for clarifying. Seems investing in good board works as 5 GHz is fast and noise free. I see no lag in music play, phone communication and navigation handling. All works seamlessly. Thanks a lot for sharing your good work and keep it up. I started using this more frequently than wired connection due to effortless connection. I will let you know if I have further feedback / related queries / issues.
Once again, thank you and closing this thread.


Modified the code to facilitate the below feature

1.In the current form on raml to spring mvc stub creation it forces the plug-in to be run inside the maven project .I have done code changes to make it enable in both inside or external to maven project. I have tested and made sure the code changes are backward compatible .

Thanks for your commit - will be reviewing it asap :)

Looks,  good :)

Thanks .Hope it will be merged soon to master  for me to refer the main stream .

Can you please merge with the main stream .


Bump op-node to v1.1.4

Review Error for roberto-bayardo @ 2023-10-05 19:22:58 UTC
User failed mfa authentication, see go/mfa-help


Wrong Folder Path for Open after OSX Rename in picker

VSCode Version: 1.0.0
OS Version: OSX 10.11

Steps to Reproduce

File -> Open
Browse to project folder (example_proj).
Right click in OSX file selector to rename project folder

Rename project folder (new_example_proj)
Project folder stays selected but now has new name.
Click Open

Expected
Project opens with renamed folder
Actual

Folder does not open.
Deselecting and reselecting the renamed project folder fixes the problem.

Seems to work if you move focus away after renaming but not if you hit enter directly.

@mattbierner I suggest you report this to Electron and see if this is something Electron can even control.


Content mismatch on the hyperlink

Greetings Team,
I was going through the link "https://learn.microsoft.com/en-us/azure/data-factory/data-factory-tutorials"
There is a section "Copy and Ingest Data" which has mentioned in the 4th Option 'Amazon S3 to ADLS Gen2'.
However In the page there is the Heading mentioned for 'Load data into Azure Data Lake Storage Gen2 with Azure Data Factory'. Could you please check if I did mistake while checking at my end.
Thank You
Ravindra Kumar

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

ID: 0ee5bdfe-c68b-09f6-0b7e-aa9c13ed70ef
Version Independent ID: 77dd85ba-eb47-0324-d7aa-5cd01f617a98
Content: Azure Data Factory tutorials - Azure Data Factory
Content Source: articles/data-factory/data-factory-tutorials.md
Service: data-factory
Sub-service: tutorials
GitHub Login: @kromerm
Microsoft Alias: makromer

@rksraviravindra
Thanks for your feedback! We will investigate and update as appropriate.

Hi @rksraviravindra
Please review the following link for your reference. In the Azure documentation, they mention using Amazon S3 as a source and ADLS Gen2 as a destination. Nothing about this is unclear. The document should be checked again.
https://learn.microsoft.com/en-us/azure/data-factory/load-azure-data-lake-storage-gen2#:~:text=In the Source,Storage Gen2 account.

@rksraviravindra
We are going to close this thread, if there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation.


chore: improve page change animation with repositories pages

Fix #1765
Closes #1774

demo video
https://github.com/user-attachments/assets/89f7cc9d-069b-49b5-848b-c309a328fa82

@Sayamame-beans どう？

よさそう


Strange rename MS behavour

Noticed that an EMU measurement set for beam14 failed to go through all four rounds of self-calibration. It seems that somehow the checks in copy_and_clean_ms_casagain that aim to detect whether a output MS already exists (which then automatically removes the file) picked up the original MS.
I can trace the code and do not see how this function in isolation could rename -> delete -> try to rename. I am wondering whether somehow the naming creation tool is incorrect. I did find an unsaved change to the MS name creation function that might be related.
Only other consideration is some weird race / concurrent task issue. At a loss on this. Raising this issue to try to keep my thoughts together and track it.
For some ~5000 flint runs as far as I remember I have never seen this. Confusion.
Measurement set to be self-calibrated: ms=MS(path=PosixPath('/scratch3/gal16b/emu_data/51818/proc_2/51818/SB51818.EMU_2006-55.beam14.round3.ms'), column='CORRECTED_DATA', beam=None, spw=None, field=None, model_column='MODEL_DATA')
02:49:32 AM
task_gaincal_applycal_ms-122
flint

Updating gaincal options with: {'solint': '600s', 'calmode': 'ap', 'round': 0, 'minsnr': 0.0, 'uvrange': '>235m', 'selectdata': True, 'gaintype': 'G', 'nspw': 4}
02:49:32 AM
task_gaincal_applycal_ms-122
flint

Detected a previous round of self-calibration.
02:49:32 AM
task_gaincal_applycal_ms-122
flint

Output MS name will be /scratch3/gal16b/emu_data/51818/proc_2/51818/SB51818.EMU_2006-55.beam14.round4.ms.
02:49:32 AM
task_gaincal_applycal_ms-122
flint

Copying /scratch3/gal16b/emu_data/51818/proc_2/51818/SB51818.EMU_2006-55.beam14.round3.ms to /scratch3/gal16b/emu_data/51818/proc_2/51818/SB51818.EMU_2006-55.beam14.round4.ms.
02:49:32 AM
task_gaincal_applycal_ms-122
flint

/scratch3/gal16b/emu_data/51818/proc_2/51818/SB51818.EMU_2006-55.beam14.round4.ms already exists. Removing it.
02:49:32 AM
task_gaincal_applycal_ms-122
flint

Removing folder /scratch3/gal16b/emu_data/51818/proc_2/51818/SB51818.EMU_2006-55.beam14.round4.ms
02:49:32 AM
task_gaincal_applycal_ms-122
flint

Encountered exception during execution:
Traceback (most recent call last):
  File "/scratch3/gal16b/miniforge3/envs/flint_main/lib/python3.8/site-packages/prefect/engine.py", line 2099, in orchestrate_task_run
    result = await call.aresult()
  File "/scratch3/gal16b/miniforge3/envs/flint_main/lib/python3.8/site-packages/prefect/_internal/concurrency/calls.py", line 327, in aresult
    return await asyncio.wrap_future(self.future)
  File "/scratch3/gal16b/miniforge3/envs/flint_main/lib/python3.8/site-packages/prefect/_internal/concurrency/calls.py", line 352, in _run_sync
    result = self.fn(*self.args, **self.kwargs)
  File "/scratch3/gal16b/packages/flint_main/flint/flint/prefect/common/imaging.py", line 248, in task_gaincal_applycal_ms
    return gaincal_applycal_ms(
  File "/scratch3/gal16b/packages/flint_main/flint/flint/selfcal/casa.py", line 256, in gaincal_applycal_ms
    cal_ms = copy_and_clean_ms_casagain(ms=ms, round=round, rename_ms=rename_ms)
  File "/scratch3/gal16b/packages/flint_main/flint/flint/selfcal/casa.py", line 88, in copy_and_clean_ms_casagain
    ms = rename_ms_and_columns_for_selfcal(
  File "/scratch3/gal16b/packages/flint_main/flint/flint/ms.py", line 795, in rename_ms_and_columns_for_selfcal
    raise FileNotFoundError(
FileNotFoundError: /scratch3/gal16b/emu_data/51818/proc_2/51818/SB51818.EMU_2006-55.beam14.round3.ms does not exists or is not a directory (hence measurement set).

Actually happened again in a RACS field. This was using the --rename-ms option on the CLI. So very likely it is related to that and the problem is somewhere in the rename_ms_and_columns_for_selfcal function and the steps in preparation for it.
Still unclear what. For this field this was the only error across all beams and rounds of self-calibration. It also happened on the last round of self-cal. Maybe related to the zip archive option? Though this was turned off for the EMU data so probably not.
Measurement set to be self-calibrated: ms=MS(path=PosixPath('/scratch3/gal16b/racs_low3_proc/proc/57475/SB57475.RACS_1336-09.beam22.round3.ms'), column='CORRECTED_DATA', beam=22, spw=None, field=None, model_column='MODEL_DATA')
02:44:43 AM
task_gaincal_applycal_ms-123
flint

Updating gaincal options with: {'solint': '480s', 'calmode': 'ap', 'round': 0, 'minsnr': 0.0, 'uvrange': '>235m', 'selectdata': True, 'gaintype': 'G', 'nspw': 4}
02:44:43 AM
task_gaincal_applycal_ms-123
flint

Detected a previous round of self-calibration.
02:44:43 AM
task_gaincal_applycal_ms-123
flint

Output MS name will be /scratch3/gal16b/racs_low3_proc/proc/57475/SB57475.RACS_1336-09.beam22.round4.ms.
02:44:43 AM
task_gaincal_applycal_ms-123
flint

Copying /scratch3/gal16b/racs_low3_proc/proc/57475/SB57475.RACS_1336-09.beam22.round3.ms to /scratch3/gal16b/racs_low3_proc/proc/57475/SB57475.RACS_1336-09.beam22.round4.ms.
02:44:43 AM
task_gaincal_applycal_ms-123
flint

/scratch3/gal16b/racs_low3_proc/proc/57475/SB57475.RACS_1336-09.beam22.round4.ms already exists. Removing it.
02:44:43 AM
task_gaincal_applycal_ms-123
flint

Removing folder /scratch3/gal16b/racs_low3_proc/proc/57475/SB57475.RACS_1336-09.beam22.round4.ms
02:44:43 AM
task_gaincal_applycal_ms-123
flint

Encountered exception during execution:
Traceback (most recent call last):
  File "/scratch3/gal16b/miniforge3/envs/flint_main/lib/python3.8/site-packages/prefect/engine.py", line 2099, in orchestrate_task_run
    result = await call.aresult()
  File "/scratch3/gal16b/miniforge3/envs/flint_main/lib/python3.8/site-packages/prefect/_internal/concurrency/calls.py", line 327, in aresult
    return await asyncio.wrap_future(self.future)
  File "/scratch3/gal16b/miniforge3/envs/flint_main/lib/python3.8/site-packages/prefect/_internal/concurrency/calls.py", line 352, in _run_sync
    result = self.fn(*self.args, **self.kwargs)
  File "/scratch3/gal16b/packages/flint_main/flint/flint/prefect/common/imaging.py", line 248, in task_gaincal_applycal_ms
    return gaincal_applycal_ms(
  File "/scratch3/gal16b/packages/flint_main/flint/flint/selfcal/casa.py", line 256, in gaincal_applycal_ms
    cal_ms = copy_and_clean_ms_casagain(ms=ms, round=round, rename_ms=rename_ms)
  File "/scratch3/gal16b/packages/flint_main/flint/flint/selfcal/casa.py", line 88, in copy_and_clean_ms_casagain
    ms = rename_ms_and_columns_for_selfcal(
  File "/scratch3/gal16b/packages/flint_main/flint/flint/ms.py", line 795, in rename_ms_and_columns_for_selfcal
    raise FileNotFoundError(
FileNotFoundError: /scratch3/gal16b/racs_low3_proc/proc/57475/SB57475.RACS_1336-09.beam22.round3.ms does not exists or is not a directory (hence measurement set).
02:44:43 AM
task_gaincal_applycal_ms-123
prefect.task_runs
Finished in state Failed('Task run encountered an exception FileNotFoundError: /scratch3/gal16b/racs_low3_proc/proc/57475/SB57475.RACS_1336-09.beam22.round3.ms does not exists or is not a directory (hence measurement set).')

And again for a separate field, again on the last round of self-calibration
Measurement set to be self-calibrated: ms=MS(path=PosixPath('/scratch3/gal16b/racs_low3_proc/proc/57778/SB57778.RACS_1419-09.beam29.round3.ms'), column='CORRECTED_DATA', beam=29, spw=None, field=None, model_column='MODEL_DATA')
02:45:21 AM
task_gaincal_applycal_ms-130
flint

Updating gaincal options with: {'solint': '480s', 'calmode': 'ap', 'round': 0, 'minsnr': 0.0, 'uvrange': '>235m', 'selectdata': True, 'gaintype': 'G', 'nspw': 4}
02:45:21 AM
task_gaincal_applycal_ms-130
flint

Detected a previous round of self-calibration.
02:45:21 AM
task_gaincal_applycal_ms-130
flint

Output MS name will be /scratch3/gal16b/racs_low3_proc/proc/57778/SB57778.RACS_1419-09.beam29.round4.ms.
02:45:21 AM
task_gaincal_applycal_ms-130
flint

Copying /scratch3/gal16b/racs_low3_proc/proc/57778/SB57778.RACS_1419-09.beam29.round3.ms to /scratch3/gal16b/racs_low3_proc/proc/57778/SB57778.RACS_1419-09.beam29.round4.ms.
02:45:21 AM
task_gaincal_applycal_ms-130
flint

/scratch3/gal16b/racs_low3_proc/proc/57778/SB57778.RACS_1419-09.beam29.round4.ms already exists. Removing it.
02:45:21 AM
task_gaincal_applycal_ms-130
flint

Removing folder /scratch3/gal16b/racs_low3_proc/proc/57778/SB57778.RACS_1419-09.beam29.round4.ms
02:45:21 AM
task_gaincal_applycal_ms-130
flint

Encountered exception during execution:
Traceback (most recent call last):
  File "/scratch3/gal16b/miniforge3/envs/flint_main/lib/python3.8/site-packages/prefect/engine.py", line 2099, in orchestrate_task_run
    result = await call.aresult()
  File "/scratch3/gal16b/miniforge3/envs/flint_main/lib/python3.8/site-packages/prefect/_internal/concurrency/calls.py", line 327, in aresult
    return await asyncio.wrap_future(self.future)
  File "/scratch3/gal16b/miniforge3/envs/flint_main/lib/python3.8/site-packages/prefect/_internal/concurrency/calls.py", line 352, in _run_sync
    result = self.fn(*self.args, **self.kwargs)
  File "/scratch3/gal16b/packages/flint_main/flint/flint/prefect/common/imaging.py", line 248, in task_gaincal_applycal_ms
    return gaincal_applycal_ms(
  File "/scratch3/gal16b/packages/flint_main/flint/flint/selfcal/casa.py", line 256, in gaincal_applycal_ms
    cal_ms = copy_and_clean_ms_casagain(ms=ms, round=round, rename_ms=rename_ms)
  File "/scratch3/gal16b/packages/flint_main/flint/flint/selfcal/casa.py", line 88, in copy_and_clean_ms_casagain
    ms = rename_ms_and_columns_for_selfcal(
  File "/scratch3/gal16b/packages/flint_main/flint/flint/ms.py", line 795, in rename_ms_and_columns_for_selfcal
    raise FileNotFoundError(
FileNotFoundError: /scratch3/gal16b/racs_low3_proc/proc/57778/SB57778.RACS_1419-09.beam29.round3.ms does not exists or is not a directory (hence measurement set).

Even stranger. It looks like it did go through the self-calibration, and then tried to do the self-calibration again?
Measurement set to be self-calibrated: ms=MS(path=PosixPath('/scratch3/gal16b/racs_low3_proc/proc/57912/SB57912.RACS_1419-04.beam06.round3.ms'), column='CORRECTED_DATA', beam=6, spw=None, field=None, model_column='MODEL_DATA')
06:21:37 AM
task_gaincal_applycal_ms-140
flint

Updating gaincal options with: {'solint': '480s', 'calmode': 'ap', 'round': 0, 'minsnr': 0.0, 'uvrange': '>235m', 'selectdata': True, 'gaintype': 'G', 'nspw': 4}
06:21:37 AM
task_gaincal_applycal_ms-140
flint

Detected a previous round of self-calibration.
06:21:37 AM
task_gaincal_applycal_ms-140
flint

Output MS name will be /scratch3/gal16b/racs_low3_proc/proc/57912/SB57912.RACS_1419-04.beam06.round4.ms.
06:21:37 AM
task_gaincal_applycal_ms-140
flint

Copying /scratch3/gal16b/racs_low3_proc/proc/57912/SB57912.RACS_1419-04.beam06.round3.ms to /scratch3/gal16b/racs_low3_proc/proc/57912/SB57912.RACS_1419-04.beam06.round4.ms.
06:21:37 AM
task_gaincal_applycal_ms-140
flint

Renaming /scratch3/gal16b/racs_low3_proc/proc/57912/SB57912.RACS_1419-04.beam06.round3.ms to target=PosixPath('/scratch3/gal16b/racs_low3_proc/proc/57912/SB57912.RACS_1419-04.beam06.round4.ms')
06:21:37 AM
task_gaincal_applycal_ms-140
flint

Removing DATA and renaming CORRECTED_DATA
06:21:38 AM
task_gaincal_applycal_ms-140
flint

Using nominated DATA column for /scratch3/gal16b/racs_low3_proc/proc/57912/SB57912.RACS_1419-04.beam06.round4.ms
06:21:38 AM
task_gaincal_applycal_ms-140
flint

Flagging NaNs and zeros in DATA.
06:21:38 AM
task_gaincal_applycal_ms-140
flint

Will flag<PHONE_NUMBER>94 NaNs, zero'd data 167040, zero'd UVW 9507.
06:21:39 AM
task_gaincal_applycal_ms-140
flint

Flagging based on extreme Stokes-V, threshold dxy_thresh=4.0
06:21:39 AM
task_gaincal_applycal_ms-140
flint

Will flag<PHONE_NUMBER> extreme Stokes-V.
06:21:39 AM
task_gaincal_applycal_ms-140
flint

Flags before: 14016388, Flags after: 14022212, Difference 5824
06:21:39 AM
task_gaincal_applycal_ms-140
flint

Adding updated flags column
06:21:39 AM
task_gaincal_applycal_ms-140
flint

Will create calibration table /scratch3/gal16b/racs_low3_proc/proc/57912/SB57912.RACS_1419-04.beam06.round4.caltable.
06:21:40 AM
task_gaincal_applycal_ms-140
flint

Transforming /scratch3/gal16b/racs_low3_proc/proc/57912/SB57912.RACS_1419-04.beam06.round4.ms to have 4 SPWs
06:21:40 AM
task_gaincal_applycal_ms-140
flint

Successfully created the transformed measurement set /scratch3/gal16b/racs_low3_proc/proc/57912/SB57912.RACS_1419-04.beam06.round4.ms_transform with 4 SPWs.
06:22:16 AM
task_gaincal_applycal_ms-140
flint

Removing folder /scratch3/gal16b/racs_low3_proc/proc/57912/SB57912.RACS_1419-04.beam06.round4.ms
06:22:16 AM
task_gaincal_applycal_ms-140
flint

Renaming /scratch3/gal16b/racs_low3_proc/proc/57912/SB57912.RACS_1419-04.beam06.round4.ms_transform to /scratch3/gal16b/racs_low3_proc/proc/57912/SB57912.RACS_1419-04.beam06.round4.ms.
06:22:16 AM
task_gaincal_applycal_ms-140
flint

Solutions have been solved. Applying them.
06:22:43 AM
task_gaincal_applycal_ms-140
flint

Will attempt to merge all spws using cvel.
06:22:57 AM
task_gaincal_applycal_ms-140
flint

Measurement set to be self-calibrated: ms=MS(path=PosixPath('/scratch3/gal16b/racs_low3_proc/proc/57912/SB57912.RACS_1419-04.beam06.round3.ms'), column='CORRECTED_DATA', beam=6, spw=None, field=None, model_column='MODEL_DATA')
06:26:38 AM
task_gaincal_applycal_ms-140
flint

Updating gaincal options with: {'solint': '480s', 'calmode': 'ap', 'round': 0, 'minsnr': 0.0, 'uvrange': '>235m', 'selectdata': True, 'gaintype': 'G', 'nspw': 4}
06:26:38 AM
task_gaincal_applycal_ms-140
flint

Detected a previous round of self-calibration.
06:26:38 AM
task_gaincal_applycal_ms-140
flint

Output MS name will be /scratch3/gal16b/racs_low3_proc/proc/57912/SB57912.RACS_1419-04.beam06.round4.ms.
06:26:38 AM
task_gaincal_applycal_ms-140
flint

Copying /scratch3/gal16b/racs_low3_proc/proc/57912/SB57912.RACS_1419-04.beam06.round3.ms to /scratch3/gal16b/racs_low3_proc/proc/57912/SB57912.RACS_1419-04.beam06.round4.ms.
06:26:38 AM
task_gaincal_applycal_ms-140
flint

/scratch3/gal16b/racs_low3_proc/proc/57912/SB57912.RACS_1419-04.beam06.round4.ms already exists. Removing it.
06:26:38 AM
task_gaincal_applycal_ms-140
flint

Removing folder /scratch3/gal16b/racs_low3_proc/proc/57912/SB57912.RACS_1419-04.beam06.round4.ms
06:26:38 AM
task_gaincal_applycal_ms-140
flint

Encountered exception during execution:
Traceback (most recent call last):
  File "/scratch3/gal16b/miniforge3/envs/flint_main/lib/python3.8/site-packages/prefect/engine.py", line 2099, in orchestrate_task_run
    result = await call.aresult()
  File "/scratch3/gal16b/miniforge3/envs/flint_main/lib/python3.8/site-packages/prefect/_internal/concurrency/calls.py", line 327, in aresult
    return await asyncio.wrap_future(self.future)
  File "/scratch3/gal16b/miniforge3/envs/flint_main/lib/python3.8/site-packages/prefect/_internal/concurrency/calls.py", line 352, in _run_sync
    result = self.fn(*self.args, **self.kwargs)
  File "/scratch3/gal16b/packages/flint_main/flint/flint/prefect/common/imaging.py", line 248, in task_gaincal_applycal_ms
    return gaincal_applycal_ms(
  File "/scratch3/gal16b/packages/flint_main/flint/flint/selfcal/casa.py", line 256, in gaincal_applycal_ms
    cal_ms = copy_and_clean_ms_casagain(ms=ms, round=round, rename_ms=rename_ms)
  File "/scratch3/gal16b/packages/flint_main/flint/flint/selfcal/casa.py", line 88, in copy_and_clean_ms_casagain
    ms = rename_ms_and_columns_for_selfcal(
  File "/scratch3/gal16b/packages/flint_main/flint/flint/ms.py", line 795, in rename_ms_and_columns_for_selfcal
    raise FileNotFoundError(
FileNotFoundError: /scratch3/gal16b/racs_low3_proc/proc/57912/SB57912.RACS_1419-04.beam06.round3.ms does not exists or is not a directory (hence measurement set).

And again.
Measurement set to be self-calibrated: ms=MS(path=PosixPath('/scratch3/gal16b/racs_low3_proc/proc/57175/SB57175.RACS_1315-04.beam01.round1.ms'), column='CORRECTED_DATA', beam=1, spw=None, field=None, model_column='MODEL_DATA')
02:44:53 AM
task_gaincal_applycal_ms-37
flint
Updating gaincal options with: {'solint': '30s', 'calmode': 'p', 'round': 0, 'minsnr': 0.0, 'uvrange': '>235m', 'selectdata': True, 'gaintype': 'G', 'nspw': 1}
02:44:53 AM
task_gaincal_applycal_ms-37
flint
Detected a previous round of self-calibration.
02:44:53 AM
task_gaincal_applycal_ms-37
flint
Output MS name will be /scratch3/gal16b/racs_low3_proc/proc/57175/SB57175.RACS_1315-04.beam01.round2.ms.
02:44:53 AM
task_gaincal_applycal_ms-37
flint
Copying /scratch3/gal16b/racs_low3_proc/proc/57175/SB57175.RACS_1315-04.beam01.round1.ms to /scratch3/gal16b/racs_low3_proc/proc/57175/SB57175.RACS_1315-04.beam01.round2.ms.
02:44:53 AM
task_gaincal_applycal_ms-37
flint
/scratch3/gal16b/racs_low3_proc/proc/57175/SB57175.RACS_1315-04.beam01.round2.ms already exists. Removing it.
02:44:53 AM
task_gaincal_applycal_ms-37
flint
Removing folder /scratch3/gal16b/racs_low3_proc/proc/57175/SB57175.RACS_1315-04.beam01.round2.ms
02:44:53 AM
task_gaincal_applycal_ms-37
flint
Encountered exception during execution:
Traceback (most recent call last):
  File "/scratch3/gal16b/miniforge3/envs/flint_main/lib/python3.8/site-packages/prefect/engine.py", line 2099, in orchestrate_task_run
    result = await call.aresult()
  File "/scratch3/gal16b/miniforge3/envs/flint_main/lib/python3.8/site-packages/prefect/_internal/concurrency/calls.py", line 327, in aresult
    return await asyncio.wrap_future(self.future)
  File "/scratch3/gal16b/miniforge3/envs/flint_main/lib/python3.8/site-packages/prefect/_internal/concurrency/calls.py", line 352, in _run_sync
    result = self.fn(*self.args, **self.kwargs)
  File "/scratch3/gal16b/packages/flint_main/flint/flint/prefect/common/imaging.py", line 248, in task_gaincal_applycal_ms
    return gaincal_applycal_ms(
  File "/scratch3/gal16b/packages/flint_main/flint/flint/selfcal/casa.py", line 256, in gaincal_applycal_ms
    cal_ms = copy_and_clean_ms_casagain(ms=ms, round=round, rename_ms=rename_ms)
  File "/scratch3/gal16b/packages/flint_main/flint/flint/selfcal/casa.py", line 88, in copy_and_clean_ms_casagain
    ms = rename_ms_and_columns_for_selfcal(
  File "/scratch3/gal16b/packages/flint_main/flint/flint/ms.py", line 795, in rename_ms_and_columns_for_selfcal
    raise FileNotFoundError(
FileNotFoundError: /scratch3/gal16b/racs_low3_proc/proc/57175/SB57175.RACS_1315-04.beam01.round1.ms does not exists or is not a directory (hence measurement set).

This is looking like a file system issue and not a flint issue.

Reasonably certain that this was from lustre issues. Closing and it is not flint in origin.


addition of comments to readme

Adding proposals and discussion items to readme

The naming convention for the metadata file is something that may become standardized with the w3c tabular data model. Which I think is a good reason to adopt it too.

I started moving some of the proposals into issues, e.g. #7 to leave the README less cluttered.

I merged some of the changes proposed here. To provide a fixed baseline for first implementations in tools like BEASTling we want to create an initial release, and after this release the changes not yet merged should be re-formulated as issues.


Prompt triggering Azure OpenAI's content management policy

Bug description

Seems the write_code_review prompt triggerred Azure OpenAI's content management policy, so that some response was filtered.
Bug solved method

Environment information

LLM type and model name:
System version: macos
Python version: 3.11

packages version: 0.7.6
installation method: pip

Screenshots or logs

2024-03-18 17:34:53.145 | INFO     | metagpt.actions.write_code_review:run:183 - Code review and rewrite board.py: 1/2 | len(iterative_code)=1601, len(self.i_context.code_doc.content)=1601
2024-03-18 17:38:48.672 | WARNING  | metagpt.utils.common:wrapper:572 - There is a exception in role's execution, in order to resume, we delete the newest role communication message in the role's memory.
2024-03-18 17:38:48.681 | ERROR    | metagpt.utils.common:wrapper:554 - Exception occurs, start to serialize the project, exp:
Traceback (most recent call last):
  File "/Users/jason/python/llm/lib/python3.11/site-packages/metagpt/utils/common.py", line 549, in wrapper
    result = await func(self, *args, **kwargs)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/jason/python/llm/lib/python3.11/site-packages/metagpt/team.py", line 134, in run
    await self.env.run()
openai.BadRequestError: Error code: 400 - {'error': {'code': 'BadRequest', 'message': "The response was filtered due to the prompt triggering Azure OpenAI's content management policy. Please modify your prompt and retry. To learn more about our content filtering policies please read our documentation: \r\nhttps://go.microsoft.com/fwlink/?linkid=2198766.", 'param': None, 'type': None}}

This is the bug of Azure OpenAI's content management policy on the LLM side.
You can send the board.py source code under the project to Microsoft to report the issue.

Could you please show me the original prompt word?

Due to the lack of updates or replies by the user for a long time, we will close it. Please reopen it if necessary.


Bring back revamped calendar

Brings back revamped calendar: https://github.com/xHain-hackspace/xhain-website/pull/42
Added grid layout: https://github.com/xHain-hackspace/xhain-website/pull/50 (thanks @jdwillemse!)

todo:

rely on and integrate the calendar-bot  for parsing the events (wip - https://github.com/xHain-hackspace/xhain-website/pull/53)

Deploying preview to https://xHain-hackspace-xhain-website-pr-52.surge.sh

Ready for review, I guess. @gueldenstone can you please check it?

Found one bug (https://github.com/gueldenstone/calendar-bot/issues/7) but would not consider this to be a blocker. What do you think?

Found one bug (gueldenstone/calendar-bot#7) but would not consider this to be a blocker. What do you think?

I don't see an issue, we just need to remember to update the dependency later.

We fixed the bug (https://github.com/gueldenstone/calendar-bot/issues/7) :smile:


Aux window: Occurrences highlight remains even after losing focus

Version: 1.85.0-insider (user setup)
Commit: 94a3d7bac770b43ce97e9685715bef1a60d1a759
Date: 2023-12-01T19:00:37.339Z
Electron: 25.9.6
ElectronBuildId: 25531495
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.22631

@MrYuto I think that is expected, see https://code.visualstudio.com/updates/v1_84#_multidocument-highlighting
This should behave the same for when multiple editor groups are opened in the same window.

@bpasero The issue is that highlighted words remain until a new word is focused. In the main window, the highlights disappear when the word loses focus.

@MrYuto not for me in this case:

Do you have a case where highlights remove to reproduce?

@bpasero In the main window, If you click on a word and then on a blank line, the highlight disappears:

@MrYuto my assumption here is that the other editor is over a word that then is highlighted in the floating editor. There is probably a heuristic to decide which highlight to apply. Can you double check my theory?

@bpasero it doesn't matter if it's on the same word or not but I found out this only happens if the same editor is opened on the main window or in other windows (in this case the first floating editor highlights disappear after losing focus).

I can reproduce but this is not a floating window issue. It reproduces even when you just have 2 editor groups opened next to each other:

tl;dr: Setting editor.occurrencesHighlight to "off" fixes it.
I'm seeing what I think is the same bug, after upgrading to 1.85.1 (first upgrade in a number of months, so I've jumped a few versions). While writing this I think there are two distinct problems.
The first is when a single file is open:

Double-click a word. It highlights that word, and in a different grey highlights the same word in rest of document.
Press esc: nothing happens. I now need to click a blank line to get the highlights to go away.  (I'm sure esc used to get rid of it before??)

The second is much more annoying, but only seems to happen when I have same file open twice, after using Split Editor Right.

Double-click a word. It highlights that word, and (in a different shade of grey) highlights the same word in rest of window. In the other window it highlights some (but not all!) of the same word.
Esc doesn't get rid of it. Clicking a blank line does not get rid of it. All the grey highlights are there forever.
Closing the other window: still the highlights are there. I can now double-click a different word and see it highlight throughout document, click blank line gets rid of that one, but still my first set of highlights survive!
The only way to get rid of them is to close the editor and open it again. OR, reduce to just one window open, double-click it again, and then click a blank line.

Playing around, I've noticed it does not matter which window I do the double-click in, it is the window on the right where the unwanted highlights survive.

Regarding editor.multiDocumentOccurrencesHighlight mentioned in the 1.84 release notes, searching for that in settings doesn't find anything. But I do have occurrencesHighlight as mentioned in https://stackoverflow.com/a/77440938/841830
It is currently set to "singleFile"
If I set it to "off", everything works as it used to. Double-click still highlights within the open file (only), and esc now cancels it again :-)
BTW, testing the 3rd option, "multiFile", it appears to behave exactly as "singleFile" in every respect I described above.
Anyway, switching to "off" gives me exactly the behaviour I want, so I'm happy.

Friendly ping! Looks like this issue requires some further steps to be verified. Please provide us with the steps necessary to verify this issue.

Steps for verification:
Open a typescript file in split view, with content as follows:
class itemA {

}

class itemB {

}

new itemA()

new itemB()

In the left panel, click the itemA symbol.
In the right panel, click the same itemA symbol.
In the right panel, click anywhere else that isn't a symbol. choose any whitespace, etc

🐛 The highlights should disappear from the left panel, but persist in the right, even as you click around the right panel.
Fixed: On insiders, you should not be able to end up in a state with persistent highlights when your cursor is not on a symbol.


Link pop-up POI and Trail names on mobile

My concern is that people will click on a point and not notice the subtle change in the green bar at bottom, so this would be another avenue to reach the panel info. Examples:
Clicking on "Beck Lake" in popup would slide the panel up for Beck Lake. Clicking on "Des Plaines Trail System" would slide up the panel for Des Plaines Trail System:

Clicking on "Des Plaines Trail System" would slide up the panel for Des Plaines Trail System:

This is implemented in v2

@shua123 Added styling for this. Mobile with show linked text in pop-up to indicate link.

I need to update a few things here.

Moving from minor testing issues:
@shua123 svg right arrow missing here, drop after highlighted code:

Added with https://github.com/smartchicago/trailsy/commit/1e8cfc7d4f597e120c70170607c15d541f7f6877. It is positioned correctly in the html but the arrow is appearing next to the segment name (Red Paved) instead of next to system.

Couldn't fix it with CSS, no idea what's happening. If you put it before the highlighted code it seems to work.

Okay, I moved it up https://github.com/smartchicago/trailsy/commit/8c15ed7bec5a79316f1ae370c354e76000adbf97


[Bug]: Running theme dev moves current directory?

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?
Theme
Expected behavior
Run the shopify theme dev within my shopify directory
Actual behavior
Appears to run in a different directory because I'm getting the following message:
"It doesn’t seem like you’re running this command in a theme directory. Are you sure you want to proceed?"
Stack trace
No response
Reproduction steps
So my webpack build I use was on 2.0, seemed simple enough to just switch over the command which was originally:
"shopify:serve": "cd shopify && shopify theme serve",
and have now changed to:
"shopify:serve": "cd shopify && shopify theme dev",
This worked absolutely fine with 2.0 but now with 3.0 I'm getting the error it isn't in the correct directory?
The main task I'm running is this:
"start": "run-p -sr shopify:serve webpack:watch",
Also worth mentioning, I tried changing the 'shopify:serve' task to this too:
"shopify:serve": "cd shopify && node ../.config/path.js && shopify theme dev",
With path.js containing:
console.log('CURRENT PATH => ', process.cwd()); and it does indeed say its within the shopify directory. So I'm not sure what's going on here?
Operating System
Mac OS Ventura
Shopify CLI version (check your project's package.json if you're not sure)
3.39.0
Shell
No response
Node version (run node -v if you're not sure)
v19.5.0
What language and version are you using in your application?
No response

hey @lukecharle , I am running into same issue!
Are you using Themelab setup? Based on these commands you listed, it seem you may be. I am using ThemeLab and CLI v3 is not recognizing the subshell directory has changed!

hey @lukecharle , I am running into same issue!
Are you using Themelab setup? Based on these commands you listed, it seem you may be. I am using ThemeLab and CLI v3 is not recognizing the subshell directory has changed!

hey @lukecharle , I am running into same issue!
Are you using Themelab setup? Based on these commands you listed, it seem you may be. I am using ThemeLab and CLI v3 is not recognizing the subshell directory has changed!

I am indeed! Really don’t understand how this is any different to 2.0 though. Because it would still expect the Shopify theme structure so something is moving it out of the correct directory

@Arkham I know its another webpack build, but could you just try cloning this repo - https://github.com/uicrooks/shopify-theme-lab and changing shopify theme serve to shopify theme dev?
This is the build I've used, I don't see it being an issue with anything from it though?
I will try your suggestion

cd shopify && npm exec -- shopify theme dev does the job for me it seems!


Driver: enable -force-autolink-symbol on Darwin as well

This further generalises the support to Darwin where MachO is the object
file format.  This environment does not support COMDAT, so use
weak_odr to ensure that the symbol is coalesced and preserved.
Thanks to John McCall for reminding me of the weak odr on MachO!

Replace this paragraph with a description of your changes and rationale. Provide links to external references/discussions if appropriate.

Resolves SR-NNNN.

@swift-ci please test

CC: @rjmccall

Build failed
Swift Test Linux Platform
Git Sha - 151167ffc5c66a1d0079ee189851039af5b9ddc1

Build failed
Swift Test OS X Platform
Git Sha - 151167ffc5c66a1d0079ee189851039af5b9ddc1

CC: @jrose-apple - bleh, seems

Hmm, functions cannot have common linkage.  I wonder what we were doing previously.

I had a global int previously, I think.

Yeah, the difference is that it is a function now, and that cannot be common, it has to be weak (weak_odr is proper as we want the instances coalesced).  I can't make it linkonce_odr as that can be dead stripped.

@swift-ci please test

@swift-ci please test

You could make it not a function on non-COMDAT platforms.

I really would rather that we kept the behaviour the same on all the platforms.  The symbol needs to be a function since you cannot do cross-module data symbol references, but you can  do cross-module function references (as that can be trampolined).  I believe that the symbol should be preserved here with the llvm.compiler.used annotation of the symbol reference.

Build failed
Swift Test OS X Platform
Git Sha - 60ac0850c50ddb177e106b4963cf68c4ff6b23c7

I don't think anyone else is doing linkonce_odr + external visibility, so that feels like a risky thing to rely on. If you want to keep the behavior the same on all platforms, we should go back to not using comdat.

since you cannot do cross-module data symbol references

…in COFF

Um, I would be really surprised if linkonce_odr+external visibility would be unused in practice.  This is safe, the only concern is whether the symbol is dead stripped or not by the linker.

@swift-ci please test

Build failed
Swift Test Linux Platform
Git Sha - 60ac0850c50ddb177e106b4963cf68c4ff6b23c7

Build failed
Swift Test OS X Platform
Git Sha - 60ac0850c50ddb177e106b4963cf68c4ff6b23c7

We don't want to use linkonce_odr + default visibility because that creates a non-hidden weak symbol, which is heavily frowned upon in the Darwin world.
The easiest solution is to just pick a file from the module that's required to emit this.

Oh, I didn't realize that linkonce_odr would create a weak symbol.  Hmm, I believe that emitting the symbol strong has the problem that you end up with multiple definitions or you need to emit to a single file, which seems to cause problems with incremental builds?

Yes, linkonce_odr is basically weak_odr but dead-strippable when the declaration is unreferenced.
Jordan might know better what the problem with incremental builds is.  Maybe it's hard to agree on which file to emit the symbol in.  Adding or deleting a file to a build might cause issues with that except that they likely force recompilation of other files anyway.
It's certainly better to use a single code-generation pattern, but we already can't necessarily do so because of COMDATs, so if we need target-specific workarounds, so be it.

Jordan might know better what the problem with incremental builds is. Maybe it's hard to agree on which file to emit the symbol in. Adding or deleting a file to a build might cause issues with that except that they likely force recompilation of other files anyway.

Yeah, that's the problem. Specifically, adding a file does not force recompilation (and we got vehement requests for that during the Swift 2 days), so you could get duplicate symbols in that one rare case.

How is it valid for adding a file to not force recompilation?  Existing lookups are allowed to resolve to new declarations.

We do do that. We only rebuild the files that change, then we check their dependency info to see if they could have affected other files. But "is the first file" isn't tracked in any way at the moment.

Okay.  So we could probably fix this that way if we had a need to, like if there was something more expensive to emit at the module level.

Yeah. I think it'd even be as simple as adding a dummy "I am first" symbol to both the "provides" and "depends" sets of the first source file. That way, if anyone new "provides" it, the formerly-first file would get rebuilt, and no longer provide it itself.
But that said, the idea of special-casing the first file is also a hack. COMDAT / Common linkage is actually closer to the intent of this thing, and yet another option would be some kind of bonus object file. (But that only works if swiftc is also doing the linking.)

At least in the case of building with CMake (3.15+) - the linker driver is swiftc!

Hmm, sounds like we should try to serialise an indicator for the primary file in the module to the swiftmodule?

At least in the case of building with CMake (3.15+) - the linker driver is swiftc!

Yeah, but that's not the only interesting case. If you're in any build system that compiles and links in separate steps, you need to know there's an extra object file. (Though I guess there's already an extra object file for the wrapped module on non-Darwin.)

Can one of the admins verify this patch?

Please update the base branch to main by Oct 5th otherwise the pull request will be closed automatically.

How to change the base branch: (Link)
More detail about the branch update: (Link)