"LANG=C wormhole receive" fails with a traceback on python 3

as noted over on https://bugs.debian.org/848508, with python3:
  joey@darkstar:~>LANG=C wormhole receive
  Traceback (most recent call last):
    File "/usr/bin/wormhole", line 11, in <module>
      load_entry_point('magic-wormhole==0.8.1', 'console_scripts', 'wormhole')()
    File "/usr/lib/python3/dist-packages/click/core.py", line 716, in __call__
      return self.main(*args, **kwargs)
    File "/usr/lib/python3/dist-packages/click/core.py", line 675, in main
      _verify_python3_env()
    File "/usr/lib/python3/dist-packages/click/_unicodefun.py", line 119, in _verify_python3_env
      'mitigation steps.' + extra)
  RuntimeError: Click will abort further execution because Python 3 was configured to use ASCII as encoding for the environment.  Either run this under Python 2 or consult http://click.pocoo.org/python3/ for mitigation steps.

It would be a shame for magic-wormhole in debian to drop back to python 2 -- i'd prefer to keep things in python 3 where possible.  It's also not clear what wormhole should do in an environment that is not unicode-capable, given that the wordlists available to it might well be unicode.
C.UTF-8 apparently isn't available on Mac OS :/
C.UTF-8 should be a strict superset of C as a locale, though.  What if magic-wormhole was just to special-case this situation to work around Click's pre-emptive abort?

