Can't write to SQLite db w/ 4.1.2; and NGINX documentation is confusing if not outright incorrect

I've been using munkireport for years, and recently changed jobs.  I've been trying to spin up a new instance of munkireport using the latest (4.1.2) tar.gz file, a very simple setup using Ubuntu 18.04 LTS with NGINX, PHP7.2, and using the SQLite database.  And I have been having one heckuva time doing so.  No matter what I do, I can't get past the fact it appears unable to write to the database.  To say it's been frustrating would be an understatement.
Now I'm well aware of dealing with file permissions, and I've made sure that www-data owns all the necessary directories and can write to the directory ./app/db/.  In fact, when I ran the database migration step to initialize the SQLite database, I did so using
sudo -u www-data php database/migrate.php
from the main munkireport-php directory, and sure enough, it generated the appropriate db.sqlite file where expected.  However, when I visit the site, every time I get a

Fatal error
Connection failed: SQLSTATE[HY000] [14] unable to open database file
Try again

message.
Now I have no trouble setting up NGINX.  I used Apache for eons, and a few years back I got into using NGINX instead for performance reasons.  And frankly, it's a lot easier to configure.  And I noticed that in v4, the setup involves setting the document root to the munkireport/public directory, thereby keeping the rest of the app, notably munkireport/app/db/ etc. out of the webroot.
However, I suspect this may well be the reason the app is unable to write to the SQLite database.  The migration step is done from the CLI, so no worries there as the code was running as user www-data.  And in older versions of munkireport-php, the SQLite database lived inside the document root, just protected using things like .htaccess files.
But now that SQLite file lives outside the webroot, and most webservers do not allow PHP code to access such files.  Or am I missing something?  (This, by the way, won't manifest itself with MySQL, as you typically connect to it using either IP:port or a socket, but in either case, it's not a file system/directory boundary issue.  But MySQL is overkill for the setup I'm doing, and at least until now, I've always found SQLite performed just fine for my use case.)
Now in the process of all this, I also found the instructions regarding configuring NGINX here to be extremely confusing:
https://github.com/munkireport/munkireport-php/wiki/NGINX
First of all, that symbolic link statement makes no sense.  Where it says

Assuming you have setup the proper symbolic link in the webroot:
ln -s /path/to/web/root/report /path/to/munkireport/public

that's backwards.  That command will create a symbolic link FROM /path/to/web/root/report which will be located inside /path/to/munkireport/public.  That is, if you type
cd /path/to/munkireport/public
ls -al
you will see what appears to be a directory named report which links to the location /path/to/web/root/report, assuming there even IS such a directory.  I doubt this is what was intended, as it makes no sense.
Next, the configuration snippet provided is also a bit confusing:

The following location block should work to serve MunkiReport out of the /report subdirectory:
root     /path/to/web/root;

location /report {
    autoindex on;
    location ~* \.php$ {
        include snippets/fastcgi-php.conf;
        fastcgi_pass unix:/var/run/php/php7.0-fpm.sock;
        fastcgi_param SCRIPT_FILENAME  /media/Data/$fastcgi_script_name;
    }
}

What exactly is the purpose of the fastcgi_param line?  And where exactly is this /media/Data/ directory referenced?  And do we really want to have autoindex enabled here?

Not sure if this is tied together or not, or if it will help or hurt track down the issue, but even though I get those failure messages, when I reload the page or click the 'Try again' link, the main dashboard does load, but I do then see under 'Events'

Request Failed: parsererror, SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data

And going to 'Listings | Clients' shows

DataTables warning: table id=DataTables_Table_0 - Invalid JSON response. For more information about this error, please see http://datatables.net/tn/1

Ok, I'm a a loss.  I can't figure out what's causing this.  I've now gone back and removed the ./app/db/db.sqlite file and done some testing.  Unless said otherwise, I'm sitting at the root of the application directory.  If I change the .env config file so that it reads
CONNECTION_DATABASE="db/db.sqlite"
as indicated on this wiki page:  https://github.com/munkireport/munkireport-php/wiki/Server-Configuration
and then try to run
sudo -u www-data php database/migrate.php
it fails.    But no matter what I do otherwise, such as
sudo chmod 777 app/db/db.sqlite
sudo chown -R www-data:www-data /path/to/munkireport
I can't get past the same error message when I login:

Fatal error
Connection failed: SQLSTATE[HY000] [14] unable to open database file
Try again

There's nothing in either the NGINX access or error log files to help indicate where the problem is.  In fact, there's NOTHING in the error log file AT ALL.  So whatever this is, it's not PHP kicking out errors as I'd typically see in other webapps.  And I'm highly doubting it's a permissions issue at this point.
The last time I setup munkireport-php, it was an older version (v2?).  But I never had issues like this.  It worked rock solid.  I would just like to have some kind of feedback to point me in the right direction.  But as it stands now, I can't figure out what's keeping it from working.

Could you try using the full path to the database file?

Thanks for reporting, I know this is from a long time ago, but did you get your issues fixed?


Migrate to lower bounds for pyproject.toml

Description of changes
This addresses #147 by relaxing the requirements to known-good lower bounds. We could perhaps go lower than these bounds but without spending too much time this unblocks users trying to use newer versions of python that have transitive dependencies that are pinned to a non-compatible version.
Summarize the changes made by this PR.

Improvements & Bug fixes

Change package dependencies to only require lower bounds

New functionality

None

Test plan
By Integration and Release CI pipelines.
Documentation Changes
None required.

Many thanks for that super quick change! ♥

@HammadB do you know when this will be available on PyPI?

@ubuntudroid It will be out shortly in v0.3.3!


Adding different types of editors we can use in the linux cheatsheet

Hello @jaisinha
Go for it. And go through the readme and contributing file first before sending the pull request.
Thank you

Done,,,pl take a look..and also a question..do I have any chance to get a t-shirt now...my 3/4 prs have been accepted

@Suryansh1720001 reply pl

Yes, you can win the swags after you complete your 1 PR which is remaining.


which layer's attention maps are used as template information?

Hi,
In your ESM-Fold paper:
The second change involves the removal of templates. Template information is passed to the model as
pairwise distances, input to the residue-pairwise embedding. We simply omit this information, passing
instead ** the attention maps from the language model ** , as these have been shown to capture structural
information well (38)
You use attention maps as template information. I wonder it's from the last layer or from all the layers?
Thanks in advance！

duplicate issue due to the network


(🎁) Make projects "activatable" so that all tools/aliases are available

Having to go ./pw poetry install is a little boilerplate-y.
Similar to how one activates a venv, what if you could do something like:
> ./pw --activate
Activating project
(current-project) >

Then you can go
(current-project) > poetry install

with an alias and px installed, you can just type px i (this is exactly what I do while developing)

@houbie I understand that px i is really useful and shorthand for px poetry install. But I still think it would be nice to be able to surface all tools (although, probably not aliases) to the top level.

this would be nice not just because it saves having to type two additional characters, but it will also improve compatibility with other tools that aren't aware of pyprojectx. some examples:

https://github.com/pdm-project/tox-pdm/issues/54
https://github.com/knowsuchagency/pdm-task-provider/issues/1

I could add an activate option that echoes the location of the activate script: ./pw -a main
You could then activate it with source $(./pw -a main)
Not sure how this would work on windows though...

maybe there can be a consistent location in .pyprojectx that contains wrappers for each installed tool:
.pyprojectx/
├── scripts/
│   ├── pdm
│   └── pdm.bat
└── venvs/
    └── pdm-0ea4e8a18e16ec37852eafe4948fceb0-py3.12/
        ├── Lib/
        │   └── ...
        └── Scripts/
            ├── pdm
            └── pdm.exe

that way, you can easily make them available globally by adding ./.pyprojectx/scripts to your PATH

Great idea, will look into it!

Final solution is different: instead of a single scripts dir, a dir per tool context is created.
This makes is possible to activate a tool context venv.
So if you install pdm as part of the main context, you can either run:

.pyprojectx/main/pdm --version
source .pyprojectx/main/activate + pdm --version

thanks for implementing this @houbie, a couple questions though:

after updating to version 2.1.0, i don't see that main directory:

i see that new pdm directory with the activate script in it though, but does that mean each tool needs to have its own separate activation script?

