Fixes .size() is not a function error.

I replaced the function .size() to .length because it was removed in jQuery
since v1.8.
Maybe updating redactor.js to a newer version it's a better idea?

Good job! The redactor plugin is no longer maintained so this edit should be safe (it is the last build of redactor v1).


Remove fixed height constraint from host details component.

If some elements content extends beyond the assumed height it will overflow outside of the details block.
These changes remove any height limit, allowing flexbox to even the details height per row. Removing justify centre keeps the header in place at the top for details that are smaller than the max height in other blocks on that row.
Used flex 1 to expand the hosts details list elements to the remaining space in the details component. Can make for some odd spacing but seems nicer than bunching elements at the top of the component.
Without;

With changes, host html manually repeated to force flexbox to reflow and differ heights;

 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.You have signed the CLA already but the status is still pending? Let us recheck it.

This is a view we plan on revamping with the next version, but for now I think your changes are appropriate and should hopefully alleviate some issues others are seeing as well. :shipit: @groob

Agreed.
Thanks for the PR @Jackbennett !


Remove default values set by argument parser.

@drew-vanderriet I removed the other usages of the action() method from the commands. Can you do a quick review to verify that I didn't miss any before merging? Thank you.


Roaming

When the users device is roaming i.e. they are in another country (e.g. UK) to their normal "home" (e.g. USA) country, does the device return the roaming network?

please see #5


Delete of micromolecules bonds works wrong (or doesn't work)

Steps to Reproduce

Go to Macro - Flex
Load from file: Delete of micromolecules bonds works wrong (or doesn't work).zip

Delete few bonds

Actual behavior
Bonds between micro and macro - remain in place and atoms are selected

if you switch to Micro and back - all bonds got recovered

Expected behavior
Bonds between micro and macro - got deleted

Versions

Ketcher Version 2.27.0-rc.1 Build at 2024-11-05; 14:55:18
Indigo Toolkit Version 1.26.0-rc.1.0-g904d2d992-wasm32-wasm-clang-19.0.0
Chrome Version 130.0.6723.117 (Official Build) (64-bit)
Win10

Issue found while testing: https://github.com/epam/ketcher/issues/5359

Verified.

Ketcher Version 2.27.0-rc.3 Build at 2024-12-25; 10:08:04
Indigo Version 1.26.0-rc.5.0-g42ee8510b-wasm32-wasm-clang-19.0.0
Chrome Version 131.0.6778.205 (Official Build) (64-bit)
Win10


Many https://github.com/chriskempson/... links are dead

https://github.com/chriskempson/base16-textmate at
https://github.com/base16-project/base16/blob/c13a31c6a99b6921f0dd120277c142e52fc2d7b2/README.md?plain=1#L136-L138
https://github.com/chriskempson/base16-html-preview at
https://github.com/base16-project/base16/blob/c13a31c6a99b6921f0dd120277c142e52fc2d7b2/README.md?plain=1#L179-L181
https://github.com/chriskempson/base16-code-examples at
https://github.com/base16-project/base16/blob/c13a31c6a99b6921f0dd120277c142e52fc2d7b2/README.md?plain=1#L226-L228
are all dead...

it's specifically the URLs with the prefix mentioned in the title. All repos that formed the (previous) canonical upstream for base16 are suddenly gone, breaking countless links all over the place.
Notably, the original base16-schemes-source and base16-templates-source repos are now gone, which kills the v0.9 compatibility layer, and any builders that may have used github as a source for list.yaml will break.

You include multiple links in each block yet I know for certain https://github.com/highlightjs/base16-highlightjs is not dead, nor is https://github.com/atelierbram/base16-prism. Could you please double check and edit your post accordingly?

Only links from Chriskempson is dead, other links in the block are completely fine.
Instead of only show one line that contain the dead links, I expand the block for a bit too easily find the position of them relative in the file.
I probably shouldn't done that because it more confusing...

This includes https://github.com/chriskempson/base16, which is really bad.
It's the first page of google search "base16". It will probably get lower ranked if it continues to be broken.

I notice that this repo is now a fork of mateomarks/base16 instead of chriskempson/base16...

It looks like his whole account is gone - I got a response from GitHub support earlier today and I've reached out for more information and to see if it can be fixed.
Unfortunately, there's a non-zero chance Chris Kempson's stuff is now gone.

So, here's what I've been able to figure out so far: Chris either made all his base16 repos private or deleted them, along with all the code. This made the oldest fork of those repos into the default fork. For this spec repo, that was mateomarks/base16.
I've reached out to @mateomarks via email to see if he'd be willing to transfer his fork to me so I can at least point something to these repos. However, if he doesn't reply in the next day, I think it would make sense to detach from those repos and do what we can to continue.
Either way, once that's resolved I plan to go into public relations mode - these repos disappeared for everyone everywhere which has to be annoying to anybody using them. I'd like to let people know that we'd like to continue maintaining this project and where to find us.
I am operating under the assumption that any of the repos Chris previously maintained are gone for good - if they come back, we can look at copying over the ones we don't have. Unfortunately, that doesn't seem very likely at this point.

Good work, belak! We also need to fix his other repos, like base16-vim.

Hi all! Here's an update on what's been going on:

Chris unfortunately has not made any attempt to reach out - so we still have no way of contacting him. His website is still down and all emails sent to his email address bounce. I have sent him messages on a number of platforms, but there's no guarantee those will get any response.
It looks like Chris blocked me on GitHub, most likely because he's unhappy with how this went down. This unfortunately means I am unable to invite him to the org any more because GitHub just throws an error. I tried to do it twice before now, but they expired. This also means I cannot comment on any of his other repo's issues.
That brings us to this: people are already filing issues (https://github.com/chriskempson/tomorrow-theme/issues/354). Unfortunately, because of the previous point, GitHub prevents me from commenting on them.
I've reached out to @mateomarks (who has the oldest fork of base16-spec) and @danielsz (who has the oldest fork of base16-shell) via email to see if they're willing to transfer the repos to me so we can point them at the updated repos. If anyone finds other repos (I haven't located the original base16-vim) where the default fork has been changed and the owner is still active on GitHub, please let me know so I can reach out to them.
I've told GitHub support that we're detaching this repo from the repo network (so it won't say "forked from ..." any more). If we don't hear back from @mateomarks in the next day or two, I will be going through with this so we can move forward.

The repos are back online.  Thanks, Chris!  Does anything more need to be done here?  Are there any our org should fork just to preserve them for the future?

Here’s the story so far:

Chris has re-uploaded his repos with a number of changes

History is completely gone on the spec and sources repos.
Spec (on his repos) is back to 0.9.1
Schemes sources no longer links to our repo
There’s a new base16-builders repo
Issue trackers haven’t been removed
The original base16 spec repo seems to have been deleted and recreated rather than rewritten

Chris still hasn’t reached out to us and I remain blocked so I cannot comment or submit pull requests to these original repos.
I’m still waiting to hear back from GitHub support about detaching our repo - hopefully that will happen today.


Using the time zone with specific name for querying Druid

Using the time zone with specific name for querying Druid.
Just use DRUID_TZ = tz.gettz('Africa/Abidjan') to test, and then it will be modified into tz.tzutc().
By the way, sorry for creating so many PRs. I just figure out that i should create the new branch time_zone to contribute codes. :)

I don't understand why we want to use a random timezone as default in our config.

Not random... The timezone of Africa/Abidjan is +00:00~+00:00

@asdf2014 arbitrary not random, sorry. Anyway why you want to do so? It's just as an example of using gettz? What's wrong with utc?

There will be a option to support when we meet a wrong result from tz.tzlocal().

Yep, i just want add tz.gettz('Africa/Abidjan') as a doc for superset's users.

By the way, i got Server Error (500) message when i visit https://landscape.io/github/airbnb/superset/pulls/2143...

I got Server Error (500) message when i visit https://landscape.io/github/airbnb/superset/pulls/2143 too... What happened to landscape? :-(

LGTM !

Okey :D

is that changing the default timezone in the query?

I want to change the "UTC" to other timezone as the datetime stored in DB are not "UTC" timezone, that query return the datetime with some hours delay.
anyone has solution?
Cheers
Zac


fix(configuration): deprecate javascript.trailingComma in favor of javascript.trailingCommas

Summary
Attempt to address this https://github.com/biomejs/biome/pull/1948#issuecomment-1974632476.
But I don't know what's the idomatic way to deprecate an option.
Test Plan
I should add a test case to ensure the change is backward compatible when I figure out how to properly deprecate an option.

@Sec-ant sorry, I missed that you wanted to know how to deprecate an option.
Overall it looks good. To create a warning, we usually do it via migration. Here's an example of formatter.indentSize:https://github.com/biomejs/biome/blob/main/crates/biome_migrate/src/analyzers/indent_size.rs

@Sec-ant sorry, I missed that you wanted to know how to deprecate an option.

Don't be sorry, I was planning to dig a little deeper, and thanks for the tips. But unfortunately I'm a little occupied these days. Still trying to figure out a way to better balance the time here and in my real life.

What's left for this PR to land? Happy to help

What's left for this PR to land? Happy to help

TLDR, this PR now is not backward compatible, because I changed all the test cases to use trailingCommas instead of trailingComma, so all of them will pass. But this will be a breaking change for all the existing code.
When I first created this PR I was trying to find a solution to map both the trailingComma and trailingCommas inputs to a single representation in the internal structure. That's what I did for the bpaf command line args parsing (--trailing-comma is just an alias of --trailing-commas, and with the help of @pacak, I was also able to add some custom messages to indicate its deprecation). But I encountered problems on parsing the configuration JSON in this way. I think that's because we have our own deserialization based on serde that emits some further diagnostics (?), and that's where I have the problem implementing the similar alias mechanism like what I did with the command line parsing.
From what you suggested on how we handled formatter.indentSize, I think I was doing it in a wrong way: It seems that we need to keep both trailingComma and trailingCommas in the internal structure. And since then I haven't found enough large block of time to debug it, sorry about that.

So, configuration wise (biome.json and CLI), we will create a new field/option, the one that you want to create.
Then, when we do the deserialization to  WorkspaceSettings, we will map this new value to the one that we currently have.
Workspace settings is an internal type, this means that we can rename it without repercussions.
Sure, users might have the two options at the same time, and we could create an error/warning, but we can do it later.


Scale dokku apps

There is some way to create multiple instances of an app with the same domains, to scale a service?

This would be super useful although I think it could be rather difficult to set up properly.


make page object available in job

if job route was issued from a panel button.
https://forum.getkirby.com/t/using-page-variable-in-config-php-janitor-plugin/14236

Totally useful, I'm absolutely interested in this!

page object is now available in the job. see example
'heist' => function(Kirby\Cms\Page $page = null, string $data = null)

as a bonus i added a new prop datato the field which you can forward data from the blueprint to the job if needed.

Loving this plugin (using it to translate pages at will). One issue though--the $page object is null when the current page is in draft status. Is there a way around that?

Loving this plugin (using it to translate pages at will). One issue though--the $page object is null when the current page is in draft status. Is there a way around that?

its using the page helper to get the page object.
https://github.com/bnomei/kirby3-janitor/blob/0a905810b3d17401bf0280f8342c8b024e493018/classes/Janitor.php#L137
retrieving a non direct subchild draft is a not easy in kirby (yet?). so i do not have a good out of the box solution for that yet.
https://forum.getkirby.com/t/cant-get-draft-subpage-with-findpageordraft/14346
but you should be able to use the data prop to forward the targets diruri and retrieve the draft in you job yourself (without relying on the page object janitor forwards to the callback).

Aha! I found this workaround that you refer to. Thank you!

@bnomei couldn't you use kirby()->page() to get the the page even if has draft status?

@bnomei couldn't you use kirby()->page() to get the the page even if has draft status?

Ah! Now saw the workaround @lukehatfield mentioned and I understand.


⚠ Bofrost.fr has degraded performance

In 43377f2, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 883 ms

Resolved: Bofrost.fr performance has improved in 90e6092 after 45 minutes.


binfmt/binfmt_execmodule: Copy filename if CONFIG_BUILD_KERNEL and ar…

…gv=NULL
The 'filename' parameter comes from user space and cannot be accessed after calling ret = addrenv_select(binp->addrenv, &binp->oldenv); as it changes the address environment and 'filename' points to who knows where. In this case, calling nxtask_init(filename...) will cause a crash.
Solve this by making a local copy before changing address environment IF argv = NULL. Why ? Because argv[0] contains the process name in this case and the argument vector is already copied into kernel memory, thus passing argv[0] to nxtask_init(argv[0]...) is safe.

I'll upstream this and update if I get comments


Question: remapping  etc.?

Hi,
I am trying to map  to always switch to RESIDENT.
Here's my .vindrc:
inoremap <alt-down> <f19>
ennoremap <f19> to_resident

It does not work, what am I doing wrong?
Also: is there a way to apply this to all modes automatically?
Thanks
Gil

Sorry I have been so busy lately.
Mapping cannot cross modes except for macro.
What does it mean to "always switch to RESIDENT"? Do you mean the following settings?
inoremap <alt-down> to_resident
ennoremap <alt-down> to_resident

In the future, I'll add something that defines multiple modes at the same time without mode prefixes ike Vim (e.g. noremap).

Thanks for coming back!!
Yes, this works for now, and let me know if you implement multiple mode mappings.
Keep on doing this great work! I work with Vind a lot!


Extract publishPackages to it's own package?

Affected Packages
cli
Problem
The publishPackages method (https://github.com/atlassian/changesets/blob/master/packages/cli/src/commands/publish/publishPackages.ts) is located under the cli package, which means that it cannot be executed programatically (because it executes the cli instead, and it's not expored)
Proposed solution
Move to a new package to allow executing it easily.

We'll consider this after settling this issue: https://github.com/atlassian/changesets/issues/399 as it might influence the API shape of such module.


Add api for getting all coordinates of given trip id

This api call will be possible only from the creator user.

merged with #15


Refactor: Add map

added maps should be shown in the layer switcher

added maps should be shown in the layer switcher

Converted to issue #44


"no networks found in /etc/cni/net.d" Error for new worker nodes after upgrading from v2.4.5 to v2.4.6-rc10

What kind of request is this (question/bug/enhancement/feature request):
bug
Steps to reproduce (least amount of steps as possible):

run v2.4.5 HA
add a custom cluster ( 1 etcd, 1 control plane, 3 workers)
upgrade Rancher to v2.4.6-rc10
add 2 new workers to the existing custom cluster

Result:

see the following error on the kubelet in both new worker nodes

E0825 20:02:57.326206   15161 kubelet_node_status.go:92] Unable to register node "ip-172-31-21-225" with API server: Post https://<IP_ADDRESS>:6443/api/v1/nodes: read tcp <IP_ADDRESS>:45536-><IP_ADDRESS>:6443: read: connection reset by peer
E0825 20:02:57.392931   15161 kubelet.go:2268] node "ip-172-31-21-225" not found
E0825 20:02:58.495572   15161 kubelet.go:2268] node "ip-172-31-21-225" not found
E0825 20:02:58.595823   15161 kubelet.go:2268] node "ip-172-31-21-225" not found
E0825 20:02:58.664120   15161 controller.go:136] failed to ensure node lease exists, will retry in 7s, error: Get https://<IP_ADDRESS>:6443/apis/coordination.k8s.io/v1/namespaces/kube-node-lease/leases/ip-172-31-21-225?timeout=10s: context deadline exceeded
E0825 20:02:58.696050   15161 kubelet.go:2268] node "ip-172-31-21-225" not found
E0825 20:02:59.698398   15161 kubelet.go:2268] node "ip-172-31-21-225" not found
E0825 20:02:59.798650   15161 kubelet.go:2268] node "ip-172-31-21-225" not found
W0825 20:02:59.858571   15161 cni.go:237] Unable to update cni config: no networks found in /etc/cni/net.d
E0825 20:02:59.898905   15161 kubelet.go:2268] node "ip-172-31-21-225" not found
E0825 20:02:59.999169   15161 kubelet.go:2268] node "ip-172-31-21-225" not found
E0825 20:03:00.099399   15161 kubelet.go:2268] node "ip-172-31-21-225" not found
E0825 20:03:00.361474   15161 kubelet.go:2188] Container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:docker: network plugin is not ready: cni config uninitialized

