UAA Route_registrar  is not running after update

Hi,
I have a problem with the route_registrar during a cf deployment. I will not start, but only for the UAA. All other registrar entries, i.e. Blobstore etc, are working.
I got the following error message.

Director task 154
Started preparing deployment > Preparing deployment. Done (00:00:00)
Started preparing package compilation > Finding packages to compile. Done (00:00:01)
Started updating job uaa > uaa/0 (3fd560a3-ae9a-4bf9-a1de-70e33dee8783) (canary). Failed: 'uaa/0 (3fd560a3-ae9a-4bf9-a1de-70e33dee8783)' is not running after update. Review logs for failed jobs: route_registrar (00:02:34)
Error 400007: 'uaa/0 (3fd560a3-ae9a-4bf9-a1de-70e33dee8783)' is not running after update. Review logs for failed jobs: route_registrar

The UAA part of manifest looks like:

name: uaa
instances: 1
vm_type: default
azs: [z1]
stemcell: ubuntu-trusty
templates:

{name: uaa, release: cf}
{name: metron_agent, release: cf}
{name: route_registrar, release: cf}
networks:
name: default
static_ips: [<IP_ADDRESS>]
properties:
login:
catalina_opts: -Xmx768m -XX:MaxPermSize=256m
route_registrar:
routes:

name: uaa
registration_interval: 20s
port: 8080
uris:

"uaa.<%= system_domain %>"
"*.uaa.<%= system_domain %>"
"login.<%= system_domain %>"
"*.login.<%= system_domain %>"
uaa:
admin:
client_secret: password
batch:
password: password
username: batch_user
cc:
client_secret: password
scim:
userids_enabled: true
users:
admin|<%= cf_admin_pwd %>|scim.write,scim.read,openid,cloud_controller.admin,doppler.firehose,routing.router_groups.read
uaadb:
address: <IP_ADDRESS>
databases:

{name: uaadb, tag: uaa}
db_scheme: postgresql
port: 5524
roles:
{name: uaaadmin, password: password, tag: admin}

/var/vcap/sys/log/route_registrar/route_registrar.stderr.log is empty.
Last entries in route_registrar.stdout.log are

{"timestamp":"1479736657.834472179","source":"Route Registrar","message":"Route Registrar.Registered routes successfully","log_level":1,"data":{}}
{"timestamp":"1479736677.834125042","source":"Route Registrar","message":"Route Registrar.no healthchecker found for route","log_level":1,"data":{"route":{"Name":"uaa","Port":8082,"Tags":null,"URIs":["uaa.de.cloudlab.com",".uaa.de.cloudlab.com","login.de.cloudlab.com",".login.de.cloudlab.com"],"RouteServiceUrl":"","RegistrationInterval":20000000000,"HealthCheck":null}}}
{"timestamp":"1479736677.834250212","source":"Route Registrar","message":"Route Registrar.Registering route","log_level":1,"data":{"route":{"Name":"uaa","Port":8082,"Tags":null,"URIs":["uaa.de.cloudlab.com",".uaa.de.cloudlab.com","login.de.cloudlab.com",".login.de.cloudlab.com"],"RouteServiceUrl":"","RegistrationInterval":20000000000,"HealthCheck":null}}}
{"timestamp":"1479736677.834356546","source":"Route Registrar","message":"Route Registrar.Registered routes successfully","log_level":1,"data":{}}

Why I get this timeout?

When you ssh onto the VM, does monit summary show the route_registrar as running? If so it might just be taking longer than you expect to start up and, and increasing your update_watch_time may help.

After redeploying a got the error everywhere

Failed updating job doppler > doppler/0 (b0d7ef00-f2ad-4b17-9634-528af3e9e51b) (canary): 'doppler/0 (b0d7ef00-f2ad-4b17-9634-528af3e9e51b)' is not running after update. Review logs for failed jobs: doppler (00:01:14)
Failed updating job loggregator_trafficcontroller > loggregator_trafficcontroller/0 (e532f1d7-bd62-4564-bb56-274076d00f63) (canary): 'loggregator_trafficcontroller/0 (e532f1d7-bd62-4564-bb56-274076d00f63)' is not running after update. Review logs for failed jobs: loggregator_trafficcontroller, metron_agent, route_registrar (00:01:15)
Failed updating job route_emitter > route_emitter/0 (0d8a9b0e-bb72-48c1-a0ef-d749a7935953) (canary): 'route_emitter/0 (0d8a9b0e-bb72-48c1-a0ef-d749a7935953)' is not running after update. Review logs for failed jobs: consul_agent, route_emitter, metron_agent (00:01:22)
Failed updating job router > router/0 (1ac5183f-2652-4409-9a7a-d4ebc641c323) (canary): 'router/0 (1ac5183f-2652-4409-9a7a-d4ebc641c323)' is not running after update. Review logs for failed jobs: gorouter, metron_agent, consul_agent (00:01:24)
Failed updating job brain > brain/0 (b768c8b4-10ae-48ec-a38b-62b819a81d5d) (canary): 'brain/0 (b768c8b4-10ae-48ec-a38b-62b819a81d5d)' is not running after update. Review logs for failed jobs: consul_agent, auctioneer, converger, metron_agent (00:01:24)
Failed updating job cc_bridge > cc_bridge/0 (aa452943-63a3-4777-86c1-f69db78b34f3) (canary): 'cc_bridge/0 (aa452943-63a3-4777-86c1-f69db78b34f3)' is not running after update. Review logs for failed jobs: consul_agent, stager, nsync_listener, nsync_bulker, tps_listener, tps_watcher, cc_uploader, metron_agent (00:01:28)
Failed updating job access > access/0 (f198a985-f981-45f4-8384-bd12f9bb8995) (canary): 'access/0 (f198a985-f981-45f4-8384-bd12f9bb8995)' is not running after update. Review logs for failed jobs: consul_agent, ssh_proxy, metron_agent, file_server (00:01:29)
Failed updating job api > api/0 (414b6459-253f-41f8-a227-641906b33988) (canary): Action Failed get_task: Task 331c4b02-3379-4fca-4828-34b14e6ee1bc result: 1 of 4 pre-start scripts failed. Failed Jobs: cloud_controller_ng. Successful Jobs: cloud_controller_worker, cloud_controller_clock, consul_agent. (00:01:56)
Failed updating job cell > cell/0 (ab5d973c-0959-4e0e-9132-5b03a30a6fe8) (canary): 'cell/0 (ab5d973c-0959-4e0e-9132-5b03a30a6fe8)' is not running after update. Review logs for failed jobs: consul_agent, rep, garden, metron_agent (00:02:19)
Failed updating job database > database/0 (75ebf467-81b7-413d-b5fc-942694402d2f) (canary): 'database/0 (75ebf467-81b7-413d-b5fc-942694402d2f)' is not running after update. Review logs for failed jobs: consul_agent, etcd, etcd_consistency_checker, bbs, metron_agent (00:02:35)
Failed updating job uaa > uaa/0 (fe92dab6-299c-4fe2-ab07-4cf0aa653b17) (canary): 'uaa/0 (fe92dab6-299c-4fe2-ab07-4cf0aa653b17)' is not running after update. Review logs for failed jobs: metron_agent, route_registrar (00:02:38)
Error 400007: 'doppler/0 (b0d7ef00-f2ad-4b17-9634-528af3e9e51b)' is not running after update. Review logs for failed jobs: doppler

Monit summary on uaa shows:

Process 'uaa'                       running
Process 'metron_agent'              running
Process 'route_registrar'           Execution failed
System 'system_localhost'           running

the log file route_registrar.stderr.log:

panic: nats: No servers available for connection
goroutine 1 [running]:
github.com/cloudfoundry-incubator/route-registrar/Godeps/_workspace/src/github.com/pivotal-golang/lager.(*logger).Fatal(0xc8200162a0, 0x7d9850, 0x12, 0x7fce1d89a028, 0xc820011280, 0x0, 0x0, 0x0)
/var/vcap/packages/route_registrar/src/github.com/cloudfoundry-incubator/route-registrar/Godeps/_workspace/src/github.com/pivotal-golang/lager/logger.go:152 +0x698
main.main()
/var/vcap/packages/route_registrar/src/github.com/cloudfoundry-incubator/route-registrar/main.go:85 +0x126f
goroutine 17 [syscall, locked to thread]:
runtime.goexit()
/usr/local/go/src/runtime/asm_amd64.s:1721 +0x1
goroutine 5 [syscall]:
os/signal.loop()
/usr/local/go/src/os/signal/signal_unix.go:22 +0x18
created by os/signal.init.1
/usr/local/go/src/os/signal/signal_unix.go:28 +0x37
goroutine 6 [select, locked to thread]:
runtime.gopark(0x836d90, 0xc820022728, 0x7a59e0, 0x6, 0x42d918, 0x2)
/usr/local/go/src/runtime/proc.go:185 +0x163
runtime.selectgoImpl(0xc820022728, 0x0, 0x18)
/usr/local/go/src/runtime/select.go:392 +0xa64
runtime.selectgo(0xc820022728)
/usr/local/go/src/runtime/select.go:212 +0x12
runtime.ensureSigM.func1()
/usr/local/go/src/runtime/signal1_unix.go:227 +0x353
runtime.goexit()
/usr/local/go/src/runtime/asm_amd64.s:1721 +0x1

