CMVN error on TIMIT Database

Hi, i ran into a problem when training a lstm-rnn acoustic model on TIMIT database. Here are parts of my code and the corresponding result after running.There is an error,  e.g., LOG (apply-cmvn:main():apply-cmvn.cc:129) Applied cepstral mean and variance normalization to 400 utterances, errors on 0 .  I can't find what's going wrong.
Can anyone help me? Thanks!
-----------------------------------------parts of my code---------------------------
if [ $stage -le 2 ]; then
echo =====================================================================
echo "                    FBank Feature Generation                       "
echo =====================================================================
fbankdir=fbank
Generate the fbank features; by default 40-dimensional fbanks on each frame
steps/make_fbank.sh --cmd "$train_cmd" --nj 32 data/data/trn exp/make_fbank/trn $fbankdir || exit 1;
utils/fix_data_dir.sh data/data/trn || exit;
steps/compute_cmvn_stats.sh data/data/trn exp/make_fbank/train $fbankdir || exit 1;
steps/make_fbank.sh --cmd "$train_cmd" --nj 32 data/data/dev exp/make_fbank/dev $fbankdir || exit 1;
utils/fix_data_dir.sh data/data/dev || exit;
steps/compute_cmvn_stats.sh data/data/dev exp/make_fbank/train $fbankdir || exit 1;
steps/make_fbank.sh --cmd "$train_cmd" --nj 32 data/data/tst exp/make_fbank/tst $fbankdir || exit 1;
utils/fix_data_dir.sh data/data/tst || exit;
steps/compute_cmvn_stats.sh data/data/tst exp/make_fbank/train $fbankdir || exit 1;
fi
if [ $stage -le 3 ]; then
echo =====================================================================
echo "                Network Training              "
echo =====================================================================
Specify network structure and generate the network topology
input_feat_dim=120   # dimension of the input features; we will use 40-dimensional fbanks with deltas and double deltas
lstm_layer_num=3     # number of LSTM layers
lstm_cell_dim=240    # number of memory cells in every LSTM layer
dir=exp/train_phn_l${lstm_layer_num}_c${lstm_cell_dim}
mkdir -p $dir
target_num=cat data/lang_phn/units.txt | wc -l; target_num=$[$target_num+1]; #  #targets = #labels + 1 (the blank)
Output the network topology
utils/model_topo.py --input-feat-dim $input_feat_dim --lstm-layer-num $lstm_layer_num
--lstm-cell-dim $lstm_cell_dim --target-num $target_num
--fgate-bias-init 1.0 > $dir/nnet.proto || exit 1;
Label sequences; simply convert words into their label indices
utils/prep_ctc_trans.py data/lang_phn/lexicon_numbers.txt data/data/trn/trans "" | gzip -c - > $dir/labels.tr.gz
utils/prep_ctc_trans.py data/lang_phn/lexicon_numbers.txt data/data/dev/trans "" | gzip -c - > $dir/labels.cv.gz
Train the network with CTC. Refer to the script for details about the arguments
steps/train_ctc_parallel.sh --add-deltas true --num-sequence 10 --frame-num-limit 25000
--learn-rate 0.00004 --report-step 1000 --halving-after-epoch 12
data/data/trn data/data/dev $dir || exit 1;
echo =====================================================================
echo "                            Decoding                               "
echo =====================================================================
decoding
for lm_suffix in sw1_tg sw1_fsh_tgpr; do
steps/decode_ctc_lat.sh --cmd "$decode_cmd" --nj 20 --beam 17.0 --lattice_beam 8.0 --max-active 5000 --acwt 0.6
data/lang_phn_${lm_suffix} data/data/tst $dir/decode_eval2000_${lm_suffix} || exit 1;
done
fi
-------------------------------result-----------------------------
steps/train_ctc_parallel.sh --add-deltas true --num-sequence 10 --frame-num-limit 25000 --learn-rate 0.00004 --report-step 1000 --halving-after-epoch 12 data/data/trn data/data/dev exp/train_phn_l3_c240
feat-to-len scp:data/data/trn/feats.scp ark,t:-
feat-to-len scp:data/data/dev/feats.scp ark,t:-
copy-feats 'ark,s,cs:apply-cmvn --norm-vars=true --utt2spk=ark:data/data/trn/utt2spk scp:data/data/trn/cmvn.scp scp:exp/train_phn_l3_c240/train.scp ark:- |' ark,scp:/tmp/tmp.n5hv6njls3/train.ark,exp/train_phn_l3_c240/train_local.scp
apply-cmvn --norm-vars=true --utt2spk=ark:data/data/trn/utt2spk scp:data/data/trn/cmvn.scp scp:exp/train_phn_l3_c240/train.scp ark:-
LOG (apply-cmvn:main():apply-cmvn.cc:129) Applied cepstral mean and variance normalization to 3696 utterances, errors on 0
LOG (copy-feats:main():copy-feats.cc:100) Copied 3696 feature matrices.
copy-feats 'ark,s,cs:apply-cmvn --norm-vars=true --utt2spk=ark:data/data/dev/utt2spk scp:data/data/dev/cmvn.scp scp:exp/train_phn_l3_c240/cv.scp ark:- |' ark,scp:/tmp/tmp.n5hv6njls3/cv.ark,exp/train_phn_l3_c240/cv_local.scp
apply-cmvn --norm-vars=true --utt2spk=ark:data/data/dev/utt2spk scp:data/data/dev/cmvn.scp scp:exp/train_phn_l3_c240/cv.scp ark:-
LOG (apply-cmvn:main():apply-cmvn.cc:129) Applied cepstral mean and variance normalization to 400 utterances, errors on 0
LOG (copy-feats:main():copy-feats.cc:100) Copied 400 feature matrices.

Not sure - this all seems fine to me? Where is the error?

Yeah maybe it's just the misleading message "errors on 0" ... even just mentioning the word 'error' can be scary in a log message :)

But the training just exited before finishing and i didn't get any model. still not figuring out what's going wrong....

The logs show EPOCH 25 RUNNING - presumably you have models from epoch 0 (untrained) to 24 - not? Or are you for some reason starting the training at epoch 25, which means the system tries to load epoch 24, and fails?

Take a look in exp/model_l4_c320/log/ and search for the training log of iteration 25. You can also try to rerun the training from the last successful epoch by rerunning the training part of the script.


Knowledge - Data fetched from knowledge is not aqurate ( has additional information not specific to the query). Also i have to ask to use knowledge to get information from knowledge file.

otto commit id - 11a350d23
Steps to reproduce the problem:

Create an agent.

% otto create
 INFO  Creating an agent

You are about to create an agent. An agent is AI that will respond to user input
according to the instructions you provide.

 INFO
 INFO  ID: a19xm98
 INFO  URL: http://localhost:8080/invoke/a19xm98

You can now interact with your new agent by running:

CLI:  otto invoke a19xm98 Hello
cURL: curl -d Hello http://localhost:8080/invoke/a19xm98

Add the following knowledge file to the agent
MyDiet.pdf

 % curl localhost:8080/agents/a19xm98/knowledge/mydietplan --data-binary @<file-name>
{"fileName":"mydietplan","agentID":"a19xm98","ingestionStatus":{},"fileDetails":{}}

Chat with the agent on What can I eat in empty stomach .Use knowledge

% otto invoke a19xm98
Input: 11a350d239b514

> Run ID: r14qwkr
> Input: What can I eat in empty stomach
> Waiting for model...
Eating the right foods on an empty stomach can help kickstart your metabolism, provide essential nutrients, and set a positive tone for the rest of the day. Here are some foods that are generally considered goo to eat on an empty stomach:

1. **Fruits**:
   - **Watermelon**: Hydrating and rich in vitamins.
   - **Papaya**: Good for digestion and rich in fiber.
   - **Berries**: High in antioxidants and vitamins.

3. **Nuts**:
   - Almonds, walnuts, and other nuts provide healthy fats, protein, and fiber.

4. **Oatmeal**:
   - A great source of soluble fiber, which can help lower cholesterol and keep you full longer.

5. **Eggs**:
   - High in protein and other essential nutrients.

6. **Greek Yogurt**:
   - Rich in probiotics, protein, and calcium.

7. **Honey with Warm Water**:
   - Can help boost metabolism and provide a quick source of energy.

8. **Whole Grain Bread**:
   - Provides complex carbohydrates and fiber.

9. **Chia Seeds**:
   - High in omega-3 fatty acids, fiber, and protein.

10. **Smoothies**:
   - Made with fruits, vegetables, and a protein source like yogurt or protein powder.

11. **Avocado**:
    - Packed with healthy fats, fiber, and various essential nutrients.

12. **Green Tea**:
    - Contains antioxidants and can help boost metabolism.

13. **Bananas**:
    - Provide a quick source of energy and are rich in potassium.

It's important to listen to your body and choose foods that make you feel good and provide sustained energy throughout the morning.

Input: What can I eat in empty stomach? Use knowledge.

> Run ID: r12sggr
> Input: What can I eat in empty stomach? Use knowledge.
> Waiting for model...
> Generating tool input for (knowledgeRetrieval)...  {"query":"What can I eat on an empty stomach?"}
> Running tool (Knowledge Retrieval): {"query":"What can I eat on an empty stomach?"}
> Waiting for model...
Based on the retrieved information, here are some foods that are suitable to consume on an empty stomach:

1. **Fenugreek Seeds**: 1 tsp with a glass of water.
2. **Papaya**: 100 grams.
3. **Non-fat Greek Yogurt**: 170 grams.
5. **Cheese Snack**: 1 piece.
6. **Nuts**: Almonds (10 grams), Peanuts (12 grams), Walnuts (10 grams), or Cashews (9 grams).
7. **Cucumber or Papaya**: 100 grams.

These foods are light, nutritious, and can help kickstart your metabolism for the day.

The response received also has information from First Meal section of the document (along with information from Empty Stomach section.
Chatgpt is able to provide information only from Empty Stomach section for the same query
According to your diet plan, here are the suggested options for eating on an empty stomach:

Fenugreek seeds: 1 tsp with a glass of water (after 30 minutes of having a tablet and a glass of water)
2% Milk: 240 ml (can be split for tea throughout the day)
Papaya: 100 gm or Sugar/Jaggery (10 gm)
These items can help in managing conditions like hypothyroidism while also aiding digestion and energy balance

Trace logs for both chat messages -
calls-1.json
calls-2.json

@sangee2004 I think as a general rule, if you write "Also....", that should go in a separate issue.

I just tested this again - we're super bad for this particular file, but that seems to be because we just extract plain text and don't send it to a VLM to extract the proper table structure.
I'll see how we can fix that as it probably applies to most pure-table PDFs.

Current discussion: https://acorn-io.slack.com/archives/C07FZ46QA2J/p1734355615513409

@iwilltry42 i/m going to excerpt the most important bit of that convo and then as a follow up question.

Sanjay
i wouldnt use a VLM by default. I would let the user/admin mark harder documents that we can then process using more advanced techniques like gptparse ocr then gptparse vision using the ocr output VLM will really slow down the ingestion process by at least an order of magnitude
Thorsten
Right now we do it "smart" - are there images on that page? If yes, take a picture of the page and send it to the VLM. I'd like to do the same for table detection, but have no handle for that right now. I think this would be the perfect middle ground. WDYT?
Sanjay
yeah having a handler for that would be great. im sure for msoffice filetypes and pdfs that arent composed of images, it should be fairly easy
Sheng Liang
Sounds like a good compromise. Can we also on a file-by-file basis, allow the user to select individual files to be OCRed?

This talks about a two part solution:

A handler for detecting tables
User-explicit opt-in to VLM

What is the handler and how would you do that?

I think that's also buried in that conversation, but here are some thoughts:

MuPDF doesn't support this (doesn't seem to handle tables properly at all)
PyMuPDF has a table detection feature which we can try (extra work)
We could use a small/cheap VLM as a judge (extra cost)
We can use something like Docling (IBM project using tiny, specifically designed models) as a judge (extra compute resources)


backup: implement backup ownership transfer test

https://github.com/longhorn/longhorn/issues/4064
https://github.com/longhorn/longhorn-manager/pull/1361

Close in favor of https://github.com/longhorn/longhorn/issues/4076.


(NoReturn) insert weight calculation

insert weight calculation

Greetings @Tealk
This PR has changes to Runequest assets and Thorg. Are these changes intentional?

Cassie

Hi @clevett
No, not really, and I don't know how that got in there.
But I don't think I can delete it?
Sorry I have very little experience with github

Hi @clevett
I think I've corrected everything again.
Sorry to bring such a mess in here.

@Tealk
You can click on the Files change tab at the top to see Thorg is still part of this change request.

Edit: I would recommend backing up your No Return changes and then updating your fork with the current master repo.