Other details that may be helpful:

provisioning a new custom cluster works (1 etcd, 1 control plane, 1 worker)

Docker Version in the worker nodes
Client: Docker Engine - Community
 Version:           19.03.2
 API version:       1.40
 Go version:        go1.12.8
 Git commit:        6a30dfc
 Built:             Thu Aug 29 05:29:11 2019
 OS/Arch:           linux/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          19.03.2
  API version:      1.40 (minimum version 1.12)
  Go version:       go1.12.8
  Git commit:       6a30dfc
  Built:            Thu Aug 29 05:27:45 2019
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.2.6
  GitCommit:        894b81a4b802e4eb2a91d1ce216b8817763c29fb
 runc:
  Version:          1.0.0-rc8
  GitCommit:        425e105d5a03fabd737a126ad93d62a9eeede87f
 docker-init:
  Version:          0.18.0
  GitCommit:        fec3683

Also seeing this from the kubelet:
F0825 22:38:38.377206   15645 server.go:274] failed to run Kubelet: could not init cloud provider "aws": error finding instance i-05c4c058d2f597ffc: "error listing AWS instances: \"NoCredentialProviders: no valid providers in chain. Deprecated.\\n\\tFor verbose messaging see aws.Config.CredentialsChainVerboseErrors\""

retested this issue on v2.4.6-rc11 upgrading form v2.4.5
It turns out that we cannot add worker (or any kind) nodes from another region in AWS.
Adding a worker node from the same region works.
This is not a bug; the issue is closed.

I'm having this exact issue when adding from the same region.


Error when trying to filter refactorings

/Users/jason/.atom/packages/omnisharp-atom/node_modules/fuzzaldrin/lib/scorer.js:60
Hide Stack Trace
TypeError: undefined is not a function
at Object.exports.score (/Users/jason/.atom/packages/omnisharp-atom/node_modules/fuzzaldrin/lib/scorer.js:60:31)
at module.exports (/Users/jason/.atom/packages/omnisharp-atom/node_modules/fuzzaldrin/lib/filter.js:25:24)
at module.exports.filter (/Users/jason/.atom/packages/omnisharp-atom/node_modules/fuzzaldrin/lib/fuzzaldrin.js:21:14)
at CodeActionsView.module.exports.SelectListView.populateList (/Users/jason/.atom/packages/omnisharp-atom/node_modules/atom-space-pen-views/lib/select-list-view.js:195:25)
at /Users/jason/.atom/packages/omnisharp-atom/node_modules/atom-space-pen-views/lib/select-list-view.js:350:26

what are you breaking now?


bluej-bin: init at 414

Motivation for this change
BlueJ is used in my programming lecture. Disclaimer: This is my first package submission to nixpkgs.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
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 nix-review --run "nix-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)
[ ] Assured whether relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

@h0chi just ping me if you have any questions or need a hand with any of this.

@h0chi bluej is currently at version 4.2.2, please update the PR or close


correct post body for http alert plugin

Purpose of the pull request
This pull request fixes the issue with http alert plugin for posting correct contentField data
close #11945
Brief change log
fix in HttpSender.java and update HttpSenderTest.java
Verify this pull request
This pull request is already covered by existing tests: HttpSenderTest

Codecov Report

Merging #11946 (6e449f2) into 2.0.7-prepare (0ff3e9f) will decrease coverage by 0.01%.
The diff coverage is n/a.

@@                 Coverage Diff                 @@
##             2.0.7-prepare   #11946      +/-   ##
===================================================
- Coverage            20.90%   20.88%   -0.02%
+ Complexity            1607     1605       -2
===================================================
  Files                  540      540
  Lines                22912    22914       +2
  Branches              2732     2733       +1
===================================================
- Hits                  4789     4786       -3
- Misses               17629    17636       +7
+ Partials               494      492       -2

Impacted Files
Coverage Δ

...org/apache/dolphinscheduler/remote/utils/Host.java
37.77% <0.00%> (-2.23%)
:arrow_down:

...e/dolphinscheduler/remote/NettyRemotingClient.java
52.11% <0.00%> (-1.41%)
:arrow_down:

...olphinscheduler/server/utils/DependentExecute.java
0.00% <0.00%> (ø)

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

@SbloodyS


build pytorch_scatter in MacOS 10.13

I have used MACOSX_DEPLOYMENT_TARGET=10.13.6 CC=clang CXX=clang++ python setup.py install to install pytorch_scatter, but failed, here is the information of my system and log. Please help me to solve this problem, I want to use it to implement GNN in my paper.
Ps: I also used gcc, but still falied.
System

OS: MacOS 10.13.6
PyTorch version: 1.1.0
How you installed PyTorch (conda, pip, source): source
Python version: Anaconda python 3.6.4
CUDA/cuDNN version: CUDA 10.1
GPU models and configuration: GeForce GTX 1080
GCC version (if compiling from source): Apple LLVM version 10.0.0 (clang-1<IP_ADDRESS>)

Log