I don't have a strong or informed opinion about this one.. I know Click is somewhat opinionated (it doesn't seem to like from __future__ import unicode_literals under py3, which seems like a shame), but I don't know if that warning is important or just trying to head off debugging problems in weird environments.
For I18N's wordlists, we'll definitely need a UTF-8-capable locale. But it might be ok to say that applications that need to parse wormhole's output (and thus want LANG=C or LANG=C.UTF-8) only get ASCII words, and don't get tab-completion (which isn't exactly easy to offer from a subprocess anyways).
What are wormhole's options here?

monkeypatch Click to disable the warning
os.environ["LANG"] = "C.UTF-8" just before wormhole does import click
??

I'm not entirely sure that Click has been a win, overall, so I've considered dropping it and moving to twisted.python.usage.Options (which might also make #61), but I imagine that will have its share of unicode/py3 problems too. (I use t.p.usage on most of my other projects, but magic-wormhole started as a non-Twisted thing, so I went with argparse, and we moved to Click because it was more powerful).

The unicode_literals import will make it harder to do py2/py3 compatible code (because magically everything becomes a unicode and it's Hard to make a plain str in py2 after that (because u'foo' is a unicode, but so is 'foo').

As to the Click warning, it seems to document exactly why this is done (i.e. Python3 problems).
I think what will break is that a non-ASCII filename won't work properly? Or something. I'm also not really qualified to comment on this ;) but the linked Python bugs seem to say this. What's the use-case for using LANG=C anyway?
Also, does "just disable the warning" or "use something besides Click" even work? It seems like you should then run into the same edge-cases that Click is talking about -- namely, if you try to print out any non-ASCII filename in Python3 it leads to tears. I haven't actually tried this and cried those tear, though so YMMV...

I guess I'm disinclined to monkeypatch Click, since there's probably a good reason for their warning. And internally stomping on LANG= feels wrong too. wormhole doesn't emit anything non-ASCII today, and if that changes in the future (I18N or alternate-language wordlists) it'll be either be controlled by LANG= or some new CLI argument like --language= or something.
How onerous would it be to require that callers (who care about locale) use a UTF8-capable locale? git-annex could set LANG=C.UTF-8 instead of just LANG=C. Or LANG=en_US.UTF-8. That parent application would be responsible for choosing a locale that actually exists on the platform (no LANG=C.UTF-8 on MacOS), but I think anyone setting LANG= should take that responsibility anyways. Maybe something like "use C.UTF-8 if that exists, else use en_US.UTF-8"?

What if I send you a file from my machine that has a non-ASCII character in the file/path name? Won't you then print out a non-ASCII character on the other end?

"5 bytes": #130
terminal escapes: hm. I'm inclined to say that if you wormhole rx from jerks using a terminal that can't display arbitrary bytes safely, then you get what you paid for. But I have to admit that I want better than that. Accepting files involves user confirmation (because you should know what proposed filesystem change you're about to allow, and to set an expectation of the transfer time based upon how large the file is). Accepting text messages does not, because that feels like a drag on what should be a simple operation. Maybe we could scan the message for codepoints below 0x20 and ask for confirmation iff they exist? Or offer to save the --text= message into a file instead? (OTOH if the user does less FILENAME right away, do they get hit with the same attack?)

And if we do that, we should think about sneaky filenames that include escape sequences. I'd rather not have two confirmation questions, especially if the first is an "are you willing to be asked about a filename that has unusual characters?" metaquestion.
I guess the deeper question is how to enable predictable subprocess/pipe -based interaction with the wormhole executable, similar to how Git's distinction between "plumbing" and "porcelain". I'd expected the internal (python) library to be the "plumbing" API, but I'm gratified that we've moved beyond just-python already.
There are plenty of other tools/options/issues to make that work better (pipe-mode #85, --write-code-to-fd= #104, overwrite #73), but since the main purpose of the executable tool is to move files around for humans, I think I'm still looking for a way to require a UTF-8 -capable locale, and to allow the stderr status messages to emit UTF-8 if they need to (which is only when the humans used something non-ASCII, like a filename or --text= message).

I'm not entirely sure about this, but aren't the above issues exactly why Click emits the warning it does?
It sounds from the Python bugs linked in the Click explanation that Python3 has basically concluded that "everyone" has unicode-capable terminals and so the only sensible thing to do on Py3 is insist on unicode. Why does Debian want/need this to work with LANG=C anyway (i.e. what's the use-case)? Also, "weird" characters in filenames are presumably way more common in Europe, right? (e.g. umlauts etc).

The upstream bug was filed on behalf of git-annex, which sets LANG=C to prevent any potential I18N translations of the output messages from changing, so wormhole can be run as a child script (with git-annex reading its output). I think LANG=C.UTF-8 is morally equivalent, but @joeyh 's report suggests that LANG=C has been tradition for a long time, and C.UTF-8 isn't quite as likely to be available as C.
I suppose the assumption is that LANG=C will get you pure-ASCII output messages, so there's no need for a UTF-8 capable terminal. Click doesn't know that we're going to avoid this, and in fact (as y'all pointed out) non-ASCII filenames will get printed regardless of which language we use for progress messages, so I guess we really do require a UTF-8 capable terminal.

...also to me (and maybe I'm wrong!) this sounds like a thing that should be debated with Python3 developers -- that is, I believe Click is punting on this because of limitations of Py3. I can certainly get behind a push for "python3 by default", but I also don't have enough knowledge/experience with the interstices of unicode-on-python3 to even know if that means necessarily abandoning LANG=C...if it does mean that, I'd be happy to know exactly why :)

On Thu 2017-01-12 18:08:10 -0500, meejah wrote:

I believe Click is punting on this because of limitations of Py3.

afaict, Click has implemented a ton of workarounds and heuristics for
Py2, and none for Py3.  I haven't tested the Py2 workarounds and
heuristics, but it hardly seems like "limitations of Py3" :)
        --dkg

Maybe not. It was this that lead me to conclude Py3 just won't really work well with LANG=C: http://bugs.python.org/issue19846#msg205545


bookmark navigation not working

Hi there,
First of, all, thank you for your work here!
I just tested the 2D navigation example - it seems that the bookmark hotkey navigation does not work anymore with current browsers...
For instance,
FF 132 opens up the search bar when pressing the shortcut keys,
while in chromium browsers nothing happens at all.
Can anybody confirm this ?
Thank you and best regards, MT

@mtness what is the shortcut key for you? I will investigate this weekend, if I can reproduce the issue. I am also working on a complete rewrite of impress, but haven't really gotten around to finishing that at all yet. I am also currently learning some really cool stuff about linear algebra allowing me to potentially improve the logic behind impress.


Upgrade from v0.10 to v0.11 breaks the InferenceService at routing level

/kind bug
cc: @gilcardoai
What steps did you take and what happened:
Upgraded from v0.10 to v0.11 to prepare for a cluster upgrade.
Spun up a new InferenceService to get the associated v0.11 resources to check if everything was working as before.
Whenever trying to get a prediction, It does not find the route anymore:
[2024-04-16T09:08:29.503Z] "POST /v1/models/lendingclub-application-model-predictor:predict HTTP/1.1" 404 NR route_not_found - "-" 0 0 0 - "<IP_ADDRESS>" "Python/3.10 aiohttp/3.8.3" "dce966b0-daf6-4bdd-a813-73a871195ce7" "lendingclub-default-prediction.model-serving-prod.example.com" "-" - - <IP_ADDRESS>:8080 <IP_ADDRESS>:33928 - -

What did you expect to happen:
A smooth upgrade to v0.11 where the InferenceService works as before.
What's the InferenceService yaml:
inference_service.yaml

apiVersion: serving.kserve.io/v1beta1
kind: InferenceService
metadata:
  annotations:
    kubectl.kubernetes.io/last-applied-configuration: [redacted]
  creationTimestamp: '2024-04-16T11:19:30Z'
  finalizers:
    - inferenceservice.finalizers
  generation: 1
  labels:
    argocd.argoproj.io/instance: lendingclub-default-prediction-kserve-prod
    env: production
  managedFields:
    - apiVersion: serving.kserve.io/v1beta1
      fieldsType: FieldsV1
      fieldsV1:
        f:metadata:
          f:annotations:
            .: {}
            f:kubectl.kubernetes.io/last-applied-configuration: {}
          f:labels:
            .: {}
            f:argocd.argoproj.io/instance: {}
            f:env: {}
        f:spec:
          .: {}
          f:predictor:
            .: {}
            f:containers: {}
            f:minReplicas: {}
            f:serviceAccountName: {}
      manager: argocd-application-controller
      operation: Update
      time: '2024-04-16T11:19:28Z'
    - apiVersion: serving.kserve.io/v1beta1
      fieldsType: FieldsV1
      fieldsV1:
        f:metadata:
          f:finalizers:
            .: {}
            v:"inferenceservice.finalizers": {}
      manager: manager
      operation: Update
      time: '2024-04-16T11:19:30Z'
    - apiVersion: serving.kserve.io/v1beta1
      fieldsType: FieldsV1
      fieldsV1:
        f:status:
          .: {}
          f:address:
            .: {}
            f:url: {}
          f:components:
            .: {}
            f:predictor:
              .: {}
              f:address:
                .: {}
                f:url: {}
              f:latestCreatedRevision: {}
              f:latestReadyRevision: {}
              f:latestRolledoutRevision: {}
              f:traffic: {}
              f:url: {}
          f:conditions: {}
          f:modelStatus:
            .: {}
            f:copies:
              .: {}
              f:failedCopies: {}
              f:totalCopies: {}
            f:states:
              .: {}
              f:activeModelState: {}
              f:targetModelState: {}
            f:transitionStatus: {}
          f:observedGeneration: {}
          f:url: {}
      manager: manager
      operation: Update
      subresource: status
      time: '2024-04-16T11:19:54Z'
  name: lendingclub-default-prediction
  namespace: model-serving-prod
  resourceVersion: '944337397'
  uid: 765c64e7-f0cd-46f8-91f9-512d3eaff0cc
  selfLink: >-
    /apis/serving.kserve.io/v1beta1/namespaces/model-serving-prod/inferenceservices/lendingclub-default-prediction
status:
  address:
    url: >-
      http://lendingclub-default-prediction.model-serving-prod.svc.cluster.local/v1/models/lendingclub-default-prediction:predict
  components:
    predictor:
      address:
        url: >-
          http://lendingclub-default-prediction-predictor-default.model-serving-prod.svc.cluster.local
      latestCreatedRevision: lendingclub-default-prediction-predictor-default-00001
      latestReadyRevision: lendingclub-default-prediction-predictor-default-00001
      latestRolledoutRevision: lendingclub-default-prediction-predictor-default-00001
      traffic:
        - latestRevision: true
          percent: 100
          revisionName: lendingclub-default-prediction-predictor-default-00001
      url: >-
        http://lendingclub-default-prediction-predictor-default.model-serving-prod.example.com
  conditions:
    - lastTransitionTime: '2024-04-16T11:19:54Z'
      status: 'True'
      type: IngressReady
    - lastTransitionTime: '2024-04-16T11:19:53Z'
      severity: Info
      status: 'True'
      type: PredictorConfigurationReady
    - lastTransitionTime: '2024-04-16T11:19:53Z'
      status: 'True'
      type: PredictorReady
    - lastTransitionTime: '2024-04-16T11:19:53Z'
      severity: Info
      status: 'True'
      type: PredictorRouteReady
    - lastTransitionTime: '2024-04-16T11:19:54Z'
      status: 'True'
      type: Ready
  modelStatus:
    copies:
      failedCopies: 0
      totalCopies: 1
    states:
      activeModelState: Loaded
      targetModelState: Loaded
    transitionStatus: UpToDate
  observedGeneration: 1
  url: http://lendingclub-default-prediction.model-serving-prod.example.com
spec:
  predictor:
    containers:
      - env:
          - name: STORAGE_URI
            value: >-
              [redacted]
          - name: MOUNT_DIR
            value: /mnt/models/
        image: [redacted]
        imagePullPolicy: Always
        name: kserve-container
        resources:
          limits:
            cpu: '1'
            memory: 2Gi
          requests:
            cpu: 100m
            memory: 1Gi
    minReplicas: 1
    serviceAccountName: lendingclub-default-prediction-sa

Anything else you would like to add:
🤷🏼♂
Environment:

Istio Version: v1.15
Knative Version: v1.7.0
KServe Version: v0.11
Kubeflow version: not installed
Cloud Environment: AWS EKS
Kubernetes version: (use kubectl version): 1.25

Check Virtual Services and Routes
Verify that the appropriate virtual services and routes are configured in Istio, which are crucial for routing in KServe/Knative environments using Istio.
kubectl get virtualservices -n model-serving-prod
kubectl describe virtualservice lendingclub-default-prediction -n model-serving-prod

Ensure that the domain lendingclub-default-prediction.model-serving-prod.example.com resolves to the correct address and matches the expected service URL. Check DNS or service mesh settings if there's a mismatch.
Examine Istio Configuration
Check Istio’s configuration for any conflicts or misconfigurations, especially around gateways and virtual services.
kubectl logs -n istio-system -l app=istiod


Integrate SAM into ClinEpiDB (Phase I)

Redmine ticket: https://redmine.apidb.org/issues/52726
We need to be able to allow the user community to access curated ClinEpiDB studies on the SAM.
Can we either (i) replace the Map viz tool to a linkout to SAM or (ii) add a new button (ie, viz type) on the viz tab that links out to SAM? In either case, the tool should be labeled Explore on Interactive Map and should have a Beta flag.
When the button is clicked, the study the user was working on should show in SAM in a NEW tab (it is important that ClinEpiDB stays open as a separate tab).
All filters that had been applied in ClinEpiDB should also be applied in the SAM
Phase 2 (which won’t happen for a long time) would be to rework SAM so it is not stand-alone. We would remove all functionality from the left menu EXCEPT for one of the modes under Configure Map. Each of the Configure Map modes (ie, donut markers, bubble markers, and bar plot markers) would be separate viz tools. We would remove the current map viz tool from the menu

Updating the eda tab automatically would require some additional effort. We would either need to introduce a way to communicate between tabs (this can be done with localstorage events), or we would check for updates when the window regains focus.

For now I would suggest a new "EDA tab" or "analysis tab" - e.g. View Study Details Browse and Subset Visualize Map Download Record Notes
That will be easy to enable/disable with a flag that Steve wisely suggests.
The Map analysis tab (could be called Analyze in Map if we want to stick with verbs, though "Map" is also a verb!) would only show up in studies with the appropriate geo-variables.  It could have a :earth_africa: icon to make it stand out.
The content of the tab could evolve:

Explanatory text and a link to "fork your subset and analyse in the full screen map" (verbiage TBD!)
In the future we could embed the full-screen-ish map in this tab, though we have to think also about map-based subsetting in the regular subsetting tab.


Support deploy ComputeHCI

Adds support for Compute nodes also be Ceph OSP nodes.
Also splits the tripleo-deploy.sh to have -r and -p option for
the two phases:
-r use ephemeral heat to render the ansible playbooks
-p run ansible playbooks
With this we can control which part of the deployment process
to run.
Note: right now skip-tags opendev-validation-ceph gets added to
the deployment command if IsHCI is set on a baremetalset. Ceph
validations check verify if lvm2 package is installed. The check
verifies if the package is in any host of the ansible facts, which
includes the "undercloud". Since the lvm2 package is not installed
in the openstackclient container image this fails.

ceph was falling back to ctlplane network, identified the issue with isolated networks. converted to draft until tested

network isolation issue fixed in https://github.com/openstack-k8s-operators/osp-director-operator/pull/214

One inline comment. I'd also like to ponder the tripleo-deploy.sh changes a bit more as my incoming patch would pretty much remove this entirely.

yes I know that this will completely change with what you work on right now. it was just a useful change to split the workflow whil I was working on this.

Do we even need an ansible runner script after its all said and done?

hmm, not sure I get that question :)

Do we even need an ansible runner script after its all said and done?

hmm, not sure I get that question :)

What I meant was do we need a script to run ansible once we merge the "playbook generator" patch. I guess it might be useful but I didn't have one in there yet.

/retest

Do we even need an ansible runner script after its all said and done?

hmm, not sure I get that question :)

What I meant was do we need a script to run ansible once we merge the "playbook generator" patch. I guess it might be useful but I didn't have one in there yet.

I think it is still useful, for debugging, or limit to run things only on specific overcloud nodes

/lgtm


Config and use Xdebug

Hey everyone!
I saw that it is possible, but I am kind of lost and confused about this...
so if possible, i would like some help about how to configure and use xdebug.
note: I already use it on the host machine.
thanks!

I'll provide instructions on it.
TL;RD; you need to configure your IDE to listen for connections instead of starting xDebug, so the application running on Ambientum calls the host that is listening for it

I did not understand either.
I found this tutorial https://serversforhackers.com/c/getting-xdebug-working, but I did not understand and could not replicate in vscode.

Hey guys, let's center the issue about xDebug on a single issue, I'm experimenting with some more simple configuration strategies.
Please follow up on #103


Thunar missing dependency

Describe the bug
Thunar is missing the required dependency xfconf which leave it with missing functionality.
Steps To Reproduce
Steps to reproduce the behavior:

Install thunar with nix
You can't save or apply any settings

Expected behavior
I should be able to save preferences by only installing Thunar
Additional context
https://gitlab.xfce.org/xfce/thunar/-/issues/1285#note_84041
Notify maintainers
@bobby285271 @romildo @muscaln
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.1.73, NixOS, 24.05 (Uakari), 24.05.20240117.842d9d8`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.18.1`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

Add a :+1: reaction to issues you find important.

Install thunar with nix

It is unclear to me how you are installing thunar, if you use the programs.thunar.enable = true; option I don't expect xfconf missing:
https://github.com/NixOS/nixpkgs/blob/47a3f853b1950430a246fdebbbb7cfa8ca9d0921/nixos/modules/programs/thunar.nix#L42
And we do build thunar with xfconf:
https://github.com/NixOS/nixpkgs/blob/47a3f853b1950430a246fdebbbb7cfa8ca9d0921/pkgs/desktops/xfce/core/thunar/default.nix#L44


Add link to adapter for Symphony

The symphony software foundation are working on a hubot adapter for the Symphony chat system @ https://github.com/symphonyoss/hubot-symphony
It would be great to get this listed on the docs

FYI the adapter is fully functional - we're using it live

Add hubot-adapter topic
The list of hubot adapters in the hubot documentation is being replaced with a link to a GitHub topic search. Add the hubot-adapter topic to your repository on GitHub to include it in this list.
/cc https://github.com/github/hubot/pull/1320


Vue app build is broken

types/index.d.ts
const vToolTip: PluginFunction;
It should be export appended on top of it .

For reference, this is the error that's returned:
ERROR in /path/to/node_modules/v-tooltip/types/index.d.ts(3,1):
3:1 Top-level declarations in .d.ts files must start with either a 'declare' or 'export' modifier.
    1 | import Vue, { VueConstructor, DirectiveOptions,
 PluginFunction } from 'vue';
    2 |
  > 3 | const vToolTip: PluginFunction<any>;
      | ^
    4 | export default vToolTip;
    5 |
    6 | export const VPopover: VueConstructor<Vue>;

https://github.com/Akryum/v-tooltip/pull/464 is a fix for this issue

Until #464 (or sth similar) is merged local solution is here - https://github.com/Akryum/v-tooltip/issues/459#issuecomment-727064463

Duplicate of #459


Custom Parameters cannot be deleted

When adding a custom parameter under configuration tab for a Custom product you cannot delete it afterwards, if you decide you no longer want that parameter. You need to delete entire product and start over.

You do not need to remove all product, simply set your custom parameter value to blank and click on Update

I did that and the parameter name still shows under the configuration tab.

Just tested this on http://demo.boxbilling.com/bb-admin.php and it works as expected.

Clicking the "Update"  button next to the plugin name does NOT remove the blanked out parameters. You need to blank out the paramters and click the "Add new configuration field" button at the bottom to remove the blanked out parametrs. Very misleading.

That right. Will change button name to something more meaningful.


Implement graph of imports for proper import resolution

https://github.com/Microsoft/python-language-server/pull/327


Deployment on pypi.org whenever a 'release' commit is merged on 'master'

Codecov Report
Base: 92.37% // Head: 92.49% // Increases project coverage by +0.11% :tada:

Coverage data is based on head (c28f147) compared to base (364b860).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files
@@             Coverage Diff             @@
##           develop      #99      +/-   ##
===========================================
+ Coverage    92.37%   92.49%   +0.11%
===========================================
  Files           27       27
  Lines          971      973       +2
===========================================
+ Hits           897      900       +3
+ Misses          74       73       -1

Impacted Files
Coverage Δ

src/ragger/__init__.py
100.00% <100.00%> (ø)

src/ragger/firmware/stax/screen.py
100.00% <100.00%> (+1.40%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


No background when clicked the day

When slide to next month or last month ,when clicked the day ,there is no circle background showed.
The mode is range

Hey @HousTracy, I sadly can't reproduce your issue! Could you provide more information? Maybe some code, screenshots, a video or steps to reproduce? Are you able to reproduce this bug with the sample app as well?
Thank you in advance

@quentin41500 Sorry,busy for a period of time.I'll give you some steps detailly.
1.Set the mode,we are MaterialCalendarView.SELECTION_MODE_RANGE,and show the current month(now is Oct)
2.select start day and end at random (now everything is OK)
3.slide to the next month or last month ,repeat the step 2,we will see the circle background doesn't show immediately at the range of selected days.

I still couldn't reproduce with 1.6.0, closing.


Document / comment platform-app javascript code

The front end React code has mostly little or no comments. I know I am a bit old-school, but I found this to be a bit of a problem especially when starting to work on the rewrite project, often having to go through code to work out the props of a particular component.
We can discuss what needs to be commented and how (e.g. JSDoc?) to go on about it - this is just to have a reference/note for later...

The FrontEnd team will address the documentation process as part of the new Monorepo implementation
https://github.com/opentargets/issues/issues/2530


dearpygui will replicate the immediate mode paradigm in python?

Hi,
This is not really an issue, but I did not know where else to put this. :)
I am evaluating which python wrapping for imgui/implot I could use for a small app.
dearpygui seems very stable, but I did not like that it does not use immediate mode and came across your project.
After looking around I saw on the dearpygui roadmap:
Major changes for Version 2: Immediate Mode API see Version 2.
I thought that might be interesting for you because as far as I understand one of the main reasons for you to develeop this binding (which is awesome!) is the lack of immediate mode API combined with implot.

Well, thank you for telling me about the plans for dearpygui, Didn't know about that.
It would be awesome, if they integrate an immedate mode API.
They have done such a good job with the first version of the dearpygui, so I'm really interested to see what they will do next.
Like you said, initially my main motivation was to replicate the immediate mode API in a pythonic way.
But to be honest, the focus for imviz has shifted a bit.
It's now much more a toolkit for writing realtime visualizations and also includes other non-gui related things, like autoreloading or storage and export functions.
For now I will continue to work on imviz and just see if I like how they implement the imgui API.

Since the dearpygui version 2 project seems to be abandoned, I'm gonna close this for now.


Education toolkit translation to French

Hi!
Let's bring the open-source education toolkit to all the French-speaking community :)
Who would want to translate? These are the files. If you want to translate any, let us know here.

[ ] README.md
[ ] 01_huggingface-hub-tour.md
[ ] 02_ml-demos-with-gradio.ipynb
[ ] 03_getting-started-with-transformers.ipynb

Thanks!

Hello, I can translate the readme if that’s fine

Hi @g0bel1n! That would be great! Thanks.

I PR for the README.md. Now, I will get the  03_getting-started-with-transformers notebook !


ci: For merge groups, add event type, skip publishing docs

Fix for working with merge queues.
We do not want to publish a new version of the documentation when running CI checks in a merge queue. Let's skip the relevant steps.
Let's also specify the event type for merge groups. As per GitHub's documentation:
Although only the checks_requested activity type is supported,
specifying the activity type will keep your workflow specific if
more activity types are added in the future.

Note: Looking more specifically at the docs workflow, I think we could improve the workflow regarding whether or not to publish. In particular, we could have another bool parameter for the workflow_dispatch, because we don't necessarily want to publish a new version when running it. I think that ideally, we should split the build workflow for docs into build, publish, preview. But given that I don't see this documentation remain in the repository long term (the docs for the Gateway will likely be in the official docs for the Fabric), I haven't spent more time on this for now.

Fails to pass merge queue because mergeability.yml is required but doesn't run in merge queue. I'll add a commit to fix this.


Inject custom plugins in runtime

Is there any way to add custom plugins programmatically? I tried:
import { generate } from 'graphql-code-generator';
async function doSomething() {
  const generatedFiles = await generate(
    {
      schema: 'http://<IP_ADDRESS>:3000/graphql',
      overwrite: true,
      documents: './src/**/*.graphql',
      generates: {
        [process.cwd() + '/models/']: './my-plugin.js'
      }
    },
    true
  );
}

Basically replacing
{ plugins: ['typescript-common', 'typescript-server'] }
with the path to the custom plugin. But it throws with Invalid "generates" config!
Generates seems to accept strings as NamedPlugin:
yml-config-types.d.ts:
generates: {
            [filename: string]: OutputConfig | ConfiguredOutput;
};
type OutputConfig = InstanceOrArray<NamedPlugin | ConfiguredPlugin>;
type NamedPlugin = string;

making it an array throws differetly saying it can't find the plugin:
generates: {
        [process.cwd() + '/models/']: ['./my-plugin.js']
}

@aniknafs Closing for now. Please feel free to open a new issue it it's still relevant.


Fix/cleanup v2.1

fixes an issue where console.log statements prevailed
fixes an issue where the contact form did not actually submit

fixes the 'start_url' field in manifest.json


Flyway clean lasts long in Oracle db

What version of Flyway are you using?

4.0.3

Which client are you using? (Command-line, Java API, Maven plugin, Gradle plugin, SBT plugin, ANT tasks)

SBT
Gradle

What database are you using (type & version)?

Oracle

What operating system are you using?

Windows

What did you do?
(Please include the content causing the issue, any relevant configuration settings, and the command you ran)

flywayClean

What did you expect to see?

That flywayClean lasts few seconds

What did you see instead?

That flywayClean lasts 10 minutes even when only 1 table was in database. With flyway version 3.2.1 it lasts only few seconds.

FWIW, I cannot reproduce this with the flyway command line tool (version 4.0.3) - running 'flyway clean' against an 11.2 XE database running in a Docker container takes only a couple seconds.
Is your Oracle DB running locally or remotely? Which version of Oracle are you running, and which version of the oracle JDBC driver are you using to connect?

We're running oracle remotely, Oracle Database 11g Enterprise Edition Release <IP_ADDRESS>.0 - 64bit Production. We're using orjdbc6 <IP_ADDRESS> driver

Without further info on which statement may be causing the issue, I am afraid there is not much we can do. Can you debug the issue and find out?

There was a great delay after line: DEBUG: Oracle Spatial Extensions are not available. No cleaning of MDSYS tables and views.
We were using cmdline flyway version that supports -X switch for debugging. Is it enough?
C:\Apps\flyway-4.0.3>flyway -X clean
Flyway 4.0.3 by Boxfuse

DEBUG: Java 1.8.0_74 (Oracle Corporation)
DEBUG: Windows 7 6.1 amd64

DEBUG: Loading config file: C:\Apps\flyway-4.0.3\conf\flyway.conf
DEBUG: Unable to load config file: C:\Users\martin.solc\flyway.conf
DEBUG: Unable to load config file: C:\Apps\flyway-4.0.3\flyway.conf
DEBUG: Using configuration:
DEBUG: flyway.placeholders.tablespace.index -> USERS
DEBUG: flyway.jarDirs -> C:\Apps\flyway-4.0.3\jars
DEBUG: flyway.password -> *******
DEBUG: flyway.url -> jdbc:oracle:thin:@q-ora-db-scan.w****d.sys:1521/stx11de.w
irecard
DEBUG: flyway.schemas -> S****M
DEBUG: flyway.user -> s***m
DEBUG: flyway.locations -> filesystem:C:/dev/repositories/cpos/etl/evolutions
DEBUG: Adding location to classpath: C:\Apps\flyway-4.0.3\drivers\derby-<IP_ADDRESS>.jar
DEBUG: Adding location to classpath: C:\Apps\flyway-4.0.3\drivers\derbyclient-<IP_ADDRESS>.jar
DEBUG: Adding location to classpath: C:\Apps\flyway-4.0.3\drivers\h2-1.4.191.jar
DEBUG: Adding location to classpath: C:\Apps\flyway-4.0.3\drivers\hsqldb-2.3.3.jar
DEBUG: Adding location to classpath: C:\Apps\flyway-4.0.3\drivers\jtds-1.3.1.jar
DEBUG: Adding location to classpath: C:\Apps\flyway-4.0.3\drivers\mariadb-java-client-1.4.5.jar
DEBUG: Adding location to classpath: C:\Apps\flyway-4.0.3\drivers\postgresql-9.4.1208.jre6.jar
DEBUG: Adding location to classpath: C:\Apps\flyway-4.0.3\drivers\sqlite-jdbc-3.7.15-M1.jar
DEBUG: Adding location to classpath: C:\Apps\flyway-4.0.3\jars\ojdbc6-<IP_ADDRESS>.jar
Database: jdbc:oracle:thin:@q-ora-db-scan.w****d.sys:1521/stx11de.w****d (Oracle 11.2)
DEBUG: DDL Transactions Supported: false
DEBUG: Schema: S***M
DEBUG: Spring Jdbc available: false
DEBUG: Scanning for SQL callbacks ...
DEBUG: Scanning for filesystem resources at 'C:/dev/repositories/cpos/etl/evolutions' (Prefix: '', Suffix: '.sql')
DEBUG: Scanning for resources in path: C:\dev\repositories\cpos\etl\evolutions (C:/dev/repositories/cpos/etl/evolutions)
DEBUG: Found filesystem resource: C:\dev\repositories\cpos\etl\evolutions\V10__incre...sql
DEBUG: Found filesystem resource: C:\dev\repositories\cpos\etl\evolutions\V11__fill_...sql
DEBUG: Found filesystem resource: C:\dev\repositories\cpos\etl\evolutions\V12__more_...sql
DEBUG: Found filesystem resource: C:\dev\repositories\cpos\etl\evolutions\V13__custo...sql
DEBUG: Found filesystem resource: C:\dev\repositories\cpos\etl\evolutions\V14__add_m...sql
DEBUG: Found filesystem resource: C:\dev\repositories\cpos\etl\evolutions\V15__add_c...sql
DEBUG: Found filesystem resource: C:\dev\repositories\cpos\etl\evolutions\V16__add_r...sql
DEBUG: Found filesystem resource: C:\dev\repositories\cpos\etl\evolutions\V17__remov...sql
DEBUG: Found filesystem resource: C:\dev\repositories\cpos\etl\evolutions\V18__some_...sql
DEBUG: Found filesystem resource: C:\dev\repositories\cpos\etl\evolutions\V19__add_p...sql
DEBUG: Found filesystem resource: C:\dev\repositories\cpos\etl\evolutions\V1__Creat...sql
DEBUG: Found filesystem resource: C:\dev\repositories\cpos\etl\evolutions\V20__remov...sql
DEBUG: Found filesystem resource: C:\dev\repositories\cpos\etl\evolutions\V21__add_a...sql
DEBUG: Found filesystem resource: C:\dev\repositories\cpos\etl\evolutions\V22__indic...sql
DEBUG: Found filesystem resource: C:\dev\repositories\cpos\etl\evolutions\V23__add_o...sql
DEBUG: Found filesystem resource: C:\dev\repositories\cpos\etl\evolutions\V24__add_b...sql
DEBUG: Found filesystem resource: C:\dev\repositories\cpos\etl\evolutions\V25__add_p...sql
DEBUG: Found filesystem resource: C:\dev\repositories\cpos\etl\evolutions\V26__add_i...sql
DEBUG: Found filesystem resource: C:\dev\repositories\cpos\etl\evolutions\V27__run_l...sql
DEBUG: Found filesystem resource: C:\dev\repositories\cpos\etl\evolutions\V2__Add_c...sql
DEBUG: Found filesystem resource: C:\dev\repositories\cpos\etl\evolutions\V3__corre...sql
DEBUG: Found filesystem resource: C:\dev\repositories\cpos\etl\evolutions\V4__custo...sql
DEBUG: Found filesystem resource: C:\dev\repositories\cpos\etl\evolutions\V5__drop_...sql
DEBUG: Found filesystem resource: C:\dev\repositories\cpos\etl\evolutions\V6__creat...sql
DEBUG: Found filesystem resource: C:\dev\repositories\cpos\etl\evolutions\V7__fill_...sql
DEBUG: Found filesystem resource: C:\dev\repositories\cpos\etl\evolutions\V8__incre...sql
DEBUG: Found filesystem resource: C:\dev\repositories\cpos\etl\evolutions\V9__add_s...sql
DEBUG: Cleaning schema "S***M" ...
DEBUG: Oracle Spatial Extensions are not available. No cleaning of MDSYS tables
and views.
Successfully cleaned schema "S***M" (execution time 11:42.731s)

C:\Apps\flyway-4.0.3>

Well the delay is there because that's when the cleaning happens. I am afraid we need more info to be able to act on this. Please debug and isolate the exact statement causing the issue.

Any news?

Can you please suggest me some potential solutions how to debug this issue?

Create a small test program that uses flyway-core and debug in your IDE. The SBT and Gradle plugins are only thin wrappers around the core and aren't relevant in this case.

I suppose the reasons are the ones addressed in #1565 / #1550
The basically happen only when there are a lot of tables (outside of the schemas managed by flyway)

I have the same problem when running many JUnit test cases. I clean the database before each test case. In my case the database contains just 2 small tables (5-10 columns, 3-4 rows, depending on the specific test), but the clean() command lasts 18 seconds.
I am using Oracle 11g Express Edition (11.2.0-1.0, in particular I run this Docker image: https://hub.docker.com/r/alexeiled/docker-oracle-xe-11g/). I have the issue with both Flyway 4.0.3 and 4.1.2.
Can I help to debug this somehow?

If the inefficient doAllTables() implementation was the reason, then this should be fixed in the master now. Try to build Flyway from master and test it.
On 4.1.2 try to log execution time for doAllTables() and for actual drops.

Closing as most likely fixed with recent improvements in this area. Please reopen if still present when using the latest sources.


Backend Connectio Losses

Bug Report
This was reported on the forum and Discord, but no acknowledgement was given
System Information
- Operating System:
1 (for Controller Instance) x Microsoft Corporation: Windows Server 2019 Datacenter (Desktop Experience) (Windows NT 6.4 Server Version 1809 17763.615)
9 (for Target Instances) x Microsoft Corporation: Windows Server 2019 Datacenter (Server Core) (Windows NT 6.4 Server Version 1809 17763.615)
- AMP version and build date: AMP Network Edition Standard: AMP Release "Lapetus" v<IP_ADDRESS> 32/06/2020 23:18
- Which AMP release stream you're using: Mainline
I confirm:

[x] that I have searched for an existing bug report for this issue.
[x] that I am using the latest available version of AMP.
[x] that my operating system is up-to-date.
[x] that my checkboxes above look like the one on the left (remove this line when done)

Symptoms
We have 10 Virtual machines running on 1 Server. 1 is stood up as an AMP Controller.
The rest of the VM's are setup as targets.
When I access the amp controller (amp.myserver.net), I am able to log in, but then met with an error "Your connection to the AMP backend was lost. AMP will attempt to reestablish a connection.. If you chose to have your password remembered, you will be logged in automatically without interruption."
I am expecting access to the AMP controller to manage to instances.
Reproduction
Install Windows Server 2019 Datacenter onto ALL 10 VM's
Install the ADS Controller onto 1 Instance (Desktop Experience)
Install the ADS Target onto the other 9'VM's pointing to the controller (Server Core).
Attempt to create Instances among the VM's,
Attempt to log in - Notice that it now errors out with 'Reconnecting Your connection to the A...'
We have reproduced this multiple times in our environment.

Would you be so kind as to deliver us debug logs of the controller and at least one target, properly named as such?

I bring forward two scrolls for you, kind Sir! Please find attached.
Thankyou.
Controller Log.log
Target 1.log

These look like fresh logs, need a log where the issue is actually happening.
Also does anything show in the browser F12 error logs when it does?

The issue occured before those logs were retrieved. No errors in the browser console.

Can you turn on debug logging and post a new set of logs once the issue shows up?

Can you provide an email, so I do not have to censor addresses from logs.
Thankyou.

If you use a text editor that supports regular expressions you can replace \d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3} with ********* to quickly remove all IP addresses from a log.

Please find attached logs retrieved at 9:04PM AEST.
Thankyou.
Target.log
Controller.log

In your settings, disable the option for session IP stickiness.

Can we push this out to all instances.

ampinstmgr reconfiguremultiple * +Core.Security.RequireSessionIPStickiness False

Still reconnecting.

In the "New Instance Defaults" you can add a new setting where the key is "Core.Security.RequireSessionIPStickiness" and the value is "False" to apply it by default to new instances.

I've just deleted all game instances, ran the command and added the key. We are still deleted.
Do you want me to begin to remove ADS Targets from the box and recreate?
When we Installed ADS, we had to manually stop and start the ADS Instance in services.msc as when we had finished the setup process in the browser and clicked the restart button, the Instance Manger was hanging on the message to setup using the browser.

Try using ampinstmgr quick to create the initial instances rather than the GUI.

Multiple errors outputted by the console:
BEFORE AMP DOWNLOAD
[Error] FileNotFoundException
[Error] [0] (FileNotFoundException) : Could not load file or assembly 'Zhaobang.FtpServer, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.
[Error] FileNotFoundException
[Error] [0] (FileNotFoundException) : Could not load file or assembly 'Zhaobang.FtpServer, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.
[Error] FileNotFoundException
[Error] [0] (FileNotFoundException) : Could not load file or assembly 'Zhaobang.FtpServer, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.
[Error] ReflectionTypeLoadException
[Error] [0] (ReflectionTypeLoadException) : Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information.
[Error]    at InstanceManagerPlugin.LocalInstanceManager.GetProvisionArguments(String ModuleName)
[Warning] Couldn't find assembly for EmailSenderPlugin
[Warning] Couldn't find assembly for WebRequestPlugin
[Warning] Couldn't find assembly for LocalFileBackupPlugin
[Warning] Couldn't find assembly for CommonCorePlugin
AFTER AMP DOWNLOAD
[Info] Complete
[Error] Failed to unpack AMP.
[Error] ZipException
[Error] [0] (ZipException) : Could not read C:\AMPDatastore\Instances\AMPCache-19910.zip as a zip file
[Error]    at Ionic.Zip.ZipFile..ctor(String fileName)
at InstanceManagerPlugin.LocalInstanceManager.()
[Error] ZipException
[Error] [1] (ZipException) : Cannot read that as a ZipFile
[Error]    at Ionic.Zip.ZipFile.ReadIntoInstance(ZipFile zf)
at Ionic.Zip.ZipFile._InitInstance(String zipFileName, TextWriter statusMessageWriter)
at Ionic.Zip.ZipFile..ctor(String fileName)
[Error] BadReadException
[Error] [2] (BadReadException) : Could not read block - no data!  (position 0x00000000)
[Error]    at Ionic.Zip.SharedUtilities._ReadFourBytes(Stream s, String message)
at Ionic.Zip.ZipFile.ReadIntoInstance(ZipFile zf)
[Info] Instance creation failed. Reason: "The core archive failed to download or unpack"

What's the output of ampinstmgr --version ?

AMP Instance Manager v<IP_ADDRESS> built 23/06/2020 23:20

Please re-run the AMP installer in repair mode and then reboot, then try that command again.
Also delete the existing AMPCache file it made.

Just clicked the green 'Restart AMP', the terminal is still stuck, go ahead and manually restart service?

Check its log but if it looks fine but stalled then just stop the service without restarting it so the installer can continue.

We are logged in as a Domain Administrator, but not the default account. Do you want me to sign in as a standard user?

You should install AMP as a new user that is a member of the "Administrators" group but is not specifically the 'Administrator' user. There's a huge difference in how they behave due to UAC.

Signed in as a domain user and same deal.

It seems to be when I manually add game server files in using C:\AMPDatastore\Instances\Minecraft01\Minecraft\ that the issues seem to arise. Is there a recommended way to add in files without using the browser?

The issue was recently diagnosed with another user on Discord, the Nightly build should have a fix for this now. It was caused by AMP issuing excessive refresh events in ADS and causing the message queue to fill up (which triggers the 'Connection Lost' dialog)

Thank you very much for letting us know, do you know when the next mainline release will probably be.
Thankyou
Sent from my iPad
On 2 Jul 2020, at 11:19 pm, PhonicUK<EMAIL_ADDRESS>wrote:

The issue was recently diagnosed with another user on Discord, the Nightly build should have a fix for this now. It was caused by AMP issuing excessive refresh events in ADS and causing the message queue to fill up (which triggers the 'Connection Lost' dialog)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/CubeCoders/AMP/issues/303#issuecomment-653000770, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AL3XQNCCZK4DNAXUR4TLPFLRZSCMRANCNFSM4OM5Y7QA.

Either late this week or early next week.


Dark Font Palette Issue #222

Dark Font Palette Issue #222

[x] Have you renamed the PR Title in a meaningful way?

Related Issue

Closes: #
Description
The palette's font colour is too dark, which can cause readability issues for users. Dark fonts on certain backgrounds or low-contrast environments may lead to eye strain, making it difficult for users to engage with the content. This can negatively impact user experience, especially for those with visual impairments or when viewed in different lighting conditions.
Additionally as I mentioned there was palette missing to draw I added it as it was.
Screenshots 📷
Before:
before.webm
After:
after.webm
Example how to mark a checkbox:-

[x] My code follows the code style of this project.
-->
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Code style update (formatting, local variables)
[X] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Checklist

[X] My code follows the code style of this project.
[X] I have followed the contribution guidelines
[X] I have performed a self-review of my own code.
[X] I have ensured my changes don't generate any new warnings or errors.
[X] I have updated the documentation (if necessary).
[X] I have resolved all merge conflicts.

@vishanurag as u mentioned because of the merge conflict the website had two palette to choose thign but not to draw i fixed it as it was earlier.
Please review it once and if you could please label it as level2 as I fixed it and even did wht I was assigned for.
Thankyou


Manual merge notice

Stack:

#155
#156
#154
#153
#152 ⮜
#151
#150
#149
#148
#147

spr PRs are almost never meant to be merged via the GitHub UI.
Add a notice to every PR explaining not to merge manually.

Exclude unstacked PRs.

⚠ Part of a stack created by spr. Do not merge manually using the UI - doing so may have unexpected results.

What do you think of the following for the message (also a good place to insert a link to spr).
"Pull request is part of a pull request stack created by spr. Do not merge it manually using the UI, doing so may have unexpected results"

✓ Commit merged in pull request #156


GUVNOR-2181: Guided Decision Table Editor: Add support for linked tables

** FOR REVIEW - DO NOT MERGE **
See https://issues.jboss.org/browse/GUVNOR-2181 and referenced BPSMPL.
@psiroky @romartin Is working on a "real" Lienzo Mockito release and GAV.... this will be updated.
This is Phase 1, replacing the existing Grid Widget.

Part of an ensemble:
https://github.com/uberfire/uberfire/pull/379
https://github.com/droolsjbpm/droolsjbpm-build-bootstrap/pull/212
https://github.com/droolsjbpm/kie-wb-common/pull/368
https://github.com/droolsjbpm/drools-wb/pull/185
https://github.com/droolsjbpm/kie-wb-distributions/pull/293

@mariofusco @psiroky This is good to go now.

@psiroky Thanks for your comments.
I've modified accordingly (and similarly for https://github.com/uberfire/uberfire/issues/379)

Thanks @manstis! +1 to merge.


Unable to resolve module ProgressBarAndroid

[x] Review the documentation: https://facebook.github.io/react-native
[x] Search for existing issues: https://github.com/facebook/react-native/issues
[x] Use the latest React Native release: https://github.com/facebook/react-native/releases

Environment
Environment:
OS: Windows 10
Node: 10.9.0
Yarn: Not Found
npm: 6.2.0
Watchman: Not Found
Xcode: N/A
Android Studio: Version  <IP_ADDRESS> AI-173.4907809
Packages: (wanted => installed)
react: 16.3.1 => 16.3.1
react-native: 0.55.4 => 0.55.4
Description
Unable to resolve module ProgressBarAndroid for my new react-native project
Reproducible Demo
i am currently using my previous project package.json and here it is

{
"name": "yuyuteiAPK",
"version": "0.0.1",
"private": true,
"scripts": {
"start": "node node_modules/react-native/local-cli/cli.js start",
"rc-start": "npm start -- --reset-cache",
"clean": "rm -rf $TMPDIR/react-* && watchman watch-del-all && npm cache clean",
"clean-start": "npm run clean && npm run rc-start",
"fresh-install": "rm -rf $TMPDIR/react-* && watchman watch-del-all && rm -rf ios/build/ModuleCache/* && rm -rf node_modules/ && npm cache clean && npm install",
"fresh-start": "npm run fresh-install && npm run rc-start",
"tron": "node_modules/.bin/reactotron"
},
"dependencies": {
"babel-loader": "^7.1.5",
"babel-preset-react": "^6.24.1",
"dot-prop-immutable": "^1.4.0",
"native-base": "^2.7.2",
"react": "16.3.1",
"react-native": "0.55.4",
"react-native-easy-grid": "^0.2.0",
"react-native-elements": "^0.19.1",
"react-native-modal-dropdown": "^0.6.2",
"react-native-multiple-select": "^0.4.4",
"react-native-router-flux": "^4.0.1",
"react-native-sectioned-multi-select": "^0.5.2",
"react-native-ultimate-listview": "^3.3.0",
"react-native-vector-icons": "^5.0.0",
"react-navigation": "^2.11.2",
"react-redux": "^5.0.7",
"redux": "^4.0.0",
"redux-thunk": "^2.3.0"
},
"devDependencies": {
"babel-jest": "23.2.0",
"babel-preset-react-native": "4.0.0",
"jest": "23.2.0",
"react-test-renderer": "16.3.1"
},
"jest": {
"preset": "react-native"
}
}

i have try to not use this package.json as well for my new created project but i still hit the same error as this. Previously, my 1st project did not hit this error tho. Please help me in this

resolved it by typing this
npm start -- --reset-cache
and then
react-native run-android

It looks like it was a caching issue, glad to know it's now resolved.
Let's close this issue.


Apply implicit conversion from derived Conversion instance defined as implicit rather than given

Fixes #21757

This seems to fix the problem, assuming usage of Conversion instances for implicit conversions is expected to work if the instance is defined as implicit def rather than given.
The specification https://docs.scala-lang.org/scala3/reference/contextual/conversions.html mentions only given instances but I assume this was intended to take implicit into account.
Anyway, this already works with implicit for simpler cases


Add monitor function which doesn't block parent from shutting down

This comes up time and again, where we want to have a fork, but do not want the fork to block the parent from shutting down. Where this is common is in the error monitor pattern that has emerged in bigtest-server. Hence the function name.
So for example:
  let errorMonitor = fork(function*() {
    let [error]: [Error] = yield on(child, "error");
    throw error;
  });

This is tricky because the error monitor will block the fork from shutting down. This is likely not what we want. Instead we want the monitor to shut down if the parent exits. To accomplish this today, we need to wrap the entire rest of the function in a try-finally.
  let errorMonitor = fork(function*() {
    let [error]: [Error] = yield on(child, "error");
    throw error;
  });

  try {
    ...
    yield
    ...
  } finally {
    errorMonitor.halt();
  }

This is both ugly and error prone. With the monitor function we can write this more naturally:
  monitor(function*() {
    let [error]: [Error] = yield on(child, "error");
    throw error;
  });

@cowboyd I'm running into this so much now, and since we've already decided that we need this, and the implementation is easy, I thought it best to just fix it.

A preview package of this pull request has been released to NPM with the tag monitor.
You can try it out by running the following command:
$ npm install effection@monitor

or by updating your package.json to:
{
  "effection": "monitor"
}

Once the branch associated with this tag is deleted (usually once the PR is merged or closed), it will no longer be available. However, it currently references<EMAIL_ADDRESS>which will be available to install forever.

  Generated by :no_entry_sign: dangerJS against 6c77671fac6c0a0d184bdabb1f9100ea6b3bcde3

A preview package of this pull request has been released to NPM with the tag monitor.
You can try it out by running the following command:
$ npm install effection@monitor

or by updating your package.json to:
{
  "effection": "monitor"
}

Once the branch associated with this tag is deleted (usually once the PR is merged or closed), it will no longer be available. However, it currently references<EMAIL_ADDRESS>which will be available to install forever.

  Generated by :no_entry_sign: dangerJS against fdf388c7de0339a62b4036cf1ff8df4be76a50b1


Add unit tests to RBAC manager

Issue:

https://github.com/rancher/rancher/issues/44694
Problem

Additional unit testing needed in the RBAC manager
Solution

Additional unit tests added.  This change does not refactor any of the code.  There will be a separate issue created for refactoring/additional tests (the refactoring will facilitate the additional tests).
Testing

Unit tests
Engineering Testing
Manual Testing

Automated Testing

Test types added/modified:

Unit

QA Testing Considerations

No QA necessary
Regressions Considerations

None

@crobby Could you please add go docs on top of the tested functions? (gatherAndDedupeRoles, gatherRoleTemplates)

@crobby Could you please add go docs on top of the tested functions? (gatherAndDedupeRoles, gatherRoleTemplates)

docs added


Changed unit in flash speed calculation to MB/s

The result is in MB/s instead of Mhz.

Thank you!


ensure error messages are propagated

this should ensure that failures to start send any
error messages back so they are available.  Tested
both in the docker and the systemd startup cases.

@havardpe please review and merge
@aressem FYI

Looks good. Please consider my minor comment about wording


Feature Request: Location + Date

Could you add the Tradingpost location with the date of the export to the json so we would get like data trends

Also maybe the page number of the market if your scanning multiple pages

What do you mean by the trading post location?

What do you mean by the trading post location?

The exact city to track market volume of each Outpost

Sure, can do that. What about the page number, not sure how I can add that to the exported json?

I literally came to request this!
This will be insane to see!

A timestamp for a historical data chart would be lovely. Though I am not familiar with C# so I'm not much help unfortunately. I have to give props though, this is one of the most un-intrusive ways you could scrape AH data from a game. Will definitely be following this repo!

Hi guys, here you:
https://github.com/adainrivers/nw-tradingpost-price-extractor/releases/tag/0.1.8
I won't add the page number, since it doesn't make much sense to add it to the exported data.


Could not load file or assembly 'Azure.Core, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=92742159e12e44c8' or one of its dependencies. The system cannot find the file specified.

Describe the bug
I receive a runtime error that crashes all my unit tests. I suspect it will crash my consuming applications also.
Expected behavior
I expect Azure.KeyVault.Secrets to accept versions of Azure.Core >= 1.0.2. My project currently references 1.2.3, which I do need, but gives the above error unless I explicitly install 1.0.2.
Actual behavior (include Exception or Stack Trace)
The runtime error:
Could not load file or assembly 'Azure.Core, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=92742159e12e44c8' or one of its dependencies. The system cannot find the file specified.
at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions)
at System.Threading.Tasks.Task1.GetResultCore(Boolean waitCompletionNotification)    at System.Threading.Tasks.Task1.get_Result()
at MyLibrary.Security.GetSecretsByTag(String tag)
Fusion log:
=== Pre-bind state information ===
LOG: DisplayName = Azure.Core, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=92742159e12e44c8
(Fully-specified)
LOG: Appbase = file:///C:/Users/sirdank/.nuget/packages/mstest.testadapter/1.4.0/build/_common
LOG: Initial PrivatePath = NULL
Calling assembly : Azure.Security.KeyVault.Secrets, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=92742159e12e44c8.
LOG: This bind starts in LoadFrom load context.
WRN: Native image will not be probed in LoadFrom context. Native image will only be probed in default load context, like with Assembly.Load().
LOG: Using application configuration file: C:\git\MyLibrary\bin\net471\MyLibrary.IntegrationTests.dll.config
LOG: Using host configuration file:
LOG: Using machine configuration file from C:\Windows\Microsoft.NET\Framework\v4.0.30319\config\machine.config.
LOG: Post-policy reference: Azure.Core, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=92742159e12e44c8
LOG: Attempting download of new URL file:///C:/Users/sirdank/.nuget/packages/mstest.testadapter/1.4.0/build/_common/Azure.Core.DLL.
LOG: Attempting download of new URL file:///C:/Users/sirdank/.nuget/packages/mstest.testadapter/1.4.0/build/_common/Azure.Core/Azure.Core.DLL.
LOG: Attempting download of new URL file:///C:/Users/sirdank/.nuget/packages/mstest.testadapter/1.4.0/build/_common/Azure.Core.EXE.
LOG: Attempting download of new URL file:///C:/Users/sirdank/.nuget/packages/mstest.testadapter/1.4.0/build/_common/Azure.Core/Azure.Core.EXE.
LOG: Attempting download of new URL file:///C:/git/MyLibrary/bin/net471/Azure.Core.DLL.
WRN: Comparing the assembly name resulted in the mismatch: Minor Version
LOG: Attempting download of new URL file:///C:/git/MyLibrary/bin/net471/Azure.Core/Azure.Core.DLL.
LOG: Attempting download of new URL file:///C:/git/MyLibrary/bin/net471/Azure.Core.EXE.
LOG: Attempting download of new URL file:///C:/git/MyLibrary/bin/net471/Azure.Core/Azure.Core.EXE.
To Reproduce
I have a multitargeted library like this <TargetFrameworks>netstandard2.0;netcoreapp2.1;net471</TargetFrameworks> with these references (among others):
	<PackageReference Include="Azure.Identity" Version="1.2.3" />
	<PackageReference Include="Azure.Security.KeyVault.Certificates" Version="4.1.0" />
	<PackageReference Include="Azure.Security.KeyVault.Keys" Version="4.1.0" />
	<PackageReference Include="Azure.Security.KeyVault.Secrets" Version="4.1.0" />

