failed to install on Windows

Using gradle install in gradlex gives a error.
I believe that the main problem is: npm unavailable.  If you're running this command using sudo, make sure npm is available to sudo
Npm is installed and accessible via npm command from the same console.

sorry not sure what you mean.  we don't have an install target, and what is gradlex?

Sorry, was writing in a hurry. I mean beakerx and it has install task:
task install() {
  doLast {
    exec {
      commandLine(*(winOrUnix('pip', "install", "-e", ".")))
    }
    exec {
      commandLine(*(winOrUnix("jupyter", "nbextension", "install", "--py", "--symlink", "--sys-prefix", "beakerx")))
    }
    exec {
      commandLine(*(winOrUnix("jupyter", "nbextension", "enable", "--py", "--sys-prefix", "beakerx")))
    }
    project('js').tasks.install.execute()
  }
}

The same result if I use linkBeakerNbextension from root project

can you provide a complete log?
it should work.

Here is the log:
:beakerx:install
Obtaining file:///D:/beakerx/beakerx
    Complete output from command python setup.py egg_info:
    setup.py entered
    $PATH=C:\Anaconda3\Library\bin;C:\Anaconda3\Library\bin;C:\Program Files\ConEmu\ConEmu\Scripts;C:\Program Files\ConEmu;C:\Program Files\ConEmu\ConEmu;C:\ProgramData\Oracle\Java\javapath;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Program Files\TortoiseHg\;C:\Anaconda3;C:\Anaconda3\Scripts;C:\Anaconda3\Library\bin;C:\Program Files (x86)\Skype\Phone\;C:\Program Files\Calibre2\;C:\Program Files\jEdit;C:\Program Files (x86)\Pandoc\;C:\Program Files\Git\cmd;C:\Program Files (x86)\PuTTY\;C:\Program Files\nodejs\;C:\Users\darksnake\AppData\Local\atom\bin;C:\Users\darksnake\AppData\Local\Microsoft\WindowsApps;C:\kotlinc\bin;C:\Users\darksnake\.posh_gvm\gradle\current\bin;C:\Users\darksnake\AppData\Roaming\npm
    running egg_info
    running jsdeps
    C:\Anaconda3\lib\site-packages\setuptools-20.3-py3.5.egg\setuptools\dist.py:285: UserWarning: Normalizing '0.1.0.dev' to '0.1.0.dev0'
    `npm` unavailable.  If you're running this command using sudo, make sure `npm` is available to sudo
    rebuilding js and css failed
    missing files: ['D:\\beakerx\\beakerx\\beakerx\\static\\extension.js', 'D:\\beakerx\\beakerx\\beakerx\\static\\index.js']
Command "python setup.py egg_info" failed with error code 1 in D:\beakerx\beakerx\    Traceback (most recent call last):

      File "<string>", line 1, in <module>
      File "D:\beakerx\beakerx\setup.py", line 166, in <module>
        setup(**setup_args)
      File "C:\Anaconda3\lib\distutils\core.py", line 148, in setup
        dist.run_commands()
      File "C:\Anaconda3\lib\distutils\dist.py", line 955, in run_commands
        self.run_command(cmd)
      File "C:\Anaconda3\lib\distutils\dist.py", line 974, in run_command
        cmd_obj.run()
      File "D:\beakerx\beakerx\setup.py", line 45, in run
        raise e
      File "D:\beakerx\beakerx\setup.py", line 38, in run
        self.distribution.run_command('jsdeps')
      File "C:\Anaconda3\lib\distutils\dist.py", line 974, in run_command
        cmd_obj.run()
      File "D:\beakerx\beakerx\setup.py", line 109, in run
        raise ValueError(msg)
    ValueError: Missing file: D:\beakerx\beakerx\beakerx\static\extension.js
    npm is required to build a development version of widgetsnbextension

    ----------------------------------------
You are using pip version 8.1.1, however version 9.0.1 is available.
You should consider upgrading via the 'python -m pip install --upgrade pip' command.
:beakerx:install FAILED

FAILURE: Build failed with an exception.

* Where:
Build file 'D:\beakerx\beakerx\build.gradle' line: 31

* What went wrong:
Execution failed for task ':beakerx:install'.
> Process 'command 'cmd'' finished with non-zero exit value 1

It is form different computer with the same setup (win 10, Anaconda 3, npm). The result is the same.

please provide the log for what happens if you run gradle linkBeakerNbextension

Exactly the same:
:linkBeakerNbextension
Obtaining file:///D:/Work/beakerx/beakerx
    Complete output from command python setup.py egg_info:
    setup.py entered
Command "python setup.py egg_info" failed with error code 1 in D:\Work\beakerx\beakerx\
    $PATH=C:\Anaconda3\Library\bin;C:\Anaconda3\Library\bin;C:\Program Files\ConEmu\ConEmu\Scripts;C:\ProgramData\Oracle\Java\javapath;C:\Program Files\ConEmu;C:\Program Files\ConEmu\ConEmu;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;c:\Program Files\Java\jdk\\bin;C:\Program Files (x86)\AMD APP\bin\x86_64;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files (x86)\Windows Kits\10\Windows Performance Toolkit\;C:\Program Files\Calibre2\;C:\Program Files\Mercurial\;C:\Program Files\Git\cmd;C:\Users\darksnake\.posh_gvm\gradle\current\bin;C:\Users\darksnake\.posh_gvm\grails\current\bin;C:\Users\darksnake\.posh_gvm\groovy\current\bin;C:\MinGW\bin;C:\Users\darksnake\AppData\Local\atom\bin;C:\Users\darksnake\AppData\Roaming\npm;C:\Program Files\Docker Toolbox;C:\Program Files\ImageMagick-7.0.0-Q16;C:\Program Files\jEdit;C:\Program Files\nodejs\;C:\Users\darksnake\AppData\Local\Microsoft\WindowsApps;C:\Program Files (x86)\Pandoc\;C:\Program Files\MiKTeX 2.9\miktex\bin\x64\;C:\Program Files\TortoiseHg\;C:\Program Files (x86)\Skype\Phone\;C:\Anaconda3;C:\Anaconda3\Scripts;C:\Anaconda3\Library\bin;C:\Users\darksnake\.posh_gvm\gradle\current\bin;C:\Users\darksnake\.posh_gvm\grails\current\bin;C:\Users\darksnake\.posh_gvm\groovy\current\bin;C:\MinGW\bin;C:\maven\bin;C:\Users\darksnake\.posh_gvm\jbake\current\bin;C:\Users\darksnake\AppData\Local\atom\bin;C:\Users\darksnake\AppData\Roaming\npm;C:\Program Files\ImageMagick-7.0.0-Q16;C:\Program Files\jEdit;C:\Program Files\Calibre2\;C:\Program Files\nodejs\;C:\Users\darksnake\AppData\Local\Microsoft\WindowsApps;C:\Program Files\CMake\bin
    running egg_info
    running jsdeps
    C:\Anaconda3\lib\site-packages\setuptools-27.2.0-py3.6.egg\setuptools\dist.py:331: UserWarning: Normalizing '0.1.0.dev' to '0.1.0.dev0'
    `npm` unavailable.  If you're running this command using sudo, make sure `npm` is available to sudo
    rebuilding js and css failed
    missing files: ['D:\\Work\\beakerx\\beakerx\\beakerx\\static\\extension.js', 'D:\\Work\\beakerx\\beakerx\\beakerx\\static\\index.js']
    Traceback (most recent call last):
      File "<string>", line 1, in <module>
      File "D:\Work\beakerx\beakerx\setup.py", line 166, in <module>
        setup(**setup_args)
      File "C:\Anaconda3\lib\distutils\core.py", line 148, in setup
        dist.run_commands()
      File "C:\Anaconda3\lib\distutils\dist.py", line 955, in run_commands
        self.run_command(cmd)
      File "C:\Anaconda3\lib\distutils\dist.py", line 974, in run_command
        cmd_obj.run()
      File "D:\Work\beakerx\beakerx\setup.py", line 45, in run
        raise e
      File "D:\Work\beakerx\beakerx\setup.py", line 38, in run
        self.distribution.run_command('jsdeps')
      File "C:\Anaconda3\lib\distutils\dist.py", line 974, in run_command
        cmd_obj.run()
      File "D:\Work\beakerx\beakerx\setup.py", line 109, in run
        raise ValueError(msg)
    ValueError: Missing file: D:\Work\beakerx\beakerx\beakerx\static\extension.js
    npm is required to build a development version of widgetsnbextension

    ----------------------------------------
:linkBeakerNbextension FAILED

FAILURE: Build failed with an exception.

* Where:
Build file 'D:\Work\beakerx\beakerx\build.gradle' line: 31

* What went wrong:
Execution failed for task ':beakerx:install'.
> Process 'command 'cmd'' finished with non-zero exit value 1

According to build.gradle, it is just an alias to :beakerx:install, so it could not be the other way around.

By the way :kernel:groovy:install works fine. It installs groovy console which actually works. Beaker features report errors though.

OK, I localized the problem: check_call(['npm', '--version']) produces an error even if I am running it from the IPython console. npm --version from system terminal works fine.

