Rasa X Starter Pack Material

Added an SQLite DB pre-loaded with two conversations and the tag nlu-issue for use with the Rasa X starter pack material

@melindaloubser1 or @erohmensing would either of you be up for taking on this PR?

sure can do

probably because of time zones, I see Aug 11, not 10, and a different time. Might need to refer to convos by other means - maybe pre-tag them?

I think adding some more convos would be good - maybe a few more with NLU issues, so you can refer to them e.g. "You'll notice some NLU issues in other conversations. Try annotating the messages that weren't predicted correctly to improve your model"

I added a flag to the first NLU issue and re-worded the wiki to refer to the next conversation as opposed to timestamp. I don't really like the idea of referring to the conversation by tag since tagging is part of the workflow

Good point, could be confusing to use tags

Looks good!


Failed to enable Windows feature

Brief description of your issue
WinGet client can not enable the Windows features listed as the dependencies of the package due to the "80040154 Class not registered" error while invoking the DISM API, and hanged for about two minutes.
Probably related to https://github.com/microsoft/winget-cli/issues/3348.
A similar bug can be found when using Get-WindowsOptionalFeature -Online in the Microsoft Store version of PowerShell 7, which is described in https://github.com/PowerShell/PowerShell/issues/13866.
Steps to reproduce

Add the following lines to the local installer manifest:

Dependencies:
  WindowsFeatures:
  - Microsoft-Windows-Subsystem-Linux

Run winget install -m '<manifest>'

Expected behavior
The feature should be enabled successfully.
Actual behavior
The feature can not be enabled, and the output is misleading. 🫤

The log is as follows:
2023-09-02 20:24:00.134 [FAIL] D:\a\_work\1\s\external\pkg\src\AppInstallerCommonCore\WindowsFeature.cpp(82)\WindowsPackageManager.dll!00007FFAB3DE49AD: (caller: 00007FFAB3D4096A) LogHr(1) tid(359c) 80040154 Class not registered

2023-09-02 20:24:00.134 [FAIL] D:\a\_work\1\s\external\pkg\src\AppInstallerCommonCore\WindowsFeature.cpp(254)\WindowsPackageManager.dll!00007FFAB3DE52EF: (caller: 00007FFAB3D410E7) LogHr(2) tid(359c) C0040004
2023-09-02 20:24:00.134 [CORE] Windows Feature [Microsoft-Windows-Subsystem-Linux] does not exist
2023-09-02 20:24:00.134 [CLI ] Terminating context: 0x8a150104 at D:\a\_work\1\s\external\pkg\src\AppInstallerCLICore\Workflows\DependenciesFlow.cpp:de
2023-09-02 20:24:00.135 [FAIL] D:\a\_work\1\s\external\pkg\src\AppInstallerCommonCore\WindowsFeature.cpp(87)\WindowsPackageManager.dll!00007FFAB3D433A2: (caller: 00007FFAB3D40F6D) LogHr(3) tid(359c) C0040004

The portable version of the WinGet client works properly:

Environment
Windows Package Manager (Preview) v1.6.2291-preview
Copyright (c) Microsoft Corporation. All rights reserved.

Windows: Windows.Desktop v10.0.22621.2215
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.21.2291.0

"Virtual Machine Platform" is the feature used by WSL and it's called out in:

https://github.com/microsoft/winget-cli/issues/3320

We still need to get the WinGet 1.6 client out with dependency support and update validation to properly use the features. Then we will be able to submit a WSL manifest with a dependency on the "Virtual Machine Platform".

I don't think this is related to the feature to be enabled. It is also the same for NetFx3.
2023-09-02 19:23:38.857 [FAIL] D:\a\_work\1\s\external\pkg\src\AppInstallerCommonCore\WindowsFeature.cpp(82)\WindowsPackageManager.dll!00007FFAB0A949AD: (caller: 00007FFAB09F096A) LogHr(1) tid(61a4) 80040154 Class not registered

2023-09-02 19:23:38.858 [FAIL] D:\a\_work\1\s\external\pkg\src\AppInstallerCommonCore\WindowsFeature.cpp(254)\WindowsPackageManager.dll!00007FFAB0A952EF: (caller: 00007FFAB09F10E7) LogHr(2) tid(61a4) C0040004
2023-09-02 19:23:38.858 [CORE] Windows Feature [netfx3] does not exist
2023-09-02 19:23:38.859 [CLI ] Terminating context: 0x8a150104 at D:\a\_work\1\s\external\pkg\src\AppInstallerCLICore\Workflows\DependenciesFlow.cpp:de
2023-09-02 19:23:38.859 [FAIL] D:\a\_work\1\s\external\pkg\src\AppInstallerCommonCore\WindowsFeature.cpp(87)\WindowsPackageManager.dll!00007FFAB09F33A2: (caller: 00007FFAB09F0F6D) LogHr(3) tid(61a4) C0040004

@SpecterShell,
We've decided to move this feature back to being experimental :(
There is an issue with enabling the windows feature in packaged context, which is why it is throwing a COM exception (Class not registered). Since we are preparing to officially release a stable version of v1.6 soon, this will need to be addressed in v1.7.

We've updated this in WinGet 1.7. Windows Features are now supported as a package dependency.


A more robust way to gather facts from nodes

I have a local setup with Redis and some application nodes. I have another redis client that is snooping on the channels that the adapter is using.
Whenever I'm snooping I get this error:

Error: timeout reached while waiting for sockets response

I looked into it and this error is because while snooping request.numSub > request.msgCount since my other client is just a spy. It would be nice if observing the channel didn't break the functionality. Perhaps there could be a way to count participant subs only.
https://github.com/socketio/socket.io-redis-adapter/blob/3242d8e91baf94720df256ab422ec5c037f6a9e1/lib/index.ts#L380-L386

Perhaps there could be a way to count participant subs only.

I'm open to suggestions on this!

I'll think about it a bit and see if I can suggest anything useful.

@darrachequesne, so here's an idea. We can have the "active" participants subscribe to a "proxy" channel when they come online. Nothing actually goes through that particular channel, it's just used for a participant to explicitly mark themselves as a participant.

@doodlesbykumbi that's an interesting idea. That would be a backward incompatible change though, which means users will need to upgrade the whole cluster at the same time, isn't it?

@darrachequesne You can fall back to the request channel for backwards compatibility if desired.

I've created a PR to demonstrate the approach^

Ping @darrachequesne


Correct community calendar link

Existing meeting link goes to the OSSF: Developer Identity calendar. This PR updates link to the OpenSSF Community Calendar

Thanks!


I can't play any audio while Raspotify is playing

Hello, I've setted up raspotify and it's working fine but I have few problems:

amixer -q sset Master 5%+ I use this command to set the volume level of my pi. Seems that it does not have an effect on raspotify.
I can't play any sound files with vlc player while the music playing on spotify. I'm not getting any errors. Vlc is actually playing the file but I can't hear anything. When I stop the music I can hear when the vlc is playing. Also when I play something on vlc this time no sound from Raspotify even though it's playing.

I'd be very glad if you help me solve these problems.

I've solved the problem by doing:
cd /var/cache/raspotify
sudo mkdir .pulse
sudo sh -c 'echo "default-server = <IP_ADDRESS>" > .pulse/client.conf'
sudo chown -R raspotify:raspotify .pulse

Edit ~/.asoundrc :
pcm.pulse {
    type pulse
}

ctl.pulse {
    type pulse
}
pcm.default pulse
ctl.default pulse

Copy default.pa file to .pulse folder in user home
sudo cp /etc/pulse/default.pa ~/.pulse/default.pa
sudo chown -R <user>:<group> .pulse/

Then edit ~/.pulse/default.pa and insert
load-module module-native-protocol-tcp auth-ip-acl=<IP_ADDRESS>
at the bottom
Add raspotify to pulse-access group: (maybe this is not so important)
sudo addgroup raspotify pulse-access
Reboot :dancer:


Update README.md

Updated instructions throughout for more clarity and changed references from eb-ucldc-solr2 to eb-ucldc-solr2-prod

@aturner This is ready for review/merge


Suggesting that some delivery components that no longer work be removed

The USPS component, the UPS component and the FedEx components are all based on outdated methods like web scraping and have all been relatively abandoned.  I'd like to suggest removing all three since they haven't worked in some time now and there are other methods developed to do roughly the same thing.

My UPS component is working.

The fedex one, isn't logging in:
fedex: Error on device update!
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/site-packages/fedexdeliverymanager/__init__.py", line 64, in wrapped
    return function(*args)
  File "/usr/local/lib/python3.7/site-packages/fedexdeliverymanager/__init__.py", line 103, in get_packages
    raise FedexError(err)
fedexdeliverymanager.FedexError: failed to get shipment list: Relogin

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/src/app/homeassistant/helpers/entity_platform.py", line 261, in _async_add_entity
    await entity.async_device_update(warning=False)
  File "/usr/src/app/homeassistant/helpers/entity.py", line 377, in async_device_update
    await self.hass.async_add_executor_job(self.update)
  File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/src/app/homeassistant/util/__init__.py", line 224, in wrapper
    result = method(*args, **kwargs)
  File "/usr/src/app/homeassistant/components/fedex/sensor.py", line 85, in _update
    for package in fedexdeliverymanager.get_packages(self._session):
  File "/usr/local/lib/python3.7/site-packages/fedexdeliverymanager/__init__.py", line 66, in wrapped
    _login(*args)
  File "/usr/local/lib/python3.7/site-packages/fedexdeliverymanager/__init__.py", line 82, in _login
    raise FedexError('could not login')
fedexdeliverymanager.FedexError: could not login

And I stopped using USPS because it stopped working 6 or so months ago.

@poldim - Hmm, it's been dead for me for so long I commented it out.  I'll give it another shot and see if things have changed and report back.  Thanks for the input.

Gave it another shot; still the same.  Cannot connect to the account.  Credentials haven't changed since day one and there's nothing else that can be entered as an option so I've gone back to commenting it out.  Not working for me and a number of folks said the same in the HA subreddit about both UPS and FedEx.
It was worth a shot though.

can't connect with fedex either, came to open an issue and found this..., UPS is the only one that works, however usps sounds promixing but you need to install additional components as described, haven't tested it yet @rpitera, have you looked at the required components for usps?
USPS
The usps platform allows one to track deliveries and inbound mail from the US Postal Service (USPS). In addition to having a USPS account, you will need to complete the “Opt-In” process for packages by clicking “Get Started Now” on this page. You must also “Opt-In” to Informed Delivery to see inbound mail.
There is currently support for the following device types within Home Assistant:
Camera
Sensor
Prerequisites
This integration requires that a headless-capable web browser is installed on your system - either PhantomJS or Google Chrome. Preferably use Chrome if your operating system supports it, since PhantomJS is deprecated.
If you are using a Raspberry Pi, you must use PhantomJS.
Hass.io containers are based on Alpine Linux. PhantomJS is not available for Alpine Linux. Therefore it is currently not possible to use this integration on Hass.io.

UPS still not working for me here, but I'll try again once I update to 0.96.x
I tried the USPS component back when I was on the Pi with a VENV and got the dependencies installed but never got it to work.  Now that I am on hassio on a VM, it's not an option.
I even tried a recent custom component for just tracking deliveries from USPS, UPS and others and while I got that installed and the sensor was in my entities list, it never caught any of the emails so that was another try.   At this point I've kind of given up.  It's a shame because at least the UPS and FedEx components worked for me at one time.

UPS just stopped working for me
On Fri, Jul 19, 2019 at 4:53 AM rpitera<EMAIL_ADDRESS>wrote:

UPS still not working for me here, but I'll try again once I update to
0.96.x
I tried the USPS component back when I was on the Pi with a VENV and got
the dependencies installed but never got it to work. Now that I am on
hassio on a VM, it's not an option.
I even tried a recent custom component for just tracking deliveries from
USPS, UPS and others and while I got that installed and the sensor was in
my entities list, it never caught any of the emails so that was another
try. At this point I've kind of given up. It's a shame because at least the
UPS and FedEx components worked for me at one time.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/home-assistant/home-assistant/issues/24332?email_source=notifications&email_token=AEAWSUNW6U5ZXVLUKYDPLLLQAGTKBA5CNFSM4HUYAIFKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2LNDYI#issuecomment-513200609,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEAWSUOXITPLKYUMUPMCAWTQAGTKBANCNFSM4HUYAIFA
.

UPS also isn't working for me

UPS working for me

For you guys giving status please include your HA version and environment (Pi?  VM?  NUC?) so we can narrow down why it's working for some but not for most?  I am running 0.95.6 on a Virtualbox VM Ubuntu instance.

For you guys giving status please include your HA version and environment (Pi? VM? NUC?)

Hassbian (Pi 3b+)
Home Assistant 0.96.5

Also I wonder if theres anything with when the account was created? I created mine fairly recently.

I just did mine today

Also, make sure it's accuratley reporting when there is 1 or more packages. I think mine was showing 0 for a while even though I had packages in transit.

On Aug 6, 2019, at 1:51 PM, Scott Grayban<EMAIL_ADDRESS>wrote:
For you guys giving status please include your HA version and environment (Pi? VM? NUC?)
Hassbian (Pi 3b+)
Home Assistant 0.96.5
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

I will watch mine...

Ah okay yeah mine has been reporting 0 but if you check the ha logs you might see an error saying it can’t connect to ups

You are right. It initially did connect when I was looking at the logs but now it's saying its failing.

Above listed PRs deprecate ups, fedex and usps integrations.


[Feature Request] Show git user name in the "right prompt"

First off. I'm VERY 😃😄😀  with this spaceship-prompt! It's delicious 😋
Is your feature request related to a problem? Please describe.
The problem is that I'm doing pair coding and therefore changing the git username frequently.
**Is your feature request related to new section on prompt? **
I wish to use the existing right side prompt to show the user - just like some use it to display date and time.
Describe the solution you'd like
Would just like to learn how to make an rprompt that shows the git user name.
.../repo/app via node v.12.4.0 via ruby ruby-2.6.3
on branch bug/just-make-it-work
$ add .                                                             [Alice & Bob]

Imagine that it calls git config --global user.name on every prompt "refresh/load" and puts in to the right
Describe alternatives you've considered
Either have it as an option (like shown below)
or
Instruct me how to make a custom option that gets call every time the prompt loads.
Documentation, adoption
SPACESHIP_RPROMPT_ORDER=(
  #time      # Time stamps section
  gituser    # Git user name
)

I found a solution! https://stackoverflow.com/a/57900968/618099
TLDR:
spaceship_git_user() {
  spaceship::is_git || return

  local username

  username="$(git config user.name)"

  if [[ -n $username ]]; then
    spaceship::section \
      "yellow" \
      "$username"
  fi
}

Then, add the custom section into spaceship prompt.
SPACESHIP_RPROMPT_ORDER =(
  # content omitted ...

  git_user

  # content omitted ...
)

One minor suggestion, It's better to quote uninitiated variables or initialize it there. See #420


Can you run crouton from a USB drive?

Apologies for opening a ticket for this, I looked around for a community or forum link or something of the sort but could not find anything.
My question is simple: Can I run crouton from a USB drive?
I'd like to buy a simple cheap chromebook to experiment with, but it only has 16GB of storage, which obviously isn't going to suffice. Nothing an external drive can't help with, but will crouton play nice with that?
Additionally, while I'm here, does anyone have experience running this with 4GB of memory and if so, how well does it work? Do you run into limits fast? Again I intend just to experiment, but long term I hope I could use this as a travel solution.
Thanks!

This wiki topic is pretty basic, but introduces the crouton -p argument, which may be used to install a chroot to a USB drive or SD card.
https://github.com/dnschneid/crouton/wiki/How-To-Install-To-External-Drive


AMBARI-25282 Prevent Auth error for hbck

Forward-port of commit: https://github.com/apache/ambari/commit/7517d032774f87ba398c314342c5adf838b1c96d

Since this already committed to 2.7, it can be directly merged into BIGTOP stack on trunk branch.


[Question] How to get grpc Release v1.62.1 with tar.gz type by using wget command (i.e. not git clone)

Hi all,
Could you please share on how to get grpc release version with tar.gz type by using wget command ?

Thanks in advance.
BR/Kyutak

Hi all,
I got the solution as below:
wget https://github.com/grpc/grpc/archive/refs/tags/v1.62.1.tar.gz
BR/kyutak


Filter by a test name regex pattern still runs test files which don't match resulting in "Test suite failed to run"

🐛 Bug Report
In my jest-cypress-react-babel-webpack project, I'm experiencing a problem that's best shown via a video (the video is using jest-watch-typeahead, but I reproduced this when commenting those plugins out, the video also shows an unrelated issue reported here: https://github.com/rogeliog/jest-watch-select-projects/issues/2).
To Reproduce
Steps to reproduce the behavior:

Install jest
Write two test files with different test titles in each
Add a test name filter that matches only one of them
The non-matching file is still run and fails with the error:

FAIL  src/__tests__/test2.js
  ● Test suite failed to run

    Your test suite must contain at least one test.

      at node_modules/jest/node_modules/jest-cli/build/test_scheduler.js:246:22

Expected behavior
It should not run test files which do not have tests which match the regex.
Link to repl or repo (highly encouraged)
https://github.com/kentcdodds/jest-cypress-react-babel-webpack
Enter the following commands in order:

npm run setup
npm t
t
mount

If a simpler reproduction repo is necessary let me know.
Run npx envinfo --preset jest
Paste the results here:
  System:
    OS: macOS Sierra 10.12.6
    CPU: x64 Intel(R) Core(TM) i7-4980HQ CPU @ 2.80GHz
  Binaries:
    Node: 8.9.4 - ~/.nvm/versions/node/v8.9.4/bin/node
    Yarn: 1.3.2 - /usr/local/bin/yarn
    npm: 6.1.0 - ~/.nvm/versions/node/v8.9.4/bin/npm
  npmPackages:
    jest: ^23.1.0 => 23.2.0

Thanks!

Looks like a duplicate of #6415

Indeed it does :+1: thanks!


⚠ Bofrost.de has degraded performance

In 8f96dd7, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1148 ms

Resolved: Bofrost.de performance has improved in f34b2ea after 6 minutes.


What is the a variant version of BEiTv2 used in ViT-Adapter?

As describled in the paper(Table 4. Comparisons with previous SOTA on COCO val 2017), the pretrain checkpoint from the a variant version of BEiTv2 used in ViT-Adapter can improve the performance, please give some details, thanks!

As describled in the paper(Table 4. Comparisons with previous SOTA on COCO val 2017), the pretrain checkpoint from the a variant version of BEiTv2 used in ViT-Adapter can improve the performance, please give some details, thanks!

The original intention of ViT-CoMer is that it can directly utilize open-source ViT pre-training instead of retraining large-scale pre-training. Therefore, we combined BEiTv2 with other advanced pre-training and also used TTA during testing, both of which improved the performance of the model.


[RFC] Revising ranking objectives.

XGBoost supports different ranking objectives based on LambdaMART, including rank:pairwise, rank:ndcg and rank:map.  The rank:pairwise is unscaled version of ranknet's cost, which means the \delta term in LambdaMART is just set to constant .  Other 2 are extensions of LambdaMART with different measures.  To clarify the ranking model implementation and make room for other objectives, I propose the following changes:
Rename the objective functions
Use lambdamark:extension for existing objectives.  All 3 objectives are pairwise approach as lambdarank/lambdamart is pairwise LTR approach.  The name rank:pairwise rank:ndcg is just confusing.  Also with recent advancement in LTR, there are revised lambdamart algorithms like the one mentioned in https://github.com/dmlc/xgboost/issues/6143 .

rank:pairwise -> lambdamart:constant.
rank:ndcg -> lambdamart:ndcg
rank:map -> lambdamart:map

More features to existing objectives
We should add class balancing to rank:ndcg to combat imbalanced target relevance degree.  Also, truncation should be explicitly specified to rank:ndcg.
Change default evaluation metrics
The default evaluation metric for rank:ndcg should be changed to ndcg instead of the current map.  With the truncation mentioned in above, the default metric should be ndcg@truncation.
Change implementation details
Right now the implementation deviates from standard algorithm described in related literature.  I want to revise the implementation to get the code closer to well known literature.  I have a prototype of rank:ndcg running on CPU, which has better accuracy then existing one even when truncation is set to 1.

@hcho3 @RAMitchell @CodingCat @ShvetsKS


Settings menu UI

Align settings menu based on designs
Check dark, light and mobile
https://www.figma.com/file/fwADI9wqDrRAdlMX8EddCw/Bancor-v3?node-id=5233%3A99585


Request for link to models in paper and correct link for training data

Hi:
Thanks for this multi-function code factory. Having fun with this repo using custom local models. Needed to tweak 'test_generation.py'
Currently readline() working but only reads a single line from P1 and P3 text files as strings  readlines() doesn't work because it returns a list and read() swallows everything.
Any suggestions would be helpful.
Just  a few quick questions.

Do you plan on releasing the models mentioned in your paper currently with placeholders in the 'models' folder? Would appreciate links.

Your posted link for the training data is returning '404' Can this be corrected?
https://drive.google.com/open?id=1wfWNo4p91OPHUSBYJ9Bv-oMNawxv_tAH

Is there a process to convert local text files to  .json for use in the repo?

Cheers

Hi,
I appreciate your interest in our project, however it is not over yet! We had to make this repo public to use it in AWS and Google EC2 instances.
That said, I'm glad you're trying to use it but we cannot guarantee that everything will be working for now. Especially, the model is currently in the training phase, it will be released afterward to put in the 'models' folder.
Concerning the data, the errors in code, the general usability and the documentation, all of this will come later when we clean our project files.
Most test files are quite old, using old versions of the functions and classes. I recommend you only look to the files at root and in src folder.
To produce .json files from a book or a text in general, you can look at "src/json_generation/prepare_data.py", this part should work already :)

Hi again,
I just updated the links to the data and model archives, so you can download them.
However, currently there is no:

trained generative model
generated data from these model
computed metrics

Currently, you will find:

all the raw and preprocessed data files (json) --> DATA_ARCHIVE
BERT_NER_Large weights, for entity recognition --> MODELS_ARCHIVE


update live-common with NFT fixes

fixes of https://github.com/LedgerHQ/ledger-live-common/releases/tag/v21.19.1

reopening when we fix live-common


Create specialized macros for each operator group

Fix mixed type checking for binops that were forcing first argument type as second now the expected type always depends on the operator
Generalize type_check fail tests
New tests for #20

all int comparison operators with bool arguments
all equality operators with (int, bool) and (bool, int) arguments
all logical operators with (int, bool) and (bool, int) arguments

Changed the macro names.

@christianpoveda so I added a ensure_ty macro. It isn't particular beautiful and I had to juggle a bit with the syntax to get to a solution that is easy to use and difficult to misuse. I added a comment to explain the rationality behind the closure.


能不能不使用grunt做工程自动化，使用gulp呢？

能不能不使用grunt做工程自动化，使用gulp呢？

Translation: Can you use gulp instead of grunt for automation?

@xiaoyang2022 Yes! 对

yes,i like gulp,grunt not easy!

gulp is better than grunt to use,yours mean-stack will be use it?

