why BLUE  difference between evaluate and valid  in WMT14 translation in transformer

❓ Questions and Help
Before asking:

search the issues.
search the docs.

What is your question?
as the title,valid up to 27.7 but evaluate only 25
Code
Download and prepare the data
cd examples/translation/
bash prepare-wmt14en2de.sh --icml17
cd ../..
Binarize the dataset
TEXT=examples/translation/wmt17_en_de
fairseq-preprocess
--source-lang en --target-lang de
--trainpref $TEXT/train --validpref $TEXT/valid --testpref $TEXT/test
--destdir data-bin/wmt17_en_de --thresholdtgt 0 --thresholdsrc 0
--workers 20
Train the model
PYTHONIOENCODING=utf-8  fairseq-train
data-bin/wmt17_en_de
--arch transformer_wmt_en_de --share-decoder-input-output-embed
--optimizer adam --adam-betas '(0.9, 0.98)' --clip-norm 0.0
--lr 5e-4 --lr-scheduler inverse_sqrt --warmup-updates 4000
--dropout 0.3 --weight-decay 0.0001
--criterion label_smoothed_cross_entropy --label-smoothing 0.1
--max-tokens 4096
--max-tokens-valid 4096
--update-freq 1
--eval-bleu
--eval-bleu-args '{"beam": 5, "max_len_a": 1.2, "max_len_b": 10}'
--eval-bleu-detok moses
--eval-bleu-remove-bpe
--eval-bleu-print-samples
--best-checkpoint-metric bleu --maximize-best-checkpoint-metric
--save-dir checkpoints/wmt17_en_de/transformer/ckpt
--log-format json
--keep-last-epochs 5
--max-epoch 30
--fp16
| tee checkpoints/wmt17_en_de/transformer/train.log
Evaluate
PYTHONIOENCODING=utf-8 fairseq-generate data-bin/wmt17_en_de
--path checkpoints/wmt17_en_de/transformer/ckpt/checkpoint_avg_last_5.pt
--batch-size 128 --beam 5 --remove-bpe
| tee checkpoints/wmt17_en_de/transformer/evaluate/evaluate.log

What have you tried?
i had try to add --scoring sacrebleu,but BLUE a littlt up
What's your environment?

fairseq Version (e.g., 1.0 or main):main
PyTorch Version (e.g., 1.0)1.11.0+cu113
OS (e.g., Linux):Linux
How you installed fairseq (pip, source):source
Build command you used (if compiling from source):
Python version:3.8
CUDA/cuDNN version:11.3
GPU models and configuration:
Any other relevant information: the problem did not appear in IWSLT'14

I guess you have to give the same arguments around inferencing, says --max-len-a 1.2 --max-len-b 10 (it is given in train, but not generate)
In addition, was it because you used a slightly different checkpoint? checkpoints/wmt17_en_de/transformer/ckpt/checkpoint_avg_last_5.pt looks like an averaged one not the exact valid one.

I guess you have to give the same arguments around inferencing, says --max-len-a 1.2 --max-len-b 10 (it is given in train, but not generate)
In addition, was it because you used a slightly different checkpoint? checkpoints/wmt17_en_de/transformer/ckpt/checkpoint_avg_last_5.pt looks like an averaged one not the exact valid one.

thank,after i try, adding --max-len-a 1.2 --max-len-b 10 did not get any change.
second,I also try best or last ,but  did not get any change.

Would you mind do a test for me? I guess I found the reason.
fairseq-train's eval-bleu is using sacrebleu, you can find it in fairseq/tasks/translation.py def _inference_with_bleu around line 463~498(the end of .py)
Fortunately, from the comment starts at line 470~ it says,

The default unknown string in fairseq is <unk>, but
this is tokenized by sacrebleu as < unk >, inflating
BLEU scores. Instead, we use a somewhat more verbose
alternative that is unlikely to appear in the real
reference, but doesn't get split into multiple tokens.