MACOSX_DEPLOYMENT_TARGET=10.13.6 CC=clang CXX=clang++ python setup.py install
running install
running bdist_egg
running egg_info
writing torch_scatter.egg-info/PKG-INFO
writing dependency_links to torch_scatter.egg-info/dependency_links.txt
writing top-level names to torch_scatter.egg-info/top_level.txt
reading manifest file 'torch_scatter.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
writing manifest file 'torch_scatter.egg-info/SOURCES.txt'
installing library code to build/bdist.macosx-10.7-x86_64/egg
running install_lib
running build_py
running build_ext
building 'torch_scatter.scatter_cuda' extension
clang -Wno-unused-result -Wsign-compare -Wunreachable-code -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -I/Users/kiwee/anaconda3/include -arch x86_64 -I/Users/kiwee/anaconda3/include -arch x86_64 -I/Users/kiwee/anaconda3/lib/python3.6/site-packages/torch/include -I/Users/kiwee/anaconda3/lib/python3.6/site-packages/torch/include/torch/csrc/api/include -I/Users/kiwee/anaconda3/lib/python3.6/site-packages/torch/include/TH -I/Users/kiwee/anaconda3/lib/python3.6/site-packages/torch/include/THC -I/usr/local/cuda/include -I/Users/kiwee/anaconda3/include/python3.6m -c cuda/scatter.cpp -o build/temp.macosx-10.7-x86_64-3.6/cuda/scatter.o -DTORCH_API_INCLUDE_EXTENSION_H -DTORCH_EXTENSION_NAME=scatter_cuda -std=c++11
/usr/local/cuda/bin/nvcc -I/Users/kiwee/anaconda3/lib/python3.6/site-packages/torch/include -I/Users/kiwee/anaconda3/lib/python3.6/site-packages/torch/include/torch/csrc/api/include -I/Users/kiwee/anaconda3/lib/python3.6/site-packages/torch/include/TH -I/Users/kiwee/anaconda3/lib/python3.6/site-packages/torch/include/THC -I/usr/local/cuda/include -I/Users/kiwee/anaconda3/include/python3.6m -c cuda/scatter_kernel.cu -o build/temp.macosx-10.7-x86_64-3.6/cuda/scatter_kernel.o -D__CUDA_NO_HALF_OPERATORS__ -D__CUDA_NO_HALF_CONVERSIONS__ -D__CUDA_NO_HALF2_OPERATORS__ --compiler-options '-fPIC' -DTORCH_API_INCLUDE_EXTENSION_H -DTORCH_EXTENSION_NAME=scatter_cuda -std=c++11
/Users/kiwee/anaconda3/lib/python3.6/site-packages/torch/include/c10/util/UniqueVoidPtr.h(69): warning: attribute namespace "clang" is unrecognized
/Users/kiwee/anaconda3/lib/python3.6/site-packages/torch/include/c10/core/Allocator.h(96): warning: attribute namespace "clang" is unrecognized
/Users/kiwee/anaconda3/lib/python3.6/site-packages/torch/include/c10/core/TensorOptions.h(175): warning: attribute namespace "clang" is unrecognized
/Users/kiwee/anaconda3/lib/python3.6/site-packages/torch/include/c10/core/TensorOptions.h(185): warning: attribute namespace "clang" is unrecognized
/Users/kiwee/anaconda3/lib/python3.6/site-packages/torch/include/c10/core/TensorOptions.h(194): warning: attribute namespace "clang" is unrecognized
/Users/kiwee/anaconda3/lib/python3.6/site-packages/torch/include/c10/core/TensorOptions.h(199): warning: attribute namespace "clang" is unrecognized
/Users/kiwee/anaconda3/lib/python3.6/site-packages/torch/include/c10/core/TensorOptions.h(206): warning: attribute namespace "clang" is unrecognized
/Users/kiwee/anaconda3/lib/python3.6/site-packages/torch/include/c10/core/TensorOptions.h(221): warning: attribute namespace "clang" is unrecognized
/Users/kiwee/anaconda3/lib/python3.6/site-packages/torch/include/c10/core/TensorOptions.h(228): warning: attribute namespace "clang" is unrecognized
/Users/kiwee/anaconda3/lib/python3.6/site-packages/torch/include/c10/core/TensorOptions.h(235): warning: attribute namespace "clang" is unrecognized
/Users/kiwee/anaconda3/lib/python3.6/site-packages/torch/include/c10/util/UniqueVoidPtr.h(69): warning: attribute namespace "clang" is unrecognized
/Users/kiwee/anaconda3/lib/python3.6/site-packages/torch/include/c10/core/Allocator.h(96): warning: attribute namespace "clang" is unrecognized
/Users/kiwee/anaconda3/lib/python3.6/site-packages/torch/include/c10/core/TensorOptions.h(175): warning: attribute namespace "clang" is unrecognized
/Users/kiwee/anaconda3/lib/python3.6/site-packages/torch/include/c10/core/TensorOptions.h(185): warning: attribute namespace "clang" is unrecognized
/Users/kiwee/anaconda3/lib/python3.6/site-packages/torch/include/c10/core/TensorOptions.h(194): warning: attribute namespace "clang" is unrecognized
/Users/kiwee/anaconda3/lib/python3.6/site-packages/torch/include/c10/core/TensorOptions.h(199): warning: attribute namespace "clang" is unrecognized
/Users/kiwee/anaconda3/lib/python3.6/site-packages/torch/include/c10/core/TensorOptions.h(206): warning: attribute namespace "clang" is unrecognized
/Users/kiwee/anaconda3/lib/python3.6/site-packages/torch/include/c10/core/TensorOptions.h(221): warning: attribute namespace "clang" is unrecognized
/Users/kiwee/anaconda3/lib/python3.6/site-packages/torch/include/c10/core/TensorOptions.h(228): warning: attribute namespace "clang" is unrecognized
/Users/kiwee/anaconda3/lib/python3.6/site-packages/torch/include/c10/core/TensorOptions.h(235): warning: attribute namespace "clang" is unrecognized
clang++ -bundle -undefined dynamic_lookup -L/Users/kiwee/anaconda3/lib -arch x86_64 -L/Users/kiwee/anaconda3/lib -arch x86_64 -arch x86_64 build/temp.macosx-10.7-x86_64-3.6/cuda/scatter.o build/temp.macosx-10.7-x86_64-3.6/cuda/scatter_kernel.o -L/usr/local/cuda/lib64 -lcudart -o build/lib.macosx-10.7-x86_64-3.6/torch_scatter/scatter_cuda.cpython-36m-darwin.so
ld: warning: directory not found for option '-L/usr/local/cuda/lib64'
ld: library not found for -lcudart
clang: error: linker command failed with exit code 1 (use -v to see invocation)
error: command 'clang++' failed with exit status 1

Hi,
As far as I know, you need clang 9.1.0 in order to compile/link with CUDA 10 by downgrading the command line tools.

@rusty1s Thank you for your reply. Now I have downgraded my "Command Line Tools" to 9.1,

but still cannot work...

I created a FAQ for common installation errors. Let me know if this fixes your issues.

@rusty1s Thank you for your advice! But as I know, the new version of clang is clang-1000...

A few more thoughts:

Ensure that CUDA ist ser in DYLP-LIBRARY_PATH.
Follow the CUDA installation guide (https://docs.nvidia.com/cuda/index.html) and verify that you can compile wirh nvcc.
It looks like you really need to use clang-

I am really sorry! Can you post the output of ls /usr/local/cuda/lib? Do you have a lib64 dir?

Hey, I noticed that I don't have the lib64 dir, is it necessary? Can you tell me how can I get that, I installed CUDA by following the guide on the official website.

No it is not necessary. It is called lib64 on Linux and lib on macOS.
ld: warning: directory not found for option '-L/usr/local/cuda/lib64'
ld: library not found for -lcudart

The error message suggest that it however expects a lib64 directory. You can maybe create a symlink from lib to lib64.
Alternatively, maybe this thread or this one can help you.

@rusty1s Wow, it works!!! Thanks for your help and patience. I just use sudo ln -s /usr/local/cuda/lib /usr/local/cuda/lib64 , and install all packages with prefix MACOSX_DEPLOYMENT_TARGET=10.13 CC=clang CXX=clang++.

@rusty1s Wow, it works!!! Thanks for your help and patience. I just use sudo ln -s /usr/local/cuda/lib /usr/local/cuda/lib64 , and install all packages with prefix MACOSX_DEPLOYMENT_TARGET=10.13 CC=clang CXX=clang++.

A bit curious about the MACOSX_DEPLOYMENT_TARGET setting: will it cause any differences in the compiling when setting MACOSX_DEPLOYMENT_TARGET=10.13 or MACOSX_DEPLOYMENT_TARGET=10.9?
Why in the official guideline and the github page, both write MACOSX_DEPLOYMENT_TARGET=10.9?
Build (from: https://pytorch.org/get-started/locally/)
git clone --recursive https://github.com/pytorch/pytorch
cd pytorch
MACOSX_DEPLOYMENT_TARGET=10.9 CC=clang CXX=clang++ python setup.py install

On macOS (from: https://github.com/pytorch/pytorch)
export CMAKE_PREFIX_PATH=${CONDA_PREFIX:-"$(dirname $(which conda))/../"}
MACOSX_DEPLOYMENT_TARGET=10.9 CC=clang CXX=clang++ python setup.py install

As far as I know, MACOSX_DEPLOYMENT_TARGET should at least be set to 10.9. There should be no differences.


🛑 Could not initialize platform for 'prod': invalid bit length repeat

How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
v16.18.1
Amplify CLI Version
10.5.2
What operating system are you using?
Mac
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
Had to open up some IAM roles to deal with other issues in the past.
Describe the bug
When running amplify pull after a user on another machine ran amplify push, we receive the message "✖ There was an error initializing your environment. 🛑 Could not initialize platform for 'prod': invalid bit length repeat".
Expected behavior
We should be able to pull our amplify backend environment.
Reproduction steps
Because of the complexity of our project the reproduction steps are unclear. It is not obvious what changes we made may have led to this error. This is the first time we've encountered this issue, and we've tried pulling with several recent versions of the amplify cli.
Project Identifier
224a9650cdd44a1d036bea5bda860dd0
Log output

# Put your logs below this line

2022-12-27T23:26:07.185Z|info : amplify status core  {"yes":false}
2022-12-27T23:26:07.217Z|info : amplify-cli-core.banner-message/index.ts.fetch banner messages from https://aws-amplify.github.io/amplify-cli/banner-message.json({}
2022-12-27T23:26:09.404Z|info : amplify-provider-awscloudformation.display-helpful-urls.showCognitoSandBoxMessage(["meetclubsoda"])
2022-12-27T23:26:15.373Z|info : amplify pull core
2022-12-27T23:26:15.407Z|info : amplify-cli-core.banner-message/index.ts.fetch banner messages from https://aws-amplify.github.io/amplify-cli/banner-message.json({}
2022-12-27T23:26:19.942Z|info : amplify-provider-awscloudformation.zip-util.downloadZip.s3.getFile([{"Key":"[***]rent-[***]ud-[***]d.zip"},null])
2022-12-27T23:26:19.943Z|info : amplify-provider-awscloudformation.aws-s3.s3.getFile([{"Key":"[***]rent-[***]ud-[***]d.zip","Bucket":"[***]ify-[***]bsoda-[***]od-[***]424-[***]ment"}])
2022-12-27T23:26:31.188Z|error : Could not initialize platform for 'prod': invalid bit length repeat
ProjectInitFault: Could not initialize platform for 'prod': invalid bit length repeat
2022-12-27T23:26:39.803Z|info : amplify upgrade core
2022-12-27T23:26:39.836Z|info : amplify-cli-core.banner-message/index.ts.fetch banner messages from https://aws-amplify.github.io/amplify-cli/banner-message.json({}
2022-12-27T23:27:27.974Z|info : amplify pull core
2022-12-27T23:27:28.002Z|info : amplify-cli-core.banner-message/index.ts.fetch banner messages from https://aws-amplify.github.io/amplify-cli/banner-message.json({}
2022-12-27T23:27:31.631Z|info : amplify-provider-awscloudformation.zip-util.downloadZip.s3.getFile([{"Key":"[***]rent-[***]ud-[***]d.zip"},null])
2022-12-27T23:27:31.632Z|info : amplify-provider-awscloudformation.aws-s3.s3.getFile([{"Key":"[***]rent-[***]ud-[***]d.zip","Bucket":"[***]ify-[***]bsoda-[***]od-[***]424-[***]ment"}])
2022-12-27T23:27:49.946Z|error : Could not initialize platform for 'prod': invalid bit length repeat
ProjectInitFault: Could not initialize platform for 'prod': invalid bit length repeat
2022-12-27T23:30:25.669Z|info : amplify version core
2022-12-27T23:33:14.418Z|info : amplify diagnose core  {"send-report":true,"yes":false}
2022-12-27T23:33:14.456Z|info : amplify-cli-core.banner-message/index.ts.fetch banner messages from https://aws-amplify.github.io/amplify-cli/banner-message.json({}

Additional information
If this information is incomplete, please let me know what else I can provide, especially in terms of reproduction steps. This is a major blocker for us as we are unable to pull, push, or otherwise make changes to our backend environment.
Before submitting, please confirm:

[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

We did some digging and found the current-cloud-backend.zip file in our deployment is corrupt. We didn't have bucket versioning enabled. Are we totally screwed?

We got it working by zipping our backend directory and uploading that to replace the #current-cloud-backend.zip in our deployment bucket. Also enabled bucket versioning so this doesn't happen again in the future.


[RHPAM-4619] - Prepare the kogito-images repository for productization

Signed-off-by: spolti<EMAIL_ADDRESS>See: https://issues.redhat.com/browse/KOGITO-4619
Many thanks for submitting your Pull Request :heart:!
Please make sure your PR meets the following requirements:

[x] You have read the contributors' guide
[x] Pull Request title is properly formatted: [KOGITO-XYZ] Subject
[x] Pull Request contains a link to the JIRA issue
[x] Pull Request contains a description of the issue
[x] Pull Request does not include fixes for issues other than the main ticket
[x] Your feature/bug fix has a unit test that verifies it
[ ] You've tested the new feature/bug fix in an actual OpenShift cluster
[x] You've added a RELEASE_NOTES.md entry regarding this change

@spolti, can you rebase?

LGTM
@spolti can you also change the target from docker-build to container-build in OLM workflow? Thanks :)

Sure thing. Nice catch :D

@Kaitou786 updated

CI on OLM is failing with
cekit.errors.CekitError: ('Image build failed, see logs above.', CekitError("Image build failed: 'Head https://registry.redhat.io/v2/ubi8/go-toolset/manifests/1.14.12: unauthorized: Please login to the Red Hat Registry using your Customer Portal credentials. Further instructions can be found here: https://access.redhat.com/RegistryAuthentication'"))

let's use registry.access.redhat.com

more conflicts =/


What is "self.super" ?

https://github.com/TheNexusAvenger/Nexus-Admin/blob/692da3b0f0f62dd268c22db555413fd631eed9cc/src/IncludedCommands/BasicCommands/sword.lua#L33
I see it in almost every commands but what is super ? I didn't find it on the documentation.

super is a feature of Nexus Instance for inheritance.
https://thenexusavenger.github.io/Nexus-Instance/getting-started/classes/nexusobject/#nexusobjectsuper


Make sure tests are triggered with updated dependencies

The key motivation of this workflow is to make sure tests are run with the updated dependencies, but I noticed that wasn't happening.
I tracked it down to the URL referenced in the comment. Also see https://github.com/EndBug/add-and-commit?tab=readme-ov-file#the-commit-from-the-action-is-not-triggering-ci The issue described there is not specific to that workflow action, it equally applies to our inline definition of git-push.
This should do the trick.

Reopening to see if that gets tests running again.


Update setup_kubernetes_auth.sh

Hi @NavikaAgarwal there's no acceptable changes in this PR so we are closing it. This repo does not accept community contributions.


Codegen Error: Syntax Error

I have an existing api I'm trying to integrate into a new application and I'm running into an issue when trying to run codegen. Specifically the error is: Syntax Error: Expected Name, found }. I don't think my schema has any errors as it doesn't complain in the appsync console and I can access it outside this. Is this an issue with the code generation itself or something in my schema?
Full Error:
✔ Downloaded the schema
⠋ Generating GraphQL operations⠋ Generating.../graphql/queries.graphql: Field "posts" argument "limit" of type "Int!" is required but not provided.
.../graphql/queries.graphql: Field "videos" argument "limit" of type "Int!" is required but not provided.
.../graphql/queries.graphql: Field "stories" argument "limit" of type "Int!" is required but not provided.
.../graphql/queries.graphql: Field "podcasts" argument "limit" of type "Int!" is required but not provided.
.../graphql/queries.graphql: Field "posts" argument "limit" of type "Int!" is required but not provided.
.../graphql/queries.graphql: Field "videos" argument "limit" of type "Int!" is required but not provided.
.../graphql/queries.graphql: Field "stories" argument "limit" of type "Int!" is required but not provided.
.../graphql/queries.graphql: Field "podcasts" argument "limit" of type "Int!" is required but not provided.
.../graphql/queries.graphql: Field "posts" argument "limit" of type "Int!" is required but not provided.
.../graphql/queries.graphql: Field "videos" argument "limit" of type "Int!" is required but not provided.
.../graphql/queries.graphql: Field "stories" argument "limit" of type "Int!" is required but not provided.
.../graphql/queries.graphql: Field "podcasts" argument "limit" of type "Int!" is required but not provided.
.../graphql/queries.graphql: Variable "$users" of type "String!" used in position expecting type "[String!]!".
.../graphql/queries.graphql: Variable "$users" of type "String!" used in position expecting type "[String!]!".
.../graphql/queries.graphql: Field "posts" argument "limit" of type "Int!" is required but not provided.
.../graphql/queries.graphql: Field "videos" argument "limit" of type "Int!" is required but not provided.
.../graphql/queries.graphql: Field "stories" argument "limit" of type "Int!" is required but not provided.
.../graphql/queries.graphql: Field "podcasts" argument "limit" of type "Int!" is required but not provided.
2018-10-05T04:41:59.242Z - error: uncaughtException: Syntax Error: Expected Name, found } (146:17)
  144 |   )
  145 |  {
> 146 |                 }
      |                 ^
  147 | }
  148 |   mutation UnlikePost   (
  149 |       $input:PostLikeInput! date=Thu Oct 04 2018 21:41:59 GMT-0700 (PDT), pid=68157, uid=501, gid=20, cwd=/LOCAL_DIRECTORY, execPath=/Users/username/.nvm/versions/node/v8.12.0/bin/node, version=v8.12.0, argv=[/Users/username/.nvm/versions/node/v8.12.0/bin/node, /Users/username/.nvm/versions/node/v8.12.0/bin/amplify, codegen], rss=151486464, heapTotal=116416512, heapUsed=80099272, external=1466198, loadavg=[2.62255859375, 2.31982421875, 2.15966796875], uptime=695325, trace=[column=493<EMAIL_ADDRESS>function=n, line=1, method=null, native=false, column=35789<EMAIL_ADDRESS>function=Object.parse, line=1, method=parse, native=false, column=19<EMAIL_ADDRESS>function=Object.parse$2 [as parse], line=7138, method=parse$2 [as parse], native=false, column=23<EMAIL_ADDRESS>function=coreFormat, line=10398, method=null, native=false, column=16<EMAIL_ADDRESS>function=format, line=10570, method=null, native=false, column=12<EMAIL_ADDRESS>function=formatWithCursor, line=10582, method=null, native=false, column=15<EMAIL_ADDRESS>function=null, line=34924, method=null, native=false, column=12<EMAIL_ADDRESS>function=Object.format, line=34943, method=format, native=false, column=19, file=/Users/kaustavg/amplify-launch/amplify-cli/packages/amplify-graphql-docs-generator/src/index.ts, function=format, line=117, method=null, native=false, column=10, file=/Users/kaustavg/amplify-launch/amplify-cli/packages/amplify-graphql-docs-generator/src/index.ts, function=renderOps, line=85, method=null, native=false], stack=[SyntaxError: Syntax Error: Expected Name, found } (146:17),   144 |   ),   145 |  {, > 146 |                 }      ,       |                 ^,   147 | },   148 |   mutation UnlikePost   (,   149 |       $input:PostLikeInput!,     at n (/Users/username/.nvm/versions/node/v8.12.0/lib/node_modules/@aws-amplify/cli/node_modules/prettier/parser-graphql.js:1:493),     at Object.parse (/Users/username/.nvm/versions/node/v8.12.0/lib/node_modules/@aws-amplify/cli/node_modules/prettier/parser-graphql.js:1:35789),     at Object.parse$2 [as parse] (/Users/username/.nvm/versions/node/v8.12.0/lib/node_modules/@aws-amplify/cli/node_modules/prettier/index.js:7138:19),     at coreFormat (/Users/username/.nvm/versions/node/v8.12.0/lib/node_modules/@aws-amplify/cli/node_modules/prettier/index.js:10398:23),     at format (/Users/username/.nvm/versions/node/v8.12.0/lib/node_modules/@aws-amplify/cli/node_modules/prettier/index.js:10570:16),     at formatWithCursor (/Users/username/.nvm/versions/node/v8.12.0/lib/node_modules/@aws-amplify/cli/node_modules/prettier/index.js:10582:12),     at /Users/username/.nvm/versions/node/v8.12.0/lib/node_modules/@aws-amplify/cli/node_modules/prettier/index.js:34924:15,     at Object.format (/Users/username/.nvm/versions/node/v8.12.0/lib/node_modules/@aws-amplify/cli/node_modules/prettier/index.js:34943:12),     at format (/Users/kaustavg/amplify-launch/amplify-cli/packages/amplify-graphql-docs-generator/src/index.ts:117:19),     at renderOps (/Users/kaustavg/amplify-launch/amplify-cli/packages/amplify-graphql-docs-generator/src/index.ts:85:10)]