Fixed the problem by replacing check_call(['npm', '--version']) with check_call(['npm', '--version'], shell = True). Now I get the following:
PS D:\beakerx> gradle linkBeakerNbextension
:linkBeakerNbextension
Obtaining file:///D:/beakerx/beakerx
    Complete output from command python setup.py egg_info:
    setup.py entered
    $PATH=C:\Anaconda3\Library\bin;C:\Anaconda3\Library\bin;C:\Program Files\ConEmu\ConEmu\Scripts;C:\Program Files\ConEmu;C:\Program Files\ConEmu\ConEmu;C:\ProgramData\Oracle\Java\javapath;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Program Files\TortoiseHg\;C:\Program Files (x86)\Skype\Phone\;C:\Program Files\Calibre2\;C:\Program Files\jEdit;C:\Program Files (x86)\Pandoc\;C:\Program Files\Git\cmd;C:\Program Files (x86)\PuTTY\;C:\Program Files\nodejs\;C:\Anaconda3;C:\Anaconda3\Scripts;C:\Anaconda3\Library\bin;C:\Users\darksnake\AppData\Local\atom\bin;C:\Users\darksnake\AppData\Local\Microsoft\WindowsApps;C:\Users\darksnake\.posh_gvm\gradle\current\bin;C:\Users\darksnake\AppData\Roaming\npm
    running egg_info
    running jsdeps
    3.10.10
    3.10.10
    Installing build dependencies with npm.  This may take a while...
    C:\Anaconda3\lib\site-packages\setuptools-27.2.0-py3.6.egg\setuptools\dist.py:331: UserWarning: Normalizing '0.1.0.dev' to '0.1.0.dev0'
    rebuilding js and css failed
    missing files: ['D:\\beakerx\\beakerx\\beakerx\\static\\extension.js', 'D:\\beakerx\\beakerx\\beakerx\\static\\index.js']
    error: [WinError 2] The system cannot find the file specified

    ----------------------------------------
Command "python setup.py egg_info" failed with error code 1 in D:\beakerx\beakerx\
:linkBeakerNbextension FAILED

FAILURE: Build failed with an exception.

Still not working:
npm ERR! Windows_NT 10.0.15063
npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "i"
npm ERR! node v4.4.4
npm ERR! npm  v2.15.1
npm ERR! code EPEERINVALID

npm ERR! peerinvalid The package<EMAIL_ADDRESS>does not satisfy its siblings' peerDependencies requirements!
npm ERR! peerinvalid Peer<EMAIL_ADDRESS>wants<EMAIL_ADDRESS>npm ERR! peerinvalid Peer<EMAIL_ADDRESS>wants<EMAIL_ADDRESS>npm ERR! peerinvalid Peer<EMAIL_ADDRESS>wants<EMAIL_ADDRESS>
npm ERR! Please include the following file with any support request:
npm ERR!     D:\Work\beakerx\beakerx\js\npm-debug.log
:beakerx:install FAILED

thanks for the report -- this is quite baffling, can anyone reproduce?
did you try a fresh clone?

Not working even with clean clone (which takes a quite a lot of time to download and build due to #5074  and npm calls).
By the way, the problem with check_call is still not solved. Without a fix, the build process barely starts. I can try to create a pull request, but it is easier to just fix lines 81 and 101 in beakerx/setup.py

setup.py comes from https://github.com/jupyter-widgets/widget-cookiecutter/blob/master/{{cookiecutter.github_project_name}}/setup.py
if it's wrong we should send a fix upstream.  would like to understand why/when it's needed though.
the cmd does not need any shell expansion or parsing.

I don't know, I am not using Python (I don't like it very much in fact). Just found the solution in the internet: here for example.

Another solution is to use either subprocess.check_call(['cmd','/c','npm', '--version']) or subprocess.check_call(['powershell','-command','npm', '--version'])

@altavir Have you resolved this issue? I believe that including the shell=True argument is the correct way to deal with Windows compatibility.
@scottdraves There is a relatively new package to abstract away Python packaging and enforce best practices: https://github.com/jupyter/jupyter-packaging

for the record the explanation from SO is:
On Windows, I believe the subprocess module doesn't look in the PATH unless you pass shell=True. However, shell=True can be a security risk if you're passing arguments that may come from outside your program. To make subprocess nonetheless able to find the correct executable, you can use shutil.which. Suppose the executable in your PATH is named frob:
subprocess.call([shutil.which('frob'), arg1, arg2])

(This works on Python 3.3 and above.)

thanks Grant we will have to look at that.  i don't have the bandwidth right now though.

I'm happy to do the refactoring to needed to adopt it :+1:

ty altavir i am thinking your soln is best.

Even with this problem fixed, there is still an error later in the npm. I am not sure it is windows specific, but it prevents beakerx from completing installation.

we are going to take this stuff out of gradle soon anyway, so just the quick fix for now.

It is not working even with the fix, so I will be waiting for reliable installer.

that fix actually breaks it on unix.  it either has to be conditional on windows or something different.
also, that is not the only place where call_check is used on npm.

While I tried to clone and install all project from zero (clean install).
I get errors.
I fix it that way:
My fix (commied PR created):
in file:
\beakerx\beakerx\build.gradle
I put this command first:
project('js').tasks.install.execute()
Was:
task install() {
  doLast {
    exec {
      commandLine(*(winOrUnix('pip', "install", "-e", ".")))
    }
    exec {
      commandLine(*(winOrUnix("jupyter", "nbextension", "install", "--py", "--symlink", "--sys-prefix", "beakerx")))
    }
    exec {
      commandLine(*(winOrUnix("jupyter", "nbextension", "enable", "--py", "--sys-prefix", "beakerx")))
    }
   project('js').tasks.install.execute()
  }
}

After fix:
task install() {
  doLast {
    project('js').tasks.install.execute()
    exec {
      commandLine(*(winOrUnix('pip', "install", "-e", ".")))
    }
    exec {
      commandLine(*(winOrUnix("jupyter", "nbextension", "install", "--py", "--symlink", "--sys-prefix", "beakerx")))
    }
    exec {
      commandLine(*(winOrUnix("jupyter", "nbextension", "enable", "--py", "--sys-prefix", "beakerx")))
    }
  }
}

Full step to install:
After I create fix I did "clean install" to try is there any errors.
Do not get any errors.
How I install "beakerx":
git clone https://github.com/twosigma/beakerx.git
conda create -y -n beakerx python=3.5 jupyter pandas
activate beakerx
gradlew --no-daemon build
gradlew --no-daemon kernelInstall
gradlew --no-daemon :beakerx:install

Do not get any errors while this commands !
afrer that just :
jupyter notebook
To start pplication.

this has been merged to master.  altavir, does it work for you?

No, still get:
npm ERR! node v4.4.4
npm ERR! npm  v2.15.1
npm ERR! code EPEERINVALID

npm ERR! peerinvalid The package<EMAIL_ADDRESS>does not satisfy its siblings' peerDependencies requirements!
npm ERR! peerinvalid Peer<EMAIL_ADDRESS>wants<EMAIL_ADDRESS>npm ERR! peerinvalid Peer<EMAIL_ADDRESS>wants<EMAIL_ADDRESS>npm ERR! peerinvalid Peer<EMAIL_ADDRESS>wants<EMAIL_ADDRESS>
I don't have time for clean install now. Will do it later.
By the way, project('js').tasks.install.execute() must be replaced by dependsOn: ":beakerx:js:install" in task declaration.
Also I do not understand the meaning of --no-daemon flags in commands. It changes nothing, just makes build process slower

the daemon can cause a problem if it's started with a different conda environment.
testing the build process requires a fresh clone, please LMK the results of this test.
thx.

Nope. Still not working even with clean install. The same error. Please fix #5074. Redownloading the repository takes a lot of time.

sorry to hear that.
you might want to try again after https://github.com/twosigma/beakerx/issues/5060

OK, it finally finishes installation, though there are still nasty warnings:
:beakerx:install
yarn install v0.24.5
[1/4] Resolving packages...
[2/4] Fetching packages...
warning<EMAIL_ADDRESS>The platform "win32" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
[3/4] Linking dependencies...
warning<EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>warning<EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>[4/4] Building fresh packages...

Examples still are not working, but at least it recognizes beaker classes. Maybe clean install will help.

thanks for the update.

I've got everything installed and running, but jupyter still does not display any beaker output (shows [*] and does nothing).
Maybe the problem is in this yarn warning:
[2/4] Fetching packages...
warning<EMAIL_ADDRESS>The platform "win32" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.

I had to completely reinstalled the system due to hard disk failure. I reinstalled everything and finally it works!
Still, it does not work on other two other computers I tried and installation requires a lot of time and additional software (like node.js, yarn and clang).
I am going to use beakerx for lectures and interactive examples this autumn, I hope that working distribution will be available before that. Otherwise my students won't manage to install it.
I will close the issue for now.  It could be reopened if someone have similar problem.

thx for circling back.  we should be on conda forge in about a month, including windows: https://github.com/twosigma/beakerx/issues/5134


Synchronize the spec and the implementation of global symbol format

Inspired by https://github.com/scalameta/scalameta/pull/1241. /cc @mberndt123

The versioning issue suggests that we may have a separate repository trying to get out.
I think that everything under semanticdb/ can go into https://github.com/scalameta/semanticdb to be versioned and published separately from https://github.com/scalameta/scalameta.
However, infrastructure setup will take lots of time, so since this is not on our critical path, let's just keep an eye on the situation and do nothing for the time being.

This pull request only updates the spec, so I'm going to merge it without waiting for Travis to finish.


Fixed ansible galaxy dependencies error

- executing: git clone https://github.com/FloeDesignTechnologies/ansible-haproxy ansible-haproxy
- executing: git archive --prefix=ansible-haproxy/ --output=/var/folders/40/1_7mkdwj20gdf3133bdhrwgm0000gn/T/tmpTp1ddK.tar HEAD
- extracting ansible-haproxy to /usr/local/etc/ansible/roles/ansible-haproxy
---
- ansible-haproxy was installed successfully
Traceback (most recent call last):
  File "/usr/local/Cellar/ansible/1.8.3/libexec/bin/ansible-galaxy", line 954, in <module>
    main()
  File "/usr/local/Cellar/ansible/1.8.3/libexec/bin/ansible-galaxy", line 948, in main
    fn(args, options, parser)
  File "/usr/local/Cellar/ansible/1.8.3/libexec/bin/ansible-galaxy", line 842, in execute_install
    role_dependencies = role_data['dependencies']
KeyError: 'dependencies'

Was getting the above when trying to install via ansible galaxy

Thank you!


Adding multiples physical and kindle book related to Flutter developm…

…ent.

Thank you for adding extra links @BLKKKBVSIK


Collection search not working as intended

Images should be self-explanatory. "Kö" gives the correct results, but "Kös" does not even though the name is "Köstekci".

Good catch - reproduced - we're going to deploy a fix to this shortly!


watchClientChanges and watchServerChanges now return an HttpServer obj