Environment:
Visual Studio version is 16.7.6
dotnet --info
.NET Core SDK (reflecting any global.json):
Version:   3.1.403
Commit:    9e895200cd
Runtime Environment:
OS Name:     Windows
OS Version:  10.0.18362
OS Platform: Windows
RID:         win10-x64
Base Path:   C:\Program Files\dotnet\sdk\3.1.403\
Host (useful for support):
Version: 3.1.9
Commit:  774fc3d6a9
.NET Core SDKs installed:
2.2.402 [C:\Program Files\dotnet\sdk]
3.1.402 [C:\Program Files\dotnet\sdk]
3.1.403 [C:\Program Files\dotnet\sdk]
.NET Core runtimes installed:
Microsoft.AspNetCore.All 2.1.23 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.2.7 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.2.8 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.App 2.1.23 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.2.7 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.2.8 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 3.0.0 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 3.1.9 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.NETCore.App 2.1.23 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.2.7 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.2.8 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 3.0.0 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 3.1.9 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.WindowsDesktop.App 3.1.9 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Thank you!

Hello, Can you check if C:\git\MyLibrary\bin\net471\MyLibrary.IntegrationTests.dll.config has any binding reddirects?

Hi @pakrym, it does. Here is the full contents of that file:

Can you please try adding the <AutoGenerateBindingRedirects>true</AutoGenerateBindingRedirects> to your test project and see if that helps?