Schema downloaded from appsync console:
GraphQL
Introspection that's downloaded during codegen:
JSON
graphqlconfig.yml:
projects:
  apiName:
    schemaPath: graphql/schema.json
    includes:
      - graphql/**/*.graphql
    excludes:
      - amplify/**
    extensions:
      amplify:
        graphQLApiId: **API_ID**
        codeGenTarget: swift
        generatedFileName: API.swift
        docsFilePath: graphql
        region: us-east-1

@arvinkx What version of amplify-cli do you have installed? You get it by running amplify -v.
Some thing odd that I see in your schema is that the return type for some of the mutations are String, is that intentional? For instance
  clearVideoVote(authorId: String!, id: ID!): String
  deletePodcast(input: DeletePodcastInput!): String
  deletePost(input: DeletePostInput!): String
  deleteStory(input: DeleteStoryInput!): String
  deleteVideo(authorId: String!, id: ID!): String
  downvoteVideo(authorId: String!, id: ID!): String
  followUser(user: String!): String!
  likePodcast(input: PodcastLikeInput!): String
  likePost(input: PostLikeInput!): String!
  removeComment(commentId: ID!, parentId: ID!): String
  reportContent(authorId: String!, id: ID!, type: String!): String
  reportPostAdImpression(id: ID!): String
  reportVideoView(authorId: String!, id: ID!): String
  unfollowUser(user: String!): String!
  unlikePodcast(input: PodcastLikeInput!): String
  unlikePost(input: PostLikeInput!): String!
  upvoteVideo(authorId: String!, id: ID!): String

When the mutation returns a Scalar type you can't use the return value from it
for   clearVideoVote(authorId: String!, id: ID!): String your statement will have to be
 mutation ClearVideoVote   (
      $authorId:String!,
      $id:ID!
  )
{
    clearVideoVote  (
      authorId:$authorId,
      id:$id
    )
}

I'm running v0.1.27 - is the reason codegen is having issues because of the use of String return values? It was intentional but if that's the issue it can be changed.

is the reason codegen is having issues because of the use of String return values

Yes, but I am going update codegen to support this use case. Thanks for reporting it

@yuth Thanks for the fix, I'm running into a possibly related issue. The generation of the graphql files seem to complete now but the validation fails with the error Validation of GraphQL query document failed. I believe the issue is related to the warnings in the original error message above about "limit" not being provided. I've included a snippet of the schema below, it looks like the generation isn't adding the extra arguments (limit and nextToken) for the posts, video, stories, etc. Are arguments in response fields not supported?
Actual Schema
type User {
    username: String!
    preferred_username: String!
    picture: String!
    email: String!
    name: String!
    family_name: String!
    posts(limit: Int!, nextToken: String): PostConnection
    videos(limit: Int!, nextToken: String): VideoConnection
    stories(limit: Int!, nextToken: String): StoryConnection
    podcasts(limit: Int!, nextToken: String): PodcastConnection
    notifications: NotificationConnection
    followerCount: Int!
    followingCount: Int!
    followerIds: [String!]!
    followingIds: [String!]!
    followingTags: [String!]
}

What's being generated (this mutation returns a User):
mutation UpdateFollowingTags($tags: String!) {
  updateFollowingTags(tags: $tags) {
    username
    preferred_username
    picture
    email
    name
    family_name
    posts {
      items {
        id
        date
        updatedAt
        title
        authorId
        content
        likesCount
        video
        isLiked
      }
      nextToken
    }
    videos {
      items {
        id
        authorId
        date
        viewCount
        category
        upvotesCount
        upvotes
        downvotesCount
        downvotes
        title
        alternativeTitle
        thumbnailUrl
        alternativeThumbnailUrl
        description
        videoUrl
        videoLength
        tags
      }
      nextToken
    }
    stories {
      items {
        id
        date
        authorId
        image
        video
      }
      nextToken
    }
    podcasts {
      items {
        id
        date
        updatedAt
        url
        authorId
        description
        likesCount
        isLiked
      }
      nextToken
    }
    notifications {
      items {
        userId
        notificationId
        date
        likes
        newLikesCount
        followers
        newFollowersCount
      }
    }
    followerCount
    followingCount
    followerIds
    followingIds
    followingTags
  }
}


Publish decklist, decklist view, decklist search, card search, card reviews and keyowords tooltips translated

When installing the assets, I have this exception:

PHP Catchable fatal error:  Argument 5 passed to AppBundle\Services\CardsData::__construct() must be an instance of Symfony\Component\Translation\DataCollectorTranslator, instance of Symfony\Bundle\FrameworkBundle\Translation\Translator given, called in /home/alsciende/thronesdb/app/cache/prod/appProdProjectContainer.php on line 427 and defined in /home/alsciende/thronesdb/src/AppBundle/Services/CardsData.php on line 18

Fixed with 46138b722c0fc425ad6866d58b7963519894cf12. Weird.


issue16868

https://github.com/zulip/zulip/issues/16868
Testing plan:
Yes , Tested it

Feel free to discuss :)   ;   Is this enough or any thing need to be added on ??

Thanks for working on this @SushanthReddyManda.
It is recommend not to make PRs from a master branch, you should make a separate branch for each PR. (Read https://zulip.readthedocs.io/en/latest/git/pull-requests.html)
Also update the commit message according to Zulip commit message guidelines: https://zulip.readthedocs.io/en/latest/contributing/version-control.html#commit-messages, and PR should also have a descriptive title.

Thanks !!  , I will again pull request as mentioned :)


Update README.md

@JoyLiuc PTAL

 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.You have signed the CLA already but the status is still pending? Let us recheck it.

LGTM, but it needs @davies review too.


Exercise 3 - Recommended tcpdump version is patched

As far as I can tell, tcpdump at tag 4.9.2 contains the patch that fixes the target CVE.
wget https://github.com/the-tcpdump-group/tcpdump/archive/refs/tags/tcpdump-4.9.2.tar.gz\n
tar xf tcpdump-4.9.2.tar.gz
grep -n 'ND_TCHECK\(bp->bp_flags\)' tcpdump-tcpdump-4.9.2/print-bootp.c
325:    ND_TCHECK(bp->bp_flags);

ref: https://github.com/the-tcpdump-group/tcpdump/commit/29e5470e6ab84badbc31f4532bb7554a796d9d52

Confirm that it has been repaired.
Use the file

After repeated operations, my libpcap version is different from , not sure if it is related to this.

@epi052 that's true. The commit that fixes the bug is the following
Thanks for the information 👍
As thanks, you have been added to the "Thanks" section.

The README stills mentions tcpdump 4.9.2 that contains the patch for the oob read.

The version is still incorrect in the readme ...


Fix project role displaying issue

Coverage remained the same at 55.804% when pulling ce19ba28891ad3329451f985eb8da46916e82eb9 on steven-zou:master into 2a0fdc4ed209d82a54ae8133c19316d73d400ce1 on vmware:master.


automation, e2e: Introduce VM latency scripts and improve existing ones.

The PR includes the following changes:
checkup-vm-latency, automation: Introduce e2e test deploy helpers
automation, e2e: Simplify binary installation
automation: Use the script full path
automation: Use ${PWD} instead of ./
automation, e2e: Fix binary path comparison

change: Rebase

@EdDev WDYT about also deploying Multus?


fix action type for default action

Contributor checklist

[ ] Bug fixes include regression tests
[ ] Features include unit/acceptance tests

Action type should be based on default action selected instead of being nil

🚀 Thank you for your contribution! 🚀


How to pass variable and files from local

Describe the bug
I was wondering how do i pass my local files and the variables to the docker at the time of loading the pod
docker run -v /path/to/local/data:/app/data -e MY_VARIABLE=my_value your_image_name
I wanted to pass this file loaction : -v /path/to/local/data:/app/data
And the Variable : -e MY_VARIABLE=my_value
How do i do it here? As i think that it uses the command docker run your_image_name directly to run the image to load template.
Is there any parameter in runpod.create_pod() where i can pass this?

Use the env parameter to add environment variables as key, value pairs.

Use the env parameter to add environment variables as key, value pairs.

thanks for the reply, can please also tell me how do i pass my local file location too.

You can not pass files in during pod creation, the easiest would be to create a custom docker image which has the files included and then launch a pod with that image. Alternatively you can use runpodctl once the pod is running to transfer in files.


[Feature Request]: Support common MFAs for Hop Web

What would you like to happen?
For Hop Web - our team would like to use Hop Web but need to be able to use MFA as a minimum for sufficient platform security. It would be helpful to have configuration options to enable common MFA tools that allow secure logins using these tools.
Issue Priority
Priority: 3
Issue Component
Component: Hop Web

Hop Web uses tomcat so you should be able to leverage all available tomcat options to limit access to the application.

Thanks for taking a look Hans. Maybe this is better described as a documentation request or a how to. The basic auth howto provided by hiromuhota for PDI was an easy to follow implementation and discussed some of the challenges with file system permissions. We're working with Okta and I've spent some time evaluating the effort and haven't made great progress (I'm not a Java Dev primarily).
I saw that the Spring framework is well supported for MFA's such as OKTA (the integration we're pursuing). Maybe there's an opportunity to provide more direction for what would be a more common task for enterprise adoptions.

We have posted a guide to add authentication to Hop Web here, it also points to the tomcat documentation on how to add other realms.
As far as I can see some extra development would be needed to support OKTA, as it is not part of the default realms supported by tomcat. Unfortunately from a community perspective we do not have access to OKTA making it hard for us to build and test such an implementation.

Thanks for the additional resources. I have enabled basic auth (using the guide you mentioned) and it works great.
Maybe a better starting point would be something like Google Auth.


fix: remove default dynamics

Implements https://github.com/ComPWA/expertsystem/pull/395 and removes the default dynamics.
https://github.com/ComPWA/tensorwaves/blob/ca494ea48a552b65cf1de40fb88e188ca20450dc/src%2Ftensorwaves%2Fphysics%2Fhelicity_formalism%2Famplitude.py#L159-L160
That was an implementation that seemed convenient, but modified the dynamics section of the input AmplitudeModel.
Note that a long-term fix should come through #172 and https://github.com/ComPWA/expertsystem/issues/22

Note: 10e115e has to be reverted once https://github.com/ComPWA/expertsystem/pull/395 is through and expertsystem==0.6.4 is released


Assign multiple users for a single task in playbooks

It would be great to be able to assign one or multiple users for a single task simultaneously in playbooks since it is very common to assign several people for one task at the same time. Currently, only a single user can be assigned for one task.

Thanks for this suggestion, @ikjnv! Do you imagine any of these users can complete the task, or do they all need to "complete" it for themselves? What other interactions would you find useful when multiple assignees are defined for a task?

@lieut-data It would make sense if any of these assigned users can complete the task for everybody, not only for themselves. Regarding other interactions, I haven't thought about other features. Being able to assign multiple people is what I thought was missing.

What you described is already the current behaviour, any participant can check off any task regardless if it is assigned to them. Could you help us understand the nuances that you had in mind besides that?

@itao Currently, I don't think that it is possible to assign several people for a single task in playbooks. What I meant was that it would be better if multiple users "simultaneously" can be assigned for a single task in playbook. But it looks impossible at the moment.

s.

IMO, in your question(what is the goal to have owners?) by saying owners, I hope you meant assignee/assignees, let me know if I'm wrong. The main behind this is that when someone is assigned to a specific task then the assigned user gets notified about it(see pic below) and can act accordingly.

And, when several people are assigned for the same task, which is the idea/feature I'm trying to explain and propose, all of them get notified and can work collaboratively. Additionally, everybody knows who is doing what(structure & organization), whose responsibility to do a specific task in case some kind of questions arise along the way or everybody knows whom to address their questions/concerns to if something happens unexpectedly. Let me know if you have any further questions.

when several people are assigned for the same task ... all of them get notified

Gotcha! This was key, thank you for clarifying. Let us think on this for a bit, as we're also exploring an initiative called Threads Everywhere that would have some overlap as it tries to bring interaction parity between message post and tasks (ie. following, @ mention, comment thread, notifications)

Hey guys,
any news on that? It would be really handy for us as well

Hi @bokkabonga! I regret that our priorities have shifted away from this feature request towards other efforts. There's no plans currently on the roadmap to add this functionality.


Added experimental vicuna 1.1+ support

As discussed in #262 and #261 , I implemented support for Vicuna 1.1+, following the original code as close as possible.
This should be even more flexible than Vicunas own finetuning/training code, as my code allows for flexible system messages.
Dataset should look like
[{"conversation":{"from": "human", "value": "Who are you?"}, {"from": "gpt", "value": "I am Vicuna"},...}]

as .jsonl file; the first "from" can be "system" instead and will be used as system message if present.
Submitting as draft as the code is still untested, but will report back.

I just finished the simple-instruct version and I was going to send it. Luckily I saw this before creating the PR. Waiting to see the results

Everything should work now, a large finetuning of Vicuna 13b v.1.3 with this implementation is currently in progress and I am excited for the results 💯 .

I finetuned Vicuna 1.3 13B sucessfully with this implementation so should be ready for merging.
There is some duplicate code and/or some duplicate functionality, but as I understood, the plan is to make prompt_strategies modular / independent of each other and thus an implementation like this one, that is very close to the original refence implementation and more or less self-contained should be in line with this idea?

Hello, thank you for your implementation of Vicuna dataset processing.
May I ask you to specify which is the correct dataset type to use?
In your implementation, I found:
"Use dataset type: orcamini in config.yml to use this prompt style."
but I can't find the orcamini config anywhere.

One note, there was a recent PR to improve tokenize speed. However, when I apply your branch to the current main with a normal sharegpt dataset, I would get the below error. I am unclear whether it's due to that PR or some mismatch with yours.
error message log
Traceback (most recent call last):
  File "/workspace/axolotl/scripts/finetune.py", line 356, in <module>
    fire.Fire(train)
  File "/workspace/axolotl/venv/lib/python3.10/site-packages/fire/core.py", line 141, in Fire
    component_trace = _Fire(component, args, parsed_flag_args, context, name)
  File "/workspace/axolotl/venv/lib/python3.10/site-packages/fire/core.py", line 475, in _Fire
    component, remaining_args = _CallAndUpdateTrace(
  File "/workspace/axolotl/venv/lib/python3.10/site-packages/fire/core.py", line 691, in _CallAndUpdateTrace
    component = fn(*varargs, **kwargs)
  File "/workspace/axolotl/scripts/finetune.py", line 226, in train
    train_dataset, eval_dataset = load_prepare_datasets(
  File "/workspace/axolotl/src/axolotl/utils/data.py", line 352, in load_prepare_datasets
    dataset = load_tokenized_prepared_datasets(
  File "/workspace/axolotl/src/axolotl/utils/data.py", line 268, in load_tokenized_prepared_datasets
    samples = samples + list(d)
  File "/workspace/axolotl/src/axolotl/datasets.py", line 41, in __iter__
    self.dataset.map(
  File "/workspace/axolotl/venv/lib/python3.10/site-packages/datasets/arrow_dataset.py", line 580, in wrapper
    out: Union["Dataset", "DatasetDict"] = func(self, *args, **kwargs)
  File "/workspace/axolotl/venv/lib/python3.10/site-packages/datasets/arrow_dataset.py", line 545, in wrapper
    out: Union["Dataset", "DatasetDict"] = func(self, *args, **kwargs)
  File "/workspace/axolotl/venv/lib/python3.10/site-packages/datasets/arrow_dataset.py", line 3087, in map
    for rank, done, content in Dataset._map_single(**dataset_kwargs):
  File "/workspace/axolotl/venv/lib/python3.10/site-packages/datasets/arrow_dataset.py", line 3441, in _map_single
    example = apply_function_on_filtered_inputs(example, i, offset=offset)
  File "/workspace/axolotl/venv/lib/python3.10/site-packages/datasets/arrow_dataset.py", line 3344, in apply_function_on_filtered_inputs
    processed_inputs = function(*fn_args, *additional_args, **fn_kwargs)
  File "/workspace/axolotl/src/axolotl/prompt_strategies/vicuna.py", line 78, in tokenize_prompt
    input_ids = self.tokenizer(
  File "/workspace/axolotl/venv/lib/python3.10/site-packages/transformers/tokenization_utils_base.py", line 2577, in __call__
    encodings = self._call_one(text=text, text_pair=text_pair, **all_kwargs)
  File "/workspace/axolotl/venv/lib/python3.10/site-packages/transformers/tokenization_utils_base.py", line 2683, in _call_one
    return self.encode_plus(
  File "/workspace/axolotl/venv/lib/python3.10/site-packages/transformers/tokenization_utils_base.py", line 2756, in encode_plus
    return self._encode_plus(
  File "/workspace/axolotl/venv/lib/python3.10/site-packages/transformers/tokenization_utils.py", line 652, in _encode_plus
    return self.prepare_for_model(
  File "/workspace/axolotl/venv/lib/python3.10/site-packages/transformers/tokenization_utils_base.py", line 3235, in prepare_for_model
    encoded_inputs = self.pad(
  File "/workspace/axolotl/venv/lib/python3.10/site-packages/transformers/tokenization_utils_base.py", line 3040, in pad
    encoded_inputs = self._pad(
  File "/workspace/axolotl/venv/lib/python3.10/site-packages/transformers/tokenization_utils_base.py", line 3425, in _pad
    encoded_inputs["attention_mask"] = encoded_inputs["attention_mask"] + [0] * difference
OverflowError: cannot fit 'int' into an index-sized integer

Hm strange, will test this out again (and also double check tokenization).
Can you put this PR in draft mode again? I am currently working on llama2 chat and will try to fix this afterwards...

Making those modifications fixed it. However, I'm getting a few tokenization mismatch, a lot being cur_len = total_len + 1. Is this normal?

I found out the same, try to set use_fast=False in the tokenizer and see if it is related to the fast tokenizer

@valeman100 , thanks for the response. No, it didn't. I'm testing this with llama-2-7b-hf with convo sharegpt dataset for reference.

I will check this again if Llama2 is running.
Just fyi, yesterday I almost got crazy testing #296  because I always got exactly these tokenization mismatches by one when running a test-finetune but not when testing locally.
This was due to my config.yml which included:
special_tokens:
  bos_token: "<s>"
  eos_token: "</s>"
  unk_token: "<unk>"
  ```;
removing these everyting works fine.

These were also included in my config during my successful Vicuna finetune, so could be related to that.

I added a pad_token [PAD] as the llama2 doc states and ref here #294 .
Also, my eval turns to NAN... Could be due to all those misses..

I added a pad_token [PAD] as the llama2 doc states and ref here #294 .
Also, my eval turns to NAN... Could be due to all those misses..
Edit: sharegpt:chat works for me though.

I am bit confused, did you mean #296 ? As there, I added the pad-token manually, but you are right that you would need to include it elswhere excep in the prompting_strategy itself.
I will check Vicuna tokenization and will try to bring this in a clean, ready-to-merge state with test fixtures at beginning of next week.

have you had a chance to look at this @jphme?

@flexchar , sorry if this is late. We have imported fastchat library, so you can now use the same as fastchat's convo.
You can check the docs
datasets:
  - path:
    type: sharegpt
    conversation:  # Optional[str] fastchat conversation type, only used with type: sharegpt

Vicuna 1.1 should be just sharegpt, but you can even use other's by modifying conversation.

I checked this back in the day, for the llama2_chat code, and the problem with the mismatch of the tokens happens because the tokenizer was initialized incorrectly. See the following https://github.com/huggingface/transformers/pull/24565. If you are adding new tokens during the retraining you need to be aware of this flag and set it properly.  Axolotl can already set this flag https://github.com/OpenAccess-AI-Collective/axolotl/issues/305. (The llama2_chat has some other issues perhaps I should open another issue to address them)

Thank you for following up @NanoCode012. I really appreciate that. It's still interesting to try but these days I'm moving onto Mistral and my preferred flavour of model (MistralOrca) uses ChatML template. I see alpaca_w_system.load_open_orca_chatml is now available for that. :)

Thank you for following up @NanoCode012. I really appreciate that. It's still interesting to try but these days I'm moving onto Mistral and my preferred flavour of model (MistralOrca) uses ChatML template. I see alpaca_w_system.load_open_orca_chatml is now available for that. :)

For conversation datasets, you actually should be able to do:
datasets:
  - path:
    type: sharegpt
    conversation: chatml

if I´m not mistaken, see https://github.com/OpenAccess-AI-Collective/axolotl/blob/490923fb78e0646c2c0ba427628a0daa72b86996/src/axolotl/prompt_strategies/sharegpt.py#L11 .
Sorry I totally forgot about this PR and think it can be closed/deleted for good :) .


Use instance arguments for has-level n

This pull request changes the library in order to use instance arguments to make Agda automatically deduce arguments of type has-level n A.
In particular, when using a function like Trunc-elim, SetQuot-elim, prop-has-all-paths, and so on, you don’t need to give the proof that the thing is of the appropriate truncation level, Agda will figure it out automatically most of the time. If Agda doesn’t figure it out, you can always give it explicitely using instance arguments syntax {{ arg }}.
Note in particular that Agda probably won’t figure it out if it uses raise-level or Trunc-preserves-level or a few others, but most of the time it does work.
Another notable change (needed for instance arguments to work) is that I changed the definition of has-level n A (see core/lib/NType.agda) and it now does not reduce anymore. In practice that means that:

Given p : is-contr A, use contr-center p and contr-path p instead of fst p and snd p
Given p : has-level (S n) A and a b : A, use has-level-apply p a b instead of p a b to get an element of type has-level n (a == b)
Given q : Σ A (λ x → ((y : A) → x == y)), use has-level-make q in order to get an element of type is-contr A
Given f : (a b : A) → has-level n (a == b), use has-level-make f in order to get an element of type has-level (S n) A

Done.
I also don’t like has-level-make but I didn’t have any better idea. has-level-in is better :)


Added badges for Travis and Coveralls

This PR simply adds badges for Travis and Coveralls to the README.
Right now the build status is unknown but will updated the PR is merged and then the badges should go green!

thank you @jlstevens


make rich_text_link text optional

The text property for the link rich text section element is optional. When excluded, the URL is also used as the inner text.
Ref: https://api.slack.com/reference/block-kit/blocks#link-element-type

Oh, good catch; thank you!


Use the correct certificate reconciler

Changes

The certificate reconciler should use the local reconciler instead of the one from the pkg repo
This local reconciler uses the filtered informer that the pkg one doesn't support

/kind bug

/lgtm
/approve


feat: new e2e automated test RHOAS (Kafka instances)

Update tests are added. The list and delete tests already existed previously.
Jira: https://issues.redhat.com/browse/MGDSTRM-11006

just little changes,
but in addition to this please: add comment that PRIMARY_USERNAME is now requiered env variable in src/test/java/io/managed/services/test/rhoas/KafkaRhoasBasicTests.java
also make a PR to mas-ci specifying that env variable PRIMARY_USERNAME should be read from the vault as well.

Hi @henryZrncik do you mean SECONDARY_USERNAME instead of PRIMARY_USERNAME in this comment?

just little changes,
but in addition to this please: add comment that PRIMARY_USERNAME is now requiered env variable in src/test/java/io/managed/services/test/rhoas/KafkaRhoasBasicTests.java
also make a PR to mas-ci specifying that env variable PRIMARY_USERNAME should be read from the vault as well.

Hi @henryZrncik do you mean SECONDARY_USERNAME instead of PRIMARY_USERNAME in this comment?

If it's so, here we have the PR: https://gitlab.cee.redhat.com/mk-ci-cd/mas-ci/-/merge_requests/855


Error when attempting to login via Microsoft Account

Just click Login, Click Microsoft Account and get this url:
https://login.live.com/err.srf?lc=1033#error=invalid_request&error_description=The+provided+value+for+the+input+parameter+'redirect_uri'+is+not+valid.+The+expected+value+is+'https://login.live.com/oauth20_desktop.srf'+or+a+URL+which+matches+the+redirect+URI+registered+for+this+client+application.&state=CfDJ8KDKGBQpwThNmiIGCRNSeBxW2NOG9G3UvzinidSXRsDJDvxDQn_oxLpyemb7n812MS4xyTODTzNDpZYazyUlD9baSlIbC9TbTK1LFetpNePklfhQBe1I7hryWtSwYChdAz1ehazs5-XqFxhl7tLsLuDjoZoG3hIK2AAk-hfqIKOrptBfPmlsnKw345Qr4U7sAKSJiKfmKAfZWupN_5WimM7sPk8kQheibmckfOMPjq2mYFx09e05WyMLQkv_j8PAtmRpKPy5KZWieWfPdh3aJJr1-50LzRieHO3Z4NVV6_IHpHy26G5TAMqhNhqZwFS0Og
with this error:

@bcbeatty this happens on both -d and -mvp and several builds.  Any ideas?

It may have something to do with registering the proper RedirectUrl in the apps' settings:
https://account.live.com/developers/applications/
A walk through is posted here: http://www.benday.com/2014/02/25/walkthrough-asp-net-mvc-identity-with-microsoft-account-authentication/
More information can be found here: http://stackoverflow.com/questions/12619532/the-provided-value-for-the-input-parameter-redirect-uri-is-not-valid

@bcbeatty okay I will look into it.  What url did you test this with your own deployment to azure?  Hopefully I can just take that and change the host name or something similar.

thanks @bcbeatty
problem solved
The issue was that we were entering this url as approved redirect and it actually needs to be
http://allready-mvp.azurewebsites.net/account/externallogincallback
http://allready-mvp.azurewebsites.net/signin-microsoft
Fixed on -mvp and when I get a moment I will create as separate app and fix it on -d

also just fixed on -d, I had to create another app.  so it is done and live

:+1:


Unable to run the script

Tried to run the script on a Mac but failed to do so. Attached the screenshot.

What's it's pointing out is a type annotation that is valid syntax in Python 3. So make sure to run it in Python 3+

Well, I tried that too. (see below) BTW I have installed Homebrew.

I mentioned in the video that this required PyAudio but unfortunately neglected to show the installation process. Sorry.
From terminal, use the following commands:
brew install portaudio
pip install pyaudio
using the pip corresponding to the python3 installation.
Source: https://people.csail.mit.edu/hubert/pyaudio/

I actually realized about that when I was trying earlier. Pyaudio is already installed in my computer.

From the file path, it seems it was installed for Python 2.7 but not for 3. In the command, try replacing pip with pip3 or whatever name corresponds to the correct installation.

It worked. Thank you so very much! 👍 🥇


Separete general commands and commands per step

add json template "step": {number of step}
It doesn't have is a general step something like aurora command

@marti1125 any update on this, or thoughts about how you'd like to approach this? I imagine that once this is completed, it will be easier to tackle #75

Done!


debug_mode documentation is wrong

Debug mode can't be turned on by setting the variable debug_mode to true. I tried
debug_mode: on
debug_mode: true
debug_mode: 'on'
debug_mode: 'true'
debug_mode: 1

But nothing worked.
So I looked at the source code and found debug-mode {{ "on" if cookiecutter.debug_mode == "True" else "off" }}
So the documentation is wrong.

Unfortunately I can't create a branch here to fix the documentation


Port Methane to 1.20.3

we should ideally use the new 1.20.3 popup system, but I'm lazy.

libMCdev is now working on 1.20.3.

Methane is hard-blocked by dependencies that i don't have control over.

Once mod menu 9.0.0 is stable, Methane will be updated.

hopefully Methane 1.20.3+ should work as-is.


Wallet crashing after sending money from multiple addresses

Machine: Windows 7
Scenario
Use coin control and select 10 different addresses (it may not need 10 addresses exactly).
The wallet will display the amount you can send by subtracting the transaction fees.
Use this amount and send the money to a valid address.
The wallet say that there is not enough money for the transaction, 0.001 XPY is missing.
Subtract 0.001 XPY from the amount you expect to send (the wallet will display in red that there will be 0.001 XPY left.)
Validate the transaction (there will be enough fees for the transaction now).
Expected behaviour
The transaction is finalized.
Current behaviour
The wallet is crashing.

Most likely a duplicate of #456

There is not enough details on the 456 so it may not be the same bug.

@Yoldark34 there's in fact a debug log so in some respect there is more detail :P
You'll note I didn't mark it as a duplicate I just said it most likely was.
That can be confirmed by checking the last thing in the debug log to see if it is crashing in the same spot.

I will reproduce it and give you the log :+1: .

@Yoldark34 thank you.

Ok, i did not reproduce the bug from 19 adresses but i did it with 30 addresses.
debug_crash.log.txt

The crashed transaction is taking a lot of time to validate, but did validate after 1 hour normally.

Yeah see it's crashing when it attempts to relay the wtx which is what the other logs have shown. Still trying to work out an exact cause at this time...

:+1:

This does look the same to me. I got as far as it crashing when it attempts to relay the wtx as well but haven't made any progress as to why this happens to the larger transactions.


Make Grafana only accessible locally

Hi, I saw that in the docs, you describe a way to use the firewall to make the Grafana port (3000) be only accessible on the <IP_ADDRESS> interface and not on the <IP_ADDRESS> interface. But I think this could be easier achieved with this change I'm proposing here. I tried it out on my staking setup and it seems to work exactly as intended: Grafana is available on <IP_ADDRESS>:3000 but not externally, which means you must use SSH tunneling to access it.
I got the idea from here: https://earthly.dev/blog/youre-using-docker-compose-wrong/#problem-2-youre-binding-ports-on-the-hosts-<IP_ADDRESS>

Yep that'd work but would break access from LAN, which is a legitimate use case. I am inclined to leave grafana-shared as-is because solo staking at home is more common than solo staking in the cloud; and for cloud, using traefik instead of grafana-shared is the far better solution to begin with.

I would entertain a PR with grafana-localhost.yml with these contents, so people can choose.

I am inclined to leave grafana-shared as-is because solo staking at home is more common than solo staking in the cloud; and for cloud, using traefik instead of grafana-shared is the far better solution to begin with.

I see. Makes sense.
I created a new file now, grafana-localhost.yml, as you mentioned in your second comment, in case you want to accept that change. I can also squash the commits if you want.


web-bluetooth: Use gatt.connect instead of connectGATT

R=@jeffposnick
The warning is shown when use connectGATT, it's deprecated.
Warning message:

'BluetoothDevice.connectGATT' is deprecated and will be removed in M52, around August 2016. Please use 'BluetoothDevice.gatt.connect' instead. See https://www.chromestatus.com/feature/5264933985976320 for more details.

Pleasw do not merge yet as chrome 50 didn't reach stable channel yet.
On Fri, Mar 11, 2016, 6:13 AM Takuya Beppu<EMAIL_ADDRESS>wrote:

R=@jeffposnick https://github.com/jeffposnick
The warning is shown when use connectGATT, it's deprecated.
Warning message:
'BluetoothDevice.connectGATT' is deprecated and will be removed in M52,
around August 2016. Please use 'BluetoothDevice.gatt.connect' instead. See
https://www.chromestatus.com/feature/5264933985976320 for more details.

You can view, comment on, or merge this pull request online at:
https://github.com/GoogleChrome/samples/pull/314
Commit Summary

Use gatt.connect instead of connectGATT

File Changes

M web-bluetooth/battery-level.js
https://github.com/GoogleChrome/samples/pull/314/files#diff-0 (2)
M web-bluetooth/characteristic-properties.js
https://github.com/GoogleChrome/samples/pull/314/files#diff-1 (2)
M web-bluetooth/get-characteristics.js
https://github.com/GoogleChrome/samples/pull/314/files#diff-2 (2)
M web-bluetooth/notifications.js
https://github.com/GoogleChrome/samples/pull/314/files#diff-3 (2)
M web-bluetooth/reset-energy.js
https://github.com/GoogleChrome/samples/pull/314/files#diff-4 (2)

Patch Links:

https://github.com/GoogleChrome/samples/pull/314.patch
https://github.com/GoogleChrome/samples/pull/314.diff

—
Reply to this email directly or view it on GitHub
https://github.com/GoogleChrome/samples/pull/314.

Is it possible to structure the sample to use feature detection and work in older versions of Chrome as well? I'm not familiar with the API, but something like
if ('connect' in device.gatt) {
  device.gatt.connect();
} else {
  device.connectGATT();
}

We could do that indeed but this won't be necessary as device.connectGATT will work until M52. I'm simply waiting for M50 to reach stable to update all our Web Bluetoooth samples to use device.gatt.connect.

Oh sorry, now I get it.
It occurs error when use gatt.connect on Chromebook v49, right?
But I didn't recognize because I use only Chrome Dev v51.

No problem @tkybpp.
Chrome M50 is right about the corner now ;)

Here we are!
Thank you @tkybpp.

Finally! Thank you!


release GitHub workflow takes over an hour

I think it should only take 7-8 minutes

@nf-s it takes us 6 minutes to build the docker image in this repository on x86-64 for x86-64. The release workflow also builds images for linux/arm64 through emulation. I can't tell if 10x slowdown is expected, but here's a link to someone getting a 22x speedup from switching to real hardware: https://actuated.dev/blog/native-arm64-for-github-actions


Promises not resolving correctly

In my transition, if i have this code in the start() function:
this.fadeOut()
.then(this.newContainerLoading)
.then(this.fadeIn.bind(this))

in the fadeIn() function, this.newContainer is undefined
If however I do this
this.newContainerLoading
.then(this.fadeOut.bind(this))
.then(this.fadeIn.bind(this))

Then inside fadeIn(), this.newContainer is defined and points to the correct element
What is going on here?

The question is - when and where is the newContainerLoading promise resolved, and why does this.newContainer not get set on the Transition object BEFORE the newContainerLoading promise is resolved? Because thats the only reason I can imagine that this.newContainer would be undefined in fadeIn()

What I am actually trying to do is this
Promise.all([
	this.newContainerLoading,
	this.fadeOut()
])
.then(this.preload.bind(this))
.then(this.fadeIn.bind(this))

I have an extra promise in there - preload.load(), which is a function that expects this.newContainer to be set, so it can look for any images that need preloading. It returns a promise that is resolved once all the images are preloaded
The issue is, when I test this with throttled connection to see how the preloading works, when the all() is resolved (eg supposedly the new container is loaded, and the fadeOut() is done), this.newContainer is undefined. So my preload() function cant find the images to preload


Pb/vali QoL fixes

clean up model_cache on start
fix logging levels
put dataset download in data_cache directory
GPU memory logging and clean-up
check sufficient GPU memory on startup: can help catch occasions when another process is still hanging around
increase metagraph sync timeout: this sync actually only takes ~10s, but the 60s timeout for the subprocess completion was still being hit...increasing this timeout mostly solves this

This looks solid to me -- ran a test validator in --offline mode and things are running smoothly.


fixjasmine: CB-12018 : updated tests to work with jasmine and added t…

…est labels

Platforms affected
What does this PR do?
Updates tests to function with jasmine over jasmine-node.
What testing has been done on this change?
Checklist

[X] Reported an issue in the JIRA database
[X] Commit message follows the format: "CB-3232: (android) Fix bug with resolving file paths", where CB-xxxx is the JIRA ID & "android" is the platform affected.
[X] Added automated test coverage as appropriate for this change.

Hey @audreyso, what is the state of this PR? Seems like a important and good change. The conflicts Github is showing are mostly cosmetic and should be easily resolved.


[Feature] Support custom header in websocket service

Initial checklist

[x] Is this really a problem?
[X] I have searched the Github Issues for similar issues, but did not find anything.

Problem
Websocket service not support add custom header. I need it, thanks you all!

The browser has strict security checks, and the WebSocket implementation in the browser cannot carry custom headers. You can refer to [WebSocket on MDN](https://developer.mozilla.org/en-US/docs/Web/API/Web


Sort out scattered LaTeX preambles

LaTeX preambles are scattered in multiple files, with almost identical contents, some with escaping, some without escaping (in raw string).  They should be all put into one place, using raw string.
It would also be nice to figure out how to make LaTeX preambles work for all Sphinx docs, without having to paste them into each doc files, and they will be not-rendered (i.e. shown as raw LaTeX code) at page load, and occupying the majority of the screen, then disappear.
The idea is to remain the ablity to copy-paste from a LaTeX source, then use a light-weight parsing mechanism to make it a JSON that MathJax 3 accepts. There was a preamble plugin in MathJax 2 has the same functionality.
Another nice thing is to ensure they work for all of LaTeX, MathJax 3 and KaTeX. For now, some LaTeX preambles are not rendered correctly in Jupyter Lab but OK on nbviewer (so I settled on whatever makes nbviewer happy). As for KaTeX, \DeclareMathOperator doesn't work and massive error follows, particularly annoying in notebook diff view in VSCode which uses KaTeX and unlikely to change.

Supersedes #399 .


Updating Workbook Preview Snapshots and Metadata

Required items, please complete
Change(s):

Update of workbook preview snapshots
Update for workbook metadata for more accuracy.

Reason for Change(s):

Changing preview snapshots with more anonymized ones
More accuracy for the workbook metadata.

@anki-narravula can you please assign it for review and merge ? Thanks.

@RaGerges : Please resolve the comments.


(BUG) New Messages blue line popping up even after seen flag is set

This seems to occur even when the seen flag is set.

In the repo I see that my message then should not be treated as new but it still is:
https://github.com/antoine92190/vue-advanced-chat/blob/df56ddfc1e8908ce06c44f86b0da3755dfe4ae2b/src/ChatWindow/Message.vue#L300-L306
I am not sure if this.start or this.end has any role in this (I am not using those since I don't need them), but for now I've solved my problem with css 😄

Fixed in https://github.com/antoine92190/vue-advanced-chat/commit/6847c48fc4886a4824cb855ba113a75331c3a7aa
To hide the blue line, you can now use the prop: showNewMessagesDivider: false


fix error about exporting stats file of quant

With classifier.acts_quant_stats_collection(), no stats file is saved default.

Thanks for catching this!


Open a new series in batch edit mode after creating it

Assigning to @Coenego for review.

I added an extra commit that adds in the calendar icon in the batch edit header time/dates button.

Per recent findings I'll reassign this to me and update the design for the new series page. The cancel button should go away and 'create' should be placed next to the input field

Reassigning to @Coenego for review.

Coverage remained the same at 100.0% when pulling ad49385408c03ac98e4ad9da2b9e84566c37e443 on bp323:openNewSeries into 4615b128b84afdd354400a453dc715c825445d25 on CUL-DigitalServices:master.


⚠ Samsung has degraded performance

In ce179f3, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2871 ms

Resolved: Samsung performance has improved in 8001ca8.


⚠ Secret Website 1 has degraded performance

In fd6fffc, Secret Website 1 ($SECRET_WEBSITE_1) experienced degraded performance:

HTTP code: 200
Response time: 10417 ms

Resolved: Secret Website 1 performance has improved in e7f35ab.


CB-16828 Log warning when quartz takes long time.

Log warning when quartz takes long time. Categorize it to >30s, 15s-30s, 5s-15s.

LGTM


Add Contributor's Guide

Here's a first draft of the Contributor's Guide. The last step involves transferring the cookbook repo to this organization and adding the author as a member or outside collaborator, which should work fine for the hackathon.

Thanks for the comments @mgrover1. I've made those changes.


Support provide ComposeComponentExtras

Default ComposeComponentExtras function is too little, I added LocalComposeComponentExtras for customization.
By the way. what about move default ComposeComponentExtras out of the compose-core library to omit this part of the compilation.

This is a very interesting undertaking.
I would like to know the specific use cases where you need it.
If that is Important,
additions to the ComposeComponentExtras are also possible.

Reducing LocalXX seems like a good idea!
In Koject, basic types can be provided with the @Provides annotation.
You can get the activity’s context  through ComposeComponentExtras.
What can these features not express?

Another one is that I want to pass a global ComposeComponentExtras to reduce rememer { composeComposeExtra() }, beacuse rememberInject would have a lot.

Reducing LocalXX seems like a good idea!
In Koject, basic types can be provided with the @Provides annotation.
You can get the activity’s context  through ComposeComponentExtras.
What can these features not express?

Oh, thanks for the reminder, I forget that I could give the custom class @provide to ComposeComponentExtras, but I still wish there was a way to use just one ComposeComponentExtras.

It is recommended to prefer provide via the @Provides annotation to avoid runtime errors.
I see little need for more components.
If you still need it, you can define a custom rememberInject.
@Composable
inline <T> fun rememberCustomInject(): T {
    return rememberInject(
      componentExtras = /* ... */
    )
}