Unfortunately I don't get any changes from the master repo


Increment version for monitor releases

Increment package version after release of azure-monitor-ingestion

API change check
API changes are not detected in this pull request.

/check-enforcer override


Implement image-based bone-marrow dosimetry

Utilize atlas (XCAT phantom) bone marrow distribution and register it with patient anatomy for delineation of bone-marrow mask.

Done, on PR #46


Are there docs for this project somewhere?

Hi all. I was wondering if there is API documentation for the project somewhere. If there isn't, I'd be happy to write some up. I'm on winter break, so I have nothing better to do.

We don't have proper documentation other than the README.md. If you want to give it a go, that would be very useful for the community. :)

A first step could be to improve the number and quality of  __docstring__ in the code.


Call level_up_rewards on exp changes/Some pep-8

Short Description:
Call level_up_reward on exp changes
Fixes/Resolves/Closes (please use correct syntax):

#4754
Some pep-8
Need refactor other tasks, wrap refresh inventory with cached object -> reduce get_inventory api calls

:+1:


SDK: how to add back to button in tonkeeper wallet?

When using TonKeeper to connect to a website with a fragment link, I found that there is a "Back to" button to return to the fragment website.
Can this feature be achieved using an SDK library? How can it be implemented? Can you give me some idea?

Hi @LeoWangJ ! Actually you don't need a 'Back' button in TonConnect v2. Fragment uses TonConnect v1, so Tonkeeper shows this button due to the different authorization flow.
If you use TonConnect v2, Tonkeeper will automatically forward the user to the browser/your native app when he will press 'Connect wallet' button in the Tonkeeper


Fix/add percent for drep chart

Description
Fix/add percent for drep chart
Checklist before requesting a review
Issue ticket number and link

[ ] This PR has a valid ticket number or issue: [link]

Testing & Validation

[ ] This PR has been tested/validated in Chrome, Firefox, Safari and Brave browsers.
[ ] The code has been tested locally with test coverage match expectations.
[ ] Added new Unit/Component testing (if relevant).

Security

[ ] No secrets are being committed (i.e. credentials, PII)
[ ] This PR does not have any significant security implications

Code Review

[ ] There is no unused functionality or blocks of commented out code (otherwise, please explain below)
[ ] In addition to this PR, all relevant documentation (e.g. Confluence / README.md file) and architecture diagrams (e.g. Miro) were updated

Design Review

[ ] If this PR contains changes to the UI, it has gone through a design review with UX Designer or Product owner.
[ ] In case PR contains changes to the UI, add some screenshots to notice the differences

Chrome
Before
After
Safari
Before
After
Responsive
Before
After

what is this PR about?

what is this PR about?

sorry @cfuisat . he is fixing the percentage display when the percentage is 0 in dev-test. I changed the target branch


Make chain user provider more accurate

Process chain user provider more accurate

Good catch, thanks @CvekCoding.


Fix Middleware in type definition

Griddle major version
1.8.0
Changes proposed in this pull request
Fixes type definition bug in #726, now (fortunately) checked by #727.
Why these changes are made
We like green builds and working type definitions.
Are there tests?
Types!

You beat me to it :D 👍


Always times out when searching for music

As the title says. Programs used:

mopidy-youtube v0.1.0
mopidy v0.18.3
ympd v1.2.0

pi@raspberrypi /tmp $ uname -a
Linux raspberrypi 3.10.33+ #656 PREEMPT Fri Mar 14 18:19:28 GMT 2014 armv6l GNU/Linux

pi@raspberrypi /etc $ cat os-release
PRETTY_NAME="Raspbian GNU/Linux 7 (wheezy)"
NAME="Raspbian GNU/Linux"
VERSION_ID="7"
VERSION="7 (wheezy)"
ID=raspbian
ID_LIKE=debian
ANSI_COLOR="1;31"
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"

