Model pull in a custom docker image at the startup

What is the issue?
I am trying to pull vicuna:13b and nmic-embed-test models at the startup of a kubernetes pod .
using a custom docker image and startup script , but it is not working
i tried everything given here , https://stackoverflow.com/questions/78232178/ollama-in-docker-pulls-models-via-interactive-shell-but-not-via-run-command-in-t
and it did not work
Can someone please give some pointers ?
OS
Linux
GPU
Nvidia, Other
CPU
Other
Ollama version
0.5.4

never mind i actually find a solution for this


google-guest-oslogin: 20220721.00 -> 20230202.00

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/GoogleCloudPlatform/guest-oslogin/releases.
meta.description for google-guest-oslogin is: OS Login Guest Environment for Google Compute Engine
meta.homepage for google-guest-oslogin is: https://github.com/GoogleCloudPlatform/compute-image-packages
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
Warning: a test defined in passthru.tests did not pass
found 20230202.00 with grep in /nix/store/g054vns9g3n72fcviqwxgv974nr189s5-google-guest-oslogin-20230202.00
found 20230202.00 in filename of file in /nix/store/g054vns9g3n72fcviqwxgv974nr189s5-google-guest-oslogin-20230202.00

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath
google-guest-agent
google-guest-oslogin

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/g054vns9g3n72fcviqwxgv974nr189s5-google-guest-oslogin-20230202.00 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A google-guest-oslogin https://github.com/r-ryantm/nixpkgs/archive/ce91999174a07d3a5a3e3316cdb9fb1b126a35ca.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/g054vns9g3n72fcviqwxgv974nr189s5-google-guest-oslogin-20230202.00
ls -la /nix/store/g054vns9g3n72fcviqwxgv974nr189s5-google-guest-oslogin-20230202.00/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

2 packages built:

google-guest-agent
google-guest-oslogin

Maintainer pings
cc @flokli for testing.

The google-oslogin VM test currently fails, which is fixed by https://github.com/NixOS/nixpkgs/pull/214811.
I cherry-picked both together and it succeeds with it, and as https://github.com/NixOS/nixpkgs/pull/214811 only fixes our mock server, we can merge this.


JSX in Typescript with only *.ts file extensions

Is it possible to configure create-react-app to process JSX syntax inside *.ts files rather than only in *.tsx? This is the default for non-Typescript projects now -- only *.js files are generated. Seems to me like the reasoning would be the same as in this issue.

The typescript community as a whole has decided on ts for typescript files with jsx and tsx for typescript files with jsx in them.  See https://github.com/microsoft/TypeScript/issues/26489 for a rundown of the basic issues.

This is indeed a requirement of TypeScript and not something that can be configured.


deploy still fails

The same python.log as ryansb#73 but now a few days later.
Further, I created a "bogus" directory under ~/app-deployments when ssh'd into the gear.
I was able to install a virtualenv, activate it, and then pip install ofcourse, and it was able to bring in 0.2.4
That seems inconsistent with openshift not being able to bring in the latest ofcourse
I didn't try to run the install from ~/app-deployments/bogus it was just a test to see that openshift could bring in the latest from pypi.

Can you attach the deploy logs from your gear?

python_log.txt


Changelog for versions

Is there an active changelog for what each new version brings? I tried to figure out through npm, but it doesn't seem like there was one.

No :/
If you really need that you can see the commits to the "version" on package.json and see the commits between them.
Dupp of https://github.com/ceifa/steamworks.js/issues/39

@ceifa can you help me understand how you do releases? If its just all manual, I can automate it, or help use some of the automation tools that github already has


Object inspector prevents entering left parenthesis

From<EMAIL_ADDRESS>on 2010-09-20T05:33:55Z
After some commands, entering left parenthesis after commands does not work in the ipython-shell any more.
What steps will reproduce the problem?

start a fresh ipython-shell in spyder
import os
os.system('ls')
figure()   # on my system, I cannot enter the left parenthesis What is the expected output? What do you see instead? I cannot enter the left parenthesis after the figure-command and other valid commands, but after invalid commands like "figu()" I can enter the left parenthesis.
I think this has something to do with the object inspector, because it turns mad (shows either "no documentation available" even if there is a docstring, or shows the documentation of a previously entered command instead of the current command) What version of the product are you using? On what operating system? I'm using spyder2.0beta3 on a ubuntu10.04-64 bit system
IPython options:
-pylab -q4thread -colors LightBG -xmode Plain -editor gedit

Please provide any additional information below
. This occurred also with other commands than "os.system", but on my system this bug is very reproducible.
When I disable the "balloon-tips", the problem disappears... (-> bug in object explorer?)
Original issue: http://code.google.com/p/spyderlib/issues/detail?id=386

From pierre.raybaut on 2010-09-20T06:16:19Z
Could you please show the 'internal console' ('View' menu > Internal console) and post its contents here: there's probably some traceback.

From<EMAIL_ADDRESS>on 2010-09-20T06:29:25Z
This is the internal console's output:
Python 2.6.5 ( r265 :79063, Apr 16 2010, 13:57:41)
[GCC 4.4.3] on linux2
Type "copyright", "credits" or "license" for more information.
>>> Traceback (most recent call last):
File "/usr/local/lib/python2.6/dist-packages/spyderlib/widgets/shell.py", line 300, in keyPressEvent
self.postprocess_keyevent(event)
File "/usr/local/lib/python2.6/dist-packages/spyderlib/widgets/shell.py", line 787, in postprocess_keyevent
ShellBaseWidget.postprocess_keyevent(self, event)
File "/usr/local/lib/python2.6/dist-packages/spyderlib/widgets/shell.py", line 444, in postprocess_keyevent
self._key_parenleft(text)
File "/usr/local/lib/python2.6/dist-packages/spyderlib/widgets/shell.py", line 864, in _key_parenleft
self.show_docstring(self.get_last_obj(), call=True)
File "/usr/local/lib/python2.6/dist-packages/spyderlib/widgets/shell.py", line 1005, in show_docstring
self.inspector.set_object_text(text)
File "/usr/local/lib/python2.6/dist-packages/spyderlib/plugins/inspector.py", line 221, in set_object_text
self.show_help(text)
File "/usr/local/lib/python2.6/dist-packages/spyderlib/plugins/inspector.py", line 342, in show_help
self.editor.set_text(hlp_text)
File "/usr/local/lib/python2.6/dist-packages/spyderlib/widgets/codeeditor/codeeditor.py", line 857, in set_text
self.setPlainText(text)
TypeError: QPlainTextEdit.setPlainText(QString): argument 1 has unexpected type 'bool'

From<EMAIL_ADDRESS>on 2010-09-20T23:02:01Z
Hello,
just to inform, I often issue the same problem, also in pdb sessions and didn't know how to reproduce it.

From pierre.raybaut on 2010-09-25T07:18:56Z
Status: Fixed


An example of custom theme inclusion in .rainbow_config.json needed

Hi,
I modified one of the standard themes and I'd like to use it, but I am unsure how exactly I am to include it in the configuration file - I know it works if if put it in the colorsets folder in the system-wide install.
The docs just mention .rainbow_config.json, but there is other stuff there (other configuration directives) - am I to just put the values (like "DECORATED_NAME") in the top scope of the file? If this is so, then apparently the new theme is not picked up in my installation (1.2.7, Ubuntu Trusty amd64, Python 2.7.6) - if I start the app, it still uses the theme set before, and if I use theme, there are only standard themes available, so I can't choose my own. Perhaps there is some variable name I am to use to name the theme somehow?
I tried setting the THEME variable to the dictionary with colour config, but it seems the app expects str there and not dict.
Could you perhaps provide a minimal example of own theme integration with other stuff in .rainbow_config.json? Thank you very much in advance.

HI @moon-musick There is quick answers:

I confirmed that if you include your file at colorsets folder it will work.
Like the doc said, color config can be placed directly to the .rainbow_config.json, despite that there is other stuff there
There is a bug when place config directly like above, while the app does not apply that colors immediately on startup. I realize that after type, eg config command, colors started to be applied. I will fix this bug when have time - sorry for your inconvenience.
theme in command only accepts string as you said - the name of theme ('monokai' v.v...)

So maybe the best way at this time is put your config files directly in colorsets folder.

This is fine with me, I am just automating my workstation setup and wanted to know if this is the right approach (putting the custom colorscheme in in the app installation directories).
I suppose if you labelled this a bug, I am to leave this issue open.
Thanks for the info and for a great Twitter client! :)


[8.x] Fix Issue #23218

Allow null value validation in exclude_if, exclude_unless, required_if and required_unless as per Issue #23218. Check for lowercased interpretation of "null", so that developers can also still write "NULL" or even "NuLl".
As indicated in the issue, this PR will aid validation of mutual exclusive fields that are both present in the request. By the time the request has passed through stripping and trimming, the empty field evaluates to null in the request. Currently, this cannot be validated against.

I have these issue on laravel 7.30

i have used the below trick in laravel 7.x
'exclude_if:field_name,""',

Laravel 7.x isn't maintained anymore, sorry. Please upgrade to Laravel 8.

The breaking change when going from laravel 7 to 8 was that in L7, I could use exclude_if:field, which does not work anymore in L8. In L8 I have to use exclude_if:field,null.


Fix DAP issues for Select

Level
Description

V
All content must reside within a WAI-ARIA landmark or labelled region role.

Likely a label/input association issue

false positive, since the preview page doesn't have a main tag. Unfortunately there's no reasonable way for us to add one at the moment. Apps should of course render into a main or other valid region.


Pinecone metadata to include confidence & summary

In the Pinecone metadata we need to include confidence & summary too.

Looks like the arxiv paper abstracts are in the summary not in the text itself. That needs to be embedded to help us retrieve relevant papers.
When editors flag an article "thumbs down," it's been embedded & in pinecone already so we want to make sure it's not provided as context for the chatbot.

I'm not sure I understand what exactly that would look like.
It would be easy to add the confidence number to the pinecone metadata, which I can do. I could also add the summaries in the metadata, that's very doable, but I don't see the advantage of doing so.
Regarding embedding the summaries, should they be split in the same way the text is, and embedded the same way the text is, with no difference otherwise? That would be easy. I'm not sure however if things like the header should be different and should note where the summary is from or something like that.
Regarding articles that have been thumbed down, it's pretty easy to remove them if we add a metadata for that, or otherwise we can just temporarily remove them from the pinecone and add them later? Which do you think is best?

I could also add the summaries in the metadata, that's very doable, but I don't see the advantage of doing so.

Right now, it looks like the arxiv abstracts are in summaries not included in the text. I think that's a key missing component. Initially, we can just split the abstract/summaries like any other text with the same header.
Eventually, we might want a separate namespace for all summaries to be embedded without splitting into chunks. This could be helpful to retrieve sources to answer questions like "What was the paper/blog post about..." which is a often requested feature. We should discuss before implementing this.

Regarding articles that have been thumbed down, it's pretty easy to remove them if we add a metadata for that, or otherwise we can just temporarily remove them from the pinecone and add them later? Which do you think is best?