Thanks for your feedback!

It is recommended to prefer provide via the @Provides annotation to avoid runtime errors.
I see little need for more components.
If you still need it, you can define a custom rememberInject.
@Composable
inline <T> fun rememberCustomInject(): T {
    return rememberInject(
      componentExtras = /* ... */
    )
}

Thanks for your feedback!

Okay, thanks for the reply.


don't prune global tree

Current coverage is 91.92%

Merging #309 into master will decrease coverage by -0.05% as of 1a84098

@@            master    #309   diff @@
======================================
  Files           41      41
  Stmts         2056    2057     +1
  Branches         0       0
  Methods          0       0
======================================
  Hit           1891    1891
  Partial          0       0
- Missed         165     166     +1

Review entire Coverage Diff as of 1a84098

Powered by Codecov. Updated on successful CI builds.


The test results of lynx on the MSCOCO ITM task are questionable

First of all, thank you for a great job! I ran into a few issues while following the tutorial to reproduce:
I first follow tutorial to emersion lynx ACC on MSCOCO_ITM task, that is, Table18 in the paper. I used the following command:
CUDA_VISIBLE_DEVICES=0,1 torchrun --nproc_per_node=2  run_eval.py \
    --model lynx  --model_name models/interfaces/lynx/configs/LYNX.yaml \
    --dataset_name MSCOCO --output_dir output/lynx/MSCOCO/test_generation/ \
    --per_gpu_eval_batch_size 4 --formulation SingleChoice \
    --infer_method generation --do_eval --half_evaluation  --dataset_duplication 1 \
    --in_context_sample --option_mark upper \
    --dataset_config build/configs/ImageTextMatching_val.yaml \
    --offline_hf