@StBurcher seems like nats machines are not reachable/failing?

It getting confused. After removing the whole system and reinstalling it with CF-238 only UAA is not running.
Error:

Director task 315
Started preparing deployment > Preparing deployment. Done (00:00:01)
Started preparing package compilation > Finding packages to compile. Done (00:00:01)
Started updating job uaa > uaa/0 (cff050ec-dc6b-4560-9a61-3282f92a3f83) (canary). Failed: 'uaa/0 (cff050ec-dc6b-4560-9a61-3282f92a3f83)' is not running after update. Review logs for failed jobs: metron_agent (00:03:34)
Error 400007: 'uaa/0 (cff050ec-dc6b-4560-9a61-3282f92a3f83)' is not running after update. Review logs for failed jobs: metron_agent
Task 315 error
Are you sure you want to deploy? (type 'yes' to continue): yes
Director task 315
Started preparing deployment > Preparing deployment. Done (00:00:01)
Started preparing package compilation > Finding packages to compile. Done (00:00:01)
Started updating job uaa > uaa/0 (cff050ec-dc6b-4560-9a61-3282f92a3f83) (canary). Failed: 'uaa/0 (cff050ec-dc6b-4560-9a61-3282f92a3f83)' is not running after update. Review logs for failed jobs: metron_agent (00:03:34)
Error 400007: 'uaa/0 (cff050ec-dc6b-4560-9a61-3282f92a3f83)' is not running after update. Review logs for failed jobs: metron_agent
Task 315 error

But, bosh instances --ps shows.

| uaa/0 (cff050ec-dc6b-4560-9a61-3282f92a3f83)*                           | running | INDIA | medium  | <IP_ADDRESS>     |
|   uaa                                                                   | running |       |         |               |
|   metron_agent                                                          | running |       |         |               |
|   route_registrar                                                       | running |       |         |               |