This is how the top of my test project .csproj looks:
<Project Sdk="Microsoft.NET.Sdk">

  <PropertyGroup>
    <TargetFrameworks>net471;netcoreapp2.1</TargetFrameworks>
    <SignAssembly>true</SignAssembly>
    <AssemblyOriginatorKeyFile>signingkey.snk</AssemblyOriginatorKeyFile>
    <AutoGenerateBindingRedirects>true</AutoGenerateBindingRedirects>
  </PropertyGroup>

I deleted the bin folder and rebuilt but the .dll.config file is unchanged and I'm getting the same error:

System.IO.FileNotFoundException: Could not load file or assembly 'Azure.Core, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=92742159e12e44c8' or one of its dependencies. The system cannot find the file specified.

This has got it working for me:
<Project Sdk="Microsoft.NET.Sdk">

  <PropertyGroup>
    <TargetFrameworks>net471;netcoreapp2.1</TargetFrameworks>
    <SignAssembly>true</SignAssembly>
    <AssemblyOriginatorKeyFile>signingkey.snk</AssemblyOriginatorKeyFile>
    <AutoGenerateBindingRedirects>true</AutoGenerateBindingRedirects>
    <GenerateBindingRedirectsOutputType>true</GenerateBindingRedirectsOutputType>
  </PropertyGroup>