running the activation script doesn't seem to work:
> .\.pyprojectx\pdm\activate
(.pyprojectx) PS C:\project> pdm --help
pdm : The term 'pdm' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is
correct and try again.
At line:1 char:1
+ pdm --help
+ ~~~
    + CategoryInfo          : ObjectNotFound: (pdm:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

In 2.0.0 the philosophy changed from creating a separate virtual environment per tool, to group tools together in a tool context.
I typically create a main context with all build related tools (everything required in github actions):
main= {requirements = ["pdm","ruff","pre-commit","px-utils"], post-install = "pre-commit install"}
BTW: the main context has special meaning; all its tools are available by default, f.e. ./pw pdm will work without requiring an alias.
As of 2.1.0, a symlink to the scripts dir of each tool venv is created in .pyprojectx. This includes the standard venv activation script.
TBH, I only tested venv activation on Mac. Is it broken on windows when you run it via a symlink?

Is it broken on windows when you run it via a symlink?

seems to be. unrelated to that issue though, i also use pyprojectx on a work PC where the admins have disabled symlinks. when attempting to use the new version on that PC, it crashes:
Traceback (most recent call last):
  File "<frozen runpy>", line 198, in _run_module_as_main
  File "<frozen runpy>", line 88, in _run_code
  File "C:\project\.pyprojectx\pyprojectx\2.1.0-py3.12\Scripts\pyprojectx.exe\__main__.py", line 7, in <module>
  File "C:\project\.pyprojectx\pyprojectx\2.1.0-py3.12\Lib\site-packages\pyprojectx\cli.py", line 20, in main
    _run(sys.argv)
  File "C:\project\.pyprojectx\pyprojectx\2.1.0-py3.12\Lib\site-packages\pyprojectx\cli.py", line 59, in _run
    if _run_alias_cmds(config, cmd, pw_args, options):
       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\project\.pyprojectx\pyprojectx\2.1.0-py3.12\Lib\site-packages\pyprojectx\cli.py", line 77, in _run_alias_cmds
    _run_alias(
  File "C:\project\.pyprojectx\pyprojectx\2.1.0-py3.12\Lib\site-packages\pyprojectx\cli.py", line 130, in _run_alias
    _run_in_ctx(
  File "C:\project\.pyprojectx\pyprojectx\2.1.0-py3.12\Lib\site-packages\pyprojectx\cli.py", line 177, in _run_in_ctx
    venv = _ensure_ctx(config, ctx, env, options, pw_args)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\project\.pyprojectx\pyprojectx\2.1.0-py3.12\Lib\site-packages\pyprojectx\cli.py", line 193, in _ensure_ctx
    ctx_path.symlink_to(scripts_path, target_is_directory=True)
  File "C:\Users\user\AppData\Local\Programs\Python\Python312\Lib\pathlib.py", line 1387, in symlink_to
    os.symlink(target, self, target_is_directory)
OSError: [WinError 1314] A required privilege is not held by the client: 'C:\\project\\.pyprojectx\\venvs\\pdm-f938d443f677560d2786a15bf0f3e7d1-py3.12\\Scripts' -> 'C:\\project\\.pyprojectx\\pdm'

i'll raise separate issues for both of these


corebluetooth: Properly raise exceptions

Currently, CoreBluetoothProvider._raise_error improperly passes the exception traceback as value to raise_, causing TypeError: instance exception may not have a separate value to be thrown instead of the real exception.
This patch fixes that error, matching the behaviour of the BlueZ driver (https://github.com/adafruit/Adafruit_Python_BluefruitLE/blob/master/Adafruit_BluefruitLE/bluez_dbus/provider.py#L105).
Testing this patch is easy: add anything that throws an exception (e.g. 1/0) to the main loop of an example app and run it under macOS.

Dear @adafruit / @tdicola
You should really pull this into the main branch, so that Mac OS X users can get proper exceptions and have a chance to debug their code.

Oh nice thanks for the sending the pull!  Just merged in.


Observable map?

Is it possible to use remotedev on observable Map? I tried remotedev(observable(new Map()), it is visible in the Redux DevTools, but no actions or state is shown there.

I guess I will close it. Four years is long time I don't know why I needed this :)


Revert "(PUP-3827) Return errors matching schema from indirected routes"

Reverts puppetlabs/puppet#4875
Tests failing - PUP-6270

👍

👍
The original PR has definitely caused a regression in the test suite and we've failed to get it fixed by EOD Friday. Reverting for clean builds and we will update #4947 on Monday with appropriate fixes.

CLA signed by all contributors.


Sidecar injector admission webhook not working 2

Bug description
Bumped into the same issue in my cluster running Istio 1.2.0 (installed via default Helm chart):
$ kubectl label namespace default istio-injection=enabled
$ kubectl -n default run -it alp --image alpine -- sh
$ kubectl get events
LAST SEEN   TYPE      REASON              OBJECT                               MESSAGE
87s         Warning   FailedCreate        replicaset/alp-8754cdf45            Error creating: Internal error occurred: admission webhook "sidecar-injector.istio.io" denied the request: error converting YAML to JSON: yaml: line 3: did not find expected key

It tells me the same line (line 3) for other deployments as well.
$ k get replicaset alp-8754cdf45 -o yaml > alp_replicaset.yaml && ./istioctl kube-inject --meshConfigMapName istio --injectConfigMapName istio-sidecar-injector -f alp_replicaset.yaml
2019-06-26T12:54:39.271379Z	warn	Failed to unmarshall template error converting YAML to JSON: yaml: line 3: did not find expected key rewriteAppHTTPProbe: false
initContainers: []

- name: istio-init
  image: "gcr.io/istio-release/proxy_init:release-1.2-latest-daily"
  args:
  - "-p"
  - "15001"
  - "-u"
  - 1337
  - "-m"
  - "REDIRECT"
  - "-i"
  - "*"
  - "-x"
  - ""
  - "-b"
  - ""
  - "-d"
  - "15020"
  imagePullPolicy: "IfNotPresent"
  resources:
    requests:
      cpu: 10m
      memory: 10Mi
    limits:
      cpu: 100m
      memory: 50Mi
  securityContext:
    runAsUser: 0
    runAsNonRoot: false
    capabilities:
      add:
      - NET_ADMIN
  restartPolicy: Always
  env: []

containers:
- name: istio-proxy
  image: "gcr.io/istio-release/proxyv2:release-1.2-latest-daily"
  ports:
  - containerPort: 15090
    protocol: TCP
    name: http-envoy-prom
  args:
  - proxy
  - sidecar
  - --domain
  - $(POD_NAMESPACE).svc.cluster.local
  - --configPath
  - "/etc/istio/proxy"
  - --binaryPath
  - "/usr/local/bin/envoy"
  - --serviceCluster
  - "alp-8754cdf45.default"
  - --drainDuration
  - "45s"
  - --parentShutdownDuration
  - "1m0s"
  - --discoveryAddress
  - "istio-pilot.istio-system:15010"
  - --zipkinAddress
  - "zipkin.istio-system:9411"
  - --dnsRefreshRate
  - 300s
  - --connectTimeout
  - "10s"
  - --proxyAdminPort
  - "15000"
  - --concurrency
  - "2"
  - --controlPlaneAuthPolicy
  - "NONE"
  - --statusPort
  - "15020"
  - --applicationPorts
  - ""
  env:
  - name: POD_NAME
    valueFrom:
      fieldRef:
        fieldPath: metadata.name
  - name: POD_NAMESPACE
    valueFrom:
      fieldRef:
        fieldPath: metadata.namespace
  - name: INSTANCE_IP
    valueFrom:
      fieldRef:
        fieldPath: status.podIP

  - name: ISTIO_META_POD_NAME
    valueFrom:
      fieldRef:
        fieldPath: metadata.name
  - name: ISTIO_META_CONFIG_NAMESPACE
    valueFrom:
      fieldRef:
        fieldPath: metadata.namespace
  - name: ISTIO_META_INTERCEPTION_MODE
    value: "REDIRECT"
  - name: ISTIO_META_INCLUDE_INBOUND_PORTS
    value: ""

  - name: ISTIO_METAJSON_LABELS
    value: |
           {"pod-template-hash":"8754cdf45","run":"alp"}

  imagePullPolicy: IfNotPresent

  readinessProbe:
    httpGet:
      path: /healthz/ready
      port: 15020
    initialDelaySeconds: 1
    periodSeconds: 2
    failureThreshold: 30
  securityContext:
    readOnlyRootFilesystem: true

    runAsUser: 1337
  resources:

    limits:
      cpu: 2000m
      memory: 1024Mi
    requests:
      cpu: 100m
      memory: 128Mi

  volumeMounts:

  - mountPath: /etc/istio/proxy
    name: istio-envoy
  - mountPath: /etc/certs/
    name: istio-certs
    readOnly: true
volumes: []
- emptyDir:
    medium: Memory
  name: istio-envoy
- name: istio-certs
  secret:
    optional: true

    secretName: istio.default

Affected product area (please put an X in all that apply)
[X] Configuration Infrastructure
[ ] Docs
[X] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[X] User Experience
[ ] Developer Infrastructure
Expected behavior
Successfully inject sidecars.
Steps to reproduce the bug
$ kubectl label namespace default istio-injection=enabled
$ kubectl -n default run -it alp --image alpine -- sh

Version (include the output of istioctl version --remote and kubectl version)
$ istioctl version --remote
client version: 1.2.0
citadel version: release-1.2-20190626-09-15
galley version: release-1.2-20190624-09-15
ingressgateway version: release-1.2-20190623-09-15
pilot version: release-1.2-20190623-09-15
policy version: release-1.2-20190624-09-15
sidecar-injector version: release-1.2-20190626-09-15
telemetry version: release-1.2-20190624-09-15
$ kubectl version
Client Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.3", GitCommit:"5e53fd6bc17c0dec8434817e69b04a25d8ae0ff0", GitTreeState:"clean", BuildDate:"2019-06-06T01:44:30Z", GoVersion:"go1.12.5", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.1", GitCommit:"b7394102d6ef778017f2ca4046abbaa23b88c290", GitTreeState:"clean", BuildDate:"2019-04-08T17:02:58Z", GoVersion:"go1.12.1", Compiler:"gc", Platform:"linux/amd64"}

How was Istio installed?
Using Ship (Adjusted namespace to istio-system in ship step 2)
echo "Remember to set namespace to 'istio-system' in Step 2"; read
mkdir istio-init && cd istio-init && ship init https://github.com/istio/istio/tree/1.2.0/install/kubernetes/helm/istio-init && cd ..
mkdir istio && cd istio && ship init https://github.com/istio/istio/tree/1.2.0/install/kubernetes/helm/istio && cd ..

cat <<HERE > namespace.yaml
apiVersion: v1
kind: Namespace
metadata:
  name: istio-system
HERE

cat <<HERE > kustomization.yaml
resources:
- namespace.yaml
- istio-init/rendered.yaml
- istio/rendered.yaml
HERE

$ kubectl apply -k .

**Environment where bug was observed (cloud vendor, OS, etc)**
On-prem Kubernetes cluster provisioned with kubespray. CentOS7.

Additionally, please consider attaching a [cluster state archive](http://istio.io/help/bugs/#generating-a-cluster-state-archive) by attaching
the dump file to this issue.

Related: https://github.com/istio/istio/issues/7239

Can you attach the output of kubectl get cm -n istio-system istio-sidecar-injector?

It is mostly like you used a lower version istioctl and sidecar-injector when rewriteAppHTTPProbe has not been implemented.

I'd like to see if I can reproduce this using istioctl kube-inject.  Can you include the output of kubectl -n istio-system get cm istio-sidecar-injector -o jsonpath="{.data.config}" and kubectl -n istio-system get cm istio-sidecar-injector -o jsonpath="{.data.values}"?

Can you attach the output of kubectl get cm -n istio-system istio-sidecar-injector?

I'd like to see if I can reproduce this using istioctl kube-inject. Can you include the output of kubectl -n istio-system get cm istio-sidecar-injector -o jsonpath="{.data.config}" and kubectl -n istio-system get cm istio-sidecar-injector -o jsonpath="{.data.values}"?

https://gist.github.com/Timoses/eabeeba43071092e091536d898cb6555

How did you get initContainers: []\n  {{ if ne (annotation .ObjectMeta sidecar.istio.io/interceptionMode    .ProxyConfig.InterceptionMode)NONE }} in your template?
If you look at the generated config you see:
initContainers: []

- name: istio-init

So you are saying initContainer is [] and then go on to provide the initContainers list. It doesn't look like our templates have initContainers: [] ever, did you modify the template?

Thanks for the hint @howardjohn . It appears that Ship somehow manipulated the configmap.
I tested with helm template and it works!
Thanks for the help!


Breaks Teamviewer website and application

Tested with Teamviewer 13 in Windows, Teamviewer works fine in Windows with usual hosts file, but with this hosts file it won't connect to Teamviewer server and also the website won't load.

website works perfectly fine here on windows.Some domains are blocked but they're all nasty ones and don't affect the browsing:
tracking.g2crowd.com
glancecdn.net
s.adroll.com

Yeah I'm not experiencing this at all. I use TeamViewer pretty heavily for work. I can't say anything for the website, as I've only ever touched it to download the client initially, but the client is working perfectly.

Hi @gut5 can you give us a clear example of how Teamviewer is broken for you?


When restart of container is needed, say so and link to documentation

In the troubleshoot section of Introduction to App Service on Linux - Azure | Microsoft Docs
https://docs.microsoft.com/en-us/azure/app-service/containers/app-service-linux-intro#troubleshooting
you say
>  you need to enable Docker Container logging under Diagnostics Logs.
It isn't clear when this takes effect. A link to a common next step, like restarting the app, would be handy also.

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

ID: ef9002ed-c817-c615-fe32-05ad4cc78b61
Version Independent ID: 72295255-8d90-a2c6-0995-0e1208fcdcab
Content: Introduction to App Service on Linux - Azure
Content Source: articles/app-service/containers/app-service-linux-intro.md
Service: app-service
GitHub Login: @naziml
Microsoft Alias: wesmc

@nealmcb, Thank you for your question on this item.
As mentioned in the “Note” in this document- https://docs.microsoft.com/en-us/azure/app-service/troubleshoot-diagnostic-logs#enablediag--“Unlike changing the web.config file, enabling Application diagnostics or changing diagnostic log levels does not recycle the app domain that the application runs within”. So, just to clarify your statement, do you mean that for the changes to take a affect; a restart is necessary or the site restarts after enabling the Docker Container logging/Application Logging and needs to be emphasized in the document?- I noticed a similar behavior, so I have assigned the issue to the content owner to review this further for providing clarity on this point and update the doc as appropriate.

Thank you for pointing me to that page. But it seems either outdated or misleading. I don't see most of the options it shows, only "application logging". No web server logging, detailed error messages, failed request tracing.
And I remember being astonished that you seem to only allow me to get the actual logs via ftp. That protocol became obsolescent many decades ago.
What does it mean to "recycle the app domain"?
I don't know which of your statements about the behavior of Azure are correct. I do mean that when you document any setting, it is important to indicate when that setting will be effective. When you document settings related to startup of a service, you should help readers know how to restart the service, especially when restarting is as difficult as it seems to be in Azure, sometimes hidden behind obscure proprietary PowerShell capabilities.
Note that in general, I'm sad to see that Linux and Python are second-class citizens on Azure, which doesn't support blob storage, and often shows me little popups saying "this feature is not available for Linux apps".

Thank you for your feedback! Agreed that the document needs some enhancement, I have assigned the issue to the content author to review further on the items you pointed out and update the document as appropriate.


fix(viewDirective): fix $element injection for controller

Fix $element injection, and also add a test for it.
closes #2467

thanks!

excellent!


The configsection example has errors

I was reading through the document and tried to use the  portion of sample xml.  However, it appears to have several errors which prevent me from using it directly.
--> type versus Type
--> missing >
--> VS gives an error regarding empty content

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

ID: a149d2bb-ccbf-42d8-5ea4-971fe211fdb6
Version Independent ID: 3bcdf305-4f85-fe4d-24f5-1ce2ecec8d15
Content: Standard and Custom Toolset Configurations - MSBuild
Content Source: docs/msbuild/standard-and-custom-toolset-configurations.md
Product: visual-studio-windows
Technology: msbuild
GitHub Login: @ghogen
Microsoft Alias: ghogen

@alexander-anderson-salesforce Thanks for pointing out the issues with the sample code in this article. We're investigating the issue.

Fixed.
@alexander-anderson-salesforce Thanks for reporting this issue.


Use SSRNormPercent instead of WifeScore for local sort and songwheel grades.

Within a a profile's Etterna.xml, there are two percentages which are stored: WifeScore and SSRNormPercent
WifeScore is simply the number spit out based on the judge you played, while SSRNormPercent is the J4 normalized value. This means that if we were to use this value instead, we could have a clear and simple way to sort local leader boards, as well as display the J4 earned grade on the song wheel to give quick reference of what was actually done.
This would be useful for a few reasons, examples being:

Getting Etterna up to speed with EO in normalizing wife percents on scores
Allowing users to freely switch judges locally and play the same files without having their personal bests be sorted incorrectly.
Allow users to quickly identify their earned grades on song wheel (e.g. having J7 quad runs actually showing on client as quads and not AAs/AAAs).
Incentivizing people to actually utilize higher judges for accuracy feedback, due to the above changes.

While it would be nice, this wouldn't change the listed judgements received. However, proper sorting and listed grades being normalized is a great step in the right direction I feel. It'd be a lot less headache for anyone trying to explore accuracy and swapping judges.

Handled in #698


session.read_csv to support public file accessible via http(s)

Description
I have data files on AWS S3 and it is accessible via a public url.
I would like to be able to use atoti session to read the file e.g.:
asset_positions_store = session.read_csv('http://data.atoti.io/notebooks/collateral-shortfall-monitoring/assets_positions.csv', keys=['Account','Asset_Code'], store_name='asset_positions_store')
Currently I am unable to do so.

You can read s3 files directly with the s3 naming scheme.
E.g. read_csv("s3://bucket/file", ...)

using s3 naming scheme would require AWS authentication and there's no way I can provide via the function call.
Currently I am using wget to download the files to local first before consuming it with read_csv.

There a multiple points here:

Reading public S3 files should work with the s3:// path without login
If we want it as a feature, we need to document how to read private S3 files.
Do we want to support public files with http(s):// path ?

Currently I am using wget to download the files to local first before consuming it with read_csv.

Since pandas supports it, another way is to download the data directly into a pandas dataframe, then you can do some data massaging with pandas and import it in atoti with a read_pandas.

@HuifangYeo can you confirm that you can use the s3 addressing scheme on your bucket if it is publicly accessible (I assume so since it's publicly accessible via http)?

Hi @rcolle,
The bucket access is public:

I tried running below:
x1 = session.read_csv('s3://data.atoti.io/test/assets_positions.csv', keys=['Account','Asset_Code'], store_name='x1')
I get this exception:
AtotiJavaException: An error occurred in the JVM:
An error occurred while calling o2.createStoreFromCsv.
: com.amazonaws.services.s3.model.AmazonS3Exception: Access Denied (Service: Amazon S3; Status Code: 403; Error Code: AccessDenied; Request ID: DD4990643B87B5AA; S3 Extended Request ID: 3IM1lk2gRgjU97l6POVDXJ4euAbjbVZeF5SvU5DLsN2lZ11NFB3cMHloXZ/BY6gv0SFJVsim27o=), S3 Extended Request ID: 3IM1lk2gRgjU97l6POVDXJ4euAbjbVZeF5SvU5DLsN2lZ11NFB3cMHloXZ/BY6gv0SFJVsim27o=

It doesn't look like the public access is correctly set up.
You can check public access by trying to access it via https://data.atoti.io.s3.amazonaws.com/ in a private session.
Since it's in the activeviam account I went ahead and fixed it for you. This should now work.

Hi @rcolle,
I have used wget to download the file locally before consuming it with Atoti. So it is not critical for me to have this feature.
I just thought that it would be useful for users to have it.
Regards

ActivePivot does not support reading directly from http. Moreover you would lose all the performance improvements that come with reading from an object storage (S3, Azure Blob, GCS), and https would be especially slow. So we don't plan in supporting it in the near future.
You can nonetheless directly access your data without the need for wget with the s3 addressing scheme, which I strongly recommend in that case.


Fix issues from building python packages

Fix issues from building python packages (pypi and conda) due to half float supporting.

resolved by https://github.com/apache/singa/pull/872


add version api and show server version in cli

some minor refactor of the cmd package

small comment on wording/displaying the versions @pdevine will have good input on this one too


Alternative trait/lifetime bounds for Engine callbacks?

This is regarding the methods on Engine like on_print, on_debug or on_progress. These functions take a closure of impl Fn(&_) -> _ + SendSync + 'static, which means the closure (1) cannot contain any mutable states unless RefCell is used, and that it (2) cannot borrow anything that outlives the Engine but doesn't have a 'static lifetime.
An example is https://github.com/alvinhochun/rhai-playground/blob/15a1b7e3b9641647979107cefa486587a0d55057/src/scripting.rs#L27 - this code aims to report script execution progress at a reasonable rate with a bit of time tracking. Note that it has to move RefCells into the closure in order to get mutable states. The lifetime issue happens to not matter here because the JavaScript values are all free-to-copy GC'ed references (i.e. doesn't follow Rust ownership rules), but the same code might not work if it is for a native application, or perhaps it would require making a few thread-local static RefCell (or Mutex if the sync feature is enabled)...
I'm wondering if it makes sense for the closures to be impl FnMut(&_) -> _ + SendSync + 'self ('self is a pseudo lifetime) instead, but doing this will require adding a lifetime bound to Engine and probably requires the closures to be passed in on construction? Or maybe there should be another way of customizing the Engine, like making a trait that users can impl for their custom Engine? (I haven't really thought this through, so please forgive me if it doesn't make sense.)

Originally Engine had a lifetime, but then it makes it rather ungainly because most uses will be Engine<'static>.
Maybe I can make a RawEngine<'e> and then pub type Engine = RawEngine<'static>?
I'm not sure if it is worth it just for integrating into a GC-ed environment though...  Outside of such environments, it is rather rare.  And, beware, the Engine can still not hold mutable pointers, unless all Fn gets turned into FnMut.
At the current time, it seems that a RefCell is a small price to pay for such special scenarios...

How about another approach which won't require adding a lifetime to the whole Engine:
Make a ScopedEngine<'_> that provides only the methods to set temporary callbacks (e.g. on_print) and to execute scripts (e.g. call_fn, eval), with other things borrowed from the original Engine, which can be used like this for example:
fn eval_with_engine(
    engine: &Engine,
    script: &str,
) -> Result<(Dynamic, Vec<String>, u64), Box<EvalAltResult>> {
    let mut output = vec![];
    let mut ops_count = 0;
    let result: Dynamic = engine.scoped(|scoped_engine: &mut ScopedEngine| {
        scoped_engine.on_print(|s| {
            output.push(s.to_owned());
        });
        scoped_engine.on_debug(|s| {
            output.push(s.to_owned());
        });
        scoped_engine.on_progess(|&ops| {
            ops_count = ops;
        });
        scoped_engine.eval(script)
    })?;
    Ok((result, output, ops_count))
}

Engine::scoped creates a ScopedEngine with a reference to self, then pass it into the closure (which will be an FnOnce) as a &mut, and then dropped after the closure returns. The callbacks (on_print and etc) are set on the ScopedEngine so they won't need a 'static lifetime and can borrow local variables mutably. These callbacks also override the ones set on the Engine.

I'm not sure if it is worth it just for integrating into a GC-ed environment though...

It's for the opposite (i.e. normal Rust references). I was saying that it doesn't matter for global GC references.

And it may actually not be very slow... since you're only updating the value infrequently.

It's not just about the speed, but also the ergonomics.

But there are a lot more functions in Rhai than just on_print, on_debug and on_progress though...
In fact, every single function right now is limited to being 'static.  If I can relax this requirement, then a command-control object type of scenario can be built very easily without RefCell as I can just pass in a mutable reference to the command object inside a function closure.

How about extending ScopedEngine to support everything? As in, make it so that the user can register any custom functions  through it which will be automatically deregistered at the end of the scope.
This would be alike to how rlua handles lifetime.

Then it would actually be easier to make EngineRaw<'e> and then type Engine = EngineRaw<'static>...

The ScopedEngine approach would allow for the Engine to be reused across multiple invocations, while the EngineRaw approach would require a new Engine instance for every time.
Is the construction of Engine an expensive operation?

Is the construction of Engine an expensive operation?

Engine::new() is... while Engine::new_raw() isn't.

The ScopedEngine approach would allow for the Engine to be reused across multiple invocations, while the EngineRaw approach would require a new Engine instance for every time.

You're probably right, but then ScopedEngine is limited to a number of standard operations, such as dumping all print/debug output to a Vec.  And there is no way to terminate a script in the middle via on_progress other than to keep counting.
It'll work wonders if those operations happen to be what the users want but...

The ScopedEngine approach would allow for the Engine to be reused across multiple invocations, while the EngineRaw approach would require a new Engine instance for every time.

You're probably right, but then ScopedEngine is limited to a number of standard operations, such as dumping all print/debug output to a Vec. And there is no way to terminate a script in the middle via on_progress other than to keep counting.
It'll work wonders if those operations happen to be what the users want but...

Most methods in Engine can be implemented for ScopedEngine, I don't see why not.

Most methods in Engine can be implemented for ScopedEngine, I don't see why not.

Yeah, I know.  But my main point is: we can only implement something that we think the user needs.  Such as logging to a Vec that practically grows unlimited.
However, what we think the user needs may not be what he really needs...
There is no way for the user to pass in his/her own implementation to these callbacks.  They can, but those callbacks must be 'static right now.

There is no way for the user to pass in his/her own implementation to these callbacks. They can, but those callbacks must be 'static right now.

Why not? The point of a ScopedEngine is to allow registering callbacks or callable functions with a scoped lifetime, eliminating the requirement of 'static, so that they can for example mutate local variables. This can enable some patterns that are currently impossible to implement.
Perhaps you can take a look at how rlua handle this with scope (example). It doesn't map to Rhai exactly but is a similar idea.

Hhhmmm... let me look into this some more...

and can borrow local variables mutabl

Not unless I make the function signatures FnMut though... And then the Engine instance must itself be mutable.  Otherwise, it can probably hold a reference, but not a mutable one.

I imagine it this way: The ScopedEngine inherits everything from the Engine but with the ability to override some aspects of it. The overrides only exists for as long as the ScopedEngine is alive. Any mutations only changes the ScopedEngine so there is no need to mutate the Engine itself.

The callbacks (on_print and etc) are set on the ScopedEngine so they won't need a 'static lifetime and can borrow local variables mutably. These callbacks also override the ones set on the Engine.

One question - how do I link up ScopedEngine's on_print with the inner Engine's on_print which takes only 'static while ScopedEngine::on_print takes a lifetime?

The ScopedEngine inherits everything from the Engine

In Rust you can't though... there is no inheritance.

The callbacks (on_print and etc) are set on the ScopedEngine so they won't need a 'static lifetime and can borrow local variables mutably. These callbacks also override the ones set on the Engine.

One question - how do I link up ScopedEngine's on_print with the inner Engine's on_print which takes only 'static while ScopedEngine::on_print takes a lifetime?
I've looked at rlua and there is heavy use of unsafe to do this...

I think there should be no issues because 'static always lives longer than any other lifetimes. rlua needs a lot of unsafe because it interacts with a C library, but for Rhai it should be solvable without the use of unsafe. When you have a reference to it, can't it just be called like normal?

The ScopedEngine inherits everything from the Engine

In Rust you can't though... there is no inheritance.

Not in the OOP sense, but ScopedEngine can contain a reference to the Engine to use its fields.

When you have a reference to it, can't it just be called like normal?

Yes I can call any method and access any field in Engine.  However, I cannot hook up to its callbacks since they are 'static.
I can provide a scoped callback to the outside, but internally there is no way for me to connect the external callback with the internal callback on Engine.

When you have a reference to it, can't it just be called like normal?

Yes I can call any method and access any field in Engine. However, I cannot hook up to its callbacks since they are 'static.
I can provide a scoped callback to the outside, but internally there is no way for me to connect the external callback with the internal callback on Engine.

Oh, I see what you mean. I was thinking of the reverse - you hook the Engine's callback into the ScopedEngine and move the script execution code into ScopedEngine, or refactor them somewhere else and then hope that the compiler can optimize them well enough, that should solve the lifetime issues?

you hook the Engine's callback into the ScopedEngine

But then, inside the closure, ScopedEngine must provide the same functionalities, because it cannot delegate back to the original Engine.
Therefore, essentially you have what I started off with: RawEngine<'e> in the inside, and type Engine = RawEngine<'static> on the outside.

you hook the Engine's callback into the ScopedEngine

But then, inside the closure, ScopedEngine must provide the same functionalities, because it cannot delegate back to the original Engine.
Therefore, essentially you have what I started off with: RawEngine<'e> in the inside, and type Engine = RawEngine<'static> on the outside.

That is somewhat true. Is it possible to make RawEngine "inherit" another existing RawEngine to avoid needing to create fresh ones every time?

But then, inside the closure, ScopedEngine must provide the same functionalities, because it cannot delegate back to the original Engine.

Or perhaps you can have the methods in Engine create a ScopedEngine and delegate to it? Except for the methods that needs to mutate the Engine.

That is somewhat true. Is it possible to make RawEngine "inherit" another existing RawEngine to avoid needing to create fresh ones every time?

Not really... can't do that in Rust.

Or perhaps you can have the methods in Engine create a ScopedEngine and delegate to it? Except for the methods that needs to mutate the Engine.

Delegation also no...

Surely something should be doable? Perhaps some refactoring may help?

I am thinking.
I tried refactoring to add lifetimes to Engine but then it seems to change thirty million lines of code and there are many references with different lifetimes and the borrow checker basically puked the whole thing back to me...

Closing this for now, as it probably won't change any time soon.


Intercom initialization

I am trying to get Intercom initialized via segment. It does not look like working as expected,
Refer this.
Here is the sample payload.
Couldn't find enough documentation on this.
dispatch({
  type: 'INTERCOM_INIT',
  meta: {
    analytics: {
      eventType: EventTypes.identify,
      eventPayload: {
        email,
        integrations: {
          Intercom: {
            hideDefaultLauncher: true,
          },
        },
        traits: {
          email,
        },
      },
    },
  },
});

Fixed it as below,
dispatch({
  type: 'INTERCOM_INIT',
  meta: {
    analytics: {
      eventType: EventTypes.identify,
      eventPayload: {
        email,
        options: {
          Intercom: {
            hideDefaultLauncher: true,
          },
        },
        traits: {
          email,
        },
      },
    },
  },
});

Ah, thanks @anupvarghese. There's a documentation overhaul ongoing that should help in cases like these.


A typo in one of the wiki pages?

In one of the wiki pages, Incrementally-Agerifying-legacy-code, there seems to be a typing mistake. In the sample code of Exposing synchronous operations as repositories, did you mean Repositories.repositoryWithInitialValue(Result<ResponseBlob>.absent()) rather than the expression        Repositories.repositoryWithInitialValue(Result.<ResponseBlob>absent()) ?

ClassName.<TypeParam>staticMethodName() is the right Java syntax :)

I sincerely apologize.


Enabling the page to be refreshed without a HashRouter

No longer applicable: Issue only occurs with current local developer set-up


Attribute errors in protein_example_1.py

For P.disorder and P.is_IDP

Should be P.predictor.disorder()

closing with a8bcc60


Ionic Serve Fails After Adding Ionic Cloud Angular

Hi,
I'm having problems getting the cloud client installed and the project to serve properly. I'm getting an error in the Chrome console that states: "Uncaught TypeError: angular.element is not a function(...)" and a white screen.
This is a problem when running 'ionic serve'. Running 'ionic emulate ios' works. It's really inconvenient because it's so fast to do much of the development in the browser.
To eliminate my existing project quirks, I decided to reproduce it on a fresh project. I then verified that ionic serve was working. After that, I followed the Cloud Module installation steps here: http://docs.ionic.io/setup.html
This is what my app.module.ts file looks like:
import { NgModule, ErrorHandler } from '@angular/core';
import { IonicApp, IonicModule, IonicErrorHandler } from 'ionic-angular';
import { MyApp } from './app.component';
import { AboutPage } from '../pages/about/about';
import { ContactPage } from '../pages/contact/contact';
import { HomePage } from '../pages/home/home';
import { TabsPage } from '../pages/tabs/tabs';
import { CloudSettings, CloudModule } from '@ionic/cloud-angular';
const cloudSettings: CloudSettings = {
'core': {
'app_id': 'f18445ea'
}
};
@NgModule({
declarations: [
MyApp,
AboutPage,
ContactPage,
HomePage,
TabsPage
],
imports: [
IonicModule.forRoot(MyApp),
CloudModule.forRoot(cloudSettings)
],
bootstrap: [IonicApp],
entryComponents: [
MyApp,
AboutPage,
ContactPage,
HomePage,
TabsPage
],
providers: [{provide: ErrorHandler, useClass: IonicErrorHandler}]
})
export class AppModule {}
If I go back into my app.module.ts and comment out the CloudModule.forRoot(cloudSettings) line in the imports, it will serve again properly. I also noticed that the main.js file in www/build is larger when CloudModule is present (which makes sense). However, on my existing project it's much smaller which is strange. This is leading me to believe that there's something going on with the build process. I also tried deleting my node_modules directory and doing an npm install. I still have the same problem. :(
Still, if I can at least get this working on a blank starter project with your help, it could clue me in as to what is going on with my other project.
Here is my ionic info:
Cordova CLI: 6.1.1
Ionic Framework Version: 2.0.0-rc.3
Ionic CLI Version: 2.1.13
Ionic App Lib Version: 2.1.7
Ionic App Scripts Version: 0.0.45
ios-deploy version: 1.8.6
ios-sim version: 5.0.8
OS: OS X El Capitan
Node Version: v6.9.1
Xcode version: Xcode 7.3 Build version 7D175
Your help is very much appreciated,
Amy

FYI: I just tried deleting my node_modules directory and doing an npm install. I still have the same problem. :(

Update: Did an install on a different machine and the starter site serve worked with the Cloud module installed and configured. It must be something with my environment. The only thing I can think of that's a recent change is that I installed Typings globally for Leaflet.
If you have no suggestions that come to mind, this issue can be closed.

The only way I could think of this happening is if angular is defined on window but it is not angular 1.
I realize this is an Angular 2 project, but somehow it got past this if statement: https://github.com/driftyco/ionic-cloud/blob/master/src/angular.ts#L11-L13

Update: I found that disabling the AngularJS Batarang extension in Chrome resolved this problem!


[stable/redis] Upgrade exporter to 0.25.0.

What this PR does / why we need it:
Which issue this PR fixes
(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

fixes #

Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped

/lgtm


tests: upload WASM plugins to kind-registry to avoid DNS issues in IPv6 clusters

Please provide a description of this PR:
Fixes #35915.
This comment explains why do we have to upload WASM plugins to kind-registry before running tests. Additionally, I had to patch CoreDNS config map, because kind-registry is not resolvable in IPv6-only cluster.
First https://github.com/istio/istio/pull/51779 must be merged.

@jewertow: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-telemetry-discovery_istio
4fc8e0079bafa795bdcbf9db03eb4ab4d36ad421
link
true
/test integ-telemetry-discovery

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@jewertow: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-telemetry-discovery_istio
4fc8e0079bafa795bdcbf9db03eb4ab4d36ad421
link
true
/test integ-telemetry-discovery

integ-telemetry_istio
4fc8e0079bafa795bdcbf9db03eb4ab4d36ad421
link
true
/test integ-telemetry

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@jewertow: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-telemetry-discovery_istio
4fc8e0079bafa795bdcbf9db03eb4ab4d36ad421
link
true
/test integ-telemetry-discovery

integ-telemetry_istio
4fc8e0079bafa795bdcbf9db03eb4ab4d36ad421
link
true
/test integ-telemetry

integ-telemetry-istiodremote_istio
4fc8e0079bafa795bdcbf9db03eb4ab4d36ad421
link
true
/test integ-telemetry-istiodremote

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@jewertow: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-telemetry-discovery_istio
4fc8e0079bafa795bdcbf9db03eb4ab4d36ad421
link
true
/test integ-telemetry-discovery

integ-telemetry_istio
4fc8e0079bafa795bdcbf9db03eb4ab4d36ad421
link
true
/test integ-telemetry

integ-telemetry-istiodremote_istio
4fc8e0079bafa795bdcbf9db03eb4ab4d36ad421
link
true
/test integ-telemetry-istiodremote

lint_istio
4fc8e0079bafa795bdcbf9db03eb4ab4d36ad421
link
true
/test lint

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@jewertow: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-telemetry-discovery_istio
4fc8e0079bafa795bdcbf9db03eb4ab4d36ad421
link
true
/test integ-telemetry-discovery

integ-telemetry_istio
4fc8e0079bafa795bdcbf9db03eb4ab4d36ad421
link
true
/test integ-telemetry

integ-telemetry-istiodremote_istio
4fc8e0079bafa795bdcbf9db03eb4ab4d36ad421
link
true
/test integ-telemetry-istiodremote

lint_istio
4fc8e0079bafa795bdcbf9db03eb4ab4d36ad421
link
true
/test lint

gencheck_istio
4fc8e0079bafa795bdcbf9db03eb4ab4d36ad421
link
true
/test gencheck

integ-telemetry-mc_istio
4fc8e0079bafa795bdcbf9db03eb4ab4d36ad421
link
true
/test integ-telemetry-mc

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@jewertow: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-telemetry-discovery_istio
4fc8e0079bafa795bdcbf9db03eb4ab4d36ad421
link
true
/test integ-telemetry-discovery

integ-telemetry_istio
4fc8e0079bafa795bdcbf9db03eb4ab4d36ad421
link
true
/test integ-telemetry

integ-telemetry-mc_istio
4fc8e0079bafa795bdcbf9db03eb4ab4d36ad421
link
true
/test integ-telemetry-mc

integ-telemetry-istiodremote_istio
26e52d266244073a4d0bdec6d63c62dbaceda134
link
true
/test integ-telemetry-istiodremote

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@jewertow: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-telemetry-discovery_istio
4fc8e0079bafa795bdcbf9db03eb4ab4d36ad421
link
true
/test integ-telemetry-discovery

integ-telemetry_istio
4fc8e0079bafa795bdcbf9db03eb4ab4d36ad421
link
true
/test integ-telemetry

integ-telemetry-istiodremote_istio
26e52d266244073a4d0bdec6d63c62dbaceda134
link
true
/test integ-telemetry-istiodremote

integ-telemetry-mc_istio
26e52d266244073a4d0bdec6d63c62dbaceda134
link
true
/test integ-telemetry-mc

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

/retest

@jewertow: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-telemetry-discovery_istio
4fc8e0079bafa795bdcbf9db03eb4ab4d36ad421
link
true
/test integ-telemetry-discovery

integ-telemetry_istio
4fc8e0079bafa795bdcbf9db03eb4ab4d36ad421
link
true
/test integ-telemetry

integ-telemetry-mc_istio
26e52d266244073a4d0bdec6d63c62dbaceda134
link
true
/test integ-telemetry-mc

integ-telemetry-istiodremote_istio
26e52d266244073a4d0bdec6d63c62dbaceda134
link
true
/test integ-telemetry-istiodremote

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@jewertow: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-telemetry-discovery_istio
4fc8e0079bafa795bdcbf9db03eb4ab4d36ad421
link
true
/test integ-telemetry-discovery

integ-telemetry_istio
4fc8e0079bafa795bdcbf9db03eb4ab4d36ad421
link
true
/test integ-telemetry

integ-telemetry-istiodremote_istio
26e52d266244073a4d0bdec6d63c62dbaceda134
link
true
/test integ-telemetry-istiodremote

integ-telemetry-mc_istio
26e52d266244073a4d0bdec6d63c62dbaceda134
link
true
/test integ-telemetry-mc

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@jewertow: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-telemetry-discovery_istio
4fc8e0079bafa795bdcbf9db03eb4ab4d36ad421
link
true
/test integ-telemetry-discovery

integ-telemetry_istio
4fc8e0079bafa795bdcbf9db03eb4ab4d36ad421
link
true
/test integ-telemetry

integ-telemetry-istiodremote_istio
26e52d266244073a4d0bdec6d63c62dbaceda134
link
true
/test integ-telemetry-istiodremote

integ-telemetry-mc_istio
26e52d266244073a4d0bdec6d63c62dbaceda134
link
true
/test integ-telemetry-mc

integ-helm_istio
26e52d266244073a4d0bdec6d63c62dbaceda134
link
false
/test integ-helm

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@jewertow: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-telemetry-discovery_istio
4fc8e0079bafa795bdcbf9db03eb4ab4d36ad421
link
true
/test integ-telemetry-discovery

integ-telemetry-istiodremote_istio
26e52d266244073a4d0bdec6d63c62dbaceda134
link
true
/test integ-telemetry-istiodremote

integ-telemetry-mc_istio
26e52d266244073a4d0bdec6d63c62dbaceda134
link
true
/test integ-telemetry-mc

integ-helm_istio
26e52d266244073a4d0bdec6d63c62dbaceda134
link
false
/test integ-helm

integ-telemetry_istio
26e52d266244073a4d0bdec6d63c62dbaceda134
link
true
/test integ-telemetry

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@jewertow: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-telemetry-istiodremote_istio
26e52d266244073a4d0bdec6d63c62dbaceda134
link
true
/test integ-telemetry-istiodremote

integ-telemetry-mc_istio
26e52d266244073a4d0bdec6d63c62dbaceda134
link
true
/test integ-telemetry-mc

integ-helm_istio
26e52d266244073a4d0bdec6d63c62dbaceda134
link
false
/test integ-helm

integ-telemetry_istio
26e52d266244073a4d0bdec6d63c62dbaceda134
link
true
/test integ-telemetry

integ-telemetry-discovery_istio
26e52d266244073a4d0bdec6d63c62dbaceda134
link
true
/test integ-telemetry-discovery

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

/retest

@jewertow: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-telemetry-mc_istio
26e52d266244073a4d0bdec6d63c62dbaceda134
link
true
/test integ-telemetry-mc

integ-telemetry_istio
26e52d266244073a4d0bdec6d63c62dbaceda134
link
true
/test integ-telemetry

integ-telemetry-discovery_istio
26e52d266244073a4d0bdec6d63c62dbaceda134
link
true
/test integ-telemetry-discovery

integ-telemetry-istiodremote_istio
eff6c3de1a539bb2e4efddf5cfaddc0ab4b653a3
link
true
/test integ-telemetry-istiodremote

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@jewertow: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-telemetry_istio
26e52d266244073a4d0bdec6d63c62dbaceda134
link
true
/test integ-telemetry

integ-telemetry-discovery_istio
26e52d266244073a4d0bdec6d63c62dbaceda134
link
true
/test integ-telemetry-discovery

integ-telemetry-istiodremote_istio
eff6c3de1a539bb2e4efddf5cfaddc0ab4b653a3
link
true
/test integ-telemetry-istiodremote

integ-telemetry-mc_istio
eff6c3de1a539bb2e4efddf5cfaddc0ab4b653a3
link
true
/test integ-telemetry-mc

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@jewertow: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-telemetry_istio
26e52d266244073a4d0bdec6d63c62dbaceda134
link
true
/test integ-telemetry

integ-telemetry-istiodremote_istio
eff6c3de1a539bb2e4efddf5cfaddc0ab4b653a3
link
true
/test integ-telemetry-istiodremote

integ-telemetry-mc_istio
eff6c3de1a539bb2e4efddf5cfaddc0ab4b653a3
link
true
/test integ-telemetry-mc

integ-telemetry-discovery_istio
eff6c3de1a539bb2e4efddf5cfaddc0ab4b653a3
link
true
/test integ-telemetry-discovery

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@jewertow: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-telemetry-istiodremote_istio
eff6c3de1a539bb2e4efddf5cfaddc0ab4b653a3
link
true
/test integ-telemetry-istiodremote

integ-telemetry-mc_istio
eff6c3de1a539bb2e4efddf5cfaddc0ab4b653a3
link
true
/test integ-telemetry-mc

integ-telemetry-discovery_istio
eff6c3de1a539bb2e4efddf5cfaddc0ab4b653a3
link
true
/test integ-telemetry-discovery

integ-telemetry_istio
eff6c3de1a539bb2e4efddf5cfaddc0ab4b653a3
link
true
/test integ-telemetry

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

/retest

@jewertow: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-telemetry-istiodremote_istio
eff6c3de1a539bb2e4efddf5cfaddc0ab4b653a3
link
true
/test integ-telemetry-istiodremote

integ-telemetry-mc_istio
eff6c3de1a539bb2e4efddf5cfaddc0ab4b653a3
link
true
/test integ-telemetry-mc

integ-telemetry_istio
eff6c3de1a539bb2e4efddf5cfaddc0ab4b653a3
link
true
/test integ-telemetry

integ-telemetry-discovery_istio
9e26d95eb6aba226da9146c6805a501f94a68d71
link
true
/test integ-telemetry-discovery

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@jewertow: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-telemetry-istiodremote_istio
eff6c3de1a539bb2e4efddf5cfaddc0ab4b653a3
link
true
/test integ-telemetry-istiodremote

integ-telemetry-mc_istio
eff6c3de1a539bb2e4efddf5cfaddc0ab4b653a3
link
true
/test integ-telemetry-mc

integ-telemetry-discovery_istio
9e26d95eb6aba226da9146c6805a501f94a68d71
link
true
/test integ-telemetry-discovery

integ-telemetry_istio
9e26d95eb6aba226da9146c6805a501f94a68d71
link
true
/test integ-telemetry

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@jewertow: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-telemetry-mc_istio
eff6c3de1a539bb2e4efddf5cfaddc0ab4b653a3
link
true
/test integ-telemetry-mc

integ-telemetry-discovery_istio
9e26d95eb6aba226da9146c6805a501f94a68d71
link
true
/test integ-telemetry-discovery

integ-telemetry_istio
9e26d95eb6aba226da9146c6805a501f94a68d71
link
true
/test integ-telemetry

integ-telemetry-istiodremote_istio
9e26d95eb6aba226da9146c6805a501f94a68d71
link
true
/test integ-telemetry-istiodremote

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@jewertow: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-telemetry-discovery_istio
9e26d95eb6aba226da9146c6805a501f94a68d71
link
true
/test integ-telemetry-discovery

integ-telemetry_istio
9e26d95eb6aba226da9146c6805a501f94a68d71
link
true
/test integ-telemetry

integ-telemetry-istiodremote_istio
9e26d95eb6aba226da9146c6805a501f94a68d71
link
true
/test integ-telemetry-istiodremote

integ-telemetry-mc_istio
9e26d95eb6aba226da9146c6805a501f94a68d71
link
true
/test integ-telemetry-mc

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

/retest

nice work, great to see this land!

hope there is no change or impact on https://github.com/istio/istio/blob/master/tests/integration/ambient/wasm_test.go#L72

JFYI: the postsubmit job failed with the following error:
2024-07-03T10:07:02.735383Z	warn	delta	ADS:ECDS: ACK ERROR b-v1-6f564645d5-2ddzq.echo-3-51866-6 Internal:cannot fetch Wasm module oci://[fd00:10:96::4456]:1338/istio-testing/wasm/attributegen:0.0.1: could not fetch Wasm OCI image: could not fetch manifest: Get "http://kind-registry:5000/v2/istio-testing/wasm/attributegen/manifests/0.0.1": dial tcp: lookup kind-registry on [fd00:10:96::a]:53: server misbehaving

I am looking at this issue.

@ilrudie on an old image I saw the same but the latest it works, maybe you had an old cached image..?

Ah, could be I wasn't quite up to date. Odd thing is I can find crane if I make shell so it should be in whatever image I was using

I'm using build-tools master-3a1982fd09c72f345f85d394d5cce906b5484b76
For a sanity check I deleted the image and pulled it fresh, same results.


Warning - Add user to project

As a user, I want to see a warning if I want to add another user to my project that the user has been a member of.

https://github.com/Cloud1e/17155_1_Project/commit/ea703c63f73916373862ad1dbeaaf83fcd7a205e


tf2.1 with gpu can't open cuda 10.2

Please make sure that this is a build/installation issue. As per our GitHub Policy, we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:build_template
System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04):  windows 10 (profession)
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device:
TensorFlow installed from (source or binary):
TensorFlow version: v2.1.0-rc2-17-ge5bf8de410
Python version:  3.68
Installed using virtualenv? pip? conda?:  pip
Bazel version (if compiling from source):
GCC/Compiler version (if compiling from source):
CUDA/cuDNN version: 10.2 cuda / 7.6 cudnn
GPU model and memory:  2G

Describe the problem
ERROR: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] cannot opened dynamic library cudart64_101.dll
Provide the exact sequence of commands / steps that you executed before running into the problem
My computer has windows 10 professional vesion os, and GPU-GTX1050. Then Install the cuda 10.2 and cudnn 7.6 version.  I use Pycharm professional version create a virtual env. Wait a moment, use pip install the tensorflow-2.1-gpu version, successfully. When I test the tensorflow2.1-gpu version, it arises the error "cannot opened dynamic library cudart64_101.dll".
How do I resolve?
Maybe It is something wrong with cuda10.2, therefore ,I search the dir where i install the cuda. I find the directory-bin which has cudart64_102.dll , not cudart64_101.dll. For safely, i copy cudart64_102.dll, and rename , push into the bin directory.
Then i rerun the tf, it can work...
2020-03-03 16:38:19.699659: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library cudart64_101.dll
Any other info / logs
Maybe it is something wrong with cuda10.2 and tensorflow-2.1-gpu.
Tensorflow can't find the cudart64_101.dll. The cuda10.2 has not cudart64_101.dll, but has cudart64_102.dll. Ok, it should be the api.

@jacketchan, Tensorflow-gpu==2.1 supports CUDA 10.1 which will have cudart64_101.dll file.
Since, CUDA 10.2 will have cudart64_102.dll file which is not supported by Tensorflow 2.1.
Please downgrade the CUDA version to 10.1. Let us know how it progresses. Thanks!

You can try this

@jacketchan, Issue still persists?

Since the title of the issue is resolved.Closing this issue. Thanks


 tag prop not working

Version
4.0.1
Reproduction link
https://jsfiddle.net/4o1xpqwf/
Steps to reproduce
I need to render "router-link" as an "li" tag. So I pass a tag property equal "li" (I also try "div", "span" and "button" - it's does't matter). Just like here: https://router.vuejs.org/api/#tag
What is expected?
router-link to render as a "li" DOM element
What is actually happening?
It's render as an "a" DOM element with prop "tag=li" and empty "class"

https://next.router.vuejs.org/guide/migration/index.html#removal-of-event-and-tag-props-in-router-link


[question] calendar, filter on category

Is it possible to filter events based  on one or more categories?
For example, tag your calendar entry with the category family, to show it on the family board

Currently not but feel free to send a PR.

What you could do is to create a google sub-calender called family with the entries and include it in the family board.
Or name every entry something with "Family: " and have MM filter them out (there are filter rules implemented into the code)
However, you would need to do something with the events in the original calendar, don't you?
I can't see away to "tag" inside the MagicMirror framework.

What you could do is to create a google sub-calender called family with the entries and include it in the family board.

But then you have to re-enter family appointments again..

However, you would need to do something with the events in the original calendar, don't you?

In my business calendar I want to tag events that should be visible on the 'family calender'/magic mirror.


chore(website): fix missing link to API docs in mobile view

Description

Issue #1431 fixed, changes the mobile nav menu to include API docs link.
Related issue(s)

Fixes https://github.com/asyncapi/modelina/issues/1431

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
5259

Relevant Lines:
5562

💛  - Coveralls


cmake: linker: arm: put RAM sections in RAM region

Cleanup RAM layout so that the RAM_REGION is now in the RAM memory region.  Put .bss in RAM_REGION.
This means we have a proper program header for the RAM region.
As part of this extend zephyr_linker_symbol to allow it to take an OBJECT paramater to specify the region to associate a symbol to.

Want to make sure we get @tejlmand review on this.


Fix TextSpan gc regression

for (final InlineSpan child in children ?? const <InlineSpan>[]) bad
Fixes https://github.com/flutter/flutter/issues/126337
Pre-launch Checklist

[ ] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[ ] I read the Tree Hygiene wiki page, which explains my responsibilities.
[ ] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[ ] I signed the CLA.
[ ] I listed at least one issue that this PR fixes in the description above.
[ ] I updated/added relevant documentation (doc comments with ///).
[ ] I added new tests to check the change I am making, or this PR is test-exempt.
[ ] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

test-exempt: code refactor with no semantic change


Fix Streamed Json Encoding

Fixes #3890
Questions: Is this a good chunk size? should we make it configurable in other versions? how does this relate to the benches for cutoff?
This should see a reduction in buffer flushes of 2000x

Questions: Is this a good chunk size? should we make it configurable in other versions? how does this relate to the benches for cutoff?

Could or should this turned into a parameter of the functions, even at a later PR?

Part of the untyped contract of encoders is that it flushes per chunk. It's the only way the user can control when partial results become available.
Instead of an arbitrary limit, could we intersperse each Chunk[Json] with a comma, and then intersperse those chunks as we do now?  It would still be slow if each Json were its own chunk, but reasonable, and easy to control, if the Jsons came in larger chunks.

That's what the most recent commit is. Each incoming chunk gets written, interpolated with the commas, and then rechunked.
The first chunk gets special treatment because it has different logic than the comma interpolation. Sorry, original PR description is now wrong with what the code implements.
As currently written outputs chunks
Chunk1 [ and first json
RestOfChunk1 , and then json in the same as the input chunk
RestofChunks The same as RestOfChunk1 except for the very last one which does not get the ,
ChunkContaining ], I really don't like this one, but don't have a good way to work it into the last chunk.


Crictl returning Internal Server Error when i try to pull images from it.

What happened:
When i try to pull a image from my nexus private repository using the command crictl --debug pull , CRIO didnt pull the image and show the error:
DEBU[0000] PullImageRequest: &PullImageRequest{Image:&ImageSpec{Image:,Annotations:map[string]string{},},Auth:nil,SandboxConfig:nil,}
E1002 17:49:13.548119 2819941 remote_image.go:167] "PullImage from image service failed" err="rpc error: code = Unknown desc = pinging container registry : Get "https:///v2/": Internal Server Error" image="/:tag"
FATA[0000] pulling image: rpc error: code = Unknown desc = pinging container registry repo-ace.infoacesso.internal.timbrasil.com.br: Get "https:///v2/": Internal Server Error
This error occurs to any image i try to use from that repository and occurs in all machines of the cluster.
What you expected to happen:
The commands download the image succesfully.
How to reproduce it (as minimally and precisely as possible):
-> Set Up a external Nexus docker hosted repository running on RKE2 and build any image.
-> Set Up an OpenShift Cluster
-> Try to download any image from the nexus private repository using the command crictl pull
Anything else we need to know?:
I have an HML enverionment running openshift too and from that HML cluster, crioctl works normally.
The funny thing is when i try to use the image using podman pull, its works normally, only with crictl this problem occurs, openshift uses crictl to run pod images, so even with podman working normally, my pod will return a crashLoopBackOff error because the crictl didint work.
Environment:

Container runtime or hardware configuration:
3 Master 5 Workers

OS (e.g: cat /etc/os-release):
NAME="Red Hat Enterprise Linux CoreOS"
ID="rhcos"
ID_LIKE="rhel fedora"
VERSION="414.92.202406041802-0"
VERSION_ID="4.14"
VARIANT="CoreOS"
VARIANT_ID=coreos
PLATFORM_ID="platform:el9"
PRETTY_NAME="Red Hat Enterprise Linux CoreOS 414.92.202406041802-0 (Plow)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:redhat:enterprise_linux:9::coreos"
HOME_URL="https://www.redhat.com/"
DOCUMENTATION_URL="https://docs.openshift.com/container-platform/4.14/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_BUGZILLA_PRODUCT="OpenShift Container Platform"
REDHAT_BUGZILLA_PRODUCT_VERSION="4.14"
REDHAT_SUPPORT_PRODUCT="OpenShift Container Platform"
REDHAT_SUPPORT_PRODUCT_VERSION="4.14"
OPENSHIFT_VERSION="4.14"
RHEL_VERSION="9.2"
OSTREE_VERSION="414.92.202406041802-0"

Kernel (e.g. uname -a):
Linux sneappnwmprd01 5.14.0-284.69.1.el9_2.x86_64 #1 SMP PREEMPT_DYNAMIC Fri May 31 14:47:07 EDT 2024 x86_64 x86_64 x86_64 GNU/Linux

Others:
OpenShift 4.14.29

I don't think this has anything immediately to do with our CLI. We don't pull anything, we ask CRI to pull the image for us.

@Anddiy, if you can reproduce this and if you believe this is an issue that is not within your infrastructure or environment, then feel free to open an issue against CRI-O so it can be tracked there.


Adds of OrderTicker UpdateXXX Methods

Expected Behavior
Be able to update an order ticker with just one method call.
Actual Behavior
We need to create a UpdateOrderFields object to use in OrderTicket.Update.
Potential Solution
Add the following methods:
OrderTicket.Update(string tag, decimal? quantity = null, decimal? limitPrice = null, decimal? stopPrice = null)
or
OrderTicket.UpdateTag(string tag)
and
OrderTicket.UpdateQuantity(decimal quantity, string tag = null)
OrderTicket.UpdateLimitPrice(decimal limitPrice, string tag = null)
OrderTicket.UpdateStopPrice(decimal stopPrice, string tag = null)
Checklist

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

Implemented in #3876


Calculating overall metris now fails with error on return int(rating) >= 4

console looked like:
python3 -m scripts evaluate --config=example_config.json --numquestions=14

error looked like
2024-01-13 00:04:04 (INFO) scripts: Running evaluation from config /workspaces/ai-rag-chat-evaluator/example_config.json
2024-01-13 00:04:04 (INFO) scripts: Replaced results_dir in config with timestamp
2024-01-13 00:04:04 (INFO) scripts: Replaced prompt_template in config with contents of example_input/prompt_refined.txt
2024-01-13 00:04:05 (INFO) azure.identity._internal.decorators: AzureDeveloperCliCredential.get_token succeeded
2024-01-13 00:04:05 (INFO) scripts: Running evaluation using data from /workspaces/ai-rag-chat-evaluator/example_input/qa-2.jsonl
2024-01-13 00:04:05 (INFO) scripts: Limiting evaluation to 14 questions
2024-01-13 00:04:05 (INFO) scripts: Sending a test question to the target to ensure it is running...
2024-01-13 00:04:28 (INFO) scripts: Starting evaluation...
Fail writing properties '{'_azureml.evaluation_run': 'azure-ai-generative-parent'}' to run history: 'FileStore' object has no attribute 'get_host_creds'
2024-01-13 00:04:28 (WARNING) azureml-metrics: Computing metrics for {'gpt_relevance', 'gpt_groundedness', 'gpt_coherence'} as y_test is None.
2024-01-13 00:04:28 (INFO) azureml-metrics: Setting max_concurrent_requests to 4 for computing GPT based question answering metrics
2024-01-13 00:04:28 (INFO) azureml-metrics: [azureml-metrics] ActivityStarted: compute_metrics-qa, ActivityType: ComputeMetrics, CustomDimensions: {'app_name': 'azureml-metrics', 'task_type': 'qa', 'azureml_metrics_run_id': 'c4410548-31bf-4409-a474-f327248fd0ca', 'current_timestamp': '2024-01-13 00:04:28'}
2024-01-13 00:04:28 (WARNING) azureml.metrics.text.qa.azureml_qa_metrics: LLM related metrics need llm_params to be computed. Computing metrics for ['gpt_relevance', 'gpt_groundedness', 'gpt_coherence']
2024-01-13 00:04:28 (INFO) azureml.metrics.common._validation: QA metrics debug: {'y_test_length': 0, 'y_pred_length': 14, 'tokenizer_example_output': 'the quick brown fox jumped over the lazy dog', 'regexes_to_ignore': '', 'ignore_case': False, 'ignore_punctuation': False, 'ignore_numbers': False}
2024-01-13 00:04:28 (WARNING) azureml.metrics.text.qa._seq2seq_qa: gpt_relevance metric is not applicable as it needs question and context for every example.
2024-01-13 00:04:28 (ERROR) azureml.metrics.rai.groundedness._groundedness_base: Contexts not provided.
100%|█████████████████████████████████████████████████████████████████████████████████████████████████████████| 14/14 [00:05<00:00,  2.46it/s]
/home/vscode/.local/lib/python3.11/site-packages/azureml/metrics/common/utilities.py:293: RuntimeWarning: Mean of empty slice
  metrics_result[constants.Metric.Metrics][mean_metric_name] = np.nanmean(metric_value)
/home/vscode/.local/lib/python3.11/site-packages/azureml/metrics/common/utilities.py:294: RuntimeWarning: All-NaN slice encountered
  metrics_result[constants.Metric.Metrics][median_metric_name] = np.nanmedian(metric_value)
2024-01-13 00:04:34 (INFO) azureml-metrics: [azureml-metrics] ActivityCompleted: Activity=compute_metrics-qa, HowEnded=SUCCESS, Duration=5735.52[ms]
Fail writing properties '{'_azureml.evaluate_artifacts': '[{"path": "eval_results.jsonl", "type": "table"}]'}' to run history: 'FileStore' object has no attribute 'get_host_creds'
2024-01-13 00:04:34 (INFO) scripts: Evaluation calls have completed. Calculating overall metrics now...
Traceback (most recent call last):

  File "<frozen runpy>", line 198, in _run_module_as_main

  File "<frozen runpy>", line 88, in _run_code

  File "/workspaces/ai-rag-chat-evaluator/scripts/__main__.py", line 6, in <module>
    app()

  File "/workspaces/ai-rag-chat-evaluator/scripts/cli.py", line 27, in evaluate
    run_evaluate_from_config(Path.cwd(), config, numquestions)

  File "/workspaces/ai-rag-chat-evaluator/scripts/evaluate.py", line 175, in run_evaluate_from_config
    run_evaluation(

  File "/workspaces/ai-rag-chat-evaluator/scripts/evaluate.py", line 117, in run_evaluation
    if passes_threshold(question_with_rating[metric_name]):
       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

  File "/workspaces/ai-rag-chat-evaluator/scripts/evaluate.py", line 109, in passes_threshold
    return int(rating) >= 4
           ^^^^^^^^^^^

TypeError: int() argument must be a string, a bytes-like object or a real number, not 'NoneType'

eval_results.jsonl is
{"question":"What is the focus of the Financial Market Analysis Report 2023 prepared by Contoso Financial Analytics?","answer":"The Financial Market Analysis Report 2023 prepared by Contoso Financial Analytics provides a deep dive into the financial markets of 2023, focusing on the trends and fluctuations within stocks, cryptocurrencies, and commodities. It covers historical patterns, current market conditions, and future predictions.\n[Financial Market Analysis Report 2023.pdf#page=1]","gpt_relevance":null,"gpt_groundedness":null,"gpt_coherence":5}
{"question":"What does the global financial market consist of according to the Financial Market Analysis Report 2023?","answer":"According to the Financial Market Analysis Report 2023, the global financial market is a vast and intricate network of exchanges, instruments, and assets, ranging from traditional stocks and bonds to modern cryptocurrencies and commodities.[Financial Market Analysis Report 2023.pdf#page=1]","gpt_relevance":null,"gpt_groundedness":null,"gpt_coherence":5}
{"question":"What is the Northwind Standard plan offered by Contoso in partnership with Northwind Health and what does it provide?","answer":"The Northwind Standard plan is a health insurance plan offered by Contoso in partnership with Northwind Health. This plan provides a balance billing protection, meaning that you are protected from unexpected costs when visiting in-network providers.\n[Northwind_Standard_Benefits_Details.pdf#page=7]","gpt_relevance":null,"gpt_groundedness":null,"gpt_coherence":5}
{"question":"What is balance billing and how does the Northwind Standard plan protect against it? What is an in-network provider and what happens if you visit an out-of-network provider?","answer":"Balance billing is when a provider bills you for the difference between what they charge and what your insurance company is willing to pay. This difference can be hundreds of dollars and is often unexpected. The Northwind Standard plan protects you from balance billing when visiting in-network providers. In-network providers are healthcare providers, such as doctors, hospitals, and labs, that have agreed to accept the Northwind Standard plan's payment terms. Visiting an in-network provider means that you are protected from balance billing. If you visit an out-of-network provider, you may not be protected from balance billing.[Northwind_Standard_Benefits_Details.pdf#page=7]","gpt_relevance":null,"gpt_groundedness":null,"gpt_coherence":5}
{"question":"What is the difference between in-network and out-of-network providers in the context of Northwind Health?","answer":"In-network providers have agreed to accept the amount of payment offered by Northwind Health and you pay the portion of the cost that is not covered by the insurance plan. They may also offer additional services or discounts that are not available to out-of-network providers. Out-of-network providers, on the other hand, have not contracted with Northwind Health and are not required to accept the amount of payment offered by Northwind Health. This means you may be responsible for a greater portion of the cost and they may not offer additional services or discounts that are available to in-network providers.\n[Northwind_Standard_Benefits_Details.pdf#page=8]","gpt_relevance":null,"gpt_groundedness":null,"gpt_coherence":5}
{"question":"What should one consider when choosing a provider in the context of Northwind Health?","answer":"When choosing a provider, it is important to make sure that the provider is in-network. While it is possible to receive care from out-of-network providers, it is important to understand that you will be responsible for a greater portion of the costs. To make sure that you are getting the best value for your health care expenses, it is recommended that you choose an in-network provider whenever possible.[Northwind_Standard_Benefits_Details.pdf#page=8]","gpt_relevance":null,"gpt_groundedness":null,"gpt_coherence":5}
{"question":"What is the financial implication of selecting an in-network provider under Northwind Standard plan?","answer":"When selecting an in-network provider, you will likely only have to pay a portion of the cost for services, often referred to as a \"co-pay\" or \"co-insurance\". Different types of services may require different co-pays or co-insurance, so it's best to contact your provider to understand what the cost will be.\n[Northwind_Standard_Benefits_Details.pdf#page=10]","gpt_relevance":null,"gpt_groundedness":null,"gpt_coherence":5}
{"question":"What should one expect when choosing an out-of-network provider or services not covered under the Northwind Standard plan?","answer":"If you choose an out-of-network provider, you may be responsible for the entire cost of services, or a far greater portion of the cost than you would with an in-network provider. In some cases, Northwind Standard may offer coverage for out-of-network providers, but you may still have to pay more than you would for an in-network provider. Additionally, some providers may offer services that are outside of the Northwind Standard plan coverage. Depending on the services provided, you may have to pay out-of-pocket for services that are not covered.[Northwind_Standard_Benefits_Details.pdf#page=10]","gpt_relevance":null,"gpt_groundedness":null,"gpt_coherence":5}
{"question":"What are the limitations of the Northwind Standard plan in relation to clinical trials?","answer":"The Northwind Standard plan does not cover travel expenses associated with attending clinical trials. Additionally, any experimental treatments or services that are not part of the clinical trial are not covered.\n[Northwind_Standard_Benefits_Details.pdf#page=24]","gpt_relevance":null,"gpt_groundedness":null,"gpt_coherence":5}
{"question":"What should members consider before participating in a clinical trial and how can Northwind Health assist?","answer":"Before participating in a clinical trial, members should consult with their doctor to make sure it's the right choice for them, understand the risks and benefits, be aware that not all clinical trials are free and some may require a fee. They should also note that clinical trials are often available in limited locations, so they may have to travel. Northwind Health can provide information about nearby clinical trials and may be able to help with the cost of travel.[Northwind_Standard_Benefits_Details.pdf#page=24]","gpt_relevance":null,"gpt_groundedness":null,"gpt_coherence":5}
{"question":"What are the gender affirming care services offered by Contoso through Northwind Standard?","answer":"Contoso offers coverage through Northwind Standard for a variety of gender affirming care services related to gender transition. These services may include hormone therapy, gender affirming surgeries, and mental health care related to gender transition.\n[Northwind_Standard_Benefits_Details.pdf#page=29]","gpt_relevance":null,"gpt_groundedness":null,"gpt_coherence":5}
{"question":"Can you explain the different types of gender affirming treatments and services offered by Contoso?","answer":"Contoso offers three main types of gender affirming treatments and services. Hormone therapy is a treatment that involves taking hormones typically associated with a certain gender to help an individual's body better reflect their gender identity. Gender affirming surgery involves surgical procedures to help an individual transition to the gender they identify with. Mental health care related to gender transition can include counseling and therapy services to help an individual through their transition process.[Northwind_Standard_Benefits_Details.pdf#page=29]","gpt_relevance":null,"gpt_groundedness":null,"gpt_coherence":5}
{"question":"What is the company's stance on providing coverage for hearing care services to its employees?","answer":"Contoso is committed to providing comprehensive coverage for hearing care services to its employees through the Northwind Standard plan. This includes coverage for all types of hearing care services, such as hearing tests, hearing aids and accessories, cochlear implants, and bone-anchored hearing aids.\n[Northwind_Standard_Benefits_Details.pdf#page=30]","gpt_relevance":null,"gpt_groundedness":null,"gpt_coherence":5}
{"question":"What specific services and items are covered under the Northwind Standard plan for hearing care, and what are the limits on these coverages?","answer":"The Northwind Standard plan covers all types of hearing care services, including hearing tests, hearing aids and hearing aid accessories, as well as cochlear implants and bone-anchored hearing aids. If a hearing aid or cochlear implant is needed, the plan covers up to two hearing aids or implants per ear every three years. The plan also covers routine hearing aid maintenance and repair, as well as counseling and hearing aid evaluations. Additionally, the plan covers up to $500 per ear for hearing aid accessories, such as ear molds, batteries, and tubing.[Northwind_Standard_Benefits_Details.pdf#page=30]","gpt_relevance":null,"gpt_groundedness":null,"gpt_coherence":5}

Please change line 44 in generate.py to:
qa.append({"question": question, "truth": answer + citation})

Merged fix for this, thanks for the report!

I'm still having problems with this.  If I print out the value, it says None. Should the fn take that into account?
def passes_threshold(rating):
    if rating is None:
        return False
    return int(rating) >=4

Okay, it didn't calculate a metric for some reason. Can you share the logs?
I can take it into account, but it usually indicates an error somewhere earlier in the script, so I'd want to put a helpful message for debugging.

The full output is at the top of the issue. Can you see if there is something there that can help pin down the issue or give me the next step? @pamelafox

Ah okay so that looks like the error from before, when generate created example ground truth data which contained "answer" for the column name. Can you check qa-2.jsonl and make sure the column is named "truth"?

Ok, its working now with that change and all the ratings are returning. I'll close this.

I am getting the same issue, some times the rating is None.
I did not understand how you fixed it @dfberry.
I've added a print to make sure the keys are correct:

Note that this occurs eventually,  but the bigger the dataset, the more this happens.
@pamelafox, it seems to be an issue in the metrics computation (by GPT-4).

return int(rating) >= 4
           ^^^^^^^^^^^
TypeError: int() argument must be a string, a bytes-like object or a real number, not 'NoneType'

During my tests, this seems to happen only with the GPT Relevance metric and in different QA pairs (sometimes it works, sometimes not, that is, I get None)

For now I've just change the code to:
    def passes_threshold(rating):
        if rating is None:
            return False
        return int(rating) >= 4

Did you notice anything in the logs about rate-limited exceeded? That can happen with your GPT-4 instance. I should probably make the change you have there, but add a warning about missing data, and count up how much missing data there is.

Did you notice anything in the logs about rate-limited exceeded? That can happen with your GPT-4 instance.

No, I did not.

I should probably make the change you have there, but add a warning about missing data, and count up how much missing data there is.
That should work.
Another option would be to add a retry for the QA pairs that get the None as the metric.
Example: Finish the current process, and check if any metric gets a None, the ones you get, try again (only that ones) until you remove all Nones

I will probably do that.


[BEAM-625] Better documentation for CompressionTypes.

Hi @chamikaramj, @dhalperi can you please take a look?

LGTM
Thanks.

Could you make the identifiers actual names (e.g. _CompressionType('zlib')) while you're at it. (Actually, I think it'd be good to clean up this and use an actual Python enum class.)

Thanks folks.
Done (using strings).
Haven't moved to Python enums. Would you mind handling that in a followup?
Also, could you merge and let me know if I can close?

Yes, enums can wait 'till a followup. I'll merge as soon as I verify tests pass.

Thanks for merging in Robert. Closing...


Chat message not sending during downtime

Describe the bug
So basically the chat messages are loaded in bulks. A very active stream sees a bulk of messages, a small pause (usually 1-3 seconds) and during this time any message you send is not actually sent.
To reproduce
Try to send a message after a bulk of chat messages are loaded.
Chatterino version
Chatterino 2.1.7 (commit 845c8fa63)
Operating system
Windows 10
Additional information
Worth noting that normal twitch chat has the same thing where the bulk stuff happens, but there you can still send a message.

That often happens due to chat server dropping your messages in those "stressful" moments and I doubt there's anything we can do about that. Same thing happens in webchat, but your message is rendered as soon as you click enter to send it - that doesn't mean it actually goes through.

I have the same issue however I don't think it has anything to do with there being a lot of chat traffic. On a stream where chat appears on screen, a message sent through the browser will work but a message sent through chatterino will not. Removing the tab, closing chatterino, reopening chatterino and readding the tab eventually fixes it.

that's a separate issue


LATER Update sudoku example so that player tx's use proof authorization

We'll wait to merge this after debugging M1 prover performance


Setting docker-compose setting 'command' causes martin to try to parse itself as a config

This docker-compose file causes martin to fail with the following error:
version: '3'

services:
  martin:
    image: maplibre/martin:v0.6.1
    restart: unless-stopped
    command : /usr/local/bin/martin
    environment:
      - DATABASE_URL=postgres://postgres:password@db/db
    depends_on:
      - db

  db:
    image: postgis/postgis:14-3.1-alpine
    restart: unless-stopped
    environment:
      - POSTGRES_DB=db
      - POSTGRES_USER=postgres
      - POSTGRES_PASSWORD=password
    volumes:
      - ./pg_data:/var/lib/postgresql/data

martin_bug-martin-1  | [2022-12-01T15:49:55Z INFO  martin] Starting Martin v0.6.1
martin_bug-martin-1  | [2022-12-01T15:49:55Z INFO  martin] Config file is not specified
martin_bug-martin-1  | [2022-12-01T15:49:55Z INFO  martin::pg::db] Connecting to database
martin_bug-martin-1  | [2022-12-01T15:49:55Z ERROR martin] Can't parse connection string /usr/local/bin/martin: invalid connection string: unexpected EOF

One might want to override the command to pass specific options as CLI arguments instead of config.

@gbip you only use command to provide arguments, not the martin binary itself.  For example, instead of using DATABASE_URL env var, you can use this:
  martin:
    image: maplibre/martin:latest
    restart: unless-stopped
    ports:
      - "3000:3000"
    command: postgres://postgres@db/db
    environment:
      - RUST_LOG=actix_web=info,martin=debug,tokio_postgres=debug

Ok, this was a misunderstanding from my side between  CMD and ENTRYPOINT, my bad.


Spark 3.0 Compatability

This package no longer works in the latest version of spark due to upgrading to Vue 2.0. There's at least one error with the package, upon attempting to open the modal this error is produced:

[Vue warn]: Inline-template components must have exactly one child element.

Fixed in the latest release.


Allow for all Misskey/Calckey servers

You just have to check if the document has #misskey_app or #calckey_app, that way it can work on instances other than .io

Thanks for the suggestion.
I once considered the idea of having it work on all misskey instances, but considering that we use CSS for filtering and each site has slightly different CSS to meet their requirements, we are currently working only on misskey.io.
(In the past, when I introduced my own CSS on nijimiss.moe, it did not work correctly and I had to modify the code.)
If we want it to work on all instances, we would not guarantee it to work on anything other than misskey.io, Or, we would allow each user to customize the CSS used for filtering (so that it can be applied in each instance).

After some thought, I decided to allow this extension to run on other servers.
We will allow it by writing the server URL we want it to work on in the settings field
(However, it is impossible to check that it works on all misskey servers, so we do not guarantee that it will work perfectly on any server other than misskey.io)