For thumbs down, I would mark the metadata confidence=0 then make sure they don't get returned in pinecone search results. As long as the results are filtered out, it's not as important whether the data remains in pinecone or not... maybe leave it for know until we decide otherwise. Obviously, anything already low confidence in MySQL should NOT be added to pinecone.

Ok, perfect. To have the chatbot not use those, we just need to add a filter that doesn't accept confidence=0: filter={"confidence": {"$ne": 0}}.

fixed #171

fixed #171


tracker: fix cross build via meson emulator hook

Description of changes
Fix cross build for tracker
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin
[x] x86_64-linux -> aarch64-linux (cross)

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

Oh I didn't think about it, but this is a zero-rebuild change for non-cross. I guess I'll target this towards master instead

fixed via https://github.com/NixOS/nixpkgs/pull/246369


Create 2023-01-05-content.md

Purpose of this pull request
This pull request (PR) ...
Update CSE release notes for 1/5/2023
Issue number:
N/A
Select the type of change:

[ ] Minor Changes - Typos, formatting, slight revisions
[X] Update Content - Revisions and updating sections
[ ] New Content - New features, sections, pages, tutorials
[ ] Site and Tools - Updates, maintenance, and new packages for the site, Gatsby, React, etc

RSS not necessary

@PaulTobia , we have your GitHub username in our CLA as ptobia. Should we replace with the one you used here?

Apologies I accidentally switched accounts. Please keep ptobia as the Sumo account.

@PaulTobia since everything is approved, can you please merge on your end? We can't do this on our end since the PR originated from your fork.


FIPS compliant version of docker image in docker repository

Title: FIPS compliant version of docker image in docker repository
Description:

It looks like images available in envoyproxy repo is boringSSL without fips compliance. Right now if we need it we have to build on our own. Is it possible to provide a fips compliant version of image ?

[optional Relevant Links:]

https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/security/ssl.html?highlight=fips#fips-140-2

This is a reasonable request but realistically I doubt this will happen any time soon. It might be better to reach out to https://www.getenvoy.io/ and see if they will do it? cc @lizan @dio

@mattklein123 Thank you. I just checked the issues there, and looks like there has been already one in their queue.
https://github.com/tetratelabs/getenvoy-package/issues/20

Yeah that's in getenvoy roadmap but I don't have an ETA right now

@lizan Thank you. Glad it is in your road map. I will follow the other issue.


Complex documented type expressions are not understood

/**
  * @param (string|string[])[]
  */

Completely misparsed right now.

Not any more!


Interesting in your work

Hi,
Thank you for your great work! I am interesting in running and studying the code.  Nevertheless, the pre-processing code to attain the basis function and its gradient seems not public yet, meanwhile, the code regarding shape interpolation part seems not public also.
Could you please share the above codes for interested readers to study, thank you very much.
Best wishes,
Mingyang

Hi,
You should find basis function initialistion, gradient computation, etc here: https://github.com/Sentient07/DeformationBasis/blob/master/utils/batched_mls_function.py . Regarding the shape interpolation, I'll release it soon. Thanks for your interest and hope that helps

Hi,
You should find basis function initialistion, gradient computation, etc here: https://github.com/Sentient07/DeformationBasis/blob/master/utils/batched_mls_function.py . Regarding the shape interpolation, I'll release it soon. Thanks for your interest and hope that helps

Thank you for your kind and timely response. Thank you!


shouldHaveLength should show the length on failure

Currently it will say
java.lang.AssertionError: qwerty should have length 32

Can you describe a little bit more, please? With the description you provided, it seems that the issue is already OK.

It doesn't show the length of the string that was incorrect.
On Tue, 2 Jul 2019, 18:28 Gustavo Fão Valvassori<EMAIL_ADDRESS>wrote:

Can you describe a little bit more, please? With the description you
provided, it seems that the issue is already OK.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/kotlintest/kotlintest/issues/869?email_source=notifications&email_token=AAFVSGU62ERDDGCMXXN26OTP5PQBJA5CNFSM4H46DJ4KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZC2MCA#issuecomment-507880968,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAFVSGWZURN22ZKCGPKH5ULP5PQBJANCNFSM4H46DJ4A
.

Like this: java.lang.AssertionError: hello should have length 32, but instead was 5?

Yep.
On Tue, 2 Jul 2019, 18:37 Gustavo Fão Valvassori<EMAIL_ADDRESS>wrote:

Like this: java.lang.AssertionError: hello should have length 32, but
instead was 5?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/kotlintest/kotlintest/issues/869?email_source=notifications&email_token=AAFVSGU2QWF3ZG2VZYHVS4DP5PRCXA5CNFSM4H46DJ4KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZC2Y3Y#issuecomment-507882607,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAFVSGVRELKJ75TNL4JVGTLP5PRCXANCNFSM4H46DJ4A
.


Add engines cap when user is uploading the plan

One tenant configured 10000 engines to one collection...We can add a cap to disallow such config.

Solved by this: https://github.com/rakutentech/shibuya/pull/46/files


Roundup: [oss-security] Persistent XSS Vulnerability in Wordpress plugin AnyVar v0.1.1

Here is a report from the oss-security mailing list for Vulnerability Roundup 27.
Skip to First Email
Instructions:
Identification
Identify if we have the software, in 16.09, 17.03, and unstable. Then determine if we are vulnerable, and make a comment with your findings. It can also be helpful to specify if you think there is a patch, or if it can be fixed via a general update.
Example:
unstable: we are not vulnerable (link to the package)
17.03: we are vulnerable (link to the package)
16.09: we don't have it packaged

IMPORTANT: If you believe there are possibly related issues, bring them up on the parent issue!
Patching
Start by commenting on this issue saying you're working on a patch. This way, we don't duplicate work.
If you open a pull request, tag this issue and the master issue for the roundup.
If you commit the patch directly to a branch, please leave a comment on this issue with the branch and the commit hash, example:
fixed:

release-16.09: abc123

Skip to First Email
Upon Completion ...

[ ] Update Graham's database

Info
Triage Indicator:
-needs-triage +roundup27 thread:0000000000003ea0

File Search: https://search.nix.gsc.io/?q=wordpress&i=fosho&repos=nixos-nixpkgs
GitHub Search: https://github.com/NixOS/nixpkgs/search?utf8=✓&q=wordpress+in%3Apath&type=Code

Should the search term be changed from wordpress? Suggest a new package search by commenting:
-suggested:wordpress +suggested:correctPackageName thread:0000000000003ea0

Known CVEs: CVE-2017-6103

Skip to End
Wed, 01 Mar 2017 04:39:21 -0500 "Larry W. Cashdollar" <larry0-at-me.com><EMAIL_ADDRESS>Title: Persistent XSS Vulnerability in Wordpress plugin AnyVar v0.1.1
Author: Larry W. Cashdollar, @_larry0
Date: 2017-02-21
Download Site: https://wordpress.org/plugins/anyvar
Vendor: https://profiles.wordpress.org/matt_dev/
Vendor Notified: 2017-02-28
Vendor Contact<EMAIL_ADDRESS>Description: AnyVar is a simple search and replace plugin. It lets you add changeable variables (text snippets) to posts, sidebars, widgets, links & themes.
Vulnerability:
$var_name and $var_text aren't sanitized before being sent to the webpage.  $var_name only can contain text so only $var_text is exploitable
In file ./anyvar/anyvar.php:

202                         echo "

203                                 <input     type='checkbox' name='delete[]' value='$var_name' />
204                                  $var_name
205                                 [$var_name]
206                                 <textarea name='anyvar_text_$var_name' i    d='anyvar_text_$var_name' cols='60' rows='3' readonly>$var_text</textarea></    td>

CVE-ID: CVE-2017-6103
Exploit Code:
	• In the text field box the following will trigger a JS alert popup:
	•
	• </textarea><textarea>