feat(service): Add Zulip service

Describe the missing service. Please provide useful links.

Add new service for zulip. API docs can be found here.

@nikoksr I've looked through libraries for zulip in golang, most of them were unmaintained so I wrote a client along with a wrapper for notify. I've created a PR at #711 . If any changes are required do let me know!


fixes #132: fs.readFile & fs.writeFile encoding 'utf-8' should be replaced by 'utf8'

Should do the trick now :+1:

:+1: thanks!


Remove boilerplate and update build

Remove support for Python 3.7, 3.8
Remove unneeded container step for library only code
Update pyproject and readme

See also: https://github.com/DiamondLightSource/dls-bluesky-core/pull/4


Conditional Storage Account for sessions

Deploy Storage account for use by Container apps for sessions and restrict access to only permit the Container Apps VNET

Todo: Better way of restricting network access to this storage account

Todo: Work out how to automate the renewal of a SAS

Improvement: Use a Key Vault managed Storage Account instead which means that Devs can use Key Vault to manage the encryption Keys used for session token generation, and then we can programatically automate the rotation of the Key Vault Key and regeneration of the SAS token. This will require an AD Service Account.

I think we should rename it, so that it's just 'enable_container_app_storage_account'
There's other uses for it, rather than just sessions
Because outside of the context of the module, it doesn't really have any settings that implies it's only for storing session data from a dotnet application
If we wanted to make it fully portable, we'd add to the module the option of changing the environment variable name, so that it wasn't tied to dotnet world