I'm using universal-hot-reload as part of a reusable build tool. I wanted to be able to:

listen to the client and the server's lifecycle events
show the client and the server's reported host and port
run some basic health checks on each load or reload

So I figured the easiest way to do this was to have universal-hot-reload return the server objects themselves, so I could reference the servers in my own build tool. I hope this functionality is useful to others and doesn't interfere with existing workflows or planned features.

Thanks @jsepia ! I'll take a look some time today.


You've Been Logged Out

Form
Put an [x] if you meet the condition, else leave [ ].
Requirements

[x] I've searched the Issues
[x] I've read the basic concepts
[x] I'm using the latest version
[x] I've debugged my code using the DEBUG variable.

Platform

[x] I'm using Node.js version v8.12.0
[ ] I'm using electron
[ ] I'm using the browser YOUR_BROWSER_AND_VERSION
[ ] I'm using some other environment YOUR_ENV

Description
I'm trying to login into my account from a script inside a VPS outside my country. Each time I try to login, a splash screen on the IG app shows up where I check "It was me".
I am given a challenge and receive an SMS. After I send the challenge code, I'm logged out again.
Here's my code: https://gist.github.com/redraw/37d077f6d71f320649923a58fa8c9ecb#file-run-js-L30
And here's what I get (with DEBUG=ig:*)
  ig:request Requesting POST /api/v1/challenge/***********/RIJTmgcZsr/ +588ms                                                                                [1626/1806]
[13.02.2020 01:29.24.804] [LOG]   checkpoint { message: 'challenge_required',
  challenge:
   { url: 'https://i.instagram.com/challenge/***********/RIJTmgcZsr/',
     api_path: '/challenge/***********/RIJTmgcZsr/',
     hide_webview_header: true,
     lock: true,
     logout: false,
     native_flow: true },
  status: 'fail',
  error_type: 'checkpoint_challenge_required' }
[13.02.2020 01:29.24.808] [LOG]   challenge { step_name: 'verify_code',
  step_data:
   { security_code: 'None',
     sms_resend_delay: 60,
     phone_number_preview: '1785',
     resend_delay: 60,
     contact_point: '1785',
     form_type: 'phone_number',
     phone_number_formatted: '+54 * *** ***-1785',
     phone_number: '+54 * *** ***-1785' },
  user_id: **********,
  nonce_code: 'RIJTmgcZsr',
  status: 'ok' }
? Challenge code 615738
  ig:request Requesting POST /api/v1/challenge/**********/RIJTmgcZsr/ +6m
[13.02.2020 01:35.46.167] [LOG]   { action: 'close', status: 'ok' }
[13.02.2020 01:35.46.169] [LOG]   challenge null
  ig:request Requesting undefined /api/v1/friendships/pending +2s
  ig:request Request GET [object Object] failed: {"message":"login_required","error_title":"You've Been Logged Out","error_body":"Please log back in.","logout_reason":2$
"status":"fail"} +151ms
[13.02.2020 01:35.46.339] [ERROR] IgLoginRequiredError: GET /api/v1/friendships/pending/?rank_token=481579f8-faaf-534a-ad59-718075570a87 - 403 Forbidden

If I send a wrong challenge code, I get an error like this,
  ig:request Requesting POST /api/v1/challenge/***********/ePjtVmnoSp/ +55s
  ig:request Request POST [object Object] failed: {"message":"Please check the code we sent you and try again.","status":"fail"}

Most of the time, after failing, I try again and I get this 502 error.
[13.02.2020 01:44.21.140] [ERROR] IgResponseError: POST /api/v1/accounts/login/ - 502 Bad Gateway;
    at Request.handleResponseError (/home/ubuntu/instaccept/node_modules/instagram-private-api/src/core/request.ts:171:12)
    at Request.send (/home/ubuntu/instaccept/node_modules/instagram-private-api/src/core/request.ts:82:24)
    at <anonymous>

Same here

You probably need to log in again after completing the challenge, else ➡ #1068


Update az cors add help doc

Fixes #5621

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR has modified HISTORY.rst describing any customer-facing, functional changes. Note that this does not include changes only to help content. (see Modifying change log).

[ ] I adhere to the Command Guidelines.

View a preview at https://prompt.ws/r/Azure/azure-cli/5848
This is an experimental preview for @microsoft users.


Build and Deploy a Java Application

Tutorial URL: https://developers.sap.com/tutorials/cp-java-reference-app-deploy.html
Please specify the step you are referring to Step 4: Bind the Application to a Database
Hello,
If I want to bind the Application to the Database i became the Error that
"Problems registering HANA database for account 's0007042004trial' and id 'espm'. Application with name 'espm' already exists."
I think the System will create a database not a shema?
Regards

Hello,
Can you try creating a database with a name other than the application name (espm) e.g. espmDatabase.
Regards,
Simona

Hi,
yes I made a new database but it has the same error...
Hm....

Hello,
Do you have any other applications deployed in your trial account with the same name as the name of your database?
If not could you please send a screenshot of the error that you are getting.
Thanks and Regards,
Simona

Thank you for your feedback. We haven't heard from you in a while, so we are closing the issue.
If you still have questions, feel free to reopen the issue.


ReplyButton's Action will not be called?

the code below will not work
replyBtn := tb.ReplyButton{
  Text: "🌕 Button #1",
  Action: func(*Callback) { // may not be called??
    fmt.Println("button clicked")
  },
}

b.Handle(&replyBtn, replyBtn.Action)

It may work if the codes
https://github.com/tucnak/telebot/blob/a67e593e355fd1e6cfcc864b48499bc0e9f1ce5c/options.go#L133

is replaced with
Action func(*Message) `json:"-"`

so we may not register like this:
b.Handle(&replyBtn, func(m *tb.Message) {
		// on reply button pressed
	})

I'm going to delete Action field . from reply and inline button types in v2.1. It's not used for anything in the package, instead it confuses people which are just started to use telebot.
So it's better for you to not use it :)

I'm going to delete Action field from reply and inline button types in v2.1. It's not used for anything in the package, instead it confuses people which are just started to use telebot.
So it's better for you to handle buttons in traditional way :)

I don't think it's a good idea to delete Action.
For some reasons, we need anonymous callback to bind to reply and inline button, especiallly to the button which be created dynamically.
Action field with the anonymous callback can make codes to be more pretty and short, isn't it?

func doAction(who string) {
 // TODO
}

// ............
menu := make([][]tb.InlineButton, 0)
// ...........
for _, name := range suggestNames {
    who := name
    tmpButton := tb.InlineButton{
        Unique: generateUUID(),
        Text:   name,
        Action: func(callback *tb.Callback) {
            doAction(who)
        },
    }
    menu = append(menu, []tb.InlineButton{tmpButton})
    b.Handle(&tmpButton, tmpButton.Action)
}

we love Action, make it better rather than drop it  foever :smile:

Isn't it the same?
func doAction(who string) {
 // TODO
}

menu := make([][]tb.InlineButton, 0)
for _, name := range suggestNames {
    who := name
    btn := tb.InlineButton{
        Unique: generateUUID(),
        Text:   name,
    }
    menu = append(menu, []tb.InlineButton{btn})
    b.Handle(&btn, func(callback *tb.Callback) {
        doAction(who)
    })
}

how about compatibility of the code used Action before?
how about the feature/improvement which may automatically register Action callback to bot handler?

how about compatibility of the code used Action before?

I agree with you about backwards compatibility. The problem of Action is that it actually useless. It seems it was left for some unimplemented feature.
Then ok, I'll fix ReplyButton's Action and leave it for v2.1 at least.

how about compatibility of the code used Action before?

I agree with you about backwards compatibility. The problem of Action is that it actually useless. It seems it was left for some unimplemented feature.
Then ok, I'll fix ReplyButton's Action and leave it for v2.1 at least.

It sounds good, thanks. Btw,  which version of Telegram Bot API is related to v2.1 , since the latest Bot API is 4.7 now! https://core.telegram.org/bots/api#january-23-2020

@guest6379 Bot API 4.7 will be implemented in v2.1, which is coming soon!

@guest6379 Bot API 4.7 will be implemented in v2.1, which is coming soon!

Greate, thank you so much for the amazing work


Create a parsable PR template

We should make a PR template and a parser to automate some of the manual labor and enforce contribution rules. The idea is that whenever someone makes a pull request, they add the changelog entries into the PR description. If we have a template, then we can write a GitHub action that scrapes these entries from the description and adds them to the changelog once the PR is merged.
Template

# Description
<!--
Describe what your PR does in this section. At least explain why this change
is necessary and briefly explain how your changes solve the problem.
-->

# Changelog
<!--
Write changelog entries here. The entries should be formated like this:
  - Added: <message>
  - Changed: <message>
  - Deprecated: <message>
  - Removed: <message>
  - Fixed: <message>
  - Security: <message>

These entries will get added to the changelog once the PR is merged.

For more guidelines, see: https://keepachangelog.com/en/1.0.0/
-->

 - Added: <!-- Description of the feature -->
 - Changed: <!-- Description of what changed -->
   <!-- etc. -->

Changelog generation
When somebody makes a pull request, they fill out the template, for example like this:

# Description
This PR adds foo and removes bar, because reasons. Bla bla bla.

# Changelog

 - Added: foo to baz
 - Removed: bar from baz

Now once the PR gets merged, a program takes the entries from the Changelog section and generates a new changelog based on this and the previous PRs.
# Changelog
All notable changes to this project will be documented in this file.

The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

## [Unreleased]
### Added
 - something interesting
 - foo to baz
### Removed
 - this and that
 - boring stuff
 - bar from baz

Semantic versioning
Another idea would be to make it possible to mark some changelog entries as breaking, for example with a bang:
# Changelog
 - Removed!: old broken code

Now we can use that information to decide, which version numbers to bump for the next release.
Existing solutions
There are some pre-made GitHub actions that are trying to do what I described here, but I haven't had any experience with them.

https://github.com/mikepenz/release-changelog-builder-action

Tasks

[ ] Create a PR template
[ ] Create a GitHub action that updates the changelog based on entries in pull request descriptions.