@xiaoyang2022 Currently the project uses both! We have plans to switch over to gulp, but for now, both work.

very good! gulp is very good,grunt don't to use that is more works for develper and it more profile.thanks

@xiaoyang2022 If you have any more questions, feel free to ask, otherwise go ahead and close the issue and Happy Hacking!


Schedule check jobs at flexible intervals (crontab-like)

Considered Python libraries:

https://github.com/agronholm/apscheduler
https://github.com/dbader/schedule
Python built-in sched: https://docs.python.org/3/library/sched.html
https://github.com/celery/celery

See #4th example

pure crontab
https://pypi.org/project/python-crontab/

I went for APScheduler v4, because:

Despite being in a pre-release version as of 2023-07-09, it worked well for me for my tests
It offers great support for asynchronous workflows


Skip an assertion test when built as Release

For the longest time this test failed if the binary was built as release, since C assert is no-op when NDEBUG is defined. Our CI action runs the tests with the Debug build. This just removes a minor annoyance when we try to run ctest with a release build.

lgtm!

@lukhnos Sounds good to me and I guess you will soon also change that in the upstream repo?

Yes. Thanks!


Nested locate bug with assert

Commit: a253b47e
This code works and produces a "2":
#let c = counter("foo")

#let foo() = {
  locate(loc => {
    let x = c.at(loc).at(0)
    // assert(x > 1)
    str(x)
  })
}

#let baz() = {
  locate(loc => {
    foo()
  })
}

c.update(2)
#baz()
c.update(1)

If you uncomment the assert in line 6, typst produces the following error:
error: assertion failed
  ┌─ bug.typ:6:10
  │
6 │     assert(x > 1)
  │           ^^^^^^^

Adding an assert seems to change the location where the inner locate is called to after c.update(1)

Weirdly enough, replacing the assert(x > 1) with something trivial like assert(x >= x) still produces 2 as content.
This does not make sense to me. Is the variable a reference to the counter value? It seems like the assert is evaluated not inside the locate call but somwhere else and at that point x evaluates to 1, even though in the line below it evaluates to2
This can be  demonstrated by:
 assert(x > 1, message: str(x))
error: assertion failed: 1
  ┌─ bug.typ:6:10
  │
6 │     assert(x > 1, message: str(x))
  │           ^^^^^^^^^^^^^^^^^^^^^^^^

States variables seem to be lazily evaluated:
#let x = 0
#let y = x
#(x = 1)

#y

produces 0, whereas:
#let x = state("x", 0)
#let y = x.display()
#(x.update(1))

#y

produces 1

State variables are resolved over multiple layout passes. Adding an assert that fails after the first pass can produce different results because then no further passes will happen.

I don't understand why this works then (the outer location is passed to the inner function):
#let c = counter("foo")

#let foo(b) = {
  locate(loc => {
    let x = c.at(b).at(0)
    assert(x > 1)
  })
}

#let baz() = {
  locate(loc => { foo(loc) })
}

#c.update(2)
#baz()
#c.update(1)

it just seems like the inner locate is inserted at the end of the document,  which was unexpected for me.
And is this a bug, or intended?

Because the outer location is resolved after the first pass whereas the inner one is still unknown after the first pass (Because it is only generated once the outer one is known.)

Delayed errors (catches errors in non-final layout passes) have been implemented a while ago, so this should be fixed.


Unexpected token, expected "," when using defineProps with computed (escaped) object key

Related plugins

[X] plugin-vue

[ ] plugin-vue-jsx

Describe the bug
Hi everyone. The following code in a Vue SFC raises a parsing error:
interface MyProps { // same with type alias
  bool?: boolean;
  msg?: string;
  'onUpdate:modelValue'?: (val: string) => void;
}

defineProps<MyProps>();