[docs] fix broken MS MPI link in Installation Guide

The "Link Checks" job is currently failing with the following error.
URL        `https://www.microsoft.com/en-us/download/details.aspx?id=100593'
Name       `MS MPI'
Parent URL file:///home/runner/work/LightGBM/LightGBM/docs/_build/html/Installation-Guide.html, line 596, col 28
Real URL   https://www.microsoft.com/en-us/download/404Error.aspx
Check time 1.069 seconds
Size       92.45KB
Info       Redirected to
           `https://www.microsoft.com/en-us/download/404Error.aspx'.
Result     Error: 404 Not Found

Most recent build was 10 hours ago: https://github.com/microsoft/LightGBM/actions/runs/782291613
I see that broken download links have also been reported in the MS MPI repo: https://github.com/microsoft/Microsoft-MPI/issues/54
This PR proposes linking to the official release notes for MS MPI instead of to aa specific download in the Microsoft Download center. That should fix the failing build and I think it's a better link anyway because users can read release notes AND get downloads there.

ugh sorry, I don't understand how these extra commits made it onto this branch.

Will fix it.


Performance of Justification

Javier might have some ideas to improve the justifier program. This should minimize the time used by clingo when grounding the justifier program.

Currently, the justifier program is not considered a bottleneck of the implementation. It works efficiently already.


UsersController Put Error while updating password only

@stevenpi do you already know the reason for this bug?


npm postinstall script on Windows

Hi! I've executed npm install -g web-component-tester (Windows 7, iojs 1.0.4, npm 2.3.0; each 64-bit).
It fails with:
-----
selenium-standalone installation finished
-----
npm ERR! Windows_NT 6.1.7601
npm ERR! argv "C:\\Program Files\\iojs\\\\node.exe" "C:\\Program Files\\iojs\\node_modules\\npm\\bin\\npm-cli.js" "install" "-g" "web-component-tester"
npm ERR! node v1.0.4
npm ERR! npm  v2.3.0
npm ERR! code ELIFECYCLE

npm ERR<EMAIL_ADDRESS>postinstall: `node scripts/postinstall.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>postinstall script 'node scripts/postinstall.js'.

Strangely npm install wct-sauce succeeds (including the post install script).

With node v0.10.36 and npm v1.4.28 it very quickly fails. "Failed at the<EMAIL_ADDRESS>postinstall script."

Are you able to install wct-sauce on its own?

This is really strange; you're not the only one hitting this too...

Can you try a npm cache clean followed by another try at installing it?

Yes, npm install wct-sauce gave no errors. Interestingly, I ran npm install wct-local and then npm install -g web-component-tester and npm downloaded and executed post-install for wct-local a second time.
Will try npm cache clean.

both plugins have a postinstall script, which may be confusing matters here - wct-local (selenium-standalone) and wct-sauce (sauce-connect-launcher)

Well, I installed wct-local to shorten installation time. Didn't work.

Hmm. Can you try a non-global install of web-component-tester (say into a temp directory)?

Non-global install worked.

Lovely. Ok hm.
npm uninstall -g sauce-connect-launcher selenium-standalone launchpad wct-local wct-remote web-component-tester
npm install -g web-component-tester

I get the error again.

Can you post the full log from that failure?

https://gist.github.com/hastebrot/e6286ca66dc5ccae01c0

Ok, I just published<EMAIL_ADDRESS>w/ some additional logging, and yanked 1.0.1 - mind trying to install again?
Ideally the output starts with something like:
><EMAIL_ADDRESS>postinstall /Users/imac/work/projects/wct-sauce
> node scripts/postinstall.js

Prefetching the Sauce Connect binary.
Creating directory: /Users/imac/work/projects/wct-sauce/node_modules/sauce-connect-launcher/sc
Missing Sauce Connect local proxy, downloading dependency
This will only happen once.

I ran
npm cache clear
npm install -g web-component-tester

It worked. A difference is, that it first ran post install for wct-sauce and then post install for wct-local.
Here a part from the console output:
><EMAIL_ADDRESS>postinstall C:\Users\benjamin\AppData\Roaming\npm
\node_modules\web-component-tester\node_modules\wct-sauce\node_modules\sauce-con
nect-launcher
> node scripts/install.js

-
><EMAIL_ADDRESS>postinstall C:\Users\benjamin\AppData\Roaming\npm\node_modules
\web-component-tester\node_modules\wct-sauce
> node scripts/postinstall.js

Prefetching the Sauce Connect binary.
Creating directory: C:\Users\benjamin\AppData\Roaming\npm\node_modules\web-compo
nent-tester\node_modules\wct-sauce\node_modules\sauce-connect-launcher\sc
Missing Sauce Connect local proxy, downloading dependency
This will only happen once.
Downloading 3.18MB
Unzipping sc-4.3.5-win32.zip
Removing sc-4.3.5-win32.zip
Sauce Connect downloaded correctly
Removing C:\Users\benjamin\AppData\Roaming\npm\node_modules\web-component-tester
\node_modules\wct-sauce\node_modules\sauce-connect-launcher\sc\sc-4.3.5-win32.zi
p

><EMAIL_ADDRESS>postinstall C:\Users\benjamin\AppData\Roaming\npm\node_modules
\web-component-tester\node_modules\wct-local
> node scripts/postinstall.js

----------
selenium-standalone installation starting
----------

We have a same kind of problem on our Codeship CI:
Platform (Linux VMware)
node 0.10.25
><EMAIL_ADDRESS>postinstall /home/rof/src/bitbucket.org/artificialunit/arcwork/build/node_modules/web-component-tester/node_modules/wct-sauce/node_modules/sauce-connect-launcher
> node scripts/install.js
><EMAIL_ADDRESS>postinstall /home/rof/src/bitbucket.org/artificialunit/arcwork/build/node_modules/web-component-tester/node_modules/wct-sauce > node scripts/postinstall.js
-e/rof/src/bitbucket.org/artificialunit/arcwork/build/node_modules/web-component-tester/node_modules/lodash/dist/lodash.js:6256
source += "' +\n__e(" + escapeValue + ")
^^^ SyntaxError: Unexpected token ILLEGAL
at Module._compile (module.js:439:25)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Module.require (module.js:364:17)
at require (module.js:380:17)
at Object.<anonymous> (/home/rof/src/bitbucket.org/artificialunit/arcwork/build/node_modules/web-component-tester/node_modules/wct-sauce/node_modules/sauce-connect-launcher/lib/sauce-connect-launcher.js:6:7)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)
><EMAIL_ADDRESS>install /home/rof/src/bitbucket.org/artificialunit/arcwork/build/node_modules/web-component-tester/node_modules/socket.io/node_modules/engine.io/node_modules/ws
> (node-gyp rebuild 2> builderror.log) || (exit 0)