Since metron_agent was listed as not running, but it was running when you ran bosh instances --ps, you might just need to increase the canary_watch_time/update_watch_time (http://bosh.io/docs/deployment-manifest.html#update). It might have just needed some additional time to start depending on your environment.

Hi,
thank you that worked. I have change the time.


Feature/bugfix unexpected form data crash

Fixes issue #4 : App crash : AttributeError: 'NoneType' object has no attribute 'select'
Update readme with macOS instructions.

Updated from feedback. Please review.

The main file logic is not correct because it should find the form in the first time if not then the data given is wrong not success
And for the README.md the tool is not working with python 2 believe me mechanicalsoup is not Python 2 compatible!

The exception handler in the code catches the runtime exception that occurs when the form has missing fields. This allows the script to fail gracefully and continue running if there is an error with one of the web sites. Without this exception handler, the script terminates if there is a runtime error. See the referenced issue for the runtime error that this addresses (#4).

If you check the GitHub repo for mechanicalsoup, you will see that it is compatible with python 2.7, which is the default python on macOS Sierra.

Okay I already updated the tool yesterday thank you


feat(appext): APPEX-461 Add reference example using App Extensions

What?
Adding in the ability to see an example of App Extensions with the already loaded products list on headerless route product/[productAppExtension]
Why?
Adding in requested changes requested from (https://github.com/bigcommerce/sample-app-nodejs/pull/145)
Testing / Proof
...
https://user-images.githubusercontent.com/109627308/210449769-2d48f7e9-c106-4645-9d0c-157cc48c4735.mov
@bigcommerce/api-client-developers

@bc-nekisham looking at the screenshot, it appears that the panel is rendering oddly - can we look into what's going on?

@bc-nekisham looking at the screenshot, it appears that the panel is rendering oddly - can we look into what's going on?
the description panel was flowing over the app ext panel and the two panels were flowing into each other themselves- I changed the margins on both

https://user-images.githubusercontent.com/109627308/210641266-97764c0e-e99f-4719-8959-d8b5685733da.mov

🍹 Not a big deal, but if you have a chance to modify the commit message to fix the typo and force push that up, that would be good.

Updated visible on storefront
https://user-images.githubusercontent.com/109627308/211098871-acbd4d9e-2f2e-4e35-b03e-f104737fb76c.mov


MacOS - Example apps don't update projection matrix when window resized

The projection matrix (or viewport?) is not updated when the window is resized as it is when running on Windows/Linux.

Could you please check gl/glutin samples to confirm an upstream issue?

Interesting results...
Anyway the examples are all very simple, just renders one triangle. When resizing the 'window' example on MacOS the triangle is scaled to fit the window at all times. On Windows10 the triangle remains a fixed size, at a fixed position relative to the bottom/left corner of the window. So it gets cropped if the window shrinks. It also flickers and bounces a bit while resizing.
This is the opposite of what I would have expected, but shows there are differences between platforms.

I can confirm that on MacOS, resizing three-rs windows generates flicker, unexpected updates to the viewport, and generally bad behavior (e.g., increasingly long lag times). I don't observe this behavior with the examples from the glutin project.

I apologize, but today I can't reproduce the behavior I reported yesterday with three-rs resizing. Today I only observe the projection matrix / viewport issue that spacejack originally reported. Specifically, when resizing the window in the vertical direction, it appears that the viewport becomes vertically off-center. I confirmed that this resizing issue does not appear in the glutin and gfx/pre-ll examples. I tested only on MacOS.

@kbarros thanks, I'll try to look into it.


BUG: accept np-coercible array-likes with array API flag set

Reference issue
Closes https://github.com/scipy/scipy/issues/19118.
What does this implement/fix?
compliance_scipy is modified to accept array-likes by coercing with np.asanyarray. Previously, they were rejected, which is unwanted for backwards compatibility reasons.
Additional information
This implementation may be suboptimal - I'm not confident that creating a new tuple and using try except is the right thing to do. But this seems to have the desired behaviour.
A follow-up may come in the future as @mdhaber has expressed a want to sometimes accept certain types of array like Masked arrays.

@mdhaber I've addressed your comments, I think this is correct?

Close, but you need to loop over the indices of the list if you want to modify it.
for i in range(len(arrays)):
    array = arrays[i]
    ...
    arrays[i] = ...  # to modify list element

and technically, you don't even need to return arrays (although it's probably not a bad idea to do so to be explicit that it's modified).
You could also try:
for i, array in enumerate(arrays):
    ...
    arrays[i] = ...  # to modify list element

Although a linter or mypy might not like it.

The rest of the changes LGTM but you might add a test that when objects are coerced to object arrays, the new error is emitted. Nit: to save a level of indentation, you could put the object dtype check after the try-except block rather than within the try.
Also @rgommers should character arrays continue to be let through?

Close, but you need to loop over the indices of the list if you want to modify it

My most recent commit has tried to address this.

add a test that when objects are coerced to object arrays, the new error is emitted.

Can you give me an example input that would be coerced to an object array?

Also @rgommers should character arrays continue to be let through?

Good question. I hadn't given that any thought before, because I can't remember a single bug report about them. However, I think there is value in defining more clearly what dtypes are accepted. I'd say it should be only boolean and numerical dtypes (signed/unsigned integer and real/complex floating-point dtypes). Would you agree with that?

Can you give me an example input that would be coerced to an object array?

Sure.
import numpy as np
from scipy import stats

x = np.asanyarray([object()])
x.dtype  # dtype('O')

y = np.asanyarray(stats)
y.dtype  # dtype('O')

Would you agree with that?

After mode stopped supporting non-numerical arrays, I can't think of functions that should support non-numerical types. So yes, I think we can restrict to subdtypes of np.number and np.bool.

thanks Matt, hopefully that's everything now.

Unless we want to include that in here too.

That would be nice. @rgommers are we going to be bothered by the overhead of np.issubdtype? It's probably the slowest thing in this function, and in the simplest implementation, it would be called separately for each array.
import numpy as np
x = np.asanyarray(['a'])
%timeit np.issubdtype(x.dtype, np.flexible)  # 646 ns ± 2.71 ns per loop (mean ± std. dev. of 7 runs, 1,000,000 loops each)

The overhead of ~650 ns is quite a bit, so we may have to optimize this later. But it's not a big worry for now - we can circle back to that once it start showing up in profiling results.


Fixes slow downloads by using yt-dlp from master

There was a bug in yt-dlp caused by a youtube change causing very slow downloads.
This installs yt-dlp from master (where it's already fixed) and configure youtube-dl-exec to use it.
Also necessary to upgrade dependencies.
Tested in my repos.
See: https://github.com/yt-dlp/yt-dlp/issues/6369

Apparently GitHub actions run in another platform, probably arm64.
Because I moved the npm install to build phase, and puppeteer installs
chromium on install, it would install a "wrong" platform.
So this is to force installing chromium. It would be possible to run the
internal puppeteer install script itself, but I suppose it's just cosmetics
and break encapsulation.
Em qua, 1 de mar de 2023 00:45, Abe Hanoka @.***>
escreveu:

@.**** approved this pull request.
In Dockerfile
https://github.com/Schrodinger-Hat/youtube-to-anchorfm/pull/78#discussion_r1121101004
:

@@ -3,7 +3,7 @@ FROM ubuntu:20.04
RUN apt-get update && apt-get install -y sudo
RUN apt-get -y upgrade
RUN apt-get install -y curl
-RUN curl -sL https://deb.nodesource.com/setup_14.x | sudo -E bash -
+RUN curl -sL https://deb.nodesource.com/setup_16.x | sudo -E bash -

I support this idea of upgrading
In entrypoint.sh
https://github.com/Schrodinger-Hat/youtube-to-anchorfm/pull/78#discussion_r1121101751
:

@@ -2,5 +2,6 @@

Guarantee that we are on the same path as our *.js scripts
cd /
-npm ci  # more suitable for installs from scratch
-npm start
+npm uninstall puppeteer
Can you explain why you do npm uninstall puppeteer and then npm install
puppeteer
Or is it a mistake?
—
Reply to this email directly, view it on GitHub
https://github.com/Schrodinger-Hat/youtube-to-anchorfm/pull/78#pullrequestreview-1318994154,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAMRQZAWAWFZFZNZIHB57ILWZ3A6LANCNFSM6AAAAAAVLJHLZQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

Sooo..... how does this work? What do I download and where?

Sooo..... how does this work? What do I download and where?

@tempname42069 check the README

https://github.com/Schrodinger-Hat/youtube-to-anchorfm#readme you mean this? Sorry I'm a tech noob, what does this have to do with yt-dlp?

https://github.com/Schrodinger-Hat/youtube-to-anchorfm#readme you mean this? Sorry I'm a tech noob, what does this have to do with yt-dlp?

@tempname42069 this has nothing to do with yt-dlp. To install the newest version of yt-dlp on your computer, check https://github.com/yt-dlp/yt-dlp/wiki/Installation#with-pip

Hello,
I do not understand what I should do on my linux system to fix this issue.
Is there any official update soon?
Regards

Thanks for updating us on the yt-dl issue. I see he will soon do a release, do you think it will be worth it to update to master?
We should then choose the next latest release, just to keep that in mind
Beside that, I think it's good to update some deps.

This has been fixed upstream and as youtube-dl-exec always download the latest version, is already fixed here too. So, feel free to close this PR without merging.

This has been fixed upstream and as youtube-dl-exec always download the latest version, is already fixed here too. So, feel free to close this PR without merging.

I am  closing this issue, I'll update the dependencies as @TheJoin95 suggested.


Remove latex build in ReadTheDocs

Latex build is currently failing in active versions so its generation will be removed for now. See below the links to failing and passing documentation builds:

Latest version (fail): https://beta.readthedocs.org/projects/vulcanexus/builds/24019332/
Current branch version (success): https://beta.readthedocs.org/projects/vulcanexus/builds/24019820/

@mergifyio backport humble


Add bg translation

Added bulgarian translation and help.
I've not moved bg to fully translated as this is maintainer decission.

It looks perfect!
Thank you very much for the translation.
I listed your name/account on /:translation if you do not mind (if it is not, please give me a sign, I will remove it).
Could you please translate bg.txt also? Currently we use translation provided by the datasource, by (1) they are sometimes inaccurate (for some languages; maybe, they are ok for Bulgarian, I do not know);
(2) if we would use some other datasource, it is not guaranteed that it supports Bulgarian too; that is why it is better to have our own translation.

(2) will work on it :)
On Thu, Jun 20, 2019, 18:27 Igor Chubin<EMAIL_ADDRESS>wrote:

[image: _lang=bg]
https://user-images.githubusercontent.com/3875145/59860971-35d8ac00-9380-11e9-9aa0-8c853a96af7c.png
It looks perfect!
Thank you very much for the translation.
I listed your name/account on /:translation if you do not mind (if it is
not, please give me a sign, I will remove it).
Could you please translate bg.txt also? Currently we use translation
provided by the datasource, by (1) they are sometimes inaccurate (for some
languages; maybe, they are ok for Bulgarian, I do not know);
(2) if we would use some other datasource, it is not guaranteed that it
supports Bulgarian too; that is why it is better to have our own
translation.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/chubin/wttr.in/pull/316?email_source=notifications&email_token=ABGYWBY66TUK45DINV47SZLP3OOWFA5CNFSM4HY7UD7KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYFYIII#issuecomment-504071201,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABGYWB5JKUS4LAO66TJM5ILP3OOWFANCNFSM4HY7UD7A
.


0.11.1 ChangeLog fixes

Fixes to the changelog file for the release.

Integration tests have been run and passed, so release will go after this.


bower install failing

When I try a bower install of fetch, I get the following error message:
 Request to https://registry.bower.io/packages/fetch failed with ECONNRESET, retrying in 1.9s

I can install other packages without any problems.

We're not sure why is that, but this doesn't sound like something that we can solve, and is instead a problem with Bower itself. We recommend using npm to download whatwg-fetch over other package managers.


error in running.....react-native-todo

$ npm start

<EMAIL_ADDRESS>start C:\Users\monangi\Desktop\react-native-todo
react-native-scripts start

'react-native-scripts' is not recognized as an internal or external command,
operable program or batch file.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>start: react-native-scripts start
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm WARN Local package.json exists, but node_modules missing, did you mean to install?
npm ERR!      C:\Users\monangi\AppData\Roaming\npm-cache_logs\2021-01-22T11_40_51_958Z-debug.log

npm WARN Local package.json exists, but node_modules missing, did you mean to install? Try npm install, then run npm start.
refer to Installing

npm WARN Local package.json exists, but node_modules missing, did you mean to install? Try npm install, then run npm start.
refer to Installing

@kiranmonangi problem solved Kiran?

@kiranmonangi problem solved Kiran?

closing this, feel free to reopen if you're still facing issues

closing this, feel free to reopen if you're still facing issues


Code Review

Invoke-PSTenableRest

TLS settings should be declared during begin, not process
Extract TLS settings into dedicated function, to avoid code duplication.

Invoke-PSTenableTokenStatus

Unsuitable use of Write-Output

Connect-PSTenable

Wrong check for $Register parameter: Should be truth content check
Otherwise this:
-Register:$false

Will cause the command to perform a register afterall!

Get-PSTenableAssetAnalysis

Duplicate type declaration in Parameter
$ComputerName parameter should be of type [PSFComputer] not [string]
No reason to not accept from pipeline and process multiple computers in one call

Get-PSTenableCVE

$CVE should be a [string[]] not a [string] type
Storing results, just so they can be returned in the end block is a bad design. Should emit them as they are reached at.

Get-PSTenablePlugin

$ID should be a [string[]] not a [string] type
Storing results, just so they can be returned in the end block is a bad design. Should emit them as they are reached at.

Get-PSTenablePluginFamilyWindows

Storing results, just so they can be returned in the end block is a bad design. Should emit them as they are reached at.

Get-PSTenableSeverity

Data retrieval should happen during process

Get-PSTenableWindowsServerJava

Data retrieval should happen during process

General PSFramework Stuff:

Configuration settings should be declared & Initialized when used in modules.
e.g. during module import, execute something like this:
Set-PSFconfig -Module PSTenable -Name Credential -Value $null -Initialize -Validation credential -Description 'The credentials used for authenticating to the Tenable server'

Thank you @FriedrichWeinmann! Published 0.2.3 with code review.


Fixed comment of the sensor data byte array

The comment didn't describe what the unpack method really does

thx!


Support for Solidity 0.8.21

Changes

[x] Updated dependencies.
[x]  Added support of Solidity 0.8.21 on compiler level.
[x] Partially update test snapshots due to issues with compiler.

Notes
There is an issue with this compiler, that is tracked here: https://github.com/ethereum/solidity/issues/14430. Until it is resolved, this PR will stay in draft state due to limitation of ways to express some introduced syntax features.
Related links

Solidity 0.8.21 release notes
Solidity 0.8.21 release blog post

Regards.

Codecov Report

Merging #219 (5927771) into master (f39f97b) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master     #219   +/-   ##
=======================================
  Coverage   91.73%   91.74%
=======================================
  Files         267      267
  Lines        6549     6550    +1
  Branches     1320     1320
=======================================
+ Hits         6008     6009    +1
  Misses        287      287
  Partials      254      254

Impacted Files
Coverage Δ

src/compile/constants.ts
100.00% <ø> (ø)

src/compile/kinds/compiler.ts
79.01% <100.00%> (+0.26%)
:arrow_up:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Tabnine binary doesn't work on Apple M1 machines

OS version: Mac M1
Editor: All
Programming language: All
Tabnine extension version: 3.1.18

Help -> Toggle Developer Tools
Issue Details:
Tabnine was installed in MacBook pro with Apple Silicon M1, but it didn't work.
There are no error logs.

@talcodota Check my post Make Tabnine Great Again on Apple M1 Chip

The x86_64 binary works fine on Apple Silicon (as the link in the previous comment indicates)
Of course, a native binary would be even better.

Hi folks
We are working on supporting Apple Silicon for Tabnine, and we are getting close to release.
We can provide a private plugin build for either vscode or intellij idea (and other jetbrains products).
If you are interested - contact<EMAIL_ADDRESS>

Hi folks
We are working on supporting Apple Silicon for Tabnine, and we are getting close to release.
We can provide a private plugin build for either vscode or intellij idea (and other jetbrains products).
If you are interested - contact<EMAIL_ADDRESS>

how

how

We have released plugins with m1 support for vscode, intellij (and other jetbrains products), sublime, vim.
If you update your plugin to the latest version, you should be able to work normally on an m1 machine.
Note that for vscode you should currently install vscode insiders build, until they formally release a version that supports m1 natively.

We have released plugins with m1 support for vscode, intellij (and other jetbrains products), sublime, vim.
If you update your plugin to the latest version, you should be able to work normally on an m1 machine.
Note that for vscode you should currently install vscode insiders build, until they formally release a version that supports m1 natively.

What's the first version that supports M1? I would like to update company-tabnine.

What's the first version that supports M1? I would like to update company-tabnine.

I think it was 3.2.84' but since we already released some more versions.
I think if you update the dl_binaries script to be the same as here and run it, it will update to the latest

I think it was 3.2.84' but since we already released some more versions.
I think if you update the dl_binaries script to be the same as here and run it, it will update to the latest

Note that for vscode you should currently install vscode insiders build, until they formally release a version that supports m1 natively.

This is also the message in the app:

Apple M1 users, you can switch to the VSCode insiders build version to enable Tabnine's local deep completions. See details here.

But VS Code supports M1 in the mainline since 1.54.

Hi,
versions 3.3.104 and 3.3.33 in vim when vim is ran inside of Alacritty are causing vim to be unusable. Non of the keys are responding. In normal terminal is fine. Does anybody have any ideas what happens when vim with TabNine is ran inside of Alacritty?

Hi, is it possible to use Tabnine on a Macbook Pro m1 2020 in Jupyter Notebook?

just in case to anyone encountered with this problem using this fix
cd ~.local/share/nvim/site/pack/packer/opt/cmp-tabnine
#then run the install.sh again in that directory, it fail for me when I run :PackerCompile, just run:
./install.sh


[MB-2619] Approve / Reject / Clear Status of Service Items

Description
Implements the UI for approving, rejecting, and clearing status of Service Items for the TIO interface.

Adds a Formik form to ReviewServiceItems where each item has a status and rejectionReason field.
User can select Approve or Reject for each service item, which will set the status accordingly
If the status is REJECTED, the rejection reason textarea field will display
Clear selection resets the values for a specific service item

Other changes:

Added stories for ServiceItemCard
Also updated some Storybook styles to make it easier to display full-height components

Not included:

Validations
Any API interactions, persisting to the server

todo:

Add accept/reject/clear icons
form should scroll within the sidebar
use service item status constants

Reviewer Notes
Is there anything you would like reviewers to give additional scrutiny?
Setup
Add any steps or code to run in this section to help others prepare to run your code:
echo "Code goes here"

Code Review Verification Steps

[ ] Code follows the guidelines for Logging
[ ] The requirements listed in
Querying the Database Safely
have been satisfied.
Any new migrations/schema changes:

[ ] Follow our guidelines for zero-downtime deploys (see Zero-Downtime Deploys)
[ ] Have been communicated to #g-database
[ ] Secure migrations have been tested following the instructions in our docs

[ ] There are no aXe warnings for UI.
[ ] This works in Supported Browsers and their phone views (Chrome, Firefox, IE, Edge).
[ ] Tested in the Experimental environment (for changes to containers, app startup, or connection to data stores)
[ ] User facing changes have been reviewed by design.
[ ] Request review from a member of a different team.
[ ] Have the Jira acceptance criteria been met for this change?

References

Jira story for this change
this article explains more about the approach used.

Screenshots
If this PR makes visible UI changes, an image of the finished UI can help reviewers and casual
observers understand the context of the changes. A before image is optional and
can be included at the submitter's discretion.
Consider using an animated image to show an entire workflow instead of using multiple images. You may want to use GIPHY CAPTURE for this! 📸
Please frame screenshots to show enough useful context but also highlight the affected regions.

Warnings

:warning:
This PR does not include changes to unit tests, even though it affects app code.

Messages

:book:
:link: MB-2619

  Generated by :no_entry_sign: dangerJS against f92bb5ce3d41d64561e727ed6d758cb79665fde1


Skip ghost atoms with no real neighbors in 3-body force featurization

The 3-body force featurization algorithm was modified (conceptually just a 2-line addition) to skip triplets where the center atom is a ghost atom and all of its neighbors are also all ghost atoms. I have verified that the resulting feature values and the model remain the same compared to before the fix in the Tungsten example, and the pytest suites with the featurization unit tests also all pass.
Right now, this PR appears to have lots of changes because it builds on top of #116 . However, it boils down to 2 things:

Slight refactoring of generate_triplets() where the outer-most for-loop (over the center atoms i_values) were taken out to its own function called group_idx_by_center()
A single if-statement in featurize_force_3b() in angles.py that checks if the center atom is a ghost atom and all its neighbors are also ghost atoms

Adding this single if-statement decreased the 3-body force featurization time of the last structure in the Tungsten example from 46.6 seconds to just 6.6 seconds, which is a 700% speedup. The total featurization time for the Tungsten example decreased from 15 minutes 20 seconds in #116 to just 3 minutes 37 seconds (with 16 cores on my server).

UPDATE: I have figured out a very easy way to filter all-ghost triplets on an individual triplet level instead of checking the entirety of the neighbor list first, and this also cuts the unnecessary computations by a good chunk. Again, these changes do not change any of the resulting feature values.
I have moved the if-statement inside generate_triplets(), in which the 3-body neighbor mesh used to be generated like j_arr, k_arr = np.meshgrid(i_group, i_group). With the newest changes, the meshes are generated by j_arr, k_arr = np.meshgrid(i_group_filtered, i_group), where i_group_filtered only includes real atoms if i_value (the central atom) is a ghost atom. For illustration, if the i_group of a central ghost atom has no real atoms, then the mesh will return an empty array, as like before. But also now, if i_group has only 1 real atom and 25 ghost atoms, it now returns a mesh with 26 entries, whereas previously it would have returned a mesh of 26^2 == 676 entries.
This change cut down the 3-body force featurization time to just 5.0 seconds, which is a 932% speedup.

I've also made the changes for 2-body force featurization, and it gives roughly a 4.4x speedup on the 2-body force featurization part but only a tiny change in the whole featurization speed because the 3-body force dominates the time.
The change was made in the derivatives_by_interaction() function, where the bottom (N-n) x (N-n) block of the supercell distance matrix is masked out, where N is the number of atoms in the supercell and n is the number of atoms in the unit cell.
I've verified that the features and the model for the Tungsten example are the same as before. Also, all the unit tests that test the feature values all pass. However, there are 2 unit tests in test_distances.py that fail: TestUnary::test_distance_derivatives and TestBinary::test_distance_derivatives. These unit tests count the number of distances returned from derivatives_by_interaction(), which is obviously going to be different because it filters out a lot of the unnecessary distances.
I will look over this further and make changes to the pytest after further discussion with other developers.

I have checked the code for accuracy. It gives accurate features that numerically match the current version. I will give detailed comments on the code at a later time.

Since the changes seem accurate, I will now correct the assertion values on the failing unit tests.

I have not changed any code since @sxie22 's approval of this PR, but all the sudden the pull requests are failing. Here is the error message from the tests:

A module that was compiled using NumPy 1.x cannot be run in
NumPy 2.0.0 as it may crash. To support both 1.x and 2.x
versions of NumPy, modules must be compiled with NumPy 2.0.
Some module may need to rebuild instead e.g. with 'pybind11>=2.12'.
If you are a user of the module, the easiest solution will be to
downgrade to 'numpy<2' or try to upgrade the affected module.
We expect that some modules will need time to support NumPy 2.

These seem to be triggered by import tables and import ndsplines and its incompatibility with Numpy 2.x.x, which was released just 5 days ago on June 16th, 2024. On my local computer, which uses Numpy 1.26.4, all the tests still pass.

@sunghjung3 What we can do is hard code the numpy version to the most latest version which works.
After couple of months we will change the hard coded version. What do you say?

@monk-04 I've pinned the Numpy version to 1.26.4 (the latest version 1) other than for Python 3.8, which doesn't support Numpy versions newer than 1.24.4.


Default branch during push not configurable

When using the Push to Gerrit option, I've noticed that the upstream branch always defaults to the respective local branch name.
In a local feature-branch workflow with arbitrary branch names, developers have to manually change the upstream branch selected in Push to Gerrit  with every push to the one their gerrit repository is configured to.
It would be great if default target branches were configurable (or memorized). One option might be parsing the defaultbranch option in  .gitreview files commonly used in gerrit-based workflows.

Implemented such approach in #329

How about an easy checkbox "remember branch" on the push dialog?


Survey Runs: add submission/approval date offsets and add an is_default column

[x] add an approval date due column
[x] add an is_default column
[x] editable owner list
[x] inline survey viewer

[x] action invocation

This turned into a bigger task, now includes:

new survey viewer (shows section)
new action section


Add Fosscord support

Describe the solution you'd like
I wanted to have Fosscord support on this bridge. This app has all the same api as Discord, just needed to specify instance endpoint instead of discord.com

Fosscord is an Discord client. I think you misunderstand what Matterbridge does.


Allow multiple selections, but with no tags. :limit doesnt really help [workaround]

What i am trying to achieve, is select with fixed height.
Something like

The problem with :limit is: select doubles the height, which is not what i want.
Top half is whatever in limit slot, botton half is placeholder.
Any suggestions how to make it inline?
#580 is kind of related.

Ok, this is what i'm came up with:
I've created component, that extend VueMultiselect, and overrides a couple of things.
<script>
    import Multiselect from 'vue-multiselect'

    export default {
        extends: Multiselect,
        name: "vue-multiselect",
        props: {
            limitText: {
                type: Function,
                default: function (count) {
                    return `${this.placeholder} (${count})`
                }
            },

        },
        computed: {

            isSingleLabelVisible () {
                return this.singleValue &&
                    (!this.isOpen || !this.searchable) &&
                    (!this.visibleValues.length && this.limit > 0)
            },
        },
    }
</script>

Thank you for your feedback and the workaround! Have you done the extension in the same component where you also use the multiselect? Because I get some errors that some other props would be missing which are required in VueMultiselect. Maybe you could provide a more detailed example. Would be create. Thank you!!

I've created MyMultiselect.vue, which contains code from comment above.
This component can be imported and used like any other component.
The only change needed In component where i used vue-multiselect, were import path. Instead of importing global vue-multiselect (from node_modules), import from local .vue component.

Cool, is working. Thank you very much!

Is there any possibility of getting the ability to turn off the singleLabel (even by making the computed a getter and setter for isSingleLabelVisible if you want) without having to resort to the extender.
I have searchable = false, limit = 0 to hide the tags, show the single selected item text if one and the count if multiple.
The way it is, it affects the height pushing content around  and even if it didnt do that having it appear at the end would look weird) just looks weird
https://jsfiddle.net/jqofkzxc/3059/
The solution provided by @sourenaraya is perfect from a UI POV, although id rather not need to have to have the wrapper (or fork it) just for this functionality, having it baked in makes sense (and it would only cost a few bytes).

That’s an interesting case. Should be possible to do much easier in 3.0.


Update Biocurious.md

Updated new address, and current SQFT
!!DELETE THIS TEMPLATE AFTER READING
Before submitting an Issue

Merge conflicts: conflicts are more common when working locally.
Organize new PRs: Members should organize pull requests and apply labels

In your Pull Request

describe proposed changes in bullet points if appropriate
link to an issues it may be addressing fixing something? include the # of the issue

Hi @eharness just want to confirm that you still want to make these updates. I went looking at some recent forks and turned them into pull requests because I noticed that many people make a fork and edited but did not make a request to merge.

Thanks,  for checking yes we still want to make the changes.   I think I forgot to merge becuase I am a neebie on the platform.  The address needes to be changed and updated.  Thansk

No problem. We're working on a form to make updates and submission easier. But as of now we rely on people's knowledge of git.


Fail to verify basic flipper contract

I've done the following:

Build the ink-verifier-image locally from main branch.
Create a basic flipper contract cargo contract new flipper
cd flipper and run build-verifiable-ink -t develop .

The result is that it fails to build the package:
  flipper build-verifiable-ink -t develop .
Building package w/ args: ["run", "-i", "-t", "--rm", "--entrypoint", "package-contract", "-v", "/Users/gorskimateusz/projects/aleph/flipper:/build", "ink-verifier:develop"]
mv: failed to preserve ownership for '/build/package/src/Cargo.toml': Permission denied
mv: failed to preserve ownership for '/build/package/src/lib.rs': Permission denied
mv: failed to preserve ownership for '/build/package/src': Permission denied
Build Info

- build_mode: Release
- cargo_contract_version: 2.0.2
- rustc_toolchain: 1.66.1-x86_64-unknown-linux-gnu
- optimization_passes: Z
- keep_debug_symbols: false

In SRC_ROOT
total 20K
drwxr-xr-x 1 501 dialout  128 May 12 08:44 .
drwxr-xr-x 1 501 dialout   96 May 12 08:44 ..
-rwxr-xr-x 1 501 dialout  573 May 12 08:44 Cargo.toml
-rwxr-xr-x 1 501 dialout 5.1K May 12 08:44 lib.rs
error: DEPRECATED: future versions of rustup will require --force-non-host to install a non-host toolchain as the default.
warning: toolchain '1.66.1-x86_64-unknown-linux-gnu' may not be able to run on this system.
warning: If you meant to build software to target that platform, perhaps try `rustup target add x86_64-unknown-linux-gnu` instead?
info: syncing channel updates for '1.66.1-x86_64-unknown-linux-gnu'
warning: Signature verification failed for 'https://static.rust-lang.org/dist/channel-rust-1.66.1.toml'
info: latest update on 2023-01-10, rust version 1.66.1 (90743e729 2023-01-10)
info: downloading component 'cargo'
info: downloading component 'rust-std'
 30.0 MiB /  30.0 MiB (100 %)   3.4 MiB/s in  8s ETA:  0s
info: downloading component 'rustc'
 67.4 MiB /  67.4 MiB (100 %)   4.7 MiB/s in 18s ETA:  0s
info: installing component 'cargo'
info: installing component 'rust-std'
 30.0 MiB /  30.0 MiB (100 %)  20.9 MiB/s in  1s ETA:  0s
info: installing component 'rustc'
 67.4 MiB /  67.4 MiB (100 %)  24.5 MiB/s in  2s ETA:  0s

  1.66.1-x86_64-unknown-linux-gnu installed - (error reading rustc version)

info: checking for self-updates
info: downloading self-update
info: downloading component 'rust-std' for 'wasm32-unknown-unknown'
info: installing component 'rust-std' for 'wasm32-unknown-unknown'
info: downloading component 'rust-src'
info: installing component 'rust-src'
    Updating crates.io index
  Downloaded cargo-contract v2.0.2
  Downloaded 1 crate (94.8 KB) in 1.47s
  Installing cargo-contract v2.0.2

// Omitting lines with downloading and installing dependencies for brevity

Downloaded 420 crates (36.2 MB) in 30.81s (largest was `ring` at 5.1 MB)
error: failed to compile `cargo-contract v2.0.2`, intermediate artifacts can be found at `/tmp/cargo-installbjuGr0`

Caused by:
  package `ink_env v4.2.0` cannot be built because it requires rustc 1.68 or newer, while the currently active rustc version is 1.66.1
  Try re-running cargo install with `--locked`

Notice the errors at the beginning.

Realted https://github.com/web3labs/ink-verifier-image/issues/6

Most probably, adding --locked to cargo install ... cargo-contract will solve the issue.

hello @deuszx ! both the problems (#6 and the --locked flag) have been resolved in the latest release, particularly, in this commit: https://github.com/web3labs/ink-verifier-image/commit/a397b0d5c13d5a554034e61556786d6b3c08256e


can you add support of .net5.0

I Make a project in .net5.0-Windows
can you modify or convert your app for that, Thanks

Apologize for the bit late reply.
Note that I have archived the current version of MadMilkman.Ini and I'm now working on a new version with more explicit API, improved performance, better documentation, etc.
However, this won't be done any time soon.
So I decided that I will add a build for .NET Standard 2.0 in the archived version.
I'll let you know when it's ready.

any news. Really like your project but need it for .net 5 :)

Ended up having to port it to .NET Standard 2.0 myself for one of my projects, so I hope this helps other people in this thread and anyone else reading this. Please note that the way I did it removed support for old versions of .NET Framework that don't support .NET Standard 2.0, but I figured it was a worthwhile tradeoff since it shouldn't vary too much from the original, and those versions of .NET Framework are, well, old for the most part.
Here's the fork: https://github.com/DrewNaylor/MadMilkman.Ini


Pass arguments for mise run interactive menu

I have a bash script which takes an argument and a mise action in .mise.toml:
[tasks."genflux"]
description = 'Generate Flux module'
run = "./Scripts/flux.sh -n $1"

I can run the action this way: mise run genflux MyModule
But is there a way to use interactive menu (using just mise run) to select the action and then pass the argument?

I don't think I would want to do this. It would require an awkward flag like mise run --args or something that feels more confusing to try to explain than is worth the value in having this

It might look like this, without passing awkward flags to mise run itself:
[tasks."genflux"]
description = 'Generate Flux module'
args = ["arg1", "arg2"]
run = "./Scripts/flux.sh --arg $1 --arg2 $2"

I think what you're asking for is default arguments, which is planned but something that might take me a while to get around to

I apologize for being confusing. What I was asking is parameters names, not their default values.
After selecting an action ditch a defined array of parameters names, mise interactive menu would ask user to input missing values (in case of interactive mode all arguments are missing lol). Like, for example, it's implemented in Fastlane.

ah this also is planned, it's part of what I'm working on with usage. That said, I have no clue when I'll be able to get to it


[move source language] Added spec id ~> code offset to compiled unit

Motivation

Added Nop's with optional label to IR
The source map now has a map from nop label ~> offset
The source language compiled unit maps from spec id ~> offset

Test Plan

cargo test

[move-prover] Move Prover test (language/move-prover/cargo test) on commit f630831 did fail. See details.

This will go away once #3037 is merged. This PR hangs in the queue for 5 hours now _&()&*(!

@bors-libra r=shazqadeer

:pushpin: Commit 28c920e has been approved by shazqadeer

:hourglass: Testing commit 28c920ebafb5230051669a4067ce028b4ba72521 with merge 583cb983397d159cbd11b3306cc14ba90b9a3422...

:sunny: Test successful - checks-actions_land_blocking_test, checks-circle_commit_workflow
Approved by: shazqadeer
Pushing 583cb983397d159cbd11b3306cc14ba90b9a3422 to master...


Don't require FLASK_APP to have .py extension

Addresses #2377. The simplest way that I found to do this was to just patch the find_default_import_path method to check if there's a file with the .py extension.
Worked in all of my testing. 🙂

Thanks! This is sort of the opposite direction of what I was imagining though. For example, a package that's not installed still requires FLASK_APP=myapp/__init__ when it should be importable as myapp because the current directory is on the PYTHONPATH.

Ah, I see. I updated the method to append the sys path if the referenced FLASK_APP is a directory. That should cover both the case where FLASK_APP=myapp and FLASK_APP=/path/to/myapp (where myapp is a module that contains a Flask app)

A friend pointed out that FLASK_APP=module flask run already works without the .py. So now I'm trying to figure out why that's importable but FLASK_APP=package isn't.

@davidism wouldn't it hinge on os.path.isfile() behavior? In that case, don't see how FLASK_APP=module would work unless os.path doesn't care about file extensions...

Because the current directory is already inserted into the path.

@davidism are you sure FLASK_APP=module flask run already works?  This is the behavior I'm seeing (without installing either mod or pack into the current environment):

FLASK_APP=(mod|package) flask run: immediate error; file/path does not seem to exist, etc. etc.
FLASK_APP=(mod|package) FLASK_DEBUG=1 flask run: the server starts but as soon as you request a page it throws a flask.cli.NoAppException

However (not surprisingly):

FLASK_APP=(module|pack) FLASK_DEBUG=(0|1) python -m flask run: always works

In no case does it seem to matter if FLASK_APP is pointed at a module or a package.

Thanks for working on this. I ended up fixing this in #2414 by dropping the .py requirement rather than handling directories differently.


"Microbatch" incremental strategy

Resolves #6136
What are you changing in this pull request and why?

Add docs on microbatch incremental strategy (v1.9+)
Add microbatch to table of incremental strategies

Checklist

[x] I have reviewed the Content style guide so my content adheres to these guidelines.
[x] The topic I'm writing about is for specific dbt version(s) and I have versioned it according to the version a whole page and/or version a block of content guidelines.
[x] I have added checklist item(s) to this list for anything anything that needs to happen before this PR is merged, such as "needs technical review" or "change base branch."
[x] Add/remove page in website/sidebars.js
[x] Provide a unique filename for new pages

Currently microbatch is supported on postgres, snowflake, and bigquery with more adapters to come!

Currently, as microbatch is still in "beta", this functionality is still gated behind an env var (will be swapped to behavior change flag ahead of the final 1.9 release) - so you need to set DBT_EXPERIMENTAL_MICROBATCH to true in your project

Just a heads up @jtcohen6 and @graciegoheen -- the screenshots are not very visible in dark mode bc of the black text:
Screenshot 2024-10-01 at 20 34 08

@mirnawong1 what color would be better for the screenshots for dark mode?

@mirnawong1 what color would be better for the screenshots for dark mode?

Hmm I think if the actual image sat on top of a white background, it'd be fine in both modes!

Adding the pics with the white background:

@graciegoheen @jtcohen6 the white imgs look better in dark and light mode! thanks for providing them


[WIP] including meta table when reading and writing xlsx files

Please confirm that this PR has done the following:

[x] Tests Added
[x] Documentation Added
[ ] Description in RELEASE_NOTES.md Added

Adding to RELEASE_NOTES.md (remove section after adding to RELEASE_NOTES.md)
Please add a single line in the release notes similar to the following:
- (#XX)[http://link-to-pr.com] Added feature which does something

Description of PR
Following #286 and some offline discussions about supporting more data formats, this PR implements also writing the meta table (by default, option to switch off) as part of to_excel(). Similarly, when initialising from xlsx, it will look for a meta sheet and use it to populate that table.
As an aside, the PR also streamlines the IO-tests and moves them into an own test file.

Coverage decreased (-0.6%) to 84.701% when pulling b7b7cf27a2a003a794801b4571973774d46b3468 on danielhuppmann:io/xslx_incl_meta into a4e266c93f531f94285311fd354aaa881aa403c4 on IAMconsortium:master.

closing in favour of #295


Exclude compiler/gcbarriers/UnsafeIntrinsicsTest.java jdk11 aarch64

Signed-off-by: Simon Rushton<EMAIL_ADDRESS>

Ref: https://github.com/adoptium/aqa-tests/issues/2640

Grinder run of failing target with this PR (now passes): https://ci.adoptopenjdk.net/view/Test_grinder/job/Grinder/825/console


add fresh lasagna recipe and picture

There's already a lasagna recipe.

There's already a lasagna recipe.

oh yeah was supposed to change that one, if you take a look at it i find it quite lackluster since it uses store bought pasta sauce etc.

Make the changes to his article and then link to separate directions for sauce so people can either follow those extra directions or buy their own. Looking on what you have, it looks like you sort of already have that in this article. You can feel free to mostly replace his.
Also, use proper markdown links. If you just paste the URL, it won't link properly.

will do!


Campy McCamp Face

Hey, working on integrating Urchin with the 600 Series Uploader for Medtronic pumps. First pass is going great and loving the rapid availability of data on the watchface and for offline use.
I have sgv, bolus and basal as well as event specific status text ie temps / suspends / running dual and square combos that can be pushed - which is nice and allows the watchface to be a extension of the pump and more then a sgv viewer.
What I'm wondering is can Urchin prefs be read? This is mainly to get the scale component for scaling the basal data.
Also when I enter a different menu on the pebble and go back to the watchface is there a way of getting a startup call so that data can be refreshed from the uploader? as it can be blank until the next sgv update.
And a few requests:
Sightly bigger fonts for the status text - hard to read them at times.
Simple alarm reciever for controler clients like this to send an alarm msg + vibe seq.
"app mode" in the prefs for the endpoint.
Thanks!

Quiet round these parts ;)
Sorted out a way of getting the watchface to refresh by intercepting acks from the pebble JS and resending data when the ID is different to the transaction ID that I'm using. A bit hacky but works for now.
The Urchin support is now part of the uploader and works well.


Does netlify dev --live support redirect shadowing?

We have a rule in the redirects that catches pages that don't exist and redirects them to a 404 page. However, it seems to be catching all pages and static assets that do exist and redirecting. This same redirect file works when live but when using the netlify dev --live command the redirect rules don't work.

BUG REPORT INFORMATION
- Do you want to request a feature or report a bug?
BUG
- What is the current behavior?
Visiting static asset urls that exist redirect because the redirect rule catches all
- If the current behavior is a bug, please provide the steps to reproduce.
Edit your _redirects file to include this at the end:
/* /404

Visit any page and all your static assets should be left in some kind of 301 redirect loop.
- What is the expected behavior?
Pages and assets that exist are not redirected and follow shadow pattern that live sites respect: Netlify Shadowing
- Local Environment Information
────────────────────┐
 Environment Info   │
────────────────────┘

System:
    OS: Linux 5.6 Fedora 32 (Workstation Edition) 32 (Workstation Edition)
    CPU: (4) x64 Intel(R) Core(TM) i5-4690K CPU @ 3.50GHz
  Binaries:
    Node: 12.16.3 - /usr/bin/node
    Yarn: 1.21.1 - /usr/bin/yarn
    npm: 6.14.4 - /usr/bin/npm
  Browsers:
    Chrome: 81.0.4044.138
    Firefox: 76.0.1
  npmGlobalPackages:
    netlify-cli: 2.51.0

netlify-cli/2.51.0 linux-x64 node-v12.16.3

@pixelprogrammer Thank you for opening this issue. netlify dev looks for static files in your publish directory, and falls back to redirect if no file exists.
Can you please share the build and dev sections of your netlify.toml and your project's directory structure!

Sure thing:
netlify.toml
[build]
  command = "npm run build"
  publish = "dist"

[dev]
  framework = "nuxt"
  command = "npm run dev"
  publish = "dist"
  autoLaunch = true

Directory Structure
dist/
  _nuxt/
  _redirects
  some-image.png
  ...etc
static/
  _redirects
  some-image.png
  ...etc
components/
pages/
netlify.toml
nuxt.config.js
...etc

So in that example, if I go to https://website.com/some-image.png I get a redirect loop for that image. Same with assets within the _nuxt folder.

Hi @erezrokah . I'm able reproduce this failure to shadow files with the current version of netlify-cli:
$ netlify version
netlify-cli/2.64.1 darwin-x64 node-v10.16.0
$ tree
.
├── README.md
├── base
│   ├── copy-build.sh
│   ├── netlify.toml
│   ├── post
│   │   ├── Page-2
│   │   │   └── index.html
│   │   ├── green-river.png
│   │   ├── index.html
│   │   └── large.jpg
│   └── pre
│       ├── Page-2
│       │   └── index.html
│       ├── _redirects
│       ├── ads.txt
│       ├── green-river.png
│       ├── index.html
│       ├── large.jpg
│       ├── logo.svg
│       └── test.svg
├── exiter.sh
└── netlify.toml

If netlify.toml contains this:
[[redirects]]
  from = "/*"
  to = "/en/:splat"
  force = false

The following happens:
$ netlify dev -d base/post
◈ Netlify Dev ◈
◈ Injected addon env var:  NETLIFY_LFS_ORIGIN_URL
◈ Injected build setting env var: CI
◈ Using simple static server because --dir flag was specified
◈ Running static server from "base/post"

◈ Server listening to 3999

   ┌─────────────────────────────────────────────────┐
   │                                                 │
   │   ◈ Server now ready on http://localhost:8888   │
   │                                                 │
   └─────────────────────────────────────────────────┘

In another terminal I see this:
$ curl -svo /dev/null http://localhost:8888/
*   Trying <IP_ADDRESS>...
* TCP_NODELAY set
* Connected to localhost (<IP_ADDRESS>) port 8888 (#0)
> GET / HTTP/1.1
> Host: localhost:8888
> User-Agent: curl/7.64.1
> Accept: */*
>
< HTTP/1.1 301 Moved Permanently
< Location: /en/
< Cache-Control: no-cache
< Date: Wed, 30 Sep 2020 08:50:45 GMT
< Connection: keep-alive
< Transfer-Encoding: chunked
<
{ [30 bytes data]
* Connection #0 to host localhost left intact
* Closing connection 0

However, for the same setup, if I remove the redirect, I get the 200 response:
$ curl -svo /dev/null http://localhost:8888/
*   Trying <IP_ADDRESS>...
* TCP_NODELAY set
* Connected to localhost (<IP_ADDRESS>) port 8888 (#0)
> GET / HTTP/1.1
> Host: localhost:8888
> User-Agent: curl/7.64.1
> Accept: */*
>
< HTTP/1.1 200 OK
< x-powered-by: netlify-dev
< date: Wed, 30 Sep 2020 08:57:24 GMT
< content-type: text/html
< content-length: 437
< connection: close
<
{ [437 bytes data]
* Closing connection 0

The only change for the second curl request is that the redirect rule was deleted from netlify.toml. As the rule isn't forced, it should always be a 200 response even with the redirect.
In other words, the file shadowing doesn't appear to be working and the redirect rule is always used whether the file exists or not. I can make the demo repo I used for this public if you like.

I believe this was fixed by https://github.com/netlify/cli/pull/2195, so I'm closing the issue.
If it still reproduces in the latest version, please comment and I'll re-open


Gradle AddDependencyVisitor should not use default Maven repos

When downloading Maven metadata the AddDependencyVisitor should not configure any default repos and must therefore use the MavenPomDownloader(ExecutionContext) constructor.

/cc @shanman190 since you have in the past also worked on this and would know if this may have undesired side effects.

@knutwannheden, this should work just fine as the total list of repositories coming from Gradle will be in the list handed to the download methods.

@shanman190 Thanks! I just noticed today that we don't properly support repos defined in a subprojects block and that issue was masked by the fact that default repos got applied.

So actually, I think that is handled already. The repositories are pulled from the RepositoryHandler when the Gradle marker is being built. So when we are processing a subproject those will be there and available. ;)
https://github.com/openrewrite/rewrite-gradle-tooling-model/blob/b6a81d97772d82d19f31ee2dff38bec1726983f4/model/src/main/java/org/openrewrite/gradle/marker/GradleProjectBuilder.java#L58

Yes, kind of. IIRC the issue was when the root project in addition to the repositories also declared dependencies inside the subprojects block. When running a recipe like UpgradeDependencyVersion across the root project it would fail if the root project doesn't have repos defined of ita own.

Ahh, I see, I see. Yeah, for that case there would need to be something to contend with what Gradle proper would consider an anti pattern today. For the subproject block, we would want to consider the dependencies block from the perspective of the child repositories rather than the root project repositories, but as you can imagine that's going to be a little... difficult.

Thanks for confirming. Sam also suggests we wait with supporting this.


FEATURE: Add NodeJS Streams support to subscriptions

NodeJS has the concept of a Stream (i.e., Readable and Writable) which allows for processing a stream of data in an efficient manner, supporting transformations, multiplexing, and backpressure. This would be useful for easily writing queue subscriptions that, for example, read in messages, perform some transformations, then publish them to a separate queue, or write them to a database.
Detailed Description
I would propose offering a  function on the broker called subscribeStream(key) that returns an object-mode Readable of an object in the form of:
{
  message: Message,
  content: string | Buffer | any,
  ackOrNak: AckOrNack
}

This can then be piped to downstream consumers for further processing and eventually piped to a terminator that calls the ackOrNak function successfully. The pipes would need to implement error handlers that call the ackOrNak() with the appropriate error and remediation strategy, but overall the usage would be identical to existing consumers of the subscribe() API.
Context
We're piping data from RabbitMQ into our ElasticSearch cluster after doing some post-processing to make it more indexable. The ElasticSearch client supports reading from a stream to do bulk inserts into the database, which would simplify a lot of our processing, and overall the architecture of the program would be more straightforward if we could model this as a series of data streams, from the subscription to the database.
I'm certain this would be beneficial to other users who similarly use APIs that support ingesting data from streams, since this is a major feature of NodeJS and pretty prevalent for backend servers, which this library generally targets.
Possible Implementation
I'm not familiar enough with the internals of Rascal to suggest one, unfortunately.

Hi @JesseDocken,
Thank you for the suggestion. I'm not rascal is a good fit for a stream based subscriber. While I haven't worked with streams extensively, I suspect it would be unusual to pass a function such as ackOrNack down the pipe as well as the data. Pausing the stream would cancelling the consumer, and resuming would require reconsuming too. Overall, it sounds quite complicated. I'll give it a bit more consideration though.

I've given this feature some more thought and still don't think that a streams based interface is a natural fit for rascal. Sorry @JesseDocken.


feat: v0.3.0 upgrade handler

Description
Adds an upgrade handler for the GMP module. This will be used for v0.3.0

Author Checklist
All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.
I have...

[ ] included the correct type prefix in the PR title
[ ] added ! to the type prefix if API or client breaking change
[ ] added appropriate labels to the PR
[ ] targeted the correct branch
[ ] provided a link to the relevant issue or specification
[ ] added a changelog entry to CHANGELOG.md
[ ] included comments for documenting Go code
[ ] updated the relevant documentation or specification
[ ] reviewed "Files changed" and left comments if necessary
[ ] confirmed all CI checks have passed

Reviewers Checklist
All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.
I have...

[ ] confirmed the correct type prefix in the PR title
[ ] confirmed all author checklist items have been addressed
[ ] reviewed state machine logic
[ ] reviewed API design and naming
[ ] reviewed documentation is accurate
[ ] reviewed tests and test coverage
[ ] manually tested (if applicable)

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (dba3a2c) 15.82% compared to head (cc6f68b) 15.82%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main     #319   +/-   ##
=======================================
  Coverage   15.82%   15.82%
=======================================
  Files          78       78
  Lines       18961    18961
=======================================
  Hits         3000     3000
  Misses      15806    15806
  Partials      155      155

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


Initial request stops downloading

Hi,
I'm trying to make a request to 'https://pastebin.com/fwW5KqVD' which has a huge initial request file size.  However when I'm loading it through the chrome remote interface it stops receiving data early on at 4205249 bytes each time.
I'm guessing that there is a limit set somewhere either because it's in headless or because I'm missing a standard chrome switch but I can't find one anywhere.  The problem is that currently all event fires for the initial request (loadingFinished and dataReceived stops) so I have no way of knowing it's not loading correctly.
Do you know what might be causing this?
Kind Regards,
Anthony.

Are you using Docker or similar?
(The issue template was there for a reason.)
It doesn't stop, it's just very slow (~3m on my machine); but that's understandable, that webpage is loading ~20MB of data in the DOM. Even more time is spent if I try to load that URL in a regular (non headless and not inspected) Chrome instance.
What are you really trying to achieve here? Fetching the raw paste is obviously much faster.

Hi Cyrus,
Thanks for your response, I was expecting a notification but looks like I haven't got them turned on.
This looks like a error on my part, it seems that the chrome remote interface is downloading the full file in the allotted time and that the events are being hit as expected.  It's just that the file is encrypted so is much smaller than the file size shown in the browser.  This is great for us as I can just access this directly using the getResponseBody.  Previously I was trying to access this through the DOM and looks like I was getting a timeout there instead which is why part of the file was getting returned, as you mentioned this is obviously much slower than retrieving the raw file.
Sorry to have bothered you but thanks to checking,
Anthony.

No worries, good luck!


Fix upsert with $setOnInsert operator

Description

Closes #3224.
Readiness checklist

[ ] I added/updated unit tests (and they pass).
[x] I added/updated integration/compatibility tests (and they pass).
[ ] I added/updated comments and checked rendering.
[x] I made spot refactorings.
[ ] I updated user documentation.
[ ] I ran task all, and it passed.
[ ] I ensured that PR title is good enough for the changelog.
[ ] (for maintainers only) I set Reviewers (@FerretDB/core), Milestone (Next), Labels, Project and project's Sprint fields.
[ ] I marked all done items in this checklist.

Just a small comment that needs clarification. Otherwise, LGTM.

Thank you!


zabbix-cli: python2 -> python3

Motivation for this change
Move to Python 3 #148779.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Looks like @mweinelt beat me to this via #153151. Thanks mate!


PySyft Integration

We want to expose tfe.keras in a syft.keras package here.  This has several dependencies:
Required

Keras API #479
Between-graph helpers (i.e. accepting queued inputs) #483
model.share(protocol) way of converting from plaintext to encrypted model

Nice to have

PySyft model searching

Closed via https://github.com/OpenMined/PySyft/pull/2170


How to embed pdf.js into another module intended for use in webpack projects?

I created a simple module for converting PDFs to image data URLs within React apps here:
https://github.com/marcaaron/react-pdf-to-image
If I import this into a webpack project e.g. create-react-app and then build / serve this project all goes well. But in development mode I receive the following error message in JS console.
bootstrap:1 Uncaught ReferenceError: window is not defined
And webpack dev server complains about this:
./node_modules/pdfjs-dist/build/pdf.js Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
Steps to reproduce the problem:

Install package as dependency
Attempt to use in a create-react-app project

What is the expected behavior?
There would be some sort of way to add pdf.js with a worker as a dependency for other projects in development out of the box. Is this a limitation of web workers in general? Or can changes be made to the current distribution to allow this to work in all projects?

I believe this is not an issue with nesting in the package, but instead with the requireEnsure config being turned off in create-react-app.
See https://github.com/mozilla/pdf.js/issues/10253. Unfortunately the only way to adjust this config currently is to eject from CRA. We have our own config where we turned this off. I wonder if PDFjs could support dynamic imports instead going forward as they are now a standard. It's a tricky export with the workers currently.

So is it correct to say that you must eject from CRA in order for your project to use PDFJS?

/cc @timvandermeij Given the example added in PR #11220, and that the Critical dependency: ... warnings should have been removed in PR #11418, should this issue be closed now?

Yes, indeed.


fifo

could this be used to implement a fifo? if so, is this thread-safe or thread-unsafe

If by fifo you mean that the elements coming in a pipe come out in the same order, then with the pipes currently implemented in the library yes.
Could you please be more specific about thread safety ? Which use case do you have in mind?

If by fifo you mean that the elements coming in a pipe come out in the same order, then with the pipes currently implemented in the library yes.
Could you please be more specific about thread safety ? Which use case do you have in mind?

Like a Thread-Safe Queue


depends: erroneous output when combining conflicting packages

libpamac-aur (required by pamac-aur) and libpamac-full (required by pamac-all) conflict. When specifying the targets separately, everything is fine:
% aur depends pamac-aur
libpamac-aur	libpamac-aur
pamac-aur	libpamac-aur
pamac-aur	pamac-aur

% aur depends pamac-all
pamac-cli	pamac-cli
pamac-all	pamac-cli
libpamac-full	snapd
snapd	snapd
libpamac-full	libpamac-full
pamac-all	libpamac-full
snapd-glib	snapd-glib
libpamac-full	snapd-glib
libpamac	libpamac
pamac-cli	libpamac
pamac-all	pamac-all

When combining them, a hyphen appears:
% aur depends pamac-all pamac-aur
pamac-all	libpamac-full
libpamac-full	libpamac-full
pamac-aur	libpamac-aur
libpamac-aur	libpamac-aur
-	libpamac
libpamac	libpamac
pamac-all	pamac-all
pamac-all	pamac-aur
pamac-aur	pamac-aur
snapd	snapd
libpamac-full	snapd
libpamac-full	snapd-glib
snapd-glib	snapd-glib

It seems that pamac-cli is removed from the results because it is provided by pamac-aur. However, libpamac is provided by both libpamac-aur and libpamac-full and not removed from the output.
This also begs the question if or how depends should handle conflicts in the general case. With a local repository it doesn't matter much, but maybe some warnings could be printed.

I can't reproduce this with master - it seems I was checking with an old commit.


update source code of spokenwoz

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.眀彰 seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


problem in TC-TSTAT-2.1 (CON-1241)

Description
I'm trying to test my device that imlements a thermostat cluster, in the PICS i added the "Thermostat Cluster Test Plan.xml" file and this implemented the test case TSTAT.
The problem is in the step 18a in my case, the test tryes to "Read attribute MaxHeatSetpointLimit from the DUT" but i get the error "Test Failure: The response value (3500) should be lower or equal to the constraint but 3500 > 3000.".

I thougt that maybe I didn't initialized correctly the values of the attributes of the thermostat but it was not the case, in fact everything seems fine and I don't have any attribute with value 3000.
In the previous steps (Step 1) it reads all the attribute values and in both AbsMaxHeatSetpointLimit and MaxHeatSetpointLimit the value is 3500.

I can't figure out why in the test is used 3000 and not the 3500 value readed before.
The problem is only in the Heating Attributes and i don't know why.
These are my values:

Environment
ESP-IDF Commit Id: a322e6bdad4b6675d4597fb2722eea2851ba88cb (HEAD, tag: v5.2.1)
ESP-Matter Commit Id: https://github.com/espressif/esp-matter/commit/1a35c738dff33e5e988d92d0028ed7a60d4336f6 (HEAD -> release/v1.2, origin/release/v1.2)
connectedhomeip Commit Id: 46e1ad8478c55ec20273da9d40a9c6fecf5c6b38
SoC: ESP32-S3
Host Machine OS: Ubuntu 22.04.3 (WSL)

This problem affect the TC-TSTAT-2.2, in the step 7c "Writes the limit of MinHeatSetpointLimit to MaxHeatSetpointLimit attribute", in this test it's checked that MinHeatSetpointLimit <= MaxHeatSetpointLimit <= AbsMaxHeatSetpointLimit, but if the AbsmaxHeatSetpointLimit is wrong the test fails. (In my case 300<=3500<=3000)
It seeems that the test can't save the right value of AbsmaxHeatSetpointLimit or in the test is used 3000 as default value.

Why is the test using 3000 as value to check if the MaxHeatSetpointLimit is valid?

3000 is the default value of the MaxHeatSetpointLimit attribute. As I mentioned earlier, the certification test cases are designed based on the default value. If you want to test the changes you have made, please update the test suite, otherwise, set the attribute value to the default.
To update the existing YAML Test Script, follow the steps shown in the attached screenshot:

Thanks, it solved the problem, I still can't understand why the test was created like this, it was possible to make it fully automatic and without hardcoded values, but maybe you have your reasnons.


CI Build Failing

The unit tests pass on my machine, but fail on the continuous integration server. The reason isn't clear, but it happened at build 16 https://travis-ci.org/jtpereyda/ezoutlet/builds/107887962.
This was several changes ago, which is what I get for not using PRs and just committing straight to master.

Fixed in PR #4


Update landing page with current version on release

Before merging we must insert the pattern to match in the landing page.

https://github.com/schibsted/strongbox/commit/8e755dc92e0dc0e2bd2ae1089424f4c3e1682356