I've created a repo for parsing PR templates: https://github.com/Soupstraw/template-parser
There's still a lot of work to do to integrate that into CI. I think the best approach would be to create a GitHub bot that listens for PR events and then collects all the changelog entries. It would then commit the new changelog at a time where we usually don't work on the repo.

I think we should stick to the manual approach. It has proven to work great so far and I don't think we want this automation anyways, since our changelogs are package specific


Builds with embedded: true hang forever on Cloudflare Pages worker

Really strange because Cloudflare Pages purportedly uses Ubuntu 22.04 which should be a supported platform for sass-embedded

I can't help unless you point me to an issues with the code of the plugin.
Please figure out if and where this is an issue with the plugin
I suggest starting with making sure that outside of the plugin
sass-embedded works fine in Cloudflare


Some small markdown formatting

I actually prefer indented code blocks for readability as plaintext so users don't need to parse fencing. I'll apply the rest of these changes though.

How's this?

Excellent. :+1:


Clean up of px4_defines.h (remove math.h)

This patch reorders px4_defines.h to make it more readable (I think)
but more importantly, cleans up the #include <math.h>/<cmath>
and [std::]isfinite stuff.
My main goal was to completely get rid of including math.h/cmath,
because that doesn't really belong in a header that is supposed to
define macro's and is included in almost every source file (if not
all).
I'm not sure what it did before ;) (pun intended), but now it does
the following:
PX4_ISFINITE is only used in C++ code (that was already the case,
but hereby is official; for C code just use 'isfinite()') and is
defined to be std::isfinite, except on __PX4_QURT because that uses
the HEXAGON toolset which (erroneously) defines isfinite as macro.
I would have liked to remove PX4_ISFINITE completely from the code
and just use std::isfinite whereever that is needed, but that would
have required changing the libecl submodule, and at the moment I'm
getting tired of changing submodules... so maybe something for the
future.
Also, all includes of <math.h> or <cmath> have been removed except
for __PX4_NUTTX. Like the HEXAGON toolset NuttX currently defines
isfinite as macro for C++. So, we could have solved this in the
same was as __P4_QURT; but since we can fix NuttX ourselves I chose
to add a kludge to px4_defines.h instead that fixes this problem,
until the time that NuttX can be fixed (again postponing changing
a submodule). The kludge still demands including <cmath>, thus.
After removal of the math header files, it needed to be included
in source files that actually need it, of course.
Finally, I had a look at the math macro's (like M_PI, M_PI_F,
M_DEG_TO_RAD etc). These are sometimes (erroneously) defined in
certain math.h header files (like both, hexagon and nuttx).
This is incorrect: neither the C nor the C++ standard defines
math constants (neither as macro nor otherwise). The "problem"
here was that px4_defines.h defined some of the M_*_F float
constants in terms of the M_* double constant, which are
sometimes not defined either thus. So, I cleaned this up by
defining the M_*_F math constants as float literals in px4_defines.h,
except when they are defined in math.h for that platform.
This means that math.h (still) has to be always included when using those
constants (even though they don't according to the standard), but well;
not much difference there as those files usually also need/use the macro
NAN (which is a standard macro defined by math.h).
All in all I think the resulting px4_defines.h is nice, giving me
much less the feeling of a nearly unmaintainable and over time
slowly growing collection of kludges and hacks.

Removed a duplicated comment, and force pushed.

I noted that DEFAULT_PARAM_FILE that is set (only) for __PX4_QURT appears to be not used anywhere. Should it be removed from px4_defines.h, or should support for that macro be added?

Nice!

@bharath374 @mcharleb Can you comment on the default param file macro?

Other than that, looks good to merge.

I would say, just get rid of DEFAULT_PARAM_FILE, it's not used anywhere, instead this one is used: https://github.com/PX4/Firmware/blob/master/src/modules/systemlib/param/param_shmem.c#L799

@CarloWood Happy to merge if that is removed.

Ok, lets see... I currently have four branches, libcwd_support on top of cw_fix_headers on top of px4_defines_cleanup ontop of begin_end_decls_cleanup on top of master. So, now I need to checkout master, pull it, checkout px4_defines_cleanup, rebase it on top of master, fix it, force push it, checkout begin_end_decls_cleanup, rebase it on top of px4_defines_cleanup (not pushing it again, yet), checkout cw_fix_headers, rebase that on top of begin_end_decls_cleanup, checkout libcwd_support, rebase that on top of cw_fix_headers...
If we'd be just using git merge instead of rebasing... I'd just have to make a commit and merge it :p.

@LorenzMeier I removed DEFAULT_PARAM_FILE and rebased.

Thanks for the cleanup!


Q LORA or LORA implementation

Feature description
For finetuning existing text generation model, LORA and QLORA are popularly being used. Can we create pipelines for download models from Huggingface, then finetune the models using LORA or QLORA ?
Feature motivation
For text generation models, finetuning is preferred, rather than training from scratch. LORA or QLORA reduces the time required for finetuning by an order of magnitude.

CCing @laggui

The plan was to add those after Llama was added, but some plans changed since we introduced CubeCL 🙂
I think it's safe to say that there will be a positive update sometime in ~3 months regarding this 👀 Stay tuned.


refactor: fix mypy

Closes #12

mypy is now passing in lint https://github.com/ibis-project/ibis-bigquery/pull/16/checks?check_run_id=2326663057


Compatibility with EntityFrameworkWithHierarchyId

Pawel, how can this be compiled against the above dll in Visual Studio as per the link below:
https://github.com/sjh37/EntityFramework-Reverse-POCO-Code-First-Generator/wiki/HierarchyId
Installing the NuGet package and then building the project results in many errors e.g.
"The type 'EdmType' is defined in an assembly that is not referenced. You must add a reference to assembly 'EntityFramework, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=6847f3395fc61b47'.
I have checked the App.config file correctly lists this PublicKeyToken:

The XML code hasn't pasted through onto GitHub - here is the line from App.config without tags:
section name="entityFramework" type="System.Data.Entity.Internal.ConfigFile.EntityFrameworkSection, EntityFramework, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=6847f3395fc61b47" requirePermission="false"

I'd overlooked the fact that the errors were from the CodeFirstStoreFunctionTests project so will close this off. Always worth checking (!)

I guess the issue was that you removed a reference to the original EntityFramework NuGet package and added a reference to the EntityFrameworkHierarchyId only to the CodeFirstFunctions project but not the test project.


Schedule daily chargeback report generation for services

Schedule daily chargeback report generation for services
https://www.pivotaltracker.com/story/show/130683757
Related PR: #11202
Depends on #11570
@miq-bot add-label wip, core
\cc @gtanzillo

@miq-bot remove-label wip

👍 LGTM

@gtanzillo Please label euwe/yes or euwe/no

Euwe Backport details:
$ git log
commit 9b71672e587d0db79816d852ca58d145827b3936
Author: Gregg Tanzillo<EMAIL_ADDRESS>Date:   Mon Oct 3 10:27:25 2016 -0400

    Merge pull request #11571 from yrudman/shedule-daily-chargeback-report-generation-for-services

    Schedule daily chargeback report generation for services
    (cherry picked from commit d2cb5172daa1dd0661972f24a609101c10c9af1e)


Custom parent container for pushpin

Added ability to specify the parent container for the pushpin plugin (window by default)

I tested this and the parent option didn't seem to work, maybe you have a example of this you've created where it works?

I wish this behavior too, I was trying to use pushpin, but can't make work, I've made this naive implementation in my code:
let scrollingTreshold = this.$('.element-to-pin').position().top;
  this.$('.scrollable-container').on('scroll', (e) => {
    if(e.target.scrollTop >= scrollingTreshold) {
      this.$('.element-to-pinr').addClass('pinned');
    } else {
      this.$('.element-to-pin').removeClass('pinned');
    }
});

Of course, the scrollable-container should have the overflow-yproperty set to auto (or scroll) I guess.
I think it would be great if pushpin could support that 😄


Support for bfloat16

Description
Are there plans to support the bfloat16 data type in the near future? This data type is becoming increasingly popular in LLM training. It looks like currently it's not supported. I.e., calling y = cp.asarray(x), where x is a torch tensor of type torch.bfloat16, returns "TypeError: Got unsupported ScalarType BFloat16". Are there any recommended workarounds in the meantime?
Additional Information
No response

Curious where/how would you use bf16 if CuPy were to support it? Any pointer or reference? Thanks! 🙂

It would be good if numpy data type extensions á la https://github.com/jax-ml/ml_dtypes/tree/main were supported, which includes bfloat16, fp8 etc.

Seconding this! bfloat16 and fp8 support are important for my use case. I'd love to see these.

Any progress on this? We really need it for LLM training and inference.

bfloat16 support is sorely missed in cupy. Would really appreciate it getting fixed!
We are currently forced to work around it like this (thankfully we have torch.view):
x = torch.arange(10, dtype=torch.bfloat16, device="cuda")
print(x)
# tensor([0., 1., 2., 3., 4., 5., 6., 7., 8., 9.], device='cuda:0',
#        dtype=torch.bfloat16)

# view as uint8
y = x.view(dtype=torch.uint8)

array_size_in_bytes = y.nelement()*y.element_size()
mem = cupy.cuda.UnownedMemory(y.data_ptr(), array_size_in_bytes, owner=None)
memptr = cupy.cuda.MemoryPointer(mem, offset=0)
arr = cupy.ndarray(y.size(), dtype=cupy.uint8, memptr=memptr)
out = torch.as_tensor(arr, device=x.device, dtype=torch.uint8)
print(out)
# tensor([  0,   0, 128,  63,   0,  64,  64,  64, 128,  64, 160,  64, 192,  64,
#         224,  64,   0,  65,  16,  65], device='cuda:0', dtype=torch.uint8)

# view as bfloat16 again
out = out.view(x.dtype)
print(out)
# tensor([0., 1., 2., 3., 4., 5., 6., 7., 8., 9.], device='cuda:0',
#        dtype=torch.bfloat16)

I see (in https://github.com/cupy/cupy/issues/8269) that the bfloat16 feature is planned for v14 release. @asi1024 , is there a WIP branch that others can play with or help if needed?

Would also love this!

We are using a spiking neural network training library that actually implements custom CuPy functions for forward and backward propagation. The fact that CuPy lacks bfloat16 support is real pain for us. I would highly appreciate any progress on this issue.


Add support for query string

We should have the support to pass a custom (non-documented) query string for every API.

@sirius17 to enable debug mode in dev center, add _debug=true in the query string of the page. By doing so, all harness view will have a parameter debug.


Feature/show issues and pr count

This feature is based on this ticket #2718

Merging; we can address the two comments later if we want to. They are no blocker for this awesomeness!


How to use several injected providers at the same time?

I have metamask and coinbase extensions installed on chrome.
If both extensions are activated, the modal displays only the metamask option, but clicking on it triggers both extensions

Facing same issue. Any solution till now?

+1

With stable version 2.0.0 of Web3Modal now released, we are officially dropping support for version 1.x
Due to this this issue/pr was marked for closing. It is highly recommended to upgrade as 2.x will be receiving further updates that will enable functionality for some of our newer sdks like auth and push as well as support for WalletConnect v2 (See this post about WalletConnect v1 being deprecated https://medium.com/walletconnect/walletconnect-v1-0-sunset-notice-and-migration-schedule-8af9d3720d2e)
If you need to continue using Web3Modal 1.x and require this feature/fix implemented, we suggest adding it via forking V1 branch.


Reduce the z-index value

I think using 9999 for z-index is a bad choice, 99 is enough.
This will help when using with other UI libraries, such as the bootstrap.

@RodolfoSilva 👍


Try to make CPLEX fail gracefully on SIGINT

Want to try this out @sbebo? Seems to work for me.

ref #45

Looks good.. but I still see segfaults. They are somewhat less frequent in the REPL. Outside of the REPL I get a segfault nearly (but not quite) all the time.
Might be an issue with my version of Julia. I'm testing with:
Julia Version 0.3.10
Commit c8ceeef* (2015-06-24 13:54 UTC)
Platform Info:
System: Darwin (x86_64-apple-darwin14.3.0)

By the way, it might be worth discussing whether one would like ctrl+c to actually kill the whole thing  or just terminate the optimization (the exit_on_sigint=0 hack should do that -- in theory) when running a Julia script from the command line (as in julia test.jl).
For sure is what you want in the REPL; not 100% sure you want that outside of the REPL, but not a big deal anyway.

Hmm yeah, I'm also seeing the old behavior on v0.3. I've also reproduced a segfault twice in about 15 runs on v0.4.

To add to the mix, I'm now sometimes getting
...
    539   492    95870.8967     0    96735.0536     8281.5550    17830   91.44%
   1172  1026    28317.6552    58    96735.0536     9456.3217    44564   90.22%
   1827  1567    15980.2780    91    96735.0536     9985.4947    70648   89.68%
^C
signal (10): Bus error: 10
CPXEgeneric_unlock at /Users/huchette/Applications/ILOG/CPLEX_Studio126/cplex/bin/x86-64_osx/cplex (unknown line)
CPXLstoreNEThandle at /Users/huchette/Applications/ILOG/CPLEX_Studio126/cplex/bin/x86-64_osx/cplex (unknown line)
CPXEgeneric_unlock at /Users/huchette/Applications/ILOG/CPLEX_Studio126/cplex/bin/x86-64_osx/cplex (unknown line)
CPXEgeneric_unlock at /Users/huchette/Applications/ILOG/CPLEX_Studio126/cplex/bin/x86-64_osx/cplex (unknown line)
_pthread_body at /usr/lib/system/libsystem_pthread.dylib (unknown line)
_pthread_body at /usr/lib/system/libsystem_pthread.dylib (unknown line)
[1]    7521 bus error  /Applications/Julia-0.3.8.app/Contents/Resources/julia/bin/julia

I think I've seen that too.
On Aug 4, 2015 10:29 PM, "Joey Huchette"<EMAIL_ADDRESS>wrote:

To add to the mix, I'm now sometimes getting
...
539   492    95870.8967     0    96735.0536     8281.5550    17830   91.44%
1172  1026    28317.6552    58    96735.0536     9456.3217    44564   90.22%
1827  1567    15980.2780    91    96735.0536     9985.4947    70648   89.68%
^C
signal (10): Bus error: 10
CPXEgeneric_unlock at /Users/huchette/Applications/ILOG/CPLEX_Studio126/cplex/bin/x86-64_osx/cplex (unknown line)
CPXLstoreNEThandle at /Users/huchette/Applications/ILOG/CPLEX_Studio126/cplex/bin/x86-64_osx/cplex (unknown line)
CPXEgeneric_unlock at /Users/huchette/Applications/ILOG/CPLEX_Studio126/cplex/bin/x86-64_osx/cplex (unknown line)
CPXEgeneric_unlock at /Users/huchette/Applications/ILOG/CPLEX_Studio126/cplex/bin/x86-64_osx/cplex (unknown line)
_pthread_body at /usr/lib/system/libsystem_pthread.dylib (unknown line)
_pthread_body at /usr/lib/system/libsystem_pthread.dylib (unknown line)
[1]    7521 bus error  /Applications/Julia-0.3.8.app/Contents/Resources/julia/bin/julia
—
Reply to this email directly or view it on GitHub
https://github.com/JuliaOpt/CPLEX.jl/pull/46#issuecomment-127750224.


storagepool api: GET device list/details for a storage pool that doesn't exist returns 500 instead of 404

Do
GET /nodes/{nodeid}/storagepools/{storagepoolname}/devices
or
GET /nodes/{nodeid}/storagepools/{storagepoolname}/devices/{deviceuuid}
for a storagepoolname that doesn't exist and it will return a 500 instead of 404

Software versions
grid : abcf275
jumpscale_core8 : 9e43171


State

Ok. Thanks for this. I have the MSS310.  Can it be polled for current power usage info?

Sorry. This is currently not planned. Feel free to contribute to this project.

Honestly, any previous coding I've done with this stuff has all been copy/paste exercises and minimum edits.
Please help!
This is, I believe what I want to poll.

These were taken at the same time for ease.

@dehsgr Like this? You can see the debug.

@Mgblugs no, as described in my message before 3 days. You should send a JSON Object Payload. 🤓

@Mgblugs okay, I found sth. wrong. Please try to replace smartcontrol.js again and give feedback.

Success!

Now I need to figure out the equations!
Thanks a lot!

@Mgblugs sorry. I had to re-commit bugfix. :-(

What does that mean?

@Mgblugs I committed files in a bad structure. It is repository-specific. Thanks for your feedback. I‘ll publish new version to NPM later this day…

Published new version to NPM.

Don't mean to be a pest but do you have to do something to deploy this update as a flow?
It still shows as 1.3.1

TIA

Should be updated now.

@dehsgr Thanks for this contribution, I was looking for how to get the power values for my meross plug.
You should reflect this option on the main page, or in the example flow.

@Mgblugs no, as described in my message before 3 days. You should send a JSON Object Payload. 🤓
{ "namespace": "Appliance.Control.Electricity" }

@Varguit this is already documented in the ReadMe?!


The previous download address has expired. Can update it?

Hi all, we have updated new stable model/feature links.


docs: preload page thumbnail if set

Note that it expects the normal non-2x image in the front matter and a 2x image must be present too.
Previews:

https://deploy-preview-39769--twbs-bootstrap.netlify.app/docs/5.3/getting-started/parcel/
https://deploy-preview-39769--twbs-bootstrap.netlify.app/docs/5.3/getting-started/vite/
https://deploy-preview-39769--twbs-bootstrap.netlify.app/docs/5.3/getting-started/webpack/

The real gain might not be noticeable in the previews, because Netlify doesn't cache aggressively the assets like Cloudflare does. But on production, the difference should be noticeable.
This along with #39768 should make these pages load significantly faster.

BTW we should probably resize these images because right now we have them in dimensions that we never reach.
Something like 1600x800 for 2x should suffice.


⚠ Bofrost.at has degraded performance

In 53914f1, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1413 ms

Resolved: Bofrost.at performance has improved in 6a78ab1 after 46 minutes.


Add the ability to crop videos or resize images. Also provide the ability to select the cropping angle for images.

Add the ability to crop videos or resize images. Also provide the ability to select the cropping angle for images.

Thanks for the suggestion!
While cropping videos, resizing images, and selecting specific cropping angles are useful features, Comet is focused on providing a simple, efficient media compression and conversion experience. The aim is to keep the app lightweight and easy to use without venturing into advanced media manipulation features like cropping or editing.
However, if you’re looking for more advanced media editing tools, there are other great applications available that specialize in these functions. If you're interested in contributing towards keeping Comet simple yet powerful for compression and conversion, feel free to submit a PR or suggest further ideas that align with our core vision.
Thanks for your feedback!


Centered spinner icon and signing in text for login page

Fixes #9083.
In my opinion, this issue was introduced with https://github.com/wagtail/wagtail/pull/8670.
After fix:

Thanks Paarth. I remember that other fix now - thanks for fixing this on top of that issue.

Cherry picked to 4.0/stable a8f234ae15e792ca62c4b934046e720178d6fd5e


Make less-relevant methods protected

This will reduce the amount of extraneous information in the API doc.

Done for now.


Fix a bug introduced when fixing shellcheck lint

Thanks to @StevenPuttemans for the bug report at https://github.com/NVIDIA/DIGITS/pull/1475#issuecomment-287744649. My bad!

Probably should have caught this when I fixed https://github.com/NVIDIA/DIGITS/pull/1478.

@StevenPuttemans I think that last commit should fix it all. Want to take a look for me?

Seems good to me now! :+1:


Link missing blog post to web archive (fixes #46 and #41)

Merging it into single doc that starts with examples would be useful.


feat: update english, casing, and messages

Issue
https://gravitee.atlassian.net/browse/APIM-6092
Description
This PR makes some changes to some of the English and casing and also moves around some of the elements of the UI.

📚  View the storybook of this branch here

https://github.com/user-attachments/assets/23cd2fcf-5dcf-4dd8-9124-7e63345c4d88


Extend component stable check

e.g com.day.cq.wcm.msm.api.RolloutManagerImpl has no config on the publish instance so the dependent OSGi component will be unsatisfied only on publish instances.
There should be a way to define PIDS ignored/failed_activation/unsatisfied_reference per run mode or instance name/pattern

per run mode will require gathering the global knowledge about instances before checking. I am not sure if this extension is needed as it will increase the complexity of the solution too much unnecessarily

fixed in 1.6.7


Configuration not working...

How do you non-globally configure settings?  This isn't working:
<div ng-scrollbars ng-scrollbars-config="scrollbarConfig"></div>

$scope.scrollbarConfig = { axis: 'x' };

Ah hmm, I'll take a closer look this weekend or when I get a chance, but does the following demo work for you? http://iominh.github.io/ng-scrollbars/demo1.html

Not sure how, but all of the sudden it started working.

Ah, gremlins perhaps. Thanks though!

Gnomes ;)

iominh, I am facing the same issue. config is not working for me.
and I have done everything by the book. are more people facing this problem?

Hi @silverrajat88! I replied in the other ticket https://github.com/iominh/ng-scrollbars/issues/26. Version 0.0.9 will be rolling out in the near future, which should hopefully fix this issue

@iominh Thanks for your help.

Sure thing! I just released 0.0.9, so if you bower update or npm install you should hopefully see the new version

sure thing i will check it out :)


ngsanitize error after migrating to angular 1.7.0

I'm submitting a ...

[X ] bug report
[ ] feature request
[ ] other

Current behavior:
my application is not loading after angular released 1.7.0 version. We are using angular-sanitize in my our application.  my application downloaded angular 1.7.0 version then correspondingly angular-sanitize is also downloaded with version 1.7.0(which is compatible with angular version 1.7.0).
angular.lowercase and angular.uppercase methods have been removed in 1.7.0 version However angular-sanitize with version 1.7.0 still has references to it and As a result my application is not loading with the below error
Error: [$injector:modulerr] Failed to instantiate module ngSanitize due to:
TypeError: lowercase is not a function
Expected / new behavior:
my application should load properly with angualr-sanitize version 1.7.0 and angular version 1.7.0. Could you make the necessary changes in angular-sanitize #1.7.0 version
Minimal reproduction of the problem with instructions:

AngularJS version: 1.7.0

Browser: all

Anything else:

Hi,
You're probably not using angular-sanitize 1.7, as it doesn't have references to angular.lowercase / angular.uppercase.
Could you verify you're using 1.7.0 ? If you are, please provide the exact stacktrace so we can debug what's going on. (or if possible, provide a reproduction using plunkr)
Thanks

Hello,
after the upgrade to angular 1.7.0, we faced the same issue when loading the application  :
Uncaught Error: [$injector:modulerr] Failed to instantiate module app due to:
Error: [$injector:modulerr] Failed to instantiate module ngSanitize due to:
TypeError: lowercase is not a function
    at toMap (http://localhost:5768/__hash__/app.min.js:46557:27)
    at new $SanitizeProvider (http://localhost:5768/__hash__/app.min.js:46533:18)
    at Object.instantiate (http://localhost:5768/__hash__/app.min.js:14923:14)
    at provider (http://localhost:5768/__hash__/app.min.js:14733:36)

if it could help, we are using angular-sanitize<EMAIL_ADDRESS>(found it in .\node_modules\angular-sanitize\package.json)

As documented, you should always use the same version of AngularJS (angular) and external modules (angular-animate, angular-sanitize, etc).

Hi frederikprijck,
Thanks for your response. I am using angular-sanitize 1.7 only . please  find the below screen shot  for the reference

There is one another user also faced the same issue I found on stack overflow
https://stackoverflow.com/questions/50213977/angularjs-ngsanitize-error

You must be either not using<EMAIL_ADDRESS>or not<EMAIL_ADDRESS>In 1.7.0, lowercase()~ is exposed as a private helper (angular.$$lowercase()) and angular-sanitize has been updated to use that.
If you still believe there is bug in AngularJS, please post a minimal reproduction (ideally a live demo using Plnkr, CodePen, etc).

Having the same symptoms. Just as Angular team suggested:  I had  been using not matching versions:

angular.js 1.7.2
angular-sanitize.js 1.6.9

My problem was incorrect constraint in the package.json (so @singireddy0598 maybe you should check your version constraints)
  "dependencies": {
    "angular": "1",  // this updated angular.js to 1.7.2
    "angular-animate": "1.6.10",
    "angular-route": "1.6.9",
    "angular-sanitize": "1.6.9",

I'm getting this with angular 1.7.8 & angular-sanitize 1.7.8

@bike2live - can you provide a reproduction of your problem, and place it in a new issue?

Error: [$injector:modulerr] Failed to instantiate module ngSanitize due to:
TypeError: lowercase is not a function
at arrayToMap (http://localhost:4444/Scripts/angular-sanitize.js:417:27)
at stringToMap (http://localhost:4444/Scripts/angular-sanitize.js:411:12)
at $SanitizeProvider (http://localhost:4444/Scripts/angular-sanitize.js:389:18)


Can't Validate Erase-Install

Github is blocked for our users and the script is trying to validate erase-install as well as trying to download IBM Notifier from github.
I deployed these through via Jamf Pro policy, and tried to by pass the validation with now luck. Keep getting error code:2
Would this script be able to be modified to allow for IBM notifier and Erase-install to be installed elsewhere instead of github?
a variable at the top to tell the script to look for the installs in github or to tell the script they are already installed?

Your referencing v3 of super which has no support for macOS Sonoma.
If you plan to use or upgrade to Sonoma then you need to be using v4 which leverages mist-cli.
In either case, yes there are variables in the script that allow you to change the location and expected version of the helper apps.


Feature request: Temperature observations

The temperature forecast is already there, it would be great to pair it with temperature observation data. It should be available from the FMI open data: https://en.ilmatieteenlaitos.fi/open-data-manual

Thanks. I actually looked at that FMI API earlier and noticed that it would take a bit of effort to read the data and decided so far against adding it. Currently all the APIs I'm using are REST + JSON and just so nice to read and consume. If you happen to find a good REST API for FMI I would love to put it to use 🙂
Sorry for the delay, I just noticed this ticket (looks like I don't get any email notifications about these).

This one seems like a reasonably straightforward API, query by GET parameters and you'll get results back in XML:
https://opendata.fmi.fi/wfs?service=WFS&version=2.0.0&request=getFeature&storedquery_id=fmi::observations::weather::hourly::multipointcoverage&place=Hämeenlinna
Of course the XML seems to be just a bloated encapsulation for the real data that's in gml:doubleOrNilReasonTupleList element as space separated numerals :smile:.
I'm looking into implementing FMIService for it myself, expect a PR when I have time to do it.

I'd be very happy to include such a PR 😛

I just learned about an API that responds with JSON. Even better.
https://www.ilmatieteenlaitos.fi/api/weather/observations?fmisid=101150&observations=true


vscode: add possibility to add command Line arguments

This can be used to run vscode under wayland when it is published
with electron 12. The arguments will be passt to electron and
further to chromium.
Based on https://nixos.org/manual/nixpkgs/stable/#ssec-gnome-hooks

Motivation for this change
Be able to use vscode nativly under wayland. Use the same behavior as chromium
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Sounds plausible, but I don't have a wayland to test it (and not planning on installing it right now). Can you parametrize and extend nixos/tests/vscodium.nix such that there are two tests, one with X and the other with wayland? And then test that the wayland vscodium test doesn't work in the VM without your change, and it does work with your change?

Heads up, possible (but improbable) conflict: https://github.com/NixOS/nixpkgs/pull/118292#issuecomment-812264089

Result of nixpkgs-review pr 118360 at 94fbe7cc run on x86_64-linux 1

3 packages built successfully:

vscode
vscode-with-extensions
vscodium

2 suggestions:

warning: build-tools-in-build-inputs
wrapGAppsHook is a build tool so it likely goes to nativeBuildInputs, not buildInputs.
Near pkgs/applications/editors/vscode/generic.nix:64:5:
   |
64 |     buildInputs = [ libsecret libXScrnSaver libxshmfence ]
   |     ^

warning: missing-phase-hooks
installPhase should probably contain runHook preInstall and runHook postInstall.
Near pkgs/applications/editors/vscode/generic.nix:74:5:
   |
74 |     installPhase =
   |     ^

Currently no released vscode / vscodium features wayland support. It will need electron 12. I've my own vscode (code-oss) build with electron 12 patches and wayland support. https://github.com/microsoft/vscode/pull/120034
The option is for passing any command line argument to vscode -> electron -> chromium. Wayland support is only my usecase for this.

There is no environment for wayland tests in nixos/tests. Chromium let the user also just add commandLineArgs

VS Code 1.56 is now shipped with Electron 12 and running code --enable-features=UseOzonePlatform --ozone-platform=wayland uses Wayland. It would be great to have this merged.

There is no environment for wayland tests in nixos/tests

What do you mean by that? I thought you can just enter arbitrary config for the virtual machines, so surely you can configure the test VM to run Wayland?
If you mean something like this:
    imports = [
      ./common/x11.nix
    ];

You could add a file ./common/wayland.nix with a minimalistic wayland config.

Wayland is only a protocol. There is no central server component like the X Server. Each Compositor like Gnomes Mutter, Kdes Kwin or sway implement the server side of the wayland protocol. Tests would be needed for each one.
Beside that, this PR adds the possibility to pass any command line arguments to VS Code -> Electron -> Chromium and is not Wayland specific. So I see no need for testing an specific overrode VS Code.
My personal intension behind this PR is to use the generic usable commandLineArgs attribute to pass the same arguments to the Chromium under VS Code I'm passing to my normal Chromium
/etc/nixos/configuration.nix: ```
[...]
chromium = (pkgs.chromium.override {
commandLineArgs =
"--enable-features=VaapiVideoDecoder,UseOzonePlatform " +
"--enable-accelerated-video-decode " +
"--ozone-platform=wayland " +
"--enable-gpu-rasterization " +
"--disable-sync-preferences " +
"--force-dark-mode " +
"--enable-native-notifications";
});
vscode = (pkgs.vscode.override {
commandLineArgs =
"--enable-features=VaapiVideoDecoder,UseOzonePlatform " +
"--enable-accelerated-video-decode " +
"--ozone-platform=wayland " +
"--enable-gpu-rasterization " +
"--force-dark-mode " +
"--enable-native-notifications";
});

As you like. I'm just recommending a way for you to ensure that noone in the future will break the feature you're introducing.

For testing, you just need to ensure that a wayland compositor (any wayland compositor, I suggest sway as it's easy to install and launch, just one option) is running and VSCode (or whatever you want to test) successfully launches with WAYLAND_DISPLAY set and DISPLAY unset.
Additionally, you CAN launch Sway inside of an X server - you'll need to manage some variables manually but it is possible, as Sway can be launched with an X11 backend instead of a DRM one.

I can have a look on a sway testing environment. But would do this outside from this PR

I don't think we should pollute the sway test with all sorts of random programs... Maybe we could make a template to test programs in cage instead?

Now done here: https://github.com/NixOS/nixpkgs/pull/123680

What's blocking merging this and #123680? I would love to see this in nixos-unstable.

@heijligen can you rebase this please? (and apply the suggestion if it works)


feat: implement skew protection

closes #10947
This implements Vercel Skew Protection. Tested manually

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

[ ] It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
[x] This message body should clearly illustrate what problems it solves.
[ ] Ideally, include a test that fails without this PR but passes with it.

Tests

[ ] Run the tests with pnpm test and lint the project with pnpm lint and pnpm check

Changesets

[x] If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running pnpm changeset and following the prompts. Changesets that add features should be minor and those that fix bugs should be patch. Please prefix changeset messages with feat:, fix:, or chore:.

Edits

[x] Please ensure that 'Allow edits from maintainers' is checked. PRs without this option may be closed.

Woohoo! Thank you for implementing this 🥳


merge from arlac77/template-github,arlac77/template-kronos-module

package.json

chore(package): add ^3.7.0 remove ^3.6.0 (devDependencies.ava)

:tada: This PR is included in version 8.3.22 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Error: No selenium server jar found at the specified location Check that the version number is up to date.

Error: No selenium server jar found at the specified location (/opt/ci/corporate/workspace/chcom-replatform-mobile-regression-QA/node_modules/protractor/selenium/selenium-server-standalone-2.51.0.jar). Check that the version number is up to date.
I am observing above issue all of a sudden in Jenkins. When I execute below command, observing different issues again
node_modules/protractor/bin/webdriver-manage update
[22:36:28] I/local - Starting selenium standalone server...
[22:36:28] I/launcher - Running 1 instances of WebDriver
[22:36:29] I/local - Selenium standalone server started at http://<IP_ADDRESS>:44726/wd/hub
/opt/ci/corporate/workspace/chcom-replatform-mobile-regression-QA/node_modules/selenium-webdriver/lib/error.js:27
super(opt_error);
^
WebDriverError: null
Everything was working as expected till last Friday. Observing this new issue from Saturday. Attached package.Json for reference
package.zip

There's a few details missing but I think this will help:
webdriver-manager v10.0.4 loads the selenium server jar file in the node_modules/webdriver-manager/selenium folder and does not use the node_modules/protractor/selenium folder by design. When launching a local instance, protractor v3.1.1 is looking for node_modules/protractor/selenium. If you are using webdriver-manager v10.0.4 to update, protractor does not know the new location of the folder. The next release of protractor will have these two items in sync.
Because protractor v3.1.1 already has webdriver-manager, prefer using node_modules/protractor/bin/webdriver-manager to update your binaries and start your server. In both the next release of protractor and v3.1.1, you should not need to include the dependency of webdriver-manager in your package.json.
If you wish to use both protractor v3.1.1 and webdriver-manager v10.0.4 node modules, this could potentially be your work around: You could specify in your configuration file where the binary files are with seleniumServerJar and chromeDriver per the referenceConf.js.

Had same error, I had to run  webdriver-manager update and it worked

My solution was to change the version of my jar file to the newest in ../e2e-tests/config/protractor.e2e.local.conf.js


Print The Pattern

What the program do ?
----   Prints The pattern
*

In what programming language it is written?
C++

This pull request do not contains files in specific folders. Please fix it and reopen


Update

Are you still working on this and when do you think it would be ready ?

Hi! Sorry for the delay, was on vacations! Yes, I'm planning a big update this weekend, hopefully it will be ready next week. Please, keep in touch and any comments are very welcome.

Golang library to handle ISO8683 mesages it should be ISO8583 not ISO8683 ... I would review after your update and then get back to you

You're absolutely right. Fixed now, thanks for reporting.


(Fix) String compatibility for python3:

(Fix)(Issue): https://github.com/jaredks/rumps/issues/57
Use top file global definition to ensure compatibility with python3 and python2.

Credits to:
    http://www.rfk.id.au/blog/entry/preparing-pyenchant-for-python-3/

Thanks for contributing! Ended up fixing in a slightly different way.


rafactor(cli): introducing vulnerability container command

New Vuln Evaluation List
The new lacework vulnerability evaluations list command lists images evaluated
by the Lacework container vulnerability assessments during the specified time range,
by default, this command displays the evaluations from the last 7 days, but it is possible
to specify a different time range.
$ lacework vulnerability evaluation list -p demo
                    REGISTRY                   |          REPOSITORY          |        TAGS        |       LAST RUN       |   STATUS    | CONTAINERS |    VULNERABILITIES     |                              IMAGE DIGEST
-----------------------------------------------+------------------------------+--------------------+----------------------+-------------+------------+------------------------+--------------------------------------------------------------------------
  index.docker.io                              | selacework/sample-nodejs-app | latest             | 2020-07-07T17:16:17Z | Success     |          0 | 7 Critical 124 Fixable | sha256:01f5882aae5ea55e0dc1b49330b0a83e6be386acd502e6c3ff4b031a227c0dac
  gcr.io                                       | customerdemo1/afiune-vul     | latest             | 2020-07-07T02:16:11Z | Unsupported |          0 |                        | sha256:77d9b938dadc2682a479c761a1353e02beac60c8fbeb377b17d1f5cbfefda26c
<PHONE_NUMBER>70.dkr.ecr.us-east-2.amazonaws.com | hipster-shop/loadgenerator   | v0.1.4-23-g05758f5 | 2020-07-06T23:21:53Z | Success     |          2 | 2 High 1 Fixable       | sha256:6f6c9c2ee2d3760194ccce2e0311b91d35149b417b8a3e594d9b9e7e4b272aff

This change also adds deprecations, a quick summary, with suppressed help output,
of the overall changes to the vulnerability commands:
Main Vulnerability Command:
$ lacework vulnerability -h

Available Commands:
  evaluation  review evaluations from assessed container images
  report      (deprecated) use 'evaluation show <sha256:hash>' instead
  scan        manage on-demand vulnerability scans

Vulnerability Evaluation Sub-Command:
$ lacework vulnerability evaluation -h

Available Commands:
  list        list all evaluations from a time range (default last 7 days)
  show        show results of a container image evaluation

Vulnerability Scan Sub-Command:
$ lacework vulnerability scan -h

Available Commands:
  run         request an on-demand vulnerability scan
  show        return results about an on-demand vulnerability scan

(DEPRECATED) Vulnerability Report Sub-Command:
$ lacework vulnerability report -h
(DEPRECATED) This command has been moved, use now the following command:

  $ lacework vulnerability evaluation show <sha256:hash>

Adds Deprecations https://github.com/lacework/go-sdk/issues/162
Closes https://github.com/lacework/go-sdk/issues/156
Signed-off-by: Salim Afiune Maya<EMAIL_ADDRESS>

Our team is working on integrating new features and functionalities to the Lacework CLI,
such new features will collide with this Pull Request and deprecations, therefore, we
are suggesting a few modifications to make:

Move all the container vulnerability commands into a sub-command named lacework vulnerability container
Underneath the container sub-command have the following commands:

$ lacework vulnerability container --help

Usage:
  lacework vulnerability container [command]

Available Commands:
  scan                request an on-demand vulnerability assessment
  scan-status         check the status of an on-demand vulnerability assessment
  list-assessments    list container image assessments from a time range
  show-assessments    show results of a container image assessment

Superseded by https://github.com/lacework/go-sdk/pull/191


any plans to update smugpy for the v2.0 SmugMug API?

Hi @chrishoffman. Thanks again for smugpy. I'm using it for smugline - a command line tool for SmugMug and it's really useful.
I know that SmugMug released their v2.0 API a while ago, and am wondering if you have any plans to update smugpy to support the latest version of their API?
Cheers
Yoav

The 2.0 API is still in beta but I will take a look

Thanks @chrishoffman. I imagine you also received a note from SmugMug about the beta launch around December last year? I was expecting things to move forward since then, but in a way it's good to know that it's not moving too fast.
In any case, I asked you just in case you already made some progress, or to find out if you have any plans in this direction.

I'm planning on working on 2.0 support for this library, happy to coordinate @chrishoffman if you are interested.

Got this email just now:

Dear SmugMug API Developer,

We want to update you on a couple of important changes that will be happening at SmugMug and what they will mean for you and your apps, plug-ins, and other SmugMug integrations.

As you may have heard, we are retiring our Old SmugMug platform on October 15. Almost all of our customers are already using New SmugMug and many of your apps already support them. If you find any problems in how your code interacts with New SmugMug, you should look at changing your app to use API v2, which was built specifically to support the New SmugMug platform. If you have any issues and/or want help getting started on the new API, please feel free to reach out to us.

Also, starting on October 15, all HTTP requests to SmugMug, including all versions of the SmugMug API, must be secured with SSL/TLS. In other words, you must make all requests with https URLs. If your application is not already using https URLs, you need to update it by October 15 in order to maintain SmugMug compatibility. We made these changes to foster the most secure environment for our customers and partners.

We will redirect insecure requests to secure URLs; however, if you are using OAuth, this may not help your application, because if your application follows redirects without recalculating the OAuth signature, the signature will be invalid when you make the secure request.

If you have any questions, please feel free to contact<EMAIL_ADDRESS>as always. Thanks for your support in making our shared customers' experiences as great and secure as possible.

Sincerely,

The SmugMug API Team

If I'm reading this correctly(?), even though the v2 API is still marked as Beta, they're retiring the old API (does it include v1.3?).

I got the same e-mail.  It doesn't look like they are retiring the old APIs but forcing connections over HTTPS.  This will probably not require any changes to the library, although I will look, since it already support https.  I created a new ticket to track this issue #14

FWIW, I've been starting an API class called "mug", so if smugpy isn't going to v2 I can clean it up and share as a starting point.

Thanks for clarifying @chrishoffman. It does sound rather vague, particularly for an email targeted at developers, I have to say. Not very clear to me what's the old platform and what's the new one and how it all fits with their API versioning etc.

I think they are just talking about their website designer platform which was opt-in for a very long time.  They added features like unlimited nesting, among other things, that did not translate well to their old API (well their current API).

Has anyone made any progress on python support for the v2 API? I'm about to start on an application myself, and don't want to reinvent the wheel if at all possible.
Thanks
Andy

I've made a start on a v2 API here:
https://github.com/adhawkins/smugmugv2py
Interested in any comments or suggestions, it's still in the early stages at the moment, with little documentation.
I have written a sync program using it though, source is here:
https://github.com/adhawkins/pysmugmugsync
Would appreciate any comments or suggestions in those repos.
Andy

@chrishoffman @adhawkins What's the status of this? Any chance getting v2 API changes merged into smugpy?

Hi,
My API is usable, at the GitHub link above. No plans to merge really.
Andy

@adhawkins Any particular reason to create a separate project for accessing the SmugMug API ? Rather than contribute to this one? (Having two libraries, for v1.3 and one for v2.0 could create fragmentation and confusion)... Or did I misunderstand your intentions?

Mainly because there was no progress on this issue for a long period before I started work on mine. There seems to have been little activity on this project as a whole for a number of years now...
Andy

That's a valid comment I suppose. @chrishoffman is this project dead?

@gingerlime Re: is this project dead?  I guess it is now.  I'm looking at the project by @adhawkins but I don't see any documentation and I'm not a Python programmer, so I don't know if it's a possible replacement for me.

Your comment is valid @e40. I keep meaning to packaging up my library such that it's more useful to others.
That said, I do have a working sync client that is using my library. It's here if you're interested.


Add ECDS interception and Wasm convertion into xds proxy.

ref: https://github.com/istio/istio/issues/29989

@bianpengyuan: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
31ad789d12862b1dcf9ea0a55d8e7de76262c608
link
/test release-notes_istio

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

@bianpengyuan: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
31ad789d12862b1dcf9ea0a55d8e7de76262c608
link
/test release-notes_istio

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

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
31ad789d12862b1dcf9ea0a55d8e7de76262c608
link
/test release-notes_istio

unit-tests_istio
31ad789d12862b1dcf9ea0a55d8e7de76262c608
link
/test unit-tests_istio

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

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
31ad789d12862b1dcf9ea0a55d8e7de76262c608
link
/test release-notes_istio

unit-tests_istio
31ad789d12862b1dcf9ea0a55d8e7de76262c608
link
/test unit-tests_istio

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

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
31ad789d12862b1dcf9ea0a55d8e7de76262c608
link
/test unit-tests_istio

release-notes_istio
6a406e4410e15f34d7552848227ab4b93571f61c
link
/test release-notes_istio

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

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
31ad789d12862b1dcf9ea0a55d8e7de76262c608
link
/test unit-tests_istio

release-notes_istio
6a406e4410e15f34d7552848227ab4b93571f61c
link
/test release-notes_istio

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

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
31ad789d12862b1dcf9ea0a55d8e7de76262c608
link
/test unit-tests_istio

release-notes_istio
06e062af157f2d85ac0ae7faf252a036cb284d0e
link
/test release-notes_istio

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

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
31ad789d12862b1dcf9ea0a55d8e7de76262c608
link
/test unit-tests_istio

release-notes_istio
06e062af157f2d85ac0ae7faf252a036cb284d0e
link
/test release-notes_istio

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

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
06e062af157f2d85ac0ae7faf252a036cb284d0e
link
/test release-notes_istio

unit-tests_istio
06e062af157f2d85ac0ae7faf252a036cb284d0e
link
/test unit-tests_istio

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

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
06e062af157f2d85ac0ae7faf252a036cb284d0e
link
/test release-notes_istio

unit-tests_istio
06e062af157f2d85ac0ae7faf252a036cb284d0e
link
/test unit-tests_istio

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

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
06e062af157f2d85ac0ae7faf252a036cb284d0e
link
/test unit-tests_istio

release-notes_istio
f2489fabfa930b7aa0a4d53bd1e52cd1745e888f
link
/test release-notes_istio

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

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
06e062af157f2d85ac0ae7faf252a036cb284d0e
link
/test unit-tests_istio

release-notes_istio
f2489fabfa930b7aa0a4d53bd1e52cd1745e888f
link
/test release-notes_istio

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

@bianpengyuan: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
e4c31e49213e8439aa97d93013ecf3f72a62a6da
link
/test release-notes_istio

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

@bianpengyuan: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
e4c31e49213e8439aa97d93013ecf3f72a62a6da
link
/test release-notes_istio

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

@bianpengyuan: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
851378df8d0ba80476880b12244977074e85800e
link
/test release-notes_istio

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

@bianpengyuan: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
851378df8d0ba80476880b12244977074e85800e
link
/test release-notes_istio

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

@kyessenov @ramaraochavali @hzxuzhonghu ptal, thanks!

@kyessenov @ramaraochavali @hzxuzhonghu ptal, thanks!

@bianpengyuan: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

gencheck_istio
aa0c63a7858b703571888d0804c0f29a539884f7
link
/test gencheck_istio

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

@bianpengyuan: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

gencheck_istio
aa0c63a7858b703571888d0804c0f29a539884f7
link
/test gencheck_istio

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

@bianpengyuan: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

gencheck_istio
f006c85b2ede2d8a9e1d100d8250826b83532d06
link
/test gencheck_istio

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

@bianpengyuan: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

gencheck_istio
f006c85b2ede2d8a9e1d100d8250826b83532d06
link
/test gencheck_istio

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

Sorry, i missed the notification

Sorry, i missed the notification

Just one concern if one wasm not updated for 24 hours, it will be removed.

@hzxuzhonghu It is fine, because Wasm VM only needs the Wasm module file when it starts up, and it won't reload once starts up. VM's lifecycle is tied to the extension config (i.e It will live as long as there is an existing extension config). Any new VM start up will need an ECDS update, which will refresh the cache entry.

Just one concern if one wasm not updated for 24 hours, it will be removed.

@hzxuzhonghu It is fine, because Wasm VM only needs the Wasm module file when it starts up, and it won't reload once starts up. VM's lifecycle is tied to the extension config (i.e It will live as long as there is an existing extension config). Any new VM start up will need an ECDS update, which will refresh the cache entry.

In response to a cherrypick label: #30086 failed to apply on top of branch "release-1.9":
Applying: Add ECDS interception and Wasm convertion into xds proxy.
Using index info to reconstruct a base tree...
M	pkg/wasm/cache.go
Falling back to patching base and 3-way merge...
Auto-merging pkg/wasm/cache.go
CONFLICT (content): Merge conflict in pkg/wasm/cache.go
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Add ECDS interception and Wasm convertion into xds proxy.
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to a cherrypick label: #30086 failed to apply on top of branch "release-1.9":
Applying: Add ECDS interception and Wasm convertion into xds proxy.
Using index info to reconstruct a base tree...
M	pkg/wasm/cache.go
Falling back to patching base and 3-way merge...
Auto-merging pkg/wasm/cache.go
CONFLICT (content): Merge conflict in pkg/wasm/cache.go
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Add ECDS interception and Wasm convertion into xds proxy.
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to a cherrypick label: new issue created for failed cherrypick: #30235

In response to a cherrypick label: new issue created for failed cherrypick: #30235


26 P --Transcriber google group mail list sign-up process

Ensure new transcribers are invited to sign up to the mailing list/new google group as part of the process.
E0 U10 S7 C9: P26

To check and see if new transcribers can click on a link and request to be added to the new google group.

This has been complete for some time - closing.


Fix required

closes https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/issues/3405

@JoanneHendrickson

@JoanneHendrickson PR has been copyedited and is ready for final review, could you please check and merge? Thanks!

@JoanneHendrickson


/en-US

Request type

[ ] Please close this issue, I accidentally submitted it without adding any details
[ ] New documentation
[x] Correction or update

Details

Under the Serving static files section, the final line "For more information, see Serving static files in Express." links to https://developer.mozilla.org/en-US/docs/Learn/Server-side/Express_Nodejs/Serving%20static%20files%20in%20Express but this page is not found. Cannot see a matching page across the MDN site.

https://developer.mozilla.org/en-US/docs/Learn/Server-side/Express_Nodejs/Introduction

@scooby359 thanks for reporting this! I think this was a placeholder that never got finished ;-)
I've replaced it with a link that works now.


Add documentation for new bloom filter settings

Description
Add documentation for new bloom filter settings
Issues Resolved
Closes https://github.com/opensearch-project/documentation-website/issues/6434
Checklist

[x] By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license and subject to the Developers Certificate of Origin.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Thanks for reviewing this PR so quickly! @vagimeli

Thanks @vagimeli for the review. I've addressed the comments based on your suggestions.
Could you please check?

Thanks @vagimeli for the review. I've addressed the comments based on your suggestions. Could you please check?

@mgodwan It's in editorial review. I'll address any of the editor's feedback and merge the PR. If any tech questions come up, I'll reach out to you. Thank you!