-ake: Entering directory `/home/rof/src/bitbucket.org/artificialunit/arcwork/build/node_modules/web-component-tester/node_modules/socket.io/node_modules/engine.io/node_modules/ws/build'
CXX(target) Release/obj.target/bufferutil/src/bufferutil.o
/ake: Leaving directory `/home/rof/src/bitbucket.org/artificialunit/arcwork/build/node_modules/web-component-tester/node_modules/socket.io/node_modules/engine.io/node_modules/ws/build'

><EMAIL_ADDRESS>install /home/rof/src/bitbucket.org/artificialunit/arcwork/build/node_modules/web-component-tester/node_modules/socket.io/node_modules/socket.io-client/node_modules/engine.io-client/node_modules/ws
> (node-gyp rebuild 2> builderror.log) || (exit 0)
/ake: Entering directory `/home/rof/src/bitbucket.org/artificialunit/arcwork/build/node_modules/web-component-tester/node_modules/socket.io/node_modules/socket.io-client/node_modules/engine.io-client/node_modules/ws/build'
CXX(target) Release/obj.target/bufferutil/src/bufferutil.o SOLINK_MODULE(target) Release/obj.target/bufferutil.node
-ake: Leaving directory `/home/rof/src/bitbucket.org/artificialunit/arcwork/build/node_modules/web-component-tester/node_modules/socket.io/node_modules/socket.io-client/node_modules/engine.io-client/node_modules/ws/build'

><EMAIL_ADDRESS>postinstall /home/rof/src/bitbucket.org/artificialunit/arcwork/build/node_modules/web-component-tester/node_modules/wct-local
> node scripts/postinstall.js
--standalone installation starting
----------
---
selenium install:
from: http://selenium-release.storage.googleapis.com/2.44/selenium-server-standalone-2.44.0.jar
to: /home/rof/src/bitbucket.org/artificialunit/arcwork/build/node_modules/web-component-tester/node_modules/wct-local/node_modules/selenium-standalone/.selenium/selenium-server/2.44.0-server.jar
---
chrome install:
from: http://chromedriver.storage.googleapis.com/2.13/chromedriver_linux64.zip
to: /home/rof/src/bitbucket.org/artificialunit/arcwork/build/node_modules/web-component-tester/node_modules/wct-local/node_modules/selenium-standalone/.selenium/chromedriver/2.13-x64-chromedriver
--
standalone installation finished
-----

npm ERR! Linux 3.13.0-35-generic
npm ERR! argv "node" "/home/rof/.nvm/v0.10.25/bin/npm" "install"
npm ERR! node v0.10.25
npm ERR! npm v2.3.0
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>postinstall: `node scripts/postinstall.js`
npm ERR! Exit status 8
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>postinstall script 'node scripts/postinstall.js'.
npm ERR! This is most likely a problem with the wct-sauce package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node scripts/postinstall.js npm ERR! You can get their info via:
npm ERR! npm owner ls wct-sauce npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! /home/rof/src/bitbucket.org/artificialunit/arcwork/build/npm-debug.log

Agh, @dominik0711 looks like the npm bug is back to being triggered; I'll whip up a workaround.
In the meantime installing WCT and lodash at the same time should alleviate it (e.g. npm install lodash web-component-tester)

@nevir. To install lodash web-component-tester together is quit difficult, because all packages will be installed through package.json and I don't know if lodash and web-component-tester can be installed together. Or is there a way to do that with package.json?

I think that if you depend on lodash and WCT in your package.json, it should work. Or, if you can run multiple commands; just install lodash first
The main issue is that npm is running the postinstall script before it has finished copying lodash into place

So, I have added a command to install lodash before the installation process through package.json. Still the same error, see log:

So, installing lodash version 2.4.1 before all other packages from package.json seems to satisfy the npm install process of web-components-tester.
Nevertheless upgrading to web-components-tester from 2.0.5 to 2.1.3 is breaking the API! Could you please, please follow the rules NOT to change the API in minor but only in major versions?!
Versions > 2.0.5 have now other API in config.js.
browsers has changed to activeBrowsers and our setting are no longer valid. Could you please tell me the right syntax for our "old fashion settings":
browsers : [{ browserName: 'chrome',
chromeOptions: { excludeSwitches : ['ignore-certificate-errors'] }}],

Thanks in advance!

Old style browsers should continue to work! Wasn't my intention to be
backwards incompatible :( I'll dig into that
What is occurring with that config for you?
On Thu, Jan 29, 2015, 11:45 dominik0711<EMAIL_ADDRESS>wrote:

So, installing lodash version 2.4.1 before all other packages from
package.json seems to satisfy the npm install process of
web-components-tester.
Nevertheless upgrading to web-components-tester from 2.0.5 to 2.1.3 is
breaking the API! Could you please, please follow the rules NOT to
change the API in minor but only in major versions?!
Versions > 2.0.5 have now other API in config.js.
browsers has changed to activeBrowsers and our setting are no longer
valid. Could you please tell me the right syntax for our "old fashion
settings":
browsers : [{ browserName: 'chrome',
chromeOptions: { excludeSwitches : ['ignore-certificate-errors'] }}],
Thanks in advance!
—
Reply to this email directly or view it on GitHub
https://github.com/Polymer/web-component-tester/issues/116#issuecomment-72090940
.

I'll get the following output:
The --browsers flag/option is deprecated. Please use --local and --sauce instead.
Warning: Object #<Object> has no method 'indexOf' Use --force to continue.

We are running our wct test through grunt. With --force the tests did not run either. Any suggestions?

@dominik0711 I've got a fix for that in 783b5579f3f95a83d799c1ce0ee1c0afd0c7ea18 - I'll have it out next version

Ok, I've got exponential backoff on the requires in both plugins (https://github.com/Polymer/wct-sauce/commit/c840bb2d2e1a1042fee73c31260f2319f73cee5b and https://github.com/Polymer/wct-local/commit/7f8e1b0659ada849afec5464f4f16ac852d734eb). Hopefully counters that bug.

Getting this with Node 4. Going to try to go back to 0.12 and see if it happens.

Meh:
Failed to load plugin "local": SyntaxError: /Users/jessewarden/Documents/_Projects/Starting-Strength-Polymer/node_modules/restify/node_modules/bunyan/lib/bunyan.js:876
});
 ^
Unexpected token )

Should I go back to Node 0.10?

Blah, same in 0.10:
/Users<my project path>/node_modules/restify/node_modules/bunyan/lib/bunyan.js:876
});
 ^

Failed to load plugin "local": SyntaxError: Unexpected token )

Disregard, nuked node_modules and bower_components, re-ran npm install && bower install, and all is (mostly) well.


Redis breaks Node AsyncLocalStorage

Description
There already exists a PR for this issue, but it has not received attention for a year: https://github.com/redis/node-redis/pull/1583
Maybe tracking it with a proper bug report might help:
As described in the PR, Node provides a local storage API to track asynchronous resources.  The current version of node-redis appears to break this context; calls to local storage return undefined.  See PR above for test case.
Node.js Version
18
Redis Server Version
No response
Node Redis Version
3.1.1
Platform
No response
Logs
No response

Update – it looks like my version was outdated.  My issue is resolved with the latest version 4.6.5


PyPy support

Currently blocked on an eventlet bug: https://github.com/eventlet/eventlet/issues/213
We should be able to add pypy to our tox config when the above is resolved.

The upcoming gevent 1.1 release supports PyPy, is that an option?

possibly, but only in the long term. gevent has different semantics to eventlet, so it's not a straight swap. at the moment, nameko is built assuming eventlet.
we have talked about abstracting out the differences and making nameko work with either eventlet or gevent, but that's only an idea at this point

PyPy now supports both eventlet and gevent. All nameko tests are passing except that coverage fails. Coverage will be failing for quite a foreseeable future (until PyTracer supports greenlets like CTracer does - as CTracer can not be compiled for PyPy).


The Project toggle should be present for Buckets

ISSUE TYPE
Enhancement/Improvement request /UI
COMPONENT NAME
Component: UI
CLOUDSTACK VERSION
Cloudstack version 4.19 RC 1
SUMMARY
The Project toggle should be present for Buckets
Navigate to
Storage > Buckets >

The project toggle button is present for all the resources and UI sections., we should extend it for buckets  also

related to #8421

Closing this, as the fix PR got merged.


Generating a test report should automatically attach a copy against the stock item

Perhaps this could be optional. Mainly for traceability purposes.

Sounds nice but could create a lot of files. Maybe we need to create a dashboard for that.

This might be a good candidate for a plugin. Will close out for now, this has been hanging around for a while and I know that @jnewlands is no longer interested in it.

This has actually come up as a requirement again, will implement for 0.8.0 as an optional feature (default=disabled)


sys.getrefcount() of a LightningModule

🐛 Bug
When creating a LightningModule, sys.getrefcount() returns 3 (vs. returning 2 for a conventional torch Module). In my particular case, for instance, this results in memory issues: even if I explicitly do del <LightningModule>, the memory is not released, and I believe this is the root of the issue.
I had originally discussed this problem on Slack. As discussed, I'm creating an issue for it and pinging @carmocca.
To Reproduce
Input:
import sys
import torch
import pytorch_lightning as pl

a = torch.nn.Module()
b = pl.LightningModule()
print(sys.getrefcount(b))
print(sys.getrefcount(a))

Output:
3
2

Expected behavior
Output:
2
2

Environment

PyTorch Lightning Version: 1.5.9
PyTorch Version: 1.10.2+cu113
Python version: 3.8.12
OS: Linux
CUDA/cuDNN version: 11.6
GPU models and configuration: Quadro RTX 8000
How you installed PyTorch: pip

Additional context
Per @carmocca's advice on Slack, a workaround is to do b._load_state_dict_pre_hooks.clear() before deleting the LightningModule. This indeed seems to work. However, I'm not sure about an explanation as to why.
Thanks!
cc @carmocca @justusschock @awaelchli @borda @ananthsub @ninginthecloud @jjenniferdai @rohitgr7