Screen Shots: [http://www.vapidlabs.com/m/xssvar.png]
Advisory: http://www.vapidlabs.com/advisory.php?v=177

Skip to End

unstable: we don't have it packaged
17.03: we don't have it packaged
16.09: we don't have it packaged

Thank you!


Setup the Login Page

Need to fix the Login Page UI. It should contain the following fields:

IITK Email address
Password field

Make sure to setup an email validator, which checks whether the typed email is valid or not. Also, create a dummy API function to send in the credentials to backend. The data object should contain the email id and the password.

Ok great. I'm working on this issue.

I'll also be working on this issue.

SahilSunda and i are working in a team on this issue.

I already added login actions that save responses using redux-react-session. I want you guys to make some good actions and reducers to handle this apart from what I added. If you have something else to save the session apart from redux-session use it as well as we don't want the user to log in again and again. As most part has been done, I think only one or max to max 2 of you can work on it.

Yeah fine, shubham will work on profile one, me and sanchit can work on this


Used a shared cache db for sessions.

This will make our stuff work when we have multiple app servers.

May want to add a cronjob or something to run clearsessions from time to time, to avoid bloat.


suse.uninstall: ceph-deploy purge fails on SUSE.

This is because ceph-deploy tries to remove a package that does not exist.
To fix this we need to change package name to correct name ceph-radosgw
from the old name radosgw.
Signed-off-by: Owen Synge<EMAIL_ADDRESS>

Refer to this link for build results (access rights to CI server needed):
http://jenkins.ceph.com//job/ceph-deploy-pull-requests/1576/
Tests failed for this pull request.

@osynge The jenkins build bots have been having lots of issues lately.  They were down for a couple of days.  Looks like the tests failed because they either didn't have internet access, or could reach GitHub for another reason.  This is a pretty clear fix.  Thanks!  :+1:


HTML entities in attributes are not always decoded for string templates

Version
2.5.17
Reproduction link
https://jsfiddle.net/sf9cg0db/
Steps to reproduce
Try to dynamically load an input field with a value that contains an encoded single quote (') as plain HTML. Normally the input field will display the single quote in the input box. However, Vue shows the ' in the input box.
I tested this with multiple encoded chars, and everything works correctly, except for the single quote. As stated by @HcySunYang, all entities except the 6 he listed have this issue.
What is expected?
A single quote is shown in the input field when loaded async with Vue
What is actually happening?
' is show in the input field when loaded async with Vue

This is not related to whether the component is asynchronous or not. Non-asynchronous components also have this problem. Vue's html-parser will only process the following entity content:
const decodingMap = {
  '<': '<',
  '>': '>',
  '"': '"',
  '&': '&',
  '
': '\n',
  '	': '\t'
}

it's here: https://github.com/vuejs/vue/blob/dev/src/compiler/parser/html-parser.js#L38-L45.

So ''' should be added to the map?

It would not be better to use something like this package?
https://github.com/mdevils/node-html-entities

Actually Vue is already using he on Node.js (compile-time and SSR) and leveraging DOM API on the browser side to perform entity decoding. It seems that only attribute values are decoded using the decodingMap mentioned above and I'm not sure it's intentional or just a miss.

Running into a similar issue when a PHP code is returning an encoded HTML attribute, especially within WordPress with the esc_attr function: https://qsandbox.com/tools/wp-functions/function/esc_attr

Behind the scenes, it uses PHP htmlspecialchars:

The difference is the leading 0 which is not interpreted by the decoding map:
https://github.com/vuejs/vue/blob/8d3fce029f20a73d5d0b1ff10cbf6fa73c989e62/src/compiler/parser/html-parser.js#L33-L43
The leading 0 should not run into any issues in browser behavior as it is interpreted as integer: https://appdevtools.com/html-entity-encoder-decoder


NTT module

Shouldn't line 165 of gen-ntt-pipeline.py be k, mul_index, phi_index = mul_tuple ???
Maybe I'm missing something....

@cgyurgyik?

Oh forgive me. I misunderstood


cant use even when instaled correctly

when i press F1 it doesn't do anything

make sure camera smoothing is off in in-game settings?

Same here :/
Camera Smoothing is turned off (no config file too :/) and I'm using BeatDrop to install it

make sure camera smoothing is off in in-game settings?

i did that it is resolved thasnks.!


[SBRP] Remove obsolete packages from source-build-reference-packages

Known dead-ended packages:

System.Memory
Microsoft.Bcl.HashCode

More to come.

[Triage] These should get cleaned up when we cleanup the unreferenced SBRP packages in 7.0.  If not, that is an indicator they are being referenced which probably means something is broken.

for our education, how did you find that these packages are not needed anymore? Is the final tarball necessary for that? Also, do we need to introduce some process to periodically prune the source-build-reference-packages of obsolete packages?

@tkapin - see https://github.com/dotnet/source-build/issues/2357 - it is an issue for automating the process and captures the steps taken to identify unused packages.

Turns out these packages do need to remain as they are required to build the product.


Can't get villager trades for modded profession working

Trying to add support for this mod to my own mod TerraMine, but can't seem to get the trades to be added, the villager with my goblin tinkerer profession will only shake his head when interacted with. Either I messed up with the json, or something else is wrong:
{
  "profession": "terramine:goblin_tinkerer",
  "trades": {
    "novice": [
      {
        "type": "numismatic-overhaul:buy_stack",
        "price": 50000,
        "buy": {
          "item": "terramine:rocket_boots",
          "count": 1
        },
        "max_uses": 1
      },
      {
        "type": "numismatic-overhaul:sell_stack",
        "price": 2000,
        "sell": {
          "item": "minecraft:dispenser",
          "count": 1
        },
        "max_uses": 15,
        "villager_experience": 10
      }
    ],
	"apprentice": [
      {
        "type": "numismatic-overhaul:buy_stack",
        "price": 50000,
        "buy": {
          "item": "terramine:stopwatch",
          "count": 1
        },
        "max_uses": 1
      },
      {
        "type": "numismatic-overhaul:sell_stack",
        "price": 1500,
        "sell": {
          "item": "minecraft:sticky_piston",
          "count": 1
        },
        "max_uses": 20,
        "villager_experience": 5
      }
    ],
	"journeyman": [
      {
        "type": "numismatic-overhaul:buy_stack",
        "price": 50000,
        "buy": {
          "item": "terramine:weather_radio",
          "count": 1
        },
        "max_uses": 1
      },
      {
        "type": "numismatic-overhaul:buy_stack",
        "price": 50000,
        "buy": {
          "item": "terramine:sextant",
          "count": 1
        },
        "max_uses": 1
      }
    ],
	"expert": [
	{
        "type": "numismatic-overhaul:sell_stack",
        "price": 2500,
        "sell": {
          "item": "minecraft:observer",
          "count": 1
        },
        "max_uses": 15,
        "villager_experience": 15
      },
      {
        "type": "numismatic-overhaul:buy_stack",
        "price": 50000,
        "buy": {
          "item": "terramine:extendo_grip",
          "count": 1
        },
        "max_uses": 1
      }
    ],
	"master": [
      {
        "type": "numismatic-overhaul:buy_stack",
        "price": 50000,
        "buy": {
          "item": "terramine:toolbelt",
          "count": 1
        },
        "max_uses": 1
      },
      {
        "type": "numismatic-overhaul:buy_stack",
        "price": 50000,
        "buy": {
          "item": "terramine:toolbox",
          "count": 1
        },
        "max_uses": 1
      }
    ]
  }
}

that was fast

The JSON certainly looks correct. If there was anything wrong with it you would get an error when the trade file is loaded. What I am more curious about is how your profession is registered.

This is my profession init:
https://github.com/jakeb072001/TerraMine/blob/1.19/src/main/java/terramine/common/init/ModProfessions.java

Do mind that Numismatic does not refresh trades retroactively, meaning you need a new Goblin Tinkerer to test the trades with

Yea, I've been spawning new villagers just to be sure and I even just tried it in another world but its still doesn't work, very odd

Thanks for opening this issue. With the next release of Numismatic Overhaul this issue should be resolved.


cannot assign pkt-tag that is greater than 4096 to a vxlan virtual network

I met an error when playing with the three nodes cluster.
vagrant@netplugin-node1 ~]$ netctl network create --subnet=<IP_ADDRESS>/24 --encap=vxlan --pkt-tag=5000 vtep5000
ERRO[0000] pktTag Value Out of bound
$ netctl global info
Fabric mode: default
Vlan Range: 1-4094
Vxlan range: 1-10000

I don't see this issue anymore.  Is it consistently reproducible?
I tried on https://github.com/contiv/netplugin/commit/ff611a2f064496246fa724fe64f46ac9586d4bf4


Issue with the search

Kibana version: 5.6.5
When I type a search query, it doesn't work even when the syntax is right. Without the plugin this works very will.

This plugin uses its own query language. Please see this page for usage: https://ppadovani.github.io/knql_plugin/knql/
The language is very SQL like in nature and the above page explains the language.


Update: ghost blog

Update to the latest version 4.1.2
Update post_install.md, include example patch to update image tag version

If your pull request concerns an existing Marketplace application, please make sure you have:

[x] Notified the Maintainer of the application in this pull request so that they are aware of your proposal.
[x] Outlined the changes you are proposing, and the reasons these are required (e.g. stability, compatibility with new versions of Kubernetes implementations, etc).
[x] Tested that the application works with the proposed updates applied (including a screenshot)

Before update image

After update image

LGTM


Re-work pagination and add tests.

Here's a first version. This version doesn't include next or previous in the metadata if a number for page can't be found. This is only really expected to happen when next or previous are null for the first and last page. An alternative would be include next and previous in the metadata and set them to -1 for the first and last pages. What do you think?
I also still need to write user facing docs but I'm waiting for that to be setup.

@benkonrath I moved version-1.0 branch to master and submitted v0.5.0.  Can you edit this PR to point at master?

The work in this PR will continue in #45.


Works with debug, but not something like googlecloud

Hello!  Thank you for working on this, I need something exactly like this.
When I try to export to googlecloud I'm getting errors like this:
2024-11-12T01:11:33.994Z	info	MetricsExporter	{"kind": "exporter", "data_type": "metrics", "name": "debug", "resource metrics": 1, "metrics": 6, "data points": 8}
2024-11-12T01:11:33.995Z	info	ResourceMetrics #0
Resource SchemaURL:
Resource attributes:
     -> service.name: Str(test)
     -> service.instance.id: Str(more_test)
ScopeMetrics #0
ScopeMetrics SchemaURL:
InstrumentationScope
Metric #0
Descriptor:
     -> Name: ping.rtt
     -> Description:
     -> Unit: ms
     -> DataType: Gauge
NumberDataPoints #0
Data point attributes:
     -> net.peer.ip: Str(<IP_ADDRESS>)
     -> net.peer.name: Str(<IP_ADDRESS>)
StartTimestamp: 1970-01-01 00:00:00 +0000 UTC
Timestamp: 2024-11-12 01:11:31.951675877 +0000 UTC
Value: 1.404978
NumberDataPoints #1
Data point attributes:
     -> net.peer.ip: Str(<IP_ADDRESS>)
     -> net.peer.name: Str(<IP_ADDRESS>)
StartTimestamp: 1970-01-01 00:00:00 +0000 UTC
Timestamp: 2024-11-12 01:11:32.952326551 +0000 UTC
Value: 1.439537
NumberDataPoints #2
Data point attributes:
     -> net.peer.ip: Str(<IP_ADDRESS>)
     -> net.peer.name: Str(<IP_ADDRESS>)
StartTimestamp: 1970-01-01 00:00:00 +0000 UTC
Timestamp: 2024-11-12 01:11:33.95269958 +0000 UTC
Value: 1.412412
Metric #1
Descriptor:
     -> Name: ping.rtt.min
     -> Description:
     -> Unit: ms
     -> DataType: Gauge
NumberDataPoints #0
Data point attributes:
     -> net.peer.ip: Str(<IP_ADDRESS>)
     -> net.peer.name: Str(<IP_ADDRESS>)
StartTimestamp: 1970-01-01 00:00:00 +0000 UTC
Timestamp: 2024-11-12 01:11:33.994490837 +0000 UTC
Value: 1.404978
Metric #2
Descriptor:
     -> Name: ping.rtt.max
     -> Description:
     -> Unit: ms
     -> DataType: Gauge
NumberDataPoints #0
Data point attributes:
     -> net.peer.ip: Str(<IP_ADDRESS>)
     -> net.peer.name: Str(<IP_ADDRESS>)
StartTimestamp: 1970-01-01 00:00:00 +0000 UTC
Timestamp: 2024-11-12 01:11:33.994490837 +0000 UTC
Value: 1.439537
Metric #3
Descriptor:
     -> Name: ping.rtt.avg
     -> Description:
     -> Unit: ms
     -> DataType: Gauge
NumberDataPoints #0
Data point attributes:
     -> net.peer.ip: Str(<IP_ADDRESS>)
     -> net.peer.name: Str(<IP_ADDRESS>)
StartTimestamp: 1970-01-01 00:00:00 +0000 UTC
Timestamp: 2024-11-12 01:11:33.994490837 +0000 UTC
Value: 1.418976
Metric #4
Descriptor:
     -> Name: ping.rtt.stddev
     -> Description:
     -> Unit: ms
     -> DataType: Gauge
NumberDataPoints #0
Data point attributes:
     -> net.peer.ip: Str(<IP_ADDRESS>)
     -> net.peer.name: Str(<IP_ADDRESS>)
StartTimestamp: 1970-01-01 00:00:00 +0000 UTC
Timestamp: 2024-11-12 01:11:33.994490837 +0000 UTC
Value: 0.014852
Metric #5
Descriptor:
     -> Name: ping.loss.ratio
     -> Description:
     -> Unit:
     -> DataType: Gauge
NumberDataPoints #0
Data point attributes:
     -> net.peer.ip: Str(<IP_ADDRESS>)
     -> net.peer.name: Str(<IP_ADDRESS>)
StartTimestamp: 1970-01-01 00:00:00 +0000 UTC
Timestamp: 2024-11-12 01:11:33.994490837 +0000 UTC
Value: 0.000000
	{"kind": "exporter", "data_type": "metrics", "name": "debug"}
2024-11-12T01:11:34.075Z	error	internal/queue_sender.go:92	Exporting failed. Dropping data.	{"kind": "exporter", "data_type": "metrics", "name": "googlecloud", "error": "rpc error: code = InvalidArgument desc = One or more TimeSeries could not be written: timeSeries[2]: Field timeSeries[2] had an invalid value: Duplicate TimeSeries encountered. Only one point can be written per TimeSeries per request.; timeSeries[1]: Field timeSeries[1] had an invalid value: Duplicate TimeSeries encountered. Only one point can be written per TimeSeries per request.\nerror details: name = Unknown  desc = total_point_count:8 success_point_count:6 errors:{status:{code:3} point_count:2}", "dropped_items": 8}
go.opentelemetry.io/collector/exporter/exporterhelper/internal.NewQueueSender.func1
	go.opentelemetry.io/collector/exporter@v0.111.0/exporterhelper/internal/queue_sender.go:92
go.opentelemetry.io/collector/exporter/internal/queue.(*boundedMemoryQueue[...]).Consume
	go.opentelemetry.io/collector/exporter@v0.111.0/internal/queue/bounded_memory_queue.go:52
go.opentelemetry.io/collector/exporter/internal/queue.(*Consumers[...]).Start.func1
	go.opentelemetry.io/collector/exporter@v0.111.0/internal/queue/consumers.go:43

If I set it to use something simple like the debug exporter, it seems fine.
I'm configuring otel like this (stripped down config for testing, the googlecloud part works fine for a number of other metrics and logs being sent now):
receivers:
  icmpcheck:
    collection_interval: 30s
    targets:
      - target: <IP_ADDRESS>

processors:
  resource:
    attributes:
      - key: service.name
        value: test
        action: upsert
      - key: service.instance.id
        value: more_test
        action: upsert

exporters:
  googlecloud:
    log:
      default_log_name: opentelemetry.io/collector-exported-log

  debug:
    verbosity: detailed

service:
  pipelines:
    metrics/test:
      receivers:
        - icmpcheck
      processors:
        - resource
      exporters:
        - googlecloud
        - debug

The metrics are showing up in GCP as expected though, just with the log noise.  Any ideas?

Might be that the googlecloud exporter uses the StartTimestamp which is unset and thus always the same. Could you maybe try with a processor to copy the timestamp into starttimestamp and validate if that works?

Apologies for my ignorance, but how does one add a starttimestamp?  I've
found many ways to modify attributes, but timestamps seem to be above that
level:
Here's a json sample:
{"resourceMetrics":[{"resource":{},"scopeMetrics":[{"scope":{},"metrics":[{"name":"ping.rtt","unit":"ms","gauge":{"dataPoints":[{"attributes":[{"key":"net.peer.ip","value":{"stringValue":"<IP_ADDRESS>"}},{"key":"
net.peer.name
","value":{"stringValue":"<IP_ADDRESS>"}}],"timeUnixNano":"1731441629004135281","asDouble":1.334812},{"attributes":[{"key":"net.peer.ip","value":{"stringValue":"<IP_ADDRESS>"}},{"key":"
net.peer.name
","value":{"stringValue":"<IP_ADDRESS>"}}],"timeUnixNano":"1731441630005306713","asDouble":2.241777},{"attributes":[{"key":"net.peer.ip","value":{"stringValue":"<IP_ADDRESS>"}},{"key":"
net.peer.name
","value":{"stringValue":"<IP_ADDRESS>"}}],"timeUnixNano":"1731441631004853906","asDouble":1.207437}]}},{"name":"ping.rtt.min","unit":"ms","gauge":{"dataPoints":[{"attributes":[{"key":"net.peer.ip","value":{"stringValue":"<IP_ADDRESS>"}},{"key":"
net.peer.name
","value":{"stringValue":"<IP_ADDRESS>"}}],"timeUnixNano":"1731441631055550689","asDouble":1.207437}]}},{"name":"ping.rtt.max","unit":"ms","gauge":{"dataPoints":[{"attributes":[{"key":"net.peer.ip","value":{"stringValue":"<IP_ADDRESS>"}},{"key":"
net.peer.name
","value":{"stringValue":"<IP_ADDRESS>"}}],"timeUnixNano":"1731441631055550689","asDouble":2.241777}]}},{"name":"ping.rtt.avg","unit":"ms","gauge":{"dataPoints":[{"attributes":[{"key":"net.peer.ip","value":{"stringValue":"<IP_ADDRESS>"}},{"key":"
net.peer.name
","value":{"stringValue":"<IP_ADDRESS>"}}],"timeUnixNano":"1731441631055550689","asDouble":1.594675}]}},{"name":"ping.rtt.stddev","unit":"ms","gauge":{"dataPoints":[{"attributes":[{"key":"net.peer.ip","value":{"stringValue":"<IP_ADDRESS>"}},{"key":"
net.peer.name
","value":{"stringValue":"<IP_ADDRESS>"}}],"timeUnixNano":"1731441631055550689","asDouble":0.460515}]}},{"name":"ping.loss.ratio","gauge":{"dataPoints":[{"attributes":[{"key":"net.peer.ip","value":{"stringValue":"<IP_ADDRESS>"}},{"key":"
net.peer.name
","value":{"stringValue":"<IP_ADDRESS>"}}],"timeUnixNano":"1731441631055550689","asDouble":0}]}}]}]}]}
On Tue, Nov 12, 2024 at 8:51 AM Thomas Hamm @.***>
wrote:

Might be that the googlecloud exporter uses the StartTimestamp which is
unset and thus always the same. Could you maybe try with a processor to
copy the timestamp into starttimestamp and validate if that works?
—
Reply to this email directly, view it on GitHub
https://github.com/thmshmm/icmpcheckreceiver/issues/2#issuecomment-2471057789,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BJ4CMV2MVLMKQKKZHF3SU332AIWXZAVCNFSM6AAAAABRS5ZOVWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINZRGA2TONZYHE
.
You are receiving this because you authored the thread.Message ID:
@.***>


Google Drive API fails to retrieve in IE11 and Edge

Due to a IE11/Edge bug: https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/7112809/

+1


Reduce the number of onUpdate events fired for dialog buttons

Noticed this while investigating the issue with the model view validation affecting dialog buttons - the code that sets the properties for a dialog button fires the onUpdate event every time a property is changed. This is fine by itself - but the only place we're currently doing that has us always setting all 5 properties and so the event would be fired 5 times and end up going through a whole bunch of extra calls (including telling angular to redraw the UI) which was a huge amount of unnecessary overhead.
So here I'm just adding a helper function to set all properties and fire the event just once at the end.
Tested this with a couple of dialogs (including ones that set the button values manually after initial rendering) and things work as expected.
We could get fancier with the setProperties and have it take in a Partial of the properties or something so as to not require setting ALL of the properties. But given how this function is called currently it didn't seem to be a huge deal to have it left simpler like this (a tiny bit of extra overhead from setting label/enabled twice).

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

10 of 10 (100.0%)  changed or added relevant lines in 2 files are covered.
5 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.0002%) to 42.566%

Files with Coverage Reduction
New Missed Lines
%

src/sql/workbench/services/dialog/common/dialogTypes.ts
5
81.63%

Totals

Change from base Build<PHONE_NUMBER>:
-0.0002%

Covered Lines:
26720

Relevant Lines:
56894

💛  - Coveralls


Restore the ability to use implicit subject in consumer specs

Follow-up of #106
To avoid situations when calling subject was having side effects it has been decided that the gem will use an explicit consumer reference to keep track of messages sent to Kafka.
This has the downside to require developers to declare a consumer object (or a named subject) in their tests instead of relying on implicit subjects.
In the issue comment thread, I thought about looking at the described_class and testing if it inherits from Karafka::BaseConsumer. If that is the case the gem's helper could try to look at the consumer referenced object or call the subject reference.
If the described_class is not a Karafka::BaseConsumer the helper will only look for the consumer object

@NotGrm can you submit a POC for this as a PR?


bugfix: use new options instead of deprecated ones

Processing this pull request

Merged into branches iso5 in 3678a48c4ccdaa8346399d1daf0c869cb0d151e1


Enable cloudkit schema for prod

User Feedback
Reported log
label: Skypiea
type: error
message: failed to subscribe to CloudPhrase iCloud subscription; description='Error saving record subscription with id 49ECB217-56A0-4075-B448-B8EAE9EDD684 to server: Did not find record type: CloudPhrase'; error='<CKError 0x281dc29a0: "Unknown Item" (11/2003); server message = "Did not find record type: CloudPhrase"; op = 744771BF4DADFF0C; uuid = 9A7DB98A-9136-4C01-B420-298B97F01D17; container ID = "iCloud.com.io.kamaal.PocketSlate">'
Additional Data
{}

Done


Error when trying to add Icon to component

I am getting the error below when I save the file (transpiles Typescript):
Field 'browser' doesn't contain a valid alias configuration
It seems like it's not finding a directory of some sort?
Field 'browser' doesn't contain a valid alias configuration
    resolve as module
      /Users/p009509B/Sharepoint/spfx-pweb-home/node_modules/@vectopus/atlas-icons-react/node_modules doesn't exist or is not a directory
      /Users/11221222/Sharepoint/spfx-pweb-home/node_modules/@vectopus/atlas-icons-react/lib doesn't exist or is not a directory
      /Users/11221222/Sharepoint/spfx-pweb-home/node_modules/@vectopus/node_modules doesn't exist or is not a directory
      /Users/11221222/Sharepoint/spfx-pweb-home/node_modules/@vectopus/lib doesn't exist or is not a directory

this is how the folder looks like in node_modules:

I am using

"react": "17.0.1"
"react-dom": "17.0.1"

I am not sure if I installed incorrectly or have configured something wrong. Please advise.

Hi @michaelsoriano, Thank you for reporting this issue.
I think this is related to custom webpack config, Could you please share with me your webpack config?

Hi @mosamy19  - sorry for the late response. I had to research where the webpack config is - since this is not a regular React Project. Apparently it's getting generated dynamically (https://github.com/SharePoint/sp-dev-docs/issues/6280), which might be causing the issue. In addition, I'm not sure if I can edit the file that generates the webpack config. Thank you anyway.


#574 cleanups

FF version tags are now square brackets (allows for [FF52-63] etc, as long as you parse for [FF. Any other references to FF versions if needed, use round brackets (e.g in descriptions, header sections etc)
FF version tags, where possible, are now after each pref. This removes confusion, and allows for extra new prefs to be inserted under that number. The bulk of these were numbered items with a single pref. Where the version tag was in the pref description but we had multiple prefs, I left those mostly alone, because I cannot be sure they all adhere to the same version release. At some stage it would be nice to enforce ALL version tags to each pref (but that would be a lot of work!).
Default tags are now all [DEFAULT*] and can contain extra info, eg [DEFAULT: true in FF61+]. This means we can ignore tagging things such as the Font information in 1402 etc. The purpose of these is to pick up where we enforce defaults, but we include the value, because of OS differences.
Hidden tags are now all `[HIDDEN PREF]
all [OS tags are now all after individual prefs
Got sidetracked on versions and defaults, but there are some other edits in here. Started to make sure numbered first lines are self contained and the wording doesn't overflow into the next line. Moved or removed a few comments bits from end of pref lines, i.e. // text where possible - e.g some setting info up into the man text
I also did this throughout the entire file (e.g deprecated also got tidied up a bit), even though this is for overdodactyl awesome project which would, when finished, stop at the beginning of the personal section
Need eyeballs on this to double check I didn't do any typos.

I have to say the compare in github on this one sucks. You would be better off downloading it and doing a compare locally with your favorite IDE

It's looking good to me!  If we're prettying certain on going this route (which I think we are), I can switch the prototype to grabbing this file instead so I can start working with the changes.

Yup, got for it. I won't commit it until at least E and :cat2: sign off. And you might pick up some new issues

I still read it, but it wasn't as easy as I thought it would be

Yeah. I said as much. It seems to jumble a few lines out of order

That makes all [FF info all assigned to user_pref lines

I really don't like the removal of FF version (and OS info, etc) from the title lines but I guess it's too late now

^^ no, it's not too late (it kinda hurt me a little as well). Where all multi-prefs under the number are the same, we could duplicate it back in the top line (it's probably all of them). I'm fine with that. Because @overdodactyl 's code will only parse for them in the pref lines, it's no big deal.
Happy to do that before we commit - just let me know (as long as we remember to remove it if the multi-prefs differ with version)
PS: am on beer # 8

Or we could MAKE @overdodactyl just propagate it and stick his code in to compare etc

I've just been looking at this for the last 2 hours, and in order to come to some sort of consensus, or informed decision, did some number crunching, in a pretty spreadsheet.
Considerations

duplication (I'm not a fan of duplication)
usability (I find it easier to spot the FF version info at the end of the first line), it seems more elegant
we can make code do anything, overdodactyl already did the [FF` versions this way before

and is looking at doing the same for propagating [SETTING etc to children prefs
and if we put them back, ONLY if all multi-prefs have the same version, then this removes the need to compare, so the code from before is actually simplified a bit, just not to the same extent

the user.js comes first, the cool real-time whizzy-ma-jiggy comes second (but we'll help if we can, this has already led to some content cleanup)
consistency of where shit goes for end users

Here's what I found (up to but excluding 5000s)
 101 numbers containing 143 [FF tags
---
  71 numbers with a single pref
      71 tags, movestotopline=77, duplicityreduction= 0

   7 numbers where some multi-prefs don't have a tag so they can't move
       8 tags, movestotopline= 0, duplicityreduction= 0

   9 numbers where tags are variable so they can't move
      32 tags, movestotopline= 0, duplicityreduction= 0

  14 numbers where all multi-prefs have a tag and the tag is the same
      32 tags, movestotopline=14, duplicityreduction=18

 TOT (check)
 ===
 101 numbers
     143 tags, movestotopline=91, duplicityreduction=18 tags removed

Although this would also include deprecated, for some reason I didn't bother to analyze that. 91 numbered items, that's a lot of items to improve "readability" (although I could counter that as end users we would get used to it), and it also removes duplication: 18 tags would be saved (duplication currently stands at 12½%, do we want that? if every pref had a version that would be 60 odd extra tags). Also, we would save characters when we can do away with the  // (just sayin).
So, knowing that @overdodactyl can still achieve an end result regardless of what we do with these (although we would still keep the square brackets, and it cleans up having a 1st line tag with other release tags in the user_pref line - i.e if the 1st line has one, apply to all children)
It really comes down to consistency IMO. Either we always stick them against each pref, or we keep our smarter hybrid system.
I'm leaning towards our hybrid (it's more elegant). I know E wants status quo. Can I get some opinions? @overdodactyl @claustromaniac

[SETTING] Privacy & Security>SecurityDeceptive Content and Software Protection - 3 times

that's because there are three numbered items, previously they all had the same string "(under Options>Privacy & Security)" in the first line.
It's just cleaner on a new line, and it's a setting (so tag it). Do we really need to list the full thing - it gets duplicitous and long
eg " * [SETTING] Privacy & Security>SecurityDeceptive Content and Software Protection>Warn you about unwanted and uncommon software" would be the longest one, at 128 chars and they only repeat what the description says

it's missing a >, that's all :)

Do you mean to include it in the /** SAFE BROWSING header instead of where they are? The 0410->0416's are more than just the three prefs we're talking about (but the setting does relate to what the header talks about 100%). How would you word it, "for 0410, 0411, 0412, go to blah blah and read the bit in quotes so understand what I mean"?
I think if we are going to give setting info, it should be with the pref where possible. It's kinda cool as one of the filters on the prototype, to be able to map everything to UI

We can do it in this pref, or I can make a note to do it later - what about 2002, one of the prefs is "obsolete"? I can't remember the story around it. When the FF51 pref was added did we keep the old one for ESR45 users?
user_pref("media.peerconnection.ice.default_address_only", true); // [FF42-FF50]

I've got a copy here with the changes reversed where appropriate. But it does show that in the past we have not followed this, eg FFv in 1st line and then variable ones for some of the children prefs.
And then it brings up another issue. Look at 0510 disable pocket: it says FF39+, bu that's the old pref that was deprecated. The new pref started in FF46. If the FF version is applied to each pref, then it removes all ambiguity AND prevents future fuckups

and if we put them back, ONLY if all multi-prefs have the same version

This is the biggest thing IMO.
Code wise it wouldn't make a big difference where tags are located (in-line or between /* .... ***/), so long as the info in the header applies to every subsequent preference.  Generally speaking, I think this is just good practice regardless to remove any confusion for the user.js file itself.

but I wouldn't mind some duplication

18 items dude ..
¯_(ツ)_/¯ IDK .. lets toss a coin

so long as the info in the header applies to every subsequent preference

AGREED, and this is where I picked up on a couple that didn't. :heavy_check_mark: will triple check
Will reverse back to our hybrid system.

OK, quadruple checked it locally. Even the github compare is much cleaner (90% of the changes are just tag format changes, eg square brackets). But it does show that we had inconsistencies in where we put tags, eg in deprecated we even had a pref line that should have been in the 1st line.
Awaiting reviewers

It's looking good to me.  Only thing that caught my eye was:
0510: disable Pocket (FF39+) --> 0510: disable Pocket [FF46+]
Was the version change intentional?

scroll up (and I said so in the commit) :)

And then it brings up another issue. Look at 0510 disable pocket: it says FF39+, bu that's the old pref that was deprecated. The new pref started in FF46.

deprecated FF46
// 0510: disable "Pocket" - replaced by extensions.pocket.*
   // [-] https://bugzilla.mozilla.org/1215694

actually, I should add [FF39+] to the old one

you've got a real thing for emojis there :cat2:
bump: waiting on big E's review... when he can, no big deal. Just can't really do any other commits otherwise it gets messy reconciling differences

LGTM too. Thanks Pantski

Hellalulah!!


Profile word usage confusing?

Mark Himelstein indicated through email that the use of 'profiles' is confusing. He suggested the following:
can we at least say "(not ISA profiles)"?

I changed all references to "profiles" to instead say "instruction profiles", save for the reference to profile-guided optimizations, since PGO is an industry standard term.  Is that sufficient to to eliminate any confusion?

"execution profiles" would seem better and broader in order to cover a wider range of (micro)architectural performance counters

@mark-riscv, would "execution" profiles help?

The issue is that many people reading the proposal are neither sw or toolchain folks. If you define execution profiles as tools/runtime related and not related to ISA-profiles then I am good. If not, it once again, in my opinion, leaves them to figure out what this means. So I suggets pick whatever language you want and just add a one line note saying whatever nomenclature you pick has no relationship to ISA profiles.

First sentence now reads: "Profile-guided optimization tools, such as autofdo, depend on accurate execution profiles (not to be confused with ISA profiles) to guide compilation and effect performance improvements."

perfect--------sent from a mobile device. please forgive any typos.On Feb 17, 2023, at 9:02 AM, Beeman Strong @.***> wrote:
First sentence now reads: "Profile-guided optimization tools, such as autofdo, depend on accurate execution profiles (not to be confused with ISA profiles) to guide compilation and effect performance improvements."
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were assigned.Message ID: @.***>


Fix outside landmines spawning in the air

This PR fixes outside landmines spawning in the air, it also sets their rotation to align with the ground.
This is achieved by casting a ray downwards and finding the hit position and normal.
Also, there was an issue where previously spawned in landmines wouldn't get cleaned up when changing maps. We now mark landmines with an OutsideLandmine marker component which allows us to easily clean them up on the next round, before spawning new ones.

A huge thank you @WarrenHood for the patch. I will update it ASAP.


x/tools/cmd/gopls: hover returns error when over non-identifier

What version of Go are you using (go version)?

$ go version
go version devel +9a00e64633 Fri Jul 5 12:11:36 2019 +0000 linux/amd64
$ go list -m golang.org/x/tools
golang.org/x/tools v0.0.0-20190706070813-72ffa07ba3db
$ go list -m golang.org/x/tools/gopls
golang.org/x/tools/gopls v0.1.2-0.20190706070813-72ffa07ba3db

Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE="on"
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/myitcv/.cache/go-build"
GOENV="/home/myitcv/.config/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/myitcv/gostuff"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/home/myitcv/gos"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/home/myitcv/gos/pkg/tool/linux_amd64"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/home/myitcv/gostuff/src/github.com/myitcv/govim/go.mod"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build249835069=/tmp/go-build -gno-record-gcc-switches"

What did you do?
Take the following simple example:
package main

import "fmt"

func main() {
	fmt.Println()
}

In Vim using govim, if we hover over the () of main() then we get the following response from gopls:
[Trace - 10:02:06 AM] Sending request 'textDocument/hover - (6)'.
Params: {"textDocument":{"uri":"file:///home/myitcv/gostuff/src/github.com/myitcv/playground/main.go"},"position":{"line":4,"character":10}}

[Error - 10:02:06 AM] send textDocument/hover#6 no identifier found

For the client to know this is an error that can be ignored would require it to know the structure of the document, which defeats the point of the LSP.
What did you expect to see?
In this instance I think gopls should simply report there is nothing to display, i.e. return empty string with no error.
What did you see instead?
As above.

cc @stamblerre @ianthehat

Duplicate of https://github.com/golang/go/issues/32967


Picking - mobile tap

Is there any easy way - setting to make picking more successful on tap?
Cheers

@primozs Are you referring to being unable to select a precise pixel in touch ux? We don't currently have a setting for this, but there is an open discussion regarding the support of something like pickingRadius. @ibgreen
Meanwhile, a work around could be rendering an extra invisible layer with "fat" geometries for picking (e.g. use [0,0,0,0] as color and twice the line width).

Hi, @Pessimistress
Yes, its very hard to tap select or touch drag start. I was thinking to make my one picking with geo point (x,y) similar like mapbox tile feature query. In my case viewport feature query.
Thank you for info and direction!

@primozs does this https://github.com/uber/deck.gl/pull/641 solve your issue

@shaojingli Hi, I was checking this yesterday. I saw that there is also feature query option now, but I did not try it in my code. I only tried picking radius in layer browser.  It looks good I guess this can be closed. Thank you for this nice project.


ENH: allow FeatureData[MAG] as input to evaluate_busco action

This PR is a stand-in replacement for #151, which was already too hard to merge because of changes incorporated into the main branch. Therefore it closes #151 and closes #111 (its associated issue).
Run it locally

Check out the PR branch.

Assuming 1) you already have a local copy of q2-moshpit installed in editable mode in your activated virtual environment and 2) the working directory is q2-moshpit; run the following.

PR=159
git fetch origin pull/${PR}/head:pr-${PR}
git checkout pr-${PR}

Let's get you some data to play with:

cd <i'll_test_this_here>
wget https://polybox.ethz.ch/index.php/s/WnZanIQECtwPEVu/download -O collated_mags.qza

Test it out!

qiime moshpit evaluate-busco
   --i-bins collated_mags.qza /
   --p-lineage-dataset bacteria_odb10 /
   --o-visualization busco.qzv /
   --o-results-table results.qza /
   --verbose --parallel --p-num-partitions 3

qiime tools view busco.qzv

@misialq the CI is fetching an outdated version of q2-types so the tests are failing. We can wait or you can merge it manually :)


on Debian with apt installation method, apt-get update is not run, leading to package download problems

When using kitchen-salt on Debian with apt installation method, I always got error messages about missing packages.
I think it could be solved adding a step to run apt-get update before doing the salt-minion installation.
Get:1 http://security.debian.org jessie/updates InRelease [63.1 kB]
Ign http://repo.saltstack.com jessie InRelease
Ign http://repo.saltstack.com jessie Release.gpg
Get:2 http://security.debian.org jessie/updates/main Sources [190 kB]
Ign http://httpredir.debian.org jessie InRelease
Get:3 http://httpredir.debian.org jessie Release.gpg [2,373 B]
Get:4 http://security.debian.org jessie/updates/main amd64 Packages [352 kB]
Ign http://repo.saltstack.com jessie Release
Get:5 http://httpredir.debian.org jessie Release [148 kB]
Err http://repo.saltstack.com jessie/main amd64 Packages

Err http://repo.saltstack.com jessie/main amd64 Packages

Get:6 http://httpredir.debian.org jessie/main Sources [7,056 kB]
Err http://repo.saltstack.com jessie/main amd64 Packages

Err http://repo.saltstack.com jessie/main amd64 Packages

Err http://repo.saltstack.com jessie/main amd64 Packages
         404  Not Found [IP: <IP_ADDRESS> 80]
Get:7 http://httpredir.debian.org jessie/main amd64 Packages [6,776 kB]
Fetched 14.6 MB in 6s (2,145 kB/s)
       W: Failed to fetch http://repo.saltstack.com/apt/debian/8/amd64/salt-latest/dists/jessie/main/binary-amd64/Packages  404  Not Found [IP: <IP_ADDRESS> 80]

       E: Some index files failed to download. They have been ignored, or old ones used instead.

Relevant part of my .kitchen.yml
provisioner:
  name: salt_solo
  salt_install: apt
  salt_version: latest
  salt_apt_repo: http://repo.saltstack.com/apt/debian/8/amd64
  salt_apt_repo_key: http://repo.saltstack.com/apt/debian/8/amd64/latest/SALTSTACK-GPG-KEY.pub

I don't have this problem since a few days, so it may came from my setup.

This depends on the state of the OS/VM. If apt update was never previously run, you have to run it in order to issue further apt commands. I guess if you would instal a VM from local media that could be the case. Otherwise, it's not a bad idea to run it either before the scripts, so I am reopening this issue and will issue a PR in a bit.

@ek9 you're right, it seems dependent of the 'freshness' of the image used (we use custom built Vagrant images).

It's already the case : https://github.com/simonmcc/kitchen-salt/blob/master/lib/kitchen/provisioner/install.erb#L36
Actually the error is here :
W: Failed to fetch http://repo.saltstack.com/apt/debian/8/amd64/**salt-**latest/dists/jessie/main/binary-amd64/Packages  404  Not Found [IP: <IP_ADDRESS> 80]

The salt- shouldn't be here. It's already fixed on master branch but no new release was created.
So it depends on the version of kitchen-salt you're using.
On master :

I am going to be doing a release soon.
I am going to go ahead and close this issue for now.
Thanks,
Daniel

I am going to go ahead and close this issue for now.

Thanks! Actually this issue is already fixed.

oh, then awesome.


update TiKV adopters list

Signed-off-by: Wenting Liu<EMAIL_ADDRESS>
What problem does this PR solve?
This PR is related to https://github.com/tikv/tikv/pull/7464 and https://github.com/tikv/tikv/pull/7789.  I wrongly deleted my repo so those two could not be merged.
Problem Summary:
What is changed and how it works?
Proposal: xxx
What's Changed:
Related changes

PR to update pingcap/docs/pingcap/docs-cn:
PR to update pingcap/tidb-ansible:
Need to cherry-pick to the release branch

Check List
Tests

Unit test
Integration test
Manual test (add detailed scripts or steps below)
No code

Side effects

Performance regression

Consumes more CPU
Consumes more MEM

Breaking backward compatibility

Release note

No release note

/merge

/run-integration-common-test


Fixing stats collection from server

Codecov Report
Attention: Patch coverage is 87.50000% with 3 lines in your changes missing coverage. Please review.

Project coverage is 36.40%. Comparing base (5562cfa) to head (2e0e6fe).

Files with missing lines
Patch %
Lines

info/as_parser.go
87.50%
3 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##           master      #62      +/-   ##
==========================================
+ Coverage   36.24%   36.40%   +0.15%
==========================================
  Files          23       23
  Lines        5615     5618       +3
==========================================
+ Hits         2035     2045      +10
+ Misses       3441     3434       -7
  Partials      139      139

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Swift Compiler Error (Xcode): Cannot find 'pronunciation' in scope

I have some problems to use  mobile_scanner: ^0.2.0, Swift Compiler Error (Xcode): Cannot find 'pronunciation' in scope /Flutter/flutter/.pub-cache/hosted/pub.flutter-io.cn/mobile_scanner-0.1.3/ios/Classes/Util.swift:110:131]()

The issue seems to be here in Util.swift:
extension BarcodePersonName {
    var data: [String: Any?] {
        return ["first": first, "formattedName": formattedName, "last": last, "middle": middle, "prefix": prefix, "pronunciation": pronunciation, "suffix": suffix]
    }

If I just delete that argument from my locally cached plugin, it works (for now)

This is because you are using an older version of MLKit cocoapod. Please run pod update in the ios folder of your application. I also constrained the version so this won't happen again.


Centering footer buttons.

The change relates to the centring of the button section. By default in SF this section is centred and this is now more intuitive to use.

Hi @KamilGadawski ,
Could you :

change the target branch to releaseCandidate
update the CHANGES.md file to describe this update

Thanks !

Thanks for this update but could you start from releaseCandidate in order to have only the updates you've made in the files Changes section ? Also you did not add your changes in CHANGES.md file

Changes have been added to the files indicated.

Please create a new branch from releaseCandidate, the one you request to merge still contains the elements from master :

Also, could you follow the convention from the CHANGES.md ie:

Add option to open extension pages in a new tab using keyboard shortcuts (contribution by Joshua Yarmak)


Fix fc-list error incurred while running install.sh

fc-list printed error message because it tried parsing incomplete 30-icons.conf file.
Hence, make a temporary file and then rename it to 30-icons.conf.
Use ~/.local/share/fonts directory instead of ~/.fonts directory which is deprecated.

@sebastiencs  Hello 😀
Can you review this PR?
I got to know this repository from the issue of 'all-the-icons' and came here  to understand how to make my Emacs display icons in terminal.
Your work about unifying fonts was very good👍👍


ECONNRESET

when starting chlient,I get this error:
X:[workspace][node.js]\minecraft\heroku-minecraft>coffee proxy/connect.coffee
wywzxxz-heroku.herokuapp.com
Warning: Native modules not compiled.  XOR performance will be degraded.
Warning: Native modules not compiled.  UTF-8 validation disabled.
TCP server listening on <IP_ADDRESS>:25565
Attempting to open WebSockets connection to ws://wywzxxz-heroku.herokuapp.com/tu
nnel
Buffering TCP Data: localhosts
Buffering TCP Data: xxxx
WebSocket connected
Flushing buffered data over WebSockets: localhosts
Flushing buffered data over WebSockets: xxxx
events.js:72
throw er; // Unhandled 'error' event
^
Error: read ECONNRESET
at errnoException (net.js:904:11)
at TCP.onread (net.js:558:19)
I then read heroku log, seems it works fine on sever.
Any idea of this?

There's a new version that cleaned up a lot of different issues - I'm going to close this for now, though let me know if you run into this issue again.


Confusion over 30 endpoint limit

I am still confused over the 30 endpoint limit, specifically what can I do to work around the limit?
Your documentation says..

Note
There may be up to 30 endpoints in a single sync group if there is only one sync group. If there is more than one sync group, the total number of endpoints across all sync groups cannot exceed 30. If a database belongs to multiple sync groups, it is counted as multiple endpoints, not one.

We are working with an Azure Hub and multiple on-premise databases where we have managed to hit the 30 endpoint limit, which according to the above description I understand.
My confusion lies in the following:

the total number of endpoints across all sync groups cannot exceed 30.
Sync Groups are associated with a database, hosted on a SQL Server..

So how do I rectify the issue.
On the same subscription we created a second SQL Server and Sql Database:
So we have the following topology:

Subscription001

SQL1\SyncDb1

This has hit the 30 Endpoint Limit

SQL2\SyncDb2

This has nothing on it

When we open SyncDb2 we see something strange:

All the agents that are registered against SyncDb1 are visible on SyncDb2?

When we attempt to register an agent that is NOT on any existing Sync Group against SyncDb2 we receive the error:

Failed to perform data sync operation: Quota 'SyncGroupMemberLimitPerServer' exceed, failed to create sync member

I would assume I could create a new database and this database would then provide another 30 endpoints, but this appears to NOT be the case.
I then thought if I created another SQL Server it would allow another 30 endpoints, but it did not?
I then used the follow topology:

Subscription001

SQL1\SyncDb1

This has hit the 30 Endpoint Limit

Subscription002

SQL2\SyncDb2

This has nothing on it

And I am able to register the agent against SyncDb2 in this configuration.
So is the limit 30 endpoints per

SQL Database
SQL Server; or
Per Subscription

At the moment with our testing it is appearing to be a limit per Subscription.
This would seem to fly in the face of this article which suggests you can create multiple sync groups.
https://azure.microsoft.com/en-us/blog/sync-sql-data-in-large-scale-using-azure-sql-data-sync
Can you advise:

Are we doing something wrong.
Is this a bug
Is your documentation incorrect?

Thanks :-)

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

ID: 18c6af1a-b5e6-70b7-999b-309540e3edb8
Version Independent ID: fa45590e-fbcc-fba6-936d-cbaa4505ff01
Content: What is SQL Data Sync for Azure? - Azure SQL Database
Content Source: azure-sql/database/sql-data-sync-data-sql-server-sql-database.md
Service: sql-database
Sub-service: sql-data-sync
GitHub Login: @WilliamDAssafMSFT
Microsoft Alias: wiassaf

I suppose the confusion is what actual defines a "SyncGroup" that the 30 endpoint limit applies too. If you read the multi-level sync architecture document where is has a master sync group and sub-sync groups, I can't believe I would need to create individual subscriptions to implement that structure?
To be clear we tried these topologies where attempting to register a new agent against SyncDb2.
Two Dbs on the Same SQL Server - Failed

Subscription001

SQL1\SyncDb1

This has hit the 30 Endpoint Limit

SQL1\SyncDb2

This has nothing on it

Two SQL Servers - Same Subscription - Failed

Subscription001

SQL1\SyncDb1

This has hit the 30 Endpoint Limit

SQL2\SyncDb2

This has nothing on it

Different Subscriptions - Success

Subscription001

SQL1\SyncDb1

This has hit the 30 Endpoint Limit

Subscription002

SQL2\SyncDb2

This has nothing on it

Hi @jcrawfor74, this avenue of communication is not for support or product questions though, if you are having a production issue, please reach out to Microsoft Support or your support provider.
This may not be the best forum for in-depth product questions and technical workarounds. As is obvious but our comms here, our turnaround for response to Docs issues doesn't follow an SLA. I recommend Microsoft Q&A (SQL Server), Microsoft Q & A (Azure SQL), SQL Server Feedback.
We'll leave this open and continue to investigate how we could improve documentation here, but if you are encountering a production design problem please do reach out to Microsoft Support or your support partners.

Hi @WilliamDAssafMSFT,
Thanks for your feedback, I appreciate this is quite a technical question and I am not expecting production support on this channel.. but..
You have not actually answered the question which I posed, which could be updated correctly and clearly in your documentation to avoid confusion.
This is the wording you currently have on the support documentation

There may be up to 30 endpoints in a single sync group if there is only one sync group. If there is more than one sync group, the total number of endpoints across all sync groups cannot exceed 30. If a database belongs to multiple sync groups, it is counted as multiple endpoints, not one.

This section is where the confusion is:

the total number of endpoints across all sync groups cannot exceed 30

The question I am posing is, "across all sync groups", where, in what context?

Per database
Per SQL Server
Per subscription

To me it seems that it is Per Subscription?
(otherwise creating a new SQL Server within the subscription should give me a further 30 endpoints?)
Can you please confirm my assumption and then clarify your documentation to make it clear how this limit is actually applied.
Potentially this version would remove the confusion

the total number of endpoints across all sync groups within a subscription cannot exceed 30

Thanks

Hi @Jcrawfor74 -
You're right, this isn't the right place to ask these type of technical support questions. :) But I would like to help if Docs can be more clear.
I think you have your answer - the total number of endpoints across all sync groups in a subscription cannot exceed 30. You've demonstrated this with the second subscription in your original post.
I'll update the docs if I can get confirmation of this internally, there may be some more nuance that requires investigation.
For now, I'll close this issue. Thanks for drawing attention to this.
#please-close


Build(deps-dev): Bump @types/qs from 6.9.7 to 6.9.8 (#5118)

Pull request opened by the merge tool on behalf of #5118

Merged in d8ea5aa172c5988baceafd5830f777277aab5a93


tf.bitwise.left_shift's behavior is different on cpu and gpu on tensorflow 2.18.0-dev20240728

Issue type
Bug
Have you reproduced the bug with TensorFlow Nightly?
Yes
Source
binary
TensorFlow version
v1.12.1-113709-gdc368f6cbd8 2.18.0-dev20240728
Custom code
Yes
OS platform and distribution
Ubuntu 22.04.4 LTS (x86_64)
Mobile device
No response
Python version
3.11.0
Bazel version
No response
GCC/compiler version
No response
CUDA/cuDNN version
cuda_12.4.r12.4/compiler.34097967_0
GPU model and memory
No response
Current behavior?
tf.bitwise.left_shift's behavior is different on cpu and gpu.
on cpu:
with tf.device("/cpu:0"):
    x = tf.constant([-2, -1, 0, 1, 2])
    y = tf.constant([3, 2, 1, 0, -1])
    z = tf.bitwise.left_shift(x, y)
    print(z.numpy()) # [-16  -4   0   1   2]

on gpu:
with tf.device("/gpu:0"):
    x = tf.constant([-2, -1, 0, 1, 2])
    y = tf.constant([3, 2, 1, 0, -1])
    z = tf.bitwise.left_shift(x, y)
    print(z.numpy())

z on cpu and gpu are not equal.
Standalone code to reproduce the issue
with tf.device("/cpu:0"):
    x = tf.constant([-2, -1, 0, 1, 2])
    y = tf.constant([3, 2, 1, 0, -1])
    z = tf.bitwise.left_shift(x, y)
    print(z.numpy()) # [-16  -4   0   1   2]

with tf.device("/gpu:0"):
    x = tf.constant([-2, -1, 0, 1, 2])
    y = tf.constant([3, 2, 1, 0, -1])
    z = tf.bitwise.left_shift(x, y)
    print(z.numpy()) # [-16  -4   0   1   0]

Relevant log output
No response

Maybe not a bug, because

If y is negative, or greater than or equal to the width of x in bits the
result is implementation defined.

@wangzhen0518,
I was able to reproduce the issue on tensorflow 2.15, v2.17 and tf-nightly. Kindly find the gist of it here.

@wangzhen0518,
As per the document it is mentioned that If y is negative, or greater than or equal to the width of x in bits the result is implementation defined, also I checked with alternative inputs for the y and observed when the y is +ve, it is providing the same result and when y is -ve, it provided the same result as mentioned.
https://www.tensorflow.org/api_docs/python/tf/bitwise/left_shift
Kindly find the gist of it here for the reference.
Thank you!

Thanks for your explanation. I am curious about whether it is necessary to maintain consistent results across different backends.

@wangzhen0518,
The reason could be due to the optimized way of calculating numbers on Nvidia which is different compared to others, there will be a small amount of precision errors. Thank you!


Documenting / detailing error messages

It would be great to (1) have better documentation on error message and / or (2) give more details on them .. ie

What do these errors mean:

no feed updates found
payload is greater than 4096

It would be great to have more details returned on reasons for failure for this:

error uploading data

@tfius please check and prioritize.

More clear messages would help developers

Feed does not exist or was not updated yet.
Payload size is too large. Maximum payload for feed is 4096 bytes.
for 2.
must discuss with @asabya, to many potential causes for this error

"no feed updates found" : this seems self explanatory to me. May be we can remove the "feed", just say "requested resource not found"

Any info on what caused "payload is greater than 4096"? @salmanff. As @tfius said while creating a feed, the payload should be less than 4096.

On many cases we just forward what bee sends us, we don't get much info on such cases. "error uploading data" is one of them. We can improve this by saying which request caused this.

Agreed, self explanatory if dev has insight how feeds work and has knowledge about limitations. We should add bit more explanatory information, like in my first comment.

lets add information about failed request.

Hi - thx and sorry for late response.
"no feed updates found" moved to discord discussion. But I understand it, even if the "Schrodinger's directories" issue remains.
On "payload is greater than 4096". This error also seems to be triggered when two write operations take place in quick sequence. So I dont think it only relates to the payload of one API call. Interestingly, it looks like the operation is finalised successfully even when the error is issued (which is why it took me forever to figure out what was going on.) ie It doesnt look like there is an error, despite the error message.
This extract of my log may explain:
First Write to filename: rec-557-1644056305149.adb
  writeOptions: {
    hostname: [REMOVED]
    path: '/v1/file/upload',
    method: 'POST',
    headers: { [REMOVED]}
  },
  contents: '{"age":5,"_id":"jYKj9di3IP5Wq6by"}\n'
}

Returns:
'{"Responses":[{"file_name":"rec-557-1644056305149.adb","message":"uploaded successfully"}]}\n' +  '\n'

Immediately afterwards, Second Write to file name: rec-581-1644056311362.adb :
writeOptions: {
    hostname: [REMOVED],
    path: '/v1/file/upload',
    method: 'POST',
    headers: {[REMOVED] }
  },
  contents: '{"age":57,"_id":"wAgMM1OvLJX8D1FZ"}\n'
}

Returns
'{"Responses":[{"file_name":"rec-581-1644056311362.adb","message":"modify dir entry : payload is greater than 4096"}]}\n'
However, when you read the same file, it has been written. Reading it results in:
{ err: null, returns: '{"age":57,"_id":"wAgMM1OvLJX8D1FZ"}\n' }
Perhaps this is not a documentation issue.. but more fundamental about when a payload error should be sent at the swarm level.

@tfius , is this implemented / solved?

@tfius what is the status?

@crtahlin There has been few improvements regarding these kind of messages in #186


Fix Clean Import Path bug when concerning CSS

Update rule to ignore @import when concerning CSS files
Fixes #95
DCO 1.1 Signed-off-by: Ben Griffith<EMAIL_ADDRESS>

@bgriffith you'll need to update the tests on this one to match the new method with the merge-defaults option.

All done Mr Purdy! I love the new option.


coverage without token?

No CODECLIMATE_REPO_TOKEN found. A CODECLIMATE_REPO_TOKEN must be specified as an environment variable.

You need the token. In which environment are you using this? Local, travis, etc.. ?

exactly, i ask for support of that feature.

In which environment are you using this

For travis, look here if you want to keep your key a secret: http://docs.travis-ci.com/user/environment-variables/#Using-Settings.
Codeclimate should want you on the project site about not setting up test coverage, just follow their instructions to get the key. (Starting with the "Set Up Test Coverage" button)

yea, im talking to completely support without token, cuz all that kind of things are very shitty shits that cost developing and CI/testing time - click here, fill that input, click there - GOD DAMN.
and the fuckin coveralls app
LOL :laughing:

That's completely up to the codeclimate team, if there's no activity or commitment, there is probably no solution in sight. But anyway, since (I assume) we don't know what happens at codeclimate, its all speculative.

It seems like CODECLIMATE_REPO_TOKEN is no longer needed?
If that's the case, it's probably worth removing from readme - I've already spent 15 min looking for it...
If it is still needed where do I find it?
Thank you!

Hey @tunnckoCore,
Thanks for your feedback. At this time, we do require the CODECLIMATE_REPO_TOKEN during test reporter runs in order to authorize the reporter with the intended repository on Code Climate.
This protects any Code Climate repository against accidental or malicious manipulation.
Many CI services allow you to add environment variables for use during builds. For Code Climate test reporters, you can add a env var with the name CODECLIMATE_REPO_TOKEN and the CC repo token as the value.
The repo token can be found in your Code Climate repository settings. Our docs on setting up test coverage can be found here.
Hope that helps. Sorry for the inconvenience.


Boost workflows and add some tests

Hi @mooniean
I've added an extra workflow for packaging. You just need to set your pypi username and password in a github secret variable and then every time you tag a version "v0.1.0" and create a release from that version it will be published automatically to pypi.
I've also added a few more tests which all seem to be passing. Changing python version >=3.6 didn't cause any problems either.
Let me know what would be helpful next for the JOSS paper!
Best wishes
James

LGTM!! I'll add the secrets so hopefully it works with the uploading!


Resetting forms

It clears the inputs but data is still there
http://jsfiddle.net/5a6z6xmk/

You'll have to add a reset listener to the form element and reset data there. This might be a bit inconvenient but it gives you the flexibility to reset to a set of non-empty default values.

Oh I thought it should empty the data automatically, I just figured out that resetting a form doesn't fire it's inputs change events.

bummer

You'll have to add a reset listener to the form element and reset data there. This might be a bit inconvenient but it gives you the flexibility to reset to a set of non-empty default values.

nice


Add Conversations.GetConversationPagedMembers tests

Add tests for the Conversations.GetConversationPagedMembers method
Include test that validates tracing feaures

not tested:

ContinuationToken feature
CustomHeaders feature

Pull Request Test Coverage Report for Build 40969

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+1.07%) to 51.819%

Totals

Change from base Build 40863:
1.07%

Covered Lines:
4459

Relevant Lines:
8605

💛  - Coveralls

These tests were included a part of #1007


Appraisal

It's awesome.

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

ID: 8b514dfb-f00b-8ac3-4027-7a28770f959e
Version Independent ID: 7db3af08-9406-10da-76a1-1f8db30d1d2d
Content: Hello World interactive tutorial - C# quickstarts
Content Source: docs/csharp/quick-starts/hello-world.yml
Product: dotnet-csharp
GitHub Login: @BillWagner
Microsoft Alias: wiwagn

Thanks, @vinrok. It's nice to hear from you, and we're happy that you enjoyed the interactive tutorial!


[objetc Object] to "Click to expand..." in the tree information that …

…is shown

test this please


Remove category/tags from All Stories view

Feature Description
Per discussion in #489, category and tags for story organization won't be supported in the version 1.0 of the story editor. As such, we need to remove the category and tags from being shown in:

story dashboard list view
All Stories view (classic wp view)

Additional Context
#489

Do not alter or remove anything below. The following sections will be managed by moderators only.
Acceptance Criteria

Implementation Brief

I can handle part 2)

I have created  -  #2073 but it seems to break the dashboard in list view.
I can leave this with @BrittanyIRL @carlos-kelly to do that work before  ( or as part of ) #2073

Perfect. Yeah we use the IDs to iterate the GET of categories and tags and match them up. We can drop that and those columns!

@spacedmonkey Would you be fine with us adding the JS-part to your branch in #2073 or we can branch off of that. Either works.

Would you be fine with us adding the JS-part to your branch in #2073 or we can branch off of that. Either works.

@carlos-kelly Feel free to add to my PR.

Verified in QA (merged - reviewed on Master)

Assigning to you for UAT step & closing


Can you add autoclicker for r click with kd and autofish

this is needed in order to put the bot on afk

anti-afk is already there, if i wanna add auto fish the app would get bloated


Pubmed Dataset Accuracy

Hi,
I've tried running your code on the Pubmed dataset using the configuration you mentioned in the paper. With 100 runs, the accuracy is about 77.61 +- 0.78 while the paper reports 79.0 +- 0.3. I'm wondering if you have done some additional modifications as in the issue about Citeseer accuracy and it will be great if you can provide these details. Thanks a lot!

Hi Mufei,
You are correct indeed -- please see #12 .
Thanks,
Petar


fix(bch-js): Bumping to v3.4.1

:tada: This PR is included in version 1.5.1 :tada:
The release is available on npm package (@latest dist-tag)
Your semantic-release bot :package::rocket:


Database column name "study_id" is misleading

Description
The field name "study_id" which is used for identification of study participants is misleading and should be renamed. It sould indicate that this value represents a subject identifier.
Study systems usually reference the following terms:

SubjectID (integer) as database reference for table relations
SubjectNumber (text) for a generated or assigned identifier for study participants that is used to identify subjects within a study center

ToDo
The name of the field should be updated in the code and all relating documentation.

Merged changes after validation #7


RPX hash function

Describe your changes
This is a first attempt at implementing a variation, called RPX, of the xHash12 hash function. There is a lot of code overlap with RPO and this PR tries to reduce that but it would probably make more sense to create a trait in order to simplify even more.
Checklist before requesting a review

Repo forked and branch created from next according to naming convention.
Commit messages and codestyle follow conventions.
Relevant issues are linked in the PR description.
Tests added for new functionality.
Documentation/comments updated according to changes.

Looks good!
Using the round constants of RPO should definitely be fine. I was thinking more of the scenario when one has a specification of how to generate them starting from something generic e.g., RPX Hash. We can comeback to this once we have constant generation in a specification.


Error on Update Flutter 2.0.1

Error using dependency in Flutter v 2.0.1
ERROR:
Because open_mail_app >=0.0.3 <0.1.0-nullsafety.0 depends on url_launcher ^5.5.0 and wallet_app depends on url_launcher ^6.0.2, open_mail_app >=0.0.3 <0.1.0-nullsafety.0 is forbidden.
So, because wallet_app depends on open_mail_app ^0.0.8, version solving failed.
pub get failed (1; So, because wallet_app depends on open_mail_app ^0.0.8, version solving failed.)

Done on version 0.1.0!


[DISCUSSION GUIDE ] Week 10 - Urban Green Space

Agenda:

[ ] Reading/watching and discussion: https://github.com/earthlab-education/Earth-Analytics-2023-01-Intro/discussions/556
[ ] Student screen share - using for loops in the urban green spaces assignment. Hopefully the new notebook will be out, but if not work together as a class to change their code to perform the same analysis for both Humboldt Park and Lincoln Park neighborhoods (using a for loop)

/adminteamassign @earthlab-education/ea-instructors


Add funding reminder

This adds the forgotten funding reminder. It will show once after 30 minutes of activity.

Closing this in favor of #8397 and a reworked reminder logic.


Dependency elasticsearch/elasticsearch before 1.3.8 and 1.4.x before 1.4.3 security warning

elasticsearch/elasticsearch contains a remote exploit
"The Groovy scripting engine in Elasticsearch before 1.3.8 and 1.4.x before 1.4.3 allows remote attackers to bypass the sandbox protection mechanism and execute arbitrary shell commands via a crafted script."
reference: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1427

@thul The library itself is fine, it is advisable to:

upgrade elasticsearch
and/or configure script.groovy.sandbox.enabled: false if you don't need it

Upgrading the elasticsearch client could be a good move to keep the dependencies up to date (it will also help to integrate broadway with other libraries).

since https://github.com/qandidate-labs/broadway/pull/237 is merged you can use elasticsearch/elasticsearch-php 2.0


[FEATURE] Creating a Contact-Us screen in the application

Description
I'd create a contact-us screen, where the users would be presented with a form to fill in, and the responses would be sent to a secured Google sheet, where all responses would be listed down, along with user's email and timestamp to differentiate between the entries. I'd do the integration of google sheets with the app via Sheets API.
Screenshots

Additional information
Google sheets api: https://developers.google.com/sheets/api/guides/concepts

Hi @bhattabhi013 please assign me this!

Hi @jaivsh,
Assigning it to you.


fix(docs): fix Algorithm list

before

https://docs.gocrane.io/dev/tutorials/using-time-series-prediction/#algorithm
after

http://gocrane-crane-preview-pr-287.surge.sh/tutorials/using-time-series-prediction/#algorithm

@qmhu PTAL

/LGTM


The requested module 'solid-js' does not provide an export named 'addEventListener'

It seems like something has changed in solid JS, do you mind checking where it's going wrong?
The requested module 'solid-js' does not provide an export named 'addEventListener'
file:///F:/app/node_modules/.pnpm/solid-dismiss@1.2.1_solid-js@1.5.5/node_modules/solid-dismiss/dist/esm/index.js:1
import { addEventListener, children, classList, createComponent, createComputed, createEffect, createMemo, createSignal, createUniqueId, delegateEvents, effect, insert, isServer, mergeProps, on, onCleanup, setAttribute, sharedConfig, template, untrack } from 'solid-js';
         ^^^^^^^^^^^^^^^^
SyntaxError: The requested module 'solid-js' does not provide an export named 'addEventListener'
    at ModuleJob._instantiate (node:internal/modules/esm/module_job:123:21)
    at async ModuleJob.run (node:internal/modules/esm/module_job:189:5)
    at async Promise.all (index 0)
    at async ESMLoader.import (node:internal/modules/esm/loader:527:24)
    at async nodeImport (file:///F:/app/node_modules/.pnpm/vite@3.1.0/node_modules/vite/dist/node/chunks/dep-665b0112.js:53404:21)
    at async eval (/src/solid/Modal.jsx:15:31)
    at async instantiateModule (file:///F:/app/node_modules/.pnpm/vite@3.1.0/node_modules/vite/dist/node/chunks/dep-665b0112.js:53333:9) (x2)
09:28:07 AM [serve]

The requested module 'solid-js' does not provide an export named 'addEventListener'
file:///F:/app/node_modules/.pnpm/solid-dismiss@1.2.1_solid-js@1.5.5/node_modules/solid-dismiss/dist/esm/index.js:1
import { addEventListener, children, classList, createComponent, createComputed, createEffect, createMemo, createSignal, createUniqueId, delegateEvents, effect, insert, isServer, mergeProps, on, onCleanup, setAttribute, sharedConfig, template, untrack } from 'solid-js';
         ^^^^^^^^^^^^^^^^
SyntaxError: The requested module 'solid-js' does not provide an export named 'addEventListener'
    at ModuleJob._instantiate (node:internal/modules/esm/module_job:123:21)
    at async ModuleJob.run (node:internal/modules/esm/module_job:189:5)
    at async Promise.all (index 0)
    at async ESMLoader.import (node:internal/modules/esm/loader:527:24)
    at async nodeImport (file:///F:app/node_modules/.pnpm/vite@3.1.0/node_modules/vite/dist/node/chunks/dep-665b0112.js:53404:21)
    at async eval (/src/solid/Modal.jsx:15:31)
    at async instantiateModule (file:///F:/app/node_modules/.pnpm/vite@3.1.0/node_modules/vite/dist/node/chunks/dep-665b0112.js:53333:9)

Code that is giving error -
import Dismiss from "solid-dismiss";
import { createSignal } from "solid-js";

export const Modal = () => {
  const [open, setOpen] = createSignal(false);
  let btnEl;

  return (

      <button ref={btnEl}>Button</button>
      <Dismiss menuButton={btnEl} open={open} setOpen={setOpen}>

Popup text!

            Lorem, ipsum dolor.

      </Dismiss>

  );
};

I also tried the modal one, and its giving same error

This issue so far appears on solid-start project, which uses SSR. I'll look into this

I'm using astro with solid Js integration

Maybe is it because of some server side stuff? 🤔 I was loading it in client side iirc

update solid-dismiss to latest, which is ^1.2.3.
In your astro.config.mjs file, include vite noExternal properties, with the value of ["solid-dismiss"].
import { defineConfig } from "astro/config";
import solidJs from "@astrojs/solid-js";

export default defineConfig({
  integrations: [solidJs()],
  vite: {
    ssr: {
      noExternal: ["solid-dismiss"],
    },
  },
});

In the future I'll try make it work in SSR without having the user to include noExternal property in the vite config

Thanks for the super fast fix! Awesome 🎉


Enable asciidoctor-diagrams extension by default

I really like Hugo with asciidoctor. Now i am searching for a way to enable asciidoctor-diagrams extension by default without patching batch files. Also there should be a way to create the diagrams files in the public directory and link them by absolute paths in blog postings.
Are there plans to integrate such features in Hugo, or do i have to implement a "work-around" by myself?
Also, what is the prefered way to use Hugo, Asciidoc and server-side syntax highlighting with Codeway and callouts support?
Thanks in advance,
Mirko

/cc @anthonyfok