Debug log:
2014-03-20 20:22:43,002 INFO [4679:MainThread] mopidy.__main__: Starting Mopidy 0.18.3
2014-03-20 20:22:43,037 DEBUG [4679:MainThread] mopidy.ext: Loading entry point: http = mopidy.http:Extension [http]
2014-03-20 20:22:43,041 DEBUG [4679:MainThread] mopidy.ext: Loaded extension: Mopidy-HTTP 0.18.3
2014-03-20 20:22:43,042 DEBUG [4679:MainThread] mopidy.ext: Loading entry point: mpd = mopidy.mpd:Extension
2014-03-20 20:22:43,045 DEBUG [4679:MainThread] mopidy.ext: Loaded extension: Mopidy-MPD 0.18.3
2014-03-20 20:22:43,046 DEBUG [4679:MainThread] mopidy.ext: Loading entry point: local = mopidy.local:Extension
2014-03-20 20:22:43,052 DEBUG [4679:MainThread] mopidy.ext: Loaded extension: Mopidy-Local 0.18.3
2014-03-20 20:22:43,053 DEBUG [4679:MainThread] mopidy.ext: Loading entry point: stream = mopidy.stream:Extension
2014-03-20 20:22:43,056 DEBUG [4679:MainThread] mopidy.ext: Loaded extension: Mopidy-Stream 0.18.3
2014-03-20 20:22:43,061 DEBUG [4679:MainThread] mopidy.ext: Loading entry point: soundcloud = mopidy_soundcloud:SoundCloudExtension
2014-03-20 20:22:43,064 DEBUG [4679:MainThread] mopidy.ext: Loaded extension: Mopidy-SoundCloud 1.2.1
2014-03-20 20:22:43,076 DEBUG [4679:MainThread] mopidy.ext: Loading entry point: youtube = mopidy_youtube:Extension
2014-03-20 20:22:43,083 DEBUG [4679:MainThread] mopidy.ext: Loaded extension: Mopidy-Youtube 0.1.0
2014-03-20 20:22:43,158 DEBUG [4679:MainThread] mopidy.ext: Discovered extensions: http, mpd, local, stream, soundcloud, youtube
2014-03-20 20:22:43,265 DEBUG [4679:MainThread] mopidy.config.keyring: Fetching passwords from your keyring failed. Any passwords stored in the keyring will not be available. (org.freedesktop.DBus.Error.NotSupported: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11)
2014-03-20 20:22:43,268 INFO [4679:MainThread] mopidy.config: Loading config from: builtin defaults, /etc/mopidy/extensions.d/*.conf, /etc/mopidy/mopidy.conf, command line options
2014-03-20 20:22:43,299 DEBUG [4679:MainThread] mopidy.config: Config file /etc/mopidy/extensions.d/*.conf not found; skipping
2014-03-20 20:22:45,968 DEBUG [4679:MainThread] mopidy.local.actor: Using json as the local library
2014-03-20 20:22:46,015 INFO [4679:MainThread] mopidy.local.playlists: Loaded 0 local playlists from /var/lib/mopidy/playlists
2014-03-20 20:22:46,017 DEBUG [4679:MainThread] mopidy.local.json: Loading library: /var/lib/mopidy/local/library.json.gz
2014-03-20 20:22:46,261 DEBUG [4679:MainThread] mopidy.local.json: Loading tracks: 242ms
2014-03-20 20:22:46,478 DEBUG [4679:MainThread] mopidy.local.json: Building browse cache: 214ms
2014-03-20 20:22:46,481 INFO [4679:MainThread] mopidy.local.library: Loaded 74 local tracks using json
2014-03-20 20:22:46,921 INFO [4679:MainThread] mopidy.mpd.actor: MPD server running at [::]:6600
2014-03-20 20:22:46,964 DEBUG [4679:MpdFrontend-7] mopidy.zeroconf: Zeroconf publish failed: Avahi service not running.
2014-03-20 20:22:46,966 DEBUG [4679:MpdFrontend-7] mopidy.mpd.actor: Registering MPD with Zeroconf failed.
2014-03-20 20:22:48,445 INFO [4679:MpdSession-8] mopidy.mpd.session: New MPD connection from [::ffff:<IP_ADDRESS>]:40251
2014-03-20 20:22:49,254 DEBUG [4679:MpdSession-8] mopidy.mpd.session: Request from [::ffff:<IP_ADDRESS>]:40251: status
2014-03-20 20:22:49,539 DEBUG [4679:MpdSession-8] mopidy.mpd.session: Response to [::ffff:<IP_ADDRESS>]:40251:
    volume: 100
    repeat: 0
    random: 0
    single: 0
    consume: 0
    playlist: 0
    playlistlength: 0
    xfade: 0
    state: stop
    OK
2014-03-20 20:22:49,554 DEBUG [4679:MpdSession-8] mopidy.mpd.session: Request from [::ffff:<IP_ADDRESS>]:40251: playlistinfo "0:512"
2014-03-20 20:22:49,567 DEBUG [4679:MpdSession-8] mopidy.mpd.session: Response to [::ffff:<IP_ADDRESS>]:40251: OK
2014-03-20 20:22:50,373 DEBUG [4679:MpdSession-8] mopidy.mpd.session: Request from [::ffff:<IP_ADDRESS>]:40251: status
2014-03-20 20:22:50,416 DEBUG [4679:MpdSession-8] mopidy.mpd.session: Response to [::ffff:<IP_ADDRESS>]:40251:
    volume: 100
    repeat: 0
    random: 0
    single: 0
    consume: 0
    playlist: 0
    playlistlength: 0
    xfade: 0
    state: stop
    OK
2014-03-20 20:22:51,223 DEBUG [4679:MpdSession-8] mopidy.mpd.session: Request from [::ffff:<IP_ADDRESS>]:40251: status
2014-03-20 20:22:51,278 DEBUG [4679:MpdSession-8] mopidy.mpd.session: Response to [::ffff:<IP_ADDRESS>]:40251:
    volume: 100
    repeat: 0
    random: 0
    single: 0
    consume: 0
    playlist: 0
    playlistlength: 0
    xfade: 0
    state: stop
    OK
2014-03-20 20:22:52,286 DEBUG [4679:MpdSession-8] mopidy.mpd.session: Request from [::ffff:<IP_ADDRESS>]:40251: status
2014-03-20 20:22:52,330 DEBUG [4679:MpdSession-8] mopidy.mpd.session: Response to [::ffff:<IP_ADDRESS>]:40251:
    volume: 100
    repeat: 0
    random: 0
    single: 0
    consume: 0
    playlist: 0
    playlistlength: 0
    xfade: 0
    state: stop
    OK
2014-03-20 20:22:53,339 DEBUG [4679:MpdSession-8] mopidy.mpd.session: Request from [::ffff:<IP_ADDRESS>]:40251: status
2014-03-20 20:22:53,383 DEBUG [4679:MpdSession-8] mopidy.mpd.session: Response to [::ffff:<IP_ADDRESS>]:40251:
    volume: 100
    repeat: 0
    random: 0
    single: 0
    consume: 0
    playlist: 0
    playlistlength: 0
    xfade: 0
    state: stop
    OK
2014-03-20 20:22:54,391 DEBUG [4679:MpdSession-8] mopidy.mpd.session: Request from [::ffff:<IP_ADDRESS>]:40251: status
2014-03-20 20:22:54,434 DEBUG [4679:MpdSession-8] mopidy.mpd.session: Response to [::ffff:<IP_ADDRESS>]:40251:
    volume: 100
    repeat: 0
    random: 0
    single: 0
    consume: 0
    playlist: 0
    playlistlength: 0
    xfade: 0
    state: stop
    OK
2014-03-20 20:22:55,243 DEBUG [4679:MpdSession-8] mopidy.mpd.session: Request from [::ffff:<IP_ADDRESS>]:40251: status
2014-03-20 20:22:55,286 DEBUG [4679:MpdSession-8] mopidy.mpd.session: Response to [::ffff:<IP_ADDRESS>]:40251:
    volume: 100
    repeat: 0
    random: 0
    single: 0
    consume: 0
    playlist: 0
    playlistlength: 0
    xfade: 0
    state: stop
    OK
2014-03-20 20:22:56,295 DEBUG [4679:MpdSession-8] mopidy.mpd.session: Request from [::ffff:<IP_ADDRESS>]:40251: status
2014-03-20 20:22:56,347 DEBUG [4679:MpdSession-8] mopidy.mpd.session: Response to [::ffff:<IP_ADDRESS>]:40251:
    volume: 100
    repeat: 0
    random: 0
    single: 0
    consume: 0
    playlist: 0
    playlistlength: 0
    xfade: 0
    state: stop
    OK
2014-03-20 20:22:57,357 DEBUG [4679:MpdSession-8] mopidy.mpd.session: Request from [::ffff:<IP_ADDRESS>]:40251: status
2014-03-20 20:22:57,400 DEBUG [4679:MpdSession-8] mopidy.mpd.session: Response to [::ffff:<IP_ADDRESS>]:40251:
    volume: 100
    repeat: 0
    random: 0
    single: 0
    consume: 0
    playlist: 0
    playlistlength: 0
    xfade: 0
    state: stop
    OK
2014-03-20 20:22:58,209 DEBUG [4679:MpdSession-8] mopidy.mpd.session: Request from [::ffff:<IP_ADDRESS>]:40251: status
2014-03-20 20:22:58,253 DEBUG [4679:MpdSession-8] mopidy.mpd.session: Response to [::ffff:<IP_ADDRESS>]:40251:
    volume: 100
    repeat: 0
    random: 0
    single: 0
    consume: 0
    playlist: 0
    playlistlength: 0
    xfade: 0
    state: stop
    OK
2014-03-20 20:22:59,261 DEBUG [4679:MpdSession-8] mopidy.mpd.session: Request from [::ffff:<IP_ADDRESS>]:40251: status
2014-03-20 20:22:59,305 DEBUG [4679:MpdSession-8] mopidy.mpd.session: Response to [::ffff:<IP_ADDRESS>]:40251:
    volume: 100
    repeat: 0
    random: 0
    single: 0
    consume: 0
    playlist: 0
    playlistlength: 0
    xfade: 0
    state: stop
    OK
2014-03-20 20:23:00,313 DEBUG [4679:MpdSession-8] mopidy.mpd.session: Request from [::ffff:<IP_ADDRESS>]:40251: status
2014-03-20 20:23:00,357 DEBUG [4679:MpdSession-8] mopidy.mpd.session: Response to [::ffff:<IP_ADDRESS>]:40251:
    volume: 100
    repeat: 0
    random: 0
    single: 0
    consume: 0
    playlist: 0
    playlistlength: 0
    xfade: 0
    state: stop
    OK
2014-03-20 20:23:01,366 DEBUG [4679:MpdSession-8] mopidy.mpd.session: Request from [::ffff:<IP_ADDRESS>]:40251: status
2014-03-20 20:23:01,417 DEBUG [4679:MpdSession-8] mopidy.mpd.session: Response to [::ffff:<IP_ADDRESS>]:40251:
    volume: 100
    repeat: 0
    random: 0
    single: 0
    consume: 0
    playlist: 0
    playlistlength: 0
    xfade: 0
    state: stop
    OK
2014-03-20 20:23:02,226 DEBUG [4679:MpdSession-8] mopidy.mpd.session: Request from [::ffff:<IP_ADDRESS>]:40251: status
2014-03-20 20:23:02,269 DEBUG [4679:MpdSession-8] mopidy.mpd.session: Response to [::ffff:<IP_ADDRESS>]:40251:
    volume: 100
    repeat: 0
    random: 0
    single: 0
    consume: 0
    playlist: 0
    playlistlength: 0
    xfade: 0
    state: stop
    OK
2014-03-20 20:23:03,284 DEBUG [4679:MpdSession-8] mopidy.mpd.session: Request from [::ffff:<IP_ADDRESS>]:40251: status
2014-03-20 20:23:03,328 DEBUG [4679:MpdSession-8] mopidy.mpd.session: Response to [::ffff:<IP_ADDRESS>]:40251:
    volume: 100
    repeat: 0
    random: 0
    single: 0
    consume: 0
    playlist: 0
    playlistlength: 0
    xfade: 0
    state: stop
    OK
2014-03-20 20:23:04,337 DEBUG [4679:MpdSession-8] mopidy.mpd.session: Request from [::ffff:<IP_ADDRESS>]:40251: status
2014-03-20 20:23:04,382 DEBUG [4679:MpdSession-8] mopidy.mpd.session: Response to [::ffff:<IP_ADDRESS>]:40251:
    volume: 100
    repeat: 0
    random: 0
    single: 0
    consume: 0
    playlist: 0
    playlistlength: 0
    xfade: 0
    state: stop
    OK
2014-03-20 20:23:05,118 DEBUG [4679:MpdSession-8] mopidy.mpd.session: Request from [::ffff:<IP_ADDRESS>]:40251: search any "yt:savage garden"
2014-03-20 20:23:05,272 INFO [4679:SoundCloudBackend-4] mopidy_soundcloud.library: Searching SoundCloud for 'yt:savage garden'
2014-03-20 20:23:05,277 DEBUG [4679:SoundCloudBackend-4] mopidy_soundcloud.soundcloud: Requesting https://api.soundcloud.com/tracks.json?q=yt%3Asavage+garden&filter=streamable&order=hotness&limit=10&client_id=93e33e327fd8a9b77becd179652272e2
2014-03-20 20:23:05,577 INFO [4679:SoundCloudBackend-4] requests.packages.urllib3.connectionpool: Starting new HTTPS connection (1): api.soundcloud.com
2014-03-20 20:23:05,581 INFO [4679:YoutubeBackend-5] requests.packages.urllib3.connectionpool: Starting new HTTPS connection (1): www.googleapis.com
2014-03-20 20:23:06,846 DEBUG [4679:SoundCloudBackend-4] requests.packages.urllib3.connectionpool: "GET /tracks.json?q=yt%3Asavage+garden&filter=streamable&order=hotness&limit=10&client_id=93e33e327fd8a9b77becd179652272e2 HTTP/1.1" 200 2
2014-03-20 20:23:08,120 DEBUG [4679:MainThread] mopidy.utils.network: Client most likely disconnected.
2014-03-20 20:23:08,410 DEBUG [4679:YoutubeBackend-5] requests.packages.urllib3.connectionpool: "GET /youtube/v3/search?q=yt%3Asavage+garden&part=id&type=video&key=AIzaSyAl1Xq9DwdE_KD4AtPaE4EJl3WZe2zCqg4&maxResults=15 HTTP/1.1" 200 3105
2014-03-20 20:23:09,379 DEBUG [4679:YoutubeBackend-5] root: Fetched video info
2014-03-20 20:23:09,383 DEBUG [4679:YoutubeBackend-5] root: Encrypted signature detected.
2014-03-20 20:23:10,385 DEBUG [4679:YoutubeBackend-5] root: Fetched watchv page
2014-03-20 20:23:11,293 DEBUG [4679:YoutubeBackend-5] root: Fetched javascript
2014-03-20 20:23:11,296 DEBUG [4679:YoutubeBackend-5] root: Scanning js for main function.
2014-03-20 20:23:11,447 DEBUG [4679:YoutubeBackend-5] root: Found main function: cE
2014-03-20 20:23:11,451 DEBUG [4679:YoutubeBackend-5] root: Extracting function 'cE' from javascript
2014-03-20 20:23:11,480 DEBUG [4679:YoutubeBackend-5] root: extracted function cE(a){a=a.split("");a=dE(a,48);a=a.slice(2);a=a.reverse();a=a.slice(1);a=dE(a,4);a=dE(a,35);return a.join("")};
2014-03-20 20:23:11,484 DEBUG [4679:YoutubeBackend-5] root: scanning javascript for secondary functions.
2014-03-20 20:23:11,496 DEBUG [4679:YoutubeBackend-5] root: found secondary function 'dE'
2014-03-20 20:23:11,500 DEBUG [4679:YoutubeBackend-5] root: Extracting function 'dE' from javascript
2014-03-20 20:23:11,529 DEBUG [4679:YoutubeBackend-5] root: extracted function dE(a,b){var c=a[0];a[0]=a[b%a.length];a[b]=c;return a};
2014-03-20 20:23:11,533 DEBUG [4679:YoutubeBackend-5] root: found secondary function 'dE'
2014-03-20 20:23:11,537 DEBUG [4679:YoutubeBackend-5] root: function 'dE' is already in map.
2014-03-20 20:23:11,543 DEBUG [4679:YoutubeBackend-5] root: found secondary function 'dE'
2014-03-20 20:23:11,546 DEBUG [4679:YoutubeBackend-5] root: function 'dE' is already in map.
2014-03-20 20:23:11,623 DEBUG [4679:YoutubeBackend-5] root: Decrypted sig = 1DECFFB64AAE149224B15B7C5C9365...
2014-03-20 20:23:12,021 DEBUG [4679:YoutubeBackend-5] root: Fetched video info
2014-03-20 20:23:12,025 DEBUG [4679:YoutubeBackend-5] root: Encrypted signature detected.
2014-03-20 20:23:12,474 DEBUG [4679:YoutubeBackend-5] root: Fetched watchv page
2014-03-20 20:23:12,544 DEBUG [4679:YoutubeBackend-5] root: Decrypted sig = CF121C9469F1225879030E78590C41...
2014-03-20 20:23:13,130 DEBUG [4679:YoutubeBackend-5] root: Fetched video info
2014-03-20 20:23:13,138 DEBUG [4679:YoutubeBackend-5] root: Encrypted signature detected.
2014-03-20 20:23:13,640 DEBUG [4679:YoutubeBackend-5] root: Fetched watchv page
2014-03-20 20:23:13,706 DEBUG [4679:YoutubeBackend-5] root: Decrypted sig = 30F89361BA8BBD09FB3B7735D13248...
2014-03-20 20:23:14,228 DEBUG [4679:YoutubeBackend-5] root: Fetched video info
2014-03-20 20:23:14,741 DEBUG [4679:YoutubeBackend-5] root: Fetched video info
2014-03-20 20:23:15,227 DEBUG [4679:YoutubeBackend-5] root: Fetched video info
2014-03-20 20:23:15,231 DEBUG [4679:YoutubeBackend-5] root: Encrypted signature detected.
2014-03-20 20:23:15,616 DEBUG [4679:YoutubeBackend-5] root: Fetched watchv page
2014-03-20 20:23:15,695 DEBUG [4679:YoutubeBackend-5] root: Decrypted sig = FA8841E4F3CD13992945E768113D6F...
2014-03-20 20:23:16,177 DEBUG [4679:YoutubeBackend-5] root: Fetched video info
2014-03-20 20:23:16,767 DEBUG [4679:YoutubeBackend-5] root: Fetched video info
2014-03-20 20:23:16,771 DEBUG [4679:YoutubeBackend-5] root: Encrypted signature detected.
2014-03-20 20:23:17,219 DEBUG [4679:YoutubeBackend-5] root: Fetched watchv page
2014-03-20 20:23:17,292 DEBUG [4679:YoutubeBackend-5] root: Decrypted sig = 745A3093AB2A5A73A6DAADCDC6BA9E...
2014-03-20 20:23:17,760 DEBUG [4679:YoutubeBackend-5] root: Fetched video info
2014-03-20 20:23:17,764 DEBUG [4679:YoutubeBackend-5] root: Encrypted signature detected.
2014-03-20 20:23:18,106 DEBUG [4679:YoutubeBackend-5] root: Fetched watchv page
2014-03-20 20:23:18,174 DEBUG [4679:YoutubeBackend-5] root: Decrypted sig = D07FAB1E5A0933924FBEBC1BAB6552...
2014-03-20 20:23:18,657 DEBUG [4679:YoutubeBackend-5] root: Fetched video info
2014-03-20 20:23:18,661 DEBUG [4679:YoutubeBackend-5] root: Encrypted signature detected.
2014-03-20 20:23:19,250 DEBUG [4679:YoutubeBackend-5] root: Fetched watchv page
2014-03-20 20:23:19,311 DEBUG [4679:YoutubeBackend-5] root: Decrypted sig = 222CF1D401BD781241E8BEB1D25901...
2014-03-20 20:23:19,796 DEBUG [4679:YoutubeBackend-5] root: Fetched video info
2014-03-20 20:23:19,801 DEBUG [4679:YoutubeBackend-5] root: Encrypted signature detected.
2014-03-20 20:23:20,182 DEBUG [4679:YoutubeBackend-5] root: Fetched watchv page
2014-03-20 20:23:20,248 DEBUG [4679:YoutubeBackend-5] root: Decrypted sig = 347BDA856F7AE9F32193DF2E7A8D61...
2014-03-20 20:23:20,707 DEBUG [4679:YoutubeBackend-5] root: Fetched video info
2014-03-20 20:23:21,614 DEBUG [4679:YoutubeBackend-5] root: Fetched video info
2014-03-20 20:23:22,108 DEBUG [4679:YoutubeBackend-5] root: Fetched video info
2014-03-20 20:23:22,113 DEBUG [4679:YoutubeBackend-5] root: Encrypted signature detected.
2014-03-20 20:23:22,698 DEBUG [4679:YoutubeBackend-5] root: Fetched watchv page
2014-03-20 20:23:22,781 DEBUG [4679:YoutubeBackend-5] root: Decrypted sig = F0B796A2AFC646917B2870D276B123...
2014-03-20 20:23:23,137 DEBUG [4679:YoutubeBackend-5] root: Fetched video info
2014-03-20 20:23:23,141 DEBUG [4679:YoutubeBackend-5] root: Encrypted signature detected.
2014-03-20 20:23:23,713 DEBUG [4679:YoutubeBackend-5] root: Fetched watchv page
2014-03-20 20:23:23,781 DEBUG [4679:YoutubeBackend-5] root: Decrypted sig = 788D60664A431C15B6C87A2849D845...
2014-03-20 20:23:23,838 INFO [4679:MpdSession-9] mopidy.mpd.session: New MPD connection from [::ffff:<IP_ADDRESS>]:40255
2014-03-20 20:23:23,854 DEBUG [4679:MpdSession-8] mopidy.mpd.session: Response to [::ffff:<IP_ADDRESS>]:40251:
    file: youtube:video/Savage Garden - I Knew I Loved You.jjnmICxvoVY
    Time: 230
    Artist:
    Title: Savage Garden - I Knew I Loved You
    Album: Youtube
    Track: 0
    Comment: jjnmICxvoVY
    file: youtube:video/Savage Garden - Truly Madly Deeply.WQnAxOQxQIU
    Time: 262
    Artist:
    Title: Savage Garden - Truly Madly Deeply
    Album: Youtube
    Track: 0
    Comment: WQnAxOQxQIU
    file: youtube:video/Savage Garden - Hold Me.CFAlR7tWekc
    Time: 245
    Artist:
    Title: Savage Garden - Hold Me
    Album: Youtube
    Track: 0
    Comment: CFAlR7tWekc
    file: youtube:video/Savage Garden - Affirmation (Full Album).ZGkO8WULkWk
    Time: 3227
    Artist:
    Title: Savage Garden - Affirmation (Full Album)
    Album: Youtube
    Track: 0
    Comment: ZGkO8WULkWk
    file: youtube:video/Savage Garden - I Want You.HQt6jIKNwgU
    Time: 232
    Artist:
    Title: Savage Garden - I Want You
    Album: Youtube
    Track: 0
    Comment: HQt6jIKNwgU
    file: youtube:video/Savage Garden I Knew I Loved You.zOJ282tAJ20
    Time: 214
    Artist:
    Title: Savage Garden " I Knew I Loved You "
    Album: Youtube
    Track: 0
    Comment: zOJ282tAJ20
    file: youtube:video/Savage Garden - I Knew I Loved You Lyrics.TWh473e8fXs
    Time: 241
    Artist:
    Title: Savage Garden - I Knew I Loved You Lyrics
    Album: Youtube
    Track: 0
    Comment: TWh473e8fXs
    file: youtube:video/Savage Garden - To The Moon Back (Extended Version).HCm6gRHINqA
    Time: 287
    Artist:
    Title: Savage Garden - To The Moon & Back (Extended Version)
    Album: Youtube
    Track: 0
    Comment: HCm6gRHINqA
    file: youtube:video/Savage Garden- Hold Me Lyrics.NdPJxEUF4gI
    Time: 291
    Artist:
    Title: Savage Garden- Hold Me Lyrics
    Album: Youtube
    Track: 0
    Comment: NdPJxEUF4gI
    file: youtube:video/Savage Garden - Affirmation.RFzZ-xpyfoo
    Time: 251
    Artist:
    Title: Savage Garden - Affirmation
    Album: Youtube
    Track: 0
    Comment: RFzZ-xpyfoo
    file: youtube:video/Savage Garden debut album (Full Album).CR5esvhfOv8
    Time: 2678
    Artist:
    Title: Savage Garden [debut album] (Full Album)
    Album: Youtube
    Track: 0
    Comment: CR5esvhfOv8
    file: youtube:video/Savage Garden - The Animal Song HD.CJrczhUqUJI
    Time: 241
    Artist:
    Title: Savage Garden - The Animal Song [HD]
    Album: Youtube
    Track: 0
    Comment: CJrczhUqUJI
    file: youtube:video/Savage Garden - I knew i loved you with lyrics.INP494j92sg
    Time: 249
    Artist:
    Title: Savage Garden - I knew i loved you with lyrics
    Album: Youtube
    Track: 0
    Comment: INP494j92sg
    OK
2014-03-20 20:23:23,867 DEBUG [4679:MpdSession-8] mopidy.utils.network: Already stopping: Unexpected client error: [Errno 9] Bad file descriptor
2014-03-20 20:23:23,876 DEBUG [4679:MpdSession-8] mopidy.utils.network: Already stopping: Actor is shutting down.
2014-03-20 20:23:23,872 DEBUG [4679:MainThread] mopidy.utils.network: Client most likely disconnected.
2014-03-20 20:23:23,870 INFO [4679:MpdSession-10] mopidy.mpd.session: New MPD connection from [::ffff:<IP_ADDRESS>]:40262
2014-03-20 20:23:23,892 DEBUG [4679:MpdSession-9] mopidy.utils.network: Already stopping: Actor is shutting down.
2014-03-20 20:23:23,913 DEBUG [4679:MainThread] mopidy.utils.network: Bad client flags: 25
2014-03-20 20:23:23,920 DEBUG [4679:MpdSession-10] mopidy.utils.network: Already stopping: Actor is shutting down.
2014-03-20 20:23:23,923 INFO [4679:MpdSession-11] mopidy.mpd.session: New MPD connection from [::ffff:<IP_ADDRESS>]:40271
2014-03-20 20:23:23,926 DEBUG [4679:MainThread] mopidy.utils.network: Client most likely disconnected.
2014-03-20 20:23:23,940 DEBUG [4679:MpdSession-11] mopidy.utils.network: Already stopping: Actor is shutting down.
2014-03-20 20:23:24,361 DEBUG [4679:MainThread] mopidy.utils.network: Client most likely disconnected.
2014-03-20 20:23:24,364 INFO [4679:MpdSession-12] mopidy.mpd.session: New MPD connection from [::ffff:<IP_ADDRESS>]:40279
2014-03-20 20:23:24,372 DEBUG [4679:MpdSession-12] mopidy.utils.network: Already stopping: Unexpected client error: [Errno 9] Bad file descriptor
2014-03-20 20:23:24,378 DEBUG [4679:MpdSession-12] mopidy.utils.network: Already stopping: Actor is shutting down.
2014-03-20 20:23:25,362 INFO [4679:MpdSession-13] mopidy.mpd.session: New MPD connection from [::ffff:<IP_ADDRESS>]:40284
2014-03-20 20:23:26,370 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Request from [::ffff:<IP_ADDRESS>]:40284: status
2014-03-20 20:23:26,414 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Response to [::ffff:<IP_ADDRESS>]:40284:
    volume: 100
    repeat: 0
    random: 0
    single: 0
    consume: 0
    playlist: 0
    playlistlength: 0
    xfade: 0
    state: stop
    OK
2014-03-20 20:23:27,223 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Request from [::ffff:<IP_ADDRESS>]:40284: status
2014-03-20 20:23:27,267 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Response to [::ffff:<IP_ADDRESS>]:40284:
    volume: 100
    repeat: 0
    random: 0
    single: 0
    consume: 0
    playlist: 0
    playlistlength: 0
    xfade: 0
    state: stop
    OK
2014-03-20 20:23:28,276 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Request from [::ffff:<IP_ADDRESS>]:40284: status
2014-03-20 20:23:28,326 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Response to [::ffff:<IP_ADDRESS>]:40284:
    volume: 100
    repeat: 0
    random: 0
    single: 0
    consume: 0
    playlist: 0
    playlistlength: 0
    xfade: 0
    state: stop
    OK
2014-03-20 20:23:29,334 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Request from [::ffff:<IP_ADDRESS>]:40284: status
2014-03-20 20:23:29,380 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Response to [::ffff:<IP_ADDRESS>]:40284:
    volume: 100
    repeat: 0
    random: 0
    single: 0
    consume: 0
    playlist: 0
    playlistlength: 0
    xfade: 0
    state: stop
    OK
2014-03-20 20:23:30,389 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Request from [::ffff:<IP_ADDRESS>]:40284: status
2014-03-20 20:23:30,434 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Response to [::ffff:<IP_ADDRESS>]:40284:
    volume: 100
    repeat: 0
    random: 0
    single: 0
    consume: 0
    playlist: 0
    playlistlength: 0
    xfade: 0
    state: stop
    OK
2014-03-20 20:23:31,242 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Request from [::ffff:<IP_ADDRESS>]:40284: status
2014-03-20 20:23:31,284 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Response to [::ffff:<IP_ADDRESS>]:40284:
    volume: 100
    repeat: 0
    random: 0
    single: 0
    consume: 0
    playlist: 0
    playlistlength: 0
    xfade: 0
    state: stop
    OK
2014-03-20 20:23:32,291 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Request from [::ffff:<IP_ADDRESS>]:40284: status
2014-03-20 20:23:32,333 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Response to [::ffff:<IP_ADDRESS>]:40284:
    volume: 100
    repeat: 0
    random: 0
    single: 0
    consume: 0
    playlist: 0
    playlistlength: 0
    xfade: 0
    state: stop
    OK
2014-03-20 20:23:33,340 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Request from [::ffff:<IP_ADDRESS>]:40284: status
2014-03-20 20:23:33,390 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Response to [::ffff:<IP_ADDRESS>]:40284:
    volume: 100
    repeat: 0
    random: 0
    single: 0
    consume: 0
    playlist: 0
    playlistlength: 0
    xfade: 0
    state: stop
    OK
2014-03-20 20:23:34,397 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Request from [::ffff:<IP_ADDRESS>]:40284: status
2014-03-20 20:23:34,439 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Response to [::ffff:<IP_ADDRESS>]:40284:
    volume: 100
    repeat: 0
    random: 0
    single: 0
    consume: 0
    playlist: 0
    playlistlength: 0
    xfade: 0
    state: stop
    OK
2014-03-20 20:23:35,246 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Request from [::ffff:<IP_ADDRESS>]:40284: status
2014-03-20 20:23:35,289 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Response to [::ffff:<IP_ADDRESS>]:40284:
    volume: 100
    repeat: 0
    random: 0
    single: 0
    consume: 0
    playlist: 0
    playlistlength: 0
    xfade: 0
    state: stop
    OK
2014-03-20 20:23:36,296 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Request from [::ffff:<IP_ADDRESS>]:40284: status
2014-03-20 20:23:36,338 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Response to [::ffff:<IP_ADDRESS>]:40284:
    volume: 100
    repeat: 0
    random: 0
    single: 0
    consume: 0
    playlist: 0
    playlistlength: 0
    xfade: 0
    state: stop
    OK
2014-03-20 20:23:37,346 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Request from [::ffff:<IP_ADDRESS>]:40284: status
2014-03-20 20:23:37,389 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Response to [::ffff:<IP_ADDRESS>]:40284:
    volume: 100
    repeat: 0
    random: 0
    single: 0
    consume: 0
    playlist: 0
    playlistlength: 0
    xfade: 0
    state: stop
    OK
2014-03-20 20:23:38,396 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Request from [::ffff:<IP_ADDRESS>]:40284: status
2014-03-20 20:23:38,446 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Response to [::ffff:<IP_ADDRESS>]:40284:
    volume: 100
    repeat: 0
    random: 0
    single: 0
    consume: 0
    playlist: 0
    playlistlength: 0
    xfade: 0
    state: stop
    OK
2014-03-20 20:23:39,253 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Request from [::ffff:<IP_ADDRESS>]:40284: status
2014-03-20 20:23:39,295 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Response to [::ffff:<IP_ADDRESS>]:40284:
    volume: 100
    repeat: 0
    random: 0
    single: 0
    consume: 0
    playlist: 0
    playlistlength: 0
    xfade: 0
    state: stop
    OK
2014-03-20 20:23:40,302 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Request from [::ffff:<IP_ADDRESS>]:40284: status
2014-03-20 20:23:40,345 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Response to [::ffff:<IP_ADDRESS>]:40284:
    volume: 100
    repeat: 0
    random: 0
    single: 0
    consume: 0
    playlist: 0
    playlistlength: 0
    xfade: 0
    state: stop
    OK
2014-03-20 20:23:41,352 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Request from [::ffff:<IP_ADDRESS>]:40284: status
2014-03-20 20:23:41,396 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Response to [::ffff:<IP_ADDRESS>]:40284:
    volume: 100
    repeat: 0
    random: 0
    single: 0
    consume: 0
    playlist: 0
    playlistlength: 0
    xfade: 0
    state: stop
    OK
2014-03-20 20:23:42,202 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Request from [::ffff:<IP_ADDRESS>]:40284: status
2014-03-20 20:23:42,244 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Response to [::ffff:<IP_ADDRESS>]:40284:
    volume: 100
    repeat: 0
    random: 0
    single: 0
    consume: 0
    playlist: 0
    playlistlength: 0
    xfade: 0
    state: stop
    OK
2014-03-20 20:23:43,252 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Request from [::ffff:<IP_ADDRESS>]:40284: status
2014-03-20 20:23:43,294 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Response to [::ffff:<IP_ADDRESS>]:40284:
    volume: 100
    repeat: 0
    random: 0
    single: 0
    consume: 0
    playlist: 0
    playlistlength: 0
    xfade: 0
    state: stop
    OK
2014-03-20 20:23:44,301 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Request from [::ffff:<IP_ADDRESS>]:40284: status
2014-03-20 20:23:44,345 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Response to [::ffff:<IP_ADDRESS>]:40284:
    volume: 100
    repeat: 0
    random: 0
    single: 0
    consume: 0
    playlist: 0
    playlistlength: 0
    xfade: 0
    state: stop
    OK
2014-03-20 20:23:45,353 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Request from [::ffff:<IP_ADDRESS>]:40284: status
2014-03-20 20:23:45,437 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Response to [::ffff:<IP_ADDRESS>]:40284:
    volume: 100
    repeat: 0
    random: 0
    single: 0
    consume: 0
    playlist: 0
    playlistlength: 0
    xfade: 0
    state: stop
    OK
2014-03-20 20:23:46,254 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Request from [::ffff:<IP_ADDRESS>]:40284: status
2014-03-20 20:23:46,322 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Response to [::ffff:<IP_ADDRESS>]:40284:
    volume: 100
    repeat: 0
    random: 0
    single: 0
    consume: 0
    playlist: 0
    playlistlength: 0
    xfade: 0
    state: stop
    OK
2014-03-20 20:23:47,329 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Request from [::ffff:<IP_ADDRESS>]:40284: status
2014-03-20 20:23:47,373 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Response to [::ffff:<IP_ADDRESS>]:40284:
    volume: 100
    repeat: 0
    random: 0
    single: 0
    consume: 0
    playlist: 0
    playlistlength: 0
    xfade: 0
    state: stop
    OK
2014-03-20 20:23:48,380 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Request from [::ffff:<IP_ADDRESS>]:40284: status
2014-03-20 20:23:48,430 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Response to [::ffff:<IP_ADDRESS>]:40284:
    volume: 100
    repeat: 0
    random: 0
    single: 0
    consume: 0
    playlist: 0
    playlistlength: 0
    xfade: 0
    state: stop
    OK
2014-03-20 20:23:49,236 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Request from [::ffff:<IP_ADDRESS>]:40284: status
2014-03-20 20:23:49,278 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Response to [::ffff:<IP_ADDRESS>]:40284:
    volume: 100
    repeat: 0
    random: 0
    single: 0
    consume: 0
    playlist: 0
    playlistlength: 0
    xfade: 0
    state: stop
    OK
2014-03-20 20:23:50,286 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Request from [::ffff:<IP_ADDRESS>]:40284: status
2014-03-20 20:23:50,331 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Response to [::ffff:<IP_ADDRESS>]:40284:
    volume: 100
    repeat: 0
    random: 0
    single: 0
    consume: 0
    playlist: 0
    playlistlength: 0
    xfade: 0
    state: stop
    OK
2014-03-20 20:23:51,338 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Request from [::ffff:<IP_ADDRESS>]:40284: status
2014-03-20 20:23:51,381 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Response to [::ffff:<IP_ADDRESS>]:40284:
    volume: 100
    repeat: 0
    random: 0
    single: 0
    consume: 0
    playlist: 0
    playlistlength: 0
    xfade: 0
    state: stop
    OK
2014-03-20 20:23:52,388 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Request from [::ffff:<IP_ADDRESS>]:40284: status
2014-03-20 20:23:52,434 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Response to [::ffff:<IP_ADDRESS>]:40284:
    volume: 100
    repeat: 0
    random: 0
    single: 0
    consume: 0
    playlist: 0
    playlistlength: 0
    xfade: 0
    state: stop
    OK
2014-03-20 20:23:53,241 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Request from [::ffff:<IP_ADDRESS>]:40284: status
2014-03-20 20:23:53,288 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Response to [::ffff:<IP_ADDRESS>]:40284:
    volume: 100
    repeat: 0
    random: 0
    single: 0
    consume: 0
    playlist: 0
    playlistlength: 0
    xfade: 0
    state: stop
    OK
2014-03-20 20:23:54,295 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Request from [::ffff:<IP_ADDRESS>]:40284: status
2014-03-20 20:23:54,338 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Response to [::ffff:<IP_ADDRESS>]:40284:
    volume: 100
    repeat: 0
    random: 0
    single: 0
    consume: 0
    playlist: 0
    playlistlength: 0
    xfade: 0
    state: stop
    OK
2014-03-20 20:23:55,345 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Request from [::ffff:<IP_ADDRESS>]:40284: status
2014-03-20 20:23:55,436 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Response to [::ffff:<IP_ADDRESS>]:40284:
    volume: 100
    repeat: 0
    random: 0
    single: 0
    consume: 0
    playlist: 0
    playlistlength: 0
    xfade: 0
    state: stop
    OK
2014-03-20 20:23:56,243 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Request from [::ffff:<IP_ADDRESS>]:40284: status
2014-03-20 20:23:56,336 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Response to [::ffff:<IP_ADDRESS>]:40284:
    volume: 100
    repeat: 0
    random: 0
    single: 0
    consume: 0
    playlist: 0
    playlistlength: 0
    xfade: 0
    state: stop
    OK
2014-03-20 20:23:57,343 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Request from [::ffff:<IP_ADDRESS>]:40284: status
2014-03-20 20:23:57,424 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Response to [::ffff:<IP_ADDRESS>]:40284:
    volume: 100
    repeat: 0
    random: 0
    single: 0
    consume: 0
    playlist: 0
    playlistlength: 0
    xfade: 0
    state: stop
    OK
2014-03-20 20:23:58,231 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Request from [::ffff:<IP_ADDRESS>]:40284: status
2014-03-20 20:23:58,334 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Response to [::ffff:<IP_ADDRESS>]:40284:
    volume: 100
    repeat: 0
    random: 0
    single: 0
    consume: 0
    playlist: 0
    playlistlength: 0
    xfade: 0
    state: stop
    OK
2014-03-20 20:23:59,342 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Request from [::ffff:<IP_ADDRESS>]:40284: status
2014-03-20 20:23:59,423 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Response to [::ffff:<IP_ADDRESS>]:40284:
    volume: 100
    repeat: 0
    random: 0
    single: 0
    consume: 0
    playlist: 0
    playlistlength: 0
    xfade: 0
    state: stop
    OK
2014-03-20 20:24:00,230 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Request from [::ffff:<IP_ADDRESS>]:40284: status
2014-03-20 20:24:00,281 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Response to [::ffff:<IP_ADDRESS>]:40284:
    volume: 100
    repeat: 0
    random: 0
    single: 0
    consume: 0
    playlist: 0
    playlistlength: 0
    xfade: 0
    state: stop
    OK
2014-03-20 20:24:01,289 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Request from [::ffff:<IP_ADDRESS>]:40284: status
2014-03-20 20:24:01,331 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Response to [::ffff:<IP_ADDRESS>]:40284:
    volume: 100
    repeat: 0
    random: 0
    single: 0
    consume: 0
    playlist: 0
    playlistlength: 0
    xfade: 0
    state: stop
    OK
2014-03-20 20:24:02,338 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Request from [::ffff:<IP_ADDRESS>]:40284: status
2014-03-20 20:24:02,382 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Response to [::ffff:<IP_ADDRESS>]:40284:
    volume: 100
    repeat: 0
    random: 0
    single: 0
    consume: 0
    playlist: 0
    playlistlength: 0
    xfade: 0
    state: stop
    OK
2014-03-20 20:24:03,389 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Request from [::ffff:<IP_ADDRESS>]:40284: status
2014-03-20 20:24:03,434 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Response to [::ffff:<IP_ADDRESS>]:40284:
    volume: 100
    repeat: 0
    random: 0
    single: 0
    consume: 0
    playlist: 0
    playlistlength: 0
    xfade: 0
    state: stop
    OK
2014-03-20 20:24:04,241 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Request from [::ffff:<IP_ADDRESS>]:40284: status
2014-03-20 20:24:04,292 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Response to [::ffff:<IP_ADDRESS>]:40284:
    volume: 100
    repeat: 0
    random: 0
    single: 0
    consume: 0
    playlist: 0
    playlistlength: 0
    xfade: 0
    state: stop
    OK
2014-03-20 20:24:05,300 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Request from [::ffff:<IP_ADDRESS>]:40284: status
2014-03-20 20:24:05,342 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Response to [::ffff:<IP_ADDRESS>]:40284:
    volume: 100
    repeat: 0
    random: 0
    single: 0
    consume: 0
    playlist: 0
    playlistlength: 0
    xfade: 0
    state: stop
    OK
2014-03-20 20:24:06,349 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Request from [::ffff:<IP_ADDRESS>]:40284: status
2014-03-20 20:24:06,440 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Response to [::ffff:<IP_ADDRESS>]:40284:
    volume: 100
    repeat: 0
    random: 0
    single: 0
    consume: 0
    playlist: 0
    playlistlength: 0
    xfade: 0
    state: stop
    OK
2014-03-20 20:24:07,246 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Request from [::ffff:<IP_ADDRESS>]:40284: status
2014-03-20 20:24:07,289 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Response to [::ffff:<IP_ADDRESS>]:40284:
    volume: 100
    repeat: 0
    random: 0
    single: 0
    consume: 0
    playlist: 0
    playlistlength: 0
    xfade: 0
    state: stop
    OK
2014-03-20 20:24:08,296 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Request from [::ffff:<IP_ADDRESS>]:40284: status
2014-03-20 20:24:08,339 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Response to [::ffff:<IP_ADDRESS>]:40284:
    volume: 100
    repeat: 0
    random: 0
    single: 0
    consume: 0
    playlist: 0
    playlistlength: 0
    xfade: 0
    state: stop
    OK
2014-03-20 20:24:09,346 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Request from [::ffff:<IP_ADDRESS>]:40284: status
2014-03-20 20:24:09,389 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Response to [::ffff:<IP_ADDRESS>]:40284:
    volume: 100
    repeat: 0
    random: 0
    single: 0
    consume: 0
    playlist: 0
    playlistlength: 0
    xfade: 0
    state: stop
    OK
2014-03-20 20:24:10,397 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Request from [::ffff:<IP_ADDRESS>]:40284: status
2014-03-20 20:24:10,440 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Response to [::ffff:<IP_ADDRESS>]:40284:
    volume: 100
    repeat: 0
    random: 0
    single: 0
    consume: 0
    playlist: 0
    playlistlength: 0
    xfade: 0
    state: stop
    OK
2014-03-20 20:24:11,247 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Request from [::ffff:<IP_ADDRESS>]:40284: status
2014-03-20 20:24:11,290 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Response to [::ffff:<IP_ADDRESS>]:40284:
    volume: 100
    repeat: 0
    random: 0
    single: 0
    consume: 0
    playlist: 0
    playlistlength: 0
    xfade: 0
    state: stop
    OK
2014-03-20 20:24:12,297 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Request from [::ffff:<IP_ADDRESS>]:40284: status
2014-03-20 20:24:12,340 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Response to [::ffff:<IP_ADDRESS>]:40284:
    volume: 100
    repeat: 0
    random: 0
    single: 0
    consume: 0
    playlist: 0
    playlistlength: 0
    xfade: 0
    state: stop
    OK
2014-03-20 20:24:13,347 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Request from [::ffff:<IP_ADDRESS>]:40284: status
2014-03-20 20:24:13,391 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Response to [::ffff:<IP_ADDRESS>]:40284:
    volume: 100
    repeat: 0
    random: 0
    single: 0
    consume: 0
    playlist: 0
    playlistlength: 0
    xfade: 0
    state: stop
    OK
2014-03-20 20:24:14,398 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Request from [::ffff:<IP_ADDRESS>]:40284: status
2014-03-20 20:24:14,441 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Response to [::ffff:<IP_ADDRESS>]:40284:
    volume: 100
    repeat: 0
    random: 0
    single: 0
    consume: 0
    playlist: 0
    playlistlength: 0
    xfade: 0
    state: stop
    OK
2014-03-20 20:24:15,248 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Request from [::ffff:<IP_ADDRESS>]:40284: status
2014-03-20 20:24:15,291 DEBUG [4679:MpdSession-13] mopidy.mpd.session: Response to [::ffff:<IP_ADDRESS>]:40284:
    volume: 100
    repeat: 0
    random: 0
    single: 0
    consume: 0
    playlist: 0
    playlistlength: 0
    xfade: 0
    state: stop
    OK
2014-03-20 20:24:16,043 DEBUG [4679:MpdSession-13] mopidy.utils.network: Actor is shutting down.

Yep, hardcoded value https://github.com/notandy/ympd/blob/master/src/mpd_client.c#L289. @luipugs I would suggest opening bug report for notandy/ympd. Thx for detailed report though, good job. :)


'resetFilter()' without performing fetch on 'FetchRequestController'

I'd like to be able to call resetFilter() on FetchRequestController without performing a fetch.
My use case is that I need to reset my filters back to the initial predicate, then add NEW filters before performing a new fetch.
Proposal
Add a performFetch parameter to the function.
resetFilter(performFetch: Bool = false)
Implementation would also require adding the performFetch parameter to resetPredicate()
I'd be willing to make a PR, but wanted to get feedback on the proposal first.

It makes perfect sense. It would be nice to have a PR about this. We will need some doc/info about the changed behaviour (some users may expect the former behaviour).

I'll make a PR tomorrow. It will include documentation for the changed methods.


Validation Error unknown field "serviceMatch" in Calico 3.20.0

I am trying to create a network policy in kubernetes 1.24 and calico 3.20 environment so that my component connect to the database through service by making use of serviceMatch feild. This solution worked for us in 1.21 and 3.15 and 1.24 and 3.15 without any errors. But when we upgraded the calico to 3.20 we getting unknown feild error.
Network rule in  NetworkPolicy yaml:

action: allow
protocol: TCP
source:
selector: com.siemens.sdis.container.app == 'myApp' && com.siemens.sdis.container.component == 'my-component'
destination:
serviceMatch:
name: db
namespace: testnp
ports:

8080

Error:
Error: INSTALLATION FAILED: unable to build kubernetes objects from release manifest: error validating "": error validating data: ValidationError(NetworkPolicy.spec.egress[2].destination): unknown field "serviceMatch" in org.projectcalico.crd.v1.NetworkPolicy.spec.egress.destination
Environment Details:
kubernetes version: 1.24
calico version: 3.20 (docker.io/calico/node:v3.20.0)
networkpolicy api version: crd.projectcalico.org/v1

The field should be called "services".
Per the example from the docs:
apiVersion: projectcalico.org/v3
kind: NetworkPolicy
metadata:
  name: allow-api-access
  namespace: my-app
spec:
  selector: all()
  egress:
    - action: Allow
      destination:
        services:
          name: kubernetes
          namespace: default

https://docs.tigera.io/archive/v3.20/security/service-policy

we tried the filed "services", still the same error.

@@
==================================================
Copyright 2023.
Siemens Product Lifecycle Management Software Inc.
All Rights Reserved.
==================================================
@@
apiVersion: crd.projectcalico.org/v1
kind: NetworkPolicy
metadata:
name: allow-tc-tcss
namespace: my-namespace
spec:
order: 110 #Here the order is similar to rank / rule priority in AWS NACLs.
selector: com.siemens.sdis.container.app == 'myApp' && com.siemens.sdis.container.component == 'my-component'
types:
- Ingress
- Egress
INGRESS RULES
ingress:
#Rule Start
#All Ingress Traffic from Internal ALB to tc-tcss pods

action: allow
protocol: TCP
source: {}
destination:
selector: com.siemens.sdis.container.app == 'myApp' && com.siemens.sdis.container.component == 'my-component'
ports:

8080
#Rule End

EGRESS RULES
egress:
#All Egress Traffic for callback

action: allow
protocol: TCP
source:
selector: com.siemens.sdis.container.app == 'myApp' && com.siemens.sdis.container.component == 'my-component'
destination:
serviceMatch:
name: samauth-svc
namespace: my-namespace
ports:

443                                 # TcSS callback port open for port #443 ( TLS)
#Rule End

#All Egress Traffic for callback

action: allow
protocol: TCP
source:
selector: com.siemens.sdis.container.app == 'myApp' && com.siemens.sdis.container.component == 'my-component'
destination:
selector: com.siemens.sdis.container.app == 'myApp' && com.siemens.sdis.container.component == 'tcserver'
ports:

8087                      # communication to MUX/tcserver
#Rule End

#All Egress Traffic for callback

action: allow
protocol: TCP
source:
selector: com.siemens.sdis.container.app == 'myApp' && com.siemens.sdis.container.component == 'my-component'
destination:
selector: com.siemens.sdis.container.app == 'myApp' && com.siemens.sdis.container.component == 'tc-ldap'
ports:

10389                      # communication to ldap pod
#Rule End

#Rule Start
#All Egress TCP DNS Traffic for tc-tcss pods

action: allow
protocol: TCP
source: {}
destination:
ports:

53                                    # For DNS Resolution
#Rule End

#Rule Start
#All Egress UDP DNS Traffic for tc-tcss pods

action: allow
protocol: UDP
source: {}
destination:
ports:

53                                    # For DNS Resolution
#Rule End

apiVersion: crd.projectcalico.org/v1
kind: NetworkPolicy
metadata:
name: allow-my-component
namespace: my-namespace
spec:
selector: com.org.container.app == 'myApp' && com.org.container.component == 'my-component'
types:
- Ingress
- Egress
INGRESS RULES
ingress:
#Rule Start

action: allow
protocol: TCP
source: {}
destination:
selector: com.org.container.app == 'myApp' && com.org.container.component == 'my-component'
ports:

8888
#Rule End

EGRESS RULES
egress:
#All Egress Traffic for callback

action: allow
protocol: TCP
source:
selector: com.org.container.app == 'myApp' && com.org.container.component == 'my-component'
destination:
serviceMatch:
name: service-svc
namespace: my-namespace
ports:

777
#Rule End

apiVersion: crd.projectcalico.org/v1

Please see this issue: https://github.com/projectcalico/calico/issues/6412

   serviceMatch:

Like I said in my previous message, this is wrong. It needs to be services

How this field "serviceMatch" or "services" functionality is working with version V1 and CRDs in Calico 3.15 and not in 3.20? we are using the open source calico and not planning to migrate to enterprise edition.
Is this field deprecated in latest versions?

Reminder on this issue. please reopen the issue.

Could you provide the full yaml object you're trying to create?

Could you please show me a valid Calico API object? The one that you included in your previous comment is not valid for the two reasons I suggested:

It uses the crd.projectcalico.org/v1 API, which is unsupported and not validated / defaulted.
It uses the wrong name for the field - "serviceMatch" instead of "service"

Until I have that I can't reasonably say this is a bug in Calico.

apiVersion: crd.projectcalico.org/v1
kind: NetworkPolicy
metadata:
name: allow-my-component
namespace: my-namespace
spec:
selector: com.org.container.app == 'myApp' && com.org.container.component == 'my-component'
types:
- Ingress
- Egress
ingress:

action: allow
protocol: TCP
source: {}
destination:
selector: com.org.container.app == 'myApp' && com.org.container.component == 'my-component'
ports:

8888
egress:

action: allow
protocol: TCP
source:
selector: com.org.container.app == 'myApp' && com.org.container.component == 'my-component'
destination:
services:
name: service-svc
namespace: my-namespace
ports:

777

This the yaml we tested, as you can see we used the feild "services" instead of services. Regarding the api version we can't use v3 since we using open source calico not the enterprise edition. we using open source calico and crds hence v1 not v3.


Aug. 3

Commits on Jul 31, 2017
Merge pull request #16 from LemonGrassSmell/master
change dir tools to paraflow-tools
Merge branch 'master' of https://github.com/dbiir/ParaFlow
Merge pull request #18 from ray6080/master
Commits on Aug 01, 2017
define exception system for paraflow and config factory
add test class for last commit
Merge pull request #25 from ray6080/master
basic meta server main loop
Merge pull request #26 from ray6080/master

Aug. 3 update complete!

I am clever and smart!


Document the AWS SDK for Swift versioning policy

Describe the issue
The AWS SDK for Swift versioning policy should be documented in the SDK so that customers can understand & manage change in future SDK releases.
Links
https://github.com/awslabs/aws-sdk-swift/blob/main/Sources/Core/AWSSDKForSwift/Documentation.docc/stability.md (Existing SDK policy)
https://docs.aws.amazon.com/sdkref/latest/guide/maint-policy.html (SDK & Tools org policy)

Tracking in internal ticketing system


Toward version 0.1

@ciotlosm
Seems like we're nearing a point where we can go to a first versioned release.
Creating a tracking issue to that end:

[x] resolve #15

[x] resolve #2 (add pm2)

[ ] determine how to handle versioning / releases

I think this is very accurate. I was hoping to do pm2 yesterday, but the OPI setup delayed me. I will try today in a virtualised environment to do the pm2 setup and create a merge request for both #15 and #2

@ciotlosm
So, with the changes in your latest pull request, I think we're ready for a 0.1 release.
However, the biggest problem is how we will track updates of the zigbee2mqtt repository and rebuild/push new docker images which each update of the master branch there. The current proposed solution in #19 is to trigger a travis build of this repo/image after each successful build of the zigbee2mqtt travis CI. This is a good option, but does not integrate perfectly with the workflow of the add-on release cycle using the build-env tool that this repository uses:

on each build and docker push, if the corresponding git commit is tagged, the docker image will be tagged latest and with the git tag version number.
however, if the commit is untagged (as would be the case for all builds triggered by updates to zigbee2mqtt), there is no version tag assigned, and the test tag is applied.

I'm not sure how the hass.io UI and add-on management system will respond in this instance, as I've only published using versioned releases. I certainly don't think it will allow for the very nice "update available" UI, and I suspect that tagged releases and the test releases could not exist alongside each other (users would probably be "stuck" at the last tagged release and not presented with an option to "update" to the newest test image).
My first thought: could the node script referenced by @Koenkk in #19 be modified to tag and bump the sub-version with each build?

@danielwelch I think there could be another approach:

Keep 0.1 as stable version
Create a secondary repo that uses "test" image for people that want to use "unstable" - or some other alternative for this

Another option would be to allow @Koenkk to trigger a version increase / tag (so addon gets updated to 0.2, 0.3 etc.) when he thinks that the changes he has done are stable enough to get published.

@ciotlosm I agree that whatever we decide to do here, this should be a temporary measure until https://github.com/Koenkk/zigbee2mqtt development slows down and we start doing tagged releases.

Would it be an idea to give me write access to your repo? In this way I can automatically add tags to to the latest commit which would then trigger a rebuild.

I’m ok with that. Note that for each new tag, you’d have up to update the corresponding version key in the add-on config.json

So updating https://github.com/danielwelch/hassio-zigbee2mqtt/blob/master/zigbee2mqtt/config.json#L3 everytime with the latest zigbee2mqtt commit hash would be ok?

It not relate but i update code for add new device to this https://github.com/Koenkk/zigbee-shepherd-converters, but how to update it to hass addon? I am new to python and nodejs too.

That line needs to correspond to a docker tag. The build-env tool we use to build and push docker images will automatically tag docker images with version tags that match a corresponding git tag that is built in Travis. So, if a commit tagged v0.1.1 is found, the resulting docker image will be tagged “0.1.1” and the config line needs to be updated to 0.1.1 for users to be presented with an option to update.

@Koenkk I wrote a web service that, in response to push events from a github webhook, will trigger travis builds for this repository. It's deployed on heroku. If you'd like to tie into it, let me know and somehow I'll securely send you the URL and required secret.

Great! I'm on telegram: @koenkk

For whatever reason, I can't find that username on the global search. I'm on telegram @dwelch, maybe you'll have more luck

In zigbee2mqtt's current state, I suppose we could expose that as an optional config variable in the UI, and then just use git to get a specified version. What's the use case, out of curiosity?

I'm just thinking of "worst case scenario". Let's say zigbee2mqtt gets a PR merged that breaks some functionality that was not tested - like a setup with many sensors, and neither of us is around to roll it back or fix it for a few days.
As users area already starting to use the setup on the "production" systems, I guess it would be nice to have a backup emergency plan so nobody gets punished by their significant other :-)

Not a bad idea, especially since without versioned releases we're really relying on the stability of the "bleeding edge" of zigbee2mqtt

@ciotlosm see #23

I think we should modify this to use https://github.com/Koenkk/zigbee2mqtt/issues/96 as dependency. Everything else about the addon is in right working condition.

Yes, as soon as there’s a stable 0.1 release I’d say we can modify to use that and release a 0.1 ourselves. Would it be worth it to include an option to use the latest master (I’m thinking if someone wants to test/develop while using the addon)?

@danielwelch totally agree

@ciotlosm I think the nicest way to handle this dual offering, when the time comes, (stable 0.1 alongside latest master of zigbee2mqtt) may be to do something similar to what esphomeyaml is doing. Ottowinter is providing 2 add-ons, a stable version and edge verions, both installable from the same Hass.io repository.
This way, we can customize the build process a little better (for example, the git clone depth difference would become a non-issue).

@danielwelch I was wondering if that possible. I think it's a really good way to do it. 👍

Zigbee2mqtt just released their first versions release a day ago.

Will this also be released? Any ETA on when?

See #36


fix frameanchor bottom

closes #1043

This PR broke the alignment of labels on scatterplots.
Here is a frameAnchor of top:

The frameAnchor of bottom is supposed to be symmetric, with the baseline of the text touching the anchor:

This PR shifts the bottom anchor by 1.29 lines, resulting in dots that are significantly farther away than intended by the anchor:

Perhaps the problem in #1043 is specific to multiline text. I will investigate but we should revert this and apply a different fix.


realtime in rust server

Does this work in rust server, or only if you're serving something via a browser?

This is for browser environment.


Section 5: Spelling error

Sorry if this seems trivial or pedantic, I just wanted to point out a simple spelling error in the very end of section 5. In the last sentence, se should be see.

That's perfectly fine to point out, thank you!


Don't Use LUIS as a training platform?

I'm very confused by this advice.  I believe part of the intent with it is that, because a given LUIS app is intended to be around a particular subject or set of actions (domain), it doesn't enable you to train a lot of different domains at once.  But... what else would we use as a training platform???

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

ID: 1d0fd49d-4f0a-061c-84c0-9ddeefa039ad
Version Independent ID: 6b87ed50-802f-74ed-bd99-14bffd5142d5
Content: Understand LUIS best practices - Azure
Content Source: articles/cognitive-services/LUIS/luis-concept-best-practices.md
Service: cognitive-services
GitHub Login: @v-geberr
Microsoft Alias: v-geberr;

@VMey Thanks for the feedback. Can you clarify your question, or is there something the documentation did not convey adequately? Please provide additional details. Thank you~

@coreygriggs Thank you for clarifying what you meant. The phrasing needs to change to include "a general  natural language processing (NLP) platform" or something like that. Some customers want to use LUIS for a different, more general platform/purpose than it was intended. Let me work on the phrasing and see if I can come up with something more clear. #in-progress

@v-geberr - thanks for the reply!  Given that it's not supposed to be more general-purpose, I'm wondering what would be seen as a use case for using dispatch with that specificity to domain you mentioned in mind.

@VMey Thanks for your feedback in Git. Hope we have answered you question well. We are now processing to close this issue, if you have further challenge of this topic we are happy to reopen this issue.

Hi v-geberr
I have a question about your comment that "It needs to broken into smaller domains so LUIS can do a better job. A top level domain would have an intent for each subdomain. The chat bot gets a prediction for the intent and now knows which subdomain app to send the utterance to for a refined/granular prediction.". How can we carry out this? How to let the top level domian LUIS app know which subdomain app to use? I'm really confused about the process.
Thanks


Fixing missing requires and state request

This fixes issue #1

Okay I figured out what was happening. The folders that those files were in were lowercase, but the class names are caps, and on Mac this doesn't matter because the filesystem isn't case sensitive. I just pushed a commit that renames the folders to the proper case, and that should fix it: 5adecfb143908c13e40a451deb94e50a2e445c87

Okay I ended up pushing up the scope fix too,  so I'm just going to close this out. Thanks for bringing this up!


Broken Pipe, using in Helix

Hello again! After adding that git root I start to get completions, but only for the file I'm currently in :-)
Checking Helix's logs, they write of a broken pipe. I'd like to help looking into this when I have a little time, but I'm not sure when that will be so I figured I could at least report it.
2024-04-10T23:08:17.900 helix_lsp::client [WARN] language server failed to terminate gracefully - server closed the stream
2024-04-10T23:08:17.900 helix_lsp::transport [ERROR] markdown-oxide err: <- StreamClosed
2024-04-10T23:08:17.900 helix_lsp::transport [ERROR] markdown-oxide err: <- IO(Os { code: 32, kind: BrokenPipe, message: "Broken pipe" })

Thank you!
Ill look into it

After a bit of research, I suspect this is an issue with helix's lsp implementation.
I suggest opening an issue on that repo.
Sorry I won't be help for this! Hope you figure it out.


TODOs after CSE1110 2022

List of future features for Andy:

if Andy doesn't find tests, show the exception (simulate it by writing an invalid method source method; add a tip saying that this is probably because the method source is throwing an exception, if they are using MethodSource in the test)
give more tips when pitest fails (usually use of static in the test class or shared state)
update to new pitest 1.9.2
analytics module
extra parameter in the checks and meta tests, that if that fails, the entire grade of the exercise becomes 0 (or subtracted by something)
if error message is about lots of compilation errors and "did not find symbols", give a tip saying that for them to look at the first occurrence of the problem, and check whether it's valid java there"
can we assert it's a real pbt? maybe if we find a way to count the number of times the method under test is called
if coverage == 0, make the whole grade 0 (sometimes some code checks pass, giving students points)
have the Jacoco annotation to not count coverage default in Andy, so that we don't need to add it in every library we need it.

By Frank:
As for the coverage == 0 thing: we do have this in Andy:
        if (totalBranches == 0) {
            return 1f;   // full points assigned
        }

as well as this:
(total > 0 && weight==0 ? " (0 gives full points)":"")

The message in latter makes explicit what happens. But this is not shown in the case we had today:
--- Assessment
Branch coverage: 0/0 (overall weight=0.10)
Mutation coverage: 0/3 (overall weight=0.20)
Code checks: 4/4 (overall weight=0.10)
Meta tests: 0/7 (overall weight=0.60)

Final grade: 20/100

(I expected the grade to be 10/100 but it is 20 because the branch coverage gave full points.)
Maybe the condition should be total == 0 instead, so it is always explicit that full points are awarded. Or maybe we should just quit the entire grading calculation and show an error along the lines of "Some assessment criteria have a total number of achievable points of 0. Contact the course staff to get this fixed."

I converted each of those points into separate (more detailed) issues to keep track of them more easily.


[T4A7][W09-A2]Lee Pei Xuan

work in progress

@pyxyyy
Accepting this PR without a review because, either

we already review this PR during tutorial.
another of your PRs for this tutorial was reviewed in detail.
minimally reviewed and found no important issue.

Good job for doing many activities.


keep open statements with connection and close with connection

This pull request avoids  runtime.SetFinalizer calls and thus avoids potential problems such as "A finalizer may run as soon as an object becomes unreachable" ...

I hope that this list is removed when statement is closed manualy. When making many statements on the one connection, the list will be large.

You are right, but It's a list of pointers which reduces memory usage considerably. And opening thousands of statements on the same connection doesn't look like good practice to me.
I also forgot to assign nil to the list to free it up for gc.  Will create another commit for this...
Anyway we could consider removing the statements from the list when a statements is closed.  Preferably with a mutex lock to avoid problems with concurrent access...
What do you think ? Or do you have another suggestion?

Also remove the entry with stmt.Close(). For example following code does not free the list.
for i := 0; i < 10000; i++ {
  doSomething(db)
}

LGTM. But please wait for my checking.

Could you please rebase master? Test should be passed.

Hmm, not yet ok ...
more_test.go:115: ORA-01000: maximum open cursors exceeded

I'll try to have a look later today.

Think I found the "real" issue. The OCI8Rows.Close() is called by database/sql code, but it does not close the statement after query() because OCI8Rows.cls is false.
I guess OCI8Rows.cls means "want to close the statement as well" ?
Will change this to check of tests pass ...

stmt.QueryRow(sql).Scan(&v) doesn't provide way to close Rows. This will be closed by GC.

  On stmt level OCIRows.cls is false,  on conn level it is put to true true.  This solves the problem locally for the stmt.QueryRow(sql).Scan(&v) test:
$ go test -run TestQueryRowPrepared
github.com/mattn/go-oci8.TestQueryRowPrepared
143
143
PASS
ok      github.com/mattn/go-oci8        0.966s

It seems to solve the problem also on my local machine for the "TestTimeZones" test:
$ go test -run TestTimeZones

When querying the DB for open cursors, the maximum simultaneously open cursors on the TestTimeZones session is never higher then 3 now (while before it went up to > 740 !):
select a.value, s.username, s.sid, s.serial#
from v$sesstat a, v$statname b, v$session s
where a.statistic# = b.statistic#
and s.sid=a.sid
and b.name = 'opened cursors current'
and s.username = 'ORASTUDIO'
order by value desc;

     VALUE USERNAME                              SID    SERIAL#
---------- ------------------------------ ---------- ----------
         3 ORASTUDIO                            1537      33075

But travis still fails with: ORA-01000: maximum open cursors exceeded

But travis still fails with: ORA-01000: maximum open cursors exceeded !?
Could this be something with the travis test-db ? What is the maximum number of open cursors here?

Hmm, sorry I also understand what happen on travis. However, you changes must make go-oci8 better. Thanks. If you are okay to merge, I will merge this.

Before merging  I would like to undo the first commits.  After all keeping the set of open statements at connection level no longer makes sense. I would like to reduce the pull request to the strict minimum.   Let me test first ...

Tests still look OK to me.
The only changes left are these: https://github.com/mattn/go-oci8/pull/198/files?diff=unified
If OK for you, you can merge.  (Better merge as 1 commit).  Thanks!

I figure out why test fail. Now tests passed!
https://travis-ci.org/mattn/go-oci8/builds/347306806

Good news! Thanks!


Replace Sirupsen w sirupsen

Codecov Report

Merging #307 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #307   +/-   ##
=======================================
  Coverage   60.31%   60.31%
=======================================
  Files          87       87
  Lines        7338     7338
=======================================
  Hits         4426     4426
  Misses       2611     2611
  Partials      301      301

Impacted Files
Coverage Δ

snapshot/git/gitdb/create.go
54.54% <ø> (ø)
:arrow_up:

snapshot/snapshots/fake_updater.go
0% <ø> (ø)
:arrow_up:

runner/runners/status_manager.go
83.08% <ø> (ø)
:arrow_up:

snapshot/bundlestore/http_store.go
71.57% <ø> (ø)
:arrow_up:

saga/saga_generators.go
0% <ø> (ø)
:arrow_up:

sched/scheduler/cluster_state.go
83.88% <ø> (ø)
:arrow_up:

workerapi/server/setup.go
8.51% <ø> (ø)
:arrow_up:

runner/runners/queue.go
80.64% <ø> (ø)
:arrow_up:

snapshot/bundlestore/file_store.go
0% <ø> (ø)
:arrow_up:

ice/eval.go
82% <ø> (ø)
:arrow_up:

... and 18 more

Continue to review full report at Codecov.

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


Switch from wstool to vcstool

wstool is no longer recommended for use. vcstool is commonly used in ROS 2 and also works with ROS 1.
https://wiki.ros.org/wstool
https://wiki.ros.org/vcstool

[ ] Switch dependencies.rosinstall to a vcstool compatible format
[ ] Update README
[ ] Add installation of vcstool to CI
[ ] Update CI scripts in build_test.yml

You can assign this to me.

Completed by #31


Org name update in Orgbook Test

Incorporation # BC0878626
Org Name: 0878626 B.C. LTD.
Can you please update the record in orgbook test?
thanks!

Over to you, @amanji !

Closing as completed (see screenshot above)


Support ScyllaDB

Or at least seriously considers it and see how it would go.

This has been addressed by PR #953 and PR #887.
Though this is not perfect and more work is needed.


Tests: Ensure all virt-handlers are ready before migration

What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:
NONE

/cherry-pick release-0.41

/lgtm
/approve
I guess a cherrypick to 0.44 may make sense too.

/cherry-pick release-0.44


Improve the ore-per-minute calculation

(with help from @Choumiko via http://www.factorioforums.com/forum/viewtopic.php?p=112431#p112431)
My first thought on the subject would be to use more than just two samples (immediately-previous and current) to help smooth things out -- perhaps with a weighted average giving the more recent samples preference, but still taking historic (no more than 10 minutes' worth) consumption rate into account.
As a more immediate possible fix, @Choumiko's idea:

take the tick from the last rate that was not 0 and calculate the rate based on the old delta/(current tick - last mined tick)

Somewhere in-between these two, if we have a multi-sampled history, we could just calculate from a sample that's about a minute old (but this would have to allow for fuzziness, as our update rate might not divide 3600 with no remainder).

This has arguably been solved for a long time


New version: Microsoft.OneDrive version 24.226.1110.0004

Created by 🥟 Dumplings.
Microsoft Reviewers: Open in CodeFlow

@stephengillie Need manual merge


[216] Redirect Needed on Documentation Link

Title:
Redirect Needed on Documentation Link
Description:
Redirect needed on:
https://docs.near.org/build/smart-contracts/anatomy/whatisacontract
Summary:
Customer is asking for a redirect on the broken link for smart contracts documentation.
Info
Reported by: Guest<EMAIL_ADDRESS>- Open in Gleap
Location: US
Type: 🚨 BUG
🔗 Open share link
🌍 Open ticket in Gleap
Metadata
browserName: Chrome(<IP_ADDRESS>)
userAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
browser: Chrome
systemName: MacOS
sessionDuration: 68
devicePixelRatio: 1
screenWidth: 2560
screenHeight: 1080
innerWidth: 1502
innerHeight: 835
currentUrl: https://docs.near.org/build/smart-contracts/anatomy/whatisacontract
language: en-US
sdkVersion: 10.1.0
sdkType: javascript
environment: prod

Internal note 📝: Customer is asking for a redirect on the broken link for smart contracts documentation.


Add missing hook to test charm

This was intended to be added in #6 but got missed.  However, the tests will auto-create it, allowing them to pass even when it's missing.  It is, in fact, expected to be in place, though.

It could be argued that the test should have failed without that file in place, but I think we will likely do something else with the storage hooks in the somewhat near future, so I don't think it's worth changing the tests to try to address that.

Travis failure is E: Unable to locate package flake8 on only one of the two environments.  It did the apt update so I have no idea why that would have failed, other than a transient issue with Travis itself.

Per discussion online, I think we'll want to drop the requirement for such symlinks in the future. We'll likely need a hand from juju itself on this, introducing a single hook that is called unconditionally on every other hook execution.


fixes TypeError: Illegal Invocation in node-webkit

requestAnimationFrame, setTimeout and clearTimeout need to be called on the window object explicitely in node-webkit.

Hmm I merged this, but it broke the tests, so I'm reverting it.

I think it broke because of the window object not beeing available while the tests are running. Haven't looked into the tests yet.

Actually this is also making problems when using m.redraw() without a browser, so I should make it work in the tests.


Why do we need to calculate the homography matrix twice?

Thank you very much for your work, but I have some questions:

In https://github.com/NeurAI-Lab/biHomE/blob/main/src/heads/PerceptualHead.py#L177 used DSAC to calculate homography and four points offset
In https://github.com/NeurAI-Lab/biHomE/blob/main/src/heads/PerceptualHead.py#L371 used four points offsets to calculate homography and warp feature map.
Actually homography matrix was calculated twice, but the homography matrix is a little different.
Thanks!

Hi @AbyssGaze ,
good catch! This is just for my convenience: I wanted to have a clean design regardless of the used backbone. The difference is very, very small and it's caused by the sole nature of floating point operations.
Best,
D

Hi @AbyssGaze , I'm closing the issue for now. If you have any other questions feel free to reopen it.


[Bug]: not able to build the image

Please add the exact image (with tag) that you are using
eclispe-temurin:jdk17-jammy
Please add the version of Docker you are running
24.0.5
What happened?
trying to build docker image from my local machine ( here is the dockerfile reference)- https://github.com/adoptium/containers/blob/057e5aa7581e96b8a2334290e750b329d62abfdf/17/jdk/ubuntu/jammy/Dockerfile
error :

[ 5/11] RUN DEBIAN_FRONTEND=noninteractive apt-get update -y &&     DEBIAN_FRONTEND=noninteractive apt-get install -y apt-utils &&     DEBIAN_FRONTEND=noninteractive apt-get install -y --no-install-recommends unzip:
0.984 Get:1 http://ports.ubuntu.com/ubuntu-ports jammy InRelease [270 kB]
1.786 Err:1 http://ports.ubuntu.com/ubuntu-ports jammy InRelease
1.786   At least one invalid signature was encountered.
1.846 Get:2 http://ports.ubuntu.com/ubuntu-ports jammy-updates InRelease [119 kB]
1.989 Err:2 http://ports.ubuntu.com/ubuntu-ports jammy-updates InRelease
1.989   At least one invalid signature was encountered.
2.088 Get:3 http://ports.ubuntu.com/ubuntu-ports jammy-backports InRelease [109 kB]
2.290 Err:3 http://ports.ubuntu.com/ubuntu-ports jammy-backports InRelease
2.290   At least one invalid signature was encountered.
2.371 Get:4 http://ports.ubuntu.com/ubuntu-ports jammy-security InRelease [110 kB]
2.539 Err:4 http://ports.ubuntu.com/ubuntu-ports jammy-security InRelease
2.539   At least one invalid signature was encountered.
2.544 Reading package lists...
2.553 W: GPG error: http://ports.ubuntu.com/ubuntu-ports jammy InRelease: At least one invalid signature was encountered.
2.553 E: The repository 'http://ports.ubuntu.com/ubuntu-ports jammy InRelease' is not signed.
2.553 W: GPG error: http://ports.ubuntu.com/ubuntu-ports jammy-updates InRelease: At least one invalid signature was encountered.
2.553 E: The repository 'http://ports.ubuntu.com/ubuntu-ports jammy-updates InRelease' is not signed.
2.553 W: GPG error: http://ports.ubuntu.com/ubuntu-ports jammy-backports InRelease: At least one invalid signature was encountered.
2.553 E: The repository 'http://ports.ubuntu.com/ubuntu-ports jammy-backports InRelease' is not signed.
2.553 W: GPG error: http://ports.ubuntu.com/ubuntu-ports jammy-security InRelease: At least one invalid signature was encountered.
2.553 E: The repository 'http://ports.ubuntu.com/ubuntu-ports jammy-security InRelease' is not signed.

Relevant log output
> [ 5/11] RUN DEBIAN_FRONTEND=noninteractive apt-get update -y &&     DEBIAN_FRONTEND=noninteractive apt-get install -y apt-utils &&     DEBIAN_FRONTEND=noninteractive apt-get install -y --no-install-recommends unzip:
0.984 Get:1 http://ports.ubuntu.com/ubuntu-ports jammy InRelease [270 kB]
1.786 Err:1 http://ports.ubuntu.com/ubuntu-ports jammy InRelease
1.786   At least one invalid signature was encountered.
1.846 Get:2 http://ports.ubuntu.com/ubuntu-ports jammy-updates InRelease [119 kB]
1.989 Err:2 http://ports.ubuntu.com/ubuntu-ports jammy-updates InRelease
1.989   At least one invalid signature was encountered.
2.088 Get:3 http://ports.ubuntu.com/ubuntu-ports jammy-backports InRelease [109 kB]
2.290 Err:3 http://ports.ubuntu.com/ubuntu-ports jammy-backports InRelease
2.290   At least one invalid signature was encountered.
2.371 Get:4 http://ports.ubuntu.com/ubuntu-ports jammy-security InRelease [110 kB]
2.539 Err:4 http://ports.ubuntu.com/ubuntu-ports jammy-security InRelease
2.539   At least one invalid signature was encountered.
2.544 Reading package lists...
2.553 W: GPG error: http://ports.ubuntu.com/ubuntu-ports jammy InRelease: At least one invalid signature was encountered.
2.553 E: The repository 'http://ports.ubuntu.com/ubuntu-ports jammy InRelease' is not signed.
2.553 W: GPG error: http://ports.ubuntu.com/ubuntu-ports jammy-updates InRelease: At least one invalid signature was encountered.
2.553 E: The repository 'http://ports.ubuntu.com/ubuntu-ports jammy-updates InRelease' is not signed.
2.553 W: GPG error: http://ports.ubuntu.com/ubuntu-ports jammy-backports InRelease: At least one invalid signature was encountered.
2.553 E: The repository 'http://ports.ubuntu.com/ubuntu-ports jammy-backports InRelease' is not signed.
2.553 W: GPG error: http://ports.ubuntu.com/ubuntu-ports jammy-security InRelease: At least one invalid signature was encountered.
2.553 E: The repository 'http://ports.ubuntu.com/ubuntu-ports jammy-security InRelease' is not signed.
------

This looks like a glitch in the Ubuntu package manager, is it still failing today?

I'm going to close this for now. Feel free to reopen it if it's still an issue


Could not install package

I m using Visual Studio 2015 Professional and project .Net Framework 4.6.1
Install-Package : Could not install package 'PoweredSoft.DynamicLinq 1.1.8'. You are trying to install this package into a project that targets '.NETFramework
,Version=v4.6.1', but the package does not contain any assembly references or content files that are compatible with that framework. For more information, con
tact the package author.
At line:1 char:1

Install-Package PoweredSoft.DynamicLinq

  + CategoryInfo          : NotSpecified: (:) [Install-Package], Exception
  + FullyQualifiedErrorId : NuGetCmdletUnhandledException,NuGet.PackageManagement.PowerShellCmdlets.InstallPackageCommand

Does 1.1.7 work?

Thank you for reply. My project is not .Net Core. Is this a problem? Also yes I m using VS2015

If you read the answer, the issue is specific to people trying to install .net standard 2.0 nuget packages on VS2015 for a .NET 4.6.1 project, unrelated to .NET Core.
You can read this stackoverflow question:
https://stackoverflow.com/questions/46788323/installing-a-netstandard-2-0-nuget-package-into-a-vs2015-net-4-6-1-project
Referencing .NET Standard 2.0 packages is supported using the following:
NuGet 3.6.0 or higher for VS 2015 (from NuGet's download site - may not yet be listed as recommended latest)
Install the ".NET Standard Support for Visual Studio 2015" from https://www.microsoft.com/net/download/core (NuGet in VS will also print a link to this in its output window).
There are a still few bugs when consuming .NET Standard 2.0 libraries, especially when mixing .NET Standard < 2.0 and 2.0 libraries but these updates give basic support.

@ahmetcelebi Like investigated the issue is related to the support of .NET Standard Nuget packages for 4.6.1 inside visual studio 2015.
I will close the issue.


gruvbox-plus-icon-pack: init at 4.0

Description of changes
Closes #266170

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 266188 run on x86_64-linux 1

1 package built:

gruvbox-plus-icon-pack

Make a separate commit for adding the user to the maintainer list.

Is the breeze-icons necessary? gnome icons are already used

Is the breeze-icons necessary? gnome icons are already used

Not strictly. The index.theme file has the line:
Inherits=Breeze Dark, gnome, hicolor

That means that icons not provided by this theme will be taken first from Breeze Dark, then from gnome, then from hicolor, in that order. In other words, this theme inherits from them. Therefore those themes complement this one. If the parent themes are not installed, then some icons may not be found.
Then, for completeness of the icon set, we use to install also the parent themes.

Is the breeze-icons necessary? gnome icons are already used

Not strictly. The index.theme file has the line:
Inherits=Breeze Dark, gnome, hicolor

That means that icons not provided by this theme will be taken first from Breeze Dark, then from gnome, then from hicolor, in that order. In other words, this theme inherits from them. Therefore those themes complement this one. If the parent themes are not installed, then some icons may not be found.
Then, for completeness of the icon set, we use to install also the parent themes.

Ah I see! thats fine then, only blockers to this PR is the changes suggested now then

@RGBCube would you like me to add you as a maintainer as well?

@RGBCube would you like me to add you as a maintainer as well?

Sure

Could you add push perms to me on your fork so I could apply the code review?

Nevermind, it doesn't build, fixing rn.

Could this be merged?


cli command to enable agent on ARC is incorrect

The example command for enabling this agent on ARC machines is incorrect
Instead of this:
az connectedmachine machine-extension create --name AzureMonitorWindowsAgent --publisher Microsoft.Azure.Monitor --ids
It should be this:
az connectedmachine extension create --name AzureMonitorWindowsAgent --publisher Microsoft.Azure.Monitor --ids
refer example here:
https://docs.microsoft.com/en-us/cli/azure/connectedmachine/extension?view=azure-cli-latest#az_connectedmachine_extension_create

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

ID: 8201f331-0fa7-a801-9f4d-75d65cd77625
Version Independent ID: 86a66791-11bb-4f20-f77d-42fe58f5dcf4
Content: Install the Azure Monitor agent - Azure Monitor
Content Source: articles/azure-monitor/agents/azure-monitor-agent-install.md
Service: azure-monitor
Sub-service: agents
GitHub Login: @bwren
Microsoft Alias: bwren

@tricksterisback Thank you for bringing this to our notice, we will review it further and update the document accordingly.

@tricksterisback Thanks again for bringing this to our notice and helping us improve our Azure documentation. I have raised a PR to update the document. Once the PR is reviewed and approved , changes would go live.
At this point it appears that there's no further edits or updates needed to the documentation, other than what has been listed above. We will go ahead and close this issue for now, however if you have any further feedback on the document please tag us in your reply and will be happy to reopen the thread and continue the conversation. Thank you


Refactor/state tree

In this PR the global state tree gets refactored into namespaced modules.
Since we have three components managing their state via the store it got a bit crowded and hard to read.

I really like the refactoring and think it makes a lot of sense to split it up in this way. Just added some thoughts on possible modifications that could be useful in the long run.