and as an alternative, fairseq replaces <unk> with  UNKNOWNTOKENINHYP.
On the other hand, fairseq-generate --scoring sacrebleu means sacrebleu but there is no replacement code found in either fairseq_cli/generate.py nor fairseq/scoring/bleu.py.
So I want you to do a test for me:
search dict.string( in generate.py and you can find 2 places.
give the src_dict one unk_string="UNKNOWNTOKENINHYP" and the tgt_dict one unk_string="UNKNOWNTOKENINREF"
run the generation again.
Please let me know if you do it and it works or not.
 There is no change at all? or do you mean the number still not fit?
It is very unlikely for a socre be the same for different checkpoints.

Would you mind do a test for me? I guess I found the reason. fairseq-train's eval-bleu is using sacrebleu, you can find it in fairseq/tasks/translation.py def _inference_with_bleu around line 463~498(the end of .py) Fortunately, from the comment starts at line 470~ it says,

The default unknown string in fairseq is <unk>, but
this is tokenized by sacrebleu as < unk >, inflating
BLEU scores. Instead, we use a somewhat more verbose
alternative that is unlikely to appear in the real
reference, but doesn't get split into multiple tokens.

and as an alternative, fairseq replaces <unk> with UNKNOWNTOKENINHYP.
On the other hand, fairseq-generate --scoring sacrebleu means sacrebleu but there is no replacement code found in either fairseq_cli/generate.py nor fairseq/scoring/bleu.py.
So I want you to do 2 test for me:

there is a --replace-unk argument, test it in generate.py. This may not work as the code flow is changed.
search dict.string( in fairseq_cli/generate.py and you can find 2 places.
give the src_dict one unk_string="UNKNOWNTOKENINHYP" and the tgt_dict one unk_string="UNKNOWNTOKENINREF"
run the generation again.

Please let me know if you do it and it works or not.
 There is no change at all? or do you mean the number still not fit? It is very unlikely for a socre be the same for different checkpoints.
I total add -replace-unk --dataset-impl=raw --source-lang en --target-lang de  in fairseq-generate

AssertionError: --replace-unk requires a raw text dataset (--dataset-impl=raw)
FileNotFoundError: Dataset not found: test (data-bin/wmt14_en_de)
Exception: Could not infer language pair, please provide it explicitly ( --source-lang en --target-lang de)
FileNotFoundError: Dataset not found: test (data-bin/wmt14_en_de)
data-bin/wmt14_en_de is below

and ...I dont know why test is not test.en or test.de
should i prepare data again by any Command?
sorry,there is change a litte ,but it is far from 27
thank

Leave that --replace-unk alone, it is not meant to be used in the document any way.
Do the 2 is okay.

Leave that --replace-unk alone, it is not meant to be used in the document any way.
Do the 2 is okay.

only give —replace-unk will get this error
AssertionError: --replace-unk requires a raw text dataset (--dataset-impl=raw)

@tjshu  What is the situation now?
Have you tried the following?

search dict.string( in fairseq_cli/generate.py and you can find 2 places.
give the src_dict one unk_string="UNKNOWNTOKENINHYP" and the tgt_dict one unk_string="UNKNOWNTOKENINREF"
run the generation again.

--replace-unk is not needed as it is asked in fairseq-preprocess. The 2nd fix I mentioned do not need this as well.

I have tried 2nd,but no any change.
I guess that I get valid blue 27.XX too low
In evaluate ,it may get a little low than valid blue 27.XX ,so should I train a model better than 28 or 28.5 ?
The key problem is in here?
Thank you

@tjshu What is the situation now? Have you tried the following?

search dict.string( in fairseq_cli/generate.py and you can find 2 places.
give the src_dict one unk_string="UNKNOWNTOKENINHYP" and the tgt_dict one unk_string="UNKNOWNTOKENINREF"
run the generation again.

--replace-unk is not needed as it is asked in fairseq-preprocess. The 2nd fix I mentioned do not need this as well.

I have tried 2nd,but no any change.
I guess that I get valid blue 27.XX too low
In evaluate ,it may get a little low than valid blue 27.XX ,so should I train a model better than 28 or 28.5 ?
The key problem is in here?
Thank you

Thanks for telling me, I guess I may look into this difference in bleu score.
Though at the fastest pace, the debug will be at the end of this week.
It is up to you to decide how much training is the best. Higher score is always appealing.
Well, if the evaluation changes from the training result without a reason, that is a must-solve problem.

Thanks for telling me, I may look into this difference in bleu score. Though at the fastest pace, the debug will be at the end of this week.
It is up to you to decide how much training is the best. Higher score is always appealing. Well, if the evaluation changes from the training result without a reason, that is a must-solve problem.

Can I ask you how difference between in valid and evaluate when you train?
Because I did not success any time, l don’t known how is normal.
why I guess this is key problem is that my classmate tell me valid too low.
thank you

I do not get your question.
If no --eval-bleu, valid loss comes from the criterion (label_smoothed_cross_entropy this time),
cross entropy is calculated by giving target sentences as decoder input to the model. So there is no generation happened.
If --eval-bleu is given, then valid will use inference_step to create hypothesises for calculating sacrebleu.
fairseq-generate uses the same inference to create hypothesises as well.
So there is no difference in model generation.
The only difference is score calculation.

I do not get your question.
If no --eval-bleu, valid loss comes from the criterion (label_smoothed_cross_entropy this time), cross entropy is calculated by giving target sentences as decoder input to the model. So there is no generation happened. If --eval-bleu is given, then valid will use inference_step to create hypothesises for calculating sacrebleu.
fairseq-generate uses the same inference to create hypothesises as well.
So there is no difference in model generation. The only difference is score calculation.

Sorry,
Can I ask you How big is the BLUE gap between in valid and evaluate when you train?
a little or no?


fix WrapPanel issue #3165 item width/height should trigger new measure

What does the pull request do?

WrapPanel trigger measure after item width/height changed
What is the current behavior?

it doesn't
What is the updated/expected behavior with this PR?

fix it
How was the solution implemented (if it's not obvious)?

Checklist

[x] Added unit tests (if possible)?
[ ] Added XML documentation to any related classes?
[ ] Consider submitting a PR to https://github.com/AvaloniaUI/Avaloniaui.net with user documentation

Breaking changes

Nope
Fixed issues

FIxes #3165

Can we add unit test for this to prevent future regressions?

Does this fix #3028?

Does this fix #3028?

i don't think so


Portal: remove header submission extrinsic from protal

Item Type
Task
Description
To simplify the type encodings, move the FV header submission away from portal and expose in the respective FV. This will make client-side type encodings much simple and saves us a couple of decoding steps.

[ ] reexpose extrinsic in FV pallet
[ ] expose and rename FV types
[ ] update CLI and eventually ranger to support the changes

Additional Information
No response
Acceptance Criteria
As a ranger, I am now able to submit the headers directly to the FV pallet.
What are the points assigned to this item?
None
Is the issue ready?

[X] This issue is ready

1


Less filter doesn't work, works from the command line and command assetic:dump?!

Quick and dirty check, stopping the process (node <script>) right after line 246 of Process.php:
$this->process = proc_open($commandline, $descriptors, $this->processPipes->pipes, $this->cwd, $this->env, $this->options);
var_dump($commandline, $this->env); die();

Output:
string(41) "'/usr/bin/node' '/tmp/assetic_less5LcIFK'"
array(41) {
  ["NODE_PATH"]=>
  string(22) "/usr/lib/node_modules/"
  ["PATH"]=>
  string(28) "/usr/local/bin:/usr/bin:/bin"

Assetic configuration:
assetic:
    use_controller: false
    node:           /usr/bin/node
    filters:
        less:
            node_paths: [/usr/lib/node_modules/]

Less filter does't work. Gives me a generic error "The process has been signaled with signal 11" (inside the CSS file). If I use the same temp file from the shell, running on CentOS 6.4 x64:
export NODE_PATH=/usr/lib/node_modules/
node /tmp/assetic_less5LcIFK

It works without problems, outputs the actual CSS complied output. Also the command php app/console assetic:dump works fine. The problem occurs when executing from the browser, i.e. www.mydomain.com/app_dev.php/test

Signal 11 means that you have a segmentation fault. You should check your server's configuration.


Very poor user experience on touchscreens

Describe the Bug
User experience on touchscreens is very bad, especially compared to alternative libraries like Rete.js.

Edge connection does not work, edge connector hit box is very small
Edge connection dragging and updating does not work well, the rest of the frame tend fo pan/scroll when attempting to update node edge on iPad
Drag and drop example requires long press and hold to activate drag functionality on touchscreens
Drag and drop example pages scrolls too much and doesn’t reliable trigger drag and drop

Your Example Website or App
https://reactflow.dev/examples/updatable-edge/
https://reactflow.dev/examples/drag-and-drop/
Steps to Reproduce the Bug or Issue
N/A
Tested with the examples on the official documentation website
Expected behavior
Edge connections should be able to easily connect and disconnect on mobile. Edge connector should have a larger hit box for fingers. See:
https://rete.js.org/#/examples/basic
Drag and drop UX needs to be more responsive and sensitive, page shouldn’t scroll when attempting to drag on touchscreens. A better implementation:
https://shopify.github.io/draggable/examples/simple-list.html
Screenshots or Videos
No response
Platform
Tested on iOS 15, Safari/WebKit
Additional context
Retejs has excellent touchscreen support for the edge connections, just copy what they are doing. For drag and drop, the behaviour needs to be revamped, it is very awkward to use right now on touchscreen.

Mobile is available in the next release: https://github.com/wbkd/react-flow/discussions/1677#discussioncomment-1833493

Hey @Immortalin
In v9 there is no support for touch devices at all.
To your points:

Edge connection does not work, edge connector hit box is very small - this is fixed in v10 and the edge connector hit box is adjustable via css
Edge connection dragging and updating does not work well, the rest of the frame tend fo pan/scroll when attempting to update node edge on iPad - there is currently no support for this specific feature for touch devices
Drag and drop example requires long press and hold to activate drag functionality on touchscreens - this has nothing to do with React Flow. It's a simple example that uses the native HTML5 drag and drop API. Of course you can use a library that does a better job in your application
Drag and drop example pages scrolls too much and doesn’t reliable trigger drag and drop - see above

Are there any plans to add support for updating edge connections on touchscreens?

Edge connection

me too , I met same problem.


Generate Swagger documentation

You can compile this either after https://github.com/zkFold/zkfold-base/pull/138 gets merged or by changing a path to you local repo of zkfold-base in cabal.project.

@Vardominator read the message above: https://github.com/zkFold/zkfold-prover-api/pull/1#issue-2353149596


support html past (e.g., jupyter notebook, QUIP)

Hi Ganessh,
Really appreciate it that you have created this awesome plugin. Personally, I work with some tools (e.g., jupyter notebook, QUIP) that doesn't have very good raw text when copying tables, so to get proper table content, I need to refer to the html paste.
Here is a draft diff that solves my problem and I hope is can also help other who have similar issues.
Best Regards

Here are some example raw text I got for your reference:
from quip
\nCOL_NAME_A\t\nCOL_NAME_B\n\nCONTENT_A\t\nCONTENT_B\n
from bento notebook
COL_NAME_A\nCOL_NAME_B\nCONTENT_A\nCONTENT_B


Add: Read-modify-write (RMW) module

Read-modify-write adapter for byte-wise read and write accesses which addresses #152 . For byte-wise read accesses, the adapter just returns the masked data. For byte-wise write accesses, the adapter stalls the original request while performing a full-width read access followed by a masked modify and full-width write
The input and of the module consist of the following signals (the output signals are mirrored)
   // Request-side channel
   input logic  mem_req_i,
   output logic mem_gnt_o,
   input        addr_t mem_addr_i,
   input        data_t mem_wdata_i,
   input        strb_t mem_strb_i,
   input logic  mem_we_i,
   output logic mem_rvalid_o,
   output       data_t mem_rdata_o

The protocol currently takes the following assumptions:

A valid handshake occurs when req and gnt are high.
The data is read/written one cycle after a valid handshake and the rvalid signal is high for both read/write requests
A gnt is raised at the earliest one cycle after the req is raised

Open questions:

Are the protocol assumptions correct?
Naming and location etc.: the module currently has its own folder ip/spm_interface. Could probably be placed somewhere else and maybe named differently. The interface is currently only used for testing purposes
Which license header to use?

What I actually wanted to say is that you can simplify the FSM a bit when not considering partial reads (as indicated by the code comment) - I am expecting that this should very much simplify the FSM. If you want to keep the two FSMs separately that is okay by me but you could also make it one - however you like 😄

I have actually discovered another protocol violation. mem_ready_o should not be asserted in the RMW_READ state but it should be delayed until the mem_ready_i is asserted in the RMW_MODIFY_WRITE state. Otherwise we lose the address.


Outer Spike on Sunburst based on hit count

When visualizing API endpoint usage data, it would be useful to show which endpoints are accessed most frequently.
This could be visualized by drawing the height of the endpoint color bar, in proportion to amount of API hits.

Closing due to staleness, and change in direction for sunburst visualization.


Dsd 470/chakra hero

This is the same as PR #685 except it's pointing to the right dev branch (chakra-phase2).
How has this been tested?

Checklist:

[ ] I have updated the Storybook documentation accordingly.
[ ] All new and existing tests passed.

Front End Review:

[ ] View the example in Storybook

Tugboat has finished building the preview for this pull request!
Link:

https://pr693-osflfnnlrjzxgxuvfn1gp8pv5i8zxdcw.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6151d5234807c0b0503c599f


'Signature is invalid' error when logging out

I'm trying to get logging out to work and I get a Signature invalid error.
There is a signature in the XML of the service provider metadata, but the XML file doesn't seem to be loaded at all.
This is relevant to Issue #71 where the metadata persister is never called, hence the settings are never cached.
I tried to fix this manually but I run into several issues, mainly to do with the metadata_persister example method that's provided in the config file:

File.open Rails.root.join("cache/saml/metadata/#{fname}"), "wb" throws an error about the file being non existent
settings.to_h (where settings is an IncomingMetadata object) throws an error too.

Is there any workaround to this? How did anyone else get logging out to work?

@thanos982
Thanks for your cooperation for this gem. I need to clarify what is your expected result.
I understand that following situation from your description, If you think I have misunderstanding, please feel free to fix.

You have XML metadata file of SP.
And you are trying todo SLO (single logout).
And you already have SP configuration like mentioned in our README and Wiki.
And you are expecting that load your XML file and configure SP config for your SP service?

If it's possible can you share with us your SP config hash in here. I think if you do mask for  your secret information might allow you or your team to share your SP config in here.

Thank you Zogoo.
I;m still not sure how and when the metadata_persister method used but I figured out that the URL of the metadata file in my SP config was wrong, that's why I couldn't get it to work.

@thanos982
Personally, I will not suggest to use SP metadata persister if your SP is a 3rd party service or communication is over internet.
Or also your SP doesn't change  the metadata content so often.
Because, SP metadata content from URL might be dangerous  especially if your SP metadata URL not protected any authentication.
I would suggest to use RAW xml data and parse with SamlIdp::IncomingMetadata.new(sp_raw_metadata).


Update API documentation for Filtered

Here is the preview link: https://review.docs.microsoft.com/en-us/qsharp/api/qsharp/microsoft.quantum.arrays.filtered?view=qsharp-preview&branch=pr-en-us-707

@KittyYeungQ: It looks like the /// # Examples section of the API documentation comment is still not attached to the Filtered function, but appears later in the file? At least on my system, that's causing the generated YAML file to exclude your changes such that I'm not getting the same output as previewed in MicrosoftDocs/quantum-docs-pr#707.
### YamlMime:QSharpType
uid: microsoft.quantum.arrays.filtered
name: Filtered
type: function
namespace: Microsoft.Quantum.Arrays
summary: |-
  Given an array and a predicate that is defined
  for the elements of the array, returns an array that consists of
  those elements that satisfy the predicate.
remarks: |-
  The function is defined for generic types, i.e., whenever we have
  an array `'T[]` and a predicate `'T -> Bool` we can filter elements.
syntax: "function Filtered (predicate : ('T -> Bool), array : 'T[]) : 'T[]"
input:
  content: "(predicate : ('T -> Bool), array : 'T[])"
  types:
  - name: predicate
    summary: A function from `'T` to Boolean that is used to filter elements.
    isFunction: true
    input:
      types:
      - uid: "'T"
        isLocal: true
    output:
      types:
      - isPrimitive: true
        uid: Bool
  - name: array
    summary: An array of elements over `'T`.
    isArray: true
    uid: "'T"
    isLocal: true
output:
  content: "'T[]"
  types:
  - summary: An array `'T[]` of elements that satisfy the predicate.
    isArray: true
    uid: "'T"
    isLocal: true
typeParameters:
- uid: "'T"
  summary: The type of `array` elements.
...


Merge Scenes

All the assets look really good. I really like the randomised grass.
I think the water and lilypad movement from the earlier versions would still be good though.
The only really major issue is that subsequent out of bounds resets have gotten bugged out somehow. I haven't had a look at it, but it could be the takeover timeout coroutine.


[tool_crash]: _TypeError: type 'String' is not a subtype of type 'bool?' in type cast when bulding for iOS

Oops; flutter has exited unexpectedly: "type 'String' is not a subtype of type 'bool?' in type cast".
 flutter build ios --flavor dev -t lib/main_dev.dart
Building com.xxx.dev for device (ios-release)...
Automatically signing iOS for device deployment using specified development team in Xcode project: xxx
Running Xcode build...
 └─Compiling, linking and signing...                         7.0s
Xcode build done.                                           32.3s
Built /,../build/ios/iphoneos/Runner.app.

Oops; flutter has exited unexpectedly: "type 'String' is not a subtype of type 'bool?' in type cast".
A crash report has been written to /.../flutter_01.log

Expected results
.ipa file should be generated
Actual results
Oops; flutter has exited unexpectedly: "type 'String' is not a subtype of type 'bool?' in type cast".
Code sample
Fails with
flutter build ios --flavor dev -t lib/main_dev.dart or  flutter build ios
or
flutter build ipa --flavor dev -t lib/main_dev.dart --export-method=ad-hoc --build-name=$version_number --build-number=$build_number
$ flutter build ipa -v --flavor dev -t lib/main_dev.dart --export-method=ad-hoc > output.txt
[        ] Oops; flutter has exited unexpectedly: "type 'String' is not a subtype of type 'bool?' in type cast".
[  +26 ms] A crash report has been written to /Users/daksh-gargas/Documents/GitHub/wildr/in-progress-mobile/wildr_flutter/flutter_01.log

output.txt
flutter_01.log
Flutter Doctor output
Doctor output
[✓] Flutter (Channel stable, 3.19.4, on macOS 14.4 23E214 darwin-arm64, locale en-US)
    • Flutter version 3.19.4 on channel stable at /Users/daksh-gargas/.asdf/installs/flutter/3.19.4
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 68bfaea224 (5 days ago), 2024-03-20 15:36:31 -0700
    • Engine revision a5c24f538d
    • Dart version 3.3.2
    • DevTools version 2.31.1

[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    • Android SDK at /Users/daksh-gargas/dev/Android/sdk
    • Platform android-34, build-tools 34.0.0
    • ANDROID_HOME = /Users/daksh-gargas/dev/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.9+0-17.0.9b1087.7-11185874)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 15.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 15E204a
    • CocoaPods version 1.15.2

[!] Android Studio (version unknown)
    • Android Studio at /Applications/Android Studio Preview.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    ✗ Unable to determine Android Studio version.
    • Java version OpenJDK Runtime Environment (build 17.0.10+0-17.0.10b1087.17-11446219)

[✓] Android Studio (version 2023.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.9+0-17.0.9b1087.7-11185874)

[✓] IntelliJ IDEA Ultimate Edition (version 2023.3.5)
    • IntelliJ at /Applications/IntelliJ IDEA.app
    • Flutter plugin version 78.3.1
    • Dart plugin version 233.14888

[✓] VS Code (version 1.87.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.84.0

[✓] Connected device (3 available)
    • Taco 12 mini (mobile)             • 00008101-000839661100001E            • ios          • iOS 17.4 21E219
    • iphone 15 pro with creds (mobile) • C9744625-6C63-4DA5-9342-6D1EA7D70645 • ios          • com.apple.CoreSimulator.SimRuntime.iOS-17-2 (simulator)
    • macOS (desktop)                   • macos                                • darwin-arm64 • macOS 14.4 23E214 darwin-arm64

[✓] Network resources
    • All expected network resources are available.

! Doctor found issues in 1 category.

P.S.
Was successfully able to generate the .ipa file from Xcode

Hi @daksh-gargas, please provide the crash file flutter_04.log.
Please also share the full verbose output of the command that you run. The output may be huge so kindly put it into a .txt file and attach it here.
Thank you

Hi @daksh-gargas, please provide the crash file flutter_04.log.
Please also share the full verbose output of the command that you run. The output may be huge so kindly put it into a .txt file and attach it here.
Thank you

@danagbemava-nc  Done

Hi @daksh-gargas, can you also share the content of your Info.plist file?
Also, looking at your logs, it seems like the archive is successfully built, the tool crash just happens to happen after the archive is built.
            ** ARCHIVE SUCCEEDED **
[ +168 ms]  └─Compiling, linking and signing... (completed in 12.3s)
[        ] Xcode archive done.

Hi @daksh-gargas, can you also share the content of your Info.plist file?
Also, looking at your logs, it seems like the archive is successfully built, the tool crash just happens to happen after the archive is built.
            ** ARCHIVE SUCCEEDED **
[ +168 ms]  └─Compiling, linking and signing... (completed in 12.3s)
[        ] Xcode archive done.

 Full crash report pasted below. From the logs shared above it seems like the crash happens after the archive has been built. I checked the logs and it seemed like most of the plist files the tool tried to read were parsed successfully, so I'm not sure why the crash is happening

Flutter crash report.
Please report a bug at https://github.com/flutter/flutter/issues.
command
flutter build ipa -v --flavor dev -t lib/main_dev.dart --export-method=ad-hoc
exception
_TypeError: type 'String' is not a subtype of type 'bool?' in type cast
#0      PlistParser.getValueFromFile (package:flutter_tools/src/ios/plist_parser.dart:178:24)
#1      _BuildIOSSubCommand.runCommand (package:flutter_tools/src/commands/build_ios.dart:746:57)
<asynchronous suspension>
#2      BuildIOSArchiveCommand.runCommand (package:flutter_tools/src/commands/build_ios.dart:425:50)
<asynchronous suspension>
#3      FlutterCommand.run.<anonymous closure> (package:flutter_tools/src/runner/flutter_command.dart:1389:27)
<asynchronous suspension>
#4      AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:153:19)
<asynchronous suspension>
#5      CommandRunner.runCommand (package:args/command_runner.dart:212:13)
<asynchronous suspension>
#6      FlutterCommandRunner.runCommand.<anonymous closure> (package:flutter_tools/src/runner/flutter_command_runner.dart:355:9)
<asynchronous suspension>
#7      AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:153:19)
<asynchronous suspension>
#8      FlutterCommandRunner.runCommand (package:flutter_tools/src/runner/flutter_command_runner.dart:295:5)
<asynchronous suspension>
#9      run.<anonymous closure>.<anonymous closure> (package:flutter_tools/runner.dart:119:9)
<asynchronous suspension>
#10     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:153:19)
<asynchronous suspension>
#11     main (package:flutter_tools/executable.dart:90:3)
<asynchronous suspension>

flutter doctor
[✓] Flutter (Channel stable, 3.19.4, on macOS 14.4 23E214 darwin-arm64, locale en-US)
    • Flutter version 3.19.4 on channel stable at /Users/daksh-gargas/.asdf/installs/flutter/3.19.4
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 68bfaea224 (6 days ago), 2024-03-20 15:36:31 -0700
    • Engine revision a5c24f538d
    • Dart version 3.3.2
    • DevTools version 2.31.1

[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    • Android SDK at /Users/daksh-gargas/dev/Android/sdk
    • Platform android-34, build-tools 34.0.0
    • ANDROID_HOME = /Users/daksh-gargas/dev/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.9+0-17.0.9b1087.7-11185874)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 15.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 15E204a
    • CocoaPods version 1.15.2

[!] Android Studio (version unknown)
    • Android Studio at /Applications/Android Studio Preview.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    ✗ Unable to determine Android Studio version.
    • Java version OpenJDK Runtime Environment (build 17.0.10+0-17.0.10b1087.17-11446219)

[✓] Android Studio (version 2023.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.9+0-17.0.9b1087.7-11185874)

[✓] IntelliJ IDEA Ultimate Edition (version 2023.3.5)
    • IntelliJ at /Applications/IntelliJ IDEA.app
    • Flutter plugin version 78.3.1
    • Dart plugin version 233.14888

[✓] VS Code (version 1.87.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.84.0

[✓] Connected device (2 available)
    • Taco 12 mini (mobile) • 00008101-000839661100001E • ios          • iOS 17.4 21E219
    • macOS (desktop)       • macos                     • darwin-arm64 • macOS 14.4 23E214 darwin-arm64

[✓] Network resources
    • All expected network resources are available.

! Doctor found issues in 1 category.

Hi, any updates on this?
This is really hurting our CI/CD too..
We use fltuter build ipa to share the .ipa files with our team.
cc @danagbemava-nc

Closing this as a duplicate of https://github.com/flutter/flutter/issues/138465. @daksh-gargas if you can share your Info.plist file on that issue, it would help us to investigate this.

@daksh-gargas I just noticed that like you I had FLTEnableImpeller set as string. According to docs now it's boolean. Setting it as boolean fixed CI pipeline issue.
Don't know when Flutter team decided to change it and if was it announced in release notes (can't see it). If no its such a shame

@daksh-gargas I just noticed that like you I had FLTEnableImpeller set as string. According to docs now it's boolean. Setting it as boolean fixed CI pipeline issue.
Don't know when Flutter team decided to change it and if was it announced in release notes (can't see it). If no its such a shame

@Chojecki thank you so much for that response.
Let me try it :D


Adopter Fosterer Dashboard: add fostered pets resource

If you log in as an adopter and go to the dashboard and click on adopted pets, you will see the adopted pets, and you can then click on two tabs to show the files and incomplete tasks.
We need to copy this implementation for fosterers, so they can do the same for their fostered pets. The fosterer should be able to go to their dashboard, see a link that says 'Fosters', click it, and see tiles for each dog currently in foster, and then click a tile to see that dog's files and incomplete tasks. This link should not be visible to users that are adopters only.
For reference, this is for pets with aMatch where the person_id matches that of the fosterer user, and the Match has a match_type of foster and it is a current match.
Implementation suggestions

a new Organizations::AdopterFosterer::FosteredPetsController and route to render the correct collection of fostered pets
re-use the same policy
re-use the same resources and implementation of these resources as the adopted pets flow
if you see opportunities to reduce duplication in the view, feel free to make shared partials that can live in Organizations::AdopterFosterer::Shared

@sarvaiyanidhi FYI this issue is up and very similar to what you just worked on, if you are interested :)

Sure @kasugaijin I would love to work on it.. Can you please assign it to me?

@sarvaiyanidhi all yours!


Analyze Usability #2: Include BOM Timestamp and Serial Number

Analyze output includes BOM name and version, resolving #78.  Example:
Analysis results for<EMAIL_ADDRESS>
Components with multiple versions:

commons-codec:commons-codec versions: 1.15 1.3
commons-io:commons-io versions: 2.8.0 2.4

It would be useful for the output to also include BOM  timestamp and serialNumber.
Use Case:  inclusion of output into a Slack DM, email, or GitHub PR review comment where the timestamp for the BOM generation can be very different from (say) the PR comment timestamp but very relevant to commit timestamps.

I also added BOM version to the output.
Available in v0.16.0


[otbn] Would it make sense to split bn.mulqacc into several different instructions?

The current syntax for mulqacc is this:
      BN.MULQACC [<wb_variant>][<zero_acc>] [<wrd><wrd_hwsel>,] <wrs1>.<wrs1_qwsel>, <wrs2>.<wrs2_qwsel>, <acc_shift_imm>

The <wrd> argument is required if and only if <wb_variant> is specified. This is a bit complicated. Would it make more sense to define one opcode for when writeback is enabled and one for when it's not? (This would not have any effect on the encoding or the hardware; just on assembly syntax).

@GregAC: I know you specified this in the first place. Would this split make sense to you?
@felixmiller, @wallento

Mentally I think I had seen it as three different instructions anyway BN.MULQACC BN.MULQACC.SO BN.MULQACC.WO
Perhaps we just need a documentation tweak so rather than having a [<wb_variant>] field we just list three different instruction mnemonics along with the current description with the appropriate tweaks? Preferably we don't want to replicate the rest of the instruction description three times.

Cool, sounds sensible to me. I'll try a documentation patch now.

I don't really have a preference here, @rswarbrick proposal lgtm and is probably a bit better readable on the asm level

Also, the <wrd_hwsel> argument is only needed for the .SO variant not for the .WO variant, right?


Code editor improvement: code snippets / live templates

That might be quite handful. See example: Live templates in PyCharm

Feature and improvement proposals for the Godot Engine are now being discussed and reviewed in a dedicated Godot Improvement Proposals (GIP) (godotengine/godot-proposals) issue tracker. The GIP tracker has a detailed issue template designed so that proposals include all the relevant information to start a productive discussion and help the community assess the validity of the proposal for the engine.
The main (godotengine/godot) tracker is now solely dedicated to bug reports and Pull Requests, enabling contributors to have a better focus on bug fixing work. Therefore, we are now closing all older feature proposals on the main issue tracker.
If you are interested in this feature proposal, please open a new proposal on the GIP tracker following the given issue template (after checking that it doesn't exist already). Be sure to reference this closed issue if it includes any relevant discussion (which you are also encouraged to summarize in the new proposal). Thanks in advance!


Prevent flickering in nushell due to FTCS marks

Tl;dr: Conpty would flush a frame whenever it encountered a FTCS mark. Combine that with the whole-line redrawing that nushell does, and the Terminal would get the prompt in two frames instead of	one, causing a slight flickering. This fixes that by rendering the frame, but not flushing to the pipe when we encounter one of these sequences.
Closes #13710
A complication here: there are some sequences that we passthrough immediately when we encounter them. For example, \x1b[ 2q. we need to also not flush when we encounter one of these sequences. nushell emits one of these as a part of the prompt, and that would force the buffered frame to get written anyways, before writing that to the pipe.


Issue when running in GPU

Hi,
Thank you for this code :). However, when i run it on a GPU i get the following error
018-10-04 11:02:34.458511: E tensorflow/stream_executor/cuda/cuda_driver.cc:806] failed to allocate 2.5K (2560 bytes) from device: CUDA_ERROR_OUT_OF_MEMORY: out of memory
2018-10-04 11:02:34.465377: E tensorflow/stream_executor/cuda/cuda_driver.cc:806] failed to allocate 2.2K (2304 bytes) from device: CUDA_ERROR_OUT_OF_MEMORY: out of memory
Traceback (most recent call last):e: 0 %
File "my-object-detection.py", line 39, in
video(args)
File "/home/ubuntu/object-detection/Object-detection-master/function/video.py", line 99, in video
print("Read frames: %-3i %% -- Write frame: %-3i %%" % (int(countReadFrame/nFrame * 100), int(countWriteFrame/nFrame * 100)), end ='\r')
KeyboardInterrupt
Process ForkPoolWorker-20:

Hello @keyankay ,
Sorry for this late reply ...
In order to use GPU with tensorflow, you shall use another way to install it. For this project I use the CPU tenserflow install process. More information on how to use GPU could be found here:
https://github.com/tensorflow/models/blob/master/research/object_detection/g3doc/installation.md
You may have to modify your local Dockerfile to use GPU tensorflow.
Let me know if you need help.
Bye


Added: Stick to bottom functionality

First pass at solving #41
Two new props:
bottomOffset=0,
bottomSticky=false
If bottomSticky=true, the component will become sticky only once it has
been scrolled above its bottom.
I think this could still use a bit of refinement, as well as some tests, but it is a start, and introduces no breaking changes.

Unless I'm misunderstanding you, this can be handled entirely by topOffset: For example, if my header is 80px high, I would set my topOffset to 80px, and once the bottom of the element reaches the top of the window, it will become sticky.
Or are you talking about something else?

Hey @dbarbalato , I think you might be misunderstanding what I'm trying to do. Basically I'm trying to get an element to become sticky when the bottom of the element reaches the bottom of the window, not the top of the window. I don't believe that functionality can currently be achieved with react-sticky.

Hey @dbarbalato, I hadn't seen your reply to #40. I'll try that out and see if it works. Thanks for the tip!
If it doesn't work, my PR'd solution does seem to be working fine as well.


As user I want to list all images to know which images I can clone

Purpose
A user want to see a list of all images of a certain repository so he knows which images are available and how he can pull these images.
We do not make the get and display of repositories a single story since for me this is not covered with business value.
Subtasks

[ ] Establish authentication between registry and gateway
[ ] GraphQL endpoint to list all repositories (required to enable navigation to images)
[ ] GraphQL endpoint to list all images of a certain repository
[ ] Adapt frontend to load (and display) repositories from server
[ ] Adapt frontend to load (and display) images from the server (per repository)

Some Links

https://hub.docker.com/_/registry
https://docs.docker.com/registry/

The URL for the GraphQL endpoint is http://localhost:5400/graphql. To run execute the query you should run a Redis instance and the docker registry as well (usual development setup).
This is a sample GraphQL request.
{
  repositories {
    name
  }
  tags(repository: "some/other/test") {
    name
    repository {
      name
    }
  }
}


Add version: univrsal.input-overlay version 5.0.3

- [X] Have you signed the Contributor License Agreement?

[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?

[ ] Have you tested your manifest locally with winget install --manifest <path>?
[X] Does your manifest conform to the 1.4 schema?

Microsoft Reviewers: Open in CodeFlow

/azp run

@wingetbot waivers Add Validation-Executable-Error


undo and redo operations

There is one icon for undo and another for redo. I want to perform undo and redo operation when then those icon are clicked

This library doesn't provide any icons, so I guess the problem is in some other piece of code.


Store channel config in the database

Currently, pmxbot stores the list of configured channels (logged and unlogged) in the config. This design requires that the service be restarted to change the config. A !config feature was added which allows the run-time configuration to be mutated, but those changes aren't persisted anywhere. There's also the !log command and !invite commands which take effect only for the currently-running instance.
A better design would be for the channel config to be stored only in the database. A new instance wouldn't listen on any channel, but could be /invited to any suitable channel. The /kick could be used to eject pmxbot or a new command such as !leave could be used to have pmxbot leave a channel. The !log command could similarly be used to enable or disable logging in a given channel. If pmxbot kept in the database the list of channels (logged and unlogged), it would completely obviate the need for a static list in the config. It would also make it trivial for any user to affect the pmxbot presence and logging behavior.
All of this would require persistence support for these config values in both sqlite and mongodb, though the infrastructure already exists to model this support.
To support a smooth transition, the implementation should:
a) load the config first from the database
b) if no config is in the database, use the static config and save it to the database
c) warn if config is present in the database and config (discouraging the possibility of changes to the static config being ignored).

Bitbucket: https://bitbucket.org/yougov/pmxbot/issue/39
Originally reported by: Jason R. Coombs
Originally created at: 2015-02-01T12:56:05.683

Initial draft without any concrete implemnetation. Ref #39.
→ <>

Original comment by: Jason R. Coombs

On further consideration, I've decided not to implement this as a half measure (only storing channel config in the DB), but to expand the scope to store all config in the database. In this way, setting up a new pmxbot instance will be as simple as providing a database URL to the process, and all other configuration and state can be managed through the bot (or possibly through other means).


Support Dev Expressions

babel-plugin-dev-expression helps eliminate development checks in production mode.
For example:
if (__DEV__) {
  console.log('foo');
}

is transformed to
if (process.env.NODE_ENV !== 'production') {
  console.log('foo');
}

klap already uses @rollup/plugin-replace to treeshake the transformed code.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Fixed Inconsistencies between Drive Paths on Windows (C:\ vs c:)

It seems like VS Code or another dependency has begun using lowercase drive names in some places, but not in ${workspaceRoot}
This will make it match up.

Build is failing

Referencing https://github.com/felixfbecker/vscode-php-debug/issues/239

Prettier seems to be printing differently on my machine than in the build environment

Builds fixed, ready for review


remove dictify from state dict

Thanks, @adhami3310, for the quick fix, just confirmed it fixes our issues


Ensure inherent are first

fix https://github.com/paritytech/substrate/issues/6243
fix https://github.com/paritytech/substrate/issues/8144
polkadot companion: https://github.com/paritytech/polkadot/pull/2560
Breaking change:

execute_block now checks that inherents are first.
inherent is any extrinsics, not signed and accepted by one module as inherent (ProvideInherent::is_inherent(call) == true)
module only check inherent for which <$module as ProvideInherent>::is_inherent(call) == true
any validate unsigned implementation which accept an inherent call is invalid as block producer could include them after some non inherents.

Description:
We basically introduce ProvideInherent::is_inherent(call) function and make use of it in impl_outer_inherent.
The implementation consider a signed extrinsic to be not an inherent.
So we can accept calls where ProvideInherent::is_inherent(call) == true and are signed. Those are not inherent and can be valid calls.
(note: we could refuse those, by adding some checker in extra_signed)
We also don't ensure that inherent call are successful.
And we don't ensure that inherent call are unique.
All we do is:

we consider unsigned extrinsic with call where ProvideInherent::is_inherent(call) == true to be inherent
inherent are first
module which requires inherent have at least one inherent (thus unsigned) for which <$module as ProvideInherent>::is_inherent(call) is true.

My general comment is that the inherent / unsigned story I think is not super clean.
It seems that the difference between an inherent tx and an unsigned tx now is whether the module remembers to write the function is_inherent.
Maybe this is as good as it gets, but i would actually expect something a little more clean, and without chance of forgetting to implement such a fine detail.

The compiler forces you to implement is_inherent, as the trait ProvideInherent requires this :P

Keep fuckin with me. Iam disabled and this isn't legal. I will win. I'm
Gods child. It's his battle and he doesn't lose
On Tue, Mar 16, 2021, 3:01 AM Bastian Köcher @.***>
wrote:

My general comment is that the inherent / unsigned story I think is not
super clean.
It seems that the difference between an inherent tx and an unsigned tx now
is whether the module remembers to write the function is_inherent.
Maybe this is as good as it gets, but i would actually expect something a
little more clean, and without chance of forgetting to implement such a
fine detail.
The compiler forces you to implement is_inherent, as the trait
ProvideInherent requires this :P
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/paritytech/substrate/pull/8173#issuecomment-800043234,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARSJH4ZISNYJIO7YAHABMPDTD4F6JANCNFSM4YA3EUJQ
.

 Iam disabled and this isn't legal. I will win. I'm
Gods child. It's his battle and he doesn't lose
On Tue, Mar 16, 2021, 3:01 AM Bastian Köcher @.***>
wrote:

My general comment is that the inherent / unsigned story I think is not
super clean.
It seems that the difference between an inherent tx and an unsigned tx
now is whether the module remembers to write the function is_inherent.
Maybe this is as good as it gets, but i would actually expect something a
little more clean, and without chance of forgetting to implement such a
fine detail.
The compiler forces you to implement is_inherent, as the trait
ProvideInherent requires this :P
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/paritytech/substrate/pull/8173#issuecomment-800043234,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARSJH4ZISNYJIO7YAHABMPDTD4F6JANCNFSM4YA3EUJQ
.

My general comment is that the inherent / unsigned story I think is not super clean.
It seems that the difference between an inherent tx and an unsigned tx now is whether the module remembers to write the function is_inherent.
Maybe this is as good as it gets, but i would actually expect something a little more clean, and without chance of forgetting to implement such a fine detail.

Yes, I also think it needs some documentation somewhere but this is the summary:

an inherent is an unsigned extrinsic, whose call is marked as inherent by one pallet.
non-inherent unsigned extrinsics are unsigned transactions.
signed extrinsic are signed transactions and not inherent.

No inherent should be accepted in ValidateUnsigned::validate_unsigned, offchain worker and must not send inherent too. Otherwise the block producer can include these extrinsics after some non-inherent and the block is invalid.
Though inherent must be accepted in ValidateUnsigned::pre_dispatch.
Maybe we can improve on this with some macro attributes on calls themself so that ppl can't mess themself.

there is no client change, so no burnin.
I guess audit is required considering it is not trivial.

@thiolliere Can you get mergable, and then it seems we are good to go

bot merge


Popover : Check popoverContentNode null before use

Description
Fixes the issue encountered in #5849 (popoverContentNode is null on Firefox)
The relevant js method attempts to access popoverContentNode.classList before a null check is performed on the popoverContentNode object. The null check exists but it happens after this point. I have therefore moved the null check to the correct point.
How Has This Been Tested?
This is already tested in ToolTipTests.cs : RenderContent(bool usingFocusout); the bug was a silent JS error which would not be caught by any C# unit testing, because the final result is still the same (popoverContentNode.Children.Should().BeEmpty();)
Types of changes

[X] Bug fix (non-breaking change which fixes an issue)

Checklist:

[X] The PR is submitted to the correct branch (dev).
[X] My code follows the code style of this project.

https://try.mudblazor.com/snippet/mkmQlPmTTylezExN
I get an error the below error in your example and don't get any other error.
Probably because try already adds the providers.
Can you see if you can strip back the example please.
blazor.webassembly.js:1

       crit: Microsoft.AspNetCore.Components.WebAssembly.Rendering.WebAssemblyRenderer[100]
      Unhandled exception rendering component: Duplicate MudPopoverProvider detected. Please ensure there is only one provider, or disable this warning with PopoverOptions.ThrowOnDuplicateProvider.
System.InvalidOperationException: Duplicate MudPopoverProvider detected. Please ensure there is only one provider, or disable this warning with PopoverOptions.ThrowOnDuplicateProvider.
   at MudBlazor.MudPopoverProvider.OnAfterRenderAsync(Boolean firstRender)
   at Microsoft.AspNetCore.Components.RenderTree.Renderer.GetErrorHandledTask(Task taskToHandle, ComponentState owningComponentState)

Thanks for the PR
https://try.mudblazor.com/snippet/mkmQlPmTTylezExN
I get the below error in your example and don't get any other error. Probably because try already adds the providers. Can you see if you can strip back the example please.
blazor.webassembly.js:1

       crit: Microsoft.AspNetCore.Components.WebAssembly.Rendering.WebAssemblyRenderer[100]
      Unhandled exception rendering component: Duplicate MudPopoverProvider detected. Please ensure there is only one provider, or disable this warning with PopoverOptions.ThrowOnDuplicateProvider.
System.InvalidOperationException: Duplicate MudPopoverProvider detected. Please ensure there is only one provider, or disable this warning with PopoverOptions.ThrowOnDuplicateProvider.
   at MudBlazor.MudPopoverProvider.OnAfterRenderAsync(Boolean firstRender)
   at Microsoft.AspNetCore.Components.RenderTree.Renderer.GetErrorHandledTask(Task taskToHandle, ComponentState owningComponentState)

Sorry, that example wasn't made by me. I was only referencing the issue because it's the same error thrown at the same line of code.
Uncaught TypeError: popoverContentNode is null
MudBlazor.min.js:6:22860

I don't know how to reproduce it. In my case, it was occurring in an application without any direct use of MudPopover. Perhaps it was part of the MudDataGrid component - which I am using in my application - but unfortunately the error isn't occurring for me any more, and I have already made far too many changes to go back and hunt for it.
However, I'm not sure if reproduction is really necessary here. If you inspect the exact line of JS that the error points to, it's clear how a null ref error would occur.

OK makes sense and since this is JS it would be hard to test.
Thanks for the PR 🙏


Delete detected webhooks

I propose that when we detect a webhook that's been posted in the guild, we call DELETE on that URL, so that the webhook is deleted.
This is to protect users against themselves, since there is the chance that their message was scraped before we deleted it, and someone now has that webhook url.
Implementing this would be as simple as calling DELETE on any webhook URLs that we detect.

I am in support of this, but just wanted to add that we should also let the user know that this happened through a message in that channel.
Alternatively or additionally, we could send one message with the webhook that explains what has happened.

I'm against executing the webhook ourselves, but yea we should update the message that gets sent in the channel.

I am in favor of deleting the webhook. We can update our DM message (do note it falls back to being inside the channel if the user has DMs disabled) to say it has been deleted and a new one should be generated.

Our channels are often rather crowded, if we send a message with the webhook they can read the message clearly themselves without scrolling.
It can also prove as a better lesson, "Look, we were able to send this message because you leaked the url!", rather than talking hypothetically.

I'm going to be very against anything other than deleting the webhook and adding information in our normal DM/in-channel message. It's not our responsibility to provide lessons to users about keeping webhooks safe, especially if it's us doing something that's pretty much against ToS.

On top of what's in the original issue description, we should also change the alert that's posted in mod-alerts to include whether the DELETE was successful or not.
i am not sure if this is current behaviour, but we should also run this filter against staff posting webhooks, since a mod may want to delete a webhook found in a grabber script.

It seems we're in agreement on this. I'll approve the issue.

I'd like to try to solve this issue.


Demo cleanup

Remove Sylva-related stuff.
Remove the provisioning network.
Migrate to kubernetes.core.helm instead of plain helm upgrade  commands.

Looks good, thanks!  I've not yet had time to test, but I wanted to check with @ipetrov117 @atanasdinov and @dprodanov4 re the Sylva removal - where should we refer to now for testing Sylva?

Looks good, thanks! I've not yet had time to test, but I wanted to check with @ipetrov117 @atanasdinov and @dprodanov4 re the Sylva removal - where should we refer to now for testing Sylva?

Currently our metal3 is part of the Sylva CI, so for testing on the Sylva side this has us covered. For setting up a testing environment for metal3 + Sylva I have written a doc, which is present in Confluence.
That said, it makes a lot of sense having a one-click deployment option for metal3 + Sylva. Once Sylva release their v0.3.0 version (which should happen this week) we could look at automating the needed steps in order to achieve an easier metal3 + Sylva testing environment deployment (which IMO should be in this repo). I would refrain from trying to automate anything around Sylva until they release the v0.3.0 version, as it would require constant monitoring on whether some new change breaks the automation configuration. For the automation itself, we can use the aforementioned Confluence documentation which outlines the main configuration that needs to be automated.

Isn't there an option to use their CI to test Sylva + our Metal3 ?

Isn't there an option to use their CI to test Sylva + our Metal3 ?

Running Sylva's CI requires for the user to have at least "Developer" permissions. The CI does not work from forks, so even opening a "Draft" MR from a fork would result in the CI failing. An example for this problem can be viewed here and the discussion on the Sylva slack can be viewed here.
Furthermore, Sylva's CI does not offer (at least at this moment) a way to login to the Equinix machine on which you deploy metal3 and go thorough all the deployed resources. For our testing purposes this is not ideal.
IMO it would be good to have an easily deployable Sylva + Metal3 setup on our side and on machines that we can access. That way we significantly faster integrate through what needs to be done for a specific feature and produce a more robust code that can then go through Sylva's CI when an MR is opened. Furthermore, by having such an automated deployment, users that do not have "Developer" permissions on the sylva-core would be able to deploy and test their Sylva related changes.

Looks good, thanks! I've not yet had time to test, but I wanted to check with @ipetrov117 @atanasdinov and @dprodanov4 re the Sylva removal - where should we refer to now for testing Sylva?

Currently our metal3 is part of the Sylva CI, so for testing on the Sylva side this has us covered. For setting up a testing environment for metal3 + Sylva I have written a doc, which is present in Confluence.
That said, it makes a lot of sense having a one-click deployment option for metal3 + Sylva. Once Sylva release their v0.3.0 version (which should happen this week) we could look at automating the needed steps in order to achieve an easier metal3 + Sylva testing environment deployment (which IMO should be in this repo). I would refrain from trying to automate anything around Sylva until they release the v0.3.0 version, as it would require constant monitoring on whether some new change breaks the automation configuration. For the automation itself, we can use the aforementioned Confluence documentation which outlines the main configuration that needs to be automated.

Thanks for the feedback @ipetrov117 - looking at the confluence page it seems at least the VM+Sushy setup is the same as for the demo (we could also probably use the minimal environment for dev-testing?) so it perhaps does make sense to continue enabling a Sylva option here, but if the current integration is broken should we go ahead with this removal and re-add post 0.3.0?
I'm planning to rework the demo automation to make it easier to split the automation into stages, similar to https://github.com/metal3-io/metal3-dev-env
The underlying automation will all be ansible (to enable easy reuse e.g in combination with stack-validation), but we can have several scripts to drive each step of the process e.g:

`01_prepare_host.sh - install packages and do other pre-requisite configuration
02_configure_host.sh - deploy VMs in a configurable way, enable sushy-tools and any other dependencies (such as an image cache)
03_launch_mgmt_cluster.sh - deploy a management cluster in a configurable way (in our case this will be SLEMicro + RKE2 deployed via EIB, although as a first step we can reuse the Leap support)
04_deploy_downstream_cluster.sh - this we'll add to drive the downstream cluster deployment, and we could have an option here to drive the process via our sample manifests or optionally Sylva (or could be a different script)

Does that sound like a reasonable plan? Any suggestions or improvements?

WIP related to my previous comment can be found at https://github.com/hardys/metal3-demo/tree/demo_rework - only the first step completed so far

If somebody had tested the current Sylva steps here and they are working, I can revert it. But if they are not working or we do not need all of them maybe we can accept this change and to implement a new flow with the correct steps once the release of Sylva comes

Looks good, thanks! I've not yet had time to test, but I wanted to check with @ipetrov117 @atanasdinov and @dprodanov4 re the Sylva removal - where should we refer to now for testing Sylva?

Currently our metal3 is part of the Sylva CI, so for testing on the Sylva side this has us covered. For setting up a testing environment for metal3 + Sylva I have written a doc, which is present in Confluence.
That said, it makes a lot of sense having a one-click deployment option for metal3 + Sylva. Once Sylva release their v0.3.0 version (which should happen this week) we could look at automating the needed steps in order to achieve an easier metal3 + Sylva testing environment deployment (which IMO should be in this repo). I would refrain from trying to automate anything around Sylva until they release the v0.3.0 version, as it would require constant monitoring on whether some new change breaks the automation configuration. For the automation itself, we can use the aforementioned Confluence documentation which outlines the main configuration that needs to be automated.

Thanks for the feedback @ipetrov117 - looking at the confluence page it seems at least the VM+Sushy setup is the same as for the demo (we could also probably use the minimal environment for dev-testing?) so it perhaps does make sense to continue enabling a Sylva option here, but if the current integration is broken should we go ahead with this removal and re-add post 0.3.0?
I'm planning to rework the demo automation to make it easier to split the automation into stages, similar to https://github.com/metal3-io/metal3-dev-env
The underlying automation will all be ansible (to enable easy reuse e.g in combination with stack-validation), but we can have several scripts to drive each step of the process e.g:

01_prepare_host.sh - install packages and do other pre-requisite configuration
02_configure_host.sh - deploy VMs in a configurable way, enable sushy-tools and any other dependencies (such as an image cache)
03_launch_mgmt_cluster.sh - deploy a management cluster in a configurable way (in our case this will be SLEMicro + RKE2 deployed via EIB, although as a first step we can reuse the Leap support)
04_deploy_downstream_cluster.sh - this we'll add to drive the downstream cluster deployment, and we could have an option here to drive the process via our sample manifests or optionally Sylva (or could be a different script)

Does that sound like a reasonable plan? Any suggestions or improvements?

For the current Sylva implementation, IMO it would be best to go ahead and remove it. We can re-add the correct automation once Sylva release v0.3.0.
The minimal environment seems also like a good place to do dev testing, I agree.
Regarding the metal3-demo automation rework plan, it sounds awesome! IMO this would significantly decrease the complexity around deploying metal3. Also it would make it easier for people that have been playing with metal3-dev-env to transition to our metal3.

If somebody had tested the current Sylva steps here and they are working, I can revert it. But if they are not working or we do not need all of them maybe we can accept this change and to implement a new flow with the correct steps once the release of Sylva comes

They won't be working, at least with the main branch of sylva-core. IMO it makes sense to remove the current Sylva implementation and re-add the correct flow once Sylva release 0.3.0


Equipment Heavy Armor and Power Armor Filters give 0 results

Describe the bug
When using the compendium browser for equipment, checking the box to filter to Heavy Armor or Power Armor returns 0 results. Light Armor works fine. If all armor is selected, I can see sets of Light Armor and Heavy Armor, so the items are in the compendium, they just don't show up properly in the filter.
To Reproduce
Open the equipment browser, select the check box for either heavy armor or power armor
Expected behavior
Heavy Armor items in the compendium appear
Screenshots
If applicable, add screenshots to help explain your problem.
Technical details (please complete the following information):

OS: Windows 10
Browser: Firefox & Chrome
Foundry Version: 10.291
SFRPG Version: 0.22.1

Already fixed on dev #910


[1.3] Adds support for Symfony 5.0 components

Q
A

Type
improvement

BC Break
no

Fixed issues

Summary
We must return int in execute of symfony console command. null is no longer allowed.
Related to #2115

@alcaeus Is it planned for 1.3 to become compatible with Symfony 5?

Yes, it is. I'l consolidate this with #2115 though.

Thank you for your PR @michaelperrin. We appreciate your contribution. Would you like to take a look at #2115 as help for making mongodb-odm compatible with Symfony 5?


Adds assert messages to std.algorithm.sorting

thanks, sorry for the noise

@burner @thewilsonator please do not use format in assert messages. format expands to a truly epic blizzard of template instantiations, which causes lots of problems with debug and unittest builds. It also causes problems by making problems hard to isolated, due to depending on most of the rest of Phobos.
assert messages should be as lightweight as possible, and should not instantiate templates. sprintf can be used for formatting.


chore(whale-migration): whale sync

What this PR does / why we need it:

Shortens some imports
Synchronises apps/whale/src with whale/src (sitting in https://github.com/JellyfishSDK/whale)

Which issue(s) does this PR fixes?:
Part of #977
Additional comments?:

Based on #1452

Any renaming / refactoring to Jellyfish conventions should be done in a future backwards-compatible PR

To check that the source code is at parity with whale, can roughly follow the steps here https://github.com/JellyfishSDK/jellyfish/pull/1248#issuecomment-1076014532

We should freeze code changes to Whale after this is merged (only allowing critical patches / fixes), then make a staging release to perform some checkouts

Manually diffed directory content changes between jellyfish:apps/whale/src vs whale:src/ and confirm that only:

imports changed
linting: lone blocks removed
linting: error typecasting
linting: export default allowed

whale: src/
jellyfish: apps/whale/src/


界面无法访问

[GIN-debug] [WARNING] Creating an Engine instance with the Logger and Recovery middleware already attached.
[GIN-debug] [WARNING] Running in "debug" mode.  Using port :8080 by default[GIN-debug] Listening and serving HTTP on :8080
[GIN] 2018/10/16 - 14:57:20 | 404 |           1ms |             ::1 | GET      /
[GIN] 2018/10/16 - 14:57:21 | 404 |            0s |             ::1 | GET      /
[GIN] 2018/10/16 - 14:57:22 | 404 |            0s |             ::1 | GET      /
[GIN] 2018/10/16 - 14:57:22 | 404 |           1ms |             ::1 | GET      /
[GIN] 2018/10/16 - 14:57:23 | 404 |            0s |             ::1 | GET      /

你是下载的release版本，还是自己搭建的开发环境，如果是自己搭建的开发环境，请确保前端正常启动
cd fabric-manager/app && npm install && gulp


Can I use the controller type hinting for inject  custom types (classes)?

Hi, I know than I can inject Request, Application and many others  classes in my controller, but currently I wish make something like this

function (Request $request, Silex\Application $app, Helpers $hlp, DB $db)

where DB is a dummy class with static methods right now, but in the future would be something more complex and the DI would be a nice solution, hope you can understand my point, please let me know if you need some clarification, thank you!!.....

In order to do that you should create your own ControllerResolver and the doGetArguments method which can detect other parameter types. Currently only Request and Application are detected.
Then you just need to overwrite the resolver service in the container.
This issue should be closed as it's not related to Silex developement. Please, do not use the issue tracker to ask questions, the support forum is the Silex Tag on Stackoverflow.

@mTorres you're right that this is not Stackoverflow but... let change this issue into feature request for some simple mechanism linke ParamConverters from symfony that allows things requested by cocodrino.

@lukaszwit there is a feature in development in Symfony (see https://github.com/symfony/symfony/pull/18308) to allow hooking into the argument resolving in 3.1 (or 3.2 if it is not ready in time for 3.1, as the feature freeze is in a few days, but it should be OK), which will allow a better implementation than what SensioFrameworkExtraBundle does today for ParamConverter.
Once shipped in Symfony, the feature will be available in Silex (with some changes to allow configuring it of course)

@cocodrino, also using controller's as services can help with this as well because you can setup the Controller via pimple with the needed dependencies.
What more do you want to do with this?

@ragboyjr thanks for the reply...can you provide me some example about that?..thank you!

Ya for sure! I do it all the time. It really helps. Currently, you can only use this feature with classes, but if #1341 gets accepted you can do any callable.
<?php

// register the service controller service provider
$app->register(new Silex\Provider\ServiceControllerServiceProvider());

// in src/Controller/SomeController.php
class SomeController
{
    private $hlp;
    private $db;

    public function __construct(Helpers $hlp, DB $db) {
        $this->hlp = $hlp;
        $this->db = $db;
    }

    public function getIndexAction(Request $req, Application $app) {
        /* use $this->db or $this->hlp to access those objects */
        return 'index';
    }
}

// defining a service in silex 1.3

// in a service provider for your app somewhere
$app['app.controller.some'] = $app->share(function() use ($app) {
    return new SomeController($app['app.helpers'], $app['app.db']);
});

// or defining a service in silex 2.0

$app['app.controller.some'] = function($app) {
    return new SomeController($app['app.helpers'], $app['app.db']);
};

// in the place where you define routes
$app->get('/', 'app.controller.some:getIndexAction');

If you like to use functions instead of classes, then in 2.0 if #1341 gets accepted, you could potentially do this.
<?php

// silex 2.0 (maybe)

// register the service controller service provider
$app->register(new Silex\Provider\ServiceControllerServiceProvider());

// in src/controllers.php
function controllerSomeGetIndex(Helpers $hlp, DB $db) {
    return function(Request $req, Application $app) use ($hlp, $db) {
        /* use $hlp or $db */
        return 'index';
    };
}

// in a service provider for your app somewhere
$app['app.controller.some'] = function($app) {
    return controllerSomeGetIndex($app['app.helpers'], $app['app.db']);
};

// in the place where you define routes
$app->get('/', 'app.controller.some');

thanks for the reply @ragboyjr , Yes I think than I'm searching for a solution similar to your 2nd example, using functions, hope than your propose will be accepted!!...

Awesome, thanks man!


Migrate color internals to termcolor

As discussed in https://github.com/rust-pretty-assertions/rust-pretty-assertions/commit/3f07591202ce5c272669137176e0e29ea5c9362f#commitcomment-121154122 we should use a library with windows support as I'm sure there are still edge cases we can outsource there.

Closed by #121 upgrading to a yansi version with windows support


Creating a yoga website template

Hi,
I would like to design the Yoga template.

Following things can be added to the template
a.introductory section consisting of navbar
b. the testimonial section
c. benefits of yoga section
d. section indicating different classes schedules, timings, duration
e. section indicating the numbers like number of lives impacted, number of teachers in yoga class and so on
f.  gallery section

If you want I can provide you with a mock-up in a few days and after finalizing it, I can start working on it

hey i am interested in resolving this issue
what will be  the deadline of this issue

I want to work on this issue under GSSOC'22.

@NikitaTalreja make PR other wise it will be assigned to other person

Assigned the issue  to you @Cypher1002

Thanks for assigning it to me

@Cypher1002 instead of adding new yoga template u can improve the any of the two existing ones
https://cool-front-end-templates.netlify.app/yoga template/
https://cool-front-end-templates.netlify.app/yoga template 2/
create  a new issue for it

Okay


OMG ! My post deleted after crash.

I am writed my post all day. When i finished it. I decited edit meta tags. after close metatags red screen appeared. And prompting stay but i reloaded page. Then my post dissappeared. I am so angry. Why ? What i need to do when error appear? Can i recover it ? Please help.

Ok post  not dissappeared. Thanks ghost. But it really scared me)))

Ok post not dissappeared. Thanks ghost. But it really scared me)))


How about a simple getArgs?

I wrote the following script as a Turtle learning exercise and was pleased with how it turned out (after a lot of backing and filling over discovering Turtle features and figuring out what else had to be imported).  Supporting
Optparse-Applicative is a wonderful goal, but a simple addition of getArgs :: IO [Text] would go a long way towards cleaning up simple scripts.
#! /usr/bin/env runghc

{-# LANGUAGE OverloadedStrings #-}

import qualified Data.Text as T
import System.Environment (getArgs)
import Turtle

-- Search for haskell files using a given symbol a la unix grep.

main = do
  [symS] <- getArgs
  let sym = T.pack symS
  dir <- fmap (</> "hs") home
  sh (do file <- find (suffix ".hs") dir
         let fn = dirname file </> basename file
         m <- grep (has (text sym)) (input file)
         liftIO . echo $ format (fp % ": " % s) fn m
     )

That's a great idea!  Could you write up a pull request to add this?

Thanks, int-index.  I don't have the foggiest idea how to do a pull request, not having used git before.  Your code is much nicer than what I would have written.

That's alright! :)
For future reference, you don't even need to install git!  Just navigate to the file you want to modify and click the pencil icon in the top-right corner of the file to edit it.  When you save the file contents it will fork the repository and create a new branch from your edits and then prompt you to create a pull request.  I use this trick all the time to submit tiny pull requests to other Haskell repositories (like bumping cabal version bounds and things like that).  Then you can rely on travis to compile and test your branch for you.  The whole process is pretty slick once you get used to it.


Ensure function has same method as defined

Before this PR, is the wrong method is entered this error is shown:
julia> foo(1.0)
ERROR: MethodError: no method matching get(::Cache{Tuple{Int64},Int64,Second}, ::Tuple{Float64}, ::Symbol)
Closest candidates are:
  get(::REPL.Terminals.TTYTerminal, ::Any, ::Any) at /Users/julia/buildbot/worker/package_macos64/build/usr/share/julia/stdlib/v1.5/REPL/src/Terminals.jl:161
  get(::IdDict{K,V}, ::Any, ::Any) where {K, V} at iddict.jl:86
  get(::Base.Iterators.Pairs, ::Any, ::Any) at iterators.jl:252
  ...
Stacktrace:
 [1] in(::Tuple{Float64}, ::Base.KeySet{Tuple{Int64},Cache{Tuple{Int64},Int64,Second}}) at ./abstractdict.jl:65
 [2] haskey(::Cache{Tuple{Int64},Int64,Second}, ::Tuple{Float64}) at ./abstractdict.jl:17
 [3] get!(::var"#9#10"{Tuple{Float64}}, ::Cache{Tuple{Int64},Int64,Second}, ::Tuple{Float64}) at ./abstractdict.jl:504
 [4] foo(::Float64) at /Users/malmiller/repos/ExpiringCaches.jl/src/ExpiringCaches.jl:169
 [5] top-level scope at REPL[5]:1

With this PR, this is the method error:
ERROR: MethodError: no method matching foo(::Float64)
Closest candidates are:
  foo(::Int64) at /Users/malmiller/repos/ExpiringCaches.jl/src/ExpiringCaches.jl:168
Stacktrace:
 [1] top-level scope at REPL[4]:1

It would be nice if the line number in the error message pointed to the correct location, but I'm not sure this is possible?
Closes #4

Codecov Report

Merging #5 (c0f1959) into master (f5ece5a) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master       #5   +/-   ##
=======================================
  Coverage   70.45%   70.45%
=======================================
  Files           1        1
  Lines          88       88
=======================================
  Hits           62       62
  Misses         26       26

Impacted Files
Coverage Δ

src/ExpiringCaches.jl
70.45% <100.00%> (ø)

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 f5ece5a...c0f1959. Read the comment docs.

Codecov Report

Merging #5 (c0f1959) into master (f5ece5a) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master       #5   +/-   ##
=======================================
  Coverage   70.45%   70.45%
=======================================
  Files           1        1
  Lines          88       88
=======================================
  Hits           62       62
  Misses         26       26

Impacted Files
Coverage Δ

src/ExpiringCaches.jl
70.45% <100.00%> (ø)

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 f5ece5a...c0f1959. Read the comment docs.


Quality is only 360 for youtube links

when i play a video from youtube the avaible quality appeared to me only 360 and i don't know why and i test this in the example app and in all my apps that using the package can you help me in it please

same issue any update ?

use package call modern_player

facing same problem

same prolem here, bump first post

facing the same problem

Same Issue

I have solution and video play with all qualities with its sound
Any one need this solution
Can contact me
+971557474526


As someone who does not yet know the Go dependency resolution process, how do I use what is in the vendor/ dir?

make emmie produces the following error output, after I set $GOPATH to look in the vendor/ dir for dependencies.
$ make emmie
GOOS=linux GOARCH=amd64 CGO_ENABLED=0 go build -a -installsuffix cgo --ldflags '-w' ./emmie.go ./pods.go ./replicationControllers.go ./services.go ./namespaces.go ./secrets.go ./configmaps.go ./deployments.go ./ingress.go ./registry.go
registry.go:32:2: cannot find package "github.com/aws/aws-sdk-go/aws" in any of:
	/usr/local/Cellar/go/1.7.3/libexec/src/github.com/aws/aws-sdk-go/aws (from $GOROOT)
	/Users/leeazzarello/src/emmie/vendor/src/github.com/aws/aws-sdk-go/aws (from $GOPATH)
registry.go:33:2: cannot find package "github.com/aws/aws-sdk-go/aws/session" in any of:
	/usr/local/Cellar/go/1.7.3/libexec/src/github.com/aws/aws-sdk-go/aws/session (from $GOROOT)
	/Users/leeazzarello/src/emmie/vendor/src/github.com/aws/aws-sdk-go/aws/session (from $GOPATH)
registry.go:34:2: cannot find package "github.com/aws/aws-sdk-go/service/ecr" in any of:
	/usr/local/Cellar/go/1.7.3/libexec/src/github.com/aws/aws-sdk-go/service/ecr (from $GOROOT)
	/Users/leeazzarello/src/emmie/vendor/src/github.com/aws/aws-sdk-go/service/ecr (from $GOPATH)
emmie.go:39:2: cannot find package "github.com/gorilla/mux" in any of:
	/usr/local/Cellar/go/1.7.3/libexec/src/github.com/gorilla/mux (from $GOROOT)
	/Users/leeazzarello/src/emmie/vendor/src/github.com/gorilla/mux (from $GOPATH)
emmie.go:40:2: cannot find package "k8s.io/client-go/1.4/kubernetes" in any of:
	/usr/local/Cellar/go/1.7.3/libexec/src/k8s.io/client-go/1.4/kubernetes (from $GOROOT)
	/Users/leeazzarello/src/emmie/vendor/src/k8s.io/client-go/1.4/kubernetes (from $GOPATH)
pods.go:32:2: cannot find package "k8s.io/client-go/1.4/pkg/api" in any of:
	/usr/local/Cellar/go/1.7.3/libexec/src/k8s.io/client-go/1.4/pkg/api (from $GOROOT)
	/Users/leeazzarello/src/emmie/vendor/src/k8s.io/client-go/1.4/pkg/api (from $GOPATH)
emmie.go:41:2: cannot find package "k8s.io/client-go/1.4/pkg/api/v1" in any of:
	/usr/local/Cellar/go/1.7.3/libexec/src/k8s.io/client-go/1.4/pkg/api/v1 (from $GOROOT)
	/Users/leeazzarello/src/emmie/vendor/src/k8s.io/client-go/1.4/pkg/api/v1 (from $GOPATH)
emmie.go:42:2: cannot find package "k8s.io/client-go/1.4/pkg/apis/extensions/v1beta1" in any of:
	/usr/local/Cellar/go/1.7.3/libexec/src/k8s.io/client-go/1.4/pkg/apis/extensions/v1beta1 (from $GOROOT)
	/Users/leeazzarello/src/emmie/vendor/src/k8s.io/client-go/1.4/pkg/apis/extensions/v1beta1 (from $GOPATH)
replicationControllers.go:38:2: cannot find package "k8s.io/client-go/1.4/pkg/fields" in any of:
	/usr/local/Cellar/go/1.7.3/libexec/src/k8s.io/client-go/1.4/pkg/fields (from $GOROOT)
	/Users/leeazzarello/src/emmie/vendor/src/k8s.io/client-go/1.4/pkg/fields (from $GOPATH)
replicationControllers.go:39:2: cannot find package "k8s.io/client-go/1.4/pkg/labels" in any of:
	/usr/local/Cellar/go/1.7.3/libexec/src/k8s.io/client-go/1.4/pkg/labels (from $GOROOT)
	/Users/leeazzarello/src/emmie/vendor/src/k8s.io/client-go/1.4/pkg/labels (from $GOPATH)
emmie.go:43:2: cannot find package "k8s.io/client-go/1.4/rest" in any of:
	/usr/local/Cellar/go/1.7.3/libexec/src/k8s.io/client-go/1.4/rest (from $GOROOT)
	/Users/leeazzarello/src/emmie/vendor/src/k8s.io/client-go/1.4/rest (from $GOPATH)

Make sure you clone the repo into your $GOPATH. Given that, the vendor dir should contain all the dependencies.  Worth noting for those new to building Go project, since there's a lot of convention wrapped up in the "clone to $GOPATH/src" and build pattern.


Calling  a DO with a missing method returns incomplete error message

If I call a DO class with a method that has not yet been implemented on it I get a message like:
{
    "error": "Durable Object I does not contain method foo()",
    "status": 500
}

Notice the name of the object printed is just I every time.
https://github.com/kwhitley/itty-durable/blob/v0.x/src/itty-durable.js#L63

Good catch - this is super old, but the problem appears to be with the minification.  By the time the error is thrown, the constructor name is already long lost.  Removing that in the upcoming version!


feat: use panda preset, initial component migration, ref leather-wall…

This PR builds on https://github.com/leather-wallet/mono/pull/151 and:

sets up panda-preset in ui/packages + removal of panda config
migration of Button, Link, Avatar components
removal of legacy Text + Caption components

This will prove the concept of moving a UI component into a package and importing into the extension / wherever. I tested it and I got it working using link:/ in the extension.

@coderabbitai review


Enforce custom import path

Force a custom import paths introduced in go 1.4. See: custom paths
This will avoid conflicts with master.

Thanks!


Should we drop cirq.Schedule?

I was discussing this idea with @dstrain and @maffoo and @MichaelBroughton and got a surprisingly positive response. So I want to bring it up as a thing we should consider doing.
Originally, we added Schedule as a way to have a finer degree of control over the hardware. But over time the following has happened:

Even when calling actual hardware, users have stuck with Circuit. We haven't had anyone complain about lack of flexibility with Circuit as far as I know or can remember. It seems like Circuit is sufficient.

Schedule has received very little work over time, and so it is in janky bit-rotted state. For example, it didn't even have a _unitary_ method until very recently. We would have to invest significant effort to make Schedule good.

Using Schedule is very easy to get wrong in the context of real hardware. There are often soft constraints like "after X you can immediately do Y, but you should wait T nanoseconds before doing Z". Coming up with a format to represent all of that and achieve optimal performance is a hard ever-deepening task.

Overall, it seems like we are being pulled towards just Circuit as the right level of abstraction.
I'm particularly interested in opinions from @dabacon and @mpharrigan .

For the record, I vote yes in dropping this functionality.  The schedule is too detailed of a level of abstraction and is nearly impossible to schedule correctly or efficiently.  I do not think we should support this level of control.
Having the WaitGate should mitigate many use cases that would have previously needed a schedule.

So one thing people haven't done, which I sort of expected, is to pack things a bit tighter than the Circuit allows (if you have gates with differing times).  WaitGate doesn't cover this case.
But this reminds me of an idea that could mitigate a bunch of these ideas: what if we added to operations instructions about when to schedule them, i.e. if you have "open time" before your gate, you can slide into this window.  Some sort of fine gained control like this might satisfy everything we can do with schedules and would cover, with WaitGate, a lot of cases.  If we were able to cover these cases with something like this, I'd say getting rid of scheduled operations sounds good.

I think it will be simpler to modify Circuit to have any currently missing functionality than to attempt to repair the neglect we've had for Schedule up until now. I vote in favor of dropping it.

what if we added to operations instructions about when to schedule them, i.e. if you have "open time" before your gate

Are you referring to relative placement within a moment, or are you referring to tight overlapped packing between different moments?
@dstrain115 this kind of timing information might be the sort of thing tags would be good at. You should consider it as a possible use case.

I'm in favor of dropping Schedule in its current form because it's not really supported. We have some schedule abstractions that we use internally that are really useful, so I could imagine bringing this back in the future if we decide to give people more control over timings, but it needs some careful design.

I suggested this in our meeting last thursday when you were talking about waitgate but I don't think anyone heard. Yes, I think we should drop schedule. If we bring something like it back, we should use (variants of) what the hardware team actually uses like @maffoo suggests

what if we added to operations instructions about when to schedule them, i.e. if you have "open time" before your gate

Are you referring to relative placement within a moment, or are you referring to tight overlapped packing between different moments?

Was thinking of both.
But I agree let's kill Schedule until we really find cases that we can't find a suitable abstraction for moments and circuits.

Verdict: kill it


Remap thumb cluster

Advantage 360 Pro PR template
What's changed:
Why has this change been implemented:
What (if any) actions must a user take after this change:

remaps thumb cluster


fix usage is not defined

this fixes "Uncaught ReferenceError: usage is not defined" by removing this check since usage is never defined in the code ans so always results in this error

thanks


Obsolete time zone database

Time zone database needs maintaining. Upstream erlang_localtime library gets some attention and already received several updates since the fork.
I think we would be better off if we merge the fork and use the upstream erlang_localtime directly.
Dmitry Melnikov (maintainer of upstream erlang_localtime) has agreed to merge https://github.com/choptastic/erlang_localtime/commit/6e14b6e734eca1f51944a0bba25a4179d068496b so I do not see any barriers in doing so. Please see https://github.com/dmitryme/erlang_localtime/issues/25 and comment. Thanks.

Indeed. Dmitry did merge in my changes, but they still broke things as the
merge was not clean and squashed some previous functionality. I have a new
PR awaiting merger here, which fixes this:
https://github.com/dmitryme/erlang_localtime/pull/24
Once this is merged, I'll update the dependency accordingly so that
mainline erlang_localtime is used. If it's not merged soon (my last PR took
2 years for him to merge), then I'll just update my fork from mainline and
be done with it.
-Jesse
Jesse Gumm
Owner, Sigma Star Systems
414.940.4866 || sigma-star.com || @jessegumm
On Nov 9, 2015 4:34 AM, "Vorticity-Flux"<EMAIL_ADDRESS>wrote:

Time zone database needs maintaining. Upstream erlang_localtime library
gets some attention and already received several updates since the fork.
I think we would be better off if we merge the fork and use the upstream
erlang_localtime directly.
Dmitry Melnikov (maintainer of upstream erlang_localtime) has agreed to
merge choptastic/erlang_localtime@6e14b6e
https://github.com/choptastic/erlang_localtime/commit/6e14b6e734eca1f51944a0bba25a4179d068496b
so I do not see any barriers in doing so. Please see
dmitryme/erlang_localtime#25
https://github.com/dmitryme/erlang_localtime/issues/25 and comment.
Thanks.
—
Reply to this email directly or view it on GitHub
https://github.com/choptastic/qdate/issues/18.

Great to see you are two steps ahead on this one!

Dmitry is taking is time merging my PR, so I've just updated my fork of erlang_localtime to fix this.


Cannot pull image on windows

This snippet:
return new Promise((resolve, reject) => {
        docker.pull('any image', (error, stream) => {
            docker.modem.followProgress(stream, (error, output) => {
                if (error) {
                    reject(error);
                    return;
                }
                resolve(output);
            }, (event) => console.log(event));
        });
})

always rejects on windows with "context canceled" as error message.
It might be a problem with Docker for Windows itself, but any help would be really appreciated. Same snippet works correctly on mac and linux

Same problem here using dockerode 2.4.3 and docker 17.04.0-ce-rc2

+1

Same issue
Docker version 17.03.1-ce
dockerode 2.4.3

Same issue. Same config as @pashist

I'm still baffled with this. I'm not sure if it's an issue from dockerode or docker-modem or Docker itself.  But most of the time (9 times out of 10) it fails with context canceled.
I also tried without using modem.followProgress and the error still happens.

This also happens in "node-docker-api" npm package that uses docker-modem, so i think this issue is a docker-modem issue.

I was playing around with the [https://github.com/apocas/docker-modem/blob/master/lib/modem.js] to see why the pull function from dockerode was giving me a 'Error: context canceled' message.   I got the pull to work with various images by commenting out req.end() on line 238.
Not sure what repercussions this will have, but hope it gives the contributors an idea where to start to fix this correctly.

Tried commenting out req.send() as suggested by @xblackhand but it broke other functionality like listing images & containers (timeout). BTW on docker-modem v1.0.0, the line # is 234 and not 238.

Maybe this is related to this docker-modem issue (Requests that return HttpDuplex (eg docker exec start) hang when using named pipe on windows.)?

Any update on this?

Not 100% sure, but I think the issue might be that you actually have to wait for the response output from HTTP request to finish before you can consider the image to have been fully pulled. I have a Docker client library that I autogenerate from the Docker swagger API here and ran into the same issue: I was assuming the moment I got a response from the server I was good to go, whereas in fact I need to consume the output stream and only once that is done can I consider the image pulled.

+1

This was plaguing our Windows builds so I dug a bit deeper, the results can be found here as it's an issue w/ docker-modem. Super interesting the Docker daemon seems to respond differently on win vs osx, but I assume that's due to HyperV differences?
Either way, if you're hurting for a solution you can just do pulls with plain ol' node http:
const http = require('http');

const options = {
  socketPath: '//./pipe/docker_engine',
  path: '/v1.37/images/create?fromImage=coinstac%2Fcoinstac-base',
  method: 'POST',
};

const callback = res => {
  console.log(`STATUS: ${res.statusCode}`);
  res.setEncoding('utf8');
  res.on('data', data => console.log(data));
  res.on('error', data => console.error(data));
};

const clientRequest = http.request(options, callback);
clientRequest.end();

Hope that helps!

Here the great workaround described by @rssk using basic authentication and private registry:
var clientRequest = http.request({
  socketPath: '//./pipe/docker_engine',
  path: '/images/create?fromImage=' + REGISTRY_HOST + '%2F' + IMAGE_NAME + '&tag=' + IMAGE_TAG,
  method: 'POST',
  headers: {
    'Content-Type': 'application/json',
    'X-Registry-Auth': new Buffer(JSON.stringify({ username: REGISTRY_USERNAME, password: REGISTRY_PASSOWRD, serveraddress: REGISTRY_HOST})).toString('base64')
  }
}, (res) => {
  res.setEncoding('utf8');
  res.on('data', data => console.log(data));
  res.on('error', data => console.error(data));
});
clientRequest.end();

Is this still an issue?
I'm able to run the image pull test on Windows.
https://github.com/apocas/dockerode/blob/master/test/docker.js#L184
Using Windows 10 and latest Docker version.

I believe it may have been resolved.  I was also experiencing this error previously, but with everything at the latest version it now works.

@apocas still an issue for me.
"dockerode": "2.5.7",
Docker Version 18.06.1-ce-win73 (19507)
Win 10

Can confirm this issue with Docker Version <IP_ADDRESS>-win81 (29211) (Engine 18.09.0) too

Closing this one, reopen if needed.


Allow th-abstraction 0.3

th-abstraction 0.3 renamed the datatypeVars field to datatypeInstTypes. This pull request enables usage of the renamed field, guarded by CPP.

Awesome, thanks for fixing that -- could you add an entry to .travis.yml for an applicable resolver (perhaps nightly-2019-06-09) so this gets tested?

Done, but I think it already got tested before:

lts-2 does not contain th-abstraction and pulls in 0.3.1  (https://travis-ci.org/codedownio/aeson-typescript/jobs/543473873)
lts-9 contains th-abstraction <IP_ADDRESS> (https://travis-ci.org/codedownio/aeson-typescript/jobs/543473877)

Ah, I didn't realize lts-2 was doing that. I'm glad we have an explicit recent resolver though.
Thanks again! I'll merge this now. I'd like to get #5 in also and then I'll cut a Hackage release.

(Actually the other one is a breaking change, so I'll release this first.)


use in-memory hashset

Thanks!

On second thought.. couldn't the usage of mapset here cause a lot of memory usage when there are millions of entries in the database?
In case it does I will have to revert this change.


Remove the linking operation for S3 storages

Fixes #4784

LGTM.
Only a mention in the release notes are missing