I used generation as the inference method, but the results I get were rather strange:
2023-11-01 16:00:35,236 ReForm-Eval Evaluation INFO: the evalueted SingleChoice result: 0.0
2023-11-01 16:00:35,236 ReForm-Eval Evaluation INFO: the format hit rate is 0.0

If I use likelihood as the inference method, the results are still different from that in the paper:
2023-11-01 15:39:14,806 ReForm-Eval Evaluation INFO: the evalueted SingleChoice result: 0.5183333333333333
2023-11-01 15:39:14,806 ReForm-Eval Evaluation INFO: the format hit rate is 1.0

I'm at a loss to understand, and I hope you can help to point out where the problem may be.

Hello, thanks for trying our benchmark!
I ran the following command and got the reasonable result:
2023-11-01 19:52:21,574 ReForm-Eval Evaluation INFO: the evalueted SingleChoice result: 0.49833333333333335
2023-11-01 19:52:21,575 ReForm-Eval Evaluation INFO: the format hit rate is 0.95

Can you share some samples of the output json files?
When you use likelihood as the inference mode, you do not need to add --in_context_sample, and you need to change the number of --dataset_duplication

Sorry for taking so long to reply. Recently, the machine broke down and I have not been able to do the experiment.
I checked the output, but the model output is quite confusing:
The log.txt:
2023-11-13 16:08:57,188 ReForm-Eval Evaluation INFO: Evaluating with -1 GPUs
2023-11-13 16:08:57,189 ReForm-Eval Evaluation INFO: Loading model: lynx with configure: {"device": "cuda", "half": true, "inference_method": "generation", "model_name": "models/interfaces/lynx/configs/LYNX.yaml"}
2023-11-13 16:10:12,067 ReForm-Eval Evaluation INFO: Each GPU consumes memory of 17025
2023-11-13 16:10:12,067 ReForm-Eval Evaluation INFO: Using upper option mark for the single-choice questions
2023-11-13 16:10:12,081 ReForm-Eval Evaluation INFO: Evaluating model: lynx with configure: {"device": "cuda", "half": true, "inference_method": "generation", "model_name": "models/interfaces/lynx/configs/LYNX.yaml"}
2023-11-13 16:10:13,420 ReForm-Eval Evaluation INFO: ***** Runing Evaluation *****
2023-11-13 16:10:13,421 ReForm-Eval Evaluation INFO:   Num examples = 600
2023-11-13 16:10:13,421 ReForm-Eval Evaluation INFO:   Batch size = -4