This is caused by this call in the __init__: https://github.com/PyTorchLightning/pytorch-lightning/blob/de085f30f05512862d970e1675536b4c70199d27/pytorch_lightning/core/lightning.py#L115 concretely, this line where we call a sharded internal method: https://github.com/PyTorchLightning/pytorch-lightning/blob/de085f30f05512862d970e1675536b4c70199d27/pytorch_lightning/core/lightning.py#L2026 that keeps an owning reference to self: https://github.com/pytorch/pytorch/blob/76e9730d0273058297f6adce76e73ac7e3db25f0/torch/nn/modules/module.py#L1406
There are multiple ways to fix it, but I wonder if the proper fix should be done upstream with weakref.proxy(self) to avoid the owning reference.
As a workaround, we can clear the _load_state_dict_pre_hooks dictionary on __del__.
cc @yifuwang as the author of the sharded integration (#8944) and @pritamdamania87 as the author of the relevant piece of code upstream (https://github.com/pytorch/pytorch/pull/62070)


Missing extern "C" in "components/esp_wifi/include/esp_wifi_default.h" (IDFGH-2370)

I am calling esp_netif_create_default_wifi_ap and esp_netif_create_default_wifi_sta from a cpp-file. Usually there is an #ifdef __cplusplus extern "C" statement at the beginning of the header.

Same as IDFGH-2241

It seems this issue is still around!
With latest master the extern C deifnition is still missing. Adding it manually fixes the problem and compilation completes successfully.
#4389 focuses on the order of the initializers and refers to this as a separate issue, so I think that this issue should be reopened.

@svenbieg @anderstogern Thanks for reporting, please help check whether the issue still happens at your side, thanks.

It's working now, thank You!

@svenbieg Thanks for the updates.


Add project preferences

[ ] Include support for configuration setup (Global vs. Project)
[ ] Hide configuration that do not make sense to display for projects (if user selects Project level config)
[ ] Include project configuration on the preferences
[ ] Add entry to the Projects menu to change configuration of the current project.

• Environment variables: Aqui debería ir una tabla con las variables de entorno definidas en el proyecto, junto la posibilidad de añadir o eliminar variables
• Packages: Aquí debería verse la lista de paquetes guardados con anaconda-proyect
• Conda Environment: Aquí debería verse el conda env asociado al proyeto, pero de pronto podemos unir esta entrada con Packages
• Master file: Este es el archivo maestro para correr el proyecto (edited)

@dalthviz, did you find the notes I gave you in January for this?

@ccordoba12 I searched but I didn't find them :/

Ok, no worries. I'll try to remember what I was thinking about it.

@ccordoba12 could you paste the paper here :-) ? thanks!

I still need to update icons and the actual logic for environments (a separate PR for anaconda-project). Is this what you had in mind @ccordoba12?

We could also add something related to Version Control which could be a separate page, or be part of the general one?

@jnsebgosselin do you have some suggestions for the icons we could use :-) ?

Is this what you had in mind

Yes, this is pretty much what I had in mind! Thanks!
About your screenshots:

The "Variables" entry should be renamed to "Environment variables" to be quite clear about the meaning of that.
The "Environment and packages" entry should be renamed simply to "Conda enviroment" and it should be deactivated (or better still, not shown at all) if Spyder is not running under Anaconda. Besides, that entry should have two tabs: one called "Environment" and the other one called "Packages". I think in "Environment" we should only show "Use existing conda environment" (without the base env on that list) and "Project environment". The idea with that is to force people to not use the base env, which is a killer for reproducibility. And the "Packages" tab should show the table of packages you already created.
Perhaps "Master file" should be removed as an entry and moved as a tab in "General"? What do you think?

About your questions:

We could also add something related to Version Control which could be a separate page, or be part of the general one?

I think we should add a separate page (entry) for this.

Where should we include the Use Global Preferences vs Use Project Preferences option? in the general page?

Yes, I think we should add this to "General".

The "Variables" entry should be renamed to "Environment variables" to be quite clear about the meaning of that.

👍

The "Environment and packages" entry should be renamed simply to "Conda enviroment" and it should be deactivated (or better still, not shown at all) if Spyder is not running under Anaconda. Besides, that entry should have two tabs: one called "Environment" and the other one called "Packages". I think in "Environment" we should only show "Use existing conda environment" (without the base env on that list) and "Project environment". The idea with that is to force people to not use the base env, which is a killer for reproducibility. And the "Packages" tab should show the table of packages you already created.

Ok, but I need some extra pointers on how we will handle some things. What packages should we display on the packages tab when:

Project env: This is clear that we will track only the packages the user explicitly asked for.
Use existing conda environment: What packages here? All the packages that currently are installed on the env? or?

Perhaps "Master file" should be removed as an entry and moved as a tab in "General"? What do you think?

Yes I think it makes sense for now.

We could also add something related to Version Control which could be a separate page, or be part of the general one? I think we should add a separate page (entry) for this.

Ok will do.

Use existing conda environment: What packages here? All the packages that currently are installed on the env? or?

I agree this is the crucial point. Without users letting us know a specific set of packages in their environment, it's not possible for us to guarantee project reproducibility.
I see two options here:

We should discourage the usage of previously created conda envs at project creation and also when users select "Use existing conda environment". We could do that by showing a modal dialog, saying that it's not possible to guarantee reproducibility of the project in that case.
Disabling the "Packages" tab, or showing the entire list of packages in the env along with a warning instructing users to select the main dependencies of the project (e.g. Numpy, Pandas, Matplotlib, and not libgcc-ng) so we can register them in anaconda-project.yml.

Perhaps both options apply?

Disabling the "Packages" tab, or showing the entire list of packages in the env along with a warning instructing users to select the main dependencies of the project (e.g. Numpy, Pandas, Matplotlib, and not libgcc-ng) so we can register them in anaconda-project.yml.

The issue I see with this option (besides adding greater complexity) is that two or more projects could be using this other conda environment so, if the user has different dependencies on different projects, that conda env might reach a point where it will has to update some packages on project switch (because the user selected different "packages" as the main packages of their environment).
The only "solution" to this is that a project could only use another existing conda env, but this also probably defeat its purpose for users wanting to recycle the same env for may different projects.

Disabling the "Packages" tab, or showing the entire list of packages

What I think would make sense to me is that if the user select an existing environment, we can display the whole list (as information for the user) but disable any modification of that env from the spyder interface (remove or disable the add/edit/remove). This allows power users that want to recycle envs to use them, but enforces "best practices" for non power users.
Thoughts?

The issue I see with this option (besides adding greater complexity) is that two or more projects could be using this other conda environment so, if the user has different dependencies on different projects, that conda env might reach a point where it will has to update some packages on project switch (because the user selected different "packages" as the main packages of their environment).

Great point! I haven't thought about that!

What I think would make sense to me is that if the user select an existing environment, we can display the whole list (as information for the user) but disable any modification of that env from the spyder interface (remove or disable the add/edit/remove). This allows power users that want to recycle envs to use them, but enforces "best practices" for non power users.

Agreed, this is a very good option! Besides, we should show a QLabel with a warning saying that the project is not reproducible.

Looking good, thanks! My only recommendation (for now) is to remove the QGroupBoxes called "Environment packages" and "Conda environment" because now those are unnecessary with the new tabs.

@ccordoba12 @goanpeca, it seems to me that there are elements here that we can extract to the Environment Manager plugin #17654.
Also, is there any consideration for having multiple projects open at one time? But maybe this is not necessary if IPython consoles are not restarted when switching projects.

it seems to me that there are elements here that we can extract to the Environment Manager

Agreed. We need to discuss further about it.


pyiceberg causing mypy to raise Exception

Apache Iceberg version
0.6.0 (latest release)
Please describe the bug 🐞
when importing the pyiceberg package, receive the following failure message from running mypy.
  File "mypy/main.py", line 173, in run_build
  File "mypy/build.py", line 154, in build
  File "mypy/build.py", line 230, in _build
  File "mypy/build.py", line 2729, in dispatch
  File "mypy/build.py", line 3087, in process_graph
  File "mypy/build.py", line 3205, in process_stale_scc
  File "mypy/build.py", line 2313, in write_cache
  File "mypy/build.py", line 1470, in write_cache
  File "mypy/nodes.py", line 352, in serialize
  File "mypy/nodes.py", line 3435, in serialize
  File "mypy/nodes.py", line 3367, in serialize
AssertionError: Definition of pydantic.types.JsonValue is unexpectedly incomplete

When I remove the import of pyiceberg, the mypy error goes away.
I believe this may be an issue with the pyiceberg package

Hello @Quixotical, thank you for reporting this issue. Can you share a minimal setup that reproduces this error?

actually we can close this out, I was using an older version of mypy and upgrading to the newest version seems to have resolved my issue. Thanks for inquiring about this!


Minimise disruption to workload in case of kube-apiserver loadbalancer issues

What happened:
If the kuber-apiserver loadbalancer is down for some time, the workload (even what is not dependent on kube-apiserver) in the cluster is disrupted because nodes and pods get evicted eventually.
The nodelifecycle controller in the kube-controller-manager is the active component that is taking the relevant actions. The following flags seem to be relevant.

--node-monitor-grace-period controls the grace period before the node is marked as NotReady if kubelet is not able to reach the kube-apiserver.
--pod-eviction-timeout controls the grace period after a node is marked as NotReady before the pods in that node are evicted.
The pods are marked as not ready (condition Ready false) as soon as node is marked as NotReady. This is not controlled by any flag.
So, none of the above flags help completely in keeping the node and the workload ready.
Only switching off the nodelifecycle controller using the the --controllers flag keeps the nodes and the workload ready. But it might be simpler to scale down the kube-controller-manager.

What you expected to happen:
The workload (not dependent on kube-apiserver) should not be disrupted.
How to reproduce it (as minimally and precisely as possible):
Delete kube-apiserver LoadBalancer Service (or replace it with a ClusterIP Service).
Anything else we need to know?:
A possible minimal solution could be to introduce a watchdog component to continually monitor the accessibility of kube-apiserver both internally from the seed cluster and externally via the loadbalancer. If it is not accessible externally but accessible internally then scale down the kube-controller-manager and scale it back up when external access is restored.
Environment:

Gardener version:
Kubernetes version (use kubectl version):
Cloud provider or hardware configuration:
Others:

We were fearing that scaling down the KCM may have undesired side effects and disabling the nodelifecycle controller may be better/less drastic. Do we know whether there is anything in KCM worth keep running or whether it can be shut down, if the nodes can't call back home anyways?

@vlerenc I tried switching off KCM for longer periods last week (~2h) while the loadbalancer was also down. I could not see any adverse affects. The existing workload was unaffected as long as the pods/nodes themselves did not have any issues. Considering that scaling down KCM is simpler compared to switching on/off individual controllers in KCM, this looks more suitable approach. WDYT?

Well then, if the anxiety wasn't justified, then it is certainly the simplest solution. I just wasn't sure whether we should check the source code to be sure or try another path (avoiding that). Not sure whether "disabling it for a week" proves the point (maybe some code paths were not touched). However, if a standard workload looks healthy, then I guess we can just do it this way. During further Gardener ring tests we will anyhow uncover more issues and if it works for us (it did for you already), then it may work for most if not all. So yes, let's go ahead with the simple solution for this "problem" and refine if necessary later. It will already improve the situation today. Thank you!


Upgrade to NSB 6

Hi Thuzi!
This looks really interesting for lightweight integration testing.  Any plans to upgrade this to support NSB 6 (beta)?

Yes. We haven't upgraded our system to NS6. But when we do, we will be upgrading this for all our tests.


Why looking for g77 in the first place?

OpenBLAS does not support g77 on Linux. I am wondering why it is then the first compiler to look for when no Fortran compiler is specified explicitly. In my case, I have both g77 and gfortran installed, and OpenBLAS picks up the former even though it fails to compile using this compiler. Thank you.
Regards,
Ivan

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/15763714-why-looking-for-g77-in-the-first-place?utm_campaign=plugin&utm_content=tracker%2F69691&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F69691&utm_medium=issues&utm_source=github).

@IvanUkhov  thank you for your patch. I just delete g77 from the list.

@xianyi, that is even better! Thanks a lot!