I'm opening this issue here because I've tested this behavior in the Vue SFC Playground without problems, hence I think the error occurs on the vite side. It seems that, at some point, vite-plugin-vue can't parse interfaces (or type aliases) containing computed (or escaped) object properties.
The error can be fixed by commenting the 'onUpdate:modelValue' prop or changing it to not be computed anymore (eg. onUpdateModelValue.
I've encountered this issue by using the new defineProps() to wrap a third party component (Quasar's QTable by extending its props (QTableProps), which contains some computed property names like onUpdate:pagination, onUpdate:selected and such.
I've reviewed Vue 3.3's announcement blog post and https://github.com/vuejs/core/pull/8083 but I believe this case should not fall in the "complex types" category. Maybe this quote by Evan is the key to understand the problem:

Do note that complex types support is AST-based (not using TS itself) and therefore not 100% comprehensive.

Additional info: i'm encountering this error with both vite 2.9.15 (locally) and vite 4.3.9 (on stackblitz).
Reproduction
https://stackblitz.com/edit/vitejs-vite-sqq4aq?file=package.json,src%2Fcomponents%2FHelloWorld.vue&terminal=dev
Steps to reproduce
pnpm install && pnpm run dev
System Info
System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 0 Bytes / 0 Bytes
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 16.14.2 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 7.17.0 - /usr/local/bin/npm
  npmPackages:
    @vitejs/plugin-vue: ^4.1.0 => 4.1.0
    vite: ^4.3.9 => 4.3.9

Used Package Manager
pnpm
Logs

Click to expand!
Unexpected token, expected "," (16:12)
16:28:50 [vite] Internal server error: Unexpected token, expected "," (16:12)
  Plugin: vite:vue
  File: /home/projects/vitejs-vite-sqq4aq/src/components/HelloWorld.vue:16:12
  20 |

  21 |        Edit
  22 |        components/HelloWorld.vue to test HMR
     |                ^
  23 |

  24 |

      at instantiate (file:///home/projects/vitejs-vite-sqq4aq/node_modules/.pnpm/@babel+parser@7.22.4/node_modules/@babel/parser/lib/index.js:63:32)
      at constructor (file:///home/projects/vitejs-vite-sqq4aq/node_modules/.pnpm/@babel+parser@7.22.4/node_modules/@babel/parser/lib/index.js:358:12)
      at TypeScriptParserMixin.raise (file:///home/projects/vitejs-vite-sqq4aq/node_modules/.pnpm/@babel+parser@7.22.4/node_modules/@babel/parser/lib/index.js:3255:19)
      at TypeScriptParserMixin.unexpected (file:///home/projects/vitejs-vite-sqq4aq/node_modules/.pnpm/@babel+parser@7.22.4/node_modules/@babel/parser/lib/index.js:3285:16)
      at TypeScriptParserMixin.expect (file:///home/projects/vitejs-vite-sqq4aq/node_modules/.pnpm/@babel+parser@7.22.4/node_modules/@babel/parser/lib/index.js:3627:28)
      at TypeScriptParserMixin.parseObjectLike (file:///home/projects/vitejs-vite-sqq4aq/node_modules/.pnpm/@babel+parser@7.22.4/node_modules/@babel/parser/lib/index.js:11662:14)
      at TypeScriptParserMixin.parseExprAtom (file:///home/projects/vitejs-vite-sqq4aq/node_modules/.pnpm/@babel+parser@7.22.4/node_modules/@babel/parser/lib/index.js:11182:23)
      at TypeScriptParserMixin.parseExprSubscripts (file:///home/projects/vitejs-vite-sqq4aq/node_modules/.pnpm/@babel+parser@7.22.4/node_modules/@babel/parser/lib/index.js:10890:23)
      at TypeScriptParserMixin.parseUpdate (file:///home/projects/vitejs-vite-sqq4aq/node_modules/.pnpm/@babel+parser@7.22.4/node_modules/@babel/parser/lib/index.js:10873:21)
      at TypeScriptParserMixin.parseMaybeUnary (file:///home/projects/vitejs-vite-sqq4aq/node_modules/.pnpm/@babel+parser@7.22.4/node_modules/@babel/parser/lib/index.js:10849:23)

Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

I guess this is a bug in Vue as it reproduces with Vue SFC Playground.


Fix subscription ID of armRPPrivateLinkServices client

Which issue this PR addresses:

Fixes N/A
What this PR does / why we need it:

This PR fixes InvalidAuthenticationTokenTenant in Prod.
The old client used _env.SubscriptionID() (see L262 and L264 on the left pane in https://github.com/Azure/ARO-RP/pull/3616/files#diff-f4933755bd63c9e160a2068e8ccb4048e8df1b43f7f4544dcbc7ae2650a07478), but the new client uses r.SubscriptionID, which caused the subscription mismatch and caused the InvalidAuthenticationTokenTenant error.
This PR fixes the subscription for armRPPrivateLinkServices and armFPPrivateEndpoints.
Test plan for issue:

e2e, e2e in prod
Is there any documentation that needs to be updated for this PR?

N/A
How do you know this will function as expected in production?

Cluster creation in prod

/azp run


Add files via upload

DORK SEARCH SOME (HACKER) FORUMS
i am doing this assignment with my partner , her student ID M11109804 @DitsayaChueasakon
Checks

[ ] Your YAML file has required fields as listed in Specs
[ ] All checks have passed yaml-lint passed
[ ] You agree to contribute your work under MIT license

I'm a partner of this assignment @gilvylanggawan11


[AzureRG Deploy release] override parameters parsing bug fix

Hi @aydey, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

It looks like you're a Microsoft contributor (Ayantika Dey). If you're full-time, we DON'T require a Contribution License Agreement. If you are a vendor, please DO sign the electronic Contribution License Agreement. It will take 2 minutes and there's no faxing! https://cla.microsoft.com.

TTYL, MSBOT;


Mass update to Devices

A question I asked in the Groups but I didn't get an answer.  We need this because all our GnG ChromeBooks will be used by staff at home during this period where virtually all staff are working at home.  Is there a way to update the return date for all devices?  Obviously there's more than one way of allowing extended loans - does anyone have a view on this?

I think Joe followed up regarding this. I'll close. If you need further assistance, don't hesitate to let us know!


json: cannot unmarshal number into Go struct field Pipeline.coverage of type string

Hello, calling function pipeline.go/GetPipeline caused this error to come up (started recently, and strangely not all pipelines are causing this error): json: cannot unmarshal number into Go struct field Pipeline.coverage of type string
I don't see any pipeline patterns (MR, tag, branch, main pipelines etc.) which would help identify where the issue is coming from, but it seems like more and more responses come back with that error (we're processing all pipelines in multiple projects).
Current Gitlab version: 14.6.0-pre
Thanks
Vlad

Update: Coverage type "string" should be changed to "float32".  This was tested locally by replacing struct Pipeline (included several other dependencies, overridden GetPipeline function etc.)

Please see #1307, this seems to be a regression in GitLab so for now I'm not going to change it in this package.


[Feature]: logger access and control

Is there an existing issue already for this feature request/idea?

[X] I have searched for an existing issue, and could not find anything. I believe this is a new feature request to be evaluated.

What problem is this feature going to solve? Why should it be added?
The plugin helper machinery hides the zap.Logger and all means of configuring it: It doesn't hook the Zap CLI options nor any env-vars. No means to control log format, json logging etc is provided.
There's only the plugin --debug flag.
Describe the solution you'd like
It would be helpful to be able to provide a plugin startup hook that can configure the logger etc, overriding the defaults here.
Otherwise each entrypoint into the plugin implementation has to reconfigure logging, and still can't influence the logging done by the helper itself.
Describe alternatives you've considered
I didn't really find any, since there doesn't seem to be a sensible means of unwrapping the logr.Logger to obtain the underlying zap root logger.
Additional context
No response
Are you willing to actively contribute to this feature?
No
Code of Conduct

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

I fixed this in https://github.com/cloudnative-pg/cnpg-i-machinery/pull/31 . It's now possible to do this by injecting a logger into the Cobra command's initial Context, using something like this in cmd/plugin/plugin.go's NewCmd():
        // Replace the pluginhelper's logging implementation with one that
        // injects a stack on panic.
        ctx := cmd.Context()
        if ctx == nil {
                ctx = context.Background()
        }
        cmd.SetContext(newLogContext(ctx))

where newLogContext might be something like
func newLogContext(ctx context.Context) context.Context {
        zc := zap.NewProductionConfig()
        zc.Level = zap.NewAtomicLevelAt(zap.DebugLevel)
        if viper.GetBool("debug") {
                zc.Development = true
                zc.Encoding = "console"
                zc.DisableStacktrace = false
        } else {
                zc.Level.SetLevel(zap.InfoLevel)
                zc.Encoding = "json"
        }
        z, err := zc.Build()
        if err != nil {
                panic(fmt.Sprintf("while building logger: %v", err))
        }
        r := zapr.NewLogger(z)
        r = r.WithName("plugin")
        return logging.IntoContext(ctx, r)
}


Bug(scope): nx monorepo translate function isn't working

Is there an existing issue for this?

[X] I have searched the existing issues

Which Transloco package(s) are the source of the bug?
Transloco
Is this a regression?
No
Current behavior
I'm using NX monorepo, with 3 angular apps ( 1 master and 2 childs). In the master app all is working fine.
For the child app, the translate function is not translating at all in the ts file. While it is working correctly in the template (html).
In the console of my web browser I can see that it takes language json files from my master app. The language json files of my child app are handled by webpack.
Expected behavior
I have to be able to use function translate inside ts file of the components which are in my child app.
Please provide a link to a minimal reproduction of the bug
NA
Transloco Config
my transloco-root.module.ts:
export const loader = ['en', 'fr'].reduce((acc, lang) => {
  acc[lang] = () => import(`../assets/i18n/${lang}.json`);
  return acc;
}, {});

@NgModule({
  exports: [TranslocoModule],
  providers: [
    {
      provide: TRANSLOCO_CONFIG,
      useValue: translocoConfig({
        availableLangs: ['fr', 'en'],
        defaultLang: 'fr',
        // Remove this option if your application doesn't support changing language in runtime.
        reRenderOnLangChange: true,
        prodMode: environment.production as unknown as boolean
      })
    },
    { provide: TRANSLOCO_SCOPE, useValue: { scope: 'dashboard', loader } }
  ]
})
export class TranslocoRootModule {
}

Please provide the environment you discovered this bug in
Transloco: 4.2.2
Angular: 15.1.5
Node: 18.12.1
Package Manager: 8.19.2
OS: ubuntu

Browser
Chrome v110.0.5481.96

Additional context
No response
I would like to make a pull request for this bug
No

@Choupa-web Please provide a reproduction link

Probably because your translations are not fully loaded yet?
I noticed that your are using scoped translations (per module) this an async operation by nature, and the translate() function is sync. So, it's up to you to ensure that the module scoped translations are ready before using the translate() function.

@Choupa-web Closing this for now as to @guzmanoj comment + no reproduction link which is mandatory.
Feel free to re-open the issue if it makes sense, only reopen it with a valid reproduction.


Stop working on Safari iOS 12

Describe the bug
This plugin stop working on Safari iOS 12 since v2.2.0 update.
Seems an infinite loop.
Was this intencional? Should it be added to the release notes?
To Reproduce

Go to tom-select.js.org with Safari 12 (tested on iPad Air 2 with iOS 12.4)

https://user-images.githubusercontent.com/11599942/193596322-dba6be73-efb1-4a2c-865b-6c6190f23599.mov
Additional context
Add any other context about the problem here.

OS: iOS
Browser: Safari
Version: 12
Device: iPad Air 2

There should be more information in the dev tools. Take a look at the "console" tab and "network" tab to get more info.

Nothing at the console :/
In this video you can see how the assets are loaded 4 times before Safari stops with "webpage crashed".
https://user-images.githubusercontent.com/11599942/193609140-47709f89-b892-4b73-bd6d-f4559c433183.mov

Was this intencional?

Definitely not.
I'm not seeing the problem when I try in Safari 12.

I'am testing in iOS 12.4, Safari 12.1.2, Webkit 607.1.40.

The equivalent in macOS should be one of this versions:

Is the version you tested? If it's working maybe it's a bug in the iOS version…

Yeah, I tested on 12.1.2 and I can't think of anything in the code that would cause the browser refresh

Could you try on iOS 12.4?
In this video it's working in iOS 13.7, but not in iOS 12.4. I testing in Simulators but it also crash in real devices.
https://user-images.githubusercontent.com/11599942/193760357-f64ea195-37f8-46a6-abac-c52694b6afd6.mov

I believe I've found and fixed the problem. Let me know if you still it.

@oyejorge it's fixed! Thanks!


Deprecation notice

ember-cli-eslint seems to do this by default now so it might make sense to deprecate this project to avoid confusion.

Awesome! The package has been deprecated.


Logging in with signInWithOTP() and using withPageAuth in Next SSR reroutes me to the unauthed route

Bug report
Describe the bug
When I log in with signInWithOTP(), I still get rerouted back to the unauthenticated route despite being authenticated from opening the magic login link. I can access pages just fine if I change the url my self.
It seems like the the withPageAuth is checking before auth data is cached
To Reproduce
Heres my code for ssr authentication
export const getServerSideProps: GetServerSideProps = withPageAuth({
  redirectTo: "/login",
  async getServerSideProps(ctx, supabase) {
    const {
      data: { user },
    } = await supabase.auth.getUser();
    const res = await supabase.rpc("user_has_any_role", {
      user_id_: user?.id,
    });

    return {
      redirect: !!res.data ? undefined : { destination: "/unauthorized" },
      props: {},
    };
  },
});

Heres the login code
const handleLogin = async (email) => {
    try {
      setLoading(true);
      const { error } = await supabase.auth.signInWithOtp({
        email,
        options: { emailRedirectTo: "/" },
      });
      if (error) throw error;
      alert("Check your email for the login link!");
    } catch (error) {
      alert(error.error_description || error.message);
    } finally {
      setLoading(false);
    }
  };

Expected behavior
Should be authenticated and let me into the emailRedirectTo page
System information
Windows
Chrome
"@supabase/supabase-js": "2.0.0-rc.10"

This is impacting the newer syntax as well, where the helpers are removed and we're meant to build it up ourselves.  I'm wondering if we need to look for a token param and let it pass through, but that seems not great.
Here's an example I've got, it's mostly just copied out of the Next README.
import { createMiddlewareSupabaseClient } from "@supabase/auth-helpers-nextjs";
import { NextResponse } from "next/server";
import type { NextRequest } from "next/server";

export async function middleware(req: NextRequest) {
  // We need to create a response and hand it to the supabase client to be able to modify the response headers.
  const res = NextResponse.next();
  // Create authenticated Supabase Client.
  const supabase = createMiddlewareSupabaseClient({ req, res });
  // Check if we have a session
  const {
    data: { session },
  } = await supabase.auth.getSession();

  // Check auth condition
  if (session) {
    // Authentication successful, forward request to protected route.
    return res;
  }

  // Auth condition not met, redirect to home page.
  const redirectUrl = req.nextUrl.clone();
  redirectUrl.pathname = "/login";
  redirectUrl.searchParams.set(`redirectedFrom`, req.url);
  return NextResponse.redirect(redirectUrl);
}

export const config = {
  matcher: ["/authenticated/:path*"],
};

This is due to the server not getting the authenticated cookie before the page loads. The token information is sent over from the client side to the server which requires that you have to land the user on a non-protected page first before redirecting them to the projected page. This will no longer be the case when PKCE lands.


hosts.local permission denied

Everytime I run vagrant up I get the error:
C:/HashiCorp/Vagrant/embedded/mingw64/lib/ruby/2.3.0/fileutils.rb:1394:in `initialize': Permission
denied @ rb_sysopen - C:/Users/trahloff/.vagrant.d/tmp/hosts.local (Errno::EACCES)

The Vagrantfile wasn't altered in any way.
Visited Links:

Hostmanager Issue
Hostupdater
Permissions

System:

Windows 10
Ruby:  2.3.4
Vagrant: 1.9.6
Vagrant-Hostmanager: 1.8.7

This probably means Vagrant doesn't have access to modify files on host's machine.
You can try to run Vagrant as Administrator or adjust file permissions for %SystemRoot%\system32\drivers\etc.

I tried to run Vagrant as Administrator (CMD and Powershell) and the file permissions are "-a---".
What else could be the problem?

No other ideas, except of file/dirs permissions.
Make sure those dirs/files (%SystemRoot%\system32\drivers\etc, %SystemRoot%\system32\drivers\etc\hosts, C:/Users/trahloff/.vagrant.d/tmp/hosts.local) are writable.
Also what means -a---, "all" something?
Did you try workarounds from the links you listed above? https://github.com/cogitatio/vagrant-hostsupdater/issues/89
The point of vagrant-hostmanager plugin is to modify hosts files, so the entire fleet of Vagrant instances can be accessed by hostname like web, db, chatops instead of IP.

I sadly couldn't figure out how to run it on the Windows host but managed to get is to work on a Linux Host.
Hostname association still fails, though. I can't access the services with "web", "chatops" but when I try <IP_ADDRESS> I actually get the NGINX welcome page.
Somehow my I can't access the StackStorm Web GUI (neither https://www.chatops, nor <IP_ADDRESS> works).
My vagrant up output:
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 31999
DEBUG subprocess: Exit status: 0
 INFO warden: Calling OUT action: #<VagrantPlugins::ProviderVirtualBox::Action::IsRunning:0x000000
03766a08>
DEBUG updater: init updater
 INFO runner: Preparing hooks for middleware sequence...
 INFO runner: 2 hooks defined.
 INFO runner: Running action: machine_action_up #<Vagrant::Action::Warden:0x000000061a2790>
 INFO warden: Calling IN action: #<Proc:0x000000069ab928@C:/HashiCorp/Vagrant/embedded/gems/gems/v
agrant-1.9.6/lib/vagrant/action/warden.rb:94 (lambda)>
 INFO warden: Calling IN action: #<VagrantPlugins::ProviderVirtualBox::Action::CheckAccessible:0x0
00000061a2718>
 INFO subprocess: Starting process: ["C:/Program Files/Oracle/VirtualBox/VBoxManage.exe", "showvmi
nfo", "44e62452-a2ea-47fe-8a2f-25a7da3c9bab", "--machinereadable"]
 INFO subprocess: Command not in installer, restoring original environment...
 Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
 INFO warden: Calling IN action: #<Vagrant::Action::Builtin::Provision:0x000000061a26f0>
 INFO provision: Checking provisioner sentinel file...
 INFO provision: Sentinel found! Not provisioning.
DEBUG updater: init updater
 INFO warden: Calling IN action: #<Vagrant::Action::Builtin::ConfigValidate:0x00000005a1ede8>
 INFO warden: Calling IN action: #<VagrantPlugins::HostManager::Action::UpdateAll:0x00000005a1edc0
>
 INFO warden: Calling IN action: #<Proc:0x0000000619b148@C:/HashiCorp/Vagrant/embedded/gems/gems/v
agrant-1.9.6/lib/vagrant/action/warden.rb:94 (lambda)>
 INFO warden: Calling IN action: #<Proc:0x00000003f27760@C:/HashiCorp/Vagrant/embedded/gems/gems/v
agrant-1.9.6/lib/vagrant/action/warden.rb:94 (lambda)>
 INFO warden: Calling IN action: #<Proc:0x000000053b0b00@C:/HashiCorp/Vagrant/embedded/gems/gems/v
agrant-1.9.6/lib/vagrant/action/warden.rb:94 (lambda)>
 INFO warden: Calling OUT action: #<Proc:0x000000053b0b00@C:/HashiCorp/Vagrant/embedded/gems/gems/
vagrant-1.9.6/lib/vagrant/action/warden.rb:94 (lambda)>
 INFO warden: Calling OUT action: #<Proc:0x00000003f27760@C:/HashiCorp/Vagrant/embedded/gems/gems/
vagrant-1.9.6/lib/vagrant/action/warden.rb:94 (lambda)>
 INFO warden: Calling OUT action: #<Proc:0x0000000619b148@C:/HashiCorp/Vagrant/embedded/gems/gems/
vagrant-1.9.6/lib/vagrant/action/warden.rb:94 (lambda)>
 INFO warden: Calling OUT action: #<VagrantPlugins::HostManager::Action::UpdateAll:0x00000005a1edc
0>
 INFO warden: Calling OUT action: #<Vagrant::Action::Builtin::ConfigValidate:0x00000005a1ede8>
 INFO interface: info: Machine already provisioned. Run `vagrant provision` or use the `--provisio
n`
flag to force provisioning. Provisioners marked to run always will still run.
 INFO interface: info: ==> chatops: Machine already provisioned. Run `vagrant provision` or use th
e `--provision`
==> chatops: flag to force provisioning. Provisioners marked to run always will still run.
==> chatops: Machine already provisioned. Run `vagrant provision` or use the `--provision`
==> chatops: flag to force provisioning. Provisioners marked to run always will still run.

 INFO runner: 1 hooks defined.
 INFO runner: Running action: environment_unload #<Vagrant::Action::Builder:0x0000000672b1a8>

Sorry to hear that.
The only thing I can help with, - will try to reproduce later with Vagrant: 1.9.6 and Vagrant-Hostmanager: 1.8.7 you mentioned before.

Thanks a lot! Will keep you posted if I somehow manage to fix it

Were you able to reproduce the problem? I think it might be the case that the st2 web instance rejects the requests because it is non-https

I tried with Vagrant 1.9.1 and couldn't reproduce the issue.
Hadn't any chance yet to try with Vagrant 1.9.6.

Ok, right now I'm deploying on a a third machine (debian) with Vagrant 1.9.6 and can access the NGINX slaves but get a HTTP301 when curling the www.chatops endpoint. I'm seriously confused right by the variety of errors I produced throughout the different systems.

don't use the plugin host updater.

vagrant plugin list
vagrant plugin uninstall

Make sure your user without elevating privileges have access to read
write to:
C:/Windows/system32/drivers/etc/hosts


set min-height for form-control textarea

set min-height for .form-control textarea

prevent user from shrink textarea
set minimum height equals default input height

before
after

📷 Chrome 75 / Mac OS X 10.14.6

To fix also #28901, is it better add min-height to .form-control and remove the specific heights?

@ysds, that would reintroduce https://github.com/twbs/bootstrap/issues/18842, unless https://github.com/twbs/bootstrap/pull/28917 is merged.

@m5o Would you add the min-height to .form-control and form-select directory and remove the specific height from those? Also need to modify the sizing options and the combinations with .input-groups.

@ysds done, hopefully as you requested.
🤔 I don't know if, for consistency, it would make sense to set min-height also to .form-file

.form-file use position: absolute, so would have to use height.

umm, confirmed

@MartijnCuppens Can you re-review, please?

Are we sure about backporting this BTW?

#18842 still seemed to be an issue. I've pushed a working fix (219e1c68ce6405778bcaf865841cc89f3d80b7c6) and also committed a fix for the input groups.

@MartijnCuppens: this doesn't apply clean on v4-dev-xmr. Can you backport it manually please?

I'm afraid we can't backport this easily since .form-controls can be selects too in v4. To make this work we'll need to rewrite quite a lot and this might introduce breaking changes.


Oanda Market Hours for EURUSD should be UTC

There is one market hours rule for all Oanda Forex (America/New York), however, the EURUSD pair is returned with a UTC timestamp, causing all ticks to be ignored in FrontierAwareEnumerator. I imagine this will also be the case for any forex pair not denominated in USD.

The logic makes sense in backtests to prevent look ahead bias. I'm not sure this is as essential in live mode. It would be useful to have a warning that data is being dropped, so I have a version running with this:

            if (underlyingCurrent != null && underlyingCurrent.Symbol.ID.Market != "empty")
            {
                _needsMoveNext = true;
                _current = underlyingCurrent;
                //tolerate 90 second timeslip between local and data. Otherwise warn.
                if (underlyingCurrent.EndTime > localFrontier.AddSeconds(90))
                {
                    Logging.Log.Error("Data timestamp was later than local. Check the markets hours: " + underlyingCurrent.Symbol.ToString());
                }
            }
            else
            {
                _current = null;
                _needsMoveNext = underlyingCurrent == null;
            }

Hey @jameschch; we distinguish between data and exchange timezone. The backtest and live streams from them are in UTC, but most people work on EST for FX (we convert it to EST). Are you seeing backtest or live streaming data in EST?
"Forex-oanda-[*]": {
      "dataTimeZone": "UTC",
      "exchangeTimeZone": "America/New_York",

I'm seeing raw tick data on live in UTC. I have only noticed this so far on EURUSD. If I change the exchangeTimeZone to UTC, the ticks are passed through to the algorithm via event handlers as normal.

Beyond that, I have also added a new rule for this pair:

	"Forex-oanda-EURUSD": {
            "dataTimeZone": "UTC",
            "exchangeTimeZone": "UTC",
            "monday": [
                {
                    "start": "00:00:00",
                    "end": "1.00:00:00",
                    "state": "market"
                }
            ],
            "tuesday": [
                {
                    "start": "00:00:00",
                    "end": "1.00:00:00",
                    "state": "market"
                }
            ],
            "wednesday": [
                {
                    "start": "00:00:00",
                    "end": "1.00:00:00",
                    "state": "market"
                }
            ],
            "thursday": [
                {
                    "start": "00:00:00",
                    "end": "1.00:00:00",
                    "state": "market"
                }
            ],
            "friday": [
                {
                    "start": "00:00:00",
                    "end": "1.00:00:00",
                    "state": "market"
                }
            ],
            "saturday": [ ],
            "sunday": [ ],
            "holidays": [ ]
        },

However, I've not tested how many other pairs are affected. I'm willing to accept this is an issue with just this pair on just my account, but am not able to verify this.

Interesting. Above *"we convert it to EST" - I mean we convert it to AlgorithmTimeZone which is EST for most people. Exchange timezone is the time zone for the market open and close hours which is correct;
      "exchangeTimeZone": "America/New_York",
      "sunday": [
        {
          "start": "17:00:00",
          "end": "1.00:00:00",
          "state": "market"
        }
      ],
     ....
           "friday": [
        {
          "start": "00:00:00",
          "end": "17:00:00",
          "state": "market"
        }
      ],

i.e. Oanda's market hours (https://oanda.secure.force.com/AnswersSupport?language=en_US&urlName=Hours-of-Operation-1436196464451) are roughly 5pm Friday -> 5pm Sunday.
Potentially you're seeing a bug somewhere else as a by product of your local timezone? What timezone are you locally working in?

Have recreated this on a windows desktop on BST as well as a linux datacentre in NY. This was my initial suspicion: it must be the local timezone, but don't see why just this one pair is affected. I'm not explicitly setting a timezone in the algorithm, but did try this earlier when trying to diagnose the problem.
I don't see the date being converted between the raw tick with a Zulu timestamp and the check in the FrontierAwareEnumerator comparing UTC to localFrontier.
Maybe this is only for accounts registered in Europe.

Hi @jameschch,
the time zone issue you were experiencing should be fixed by this PR (merged today): https://github.com/QuantConnect/Lean/pull/807
When you have time, can you please check if the issue is resolved, so we can close it ?

Excellent. Will take a look as soon as I can.
On 20 March 2017 20:38:47 GMT+00:00, Stefano Raggi<EMAIL_ADDRESS>wrote:
Hi @jameschchhttps://github.com/jameschch,
the time zone issue you were experiencing should be fixed by this PR (merged today): #807https://github.com/QuantConnect/Lean/pull/807
When you have time, can you please check if the issue is resolved, so we can close it ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/QuantConnect/Lean/issues/757#issuecomment-287890242, or mute the threadhttps://github.com/notifications/unsubscribe-auth/APvtWFQCPti9SO-7EsaiLe-C3o7dP7I1ks5rnuPXgaJpZM4MGII_.

Thanks for looking into this, I can see the ticks feed through on EURUSD with a utc timestamp using the current build.

Oanda ticks come in from the Oanda REST API as UTC, but now should always be converted by OandaBrokerage DataQueueHandler to the configured ExchangeTimeZone:
https://github.com/QuantConnect/Lean/blob/master/Brokerages/Oanda/OandaBrokerage.DataQueueHandler.cs#L246
The default value for all Forex symbols in the current market-hours-database is America/NewYork:
"Forex-oanda-[*]": {
      "dataTimeZone": "UTC",
      "exchangeTimeZone": "America/New_York",

Are you still using the market-hours rule for EURUSD you posted above ?

I'm testing with the current master build including config files. When I say ticks are coming through as UTC, I mean in the FrontierAwareEnumerator (which had the switch causing the previous error). In the algorithm the time is converted to NY as expected.


Cannot use any icons. Everything up-to-date.

Hi! This is probably my inexperience but I have encountered an issue where I am unable to use any of the icons.
Here is my Cargo.toml file:
[package]
name = "kony-web"
version = "0.1.0"
edition = "2021"

[dependencies]
yew = "0.21"
web-sys = "0.3"
yew-router = "0.18"
yew_icons = {version = "0.8", features = ["BOOTSTRAP_DISCORD"]}

My navbar.rs:
use yew_icons::{Icon, IconId};
...some code
 html! {

            {title_home}

                {home_nav}
                {discord_nav}

                <Icon icon_id={IconId::BOOTSTRAP_DISCORD}/> // <-------- Error here

    }

Error in terminal:
2024-08-13T11:57:07.324305Z ERROR ❌ error
error from build pipeline

Caused by:
    0: error getting cargo metadata
    1: `cargo metadata` exited with an error:     Updating crates.io index
       error: failed to select a version for `yew_icons`.
           ... required by package `kony-web v0.1.0 (/home/kony/Documents/kony_clowning_2/tailwind-yew)`
       versions that meet the requirements `^0.8` (locked to 0.8.0) are: 0.8.0

       the package `kony-web` depends on `yew_icons`, with features: `BOOTSTRAP_DISCORD` but `yew_icons` does not have these features.

       failed to select a version for `yew_icons` which could resolve this conflict

Notes:

I dont have any more errors
Downgrading yew_icons doesnt help.

I would appreciate any help. Thanks in advance and I appologise if I am making some silly mistake

Found a solution! Had to change "BOOTSTRAP_DISCORD" => "BootstrapDiscord". Please consider changing all names in the gallery to match this format that actually works. I find this quite misleading and poorly executed.

Thanks for reporting this. I am changing to UPPER_SNAKE_CASE on the [constants_not_enum branch](https://github.com/finnbear/yew_icons/tree/constants_not_enum). The GitHub workflow was misconfigured to deploy the GitHub pages gallery site from any commit, including on a pull request branch. I'm attempting to reconfigure it to only deploy the gallery from commits to main.


HDDS-11373. Log for EC reconstruction command lists the missing indexes as ASCII control characters

What changes were proposed in this pull request?
Logs for EC reconstruction command lists the missing indexes as ASCII control characters like ^A ^B.
Fix by restoring Arrays.toString in EC reconstruction command's toString().
https://issues.apache.org/jira/browse/HDDS-11373
How was this patch tested?
Added assertion in unit test.
CI:
https://github.com/adoroszlai/ozone/actions/runs/10574613444

Thanks @sodonnel for the review.


[AutoPR recoveryservicesbackup/resource-manager] Adding non mandatory fields in ProtectedItem and AzureVmWorkloadProte…

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/6818

(message created by the CI based on PR content)

This PR has been merged into https://github.com/Azure/azure-sdk-for-python/pull/6799


Agm-cluster for npm install @agm/core

Agm-cluster for npm install @agm/core
Hi! Then you planning add agm-cluster for @agm/core ?
Thank You !!!!!

When it's done...


FOOTBALL INTRODUCTORY SESSION

Session Name
FOOTBALL INTRODUCTORY SESSION
Organised by SUTD Football EXCO
Abstract
A brief introduction to the regular training format and a bonding session enabling the newcomers to get to know everyone from the club.

What to bring: Sports shoes, sports attire, a water bottle, and yourself!
Session details
The session will take place on 21st and 23rd September 2021, from 8 pm to 10 pm.
The session will be on a first come first serve basis, for the first 40 participants each day.
Speakers/Workshop facilitators
SUTD Football Coach/ SUTD Football Exco
Logistical details
100 cans of 100 plus ($55)
100 pieces of sunshine cream bread ($100)(might be cheaper since we are buying in bulk!)
10 kg of ice ($10)
cooler box to store ice (~$25)
club email address<EMAIL_ADDRESS>form: https://forms.office.com/Pages/ResponsePage.aspx?id=drd2NJDpck-5UGJImDFiPcBLaJRLgXpLrbUxD8zB1C1UQjgxR0NTWkNTMkg2SjZCTDJMOFJIR0lZWS4u

Hi @sutdfootball congratulations on being the first to submit the Github issues!!
Could we check if you need any funding from DiscoverSUTD? I see that there are some refreshments to be catered in the logistical details, we would need a breakdown of the cost as well so that we can help you get approval for funding.

Hi @sutdfootball congratulations on being the first to submit the Github issues!!
Could we check if you need any funding from DiscoverSUTD? I see that there are some refreshments to be catered in the logistical details, we would need a breakdown of the cost as well so that we can help you get approval for funding.
Additionally, will this be on a first come first serve basis in terms of turning up, or in terms of who signs up first on the Microsoft forms? If it's the latter, would probably be good to specify in the forms that participants shouldn't bail or at least inform you beforehand if they back out so that you can ensure they are committed after registration.

Hi @jolow99 thank you!
The breakdown of the cost of the refreshments is as such:

100 cans of 100 plus ($55)
100 pieces of sunshine cream bread ($100)(might be cheaper since we are buying in bulk!)
10 kg of ice ($10)
cooler box to store ice (~$25)

As for the signing up, it will be in terms of who signs up via the Microsoft forms first. We will add in that if participants are unable to make it, they are to inform us beforehand so that others get a chance to come for the intro session.
Thank you! Do let us know if there is any other clarification required.

Hi @sutdfootball ,
May I know the number of facilitators on the day of the event? Would like to know the expected number of attendee including the 40 participants will be on the day itself.
Thank you

@sutdfootball
Note the Registration form you added seems like it's the wrong link ! Do send us the correct link here ya.


No response after firmware updating

After I used the Application WaveTool to update my watch firmware, the screen stopped at the display of a tick icon √, which meant the update was successful, I guess. But there was no more response after that, no matter I pressed two buttons in any way.
Is there anybody who could tell me how to make everything right? Or how to re-install the system when the watch has no response? @anoop-adi @nphilip-adi Thanks!

Hi MaxandYuki,
Try to reset the watch by pressing the bottom navigation button (for 3 seconds).
Regards,
Anoop

Hi Anoop,
Thanks for your reply! I have done that, but it didn't work. Also, I have tried several combinations of pressing buttons. But all cannot turn on/off the watch. Overall, the watch is out of response.
Best
Max

Hi Max,
We can't replicate this issue on our side, so let us know the steps you followed, and info about the watch, Application WaveTool version, and how you were trying to update the firmware with BLE or USB.
Possible solutions: (you can try these options and then respond whether it worked or not for you)
1 - Try to connect the watch with a USB and see if you can see any COM port assigned to the device. (You can check it with ** Device Manager** > ports in windows )
2 - Try NRF connect app from the google play store (https://play.google.com/store/apps/details?id=no.nordicsemi.android.mcp&hl=en_IN&gl=US) and see if you can detect watch BLE on that APP. (NRF Connects scans for BLE devices)
3 - If none of the above methods work, its bootloader must be corrupted, but you can wait for the watch to discharge (It normally takes 24-48 hours for the watch to discharge) and then try to connect it with a USB for charging. (This should reset the watch)
If the watch is still not working, you need to update the bootloader using a Jlink. (I will send you detailed info about it once you confirm all the above 3 steps failed.)
Regards,
Anoop

Hi Anoop,
Thank you for the detailed information provided in the last comment. Here, let me give more clues about the watch, software, and operations I went through.

Watch: From the guidebook, I think the version is ADI VSM Watch IV. The MCU is nRF52840And the ADI technologies used include ADPD4100, ADP5360, etc.
Software: The software I used to perform the hardware update is WaveTool 5.0. After I encountered the problem, I also tried WaveTool 3.5. They both cannot solve it.
Operations: The updating procedure is this: I used a USB cable to link the watch with my PC (with Win10). Then I successfully found the COM port and connected them. Then just followed the instructions in the guidebook to update the firmware. This process was smooth, and the progress bar in WaveTool was finished. However, after I disconnected the watch with PC, the watch screen only showed a tick icon. Whatever I do to it, there is no response. So I tried to totally discharge it (the details about this will be described later).

As for the three steps you aforementioned:

I link the watch with a PC using a USB cable. The WaveTool 5.0 can detect the port where the watch is mounted. But the connection failed.
Since I have no BLE dongle, I didn't try this connection method before. I have just now operated following your instruction in your comment step 2, the watch can be detected by Bluetooth using the APP nRF Connect.
I have tried to connect the watch via USB after the watch was discharged. Here some strange things happened. First, the screen showed some static horizontally organized snow dots, instead of the logo of ADI. Besides this, the WaveTool 5.0 USB connection can detect the port, but the connection result is failed and showed "Chip ID not detected - Please Reset the Device and Connect". And the screen froze at the display of those horizontal snow dots.

Best,
Max

Hi Max,
Since you can get the COM port, so bootloader is fine. It looks like the firmware is not updated.
Few questions:
1 - Are you able to enter the bootloader mode?
2 - Have you tried to re-update the firmware?
Anyway, I think you should be able to access the watch using SDK. Can you try our python SDK and check if you can use the ADXL stream (getting started with python SDK: https://analogdevicesinc.github.io/study-watch-sdk/python/)
Regards,
Anoop

Hi Anoop
Yes, the COM port and the Bluetooth signal are detectable. The problem is that I cannot communicate with the watch, either via the screen and the button or via the USB cable and WaveTool.
To answer your questions:

There is no response when I press buttons in any combinations. Consequently, I cannot enter the bootloader mode by pressing the select+navigate buttons.
Though the WaveTool can detect the COM port, the connection is failed all the time. So, I cannot carry out the update again.

Let me try to communicate with the watch using Python SDK. And the progress will be updated here later. Thank you for the help!
Best
Max

Hi Anoop,
I have tested two example programs in the SDK reference doc, and the results are like the following:

Basic Example using USB

import time
from datetime import datetime
from adi_study_watch import SDK

# callback function to receive adxl data
def callback_data(data):
    sequence_number = data["payload"]["sequence_number"]
    for stream_data in data["payload"]["stream_data"]:
        dt_object = datetime.fromtimestamp(stream_data['timestamp'] / 1000)  # convert timestamp from ms to sec.
        print(f"seq :{sequence_number} timestamp: {dt_object} x,y,z :: ({stream_data['x']}, "
              f"{stream_data['y']}, {stream_data['z']})")

if __name__ == "__main__":
    sdk = SDK("COM4")
    application = sdk.get_adxl_application()
    application.set_callback(callback_data)

    # quickstart adxl stream
    application.start_sensor()
    application.enable_csv_logging("adxl.csv") # logging adxl data to csv file
    application.subscribe_stream()
    time.sleep(10)
    application.unsubscribe_stream()
    application.disable_csv_logging()
    application.stop_sensor()

The result is no output. I find that the function callback_data() is not called. This may be because the program didn't get any data from the watch.

How to log and download adxl stream data

from adi_study_watch import SDK
import time

# SDK setup
sdk = SDK("COM4")
adxl_application = sdk.get_adxl_application()
fs_application = sdk.get_fs_application()

# START LOGGING
adxl_application.start_sensor()
fs_application.subscribe_stream(fs_application.STREAM_ADXL)
fs_application.start_logging()
print(fs_application.get_status()["payload"]["status"])

print("logging...")
time.sleep(20)

# STOP LOGGING
adxl_application.stop_sensor()
fs_application.unsubscribe_stream(fs_application.STREAM_ADXL)
fs_application.stop_logging()
print(fs_application.get_status()["payload"]["status"])

# List all the files available to download.
files = fs_application.ls()
for x in files:
    print(x["payload"]["filename"])

# download data from the watch and save it to a file.
fs_application.download_file(files[0]["payload"]["filename"], download_to_file=True, display_progress=True)

The result of this program is error output, and the output print is like the following:
FSStatus.LOGGING_IN_PROGRESS
logging...
Traceback (most recent call last):

  File "...\temp.py", line 22, in <module>
    fs_application.stop_logging()

  File "...\adi_study_watch\application\fs_application.py", line 256, in stop_logging
    return self._send_packet(packet, FSCommand.STOP_LOGGING_RES)

  File "...\adi_study_watch\application\common_application.py", line 93, in _send_packet
    packet.decode_packet(response_byte)

  File "...\adi_study_watch\core\packets\fs_packets.py", line 447, in decode_packet
    self._packet["payload"]["stop_type"] = FSLogging(data[10:])

  File "...\enum.py", line 339, in __call__
    return cls.__new__(cls, value)

  File "...\enum.py", line 663, in __new__
    raise ve_exc

ValueError: [194] is not a valid FSLogging

From these tests, I feel that (1) the watch system perhaps got stuck, most likely during the loading procedure, so the SDK program cannot read data from the watch. (2) Or the system has not been updated successfully. Maybe something got wrong accidentally during the updating process.
Best
Max

Hi Max,
I have attached two examples; when you run these examples, it will create an SDK.log and SDK1.log, respectively. Can you send those logs?
from adi_study_watch import SDK

sdk = SDK("COM4", logging_filename="SDK1.log")
application = sdk.get_adxl_application()

# quickstart adxl stream
application.start_sensor()
application.subscribe_stream()
application.unsubscribe_stream()
application.stop_sensor()

This code example will place your watch into bootloader mode. If this code works, you can use Wavetool to re-update the firmware.
from adi_study_watch import SDK

sdk = SDK("COM4", logging_filename="SDK.log")
application = sdk.get_pm_application()
application.enter_boot_loader_mode()

Regards,
Anoop

Hi Anoop,
The code blocks have been executed. The logging files are here:

SDK1.log -  adxl reading

2021-09-07 22:26:03 - MainThread - adi_study_watch.sdk - DEBUG - ----- Study Watch SDK Started -----
2021-09-07 22:26:03 - MainThread - adi_study_watch.core.packet_manager - DEBUG - Packet ready : {'header': {'source': [199, 5], 'destination': [197, 0], 'length': [0, 21], 'checksum': [0, 0]}, 'payload': {'command': [66], 'status': [0], 'year': [229, 7], 'month': [9], 'day': [7], 'hour': [22], 'minute': [26], 'second': [3], 'tz_sec': [128, 112, 0, 0]}}
2021-09-07 22:26:03 - MainThread - adi_study_watch.core.packet_manager - INFO - TX :: 0xC7:0x05:0xC5:0x00:0x00:0x15:0x00:0x00:0x42:0x00:0xE5:0x07:0x09:0x07:0x16:0x1A:0x03:0x80:0x70:0x00:0x00
2021-09-07 22:26:03 - process_thread - adi_study_watch.core.packet_manager - INFO - RX::0xC5:0x00:0xC7:0x05:0x00:0x0A:0x00:0x00:0x43:0x00
2021-09-07 22:26:03 - MainThread - adi_study_watch.application.common_application - DEBUG - Packet decoded : {'header': {'source': <Application.PM: ['0xC5', '0x00']>, 'destination': <Application.APP_USB: ['0xC7', '0x05']>, 'length': '0xA', 'checksum': '0x0'}, 'payload': {'command': <PMCommand.SET_DATE_TIME_RES: ['0x43']>, 'status': <CommonStatus.OK: ['0x00']>}}
2021-09-07 22:26:03 - MainThread - adi_study_watch.core.packet_manager - DEBUG - Packet ready : {'header': {'source': [199, 5], 'destination': [193, 2], 'length': [0, 12], 'checksum': [0, 0]}, 'payload': {'command': [4], 'status': [0], 'stream_address': [0, 0]}}
2021-09-07 22:26:03 - MainThread - adi_study_watch.core.packet_manager - INFO - TX :: 0xC7:0x05:0xC1:0x02:0x00:0x0C:0x00:0x00:0x04:0x00:0x00:0x00
2021-09-07 22:26:03 - process_thread - adi_study_watch.core.packet_manager - INFO - RX::0xC1:0x02:0xC7:0x05:0x00:0x0C:0x00:0x00:0x05:0x02:0x00:0x00
2021-09-07 22:26:03 - MainThread - adi_study_watch.application.common_application - DEBUG - Packet decoded : {'header': {'source': <Application.ADXL: ['0xC1', '0x02']>, 'destination': <Application.APP_USB: ['0xC7', '0x05']>, 'length': '0xC', 'checksum': '0x0'}, 'payload': {'command': <CommonCommand.START_SENSOR_RES: ['0x05']>, 'status': <CommonStatus.STREAM_STARTED: ['0x02']>, 'stream_address': <Stream.NULL: ['0x00', '0x00']>}}
2021-09-07 22:26:03 - MainThread - adi_study_watch.core.packet_manager - DEBUG - Packet ready : {'header': {'source': [199, 5], 'destination': [193, 2], 'length': [0, 12], 'checksum': [0, 0]}, 'payload': {'command': [12], 'status': [0], 'stream_address': [2, 194]}}
2021-09-07 22:26:03 - MainThread - adi_study_watch.core.packet_manager - INFO - TX :: 0xC7:0x05:0xC1:0x02:0x00:0x0C:0x00:0x00:0x0C:0x00:0x02:0xC2
2021-09-07 22:26:03 - process_thread - adi_study_watch.core.packet_manager - INFO - RX::0xC1:0x02:0xC7:0x05:0x00:0x0C:0x00:0x00:0x0D:0x09:0x02:0xC2
2021-09-07 22:26:03 - MainThread - adi_study_watch.application.common_application - DEBUG - Packet decoded : {'header': {'source': <Application.ADXL: ['0xC1', '0x02']>, 'destination': <Application.APP_USB: ['0xC7', '0x05']>, 'length': '0xC', 'checksum': '0x0'}, 'payload': {'command': <CommonCommand.SUBSCRIBE_STREAM_RES: ['0x0D']>, 'status': <CommonStatus.SUBSCRIBER_ADDED: ['0x09']>, 'stream_address': <Stream.ADXL: ['0xC2', '0x02']>}}
2021-09-07 22:26:03 - MainThread - adi_study_watch.core.packet_manager - DEBUG - Packet ready : {'header': {'source': [199, 5], 'destination': [193, 2], 'length': [0, 12], 'checksum': [0, 0]}, 'payload': {'command': [14], 'status': [0], 'stream_address': [2, 194]}}
2021-09-07 22:26:03 - MainThread - adi_study_watch.core.packet_manager - INFO - TX :: 0xC7:0x05:0xC1:0x02:0x00:0x0C:0x00:0x00:0x0E:0x00:0x02:0xC2
2021-09-07 22:26:03 - process_thread - adi_study_watch.core.packet_manager - INFO - RX::0xC1:0x02:0xC7:0x05:0x00:0x0C:0x00:0x00:0x0F:0x0A:0x02:0xC2
2021-09-07 22:26:03 - MainThread - adi_study_watch.application.common_application - DEBUG - Packet decoded : {'header': {'source': <Application.ADXL: ['0xC1', '0x02']>, 'destination': <Application.APP_USB: ['0xC7', '0x05']>, 'length': '0xC', 'checksum': '0x0'}, 'payload': {'command': <CommonCommand.UNSUBSCRIBE_STREAM_RES: ['0x0F']>, 'status': <CommonStatus.SUBSCRIBER_REMOVED: ['0x0A']>, 'stream_address': <Stream.ADXL: ['0xC2', '0x02']>}}
2021-09-07 22:26:03 - MainThread - adi_study_watch.core.packet_manager - DEBUG - Packet ready : {'header': {'source': [199, 5], 'destination': [193, 2], 'length': [0, 12], 'checksum': [0, 0]}, 'payload': {'command': [6], 'status': [0], 'stream_address': [0, 0]}}
2021-09-07 22:26:03 - MainThread - adi_study_watch.core.packet_manager - INFO - TX :: 0xC7:0x05:0xC1:0x02:0x00:0x0C:0x00:0x00:0x06:0x00:0x00:0x00
2021-09-07 22:26:03 - process_thread - adi_study_watch.core.packet_manager - INFO - RX::0xC1:0x02:0xC7:0x05:0x00:0x0C:0x00:0x00:0x07:0x03:0x00:0x00
2021-09-07 22:26:03 - MainThread - adi_study_watch.application.common_application - DEBUG - Packet decoded : {'header': {'source': <Application.ADXL: ['0xC1', '0x02']>, 'destination': <Application.APP_USB: ['0xC7', '0x05']>, 'length': '0xC', 'checksum': '0x0'}, 'payload': {'command': <CommonCommand.STOP_SENSOR_RES: ['0x07']>, 'status': <CommonStatus.STREAM_STOPPED: ['0x03']>, 'stream_address': <Stream.NULL: ['0x00', '0x00']>}}

SDK.log - enter bootloader mode

2021-09-07 22:27:06 - MainThread - adi_study_watch.sdk - DEBUG - ----- Study Watch SDK Started -----
2021-09-07 22:27:06 - MainThread - adi_study_watch.core.packet_manager - DEBUG - Packet ready : {'header': {'source': [199, 5], 'destination': [197, 0], 'length': [0, 21], 'checksum': [0, 0]}, 'payload': {'command': [66], 'status': [0], 'year': [229, 7], 'month': [9], 'day': [7], 'hour': [22], 'minute': [27], 'second': [6], 'tz_sec': [128, 112, 0, 0]}}
2021-09-07 22:27:06 - MainThread - adi_study_watch.core.packet_manager - INFO - TX :: 0xC7:0x05:0xC5:0x00:0x00:0x15:0x00:0x00:0x42:0x00:0xE5:0x07:0x09:0x07:0x16:0x1B:0x06:0x80:0x70:0x00:0x00
2021-09-07 22:27:06 - process_thread - adi_study_watch.core.packet_manager - INFO - RX::0xC5:0x00:0xC7:0x05:0x00:0x0A:0x00:0x00:0x43:0x00
2021-09-07 22:27:06 - MainThread - adi_study_watch.application.common_application - DEBUG - Packet decoded : {'header': {'source': <Application.PM: ['0xC5', '0x00']>, 'destination': <Application.APP_USB: ['0xC7', '0x05']>, 'length': '0xA', 'checksum': '0x0'}, 'payload': {'command': <PMCommand.SET_DATE_TIME_RES: ['0x43']>, 'status': <CommonStatus.OK: ['0x00']>}}
2021-09-07 22:27:06 - MainThread - adi_study_watch.core.packet_manager - DEBUG - Packet ready : {'header': {'source': [199, 5], 'destination': [197, 0], 'length': [0, 10], 'checksum': [0, 0]}, 'payload': {'command': [128], 'status': [0]}}
2021-09-07 22:27:06 - MainThread - adi_study_watch.core.packet_manager - INFO - TX :: 0xC7:0x05:0xC5:0x00:0x00:0x0A:0x00:0x00:0x80:0x00

When I tried to make the watch enter the bootloader mode via the SDK, the watch screen had no change. After that, I tried to connect the watch with WaveTool, but the problem remained the same, i.e., the connection failed.
Best
Max

Hi Max,
Try to move your watch in bootloader mode using python SDK.
Then try nrfutil library(https://github.com/NordicSemiconductor/pc-nrfutil). It is a python library that can also flash the watch, an alternative for wavetool firmware upgrade.
Use the following command to upgrade the firmware: (Don't forget to put your watch in bootloader mode using python SDK)
nrfutil dfu serial -pkg ADI_project.zip -p COM4
Regards,
Anoop

Hi Anoop,
That sounds cool! However, I am not sure that the watch can enter the bootloader mode with the help of Python SDK. Did the logging file SDK.log aforementioned before mean the watch had entered the bootloader mode?
Best
Max

Hi Max,
The only way to tell if the watch is in bootloader mode is by checking on the screen, and the LOG file only tells that watch is responding to commands.
You can try nrfutil and let me know your observations.
Regards,
Anoop

Hi Anoop,
The watch screen still doesn't work normally after I run the SDK-based code trying to make it enter bootloader mode. The watch screen shows meaningless snow dots.
Here I tried two ways to execute the re-updating:

The first way is: I use SDK code trying to set the watch to enter the bootloader mode. But the watch screen has no change. Then I run the command line nrfutil dfu serial -pkg ADI_project.zip -p COM5, the progress bar keeps at 0% for a while. Finally, the program ends and prints an error, the key info is: pc_ble_driver_py.exceptions.NordicSemiException: Serial port could not be opened on COM5. Reason: None. I think this may be because the port is occupied by the adi_study_watch SDK.
Based on the result of the first way, the second way is: firstly, I run the adi_study_watch SDK code trying to set the watch into the bootloader mode, which is the same as the first way. Then, I terminate it and run the nrfutil command. The progress bar keeps at 0%, too. After the programs finish, the key info of the printed error is: pc_ble_driver_py.exceptions.NordicSemiException: No ping response after opening COM port. This may mean the communication doesn't really start.

Do you think the bootloader has some problem and needs to be updated? I don't know whether the bootloader update with Jlink is complex or not. If it is simple, how about updating it first and then reinstall the firmware?
Best,
Max

Hi Max,
Do you have a Jlink or any similar device (https://www.segger.com/products/debug-probes/j-link/)? It looks like we need to update the bootloader.
Regards,
Anoop

Hi Anoop,
I have got one now. And what need I do next? If you have any large attachments, you might send them to my email (maxleizhao@gmail.com).
Best,
Max

Dear MaxandYuki,
I have the same described problem with ADI study watch exactly. Everything that happened to your watch is happening to mine. I followed all suggested solutions in this discussion but none of them worked. Did you find a solution for the problem? Please help.


Use systemctl is-enabled in function is-enabled

This PR changes the function is-enabled in scripts/install-lib to use the built-in systemctl is-enabled command instead of piping the output of systemctl list-unit-files to awk.

I feel like there was a reason we were using list-unit-files instead of is-enabled here, but I could be very wrong.
@matteodelabre?

I feel like there was a reason we were using list-unit-files instead of is-enabled here, but I could be very wrong.
@matteodelabre?

I feel like there was a reason we were using list-unit-files instead of is-enabled here, but I could be very wrong.
@matteodelabre?

I personally don't see a problem there. The function is documented what it is supposed to do.
# Check whether a systemd unit exists and is enabled
#
# Arguments:
#
# $1 - Full name of the systemd unit, e.g. "xochitl.service"
#
# Exit code:
#
# 0 if the unit exists and is enabled, 1 otherwise
is-enabled() { ... }

The only change now would be that checking e.g. for "tarnish" instead of "tarnish.service" would works. But I don't see a problem there. If anything this seems like an improvement to me. Could be wrong though.

I feel like there was a reason we were using list-unit-files instead of is-enabled here, but I could be very wrong.
@matteodelabre?

I personally don't see a problem there. The function is documented what it is supposed to do.
# Check whether a systemd unit exists and is enabled
#
# Arguments:
#
# $1 - Full name of the systemd unit, e.g. "xochitl.service"
#
# Exit code:
#
# 0 if the unit exists and is enabled, 1 otherwise
is-enabled() { ... }

The only change now would be that checking e.g. for "tarnish" instead of "tarnish.service" would works. But I don't see a problem there. If anything this seems like an improvement to me. Could be wrong though.

Maybe an edit to the documentation, that not just the full name is required would be appropriate. But whether we want this behaviour is also a point to discuss.

Maybe an edit to the documentation, that not just the full name is required would be appropriate. But whether we want this behaviour is also a point to discuss.

All in all, the changes seem to boil down to these test cases as far as I can see (when suggestions are applied to fix bugs):
In my example, tarnish.service is currently enabled and remux.service is present but disabled.

Value of $1
Old exit code
New exit code

tarnish.service
0
0

tarnish
1
0

tarnishfoo.service
1
1

remux.service
1
1

All in all, the changes seem to boil down to these test cases as far as I can see (when suggestions are applied to fix bugs):
In my example, tarnish.service is currently enabled and remux.service is present but disabled.

Value of $1
Old exit code
New exit code

tarnish.service
0
0

tarnish
1
0

tarnishfoo.service
1
1

remux.service
1
1

So because the exit code is 0 if at least one service is enabled, it's probably better (less error-prone) if the full name is required, no?

So because the exit code is 0 if at least one service is enabled, it's probably better (less error-prone) if the full name is required, no?

So because the exit code is 0 if at least one service is enabled, it's probably better (less error-prone) if the full name is required, no?

I'm not sure what systemd decides in the case of duplicate services files. From testing it seems, that if $1 has not ending (.service, .mount, .socket, ...), systemd puts a .service at the end by default.
Returning exit code 1 if a file didn't contain a dot (.) would most likely make the behaviour match again.

So because the exit code is 0 if at least one service is enabled, it's probably better (less error-prone) if the full name is required, no?

I'm not sure what systemd decides in the case of duplicate services files. From testing it seems, that if $1 has not ending (.service, .mount, .socket, ...), systemd puts a .service at the end by default.
Returning exit code 1 if a file didn't contain a dot (.) would most likely make the behaviour match again.

I feel like there was a reason we were using list-unit-files instead of is-enabled here, but I could be very wrong.
@matteodelabre?

I think I simply missed systemctl is-enabled while reading the man page. Anyway, this is clearly a welcome improvement, thanks @koenvervloesem!
In addition to the differences highlighted by @LinusCDE, we should also be aware that systemctl is-enabled also reports success for units in the following states: enabled-runtime, alias, static, indirect, generated and transient, whereas the existing is-enabled() function only reports success for enabled units.
Overall, I don’t believe that making the function more permissive is an issue given how it is currently used, i.e. for checking if a launcher is enabled or if conflicting units are enabled.

I feel like there was a reason we were using list-unit-files instead of is-enabled here, but I could be very wrong.
@matteodelabre?

I think I simply missed systemctl is-enabled while reading the man page. Anyway, this is clearly a welcome improvement, thanks @koenvervloesem!
In addition to the differences highlighted by @LinusCDE, we should also be aware that systemctl is-enabled also reports success for units in the following states: enabled-runtime, alias, static, indirect, generated and transient, whereas the existing is-enabled() function only reports success for enabled units.
Overall, I don’t believe that making the function more permissive is an issue given how it is currently used, i.e. for checking if a launcher is enabled or if conflicting units are enabled.

This looks like an example 'in the wild' of the use of systemd unit names without the full name:
https://github.com/toltec-dev/toltec/blob/testing/package/rm2fb/package#L61
Apart from the typo (xochtil instead of xochitl), it would probably be better to make use of the is-enabled function here too, and using the full name xochitl.service.

This looks like an example 'in the wild' of the use of systemd unit names without the full name:
https://github.com/toltec-dev/toltec/blob/testing/package/rm2fb/package#L61
Apart from the typo (xochtil instead of xochitl), it would probably be better to make use of the is-enabled function here too, and using the full name xochitl.service.

I feel like there was a reason we were using list-unit-files instead of is-enabled here, but I could be very wrong.
@matteodelabre?

I think I simply missed systemctl is-enabled while reading the man page. Anyway, this is clearly a welcome improvement, thanks @koenvervloesem!
In addition to the differences highlighted by @LinusCDE, we should also be aware that systemctl is-enabled also reports success for units in the following states: enabled-runtime, alias, static, indirect, generated and transient, whereas the existing is-enabled() function only reports success for enabled units.
Overall, I don’t believe that making the function more permissive is an issue given how it is currently used, i.e. for checking if a launcher is enabled or if conflicting units are enabled.

Nice. Feel free to approve this then if there is no more to discuss.

I feel like there was a reason we were using list-unit-files instead of is-enabled here, but I could be very wrong.
@matteodelabre?

I think I simply missed systemctl is-enabled while reading the man page. Anyway, this is clearly a welcome improvement, thanks @koenvervloesem!
In addition to the differences highlighted by @LinusCDE, we should also be aware that systemctl is-enabled also reports success for units in the following states: enabled-runtime, alias, static, indirect, generated and transient, whereas the existing is-enabled() function only reports success for enabled units.
Overall, I don’t believe that making the function more permissive is an issue given how it is currently used, i.e. for checking if a launcher is enabled or if conflicting units are enabled.

Nice. Feel free to approve this then if there is no more to discuss.

This looks like an example 'in the wild' of the use of systemd unit names without the full name:
https://github.com/toltec-dev/toltec/blob/testing/package/rm2fb/package#L61
Apart from the typo (xochtil instead of xochitl), it would probably be better to make use of the is-enabled function here too, and using the full name xochitl.service.

Nice catch! Would you be willing to make this change too?

This looks like an example 'in the wild' of the use of systemd unit names without the full name:
https://github.com/toltec-dev/toltec/blob/testing/package/rm2fb/package#L61
Apart from the typo (xochtil instead of xochitl), it would probably be better to make use of the is-enabled function here too, and using the full name xochitl.service.

Nice catch! Would you be willing to make this change too?

Sure!
This looks wrong too:
https://github.com/toltec-dev/toltec/blob/testing/scripts/bootstrap/bootstrap#L137
systemctl -q --is-enabled opt.mount would have systemctl complain about an unknown option --is-enabled because it doesn't need the dashes. Is the install-lib script also imported in the bootstrap script so the is-enabled function can be used there?

Sure!
This looks wrong too:
https://github.com/toltec-dev/toltec/blob/testing/scripts/bootstrap/bootstrap#L137
systemctl -q --is-enabled opt.mount would have systemctl complain about an unknown option --is-enabled because it doesn't need the dashes. Is the install-lib script also imported in the bootstrap script so the is-enabled function can be used there?

This looks wrong too:
https://github.com/toltec-dev/toltec/blob/testing/scripts/bootstrap/bootstrap#L137
systemctl -q --is-enabled opt.mount would have systemctl complain about an unknown option --is-enabled because it doesn't need the dashes.

Indeed. Thanks for reporting!

Is the install-lib script also imported in the bootstrap script so the is-enabled function can be used there?

Unfortunately not, since the bootstrap script is meant to be fully standalone to simplify the installation procedure.

This looks wrong too:
https://github.com/toltec-dev/toltec/blob/testing/scripts/bootstrap/bootstrap#L137
systemctl -q --is-enabled opt.mount would have systemctl complain about an unknown option --is-enabled because it doesn't need the dashes.

Indeed. Thanks for reporting!

Is the install-lib script also imported in the bootstrap script so the is-enabled function can be used there?

Unfortunately not, since the bootstrap script is meant to be fully standalone to simplify the installation procedure.

Ok, that's it then. My first minor contribution to toltec, as a professional nitpicker ;)

Ok, that's it then. My first minor contribution to toltec, as a professional nitpicker ;)

Sorry, forgot to increase the pkgver of rm2fb, @Eeems

Sorry, forgot to increase the pkgver of rm2fb, @Eeems

@koenvervloesem You'll also need to update the sha256sum in the readme to match the bootstrap script.

@koenvervloesem You'll also need to update the sha256sum in the readme to match the bootstrap script.

I took the liberty to update the docblock above is-enabled to reflect the updated semantics due to this changeset.

I took the liberty to update the docblock above is-enabled to reflect the updated semantics due to this changeset.

Sha256sum updated

Sha256sum updated

Your first contribution is much appreciated @koenvervloesem! Looking forward to the next ones :-)

Your first contribution is much appreciated @koenvervloesem! Looking forward to the next ones :-)


WEBCFW seems to be broken

With previous rumors and now actual testing, we have concluded that the javascript webusb implementation of fusee-gelee seems to be broken right now.

Possibly fixed through https://github.com/AtlasNX/web-cfw-loader/commit/3e42e972d1fa231074b096102f1c415a0983c13f - Needs testing!

Not fixed, Ubuntu 18.04, Chrome 69.0.3497.100

Worked fine for me past 2 days, all Arch packages up to date.

@tylertoilet chrome version?

Chromium Version 76.0.3809.132

Hmm, tested Ubuntu 18.04 with Chromium 76.0.3809.100 and it doesn't work. Might be some incompatibility across distros.

Last test on Pop! Os 19.04 with latest Brave wasn't successful either.

Not working, tested on Windows 10 1903 x86-64 with Brave.

Confirmed working again on Pop! Os 19.04 with Brave. I do understand Nichole's concern though, we definitely need to explain this better

Doesnt work on macOS 10.14.6 with Chrome Stable (77.0.3865.90). APX comes up; and it connects:
Requesting access to device...
Preparing to launch CTCaer_Hekate...
Connected to NVIDIA Corp. APX
However thats it. No payload is pushed. Screen on Switch remains blank.

macOS might possibly be fixed through #59.
Windows seems to sometimes work (Heard about Edge Chromium supporting it correctly)
Linux works fully again (with the tweak).


[GCCBOSC CodeFest] Creation of a jupyter tutorial

I started to work on a short tutorial for introduction at using Jupyter notebooks in Galaxy, import/export data, installation of packages, image display etc.

Thanks @Delphine-L


[New Feature]: Package analytics support

Description of the new feature/enhancement
Could winget show the package analytics data, like download, install data etc.
Proposed technical implementation details (optional)
Here is an example from Brew.sh:
https://formulae.brew.sh/formula/libsoup#default

https://github.com/microsoft/winget-pkgs/discussions/39736