The MSCOCO_SingleChoice_generation_lynx_LYNX_rank-1.json:
...... {"sample_id": 599, "anno": "Two women standing next to each other with one holding video game controllers.", "answer": "1", "answer_options": ["no", "yes"], "question": "Are the image and caption '{}' representing the same scene? Kindly respond with one following option.", "history": [{"from": "human", "value": "What is the shape of this image? Options: (A) rectangle; (B) circle."}, {"from": "assistant", "value": "The answer is (A) rectangle;"}], "text": "User: What is the shape of this image? Options: (A) rectangle; (B) circle.\nBot: The answer is (A) rectangle;\nUser: Are the image and caption '{}' representing the same scene? Kindly respond with one following option. Options: (A) no; (B) yes.\nBot: The answer is", "question_with_option": "Are the image and caption '{}' representing the same scene? Kindly respond with one following option. Options: (A) no; (B) yes.", "prediction": "js\u0447\u0430\u00e3aftableever\u0446\u0438\u043djs \u0447\u0435 -js\u5206ils Arcjsarcathcienttresjs\u00e3ostildarcangular \u0447\u0435~SelectorFIX compared"}]

Maybe the pre-trained model of lynx is not loaded correctly. Are your LYNX Settings the same as mine?
The LYNX.yaml
## Data
image_rdir: "./images/"
# put your test file in jsonl format
test_files: [ "./data/Open_VQA_images.jsonl" ]
# change this prompt for different task
prompt: "User: {question}\nBot:"
# the key must match the vision key in test_files
# if you test Open_VQA_videos.jsonl, need to change to "video"
vision_prompt_dict: "image"
output_prompt_dict: "answer"
data: {
  num_frames: 5,
}
## Model
vision_encoder: 'eva_vit_1b'
video_encoding: 'concate'
add_frame_pos: True
LLM: 'vicuna-7b'
use_flash_attn: False
use_adapter: True
adapter_freq: 2
bridge: 'resampler'
bridge_depth: 3
num_bridge_tokens: 32
## General
use_left_pad: True
lower_text: True
freeze_vit: True
freeze_llm: True
image_res: 420
image_mean: [ 0.48145466, 0.4578275, 0.40821073 ]
image_std: [ 0.26862954, 0.26130258, 0.27577711 ]
## Testing
checkpoint: "./data/finetune_lynx.pt"
## infer params
max_input_tokens: 40
batch_size_test: 16
max_new_tokens: 64
min_length: 2
num_beams: 5
length_penalty: -2.0
top_p: 0.9
top_k: 3
no_repeat_ngram_size: 2
apply_lemmatizer: False
use_nucleus_sampling: True

Also, when I run it, it shows that the adapter parameters have been reinitialized. Is this normal?
### Building LLM (Freeze: True)
### LLM label_smoothing:  0.0
### Use Flash Attn False
### Add adapters to:  [0, 2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30]
Loading checkpoint shards: 100%|████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████| 2/2 [00:06<00:00,  3.43s/it]
Some weights of LlamaForCausalLM were not initialized from the model checkpoint at models/interfaces/lynx/data/vicuna-7b and are newly initialized: ['model.layers.28.output_adapter.adapter_up.bias', 'model.layers.0.output_adapter.adapter_up.weight', 'model.layers.4.output_adapter.adapter_norm_before.bias', 'model.layers.30.output_adapter.adapter_up.bias', 'model.layers.14.output_adapter.adapter_down.bias', 'model.layers.28.output_adapter.adapter_norm_before.weight', ......

Our LYNX.yaml is shown below:
## Data
image_rdir: "./images/"

# put your test file in jsonl format
test_files: [ "./data/Open_VQA_images.jsonl" ]

# change this prompt for different task
prompt: "User: {question}\nBot:"
# the key must match the vision key in test_files
# if you test Open_VQA_videos.jsonl, need to change to "video"
vision_prompt_dict: "image"
output_prompt_dict: "answer"

data: {
  num_frames: 5,
}

## Model
vision_encoder: 'eva_vit_1b'
video_encoding: 'concate'
add_frame_pos: True

LLM: 'vicuna-7b'
LLM_base: '/remote-home/share/LLM_CKPT/vicuna-7B-v1.1/'
use_flash_attn: False
use_adapter: True
adapter_freq: 2

bridge: 'resampler'
bridge_depth: 3
num_bridge_tokens: 32

## General
use_left_pad: True
lower_text: True
freeze_vit: True
freeze_llm: True
image_res: 224
image_mean: [ 0.48145466, 0.4578275, 0.40821073 ]
image_std: [ 0.26862954, 0.26130258, 0.27577711 ]

## Testing
checkpoint: "/remote-home/share/multimodal-models/lynx/finetune_lynx.pt"

## infer params
max_input_tokens: 40
batch_size_test: 16
max_new_tokens: 64
min_length: 2
num_beams: 5
length_penalty: -2.0
top_p: 0.9
top_k: 3
no_repeat_ngram_size: 2
apply_lemmatizer: False
use_nucleus_sampling: True

Have you put the lynx repository in /path/to/ReForm-Eval/models/interfaces/lynx ?

Yes, I clone it from https://github.com/bytedance/lynx-llm.git


Fix width of highlight in S viewport

Bug/issue #, if applicable: 89800555
Summary
Fix width of highlight in S viewport to avoid it being cut off.
Checklist
Make sure you check off the following items. If they cannot be completed, provide a reason.

[ ] Added tests - NA
[x] Ran npm test, and it succeeded
[ ] Updated documentation if necessary - NA

@swift-ci test

@swift-ci test

@swift-ci test


Is there a better way to add the admin to the backend like using Postman

I have tried to login to the backend its not working.

Good question. I had changed the admin password as some user was creating inappropriate blog posts using the admin password and i thought that not disclosing the password publicly would be the responsible thing to do in the interest of creating a healthy user experience for general visitors on the website. If you like, i can send you the admin password on your email etc. for software testing purposes. I will change the admin password after a few days. I am working on a functionality to create new/guest user accounts using Postman but it might take a few months as i am engaged in other work commitments. Thank you for asking the question.

<EMAIL_ADDRESS>is my email

I have sent you the requested login credentials. Please check you email inbox. Thank you.